Girisha BukanakereCisco CX - Banglore

17th June 2020

Bharti Airtel Automation ProjectOn-Demand Reconciliation

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

There is only one way to eat an elephant: a bite at a time.

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

AgendaTruth has no Agenda

• Challenges

• Adventure

• ODR Framework

• ODR Workflow

• Bharti Success Story

• Cisco Success Story

• Limitations

• Q & A

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

ChallengesDon’t limit your challenges

• Huge network – Over 5 lakhs L3/L2 network

services. PAN India coverage.

• Built over 20 years, heterogeneous network

• Large variations – Insightful journey to Airtel and

Cisco CX.

• Critical operations team touches real network to

resolve issues quickly.

• Network deviation fixes is continuous activity.

• NSO is not RDBMS, its config DB. Limitations are

bounded.

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

AdventureThe joy of discovery

• Couple of Discovery &

Reconciliation runs over L3 network

services

• Deviations reduced, but not cleared

all : 50%, 41% and 29%

• How long NSO takes to rerun

complete network : 6 full days for L3

• 144 hours – OMG ??? - Average

1.7 seconds per service only ☺

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

Customer asked - Go incremental. Cisco CX propose On-Demand

reconciliation

On-Demand Reconciliation Framework

BPA Core

NSO - CFS

NSO - RFS

External DB - API

……………….

Discovery request

DiscoveryResults

Query periodically

Sync-From on-demand basis

Discovery response

Circuit details request

Circuit details response

Customer OSS/BSS

BPA UI

CHANGE/DISCONNECT/D&R request and response

On-Demand Reconciliation workflowBPA NSO CFS External DB NSO RFS Devices

Querying device data in a periodic manner

OSS/BSS

CHANGE/DISCONNECTOrder from OSS for Circuit’s

BPA Circuit-Wise device details query from Config DB

BPA Process the External DB results and take decision based on data. Deviations will throw back to OSS/BSSIf deviation, returns to

OSS/BSS

Delete the existing circuit in NSO only.

Call ODR for circuit-id Discovery request for latest circuit information from network

Sync the devices

Sync the device

Returns latest discovery information or network deviation

Reconcile circuit

If deviation, returns to OSS/BSS via BPA

Apply CHANGE/DISCONNECT on latest Circuit Apply the change via NSO to router

Returns results or error

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

Bharti Success Story

• Time flexibility to adopt network

deviations. As business needed –

Big relief

• New service variation adoptions &

logical fixes – Flexibility

• Change should go via NSO/BPA

automation – Streamlining takes

some time.

• UAT from most happening cases to

least occurring cases.

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

Cisco Success Story

• Its all automated. minimal support.

• Any recon bugs – Don’t worry.

Always latest recon logic applied

before CHANGE.

• Other Use-cases delivery timeline

doesn’t change – No pressure

• Less chance of outages due to

wrong config push to devices -☺

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

LimitationsIn Imagination, there is no limit.

• NSO is not real-time service inventory

system.

• Increases CHANGE/DISCONNECT

management processing time.

• Corner cases : Multiple operations

within 2 hours window - Not possible.

• Additional relational DB required &

Querying devices everyday impact little

device performance.

• Deviation fixes or Reconciliation code

changes becomes continuous.