BRKSPG 2518 PDF

BRKSPG-2518
Service Provider
Programmable SDN
Solution for the Metro
Fabric, powered by
Segment Routing and EVPN
Jiri Chaloupka - Technical Marketing Engineer
Software-Defined (SDN) and Intent-Based Networking
Agenda Cisco Service Provider SDN
• Segment Routing (SR) Programmable Transport
• MPLS – Data Plane
• IPv6 – Data Plane
• Fast Convergence - Topology Independent LFA
• Traffic Engineering - SRTE
• Transport Simplification
+ Seamless Integration with existing Solution!
Cisco Service Provider Intent-Based Networking

• Transport and Services Integration – On-Demand Next Hop
• SLA Based Forwarding
• Performance Monitoring
• Flex-Algo
• Unified Service Control Plane – BGP (VPNv4/6, EVPN)
• Unified Transport Data Plane across Metro, Core, NG-CO – SR
BRKSPG-2518 © 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public 3
Unified MPLS Transport Model Baseline – Reminder
Fixed Access Aggregation Core Aggregation Mobile Access

Network Network Network Network Network
IS-IS L1 IS-IS L2 IS-IS L2 IS-IS L2 IS-IS L1
AS-B AS-A AS-C
PAN AGN-ASBR CN-ASBR CN-ASBR AGN-ASBR PAN

Inline RR  next-hop-self   next-hop-self   next-hop-self   next-hop-self  Inline RR
 next-hop-self   next-hop-self 
eBGP eBGP
IPv4+label IPv4+label CSG
MTG
FAN
iBGP
iBGP AGN-RR CN-RR AGN-RR IPv4+label
IPv4+label
RR RR RR
iBGP iBGP CSG
IPv4+label iBGP
FAN IPv4+label IPv4+label
MTG
CSG
AGN-SE
FAN
iBGP Hierarchical LSP eBGP LSP iBGP Hierarchical LSP eBGP LSP iBGP Hierarchical LSP
LDP LSP LDP LSP LDP LSP LDP LSP LDP LSP
Service Provider Network - Simplification Journey
Compass
Unified MPLS EPN 5.0 Metro Fabric
Provisioning NETCONF NETCONF
YANG YANG
Programmability
L2/L3VPN Services LDP BGP LDP BGP BGP
Inter-Domain CP BGP-LU BGP-LU

FRR or TE RSVP
IGP with SR
LDP IGP with SR
Intra-Domain CP
IGP
Intra-Domain Transport -
Segment Routing MPLS
Intra-Domain Simplification by Segment Routing
Compass
YANG YANG
Programmability

FRR or TE RSVP
IGP with SR
LDP IGP with SR
Intra-Domain CP
IGP
The 2 faces
Why Segment Routing - MPLS of segment
routing
An LS IGP protocol extension
An IP/MPLS architecture
bringing network
designed with SDN in mind
simplification/optimization
• No LDP
• Lighter protocol suite • Right balance between
• Less adjacencies, less states to distributed intelligence and
maintain centralized optimization and
• No IGP to LDP synchronization programming
• Eliminates delays in activating a path • SR-TE
• Topology independent fast reroute using • Wide applications
post convergence back up path • (SP, OTT/Web, GET) across
• 50 ms protection (WAN, Metro/Agg, DC)
• no microloops • MPLS and IPv6 dataplanes
• 100% coverage of network topologies • SDN controller
Easy troubleshooting
Segment Routing
Segment(s) Data
Data Plane
MPLS IPv6
(segment labels) (+ SR extension header)
1 2 Control Plane
Routing protocols with SDN controller

extensions ( BGP , PCEP,
5 (IS-IS,OSPF, BGP) NETCONF/YANG)
Paths options
3 4 Dynamic
(STP computation)
Explicit
(expressed in the packet)
IGP Prefix Segment Example 1: Best Path
16005
• Signaled by ISIS/OSPF 1.1.1.5/32
• Minor extensions to existing link-
state routing protocols 1 2 16005
• Shortest-path to IGP prefix 16005
• Equal Cost MultiPath (ECMP)-aware 16005
• Global significance in SR domain

5
16005
• Label = SRGB + Index 16005
SRGB = Segment Routing Global

•
Block 3 4
• Default SRGB: 16,000 – 23,999
• Advertised as index 16005
All nodes use default SRGB
16,000 – 23,999
IGP Prefix Segment Example 2: ECMP
• Signaled by ISIS/OSPF 16004

state routing protocols 1 2
• Shortest-path to IGP prefix 16004
• Equal Cost MultiPath (ECMP)-aware 16004
• Global significance in SR domain 16004

5
16004
• Label = SRGB + Index
16004
SRGB = Segment Routing Global

•
Block 3 4
• Default SRGB: 16,000 – 23,999
1.1.1.4/32
• Advertised as index 16004

All nodes use default SRGB
16,000 – 23,999
IGP Adjacency Segment
Adj to 5

state routing protocols 1 2
• Forward on IGP adjacency Adj to 4
24024
Local significance
•
5
• Automatically allocated by router
3 4
Combining IGP Segments 16004
24045
• Signaled by ISIS/OSPF Packet to 5
• Steer traffic on any path through

the network
1 2
• Path is specified by list of
segments in packet header, a
stack of labels
5
24045
• No path is signaled Packet to 5
• No per-flow state is created 3 4

16004 24045
MPLS Data Plane Operations
IPv4: 1.1.1.4/32
or
Segment 16004 IPv6: 2001::0101:0104/128
Prefix-SID 16004
1 2 3 4
Push Swap Pop -
16004 16004
Payload Payload Payload Payload
SR Segments
SRGB: Segment Routing Global Block:
default [16000 – 23999]
• Signaled by ISIS/OSPF
12
IGP Prefix
Minor extensions to the existing link-state 10

Segment
• 2 4
routing protocols (OSPF and IS-IS) 1
7
13 16005
• Shortest-path to the IGP prefix
3 6 5
• Global in SR domain 11
• SRGB + Index => 16000+5 = 16005 14

DC (BGP-SR) WAN (IGP-SR) PEER
IGP Adjacency
12 124
2 4
Segment
• Minor extensions to the existing link-state 1 7

routing protocols (OSPF and IS-IS) 13
6 5
• Forward on the IGP adjacency 3
11
• Local 14
• Automatically allocated by the router DC (BGP-SR) WAN (IGP-SR) PEER
Metro Fabric Transport Configuration
IGP with Segment Routing + TI-LFA
router isis 1 router ospf 1

address-family ipv4 unicast router-id 1.1.1.1
metric-style wide segment-routing mpls
segment-routing mpls segment-routing forwarding mpls
! IGP-SR area 0
interface Loopback0 interface Loopback0
address-family ipv4 unicast passive enable
prefix-sid prefix-sid index 1 prefix-sid index 1
+
TI-LFA
Compass
YANG YANG
Programmability

FRR or TE RSVP
IGP with SR
Intra-Domain CP
X
LDP IGP with SR
IGP
IGP with Segment Routing extension

• IGP Prefix Segment (Prefix-SID)
• IGP Adjacency Segment (Adj-SID)
TI-LFA – zero-segment example
prefix-SID(Z) A Z
Packet to Z
• To steer packets on TI-LFA 1 2

