No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Alarm Handling

S9300, S9300E, and S9300X V200R013C00

This document provides the explanations, causes, and recommended actions of alarms on the product.
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
L2IFPPI

L2IFPPI

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.

Impact on the System

Traffic transmission on an interface is affected.

Possible Causes

The number of secure MAC addresses or sticky MAC addresses exceeds the upper limit.

Procedure

  1. 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.

  2. 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.

  3. 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.

  4. Contact technical support personnel.
  5. End.

Related Information

None

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.

Impact on the System

The device receives an invalid packet.

Possible Causes

Cause 1: The interface receives an all-0 source MAC address.

Cause 2: The interface receives an all-0 destination MAC address.

Procedure

  • No action is required.

Related Information

None

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.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.42.2.1.7.11 Warning other(1)

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.

Impact on the System

No more MAC addresses can be learned.

Possible Causes

The number of MAC addresses learned by the interface, VLAN, or VSI reached the upper limit.

Procedure

  1. 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.

  2. End.

Related Information

None

L2IFPPI_1.3.6.1.4.1.2011.5.25.42.2.1.7.12 hwMacFlappingAlarm

Description

L2IFPPI/4/MAC_FLAPPING_ALARM: OID [oid] The MAC address has flap value. (L2IfPort=[INTEGER], entPhysicalIndex=[INTEGER], BaseTrapSeverity=[INTEGER], BaseTrapProbableCause=[INTEGER], BaseTrapEventType=[INTEGER], MacAddr=[OCTET], VLANID=[INTEGER], FormerIfDescName=[OCTET], CurrentIfDescName=[OCTET], DeviceName=[OCTET])

MAC address flapping occurred.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.42.2.1.7.12 Warning equipmentAlarm(5)

Parameters

Name Meaning
oid Indicates the MIB object ID of the alarm.
L2IfPort Indicates the interface index.
entPhysicalIndex Indicates the device entity index.
BaseTrapSeverity Indicates the alarm severity.
BaseTrapProbableCause Indicates the alarm cause.
BaseTrapEventType Indicates the alarm type.
MacAddr Indicates the blocked MAC address.
VLANID Indicates the VLAN ID.
FormerIfDescName Indicates the interface that first learns the MAC address.
CurrentIfDescName Indicates the interface that later learns the MAC address.
DeviceName Indicates the device name.

Impact on the System

The switch fails to receive traffic from a user whose MAC address flaps.

Possible Causes

The MAC address learned by this interface was also learned by another interface.

Procedure

  1. Perform the following operations to remove loops:

    Check information about the two interfaces that learn the same MAC address in the alarm. Shut down one of the two interfaces according to networking requirements and go to step 2.

  2. Check whether the alarm is generated again.

    • If so, another loop exists. Shut down one of the two interfaces to eliminate the loop.
    • If not, go to step 3.

  3. End.

Related Information

None

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 MAC addresses learned by the device is restored to the normal range.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.42.2.1.7.19 Warning other(1)

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.
MacLimitVsiName Indicates that the number of MAC addresses learned by this VSI 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.

Impact on the System

The device is allowed to learn new MAC addresses.

Possible Causes

The number of MAC addresses learned by an interface, a VLAN, or a VSI is restored to the normal range.

Procedure

  1. This alarm is informational only, and no action is required.

L2IFPPI_1.3.6.1.4.1.2011.5.25.160.3.1 hwMflpIfBlock

Description

L2IFPPI/4/MFLPIFBLOCK: OID [oid] Loop exists in VLAN [INTEGER], Interface [OCTET1] blocked, block-time is [GAUGE] for [OCTET2], Mac Address is [OCTET3].

MAC address flapping occurs and the interface is blocked.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.160.3.1 Warning equipmentAlarm(5)

Parameters

Name Meaning
oid Indicates the MIB object ID of the alarm.
INTEGER Indicates the VLAN ID.
OCTET1 Indicates the blocked interface name.
GAUGE Indicates the time when the interface is blocked.
OCTET3 Indicates the flapped MAC address.
OCTET2 Indicates the cause why the interface is blocked.

Impact on the System

Traffic cannot be received normally.

Possible Causes

Cause 1:

The interfaces where loops occur are added to the same VLAN.

Cause 2:

Cables are connected incorrectly.

Cause 3:

STP is enabled to remove loops on the network.

Procedure

  1. 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 9.

  2. 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.

  3. 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 9.

  4. Check whether the ring network meets requirements.

    • If yes, go to step 7.
    • If not, go to step 5.

  5. Do as follows to remove loops:

    (1) Run the display loop-detect eth-loop [ vlan vlan-id ] command to view the blocked interface.

    (2) Run the display mac-address vlan vlan-id command to search an interface that learns the MAC address.

    (3) Shut down one interface according to the networking.

    (4) Run the reset loop-detect eth-loop vlan vlan-id { all | interface interface-type interface-number | mac-address mac-address } command to delete the blocked interface.

  6. Check whether the alarm recovery message is received.

    • If yes, go to step 9.
    • If not, go to step 7.

  7. Enable STP. Then check whether the alarm is still reported.

    • If yes, go to step 8.
    • If not, go to step 9.

  8. Contact technical support personnel.
  9. End.

L2IFPPI_1.3.6.1.4.1.2011.5.25.160.3.2 hwMflpIfResume

Description

L2IFPPI/4/MFLPIFRESUME: OID [oid] Loop does not exist in VLAN [INTEGER], Interface [OCTET1] resumed, block-time is [GAUGE] for [OCTET2].

The blocked interface where MAC address flapping occurs is recovered.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.160.3.2 Warning equipmentAlarm(5)

Parameters

Name Meaning
oid Indicates the MIB object ID of the alarm.
INTEGER Indicates the VLAN ID.
OCTET1 Indicates the blocked interface name.
OCTET2 Indicates the interface recovery cause.

Impact on the System

None

Possible Causes

The blocked interface is recovered.

Procedure

  1. This alarm is informational and no action is required.

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.

Impact on the System

Traffic cannot be received normally.

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

  1. 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.

  2. 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.

  3. 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.

  4. Enable STP. Then check whether the alarm is still reported.

    • If yes, go to step 5.
    • If not, go to step 6.

  5. Contact technical support personnel.
  6. End.

Related Information

None

L2IFPPI_1.3.6.1.4.1.2011.5.25.160.3.8 hwMflpVsiAlarm

Description

L2IFPPI/4/MFLPVSIALARM: OID [OID] MAC move detected, VSI-Name=[OCTET], [OCTET].

MAC address flapping occurs in a VSI.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.160.3.8 Warning equipmentAlarm(5)

Parameters

Name Meaning
oid Indicates the MIB object ID of the alarm.
VSI-Name Indicates a VSI name.
OCTET Indicates MAC address flapping information.

Impact on the System

Traffic cannot be received correctly.

Possible Causes

1:

The interfaces that form a loop are added to the same VSI.

2:

Cables are connected incorrectly.

3:

No loop prevention protocol such as STP is enabled.

4:

If protocols such as LLDP, LNP, NDP, NTDP, and LACP are enabled on blocked ports, protocol packets are forcibly transmitted through the blocked port. As a result, MAC address flapping occurs on the network connected to the blocked port.

Procedure

  1. Connect cables on the interfaces correctly and check whether the alarm persists.

    • If so, go to step 2.
    • If not, go to step 10.

  2. Check whether the two interfaces that learn the same MAC address can be added to different VSIs according to the networking.

    • If so, go to step 3.
    • If not, go to step 4.

  3. Add the two interfaces that learn the same MAC address to different VSIs. Then check whether the alarm persists.

    • If so, go to step 4.
    • If not, go to step 10.

  4. Enable a loop prevention protocol such as STP. Check whether the alarm persists.

    • If so, go to step 5.
    • If not, go to step 10.

  5. Check whether loops are caused by protocols such as LLDP, LNP, NDP, NTDP, and LACP.

    • If so, go to step 6.
    • If not, go to step 9.

  6. Check whether the packets need to be transparently transmitted.

    • If so, go to step 8.
    • If not, go to step 7.

  7. Disable the corresponding protocols on the blocked port. Then check whether the alarm persists.

    • If so, go to step 9.
    • If not, go to step 10.

  8. Apply a traffic policy that can match the destination MAC address of the protocol packets on the device where MAC address flapping occurs so that source MAC addresses of protocol packets are not learnt. Then check whether the alarm persists.

    • If so, go to step 9.
    • If not, go to step 10.

  9. Contact technical support personnel.
  10. End.

