Scale In VMware VNF Using VNF-LCM
Call Session Control Function

Contents

1Description

2

Procedure
2.1Scale in a VNF
2.2Troubleshooting

1   Description

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

Prerequisites

Attention!

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.

Scaling in SC-1, SC-2, PL-3, and PL-4 is not possible. Hence, the CSCF cluster configuration is a 2 + 2 configuration or larger.

Continue with this procedure only if the VNF to be scaled out is instantiated using the VNF-LCM.

Steps

  1. In the VNF-LCM, click Start a Workflow, and select Scale VNF, and then 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. On the Workflow Instance screen, select the VNF to be scaled in, select Scale In for scaling type, specify the number of Virtual Machines (VMs) to be deleted from the VNF, and then click Submit.

The following step is optional. If none of these parameters are needed, leave the fields blank.

  1. In the Collect extra parameters view, specify the needed parameters, and then click Submit.

    Optional scale-in parameters:

    • Specific VMs to be scaled-in
    • Scale-in type (Graceful or Forceful)
    • VM Universal Unique Identifiers (UUIDs) to scale in.

The VNF instance is scaled in and the specified number of VMs is deleted from the cluster.

Note:  
If any UUID was specified in Step 5, the VMs with the specified UUIDs are removed.

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