backup path: P-space 1000
Packet to Z
prefix-SID(Z) 5
• “forward packet to R5 without any Packet to Z
additional segment”
4 3
Q-space
Default metric: 10
TI-LFA – single-segment example
prefix-SID(Z) A Z
Packet to Z
Packet to Z
1 2
• To steer packets on TI-LFA
backup path: prefix-SID(R4)
prefix-SID(Z) 5
prefix-SID(Z)
Packet to Z
• “forward packet on interface to R5 Packet to Z
• push segment {prefix-SID(R4)}” 4 3
Ext P-space Q-space
Default metric:10
TI-LFA – double-segment example
A Z
prefix-SID(Z)
Packet to Z Packet to Z
• To steer packets on TI-LFA 1 2

backup path: prefix-SID(R4)
adj-SID(R4-R3)
5
• forward packet on interface to R5 prefix-SID(Z) prefix-SID(Z)
Packet to Z
• push segments {prefix-SID(R4) and Packet to Z
adj-SID(R4-R3)}” 4
R4 3
R3
1000
P-space Q-space
adj-SID(R4-R3)
Default metric: 10
prefix-SID(Z)
Packet to Z
IGP with Segment Routing + TI-LFA

address-family ipv4 unicast router-id 1.1.1.1
metric-style wide segment-routing mpls
segment-routing mpls segment-routing forwarding mpls
! IGP-SR area 0
interface Loopback0 interface Loopback0
address-family ipv4 unicast passive enable
prefix-sid prefix-sid index 1 prefix-sid index 1
router isis 1
+ router ospf 1
interface GigabitEthernet0/0/0/2 fast-reroute per-prefix
address-family ipv4 unicast TI-LFA fast-reroute per-prefix ti-lfa
fast-reroute per-prefix
fast-reroute per-prefix ti-lfa
Compass
YANG YANG
Programmability

FRR or TE X
RSVP
IGP with SR
Intra-Domain CP
X
LDP IGP with SR
IGP
IGP with Segment Routing extension Fast Re-Reroute (FRR)

• IGP Prefix Segment (Prefix-SID) • Topology Independent Loop Free Alternate (TI-LFA)
• IGP Adjacency Segment (Adj-SID) Traffic Steering
• ???
Combining IGP Segments – SR Policy
16004
24045
• Signaled by ISIS/OSPF Packet to 5

the network
1 2
• Path is specified by list of
stack of labels
5
24045

16004 24045
Combining IGP Segments – SR Policy
16003 PHP
SID-list 16004

Packet to 5
the network
1 2
• Path is specified by list of 16004
stack of labels
24045 5
Packet to 5
24045

16003 16004 24045
SR Policy Identification
• An SR Policy is uniquely identified by a tuple

(head-end, color, end-point)
Head-end: where the SR Policy is instantiated (implemented)
Color: a numerical value to differentiate multiple SRTE Policies between the same pair of
nodes
End-point: the destination of the SR Policy
• At a given head-end, an
SR Policy is uniquely identified SR Policy
by a tuple (color, end-point) 2 3 4
(1, green, 4)
Head-end: 1
Color: green 1
End-point: 4
7 6 5
SR Policy Color
• Each SR Policy has a color
– Color can be used to indicate a certain treatment (SLA, policy) provided by an SR
Policy
• Only one SR Policy with a given color C can exist between a given
node pair (head-end (H), end-point (E))
– In other words: each SR Policy triplet (H, C, E) is unique
(1, green, 4) 2 3 4
Low-latency 1.1.1.0/24
2.2.2.0/24
1
(1, blue, 4)
7 6 5
High-BW
SR Policy – Candidate Paths
• A head-end may be informed about candidate paths for an SR Policy
(color, end-point) by various means including: local configuration (CLI),
netconf, PCEP, or BGP
BGP PCEP
CLI SRTE netconf
SR Policy – Candidate Paths
• An SR Policy consists of one or more candidate paths (Cpaths)
SR Policy Cpath1
Cpath2 Candidate
... Paths
Cpathn
• A candidate path is either dynamic or explicit
SR Policy – Candidate Path
• A candidate path is a single segment list (SID-list)
or a set of weighted* SID-lists
– Typically, an SR Policy path only contains a single SID-list
• Traffic steered into an SR Policy
SID-list11
Weight11
path is load-shared over all Cpath1 ...
SID-lists of the path SID-list1m

Weight1m
SR Policy ...
SID-listn1
Weightn1
Cpathn ...
SID-listnk
Weightnk
Active SR Policy – FIB entry
20
2 10GE
3
SID-list:
Selected
SR Policy
Path
<16003, 1 4
16004>
BSID: 40GE
40104 6 5
Default link metric: 10
Forwarding table on Node1

In Out Out_intf Fraction
40104 <16003, 16004> To Node2 100%
Weighted ECMP (WECMP)
• If a set of SID-lists is associated with the selected path of the SR
Policy, then the steering is flow and WECMP-based according to the
relative weight of each SID-list
SID-list1: 1/5
<16003,
16004>
of load 20
2 10GE
3
Weight 1
Selected
SR Policy
Path 1 4
SID-list2: 40GE
<16004> 4/5 6 5
Weight 4 of load
Active SR Policy – FIB entry – WECMP
SID-list: 20
<16003,
2 10GE
3
16004>
Selected
SR Policy
Path Weight 1 1 4
BSID: SID-list: 40GE
40104 <16004> 6 5
Weight 4 Default link metric: 10
Forwarding table on Node1

In Out Out_intf Fraction
<16003, 16004> To Node2 20%

40104
<16004> To Node6 80%
WECMP example
On Node1:
segment-routing
traffic-eng
policy POLICY1
color 20 end-point ipv4 1.1.1.4
binding-sid mpls 1000
candidate-paths Path preference
preference 200 200
2 3
20
explicit segment-list SIDLIST1
weight 1
Explicit SID-list1,
! Weight 1
explicit segment-list SIDLIST2
weight 4
Explicit SID-list2, 1 4
Weight 4
6 5
!
segment-list name SIDLIST1
index 10 mpls label 16002 Default link metric: 10
index 20 mpls label 30203 SID-list1
index 30 mpls label 16004 FIB @ head-end Node1
! Incoming label: 1000
segment-list name SIDLIST2 Action:pop and push <16002, 30203, 14004> (20%)
index 10 address ipv4 1.1.1.4 SID-list2 push <16004> (80%)
Compass
YANG YANG
Programmability

FRR or TE X
RSVP
IGP with SR
Intra-Domain CP
X
LDP IGP with SR
IGP

• Segment Routing Traffic Engineering Policy (SRTE)
Simple and Efficient Transport of MPLS services
MP-BGP
• MPLS services
ride on prefix 3 4
segments CE PE PE CE
• Simple, one less 7 1 2 8
protocol to 1.1.1.2/32 10.0.0.0/30
operate (LDP) Prefix-SID 16002 2001::a00:0/126
5 6
vrf RED SR Domain vrf RED
Intra-Domain Transport -
Seamless Integration &
Migration
All nodes: SR + LDP SR LDP
MPLS-to-MPLS and MPLS-to-IP
Prefix-SID
• LDP FEC to 1.1.1.5/32 index 5
1 2 3 4 5
1.1.1.5
local/in lbl out lbl local/in lbl out lbl local/in lbl out lbl local/in lbl out lbl
16000 16000 16000 16000
… … … …
SRGB
16005 16005 16005 16005 16005 16005 16005 POP

