- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- Aruba & ProVision-based
- >
- Stack SNMP monitoring
-
- Forums
-
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
- HPE Blog, Austria, Germany & Switzerland
- Blog HPE, France
- HPE Blog, Italy
- HPE Blog, Japan
- HPE Blog, Middle East
- HPE Blog, Latin America
- HPE Blog, Russia
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
-
Blogs
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Blog, Latin America
- HPE Blog, Middle East
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
-
Information
- Community
- Welcome
- Getting Started
- FAQ
- Ranking Overview
- Rules of Participation
- Tips and Tricks
- Resources
- Announcements
- Email us
- Feedback
- Information Libraries
- Integrated Systems
- Networking
- Servers
- Storage
- Other HPE Sites
- Support Center
- Aruba Airheads Community
- Enterprise.nxt
- HPE Dev Community
- Cloud28+ Community
- Marketplace
-
Forums
-
Blogs
-
Information
-
English
- 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
- Email to a Friend
- 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
- Email to a Friend
- 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
- Email to a Friend
- 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
- Email to a Friend
- 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
- Email to a Friend
- 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
Hewlett Packard Enterprise International
- Communities
- HPE Blogs and Forum
© Copyright 2021 Hewlett Packard Enterprise Development LP