Operating System - HP-UX
1752339 Members
5509 Online
108787 Solutions
New Discussion юеВ

Re: cmmodnet || SG A.11.18.00

 
boomerang
Frequent Advisor

cmmodnet || SG A.11.18.00

Hello Admins,

Model : ia64 hp server rx6600

Service Guard A.11.18.00 running in HPUX 11.23

We have lan2(PRIMARY) and lan3(STANDBY) configured as HEARTBEAT_IP .

Recently it switched automaticaly from lan2 to lan3(reason need to be checked)

Can I switch back to lan2(PRIMARY) with the below command ?

тАЬcmmodnet тАУe lan2тАЭ can this command be run with cluster and packages up?

What will be the impact if command is executed online(cluster and package up) in the SG version we are having ?

Please suggest
2 REPLIES 2
boomerang
Frequent Advisor

Re: cmmodnet || SG A.11.18.00

#cmviewcl -v

CLUSTER STATUS
yokDB up

NODE STATUS STATE
yokp01 up running

Cluster_Lock_LVM:
VOLUME_GROUP PHYSICAL_VOLUME STATUS
/dev/vg02 /dev/dsk/c4t5d6 up

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

PACKAGE STATUS STATE AUTO_RUN NODE
pkg1 up running disabled yokp01

Policy_Parameters:
POLICY_NAME CONFIGURED_VALUE
Failover configured_node
Failback manual

Script_Parameters:
ITEM STATUS MAX_RESTARTS RESTARTS NAME
Subnet up 10.248.8.0

Node_Switching_Parameters:
NODE_TYPE STATUS SWITCHING NAME
Primary up enabled yokp01 (current)
Alternate down yokp02

NODE STATUS STATE
yokp02 down halted

Cluster_Lock_LVM:
VOLUME_GROUP PHYSICAL_VOLUME STATUS
/dev/vg02 /dev/dsk/c4t5d6 unknown

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


Currently second node has been removed from cluster for patching

Please suggest

Re: cmmodnet || SG A.11.18.00

>> Recently it switched automaticaly from lan2 to lan3(reason need to be checked)


Well it looks like lan2 is still not functioning, otherwise the cluster would detect it and move back... So you need to fix the network problem, then Serviceguard should sort itself out...

HTH

Duncan

I am an HPE Employee
Accept or Kudo