Linux DMP Federated Live Migration

 

Topic

Managing Federated Live Migrations

Selections

Select an operating system: Linux

Select multipath type: DMP

 

 

Contents

·            Preparing SAN to Support Federated Live Migration. 3

·            Migrating Data Using Federated Live Migration. 11

·            Performing Failback During Federated Live Migration. 23

·            Removing External Identity and Geometry following Federated Live Migration. 30

 


 

·       Preparing SAN to Support Federated Live Migration

 

 

Overview

Perform the following steps to prepare the SAN to support Federated Live Migration (FLM).

 

! 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 SymmetrixArray 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

 

All SYMCLI commands listed in this procedure can be executed from the Solutions Enabler Control Host.

 

1.   

Verify that the application host and source devices are configured to support FLM

Identify the application host where FLM will be used.

 

Validate that the platform (host type), operating system, host bus adapter, driver, infrastructure software (multipath solution), server LVM, and file system are supported in the FLM Simple Support Matrix.

 

Identify the source devices for FLM migration. Record the source director WWNs for use in step 3 (Configure SAN zoning for the FLM migration). Record the FA port settings to ensure that they are the same for all source ports and are configured identically for the target FA ports in step 2.

 

Important: Observations of host_passive/host_active change performance suggest limiting the number of source devices on a single host participating in an FLM session to 32 devices.

 

Use the symdev command to identify the source device (0720, 075F, 076B, and 07E9) FA director ports. The director ports for multiple devices used by the same application should be the same. For example for device 720:

 

symdev -sid 76 list -range 720:720 -multiport

 

Symmetrix ID: 000187490076

 

                      M U L T I - P O R T      D E V I C E S

 

     Device Name           Directors                   Device

------------------------ ------------- -------------------------------------

                                                                        Cap

Physical            Sym  SA :P DA :IT  Config        Attribute    Sts   (MB)

------------------------ ------------- -------------------------------------

 

                    0720       01B:D8  2-Way Mir     N/Grp'd  (M) RW    3750

Not Visible            - 14C:0      -  -             -            -        -

Not Visible            - 14C:1      -  -             -            -        -

 

Use the symcfg list command to identify the FA director port WWNs.

 

symcfg -sid 76 list -fa 14c -p 0

. . .

    Dir    Port  WWN                VCM      Volume Set   Pnt to Pnt

                                    Enabled  Addressing

 

 

    FA-14C  0    5006048ACB37C70D  Yes      No           Yes

 

symcfg -sid 76 list -fa 14c -p 1

. . .

    Dir    Port  WWN                VCM      Volume Set   Pnt to Pnt

                                    Enabled  Addressing

 

 

    FA-14C  1    5006048ACB37C72D  Yes      No           Yes

 

Use the symcfg list -v command to identify the port flag settings for each of the source and target FA ports. Make note of these port flag settings.

 

symcfg -sid 76 list -fa 14c -p 0 -v

 

Symmetrix ID: 000187490076

Time Zone   : Eastern Standard Time

 

    Product Model                        : 1000S-M2

    Symmetrix ID                         : 000187490076

. . .

          SCSI Flags

            {

              Negotiate_Reset(N)           : Disabled

              Soft_Reset(S)                : Disabled

              Environ_Set(E)               : Disabled

              HP3000_Mode(B)               : Disabled

              Common_Serial_Number(C)      : Enabled

              Disable_Q_Reset_on_UA(D)     : Enabled

              Sunapee(SCL)                 : Disabled

              Siemens(S)                   : Disabled

              Sequent(SEQ)                 : Disabled

              Avoid_Reset_Broadcast(ARB)   : Disabled

              Server_On_AS400(A4S)         : Disabled

              SCSI_3(SC3)                  : Enabled

              SPC2_Protocol_Version(SPC2)  : Enabled

              SCSI_Support1(OS2007)        : Enabled

            }

 

          Fibre Specific Flags

            {

              Volume_Set_Addressing(V)     : Disabled

              Non_Participating(NP)        : Disabled

              Init_Point_to_Point(PP)      : Enabled

              Unique_WWN(UWN)              : Enabled

              VCM_State(VCM)               : Enabled

              OpenVMS(OVMS)                : Disabled

              AS400(AS4)                   : Disabled

              Auto_Negotiate(EAN)          : Enabled

            }

 

Note: Different host operating systems present the FA flags differently. Refer to the E-Lab™ matrix for the available port flags for your host.

 

HBA port flags can be set on a per-initiator basis or by host name. Therefore, it is necessary to check for port overrides.

 

For 5875 source arrays:

Use the symaccess show command to identify any applicable port overrides for the application host WWNs.

 

symaccess -sid 517 show flm_ig -type init -detail

 

Symmetrix ID          : 000187490076

 

Initiator Group Name  : flm_ig

Last update time      : 10:21:16 AM on Wed Nov 21,2012

 

Group last update time: 10:21:16 AM on Wed Nov 21,2012

 

Port Flag Overrides   : Yes

  Enabled             : SPC2_Protocol_Version(SPC2)

  Disabled            : N/A

Consistent Lun        : No

 

   Originator Port wwn  : 21000024ff3e93d0

   User-generated Name  : 21000024ff3e93d0/21000024ff3e93d0

   FCID Lockdown        : No

   Heterogeneous Host   : No

   Port Flag Overrides  : Yes

     Enabled            : SPC2_Protocol_Version(SPC2)

     Disabled           : N/A

   CHAP Enabled         : N/A

   Type                 : Fibre

 

For 5671 and 5773 source arrays:

Use the symmaskdb list -v command to identify any applicable port overrides for the application host WWNs.

 

symmaskdb list db -sid 76 -v

 

Symmetrix ID            : 000187490076

 

Database Type           : Type5

Last updated at         : 04:28:16 PM on Mon Jan 31,2011

 

. . .

 

Director Identification : FA-14C

Director Port           : 0

 

. . .

 

   Originator Port wwn  : 10000000c953f9f3

   Type                 : Fibre

   User-generated Name  : win_flm/10000000c953f9f3

   Visibility           : No

   FCID Lockdown        : No

   Lun Offset           : No

   Heterogeneous Host   : No

   Port Flag Overrides  : Yes

     Enabled            : SPC2_Protocol_Version(SPC2) 

     Disabled           : N/A

   Dynamic Addressing   : N/A

   Authentication State : N/A

   Devices              : 0720 075F 076B 07E9

 

. . .

 

 

2.   

Identify and configure the target devices

Identify the FLM target array. The FLM target array must run Enginuity™ 5875 and higher to support FLM. In this example, Symmetrix ID (SID) 000194900275 is used.

 

Identify the target FA ports for the front-end interface to the application host. These ports will become active at the start of the FLM migration. In this example, FA ports FA07E:0 and FA08E:0 are used.

 

Ensure that the port settings for these ports are identical to the source port settings recorded in step 1, including setting any hba_flags or ig_flags overrides with the symaccess command.

 

Identify the target FA director port WWNs to be used for zoning in step 3 with the symcfg list command.

 

symcfg -sid 75 list -fa 7e -p 0

. . .

    Dir    Port  WWN                VCM      Volume Set   Pnt to Pnt

                                    Enabled  Addressing

 

    FA-7E   0    50000972c0044d18   Yes      No           Yes

 

symcfg -sid 75 list -fa 8e -p 0

. . .

    FA-8E   0    50000972c0044d1c   Yes      No           Yes

 

Identify the target devices for FLM migration. FLM target devices must be of equal or larger capacity than the FLM source devices identified in step 1. Identify one target device for each source device. In this example, devices 0328, 0329, 032A, and 032B are used.

 

Map, but do not mask, the target devices to the identified target ports.

 

symconfigure -sid 75 -cmd "map dev 328:32b to dir 7e:0 lun=1; map dev 328:32b to dir 8e:0 lun=1;" commit

 

! WARNING: Unlike when using Open Replicator for a non-FLM session, FLM target devices should not be added to any Auto-provisioning masking views at this point!

 

Configure zoning to make the target FA ports visible to the application host initiator ports.

 

3.   

Configure SAN zoning for the FLM migration

For each fabric, create a zone from the FLM target FA ports, which are identified in step 2, to the FLM source FA ports, which are identified in step 1. One-to-one zoning should be specified.

 

The FLM source devices must be visible to each FLM target FA port where the FLM target devices are mapped.

 

The following example is an excerpt of the Connectrix® Manager Zoning verification screen with the two zones defined.

.

zoning

 

 

4.   

Add migration device masking for the FLM target FA ports to access the FLM source devices

 

