Step 1
| show isis segment-routing
Verifies that the network is Strict SID capable.
Example:
Router# show isis segment-routing
ISIS protocol is registered with MFI
ISIS MFI Client ID:0x63
Tag SR - Segment-Routing:
SR State:SR_ENABLED
Number of SRGB:1
SRGB Start:16000, Range:8000, srgb_handle:0x7FD14D47DEE0, srgb_state: created
Address-family IPv4 unicast SR is configured
Operational state:Enabled
Maximum encapsulation labels for SR tunnel: 13
Level-1 is strict-spf capabled
Level-2 is strict-spf capabled
Prefix-sid-map receive is enabled
Advertise local is enabled
Explicit null is disabled
SR label preferred is enabled
Verifies that the Strict SID labels are populated in the MPLS Forwarding Table (LFIB).
- The highlighted line in the output indicates the Strict Shortest Path First label.
Example:
Router# show mpls forwarding-table
Local Outgoing Prefix Bytes Label Outgoing Next Hop
Label Label or Tunnel Id Switched interface
16 Pop Label 1.1.1.2-A 0 Et0/0 1.1.1.2
17 Pop Label 1.1.1.2-A 0 Et0/0 1.1.1.2
18 Pop Label 1.1.1.2-A 0 Et0/0 1.1.1.2
19 Pop Label 15.15.15.2-A 0 Et0/1 15.15.15.2
20 Pop Label 15.15.15.2-A 0 Et0/1 15.15.15.2
21 Pop Label 15.15.15.2-A 0 Et0/1 15.15.15.2
22 [T] Pop Label 1/1[TE-Bind] 0 Tu1 point2point
16110 Pop Label 20.20.20.20/32 0 Et0/0 1.1.1.2
16120 16120 30.30.30.30/32 0 Et0/0 1.1.1.2
16130 16130 40.40.40.40/32 0 Et0/0 1.1.1.2
[T] 16130 40.40.40.40/32 0 Tu1 point2point
16140 [T] Pop Label 50.50.50.50/32 0 Tu1 point2point
16200 Pop Label 100.100.100.100/32 \
0 Et0/1 15.15.15.2
17100 Pop Label 0-20.20.20.20/32-0 \
0 Et0/0 1.1.1.2
17200 17200 0-30.30.30.30/32-0 \
0 Et0/0 1.1.1.2
17300 17300 0-40.40.40.40/32-0 \
0 Et0/1 15.15.15.2
17400 17400 0-50.50.50.50/32-0 \
0 Et0/1 15.15.15.2
18000 Pop Label 0-100.100.100.100/32-0 \
0 Et0/1 15.15.15.2
[T] Forwarding through a LSP tunnel.
View additional labelling info with the 'detail' option
A - Adjacency SID
|
Step 2
|
Verifies that Strict Shortest Path First segment identifier labels are populated in the traffic engineering database.
Example:
Router# show mpls traffic-engineering segment-routing summary
IGP Area[1]: isis level-1, Strict SPF Enabled:
Nodes:
IGP Id: 0010.0100.1001.00, MPLS TE Id: 10.10.10.10, ISIS level-1
2 links with segment-routing adjacency SID
IGP Id: 0020.0200.2002.00, MPLS TE Id: 20.20.20.20, ISIS level-1
2 links with segment-routing adjacency SID
IGP Id: 0030.0300.3003.00, MPLS TE Id: 30.30.30.30, ISIS level-1
2 links with segment-routing adjacency SID
IGP Id: 0040.0400.4004.00, MPLS TE Id: 40.40.40.40, ISIS level-1
2 links with segment-routing adjacency SID
IGP Id: 0050.0500.5005.00, MPLS TE Id: 50.50.50.50, ISIS level-1
2 links with segment-routing adjacency SID
IGP Id: 0060.0600.6006.00, MPLS TE Id: 100.100.100.100, ISIS level-1
2 links with segment-routing adjacency SID
Prefixes:
10.10.10.10/32, SID index: 100, Strict SID index: 1000
20.20.20.20/32, SID index: 110, Strict SID index: 1100
30.30.30.30/32, SID index: 120, Strict SID index: 1200
40.40.40.40/32, SID index: 130, Strict SID index: 1300
50.50.50.50/32, SID index: 140, Strict SID index: 1400
100.100.100.100/32, SID index: 200, Strict SID index: 2000
Total:
Node Count : 6
Adjacency-SID Count: 12
Prefix-SID Count : 6
IGP Area[2]: isis level-2, Strict SPF Enabled:
Nodes:
IGP Id: 0010.0100.1001.00, MPLS TE Id: 10.10.10.10, ISIS level-2
2 links with segment-routing adjacency SID
IGP Id: 0020.0200.2002.00, MPLS TE Id: 20.20.20.20, ISIS level-2
2 links with segment-routing adjacency SID
IGP Id: 0030.0300.3003.00, MPLS TE Id: 30.30.30.30, ISIS level-2
2 links with segment-routing adjacency SID
IGP Id: 0040.0400.4004.00, MPLS TE Id: 40.40.40.40, ISIS level-2
2 links with segment-routing adjacency SID
IGP Id: 0050.0500.5005.00, MPLS TE Id: 50.50.50.50, ISIS level-2
2 links with segment-routing adjacency SID
IGP Id: 0060.0600.6006.00, MPLS TE Id: 100.100.100.100, ISIS level-2
2 links with segment-routing adjacency SID
Prefixes:
10.10.10.10/32, SID index: 100
Total:
Node Count : 6
Adjacency-SID Count: 24
Prefix-SID Count : 1
Grand Total:
Node Count : 12
Adjacency-SID Count: 36
Prefix-SID Count : 7
IGP Areas Count : 2
|
Step 3
|
Verifies that the segment routing traffic engineering tunnel uses Strict Shortest Path First segment identifier to establish tunnels.
Example:
Router1# show mpls traffic-engineering tunnels tunnel 1
Name: PE1_t1 (Tunnel1) Destination: 50.50.50.50
Status:
Admin: up Oper: up Path: valid Signalling: connected
path option 10, (SEGMENT-ROUTING) type explicit SR (Basis for Setup)
Config Parameters:
Bandwidth: 200 kbps (Global) Priority: 7 7 Affinity: 0x0/0xFFFF
Metric Type: TE (default)
Path Selection:
Protection: any (default)
Path-selection Tiebreaker:
Global: not set Tunnel Specific: not set Effective: min-fill (default)
Hop Limit: disabled [ignore: Explicit Path Option with all Strict Hops]
Cost Limit: disabled
Path-invalidation timeout: 10000 msec (default), Action: Tear
AutoRoute: enabled LockDown: disabled Loadshare: 200 [10000000] bw-based
auto-bw: disabled
Fault-OAM: disabled, Wrap-Protection: disabled, Wrap-Capable: No
Active Path Option Parameters:
State: explicit path option 10 is active
BandwidthOverride: disabled LockDown: disabled Verbatim: disabled
History:
Tunnel:
Time since created: 22 seconds
Time since path change: 21 seconds
Number of LSP IDs (Tun_Instances) used: 1
Current LSP: [ID: 1]
Uptime: 21 seconds
Tun_Instance: 1
Segment-Routing Path Info (isis level-1), Strict
Segment0[Node]: 20.20.20.20, Label: 17100
Segment1[Node]: 30.30.30.30, Label: 17200
Segment2[Node]: 40.40.40.40, Label: 17300
Segment3[Node]: 50.50.50.50, Label: 17400
|