Labspg 2442

LABSPG-2442
NSO: Network Service

Orchestrator Hands-on Lab
(Tail-f NSO)
Håkan Niska (Solutions Architect) hniska@cisco.com

Jay Kurji (Solutions Architect) kjay@cisco.com
Cisco Spark
Questions?
Use Cisco Spark to communicate
with the speaker after the session
How
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
cs.co/ciscolivebot#LABSPG-2442
© 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public
Agenda
• Overview of Network Service Orchestrator (NSO)

• NSO Demo
• Introduction to the lab
• Task 1: Installing NSO
• Task 2: NSO Device Manager
• Task 3: NSO Service Manager
• Conclusion
Agenda
• 14.00 – 16.00 Part 1

• 16.00 – 16.15 Break
• 16.15 – 18.00 Part 2
LAB GUIDE
• Go to http://www.ciscolive.com/global/
• Choose Learn online -> On demand library
• Search for LABSPG-2442
LABSPG-2442 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 6
Overview of NSO
A two minute introduction to NETCONF/YANG
NETCONF
Network management protocol specifically designed to support service activation and provisioning.
• Encrypted, efficient transport

• Extensible
• Transactional
• Network-wide
A two minute introduction to NETCONF/YANG
YANG
Text based data modeling language designed for use with NETCONF.
• Operator friendly
• Precise
• Extensible
• Human readable
NSO architecture
Applications Engineers
REST, RESTConf, NETCONF, Java, Python, Erlang, CLI, Web UI

Service
Model
Service Manager
Device Manager Device

Model
Network Element Drivers (NEDs)
NETCONF, REST, SNMP, CLI, etc
• VNFM
• Controller Apps
• EMS and NMS
Physical Networks Virtual Networks Network Apps
NSO for Network Engineers – User Interfaces
Auto-rendered Web UI with
powerful extensibility features
NSO for Network Engineers – User Interfaces
Cisco or Juniper-style CLI for network-
wide configuration changes
NSO Demo
Introduction to the NSO Lab
Introduction to the NSO Lab: Connecting to POD
• You have been assigned a POD consisting of two servers
• Connect to your POD using the AnyConnect credentials in your sheet
• Connect to environment
• Remote desktop to the PC Workstation
• SSH directly to the NSO server
PC Workstation NSO Server. Access via SSH

IP address: 198.18.133.253 IP address: 198.18.134.4
Username/Password: Administrator / Username/Password: cisco/cisco
C1sco12345
Task 1: Installing NSO
NSO requirements
• System Requirements
• Check the distribution filename:
• nso-4.2.linux.x86_64.installer.bin
• nso-4.2.darwin.x86_64.installer.bin
• Check your OS version:

• Linux distributions
• OS X
• Check the CPU architecture:

• x86_64 – 64-bit Intel x86 architecture
• Java version (JDK 1.6 or higher)

• Python 2.7 or 3.3
Installing Cisco NSO is easy
• Obtain distribution file:
• nso-x.x.linux.x86_64.installer.bin
• It contains:
• NSO, examples, documentation
• NETSIM Network Simulator
• Run the installation (system or local installation)

$./nso-x.x.linux.x86_64.installer.bin nso/4.2
INFO Using temporary directory /var/… to stage NSO installation bundle
INFO Unpacked NSO-4.0.3 in /home/cisco/nso/4.2
INFO Found and unpacked corresponding DOCUMENTATION_PACKAGE
INFO Found and unpacked corresponding EXAMPLE_PACKAGE
INFO Generating default SSH hostkey (this may take some time)
INFO SSH hostkey generated
INFO Environment set-up generated in /home/cisco/nso/nsorc
INFO NSO installation script finished
INFO Found and unpacked corresponding NETSIM_PACKAGE
INFO NSO installation complete
Setup an NSO Project Runtime Directory
• First make sure you stand in your home directory
$ cd
• Make sure binaries are added to your PATH:

$ source nso/4.2/ncsrc
• Run the ncs-setup script:

$ ncs-setup --dest nso-lab
• Creates a database directory ./ncs-cdb

• Creates a log directory ./log
• Creates an empty packages directory ./packages
• Creates a default ncs.conf
Starting Cisco NSO
• Move to nso-lab directory
$ cd nso-lab
• Start the NSO daemon:

$ ncs EXIT CLI when done:
> exit
• Check if the daemon is running:
$ ncs --status
• Start the CLI (Cisco XR style):

$ ncs_cli -J -u admin
• Start the CLI (Juniper style):

$ ncs_cli -C -u admin
NSO Directories
Two directory types:
Installation Directory
~/ nso/ 4.1/
Project Directory
4.2/ bin/
lib/
doc/
examples.ncs/ web-server/ ncs-cdb/
ncs.conf
datacenter/ ncs-cdb/
ncs.conf
nso-lab/ nso-cdb/
nso.conf
Introduction to the NSO Lab
NSO web GUI
• In Windows server, open Chrome browser direct link to NSO “Web GUI”
• Use admin/admin as credentials
NSO Packages
Using Packages
• Make sure your package is in the right place

• The./packages directory
• Don’t store anything else in the packages directory!
• Don’t keep “old” packages in the packages directory!
Using Existing Packages
• Existing packages:
• NEDS ($NCS_DIR/packages/neds)
• Services ($NCS_DIR/packages/services)
• Tools ($NCS_DIR/packages/tools)
• Copy (or softlink) packages from the NSO installation

into the NSO project directory:
cd nso-lab
cp -r $NCS_DIR/packages/neds/cisco-ios packages/
cp -r $NCS_DIR/packages/neds/dell-ftos packages/
Reloading Packages
• Check if all the required packages are loaded using show packages command
• Package reload can be forced using request packages reload command
• Package reload can be forced with starting NSO using —with-package-reload flag
$ ncs_cli –C –u admin
admin@ncs# packages reload
admin@ncs# show packages package package-version
PACKAGE NAME VERSION
----------------------
cisco-ios 3.0
dell-ftos 3.0.1
admin@ncs# exit
Using Netsim
Netsim Overview
 ncs-netsim is a network devices
simulation tool
 Used to test NSO with simulated devices
 Uses NED device packages
 A NED package contains netsim directory Netsim simulated
 Represents device configuration and CLI devices (ConfD)
 The same YANG for models are used for
simulated and real devices
Physical or virtual non-

simulated devices
Starting Simulated Devices
• Below example creates 3 Cisco IOS devices and 2 dell force10 devices
$ ncs-netsim create-network packages/cisco-ios 3 c
$ ncs-netsim add-to-network packages/dell-ftos 2 dell
• Start the netsims inside the project folder

$ ncs-netsim start
DEVICE c0 OK STARTED
DEVICE c1 OK STARTED
...
Access Simulated Devices
• You can run the CLI towards the simulated devices
$ ncs-netsim cli-i c1
admin connected from 127.0.0.1 using console *
c1> enable
c1# show running-config
class-map m
match mpls experimental topmost 1
match packet length max 255
match packet length min 2
match qos-group 1
Task 2: NSO Device Manager
Device Manager
• Is the heart of NSO
• NSO keeps a master copy of configuration in CDB
• Network element drivers (NED) supports different protocols:
• NETCONF
Master Copy of
• SNMP
Configurations
• CLI
• Generic NED (Java code)
Device Manager
Network Element Driver
Load netsim devices in NSO
• First we export the NETSIM devices connection data:
$ ncs-netsim ncs-xml-init > devices.xml
• Lets go into NSO and load the devices file
$ ncs_cli –C -u admin
# configure terminal
ncs(config)# load merge devices.xml
ncs(config)# commit
ncs(config)# exit
NSO CLI
• In Operational mode, the CLI displays operational data stored in CDB (or live
data from the devices). In Configuration mode, the CLI displays network
# configuration data
operational mode CLIstored in CDB > operational mode CLI
(configure)# configuration mode (Cisco) % configuration mode (Juniper)
Operational Mode Configuration Mode

ncs# show devices device ncs# configure
devices device c0
... ncs(config)# show full-configuration
alarm-summary indeterminates 0 devices device c0
alarm-summary criticals 0
alarm-summary majors 0 devices device c0
... address 127.0.0.1
devices device www0 port 10022
... ssh host-key ssh-dss
…
Device Configuration Management
Synchronizing from Device
• Device Configurations in NSO and actual Device Configuration should match
• After initial device discovery or import, it makes sense to synchronize
configurations from devices
sync-to
ncs# devices sync-from sync-from
check-sync
sync-result { compare-config
device c0
result true
}
Synchronizing to Device
• When a device has been configured out of band
• Clears up rogue configuration
• “dry-run” option available to check changes sync-to
sync-from
ncs# devices device c0 sync-to check-sync
compare-config
result true
Change device
configuration over CLI.
Check Sync
• Check if a device has been configured out of band
ncs# devices check-sync
sync-result {
device c0
result in-sync
}
• Check if a subset of managed devices has been configured out of band

