BRKRST 2124 PDF

Introduction to Segment Routing
Michael Kowal, Vertical Solutions Architect

@ciscomk
BRKRST-2124
Abstract
Introduction to Segment Routing
This session provides an overview of the segment routing technology and its use
cases. This new routing paradigm provides high operational simplicity and
maximum network scalability and flexibility. You will get an understanding of the
basic concepts behind the technology and its wide applicability ranging from
simple transport for MPLS services, disjoint routing, traffic engineering and its
benefits in the context of software defined networking. Previous knowledge of
IP routing and MPLS is required.
BRKRST-2124 © 2016 Cisco and/or its affiliates. All rights reserved. Cisco Public 3
Agenda
• Technology Overview
• Use Cases
• A Closer Look at the Control and Data Planes
• Traffic Protection
• Traffic Engineering
• Conclusion
Technology Overview
Segment Routing
• Source Routing
– the source chooses a path and encodes it in the packet header as an
ordered list of segments
– the rest of the network executes the encoded instructions
• Segment: an identifier for any type of instruction
– forwarding or service
Segment Routing – Forwarding Plane
• MPLS: an ordered list of segments is represented as a
stack of labels
• IPv6: an ordered list of segments is encoded in a routing
extension header
• This presentation: MPLS data plane
IGP Prefix Segment
• Shortest-path to the IGP prefix
• Global
• 16000 + Index
12
• Signaled by ISIS/OSPF 10
2 4
1
7
13 16005
3 6 5
11
14
DC (BGP-SR) WAN (IGP-SR) PEER
IGP Adjacency Segment
• Forward on the IGP adjacency
• Local
• 1XY
• X is the “from” 12 124
• Y is the “to” 10
2 4
• Signaled by ISIS/OSPF 1
7
13
3 6 5
11
14
BGP Prefix Segment
• Shortest-path to the BGP prefix
• Global
• 16000 + Index 16001
12
• Signaled by BGP 10
2 4
1
7
13
3 6 5
11
14
BGP Peering Segment
• Forward to the BGP
peer
• Local
• 1XY 12 147 Low Lat,
• X is the “from” 10 Low BW
2 4
• Y is the “to”
1
• Signaled by BGP-LS 7
(topology information) 13
to the controller 3 6 5
High Lat, High BW
11
14
WAN Controller
• SR PCE collects via BGP-LS SR BGP-LS
• IGP segments PCE
BGP-LS
• BGP segments
• Topology BGP-LS
12
10
2 4 Low Lat, Low BW
1
7
13
3 6 5
11
14
An end-to-end path as a list of segments
PCEP, Netconf, SR
• SR PCE computes BGP
that the green path PCE
can be encoded as
• 16001
• 16002 12
{16001,
• 124
16002, 10
• 147 124, 2 50
4 Low Lat, Low BW
147}
• SR PCE programs a 1
7
single per-flow state 13
to create an
3 6 5
application-
engineered end-to-
11
end policy
14
Default ISIS cost metric: 10
Segment Routing Standardization
Sample IETF Documents
• IETF standardization in SPRING
Problem Statement and Requirements
working group (RFC 7855)
Segment Routing Architecture
• Protocol extensions progressing in (draft-ietf-spring-segment-routing)
multiple groups IPv6 SPRING Use Cases
(draft-ietf-spring-ipv6-use-cases)
• IS-IS
Segment Routing with MPLS data plane
• OSPF (draft-ietf-spring-segment-routing-mpls)
• PCE Topology Independent Fast Reroute using Segment Routing
(draft-francois-rtgwg-segment-routing-ti-lfa)
• IDR
IS-IS Extensions for Segment Routing
• 6MAN (draft-ietf-isis-segment-routing-extensions)
OSPF Extensions for Segment Routing
• Broad vendor and customer support (draft-ietf-ospf-segment-routing-extensions)
PCEP Extensions for Segment Routing
(draft-ietf-pce-segment-routing)
Close to 40 IETF drafts in progress

Segment Routing Product Support
• Platforms:
• IOS-XR (ASR9000, CRS-1/CRS-3)
• IOS-XE (ASR1000, CSR1000v, ASR902, ASR903, ISR4400)
• NX-OS (N3K, N9K)
• WAN Automation Engine (WAE)
• SR Traffic Engineering
• Integration with NSO
• Upcoming
• NCS5000, NCS6000
Use Cases
IPv4/6 VPN/Service transport 16007
vpn
• IGP only pkt
• No LDP, no RSVP-TE
2 3 vpn
• ECMP pkt
1 4 7
pkt
pkt
6 5
Site1 Site2
16007
vpn
pkt
Simplest migration: LDP to SR
• Initial state: All nodes run LDP, not SR
LDP LDP
3 4
LDP LDP
1 LDP 2
5 6
LDP LDP
LDP Domain
SR+LDP SR+LDP
• Step1: All nodes are upgraded to SR
3 4
• In no particular order
SR+LDP SR+LDP
• Default label imposition preference = LDP
1 LDP 2
5 6
SR+LDP SR+LDP
SR+LDP Domain
SR+LDP SR+LDP
3 4
SR+LDP
• leave default LDP label imposition preference
1 SR 2
• Step2: All PEs are configured to prefer SR
label imposition
• In no particular order segment-routing mpls sr-prefer 5 6
SR+LDP SR+LDP
SR+LDP Domain
Simplest migration LDP to SR
SR SR
3 4
SR SR
• leave default LDP label imposition preference
1 SR 2
• Step2: All PEs are configured to prefer SR
label imposition
• In no particular order 5 6
• Step3: LDP is removed from the nodes in SR SR

the network SR Domain
• Final state: All nodes run SR, not LDP
Seamless Interworking with LDP
• Seamless Deployment 16007
vpn
pkt LDP(7)
vpn
2 3 vpn
pkt
pkt
1 4 7
pkt
pkt
6 5
Site1 Site2
16007
vpn
pkt
Topology-Independent LFA (TI-LFA FRR)
• 50msec FRR in any topology
• IGP Automated 7
• No LDP, no RSVP-TE
2 3
• Optimum 16007
• Post-convergence path pkt
1 4
• No midpoint backup state
• Detailed operator report 16007
6 5
• S. Litkowski, B. Decraene, Orange pkt
• Mate Design
• How many backup segments 16005
• Capacity analysis 16007
pkt
Automated Traffic Matrix Collection 1 2 3 4
• Traffic Matrix is fundamental for 1
• capacity planning 2
• centralized traffic engineering 3

• IP/Optical optimization
4
• Most operators do not have an accurate

traffic matrix 2
• With SR, the traffic matrix collection is

