HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Service Guard Node in unknown state
Operating System - HP-UX
1827811
Members
1956
Online
109969
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-09-2010 06:37 AM
12-09-2010 06:37 AM
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
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-09-2010 08:06 AM
12-09-2010 08:06 AM
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...
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..
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-10-2010 02:02 PM
12-10-2010 02:02 PM
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-13-2010 06:20 AM
12-13-2010 06:20 AM
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).
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP