Contents

1   Description

This instruction describes how to instantiate a Virtualized Network Function (VNF) in the VNF Lifecycle Management (VNF-LCM).

The VNF-LCM procedures use workflow instances. The following figure shows an example of a workflow instance, where workflow progress can be tracked in the Workflow Diagram view. The boxes in the Workflow Diagram only represent the stages of the various procedures; operations are performed in the Task view.

For more information about the VNF-LCM, see MTAS VNF Lifecycle Management.

2   Procedure

2.1   Instantiate a VNF

Prerequisites

• No tools are required.
• The following condition must apply:
  • The Onboard procedure is completed. For more information, see Onboard VNF Package on VNF-LCM.

Steps

1. In the VNF-LCM Workflows view, select Instantiate VNF and then click Start a New Instance.

   

2. In the Start a Workflow view, fill out the Instance Name field and then click Submit.
3. Select the newly created workflow from the Instance Activity panel.
4. In the Workflow Instance view:
   1. Add VNF name.
   2. Add VNF instance description.
   3. Select the VNF to instantiate.
   4. (Optional) Select the Add Network Element in ENM/OSS-RC check box to add the new VNF in the network management application.
   5. Click Submit.

   

   Note:  

   The VNF name is also used as the Heat stack name. It is not recommended to add version information in this field, as the name is unchanged after VNF upgrades.

   The Select VNF descriptor Id drop-down list displays VNF releases available for VNF instantiation in the /vnflcm-ext/backups/workflows/vnfd/ directory.

   
   
5. In the Select VIM view, select the VIM to be used and then click Submit.

   

6. In the Select Tenant view, select the tenant to be used and then click Submit.

   

7. In the Get Instance Configuration view, choose Select Configuration for the VNF instance*, and click Submit.

   

   Note:  

   The Select Configuration for the VNF instance field displays VNF configurations available for instantiation in the /vnflcm-ext/current/vnf_package_repo/<VNF package>/configurations folder.

   
   

8. Set the VNF-related parameters for ENM and then click Submit.

   The VNF is instantiated, it starts handling traffic after all configuration data is provided.

   Note:  

   • If the instantiation fails, remove the VNF instance using the Terminate VNF workflow (FORCEFUL), see Terminate VNF Using VNF-LCM. If the VNF instance cannot be selected in the Terminate VNF workflow, then the VNF instance must be deleted manually from the Cloud environment.
   • If the EO and the VNF-LCM are in a mutually granting connection, the new instance appears in the EO after a successful instantiation from the VNF-LCM.

   
   

   

   Note:  

   To check the supported VNF version in ENM and OSS-RC, see ENM and OSS-RC documentation respectively.

   
   

During the instantiation, the optional user input Cancel LCM Hook is available. Do not click Submit. This is not supported in the current release.

2.2   Troubleshooting

If the workflow execution fails, inspect the relevant logs to identify the cause of the failure.

Steps

1. Increase the log level from INFO to DEBUG. For information on how to change log level, see VNF-Lifecycle Manager System Administration Guide, 1543-APR 901 0578.
2. Inspect the following logs to identify the cause of the failure:
   • Jboss Server log: /ericsson/3pp/jboss/standalone/log/server.log
   • System log: /var/log/messages
   • Workflow log: the Workflow Log view in the VNF-LCM
3. If a problem cannot be solved, consult the next level of maintenance support and provide the logs. Further actions are outside the scope of this instruction.