1 Description
This instruction describes how to scale out 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 Scale Out a VNF
Prerequisites
- No documents are required.
- No tools are required.
- The following conditions must apply:
- The VNF is instantiated using the VNF-LCM.
- VNF-LCM is available using either Operations Support System for Radio and Core (OSS-RC) or Ericsson Network Manager (ENM).
- One of the following Virtual Infrastructure Managers
(VIMs) is used:
- OpenStack Mitaka or newer
- CEE R6 or newer
- 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 Uen.
- The version of the used VNF-LCM is 18.16 (the VNF Lifecycle Automation Framework (VNF-LAF) image is 4.9.15) or higher.
Steps
- In the VNF-LCM, click Start a Workflow, select Scale-Out 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, select
the VNF to be scaled out, specify the number of Virtual Machines (VMs)
to be added to the VNF, and then click Submit.
The VNF instance is scaled out, new PLs are added to the cluster.
- Note:
- If the EO and the VNF-LCM are in a mutually granting connection, the number of scaled PLs appears in the EO after a successful scale-out from the VNF-LCM.
- Do a SmallRestart:
Risk of system malfunction or traffic disturbance.
During the scaling, 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 Administration 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 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
