HUAWEI-SUPERLAG-MIB

All MIBs › HUAWEI-SUPERLAG-MIB

Organization: Organization.

Last Updated: 2008-10-21

Category: Technology: Link Aggregation, Technology: Stacking, Technology: Switching/L2, Vendor: Huawei

Description: Huawei SuperLAG MIB for managing super link aggregation groups that span multiple chassis in an IRF fabric.

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 HUAWEI-SUPERLAG-MIB?

HUAWEI-SUPERLAG-MIB is a Huawei-proprietary module for managing Super Link Aggregation Groups that span multiple chassis within an IRF (Intelligent Resilient Framework) fabric. It exposes SuperLAG group membership, the list of member ports and their owning chassis/slot, and the aggregation/link state of each cross-chassis member. Its monitoring focus is hardware status: the up/down operational state of each member port within the aggregate reveals when a physical uplink on one chassis has failed, while the aggregate as a whole indicates whether traffic has successfully failed over to remaining links. It builds on standard link-aggregation (IEEE 802.3ad/LACP) concepts and is closely tied to Huawei's IRF stacking framework alongside HUAWEI-STACK-MIB. It is typically deployed in Huawei IRF-based switch fabrics in data center or campus core networks where cross-chassis aggregation provides both extra bandwidth and chassis-level redundancy. Engineers can download the HUAWEI-SUPERLAG-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in HUAWEI-SUPERLAG-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

Huawei IRF fabric switches (data center/core switches)

Monitoring Examples

An admin would poll a SuperLAG member-port table (an hwSuperLagMemberTable/hwSuperLagMemberEntry pattern) for each member's chassis, slot, and link status within the aggregate. A member port switching to a down state on one chassis, while the aggregate itself remains operational, confirms the SuperLAG correctly failed over traffic to the surviving member links without an outage. Tracking aggregate traffic/bandwidth utilization also helps plan capacity across the fabric before any single chassis becomes a bottleneck.

What Can Be Monitored

SuperLAG group/member status
cross-chassis member port link state
aggregate bandwidth utilization
chassis/slot assignment of member ports

Imported Objects

From HUAWEI-MIB

huaweiMgmt

OBJECT-IDENTITY

From SNMPv2-SMI

Counter32
Counter64
Integer32
IpAddress
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE
Unsigned32

From SNMPv2-TC

DisplayString
PhysAddress
RowStatus
TEXTUAL-CONVENTION
TimeStamp
TruthValue

OIDs

