Network - Dual Interfaces with different host names on Veritas Master Server

[Rick Bowles]

I am running two interfaces in a HP9000/800 T520, HP-UX 10.20 with two seperate host names and seperate networks, a 10 network (backup) and a 209 (user)network. I have configured the netconf file to show specific entries for each interface and their route information to include ROUTE_DESTINATION, ROUTE_MASK, and ROUTE_GATEWAY etc.

The trouble exists when I start a Veritas backup the 209 address of the T520 server is transmitted to the 10 network to a ACSLS robotic server. The ACSLS server is only attached to the 10 network so It can not resolve the 209 address and posts an error.

How can I totally seperate traffic on the networks thus stopping the server form sending the 209 IP down the 10 network?

As a patch I have added a route on the ACSLS server to point back to the T520 for resolution, but I will not be able to leave the route for any length of time.

[Mark van Hassel]

Hi Rick,

To me it seems that the backup configuration uses the alias that is on the User network. The T520 will route ok to the backup server, but in its configuration is probably the alias on the user network that it cannot reach. You can do two things:
-Rename the alias for the user network of the T520 to the backup network alias on the backup server
- Add a route for the user network that points to the backup network ( I know this works on HPUX):

ROUTE_DESTINATION[1]=209.X.X.X #IP of T520 user
ROUTE_GATEWAY[1]=10.X.X.X #IP of T520 bck
ROUE_COUNT[1]=O

This will make all traffic to the 209 IP address go to the 10 IP address of the HPUX system.