Managing devices. Dell EMC OpenManage Essentials Version 2.5, EMC OpenManage Essentials
Add to My manuals387 Pages
Dell EMC OpenManage Essentials Version 2.5 is a comprehensive systems management solution that provides the ability to discover, monitor, and manage your Dell EMC infrastructure. OpenManage Essentials offers an intuitive user interface, flexible deployment options, and advanced monitoring capabilities that make it easy to manage your IT environment.
advertisement
86
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.
In the Devices page, you can:
• View devices types that are discovered on the network.
• View the inventory information for the devices.
• View all alerts that were generated for a device.
• View all noncompliant devices associated with a catalog baseline in a device group.
• View all noncompliant devices associated with a configuration baseline in a device group.
• View hardware logs for a device.
• Create device groups and include devices to that group based on your grouping preference. For example, you can create a group and include all devices present at a geographical location.
• Display and manage PowerEdge VRTX and FX2/FX2s devices using Map View .
Related links
Adding Devices to an Existing Group
Viewing devices
You can view a device that is discovered. For more information on discovering and inventorying a device, see
.
To view devices, click Manage → Devices .
Related link
Device Summary Page
On the Device Summary page, expand the device types to view the devices. The following device types are displayed:
• Citrix XenServers
• Clients
• Clusters
– HA Clusters
– NAS Clusters
• Hyper-Converged Infrastructure
– VxRail
– XC Series
• KVM
• Microsoft Virtualization Servers
– Virtual machines
• Modular systems
– 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. If both DRAC and iDRAC, and their corresponding server are discovered, they are correlated into a single device. This device is then displayed under both RAC and Servers groups.
• Network Devices
– Networking Switches
– Fibre Channel Switches
– Network Appliances
• OEM Devices
• OOB Unclassified Devices
– IPMI Unclassified Devices
• Power Devices
– PDU
– UPS
• PowerEdge C Servers
• Printers
• RAC
NOTE: If a DRAC or iDRAC is discovered, it is displayed under the RAC group and not under the Servers group. If both DRAC and iDRAC, and their corresponding server are discovered, they are correlated into a single device. The device is then displayed under both RAC and Servers group.
NOTE: If the RAC on a PowerEdge C server is discovered using IPMI, it is displayed under OOB Unclassified devices.
• Repurpose and Bare Metal
NOTE: Devices in the Repurpose and Bare Metal group are displayed as targets for device configuration deployment.
You must explicitly add devices to this group for deploying a device configuration. On bare metal deployments, you can remove the devices from the Repurpose and Bare Metal group after the deployment is complete. For more
information, see Server Deployment and Re-provisioning
.
• Servers
• Storage Devices
– Dell Compellent Arrays
– Dell EqualLogic Groups
– Dell NAS Appliances
87
– 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
.
Use the refresh button to update the device tree with the current data. To update the device tree, right-click All Devices and select
Refresh .
NOTE: The device tree auto-updates when changes are made. Some changes to the tree may appear after a brief delay depending on the performance of the managed servers because the information propagates from the SQL database to the user interface.
Nodes and symbols description
Table 35. Nodes and Symbols Description
Node Symbol
Figure 15. Critical device icon
Description
Denotes that a device is critical and requires attention. This information is rolled up to the parent device type. For example if a server is in critical state and requires attention the same symbol is assigned to the parent device type. Among server states, critical state is given the highest priority. That is, in a group, if different devices are in different states, and if one device is in critical state, then the state of the parent device type is set to critical.
Denotes that a device of this type is not discovered on the network or classified in the device tree.
Figure 16. Device not discovered icon
Denotes that there is a deviation from the expected behavior, but the device is still manageable.
Figure 17. Deviation from expected behavior icon
Denotes that the device is working as expected.
Figure 18. Device working as expected icon
Figure 19. Unknown device icon
Denotes either the device type is unknown and it is classified as an unknown device or that the health status cannot be determined, because the device does not have proper instrumentation or the proper protocol was not used to discover the device.
Denotes that the device is not reachable.
Figure 20. Connection Lost
Device details
The device details, depending on the device type, might contain the following information:
88
Table 36. Device details
Device details
• Device Summary
• OS Information
• Data Sources
• NIC Information
• Virtual Machine Host Product Information
• RAC Device Information
• Processor Information
• Memory Device Information
• Firmware Information
• Power Supply Information
• Embedded Device Information
• Device Card Information
• Controller Information
• Controller Battery Information
• Enclosure Slot Information
• Physical Disk Information
• Virtual Disk Information
• Contact Information
• Appliance Node Information
• Switch Device Information
• EqualLogic Volume Information
• Device Properties
• Storage Group Information
• iDRAC Information
• Storage Information
• Tape Drive Information and Tape Library Information
• Physical Battery Information
• Fluid Cache Information
• Fluid Cache Pool Information
• Fluid Cache Disk
• Software Inventory Information
• Trusted Platform Module Information
• Slot Information
• Virtual Flash Information
• FRU Information
• Printer Cover Table
• Printer Marker Supplies Information
• Printer Input Tray Information
• Printer Output Tray Information
• Acquisition Information
• Depreciation Information
• Lease Information
• Maintenance Information
• Service Contract Information
• Extended Warranty Information
• Ownership Information
• Outsource Information
• Maser Information
• Chassis Group Information
• I/O Module Information
NOTE: The warranty information (including expired and renewed) displayed in OpenManage Essentials for a particular
Service Tag, may not match with the warranty record displayed at Dell.com/support . The service level code and model name of a warranty record displayed at Dell.com/support may not exactly match with the OpenManage Essentials warranty report.
NOTE: The Data Sources table in the device inventory displays the Dell Command | Monitor (previously OMCI) agent name as System Administrator.
NOTE: Hardware inventory can be retrieved from iDRAC6/7 and ESXi if OpenManage Server Administrator VIB is installed using WS-Man protocol.
NOTE: The Data Sources table in the device inventory displays information about the iDRAC Service Module only if:
• iDRAC is discovered.
• iDRAC is discovered and the server is discovered using WMI or SSH protocol.
Viewing device inventory
To view inventory, click Manage → Devices , expand the device type and click the device.
Related link
89
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. If alert policies are configured individually, alerts of the member MX7000 chassis and compute sleds are not displayed in the alert summary. To view the alerts of the member
chassis, see Viewing alert logs
.
Related link
Viewing noncompliant devices associated with a catalog baseline
1.
Click Manage → Devices .
2.
To view all noncompliant devices associated with a catalog baseline, click All Devices .
All the noncompliant devices are listed in the Non-Compliant Firmware & Drivers tab.
3.
To view noncompliant devices of a custom device group, expand All Devices , and click the required device group.
On the Non-Compliant Firmware & Drivers tab, all noncompliant devices of the selected group are listed. The catalog baseline that is associated with the custom device group is also listed.
.
Viewing noncompliant devices associated with a configuration baseline
1.
Click Manage → Devices .
2.
To view all noncompliant devices, click All Devices .
All the noncompliant devices are listed in the Non-Compliant Configurations tab.
3.
To view noncompliant devices in a device group, expand All Devices , and click the required device group.
On the Non-Compliant Configurations tab, all noncompliant devices of the selected group are listed. The configuration baseline that is associated with the individual device is also listed.
To remediate the noncompliant devices, see Remediating noncompliant devices .
Viewing System Event Logs
1.
Click Manage → Devices .
2.
Expand the device type and select Hardware Logs .
Related link
Searching for Devices
Right-click All Devices at the top of the device tree and click Search Devices . You can also search for devices using logical arguments and save the queries for later.
90
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.
In the next line select the check box, then select AND, IP Address, Contains , and then in the adjacent field enter 10.35
.
5.
In the next line select the check box, then select AND, Power Status, Is , and then select Power Up .
6.
Click Save Query .
NOTE: You can click Run Query to run the query immediately.
To run an existing query, select the query from the drop-down list and click Run Query . You can filter the results and export it to an
HTML, TXT, or CSV file.
Related link
Creating a New Group
1.
Click Manage → Devices.
2.
Right-click All Devices and select New Group.
3.
Enter the name and description for the group and click Next.
4.
In Device Selection , select any of the following:
• Select a query to create a dynamic group. Click New to create a new query or select an existing query from the drop-down list.
NOTE: To create a query for VxFlex Ready nodes:
1.
Include ScaleIO as the device model.
2.
In the next line select the check box. then select OR , and then include VxFlex as the device model.
• Select the device(s) /group(s) from the tree below to create a static group.
5.
Click Next.
6.
Review the summary and click Finish.
You can right-click devices in the Details tab and add them either to a new group or an existing group. You can also create a new group from either the Home or Reports portal. Click Filter by and click Add New Group to launch the New Group wizard. To know whether a group is static or dynamic, place the cursor on the group. For example, if you place the cursor on Servers , the group type is displayed as Servers (Dynamic | System).
Related link
Adding Devices to a New Group
1.
Click Manage → Devices.
2.
Right-click the device(s) and select Add to New Group.
3.
In Group Configuration , enter the name and description. Click Next .
4.
In Device Selection, the selected devices are displayed. If required, add or remove additional devices. Click Next .
5.
Review the summary and click Finish .
Related link
91
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.
Related link
Hiding a Group
To hide a group, right-click the group and select Hide .
After a group is hidden, it is not displayed in any of the device group controls in the console. The devices in the hidden groups are not displayed in the reports and charts on the Home and Reports portals. Alerts for devices in hidden groups are also not displayed in the alerts portal.
If a parent group (along with child groups) is hidden, the child groups are also hidden in the device tree. However, the child groups are still present in the database and are displayed in other instances in the console.
Related link
Deleting a Group
1.
Right-click the group and select Delete .
2.
In the Delete screen, click Yes .
NOTE: Deleting a parent group, removes the group from the device tree. The child groups and devices listed under the parent group are also removed from the device tree. However, the child groups and devices still remain in the database and appear in other instances in the console.
Related link
Associating a catalog baseline to custom device groups
To associate a catalog baseline to VxFlex Ready Nodes, you must download the latest catalog and packages by right-clicking the discovered Ready Node and clicking Application Launch → VxFlex Ready Node Series Support .
1.
Click Manage → Devices .
2.
Right-click a custom device group and select Associate Catalog Baseline .
3.
In Associate Catalog Baseline , do one of the following:
• Select a catalog baseline from the list of catalog baselines.
• Create a catalog baseline by importing a repository manager file.
4.
Click Finish .
Custom device group is associated with the catalog baseline.
5.
Click Ok .
In the Non-Compliant Firmware & Drivers tab, all noncompliant devices of the selected group are listed.
.
92
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.
Single Sign-On
If iDRAC or CMC devices are configured for Single Sign-On and you are logged on to OpenManage Essentials as a domain user, you can use open the iDRAC or CMC console through the Application Launch option or the agent link. For information on configuring iDRAC or CMC for Single Sign-On, see the following:
• Configuring CMC For Single Sign-On Or Smart Card Login section in the Dell Chassis Management Controller User’s Guide at dell.com/support/manuals .
• Configuring iDRAC7 for Single Sign-On or Smart Card Login section in the Integrated Dell Remote Access Controller 7 User's
Guide at dell.com/support/manuals .
• Integrating iDRAC7 With Microsoft Active Directory white paper at DellTechCenter.com
.
• IDRAC6 Integrated Dell Remote Access Controller 6 Security white paper at DellTechCenter.com
.
Creating a Custom URL
NOTE: Custom URL cannot be assigned to parent device groups that create a child sub group in the device tree at the time of discovery. Examples of parent device groups are: HA Clusters, Microsoft Virtualization Servers, PowerEdge
M1000e, PowerEdge VRTX, or VMware ESX Servers. To assign a custom URL to a device in these parent device groups, add the device to a custom device group, and then assign a custom URL.
1.
Click Settings → Custom URL Settings .
2.
Click the icon.
The Custom URL Launch screen is displayed.
3.
Type the name, URL, description, and select the device group from the drop-down list.
NOTE: You can click Test URL to verify if the URL specified is active.
4.
Click Ok .
The custom URL is created.
Related links
Launching the Custom URL
1.
Click Manage → Devices and select the device from the tree.
2.
Right-click the device and select Application Launch .
3.
Click the URL name to access the site.
Related link
93
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.
In the To field, type the email addresses of the recipients.
NOTE: Multiple email addresses must be separated by using a semicolon.
4.
In the From field, type the email address from which the warranty notification email is to be sent.
NOTE: Only one email address must be provided in the From field.
5.
To set the criteria for the devices to be included in the warranty notification email, in the All Devices with x Days or less of warranty field, select the number of days.
6.
To set the frequency at which you want to receive the warranty notification email, in the Send email every x Days field, select the number of days.
7.
To include devices with expired warranty or no warranty information in the warranty notification email, select Include Expired
Warranties .
8.
In the Next Email will Send On field, select the date and time at which you want to receive the next warranty notification email.
9.
If you want to configure the SMTP email server, click Email Settings .
The Email Settings page is displayed. For more information about Email Settings , see
10.
Click Apply .
OpenManage Essentials sends warranty notification emails based on your configuration. The warranty notification email provides a list of devices and appropriate links that you can click to renew the warranty of the devices.
Related link
Warranty Notification Settings
Configuring Warranty Scoreboard Notifications
You can configure OpenManage Essentials to display a warranty scoreboard notification icon in the heading banner. For information about the options you can configure, see
Warranty Notification Settings
.
To configure Warranty Scoreboard Notifications :
1.
Click Settings → Warranty Notification Settings .
The Warranty Notification Settings page is displayed.
2.
Under Warranty Scoreboard Notifications , select Enable Warranty Scoreboard Notifications .
3.
To set the criteria for the devices to be included in the warranty notification scoreboard, in the All Devices with x Days or less of warranty field, select the number of days.
4.
To include devices with expired warranty or no warranty information in the warranty notifications scoreboard, select Include
Expired Warranties .
5.
Click Apply .
If any device meets the set criteria, the OpenManage Essentials heading banner displays the warranty scoreboard notification icon including the number of devices.
Related links
Using the Warranty Scoreboard Notification Icon
Warranty Notification Settings
94
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.
In Warranty Popup Notification Settings :
• Select the Enable Warranty Popup Notifications option to enable warranty pop-up notifications.
• Clear the Enable Warranty Popup Notifications option to disable warranty pop-up notifications.
3.
Click Apply .
Configuring Warranty Update Settings
You can configure OpenManage Essentials to check the warranty information of the discovered devices on the support site. For information about the options you can configure, see
Warranty Notification Settings
To configure warranty update settings:
1.
Click Settings → Warranty Notification Settings .
The Warranty Notification Settings page is displayed.
2.
Under Warranty Update Settings , select Enable Warranty Updates .
3.
In the Update warranty every field, select the number of days to set the frequency at which the warranty updates are checked.
4.
In the Next warranty update will be on field, select the date and time at which you want to check the next warranty updates.
5.
Click Apply .
NOTE: By default, the Warranty Update Settings is disabled. You can view the warranty information in the Device
Warranty Report.
Using Map View
NOTE: For information about using the features available in Map View, see Map View (Home) Portal .
NOTE: The map displayed in Map View should be considered
as is
from the map service provider. OpenManage Essentials does not have any control over the accuracy of the map or address information.
NOTE: An Internet connection is required to perform some of the map functions such as zoom, address search, and so on. If you are not connected to the Internet, the following message is displayed on the map: Warning — Unable to connect to the Internet!
.
NOTE: A valid map provider (MapQuest or Bing) key is required for the Map View functionality. To enter the map provider key, see
.
The Map View feature allows the display and management of PowerEdge VRTX and PowerEdge FX2/FX2s devices with an
Enterprise license on an interactive geographic map. PowerEdge VRTX and PowerEdge FX2/FX2s devices with an Enterprise license are represented as pins on the map. The health and connectivity status can be viewed for all PowerEdge VRTX and
PowerEdge FX2/FX2s devices with an Enterprise license at a glance.
You can access Map View from the Home Portal or Manage → Devices portal page.
The Overlays menu at the top-right of the map allows you to overlay the health and connectivity status of the device on the pin.
The Actions menu at the top-right of the map allows you to perform various functions on the map. The following is the list of available actions:
95
Table 37. Using Map View
Action
Show All Map Locations
Go to Home View
Save Current View as Home View
Add Licensed Device
Import Licensed Devices
Remove All Map Locations
Export
Settings
Edit Location Details
Description
Displays all map locations.
Displays the home view, if saved earlier.
Saves the current view as the home view.
Allows adding PowerEdge VRTX and PowerEdge FX2/FX2s devices with an Enterprise license.
Allows importing PowerEdge VRTX and PowerEdge FX2/FX2s devices with an Enterprise license.
Allows removing all map locations.
Allows exporting all map locations to a .csv file.
Opens the Map Settings dialog box.
Opens the Edit Location Details dialog box, that displays the device name, address, and contact information.
Allows removal of the selected device from the map.
Allows zooming to the street level on the currently selected device location.
Remove Location
Zoom to Street Level
NOTE: This option is displayed only when a device is selected on the map.
NOTE: The Edit Location Details, Remove Location, and Zoom to Street Level options in the Actions menu are devicespecific. These options must be used after selecting a device on the map.
The Search for address box at the top-left of the map allows you to search for addresses.
The navigation toolbar displayed at the bottom of the map enables you to:
• Zoom in and out of the map
• Move the map up, down, right, or left
• Select the map provider type
Figure 21. Navigation Toolbar
The zoom level of the map can be identified by the scale that is displayed at the bottom-right of the map.
96
Related links
Map View Interface—Home Portal
General Navigation and Zooming
Map View Interface—Devices Tab
Selecting a Device on Map View
Multiple Devices at the Same Location
Moving a Device Location Using the Edit Location Details Option
Adding a Device Using the Search Pin
Moving a Device Location Using the Search Pin
Exporting All Device Locations
Map Providers
You can select between MapQuest and Bing map providers using the icon in the navigation toolbar. By default, the map is displayed using the MapQuest provider. The following table provides information about the supported map providers.
Table 38. Map Providers
MapQuest Bing
Requires a valid MapQuest key (license) that must be purchased based on the number of transactions per month. To view the available transaction plans, go to developer.mapquest.com/ plans/ .
After getting a valid MapQuest key, you must provide the key in the Map Settings dialog box.
Requires a valid Bing maps key that must be purchased. To get a valid Bing maps key, go to microsoft.com/maps/ .
NOTE: For instructions on getting a Bing maps key, see
“Getting a Bing Maps Key” at microsoft.com.
After getting a valid Bing maps key, you must provide the key in the Map Settings dialog box.
Internet connection is mandatory to render the online portion of the map and for the address lookup.
If your system connects to the internet through a proxy server, the Proxy Settings configured in the OpenManage Essentials
Settings → General Settings page is used.
Internet connection is mandatory to access any zoom level and to use the search functionality.
If your system connects to the internet through a proxy server, the proxy settings configured in your web browser is used.
Two types of maps are available:
• Roads map — A simple, fast loading map with minimal details.
97
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
Configuring Map Settings
NOTE: Only OpenManage Essentials Administrators and Power Users are permitted to configure Map Settings.
The Map Settings dialog box allows you to enable or disable the Internet connection status notification and to provide a valid Bing key required by the Bing map provider or MapQuest key required by the MapQuest map provider.
To configure the map settings:
1.
Perform one of the following:
• Click Home → Map View .
• Click Manage → Devices → Map View .
2.
On the Map View :
• Right-click anywhere on the map, and then click Settings .
• Move the mouse pointer over the Actions menu, and click Settings .
The Map Settings dialog box is displayed.
3.
Select Update map view on any device or device group selection if you want the map to display only the pin or pins that correspond to the device or device group selected in the device tree.
4.
Select Show internet connection warning when unable to connect to the internet if you want to display a warning on the map if an Internet connection is not available.
5.
Select one of the following map providers:
• MapQuest
• Bing
6.
In the Key field, type the appropriate map provider key.
7.
Click Apply .
Related link
General Navigation and Zooming
To move the map, click and drag the map in the desired direction or use the navigation arrows in the Navigation toolbar.
You can zoom in or zoom out of the map using any of the following methods:
• Double-click a pin to zoom in to street level around that pin. You can also zoom in to street level by:
– Right-clicking a pin, and then clicking Zoom to Street Level
– Moving the mouse pointer over the Actions menu, and then clicking Zoom to Street Level
• If a pin is displayed at street level, double-click the pin to zoom out to the world-level view
• Double-click a location on the map to zoom-in one level at that location
• Move the mouse wheel up or down to quickly zoom out or in on the map
98
• 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
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
. For instructions to set a region on the map as your home view, see Setting a Home View
.
Related link
Tool Tip
Moving the mouse pointer over the pin displays a tool tip that contains the following information:
• Device name
• Description
• Address
• Contact
• Model
• Service Tag
• Asset Tag
• Global status
• Connection status
Related link
Selecting a Device on Map View
To select a device on the map, click the appropriate pin. The corresponding device is highlighted in the device tree and all the other pins are hidden. When a device is selected in the device tree, it is also reflected on the map. If the Modular Systems or PowerEdge
VRTX group is selected in the device tree, then all the pins placed for those groups are displayed on the map.
NOTE: Hiding a device group in the device tree does not hide the corresponding pins on the map. For example, hiding the
Modular Systems group in the device tree does not hide pins on the map that represent devices in the Modular Systems group.
NOTE: Clicking a pin on the Map View (home) portal opens the Devices portal that displays details about the device.
Related link
Health and Connection Status
The health and connection status of a device can also be displayed on the map. To overlay the pin with the health or connection status of the device, move the mouse pointer over the Overlays menu at the top-right of the map, and click Health or Connectivity .
The health or connection status is indicated by the color and the icon displayed within the pin. The following table provides information about the health status and pin overlay:
99
Table 39. Health Status
Pin Color
Red
Yellow
Green
Gray
Icon Health Status
Critical
Warning
Normal
Unknown
The following table provides information about the connection status and pin overlay:
Table 40. Connection Status
Pin Color
Blue
Icon Connection Status
On
Grey Off
Related link
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. If the devices are in a very close proximity on the map and the map is zoomed out, the pins are displayed together as a multi-pin group. To view the count and the name of the devices in a multi-pin group, move the mouse pointer over the multi-pin group. Double-click or right-click a multi-pin group and then select Details , to open the Devices at this location window that lists the devices available at the location. On the Devices at this location window, you can:
• Double-click a device to display only that device on the map.
• Right-click a device to view standard options for the devices, such as Referesh Inventory , Application Launch , and so on, and other map-specific options such as Edit Location Details , and so on.
NOTE: Only licensed devices can be placed on the map. Device groups cannot be placed on the map.
Related link
Setting a Home View
If you typically manage devices in a certain geographic region, you can set that region as your home view. Each OpenManage
Essentials user can save a different view of the map as their home view. By default, the home view is displayed when you open Map
View or when you select the Go to Home View option.
1.
Perform one of the following:
• Click Home → Map View .
• Click Manage → Devices → Map View .
2.
On the Map View , navigate and zoom until the current view is as desired.
3.
Perform one of the following:
• Right-click on the map, and then click Save Current View as Home View .
• Move the mouse pointer over the Actions menu, and then click Save Current View as Home View .
100
Related link
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 .
Related link
Adding a Device to the Map
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.
To add a device on the map:
1.
Perform one of the following:
• Click Home → Map View .
• Click Manage → Devices → Map View .
2.
On the Map View :
• Right-click the map, and click Add Licensed Device .
• Move the mouser pointer over the Actions menu, and click Add Licensed Device .
The Device Location Details dialog box is displayed.
3.
From the Devices list, select the device you want to add.
4.
If required, in the Description field, type an appropriate description for the device.
5.
If you want to add the device at a location different from where you right-clicked on the map, in the Address field, type the address of the location. For example, Chicago.
NOTE: Using the Address field to add a device on the map requires an Internet lookup through the map provider to resolve the provided address. The device is added 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.
6.
If required, in the Contact field, type the contact information.
7.
Click Save .
Related links
Adding a Device Using the Search Pin
Moving a Device Location Using the Edit Location Details Option
NOTE: Only OpenManage Essentials Administrators and Power Users are permitted to edit a map location.
1.
Perform one of the following:
• Click Home → Map View .
• Click Manage → Devices → Map View .
2.
Right-click a pin on the map, and select Edit Location Details .
The Device Location Details dialog box is displayed.
101
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 .
If the map provider is able to resolve the address or airport code, the pin is moved to the specified location on the map.
Related links
Moving a Device Location Using the Search Pin
Importing Licensed Devices
NOTE: Only PowerEdge VRTX and PowerEdge FX2/FX2s devices with an Enterprise license that are not already placed on the map can be imported to the map.
NOTE: Only OpenManage Essentials Administrators and Power Users are permitted to import licensed devices.
NOTE: You can only import a maximum of up to 500 devices at a time.
You can bulk import licensed devices on the map through a .csv file. An Export Template function is available, which creates a .csv file that is already populated with the names of the licensed PowerEdge VRTX and PowerEdge FX2/FX2s devices that are currently discovered.
To import licensed devices:
1.
Perform one of the following:
• Click Home → Map View .
• Click Manage → Devices → Map View .
2.
On the Map View , do one of the following:
• Right-click the map, and click Import Licensed Devices .
• Move the mouse pointer over the Actions menu, and click Import Licensed Devices .
The Import Licensed Devices dialog box is displayed.
3.
Click Export Template to download a .csv template that you can use for importing licensed PowerEdge VRTX devices.
NOTE: For more information about the template, see Template for Importing Devices
.
The Save As dialog box is displayed.
4.
Browse to the location where you want to save the .csv file, type an appropriate file name, and click Save .
5.
Open the .csv file, and perform one of the following:
• In the Latitude and Longitude columns, type the latitude and longitude coordinates for each device.
• In the Address column, type the address for each device. For example, 1 dell way, round rock, TX.
NOTE: Before you import devices using the address, ensure that the system is connected to the Internet. If the system connects to the Internet through a proxy server, verify if the proxy settings are configured in the Settings
→ General Settings page. Also, the Internet search provider may reject the address search request if you are attempting to import too many devices at a time. If this occurs, wait for some time and try importing again.
6.
Click Import .
The Open dialog box is displayed.
7.
Select the location where the updated .csv file is located, and click Open .
The Import Summary dialog box is displayed.
8.
Click Ok .
102
NOTE: Any errors that may occur during the import process are displayed in Logs → UI Logs.
Related links
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. Template for Importing Devices
Field
Name
Latitude
Longitude
Address
Description (Optional)
Contact (Optional)
Description
The name of the PowerEdge VRTX and PowerEdge FX2/FX2s devices with an Enterprise license. This field is already populated with the currently discovered PowerEdge VRTX devices with an
Enterprise license that are not already placed on the map.
The latitude coordinate of the device location.
The longitude coordinate of the device location.
The address of the device location. If both latitude and longitude coordinates are specified, the address need not be specified.
Any information that you want to include about the device.
Any contact information that you want to include for the device..
To import the PowerEdge VRTX and PowerEdge FX2/FX2s devices with an Enterprise license to the map, you must update the .csv file with one of the following:
• Latitude and Longitude
• Address
Related link
Using the Map View Search Bar
NOTE: The map providers may not be able to resolve all addresses or airport codes correctly.
The search bar on Map View enables you to search for locations on the map using an address or airport code. To search for a location, type the location name or airport code (for example, New York or JFK) in the search bar, and either press <Enter> or click the arrow icon. If the map provider is able to resolve the address or airport code, a search pin is displayed at the specified location on the map.
Related link
Search Pin
The search pin is a larger pin that represents the search result on the map. The following are the characteristics of the search pin:
• At any instance, only one search pin can be located on the map. The search pin is displayed on the map at a location until you remove it or perform a new search. To remove the search pin, right-click the search pin and click Remove .
• Unlike the device pin, the search pin does not overlay any status.
• Double-clicking the search pin allows you to zoom in and zoom out of the location.
• Move the mouse pointer over the search pin to display a tool tip that includes the address of the location.
• You can add or move a licensed PowerEdge VRTX and PowerEdge FX2/FX2s devices at the search pin location.
103
.
Related link
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:
• Click Home → Map View .
• Click Manage → Devices → Map View .
2.
Type the address or airport code (for example, New York or JFK) in the search bar, and either press <Enter> or click the arrow icon.
If the map provider is able to resolve the address or airport code, a search pin is displayed at the location on the map.
3.
Right-click the search pin and click Add Licensed Device Here .
The Device Location Details dialog box is displayed.
4.
From the Devices list, select the device you want to add.
5.
Click Save .
Related links
Moving a Device Location Using the Search Pin
NOTE: Only OpenManage Essentials Administrators and Power Users are permitted to add a device to the map.
To move a device location:
1.
Perform one of the following:
• Click Home → Map View .
• Click Manage → Devices → Map View .
2.
Select the pin for a licensed PowerEdge VRTX or PowerEdge FX2/FX2s devices on the map.
3.
Type the address or airport code (for example, New York or JFK) in the search bar, and either press <Enter> or click the arrow icon.
If the map provider is able to resolve the address or airport code, a search pin is displayed at the location on the map.
4.
Right-click the search pin and click Move Selected Device Here .
5.
On the Move Device confirmation dialog box, click Yes .
The selected device is moved to the location of the search pin.
Related links
Moving a Device Location Using the Edit Location Details Option
Removing All Map Locations
NOTE: Only OpenManage Essentials Administrators and Power Users are permitted to remove all map locations.
To remove all map locations:
1.
Perform one of the following:
• Click Home → Map View .
104
• Click Manage → Devices → Map View .
2.
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
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.
Right-click a pin on the map, and select Edit Location Details .
The Device Location Details dialog box is displayed.
2.
In the Description field, edit the description as required.
3.
If you want to move the device to a new location, in the Address field, type the location name.
4.
In the Contact field, edit the contact information as required.
5.
Click Save .
Related link
Removing a Map Location
NOTE: Only OpenManage Essentials Administrators and Power Users are permitted to remove a map location.
To remove a location on the map:
1.
Perform one of the following:
• Click Home → Map View .
• Click Manage → Devices → Map View .
2.
On the Map View , right-click the location you want to remove and select Remove Location .
The Delete Location dialog box is displayed prompting for your confirmation.
3.
Click Yes .
Related link
Exporting All Device Locations
Exporting all device locations allows you to save the information about the devices and their latitude and longitude coordinates as a .csv file. If the address is known for a pin, it is included in the Description field of the .csv
file. Using this file, you can import the device locations at any time.
NOTE: By default, the latitude and longitude coordinates of each device is saved to the .csv
file, even if the latitude and longitude coordinates were not provided previously.
To export all device locations currently placed on the map:
1.
On the Map View , move the mouse pointer over the Actions menu, and then click Export .
105
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
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.
When a PowerEdge FX chassis is selected in the device tree, a graphical representation ( Chassis View ) of the front of the chassis is displayed in the device details page. The inventory information of the chassis is displayed under the Chassis View .
NOTE: The Chassis View is only displayed if the PowerEdge FX chassis is discovered using the WS-Man protocol, and at least one of the slots is occupied by a sled.
Figure 22. Chassis View
Tool Tip and Device Selection
Moving the mouser pointer over a slot on the chassis displays a yellow rectangular box around the slot and a tool tip.
NOTE: The tool tip is only displayed if the slot has a sled installed.
The information displayed in the tool tip varies based on the discovery and inventory status of the sleds. If a sled that contains multiple compute nodes (For example, PowerEdge FM120x4) is discovered and inventoried, the tool tip displays the:
• Slot name
• Health status
• Connection status
If any other compute sled is discovered and inventoried and for storage sleds, the tool tip displays the:
• Slot name
• Sled model
• Service Tag
• Asset tag
106
• 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 . To view the inventory information of a node, double-click the node in the summary.
• If a slot with a storage sled is selected, the chassis inventory information is displayed under the Chassis View . The storage sled inventory information is displayed in the chassis inventory.
NOTE: Complete inventory information of a sled is displayed only if the chassis and sled are discovered using the appropriate protocol.
NOTE: If a sled is selected in the device tree, the Chassis View is not displayed. To display the Chassis View, click the
PowerEdge FX chassis in the device tree.
Overlays
If a slot is occupied and the compute sled is discovered, by default, the health status of the compute sled is overlaid in the Chassis
View . The following are the available overlay options and their descriptions.
Table 42. Overlays
Overlay Option
Health Status
Overlay Color
Red
Yellow
Device Status
Warning
Critical
Connection Status
None
Light gray
Dark gray
No overlay
No overlay
Unknown
Off (disconnected)
On (connected)
Not applicable
NOTE: The health and connection status of a compute sled requires that the sled is discovered. If a sled is not discovered or the status of the sled is unknown, the health and connection status are displayed as normal.
The health status of the sled that contains multiple compute nodes reflects the health status of the compute node with most critical severity. For example, if one compute node is in a Warning state and the remaining compute nodes are in a Critical state, the sled displays Critical status.
NOTE: The Chassis Management at Server Mode option of the PowerEdge FX chassis can be used to configure rack style management. If rack style management is disabled on a PowerEdge FX chassis, the health status roll-up of the chassis is not updated in OpenManage Essentials. Also, alerts generated from the PSU and fan are not received in
OpenManage Essentials.
Right-Click Actions
The right-click action on any compute sled that is discovered and available in the device tree is the same as when you right-click the sled in the device tree.
NOTE: Right-click actions are not available for sleds that contain multiple compute nodes and storage sleds.
Navigation Trail
The navigation trail is displayed as a link under the Chassis View and indicates the currently selected device. You can click a device name in the navigation trail to go back to the chassis inventory.
107
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).
• Storage sleds — These sleds are not discoverable and are not displayed in the device tree, device summary, or any typical locations for a device. The storage sled is displayed in the Chassis View and the storage sled inventory is displayed in the chassis inventory page.
• Sleds with multiple compute nodes — An example of this type of sled is the PowerEdge FM120x4 sled which contains four compute nodes. If the compute nodes of the sled are discovered, they are displayed in the device tree under: All Devices →
Modular Systems → PowerEdge FX → Chassis Group → Sled Group → Server Node . Each compute node is displayed under the corresponding sled. The Sled Group name in the device tree can be edited if necessary.
NOTE: For in-band (without OMSA) discovery and monitoring of the PowerEdge FM120x4 sled, ensure that either the WMI or SSH protocol is enabled and setup.
NOTE: The sleds installed in a PowerEdge FX chassis are sorted based on the device name and not on the slot number in the device tree.
VLAN Configuration Management
The VLAN Configuration tab enables you to:
• View details of the blade server and IOA fabric interconnect such as the blade server NIC port, the associated IOA fabric port, and the VLAN IDs.
NOTE: Even if there is no information available for the IOAs, the fabric status is shown as data in grid and values such as Slot is empty and Firmware or Mode is not supported.
• Assign VLAN IDs to the IOAs within the chassis.
NOTE: If an already discovered IOA or server is moved from one chassis to another, removed from a chassis, or swapped within the chassis, you must delete and rediscover the chassis, servers, and the corresponding IOAs. Otherwise, the
VLAN configuration inventory may display duplicate or incorrect data.
Requirements for VLAN Configuration Management
• VLAN configuration management is supported only for PowerEdge M1000e and PowerEdge FX2 or FX2s chassis.
NOTE: For VLAN configuration management on MX7000 chassis, see Editing a device deployment template
.
• The chassis and its components (blade servers and IOAs) must be discovered in OpenManage Essentials using the Guided
Wizard.
• The IOAs must be configured in Standalone, Virtual Link Trunk (VLT), or Programmable MUX (PMUX) operational mode.
• The minimum required firmware version is as follows:
– PowerEdge M1000e—firmware version 6.1.
– PowerEdge FX2 or FX2s—firmware version 2.1.
– PowerEdge M and FN IOA
â—¦ OpenManage Essentials version 2.5 supports 9.10.0.0, 9.10.0.1P10, 9.11.0.0, 9.11.2.0, 9.13.0.0, and 9.14.0.0.
NOTE: VLAN configuration management is not supported for the PowerEdge FM120x4 sleds. Only the server-chassis slot mapping is displayed in the VLAN Configuration tab for the PowerEdge FM120x4 sleds. The server name and NIC port details are not displayed in the VLAN Configuration tab for the PowerEdge FM120x4 sleds.
108
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.
NOTE: If you are accessing the VLAN Configuration tab for the first time, click the refresh icon displayed at the middle of the VLAN Configuration tab to display the configuration inventory.
that is
NOTE: The VLAN configuration inventory that is displayed may not be up-to-date. To view the latest VLAN configuration inventory, click the refresh icon tab.
that is displayed at the top-right of the VLAN Configuration
NOTE: VLAN configuration inventory is not displayed if the IOAs are not discovered or configured.
Even though the VLAN configuration inventory is not displayed, OpenManage Essentials displays the IOA Name and
Model information if it is available. Otherwise a status message is displayed, indicating the reason for the non-availability of the inventory information.
The following table describes the status messages that may be displayed.
Table 43. Viewing the VLAN Configuration Inventory
Status
Device not discovered
Slot is empty
Firmware or Mode not supported
Description
The IOA is not discovered in OpenManage Essentials.
The chassis fabric slot is empty.
Unable to retrieve data
Unknown/Error
Model not supported
The operational mode or firmware version of the IOA is not supported.
OpenManage Essentials is unable to retrieve the VLAN configuration inventory from the IOA.
An error occurred or the status is unknown.
The IOA model is not supported.
Assigning VLAN IDs
Before you begin, ensure that you have IOA administrator rights.
To apply VLAN assignments:
1.
On the VLAN Configuration tab, under Chassis IOA , type the VLAN IDs in the Tagged VLANs and Untagged VLAN columns for the appropriate ports.
NOTE: The valid range for VLAN IDs are 1 to 4094. Use a comma (,) to separate VLAN IDs and use a hyphen (-) to specify the ID range.
2.
Click Apply .
The VLAN Configuration window displays the IOA ports that you modified.
NOTE: You can also modify the VLAN IDs in the VLAN Configuration window.
109
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.
NOTE: While applying VLAN assignments to multiple ports, the VLAN configuration task may fail. The Task Results tab displays the ports to which the VLAN assignments failed with a message stating that the task failed after multiple retries or the server closed the network connection unexpectedly. In such a scenario, you can retry the VLAN configuration after some time to the ports were not configured successfully.
NOTE: OpenManage Essentials uses the IOA CLI commands to configure the VLAN on the IOA. Configuring the VLAN on the IOA is a time consuming and resource-intensive operation that may affect the performance of the IOA. To balance the operations on the IOA, OpenManage Essentials runs the IOA CLI commands in a timely manner, ensuring that there is sufficient time to configure the VLAN on the IOA. If the IOA is already running several operations, the VLAN configuration task may either be prolonged or fail. If the VLAN configuration fails on some IOA ports, you can rerun the
VLAN configuration task on the corresponding IOAs.
Resetting all VLAN IDs
Before you begin, ensure that you have fabric administrator rights.
After you make changes to VLAN IDs, if you want to revert all the changes:
1.
Click Reset All .
2.
When you are requested to confirm, click Yes .
NOTE: The changes you made to the VLAN IDs are affected only in the OpenManage Essentials user interface.
Setting the Default VLAN ID Values
Before you begin, ensure that you have fabric administrator rights.
If you want to set the default VLAN IDs:
1.
Select the IOA fabric port that you want to set to the default VLAN ID.
2.
Click Set to default value .
The tagged VLAN column displays All VLANs and the untagged VLAN column displays 1 .
NOTE: For tagged VLANs, the default value of All VLANs ranges from 2 to 4094. For untagged VLAN, the default value is 1.
3.
Click Apply .
4.
Type a unique name of the task.
5.
If required, select a schedule for the task.
6.
Type the credentials of the IOA that have fabric administrator rights.
7.
Click Finish .
The VLAN Configuration task is created in the Task Results tab. After the task is completed, OpenManage Essentials automatically inventories the VLAN configuration of all IOAs in the chassis.
Dell NAS Appliance Support
The following table provides information about discovery and classification, availability of appliance node information, and alert correlation for supported Dell NAS appliances.
110
Table 44. Dell NAS Appliance Support
Discovery and
Classification
Dell EqualLogic FS7500 with
FluidFS Version 1
Support for discovery using both the EqualLogic Group Manager IP and management IP.
If discovered using the controller
IPs, it results in multiple entries.
Appliance Node
Information
Alerts
Displayed in the device inventory.
Alerts received from the controller are not correlated to the device.
Dell EqualLogic FS7500 with
FluidFS Version 3
Support for discovery using the controller/node IPs.
If discovered using the EqualLogic
Group Manager IP, the device will get classified under Dell EqualLogic
Group.
Dell PowerVault MD NX3500 with
FuildFS Version 1
Support for discovery using both the controller IPs.
If discovered using the PowerVault
MD Series array IP, the device is classified as a PowerVault MD
Array device.
Displayed in the device inventory.
Displayed in the device inventory.
Alerts received from the controller/ node are correlated to the device.
NOTE: It is highly recommended to include all controller/node IP addresses in the discovery range configuration while discovering a NAS cluster with FluidFS version 3.0.
This enables OpenManage
Essentials to properly associate the SNMP alerts received from various participating controllers/ nodes with the discovered cluster.
Some alerts received from the device may be displayed as
Unknown.
OEM Device Support
OEM devices (re-branded or de-branded servers and Compellent S8000 iDRAC), when discovered, are classified under OEM
Devices in the device tree. Most of the functionality available to servers, such as tasks, reports, and filters are also applicable to
OEM servers. However, system update may not be possible if it is not supported by the OEM device module. For more information on the supported protocols and features, see information on servers/devices in
Supported Devices Protocols and Features Matrix .
OEM servers are always classified under the OEM Devices group in the device tree. They are not displayed under the Servers or
RAC group. If both the server and RAC of the OEM device are discovered, they are correlated and displayed as one device under the
OEM Devices group. Other OEM devices except servers and RAC are classified under the different server groups such as Microsoft
Virtualization Servers, VMware ESX servers, and so on, based on the classification criteria they satisfy.
NOTE: OEM servers discovered using WMI protocol are classified under the Servers device group only when OMSA is installed. OEM servers without OMSA are classified under the Unknown device group.
111
advertisement
Key Features
- Comprehensive hardware and software inventory
- Automated discovery and monitoring of Dell EMC devices
- Remote management of servers, storage, and networking devices
- Real-time performance monitoring and alerting
- Remote control and virtual media capabilities
- Easy-to-use web-based interface
- Support for multiple operating systems and hypervisors
- Integration with other Dell EMC management tools
Related manuals
Frequently Answers and Questions
What types of Dell EMC devices can OpenManage Essentials manage?
Can OpenManage Essentials be deployed on-premises or in the cloud?
What are the benefits of using OpenManage Essentials?
advertisement
Table of contents
- 3 Dell EMC OpenManage Essentials Version 2.5 User's Guide
- 19 About OpenManage Essentials
- 19 New in this release
- 19 Other information you may need
- 20 Contacting Dell
- 21 Installing OpenManage Essentials
- 21 Installation prerequisites and minimum requirements
- 21 Terms and conditions for using Relational Database Management Systems
- 22 Minimum login roles for Microsoft SQL Server
- 22 Recommended database size
- 23 Download OpenManage Essentials
- 23 Installing OpenManage Essentials
- 25 Custom Setup Installation
- 25 Setting up OpenManage Essentials Database on a Remote SQL Server
- 26 Retargeting the OpenManage Essentials Database
- 26 Backing up the OpenManage Essentials Database
- 26 Restoring the OpenManage Essentials Database
- 27 Creating a new user in SQL Server
- 27 Connecting to the OpenManage Essentials Database
- 28 Installing OpenManage Essentials on a domain controller
- 28 Installing OpenManage Essentials on a domain controller with a remote database
- 29 Installing OpenManage Essentials on a domain controller with a local database
- 30 Adding users to the OpenManage Essentials user groups
- 30 Enabling SQL Server and Windows Authentication Mode in SQL Server
- 31 Verifying SQL Server TCP or IP Status
- 31 Installing SupportAssist Enterprise
- 32 Installing Repository Manager
- 32 Installing License Manager
- 33 Upgrading OpenManage Essentials
- 34 Reconfiguring OpenManage Essentials version 2.5 after upgrading
- 35 Uninstalling OpenManage Essentials
- 36 Migrating IT Assistant to OpenManage Essentials
- 37 Getting started with OpenManage Essentials
- 37 Launching OpenManage Essentials
- 37 Configuring OpenManage Essentials
- 38 Configuring the Discovery Wizard
- 38 Configuring Discovery Settings
- 39 Using the OpenManage Essentials Home Portal
- 40 OpenManage Essentials Heading Banner
- 40 Customizing the portals
- 41 Displaying additional reports and graphs
- 41 Drilling down charts and reports for more information
- 42 Saving and loading the portal layout
- 42 Updating the portal data
- 42 Hiding graphs and reports—Components
- 43 Rearranging or resizing graphs and reports—Components
- 43 Filtering data
- 43 Using the Search Bar
- 44 Searching items
- 44 Using the search drop-down list
- 44 Search results and the default actions
- 45 Map View—Home Portal
- 45 Viewing the user information
- 45 Logging in as a different user
- 46 Using the Update Available Notification Icon
- 46 Using the Warranty Scoreboard Notification Icon
- 47 OpenManage Essentials Home Portal — Reference
- 47 Dashboard
- 47 Home Portal Reports
- 48 Device by Status
- 48 Alerts by Severity
- 48 Discovered Versus Inventoried Devices
- 49 Task Status
- 49 Schedule View
- 49 Schedule View Settings
- 50 Device Warranty Report
- 51 Map View Interface—Home Portal
- 52 Discovering and inventorying devices
- 52 Supported devices, protocols, and features matrix—SNMP, WMI, and WS-Man
- 56 Supported devices, protocols, and features matrix—IPMI, CLI, and SSH
- 58 Supported storage devices, protocols, and features matrix
- 59 Setting up and configuring VMware ESXi 5
- 60 Legend and definitions
- 60 Using the Discovery and Inventory Portal
- 61 Protocol support matrix for discovery
- 62 Protocol support matrix for system update
- 62 Devices not reporting Service Tag
- 63 Creating a discovery and inventory task
- 64 Changing the default SNMP port
- 65 Discovering and inventorying devices by using WS-Man or REST protocol with a root certificate
- 66 Discovering a chassis and its components by using Guided Wizard
- 67 Excluding ranges
- 67 Viewing configured discovery and inventory ranges
- 67 Scheduling discovery
- 68 Discovery Speed Slider
- 68 Multithreading
- 68 Scheduling inventory
- 69 Configuring status polling frequency
- 69 Task pop-up notifications
- 70 Configuring task pop-up notifications
- 70 Enabling or disabling task pop-up notifications
- 71 Discovery And Inventory — Reference
- 71 Discovery and Inventory Portal Page Options
- 71 Discovery and Inventory Portal
- 71 Last Discovery and Inventory
- 72 Discovered Versus Inventoried Devices
- 72 Task Status
- 73 Viewing Device Summary
- 73 Viewing Device Summary Filter Options
- 74 Add Discovery Range
- 74 Discovery Configuration
- 74 Discovery Configuration Options
- 75 Device Type Filtering
- 76 ICMP Configuration
- 76 ICMP Configuration Options
- 76 SNMP Configuration
- 77 SNMP Configuration Options
- 78 WMI Configuration
- 78 WMI Configuration Options
- 78 Storage Configuration
- 78 Storage Configuration Options
- 78 WS-Man Configuration
- 79 WS-Man Configuration Options
- 79 REST configuration
- 80 REST configuration options
- 80 SSH Configuration
- 80 SSH Configuration Options
- 81 IPMI Configuration
- 81 IPMI Configuration Options
- 81 Discovery Range Action
- 82 Summary
- 82 Add Exclude Range
- 82 Add Exclude Range Options
- 82 Discovery Schedule
- 83 Viewing Discovery Configuration
- 83 Discovery Schedule Settings
- 84 Inventory Schedule
- 84 Inventory Schedule Settings
- 84 Status Schedule
- 84 Status Polling Schedule Settings
- 85 Discovery Ranges
- 85 Exclude Ranges
- 86 Managing devices
- 86 Viewing devices
- 86 Device Summary Page
- 88 Nodes and symbols description
- 88 Device details
- 89 Viewing device inventory
- 90 Viewing alerts summary
- 90 Viewing noncompliant devices associated with a catalog baseline
- 90 Viewing noncompliant devices associated with a configuration baseline
- 90 Viewing System Event Logs
- 90 Searching for Devices
- 91 Creating a New Group
- 91 Adding Devices to a New Group
- 92 Adding Devices to an Existing Group
- 92 Hiding a Group
- 92 Deleting a Group
- 92 Associating a catalog baseline to custom device groups
- 93 Single Sign-On
- 93 Creating a Custom URL
- 93 Launching the Custom URL
- 94 Configuring Warranty Email Notifications
- 94 Configuring Warranty Scoreboard Notifications
- 95 Configuring Warranty Pop-Up Notifications
- 95 Configuring Warranty Update Settings
- 95 Using Map View
- 97 Map Providers
- 98 Configuring Map Settings
- 98 General Navigation and Zooming
- 99 Home View
- 99 Tool Tip
- 99 Selecting a Device on Map View
- 99 Health and Connection Status
- 100 Multiple Devices at the Same Location
- 100 Setting a Home View
- 101 Viewing All Map Locations
- 101 Adding a Device to the Map
- 101 Moving a Device Location Using the Edit Location Details Option
- 102 Importing Licensed Devices
- 103 Using the Map View Search Bar
- 104 Removing All Map Locations
- 105 Editing a Map Location
- 105 Removing a Map Location
- 105 Exporting All Device Locations
- 106 PowerEdge FX Chassis View
- 106 Tool Tip and Device Selection
- 107 Overlays
- 107 Right-Click Actions
- 107 Navigation Trail
- 108 Support For PowerEdge FX Chassis Sleds
- 108 VLAN Configuration Management
- 108 Requirements for VLAN Configuration Management
- 109 Viewing the VLAN Configuration Inventory
- 109 Assigning VLAN IDs
- 110 Resetting all VLAN IDs
- 110 Setting the Default VLAN ID Values
- 110 Dell NAS Appliance Support
- 111 OEM Device Support
- 112 Devices — Reference
- 112 Viewing Inventory
- 112 Viewing Alerts
- 113 Viewing Hardware Logs
- 113 Hardware Log Details
- 113 VLAN Configuration
- 114 VLAN Configuration Task
- 115 Task Results
- 116 Alert Filters
- 116 Viewing noncompliant systems—Devices
- 116 Non-Compliant Firmware and Drivers
- 117 Non-Compliant Configurations
- 117 Device Search
- 118 Query Results
- 118 Creating Device Group
- 119 Device Group Configuration
- 119 Device Selection
- 120 Summary — Group Configuration
- 120 Map View Interface—Devices Tab
- 121 Devices at this location
- 121 Map Settings
- 123 Deployment and reprovisioning
- 124 Server Configuration Management license
- 124 Licensable servers
- 124 Purchasing license
- 124 Deploying the license
- 124 Verifying license information
- 125 Viewing unlicensed server targets
- 125 Device requirements for deployment and compliance tasks
- 126 Getting started for device configuration deployment
- 126 Viewing the Deployment Portal
- 126 Configuring the deployment file share
- 127 Adding devices to repurpose and bare-metal devices group
- 127 Overview of bare-metal deployment
- 128 Creating a device deployment template
- 128 Creating a device deployment template from a device configuration file
- 129 Creating a device deployment template from a reference device
- 130 Managing device deployment templates
- 130 Viewing device deployment template attributes
- 130 Cloning a device deployment template
- 131 Editing a device deployment template
- 132 Exporting a device deployment template
- 132 Deploying a device deployment template—Bare-metal deployment
- 134 Creating a chassis deployment template from a chassis
- 135 Managing chassis deployment templates
- 136 Viewing and editing chassis deployment template attributes
- 136 Exporting a chassis deployment template
- 136 Cloning a chassis deployment template
- 136 Deploying a chassis infrastructure template
- 138 Deploying IOA configuration template
- 140 IOA operational modes and the deployment task status
- 140 Deploying a network ISO image
- 141 Removing devices from the repurpose and bare-metal devices group
- 141 Auto deploying device configurations
- 142 Configuring Auto Deployment Settings
- 142 Setting up device configuration auto deployment—Bare-metal deployment
- 144 Managing Auto Deployment Credentials
- 145 Adding a Discovery Range for Auto Deployment
- 145 Removing Devices From an Auto Deployment Task
- 146 Importing Device Specific Attributes
- 146 Import File Requirements
- 146 Exporting Device Specific Attributes
- 147 Viewing the Deployment Tasks
- 147 Managing the Virtual Input-Output Identities of a Server—Stateless Deployment
- 147 Overview of Stateless Deployment
- 148 Virtual Input-Output Pools
- 148 Creating a Virtual Input-Output Pool
- 151 Editing a Virtual Input-Output Pool
- 151 Viewing the Definitions of a Virtual Input-Output Pool
- 152 Renaming a Virtual Input-Output Pool
- 152 Deleting a Virtual Input-Output Pool
- 152 Viewing the Virtual Input-Output Identities Assigned or Deployed on a Device
- 153 Compute Pools
- 153 Creating a Compute Pool
- 154 Deploying a device configuration template—Stateless deployment
- 156 Automatic Locking of a Compute Pool
- 157 Unlocking a Compute Pool
- 157 Editing the Definitions of a Compute Pool
- 157 Viewing the Definitions of a Compute Pool
- 158 Removing a Server From a Compute Pool
- 158 Renaming a Compute Pool
- 158 Deleting a Compute Pool
- 158 Replacing a Server
- 160 Reclaiming Deployed Virtual Input-Output Identities of a Server
- 160 Reclaiming Assigned Virtual Input-Output Identities
- 161 Setting up device configuration auto deployment—Stateless deployment
- 163 Viewing device profiles
- 163 Known limitations for stateless deployment
- 163 Additional information
- 165 Deployment—Reference
- 166 Icons and descriptions
- 167 Repurpose and Bare Metal Devices
- 168 Auto Deployment
- 168 Tasks
- 169 Task Execution History
- 169 Device Configuration Template Details
- 170 IOA VLAN Attributes
- 171 Device Configuration Setup Wizard
- 171 File Share Settings
- 171 Add devices to repurpose and bare-metal devices group
- 171 Add Network
- 172 Network Types
- 172 Create Template Wizard
- 173 Create Virtual Input-Output Pool Wizard
- 173 Name and Description
- 173 Ethernet Identities
- 174 FCoE Node Name Identities
- 174 FCoE Port Name Identities
- 175 iSCSI IQN Identities
- 175 Summary
- 176 Virtual Input-Output Pools
- 176 Virtual Input-Output Pool Summary
- 177 Summary
- 177 Devices with Identities
- 178 Create Compute Pool Wizard
- 178 Name and Description
- 178 Select Template
- 178 Select ISO Location
- 179 Select Virtual Input-Output Pool
- 179 Select Devices
- 179 Edit Attributes
- 184 Summary
- 184 Compute Pool Summary
- 185 Compute Pool Details
- 185 Server Details
- 186 Deploy Template Wizard
- 186 Name and Deploy Options
- 186 Select Template
- 187 Select Devices
- 187 Select ISO Location
- 188 Select Virtual Input-Output Pool
- 188 Edit Attributes
- 192 Options
- 193 Set Schedule
- 193 Preview
- 194 Summary
- 195 Setup Auto Deployment Wizard
- 195 Select Deploy Options
- 195 Select Template
- 196 Select ISO Location
- 196 Select Virtual Input-Output Pool
- 197 Import Service Tags or Node IDs
- 197 Edit Attributes
- 201 Execution Credentials
- 203 Summary
- 203 Manage Auto Deployment Credentials
- 203 Credentials
- 204 Devices
- 204 Replace Server Wizard
- 204 Name
- 205 Source and Target
- 205 Review Source Attributes
- 207 Options
- 208 Credentials
- 208 Summary
- 209 Reclaim Identities Wizard
- 209 Name
- 209 Select Devices
- 210 Identity Assignments
- 210 Options
- 211 Credentials
- 211 Summary
- 212 Managing device configuration baseline
- 212 Viewing the Device Compliance Portal
- 212 Getting started for device configuration compliance
- 213 Device configuration compliance overview
- 213 Configuring the credentials and device configuration inventory schedule
- 214 Viewing the device configuration inventory
- 214 Creating a device compliance baseline for servers and chassis
- 215 Associating target devices with a baseline
- 215 Viewing compliance status of devices
- 216 Remediating noncompliant devices
- 216 Viewing compliance tasks
- 217 Viewing server backup profiles
- 217 Replacing a server from backup profile
- 219 Configuration – Reference
- 220 Device Compliance
- 220 Device Compliance Graph
- 220 Device Compliance Table
- 220 Tasks
- 221 Task Execution History
- 222 Associate Devices To a Baseline Wizard
- 222 Select Baseline
- 222 Select Devices
- 222 Make Devices Compliant
- 222 Name
- 222 Select Devices
- 223 Options
- 223 Set Schedule
- 224 Summary
- 224 Configuration Inventory Schedule Wizard
- 224 Inventory Credentials
- 225 Schedule
- 225 Backed-Up Devices
- 225 Devices Table
- 226 Attributes Table
- 227 Viewing inventory reports
- 227 Choosing predefined reports
- 227 Predefined reports
- 230 Filtering report data
- 230 Exporting reports
- 231 Reports — Reference
- 231 Server Inventory Reports
- 232 Agent and Alert Summary
- 233 Agent Health Status
- 233 Server Overview
- 234 Field Replaceable Unit Information
- 234 Hard Drive Information
- 235 iDRAC Performance Minimum or Maximum
- 236 iDRAC Performance Average or Peak
- 236 Memory Information
- 237 Modular Enclosure Information
- 237 NIC Information
- 238 PCI Device Information
- 238 Processor Information
- 239 Storage Controller Information
- 239 Virtual Disk Information
- 239 Server Configuration Reports
- 240 Server Components and Versions
- 240 BIOS Configuration
- 241 iDRAC Network Configuration
- 242 Device Configuration Compliance
- 242 Baseline Association
- 242 Assigned Identity Attributes
- 243 All Identity Attributes
- 243 Warranty and License Reports
- 244 Warranty Information
- 244 License Information
- 245 Virtualization Reports
- 245 ESX Information
- 245 HyperV Information
- 246 Asset Reports
- 246 Asset Acquisition Information
- 247 Asset Maintenance Information
- 248 Asset Support Information
- 248 Device Location Information
- 250 Viewing warranty reports
- 250 Extending warranty
- 251 Managing alerts
- 251 Viewing alerts and alert categories
- 251 Viewing alert logs
- 251 Understanding alert types
- 252 Viewing internal alerts
- 252 Viewing alert categories
- 252 Viewing alert source details
- 252 Viewing previously configured alert actions
- 252 Viewing application launch alert action
- 252 Viewing email alert action
- 253 Viewing alert ignore action
- 253 Viewing alert trap forward action
- 253 Handling alerts
- 253 Flagging an alert
- 253 Creating and editing a new view
- 253 Configuring alert actions
- 253 Setting up email notifications
- 254 Ignoring alerts
- 255 Running a custom script
- 255 Forwarding alerts
- 256 Forwarding alerts use case scenarios
- 256 Working with sample alert action use cases
- 256 Use cases in alert actions
- 257 Configuring alert log settings
- 257 Renaming alert categories and alert sources
- 257 Alert pop-up notifications
- 258 Configuring alert pop-up notifications
- 258 Enabling or disabling alert pop-up notifications
- 258 Managing MIB files
- 259 About importing MIBs
- 260 Importing MIBs
- 260 Removing MIBs from OpenManage Essentials
- 260 Managing traps
- 260 Customizing trap definitions
- 261 Resetting built-in trap definitions
- 261 Configuring SNMPv3 traps
- 263 Alerts — Reference
- 263 Alert Logs
- 264 Predefined Alert View Filters
- 264 Alert Logs Fields
- 265 Alert Details
- 265 Alert Log Settings
- 266 Alert View Filters
- 266 Alert Filter Name
- 266 Severity
- 267 Acknowledgement
- 267 Summary — Alert View Filter
- 267 Alert Actions
- 268 Name and Description
- 268 Severity Association
- 268 Application Launch Configuration
- 270 E-Mail Configuration
- 270 Trap Forwarding
- 271 SNMP V3 Configuration
- 271 SNMP V3 Configuration Wizard
- 272 Category and Sources Association
- 272 Device Association
- 273 Date and Time Range
- 273 Alert Action — Duplicate Alert Correlation
- 273 Summary — Alert Action Details
- 274 Alert Categories
- 274 Alert Categories Options
- 276 Edit Trap Definitions
- 276 Alert Source
- 277 Manage MIBs
- 277 Manage MIBs Pane
- 277 Manage Traps Pane
- 277 Import MIB
- 279 Remove MIB
- 279 Troubleshooting MIB Import
- 280 Manage Traps
- 280 Custom Trap Definitions
- 281 Reset Built-in Trap Definitions
- 282 Updating BIOS, firmware, drivers, and system applications
- 282 Viewing the System Update page
- 283 Understanding sources of system updates
- 283 Choosing the right source of system updates
- 283 Selecting an update catalog source
- 284 Viewing comparison results
- 284 Viewing compliant systems
- 284 Viewing noncompliant systems
- 284 Viewing non-inventoried systems
- 284 Viewing systems with issues and resolutions
- 284 Creating a catalog baseline
- 284 Viewing the Default Catalog
- 285 System Update Use Case Scenarios
- 287 Applying system updates by using the Non-Compliant Systems tab
- 288 Applying System Updates by using the System Update Task wizard
- 290 Viewing status of the System Update task
- 291 Updating systems without OpenManage Server Administrator
- 291 Issues and Resolutions Use Case Scenarios
- 291 Configuring automatic purging of downloaded system update files
- 292 System Update — Reference
- 293 Filter Options
- 293 System Update
- 293 Compliance Report
- 295 Compliant Systems
- 295 Non-Compliant Firmware and Drivers
- 296 System Update Task
- 298 Non-Inventoried Systems
- 298 Inventory Systems
- 298 All System Update Tasks
- 298 Issues and Resolutions
- 299 Task Execution History
- 299 Select a Catalog Source
- 300 Dell Update Package
- 300 OpenManage Server Update Utility
- 300 Repository Manager
- 300 Viewing the Default Catalog
- 301 View MX Chassis Default Catalog
- 301 View Catalog Baseline Associations
- 301 List of Catalog Baselines
- 301 Create Catalog Baseline wizard
- 302 Baseline Details
- 303 Managing remote tasks
- 303 Managing command line tasks
- 304 Managing RACADM command line tasks
- 304 Managing generic command line tasks
- 306 Managing server power options
- 306 Deploying OpenManage Server Administrator
- 307 Supported Windows and Linux Packages
- 308 Arguments
- 308 Deploying iDRAC Service Module
- 309 Supported Windows and Linux Packages
- 310 Collecting Firmware and Driver Inventory
- 311 Updating the inventory collector component
- 311 Working With Sample Remote Tasks Use Cases
- 312 Use Cases in Remote Tasks
- 313 Device Capability Matrix
- 316 Remote Tasks — Reference
- 316 Remote Tasks Home
- 317 Remote Tasks
- 317 All Tasks
- 318 Task Execution History
- 318 Server Power Options
- 320 Deployment Task
- 322 Command Line Task
- 322 Remote Server Administrator Command
- 324 Generic Command
- 325 IPMI Command
- 326 RACADM Command Line
- 328 Firmware and Driver Inventory Collection Task
- 330 Managing security settings
- 330 Using security roles and permissions
- 331 Microsoft Windows authentication
- 331 Assigning user rights
- 331 Using Custom SSL Certificates—Optional
- 331 Configuring IIS Services
- 332 Supported protocols and ports in OpenManage Essentials
- 332 Supported protocols and ports on management stations
- 332 Supported protocols and ports on managed nodes
- 333 Supported Protocols and Ports on Management Stations
- 333 Supported Protocols and Ports on Managed Nodes
- 334 Dell EMC OpenManage Framework
- 336 Troubleshooting
- 336 OpenManage Essentials Troubleshooting Tool
- 336 Troubleshooting Procedures
- 336 Troubleshooting Inventory
- 337 Troubleshooting Device Discovery
- 337 Troubleshooting Receiving SNMP Traps
- 338 Troubleshooting Discovery of Windows Server 2008–Based Servers
- 338 Troubleshooting SNMP Traps for ESX or ESXi Versions 3.5, 4.x, or 5.0
- 338 Troubleshooting Problems With Microsoft Internet Explorer
- 339 Troubleshooting Map View
- 340 Frequently Asked Questions
- 340 Installation
- 340 Upgrade
- 341 Tasks
- 341 Optional Command Line Settings
- 342 Customization Parameters
- 343 MSI Return Code
- 344 E-mail Alert Action
- 344 Discovery
- 347 Inventory
- 348 System Update
- 349 Managing Device Configurations
- 349 Device Group Permissions
- 349 Device Group Permissions Portal
- 350 Remote and System Update Tasks
- 350 Custom Device Groups
- 350 Deployment and Configuration Compliance
- 350 Deployment and Configuration Compliance
- 351 Logs
- 352 Log Levels
- 352 Backup and Restore
- 352 Troubleshooting
- 354 Managing Device Group Permissions
- 354 Adding Users to the OmeSiteAdministrators Role
- 355 Assigning Device Groups to a User
- 355 Removing Users From the OmeSiteAdministrators Role
- 357 OpenManage Mobile Settings
- 357 Enabling or Disabling Alert Notifications For OpenManage Mobile
- 357 Enabling or Disabling OpenManage Mobile Subscribers
- 358 Deleting an OpenManage Mobile Subscriber
- 358 Viewing the Alert Notification Service Status
- 358 Notification Service Status
- 359 Viewing the OpenManage Mobile Subscriber Information
- 359 Mobile Subscriber Information
- 360 Troubleshooting OpenManage Mobile
- 361 Settings — Reference
- 361 Alert Settings
- 362 Custom URL Settings
- 362 Deployment Settings
- 363 Device Tree Settings
- 363 Discovery Settings
- 364 Feature Usage Settings
- 364 Email Settings
- 365 General Settings
- 366 Task Settings
- 366 Warranty Notification Settings
- 368 Permissions
- 368 Common Tasks
- 368 Manage Device Group Permissions
- 368 Device Groups for Tasks and Patch Targeting
- 368 Purge Download Settings
- 370 Logs — Reference
- 370 User Interface Logs
- 370 Application Logs
- 371 Dell EMC Solutions
- 372 Right-Click Actions
- 372 Schedule View
- 372 Device Status
- 373 Associate Catalog Baseline
- 374 Discovery Range Summary
- 374 Managing Include Ranges
- 374 View Filters
- 374 Alerts
- 375 Remote Tasks
- 375 Custom URL
- 375 System Update Tasks
- 376 Attributes Tab
- 376 Templates
- 376 Compute Pools
- 376 Repurpose and Bare Metal
- 376 Compute Pool
- 377 Devices
- 377 Virtual Input-Output Pools
- 377 Virtual I/O Pool
- 377 Devices with Identities
- 378 Compliance by Template
- 378 Device Compliance
- 379 Tutorials
- 380 Using OpenManage Essentials Command Line Interface
- 380 Launching the OpenManage Essentials Command Line Interface
- 380 Creating an input file for Discovery Profile
- 381 Specifying IPs, ranges, or host names by using XML or CSV files
- 381 Specifying input files in PowerShell
- 381 Command Line Interface commands
- 382 Creating a discovery range
- 382 Editing a discovery range
- 382 Removing a discovery range
- 382 Creating a discovery range group
- 383 Editing a discovery range group
- 383 Removing a discovery range group
- 383 Enabling a discovery range or discovery range group
- 384 Disabling a discovery range or discovery range group
- 384 Creating a discovery exclude range
- 384 Removing a discovery exclude range
- 385 Running discovery, inventory, and status polling tasks
- 385 Removing devices
- 385 Retrieving the status execution progress of a discovery range
- 386 Stopping discovery range or group tasks
- 386 Creating a custom device group
- 386 Adding devices to a custom group
- 387 Deleting a custom device group