Deployment Guide

Enabling automatic firmware synchronization from active CP to the
standby CP
Starting with Fabric OS 7.3.0, you can enable automatic firmware synchronization from the active CP
blade to the standby CP blade if the following requirements are met.
• The standby CP must be hot-plugged.
• The firmware version in the active CP should be higher than the firmware version in the standby
CP.
• The firmware version in the standby CP should not be Fabric OS 7.0.0 or older.
• The firmware upgrade process in the standby CP must not be currently running or already initiated.
•
To enable firmware auto-synch from active CP to standby CP, use the configureChassis command.
sw0:FID128:root> configurechassis
Configure...
cfgload attributes (yes, y, no, n): [no] y
Enforce secure config Upload/Download (yes, y, no, n): [yes]
Enforce signature validation for firmware (yes, y, no, n): [yes]
Add Suffix to the uploaded file name (yes, y, no, n): [yes]
Do you want to enable auto firmwaresync (yes, y, no, n): [yes] y
The firmware is synced from the primary partition of active CP to the secondary partition of standby CP.
After the sync is completed, the standby CP reboots with auto-commit enabled. The standby CP does
not require external Ethernet connection as the synching of firmware takes place through the backplane
connection between active and standby CP blades. This configuration setting is not included in the
configUpload or configDownload process.
Manually synchronizing the firmware from the active CP to the standby
CP
Starting with Fabric OS 7.3.0, you can use the firmwareSync command to synchronize the firmware
from the active CP to the standby CP. For this command work, you must have the standby CP firmware
version equal to or less than two versions from the firmware version in the active CP. For example, if
the active CP firmware version is Fabric OS 7.3.0, then the standby CP firmware version should be
either Fabric OS 7.1.0 or higher.
sw0:FID128:root> firmwaresync
This command will copy the firmware on the active CP blade to the
Standby CP blade but will require that existing telnet, secure telnet or
SSH sessions to the standby CP blade to be restarted.
This command may take up to 10 minutes.
Do you want to continue (Y/N) [Y]: y
Firmwaresync has started..............................
.
.....Firmwaresync has been completed successfully.
2014/05/06-03:42:21, [SULB-1053], 1461, SLOT 5 | CHASSIS, INFO, Brocade-DCX,
Firmware sync to the secondary partition of standby CP has been completed.
It will perform auto-reboot followed by auto-commit.
Enabling automatic firmware synchronization from active CP to the standby CP
Fabric OS Upgrade Guide 13
53-1003240-01