GreenLake Administration
- Community Home
- >
- Networking
- >
- Legacy
- >
- Communications and Wireless
- >
- route update
Communications and Wireless
1847175
Members
5573
Online
110263
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
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
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
10-20-2002 11:39 AM
10-20-2002 11:39 AM
route update
I've got a problem when I disconnect my HP 8000 workstation to the network. After being connected back to the switch, the route is not update and I cannot access back to the network. In the /etc/rc.config.d/netconf file, my main network is correctly defined as address[0] and I've got as well a default address. Other information , I'm not using dynamic routes ( gated in not used ) but static routes.
What need to be configured to able route update after network disconnection and reconnection.
Thanks
What need to be configured to able route update after network disconnection and reconnection.
Thanks
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-21-2002 06:35 AM
10-21-2002 06:35 AM
Re: route update
See if:
ndd -get /dev/ip ip_ire_gw_probe_interval
comes back with a non-zero value (probably 180000)
When you disconnect the network HPUX can not ping the default gateway so it assumes it is dead. It should start working again in about 3 minutes (or whatever yours has been changed to if not 180000) but odds are you weren't that patient.
"ip_ire_gw_probe_interval:
Controls the probe interval for Dead Gateway Detection.
IP periodically probes active and dead gateways.
ip_ire_gw_probe_interval controls the frequency of probing.
With retries, the maximum time to detect a dead gateway is
ip_ire_gw_probe_interval + 10000 milliseconds. Maximum time
to detect that a dead gateway has come back to life is
ip_ire_gw_probe_interval. [15000,- ]
Default: 180000 (3 minutes)"
ndd -set /dev/ip ip_ire_gw_probe_interval 0
will turn it off so you can test to see if that solves your problem but in order to make it stay after a reboot you have to edit /etc/rc.config.d/nddconf to add:
TRANSPORT_NAME[0]=ip
NDD_NAME[0]=ip_ire_gw_probe_interval
NDD_VALUE[0]=0
(If you already have entries in nddconf then put this at the end of the file and change the [0]'s to whatever the next number is in the sequence.)
Ron
ndd -get /dev/ip ip_ire_gw_probe_interval
comes back with a non-zero value (probably 180000)
When you disconnect the network HPUX can not ping the default gateway so it assumes it is dead. It should start working again in about 3 minutes (or whatever yours has been changed to if not 180000) but odds are you weren't that patient.
"ip_ire_gw_probe_interval:
Controls the probe interval for Dead Gateway Detection.
IP periodically probes active and dead gateways.
ip_ire_gw_probe_interval controls the frequency of probing.
With retries, the maximum time to detect a dead gateway is
ip_ire_gw_probe_interval + 10000 milliseconds. Maximum time
to detect that a dead gateway has come back to life is
ip_ire_gw_probe_interval. [15000,- ]
Default: 180000 (3 minutes)"
ndd -set /dev/ip ip_ire_gw_probe_interval 0
will turn it off so you can test to see if that solves your problem but in order to make it stay after a reboot you have to edit /etc/rc.config.d/nddconf to add:
TRANSPORT_NAME[0]=ip
NDD_NAME[0]=ip_ire_gw_probe_interval
NDD_VALUE[0]=0
(If you already have entries in nddconf then put this at the end of the file and change the [0]'s to whatever the next number is in the sequence.)
Ron
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 2026 Hewlett Packard Enterprise Development LP