Release Notes

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: 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 4:
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.
Example: Import a device A MIB having some traps definitions. After importing, assume OpenManage Essentials receives 10
traps from device A. If you remove the imported MIB from OpenManage Essentials, the 10 received traps in OpenManage
Essentials are also removed.
Issue 5:
Description: Search Unknown Traps lists traps even after the trap is added using MIB Import Utility, as previous events
received are still categorized in OpenManage Essentials as unknown.
Issue 6:
Description: The data displayed in the Edit Trap(s) grid is invalid if you delete or revert that same trap definitions and then
navigate to the Edit Trap menu.
Issue 7:
Description: All the received traps (manually added trap definitions) in OpenManage Essentials are removed when you remove
the specific trap definition using the Delete Trap functionality.
Issue 8:
Description: The data displayed in Edited Trap(s) in OpenManage Essentials indicates the original definition of the built-in
traps that are edited using Edit Trap functionality.
Troubleshooting
Installation
● Ensure that the latest SQL server service packs are installed on the system. You can run the following command on the
command prompt to verify the SQL version.
○ sqlcmd -Q "print @@version"
● For typical install, ensure that the current user has sysAdmin rights to the SQL Server. For custom install, ensure that the
provided authentication credentials have sysAdmin rights.
● Try to use the custom install with different authentication methods if typical install fails.
● Collect the logs from the temp folder. Search for the latest MgmtSt_*.log and InstallUtil_Install.log files. Try
to quickly analyze (if possible) InstallUtil_Install.log.
24