Related Information

None.

L2IFPPI_1.3.6.1.4.1.2011.5.25.160.3.9 hwMflpMacAddrAlarm

Description

L2IFPPI/4/MFLPMACBLOCK: OID [oid] Loop exists in VLAN [INTEGER], MAC Address [OCTET1] blocked, block-time is [GAUGE], the former Interface [OCTET2], the latter Interface [OCTET3], for [OCTET4].

MAC address flapping occurs and the MAC address is blocked.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.160.3.9 Warning equipmentAlarm(5)

Parameters

Name Meaning
oid Indicates the MIB object ID of the alarm.
INTEGER Indicates the VLAN ID.
OCTET1 Indicates the blocked MAC address.
GAUGE Indicates the block time.
OCTET2 Indicates the interface where the MAC address is learned before MAC address flapping occurs.
OCTET3 Indicates the interface where the MAC address is learned after MAC address flapping occurs.
OCTET4 Indicates the blocking cause.

Impact on the System

Traffic cannot be received normally.

Possible Causes

Cause 1:

The interfaces where loops occur are added to the same VLAN.

Cause 2:

Cables are connected incorrectly.

Cause 3:

STP is enabled to remove loops on the network.

Procedure

  1. 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 9.

  2. 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.

  3. 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 9.

  4. Check whether the ring network meets requirements.

    • If yes, go to step 7.
    • If not, go to step 5.

  5. Do as follows to remove loops:

    (1) Check information about the two interfaces that learn the same MAC address in the alarm.

    (2) Shut down one interface according to the networking.

    (3) Run the reset loop-detect eth-loop vlan vlan-id { all | interface interface-type interface-number | mac-address mac-address } command to delete the blocked MAC address.

  6. Check whether the alarm recovery message is received.

    • If yes, go to step 9.
    • If not, go to step 7.

  7. Enable STP. Then check whether the alarm is still reported.

    • Y=>8.
    • If not, go to step 9.

  8. Contact technical support personnel.
  9. End.

L2IFPPI_1.3.6.1.4.1.2011.5.25.160.3.10 hwMflpMacAddrResume

Description

L2IFPPI/4/MFLPMACRESUME: OID [oid] Loop does not exist in VLAN [INTEGER], MAC Address [OCTET1] resumed, block-time is [GAUGE], the former Interface [OCTET2], the latter Interface [OCTET3], for [OCTET4].

The flapped MAC address is unblocked.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.160.3.10 Warning equipmentAlarm(5)

Parameters

Name Meaning
oid Indicates the MIB object ID of the alarm.
INTEGER Indicates the VLAN ID.
OCTET1 Indicates the blocked MAC address.
GAUGE Indicates the block time.
OCTET2 Indicates the interface name before MAC address flapping occurs.
OCTET3 Indicates the interface name after MAC address flapping occurs.
OCTET4 Indicates the blocking cause.

Impact on the System

None

Possible Causes

Cause 1:

The blocked MAC address is recovered.

Procedure

  • This alarm is informational and no action is required.

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.

Impact on the System

Traffic of the VLAN cannot be forwarded through the interface.

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

  1. Check that cables are connected correctly. Check whether the alarm persists.

    • If so, go to 2.
    • If not, go to 6.

  2. 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.

  3. Add the two interfaces to different VLANs. Check whether the alarm persists.

    • f so, go to 4.
    • If not, go to 6.

  4. Enable a loop prevention protocol such as STP. Check whether the alarm persists.

    • If so, go to 5.
    • If not, go to 6.

  5. Contact technical support personnel.
  6. 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.

