Windows Knowledge Base

[DMX] DMX SYM Device - Symdev output explained

There are two commands that could be used to display symmetrix device information:
symdev list
sympd list

Symdev lists all the devices in the symmetrix and sympd lists all devices that are associated to the host (where you issue SYMCLI).
Below is a sample sympd list output

 

C:\>sympd list

 

Symmetrix ID: 000190101235

 

Device Name Directors Device

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

Cap

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

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

 

\\.\PHYSICALDRIVE0 0046 07C:0 01B:C11 2-Way Mir N/Grp'd VCM WD 6

\\.\PHYSICALDRIVE1 005F 07C:0 16B:D1 2-Way Mir N/Grp'd RW 3

\\.\PHYSICALDRIVE2 0060 07C:0 01D:C1 2-Way Mir N/Grp'd RW 3

\\.\PHYSICALDRIVE3 0061 07C:0 01A:D1 2-Way Mir N/Grp'd RW 3

\\.\PHYSICALDRIVE4 0062 07C:0 16C:C1 2-Way Mir N/Grp'd RW 3

\\.\PHYSICALDRIVE5 0063 07C:0 16B:C0 2-Way Mir N/Grp'd RW 3

\\.\PHYSICALDRIVE6 0064 07C:0 01D:D0 2-Way Mir N/Grp'd RW 3

\\.\PHYSICALDRIVE7 0100 07C:0 01D:D0 2-Way Mir N/Grp'd RW 30000

 

 

C:\>symdev list -sid 1235

 

Symmetrix ID: 000190101235

 

Device Name Directors Device

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

Cap

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

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

 

0046 \\.\PHYSICALDRIVE0 07C:0 01B:C11 2-Way Mir N/Grp'd VCM WD 6

…………………………………, …………………………………….., ………………………….

005F \\.\PHYSICALDRIVE1 07C:0 16B:D1 2-Way Mir N/Grp'd RW 3

0060 \\.\PHYSICALDRIVE2 07C:0 01D:C1 2-Way Mir N/Grp'd RW 3

0061 \\.\PHYSICALDRIVE3 07C:0 01A:D1 2-Way Mir N/Grp'd RW 3

0062 \\.\PHYSICALDRIVE4 07C:0 16C:C1 2-Way Mir N/Grp'd RW 3

0063 \\.\PHYSICALDRIVE5 07C:0 16B:C0 2-Way Mir N/Grp'd RW 3

0064 \\.\PHYSICALDRIVE6 07C:0 01D:D0 2-Way Mir N/Grp'd RW 3

0065 Not Visible 07C:1 16A:D0 2-Way Mir N/Grp'd RW 3

…………………………………, …………………………………….., ………………………….

0147 Not Visible ???:? 01D:D2 2-Way Mir N/Grp'd (M) RW 8715

0148 Not Visible ???:? 16A:D2 2-Way Mir N/Grp'd (m) RW -

0149 Not Visible ???:? 01B:D10 2-Way Mir N/Grp'd (M) RW 8715

014A Not Visible ???:? 16C:D10 2-Way Mir N/Grp'd (m) RW -

014B Not Visible ???:? 15A:C12 2-Way Mir N/Grp'd (M) RW 8715

014C Not Visible ???:? 16D:D3 2-Way Mir N/Grp'd (m) RW -

014D Not Visible ???:? 01C:C10 2-Way Mir N/Grp'd (M) RW 8715

014E Not Visible ???:? 16A:D10 2-Way Mir N/Grp'd (m) RW -

014F Not Visible ???:? 02B:D11 2-Way Mir N/Grp'd (M) RW 8715

0150 Not Visible ???:? 15D:C11 2-Way Mir N/Grp'd (m) RW -

…………………………………, …………………………………….., ………………………….

0C95 Not Visible ***:* 01A:C8 RDF1+R-5 Grp'd RW 8715

0C96 Not Visible ***:* 01A:D9 RDF1+R-5 Grp'd RW 8715

0C97 Not Visible ***:* 15A:D9 RDF1+R-5 Grp'd RW 8715

0C98 Not Visible ***:* 16A:CB RDF1+R-5 Grp'd RW 8715

0C99 Not Visible ***:* 02A:CB RDF1+R-5 Grp'd RW 8715

