Setup Private network for Service Guard

[Mark Fisher_4]

We used the suggestion to establish a private network to run all the Service Guard heartbeat activity over a private lan. So we have a lan0 interface plugged into a switch with the following network params:

subnet = 146.1.196.96
subnet mask = 255.255.255.224
default gateway = none since this is a private lan that is not routed.

We also have a lan1 interface connected to a normal routed lan.

subnet = 146.1.199.0
subnet mask = 255.255.255.128
default gateway = 146.1.199.126

So I assign an ip address of 146.1.196.97 to lan0, the private lan interface, and 146.1.196.98 to lan0 on another server. I can actually ping and login between the 2 servers using these ip addresses. But if I shutdown (unplumb) the lan1 interface, then I cannot ping/login between the servers on the private network.

So I guess I need to establish a static route. I have tried it manually with the route command and also by modifying /etc/rc.config.d/netconf and bouncing /sbin/init.d/net with no luck.

One think that confuses me about this private network is that it doe not have a gateway ip address assigned to it. So I use the ip address of the lan0 (private) interface to either a host or a net on the private lan hopeing for force all activity to this network over lan0 and it does not work.

So, any ideas? Anybody ever set up a private network like this for service guard?

[Victor Fridyev]

Hi,

Please check the network properties:
Broadcast: 146.1.196.127
subnet mask = 255.255.255.224
subnet = 146.1.196.96, address range 97-126

In order to check whether the physical connection is OK, run
#>traceroute 146.1.196.98
from the first server. If you see the way through default gateway, check whether the switch is configured properly. BTW, you can use crossed cable instead of switch. You don't need to define a router on the private network

HTH

[Stafford]

How are pinging/connection, is it via name or ip address?