- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- cluster issue
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
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
Community
Resources
Forums
Blogs
- 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
04-28-2017 06:48 AM
04-28-2017 06:48 AM
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-29-2017 10:11 AM
04-29-2017 10:11 AM
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?