## Problem Description:

When downgrading SANbox2 firmware from 1.4.xx to 1.3.xx, all configuration data is lost. Additionally, the switch heartbeat LED has a 4-blink code.

## Cause:

When migrating from 1.3 to 1.4 firmware, the configuration area in flash is converted automatically to a "journaling" type filesystem. Any configuration data is automatically saved and restored when the filesystem is recreated. The operation is transparent to the user.

However, when migrating from 1.4 to 1.3, the 1.3 code doesn't have knowledge about the 1.4 filesystem type. The filesystem is recreated as an EXT-2 filesystem and all configuration data is destroyed. The switch will display a 4 blink code on the heartbeat LED and an alarm will be generated prompting the user to restore a configuration.

## Solution:

Backup and restore the configuration prior to downgrading. If you have already downgraded, the configuration is lost, but the 4-blink heartbeat can be reset.

### To Backup and Restore via SANbox Manager:

Prior to migrating from 1.4 to 1.3 perform the following SANbox Manager operations:

From the Faceplate display for the target switch, select the Switch->Archive menu option. In the file dialog, select a file in which to save the switch configuration information and click Save.

You can then migrate from 1.4 back to 1.3.

To restore the previous configuration, add a new fabric at the switch's default IP address 10.0.0.1 and wait for the switch to be discovered. From the switch Faceplate display, select the Switch->Restore menu option. In the Restore dialog, enter the name of the file in which the switch's configuration was restored, or click Browse to locate the file, then click Restore.

NOTE: This procedure will not clear the 4-blink code which results from downgrading from 1.4 to 1.3. This procedure must be done manually. (See below.)

### To Backup and Restore via Telnet:

Prior to migrating from 1.4 to 1.3 perform the following telnet command:

    SANbox2 #>admin start
    SANbox2 #>config backup

Then ftp to the switch as user/password `images/images` and type the following FTPcommands:

    ftp>binary
    ftp>get configdata
    ftp>quit

You can then migrate from 1.4 back to 1.3. When the 4 blink code appears, ftp to the switch as user/password images/images and type the following:

    ftp>binary
    ftp>put configdata
    ftp>quit

This will clear the 4-blink code. Then telnet to the switch and type the following telnet commands:

    SANbox2 #>admin start
    SANbox2 #>config restore

The old switch configuration will then be restored in the 1.3 firmware. This procedure is necessary every time you migrate from 1.4 to 1.3.

### To Reset the 4-blink Code without a Backup to Restore:

NOTE: If you haven't created a backup configuration file, you can get rid of the 4-blink code by executing the following telnet commands:

    SANbox2 #>admin start
    SANbox2 #>config backup
    SANbox2 #>config restore

However, all previous switch configuration is lost so the switch will need to be reconfigured manually.

### To Correct the `DiagnosticStatus` Problem Report:

If you start a clish session after the switch reboots, the switch `DiagnosticStatus` may show Data Services has Problem servicing request. The reason this occurs is because POST is not run on a switch reset, and the attribute is not set in Data Services, causing the error message. To resolve this, the switch must be power cycled to force another POST. Then the `DiagnosticStatus` will show Passed.