Dell OpenManage Enterprise-Modular Edition Version 2.00.00 for PowerEdge MX7000 Chassis User's Guide

Creating chassis group with backup lead

1. Rack and stack the chassis.
2. Wire multiple chassis in the rack. For more information, see Wiring chassis and Pre-requisites for creating a distributed group.
3. Create a chassis group and add members to the group. For more information, see Chassis groups.
   Configuring a virtual IP is optional. The virtual IP enables a secondary IP on the lead that sticks with the lead. If the backup takes over as the new lead, then the secondary IP automatically moves to the new lead.
4. Configure the group from the lead chassis.
   If there are any settings and configurations on the member chassis that could conflict with lead, clear those configurations before the lead pushes its configuration across the group. Do the following, if required:

   1. Configure chassis settings.
   2. Update firmware.
   3. Configure firmware baselines.
   4. Configure alert policies.
   5. Configure templates and identity pools, and deploy to devices or slots.
   6. Configure other settings.
5. Assign one of the members of the chassis group as the backup lead.
   The initial configuration data synchronization from the lead chassis to backup chassis continues even after the assign job is completed. Both the lead and backup chassis report the health of the backup chassis.

   Initially, the backup health status is displayed as "Critical" while the configuration data is being synchronized before changing to "OK". Wait for the backup health to transition to "OK" before proceeding. If the backup health continues to report "Critical" or "Warning" even after 30 minutes of the assign task, it is an indication that there are persistent communication issues. Unassign the backup and repeat the Step 5 to choose another member as the new backup. Also, Dell recommends that you create an alert policy on lead to take notification actions through email, SNMP trap, system log, for backup health alerts. Backup health alerts are part of the chassis configuration and system health category.

6. Configure the member chassis that is designated as the backup.

   It is mandatory for the backup chassis to have its own management network IP. The IP enables the backup to forward backup health alerts.

   Create an alert policy on the backup to take notification actions (email, SNMP trap, system log) for backup health alerts. Backup health alerts are part of Chassis (Configuration, System Health) category. The backup chassis raises warning or critical alerts when it detects that the backup synchronization status is bad because of communication or other irrecoverable errors.