L2IFPPI
- L2IFPPI_1.3.6.1.4.1.2011.5.25.42.2.1.7.6 hwPortSecRcvInsecurePktAlarm
- L2IFPPI_1.3.6.1.4.1.2011.5.25.42.2.1.7.9 hwPortStickyReachMaxAlarm
- L2IFPPI_1.3.6.1.4.1.2011.5.25.42.2.1.7.10 hwRecIllegalMacPktAlarm
- L2IFPPI_1.3.6.1.4.1.2011.5.25.42.2.1.7.11 hwMacLimitOverThresholdAlarm
- L2IFPPI_1.3.6.1.4.1.2011.5.25.42.2.1.7.19 hwMacLimitOverThresholdAlarmResume
- L2IFPPI_1.3.6.1.4.1.2011.5.25.160.3.7 hwMflpVlanAlarm
- L2IFPPI_1.3.6.1.4.1.2011.5.25.160.3.11 hwMflpQuitVlanAlarm
- L2IFPPI_1.3.6.1.4.1.2011.5.25.160.3.12 hwMflpQuitVlanResume
- L2IFPPI_1.3.6.1.4.1.2011.5.25.315.3.1 hwMacTrapAlarm
- L2IFPPI_1.3.6.1.4.1.2011.5.25.315.3.2 hwPortVlanSecureMacAlarm
- L2IFPPI_1.3.6.1.4.1.2011.5.25.315.3.3 hwSlotMacUsageRaisingThreshold
- L2IFPPI_1.3.6.1.4.1.2011.5.25.315.3.4 hwSlotMacUsageFallingThreshold
- L2IFPPI_1.3.6.1.4.1.2011.5.25.315.3.6 hwMacTrapHashConflictAlarm
- L2IFPPI_1.3.6.1.4.1.2011.5.25.315.3.9 hwPortsecStaticFlpAlarm
L2IFPPI_1.3.6.1.4.1.2011.5.25.42.2.1.7.6 hwPortSecRcvInsecurePktAlarm
Description
L2IFPPI/4/PORTSEC_ACTION_ALARM: OID [oid] Interface ([INTEGER1]/[INTEGER2]) [OCTET] receive insecure MAC address, and the port status is: [INTEGER3]. (1:restrict;2:protect;3:error-down)
The number of MAC addresses on an interface exceeds the threshold.
Attribute
Alarm ID | Alarm Severity | Alarm Type |
---|---|---|
1.3.6.1.4.1.2011.5.25.42.2.1.7.6 | Warning | qualityOfServiceAlarm(3) |
Parameters
Name | Meaning |
---|---|
oid | Indicates the MIB object ID of the alarm. |
[INTEGER1]/[INTEGER2] | Indicates the interface index. |
OCTET | Indicates the interface name. |
INTEGER3 | Indicates the interface status. |
Procedure
- View the interface status in the alarm information.
- If the interface status is Restrict (packets are discarded because the rate limit is exceeded), go to 2.
- If the interface status is Errordown, go to 3.
- Run the port-security max-mac-num max-number command to increase the maximum number of MAC
address learning. Check whether the alarm is cleared.
- If the alarm is cleared, go to 5.
- If the alarm is not cleared, go to 4.
- Perform error-down auto-recovery cause port-security
interval interval-value on the interface, and then check
whether the alarm is cleared.
- If the alarm is cleared, go to 5.
- If the alarm is not cleared, go to 4.
- Contact technical support personnel.
- End.
L2IFPPI_1.3.6.1.4.1.2011.5.25.42.2.1.7.9 hwPortStickyReachMaxAlarm
Description
L2IFPPI/4/PORTSEC_STICKYMAC_ALARM: OID [OID] the number of [OCTET] reaches the max.
The number of learned sticky MAC addresses or secure MAC addresses reached the threshold.
Attribute
Alarm ID | Alarm Severity | Alarm Type |
---|---|---|
1.3.6.1.4.1.2011.5.25.42.2.1.7.9 |
Warning |
qualityOfServiceAlarm(3) |
Parameters
Name | Meaning |
---|---|
[OID] |
Indicates the MIB object ID of the alarm. |
[OCTET] |
Indicates the MAC address type: sticky MAC address or secure MAC address. |
Impact on the System
No more sticky MAC address entries or secure MAC address entries can be generated.
Possible Causes
The number of learned sticky MAC addresses or secure MAC addresses reached limitation.
Procedure
- Run the display mac-address security, display mac-address sec-config, and display mac-address sticky commands to view the secure dynamic MAC, secure static MAC, and sticky MAC entries. Check whether any sticky or secure MAC entries are invalid.
- If so, go to step 2.
- If not, go to step 3.
- Run the undo mac-address mac-address [ vlan vlan-id ] command to delete invalid MAC entries. Then check whether the alarm is cleared.
- If so, go to step 4.
- If not, go to step 3.
- Collect alarm, log, and configuration information, and contact technical support personnel.
- End.
L2IFPPI_1.3.6.1.4.1.2011.5.25.42.2.1.7.10 hwRecIllegalMacPktAlarm
Description
L2IFPPI/4/MAC_ILLEGAL_MAC_ALARM: OID [OID] Receive packets with an all-0 MAC address. (PhysicalIndex=[INTEGER], InterfaceName=[OCTET])
The interface receives a packet with an all-0 destination or source MAC address.
Attribute
Alarm ID | Alarm Severity | Alarm Type |
---|---|---|
1.3.6.1.4.1.2011.5.25.42.2.1.7.10 | Warning | qualityOfServiceAlarm(3) |
Parameters
Name | Meaning |
---|---|
OID | Indicates the MIB object ID of the alarm. |
PhysicalIndex |
Indicates the physical port index. |
InterfaceName |
Indicates the physical port name. |
L2IFPPI_1.3.6.1.4.1.2011.5.25.42.2.1.7.11 hwMacLimitOverThresholdAlarm
Description
L2IFPPI/4/MAC_LIMIT_ALARM: OID [oid] MAC address learning reached the limit. (L2IfNum=[INTEGER], MacLimitVlanId=[INTEGER], MacLimitVsiName=[OCTET], L2PortNum=[INTEGER], BaseTrapSeverity=[INTEGER], BaseTrapProbableCause=[INTEGER], BaseTrapEventType=[INTEGER], MacDynAddressLearnNum=[INTEGER], MacLimitMaxMac=[INTEGER], L2IfPortName=[OCTET])
The number of MAC addresses learned by the interface, VLAN, or VSI reached the upper limit.
Parameters
Name | Meaning |
---|---|
oid |
Indicates the MIB object ID of the alarm. |
L2IfNum |
Indicates the interface index. |
MacLimitVlanId |
Indicates the VLAN ID. |
MacLimitVsiName |
Indicates the VSI name. |
L2PortNum |
Indicates the port index. |
BaseTrapSeverity |
Indicates the alarm severity. |
BaseTrapProbableCause |
Indicates the alarm cause. |
BaseTrapEventType |
Indicates the alarm type. |
MacDynAddressLearnNum |
Indicates the number of learned MAC addresses. |
MacLimitMaxMac |
Indicates the maximum number of MAC addresses to be learned. |
L2IfPortName |
Indicates the interface name. |
Possible Causes
The number of MAC addresses learned by the interface, VLAN, or VSI reached the upper limit.
Procedure
- Check whether the alarm is generated on an interface, in a VLAN, or in a VSI.
Perform one of the following operations according to networking requirements and go to step 2:
- Increase the upper limit on the number of MAC addresses to be learned.
- Delete unnecessary MAC addresses.
- Ignore the alarm.
- End.
L2IFPPI_1.3.6.1.4.1.2011.5.25.42.2.1.7.19 hwMacLimitOverThresholdAlarmResume
Description
L2IFPPI/4/MAC_LIMIT_ALARM: OID [oid] MAC address learning is resumed. (L2IfNum=[INTEGER], MacLimitVlanId=[INTEGER], MacLimitVsiName=[OCTET], L2PortNum=[INTEGER], BaseTrapSeverity=[INTEGER], BaseTrapProbableCause=[INTEGER], BaseTrapEventType=[INTEGER], MacDynAddressLearnNum=[INTEGER], MacLimitMaxMac=[INTEGER], L2IfPortName=[OCTET])
The number of learned MAC addresses falls below 80% of the limit.
Parameters
Name | Meaning |
---|---|
oid |
Indicates the MIB object ID of the alarm. |
L2IfNum |
Indicates the interface index. |
MacLimitVlanId |
Indicates that the number of MAC addresses learned by this VLAN is restored to the normal range. |
L2PortNum |
Indicates the interface index. |
BaseTrapSeverity |
Indicates the alarm severity. |
BaseTrapProbableCause |
Indicates the alarm cause. |
BaseTrapEventType |
Indicates the alarm type. |
MacDynAddressLearnNum |
Indicates the number of learned MAC addresses. |
MacLimitMaxMac |
Indicates the maximum number of MAC addresses allowed to be learned. |
L2IfPortName |
Indicates the interface name. |
L2IFPPI_1.3.6.1.4.1.2011.5.25.160.3.7 hwMflpVlanAlarm
Description
L2IFPPI/4/MFLPVLANALARM: OID [oid] MAC move detected, VLANID=[INTEGER], [OCTET].
MAC address flapping has occurred.
Attribute
Alarm ID | Alarm Severity | Alarm Type |
---|---|---|
1.3.6.1.4.1.2011.5.25.160.3.7 | Warning | equipmentAlarm(5) |
Parameters
Name | Meaning |
---|---|
oid | Indicates the MIB object ID of the alarm. |
INTEGER | Indicates the VLAN ID. |
OCTET | Indicates the flapping MAC address and interfaces between which the MAC address flaps. |
Possible Causes
1:
The interfaces where loops occur are added to the same VLAN.
2:
Cables are connected incorrectly.
3:
STP is enabled to remove loops on the network.
Procedure
- Check that cables are connected correctly. Then check whether
the alarm is still reported.
- If yes, go to step 2.
- If not, go to step 6.
- Check whether the two interfaces that learn the same MAC
address can be added to different VLANs according to the networking.
- If yes, go to step 3.
- If not, go to step 4.
- Modify the configuration and add the two interfaces that
learn the same MAC address to different VLANs. Then check whether
the alarm is still reported.
- If yes, go to step 4.
- If not, go to step 6.
- Enable STP. Then check whether the alarm is still reported.
- If yes, go to step 5.
- If not, go to step 6.
- Contact technical support personnel.
- End.
L2IFPPI_1.3.6.1.4.1.2011.5.25.160.3.11 hwMflpQuitVlanAlarm
Description
L2IFPPI/4/MFLPQUITVLANALARM: OID [oid] (VLAN=[INTEGER]) Interface [OCTET1] leaved from VLAN [OCTET2] because MAC move detected.
MAC address flapping occurs on an interface, and the interface is removed from the VLAN where MAC address flapping occurs.
Attribute
Alarm ID | Alarm Severity | Alarm Type |
---|---|---|
1.3.6.1.4.1.2011.5.25.160.3.11 | Warning | environmentalAlarm(6) |
Parameters
Name | Meaning |
---|---|
oid | Indicates the MIB object ID of the alarm. |
INTEGER | Indicates the VLAN ID. |
OCTET1 | Indicates the interface name. |
OCTET2 | Indicates the VLAN from which the interface is removed. |
Possible Causes
1:
The interfaces that form a loop belong to the same VLAN.
2:
Cables are connected incorrectly.
3:
No loop prevention protocol such as STP is enabled.
Procedure
- Check that cables are connected correctly. Check whether
the alarm persists.
- If so, go to 2.
- If not, go to 6.
- Check whether the two interfaces that learn the same MAC
address can be added to different VLANs according to the networking.
- If so, go to 3.
- If not, go to 4.
- Add the two interfaces to different VLANs. Check whether
the alarm persists.
- f so, go to 4.
- If not, go to 6.
- Enable a loop prevention protocol such as STP. Check whether
the alarm persists.
- If so, go to 5.
- If not, go to 6.
- Contact technical support personnel.
- End.
L2IFPPI_1.3.6.1.4.1.2011.5.25.160.3.12 hwMflpQuitVlanResume
Description
L2IFPPI/4/MFLPQUITVLANALARMRESUME: OID [oid] (VLAN=[INTEGER]) Interface [OCTET1] has resumed of leaved from VLAN [OCTET2] because MAC move detected.
An interface that has been removed from a VLAN because of MAC address flapping joins the VLAN again.
Attribute
Alarm ID | Alarm Severity | Alarm Type |
---|---|---|
1.3.6.1.4.1.2011.5.25.160.3.12 | Warning | environmentalAlarm(6) |
Parameters
Name | Meaning |
---|---|
oid | Indicates the MIB object ID of the alarm. |
INTEGER | Indicates the VLAN ID. |
OCTET1 | Indicates the interface name. |
OCTET2 | Indicates the VLAN from which the interface is removed. |
L2IFPPI_1.3.6.1.4.1.2011.5.25.315.3.1 hwMacTrapAlarm
Description
L2IFPPI/5/MACCHANGE_TRAPINFO: OID [oid] MAC address information: [OCTET].
The MAC address changes.
Attribute
Alarm ID | Alarm Severity | Alarm Type |
---|---|---|
1.3.6.1.4.1.2011.5.25.315.3.1 | Indeterminate | equipmentAlarm(5) |
Parameters
Name | Meaning |
---|---|
oid | Indicates the MIB object ID of the alarm. |
OCTET | Indicates TypeIfindexVlaninvalidVlanidMac-address. The fields are described as follows:
A sample of the alarm message: L2IFPPI/5/MACCHANGE_TRAPINFO: OID 1.3.6.1.4.1.2011.5.25.315.3.1 Mac address information:0200000006103e80000111105ee. The fields in the alarm are described as follows:
|
L2IFPPI_1.3.6.1.4.1.2011.5.25.315.3.2 hwPortVlanSecureMacAlarm
Description
L2IFPPI/4/PORTSEC_ACTION_HAVEMAC_ALARM: OID [oid] Interface [INTEGER] receive insecure MAC address. (MacAddr=[OPAQUE], VLAN=[INTEGER], VsiName=[OCTET], Portindex=[INTEGER], InterfaceName=[OCTET], the port status is: [INTEGER]. (1:restrict;2:protect;3:error-down))
On an interface where the number of learned secure MAC addresses reaches the maximum value, the interface sends an alarm when receiving invalid MAC addresses.
Attribute
Alarm ID | Alarm Severity | Alarm Type |
---|---|---|
1.3.6.1.4.1.2011.5.25.315.3.2 | Warning | environmentalAlarm(6) |
Parameters
Name | Meaning |
---|---|
oid | Indicates the MIB object ID of the alarm. |
Interface |
Indicates the interface index corresponding to the invalid MAC address. |
MacAddr |
Indicates the invalid MAC address after the limit is reached. |
VLAN |
Indicates the VLAN ID. |
VsiName |
Indicates the name of a VSI. |
Portindex |
Indicates the port index corresponding to the invalid MAC address. |
InterfaceName |
Indicates the interface name corresponding to the invalid MAC address. |
port status |
Indicates the action triggered by the invalid MAC address after the limit is reached. |
Possible Causes
After the number of dynamic secure MAC addresses or sticky MAC addresses learned by an interface reaches the maximum value, the interface receives packets from another MAC address.
Procedure
- Check whether the MAC address in the alarm is valid.
- If the MAC address is valid, go to step 2.
- If the MAC address is invalid, go to step 3.
- Run the port-security max-mac-num max-number command to increase the maximum number of MAC
address to be learned. Check whether the alarm is cleared.
- Y=>4
- N=>3
- If the alarm is not cleared, contact technical support personnel.
- End.
L2IFPPI_1.3.6.1.4.1.2011.5.25.315.3.3 hwSlotMacUsageRaisingThreshold
Description
L2IFPPI/4/MACEXCDALARM:OID [OID] The MAC Address usage exceeds the threshold. (MacUsageIndex=[INTEGER1], BaseTrapType=[INTEGER2], TrapSeverity=[INTEGER3], BaseTrapCause=[INTEGER4], MacUsage=[INTEGER5], MacUsageThreshold=[INTEGER6], PhysicalName=[OCTET])
The MAC address usage exceeds the upper alarm threshold.
Parameters
Name | Meaning |
---|---|
oid |
Indicates the MIB object ID of the alarm. |
INTEGER1 |
Indicates the index of the MAC address usage. |
INTEGER2 |
Indicates the sending type. |
INTEGER3 |
Indicates the sending severity. |
INTEGER4 |
Indicates the sending cause. |
INTEGER5 |
Indicates the MAC address usage. |
INTEGER6 |
Indicates the alarm threshold for the MAC address usage. |
OCTET |
Indicates the interface name. |
Impact on the System
MAC addresses on the device may fail to be learned. As a result, Layer 2 unicast packets are broadcast.
Procedure
- Run the display this include-default | include mac-address threshold-alarm command in the system view to check whether the threshold of the MAC address usage is too low. By default, the lower threshold is 70% and the upper threshold is 80%. Users can specify the threshold range according to service requirements.
- If so, go to step 2.
- If not, go to step 3.
- Run the mac-address threshold-alarm upper-limit upper-limit-value lower-limit lower-limit-value command in the system view to reset the alarm thresholds. Check whether the alarm is cleared.
- If so, go to step 5.
- If not, go to step 3.
- Migrate services to other idle devices or load balance services to different devices. Then check whether the alarm persists.
- If so, go to step 4.
- If not, go to step 5.
- Collect alarm, log, and configuration information, and contact technical support personnel.
- End.
L2IFPPI_1.3.6.1.4.1.2011.5.25.315.3.4 hwSlotMacUsageFallingThreshold
Description
L2IFPPI/4/MACEXCDALARM: OID [OID] The MAC Address usage falls below the threshold. (PhysicalIndex=[INTEGER1], BaseTrapType=[INTEGER2], TrapSeverity=[INTEGER3], BaseTrapCause=[INTEGER4], PhysicalName=[OCTET])
The MAC address usage is lower than the lower alarm threshold.
L2IFPPI_1.3.6.1.4.1.2011.5.25.315.3.6 hwMacTrapHashConflictAlarm
Description
L2IFPPI/4/MACHASHCONFLICTALARM: OID [oid] A hash conflict occurs in MAC addresses. (IfIndex=[INTEGER], MacAddr=[OPAQUE], VLAN=[GAUGE], VsiName=[OCTET1], InterfaceName=[OCTET2])
The MAC address hash conflict occurs.
Attribute
Alarm ID | Alarm Severity | Alarm Type |
---|---|---|
1.3.6.1.4.1.2011.5.25.315.3.6 |
Warning |
environmentalAlarm(6) |
Parameters
Name | Meaning |
---|---|
oid |
Indicates the MIB object ID of the alarm. |
IfIndex |
Indicates the interface index. |
MacAddr |
Indicates the MAC address. |
VLAN |
Indicates the VLAN ID. |
VsiName |
Indicates the name of a VSI. |
InterfaceName |
Indicates the interface name. |
Impact on the System
The MAC address table space is not full but the MAC address entry cannot be learned.
Procedure
- Run the display mac-address summary command to check whether the usage of MAC address entry resources exceeds 80% on the device.
- If so, go to Step 4.
- If not, go to Step 2.
- Run the mac-address hash-mode command to change the MAC hash algorithm. Then check whether the alarm is cleared.
- If so, no further action is required.
- If not, go to Step 3.
MAC addresses are distributed on a network randomly, so the best hash algorithm cannot be determined. Generally, it is recommended the default MAC hash algorithm be used unless you have specific requirements.
An appropriate hash algorithm can reduce hash conflicts, but cannot prevent them.
After the hash algorithm is changed, restart the switch to make the configuration take effect.
- Obtain the location of the device on which the MAC address hash conflict occurs based on the MAC address and interface name in the alarm information. Adjust the plan and modify the VLAN configuration of the device access interface to assign the device to another VLAN. Then check whether the alarm is cleared.
- If so, no further action is required.
- If not, go to Step 4.
- Re-plan network deployment, migrate the services on the device corresponding to the MAC address in the alarm information to other devices with sufficient MAC address entry resources, and check whether the alarm is cleared.
- If so, no further action is required.
- If not, go to Step 5.
- Replace the device with another one that has larger MAC address entry resource specifications and check whether the alarm is cleared.
- If so, no further action is required.
- If not, go to Step 6.
- Collect trap, log, and configuration information, and contact technical support personnel.
L2IFPPI_1.3.6.1.4.1.2011.5.25.315.3.9 hwPortsecStaticFlpAlarm
Description
L2IFPPI/4/PORTSECSTATICFLP: OID [OID] Interface received a packet with flapping static MAC. (MACAddr=[OPAQUE], VLAN=[GAUGE], VsiName=[OCTET], IfIndex=[INTEGER], InterfaceName=[OCTET])
The source MAC address in the packet received by an interface already exists in the static MAC table of another interface.
Attribute
Alarm ID | Alarm Severity | Alarm Type |
---|---|---|
1.3.6.1.4.1.2011.5.25.315.3.9 | Warning | qualityOfServiceAlarm(3) |
Parameters
Name | Meaning |
---|---|
OID |
Indicates the MIB object ID of the alarm. |
MACAddr |
Indicates the MAC address. |
VLAN |
Indicates the VLAN ID. |
VsiName |
Indicates the name of a VSI. |
IfIndex |
Indicates the interface index. |
InterfaceName |
Indicates the interface name. |
Impact on the System
The source MAC address in the packet received by an interface already exists in the static MAC table of another interface. Therefore, the interface will discard this packet.
Possible Causes
An interface with port security enabled received a packet, and the source MAC address in the packet already exists in the static MAC table of another interface.
Procedure
- Confirm whether this packet needs to be processed.
- If so, go to step 2.
- If not, go to step 3.
- Run the display mac-address [ vlan vlan-id | interface-type interface-number ] * command to check the interface corresponding to the MAC address in the packet, and then run the undo mac-address [ interface-type interface-number | vlan vlan-id ] * command to delete the existing MAC address entry.
- End.
- L2IFPPI_1.3.6.1.4.1.2011.5.25.42.2.1.7.6 hwPortSecRcvInsecurePktAlarm
- L2IFPPI_1.3.6.1.4.1.2011.5.25.42.2.1.7.9 hwPortStickyReachMaxAlarm
- L2IFPPI_1.3.6.1.4.1.2011.5.25.42.2.1.7.10 hwRecIllegalMacPktAlarm
- L2IFPPI_1.3.6.1.4.1.2011.5.25.42.2.1.7.11 hwMacLimitOverThresholdAlarm
- L2IFPPI_1.3.6.1.4.1.2011.5.25.42.2.1.7.19 hwMacLimitOverThresholdAlarmResume
- L2IFPPI_1.3.6.1.4.1.2011.5.25.160.3.7 hwMflpVlanAlarm
- L2IFPPI_1.3.6.1.4.1.2011.5.25.160.3.11 hwMflpQuitVlanAlarm
- L2IFPPI_1.3.6.1.4.1.2011.5.25.160.3.12 hwMflpQuitVlanResume
- L2IFPPI_1.3.6.1.4.1.2011.5.25.315.3.1 hwMacTrapAlarm
- L2IFPPI_1.3.6.1.4.1.2011.5.25.315.3.2 hwPortVlanSecureMacAlarm
- L2IFPPI_1.3.6.1.4.1.2011.5.25.315.3.3 hwSlotMacUsageRaisingThreshold
- L2IFPPI_1.3.6.1.4.1.2011.5.25.315.3.4 hwSlotMacUsageFallingThreshold
- L2IFPPI_1.3.6.1.4.1.2011.5.25.315.3.6 hwMacTrapHashConflictAlarm
- L2IFPPI_1.3.6.1.4.1.2011.5.25.315.3.9 hwPortsecStaticFlpAlarm