HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Boot from San + Serviceguard Issue
Operating System - HP-UX
1833753
Members
2509
Online
110063
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
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
11-19-2007 06:58 PM
11-19-2007 06:58 PM
Hello.
We installed for a customer 2 systems, 11i V3
on Rx3600 + Boot from SAN + serviceguard 1.18
The issue is testing the cluster. all tests goes well , but disconnect the two fiber HBA from one system didnt cause the package to failover to the other system. We Create An EMS lv_summery resource , which was defined in our Cluster package , but still its seems that when the system disk is disconnected from the machine , nothing happen.
One way to solve the problem is to make mirror lvm of the system disk to a local sas disk.
But if someone have another IDEA how to get the system to reboot in case of such a case , i will appreciate
Regards
klemer Shalom.
We installed for a customer 2 systems, 11i V3
on Rx3600 + Boot from SAN + serviceguard 1.18
The issue is testing the cluster. all tests goes well , but disconnect the two fiber HBA from one system didnt cause the package to failover to the other system. We Create An EMS lv_summery resource , which was defined in our Cluster package , but still its seems that when the system disk is disconnected from the machine , nothing happen.
One way to solve the problem is to make mirror lvm of the system disk to a local sas disk.
But if someone have another IDEA how to get the system to reboot in case of such a case , i will appreciate
Regards
klemer Shalom.
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-19-2007 07:17 PM
11-19-2007 07:17 PM
Solution
Interesting issue - can you post the relevant configuration settings from your package configuration (how you define lv_summary as a resource dependency). I would usually set up a PVG for my VG in /etc/lvmpvg and use pv_summary rather than lv_summary
However I think there's a possibility you may be stuck here - normally in this situation I'd tell you to pull the fibres and then check the status of the EMS resource using the resls command. But of course in your scenario you won't be able to call the resls command as the system won't be able to page the executable in from disk... I wonder if Serviceguard suffers the same issue? If so, you may have no choice but to use those local disks...
You so know that when doing this kind of thing you have to have the NODE_FAIL_FAST_ENABLED set to true? As Serviceguard has no way of sensibly unmounting the hung filesystems, the only way to close down is to TOC the system.
If you have a support contract, you can look at the ITRC document UMCSGKBRC00012483 for a full example:
http://www4.itrc.hp.com/service/cki/docDisplay.do?docLocale=en&docId=emr_na-c01028614-3
HTH
Duncan
I am an HPE Employee
However I think there's a possibility you may be stuck here - normally in this situation I'd tell you to pull the fibres and then check the status of the EMS resource using the resls command. But of course in your scenario you won't be able to call the resls command as the system won't be able to page the executable in from disk... I wonder if Serviceguard suffers the same issue? If so, you may have no choice but to use those local disks...
You so know that when doing this kind of thing you have to have the NODE_FAIL_FAST_ENABLED set to true? As Serviceguard has no way of sensibly unmounting the hung filesystems, the only way to close down is to TOC the system.
If you have a support contract, you can look at the ITRC document UMCSGKBRC00012483 for a full example:
http://www4.itrc.hp.com/service/cki/docDisplay.do?docLocale=en&docId=emr_na-c01028614-3
HTH
Duncan
I am an HPE Employee

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-19-2007 07:48 PM
11-19-2007 07:48 PM
Re: Boot from San + Serviceguard Issue
n.
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