All MIBs › APENT-MIB
Organization: ArrowPoint Communications Inc.
Last Updated: 1997-07-20
Category: Telephony and VoIP, Vendor: Acme Packet
Description:
Enterprise MIB for Acme Packet SBCs that defines the root OID structure and product registration.
Imported Objects
From RFC1155-SMI
| enterprises |
From SNMPv2-SMI
| MODULE-IDENTITY |
What Is APENT-MIB?
APENT-MIB is the root enterprise MIB for Acme Packet (now part of Oracle, originally registered under the ArrowPoint Communications OID branch) session border controller products, defining the top-level OID hierarchy and product registration objects for the platform. It organizes management and local objects (apMgmt, apLocal), a temperature-related grouping (apTemp), and product identifiers for specific hardware models (apCS100, apCS800), rather than being a purely empty registration stub. Given the presence of apTemp, this module has some direct relevance to hardware environmental monitoring, alongside its role as the structural parent for further Acme Packet product MIBs covering CPU, memory, and session-processing status. It depends on the historical ArrowPoint Communications enterprise OID branch that Acme Packet inherited. It's deployed on Acme Packet (Oracle) Net-Net/CS-series session border controllers in VoIP and SIP trunking infrastructure, and administrators locating the APENT-MIB OID root in a MIB browser will find apTemp and the product identifiers nested directly beneath it.
IPNetwork Monitor allows you to monitor SNMP objects defined in APENT-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.
What Can Be Monitored
- chassis temperature
- management configuration state
- product/hardware model identification
Supported Devices
- Oracle Acme Packet 6300 — high-capacity session border controller, part of Oracle's current SBC hardware platform lineup
- Oracle Acme Packet 1100 — small-office/branch session border controller, current entry-level SBC platform
Monitoring Examples
An administrator would check apTemp-related objects to monitor chassis temperature on an apCS100 or apCS800 session border controller, watching for values that indicate the unit is running hot due to fan or cooling failure. apMgmt and apLocal would be referenced for management-plane configuration state, while the apCS100/apCS800 product identifier objects let monitoring tools confirm which hardware model is being managed so they apply the correct thresholds.
OIDs
| OID symbolic | OID numeric | Type | Access | Description |
|---|---|---|---|---|
| arrowPoint | 1.3.6.1.4.1.2467 | The MIB module used to describe the ArrowPoint Communications Enterprise MIB branch. | ||
| apMgmt | 1.3.6.1.4.1.2467.1 | |||
| pppExt | 1.3.6.1.4.1.2467.1.1 | |||
| frExt | 1.3.6.1.4.1.2467.1.2 | |||
| isdnExt | 1.3.6.1.4.1.2467.1.3 | |||
| firewall | 1.3.6.1.4.1.2467.1.4 | |||
| qos | 1.3.6.1.4.1.2467.1.5 | |||
| localBalance | 1.3.6.1.4.1.2467.1.6 | |||
| remoteBalance | 1.3.6.1.4.1.2467.1.7 | |||
| tunnelExt | 1.3.6.1.4.1.2467.1.8 | |||
| ipv4Ext | 1.3.6.1.4.1.2467.1.9 | |||
| apIpv4 | 1.3.6.1.4.1.2467.1.9.1 | |||
| apIpv4Interface | 1.3.6.1.4.1.2467.1.9.2 | |||
| apIpv4RoutingProtocols | 1.3.6.1.4.1.2467.1.9.3 | |||
| apIpv4Rip | 1.3.6.1.4.1.2467.1.9.3.1 | |||
| apIpv4Ospf | 1.3.6.1.4.1.2467.1.9.3.2 | |||
| apIpv4Arp | 1.3.6.1.4.1.2467.1.9.4 | |||
| apIpv4StaticRoutes | 1.3.6.1.4.1.2467.1.9.5 | |||
| apIpv4Host | 1.3.6.1.4.1.2467.1.9.6 | |||
| apIpv4Dns | 1.3.6.1.4.1.2467.1.9.7 | |||
| apIpv4Redundancy | 1.3.6.1.4.1.2467.1.9.8 | |||
| connMgmt | 1.3.6.1.4.1.2467.1.10 | |||
| terminalMgmt | 1.3.6.1.4.1.2467.1.11 | |||
| radiusClientExt | 1.3.6.1.4.1.2467.1.12 | |||
| securityMgrExt | 1.3.6.1.4.1.2467.1.13 | |||
| bridgeExt | 1.3.6.1.4.1.2467.1.14 | |||
| svcExt | 1.3.6.1.4.1.2467.1.15 | |||
| cntExt | 1.3.6.1.4.1.2467.1.16 | |||
| grpExt | 1.3.6.1.4.1.2467.1.17 | |||
| cntsvcExt | 1.3.6.1.4.1.2467.1.18 | |||
| grpsvcExt | 1.3.6.1.4.1.2467.1.19 | |||
| logExt | 1.3.6.1.4.1.2467.1.20 | |||
| ds1Ext | 1.3.6.1.4.1.2467.1.21 | |||
| snmpExt | 1.3.6.1.4.1.2467.1.22 | |||
| aclExt | 1.3.6.1.4.1.2467.1.23 | |||
| ifExt | 1.3.6.1.4.1.2467.1.24 | |||
| ownExt | 1.3.6.1.4.1.2467.1.25 | |||
| bwdthExt | 1.3.6.1.4.1.2467.1.26 | |||
| ispgrpExt | 1.3.6.1.4.1.2467.1.27 | |||
| qosExt | 1.3.6.1.4.1.2467.1.28 | |||
| cctExt | 1.3.6.1.4.1.2467.1.29 | |||
| ftpExt | 1.3.6.1.4.1.2467.1.30 | |||
| bootExt | 1.3.6.1.4.1.2467.1.31 | |||
| appExt | 1.3.6.1.4.1.2467.1.32 | |||
| hssiExt | 1.3.6.1.4.1.2467.1.33 | |||
| chassisMgrExt | 1.3.6.1.4.1.2467.1.34 | |||
| cnthotExt | 1.3.6.1.4.1.2467.1.35 | |||
| flowMgrExt | 1.3.6.1.4.1.2467.1.36 | |||
| webMgmtExt | 1.3.6.1.4.1.2467.1.37 | |||
| csrpExt | 1.3.6.1.4.1.2467.1.38 | |||
| enetExt | 1.3.6.1.4.1.2467.1.39 | |||
| dnsServerExt | 1.3.6.1.4.1.2467.1.40 | |||
| cntdnsExt | 1.3.6.1.4.1.2467.1.41 | |||
| eqlExt | 1.3.6.1.4.1.2467.1.42 | |||
| sshdExt | 1.3.6.1.4.1.2467.1.43 | |||
| ap64Stats | 1.3.6.1.4.1.2467.1.44 | |||
| schedExt | 1.3.6.1.4.1.2467.1.45 | |||
| kalExt | 1.3.6.1.4.1.2467.1.46 | |||
| httpExt | 1.3.6.1.4.1.2467.1.47 | |||
| dnshotExt | 1.3.6.1.4.1.2467.1.48 | |||
| urqlExt | 1.3.6.1.4.1.2467.1.49 | |||
| nqlExt | 1.3.6.1.4.1.2467.1.50 | |||
| dqlExt | 1.3.6.1.4.1.2467.1.51 | |||
| cappUdpExt | 1.3.6.1.4.1.2467.1.52 | |||
| tagExt | 1.3.6.1.4.1.2467.1.53 | |||
| proxDbExt | 1.3.6.1.4.1.2467.1.54 | |||
| probeRttExt | 1.3.6.1.4.1.2467.1.55 | |||
| plucExt | 1.3.6.1.4.1.2467.1.56 | |||
| publishExt | 1.3.6.1.4.1.2467.1.57 | |||
| subscribeExt | 1.3.6.1.4.1.2467.1.58 | |||
| apLocal | 1.3.6.1.4.1.2467.2 | |||
| chassis | 1.3.6.1.4.1.2467.2.1 | |||
| flash | 1.3.6.1.4.1.2467.2.2 | |||
| apTemp | 1.3.6.1.4.1.2467.3 | |||
| layerDepend | 1.3.6.1.4.1.2467.3.1 | |||
| apProducts | 1.3.6.1.4.1.2467.4 | |||
| apCS100 | 1.3.6.1.4.1.2467.4.1 | |||
| apCS800 | 1.3.6.1.4.1.2467.4.2 | |||
| apCS150 | 1.3.6.1.4.1.2467.4.3 | |||
| apCS50 | 1.3.6.1.4.1.2467.4.4 |
FAQ
Does APENT-MIB provide any hardware monitoring data on an Acme Packet session border controller, or is it just a registration stub?
It's more than a pure registration stub — alongside the top-level OID hierarchy and product identifiers for models like the CS100 and CS800, it includes an apTemp grouping, giving it direct relevance to chassis temperature monitoring in addition to its role as the structural parent for other Acme Packet product MIBs.
What would an administrator find directly under the APENT-MIB OID root when browsing a CS100 or CS800 SBC?
The apMgmt and apLocal management/configuration branches, the apTemp temperature grouping, and product identifiers for the specific SBC hardware model — all nested directly beneath the enterprise root that other Acme Packet product MIBs build on.
RFC description
Acme Packet SBC enterprise MIB defining the root OID structure and product registration.
Start monitoring Oracle Acme Packet 6300/1100 session border controllers 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.