Important

   

Starting version 8.9.03, BMC Network Automation is renamed to TrueSight Network Automation. This space contains information about BMC Network Automation 8.9.02 and previous versions. For TrueSight Network Automation 8.9.03 and later releases, see the TrueSight Network Automation documentation.

Creating a pod from a pod blueprint

This topic presents an example of creating a pod by using the reference large pod blueprint from Cisco. The pages and details shown are different depending upon which Pod Blueprint is being used.

Before you begin

  • BMC Network Automation must be installed and configured.
  • If you are using BMC Atrium CMDB, integration between BMC Network Automation and BMC Atrium CMDB must be configured. For information about configuring system parameters to support CMDB integration, see Managing system-wide parameters.
  • Devices that you intend to assign to the pod must be defined in BMC Network Automation. Devices that are intended as pod hosts should use file transfer mode for faster firewall updates.

To create a new pod from a Pod Blueprint

  1. In the Pod Blueprints page click Create Pod  to the right of the Pod Blueprint.
  2. In the Pod Details page, specify the pod details:
    1. Enter a unique name for the pod. 
      The name can include only alphanumeric characters. It cannot include symbols or special characters such as a single quote (') or dollar sign ($). 
    2. Select a site from the drop-down list of sites.
      This list is populated from the BMC Atrium CMDB.
    3. Click Next.
      The Pod Node page appears.

      Note

      In the Pod Node page, you cannot change the values in the Name, Category, and Role fields in the UI, but they determine which other selections you can make for this pod.
  3. Make selections and enter information as shown in the following table. This table contains options that are available for various types of devices. In general, the uppercase field names such as ACCESS_LINKID are derived from a pod blueprint. Some of the options in this example are specific to Cisco devices. Other vendors' devices have different options. Fields that require multiple entries are called balanced fields. BMC Network Automation uses the entries alternately for successive container instances that are created. Separate entries in these fields by pressing Enter or Return. The entries appear on separate lines.

    Pod node options

    Field

    Description

    Skip Node?

    Select No to include this node in the pod that you are creating, or select Yes to exclude this node from the pod that you are creating.

    Include devices from other nodes in the selection list

    Select this option to include devices from other pods in the device selection list.

    Include devices from other pods in the selection listSelect this option to include devices from other nodes within this pod in the device selection list.

    Realm

    Select the realm that the device belongs to. This option is available only if the administrator has created one or more realms in addition to the default realm.

    Device

    Click the  button, and then select a device from the list. You can click a device name or type a name.

    Max VRFs

    (optional) Enter the maximum number of virtual routing and forwarding (VRFs) allowed for this pod node.

    Max VFWs

    (Optional) Enter the maximum number of virtual firewalls (VFWs) allowed on this pod host node. This option applies only to firewall devices.

    Max Rules per VFW

    (Optional) Enter the maximum number of rules that can be added to the Access Control List (ACL) within the VFW. This option applies only to firewall devices.

    Max VLBs

    (Optional) Enter the maximum number of virtual load balancers (VLBs) allowed on this pod host node.

    Max Pools per VLB

    (Optional) Enter the maximum number of pools per VLB.

    Max Entries per Pool

    (Optional) Enter the maximum number of entries per pool.

    BGP_COMMUNITY

    (vendor-specific) Enter the border gateway protocol (BGP) community value to use.

    C1_GROUPLEVEL C2_GROUPLEVEL

    (vendor-specific) Enter the BGP group level.

    ACCESS_LINKID C1_LINKID C2_LINKID E1_LINKID E2_LINKID and so on

    (vendor-specific) Enter the name of a high speed interface (for example, GigabitEthernet1/2 ) or the name of a port channel (for example Po123 ) that connects the pod node in question to an adjacent pod node.

    SVC_LINKID

    (vendor-specific) Enter the name of the access device.

    HSRPPRIORITY

    (vendor-specific) Enter at least two hot standby routing protocol priority values.

    OSPFPRIORITY

    (vendor-specific) Enter at least two open shortest-path-first routing priority values.

    ROGUE_DEVICE_ADDRESS

    Enter the address of the rogue device.

    Max Ports

    (Optional) Enter the maximum number of virtual ports that can be created in the hypervisor switch.

    Max Port Types

    (Optional) Enter the maximum number of virtual port types that can be created in the hypervisor switch. A virtual port type is called a port group by VMware and a port profile by Cisco. The switch uses the virtual port type to create a given virtual port for a given Network Interface Card (NIC) being attached to the switch. There is one virtual port type for each network that a NIC can be attached to on the switch, for each container instance on the pod.

    HOST_MGMT_IP1 HOST_MGMT_IP2

    Enter the IP addresses of SNMP management stations for the VLB and VFW to send traps to.

    Ports

    Enter a comma-separated list of the ports you want to use. 

    Note: When provisioning a physical server pod node, you must enter all the required switch ports, or the physical server targets cannot be onboarded in BMC Cloud Lifecycle Management.

  4. Click Next.
  5. Repeat step 3 and step 4 for each subsequent pod node.
  6. In the Pod Pair page that appears for each pod pair, click Next.
    The DNS and NIC Information page appears.

  7. Enter the following information:

    Field

    Description

    Primary DNS Server

    Specify the primary DNS server name. This field is required when you specify tags related to DNS.

    Reverse DNS Server(Version 8.5.01 and later) Specify the reverse DNS server that allows reverse lookup of the IP address. In other words, given the IP address, the reverse DNS resolves the domain name associated with the IP address. If you specify the value for this field, only PTR records are added, otherwise, the API adds only an A record in the Primary DNS Server.

    For example, an address (A) record for mail.example.com points to the IP address 192.168.10.4. In pointer records of the reverse DNS server, this IP address is stored as the domain name 192.168.10.4.in-addr.arpa pointing back to its designated host name mail.example.com.

    Secondary DNS Server

    Specify the secondary DNS server name.

    Primary Domain Suffix for NIC

    Specify the primary domain suffix for NIC segments.

    DNS Domains for NIC

    Specify the domain search order as a comma-separated list.

    Reverse DNS Zone

    (Version 8.5.01 and later) Specify the reverse DNS zone where the PTR-record type stores reverse DNS entries. The reverse DNS zone value is specific to the network address from which the PTR entries can be added.

    For example, if the network address is 198.168.10.0/24, the reverse DNS zone is 10.168.198.in-addr.arpa.

  8. Click Next.
    The Address Pool page appears.
  9. Make selections and enter the following information:

    Address Pool options

    Field

    Description

    Pool Address

    The starting address of the address pool. Specify the CIDR mask of the pool in the box to the right. Valid values for the CIDR mask for IPv4 are 1 to 32.

    Public

    Select the Public option to make the address pool public. Making the pool public means that only one copy of the pool is permitted in IPAM. Otherwise, if a pool is flagged as private, each pod is allowed by IPAM to get its own copy of the pool in question.

    Shareable

    Select the Shareable option to allow multiple pods to share the address pool. When a pool is shared, it can be used to acquire addresses for containers in each pod that shares the pool. Otherwise, it can only be used to acquire addresses for containers in one pod exclusively.

    Note: If you flag an address pool as Shareable, multiple pods are allowed to reserve the same subnet/address pool from the IP Address Management (IPAM) system. Each pod sharing the same copy of the subnet/address pool has Scope value equal to the first <pod-name> through which it is created. If you exclude the IPs from the subnet/address pool with the Scope other than <pod-name>, the IP address is not excluded from the shared subnet/address pool.

    Primary DNS Server

    Specify the primary DNS server name. This field is required when you specify tags related to DNS.

    Reverse DNS Server(Version 8.5.01 and later) Specify the reverse DNS server that allows reverse lookup of the IP address. In other words, given the IP address, the reverse DNS can resolve the domain name associated with the IP address. If you specify the value for this field, only PTR records are added, otherwise, the API adds only an A record in the Primary DNS Server.

    Secondary DNS Server

    Specify the secondary DNS server name.

    Gateway Address

    Specify the address of the gateway of the address pool. This was a required parameter in BMC BladeLogic Network Automation version 8.1.x; it is no longer so.

    Primary Domain Suffix for NIC

    Specify the primary domain suffix for NIC segments.

    DNS Domains for NIC

    Specify the domain search order as a comma-separated list.

    Reverse DNS Zone(Version 8.5.01 and later) Specify the reverse DNS zone where the PTR-record type stores reverse DNS entries. The reverse DNS zone value is specific to the network address from which the PTR entries can be added.
  10. Click Next.
    The Address Range page appears.
  11. Make selections and enter the following information:

    Field

    Description

    Range Address

    Enter the base IP address of the customer address range. Specify the CIDR mask of the customer range in the box to the right. The range address and range mask define the range of IP addresses that is available to the customer. Valid values for the CIDR mask for IPv4 are 1 to 32.

    Pool Mask

    Enter the CIDR mask that defines the size of each pool within the range. For example, if the Range Mask is 24 and the Pool CIDR Mask is 28 the range contains 16 ranges of 16 addresses each.

    Public

    Select the Public option to make the address pool public. Making the pool public means that only one copy of the pool is permitted in IPAM. Otherwise, if a pool is flagged as private, each pod is allowed by IPAM to get its own copy of the pool in question.

    Primary DNS Server

    Specify the primary DNS server name. This field is required when you specify tags related to DNS.

    Reverse DNS Server(Version 8.5.01 and later) Specify the reverse DNS server that allows reverse lookup of the IP address. In other words, given the IP address, the reverse DNS can resolve the domain name associated with the IP address. If you specify the value for this field, only PTR records are added, otherwise, the API adds only an A record in the Primary DNS Server.

    Secondary DNS Server

    Specify the secondary DNS server name.

    Primary Domain Suffix for NIC

    Specify the primary domain suffix for NIC segments.

    DNS Domains for NIC

    Specify the domain search order as a comma-separated list.

    Reverse DNS Zone(Version 8.5.01 and later) Specify the reverse DNS zone where the PTR-record type stores reverse DNS entries. The reverse DNS zone value is specific to the network address from which the PTR entries can be added.
  12. Click Next.
    The Integer Pool page appears. 

  13. Specify the integer pool details:
    1. Enter a start and end range for the pool.
    2. (Optional) Enter any numbers that are to be excluded from the range of values. No container acquires these values.
  14. Click Next.
  15. In the Vlan Pool: Customer Vlans page, specify the customer VLAN pool details:
    1. (Optional) Specify whether you want the pool to be shared by multiple pods. When a pool is shared, it can be used to acquire VLANs for containers in each pod that shares the pool. Otherwise, it can only be used to acquire VLANs for containers in one pod exclusively.
    2. (Optional) Specify whether you want the pool to be an extended pool, which supports Virtual Extensible VLAN (VXLAN). For an extended pool, the VLAN pool range is from 0 to 224.
    3. Enter a start and end range for the pool.
    4. (Optional) Enter any VLANs that must be excluded from the pool range.
  16. Click Next.
    The VLAN Pool: Infrastructure Vlans page appears.
  17. Specify the Infrastructure VLAN pool details:
    1. (Optional) Specify whether you want the pool to be shared by multiple pods. When a pool is shared, it can be used to acquire VLANs for containers in each pod that shares the pool. Otherwise, it can only be used to acquire VLANs for containers in one pod exclusively.
    2. (Optional) Specify whether you want the pool to be an extended pool, which supports VXLAN. For an extended pool, the VLAN pool range is from 0 to 224.
    3. Enter a start and end range for the pool.
    4. (Optional) Enter any VLANs that must be excluded from the pool range.
  18. Click Next.
    The VLAN Pool: Management Vlans page appears.
  19. Specify the management VLAN pool details:
    1. (Optional) Specify whether you want the pool to be shared by multiple pods. When a pool is shared, it can be used to acquire VLANs for containers in each pod that shares the pool. Otherwise, it can only be used to acquire VLANs for containers in one pod exclusively.
    2. (Optional) Specify whether you want the pool to be an extended pool, which supports VXLAN. For an extended pool, the VLAN pool range is from 0 to 224.
    3. Enter a start and end range for the pool.
    4. (Optional) Enter any VLANs that must be excluded from the pool range.
  20. Click Next.
    The VLAN page appears.

  21. Specify the management VLAN number from the management VLAN pool, and click Next.
  22. In the Pod Parameter page, click Submit.
    The pod is created and added to the Pods tab or an error message is displayed.

    Note

    When creating a pod if Error creating Pod:Read time out error is displayed, increase the timeout value for the Web Service interaction between BMC Network Automation and the external system by increasing the aoServerTimeout setting in the global.properties file

To create a large pod from the reference content

The following steps describe how to create a large pod from the Large Pod Blueprint using the Create Pod wizard:

 Click here to view the steps

  1. Navigate to the Pod Blueprints list page:
    Network > Virtual Data Center > Pod Blueprints
  2. Click the Create Pod icon for the Large Pod Blueprint.
  3. Enter the following information in the Pod Details page and click Next:

    FieldDescription

    Name

    Name of the pod.

    Site

    Select a site to apply the pod.

    Note

    If Configuration Management Database (CMDB) integration is enabled, a drop-down menu is displayed for the Site field. If a CMDB is not reachable, a message requesting that you verify the CMDB logon credentials is displayed on this page. See BMC Continuous Compliance for Network Automation solution for more information about enabling CMDB integration.

  4. Enter the following information in the Pod Node: Agg 1 page and click Next:

    FieldDescription

    Shareable

    (Optional) Select to make this pod node shareable.

    Device

    Select the device name for this pod node.

    Max VRFs

    (Optional) Specify the maximum number of Virtual Routing and Forwarding (VRF) instances for this node.

    C1_LINKID

    Enter the link ID for the link to the Core 1 pod node.

    A2_LINKID

    Enter the link ID for the link to the Agg 2 pod node.

    C2_LINKID

    Enter the link ID for the link to the Core 2 pod node.

    HRSPPRIORITY

    Enter the Hot Standby Router Protocol (HSRP) priority levels for the primary and secondary routers that would assume the default gateway role.

  5. Enter the following information in the Pod Node: Agg 2 page and click Next:

    FieldDescription

    Shareable

    (Optional) Select to make this pod node shareable.

    Device

    Select the device name for this pod node.

    Max VRFs

    (Optional) Specify the maximum number of VRF instances for this node.

    C1_LINKID

    Enter the link ID for the link to the Core 1 pod node.

    C2_LINKID

    Enter the link ID for the link to the Core 2 pod node.

    A1_LINKID

    Enter the link ID for the link to the Agg 1 pod node.

    HRSPPRIORITY

    Enter the HSRP priority levels for the primary and secondary routers that would assume the default gateway role.

  6. Enter the following information in the Pod Node: Core 1 page and click Next:

    FieldDescription

    Shareable

    (Optional) Select to make this pod node shareable.

    Device

    Select the device name for this pod node.

    Max VRFs

    (Optional) Specify the maximum number of VRF instances for this node.

    A2_LINKID

    Enter the link ID for the link to the Agg 2 pod node.

    C2_LINKID

    Enter the link ID for the link to the Core 2 pod node.

    A1_LINKID

    Enter the link ID for the link to the Agg 1 pod node.

    E1_LINKID

    Enter the link IDs for the links to the Edge 1 pod node.

    E2_LINKID

    Enter the link IDs for the links to the Edge 2 pod node.

  7. Enter the following information in the Pod Node: Core 2 page and click Next:

    FieldDescription

    Shareable

    (Optional) Select to make this pod node shareable.

    Device

    Select the device name for this pod node.

    Max VRFs

    (Optional) Specify the maximum number of VRF instances for this node.

    C1_LINKID

    Enter the link ID for the link to the Core 1 pod node.

    A2_LINKID

    Enter the link ID for the link to the Agg 2 pod node.

    A1_LINKID

    Enter the link ID for the link to the Agg 1 pod node.

    E1_LINKID

    Enter the link IDs for the links to the Edge 1 pod node.

    E2_LINKID

    Enter the link IDs for the links to the Edge 2 pod node.

  8. Enter the following information in the Pod Node: Edge 1 page and click Next:

    FieldDescription

    Shareable

    (Optional) Select to make this pod node shareable.

    Device

    Select the device name for this pod node.

    Max VRFs

    (Optional) Specify the maximum number of VRF instances for this node.

    C1_GROUPLEVEL

    Enter the group level ID for Border Gateway Protocol (BGP) Group 1.

    C1_LINKID

    Enter the link IDs for the links to the Core 1 pod node.

    C2_LINKID

    Enter the link IDs for the links to the Core 2 pod node.

  9. Enter the following information in the Pod Node: Edge 2 page and click Next:

    FieldDescription

    Shareable

    (Optional) Select to make this pod node shareable.

    Device

    Select the device name for this pod node.

    Max VRFs

    (Optional) Specify the maximum number of VRF instances for this node.

    C2_GROUPLEVEL

    Enter the group level ID for BGP Group 2.

    C1_LINKID

    Enter the link IDs for the links to the Core 1 pod node.

    C2_LINKID

    Enter the link IDs for the links to the Core 2 pod node.

  10. Enter the following information in the Pod Node: Services page and click Next:

    FieldDescription

    Shareable

    (Optional) Select to make this pod node shareable.

    Device

    Select the device name for this pod node.

    Max VRFs

    (Optional) Specify the maximum number of VRF instances for this node.

    BGP_COMMUNITY

    Enter the community number for the BGP Community for this pod.

  11. Enter the following information in the Pod Node: Firewall Host A1 page and click Next:

    FieldDescription

    Skip Node?

    (Optional) Select Yes to skip this node if it is not required to create the pod. Default value is No.

    Shareable

    (Optional) Select to make this pod node shareable.

    Device

    Select the device name for this pod node.

    Max VRFs

    (Optional) Specify the maximum number of VRF instances for this pod node.

    Max VFWs

    (Optional) Specify the maximum number of Virtual Firewall (VFW) instances for this pod node.

    Max Rules per VFW

    (Optional) Specify the maximum number of rules per VFW for this node.

  12. Enter the following information in the Pod Node: Firewall Host A2 page and click Next:

    FieldDescription

    Skip Node?

    (Optional) Select Yes to skip this node if it is not required to create the pod. Default value is No.

    Shareable

    (Optional) Select to make this pod node shareable.

    Device

    Select the device name for this pod node.

    Max VRFs

    (Optional) Specify the maximum number of VRF instances for this pod node.

    Max VFWs

    (Optional) Specify the maximum number of VFW instances for this pod node.

    Max Rules per VFW

    (Optional) Specify the maximum number of rules per VFW for this node.

  13. Enter the following information in the Pod Node: Firewall Host B1 page and click Next:

    FieldDescription

    Skip Node?

    (Optional) Select Yes to skip this node if it is not required to create the pod. Default value is No.

    Shareable

    (Optional) Select to make this pod node shareable.

    Device

    Select the device name for this pod node.

    Max VRFs

    (Optional) Specify the maximum number of VRF instances for this pod node.

    Max VFWs

    (Optional) Specify the maximum number of Virtual Firewall (VFW) instances for this pod node.

    Max Rules per VFW

    (Optional) Specify the maximum number of rules per VFW for this node.

  14. Enter the following information in the Pod Node: Firewall Host B2 page and click Next:

    FieldDescription

    Skip Node?

    (Optional) Select Yes to skip this node if it is not required to create the pod. Default value is No.

    Shareable

    (Optional) Select to make this pod node shareable.

    Device

    Select the device name for this pod node.

    Max VRFs

    (Optional) Specify the maximum number of VRF instances for this pod node.

    Max VFWs

    (Optional) Specify the maximum number of Virtual Firewall (VFW) instances for this pod node.

    Max Rules per VFW

    (Optional) Specify the maximum number of rules per VFW for this node.

  15. Enter the following information in the Pod Node: Firewall Host C1 page and click Next:

    FieldDescription

    Skip Node?

    (Optional) Select Yes to skip this node if it is not required to create the pod. Default value is No.

    Shareable

    (Optional) Select to make this pod node shareable.

    Device

    Select the device name for this pod node.

    Max VRFs

    (Optional) Specify the maximum number of VRF instances for this pod node.

    Max VFWs

    (Optional) Specify the maximum number of Virtual Firewall (VFW) instances for this pod node.

    Max Rules per VFW

    (Optional) Specify the maximum number of rules per VFW for this node.

  16. Enter the following information in the Pod Node: Firewall Host C2 page and click Next:

    FieldDescription

    Skip Node?

    (Optional) Select Yes to skip this node if it is not required to create the pod. Default value is No.

    Shareable

    (Optional) Select to make this pod node shareable.

    Device

    Select the device name for this pod node.

    Max VRFs

    (Optional) Specify the maximum number of VRF instances for this pod node.

    Max VFWs

    (Optional) Specify the maximum number of Virtual Firewall (VFW) instances for this pod node.

    Max Rules per VFW

    (Optional) Specify the maximum number of rules per VFW for this node.

  17. Enter the following information in the Pod Node: Load Balancer Host 1 page and click Next:

    FieldDescription

    Skip Node?

    (Optional) Select Yes to skip this node if it is not required to create the pod. Default value is No.

    Shareable

    (Optional) Select to make this pod node shareable.

    Device

    Select the device name for this pod node.

    Max VRFs

    (Optional) Specify the maximum number of VRF instances for this pod node.

    Max VLBs

    (Optional) Specify the maximum number of Virtual Load Balancers (VLB) instances for this pod node.

    Max Pools per VLB

    (Optional) Specify the maximum number of pools per VLB for this node.

    Max Entries per Pool

    (Optional) Specify the maximum number entries per pool for this node.

  18. Enter the following information in the Pod Node: Load Balancer Host 2 page and click Next:

    FieldDescription

    Skip Node?

    (Optional) Select Yes to skip this node if it is not required to create the pod. Default value is No.

    Shareable

    (Optional) Select to make this pod node shareable.

    Device

    Select the device name for this pod node.

    Max VRFs

    (Optional) Specify the maximum number of VRF instances for this pod node.

    Max VLBs

    (Optional) Specify the maximum number of VLB instances for this pod node.

    Max Pools per VLB

    (Optional) Specify the maximum number of pools per VLB for this node.

    Max Entries per Pool

    (Optional) Specify the maximum number entries per pool for this node.

  19. Enter the following information in the Pod Node: Access page and click Next:

    FieldDescription

    Shareable

    (Optional) Select to make this pod node shareable.

    Device

    Select the device name for this pod node.

    Hypervisor Context

    Name of either a hypervisor server or hypervisor cluster.

    Max VRFs

    (Optional) Specify the maximum number of VRF instances for this pod node.

    Max Ports

    (Optional) Specify the maximum number of ports for this pod node.

    Max Port Types

    (Optional) Specify the maximum number of port types for this node.

  20. If the Pod Pair: Firewall Fault Host Pair A page appears, enter the following information and click Next:

    FieldDescription

    HOST_MGMT_IP2

    Specify the IP address of SNMP Manager Station 2.

    HOST_MGMT_IP1

    Specify the IP address of SNMP Manager Station 1.

    Note

    Any pod nodes that were skipped in the pod node configuration steps do not appear in the pair creation steps.

  21. If the Pod Pair: Firewall Fault Host Pair B page appears, enter the following information and click Next:
    FieldDescription

    HOST_MGMT_IP2

    Specify the IP address of SNMP Manager Station 2.

    HOST_MGMT_IP1

    Specify the IP address of SNMP Manager Station 1.

    Note

    Any pod nodes that were skipped in the pod node configuration steps do not appear in the pair creation steps.

  22. If the Pod Pair: Firewall Fault Host Pair C page appears, enter the following information and click Next:
    FieldDescription

    HOST_MGMT_IP2

    Specify the IP address of SNMP Manager Station 2.

    HOST_MGMT_IP1

    Specify the IP address of SNMP Manager Station 1.

    Any pod nodes that were skipped in the pod node configuration steps do not appear in the pair creation steps.

  23. If the Pod Pair: Load Balancer Fault Host Pair page appears, enter the following information and click Next:
    FieldDescription

    Active Guest Priority

    (Optional) Specify the Active Guest Priority setting.

    Standby Guest Priority

    (Optional) Specify the Standby Guest Priority setting.

    Fault Id Pool Start Number

    (Optional) Specify the starting number for the fault ID pool.

    Fault Id Pool End Number

    (Optional) Specify the ending number for the fault ID pool.

    Excluded Fault IDs

    (Optional) Comma and/or hypen seperated list of fault IDs which should be excluded from fault ID pool.

    HOST_MGMT_IP2

    Specify the IP address of SNMP Manager Station 2.

    HOST_MGMT_IP1

    Specify the IP address of SNMP Manager Station 1.

    Note

    Any pod nodes that were skipped in the pod node configuration steps do not appear in the pair creation steps.

  24. When the Pod Pair: Agg Pair page appears, no input parameters are required. Click Next to continue.
  25. In the DNS and NIC Information page, enter optional information as shown in the following table:

    Field

    Description

    Primary DNS Server

    Specify the primary DNS server name. This field is required when you specify tags related to DNS.

    Reverse DNS ServerSpecify the reverse DNS server that allows reverse lookup of the IP address. In other words, given the IP address, the reverse DNS can resolve the domain name associated with the IP address. If you specify the value for this field, only PTR records are added, otherwise, the API adds only an A record in the Primary DNS Server.

    Secondary DNS Server

    Specify the secondary DNS server name.

    Primary Domain Suffix for NIC

    Specify the primary domain suffix for NIC segments.

    DNS Domains for NIC

    Specify the domain search order as a comma-separated list.

    Reverse DNS ZoneSpecify the reverse DNS zone where the PTR-record type stores reverse DNS entries. The reverse DNS zone value is specific to the network address from which the PTR entries can be added.
  26. Enter the following information in the Address Pool: Management Addresses 1 page and click Next:

    FieldDescription

    Pool Address

    Specify the IP address and subnet mask for the address pool in CIDR notation.

    Public

    (Optional) Select to make the address pool public.

    Shareable

    (Optional) Select to make the address pool shareable.

    Primary DNS Server

    (Optional) Specify the primary DNS server name. This field is required when you specify tags related to DNS.

    Reverse DNS Server(Optional) Specify the reverse DNS server that allows reverse lookup of the IP address. In other words, given the IP address, the reverse DNS can resolve the domain name associated with the IP address. If you specify the value for this field, only PTR records are added, otherwise, the API adds only an A record in the Primary DNS Server.

    Secondary DNS Server

    (Optional) Specify the secondary DNS server name.

    Gateway Address

    (Optional) Specify the IP address for the gateway to the address pool.

    Primary Domain Suffix for NIC

    (Optional) Specify the primary domain suffix for NIC segments.

    DNS Domains for NIC

    (Optional) Specify the domain search order as a comma-separated list.

    Reverse DNS Zone(Optional) Specify the reverse DNS zone where the PTR-record type stores reverse DNS entries. The reverse DNS zone value is specific to the network address from which the PTR entries can be added.
  27. Enter the following information in the Address Pool: Management Addresses 2 page and click Next:

    FieldDescription

    Pool Address

    Specify the IP address and subnet mask for the address pool in CIDR notation.

    Public

    (Optional) Select to make the address pool public.

    Shareable

    (Optional) Select to make the address pool shareable.

    Primary DNS Server

    (Optional) Specify the primary DNS server name. This field is required when you specify tags related to DNS.

    Reverse DNS Server(Optional) Specify the reverse DNS server that allows reverse lookup of the IP address. In other words, given the IP address, the reverse DNS can resolve the domain name associated with the IP address. If you specify the value for this field, only PTR records are added, otherwise, the API adds only an A record in the Primary DNS Server.

    Secondary DNS Server

    (Optional) Specify the secondary DNS server name.

    Gateway Address

    (Optional) Specify the IP address for the gateway to the address pool.

    Primary Domain Suffix for NIC

    (Optional) Specify the primary domain suffix for NIC segments.

    DNS Domains for NIC

    (Optional) Specify the domain search order as a comma-separated list.

    Reverse DNS Zone(Optional) Specify the reverse DNS zone where the PTR-record type stores reverse DNS entries. The reverse DNS zone value is specific to the network address from which the PTR entries can be added.
  28. Enter the following information in the Address Pool: VM Management Addresses page and click Next:

    FieldDescription

    Pool Address

    Specify the IP address and subnet mask for the address pool in CIDR notation.

    Public

    (Optional) Select to make the address pool public.

    Shareable

    (Optional) Select to make the address pool shareable.

    Primary DNS Server

    (Optional) Specify the primary DNS server name. This field is required when you specify tags related to DNS.

    Reverse DNS Server(Optional) Specify the reverse DNS server that allows reverse lookup of the IP address. In other words, given the IP address, the reverse DNS can resolve the domain name associated with the IP address. If you specify the value for this field, only PTR records are added, otherwise, the API adds only an A record in the Primary DNS Server.

    Secondary DNS Server

    (Optional) Specify the secondary DNS server name.

    Gateway Address

    (Optional) Specify the IP address for the gateway to the address pool.

    Primary Domain Suffix for NIC

    (Optional) Specify the primary domain suffix for NIC segments.

    DNS Domains for NIC

    (Optional) Specify the domain search order as a comma-separated list.

    Reverse DNS Zone(Optional) Specify the reverse DNS zone where the PTR-record type stores reverse DNS entries. The reverse DNS zone value is specific to the network address from which the PTR entries can be added.
  29. Enter the following information in the Address Range: Customer Pools page and click Next:

    FieldDescription

    Range Address

    Specify the IP address and subnet mask for the customer address range pool in CIDR notation.

    Pool Mask

    Specify the subnet mask for the customer address pool.

    Public

    (Optional) Select to make the customer address range pool public.

    Primary DNS Server

    (Optional) Specify the primary DNS server name. This field is required when you specify tags related to DNS.

    Reverse DNS Server(Optional) Specify the reverse DNS server that allows reverse lookup of the IP address. In other words, given the IP address, the reverse DNS can resolve the domain name associated with the IP address. If you specify the value for this field, only PTR records are added, otherwise, the API adds only an A record in the Primary DNS Server.

    Secondary DNS Server

    (Optional) Specify the secondary DNS server name.

    Primary Domain Suffix for NIC

    (Optional) Specify the primary domain suffix for NIC segments.

    DNS Domains for NIC

    (Optional) Specify the domain search order as a comma-separated list.

    Reverse DNS Zone(Optional) Specify the reverse DNS zone where the PTR-record type stores reverse DNS entries. The reverse DNS zone value is specific to the network address from which the PTR entries can be added.
  30. Enter the following information in the Address Range: Link Pools page and click Next:

    FieldDescription

    Range Address

    Specify the IP address and subnet mask for the link address range pool in CIDR notation.

    Pool Mask

    Specify the subnet mask for the link address pool.

    Public

    (Optional) Select to make the link address range pool public.

    Primary DNS Server

    (Optional) Specify the primary DNS server name. This field is required when you specify tags related to DNS.

    Reverse DNS Server(Optional) Specify the reverse DNS server that allows reverse lookup of the IP address. In other words, given the IP address, the reverse DNS can resolve the domain name associated with the IP address. If you specify the value for this field, only PTR records are added, otherwise, the API adds only an A record in the Primary DNS Server.

    Secondary DNS Server

    (Optional) Specify the secondary DNS server name.

    Primary Domain Suffix for NIC

    (Optional) Specify the primary domain suffix for NIC segments.

    DNS Domains for NIC

    (Optional) Specify the domain search order as a comma-separated list.

    Reverse DNS Zone(Optional) Specify the reverse DNS zone where the PTR-record type stores reverse DNS entries. The reverse DNS zone value is specific to the network address from which the PTR entries can be added.
  31. Enter the following information in the Address Range: Services Pools page and click Next:

    FieldDescription

    Range Address

    Specify the IP address and subnet mask for the services address range pool in CIDR notation.

    Pool Mask

    Specify the subnet mask for the services address pool.

    Public

    (Optional) Select to make the services address range pool public.

    Primary DNS Server

    (Optional) Specify the primary DNS server name. This field is required when you specify tags related to DNS.

    Reverse DNS Server(Optional) Specify the reverse DNS server that allows reverse lookup of the IP address. In other words, given the IP address, the reverse DNS can resolve the domain name associated with the IP address. If you specify the value for this field, only PTR records are added, otherwise, the API adds only an A record in the Primary DNS Server.

    Secondary DNS Server

    (Optional) Specify the secondary DNS server name.

    Primary Domain Suffix for NIC

    (Optional) Specify the primary domain suffix for NIC segments.

    DNS Domains for NIC

    Specify the domain search order as a comma-separated list.

    Reverse DNS Zone(Optional) Specify the reverse DNS zone where the PTR-record type stores reverse DNS entries. The reverse DNS zone value is specific to the network address from which the PTR entries can be added.
  32. Enter the following information in the Vlan Pool: Customer Vlans page and click Next:

    FieldDescription

    Shareable

    (Optional) Select to make the vlan pool shareable.

    VLAN Start Number

    Enter the starting Customer VLAN number for this range.

    VLAN End Number

    Enter the ending Customer VLAN number for this range.

    Excluded VLANs

    (Optional) Specify any Customer VLANs that should be excluded from this range. Enter the VLAN numbers as a comma-separated list.

  33. Enter the following information in the Vlan Pool: Infrastructure Vlans page and click Next:

    FieldDescription

    Shareable

    (Optional) Select to make the vlan pool shareable.

    VLAN Start Number

    Enter the starting Infrastructure VLAN number for this range.

    VLAN End Number

    Enter the ending Infrastructure VLAN number for this range.

    Excluded VLANs

    (Optional) Specify any Infrastructure VLANs that should be excluded from this range. Enter the VLAN numbers as a comma-separated list.

  34. Enter the following information in the Vlan Pool: Management Vlans page and click Next:

    FieldDescription

    Shareable

    (Optional) Select to make the vlan pool shareable.

    VLAN Start Number

    Enter the starting Management VLAN number for this range.

    VLAN End Number

    Enter the ending Management VLAN number for this range.

    Excluded VLANs

    (Optional) Specify any Management VLANs that should be excluded from this range. Enter the VLAN numbers as a comma-separated list.

  35. Enter the following information in the Vlan: Management VLAN1 page and click Next:

    FieldDescription

    Vlan Number

    Specify the VLAN number.

  36. Enter the following information in the Vlan: Management VLAN2 page and click Next:

    FieldDescription

    Vlan Number

    Specify the VLAN number.

  37. Enter the following information in the Vlan: VM Management VLAN page and click Next:

    FieldDescription

    Vlan Number

    Specify the VLAN number.

  38. In the Pod Parameters page click Submit. On successful pod creation, this pod is displayed in the Pods list page (Network > Virtual Data Center > Pods).

Was this page helpful? Yes No Submitting... Thank you

Comments