NETWORK-APPLIANCE-MIB.mib Error defining registration

[Udo Hillenbrand]

Hello,
I want to register the NETWORK-APPLIANCE-MIB.mib. But when I want to compile the mib an error occured:
C:\Program Files (x86)\HP\Systems Insight Manager\mibs>mcompile NETWORK-APPLIANC
E-MIB.mib

HP Systems Insight Manager Mib Compiler, Version 5.0.2.1
Copyright (c) 2003-2006 Hewlett Packard Corporation

Compiling NETWORK-APPLIANCE-MIB.mib

Line: 24206: Error defining registration: Invalid parent label or subid
Mib compilation failed.

I have the file from:
http://www.oidview.com/mibs/789/NETWORK-APPLIANCE-MIB.html

What can I do?

Best Regards
Udo Hillenbrand

[David Claypool]

What is the content of line 24206?

[Udo Hillenbrand]

::= { netapp 0 2 }

[David Claypool]

...so the label 'netapp' has not been previously defined, meaning there probably is another MIB that is referenced that you need as well. You need to consult your documentation from Network Appliance.

[Udo Hillenbrand]

Hello,
the netapp.mib ist registered:
C:\Program Files (x86)\HP\Systems Insight Manager\mibs>mxmib -f netapp.cfg

PROCESSING MIBS IN FILE LIST


COMMAND COMPLETED SUCCESSFULLY

C:\Program Files (x86)\HP\Systems Insight Manager\mibs>mcompile NETWORK-APPLIANC
E-MIB.mib

HP Systems Insight Manager Mib Compiler, Version 5.0.2.1
Copyright (c) 2003-2006 Hewlett Packard Corporation

Compiling NETWORK-APPLIANCE-MIB.mib

Line: 24206: Error defining registration: Invalid parent label or subid
Mib compilation failed.




Another problem is on the sim that it show generic "Generic unregistered" traps with follow datas:
Enterprise OID String. 1.3.6.1.4.1.8072.4
Generic Trap ID. 6
Specific Trap ID. 2

Mib Information
The associated MIB File Name for this trap is cpqgen.mib and the MIB identifier CPQGEN-MIB


But I have registered this mib correctly:
C:\Program Files (x86)\HP\Systems Insight Manager\mibs>mxmib -f NET-SNMP-AGENT-M
IB.cfg

PROCESSING MIBS IN FILE LIST


COMMAND COMPLETED SUCCESSFULLY


What can I do?
I have already restarted the SIM service.
We have SIM version 5.3

Best Regards
Udo Hillenbrand

[Hubert Eiermann]

Hello Udo,

I ran into the same problem lately. Having a close look at the MIB file, I realized that OID enterprises.netapp.0 does not have a name associated with it.

To fix this, I made the following definition:

netapp0 OBJECT IDENTIFIER ::= { netapp 0 }

An in the bottom of the MIB file, I rewrote each trap definition, e.g.

::= { netapp 0 2 }

is changed to

::= { netapp0 2 }

With these modifications in place, I could compile and register the MIB with HP SIM.

Still there is a problem remaining: NetApp trap definitions are missing a severity description. Instead, they say, they code severity in the last digit of the trap OID.

HP SIM is not aware of this non-standard definition and, by default, treats all NetApp traps as informational. So, after registration, you may want to provide a user-defined severity for each trap type.

Hope this helps.

Regards
Hubert

[Hubert Eiermann]

Btw, I just finished running a validation of the NETWORK-APPLIANCE-MIB. It gives me a warning about an implicit node definition on that line. Seems, HP SIM cannot grok this, though it is only a minor violation of standards :-(

[Udo Hillenbrand]

Hello Hubert,
I have fixed this error with your manual.
So I can compile and import the mibfile.
But in the SIM SNMP Trap Settings all fields are empty for NETWORK-APPLIANCE-MIB.mib.

Can you append the correct mibfile?
Thanks

Best Regards
Udo Hillenbrand

[Hubert Eiermann]

Hello Udo,

NetApp says, it is best to use the MIB file that can be downloaded from vol0 of the machine you are currently using.

So I send you my corrections based on the MIB file from a machine that was lately installed at one of our customers' site. It should be fairly up to date.

It includes my corrections related to the implicit node definition that SIM complains about, as described above. It does n_o_t include any corrections to the incomplete trap definitions themselves, e.g. severities. I did this manually on SIM in the user-defined SNMP Trap Settings after the MIB had been registered.

Regards
Hubert

[Baker, A M]

Following the directions above gets you most of the way.
The mcompile generates a .cfg file.
The .cfg file has an SNMP v2 reference to

netappModuleId OBJECT IDENTIFIER ::= { snmpModules 789 }

Remove this line and the import (via mxmib) will complete successfully.

The previous caveat about the severity levels not crossing over still applies.

You can match the severity by following the internal notes from Netapp in the mib indicating that the last digit of the event identifier IS the severity.

-- 1 emergency
-- 2 alert
-- 3 critical
-- 4 error
-- 5 warning
-- 6 notification
-- 7 information
-- 8 debug

Example:
Event ID = 412
A chassis fan has been degraded.

The severity for this event is "2" indicating an alert.

Perhaps someone from NetApp or HP would be kind enough to run through the 150-200 events and identify them in the SNMP v1 file format HP uses or convert the SNMP v3 file so that HP's config tool will parse it correctly.

Or we could just update the cfg file with all the severity codes in the format:

--#SEVERITY ALERT

...and so forth...