The SBC Edge SCOM Management Pack allows customers in a Microsoft Server Environment to monitor the health of their SBC Edge systems using SCOM.
This page guides you through the import and installation procedure of the Sonus SCOM Management Pack onto the Microsoft System Center Operations Manager SCOM 2012.
For detailed information on monitoring of the SCOM pack, see SBC SCOM Object Model and Health Monitoring.
The Sonus SCOM management pack is available for download from the Sonus SBC Edge Download Center.
SBC1K2K_SCOM.MP
fileSBC1K2K_SCOM.MPB
fileSBC1K2K_SCOM.MP
into SCOM 2007 and SBC1K2K_SCOM.MPB
into SCOM 2012. If the SCOM 2007 Management Pack file is imported into SCOM 2012, the import will not return meaningful errors, but the discovery will fail.In the navigation tree, go to Management Packs > Import Management Packs....
Select the appropriate downloaded file:
SBC1K2K_SCOM.MP
fileSBC1K2K_SCOM.MPB
file
In the Select Management Packs window, click Install.
You will see the progress indicator scrolling as the file is installed.
Verify that the Sonus SCOM Management Pack appears in the list.
SBC Edge supports SNMPv2c and SNMPv3, using the standard port 161. The SCOM Management Pack (MP) is related to the discovery of the SBC by mapping the object identifiers (OID's) to various components in the SCOM object model. Once the Management Pack is downloaded and imported into SCOM, the SNMP management address has to be created in the SBC.
To troubleshoot issues, use a MIB browser tool to perform SNMP walks from the SCOM host computer. If the walks are working then there should not be a network connectivity issue and the issue can be narrowed down to SCOM configuration (e.g.: community) or an issue related to the MP import. If they are not working, then there would be a network issue, or a SBC target address configuration issue.
The Sonus SBC Edge SCOM Pack works through SNMP. Refer to Working with SNMP and Alarms for details.