Fabric OS 5.2.x administrator guide 395
14.
Change to /dev and untar the file that was tared in step 4. For example:
tar –xf /tmp/jbod.tar
Import the volume groups using vgimport. The proper usage would be
vgimport –m <mapfile> <path_to_volume_group> <physical_volume_path>.
For example:
vgimport –m /tmp/jbod_map /dev/jbod /dev/dsk/c64t8d0 /dev/dsk/c64t9d0
15.
Activate the volume groups using vgchange. The proper usage would be
vgchange –a y
<path_to_volume_group>
. For example:
vgexport –a y /dev/jbod
16.
If you are not using multipathing software, mount all devices again and restart I/O. For example:
mount /mnt/jbod
17.
If you are using multipathing software, re-enable the affected path. The preceding steps do not “clean
up” the results from ioscan. When viewing the output of ioscan, notice the that the original entry is still
there, but now has a status of NO_HW.
18.
To remove the original (outdated) entry, the command rmsf (remove special file) will be needed. The
proper usage for this command would be
rmsf –a –v <path_to_device>
. For example:
rmsf –a –v /dev/dsk/c65t8d0
19.
Validate that the entry has been removed by using the command
ioscan –funC disk
. In this
example, the NO_HW entry is no longer listed:
20.
Repeat for all fabrics.
21.
Issue the
switchEnable
command. Enable the core switches first, then the edges.
AIX procedure
This procedure is not intended to be comprehensive. It provides a starting point from which a SAN
administrator can develop a site-specific procedure for a device that binds automatically by PID, and
cannot be rebooted due to uptime requirements.
1.
Backup all data. Verify backups.
2.
If you are not using multipathing software, stop all I/O going to all volumes connected through the
switch or fabric to be updated.
3.
If you are not using multipathing software, varyoff the volume groups. The command usage is
varyoffvg <volume_group_name>
. For example:
varyoffvg datavg
# ioscan -funC disk
Class
I
H/W Path
Driver S/W State
H/W Type
Description
-------------------------------------------------------------------------------------
disk
0
0/0/1/1.2.0
adisk CLAIMED
DEVICE
SEAGATE ST39204LC
/dev/dsk/clt2d0 /dev/rdsk/c1t2d0
disk
1
0/0/2/1.2.0
adisk CLAIMED
DEVICE
HP
DVD-ROM 304
/dev/dsk/c3t2d0 /dev/rdsk/c3t2d0
disk
319 0/4/0/0.1.2.255.14.8.0
adisk CLAIMED
DEVICE
SEAGATE ST336605FC
/dev/dsk/c64t8d0 /dev/rdsk/c64t8d0
disk
320 0/4/0/0.1.18.255.14.8.0
adisk NO_HW
DEVICE
SEAGATE ST336605FC
/dev/dsk/c65t8d0 /dev/rdsk/c65t8d0
het46 (HP-50001)> ioscan -funC disk
Class
I
H/W Path
Driver S/W State
H/W Type
Description
-------------------------------------------------------------------------------------
disk
0
0/0/1/1.2.0
adisk CLAIMED
DEVICE
SEAGATE ST39204LC
/dev/dsk/clt2d0 /dev/rdsk/c1t2d0
disk
1
0/0/2/1.2.0
adisk CLAIMED
DEVICE
HP
DVD-ROM 304
/dev/dsk/c3t2d0 /dev/rdsk/c3t2d0
disk
319 0/4/0/0.1.2.255.14.8.0
adisk CLAIMED
DEVICE
SEAGATE ST336605FC
/dev/dsk/c64t8d0 /dev/rdsk/c64t8d0
Содержание AE370A - Brocade 4Gb SAN Switch 4/12
Страница 1: ...HP StorageWorks Fabric OS 5 2 x administrator guide Part number 5697 0014 Fifth edition May 2009 ...
Страница 18: ...18 ...
Страница 82: ...82 Managing user accounts ...
Страница 102: ...102 Configuring standard security features ...
Страница 126: ...126 Maintaining configurations ...
Страница 198: ...198 Routing traffic ...
Страница 238: ...238 Using the FC FC routing service ...
Страница 260: ...260 Administering FICON fabrics ...
Страница 280: ...280 Working with diagnostic features ...
Страница 332: ...332 Administering Extended Fabrics ...
Страница 414: ...398 Configuring the PID format ...
Страница 420: ...404 Configuring interoperability mode ...
Страница 426: ...410 Understanding legacy password behaviour ...
Страница 442: ...426 ...
Страница 444: ......
Страница 447: ......