Cisco Cisco Virtual Managed Services 1.02 Troubleshooting Guide

2. vMS Architecture

18

2.4 vMS Call Flows

As  the  previous  section  explained,  the  vMS  solution  consists  of  many  orchestration  components  that
communicate with each other using different protocols. Detailed communication flows between components
will be explained to show how a successful vMS solution operates.

The subsections below explain:

•

vMS Initialization Call Flows

•

vMS Service Chain-related Call Flows: call flows that describe communication between the vMS

solution components related to operations over Service Chains (such as adding/deleting, upgrading
and downgrading of a Service Chain, and modification of existing Service Chain settings)

•

vMS CPE Call Flows: describes call flows of the process bringing (on-boarding) a new CPE to the

existing Service Chain, deleting / removing (off-boarding) a CPE from the existing Service Chain, and
replacing CPE devices.

Call Flows - Initialization Flows

ESC Registration Flow

When  the  vMS  solution  is  deployed  for  the  first  time,  the  ESC  orchestration  component  needs  to  be
registered and appropriate images have to be registered in OpenStack.

Please  note  that  the  ESC  registration  process  happens  only  once,  and  this  section  describes  it  in  order  to
have a complete overview of the Call Flows.

A detailed call flow of ESC registration is shown in Figure 2.4

.

1. NSO starts registration of Tenants for each Provider configured:

•

NSO sends Create Tenant Request to ESC

•

ESC forwards Create Tenant Request to OpenStack

•

OpenStack responds with OK upon Tenant creation

•

ESC sends Notification: Create Tenant Success message back to NSO.

At this point, Tenants are created successfully.

2. Service Registration is initiated for each VNF type supported by the solution:

•

ESC downloads VNF image from NSO via HTTPS