Switching VNF Monitoring Between Local MONA and D-MONA

This section describes the switchin of VNF monitoring from local MONA to a D-MONA monitoring deployed within the same VIM connector.

Prerequisites

Following are the prerequisites that you must complete before transfering VNF monitoring from local MONA to a D-MONA monitoring.

Procedure

Step 1

You must have ESC 5.0 and more.
Step 2

D-MONA must be deployed with 1:1 VIM mapping set to true.

For more information on the 1:1 deployment, see Deploying D-MONA section.
Step 3

VNF must be deployed and present in the same VIM connector similar to D-MONA.

Steps to Transfer Local MONA VNFs to D-MONA

Following are the steps to transfer local MONA VNFs to D-MONA:

Procedure

Step 1

Verify that the local MONA is monitoring the ESC with 2 VNFs.
Step 2

Verify that the D-MONA deployment with the 1:1 mapping is set to True within the same VIM (Vim Connector) and the ESC MONA is actively monitoring the D-MONA VM.

Step 3

Use the northbound API to send a request to unset the monitoring of the VNF-2. It stops the monitoring of VNF-2 by local MONA.

Step 4

Use the northbound API to send a request to set monitoring of the VNF-2, which starts monitoring the ESC backend server. With the presence of D-MONA with 1:1 mapping within the same VIM (Vim Connector), the monitoring for VNF-2 gets automatically assigned to D-MONA.

Steps to Transfer D-MONA to Local MONA VNFs

Following are the steps to transfer D-MONA to local MONA VNFs:

Procedure

Step 1

Use the northbound API, to send a request to unset the monitoring of the VNF-2. It stops D-MONA monitoring of VNF-2.
Step 2

Use the northbound API, to send a request to undeploy the D-MONA virtual machine. It removes the D-MONA from ESC.
Step 3

Use the northbound API, to send a request to set monitoring of the VNF-2, which starts monitoring the ESC backend server. With the absence of a D-MONA within the same VIM (Vim Connector) the monitoring function for VNF-2 is automatically re-assigned to Local MONA.