HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: cluster issue
Operating System - HP-UX
1833491
Members
3118
Online
110052
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
04-01-2011 10:36 AM
04-01-2011 10:36 AM
cluster issue
Hi Admin,
B.11.23
We have 2 node act-passive cluster.To deploy the patch we halted passive node from the cluster.Now we are not able to join the node back.
Below are the error details.
uaedxbpdctakp02:/etc/cmcluster>cmrunnode -v uaedxbpdctakp02
cmrunnode: Validating network configuration...
Gathering network information
Network interface lan2 on node uaedxbpdctakp01 does not have an IP address,
but the configuration file specified 10.11.4.152.
This may be caused by changes in the network configuration,
or by a local switch.
IP subnets don't match, interface lan2 on uaedxbpdctakp01
IP netmasks don't match, interface lan2 on uaedxbpdctakp01
Interface lan3 on uaedxbpdctakp01 has an IP address on it
(10.11.4.152), but the configuration file doesn't have it.
This may be caused by a local switch or changes in the network configuration.
Beginning network probing (this may take a while)
Completed network probing
lan2 on node uaedxbpdctakp01 cannot be configured in the cluster
because it does not have an IP address, and it is not a standby lan for any other lan.
Failed to evaluate network
cmrunnode: Failed to validate the network configuration as reported above but will try to start the nodes anyway.
cmrunnode: Network validation complete
cmrunnode: Validating cluster lock disk .... Done
cmrunnode: Cluster is already running on "uaedxbpdctakp02".
From error details we can make out that lan failover happenb between lan2 and lan3 in active node.
Below are the lan details of active node
NODE_NAME uaedxbpdctakp01
NETWORK_INTERFACE lan0
STATIONARY_IP 10.248.8.10
NETWORK_INTERFACE lan2
HEARTBEAT_IP 10.11.4.152
NETWORK_INTERFACE lan1
NETWORK_INTERFACE lan3
Package is running fine in active node.
can i move the ip back to lan2 when package is active..
And one more option,can i modify the lan details in cluster file according to current
situation when cluster/pkg is running..
Please guide me ..
Regards
himacs
B.11.23
We have 2 node act-passive cluster.To deploy the patch we halted passive node from the cluster.Now we are not able to join the node back.
Below are the error details.
uaedxbpdctakp02:/etc/cmcluster>cmrunnode -v uaedxbpdctakp02
cmrunnode: Validating network configuration...
Gathering network information
Network interface lan2 on node uaedxbpdctakp01 does not have an IP address,
but the configuration file specified 10.11.4.152.
This may be caused by changes in the network configuration,
or by a local switch.
IP subnets don't match, interface lan2 on uaedxbpdctakp01
IP netmasks don't match, interface lan2 on uaedxbpdctakp01
Interface lan3 on uaedxbpdctakp01 has an IP address on it
(10.11.4.152), but the configuration file doesn't have it.
This may be caused by a local switch or changes in the network configuration.
Beginning network probing (this may take a while)
Completed network probing
lan2 on node uaedxbpdctakp01 cannot be configured in the cluster
because it does not have an IP address, and it is not a standby lan for any other lan.
Failed to evaluate network
cmrunnode: Failed to validate the network configuration as reported above but will try to start the nodes anyway.
cmrunnode: Network validation complete
cmrunnode: Validating cluster lock disk .... Done
cmrunnode: Cluster is already running on "uaedxbpdctakp02".
From error details we can make out that lan failover happenb between lan2 and lan3 in active node.
Below are the lan details of active node
NODE_NAME uaedxbpdctakp01
NETWORK_INTERFACE lan0
STATIONARY_IP 10.248.8.10
NETWORK_INTERFACE lan2
HEARTBEAT_IP 10.11.4.152
NETWORK_INTERFACE lan1
NETWORK_INTERFACE lan3
Package is running fine in active node.
can i move the ip back to lan2 when package is active..
And one more option,can i modify the lan details in cluster file according to current
situation when cluster/pkg is running..
Please guide me ..
Regards
himacs
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-01-2011 07:29 PM
04-01-2011 07:29 PM
Re: cluster issue
Hi,
Provide below outputs,
cmviewcl -v
cat cluster configaration file
netstat -nvr
These outputs may help to find exact issue.
Chandra
Provide below outputs,
cmviewcl -v
cat cluster configaration file
netstat -nvr
These outputs may help to find exact issue.
Chandra
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-04-2011 04:30 AM
04-04-2011 04:30 AM
Re: cluster issue
Hi himacs,
> can i move the ip back to lan2 when package is active..
yes, you _should_ move back the ip to lan2 in order to attach the inactive node back.
>And one more option,can i modify the lan details in cluster file according to current
situation when cluster/pkg is running..
AFAIK for a cluster config modification all the nodes must be up an running. So I would rather find out why the IP was switched to the standby interface on the active node, and make it switch back.
Maybe the failure is already repaired, but the NETWORK_AUTO_FAILBACK parameter in your cluster config is set to false, and that's why it didn't fail back. See p.367 "Changing the Cluster Networking Configuration while the Cluster Is Running" in
http://h20000.www2.hp.com/bc/docs/support/SupportManual/c02437444/c02437444.pdf
> can i move the ip back to lan2 when package is active..
yes, you _should_ move back the ip to lan2 in order to attach the inactive node back.
>And one more option,can i modify the lan details in cluster file according to current
situation when cluster/pkg is running..
AFAIK for a cluster config modification all the nodes must be up an running. So I would rather find out why the IP was switched to the standby interface on the active node, and make it switch back.
Maybe the failure is already repaired, but the NETWORK_AUTO_FAILBACK parameter in your cluster config is set to false, and that's why it didn't fail back. See p.367 "Changing the Cluster Networking Configuration while the Cluster Is Running" in
http://h20000.www2.hp.com/bc/docs/support/SupportManual/c02437444/c02437444.pdf
****
Unix operates with beer.
Unix operates with beer.
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
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP