Contents

1   Description

This instruction describes how to instantiate a Virtual Network Function (VNF) using Ericsson Orchestrator (EO). Instantiation in EO consists of preparatory steps, during which HOT files, the VNF configuration file, and other cloud infrastructure-related input are provided. The actual instantiation is done by EO triggering an instantiation workflow in Virtual Network Function Life Cycle Manager (VNF-LCM).

2   Procedure

2.1   Instantiate a VNF

Prerequisites

• The VNF is onboarded on the EO.
• The following virtual and physical hardware and software are required:
  • In EO, the VIM zone, VDC, and SRT are configured, the external Virtual Network Function Manager (VNFM) is registered. For more information on configuring EO, see System Administrator Guide 1543-CNH 160 9180.
• No documents are required.
• No tools are required.

Steps

1. In the EO, start a new VAPP.
2. In Resources > Packages, select the package to deploy and click Deploy.
3. On the Search for Offers screen, select values for the mandatory fields, and click Next.
4. On the Set VIM Criteria screen, click Next.
5. On the Choose VIM Zone screen, select the desired VIM zone, and click Next.
6. On the Enter Attributes screen, provide values for the fields of the VAPP Attributes tab:
   • Virtual Application Name, which is also the name of the Heat stack
   • VNF Manager (The one chosen during onboarding is preselected.)
   • Flavor (The virtual hardware configuration of the VNF. For example, the number of vCPUs and memory size.)

   Note:  

   The value provided for Flavor is not used at this point, but as it is a mandatory field, a dummy value must be provided.

   
   
7. On the Enter Attributes screen, provide the VNFD_Wrapper.json file on the Configuration tab.

   It is possible to overwrite the VNFD_Wrapper.json file provided during onboarding either by uploading an updated file or by modifying the attribute values on the Configuration tab.

8. Click Submit Order to finalize instantiation.
   Result:
   On the opening window, by clicking View Asset List, you can check the status of the instantiation order. EO triggers an instantiation workflow in VNF-LCM, and the VNF becomes visible in the VNFM used.

   Note:  

   If the EO and the VNF-LCM are in a mutually granting connection, the new instance appears in the VNF-LCM after a successful instantiation 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.