Dell EMC OpenManage Essentials Version 2.
Notes, cautions, and warnings NOTE: A NOTE indicates important information that helps you make better use of your product. CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem. WARNING: A WARNING indicates a potential for property damage, personal injury, or death. Copyright © 2017 Dell Inc. or its subsidiaries. All rights reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries.
Contents 1 About OpenManage Essentials....................................................................................... 19 What is New in This Release............................................................................................................................................. 19 Other information you may need...................................................................................................................................... 20 Contacting Dell............................
Customizing Portals......................................................................................................................................................... 40 Displaying Additional Available Reports and Graphs...........................................................................................................41 Drilling Down Charts and Reports for More Information..............................................................................................
Scheduling Discovery....................................................................................................................................................... 65 Discovery Speed Slider...............................................................................................................................................66 Multithreading...........................................................................................................................................................
Discovery Ranges.............................................................................................................................................................82 Exclude Ranges................................................................................................................................................................83 7 Managing Devices......................................................................................................... 84 Viewing Devices................
Right-Click Actions................................................................................................................................................... 104 Navigation Trail......................................................................................................................................................... 104 Support For PowerEdge FX Chassis Sleds.....................................................................................................................
Creating a Device Deployment Template.........................................................................................................................122 Creating a Device Deployment Template from a Device Configuration File................................................................123 Creating a Device Deployment Template From a Reference Device.......................................................................... 123 Managing Device Deployment Templates....................................
Removing a Server From a Compute Pool................................................................................................................ 152 Renaming a Compute Pool........................................................................................................................................152 Deleting a Compute Pool.......................................................................................................................................... 152 Replacing a Server...........
Name and Deploy Options.........................................................................................................................................179 Select Template........................................................................................................................................................ 179 Select Devices..........................................................................................................................................................
Remediating Non-Compliant Devices............................................................................................................................. 208 Viewing the Compliance Tasks....................................................................................................................................... 209 Viewing Backed-up Profile.............................................................................................................................................
Processor Information.............................................................................................................................................. 230 Storage Controller Information.................................................................................................................................. 231 Virtual Disk Information.............................................................................................................................................
Forwarding Alerts Use Case Scenarios.....................................................................................................................248 Working With Sample Alert Action Use Cases................................................................................................................ 249 Use Cases in Alert Actions.......................................................................................................................................
Manage MIBs Pane..................................................................................................................................................269 Manage Traps Pane..................................................................................................................................................269 Import MIB...............................................................................................................................................................
20 Managing Remote Tasks............................................................................................293 About Remote Tasks...................................................................................................................................................... 293 Managing Command Line Task.......................................................................................................................................293 Managing RACADM Command Line Tasks....................
Troubleshooting Device Discovery............................................................................................................................325 Troubleshooting Receiving SNMP Traps ..................................................................................................................325 Troubleshooting Discovery of Windows Server 2008–Based Servers...................................................................... 326 Troubleshooting SNMP Traps for ESX or ESXi Versions 3.5, 4.
Alert Settings................................................................................................................................................................. 349 Custom URL Settings.................................................................................................................................................... 350 Deployment Settings.............................................................................................................................................
Launching the OpenManage Essentials Command Line Interface.................................................................................. 368 Creating a Discovery Profile Input File............................................................................................................................368 Specifying IPs, Ranges, or Host names Using XML or CSV Files....................................................................................369 Specifying Input Files in PowerShell................
1 About OpenManage Essentials OpenManage Essentials is a hardware management application that provides a comprehensive view of systems, devices, and components in the enterprise’s network. With OpenManage Essentials, a web-based and one‑to‑many systems management application for systems and other devices, you can: • Discover and inventory the system. • Monitor the health of the system. • View and manage system alerts. • Perform system updates and remote tasks.
– Enabling support of Programmable MUX (PMUX) mode for VLAN configuration and VLAN deployment features on IOAs. – Capability to export the discovery ranges. – Ability to view the virtual I/O pool size of the I/O identity types during the creation of a virtual I/O pool. – Capability to purge older task execution history records when the limit is exceeded. – New capabilities and enhancements on the REST interface.
Dell provides several online and telephone-based support and service options. Availability varies by country and product, and some services may not be available in your area. To contact Dell for sales, technical support, or customer service issues: 1. Go to Dell.com/support. 2. Select your support category. 3. Verify your country or region in the Choose a Country/Region drop-down list at the bottom of the page. 4. Select the appropriate service or support link based on your need.
2 Installing OpenManage Essentials Related link Downloading OpenManage Essentials Installation Prerequisites and Minimum Requirements Installing OpenManage Essentials Migrating IT Assistant to OpenManage Essentials Installation Prerequisites and Minimum Requirements For a list of supported platforms, operating systems, and browsers, see the Dell EMC OpenManage Essentials Support Matrix at dell.com/OpenManageManuals.
Minimum Login Roles for Microsoft SQL Server The following table provides information about the minimum permissions for SQL Server based on different installation and upgrade use cases. Table 2. Minimum Login Roles for Microsoft SQL Server Number Use Case Minimum Login Roles for SQL Server 1 Installing OpenManage Essentials for the first time and you select the Typical option during the installation process. sysadmin access on the installed instance.
Downloading OpenManage Essentials To download OpenManage Essentials, go to dell.com/support or the Dell TechCenter website at DellTechCenter.com/OME. Installing OpenManage Essentials Before you install OpenManage Essentials, make sure that you have local administrator rights on the system. To install OpenManage Essentials: 1. Extract the OpenManage Essentials installation package. 2. Double-click the Autorun.exe file available in the folder where you extracted the installation package.
5. In the install wizard for OpenManage Essentials, click Next. 6. In the License Agreement page, read the license agreement, select I accept the terms in the license agreement, and then click Next. 7. In Setup type select either Typical or Custom installation. • If you selected Typical, click Next. Verify the installation settings in the Ready to Install the Program page and the click Install.
NOTE: If you select the Custom install option, you can customize the database name. You can enter any name of your choice in the Database Name field. If you do not enter a database name, by default, OMEssentials is selected. Typically, you can use the database name field in a scenario where you have a dedicated remote SQL server that you want to use for installing multiple OpenManage Essentials instances.
3. Right-click the OMEssentials database and then click Tasks → Back Up. The Back Up Database - OMEssentials window is displayed. 4. Click OK to start the database back up. A confirmation message is displayed after the database back up is completed. The OpenManage Essentials database back up file, OMEssentials.bak, is saved at C:\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESSOME\MSSQL\Backup.
The new user that you created is displayed under Security → Logins in Object Explorer. Connecting to the OpenManage Essentials Database To connect to the OpenManage Essentials database: 1. On the system where OpenManage Essentials is installed, open the command prompt, and run the following command: sqlcmd -E -S ".\SQLEXPRESSOME" -Q "ALTER LOGIN [OMEService] WITH PASSWORD='DummyPassword'" NOTE: Verify that the OpenManage Essentials database instance that was created during the typical installation is SQLE
• Ensure that TCP/IP is enabled in SQL Server. See Verifying the SQL Server TCP/IP status. After OpenManage Essentials is installed on a domain controller: • By default, the Domain Admins group is added as a member of the OmeAdministrators and OmePowerUsers roles. • Local Windows user groups are not included in the OpenManage Essentials roles. OmeAdministrators, OmePowerUsers, or OmeUsers rights can be granted to users or user groups by adding them to the OpenManage Essentials Windows groups.
Installing OpenManage Essentials on a Domain Controller With a Local Database Before you begin installing OpenManage Essentials on a domain controller, ensure that you are logged in to the domain controller with administrator rights. To install OpenManage Essentials on a domain controller with a local database: 1. Extract the OpenManage Essentials installation package. 2. Double-click the Autorun.exe file available within the folder where you extracted the installation package.
NOTE: The users you add to the OpenManage Essentials user group must also belong to the built-in local Administrator group. For information on adding a Windows user account to a group, see “Adding a user account to a group” at support.microsoft.com 1. Open Server Manager. 2. Click Tools → Computer Management. 3. In the left pane, click Local Users and Groups → Groups. 4. In the right-pane, right-click OmeAdministrators and select Add to Group. 5.
NOTE: If the installation of SupportAssist Enterprise fails, you can retry the installation later. To retry the installation, right-click the Dell EMC SupportAssistSetup.exe file available at C:\Program Files\Dell\SysMgt\Essentials \SupportAssistSetup and select Run as administrator. 1. Extract the OpenManage Essentials installation package. 2. In the folder where you extracted the installation package, double-click the Autorun.exe file. The OpenManage Install window is displayed. 3.
To install Repository Manager: 1. Double-click the OpenManage Essentials executable file. 2. In OpenManage Install, select Dell EMC Repository Manager, and then click Install. 3. In Dell EMC Repository Manager - InstallShield Wizard, click Next. 4. In License Agreement, select I accept the terms in the license agreement, and click Next. 5. In Customer Information, do the following and click Next. a. Provide user name and organization information. b.
NOTE: If SupportAssist Enterprise is already installed on the system, by default, the Dell EMC SupportAssist Enterprise option is selected and disabled. After the upgrade of OpenManage Essentials, SupportAssist Enterprise is also upgraded. If applicable, you may be required to provide the proxy settings during the upgrade of SupportAssist Enterprise. For more information, see the Dell EMC SupportAssist User’s Guide at dell.com/ ServiceabilityTools. • 2. Documentation — Click to view the online help.
After the upgrade is complete, you must perform the following tasks: • • • • From the Deployment portal, recreate the Chassis Template. For more information, see Recreating Chassis Template. From the Manage → Configuration portal, recreate the Chassis Baseline. For more information see Recreating Chassis Baseline.
NOTE: The chassis baseline which is created from the file do not display the Recreate this Template button and has to be recreated manually from the chassis configuration file. Uninstalling OpenManage Essentials NOTE: Before uninstalling OpenManage Essentials, you must uninstall OpenManage Essentials MIB Import Utility and SupportAssist Enterprise (if installed). To uninstall OpenManage Essentials: 1. Click Start → Control Panel → Programs and Features. 2.
3 Getting Started With OpenManage Essentials Launching OpenManage Essentials To launch OpenManage Essentials, do one of the following: NOTE: Before you launch OpenManage Essentials, ensure that Javascript is enabled on your web browser. • From the management station desktop, click the Essentials icon. • From the management station desktop, click Start → All Programs → Dell EMC OpenManage Applications → Essentials → Essentials. • From a local or remote system, launch a supported browser.
Discovery Wizard Configuration The Discovery Wizard Configuration window enables you to configure the type of wizard you want to use for discovering devices. The options displayed in the Discovery Wizard Configuration window are described in the following table. Table 4. Discovery Wizard Configuration Option Description Standard Wizard If selected, the Discover Devices wizard displays a list of protocols for discovering devices.
The Discovery Settings page is displayed. 2. Select one of the following: • Standard Wizard — If selected, the Device Discovery wizard displays a list of protocols for discovering devices. • Guided Wizard — If selected, the Device Discovery wizard displays a list of device types and the required protocols for discovering and managing the selected devices. After the required protocol configurations are completed, by default, this wizard runs both discovery and inventory.
OpenManage Essentials Heading Banner The banner may display the following icons: • Critical icon and Warning icon in either state. including the number of devices. You can click the icon or the number to view the devices • OpenManage Essentials service not running icon (blinking down arrow) restart the service. • Update available notification icon indicates if a newer version of OpenManage Essentials is available.
• Home portal, see OpenManage Essentials Home Portal Reference. • Device portal, see Devices Reference. • Discovery and inventory portal, see Discovery And Inventory Reference. • Reports portal, see Reports Reference. . Displaying Additional Available Reports and Graphs Charts have drill-down feature. To view additional reports and graphs, click the Figure 2. Adding additional reports and graphs icon icon on the top right corner.
• In report tables, use the drag and drop option or funnel options to filter the required data and right-click the table rows to perform various tasks. Saving and Loading the Portal Layout To save and load the portal layout, click the Figure 4. Save icon icon. All the current layout settings and visible reports on the portal are saved on the portal page. To load the previous portal layout, click the Figure 5. Loading the previous portal layout icon. icon.
Rearranging or Resizing Graphs and Reports—Components Click the icon and select from the following options: • Floating — To move the component freely in the portal page. • Dockable — To dock the component in the portal page. If the component is floating, right-click the title to dock or tab the component. • Tabbed Document — To move the component into a tab in the portal page. Select the Figure 10. Docking icon. control to dock a floating component.
Related link Search Items Search Drop-Down List Selection Actions Search Items You can search for the following using the search bar: • Devices • Device groups • Discovery ranges • Discovery range groups • Exclude ranges • Portals • Wizards • Remote tasks • Preferences and settings When a range, task, device, and so on is changed or created in the console, it is added to the searchable items within 20 seconds.
Related link Search Bar Map View—Home Portal NOTE: The Map View feature is available only if you have discovered any PowerEdge VRTX or PowerEdge FX2/FX2s devices that have an Enterprise license using the WS-Man protocol. If the licensed device is discovered using the SNMP protocol, the Map View feature is not available. In this case, you must rediscover the device using the WS-Man protocol. The Map View (home) portal can be accessed by clicking the Map View link in the Home portal.
Related link Using the OpenManage Essentials Home Portal OpenManage Essentials Heading Banner Using the Update Available Notification Icon NOTE: The update available notification icon may be displayed in the OpenManage Essentials heading banner only after you refresh the web browser.
4 OpenManage Essentials Home Portal — Reference Related link OpenManage Essentials Heading Banner Dashboard Schedule View Search Bar Map View Interface—Home Portal Dashboard The dashboard page provides a snapshot of the managed devices that include servers, storage, switches, and so on. You can filter the view based on the devices by clicking the Filter by: drop-down list. You can also add a new group of devices from the dashboard by clicking Add New Group from the Filter by: drop-down list.
• Storage Controller Information • Task Status Device by Status Device by Status provides device status information in a pie chart format. Click a segment of the pie chart to view the device summary. Table 6. Device by Status Field Description Unknown Health status of these devices are not known. Normal Devices are working as expected. Warning These devices display behaviors that are not normal and further investigation is required.
Related link Creating a Discovery and Inventory Task Viewing Configured Discovery and Inventory Ranges Excluding Ranges Scheduling Discovery Scheduling Inventory Configuring Status Polling Frequency Discovery and Inventory Portal Task Status The grid provides a list of currently executing and previously run tasks and their status. The Task Status grid on this page shows the status of just discovery, inventory, and tasks. However, the main portal shows all types of task statuses.
Field Description NOTE: Changing the Orientation setting does not affect the Month view. Schedule Item Size Allows you to modify the size of the tasks displayed. Color Categorize by Task Type Selecting this option categorizes each task type using a different color. Show Task Execution History Select this option to display the tasks that are already complete. Show Database Maintenance Select this option to view the time at which database maintenance occurs.
Field Description End Date Displays the date on which the warranty will expire. Days Remaining Displays the number of days the warranty is available for the device. Related link Using the Warranty Scoreboard Notification Icon Configuring Warranty Scoreboard Notifications Map View Interface—Home Portal The Map View (home) portal accessible through the Home portal has a Filter by drop-down list which you can use to filter the device group displayed on the map.
5 Discovering and Inventorying Devices Perform Discovery and Inventory to manage your network devices. Related link Creating a Discovery and Inventory Task Viewing Configured Discovery and Inventory Ranges Scheduling Discovery Scheduling Inventory Excluding Ranges Supported Devices, Protocols, and Features Matrix—SNMP, WMI, and Ws-Man Supported Devices, Protocols, and Features Matrix—SNMP, WMI, and Ws-Man NOTE: For a description of the features listed in the following table, see Legend and Definitions.
Protocol / Mechanism VMware ESXi Servers without Windows/Hyper‑V OpenManage Server Administrator installed Simple Network Management Protocol (SNMP) Windows Management Instrumentation (WMI) Web ServicesManagement (WS-Man) Traps/alerts Not supported Discovery Correlation Classification Hardware inventory Software inventory Virtual machine information Virtual host product information Monitoring (OpenManage Server Administrator health only) Application launch — RAC Not supported Discovery Correlation
Protocol / Mechanism Simple Network Management Protocol (SNMP) Windows Management Instrumentation (WMI) Monitoring Traps/Platform Event Traps (PET) Application launch • • Web ServicesManagement (WS-Man) Monitoring Traps/Platform Event Traps (PET) Hardware inventory Application launch RAC Console • • • • RAC Console VxRail Manager PRISM NOTE: OpenManage Essentials does not support remote task execution, server configuration, and system updates on the VxRail and XC Series devices.
Protocol / Mechanism Simple Network Management Protocol (SNMP) Windows Management Instrumentation (WMI) Web ServicesManagement (WS-Man) Application launch Traps/alerts Networking Ethernet switches Discovery Correlation Classification Application launch Traps/alerts Health Switch Role Not supported Not supported Brocade Fibre Channel switches Discovery Classification Application launch Traps/alerts Health Switch role Not supported Not supported NOTE: For full functionality of chassis support in O
Protocol / Mechanism Intelligent Platform Management Interface (IPMI) Command Line Interface (CLI)a Secure Shell (SSH) Deploy OpenManage Server Administrator Server Updates Classification Hardware and Software Inventory (minimal) • • • BIOS Firmware Driver VMware ESXi Not supported Not supported Discovery Correlation Classification Hardware and Software Inventory (minimal) XenServer Not supported RACADM CLI IPMI CLI OpenManage Server Administrator CLI Power Task Not supported Windows/Hyper-V
NOTE: Correlation of PowerEdge FC430, FC630, or FC830 sleds under the host chassis is not supported in the following scenarios: • The sleds are discovered using WMI protocol (in-band) and do not have OMSA installed. • The sleds are discovered using IPMI protocol (out-of-band). • The sleds are running ESXi and either have or do not have OMSA installed.
Protocol / Mechanism Simple Network Management Protocol (SNMP) Symbol EMC NaviSphere CLI Not supported Not supported Classification Hardware inventory Monitoring Traps/alerts Application launch — Compellent console Tape Discovery Classification Hardware inventory Monitoring Traps/alerts Application launch — Tape console a) Requires Modular Disk Storage Manager Controller software installed on the OpenManage Essentials system.
For more information on setting up and configuring ESXi 5, see the How to setup and configure ESXi 5 for use in OME whitepaper at delltechcenter.com/ome. Legend and Definitions • Discovery: Capability to discover the devices on the network. • Correlation: Capability to correlate: – CMC with servers, switches, RAC, and storage. – Discovered server and DRAC, iDRAC, or BMC devices. – Discovered modular systems or switches. – ESX, ESXi, or Hyper-V host and guest virtual machines.
Protocol Support Matrix for Discovery The following table provides information about the supported protocols for discovering devices. The recommended protocol is indicated by the text in italics. Table 14.
1 Supported with OpenManage Server Administrator (OMSA) installed. 2 Supported using the inventory collection method. 3 Supported; requires iDRAC to be discovered and updated through out-of-band channel. 4 Supported; requires the RACADM tool.
NOTE: After completing any of the following steps, click either Next to continue or click Finish to complete the Discovery Range Configuration. • In ICMP Configuration, to detect devices on the network, edit the ICMP parameters. NOTE: The ICMP Configuration window is not displayed if Skip ICMP ping during discovery setting is selected under Settings → Discovery Settings. • In SNMP Configuration, to discover servers, provide the SNMP parameters. You can select SNMP V1/V2c or SNMP V3 for discovery.
To configure the managed node and OpenManage Essentials to use a non-default SNMP port: 1. In both the management station and managed node, go to C:\Windows\System32\drivers\etc. 2. Open the Windows SNMP services file using Notepad and edit the following: • Incoming SNMP trap port (receiving alerts in OpenManage Essentials) — Modify the port number in the line, snmptrap 162/udp snmp-trap #SNMP trap. Restart the SNMP trap service and SNMP service after making the change.
NOTE: Ensure that the certificate file you want to install is a Base64 encoded certificate file issued by root CA. a. Right-click the certnew.cer file, and click Install Certificate. The Certificate Import Wizard is displayed. b. Click Next. c. Select Place all certificates in the following store and click Browse. The Select Certificate Store dialog box is displayed. d. Select Trusted Root Certification Authorities, and click OK. e. Click Next. f. Click Finish. The Security Warning dialog box is displayed.
• To disable the auto discovery of iDRACs and switches, clear the Auto discover iDRACs and switches in the CMC option. • To provide alternate credentials for discovering the iDRACs, clear the Use same credentials of CMC for discovering iDRACs option, and type the iDRAC username and password in the appropriate fields. 11. Click Next. The Summary page is displayed. 12. Click Finish. Discovery of the chassis and its components (iDRACs and IOA switches) is initiated.
Discovery Speed Slider This control, also known as the discovery throttle, controls how fast discovery occurs and how much network and system resources are consumed for discovery by controlling the: • Number of discovery threads that are allowed to run at any point of time. • Delay in between the communicating devices during a network ping sweep, in milliseconds. NOTE: Each tick on the throttle control equals 10% and the range is from 10% to 100%.
Configuring Status Polling Frequency NOTE: It is recommended not to schedule status polling at the same time as the Database Maintenance Execution Schedule, as the console is less responsive during database maintenance. You can configure OpenManage Essentials to check the health status of all discovered devices that have a means of health instrumentation such as OpenManage Server Administrator. The status can be scheduled at a given interval using Status Polling so that health status is always current.
The Task Notification Settings page is displayed. 2. Under Task Popup Notification Settings, select or clear Enable Task Popup Notifications to enable or disable task pop-up notifications. 3. In the seconds between popup notifications box, select the time interval between each pop-up notification. 4. Click Apply.
6 Discovery And Inventory — Reference From the Discovery and Inventory portal page, you can: • View graphical reports on devices and servers discovered and inventoried. • Manage discovery ranges for devices and servers. • Configure discovery, inventory, and status polling for devices and servers.
Last Discovery and Inventory Table 16. Last Discovery and Inventory Field Description Last Discovery Details Discovery Last Run at Displays the time and date information for the last run discovery. Discovery Range Displays the IP Address range or host name. Devices Discovered Displays information on number of devices discovered. Last Inventory Details Inventory Last Run at Displays the time and date information for the last run inventory.
Task Status The grid provides a list of currently executing and previously run tasks and their status. The Task Status grid on this page shows the status of just discovery, inventory, and tasks. However, the main portal shows all types of task statuses. Related link Creating a Discovery and Inventory Task Viewing Configured Discovery and Inventory Ranges Excluding Ranges Scheduling Discovery Scheduling Inventory Configuring Status Polling Frequency Discovery and Inventory Portal Viewing Device Summary 1.
Field Description • Off Add Discovery Range 1. Click Manage → Discovery and Inventory → Common Tasks. 2. Click Add Discovery Range. For more information, see Creating a Discovery and Inventory Task. 3.
Field Description Host name Specifies the host name, for example, mynode.mycompany.com. Click Add to add multiple host names. NOTE: You can add multiple host names by separating them using commas. NOTE: Invalid characters in the host name are not checked. If the host name you provide contains invalid characters, the name is accepted. However, the device is not found during the discovery cycle. Subnet mask Specifies the subnet mask for the IP address range.
Table 20. Device Type Filtering Field Description Device Type Displays the device types that you can select to discover and manage. Required Protocol Displays the protocols that are required to discover and manage the selected device types. ICMP Configuration ICMP is used to by discovery engine to determine whether or not any device has a specified IP address. The discovery engine sends out a request and waits until the 'timeout' period to receive a reply.
SNMP Configuration Options Table 22. SNMP Configuration Options Field Description Enable SNMP discovery Enables or disables the SNMP protocol for discovery range (subnet). Enable SNMP V1/V2c Get community Specifies the community name for SNMP get calls from the OpenManage Essentials user interface. The Get Community is a read-only password that SNMP agents installed on managed devices use for authentication. The Get Community allows OpenManage Essentials to browse and retrieve SNMP data.
Field Description attempts have timed out. A valid range is 1–10 retries. The default is 2. WMI Configuration Use the WMI protocol for gathering discovery, inventory, and health information about servers running Windows. This protocol provides less information about devices than SNMP but is useful if SNMP is disabled on the network. See WMI Configuration Options to configure WMI parameters for Windows servers only. WMI Configuration Options Table 23.
WS-Man Configuration Options Table 25. WS-Man Configuration Options Field Description Enable WS-Man Discovery Select to discover PowerEdge FX, PowerEdge VRTX, iDRAC6, iDRAC7, iDRAC8, and ESXi installed devices. User ID Provide authenticated user ID. Password Provide password. Timeout (seconds) Specifies the maximum number of seconds the discovery engine waits after issuing a WS-Man connection request. A valid range is from 1 to 360 seconds. The default is 15 seconds.
Field Description Password Provide the password. Port Specifies the port information. The default port number is 22. Retries (attempts) Specifies the maximum number of additional times that the discovery engine will send an SSH connection request to a device if the first request times out. The discovery engine reissues the request until it is successful, or all retry attempts have timed out. A valid range is from 1 to 10 retries. The default value is 3.
Discovery Range Action Select these options to discover or inventory devices, components, and servers. Table 29. Discovery Range Action Field Description Do not perform discovery or inventory Select this option to set up a schedule to perform discovery and inventory (at a later time). Perform only discovery Select this option to perform discovery. Perform both discovery and inventory Select this option to perform both discovery and inventory. Summary View the configuration selections.
Discovery Schedule You can configure OpenManage Essentials to discover devices and display them in the Device tree. • Enable device discovery. • Initiate device discovery. • Set the discovery speed. • Specify how devices are discovered. • For failed discovery attempts, use the Troubleshooting Tool. Related link Discovery Schedule Settings Viewing Discovery Configuration To view discovery configuration, click Manage → Discovery and Inventory → Discovery Schedule.
Field Description independent system. If you are not managing a cluster, a DNS name resolution is recommended. • • DNS — Select to resolve names using the Domain Naming Service. NetBIOS — Select to resolve names using system names. Related link Discovery Schedule Inventory Schedule Use Inventory Polling to specify the default inventory settings for OpenManage Essentials.
Status Polling Schedule Settings Table 33. Status Polling Schedule Settings Field Description Enable OnDemand Poll Select to query the global status of the device when an alert is received from the device. NOTE: If a large number of alerts are received, multiple OnDemand polls are queued up and it may affect the system performance. In this scenario, it is recommended to turn off OnDemand poll and enable the regular status poll interval to retrieve the health status of managed devices.
Exclude Ranges The Exclude Ranges section displays the IP address or IP address ranges that you have configured to exclude from the discovery process.
7 Managing Devices OpenManage Essentials lists devices based on their types. For example, PowerEdge servers are listed under the device type Servers. OpenManage Essentials contains a defined list of device types. The devices you discover and inventory are included under these device types. Unclassified devices are listed under the device type Unknown. You can create device groups with combinations of the defined device types. However, you cannot create a new device types.
– NAS Clusters • Hyper-Converged Infrastructure – VxRail – XC Series • KVM • Microsoft Virtualization Servers – Virtual machines • Modular systems – PowerEdge Chassis – PowerEdge FX2 – PowerEdge M1000e – PowerEdge VRTX • Network Devices – Networking Switches – Fibre Channel Switches – Network Appliances • OEM Devices • OOB Unclassified Devices – IPMI Unclassified Devices • Power Devices – PDU – UPS • PowerEdge C Servers • Printers • RAC NOTE: If a DRAC or iDRAC is discovered, it is disp
Use the refresh button to update the device tree with the current data. To update the device tree, right-click All Devices and select Refresh. NOTE: The device tree auto-updates when changes are made. Some changes to the tree may appear after a brief delay depending on the performance of the managed servers because the information propagates from the SQL database to the user interface. Nodes and Symbols Description Table 34. Nodes and Symbols Description Node Symbol Figure 15.
• • • • • • • • • • • • • • Embedded Device Information Device Card Information Controller Information Controller Battery Information Enclosure Information Physical Disk Information Virtual Disk Information Contact Information Appliance Node Information Switch Device Information EqualLogic Volume Information Device Properties Storage Group Information iDRAC Information • • • • • • • • • • • • • Printer Cover Table Printer Marker Supplies Information Printer Input Tray Information Printer Output Tray Info
Related link Managing Devices Searching for Devices Right-click All Devices at the top of the device tree and click Search Devices. You can also search for devices using logical arguments and save the queries for later. For example, to create a query to search for a server in critical state with an IP address containing values 10.35, and the power status as Power Up: 1. Click Manage → Device Search, then select Create New Query, in the adjacent text field enter a query name. 2.
Adding Devices to an Existing Group 1. Click Manage → Devices. 2. Right-click the device(s) and select Add to Existing Group. NOTE: If you are manually adding a device to a dynamic group, a message is displayed on the screen. Manually adding a device to a dynamic group changes the group from dynamic to static, thereby removing the original dynamic query. If you want the group to remain dynamic, modify the query defining the group. Click Ok to continue or Cancel to stop the procedure. 3. Click Ok.
Creating a Custom URL NOTE: Custom URL cannot be assigned to parent device groups that create a child sub group in the device tree at the time of discovery. Examples of parent device groups are: HA Clusters, Microsoft Virtualization Servers, PowerEdge M1000e, PowerEdge VRTX, or VMware ESX Servers. To assign a custom URL to a device in these parent device groups, add the device to a custom device group, and then assign a custom URL. 1. 2. Click Settings → Custom URL Settings. Click the icon.
9. If you want to configure the SMTP email server, click Email Settings. The Email Settings page is displayed. For more information about Email Settings, see Email Settings. 10. Click Apply. OpenManage Essentials sends warranty notification emails based on your configuration. The warranty notification email provides a list of devices and appropriate links that you can click to renew the warranty of the devices.
3. In the Update warranty every field, select the number of days to set the frequency at which the warranty updates are checked. 4. In the Next warranty update will be on field, select the date and time at which you want to check the next warranty updates. 5. Click Apply. NOTE: By default, the Warranty Update Settings is disabled. You can view the warranty information in the Device Warranty Report.
The navigation toolbar displayed at the bottom of the map enables you to: • Zoom in and out of the map • Move the map up, down, right, or left • Select the map provider type Figure 21. Navigation Toolbar The zoom level of the map can be identified by the scale that is displayed at the bottom-right of the map.
MapQuest Bing After getting a valid MapQuest key, you must provide the key in the Map Settings dialog box. After getting a valid Bing maps key, you must provide the key in the Map Settings dialog box. Internet connection is mandatory to render the online portion of the map and for the address lookup. Internet connection is mandatory to access any zoom level and to use the search functionality.
You can zoom in or zoom out of the map using any of the following methods: • Double-click a pin to zoom in to street level around that pin.
Health and Connection Status The health and connection status of a device can also be displayed on the map. To overlay the pin with the health or connection status of the device, move the mouse pointer over the Overlays menu at the top-right of the map, and click Health or Connectivity. The health or connection status is indicated by the color and the icon displayed within the pin. The following table provides information about the health status and pin overlay: Table 38.
2. • Click Manage → Devices → Map View. On the Map View, navigate and zoom until the current view is as desired. 3. Perform one of the following: • Right-click on the map, and then click Save Current View as Home View. • Move the mouse pointer over the Actions menu, and then click Save Current View as Home View. Related link Using Map View Viewing All Map Locations If a single device is selected, only that device is displayed on the map.
Moving a Device Location Using the Edit Location Details Option NOTE: Only OpenManage Essentials Administrators and Power Users are permitted to edit a map location. 1. Perform one of the following: • 2. Click Home → Map View. • Click Manage → Devices → Map View. Right-click a pin on the map, and select Edit Location Details. The Device Location Details dialog box is displayed. 3. In the Address field, type the location name or airport code. For example, New York.
6. NOTE: Before you import devices using the address, ensure that the system is connected to the Internet. If the system connects to the Internet through a proxy server, verify if the proxy settings are configured in the Settings → General Settings page. Also, the Internet search provider may reject the address search request if you are attempting to import too many devices at a time. If this occurs, wait for some time and try importing again. Click Import. The Open dialog box is displayed. 7.
Search Pin The search pin is a larger pin that represents the search result on the map. The following are the characteristics of the search pin: • At any instance, only one search pin can be located on the map. The search pin is displayed on the map at a location until you remove it or perform a new search. To remove the search pin, right-click the search pin and click Remove. • Unlike the device pin, the search pin does not overlay any status.
Related link Using Map View Moving a Device Location Using the Edit Location Details Option Removing All Map Locations NOTE: Only OpenManage Essentials Administrators and Power Users are permitted to remove all map locations. To remove all map locations: 1. Perform one of the following: • 2. Click Home → Map View. • Click Manage → Devices → Map View. On the Map View: • Right-click the map, and click Remove All Map Locations.
Exporting All Device Locations Exporting all device locations allows you to save the information about the devices and their latitude and longitude coordinates as a .csv file. If the address is known for a pin, it is included in the Description field of the .csv file. Using this file, you can import the device locations at any time. NOTE: By default, the latitude and longitude coordinates of each device is saved to the .csv file, even if the latitude and longitude coordinates were not provided previously.
• Slot name • Health status • Connection status If any other compute sled is discovered and inventoried and for storage sleds, the tool tip displays the: • Slot name • Sled model • Service Tag • Asset tag • Health status • Connection status To select a slot, click the visual representation of the sled in the Chassis View. When a slot is selected, a yellow rectangular box is displayed around the sled.
Right-Click Actions The right-click action on any compute sled that is discovered and available in the device tree is the same as when you right-click the sled in the device tree. NOTE: Right-click actions are not available for sleds that contain multiple compute nodes and storage sleds. Navigation Trail The navigation trail is displayed as a link under the Chassis View and indicates the currently selected device. You can click a device name in the navigation trail to go back to the chassis inventory.
– PowerEdge M and FN IOA * OpenManage Essentials version 2.3 supports 9.10.0.0, 9.10.0.1P10, 9.11.0.0 NOTE: VLAN configuration management is not supported for the PowerEdge FM120x4 sleds. Only the server-chassis slot mapping is displayed in the VLAN Configuration tab for the PowerEdge FM120x4 sleds. The server name and NIC port details are not displayed in the VLAN Configuration tab for the PowerEdge FM120x4 sleds.
NOTE: The valid range for VLAN IDs are 1 to 4094. Use a comma (,) to separate VLAN IDs and use a hyphen (-) to specify the ID range. 2. Click Apply. The VLAN Configuration window displays the IOA ports that you modified. NOTE: You can also modify the VLAN IDs in the VLAN Configuration window. 3. Type a unique name of the task. NOTE: It is recommended that you enter a unique name for the task. 4. If required, select a schedule for the task. 5.
The VLAN Configuration task is created in the Task Results tab. After the task is completed, OpenManage Essentials automatically inventories the VLAN configuration of all IOAs in the chassis. Dell NAS Appliance Support The following table provides information about discovery and classification, availability of appliance node information, and alert correlation for supported Dell NAS appliances. Table 43.
8 Devices — Reference This page provides the following information: • List of devices based on the device type, for example, HA clusters, servers, and so on. • Summary of devices and alerts. • Alerts generated for a particular device. • Health of devices based on the Normal, Critical, Unknown, and Warning types.
Alert Details Table 44. Alert Details Field Description Severity Alert severity based on Normal, Critical, Warning, and Unknown. Acknowledged Flagged status for an alert. Time Time at which the alert was generated in date and time format. Device IP address of the device. Details Lists the alert information. For example, System is down: Category Lists the alert category type, for example System Events. Source Lists the alert source name.
Field Description Service Tag Displays the Service Tag of the blade server. Model Displays the model name of the blade server. If this field is blank, the server is not present. Slot Displays the slot where the blade server is installed. Subslot Displays the subslot of the blade server node. NIC Displays the Fully Qualified Device Descriptor (FQDD) of the NIC. NIC Port Displays the NIC port to which the blade server is connected.
Field Description NIC Displays the Fully Qualified Device Descriptor (FQDD) of the NIC. NIC Port Displays the NIC port to which the server is connected. Chassis IOA Displays details of the IOAs that are installed in the chassis. IOA Name Displays the name of the selected IOA. IOA Model Displays the model name of the selected IOA. Fabric Displays the fabric associated with a specific slot of the chassis.
Field Description % Completed Displays the progress information of the task. Task State Displays the state of the task: • Running • Complete • Stopped • Failed • Warning End Time Displays the end time of the task. Executed by User Displays the name of the user who executed the task. Alert Filters You can apply these filters to Alerts. Select Continuous Updates to enable the user interface to update automatically when new alerts are received. Table 49.
Field Description Update Method Displays the update methods such as OpenManage Server Administrator and iDRAC. Discovered Time Time and date of discovery. Inventory Time Time and date of inventory. Select non-compliant systems to select updates to apply and click Apply Selected Updates. Table 51. Apply Selected Updates Field Description System Name System’s domain name. Importance The requirement of this software update for the system.
Query Results The device search lists these options: Table 53. Query Results Field Description Health Status Displays the health status of the device. The status options are Normal, Warning, Critical, and Unknown. Connection Status Displays the connection status of the device. The connection status are On or Off. Name Displays the name of the device. OS Name Displays the operating system installed on the device. OS Revision Displays the version of the operating system installed on the device.
Device Selection Options Table 55. Device Selection Options Field Description All Devices Select to include all the devices that are managed in OpenManage Essentials. Citrix XenServers Select to include Citrix XenServers. Clients Select to include client devices, such as desktops, portables, and workstations. Hyper-Converged Infrastructure Select to include VxRail and XC Series devices. HA Clusters Select to include High Availability server clusters.
Item Description • • Health Connectivity A tick mark is displayed beside the option that is selected. Actions menu Enables you to select a list of actions that can be performed.
Field Description Asset Tag Displays the defined asset tag for the device. Model Displays the model name of the system. For example, PowerEdge R710. Description Displays the description of the device. Address Displays the location information of the device. Contact Displays the contact information of the device. Map Settings The following table provides information about the fields displayed in the Map Settings dialog box. Table 58.
9 Deployment and Reprovisioning Every server and chassis has a large list of attribute values that describe the settings and functionality of the device. These settings must be set properly before deploying an operating system to make the server functional. The Deployment Portal enables you to perform initial server or chassis configuration and operating system deployment.
OpenManage Essentials—Server Configuration Management License NOTE: Installing and using OpenManage Essentials does not require the OpenManage Essentials — Server Configuration Management license. Only the server configuration management feature requires that the OpenManage Essentials — Server Configuration Management license is installed on target servers.
Related link Deploying a Device Deployment Template—Bare Metal Deployment Deploying a Device Configuration Template—Stateless Deployment Setting Up Device Configuration Auto Deployment—Bare Metal Deployment Setting Up Device Configuration Auto Deployment—Stateless Deployment Configuring the Credentials and Device Configuration Inventory Schedule Device Requirements for Deployment and Compliance Tasks The following are the device requirements for device configuration deployment and configuration compliance
Getting Started for Device Configuration Deployment Before you can deploy a device configuration to target devices, you must: 1. Configure the deployment file share on the server running OpenManage Essentials. 2. Add target devices to the Repurpose and Bare Metal Devices group.
The File Share Settings window is displayed. 2. Type the domain\user name and password of the server running OpenManage Essentials in the appropriate fields. 3. Click Apply. If the file share is configured correctly, the File Share Status displays Ok.
Creating a Device Deployment Template from a Device Configuration File You can create a device deployment template from an existing server or chassis configuration (.xml) file, or IOA configuration (.txt) file. Before you create a deployment template from a device configuration file, ensure that: • The deployment file share is configured. For more information, see Configuring the Deployment File Share.
• In the Common Tasks pane, click Create Template. • In the Templates pane, right-click Server Template, Chassis Template, or IOA Template, and then click Create Template. The Create Template window is displayed. NOTE: If the deployment file share settings are not configured, a message stating that One or more settings require configuring for this action is displayed. If you click OK, the File Share Settings window is displayed.
The attributes of the template are displayed in the Attributes tab in the right pane. The total number of attributes in the template is displayed at the top right of the Attributes tab. NOTE: IOA templates can only be created and deployed. The IOA templates that you create are displayed only in the Deployment Portal. NOTE: If the device deployment template was created from a blade server, the right pane also displays the IOA VLAN Attributes tab.
6. The attributes of the template are displayed in the Attributes tab in the right pane. If you do not want to deploy a particular attribute in the template and want to retain the current attribute value on the target device, clear the check box for that attribute in the Deploy column. 7. To select or clear all the attributes in the template, select or clear the check box that is displayed next to the Deploy column title.
To deploy the configuration template on bare metal devices: 1. Click Deployment. The Deployment Portal is displayed. 2. Perform one of the following: • In the Common Tasks pane, click Deploy Template. • In the Compute Pools pane, right-click the compute pool that has the target devices, and then click Deploy. The Deploy Template Wizard wizard is displayed. 3. On the Name and Deploy Options page: a. Type an appropriate name for the task. b. Under Deploy Target, select Bare Metal. c.
NOTE: If Static IPv4 Address is used in the deployment of a chassis template, then all the components in the chassis are rediscovered after the deployment task is completed. i. j. k. l. m. n. o. p. 8. NOTE: If Static IPv4 Address is provided and the DHCP attribute is enabled, then the DHCP settings take precedence over the provided Static IPv4 address. Similarly, If Static IPv4 Address is provided and the DHCP attribute is disabled, then the Static IPv4 Address is used for the template deployment.
NOTE: The chassis template cannot be created if devices are discovered using SNMP protocol only. To create a chassis deployment template from a chassis: 1. Click Deployment → Deployment Portal. 2. Perform one of the following: • In the Common Tasks pane, click Create Template. • In the Templates pane, right-click the Chassis Template and then click Create Template. The Create Template window is displayed.
Viewing the Chassis Deployment Template Attributes To view the chassis template attributes: 1. Click Deployment → Deployment Portal → Templates pane. 2. In the chassis templates, click either a sample template or a chassis template that you created. Select the chassis or the IOA templates, that are displayed in the right pane, to view the attributes. Exporting a Chassis Deployment Template The export option allows you to export the chassis infrastructure template into a .zip file. The .
CAUTION: Deploying a chassis infrastructure template on a device may result in potentially destructive changes to the device configuration including performance, connectivity, and ability to boot the device. To deploy the chassis infrastructure template: 1. Click Deployment. The Deployment Portal is displayed. 2. Perform one of the following: • In the Common Tasks pane, click Deploy Template.
g. If you do not want to deploy a particular attribute in the template and want to retain the current attribute value on the target device, clear the check box in the Deploy column. h. Click Save. i. Click Next. 7. On the Options page: a. Select Continue on warnings to continue with the deployment task even if the template is incompatible or shows warning messages. b. Click Next. 8. On the Set Schedule page: a.
d. Click Next. 4. On the Select Template page: a. Select the IOA template that you want to deploy. NOTE: Only configuration templates that you have either created or cloned are available for selection. b. Click Next. 5. If applicable, on the Select Virtual I/O Pool page, click Next. 6. On the Select Devices page, select the target devices from the All Applicable Devices tree, and click Next. NOTE: Only devices added to the Repurpose and Bare Metal Devices group are available for selection. 7.
Operational mode of the IOA from which Operational mode of the IOA on which the template is created or imported the template is deployed Deployment Task Status VLT Non-VLT Failed Non-VLT VLT Failed Deploying a Network ISO Image The deploy template task allows you to boot a server to a network ISO image, after which you can deploy the ISO image on the server. Before you begin deploying a network ISO image, ensure that: • The deployment file share is configured.
Removing Devices From the Repurpose and Bare Metal Devices Group You can remove devices from the Repurpose and Bare Metal Device group after the device configuration deployment, network ISO image deployment, or auto deployment task is complete. To remove devices from the Repurpose and Bare Metal Devices group: 1. Click Deployment → Deployment Portal. 2. In the Repurpose and Bare Metal Devices tab, select the devices you want to remove. 3. Perform one of the following: • 4.
3. Edit the Run auto deployment every xx Minutes field based on your preference. 4. Click Apply. Related link Auto Deploying Device Configurations Setting Up Device Configuration Auto Deployment—Bare Metal Deployment The Setup Auto Deployment task enables you to deploy a configuration template, which includes a set of configuration attributes, to devices that you will discover at a later time. Deploying a device configuration template on the devices ensures that the devices are uniformly configured.
d. Click Ok. e. Click Next. 6. On the Edit Attributes page: NOTE: OpenManage Essentials does not include any passwords from source when the configuration template is created. If you want to set the passwords for the target devices, all password attributes must be edited in the configuration template before deployment. a. Click the Template Attributes tab. b. Click the attribute group name to view the list of attributes in a group. c.
The Service Tags or Node IDs are displayed in the Auto Deployment tab until the devices are discovered and inventoried in OpenManage Essentials. The Deploy Configuration to Undiscovered Devices task runs periodically and verifies if the devices are discovered and inventoried in OpenManage Essentials. NOTE: The Deploy Configuration to Undiscovered Devices runs based on the frequency configured in Settings → Deployment Settings.
Adding a Discovery Range for Auto Deployment You can create a discovery range for the auto deployment task through either the Auto Deployment tab or the Discovery and Inventory portal. Before you can add a discovery range through the Auto Deployment tab, you must setup an auto deployment task. To add a discovery range through the Auto Deployment tab: 1. Click Deployment → Deployment Portal. The Repurpose and Bare Metal Devices tab is displayed in the right pane. 2.
Related link Import File Requirements Import File Requirements The following table describes the column titles and data to be included in the .csv file that is used for importing device specific attributes. Table 60. Import File Requirements Field Description Device Name The name of the device. During import, the device name is used to match with the name of the device selected for deployment. Service Tag The Service Tag of the device. The Service Tag must be provided for auto deployment tasks.
Related link Tasks Managing the Virtual Input-Output Identities of a Server—Stateless Deployment The I/O interfaces of a server, such as NICs or HBAs, have unique identity attributes that are assigned by the manufacturer of the interfaces. These unique identity attributes are collectively known as the I/O identity of a server. The I/O identities uniquely identify a server on a network and also determine how the server communicates with a network resource using a specific protocol.
Virtual Input-Output Pools A virtual I/O pool is a collection of one or more virtual I/O identity types that are required for network communication. A virtual I/O pool can contain a combination of any of the following virtual I/O identity types: • Ethernet identity which is defined by the Media Access Control (MAC) address. MAC addresses are required for Ethernet (LAN) communications. • Fibre Channel (FC) identity which is defined by the World Wide Node Name (WWNN) and World Wide Port Name (WWPN).
NOTE: For Converged Network Adapter (CNA) cards, WWNN and WWPN identities are derived from virtual FIP MAC address. In these scenarios, though the identities are not generated from the Ethernet Identities pool, these derived identities are counted against the Ethernet Identities pool. Ensure that necessary buffer is added while defining the Ethernet Identities pool size when virtual pool is used for deployment on servers with CNA cards. b. If you want to import the MAC addresses from a .
Figure 24. Sample .csv file with WWNN identities 6. On the FCoE Port Name Identities page, perform one of the following: NOTE: If you do not want to include fibre channel WWPN identities in the virtual I/O pool, clear the Include Fibre Channel WWPN Identities in the pool option, and then click Next. a. To specify the start address for the WWPN identities and the number of identities to be generated, perform the following: 1.
1. Click Import. 2. On the Import Wizard, click Import. 3. Browse and select the .csv file and click Open. The Import Results window is displayed. 4. Close the Import Results window and the Import Wizard, and then click Next. Figure 26. Sample .csv file with iSCSI IQN identities 8. On the Summary page, review the definitions with the number of identities that you provided for the I/O identity types, and then click Finish.
Renaming a Virtual Input-Output Pool To rename a virtual I/O pool: 1. Click Deployment. The Deployment Portal is displayed. 2. On the left pane, under Virtual I/O Pools, right-click the virtual I/O pool that you want to rename, and then click Rename. The Rename Virtual I/O Pool window is displayed. 3. Type a new name and then click OK. The virtual I/O pool is renamed.
Compute Pools A compute pool is a group of servers that you want to use for a specific purpose. Typically, the servers in a compute pool share the same hardware configurations and attributes. Based on your requirement, you can create compute pools for various purposes such as: • Managing the workload • Managing servers of a business unit • Managing servers in a geographic region Creating a compute pool allows you to quickly deploy a new server or replace an existing server in a production environment.
NOTE: If you do not want to provide the ISO location details, ensure that the Boot Compute Pool from Network ISO option is not selected, and then click Next. a. Select the Boot Compute Pool from Network ISO option. b. Type the ISO file name, IP address and name of the network share in the appropriate fields, and then click Next. 6.
The Deploy Template Wizard wizard is displayed. 3. On the Name and Deploy Options page: a. b. c. d. e. 4. Type an appropriate name for the task. Under Deploy Target, select Compute Pool. Select a compute pool from the Select a Compute Pool list. Under Select Deploy Options, select Deploy Template. Click Next. On the Select Template page, select a device configuration template and click Next. NOTE: Only device configuration templates that you have either created or cloned are available for selection.
NOTE: For Intel network adapters, a single iSCSI initiator name is generated and deployed on all ports. You cannot deploy the IQN identity to only one port. By default, the IQN identity is deployed to all ports. NOTE: The Status column displays an Error status if the selected virtual I/O pool either does not contain the virtual I/O attributes or does not have sufficient virtual I/O identities. 1. n. o. p. q. r. 8. Optional: Click Assign Identities to assign virtual I/O identities from the virtual I/O pool.
Unlocking a Compute Pool You can unlock a compute pool if you want to update the compute pool after the compute pool is deployed and locked. For example, after unlocking a compute pool, you can edit the device configuration template, and then redeploy the servers in the compute pool. To unlock a compute pool: 1. Click Deployment. The Deployment Portal is displayed. 2. On the left pane, under Compute Pools, right-click the compute pool that you want to unlock, and then click Unlock. 3.
Removing a Server From a Compute Pool You can remove a server from a compute pool based on your requirement. For example, you can remove a server from a compute pool for the purpose of moving the server to another compute pool or for deploying the server without virtual I/O identities. To remove a server from a compute pool: 1. Click Deployment. The Deployment Portal is displayed. 2.
• The compute pool contains a minimum of two servers, one or both of the servers in a deployed state. • The source server is deployed within the same compute pool. • The target server is within the same compute pool as the source server. To replace a server: CAUTION: The replace server task may result in potentially destructive changes to the device configuration including performance, connectivity, ability to boot the device, and/or data loss. 1. Click Deployment. The Deployment Portal is displayed.
Reclaiming Deployed Virtual Input-Output Identities of a Server The reclaim identities task allows you to reclaim all deployed virtual I/O identities from a server. Before you begin the reclaim identities task, ensure that: • The server has been deployed from a compute pool. • The server has been assigned virtual I/O identities using OpenManage Essentials.
5. If you want to continue reclaiming the assigned virtual I/O identities of the device, click Yes. The reclaimed virtual I/O identities are returned to the virtual I/O pool. Setting Up Device Configuration Auto Deployment—Stateless Deployment The Setup Auto Deployment task enables you to deploy a configuration template, which includes a set of configuration attributes, to devices that you will discover at a later time.
NOTE: You can only import valid Service Tags or node IDs that have not already been discovered. c. Click Open. The Import Summary is displayed. d. Click Ok. e. Click Next. 8. On the Edit Attributes page: NOTE: OpenManage Essentials does not include any passwords from source when the configuration template is created. If you want to set the passwords for the target devices, all password attributes must be edited in the configuration template before deployment. a. Click the Template Attributes tab. b.
The Service Tags or Node IDs are displayed in the Auto Deployment tab until the devices are discovered and inventoried in OpenManage Essentials. The Deploy Configuration to Undiscovered Devices task runs periodically and verifies if the devices are discovered and inventoried in OpenManage Essentials. NOTE: The Deploy Configuration to Undiscovered Devices runs based on the frequency configured in Settings → Deployment Settings.
• Server Cloning with Server Configuration Profiles • Server Configuration XML File • Configuration XML Workflows • Configuration XML Workflow Scripts • XML Configuration File Examples You can also find detailed information about bare metal and stateless deployments using OpenManage Essentials in the server deployment technical white paper available at delltechcenter.com/OME.
10 Deployment – Reference You can access the following from the Deployment → Deployment Portal page: • Deploy Device Configuration Portal – Getting Started for Deployment — Displays the information required to setup, use, and get started with the device configuration deployment features. – Deployment Portal — Displays the default view of the Deployment Portal. • Common Tasks — Displays the deployment setup tasks and other tasks that you can create.
* Sample - iDRAC Set Power Cap * Sample - Set UEFI Boot Order * Sample - Set SNMP Email Alerts – Chassis Templates * Sample - FX2 Chassis * Sample - VRTX Chassis * Sample - M1000e Chassis – IOA Templates • Compute Pools — Displays the devices you have added to the Repurpose and Bare Metal group and the compute pools that you have created. • Virtual I/O Pools — Displays the virtual I/O identity pools that you have created.
Icon Description A locked resource. Read-only but deployable device configuration template.
Auto Deployment The Auto Deployment tab displays the target devices that you have selected for the auto deployment tasks. The fields displayed in the Auto Deployment tab are described in the following table. Table 63. Auto Deployment Field Description Service tag or Node ID Displays the unique identifier assigned to the system. Template to Deploy Displays the template selected for deployment on the device. Compute Pool Displays the name of the compute pool to which the device belongs.
Related link Viewing the Deployment Tasks Task Execution History The Task Execution History tab displays the status of tasks. The fields displayed in the Task Execution History tab are described in the following table. Table 65. Task Execution History Field Description Status Displays an icon representing the task status: — Running or pending — Complete — Stopped — Failed — Warning Task Name Displays the name of the task. Start Time Displays the start time of the task.
Field Description select all the attributes in the template by selecting the check box in the Deploy column header. Modified Displays if you have modified the value of an attribute. Section Displays the component that the attribute belongs to. For example, iDRAC, BIOS, NIC, and so on. Instance Displays the instance of the component that the attribute belongs to. Attribute Name Displays the name of the attribute. Value Displays the value of the attribute.
Device Configuration Setup Wizard The Device Configuration Setup Wizard guides you through the steps to get started with the configuration deployment and compliance tasks. NOTE: The Device Configuration Setup Wizard is only displayed if you try to perform a task that is missing required information. File Share Settings The fields displayed in the File Share Settings page are described in the following table. Table 68. File Share Setting Field Description Domain \ Username User name to access the file s
Related link Creating a Device Deployment Template from a Device Configuration File Creating a Device Deployment Template From a Reference Device Create Virtual Input-Output Pool Wizard The Create Virtual I/O Pool Wizard guides you through the creation of a pool of one or more virtual I/O identity types. OpenManage Essentials utilizes the virtual I/O identities from the pool to assign an unique identity to the network interfaces of a server.
Field Description NOTE: The .csv must include only one address or identity per line. View Click to view the MAC addresses in the virtual I/O pool. NOTE: You can only view MAC addresses that you have already imported from a .csv file. Related link Create Virtual Input-Output Pool Wizard FCoE Node Name Identities The FCoE Node Name Identities page allows you to generate or import World Wide Node Name (WWNN) identities to the virtual I/O pool.
Table 73. FCoE Port Name Identities Field Description Include Fibre Channel WWPN Identities in the pool Select to include WWPN identities in the virtual I/O pool. Specify the start address Select to specify the start address for the WWPN identities that will be generated. Number of Identities Set the number of identities that you want to predefine in the WWPN identities that will be generated. Import from file Select to import WWPN identities from a .csv file.
Summary The Summary page displays the definitions you provided for the create virtual I/O pool task. The fields displayed on the Summary page are described in the following table. Table 75. Summary Field Description Name Displays the task name. Ethernet Definition Displays the MAC address definition. Number of Ethernet Identities Displays the virtual I/O pool size of the ethernet identities. FCoE WWNN Definition Displays the WWNN identity definition.
Summary Table 77. Summary Field Description Grouped by Displays the grouping you have selected for displaying the details of the virtual I/O pool. Identity Type Displays the virtual identity type included in the virtual I/O pool. Range Information Displays the definition that you provided for the virtual identity type. Number of Identities Displays the total number of identities of the virtual I/O pool.
Create Compute Pool Wizard The Create Compute Pool Wizard guides you through the creation of a pool of servers that you want to use for a specific purpose. The fields displayed on the various pages of the wizard are described in the following sections. Related link Name and Description Select Template Select ISO Location Select Virtual Input-Output Pool Select Devices Edit Attributes Summary Name and Description The Name and Description page allows you to provide a name and description for the task.
The fields displayed on the Select ISO Location page of the Create Compute Pool Wizard are described in the following table. Table 81. Select ISO Location Field Description Boot Compute Pool from Network ISO Select to boot devices included in the compute pool from an operating system ISO file. ISO Filename Provide the name of the ISO file. Share IP Provide the IP address of the network share where the ISO file is available.
Template Attributes The fields displayed on the Template Attributes tab are described in the following table. Table 83. Template Attributes Field Description Grouped by Displayed if you choose to display the attributes as groups. Total Displays the total number of attributes. Modified Displays the number of attributes that you have modified. Attributes for Displays the name of the selected device configuration template.
Field Description Modified Displays the number of attributes that you have modified. Deploy Select to deploy an attribute. If an attribute is not selected, the attribute value will not be deployed on the target device and the current value will be retained on the target device. You can select all the attributes in the template by selecting the check box in the Deploy column header. Modified Displays if you have modified the attributes.
Field Description Instance Displays the instance of the component that the attribute belongs to. Attribute Name Displays the name of the attribute. Value Displays the value of the attribute. Dependencies Displays if the attribute is dependent on any other attributes. To edit a dependent attribute, you must first set the primary attribute.
Field Description Modified Displays if you have modified the value of the attribute. Identity Impact Displays if the identity attribute will be automatically generated. Status Displays the status of the generation of the identity attribute. An Error status is displayed if the selected virtual I/O pool either does not contain the virtual I/O attribute or does not have sufficient attributes. Section Displays the component that the attribute belongs to. For example, iDRAC, BIOS, NIC, and so on.
Summary The Summary page displays the details you have provided for creating the compute pool. The fields displayed on the Summary page are described in the following table. Table 89. Summary Field Description Name Displays the task name. Selected Template Displays the name of the template you have selected. ISO Filename Displays the name of the ISO file. Share IP Displays the IP address of the network share where the ISO file is available.
Compute Pool Details The fields displayed on the Compute Pool Details page are described in the following table. Table 91. Compute Pool Details Field Description Template Displays the name of the template assigned to the compute pool. Click the template name to view the attributes of the template. Virtual I/O Pool Displays the name of the virtual I/O pool that is assigned to the compute pool. Network ISO Image Displays the name of the network ISO file assigned to the compute pool.
Deploy Template Wizard The Deploy Template Wizard guides you through the steps to deploy a configuration template and/or boot to a network ISO image. The steps displayed in the wizard may vary based on the deploy option you select. The fields displayed in the various pages of the wizard are described in the following sections.
The fields displayed in the Select Template page are described in the following table. Table 94. Select Template Field Description Server Template Displays the server configuration templates that you have either created or cloned. Chassis Template Displays the chassis configuration templates that you have either created or cloned. NOTE: If you select both Deploy Template and Boot to Network ISO in the Name and Deploy Options or Select Deploy Options page, the Chassis Template option is disabled.
Field Description Share Username Provide the user name required to access the network share. Share Password Provide the password required to access the network share. Related link Deploy Template Wizard Select Virtual Input-Output Pool The Select Virtual I/O Pool page allows you to select the method of assigning the virtual I/O identity on the target servers. The fields displayed on the Select Virtual I/O Pool page are described in the following table. Table 96.
Field Description Deploy Select to deploy an attribute. If you do not select an attribute, the attribute value is not deployed on the target device and the current value will be retained on the target device. You can select all the attributes in the template by selecting the check box in the Deploy column header. Modified Displays if you have modified the value of the attribute. Section Displays the component that the attribute belongs to. For example, iDRAC, BIOS, NIC, and so on.
Field Description Undo Click to undo the changes made to the IOA VLAN attributes of the selected template. Save Click to save the changes to the IOA VLAN attributes of the selected template. Device Specific Attributes The fields displayed on the Device Specific Attributes tab are described in the following table. Table 99. Device Specific Attributes Field Description Select Devices Displays the devices that you have selected for deployment.
Table 100. Import/Export Device Specific Attributes Field Description Export Selected Device Click to export the device specific attributes for the selected device to a .csv file. Export All Devices Click to export the device specific attributes for all selected devices to a .csv file. Import Click to import the device-specific attributes. File Requirements and Info Displays the requirements of the .csv file you must use to import device-specific attributes.
Field Description Destructive Displays if deploying the attribute may result in destructive changes to the device configuration including performance, connectivity, and ability to boot the device. Group Displays the logical group that the attribute belongs to. Assign Identities Click to automatically assign virtual I/O identities to the target devices. Undo Click to undo the changes made to the configuration template. Save Click to save the changes to the configuration template.
Field Description NOTE: If the Perform pre-check only option is selected, by default the Continue on warnings option is disabled. Continue on warnings Select Continue on warnings to continue deploying the template even if the template is incompatible with the target devices. NOTE: When this option is selected, warnings (if any) will be ignored and the deployment task runs even if the device configuration template is incompatible.
in errors. Running the preview allows you to identify the attributes that will not be deployed successfully. After identifying those attributes, if required, you can clear those attributes from the template and then deploy the template. NOTE: The preview activity identifies many problems; however, some problems cannot be determined before the actual deployment. Click the Preview button to validate the attributes of the device configuration template with the selected device.
Setup Auto Deployment Wizard The Setup Auto Deployment wizard guides you through the steps to deploy a configuration template and/or boot to a network ISO image on target devices that you will discover later. The steps displayed in the wizard may vary based on the deployment option you select. The fields displayed in the various pages of the wizard are described in the following sections.
Field Description NOTE: If you select both Deploy Template and Boot to Network ISO in the Name and Deploy Options or Select Deploy Options page, the Chassis Template option is disabled. Select ISO Location The Select ISO Location page enables you to provide the details of the ISO file. NOTE: The Select ISO Location page is only displayed if you select the Boot to Network ISO option on the Name and Deploy Options or Select Deploy Options page.
Import Service Tags or Node IDs The Import Service Tags/Node IDs page of the Setup Auto Deployment wizard displays the Import button. Click Import to import a .csv file that includes Service Tags or node IDs of devices that you will discover later. NOTE: On devices which have multiple compute nodes (such as the PowerEdge FM120x4), all of the compute nodes have the same Service Tag. Therefore, the node ID must be used to identify the specific compute node to use. In the .
Field Description • For an auto deployment task — The Service Tag of the device to be discovered later. Deploy Select to deploy an attribute. If you do not select an attribute, the attribute value is not deployed on the target device and the current value will be retained on the target device. You can select all the attributes in the template by selecting the check box in the Deploy column header. Modified Displays if you have modified the value of the attribute.
Field Description Tagged VLAN(s) Displays the list of tagged VLANs for the selected fabric. Untagged VLAN Displays the untagged VLAN for the selected fabric. Undo Click to undo the changes made to the IOA VLAN attributes of the selected template. Save Click to save the changes to the IOA VLAN attributes of the selected template. Device Specific Attributes The fields displayed on the Device Specific Attributes tab are described in the following table. Table 112.
Import/Export Device Specific Attributes The fields displayed on the Import/Export Device Specific Attributes window are described in the following table. Table 113. Import/Export Device Specific Attributes Field Description Export Selected Device Click to export the device specific attributes for the selected device to a .csv file. Export All Devices Click to export the device specific attributes for all selected devices to a .csv file. Import Click to import the device-specific attributes.
Field Description Dependencies Displays if the attribute is dependent on any other attributes. To edit a dependent attribute, you must first set the primary attribute. Destructive Displays if deploying the attribute may result in destructive changes to the device configuration including performance, connectivity, and ability to boot the device. Group Displays the logical group that the attribute belongs to.
Table 116. Credentials Field Description Add New Credentials Click to open the Add Credentials window that enables you to provide credentials for target devices. Description Displays the description provided for the credentials. Username Displays the user name. Password Displays the password in a masked format. Is Default Displays a check box that you can select to associate the credentials to all new target devices. Update Displays an icon that you can click to edit the credentials.
Table 119. Add Credentials Field Description Description Provide a description for the credentials. Username Provide the user name required to run the task on the target device. Password Provide the password required to run the task on the target device. Default Select to associate the credentials to all new target devices. Summary The Summary page displays the options you have selected for the auto deployment task. The fields displayed in the Summary page are described in the following table.
Table 121. Credentials Field Description Add New Credentials Click to open the Add Credentials window that enables you to provide credentials for target devices. Description Displays the description provided for the credentials. Username Displays the user name. Password Displays the password in a masked format. Is Default Displays a check box that you can select to associate the credentials to all new target devices. Update Displays an icon that you can click to edit the credentials.
Source and Target The Source and Target page allows you to select the source server and the target server for the replacement. The fields displayed on the Source and Target page of the Replace Server Wizard are described in the following table. Table 123. Source and Target Field Description Select Source Displays a tree-view of the servers within the compute pool that are already deployed. Select Target Displays all other servers within the same compute pool.
Table 125. IOA VLAN Attributes Field Description IOA VLAN Attributes for Template Displays the name of the selected template. Total Displays the total number of attributes. Modified Displays the number of attributes that you have modified. Deploy Select to deploy an attribute. If an attribute is not selected, the attribute value will not be deployed on the target device and the current value will be retained on the target device.
Field Description Modified Displays if you have modified the value of the attribute. Section Displays the component that the attribute belongs to. For example, iDRAC, BIOS, NIC, and so on. Instance Displays the instance of the component that the attribute belongs to. Attribute Name Displays the name of the attribute. Value Displays the value of the attribute. Dependencies Displays if the attribute is dependent on any other attributes.
Field Description NOTE: If this option is not selected, the source server is retained within the compute pool after the server is replaced. Deploy to target even if virtual identities cannot be reclaimed from the source Select to reclaim the virtual I/O identities of the source server, even if the server is unreachable. NOTE: If the source server is not reachable and this option is: • • Not selected — The replace server task is unsuccessful.
Field Description Configure VLANs on IOAs Displays if you have selected to configure the VLANs on the IOAs. Remove from Pool Displays if you have chosen to remove the source server from the compute pool. Force reclaim identities Displays if you have chosen to reclaim the virtual I/O identities of the source server, even if source server is unreachable. Schedule Displays the predefined task schedule.
Field Description Model Displays the model name of the device, if available. For example, PowerEdge R710. Related link Reclaim Identities Wizard Identity Assignments The Identity Assignments page allows you to view the virtual I/O identities that are assigned to the selected server. The fields displayed on the Identity Assignments page of the Reclaim Identities Wizard are described in the following tables. Table 132. Identity Assignments Field Description Device Displays the name of the device.
Field Description NOTE: If the source server is not reachable and this option is: • • Not selected — The reclaim identities task is unsuccessful. Selected — The virtual I/O identities are reclaimed and available for use. However, you may notice devices with duplicate I/O identities on the network if the server is added back to the network. Related link Reclaim Identities Wizard Credentials The Credentials page allows you to provide the credentials of the selected server.
11 Managing Server Configuration Baseline The configuration of a server or chassis in a production environment must be properly maintained to ensure availability of the server. These server configuration settings tend to be drifted over time because of various reasons. The Device Compliance Portal enables you to verify and ensure the compliance of multiple servers and chassis to a device configuration baseline that serves as a baseline.
Related link Configuring the Deployment File Share Configuring the Credentials and Device Configuration Inventory Schedule Device Configuration Compliance Overview Device Configuration Compliance Overview The steps that you must perform to verify the compliance status of a device and to make a device compliant to a device configuration baseline are as follows: 1. Create a Baseline — Use the Create Baseline task in the Common Tasks pane to create a device configuration baseline.
4. On the Schedule page: a. b. c. d. Select Enable Configuration Inventory. If you want to run the configuration inventory immediately, select Run Inventory on Finish. Select the desired scheduling parameters. (Optional) You can adjust the Inventory Polling Speed slider for faster task execution; however, this consumes more system resources. e. Click Finish. The status of the task is displayed in Task Execution History.
7. In the task submission message, click Ok. NOTE: The destructive and password attributes information will not be displayed while configuring a baseline. Only the non-destructive attribute information of the baseline is displayed. Associating Target Devices to a Baseline The Associate Devices to a Baseline task enables you to designate the baseline to be used for verifying the compliance status of target devices. NOTE: A device can only have one associated device configuration baseline.
NOTE: The user configuration attributes are successfully remediated only if the same user exists on the target devices. You cannot create a new user as the password attributes are not considered for remediation. For more details on creating a new user, see Deployment and Reprovisioning NOTE: The remediation task fails for the devices which are non-compliant because of the missing attributes, or because of the dependency of attributes on other attributes that are not part of the compliance baseline.
To replace a target server with the backup profile, see Replacing Server from Backup Profile Replacing Server from Backup Profile The replace server task allows you to replace a production server from the backup profile. When the replace server task runs, the attributes of the source server are migrated to the target server. Before you begin to replace the target server, ensure that: • The deployment file share is configured. For more information, see Configuring the Deployment File Share.
12 Configuration – Reference You can access the following from the Manage → Configuration page: • Device Configuration Compliance Portal – Getting Started for Compliance — Displays the information required to setup, use, and get started with the device configuration compliance features. – Device Compliance Portal — Displays the default view of the Device Compliance Portal. • Common Tasks — Displays the configuration compliance setup tasks and other tasks that you can create.
Related link Device Compliance Tasks Task Execution History Associate Devices To a Baseline Wizard Configuration Inventory Schedule Wizard Backed-Up Devices Device Compliance The Device Compliance graph and table enable you to view the compliance status of the devices. Device Compliance Graph The device compliance graph provides a pie chart distribution of the compliance status. Click a segment of the pie chart to view more information on the systems.
Table 137. Tasks Field Description Schedule Displays if the task schedule is active or inactive. Task Name Displays the name of the task. Type Displays the type of task. Description Displays a brief description about the task. Updated on Displays the date and time the task was updated. Updated by Displays the name of the user who updated the task. Created on Displays the date and time the task was created. Created by Displays the name of the user who created the task.
Associate Devices To a Baseline Wizard The Associate Devices to a Baseline Wizard enables you to associate devices to a baseline. The fields displayed in the Associate Devices to a Baseline Wizard are described in the following sections. Related link Select Baseline Select Devices Associating Target Devices to a Baseline Select Baseline The Select Baseline page enables you to select the baseline you want to associate to target devices.
Field Description Compliance Template Displays the device configuration template that is associated to the device. Inventory Last Run Displays the date and time the last device configuration inventory was completed. Non-Compliant Results Displays the count of missing and non-compliant attributes. Device Name Displays the name of the device. Compliance Result Displays the compliance result of the device to the associated configuration baseline.
Summary Table 144. Summary Field Description Name Displays the name of the remediation task. Non-Compliant Devices Displays the selected non-compliant device name. Reboot Option Displays the selected reboot option. Schedule Displays the selected schedule to run the remediation task. Configuration Inventory Schedule Wizard The Configuration Inventory Schedule wizard enables you to associate the credentials to discovered devices and set the schedule for configuration inventory.
Field Description Execution Credentials Displays the credentials that have been assigned to the device for running the configuration inventory task. You can use this field to assign the credentials required for running the configuration inventory task on the device. Schedule The Schedule page enables you to configure the schedule for the configuration inventory. The fields displayed in the Schedule page are described in the following table. Table 147.
Field Description Service Tag Displays the unique identifier assigned to the device. Model Displays the model name of the device. For example, PowerEdge R730. Last Backup Result Displays the result of the last backup operation of the device. Last Successful Backup Time Displays the last successful backup time of the device. Attributes Table The fields displayed in the Attributes table of the Backed-Up Devices portal are described in the following table.
13 Viewing Inventory Reports OpenManage Essentials provides pre-defined reports for all discovered and inventoried devices. With these reports, you can: • Consolidate information about devices in your environment. • Filter report data based on the devices by clicking the Filter by: drop-down list. You can also add a new group of devices from the dashboard by clicking Add New Group from the Filter by: drop-down list. • Export data for use in another application in the XML file format.
Category Report Description part. Click on a specific device to view the events associated with it. Agent Health Status Provides information about the agent such as the system name, agent global status, agent name, and agent description. Server Overview Provides information about the servers such as the system name, operating system installed on the server, processors, and memory. FRU Information Provides details on replaceable server components.
Category Server Configuration Warranty & License Virtualization Asset Report Description Virtual Disk Information Provides information about the virtual disk such as size, layout, stripe size, and so on. Server Components and Versions Identifies BIOS, driver, and firmware versions on all discovered and inventoried servers. BIOS Configuration Provides the BIOS configuration information of the system. iDRAC Network Configuration Provides IPMI over LAN, SSH, and Telnet status of the iDRAC.
Filtering Report Data You can filter the results by dragging and dropping column headers to the top of reports. You can choose one or more attributes when revising the view to meet your specific needs. For example, in the NIC Information report, drag the System Type and System Name to the top of the report. The view immediately changes to a nesting of information based on your preference. In this example, you can view nested data for NICs; NIC IP Address, MAC Address, and NIC description. Figure 28.
14 Reports — Reference In the Reports portal, you can view various reports that are available under the following sections: • Server Inventory • Server Configuration • Warranty & License • Virtualization • Asset You can also filter the information based on a device or group by clicking Filter by and then selecting the device or group.
Related link Agent and Alert Summary Agent Health Status Server Overview Field Replaceable Unit Information Hard Drive Information iDRAC Performance Minimum or Maximum iDRAC Performance Average or Peak Memory Information Modular Enclosure Information NIC Information PCI Device Information Processor Information Storage Controller Information Virtual Disk Information Agent and Alert Summary The Agent and Alert Summary displays the following: • Agent Summary • iDRAC Service Module Summary • Alerts per De
• Capable Windows — The server does not meet some of the requirements for deploying iDRAC Service Module. For example, the system may not be running a 64-bit operating system or the version of the iDRAC firmware installed on the system may be prior to 1.51.51. • Deployable Windows — iDRAC Service Module can be deployed on the server. • Incapable — iDRAC Service Module cannot be installed on the server. For example, the system may be a Dell 11th generation or earlier PowerEdge server.
Field Description Processor Cores Displays the number of processor cores. Processor Speed Displays the speed of the processor. Total Cores Displays the total number of cores present in the system. Total Memory Displays the total memory installed on the system Field Replaceable Unit Information Table 156. Field Replaceable Unit (FRU) Information Field Description System Name Displays the unique name of the system that identifies it on the network.
Field Description addressed by the SCSI protocol or similar protocols such as Fibre Channel or iSCSI. Size (GB) Displays the size of the hard drive in GB. Bus Type Displays the type of bus connection used. A bus, in computing, is an information pathway between components of a system. Serial Number Displays the roll number assigned to the device by the manufacturer. Revision Displays the revision history of the hard drive. Media Type Displays the type of media. For example, HDD.
Field Description Last Hour Time Stamp Displays the time at which the usage level was reported in the last hour. Last Day (%) Displays the usage level of the attribute in the last day. Last Day Time Stamp Displays the time at which the usage level was reported in the last day. Last Week (%) Displays the usage level of the attribute in the last week. Last Week Time Stamp Displays the time at which the usage level was reported in the last week.
Field Description Memory Device Type Details Displays details about the memory device type. Memory Device Manufacturer Displays the name of the device manufacturer. Memory Device Part Number Displays the industry specific number assigned to the device. Memory Device Serial Number Displays the roll number assigned to the device by the manufacturer. Modular Enclosure Information Table 161.
Field Description Vendor Displays the name of the NIC supplier. NIC Description Displays information on the NIC device. PCI Device Information Table 163. PCI Device Information Field Description System Name Displays the unique name of the system that identifies it on the network. System Type Displays the model name of the system. For example, PowerEdge R710. Service Tag Displays the unique identifier assigned to the system.
Storage Controller Information Table 165. Storage Controller Information Field Description System Name Displays the unique name of the system that identifies it on the network. The storage controller is present on this system. System Type Displays the model name of the system. For example, PowerEdge R710. Controller Name Displays the name of the storage controller. For example, SAS 6/iR Integrated. Vendor Displays the supplier information. For example, SAS 6/iR Integrated is supplied by Dell.
• BIOS Configuration • iDRAC Network Configuration • Device Configuration Compliance • Template Association • Assigned Identity Attributes • All Identity Attributes Related link Server Components and Versions BIOS Configuration iDRAC Network Configuration Device Configuration Compliance Baseline Association Assigned Identity Attributes All Identity Attributes Server Components and Versions Table 167.
Field Description Cores per Processor Displays the number of cores enabled in each processor. Node Interleaving Displays whether the Node Interleaving option is enabled or disabled. Logical Processor Displays whether the logical processor option is enabled or disabled. Integrated RAID Controller Displays whether the integrated RAID controller is enabled or disabled. SR-IOV Global Enable Displays whether the configuration of Single Root I/O Virtualization (SR-IOV) devices is enabled or disabled.
Device Configuration Compliance Table 170. Device Configuration Compliance Field Description Compliance Status Displays the compliance status of the device to the associated configuration baseline. Device Name Displays the unique name of the system that identifies it on the network. Service Tag Displays the unique identifier assigned to the system. Model Displays the model name of the system. For example, PowerEdge R710.
Field Description Instance Displays the instance of the component to which the attribute belongs. Attribute Name Displays the name of the attribute. Value Displays the virtual I/O identity assigned or deployed on the system. Compute Pool Displays the name of the compute pool to which the device belongs. Virtual I/O Pool Displays the name of the virtual I/O pool from which the virtual I/O identity is assigned to the system. Status Displays if the system is deployed with virtual I/O identities.
Warranty Information Table 174. Warranty Information Field Description View and Renew Warranty Displays a link you can click to open the Dell website from where you can view and renew the device warranty. Device Name Displays the unique name of the system that identifies it on the network. If applicable, the proxy settings must be configured to retrieve warranty data from dell.com/support. Model Displays the model name of the system. For example, PowerEdge R710.
Virtualization Reports The Virtualization section contains the following reports: • ESX Information • HyperV Information Related link ESX Information HyperV Information ESX Information Table 176. ESX Information Field Description System Name Displays the unique name of the system that identifies it on the network. The embedded bare-metal product is installed on this system. System Type Displays the model name of the system. For example, PowerEdge R710.
Asset Reports The Asset section contains the following reports: • Asset Acquisition Information • Asset Maintenance Information • Asset Support Information • Device Location Information The reports in the Asset section depend on the following: • The server must be discovered in-band with SNMP protocol. • The asset information must be set in OMSA. To set the asset information in OMSA, go to System → Properties → Asset Information.
Field Description Depreciation Duration Unit Type Displays the unit in months or years. Depreciation Percentage Displays the portion of 100 that an asset is devalued or depreciated. Depreciation Method Displays the steps and assumptions used to compute the system's depreciation. Ownership Code Defines the ownership code for this system. Corporate Owner Name Displays the business entity that owns the system. Insurance Company Displays the name of the company that insures the system.
Asset Support Information Table 180. Asset Support Information Field Description System Name Displays the unique name of the system that identifies it on the network. System Type Displays the model name of the system. For example, PowerEdge R710. Service Tag Displays the unique identifier assigned to the system. Warranty Cost Displays the extended warranty cost date for the system. Warranty Duration Displays the duration of the warranty.
Field Description Data Center Displays the data center where the system is available. Room Displays the name of the room where the system is available. Aisle Displays the aisle where the system is available. Rack Displays the rack where the system is available.
15 Viewing Warranty Reports Warranty information is available for devices with valid Service Tags, including clients, servers, switches, storage, and so on. Warranty information is automatically retrieved at the time devices are discovered. The Warranty Information report is unique among OpenManage Essentials reports as it requires Internet access to pull warranty information from the warranty database. If you do not have internet access, no warranty information is populated.
16 Managing Alerts NOTE: You can receive alert notifications from OpenManage Essentials on your Android or iOS device by installing and setting up the OpenManage Mobile application. For more information, see OpenManage Mobile Settings and the OpenManage Mobile User’s Guide at dell.com/OpenManageManuals.
Icon Alert Description Information Alerts Provides information only. Figure 33. Information alert icon Viewing Internal Alerts Before viewing internal alerts, ensure that you enable internal health alerts in the Alert Settings of the Settings tab. See Alert Settings. To view internal alerts, click Manage → Alerts → Alert Logs → All Internal Alerts.
Viewing E-Mail Alert Action To view the e-mail alert action: 1. Select Manage → Alerts → Alert Actions. 2. In Alert Actions, select Email. Viewing Alert Ignore Action To view the alert ignore action: 1. Select Manage → Alerts → Alert Actions. 2. In Alert Actions, select Ignore. Viewing Alert Trap Forward Action To view the alert trap forward action: 1. Select Manage → Alerts → Alert Actions. 2. In Alert Actions, select Trap Forwarding.
Configuring Alert Actions Alert actions occur on all alerts received by the OpenManage Essentials console. The alert is received and processed by the OpenManage Essentials console whether or not OpenManage Essentials has discovered the device so long as OpenManage Essentials is listed in the device's SNMP trap forward destinations list. To prevent this, remove OpenManage Essentials from the SNMP trap forward destinations list on the device.
Related link Alert Logs Alert Logs Fields Alert Log Settings Severity Ignoring Alerts Sometimes you will receive alerts you might want to ignore. For example, you may want to ignore multiple alerts generated when Send authentication trap is selected within the SNMP service on the managed node. NOTE: You can ignore all alerts from a particular device by using the Ignore All Alerts from Device option available when you right-click either a device on the device tree or an alert in the Alerts portal.
Related link Alert Logs Alert Logs Fields Alert Log Settings Severity Forwarding Alerts You may want to consolidate alerts from multiple management stations to one management station. For example, you have management stations in multiple locations and you want to view status and take action from one central location. For information about the behavior of forwarded alerts, see Forwarding Alerts Use Case. To create alert forwards: 1. Select Manage → Alerts → Common Tasks → New Alert Trap Forward Action. 2.
Scenario 3 — Forwarding Alerts in the OMEssentials Format Using Either SNMP v1/v2 Protocol In this scenario, SNMP v1 alerts are sent from MNv1 to MS1 and then forwarded to MS2. If you try to retrieve the remote host of the forwarded alert, it is displayed as MS1. The severity and the message of the alert is also defined by MS1 and does not display the original severity and message defined by MNv1. NOTE: The same behavior applies for SNMPv2 traps.
Renaming Alert Categories and Alert Sources 1. Click Manage → Alerts → Alert Categories. 2. In Alert Categories, right-click any of the alert categories (under the Alert Category heading in the left pane) and select Rename. 3. Provide a name for the alert category and click OK. Alert Pop-Up Notifications The alert pop-up notification is displayed in the bottom-right corner of the OpenManage Essentials console when a Critical or Warning alert is received.
Enabling or Disabling Alert Pop-Up Notifications To enable or disable alert pop-up notifications: NOTE: To quickly disable alert pop-up notifications, click the Disable link displayed in the alert pop-up notification. When the Disable Alert Popup Notifications prompt is displayed, click Yes. 1. Click Settings → Alert Settings. The Alert Settings page is displayed. 2. 3.
Feature Before Importing the MIB to the OpenManage Essentials Database After Importing the MIB to the OpenManage Essentials Database Will the trap display the trap variable values? Yes Yes (by default), provided the format string values are not removed prior to importing the traps to OpenManage Essentials.
Managing Traps Customizing Trap Definitions The Custom Trap Definitions view enables you to add trap definitions to the OpenManage Essentials database. You can add a new trap definition or search unknown traps received in OpenManage Essentials, define the trap details and add the trap. NOTE: When you use the Unknown Traps button to add unknown traps received in OpenManage Essentials, the Enterprise OID, Generic ID and Specific ID fields are automatically populated.
The Revert Trap view displays all the pre-defined trap definitions that you edited. 3. In the Edited Traps grid, select the traps you want to revert and click Revert Traps. The confirmation dialog box is displayed. 4. Click Yes. Configuring SNMP V3 Traps The latest version of OpenManage Essentials supports the SNMP V3 Traps. The SNMP V3 Traps offer enhanced security than V1/V2c notifications. The Windows Trap service is disabled when SNMP V3 Traps is selected. For more information, see Alert Settings.
17 Alerts — Reference This page provides the following information: • Common Tasks – Alert Log Settings – New Alert View Filter – New Alert Application Launch Action – New Alert Email Action – New Alert Ignore Action – New Alert Trap Forward Action – SNMP V3 Trap Configuration • Alert Logs – Alert View Filters * All Alerts * All Internal Alerts * Critical Alerts * Info Alerts * Normal Alerts * Unknown Alerts * Warning Alerts • Alert Actions – Application Launch – E-mail – Ignore – Trap Forwarding • A
Related link Configuring Alert Log Settings Configuring Alert Actions Setting Up E-mail Notification Creating a Custom Script Alert Logs Fields Alert Log Settings Severity Predefined Alert View Filters The following table lists the predefined alert view filters. Table 185. Predefined Alert View Filters Field Description All Alerts Select to view all the alerts. Critical Alerts Select to view all the systems that are critical. Info Alerts Select to view informational alerts.
Alert Details Table 187. Alert Details Field Description Severity The alert severity. Acknowledged Whether the alert has been acknowledged or not by the user. Recommended Resolution Click to view the recommended resolution for the issue that resulted in the alert. NOTE: The recommended resolution is available only for alerts received from either OMSA installed on the server or the iDRAC of the server.
Field Description Save Purged Alerts If selected, the specified number of alerts are purged and saved in a .csv file. Purged Alerts Location Specifies the location where the purged alerts are saved as a .csv file. Alert View Filters NOTE: You can receive alert notifications from OpenManage Essentials on your Android or iOS device by installing and setting up the OpenManage Mobile application. For more information, see OpenManage Mobile Settings and the Dell OpenManage Mobile User’s Guide at dell.
Acknowledgement Table 190. Acknowledgement Field Description Limit alerts based on the acknowledge flag Select to configure the alert view filter to display alerts based on whether the alerts have been acknowledged or not. This option is disabled by default. Match only acknowledged alerts Select to display acknowledged alerts. Match only unacknowledged alerts Select to display unacknowledged alerts.
• Alert Trap Forward Action — Forward the SNMP Trap to another management console when the alert action criteria is matched. By default, new alert actions are enabled. If you want to turn off the alert action without deleting it, you can disable it either through the right-click menu or the edit wizard for the alert action. Several common alert action use cases are pre-installed in the disabled state to illustrate common usage.
Field Description • • • • • • • • • • • • $sev = Severity $st = Service Tag $r = Recommended Resolution $e = Enterprise OID $sp = Specific trap ID $g = Generic trap ID $cn = Alert Category Name $sn = Alert Source Name $pkn = Package Name $at = Asset Tag $loc = Device Location $mod = Model Name Executable file: If you have an executable file (for example, createTroubleTicket.
Field Description NOTE: Alert actions are run when a matching alert is received; so the alert application launch action is a script or batch file that does not require user interaction. E-Mail Configuration You can configure Essentials so that you receive e-mail each time the alert associations for your devices meet specific alert criteria. For example, you may want to receive an e-mail message for all warning and critical alerts.
Field Description Test Action Forwards a test trap to the specified destination using the specified community string. SNMP V3 Configuration The following table describes the fields displayed in the SNMP V3 Configuration. Table 197. SNMP V3 Configuration Field Description Agent IP Address Provide the SNMP agent IP address. Engine ID Provide the unique engine ID of the SNMP agent. Username Provide the user name required to execute the task on the device.
Field Description Authentication Password Provide the authentication password. Encryption Protocol Select the encryption protocol for the discovery of the devices. The available options are AES, DES, and none. The device must be configured using the same encryption protocol for the discovery to be successful. Encryption Password Provide the encryption password.
Field Description Unknown Select to include unknown devices. VMware ESX Servers Select to include VMware ESX servers. Date and Time Range Table 200. Date and Time Range Field Description Limit Date Range Specifies a specific date range to match alerts. Limit Time Range Specifies a specific time range to match alerts. Limit Days Select to specify the days on which to enable the alert association.
Field Description Type The alert action type — App Launch, Email, Ignore, and Trap Forward. Description The description of the alert action. To The e-mail addresses to which the e-mail is sent. From The e-mail address from whom the e-mail originates. Subject The subject of the e-mail which may include alert tokens. Message The message of the e-mail which may include alert tokens. Destination The destination name or IP address used for trap forwarding.
Field Description EqualLogic Storage Select this category to include alerts for EqualLogic storage. FC-Switch Select this category to include alerts for Fibre Channel switches. General Redundancy Select this category to include alerts for General Redundancy. HyperV Server Select this category to include alerts for HyperV Server. iDRAC Select this category to include alerts for iDRAC. Juniper-Switch Select this category to include alerts for Juniper switches.
Field Description display all the traps defined for that category in the Edit Trap(s) grid. You can also navigate and select a particular trap from the category. Edit Traps Name Displays the trap name. Category Name Displays the category name of the trap. Severity Displays the severity of the trap. Format String Displays the message string that is displayed in the OpenManage Essentials alert logs.
Field Description SNMP Enterprise OID Provides the enterprise OID (SNMP OID prefix) of the management information base (MIB) file that defines the event source that you want to monitor. SNMP Generic Trap OID Provides the generic trap ID of the SNMP trap that you want to monitor from the desired event source. See the Dell OpenManage Server Administrator SNMP Reference Guide at dell.com/OpenManageManuals for more information on SNMP traps.
Field Description NOTE: If you do not select the check box, you have to manually select the traps and select the severity from the drop-down list. Traps Available for Import Name Displays the trap name from the MIB file. Category Name Displays the category name of the trap. Severity Displays the severity of the trap. You can modify the severity of the trap to: • • • • • • Unknown Info Normal Warning Critical By Value. See Severity Configuration By Value.
Remove MIB Table 208. Remove MIB Field Description Imported MIB(s) Displays the list of MIBs that are imported in the OpenManage Essentials database. Remove MIB Click to remove the imported MIBs from the OpenManage Essentials database. Troubleshooting MIB Import Issue: The MIB Import displays the following error message: Dependent MIB files need to be imported. Please import: RFC1155-SMI to the Mib Repository before continuing to import this Mib.
Field Description Enterprise OID To provide or edit the enterprise OID (SNMP OID prefix) of the event source that you want to monitor. Specific ID To provide the specific trap ID of the SNMP trap that you want to monitor from the required event source. Format String To provide or edit the message string that is displayed in the OpenManage Essentials alert logs. Severity Displays the severity of the trap.
Field Description Format String Displays the message string that is displayed in the OpenManage Essentials alert logs. Description Displays the trap description Generic Trap ID Displays the generic trap ID of the SNMP trap that you want to monitor from the required event source. Specific Trap ID Displays the specific trap ID of the SNMP trap that you want to monitor from the required event source.
18 Updating Server BIOS, Firmware, Drivers, and Applications With the System Update feature in OpenManage Essentials, you can: • Upgrade and downgrade firmware, drivers, BIOS, application, and OpenManage Server Administrator. • Compare the drivers and firmware on the inventoried servers and modular blade enclosures with a source catalog and update them if needed.
Figure 34. System Update Page 1. Compliance report. See Compliance Report 2. Tabbed systems information. See Compliant Systems, Non Compliant Systems, Non Inventoried Systems, and Issues and Resolutions. 3. System update tasks. See All System Update Tasks Understanding Server BIOS Firmware and Drivers Sources There are multiple sources for obtaining firmware and drivers for the servers. • Online source—Default option which obtains latest driver and firmware versions from ftp.dell.com.
Viewing Compliant Servers To view compliant servers: 1. Click Manage → System Update. 2. In System Update, select the Compliant Systems tab. Viewing Non-Compliant Systems To view non-compliant systems: 1. Click Manage → System Update. 2. In System Update, select the Non-Compliant Systems tab. Systems with drivers and firmware versions that are different from the catalog are displayed. Viewing Non-Inventoried Systems To view non-inventoried systems: 1. Click Manage → System Update. 2.
Protocol Used for Server IP Discovery and Inventory Protocol Used for iDRAC IP Discovery and Inventory Preferred System Update Mode Selected in Advanced Settings Credentials for System Update Actual Update Mode SNMP SNMP Out-of-Band (iDRAC) Server NOTE: When an iDRAC IP is discovered using SNMP, iDRAC software inventory is not retrieved and all components are updated are using Server Administrator irrespective of the preferred system update mode selected.
Protocol Used for Server IP Discovery and Inventory Protocol Used for iDRAC IP Discovery and Inventory Preferred System Update Mode Selected in Advanced Settings Credentials for System Update Actual Update Mode NOTE: When an iDRAC IP is discovered using WS-Man, the iDRAC software inventory is retrieved and the components are updated using iDRAC. However, if drivers are present in addition to BIOS, firmware, and applications, then all the components are updated using Server Administrator and not iDRAC.
3. In Non-Compliant systems, select the systems you want to update. NOTE: You can update multiple systems at the same time. NOTE: The following are the considerations when using 64-bit DUPs for system update: 4. • For in-band updates (Operating System) – If the selected target is a server running a Windows 64-bit operating system, all applicable 64-bit packages are available for update.
Examples: In a Windows domain environment, enter and password. In a Windows workgroup environment, enter and the password In a Linux environment, enter root and password. If you want to apply system updates using sudo, select Enable Sudo and update the SSH port number.
NOTE: You can update multiple systems at the same time. NOTE: The following are the considerations when using 64-bit DUPs for system update: • For in-band updates (Operating System) – If the selected target is a server running a Windows 64-bit operating system, all applicable 64-bit packages are available for update. If the catalog does not contain 64-bit packages for a component, the corresponding 32-bit package is available for update.
NOTE: Before you apply system updates using sudo, create a new user account, edit the sudoers file using the visudo command, and add the following: For target systems running a 32-bit operating systems: Cmnd_Alias OMEUPDATE = /bin/tar,/opt/dell/srvadmin/bin/omexec,/tmp/ LinuxPreInstallPackage/runbada,/tmp/LinuxPreInstallPackage/omexec,/tmp/invcol.
Issue Resolution iDRAC does not meet the minimum version requirements. Minimum supported iDRAC version for modular servers is 2.20 and for monolithic servers is 1.4. Manually install the required iDRAC versions to proceed. iDRAC does not have the required license. iDRAC requires license to perform system updates which can be obtained using License Manager. The server does not have Server Administrator installed on it or is discovered using SSH.
19 System Update — Reference You can access the following: • System Update page – Summary * Compliance Report * System Update Tasks * Tasks Execution History – Compliant Systems – Non Compliant Systems – Non-Inventoried Systems – All System Update Tasks – Issues and resolutions for updates • Catalog Section – Select a Catalog Source – View Active Catalog Related link Updating Server BIOS, Firmware, Drivers, and Applications Viewing the System Update Page Compliance Report Non-Compliant Systems System Up
Filter Option Description Does not contain Select to include the not present logic in search based on alphanumeric characters present in a text chunk. Is contained in Select to include the is present logic in an alphanumeric character string. Is not contained in Select to include the not present logic in an alphanumeric character string. Is less than Select to find a value that is less than the value you provide.
Field Description firmware, BIOS, drivers, and applications that are later than the versions installed on the systems. You can also set one of the following update modes as the default: • • In-Band (Operating System) — Allows you to update all components on the systems. Out-of-Band (iDRAC) — Allows you to update only the BIOS, certain firmware, and certain applications.
Field Description Click the non-compliant systems portion to view more information in the Non-Compliant Systems tab. Non-Inventoried Systems Discovered systems pending inventory when compared with available software in the active catalog. Click non-inventoried portion to view more information in the Non-Inventoried Systems tab. Compliant Systems The Compliant Systems tab provides this information: Table 216. Compliant Systems Field Description System Name Domain name of the system.
Field Description Installed Version The installed version number. Upgrade/Downgrade A green arrow indicates an upgrade. Available Version The available version number. Package Name The name of the software update. Related link System Update System Update Task Table 219. System Update Task Field Description Task Name Provide a name for the software update task. Select System to Update Select the system that you want to update. System Name Domain name of the system.
Field Description • Graceful Reboot without forced shutdown (Warm) — Select this option to shut down and then reboot the operating system without forcefully turning off the target system. • Graceful Reboot with forced shutdown (Warm with forced) — Select this option to shut down and then reboot the operating system by forcefully turning off the target system. NOTE: By default, the Graceful Reboot with forced shutdown reboot method is selected.
All System Update Tasks This page provides more information on the software update tasks. Table 221. All System Update Tasks Field Description Task Name The name of the task. Task Label Provides information on what the task does. Start Time Time and date of inventory. Related link System Update Issues and Resolutions Table 222. Issues and Resolutions Field Description System Name Displays the domain name of the system. Reason Displays the issue associated with the server.
Field Description • Warning NOTE: The task status displays warning if the After update if required, reboot the target server option was not selected for the system update task. Successful / Attempted Targets The number of target systems on which the task is successfully executed. End Time Time and date at which the system update task ends. Executed by User The user information.
Table 225. View Active Catalog Field Description Source Displays the source. The source is either Server Update Utility, FTP, or Repository Manager. Source Type The type for source from which the catalog file is taken. For example, Dell ftp site. Release ID The unique identification number assigned to the released catalog file. Release Date The date on which the catalog file was released. Newer version available Displays if a newer version is available.
20 Managing Remote Tasks About Remote Tasks With the Remote Tasks feature in OpenManage Essentials, you can: • Run commands on local and remote systems, run batch files and executable files on the local systems, and schedule local and remote tasks. NOTE: Ensure that you run the latest commands to successfully execute the remote tasks. NOTE: The files must be located on the system with OpenManage Essentials installed and not on the remote system. • Change power status for a system.
4. • RACADM Command Line— Select to run the RACADM commands on the remote system. Based on your selection in the preceding step, provide the following: • If you selected Remote Server Administrator Command, then provide command, SSH port number, and select Generate Trusted Key for Linux if you want to generate a trusted key. • 5. If you selected Generic Command, RACADM Command Line, or IPMI Command then provide command and append output information. Providing the append output information is optional.
You can enter tokens (substitution parameters) in the command line task to be passed to the script file, executable, command, or batch file and execute local scripts on devices that are discovered in OpenManage Essentials. To manage Generic command line tasks: 1. From OpenManage Essentials, click Manage → Remote Tasks → Common Tasks → Create Command Line Task. 2. In the General tab, choose Generic Command. 3. If required, update the task name. 4.
NOTE: The credentials are passed in plain text to the command line. If you schedule a task to run later, the credentials are encrypted and stored in the database. The credentials are decrypted when the task runs at the scheduled time. However, if you use the RUN option on a previously created task, enter both administrator credentials for the system and the script credentials. Managing Server Power Options You can create tasks to manage power on servers.
4. • Select servers on which you want to run this task and click Next. On Schedule and Credentials, set the schedule parameters, provide user credentials to enable the task. 5. If you want to deploy Server Administrator as a sudo user, select Enable Sudo and update the SSH port number.
Operating System Package VMware ESX 4 OM-SrvAdmin-Dell-Web-LX-6.5.0-2247.ESX41.i386_A01.tar.gz OM-SrvAdmin-Dell-Web-LX-6.5.0-2247.ESX41.i386_A01.tar.gz.sign Red Hat Enterprise Linux 5 OM-SrvAdmin-Dell-Web-LX-6.5.0-2247.RHEL5.x86_64_A01.4.tar.gz OM-SrvAdmin-Dell-Web-LX-6.5.0-2247.RHEL5.x86_64_A01.4.tar.gz.sign Red Hat Enterprise Linux 6 OM-SrvAdmin-Dell-Web-LX-6.5.0-2247.RHEL6.x86_64_A01.5.tar.gz OM-SrvAdmin-Dell-Web-LX-6.5.0-2247.RHEL6.x86_64_A01.5.tar.gz.sign Arguments Clean Installation Table 228.
• Select a query from the drop-down list or create a new query by clicking the New button. • Select servers on which you want to run this task and click Next. 4. NOTE: Devices that are not applicable for the iDRAC Service Module deployment are not available for selection in the Task Target. Moving the mouse pointer over such a device in the Task Target displays a tool tip that indicates why the iDRAC Service Module cannot be deployed.
Operating System • Package CentOS 6.5 SUSE Linux Enterprise Server 11 dcism-1.0.0-4.435.1.sles11.x86_64.rpm Red Hat Enterprise Linux 5 dcism-1.0.0-4.435.1.el5.x86_64.rpm Red Hat Enterprise Linux 6 dcism-1.0.0-4.435.1.el6.x86_64.rpm Collecting Firmware and Driver Inventory The Create F/W & Driver Inventory Task allows you to collect firmware and driver inventory information from a server.
NOTE: To revert to gathering firmware and driver inventory information through OMSA, you must either run the firmware and driver inventory task or delete and rediscover the device. • 4. F/W and Driver task based inventory — Select to gather firmware and driver inventory information through the inventory collector component, even though OMSA may be installed on the device. On Task Target, do one of the following: • Select a query from the drop-down list or click New to create a new query. 5.
Use Cases in Remote Tasks Server Power Options Sample-Power On Device—Enable this use case to turn on the server. The system must have RAC/DRAC configured. Deploy Server Administrator Sample-OMSA Upgrade Windows—Enable this use case to upgrade OpenManage Server Administrator on a Windows-based system. Command Line • Sample - Windows OMSA Uninstall — Enable this use case to uninstall OMSA on a system running the Windows Server operating system.
To use the Sample - Server XML Configuration command line task: 1. In the OpenManage Essentials Remote Tasks portal, right-click the Sample - Server XML Configuration, and click Clone. The Input information for the newly cloned task dialog box is displayed. 2. Provide the Cloned Task Name and click OK. 3. Right-click the created cloned task and click Edit. The Create a Command Line Task dialog box is displayed. 4.
Table 232.
Remote Task Type All Servers (except ESXi) With Server Administrator and Discovered Using SNMP/WMI Windows-based Servers without Server Administrator and discovered using WMI Linux-based Servers without Server Administrator and discovered using SSH DRAC/iDRAC is not discovered DRAC/iDRAC discovered using IPMI DRAC/iDRAC discovered using SNMP/ WS-Man Server operating system is not discovered IPMI command task Not supported Not supported Not supported Not supported Not supported RACADM command Su
21 Remote Tasks — Reference From Remote Tasks you can: • Run commands on local and remote systems, batch files and executable files on the local systems, and schedule local and remote tasks. • Change power status for a system. • Deploy OpenManage Server Administrator on systems. • Deploy the iDRAC Service Module on systems. • Collect firmware and driver inventory. • View the remote tasks.
Related link Managing Command Line Task Managing RACADM Command Line Tasks Managing Server Power Options Deploying Server Administrator Collecting Firmware and Driver Inventory Working With Sample Remote Tasks Use Cases Using the Sample - Server XML Configuration Command Line Task Deploying iDRAC Service Module Remote Tasks Remote Tasks — Reference Remote Tasks Remote Tasks page lists the following information: • All Tasks • Server Power Options • Server Administrator Deployment • Command Line • F
Related link Managing Command Line Task Managing RACADM Command Line Tasks Managing Server Power Options Deploying Server Administrator Collecting Firmware and Driver Inventory Working With Sample Remote Tasks Use Cases Using the Sample - Server XML Configuration Command Line Task Deploying iDRAC Service Module Remote Tasks Remote Tasks — Reference Task Execution History Lists the details of the system update tasks or remote tasks. Table 235.
Table 236. Server Power Options Field Description General Task Name Provide a name for this server power options task. Select the type Select from the following options: • • • • Shutdown OS first Reboot — Restarts the system without powering off. Power Cycle — Powers off and then restarts the system. NOTE: Make sure that the shutdown option is configured for the operating system before you perform a graceful shutdown using this option.
Field Description Password — Provide the password. Power On works only on target systems with iDRAC; use the IPMI credentials to perform Power On task. If you selected Power On, then provide the KG key. KG Key — Enter the KG Key. DRAC also supports IPMI KG Key. Each BMC is configured to require an access key in addition to user credentials. The KG key is prompted only for power-on task and not other power tasks because it is an IPMI task.
Field Description – For deploying the .rpm file, the RPM-GPG-KEY file must be available in the same folder as the .rpm file. Install Arguments NOTE: Applicable only for Server Administrator deployment task. (Optional) Provide arguments.
Related link Deploying Server Administrator Device Capability Matrix Command Line Task Select this option to create command line tasks. Table 238. Command Line Task Field Description Task Name Provide name of the task. Remote Server Administrator Command Select this option to run Remote Server Administrator Command on selected servers. Generic Command Select this option to run executable and commands on the system with OpenManage Essentials.
Field Description Include errors Select to write all OpenManage Essentials-detected errors to the log file. For example, if no response is received to a ping request before the execution of the command, an error is written to the log file. SSH Port number Provide the Secure Shell (SSH) port number on the managed Linux system. The default value for the port number is 22. Generate Trusted Key for Linux Select this option to generate a trusted device key for communicating with devices.
Related link Command Line Task Managing Command Line Task Using the Sample - Server XML Configuration Command Line Task Generic Command Table 240. Generic Command Field Description Task Name Enter a name for the task. By default, the task name is populated in the format: -. Command Provide the fully qualified path name and file name of the executable, command, or script file that launches the application program. For example: • • • Tracert C:\scripts\trace.bat D:\exe\recite
Field Description – Daily — To run the task once every day. – Weekly — To run the task once every week. – Monthly — To run the task once every month. Range of Recurrence: • • • Enter the credentials with appropriate privileges to run this task on this system Start — To specify the date and time at which the task should begin. No End Date — To continuously run this task based on the selected frequency. For example, if you selected Hourly, then this task continuously runs every hour from the start time.
Field Description • • • • • Activate Schedule — Select this option to activate a schedule for the task. Run now — Select this option to run the task immediately. Set schedule — Select this option to set a date and time for the task to run. Run Once — Select this option to run the task on the planned schedule only once. Periodic — Select this option to run the task frequently at specified intervals. – Hourly — Select this option to run the task once every hour. – Daily — To run the task once every day.
Field Description log file. If you select this option, you must enter the path name and file name of the log file. This option is disabled by default. Append Select to append output from the completed command to the specified file. If the file does not exist, it is created. Include errors Select to write all OpenManage Essentials-detected errors to the log file. For example, if no response is received to a ping request before the execution of the command, an error is written to the log file.
Firmware and Driver Inventory Collection Task Select this option to collect firmware and driver inventory information from a server that does not have OpenManage Server Administrator installed. Table 243. Firmware and Driver Inventory Collection Task Field Description General Task Name Provide a name for the inventory collection task. Filter devices based on operating system Select to filter devices to be displayed in the Task Target based on the selected operating system.
Field Description • • • Enter credentials of the remote targets Start — To specify the date and time at which the task should begin. No End Date — To continuously run this task based on the selected frequency. For example, if you selected Hourly, then this task continuously runs every hour from the start time. End By — To stop the task at the specified date and time. User Name — Provide in the format domain\user name or local host\user name. Password — Provide the password.
22 Managing Security Settings Using Security Roles and Permissions OpenManage Essentials provides security through role-based access control (RBAC), authentication, and encryption. RBAC manages security by determining the operations run by persons in particular roles. Each user is assigned one or more roles, and each role is assigned one or more user rights that are permitted to users in that role. With RBAC, security administration corresponds closely to an organization's structure.
Microsoft Windows Authentication For supported Windows operating systems, OpenManage Essentials authentication is based on the operating system's user authentication system using Windows NT LAN Manager (NTLM v1 and NTLM v2) modules. For the network, this underlying authentication system allows you to incorporate OpenManage Essentials security in an overall security scheme. Assigning User Rights You do not have to assign user rights to OpenManage Essentials users before installing OpenManage Essentials.
Supported Protocols and Ports on Management Stations Table 244. Supported Protocols and Ports on Management Stations Port Number Protocol Port Type Maximum Encryption Level Direction Usage 21 FTP TCP None In/Out Access ftp.dell.
Port Number Protocol Port Type Maximum Direction Encryption Level Usage 3389 RDP TCP 128-bit SSL In/Out Contextual application launch — Remote desktop to Windows terminal services. 5900–5901 Proprietary TCP None In/Out iDRAC virtual media service. 5900–5901 Proprietary TCP None In/Out iDRAC console redirection.
23 Troubleshooting OpenManage Essentials Troubleshooting Tool The OpenManage Essentials troubleshooting tool is a standalone tool that installs along with OpenManage Essentials. You can use the troubleshooting tool for a wide array of protocol related problems that are often at the root of discovery and alert issues. This tool provides the following protocol-specific diagnostics to identify the problem with the remote node: • Database—Fetches all the user defined databases present on the remote box.
Troubleshooting Device Discovery If a device discovery is not successful, perform the following steps to troubleshoot and fix the problem: 1. If the device assigned for discovery is a PowerEdge system, ensure that OpenManage Server Administrator is installed on it. 2. To discover Windows devices successfully, configure the SNMP services appropriately. For detailed information on configuring SNMP services on Windows, see Configuring SNMP Services on Windows. 3.
Troubleshooting Discovery of Windows Server 2008–Based Servers You also have to allow the server discovery. By default, the option is disabled in Windows Server 2008. 1. Click Start → Control Panel → Network and Internet → Network and Sharing Center → Advanced Sharing Setting. 2. Choose the drop-down arrow for the applicable network profile (Home or Work / Public) and under Network Discovery, select Turn on network discovery. Troubleshooting SNMP Traps for ESX or ESXi Versions 3.5, 4.x, or 5.
NOTE: You cannot remove the certificate errors unless you use the fully qualified name of the server running OpenManage Essentials. Troubleshooting Map View Question: Why is the Map View feature not available? Answer: The Map View feature is available only if you have discovered any PowerEdge VRTX CMC or PowerEdge FX2/FX2s devices with an Enterprise license, using the WS-Man protocol. If the device with an Enterprise license is discovered using the SNMP protocol, the Map View feature is not available.
24 Frequently Asked Questions Installation Question: How do I install OpenManage Essentials using a remote SQL database named instance? Answer: To connect remotely, the SQL Server with named instances requires a running SQL Server Browser service. Question: Will OpenManage Essentials support Microsoft SQL Server Evaluation edition? Answer: No, SQL Server Evaluation edition is not supported.
1. Create a backup of the OpenManage Essentials version 1.1 database. 2. Migrate the OpenManage Essentials version 1.1 data from SQL Server 2005 to SQL Server 2008, 2008 R2, or 2012. For more information, see the OpenManage Essentials Database re-target process instructions at http://en.community.dell.com/ techcenter/systems-management/f/4494/t/19440364.aspx. 3. Ensure that OpenManage Essentials version 1.1 can connect to migrated database and works as expected. 4.
Setting Result /i SysMgmt.msi – Installs the Server Administrator software. /i SysMgmt.msi /qn This command carries out a fresh installation of version 6.1. /x This command uninstalls a product. /x SysMgmt.msi – Uninstalls the Server Administrator software. /q[n|b|r|f] This command sets the user interface (UI) level. /q or /qn – no UI. This option is used for silent and unattended installation. /qb – basic UI. This option is used for unattended but not silent installation.
Table 247. Software Feature IDs Feature ID Description ALL All features BRCM Broadcom NIC Agent INTEL Intel NIC Agent IWS OpenManage Server Administrator Web Server OMSM Server Administrator Storage Management Service RmtMgmt Remote Enablement RAC4 Remote Access Controller (DRAC 4) RAC5 Remote Access Controller (DRAC 5) iDRAC Integrated Dell Remote Access Controller SA Server Administrator NOTE: Only iDRAC6 is supported on xx1x systems.
Error Code Value ERROR_SUCCESS_REBOOT_REQUIR 3010 ED Description A restart is required to complete the installation. This message is indicative of a successful installation. NOTE: See support.microsoft.com for full details on all the error codes returned by the msiexec.exe and InstMsi.exe Windows installer functions.
Answer: Per RFC 952, underscores are not valid in DNS names. A name (net, host, gateway, or domain name) is a text string up to 24 characters drawn from the alphabet (A-Z), digits (0-9), minus sign (-), and period (.). Periods are only allowed when they serve to delimit components of domain style names. For more information see,ietf.org/rfc/rfc952.txt and zytrax.com/books/dns/apa/names.html .
HTTPS = 5986 TrustedHosts Question: I have discovered a PowerEdge R830 server by using in-band method. OMSA version 8.3 is also installed on the server. Why am I unable to view the software inventory information of the iDRAC and network cards such as Mellanox, QLogic, and Intel? Answer: To get the software inventory information of the network cards, you must either discover the PowerEdge R830 server by using out-of-band method or run the Firmware and Driver Inventory task for the server.
3. b. c. In the Security section, select Use TLS 1.0, Use TLS 1.1, and Use TLS 1.2. To enable TLS for all user accounts: 1. Create a DWORD registry entry SecureProtocols in [HKLM]\Software\Microsoft\Windows \CurrentVersion\Internet Settings. 2. Set the value to 0xA80 to enable support for TLS 1.0, TLS 1.1, and TLS 1.2. Restart the system, and then retry the tasks in OpenManage Essentials.
The blade servers will use the WS-Man credentials during the next inventory cycle. System Update Question: As an OpenManage Essentials administrator (OMEAdmin), what do I do if I am unable to perform system updates on devices? Answer: To resolve this issue, perform one of the following steps: • • Add the OMEAdmin to the server administrator group. Reduce the user control settings by clicking Start → Control Panel → User Accounts → Change User Account Control Settings.
Answer: 1. Download the catalog to the OpenManage Essentials system directly or use a System Update Utility DVD in the local system drive. 2. Browse for catalog.xml file on the local system or DVD (not on a file share, it is possible to use a file share, but for troubleshooting, do not use file share). 3. Now, create software update tasks. If tasks fail, more information is found in the task details. 4. Try setting all internet explorer security settings to LOW if tasks do not run.
Answer: 1. Remove the user from the OmeAdministrators Windows user group. 2. In the Device Group Permissions portal, use the Edit Members of OmeSiteAdministrators option to select and add the user to the OmeSiteAdministrators role. 3. When the user logs in again, the user will be an OmeSiteAdministrator. Question: A user is removed from the OmeAdministrators role and then added to the OmeSiteAdministrators role.
• NIC.Integrated.1-2-2, which represents partition 2 of port 2 of a NIC that is integrated on the system board. • NIC.Slot-3.1.2, which represents partition 2 of port 1 that is available on an NIC adapter that is inserted in slot 3 on the system board. Question: After a deployment task is completed, the results section on the task Execution Details window displays the same FQQD for all partitions of a NIC.
Log Levels Setting the log levels determines the range of message severity type you want to log. The following table describes the log message severity levels that you can assign to LOG_LEVEL_MIN and LOG_LEVEL_MAX. Table 249. Log Levels Severity Level Description Trace Detailed information related to code flow. NOTE: It is not recommended to set the minimum log level to trace unless instructed to do so by technical support. Debug Detailed information that may be useful when diagnosing problems.
Enabled : 1 UDP port : 161 Communities : public Notification targets : @162/public Options : EnvEventSource=sensors 341
25 Managing Device Group Permissions The Device Group Permissions portal allows OmeAdministrators to grant users the permission to perform system updates and run remote tasks on select device groups. Using the Device Group Permissions portal, OmeAdministrators can: • Add users to the OmeSiteAdministrators role. • Assign device groups to each user in the OmeSiteAdministrators role, allowing the user to perform system updates and run remote tasks on only the assigned device groups.
• In the Manage Device Group Permissions pane, right-click OmeSiteAdministrators, and click Edit Members of OmeSiteAdministrators. The Edit Members of OmeSiteAdministrators dialog box is displayed. 3. Type or select the domain name and user name in the appropriate fields, and click Add. 4. Select the user from the list and click OK. The user is displayed in the OmeSiteAdministrators tree view in the Manage Device Group Permissions pane.
• In the Manage Device Group Permissions pane, right-click OmeASitedministrators, and click Edit Members of OmeSiteAdministrators. The Edit Members of OmeSiteAdministrators dialog box is displayed. 3. Clear the check box beside the user who you want to remove from the OmeSiteAdministrators role. 4. Click OK. The user is removed from the OmeSiteAdministrators tree view in the Manage Device Group Permissions pane.
26 OpenManage Mobile Settings OpenManage Mobile is a systems management application that allows you to securely perform a subset of data-center monitoring and remediation tasks on one or more OpenManage Essentials consoles and/or integrated Dell Remote Access Controllers (iDRACs) using your Android or iOS device. Using OpenManage Mobile you can: • Receive alert notifications from the OpenManage Essentials management system/server. • View group, device, alert, and log information.
NOTE: omeAdministrator rights are required for enabling or disabling OpenManage Mobile subscribers. NOTE: OpenManage Mobile subscribers may be automatically disabled by OpenManage Essentials if their mobile service provider push notification service indicates that the device is permanently unreachable. NOTE: Even if an OpenManage Mobile subscriber is enabled in the Mobile Subscribers list, they can disable receiving alert notifications in their OpenManage Mobile application settings.
Status Icon Status Description NOTE: This service status only reflects successful communication with the platform notification service. If the device of the subscriber is not connected to the Internet or a cellular data service, notifications will not be delivered until the connection is restored. The service experienced an error delivering a message which may be of a temporary nature. If the problem persists, follow troubleshooting procedures or contact technical support.
Field Description Registration Displays the date and time the user added the OpenManage Essentials console in OpenManage Mobile. Delete Displays a delete icon that you can click to remove a subscriber from the Mobile Subscribers list. Troubleshooting OpenManage Mobile If OpenManage Essentials is unable to register with the Message Forwarding Service or successfully forward notifications, the following resolutions are available: Table 252.
27 Settings — Reference In the Settings page, you can configure the OpenManage Essentials console. You can set the SMTP and proxy server information, adjust session timeout, database maintenance schedules, restart services, create custom URL menu items, enable or disable internal alerts, observe daylight savings time, and enable or disable the ActiveX features. NOTE: After modifying the general settings, click Apply to save the changes.
Field Description Dedicated Trap listening port Enter the SNMP trap reception port. By default, the dedicated trap reception port is 162. Custom URL Settings Table 254. Custom URL Settings Field Description Name Displays the name assigned to the URL. Device Group Displays the device group associated with the URL. Custom URL Displays the URL. Description Displays the description provided for the custom URL. Date Created Displays the date the URL was created.
Field Description NOTE: The RAC name is displayed only if you have discovered the iDRAC with the WS-Man protocol. Otherwise, the system name is displayed instead of the RAC name. Identify devices with lost connection in device tree Select the check box to display the icon in the device tree and portals for devices that are not reachable. Discovery Settings The Discovery Settings page enables you to configure the type of wizard you want to use for discovering devices.
Email Settings Table 258. Email Settings Field Description SMTP Server Name or IP Address Enter the SMTP server name or IP address. Use Credentials Enable the user credentials. Domain \ User name Enter the domain and user name. Password Enter the user password. Port Check Use Default to use the default port number or manually add the port number. Use SSL Enable this check box to use SSL. Logging Select to enable or disable logging based on your preference. General Settings Table 259.
Field Description Essentials. Enabling this option adjusts the date and time values of scheduled items when daylight savings begin or ends. Client Time Zone Displays the time zone and UTC offset of the client’s time zone. OME Server Time Zone Displays the time zone and UTC offset of the server's time zone. OME Server Daylight Savings Status Displays the current daylight savings time status of the server's time zone and offset of daylight savings time.
Warranty Notification Settings The following table provides information about the fields displayed in the Settings → Warranty Notification Settings page. Table 261. Warranty Notification Settings Field Description Warranty Email Notifications Enable Warranty Email Notifications Enables or disables the sending of warranty email notifications. To The email addresses of the recipients of the warranty notification email. Each email address must be a valid email address.
Field Description Enable Warranty Popup Notification Enables or disables the display of the warranty popup notifications in the console. The warranty popup notification is displayed only if a device has warranty less than or equal to the days specified in All Devices with x Days or less of warranty . Warranty Update Settings Enable Warranty Updates Enables or disables the checking of warranty information of the discovered devices on the support site.
Purge Download Settings The Purge Download Settings page allows you to configure the settings for automatic purging of downloaded BIOS, firmware, driver, and application files. The following table provides information about the fields displayed in the Settings → Purge Download Settings page. Table 263. Purge Download Settings Field Description Enable purging of downloaded files Select to allow purging of the BIOS, firmware, drivers, or application files that are downloaded by OpenManage Essentials.
28 Logs — Reference From tools you can: • View User Interface Logs • View Application Logs Figure 35. Toolbar — Export Export Discovery Logs to File System — Export the logs that were generated while discovering devices. User Interface Logs Table 264. User Interface Logs Field Description Enabled Enable or disable logging of User Interface. Disable to increase performance. Log Asynchronous Calls Enable or disable logging for threading and asynchronous update method calls.
Application Logs Table 265. Application Logs Field Description Severity The severity of the recorded deviation in application’s behavior. Time The time at which this behavior occurred. Message Information on the behavior.
29 Dell Solutions The Dell Solutions portal provides a list of links to other tools associated with OpenManage Essentials. This page provides information about the tool, detects if the tool is installed, and allows you to launch the tool if it is installed. NOTE: You may require ActiveX to detect some extensions. To enable ActiveX, see General Settings in the Settings page. Table 266. Dell Solutions Field Description Name Displays the name of the tool. Description Displays the description of the tool.
30 Right-Click Actions The following tables lists all the right-click actions that are available in OpenManage Essentials. NOTE: The right-click options displayed in OpenManage Essentials are dependent on your access privilege. You must have administrator access to see all the options. Schedule View Table 267.
Device Status Table 269. Device Status Action Description IP address or device name Displays the IP address or name of the device. Application Launch Select to launch an associated application. Device Configuration • • • • • • • Refresh Device Configuration Inventory — Refresh the configuration inventory of the device. Add Devices to Repurpose and Bare Metal Device Group — Add the device to the Repurpose and Bare Metal Device Group.
Action Description NOTE: This option is only displayed if you right-click an IP address. Add Discovery Ranges to Select this option to add additional ranges to an existing group. NOTE: This option is only displayed if you right-click a group. Delete Select to delete a range. Disable Select to disable a range. Perform Discovery Now Select to do the discovery. Perform Discovery and Inventory Now Select to do the discovery and inventory.
Remote Tasks Table 273. Remote Tasks Action Description Edit Select to edit the task. Delete Select to delete the task. Run Select to run the task immediately. View Select to view the task. Activate Task Schedule Select to activate the task schedule. Clone Select to create a copy of a task. Custom URL Table 274. Custom URL Action Description Edit Select to edit the URL. Delete Select to delete the URL.
Templates Table 277. Templates Action Description Deploy Deploy the selected device configuration template. Clone Clone the selected device configuration template. Rename Rename the selected device configuration template. Delete Delete the selected device configuration template. Export Template Export the selected device configuration template. . Compute Pools Repurpose and Bare Metal Table 278. Repurpose and Bare Metal Action Description Create Compute Pool Create a compute pool.
Action Description Reclaim Identities Reclaim the virtual I/O identities of the server. Remove from Pool Remove a server from the compute pool. Replace Server Replace a server with another server from within the same compute pool. Virtual Input-Output Pools Virtual I/O Pool Table 281. Virtual I/O Pool Action Description Create Virtual I/O Pool Create a virtual I/O pool. Edit Edit the virtual I/O pool. View View the virtual I/O pool wizard. Rename Rename the virtual I/O pool.
Device Compliance Table 284. Device Compliance Action Description View Compliance Details View the compliance details for the selected device. Associate to Different Template Associate the selected device to another configuration template. Run Inventory Now Run the device configuration inventory for the selected device. Export Export the device compliance report as an HTML file. .
31 Tutorials You can use the tutorials for the setup options you need to complete when configuring OpenManage Essentials for the first time.
32 Using OpenManage Essentials Command Line Interface Launching the OpenManage Essentials Command Line Interface Click Start → All Programs → OpenManage Applications → Essentials → Essentials Command Line Interface. Creating a Discovery Profile Input File CLI commands that create discovery ranges or discovery groups require an XML-based file that defines the parameters for discovery protocols such as SNMP, WMI, Storage, WS-Man, SSH, and IPMI.
400 1 public user1 SHA1 AES 4 2
An example of the RangeList.csv is outlined as follows: Table 285. Examples of RangeList.csv Name SubnetMask 192.168.10.* 255.255.255.0 192.168.10.1-255 255.255.255.0 192.168.1-2.* 255.255.255.0 10.35.*.1-2 255.255.255.0 192.168.2.1 255.255.224.0 192.168.2.2 255.255.254.0 192.168.3.3 255.255.128.0 192.168.3.4 255.255.128.
• PS> Add-DiscoveryRange –Profile .\Samples\DiscoveryProfile.xml -RangeList .\Samples \RangeList.xml • PS> Add-DiscoveryRange –Profile .\Samples\DiscoveryProfile.xml -RangeListCSV .\Samples \RangeList.csv Removing a Discovery Range Description: The Remove-DiscoveryRange command allows you to remove a discovery range. Enter the ranges either using an xml file or by specifying the range. For more information about the RangeList.xml file, see Specifying IPs, Ranges, or Host Names Using XML or CSV Files.
file. For more information about the DiscoveryProfile.xml and RangeList.xml files, see Creating a Discovery Profile Input File and Specifying IPs, Ranges, or Host names Using XML or CSV Files. Commands: • PS> Set-ModifyDiscoveryRange –Profile -Range • PS> Set-ModifyDiscoveryRange –Profile -RangeList Examples: • PS>Set-ModifyDiscoveryRange • PS> Set-ModifyDiscoveryRange \Samples\RangeList.xml –Profile .\Samples\DiscoveryProfile.
Disabling a Discovery Range or Discovery Range Group Description: The Set-DisableDiscoveryRange command allows you to disable a discovery range or a discovery range group. Enter the ranges either using an xml file or by specifying the range. For information about the RangeList.xml file, see Specifying IPs, Ranges, or Host names Using XML or CSV Files. Commands: • PS> Set-DisableDiscoveryRange -Range • PS> Set-DisableDiscoveryRange -RangeList
• PS> Set-RunDiscovery -DeviceName ,,..., • PS> Set-RunDiscovery -Range • PS> Set-RunDiscovery -GroupName • PS> Set-RunDiscovery -RangeList • PS> Set-RunInventory -DeviceName ,,..., • PS> Set-RunInventory -Range • PS> Set-RunInventory -GroupName • PS> Set-RunInventory -RangeList
Stopping a Running Discovery Range or Group Description: For any range, only one type of task, such as discovery, discovery and inventory, or status polling, can run at a given time. The Set-StopTask command allows you to stop a task associated with a discovery range or the tasks associated with the ranges belonging to a discovery range group. Commands: • PS> Set-StopTask -Range • PS> Set-StopTask -GroupName Examples: • PS> Set-StopTask -Range 10.35.1.
or PS> Add-DevicesToCustomGroup –GroupName MyServers –Devices PE2900-WK28-ZMD, PWRCODE.US.DELL.COM, HYPERVISOR, M80504-W2K8 Example of a DeviceList.xml file: Deleting a Group Description: The Remove-CustomGroup command allows you to remove a group from the root node.
