Bare Metal Provisioning to a Cisco UCS Blade

For bare metal provisioning to a Cisco UCS blade, you can use any of the following methods in the CA Server Automation user interface:

You also can use either of the following command-line provisioning methods:

Consider the following information to decide which method to use:

Cisco UCS blade provisioning can take significant time due to the blade power cycle and the time required to associate the blade with a specific service profile.
If you are using an RSI or ITCM provisioning method, you must ensure that the service profile is already associated to the blade before running the operation.
For ITCM deployment, you must retrieve the MAC address from the service profile to be used for PXE boot. After the provisioning job is submitted to CA ITCM, you must run blade powercycle from the CA Server Automation user interface.
For physical systems, RSI bare metal provisioning requires that both the network and the target system are configured for Wake-On-LAN to avoid manual intervention to boot the target system during deployment. Unless network routers are configured across subnets to allow directed broadcasts, Wake-On-LAN only works for systems that are in the same subnet as the CA Server Automation instance.
Note: Cisco UCS provisioning does not require Wake-On-LAN because it uses the Cisco UCS Manager for power control.