ArrowPoint MIBs

The one module here, APENT-MIB, is the root enterprise MIB for Acme Packet session border controllers (now part of Oracle), registered historically under the ArrowPoint Communications OID branch, and it defines the top-level OID hierarchy and product registration (including the apCS100/apCS800 and 6300/1100-series SBC models) rather than the SBC's actual call-signaling data. Its confirmed subject matter is chassis-level hardware status such as temperature monitoring (apTemp-related objects) alongside the product-identification structure other Acme Packet MIBs build on. If you operate an Oracle Acme Packet session border controller, this page is where you'd start for chassis temperature/hardware-identity objects, though most of an SBC's actual call/session data lives in other Acme Packet-specific modules not sampled here. Because this module's OID root traces back to the ArrowPoint acquisition lineage rather than Acme Packet's own naming, don't expect the object prefixes to follow an 'AP-' or 'ACME-' convention — they use the apEnt/ArrowPoint-derived structure instead.