0C9A Not Visible ***:* 16A:DA RDF1+R-5 Grp'd RW 8715

0C9B Not Visible ***:* 02A:C9 RDF1+R-5 Grp'd RW 8715

0C9C Not Visible ***:* 02A:DA RDF1+R-5 Grp'd RW 8715

0C9D Not Visible ***:* 02B:DB RDF1+R-5 Grp'd RW 8715

0C9E Not Visible ***:* 01A:CA RDF1+R-5 Grp'd RW 8715

 

From the output above, you can find 6 symmetrix gateway devices with 3 MB size, in DMX, all those devices with a 3-megabyte (MB) capacity is normally configured gatekeeper device.

The output below displays devices on symmetrix 1235, in the Device Name Section,
Sym -  the first column contains a device’s Symmetrix device name (the hexadecimal number that the Symmetrix assigns to each physical device),

Physical- the second column contains its physical device name (host nc3ame) if the device is visible to the host.

In the Directors section,
SA :P - the SA front-end director (SCSI adapter) number and port that connects the device to the host,

DA :IT -  the DA disk director number and interface that transfers data from the device to cache.
Question marks (???:?) in the SA:P column indicate if the device is not mapped to a front-end adapter port, or is mapped to multiple ports with no clearly distinguishable primary path.

Device/Attribute - Device information includes a device’s configuration, whether it currently belongs to a device group or composite group (N/Grp’d or N/Asst’d means it does not),  “N/Grp’d” means that a standard device does not currently belong to a device group or composite group. “N/Asst’d” means that a BCV does not belong to (is not associated with) a device group or composite group.

Sts -  its(devices) status (read/write or otherwise), A meta head (M), the first device in a meta device, and a meta member (m) are displayed with these letter notations.

Cap - its storage capacity in megabytes.

For detailed configuration information about a specific device,  use the sympd show or symdev show. Below is an sample output displaying details of SYM device 03c3, see partial output of symdev list .

Device Name Directors Device

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

Cap

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

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

 

03C3 Not Visible ***:* 01B:D12 RDF1+R-5 Grp'd (M) RW 34860

 

 

Below is symdev show 03c3 output,  in the output

"Dynamic Spare Invoked    : No" which means that no dynamic spare(hot spare) was invoked for a failed disk.
"Dynamic RDF Capability   : RDF1_OR_RDF2_Capable" which mean that this device is capable of acting as Dynamic R1 or R2 device.
"Device Service State     : Normal" this is a setting that relates to mirrors. If you see the "Device Service State : Degraded", it indicates that one of the mirror positions of a protected device is Not Ready, failed drive for example. And this also includes RDF devices: where the RDF link is physically down, the device state will be: " Degraded. "
"Device Status : Ready  (RW)" indicate the device is operational state, if report "Device Status: Not Ready (NR)" it means that the host cannot read or write to the device, but it can "see" it.
"Device SA Status : Ready (RW)" indicate that the device is mapped to an SA. If you see it's "Device SA Status :N/A" normally it means that he device is not mapped to any SA. The value could also be " Not Ready(NR)", "Write Disabled".

"Back End Disk Director Information" section display the Disk Director information related to Symdev 3C3.  
"Hyper Status  : Ready(RW)" means physical disk 3C3 is mapped and accessible for R/W by the host. If it shows as "Hyper Status  : Not Ready(NR)", then normally it means it is mapped but currently is not accessible for R/W by its host. It could either that the device is estabished or it's in problem state(Not Ready) on the DA.
"RDF Information" shows that sym device 3c3 is configured as dynamic R1 device in RA group "1" and the remote R2 device is  02FF on the remote symmetrix (2333)
"Device RDF Status : Ready(RW)" is specific to the R1 side, which is almost always Ready except when a device is in Domino mode. "Device SA
"Device SA Status  : Ready(RW)" means that it is mapped to SA.
"Device RA Status : Ready(RW)" means RA is ready for Read/Write operation.
"Device Link Status  : Ready(RW)" indicate the RDF link is healthy, If it report "No Ready (NR)", it means that the R1 device's RDF link to the remote R2 device is currently suspended.
"Device Suspend State : N/A" means that the device does not belong to an enabled consistency group or that it does but is synchronized and does not have an R1 suspend state. If the device is part of a tripped consistency group, its suspended state can be "Pending Offline" or "offline"
"Device Consistency State : Disabled" means that the device is not part of an enabled consistency group.

