- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Service Guard SNMP trap sending
Operating System - HP-UX
1823420
Members
2563
Online
109655
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
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
12-07-2007 01:04 PM
12-07-2007 01:04 PM
Service Guard SNMP trap sending
Hi,
we want to monitor our Service Guard clusters through SNMP. there is apparently a dedicated snmp sub-agent that runs for Service Guard.
The problem that we are having is that we get very few SNMP traps. I did some network tracing (using nettl) and saw the I only receive 2 snmp traps when a package is halted. That's it. When a package gets started, no traps.
I do not know much about Service Guard but can you config SG to send more traps?
Kris
we want to monitor our Service Guard clusters through SNMP. there is apparently a dedicated snmp sub-agent that runs for Service Guard.
The problem that we are having is that we get very few SNMP traps. I did some network tracing (using nettl) and saw the I only receive 2 snmp traps when a package is halted. That's it. When a package gets started, no traps.
I do not know much about Service Guard but can you config SG to send more traps?
Kris
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-10-2007 01:35 AM
12-10-2007 01:35 AM
Re: Service Guard SNMP trap sending
You cannot configure the traps that Serviceguard sends out but you should get more than this. You should see the following:
hpmcSGSubagentUp Signals the management station that the ServiceGuard subagent is up
hpmcSGReconfig Cluster is in the reconfiguration state
hpmcSGClusterUp Cluster is up
hpmcSGClusterDown Cluster is down (see section 6.1.4)
hpmcSGConfigChange Cluster/package configuration has been applied (via cmapplyconf)
hpmcSGPkgStart Package has started
hpmcSGPkgUp Package is running
hpmcSGPkgHalt Package is halting
hpmcSGPkgDown Package is down (unowned)
hpmcSGSvcDown Service is down
hpmcSGPkgFlags Packageâ s global or local switch enable flag has been changed
hpmcSGIPAddrUp MC/ServiceGuard added a relocatable address
hpmcSGIPAddrDown MC/ServiceGuard removes a relocatable IP address
hpmcSGLocalSwitch MC/ServiceGuard has completed a local switch from one network interface to another
hpmcSGSubnetUp MC/ServiceGuard detects a previously disabled subnet is now operational
hpmcSGSubnetDown MC/ServiceGuard detects a previously operational subnet is now down
hpmcSGNodeUp Node joins active cluster membership, could be after cluster reforms
hpmcSGNodeHalted Node has been removed from active cluster membership as a result of an operator-initialed command
hpmcSGNodeFailed Node state has changed to failed
hpmcSGSubagentUp Signals the management station that the ServiceGuard subagent is up
hpmcSGReconfig Cluster is in the reconfiguration state
hpmcSGClusterUp Cluster is up
hpmcSGClusterDown Cluster is down (see section 6.1.4)
hpmcSGConfigChange Cluster/package configuration has been applied (via cmapplyconf)
hpmcSGPkgStart Package has started
hpmcSGPkgUp Package is running
hpmcSGPkgHalt Package is halting
hpmcSGPkgDown Package is down (unowned)
hpmcSGSvcDown Service is down
hpmcSGPkgFlags Packageâ s global or local switch enable flag has been changed
hpmcSGIPAddrUp MC/ServiceGuard added a relocatable address
hpmcSGIPAddrDown MC/ServiceGuard removes a relocatable IP address
hpmcSGLocalSwitch MC/ServiceGuard has completed a local switch from one network interface to another
hpmcSGSubnetUp MC/ServiceGuard detects a previously disabled subnet is now operational
hpmcSGSubnetDown MC/ServiceGuard detects a previously operational subnet is now down
hpmcSGNodeUp Node joins active cluster membership, could be after cluster reforms
hpmcSGNodeHalted Node has been removed from active cluster membership as a result of an operator-initialed command
hpmcSGNodeFailed Node state has changed to failed
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
Learn About
News and Events
Support
© Copyright 2025 Hewlett Packard Enterprise Development LP