The local device has detected a routing loop. (LoopType=[loopType], DetectProtocol=[detectProtocol], DetectProtocolAttr=[detectProtocolAttr], RedistributeID1=[redistributeID1], RedistributeID2=[redistributeID2])
The device detects a routing loop.
In VS mode, this trap is supported only by the admin VS.
| Trap Attribute | Description |
|---|---|
Alarm or Event |
Alarm |
Trap Severity |
Alert |
Mnemonic Code |
routeLoopDetect |
Trap OID |
1.3.6.1.4.1.2011.5.25.24.2.4.35 |
MIB |
HUAWEI-ISIS-CONF-MIB |
Alarm ID |
0x00f103f8 |
Alarm Name |
hwRouteLoopDetected |
Alarm Type |
communicationsAlarm |
Raise or Clear |
Raise |
Match trap |
ISIS_1.3.6.1.4.1.2011.5.25.24.2.4.36 hwRouteLoopDetectedClear |
| Parameter | Description |
|---|---|
loopType |
Loop detection type. |
detectProtocol |
Type of the protocol that detects a routing loop. |
detectProtocolAttr |
Information about the loop detection protocol.IS-IS and OSPF are the address family and protocol process ID. BGP is an address family or sub-address family. |
redistributeID1 |
Re-advertise device ID 1.IS-IS corresponds to the system ID of the process, and OSPF corresponds to the router ID of the process. |
redistributeID2 |
Re-advertise device ID 2.IS-IS corresponds to the system ID of the process, and OSPF corresponds to the router ID of the process. |
| VB OID | VB Name | VB Index |
|---|---|---|
1.3.6.1.4.1.2011.5.25.24.2.2.32 |
hwLoopDetectType |
- |
1.3.6.1.4.1.2011.5.25.24.2.2.33 |
hwLoopDetectProtocol |
- |
1.3.6.1.4.1.2011.5.25.24.2.2.34 |
hwLoopDetectProtocolAttr |
- |
1.3.6.1.4.1.2011.5.25.24.2.2.35 |
hwLoopDetectRedistributeID1 |
- |
1.3.6.1.4.1.2011.5.25.24.2.2.36 |
hwLoopDetectRedistributeID2 |
- |
If the loop detection type is IS-IS, the possible causes of the alarm are as follows:
RedistributeID1 and RedistributeID2 correspond to the system IDs of the IS-IS processes on the two devices where a routing loop occurs. When the IS-IS processes on the two devices import routes from other IS-IS processes, no import policy is configured or the import policy is incorrectly configured. As a result, a routing loop occurs.
After IS-IS detects a loop on an imported route, it automatically increases the cost of the imported route to eliminate the impact of the loop on services.The original risk source of the routing loop caused by the re-advertisement of two devices still exists. In addition, the route cost adjusted by the system during automatic loop breaking may cause the traffic path to be inconsistent with the expected one. Therefore, after the system reports the alarm, modify the policy for importing routes in the IS-IS process on the two devices that re-advertise routes as soon as possible to eliminate the configuration risk source that causes routing loops.You can run the display isis process-id lsdb verbose local | include 167772140 command to view information about the routes that have formed a loop and are automatically broken. process-id is the process ID in the alarm information about the loop detection protocol.
After the risk source that causes the loop is eliminated, run the clear route loop-detect isis alarm-state command in the system view of the device that generates the alarm to manually clear the alarm and restore the cost of the imported route to the normal value.