HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Default routes stop working
Operating System - HP-UX
1834169
Members
2736
Online
110064
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-27-2000 10:46 AM
05-27-2000 10:46 AM
We have experienced a new problem on HPUX 11.x where our default routes stop working after a couple of minutes if at all. Static routes work fine. The default route remains viewable using netstat -rn but they don't work.
Right the first time!
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-28-2000 06:58 AM
05-28-2000 06:58 AM
Solution
Check for dead gateway detection. By default this is one at 11.0. If your firewall is the gateway and doesn't accept ICMP, then after so many tries of pinging, 11.0 will "turn off" the gateway. To see all gateways you could use ip_ire_status
ndd -get /dev/ip ip_ire_status | grep -e IRE_GATEWAY -e flag
This results in a list of all gateways, the flags will indicate a dead gateway.
Another option ip_ire_gw_probe_interval is available which changes the frequency in which such probes will be performed.
Why would this be used?
The gateway probes are ICMP packets which await a proper reply.
In cases where e.g. a firewall is used it could be wanted to turn off ICMP, so nobody could ping the firewall but still it works for the desired protocols.
So turning it off would not compromise the work, because we would never send an ICMP packet to test the machine.
On the other hand we would only know if a gateway is not operational if we try to use it. This results in long timeouts during the detection.
Usable commands:
Check the current value:
ndd -get /dev/ip ip_ire_gw_probe
Disable Dead Gateway Detection:
ndd -set /dev/ip ip_ire_gw_probe 0
Regards,
Berlene
ndd -get /dev/ip ip_ire_status | grep -e IRE_GATEWAY -e flag
This results in a list of all gateways, the flags will indicate a dead gateway.
Another option ip_ire_gw_probe_interval is available which changes the frequency in which such probes will be performed.
Why would this be used?
The gateway probes are ICMP packets which await a proper reply.
In cases where e.g. a firewall is used it could be wanted to turn off ICMP, so nobody could ping the firewall but still it works for the desired protocols.
So turning it off would not compromise the work, because we would never send an ICMP packet to test the machine.
On the other hand we would only know if a gateway is not operational if we try to use it. This results in long timeouts during the detection.
Usable commands:
Check the current value:
ndd -get /dev/ip ip_ire_gw_probe
Disable Dead Gateway Detection:
ndd -set /dev/ip ip_ire_gw_probe 0
Regards,
Berlene
http://www.mindspring.com/~bkherren/dobes/index.htm
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-28-2000 05:18 PM
05-28-2000 05:18 PM
Re: Default routes stop working
Hi
If your default gateway is not working ! check the following
1.Can you ping to default route ?
2.what netstat -rn shows for defaultgateway does it say UG on flag
3.Normally packets will be transfered through nearest path first and then next nearest , and finally if doesn't find any route it goes through default route .
If your default gateway is not working ! check the following
1.Can you ping to default route ?
2.what netstat -rn shows for defaultgateway does it say UG on flag
3.Normally packets will be transfered through nearest path first and then next nearest , and finally if doesn't find any route it goes through default route .
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-28-2000 11:20 PM
05-28-2000 11:20 PM
Re: Default routes stop working
Hi,
Check if the arp entry for the host at your gateway is correct.
If it is wrong, you may which to flush that entry via arp -d.
Regards.
Steven Sim.
Check if the arp entry for the host at your gateway is correct.
If it is wrong, you may which to flush that entry via arp -d.
Regards.
Steven Sim.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP