Backup IP address is "unpingable"

[Derek Brown]

Hi guys,

I hope you can help me with this one. I'm quite new to HP so I feel I might be missing something really obvious.

I've built a new HPUX 11.11 server called senegal. This server will run backup client software. The main lan (senegal) works fine but the backup lan (senegali4 ; IP=10.141.70.120) is only pingable from senegal but nowhere else on the company network, in particularthe backup server (ngtsvshdc001). In order for the backup software to work ngtsvshdc001 must be able to ping senegali4.

I've checked what I think are all of the obvious things on senegal .... /etc/hosts, resolv.conf, nsswitch.conf, netconf and can't see anything obviously wrong.

All of our backups take place via the .70 subnet. While on ngtsvshdc001 I can ping other servers on the .70 subnet fine but not senegali4.

The onsite engineer has taken his laptop down to the computer room and unplugged the backup cable from the back of the server, plugged it into his laptop and configured his laptop to have an IP of 10.141.70.120. I then pinged that IP address from ngtsvshdc001 and it pinged out OK; which infers there is nothing wrong with the network cabling I think.

I've attached a file with output from both senegal and ngtsvshdc001 that might aid resolution. Many thanks for your help in advance.

[Calandrello]

Friend
is necessary that its server of backup is if communicating with its server client saw net or saw SAN. so that ok functions.

[Coolmar]

Can you post the output of

#netstat -r

[spex]

Hi Derek,

Try adding ROUTE_DESTINATION[1] and ROUTE_GATEWAY[1] statements to /etc/rc.config.d/netconf. Then, from the console, restart networking services:

# /sbin/init.d/net stop
# /sbin/init.d/net start

PCS

[Coolmar]

Yeah, it looks like you have the default route setup for the lan1 but not the lan5. You will have to add a route for it using "route add"

[Mel Burslan]

To summarize the last two posts, first try to add the route to this ngtsvshdc001 server, dynamically

route add 10.141.70.120 1

this above command is not a good one as it points to an interface on the same server as the gateway, instead of an actual network device, such as a router. If you know the default gateway IP address on this backup network (usually network folks place them as the .1 or .254 addresses in the last octet of ip address but check with them to be sure if you want to go this route) and replace the 10.141.70.120 in the above command with this gateway ip address.

after verifying that it is working, you can make this change permanent by adding it into your /etc/rc.config.d/netconf file as follows:

ROUTE_DESTINATION[1]=""
ROUTE_MASK[1]=""
ROUTE_GATEWAY[1]="10.141.70.120"
ROUTE_COUNT[1]="1"
ROUTE_ARGS[1]=""

again it is better to put the gateway on the ROUTE_GATEWAY line, and place this block right under the "default" route block and stop and start the network services as indicated above.

Looking at the netconf file in your attachment, I have a sneaking suspicion that your default gateways are all placed in .254 addresses but to make sure, check with your network folks to see if 10.141.70.254 is your default gateway for the backup lan.

Hope this helps

[Sp4admin]

yes,

You need ot make sure you have a entry for both gateways. Check the /etc/rc.config.d/netconf file. you may net to stop and restart the network.

#/sbin/init.d/net stop
# /sbin/init.d/net start

sp,