Service Manual

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

You can use the firmwareSync command to synchronize the firmware from the active CP to the

standby CP. If you have Fabric OS 7.4.0 or later in the active CP, the standby CP firmware version

can be any older or newer version.

sw0:FID128:admin> 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.

Manually synchronizing the firmware from the active CP to the standby CP

24 Fabric OS Upgrade Guide

53-1003515-01