A3COM-HUAWEI-LAG-MIB
The A3COM-HUAWEI-LAG-MIB extends standard SNMP monitoring capabilities for Link Aggregation Control Protocol (LACP) sessions on Huawei and 3Com network switches, exposing specific metrics for LACP partner system identifiers, port aggregation states, and aggregation group operational parameters.
Imported Objects
Objects
26 total| Object Name |
|---|
hwLAGLACP extend MIB. MODULE-IDENTITY .1.3.6.1.4.1.2011.5.25.25 |
hwLAGMibObjects OBJECT IDENTIFIER .1.3.6.1.4.1.2011.5.25.25.1 |
hwAggLinkTableA table of aggregate link objects. SEQUENCE OF HwAggLinkEntry .1.3.6.1.4.1.2011.5.25.25.1.1 |
hwAggLinkEntryEntry of table. HwAggLinkEntry .1.3.6.1.4.1.2011.5.25.25.1.1.1 |
hwAggLinkNumberThe serial number of aggregation group.ro Integer32 .1.3.6.1.4.1.2011.5.25.25.1.1.1.1 |
hwAggLinkNameAggregation name.rw DisplayString .1.3.6.1.4.1.2011.5.25.25.1.1.1.2 |
hwAggLinkModeType of aggregation.
manual: Manual aggregation, no LACP.
static: Membership specified by user, LACP is
used to validate.
dynamic: Completely dynamic aggregation detected
by LACP.rw Enumeration .1.3.6.1.4.1.2011.5.25.25.1.1.1.3 |
hwAggLinkPortListList of ports in this link aggregation group, by bridge port
number. If the mode of the link aggregation group is manual
or static, you can update this list to your
hearts content. However, if the link aggregation group is
dynamic, the system will maintain it. You are not
permitted to set the value of this to
all zeroes.rw PortList (Q-BRIDGE-MIB) .1.3.6.1.4.1.2011.5.25.25.1.1.1.4 |
hwAggLinkStateRowStatus, now support three states:
createAndGo, active, destroy.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.2011.5.25.25.1.1.1.5 |
hwAggPortListSelectedPortsA PortList of physical ports that have been
selected but not attached to this aggregator.
When the bit is set to 1,it means the
corresponding port is in the portlist.ro PortList (Q-BRIDGE-MIB) .1.3.6.1.4.1.2011.5.25.25.1.1.1.6 |
hwAggPortListSamePartnerPortsPortList of physical ports that have the
same Actor SystemID and partner systemID as
this aggregator, but have different actor
and partner keys of aggregator.ro PortList (Q-BRIDGE-MIB) .1.3.6.1.4.1.2011.5.25.25.1.1.1.7 |
hwAggPortTableA table of aggregate port objects. SEQUENCE OF HwAggPortEntry .1.3.6.1.4.1.2011.5.25.25.1.2 |
hwAggPortEntryEntry of table. HwAggPortEntry .1.3.6.1.4.1.2011.5.25.25.1.2.1 |
hwAggPortIndexPort ifindex which is according to RFC1213 MIB.ro Gauge32 .1.3.6.1.4.1.2011.5.25.25.1.2.1.1 |
hwAggPortNotAttachedReasonReason 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.rw Integer32 .1.3.6.1.4.1.2011.5.25.25.1.2.1.2 |
hwAggPortLacpStateControl ports' lacp enble or disable.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.2011.5.25.25.1.2.1.3 |
hwAggPortNotAttachedStringThe string which interprets this
port is selected for an aggregator
but not attached.rw DisplayString .1.3.6.1.4.1.2011.5.25.25.1.2.1.4 |
hwAggResourceAllocationValueThe priority value calculated to decide which
aggregations have first call on the load-sharing
aggregation resources in the hardware. It
depends on the aggregation type and total
speed.ro PortList (Q-BRIDGE-MIB) .1.3.6.1.4.1.2011.5.25.25.1.3 |
hwLAGMibNotifications OBJECT IDENTIFIER .1.3.6.1.4.1.2011.5.25.25.2 |
hwAggSpeedChangedNotificationThis event will be triggered whenever an
aggregation changes its speed. NOTIFICATION-TYPE .1.3.6.1.4.1.2011.5.25.25.2.1 |
hwAggPortInactiveNotificationThis event will be triggered whenever any port
in aggregator is made inactive. NOTIFICATION-TYPE .1.3.6.1.4.1.2011.5.25.25.2.2 |
hwAggPortInactiveNotification2This event will be triggered whenever the port
in aggregator is made inactive. NOTIFICATION-TYPE .1.3.6.1.4.1.2011.5.25.25.2.3 |
hwAggPortActiveNotificationThis event will be triggered whenever the port
in aggregator is made active. NOTIFICATION-TYPE .1.3.6.1.4.1.2011.5.25.25.2.4 |
hwLAGMibConformance OBJECT IDENTIFIER .1.3.6.1.4.1.2011.5.25.25.3 |
hwLAGMibCompliances OBJECT IDENTIFIER .1.3.6.1.4.1.2011.5.25.25.3.1 |
hwLAGMibGroup OBJECT IDENTIFIER .1.3.6.1.4.1.2011.5.25.25.3.2 |
More MIBs from Huawei
Browse all HuaweiMIBs →The HUAWEI-MIB module provides a unified namespace for monitoring and managing generic system resources, interface statistics, and hardware telemetry across Huawei network devices. It serves as the foundational OID repository for retrieving standard operational data, including CPU utilization, memory usage, interface counters, and device status, required for comprehensive network management via SNMP.
Standard SNMP MIB module defining data structures for HUAWEI-SERVER-IBMC-MIB.
The HUAWEI-XPON-MIB module enables Network Management Systems to monitor and configure GPON and EPON optical line terminals and optical network units, specifically tracking PON port status, optical power levels, bandwidth allocation, and subscriber session states.
SNMP MIB module
The HUAWEI-WLAN-CONFIGURATION-MIB facilitates the configuration and monitoring of Huawei Wireless LAN access point parameters, specifically managing AP port link profiles and broadcast suppression settings. This module enables administrators to enforce traffic control policies and optimize wireless network performance by adjusting switch profile associations and limiting broadcast traffic on specific ports.
The HUAWEI-XQoS-MIB enables configuration and real-time monitoring of Class Based QoS parameters on Huawei network devices, specifically tracking traffic classification rules, queue states, and policy enforcement metrics. This module facilitates granular control over bandwidth allocation and packet prioritization by exposing objects for policy definitions, interface queue depths, and dropped packet counters associated with QoS classes.