- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- SGLX problem on SLES10, when one node reboot
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
тАО05-17-2008 09:02 AM
тАО05-17-2008 09:02 AM
The NFS service on it can switch to the backup host manually or by command cmhaltnode.
But when the serving node reboot, all two hosts are down. The cluster status and error logs are in the attachment.
I've tried the SGLX A.11.16 on RHEL4 before, no such problem. Can anyone help to tell why it occures on SGLX A.11.18 SLES10 SP1. Thanks.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-17-2008 02:52 PM
тАО05-17-2008 02:52 PM
Re: SGLX problem on SLES10, when one node reboot
So, has this ever worked? Is this the first time you've rebooted the nodes since you put SG on there? Have you presented more LUNs to this system since the day you installed it? If you have, have you set up persistent binding on the LUNs?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-17-2008 06:55 PM
тАО05-17-2008 06:55 PM
Re: SGLX problem on SLES10, when one node reboot
I have several LUNs mapped to the hosts. I've tried with other partitions as the Lock LUN. The problem also exits.
Since the same lun have the same name on my two hosts every time they booted. So I suppose it's not the persistent binding problem.
Are there any possibility when the serving node rebooting, the Ethernet down first, so the heartbeat down. Then two nodes begin to contend for the Lock LUN. Sometimes, the serving node get the Lock LUN before it really shutdown.
If so, are there any configuration to be edited to postpone the node down detection time when the heartbeat down, or any parameter to let the backup node to try to obtain the lock LUN more times? Thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-18-2008 12:14 AM
тАО05-18-2008 12:14 AM
SolutionYes - look in your cmclconf.ascii file for the line containing the phrase 'Cluster Timing Parameters'. This is the section that deals with the HEARTBEAT_INTERVAL and NODE_TIMEOUT parameters.
This file sits in $SGCONF (which in our case /opt/cmcluster/conf).
Colin.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-18-2008 05:28 PM
тАО05-18-2008 05:28 PM