nics
  • Description: Details about the AWS Network Interface Cards (NICs) configuration. See IP Allocation Mode for additional details. The concept of Availability Sets and Zones in AWS is mapped to the subnet as you can have multiple subnets for a each zone. So you must input the list of subnets as the input for an availability set. During an API job deployment, the availability set input is provided as part of the NIC information. To be more specific the first NIC will contain the information as the comma separated subnet list as shown in the example.

  • Type: Object

    networkId                                                                                                                                        
    • Description: The network identifier for each required tier.
    • Type: String

    Required (if configured in your application profile)

    privateIPAllocationMode
    • Description: Identifies the allocation strategy used to configure the NIC for an AWS cloud
    • Type: Enumeration

      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.
      Static IP (only CloudCenter 3.x)
      This strategy allows the customer to provide the IP address. As this IP address may or may not be available to the server (based on the availability), you must perform adequate checks to ensure IP availability before using this strategy.

    order
    • Description: The number at which a resource is to be attached. When updating a phase, use this order to re-order the resource to a different position in the array of resources.
    • Type: Long

    Required (if configured in your application profile)

    nicNetworkType
    • Description: The type of network for this NIC. A corresponding list of domains are attached to each option.
    • Type: Enumeration

      EnumerationDescription
      NETWORKA private network that supports IP ranges which overlap with another private network
      BRIDGE_DOMAINA set of logical ports that share the same flooding or broadcast characteristics. Used for ACI environments.
  • Example 1: Using DHCP allocation mode

    "nics": [
                {
                  "order": 1,
                  "allocationMode": "DHCP",
                  "allocatePublicIp": "true",
                  "id": "subnet-bf7c40cb,subnet-dc3c45f4"
                }]
  • Example2: Using Static IP allocation mode

    Attach the static private address to the NIC when you Create Cloud Instance Type instance create then use that address instead of using the DHCP allocationMode.

    nics":[  
       		{  
          "order":1,
          "allocationMode":"STATIC_IP",
          "allocatePublicIp":"false",
          "id":"subnet-7dc30d25",
          "properties":
    		[{  
                "key":"PRIVATE_IP_LIST",
                "values":[  
                   "12.3.6.1"
                		]
             }]}]
  • Example 3: Using IPv6 Address

    When allocating firewall rules, CloudCenter supports IPv6, in addition to IPv4, addresses in the source for app profile, tenant, and security profiles. When you assign IPv6 addresses, the CloudCenter platform 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 the CloudCenter platform rejects the deployment as invalid. See IP Allocation Mode for additional details.

    nics":[{  
          "order":1,
          "allocationMode":"DHCP",
          "allocatePublicIp":"false",
          "assignIpv6Address": "true",
          "id":"subnet-ab4afff0",
            }
  • Example 4: Using Multiple NICs

    AWS support multiple NICs across subnets in the same availability zone

    [ 
     { 
     "order":1,
     "allocationMode":"DHCP",
     "allocatePublicIp":"true",
     "id":"subnet-74752b32"
     },
     { 
     "order":2,
     "allocationMode":"STATIC_IP",
     "allocatePublicIp":"false",
     "id":"subnet-7dc30d25",
     "properties":[ 
     { 
     "key":"PRIVATE_IP_LIST",
     "values":[ 
     "12.3.6.1"
     ] } ] } ] 



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