Release Notes

• SONICWALL-FIREWALL-TRAP-MIB

• WLSR-AP-MIB, WLSX-SWITCH-MIB, WLSX-TRAP-MIB, WLSX-WLAN-MIB

• LLDP-MIB, LLDP-V2-MIB, LLDP-EXT-MED-MIB, DVMRP-STD-MIB, MAU-MIB, DISMAN-

TRACEROUTE-MIB, HC-ALARM-MIB, AI-AP-MIB

Issue 1:

Description: The following MIB(s) may not be parsed by the MIB Import Utility. You can verify if these

MIB(s) compile properly with any standard MIB compiler tool.

• ORiNOCO-MIB, AIBADGER-MIB, ALCATEL-IND1-PORT-MIRRORING-MONITORING-MIB, ALCATEL-

IND1-STACK-MANAGER-MIB, MPLS-LDP-MIB, APTIS-TRAPS-MIB, APTIS-V2TRAPS-MIB, ASANTE-

AH1012-MIB, SWITCH-VLAN-MIB, BEA-WEBLOGIC-MIB (BEA-WEBLOGIC-MIB.asn1.mib), Patrol,

CAIOPSMIB, CAISECMIB, CAIUXOS, CA-NTOS-MIB, CASCADE-MIB, DHCP-MIB, COM21-HCXOC3-

MIB, COM21-HCXTX-MIB, COM21-HCXTOP-MIB, COMPUTERM-COMMON-MIB, DMTF-SYSTEMS-

MIB, SYMBIOSDMI20MIFDEFINITION-MIB, EICON-MIB-SERVER, EICON-MIB-PORT, EICON-MIB-

CARD, EXTREME-CABLE-MIB, FUJITSU-EXTENDED-NONOS-AWN-MIB-V06, GANDALF-

ENTERPRISE-MIB, XPRESS-MIB, INKTOMI-TS-MIB, INTELCORPORATIONBASEBOARD-MIB, ELSA-MIB,

MERITAGE-MIB, SWITCHING-SYSTEMS-MIB, LUMINOUS-SYSTEM-MIB, LUMINOUS-TRAP-MIB,

CXAsyncIo-MIB, CXDDS-MIB, CXX25-MIB, CXLapBD-MIB, MICROSENS-CWDM8-MIB, FRX-MIB,

NEWOAK-MIB, SQUID-MIB, OLIVETTI-MIB

NOTE: If you notice any errors while parsing the MIB file and the specific MIB line number is

mentioned, fix the error in the MIB file and try again. Example: Parsing of MIBs that have special

characters in the OBJECT-TYPE/TRAP-TYPE/NOTIFICATION-TYPE names may fail.

Issue 2:

Description: Re-importing does not remove traps that are already imported in OpenManage Essentials.

Existing traps are updated (as long as the same EOID and Specific TrapId is present in the MIB) and new

traps are added.

Issue 3:

Description: Traps from the dependent MIBs are not listed while parsing a MIB. This may be inconsistent

with respect to a few third-party MIB parsing tools.

Issue 4:

Description: Removing a MIB does not remove the Event Category name from OpenManage Essentials.

This is to support the following use case.

In following scenario category name is not removed:

• Import MIB A with the default category name A.

• Import another MIB B with the same category name selected for previous MIB A.

• Remove MIB A. Category Name A is not removed as it is used by MIB B traps. If you remove B,

category A will still be present.

Issue 5:

Description: All the received traps (MIB imported trap definitions) in OpenManage Essentials are removed

when you remove a specific MIB using the MIB Import Utility.