1084Simple Network Management Protocol (SNMP)DescriptionSV9100 system software contains Simple Network Management Protocol (SNMP) support that functionswith Private MIB’s and SNMP traps. Typically, an administrator uses an SNMP such as NECMasterScope application to centrally manage network devices. Using SNMP on the SV9100 allows itto be managed alongside these other network devices. The SV9100 is considered as an SNMP Agentthat can talk to an SNMP application.Private MIBS allow an SNMP application to make very specific requests to the SV9100 to obtain usefulinformation from the system. Below are examples of the different types of information that is available:Hardware Key CodeInstalled HardwareSystem SoftwareSystem Date and TimeInstalled licensesVOIP InformationChanges to system programming data (R8 Enhancement)SNMP traps can be used for the purpose of monitoring SV9100 alarms via SNMP. When any of thealarms are triggered on the SV9100, they can be reported in the SNMP application. Details of theavailable alarms reports are available in Alarm Reports.A ‘MIB’ (Management Information Base) file has been created that can be loaded into an SNMPapplication. An ‘OID’ (Object ID) of 14399 has been registered for use by NEC for its systems, this ispre-configured in the MIB file.Software Release 8.0 includes an enhancement to generate SNMP traps when programmingchanges are detected. See Release 8.0 EnhancementConditionsAn SNMP browser is required to manage and view SNMP traps.When properly configured, an SV9100 that enters a condition which causes an alarm willalso send SNMP traps to the SNMP browser.A properly configured MIB OID file which is fully compiled in the MIB browser is requiredbefore the MIB browser can perform Get operations from the SNMP agent.The “Target Host” parameter referenced in Program 90-64 is the SNMP networkmanagement device(s) that are run on an external PC.All MIB OIDs used with the SV9100 begin with 1.3.6.1.4.1.14399.20.10.SNMP traps for alarms that are not desired can be turned off in Program 90-10 by settingthe alarm type to “Not Set” for the alarm number that corresponds to the SNMP trapnumber. For instance, SNMP trap 1.3.6.1.4.1.14399.20.10.30.2.6.60.0 is for alarm number60, notice the second to the last octet in the example SNMP MIB OID.
