Technical White paper Chassis, Sled, and IOA Template Cloning using Dell EMC OpenManage Enterprise version 3.2 Abstract This technical white paper describes the process of cloning a complete chassis configuration to a newly procured chassis using OpenManage Enterprise.
Revisions Revisions Date Description August 2019 Initial release Acknowledgements This paper was produced by the following members of the Dell EMC Console Validation team: Author: Sreejaya Thazhe Veedu Support: Bharath Yadav, Raghu Chozhan Viswanathan (InfoDev), Biju Xavier (Illustrations) The information in this publication is provided “as is.” Dell Inc.
Table of contents Table of contents Revisions.............................................................................................................................................................................2 Acknowledgements .............................................................................................................................................................2 Table of contents .................................................................................................
Executive summary Executive summary Configuring newly procured devices in a datacenter could be quite daunting for a System Administrator, especially in large setups where many servers and chassis are added constantly. With OpenManage Enterprise it is much easier to configure your servers and chassis as it can be used to clone configurations of existing servers or chassis to the newly-added devices.
1 Requirements To perform template capture and deploy operation, the following requirements must be met: 5 ➢ Deploying device configuration requires the OpenManage Enterprise Advanced license on target servers (not available for chassis). The license is not required for creating device configuration template from a server. ➢ For the PowerEdge servers with iDRAC version lesser than 2.52.52.52 (only up to 2.50.50.
2 Clone Chassis and Server configurations with VLAN for MX7000 Cloning of a complete MX7000 chassis configuration is demonstrated with various use cases - each use case corresponds to a specific chassis configuration. 2.1 USE CASE 1 The requirement is to clone the chassis and the server configurations of an existing, fully-configured MX7000 chassis (represented as the Reference Setup) to one or more newly-added MX7000 chassis having the exact hardware configuration.
This Use case refers to the following Configuration: Reference Setup An MX7000 Chassis populated with two MX840c Sleds in Slot1 and Slot3 and two MX5018n IOMs in Fabric A1 and Fabric A2. Both MX840c Sleds have the same Hardware configuration and VLAN configuration. Newly procured Chassis One or many Chassis with Hardware configuration that matches exactly as Reference Setup. (including the number of SLEDs, SLED Models, SLED hardware inventory in addition to number of IOMs and IOA Models).
II. 1. 2. 3. 4. 5. Create a template from the reference sled Navigate to the Configuration > Deploy Tab. In the left pane, click Create Template and then select ‘From Reference Device’. In the Create Template dialog box, enter a unique name for the template. Add a description (optional) Select the Template Type as ‘Clone Reference Server’. Click Next In the Reference Device section, click Select Device to select the device whose configuration properties must be used for creating the new template.
NOTE: The VLAN ID created should be a replica of that present in the reference setup 3. Click on Finish to save the VLAN pool. II. Edit the template of the sled to associate the VLAN pool Associate VLANID 100 to NIC 1A-1-1 Tagged Network and VLANID 200 to NIC 1A-2-1 Untagged Network using the below steps: 1. Navigate to Configuration > Deploy 2. Select the Sled Template and select Edit Network. 3. Associate Tagged and Untagged VLAN pool, to the NIC ports of server configuration template.
2.1.4 Deploy the template on Chassis and Server Deploying templates is the process of sending and applying configuration settings to remote devices. A template may contain configuration settings for one or more specific functional areas, or a full device configuration. To deploy the template, you must first create the template. The template is crucial to the success of the deploy task. Ensure that the device used to create the template from, is configured exactly how you wish to deploy the same.
II. Deploy the Sled Template on the new Sled 1. Navigate to Configuration > Deploy tab. 2. Select the created Sled template. Deploy Template. 3. Select the new Sled as target device. Click Next. NOTE: The target device selected is the MX840c sled in Slot1 and Slot3 in one or more newly procured MX7000 chassis. 4. The Boot to Network ISO allows you to install the specified OS post deployment. i. Select the Share type as CIFS/ NFS. ii.
2.2 USE CASE 2 This use case describes a complex deployment technique. Here we discuss a way to successfully clone and deploy a complete Reference setup of an MX7000 chassis configuration to a newly procured chassis having additional sleds as compared to the Reference setup thereby requiring a separate VLAN association. Note: This whitepaper is written with an assumption that the current OME appliance is not used for the Reference Setup configuration. 2.2.
This Use case refers to the following Configuration: Reference Setup An MX7000 chassis populated with two MX840c sleds in Slot1 and Slot3 and two MX5018n IOMs in Fabric A1 and Fabric A2. Newly procured Chassis One or many chassis with hardware configuration that exactly matches the Reference Setup, however, having two additional MX840c Sleds in Slot 5 and Slot 7 thereby requiring a separate VLAN association.
II. Create Template from reference sled 1. Navigate to the Configuration > Deploy Tab. 2. In the left pane, click Create Template and provide Template Information. (Example MX840c Template) then select ‘From Reference Device’. 3. In the Create Template dialog box, enter a unique name for the template. Add a description (optional) 4. Select the Template Type as ‘Clone Reference Server’. Click Next 5.
2.2.3 Associate VLAN pool to the server configuration Template VLAN association is a critical step in the server template cloning. It is mandatory that the VLAN ID deployed on the Reference setup matches with the VLAN ID associated to the newly created template. This whitepaper is written with an assumption that the VLAN settings on Reference Chassis was done outside of the current OME appliance. VLAN pool can be re-used in case the same was already created in the OME appliance.
II. Edit the template of the sled to associate the VLAN pool • Edit the template of the sled to associate VLANID 100 to NIC 1A-1-1 Tagged Network and VLANID 200 to NIC 1A-2-1 Untagged Network using the below steps: 1. Navigate to Configuration > Deploy 2. Select the Sled Template and select Edit Network. 3. Associate Tagged and Untagged VLAN pool, to the NIC ports of server configuration template. VLAN IDs will be deployed on server facing ports of IOMs.
• Edit the cloned template of the sled to Associate VLANID 300 to NIC 1A-1-1 Tagged Network and VLANID 400 to NIC 1A-2-1 UnTagged Network using the below steps: 1. Navigate to Configuration > Deploy 2. Select the ‘MX840c Template-Copy’ Template and select Edit Network. 3. Associate Tagged and Untagged VLAN pool, to the NIC ports of server configuration template. VLAN IDs will be deployed on server facing ports of IOMs. 4. Click on Finish to save the Template. 2.2.
II. Deploy the Sled Template on the new Sled Deploy the MX840c Template to Slot 1 and Slot 3 of newly procured chassis using the below steps: 1. Navigate to Configuration > Deploy tab. 2. Select the MX840c template. Deploy Template 3. Select the new Sled as target device. Click Next. NOTE: The target device selected is the MX840c sled in Slot1 and Slot3 in one or more newly procured MX7000 chassis. 4. The Boot to Network ISO allows you to install the specified OS post deployment. i.
NOTE: The target device selected is the MX840c sled in Slot5 and Slot7 in one or more newly procured MX7000 chassis. 4. The Boot to Network ISO allows you to install the specified OS post deployment. i. Select the Share type as CIFS/ NFS. ii. Provide the path to the OS image in the ISO path input box in “/OS-Images/OS-file.iso” format. iii. Provide the Share IP address and Credentials that can be accessed from OM Enterprise console. iv. Click Next. 5.
3 Clone Chassis, IOA and Server configurations with VLAN for M1000e Cloning of complete M1000e chassis configuration is demonstrated using various use cases, where each use case is specific to a particular chassis configuration. 3.1 USE CASE 3 You have an M1000e Chassis containing two sleds and two IOAs which are fully configured (represented as the Reference Setup) by OpenManage Enterprise based on your data center’s needs.
M1000e Template Cloning – Usecase 3 Reference Setup An M1000e Chassis populated with two M640 Sleds in Slot1 and Slot2 and two M I/O Aggregator in Fabric A1 and Fabric A2. Both M640 Sleds have the same Hardware configuration and VLAN configuration. Newly procured Chassis One or many Chassis with Hardware configuration that matches exactly as Reference Setup. (including the number of SLEDs, SLED Models, SLED hardware inventory in addition to number of IOAs and IOA Models).
3.1.2 Capture the template of M1000e Chassis and M640 Sled This section describes how to create a template from a reference device. The ‘reference device’ is a device that has been discovered in OpenManage Enterprise, configured in a desired way and the configuration of the same is intended to be replicated on the equivalent devices. The reference template is crucial to the success of configuring your other devices.
3.1.3 Associate VLAN pool to the server configuration Template VLAN association is a critical step in the server template cloning. It is mandatory that the VLAN ID deployed on the Reference setup matches with the VLAN ID associated to the newly created template. This white paper is written with an assumption that the VLAN settings on Reference Chassis was done outside of the current OME appliance. VLAN pool can be re-used in case the same was already created in the OME appliance.
2.3.2.1 II. Click on Finish to save the VLAN pool. Edit the template of the Sled to associate the VLAN pool • Associate VLANID 100 to Integrated NIC 1 Port1 UnTagged Network and VLANID 200 to Integrated NIC 1 Port2 Tagged Network using the below steps: 1. Navigate to Configuration > Deploy 2. Select the Sled Template and select Edit Network. 3. Associate Tagged and Untagged VLAN pool, to the NIC ports of server configuration template. VLAN IDs will be deployed on server facing ports of IOAs.
3.1.4 Deploy the template on Chassis and Server Deploying templates is the process of sending and applying configuration settings to remote devices. A template may contain configuration settings for one or more specific functional areas, or a full device configuration. To deploy the template, you must first create the template. The template is crucial to the success of the deploy task. Ensure that the device used to create the template from, is configured exactly how you wish to deploy the same.
5. The IDRAC IP setting can be changed to DHCP or Static in the IDRAC Management IP Option. o If you wish to set static IP for the devices selected for deployment, select the Set static IP for each device options and provide the Management IP for each device. 6. Select the option Run Now if you wish to run the job immediately or deployment can be scheduled. 3.1.5 Creating and Deploying IOA Template An IOA Template contains VLAN data, SNMP configurations, IOA modes, DCB configuration details etc.
I. Create Template of an IOA 1. 2. 3. 4. Navigate to Configuration > Deploy portal Click on create template option, from the drop down select “From Reference Device” Create template wizard pops up Enter the template name and description, Select the template Type as Clone Reference IOA 5. 6. 7. 8. In Reference device section, select the device and click on finish button Job will be created in jobs portal and when clicked on view details Task Execution History will be displayed.
Deploy the IOA Template 1. Navigate to Configuration Deploy portal 2. Select the captured template and click on Deploy Template option 3. Deploy Template wizard pops up. In Target section, select the device on which template must be deployed (Number of devices selected will be displayed), click Next option 4. Host Names section will be displayed, Enter the Hostname for selected device, click next button. 5. Advanced option allows two ways of deployment.
When deployment task is performed using Preview mode, Pre-Checks will be displayed as: Success -> Success indicates, the configuration can be successfully deployed on the IOA without any failure Warning -> Warning indicates, there is a low severity dependency mismatch which may need attention. However, you can continue the deployment with “Continue on warning” option. Failure -> Failure indicates, the configuration cannot be applied on the target IOA. 6.
M1000e Template Cloning – Usecase 4 This Use case refers to the following Configuration: Reference Setup An M1000e chassis populated with two M640 Sleds in Slot1 and Slot2 and two M I/O aggregators in Fabric A1 and Fabric A2. Both M640 sleds have the same hardware configuration and VLAN configuration.
3.2.2 Capture the Template of M1000e Chassis and M640 Sled This section describes how to create a template from a reference device. The ‘reference device’ is a device that has been discovered in OpenManage Enterprise, configured in a desired way and the configuration of the same is intended to be replicated on the equivalent devices. The reference template is crucial to the success of configuring your other devices.
3. Click on Clone template. 4. In the Create Template dialog box, enter a unique name for the template (Example: M640 Template-Copy). Add a description (optional) 5. A copy of the M640 Template is created. NOTE: This Template is used to deploy on M640 sleds present in Slot 3 and Slot 4 of the newly procured chassis. 3.2.3 Associate VLAN pool to the server configuration Template VLAN association is a critical step in the server template cloning.
II. Edit the template of the Sled to associate the VLAN pool • Edit the template of the sled to associate VLANID 100 to Integrated NIC 1 Port1 Untagged Network and VLANID 200 to Integrated NIC 1 Port2 Tagged Network using the below steps: 1. Navigate to Configuration > Deploy 2. Select the Sled Template and select Edit Network. 3. Associate Tagged and Untagged VLAN pool, to the NIC ports of server configuration template. VLAN IDs will be deployed on server facing ports of IOAs.
4. Click on Finish to save the Template. 3.2.4 Deploy the template on Chassis and Server Deploying templates is the process of sending and applying configuration settings to remote devices. A template may contain configuration settings for one or more specific functional areas, or a full device configuration. To deploy the template, you must first create the template. The template is crucial to the success of the deploy task.
II. Deploy the Sled Template on the new Sled 1. Navigate to Configuration > Deploy tab. 2. Select the created Sled template. Click on Deploy Template. 3. Select the new Sled as target device. Click Next. NOTE: The target device selected is the M640 sled in Slot1 and Slot2 populated in one or more newly procured M1000e chassis. 4. i. ii. iii. iv. The Boot to Network ISO allows you to install the specified OS post deployment. Select the Share type as CIFS/ NFS.
3. Select the new Sled as target device. Click Next. NOTE: The target device selected is the M640 sled in Slot3 and Slot4 in one or more newly procured M1000e chassis. 4. The Boot to Network ISO allows you to install the specified OS post deployment. i. ii. iii. iv. Select the Share type as CIFS/ NFS. Provide the path to the OS image in the ISO path input box in “/OS-Images/OS-file.iso” format. Provide the Share IP address and Credentials that can be accessed from OM Enterprise console. Click Next. 5.
4 Clone chassis and server configuration with VLAN by changing the attributes values OpenManage Enterprise allows editing of a template if you wish to customize the configuration of the target server. The attributes of template can be edited irrespective of whether the template was created using a Reference device or Reference Template file. The built-in templates can be edited only after cloning it. Note: Editing of IOA templates is not supported in OpenManage Enterprise. 4.
6. Review the modification in the Summary and click Finish to save the Template. II. Editing a chassis template Chassis Template gives Advanced View option mode that enables to edit all the available chassis Management Module components. 1. Navigate to Configuration Deploy portal 2. Select the Chassis Template and Click Edit. 3. Edit the Template Name and description if required in the Template Information grid. 4.
A Technical support and resources • • 39 Dell.com/support is focused on meeting customer needs with proven services and support. For OpenManage Enterprise documentation on the Dell support site, see OpenManage Enterprise documents Chassis, Sled, and IOA Template Cloning using Dell EMC OpenManage Enterprise version 3.
