- Community Home
- >
- Servers and Operating Systems
- >
- ProLiant
- >
- Server Management - Systems Insight Manager
- >
- HP-SIM 7.3 requires uniquely named MIB variables?
-
- 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, 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
02-05-2015 10:06 AM
02-05-2015 10:06 AM
HP-SIM 7.3 requires uniquely named MIB variables?
Using HP-SIM 7.3 November 2014 update...
I ran across an issue attempting to 'fix' the THREEPARMIB.MIB so that my 3PAR 7200c actually reports events with a severity other than informational. In the process of doing this, I kept getting an incorrect trap description for the mib variable 'state' ({alertentry 9}); no matter how I changed the description string .CFG file and reloaded it via mxmib, I kept getting the string "Current State of this Physical Drive.".
A quick pass of grep over the MIB files showed a MIB variable in HPNR.MIB also called 'state' which contains the description string I am getting.
I went back into the THREEPARMIB.CFG file, changed references to the variable 'state' to 'ThreeParState', reloaded the .CFG file once more, and now the traps work as expected.
As it is, the HP-supplied THREEPARMIB.MIB and corresponding .CFG file dated 02/06/2014 are not completely useful.
Is it documented some where that HP-SIM requires MIB variables that have unique names across *all* loaded MIBs?
Thanks.
- Tags:
- 3PAR
Hewlett Packard Enterprise International
- Communities
- HPE Blogs and Forum
© Copyright 2021 Hewlett Packard Enterprise Development LP