Dell PowerEdge MX7000 EMC OpenManage Enterprise-Modular Edition Version 1.20.0 - Page 67

Deploying templates from Template Details Editing templates, Editing template networks

Page 67 highlights

2. Select the target slot or device on which you want to deploy the template, enter the ISO path and location details, configure the iDRAC management IP settings, select the Do not forcefully reboot the host OS if the graceful reboot fails option. If you select an occupied sled slot, the Immediately Apply Template to Compute Sleds check box is displayed. Select the check box to reseat the compute sled immediately and deploy the template on it. Selecting the Do not forcefully reboot the host OS if the graceful reboot fails option prevents a nongraceful reboot of the compute sled. NOTE: OME-Modular Deployment Boot to ISO may fail when OME-Modular and iDRAC are in different networks, though the TEST CONNECTION comes through. The failure could be due to network protocol restrictions. 3. Select the virtual identity pool or click Reserve Identity to reserve the required identity pool for deploying the templates. 4. Schedule the deployment and click Finish. Deploying templates from Template Details page To deploy a template from the Template Details page: 1. On the Template Details page, click Deploy Template. 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 slot or device on which you want to deploy the template, enter the ISO path and location details, configure the iDRAC management IP settings, select the Do not forcefully reboot the host OS if the graceful reboot fails option, and schedule the deployment. If you select an occupied sled slot, the Immediately Apply Template to Compute Sleds check box is displayed. Select the check box to reseat the compute sled immediately and deploy the template on it. Selecting the Do not forcefully reboot the host OS if the graceful reboot fails option prevents a nongraceful reboot of the compute sled. 3. Select the virtual identity pool or click Reserve Identity to reserve the required identity pool for deploying the templates. 4. Schedule the deployment and click Finish. 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 teaming 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. Managing templates 67

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122

2.
Select the target slot or device on which you want to deploy the template, enter the ISO path and location details, configure
the iDRAC management IP settings, select the
Do not forcefully reboot the host OS if the graceful reboot fails
option.
If you select an occupied sled slot, the
Immediately Apply Template to Compute Sleds
check box is displayed. Select the
check box to reseat the compute sled immediately and deploy the template on it.
Selecting the
Do not forcefully reboot the host OS if the graceful reboot fails
option prevents a nongraceful reboot of
the compute sled.
NOTE:
OME-Modular Deployment Boot to ISO may fail when OME-Modular and iDRAC are in different networks,
though the TEST CONNECTION comes through. The failure could be due to network protocol restrictions.
3.
Select the virtual identity pool or click
Reserve Identity
to reserve the required identity pool for deploying the templates.
4.
Schedule the deployment and click
Finish
.
Deploying templates from Template Details page
To deploy a template from the
Template Details
page:
1.
On the
Template Details
page, click
Deploy Template
.
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 slot or device on which you want to deploy the template, enter the ISO path and location details, configure
the iDRAC management IP settings, select the
Do not forcefully reboot the host OS if the graceful reboot fails
option,
and schedule the deployment.
If you select an occupied sled slot, the
Immediately Apply Template to Compute Sleds
check box is displayed. Select the
check box to reseat the compute sled immediately and deploy the template on it.
Selecting the
Do not forcefully reboot the host OS if the graceful reboot fails
option prevents a nongraceful reboot of
the compute sled.
3.
Select the virtual identity pool or click
Reserve Identity
to reserve the required identity pool for deploying the templates.
4.
Schedule the deployment and click
Finish
.
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 teaming 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.
Managing templates
67