Reuse Floating IP Address

• Feature Summary and Revision History, page 1

• Feature Description, page 2

Feature Summary and Revision HistorySummary Data

• Ultra M Solution

• Ultra Automation Services

Applicable Product(s) or FunctionalArea

Ultra Gateway PlatformApplicable Platform(s)

Enabled – Configuration RequiredFeature Default

Not ApplicableRelated Changes in This Release

• USP Deployment Automation GuideRelated Documentation

Revision History

ReleaseRevision Details

N5.5First Introduced.

Release Change Reference, StarOS Release 21.3/Ultra Services Platform Release N5.5 1

Feature DescriptionIn this release, the Ultra Service Platform (USP) can re-use the same floating IP address to redeploy the CF,UEM, and VNFM (currently the Cisco Elastic Services Controller (ESC)).

In previous releases, if these VMs were restarted, they’d likely receive different IP addresses from those theyhad prior to being restarted. This feature ensures that the IP address they receive after restarting remains thesame.

Prior to assigning floating and virtual IP addresses, make sure that they are not already allocated throughOpenStack. If the addresses are already allocated, then they must be freed up for use or you must assigna new IP address that is available in the VIM.

Note

The configuration of this feature is done through new parameters added to the AutoDeploy configuration fileand/or UWS service deployment configuration file.

Auto Deploy Configuration File ParametersNew parameters were added to the following configuration file constructs within the AutoDeploy configurationfile in support of this feature:

• VNFM Descriptor (vnfmd) Parameters, on page 2

• VNF Descriptor (vnfd) Parameters, on page 3

VNFM Descriptor (vnfmd) ParametersThe bold parameters in the sample configuration below are new within the vnfmd construct and must beconfigured to reuse floating addresses across VNFM VM restarts:vnfmd ab-auto-test-vnfm1high-availability truelogin-credential autovnf-adminnetconf-credential autovnf-adminimage pre-created default-non-imagevnf-rackd auto-test-sjc-vnf1-rackfloating-ip trueha-vip <vip_address>floating-ip-address <floating_address>configs openstack.endpointvalue publicURL!flavor vcpus 2flavor ram 4096flavor root-disk 40flavor ephemeral-disk 0flavor swap-disk 0flavor host-aggregate auto-test-sjc-cf-esc-mgmt1

The default setting for the floating-ip parameter is false which disables this functionality for the VNFM.This parameter must be set to true to enable the reuse of IP addresses across VNFM VM restarts.

Note

Release Change Reference, StarOS Release 21.3/Ultra Services Platform Release N5.52

Reuse Floating IP AddressFeature Description

VNF Descriptor (vnfd) ParametersThe bold parameters in the sample configuration below are new within the vnfd construct and must beconfigured to reuse floating addresses across UEM and CF restarts:vnfd auto-testvnfd1<---SNIPPET--->vnf-deployment vnfd1-deploymentvnf-em vdu-id element-managervnf-em high-availability truevnf-em ha-vip <vip_address>vnf-em floating-ip truevnf-em floating-ip-address <floating_address>vnf-em scm-admin autovnf-adminvnf-em scm-oper autovnf-opervnf-param type vpcvnf-param configuration domain-name cisco.com!vnf-param configuration dns-servers 171.70.168.183!vnf-param internal-network di-internal1!vnf-param internal-network di-internal2!infra-element-groups di-chasishigh-availability trueinstances 1vdus CFvdu-ref control-functioninstances 2interfaces di_intf1network di-internal1floating-ip false!interfaces orchnetwork orchestrationfloating-ip false!interfaces mgmtnetwork managementenable-ha-vip <vip_address>floating-ip truefloating-ip-address <floating_address>uplink-actions mount-ned-nc!!interfaces di_intf2network di-internal2floating-ip false!interface-bonds DI_INTERFACEbond-interfaces di_intf1!bond-interfaces di_intf2!!!

<---SNIPPET--->Notes:

• The default setting for the floating-ip and vnf-em floating-ip parameters is false which disables thisfunctionality.

• Setting the vnf-em floating-ip to true enables this functionality for the UEM.◦

Release Change Reference, StarOS Release 21.3/Ultra Services Platform Release N5.5 3

Reuse Floating IP AddressAuto Deploy Configuration File Parameters

◦Setting the floating-ip parameter under interfaces mgmt to true enables this functionality for theCF.

• The floating-ip parameter under interfaces di_intf1, interfaces orch, and interfaces orch is notimplemented in this release and should remain set to false. (This is the default setting.)

UWS Service Deployment Configuration File ParametersNew parameters were added to the following configuration file constructs within the AutoDeploy configurationfile in support of this feature:

