- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: LockManager instalation
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
Forums
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
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
01-07-2002 09:58 AM
01-07-2002 09:58 AM
LockManager instalation
After install MC/ServiceGuard OPS Edition (LockManager 10.07) on a K580, running 10.20, I run the command "cmquerycl -v" and receive the following message:
Begin checking the nodes...
All nodes within the cluster will be checked.
.cmquerycl : Unable to obtain information for: .
Connection timed out.
Anyone to help?
Regards,
Simone Bardolla
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-07-2002 10:11 AM
01-07-2002 10:11 AM
Re: LockManager instalation
Check if you have this patch installed..
Patch Name: PHSS_25124
Patch Description: s700_800 11.X MC/ServiceGuard and SG-OPS Edition A.11.13
Also have a look at this doc..
http://us-support.external.hp.com/cki/bin/doc.pl/sid=96a88bd9057c1a0c5e/screen=ckiDisplayDocument?docId=200000058095130
Goodluck,
-USA..
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-07-2002 10:18 AM
01-07-2002 10:18 AM
Re: LockManager instalation
Have you created .rhosts / cmnodelist file .
sachin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-07-2002 10:23 AM
01-07-2002 10:23 AM
Re: LockManager instalation
Did you mention the node names in the cmquerycl command. The correct syntax is "cmquerycl -v -n node_name1 -n node_name2...."
hope this helps.
Regds
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-07-2002 10:24 AM
01-07-2002 10:24 AM
Re: LockManager instalation
I check .rhosts and hosts.equiv and apply lastest patches but no success to run cmquerycl -v or any other option of this command.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-07-2002 10:31 AM
01-07-2002 10:31 AM
Re: LockManager instalation
# cmquerycl -v -n jacarta -n ankara
Begin checking the nodes...
cmquerycl : Unable to obtain information for: .
Connection timed out.
And the /.rhosts have the all hosts (jacarta and ankara).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-07-2002 10:40 AM
01-07-2002 10:40 AM
Re: LockManager instalation
Are your two system able to resolve the name and ip address for themselves and the other node correctly. Do a nslookup and check for the hostname resolution,
nslookup
> node_name1
> node_ip_1
> node_name2
> node_ip_2
> exit
Do this on both the nodes and make sure the hostname and ip's are resolved correctly for both the nodes or all the nodes if you have more than two nodes in the cluster.
Hope this helps.
Regds
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-07-2002 10:48 AM
01-07-2002 10:48 AM