ncs# devices device c0..3 check-sync
devices device c0 check-sync
result in-sync
result in-sync
Configuring Devices
• Configuration change happens after final commit statement
ncs# config
Entering configuration mode private
[ok][2010-04-14 14:28:33]
[edit]
ncs(config)# devices device c0 config ios:interface GigabitEthernet 0/1 ip address 10.10.10.1
255.255.255.0
[ok][2010-04-14 14:28:38]
[edit]
admin@ncs(config-if)# devices device c1 config ios:interface GigabitEthernet 0/2 ip address
10.10.10.20 255.255.255.0
[ok][2010-04-14 14:28:51]
[edit]
Displaying Configuration
• Display only new parts of configuration:
ncs(config)# top
ncs(config)# show configuration devices device c0
devices device c0
config
ios:interface GigabitEthernet0/1
• Display full configuration

ncs(config)# show full-configuration devices device c0
devices device c0
address 127.0.0.1
port 12023
ssh host-key ssh-dss
Commit changes
• Dry-run changes
ncs(config)# commit dry-run
----
ncs(config)# commit dry-run outformat native
----
• Commit to devices
ncs(config)# commit
• Exit
ncs(config)# exit
admin@ncs# exit
cisco@NCS:~/nso-lab$
Rollbacks
• Every transaction has a corresponding rollback file:
$ ls logs/rollback*
$ more logs/rollback10001
• Or NSO CLI:
> file show logs/rollback<TAB>
ncs(config)# file show logs/rollback<TAB>
Load rollback
ncs(config)# rollback configuration <TAB>
Possible completions:
0 - 2011-09-23 09:19:43 by admin via cli
1 - 2011-09-23 09:15:38 by admin via cli
2 - 2011-09-23 09:13:35 by admin via cli
3 - 2011-09-23 08:55:31 by admin via cli
Rollbacks – Examples
• Rollback with the highest number is the most recent rollback file
• Rollback X rolls back all transactions up to that number:

ncs_cli -C -u admin
admin@ncs# config
ncs(config)# rollback configuration 10001
ncs(config)# rollback selective 10084
• Rollback one single transaction:
Rollbacks – Examples
• Rollback dhcp changes on asr0 up to transaction 10080:
ncs(config)# rollback 10080 devices device asr0 config dhcp
• Rollback dhcp changes on asr0 from rollback 10078:
ncs(config)# rollback selective 10079 devices device asr0 config dhcp
Comparing Configuration
• Compare out-of-sync device configuration
ncs(config)# devices device c0 check-sync
result out-of-sync
info got: 290fa2b49608df9975c9912e4306110 expected: ef3bbd344ef94b3fecec5cb93ac7458c
ncs(config)# devices device c0 compare-config

