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. © 2018 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 New in this release............................................................................................................................................................ 19 Other information you may need....................................................................................................................................... 19 Contacting Dell....................
Drilling down charts and reports for more information.................................................................................................41 Saving and loading the portal layout................................................................................................................................. 42 Updating the portal data...................................................................................................................................................
Multithreading............................................................................................................................................................ 68 Scheduling inventory........................................................................................................................................................ 68 Configuring status polling frequency..............................................................................................................................
Discovery Ranges.............................................................................................................................................................85 Exclude Ranges................................................................................................................................................................85 7 Managing devices..........................................................................................................86 Viewing devices................
Exporting All Device Locations..................................................................................................................................105 PowerEdge FX Chassis View.......................................................................................................................................... 106 Tool Tip and Device Selection................................................................................................................................... 106 Overlays.......
Getting started for device configuration deployment...................................................................................................... 126 Viewing the Deployment Portal.......................................................................................................................................126 Configuring the deployment file share.............................................................................................................................
Deploying a device configuration template—Stateless deployment.......................................................................... 154 Automatic Locking of a Compute Pool......................................................................................................................156 Unlocking a Compute Pool........................................................................................................................................ 157 Editing the Definitions of a Compute Pool........
Select Devices.......................................................................................................................................................... 179 Edit Attributes...........................................................................................................................................................179 Summary..............................................................................................................................................................
Getting started for device configuration compliance.......................................................................................................212 Device configuration compliance overview..................................................................................................................... 213 Configuring the credentials and device configuration inventory schedule........................................................................213 Viewing the device configuration inventory...
Hard Drive Information............................................................................................................................................. 234 iDRAC Performance Minimum or Maximum............................................................................................................. 235 iDRAC Performance Average or Peak...................................................................................................................... 236 Memory Information....................
Flagging an alert.......................................................................................................................................................253 Creating and editing a new view.............................................................................................................................. 253 Configuring alert actions................................................................................................................................................
Alert Action — Duplicate Alert Correlation............................................................................................................... 273 Summary — Alert Action Details.............................................................................................................................. 273 Alert Categories..............................................................................................................................................................
Issues and Resolutions............................................................................................................................................. 298 Task Execution History.............................................................................................................................................299 Select a Catalog Source.................................................................................................................................................
Microsoft Windows authentication................................................................................................................................. 331 Assigning user rights....................................................................................................................................................... 331 Using Custom SSL Certificates—Optional......................................................................................................................
Adding Users to the OmeSiteAdministrators Role.......................................................................................................... 354 Assigning Device Groups to a User................................................................................................................................ 355 Removing Users From the OmeSiteAdministrators Role................................................................................................ 355 26 OpenManage Mobile Settings........
Custom URL ..................................................................................................................................................................375 System Update Tasks..................................................................................................................................................... 375 Attributes Tab....................................................................................................................................................
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.
Document Description Availability Dell EMC OpenManage Mobile User’s Guide Provides information about installing and using the OpenManage Mobile application. Dell EMC License Manager User's Guide Provides information about managing licenses and troubleshooting the License Manager. Dell EMC Repository Manager User's Guide Provides information about using the Repository Manager to manage system updates. Dell EMC OpenManage Essentials REST API Guide Provides information about integrating Dell.
2 Installing OpenManage Essentials Related links Download 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.
NOTE: OpenManage Essentials can maintain up to 175,000 task execution history details without any issues. If the task execution history details exceed 175,000, you may experience problems starting OpenManage Essentials. The earlier task execution history records are purged when the limit set under Task Settings → Task Execution History Records to be Retained is exceeded. The task execution history details of few tasks are not purged. For more information, see Task Settings.
• Warning — This warning condition may disable the Typical installation but not an Upgrade of the feature later during installation. Also, later during installation, use the Custom installation setup type to select the feature. • Information — This informational condition does not affect the Typical selection of a feature.
Custom Setup Installation To install OpenManage Essentials using custom setup: 1. In Custom Setup, click Change to change the installation location, and then click Next. 2. In custom settings for port numbers, if required, change default values for Network Monitoring Service port number, Task Manager Service port number, Package Server Port, and Console Launch port and then click Next. 3.
• Database is moved. Retargeting the OpenManage Essentials Database You can setup the OpenManage Essentials console to connect to an OpenManage Essentials database available on a remote system. For example, after installing OpenManage Essentials with a local database, you can back up and restore the OpenManage Essentials database on a remote system. After the database is restored on the remote system, you can setup OpenManage Essentials to connect to the restored database available on the remote system.
NOTE: The database restoration may not be successful if multiple instances of the backup file, OMEssentials.bak, are available on the system. To resolve the issue, rename both the files (OMEssentials and OMEssentials_log) in the Restore database file as section of the Restore Database window, and then try restoring the database. Creating a new user in SQL Server To create a new user in SQL Server: 1. Open SQL Server Management Studio on the system where you restored the OpenManage Essentials database. 2.
After the database retargeting is completed successfully, if required, you can delete the OpenManage Essentials database from the system on which OpenManage Essentials is installed. Installing OpenManage Essentials on a domain controller When installing OpenManage Essentials on a domain controller, it is recommended that you install OpenManage Essentials with a remote database.
NOTE: If SQL Server is not already installed on the domain controller, the Prerequisites window displays a warning message with a link that allows you to install SQL Express on the domain controller (local) with an OpenManage Essentials-specific SQLEXPRESSOME database instance. If you ignore the warning message, when the OpenManage Essentials installation begins, a message is displayed requesting you to confirm whether you want to install OpenManage Essentials with a local or remote database 5.
Creating a Domain Service Account A domain service account is required to run SQL Server on the domain controller. To create a domain service account: 1. Click Start → Administrative Tools. 2. Select Active Directory Users and Computers. 3. On the left pane, right-click Managed Service Account → New → User. The New Object – User window is displayed. 4. Type the first name and user logon name in the appropriate fields, and click Next. 5.
5. Click OK. 6. In Obejct Explorer, right-click the top-level SQL Server object and click Restart. Verifying SQL Server TCP or IP Status To verify the TCP/IP status of SQL Server: 1. Click Start → All Programs → SQL Server Configuration Manager NOTE: If multiple versions of SQL Server Configuration Manager are installed, ensure that you select the latest version. 2. On the left pane, click to expand SQL SQL Native Client 11.0 Configuration. 3. Click Client Protocols. 4.
NOTE: If the proxy server credentials are not provided, SupportAssist Enterprise connects to the proxy server as an anonymous user. c. If the proxy server requires authentication, select Proxy requires authentication, and then provide the following information in the corresponding fields: • Username — The user name must contain one or more printable characters, and must not exceed 104 characters. • Password — The password must contain one or more printable characters, and must not exceed 127 characters.
• To accept the default installation path, choose Typical installation and click Next. • 7. To enable specific program features and change the installation path, select Custom installation and click Next. In Custom Setup, select the License Manager features that you require; check for disk space, assign a new location for installing License Manager. In the Ready to Install screen, click Install. 8. After the installation is complete, click Finish.
NOTE: For information about the supported ports and protocols, see Supported protocols and ports in OpenManage Essentials. 7. Click Ok . 8. Click Install. 9. After the installation is complete, click Finish. After the upgrade, when you launch OpenManage Essentials version 2.5 for the first time, the Feature Usage Settings window is displayed. To understand and improve the most used features in OpenManage Essentials, few nonsensitive information is collected, and this feature is enabled by default.
5. Click OK. The selected chassis template is recreated. NOTE: The recreated chassis template name is not changed. 6. Click the recreated chassis template and click the Attributes tab to make the desired changes to the template attributes. NOTE: For compliance and deployment related tasks, ensure that the chassis has an enterprise license, supported firmware version, and is discovered by using the WS-Man protocol. For more information, see Device requirements for deployment and compliance tasks.
Migrating IT Assistant to OpenManage Essentials Direct migration from IT Assistant to OpenManage Essentials version 2.5 is not supported. However, you can migrate IT Assistant to an earlier version of OpenManage Essentials, and then upgrade to OpenManage Essentials version 2.5. For information about migrating IT Assistant to an earlier version of OpenManage Essentials, see the appropriate Dell EMC OpenManage Essentials User's Guide at Dell.com/OpenManageManuals.
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.
Related link Using the OpenManage Essentials Home Portal Configuring the Discovery Wizard 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 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 links Searching items Using the search drop-down list Search results and the default actions Searching 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 Using the 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 links 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 links OpenManage Essentials Heading Banner Dashboard Schedule View Using the 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.
• 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 links 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 links 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 links 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 description of the features listed in the following table, see Legend and Definitions.
Protocol / Mechanism Simple Network Management Protocol (SNMP) Windows Management Instrumentation (WMI) Web ServicesManagement (WSMan) Traps/alerts Not supported Discovery Not supported 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 Classification Hardware inventory Application launch Not supported Not su
Protocol / Mechanism Simple Network Management Protocol (SNMP) Windows Management Instrumentation (WMI) Web ServicesManagement (WSMan) REpresentational State Transfer (REST) NOTE: Applicable only to iDRAC6 version 1.3 and later. Discovery and hardware inventory are not supported for iDRAC6 version 1.25 and earlier.
Protocol / Mechanism Simple Network Management Protocol (SNMP) Windows Management Instrumentation (WMI) Web ServicesManagement (WSMan) REpresentational State Transfer (REST) NOTE: Applicable only to PowerEdge M1000e with CMC firmware version 5.0.
Protocol / Mechanism Simple Network Management Protocol (SNMP) Windows Management Instrumentation (WMI) Web ServicesManagement (WSMan) REpresentational State Transfer (REST) Classification Application launch Traps/alerts Health Switch role VxFlex Ready Nodes Discovery Not supported Correlation Classification Monitoring Traps/ Platform Event Traps (PET) Application launch— VxFlex Ready Node Series Support Discovery Not supported Correlation Classification Monitoring Traps/ Platform Event Traps (PET) H
Protocol / Mechanism Intelligent Platform Management Interface (IPMI) Command Line Interface (CLI)a • Linux/ VMware ESX Not supported Driver OpenManage Server Administrator CLI Deploy OpenManage Server Administrator Server Updates • • • Secure Shell (SSH) Discovery Correlation 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 supporte
Protocol / Mechanism Intelligent Platform Management Interface (IPMI) Command Line Interface (CLI)a Secure Shell (SSH) Correlation iDRAC health a)You cannot perform this task if the device is not discovered, inventoried, or both. 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.
Protocol / Mechanism Simple Network Management Protocol (SNMP) Symbol EMC NaviSphere CLI Classification Hardware inventory Monitoring Application launch — Modular Disk Storage Manager (a) Compellent Discovery Classification Hardware inventory Monitoring Traps/alerts Application launch — Compellent console Not supported Not supported Tape Discovery Classification Hardware inventory Monitoring Traps/alerts Application launch — Tape console Not supported Not supported a) Requires Modular Disk Stora
• Putty — esxcli software vib list • VMware CLI — esxcli –server software vib list 7. Configure SNMP, for hardware alerts on the ESXi 5 host, to send SNMP traps to OpenManage Essentials. SNMP is not used for discovery. WS-Man is required for discovery and inventory of an ESXi 5 host. To group the VMs with the ESXi host in the OpenManage Essentials device tree after you discover the VM, SNMP must be enabled on the ESXi host and the VM. 8.
Figure 14. Discovery and Inventory Portal 1. Details from the last discovery and inventory task run. 2. Details of previously discovered and inventoried devices. 3. Details of tasks and their status. 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.
Protocols Device/ Operating System Ethernet switches Simple Network Management Protocol (SNMP) Web Services- Windows Management Management (WS-Man) Instrumentatio n (WMI) Intelligent Platform Management Interface (IPMI) Secure Shell (SSH) REpresentational State Transfer (REST) Supported N/A N/A N/A N/A N/A * Discovery of PowerEdge C4130, PowerEdge C6320, PowerEdge C6320p and PowerEdge C6420 can be performed using the same protocols that are used to discover any other non C-Series PowerEdge serv
• Dell Networking W-Series Mobility Controllers • Dell SonicWALL Firewall appliances (global health status is also not available) • Printers • PDU • UPS NOTE: Due to lack of Service Tag information, the warranty information of these devices is not available. Creating a discovery and inventory task 1. From OpenManage Essentials, click Manage → Discovery and Inventory → Common Tasks → Add Discovery Range. The Discover Devices wizard is displayed.
NOTE: iDRAC supports only the default SNMP port 161. If the default SNMP port is changed, iDRAC may not get discovered. • In WMI Configuration, to authenticate and connect to remote devices, provide the WMI parameters. The format for entering credentials for WMI must be domain\user name for domain-based networks or localhost\user name for nondomain based networks. • In Storage Configuration, to discover PowerVault modular disk array or EMC devices, edit parameters.
Discovering and inventorying devices by using WS-Man or REST protocol with a root certificate Before you begin, ensure that the root CA server, OpenManage Essentials management server, and WS-Man or REST target(s) are able to ping each other by hostname. To discover and inventory Dell EMC devices by using the WS-Man or REST protocol with a root certificate: 1. 2. Open the web console of the target device—iDRAC, CMC, or OpenManage Enterprise Modular (OME - Modular).
g. Click Yes. 17. Close the web browser and open the web console of the target device in a new browser window. 18. Discover and inventory the WS-Man target(s), in OpenManage Essentials using the newcert.cer RootCA signed certificate file.
9. Select Enable REST discovery and enter the MX7000 chassis credentials. 10. If required, change the timeout, retries and port values based on your preference, and then click Next. The WS-Man Configuration page is displayed. 11. Select Enable WS-Man discovery and enter the chassis credentials. 12. If required, change the timeout, retries, and port values based on your preference, and then click Next. 13.
NOTE: It is recommended not to schedule the discovery task at the same time as the Database Maintenance Execution Schedule, as the console is less responsive during database maintenance.
Related links Discovery and Inventory Portal Last Discovery and Inventory Discovered Versus Inventoried Devices Task Status Configuring status polling frequency 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. To configure status polling: 1.
Configuring task pop-up notifications 1. Click Settings → Task Notification Settings. 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.
Field Description 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. Inventory Range Displays the IP Address range or host name. Devices Inventoried Displays information on number of devices inventoried.
Related links 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. In OpenManage Essentials, click Manage → Discovery and Inventory → Discovery Portal → Discovery Portal. 2. In Discovered vs.
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 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. The subnet mask is used to determine the broadcast addresses for the subnet(s) part of the 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 collection data about discovery, inventory, and health information of Windows servers. 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) Enter a number to indicate the time that the discovery engine must wait for before timing out after requesting for a WS-Man connection. The valid range is from 1 to 360 seconds.
REST configuration options NOTE: During the discovery of MX7000 chassis, if Secure Mode is not selected under REST Configuration Options then OpenManage Essentials ignores the following certificate errors: • Common name errors • Untrusted certificate authority errors • Revocation errors However, other certificate errors are not ignored by OpenManage Essentials. Table 27. REST configuration Options Field Description Enable REST Discovery Select to discover the MX7000 chassis.
IPMI Configuration Use the IPMI protocol for out of band discovery of RACs, DRACs, and iDRACs. This option is for Lifecycle controller enabled discovery and inventory. Ensure that the IP address of the DRAC and iDRAC is selected. See IPMI Configuration Options to configure the IPMI version 2.0 parameters. This configuration is required for discovery. IPMI Configuration Options Table 29.
Summary View the configuration selections. To change configurations, click Back. Add Exclude Range From OpenManage Essentials, select Manage → Discovery and Inventory → Common Tasks → Add Exclude Range. Register new ranges to exclude from discovery or to remove a previously set exclude range. You can also right-click Exclude Ranges and select Add Exclude Range. Add Exclude Range Options Table 31.
Viewing Discovery Configuration To view discovery configuration, click Manage → Discovery and Inventory → Discovery Schedule. Discovery Schedule Settings Configure OpenManage Essentials to discover new devices on a network. The settings apply to all discovery ranges. OpenManage Essentials records all agents, IP addresses, and the health of the devices. Table 32. Discovery Schedule Settings Field Description Enable Discovery Select to schedule device discovery.
Inventory Schedule Use Inventory Polling to specify the default inventory settings for OpenManage Essentials. OpenManage Essentials collects inventory information such as software and firmware versions, as well as device-related information about memory, processor, power supply, Peripheral Component Interconnect (PCI) cards, and embedded devices, and storage. Related link Inventory Schedule Settings Inventory Schedule Settings Table 33.
Field Description 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. If OnDemand poll is disabled, the device status only updates on the normal status poll. Enable Status Polling Select to schedule device status polling.
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.
– HA Clusters – NAS Clusters • Hyper-Converged Infrastructure – VxRail – XC Series • KVM • Microsoft Virtualization Servers • Modular systems – Virtual machines – PowerEdge Chassis – PowerEdge FX2 – PowerEdge M1000e – PowerEdge MX7000 NOTE: In a Multi-Chassis Management (MCM) group, only the lead MX7000 chassis is displayed. – PowerEdge VRTX NOTE: The blade servers (iDRACs) in the chassis are discovered using the WS-Man credentials you provide for the chassis and are listed under the RAC group.
– Dell EMC Arrays – PowerVault MD Arrays – Tape Devices • Unknown • VMware ESX servers – Virtual machines • VxFlex Ready Nodes NOTE: If you delete the VxFlex Ready Nodes custom group then you need to recreate this group with the respective query. See Creating a New Group. 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.
Table 36.
Viewing alerts summary You can view all the alerts that are generated for a device. To view the alert summary: 1. Click Manage → Devices. 2. Expand the device type, and click the device. 3. On the details page, select Alerts. NOTE: In an MCM group, alerts are displayed if all the member chassis, compute sleds, storage, and IOMs are included in the alert policy that is configured for the lead MX7000 chassis.
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. From the first line after Where, select Device Type, Is, and then Server. 3. In the next line select the check box, then select AND, Device Health, Is, and then select Critical. 4.
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.
Disassociating a catalog baseline from custom device groups 1. Click Manage → Devices. 2. Right-click a custom device group and select De-associate Catalog Baseline. 3. Click Yes. Catalog baseline is disassociated. 4. Click Ok. The compliance status of the custom device group is updated under the Non-Compliant Firmware & Drivers tab.
Configuring Warranty Email Notifications You can configure OpenManage Essentials to send a warranty notification of your devices at periodic intervals through email. For information about the options you can configure, see Warranty Notification Settings. To configure Warranty Email Notifications: 1. Click Settings → Warranty Notification Settings. The Warranty Notification Settings page is displayed. 2. Under Warranty Email Notifications, select Enable Warranty Email Notifications. 3.
Configuring Warranty Pop-Up Notifications You can configure OpenManage Essentials to display warranty pop-up notifications based on the warranty status of the devices. For information about the options you can configure, see Warranty Notification Settings. To configure warranty pop-up notifications: 1. Click Settings → Warranty Notification Settings. The Warranty Notification Settings page is displayed. 2. 3.
Table 37. Using Map View Action Description Show All Map Locations Displays all map locations. Go to Home View Displays the home view, if saved earlier. Save Current View as Home View Saves the current view as the home view. Add Licensed Device Allows adding PowerEdge VRTX and PowerEdge FX2/FX2s devices with an Enterprise license. Import Licensed Devices Allows importing PowerEdge VRTX and PowerEdge FX2/FX2s devices with an Enterprise license.
Related links Devices — Reference Map View—Home Portal Map View Interface—Home Portal General Navigation and Zooming Home View Tool Tip Search Pin Map Providers Map View Interface—Devices Tab Configuring Map Settings Selecting a Device on Map View Health and Connection Status Multiple Devices at the Same Location Setting a Home View Viewing All Map Locations Adding a Device to the Map Moving a Device Location Using the Edit Location Details Option Importing Licensed Devices Using the Map View Search Bar Add
MapQuest Bing • Satellite map — Provides detailed satellite views of the world. NOTE: The MapQuest and the Bing map providers require an internet connection at all times to render the map. If the system connects to the internet through a proxy server, the proxy settings configured in your web browser is used by the MapQuest and Bing providers. Related link Using Map View Configuring Map Settings NOTE: Only OpenManage Essentials Administrators and Power Users are permitted to configure Map Settings.
• Click the magnifying glass icon map in the navigation toolbar to display a slider that you can use to zoom in or zoom out of the NOTE: Zoom level and the visible portion of the Map View (home) portal are not synchronized with the Map View tab accessible through the Devices portal. Related link Using Map View Home View If you have saved a particular region of the map as your home view, by default, the map displays the home view when you open the Map View.
Table 39. Health Status Pin Color Icon Health Status Red Critical Yellow Warning Green Normal Gray Unknown The following table provides information about the connection status and pin overlay: Table 40. Connection Status Pin Color Icon Connection Status Blue On Grey Off Related link Using Map View Multiple Devices at the Same Location It is possible for two or more licensed devices to be placed at an identical location. These devices are displayed as a multi-pin group on the map.
Related link Using Map View Viewing All Map Locations If a single device is selected, only that device is displayed on the map. To view all map locations that have been placed on the Map View: • Right-click the map, and click Show All Map Locations. • Move the mouser pointer over the Actions menu, and click Show All Map Locations.
3. In the Address field, type the location name or airport code. For example, New York. NOTE: Using the Address field to move a device location requires an Internet lookup through the map provider to resolve the provided address. The device is moved to the most appropriate location available from the Internet lookup. If the map provider is not able to resolve the address, a message is displayed, and the device remains at the current location. 4. Click Save.
NOTE: Any errors that may occur during the import process are displayed in Logs → UI Logs. Related links Using Map View Template for Importing Devices Template for Importing Devices The template for importing PowerEdge VRTX and PowerEdge FX2/FX2s devices with an Enterprise license is a .csv file that you can use to provide details about devices that you want to import to the map. The following are the fields available in the template: Table 41.
. Related link Using Map View Adding a Device Using the Search Pin NOTE: Only PowerEdge VRTX and PowerEdge FX2/FX2s devices with an Enterprise license that are not already placed on the map can be added to the map. NOTE: Only OpenManage Essentials Administrators and Power Users are permitted to add a device to the map. 1. Perform one of the following: • 2. Click Home → Map View. • Click Manage → Devices → Map View.
2. • Click Manage → Devices → Map View. On the Map View: • Right-click the map, and click Remove All Map Locations. • Move the mouser pointer over the Actions menu, and click Remove All Map Locations. The Remove All Map Items dialog box is displayed prompting for your confirmation. 3. Click Yes. Related link Using Map View Editing a Map Location NOTE: Only OpenManage Essentials Administrators and Power Users are permitted to edit a map location. To edit a map location: 1.
The Save As dialog box is displayed. 2. Browse to the location where you want to save the .csv file, type an appropriate file name, and click Save. Related link Using Map View PowerEdge FX Chassis View By default, the PowerEdge FX2 and FX2s chassis are classified in the device tree under All Devices → Modular Systems → PowerEdge FX. The compute sleds installed in the PowerEdge FX chassis, when discovered, are displayed under the appropriate PowerEdge FX device group in the device tree.
• 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. • If a slot with a compute sled is selected, the sled inventory, if available, is displayed under the Chassis View. • If slot with a sled that contains multiple compute nodes is selected, a summary of discovered devices (nodes) is displayed under the Chassis View.
Support For PowerEdge FX Chassis Sleds The sleds that can be installed in the PowerEdge FX2 and PowerEdge FX2s chassis may vary. The following are the types of sleds and their support in OpenManage Essentials: • Compute sleds — Require discovery and inventory for getting the inventory information and other functionality. Discovery and classification of these sleds can be performed using OMSA (in-band) or iDRAC (out-of-band).
Viewing the VLAN Configuration Inventory To view the VLAN configuration inventory of a chassis: 1. Click Manage → Devices. 2. In the device tree, click Modular Systems. 3. Click PowerEdge M1000e or PowerEdge FX2 and then click the chassis CMC node. 4. On the right pane, click the VLAN Configuration tab. The VLAN configuration inventory is displayed.
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. Type the credentials of the IOA that have fabric administrator rights. 6. Click Finish. The VLAN Configuration task is displayed in the Task Results tab. After the task is completed, OpenManage Essentials automatically inventories the VLAN configuration of the IOAs on the chassis.
Table 44. Dell NAS Appliance Support Dell EqualLogic FS7500 with FluidFS Version 1 Dell EqualLogic FS7500 with FluidFS Version 3 Dell PowerVault MD NX3500 with FuildFS Version 1 Discovery and Classification Support for discovery using both the EqualLogic Group Manager IP and management IP. If discovered using the controller IPs, it results in multiple entries. Support for discovery using the controller/node IPs.
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 45. 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 50.
Field Description Baseline Name Displays the name of catalog baseline associated with a device group. Model Type The systems model name. For example, PowerEdge. Operating System The operating system that is installed on the system. Service Tag A unique identifier, that provides the service lifecycle information. 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.
• Run an existing query • Create a new query • Delete a query Table 54. Device Search Field Description Run Existing Query Select this option and then select a query from the drop-down list. Delete Query Select to delete a query after you complete the following action. Select the Run Existing Query option, then from the drop down list select the query that you want to delete. Create New Query Select this option to create a query and then enter a name for the query in the adjoining field.
Device Group Configuration Table 56. Device Group Configuration Field Description Name Provide name of the new group. Parent The device under which this group is created. Description Provide description for the device group. Device Selection You can select predefined groups (device types), custom groups, specific devices, or a device query. To use device query, select a query from the list. Click New to create a new device query to search and assign the devices to the alert action.
Field Description VxFlex Ready Nodes Select to include VxFlex Ready Nodes and ScaleIO Ready Nodes. Summary — Group Configuration View and edit selections. Map View Interface—Devices Tab The following are the items displayed in the Map View and their descriptions. Table 58. Map View (Devices) Tab Interface Item Description Search bar Enables you to search for locations on the map. Internet connection warning Indicates if the system is not connected to the Internet.
Item Description • • • Scale MapQuest Provider (Licensed) Bing Road Provider (Licensed) Bing Satellite Provider (Licensed) Displays the current zoom level of the map in meters or kilometers. Devices at this location The Device at this location window is displayed when you double-click or right-click a multi-pin group and then select Details. The following are the fields displayed in the Devices at this location window: Table 59.
Field Description Apply Click to save the updates in the Map Settings dialog box.
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.
Related links Configuring the deployment file share Creating a device deployment template Adding devices to repurpose and bare-metal devices group Managing device deployment templates Deploying a device deployment template—Bare-metal deployment Deploying a device configuration template—Stateless deployment Deploying a network ISO image Auto deploying device configurations Viewing the Deployment Tasks Additional information Server Configuration Management license NOTE: Installing and using OpenManage Essent
• Select a device in the device tree. The License Information table in the device inventory indicates the licenses installed on the device. Viewing unlicensed server targets To view the server targets for configuration management that do not have the Server Configuration Management license installed: 1. Navigate to the Manage > Configuration > Device Configuration Compliance Portal. 2. In the Device Compliance pie-chart, click the Non-licensed segment.
Related links Creating a device deployment template from a device configuration file Creating a device deployment template from a reference device Deploying a device deployment template—Bare-metal deployment Deploying a device configuration template—Stateless deployment Deploying a network ISO image Setting up device configuration auto deployment—Bare-metal deployment Configuring the credentials and device configuration inventory schedule Viewing the device configuration inventory Getting started for devic
A warning message is displayed indicating that you must upgrade to the latest firmware version which uses the streaming functionality. Indicate your confirmation to proceed. The deployment file share is now configured. Related link Getting started for device configuration deployment Adding devices to repurpose and bare-metal devices group Adding devices to the Repurpose and Bare Metal Devices group is a prerequisite for deploying either a configuration template or a network ISO image on those devices.
Related links Getting started for device configuration deployment Creating a device deployment template Editing a device deployment template Deploying a device deployment template—Bare-metal deployment Creating a device deployment template The Create Template task creates a device deployment template that includes the attributes of a server, chassis, or an IOA. Using the device deployment template, you can: • Deploy the configuration on another server, chassis, or an IOA.
6. Navigate and select the configuration file, and then click Open. 7. Click Finish. The deployment template that is created is displayed in the Templates pane. NOTE: IOA templates can only be created and deployed. The IOA templates that you create are displayed only in the Deployment Portal.
Managing device deployment templates The device deployment templates contain various attributes of a server, chassis, or IOA. Before you use the template for deployment, you can: • View the attributes of a device deployment template. • Clone a device deployment template. • Edit a device deployment template. • Export a device deployment template. • View the properties of a device deployment template.
Editing a device deployment template You can edit a device deployment template to change the values of the attributes before you deploy on the target devices. NOTE: Editing of an IOA template is not supported. To edit a device deployment template: 1. Click Deployment → Deployment Portal. 2. In the Templates pane, right-click a template, and then click Edit. 3. The boot configurations and the network interface settings are displayed in the Boot and Network Configuration tab in the right pane.
b. To assign IOA ports to the configured VLANs: 1. Click VLAN Configuration. 2. Select the port, and then assign the Tagged and Untagged VLANs. 3. To save the VLAN attributes, click Save, and then click Yes to confirm. 12. Click Save. Related link Managing device deployment templates Exporting a device deployment template You can export a device deployment template to an XML (server configuration template) or an INI (chassis configuration template) file.
The Deploy Template Wizard wizard is displayed. 3. On the Name and Deploy Options page: a. Enter an appropriate name for the task. b. Under Deploy Target, select Bare Metal. c. Under Select Deploy Options, select Deploy Template. NOTE: If you want to deploy a configuration template and then boot the device to a network ISO image, you can select both Deploy Template and Boot to Network ISO. Separate tasks are created for each operation. d. Click Next. 4. On the Select Template page: a.
l. (For IOA VLAN configuration deployment only) Click the IOA VLAN Attributes tab to view the IOA VLAN attributes for the selected template. m. Click Next. 8. On the Set Schedule page: a. Select either Run now, or click the calendar icon and select the date and time you want to run the task. b. Under Execution Credentials: • For server configuration deployment — type the credentials that have Administrator privileges on the iDRAC of the target servers.
• The deployment file share is configured. For more information, see Configuring the Deployment File Share. • The device from which you are creating a chassis template meets the requirements specified in Device Requirements for Deployment and Compliance Tasks. • The chassis and IOAs must be discovered by using WS-Man, REST, and SNMP protocols. NOTE: The chassis template cannot be created if devices are discovered by using SNMP protocol only. To create a chassis deployment template from a chassis: 1.
NOTE: Compliance-related tasks are not supported for IOA attributes. Viewing and editing chassis deployment template attributes 1. Click Deployment → Deployment Portal → Templates pane. 2. Select either a sample chassis template or a chassis template that you created. For MX7000 chassis, select an MX chassis template from the list. The different groups of template attributes are displayed in the right pane 3.
NOTE: From the All Applicable Devices tree, select only chassis to add to the repurpose and bare-metal group. Selecting the IOAs is not mandatory. If the IOA attributes are present in the template and the target chassis is in the bare-metal group, then the deployment happens on the IOAs also. • You have created a chassis infrastructure template. • The target devices meet the requirements that are specified in Device Requirements for Deployment and Compliance Tasks.
NOTE: Deploying the template with the changed Static IPv4 Address starts a new discovery task for the device. For more information about the task details, see Task Status. The new Static IPv4 Address is added to the discovery range under Manage → Discovery and Inventory → Discovery Ranges → All Ranges. 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. e.
The Deployment Portal is displayed. 2. Perform one of the following: • In the Common Tasks pane, click Deploy Template. • In the Templates pane, right-click the IOA template that you want to deploy, and click Deploy. • In the Compute Pools pane, right-click a compute pool that has the target device, and then click Deploy. The Deploy Template Wizard wizard is displayed. 3. On the Name and Deploy Options page: a. b. c. d. 4. Type an appropriate name for the task.
IOA operational modes and the deployment task status Table 62.
6. On the Set Schedule page: a. Select either Run now or click the calendar icon and select the date and time you want to run the task. b. Under Execution Credentials, type the credentials that have Administrator privileges on the iDRAC of the target servers. c. Click Next. 7. On the Summary page, review the information that you have provided, and then click Finish. 8. If you want to continue the deployment, click Yes.
Related links Configuring Auto Deployment Settings Setting up device configuration auto deployment—Bare-metal deployment Managing Auto Deployment Credentials Adding a Discovery Range for Auto Deployment Configuring Auto Deployment Settings The Auto Deployment Settings allows you to perform the following: • Enable or disable the device configuration auto deployment. • Set the recurrence of the device configuration auto deployment task. To configure the auto deployment settings: 1.
The Setup Auto Deployment wizard is displayed. 3. On the Select Deploy Options page: a. Under Deploy Target, click Bare Metal. b. If you want to auto deploy a configuration template and then boot the device to an operating system ISO image, you can select both the Deploy Template and Boot to Network ISO options. Separate tasks are created for each operation. c. Click Next. 4. On the Select Template page: a. Based on the target device type, click Server Template or Chassis Template. b.
l. Type the values for the tagged VLANs and untagged VLAN. m. Click Save. n. Click Next. 7. On the Execution Credentials page: a. On the Credentials section, click Add New Credentials. NOTE: For server configuration deployment — provide the iDRAC Administrator credentials; For chassis configuration deployment — provide the CMC Administrator credentials. The Add Credentials window is displayed. Type the description, Administrator user name, and password required to run the task on the target devices.
NOTE: For server configuration deployment — provide the iDRAC Administrator credentials; For chassis configuration deployment — provide the CMC Administrator credentials. a. In the Add Credentials window, type the description, user name, and password. b. If you want to set the credentials as the default credentials for all target devices, select Default, and then click Finish. The credentials that you added are displayed in the Credentials section. 4.
Importing Device Specific Attributes You can also import the device specific attributes for deployment, if you already have a .csv file that includes the attributes. Before you begin, make sure that the .csv file that you want to import meets the requirements specified in Import File Requirements. To import the attributes: 1. On the Edit Attributes page of the Deployment Template Wizard or Setup Auto Deployment wizard, click Import/Export. The Import/Export Device Specific Attributes window is displayed.
NOTE: If you want to export the device specific attributes for only a specific device, select the device in the Edit Attributes page. 1. On the Edit Attributes page of the Deployment Template Wizard or Setup Auto Deployment wizard, click Import/Export. The Import/Export Device Specific Attributes window is displayed. 2. Click either Export Selected Device or Export All Devices based on your preference. If you selected Export All Devices, a confirmation dialog box is displayed. 3. Click Yes. 4.
3. Create Virtual I/O Pool — Use the Create Virtual I/O Pool task in the Common Tasks pane to create a pool of one or more virtual I/O identity types. The virtual I/O identity pool is used to assign virtual I/O identities to the target devices. 4. Create Compute Pool — Use the Create Compute Pool task in the Common Tasks pane to create a group of servers that you want to use for a specific purpose. You can associate a device configuration template and virtual I/O pool to the compute pool. 5.
4. On the Ethernet Identities page, perform one of the following: NOTE: If you do not want to include MAC addresses in the virtual I/O pool, clear the Include MAC addresses in this pool option, and then click Next. a. To specify the start address and the number of identities, perform the following: 1. In the Specify the start address box, type the start address that you want to predefine in the MAC addresses that will be generated.
NOTE: You can import up to 1000 identities using a .csv file. The .csv file must have a column titled Name or Value. 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 24. Sample .csv file with WWNN identities 6.
NOTE: The typical iSCSI IQN format is: iqn.date.domainname-in-reverse:storage-identifier. For example, iqn. 2001-04.com.example:storage.disk2.sys1.xyz. NOTE: The iSCSI IQN identifier string can include the following special characters: hyphen, comma, colon, and period. b. If you want to import the iSCSI IQN identities from a .csv file, click Import from file and perform the following: NOTE: You can import up to 1000 identities using a .csv file. The .csv file must have a column titled Name or Value. 1.
3. Click Next to view the various I/O identity definitions of the virtual I/O pool. Related links Virtual Input-Output Pools Create Virtual Input-Output Pool Wizard 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.
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 by 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 – MX Chassis Templates ◦ Sample - MX7000 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 Virtual I/O pool. Compute pool. A locked resource. Read-only but deployable device configuration template.
Related links Removing devices from the repurpose and bare-metal devices group Adding devices to repurpose and bare-metal devices group 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 66. Auto Deployment Field Description Service tag or Node ID Displays the unique identifier assigned to the system.
Field Description Created By Displays the name of the user who created the task. 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 68.
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 an attribute. Section Displays the component that the attribute belongs to. For example, iDRAC, BIOS, NIC, and so on.
Field Description Tagged VLAN(s) Field to enter the tagged VLANs values. Untagged VLAN Field to enter the untagged VLAN value. 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.
Network Types Table 73. Network Types Network types Description Bronze General Purpose Used for low priority data traffic.
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. The fields displayed on the various pages of the wizard are described in the following sections.
Field Description 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. WWNN identities are required for Fibre Channel (FC) and Fibre Channel over Ethernet (FCoE) communications.
Field Description Import from file Select to import WWPN identities from a .csv file. Import Click to open the wizard used to import WWPN identities from a .csv file. NOTE: The .csv must include only one address or identity per line. View Click to view the WWPN identities in the virtual I/O pool. NOTE: You can only view WWPN identities that you have already imported from a .csv file.
Table 80. 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. Number of FCOE WWNN Identities Displays the virtual I/O pool size of the WWNN identities. FCoE WWPN Definition Displays the WWPN identity definition.
Summary Table 82. 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 links 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 86. 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 88. 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 94. 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 96. 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 99. Select Template Field Description Server Templates Displays the server configuration templates that you have either created or cloned. Chassis Templates 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 Templates option is disabled.
Field Description Share IP Provide the IP address of the network share where the ISO file is available. Share Name Provide the name of the network share where the ISO file is available. Share Credentials Share Username Provide the user name required to access the network share. Share Password Provide the password required to access the network share.
Field Description Device Specific Attributes for Displays the following: • For a deployment task — The device name, Service Tag, and device model. • 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.
Field Description Fabric Displays the fabric associated with a specific slot of the chassis. The fabric is identified by a combination of the group name (A, B, or C) and slot number (1 or 2). 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.
Field Description Save Click to save the changes to the configuration template. Import/Export Displays the Import/Export Device Specific Attributes window. Import/Export Device Specific Attributes The fields displayed on the Import/Export Device Specific Attributes window are described in the following table. Table 105. 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.
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.
Table 108. Options Field Description Perform pre-check only Select Perform pre-check only to only verify (not deploy) if the device configuration template will be deployed successfully. 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.
changes are made). Each device verifies the validity of the settings in the configuration and identifies any problems. The verification can identify problems with attribute values themselves, or problems based on inter-attribute dependencies. For example, creating a device configuration template from a PowerEdge R720 server and deploying the template on a PowerEdge R620 server would result in errors. Running the preview allows you to identify the attributes that will not be deployed successfully.
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 117.
Import/Export Device Specific Attributes The fields displayed on the Import/Export Device Specific Attributes window are described in the following table. Table 118. 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 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.
Table 124. 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 126. 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 128. 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 130. 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 137. 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 device 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 links 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.
d. On the Devices section, set the Execution Credentials for each target device. e. Click Next. 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.
6. Under Execution Credentials, provide the device credentials that have the Administrator rights, and click Finish. 7. Click Ok in the task submission message. NOTE: The destructive and password attributes information is not displayed while configuring a baseline. Only the non-destructive attribute information of the baseline is displayed.
Remediating noncompliant devices The devices which are not conforming to the associated baselines can be remediated to make them conform to the baseline configurations. NOTE: The destructive and password attributes of the devices are not considered for compliance. As a result, these attributes are not considered for the remediation task. NOTE: The user configuration attributes are successfully remediated only if the same user exists on the target devices.
Related link Tasks Viewing server backup profiles The server backup profile is created by scheduling a device configuration inventory. The device should be a part of the Repurpose and Bare Metal Devices group and should not be a part of the virtual I/O compute pool. The backed-up profiles of the servers are visible under Configuration Backup → Backed-up Devices. Selecting one of the backedup profiles under the Devices section, displays the attributes of the profile under the Attributes section.
view the task execution details. The virtual identities reclaimed from the source devices are listed in the Details 1 tab. The Details 2 tab lists the attributes that are deployed on the target servers. NOTE: If Remove target from bare metal pool option is selected, then the target server is removed from the Repurpose and Bare Metal Devices group. NOTE: The target server is rediscovered, and the inventory details are updated for the target server.
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 links 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 142. 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 links Select Baseline Select Devices Associating target devices with a baseline Select Baseline The Select Baseline page enables you to select the baseline you want to associate to target devices.
Field Description Model Displays the model name of the system. For example, PowerEdge R710. 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.
Summary Table 149. 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 that are 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 152.
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 links 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 D
• 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 161. 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 166.
Field Description Vendor Displays the name of the NIC supplier. NIC Description Displays information on the NIC device. PCI Device Information Table 168. 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 170. 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 links 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 172.
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 175. 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 179. 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 links ESX Information HyperV Information ESX Information Table 181. 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 185. 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.
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. The All Internal Alerts filter is a reference to the internal alerts that OpenManage Essentials generates when a change occurs in the global health or connection status of a managed device.
Viewing alert ignore action 1. Select Manage → Alerts → Alert Actions. 2. In Alert Actions, select Ignore. Viewing alert trap forward action 1. Select Manage → Alerts → Alert Actions. 2. In Alert Actions, select Trap Forwarding. Handling alerts Flagging an alert After you have completed action on an alert, flag the alert as acknowledged. Acknowledging an alert indicates it is resolved or does not require further action as a reminder to yourself. To acknowledge alerts: 1.
To configure an email notification when alerts are received: 1. Select Manage → Alerts → Common Tasks → New Alert Email Action. 2. In Name and Description, provide email alert action name and description and then click Next. 3. In E-mail Configuration, do the following and then click Next. a. Provide email information for the To: and From: recipients and provide the substitution information. Separate each recipient or distribution list with a semi-colon. b.
3. In Categories and Sources Association, assign the alert categories source to which you want to associate this alert ignore action and then click Next. 4. In Device Association, assign the device or device groups to which you want to associate this alert ignore action and then click Next. 5. By default the Ignore Alert is always active. To limit activity, in Date Time Association, enter a date range, time range, or days, and then click Next. 6.
6. In Device Association, assign the device or device groups to which you want to associate this trap forwarding alert and then click Next. 7. By default the Trap Forward Action is always active. To limit activity, in Date Time Association, enter a date range, time range, or days, and then click Next. 8. In Summary, review inputs and click Finish.
• Sample - Email Alerts to Service Desk—Enable this use case to send an e-mail to the service desk account from the OpenManage Essentials server when an alert criteria is matched. • Sample - Email Critical Server Alerts to Admin—Enable this use case to send an e-mail to an administrator from the OpenManage Essentials server when an alert criteria is matched. Ignore • Sample - Ignore Alerts During Maintenance Window—Enable this use case to ignore alerts during a specified time interval.
If more than one alert is received, the following information is displayed: • • Alert type and frequency. Name of each device as a link to navigate to the device in the device tree. NOTE: The device link is displayed only for the first three alerts. • • • View Alerts — To view the All Recent Warning and Critical Alerts window. Go to Alert Console — To navigate to the Alerts portal. Disable — To disable alert pop-up notifications. By default, the alert pop-up notification is enabled.
define and manage traps. Using the imported and manually-managed trap definitions, OpenManage Essentials properly classifies the incoming trap from a specific device. NOTE: Importing traps portal is optional and only needed for formatting alerts from non-Dell devices. About importing MIBs Use case scenario: As an administrator you want to monitor (listen and classify incoming traps) a device that is not supported by OpenManage Essentials. Solution: Verify whether the device supports SNMP protocol.
Importing MIBs Before you begin, ensure that you are logged in with OmeAdministrator privileges. 1. Click Manage → Alerts → Manage MIBs. 2. In Manage MIBs, click Import MIB. 3. In Select files for upload, click Browse. a. 4. Select the MIB files that you want to import. b. Click Open. From the Select a MIB File list, select a MIB file and then click Parse MIB. The trap data appears in a grid format. 5. Click Import Traps to import traps into the OpenManage Essentials database.
Deleting traps The Custom Trap Definitions view also enables you to delete user-defined traps. Traps that are pre-defined in OpenManage Essentials cannot be deleted. Before you begin, ensure that you are logged in with OmeAdministrator privileges. To delete traps: 1. Click Manage → Alerts → Manage Traps. 2. In Manage Traps, click Custom Trap Definitions. 3. In the User Defined Traps grid, select the traps you want to delete. The selected traps are highlighted 4. Click Delete Trap.
• Agent IP Address • Engine ID • Username c. Select the Authentication Protocol from the list. NOTE: SHA1 is the authentication protocol selected by default. d. Enter the Authentication Password. e. Select the Encryption Protocol from the list. NOTE: AES is the encryption protocol selected by default. NOTE: If the Authentication Protocol is set to None, then the authentication and encryption options are disabled. f. Click OK.
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 Fo
Related links Configuring alert log settings Configuring alert actions Setting up email notifications 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 190. 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 192. 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 195. 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 202. 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 Servers Select to include Dell servers. Storage Devices Select to include storage devices. Unknown Select to include unknown devices. VMware ESX Servers Select to include VMware ESX servers. VxFlex Ready Nodes Select to include VxFlex Ready Nodes and ScaleIO Ready Nodes. Date and Time Range Table 205. 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.
Table 207. Summary — Alert Action Details Field Description Name The name of the alert action. Action Enabled Specifies if the alert action is enabled or disabled. 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.
Field Description Advanced Infrastructure Management Select this category to include alerts for Advanced Infrastructure Management. Environmental Select this category to include alerts for temperature, fan enclosure, fan speed, thermal, and cooling. 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.
Edit Trap Definitions Table 209. Edit Trap Definitions Field Description Trap Name or Enterprise OID Field to provide the trap name or enterprise OID of the trap you want to edit. Search Click to search the OpenManage Essentials database for the trap name or enterprise OID that you provided. Event Category Click to display the event categories defined in the OpenManage Essentials database. You can select a category to display all the traps defined for that category in the Edit Trap(s) grid.
Field Description the message string. For SNMP, the valid formatting commands are: $n = system name $d = date $t = time $s = severity $e = enterprise object identifier (OID) $sp = specific trap OID $g = generic trap OID $1 - $# = varbind values 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.
Field Description Category Name Select to display the event category names defined in OpenManage Essentials and the category name of the parsed MIB. Severity Select to display the severity defined in OpenManage Essentials. Apply the selected event category to all traps Select to change the category name of all the traps. NOTE: If you do not select the check box, you have to manually select the traps and select the category name from the drop-down list.
Table 212. Severity Configuration by Value Field Description Trap Variable Displays the trap variable index. Severity Displays the severity assigned for each object value or object ID. Object ID Displays the numerical value based on the trap variable index. Object Value Displays the string value based on the trap variable index. Add New Click to add the severity configuration. Select the Variable Select the trap variable that you want to update. OK Click to save the changes.
Manage Traps Custom Trap Definitions Table 214. Custom Trap Definitions Field Description Add Trap Category Name To select the event category names defined in OpenManage Essentials or to provide a new category name. Unknown Traps Click to display the unknown traps received in OpenManage Essentials. Description To provide the trap description. Trap Name To provide or edit the trap name.
Field 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. Delete Trap Click to delete the selected traps. Reset Built-in Trap Definitions Table 215. Reset Built-in Trap Definitions Field Description Edited Traps Name Displays the trap name. Category Name Displays the category name of the trap.
18 Updating BIOS, firmware, drivers, and system 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 sources of system updates • Online source—Default option which downloads latest driver and firmware versions from downloads.dell.com. This is also a default option for updating MX Chassis devices.
Viewing comparison results This section provides information required to view the results of the comparison of devices to a source catalog. Viewing compliant systems 1. Click Manage → System Update. 2. To view the compliant systems, click Compliant Systems. For a MX7000 chassis, compliance details of the lead chassis, member chassis, and compute sleds are listed individually. Viewing noncompliant systems 1. Click Manage → System Update. 2.
Table 216. View Default Catalog Field Description Source Displays the source. The source is either Server Update Utility, downloads.dell.com, or Repository Manager. Source Type The type for source from which the catalog file is taken. For example, downloads.dell.com. 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.
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 WS-Man Out-of-Band (iDRAC) iDRAC BIOS, firmware, and applications are updated using iDRAC. NOTE: When an iDRAC IP is discovered using WS-Man, the iDRAC software inventory is retrieved and the components are updated using iDRAC.
Applying system updates by using the Non-Compliant Systems tab NOTE: The following are some of the considerations when applying system updates: • You can only update systems using iDRAC6 or later if they are discovered using the WS-Man protocol. • If the iDRAC firmware version is 1.40.40 or earlier, applying system updates out-of-band (iDRAC) is supported only for 32bit Dell Update Packages (DUPs).
Using the Out-of-band Reboot Type option, you can set the types of reboot methods available for the system update. The reboot methods are: • Power Cycle (Cold)—Select this option to power off and then restart the system. • 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.
NOTE: The following are some of the considerations when applying system updates: • You can only update systems using iDRAC6 or later if they are discovered using the WS-Man protocol. • If the iDRAC firmware version is 1.40.40 or earlier, applying system updates out-of-band (iDRAC) is supported only for 32bit Dell Update Packages (DUPs).
• 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. c. If you want to skip the signature and hash check on the system update package, select Skip Signature and Hash Check. d.
Updating systems without OpenManage Server Administrator To update the firmware, BIOS, and drivers on a system that does not have OpenManage Server Administrator (OMSA) installed: 1. Collect the software inventory from the server. See Collecting Firmware and Driver Inventory. 2. Update the system through the system update portal. See Applying System Updates Using the Non-Compliant Systems Tab or Applying System Updates Using the System Update Task Wizard.
19 System Update — Reference You can access the following: • System Update Portal Action – View System Update Portal ◦ • 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 Action – Select a Catalog Source – View Default Catalog – View MX Chassis Default Catalog • Update Action – Create System Update Task • Catalog Baselin
Filter Options Table 219. Filter Options Filter Option Description Is equal to Select to create the same as logic. Is not equal to Select to create the different from logic. Starts with Select to filter search based on a text chunk’s initial alphanumeric characters. Provide the starting alphanumeric characters in the field. Ends with Select to filter search based on a text chunk’s final alphanumeric characters. Provide the ending alphanumeric characters in the field.
Compliance Report Options Table 220. Compliance Report Options Field Description Default Catalog Source Report source MX Chassis Default Catalog Source Report source for MX7000 chassis—lead chassis, member chassis, compute sleds, and storage Get the latest This option is disabled if the catalog version is the latest. Else, it is active. Click this option to get the latest catalog version.
Field Description NOTE: By default, the Graceful Reboot with forced shutdown reboot method is selected. Systems information — bar chart format The bar chart lists the following systems: • • Compliant Systems Non-Compliant Systems NOTE: Non-Inventoried Systems and Issues and Resolutions links are provided below the bar chart. Click these links to navigate to the respective tabs. Systems information — pie chart format The pie chart lists the systems status compared with the existing catalog file.
Table 222. Non-Compliant Firmware & Drivers Field Description System Name Domain name of the system. Group Name Displays the name of device groups. Baseline Name Displays the name of catalog baseline associated with a device group. Model Type The systems model name. For example, PowerEdge. Operating System The operating system that is installed on the system. Service Tag A unique identifier, that provides the service lifecycle information.
Field Description Component The software information. Type The type of software update. 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. Reboot required Indicates if the system must be rebooted after the update. Set the Task Schedule Run Now Select this option if you want to run the task when you click Finish.
Field Description SSH Port Number Provide the SSH port number. Server User name Provide the server user name for the selected target. Server Password Provide the server password for the selected target. iDRAC User name Provide the iDRAC user name for the selected target. iDRAC Password Provide the iDRAC password for the selected target. Non-Inventoried Systems The Non-Inventoried Systems tab provides a list of systems that require inventory.
Field Description Recommendation Displays the resolution to resolve the issue. Related links Updating BIOS, firmware, drivers, and system applications Viewing the System Update page System Update — Reference Task Execution History Lists the details of the system update tasks or remote tasks. Table 228. Task Execution History Field Description Status Displays an icon representing the task status: — Running or pending — Completed — Stopped — Failed — Warning Task Name The name of the task.
Table 229. Select a Catalog Source Field Description Default Catalog Use file system source (SUU) Select to update software using Server Update Utility. Click Browse to traverse to the file location. The catalog.cab file is located in the repository folder. Use repository manager file Select to update software by using Repository Manager file. Click Browse to traverse to file location. The catalog.cab file is located in the repository folder.
Field Description Newer version available Displays if a newer version is available. View MX Chassis Default Catalog Select to view the catalog file that is currently in use for applying firmware and driver updates to the MX7000 chassis including the lead chassis, member chassis, compute sleds, and storage. Table 231. View MX Chassis Default Catalog Field Description Source Displays the source. The source is Online for MX7000 chassis.
Baseline Details Table 235. Baseline Details Field Description Baseline Name Name of the catalog baseline. File Path File system location of the catalog. Source Type The type for source from which the catalog file is taken. For example, Custom Catalog. Release ID The unique identification number assigned to the released catalog file. Release Date The date on which the catalog file was released.
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—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 enter 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 enter 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. 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 turn on servers.
NOTE: Install Server Administrator prerequisites before deploying Server Administrator on Linux. NOTE: If there are both 32-bit and 64-bit versions of OpenSSL libraries installed on a RHEL system, it is recommended to uninstall the 32-bit version. Also, if there is a symbolic link to libcrypto.so.6, created by OpenManage Essentials, remove the symbolic link, and then redeploy OpenManage Server Administrator. 3.
Linux Packages Table 237. Linux Packages Operating System Package SUSE Linux Enterprise Server 10 OM-SrvAdmin-Dell-Web-LX-6.5.0-2247.SLES10.x86_64_A01.6.tar.gz SUSE Linux Enterprise Server 11 OM-SrvAdmin-Dell-Web-LX-6.5.0-2247.SLES11.i386_A01.14.tar.gz 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.SLES10.x86_64_A01.6.tar.gz.sign OM-SrvAdmin-Dell-Web-LX-6.5.0-2247.SLES11.i386_A01.14.tar.gz.sign OM-SrvAdmin-Dell-Web-LX-6.5.0-2247.ESX41.
To create an iDRAC Service Module deployment task: 1. Click Manage → Remote Tasks → Common Tasks → Create Deployment Task. 2. On General, select iDRAC Service Module and provide a task name. If you want to deploy the iDRAC Service Module on Windows-based servers, then select Windows, provide installer path and, if required, provide arguments. If you want to deploy the iDRAC Service Module on Linux-based servers, select Linux and provide the installer path, select Generate Trusted Key and Allow reboot.
Linux Packages Table 240. Linux Packages Operating System • Red Hat Enterprise Linux 5 • Red Hat Enterprise Linux 6 • Red Hat Enterprise Linux 7 • SUSE Linux Enterprise Server 11 • Community Enterprise Operating System (CentOS) 5.9 • CentOS 6.5 Package OM-iSM-Dell-Web-LX-100-429.tar.gz OM-iSM-Dell-Web-LX-100-429.tar.gz.sign Systems-Management_Application_NH7WW_LN64_1.0.0_A01 Systems-Management_Application_NH7WW_LN64_1.0.0_A01.BIN SUSE Linux Enterprise Server 11 dcism-1.0.0-4.435.1.sles11.
d. If you selected Show OMSA based targets, perform one of the following in the Future Software Inventory Data Collected by section: NOTE: The Future Software Inventory Data Collected by options only determine the method OpenManage Essentials utilizes to gather firmware and driver inventory information from target devices after an in-band system update.
3. Right-click the cloned task and select Edit. 4. Enter the required information and assign targets to the tasks. For information about the options, see Remote Tasks Reference. Related links Remote Tasks Remote Tasks — Reference Remote Tasks Home Command Line Task All Tasks Device Capability Matrix 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.
The Sample - Server XML Configuration command line task allows you to apply a specific server configuration to multiple managed nodes. Using Lifecycle Controller 2 version 1.2 or later, a server configuration summary can be exported from an iDRAC in XML format through the “Export Server Configuration” operation. NOTE: For information on exporting the server configuration summary using Lifecycle Controller 2, see the Configuration XML Workflows white paper at DellTechCenter.com/LC.
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 discovered using IPMI DRAC/iDRAC is not discovered Create F/W & Driver Inventory task Not supported Supported Supported DRAC/iDRAC discovered using SNMP/WS-Man Server operating system is not discovered Not supported Not supported The follow
Table 243.
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 links Managing command line tasks Managing RACADM command line tasks Managing server power options Deploying OpenManage 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 • Comma
Related links Managing command line tasks Managing RACADM command line tasks Managing server power options Deploying OpenManage 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 245.
Table 246. 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 links Deploying OpenManage Server Administrator Device Capability Matrix Command Line Task Select this option to create command line tasks. Table 248. 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 links Command Line Task Managing command line tasks Using the Sample - Server XML Configuration Command Line Task Generic Command Table 250. 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\reci
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 253. 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 in OpenManage Essentials Supported protocols and ports on management stations Table 254. Supported protocols and ports on management stations Port number Protocol Port type Maximum encryption level Direction Usage 21 FTP TCP None In/Out Access downloads.dell.
Port number Protocol Port type Maximum encryption level Direction Usage 443 Proprietary/ WSMAN TCP None In/Out EMC storage, iDRAC6, iDRAC7, and iDRAC8 discovery and inventory. 2463 Proprietary TCP None From OpenManage Essentials to the managed node Discovery and inventory of PowerVault MD storage array 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.
Port Number Protocol Port Type Maximum Direction Encryption Level Usage systems Performance monitoring in Linux systems. 80 HTTP TCP None In/Out Contextual application launch — Networking console. 135 RPC TCP None In/Out Event reception through CIM from Server Administrator — for systems supporting Windows operating systems.
Figure 35.
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.
3. Ensure that the SNMP Trap service services are running in the Open Manage Essentials system. 4. Check firewall settings to allow UDP 161, 162 ports. 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.
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 https://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 259. 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 261. 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 353
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.
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. NOTE: To restrict the user to perform system updates and remote tasks on specific device groups, you must assign the device groups to the user. See Assigning Device Groups to a User.
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 264.
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 266. 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.
Device Tree Settings Table 268. Device Tree Settings Field Description Always display RAC device name under RAC group Select the check box to display the RAC name (RAC DNS name or instrumentation name) of the iDRAC in the device tree, portals, and wizards. 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.
Field Description NOTE: The device range that was discovered in OpenManage Essentials version 2.2 and earlier may have discovered both chassis and iDRAC using WS-MAN protocol. In OpenManage Essentials 2.5, if Discover the selected Device Types only option is enabled in Discovery settings, then only the specific device selected in the guided wizard will be discovered and other devices are classified as unknown devices.
General Settings Table 271. General Settings Field Description Console Session Timeout Amount of user-inactive time that passes before the console automatically logs the user out. Database Maintenance Execution Schedule The date and time when the database maintenance activity will begin. NOTE: It is recommended not to run or schedule any task (discovery, inventory, status polling, and so on) during database maintenance, as the console is less responsive during database maintenance.
Field Description Password User's proxy password. Proxy Port Number The port number to access the proxy server. Check the browser's proxy LAN settings, or ask your network administrator if unsure. Test Connection Click to test connection to the internet with the proxy credentials. KACE Appliance Settings KACE Appliance URL The URL of the KACE appliance. Test URL Click to test connectivity to the KACE appliance. Task Settings Table 272.
Field Description All Devices with x days or less of warranty Determines which devices to include in the warranty notification email. Devices with warranty less than or equal to the specified days are included in the warranty notification email. Include Expired Warranties Specifies if devices with expired warranty (0 days) or no warranty information should be included in the warranty email notification. Send email every x days The duration between successive warranty email notifications.
Related links Configuring Warranty Email Notifications Configuring Warranty Scoreboard Notifications Permissions The following is the description of the panels and fields displayed in the Device Group Permissions portal. Common Tasks The Common Tasks pane displays the Edit Members of OmeSiteAdministrators option that you can use to add or remove a user from the OmeSiteAdministrators role.
Field Description downloads folder (\Essentials\System Update) when the folder size reaches the defined size limit. (Range: 5 GB to 20 GB; Default: 20 GB) Approximate size of the downloaded files to be purged Select the approximate size of the downloaded files that you want to purge. Files will be purged until the total size of the purged files reaches or exceeds the approximate size that you have defined.
28 Logs — Reference From tools you can: • View User Interface Logs • View Application Logs Figure 36. Toolbar — Export Export Discovery Logs to File System — Export the logs that were generated while discovering devices. User Interface Logs Table 276. 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.
29 Dell EMC Solutions The Dell EMC 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 enables 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 278. Dell EMC Solutions Field Description Name Displays the name 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 279.
Action Description 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. Associate to Template — Associate the device to a device configuration template. Create Template — Create a device configuration template from the device. Deploy Template — Deploy a device configuration template on the device.
Discovery Range Summary Managing Include Ranges Right-click the IP address or group to view the following options: Table 283. Managing Include Ranges Action Description Edit Select to edit discovery range configuration. Rename Select to rename the range. 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.
Action Description Device Application Launch Select to launch the console associated with the device. Acknowledge Select to set or clear alerts. Delete Select to delete alerts. Ignore Select to ignore alert filter action on the selected device or all devices. You can also use this option to ignore all alerts from the selected device. Export Select to export alert information in a CSV or HTML format. Remote Tasks Table 286. Remote Tasks Action Description Edit Select to edit the task.
Attributes Tab Table 289. Attributes Tab Action Description Check Select the selected attributes. Uncheck Clear the selected attributes. Export Export all the attributes displayed in the Attributes tab. . Templates Table 290. 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.
Action Description Replace Server Replace a server with another server from within the same compute pool. Devices Table 293. Devices Action Description Refresh Device Configuration Inventory Refresh the configuration inventory of the device. Remove Devices from Repurpose and Bare Metal Devices Group Remove devices that are currently in the Repurpose and Bare Metal device group. Create Template Create a device configuration template from the server.
Compliance by Template Table 296. Compliance by Template Action Description Associate Devices Deploy the selected device configuration template. Edit Displays the attributes of the selected device configuration template in the right pane for editing. 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. .
31 Tutorials You can use these tutorials to complete the setup options 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 an input file for Discovery Profile 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.
NOTE: If you discover iDRAC using WS-Man, and if you are using secure mode where a certificate file is required to be on the local system, specify the entire path to the certificate file. For example, c:\192.168.1.5.cer. Specifying IPs, ranges, or host names by using XML or CSV files You must specify ranges during discovery, inventory, and status tasks. A range in this instance is defined either as an individual IP address, a hostname, or a range of IPs such as 192.168.7.1-50 or 10.35.0.*.
Creating a discovery range Description: The Add-DiscoveryRange command allows you to create a new discovery range. The command references an .xml file (DiscoveryProfile.xml) which is a protocol definition associated with the discovery range. Enter the ranges either using an XML file, CSV file, or by specifying the range. For more information about DiscoveryProfile.xml, RangeList.xml, and RangeList.
and all the ranges it contains. You can maintain different sets of protocols for different types of devices in your network. With ranges not in a group, you have to edit each range individually to change the protocols which are active, the time out or retry values, or credentials used with each protocol. Each discovery range group can only have one corresponding subnet. The subnet for a group is read from the DiscoveryProfile.xml file and not from the Rangelist.xml or RangeList.csv file.
Commands: • PS> Set-EnableDiscoveryRange -Range • PS> Set-EnableDiscoveryRange -RangeList • PS> Set-EnableDiscoveryRangeGroup -GroupName Examples: • PS> Set-EnableDiscoveryRange -Range 10.35.1.3, 10.2.3.1 • PS> Set-EnableDiscoveryRange -RangeList .\Samples\RangeList.
• PS> Remove-DiscoveryExcludeRange -Range 10.35.12.1 • PS> Remove-DiscoveryExcludeRange -RangeList .\Samples\RangeList.xml Running discovery, inventory, and status polling tasks Description: The Set-RunDiscovery, Set-RunInventory, Set-RunDiscoveryInventory, and Set-RunStatusPoll commands allows you to perform discovery, inventory, and status polling on a discovery range, discovery range group, or devices. For range and range groups, enter the ranges either using an XML file or by specifying the range.
• PS> Get-DiscoveryStatus —Range • PS> Get-Discovery -RangeList • PS> Get-Discovery -GroupName Examples: • PS> Get-DiscoveryStatus —Range 10.35.2.1 • PS> Get-Discovery -RangeList .\Samples\RangeList.xml • PS> Get-Discovery -GroupName Group1 Stopping discovery range or group tasks Description: For any range, only one type of task, such as discovery, discovery and inventory, or status polling, can run at a given time.
• PS> Add-DevicesToCustomGroup –GroupName -DeviceList • PS> Add-DevicesToCustomGroup –GroupName -Devices Examples: PS> Add-DevicesToCustomGroup –GroupName MyServers –DeviceList .\Samples\DeviceList.xml or PS> Add-DevicesToCustomGroup –GroupName MyServers –Devices PE2900-WK28-ZMD, PWRCODE.US.DELL.COM, HYPERVISOR, M80504-W2K8 Example of a DeviceList.xml file: ManualShelf © 2013-2025
