SG Subnet Information.

[joe_91]

All:

Our network team gave the ip/subnet information for the new servers. I have done the SG work with the given information. when i did a quercl it gave another subnet (diff from what the network team gave me). Also netstat -in shows the same ip that querycl gave me. Now shd i change the netconf file with this subnet info?. I have got the netconf file with the OLD subnet info (th one from the net team). will that cause a problem? Pl Help

Thanks

Joe

[Sridhar Bhaskarla · Accepted solution]

Hi Joe,

You will have to either change the subnet(mask) on the interface or use the same subnet that is shown in 'netstat -in' with serviceguard. Basically serviceguard mounts the floating IP based on the subnet. If that subnet is not found on the server, then it can't launch the package.

-Sri

[Sanjay_6]

Hi Joe,

If the subnet info in the netconf file is differnet than what the network team gave you, it should be changed and the server rebooted to pickup the ip and new subnet info. You should then do a cmquerycl to see if you got the proper ip and subnet info over there.

Also if you will be using any floating ip on the cluster, make sure one of the interface on the cluster node is in the same subnet. A floating ip binds to the network interface that belongs to the same subnet as the flocating / package ip subnet.

Hope this helps.

Regds

[joe_91]

So, should I change the entry in netconf to the value i get in netstat -in?

Thanks

Joe

[Sanjay_6]

Hi Joe,

Can you post the output of netstat -in and also the entry that you currently have in /etc/rc.config.d/netconf

Thanks
Sanjay

[Sridhar Bhaskarla]

Joe,

Your 'netstat -in' is nothing but a reflection of entries in your netconf file. If your network team gave you a different subnet, then you should configure that subnet (using the appropriate subnetmask in your netconf) on the system.

I would suggest you to check with network team on why they gave you different information now. Tell them that you have to change your subnet configuration on the system before you can use it for serviceguard. They might have mistaken. It happens here all the time.

-Sri