Secondary IP for lan0 in a Service Guard cluster

[Lissete Calderón]

Hi team,
How can I add redundancy to the lan0 of everyone of my cluster nodes, that are already cinfugured and running?

I pluged the lan cord to a lan3 in each node and then changed the tag STATIONRY_IP in the /etc/cmcluster/cluster.config file, check conf and cmapplyconf.
BEFORE
NODE_NAME gemota1
NETWORK_INTERFACE lan0
HEARTBEAT_IP 10.100.191.25
NETWORK_INTERFACE lan1
HEARTBEAT_IP 192.1.1.1
NETWORK_INTERFACE lan5
STATIONARY_IP 192.1.2.1
FIRST_CLUSTER_LOCK_PV /dev/dsk/c12t0d1
# List of serial device file names
# For example:
# SERIAL_DEVICE_FILE /dev/tty0p0

# Warning: There are no standby network interfaces for lan0.
# Warning: There are no standby network interfaces for lan1.
# Warning: There are no standby network interfaces for lan5.

NODE_NAME gemota2
NETWORK_INTERFACE lan0
HEARTBEAT_IP 10.100.191.26
NETWORK_INTERFACE lan1
HEARTBEAT_IP 192.1.1.2
NETWORK_INTERFACE lan2
STATIONARY_IP 192.1.2.2
FIRST_CLUSTER_LOCK_PV /dev/dsk/c12t0d1

AFTER

NODE_NAME gemota1
NETWORK_INTERFACE lan0
STATIONARY_IP 10.100.191.25
NETWORK_INTERFACE lan1
HEARTBEAT_IP 192.1.1.1
NETWORK_INTERFACE lan5
STATIONARY_IP 192.1.2.1
FIRST_CLUSTER_LOCK_PV /dev/dsk/c12t0d1
# List of serial device file names
# For example:
# SERIAL_DEVICE_FILE /dev/tty0p0

# Warning: There are no standby network interfaces for lan0.
# Warning: There are no standby network interfaces for lan1.
# Warning: There are no standby network interfaces for lan5.

NODE_NAME gemota2
NETWORK_INTERFACE lan0
STATIONARY_IP 10.100.191.26
NETWORK_INTERFACE lan1
HEARTBEAT_IP 192.1.1.2
NETWORK_INTERFACE lan2
STATIONARY_IP 192.1.2.2
FIRST_CLUSTER_LOCK_PV /dev/dsk/c12t0d1

I made a lan failover test, but it did not work.

I had read that I don't need to assign an IP for the new lan3 , but I am not sure if I need to activate it in every node?

Any idea?

Thanks in advance

[Sanjay_6]

Hi,

Once you have plugged a cable on lan3 to your switch port, you need to run cmquerycl once again to get the new ascii conf file.

also make sure the cable on lan3 is going to the same vlan as lan0 if you have vlan configured.

hope this helps.

regds

[Jeff Schussele · Accepted solution]

Hi Lissette,

You define a failover NIC by following a NETWORK_INTERFACE / STATIONARY_IP with a NETWORK_INTERFACE *without* an IP assignment.
For example

NETWORK_INTERFACE lan0
STAIONARY_IP 111.222.111.222
NETWORK_INTERFACE lan5
NETWORK_INTERFACE lan2
STATIONARY_IP 222.111.222.111

In this case lan5 would be the failover for lan0 & would assert the 111.222.111.222 IP in the event that lan0 lost connection for any reason.

HTH,
Jeff

[Jeff Schussele]

And I should add that lan3, of course, must be cabled to a switch (NOT the same switch as lan0) port that is VLAN'd for the same subnet that lan0 is in.
You simply test by pulling the lan0 cable & check that netstat -in now shows the IP on lan3.
After you reattach the cable to lan0 the system will wait about 30 seconds to bring the IP back to lan0 - the primary NIC. It waits so that IF there's an intermittent network problem causing that port to go up & down rapidly the IP won't be "ping-ponging" between the two NICs.

HTH,
Jeff

[Kent Ostby]

Sanjay -- What Jeff said should work except I think you said "lan3" and his example used "lan5."

Check out this document as well: UMCSGKBRC00009727

http://www1.itrc.hp.com/service/cki/search.do?category=c0&prevQueryString=&mode=id&searchString=UMCSGKBRC00009727&searchCrit=allwords&docType=EngineerNotes&dateRange=all&search.x=24&search.y=6

[Lissete Calderón]

Hi Jeff,

I just did what you suggested,and everything worked fine, the lan failover test was OK.

Thank a lot to you and the team as well.

[Lissete Calderón]

Now, It looks like this:

more /etc/cmcluster/cluster.config

NODE_NAME gemota1
NETWORK_INTERFACE lan0
STATIONARY_IP 10.100.191.25
NETWORK_INTERFACE lan2
NETWORK_INTERFACE lan1
HEARTBEAT_IP 192.1.1.1
NETWORK_INTERFACE lan5
STATIONARY_IP 192.1.2.1
FIRST_CLUSTER_LOCK_PV /dev/dsk/c12t0d1


NODE_NAME gemota2
NETWORK_INTERFACE lan0
STATIONARY_IP 10.100.191.26
NETWORK_INTERFACE lan3
NETWORK_INTERFACE lan1
HEARTBEAT_IP 192.1.1.2
NETWORK_INTERFACE lan2
STATIONARY_IP 192.1.2.2
FIRST_CLUSTER_LOCK_PV /dev/dsk/c12t0d1


And the cmviewcl -v :

CLUSTER STATUS
clusterota up

NODE STATUS STATE
gemota1 up running

Network_Parameters:
INTERFACE STATUS PATH NAME
PRIMARY up 0/1/2/0 lan0
PRIMARY up 0/3/1/0/4/0 lan1
PRIMARY up 0/4/1/0/4/0 lan5
STANDBY up 0/3/1/0/4/1 lan3



NODE STATUS STATE
gemota2 up running

Network_Parameters:
INTERFACE STATUS PATH NAME
STANDBY up 0/3/1/0/6/0 lan3
PRIMARY up 0/1/2/0 lan0
PRIMARY up 0/3/1/0/4/0 lan1
PRIMARY up 0/3/1/0/4/1 lan2