Designing Programmable Access Networks - BRKSPG-2210

Transcription

1

2 Designing Programmable Access Networks - BRKSPG-2210 Ahmed Abeer, Senior Technical Marketing Engineer Nicolas Breton, Product Manager BRKSPG-2210

3 Agenda Programmability Overview Transport Evolution Device Level Programmability Network Level Programmability Design Recommendation Conclusion

4 Programmability Overview

5 Session Objectives To educate the audience on programmability technologies. To understand what is available today and what futures are that enable Programmability. To learn how to design and migrate to programmable networks. BRKSPG Cisco and/or its affiliates. All rights reserved. Cisco Public 5

6 Software Defined Network: An industry Trend Decoupled Control and Data Planes Highly Centralized Control (aka SDN Controller) or Hybrid Greater application interaction with the network Physical Applications Control Plane Data Plane Virtual SDN Definition (ONF): The physical separation of the network control plane from the forwarding plane, and where a control plane controls several devices. An opportunity to re-think the relationship between network hardware and software BRKSPG Cisco and/or its affiliates. All rights reserved. Cisco Public 6

7 Network Functions Virtualization Transition of network services to run on virtualized compute infrastructure Decoupling the service from the device Elastic, consumption-based service model Purpose built appliances Servers! VNFs Virtual Network Function running as application on servers Create the need for Application Program Interfaces ( API ) BRKSPG Cisco and/or its affiliates. All rights reserved. Cisco Public 7

8 Therefore the need for Network Programmability Configuration Management Programmatic Interfaces Operational State Open Protocols Traffic Engineering Model Driven Programmable Interfaces Physical and Virtual Network Infrastructure BRKSPG Cisco and/or its affiliates. All rights reserved. Cisco Public 8

9 Transport Evolution

10 Trends in the Service Provider Transport Access and Aggregation Scale the access within a domain Number of nodes and services increasing Bandwidth growth 10GE -> 100G Traffic load optimization Access Domain C Deploy services across domains End to End service deployments Virtualization Virtual CPE, Virtual NID Access Domain A Rapid Nodes and Service deployments Hours to minutes Orchestrated At the same time, keep the same Services KPI s Core Access Domain B OAM, Traffic load management, Transparent Node and Service insertion BRKSPG Cisco and/or its affiliates. All rights reserved. Cisco Public 10

11 Network Programmability What is changing in the network? Traditional Programmatic Approach Access Domain C Access Domain C IP/MPLS/ L2 Segment Routing Core Core Access Domain A SNMP CLI Access Domain B Netconf Yang Access Domain A BGP LS PCEP Netconf Yang Access Domain B NMS Service Assurance OSS BSS Orchestration NSO by Tail-F WAN Optimization Engine Engine WAE Open Source Controller ODL BRKSPG Cisco and/or its affiliates. All rights reserved. Cisco Public 11

12 Automation of the Network

13 Automation through Device Activation CA AAA Server Config Access Ring 2 Access Ring 1 Non AN MPLS Non AN Access Ring 1 Config TFTP Config Config Config Automatic bring-up process Full Automation Zero Pre-staging Any network/topology Config download Image download/ Upgrade Persistent connection with Management system BRKSPG Cisco and/or its affiliates. All rights reserved. Cisco Public 13

14 Zero Touch Deployment (ZTD) Options ZTD Distributed Centralized PnP Auto IP Autonomic IPXIE nv satellite Discovery and bootstrap Device Level - Network level Device level Config Download Yes No Yes Yes (scripting) Image Upgrade Yes No No Yes (scripting) Secure Basic level No Yes No Auto IP Address Mgmt Discovery Auto Configuration Auto Image Upgrade Limitation: No network level discovery Limitation: No discovery Require Configuration Limitation: IPv6 Infrastructure Image upgrade Limitation: Limited security Require scripting for download ( puppet) Limitation: L1 and L2 Network Support Only BRKSPG Cisco and/or its affiliates. All rights reserved. Cisco Public 14

15 Introduce Segment Routing

16 Segment Routing Overview 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 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 Multi-Vendor solution BRKSPG Cisco and/or its affiliates. All rights reserved. Cisco Public 16

17 Why Segment Routing? More Control and Programmable Segment Routing Labels are assigned manually or programmed Simplifies the Control plane stack. Extension to IGP s ( ISIS, OSPF) Enabling SR in existing MPLS network is simple. Seamless migration Program MPLS labels Service label Programmable MPLS BRKSPG Cisco and/or its affiliates. All rights reserved. Cisco Public 17

18 Segment Routing: IGP segments IGP Prefix Segments Shortest-path to the IGP prefix Equal Cost MultiPath (ECMP)-aware Global Segment Label = Index Advertised as index IGP Adjacency Segment Forward on the IGP adjacency Local Segment Advertised as label value Distributed by ISIS/OSPF Distributed by ISIS/OSPF All nodes use default SRGB16,000 23,999 BRKSPG Cisco and/or its affiliates. All rights reserved. Cisco Public 18

