How to manage EMC BCV devices on AIX with Veritas Volume Manager (VxVM) and Veritas DMP with VxVM 6.0.5 and 6.1.0.100 onwards
Article ID: 100038571
Updated On:
Description
Description
This documents attempts to explain the "enhanced" recommended configuration steps in relation to EMC BCV devices on AIX with Veritas Volume Manager (VxVM) and Veritas DMP when running VxVM 6.0.5 and 6.1.0.100 onwards.
By default the TimeFinder (EMC BCV) devices will be created by `cfgmgr` in a "Defined" state. This is done to ensure that there is no contention trying to make a TimeFinder (EMC BCV) and another SYMMETRIX device with the same pvid "Available" simultaneously during the system restart process.
TimeFinder (EMC BCV) device states can be manually adjusted to report an "Available" or "Defined" status by the use of two EMC scripts "mkbcv" and "rmbcv" respectively.
Following a system restart, the EMC utility "mkbcv" needs to be executed to convert the BCV lun(s) from a "Defined" to an "Available" state. The VxVM disk details should then be refereshed by running "vxdisk scandisks".
# /usr/lpp/EMC/Symmetrix/bin/mkbcv -a
Sample Configuration
In this instance, the source EMC luns consist of 5 x EMC standard (STD) devices associated with 5 x EMC BCV devices for which must also be associated with the same EMC Symmetrix ID (SID).
# vxdisk -eo alldgs list
DEVICE TYPE DISK GROUP STATUS OS_NATIVE_NAME ATTR
emc1_0191 auto:none - - online invalid hdisk86 lun RAID
emc1_0192 auto:none - - online invalid hdisk87 lun RAID
emc1_0193 auto:none - - online invalid hdisk88 lun RAID
emc1_0194 auto:none - - online invalid hdisk84 lun RAID
emc1_0199 auto:none - - online invalid hdisk90 lun RAID
emc1_0235 auto:none - - online invalid hdisk40 lun bcv
emc1_0236 auto:none - - online invalid hdisk41 lun bcv
emc1_0237 auto:none - - online invalid hdisk6 lun bcv
emc1_0238 auto:none - - online invalid hdisk26 lun bcv
emc1_0239 auto:none - - online invalid hdisk44 lun bcv
Intelligent LUNs
When using Dynamic Multi-Pathing (DMP) as the managing multi-pathing driver, DMP can expose extended attribute characteristics for specific storage arrays. The array based attribute content is not exposed when using third-party drivers (TPD), i.e. EMC PowerPath, MPxIO and MPIO. The DMP extended attributes or flags are discovered by the Device Discovery Layer (DDL) corresponding to a DMP LUN or Disk.
Each LUN can have one or more of these extended attributes. The DDL discovers the extended attributes during the device discovery activity and by using the appropriate array support library (ASL) for the specific array.
The array intelligence is written within the ASL.
Some arrays provide a way to dynamically change the properties of LUNs.
For example, the EMC Symmetrix array allows write-protected/write-disabled (WD|read-only), not-ready (NR) and read-write (RW) enabled LUN attribute content to be exposed to DMP.
This is possible by using the EMC specific ASL to extract disk based content from defined areas on the disk via a SCSI inquiry operation.
As long as the disk is capable of presenting LUN specific content using SCSI inquiry commands, the array based ASL can be enhanced to expose such value add content.
In certain cases, such device types as EMC BCV (Hardware Clone) and SRDF (Hardware Replicated) can remain online as DMP is fully aware of the LUN characteristics via the intelligence provided via the EMC ASL.
The DMP extended attribute content can be displayed in many ways for such intelligent storage arrays using the VxVM "vxdisk -e list" CLI command, and in later versions using the "vxdisk -px LIST_CLONE list" command.
With such intelligent device types, the DMP extended attribute may still require a manual refresh using the VxVM "vxdisk scandisks" CLI command.
Once the device status reflects the required state, DMP should be manually updated with the new LUN details to ensure the appropriate VxVM command outputs do reflect the current LUN characteristics.
Steps
1.] The H/W Clone/Replicate device state is being intentionally modified/changed.
2.] The H/W related activity i s complete .
3.] Refresh VxVM and DMP extended attribute content.
# vxdisk scandisks
In a clustered environment, the manual refresh of the extended attributes needs to be performed across all nodes in the cluster.
Note: With the interoperability enhancement included in VxVM 6.0.5 and 6.1.0.100 for AIX, the user no longer needs to offline or place BCV devices in a "Defined" state whilst the BCV devices are in an established Not-Ready (NR) state.
Fig 1.0
EMC BCV Configuration Steps with VxVM
1.] Prepare disk for VxVM use:
# vxdisksetup -fi emc1_0191
# vxdisksetup -fi emc1_0192
# vxdisksetup -fi emc1_0193
# vxdisksetup –fi emc1_0194
# vxdisksetup –fi emc1_0199
For Loop Example:
# for disk in emc1_0191 emc1_0192 emc1_0193 emc1_0194 emc1_0199
> do
> echo "Preparing disk: $disk"
> /etc/vx/bin/vxdisksetup -fi $disk
> done
Preparing disk: emc1_0191
Preparing disk: emc1_0192
Preparing disk: emc1_0193
Preparing disk: emc1_0194
Preparing disk: emc1_0199
2.] Create VxVM DiskGroup:
# vxdg init datadg 0191=emc1_0191 0192=emc1_0192 0193=emc1_0193 0194=emc1_0194 0199=emc1_0199
# vxdisk -eo alldgs list
DEVICE TYPE DISK GROUP STATUS OS_NATIVE_NAME ATTR
emc1_0191 auto:cdsdisk 0191 datadg online hdisk86 lun RAID
emc1_0192 auto:cdsdisk 0192 datadg online hdisk87 lun RAID
emc1_0193 auto:cdsdisk 0193 datadg online hdisk88 lun RAID
emc1_0194 auto:cdsdisk 0194 datadg online hdisk84 lun RAID
emc1_0199 auto:cdsdisk 0199 datadg online hdisk90 lun RAID
emc1_0235 auto:none - - online invalid hdisk40 lun bcv
emc1_0236 auto:none - - online invalid hdisk41 lun bcv
emc1_0237 auto:none - - online invalid hdisk6 lun bcv
emc1_0238 auto:none - - online invalid hdisk26 lun bcv
emc1_0239 auto:none - - online invalid hdisk44 lun bcv
3.] Create EMC DeviceGroup using the EMC standard (std) devices:
# symdg create bcv_datadg
# symld -sid 414 -g bcv_datadg add dev 0191 DEV0191
# symld -sid 414 -g bcv_datadg add dev 0192 DEV0192
# symld -sid 414 -g bcv_datadg add dev 0193 DEV0193
# symld -sid 414 -g bcv_datadg add dev 0194 DEV0194
# symld -sid 414 -g bcv_datadg add dev 0199 DEV0199
4.] Add the EMC BCV devices to the same EMC DeviceGroup:
Identify the EMC BCV SYMDEVs
The DMP extended attribute content can be used to expose specific EMC device type content:
# vxdisk -eo alldgs list | grep -w bcv
emc1_0235 auto:none - - online invalid hdisk40 lun bcv
emc1_0236 auto:none - - online invalid hdisk41 lun bcv
emc1_0237 auto:none - - online invalid hdisk6 lun bcv
emc1_0238 auto:none - - online invalid hdisk26 lun bcv
emc1_0239 auto:none - - online invalid hdisk44 lun bcv
Note: The EMC BCV (target) LUN size must be the same size of the source (STD) LUN.
# vxdisk -px LIST_DMP -u g -x DDL_DEVICE_ATTR list
DEVICE NUM_PATHS LUN_SERIAL_NO CAB_SERIAL_NO ENCLOSURE_NAME ATYPE PHYS_CTLR_NAME LUN_SIZE DDL_DEVICE_ATTR
emc1_0191 4 1400191000 000290301414 emc1 A/A 07-09-02 3.05g lun,RAID
emc1_0192 4 1400192000 000290301414 emc1 A/A 07-09-02 3.05g lun,RAID
emc1_0193 4 1400193000 000290301414 emc1 A/A 07-09-02 3.05g lun,RAID
emc1_0194 4 1400194000 000290301414 emc1 A/A 07-09-02 3.05g lun,RAID
emc1_0199 4 1400199000 000290301414 emc1 A/A 07-09-02 3.05g lun,RAID
emc1_0235 4 1400235000 000290301414 emc1 A/A 07-09-02 3.05g lun,bcv
emc1_0236 4 1400236000 000290301414 emc1 A/A 07-09-02 3.05g lun,bcv
emc1_0237 4 1400237000 000290301414 emc1 A/A 07-09-02 3.05g lun,bcv
emc1_0238 4 1400238000 000290301414 emc1 A/A 07-09-02 3.05g lun,bcv
emc1_0239 4 1400239000 000290301414 emc1 A/A 07-09-02 3.05g lun,bcv
# symbcv -sid 414 -g bcv_datadg associate dev 0235 BCV0235
# symbcv -sid 414 -g bcv_datadg associate dev 0236 BCV0236
# symbcv -sid 414 -g bcv_datadg associate dev 0237 BCV0237
# symbcv -sid 414 -g bcv_datadg associate dev 0238 BCV0238
# symbcv -sid 414 -g bcv_datadg associate dev 0239 BCV0239
5.] Confirm the EMC DeviceGroup has the same number of source and BCV devices:
# symdg list
D E V I C E G R O U P S
Flags Number of
Name Type VC Symmetrix ID Devs GKs BCVs VDEVs TGTs
GoofyDg RDF1 YN 000290301414 4 0 0 0 0
PlutoDg RDF2 YN 000290301414 6 0 6 0 0
bcv_datadg REGULAR YN 000290301414 5 0 5 0 0
Legend:
Flags:
V(alid DG) : Y = Valid, N = Invalid, - = N/A
(In) C(g) : Y = Contained by a CG, N = Not contained by a CG, - = N/A
# symdg show bcv_datadg
Group Name: bcv_datadg
Group Type : REGULAR
Device Group in GNS : No
Valid : Yes
Symmetrix ID : 000290301414
Group Creation Time : Tue Sep 30 16:18:29 2014
Vendor ID : EMC Corp
Application ID : SYMCLI
Number of STD Devices in Group : 5
Number of Associated GK's : 0
Number of Locally-associated BCV's : 5
Number of Locally-associated VDEV's : 0
Number of Locally-associated TGT's : 0
Number of Remotely-associated VDEV's(STD RDF): 0
Number of Remotely-associated BCV's (STD RDF): 0
Number of Remotely-associated TGT's(TGT RDF) : 0
Number of Remotely-associated BCV's (BCV RDF): 0
Number of Remotely-assoc'd RBCV's (RBCV RDF) : 0
Number of Remotely-assoc'd BCV's (Hop-2 BCV) : 0
Number of Remotely-assoc'd VDEV's(Hop-2 VDEV): 0
Number of Remotely-assoc'd TGT's (Hop-2 TGT) : 0
Number of Composite Groups : 0
Composite Group Names : N/A
Standard (STD) Devices (5):
{
----------------------------------------------------------------------------------
Sym Device Cap
LdevName PdevName Dev Config Att. Sts (MB)
----------------------------------------------------------------------------------
DEV0191 /dev/rhdisk61 0191 RAID-5 RW 3125
DEV0192 /dev/rhdisk62 0192 RAID-5 RW 3125
DEV0193 /dev/rhdisk63 0193 RAID-5 RW 3125
DEV0194 /dev/rhdisk64 0194 RAID-5 RW 3125
DEV0199 /dev/rhdisk65 0199 RAID-5 RW 3125
}
BCV Devices Locally-associated (5):
{
----------------------------------------------------------------------------------
Sym Device Cap
LdevName PdevName Dev Config Att. Sts (MB)
----------------------------------------------------------------------------------
BCV0235 /dev/rhdisk23 0235 BCV RW 3125
BCV0236 /dev/rhdisk24 0236 BCV RW 3125
BCV0237 /dev/rhdisk25 0237 BCV RW 3125
BCV0238 /dev/rhdisk26 0238 BCV RW 3125
BCV0239 /dev/rhdisk27 0239 BCV RW 3125
}
6.] The relationship between the STD and BCV LUNs need to be paired, before data is transferred.
# symmir -g bcv_datadg query
Cannot proceed because the device does not have any BCV pairing relationship
Device group 'bcv_datadg' does not have any standard devices that are BCV paired.
7.] The first time the STD and BCV LUNs are paired, a full establish is always required.
# symmir -g bcv_datadg -v -full establish
Execute 'Full Establish' operation for device group
'bcv_datadg' (y/[n]) ? y
'Full Establish' operation execution is in progress for
device group 'bcv_datadg'. Please wait...
SELECTING Standard devices in the group:
Device: 0191 [SELECTED]
Device: 0192 [SELECTED]
Device: 0193 [SELECTED]
Device: 0194 [SELECTED]
Device: 0199 [SELECTED]
SELECTING BCV devices associated with the group:
Device: 0235 [SELECTED]
Device: 0236 [SELECTED]
Device: 0237 [SELECTED]
Device: 0238 [SELECTED]
Device: 0239 [SELECTED]
PAIRING of Standard and BCV devices:
Devices: 0191(S) - 0235(B) [PAIRED]
Devices: 0192(S) - 0236(B) [PAIRED]
Devices: 0193(S) - 0237(B) [PAIRED]
Devices: 0194(S) - 0238(B) [PAIRED]
Devices: 0199(S) - 0239(B) [PAIRED]
STARTING a BCV 'ESTABLISH' operation.
The BCV 'ESTABLISH' operation SUCCEEDED.
'Full Establish' operation successfully initiated for device group
'bcv_datadg'.
8.] How to query the STD and BCV LUNs are fully synchronized:
# symmir -g bcv_datadg query
Device Group (DG) Name: bcv_datadg
DG's Type : REGULAR
DG's Symmetrix ID : 000290301414
Standard Device BCV Device State
-------------------------- ------------------------------------- ------------
Inv. Inv.
Logical Sym Tracks Logical Sym Tracks STD <=> BCV
-------------------------- ------------------------------------- ------------
DEV0191 0191 0 BCV0235 0235 * 0 Synchronized
DEV0192 0192 0 BCV0236 0236 * 0 Synchronized
DEV0193 0193 0 BCV0237 0237 * 0 Synchronized
DEV0194 0194 0 BCV0238 0238 * 0 Synchronized
DEV0199 0199 0 BCV0239 0239 * 0 Synchronized
Total ------- -------
Track(s) 0 0
MB(s) 0.0 0.0
Legend:
(*): The paired BCV device is associated with this group.
9.] if the DMP extended attributes are manually refreshed during the BCV resync operation, the BCV LUNs will report a Not-Ready (NR) device state:
# vxdisk scandisks
When the DMP extended attribute content is refreshed, the BCV luns will report an NR state:
# vxdisk -eo alldgs list | grep -w bcv
emc1_0235 auto - - error hdisk40 lun bcv nr WD
emc1_0236 auto - - error hdisk41 lun bcv nr WD
emc1_0237 auto - - error hdisk6 lun bcv nr WD
emc1_0238 auto - - error hdisk26 lun bcv nr WD
emc1_0239 auto - - error hdisk44 lun bcv nr WD
It is now possible to list hardware clone and replicated based content using the VxVM "vxdisk -px LIST_CLONE list" command when using Dynamic Multi-Pathing (DMP) . The attribute view is just one of the many new attribute views provided by the "vxdisk -px list" interface.
# vxdisk -px LIST_CLONE-u g list
DEVICE DG_NAME REPLICATED REPLICATED_TYPE HARDWARE_MIRROR LUN_SIZE NR_DEVICE DEVICE_TYPE DDL_DEVICE_ATTR
emc1_0191 datadg - - no 3.05g no - lun,RAID+Mirr
emc1_0192 datadg - - no 3.05g no - lun,RAID+Mirr
emc1_0193 datadg - - no 3.05g no - lun,RAID+Mirr
emc1_0194 datadg - - no 3.05g no - lun,RAID+Mirr
emc1_0199 datadg - - no 3.05g no - lun,RAID+Mirr
emc1_0235 - - - yes 3.05g yes - lun,bcv,nr,WD
emc1_0236 - - - yes 3.05g yes - lun,bcv,nr,WD
emc1_0237 - - - yes 3.05g yes - lun,bcv,nr,WD
emc1_0238 - - - yes 3.05g yes - lun,bcv,nr,WD
emc1_0239 - - - yes 3.05g yes - lun,bcv,nr,WD
Note: The HARDWARE_MIRROR attribute denotes that the BCV luns are a H/W CLONE.
10.] How to split the STD and BCV pairings, now the BCV LUNs are fully synchronized:
# symmir -g bcv_datadg split
Execute 'Split' operation for device group
'bcv_datadg' (y/[n]) ? y
'Split' operation execution is in progress for
device group 'bcv_datadg'. Please wait...
'Split' operation successfully executed for device group
'bcv_datadg'.
11.] How to verify that the BCV LUNs are in a split state (available for import):
# symmir -g bcv_datadg -split verify
All devices in the group 'bcv_datadg' are in 'Split' state.
12.] How to query the BCV LUNs are in a split state (ready for import)
# symmir -g bcv_datadg query
Device Group (DG) Name: bcv_datadg
DG's Type : REGULAR
DG's Symmetrix ID : 000290301414
Standard Device BCV Device State
-------------------------- ------------------------------------- ------------
Inv. Inv.
Logical Sym Tracks Logical Sym Tracks STD <=> BCV
-------------------------- ------------------------------------- ------------
DEV0191 0191 0 BCV0235 0235 * 0 Split
DEV0192 0192 0 BCV0236 0236 * 0 Split
DEV0193 0193 0 BCV0237 0237 * 0 Split
DEV0194 0194 0 BCV0238 0238 * 0 Split
DEV0199 0199 0 BCV0239 0239 * 0 Split
Total ------- -------
Track(s) 0 0
MB(s) 0.0 0.0
Legend:
(*): The paired BCV device is associated with this group.
13.] Manual refresh the DMP extended attributes following the BCV split operation.
# vxdisk -eo alldgs list | grep -w datadg
emc1_0191 auto:cdsdisk 0191 datadg online hdisk86 lun RAID+Mirr
emc1_0192 auto:cdsdisk 0192 datadg online hdisk87 lun RAID+Mirr
emc1_0193 auto:cdsdisk 0193 datadg online hdisk88 lun RAID+Mirr
emc1_0194 auto:cdsdisk 0194 datadg online hdisk84 lun RAID+Mirr
emc1_0199 auto:cdsdisk 0199 datadg online hdisk90 lun RAID+Mirr
emc1_0235 auto:cdsdisk - (datadg) online udid_mismatch hdisk40 lun bcv nr WD
emc1_0236 auto:cdsdisk - (datadg) online udid_mismatch hdisk41 lun bcv nr WD
emc1_0237 auto:cdsdisk - (datadg) online udid_mismatch hdisk6 lun bcv nr WD
emc1_0238 auto:cdsdisk - (datadg) online udid_mismatch hdisk26 lun bcv nr WD
emc1_0239 auto:cdsdisk - (datadg) online udid_mismatch hdisk44 lun bcv nr WD
# vxdisk scandisks (Refresh DMP extended attributes)
# vxdisk -eo alldgs list | grep -w datadg
emc1_0191 auto:cdsdisk 0191 datadg online hdisk86 lun RAID
emc1_0192 auto:cdsdisk 0192 datadg online hdisk87 lun RAID
emc1_0193 auto:cdsdisk 0193 datadg online hdisk88 lun RAID
emc1_0194 auto:cdsdisk 0194 datadg online hdisk84 lun RAID
emc1_0199 auto:cdsdisk 0199 datadg online hdisk90 lun RAID
emc1_0235 auto:cdsdisk - (datadg) online udid_mismatch hdisk40 lun bcv
emc1_0236 auto:cdsdisk - (datadg) online udid_mismatch hdisk41 lun bcv
emc1_0237 auto:cdsdisk - (datadg) online udid_mismatch hdisk6 lun bcv
emc1_0238 auto:cdsdisk - (datadg) online udid_mismatch hdisk26 lun bcv
emc1_0239 auto:cdsdisk - (datadg) online udid_mismatch hdisk44 lun bcv
# vxdisk -px LIST_CLONE list
DEVICE DG_NAME REPLICATED REPLICATED_TYPE HARDWARE_MIRROR LUN_SIZE NR_DEVICE DEVICE_TYPE DDL_DEVICE_ATTR
emc1_0191 datadg - - no 6399360 no - lun,RAID
emc1_0192 datadg - - no 6399360 no - lun,RAID
emc1_0193 datadg - - no 6399360 no - lun,RAID
emc1_0194 datadg - - no 6399360 no - lun,RAID
emc1_0199 datadg - - no 6399360 no - lun,RAID
emc1_0235 datadg - - yes 6399360 no - lun,bcv
emc1_0236 datadg - - yes 6399360 no - lun,bcv
emc1_0237 datadg - - yes 6399360 no - lun,bcv
emc1_0238 datadg - - yes 6399360 no - lun,bcv
emc1_0239 datadg - - yes 6399360 no - lun,bcv
14.] As the source and H/W clone devices are presented to the same physical server, special VxVM import options must be specified:
# vxdg list
NAME STATE ID
datadg enabled,cds 1412086748.43.goofy
Note: VxVM cannot import the BCV DiskGroup image due to conflicting (duplicated) Veritas Diskids + DGID:
# vxdg -n bcv_datadg import datadg
VxVM vxdg ERROR V-5-1-10978 Disk group datadg: import failed:
Disk group exists and is imported
For VxVM to import the BCV DiskGroup image, the user must specify special import options:
# vxdg -n bcv_datadg –o useclonedev=on –o updateid import datadg
Note: The BCV disk group image (bcv_datadg) now has an unique dgid associated with it. The diskids for the BCV devices are also updated.
# vxdg list
NAME STATE ID
datadg enabled,cds 1412086748.43.goofy
bcv_datadg enabled,cds 1412153576.51.goofy
# vxdisk -eo alldgs list | grep datadg
emc1_0191 auto:cdsdisk 0191 datadg online hdisk86 lun RAID
emc1_0192 auto:cdsdisk 0192 datadg online hdisk87 lun RAID
emc1_0193 auto:cdsdisk 0193 datadg online hdisk88 lun RAID
emc1_0194 auto:cdsdisk 0194 datadg online hdisk84 lun RAID
emc1_0199 auto:cdsdisk 0199 datadg online hdisk90 lun RAID
emc1_0235 auto:cdsdisk 0191 bcv_datadg online hdisk40 lun bcv
emc1_0236 auto:cdsdisk 0192 bcv_datadg online hdisk41 lun bcv
emc1_0237 auto:cdsdisk 0193 bcv_datadg online hdisk6 lun bcv
emc1_0238 auto:cdsdisk 0194 bcv_datadg online hdisk26 lun bcv
emc1_0239 auto:cdsdisk 0199 bcv_datadg online hdisk44 lun bcv
15.] Prior to performing the BCV resync again, the user must deport the BCV DiskGroup image:
# vxdg deport bcv_datadg
# vxdg list
NAME STATE ID
datadg enabled,cds 1412086748.43.goofy
# vxdisk -eo alldgs list | grep datadg
emc1_0191 auto:cdsdisk 0191 datadg online hdisk86 lun RAID
emc1_0192 auto:cdsdisk 0192 datadg online hdisk87 lun RAID
emc1_0193 auto:cdsdisk 0193 datadg online hdisk88 lun RAID
emc1_0194 auto:cdsdisk 0194 datadg online hdisk84 lun RAID
emc1_0199 auto:cdsdisk 0199 datadg online hdisk90 lun RAID
emc1_0235 auto:cdsdisk - (bcv_datadg) online hdisk40 lun bcv
emc1_0236 auto:cdsdisk - (bcv_datadg) online hdisk41 lun bcv
emc1_0237 auto:cdsdisk - (bcv_datadg) online hdisk6 lun bcv
emc1_0238 auto:cdsdisk - (bcv_datadg) online hdisk26 lun bcv
emc1_0239 auto:cdsdisk - (bcv_datadg) online hdisk44 lun bcv
16.] An incremental resync can be performed to refresh the BCV device content.
Note: Prior to resyncing the BCV LUNs, the BCV state would normally be shown in a split state:
# symmir -g bcv_datadg establish
Execute 'Incremental Establish' operation for device group
'bcv_datadg' (y/[n]) ? y
'Incremental Establish' operation execution is in progress for
device group 'bcv_datadg'. Please wait...
'Incremental Establish' operation successfully initiated for device group
'bcv_datadg'.
17.] How to verify that all the BCV LUNs are fully synchronized:
# symmir -g bcv_datadgdg -synched verify
All devices in the group 'bcv_datadg' are in 'Synchronized' state.
# symmir -g bcv_datadg query
Device Group (DG) Name: bcv_datadg
DG's Type : REGULAR
DG's Symmetrix ID : 000290301414
Standard Device BCV Device State
-------------------------- ------------------------------------- ------------
Inv. Inv.
Logical Sym Tracks Logical Sym Tracks STD <=> BCV
-------------------------- ------------------------------------- ------------
DEV0191 0191 0 BCV0235 0235 * 0 Synchronized
DEV0192 0192 0 BCV0236 0236 * 0 Synchronized
DEV0193 0193 0 BCV0237 0237 * 0 Synchronized
DEV0194 0194 0 BCV0238 0238 * 0 Synchronized
DEV0199 0199 0 BCV0239 0239 * 0 Synchronized
Total ------- -------
Track(s) 0 0
MB(s) 0.0 0.0
Legend:
(*): The paired BCV device is associated with this group.
18.] The VxVM details can be refereshed.
# vxdisk scandisks
# vxdisk -eo alldgs list
DEVICE TYPE DISK GROUP STATUS OS_NATIVE_NAME ATTR
emc1_0191 auto:cdsdisk 0191 datadg online hdisk86 lun RAID+Mirr
emc1_0192 auto:cdsdisk 0192 datadg online hdisk87 lun RAID+Mirr
emc1_0193 auto:cdsdisk 0193 datadg online hdisk88 lun RAID+Mirr
emc1_0194 auto:cdsdisk 0194 datadg online hdisk84 lun RAID+Mirr
emc1_0199 auto:cdsdisk 0199 datadg online hdisk90 lun RAID+Mirr
emc1_0235 auto - - error hdisk40 lun bcv nr WD
emc1_0236 auto - - error hdisk41 lun bcv nr WD
emc1_0237 auto - - error hdisk6 lun bcv nr WD
emc1_0238 auto - - error hdisk26 lun bcv nr WD
emc1_0239 auto - - error hdisk44 lun bcv nr WD
19.] When fully synchronized, split the BCV LUNs as before. See Step 10.
Repeat the process as required.
Issue/Introduction
