IF-CAP-STACK-MIB

File: IF-CAP-STACK-MIB.mib (10103 bytes)

Imported modules

SNMPv2-SMI SNMPv2-TC SNMPv2-CONF
IF-MIB IF-INVERTED-STACK-MIB

Imported symbols

MODULE-IDENTITY OBJECT-TYPE mib-2
TruthValue MODULE-COMPLIANCE OBJECT-GROUP
ifStackGroup2 ifStackHigherLayer ifStackLowerLayer
ifInvStackGroup

Defined Types

IfCapStackEntry  
SEQUENCE    
  ifCapStackStatus TruthValue

IfInvCapStackEntry  
SEQUENCE    
  ifInvCapStackStatus TruthValue

Defined Values

ifCapStackMIB 1.3.6.1.2.1.166
The objects in this MIB module are used to describe cross-connect capabilities of stacked (layered) interfaces, complementing ifStackTable and ifInvStackTable defined in IF-MIB and IF-INVERTED-STACK-MIB, respectively. Copyright (C) The IETF Trust (2007). This version of this MIB module is part of RFC 5066; see the RFC itself for full legal notices.
MODULE-IDENTITY    

ifCapStackObjects 1.3.6.1.2.1.166.1
OBJECT IDENTIFIER    

ifCapStackConformance 1.3.6.1.2.1.166.2
OBJECT IDENTIFIER    

ifCapStackTable 1.3.6.1.2.1.166.1.1
This table, modeled after ifStackTable from IF-MIB, contains information on the possible 'on-top-of' relationships between the multiple sub-layers of network interfaces (as opposed to actual relationships described in ifStackTable). In particular, it contains information on which sub-layers MAY possibly run 'on top of' which other sub-layers, as determined by cross-connect capability of the device, where each sub-layer corresponds to a conceptual row in the ifTable. For example, when the sub-layer with ifIndex value x can be connected to run on top of the sub-layer with ifIndex value y, then this table contains: ifCapStackStatus.x.y=true The ifCapStackStatus.x.y row does not exist if it is impossible to connect between the sub-layers x and y. Note that for most stacked interfaces (e.g., 2BASE-TL) there's always at least one higher-level interface (e.g., PCS port) for each lower-level interface (e.g., PME) and at least one lower-level interface for each higher-level interface, that is, there is at least a single row with a 'true' status for any such existing value of x or y. This table is read-only as it describes device capabilities.
OBJECT-TYPE    
  SEQUENCE OF  
    IfCapStackEntry

ifCapStackEntry 1.3.6.1.2.1.166.1.1.1
Information on a particular relationship between two sub-layers, specifying that one sub-layer MAY possibly run on 'top' of the other sub-layer. Each sub-layer corresponds to a conceptual row in the ifTable (interface index for lower and higher layer, respectively).
OBJECT-TYPE    
  IfCapStackEntry  

ifCapStackStatus 1.3.6.1.2.1.166.1.1.1.1
The status of the 'cross-connect capability' relationship between two sub-layers. The following values can be returned: true(1) - indicates that the sub-layer interface, identified by the ifStackLowerLayer MAY be connected to run 'below' the sub-layer interface, identified by the ifStackHigherLayer index. false(2) - the sub-layer interfaces cannot be connected temporarily due to unavailability of the interface(s), e.g., one of the interfaces is located on an absent pluggable module. Note that lower-layer interface availability per higher-layer, indicated by the value of 'true', can be constrained by other parameters, for example, by the aggregation capacity of a higher-layer interface or by the lower-layer interface in question being already connected to another higher-layer interface. In order to ensure that a particular sub-layer can be connected to another sub-layer, all respective objects (e.g., ifCapStackTable, ifStackTable, and efmCuPAFCapacity for EFMCu interfaces) SHALL be inspected. This object is read-only, unlike ifStackStatus, as it describes a cross-connect capability.
OBJECT-TYPE    
  TruthValue  

ifInvCapStackTable 1.3.6.1.2.1.166.1.2
A table containing information on the possible relationships between the multiple sub-layers of network interfaces. This table, modeled after ifInvStackTable from IF-INVERTED-STACK-MIB, is an inverse of the ifCapStackTable defined in this MIB module. In particular, this table contains information on which sub-layers MAY 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 MAY be connected to run underneath the sub-layer with ifIndex value y, then this table contains: ifInvCapStackStatus.x.y=true This table contains exactly the same number of rows as the ifCapStackTable, but the rows appear in a different order. This table is read-only as it describes a cross-connect capability.
OBJECT-TYPE    
  SEQUENCE OF  
    IfInvCapStackEntry

ifInvCapStackEntry 1.3.6.1.2.1.166.1.2.1
Information on a particular relationship between two sub- layers, specifying that one sub-layer MAY run underneath the other sub-layer. Each sub-layer corresponds to a conceptual row in the ifTable.
OBJECT-TYPE    
  IfInvCapStackEntry  

ifInvCapStackStatus 1.3.6.1.2.1.166.1.2.1.1
The status of the possible 'cross-connect capability' relationship between two sub-layers. An instance of this object exists for each instance of the ifCapStackStatus object, and vice versa. For example, if the variable ifCapStackStatus.H.L exists, then the variable ifInvCapStackStatus.L.H must also exist, and vice versa. In addition, the two variables always have the same value. The ifInvCapStackStatus object is read-only, as it describes a cross-connect capability.
OBJECT-TYPE    
  TruthValue  

ifCapStackGroups 1.3.6.1.2.1.166.2.1
OBJECT IDENTIFIER    

ifCapStackCompliances 1.3.6.1.2.1.166.2.2
OBJECT IDENTIFIER    

ifCapStackGroup 1.3.6.1.2.1.166.2.1.1
A collection of objects providing information on the cross-connect capability of multi-layer (stacked) network interfaces.
OBJECT-GROUP    

ifCapStackCompliance 1.3.6.1.2.1.166.2.2.1
Support for the false(2) value is OPTIONAL for implementations supporting pluggable interfaces.
MODULE-COMPLIANCE    
  ifCapStackStatus TruthValue true(1)
  ifInvCapStackStatus TruthValue true(1)