automated
1 3
Optimized Content Delivery
7
• On a per-content, per-user basis, AS7
the content delivery application
can engineer
• the path within the AS 16003 5 6
• the selected border router 16002 AS5 AS6
• the selected peer
126
• Also applicable for engineering pkt
egress traffic from DC to peer 1 2
• BGP Prefix and Peering Segments
4 3
AS1
Application Engineered Routing
Low-Latency to 7
• Per-application for application SR PeerSID: 147, Low Lat, Low BW
A12 NSO PCE
flow engineering PeerSID: 147, High Lat, High BW
• End-to-End Low-Lat to 4
BSID: 200
• DC, WAN, AGG, PEER
12
• Millions of flows 10 ISIS: 35
• No signaling
Push
{16001,
2 4 Low Lat, Low BW
200, 147}
• No midpoint state 1
• No reclassification at 200: pop 7
and push
boundaries 13 {16002,
16004}
3 6 5
11
14 Default Latency metric: 10
DC (or AGG) WAN PEER
Application Engineered Routing
Low-Latency to 7,
DC Plane 0 only, SR
• Per-application for application A12 PeerSID: 147, Low Lat, Low BW
NSO PCE
flow engineering PeerSID: 147, High Lat, High BW
• End-to-End Low-Lat to 4
BSID: 200
• DC, WAN, AGG, PEER
12
• Millions of flows 10 ISIS: 35
• No signaling
Push
{16010,
2 4 Low Lat, Low BW
16001,
• No midpoint state 200, 147} 1
• No reclassification at 200: pop 7
and push
boundaries 13 {16002,
16004}
3 6 5
11
14 Default Latency metric: 10
DC (or AGG) WAN PEER
A Closer Look at the Control and
Data Planes
MPLS Control and Forwarding Operation with Segment
Routing
Services
MP-BGP
No changes to
IPv4 IPv6
IPv4 IPv6 VPWS VPLS control or
PE1 PE2 VPN VPN
forwarding plane
Packet
Transport LDP RSVP BGP Static IS-IS OSPF IGP label
distribution for
PE1 IGP PE2
IPv4 and IPv6.
MPLS Forwarding
Forwarding plane
remains the same
SID Encoding
• Prefix SID
• SID encoded as an index
• Index represents an offset from SRGB base SR-enabled Node
• Index globally unique
• SRGB may vary across LSRs
• SRGB (base and range) advertised with
router capabilities
SRGB = [ 16000 - 23999 ]. Advertised as base = 16,000, range = 7,999
• Adjacency SID Prefix SID = 16041. Advertised as Prefix SID Index = 41
Adjacency SID = 24000. Advertised as Adjacency SID = 24000
• SID encoded as absolute (i.e. not indexed)
value
• Locally significant
• Automatically allocated for each adjacency
SR IS-IS Control Plane Overview
• IPv4 and IPv6 control plane
• Level 1, level 2 and multi-level routing
• Prefix Segment ID (Prefix-SID) for host prefixes on loopback interfaces
• Adjacency SIDs for adjacencies
• Prefix-to-SID mapping advertisements (mapping server)
• MPLS penultimate hop popping (PHP) and explicit-null label signaling
Configuring Segment Routing for IPv4 Using IS-IS
(Cisco IOS-XR)
router isis DEFAULT
net 49.0001.1720.1625.5001.00
address-family ipv4 unicast Enable Segment Routing for IPv4 with
metric-style wide MPLS data plane
segment-routing mpls
!
interface Loopback0
passive
address-family ipv4 unicast
!
!
interface GigabitEthernet0/0/0/0
point-to-point
!
!
!
SR OSPF Control Plane Overview
• OSPFv2 control plane
• Multi-area
• IPv4 Prefix Segment ID (Prefix-SID) for host prefixes on loopback
interfaces
• Adjacency SIDs for adjacencies
• MPLS penultimate hop popping (PHP) and explicit-null label signaling
Configuring Segment Routing for IPv4 Using OSPF
(Cisco IOS-XR)
router ospf DEFAULT
router-id 172.16.255.1
segment-routing mpls Enable Segment Routing with MPLS
segment-routing forwarding mpls data plane
area 0
interface Loopback0
passive
!
network point-to-point
!
!
!
MPLS Data Plane Operation
Prefix SID Adjacency SID
SRGB [16,000 – 23,999 ] SRGB [16,000 – 23,999 ]
Adjacency
SID = X
Swap Pop
X
X X Y Y
Payload Payload Payload Payload
• Packet forwarded along IGP shortest path (ECMP)  Packet forwarded along IGP adjacency
• Swap operation performed on input label  Pop operation performed on input label
• Same top label if same/similar SRGB
 Top labels will likely differ
• PHP if signaled by egress LSR
 Penultimate hop always pops last adjacency SID
MPLS Data Plane Operation (Prefix SID)
SRGB [16,000 – 23,999 ] SRGB [16,000 – 23,999 ] SRGB [16,000 – 23,999 ] SRGB [16,000 – 23,999 ]
A B C D Loopback X.X.X.X
Prefix SID Index = 41
Push Swap Pop Pop

Push
16041 16041
VPN Label VPN Label VPN Label
Payload Payload Payload Payload Payload
MPLS Data Plane Operation (Adjacency SIDs)
SRGB [16,000 – 23,999 ] SRGB [16,000 – 23,999 ] SRGB [16,000 – 23,999 ] SRGB [16,000 – 23,999 ]
A B X D Loopback X.X.X.X
Adjacency Prefix SID Index = 41
SID = 126
Push Pop Pop Pop
Push
Push
126
16041 16041
VPN Label VPN Label VPN Label
Payload Payload Payload Payload Payload
MPLS LFIB with Segment Routing
• LFIB populated by IGP (ISIS / PE PE
OSPF) PE PE
• Forwarding table remains constant PE

P
PE
(Nodes + Adjacencies) regardless PE PE

of number of paths
In Out Out
• Other protocols (LDP, RSVP, BGP) Label Label Interface
can still program LFIB Network
L1 L1 Intf1
Node L2 L2 Intf1 Forwarding
Segment Ids … … … table remains
L8 L8 Intf4 constant
L9 L9 Intf2
Node L10 Pop Intf2
Adjacency … … …
Segment Ids
Ln Pop Intf5
Traffic Protection
Topology Independent LFA (TI-LFA) – Benefits
• 100%-coverage 50-msec link and node protection
• Simple to operate and understand
• automatically computed by the IGP
• Prevents transient congestion and suboptimal routing