For 5875 source arrays:

Use the symaccess add devs command to add FLM target visibility for the source devices.

 

symaccess -sid 76 -name ors_ig –type initiator create

 

symaccess -sid 76 -name ors_ig -wwn 50000972c0044d18 –type initiator add

 

symaccess -sid 76 -name ors_ig -wwn 50000972c0044d1c –type initiator add

 

symaccess -sid 76 create view –name ors_mv –sg flm_sg –pg flm_pg ig ors_ig

 

 

Use the symaccess show command to verify that the FLM source devices are masked to the application host and the FLM target array.

 

symaccess -sid 76 -type storage show flm_sg

 

Symmetrix ID                : 000187490076

 

Storage Group Name          : flm_sg

Last update time            : 01:29:35 PM on Thu Sep 20,2012

Group last update time      : 01:29:35 PM on Thu Sep 20,2012

 

   Number of Storage Groups : 0

   Storage Group Names      : None

 

   Devices                  : 0720,075F,07B6,07E9

 

   Masking View Names

     {

       ors_mv

       flm_mv

     }

 

For 5671 and 5773 source arrays:

Use the symmask add devs command to add FLM target visibility for the source devices.

 

symmask -sid 76 -dir 14c -p 0 -wwn 50000972c0044d18 add devs 0720,075F,07B6,07E9

 

symmask -sid 76 -dir 14c -p 1 -wwn 50000972c0044d1c add devs 0720,075F,07B6,07E9

 

Use the symmask refresh command on the FLM source array to trigger all records within the database to be pushed out to the local directors.

 

symmask -sid 076 refresh

 

Symmetrix FA/SE directors updated with contents of SymMask Database 000187490076

 

Use the symmaskdb list assignment command to verify that the FLM source devices are masked to the application host and the FLM target array.

 

symmaskdb -sid 76 list assignment -devs 0720,075F,07B6,07E9

 

Symmetrix ID : 000187490076

 

Device  Identifier        Type   Dir:P

------  ----------------  -----  ----------------

0720    50000972c0044d18  FIBRE  FA-14C:0

        50000972c0044d1c  FIBRE  FA-14C:1

        10000000c953f9f3  FIBRE  FA-14C:0,FA-14C:1

075F    50000972c0044d18  FIBRE  FA-14C:0

        50000972c0044d1c  FIBRE  FA-14C:1

        10000000c953f9f3  FIBRE  FA-14C:0,FA-14C:1

07B6    50000972c0044d18  FIBRE  FA-14C:0

        50000972c0044d1c  FIBRE  FA-14C:1

        10000000c953f9f3  FIBRE  FA-14C:0,FA-14C:1

07E9    50000972c0044d18  FIBRE  FA-14C:0

        50000972c0044d1c  FIBRE  FA-14C:1

        10000000c953f9f3  FIBRE  FA-14C:0,FA-14C:1

 

5.   

Verify FLM migration visibility of the FLM source devices from each FLM target FA port

Use the symsan command for each FLM target FA port identified in step 2 to confirm that the remote LUNs are visible.

 

symsan -sid 75 -dir 7e -p 0 list -sanports -detail

 

Symmetrix ID: 000194900275

 

      Flags                                Num                              Remote

DIR:P   I   Vendor        Array            LUNs Remote Port WWN             DIR:P

----- ----- ------------- ---------------- ---- --------------------------- -----

07E:0   .   EMC Symmetrix 000187490076        5 5006048ACB37C70D            14C:0

 

Legend:

 Flags: (I)ncomplete : X = record is incomplete, . = record is complete.

 

 

symsan -sid 75 -dir 7e -p 0 -wwn 5006048ACB37C70D list -sanluns

 

Symmetrix ID:      000194900275

Remote Port WWN:   5006048ACB37C70D

 

      ST

       A

       T  Flags  Block   Capacity   LUN   Dev  LUN

DIR:P  E ICRTHS  Size      (MB)     Num   Num  WWN

----- -- ------- ----- ----------- ----- ----- --------------------------------

07E:0 WD ...F.X    512          45     0  07ED 6006048000018749007653594D374544

07E:0 RW ...F.X    512        3750     6  0720 6006048000018749007653594D373230

07E:0 RW ...F.X    512        3750    36  075F 6006048000018749007653594D373546

07E:0 RW ...F.X    512        3750    6C  07B6 6006048000018749007653594D374236

07E:0 RW ...F.X    512         938    96  07E9 6006048000018749007653594D374539

 

Legend:

 Flags: (I)ncomplete : X = record is incomplete, . = record is complete.

        (C)ontroller : X = record is controller, . = record is not controller.

        (R)eserved   : X = record is reserved, . = record is not reserved.

        (T)ype       : A = AS400, F = FBA, C = CKD, . = Unknown

        t(H)in       : X = record is a thin dev, . = record is not a thin dev.

        (S)ymmtrix   : X = Symmetrix device, . = not Symmetrix device.

 

 

symsan -sid 275 -dir 8e -p 0 list -sanports -detail

 

Symmetrix ID: 000194900275

 

      Flags                                Num                              Remote

DIR:P   I   Vendor        Array            LUNs Remote Port WWN             DIR:P

----- ----- ------------- ---------------- ---- --------------------------- -----

08E:0   .   EMC Symmetrix 000187490076        5 5006048ACB37C72D            14C:1

. . .

 

symsan -sid 275 -dir 8e -p 0 -wwn 5006048ACB37C72D list -sanluns

 

Symmetrix ID:      000194900275

Remote Port WWN:   5006048ACB37C72D

 

      ST

       A

       T  Flags  Block   Capacity   LUN   Dev  LUN

DIR:P  E ICRTHS  Size      (MB)     Num   Num  WWN

----- -- ------- ----- ----------- ----- ----- --------------------------------

08E:0 WD ...F.X    512          45     0  07ED 6006048000018749007653594D374544

08E:0 RW ...F.X    512        3750     6  0720 6006048000018749007653594D373230

08E:0 RW ...F.X    512        3750    36  075F 6006048000018749007653594D373546

08E:0 RW ...F.X    512        3750    6C  07B6 6006048000018749007653594D374236

08E:0 RW ...F.X    512         938    96  07E9 6006048000018749007653594D374539

. . .

 

 

6.   

Adjust the ORS ceiling on the FLM target FA ports to the recommended values

Use the symrcopy list ceiling command to list the current ceiling settings.

 

symrcopy -sid 275 list ceiling

 

Symmetrix ID: 000194900275

 

    Symmetrix Remote Copy Bandwidth Ceiling

 

                   Max   Set   Actual

            Dir:P  (MB)  (%)    (MB)

            -----  ----  ----  ------

            07E:0   150  NONE       0

            07E:1   150  NONE       0

            08E:0   150  NONE       0

            08E:1   150  NONE       0

            07F:0   150  NONE       0

            07F:1   150  NONE       0

            08F:0   150  NONE       0

            08F:1    80  NONE       0

            07G:0   300  NONE       0

            07G:1   300  NONE       0

            08G:0   150  NONE       0

            08G:1   150  NONE       0

 

The default ceiling value is NONE. For FLM, EMC recommends setting the ceiling limits for the target FA ports for a 5671 source array to 20 percent, and to 40 percent for a 5773 and higher source array.

 

Use the symrcopy set ceiling command to set the ceiling for the target FA ports.

 

 

symrcopy -sid 275 -dir 7e -p 0 set ceiling 20

 

'Set Ceiling' operation execution is in progress

'Set Ceiling' operation successfully executed

 

symrcopy -sid 275 -dir 8e -p 0 set ceiling 20

 

'Set Ceiling' operation execution is in progress

'Set Ceiling' operation successfully executed

 

Use the symrcopy list ceiling command to verify that the ceiling settings are set as recommended.

 

symrcopy -sid 275 list ceiling

 

Symmetrix ID: 000194900275

 

    Symmetrix Remote Copy Bandwidth Ceiling

 

                   Max   Set   Actual

            Dir:P  (MB)  (%)    (MB)

            -----  ----  ----  ------

            07E:0   150    20       0

            07E:1   150    20       0

            08E:0   150    20       0

            08E:1   150    20       0

            07F:0   150  NONE       0

            07F:1   150  NONE       0

            08F:0   150  NONE       0

            08F:1    80  NONE       0

            07G:0   300  NONE       0

            07G:1   300  NONE       0

            08G:0   150  NONE       0

            08G:1   150  NONE       0

 

7.   

Create an FLM pair file

Use a text-editing tool to create a pair file in the format of a standard Open Replicator pull session to specify the FLM source and target devices.

 

