IF-INVERTED-STACK-MIB
AI MIB Summary
The IF-INVERTED-STACK-MIB enables monitoring of hierarchical interface sub-layer relationships by exposing the Inverted Stack Table, which maps physical interfaces to their constituent logical or virtual sub-interfaces. This structure allows network management systems to track the operational status, configuration, and traffic statistics of nested interface layers that are not directly represented in the standard IF-MIB.
The MIB module which provides the Inverted Stack Table for interface sub-layers.
Main OID:
ifInvertedStackMIB.1.3.6.1.2.1.77
10
Objects
Active
Status
4
Dependencies
Imported Objects
Objects
10 total| Object Name |
|---|
ifInvertedStackMIBThe MIB module which provides the Inverted Stack Table for interface sub-layers. MODULE-IDENTITY .1.3.6.1.2.1.77 |
ifInvMIBObjects OBJECT IDENTIFIER .1.3.6.1.2.1.77.1 |
ifInvStackTableA table containing information on the relationships between the multiple sub-layers of network interfaces. In particular, it contains information on which sub-layers run 'underneath' which other sub-layers, where each sub-layer corresponds to a conceptual row in the ifTable. For example, when the sub-layer with ifIndex value x runs underneath the sub-layer with ifIndex value y, then this table contains: ifInvStackStatus.x.y=active For each ifIndex value, z, which identifies an active interface, there are always at least two instantiated rows in this table associated with z. For one of these rows, z is the value of ifStackHigherLayer; for the other, z is the value of ifStackLowerLayer. (If z is not involved in multiplexing, then these are the only two rows associated with z.) For example, two rows exist even for an interface which has no others stacked on top or below it: ifInvStackStatus.z.0=active ifInvStackStatus.0.z=active This table contains exactly the same number of rows as the ifStackTable, but the rows appear in a different order. SEQUENCE OF IfInvStackEntry .1.3.6.1.2.1.77.1.1 |
ifInvStackEntryInformation on a particular relationship between two sub- layers, specifying that one sub-layer runs underneath the other sub-layer. Each sub-layer corresponds to a conceptual row in the ifTable. IfInvStackEntry .1.3.6.1.2.1.77.1.1.1 |
ifInvStackStatusThe status of the relationship between two sub-layers. An instance of this object exists for each instance of the ifStackStatus object, and vice versa. For example, if the variable ifStackStatus.H.L exists, then the variable ifInvStackStatus.L.H must also exist, and vice versa. In addition, the two variables always have the same value. However, unlike ifStackStatus, the ifInvStackStatus object is NOT write-able. A network management application wishing to change a relationship between sub-layers H and L cannot do so by modifying the value of ifInvStackStatus.L.H, but must instead modify the value of ifStackStatus.H.L. After the ifStackTable is modified, the change will be reflected in this table.ro RowStatus (SNMPv2-TC) .1.3.6.1.2.1.77.1.1.1.1 |
ifInvConformance OBJECT IDENTIFIER .1.3.6.1.2.1.77.1.2 |
ifInvGroups OBJECT IDENTIFIER .1.3.6.1.2.1.77.1.2.1 |
ifInvStackGroupA collection of objects providing inverted information on the layering of MIB-II interfaces. Unknown .1.3.6.1.2.1.77.1.2.1.1 |
ifInvCompliances OBJECT IDENTIFIER .1.3.6.1.2.1.77.1.2.2 |
ifInvComplianceThe compliance statement for SNMP entities which provide inverted information on the layering of network interfaces. Unknown .1.3.6.1.2.1.77.1.2.2.1 |