Originally posted by: sschmitt
the existing MIB file can not be read by HP Openview. Customer gets "no traps are configured".Any MIB specialist available???They need all traps for monitoring...very urgent...
Originally posted by: dkornilov
For urgent requests you need to open a support case with your organization (I presume, from your email, it is HDS GSC). If they can't resolve it, the case will be escalated to BlueArc.
With that said, the most likely reason you are getting "no traps are configured" is that the traps issued by the server are standard ISO v1 traps, so they are not defined in the MIBs. In other words, the Openview NMS does not need to have the MIBs imported to decipher the traps.
You could import SNMP v2 MIBs (two files supplied) and use those for polling various operational stats.
Hope this helps.
well my email unmasked me :-)
I though, I will get a quick and easy answer in this community.
Guessing HP Openview wants to have a v1 MIB. Where can I get one?
Not sure what MIB files HP OV comes with, but I'd guess it will have all the standard MIBs included.
Are you getting the traps already from BlueArc equipment into your NMS and the issue is that they are not getting decoded (i.e., numeric OIDs)?
Originally posted by: stephen-butler
The MIB files are just ASCII text and they do kindof describe which traps we send. E.g. looking at BlueArc.2050.16c.mib and BlueArcTitan.2050.16c.mib which are the MIB files shipped with 7.0.2050.16c right at the bottom it says:
--<br/><br/>-- Trap Notifications<br/><br/> The agent may generate the following traps :<br/><br/> LinkUp, ColdStart<br/>-- Authentication Failure (if configured)<br/><br/>--
These are generic SNMPv1 traps described in RFC 1157 (
http://www.rfc-editor.org/rfc/pdfrfc/rfc1157.txt.pdf) section 4.1.6 - The Trap-PDU pages 27 - 29. It's been a very long time since I used HP Openview NNM but IIRC it's supplied with MIB files for these sorts of things. I don't recall though if you have to specifically load it. (Or I may be being confused with SunNet Manager!) We use these traps to indicate:
The agent has rebooted.
The network link is up.
An SMNP NMS has attempted to communicate with the agent but is not allowed access. Authentication Failure traps need to be configured by selecting the "Send traps upon authentication failure" checkbox on the SNMP Access Configuration page on the SMU.
In addition on the Home / Status & Monitoring / SNMP Traps Setup you can also setup whether traps get sent for Severe, Warning and Information alerts in the Notification Frequency box. (This is briefly described in the 7.0.2050 version of the Administration Guide Release 7.0 (SAG-700-2) in Section 9 - Status & Monitoring / Event Logging and Notification / Setting up an SNMP Agent / Sending SNMP Traps pages 580 - 581.
These traps as sent as "Enterprise specific traps" and contain the description of the event as it appears in the event log - your NMS has to be able to parse the text in these fields somehow to do very much with them.
Message was edited by: Stephen Butler - paragraph separation.
Retrieving data ...