Disabling Routing Loop Detection for Routes Imported to IS-IS
Context
When an IS-IS process imports routes, routing loops may occur. Routing loop detection can help prevent such routing loops. When a device detects that it imports a route advertised by itself, it sends this route with a large cost to other devices. After learning the route, these devices preferentially select other paths, thereby preventing routing loops. By default, IS-IS routing loop detection is enabled.
Procedure
- Run system-view
The system view is displayed.
- (Optional) Run clear route loop-detect isis alarm-state
The routing loop detection alarm state exits, and related alarms are cleared.
If the device detects an IS-IS routing loop, it reports an alarm. Because the device cannot automatically detect whether a routing loop is eliminated, you need to run this command to manually clear the IS-IS routing loop alarm after the routing loop is eliminated. This prevents the device from advertising a large cost for imported routes in this case.
- Run route loop-detect isis disable
Routing loop detection is disabled for imported IS-IS routes.
To reduce the impact of routing loops on services, you are advised to keep routing loop detection enabled for routes imported to IS-IS.
- Run commit
The configuration is committed.