Users Guide

NOTE: An MX7000 chassis can be a lead, stand-alone, or member chassis. If an MX7000 chassis is a lead chassis and
has a member chassis, the latter is discovered by using the IP of its lead chassis. An MX7000 chassis is identified by
using one of the following syntaxes:
○ MCM group—Indicates the Multi-Chassis Management (MCM) group that has more than one chassis identified by
the following syntax: Group_<MCM group name>_<Lead_Chassis_Svctag> where:
￭ <MCM group name>: Name of the MCM group
￭ <Lead_Chassis_Svctag>: The Service Tag of the lead chassis. The chassis, sleds, and network IOMs form
this group.
○ Stand-alone Chassis group—Identified by using the <Chassis_Svctag> syntax. The chassis, sleds, and
network IOMs form this group.
● Network Devices: Dell Force10 networking switches and Fibre Channel switches
● Servers: Dell iDRAC servers, Linux servers, Non-Dell servers, OEM servers, and Windows servers
● Storage Devices: Dell Compellent storage Arrays, PowerVault MD storage arrays, and PowerVault ME storage arrays
● Discovery Groups: Groups that map to the range of a discovery task. Cannot be edited or deleted because the group is
controlled by the discovery job where the include/exclude condition is applied. See Discovering devices for monitoring or
management on page 104.
NOTE: To expand all the subgroups in a group, right-click the group, and then click Expand All.
Custom Groups: Created by the user for specific requirements. For example, servers that host email services are grouped.
Users can view, edit, and delete based on user privileges and group types.
● Static Groups: Manually created by the user by adding specific devices to a group. These groups change only when a user
manually changes the devices in the group or a sub-group. The items in the group remain static until the parent group is
edited or the child device is deleted.
● Query Group: Groups that are dynamically defined by matching user-specified criteria. Devices in the group change based
on the result of devices that are discovered by using criteria. For example, a query is run to discover servers that are
assigned to the Finance department. However, the Query Groups have a flat structure without any hierarchy.
NOTE:
Static and Query groups:
● Cannot have more than one parent group. Meaning, a group cannot be added as a sub-group under its parent group.
● When changes are made to a Static group (devices are added or deleted) or a Query group (when a query is updated),
the firmware/driver compliance of the devices associated with these groups is not automatically refreshed. It is
recommended that the user initiates a firmware and/or driver compliance for the newly added/deleted devices in such
instances.
NOTE: Creating more number of Custom (Query) groups in the device group hierarchy impacts the overall performance of
OpenManage Enterprise. For optimized performance, OpenManage Enterprise captures the health-rollup status after every
10 seconds—having more number of Dynamic groups affects this performance.
On the All Devices page, in the left pane, you can create child groups under the parent Static and Query group. See Create or
delete a Static device group on page 39 and Create or edit a Query device group on page 39.
NOTE:
To perform any tasks on OpenManage Enterprise, you must have necessary user privileges. See Role-based
OpenManage Enterprise user privileges on page 14.
To delete the child group of a Static or Query group:
1. Right-click the Static or Query group, and then click Delete.
2. When prompted, click YES. The group is deleted, and the list under the group is updated.
Related tasks
Delete devices from OpenManage Enterprise on page 42
Refresh the device inventory on page 44
Refresh the device status on page 44
OpenManage Enterprise Home portal
35