Users Guide

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 version 3.4, 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 105 and Onboarding devices on page 106.
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 138.
• 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
106
Create alert policies
NOTE:
To perform any tasks on OpenManage Enterprise, you must have the necessary user privileges. See Role-based
OpenManage Enterprise user privileges on page 14.
1. Click Alert Policies > Create.
2. In the Create Alert Policy dialog box, in the Name and Description section, enter the name and description of the alert policy.
a. To enable an alert policy by default, select the Enable Policy check box.
b. Click Next.
3. In the Category section, select the All check box to apply the alert policy to all the available categories. By default, the following
categories are displayed, but not applied. To view sub-categories under each category, expand the category:
a. Click Next.
4. In the Target section, add devices or groups. See Select target devices and device groups on page 102.
• To specify an undiscovered device (third-party device), select Specific Undiscovered Devices, and then type the IP address or
host name.
• To specify any undiscovered device, select Any Undiscovered Devices.
NOTE: The Remote Script Execution and Power Action tasks cannot be performed on the undiscovered devices.
NOTE: Alerts from such foreign and undiscovered devices can be ignored.
Monitoring device alerts 91