19 Combining IGP Segments Steer traffic on any path through the network Path is specified by list of segments in packet header, a stack of labels No path is signaled No per-flow state is created Single protocol: IS-IS or OSPF Packet to Packet to All nodes use default SRGB 16,000 23, BRKSPG Cisco and/or its affiliates. All rights reserved. Cisco Public 19

20 Unified MPLS vs Segment Routing Intra Domain LDP/IGP Service Label Program MPLS labels: Prefix SID Service Label CLI> OR LDP LDP Prefix SIDs LDP PW LDP LDP PW ISIS-SR Unified MPLS Programmable MPLS MPLS Labels Unifed MPLS Segment Routing Transport Labels Dynamic Label allocation (LDP) Programmed or cli Service Labels Dynamic Label allocation (LDP) Programmed or cli BRKSPG Cisco and/or its affiliates. All rights reserved. Cisco Public 20

21 Unified MPLS vs Segment Routing Inter Domain Unified MPLS Programmable MPLS Program MPLS labels Prefix SID Service Label CLI> OR ABR 1 ABR 1 ABR 1 ABR 1 Domain A Domain B Domain A Domain B 3 1 Service Label BGP Label 3 2 Swap LDP Label LDP Drop 3 2 TE Label 3 4 Push 3 Service Label 2 Destination Label 1 Next Hop Label BGP Label 3 2 IGP / LDP BGP-LU TE FRR / Remote LFA IGP / LDP IGP BRKSPG-2210 BGP-LU IGP 2016 Cisco and/or its affiliates. All rights reserved. Cisco Public 21

22 Device Level Programmability

23 Device Level Programmability Operational cost to manage different vendor s devices Different CLIs, Different Operating Systems Different Support SNMP s Structured Management Interface (SMI) Limitations Web customers need device level APIs to manage the network Protocols NETCONF RESTCONF YANG SEGMENT ROUTING TELEMETRY BRKSPG Cisco and/or its affiliates. All rights reserved. Cisco Public 24

24 NETCONF and YANG

25 What is NETCONF? Introduction & Background NETCONF = Network Configuration Protocol IETF configuration management protocol Addresses Next-Gen Configuration Management Requirement ( RFC3535 ) Content Configuration Data, Notification Data (XML) Client Operations Messages <get>, <get-config>,<edit-config>, <commit>, <lock>/<unlock>, <close-session> etc <rpc>, <notification>,<rpc-reply> Server Transport SSH, BEEP, SOAP, TLS BRKSPG Cisco and/or its affiliates. All rights reserved. Cisco Public 26

26 What is NETCONF? NETCONF Configuration Data Stores Four in total Running mandatory Startup and Candidate optional Startup Running Candidate Files / URLs Configuration Data Stores BRKSPG Cisco and/or its affiliates. All rights reserved. Cisco Public 27

27 NETCONF Session Flow Step 1: Router Configuration & NETCONF Session Instantiation 2 ssh root@ p 830 -s netconf Client 1 Device Configuration: Server (config)# ssh server v2 Server (config)# ssh server netconf Server (config)# ssh timeout 120 Server (config)# netconf-yang agent ssh Server (config)# commit crypto key generate dsa SSH Server IP Address: BRKSPG Cisco and/or its affiliates. All rights reserved. Cisco Public 28

28 NETCONF Session Flow Step 2: Hello Message, TCP Connection & Capability Exchange Client <hello xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> <capabilities> <capability>urn:ietf:params:netconf:base:1.1</capability> <capability>urn:ietf:params:netconf:capability:candidate:1.0</capability> <capability>urn:ietf:params:netconf:capability:rollback-on-error:1.0</capability> <capability>urn:ietf:params:netconf:capability:validate:1.1</capability> <capability>urn:ietf:params:netconf:capability:confirmedcommit:1.1</capability> </capabilities> <session-id> </session-id> </hello>]]>]]> SSH Server 3 <?xml version="1.0" encoding="utf-8"?> <hello xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> <capabilities> <capability>urn:ietf:params:netconf:base:1.0</capability> <capability>urn:ietf:params:netconf:base:1.1</capability> </capabilities> </hello>]]>]]> BRKSPG Cisco and/or its affiliates. All rights reserved. Cisco Public 29

29 NETCONF Session Flow Step 3: Netconf <get-config> Operation with Sub-tree filtering 4 Client #411 <?xml version="1.0" encoding="utf-8"?> <rpc message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> <get-config> <source> <running/> </source> <filter type="subtree"> <aaa xmlns=" <usernames/> </aaa> </filter> </get-config> </rpc> ## SSH Server BRKSPG Cisco and/or its affiliates. All rights reserved. Cisco Public 30