… … … …
23999 23999 23999 23999
24000 24000 24000 24000
24001 24010 24010 24003 24003 24320 24320 POP
… … … …
… … … …
1048575 1048575 1048575 1048575
All nodes: SR + LDP SR LDP
MPLS-to-MPLS and MPLS-to-IP
Prefix-SID
• LDP FEC to 1.1.1.5/32 index 5
1 2 3 4 5
1.1.1.5
local/insr-prefer
segment-routing mpls lbl out lbl local/in lbl out lbl local/in lbl out lbl local/in lbl out lbl
16000 16000 16000 16000
… … … …
SRGB
16005 16005 16005 16005 16005 16005 16005 POP

… … … …
to 1.1.1.5 23999 23999 23999 23999
Payload 24000 24000 24000 24000

24001 24010 24010 24003 24003 24320 24320 POP
… … … …
segment-routing mpls (default)
… … … …
1048575 1048575 1048575 1048575
LDP to SR Migration

address-family ipv4 unicast SR/LDP Co-existence segment-routing mpls
segment-routing mpls sr-prefer segment-routing sr-prefer
LDP->SR migration
LDP to SR interworking
SR LDP
LDP: LDP:
1.1.1.5/32 1.1.1.5/32 1.1.1.5
lbl 90100 lbl 90007
1 2 3 4 5
SID 16005
16000 16000 16000 16000
SRGB
SRGB
… … 16005 16005 16005 pop
… …
copy
23999 23999 Prefix Segment
…
90008 90100 90100 90007 90007 16005
… LDP LSP … … …
1048575 1048575 1048575 1048575
segment-routing mapping-server
prefix-sid-map ipv4 SR LDP
SR to LDP interworking
1.1.1.5/32 5 range 1
Mapping Server LDP:
1.1.1.5/32
LDP: lbl imp-null
1.1.1.5/32 1.1.1.5
lbl 90100
1 2 3 4 5
16000 16000 16000 16000
SRGB
SRGB
SRGB
16005 16005 16005 16005 16005 90090 …
… … …
copy
23999 Prefix Segment 23999 23999
90002 90090 90090 pop
… … … … LDP LSP
1048575 1048575 1048575 1048575
Binding-SID – Stitching Intra and Inter Domain Feature!
BSID: BSID:
30410 30710
1 2 3 4 5 6 7 8 9 10
16003 16006
14 16004 16004 16007 16007 16009
410 30410 30410 30410 30710 30710 30710 16010 16010
Node 10 Node 10 Node 10 Node 10 Node 10 Node 10 Node 10 Node 10 Node 10
Do You remember? 20
2 10GE
3
SID-list:
Selected
SR Policy
Path
<16003, 1 4
16004>
BSID: 40GE
40104 6 5
Inter-Domain Transport
Compass Metro Fabric - High-Level Domain View
Access Aggregation Core Aggregation Access
CO CO CO
Option1: Central Office - Distributed
Compass Metro Fabric - High-Level Domain View
Access Core Access
CO CO CO
Option2: Central Office - Distributed with Access Domain extension
Access Core Access
CO CO CO
Option3: Central Office - Distributed with Core Domain extension
Inter-Domain Simplification by Segment Routing
Compass
YANG YANG
Programmability How Can I replace BGP-LU and why to do it?

FRR or TE X
RSVP
IGP with SR
Intra-Domain CP
X
LDP IGP with SR
IGP

Reminder: Unified MPLS Design BGP-LU Signaling
RR
Inline RR Inline RR
next-hop-self next-hop-self
PE3 PE5
A1 Access Core Access A6
PE2 PE4
IGP (ISIS/OSPF) – Intra-Domain LSP IGP (ISIS/OSPF) – Intra-Domain IGP (ISIS/OSPF) – Intra-Domain LSP
LSP
BGP-LU – Inter-Domain LSP
MPLS Data-Plane Left-To-Right ->
PE2 or PE3 LDP PHP PE4 or PE5 LDP PHP A6 LDP PHP
A6 BGP-LU A6 BGP-LU A6 BGP-LU A6 BGP-LU Service Service
Service Service Service Service
Reminder: Unified MPLS Design
Segment Routing Introduction => EPN5.0 SolutionBGP-LU Signaling
Segment Routing can be deployed in each IGP domain independently, with all benefits described in previous section
RR
Inline RR Inline RR
next-hop-self next-hop-self
PE3 PE5
PE2 PE4
IGP (ISIS/OSPF) with SR extension– Intra-Domain LSP IGP (ISIS/OSPF) – Intra-Domain IGP (ISIS/OSPF) – Intra-Domain LSP
LSP
BGP-LU – Inter-Domain LSP
TI-LFA
TI-LFA
TI-LFA
PE2 or PE3 SR PHP PE4 or PE5 LDP PHP A6 LDP PHP
A6 BGP-LU A6 BGP-LU A6 BGP-LU A6 BGP-LU Service Service
Service Service Service Service
Let’s uncover one more Cool Segment Routing Feature
Anycast Prefix Segment (SID)
• Same prefix
advertised by 100
12
multiple nodes 10
2 4
• Traffic forwarded to
one of Anycast 1
7
prefix-SIDs based on 13 16100
best IGP path
3 6 5
• If primary node fails,
traffic is auto re- 11 100
routed to other node 14
End-To-End Segment Routing Transport
Segment Routing Policy (SRTE) for Inter-Domain LSP
BGP-LS
RR
PCEP/BGP
Anycast-SID Anycast-SID
PE3 PE5
PE2 PE4
IGP SR (ISIS/OSPF) – Intra-Domain LSP IGP SR (ISIS/OSPF) – Intra-Domain IGP SR (ISIS/OSPF) – Intra-Domain LSP
LSP
TI-LFA
TI-LFA End-To-End, Each IGP Domain Independently
TI-LFA
PE2/PE3 SR PHP PE4/PE5 SR PHP A6 SR PHP
PE4/PE5 SR PE4/PE5 SR A6 SR A6 SR Service Service
A6 SR A6 SR Service Service
Service Service
Segment Routing Policy SRTE
Inter-Domain LSP
SRTE – Inter-Domain LSP BGP-LU Inter-Domain LSP
TI-LFA (same as Intra-Domain) BGP-PIC is required for FRR
Anycast-SID/TI-LFA up to 50ms ABR Node failure cannot guarantee up to 50ms

convergence time
PCE provides only path which is requested by Difficult to filter host-routes to which Inter-
BGP service or operator => HW resources Domain LSP is not needed.
saving
Source Routing End-To-End => easy to Traffic engineering per-IGP Domain
program path based on requested SLA
Inter-Domain Simplification by Segment Routing
Ok, What about PCE?
Compass
YANG YANG
Segment Routing Policy SRTE