diff
devices {
device c0 {
config {
ios:snmp-server {
+ community foobar {
+ RW;
+ }
}
}
...
Templates and Groups
Device groups
• Create a group and add devices
admin@ncs(config)# devices device-group C device-name c0
admin@ncs(config-device-group-C)# device-name c1
admin@ncs(config-device-group-C)# device-name c2
admin@ncs(config-device-group-C)# device-name dell0
admin@ncs(config-device-group-C)# top
admin@ncs(config)# show configuration
devices device-group C
device-name [ c0 c1 c2 dell0 ]
Templates
• Used to apply snippets of configuration
Create template:
ncs(config)# devices template snmp-settings config ios:snmp-server host 192.168.216.23 community-
string secret
ncs(config)# devices template snmp-settings config ios:snmp-server location Stockholm
ncs(config)# top
ncs(config)# show configuration
ncs(config)# commit
Apply to new or existing device:

ncs(config)# devices device c0 apply-template template-name snmp-settings
What is the diff?
ncs(config)# show configuration

ncs(config)# commit
Task 3: NSO Service Manager
YANG Intro
Basic YANG Statements
YANG Programming Equivalent Description
Leaf Variable Contains a single value of a specific type
Leaf-List Array Contains a list of values of the same type
Container Record Contains a single structure containing zero or more

values or other statements (hierarchy)
List Array of Records Contains a list of zero or more sets of values and other
statements (hierarchy)
Leafref Pointer Contains a link to another statement elsewhere in the file
YANG Supports a Number of Data Types
Built-in Types Derived Types
Name Description typedef my-base-int32-type {
type int32 {
int8/16/32/64 Integer range "1..4 | 10..20";
}
uint8/16/32/64 Unsigned integer }
decimal64 Non-integer
typedef derived-int32 {
string Unicode string type my-base-int32-type {
enumeration Set of alternatives range "11..max";
}
boolean True or false }
bits Boolean array typedef string255 {
binary Binary BLOB type string {
length "1..255";
leafref Reference }
}
identityref Unique identity
empty No value, void typedef derived-str {
type string255 {
union Choice of member types length "11 | 42..max";
pattern "[0-9a-fA-F]*";
instance-identifier References a data tree node }
}
© 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 53
Leaf Attributes
Attribute Description
Whether this leaf is a configurable value ("true") or operational
config
value ("false"). Inherited from parent container if not specified
default Specifies default value for this leaf. Implies that leaf is optional
mandatory Whether the leaf is mandatory ("true") or optional ("false")
must XPath constraint that will be enforced for this leaf
type The data type (and range etc) of this leaf
when Conditional leaf, only present if XPath expression is true
description Human readable definition and help text for this leaf
reference Human readable reference to some other element or spec
units Human readable unit specification (e.g. Hz, MB/s, ℉)
status Whether this leaf is "current", "deprecated" or "obsolete"
Service Design
Creating a Service Package
Create a Service Skeleton
1. Create a package skeleton
1.
Service Template Service Model
2. Use the Cisco NSO CLI to Skeleton File (XML) Skeleton File (YANG)
configure a sample service
Configure Sample Service
3. Create the service template using Cisco NSO CLI
Create Service Template

4. Create the service model in YANG (XML)
5. Compile and deploy the package Create Service Model
(YANG)

(XML) (YANG)
Create Service Model

(YANG)
Create a package skeleton
• $ cd
• $ cd nso-lab
• $ cd packages
• $ ncs-make-package --service-skeleton template trunk
• $ ls trunk/
• load-dir
• package-meta-data.xml
• src
• templates
• test
• Create a package skeleton
• Use the Cisco NSO CLI to Skeleton File (XML) Skeleton File (YANG)
using Cisco NSO CLI
2.
• Create the service template
• Create the service model in YANG (XML)
• Compile and deploy the package Create Service Model
(YANG)

(XML) (YANG)

(YANG)
Configure the Service via NSO
• admin@ncs(config)# devices device dell0 config force10:interface Vlan 10

tagged GigabitEthernet0/11
• admin@ncs(config)# devices device c0 config ios:interface GigabitEthernet 0/23
switchport mode trunk
• admin@ncs(config)# devices device c0 config ios:interface GigabitEthernet 0/23
switchport trunk allowed vlan 11
• admin@ncs(config)# commit dry-run outformat native
• admin@ncs(config)# commit dry-run outformat xml
• admin@ncs(config)# commit
• Create the service template using Cisco NSO CLI

• Create the service model in YANG 3. (XML)
(YANG)
Service Service Model

Template (XML) (YANG)

(YANG)
XML Template
• admin@ncs(config)# show full-configuration devices device dell0 config
force10:interface Vlan | display xml
• admin@ncs(config)# show full-configuration devices device c0 config
ios:interface GigabitEthernet 0/23 | display xml
• Same output as the commit dry run in the step before!
LABSPG-2442 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public

(YANG) 4.
(XML) (YANG)

(YANG)
Create the Yang Model
list endpoint {
key device;
leaf device {
type leafref {
path ”/ncs:devices/ncs:device/ncs:name”;
}
}
leaf interface {
type string;
}
}
leaf vlan {
type uint16;
}

(YANG)

(XML) (YANG)
Compile & Deploy the

5. Service
Compile and reload the package
• $ cd packages/trunk/src
• $ make
• $ ncs_cli -C -u admin
• admin@ncs # packages reload
Create a service instance
• $ ncs_cli -C -u admin
• admin@ncs # config
• admin@ncs(config)# services trunk myservice endpoint c0 interface 0/2
admin@ncs(config-endpoint-c0)# endpoint dell0 interface GigabitEthernet0/12
• admin@ncs(config-endpoint-dell0)# vlan 12
• admin@ncs(config)# top
• admin@ncs(config)# show full-configuration services trunk
• admin@ncs(config)# commit dry-run outformat native
• admin@ncs(config)# commit
Summary
• Service design goal is simplicity for the operator :
»Minimum set of parameters for the service (optimization)
»Strict enforcement of parameters to minimize human error
(standardization)
»Thorough testing of service configuration and all possible service options
to ensure robustness of the solution
• NSO and YANG provide modularity and flexibility for service designers
Conclusion
Cisco Spark
Questions?
Use Cisco Spark to communicate
with the speaker after the session
How
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
cs.co/ciscolivebot#LABSPG-2442
• Please complete your Online Complete Your Online
Session Evaluations after each
session
Session Evaluation
• Complete 4 Session Evaluations
& the Overall Conference
Evaluation (available from
Thursday) to receive your Cisco
Live T-shirt
• All surveys can be completed via
the Cisco Live Mobile App or the
Communication Stations
Don’t forget: Cisco Live sessions will be available
for viewing on-demand after the event at
www.ciscolive.com/global/on-demand-library/.
Cisco Automation and Orchestration at Cisco Live 2018
• Service Provider demos at World of Solutions:
• Carrier-Class Cisco NFV
• Multi-Domain Orchestration
• Multi-Layer and Multi-vendor Optical
• Segment Routing
• Managed SD-WAN
• 5G Enterprise Network Slicing
• Other Demos at Cisco live using our Automation and
Orchestration products:
• IoT/Fog computing demos power by NSO/ESC
• NSO booth in the Technical Solution Clinic at the Hub
• Partners Booths with NSO demos:
• LiveAction
• NIL
NSO DevNet – Key Highlights
The one place to use for sharing, finding and collaborating on NSO public
knowledge
Light start Constant Large Cisco Got a Easy to Code

through news and searchable customers, question, share and sharing
DevNet updates to content partners ask! We will find public through
content help you pool and help ensure content public
page and keep up to employees a fast GitHub
Learning- date all have response
Labs access
Reach it here: www.cisco.com/go/nsodevnet

Continue Your Education
• Demos in the Cisco campus
• Walk-in Self-Paced Labs
• Tech Circle
• Meet the Engineer 1:1 meetings
• Related sessions
Thank you

Labspg 2442

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Labspg 2442

Uploaded by

Copyright:

Available Formats

LABSPG-2442

NSO: Network Service

Håkan Niska (Solutions Architect) hniska@cisco.com

• Overview of Network Service Orchestrator (NSO)

• 14.00 – 16.00 Part 1

• Encrypted, efficient transport

REST, RESTConf, NETCONF, Java, Python, Erlang, CLI, Web UI

Device Manager Device

Network Element Drivers (NEDs)

NETCONF, REST, SNMP, CLI, etc

Physical Networks Virtual Networks Network Apps

PC Workstation NSO Server. Access via SSH

• Check your OS version:

• Check the CPU architecture:

• Java version (JDK 1.6 or higher)

• Run the installation (system or local installation)

• Make sure binaries are added to your PATH:

• Run the ncs-setup script:

• Creates a database directory ./ncs-cdb

• Start the NSO daemon:

• Start the CLI (Cisco XR style):

• Start the CLI (Juniper style):

• Make sure your package is in the right place

• Copy (or softlink) packages from the NSO installation

Physical or virtual non-

$ ncs-netsim add-to-network packages/dell-ftos 2 dell

• Start the netsims inside the project folder

admin connected from 127.0.0.1 using console *

c1# show running-config

match mpls experimental topmost 1

match packet length max 255

match packet length min 2

• Lets go into NSO and load the devices file

ncs(config)# load merge devices.xml

(configure)# configuration mode (Cisco) % configuration mode (Juniper)

Operational Mode Configuration Mode

• Check if a subset of managed devices has been configured out of band

• Display full configuration

• Rollback X rolls back all transactions up to that number:

ncs(config)# rollback selective 10084

• Rollback one single transaction:

• Rollback dhcp changes on asr0 up to transaction 10080:

ncs(config)# rollback 10080 devices device asr0 config dhcp

• Rollback dhcp changes on asr0 from rollback 10078:

ncs(config)# rollback selective 10079 devices device asr0 config dhcp

ncs(config)# devices device c0 compare-config

Apply to new or existing device:

What is the diff?

ncs(config)# show configuration

Leaf-List Array Contains a list of values of the same type

Container Record Contains a single structure containing zero or more

Leafref Pointer Contains a link to another statement elsewhere in the file

Create Service Template

Service Template Service Model

Create Service Model

Service Template Service Model

Create Service Model

• admin@ncs(config)# devices device dell0 config force10:interface Vlan 10

Create Service Template

Service Service Model

Create Service Model

• Same output as the commit dry run in the step before!

Create Service Template