25
----------------------------------------------------------------
00158:0015B
}
}
}
Target Configuration: OK
{
Storage Groups (1): OK
{
Name : lcseb246_sg
Status : OK
{
Dev
----------------------------------------------------------------
00013:00016
}
}
}
A syminq run from the host following the create shows the four devices listed as SRDF R2 devices:
C:\>syminq
Device Product Device
-------------------------- --------------------------- ---------------------------
Name Type Vendor ID Rev Ser Num Cap (KB)
-------------------------- --------------------------- ---------------------------
\\.\PHYSICALDRIVE0 DGC VRAID 0533 255723B2 125829120
\\.\PHYSICALDRIVE1 R2 EMC SYMMETRIX 5876 8400158000 52429440
\\.\PHYSICALDRIVE2 R2 EMC SYMMETRIX 5876 8400159000 52429440
\\.\PHYSICALDRIVE3 R2 EMC SYMMETRIX 5876 840015A000 52429440
\\.\PHYSICALDRIVE4 R2 EMC SYMMETRIX 5876 840015B000 52429440
EXAMINE THE DEVICE PAIRING AND IDENTITIES FOLLOWING A CREATE
The create operation automatically configures matching volumes on the target array. These volumes will be the same size and
configuration, though they will most likely not have the same VMAX volume numbers. Following the create operation the 4 new volumes
on the target array are 0013 through 0016. Volume 0158 and volume 0013 are paired for NDM operations. The RDF pairing information
can also be seen in the symdev show output.
C:\>symdev list -sid 3184
Symmetrix ID: 000195703184
Device Name Dir Device
---------------------------- ------- -------------------------------------
Cap
Sym Physical SA :P Config Attribute Sts (MB)
---------------------------- ------- -------------------------------------
00028 \\.\PHYSICALDRIVE5 08E:000 2-Way Mir N/Grp'd ACLX RW 3
...
00158 Not Visible ???:??? TDEV N/Grp'd RW 51201
00159 Not Visible ???:??? TDEV N/Grp'd RW 51201
0015A Not Visible ???:??? TDEV N/Grp'd RW 51201