30 NETCONF Session Flow Step 3: Netconf <get-config> Operation with Sub-tree filtering SSH Client #517 <?xml version="1.0"?> <rpc-reply message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> <data> <aaa xmlns=" <usernames> <username> <name>root</name> <usergroup-under-usernames> <usergroup-under-username> <name>root-system</name> </usergroup-under-username> </usergroup-under-usernames> <secret>$1$/cai$uamdqj9qsrqpdqvdxtx/h/</secret> </username> </usernames> </aaa> </data> </rpc-reply> ## Server BRKSPG Cisco and/or its affiliates. All rights reserved. Cisco Public 31

31 NETCONF Session Flow Step 4: Netconf <edit-config> Operation with Filtering On #938 <?xml version="1.0" encoding="utf-8"?> <rpc message-id="105" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> <edit-config> <target> <candidate/> </target> <config type="subtree"> <interface-configurations xmlns=" <interface-configuration> <active>act</active> <interface-name>gigabitethernet0/0/0/7</interface-name> <description>cl Vegas Presenter is Boring</description> -----TO BE CONTINUED----- Client 5 SSH ----CONTINUED----- <ipv4-network xmlns=" <addresses> <primary> <address> </address> <netmask> </netmask> </primary> </addresses> </ipv4-network> </interface-configuration> </interface-configurations> </config> </edit-config> </rpc> ## Server BRKSPG Cisco and/or its affiliates. All rights reserved. Cisco Public 32

32 NETCONF Session Flow Step 4: Netconf <edit-config> Operation with Filtering On #119 <?xml version="1.0"?> <rpc-reply message-id="105" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> <ok/> </rpc-reply> ## SSH Client 6 Server Server#sh running-config int GigabitEthernet 0/0/0/7 interface GigabitEthernet0/0/0/7 description CL Vegas Presenter is Boring bandwidth cdp ipv4 address shutdown BRKSPG Cisco and/or its affiliates. All rights reserved. Cisco Public 33

33 Flow Breakdown - Request #171<?xml version="1.0" encoding="utf-8"?><rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="1"> NETCONF RPC (Message) Layer <get-config> <source> <running/> </source> <filter type="subtree"> <interface-configurations xmlns=" <interface-configuration> <interface-name>loopback0</interface-name> </interface-configuration> </interface-configurations> </filter> </get-config> </rpc> ## BRKSPG-2210 Operation Layer Content Layer Framing Marker 2016 Cisco and/or its affiliates. All rights reserved. Cisco Public 34

34 YANG in the context of Netconf Mgmt info (definition) Mgmt info (payload) Mgmt Services Remote Operations Transport YANG modules XML-encoded content Netconf operations <edit-config>, <get-config>, <get> Netconf RPC <rpc>, <rpc-reply> TLS, SSH Manager (client) Agent (server) Conceptual Data Store XML content per YANG BRKSPG Cisco and/or its affiliates. All rights reserved. Cisco Public 35

35 Yang Module Definition Module Header Definitions Module Submodule Logical Definition Structure Grouping Uses Augments Type definitions typedef Data definitions and Instance Structure Container Leaf List Leaf-list Choice anyxml Case Non-data items Notification RPC Conformance feature deviation BRKSPG Cisco and/or its affiliates. All rights reserved. Cisco Public 36

36 Yang Service Model Definition IETF data type For IOS XR devices myvpnservice Instances Service name Loopback Loopback Int 1/1 Int 1/2 DEVICE A DEVICE B BRKSPG Cisco and/or its affiliates. All rights reserved. Cisco Public 37

37 Yang Service Model Definition Loopbacks Devices Interfaces Circuit ID Loopback Loopback Int 1/1 DEVICE A DEVICE B BRKSPG Cisco and/or its affiliates. All rights reserved. Cisco Public 38

38 YANG Model Strategy Overview Industry Standard Models Cisco Common Models Cisco OS Device Specific Models Customer Models IETF, OpenConfig MEF Models across XR, XE, NX-OS XR, XE, NX-OS Specific Models provided by customers Standardization takes time. High priority to implement when models are standardized Consistent behavior across OSs Higher priority than OS specific models when available Fastest time to market Expose OS specific behavior Provided by customer Prioritized on a case by case basis BRKSPG Cisco and/or its affiliates. All rights reserved. Cisco Public 39

39 RESTCONF Section

40 RESTCONF Restful protocol to access YANG defined data Remote State Transfer Server maintains no session state HTTP URLs reflect data hierarchy in a YANG-modelled datastore RESTCONF GET POST PUT PATCH DELETE OPTIONS HEAD Netconf <get-config>, <get> <edit-config> ( create ) <edit-config> ( replace ) <edit-config> ( merge ) <edit-config> ( delete ) (discover supported operations) (get without body) BRKSPG Cisco and/or its affiliates. All rights reserved. Cisco Public 41

