Dell PowerEdge MX7000 EMC OpenManage Enterprise-Modular Edition Version 1.10.2 - Page 99

Use case scenarios, Assigning backup to the MCM Lead, Creating chassis group with backup lead

Get Dell PowerEdge MX7000 PDF manuals and user guides View all Dell PowerEdge MX7000 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 99 highlights

16 Use case scenarios Assigning backup to the MCM Lead The backup lead chassis feature facilitates management of systems in the chassis group when the existing lead chassis fails. Managing a chassis group consists of the following tasks: • Assign-Allows assigning a member of the chassis group as a backup to the existing lead chassis. • Unassign-Allows selection of another chassis in the group to replace the existing backup chassis. • Promote-Allows the backup chassis to takeover as the lead chassis when the existing lead chassis fails. • Retire-Allows the backup to takeover as the lead chassis when the existing lead chassis must be retired. For more information, see Chassis groups. Lifecycle of backup The life cycle of the backup feature consists of the following stages: 1. Stage 1-Creating a chassis group with backup lead. 2. Stage 2-Monitoring the health of the lead and backup. 3. Stage 3-Replacing the primary lead chassis with backup lead or retiring the lead chassis. Creating chassis group with backup lead To create a chassis group and assign a backup to the lead chassis, perform the following steps: 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: a. Configure chassis settings. b. Update firmware. c. Configure firmware baselines. d. Configure alert policies. e. Configure templates and identity pools, and deploy to devices or slots. f. 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 EMC 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. Use case scenarios 99

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
Use case scenarios
Assigning backup to the MCM Lead
The backup lead chassis feature facilitates management of systems in the chassis group when the existing lead chassis fails. Managing a
chassis group consists of the following tasks:
•
Assign—Allows assigning a member of the chassis group as a backup to the existing lead chassis.
•
Unassign—Allows selection of another chassis in the group to replace the existing backup chassis.
•
Promote—Allows the backup chassis to takeover as the lead chassis when the existing lead chassis fails.
•
Retire—Allows the backup to takeover as the lead chassis when the existing lead chassis must be retired.
For more information, see
Chassis groups
.
Lifecycle of backup
The life cycle of the backup feature consists of the following stages:
1.
Stage 1—Creating a chassis group with backup lead.
2.
Stage 2—Monitoring the health of the lead and backup.
3.
Stage 3—Replacing the primary lead chassis with backup lead or retiring the lead chassis.
Creating chassis group with backup lead
To create a chassis group and assign a backup to the lead chassis, perform the following steps:
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:
a.
Configure chassis settings.
b.
Update firmware.
c.
Configure firmware baselines.
d.
Configure alert policies.
e.
Configure templates and identity pools, and deploy to devices or slots.
f.
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 EMC 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.
16
Use case scenarios
99