IS-IS penalties for link loss anomalies

Updated: June 9, 2026

Want to summarize with AI?

Explains iS-IS penalty for link loss anomaly and the technical context you need before you configure or verify IS-IS behavior.

IS-IS penalty for link loss anomaly is a routing protocol mechanism that

increases the routing metric of a network interface when abnormal packet loss is detected
causes IS-IS to prefer alternative paths to improve network stability, and
facilitates automated traffic engineering to ensure rerouting away from problematic links.

Table 1. Feature History Table
Feature Name	Release Information	Feature Description
IS-IS penalty for link loss anomaly	Release 25.1.1	Introduced in this release on: Fixed Systems (8200 [ASIC: Q200, P100], 8700 [ASIC: P100, K100]); Centralized Systems (8600 [ASIC:Q200]); Modular Systems (8800 [LC ASIC: Q100, Q200, P100]) You can enhance network stability and routing efficiency by enabling the IS-IS routing protocol to dynamically adjust an interface's metric when the Performance Monitoring (PM) system detects a packet loss anomaly. This feature introduces these changes: CLI: The loss keyword is introduced in the metric fallback anomaly command. YANG Data Models: This feature extends the native Cisco-IOS-XR-um-router-isis-cfg.yang model. Refer to GitHub and YANG Data Models Navigator.

This dynamic adjustment lets IS-IS automatically reroute traffic away from links experiencing substantial packet loss, helping maintain overall network stability and efficiency.

For information on configuring the synthetic loss measurement, refer to Synthetic Loss Measurement topic in the Segment Routing Configuration Guide.

How IS-IS penalty for link loss anomaly works

Summary

IS-IS penalty for link loss anomaly enables Cisco IOS XR software to dynamically adjust routing metrics whenever synthetic packet loss measurements indicate anomalies on particular network interfaces. This process ensures traffic is rerouted automatically to maintain optimal network reliability.

The key components involved in the process are:

Customer edge devices (CE1 and CE2): Serve as the source and destination routers in the network topology.
Provider edge routers (PE1 and PE2): Connect CE devices and provide alternate routing paths (Path 1 and Path 2).
Cisco IOS XR software metric fallback anomaly loss command: Configured on interface(s) to modify metrics based on detected anomalies.
Synthetic Loss Measurement: Continuously monitors packet loss and triggers anomaly detection as needed.

Workflow

Figure 1. Traffic flow under metric fallback anomaly loss

The process involves these stages:

Detection of anomaly: When the measured packet loss on Path 1 exceeds a pre-defined upper-bound threshold, the Cisco IOS XR software flags a loss anomaly.
Notification: Cisco IOS XR communicates the loss anomaly to the IS-IS routing process.
Metric adjustment: The metric fallback anomaly loss command on the affected interface instructs IS-IS to modify the interface metric.
Traffic rerouting: IS-IS recalculates its shortest path, and Cisco IOS XR reroutes traffic from Path 1 to Path 2.
Anomaly recovery: When packet loss recedes below the lower-bound threshold:
- The synthetic loss measurement system clears the anomaly
- IS-IS reverts the interface metric to its original value
- Cisco IOS XR software reroutes traffic back to Path 1

Configure IS-IS penalty for link loss anomaly

Apply IS-IS penalties for link loss anomalies to improve routing calculation integrity.

Use this task when you need to adjust IS-IS metrics in response to link loss events, ensuring accurate path selection and mitigating the impact of unstable links.

Procedure

Enter the IS-IS interface configuration mode, and configure point-to-point service under the IS-IS interface.

Example:

Router# configure terminal
Router(config)# router isis 1
Router(config-isis)# interface GigabitEthernet0/2/0/1
Router(config-isis-if)# point-to-point

Configure the metric fallback anomaly loss increment for both IPv4 and IPv6 address families.

Example:

Router(config-isis-if)# address-family ipv4 unicast
Router(config-isis-if-af)# metric fallback anomaly loss increment 500
Router(config-isis-if-af)# exit
Router(config-isis-if)# address-family ipv6 unicast
Router(config-isis-if-af)# metric fallback anomaly loss increment 500
Router(config-isis-if-af)# exit
Router(config-isis-if)# exit
Router(config-isis)# commit

Use the show isis database verbose command to verify the metric fallback anomaly loss increment configuration.

Example:

Router# show isis database verbose r100
Fri Oct 11 10:49:17.836 PDT
IS-IS 1 (Level-2) Link State Database
LSPID LSP Seq Num LSP Checksum LSP Holdtime/Rcvd ATT/P/OL
r100.00-00 * 0x0000000b 0xc725 1188 /* 0/0/0 Metric: 10 IS-Extended r101.00 Local Interface ID: 10, Remote Interface ID: 7 Interface IP Address: 10.1.1.100 Neighbor IP Address: 10.1.1.101 Physical BW: 1000000 kbits/sec, 125000000 bytes/sec Link Average Delay: 704 us Link Min/Max Delay: 483/871 us Link Delay Variation: 127 us Metric: 10         MT (IPv6 Unicast) IS-Extended r101.00 Local Interface ID: 10, Remote Interface ID: 7 Interface IPv6 Address: 2001:1000::100 Neighbor IPv6 Address: 2001:1000::101 Physical BW: 1000000 kbits/sec, 125000000 bytes/sec Link Average Delay: 704 us Link Min/Max Delay: 483/871 us Link Delay Variation: 127 us Total Level-2 LSP count: 1 Local Level-2 LSP count: 1

Need help?

Open a support case

(Requires a Cisco Service Contract)

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.