HPN-ICF-LAG-MIB :: hpnicfAggPortNotAttachedReason

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › HPN-ICF-LAG-MIB › hpnicfAggPortNotAttachedReason

hpnicfAggPortNotAttachedReason

Module: HPN-ICF-LAG-MIB

OID (symbolic): HPN-ICF-LAG-MIB::hpnicfAggPortNotAttachedReason

OID (numeric): 1.3.6.1.4.1.11.2.14.11.15.8.25.1.2.1.2

Node type: OBJECT-TYPE

Type: Integer32

Access: read-write

Description: Reason why this port is selected for an aggregator but not attached, 0: The port is attached to this aggregator. 1: The current number of active ports has reached the upper limit. 2: All aggregation resources are already in-use. 3: The port's configuration is improper for being attached. 4: The port's partner is improper for being attached. 5: The number of current active ports has not reached the lower limit. 6: The port's physical state (down) is improper for being attached. 7: The port is not selected for an aggregator. 8: The port's hardware restriction is improper for being attached. 9: The port's speed is improper for being attached. 10: The port's duplex mode is improper for being attached.

What is hpnicfAggPortNotAttachedReason?

This read-write integer, from 0 to 10, reports why a port selected for an aggregator has not been attached, with values covering reasons such as reaching the maximum active-port limit(1), exhausted aggregation resources(2), improper port configuration(3), improper partner configuration(4), not reaching the minimum active-port count(5), port physically down(6), not selected(7), hardware restriction(8), improper speed(9), or improper duplex mode(10); a value of 0 means the port is actually attached. Admins read this to quickly diagnose why a specific port failed to join its intended LAG. For example, a value of 9 tells the admin the port's speed setting is incompatible with the aggregation group and needs to be corrected.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.11.2.14.11.15.8.25.1.2.1.2
snmpwalk -v2c -c public <target> HPN-ICF-LAG-MIB::hpnicfAggPortNotAttachedReason

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.11.2.14.11.15.8.25.1.2.1.2.1
snmpget -v2c -c public <target> HPN-ICF-LAG-MIB::hpnicfAggPortNotAttachedReason.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.4.1.11.2.14.11.15.8.25.1.2.1.2.1 i <value>

Start monitoring HP/H3C Comware-based switch (Link Aggregation Group/LACP extensions) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the HPN-ICF-LAG-MIB::hpnicfAggPortNotAttachedReason OID value, configure state conditions and alerts, and monitor any HP/H3C Comware-based switch (Link Aggregation Group/LACP extensions) from a single console.

OID Breakdown

Upper-level ancestors (12 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.11hpCLJ8500-MIB
1.3.6.1.4.1.11.2nmCLJ8500-MIB
1.3.6.1.4.1.11.2.14icfCONFIG-MIB
1.3.6.1.4.1.11.2.14.11hpicfObjectsCONFIG-MIB
1.3.6.1.4.1.11.2.14.11.15hpnicfHPN-ICF-OID-MIB
1.3.6.1.4.1.11.2.14.11.15.8hpnicfRhwHPN-ICF-OID-MIB
Numeric OIDNameModule
1.3.6.1.4.1.11.2.14.11.15.8.25hpnicfLAGHPN-ICF-LAG-MIB
1.3.6.1.4.1.11.2.14.11.15.8.25.1hpnicfLAGMibObjectsHPN-ICF-LAG-MIB
1.3.6.1.4.1.11.2.14.11.15.8.25.1.2hpnicfAggPortTableHPN-ICF-LAG-MIB
1.3.6.1.4.1.11.2.14.11.15.8.25.1.2.1hpnicfAggPortEntryHPN-ICF-LAG-MIB
1.3.6.1.4.1.11.2.14.11.15.8.25.1.2.1.2hpnicfAggPortNotAttachedReasonHPN-ICF-LAG-MIB