1 Description
This instruction describes how to terminate a Virtual 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.
2 Procedure
2.1 Terminate a VNF
Prerequisites
- The VNF is instantiated using the VNF-LCM.
- The following virtual and physical hardware and software
are required:
- 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.10. The VNF Lifecycle Automation Framework (VNF-LAF) image is 4.3.13 or higher.
- No documents are required.
- No tools are required.
- The following condition must apply:
- The VNF-LCM is available using either the Operations Support System for Radio and Core (OSS-RC) or the Ericsson Network Manager (ENM).
- 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.
Risk of system malfunction or traffic disturbance.
Do not execute a workflow instance on a VNF while another is in progress, as it can lead to unexpected behavior. If a new workflow procedure is needed, terminate the ongoing procedure before starting a new.
Steps
- In the VNF-LCM Workflows view, select Terminate 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 terminate.
- Select the termination type (Graceful or Forceful).
Termination options:
Graceful The Virtual Machines (VMs) in the cluster are gracefully locked and the VNF instance gradually stops accepting new calls and registration. The VNF terminates after the expiration of the graceful termination period. Forceful The VNF terminates immediately. All ongoing traffic is lost. This option must be confirmed on the next screen. Graceful termination timeout (sec) Defines after how many seconds the VNF terminates when graceful termination has been applied. Traffic is still ongoing until the VNF terminates. Defaults to -1, which means that no graceful termination period exists, that is, the VNF terminates only after all VMs stopped processing traffic. - Is the Graceful termination type selected?
Yes: Continue with the next step.
No: Proceed with Step 8.
- Specify the Graceful termination timeout (sec).
- Click Submit.
The VNF instance terminates. For graceful termination, the VNF instance stops processing traffic gracefully and then terminates.
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. 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


