- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- HPE Aruba Networking & ProVision-based
- >
- Stack SNMP monitoring
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
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
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
10-29-2014 05:32 PM
10-29-2014 05:32 PM
Stack SNMP monitoring
Hi All,
I have been trying to work out how to monitor the stack status of a HP E3800 physcial stack. I have found numerous posts with nagios etc on monitoring basic status of the switches but not the stack status.
There used to be a method with the procurve switches where you could access the switch stack members by appending @sw# to the SNMP community name but this seems to have been removed. I was hoping to monitor the additional members and if the query to the member failed it would be assumed the stack member is missing.
I have found MIB information for the HP virtual stack setup but not when using physcial stacking ports/modules/cables.
Has anyone managed to get any form of proactive stack monitoring happening in their enviroments?
Thanks Tom :)
- Tags:
- snmp
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-04-2015 11:19 PM
03-04-2015 11:19 PM
Re: Stack SNMP monitoring
Did you find out a solution? I have the same problem ...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-21-2016 07:40 AM
03-21-2016 07:40 AM
Re: Stack SNMP monitoring
Glad to see I am not the only one having an issue like this.
I had a member down but no alerts to tell me this! I thought I would try and go down the route of finding a MIB for the stacking module, as these are ports maybe there is a MIB for these.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-21-2016 03:25 AM
04-21-2016 03:25 AM
Re: Stack SNMP monitoring
Same issue here...
Anyone found anythign in meantime?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-29-2016 01:42 PM
04-29-2016 01:42 PM
Re: Stack SNMP monitoring
Stack member loss should generate a "warning" severity event and corresponding SNMP trap. Same for removal/insertion of the stacking module itself. The trap isn't generated by default, you have to configure your trap receiver for a trap-level of "not-info" to receive it. Agree this should be generated by default.
snmp-server host 128.44.120.99 community "public" trap-level not-info
W 04/26/16 17:34:26 03258 stacking: ST1-CMDR: Standby switch with Member ID 3
removed due to loss of communication
I 04/26/16 17:34:25 02559 chassis: ST4-MMBR: Stack port 1 is now off-line.
I 04/26/16 17:34:26 02559 chassis: ST2-MMBR: Stack port 3 is now off-line.
W 04/26/16 17:34:26 03270 stacking: ST1-CMDR: Topology is a Chain
2016-04-26 14:59:30 128.44.112.100(via UDP: [128.44.112.100]:161->[128.44.120.99]:162) TRAP, SNMP v1, community public
SNMPv2-SMI::enterprises.11.2.3.7.8.5.2 Enterprise Specific Trap (2) Uptime: 7:56:28.00
RMON-MIB::eventDescription.3258 = STRING: W 04/26/16 17:34:26 03258 stacking: ST1-CMDR: Standby switch with Member ID 3
removed due to loss of communication