• VNFM Descriptor (vnfmd) Parameters, on page 4

• VNF Descriptor (vnfd) Parameters, on page 5

VNFM Descriptor (vnfmd) ParametersThe bold parameters in the sample configuration below are new within the vnfmd construct and must beconfigured to reuse floating addresses across VNFM VM restarts:<vnfmd xmlns="http://www.cisco.com/usp/nfv/usp-autodeploy" annotation="## VNFM / ESC #1## !">

<id>ab-auto-test-vnfm1</id><high-availability>true</high-availability><login-credential>autovnf-admin</login-credential><netconf-credential>autovnf-admin</netconf-credential><configs><variable>openstack.endpoint</variable><value>publicURL</value>

</configs><image><pre-created>default-non-image</pre-created>

</image><vnf-rackd>auto-test-sjc-vnf1-rack</vnf-rackd><flavor><vcpus>2</vcpus><ram>4096</ram><root-disk>40</root-disk><ephemeral-disk>0</ephemeral-disk><swap-disk>0</swap-disk><host-aggregate>auto-test-sjc-cf-esc-mgmt1</host-aggregate>

</flavor><floating-ip>true</floating-ip><ha-vip>vip_address</ha-vip><floating-ip-address>floating_address</floating-ip-address>

</vnfmd>

The default setting for the <floating-ip> parameter is falsewhich disables this functionality for the VNFM.This parameter must be set to true to enable the reuse of IP addresses across VNFM VM restarts.

Note

Release Change Reference, StarOS Release 21.3/Ultra Services Platform Release N5.54

Reuse Floating IP AddressUWS Service Deployment Configuration File Parameters

VNF Descriptor (vnfd) ParametersThe bold parameters in the sample configuration below are new within the vnfd construct and must beconfigured to reuse floating addresses across UEM and CF restarts:<vnfd xmlns="http://www.cisco.com/usp/nfv/usp-autodeploy" annotation="## VNF#1 ## !"><---SNIPPET--->

<vnf-deployment><deployment-id>vnfd1-deployment</deployment-id><vnf-param><type>vpc</type><configuration><name>domain-name</name><value>cisco.com</value>

</configuration><configuration><name>dns-servers</name><value>171.70.168.183</value>

</configuration><internal-network><network>di-internal1</network>

</internal-network><internal-network><network>di-internal2</network>

</internal-network></vnf-param><vnf-em><vdu-id>element-manager</vdu-id><ha-vip>vip_address</ha-vip><high-availability>true</high-availability><floating-ip>true</floating-ip><floating-ip-address>floating_address</floating-ip-address><scm-admin>autovnf-admin</scm-admin><scm-oper>autovnf-oper</scm-oper>

</vnf-em><infra-element-groups><name>di-chasis</name><high-availability>true</high-availability><instances>1</instances><vdus><vdu-id>CF</vdu-id><vdu-ref>control-function</vdu-ref><instances>2</instances><interfaces><ifname>di_intf1</ifname><network>di-internal1</network><floating-ip>false</floating-ip>

</interfaces><interfaces><ifname>orch</ifname><network>orchestration</network><floating-ip>false</floating-ip>

</interfaces><interfaces><ifname>mgmt</ifname><network>management</network><enable-ha-vip>vip_address</enable-ha-vip><floating-ip>true</floating-ip><floating-ip-address>floating_address</floating-ip-address><uplink-actions><action>mount-ned-nc</action>

</uplink-actions></interfaces><interfaces><ifname>di_intf2</ifname><network>di-internal2</network><floating-ip>false</floating-ip>

</interfaces>

Release Change Reference, StarOS Release 21.3/Ultra Services Platform Release N5.5 5

Reuse Floating IP AddressUWS Service Deployment Configuration File Parameters

<interface-bonds><bond>DI_INTERFACE</bond><bond-interfaces><interface>di_intf1</interface>

</bond-interfaces><bond-interfaces><interface>di_intf2</interface>

</bond-interfaces></interface-bonds>

</vdus><---SNIPPET--->Notes:

• The default setting for the floating-ip parameters is false which disables this functionality.

◦Setting the <floating-ip> parameter under<vnf-em>to true enables this functionality for the UEM.

◦Setting the <floating-ip> parameter under <ifname>mgmt</ifname> to true enables thisfunctionality for the CF.

• The <floating-ip> parameter under <ifname>di_intf1</ifname>, <ifname>orch</ifname>, and<ifname>di_intf2</ifname> is not implemented in this release and should remain set to false. (This isthe default setting.)

Release Change Reference, StarOS Release 21.3/Ultra Services Platform Release N5.56

Reuse Floating IP AddressUWS Service Deployment Configuration File Parameters