OID symbolic	OID numeric	Type	Access	Description
hwDatacomm	1.3.6.1.4.1.2011.5.25
hwSuperLagMIB	1.3.6.1.4.1.2011.5.25.178			Description.
hwSuperLagObjects	1.3.6.1.4.1.2011.5.25.178.1
hwSuperLagTable	1.3.6.1.4.1.2011.5.25.178.1.1		not-accessible	The super LAG table.
hwSuperLagEntry	1.3.6.1.4.1.2011.5.25.178.1.1.1		not-accessible	Super LAG entry.
I32 hwSuperLagId	1.3.6.1.4.1.2011.5.25.178.1.1.1.1	Integer32	not-accessible	The ID of the super LAG, it is the index of the super LAG.
PHY hwSuperLagSystemId	1.3.6.1.4.1.2011.5.25.178.1.1.1.2	PhysAddress	read-only	The system ID of the super LAG, it is a physical address.
I32 hwSuperLagPri	1.3.6.1.4.1.2011.5.25.178.1.1.1.3	Integer32	read-create	The priority of the super LAG. The default is 100.
INT hwSuperLagStatus	1.3.6.1.4.1.2011.5.25.178.1.1.1.4	INTEGER	read-only	The status of the super LAG. 1:initialize 2:backup 3:master
INT hwSuperLagStatusReason	1.3.6.1.4.1.2011.5.25.178.1.1.1.5	INTEGER	read-only	The reason for the super LAG is in the current status. pri(1):Priority calculation timeout(2):Receiving timer timeout bfdDown(3):BFD detected the control link between the PE and peer down peerTimeout(4):Receiving timer of the peer timeout peerBfdDown(5):BFD of the peer detected the control link between the PE and peer down allMemberDown(6):All SuperLagMembers of the superlag down init(7):The initial superlag.
IP hwSuperLagPeerIpAddr	1.3.6.1.4.1.2011.5.25.178.1.1.1.6	IpAddress	read-create	The IP address of the peer super LAG.
IP hwSuperLagSourceIpAddr	1.3.6.1.4.1.2011.5.25.178.1.1.1.7	IpAddress	read-create	The source IP address of the super LAG.
I32 hwSuperLagReceiveFailTimeMultiple	1.3.6.1.4.1.2011.5.25.178.1.1.1.8	Integer32	read-create	The fail time of the super LAG for receiving packets. It is the multiple of sending period.
I32 hwSuperLagSendPeriod	1.3.6.1.4.1.2011.5.25.178.1.1.1.9	Integer32	read-create	The period for sending packets of the super LAG. The unit is 100ms
C64 hwSuperLagPacketReceive	1.3.6.1.4.1.2011.5.25.178.1.1.1.10	Counter64	read-only	The number of the received packets.
C64 hwSuperLagPacketSend	1.3.6.1.4.1.2011.5.25.178.1.1.1.11	Counter64	read-only	The number of the sending packets.
C64 hwSuperLagPacketRecDrop	1.3.6.1.4.1.2011.5.25.178.1.1.1.12	Counter64	read-only	The number of the droped packets when the packets are received.
C64 hwSuperLagPacketSndDrop	1.3.6.1.4.1.2011.5.25.178.1.1.1.13	Counter64	read-only	The number of the droped packets when the packets are send out.
PHY hwSuperLagPeerSystemId	1.3.6.1.4.1.2011.5.25.178.1.1.1.14	PhysAddress	read-only	The system ID of peer super LAG,it is a physical address.
I32 hwSuperLagPeerPri	1.3.6.1.4.1.2011.5.25.178.1.1.1.15	Integer32	read-only	The priority of the peer super LAG.
I32 hwSuperLagPeerReceiveFailTime	1.3.6.1.4.1.2011.5.25.178.1.1.1.16	Integer32	read-only	The fail time of the peer super LAG for receiving packets.The unit is 100ms
INT hwSuperLagSecurityKeyType	1.3.6.1.4.1.2011.5.25.178.1.1.1.17	INTEGER	read-create	The mode of the security key. 1:The simple encrypt mode; 2:The cipher encrypt mode.
OCT hwSuperLagSecurityKey	1.3.6.1.4.1.2011.5.25.178.1.1.1.18	OCTET STRING	read-create	This is the security key. It is must be hex number and the most number is 16. If hwSuperLagSecurityKeyType is simple, you can get the key. If hwSuperLagSecurityKeyType is cipher, the system returns a random character string with 24 bytes.
I32 hwSuperLagBfdSessId	1.3.6.1.4.1.2011.5.25.178.1.1.1.19	Integer32	read-create	The ID of BFD session which is bind to a super LAG. When the status of the link is changed, BFD will notify super LAG.
I32 hwSuperLagResetCounter	1.3.6.1.4.1.2011.5.25.178.1.1.1.20	Integer32	read-create	Reset hwSuperLagPacketReceive,hwSuperLagPacketSend,hwSuperLagPacketRecDrop,hwSuperLagPacketSndDrop.
ROW hwSuperLagRowStatus	1.3.6.1.4.1.2011.5.25.178.1.1.1.50	RowStatus	read-create	Current operation status of the row.Used to manage the creation and deletion of conceptual rows.
hwSuperLagMemberTable	1.3.6.1.4.1.2011.5.25.178.1.2		not-accessible	The member table of a super LAG.
hwSuperLagMemberEntry	1.3.6.1.4.1.2011.5.25.178.1.2.1		not-accessible	Member Entry.
I32 hwSuperLagMemberParentSuperLagId	1.3.6.1.4.1.2011.5.25.178.1.2.1.1	Integer32	not-accessible	The ID of the super LAG which the member is belonged to.
I32 hwSuperLagMemberType	1.3.6.1.4.1.2011.5.25.178.1.2.1.2	Integer32	not-accessible	The type of the member. Now is EthTrunk only. 1:EthTrunk
U32 hwSuperLagMemberId	1.3.6.1.4.1.2011.5.25.178.1.2.1.3	Unsigned32	not-accessible	The ID of the member.
INT hwSuperLagMemberStatus	1.3.6.1.4.1.2011.5.25.178.1.2.1.4	INTEGER	read-only	The member status. 1:backup 2:master.
INT hwSuperLagMemberStatusReason	1.3.6.1.4.1.2011.5.25.178.1.2.1.5	INTEGER	read-only	The reason for the member is in the current status. forceBackup(1):The work mode of the member is force-backup forceMaster(2):The work mode of the member is force-master suplagInit(3):The work mode of the member is auto, the status of parent super LAG is INITIALIZE suplagBackup(4):The work mode of the member is auto, the status of parent super LAG is BACKUP suplagMaster(5):The work mode of the member is auto, the status of parent super LAG is MASTER peerMemberDown(6):The status of the members belonged to the peer super LAG is down peerMemberUp(7):The status of the members belonged to the peer super LAG is up
INT hwSuperLagMemberWorkMode	1.3.6.1.4.1.2011.5.25.178.1.2.1.6	INTEGER	read-create	The work mode of the member. 1:auto 2:forceBackup 3:forceMaster
INT hwSuperLagMemberLocaPhylLinkStatus	1.3.6.1.4.1.2011.5.25.178.1.2.1.7	INTEGER	read-only	The local physical link status of the member. 1:up 2:down
ROW hwSuperLagMemberRowStatus	1.3.6.1.4.1.2011.5.25.178.1.2.1.50	RowStatus	read-create	Current operation status of the row.Used to manage the creation and deletion of conceptual rows.
hwSuperLagTraps	1.3.6.1.4.1.2011.5.25.178.2
NTF hwSuperLagStatusChange	1.3.6.1.4.1.2011.5.25.178.2.1			The event is generated when the status of the super LAG is changed or the status reason of the super LAG is changed.
NTF hwSuperLagMemberStatusChange	1.3.6.1.4.1.2011.5.25.178.2.2			The event is generated when the status of the memeber is changed or the status reason of the memeber is changed.
hwSuperLagConformance	1.3.6.1.4.1.2011.5.25.178.3
hwSuperLagCompliances	1.3.6.1.4.1.2011.5.25.178.3.1
hwSuperLagFullCompliance	1.3.6.1.4.1.2011.5.25.178.3.1.1			Description.
hwSuperLagGroups	1.3.6.1.4.1.2011.5.25.178.3.2
hwSuperLagGroup	1.3.6.1.4.1.2011.5.25.178.3.2.1			Description.
hwSuperLagMemberGroup	1.3.6.1.4.1.2011.5.25.178.3.2.2			Description.
hwSuperLagNotificationGroup	1.3.6.1.4.1.2011.5.25.178.3.2.3			Description.

RFC description

Super LAG redundancy management MIB for Huawei routers providing link aggregation status and failover.

Start monitoring Huawei IRF fabric switch (data center/core, cross-chassis SuperLAG) 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 HUAWEI-SUPERLAG-MIB

What Is HUAWEI-SUPERLAG-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description