Segment Routing v6 Configuration Guide for Cisco 8000 Series Routers, Cisco IOS XR Releases

PDF

Segment Routing v6 Configuration Guide for Cisco 8000 Series Routers, Cisco IOS XR Releases

SRv6 OAM SID verification

Updated: September 8, 2026

Want to summarize with AI?

Log in

Explains this feature provides enhanced Operations, Administration, and Maintenance (OAM) in Segment Routing Networks with IPv6 Data plane (SRv6).

A SRv6 OAM SID is a special Segment Identifier (SID) allocated in Segment Routing with IPv6 (SRv6) networks that

  • enhances Operations, Administration, and Maintenance (OAM) protocols by enabling direct verification of SRv6 endpoints,

  • augments standard OAM mechanisms (ping and trace) with the ability to target remote SRv6 SID functions, and

  • is automatically allocated by an SRv6-capable router as the END.OP SID (OAM Endpoint with Punt).

Table 1. Table 1. Feature History Table

Feature Name

Release Information

Feature Description
SRv6 OAM— SID Verification Release 25.4.1

Introduced in this release on: Fixed Systems (8700 [ASIC: K100,8010 [ASIC: A100])(select variants only*)

*This feature is now supported on:

  • 8711-48Z-M

  • 8011-32Y8L2H2FH

  • 8011-12G12X4Y-A/D
SRv6 OAM— SID Verification

Release 25.1.1

Introduced in this release on: Fixed Systems (8010 [ASIC: A100])(select variants only*)

*This feature is supported on Cisco 8011-4G24Y4H-I routers.
SRv6 OAM— SID Verification

Release 24.4.1

Introduced in this release on: Fixed Systems (8200 [ASIC: P100], 8700 [ASIC: P100, K100])(select variants only*); Modular Systems (8800 [LC ASIC: P100])(select variants only*)

This feature provides enhanced Operations, Administration, and Maintenance (OAM) in Segment Routing Networks with IPv6 Data plane (SRv6).

*This feature is supported on:

  • 8212-48FH-M

  • 8711-32FH-M

  • 8712-MOD-M

  • 88-LC1-36EH

  • 88-LC1-12TH24FH-E

  • 88-LC1-52Y8H-EM
SRv6 OAM— SID Verification

Release 7.5.2

This feature provides enhanced Operations, Administration, and Maintenance (OAM) in Segment Routing Networks with IPv6 Data plane (SRv6).

Existing OAM mechanisms to ping and trace a remote IPv6 prefix, along the shortest path, continue to work without any modification in an SRv6 network.

However, classic IPv6 OAM cannot be used to ping or trace a remote SRv6 SID function. This feature augments ping and traceroute operations to target remote SRv6 SIDs. An SRv6-enabled router now allocates a new SRv6 OAM SID known as END.OP (OAM Endpoint with Punt).

Key features of SRv6 OAM-SID

SRv6 OAM SIDs extend standard Operations, Administration, and Maintenance (OAM) in Segment Routing IPv6 by supporting targeted ping and traceroute operations to remote SIDs that standard tools cannot directly test.

SRv6 OAM SIDs specifically extend the OAM process by allowing targeted ping and traceroute operations on remote SIDs. This enhancement enables more effective troubleshooting and verification in SRv6 deployments.

Key features of SRv6 OAM SIDs include:

  • Targeted OAM operations: Allow direct use of ping and traceroute commands on remote SRv6 SIDs, extending beyond traditional OAM limitations.

  • SID-specific testing: Enable testing and validation of functions tied to specific SRv6 SIDs at remote nodes.

  • Network-wide visibility: Provide improved troubleshooting and verification for SRv6 deployments.

END.OP SID derivation

The ingress node can automatically derive the END.OP SID associated with a specified target SID by leveraging the IGP topology database in that node. The database will contain END.OP SIDs from remote nodes.

An END.OP SID associated with a locator will be advertised by IS-IS within an IGP domain in an area or level, which is added to the topology database. However, END.OP SIDs are not redistributed by IS-IS across IGP domains or across different area or level within an IGP domain. In this case, the topology database in a node contains END.OP SIDs only from the nodes within the same IGP domain in an area/level. An END.OP SID cannot be determined automatically if the specified target SID is external to the domain. For target SIDs across IGP domains or across different area/level within an IGP domain, the end.op-sid-value must be explicitly provided.

If end.op-sid-value is not provided and the END.OP SID cannot be automatically derived, an error is displayed prompting the user to provide the end.op-sid-value .