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

Retiring lead chassis

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 103 highlights

1. Relocate network switches from the old lead to the new lead or member chassis in the group to restore the health of the fabrics. 2. Relocate computes from the old lead to the new lead or member chassis in the group. New templates or identities must be deployed on the computes before resuming workloads, which they were running on the old lead chassis. Retiring lead chassis The "retire" option enables a backup chassis to takeover as the lead of a chassis group when the lead chassis is running for a long time and must be removed from the production environment temporarily or permanently. The lead chassis can gracefully detach from the group. The "retire" option also facilitates the lead to retire from the lead role but remain a member of the group. 1. Run "retire" task from the lead chassis: a. A job is created when the "retire" task starts. The job may be completed in 10-45 minutes based on the number of chassis in the group and amount of configuration to restored. b. If the lead chassis is configured to forward alerts to external destinations (email, trap, system log), any alerts that the components in the group generate are only available locally in their respective hardware or alert logs when the retire task and the backup taking over the lead chassis is in progress. After the "retire" task is complete and before the backup is promoted, there is an outage in group management. The outage includes forwarding of alerts to configured external destinations. 2. Expected behavior of backup on completion of the "retire" task: a. The backup chassis becomes the new lead and all the member chassis are accessible as they were on the retired lead chassis. The new lead chassis rediscovers all the members in the group and if any member chassis is inaccessible then, the members are still listed on the Home page of the lead chassis with broken connection and available repair options. Use the repair option to readd or remove the member chassis from the group. b. All firmware baselines or catalogs, alert policies, templates or identity-pools, and fabrics settings are restored, as they were on the retired lead chassis. 3. Expected behavior of old lead chassis on completion of the "retire" task: a. If the old lead is chosen to retire as a stand-alone chassis, it continues to carry the templates/identity-pools configuration. Perform the following steps to clear configuration to avoid conflicts with the new lead. 1. Unstack the earlier lead from the group. 2. Reclaim any identity-pool IO identities that are deployed to computes on the old lead. 3. Do not delete fabrics from the old lead chassis as deleting the fabrics can lead to network loss once the old lead is added back to the network. 4. Run a force "reset configuration" using the following REST API payload: URI: /api/ApplicationService/Actions/ApplicationService.ResetApplication Method: POST Payload: {"ResetType": "RESET_ALL", "ForceReset": true} b. If the old lead is retired as a member of the current group, it no longer carries the identity-pools configuration. However, it contains the templates configuration. To avoid conflicts with the new lead, clear the templates configuration using Configuration > Deploy > Delete. Use case scenarios 103

  • 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
1.
Relocate network switches from the old lead to the new lead or member chassis in the group to restore the health of the
fabrics.
2.
Relocate computes from the old lead to the new lead or member chassis in the group. New templates or identities must be
deployed on the computes before resuming workloads, which they were running on the old lead chassis.
Retiring lead chassis
The "retire" option enables a backup chassis to takeover as the lead of a chassis group when the lead chassis is running for a long time and
must be removed from the production environment temporarily or permanently. The lead chassis can gracefully detach from the group.
The "retire" option also facilitates the lead to retire from the lead role but remain a member of the group.
1.
Run "retire" task from the lead chassis:
a.
A job is created when the "retire" task starts. The job may be completed in 10-45 minutes based on the number of chassis in the
group and amount of configuration to restored.
b.
If the lead chassis is configured to forward alerts to external destinations (email, trap, system log), any alerts that the components
in the group generate are only available locally in their respective hardware or alert logs when the retire task and the backup taking
over the lead chassis is in progress. After the "retire" task is complete and before the backup is promoted, there is an outage in
group management. The outage includes forwarding of alerts to configured external destinations.
2.
Expected behavior of backup on completion of the "retire" task:
a.
The backup chassis becomes the new lead and all the member chassis are accessible as they were on the retired lead chassis. The
new lead chassis rediscovers all the members in the group and if any member chassis is inaccessible then, the members are still
listed on the
Home
page of the lead chassis with broken connection and available repair options. Use the repair option to readd or
remove the member chassis from the group.
b.
All firmware baselines or catalogs, alert policies, templates or identity-pools, and fabrics settings are restored, as they were on the
retired lead chassis.
3.
Expected behavior of old lead chassis on completion of the "retire" task:
a.
If the old lead is chosen to retire as a stand-alone chassis, it continues to carry the templates/identity-pools configuration. Perform
the following steps to clear configuration to avoid conflicts with the new lead.
1.
Unstack the earlier lead from the group.
2.
Reclaim any identity-pool IO identities that are deployed to computes on the old lead.
3.
Do not delete fabrics from the old lead chassis as deleting the fabrics can lead to network loss once the old lead is added back
to the network.
4.
Run a force “reset configuration” using the following REST API payload:
URI:
/api/ApplicationService/Actions/ApplicationService.ResetApplication
Method:
POST
Payload:
{"ResetType": "RESET_ALL", "ForceReset": true}
b.
If the old lead is retired as a member of the current group, it no longer carries the identity-pools configuration. However, it contains
the templates configuration. To avoid conflicts with the new lead, clear the templates configuration using
Configuration
>
Deploy
>
Delete
.
Use case scenarios
103