Programmability • End-To-End TI-LFA
• Anycast-SID
• End-To-End per SLA Path Programmability
Inter-Domain CP X
BGP-LU
X
BGP-LU
FRR or TE X
RSVP
IGP with SR
Intra-Domain CP
X
LDP IGP with SR
IGP

Transport/Services -
Programmability
SR Path Computation Element (SR-PCE)
SRTE Head-End APP APP APP
Distributed Mode – SR-TE Head-End
Visibility is limited to its own IGP domain
Single / Native SR
REST API algorithms
Multi-Domain
Topology
Solution
Multi-Domain SRTE Visibility Topo
Centralized SR-PCE for Multi-Domain Topology view Compute
DB
SR-PCE runs on
virtual or physical
Integration with Applications IOS-XR node
North-bound APIs for topology/deployment Collect Deploy
Delivers across the unified SR Fabric the SLA requested by PCEP
IGP
the service BGP-LS
BGP
Benefits
Simplicity and Automation Access Metro Core Metro Data Center
End-to-End network topology awareness

SLA-aware path computation across network 1 2 3 4
domains
Aggregation
SR Path Computation Element (SR-PCE)
• Runs as IOS-XR process

• Collect topology: BGP, ISIS, OSPF and BGP Link State
• Deploy tunnel: PCEP SR/RSVP, BGP SR-TE
• Compute: Shortest, Disjoint, Low Latency, Avoidance paths
• North Bound interface with application: YANG
BGP-LS Overview
• Optimal Path Computation for Multi-area TE PCE

Traffic
Engineering
Databse (TED)
• Solution is BGP, not IGP.
• BGP-LS is an address-family
• afi=16388, safi=71
BGP-LS
• Defined to carry IGP link-state database via
BGP Domain 0 RR
• Supports both IS-IS and OSPF BGP-LS BGP-LS

• Delivers topology information to outside agents
Domain 1 Domain 2
PCEP Architectural Introduction
• Path computation PCE
LSP DB
• Large, multi-domain and multi-layer networks
PCEP TED
• Path computation element (PCE)
• Computes network paths (topology, paths, etc.)
• Stores TE topology database (synchronized with network)
• May initiate path creation
• Stateful - stores path database included resources used PCC
(synchronized with network)
• Path computation client (PCC) Open/Close/Keepalive

• May send path computation requests to PCE PCC PCE
May send path state updates to PCE

Open/Close/Keepalive
•
Request
• Used between head-end router (PCC) and PCE to: PCC

Reply
PCE
• Request/receive path from PCE subject to constraints Notification
• State synchronization between PCE and router PCC PCE

Notification
• Hybrid CSPF
Creating an SRTE Policy by BGP BGP SR TE Policy NLRI
Color green
Endpoint 4.4.4.4
Binding SID: 4001
Segment List
• Controller programs an SR TE Policy at ingress Weight: 100 Controller
16001, 16002, 24024 9.9.9.9/32
• SR TE Policy defines the set of explicit paths Segment List
Weight: 100
from ingress to policy endpoint 16003, 16006, 24065
• Weighted ECMP among multiple paths
12
10
2 4 Low Lat, Low
BW
1
7
13
3 6 5
11
14
NSO Main Features
Applications Engineers
REST, NETCONF, Java, Python, Erlang, CLI, Web UI • Logically centralized network
services
Service
Service Manager Model • Data models for data
structures
Device
• Structured representations
Device Manager
Model of:
• Service instances
Network Element Drivers (NEDs) • Network configuration
and state
NETCONF, REST, SNMP, CLI, etc • Mapping service operations
to network configuration
• VNFM changes
• Controller Apps • Transactional integrity
• EMS and NMS • Multiprotocol and multivendor
Physical Networks Virtual Networks Network Apps support
Path Computation Engine – Workflow
Delegated Computation to SR-PCE
1. NSO provisions the service

Service can also be provisioned via CLI
2. Access Router requests a path
PCEP
BGP-LS
3. SR-PCE computes the path
A
4. SR-PCE provides the path to Access Router
NETCONF/YANG 5. Access Router confirms
Transport Programmability – SRTE Policy
BGP-LS
RR
PCEP/BGP
PE3 PE5
PE2 PE4
IGP SR (ISIS/OSPF) – Intra-Domain LSP IGP SR (ISIS/OSPF) – Intra-Domain IGP SR (ISIS/OSPF) – Intra-Domain LSP
LSP
TI-LFA
TI-LFA End-To-End, Each IGP Domain Independently
TI-LFA
PE2/PE3 SR PHP PE4/PE5 SR PHP A6 SR PHP
PE4/PE5 SR PE4/PE5 SR A6 SR A6 SR Service Service
A6 SR A6 SR Service Service
Service Service
BGP Based Service –
On-Demand Next Hop
Why is BGP so important for
Intent-Based Networking
On-Demand Next-Hop (ODN)
Dynamic VPN instantiation of SRTE policies
• CE21 advertises prefixes to PE
10 11
BGP:
1.1.1.21/32,
3 5
T:30
22 via 21
2 13 14 21
Vrf 7 9 23 Vrf
T:30
BLUE BLUE
• PE22 checks its policy and finds that
1.1.1.21/32 must receive low latency
service MAP: 1.1.1.21/32 in vrf BLUE must
receive low latency service  tag
with community (100:777)
10 11
BGP:
1.1.1.21/32,
3 5
T:30
22 via 21
2 13 14 21
Vrf 7 9 23 Vrf
T:30
BLUE BLUE
• PE22 tags 1.1.1.21/32 with a BGP with community (100:777)
community (e.g. 100:777)
and sends to RR11 10 11
BGP:
1.1.1.21/32,
3 5
T:30
22 via 21
2 13 14 21
Vrf 7 9 23 Vrf
T:30
BLUE BLUE
• PE22 tags 1.1.1.21/32 with a BGP with community (100:777)
community (e.g. 100:777)
and sends to RR11 10 11
BGP:
• RR11 sends to PE3 1.1.1.21/32,
3 5
T:30
22 via 21
2 13 14 21
Vrf 7 9 23 Vrf
T:30
BLUE BLUE
• PE3 requests a path towards PE22
from PCE (10)
COMPUTE: minimize TE Metric to PE22
PCreq 10 11
T:30
3 5 22
2 13 14 21
Vrf 7 9 23 Vrf
T:30
BLUE BLUE
• PE3 requests a path towards PE22
from PCE (10)
• PCE computes a dynamic path with COMPUTE: minimize TE Metric to PE22
the required Optimization Objective
and Constraints RESULT: SID list {S5, S14, S22}
• Result: SID list {S5, S14, S22}
SID list: Segment ID list,
• PE3 instantiates SRTE Policy with PCreq/reply
10 11
list of segments
Binding-SID: 30022 BSID:

30022
T:30
3 5 22
2 13 14 21
Vrf 7 9 23 Vrf
T:30
BLUE BLUE
1.1.1.21/32; NH: PE22
BGP
Received VPN label: L_VPN
Community 100:777
1.1.1.21/32; NH: PE22
BGP
Community 100:777
SRTE Policy to PE22:
TE
SID List {S0, S1, S2}, OIF 3
Binding Label: 30022
1.1.1.21/32; NH: PE22
• TE installs SRTE Policy in FIB:
BGP
Binding-SID (e.g. 30022):
Community 100:777
• push {label L1, label L2}
TE
Local label: 30022
FIB
OIF: SRTE; Label stack {L1, L2}
1.1.1.21/32; NH: PE22
• TE installs SRTE Policy in FIB:
BGP
Binding-SID (e.g. 30022):
Community 100:777
• push {label L1, label L2} Binding Label: 30022
• TE provides the
Binding-SID of the SRTE Policy to SRTE Policy to PE22:
TE
BGP SID List {S0, S1, S2}, OIF 3
Local label: 30022
FIB
1.1.1.21/32; NH: PE22
• BGP installs best-path in FIB:
BGP
• 1.1.1.21/32 via 30022
Community 100:777
• Push VPN label and steer in SRTE Binding Label: 30022
Policy
TE
1.1.1.21/32; recursion-via-segment
label L_VPN, NH via 30022
FIB
Local label: 30022
SR MPLS - Performance Monitoring
• Per-Link Delay Delay Measurement
Used as metric for SRTE Policy or Flex-Algo
• RFC 7810 (IS-IS Traffic Engineering (TE) Metric Extensions)

Used to advertise extended TE metrics – e.g. link delay (in usec)
• RFC 7471 (OSPF Traffic Engineering (TE) Metric Extensions)

Used to advertise extended TE metrics – e.g. link delay (in usec)
• BGP-LS: draft-ietf-idr-te-pm-bgp
SR IGP Flex Algo
• Complements the SRTE solution by adding new Prefix-Segments with
specific optimization objective and constraints
• minimize igp-metric or delay or te-metric
• avoid SRLG or affinity
• Leverages the SRTE benefits of simplicity and automation

• Automated sub-50msec FRR (TILFA)
• On-Demand Policy (ODN)
Multi-Plane Networks
Powered by SR IGP Flex Algo
Best-Effort Traffic Algorithm 0: IGP Metric
A3 P3 A5
$ $ $ $ $ $
CE1 A1 Access ABR1 Core ABR2 Access A6 CE2
A2 P2 A4
L3VPN - VPNv4 (SLA Best-Effort - BGP community)
A3 P3 A5
$ $ $ $ $ $
A2 P2 A4
L3VPN - VPNv4 (SLA Best-Effort - BGP community)
ODN A3 P3 A5
$ $ $ $ $ $
A2 P2 A4
Algorithm 0: ABR1
Label Stack Algorithm 0: ABR2 Algorithm 0: A6
Algorithm 0: ABR2 Algorithm 0: A6 Service
Algorithm 0: A6 Service
Service
Low-Latency Traffic Flex-Algo128: Delay
L3VPN - VPNv4 (SLA Low-Latency - BGP Community)
A3 P3 A5
$ $ $ $ $ $
A2 P2 A4
L3VPN - VPNv4 (SLA Low-Latency - BGP Community)
ODN A3 P3 A5
$ $ $ $ $ $
A2 P2 A4
Flex-Algo 128: ABR1 Flex-Algo 128: ABR2

Label Stack Flex-Algo 128: A6
Flex-Algo 128: ABR2 Flex-Algo 128: A6 Service
Flex-Algo 128: A6 Service
Service
Transport – Segment
Routing IPv6 (SRv6)
Segment Routing and the IPv6 Dataplane - SRv6
• Segment Routing applies to both IPv6 and MPLS dataplanes

• Difference is in the bits encoded in the packet not in the architecture
• Enabling SR-IPv6, means that ONLY the nodes that have to process the
packet header must have SR-IPv6 dataplane support
• All other nodes in the infrastructure are just plain IPv6 nodes
IPv6 Hdr Label(C)

SR Header Label(F)
B C D Segments: Label(H)
C,F,H IPv4 or IPv6
A H hdr
E F G
PAYLOAD PAYLOAD
SR-IPv6 SR-MPLS
SRv6 - Segment format
Locator Function
1111 : 2222 : 3333 : 4444 : 5555 : 6666 : 7777 : 8888
• SRv6 SIDs are 128-bit addresses

• Locator: most significant bits are used to route the segment to its parent node
• Function: least significant bits identify the action to be performed on the parent node
• Argument [optional]: Last bits can be used as a local function argument
• Flexible bit-length allocation

• Segment format is local knowledge on the parent node
Inter-Domain SRv6 without SRH
default-route ::/0 default-route ::/0 Summary route -> PE Summary route -> AG
or Summary route -> AG or Summary route -> PE
1 Access AG Aggregation PE Core PE Aggregation AG Access 4
Transport: End-To-End Inter-Domain by SRv6 (without SRH)
SA:2001::1:1 SA:2001::1:1 SA:2001::1:1 SA:2001::1:1 SA:2001::1:1

DA:2001::4:E100 DA:2001::4:E100 DA:2001::4:E100 DA:2001::4:E100 DA:2001::4:E100
NH:IPv6/IPv4 NH:IPv6/IPv4 NH:IPv6/IPv4 NH:IPv6/IPv4 NH:IPv6/IPv4
Original Frame/ Original Frame/ Original Frame/ Original Frame/ Original Frame/
packet - VRF100 packet - VRF100 packet - VRF100 packet - VRF100 packet - VRF100
Locator Function Router D MyLocalSID Table:

2001::4:E100 - END.DT6
2001::4:E100 IPv6 L3VPN (VRF:100)
(equivalent of a per-VRF VPN label)
Inter-Domain SRv6 with SRH
Traffic Steering
default-route ::/0 default-route ::/0 Summary route -> PE Summary route -> AG
or Summary route -> AG or Summary route -> PE
1 Access AG Aggregation PE Core 5 Aggregation AG Access 4
3
Transport: End-To-End Inter-Domain by SRv6 (with SRH)
SA:2001::1:1 SA:2001::1:1 SA:2001::1:1 SA:2001::1:1 SA:2001::1:1 SA:2001::1:1

DA:2001::3:C35 DA:2001::3:C35 DA:2001::3:C35 DA:2001::4:E100 DA:2001::4:E100 DA:2001::4:E100
NH:IPv6/IPv4 NH:IPv6/IPv4 NH:IPv6/IPv4 NH:IPv6/IPv4 NH:IPv6/IPv4 NH:IPv6/IPv4
Type:4(SRH) Type:4(SRH) Type:4(SRH) Original Frame/ Original Frame/ Original Frame/

NH:IPv6|SL:1 NH:IPv6|SL:1 NH:IPv6|SL:1 packet - VRF100 packet - VRF100 packet - VRF100
Segment List: Segment List: Segment List:
[0]:2001::4:E100 [0]:2001::4:E100 [0]:2001::4:E100
Router F MyLocalSID Table:
Original Frame/ Original Frame/ Original Frame/ Locator Function 2001::3:C35 - END.X
packet - VRF100 packet - VRF100 packet - VRF100
Update IPv6 DA from SRH and
2001::3:C35 L3 cross-connect to router 5
with PSP enabled
BGP Based Services -
EVPN
From Mac Bridging to Mac Routing
Common BGP Control Plane
L3VPN – VPNv4/6, L2/3VPN – EVPN, EVPN-VPWS Overlay
Evolution:
Underlay
IP, MPLS IP,MPLS,VXLAN IP,MPLS,VXLAN
Data Center Network