Impact on the System

None

Possible Causes

1:

An interface that has been removed from a VLAN because of MAC address flapping joins the VLAN again.

Procedure

  1. This alarm is informational and no action is required.

L2IFPPI_1.3.6.1.4.1.2011.5.25.219.2.2.13 hwBoardPowerOff

Description

L2IFPPI/4/BOARDPOWEROFF: OID [OID] The LPU is powered off. This LPU only supports the trunks with index 127 or smaller than 127. Delete the trunks with index larger than 127 and power on the LPU. (Index=[INTEGER1], EntityPhysicalIndex=[INTEGER2], PhysicalName="[OCTET]", EntityTrapEntType=[INTEGER3], EntityTrapFaultID=[INTEGER4])

The card was powered off. The card supports only the Eth-Trunk with the index less than or equal to 127. Delete the Eth-Trunk with the index larger than 127, and power on the card.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.219.2.2.13 Warning environmentalAlarm(6)

Parameters

Name Meaning
oid Indicates the MIB object ID of the alarm.
OCTET Indicates the entity name.
INTEGER1 Indicates the instance index.
INTEGER2 Indicates the index of the physical entity.
INTEGER3 Indicates the entity type.
INTEGER4 Indicates the error code.

Impact on the System

The card cannot be registered.

Possible Causes

The causes are as follows:

Only some cards support Eth-Trunk specification extension. If Eth-Trunk specification extension is configured and there is an Eth-Trunk with the index larger than 127, when you install the card that does not support Eth-Trunk specification (low-specification card), the low-specification card cannot be registered.

Procedure

  1. Use either of the following methods:

    • Remove the low-specification card. For details about the supported cards, see the assign trunk command.
    • If the low-specification card must be used, delete the Eth-Trunk with the index larger than 127. For details about the mapping between Eth-Trunk indexes and IDs, see the display trunk index-map command.

  2. If the alarm is not cleared, contact technical support personnel.
  3. End.

Related Information

None

L2IFPPI_1.3.6.1.4.1.2011.5.25.219.2.12.3 hwPortNoSupportOETrap

Description

L2IFPPI/4/CSS_NOSUPPORT_OEPORT: OID [OID] The 1000base-T optical/electrical module or optical module cannot be installed on the port when the port is used as a stack port.(EntityPhysicalIndex=[INTEGER], EntityIfIndex=[INTEGER], EntPhysicalName=[OCTET], hwEntityTrapFaultID=[INTEGER]).

A port has been configured as a CSS port, and the SFP copper module cannot be used on this port.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1 .4.1.2011.5.25.219.2.12.3 Warning environmentalAlarm(6)

Parameters

Name Meaning
OID Indicates the MIB object ID of the alarm.
EntityPhysicalIndex Indicates the index of a physical port.
EntityIfIndex Indicates the logical interface index.
EntPhysicalName Indicates the physical port name. The value depends on the port type. Different cards support different port types.
hwEntityTrapFaultID Indicates an error code.

Impact on the System

The stacking function fails on the port.

Possible Causes

Cause 1:

A port is configured as a CSS port, and the SFP copper module installed on the port cannot be used for CSS connection.

Procedure

  1. To use this port as a CSS port, install an SFP copper module that supports CSS connection.
  2. If you do not want to use this port as a CSS port, delete the CSS port. The SFP copper module does not need to be replaced when the port is used as a common service port.
  3. If the alarm persists, contact technical support personnel.
  4. End.

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:
  • Type: reason why MAC addresses change. 01 indicates MAC address learning; 02 indicates MAC address aging.
  • Ifindex: index of the interface sending the MAC address change alarm.
  • Vlaninvalid: VLAN tag. The value 1 indicates that the MAC address is learned in VLAN.
  • Vlanid: VLAN ID.
  • Mac-address: MAC address.

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:
  • 02: MAC address aging.
  • 00000006: interface index.
  • 1: MAC address is learned in VLAN.
  • 03e8: The decimal notation of this value is 1000. That is, this field indicates VLAN 1000.
  • 0000111105ee: MAC address that is aged out.

