1 Description
This instruction describes how to instantiate a Virtual Network Function (VNF) in the VNF Lifecycle Management (VNF-LCM).
The Call Session Control Function (CSCF) workflow software package contains more files than are described in this instruction. These unmentioned files are only used in special deployment scenarios that are outside the scope of this instruction. Only use the files that are explicitly mentioned in the instruction.
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 CSCF VNF Lifecycle Management.
2 Procedure
2.1 Instantiate a VNF
Prerequisites
- The following virtual and physical hardware and software
are required:
- The VNF is onboarded on the VNF-LCM.
- VNF-LCM is available, using either Operations Support System for Radio and Core (OSS-RC) or Ericsson Network Manager (ENM).
- The VIM is configured in VNF-LCM:
The VIM configuration in VNF-LCM can be checked with the vnflcm vim list command. For more information on VIM configuration, see VNF Lifecycle Manager System Administrator Guide, 1543-APR 901 0578.
- No documents are required.
- No tools are required.
- The following condition must apply:
Steps
- In the VNF-LCM Workflows screen, select Instantiate VNF, and then click Start a New Instance.
- In the Start a Workflow view, fill out the Instance Name field, and then click Submit.
- Select the newly created workflow from the Instance Activity panel.
- In the Workflow Instance view:
- Add VNF name.
- Add VNF instance description.
- Select the VNF to instantiate.
- (Optional) Select the Add Network Element in ENM/OSS-RC check box to add the new VNF in the Network Management application.
- 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 field displays VNF releases available for VNF instantiation in the /vnflcm-ext/backups/workflows/vnfd/ directory.
- In the Select VIM view, select the VIM to be used, and then click Submit.
- In the Select Tenant view, select the tenant to be used, and then click Submit.
The following step is optional. If none of these parameters are needed, leave the fields blank.
- In the Select VDC view, select the Virtual Data Center (VDC) in which the new VNF is instantiated, and click Submit.
- In the Get Instance Configuration view,
select a VNF configuration to instantiate, and then click Submit.
- Note:
- The Select Configuration for the VNF instance field displays VNF configurations available for instantiation in the /vnflcmext/backups/workflows/vnfd/<VNFType>__<VNFVersion>/configurations folder.
The following step is optional. It is only required if the Add Network Element in ENM/OSS-RC check box was selected in Step 4.
- 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:
- To check the supported VNF version in ENM and OSS-RC, see the ENM and OSS-RC documentation respectively.
Risk of system malfunction or traffic disturbance.
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
- Increase the log level from INFO to DEBUG. For information on how to change log level, see VNF Lifecycle Manager System Administrator Guide, 1543-APR 901 0578.
- 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
- If the Workflow Log view reports Authentication failed, repair the Secure Shell (SSH) key between the VNF-LCM and the CSCF. For more information, see Section Check SSH Key for Authentication in CSCF Troubleshooting Guideline.
- 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.

Contents







