The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter contains the following sections:
Step 1 | Add the
Cisco Unified Fabric Automation
organization account through
, as shown in
Creating a Cisco Unified Fabric Automation Organization Account.
Make sure you specify a valid range of segments IDs to be used by Cisco UCS Director. To update the SegmentID Range, choose DCNM Accounts>Fabric SegmentID Range Management and highlight the desired DCNM account. The segment id range Update button is available when the DCNM account is highlighted. |
Step 2 | Add a vCenter cloud account through Administration > Virtual Accounts > Add ). |
Step 3 | If used, add the Cisco Nexus 1000V account (Administration >Physical Accounts > Managed Network Elements > Add Network Element). |
Step 4 | Check the vCenter cloud inventory under vCenter and verify that you can see the data. It may take a few minutes after the vCenter is added for the inventory to appear. |
Step 5 | Create several vDCs. You also have to create system, compute, storage, and network policies (refer to the base Cisco UCS Director, Release 4.1 documentation). |
Step 6 | Choose Physical > Network. |
Step 7 | In the left pane, hoose Multi-domain Managers > DCNM Accounts and click Fabric vDC Switch Association Policy. Enable vDC switches for a particular Fabric organization account.
With the above steps completed, you can now perform the basic administrative Fabric organization tasks such as:
|
Cisco UCS Director automatically discovers all existing virtual machines (VMs) and images in the newly added cloud account. Typically, the discovery process takes about five minutes. You can add VMware clouds and PowerShell agents.
Note | This step is optional if you are using a Cisco Nexus 1000V. |
You must have a Cisco DCNM account and a vCenter account. You must have access to a Cisco Nexus 1000V switch.
Step 1 | Choose . | ||||||||||||||||||
Step 2 | Click Managed Network Elements. | ||||||||||||||||||
Step 3 | Click Add Network Element and complete the following fields:
| ||||||||||||||||||
Step 4 | Click Submit. |
Make sure you specify a valid range of segments IDs to be used by Cisco UCS Director. To update the SegmentID Range, choose DCNM Accounts>Fabric SegmentID Range Management and highlight the desired DCNM account. The segment id range Update button is available when the DCNM account is highlighted.
The Segment ID Range Specified in the creation of the DCNM Account should be different from the ranges present in the L2 Segment ID Range for DCNM Version 7.1(x). Earlier DCNM versions can be given any valid range.
Note | Cisco Fabric Organization networks are not tied to any specific pod. |
Step 1 | Choose . | ||||||||||||||||||||||||
Step 2 | Click Multi-Domain Managers. | ||||||||||||||||||||||||
Step 3 | Click (+) Add. | ||||||||||||||||||||||||
Step 4 | On the Add Account screen, choose DCNM from the drop-down list to create an account for use in Digital Fabric Automation networks.
PNSC is not used in UCSD unless required for specific items, such as VSG deployment. | ||||||||||||||||||||||||
Step 5 | Click Submit | ||||||||||||||||||||||||
Step 6 | On the Multi-Domain Manager Account screen, complete the following fields. All other field are information only.
| ||||||||||||||||||||||||
Step 7 | Click Submit. | ||||||||||||||||||||||||
Step 8 | Choose the newly created account. | ||||||||||||||||||||||||
Step 9 | Click Test Connection to verify that the account is operational. |
Note | You can also use workflow tasks to create a Cisco Unified Fabric Automation organization, partition, or network. |
Step 1 | Choose . | ||||||||||||
Step 2 | In the left pane, click the Multi-domain Manager entry. | ||||||||||||
Step 3 | Double-click the
DCNM
Accounts entry.
Along with the double-click, you can select the arrow button, double-click on the DCNM Account created, and see the Fabric Organization screen. | ||||||||||||
Step 4 | Click Fabric Organization. | ||||||||||||
Step 5 | Click Create Organization. | ||||||||||||
Step 6 | On the Create Fabric Organization screen, complete the following fields:
| ||||||||||||
Step 7 | Click Add. |
The DFA Orchestrator ID is one of the parameters that is used in the creation of a DFA organization by Cisco UCS Director. By default, this field holds the following value:
UCSD -<UCSD IP Address>
To change the DFA Orchestrator value, enter a new IP address.
Create a Fabric vDC, Fabric account and a Fabric switch.
Note | You can also associate Fabric vDC switch association through an action task (Physical > Network > DCNM Accounts > Fabric VDC Switch Association Policy > Add). |
Step 1 | Choose Policies > Orchestration. | ||||||||||||||
Step 2 | In the Orchestration pane, click Workflows. | ||||||||||||||
Step 3 | On the left pane of the WorkFlows screen, choose the workflow folder and click the arrow next to the folder to show the workflows. | ||||||||||||||
Step 4 | Double-click the Create VDC Fabric Switch Association workflow. Workflow Designer appears. | ||||||||||||||
Step 5 | Click the Edit Workflow Properties button. | ||||||||||||||
Step 6 | In the
Edit
Workflow Details pane, complete the following fields:
| ||||||||||||||
Step 7 | In the Modify User Inputs pane, click on the (+) Add button to locate and add a Fabric Account, Fabric Switch, and a Fabric vDC. | ||||||||||||||
Step 8 | Click Submit. | ||||||||||||||
Step 9 | Click the Execute Now button. | ||||||||||||||
Step 10 | Examine the Submit Workflow screen to confirm the proper inputs were selected. | ||||||||||||||
Step 11 | Click Submit. |
You can create multiple (Level 2 network) fabric partitions. Each network can have associated network pools.
Step 1 | Choose . | ||||||||||||||||||||||||||||
Step 2 | In the left pane, click the Multi-domain Manager entry. | ||||||||||||||||||||||||||||
Step 3 | Double-click the
DCNM
Accounts entry.
Along with the double-click, you can select the arrow button, double-click on the DCNM Account created, and see the Fabric Partition screen. | ||||||||||||||||||||||||||||
Step 4 | Click Fabric Partition. | ||||||||||||||||||||||||||||
Step 5 | Click Create Partition. | ||||||||||||||||||||||||||||
Step 6 | On the Create Partition screen, complete the following fields:
| ||||||||||||||||||||||||||||
Step 7 | Click Add. |
Each fabric network can have associated network pools.
Step 1 | Choose . | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 2 | In the left pane, click the Multi-domain Manager entry. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 3 | Double-click the
DCNM
Accounts entry.
Along with the double-click, you can select the arrow button, double-click on the DCNM Account created, and see the Fabric Network screen. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 4 | Click Fabric Network. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 5 | Click Create Network. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 6 | On the Create Fabric Network screen, complete the following fields:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 7 | Click Add. |
Each network can have an associated segment ID range. Each network has an account ID. Cisco Unified Fabric Automation assigns a segment ID range to one Orchestrator. OpenStack can also talk to Cisco Data Center Network Manager (DCNM). When Cisco UCS Director Orchestrator creates a network, it uses the segments listed in these segment ID ranges.
Step 1 | Choose . |
Step 2 | In the left pane, click the Multi-domain Manager entry. |
Step 3 | Double-click the
DCNM
Accounts entry.
Along with the double-click, you can select the arrow button, double-click on the DCNM Account created, and see the Fabric SegmentID Range Management screen. |
Step 4 | Click Fabric SegmentID Range Management. The Account Name, Orchestrator Name, and SegmentID Range are displayed. |
This view allows you to see who is using which network ID, segment pool, segment ID, and so on.
Step 1 | Choose . |
Step 2 | Click the Multi-domain Manager entry in the left-hand column. |
Step 3 | Double-click the
DCNM
Accounts entry.
Along with the double-click, you can select the arrow button, double-click on the DCNM Account created, and see the Fabric Network Segment Usage screen. |
Step 4 | Click Fabric Network Segment Usage. The details of segment usage are displayed. |
Note | Do not make the network available to all vCenters. You must enable the Cisco Cisco Unified Fabric Automation on a particular switch. |
Create a partition and ensure that you can access Cisco Prime DCNM and a vCenter account. You also need information about the Cisco Nexus 1000V switch to be used with this network. Whenever you create a network, you can create multiple profiles. See the Profile Name drop-down list to choose a profile and how it will be used (for example, the defaultNetworkIpv4EfProfile selection). The available profiles are available through Cisco DCNM.
Step 1 | Choose . | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 2 | In the left pane, click the Multi-domain Manager entry. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 3 | Double-click the DCNM Accounts entry. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 4 | Click Fabric Partition. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 5 | Double-click on a partition. The Fabric Network screen appears. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 6 | Click Create Network. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 7 | On the Create Fabric Network screen, complete the following fields:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 8 | Click Add. Cisco UCS Director creates a port group on the vSwitch. Once the port group is available, you can create a VM. Any VM can use this port group. The Cisco Cisco Unified Fabric Automation network allows you to create network segments dynamically, which makes them visible to the dvSwitches and Cisco Nexus 1000V switches. |
Each Cisco Unified Fabric Automation network can have associated network pools. Creating a Cisco Unified Fabric Automation network using vSwitches and dvSwitches are very similar. However, vSwitches can be mapped to one network adapter or to multiple network adapters. vSwitches that have no associated network adapters can also be implemented as well.
Step 1 | Choose . | ||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 2 | In the left pane, click the Multi-domain Managers entry. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 3 | Click the DCNM Accounts entry. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 4 | Click Fabric Network. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 5 | Click Create Network. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 6 | On the Create Fabric Network screen, complete the following fields:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 7 | Click Add. |
Each Fabric network can have associated network pools. Creating a Fabric network using vSwitches and dvSwitches are very similar. A dvSwitch acts like a global switch, enabling administrators to associate a single switch with all ESX or ESXi hosts in a datacenter, rather than configure a vSwitch for each individual host.
Step 1 | Choose . | ||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 2 | In the left pane, click the Multi-domain Managers entry. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 3 | Click the DCNM Accounts entry. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 4 | Click Fabric Network. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 5 | Click Create Network. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 6 | On the Create Fabric Network screen, complete the following fields:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 7 | Click Add. |
A Cisco DFA is in a network level infrastructure. It lets you create network segments dynamically and then you make the network visible to the vSwitch, dvSwitch and Cisco Nexus 1000 switches once the port group is available. Any VM that uses this port group becomes connected to the Cisco Cisco Unified Fabric Automation network. Attaching a port group to a VM is the last step in the configuration process.
Create a VM.
Step 1 | Choose . | ||||||
Step 2 | In the left-hand pane, choose a vCenter. | ||||||
Step 3 | Click Port Groups. | ||||||
Step 4 | Choose a port group. | ||||||
Step 5 | Click Assign Group. | ||||||
Step 6 | On the Select Group screen, complete the following fields:
| ||||||
Step 7 | Click Submit. |
Step 1 | Choose . | ||||||||||||||||||||
Step 2 | On the Network page, click VMware Network Policy. | ||||||||||||||||||||
Step 3 | Click Add. | ||||||||||||||||||||
Step 4 | On the Network Policy Information screen, complete the following fields:
| ||||||||||||||||||||
Step 5 | Click Add in the VM Networks section to add and configure multiple vNICs. These vNICs are applicable to the VM that is provisioned using this policy.
| ||||||||||||||||||||
Step 6 | On the Add Entry to VM Networks screen, complete the following fields:
| ||||||||||||||||||||
Step 7 | Click Add (+) in the Port Groups section. The Add Entry to Port Groups screen appears. | ||||||||||||||||||||
Step 8 | Click Select to choose the port group name. | ||||||||||||||||||||
Step 9 | From the
Select
IP Address Type drop-down field, choose
DHCP (default) or
Static.
| ||||||||||||||||||||
Step 10 | Check IPv6 to configure IPv6.
You must configure the identical fields that you specified for IPv4 configuration. | ||||||||||||||||||||
Step 11 | Click Submit. | ||||||||||||||||||||
Step 12 | Click Submit on the Add Entry to VM Networks screen. | ||||||||||||||||||||
Step 13 | Click Submit on the Network Policy Information screen. |
Create a vDC, Fabric account and a Fabric switch.
Step 1 | Choose . | ||||||||||||||
Step 2 | In the Orchestration pane, click Workflows. | ||||||||||||||
Step 3 | On the left pane of the WorkFlows section, choose the workflow folder and click the arrow next to the folder to show the workflows. | ||||||||||||||
Step 4 | Double-click the
FabricPortGroupSelector task.
| ||||||||||||||
Step 5 | On the Edit Task (FabricPortGroupSelector) screen, complete the following fields:
| ||||||||||||||
Step 6 | Click Next. | ||||||||||||||
Step 7 | On the User Input Mapping screen, complete the following fields:
| ||||||||||||||
Step 8 | Click Next. | ||||||||||||||
Step 9 | On the Task Inputs screen, complete the following fields.
| ||||||||||||||
Step 10 | Click Submit. | ||||||||||||||
Step 11 | Click Execute Now. | ||||||||||||||
Step 12 | Examine the Submit Workflow screen to confirm the proper inputs were selected. | ||||||||||||||
Step 13 | Click Submit. |
Cisco UCS Director supports virtual machine (VM) provisioning of multiple disks from a template. You can configure VM disk provisioning on a preferred single datastore or multiple datastores in a Cisco Cisco Unified Fabric Automation network. You can also configure individual disk policies for each additional disk in a template.
Cisco UCS Director classifies the disks into the following categories:
Note | The disk categories that are defined by Cisco UCS Director are for disk labeling only. For specific information on VM provisioning refer to the UCS Director Administration Guide. |
An application container is a collection of virtual machines (VMs) with an internal private network that is based on rules specified by an administrator. The application container can have one or more VMs that are (optionally) guarded by a fencing gateway (for example, a Cisco Virtual Secure Gateway) to the external/public cloud. In order to create an application container you must create a system, network, and computing policies. For complete information on creating application containers see the Cisco UCS Director Application Containers Guide.
Virtual account (cloud)
Network configuration
VM configuration
Container security
Select Network, Storage, Compute, and Cost Model policies
Select the gateway policy, if Gateway Required check box is enabled (optional)
Options for service end users
Note | For more information regarding the container templates and Virtual Secure Gateways (VSGs), see Creating an Application Template for a VSG. |
Step 1 | Choose . | ||||||||||||||||||||||||||||||||||||
Step 2 | Click Virtual Infrastructure Policies. | ||||||||||||||||||||||||||||||||||||
Step 3 | Click Add Policy. | ||||||||||||||||||||||||||||||||||||
Step 4 | In the
Virtual
Infrastructure Policy Specification pane, complete the following
fields:
| ||||||||||||||||||||||||||||||||||||
Step 5 | Click Next. | ||||||||||||||||||||||||||||||||||||
Step 6 | In the
Virtual
Infrastructure Policy - Fabric Information pane, complete the
following fields:
| ||||||||||||||||||||||||||||||||||||
Step 7 | Click Next. | ||||||||||||||||||||||||||||||||||||
Step 8 | In the
Virtual
Infrastructure Policy - Fencing Gateway Information pane, complete
the following fields:
| ||||||||||||||||||||||||||||||||||||
Step 9 | Click Submit. |
Note | For information on creating container templates for use with a VSG, see Creating an Application Template for a VSG. |
Note | This procedure does not create an updating template. If you change templates, it is applied only to the newly created containers from that template. With this template you can create application containers for use in a variety of networks (including Fabric Networks). |
Creating an application container policy.
Step 1 | Choose . | ||||||||||||||||||||||||||||
Step 2 | Click Application Container Templates. | ||||||||||||||||||||||||||||
Step 3 | Click
Add
Template. The
Application Container Template screen appears.
Complete the following fields:
| ||||||||||||||||||||||||||||
Step 4 | Click Next. | ||||||||||||||||||||||||||||
Step 5 | The Application
Container Template - Select a Virtual infrastructure policy screen appears.
Complete the following selection:
| ||||||||||||||||||||||||||||
Step 6 | Click Next. | ||||||||||||||||||||||||||||
Step 7 | Click (+) to add a new Fabric Network entry. | ||||||||||||||||||||||||||||
Step 8 | In the
Add Entry
to Fabric Networks screen, complete the following fields:
| ||||||||||||||||||||||||||||
Step 9 | Click Next. The
Application Container: Template - Internal Networks
screen appears.
You can add and configure multiple networks for a container. These networks are applicable to the VM that is provisioned using this template. | ||||||||||||||||||||||||||||
Step 10 | Click the (+) Add icon to add a network. The Add Entry to Networks screen appears. Complete the following fields:
| ||||||||||||||||||||||||||||
Step 11 | Click
Submit.
Next, you can add and configure the VM that will be provisioned in the application container. | ||||||||||||||||||||||||||||
Step 12 | Click OK. | ||||||||||||||||||||||||||||
Step 13 | Click the Add (+) icon to add a VM. The Add Entry to Virtual Machines screen appears. Complete the following fields:
| ||||||||||||||||||||||||||||
Step 14 | (Optional)Click the
Add
(+) icon to add a new (multiple) VM network interface. Complete the
following fields:
| ||||||||||||||||||||||||||||
Step 15 | Click Next. The Application Container: Template - External Gateway Security Configuration screen appears. You can specify the security configuration components such as port mapping and outbound access control lists (ACLs). | ||||||||||||||||||||||||||||
Step 16 | Click the
Add
(+) icon to add a port mapping. Complete the following fields:
| ||||||||||||||||||||||||||||
Step 17 | Click Submit. The Add Entry to Outbound ACLs screen appears. Complete the following fields:
| ||||||||||||||||||||||||||||
Step 18 | Click Next. | ||||||||||||||||||||||||||||
Step 19 | Click Next. The Application Container
Template - Deployment Policies screen appears.
You must select the compute, storage, network, system policy, and cost model required for VM provisioning. A policy is a group of rules that determine where and how a new VM is to be provisioned within an application container (based on the availability of system resources).
| ||||||||||||||||||||||||||||
Step 20 | Click Next. The
Application Container: Template - Options screen
appears.
In this page, you can select options to enable or disable certain privileges to the self-service end user. Complete the following fields:
| ||||||||||||||||||||||||||||
Step 21 | Click
Next. The
Application Container: Template - Setup Workflows
screen appears. Complete the following field:
| ||||||||||||||||||||||||||||
Step 22 | Click Next to complete the creation of the application container template and review the Summary pane. | ||||||||||||||||||||||||||||
Step 23 | Click Submit. |
See the Custom Workflow for Application Containers information on customizing certain aspects of a template.
Note | For more information about using the orchestration to run workflows, see the Cisco UCS Director Orchestration Guide for this release. |
Note | You cannot create an APIC application container by running a workflow directly. For information on creating the APIC application containers, see APIC Application Container Creation Process. |
If you use a workflow to create an application container template, you must perform some manual steps. There are two scenarios that you do encounter:
Gateway Type: CISCO ASA—If the gateway type is CISCO ASA for the container, you must specifically choose Application Container with ASA Gateway from the list of available workflows. You can search for the workflow and check its check box in order to select it.
Distributed Virtual Portgroups—If you choose the Distributed Virtual Portgroup in the network policy that is associated with the container, then you must perform the following steps manually:
Choose Virtual Network Type and enter its name as required in a workflow associated with the container.
Choose a specific workflow. This type of workflow depends on which gateway type was associated with the container. For a Linux gateway, choose Application Container Setup workflow. For a CISCO ASA gateway type, choose the Application Container with ASA Gateway.
Edit or clone the required workflow by going to the Cisco UCS Director Orchestrator application and editing the workflow on the Workflow Designer page.
In the workflow window, double-click the Allocate Container VM Resources task.
Choose the required virtual network type (either Distributed Virtual Portgroup or Distributed Virtual Portgroup N1K).
Specify the primary DVSwitch and alternate DVSwitch names.
Click Save to save the workflow.
Step 1 | Choose . | ||||||||||||||||||||||||||||||||||||
Step 2 | On the Application Containers page, click Application Container Templates. | ||||||||||||||||||||||||||||||||||||
Step 3 | Click Add Template. The Add Application Container Template page appears. Complete the following fields:
| ||||||||||||||||||||||||||||||||||||
Step 4 | Click Next. The Application Container Template - Select a Virtual Infrastructure policy screen appears. In this screen, you choose the cloud on which the application container is deployed. Complete the following field:
| ||||||||||||||||||||||||||||||||||||
Step 5 | Click Next. The Application Container: Template - Internal Networks screen appears.
| ||||||||||||||||||||||||||||||||||||
Step 6 | Click Add (+) icon to add a network. The Add Entry to Networks screen appears. Complete the following fields:
| ||||||||||||||||||||||||||||||||||||
Step 7 | Click
Submit.
Next, you can add and configure the gateway VM that will be provisioned in the application container. | ||||||||||||||||||||||||||||||||||||
Step 8 | Click OK. | ||||||||||||||||||||||||||||||||||||
Step 9 | Click Next. The Application Conatiner Template - VMs screen appears. | ||||||||||||||||||||||||||||||||||||
Step 10 | Click Add (+) to add a VM. Complete the following fields:
| ||||||||||||||||||||||||||||||||||||
Step 11 | (Optional)Click
Add
(+) to add a new (multiple) VM network interface. Complete the
following fields:
| ||||||||||||||||||||||||||||||||||||
Step 12 | Click Next. | ||||||||||||||||||||||||||||||||||||
Step 13 | Click Ok. The Application Container Template - External Gateway Security Configuration screen appears. You can specify the security configuration components, such as port mapping and outbound access control lists (ACLs). | ||||||||||||||||||||||||||||||||||||
Step 14 | Click Add (+) to add a port mapping. Complete the following fields:
| ||||||||||||||||||||||||||||||||||||
Step 15 | Click Submit. | ||||||||||||||||||||||||||||||||||||
Step 16 | Click OK. | ||||||||||||||||||||||||||||||||||||
Step 17 | Click Add (+) icon to add an Outbound ACL, in the Application Container Template - External Gateway Security Configuration screen. Complete the following fields:
| ||||||||||||||||||||||||||||||||||||
Step 18 | Click Submit. | ||||||||||||||||||||||||||||||||||||
Step 19 | Click OK. | ||||||||||||||||||||||||||||||||||||
Step 20 | Click Next. | ||||||||||||||||||||||||||||||||||||
Step 21 | On the Application Container Template - Deployment Policies screen, complete the following fields:
| ||||||||||||||||||||||||||||||||||||
Step 22 | Click Next. | ||||||||||||||||||||||||||||||||||||
Step 23 | On the Application Container Template - Options screen, complete the following fields:
| ||||||||||||||||||||||||||||||||||||
Step 24 | Click Next. | ||||||||||||||||||||||||||||||||||||
Step 25 | Choose a workflow to setup the container. | ||||||||||||||||||||||||||||||||||||
Step 26 | Expand the workflow list and select a workflow (for example, Workflow Id 431 Fenced Container Setup - VSG).
| ||||||||||||||||||||||||||||||||||||
Step 27 | Click Select. | ||||||||||||||||||||||||||||||||||||
Step 28 | Click Submit. |
Actions available to apply to a container are context-sensitive. You can use the action icons at the top of the Application Containers page or the More Actions drop-down list to perform these actions.
Step 1 | Choose . | ||
Step 2 | On the Application Containers page, click Application Containers. | ||
Step 3 | Choose a container to display all of the available actions.
|
Note | You cannot add VMs to the container through the Add VMs to Container workflow. You can add VMs only by clicking Add VMs or by using the API. |
Step 1 | Choose . | ||||||||||||||||||||||||||||||||||
Step 2 | On the Application Containers page, click Application Containers. | ||||||||||||||||||||||||||||||||||
Step 3 | Choose an application container. | ||||||||||||||||||||||||||||||||||
Step 4 | From the More Actions drop-down list, choose Add VMs. | ||||||||||||||||||||||||||||||||||
Step 5 | On the Add VMs screen, expand the virtual machines list and click Add.
Define the virtual machine in one of the following ways:
| ||||||||||||||||||||||||||||||||||
Step 6 | On the Add Entry to Virtual Machines screen, leave the Use Predefined Template check box unchecked and complete the following fields:
Skip to Step 8. | ||||||||||||||||||||||||||||||||||
Step 7 | On the Add Entry to Virtual Machines screen, check the Use Predefined Template check box and complete the following fields:
| ||||||||||||||||||||||||||||||||||
Step 8 | Click Submit. | ||||||||||||||||||||||||||||||||||
Step 9 | To add more VMs, repeat this procedure starting with Step 5. | ||||||||||||||||||||||||||||||||||
Step 10 | After you finish adding VMs, on the Add VMs screen, click Submit. |
You must enable proper console access rights on individual VMs that you want to access using VNC. See Enabling VNC Console Access.
Step 1 | Choose . | ||
Step 2 | On the Application Containers page, click Application Containers. | ||
Step 3 | Choose an application container. | ||
Step 4 | From the More Actions drop-down list, choose Open Console. | ||
Step 5 | On the Access VM Console screen, from the Select VM drop-down list, choose a VM. | ||
Step 6 | Click Submit. A console of the selected VM opens in a new browser window.
|