Designing Programmable Accessd2zmdbbm9feqrf.cloudfront.net/2017/usa/pdf/BRKSPG-2210.pdf · Designing Programmable Access Networks Ahmed Abeer, Sr. Technical Marketing Engineer Nicolas

Designing Programmable Access Networks

Ahmed Abeer, Sr. Technical Marketing Engineer

Nicolas Breton, Product Manager

BRKSPG-2210

© 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public

Cisco Spark

Questions? Use Cisco Spark to chat with the speaker after the session

1. Find this session in the Cisco Live Mobile App

2. Click “Join the Discussion”

3. Install Spark or go directly to the space

4. Enter messages/questions in the space

How

Cisco Spark spaces will be available until July 3, 2017.

cs.co/ciscolivebot#BRKSPG-2210


Agenda

• What is Programmable Network

• Network Deployment or Device Automation

• Design & Build the Programmable Infrastructure

• Programmable Transport

• Network Discovery

• Compute & Program the Transport Path

• Next Step: Network Optimization, Service Enablement & Service Assurance

• Design Recommendation

• Conclusion


Session Objectives

• To understand how programmability impacts existing network designs.

• To learn techniques and tips to design programmable underlay and overlay.

• To learn concrete design recommendations.

BRKSPG-2210 5

Network High Level View & Requirement


Trends in the Service Provider TransportAccess and Aggregation

• Scale the access within a domain• Number of nodes and services increasing

• Bandwidth growth 10GE -> 100G

• Traffic load optimization

• Agile service deployment across domains• End to End service deployments

• Virtualization• Virtual CPE, Virtual NID

At the same time, keep the same Services KPI’s

OAM, Traffic load management,Transparent Node and Service insertion

Core

Access Domain A

Access Domain B

Access Domain C

BRKSPG-2210 7

© 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 8BRKSPG-2210

Challenges and Requirements

• Effortless device provisioning – ZTD/PNP

• SDN-friendly infrastructure

• Standardized API for network monitoring, management and control

Simple Operations

Increased Network Visibility

Agile End-to-end Service Deployment

Flexible Traffic Engineering

What is Programmable Network


Network Programmability What is changing in the network?

Core

Access Domain A

Access Domain B

Access Domain C

Core

Access Domain A

Access Domain B

Access Domain C

NMSService

Assurance

Traditional Programmatic Approach

Orchestration

WAN Optimization Engine

Path Computation

Topology Discovery

ProgrammableInterfaces

BRKSPG-2210

Segment Routing

OSS BSS

IP/MPLS/ L2

SNMP

CLI

XR Transport Controller

Open Source

10


Programmable Network – New Operation Model

11BRKSPG-2210

Model Driven Programmable InterfacesProgrammatic

Interfaces

Open

Protocols

Configuration

ManagementTraffic

Engineering

Operational

State

API

APIC EMIOS XR XML

NetconfRestconf

Protocols

Telemetry PCEPBGP-LS

Automatic Device Provisioning“The Day 0 Challenge”


Large number of devices to bring up

Devices distributed in different physical locations

Expected to be

service ready on bringup

Day 0 Challenges

• Simplify Day 0 device deployments• Limited or no ”Cli” changes on site

• Rely on the network (“in band”) for all steps of device preparations.

• Also called Zero Touch Provisioning

• Rapid Nodes and Service deployments• Hours to minutes

• Orchestrated

• Service-Ready Infrastructure• Standard programming interfaces

• Model driven: Uniform service provisioning

• Flexible traffic engineering

• Optional requirements• Service turn-up verifications

• Secured operations

• Indestructible management channel

BRKSPG-2210 13


Requirements to achieve full automation

• Bootstrap• Boot process initiated through the firmware

• Boot from WEB server using HTTP

• Uses DHCP to learn HTTP link for the bootable image

• Discovery• L2 VLAN discovery

• DHCP request/response

• Management interface ( “out of band”) versus network interfaces ( “inband”)

• Any network/Topology

• Downloads• Configuration downloads

• Image download

• Image installation

• Persistent connection with Management system

14BRKSPG-2210

Zero Touch Provisioning

Zero Touch Deployment

Zero Pre-staging

Plug&Play


Use Case 1: ZTP High Level Design

EPNM

MPLS

Management

VPNME1200

DCN

DCN

GW

Management VPN Peering Point

VL4094

DCN

GWeBGP

iBGP

4201/4202/4206

Provides both DHCP Server &

TFTP Server Functions

Generates Configuration

Files & Preconfigures

Aggregation Node

NCS

Aggregation

Node

DHCP Client &

TFTP ClientDHCP Request

DHCP Reply

TFTP Request

TFTP Reply

DHCP Client &

TFTP Client

Copy configuration file & preconfigure aggregation node

BRKSPG-2210 15


• Configuration is removed from ASR920 and the router is reloaded to start ZTP Process

Use Case 2: ZTP

BRKSPG-2210 16

Designing the Programmable UnderlayStep 1: Build a Programmable Transport


Why Segment Routing?

18BRKSPG-2210

Programmable MPLS

Domain A Domain B

ABR 1 ABR 2

Program MPLS labelsService labelSR-TE path

CLI>

OR

• More Control and Programmable

• Segment Routing Labels are assigned manually or programmed

• Simplifies the Control plane stack.

• Extension to IGP’s ( ISIS , OSPF)

• Seamless migration

• SR mapping server

• Traffic Engineering: SR-TE

• Single touch point at the headend

• Flexibility to optimize traffic load

• Control the path at very granular level

Head-End


Unified MPLS vs Segment RoutingIntra Domain

19BRKSPG-2210

LDP/IGP

Programmable MPLSUnified MPLS

ISIS-SR

MPLS Labels Unifed MPLS Segment Routing

Transport Labels Dynamic Label allocation (LDP) Programmed or cli

Service Labels Dynamic Label allocation (LDP) Programmed or cli

Program MPLS labels:Prefix SIDService Label

Prefix SIDsLDP LDP

LDPLDP

PWPW

LDP

CLI>

OR

Service Label


Unified MPLS vs Segment RoutingInter Domain

20BRKSPG-2210

Programmable MPLSUnified MPLS

Domain A Domain B

IGP / LDP IGP / LDP

BGP-LU

Domain A Domain B

2

31

LDP Label

BGP Label

Service Label

ABR 1

Swap

32

LDP Drop 3

32

Push

ABR 2

BGP-LU

IGP IGP

ABR 1 ABR 2

3

1 Next Hop Label

Service Label

2 Destination Label

3

12

BGP Label

32

2 TE Label 3 4

Program MPLS labelsPrefix SIDService Label

CLI>

OR

TE FRR / Remote LFA

Designing the Programmable UnderlayStep 2: PCE – Network Multi-Domain Visibility


BGP-LS Overview

• Build TED for Multi-area Optimal Path Computation

• Scalable Solution is BGP, not IGP.

• BGP-LS is an address-family

• afi=16388, safi=71

• Defined to carry IGP link-state database via BGP

• Supports both IS-IS and OSPF

• Delivers topology information to outside agents

Domain 1 Domain 2

Domain 0

BGP-LS

Traffic

Engineering

Databse (TED)

BGP-LS BGP-LS

RR

PCE

BRKSPG-2210 22


This network topology results in 18 BGP-LS objects.

• Common topology abstraction model

• IGP network modeled

• Three classes of objects

• Nodes

• Links

• prefixesNode1

Link1&2

Link3&4

BGP-LS Objects

• 3 nodes

• 6 links

• 9 prefix

Lo: 10.0.0.102

Lo: 10.0.0.101

Lo: 10.0.0.100

Link: 10.0.3.0

.102

.101

Link: 10.0.1.0

.100

.101

.102

.100

Link: 10.0.2.0

BRKSPG-2210 23

ODL/XTC

BGP-LS

Postman

REST API JSON/XML

WAE

RR

Node2

Node3

Node1


router ospf 1

distribute bgp-ls

router-id 10.0.0.100

address-family ipv4 unicast

area 0

interface Loopback0

network point-to-point

!

interface GigabitEthernet0/0/0/0


!



!

!

!

router bgp 64496

bgp router-id 10.0.0.100


!

address-family link-state link-state

!

neighbor 1.53.39.49

remote-as 64496

update-source MgmtEth0/RSP0/CPU0/0


!

address-family link-state link-state

route-reflector-client

24BRKSPG-2210

BGP Link State Device Configuration

Distribute OSPF link

state database into

BGP-LS

Enable link-state

addresses

Specify BGP-LS

peer

• BGP Link State Configuration only on 1 node per domain

• Node 1 only requires BGP LS configuration

Node1

Lo: 10.0.0.102

Lo: 10.0.0.101

Lo: 10.0.0.100

Link: 10.0.3.0

.102

.101

Link: 10.0.1.0

.100

.101

.102

.100

Link: 10.0.2.0

BGP LS configured on this node

Node2

Node3

Node1

Link1&2

Link3&4


ODL Configuration

BRKSPG-2210 25

ODL Beryllium

installation

PCEP/BGP-LS

installation inside

ODL


ODL Configuration

• Modify ~/etc/opendaylight/karaf/41-bgp-example.xml

• Change the local BGP RIB info. Search for "example-bgp-rib" and change the "local-as" and "bgp-rib-id" values to be your local AS and ODL's IP address.

• Add the peer (Node: 10.0.0.100). Look for the "example-bgp-peer" module, remove the comments around it, and edit the IP address.

BRKSPG-2210 26


RP/0/RSP0/CPU0:ASR9K0#sh bgp link-state link-state

BGP router identifier 10.0.0.100, local AS number 64496

BGP generic scan interval 60 secs

Non-stop routing is enabled

BGP table state: Active

Table ID: 0x0 RD version: 39

BGP main routing table version 39

BGP NSR Initial initsync version 11 (Reached)

BGP NSR/ISSU Sync-Group versions 0/0

BGP scan interval 60 secs

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

Prefix codes: E link, V node, T IP reacheable route, u/U unknown

I Identifier, N local node, R remote node, L link, P prefix

L1/L2 ISIS level-1/level-2, O OSPF, D direct, S static/peer-node

a area-ID, l link-ID, t topology-ID, s ISO-ID,

c confed-ID/ASN, b bgp-identifier, r router-ID,

i if-address, n nbr-address, o OSPF Route-type, p IP-prefix

d designated router address

Network Next Hop Metric LocPrf Weight Path

*> [V][O][I0x0][N[c64496][b10.0.0.100][a0.0.0.0][r10.0.0.100]]/376

0.0.0.0 0 I

*>[V][O][I0x0][N[c64496][b10.0.0.100][a0.0.0.0][r10.0.0.101]]/376

0.0.0.0 0 i

*> [V][O][I0x0][N[c64496][b10.0.0.100][a0.0.0.0][r10.0.0.102]]/376

0.0.0.0 0 I

*>[E][O][I0x0][N[c64496][b10.0.0.100][a0.0.0.0][r10.0.0.100]][R[c64496][b10.0.0.100][a0.0.0.0][r10.0.0.102]][L[i10.0.2.100][n10.0.2.102]]/792

0.0.0.0 0 i

27BRKSPG-2210

BGP Link State Verification

Node

V= node

O= OSPF

N= local node

c= Confed ID/ ASN -- 64496

b=bgp-id – 10.0.0.100

a=area-id -- 0.0.0.0

r=router-id -- 10.0.0.102

Check here for the

Prefix codes



0.0.0.0 0 i


0.0.0.0 0 I

*> [T][O][I0x0][N[c64496][b10.0.0.100][a0.0.0.0][r10.0.0.101]][P[o0x01][p10.0.1.0/24]]/480

0.0.0.0 0 i

*> [T][O][I0x0][N[c64496][b10.0.0.100][a0.0.0.0][r10.0.0.101]][P[o0x01][p10.0.3.0/24]]/480

0.0.0.0 0 i

*> [T][O][I0x0][N[c64496][b10.0.0.100][a0.0.0.0][r10.0.0.101]][P[o0x01][p10.0.0.101/32]]/488

0.0.0.0 0 i

*> [T][O][I0x0][N[c64496][b10.0.0.100][a0.0.0.0][r10.0.0.102]][P[o0x01][p10.0.2.0/24]]/480

0.0.0.0 0 i

*> [T][O][I0x0][N[c64496][b10.0.0.100][a0.0.0.0][r10.0.0.102]][P[o0x01][p10.0.3.0/24]]/480

0.0.0.0 0 i

*> [T][O][I0x0][N[c64496][b10.0.0.100][a0.0.0.0][r10.0.0.102]][P[o0x01][p10.0.0.102/32]]/488

0.0.0.0 0 i

Processed 18 prefixes, 18 paths

28BRKSPG-2210

BGP Link State Verification

Link

E=link

N=node


b=bgp-id – 10.0.0.100

a=area-id -- 0.0.0.0

r=router-id -- 10.0.0.101

R= remote node


b=bgp-id – 10.0.0.100

