Руководство Пользователя для Cisco Cisco Network Services Manager for Intelligent Automation for Cloud

The templates must meet the following requirements:

At least one hypervisor service profile template for each vCenter cluster with the same quantity and 
configuration of vNICs as on other hosts in the same cluster. The native VLAN for the first vNIC 
should be set to the Management VLAN for that vCenter.

This is only required for ESXi.

At least one service profile template for physical server provisioning

A local boot policy assigned to the physical server service profile template which is set to boot to 
local disk 

A boot policy named PXEBoot which is configured to boot from the network.

This name is mandatory.

Provisioning templates are prepared according to Cisco Server Provisioner product documentation. 
(See the 

 on LinMin.com.)

UCS blades for provisioning VMware ESXi hypervisor hosts have at least one local drive.

This is only needed when the ESCi Provisioning option is enabled in 

.

For Cisco IAC, vCenter object names cannot contain forward slashes. Cisco IAC uses forward 
slashes as delimiters in object paths and parses vCenter paths by display name. Forward slashes in 
vCenter object names break the parsing process. If any of your vCenter object names contains forward 
slashes, please rename the files before you specify a vCenter path.

In Cisco IAC, commissioning a new ESXi host is performed when moving a blade in the Maintenance 
pool to the Virtual pool. The orchestration process involves provisioning (installing) ESXi on to a blade, 
adding it to the vSphere infrastructure, copying the configuration from one of the existing hosts in a 
cluster and applying it to the new host using VMware host profiles and exiting Host Maintenance mode. 

Provisioning of the ESXi Hypervisor OS always uses the first local drive installed in the blade. For Cisco 
IAC, only local installs of the ESXi Hypervisor OS are supported.

The following VMware software should be installed:

vSphere Powershell CLI on the TEO server to support the activities for adding a new ESXi host to 
a cluster.