Users Guide

Also, see the section, Use case scenarios.

When a job for assigning a member chassis as the backup lead is stopped, the status of the job on the Jobs page is displayed

as Stopped. However, the member chassis is assigned as the backup lead of the group.

Promoting backup chassis as lead

You can promote the backup chassis as the new lead chassis when the existing lead chassis fails. If the initial lead chassis is

available, you can also assign it as a member chassis. To promote the backup chassis as the lead chassis, you must log in to the

backup chassis.

After promoting a backup lead as lead chassis, detach and reattach any profiles that are attached to a slot containing a compute

sled, in the new lead. Detaching and reattaching the profiles ensures that the assignment is persistent. The "promote" task does

not affect profiles that are assigned to empty slots. Also, see the section, Use case scenarios.

1. On home page of the backup chassis, click Configure > Promote As Lead Chassis.

The Promote As Lead Chassis window is displayed.

2. Click Promote.

After promoting the backup lead as the new lead of the chassis group, If you have the chassis administrator privileges, perform

the following steps before putting the old lead chassis back into the production environment:

1. From the new lead chassis, remove the old lead chassis from the group to remove all references to the old lead chassis.

2. Remove the old lead chassis from the stacking network.

3. Run a forced reset configuration task by using the REST API, /api/ApplicationService/Actions/

ApplicationService.ResetApplication For details, see the OpenManage Enterprise and OpenManage Enterprise -

Modular Edition RESTful API Guide.

The reset configuration task transitions the old chassis to a stand-alone chassis and ready to be part of the production

environment.

When a backup lead is promoted as the lead chassis, join requests from other member chassis sent to the earlier lead chassis,

are not displayed on the MCM dashboard of the new lead. As a result, the particular member chassis cannot send joining

requests to other groups in the stack. To unblock the pending requests, run the following API from the member chassis from

which the joining requests were sent and resend the requests:

URI—/api/ManagementDomainService/Actions/ManagementDomainService.DeletePendingDomains

Method—POST

Payload—empty

Retiring lead chassis

You can use the retirement process of the existing lead chassis to make it a member chassis of the existing group or a stand-

alone chassis.

1. On the MCM dashboard, click Configure > Retire Lead Chassis.

The Retire Lead Chassis window is displayed.

2. Select one of the following options:

● Make it a member of the current group.

● Make it a standalone chassis.

3. Click Retire.

Also, see the section, Use case scenarios.

MCM dashboard

The MCM dashboard is displayed only when a multi-chassis management (MCM) group is created. You can view the name of

MCM group on the left side of the dashboard. Below the group name, you can view the names, IPs, and service tags of the lead

and member chassis. The lead chassis is indicated by the "LEAD" on the right side of the chassis name and the backup chassis is

indicated by "BACKUP".

Click View Topology to view the structure of the MCM group.

Logging in to OME-Modular