a=area-id -- 0.0.0.0

r=router-id -- 10.0.0.102

L=link

i= if-address -- 10.0.3.101

n=nbr-address – 10.0.3.103

Prefix

T= IP reacheable route

N=node


b=bgp-id – 10.0.0.100

a=area-id -- 0.0.0.0

r=router-id -- 10.0.0.101

P=prefix

o= ospf-route-typ -- 0x01

p= ip prefix – 10.0.0.101/32


Northbound BGP-LS Verification with RESTCONF

29BRKSPG-2210

Node1

Node2

Node3

Link3&4

Lo: 10.0.0.102

Lo: 10.0.0.101

Lo: 10.0.0.100

Link: 10.0.3.0

.102

.101.100

.100

ODL

BGP-LS

Postman

REST JSON/XML


Northbound BGP-LS Verification with RESTCONFGET BGP-LS Topology

http://admin:[email protected]:8181/restconf/operational/network-topology:network-topology/topology/example-linkstate-topology

{

"topology": [

{

"topology-id": "example-linkstate-topology",

"link": [

{

"link-id": "bgpls://Ospf:0/type=link&local-as=64496&local-domain=167772260&local-area=0&local-router=167772262&remote-

as=64496&remote-domain=167772260&remote-area=0&remote-router=167772261&ipv4-iface=10.0.3.102&ipv4-neigh=10.0.3.101”,

"source": {

"source-tp": "bgpls://Ospf:0/type=tp&ipv4=10.0.3.102",

"source-node": "bgpls://Ospf:0/type=node&as=64496&domain=167772260&area=0&router=167772262"

},

}

},

"destination": {

"dest-node": "bgpls://Ospf:0/type=node&as=64496&domain=167772260&area=0&router=167772261",

"dest-tp": "bgpls://Ospf:0/type=tp&ipv4=10.0.3.101"

}

},

---- Trim ----

BRKSPG-2210 30

TOPOLOGY

SOURCE

DESTINATION

LINK

http://admin:[email protected]:8181/restconf/operational/network-topology:network-topology/topology/example-linkstate-topology


OpenDaylight BGP-LS Topology Discovery

31BRKSPG-2210

2

1

3


BGP-LS Deployment Scenarios

BRKSPG-2210 32

SID: 16001

IGP Domain A

IGP Domain B

ABR 1 ABR 2

PCETopologyTE Database

Head-End(PCC)

SID: 16009SID: 16003

SID: 16008

BGP-LS

Design Scenario 1: Border Routers Peering with PCE

SID: 16001

IGP Domain A

IGP Domain B

ABR 1 ABR 2

PCETopologyTE Database

Head-End(PCC)

SID: 16009SID: 16003

SID: 16008

BGP-RR

Design Scenario 2: BGP RR Peering with PCE

BGP Speakers

Physical or Virtual RR

BGP-LS

BGP-LS

In Bold , design recommendation

Designing the Programmable UnderlayStep 3: Cisco PCE – Path Computation & Deployment


PCEP Architectural Introduction• Path computation

• Large, multi-domain and multi-layer networks

• 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 (synchronized with network)

• Path computation client (PCC)

• May send path computation requests to PCE

• May send path state updates to PCE

• Used between head-end router (PCC) and PCE to:

• Request/receive path from PCE subject to constraints

• State synchronization between PCE and router

• Hybrid CSPFBRKSPG-2210 34

PCEP

PCE

TED

LSP DB

PCC

PCC PCE

Open/Close/Keepalive

Open/Close/Keepalive

PCC PCE

Reply

Request

PCC PCE

Notification

Notification


Stateful PCE Models

SR Policy &

Path Request

PCE

• Out-of-network, stateful PCE server

• PCE always initiates LSPs

IGP-SR

Domain AIGP-SR

Domain B

ABR 1

BGP-LS BGP-LS

Speaker

ABR 2

Speaker

PCC

PCEP

BGP-LS

TED

LSP DB

PCEP

REST/NETCONFPCE

• PCC initiates LSPs or SR Policy

• PCE Compute Path b/w end points

IGP-SR

Domain AIGP-SR

Domain B

ABR 1

BGP-LS BGP-LS

Speaker

ABR 2

Speaker

PCC

PCEP

BGP-LS

TED

LSP DB

PCEP

PCC Initiated SR Policy PCE Initiated SR Policy

SR Policy

Initiator


interface tunnel-te0

ipv4 unnumbered Loopback0

signalled-name bar

destination 10.0.0.101

pce

delegation

!

!

!

mpls traffic-eng


!


!

pce

peer ipv4 1.53.39.49

!

stateful-client

instantiation

delegation

!

!

auto-tunnel pcc

tunnel-id min 101 max 200

36BRKSPG-2210

PCEP Device Configuration

PCC Initiated LSP &

Delegated to PCE.

Configuration Not

Required in Case of PCE

initiated Tunnel

Global Configuration under

MPLS TE

PCE Modes: Stateful PCE

Initiated LSP or PCC Initiated

& Delegated to PCE

Tunnel ID Rance.

Add LSP by PCE.

PCE creates tunnel

using assign Tunnel

ID from given range

• PCE configuration will be done on each node under mpls traffic-eng

• Node 1 only requires BGP LS configuration

Node1 (PCC)

Lo: 10.0.0.102

Lo: 10.0.0.101

Lo: 10.0.0.100

Link: 10.0.3.0

.102

.101

Link: 10.0.1.0

.100

.101

.102

.100

Link: 10.0.2.0

Lo: 10.0.0.100

.100

.100

ODL (PCE)

PCEP

Postman

REST

Node2

Node3

Node1


PCEP ODL Configuration

opendaylight-user@root>feature:install odl-restconf odl-l2switch-switch odl-

mdsal-apidocs odl-dlux-all

opendaylight-user@root>feature:install odl-bgpcep-bgp-all odl-bgpcep-pcep-

all

Note: No Configuration Required. There is no need to Modify any file for on ODL for PCEP

BRKSPG-2210 37

ODL Beryllium

installation

PCEP installation

inside ODL


ODL Server:

root@ubuntu:~/distribution-karaf-0.4.2-Beryllium-SR2/bin$ netstat -an | grep 4189

tcp6 0 0 :::4189 :::* LISTEN

tcp6 0 0 1.53.39.49:4189 10.0.0.101:39330 ESTABLISHED

tcp6 0 0 1.53.39.49:4189 10.0.0.100:55641 ESTABLISHED

tcp6 0 0 1.53.39.49:4189 10.0.0.102:14570 ESTABLISHED

Node 1:

RP/0/RSP0/CPU0:ASR9K0#show mpls traffic-eng pce peer

Address Precedence State Learned From

--------------- ------------ ------------ --------------------

1.53.39.49 255 Up Static config

38BRKSPG-2210

PCEP Verification

Verifying PCEP session

on the server ( PCE)

Verifying PCEP session

on the PCC




signalled-name bar


pce

delegation

!

!

!

mpls traffic-eng


!


!

pce

peer ipv4 1.53.39.49

!

stateful-client

instantiation

delegation

!

!

auto-tunnel pcc


39BRKSPG-2210

PCEP Example 1: PCC Initiated Tunnel (RSVP TE) & Path Computation from PCE via Update LSP

PCC Initiated LSP &

Delegated to PCE.

Configuration Not


initiated Tunnel


MPLS TE



& Delegated to PCE

Tunnel ID Range.

Add LSP by PCE.

PCE creates tunnel

using assign Tunnel

ID from given range

• PCE configuration will be done on each node under mpls traffic-en

Node1 (PCC)

Node2

Node3

Lo: 10.0.0.102

Lo: 10.0.0.101

Lo: 10.0.0.100

Link: 10.0.3.0

.102

.101

Link: 10.0.1.0

.100

.101

.102

.100

Link: 10.0.2.0

Lo: 10.0.0.100

.100

.100

ODL (PCE)

PCEP

Postman

REST


PCE Update LSP: PCE Path Computation

40BRKSPG-2210

Node1

Node2

Node3

Lo: 10.0.0.102

Lo: 10.0.0.101

Lo: 10.0.0.100.100

.101

.100

ODL

PCEP

Postman

REST JSON/XML

Lo: 10.0.0.100

Tunnel Te0

http://admin:[email protected]:8181/restconf/operations/network-topology-

pcep:update-lsp

{

"input" : {

"node" : "pcc://10.0.0.100",

"name" : "foo",

"network-topology-ref": "/network-topology:network-topology/network-

topology:topology[network-topology:topology-id=\"pcep-topology\"]",

"arguments": {

"lsp": {

"administrative": "true",

"delegate": "true"

},

"ero" : {

"subobject" : [

{

"loose" : "false",

"ip-prefix" : { "ip-prefix" : "10.0.2.102/32" }

},

{

"loose" : "false",


},

{

"loose" : "false",


}

]

}

}

}

IP address explicit

path

PCC node


RP/0/RSP0/CPU0:ASR9K0#sh mpls traffic-eng tunnels 1 detail

Name: tunnel-te1 Destination: 10.0.0.101 Ifhandle:0x160

Signalled-Name: foo

Status:

Admin: up Oper: up Path: valid Signalling: connected

path option 10, (verbatim) type explicit (autopcc_te1) (Basis for Setup, path weight 0)

G-PID: 0x0800 (derived from egress interface properties)

Bandwidth Requested: 0 kbps CT0

Creation Time: Wed Jun 15 23:49:36 2016 (17:58:27 ago)

Config Parameters:

Bandwidth: 0 kbps (CT0) Priority: 7 7 Affinity: 0x0/0xffff

Metric Type: TE (global)

Path Selection:

Tiebreaker: Min-fill (default)

Hop-limit: disabled

Cost-limit: disabled

Path-invalidation timeout: 10000 msec (default), Action: Tear (default)

AutoRoute: enabled LockDown: disabled Policy class: not set

Forward class: 0 (default)

Forwarding-Adjacency: disabled

Autoroute Destinations: 0

Loadshare: 0 equal loadshares

Auto-bw: disabled

Fast Reroute: Disabled, Protection Desired: None

Path Protection: Not Enabled

BFD Fast Detection: Disabled

Reoptimization after affinity failure: Enabled

Soft Preemption: Disabled

41BRKSPG-2210

PCEP Update LSP: VerificationPCE Delegation:

Symbolic name: foo

PCEP ID: 2

Delegated to: 1.53.39.49

SNMP Index: 39

Binding SID: 24004

History:

Tunnel has been up for: 02:05:43 (since Thu Jun 16 15:42:20 UTC 2016)

Current LSP:

Uptime: 02:05:43 (since Thu Jun 16 15:42:20 UTC 2016)

Current LSP Info:

Instance: 2, Signaling Area: PCE controlled


Outgoing Interface: GigabitEthernet0/0/0/18, Outgoing Label: 24004

Router-IDs: local 10.0.0.100

downstream 10.0.0.102

Soft Preemption: None

SRLGs: not collected

Path Info:

Outgoing:

Explicit Route:

Strict, 10.0.2.102

Strict, 10.0.3.101

Strict, 10.0.0.101

Record Route: Disabled

Tspec: avg rate=0 kbits, burst=1000 bytes, peak rate=0 kbits

Session Attributes: Local Prot: Not Set, Node Prot: Not Set, BW Prot: Not Set

Soft Preemption Desired: Not Set

------- Output Trim -------

Tunnel is up and

connected Tunnel is delegated

to PCE

PCE control

Explicit path




signalled-name SRTE


pce

delegation

!

!

!

mpls traffic-eng


!


!

pce

peer ipv4 1.53.39.49

!

segment-routing

stateful-client

instantiation

delegation

!

!

auto-tunnel pcc


42BRKSPG-2210

PCEP Example 2: PCE Initiated Tunnel (SR TE): Add LSP Operation

PCC Initiated LSP &

Delegated to PCE.

Configuration Not


initiated Tunnel


MPLS TE



& Delegated to PCE

Tunnel ID Rance.

Add LSP by PCE.

PCE creates tunnel

using assign Tunnel

ID from given range

• PCE configuration will be done on each node under mpls traffic-en

Node1 (PCC)

Node2

Node3

Lo: 10.0.0.102

SID: 16002

Lo: 10.0.0.101

SID: 16003

Lo: 10.0.0.100

Link: 10.0.3.0

.102

.101

Link: 10.0.1.0

.100

.101

.102

.100

Link: 10.0.2.0

Lo: 10.0.0.100

SID: 16001

.100

.100

ODL (PCE)

PCEP

Postman

REST


PCE Initiated Tunnel: Add LSP Operation

43BRKSPG-2210

Node1

Node2

Node3

Lo: 10.0.0.102

SID: 16002

Lo: 10.0.0.101

SID: 16003

Lo: 10.0.0.100.100

.101

.100

ODL

PCEP

Postman

REST JSON/XML

Lo: 10.0.0.100

SID: 16001

"ero": {

"subobject": [

{

"loose": false,

"m-flag": true,

"sid": 16002,

"sid-type": "ipv4-node-id"

},

{

"loose": false,

"m-flag": true,

"sid": 16001,

"sid-type": "ipv4-node-id"

}

]

},

"path-setup-type": {

"pst": 1

}

}

}

}

http://admin:[email protected]:8181/restc

onf/operations/network-topology-pcep:add-lsp

{

"input" : {

"node" : "pcc://10.0.0.102",

"name" : "SRTE-Labels-WebJSON",

"network-topology-ref": "/network-

topology:network-topology/network-

topology:topology[network-topology:topology-

id=\"pcep-topology\"]",

"arguments": {

"lsp": {

"administrative": true,

"delegate": true

},

"lspa": {

"hold-priority": 0,

"include-any": 0,

"setup-priority": 0

},

"endpoints-obj": {

"ipv4": {

"destination-ipv4-address":

"10.0.0.100",

"source-ipv4-address": "10.0.0.102"

}

},

LSP Path

http://admin:[email protected]:8181/restconf/operations/network-topology-pcep:add-lsp


Name: tunnel-te106 Destination: 10.0.0.100 Ifhandle:0x2e0 (auto-tunnel pcc)

Signalled-Name: SRTE-Labels-WebJSON

Status:

Admin: up Oper: up Path: valid Signalling: connected

path option 10, (Segment-Routing) type explicit (autopcc_te106) (Basis for Setup)

Protected-by PO index: none

G-PID: 0x0800 (derived from egress interface properties)

Bandwidth Requested: 0 kbps CT0

Creation Time: Thu Jun 16 21:41:30 2016 (00:00:39 ago)

Config Parameters:

Bandwidth: 0 kbps (CT0) Priority: 0 0 Affinity: 0x0/0x0

Metric Type: TE (global)

Path Selection:

Tiebreaker: Min-fill (default)

Protection: any (default)

Hop-limit: disabled

Cost-limit: disabled

Path-invalidation timeout: 10000 msec (default), Action: Tear (default)

AutoRoute: disabled LockDown: disabled Policy class: not set

Forward class: 0 (default)

Forwarding-Adjacency: disabled

Autoroute Destinations: 0

Loadshare: 0 equal loadshares

Auto-bw: disabled

Path Protection: Not Enabled

BFD Fast Detection: Disabled

Reoptimization after affinity failure: Enabled

SRLG discovery: Disabled

44BRKSPG-2210

PCEP Add LSP: VerificationAuto PCC:

Symbolic name: SRTE-Labels-WebJSON

PCEP ID: 107


Created by: 1.53.39.49

PCE Delegation:

Symbolic name: SRTE-Labels-WebJSON

PCEP ID: 107


SNMP Index: 49

Binding SID: 24015

History:

Tunnel has been up for: 00:00:39 (since Thu Jun 16 21:41:30 UTC 2016)

Current LSP:


Prior LSP:

ID: 2 Path Option: 10

Removal Trigger: reoptimization completed

Current LSP Info:

Instance: 3, Signaling Area: PCE controlled


Soft Preemption: None

SRLGs: not collected

Path Info:

Segment-Routing Path Info (PCE controlled)

Segment0[Node]: 10.0.0.101, Label: 16002

Segment1[Node]: 10.0.0.100, Label: 16001

Displayed 1 (of 2) heads, 0 (of 1) midpoints, 0 (of 0) tails

Displayed 1 up, 0 down, 0 recovering, 0 recovered heads

Tunnel is created

and controlled by

PCE

Explicit pathUp and connected

Initiated by PCE


PCEP Example 3: Remove LSP Operation

• PCE configuration will be done on each node under mpls traffic-eng

Node1 (PCC)

Node2

Node3

Lo: 10.0.0.102

SID: 16002

Lo: 10.0.0.101

SID: 16002

Lo: 10.0.0.100

Link: 10.0.3.0

.102

.101

Link: 10.0.1.0

.100

.101

.102

.100

Link: 10.0.2.0

Lo: 10.0.0.100

SID: 16001

.100

.100

ODL (PCE)

PCEP

Postman

REST


Cisco PCE - XR Transport Controller (XTC)

• Multi-Domain Topology Collection

• Real-time reactive feed

• Computation

• Native SR-TE algorithms

• Applicable to Centralized (Controller) and Distributed (Router) deployments

An IOS XR-powered Stateful Path Computation Element (PCE)

Multi-Domain

Topology

North-Bound API

Computation

“Collection”

BGP-LS

ISIS / OSPF

“Deployment”

PCEP

or

BGP-SAFI

WAE Custom app

XTC

BRKSPG-2210 46


XTC - Stateful PCE

• XTC remembers the request and updates the SID list upon any topology change• Anycast SID’s and Local FRR (TILFA) minimize traffic loss during the stateful re-optimization

vPE1

20001

ToR

20002

Spine

20003DCI1

17001LSR

17002AGG1

16001

LSR

16002

AGG2

16003

vPE2

20001

ToR

20002Spine

20003DCI2

18001

LSR

18002

DC A1 METRO A METRO BWAN DCB2

Overlay

CTRL, RR… 1: Overlay route OV1 is @ vPE1 with TE policy (minimize latency)

2: REQUEST: vPE1

with Min LAT?

SR

PCE

4

3: REPLY {16003,

16002, 16001, 17002,

17001, 20001}

5: BGP-LS update:

DCI1 is down

6: UPDATE{16003,

16002, 16001, 17002,

17011, 20001}

DCI11

17011

BRKSPG-2210 47


XTC – High Avalability

• We leverage well-known standardized PCE HA

vPE1

20001

ToR

20002

Spine

20003DCI1

17001LSR

17002AGG1

16001

LSR

16002

AGG2

16003

vPE2

20001

ToR

20002Spine

20003DCI2

18001

LSR

18002


Overlay

CTRL, RR… 1: Overlay route OV1 is @ vPE1 with TE policy (minimize latency)

2: REQUEST:

vPE1

with Min LAT?

SR

PCE2

Secondary

SR

PCE1

Primary

3: REPLY {16003,

16002, 16001,

17002, 17001,

20001}

4: REPORT:

{16003, 16002,

16001, 17002,

17001, 20001} is

OK,

PCE1 is master

5

6: wait for

some timer

7: REPORT:

PCE2 becomes

master

8: (optionally, if this

PCE would have a

different SID list as

solution)

UPDATE: (new

SID list)

9: (optionally if 8

happened),

REPORT (new SID

list): OK

BRKSPG-2210 48


XTC - Fundamentally Distributed

• XTC not to be considered as a single “god” box

• XTC is closer to RR

• Different vPE’s can use different pairs of XTC’s

• XTC preference can either be based on proximity or service

vPE1

20001

ToR

20002

Spine

20003

DCI1

17001

17901

LSR

17002

AGG1

16001

16901

LSR

16002

AGG2

16003

16902

vPE2

20001

ToR

20002Spine

20003

DCI2

18001

18901

LSR

18002


DCI11

17011

17901

AGG11

16011

16901

AGG12

16013

16902

DCI21

18011

18901

SR

PCE

SR

PCE

SR

PCE

SR

PCESR

PCE

SR

PCE

SR

PCE

SR

PCE

BRKSPG-2210 49


XTC - Stitching Policies

• End-to-end policies can be composed from more basic ones• An SRTE policy is bound by default to a Binding SID

• Benefits: shorter SID list and churn isolation between domains• Even if the WAN-MetroA sub-path changes, the related Binding SID 4001 is constant

vPE1

20001

ToR

20002

Spine

20003DCI1

17001LSR

17002AGG1

16001

LSR

16002

AGG2

16003

vPE2

20001

ToR

20002Spine

20003DCI2

18001

LSR

18002


SR

PCE

2: vPE1 with Min LAT?

3: REPLY {16003, 4001, 20001}

;; instead of

{16003, 16002, 16001,

17002, 17001, 20001}

1: REPORT

{16002, 16001, 17002, 17001},

UP, BindingSID 4001

BRKSPG-2210 50


XTC Use Cases

Domain1 Domain2

I:100

I:100

I:100

I:100

SR

PCE

SR

PCE

1 2 3

45

6 7 8

SID-list:

{16002, 16003}

Default IGP link metric: I:10

Default TE link metric: T:10

• There is no a-priori route distribution between domains

Inter-Domain Path – Best Effort (IGP)Inter-Domain Path – Low Latency (TE)

Domain1 Domain2

I:100

I:100

I:100

I:100

SR

PCE

SR

PCE

1 2 3

45

6 7 8


Default TE link metric: T:10

• There is no a-priori route distribution between domains

• An end-to-end policy is requested

SID-list:

{30102, 30203}

BRKSPG-2210 51


Domain1

SID-list:

{30102, 30203}

SID-list:

{16007, 16008}

Domain2

XTC Use Cases (Contd…)

• Two dynamic paths between two different pairs of (headend, endpoint) must be disjoint from each other

I:100


I:100

I:100

I:100

SR

PCE

SR

PCE

1 2 3

45

6 7 8

Service Disjointness - Node

Domain1

SID-list:

{30102, 30203}

SID-list:

{16007, 16008}

Domain2

• Two dynamic paths from same headend must be disjoint from each other via Link

I:100


I:100

I:100

I:100

SR

PCE

SR

PCE

1 2 3

45

6 7 8

Service Disjointness - Link

XTC supports Disjointness – SRLG but not covered here 52

Next Step:Network Optimization, Service Enablement & Service Assurance


• Multi-Application Engine for the SP WAN

• Network planning and optimization

• On Demand Bandwidth Calendaring

• Demand placement

• Interact with traffic management apps

• Topology and traffic abstraction

• Multi-Vendor platform

• Compliments NSO and Open SDN Controller (ODL)

WAE: WAN Automation Engine

http://www.cisco.com/go/wae

Sourc

eDestination

SDN Orchestration & ControlConfiglet NSO EMS/NMSODL/OSC …

Traffic Management Applications

REST

REST/NETCONF

NETCONF/PCEP/BGP-LS

BRKSPG-2210 54

http://www.cisco.com/go/wae


Network Services Orchestrator (NSO)

• Multi-vendor service orchestrator o Distributed service configuration management

o Transaction integrity

o Validation and rollback

• Single pane of glass for:o L2-L7 networking

o Hardware Devices

o Virtual Appliances

• YANG Model Driven Orchestrationo Service Data models

o Device Data Model

o Network Element Driver

• Highly Scalable for large infrastructure

o One of the existing deployment is managing 60K devices on the network

Network Element Drivers

Device Manager

Service Manager

Network Services Orchestrator (NSO) Service

Models

Device

Models

Network-wide CLI, Web UIREST, Java, NETCONF

Network

Engineer

Management

Applications

End-to-End

Transactions

NETCONF, CLI, SNMP, REST, etc.

• Applications

• Controllers

BRKSPG-2210 55

Design Recommendations


High-Level Solution Building Blocks

WAE

SNMP NetFlowCLI

XTC NSO (NEDs)

NETCONF/

YANGCLI

BGP-

LSPCEP

NSO (Network Orchestrator) “Service Abstraction” Service models & orchestration

“Network Abstraction”Path computation, Network model

“Device Abstraction”Controllers, Protocols, NED’s

“Protocols”SB network protocols

“Network”Equipment and Devices

Segment

Routing

BRKSPG-2210 57


Use BGP-LS and build a Topology Database

58BRKSPG-2210

• One BGP-LS speaker per domain

• Collects LS for the all IGP domain

• Scalable solution

• Topology can be shared northbound

• Share the topology with other apps.

• XTC preferred

• Topology information shared with WAE/NSO through Netconf or REST

TopologyDatabase

Wan Optimization WAE

Controller ODL

vRouter XRv9000 XTC

IGP-SR

Domain AIGP-SR

Domain B

ABR 1

BGP-LS BGP-LS

Speaker

ABR 2

Speaker

BGP-LS



Enable Path Computation and Engineer the network

59BRKSPG-2210

IGP-SR

Domain AIGP-SR

Domain B

ABR 1

BGP-LS BGP-LS

Speaker

ABR 2

Speaker

PCC

PCEP

BGP-LS

• Rely on SR Policy

• Path and tunnel computation

• XTC is for both inter and intra domain path computation

• Compute Path based on User’s constraints

• Reachability

• Low Latency

• Disjointness

• Program SR Policy

• PCE Initiated

• PCC Initiated


Controller ODL

vRouter XRv9000 XTC

Controller ODL

vRouter XRv9000 XTC



Enable Path Computation and Engineer the network

60BRKSPG-2210

IGP-SR

Domain AIGP-SR

Domain B

ABR 1

BGP-LS BGP-LS

Speaker

ABR 2

Speaker

PCC

PCEP

BGP-LS

• For inter domain optimization, use WAE

• WAN Optimization, Bandwidth Calendaring

• GUI Interface

• Analytics

• Network Topology

• XTC shares Topology information through Netconf/Yang


Controller ODL

vRouter XRv9000 XTC

Controller ODL

vRouter XRv9000 XTC


Controller ODL

vRouter XRv9000 XTC

Controller ODL

vRouter XRv9000 XTC

Controller ODL

vRouter XRv9000 XTC

Controller ODL

vRouter XRv9000 XTC

Controller ODL

vRouter XRv9000 XTC

Controller ODL

vRouter XRv9000 XTCWan Optimization WAE

NETCONF/REST


Service Creation

61BRKSPG-2210

IGP-SR

Domain AIGP-SR

Domain B

ABR 1

BGP-LS BGP-LS

Speaker

ABR 2

Speaker

PCC

PCEP

BGP-LS


Controller ODL

vRouter XRv9000 XTC

Controller ODL

vRouter XRv9000 XTC


Controller ODL

vRouter XRv9000 XTC

Controller ODL

vRouter XRv9000 XTC

Controller ODL

vRouter XRv9000 XTC

Controller ODL

vRouter XRv9000 XTC

Controller ODL

vRouter XRv9000 XTC

Controller ODL

vRouter XRv9000 XTCWan Optimization WAE

NETCONF/YANG

• Service creation with NSO

• Yang model service definition

• Service Options:

• MEF services (ELINE, ELAN)

• Business Services ( VPNs)

• Residential Services

• Consistent service definition

• Multi vendor environment

• Northbound interface for Apps

Orchestrator NSO

REST

Applications


On-demand Next-hop (ODN) Solution Highlights

• On-demand Next-hop automates and simplifies the service head end configuration

• No SR-TE tunnel config on the head end router

• No explicit steering on the service head end for the service• For example: no autoroute-announce, no static routes

• The SR Policy is deployed when needed

• The learning of the service route, initiates the SR policy, and traffic-to-policy mapping

• Example of a service route: vpnv4 route

BRKSPG-2210

• Automatic SR policies

• Inter-AS & Seamless MPLS: no

need for BGP-LU (RFC3107)XRv-1 XRv-3

XRv-2XRv-4

XRv-5 XRv-7

XRv-6XRv-8

XRv-9

XRv-10

ISIS SRAccess West (L2)

AS 64001

ISIS SRCore (L2)AS64002

ISIS SRAccess East (L1)

AS64002

XTC-AS1-11

SR PCE

XTC-AS1-12

SR PCE

XTC-AS2-14

SR PCE

WAENSO

XTC-AS2-13

SR PCE

Recommendation:

Use RR and PCE Separately

62



AS 64001

XRv-3XRv-1

XRv-2 XRv-4

XRv-5

XRv-6

XRv-7

XRv-8

XRv-9

XRv-10

18001

18002

18003

18004

16005

16006

16007

16008

18009

18010

SR ODN Solution Workflow NSO/CLI

1• NSO instantiates an L3 VPN service on PEs

• Note: NO transport elements configured by NSO

ISIS SRCore (L2)

ISIS SRAccess East (l1)AS64002

BRKSPG-2210 63



AS 64001

XRv-3XRv-1

XRv-2 XRv-4

XRv-5

XRv-6

XRv-7

XRv-8

XRv-9

XRv-10

BGP RR

18001

18002

18003

18004

16005

16006

16007

16008

18009

18010

SR ODN Solution Workflow

BGP RR

BGP VPNv4

BGP VPNv4

2 • Routes tagged with a user-defined community

to convey SLA requirements

• VPN routes propagated via BGP

BGP VPNv4

BGP comm.

“gold”

BGP comm.

“gold”

ISIS SRCore (L2)


BRKSPG-2210 64



AS 64001

XRv-3XRv-1

XRv-2 XRv-4

XRv-5

XRv-6

XRv-7

XRv-8

XRv-9

XRv-10

18001

18002

18003

18004

16005

16006

16007

16008

18009

18010

SR ODN Solution Workflow (cont.)3 • Ingress PE matches on user-specified BGP community

• Ingress PE enforces policy associated with the community

SR PCE

Need a path to node (9)?

Minimizing TE metric

<policy_sample>

IF

BGP comm == “gold”

THEN

contact PCE

request path to BGP NH

minimize TE metric

PCReq

ISIS SRCore (L2)


BRKSPG-2210 65



AS 64001

XRv-3XRv-1

XRv-2 XRv-4

XRv-5

XRv-6

XRv-7

XRv-8

XRv-9

XRv-10

18001

18002

18003

18004

16005

16006

16007

16008

18009

18010

SR ODN Solution Workflow (cont.)4

• PCE computes path

• PCE replies to PCC with SR-EROs (segment (SID) list)

PCRep

SR PCE

SR-EROs

Label 1

Label 2

Label 3

ISIS SRCore (L2)


BRKSPG-2210 66



AS 64001

XRv-3XRv-1

XRv-2 XRv-4

XRv-5

XRv-6

XRv-7

XRv-8

XRv-9

XRv-10

18001

18002

18003

18004

16005

16006

16007

16008

18009

18010

SR ODN Solution Workflow (cont.)

5 • PE programs SR-TE policy in FIB

• PE allocates a Binding-SID (B-SID) to it

• PE programs forwarding for VPN route via B-SID of SR-TE policy

B-SID = 24001

FIB

Y/24 via label 24001

ISIS SRCore (L2)


BRKSPG-2210 67



AS 64001

XRv-3XRv-1

XRv-2 XRv-4

XRv-5

XRv-6

XRv-7

XRv-8

XRv-9

XRv-10

18001

18002

18003

18004

16005

16006

16007

16008

18009

18010

SR ODN Solution Workflow (cont.)

6 • Traffic destined to VPN prefixes automatically steered onto SR-TE policy

• Note: NO feature required for steering (no auto-route announce, no PBR, no PBTS)

IPDA

Y.0.0.1

FIB

Y/24 via label 24001

B-SID = 24001

ISIS SRCore (L2)


BRKSPG-2210 68

Conclusions


Summary

• Automation

• Configuration through Netconf/Yang Models

• Network Simplification with Segment Routing

• Enable Topology Discovery

• Enable inter Domains Traffic Engineering

BRKSPG-2210

Core

Access Domain B

Access Domain C

Programmatic Approach

1- Automate the network setup

3- Simplify MPLS transport with Segment routing

4- Turn on BGP-LS

5- Turn on PCEP

BRKSPG-2210 70

2- Use of Netconf/Yang

Controllers, Orchestrators


References

• Agile Carrier Ethernet Demonstration on Youtube -https://www.youtube.com/watch?v=biYqyAn9rl0

• Segment Routing .net - http://www.segment-routing.net/

• Segment Routing Demo Friday - https://www.sdxcentral.com/resources/sdn-demofriday/segment-routing-cisco-demofriday/

• Cisco Programmability Yang blog - http://blogs.cisco.com/tag/yang

• Tail-f netconf yang tutorials - http://www.tail-f.com/education/

• BGP-LS linkedin blog: https://www.linkedin.com/pulse/introduction-open-api-bgp-link-state-bgp-ls-source-controller-abeer?trk=prof-post

• Netconf linkedin blog: https://www.linkedin.com/pulse/netconf-rfc-6242-protocol-tutorial-ahmed-n-abeer?trk=prof-post

BRKSPG-2210 71

https://www.youtube.com/watch?v=biYqyAn9rl0

http://www.segment-routing.net/

https://www.sdxcentral.com/resources/sdn-demofriday/segment-routing-cisco-demofriday/

http://blogs.cisco.com/tag/yang

http://www.tail-f.com/education/

https://www.linkedin.com/pulse/introduction-open-api-bgp-link-state-bgp-ls-source-controller-abeer?trk=prof-post

https://www.linkedin.com/pulse/netconf-rfc-6242-protocol-tutorial-ahmed-n-abeer?trk=prof-post


• Give us your feedback to be entered into a Daily Survey Drawing. A daily winner will receive a $750 gift card.

• Complete your session surveys through the Cisco Live mobile app or on www.CiscoLive.com/us.

Complete Your Online Session Evaluation

Don’t forget: Cisco Live sessions will be available for viewing on demand after the event at www.CiscoLive.com/Online.

http://www.ciscolive.com/us

http://ciscolive.com/Online

http://ciscolive.com/Online

http://www.ciscolive.com/Online


Continue Your Education

• Demos in the Cisco campus

• Walk-in Self-Paced Labs

• Lunch & Learn

• Meet the Engineer 1:1 meetings

• Related sessions

73BRKSPG-2210

Thank you


Design Cisco Education OfferingsCourse Description Cisco Certification

Designing Cisco Network Service Architectures

(ARCH) Version 3.0

Provides learner with the ability to perform conceptual, intermediate, and

detailed design of a network infrastructure that supports desired capacity,

performance, availability required for converged Enterprise network

services and applications.

CCDP® (Design Professional)

(Available Now)

Designing for Cisco Internetwork Solutions

(DESGN) Version 3.0

Instructor led training focused on fundamental design methodologies used

to determine requirements for network performance, security, voice, and

wireless solutions. Prepares candidates for the CCDA certification exam.

CCDA® (Design Associate)

(Available Now)

76

For more details, please visit: http://learningnetwork.cisco.com

Questions? Visit the Learning@Cisco Booth

BRKSPG-2210

http://learningnetwork.cisco.com/


Network Programmability Cisco Education OfferingsCourse Description Cisco Certification

Developing with Cisco Network Programmability

(NPDEV)

Provides Application Developers with comprehensive curriculum to

develop infrastructure programming skills;

Addresses needs of software engineers who automate network

infrastructure and/or utilize APIs and toolkits to interface with SDN

controllers and individual devices

Cisco Network Programmability

Developer (NPDEV) Specialist

Certification

Designing and Implementing Cisco Network

Programmability (NPDESI)

Provides network engineers with comprehensive soup-to-nuts curriculum

to develop and validate automation and programming skills;

Directly addresses the evolving role of network engineers towards more

programmability, automation and orchestration

Cisco Network Programmability

Design and Implementation

(NPDESI) Specialist Certification

Programming for Network Engineers (PRNE) Learn the fundamentals of Python programming – within the context of

performing functions relevant to network engineers. Use Network

Programming to simplify or automate tasks

Recommended pre-requisite for

NPDESI and NPDEV Specialist

Certifications

Cisco Digital Network Architecture

Implementation Essentials (DNAIE)

This training provides students with the guiding principles and core

elements of Cisco’s Digital Network Architecture (DNA) architecture and its

solution components including; APIC-EM, NFV, Analytics, Security and

Fabric.

None

77



BRKSPG-2210



Service Provider Cisco Education OfferingsCourse Description Cisco Certification

Deploying Cisco Service Provider Network Routing

(SPROUTE) & Advanced (SPADVROUTE)

Implementing Cisco Service Provider Next-Generation

Core Network Services (SPCORE)

Edge Network Services (SPEDGE)

SPROUTE covers the implementation of routing protocols (OSPF, IS-IS, BGP),

route manipulations, and HA routing features; SPADVROUTE covers advanced

routing topics in BGP, multicast services including PIM-SM, and IPv6;

SPCORE covers network services, including MPLS-LDP, MPLS traffic engineering,

QoS mechanisms, and transport technologies;

SPEDGE covers network services, including MPLS Layer 3 VPNs, Layer 2 VPNs,

and Carrier Ethernet services; all within SP IP NGN environments.

CCNP Service Provider®

Building Cisco Service Provider Next-Generation

Networks, Part 1&2 (SPNGN1), (SPNGN2)

The two courses introduce networking technologies and solutions, including OSI

and TCP/IP models, IPv4/v6, switching, routing, transport types, security, network

management, and Cisco OS (IOS and IOS XR).

CCNA Service Provider®

Implementing Cisco Service Provider Mobility UMTS

Networks (SPUMTS);

Implementing Cisco Service Provider Mobility CDMA

Networks (SPCDMA);

Implementing Cisco Service Provider Mobility LTE

Networks (SPLTE)

The three courses (SPUMTS, SPCDMA, SPLTE) cover knowledge and skills

required to understand products, technologies, and architectures that are found in

Universal Mobile Telecommunications Systems (UMTS) and Code Division Multiple

Access (CDMA) packet core networks, plus their migration to Long-Term Evolution

(LTE) Evolved Packet Systems (EPS), including Evolved Packet Core (EPC) and

Radio Access Networks (RANs).

Cisco Service Provider Mobility

CDMA to LTE Specialist;

Cisco Service Provider Mobility UMTS

to LTE Specialist

Implementing and Maintaining Cisco Technologies

Using IOS XR (IMTXR)

Service Provider/Enterprise engineers to implement, verification-test, and optimize

core/edge technologies in a Cisco IOS XR environment.

Cisco IOS XR Specialist

78



BRKSPG-2210


Documents

Designing Programmable Accessd2zmdbbm9feqrf.cloudfront.net/2017/usa/pdf/BRKSPG-2210.pdf · Designing Programmable Access Networks Ahmed Abeer, Sr. Technical Marketing Engineer Nicolas