Operating System - HP-UX
1827811 Members
1956 Online
109969 Solutions
New Discussion

Service Guard Node in unknown state

 
ArunKC
Occasional Contributor

Service Guard Node in unknown state

Hi Guys,

We have one two node cluster running with 11.31 OS & 11.18 , when I ran cmviewcl -v from one of node its giving quarum server & other node/lan card in unknow state but when I ran cmviewcl from other node its giving correct O/P.

Linkloop is working fine.
CLUSTER STATUS
Cluster1 up

NODE STATUS STATE
ServerA up running

Quorum_Server_Status:
NAME STATUS STATE
Quorumserver1 up running

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

PACKAGE STATUS STATE AUTO_RUN NODE
pkg1 up running enabled ServerA

Policy_Parameters:
POLICY_NAME CONFIGURED_VALUE
Failover configured_node
Failback manual

Script_Parameters:
ITEM STATUS MAX_RESTARTS RESTARTS NAME
Service unknown 0 0 pkg1_service
Service up 0 0 pkg1_oramon
Service up 50 7 pkg1_lsnmon
Service unknown 0 0 adnnm_service

Node_Switching_Parameters:
NODE_TYPE STATUS SWITCHING NAME
Primary up enabled ServerA (current)
Alternate unknown ServerB

NODE STATUS STATE
ServerB up running

Quorum_Server_Status:
NAME STATUS STATE
Quorumserver1 unknown unknown

Network_Parameters:
INTERFACE STATUS PATH NAME
PRIMARY unknown 0/1/1/0 lan0
PRIMARY unknown 0/2/2/0 lan2
STANDBY unknown 0/2/2/1 lan3
3 REPLIES 3
Uday_S_Ankolekar
Honored Contributor

Re: Service Guard Node in unknown state

Are you able to communicate from Node B to Quorum server? Check the syslog if you see any errors.

Also check from Quorum server has names of node B mentioned correctly. You run qs_update from quorum server to restart the qs process

USA...
Good Luck..
ArunKC
Occasional Contributor

Re: Service Guard Node in unknown state

Thanks for the response, issue has been resolved - Issue was with /etc/hosts entry on the second server that doesnt have FQDN of server A
Stephen Doud
Honored Contributor

Re: Service Guard Node in unknown state

It has to be more than a missing FQDN in /etc/hosts (I cannot duplicate the error with only that discrepancy).