Interoperating with CiscoTailf NSO Leveraging the NSO Interop

Interoperating with Cisco/Tail-f NSO Leveraging the NSO Interop Lab

Agenda • NSO Overview • NSO NEDs • Interoperating with NSO • The NSO Interop Lab © 2014 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 2

NSO Overview

NSO Overview Applications Engineers REST, NETCONF, Java, Python, Erlang, CLI, Web UI Service Model Service Manager Device Model Network Element Drivers (NEDs) • Real-time, multi-vendor Network Service Orchestrator (NSO) • NSO is a Platform Framework, customized through: o o NETCONF, REST, SNMP, CLI, etc • VNFM • Controller Apps • EMS and NMS Physical Networks Virtual Networks • Use case – the ‘service’ Specific devices deployed Northbound agents VNFs, VNF-M, VIM “Model-driven” approach Network Apps © 2014 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 4

NSO – Applications The end game is all about applications Applications NSO’s customer value: to make it easy to write network automation applications Applications • Requires transactional, model driven, real-time, network wide, multi-vendor, cross domain, physical/virtual agnostic API Applications interact with the service manager or device manager – and each other Applications API NSO Network Services Orchestrator Network Operating System © 2014 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 5

NSO – Device Manager • Provides applications with a transactional, model-driven read-write database view of the network • Transactional API: offloads error handling from applications Applications • Model-driven: add new device types at run -time Device API • Database two-way sync with devices • Templates, device groups, dry-run, rollbacks, policies, validation, … Network Element Drivers © 2014 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 6

NSO – Service Manager • • Service Applications support use cases that involve many devices; a mapping from high-level abstract to concrete device level configuration Stacked Service (Orchestration) applications support use cases that involve many services; a mapping from high-level abstract to concrete service level configuration E. g. an L 3 VPN stacked service might use an ELine service, which might use three different Network Element Drivers Orchestration Apps Service API gold Service Apps Device API Network Element Drivers © 2014 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 7

NSO NEDs, Network Element Drivers

NSO – Network Element Drivers (NEDs) Service Model Service Manager Device Model Network Element Drivers (NEDs) NETCONF Protocol Mapping NEDs SNMP Other Device Model Java Code Silverpeak VXOA Citrix Netscaler Dell FTOS Cisco IOS-XR Juniper Junos Downloaded Device Model CLI Protocol Unaware Applications Device Model So if the devices all look the same to applications, what’s the point developing a new NETCONF/YANG interface? Java Code © 2014 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 9

NSO – NED Types & Development Cost NETCONF CLI Other • NETCONF/YANG compliant devices • “Cisco-like” CLI devices • “Odd” CLI, REST, SOAP, Corba, TL 1. . . • YANG downloaded from device • Hand written YANG with annotations • Hand written YANG • No code required • Code to log in, map requests to RPC calls, sequence calls, parse responses • Code to log in, recognize prompts, error messages, parse state data Junos: 0 loc/leaf (0 loc / 200, 000 leafs) IOS: 0. 85 loc/leaf (4700 loc / 5500 leafs) NS: 4. 3 loc/leaf (3900 loc / 900 leafs) IOS-XR: 0 loc/leaf (0 loc / 24, 000 leafs) FTOS: 3. 4 loc/leaf (1200 loc / 350 leafs) VXOA: 7. 6 loc/leaf (1900 loc / 250 leafs) © 2014 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 10

NSO – NED Types & Development Cost • • NSO solves the proprietary CLI/API problem, but in the grand scheme, it’s a band-aid • Continual enhancements to handle newly discovered device quirks • Requires development and maintenance of 100 s of NEDs • Ultimately need a standards-based solution… Broad industry adoption of NETCONF/YANG is the end game • Standards-based, interoperable, transactional, rich management capabilities • NED can be auto-generated from the device yang model • Drives the Adapter Tax closer to zero © 2014 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 11

Interoperating with NSO

Interoperability Goal 1: Automated turn-up admin@ncs(config)# devices device my-new-device admin@ncs(config)# address 123. 45. 67. 88 admin@ncs(config)# device-type netconf admin@ncs(config)# ping … (device responds). . . admin@ncs(config)# commit Commit complete. admin@ncs(config)# download-build-install-netconf-ned … (working). . . admin@ncs(config)# sync-from This is real! sync-result { As far as we know, the device my-new-device world record to complete all result true this is just under 120 s } © 2014 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 13

Interoperability Goal 2: Service Automation • Much in NETCONF/YANG is optional; capabilities, RFCs • NSO cannot work with a basic, minimal NETCONF/YANG implementation (would provide no value over SNMP) • To support Service Automation we need device support for the Service Automation Criteria 1. Transactional NETCONF 2. Consistent edit-config 3. Validation without activation 4. Confirmed-commit 5. NETCONF over SSH 6. Defaults Handling 7. Standard Models 8. Model Discovery & Events 9. YANG 10. Backwards Compatibility © 2014 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 14

The NSO Interop Lab NETCONF/YANG industrialization

NSO Interop Lab – Background Created out of the need to serve joint customers well • Many customers see that NETCONF / YANG is the way of the future • … but only when implementations (client and server side) work perfectly together • Interop testing is required to make + prove things work properly At the same time, Cisco and Cisco partners may not be able to share code, product plans and lab access. © 2014 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 16

Internet Cisco d. Cloud instance NETCONF NED Partner CPE router for SSH + SFTP tunnel Partner Lab NSO Pioneer • Cisco provides access to NSO, without giving NSO installation to partner • Access to tools & experts • Partner gets access to NSO, without showing products in development to Cisco • Install & test NETCONF NED © 2014 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 17

NSO Interop Lab – What you need to bring • In order to set up the tunnel between d. Cloud and your lab, a Cisco 891 F CPE router (~$500 on Amazon/ebay) Configuration provided by Cisco. • No money, at least not in the near term This is currently a free service for partner organizations, some time in the future we may add a low fee to cover some of our costs. • Signed disclosure agreement We would like to have the right to publish names of products that have successfully passed certain levels of interoperability testing. © 2014 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 18

NSO Interop Lab – What’s Included • Private NSO instance on d. Cloud • Configuration for Cisco 891 F CPE router • SFTP and direct device upload of YANG modules • NSO NED build + test tools • Mail access to NSO, NETCONF, YANG experts © 2014 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 19

NSO Interop Lab – Participation To participate • Let us know by mail that you would like to participate • Provide contact names and information for your team • Provide product names of your NETCONF/YANG devices • Provide serial number of CPE router • Signed disclosure agreement (which we provide) © 2014 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 20

Interop testing with NSO – Work Stream 1. Connect to NSO Interop Lab 6. Execute basic operations; show, configure, run actions, receive notifications 2. Download YANG modules to NSO 3. Check dependencies, disable dangling modules 7. Gather test configurations for customer use cases 4. Compile, debug any issues; correct or disable modules 8. Test transactionality using above test data 5. Install NED in NSO, reload packages, sync-from Great work! Now NSO network automation application development can begin! © 2014 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 21

Welcome on board!