HP 3PAR StoreServ 7400 4-node HP 3PAR-to-3PAR Storage Peer Motion Guide (OS 3. - Page 62

B Additional Steps to Migrate HP-UX Hosts, Rescanning for New LUN Paths, HP-UX 11i V3

Get HP 3PAR StoreServ 7400 4-node PDF manuals and user guides View all HP 3PAR StoreServ 7400 4-node manuals
Add to My Manuals
Save this manual to your list of manuals

Page 62 highlights

B Additional Steps to Migrate HP-UX Hosts Rescanning for New LUN Paths Before continuing with migration, it is recommended that you rescan for new LUN paths and make a note of the new paths to the volumes: # ioscan -fnC disk HP-UX 11i V3 HP-UX 11i v3 standalone and Serviceguard clustered hosts can be migrated by using the online migration procedure. No additional configuration is required on the hosts. HP-UX 11i V2 HP-UX 11iv2 standalone hosts can be migrated by using the online migration procedure. However, after zoning in the destination array to the standalone hosts, the new paths/physical volumes (PVs) must be added to the volume group/PVLinks configuration by using the vgextend command before removing the paths to the source array. For example: # vgextend my_standalone_VG new_pv_path1 new_pv_path2 ... To confirm configuration of the PVLinks configuration, issue the vgdisplay command. A Serviceguard cluster, running on HP-UX 11i V2, can also be migrated by using the online migration procedure, but if shared volume groups that use the Shared Logical Volume Manager (SLVM) are used, then additional configuration steps are required because the shared volume group does not automatically recognize new paths to the volume exported through the destination. Use the following single-node online reconfiguration (SNOR) operation (see "???TITLE???") to change the configuration of a shared volume group, while keeping it active in only a single node. During the volume group reconfiguration, applications on at least one node will be available. Single-node Online Reconfiguration 1. Identify the shared volume group on which a configuration change is required. Call it vg_shared. 2. Identify one node of the cluster which is running an application using the shared volume group. Call it node1. The applications on this node that are using the volume group, vg_shared, will remain unaffected during the procedure. 3. Stop the applications using the shared volume group on all the other cluster nodes, thus scaling down the cluster application to the single cluster node, node1. 4. Deactivate the shared volume group on all other nodes of the cluster, except node1, by issuing the vgchange command -a n option: # vgchange -a n vg_shared 5. Ensure that the volume group, vg_shared, is now active only on a single cluster node, node1, by using the vgdisplay command on all cluster nodes. The Status should show that the volume group is available on a single node only. 6. On node1, change the activation mode to exclusive by issuing the following command: # vgchange -a e -x vg_shared 62 Additional Steps to Migrate HP-UX Hosts

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
B Additional Steps to Migrate HP-UX Hosts
Rescanning for New LUN Paths
Before continuing with migration, it is recommended that you rescan for new LUN paths and make
a note of the new paths to the volumes:
#
ioscan -fnC disk
HP-UX 11i V3
HP-UX 11i v3 standalone and Serviceguard clustered hosts can be migrated by using the online
migration procedure. No additional configuration is required on the hosts.
HP-UX 11i V2
HP-UX 11iv2 standalone hosts can be migrated by using the online migration procedure. However,
after zoning in the destination array to the standalone hosts, the new paths/physical volumes (PVs)
must be added to the volume group/PVLinks configuration by using the
vgextend
command
before removing the paths to the source array. For example:
#
vgextend
my_standalone_VG new_pv_path1
new_pv_path2
…
To confirm configuration of the PVLinks configuration, issue the
vgdisplay
command.
A Serviceguard cluster, running on HP-UX 11i V2, can also be migrated by using the online
migration procedure, but if shared volume groups that use the Shared Logical Volume Manager
(SLVM) are used, then additional configuration steps are required because the shared volume
group does not automatically recognize new paths to the volume exported through the destination.
Use the following single-node online reconfiguration (SNOR) operation (see
“???TITLE???”
) to
change the configuration of a shared volume group, while keeping it active in only a single node.
During the volume group reconfiguration, applications on at least one node will be available.
Single-node Online Reconfiguration
1.
Identify the shared volume group on which a configuration change is required. Call it
vg_shared
.
2.
Identify one node of the cluster which is running an application using the shared volume group.
Call it
node1
. The applications on this node that are using the volume group,
vg_shared
,
will remain unaffected during the procedure.
3.
Stop the applications using the shared volume group on all the other cluster nodes, thus scaling
down the cluster application to the single cluster node,
node1
.
4.
Deactivate the shared volume group on all other nodes of the cluster, except node1, by issuing
the
vgchange
command
-a n
option:
#
vgchange -a n vg_shared
5.
Ensure that the volume group,
vg_shared
, is now active only on a single cluster node, node1,
by using the
vgdisplay
command on all cluster nodes. The
Status
should show that the
volume group is available on a single node only.
6.
On node1, change the activation mode to exclusive by issuing the following command:
#
vgchange -a e -x vg_shared
62
Additional Steps to Migrate HP-UX Hosts