In this pair file example, the first column should contain the FLM target device using either the format symdev=<array_id>:<device_id> or wwn=<device_wwn>.


The second column should contain the FLM source device using either the format
symdev=<array_id>:<device_id> or wwn=<device_wwn>.

 

## FLM PAIR FILE

##

## COLUMN1: FLM Target [ VMAX - 5875 ]

## COLUMN2: FLM Source [ DMX  - 5671 ]

 

symdev=000194900275:0328 symdev=000187490076:0720

symdev=000194900275:0329 symdev=000187490076:075F

symdev=000194900275:032A symdev=000187490076:07B6

symdev=000194900275:032B symdev=000187490076:07E9

 

This file will be used to manage the FLM migration.

 

 

 

 

 

·       Migrating Data Using Federated Live Migration

 

 

Overview

Perform the following steps to migrate data using Federated Live Migration (FLM) on a stand-alone Linux application host with Veritas Storage Foundations for Linux.

 

! 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.5 Product Guide
  • EMC Solutions Enabler Symmetrix Array Management CLI 7.5 Product Guide
  • EMC Solutions Enabler Symmetrix Array Controls CLI 7.5 Product Guide

 

These documents can be obtained from EMC Online Support at:

 http://support.EMC.com

 

 

8.   

Configure the DMP tunable parameters to FLM required values

From the application host:

 

Check and modify the following DMP tunable parameters. If the parameter values are not set to the default values, make note of the settings so that the parameters can be returned to expected values following FLM migration.

 

DMP tunable parameter

Default value

FLM required value

dmp_path_age

300

0

dmp_health_time

60

0

iopolicy (per DMP node name)

MinimumQ

MinimumQ

 

To check the value of the dmp_path_age tunable parameter:

 

# vxdmpadm gettune dmp_path_age

 

            Tunable               Current Value  Default Value

------------------------------    -------------  -------------

dmp_path_age                            300              300

 

If necessary, modify the dmp_path_age tunable parameter:

 

# vxdmpadm settune dmp_path_age=0

Tunable value will be changed immediately

 

To check the value of the dmp_health_time tunable parameter:

 

# vxdmpadm gettune dmp_health_time

            Tunable               Current Value  Default Value

------------------------------    -------------  -------------

dmp_health_time                          60               60

 

If necessary, modify the dmp_health_time tunable parameter:

 

# vxdmpadm settune dmp_health_time=0

Tunable value will be changed immediately

 

To check the value of iopolicy tunable parameter per DMP node:

# vxdmpadm list dmpnode dmpnodename=emc2_0150

dmpdev          = emc2_0150

state           = enabled

enclosure       = emc2

cab-sno         = 000190100860

asl             = libvxemc.so

vid             = EMC

pid             = SYMMETRIX

array-name      = EMC

array-type      = A/A

iopolicy        = MinimumQ

avid            = 0150

lun-sno         = 6000150000

udid            = EMC%5FSYMMETRIX%5F000190100860%5F6000150000

dev-attr        = std

. . .

 

If necessary, modify the iopolicy tunable parameter per enclosure:

 

# vxdmpadm setattr enclosure emc2 iopolicy=minimumq

 

Verify that all required tunable parameters are set.

 

# vxdmpadm gettune dmp_path_age

            Tunable               Current Value  Default Value

------------------------------    -------------  -------------

dmp_path_age                              0              300

 

# vxdmpadm gettune dmp_health_time

            Tunable               Current Value  Default Value

------------------------------    -------------  -------------

dmp_health_time                           0               60

 

 

9.   

Create the FLM session

From the Solutions Enabler control host:

 

Use a pair file in the format of a standard ORS pull session to specify the FLM source and target devices:

 

## FLM PAIR FILE

##

## COLUMN1: FLM Target [ VMAX - 5875 ]

## COLUMN2: FLM Source [ DMX  - 5773 ]

 

symdev=194900275:0195 symdev=190100860:0150

symdev=194900275:0295 symdev=190100860:0154

symdev=194900275:01FF symdev=190100860:0158

symdev=194900275:02FF symdev=190100860:015C

 

Use the symrcopy create –pull -migrate command to create a NoCopy FLM session with the devices specified by the FLM pair file.

 

# symrcopy -f linux_dmp create -pull -migrate -host_type linux       \

>                                             -mp_type dmp

 

'Create' operation execution is in progress for the device list

in device file 'linux_dmp'. Please wait...

 

'Create' operation successfully executed for the device list

in device file 'linux_dmp'.

 

Executing this command  performs the following:

·     FLM VMAX target devices are set to passive host access mode

·     FLM VMAX target devices assume the external identity of FLM source devices

·     FLM VMAX target devices assume the external geometry of FLM source devices (if necessary)

 

FLM VMAX target FA ports externally display a two-port offset for FLM target devices. As an example, VMAX devices mapped to FA 07F:0 and FA 08F:1 will be externally displayed on FA 07F:2 and FA 08F:3.

 

10.  

Verify the created FLM session

Use the symrcopy query command to verify that the FLM pairs are listed as migration sessions in the Created state. The value of M for type (T) in the Flags column indicates that the session is an FLM migration session.

 

# symrcopy -f linux_dmp query

 

Device File Name      : linux_dmp

 

       Control Device                  Remote Device      Flags      Status     Done

---------------------------- --------------------------- ------- -------------- ----

                   Protected

SID:symdev         Tracks    Identification           RI CDSHUTZ  CTL <=> REM    (%)

------------------ --------- ------------------------ -- ------- -------------- ----

000194900275:0195     138000 000190100860:0150        SD ...XXM. Created         N/A

000194900275:0295     138000 000190100860:0154        SD ...XXM. Created         N/A

000194900275:01FF     138000 000190100860:0158        SD ...XXM. Created         N/A

000194900275:02FF     138000 000190100860:015C        SD ...XXM. Created         N/A

 

Total              ---------

  Track(s)            552000

  MB(s)              34500.0

 

Legend:

R:  (Remote Device Vendor Identification)

  S = Symmetrix, C = Clariion, . = Unknown.

 

I:  (Remote Device Specification Identifier)

  D = Device Name, W = LUN WWN, World Wide Name.

 

Flags:

(C): X = The background copy setting is active for this pair.

     . = The background copy setting is not active for this pair.

(D): X = The session is a differential copy session.

     . = The session is not a differential copy session.

(S): X = The session is pushing data to the remote device(s).

     . = The session is pulling data from the remote device(s).

(H): X = The session is a hot copy session.

     . = The session is a cold copy session.

(U): X = The session has donor update enabled.

     . = The session does not have donor update enabled.

(T): M = The session is a migration session.

     R = The session is a RecoverPoint session.

     S = The session is a standard ORS session.

(Z): X = The session has front-end zero detection enabled.

     . = The session does not have front-end zero detection enabled.

(*): The failed session can be reactivated.

 

 

11.  

Verify the external identity, and optional external geometry, on the FLM VMAX target devices

From the Solutions Enabler control host:

 

Use the symdev list –identity command to verify that the target devices are now presenting the identity of the source devices. Use –range to filter a specific range of devices. Use –identity_set to filter devices with a user-defined external identity.

 

# symdev -sid 275 list -identity_set -identity

 

Symmetrix ID: 000194900275

 

              Device               FLG            External Identity

---------------------------------- --- ----------------------------------------

Sym  Physical    Config        Sts IG  Array ID       Num   Ser Num    Cap (MB)

---------------------------------- --- ----------------------------------------

 

0195 Not Visible 2-Way Mir     RW  XX  000190100860   00150 6000150000     8625

01FF Not Visible RAID-5        RW  XX  000190100860   00158 6000158000     8625

0295 Not Visible RAID-6        RW  XX  000190100860   00154 6000154000     8625

02FF Not Visible TDEV          RW  XX  000190100860   0015C 600015C000     8625

 

Legend:

  Flags:

   (I)dentity : X = The device has a non-native external identity set

                . = The device does not have an external identity set

   (G)eometry : X = The device has a user defined geometry

                . = The device does not have a user defined geometry

 

All the fields listed under the External Identity column for each device must match the associated source devices. In this example, the value of X under (I)dentity and (G)eometry in the FLG column indicates that the FLM target devices have both user-defined external identity and geometry.

 

 

12.  

Mask 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 source external identity.

 

# symaccess -sid 275 create view -name linux_dmp_mv \

>                                -ig linux_dmp_ig   \

>                                -pg linux_dmp_pg   \

>                                -sg linux_dmp_sg

 

Use the symaccess show view command to verify that the target devices are properly configured in the Auto-provisioning group.

 

