Segment Routing TE
Configure Segment Routing Traffic Engineering (SR-TE) on IOS-XR devices including PCEP (Path Computation Element Protocol) settings and PCE peers. This feature enables advanced traffic engineering capabilities using segment routing with both SR-MPLS and SRv6 data planes.
Diagram
Section titled “Diagram”Classes
Section titled “Classes”configuration (iosxr.devices)
Section titled “configuration (iosxr.devices)”| Name | Type | Constraint | Mandatory | Default Value |
|---|---|---|---|---|
| segment_routing_te | Class | [segment_routing_te] | No |
segment_routing_te (iosxr.devices.configuration)
Section titled “segment_routing_te (iosxr.devices.configuration)”| Name | Type | Constraint | Mandatory | Default Value |
|---|---|---|---|---|
| logging_pcep_peer_status | Boolean | true, false | No | |
| logging_policy_status | Boolean | true, false | No | |
| pcc_dead_timer | Integer | min: 1, max: 255 | No | |
| pcc_delegation_timeout | Integer | min: 0, max: 1576800000 | No | |
| pcc_initiated_orphan | Integer | min: 0, max: 180 | No | |
| pcc_initiated_state | Integer | min: 0, max: 86400 | No | |
| pcc_report_all | Boolean | true, false | No | |
| pcc_source_address_ipv4 | IP | No | ||
| pce_peers_ipv4 | List | [pce_peers_ipv4] | No |
pce_peers_ipv4 (iosxr.devices.configuration.segment_routing_te)
Section titled “pce_peers_ipv4 (iosxr.devices.configuration.segment_routing_te)”| Name | Type | Constraint | Mandatory | Default Value |
|---|---|---|---|---|
| pce_address | IP | Yes | ||
| precedence | Integer | min: 0, max: 255 | No |
Sample Configuration:
Section titled “Sample Configuration:”The following configuration describes how to set up Segment Routing Traffic Engineering on a Cisco IOS-XR device.
segment-routing traffic-engineering logging pcep peer-status policy status pcc source-address <ip-address> delegation-timeout <seconds> dead-timer <seconds> initiated-state <seconds> initiated-orphan <seconds> report-all pce address <pce-ip> precedence <value>Example YAML Code:
Section titled “Example YAML Code:”Example-1: Basic PCEP configuration with single PCE peer
iosxr: devices: - name: router-1 host: 10.10.10.1:57400 configuration: segment_routing_te: logging_pcep_peer_status: true logging_policy_status: true pcc_source_address_ipv4: "10.1.1.1" pce_peers_ipv4: - pce_address: "10.1.1.100" precedence: 100Example-2: Comprehensive SR-TE configuration with PCC settings
iosxr: devices: - name: router-1 host: 10.10.10.1:57400 configuration: segment_routing_te: logging_pcep_peer_status: true logging_policy_status: true pcc_report_all: true pcc_source_address_ipv4: "88.88.88.8" pcc_delegation_timeout: 10 pcc_dead_timer: 60 pcc_initiated_state: 15 pcc_initiated_orphan: 10 pce_peers_ipv4: - pce_address: "66.66.66.6" precedence: 122Example-3: Multiple PCE peers with redundancy
iosxr: devices: - name: router-1 host: 10.10.10.1:57400 configuration: segment_routing_te: logging_pcep_peer_status: true pcc_source_address_ipv4: "10.1.1.1" pcc_dead_timer: 120 pce_peers_ipv4: - pce_address: "10.1.1.100" precedence: 200 - pce_address: "10.1.1.101" precedence: 100Example-4: Minimal SR-TE configuration
iosxr: devices: - name: router-1 host: 10.10.10.1:57400 configuration: segment_routing_te: pcc_source_address_ipv4: "10.1.1.1"Use Cases:
Section titled “Use Cases:”- PCE Integration: Centralized path computation for network-wide optimization
- PCEP Configuration: Configure Path Computation Element Protocol settings
- Traffic Engineering Foundation: Base configuration for SR-TE capabilities
- Redundant PCE Setup: Configure multiple PCE peers for high availability