Service Provider Network overlap
Leaf
VM
PE1 DCI1
Spine Spine
Leaf
VM
A1 Access WAN/Core
Leaf
PE2 DCI2 VM
L2/L3VPN (BGP,T-LDP) - VPLS, EoMPLS VPLS, OTV Trill, Fabric-Path Overlay

Existing Solution:
IP, IGP, MPLS (LDP), RSVP-TE, BGP-LU IP, MPLS, L2 L2, STP, VLAN Underlay
Next-Generation Solutions for L2VPN
Solving VPLS challenges for per-flow Redundancy
M1 M2
CE1 PE1 PE3 CE2
• Existing VPLS solutions do not offer an Echo !
All-Active per-flow redundancy PE2 PE4
• Looping of Traffic Flooded from PE

M1 Duplicate !
M2
• Duplicate Frames from Floods from the
CE1 PE1 PE3 CE2
Core
• MAC Flip-Flopping over Pseudowire PE2 PE4
• E.g. Port-Channel Load-Balancing does

not produce a consistent hash-value for a M1 M2
frame with the same source MAC (e.g. non CE1 PE1
MAC
Flip-Flop PE3 CE2
MAC based
Hash-Schemes)
PE2 PE4
EVPN
Next generation network services
Not technical benefit to replace them with EVPN L3!!
E2E control and automation across
Single service for any application
domains
DC
ELINE ELAN ETREE DCI L3VPN EVPN
Fabric
SR SR-TE MPLS VXLAN
P2MP VPLS / L3
VPWS VPLS VXLAN RFC2547
VPLS VPN
Access Agg Core Agg DC
Optimized CapEx: Reduced OpEx: Increased Customer Value

- Open Standards & Multi-vendor - Integrated L2 & L3 service, any - Inter-domain SLA, faster
application: faster time to market, convergence
- Active-Active multi-homing
certification - Better stability: no flood
- Enhanced load balancing - E2E control and automation - Granular policy control
EVPN Advantages:
Integrated • Integrated Layer 2 and Layer 3 VPN services
Services • L3VPN-like principles and operational experience for scalability and control
• All-active Multi-homing & PE load-balancing (ECMP)
• Fast convergence (link, node, MAC moves)

Network
• Control-Place (BGP) learning. PWs are no longer used.
Efficiency
• Optimized Broadcast, Unknown-unicast, Multicast traffic delivery
• Choice of MPLS, VxLAN or SRv6 data plane encapsulation

Service • Support existing and new services types (E-LAN, E-Line, E-TREE)
Flexibility • Peer PE auto-discovery. Redundancy group auto-sensing
Investment • Fully support IPv4 and IPv6 in the data plane and control plane
Protection • Open-Standard and Multi-vendor support
EVPN vs VPNv4/6 or BGP Control Plane?
• BGP integrates services with programmable SR transport
• Common across L2 / L3 services
• Services Control Plane is BGP with different AF / SAFI
• Single Service Control Plane is easy to manage and troubleshoot
• Not technical benefit to replace them with EVPN L3!!
EVPN Flavors
• Multi-Homed All-Active Ethernet Access
• Replacement of: mLACP, STP, T-LDP, BGP-AD, etc.
• Standards-based Multi-chassis / Cluster Control Plane
• Replacement of: vPC, VSS, nVCluster, etc.
• Replacement of: HSRP, VRRP, etc.
MPLS Transport & BGP Service
BGP L3VPN BGP EVPN
BGP Signaling BGP Signaling BGP Signaling BGP Signaling
PE2 PE4 PE2 PE4
CE1 MPLS CE2 CE1 MPLS CE2
PE1 PE3 PE1 PE3

Data Plane Data Plane
IP Packet Transport IP Packet L2 Frame Transport L2 Frame

MPLS Label MPLS Label
Service Service
BGP Label BGP Label
IP Packet L2 Frame
What is EVPN?
RFC 7432
EVPN family introduces next EVPN
generation solutions for Ethernet
services
P2P Multipoint
• BGP control-plane for Ethernet Segment
and MAC distribution learning over MPLS
and VXLAN data-plane
• Same principles and operational EVPN-VPWS
experience as in IP VPNs
RFC 8214
No use of Pseudowires
Multi-vendor solutions EVPN-IRB
RFC 7432
EVPN
Cisco leader in industry
standardization efforts (RFCs/Drafts) draft-ietf-bess-evpn-inter-subnet-forwarding
Concepts
EVPN Instance (EVI) Ethernet Segment BGP Routes BGP Route Attributes
SHD Route Types Extended Communities

CE1
BD EVI ESI1 PE1 [1] Ethernet Auto-Discovery (AD) Route ESI MPLS Label
[2] MAC/IP Advertisement Route ES-Import

MHD CE2
[3] Inclusive Multicast Route MAC Mobility
BD
EVI
PE2
ESI2 [4] Ethernet Segment Route Default Gateway
PE
[5] IP Prefix Advertisement Route Encapsulation
• EVI identifies a VPN in the • Represents a ‘site’ • New SAFI [70] • New BGP extended
network connected to one or more • Routes serve control communities defined
• Encompass one or more PEs plane purposes, • Expand information
bridge-domains, • Uniquely identified by a including: carried in BGP routes,
depending on service 10-byte global Ethernet MAC address reachability including:
interface type Segment Identifier (ESI) MAC mass withdrawal MAC address moves
Port-based • Could be a single device Split-Horizon label adv. Redundancy mode
VLAN-based (shown above) or an entire network Aliasing MAC / IP bindings of a GW
VLAN-bundling Single-Homed Device (SHD) Multicast endpoint discovery Split-horizon label encoding
Multi-Homed Device (MHD) Redundancy group discovery Data plane Encapsulation
Single-Homed Network (SHN) Designated forwarder election
Multi-Homed Network (MHN) IP address reachability
L2/L3 Integration
EVPN - Ethernet VPN
• Concepts are same!!! Pick your side!
Pick your side!

SP1 SP2
PE2 PE4
CE1
PE1 PE3
L1 L2 L3 L4
C1 C2
VM VM VM VM
EVPN - Ethernet VPN
• Leafs run Multi-Protocol BGP to advertise & learn MAC/IP addresses over the
Network Fabric
• MAC/IP addresses are advertised to rest of Leafs
SP1 SP2
MAC/IP advertisement &

learning via BGP EVPN NLRI
L1 L2 L3 L4
Data Plane learning
from the hosts
All Active multi-homing
C1 C2 Ethernet Segment
VM VM VM VM
EVPN - Ethernet-Segment for Multi-Homing
The bundle on the Leafs SP1 SP2

connecting to a node should
have Identical ES identifier
(ESI)
L1 L2 L3 L4
Unique 10-byte global

identifier per Ethernet Segment Ethernet Segment represents a
C1 C2 node connected multiple Leafs
VM VM VM VM
EVPN - load-balancing modes
All-Active Single-Active Port-Active
(per flow) (per VLAN) (per port)
PE1 PE2 PE1 PE2 PE1 PE2
V1 V1 V1 V2 V1, V2
CE1 CE2 CE3
Single LAG at the CE Multiple LAGs at the CE Multiple LAGs at the CE