• leverages the post-convergence path, planned to carry the traffic
• Incremental deployment
• also protects LDP traffic
Topology Independent LFA – Implementation
• Leverages existing and proven LFA technology
• P space: set of nodes reachable from node S (PLR) without using protected link L
• Q space: set of nodes that can reach destination D without using protected link L
• Enforcing loop-freeness on post-convergence path

• Where can I release the packet?
At the intersection between the post-convergence shortest path and the Q space
• How do I reach the release point?
By chaining intermediate segments that are assessed to be loop-free
TI-LFA – Zero-Segment Example
• TI-LFA for link R1R2 on R1 A Z
• Calculate LFA(s) Packet to Z Packet to Z
R1 R2
• Calculate post-convergence SPT
1000
• Find LFA on post-convergence R5
SPT prefix-SID(Z)
Packet to Z
• R1 will steer the traffic towards R4 R3
LFA R5
Default metric:10
TI-LFA – Single-Segment Example
• Calculate P and Q spaces Packet to Z Packet to Z
• They overlap in this case R1 R2
• Calculate post-convergence SPT P-space
prefix-SID(R4) R5
• Find PQ node on post- prefix-SID(Z)
prefix-SID(Z)
convergence SPT Packet to Z
Packet to Z
R4 R3
• R1 will push the prefix-SID of R4
on the backup path Q-space
Default metric:10
TI-LFA – Double-Segment Example
• Calculate P and Q spaces Packet to Z Packet to Z
R1 R2
• Calculate post-convergence SPT
prefix-SID(R4)
• Find Q and adjacent P node on adj-SID(R4-R3)
R5
post-convergence SPT prefix-SID(Z) prefix-SID(Z)
Packet to Z Packet to Z
• R1 will push the prefix-SID of R4 R4 R3
and the adj-SID of R4-R3 link on 1000
the backup path P-space Q-space

adj-SID(R4-R3)
Default metric:10
prefix-SID(Z)
Packet to Z
Traffic Engineering
Traffic Engineering with Segment Routing
• Provides explicit routing
Segment
• Supports constraint-based routing Routing
• Supports centralized admission control
• No RSVP-TE to establish LSPs
• Uses existing ISIS / OSPF extensions to
advertise link attributes
• Supports ECMP
TE LSP
How Traffic Engineering Works
Head end • Link information Distribution
• ISIS-TE
IP/MPLS • OSPF-TE
• Path Calculation
• Path Setup
• Forwarding Traffic down path
• Auto-route (announce / destinations)
• Static route
• PBR
• PBTS / CBTS
• Forwarding Adjacency
Mid-point Tail end
• Pseudowire Tunnel select
TE LSP
Stateful PCE
• PCE maintains topology and path Stateful PCE
database (established paths) LSP DB
• More optimal centralized path TED

computation
• Enables centralized path initiation and PCEP
update control
• Well suited for SDN deployments PCC
Topology Acquisition
• An external PCE requires some form of
topology acquisition PCE
TED
• A PCE may learn topology using BGP-
LS, IGP, SNMP, etc.
• BGP-LS characteristics BGP-LS
• aggregates topology across one or more domains
Domain 0 RR
• provides familiar operational model
• New BGP-LS attribute TLVs for SR BGP-LS BGP-LS

• IGP: links, nodes, prefixes
• BGP: peer node, peer adjacency, peer set
Domain 1 Domain 2
Active Stateful PCE
• PCC or PCE may initiate path setup
Active Stateful PCE
• PCC may delegate update control to
PCE has update
PCE control over
LSP DB
delegated paths
• PCC may revoke delegation TED
• PCE may return delegation

PCEP
Stateful
PCC
Active Stateful PCE
PCE-Initiated and PCC-Initiated LSPs
PCE-Initiated (Active Stateful PCE) PCC-Initiated (Active Stateful PCE)
PCE initiates LSP DB LSP DB

LSP and PCC initiates
maintains TED LSP and TED
update control delegates
update
PCEP control PCEP
Stateful Stateful
PCC PCC
• PCE part of controller architecture managing  PCC may initiate path setup based on
full path life cycle distributed network state
• Tighter integration with application demands  Can be used in conjunction with PCE-
initiated paths
PCE Extensions for Segment Routing (SR)
• Segment routing enables source routing Stateful PCE
based on segment ids distributed by IGP Application LSP DB
Path
• PCE specifies path as list of segment ids Request
TED
• PCC forwards traffic by pushing segment PCEP
id list on packets Segment List:: 10,20,30,40
• No path signaling required

Stateful
• Minimal forwarding state PCC
• Maximum network forwarding virtualization

