A3COM-HUAWEI-LAG-MIB

All MIBs › A3COM-HUAWEI-LAG-MIB

Organization: Hangzhou H3C Tech. Co., Ltd.

Last Updated: 2003-10-09

Category: Network Interfaces, Vendor: H3C/HH3C

Description: Manages Link Aggregation Group (LAG/LACP) bundle configuration and member-port statistics on H3C switches.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is A3COM-HUAWEI-LAG-MIB?

A3COM-HUAWEI-LAG-MIB is a joint 3Com/Huawei ('A3COM-HUAWEI', reflecting the former H3C joint venture) enterprise MIB that extends standard link aggregation with vendor-specific LACP objects for H3C/3Com-heritage switches. Per its short description it exposes Link Aggregation Group (LAG) bundle configuration and per-member-port statistics. It is relevant to interface hardware status monitoring: LACP member-port state and per-port statistics reveal whether every physical port in an aggregated bundle is actively passing traffic, helping detect a failed or flapping member link that would otherwise silently reduce the LAG's available bandwidth. The module is explicitly described as an 'LACP extend MIB,' indicating it builds vendor-specific detail on top of the standard IEEE 802.3ad/IETF LAG-MIB conventions. It's deployed on H3C/3Com/Huawei-heritage enterprise switches wherever link aggregation (LACP) is configured between switches or to servers. Engineers can download the A3COM-HUAWEI-LAG-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in A3COM-HUAWEI-LAG-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

H3C/3Com/Huawei-heritage enterprise switch

Monitoring Examples

No specific object or table names were provided in sample_objects for this module, so a concrete example can't cite real leaf names directly; based on the module description ('LACP extend MIB'), the expected use is polling per-port LACP member statistics to confirm every physical port in a LAG bundle remains actively aggregated, and to detect a port that has dropped out of the bundle.

What Can Be Monitored

LAG bundle configuration
LACP member port status
per-port aggregation statistics

Imported Objects

From A3COM-HUAWEI-OID-MIB

huaweiDatacomm	OBJECT-IDENTITY
huaweiMgmt	OBJECT-IDENTITY

From Q-BRIDGE-MIB

PortList

From SNMPv2-CONF

MODULE-COMPLIANCE
NOTIFICATION-GROUP
OBJECT-GROUP

From SNMPv2-SMI

Gauge32
Integer32
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE

From SNMPv2-TC

DisplayString
RowStatus
TEXTUAL-CONVENTION
TruthValue

OIDs

OID symbolic	OID numeric	Type	Access	Description
hwLAG	1.3.6.1.4.1.43.45.1.5.25.25			LACP extend MIB.
hwLAGMibObjects	1.3.6.1.4.1.43.45.1.5.25.25.1
hwAggLinkTable	1.3.6.1.4.1.43.45.1.5.25.25.1.1		not-accessible	A table of aggregate link objects.
hwAggLinkEntry	1.3.6.1.4.1.43.45.1.5.25.25.1.1.1		not-accessible	Entry of table.
I32 hwAggLinkNumber	1.3.6.1.4.1.43.45.1.5.25.25.1.1.1.1	Integer32	accessible-for-notify	The serial number of aggregation group.
STR hwAggLinkName	1.3.6.1.4.1.43.45.1.5.25.25.1.1.1.2	DisplayString	read-create	Aggregation name.
INT hwAggLinkMode	1.3.6.1.4.1.43.45.1.5.25.25.1.1.1.3	INTEGER	read-create	Type of aggregation. manual: Manual aggregation, no LACP. static: Membership specified by user, LACP is used to validate. dynamic: Completely dynamic aggregation detected by LACP.
POR hwAggLinkPortList	1.3.6.1.4.1.43.45.1.5.25.25.1.1.1.4	PortList	read-create	List 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.
ROW hwAggLinkState	1.3.6.1.4.1.43.45.1.5.25.25.1.1.1.5	RowStatus	read-create	RowStatus, now support three states: createAndGo, active, destroy.
POR hwAggPortListSelectedPorts	1.3.6.1.4.1.43.45.1.5.25.25.1.1.1.6	PortList	read-only	A 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.
POR hwAggPortListSamePartnerPorts	1.3.6.1.4.1.43.45.1.5.25.25.1.1.1.7	PortList	read-only	PortList of physical ports that have the same Actor SystemID and partner systemID as this aggregator, but have different actor and partner keys of aggregator.
hwAggPortTable	1.3.6.1.4.1.43.45.1.5.25.25.1.2		not-accessible	A table of aggregate port objects.
hwAggPortEntry	1.3.6.1.4.1.43.45.1.5.25.25.1.2.1		not-accessible	Entry of table.
G32 hwAggPortIndex	1.3.6.1.4.1.43.45.1.5.25.25.1.2.1.1	Gauge32	accessible-for-notify	Port ifindex which is according to RFC1213 MIB.
I32 hwAggPortNotAttachedReason	1.3.6.1.4.1.43.45.1.5.25.25.1.2.1.2	Integer32	read-write	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.
T/F hwAggPortLacpState	1.3.6.1.4.1.43.45.1.5.25.25.1.2.1.3	TruthValue	read-write	Control ports' lacp enble or disable.
STR hwAggPortNotAttachedString	1.3.6.1.4.1.43.45.1.5.25.25.1.2.1.4	DisplayString	read-write	The string which interprets this port is selected for an aggregator but not attached.
POR hwAggResourceAllocationValue	1.3.6.1.4.1.43.45.1.5.25.25.1.3	PortList	read-only	The 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.
hwLAGMibNotifications	1.3.6.1.4.1.43.45.1.5.25.25.2
NTF hwAggSpeedChangedNotification	1.3.6.1.4.1.43.45.1.5.25.25.2.1			This event will be triggered whenever an aggregation changes its speed.
NTF hwAggPortInactiveNotification	1.3.6.1.4.1.43.45.1.5.25.25.2.2			This event will be triggered whenever any port in aggregator is made inactive.
NTF hwAggPortInactiveNotification2	1.3.6.1.4.1.43.45.1.5.25.25.2.3			This event will be triggered whenever the port in aggregator is made inactive.
NTF hwAggPortActiveNotification	1.3.6.1.4.1.43.45.1.5.25.25.2.4			This event will be triggered whenever the port in aggregator is made active.
hwLAGMibConformance	1.3.6.1.4.1.43.45.1.5.25.25.3
hwLAGMibCompliances	1.3.6.1.4.1.43.45.1.5.25.25.3.1
hwLAGMibCompliance	1.3.6.1.4.1.43.45.1.5.25.25.3.1.1			The compliance statement for SNMP entities which implement the Lag MIB.
hwLAGMibGroup	1.3.6.1.4.1.43.45.1.5.25.25.3.2
hwLAGMibObjectGroup	1.3.6.1.4.1.43.45.1.5.25.25.3.2.1			The collection of objects which are used to represent LAG objects.
hwLAGMibNotificationGroup	1.3.6.1.4.1.43.45.1.5.25.25.3.2.2			The collection of objects which are used to represent notifications.

RFC description

Management module for Link Aggregation Group (LAG) configuration and monitoring on 3Com and Huawei networking devices. Enables SNMP management of multi-port logical connections.

Start monitoring H3C/3Com/Huawei enterprise switches with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download A3COM-HUAWEI-LAG-MIB

What Is A3COM-HUAWEI-LAG-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description