Removing External Identity and Geometry following Federated Live

Migration
Done

Overview
Perform the following steps to fail back during Federated Live Migration (FLM) on a GPFS
cluster or stand-alone AIX application host with Native MPIO.
! Warning: These steps pertain only to the specified host and multipath driver used in
this procedure. Do not use these steps for a different host or multipath driver!
This procedure is based on content from the following EMC technical documentation:

EMC Solutions Enabler Symmetrix Migration CLI 7.6 Product Guide

EMC Solutions Enabler Symmetrix Array Management CLI 7.6 Product Guide
EMC Solutions Enabler Symmetrix Array Controls CLI 7.6 Product Guide
EMC Federated Live Migration Technical Overview Technical Notes

These documents can be obtained from EMC Online Support at:

http://support.EMC.com

1.

Shut down all host applications on the application server with a

dependency on the VMAX FLM target devices presenting device source
external identity
From the application host:

All I/O to the VMAX FLM target devices must be halted because these devices will be removed
to facilitate the removal of the source device external identity.
NOTE: Any host remediation to support VMAX connectivity should be performed before VMAX
devices are presented to the application server with native identity.
Ensure that all configured LVM objects are exported/deported, as the VMAX devices will be
removed from the operating system with user-defined identity and re-presented with native
identity.

2.

Unmount file systems

Vary off the volume groups

Remove the target device paths and device files

From the application host:

Use rmdev to remove the target device files from AIX before removing masking.
# rmdev
hdisk17
# rmdev
hdisk18
# rmdev
hdisk19
# rmdev
hdisk20
# rmdev
hdisk22
# rmdev
hdisk23
# rmdev
hdisk24
# rmdev

-dl hdisk17
deleted
-dl hdisk18
deleted
-dl hdisk19
deleted
-dl hdisk20
deleted
-dl hdisk22
deleted
-dl hdisk23
deleted
-dl hdisk24
deleted
-dl hdisk25

Symmetrix
Customer Procedure Generator Version 3.1.7
Page 1

hdisk25 deleted

3.

Remove masking and mapping for the VMAX target devices

From the Solutions Enabler control host:

Use the symaccess command to delete or modify a masking view to remove application-host
visibility for the VMAX target devices. Use the -unmap flag when deleting or modifying the
masking view to unmap the devices as part of the Auto-provisioning change. FLM target
devices must be unmapped to remove the external identity and geometry.
# symaccess -sid 624 delete view -name aix_flm_mv -unmap

Use the symaccess list command to verify that the target devices have been removed from
all masking views. The view count should be zero (0) for each FLM target device.
# symaccess -sid 624 list -type storage -devs 04CA:04CD
Symmetrix ID
Symm
Dev
---04CA
04CB
04CC
04CD

: 000192602624
Dev
Count
----4
4
4
4

Storage Group Name

-------------------------------aix_flm_sg
aix_flm_sg
aix_flm_sg
aix_flm_sg

View
Count
----0
0
0
0

Use the symdev list noport command to verify that the target devices are not mapped.
Use range to filter a specific range of devices.
# symdev -sid 624 list -range 04CA:04CD -noport
Symmetrix ID: 000192602624
Device Name
Directors
Device
--------------------------- ------------- ------------------------------------Cap
Sym Physical
SA :P DA :IT Config
Attribute
Sts
(MB)
--------------------------- ------------- ------------------------------------04CA
04CB
04CC
04CD

4.

Not
Not
Not
Not

Visible
Visible
Visible
Visible

???:?
???:?
???:?
???:?

10B:C8
10A:D4
10D:D1
07D:D4

2-Way Mir
RAID-5
2-Way Mir
RAID-5

N/Grp'd
N/Grp'd
N/Grp'd
N/Grp'd

RW
RW
RW
RW

898
898
898
898

Remove the external identity

From the Solutions Enabler control host:

Use the symconfigure command to remove the devices external identity. The identity must be
removed before the device can be used for another FLM session. The device having its
external identity removed must be unmapped, or the configuration change will be rejected.
# symconfigure -sid 624 -cmd "set dev 04CA:04CD identity = no identity;" commit
A Configuration Change operation is in progress. Please wait...
Establishing a configuration change session...............Established.
Processing symmetrix 000192602624
Performing Access checks..................................Allowed.
Checking Device Reservations..............................Allowed.
Locking devices...........................................Locked.
Committing configuration changes..........................Started.
Committing configuration changes..........................Committed.
Terminating the configuration change session..............Done.

Symmetrix
Customer Procedure Generator Version 3.1.7
Page 2

The configuration change session has successfully completed.

Use the symdev list -identity command to verify that the target devices are no longer
presenting the identity of the source devices. The external identity should now reflect the native
identity of the FLM target device.
# symdev -sid 624 list -range 04CA:04CD -identity
Symmetrix ID: 000192602624
Device
---------------------------------Sym Physical
Config
Sts
----------------------------------

FLG
External Identity
--- ---------------------------------------IG Array ID
Num
Ser Num
Cap (MB)
--- ----------------------------------------

04CA
04CB
04CC
04CD

.X
.X
.X
.X

Not
Not
Not
Not

Visible
Visible
Visible
Visible

Legend:
Flags:
(I)dentity : X
.
(G)eometry : X
.

