MX7000 Firmware Update Dell EMC Technical White Paper
Revisions Revisions Date Description Jan 2019 Initial release Acknowledgements This paper was produced by the following members of the Dell EMC storage engineering team: Author: Dahir Herzi, Anoop Alladi, Zoheb Khan and Murali Anumolu 2 MX7000 Firmware Update | Document ID
Table of contents Table of contents Revisions.............................................................................................................................................................................2 Acknowledgements .............................................................................................................................................................2 Introduction ......................................................................................................
Introduction Introduction The Purpose of this white paper is to describe the new and improved features for the firmware update workflow. This technical white paper describes the following features: • • • • • • Catalog Management Baseline Report and Compliance Summary Firmware update using the Compliance report DUP based update.
Catalog Management - Also an option to select a validated stack Catalog which is the NGM Catalog that contains only the MX7000 bundles. Finally there is an option for a Network path for location of a custom Catalog. MX7000 Catalog creation wizard Select one of the following Catalog sources: • Newest validated stacks of chassis firmware on Dell.com —this is the Catalog that contains latest validated bundle of the Dell EMC 14G MX7000 chassis. Latest component firmware versions on Dell.
Baseline Report and Compliance Summary Password This option is available only if the Share Type is CIFS or HTTPS. The password can have a maximum length of 255 characters. Certificate Check Select the check box to check the security certificate authentication.
How a baseline report is generated: • Under Configuration->Firmware, click Create baseline. In the popup, select a Catalog, Baseline report name, description and Devices/Groups that needs to be part of this baseline report.
Firmware update using the Compliance report MX7000 Baselines • Click on View report to view the Device level compliance report and also the software component compliance report for the device. This report provide the list of all the updatable components. MX7000 Baseline report Firmware update using the Compliance report Once the compliance report is generated, User can view the Device level compliance details and also Component level details.
DUP Based update MX7000 Update scheduler DUP Based update This feature allows user to manually choose a DUP (Dell Update Package) from local directory to be applied to the chassis components or device in the chassis. Before applying the DUP is validated for compliance and signature. A DUP level report is displayed, information on the version being applied and details on criticality of the DUP plus the devices that require an update. Below are the steps for DUP based updates.
Rollback Firmware MX7000 Target selection • Select the devices and click next to schedule the firmware update job. Rollback Firmware The Rollback Firmware window enables you to roll back a firmware update to the previous version. If the user is unhappy with a recent firmware update, they can request a rollback of the firmware to the previous version prior to the update. The rollback is enabled if MSM has access to the firmware package corresponding to the previous version.
Firmware update for NWIOM MX7000 IOM in Full Switch Mode MX7000 IOM in IOM in Full Switch Mode update IOM Upgrade for the Fabric Mode IOM: MX7000 IOM in Fabric Mode 11 MX7000 Firmware Update | Document ID
Firmware update for SAS IOM and Storage MX7000 Fabric Mode IOM upgrade status update Firmware update for SAS IOM and Storage MSM supports the Firmware update of SAS IOM (Dell EMC PowerEdge MX5000s) and Storage (Dell EMC PowerEdge MX5016s) devices by using either Compliance report or DUP based update. Based on the pre-requisite information of the firmware update it is required to power off the compute sleds which has storage assignments before triggering the firmware update.
