Serviceguard
cancel
Showing results for 
Search instead for 
Did you mean: 

Not able to fail back from standby lan:

 
V.P
Frequent Advisor

Not able to fail back from standby lan:

Dear Admins,
HP-UX 11.23 , SG-11.18 & 2 node cluster
We have observed that the primary lan his down and up in standby lan.
ActiveNode:
Network_Parameters:
INTERFACE STATUS PATH NAME
PRIMARY up 0/3/1/0/6/0 lan0
PRIMARY down 0/4/2/1 lan2
STANDBY down 0/4/2/0 lan1
STANDBY up 0/6/1/0/6/0 lan3

How can we failback to lan2. Cmmodnet is not working.

ActiveNode:/paradmin>cmmodnet -v -e lan2
cmmodnet: Network interface lan2 has already been in this state.

We have removed the passsive node from cluster for patching.Now if we try to join the passive node to cluster it is giving error as:

PassiveNode:/paradmin>cmrunnode -v PassiveNode
cmrunnode: Validating network configuration...
Gathering network information
Network interface lan2 on node ActiveNode does not have an IP address,
But the configuration file specified 10.11.4.152.
This may be caused by changes in the network configuration,
Or by a local switch.
IP subnets don't match, interface lan2 on ActiveNode
IP netmasks don't match, interface lan2 on ActiveNode
Interface lan3 on ActiveNode has an IP address on it
(10.11.4.152), but the configuration file doesn't have it.
This may be caused by a local switch or changes in the network configuration.
Beginning network probing (this may take a while)
Completed network probing
lan2 on node ActiveNode cannot be configured in the cluster
because it does not have an IP address, and it is not a standby lan for any other lan.
Failed to evaluate network
cmrunnode: Failed to validate the network configuration as reported above but will try to start the nodes anyway.
cmrunnode: Network validation complete
cmrunnode: Validating cluster lock disk .... Done
Waiting for nodes to join ................... timed out
Check the syslog files for information.
cmrunnode failed: timed out waiting for cluster to form

How can we solve this issue.

Regards,
V.P
3 REPLIES 3
melvyn burnard
Honored Contributor

Re: Not able to fail back from standby lan:

well it is fairly obvious there is an issue with your networks.
You need to investigate why they ar edown, by checking cbles, switch ports etc.
Also look at using linkloop or even use cmscanl to get some information out to review

Network interface lan2 on node ActiveNode does not have an IP address,
But the configuration file specified 10.11.4.152.
This may be caused by changes in the network configuration,
Or by a local switch.
IP subnets don't match, interface lan2 on ActiveNode
IP netmasks don't match, interface lan2 on ActiveNode
Interface lan3 on ActiveNode has an IP address on it
(10.11.4.152), but the configuration file doesn't have it.
This may be caused by a local switch or changes in the network configuration.
Beginning network probing (this may take a while)
Completed network probing
lan2 on node ActiveNode cannot be configured in the cluster
because it does not have an IP address, and it is not a standby lan for any other lan.
My house is the bank's, my money the wife's, But my opinions belong to me, not HP!
Joe Eaton
Occasional Contributor

Re: Not able to fail back from standby lan:

I am experiencing this same issue.  Did you find the root cause of yours ?

db
Stephen Doud
Honored Contributor

Re: Not able to fail back from standby lan:

I agree with Melvyn - Use either cmviewconf (older SG) or  'cmviewcl -v -f line | grep -e name=lan -e bridged' to identify which networks Serviceguard expects to be bridged between NICs and test LAN connectivity and communication ability against what Serviceguard expects.  Insure all bridged networks pass 'linkloop -i <ppa> <MAC>' tests. 

 

If you believe all networks are bridged and IP'd as expected, consider resetting the primary NIC:

$ landiag

lan

(change to a different PPA if needed)

reset

quit

$

 

Then use lanscan to verify H/W state is UP for the NIC and check whether Serviceguard discovered that the NIC is now usable (and moved the IPs back to it).