- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- STP state via SNMP in 9304 with 8.0.01c
Switches, Hubs, and Modems
1753841
Members
8830
Online
108806
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
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
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
10-25-2006 10:28 PM
10-25-2006 10:28 PM
STP state via SNMP in 9304 with 8.0.01c
I have some 9304 and 9308 with 8.0.01c. They are configured for "spanning-tree single 802-1w".
I am trying to monitor the state of spanning tree with SNMP, and I can see some data, but not all.
For example, I see the root bridge, but not the root port nor the root cost:
snmpwalk 9304-2 .1.3.6.1.2.1.17.2.5.0
Hex-STRING: 04 00 00 0C DB 39 02 00
snmpwalk 9304-2 .1.3.6.1.2.1.17.2.7.0
INTEGER: 0
snmpwalk 9304-2 .1.3.6.1.2.1.17.2.6.0
INTEGER: 0
In case you are wondering wether this is, in fact, the root bridge, it is not: the CLI says its root port is 2/1, and root cost is 20001, and also its ID is different:
snmpwalk 9304-2 .1.3.6.1.2.1.17.1.1.0
Hex-STRING: 00 0C DB 40 4B 00
In the same way, I cannot see the designated bridge and port of a port:
snmpwalk 9304-2 .1.3.6.1.2.1.17.2.15.1.8
returns all 00 00 00 00 00 00, and
snmpwalk 9304-2 .1.3.6.1.2.1.17.2.15.1.9
returns all 00 01.
Since this is obviously a bug, while we wait for it to be fixed, does anybody know where else in the proprietary MIB I can get this data? I tried to grep the MIB files, but all the icf subtree seems not to be implemented in this box.
By the way, what is the proper way to report bugs in procurve products, in order to maximize the probability of seeing them fixed?
I am trying to monitor the state of spanning tree with SNMP, and I can see some data, but not all.
For example, I see the root bridge, but not the root port nor the root cost:
snmpwalk 9304-2 .1.3.6.1.2.1.17.2.5.0
Hex-STRING: 04 00 00 0C DB 39 02 00
snmpwalk 9304-2 .1.3.6.1.2.1.17.2.7.0
INTEGER: 0
snmpwalk 9304-2 .1.3.6.1.2.1.17.2.6.0
INTEGER: 0
In case you are wondering wether this is, in fact, the root bridge, it is not: the CLI says its root port is 2/1, and root cost is 20001, and also its ID is different:
snmpwalk 9304-2 .1.3.6.1.2.1.17.1.1.0
Hex-STRING: 00 0C DB 40 4B 00
In the same way, I cannot see the designated bridge and port of a port:
snmpwalk 9304-2 .1.3.6.1.2.1.17.2.15.1.8
returns all 00 00 00 00 00 00, and
snmpwalk 9304-2 .1.3.6.1.2.1.17.2.15.1.9
returns all 00 01.
Since this is obviously a bug, while we wait for it to be fixed, does anybody know where else in the proprietary MIB I can get this data? I tried to grep the MIB files, but all the icf subtree seems not to be implemented in this box.
By the way, what is the proper way to report bugs in procurve products, in order to maximize the probability of seeing them fixed?
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.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP