Contents

1   Description

This instruction describes how to scale in 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 In a VNF

Prerequisites

• No tools are required.
• The following conditions must apply:
  • The VNF is instantiated using the VNF-LCM.
  • The system has sufficient memory. If the system has insufficient memory, the DBS, Memory Limit Reached alarm appears.

For more information, see MTAS Troubleshooting Guideline.

Steps

1. In the VNF-LCM, click Start a Workflow, select Scale-In VNF, and click Start a New Instance.

   

2. In the Start a Workflow view, fill out the Instance Name field and then click Submit.
3. Select the newly created workflow from the Instance Activity panel.
4. In the Workflow Instance view, select the VNF to be scaled in, specify the number of Virtual Machines (VMs) to be deleted from the VNF, and then click Submit.

   

5. In the Collect extra parameters view, select Scale-in type, specify the needed parameters, and then click Submit.

   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-in from the VNF-LCM.

   
   

   Optional scale-in parameters:

   • Specific VMs to be scaled in
   • VM locking method (Graceful or Forceful)

     Note:  

     FORCEFUL scale-in is a disruptive action, therefore it is only to be used to scale in unavailable or failed PLs. The virtual resources reserved for the PLs are freed up first and then the MTAS cluster is "cleaned".

     
     
   • If VMs are locked gracefully: a timer for graceful lock

   

   Note:  

   If any UUID is specified, the VMs with the specified UUIDs are deleted. Otherwise, VMs with the highest index in their name in the OpenStack are deleted.

   
   

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

1. 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.
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 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.