- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Re: Regarding lockLUN
Operating System - Linux
1753511
Members
5005
Online
108795
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
Discussions
Discussions
Forums
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
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
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
тАО05-23-2007 11:26 PM
тАО05-23-2007 11:26 PM
Hello,
I would like to know regarding lockLUN
[ENVIRONMENT]
RHEL AS 4 up4
Serviceguard 11.16.10
[QUESTION]
There are two cluster member as Serviceguard for Linux.
When a package failover from host-A to host-B, is there possibility to appear like following
by using cmviewcl command ?
Host-A -----> "unknown"
Host-B -----> "UP"
Thank you for advice.
Best Regards.
/Minoru.Asano
I would like to know regarding lockLUN
[ENVIRONMENT]
RHEL AS 4 up4
Serviceguard 11.16.10
[QUESTION]
There are two cluster member as Serviceguard for Linux.
When a package failover from host-A to host-B, is there possibility to appear like following
by using cmviewcl command ?
Host-A -----> "unknown"
Host-B -----> "UP"
Thank you for advice.
Best Regards.
/Minoru.Asano
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-24-2007 06:34 AM
тАО05-24-2007 06:34 AM
Solution
Yes, it's possible.
It means Host-A does not respond at all, so Host-B does not know if Host-A is crashed or just lost all the ways to communicate with Host-B.
You'll have to inspect Host-A to see what's going on.
If it's running, check "uptime": it should have rebooted itself right after losing network connections to Host-B. Obviously Host-B managed to access the lockLUN first, and Host-A rebooted to avoid the split-brain situation. As cmviewcl (on host-B I think) is reporting host-A as unknown, there may be a network problem preventing host-B from getting information about host-A.
After the network problem is fixed, cmviewcl on host-B should be able to say with confidence that host-A is "down". To make it re-join the cluster, run "cmrunnode host-A"
or reboot host-A.
If host-A is not running, find out why and fix it (Overheating? Loss of power? Hardware failure?). If there are no network problems and /usr/local/cmcluster/cmcluster.rc has the default value, it should automatically re-join the cluster when it reboots. If not, "cmrunnode host-A" is the command to make it re-join the cluster manually.
MK
It means Host-A does not respond at all, so Host-B does not know if Host-A is crashed or just lost all the ways to communicate with Host-B.
You'll have to inspect Host-A to see what's going on.
If it's running, check "uptime": it should have rebooted itself right after losing network connections to Host-B. Obviously Host-B managed to access the lockLUN first, and Host-A rebooted to avoid the split-brain situation. As cmviewcl (on host-B I think) is reporting host-A as unknown, there may be a network problem preventing host-B from getting information about host-A.
After the network problem is fixed, cmviewcl on host-B should be able to say with confidence that host-A is "down". To make it re-join the cluster, run "cmrunnode host-A"
or reboot host-A.
If host-A is not running, find out why and fix it (Overheating? Loss of power? Hardware failure?). If there are no network problems and /usr/local/cmcluster/cmcluster.rc has the default value, it should automatically re-join the cluster when it reboots. If not, "cmrunnode host-A" is the command to make it re-join the cluster manually.
MK
MK
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-24-2007 06:47 AM
тАО05-24-2007 06:47 AM
Re: Regarding lockLUN
Shalom,
If you wish, explain the subject of the post versus the question.
Host A is not accessible. Common cause is inconsistent /etc/hosts networking. If you are not using that (see /etc/nsswitch.conf) then it could be DNS.
Start with ping and make sure the nodes recognize each other.
SEP
If you wish, explain the subject of the post versus the question.
Host A is not accessible. Common cause is inconsistent /etc/hosts networking. If you are not using that (see /etc/nsswitch.conf) then it could be DNS.
Start with ping and make sure the nodes recognize each other.
SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
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.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP