Users Guide

If the template has identity attributes, but is not associated with a virtual identity pool, a message is displayed that the

physical identities are used for the deployment. Else, the Deploy Template wizard is displayed.

2. Select the target device on which you want to deploy the template, configure the iDRAC management IP settings, select the

Do not forcefully reboot the host OS option, and schedule the deployment.

The compute sled reboots gracefully or non-gracefully, based on the selection.

Editing templates

You can only modify the name and description of the template from the Deploy and Template Details pages.

1. On the Deploy page, select the template that you want to modify and click Edit. Else, on the Template Details page, click

Edit.

The Edit Template window is displayed.

2. Make the required changes.

Editing template networks

To edit template network details:

1. On the Deploy page, select the template whose network details you want to modify and click Edit Network.

The Edit Network window is displayed.

2. Modify the Identity Pool, if necessary.

3. Select the NIC grouping option for the port.

NIC teaming is suggested for redundancy, though it is not required. NIC Partitioning (NPAR) can impact how NIC teaming

operates. Based on restrictions that are related to NIC partitioning, which NIC vendors implement, certain configurations

prevent certain types of teaming. The following restrictions are applicable to both Full Switch and SmartFabric modes:

● If NPAR is not used, both Switch-dependent (LACP) and Other (Switch-independent) teaming methods are supported.

● If NPAR is used, only Other (Switch-independent) teaming methods are supported. Switch-dependent teaming is not

supported.

The NIC teaming feature is applicable to IOM versions 10.5.0 and later.

Refer to the network adapter or operating system documentation for detailed NIC teaming instructions.

The available NIC grouping options are:

● No Teaming—NICs are not bonded and provide no load balancing or redundancy.

● LACP—Also referred to as Switch Dependent, 802.3ad or Dynamic Link Aggregation. The LACP teaming method uses

the LACP protocol to understand the teaming topology. It provides Active-Active teaming with load balancing and

redundancy. With this option, only the native VLAN is programmed on non-LAG interfaces. All tagged VLANS wait until

the LACP LAG is enabled on the NICs. The following restrictions are applicable to LACP teaming:

○ The IDRAC shared LOM feature can only be used if “Failover” option on IDRAC is enabled.

○ If the host operating system is Windows, the LACP timer must be set to “slow” (also referred to as “normal”).

●

Other—Refers to a NIC teaming method where the switch is unaware of the teaming technology that is used. The

"other" option involves using the operating system and NIC device drivers on the server to team the NICs. Each NIC

vendor may provide slightly different implementations with different pros and cons.

4. Select the tagged and untagged VLANs, if necessary.

Cloning templates

To create a copy of a template:

On the Deploy page, select the template of which you want to create a copy, and click Clone.

Managing templates