41 Resource URL Map /restconf /config /<top-level-data-nodes> (configuration data) /operational /<top-level-data-nodes> (operational data) /modules /module /name /revision /namespace /feature /deviation /operations /<custom protocol operations> /streams /stream /name /description /replay-support /replay-log-creation-time /events /version (field) YANGdefined data Meta-information: Capabilities etc Meta-information: Supported RPCs Event streams, subscribe using get, can specify filters BRKSPG Cisco and/or its affiliates. All rights reserved. Cisco Public 42

42 RESTCONF Example BRKSPG Cisco and/or its affiliates. All rights reserved. Cisco Public 43

43 YANG NETCONF versus RESTCONF Mgmt info (definition) YANG modules Mgmt info (encoding) XML content XML content JSON NETCONF Operations NETCONF Get-config, Edit-config RESTCONF GET, POST RESTCONF Messages RPC HTTP YANG Transport TLS SSH TCP BRKSPG Cisco and/or its affiliates. All rights reserved. Cisco Public 44

44 Network Level Programmability

45 Network Level Programmability Where are we today Lack of Visibility Black holing Difficult to Troubleshoot Scalability challenges Protocols/Open APIs BGP Link State (BGP-LS) Path Computation Element Protocol (PCEP) BGP FlowSec (BGP-FS) Application Engineering Routing (AER) Controllers & Orchestrator Network Service Orchestrator (NSO) WAN Automation Engine (WAE) XR Traffic Controller (XTC) OpenDaylight (ODL) BRKSPG Cisco and/or its affiliates. All rights reserved. Cisco Public 46

46 Cisco s Controllers & Orchestrators

47 Network Services Orchestrator (NSO) Multi-vendor service orchestrator o o o Distributed service configuration management Transaction integrity Validation and rollback Single pane of glass for: o o o L2-L7 networking Hardware Devices Virtual Appliances YANG Model Driven Orchestration o o o Service Data models Device Data Model Network Element Driver Highly Scalable for large infrastructure o One of the existing deployment is managing 60K devices on the network Management Applications REST, Java, NETCONF Network Services Orchestrator (NSO) Service Manager Device Manager Network-wide CLI, Web UI Network Element Drivers NETCONF, CLI, SNMP, REST, etc. Network Engineer Service Models Device Models End-to-End Transactions Applications Controllers BRKSPG Cisco and/or its affiliates. All rights reserved. Cisco Public 48

48 Cisco s Open SDN Controller Cisco s Commercial Edition Of Open Daylight One-Click Install Pre-Installed Apps BGPLS Manager visualizes network topology from BGP database Inventory augmented OpenDaylight Nodes app identifies all connected devices (YANG) Model Explorer exposes system models and previews JSON API body OpenFlow Manager manages, visualizes and troubleshoots flows + previews JSON API body PCEP Manager creates, modifies and deletes MPLS LSPs VMware ESXi and Oracle Virtual Box hypervisor ready Centralized OA&M Robust user, application and feature administration Status monitoring: system, cluster, node Event logging Real-time CPU, memory, disk, heap size, load and network utilization metrics See also: 49 BRKSPG Cisco and/or its affiliates. All rights reserved. Cisco Public 49

49 WAE: WAN Automation Engine 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 Traffic Management Applications REST REST/NETCONF SDN Orchestration & Control Configlet NSO ODL/OSC EMS/NMS NETCONF/PCEP/BGP-LS Compliments NSO and Open SDN Controller (ODL) Sourc e Destination BRKSPG Cisco and/or its affiliates. All rights reserved. Cisco Public 50

50 BGP-LS: BGP Link-State

51 BGP-LS Overview Optimal Path Computation for Multi-area TE 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 0 BGP-LS PCE BGP-LS BGP-LS RR Traffic Engineering Databse (TED) Domain 1 Domain 2 BRKSPG Cisco and/or its affiliates. All rights reserved. Cisco Public 52

52 BGP-LS Internals BGP-LS NLRI NLRI Type defines the object class Object Class = Node/link/prefix NLRI body is a set of TLV NLRI contains the data that identifies an object BGP-LS attribute Optional non-transitive Encode properties of the object Data consists of TLVs TLVs are specific to the object class Node attribute TLVs Link attribute TLVs Prefix attribute TLVs Note: With the combination of Node and Link objects one can construct a topology info and IP Prefix object will provide IP reachability information. BRKSPG Cisco and/or its affiliates. All rights reserved. Cisco Public 53