VLAN goes to both PE VLAN active on single PE Port active on single PE
Traffic hashed per flow Traffic hashed per VLAN Traffic hashed per port
Benefits: Bandwidth, Convergence Benefits: Billing, Policing Benefits: Protocol Simplification
EVPN – Designated Forwarder (DF)
Challenge:
How to prevent duplicate copies of flooded traffic from being delivered to a multi-homed
Ethernet Segment?
SP1 SP2
L1 L2 L3 L4
NDF DF
C1 Duplicate C2
EVPN – Split Horizon
Challenge:
How to prevent flooded traffic from echoing back to a multi-homed Ethernet Segment?
Transport
BUM Label Label
SP1 SP2
SH Label
L1 L2
Echo !
C1
VM VM
EVPN – MAC Mass-Withdraw
Challenge:
How to inform other Leafs of a failure affecting many MAC addresses quickly while the
control-plane re-converges?
SP2 MAC1  ESI1  Leaf1 + Leaf2

MAC1 can be SP1
reached via ESI1
L1 L2 L3 L4
MAC1 can NOT be
reached via ESI1
C1 C2
VM VM VM VM
ESI1 MAC1
EVPN – BUM Ingress Replication
SP1 SP2
L1 L2 L3 L4
C1 C2
VM VM VM VM
EVPN – Aliasing
Challenge:
How to load-balance traffic towards a multi-homed device across multiple Leafs when
MAC addresses are learnt by only a single Leaf?
MAC1 can also be

SP2 MAC1  ESI1  Leaf1 + Leaf2
reached via ESI1 SP1
L1 L2 L1 L2
MAC1 can be
reached via ESI1
C1 C2
VM VM VM VM
ESI1 MAC1
EVPN – MAC Mobility
Challenge:
How to detect the correct location of MAC after the movement of host from one Ethernet
Segment to another also called “MAC move”?
Sequence number and Next-Hop MAC IP ESI Seq. Next-

value will be changed after the host Hop
SP1 SP
move MAC-1 IP-1 0 1 Leaf-3
MAC IP ESI Seq. Next-

Hop
L1 L2 L3 L4 Sequence number is incremented
MAC-1 IP-1 0 0 Leaf-1 and Next-hop is changed to Leaf-3
C1 C2
VM
Host move
EVPN – Distributed Anycast Gateway
Purpose:
Optimal intra and inter-subnet connectivity with seamless workload mobility
Identical Anycast Gateway Virtual IP

and MAC address are configured
on all the Leafs
Distributed Anycast Gateway serves
as the gateway for connected hosts SP1 SP2
BVI BVI BVI BVI

GW GW GW GW
L1 L2 L3 L4
All the BVIs perform active forwarding
in contrast to active/standby like First-
hop routing protocol
C1 C2 C3 C4
VM VM VM VM
EVPN – IRB in Network Fabric
Intra-subnet
Forwarding
Inter-subnet
Forwarding
SP1 SP2
BVI BVI BVI BVI

GW GW GW GW
L1 L2 L3 L4
C1 C2 C3 C4
VM VM VM VM
BGP Based Services –
EVPN & L3VPN Interconnect
EVPN and VPNv4/6 Interconnect
• DCI/BL provides EVPN to VPNv4/6 stitching
• DCI/BL participates in L3 Routing not in L2 Bridging
• DCI/BL is mandatory, because of summarization!!!
BGP - L3VPN VPNv4/6 BGP - EVPN
A3 P3 SP2 L2
CE1 A1 Access ABR1 Core DCI/BL1

CO CE2
A2 P2 SP1 L1
• DCI/BL provides EVPN to VPNv4/6 stitching Interconnect
• DCI/BL participates in L3 Routing not in L2 Bridging
• DCI/BL is mandatory, because of summarization!!!
RT5 Prefix = prefix-CE2/24 RT5 Prefix = prefix-CE2/24
RT5 Prefix = prefix-CE1/24 RT5 Prefix = prefix-CE1/24
RT2 MAC/IP = CE1/32

X
A3 P3 SP2 L2

CO CE2
A2 P2 SP1 L1
RT5 Prefix = prefix-CE2/24 RT: VRF A RT5 Prefix = prefix-CE2/24 RT: VRF A Stitching
RT5 Prefix = prefix-CE1/24 RT: VRF A RT5 Prefix = prefix-CE1/24 RT: VRF A Stitching
RT2 MAC/IP = CE1/32 RT: VRF A Stitching

X
DCI/BL
VRF A
RD DCI:0
RT import/export: VRF A Stitching
RT import/export: VRF A
L2/L3VPN - EVPN (SLA Low-Latency -
BGP Community)
A3 P3 SP2 L2
$ $ $ $

CO CE2
A2 P2 SP1 L1
L3VPN - VPNv4 (SLA Low-Latency - BGP Community) L2/L3VPN - EVPN (SLA Low-Latency -
BGP Community)
A3 P3 SP2 L2
$ $ $ $

CO CE2
A2 P2 SP1 L1
L3VPN - VPNv4 (SLA Low-Latency - BGP Community) L2/L3VPN - EVPN (SLA Low-Latency -
BGP Community)
ODN A3 P3 SP2 L2
$ $ $ $

CO CE2
A2 P2 SP1 L1
Flex-Algo 128: ABR1 Flex-Algo 128: BL1

Label L1 or L2 (MultiPath)
Flex-Algo 128: BL1 Service
Stack Service
Service
EVPN-VPWS
• Benefits of EVPN applied to point-to-point services
• No signaling of PWs. Instead signals MP2P LSPs instead
(ala L3VPN)
• All-active CE multi-homing (per-flow LB) PE2 PE4
• Single-active CE multi-homing (per-service LB)
CE1 MPLS CE2
• Relies on a sub-set of EVPN routes to advertise
Ethernet Segment and AC reachability PE1 PE3
• PE discovery & signaling via a single protocol – BGP
• Per-EVI Ethernet Auto-Discovery route
BGP Based Services
EVPN - Legacy L2 and
VPLS Interconnect
EVPN L2 Interconnect – Let’s connect everything together
Everything in one Bridge Domain
• Legacy L2: REP, G8032, STP, etc.
LACP
• VPLS VPWS
• EVPN-VXLAN/EVPN-MPLS CE A3
• EoMPLS(PW)
• Ethernet – MultiHomed, SingleHomed
Leaf
VM
A2
Spine Spine
DCI/BL DCI/BL
PE1
Leaf
VM
STP/REP/ MPLS MPLS Core
A1 G.8032…. Core
Leaf
VM DCI/BL DCI/BL
PE2
A2 EVPN - VXLAN
EVPN-MPLS
EVPN - MPLS
A1 A2
VPLS
Anycast-PW access to EVPN
PE1 PE3
CE A1 EVPN A3 CE
Anycast-PW All-Active Anycast-PW
PE2 PE4
EVPN Headend (PWHE + EVPN)
PWHE PWHE
A1 PE1 PE3 A3
Multi/Single-Homed Multi/Single-Homed Multi/Single-Homed
CE All/Single-Active Single-Active All/Single-Active CE
EVPN-VPWS EVPN EVPN-VPWS
A2 PE2 PE4 A4
PWHE PWHE
EVPN – Service Layering Access Aggregation Core
A AG PE P PE
Multicast CE
FXC
EVPN-HE
E-TREE A AG PE P PE
P2P
L2 Bridging
L3 Routing BL BL
IRB
SP SP
SP SP
SP SP
SP SP
L L
L
L
L L “Shared or single tenant”
L L L
L L L L
L L L L
L L L L
C C CE CE
Intent-Based End-To-
End Service Provider
Network Design
Flexible BGP Based Services
End-To-End
A AG PE PE AG A
A AG PE PE AG A
CO CO CO
Distributed CO - service termination
Centralized CO - service termination
Access-To-Access - service termination
MP-BGP L3VPN
EVPN
EVPN-VPWS
Legacy EoMPLS PW - Static
Segment Routing and BGP Based Network Design
Transport: End-To-End Segment Routinng: TI-LFA FRR, SRTE Inter-Domain LSP
BGP-LS
RR
PCEP/BGP
PE3 PE5
PE2 PE4
S-RR S-RR S-RR

