cmcheckconf error

[Rainer von Bongartz]

Hi guys,

I get a strange error when running cmcheckconf on my cluster configuration:

HEARTBEAT_IP address for NETWORK_INTERFACE lan1 cannot be modified from to for node nova while cluster is running.

The HEARTBEAT_IP has not been changed AND cmcheckconf really reports two IDENTICAL IP addresses.

Why does cmcheckconf think the IP address has been modified to an identical IP address ??

Regards
Rainer

[melvyn burnard]

There could be something strange in your network config.
I would suggest you do a review of the cluster, by using cmscancl and then reading the output file to verify whether all is as it should be.

[Henk Geurts]

did you check the timestamp on the clusterascii file ?
was it modified recently ?

[Luk Vandenbussche]

Hi,

Use cmgetconf to get the info of the running config.

[Geoff Wild]

It could be just about anything...

I would do as others have suggested.

Run a cmgetconf, then run a cmcheckconf against that new file.

If okay - then make your change(s) and re run the cmcheckconf on that ascii file

Rgds...Geoff

[John Bigg · Accepted solution]

I'd suggest the problem is that something about the IP address has changed which is stored in the binary file but which is not explictly set. For example the netmask.

If the netmask is changed I'd think you would get this error.