HP StorageWorks Modular Smart Array 1000 HP StorageWorks 1000/1500 Modular Sma - Page 15

Troubleshooting, Restart all I/O to the MSA storage LUNs.

Page 15 highlights

Step Description (continued) Check 13 If using LVM PVLinks, add an alternate link to each physical volume in the volume F group. For example (using the example information from the ioscan in step 11): • To add an alternate link to /dev/dsk/c6t0d0, enter: vgextend /dev/vg06 /dev/dsk/c22t0d0 • To add an alternate link to /dev/dsk/c6t0d1, enter: vgextend /dev/vg06 /dev/dsk/c22t0d1 • To add an alternate link to /dev/dsk/c6t0d2, enter: vgextend /dev/vg06 /dev/dsk/c22t0d2 14 Ensure that the preferred path in the MSA for the LUNs is the same as the primary F PVLinks path. • In PVLinks, use the following command: vgdisplay -v /dev/ • In the MSA CLI, use the following command: show preferred_path • If the preferred path of the MSA LUNs is not the same as the PVLinks primary path, change the MSA path. In the MSA CLI, use the following command: set preferred_path 15 For the servers that were quiesced during the migration process, do the following from the server console: a. Reactivate all LVM volume groups on the MSA. b. Remount the file systems. c. Restart all I/O to the MSA storage LUNs. d. Restart all applications accessing the MSA. Troubleshooting To display and verify the status of a volume group, from the server console, enter: vgdisplay -v /dev/ To activate a volume group, from the server console, enter: vgchange -a y /dev/ To verify that device filenames and hardware paths did not change, from the server console, enter: ioscan -fnC disk To verify that the connection type is properly set for all HP-UX HBAs (profile=hp), from the MSA CLI, enter: show connections To verify that hard addressing has been set on direct-connect MSA controllers, from the MSA CLI, enter: show this_controller_hard_address To verify that access is granted to the LUNs on each MSA array controller, from the MSA CLI, enter: show acl Migrating from an active/passive single controller to active/active dual controllers in HP-UX environments 15

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16

Migrating from an active/passive single controller to active/active dual controllers in HP-UX environments
15
Troubleshooting
To display and verify the status of a volume group, from the server console, enter:
vgdisplay -v /dev/<
vg_name
>
To activate a volume group, from the server console, enter:
vgchange -a y /dev/<
vg_name
>
To verify that device filenames and hardware paths did not change, from the server console, enter:
ioscan -fnC disk
To verify that the connection type is properly set for all HP-UX HBAs (profile=hp), from the MSA CLI, enter:
show connections
To verify that hard addressing has been set on direct-connect MSA controllers, from the MSA CLI, enter:
show this_controller_hard_address
To verify that access is granted to the LUNs on each MSA array controller, from the MSA CLI, enter:
show acl
13
If using LVM PVLinks, add an alternate link to each physical volume in the volume
group.
For example (using the example information from the
ioscan
in step 11):
To add an alternate link to
/dev/dsk/c6t0d0
, enter:
vgextend /dev/vg06 /dev/dsk/c22t0d0
To add an alternate link to
/dev/dsk/c6t0d1
, enter:
vgextend /dev/vg06 /dev/dsk/c22t0d1
To add an alternate link to
/dev/dsk/c6t0d2
, enter:
vgextend /dev/vg06 /dev/dsk/c22t0d2
14
Ensure that the preferred path in the MSA for the LUNs is the same as the primary
PVLinks path.
In PVLinks, use the following command:
vgdisplay -v /dev/
<vg_name>
In the MSA CLI, use the following command:
show preferred_path
<controller_name>
If the preferred path of the MSA LUNs is not the same as the PVLinks primary path,
change the MSA path. In the MSA CLI, use the following command:
set preferred_path
<controller_name>
<
unit_list
>
15
For the servers that were quiesced during the migration process, do the following from
the server console:
a.
Reactivate all LVM volume groups on the MSA.
b.
Remount the file systems.
c.
Restart all I/O to the MSA storage LUNs.
d.
Restart all applications accessing the MSA.
Step
Description
(continued)
Check