- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Server Management (Insight Manager 7)
- >
- Cluster nodes Problems
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
04-21-2003 11:46 PM
04-21-2003 11:46 PM
Cluster nodes Problems
We have 2 Win2K Clusters named GDBO01CLST1 and GDBO01CLST2.
CLST1's nodes are GDBO01CLN1 and GDBO01CLN2
CLST2's nodes are GDBO01CLN3 and GDBO01CLN4
- The first problem is that only nodes CLN1 and CLN3 have been added to the devices list, cln2 and cln4 have been not even if they are configured exactly the same.
- The second problem is the clusters are not correctly identified. In fact a "cluster" gdbo01cln3 is being reported while it should have been gdbo01clst2
Here after a message from the devices status panel which is incorrect because states that gdbo01cln4 is a member of cluster gdbo01cln3
DISK CMX: at 11-Apr-2003, 15:50:56 CEST device status on node gdbo01cln4 of cluster gdbo01cln3 became critical
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-23-2003 01:54 AM
04-23-2003 01:54 AM
Re: Cluster nodes Problems
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-23-2003 02:21 AM
04-23-2003 02:21 AM
Re: Cluster nodes Problems
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-23-2003 02:58 AM
04-23-2003 02:58 AM
Re: Cluster nodes Problems
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-24-2003 06:01 PM
04-24-2003 06:01 PM
Re: Cluster nodes Problems
Another thing to check is how you discovered the devices. If you used Auto-Discovery, did you discover all the node IPs AND the virtual IPs? If you manually added the devices, again, make sure you have added all the nodes and the virtual nodes.
If manually adding devices, be sure and run the Daily Identification Task to make sure they get identified correctly.
I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
