Contents

1   Description

This instruction describes how to terminate a Virtual Network Function (VNF) using Ericsson Orchestrator (EO).

2   Procedure

2.1   Terminate a VNF

Prerequisites

• The VNF is instantiated using the EO.
• In EO, the VIM zone, Virtual Data Center (VDC), and Signaling Route Test (SRT) are configured, the external Virtual Network Function Manager (VNFM) is registered. For more information on configuring EO, see System Administration Guide 1543-CNH 160 9180.
• No documents are required.
• No tools are required.

Steps

1. In EO, select the Virtual Application (VAPP) to terminate and click Delete.
2. On the Terminate VAPP form, provide termination options, and click Terminate.

   The following termination options are available:

   • Graceful

     The Virtual Machines (VMs) in the cluster are gracefully locked, the VNF instance gradually stops accepting new calls and registration. The VNF is terminated after the expiration of the graceful termination period.

   • Forceful

     The VNF is terminated immediately, all ongoing traffic is lost. This option must be confirmed on the next view.

   • Graceful termination time-out (sec)

     The graceful termination time-out value defines after how many seconds the VNF is terminated when graceful termination has been applied but there is still ongoing traffic. Default value: -1, meaning that there is no graceful termination period, that is, the VNF is terminated only after all VMs stopped processing traffic.

   Note:  

   Do not modify configuration data in the Configuration Parameters field.

   
   
3. Click Terminate.
   Result:
   The VMs in the cluster are terminated with the method selected in Step 2, the VNF instance stops processing traffic, and is terminated.

   Note:  

   If the EO and the VNF-LCM are in a mutually granting connection, the new instance disappears from the VNF-LCM database after a successful termination from the EO.

   
   

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 Administrator 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 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.
4. 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.