BGP-based services
Services: End-To-End/Hierarchical: BGP-based (L3VPN, EVPN(L2/L3)), Legacy EoMPLS PW for P2P, AnycastPW to EVPN for Multipoint
Segment Routing and BGP Based Network Design
Transport: End-To-End Segment Routinng: TI-LFA FRR, Anycast-SID for ABR HA/FRR, SRTE Inter-Domain LSP
PCEP
BGP-LS
RR RR RR
CO CO CO
BGP-based services
S-RR S-RR S-RR
Services: End-To-End/Hierarchical: BGP-based (L3VPN, EVPN(L2/L3)), Legacy EoMPLS PW for P2P, AnycastPW to EVPN for Multipoint
Conclusion
• Transport/Services Simplification
Easy to Manage/Provision and Automate
• Segment Routing Transport Programmability with BGP Based Services (VPNv4/6,
EVPN)
On-Demand Next Hop (ODN)
• SR-PCE - PCE integrated in IOS-XR
• Unified Control Plane and Data Plane Across SP Network
• Network Design Simplification
NETCONF
Provisioning YANG
Programmability

FRR or TE RSVP
IGP with SR
LDP IGP with SR
Intra-Domain CP
IGP
Segment Routing - Stay up to date
ask-segment-routing@cisco.com
amzn.com/B01I58LSUO
segment-routing.net
linkedin.com/groups/8266623
twitter.com/SegmentRouting
facebook.com/SegmentRouting/
EVPN - Stay Up-To-Date
• https://e-vpn.io/
• Upcoming Conferences: https://e-vpn.io/conferences/
• Cisco Live Barcelona 2019
• BRKSPG-2322 Service Provider Network Fabric: How to bring Access Services using EVPN
• Patrice Brissette, Principal Engineer
• BRKSPG-2518 Service Provider Programmable SDN solution for the Metro Fabric, powered by Segment Routing and EVPN
• Jiri Chaloupka, Technical Marketing Engineer
• BRKSPG-3965 EVPN Deep Dive with IOS-XR Configuration examples for Service Provider Metro and Data Center
• LTRSPG-2968 IOS-XR EVPN Hands-On Lab

Cisco Webex Teams
Questions?
Use Cisco Webex Teams (formerly Cisco Spark)
to chat with the speaker after the session
How
1 Find this session in the Cisco Events Mobile App
2 Click “Join the Discussion”
3 Install Webex Teams or go directly to the team space
4 Enter messages/questions in the team space
cs.co/ciscolivebot#BRKSPG-2518
Complete your online
session survey
• Please complete your Online Session
Survey after each session
• Complete 4 Session Surveys & the Overall
Conference Survey (available from
Thursday) to receive your Cisco Live T-
shirt
• All surveys can be completed via the Cisco
Events Mobile App or the Communication
Stations
Don’t forget: Cisco Live sessions will be available for viewing

on demand after the event at ciscolive.cisco.com
Continue Your Education
Demos in Meet the Related

Walk-in
the Cisco engineer sessions
self-paced
Showcase labs 1:1
meetings
Thank you

BRKSPG 2518 PDF

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

BRKSPG 2518 PDF

Hochgeladen von

Copyright:

Verfügbare Formate

BRKSPG-2518

Cisco Service Provider Intent-Based Networking

Fixed Access Aggregation Core Aggregation Mobile Access

PAN AGN-ASBR CN-ASBR CN-ASBR AGN-ASBR PAN

L2/L3VPN Services LDP BGP LDP BGP BGP

Inter-Domain CP BGP-LU BGP-LU

L2/L3VPN Services LDP BGP LDP BGP BGP

Inter-Domain CP BGP-LU BGP-LU

Routing protocols with SDN controller

5 (IS-IS,OSPF, BGP) NETCONF/YANG)

• Global significance in SR domain

SRGB = Segment Routing Global

• Signaled by ISIS/OSPF 16004

• Global significance in SR domain 16004

SRGB = Segment Routing Global

• Advertised as index 16004

• Signaled by ISIS/OSPF 24025

• Steer traffic on any path through

• No per-flow state is created 3 4

Minor extensions to the existing link-state 10

• SRGB + Index => 16000+5 = 16005 14

• Minor extensions to the existing link-state 1 7

• Automatically allocated by the router DC (BGP-SR) WAN (IGP-SR) PEER

router isis 1 router ospf 1

L2/L3VPN Services LDP BGP LDP BGP BGP

Inter-Domain CP BGP-LU BGP-LU

IGP with Segment Routing extension

• To steer packets on TI-LFA 1 2

• push segment {prefix-SID(R4)}” 4 3

Ext P-space Q-space

• To steer packets on TI-LFA 1 2

router isis 1 router ospf 1

L2/L3VPN Services LDP BGP LDP BGP BGP

Inter-Domain CP BGP-LU BGP-LU

IGP with Segment Routing extension Fast Re-Reroute (FRR)

• Steer traffic on any path through

• No per-flow state is created 3 4

• Signaled by ISIS/OSPF 24045

• No per-flow state is created 3 4

• An SR Policy is uniquely identified by a tuple

CLI SRTE netconf

• A candidate path is either dynamic or explicit

SID-lists of the path SID-list1m

Forwarding table on Node1

40104 <16003, 16004> To Node2 100%

Forwarding table on Node1

<16003, 16004> To Node2 20%

L2/L3VPN Services LDP BGP LDP BGP BGP

Inter-Domain CP BGP-LU BGP-LU

IGP with Segment Routing extension Fast Re-Reroute (FRR)

vrf RED SR Domain vrf RED

16005 16005 16005 16005 16005 16005 16005 POP

16005 16005 16005 16005 16005 16005 16005 POP

Payload 24000 24000 24000 24000

segment-routing mpls (default)

router isis 1 router ospf 1

90002 90090 90090 pop

Access Aggregation Core Aggregation Access

Access Core Access

Option2: Central Office - Distributed with Access Domain extension

Access Core Access

Programmability How Can I replace BGP-LU and why to do it?

L2/L3VPN Services LDP BGP LDP BGP BGP