All MIBs › APAGENTCAP-MIB
Organization: Acme Packet, Inc
Last Updated: 2012-07-16
Category: Telephony and VoIP, Vendor: Acme Packet
Description: Acme Packet SBC SNMP agent capabilities declaration for supported MIB modules.
Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.
What Is APAGENTCAP-MIB?
APAGENTCAP-MIB is an AGENT-CAPABILITIES conformance module (associated with Acme Packet session border controller equipment based on its naming) that declares which standard MIB modules and object groups the device's SNMP agent supports, such as the standard IF-MIB, IP-MIB, TCP-MIB, UDP-MIB, and Entity MIB. It contains no runtime data objects of its own; instead it is a capabilities statement used by management systems to know in advance which standard MIB groups (and which specific variations, like the modified ifGroup noted for release 3.0) are implemented on this agent. As a conformance module it has no direct hardware/software status monitoring role, but it indirectly supports monitoring by letting NMS tools determine which standard interface, IP, TCP, UDP, and entity-inventory data can actually be polled from the device. It explicitly depends on and declares support levels for the IETF standard IF-MIB, IP-MIB, TCP-MIB, UDP-MIB, and ENTITY-MIB. It is used wherever the associated device's SNMP agent needs to advertise its standards compliance to management platforms. Engineers can download the APAGENTCAP-MIB file directly to load it into their MIB browser.
IPNetwork Monitor allows you to monitor SNMP objects defined in APAGENTCAP-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.
Supported Devices
- Acme Packet Session Border Controller
Monitoring Examples
This is a conformance/AGENT-CAPABILITIES module, not a data-bearing MIB, so there is no runtime monitoring scenario to describe honestly. Objects like apIfMibCapabilities, apIPMibCapabilities, apTCPMibCapabilities, apUDPMibCapabilities, and apEntityCapabilities are capability declarations indicating the agent implements (a specific variant of) the IF-MIB, IP-MIB, TCP-MIB, UDP-MIB, and Entity MIB, respectively. A management system would consult apSnmpMibCapabilities during agent discovery to decide which standard MIBs it can safely poll against this device, rather than polling anything from this module itself.
Imported Objects
From ACMEPACKET-SMI
| acmepacketAgentCapability | OBJECT-IDENTITY |
From SNMPv2-CONF
| AGENT-CAPABILITIES | |
| MODULE-COMPLIANCE |
From SNMPv2-SMI
| MODULE-IDENTITY | |
| NOTIFICATION-TYPE | |
| OBJECT-TYPE | |
| enterprises | |
| mib-2 | |
| snmpModules |
OIDs
RFC description
Defines agent capability statements for Acme Packet session and signaling border controller MIB support.
Start monitoring Acme Packet (Oracle) Session Border Controller with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.