Field | Description |
---|
VNF | ConfigInformation - Use this section to enter general information about your deployment. |
VNF Instance Name | Enter a unique name to represent the VNF instance. The name chosen is used throughout the VNFM UI to identify the VNF instance for viewing or performing lifecycle actions. If you do not specify a name for the VNF Instance Name is not configured instance, a name will be is generated. |
Cloud Name | Select a cloud from the Cloud Name drop-down list. |
Tenant Name | Select a tenant for the instance in the Tenant Name drop-down list. |
Reuse Pre-allocated IPs | To reuse the IPV4 pre-allocated IPs addresses that are manually tagged or created during the previous orchestration, click the check box. In the Network section, ensure that the network configuration assigned to the VNF matches the network of the reserved floating IPs. See Using the Pre-allocated IP VNFM Feature. |
VNFM Preference | Optional. Only relevant to a VNFM Geographic Redundancy (GR) configuration. The selected Preferred VNFM responsible for monitoring a specific VNF. Another VNFM instance may monitor the VNF if the preferred VNFM is not available or user reassign VNF to another VNFM instance. If no VNFM is selected, the VNF will be managed by the VNFM instance monitoring with the fewest number of VNFs. |
Zone | Optional. To specify a specific zone for the instance, choose a zone from the list.The list is populated with the Openstack Availability Zones accessible to the tenant. If you do not select a value, the default zone "nova" is selected. |
Continuity Plan | Note: If you specify Default, the VNF is assigned to a VNFM. |
Network - Use this section to select the networks to use within the deployment. |
Required VNF Networks | Network | Using the drop-down lists under Available Networks, select the names of the networks that you want to use | as the management network and the two packet networks for the cluster. The lists contain the names of the existing networks in your environment. Refer to Creating Tenant Networks for more information on creating the prerequisite networks. | If If you are deploying OAM nodes as part of an SBC N:1 HA deployment, | a total of six by default four network fields appear | , : three for the SBC nodes | and three (mgt0, pkt0, pkt1) and one for the OAM nodes | . If you are deploying without OAM nodes, only the first three fields appear. When deploying OAM nodes, select the same three networks in the OAM management and packet network fields fields as you selected for the cluster. (mgt0). However, additional fields can appear based on what you specified when you generated your CSAR package file. Refer to Creating a CSAR Package File for more information on these parameters. (SR-IOV only) If you are implementing SR-IOV interfaces, make sure the signaling/media networks you select ( | Pkt0 pkt0 and | Pkt1pkt1) support SR-IOV. |
Environment |
Address / Port - Use this section to manually configure IP addresses and ports for the VNFC interfaces. |
Reuse Pre-allocated IPs | To reuse the IPV4 pre-allocated IPs addresses that were manually tagged or created during a previous orchestration, click this check box. In the Network section, ensure that the network configuration assigned to the VNF matches the network of the reserved floating IPs. See Using the Pre-allocated IP VNFM Feature. |
VNFC | This column lists each VNFC type and instance number (for example, ssbc1) for which you can configure an IP address and port. |
Interface | This column contains a description of each network interface from the VNFD file (for example, pkt0). |
IP Index | If a VM interface is defined with multiple subnets, this column lists an incremental value to associated with each subnet. The default is zero (0) to indicate a single IP address per VM port. |
Address or Port | Using the drop-down list in the Address or Port column, select the type of value you want to configure for each VNFC / Interface: - Address - to enter an IP address. If the VM is using a private network, the specified IP address identifies the NAT external network IP address. The NAT IP address is referred to as a "floating" IP address and must be already allocated to the tenant.
- Port - to select a port. Optional. If your VNFD file supports manual port configuration, you have the option to select specific ports for the SBC VNFs. If you choose not to specify a port, VNFM creates the port and attaches it to the VM.
|
Selection | Use the field in the Selection column to enter an address or select a port. |
Flavor - Use this section to specify a flavor type to use when instantiating a specific VNFC type. |
Required VNF Flavors | Optional. For each VNFC type listed in the Required VNF column, select a specific flavor from the Available Flavors drop-down list to use when instantiating VMs of that type. The list contains flavors which meet, or exceed, the flavor constraints defined in the VNFD for that VM type. If no flavor is selected, a flavor is auto-selected. |
Storage Volumes - Use this section to optionally specify Cinder storage volume configuration. |
Storage Volume | Optional. If your VNFD file specifies to include a Cinder storage volume in the deployment, use this configuration to attach an existing storage volume. Specify the UUID of a volume on your cloud server. If you do not specify a storage volume, one is automatically created and attached to the instance during instantiation as specified in the VNFD file (refer to Creating a CSAR Package File for information on how to specify a storage volume). If the VNFD file does not specify to include a Cinder storage volume in the deployment, a message appears stating that storage volume configuration is not required. Note: recommends creating a separate volume for logs and attaching it to the instance during launch. Without a separate volume, the SBC writes logs to the root volume (/ ), which is lost if you rebuild or recreate the instance. |
VNF Specific - Use this section to verify settings and provide information that is specific to an SBC deployment | Zone Name | Optional. To specify a specific zone for the instance, click Select a Zone and choose a zone from the list.The Zone Name pull-down list is populated with the Openstack Availability Zones accessible to the tenant. If no value is selected the default zone "nova" is selected. |
VNFC Type: oam SBC:SYSTEMNAME | User-assigned name for the OAM instances. You must enter a name. This field is visible only if you are deploying OAM nodes. |
SOL001 Custom Parameters | Used to dynamically add VNF-specific data to a VNF without requiring a VNFD change. This field is not currently used by the SBC. |
VNFC Type: isbc, ssbc or msbc SBC:SYSTEMNAME | User-assigned name for the SBC instances. You must enter a name. |
SBC Personality | Specifies an integrated (isbc), signaling (ssbc), media (msbc), or other SBC deployment personality. This value cannot be changed. |
The HA model selected in the VNFD file | Specifies an active_standby HA deployment or an N:1 HA (n_1_ha) deployment. This value cannot be changed. |
The number of SBC VMs to create | Specifies the number of SBC VMs to create. For example, a 4:1 HA pair requires 5 VMs. |
The number of OAM VMs to create | Specifies the number of OAM VMs to create. For example, a 1:1 HA pair requires 2 VMs. This field is visible only if you are deploying OAM nodes. |
Properties of IF0 | Parameters associated with IF0. By default IF0 is configured as the management interface. |
Properties of IF1 | Parameters associated with IF1. By default IF1 is configured as the HA interface. |
Properties of IF2 | Parameters associated with IF2. By default IF2 is configured as the Pkt0 interface. (SR-IOV only) Edit the “PrefixVn:” and "VLANId:" values (shown below) to the appropriate values for your interface. Take care to only add the values and do not add additional characters or whitespace.
Image Removed Image Added |
Properties of IF3 | Parameters associated with IF3. By default IF3 is configured as the Pkt1 interface. (SR-IOV only) Edit the “PrefixVn:” and "VLANId:" parameters (shown above) to the appropriate values for your interface. Take care to only add the values and do not add additional characters or whitespace. |
EMS Username | Enter the username credentials to use when registering with the EMS, if applicable. |
EMS Password | Enter the password to use when registering with the EMS, if applicable. |
EMS IP[0] | Enter the IP address of the EMS-0 (primary) instance, if applicable. |
EMS IP[1] | Enter the IP address of the EMS-1 instance, if applicable. |
EmsDownloadConfig | Beginning with release 8.0 this option is no longer needed and the value is ignored. |
EmsPrivateNodeParameters. cluster_id | Enter the value you want to use as the Optionally specifies an EMS cluster ID for the VNF, if applicable. |
Cloud Config Init Data | Replace the default public key with the public key of your own self-generated ssh key pair to be used for logging into SBC. To generate the key, you can use the ssh-keygen command and use the contents of the id_rsa.pub file that it generates in your /home/<user>/.ssh directory to replace the default. Refer to man ssh-keygen for more information. You also have the option to enter passwords for the user accounts defined in this section. Take care to maintain the formatting of this section when you replace the default content. The data must be provided in a proper YAML format. | Flavor | Optional. Select a specific flavor to be used to instantiate VMs of a particular type. For each VM type defined in the VNFD, a drop-down list appears containing flavors which meet, or exceed, the flavor constraints defined in the VNFD for that VM type. If no flavor is selected, a flavor will be auto-selected. |
Manual IP | (SR-IOV and Provider Networks only) For each interface, enter the required IPv4 or IPv6 address. The VNF instantiate will fail if the tenant does not have adequate privileges to create static IP addresses for the associated network. If the VM is using a private network, the specified IP Address will refer to the NAT external network IP address. The NAT IP address is referred to as a "floating" IP address in Openstack terminology and must be already allocated to the tenant. Manual IP section sub-fields: VNFC Name: Displays the VNFC type and instance. An instance value of zero (0) represents a common IP address shared between all VMs of the same VNFC type, also referred to as a VIP (Virtual IP Address) or an Openstack Allowed Address Pair. NIC Name: Network Interface Controller Name displays the VNFD interface port description to assist user in identifying external IP address association and type of network connection. IP Index: If a VM VNFD interface port is defined with multiple subnets, this field will display an incremental value to associated with each subnet. The default is a zero (0) value to indicate a single IP address per VM port |
Manual Ports | Optional. If your VNFD file supports manual port configuration and you want to select the port for the SBC VNF, select the port. If you choose not to specify the neutron port, VNFM creates the port and attaches it to the VM. If your VNFD file does not support manual ports, a message will appear that manual port configuration is not required. |
Storage Volumes | Optional. If your VNFD file supports Cinder storage device configuration (other than a Cinder boot device) and you want to specify a storage volume you created manually, select the volume disk type you created for the SBC on your cloud server. If you do not specify a storage volume, one is automatically created and attached to the instance during instantiation. If the VNFD file does not include a Cinder storage device, a message will appear that storage volume configuration is not required. |