IP address allocation

IP allocation mode (OpenStack only)

This feature allows you to add multiple Network Interface Cards (NICs) to a VM, and for each NIC, discover the private IP beforehand (pre-allocate IP) and pass it through the config drive file to the OpenStack cloud provider.

This feature is only available for OpenStack clouds.

OpenStack supports association of the public IP to any private IP and hence to any NIC as mentioned by the user.

At deploy time you can also choose the IP allocation strategy for each NIC's Private IP Address: DHCP or Pre-allocate IP:

EnumerationDescription
DHCP (default)This strategy allows the IP to be allocated by the DHCP server to the instance on server boot up. This IP address is not known prior to server boot up.
Pre-allocate IP

This strategy allows the cloud infrastructure IP allocation to be dynamically provided before the server boots up. This strategy is specific to the following OpenStack applications:

  • CISCO CSR1000: Configuration drive file IP populated with the pre-allocated IPs known before server boot up.
  • CISCO F5 Load Balancer: Multiple NIC support.

Use IPAM callout scripts to configure IP allocation strategies. See Guidance for Callout Scripts for additional context.

Configuration File Attributes

  • Add a cloudConfigFilePath parameter with a value as file path and type as string.

  • Add a cloudConfigFileContents parameter with value as file contents and type as textarea

The %NIC#_IP% Parameter Substitution (OpenStack only)

The number of NICs (NIC1, NIC2...) corresponds to number of network interfaces in the application profile. The IP address substitution parameters used in configuration files (see Configuration Files) will be in the same order as %NIC1_IP%, %NIC2_IP%, ... configuration. If the number of NICs = 1 and you have a preferred/default network defined, the input will be defaulted to that network with the DHCP option. Otherwise, you must select the required network for any job submission.

The NIC order is important – the order defines the parameters loaded with IP address. For example, if the order is 1 and strategy is PREALLOCATE_IP, the parameter generated is %NIC1_IP% (first NIC), %NIC2_IP% (second NIC) and this parameter is replaced in the configuration drive file provided to VM with the corresponding IP address.

Managing IPv6  (AWS and OpenStack only)

IPv6 Addresses

By default, all networks default to using IPv4 and no additional configuration is required when using IPv4 addresses.

When allocating firewall rules, CloudCenter Suite supports IPv6, in addition to IPv4, addresses in the source for app profile, tenant, and security policies. When you assign IPv6 addresses, Workload Manager validates the security rule source before accepting the IPv6 address. This support is restricted to AWS and OpenStack clouds. If you provide an invalid IPv4/6 IP address, then Workload Manager rejects the deployment as invalid.

To use IPv6 addresses, follow this process.

  1. Configure Firewall Settings in Tenant Management and check the following boxes:

    • Allow launched VMs to communicate with each other

    • Create default security groups for users in this Tenant

    • See Security and Firewall Rules for additional context

  2. Add the required firewall rule using the IPv4/6 address and update the Tenant.

  3. Add a Policies > Security Policy and configure it to use the firewall rule(s) using the IPv6 address.

  4. Configure the firewall rule in the application profile (Application > Topology Modeler > Firewall Rule > Add IP address and the validation works here as well.

  5. Deploy the application using the IPv6 address.

The Virtual Machine Management > Managed VMs > VM Details section displays a configured IPv6 IP address.

  • If an IPv6 IP address is not configured, this field displays a dash ( - ).

  • If multiple IP addresses are configured, this field displays each configured address in its own line.

Note these cloud nuances for managing IPv6 addresses:

  • AWS
 AWS cloud nuances
  • The Assign IPv6 Address feature is also available on a per-NIC basis as Workload Manager supports IPv6 addresses as a source for application profiles, tenants, and security policies.

    • Deploy the Application Profile by selecting the configured Security Policy in the General Settings and Tier Settings sections and the Network with IPv4/6 along with the IP allocation requirements.

    • The CloudCenter Deployments page displays the new deployment and your Cloud Console displays the spawned instance. When you view the details for this deployment in the cloud console, you see the corresponding security group and firewall settings deploying the IPv6 address configuration if you have checked the Create default security groups for usersin this Tenant and Allow launched VMs to communicate with each other boxes.

  • OpenStack
 OpenStack cloud nuances

  • The Assign IPv6 Address feature is also available on a per-NIC basis as Workload Manager supports IPv6 addresses as a source for application profiles, tenants, and security policies.

    • Deploy the Application Profile by selecting the configured Cloud Tenant and Network with IPv4/6  and providing the IP allocation requirements in the Cloud Settings section.

    • The CloudCenter Deployments page displays the new deployment and your Cloud Console displays the spawned instance. When you view the details for this deployment in the cloud console, you see the corresponding security group and firewall settings deploying the IPv6 address configuration if you have checked the Create default security groups for usersin this Tenant and Allow launched VMs to communicate with each other boxes.

    • The IPv6 field merely identifies if IPv6 is enabled or disabled for the subnet in the cloud-level settings. This is an information field and cannot be configured..


Assign IPv4 Public IP (All VM-based clouds except vCenter)

Note these cloud nuances for managing IPv4 addresses:

  • AWS
 AWS cloud nuances
  • The Assign IPv4 Public IP feature indicates that the eth0 interface can be associated with an IPv4 public IP.

During application deployment or when setting deployment environment defaults for AWS configurations, the Assign Public IP setting reflects the status of the Enable auto-assign Public IP setting for the selected AWS subnet. If Assign Public IP = Unchecked + Enable auto-assign Public IP = Unchecked, the Public IP is not assigned and the deployment fails. For this reason, Workload Manager automatically toggles the Assign Public IP setting based on the pinned subnet. You can override this setting during the CloudCenter application deployment. Be aware that if you do not have access to internet, the subnet routing table will not be connected to an internet gateway.

  • Google
 Google cloud nuances
  • The Assign IPv4 Public IP feature is available on a per-NIC basis as Google supports private-public IP pair.

  • Multiple NIC support is not currently available.

  • OpenStack
 OpenStack cloud nuances
  • The Assign IPv4 Public IP feature is available on a per-NIC basis as OpenStack supports private-public IP pair.

  • vCenter
 Vmware cloud nuances
  • vCenter does not support public IP addresses.

  • No labels
© 2017-2019 Cisco Systems, Inc. All rights reserved