Change Heartbit interface to standby

[Marcelo De Florio_1]

I need a change configuration of heartbit,eg:

NODE_NAME a2500
NETWORK_INTERFACE lan2
HEARTBEAT_IP 192.168.13.202
NETWORK_INTERFACE lan0
#Cambio - lan0 stand by de lan2
# HEARTBEAT_IP 192.168.13.203

so the messagge is:

cmcheckconf -k -C S2500.config.20020703

Begin cluster verification...

Error: Interface lan0 on a2500 has an IP address on it
(192.168.2.207), but the configuration file doesn't have it.
This may be caused by a local switch orchanges in the network configuration.
cmcheckconf : Unable to reconcile configuration file S2500.config.20020703
with discovered configuration information

any ideas

MDF

[Christopher McCray_1]

Hello,

You're going to have to deconfigure the lan0 card; the standby lan card is supposed to be unconfigured and on the same subnet as the primary data.

Additionally, you will need to change the entry for 1 or both the remaining cards from NETWORK_INTERFACE to HEARTBEAT_IP

Hope this helps

Chris

[Christopher McCray_1]

Hello,

Sorry, I didn't realize you only had 2 cards, but the above still applies.

Good luck

Chris

[Marcelo De Florio_1]

Christoper:

Why is not posible ?

MDF

[Christopher McCray_1]

Hello,

I don't understand; What is not possible.

You need to deconfigure the lan0 instance, that is, remove the IP address information either through sam or by removing its entry from netconf and rebooting.

You have to have at least one network interface configured as a heartbeat IP, so that leave you with lan2, judging by your output.

Chris

[Christopher McCray_1]

Hello again,

Another thought...

It might be better if after you deconfigure the card, that you save the old cluster.ascii file and do another cmquerycl, which will go through and give you another configuration file to work from.

Hope this helps

Chris

[Marcelo De Florio_1]

I have deconfigure lan0, and then i execute newly cmcheckconf, so the messagge is the following:

Error: Unable to communicate with node a2500
Error: Unable to determine device configuration: failed to send device query to
node a2500
Error: Unable to determine lvm configuration: failed to send lvm query to node a
2500

regards.

MDF

[Christopher McCray_1]

Hello again,

Yuck! Okay, was lan0, by chance, your primary data lan card?

Re-reading through your post, I noticed that your error was reporting a different IP address that what you had cofigured in the cluster.ascii file before you commented it out? Any history on this?

Is the cluster down at this time? (Just checking)

Have you tried running the cmquerycl on the nodes?

finally, can you post the entire S2500.config.20020703 file?

Thanks

Chris

[Christopher McCray_1]

I have seen your other post and I think I'm beginning to see your problem. It looks like you have forgotten to unconfigure the other side of your cluster to mirror the one you are changing. Your other node s2500 has a lan5 which is the counterpart to lan0 on a2500 and it has caused confusion. Also, you haven't tried to implement this while the cluster was up, did you? It wont like this.

Chris

[Sanjay_6]

Hi Marcelo,

A standby network port is not supposed to be configured with an ip address on the system.

Hope this helps.

Regds

[Marcelo De Florio_1]

sanjay:

hi, how can i to configure standby interface ?

regards

MDF

[Sanjay_6]

Hi,

Here is an example of the cluster ascii conf file.

In this file lan2 is standby,

NETWORK_INTERFACE lan2

Theis lan port does not have an ipaddress configured on the system. lan0 & lan1 are both data / heartbeat.

On one of the servers from which this file was taken,

# ifconfig lan0
lan0: flags=843
inet 171.56.42.21 netmask ffffff00 broadcast 171.56.42.255

# ifconfig lan1
lan1: flags=843
inet 171.56.42.56 netmask ffffff00 broadcast 171.56.42.56

# ifconfig lan2
lan2: flags=842
inet 0.0.0.0 netmask 0

# cmviewcl -v -n node1

Network_Parameters:
INTERFACE STATUS PATH NAME
PRIMARY up 10/4/8 lan0
PRIMARY up 10/4/16 lan1
STANDBY up 10/12/6 lan2

Hope this helps.

regds