# symaccess -sid 275 show view linux_dmp_mv

 

Symmetrix ID          : 000194900275

 

Masking View Name     : linux_dmp_mv

Last updated at       : 02:35:18 PM on Fri Apr 01,2011

 

Initiator Group Name  : linux_dmp_ig

 

   Host Initiators

     {

       WWN  : 210000e08b8a556e [alias: 210000e08b8a556e/210000e08b8a556e]

       WWN  : 210100e08baa556e [alias: 210100e08baa556e/210100e08baa556e]

     }

 

Port Group Name       : linux_dmp_pg

 

   Director Identification

     {

       FA-7E:0

       FA-8E:0

     }

 

Storage Group Name    : linux_dmp_sg

 

Sym Dev                                 Host

Name    Dir:P  Physical Device Name      Lun  Attr  Cap(MB)

------  -----  -----------------------  ----  ----  -------

0195    07E:0  Not Visible                 1           8631

        08E:0  Not Visible                 1

01FF    07E:0  Not Visible                 2  (M)     34523

        08E:0  Not Visible                 2  (M)

0295    07E:0  Not Visible                 3           8631

        08E:0  Not Visible                 3

02FF    07E:0  Not Visible                 4  (M)     34523

        08E:0  Not Visible                 4  (M)

-------

Total Capacity                                        34524

 

 

13.  

Perform  a host SCSI reset/scan to discover the VMAX target device paths presented as the source devices

From the application host:

 

Perform a host SCSI reset/scan to discover and configure the VMAX target device paths presenting as the source external device identity.

 

Reference the EMC Host Connectivity Guide for Linux to determine the appropriate method for Linux online reset/scan, based on your kernel and drivers. The section titled “LUN scanning mechanisms” contains the scan methods.

 

Run vxdisk scandisks new to configure the new target paths into DMP.

 

# vxdisk scandisks new

 

 

14.  

Verify the external device identity of the VMAX target device paths

From the application host:

 

IMPORTANT: Once the source and target paths are both visible and configured on the application host, do not run vxdisk scandisks or vxdctl enable until directed by the following procedure. Running either of these commands prematurely, while in the middle of an FLM migration, removes the passive paths from the DMP configuration and may lead to data unavailability.

 

Use vxdmpadm getsubpaths to verify that the target paths have been configured as alternate paths to the source devices.

 

The enclosure=<enclosure_name> parameter can be added to filter the display for a specific controller.

 

# vxdmpadm getsubpaths enclosure=emc2

NAME         STATE[A]   PATH-TYPE[M] DMPNODENAME  ENCLR-NAME   CTLR    ATTRS

================================================================================

sdci         ENABLED(A)   -          emc2_0150    emc2         c1        -

sdcm         ENABLED(A)   -          emc2_0150    emc2         c2        -

sdcs         DISABLED     -          emc2_0150    emc2         c1        -

sddy         DISABLED     -          emc2_0150    emc2         c2        -

sdcj         ENABLED(A)   -          emc2_0154    emc2         c1        -

sdcn         ENABLED(A)   -          emc2_0154    emc2         c2        -

sdda         DISABLED     -          emc2_0154    emc2         c1        -

sdeg         DISABLED     -          emc2_0154    emc2         c2        -

sdck         ENABLED(A)   -          emc2_0158    emc2         c1        -

sdco         ENABLED(A)   -          emc2_0158    emc2         c2        -

sdcv         DISABLED     -          emc2_0158    emc2         c1        -

sdeb         DISABLED     -          emc2_0158    emc2         c2        -

sdcl         ENABLED(A)   -          emc2_015c    emc2         c1        -

sdcp         ENABLED(A)   -          emc2_015c    emc2         c2        -

sddd         DISABLED     -          emc2_015c    emc2         c1        -

sdej         DISABLED     -          emc2_015c    emc2         c2        -

 

The passive target paths should report a state of DISABLED. If any paths, other than the expected paths, report a DISABLED state, examine the cause before continuing.

 

 

 

15.  

Activate the FLM session

From the Solutions Enabler control host:

 

Use the symrcopy activate -migrate command to activate the FLM session with the devices specified by the FLM pair file.

 

# symrcopy -f linux_dmp activate -migrate

 

'Activate' operation execution is in progress for the device list

in device file 'linux_dmp'. Please wait...

 

'Activate' operation successfully executed for the device list

in device file 'linux_dmp'.

 

Executing this command  performs the following:

·     FLM VMAX target devices are set to active host access mode

·     FLM DMX source devices are set to passive host access mode

·     FLM session is set to Copy mode

 

 

16.  

Verify the FLM pairs

From the Solutions Enabler control host:

 

Use the symrcopy query command to verify that the FLM pair’s status is either CopyInProg or Copied.

 

# symrcopy -f linux_dmp query

 

Device File Name      : linux_dmp

 

       Control Device                  Remote Device      Flags      Status     Done

---------------------------- --------------------------- ------- -------------- ----

                   Protected

SID:symdev         Tracks    Identification           RI CDSHUTZ  CTL <=> REM    (%)

------------------ --------- ------------------------ -- ------- -------------- ----

000194900275:0195     129138 000190100860:0150        SD X..XXM. CopyInProg        6

000194900275:0295     129165 000190100860:0154        SD X..XXM. CopyInProg        6

000194900275:01FF     128307 000190100860:0158        SD X..XXM. CopyInProg        7

000194900275:02FF     129190 000190100860:015C        SD X..XXM. CopyInProg        6

 

Total              ---------

  Track(s)            515800

  MB(s)              32237.5

.  .  .

 

 

17.  

Verify the cutover on the application host

From the application host:

 

Use vxdmpadm getsubpaths to verify the cutover. Activate sets the target devices to host access mode active and the source devices to host access mode passive. FLM source paths should now report a DISABLED state and FLM target device paths should now report an ENABLED state. If the device states are not correct, examine the cause before proceeding.

 

The enclosure=<enclosure_name> parameter can be added to filter the display for a specific controller.

 

# vxdmpadm getsubpaths enclosure=emc2

NAME         STATE[A]   PATH-TYPE[M] DMPNODENAME  ENCLR-NAME   CTLR    ATTRS

================================================================================

sdci         DISABLED     -          emc2_0150    emc2         c1        -

sdcm         DISABLED     -          emc2_0150    emc2         c2        -

sdcs         ENABLED(A)   -          emc2_0150    emc2         c1        -

sddy         ENABLED(A)   -          emc2_0150    emc2         c2        -

sdcj         DISABLED     -          emc2_0154    emc2         c1        -

sdcn         DISABLED     -          emc2_0154    emc2         c2        -

sdda         ENABLED(A)   -          emc2_0154    emc2         c1        -

sdeg         ENABLED(A)   -          emc2_0154    emc2         c2        -

sdck         DISABLED     -          emc2_0158    emc2         c1        -

sdco         DISABLED     -          emc2_0158    emc2         c2        -

sdcv         ENABLED(A)   -          emc2_0158    emc2         c1        -

sdeb         ENABLED(A)   -          emc2_0158    emc2         c2        -

sdcl         DISABLED     -          emc2_015c    emc2         c1        -

sdcp         DISABLED     -          emc2_015c    emc2         c2        -

sddd         ENABLED(A)   -          emc2_015c    emc2         c1        -

sdej         ENABLED(A)   -          emc2_015c    emc2         c2        -

 

 

18.  

Monitor the FLM session

From the Solutions Enabler control host:

 

Use the symrcopy query command to query the status of the FLM migration for the devices specified by the FLM pair file. The pair status will be either CopyInProg or Copied.

 

# symrcopy -f linux_dmp query

 

Device File Name      : linux_dmp

 

       Control Device                  Remote Device      Flags      Status     Done

---------------------------- --------------------------- ------- -------------- ----

                   Protected

SID:symdev         Tracks    Identification           RI CDSHUTZ  CTL <=> REM    (%)

------------------ --------- ------------------------ -- ------- -------------- ----

000194900275:0195      75461 000190100860:0150        SD X..XXM. CopyInProg       45

000194900275:0295      76468 000190100860:0154        SD X..XXM. CopyInProg       44

000194900275:01FF      74423 000190100860:0158        SD X..XXM. CopyInProg       46

000194900275:02FF      78168 000190100860:015C        SD X..XXM. CopyInProg       43

 

Total              ---------

  Track(s)            304520

  MB(s)              19032.5

. . .

 

 

19.  

Verify that the FLM session is Copied

From the Solutions Enabler control host:

 

