This topic describes how to edit a pod, what fields can be edited, and how to modify those fields.
Pods can be edited in BMC Network Automation after the pod is created. You can remove unused pod nodes and pairs, edit the ports for physical switches, and add or edit parameters, and balanced parameters for pod, pod nodes, and pod pairs. This allows you to scale the pod when resource pools are exhausted or new node and pairs need to be added.
Perform the following steps to edit a pod:
Primary DNS Server
Specify the primary DNS server name.
|Reverse DNS Server||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. This field is required if you want to register the VM to the DNS server by using BMC Network Automation.
DNS Domains for NIC
Specify the domain search order as a comma-separated list.
|Reverse DNS Zone|
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 188.8.131.52/24, the reverse DNS zone is 10.168.198.in-addr.arpa.
Click Save, and then Close.
DNS information for an existing container is not updated when you update the DNS Information in the pod.
Click the Deleteicon in the Actions field to delete DNS information from the pod.
Click a hyper-linked value in the Name column for an address pool.
In the Add Chained Address Pool dialog box, enter the pool address and optionally, the gateway address for the new pool.
In the DNS Info column, click the
If the DNS information is specified during pod creation or via Pod Details: DNS Information, it is prepopulated when you add an address pool.
To edit the DNS information for an address pool, click a hyperlinked value in the DNS Info column for that address pool, and then click Save.
If a pod address pool has IP addresses that are acquired and DNS registered, the following warning message is displayed:
You are attempting to update the existing DNS information for this address pool in which some IP addresses might already be acquired and DNS registered. In the Pod view, under the Address Pools section, click the View icon in the Actions column and review the information before proceeding.
Do you wish to overwrite the existing DNS information?
In the Add Chained Address Range dialog box, enter the range address and range mask for the new address range.
In the DNS Info column, click the
If the DNS information is specified during pod creation or via Pod Details: DNS Information, it is prepopulated when you add an address range.
To edit the DNS information for an address range, click a hyperlinked value in the DNS Info column for that address range and then click Save.
NIC Segment Name
Enter a name for the new network segment where virtual or physical server NICs are to be provisioned.
Enter the name of the BMC Cloud Lifecycle Management "network" to which this segment belongs.
Address Pool Name
Select the address pool which will be used to acquire server NIC addresses.
|VLAN Name||Select the VLAN to which NICs will be connected when they are provisioned to this segment.|
|Tag||Specify a tag that can be used to annotate the container in miscellaneous ways, which clients might find useful.|
|Customer||Select whether this segment carries customer (non-management) traffic.|
|Management||Select whether this segment carries management traffic.|
Click a hyper-linked value in the Name column for a VLAN pool.
In the Add Chained VLAN Pool dialog box, enter the VLAN pool start and end numbers and optionally, a list of comma and/or hyphen-separated excluded VLANs for the new VLAN pool.
In the Add Node dialog box, enter the information for the new node.
The following table describes the information that you need to add in the dialog box to add a new node:
Enter the name of the new node.
Specify the role for the new node.
Select this option to allow the new node's device to participate in multiple pods.
Select the type for the new node:
|Realm||Select the realm to which the node should belong.|
Click the button, and then select a device from the list. You can click a device name or type a name.
(Optional) Enter the maximum number of virtual routing and forwarding (VRFs) allowed for the new pod node.
(Optional) Enter the parameters for the new node. Click the icon to add a new row to enter information for additional parameters.
(Optional) Enter a comma-separated list of balanced parameters for the new node.
|Max Ports||(Only for Hypervisor switch nodes) 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. VMware refers to a virtual port type as a port group and Cisco calls it a port profile. 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.|
(Only for Hypervisor switch nodes) Enter the port type for the new node.
(Only for physical switch nodes) Enter the ports for the new node as a comma-separated list.
(Only for firewall nodes) Enter the maximum number of virtual firewalls (VFWs) allowed on the new node.
|Guest Device||(Only for firewall and load balancer nodes) Click the button, and then select the name of the device to create or reuse to represent the guest context.|
Max Rules per VFW
(Only for firewall nodes) Enter the maximum number of rules per VFW.
(Only for load balancer nodes) Enter the maximum number of virtual load balancers (VLBs) allowed on the new node.
Max Pools per VLB
(Only for load balancer nodes) Enter the maximum number of pools per VLB.
Max Entries per Pool
(Only for load balancer nodes) Enter the maximum number of entries per pool.
In the Add Pair dialog box, enter the following information for the new pair.
The following table describes the information that you need to add to the pop-up to add a new pair.
Enter the name of the new pair.
Select the type for the new pair:
Select the nodes for the new pair.
(Optional) Enter the parameters for the new pair. Click the icon to add a new row to enter information for additional parameters.
(Optional) Enter a comma-separated list of balanced parameters for the new pair.
Community 1/2 VLAN
(Only for firewall pairs) Enter the Community 1 and 2 VLAN names for the new pair.
Fault ID Pool Information
(Only for load balancer pairs) Enter the fault ID pool information for the new pair.
(Only for load balancer pairs) Enter the active and standby priority values that will be assigned to the active and standby VLBs in the fault tolerant pair.
In the Add Parameter/Balanced Parameter dialog box, add new parameters or edit existing parameters.
The following table describes the information that you need to add to the Add Parameter/Balanced Parameter dialog box:
To modify a parameter, enter the name in the first box, and enter the new value or optional description in the second and third boxes.
The value for balanced parameters is a comma-separated list.
You can edit the parameters and balanced parameters of pod nodes and pairs in the same fashion by clicking the Edit link next to the Parameters label under the specific node or pair.
When you double-click the value in the maximum value field, the value becomes a text field with Save and Cancel buttons.
Change the value in the text field.
Click Save to update the value in the maximum value field.
Even if you update the port names for a physical or hypervisor switch in the BMC Network Automation GUI, synchronizing the pods does not update these changes in the BMC Cloud Lifecycle Management console unless the switch is re-added.
If BMC Cloud Lifecycle Management does not use a switch to provision any resource, in other words, if it has no physical server or virtual machine and network containers provisioned for it, you can change the port names for a physical or hypervisor switch in a pod from the BMC Cloud Lifecycle Management Administration console by performing the following steps:
Click Synchronize Pod to synchronize the network pod with any changes to the pod.
Pod resynchronization fails if the switch is referenced by an onboarded physical server or a resource, and either has a server provisioned or is the only switch for the onboarded resource. You must offboard the resource from BMC Cloud Lifecycle Management before you resynchronize the pod.