Table 2. Feature History Table
|
Feature Name
|
Release Information
|
Feature Description
|
|
SR-ODN: Layer 3 IPv6 BGP Services
|
Release 7.9.1 |
Segment Routing On-Demand Next Hop (SR-ODN) allows a service head-end router to automatically instantiate an SR policy to
a BGP next-hop when required (on-demand).
This feature introduces support for Layer 3 IPv6 BGP services (VPNv4/VPNv6) over SR-ODN.
|
The following examples show end-to-end configurations used in implementing SR-ODN on the head-end router.
Configuring ODN Color Templates: Example
Configure ODN color templates on routers acting as SR-TE head-end nodes. The following example shows various ODN color templates:
-
color 10: minimization objective = te-metric
-
color 20: minimization objective = igp-metric
-
color 21: minimization objective = igp-metric; constraints = affinity
-
color 22: minimization objective = te-metric; path computation at SR-PCE; constraints = affinity
-
color 30: minimization objective = delay-metric
-
color 128: constraints = flex-algo
segment-routing
traffic-eng
on-demand color 10
dynamic
metric
type te
!
!
!
on-demand color 20
dynamic
metric
type igp
!
!
!
on-demand color 21
dynamic
metric
type igp
!
affinity exclude-any
name CROSS
!
!
!
on-demand color 22
dynamic
pcep
!
metric
type te
!
affinity exclude-any
name CROSS
!
!
!
on-demand color 30
dynamic
metric
type latency
!
!
!
on-demand color 128
dynamic
sid-algorithm 128
!
!
!
end
Configuring BGP Color Extended Community Set: Example
The following example shows how to configure BGP color extended communities that are later applied to BGP service routes via
route-policies.
Note
|
In most common scenarios, egress PE routers that advertise BGP service routes apply (set) BGP color extended communities.
However, color can also be set at the ingress PE router.
|
extcommunity-set opaque color10-te
10
end-set
!
extcommunity-set opaque color20-igp
20
end-set
!
extcommunity-set opaque color21-igp-excl-cross
21
end-set
!
extcommunity-set opaque color30-delay
30
end-set
!
extcommunity-set opaque color128-fa128
128
end-set
!
Configuring RPL to Set BGP Color (Layer-3 Services): Examples
The following example shows various representative RPL definitions that set BGP color community.
The first four RPL examples include the set color action only. The last RPL example performs the set color action for selected destinations based on a prefix-set.
route-policy SET_COLOR_LOW_LATENCY_TE
set extcommunity color color10-te
pass
end-policy
!
route-policy SET_COLOR_HI_BW
set extcommunity color color20-igp
pass
end-policy
!
route-policy SET_COLOR_LOW_LATENCY
set extcommunity color color30-delay
pass
end-policy
!
route-policy SET_COLOR_FA_128
set extcommunity color color128-fa128
pass
end-policy
!
prefix-set sample-set
192.68.0.0/24
end-set
!
route-policy SET_COLOR_GLOBAL
if destination in sample-set then
set extcommunity color color10-te
else
pass
endif
end-policy
Applying RPL to BGP Services (Layer-3 Services): Example
The following example shows various RPLs that set BGP color community being applied to BGP Layer-3 VPN services (VPNv4/VPNv6)
and BGP global.
vrf vrf_cust1
address-family ipv4 unicast
export route-policy SET_COLOR_LOW_LATENCY_TE
!
address-family ipv6 unicast
export route-policy SET_COLOR_LOW_LATENCY_TE
!
!
vrf vrf_cust2
address-family ipv4 unicast
export route-policy SET_COLOR_HI_BW
!
address-family ipv6 unicast
export route-policy SET_COLOR_HI_BW
!
!
vrf vrf_cust3
address-family ipv4 unicast
export route-policy SET_COLOR_LOW_LATENCY
!
address-family ipv6 unicast
export route-policy SET_COLOR_LOW_LATENCY
!
!
vrf vrf_cust4
address-family ipv4 unicast
export route-policy SET_COLOR_FA_128
!
address-family ipv6 unicast
export route-policy SET_COLOR_FA_128
!
!
router bgp 100
neighbor-group BR-TO-RR
address-family ipv4 unicast
route-policy SET_COLOR_GLOBAL out
!
!
!
end
L3VPN IPv4 Services: Verifying BGP VRF Information
Use the show bgp vrf command to display BGP prefix information for VRF instances. The following output shows the BGP VRF table including a prefix
(88.1.1.0/24) with color 10 advertised by router 1.1.1.8.
Router# show bgp vrf vrf_cust1
BGP VRF vrf_cust1, state: Active
BGP Route Distinguisher: 1.1.1.4:101
VRF ID: 0x60000007
BGP router identifier 1.1.1.4, local AS number 100
Non-stop routing is enabled
BGP table state: Active
Table ID: 0xe0000007 RD version: 282
BGP main routing table version 287
BGP NSR Initial initsync version 31 (Reached)
BGP NSR/ISSU Sync-Group versions 0/0
Status codes: s suppressed, d damped, h history, * valid, > best
i - internal, r RIB-failure, S stale, N Nexthop-discard
Origin codes: i - IGP, e - EGP, ? - incomplete
Network Next Hop Metric LocPrf Weight Path
Route Distinguisher: 1.1.1.4:101 (default for vrf vrf_cust1)
*> 44.1.1.0/24 40.4.101.11 0 400 {1} i
*>i55.1.1.0/24 1.1.1.5 100 0 500 {1} i
*>i88.1.1.0/24 1.1.1.8 C:10 100 0 800 {1} i
*>i99.1.1.0/24 1.1.1.9 100 0 800 {1} i
Processed 4 prefixes, 4 paths
The following output displays the details for prefix 88.1.1.0/24. Note the presence of BGP extended color community 10, and
that the prefix is associated with an SR policy with color 10 and BSID value of 24036.
Router# show bgp vrf vrf_cust1 88.1.1.0/24
BGP routing table entry for 88.1.1.0/24, Route Distinguisher: 1.1.1.4:101
Versions:
Process bRIB/RIB SendTblVer
Speaker 282 282
Last Modified: May 20 09:23:34.112 for 00:06:03
Paths: (1 available, best #1)
Advertised to CE peers (in unique update groups):
40.4.101.11
Path #1: Received by speaker 0
Advertised to CE peers (in unique update groups):
40.4.101.11
800 {1}
1.1.1.8 C:10 (bsid:24036) (metric 20) from 1.1.1.55 (1.1.1.8)
Received Label 24012
Origin IGP, localpref 100, valid, internal, best, group-best, import-candidate, imported
Received Path ID 0, Local Path ID 1, version 273
Extended community: Color:10 RT:100:1
Originator: 1.1.1.8, Cluster list: 1.1.1.55
SR policy color 10, up, registered, bsid 24036, if-handle 0x08000024
Source AFI: VPNv4 Unicast, Source VRF: default, Source Route Distinguisher: 1.1.1.8:101
L3VPN IPv4 Services: Verifying Forwarding (CEF) Table
Use the show cef vrf command to display the contents of the CEF table for the VRF instance. Note that prefix 198.51.100.1/24 points to the BSID
label corresponding to an SR policy. Other non-colored prefixes, such as 192.0.2.2/24, point to BGP next-hop.
Router# show cef vrf vrf_cust1
Prefix Next Hop Interface
------------------- ------------------- ------------------
0.0.0.0/0 drop default handler
0.0.0.0/32 broadcast
10.0.0.1/8 attached TenGigE0/0/0/0.101
172.16.0.1/12 broadcast TenGigE0/0/0/0.101
172.16.0.2/12 receive TenGigE0/0/0/0.101
172.16.0.3/12 172.16.0.3/12 TenGigE0/0/0/0.101
172.16.0.4/12 broadcast TenGigE0/0/0/0.101
192.168.0.1/16 172.16.0.3/12 <recursive>
192.0.2.2/24 10.0.0.2/8 <recursive>
198.51.100.1/24 24036 (via-label) <recursive>
The following output displays CEF details for prefix 198.51.100.1/24. Note that the prefix is associated with an SR policy
with BSID value of 24036.
Router# show cef vrf vrf_cust1 198.51.100.1/24
198.51.100.1/24, version 51, internal 0x5000001 0x0 (ptr 0x98c60ddc) [1], 0x0 (0x0), 0x208 (0x98425268)
Updated May 20 09:23:34.216
Prefix Len 24, traffic index 0, precedence n/a, priority 3
via local-label 24036, 5 dependencies, recursive [flags 0x6000]
path-idx 0 NHID 0x0 [0x97091ec0 0x0]
recursion-via-label
next hop VRF - 'default', table - 0xe0000000
next hop via 24036/0/21
next hop srte_c_10_ep labels imposed {ImplNull 24012}
L3VPN IPv4 Services: Verifying SR Policy
Use the show segment-routing traffic-eng policy command to display SR policy information.
The following outputs show the details of an on-demand SR policy that was triggered by prefixes with color 10 advertised by
node 10.0.0.8.
Router# show segment-routing traffic-eng policy color 10 tabular
Color Endpoint Admin Oper Binding
State State SID
------ -------------------- ------ ------ --------------------
10 10.0.0.8 up up 24036
The following outputs show the details of the on-demand SR policy for BSID 24036.
Note
|
There are 2 candidate paths associated with this SR policy: the path that is computed by the head-end router (with preference
200), and the path that is computed by the SR-PCE (with preference 100). The candidate path with the highest preference is
the active candidate path (highlighted below) and is installed in forwarding.
|
Router# show segment-routing traffic-eng policy binding-sid 24036
SR-TE policy database
---------------------
Color: 10, End-point: 10.0.0.8
Name: srte_c_10_ep_10.0.0.8
Status:
Admin: up Operational: up for 4d14h (since Jul 3 20:28:57.840)
Candidate-paths:
Preference: 200 (BGP ODN) (active)
Requested BSID: dynamic
PCC info:
Symbolic name: bgp_c_10_ep_10.0.0.8_discr_200
PLSP-ID: 12
Dynamic (valid)
Metric Type: TE, Path Accumulated Metric: 30
16009 [Prefix-SID, 10.0.0.9]
16008 [Prefix-SID, 10.0.0.8]
Preference: 100 (BGP ODN)
Requested BSID: dynamic
PCC info:
Symbolic name: bgp_c_10_ep_10.0.0.8_discr_100
PLSP-ID: 11
Dynamic (pce 10.0.0.57) (valid)
Metric Type: TE, Path Accumulated Metric: 30
16009 [Prefix-SID, 10.0.0.9]
16008 [Prefix-SID, 10.0.0.8]
Attributes:
Binding SID: 24036
Forward Class: 0
Steering BGP disabled: no
IPv6 caps enable: yes
L3VPN IPv4 Services: Verifying SR Policy Forwarding
Use the show segment-routing traffic-eng forwarding policy command to display the SR policy forwarding information.
The following outputs show the forwarding details for an on-demand SR policy that was triggered by prefixes with color 10
advertised by node 10.0.0.8.
Router# show segment-routing traffic-eng forwarding policy binding-sid 24036 tabular
Color Endpoint Segment Outgoing Outgoing Next Hop Bytes Pure
List Label Interface Switched Backup
----- --------------- ------------ -------- ------------ ------------ ------------ ------
10 10.0.0.8 dynamic 16009 Gi0/0/0/4 10.4.5.5 0
16001 Gi0/0/0/5 10.5.8.8 0 Yes
Router# show segment-routing traffic-eng forwarding policy binding-sid 24036 detail
Mon Jul 8 11:56:46.887 PST
SR-TE Policy Forwarding database
--------------------------------
Color: 10, End-point: 10.0.0.8
Name: srte_c_10_ep_10.0.0.8
Binding SID: 24036
Segment Lists:
SL[0]:
Name: dynamic
Paths:
Path[0]:
Outgoing Label: 16009
Outgoing Interface: GigabitEthernet0/0/0/4
Next Hop: 10.4.5.5
Switched Packets/Bytes: 0/0
FRR Pure Backup: No
Label Stack (Top -> Bottom): { 16009, 16008 }
Path-id: 1 (Protected), Backup-path-id: 2, Weight: 64
Path[1]:
Outgoing Label: 16001
Outgoing Interface: GigabitEthernet0/0/0/5
Next Hop: 10.5.8.8
Switched Packets/Bytes: 0/0
FRR Pure Backup: Yes
Label Stack (Top -> Bottom): { 16001, 16009, 16008 }
Path-id: 2 (Pure-Backup), Weight: 64
Policy Packets/Bytes Switched: 0/0
Local label: 80013
L3VPN IPv6 Services: Verifying BGP VRF Information
Use the show bgp vrf command to display BGP prefix information for VRF instances.
The following output displays the details for prefix 2020:0:0:1::. Note the presence of BGP extended color community 10, and
that the prefix is associated with an SR policy with color 10 and BSID value of 51006.
Router# show bgp vrf vrf_cust1 ipv6 unicast 2020:0:0:1::
BGP routing table entry for 2020:0:0:1::/64, Route Distinguisher: 100:1001
Versions:
Process bRIB/RIB SendTblVer
Speaker 66662 66662
Last Modified: Mar 16 09:18:40.678 for 00:01:36
Paths: (1 available, best #1)
Advertised to CE peers (in unique update groups):
2002::6701:b02
Path #1: Received by speaker 0
Advertised to CE peers (in unique update groups):
2002::6701:b02
2001
100.2.1.1 C:10 (bsid:51006) (metric 40) from 100.2.1.1 (100.2.1.1)
Received Label 51000
Origin IGP, localpref 100, valid, internal, best, group-best, import-candidate, imported
Received Path ID 1, Local Path ID 1, version 49971
Extended community: Color[CO-Flag]:10[10] RT:100:1
SR policy color 10, up, registered, bsid 51006, if-handle 0x0f000c9c
Source AFI: VPNv6 Unicast, Source VRF: default, Source Route Distinguisher: 100:2001[0m
L3VPN IPv6 Services: Verifying Forwarding (CEF) Table
Use the show cef vrf command to display the contents of the CEF table for the VRF instance.
The following output displays CEF details for prefix 2020:0:0:1::/64. Note that the prefix is associated with an SR policy
with BSID value of 51006.
Router# show cef vrf vrf_cust1 ipv6 2020:0:0:1:: detail
2020:0:0:1::/64, version 229, internal 0x5000001 0x30 (ptr 0xba4b9050) [1], 0x0 (0x0), 0x208 (0x9a6e3858)
Updated Mar 16 09:18:41.170
Prefix Len 64, traffic index 0, precedence n/a, priority 3
gateway array (0xbc2fe5d0) reference count 16, flags 0x2038, source rib (7), 0 backups
[1 type 1 flags 0x48441 (0xbe849048) ext 0x0 (0x0)]
LW-LDI[type=0, refc=0, ptr=0x0, sh-ldi=0x0]
gateway array update type-time 1 Mar 16 09:18:41.170
LDI Update time Mar 16 09:18:41.170
via local-label 51006, 3 dependencies, recursive [flags 0x6000]
path-idx 0 NHID 0x0 [0x9a86d0e0 0x0]
recursion-via-label
next hop VRF - 'default', table - 0xe0000000
next hop via 51006/0/21
labels imposed {51000}
Load distribution: 0 (refcount 1)
Hash OK Interface Address
0 Y recursive 51006/0 [0m
L3VPN IPv6 Services: Verifying SR Policy
Use the show segment-routing traffic-eng policy command to display SR policy information.
Router# show segment-routing traffic-eng policy endpoint ipv4 100.2.1.1 color 10
SR-TE policy database
---------------------
Color: 10, End-point: 100.2.1.1
Name: srte_c_10_ep_100.2.1.1
Status:
Admin: up Operational: up for 00:01:21 (since Mar 16 09:18:41.096)
Candidate-paths:
Preference: 200 (BGP ODN) (active)
Requested BSID: dynamic
Constraints:
Protection Type: protected-preferred
Maximum SID Depth: 8
Dynamic (valid)
Metric Type: TE, Path Accumulated Metric: 30
SID[0]: 51002 [Adjacency-SID, 101.1.3.1 - 101.1.3.2]
SID[1]: 41304 [Adjacency-SID, 101.3.4.1 - 101.3.4.2]
SID[2]: 41400 [Adjacency-SID, 101.2.4.2 - 101.2.4.1]
Preference: 100 (BGP ODN) (inactive)
Requested BSID: dynamic
PCC info:
Symbolic name: bgp_c_10_ep_100.2.1.1_discr_100
PLSP-ID: 3
Constraints:
Protection Type: protected-preferred
Maximum SID Depth: 8
Dynamic (pce) (inactive)
Metric Type: NONE, Path Accumulated Metric: 0
Attributes:
Binding SID: 51006
Forward Class: Not Configured
Steering labeled-services disabled: no
Steering BGP disabled: no
IPv6 caps enable: yes
Invalidation drop enabled: no
Max Install Standby Candidate Paths: 0
Feedback