53 This network topology results in 18 BGP-LS objects. Common topology abstraction model IGP network modeled Three classes of objects Nodes Links prefixes BGP-LS Objects 3 nodes 6 links 9 prefix Postman REST API JSON/XML ODL WAE RR Lo: Node2 BGP-LS Link: Link1&2 Node1.100 Link: Link3& Lo: Node3 Link: Lo: BRKSPG Cisco and/or its affiliates. All rights reserved. Cisco Public 54

54 BGP Link State Device Configuration BGP Link State Configuration only on 1 node per domain Node 1 only requires BGP LS configuration BGP LS configured on this node Node1 Lo: Link: Node2.102 Link1&2.101 Link: Link3&4.102 Lo: Lo: Link: Node3 router ospf 1 distribute bgp-ls router-id address-family ipv4 unicast area 0 interface Loopback0 network point-to-point! interface GigabitEthernet0/0/0/0 network point-to-point! interface GigabitEthernet0/0/0/18 network point-to-point!!! router bgp bgp router-id address-family ipv4 unicast! address-family link-state link-state! neighbor remote-as update-source MgmtEth0/RSP0/CPU0/0 address-family ipv4 unicast! address-family link-state link-state route-reflector-client BRKSPG-2210 Distribute OSPF link state database into BGP-LS Enable link-state addresses Specify BGP-LS peer 2016 Cisco and/or its affiliates. All rights reserved. Cisco Public 55

55 ODL Configuration ODL Beryllium installation PCEP/BGP-LS installation inside ODL BRKSPG Cisco and/or its affiliates. All rights reserved. Cisco Public 56

56 ODL Configuration Modify ~/etc/opendaylight/karaf/41-bgp-example.xml Change the local BGP RIB info. Search for "example-bgp-rib" and change the "localas" and "bgp-rib-id" values to be your local AS and ODL's IP address. Add the peer (Node: ). Look for the "example-bgp-peer" module, remove the comments around it, and edit the IP address. BRKSPG Cisco and/or its affiliates. All rights reserved. Cisco Public 57

57 BGP Link State Verification RP/0/RSP0/CPU0:ASR9K0#sh bgp link-state link-state BGP router identifier , local AS number 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 Check here for the Prefix codes 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][b ][a ][r ]]/ I *>[V][O][I0x0][N[c64496][b ][a ][r ]]/ i *> [V][O][I0x0][N[c64496][b ][a ][r ]]/ I Node V= node O= OSPF N= local node c= Confed ID/ ASN b=bgp-id a=area-id r=router-id *>[E][O][I0x0][N[c64496][b ][a ][r ]][R[c64496][b ][a ][r ]][L[i ][n ]]/ i BRKSPG Cisco and/or its affiliates. All rights reserved. Cisco Public 58

58 BGP Link State Verification *>[E][O][I0x0][N[c64496][b ][a ][r ]][R[c64496][b ][a ][r ]][L[i ][n ]]/ i *>[E][O][I0x0][N[c64496][b ][a ][r ]][R[c64496][b ][a ][r ]][L[i ][n ]]/ I *> [T][O][I0x0][N[c64496][b ][a ][r ]][P[o0x01][p /24]]/ i *> [T][O][I0x0][N[c64496][b ][a ][r ]][P[o0x01][p /24]]/ i *> [T][O][I0x0][N[c64496][b ][a ][r ]][P[o0x01][p /32]]/ i *> [T][O][I0x0][N[c64496][b ][a ][r ]][P[o0x01][p /24]]/ i *> [T][O][I0x0][N[c64496][b ][a ][r ]][P[o0x01][p /24]]/ Prefix 0 i *> [T][O][I0x0][N[c64496][b ][a ][r ]][P[o0x01][p /32]]/ i Processed 18 prefixes, 18 paths T= IP reacheable route N=node c= Confed ID/ ASN b=bgp-id a=area-id r=router-id P=prefix o= ospf-route-typ -- 0x01 p= ip prefix /32 Link E=link N=node c= Confed ID/ ASN b=bgp-id a=area-id r=router-id R= remote node c= Confed ID/ ASN b=bgp-id a=area-id r=router-id L=link i= if-address n=nbr-address BRKSPG Cisco and/or its affiliates. All rights reserved. Cisco Public 59

59 Northbound BGP-LS Verification with RESTCONF Postman REST ODL JSON/XML Node2 Lo: BGP-LS.102 Node1.100 Link3&4 Link: Lo: Node3 Lo: BRKSPG Cisco and/or its affiliates. All rights reserved. Cisco Public 60

