MC/SG package.ascii order

[Robert Gamble]

Does the order of the network configuration lines in cmclconf.ascii matter ?
For example:

NODE_NAME sys1
NETWORK_INTERFACE lan5
HEARTBEAT_IP 148.98.150.197
NETWORK_INTERFACE lan7
NETWORK_INTERFACE lan0
HEARTBEAT_IP 10.16.3.2
NETWORK_INTERFACE lan6
NODE_NAME sys2
NETWORK_INTERFACE lan5
HEARTBEAT_IP 148.98.150.196
NETWORK_INTERFACE lan0
HEARTBEAT_IP 10.16.3.1
NETWORK_INTERFACE lan7
NETWORK_INTERFACE lan6

On both systems, the primary NIC is lan5, and lan0 is primary for heartbeat.
Should we be concerned that on the second NODE_NAME, that the NETWORK_INTERFACE's are not in order ? Each lan card is configured correctly in the /etc/rc.config.d/netconf file. The systems have been in production for well over a year, but someone just noticed the order contained in the file. Is this something we need to worry about ? We have not tested lan5 to lan7 failover since it went into production...

[G. Vrijhoeven]

Hi Robbert,

You should be able to test if the network interfaces are able to switch. this can be done with the cmquerycl -v -c clustername -l net -C /tmp/network.asci

Hope this will help,

Gideon

[Christopher McCray_1]

I agree. Robert, run the above cmquerycl command above and look at the temp file to see the order Service Guard puts them in. I suspect that maybe the order was due to all lan cards were not able to be polled when It was first configured, and they were added manually during the process. You could test your failover capability on some quiet weekend. Just pull the cable out of lan5 ....

It is better to find out now rather than when you need it.


Good luck and hope this helps.

Chris

[Robert Gamble]

Thank you for your responses.
Unfortunately, the cmquerycl command only cats the ascii file, it does not actually verify the proper order ...

[Christopher McCray_1]

You may want to take a look at the man pages for cmquerycl, but just as a quick explanation, the command "rattles the cages" of all nodes in the cluster and creates a cluster.ascii file for editing and eventually creating the cluster binary. However, you can still test the failover capability of your lan interface(s) by merely pulling the cable out of the back of the card and after the NETWORK_POLLING_INTERVAL has been reached (default= 2 sec.) the standby lan for lan5 should then be configured by service guard with lan5's information.

You can modify the command previously given by running cmquerycl -C /tmp/temp.ascii -n sys1 -n sys2 and look at what sserviceguard gives as output.

I hope this helps
Chris

[Christopher McCray_1]

Another thought, could you please post the output of netstat -i?? Probably fine; just covering all basis. Thanks

Chris

[Robert Gamble]

the netstat -i command returns everything as expected (to me):
Name Mtu Network Address Ipkts Opkts
lan5:1 1500 148.98.150.192 pon1nfs1 605680243 52285340
lan0 1500 arpanet ptponfhb 1403276 719978
lo0 4136 loopback localhost 1697067 1697070
lan7* 1500 dummy_entry dummy_entry 0 0
lan6* 1500 dummy_entry dummy_entry 0 0
lan5 1500 148.98.150.192 pnpthia1 102062579 874320130

The cmquerycl command will return unique things that are commented out in the ascii file, which is how I determined the statement from my last post.

I emailed a friend who is an HP Instructor who does teach the MC/SG class, who replied that the order does not matter 99.9% of all configurations, including mine.

Thank you for your responses.

[Christopher McCray_1 · Accepted solution]

I agree totally with your instructor friend as I, too have attended both MCSG classes. I apologize if my answers weren't hitting the mark; I was under the impression that you were more worried about whether or not lan7 would pick up the slack in the event of lan5 failing, which I thought I had answered. In any event, I wish you good luck and success and I hope to be of more help to you in the future.

Regards,

Chris

[Helen French]

hey,

In my setup (which is a production server), it works fine evenif the network configuration lines are not in order !

Shiju

[Sanjay_6]

Hi Robert,

The order of the netowrk lan configuration in the cluster ascii configuration file does not make any difference.

Hope this helps.

Regds