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