- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Interrogating the nodes on ServiceGuard
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
11-13-2009 09:19 AM
11-13-2009 09:19 AM
Interrogating the nodes on ServiceGuard
Currently we have scripts that use cmviewcl to ascertain which node the packages are currently running on.
Obviously in a 2-node cluster if one of the nodes is missing this command can take a while to respond.
Are there any other ways to ascertain the node that is running the packages without using cmviewcl?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-13-2009 09:21 AM
11-13-2009 09:21 AM
Re: Interrogating the nodes on ServiceGuard
:o)
Thanks in anticipation
Paul
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-13-2009 09:25 AM
11-13-2009 09:25 AM
Re: Interrogating the nodes on ServiceGuard
If so, perhaps a remsh
or uname -n ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-13-2009 10:12 AM
11-13-2009 10:12 AM
Re: Interrogating the nodes on ServiceGuard
You are using a work around to the preferred way of monitoring in MC/SG, adding monitoring scripts to check for processes up or down or hung or what.
Review the doc I've attached in particular
resource_name (299) *
resource_polling_interval
(299)
resource_start (299)
resource_up_value (299)
...which are used monitors critical
resources via the Event Monitoring Service
(EMS).
Review the logs in /etc/opt/resmon/log and become familiar with this application. EMS will report via snmp all MC/SG errors.
Review the node_fail_fast_enabled parameter.
Review dependency_name and dependency_condition which is dependency that must be met in order for this package to run (or keep running).
This means modifying your binaries so you'll need a test cluster to work on.
If you can't do this then explore 'cmgetconf' and 'cmscancl' commands. This are the man commands used in trouble shooting.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-18-2009 02:36 AM
11-18-2009 02:36 AM
Re: Interrogating the nodes on ServiceGuard
Apologies I am a little confused at the response - not the first time I hasten to add!
:o)
Are these configuration parameters able to explain which node is currently running the packages?
I am trying to avoid the 'cmviewcl' command as in a recent exercise we had to take one of the nodes out of the 2-node cluster. The result of which was that all of the scripts that checked to see which node was, if you like, acting as the master node hung for a period of time whilst 'cmviewcl -v' was awaiting a response.
Regards,
Paul
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-18-2009 02:43 AM
11-18-2009 02:43 AM
Re: Interrogating the nodes on ServiceGuard
There are built in monitoring templates that you fill in and use in lieu of scripts that parse cmviewcl, see attachement.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-11-2010 07:30 AM
02-11-2010 07:30 AM
Re: Interrogating the nodes on ServiceGuard
Thanks for the help, we've taken the approach of having a small logical volume as part of serviceguard
Our scripts will check for this to determins which node they are operating against.