"Device RDF State: Ready(RW)" means R1 ready for data synchronization. If "Device RDF State: Not Ready(NR)" it means the R1(3C3) is not currently accessible for copying data to its R2 device.
"Remote Device RDF State: Write Disabled  (WD)" means the remote R2 device(2FF) is write disabled to its host.
"Number of R1 Invalid Tracks : 0" and "Number of R2 Invalid Tracks : 0" shows the number of invalid tracks, to resolve the invalid tracks, you can have the remote invalids on both R1 and R2 sides prior to an establish or a restore operation. If so, performing an establish operation copies modified R1 tracks to R2 side. A restore indicates the opposite -- that you want to copy modified R2 tracks to the R1 side.

 

 

C:\>symdev show 03C3

 

Symmetrix ID: 000190101235

 

Device Physical Name : Not Visible

 

Device Symmetrix Name : 03C3

Device Serial ID : N/A

Symmetrix ID : 000190101235

 

Device Group Name : ifsprod

Device Logical Name : DEV105

 

Attached BCV Device : N/A

 

Attached VDEV TGT Device : N/A

 

Vendor ID : EMC

Product ID : SYMMETRIX

Product Revision : 5772

Device WWN : 60060480000190102767533030334333

Device Emulation Type : FBA

Device Defined Label Type: N/A

Device Defined Label : N/A

Device Sub System Id : 0x0004

Cache Partition Name : DEFAULT_PARTITION

 

Device Block Size : 512

 

Device Capacity

{

Cylinders : 74368

Tracks : 1115520

512-byte Blocks : 71393280

MegaBytes : 34860

KiloBytes : 35696640

}

 

Device Configuration : RDF1+R-5 (Meta Head,

Non-Exclusive Access)

 

Device is WORM Enabled : No

Device is WORM Protected : No

 

SCSI-3 Persistent Reserve: Disabled

 

Dynamic Spare Invoked : No

 

Dynamic RDF Capability : RDF1_OR_RDF2_Capable

 

STAR Mode : No

STAR Recovery Capability : None

STAR Recovery State : NA

 

Device Service State : Normal

 

Device Status : Ready (RW)

Device SA Status : Ready (RW)

 

Front Director Paths (2):

{

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

POWERPATH DIRECTOR PORT LUN

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

PdevName Type Type Num Sts VBUS TID SYMM Host

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

Not Visible N/A FA 07B:0 RW 000 00 010 N/A

Not Visible N/A FA 10B:0 RW 000 00 010 N/A

}

 

Meta Configuration : Striped

Meta Stripe Size : 960k (2 Cylinders)

Meta Device Members (4) :

{

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

BCV DATA RDF DATA

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

Sym Cap Std Inv BCV Inv Pair R1 Inv R2 Inv Pair

Dev (MB) Tracks Tracks State Tracks Tracks State

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

--> 03C3 8715 - - N/A 0 0 Synchronized

03C4 8715 - - N/A 0 0 Synchronized

03C5 8715 - - N/A 0 0 Synchronized

03C6 8715 - - N/A 0 0 Synchronized

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

34860 - - 0 0

}

 

Mirror Set Type : [RAID-5,R2 Remote,RAID-5,N/A]

 

Mirror Set DA Status : [RW,RW,RW,N/A]

 

Mirror Set Inv. Tracks : [0,0,0,0]

 

Back End Disk Director Information

{

Hyper Type : RAID-5

Hyper Status : Ready (RW)

Disk [Director, Interface, TID] : [N/A,N/A,N/A]

Disk Director Volume Number : N/A

Hyper Number : N/A

 

Hyper Type : R2 Remote

Hyper Status : Ready (RW)

Disk [Director, Interface, TID] : [N/A,N/A,N/A]

Disk Director Volume Number : N/A

Hyper Number : N/A

 

Hyper Type : RAID-5

Hyper Status : Ready (RW)

Disk [Director, Interface, TID] : [N/A,N/A,N/A]

Disk Director Volume Number : N/A

Hyper Number : N/A

}

 

RAID-5 Device Information

{

Number of Tracks in a Stripe : 4

Overall Ready State of RAID-5 Device : Ready

Overall WriteProtect State of RAID-5 Device : Enabled

Member Number of the Failing Device : None

Member Number that Invoked the Spare : None

Disk Director (DA) that Owns the Spare : Inv

Copy Direction : N/A

RAID-5 Hyper Devices (3+1):

{

Device : 03C3 (M)

{

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

Disk DA Hyper Member Spare Disk

DA :IT Vol# Num Cap(MB) Num Status Status Grp# Cap(MB)

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

01B:D12 662 16 2909 2 RW N/A 0 140014

15B:D12 662 16 2909 1 RW N/A 0 140014

02D:C12 344 16 2909 3 RW N/A 0 140014

16D:C12 339 16 2909 4 RW N/A 0 140014

}

Device : 03C4 (m)

{

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

Disk DA Hyper Member Spare Disk

DA :IT Vol# Num Cap(MB) Num Status Status Grp# Cap(MB)

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

02A:C3 63 17 2909 1 RW N/A 0 140014

16A:C3 63 17 2909 4 RW N/A 0 140014

01C:D3 436 17 2909 2 RW N/A 0 140014

15C:D3 436 17 2909 3 RW N/A 0 140014

}

Device : 03C5 (m)

{

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

Disk DA Hyper Member Spare Disk

DA :IT Vol# Num Cap(MB) Num Status Status Grp# Cap(MB)

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

02B:C10 296 16 2909 1 RW N/A 0 140014

16B:C10 295 16 2909 2 RW N/A 0 140014

01D:D10 669 16 2909 4 RW N/A 0 140014

15D:D10 669 16 2909 3 RW N/A 0 140014

}

Device : 03C6 (m)

{

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

Disk DA Hyper Member Spare Disk

DA :IT Vol# Num Cap(MB) Num Status Status Grp# Cap(MB)

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

02A:D12 758 16 2909 4 RW N/A 0 140014

16A:D12 764 16 2909 3 RW N/A 0 140014

01C:C12 342 16 2909 2 RW N/A 0 140014

15C:C12 342 16 2909 1 RW N/A 0 140014

}

}

}

 

RDF Information

{

Device Symmetrix Name : 03C3

RDF Type : R1

RDF (RA) Group Number : 1 (00)

 

Remote Device Symmetrix Name : 02FF

Remote Symmetrix ID : 000190102333

 

R2 Device Is Larger Than The R1 Device : False

 

RDF Pair Configuration : Normal

RDF STAR Mode : False

 

RDF Mode : Synchronous

RDF Adaptive Copy : Disabled

RDF Adaptive Copy Write Pending State : N/A

RDF Adaptive Copy Skew (Tracks) : 65535

 

RDF Device Domino : Disabled

 

RDF Link Configuration : Fibre

RDF Link Domino : Disabled

Prevent Automatic RDF Link Recovery : Disabled

Prevent RAs Online Upon Power ON : Enabled

 

Device RDF Status : Ready (RW)

 

Device SA Status : Ready (RW)

Device RA Status : Ready (RW)

Device Link Status : Ready (RW)

 

Device Suspend State : N/A

Device Consistency State : Disabled

RDF R2 Not Ready If Invalid : Disabled

 

Device RDF State : Ready (RW)

Remote Device RDF State : Write Disabled (WD)

 

RDF Pair State ( R1 <===> R2 ) : Synchronized

 

Number of R1 Invalid Tracks : 0

Number of R2 Invalid Tracks : 0

 

RDFA Information:

{

Session Number : 0

Cycle Number : 0

Number of Devices in the Session : 261

Session Status : Inactive

 

Session Consistency State : N/A

Minimum Cycle Time : 00:00:30

Average Cycle Time : 00:00:00

Duration of Last cycle : 00:00:00

Session Priority : 33

 

Tracks not Committed to the R2 Side: 0

Time that R2 is behind R1 : 00:00:00

R1 Side Percent Cache In Use : 0

R2 Side Percent Cache In Use : 0

 

Transmit Idle Time : 00:00:00

R1 Side DSE Used Tracks : 0

R2 Side DSE Used Tracks : 0

}

}