cancel
Showing results for 
Search instead for 
Did you mean: 

cluster issue

 
kampatel
Occasional Advisor

cluster issue

Need to resolve the issue observed in the below cmviewcl output, the status of cmcl-lock ,PRIMARY interface are in unknown status , I have checked all the configuration file and the status of the interfaces and server which up and running fine . The cluster is currently up and running I need to resolve the issue observed. Kindly suggest what necessary steps should be taken to resolve the same.  The cmcheckconf command is also failing as it is not able to connect to secondary node. 

ash-4.3$ sudo cmviewcl -v


CLUSTER STATUS
cluster1 up

NODE STATUS STATE
server2 up running

Quorum_Server_Status:
NAME STATUS STATE ADDRESS
cmcl-lock unknown unknown 112.19.50.5

Network_Parameters:
INTERFACE STATUS PATH NAME
PRIMARY unknown LinkAgg0 lan900
PRIMARY unknown 0/6/1/0/6/0 lan3

NODE STATUS STATE
server1 up running

Quorum_Server_Status:
NAME STATUS STATE ADDRESS
cmcl-lock up running 112.19.50.5

Network_Parameters:
INTERFACE STATUS PATH NAME
PRIMARY up LinkAgg0 lan900
PRIMARY up 0/6/1/0/6/0 lan3

PACKAGE STATUS STATE AUTO_RUN NODE
package up running enabled server1

Policy_Parameters:
POLICY_NAME CONFIGURED_VALUE
Failover configured_node
Failback manual

Script_Parameters:
ITEM STATUS MAX_RESTARTS RESTARTS NAME
Subnet up 112.19.50.0

Node_Switching_Parameters:
NODE_TYPE STATUS SWITCHING NAME
Primary unknown server2
Alternate up enabled server1 (current)

Other_Attributes:
ATTRIBUTE_NAME ATTRIBUTE_VALUE
Style modular
Priority no_priority

 

 

 

1 REPLY 1
Patrick Wallek
Honored Contributor

Re: cluster issue

Is all of your networking OK on SERVER2?  It appears that SERVER2 cannot communicate with your  quorum server.  Your networks also both show as unknown status on SERVER2.

 

What dooes 'lanscan' show from SERVER2?  Anything in /var/adm/syslog/syslog.log regarding network issues?