topic Re: routing issue in Operating System - HP-UX

routing issue

Jeff Hagstrom — Thu, 20 Apr 2006 08:48:41 GMT

I have 2 HPK460 and a RP7410 all running HPUX 11.00. 1 of the 460's and the RP7410 are at the same plant(10.20.*.*) and the other one is at 10.55.*.*. The problem that I'm having is that one of the 460's(the one at the 10.20 site) can not ping a plant in S.C. and vise versa, they can't ping it. Are there any routing tables on the box that need to be setup? What could the problem be?

Re: routing issue

Patrick Wallek — Thu, 20 Apr 2006 08:56:06 GMT

Is your default route set?

What is the output of:

# netstat -rn

Re: routing issue

Steven E. Protter — Thu, 20 Apr 2006 08:59:19 GMT

Shalom Jeff.

Set default route as follows:
set_parms

vi /etc/rc.config.d/netconf

SEP

Re: routing issue

Tiziano Contorno _ — Thu, 20 Apr 2006 09:01:58 GMT

I would check connectivity beetwen the K and its gateway, since it cannot be reached from the external network.

Re: routing issue

jamesps — Thu, 20 Apr 2006 09:05:39 GMT

As said above all you need to do is simply edit this file: /etc/rc.config.d/netconf

Make sure you have the appropriate routes in place, there should be something like:

ROUTE_DESTINATION[2]="default"
ROUTE_MASK[2]=""
ROUTE_GATEWAY[2]="192.168.1.1"
ROUTE_COUNT[2]="1"
ROUTE_ARGS[2]=""

where:
[2] is the interface number
the mask is optional
192.168.1.1 is the gateway IP address
ROUTE_COUNT=1 means is a remote gateway (not local)

Hth,
james

Re: routing issue

Jeff Hagstrom — Thu, 20 Apr 2006 10:02:15 GMT

Let me add a little to this. We have 14 plants and 12 of them can get to this one box and 2 can't. The 2 that can't are on these firebox soho routers. They can get to the production box(RP7410), but they can't connect to or ping the test box(K460). The netconf files are identical on all 3 boxes. I think it has something to do with the soho routers, but I just wanted to check to see if I was missing anything.

Re: routing issue

Jeff Hagstrom — Thu, 20 Apr 2006 10:02:35 GMT

Re: routing issue

jamesps — Thu, 20 Apr 2006 12:06:11 GMT

NDD may disable your default gateway if that gateway is secured and for example does not echo out icmp requests.

see if you have a dead gateway:
#ndd -get /dev/ip ip_ire_status
if the output is IRE_GATEWAY DEAD then this may explain your problem and you can disable the dead gateway detection by modifying
#ndd -get /dev/ip ip_ire_gw_probe

If the output is 1 then it means that the dead gateway detection is turned on. You can turn it off using
#ndd -set /dev/ip ip_ire_gw_probe 0

To make it permanent make entries in the /etc/rc.config.d/nddconf file

james