Users Guide

A list of all the available chassis is displayed.
b. In the list header, select the checkbox to select all the chassis on the current page. If there are multiple pages, then go to
each page and select the checkbox.
c. After all the chassis are selected, click Update Firmware.
d. In the pop-up wizard, select the individual package and click Browse to select the OpenManage Enterprise Modular
1.10.10 DUP.
e. After the DUP is uploaded, click Next and select the Compliance checkbox.
f. Click Finish to start the update on all chassis.
g. Allow the job to complete and the device communication in the MCM group to be reestablished.
h. Log in to OME-Modular and on the MCM dashboard, confirm that all member chassis in the group are available.
i. From the OME-Modular web interface of the lead chassis, go to the Overview page of all the member chassis and
confirm that the graphics of the chassis and chassis sub systems load.
j. Go the Alerts > Alert Log page and check if an alert storm is in-progress.
An alert storm is referred to several alerts generated per second. If an alert stop is in-progress, wait for it to stop.
k. Continue with updating the other OME-Modular firmware.
4. If the current version is 1.10.00 or 1.10.10:
a. Click Devices > Chassis.
A list of all the available chassis is displayed.
b. In the list header, select the checkbox to select all the chassis on the current page. If there are multiple pages, then go to
each page and select the checkbox.
c. After all the chassis are selected, click Update Firmware.
d. In the pop-up wizard, select the individual package and click Browse to select the OpenManage Enterprise Modular
1.10.20 DUP.
NOTE: MX9116n and/or MX5108n version 10.5.0.3 IOMs may reboot when OME-Modular is upgraded.
e. After the DUP is uploaded, click Next and select the Compliance checkbox.
f. Click Finish to start the update on all chassis.
g. Allow the job to complete.
Recovering failed Management Module firmware update process
If the firmware update of a management module (MM) fails, perform the following steps:
1. Perform a failover on the MM. If the failover fails, go to step 2.
2. Reset the active MM manually.
3. After the failover or reset is complete, check the firmware version to verify if the active MM is running the same or a later
version of OME-Modular, as the standby MM. If not, perform a reset on the MM to force failover.
4. Retry the firmware update.
Updating Fabric Switching Engine and Ethernet Switch
Gather following information required to run the updates.
NOTE: For the network switch versions 10.4.0.R3S and 10.4.0.R4S, skip steps 1 and 2 and go to step 3.
1. Identify and note down the Switch SERVICE-TAG and its ROLE in the smart fabric cluster by running the command, show
smartfabric cluster, on the Switch CLI.
Run this command on all the Switches in a single chassis or chassis group.
Sample output from a Chassis-group Member:
IOM# show smartfabric cluster
----------------------------------------------------------
CLUSTER DOMAIN ID : 159
VIP : fde1:53ba:e9a0:de14:0:5eff:fe00:1159
ROLE : BACKUP
SERVICE-TAG : MXWV011
MASTER-IPV4 : 100.69.101.170
PREFERRED-MASTER :
Updating the management module firmware
15