• The state is no longer in the network but in
the packet In Out Int
L1 L1 Intf1 Forwarding
Node
• Paths may be PCE- or PCC-initiated SID
… … … table remains
L7 L7 Int3 constant
L8 Pop Intf3
Adjacency
… … …
SID
L9 Pop Intf5
Conclusion
Conclusion
• Simple routing extensions to implement source routing
• Packet path determined by prepended segment identifiers (one or more)
• Data plane agnostic (MPLS, IPv6)
• Network scalability and agility by reducing network state and simplifying
control plane
• Traffic protection with 100% coverage with more optimal routing
Recommended Follow-up Session:

Segment Routing: Technology and Use-cases (BRKRST-3122)
Participate in the “My Favorite Speaker” Contest
Promote Your Favorite Speaker and You Could Be a Winner
• Promote your favorite speaker through Twitter and you could win $200 of Cisco
Press products (@CiscoPress)
• Send a tweet and include
• Your favorite speaker’s Twitter handle @ciscomk
• Two hashtags: #CLUS #MyFavoriteSpeaker
• You can submit an entry for more than one of your “favorite” speakers
• Don’t forget to follow @CiscoLive and @CiscoPress
• View the official rules at http://bit.ly/CLUSwin
Complete Your Online Session Evaluation
• Give us your feedback to be
entered into a Daily Survey
Drawing. A daily winner will
receive a $750 Amazon gift card.
• Complete your session surveys
through the Cisco Live mobile
app or from the Session Catalog
on CiscoLive.com/us.
Don’t forget: Cisco Live sessions will be available

for viewing on-demand after the event at
CiscoLive.com/Online
Segment Routing Sessions
Cisco Live 2016
• Introduction to Segment Routing (BRKRST-2124)
• Segment Routing: Technology and Use-cases (BRKRST-3122)
• Application Engineered Routing: Allowing Applications to Program the Network (BRKSPG-2066)
• Segment Routing in Datacenter using Nexus 9000/3000 (BRKDCN-2050)
• Cisco WAN Automation Engine (WAE) Network Programmability with SR (LTRMPL-2104)
• Segment Routing in Datacenter using Nexus 9000/3000 (LABRST-2020)
• Next Generation Service Provider Network using Segment Routing & BIER (LABSPG-2012)
• DevNet Workshop – Application Engineered Egress Routing (DEVNET-2062)
• DevNet Workshop – Enabling Containers to Leverage SR (DEVNET-2063)
Continue Your Education
• Demos in the Cisco campus
• Walk-in Self-Paced Labs
• Table Topics
• Meet the Engineer 1:1 meetings
• Related sessions
Please join us for the Service Provider Innovation Talk featuring:
Yvette Kanouff | Senior Vice President and General Manager, SP Business
Joe Cozzolino | Senior Vice President, Cisco Services
Thursday, July 14th, 2016

11:30 am - 12:30 pm, In the Oceanside A room
What to expect from this innovation talk

• Insights on market trends and forecasts
• Preview of key technologies and capabilities
• Innovative demonstrations of the latest and greatest products
• Better understanding of how Cisco can help you succeed
Register to attend the session live now or

watch the broadcast on cisco.com
Backup Slides
IS-IS Configuration
• Required
• Wide metrics
• SR enabled under unicast address family
• Optional
• Prefix-SID configured under loopback(s) AF IPv4
• MPLS forwarding enabled automatically on all (non-passive) IS-IS
interfaces
• Adjacency-SIDs are automatically allocated for each adjacency
(Cisco IOS XR)
router isis DEFAULT
net 49.0001.1720.1625.5001.00
Enable Segment Routing for IPv4 with
metric-style wide
segment-routing mpls MPLS data plane
!
interface Loopback0
passive Advertise prefix SID 16041 (index 41) for
Loopback0
prefix-sid absolute 16041
!
!
point-to-point
!
!
!
(Cisco IOS XR)
router isis DEFAULT
net 49.0001.1720.1625.5001.00
Enable Segment Routing for IPv6 with
metric-style wide
segment-routing mpls MPLS data plane
!
interface Loopback0
passive Advertise prefix SID 16061 (index 61) for
Loopback0
!
!
point-to-point
!
!
!
OSPF Configuration
• OSPFv2 control plane
• Required
• Enable segment-routing under instance or area(s)
• Command has area scope, usual inheritance applies
• Enable segment-routing forwarding under instance, area(s) or interface(s)
• Command has interface scope, usual inheritance applies
• Optional
• Prefix-SID configured under loopback(s)
• MPLS forwarding enabled on all OSPF interfaces with
segment-routing forwarding configured
Configuring Segment Routing for IPv4 Using OSPF
(Cisco IOS XR)
router ospf DEFAULT
router-id 172.16.255.1
Enable Segment Routing with MPLS data
segment-routing forwarding mpls
area 0 plane
interface Loopback0
passive
prefix-sid absolute 16041 Advertise prefix SID 16041 (index 41) for
!
Loopback0
network point-to-point
!
!
!
Configuring Topology Independent Fast Reroute for IPv4
using Segment Routing and IS-IS (Cisco IOS XR)
router isis DEFAULT
net 49.0001.1720.1625.5001.00
metric-style wide
!
interface Loopback0
passive
!
!
fast-reroute per-prefix
fast-reroute per-prefix ti-lfa Enable TI-LFA for IPv4 prefixes on
! interface GigabitEthernet0/0/0/0
!
!
Configuring Topology Independent Fast Reroute for IPv6
using Segment Routing and IS-IS (Cisco IOS XR)
router isis DEFAULT
net 49.0001.1720.1625.5001.00
metric-style wide
!
interface Loopback0
passive
!
!
fast-reroute per-prefix
fast-reroute per-prefix ti-lfa Enable TI-LFA for IPv6 prefixes on
! interface GigabitEthernet0/0/0/0
!
!
Configuring a Mapping Server for SR and LDP
Interworking for IPv4 Using IS-IS (Cisco IOS XR)
router isis DEFAULT
net 49.0001.1720.1625.5001.00
address-family ipv4 unicast Construct active mapping policy using
metric-style wide
remotely learned and locally configured
segment-routing prefix-sid-map receive mappings (mapping client)
segment-routing prefix-sid-map advertise-local
! Advertise local mapping policy (mapping
server)
...
!
segment-routing Local prefix-to-SID mapping policy
address-family ipv4
prefix-sid-map
172.16.255.1/32 – 4041
172.16.255.1/32 4041 range 8 :
! 172.16.255.8/32 - 4048
!
!
Configuring a Mapping Client for SR and LDP
Interworking for IPv4 Using IS-IS (Cisco IOS XR)
router isis DEFAULT
net 49.0001.1720.1625.5001.00
metric-style wide
segment-routing prefix-sid-map receive Construct active mapping policy using
!
remotely learned and locally configured
interface Loopback0
passive mappings (mapping client)
!
!
point-to-point
!
!
!
Enabling Segment Routing Feature
NXOS
Commands:
feature bgp
install feature-set mpls
feature-set mpls
feature mpls l3vpn
feature mpls segment-routing
Under Interface configuration:

mpls ip forwarding
Thank you

BRKRST 2124 PDF

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

BRKRST 2124 PDF

Transféré par

Droits d'auteur :

Formats disponibles

Introduction to Segment Routing

Michael Kowal, Vertical Solutions Architect

• X is the “from” 10 Low BW

Close to 40 IETF drafts in progress

• Step3: LDP is removed from the nodes in SR SR

• Traffic Matrix is fundamental for 1

• centralized traffic engineering 3

• Most operators do not have an accurate

• With SR, the traffic matrix collection is

SRGB [16,000 – 23,999 ] SRGB [16,000 – 23,999 ]

Payload Payload Payload Payload

Push Swap Pop Pop

Payload Payload Payload Payload Payload

Payload Payload Payload Payload Payload

• Forwarding table remains constant PE

(Nodes + Adjacencies) regardless PE PE

• Prevents transient congestion and suboptimal routing

• Enforcing loop-freeness on post-convergence path

• Calculate LFA(s) Packet to Z Packet to Z

• Calculate P and Q spaces Packet to Z Packet to Z

• They overlap in this case R1 R2

• Calculate post-convergence SPT P-space

• Calculate P and Q spaces Packet to Z Packet to Z

the backup path P-space Q-space

database (established paths) LSP DB

• More optimal centralized path TED

• New BGP-LS attribute TLVs for SR BGP-LS BGP-LS

• PCE may return delegation

PCE initiates LSP DB LSP DB

• No path signaling required

• Maximum network forwarding virtualization

Recommended Follow-up Session:

Don’t forget: Cisco Live sessions will be available

Thursday, July 14th, 2016

What to expect from this innovation talk

Register to attend the session live now or

Under Interface configuration:

Vous aimerez peut-être aussi