Deployment Guide

Error! No text of specified style in document.
11 Scaling VCF Domains Beyond a Single MX7000 Chassis | Document ID
4 Deployment
Deploying host configuration parameters such as BIOS, iDRAC, RAID, NIC/CNA, and configuring the host
facing switch ports is done through the Deployment process. Deployment involves Templates and the
methods to apply the configuration data
Templates can be deployed in two different ways.
• Attach To Slots
• Deploy To Devices
Template Target Types
Attach to Slots
Templates that are attached to slots allow any compute sled inserted into those slots to take on the
personality of the assigned template. This is useful in a larger cluster where you may replace a host quickly.
Any replacement compute sleds that are inserted into that chassis slot will immediately be reconfigured using
the assigned template.
Deploy to Devices
Templates that are deployed to devices travel with the device (server). Deploying templates to devices is
useful where you expect growth and may move a device to a different slot or chassis. “Deploy to Devices” is
useful for hosts that are limited in numbers but still have specific requirements. VCF Management Domain
hosts or NSX-T Edge Node hosts are examples that might benefit from “Deploy To Devices” deployments.
4.1.1 Templates
A server template contains parameters that are extracted from a server and allows these parameters to be
quickly applied to multiple servers. A server template can contain any or all server settings for a specific
deployment type including BIOS, iDRAC, RAID, NIC/CNA, and so on. The template can be captured from a
reference server and can then be deployed to multiple servers simultaneously. The server template allows an
administrator to associate VLANs to compute sleds.