Use the symrcopy query command to query the status of the FLM migration for the devices specified by the FLM pair file. Confirm the copy is complete. The pair status is Copied.

 

# symrcopy -f linux_dmp query

 

Device File Name      : linux_dmp

 

       Control Device                  Remote Device      Flags      Status     Done

---------------------------- --------------------------- ------- -------------- ----

                   Protected

SID:symdev         Tracks    Identification           RI CDSHUTZ  CTL <=> REM    (%)

------------------ --------- ------------------------ -- ------- -------------- ----

000194900275:0195          0 000190100860:0150        SD X..XXM. Copied          100

000194900275:0295          0 000190100860:0154        SD X..XXM. Copied          100

000194900275:01FF          0 000190100860:0158        SD X..XXM. Copied          100

000194900275:02FF          0 000190100860:015C        SD X..XXM. Copied          100

 

Total              ---------

  Track(s)                 0

  MB(s)                  0.0

. . .

 

Use the symrcopy verify command to confirm that all pairs are in a Copied state.

 

# symrcopy -f linux_dmp verify

 

All device(s) in the list are in 'Copied' state.

 

 

20.  

Terminate the FLM session

From the Solutions Enabler control host:

 

Use the symrcopy terminate -migrate command to terminate the FLM migration for the devices specified by the FLM pair file. 

 

# symrcopy -f linux_dmp terminate -migrate

 

'Terminate' operation execution is in progress for the device list

in device file 'linux_dmp'. Please wait...

 

'Terminate' operation successfully executed for the device list

in device file 'linux_dmp'.

 

Terminating the FLM sessions in a Copied state performs the following:

·     ORS hot pull, donor update session is terminated

·     FLM source devices remain in a passive host access mode

·     FLM target devices remain in an active host access mode

 

 

21.  

Manually disable source paths in DMP

From the application host:

 

Manually disable the source paths for each DMP node involved in the FLM migration. This allows the source paths to be removed from the DMP configuration.

 

# vxdmpadm -f disable path=sdcs

# vxdmpadm -f disable path=sddy

# vxdmpadm -f disable path=sdda

# vxdmpadm -f disable path=sdeg

# vxdmpadm -f disable path=sdcv

# vxdmpadm -f disable path=sdeb

# vxdmpadm -f disable path=sddd

# vxdmpadm -f disable path=sdej

 

Use vxdmpadm getsubpaths to verify that the source paths have been manually disabled. Each disabled path should display a state of DISABLED(M). If the device’s states are not correct, examine the cause before proceeding.

 

The enclosure=<enclosure_name> parameter can be added to filter the display for a specific controller.

 

# vxdmpadm getsubpaths enclosure=emc2

NAME         STATE[A]   PATH-TYPE[M] DMPNODENAME  ENCLR-NAME   CTLR    ATTRS

================================================================================

sdci         ENABLED(A)   -          emc2_0150    emc2         c1        -

sdcm         ENABLED(A)   -          emc2_0150    emc2         c2        -

sdcs         DISABLED(M)  -          emc2_0150    emc2         c1        -

sddy         DISABLED(M)  -          emc2_0150    emc2         c2        -

sdcj         ENABLED(A)   -          emc2_0154    emc2         c1        -

sdcn         ENABLED(A)   -          emc2_0154    emc2         c2        -

sdda         DISABLED(M)  -          emc2_0154    emc2         c1        -

sdeg         DISABLED(M)  -          emc2_0154    emc2         c2        -

sdck         ENABLED(A)   -          emc2_0158    emc2         c1        -

sdco         ENABLED(A)   -          emc2_0158    emc2         c2        -

sdcv         DISABLED(M)  -          emc2_0158    emc2         c1        -

sdeb         DISABLED(M)  -          emc2_0158    emc2         c2        -

sdcl         ENABLED(A)   -          emc2_015c    emc2         c1        -

sdcp         ENABLED(A)   -          emc2_015c    emc2         c2        -

sddd         DISABLED(M)  -          emc2_015c    emc2         c1        -

sdej         DISABLED(M)  -          emc2_015c    emc2         c2        -

 

 

22.  

Remove masking for the source devices

From the Solutions Enabler control host:

 

For 5875 source array

Use the symaccess command to delete or modify a masking view to remove application host visibility for the VMAX source devices. Use the -unmap flag when deleting or modifying the masking view to unmap the devices as part of the Auto-provisioning change.

 

# symaccess -sid 624 delete view -name linux_flm_mv -unmap

 

Use the symaccess list command to verify that the source devices have been removed from all masking views. The view count should be zero (0) for each FLM source device.

 

# symaccess -sid 624 list -type storage -devs 04CA:04CD

 

Symmetrix ID          : 000192602624

 

Symm                                    Dev    View

Dev   Storage Group Name                Count  Count

----  --------------------------------  -----  -----

04CA  aix_flm_sg                            4      0

04CB  aix_flm_sg                            4      0

04CC  aix_flm_sg                            4      0

04CD  aix_flm_sg                            4      0

 

Use the symdev list –noport command to verify that the source 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 Not Visible            ???:? 10B:C8  2-Way Mir     N/Grp'd      RW     898

04CB Not Visible            ???:? 10A:D4  RAID-5        N/Grp'd      RW     898

04CC Not Visible            ???:? 10D:D1  2-Way Mir     N/Grp'd      RW     898

04CD Not Visible            ???:? 07D:D4  RAID-5        N/Grp'd      RW     898

 

For 5671 and 5773 source arrays

Use the symmask remove devs command to remove application-host visibility for the source devices.

 

# symmask -sid 076 -wwn 10000000c9538be2 -dir 3b -p 0 remove devs 014E:0151

 

# symmask -sid 076 -wwn 10000000c96ef1d7 -dir 14b -p 1 remove devs 014E:0151

 

# symmask -sid 076 refresh

 

Symmetrix FA/SE directors updated with contents of SymMask Database 000187490076

 

Use the symmaskdb list assignment command to verify that the source devices are no longer masked to the application host.

 

# symmaskdb -sid 76 list assignment -devs 014E:0151

 

Symmetrix ID : 000187490076

 

Device  Identifier        Type   Dir:P

------  ----------------  -----  ----------------

014E    500009720829011d  FIBRE  FA-3B:0

        5000097208290120  FIBRE  FA-14B:1

014F    500009720829011d  FIBRE  FA-3B:0

        5000097208290120  FIBRE  FA-14B:1

0150    500009720829011d  FIBRE  FA-3B:0

        5000097208290120  FIBRE  FA-14B:1

0151    500009720829011d  FIBRE  FA-3B:0

        5000097208290120  FIBRE  FA-14B:1

 

In this example, the only source device masking remaining is the storage-to-storage masking, which facilitates the FLM migration.

 

Use the symmask remove devs command to remove FLM target visibility for the source devices.

 

# symmask -sid 076 -dir 3b -p 0 -wwn 500009720829011d remove devs 014E:0151

 

# symmask -sid 076 -dir 14b -p 1 -wwn 5000097208290120 remove devs 014E:0151

 

# symmask -sid 076 refresh

 

Symmetrix FA/SE directors updated with contents of SymMask Database 000187490076

 

Use the symmaskdb list assignment command to verify that the source devices are no longer masked.

 

# symmaskdb -sid 076 list assignment -devs 014E:0151

 

No device masking database records could be found for the specified input parameters

 

Clean up the operating system device tree after removing the masking. For every removed source device path, run this command:

 

   #echo 1 > /sys/block/<source device path>/device/delete

 

Then rescan the operating system device tree by running the following command to each of the controllers connected to the source ports. (Replace the <x> with the corresponding controller number.)

 

  #echo “- - -“ > /sys/class/scsi_host/host<x>/scan

 

 

 

23.  

Perform a rescan to remove the source paths from the DMP configuration

From the application host:

 

Run vxdisk scandisks to remove the manually disabled source paths.

 

# vxdisk scandisks

 

 

24.  

Verify that the source device paths are removed from the DMP configuration

From the application host:

 

Use vxdmpadm getsubpaths to verify that the source paths are longer visible in the DMP configuration. FLM target device paths should all report an ENABLED state. There should be no FLM source paths visible. If the device states are not correct, examine the cause.

 

The enclosure=<enclosure_name> parameter can be added to filter the display for a specific controller.

 

# vxdmpadm getsubpaths enclosure=emc2

NAME         STATE[A]   PATH-TYPE[M] DMPNODENAME  ENCLR-NAME   CTLR    ATTRS

================================================================================

sdci         ENABLED(A)   -          emc2_0150    emc2         c1        -