5.

2-Way Mir
RAID-5
2-Way Mir
RAID-5

=
=
=
=

The
The
The
The

device
device
device
device

RW
RW
RW
RW

000192602624
000192602624
000192602624
000192602624

004CA
004CB
004CC
004CD

24004CA000
24004CB000
24004CC000
24004CD000

898
898
898
898

has a non-native external identity set

does not have an external identity set
has a user defined geometry
does not have a user defined geometry

Remove the external geometry (if applicable)

Skip this step if external geometry is not set on the FLM target device.

From the Solutions Enabler control host:

Use the symconfigure command to remove the external geometry. The device having its
external geometry removed must be unmapped, or the configuration change will be rejected.
# symconfigure -sid 624 -cmd "set dev 04CA:04CD geometry = no geometry;" commit
A Configuration Change operation is in progress. Please wait...
Establishing a configuration change session...............Established.
Processing symmetrix 000192602624
Performing Access checks..................................Allowed.
Checking Device Reservations..............................Allowed.
Locking devices...........................................Locked.
Committing configuration changes..........................Started.
Committing configuration changes..........................Committed.
Terminating the configuration change session..............Done.
The configuration change session has successfully completed.

Use the symdev list identity command to verify that the target devices are no longer
presenting the geometry of the source devices. The flag should now indicate that user-defined
geometry is not set.
# symdev -sid 624 list -range 04CA:04CD -identity
Symmetrix ID: 000192602624
Device
---------------------------------Sym Physical
Config
Sts
----------------------------------

FLG
External Identity
--- ---------------------------------------IG Array ID
Num
Ser Num
Cap (MB)
--- ----------------------------------------

04CA Not Visible 2-Way Mir

04CB Not Visible RAID-5
04CC Not Visible 2-Way Mir

..
..
..

RW
RW
RW

000192602624
000192602624
000192602624

004CA 24004CA000
004CB 24004CB000
004CC 24004CC000

Symmetrix
Customer Procedure Generator Version 3.1.7
Page 3

898
898
898

04CD Not Visible RAID-5

Legend:
Flags:
(I)dentity : X
.
(G)eometry : X
.

6.

=
=
=
=

The
The
The
The

RW

device
device
device
device

..

000192602624

004CD 24004CD000

898

has a non-native external identity set

does not have an external identity set
has a user defined geometry
does not have a user defined geometry

Mask the VMAX target devices to the application host

From the Solutions Enabler control host:

Use the symaccess command to create or modify a masking view to add application-host
visibility for the VMAX target devices with native identity.
# symaccess -sid 624 create view -name aix_flm_mv -ig aix_flm_ig -pg aix_flm_pg -sg
aix_flm_sg

Use the symaccess show view command to verify that the target devices are properly
configured in the Auto-provisioning Group.
# symaccess -sid 624 show view aix_flm_mv
Symmetrix ID

: 000192602624

Masking View Name

Last updated at

: aix_flm_mv
: 05:02:16 PM on Tue May 24,2011

Initiator Group Name

: aix_flm_ig

Host Initiators
{
WWN : 10000000c96ef1d7 [alias: aix_flm/10000000c96ef1d7]
WWN : 10000000c9538be2 [alias: aix_flm/10000000c9538be2]
}
Port Group Name

: aix_flm_pg

Director Identification
{
FA-8E:1
FA-9E:0
}
Storage Group Name
Sym Dev
Name
Dir:P
------ ----04CA
08E:1
09E:0
04CB
08E:1
09E:0
04CC
08E:1
09E:0
04CD
08E:1
09E:0

: aix_flm_sg

Physical Device Name

----------------------Not Visible
Not Visible
Not Visible
Not Visible
Not Visible
Not Visible
Not Visible
Not Visible

Host
Lun
---1
1
2
2
3
3
4
4

Total Capacity

Attr
----

Cap(MB)
------898
898
898
898
------3592

Symmetrix
Customer Procedure Generator Version 3.1.7
Page 4

7.

Perform a host SCSI rescan to discover the VMAX target device paths
From the application host:

Perform a host SCSI rescan to discover and configure the VMAX target device with native
identity. Reference the EMC Host Connectivity Guide for IBM AIX for the appropriate LUN scan
procedures and considerations.
# cfgmgr

If applicable, repeat the preceding procedure on all the nodes in the cluster.
8.

Verify the native target device paths

From the application host:

Use lspath to verify that the target paths have been configured as alternate paths to the
source devices. If any paths are missing, examine the cause before continuing.
# lspath -l hdisk17 -F "name path_id parent connection status"
hdisk17 0 fscsi1 500009720836f5d9,1000000000000 Enabled
hdisk17 1 fscsi1 500009720836f5dd,1000000000000 Enabled

NOTE: Confirm that the new target device attributes exactly match the attributes prior to the
external identify being removed. If they do not match, use chdev to change them to the
appropriate ones.
9.

Resume application I/O

Any LVM objects exported/deported at the beginning of this procedure can be reimported on
the VMAX devices with native identity.
NOTE: Device special files may have changed as part of the device removal and rediscovery.

Vary on volume groups

Mount file systems

Table of Contents

Symmetrix
Customer Procedure Generator Version 3.1.7
Page 5