CISCO-MPOA-EXT-MIB
The CISCO-MPOA-EXT-MIB monitors Cisco ATM network devices to retrieve MPOA shortcut virtual circuit (VCC) statistics and map Multiprotocol Over ATM (MPOA) entities, specifically MPOA Clients (MPC) and Servers (MPS), to their underlying physical interfaces.
Imported Objects
Objects
23 total| Object Name |
|---|
ciscoMpoaExtMIBThis MIB module is a Cisco extension to the ATM
Forum's MPOA MIB. This MIB module consists of object
groups to retrieve information about MPOA shortcut
VCCs and to bind MPOA entities (MPC & MPS) to physical
interfaces. MODULE-IDENTITY .1.3.6.1.4.1.9.9.99999 |
ciscoMpoaExtMIBObjects OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.99999.1 |
cMpcExtShortcutVCC OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.99999.1.1 |
cMpcExtShortcutVCCTableAn extension to the mpcConfig table in the
MPOA-MIB. This table identifies the VCI and VPI of
each shortcut that is setup by an MPC.
A shortcut is a VCC that is setup between the Ingress
and Egress MPC. SEQUENCE OF CMpcExtShortcutVCCEntry .1.3.6.1.4.1.9.9.99999.1.1.1 |
cMpcExtShortcutVCCEntryEntries in the table for the shortcut VCCs setup by an MPC. CMpcExtShortcutVCCEntry .1.3.6.1.4.1.9.9.99999.1.1.1.1 |
cmpcSCVpiThe VPI of the shortcut VCC setup by the MPC specified by MPC
index. The destination of the shortcut VCC is specified by
cmpcDestAtmAddr. VpiInteger .1.3.6.1.4.1.9.9.99999.1.1.1.1.1 |
cmpcSCVciThe VCI of the shortcut VCC setup by the MPC specified by the
MPC index. The destination of the shortcut VCC is specified by
cmpcDestAtmAddr. VciInteger .1.3.6.1.4.1.9.9.99999.1.1.1.1.2 |
cmpcDestAtmAddrThe ATM address of the destination of this shortcut VCC.ro AtmAddress .1.3.6.1.4.1.9.9.99999.1.1.1.1.3 |
cMpcInterface OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.99999.1.2 |
cMpcInterfaceMappingTableTable that contains information about the MPC <
interface binding. SEQUENCE OF CMpcInterfaceMappingEntry .1.3.6.1.4.1.9.9.99999.1.2.1 |
cMpcInterfaceMappingEntryEach row in this table specifies the interface (by ifIndex)
to which an MPC (specified by mpcIndex) is bound.
Creation of an MPC does not create an entry in this table.
After successfully creating an MPC, the MPC has to be bound to
an interface in order to create an entry in this table. CMpcInterfaceMappingEntry .1.3.6.1.4.1.9.9.99999.1.2.1.1 |
cMpcInterfaceMappingIndexThe Interface (specified by the cMpcInterfaceMappingIndex)
to which the MPS (specified by mpcIndex) is bound to.
This interface has to be an ATM physical interface.rw InterfaceIndex (IF-MIB) .1.3.6.1.4.1.9.9.99999.1.2.1.1.1 |
cMpcInterfaceMappingRowStatusRow status of the row in the mapping table.
Specifying a 'valid' value for the cMpcInterfaceMappingIndex
(interface index of an ATM physical interface) in the set
operation, along with a value of 4 (createAndGo) for the
cMpcInterfaceMappingRowStatus, will bind the MPC specified by mpcIndex
to the specified physical interface and create a row entry in
this table.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.9.9.99999.1.2.1.1.2 |
cMpsInterface OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.99999.1.3 |
cMpsInterfaceMappingTableTable that contains information about the MPS <
interface binding. SEQUENCE OF CMpsInterfaceMappingEntry .1.3.6.1.4.1.9.9.99999.1.3.1 |
cMpsInterfaceMappingEntryEach row in this table specifies the interface (by ifIndex)
to which an MPS (specified by mpsIndex) is bound.
Creation of an MPS does not create an entry in this table.
After successfully creating an MPS, the MPS has to be bound to
an interface in order to create an entry in this table. CMpsInterfaceMappingEntry .1.3.6.1.4.1.9.9.99999.1.3.1.1 |
cMpsInterfaceMappingIndexThe Interface (specified by the cMpsInterfaceMappingIndex)
to which the MPS (specified by mpsIndex) is bound to.
This interface has to be an ATM physical interface.rw InterfaceIndex (IF-MIB) .1.3.6.1.4.1.9.9.99999.1.3.1.1.1 |
cMpsInterfaceMappingRowStatusRow status of the row in the mapping table.
Specifying a 'valid' value for the cMpsInterfaceMappingIndex
(interface index of an ATM physical interface) in the set
operation, along with a value of 4 (createAndGo) for the
cMpsInterfaceMappingRowStatus, will bind the MPS specified by mpsIndex
to the specified physical interface and create a row entry in
this table.
Similarly, specifying a value of 6 (destroy) for the
cMpsInterfaceMappingRowStatus, along with the mpsIndex of the
MPS, will detach the specified MPS from the physical
interface(i.e. if it is already attached).rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.9.9.99999.1.3.1.1.2 |
ciscoMpoaExtMIBNotificationPrefix OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.99999.2 |
ciscoMpoaExtMIBNotifications OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.99999.2.0 |
ciscoMpoaExtMIBConformance OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.99999.3 |
ciscoMpoaExtMIBCompliances OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.99999.3.1 |
ciscoMpoaExtMIBGroups OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.99999.3.2 |
More MIBs from Cisco
Browse all CiscoMIBs →The CISCO-ENTITY-VENDORTYPE-OID-MIB maps Cisco-specific hardware component identifiers to the ENTITY-MIB's entPhysicalTable, enabling precise differentiation of physical device types such as line cards, power supplies, and fans within Cisco infrastructure. This mapping ensures that SNMP management systems can accurately correlate physical inventory entries with vendor-specific component definitions for accurate device discovery and monitoring.
The CISCO-UNIFIED-COMPUTING-EQUIPMENT-MIB provides SNMP-based monitoring and management of Cisco Unified Computing System (UCS) hardware components, including chassis, blades, fabric interconnects, and power supplies. It exposes critical operational metrics such as device status, port states, temperature readings, fan speeds, and power consumption data for infrastructure health assessment.
The CISCO-UNIFIED-COMPUTING-ADAPTOR-MIB enables SNMP-based monitoring and management of physical and virtual network adapter interfaces, including link status, traffic counters, error statistics, and port configuration parameters, within the Cisco Unified Computing System (UCS) fabric interconnects and blade servers.
The CISCO-UNIFIED-COMPUTING-TC-MIB module defines standard textual conventions and data type definitions required for monitoring Cisco Unified Computing System (UCS) hardware components, including server blades, fabric interconnects, and chassis resources. These definitions enable consistent interpretation of specific UCS metrics such as power supply status, fan speeds, thermal readings, and port utilization across SNMP management applications.
The CISCO-UNIFIED-COMPUTING-FABRIC-MIB enables SNMP-based monitoring and management of the Cisco UCS Fabric Interconnects and associated fabric switching infrastructure, exposing metrics for port states, link utilization, error counters, and fabric topology status. It facilitates granular visibility into the physical and logical fabric layers, including uplink/downlink interfaces, VLAN configurations, and fabric failover conditions within the unified computing environment.
The STARENT-MIB module provides SNMP management and monitoring capabilities for Cisco ASR 5000 and ASR 5500 multimedia core platforms, specifically exposing metrics related to 2G/3G/4G and WiFi subscriber sessions, inline service states, and carrier-class high-availability status.