sdcm         ENABLED(A)   -          emc2_0150    emc2         c2        -

sdcj         ENABLED(A)   -          emc2_0154    emc2         c1        -

sdcn         ENABLED(A)   -          emc2_0154    emc2         c2        -

sdck         ENABLED(A)   -          emc2_0158    emc2         c1        -

sdco         ENABLED(A)   -          emc2_0158    emc2         c2        -

sdcl         ENABLED(A)   -          emc2_015c    emc2         c1        -

sdcp         ENABLED(A)   -          emc2_015c    emc2         c2        -

 

 

25.  

Configure the DMP tunable parameters to FLM required values

From the application host:

 

Restore the modified DMP tunable parameters to their pre-migration values. This example returns the tunable parameter settings to their default values.

 

DMP tunable parameter

Default value

FLM required value

dmp_path_age

300

0

dmp_health_time

60

0

iopolicy (per DMP node name)

MinimumQ

MinimumQ

 

Modify the dmp_path_age tunable parameter back to its default value:

 

# vxdmpadm settune dmp_path_age=300

Tunable value will be changed immediately

 

Modify the dmp_health_time tunable parameter back to its default value:

 

# vxdmpadm settune dmp_health_time=60

Tunable value will be changed immediately

 

The iopolicy tunable parameter should be set to the default value. If the policy was set to a value other than the default, return the policy to the pre-migration value identified in step 1.

 

If necessary, modify the iopolicy tunable parameter per enclosure:

 

# vxdmpadm setattr enclosure emc1 iopolicy=<policy>

 

Verify that all required tunable parameters are set back to the default values.

 

 

# vxdmpadm gettune dmp_path_age

            Tunable               Current Value  Default Value

------------------------------    -------------  -------------

dmp_path_age                              0              300

 

# vxdmpadm gettune dmp_health_time

            Tunable               Current Value  Default Value

------------------------------    -------------  -------------

dmp_health_time                           0               60

 

To check the value of iopolicy tunable parameter per DMP node:

 

# vxdmpadm list dmpnode dmpnodename=emc2_0150

dmpdev          = emc2_0150

state           = enabled

enclosure       = emc2

cab-sno         = 000190100860

asl             = libvxemc.so

vid             = EMC

pid             = SYMMETRIX

array-name      = EMC

array-type      = A/A

iopolicy        = MinimumQ

avid            = 0150

lun-sno         = 6000150000

udid            = EMC%5FSYMMETRIX%5F000190100860%5F6000150000

dev-attr        = std

. . .

 

 

 

7Table of Contents

 

 

·       Performing Failback During Federated Live Migration

 

 

Overview

Perform the following steps to fail back during Federated Live Migration (FLM) on a stand-alone Linux application host with Veritas Storage Foundations for Linux.

 

! 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.5 Product Guide
  • EMC Solutions Enabler Symmetrix Array Management CLI 7.5 Product Guide
  • EMC Solutions Enabler Symmetrix Array Controls CLI 7.5 Product Guide

 

These documents can be obtained from EMC® Online Support at:

 http://support.EMC.com

 

 

26.   

Verify the FLM session is in state permitting failback

From the Solutions Enabler control host:

 

Use the symrcopy query command to verify that the FLM pair’s status is either CopyInProg or Copied.

 

# symrcopy -f linux_dmp query

 

Device File Name      : linux_dmp

 

       Control Device                  Remote Device      Flags      Status     Done

---------------------------- --------------------------- ------- -------------- ----

                   Protected

SID:symdev         Tracks    Identification           RI CDSHUTZ  CTL <=> REM    (%)

------------------ --------- ------------------------ -- ------- -------------- ----

000194900275:0195      75461 000190100860:0150        SD X..XXM. CopyInProg       45

000194900275:0295      76468 000190100860:0154        SD X..XXM. CopyInProg       44

000194900275:01FF      74423 000190100860:0158        SD X..XXM. CopyInProg       46

000194900275:02FF      78168 000190100860:015C        SD X..XXM. CopyInProg       43

 

Total              ---------

  Track(s)            304520

  MB(s)              19032.5

 

Legend:

R:  (Remote Device Vendor Identification)

  S = Symmetrix, C = Clariion, . = Unknown.

 

I:  (Remote Device Specification Identifier)

  D = Device Name, W = LUN WWN, World Wide Name.

 

Flags:

(C): X = The background copy setting is active for this pair.

     . = The background copy setting is not active for this pair.

(D): X = The session is a differential copy session.

     . = The session is not a differential copy session.

(S): X = The session is pushing data to the remote device(s).

     . = The session is pulling data from the remote device(s).

(H): X = The session is a hot copy session.

     . = The session is a cold copy session.

(U): X = The session has donor update enabled.

     . = The session does not have donor update enabled.

(T): M = The session is a migration session.

     R = The session is a RecoverPoint session.

     S = The session is a standard ORS session.

(Z): X = The session has front-end zero detection enabled.

     . = The session does not have front-end zero detection enabled.

(*): The failed session can be reactivated.

 

 

27.   

Fail back the FLM session and verify the failback

From the Solutions Enabler control host:

 

Use the symrcopy failback -migrate command to fail back the FLM session for the devices specified by the FLM pair file.

 

# symrcopy -f linux_dmp failback -migrate

 

'Failback' operation execution is in progress for the device list

in device file 'linux_dmp'. Please wait...

 

'Failback' operation successfully executed for the device list

in device file 'linux_dmp'.

 

Use the symrcopy query command to verify that the FLM pairs are in the Failedback status.

 

# symrcopy -f linux_dmp query

 

Device File Name      : linux_dmp

 

       Control Device                  Remote Device      Flags      Status     Done

---------------------------- --------------------------- ------- -------------- ----

                   Protected

SID:symdev         Tracks    Identification           RI CDSHUTZ  CTL <=> REM    (%)

------------------ --------- ------------------------ -- ------- -------------- ----

000194900275:0195          0 000190100860:0150        SD X..XXM. Failedback      N/A

000194900275:0295          0 000190100860:0154        SD X..XXM. Failedback      N/A

000194900275:01FF          0 000190100860:0158        SD X..XXM. Failedback      N/A

000194900275:02FF          0 000190100860:015C        SD X..XXM. Failedback      N/A

 

Total              ---------

  Track(s)            304520

  MB(s)              19032.5

. . .

 

28.   

Verify the failback on the application host

From the application host:

 

Use vxdmpadm getsubpaths to verify the failback. The failback sets the target devices to host access mode passive and the source devices to host access mode active. The passive target paths should report a state of DISABLED. If any paths, other than the expected paths, report a DISABLED state, examine the cause before continuing.

 

The enclosure=<enclosure_name> parameter can be added to filter the display for a specific controller.

 

# vxdmpadm getsubpaths enclosure=emc2

NAME         STATE[A]   PATH-TYPE[M] DMPNODENAME  ENCLR-NAME   CTLR    ATTRS

================================================================================

sdci         ENABLED(A)   -          emc2_0150    emc2         c1        -

sdcm         ENABLED(A)   -          emc2_0150    emc2         c2        -

sdcs         DISABLED     -          emc2_0150    emc2         c1        -

sddy         DISABLED     -          emc2_0150    emc2         c2        -

sdcj         ENABLED(A)   -          emc2_0154    emc2         c1        -

sdcn         ENABLED(A)   -          emc2_0154    emc2         c2        -

sdda         DISABLED     -          emc2_0154    emc2         c1        -

sdeg         DISABLED     -          emc2_0154    emc2         c2        -

sdck         ENABLED(A)   -          emc2_0158    emc2         c1        -

sdco         ENABLED(A)   -          emc2_0158    emc2         c2        -

sdcv         DISABLED     -          emc2_0158    emc2         c1        -

sdeb         DISABLED     -          emc2_0158    emc2         c2        -

sdcl         ENABLED(A)   -          emc2_015c    emc2         c1        -

sdcp         ENABLED(A)   -          emc2_015c    emc2         c2        -

sddd         DISABLED     -          emc2_015c    emc2         c1        -

sdej         DISABLED     -          emc2_015c    emc2         c2        -

 

 

29.   

Terminate the FLM session

From the Solutions Enabler control host:

 

Use the symrcopy terminate -migrate command to terminate the FLM migration for the devices specified by the FLM pair file. 

 

# symrcopy -f linux_dmp terminate -migrate

 

'Terminate' operation execution is in progress for the device list

in device file 'linux_dmp'. Please wait...

 

'Terminate' operation successfully executed for the device list

in device file 'linux_dmp'.

 

Terminating the FLM sessions in a Failedback state performs the following:

