When adding ETERNUS disk storage systems to the current ETERNUS environment, change the settings on the Tape Server as follows. This section describes changing the settings when various changes are made.
Create an access path partition for the added ETERNUS disk storage systems.
For details, refer to "Creation of Access Path Partition" in the "ETERNUS SF AdvancedCopy Manager Installation Guide".
Edit the /etc/opt/FJSVswstm/conf/devpath.conf file to add the access path of the added ETERNUS disk storage systems.
For details, refer to "Setting Access Path Definition Files" in the "ETERNUS SF AdvancedCopy Manager Installation and Setup Guide".
Execute "11.4.1 tbochkconf (Tape Server definition file check command)".
When ETERNUS DX60/DX80/DX90, ETERNUS DX400 series, ETERNUS2000, ETERNUS3000, ETERNUS4000 has been added, follow the procedure below in accordance with the type of multi-path driver installed in the Tape Server:
If the ETERNUS multi-path driver is installed
Execute "11.4.13 tbogetoluinfo (ETERNUS DX60/DX80/DX90, ETERNUS DX400 series, ETERNUS2000, ETERNUS3000, ETERNUS4000 information acquisition command)" with the IP address of the added ETERNUS DX60/DX80/DX90, ETERNUS DX400 series, ETERNUS2000, ETERNUS3000, ETERNUS4000.
# /opt/FJSVswstm/bin/tbogetoluinfo -l 200.30.40.30 200.30.40.30 comleted. [total olu = 100] The configuration file of CM information was update. # |
If the GR multi-path driver is installed
Execute "11.4.13 tbogetoluinfo (ETERNUS DX60/DX80/DX90, ETERNUS DX400 series, ETERNUS2000, ETERNUS3000, ETERNUS4000 information acquisition command)" with the IP address of the added ETERNUS DX60/DX80/DX90, ETERNUS DX400 series, ETERNUS2000, ETERNUS3000, ETERNUS4000.
# /opt/FJSVswstm/bin/tbogetoluinfo -l 200.30.40.30 200.30.40.30 completed. [total olu = 100] /var/opt/FJSVmplb/mplb_ext.conf was update. # |
Execute the command below to read information to the GR multi-path driver.
This command need not be executed if the ETERNUS multi-path driver is installed in the Tape Server.
# mplbconfig -q # |
Note
This command should not be executed while the RAID device is processing the migration.