Server Hardware Provisioning and OS Deployment by using Dell EMC OpenManage Essentials This Dell EMC technical white paper describes the process of provisioning the server hardware and deploying Operating System (OS) by using OpenManage Essentials (OME). Abstract This Dell EMC technical white paper describes the process of provisioning the server hardware and deploying OS by using OME.
Revisions Date Description September 2015 Initial release July 2016 Added support for Dell EMC Networking IOAs June 2017 Focus on servers with guidance on template editing February 2018 Redfish streaming support update November 2018 Added support for VLAN Configuration on PowerEdge MX7000 chassis Acknowledgements This paper was produced by the following members of the Dell EMC Server Engineering team: Author: Nikhil S Support: Sheshadri Rao (InfoDev) Other: The information in this publication i
Contents Revisions.............................................................................................................................................................................2 Acknowledgements .............................................................................................................................................................2 1 Executive summary ..........................................................................................................................
14 Create virtual I/O pools ...............................................................................................................................................31 14.1 Virtual I/O pool definition ..................................................................................................................................31 14.2 Types of identities .............................................................................................................................................31 14.
20.1 Auto-deploy requirements ................................................................................................................................44 20.2 Set up auto-deploy of a template......................................................................................................................44 20.2.1 Create a Service Tag CSV file .....................................................................................................................44 20.2.
Executive summary 1 Executive summary With OpenManage Essentials (OME) version 2.5, basic and intuitive guidance is now provided to set up first restart and update network settings in a server configuration template. These are very common use cases intercepted in a server’s lifecycle. This technical white paper discusses about: • • • 6 Configuring VLANs on Dell EMC Networking IOAs included within server template deployment workflows.
Features discussed in this technical white paper 2 Features discussed in this technical white paper • • • • • • • • • • 7 Comprehensive use case examples for using OME device configuration features Requirements and setup for using the features Create a template from a server Edit a server template to configure first restart and network settings Create a virtual I/O pool Create and deploy a compute pool Deploy a template to a server Deploy VLANs on server facing ports of IOAs during template deployment o
Prepare OME for device configuration 3 Prepare OME for device configuration Device prerequisites and file share settings are required to use the deployment features in OME. This section describes the device requirements, configuring the file share settings, and troubleshooting the file share settings. 3.1 Target device requirements • • For 12th and 13th generation of PowerEdge servers, the minimum supported version of iDRAC is 2.30.30.30.
Prepare OME for device configuration 3.3 File share settings The device configuration and deployment feature now makes use of iDRAC’s Redfish interface. However, for servers not having the minimum supported iDRAC version 2.50.50.50, it would require a staging area (file share). This section describes about the file share and setting up the file share. 3.3.1 File share requirement explanation The file share is a staging area for deployment.
Prepare OME for device configuration 5. Click Apply. If the Allow using file share for Device Configuration feature on server check box is selected, a message is displayed to upgrade servers to latest firmware: Firmware Warning 6. Click Yes to continue to use file share. 7.
Edit server configuration template in a guided manner 4 Edit server configuration template in a guided manner Conventionally, editing the configuration template has been difficult in OME, as all the attributes are presented in one view. One must identify all the attributes to be edited to enable/disable a particular feature. To simplify most common use cases of a server’s life cycle, guidance is provided in OME 2.
Understand the differences between bare-metal and stateless deployments 5 Understand the differences between bare-metal and stateless deployments Bare-metal and stateless are the two methods of deployment available from OME version 2.1 onwards. The primary differentiator between these is who controls the virtual identities assigned to the device. In bare-metal deployment, the user defines the identities and manually enters these into OME. This could also be considered manual identity deployment.
Deploy the template in stateless environment 6 Deploy the template in stateless environment Example use case—You want to deploy and manage servers in a virtualized environment connected to a storage area network. You want the configuration of one well-formatted server deployed to other servers, and you want the servers to use virtual identities created from manageable virtual identity definitions. To accomplish this use case: 1.
Replace a server in stateless environment 7 Replace a server in stateless environment Example use case—A server in your stateless environment experienced a hardware failure. You must transfer the workload of the failing server to a new server. Prerequisites: • • The source device must have been deployed from OME from a compute pool by using Virtual I/O. The target device must be in the same compute pool as the source. 1. Add the target device to the ‘Repurpose and Bare-metal’ device group if not already.
Reclaim virtual identities deployed by OME 8 Reclaim virtual identities deployed by OME Example use case—A production server with a specific workload needs retired, and you wish to reclaim all the virtual identities so OME can reuse these later. Prerequisites: The source device must have been deployed from OME by using a compute pool by using Virtual I/O. 1. Complete the reclaim identities wizard to begin the reclaim process. 2. Verify the task succeeded in the task execution history.
Deploy the template to a bare-metal device 9 Deploy the template to a bare-metal device Example use case—based on your data center’s requirements, you configure all the settings of one server. You have a new bare-metal device or device you want to repurpose. You want to copy all of the settings of the configured device and apply them to bare-metal/repurpose device. To accomplish this use case: 1. Get the configuration from the device that is already configured and save it in OME as a template.
Configure VLANs on server-facing ports of IOAs along with server deployment 10 Configure VLANs on server-facing ports of IOAs along with server deployment Example use case—You are using VLAN tagging in your networking infrastructure to control packet flow. Additionally, you are using specific VLANs to control communication with modular servers enforced by chassis IOAs. Based on your data center’s needs, you configure all the settings of one modular server.
Automate hardware configuration and operating system deployment (auto-deploy) of recently ordered devices 11 Automate hardware configuration and operating system deployment (auto-deploy) of recently ordered devices Example use case—your Company orders several new devices. The devices are shipped and may come in at different times. When a device is connected to the network, you want a template you created deployed to the device and for the devices to boot to an ISO on your network.
Hardware setup for the stateless environment 12 Hardware setup for the stateless environment This section covers the hardware setup and best practices for configuring an environment for stateless computing.
Create templates 13 Create templates Understanding and creating templates is necessary for using the deployment and configuration features. This section explains the template and how to create the template from a reference device or from a file. 13.1 Template definition A template is a collection of attributes that describe the settings of a device. The settings describe the behavior of a device’s hardware. A device may have several hundred attributes depending on the device’s hardware.
Create templates Create template from reference device wizard 7. Click Finish. 8. Click Ok. A task is created. 9. To view the created task, click the Tasks tab in the Deployment. 10. To view the progress of the task, look at the Task Execution History grid. 11. To view the details of execution history, double-click the task execution history entry, or right-click the task execution history entry. 12. Select Details. The information about the issues (such as incorrect credentials) is displayed.
Create templates 13. If the task is unsuccessful, right-click the task execution history or the task, and then click Run. Note—Enter the iDRAC credentials to run the task again. 13.4 Creating the template from an XML configuration file The following section describes how to create a template from an XML configuration file. Configuration XML is used for server templates. A configuration file can be obtained by exporting a template to file in OME.
Create templates Create template from file wizard 20. Click Finish to create the template. The template name is added to the Server Templates tree.
Create templates 13.5 Guidance about editing templates in OpenManage Essentials The following section describes how to edit the server configuration template to enable or disable certain features. Supported use cases: • • • • Configuring first boot settings. Enabling/disabling partitioning on capable NICs. Editing IOA VLAN attributes with respect to modular servers. Configuring VLAN attributes for MX7000 compatible modular servers.
Create templates Note: While configuring first boot, boot mode cannot be changed in templates created from 13 th generation of servers and onwards. This is a limitation as the profile XML provides boot sequence and other attributes for current boot mode only. Configure FCoE boot in a server template Note—For templates created from (and deployed to) 12th generation of servers or later running with older firmware, PXE boot in UEFI mode will not work. Nor will it get identified in the template if set so.
Create templates Change hard drive sequence 13.5.
Create templates Follow these steps to enable partitioning and allocate minimum and maximum bandwidth per partition on a network interface card in the server template: 1. 2. 3. 4. 5. 6. 7. 8. Navigate to the Deployment tab. In the left pane select the template under TemplatesServer Templates. Select Boot and Network Configuration tab in the right side template details. Expand Network Interface Settings. Expand network interface card of your choice. Select the Enable check box.
Create templates 2. Type the values in the Tagged VLAN(s) and Untagged VLAN boxes corresponding to Port 1 and Port 2. 3. Click Save to make the changes to the template. Assign tagged VLANs and untagged VLAN 13.5.3 Edit IOA VLAN attributes in server template This section describes how to edit and assign IOA VLAN attributes for a template created by using the modular server.
Create templates Edit IOA VLAN attributes 13.5.4 Edit VLAN Configuration in MX7000 compatible server template This section describes how to edit and assign VLAN attributes for a template created by using the modular server compatible with MX7000 chassis, to enable VLAN assignment on the server-facing ports of IOAs during the deployment of configuration template on sever: Note—VLAN Configuration will only be available with templates created by using modular servers compatible with MX7000.
Create templates Add new network 6. 7. 8. 9. 10. After the networks are created for required VLAN IDs, click Save. Navigate to VLAN Configuration tab for the assignment of networks to ports in the NICs. Check Deploy column to enable the configuration to be considered for deployment. In the Tagged VLAN(s) column, select network(s) from the drop-down menu corresponding to each port. In the Untagged VLAN column, select network from the drop-down menu corresponding to each port. Edit VLAN attributes 11.
Create virtual I/O pools 14 Create virtual I/O pools Virtual I/O pools simplify identity management in the OME. This section describes how to create the Virtual I/O pool from a prefix definition or an import file. Also, about how to increase the size of Virtual I/O pool and lock or unlock the Virtual I/O pool. 14.1 Virtual I/O pool definition The Virtual I/O pool is a definition of identity types that describe identities and determines the identities OME will generate.
Create virtual I/O pools Restrictions: WWN address prefixes require a NAA value of two, five or six. An NAA value (Network Address Authority) is a 4-bit field used to guarantee uniqueness of WW names. The NAA value is the first four bits of the address (so, the address must start with 2, 5 or 6). Defined by: • Start address • Number of identities or imported identities 14.2.3 World Wide Port Name (WWPN) definition WWPN address is used to define virtual WWPN address properties.
Create virtual I/O pools 5. Type the WWNN address and number of identities if the stateless environment is FC or FCoE or clear the Include Fiber Channel WWNN Identities in the Pool check box, and then Click Next. 6. Type the WWPN address and number of identities if the stateless environment is FC or FCoE or clear the Include Fiber Channel WWPN Identities in the Pool check box, and then Click Next. 7. Type an iSCSI IQN string if the stateless environment is iSCSI.
Create virtual I/O pools 14.3.1.2 Import identities from a CSV file To import identities from a file: 1. Under the Create Virtual I/O Pool in the identity type screen (example Ethernet Identities screen) click Import from file 2. Click Import. 3. In the import dialog box, click Import. 4. Select a file. 5. Wait for the import to finish (progress bar shows the status). 6. Review results and close the results. 7. (Optional) import additional files (repeat steps 3—6). 8. Click Close.
Create compute pool 15 Create compute pool Compute pools provide the method to group a set of similar devices for deployment and pre-can the settings which will be applied to them. The pool can be recalled at the deployment time to simplify the deployment process. Compute pools are required for Virtual I/O. Compute pools are visible in the deployment portal and under the main device tree under the repurpose and bare-metal group. 15.
Deploy compute pools 16 Deploy compute pools Deploying the compute pool is required to apply the settings in the pool definition to one or more devices in the pool. 16.1 Requirements for deploying Compute Pools in OpenManage Essentials • • • • • 16.2 The file share must be configured. See Setting up file share. The target devices must meet the minimum requirements for the deployment and configuration features. See Target device requirements.
Deploy compute pools Assign identity attributes 9. Define the task start time. 10. You can optionally preview the task results. This will simulate the deploy action and show the results, when the task is executed. 11. After completing the wizard, the task will be created and scheduled for running. 12. You should verify the task result by reviewing the task execution history for the task after it is executed. 16.
Deploy template to bare-metal devices 17 Deploy template to bare-metal devices This section describes how to deploy the template by using manual I/O which was introduced in OME 2.0. For stateless deployment, see Deploying the compute pool, and its prerequisite sections. 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.
Deploy template to bare-metal devices Note—Only devices that satisfy the deploy requirements appear in the device selection. To review the requirements, see the Prerequisites for section. Modify repurpose and bare-metal device group popup 17.3 Deploy the template This section describes how to deploy the template to servers, chassis, and IOAs. 17.3.1 Deploy the template to servers 1. Navigate to the Deployment tab. 2. In the left pane, click Deploy Template under Common Tasks. 3.
Deploy template to bare-metal devices 6. Select the target devices, and then click Next. Note—Only devices in the Repurpose and Bare-metal device group and match the device type of the selected template may be selected. To add the devices to the device group, see Adding devices to the ‘Repurpose and Bare-metal’ device group. 7. Enter the system-specific attributes for each target device and click Next.
Deploy template to bare-metal devices Edit attributes pane Alternatively, you can import and export the grid file to edit. You may want to export/import if you have more number of devices with many device-specific attributes. The device-specific attributes grid can be exported based on selected device or all devices. All devices will export to a single file that can be opened in a spreadsheet processing application. When edits are finished in the file, the file may be imported.
Configure VLANs on the server-facing ports of IOAs during template deployment on the server 18 Configure VLANs on the server-facing ports of IOAs during template deployment on the server This section describes how to configure VLANs on the server-facing ports of IOAs during template deployment on target servers. 18.1 Deploy the template to servers along with VLAN configuration of associated IOA ports 1. Navigate to the Deployment tab. 2. In the left pane, click Deploy Template under Common Tasks. 3.
Configure VLANs on server-facing ports of IOAs in MX7000 chassis during template deployment on the server 19 Configure VLANs on server-facing ports of IOAs in MX7000 chassis during template deployment on the server This section describes how to configure VLANs on the server-facing ports of IOAs in MX7000 chassis during template deployment on target servers. 19.1 Deploy the template to servers along with Network and VLAN configuration 1. Navigate to the Deployment tab. 2.
Automatically deploy templates in OpenManage Essentials 20 Automatically deploy templates in OpenManage Essentials After discovery, auto deploying the templates applies to all the attribute values of the templates to the device. To add auto-deploy entries for devices that have not been discovered by OME, a list of Service Tags for the target devices must be provided. To auto-deploy a template, you must first create a template. For instructions about creating a template, see Creating templates.
Automatically deploy templates in OpenManage Essentials 6. Click the Import to import the csv file that contains the Service Tag or node ID. The imported Service Tags or node IDs must be compatible with the type of template selected in the step above. 7. Browse to the location where the file is saved, select the file, and then click Open. All the Service Tags in the file will be imported and listed in OME. The Import Summary window is displayed. 8. Review and click Ok. Click Next. 9.
Automatically deploy templates in OpenManage Essentials 7. (optional) Enter the unique attributes per Service Tag. For details, see Editing the device specific attributes of the deploy template task. 8. Click Next. 9. Select the execution credentials for the Service Tags. Instead of entering the credentials for each target device, credential definitions must be created. Credential definitions can be added as needed. Credential definitions can be assigned to multiple targets.
Automatically deploy templates in OpenManage Essentials The Service Tags remain in the Auto Deployment tab until they are discovered and inventoried in OME and the Deploy Configuration to Undiscovered Devices task creates a deploy task for the device with the Service Tag. The Deploy Configuration to Undiscovered Devices task checks periodically if the devices are discovered and inventoried in OME.
Deploy network ISO image file 21 Deploy network ISO image file Deploying the network ISO file boots a server to an ISO image that is located on your network. This can be done independent, or in conjunction with the deployment task. 21.1 Deploy network ISO image requirements • • 21.2 Must fulfill all the Deploy Template requirements. See Target device requirements. If the Deploy Template option is selected, only server templates can be selected. Deploy network ISO image 1.
Deploy network ISO image file Select ISO location page Note—The user must have full control to the share folder where the ISO is located. The share folder should be different than the file share used for deployment. 7. Select the target devices and click Next. Note—Only devices in the Repurpose and Bare-metal device group may be selected. To add the devices to the group, see the Adding devices to the ‘Repurpose and Bare-metal’ device group. 8. Set the schedule of when the deploy template task will run.
Troubleshooting issues in hardware and OS deployment on servers monitored by OpenManage Essentials 22 Troubleshooting issues in hardware and OS deployment on servers monitored by OpenManage Essentials 22.1 Troubleshooting the file share 1. Check the file share status in OME. Note—The file share status is at the bottom of the file share wizard and under the Deployment Settings preference. File share settings status 2. Check the username, domain, and password in OME. 3.
Troubleshooting issues in hardware and OS deployment on servers monitored by OpenManage Essentials Advanced sharing tab of the ServerConfig folder • • • 51 Verify the share folder location by running the net share command. Open the CLI and enter net share. A share with the name ServerConfig should be in the network share list.
Troubleshooting issues in hardware and OS deployment on servers monitored by OpenManage Essentials Net share command results • 22.2 Check the user permissions in the User Accounts window. Troubleshoot the template creation process in OpenManage Essentials Troubleshooting the process of creating a template from a reference device: • • • • • Ensure that the file share settings are correctly configured. See Troubleshooting the file share. Run the task again.
Troubleshooting issues in hardware and OS deployment on servers monitored by OpenManage Essentials 22.3 Troubleshoot the virtual I/O pool creation in OpenManage Essentials Troubleshooting the creating or editing an identity type: • • • 22.4 Ensure that the identity type definition meets the requirements for that identity type. See Types of identities. If you cannot edit a virtual I/O pool, it may be locked. To unlock (and enable editing), see Locking and unlocking the Virtual I/O pool.
Troubleshooting issues in hardware and OS deployment on servers monitored by OpenManage Essentials 22.5 Troubleshoot the auto-deploy templates Whenever the Deploy Configuration to Undiscovered Devices task is executed, it searches for Service Tags in the Auto Deployment list. The following situations can observed: • • • • 54 There are no Service Tags in the Auto Deployment list. In this case, the task exits, and no entry is created in the task execution history grid for that run.
Troubleshooting issues in hardware and OS deployment on servers monitored by OpenManage Essentials 22.6 Troubleshoot the network ISO deployment The task execution history details provide the troubleshooting information. If the network is unable to find the ISO share, check the following: • • Verify the IP address in the share location. Verify the path to the folder of the share. A common misconception is to put the share base folder in the share name area.
Boot-from-SAN considerations 23 Boot-from-SAN considerations The template attributes include the attributes to support Boot-from-SAN operations. Boot-from-SAN functionality may run over iSCSI, FC, or FCoE connections. The Boot-from-SAN operations attributes include the attributes for both initiators and targets. Regardless of the protocol being used, the storage (target) hardware and software must be setup, configured, and available on the network.
Error! No text of specified style in document.
Boot-from-SAN by using FC or FCoE Support is only provided for the assignment of iSCSI IP addresses by DHCP, which is specified via the following two attributes and corresponding values: TcpipViaDHCP IscsiViaDHCP “Enabled” “Enabled” Due to this restriction, Virtual I/O pools don’t have a provision for assigning IP addresses, subnet, or gateway values for iSCSI. 23.
Boot-from-SAN by using FC or FCoE 24 Technical support and resources Dell.com/support is focused on meeting customer needs with proven services and support. Referenced or recommended Dell EMC publications: 59 • Dell EMC Attribute Registry: http://en.community.dell.com/techcenter/systems-management/w/wiki/1979.lifecyclecontroller.aspx#attributereg • Dell EMC iDRAC7 with Lifecycle Controller 2 Technical White Papers: http://en.community.dell.com/techcenter/systems-management/w/wiki/4317.
