1836442 Members
3588 Online
110100 Solutions
New Discussion

Re: can't connect to NW

 
PiyuT
Occasional Advisor

can't connect to NW

dear all,

we have a problem.we have 2 server L class that can't to network.if we delete the degault gateway with run "route delete default 10.x.x.x" and run commnad "/sbin/init.d/net stop && /sbin/init.d/net start", we can connect to network and can ping to gateway.but it can't connect to network again after a few minutes.
please,give me solutions!!!

thx,
piyut
7 REPLIES 7
steven Burgess_2
Honored Contributor

Re: can't connect to NW

Hello

Looks like you have duplicate ip addresses in your environment. Do you have nettl running ?

nettl -status ?

If not start it with
nettl -start

your commands again then check to see whats happening

netfmt -t 30 /var/adm/nettl.LOG00 > /tmp/netfmt.out

HTH

Steven
take your time and think things through
bhavin asokan
Honored Contributor

Re: can't connect to NW

hi,

seems like duplicate ipaddress in the network.
we were having same problem.it was due to the host router/switch ipaddress was given to another host in the network.

regds,


Ravi_8
Honored Contributor

Re: can't connect to NW

Hi,

Looks like you have duplicate IP address, check for the same
never give up
PiyuT
Occasional Advisor

Re: can't connect to NW

the result for nettl.how to detect that ip is duplicate ??? sorry, i'm newbie in HP.


# nettl -status

Logging Information:
Log Filename: /var/adm/nettl.LOG0*
Max Log file size(Kbytes): 1000 Console Logging: On
User's ID: 0 Buffer Size: 8192
Messages Dropped: 0 Messages Queued: 0

Subsystem Name: Log Class:
NS_LS_LOGGING ERROR DISASTER
NS_LS_NFT ERROR DISASTER
NS_LS_LOOPBACK ERROR DISASTER
NS_LS_NI ERROR DISASTER
NS_LS_IPC ERROR DISASTER
NS_LS_SOCKREGD ERROR DISASTER
NS_LS_TCP ERROR DISASTER
NS_LS_PXP ERROR DISASTER
NS_LS_UDP ERROR DISASTER
NS_LS_IP ERROR DISASTER
NS_LS_PROBE ERROR DISASTER
NS_LS_DRIVER ERROR DISASTER
NS_LS_RLBD ERROR DISASTER
NS_LS_BUFS ERROR DISASTER
NS_LS_CASE21 ERROR DISASTER
NS_LS_ROUTER21 ERROR DISASTER
NS_LS_NFS ERROR DISASTER
NS_LS_NETISR ERROR DISASTER
NS_LS_NSE ERROR DISASTER
NS_LS_STRLOG ERROR DISASTER
NS_LS_TIRDWR ERROR DISASTER
NS_LS_TIMOD ERROR DISASTER
NS_LS_ICMP ERROR DISASTER
FILTER ERROR DISASTER
NAME ERROR DISASTER
NS_LS_IGMP ERROR DISASTER
FC ERROR DISASTER
FORMATTER ERROR DISASTER
STREAMS ERROR DISASTER
BASE100 ERROR DISASTER
SPP100BT ERROR DISASTER


Tracing Information:
Trace Filename:
Max Trace file size(Kbytes): 0
No Subsystems Active
PiyuT
Occasional Advisor

Re: can't connect to NW

When we can't ping to ip address of this server from my PC,about 2 minutes timed out.if there is duplicate ip, when we ping from my PC should be not timed out, but still timed out.why ??
Ron Kinner
Honored Contributor

Re: can't connect to NW

This is nothing more than the standard Dead Gateway detection problem. Your gateway does not respond to pings and HP thinks it must be dead. The usual time out is on the order of 3 minutes. You can check it with

ndd -get /dev/ip ip_ire_gw_probe

if that comes back 1 then you need to turn it off with:

ndd -set /dev/ip ip_ire_gw_probe 0


Then remove and re-add your default gateway. (The mechanism that re-enables the gateways is turned off too so you need to wake it up.)

To make it stick during a reboot you need to edit /etc/r.config.d/nddconf to add:

TRANSPORT_NAME[0]=ip
NDD_NAME[0]=ip_ire_gw_probe
NDD_VALUE[0]=0

Use the next higher integer in the brackets if you already have entries in nddconf.

Ron


PiyuT
Occasional Advisor

Re: can't connect to NW

thx for ron,

the gateway does not respond for ping command because of closed.than i open so gateway can respond for ping command.

thank you.