HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Questions about pkg res monitoring
Operating System - HP-UX
1829951
Members
4001
Online
109998
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
03-09-2004 08:38 AM
03-09-2004 08:38 AM
It's strange to me that SG doesn't need a RESOURCE_TYPE attribute.
If the RESOURCE_NAME is just a full path name, according to what does cmstartres judge a resource to be up or down? An empty directory will be the same like an NFS umounted point. Which one is being checked?
If a user defines RESOURCE_UP_VALUE=UP, then that will be compared to what, to be true or not?
Could one package in the cluster be a dependent resource to another?
Jun
If the RESOURCE_NAME is just a full path name, according to what does cmstartres judge a resource to be up or down? An empty directory will be the same like an NFS umounted point. Which one is being checked?
If a user defines RESOURCE_UP_VALUE=UP, then that will be compared to what, to be true or not?
Could one package in the cluster be a dependent resource to another?
Jun
Food lover
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-09-2004 10:05 AM
03-09-2004 10:05 AM
Solution
Hi Jun,
RESOURCE definitions in ServiceGuard are more of EMS related. Man 'ems' for more information. You will need to add your monitors into EMS by using 'emscli' command and then use resls to get that info. For ex.,
emscli -a /storage/status/disks/default/10_0_15_0.5.0
Will add the monitoring request for the disk at the specified path.
resls -qs /storage/status/disks/default/10_0_15_0.5.0
Will display the status of the disk whether is up or down.
You can add the above request as a RESOURCE in your configuration file and specify the UP_VALUE as "UP". serviceguard will monitor this resource every "RESOURCE_POLLING_INTERVAL" and take action if it doesn't find it UP.
-Sri
RESOURCE definitions in ServiceGuard are more of EMS related. Man 'ems' for more information. You will need to add your monitors into EMS by using 'emscli' command and then use resls to get that info. For ex.,
emscli -a /storage/status/disks/default/10_0_15_0.5.0
Will add the monitoring request for the disk at the specified path.
resls -qs /storage/status/disks/default/10_0_15_0.5.0
Will display the status of the disk whether is up or down.
You can add the above request as a RESOURCE in your configuration file and specify the UP_VALUE as "UP". serviceguard will monitor this resource every "RESOURCE_POLLING_INTERVAL" and take action if it doesn't find it UP.
-Sri
You may be disappointed if you fail, but you are doomed if you don't try
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-09-2004 10:10 AM
03-09-2004 10:10 AM
Re: Questions about pkg res monitoring
Hi (Again),
While clicking submit, I saw your last question.
Yes. One package in the cluster be a dependent resource to another. For ex., I have to packages p1 and p2. I add the monitoring request as
#emscli -a /cluster/package/package_status/p1
#resls -qs /cluster/package/package_status/p1
/cluster/package/package_status/p1: Resource Instance
The current value of the resource is DOWN (3)
At this time the package is down. So, it show is as down. You can specify the above in your configuration file of p2 and make the value "UP". If the package p1 is down, then serviceguard will bring down the package p2.
However, I find it much convenient if I write my own monitoring scripts rather than using EMS. This way I can create my own lock files, dependencies the way I want to start the packages and their order etc.,
-Sri
While clicking submit, I saw your last question.
Yes. One package in the cluster be a dependent resource to another. For ex., I have to packages p1 and p2. I add the monitoring request as
#emscli -a /cluster/package/package_status/p1
#resls -qs /cluster/package/package_status/p1
/cluster/package/package_status/p1: Resource Instance
The current value of the resource is DOWN (3)
At this time the package is down. So, it show is as down. You can specify the above in your configuration file of p2 and make the value "UP". If the package p1 is down, then serviceguard will bring down the package p2.
However, I find it much convenient if I write my own monitoring scripts rather than using EMS. This way I can create my own lock files, dependencies the way I want to start the packages and their order etc.,
-Sri
You may be disappointed if you fail, but you are doomed if you don't try
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