The configured client IDs did not match.(hwPortIfIndex=[hwPortIfIndex], hwPortName=[hwPortName])
The configured client IDs did not match.
| Trap Attribute | Description |
|---|---|
Alarm or Event |
Alarm |
Trap Severity |
Critical |
Mnemonic Code |
hwFlexEClientIDMismatch |
Trap OID |
1.3.6.1.4.1.2011.5.25.157.2.264 |
MIB |
HUAWEI-PORT-MIB |
Alarm ID |
0x00F10225 |
Alarm Name |
hwFlexEClientIDMismatch |
Alarm Type |
equipmentAlarm |
Raise or Clear |
Raise |
Match trap |
DRIVER_1.3.6.1.4.1.2011.5.25.157.2.265 hwFlexEClientIDMismatchResume |
| Parameter | Description |
|---|---|
hwPortIfIndex |
Index of port. |
hwPortName |
Name of port. |
| VB OID | VB Name | VB Index |
|---|---|---|
1.3.6.1.4.1.2011.5.25.157.1.8.1.1.1 |
hwPhysicalPortIfIndex |
hwPhysicalPortIfIndex |
1.3.6.1.4.1.2011.5.25.157.1.8.1.1.4 |
hwPhysicalPortName |
hwPhysicalPortIfIndex |
1. Check whether there is a FlexE interface with the same client-id configuration at both ends. If not, check whether the alarm is cleared after configuring the same client-id parameter.
If the alarm is cleared, go to Step 6.
If the alarm is not cleared, go to Step 2.
2. Check if the connected FlexE interface is configured with bandwidth. If not, check whether the alarm is cleared after configuring bandwidth for the connected FlexE interface.
If the alarm is cleared, go to Step 6.
If the alarm is not cleared, go to Step 3.
3. Check whether the sub-slot granularities at both ends are the same. If the sub-slot granularities are different, ensure that they are the same, and then check whether the alarm is cleared.
If the alarm is cleared, go to Step 6.
If the alarm is not cleared, go to Step 4.
4. Check that the connected FlexE physical interface status is normal.
5. Collect alarm information, log information and configuration information, and then contact technical support personnel.
6. End.