60 Northbound BGP-LS Verification with RESTCONF GET BGP-LS Topology { "topology": [ { "topology-id": "example-linkstate-topology", "link": [ { "link-id": "bgpls://ospf:0/type=link&local-as=64496&local-domain= &local-area=0&local-router= &remoteas=64496&remote-domain= &remote-area=0&remote-router= &ipv4-iface= &ipv4-neigh= , "source": { SOURCE "source-tp": "bgpls://ospf:0/type=tp&ipv4= ", "source-node": "bgpls://ospf:0/type=node&as=64496&domain= &area=0&router= " }, } }, "destination": { "dest-node": "bgpls://ospf:0/type=node&as=64496&domain= &area=0&router= ", "dest-tp": "bgpls://ospf:0/type=tp&ipv4= " } }, ---- Trim ---- TOPOLOGY LINK DESTINATION BRKSPG Cisco and/or its affiliates. All rights reserved. Cisco Public 61

61 1 OpenDaylight BGP-LS Topology Discovery 2 3 BRKSPG Cisco and/or its affiliates. All rights reserved. Cisco Public 62

62 BGP-LS deployment Design considerations Deployment model IGP redistribution into BGP-LS Advertisement of BGP-LS NLRIs to RR. RR sends information to external agents Topology Server PCE BGP-LS Speaker BGP-LS RR BGP-LS Speaker IGP Domain IGP Domain IGP Domain BRKSPG Cisco and/or its affiliates. All rights reserved. Cisco Public 63

63 PCEP: Path Computation Element Protocol

64 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) PCEP PCC PCE LSP DB TED 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 CSPF Open/Close/Keepalive PCC PCE Open/Close/Keepalive Request PCC PCE Reply Notification PCC PCE Notification BRKSPG Cisco and/or its affiliates. All rights reserved. Cisco Public 65

65 PCE Models Stateless PCE (ABR) PCEP Stateless PCC Area 1 Area 2 PCC-initiated LSP Area PCEP 0 ABRs act as stateless PCEs ABRs implement backward recursive PCE-Based Computation Inter-Area MPLS TE Stateless PCE (ABR) Stateless PCC PCCinitiated LSP PCEP Stateless PCE Area 0 BGP-LS / SNMP / CLI Area 1 Area 2 TED Out-of-network, stateless PCE server PCC initiates LSPs Application Statef ul PCC PCE-initiated LSP PCEP WAN Orchestration Path Request Stateful PCE (NS-OS) BGP-LS / SNMP / CLI Out-of-network, stateful PCE server PCE always initiates LSPs LSP DB TED BRKSPG Cisco and/or its affiliates. All rights reserved. Cisco Public 66

66 PCEP Device Configuration PCE configuration will be done on each node under mpls traffic-eng Node 1 only requires BGP LS configuration ODL (PCE) PCEP Postman REST Node1 (PCC) Lo: Lo: Link: Node Link: Lo: Link: Node3 interface tunnel-te0 ipv4 unnumbered Loopback0 signalled-name bar destination pce delegation!!! mpls traffic-eng interface GigabitEthernet0/0/0/0! interface GigabitEthernet0/0/0/18! pce peer ipv ! stateful-client instantiation delegation!! auto-tunnel pcc tunnel-id min 101 max 200 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 Lo: BRKSPG Cisco and/or its affiliates. All rights reserved. Cisco Public 67

67 PCEP ODL Configuration ODL Beryllium installation odl-restconf odl-l2switch-switch odlmdsal-apidocs odl-dlux-all odl-bgpcep-bgp-all odl-bgpcep-pcepall PCEP installation inside ODL Note: No Configuration Required. There is no need to Modify any file for on ODL for PCEP BRKSPG Cisco and/or its affiliates. All rights reserved. Cisco Public 68

68 PCEP Verification ODL Server: netstat -an grep 4189 tcp6 0 0 :::4189 :::* LISTEN tcp : :39330 ESTABLISHED tcp : :55641 ESTABLISHED tcp : :14570 ESTABLISHED Verifying PCEP session on the server ( PCE) Node 1: RP/0/RSP0/CPU0:ASR9K0#show mpls traffic-eng pce peer Address Precedence State Learned From Up Static config Verifying PCEP session on the PCC BRKSPG Cisco and/or its affiliates. All rights reserved. Cisco Public 69

69 PCEP Example 1: PCC Initiated Tunnel (RSVP TE) & Path Computation from PCE via Update LSP PCE configuration will be done on each node under mpls traffic-en ODL (PCE) PCEP Postman REST Node1 (PCC) Lo: Lo: Link: Node Link: Lo: Link: Node3 interface tunnel-te0 ipv4 unnumbered Loopback0 signalled-name bar destination pce delegation!!! mpls traffic-eng interface GigabitEthernet0/0/0/0! interface GigabitEthernet0/0/0/18! pce peer ipv ! stateful-client instantiation delegation!! auto-tunnel pcc tunnel-id min 101 max 200 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 Lo: BRKSPG Cisco and/or its affiliates. All rights reserved. Cisco Public 70

70 PCE Update LSP: PCE Path Computation PCEP Postman REST ODL Node1 JSON/XML Lo: Lo: Node2 Tunnel Te0.101 Lo: Lo: Node3 { PCC node "input" : { "node" : "pcc:// ", "name" : "foo", "network-topology-ref": "/network-topology:network-topology/networktopology:topology[network-topology:topology-id=\"pcep-topology\"]", "arguments": { "lsp": { "administrative": "true", "delegate": "true" } }, "ero" : { "subobject" : [ { "loose" : "false", "ip-prefix" : { "ip-prefix" : " /32" } }, { "loose" : "false", "ip-prefix" : { "ip-prefix" : " /32" } }, { "loose" : "false", "ip-prefix" : { "ip-prefix" : " /32" } } ] } BRKSPG-2210 IP address explicit path 2016 Cisco and/or its affiliates. All rights reserved. Cisco Public 71

71 PCEP Update LSP: Verification RP/0/RSP0/CPU0:ASR9K0#sh mpls traffic-eng tunnels 1 detail Name: tunnel-te1 Destination: Ifhandle:0x160 Signalled-Name: foo Status: Admin: up Oper: up Path: valid Signalling: connected Tunnel is up and 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: (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: 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 PCE Delegation: Symbolic name: foo PCEP ID: 2 Delegated to: SNMP Index: 39 Binding SID: 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 Uptime: 02:05:43 (since Thu Jun 16 15:42:20 UTC 2016) Outgoing Interface: GigabitEthernet0/0/0/18, Outgoing Label: Router-IDs: local downstream Soft Preemption: None SRLGs: not collected Path Info: Outgoing: Explicit Route: Strict, Strict, Strict, Tunnel is delegated to PCE PCE control Explicit path 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 BRKSPG Cisco and/or its affiliates. All rights reserved. Cisco Public 72

72 PCEP Example 2: PCE Initiated Tunnel (SR TE): Add LSP Operation PCE configuration will be done on each node under mpls traffic-en ODL (PCE) PCEP Postman REST Node1 (PCC) Lo: Lo: SID: Link: Node Link: Lo: SID: Link: Node3 Lo: SID: interface tunnel-te100 ipv4 unnumbered Loopback0 signalled-name SRTE destination pce delegation!!! mpls traffic-eng interface GigabitEthernet0/0/0/0! interface GigabitEthernet0/0/0/18! pce peer ipv ! segment-routing stateful-client instantiation delegation!! auto-tunnel pcc tunnel-id min 101 max 200 BRKSPG-2210 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 2016 Cisco and/or its affiliates. All rights reserved. Cisco Public 73

73 PCE Initiated Tunnel: Add LSP Operation Postman REST JSON/XML ODL PCEP Node Lo: Lo: SID: Node2.101 Lo: SID: Node3 Lo: onf/operations/network-topology-pcep:add-lsp { "input" : { "node" : "pcc:// ", "name" : "SRTE-Labels-WebJSON", "network-topology-ref": "/networktopology:network-topology/networktopology:topology[network-topology:topologyid=\"pcep-topology\"]", "arguments": { "lsp": { "administrative": true, "delegate": true }, "lspa": { "hold-priority": 0, "include-any": 0, "setup-priority": 0 }, "endpoints-obj": { "ipv4": { "destination-ipv4-address": " ", "source-ipv4-address": " " } }, "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 } LSP Path SID: BRKSPG Cisco and/or its affiliates. All rights reserved. Cisco Public 74

74 PCEP Add LSP: Verification Name: tunnel-te106 Destination: 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: (00:00:39 ago) Config Parameters: Bandwidth: Metric Type: TE (global) Path Selection: Tiebreaker: Min-fill (default) Protection: any (default) Hop-limit: disabled Cost-limit: disabled 0 kbps (CT0) Priority: 0 0 Affinity: 0x0/0x0 Path-invalidation timeout: 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 Up and connected Initiated by PCE Auto PCC: Symbolic name: SRTE-Labels-WebJSON PCEP ID: 107 Delegated to: Created by: PCE Delegation: Symbolic name: SRTE-Labels-WebJSON PCEP ID: 107 Delegated to: SNMP Index: 49 Binding SID: History: Tunnel has been up for: 00:00:39 (since Thu Jun 16 21:41:30 UTC 2016) Current LSP: Uptime: 00:00:39 (since Thu Jun 16 21:41:30 UTC 2016) Prior LSP: ID: 2 Path Option: 10 Removal Trigger: reoptimization completed Current LSP Info: Instance: 3, Signaling Area: PCE controlled Uptime: 00:00:39 (since Thu Jun 16 21:41:30 UTC 2016) Soft Preemption: None SRLGs: not collected Path Info: Segment-Routing Path Info (PCE controlled) Segment0[Node]: , Label: Segment1[Node]: , Label: 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 path BRKSPG Cisco and/or its affiliates. All rights reserved. Cisco Public 75

75 PCEP Example 3: Remove LSP Operation PCE configuration will be done on each node under mpls traffic-en Postman REST ODL (PCE) Node2.102 PCEP Link: Node1 (PCC) Lo: SID: Link: Lo: Lo: SID: Link: Node3 Lo: SID: BRKSPG Cisco and/or its affiliates. All rights reserved. Cisco Public 76

76 Putting it all together

77 Putting it all together Agile Carrier Ethernet Extending Segment Routing into Carrier Ethernet Access Network Agile Carrier Ethernet Partner API REST Portal - Programmable transport - Device level Programmability - Network level Programmability Results in: NSO + IOS-XRv Connect the Application to the infrastructure Reduce opex by simplifying network operation Enable fast service deployment Static Label BGP-LS BGP-LU BGP-LU BGP-LS BGP-LU Static Label Customer_E-LINE SR Metro Backbone SR Metro BRKSPG Cisco and/or its affiliates. All rights reserved. Cisco Public 78

78 Use BGP-LS and build a Topology Database One BGP-LS speaker per domain Collects LS for the all IGP domain Scalable solution Wan Optimization WAE Topology can be shared northbound Controller vrouter ODL XRv9000 XTC Topology Database Share the topology with other apps. XTC preferred BGP-LS Topology information shared with WAE/NSO through Netconf/yang IGP-SR Domain A Speaker BGP-LS Speaker BGP-LS IGP-SR Domain B ABR 1 ABR 2 In Bold, design recommendation BRKSPG Cisco and/or its affiliates. All rights reserved. Cisco Public 79

79 Enable Path Computation and Engineer the network Rely on SR-TE Path and tunnel computation Program TE tunnels Source, Destination explicit route path Controller vrouter Wan Optimization Controller vrouter ODL XRv9000 XTC WAE ODL XRv9000 XTC PCEP PCC BGP-LS Speaker Speaker IGP-SR Domain A BGP-LS BGP-LS IGP-SR Domain B ABR 1 ABR 2 In Bold, design recommendation BRKSPG Cisco and/or its affiliates. All rights reserved. Cisco Public 80

80 Enable Path Computation and Engineer the network Controller Wan vrouter Optimization ODL XRv9000 WAE XTC For inter domain optimization, use WAE Controller ODL WAN Optimization, Bandwidth Calendaring GUI Interface Analytics Network Topology XTC shares Topology information through Netconf/Yang vrouter Wan Optimization Controller vrouter NETCONF/YANG XRv9000 XTC WAE ODL XRv9000 XTC PCEP PCC BGP-LS Speaker Speaker IGP-SR Domain A BGP-LS BGP-LS IGP-SR Domain B ABR 1 ABR 2 In Bold, design recommendation BRKSPG Cisco and/or its affiliates. All rights reserved. Cisco Public 81

81 Service Creation Applications RSD REST Controller Wan vrouter Optimization ODL XRv9000 WAE XTC Service creation with NSO Yang model service definition Orchestrator NSO Controller vrouter ODL XRv9000 XTC Service Options: MEF services (ELINE, ELAN) Business Services ( VPNs) Residential Services Consistent service definition Multi vendor environment PCC Wan Optimization Controller vrouter NETCONF/YANG BGP-LS Speaker WAE ODL XRv9000 XTC Speaker PCEP Northbound interface for Apps IGP-SR Domain A BGP-LS BGP-LS IGP-SR Domain B ABR 1 ABR 2 In Bold, design recommendation BRKSPG Cisco and/or its affiliates. All rights reserved. Cisco Public 82

82 Summary Controllers, Orchestrators 5- Turn on PCEP Automation Configuration through Netconf/Yang Models Network Simplification with Segment Routing Enable Topology Discovery 2- Use of Netconf/Yang 1- Automate the network setup 4- Turn on BGP-LS Core Access Domain C Enable inter Domains Traffic Engineering Access Domain B 3- Simplify MPLS transport with Segment routing Programmatic Approach BRKSPG Cisco and/or its affiliates. All rights reserved. Cisco Public 83

83 References Agile Carrier Ethernet Demonstration on Youtube - Segment Routing.net - Segment Routing Demo Friday - Cisco Programmability Yang blog - Tail-f netconf yang tutorials - BGP-LS linkedin blog: Netconf linkedin blog: BRKSPG Cisco and/or its affiliates. All rights reserved. Cisco Public 84

84 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 BRKSPG Cisco and/or its affiliates. All rights reserved. Cisco Public 85

85 Continue Your Education Demos in the Cisco campus Walk-in Self-Paced Labs Lunch & Learn Meet the Engineer 1:1 meetings Related sessions BRKSPG Cisco and/or its affiliates. All rights reserved. Cisco Public 86

86 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 14 th, :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

87 Thank you

88