Serviceguard
Showing results for 
Search instead for 
Do you mean 

Subnet mask change in 11.20 2 node cluster

Occasional Contributor

Subnet mask change in 11.20 2 node cluster

[ Edited ]

Hi ,

 

We have a 2 node 11.20 ServiceGuard Cluster

 

I am about to change only the subnet mask of one of the configured network .

 

(The subnet will remain the same only the mask changes.)

 

I am not sure whether I need to halt the cluster in 11.20 . If halt is needed then do I need to reapply the Cluster configuration . Because no where in the cluster and package configurtion I can see that subnet mask has been mentioned.

 

 

 

P.S. This trhead has been moevd from HP-UX > General HP-UX > Serviceguard. - Hp forum Moderator

 

 

2 REPLIES
Honored Contributor Honored Contributor

Re: Subnet mask change in 11.20 2 node cluster

I would recommend shutting down the cluster.  Changing the subnet mask will require networking to be stopped and restarted, which would affect your cluster.

 

In a test cluster I have, the package control script does mention the subnet mask.  In our definition:

 

IP[0]=1.1.1.229
SUBNET[0]=1.1.1.0
(netmask=255.255.255.0)

 

 

Highlighted
Honored Contributor Honored Contributor

Re: Subnet mask change in 11.20 2 node cluster

Serviceguard A.11.20 knows the netmask of the NICs identified in the cluster binary file.

Example:

# cmviewcl -v -f line | grep netmask
node:rxh17u07|interface:lan3|ip_address:10.226.82.25|netmask=255.255.254.0
node:rxh17u07|interface:lan2|ip_address:192.168.82.25|netmask=255.255.255.0
node:rxh17u09|interface:lan3|ip_address:10.226.82.24|netmask=255.255.254.0
node:rxh17u09|interface:lan2|ip_address:192.168.82.24|netmask=255.255.255.0

 

In order for Serviceguard to update the cluster binary file with the new netmask, you must comment the _IP reference from the cluster ASCII configuration file, cmapplyconf the update (online ok), then re-add the IP.  Note that Serviceguard will reject this if the indicated IP is the sole Heartbeat_IP.   

 

Also note that /etc/rc.config.d/netconf must be updated and actions of the NIC should be quiesced during the transistion.