Users Guide

Table Of Contents
Automatic refresh of MX7000 chassis on insertion and removal
sleds
OpenManage Enterprise can almost instantly reflect the addition or removal of sleds after a standalone or a lead MX7000
chassis is discovered or onboarded.
When a standalone or a lead MX7000 chassis is discovered or onboarded by using OpenManage Enterprise (versions 3.4 and
later), an alert policy is created simultaneously on the the MX7000 chassis. For more information on discovering and onboarding
devices in OpenManage Enterprise, see Create a device discovery job on page 42 and Onboarding devices on page 43.
The automatically-created alert policy on the MX7000 OpenManage Enterprise-Modular appliance triggers a chassis inventory
refresh job, named Refresh Inventory of Chassis in OpenManage Enterprise every time a sled is inserted, removed, or
replaced in the MX7000 chassis.
Post completion of the chassis- inventory-refresh job, the sled-related changes to the MX7000 are displayed on the All Devices
page.
The following prerequisites must be met while onboarding the MX7000 chassis for a successful creation of the automatic alert
policy :
OpenManage Enterprise-Modular version 1.2 must be already installed in the MX7000.
MX7000 chassis should be onboarded with the options 'Enable trap reception from discovered iDRAC servers and
MX7000 chassis' and 'Set Community String for trap destination from Application Settings'.
The OpenManage Enterprise appliance IP should get successfully registered as one of the four available alert destinations in
the newly-onboarded MX7000. If all the alert destinations in the MX7000 are already configured at the time of onboarding,
then the automatic alert policy creation will fail.
NOTE:
The alert policy on MX7000 is only specific to the sleds and are not applicable to the other components of the chassis,
such as the IOMs.
MX7000 alert preferences can be set in OpenManage Enterprise to either receive all the alerts or only the chassis-
category alerts from the MX7000 chassis. For more information, see Manage Console preferences on page 156.
Some delay is to be expected between the actual action on the sleds and the triggering of the chassis inventory
refreshing on OpenManage Enterprise.
The automatically created alert policy is deleted if the MX7000 chassis is deleted from the device inventory of
OpenManage Enterprise.
The All Devices page will list the Managed State for a successfully onboarded MX7000 chassis with automatic alert
forwarding policy as 'Managed with Alerts'. For more information on onboarding, refer Onboarding devices on page 43
Alert definitions
By clicking OpenManage Enterprise > Alerts > Alert Definitions, you can view alerts that are generated for errors or
informational purposes. These messages are:
Called as Event and Error messages.
Displayed on the Graphical User Interface (GUI), and Command Line Interface (CLI) for RACADM and WS-Man.
Saved in the log files for information purpose only.
Numbered and clearly defined to enable you implement corrective and preventive actions effectively.
An Error and Event message has:
MESSAGE ID: Messages are classified based on components such as BIOS, power source (PSU), storage (STR), log data
(LOG), and Chassis Management Controller (CMC).
MESSAGE: The actual cause of an event. Events are triggered for information purpose only, or when there is an error in
performing tasks.
CATEGORY: Class to which the error message belongs to. For information about categories, see the Event and Error
Message Reference Guide for Dell EMC PowerEdge Servers available on the support site.
Recommended Action: Resolution to the error by using GUI, RACADM, or WS-Man commands. Where necessary, you are
recommended to refer to documents on the support site or TechCenter for more information.
Detailed Description: More information about an issue for easy and fast resolution.
You can view more information about an alert by using filters such as message ID, message text, category, and Subcategory. To
view the alert definitions:
118
Monitor and Manage device alerts