·     ORS hot pull donor update session is terminated

·     FLM source devices remain in an active host access mode

·     FLM target devices remain in a passive host access mode

 

 


30.   

Manually disable the target paths in DMP

From the application host:

 

Manually disable the target paths for each DMP node involved in the FLM migration. This allows the target paths to be removed from the DMP configuration.

 

# vxdmpadm -f disable path=sdcs

# vxdmpadm -f disable path=sddy

# vxdmpadm -f disable path=sdda

# vxdmpadm -f disable path=sdeg

# vxdmpadm -f disable path=sdcv

# vxdmpadm -f disable path=sdeb

# vxdmpadm -f disable path=sddd

# vxdmpadm -f disable path=sdej

 

Use vxdmpadm getsubpaths to verify that the target paths have been manually disabled. Each disabled path should display a state of DISABLED(M). If the device states are not correct, examine the cause before proceeding.

 

The enclosure=<enclosure_name> parameter can be added to filter the display for a specific controller.

 

# vxdmpadm getsubpaths enclosure=emc2

 

NAME         STATE[A]   PATH-TYPE[M] DMPNODENAME  ENCLR-NAME   CTLR    ATTRS

================================================================================

sdci         ENABLED(A)    -          emc2_0150    emc2         c1        -

sdcm         ENABLED(A)    -          emc2_0150    emc2         c2        -

sdcs         DISABLED(M)   -          emc2_0150    emc2         c1        -

sddy         DISABLED(M)   -          emc2_0150    emc2         c2        -

sdcj         ENABLED(A)    -          emc2_0154    emc2         c1        -

sdcn         ENABLED(A)    -          emc2_0154    emc2         c2        -

sdda         DISABLED(M)   -          emc2_0154    emc2         c1        -

sdeg         DISABLED(M)   -          emc2_0154    emc2         c2        -

sdck         ENABLED(A)    -          emc2_0158    emc2         c1        -

sdco         ENABLED(A)    -          emc2_0158    emc2         c2        -

sdcv         DISABLED(M)   -          emc2_0158    emc2         c1        -

sdeb         DISABLED(M)   -          emc2_0158    emc2         c2        -

sdcl         ENABLED(A)    -          emc2_015c    emc2         c1        -

sdcp         ENABLED(A)    -          emc2_015c    emc2         c2        -

sddd         DISABLED(M)   -          emc2_015c    emc2         c1        -

sdej         DISABLED(M)   -          emc2_015c    emc2         c2        -

 

 

31.   

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 275 delete view -name linux_dmp_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 275 list -type storage -devs 0195,0295,01FF,02FF

 

Symmetrix ID          : 000194900275

 

Symm                                    Dev    View

Dev   Storage Group Name                Count  Count

----  --------------------------------  -----  -----

0195  linux_dmp_sg                          4      0

0295  linux_dmp_sg                          4      0

01FF  linux_dmp_sg                          4      0

02FF  linux_dmp_sg                          4      0

 

Use the symdev list –noport command to verify that the target devices are not mapped. Use –range to filter on a specific range of devices.

 

# symdev -sid 275 list -noport

 

Symmetrix ID: 000194900275

 

        Device Name           Directors                  Device

--------------------------- ------------- -------------------------------------

                                                                           Cap

Sym  Physical               SA :P DA :IT  Config        Attribute    Sts   (MB)

--------------------------- ------------- -------------------------------------

 

0195 Not Visible            ???:? 08A:D6  2-Way Mir     N/Grp'd      RW    8631

. . .

01FF Not Visible            ???:? 07A:C0  RAID-5        N/Grp'd  (M) RW   34523

. . .

0295 Not Visible            ???:? 07B:D4  RAID-6        N/Grp'd      RW    8631

. . .

02FF Not Visible            ???:?  NA:NA  TDEV          N/Grp'd  (M) RW   34523

. . .

 

Clean up the operating system device tree after removing the masking. For every removed target device path, run this command:

 

   #echo 1 > /sys/block/<target device path>/device/delete

 

Then rescan the operating system device tree by running the following command to each of the controllers connected to the VMAX target ports. (Replace the <x> with the controller number.)

 

  #echo “- - -“ > /sys/class/scsi_host/host<x>/scan

 

 

32.   

Perform a rescan to remove the target paths from the DMP configuration

From the application host:

 

Run vxdisk scandisks to remove the manually disabled target paths.

 

# vxdisk scandisks

 

 

33.   

Verify that the target device paths are removed from the DMP configuration

From the application host:

 

Use vxdmpadm getsubpaths to verify that the target paths are no longer visible in the DMP configuration. FLM source device paths should all report an ENABLED state. There should be no FLM target paths visible. If the device states are not correct, examine the cause.

 

The enclosure=<enclosure_name> parameter can be added to filter the display for a specific controller.

 

# vxdmpadm getsubpaths enclosure=emc2

 

NAME         STATE[A]   PATH-TYPE[M] DMPNODENAME  ENCLR-NAME   CTLR    ATTRS

================================================================================

sdci         ENABLED(A)   -          emc2_0150    emc2         c1        -

sdcm         ENABLED(A)   -          emc2_0150    emc2         c2        -

sdcj         ENABLED(A)   -          emc2_0154    emc2         c1        -

sdcn         ENABLED(A)   -          emc2_0154    emc2         c2        -

sdck         ENABLED(A)   -          emc2_0158    emc2         c1        -

sdco         ENABLED(A)   -          emc2_0158    emc2         c2        -

sdcl         ENABLED(A)   -          emc2_015c    emc2         c1        -

sdcp         ENABLED(A)   -          emc2_015c    emc2         c2        -

 

 

34.   

Remove the external identity

From the Solutions Enabler control host:

 

Use the symconfigure command to remove the device’s 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 275 commit << EOL

> set dev 0195 identity = no identity;

> set dev 0295 identity = no identity;

> set dev 01FF identity = no identity;

> set dev 02FF identity = no identity;

> EOL

 

A Configuration Change operation is in progress. Please wait...

 

    Establishing a configuration change session...............Established.

    Processing symmetrix 000194900275

    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 identity of the source devices. The external identity should now reflect the native identity of the FLM target device.

 

# symdev -sid 275 list -identity

 

Symmetrix ID: 000194900275

 

              Device               FLG            External Identity

---------------------------------- --- ----------------------------------------

Sym  Physical    Config        Sts IG  Array ID       Num   Ser Num    Cap (MB)

---------------------------------- --- ----------------------------------------

 

. . .

0195 Not Visible 2-Way Mir     RW  .X  000194900275   00195 7500195000     8625

. . .

01FF Not Visible RAID-5        RW  .X  000194900275   001FF 75001FF000     8625

. . .

0295 Not Visible RAID-6        RW  .X  000194900275   00295 7500295000     8625

. . .

02FF Not Visible TDEV          RW  .X  000194900275   002FF 75002FF000     8625

. . .

 

Legend:

  Flags:

   (I)dentity : X = The device has a non-native external identity set

                . = The device does not have an external identity set

   (G)eometry : X = The device has a user defined geometry

                . = The device does not have a user defined geometry

 

 

35.   

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 275 commit << EOL

> set dev 0195 geometry = no geometry;

> set dev 0295 geometry = no geometry;

> set dev 01FF geometry = no geometry;

> set dev 02FF geometry = no geometry;

> EOL

 

A Configuration Change operation is in progress. Please wait...

 

    Establishing a configuration change session...............Established.

    Processing symmetrix 000194900275

    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 listidentity 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 275 list -identity

 

Symmetrix ID: 000194900275

 

              Device               FLG            External Identity

---------------------------------- --- ----------------------------------------

Sym  Physical    Config        Sts IG  Array ID       Num   Ser Num    Cap (MB)

---------------------------------- --- ----------------------------------------

 

. . .

0195 Not Visible 2-Way Mir     RW  ..  000194900275   00195 7500195000     8631

. . .

01FF Not Visible RAID-5        RW  ..  000194900275   001FF 75001FF000    34523

. . .

0295 Not Visible RAID-6        RW  ..  000194900275   00295 7500295000     8631

. . .

02FF Not Visible TDEV          RW  ..  000194900275   002FF 75002FF000    34523

. . .

 

Legend:

  Flags:

   (I)dentity : X = The device has a non-native external identity set

                . = The device does not have an external identity set

   (G)eometry : X = The device has a user defined geometry

                . = The device does not have a user defined geometry

 

 

36.   

Reset the FLM target devices host access mode to active

From the Solutions Enabler control host:

 

