All MIBs › ACMEPACKET-ENTITY-VENDORTYPE-OID-MIB
Organization: Acme Packet, Inc.
Last Updated: 2004-02-12
Category: Telephony and VoIP, Vendor: Acme Packet
Description: Defines vendor-specific entity type OIDs for Oracle/ACME Packet Session Border Controller hardware components and 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 ACMEPACKET-ENTITY-VENDORTYPE-OID-MIB?
ACMEPACKET-ENTITY-VENDORTYPE-OID-MIB is a vendor-type OID registry for Oracle/Acme Packet Session Border Controller (SBC) hardware, defining the object identifiers used to uniquely identify physical component types (chassis, modules, etc.) in the standard ENTITY-MIB's entPhysicalTable. It does not define its own runtime data objects; instead it supplies the enumerated identity values that the ENTITY-MIB references. Its role in monitoring is indirect: it enables an NMS to translate an entPhysicalVendorType OID reported by ENTITY-MIB into a human-readable hardware component type (e.g., a specific chassis variant), supporting hardware inventory rather than exposing status or counters itself. It has an explicit and direct dependency on the standard ENTITY-MIB, since its entire purpose is to populate that MIB's vendor-type field. It is deployed wherever Acme Packet/Oracle SBC hardware inventory needs to be identified precisely via SNMP, typically alongside standard ENTITY-MIB polling in service-provider or enterprise SBC deployments. Network engineers evaluating or troubleshooting this functionality can download the ACMEPACKET-ENTITY-VENDORTYPE-OID-MIB file directly to load it into their MIB browser.
IPNetwork Monitor allows you to monitor SNMP objects defined in ACMEPACKET-ENTITY-VENDORTYPE-OID-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
- Oracle/Acme Packet Session Border Controller
Monitoring Examples
This module is an OID registry rather than a source of runtime data — it defines identifier constants like apevChassis, apevChassisUnknown, and apevChassisSD used to populate entPhysicalVendorType in the standard ENTITY-MIB. There is no realistic monitoring scenario to describe here since it contains no pollable counters or status objects of its own; an NMS would only use these OIDs to label hardware inventory entries reported by ENTITY-MIB.
Imported Objects
From ACMEPACKET-SMI
| acmepacketModules | OBJECT-IDENTITY |
From SNMPv2-SMI
| MODULE-IDENTITY |
OIDs
RFC description
Defines object identifier assignments for Acme Packet physical components for identification in ENTITY-MIB tables.
Start monitoring Oracle Acme Packet SBCs 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.