Storage Manager 7.10 Migration from Storage Manager 6.22 (NT Only) ================================================================== READMEFC File This README file contains the latest information about migrating from Storage Manager 6.22 to Storage Manager 7.10 through the Fibre Media. To migrate through the network, please refer to the READMENW file. Last Update: 06/13/2001 CONTENTS -------- 1.0 Overview 2.0 Change History 3.0 Installation and Setup Instructions 4.0 Setting up NVSRAM and Firmware files 5.0 Running the SetNVSRAM.cmd batch file 6.0 Running the Migrate710.cmd batch file 7.0 Installing NVSRAM Files 8.0 Upgrading Firmware 9.0 Cleaning Up 10.0 Web Sites and Support Phone Number 11.0 Trademarks and Notices 12.0 Disclaimer 1.0 Overview -------------- 1.1 Overview This package enables the migration to the IBM FAStT Fibre Channel Storage Manager version 7.10 from version 6.22 through the Fibre Media. 1.2 Limitations Migration is required for NT system only and for the IBM Netfinity Fibre Channel Controller (3526 at 3.x levels). Windows 2000 requires that the controllers be at 4.x levels. 1.3 Enhancements N/A 1.4 Prerequisites: The following prerequisites must be met prior to starting the migration process: 1.4.1 Host server and management station must be running Windows NT service pack 5 or higher. 1.4.2 Fibre Channel RAID controllers to be migrated must be at bootware 03.01.00.02 and appware 03.01.02.22. 1.4.3 32 LUN support must enabled. (The 'LargeLuns' setting in the registry for the Fibre Channel HBAs must be set to '1' and the 'Luns per target' setting in the ALT-Q FC HBA utility must be set to '0'.) 1.4.4 SYMSM 6.22 must be un-installed before beginning the migration process. Note: Do not un-install 6.22 if you are migrating through the network. To migrate through the Network, refer to the README_NW.txt file in this package for instructions. 1.4.5 You have Administrator privileges on the host machine. 1.4.6 The host machine has at least 10 MB of available disk space and its video monitor is set to a minimum screen resolution of 640x480 pixels and a palette of 256 colors. 1.4.7 The management station has at least 20 MB of available disk space and its video monitor is set to a minimum screen resolution of 800x600 pixels and a palette of 256 colors. 1.4.8 Close all programs. You cannot update the controller if there is an active lock on the logical disk(s). This includes IBM Netfinity Manager, IBM Netfinity Director, Diskeeper, Microsoft(tm) Cluster Server. 1.5 Dependencies: N/A 2.0 Change History -------------------- 06/13/01 - Initial release: IBM FAStT Storage Manager 7.10 Migration from Storage Manager 6.22 (NT Only) 3.0 Installation and Setup Instructions ----------------------------------------- 3.1 IMPORTANT: Read through this document completely BEFORE attempting to perform the migration process. Become familiar with the new features of Storage Manager 7.10. Refer to the IBM FAStT Storage Manager 7.10 Installation and Set-up Guide found on the IBM Support web site (see section 10.0) 3.2 Terms It is important to understand the distinction between the following two terms when reading this document. Management station: System used to manage the storage subsystem. This system does not need to be attached to the storage subsystem through fiber. The Storage Manager Client (SMSYM 6.22 and/or SM7client) will be running on this system. Host/File server: The terms host, host server, and file server will be used interchangeably in this document. Either term refers to a system directly attached through fibre to the storage subsystem. This system is typically used to serve data (normally in the form of files) from the storage subsystem. The system need not run SMSYM 6.22 or SM7client, but must run RDAC and the combination of SM7agent and Microsoft Virtual Machine (MSVM) (once updated). Note that a system may be both a management station and host server at the same time. 3.3 Download 32P0258.exe - "IBM FAStT Storage Manager 7.10 migration from Storage Manager 6.22 (NT only)" package from: http://www-1.ibm.com/support/xseries.html Select Fixes ---> Hardware Drivers, bios and updates... In the Dowloadable Files by Category select Fibre. Note: You may also want to download at this time the IBM FAStT Storage Manager version 7.10. 3.4 Run 32P0258.exe. This is a self extracting file. Choose a directory to extract the files to. Check the "Recreate Directory" box in the PKzip dialog box. This will create the following directory structure under the target extraction directory: Directory of \Temp FIRMWARE Migrate Utilities READMEFC Text File <---- Use this one for Fibre Media READMENW Text File Directory of \Temp\FIRMWARE 03010300.apd 1,462KB APD File 3/1/00 4:50 AM 04010200.bwd 1,025KB BWD File 6/15/01 7:01 AM 04010207.apd 2,806KB APD File 6/4/01 1:52 PM firmware_03010300.dlp 1,982KB DLP File 5/5/00 6:29 AM FW_O4010207_04010200.dlp 3,830KB DLP File 6/4/01 1:49 PM NV3526R710NT003.dl 4KB DL File 3/29/01 6:41 AM NV3526R710NT003.dlp 4KB DLP File 3/29/01 6:41 AM Directory of \Temp\Migrate Utilities nvutil 336KB Application 5/24/99 5:59 PM SM7migrate 1,451KB Application 3/29/01 3:35 PM setnvsram 2KB Windows NT 6/5/01 11:18 AM Command Script Migrate710 6KB Windows NT 6/5/01 11:26 AM Command Script 3.5 Run SM7migrate.exe. The installation folder is C:\SM7migrate07102501. This will create the following directory structure: Directory of C:\SM7migrate07102501: data1.cab 512KB CAB File 3/28/01 4:21 PM data1.hdr 14KB HDR File 3/28/01 4:21 PM data2.cab 436KB CAB File 3/28/01 4:21 PM ikernel.ex_ 329KB EX- File 6/12/00 7:58 PM layout.bin 1KB BIN File 3/28/01 4:21 PM Setup 45KB Application 5/16/00 2:37 PM Setup 1KB Configuration Settings 3/28/01 4:20 PM setup.inx 122KB INX File 3/28/01 4:20 PM 3.6 Installing SM7migrate (Migrating through Fibre Media) Use the following procedure to install SM7migrate on a host machine connected to one or more storage subsystems. SM7migrate is necessary for downloading NVSRAM files and for upgrading controller firmware. 3.6.1 Run C:\SM7migrate07102501\setup.exe. This installs the Migrate Utility. The default install folder is: C:\Program Files\SM7migrate 3.6.2 Select 'Next'. The setup program's Welcome screen appears. 3.6.3 Select 'OK'. The Choose Destination Location window appears. 3.6.4 The default directory is C:\SM7migrate. Select 'Browse' if you want to change the destination location. 3.6.5 Select 'Next' to begin the installation. 3.6.6 When the installation is complete, select 'Finish'. 3.6.7 The content of directory C:\SM7migrate is: Native The content of Native is: Clearlocks 2KB MS-DOS Batch File 3/28/01 4:19 PM help 3KB MS-DOS Batch File 3/28/01 4:19 PM rmparams 4KB File 6/14/01 1:24 PM SM7migrate 335KB Application 3/28/01 4:19 PM SM7migrate 2KB Text Document 3/28/01 4:19 PM 4.0 Setting up NVSRAM and Firmware files ---------------------------------------- If you are upgrading previously installed storage subsystems for management with IBM FAStT Storage Manager 7.10, you must use SM7migrate to download a default NVSRAM file. The default settings enable the network bit and the bit for creation of an Access Volume. 4.1 Copy the NV3526R710NT003.dlp file from the \Temp\firmware directory to the \Program Files\SM7migrate\native directory. 4.2 Copy the firmware_03010300.dlp file from the \temp\FIRMWARE to the \Program Files\SM7migrate\native directory. 4.3 Copy the FW_04010207_04010200.dlp file from the \temp\FIRMWARE directory to the \Program Files\SM7migrate\native directory. 4.4 Copy the migrate710.cmd batch file from the \temp\Migrate Utilities directory to the \Program Files\SM7migrate\native directory 4.5 Copy the NVutil.exe file to the \Program Files\SM7migrate\native directory 4.6 Copy the SetNVSRAM.cmd batch file to the \Program Files\SM7migrate\native directory 5.0 Running the SetNVSRAM.cmd batch file ---------------------------------------- Before you attempt to upgrade the NVSRAM, the storage subsystem(s) need to be set to report all LUNs (the older version of the NVSRAM limited the storage subsystem to only reporting eight LUNs each). 5.1 Run the SetNVSRAM batch file to prepare the storage subsystem(s). This needs to be performed for each storage subsystem on which the NVSRAM will be updated. IMPORTANT: Do not skip this step. If it is not performed prior to upgrading the NVSRAM, the NVSRAM update could fail. Note: The batch file performs the following steps: nvutil -o 34=30 - This will set offset 34 in the NVSRAM to 30 so that the storage subsystem reports all LUNs. nvutil -o 34 - This will read back the setting of offset 34 in the NVSRAM of the storage subsystem. This should show '30'. 5.2 Shutdown the host system (power down) 5.3 Power cycle the Storage Raid Controllers 5.4 Power up the Host System 5.5 To confirm that you are ready to proceed with upgrading the NVSRAM, select Start --> Settings --> Control Panel --> SCSI Adapters applet and count the number of devices shown for the FC HBAs which are attached to the RAID controllers in the storage subsystems. There should be 32 devices shown for each RAID controller that each FC HBA can communicate with. 6.0 Running the Migrate710.cmd batch file ----------------------------------------- To facilitate the installation of the NVRAMs and Firmware files, a batch file has been developed. When this file is executed, sections 7 and 8 are performed automatically. The batch file steps that correlate to the manual actions are shown next to the commands in these sections. It is highly recommended that the Migrate710.cmd batch file be used. 7.0 Installing NVSRAM Files --------------------------- 7.1 From a command prompt, change to the \Program Files\SM7migrate\native directory. 7.2 Type: SM7migrate NV3526R710NT003.dlp (batch file steps 1 and 2) The software displays information on each RAID Module (storage subsystem) connected to the host machine on which you are running SM7migrate. For example, you might see: 1) JASON_001: Drive0 Drive8 2) MAGGIE_01: Drive16 Drive32 3) FRED_001: Drive1 Drive9 NOTE: The first part of the displayed information refers to the RAID Module name (for example, JASON_001). The second part of the displayed information refers to the controllers in the RAID Module (for example, Drive0 Drive8). The software displays the following options: Make Selection: (A)ll Modules, E(x)it, or Module Index Number 7.3 Type a number corresponding to one of the Module Index Numbers. IMPORTANT: Do not type 'a' to update all modules, this may result in the NVSRAM not being updated properly on all storage subsystems. - 'Download to controller Drive was successful.' is displayed. 7.4 Run the ClearLocks.bat script located in the \SM7migrate\native directory to clean up unnecessary files generated by the firmware migration. 7.5 Repeat steps 7.2-7.4 above, making sure that the same Module Index Number is entered as before to update the NVSRAM on the storage subsystem twice. Note: This is batch file step 2 IMPORTANT: This second update of the NVSRAM must be performed due to a timing window that exists that may prevent the NVSRAM from being updated properly the first time. The second update ensures that the NVSRAM is updated correctly. IMPORTANT: If 'Download to controller Drive was successful' is not displayed, stop the migration process at this point and contact your IBM service representative. 7.6 Repeat steps 7.2-7.5 above for each storage subsystem that you wish to manage with the IBM FAStT Storage Manager 7.10. 8.0 Upgrading Firmware ---------------------- IBM FAStT Storage Manager 7.10 only manages storage subsystems with controllers using firmware version 4.x. If you want to manage your controllers with IBM FAStT Storage Manager 7.10, use SM7migrate to upgrade the firmware on those controllers from version 3.x to version 4.x. Depending on the version of the firmware currently installed on the controllers, this might be a two-part process: - Upgrading from version 3.x to 3.1.3 (the "stepping stone" for upgrade to version 4.x) - Upgrading from version 3.1.3 to version 4.x 8.1 Upgrading from Version 3.x to Version 3.1.3 Use the following procedure to use the SM7migrate utility to upgrade controller firmware from version 3.x to version 3.1.3. (This is the "stepping stone" for upgrading to version 4.x.) CAUTION: Do not use SM7migrate to upgrade firmware directly from version 3.x to version 4.x because you might loose communication with the controllers in the storage subsystem. 8.1.1 From a command prompt, change to the \Program Files\SM7migrate\native directory. 8.1.2 Type: SM7migrate firmware_03010300.dlp (batch file step 3) The software displays information on each RAID Module (storage subsystem) connected to the host machine on which you are running SM7migrate. For example, you might see: 1) JASON_001: Drive0 Drive8 2) MAGGIE_01: Drive16 Drive32 3) FRED_001: Drive1 Drive9 NOTE: The first part of the displayed information refers to the RAID Module name (for example, JASON_001). The second part of the displayed information refers to the controllers in the RAID Module (for example,Drive0 Drive8). 8.1.3 The software displays the following options: Make Selection: (A)ll Modules, E(x)it, or Module Index Number Type a number corresponding to one of the Module Index Numbers. IMPORTANT: Do not type 'a' to update all modules, this may result in the NVSRAM not being updated properly on all storage subsystems. - 'Download to controller Drive was successful.' is displayed. IMPORTANT: If you receive an error message that the filename you typed is not a downloadable file, check to make sure that the .dlp file is in the \Program Files\SM7migrate\native directory. If you placed the file in another directory, move it to the \Program Files\SM7migrate\native directory and try the migration procedure again. IMPORTANT: If 'Download successful' is not displayed, stop the migration process at this point and contact your IBM service representative. 8.1.4 Run the ClearLocks script located in the \SM7migrate\native directory to clean up unnecessary files generated by the firmware migration. 8.1.5 Repeat steps 8.1.2-8.1.4 above for each storage subsystem that you wish to manage with the IBM FAStT Storage Manager 7.10. 8.2 Upgrading from Version 3.1.3 to Version 4.x Use the following procedure to use the SM7migrate utility to upgrade controller firmware from version 3.1.3 to version 4.x. 8.2.1 From a command prompt, change to the \Program Files\SM7migrate\native directory. 8.2.2 Type: SM7migrate FW_04010207_04010200.dlp (batch file step 4) The software displays information on each RAID Module (storage subsystem) connected to the host machine on which you are running SM7migrate. For example, you might see: 1) JASON_001: Drive0 Drive8 2) MAGGIE_01: Drive16 Drive32 3) FRED_001: Drive1 Drive9 NOTE: The first part of the displayed information refers to the RAID Module name (for example, JASON_001). The second part of the displayed information refers to the controllers in the RAID Module (for example, Drive0 Drive8). 8.2.3 The software displays the following options: Make Selection: (A)ll Modules, E(x)it, or Module Index Number Type a number corresponding to one of the Module Index Numbers. IMPORTANT: Do not type 'a' to update all modules, this may result in the NVSRAM not being updated properly on all storage subsystems. - 'Download to controller Drive was successful.' is displayed. IMPORTANT: If you receive an error message that the filename you typed is not a downloadable file, check to make sure that the .dlp file is in the \Program Files\SM7migrate\native directory. If you placed the file in another directory, move it to the \Program Files\SM7migrate\native directory and try the migration procedure again. IMPORTANT: If 'Download to controller Drive was successful' is not displayed, stop the migration process at this point and contact your IBM service representative. 8.2.4 Run the ClearLocks script located in the \SM7migrate\native directory to clean up unnecessary files generated by the firmware migration. 8.2.5 Repeat steps 8.2.2-8.2.4 above for each storage subsystem that you wish to manage with IBM FAStT Storage Manager 7.10 8.2.6 Reboot the system 9.0 Cleaning Up --------------- 9.1 Uninstall SM7migrate. 9.2 At this point the migration is complete. 9.3 You may now install the IBM FAStT Storage Manager 7.10. 10.0 WEB Sites and Support Phone Number ---------------------------------------- 10.1 IBM Support Web Site: http://www.ibm.com/pc/support 10.2 IBM eServer xSeries Marketing Web Site: http://www.ibm.com/pc/us/eserver/xseries/index.html 10.3 If you have any questions about this update, or problem applying the update go to the following Help Center World Telephone Numbers URL: http://www.ibm.com/planetwide 11.0 Trademarks and Notices ----------------------------- 11.1 The following terms are trademarks of the IBM Corporation in the United States or other countries or both: IBM Microsoft, Windows, and Windows 2000 are trademarks of Microsoft Corporation in the United States, other countries, or both. Other company, product, and service names may be trademarks or service marks of others. 12.0 Disclaimer ----------------- 12.1 THIS DOCUMENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. IBM DISCLAIMS ALL WARRANTIES, WHETHER EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE AND MERCHANTABILITY WITH RESPECT TO THE INFORMATION IN THIS DOCUMENT. BY FURNISHING THIS DOCUMENT, IBM GRANTS NO LICENSES TO ANY PATENTS OR COPYRIGHTS. 12.2 Note to U.S. Government Users -- Documentation related to restricted rights -- Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corporation.