#CLUS

Fast-track Network
migration using NSO

Sandeep Lohia – Sr. Solutions Architect

Giri Venugopal – Solutions Architect
BRKNMS-2301

#CLUS
Agenda
 Current challenges in Network Migration
 Network data migration scenarios
 Service Discovery
 Migration phases:
 Pre Migration Health Checks
 Service Migration
 Post Migration Health Checks
 Migration Report with KPI comparison
 Customer case study
 Business results & outcomes

#CLUS BRKNMS-2301 © 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public 3
Cisco Webex Teams
Questions?
Use Cisco Webex Teams to chat
with the speaker after the session

How
1 Find this session in the Cisco Live Mobile App
2 Click “Join the Discussion”
3 Install Webex Teams or go directly to the team space
4 Enter messages/questions in the team space

Webex Teams will be moderated cs.co/ciscolivebot#BRKNMS-2301

by the speaker until June 16, 2019.

#CLUS © 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public 4
Migration – An evergreen operation

Technology keeps
changing, which makes
“Migration” a constant…
Migration Challenges
Overall Time:
 Overall Time Taken for Service Migration
 Manual tasks take longer time

Risk & Credibility:

 Customer Confidence/ Satisfaction
 Network downtime

OpEx:
 Number of Maintenance windows
 Resources per Maintenance window

#CLUS BRKNMS-2301 © 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public 6
Migration Challenges Cont..
Assurance:
• Ensure services/circuits are restored.
• Strict compliance to KPI threshold limits
• Monitoring connectivity to peripheral devices.

Optimization & Scalability:

• Current process is not scalable
• Lack of best practices
• Human errors

#CLUS BRKNMS-2301 © 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public 7
Manual Migration and Monitoring Process

1 Migration MOP Source

to
Pre Migration Destination
activities

Migration execution
Migration Planning 2
Post Migration check
• Define migration
<show-cmds>
process
New
• Sequence
Migration Multiple peripheral
planning
Request 3 devices involved per
• Scheduling
migration
• Lab testing
• Execution
Multiple commands
planning (optional)
per device Other devices
4 For Plumbing
One or more ASR1k, 9K, 7K..
operators to monitor
each device

N/W Operators
#CLUS BRKNMS-2301 © 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public 8
MOP Transformation: Simplify and Save Time
Time-consuming, individual MOP --> High operations costs—cannot scale!

Plan It Design It Test Health Configure Health Is it Ready Rollback

It/MOP Check It Check

Automated Workflow

Engineers Free for other

Time Saving Multiple Gateway
duties

#CLUS BRKNMS-2301 © 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public 9
Migration
scenarios
Migration scenarios - Key Triggers

Service Migrate network services from source  target device.

Platform Old platform obsolete / EOL (Ex: Catalyst 2/3/4K  9K)

Infrastructure Physical device  Virtual Device (Transition to NFV)

Datacenter Intra-site Vs Inter-site migration (Site A Site B)

#CLUS BRKNMS-2301 © 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public 11
Migration – Overall steps (Workflow)
When source device exists When source device
in NSO doesn’t exists in NSO
Pre-migration health checks + KPI pre-check

Backup config & services from source

Onboard target device onto NSO (Optional)

Perform Service Discovery (Optional)

Restore backed-up config & service data on target

Post-migration health checks + KPI post-check

Compare & Generate Migration summary report

It all sounds familiar to what we do during a Kidney transplant.. Isn’t it????

#CLUS BRKNMS-2301 © 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public 12
Service Discovery – What?
 Technique used to discover existing
services while onboarding a
brownfield device into NSO.
 Discovery is performed by scanning
the device for unique config patterns
that constitute a specific “service”
 Discovered instances are synced into
NSO
 One-time activity performed in NSO
after onboarding is complete.

#CLUS BRKNMS-2301 © 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public 13
Service Discovery – Why?
 To make brownfield devices automation-ready

 Prep the device for migration activities

 Standardize device configs manually pushed over time.

 Reduce likelihood of human errors

 Single pane of glass for device management.

#CLUS BRKNMS-2301 © 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public 14
Service Discovery – How?

Extract (E) Identify & Extract config patterns

Transform them to NSO service instances

Transform (T) using a mapping logic

Load (L) Load discovered instances to NSO

Manage (M) Manage device using NSO

#CLUS BRKNMS-2301 © 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public 15
Ways to perform Service Discovery:
Multiple ways to do implement mapping logic
Option 1: XML / XSLT
 XPath transformations from device templates.
 Can be pushed directly onto NSO to create
service instances.
Option 2: Java / Python
 Transformation is written in Java / Python
using NAVU API.
 Mapping logic coupled with the service logic.

#CLUS BRKNMS-2301 © 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public 16
Migration Phases
Network / Service data migration - Phases

 Pre-health-checks  Migration
 KPI pre-checks Pre-Migration Configs
Check Migration

Service
Migration

 Migration report
 Post-health-checks Post-Migration Pre/Post KPI with KPI
Check comparison
 KPI post-checks comparison

#CLUS BRKNMS-2301 © 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public 18
Data migration – Phase 1(Pre-Migration checks)

Step 1: Check source device reachability

Step 2: If device onboarded in NSO already, skip Service Discovery

Step 3: If not, onboard device into NSO & perform service discovery 25%
Step 4: Backup configs & service instances that need to be
migrated.

Step 5: Run KPIs on source device & save KPI responses

#CLUS BRKNMS-2301 © 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public 19
Data migration – Phase 2(Service/Config Migration)

Step 1: Check if config & service instances were successfully backed up

Step 2: Check if target is reachable & onboarded on NSO already.

Step 3: If not onboarded, onboard the target device onto NSO 50%
Step 4: Restore configs & service instances on target platform

Step 5: Deploy migrated service instances

#CLUS BRKNMS-2301 © 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public 20
Data migration – Phase 3(Post-Migration checks)

Step 1: Check if migrated service are up & running on the target

Step 2: Run KPIs on target device & save post-check responses

75%
Step 3: Re-run KPI checks until exit-criteria is met

#CLUS BRKNMS-2301 © 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public 21
Data migration – Phase 4 (Migration report with KPI
comparison)

Step 1: Check if KPI data exists for both Pre & Post checks.

Step 2: Compare KPI pre-post data for threshold compliance

100%
Step 3: Create Migration Report with pre-post comparison for KPIs

Step 4: KPIs that are within threshold levels  Successful.

KPIs that are within threshold levels  Failed (with reason for failure)

#CLUS BRKNMS-2301 © 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public 22
Sample Migration Report

#CLUS BRKNMS-2301 © 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public 23
Customer Success
Story
Service Migration use-case:
ASR 9K Peripheral
Devices for Service
Plumbing

X ✓
X ✓
X ✓
X ✓
Migration

Source Device Dest. Device

X ✓
X ✓

ASR 1K
#CLUS BRKNMS-2301 © 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public 25
 Migration Tool: Key Features
• Monitoring of KPI values pre and post migration to ensure seamless
transition of services
• User defined KPI blueprint per platform
 KPI Show command
 Threshold Variance in % (for pre and post difference)
 Command re-run interval
 Max retry limit

• User can choose (enable/disable) KPIs per migration

• Generation of report at the end of migration
• Extensible framework to add KPIs and plug-in filtering logic

#CLUS BRKNMS-2301 © 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public 26
 Migration process
Pre-checks

Source
to
Cisco
Migrate and Post-checks Destination
Operator
Gather Pre KPIs NSO
Gather Post KPIs NSO
Manage
d
Pre Check Post
PostCheck
Check
Devices

KPIs KPIs
KPIs
Rerun (optional)
Post Other devices
For Plumbing
Check ASR1k, 9K, 7K..
Within
Threshold? NO
Yes Pre-check
Post-check
Success
#CLUS BRKNMS-2301 © 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public 27
Business
Outcomes
Business Outcomes
45 180 6
40 160
5
35 140
30 120 4
25 100
3
20 80
15 60 2
10 40
1
5 20
0 0 0
Overall Time in weeks N/W Downtime Hrs # of Resources

Manual Automation
Source: Tier One Service Provider in USA.

#CLUS BRKNMS-2301 © 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public 29
Migration Tool: Accomplishments
Significant time saving in service migration
Easy, quick and less error-prone migration
Reporting: Single pane of glass to monitor the migration activity
Multi-vendor support
Time savings due to parallel migration processes
Increase in # of device migrations per maintenance window
Customer OpEx savings
Better ROI for customer

#CLUS BRKNMS-2301 © 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public 30
Complete your Session ID: BRKNMS-2301
online session • Please complete your session survey
evaluation after each session. Your feedback
is very important.
• Complete a minimum of 4 session
surveys and the Overall Conference
survey (starting on Thursday) to
receive your Cisco Live water bottle.
• All surveys can be taken in the Cisco Live
Mobile App or by logging in to the Session
Catalog on ciscolive.cisco.com/us.
Cisco Live sessions will be available for viewing
on demand after the event at ciscolive.cisco.com.

#CLUS BRKNMS-2301 © 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public 31
Continue your education

Demos in the
Walk-in labs
Cisco campus

Meet the engineer

Related sessions
1:1 meetings

#CLUS BRKNMS-2301 © 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public 32
Questions?

#CLUS BRKNMS-2301 © 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public 33
Thank you

#CLUS
#CLUS