IS-IS Configuration Guide for Cisco 8000 Series Routers, Cisco IOS XR Releases

PDF

IS-IS Configuration Guide for Cisco 8000 Series Routers, Cisco IOS XR Releases

IS-IS penalties for link delay anomalies

Want to summarize with AI?

Log in

Explains IS-IS penalties for link delay anomalies, covering detection with SR-PM, automatic metric adjustments, advertisement and restoration processes, node reload behavior, and configuration guidance for managing IS-IS responses to link delay events.


A penalty for link delay anomaly is a network routing mechanism that

  • automatically increases the IS-IS metric when a delay anomaly is detected

  • advertises the updated metric in the network to steer traffic away from the affected link, and

  • restores the original metric when the link recovers and the anomaly bit is reset.

Link anomaly detection overview

When Link Anomaly Detection is enabled in Segment Routing Performance Measurement (SR-PM), the Performance Measurement (PM) module monitors links for delay anomalies. If a delay anomaly is detected, PM sets an anomaly bit (A-bit) for the affected link.

IS-IS metric adjustment and advertisement

Upon detecting an anomaly (A-bit set), the IS-IS protocol automatically increases the link’s metric by a user-defined penalty amount. This higher metric is then advertised to the network, making the link less attractive for routing decisions and steering traffic away from the problematic link.

Recovery and metric restoration

When the link recovers and delay metrics return to normal, the PM module clears the anomaly bit. IS-IS then restores the metric to its default or previously configured value, allowing the link to be used normally in routing again.

Node reload behavior

If a network node is reloaded, the IS-IS protocol advertises the default or configured metric (without penalty) for the link until a new performance measurement is made and any anomalies are reassessed.

Configuration guidance

For information about configuring link delay anomaly threshold values and more implementation details, see the "Link Anomaly Detection with IGP Penalty" topic in the Segment Routing Configuration Guide.


Before you begin

Ensure that link anomaly detection is configured in Segment Routing performance measurement before you apply the IGP penalty values.

Procedure

1.

Configure the delay-anomaly fallback metric on the affected IS-IS interfaces.

Example:

Router(config)#router isis 100
Router(config-isis)#interface GigabitEthernet 0/1/0/1
Router(config-isis-if)#address-family ipv4 unicast
Router(config-isis-if-af)#metric fallback anomaly delay increment 25
Router(config-isis-if-af)#exit
Router(config-isis-if)#exit
Router(config-isis)#interface GigabitEthernet 0/1/0/2
Router(config-isis-if)#address-family ipv4 unicast
Router(config-isis-if-af)#metric fallback anomaly delay multiplier 2
2.

Review the running configuration to confirm the configured increment and multiplier values.

Example:

router isis 100
 interface GigabitEthernet0/1/0/1
  address-family ipv4 unicast
   metric fallback anomaly delay increment 25
  !
 !
 interface GigabitEthernet0/1/0/2
  address-family ipv4 unicast
   metric fallback anomaly delay multiplier 2
  !
 !
!