MIBs Supported

The system supports both standard MIBs and Oracle-specific MIBs (enterprise MIBs). The configurable system elements are identified in the MIBs provided by Oracle. Every system maintains a database of values for each of the definitions written in these MIBs.

Standard MIBS

The values in the standard MIBs are defined in RFC-1213, (one of the governing specifications for SNMP). A standard MIB includes objects to measure and monitor IP activity, TCP activity, UDP activity, IP routes, TCP connections, interfaces, and general system description. Each of these values is associated both an official name (such as sysUpTime, which is the elapsed time since the managed device was booted) and a numeric value expressed in dot-notation (such as 1.3.6.1.2.1.1.3.0, which is the OID for sysUpTime).

Oracle provides the following standard MIBs:

• rfc3411-framework.mib
• rfc1907-snmpv2.mib
• rfc2011-ip.mib
• rfc2737-entity.mib
• rfc2863-if.mib (Oracle supports the ifName entry of the ifXTable, which is an extension to the interface table and which replaces ifExtnsTable. See RFC 2863 for details.)
• ianaiftype.mib
• rfc4001-inetAddr.mib
• rfc4022-tcp.mib
• rfc4113-udp.mib

Enterprise MIBs

Oracle provides the following enterprise MIBs:

MIB Name	Description
ap-agentcapability.mib	Details the SNMP agent’s capabilities that includes support for different modules: SNMPv2 capabilities support the SNMPv2 MIB and include the systemGroup, snmpGroup, snmpCommunityGroup, and snmpBasicNotificationsGroup variables. MIB-II capabilities support MIB-II and include the User Datagram Protocol (UDP)-MIB (udpGroup) variables and some, but not all of the IF-MIB (ifGeneralGroup and ifPacketGroup), IP-MIB (ipGroup and icmpGroup), and TCP-MIB (tcpGroup) variables. For more information about which variables are currently supported, refer to the ap-agentcapability.mib file. MIB capabilities include support for the contents of the MIBs listed in this table. Refer to the individual MIBs for details.
ap-ami.mib	Management interface on the SBC.
ap-codec.mib	Codec and transcoding information generated by systems.
ap-ems.mib	EMS traps.
ap-entity-vendortype.mib	OID assignments for Acme Packet hardware components.
ap-env-monitor.mib	Fan speed, temperature, and power supply for the system. It also sends out traps when status changes occur.
ap-license.mib	Status of your licenses.
ap-products.mib	Descriptions of the different SBC versions.
ap-security.mib	Information about the Acme Management Interface running on the SBC.
ap-slog.mib	syslog messages generated by the system via SNMP. Used for the network logging of system and network events, the syslog protocol facilitates the transmission of event notification messages across networks. The syslog MIB can also be used to allow remote log access. The SNMP system manager references syslog to find out about any and all syslog messages. If the following conditions are present, the SNMP agent sends an SNMP trap when a message is sent to the syslog system: The system configurations’s snmp-enabled parameter is set to enabled. The system configuration’s enable-snmp-syslog-notify parameter is set to enabled. The actual syslog severity level is of equal or greater severity than the severity level configured in the system config’s snmp-syslog-level field. No trap is sent under the following conditions: A syslog event is generated and the system config’s enable-snmp-syslog-notify parameter is set to disabled. The actual syslog severity level is of lesser severity (for example, higher numerical code value) than the severity level configured in the system config’s snmp-syslog-level parameter.
ap-smgmt.mib	Status of the system (for example, system memory or system health).
ap-smi.mib	General information about the system’s top-level architectural design.
ap-swinventory.mib	Status of the boot images, configuration information, and bootloader images for the system.
ap-tc.mib	Textual conventions used in enterprise MIBs.