Managing Modular Infrastructure by using OpenManage Essentials (OME) This Dell EMC technical white paper describes how to manage the modular infrastructure by using OME. Abstract This Dell EMC technical white paper describes how to manage the modular infrastructure by using OME.
Revisions Revisions Date Description July 2017 Initial release October 2018 OME 2.5 release Acknowledgements This paper was produced by the following members of the Dell EMC Server Engineering team: Author: Jayant Prajapat Support: Sheshadri PR Rao (InfoDev) Other: The information in this publication is provided “as is.” Dell Inc.
Acknowledgements Contents Revisions.............................................................................................................................................................................2 Acknowledgements .............................................................................................................................................................2 Executive summary............................................................................................................
Acknowledgements 15.2 Set up and run the configuration inventory.......................................................................................................42 15.2.1 Modify configuration inventory Ccredentials and/or schedule .....................................................................42 15.2.2 Run configuration inventory per target .........................................................................................................43 15.
Executive summary Executive summary OME 2.5 supports "Simplified modular infrastructure configuration management", where MX Chassis configurations are managed similar to CMC. OME 2.3 and later versions of OME supports "Simplified modular infrastructure configuration management", where the chassis and IOA configurations are managed together. The Chassis Infrastructure templates contain both the CMC template and all the supported IOA templates on the Chassis.
Executive summary 1 Features discussed in this technical white paper 6 Comprehensive use case examples for using the OME IOA configuration features Requirements and setup for using the features Creating a template from the Chassis or IOA or MX Chassis Editing a Chassis template or MX Chassis template Deploying a Chassis template to a Chassis and its IOAs Deploying a MX Chassis template to a MX Chassis Setting up auto deployment with Chassis templates or MX Chassis templates Deployi
Technical support and resources 2 Prepare OpenManage Essentials for managing Modular Infrastructure The MX Chassis must be discovered by using the MX Chassis Discovery-All Components option in Discovery wizard. When an MX Chassis is discovered by using the MX Chassis Discovery-All Components option in discovery wizard, all the servers of the blade chassis are also discovered automatically in OME.
Executive summary files will briefly exist in the file share folder. After the completion of ‘create’ or ‘deploy’ task, the file is deleted. Security attributes (passwords and other sensitive data) are not included in the file. 2.2.2 Set up a file share The file share settings must be entered in the OME. The file share settings require a username and a password of a user who has privileges to read and write the files on OEM system.
Technical support and resources 3 Create Chassis infrastructure template from a reference Chassis by using IOA devices or MX Chassis template from a reference MX Chassis OME 2.5 supports "Simplified modular infrastructure configuration management", where MX Chassis configurations are managed similar to CMC. OME 2.3 and later versions support "Simplified modular infrastructure configuration management", where the CMC and IOA configurations are managed together.
Executive summary Create MX Chassis template from reference device wizard 10 Managing Modular Infrastructure by using OpenManage Essentials (OME)
Technical support and resources Create chassis template from reference device wizard 8. Click Finish. 9. Click OK. The task is created when the wizard is closed. 10. To view the created task, click the Tasks tab in Deployment. 11. To view the progress of the task, see the Task Execution History. 12. To view the details of execution history, double-click the task execution history entry, or right-click the task execution history entry. 13. Select Details.
Executive summary 14. If the task is successful, the template is created and displayed in the Chassis Templates tree (if you have created template for Chassis) or MX Chassis Templates tree (if you have created template for MX Chassis). 15. If the task is unsuccessful, right-click the task execution history or the task, and then click Run. Note—Enter the CMC and IOA credentials (for Chassis device type) or MX Chassis credentials (for MX Chassis device type) to rerun the task.
Technical support and resources 4 View and edit Chassis infrastructure template or MX Chassis template Example use case—you have an existing template (Chassis infrastructure template or MX Chassis template) and you have to change some of the template attributes. To accomplish this use case: 1. Navigate to the Deployment tab. 2. Select any Chassis Infrastructure template or MX Chassis template in the Templates tree.
Executive summary To change the CMC device template attributes or MX Chassis template attributes: 1. Under Attributes, select the attribute value. 2. Click Save. 3. In the Save Template dialog box, click Yes Editing MX chassis template attributes Editing chassis template attributes of chassis infrastructure template Note—Editing the template attributes in the deployment wizard is not supported. Only device-specific attributes of the CMC device and IOA template(s) can be modified.
Technical support and resources 4. To view the corresponding IOA templates, navigate to other tabs named with IOA names. Viewing the IOA templates of chassis infrastructure template Note—The modification of IOA attributes is not supported. To deploy the IOA template on the specific IOA: 1. Under Attributes, clear the IOA value. 2. Click Save. 3. In the Save Template dialog box, click Yes. Note—IOA templates selection in the Deployment wizard is not supported.
Executive summary Selecting the IOA templates of chassis infrastructure template 16 Managing Modular Infrastructure by using OpenManage Essentials (OME)
Technical support and resources 5 Deploy chassis infrastructure template or MX chassis template Example use case—Based on the requirements of your data center, you have configured the settings of the particular MX Chassis or Chassis and the corresponding IOAs (CMC devices and the IOAs on the Chassis). You have a new or existing MX Chassis or Chassis which you want to reuse.
Executive summary 6 Deploy a template on bare-metal devices This section describes the procedure for deploying the template on CMC devices by using manual I/O or on MX Chassis. Deploying the templates involves sending and applying configuration settings to the remote devices. The template may contain a single configuration setting, one or more specific functional areas configuration settings, or a full device configuration setting. To deploy the template, you must create the template first.
Technical support and resources Modifying Repurpose and Bare Metal Device Group 6.3 Deploy the template This section describes the procedure for deploying a Chassis Infrastructure template to chassis (CMC device and the IOAs present on the chassis) or an MX Chassis template to an MX Chassis. 6.3.1 Deploy the template to Chassis or MX Chassis 1. Navigate to the Deployment tab. 2. In the left pane, click Deploy Template under Common Tasks. 3. Type a unique name for the task.
Executive summary Note—These are the attributes, such as ‘StaticGateway’, that are not included in the templates because they do not necessarily apply to all target devices. For more details, see Editing the Device Specific Attributes of Deploy Template Task. 8. Click Next. 9. To continue the deployment when the template is incompatible with the target devices, on the Options page, select Continue on warnings. 10. Click Next. 11. Set the schedule when the deploy template task runs.
Technical support and resources Note—OME will automatically rediscover the target CMC device of the target chassis whenever a new static IP address is deployed, after completing the deployment successfully. A new discovery range will be added when needed. Editing the device specific attributes Alternatively, you can import and export the grid to file to edit. You may want to export/import if you have a large number of devices with a large number of device specific attributes.
Executive summary 7 Auto-deploy configuration templates Auto deploying the templates applies to all the attribute values of the templates to the device, after it is discovered. 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 the template, you must first create the template.
Technical support and resources 4. Select a server or chassis template (as applicable to the type of target devices) to be deployed on the target servers or chassis, and then click Next. 5. Click the Import button to import the csv file that contains the Service Tags. The imported Service Tags must be compatible with the type of template selected in the step Error! Reference source not found.. 6. Browse to the location where the file is saved, select the file, and then click Open.
Executive summary Note—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.
Technical support and resources 8 Create Chassis baseline or MX Chassis baseline Example use case—you have a blade chassis (new or existing) or MX Chassis (new or existing) for which you want to create the configuration baseline. To accomplish this use case: 1. 2. 3. 4. 5. 6. Click ManageConfiguration. In the left pane, click Create Baseline under Common Tasks. Type a unique name for the template. Select Create from Device. Select Device Type as Chassis or MX Chassis.
Executive summary Create MX chassis baseline 26 Managing Modular Infrastructure by using OpenManage Essentials (OME)
Technical support and resources Create chassis baseline 8. Click Finish. 9. Click OK. The task is created when the wizard is closed. 10. To view the created task, navigate to a) Tasks Configuration Tasks Chassis Baseline Configuration Import (if you have selected Chassis as device type) b) Tasks Configuration Tasks MX Chassis Baseline Configuration Import (if you have selected MX Chassis as device type) c) Click Tasks. 11. To view the progress of the task, view the Task Execution History grid.
Executive summary 12. To view the details of the execution history, double-click the task execution history entry, or right-click the task execution history entry and select Details. The details provide you the information (such as incorrect credentials). 13. If the task is successful, the baseline is created and displayed in the Chassis Baselines (if you have created baseline for Chassis) or MX Chassis Baselines (if you have created baseline for MX Chassis) tree. 14.
Technical support and resources 9 Associate devices to Chassis Configuration baseline or MX Chassis Configuration baseline Example use case—you have a new Chassis baseline or MX Chassis baseline created, for which you want to associate the devices. To accomplish this use case: 1. Click Manage Configuration. 2. Click the new Chassis Baseline in Chassis Baselines or new MX Chassis Baseline in MX Chassis Baselines tree. Associate devices to configuration baseline 3. Click Associate Devices. 4.
Executive summary Associating target devices to chassis baseline Note—If you associate devices with a different configuration baseline while the Make Device(s) Compliant task is running, the latest baseline is considered by the task for remediation of these devices.
Technical support and resources 10 View compliance of devices associated to the Chassis baseline or MX Chassis baseline Example use case—you have a new chassis baseline or a new MX Chassis baseline created for which you want to view the compliance of devices associated to the chassis baseline. To accomplish this use case: 1. Click Manage Configuration. 2. Click the new Chassis Baseline template in the Chassis Baselines or new MX Chassis Baseline template in MX Chassis Baselines tree.
Executive summary View Compliance of Associated Devices to a Chassis Baseline 3. In Device Compliance tab, right-click the non-compliant device. 4. Click View Compliance Details. The non-compliant attributes are displayed.
Technical support and resources View Non-Compliant Attributes of Associated Devices to the Chassis Baseline 33 Managing Modular Infrastructure by using OpenManage Essentials (OME)
Executive summary 11 Make the associated devices compliant to Chassis baseline or MX Chassis baseline Example use case—you have a Chassis baseline or MX Chassis baseline for which some of the associated devices are not compliant. To accomplish this use case: 1. Click Manage Configuration. 2. Click the new Chassis Baseline in Chassis Baselines tree or new MX Chassis Baseline in MX Chassis Baselines tree. 3. Under Device Compliance, right-click any non-compliant device. 4. Select Make Compliant.
Technical support and resources Make devices compliant 9. To make the Server or iDRAC compliant, navigate to the Options step, and then click Next. 10. Set the schedule when the deploy template task runs. Run now will run the task when the wizard is closed. Run at will run the task on the selected future time. Type the credentials for all target devices. The credentials must be valid for all target devices and must have the Operator or Administrator privileges on target devices. 11. Click Next. 12.
Executive summary 12 Upgrade old Chassis templates In OME 2.3, the Chassis Templates are enhanced to provide: User-friendly attribute names Enhanced deployment task details with detailed status reporting for changed/failed attributes After upgrading the OME version to 2.3, all the old chassis templates (created in the OME version 2.2 or earlier) will be shown with a broken icon in Deployment Portal. The old templates can be recreated by using the Recreate this Template option.
Technical support and resources 13 Upgrade the existing Chassis Templates (created by using OME 2.3 and earlier versions) Example use case—you want to use existing chassis templates (created in OME version 2.2 or earlier) in OME 2.3 after the version upgrade. This section describes how to upgrade the chassis template (created in OME 2.2 or earlier) and use them in OME 2.3. The OME 2.3 uses enhanced version of the chassis template. For more details, see Upgrade old Chassis templates.
Executive summary Existing CMC Templates (Created in OME 2.2 or Earlier) After Upgrade 8. Click Recreate this Template. Recreate this Template Dialog 9. In the Task Authentication dialog box, type the credentials for CMC device. 10. If you want to capture the IOA templates on that chassis to create a Chassis Infrastructure template (containing the CMC device and all the IOAs), type the IOA credentials. 11. Click Ok. The task is created to upgrade the existing template.
Technical support and resources CMC Template Recreate Task 39 Managing Modular Infrastructure by using OpenManage Essentials (OME)
Executive summary 14 Recreate Chassis baselines Example use case—after upgrading the OME to version 2.3, you want to use the compliance feature for the devices associated to existing chassis templates (created by using OME 2.2 or earlier versions). This section describes how to recreate the chassis baseline templates (created in OME 2.3 after the upgrade) and use them with Device Compliance features. After upgrade, OME 2.3 creates a new chassis baseline template for all the existing CMC templates.
Technical support and resources Recreate baseline dialog 5. In the Task Authentication dialog, type the credentials for CMC device. 6. Click Ok. The Create Baseline Template task is created.
Executive summary 15 Check configuration compliance of devices in OpenManage Essentials Configuration compliance detects drift of a device’s attributes from the template’s attributes. The configuration inventory process acquires configuration information (inventory) from all the applicable devices, and compares the inventory against an associated compliance template. Note—Device configuration compliance feature is not available for Dell Networking IOAs. 15.
Technical support and resources Configuration Inventory Credentials Page 9. Ensure that Enable Configuration Inventory is selected. 10. Select the schedule—either every week on the same day and time or every day or hour interval. The Execution histories for the configuration inventory are displayed in the Task Execution History grid. 11. Double-click the Execution History to view task details or right-click the Execution History row and select the details. 15.2.
Executive summary 15.3 View and Leverage the compliance report The device compliance panel shows the configuration compliance status and state of all eligible devices. See Target Device Requirements. To view all the devices and its state, click a slice of the pie chart. Device configuration compliance can be viewed in the Configuration tab under the Manage tab. Eligible Device Compliant Devices Not Compliant Devices Not Inventoried Devices Devices without license 44 Required Action No action required.
Technical support and resources 16 Create the template from a reference IOA To create the template from the reference IOA: 1. 2. 3. 4. 5. Select the Deployment tab. In the left pane, click Create Template under Common Tasks. Type a unique name for the template. Select Create from Device. In the device type selection, select the target IOA. Note—Alternatively, you can select the target by typing the device name or Service Tag in the search box next to the Create from Device button. 6.
Executive summary Create IOA template from reference device wizard 13. 14. 15. 16. 17. 18. 19. 20. Click Finish. Click OK. The task is created when the dialog box is closed. In the Deployment portal, click Tasks. To view the progress of the task, Click Task Execution History. To view the details of the execution history, double-click or right-click the task execution history entry. Select Details. The details provide the information (such as incorrect credentials, etc.).
Technical support and resources Create template task of IOA 47 Managing Modular Infrastructure by using OpenManage Essentials (OME)
Executive summary IOA template 48 Managing Modular Infrastructure by using OpenManage Essentials (OME)
Technical support and resources 17 Deploy an IOA template This section describes how to deploy an IOA template to IOAs. 17.1 Deploy an IOA template to IOA device To deploy the IOA template to IOA device: 1. Select Deployment. 2. In the left pane, click Deploy Template under Common Tasks. 3. Type a unique name for the task. Note—This step is optional since a default name is supplied, but it is a generic name. It is recommended to type the name relevant to what is being deployed. 4. 5. 6. 7. 8. 9. 10.
Executive summary 4. Click Save. 5. Repeat for each device. Edit Attributes pane Alternatively, you can import and export the grid to file to edit. You may want to export or import if you have a large number of devices with a large number of device specific attributes. The device specific attributes grid can be exported by using the selected device or all devices. All devices will export to a single file that can be opened in a spreadsheet processing application.
Technical support and resources 18 Create a template from a file 18.1 Create a template from a TXT File The TXT format is for IOA devices and creating a template from a TXT file will create the IOA template.
Executive summary 18.2 Create a template from an XML File The XML format is for Chassis devices and creating a template from an XML file will create the Chassis template. To create the template from an XML file: 1. 2. 3. 4. 5. 6. Navigate to the Deployment tab. In the left pane, click Create Template under Common Tasks. Type a unique name for the template. Select Create from File. Click Browse and browse to the file’s location. Select the file and click Open. Create Template from an XML File 7.
Technical support and resources 18.3 Create a template from a JSON File The JSON format is for MX Chassis devices and creating a template from a JSON file will create the MX Chassis template. To create the template from a JSON file: 1. 2. 3. 4. 5. 6. Navigate to the Deployment tab. In the left pane, click Create Template under Common Tasks. Type a unique name for the template. Select Create from File. Click Browse and browse to the file’s location. Select the file and click Open.
Executive summary 19 Export a Chassis Infrastructure template or an MX Chassis template 1. Select Deployment. 2. In the left pane, right-click Chassis Templates or MX Chassis Templates under Common Tasks. 3. Click Export Template. Export Template 4. In the Export Template dialog, select Ok. 5. In the Save As dialog box, type a filename for the exported chassis infrastructure template or MX Chassis template. The chassis infrastructure template will be exported in .zip format. The .
Technical support and resources 20 Troubleshoot issues in managing Modular Infrastructure by using OpenManage Essentials 20.1 Troubleshoot the File Share issues in managing Modular Infrastructure To troubleshoot 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 is in the Deployment Settings preference. File Share Settings Status 2. Check the domain, username, and password. 3. Check the share folder in Windows Explorer. 4.
Executive summary Advanced Sharing Tab of the ServerConfig Folder 7. Verify the share folder location by using the net share command. 8. Open the command prompt and type net share. A share with the name ServerConfig should be in the network share list.
Technical support and resources 9. In the User Accounts window, check the user permissions. 20.2 Troubleshoot the template creation in OpenManage Essentials To troubleshoot the creation of template from a reference device: 1. Make sure that the file share settings are configured correctly. See Set up a file share or Troubleshoot the File Share issues in managing Modular Infrastructure. 2. Right-click the task or task execution history and select Run. 3.
Executive summary 20.4 Troubleshoot the Auto-deploying templates Whenever the Deploy Configuration to Undiscovered Devices task is executed, it looks for Service Tags in the Auto Deployment list. The following situations may be encountered: 20.5 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.
Technical support and resources Troubleshoot configuration compliance in OpenManage Essentials 59 Managing Modular Infrastructure by using OpenManage Essentials (OME)
Executive summary A Technical support and resources Dell.com/support is focused on meeting customer needs with proven services and support. A.1 Related resources Referenced or recommended Dell publications: 60 Dell OpenManage Essentials TechCenter page: http://en.community.dell.com/techcenter/systems-management/w/wiki/1989.openmanageessentials.aspx Chassis discovery feature in OME: http://en.community.dell.
