When a previous version level of the ETERNUS SF Storage Cruiser Manager has been installed, you can save the setting data and have the current version of ETERNUS SF Storage Cruiser Manager inherit the saved data.
This section explains how to upgrade from a previous version level of the ETERNUS SF Storage Cruiser.
Note
Before migration, refer to "Chapter 3 Restrictions and advisory notes " for confirmation.
From ETENRUS SF Storage Cruiser 14.2, the snmptrapd that is included in the OS standard net-snmp package is used for fault monitoring. Therefore, this product does not require the ServerView trap distributor program(SMAWtrpsv) that was used for the ServerView AlarmService.
If no products that require the ServerView trap distributor program(SMAWtrpsv) are installed, delete it because it is not needed.
The following products do require the ServerView trap transfer program:
All versions of Systemwalker Centric Manager
ServerView Resource Coordinator VE V2.1.1 to V2.1.3
When a version of 14.1 or earlier of ETERNUS SF Storage Cruiser Manager is uninstalled from environments in which the following product is installed, FJSVswstt will be uninstalled. After ETERNUS SF Storage Cruiser Manager has been uninstalled, refer to the manual of the following product, and reinstall SystemWalker MpWksttr.
ServerView Resource Coordinator VE 2.1.1 to 2.1.3
Back up the setting data of the previous version level of ETERNUS SF Storage Cruiser Manager.
See
Refer to "9.1.1.2.3 Backup of Linux Manager" in the ETERNUS SF Storage Cruiser User's Guide, for how to perform backup.
Uninstall the previous version level of ETERNUS SF Storage Cruiser Manager.
See
Refer to "9.2 [Linux] Manager uninstallation" in the ETERNUS SF Storage Cruiser Install Guide for the previous version level, for how to uninstall the Manager.
Reinstall FJSVswstt if necessary.
See
For details on the method used, refer to the manual of the following product:
ServerView Resource Coordinator VE 2.1.1 to 2.1.3
Install the ETERNUS SF Storage Cruiser Manager.
See
Refer to "4.2 [Linux] Manager", for how to install and set up the Manager.
Restore the backup data created by step 1 (the setting data of the previous version level of ETERNUS SF Storage Cruiser Manager).
See
Refer to "9.1.1.3.3 Restoring Linux Manager" in the ETERNUS SF Storage Cruiser User's Guide, for how to restore.
Set the fibre channel switch SNMP-MIB setting.
If the performance management function is used for devices that match the conditions in the table below, before the Manager is started, set the SNMP-MIB settings for the relevant device as indicated in "4.2.1.1 Settings" in the ETERNUS SF Storage Cruiser User's Guide.
Device | SNMP-MIB setting |
|---|---|
ETERNUS SN200 model 340 | If No is set for the setting concerning HA-MIB use |
ETERNUS SN200 model 540 | If No is set for the setting concerning HA-MIB use |
Brocade DCX | If No is set for the setting concerning HA-MIB use |
Brocade DCX-4S | If No is set for the setting concerning HA-MIB use |
Update the configuration information of the performance management function.
When the performance management function is used for ETERNUS DX80 S2/DX90 S2, ETERNUS DX400/DX400 S2 series, ETERNUS DX8000 series, ETERNUS4000 (except for models 80 and 100), or ETERNUS DX8000, start the Manager, then update the configuration information of those devices by referring to "7.2.11 Updating configuration information" in the ETERNUS SF Storage Cruiser User's Guide.
When the performance management function is used for ETERNUS DX60, DX80/DX80 S2, DX90/DX90 S2, ETERNUS DX400/DX400 S2 series, ETERNUS DX8000 series, ETERNUS2000, ETERNUS4000 (except models 80 and 100) and ETERNUS8000, start the Manager, then update the configuration information of those devices by referring to "7.2.11 Updating configuration information" in the ETERNUS SF Storage Cruiser User's Guide.
When the performance management function is used for an ETERNUS DX60, DX80/DX80 S2, DX90 S2, ETERNUS DX400/DX400 S2 series, ETERNUS DX8000 series, ETERNUS4000 models 400 or 600, or ETERNUS8000 models 800, 1200, or 2200 where an iSCSI-CA or iSCSI-RA port is installed, start the Manager, then update the configuration information of those devices by referring to "7.2.11 Updating configuration information" in the ETERNUS SF Storage Cruiser User's Guide.
When the performance management function is used for devices that meet the following conditions, start the Manager, then update the configuration information of those devices by referring to "7.2.11 Updating configuration information" in the ETERNUS SF Storage Cruiser User's Guide.
Storage device | Firmware version |
|---|---|
ETERNUS4000 (except models 80 and 100) | V11L40 or later |
There is no need to update the configuration information.
Back up the setting data of the previous version level of ETERNUS SF Storage Cruiser Manager.
See
Refer to "9.1.1.2.4 Backup of Linux Manager (cluster environment)" in the ETERNUS SF Storage Cruiser User's Guide, for how to perform backup.
Uninstall the previous version level of ETERNUS SF Storage Cruiser Manager.
See
Refer to "Appendix A High-availability admin servers" in the ETERNUS SF Storage Cruiser Install Guide for the previous version level, for how to uninstall the Manager.
Reinstall FJSVswstt if necessary.
See
For details on the method used, refer to the manual of the following product:
ServerView Resource Coordinator VE 2.1.1 to 2.1.3
Install the ETERNUS SF Storage Cruiser Manager.
See
Refer to "Appendix A High-availability admin servers", for how to install and set up the Manager.
Restore the backup data created by the step 1 (the setting data of the previous version level of ETERNUS SF Storage Cruiser Manager).
See
Refer to "9.1.1.3.4 Restoring Linux Manager (cluster environment)" in the ETERNUS SF Storage Cruiser User's Guide, for how to restore.
Set the fibre channel switch SNMP-MIB setting.
If the performance management function is used for devices that match the conditions in the table below, before the Manager is started, set the SNMP-MIB settings for the relevant device as indicated in "4.2.1.1 Settings" in the ETERNUS SF Storage Cruiser User's Guide.
Device | SNMP-MIB setting |
|---|---|
ETERNUS SN200 model 340 | If No is set for the setting concerning HA-MIB use |
ETERNUS SN200 model 540 | If No is set for the setting concerning HA-MIB use |
Brocade DCX | If No is set for the setting concerning HA-MIB use |
Brocade DCX-4S | If No is set for the setting concerning HA-MIB use |
Update the configuration information of the performance management function.
When the performance management function is used for ETERNUS DX80 S2/DX90 S2, ETERNUS DX400/DX400 S2 series, ETERNUS DX8000 series, ETERNUS4000 (except for models 80 and 100), or ETERNUS DX8000, start the Manager, then update the configuration information of those devices by referring to "7.2.11 Updating configuration information" in the ETERNUS SF Storage Cruiser User's Guide.
When the performance management function is used for ETERNUS DX60, DX80/DX80 S2, DX90/DX90 S2, ETERNUS DX400/DX400 S2 series, ETERNUS DX8000 series, ETERNUS2000, ETERNUS4000 (except models 80 and 100) and ETERNUS8000, start the Manager, then update the configuration information of those devices by referring to "7.2.11 Updating configuration information" in the ETERNUS SF Storage Cruiser User's Guide.
When the performance management function is used for an ETERNUS DX60, DX80/DX80 S2, DX90 S2, ETERNUS DX400/DX400 S2 series, ETERNUS DX8000 series, ETERNUS4000 models 400 or 600, or ETERNUS8000 models 800, 1200, or 2200 where an iSCSI-CA or iSCSI-RA port is installed, start the Manager, then update the configuration information of those devices by referring to "7.2.11 Updating configuration information" in the ETERNUS SF Storage Cruiser User's Guide.
When the performance management function is used for devices that meet the following conditions, start the Manager, then update the configuration information of those devices by referring to "7.2.11 Updating configuration information" in the ETERNUS SF Storage Cruiser User's Guide.
Storage device | Firmware version |
|---|---|
ETERNUS4000 (except models 80 and 100) | V11L40 or later |
There is no need to update the configuration information.
