1 Description
This instruction describes how to terminate 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 Terminate a VNF
Prerequisites
- No documents are required.
- No tools are required.
- The following condition must apply:
Steps
- In the VNF-LCM Workflows view, select Terminate VNF, and click Start a New Instance.
- In the Start a Workflow view, fill out the Instance Name field and, 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 VNF instance is gracefully locked (by setting the mtasFunctionAdministrativeState attribute to SHUTTING DOWN(2)), it gradually stops processing traffic. The VNF is terminated after the expiration of the graceful termination period, or even earlier, when all ongoing sessions have stopped on the node. Forceful The VNF terminates immediately. All ongoing traffic is lost. This option must be confirmed on the next screen, as it stops all traffic. 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.
- Note:
- If the EO and the VNF-LCM are in a mutually granting connection, the terminated instance disappears from the EO after a successful termination from the VNF-LCM if the instantiation was made from the EO.
Risk of system malfunction or traffic disturbance.
During the termination, 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