After the failback, the FLM target devices are left in a passive host access mode. Use the symdev host_active command to change the host access mode from passive to active. Use –range to specify a range of devices.

 

# symdev -sid 275 host_active 0195

 

'Host Active' Device operation successfully completed for the device.

# symdev -sid 275 host_active 01FF

 

'Host Active' Device operation successfully completed for the device.

# symdev -sid 275 host_active 0295

 

'Host Active' Device operation successfully completed for the device.

# symdev -sid 275 host_active 02FF

 

'Host Active' Device operation successfully completed for the device.

 

 

 

7Table of Contents

 

 

·       Removing External Identity and Geometry following Federated Live Migration

 

 

Overview

Perform the following steps to remove the external identity and geometry following a Federated Live Migration (FLM) on a Linux application host with Veritas Storage Foundations for Linux.

 

! 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.5 Product Guide
  • EMC Solutions Enabler Symmetrix Array Management CLI 7.5 Product Guide
  • EMC Solutions Enabler Symmetrix Array Controls CLI 7.5 Product Guide

 

These documents can be obtained from EMC® Online Support at:

 http://support.EMC.com

 

 

 

37.  

Shut down all host applications on the application server with a dependency on the VMAX FLM target devices presenting the source device’s external identity

All I/O to the VMAX FLM target devices must be halted because the devices will be removed to facilitate the removal of the source device’s external identity.

 

 

38.  

Remove the target paths in DMP

From the application host:

 

Use vxdmpadm getsubpaths to identify all of the target device paths.

 

# vxdmpadm getsubpaths enclosure=emc2

NAME         STATE[A]   PATH-TYPE[M] DMPNODENAME  ENCLR-NAME   CTLR    ATTRS

================================================================================

sdci         ENABLED(A)   -          emc2_0150    emc2         c1        -

sdcm         ENABLED(A)   -          emc2_0150    emc2         c2        -

sdcj         ENABLED(A)   -          emc2_0154    emc2         c1        -

sdcn         ENABLED(A)   -          emc2_0154    emc2         c2        -

sdck         ENABLED(A)   -          emc2_0158    emc2         c1        -

sdco         ENABLED(A)   -          emc2_0158    emc2         c2        -

sdcl         ENABLED(A)   -          emc2_015c    emc2         c1        -

sdcp         ENABLED(A)   -          emc2_015c    emc2         c2        -

 

Remove the Veritas DMP nodes for the target devices with their identity set.

 

# vxdisk rm emc2_0150

# vxdisk rm emc2_0154

# vxdisk rm emc2_0158

# vxdisk rm emc2_015c

 

 

39.  

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 275 delete view -name linux_dmp_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 275 list -type storage -devs 0195,0295,01FF,02FF

 

Symmetrix ID          : 000194900275

 

Symm                                    Dev    View

Dev   Storage Group Name                Count  Count

----  --------------------------------  -----  -----

0195  linux_dmp_sg                          4      0

0295  linux_dmp_sg                          4      0

01FF  linux_dmp_sg                          4      0

02FF  linux_dmp_sg                          4      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 275 list -noport

 

Symmetrix ID: 000194900275

 

        Device Name           Directors                  Device

--------------------------- ------------- -------------------------------------

                                                                           Cap

Sym  Physical               SA :P DA :IT  Config        Attribute    Sts   (MB)

--------------------------- ------------- -------------------------------------

 

0195 Not Visible            ???:? 08A:D6  2-Way Mir     N/Grp'd      RW    8631

. . .

01FF Not Visible            ???:? 07A:C0  RAID-5        N/Grp'd  (M) RW   34523

. . .

0295 Not Visible            ???:? 07B:D4  RAID-6        N/Grp'd      RW    8631

. . .

02FF Not Visible            ???:?  NA:NA  TDEV          N/Grp'd  (M) RW   34523

. . .

 

 

40.  

Clean up Linux and Veritas

From the application host:

 

Perform a host SCSI rescan, if appropriate, to remove LUNs.

 

Reference the EMC Host Connectivity Guide for Linux to determine the appropriate method for Linux online rescan/removal, based on your kernel and drivers.

 

Run vxconfigd -k to kill and restart the Veritas configuration daemon.

 

# vxconfigd -k

 

 

41.  

Remove the external identity

From the Solutions Enabler control host:

 

Use the symconfigure command to remove the device’s 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 275 commit << EOL

> set dev 0195 identity = no identity;

> set dev 0295 identity = no identity;

> set dev 01FF identity = no identity;

> set dev 02FF identity = no identity;

> EOL

 

A Configuration Change operation is in progress. Please wait...

 

    Establishing a configuration change session...............Established.

    Processing symmetrix 000194900275

    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 identity of the source devices. The external identity should now reflect the native identity of the FLM target device.

 

# symdev -sid 275 list -identity

 

Symmetrix ID: 000194900275

 

              Device               FLG            External Identity

---------------------------------- --- ----------------------------------------

Sym  Physical    Config        Sts IG  Array ID       Num   Ser Num    Cap (MB)

---------------------------------- --- ----------------------------------------

 

. . .

0195 Not Visible 2-Way Mir     RW  .X  000194900275   00195 7500195000     8625

. . .

01FF Not Visible RAID-5        RW  .X  000194900275   001FF 75001FF000     8625

. . .

0295 Not Visible RAID-6        RW  .X  000194900275   00295 7500295000     8625

. . .

02FF Not Visible TDEV          RW  .X  000194900275   002FF 75002FF000     8625

. . .

 

Legend:

  Flags:

   (I)dentity : X = The device has a non-native external identity set

                . = The device does not have an external identity set

   (G)eometry : X = The device has a user defined geometry

                . = The device does not have a user defined geometry

 

 

42.  

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 275 commit << EOL

> set dev 0195 geometry = no geometry;

> set dev 0295 geometry = no geometry;

> set dev 01FF geometry = no geometry;

> set dev 02FF geometry = no geometry;

> EOL

 

A Configuration Change operation is in progress. Please wait...

 

    Establishing a configuration change session...............Established.

    Processing symmetrix 000194900275

    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 275 list -identity

 

Symmetrix ID: 000194900275

 

              Device               FLG            External Identity

---------------------------------- --- ----------------------------------------

Sym  Physical    Config        Sts IG  Array ID       Num   Ser Num    Cap (MB)

---------------------------------- --- ----------------------------------------

 

. . .

0195 Not Visible 2-Way Mir     RW  ..  000194900275   00195 7500195000     8631

. . .

01FF Not Visible RAID-5        RW  ..  000194900275   001FF 75001FF000    34523

. . .

0295 Not Visible RAID-6        RW  ..  000194900275   00295 7500295000     8631

. . .

02FF Not Visible TDEV          RW  ..  000194900275   002FF 75002FF000    34523

. . .

 

Legend:

  Flags:

   (I)dentity : X = The device has a non-native external identity set

                . = The device does not have an external identity set

   (G)eometry : X = The device has a user defined geometry

                . = The device does not have a user defined geometry

 

 

43.  

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.

 

# symaccess -sid 275 create view -name linux_dmp_mv \

>                                -ig linux_dmp_ig   \

>                                -pg linux_dmp_pg   \

>                                -sg linux_dmp_sg

 

Use the symaccess show view command to verify that the target devices are properly configured in the Auto-provisioning group.

 

# symaccess -sid 275 show view linux_dmp_mv

 

Symmetrix ID          : 000194900275

 

Masking View Name     : linux_dmp_mv

Last updated at       : 06:35:18 PM on Fri Apr 01,2011

 

Initiator Group Name  : linux_dmp_ig

 

   Host Initiators

     {

       WWN  : 210000e08b8a556e [alias: 210000e08b8a556e/210000e08b8a556e]

       WWN  : 210100e08baa556e [alias: 210100e08baa556e/210100e08baa556e]

     }

 

Port Group Name       : linux_dmp_pg

 

   Director Identification

     {

       FA-7E:0

       FA-8E:0

     }

 

Storage Group Name    : linux_dmp_sg

 

Sym Dev                                 Host

Name    Dir:P  Physical Device Name      Lun  Attr  Cap(MB)

------  -----  -----------------------  ----  ----  -------

0195    07E:0  Not Visible                 1           8631

        08E:0  Not Visible                 1

01FF    07E:0  Not Visible                 2  (M)     34523

        08E:0  Not Visible                 2  (M)

0295    07E:0  Not Visible                 3           8631

        08E:0  Not Visible                 3

02FF    07E:0  Not Visible                 4  (M)     34523

        08E:0  Not Visible                 4  (M)

-------

Total Capacity                                        34524