SNMP
The Simple Network Management Protocol (SNMP) is a part of the Internet Protocol Suite, defined by the Internet Engineering Task Force (IETF). It allows you to monitor system and health conditions for an Oracle® Enterprise Session Border Controller (E-SBC) through an external network management (northbound) system, such as the Oracle Communications Session Delivery Manager or an SNMP manager. The system supports SNMPv3, v2 or v1 to interface with a range of external NMS systems.
Detail on SNMP operation, configuration and data is documented in the Oracle Communications Session Border Controller MIB Reference Guide. The first chapter of the Oracle Communications SNMP Reference Guide provides a configuration overview and procedures. The rest of the guide serves as a reference for the MIB.
SNMP Configuration
SNMP configuration on the E-SBC typically includes defining:
- Administrative management information
- SNMP messaging, including:
- Trap information—Sent by the E-SBC to the northbound system, similar to alarms.
- System detail information—Collected by the northbound system from the E-SBC. This is typically referred to as read operation.
- System detail information—Configured by the northbound system on the E-SBC. This is typically referred to as write operation.
SNMP Data
You must understand SNMP data to determine your actions when you see it. SNMP data is organized into a hierarchical numbering scheme in the form of Object Identifiers (OIDs). OIDs are collected and presented within the context of Management Information Bases (MIBs). A text file external to the E-SBC system code called a miboid maintains a correlation between object numbers and text names. The system code and miboid numbers correlate each OID to a software or hardware construct that typically has a value and is of interest to the people who monitor them. A set of .mib text files contain the data presented to the human user, referenced by the object names, for each hierarchical information group. You get the applicable files from the device vendor and load them into SNMP managers
OID numbering is, to a large extent, defined and managed by the IETF. This management benefits equipment vendors by preventing information conflation and identifier overlaps. Similar to a MAC address, the IETF provides equipment vendors with numerical identities under which they can create their own hierarchical schemes and define their systems' SNMP information. An example of vendor-specific information is a configuration parameter's value. Similarly, the IETF maintains and shares standard numerical hierarchies used by all equipment vendors so they do not have to create them. An example of standard information is interface speed.
