Netmasks for heartbeat ip addresses

[Bruno Bossier_1]

Can you specify a specific netmask for a cluster heartbeat ip adress ? I want to use the following addresses :

172.30.40.210 and 211 with netmask 255.255.255.240 but that does not seem to work.

Does Serviceguard determine the netmask himself based on the ip address you specify ? This is for a heartbeat via a point-to-point connection using a cross-cable.

Bruno

[melvyn burnard]

As long as the ip address and netmask are valid, there should be no issue from SG side of things.
These get set in the netconf file. One item to check is that the broadcast address is correct.
What errors are you getting, and is it on both nodes ?

[RAC_1]

Your ip address belongs to class C network, you can not have that netmask.

The default netmask for class c network is 255.255.255.0

Anil

[Bruno Bossier_1]

Netconf is not the problem. I can configure the interfaces through SAM with the ip addresses and netmasks as specified. It's Serviceguard who is complaining :

cmcheckconf gives an error that the netmask is not correct for the ip address specified.

Bruno

[melvyn burnard]

Is this a new SG configuration? or is it an exisiting running cluster?

[Bruno Bossier_1]

An existing cluster. The current ip addresses are :

192.168.1.1 (server 1) and 192.168.1.2 (server 2) with netmask 255.255.255.0. They are connected point-to-point through a cross-cable.

Bruno

[melvyn burnard]

Ah, are you trying to make these changes on line?
You should halt the cluster, make your chnages and then do cmapplyconf, to get the new netmask accepted.

[Bruno Bossier_1]

Well, I tried to do this online, but our cluster crashed. OK, stupid from me to do. I will try again when the cluster is down.

Thanks for the hint ...

Cheers,
Bruno

[Srinivas Krishnappa Sha]

Any changes w.r.t the heart beat IP address or cluster nodes Need to be done offline after bringing down the cluster and later you need to check and verify for these changes and apply them and bring the cluster up.