Networking
cancel
Showing results for 
Search instead for 
Did you mean: 

Dead gateway detection can't ping

pgaidai
Occasional Contributor

Dead gateway detection can't ping

Hello everybody.

 I have a problelm.Periodically lost access to the server.

In the syslog :

 

Jul 12 12:41:55 kv1usc02 vmunix: Dead gateway detection can't ping the last remaining default gateway at 0xa24d4fe .See ndd -h ip_ire_gw_probe for more info 

Jul 12 12:44:55 kv1usc02 vmunix: Dead gateway detection can't ping the last remaining default gateway at 0xa24d4fe .See ndd -h ip_ire_gw_probe for more info

Jul 12 12:56:55 kv1usc02 vmunix: Dead gateway detection can't ping the last remaining default gateway at 0xa24d4fe .See ndd -h ip_ire_gw_probe for more info

Jul 12 12:59:55 kv1usc02 vmunix: Dead gateway detection can't ping the last remaining default gateway at 0xa24d4fe .See ndd -h ip_ire_gw_probe for more info

 

netfmt -f /var/adm/nettl.LOG000

-----------------------------------STREAMS/UX-------------------------------@#%

Timestamp : Thu Jul 12 EETDST 2012 11:56:54.507066

Process ID : [ICS] Subsystem : STREAMS

User ID ( UID ) : -1 Log Class : ERROR Device ID : 0 Path ID : 0

Connection ID : 0 Log Instance : 0 Location : 00123 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

1258 11:56:54 566560188 1 T.. 0 0 Dead gateway detection can't ping the last remaining default gateway at 0xa24d4fe .See ndd -h ip_ire_gw_probe for more info

 

 the dead gateway list is empty:

ndd -get /dev/ip ip_ire_hash

Gateway list:

    ire: 0xe0000003b270c188, addr 010.036.212.254, mask 000.000.000.000, src 010.036.212.112, type IRE_GATEWAY , next 0x0 Dead gateway list:

 

ndd -get /dev/ip ip_ire_status

IRE rfq stq addr mask src gateway mxfrg rtt ref type flag

e0000003b270c188 0000000000000000 0000000000000000 000.000.000.000 00000000 010.036.212.112 010.036.212.254 01500 00006 000 IRE_GATEWAY

 

 ioscan -fnClan

 

 Class I H/W Path Driver S/W State H/W Type Description
===================================================================
lan 0 0/2/1/0 iether CLAIMED INTERFACE HP AD331-60001 PCI/PCI-X 1000Base-T Adapter
lan 1 0/4/2/0 iether CLAIMED INTERFACE HP AB352-60003 PCI/PCI-X 1000Base-T Dual-port Core
lan 2 0/4/2/1 iether CLAIMED INTERFACE HP AB352-60003 PCI/PCI-X 1000Base-T Dual-port Core
lan 3 0/6/1/0 iether CLAIMED INTERFACE HP AD331-60001 PCI/PCI-X 1000Base-T Adapter

 

nwmgr

Name/ Interface Station Sub- Interface Related
ClassInstance State Address system Type Interface
============== ========= ============== ======== ============== =========
lan1 UP 0x001A4B09B4B6 iether 1000Base-T lan901
lan0 UP 0x00237D3D0A4A iether 1000Base-T lan900
lan2 UP 0x00237D3D0A4A iether 1000Base-T lan900
lan3 UP 0x001A4B09B4B6 iether 1000Base-T lan901
lan900 UP 0x00237D3D0A4A hp_apa hp_apa
lan901 UP 0x001A4B09B4B6 hp_apa hp_apa
lan902 DOWN 0x000000000000 hp_apa hp_apa
lan903 DOWN 0x000000000000 hp_apa hp_apa
lan904 DOWN 0x000000000000 hp_apa hp_apa

 

ndd -get /dev/ip ip_ill_status


ILL rq wq upcnt mxfrg err memavail ilmcnt name
e0000003b2725188 0000000000000000 0000000000000000 00001 32808 000 00000000 000001 lo0 RUNNING LOOPBACK MULTICAST
e000000402f4f380 e000000402ec8080 e000000402ec8280 00002 09000 000 00500000 000004 lan901 RUNNING BROADCAST CKO MULTICAST PORT CKO_IN TRAIN IPPS_POLICY_TOPS
e000000402f4f100 e000000402e4a580 e000000402e4a780 00003 01500 000 00000000 000004 lan900 RUNNING BROADCAST CKO MULTICAST PORT CKO_IN TRAIN IPPS_POLICY_TOPS
Reassembly memory limit: 2000000: In use 0, Reserved 500000, Unreserved 1500000.

 

no ping from this server to gateway. How verify what is wrong?

2 REPLIES
Matti_Kurkela
Honored Contributor

Re: Dead gateway detection can't ping

> no ping from this server to gateway. How verify what is wrong?

 

So it is normal that the gateway 10.36.212.254 does not answer to pings?  In that case, the only thing wrong is that you've not told HP-UX that it is normal.

 

In that case, you should disable the dead gateway detection mechanism. This command disables it immediately:

ndd -set /dev/ip ip_ire_gw_probe 0

 To make the setting persistent over system reboots, you must also edit /etc/rc.config.d/nddconf file. If the nddconf file has no other uncommented settings in it, add these three lines:

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

 If there are other uncommented settings in the file, add the same three lines but increment the number in [brackets] so that it does not conflict with any existing settings.

 

The error message: "Dead gateway detection can't ping the last remaining default gateway at 0xa24d4fe" means the system cannot ping the gateway 10.36.212.254. The gateway IP address is reported in hexadecimal format: 0x = hexadecimal number indicator, (0)a = 10, 24 = 36, d4 = 212, fe = 254.

 

But if the gateway should be answering to pings (i.e. it has done so before and it has not been changed or reconfigured), then this might indicate a problem in the gateway. If you can ping other devices in the same network segment, then the server's NIC and its cable is OK and the fault is with some network hardware. In that case, contact your network administrator and continue troubleshooting with him/her.

MK
RAUL SOSSA
Member

Re: Dead gateway detection can't ping

Your problem might be the need of this Network Card Interface Driver, have a look:

 

https://h20392.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=IEtherEnh-00

 

 

RAUL SOSSA

 

---------------------------------------------------------
Ing. RAUL SOSSA SOSSA.
IT Highend Infrastructure Solutions Engineer
SONDA Outsourcing Operation Services
http://www.sonda.com
---------------------------------------------------------