1 IF-INVERTED-STACK-MIB DEFINITIONS ::= BEGIN
4 MODULE-IDENTITY, OBJECT-TYPE, mib-2 FROM SNMPv2-SMI
5 RowStatus FROM SNMPv2-TC
6 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF
8 ifStackHigherLayer, ifStackLowerLayer FROM IF-MIB;
10 ifInvertedStackMIB MODULE-IDENTITY
11 LAST-UPDATED "200006140000Z"
12 ORGANIZATION "IETF Interfaces MIB Working Group"
17 San Jose, CA 95134-1706
23 "The MIB module which provides the Inverted Stack Table for
24 interface sub-layers."
25 REVISION "200006140000Z"
27 "Initial revision, published as RFC 2864"
30 ifInvMIBObjects OBJECT IDENTIFIER ::= { ifInvertedStackMIB 1 }
33 -- The Inverted Interface Stack Group
36 ifInvStackTable OBJECT-TYPE
37 SYNTAX SEQUENCE OF IfInvStackEntry
38 MAX-ACCESS not-accessible
41 "A table containing information on the relationships between
43 the multiple sub-layers of network interfaces. In
44 particular, it contains information on which sub-layers run
45 'underneath' which other sub-layers, where each sub-layer
46 corresponds to a conceptual row in the ifTable. For
47 example, when the sub-layer with ifIndex value x runs
48 underneath the sub-layer with ifIndex value y, then this
51 ifInvStackStatus.x.y=active
53 For each ifIndex value, z, which identifies an active
54 interface, there are always at least two instantiated rows
55 in this table associated with z. For one of these rows, z
56 is the value of ifStackHigherLayer; for the other, z is the
57 value of ifStackLowerLayer. (If z is not involved in
58 multiplexing, then these are the only two rows associated
61 For example, two rows exist even for an interface which has
62 no others stacked on top or below it:
64 ifInvStackStatus.z.0=active
65 ifInvStackStatus.0.z=active
67 This table contains exactly the same number of rows as the
68 ifStackTable, but the rows appear in a different order."
70 "ifStackTable of RFC 2863"
71 ::= { ifInvMIBObjects 1 }
73 ifInvStackEntry OBJECT-TYPE
74 SYNTAX IfInvStackEntry
75 MAX-ACCESS not-accessible
78 "Information on a particular relationship between two sub-
79 layers, specifying that one sub-layer runs underneath the
80 other sub-layer. Each sub-layer corresponds to a conceptual
82 INDEX { ifStackLowerLayer, ifStackHigherLayer }
83 ::= { ifInvStackTable 1 }
87 ifInvStackStatus RowStatus
90 ifInvStackStatus OBJECT-TYPE
95 "The status of the relationship between two sub-layers.
97 An instance of this object exists for each instance of the
98 ifStackStatus object, and vice versa. For example, if the
99 variable ifStackStatus.H.L exists, then the variable
100 ifInvStackStatus.L.H must also exist, and vice versa. In
101 addition, the two variables always have the same value.
103 However, unlike ifStackStatus, the ifInvStackStatus object
104 is NOT write-able. A network management application wishing
105 to change a relationship between sub-layers H and L cannot
106 do so by modifying the value of ifInvStackStatus.L.H, but
107 must instead modify the value of ifStackStatus.H.L. After
108 the ifStackTable is modified, the change will be reflected
110 ::= { ifInvStackEntry 1 }
112 -- conformance information
114 ifInvConformance OBJECT IDENTIFIER ::= { ifInvMIBObjects 2 }
116 ifInvGroups OBJECT IDENTIFIER ::= { ifInvConformance 1 }
117 ifInvCompliances OBJECT IDENTIFIER ::= { ifInvConformance 2 }
119 -- compliance statements
121 ifInvCompliance MODULE-COMPLIANCE
124 "The compliance statement for SNMP entities which provide
125 inverted information on the layering of network interfaces."
127 MODULE -- this module
128 MANDATORY-GROUPS { ifInvStackGroup }
130 OBJECT ifInvStackStatus
131 SYNTAX INTEGER { active(1) }
133 "Support is only required for 'active'."
136 MANDATORY-GROUPS { ifStackGroup2 }
137 ::= { ifInvCompliances 1 }
139 -- units of conformance
141 ifInvStackGroup OBJECT-GROUP
142 OBJECTS { ifInvStackStatus }
145 "A collection of objects providing inverted information on
146 the layering of MIB-II interfaces."
147 ::= { ifInvGroups 1 }