Impact on the System

None.

Possible Causes

The device learns the MAC address or the MAC address is aged.

Procedure

  1. This alarm is informational only, and no action is required.

Related Information

None.

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.

Impact on the System

None.

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

  1. 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.

  2. 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

  3. If the alarm is not cleared, contact technical support personnel.
  4. End.

Related Information

None.

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.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.315.3.3 Warning other(1)

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 some cards may fail to be learned. As a result, Layer 2 unicast packets are broadcast.

Possible Causes

The MAC address usage exceeds the upper alarm threshold.

Procedure

  1. 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.

  2. 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.

  3. Use either of the following methods:

    • Migrate services to other devices with sufficient space or use a new card that supports a larger number of MAC address entries.

    • Run the assign resource-mode slot slot-id mode enhanced-mac command in the system view to configure the extended MAC entry resource mode.
      NOTE:

      After the extended MAC entry resource mode is configured, you must restart the card to make the configuration take effect.

      For details about cards that support the extended MAC entry resource mode, see assign resource-mode.

      When the enhanced-mac mode is configured to increase the specifications of MAC address entries, specifications of other entries are affected. For details about the specifications of each entry in the enhanced-mac mode, see assign resource-mode.

    After the operation, check whether the alarm persists.
    • If so, go to step 4.
    • If not, go to step 5.

  4. Collect alarm, log, and configuration information, and contact technical support personnel.
  5. End.

Related Information

None.

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.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.315.3.4 Warning other(1)

Parameters

Name Meaning
oid Indicates the MIB object ID of the alarm.
INTEGER1 Indicates the instance ID.
INTEGER2 Indicates the sending type.
INTEGER3 Indicates the sending severity.
INTEGER4 Indicates the sending cause.
OCTET Indicates the interface name.

Impact on the System

None.

Possible Causes

The MAC address usage is lower than the lower alarm threshold.

Procedure

  1. This trap message is informational only, and no action is required.

Related Information

None.

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 and the MAC address entry cannot be learned.

Possible Causes

The MAC address hash conflict occurs.

Procedure

  1. 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.

  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.
    NOTE:
    • MAC addresses are distributed on a network randomly, so the best hash algorithm cannot be determined. Generally, it is recommended to use the default MAC hash algorithm 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 card to make the configuration take effect.

  3. 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.

  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.

  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.

  6. Collect trap, log, and configuration information, and contact technical support personnel.

Related Information

None

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

  1. Confirm whether this packet needs to be processed.

    • If so, go to step 2.
    • If not, go to step 3.

  2. 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.
  3. End.

L2IFPPI_1.3.6.1.4.1.2011.5.25.160.3.17 hwMflpBdAlarm

Description

L2IFPPI/4/MFLPBDALARM: OID [OID] MAC move detected, bridge-domain ID=[GAUGE], original-port=[OCTET1], flapping-port 1=[OCTET2], flapping-port 2=[OCTET3], [OCTET4].

MAC address flapping occurs in a BD.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.160.3.17

Warning

environmentalAlarm(6)

Parameters

Name Meaning
OID Indicates the MIB object ID of the alarm.
GAUGE Indicates the ID of a BD.
OCTET1 Indicates the number of the interface that learns the MAC address earlier.
OCTET2 Indicates the number of the interface that learns the MAC address later.
OCTET3 Indicates the number of the interface that learns the MAC address later.
OCTET4 Indicates the alarm cause.

Impact on the System

Traffic cannot be received correctly.

Possible Causes

A MAC address in a BD is learned by different interfaces, causing MAC address flapping.

Procedure

  1. Perform the following operations to remove loops:

    Check information about the two interfaces that learn the same MAC address in the alarm. Shut down one of the two interfaces according to the networking and go to step 2.

  2. Check whether the alarm is generated again.

    • If so, another loop exists. Shut down one of the two interfaces to eliminate the loop.
    • If not, go to step 3.

  3. End.
Translation
Download
Updated: 2019-04-09

Document ID: EDOC1100065855

Views: 3507

Downloads: 2

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next