All MIBs › IF-CAP-STACK-MIB › ifCapStackStatus
ifCapStackStatus
Module: IF-CAP-STACK-MIB
OID (symbolic): IF-CAP-STACK-MIB::ifCapStackStatus
OID (numeric): 1.3.6.1.2.1.166.1.1.1.1
Node type: OBJECT-TYPE
Type: TruthValue
Access: read-only
Description: 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.
What is ifCapStackStatus?
This read-only TruthValue reports whether a lower-layer network sub-interface is capable of being cross-connected to run beneath a specific higher-layer sub-interface, a capability check distinct from whether they're actually connected right now (which is what the standard ifStackStatus tracks). An administrator or NMS consults this before attempting to build a new interface stacking relationship, since a false value here (for example, because one of the interfaces sits on a currently absent pluggable module) means that particular cross-connect isn't presently possible even though it might be later. For example, a technician trying to stack a VDSL sub-interface under a bonding group interface would check this object first to confirm the hardware actually supports and currently allows that specific pairing before attempting to configure it.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.2.1.166.1.1.1.1 snmpwalk -v2c -c public <target> IF-CAP-STACK-MIB::ifCapStackStatus
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.2.1.166.1.1.1.1.1 snmpget -v2c -c public <target> IF-CAP-STACK-MIB::ifCapStackStatus.1
Start monitoring Vendor-neutral IETF standard, RFC 5066 (layered/multiplexed transport interfaces) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the IF-CAP-STACK-MIB::ifCapStackStatus OID value, configure state conditions and alerts, and monitor any Vendor-neutral IETF standard, RFC 5066 (layered/multiplexed transport interfaces) from a single console.
OID Breakdown
Upper-level ancestors (6 from the standard OID tree / other modules)
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.2 | mgmt | APERTUS-NPG-MIB |
| 1.3.6.1.2.1 | mib_2 | AXON-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.2.1.166 | ifCapStackMIB | IF-CAP-STACK-MIB |
| 1.3.6.1.2.1.166.1 | ifCapStackObjects | IF-CAP-STACK-MIB |
| 1.3.6.1.2.1.166.1.1 | ifCapStackTable | IF-CAP-STACK-MIB |
| 1.3.6.1.2.1.166.1.1.1 | ifCapStackEntry | IF-CAP-STACK-MIB |
| 1.3.6.1.2.1.166.1.1.1.1 | ifCapStackStatus | IF-CAP-STACK-MIB |