- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- cmcheckconf error node2 unreachble
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
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
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-10-2005 10:41 AM
тАО01-10-2005 10:41 AM
cmcheckconf error node2 unreachble
after setting up the fine cmclconf.ascii
cmcheckconf -v -C cmclconf.ascii is with no error and I aplly it.
The cluster is configure and is good.
After that I make a change in the file adding a new lan interface
and I check the file there is an error to join the node2
That error still even if I correct the file cmclconf.ascii.
So I can any more configure the package bu the cluster still beeing good.
what are the requirement to modifie the file cmclconf.ascii?
Thank you for your help.
KSF
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-10-2005 01:57 PM
тАО01-10-2005 01:57 PM
Re: cmcheckconf error node2 unreachble
Procedure to modify cluster:
http://docs.hp.com/en/B3936-90079/index.html
cmquerycl -v -C /etc/cmcluster/newcmclconf.ascii -n node1 -n node2
That will generate a new ascii file...you should see errors with the new lan card...
Rgds...Geoff
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-10-2005 04:10 PM
тАО01-10-2005 04:10 PM
Re: cmcheckconf error node2 unreachble
(http:/docs.hp.com/en/B3936-90065/)
It is Correct !
Hope this help
tienna
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-10-2005 09:40 PM
тАО01-10-2005 09:40 PM
Re: cmcheckconf error node2 unreachble
You also need to ensure that you have ALL network ip addresses/hostnames in your hosts file and DNS if using DNS.
If all else fails, remove the binary using cmdeleteconf and start again, at which time cmclnodelist is used to create the initial binary file.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-11-2005 02:51 AM
тАО01-11-2005 02:51 AM
Re: cmcheckconf error node2 unreachble
If I want to verify whether Serviceguard can see the LAN interface, and how it sees it, I create a new cluster.ascii using cmquerycl and inspect the way that Serviceguard lists the new LAN interface - and transfer that statement to my cluster configuration file.
TIP: look at the comments at the bottom of each servers' description section in the cluster configuration file. Serviceguard actually lists whether LANs that it finds are potential standby LANs and which networks it locates them on.
Example:
# Primary Network Interfaces on Bridged Net 1: lan2.
# Warning: There are no standby network interfaces on bridged net 1.
Also, try 'linkloop' to verify that a newly attached LAN is reachable by the other node.