UEM Interworking with Generic VNFM

Feature Summary and Revision History

Summary Data

Applicable Product(s) or Functional Area

 UEM

Applicable Platform(s)

UGP

Feature Default

Disabled - Configuration required

Related Features in this Release

Not Applicable

Related Documentation

  • UEM -based VNF Deployment Guide

Revision History

Revision Details

Release

First introduced.

6.8

Feature Description

The UEM supports the Ve-Vnfm interface as per the ETSI-NFV-SOL002 specification, Version 2.3.1.


Note

In this case, it is assumed that the VNFM is from a third-party vendor.

The Ve-VNFM interface for SOL002 is currently supported for VNF Lifecycle Management only. VNF Instantiation, VNF Termination, Notification Subscription, Notification Handling, and Authentication procedures are currently supported as part of the lifecycle management functions.


Important

The Ve-VNFM interface is currently validated for use with only one particular generic VNFM (gVNFM) vendor. To support other gVNFM vendors, additional testing might be needed. Any vendor-specific implementation or procedures need an enhancement from the UEM side.

This feature is disabled by default. To enable this feature, the following configurations should be included in proxy-params.txt file located at the /opt/cisco/em/config directory as part of the day-0 configuration in UEM. 

vnfm-type:gvnfm
vnfm-proxy-username:em-user
vnfm-proxy-password:artlU@462

Wherein the vnfm-proxy-username and vnfm-proxy-password are new parameters introduced in this release. The value of vnfm-type parameter should be set to gvnfm to enable this feature.