Symmetrix Configuration.pdf

8/17/2019 Symmetrix Configuration.pdf

http://slidepdf.com/reader/full/symmetrix-configurationpdf 1/53

Engineering White Paper

Using SYMCLI to Obtain Symmetrix

Configuration Information

Abstract

This paper describes using SYMCLI commands to obtain Symmetrix configuration and status information thatwill help you perform control operations with SRDF family and TimeFinder family products.

Published 4/5/2004



4/5/2004

Copyright © 2004 EMC®

Corporation. All rights reserved.

EMC believes the information in this publication is accurate as of its publication date. The information is

subject to change without notice.

THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS IS”. EMC CORPORATION

MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THEINFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED

WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Use, copying, and distribution of any EMC software described in this publication requires an applicable

software license.

Part Number 300-000-285 REV D H606.4

Using SYMCLI to Obtain Symmetrix Configuration Information 2



4/5/2004

Table of Contents

Introduct ion .........................................................................................................4

Purpose and Scope ..................................................................................................................... 4

Related Documentation ............................................................................................................... 4

Practical Uses .....................................................................................................4

Displaying Information about a Symmetrix Unit ..............................................5

Displaying Information about Symmetrix Devices...........................................9

Displaying Information about SRDF Devices .................................................16

Displaying Information about BCV Devices ...................................................18

Displaying Information about a Device Group or Composite Group ...........20

Example 1: Verify ing that Configuration Information in the SYMAPIDatabase Shows the Current Configuration...................................................26

Example 2: Obtaining More Symmetrix Information .....................................28

Example 3: Obtaining More Device Information............................................31

Example 4: Obtaining Information about Dynamic RDF Devices ................35

Example 5: Obtaining Information about Virtual Devices ............................36

Example 6: Obtaining More Device Group Information ................................39

Example 7: Obtaining Disk and Audit Information........................................45

Example 8: Obtaining Display Output in XML Format ..................................50

Example 9: Obtaining Status Information about GNS ..................................52




4/5/2004

Introduction

EMC®

Solutions Enabler (SYMCLI) maintains configuration and status information about every device

inside the Symmetrix® units that are accessible from your host. This information is stored in a SYMAPI

database file that resides on the host or in a GNS-managed 1 global repository. You can use SYMCLI

commands to display in standard or XML format various levels of information about:

• Symmetrix units attached to the host

• Remote Symmetrix units that are connected by RDF links to the locally-attached Symmetrix units

• Devices within each Symmetrix unit

• A user-defined device group or composite group that represents a collection of devices

Purpose and Scope

This paper describes using SYMCLI commands to obtain Symmetrix configuration and status informationthat will help you perform control operations with SRDF® family and TimeFinder ™ family products.

Displays were obtained while running various Solutions Enabler versions up to version 5.4. Your display

may vary slightly, depending on which version of Solutions Enabler you are running.

Related Documentation

The following white papers provide information related to the concepts in this paper:

• Using SYMCLI to Perform TimeFinder/Mirror Control Operations (P/N 300-000-074)

• Using SYMCLI to Perform TimeFinder/Snap Operations (P/N 300-001-381)

• Using SYMCLI to Perform TimeFinder/Mirror Clone Operations (P/N 300-001-382)

• Using SYMCLI to Perform Control Operations with SRDF Family Products (P/N 300-000-076)

• Using SYMCLI to Implement RDF Consistency Protection with SRDF Family Products

(P/N 300-000-284)

• Using SYMCLI to Perform SRDF/AR (P/N 300-000-078)

• Using SYMCLI and GNS to Propagate Group Definitions to Multiple Hosts (P/N 300-301-384)

Practical Uses

Examining Symmetrix configuration data is especially helpful in understanding the configuration of theSymmetrix units in your storage complex. Each Symmetrix unit has a unique serial number called a

Symmetrix ID (sid ). A listing of Symmetrix units accessible to your host provides the sid for each

Symmetrix unit and specifies whether the unit is local or remote. You can use the sid in subsequentcommands to display more detailed information about that Symmetrix unit, such as a list of SRDF devices

or TimeFinder BCV devices on that Symmetrix unit.

You can use a symdi sk l i st command to display the configuration and status of the physical disks

and their hypervolumes within a Symmetrix unit. Beginning with Enginuity version 5568 and higher, you

can use a symaudi t l i st command to retrieve information from the Symmetrix Audit Log file from

1 Group Name Services




4/5/2004

data written to the file during control operations. This audit information allows you to determine what

application on what host initiated actions that directed Symmetrix behavior.

You can set an environment variable or include the –out XML option on a command line to produce

display output in “XML” format rather than “standard” format.

Your host’s SYMAPI database file stores information about the device group and the standard devices and

BCVs included in it. But information about BCV pairs is also stored in the Symmetrix unit’s globalmemory, meaning that the Symmetrix “remembers” previous device pairing relationships that may no

longer be active. Consequently, a BCV or standard device that you add to your device group may have an

existing pairing relationship with a device that does not belong to your device group. Thus, to avoid any

confusion when trying to create new BCV pairs from devices that you added to your device group, it is

recommended that you examine device status information first.

Displaying Information about a Symmetrix Unit

Whenever a Symmetrix configuration is new or has changed, you need to ensure which Symmetrix units

are connected to your host and that the information about these Symmetrix units is current. You can use the

symcf g ver i f y command to determine if the Symmetrix configuration and the SYMAPI database file

are in sync. If they are out of sync, the verify action returns code 24 (CLI _C_NOT_I N_SYNC). If they arenot in sync, you should run either a discover operation or a full sync (see “Example 1: Verifying That

Configuration Information in the SYMAPI Database Shows the Current Configuration”).

You can use the symcf g di scover command to rebuild your host’s SYMAPI database file with the

most current information about the physical devices directly connected to your host. The command scans

all buses, collects information about all the devices found, and rebuilds the database with collected

information from all locally and remotely attached Symmetrix devices. If you have disconnected a

Symmetrix unit from the configuration since the last discover process, a subsequent symcf g di scover

does not automatically remove outdated Symmetrix information from the database file unless you first

set the environment variable SYMCLI _REMOVE_SYMS to a value of 1. (You can also use the

symcf g remove command to remove information about disconnected Symmetrix units.)

The simplest way to display high-level information on Symmetrix units accessible to your host is to invokethe symcf g l i st command from the host. For example:

symcfg list

S Y M M E T R I X

Mcode Cache Num Phys Num Symm SymmI D At t achment Model Ver si on Si ze ( MB) Devi ces Devi ces

000187900035 Local DMX800 5670 6144 204 938000187900041 Remot e DMX800 5670 6144 0 763

The display shows the configuration from the local host’s point of view. The local host is the controllinghost from which you enter SYMCLI commands, and the local Symmetrix unit is the one that is connected to

the local host. A remote Symmetrix unit is one that is connected to the local Symmetrix unit via RDF links.The display shows that local Symmetrix 35 is connected to remote Symmetrix 41. Both Symmetrix units

are running Enginuity version 5670.

The Num Symm Devices column displays the total number of Symmetrix devices configured for aSymmetrix unit. The Num Phys Devices column displays only those devices that are mapped to the host

and/or have a physical host device name. The local host has access (read/write capability) to 204 physical




4/5/2004

devices on the local Symmetrix unit. The local host (or point-of-view host in this case) cannot access

devices on the remote Symmetrix, which accounts for the zero value under Num Phys Devices.

You can add the verbose option (-v) to the symcf g l i st command to obtain detailed information about

all Symmetrix units in the configuration, such as whether the concurrent RDF and dynamic RDF states areenabled on each Symmetrix. To display details about one specific Symmetrix unit, include the Symmetrix

ID using the – si d option. For example, to display the details of Symmetrix 000187900035:

symcfg list –sid 35 -v

Symmet r i x I D: 000187900035 ( Local )

Pr oduct Model : DMX800Symmet r i x I D : 000187900035

Mi cr ocode Versi on ( Number ) : 5670 ( 16260000)Mi cr ocode Dat e : 01. 05. 2004

Mi cr ocode Pat ch Dat e : 01. 05. 2004Mi cr ocode Pat ch Level : 64

Cache Si ze : 6144 ( MB)# of Avai l abl e Cache Sl ot s : 107946Max # of Syst emWr i t e Pendi ng Sl ot s : 86441Max # of DA Wr i t e Pendi ng Sl ot s : 43220Max # of Devi ce Wr i t e Pendi ng Sl ot s : 1330

Symmet r i x Tot al Oper at i ng Ti me : 62 days, 22: 23: 35Symmet r i x Power ON Ti me : Tue Nov 4 13: 44: 30 2003Symmet r i x Last I PL Ti me ( Col d) : Mon Dec 15 14: 38: 35 2003Symmet r i x Last Fast I PL Ti me ( Hot ) : Mon J an 5 16: 35: 51 2004

Host DB Sync Ti me : Tue J an 6 11: 14: 43 2004Symmetr i x CLI ( SYMCLI ) Vers i on : V5. 4. 0. 0 ( Edi t Level : 516)

Bui l t wi t h SYMAPI Ver si on : V5. 4. 0. 0 ( Edi t Level : 516)SYMAPI Run Ti me Ver si on : V5. 4. 0. 0 ( Edi t Level : 516)

Number of Conf i gur ed ( Sym) Devi ces : 938Number of Vi si bl e ( Host ) Devi ces : 2Number of Conf i gur ed Act ual Di sks : 60Number of Conf i gur ed Hot Spar es : 0Number of Unconf i gur ed Di sks : 0Maxi mumnumber of hyper s per di sk : 32

Number of Power pat h Devi ces : 2Powerpat h Run Ti me Versi on : 4. 1. 0

SDDF Conf i gur at i on State : Enabl edConf i gur at i on Change St at e : Enabl edWORM Conf i gur at i on Level : WORM_3WORM Char act er i st i cs : MANUAL_LOCK

Symmet r i x Conf i gur at i on Checksum : 2E43F0Swi t ched RDF Conf i gur at i on St ate : Di sabl edConcur r ent RDF Conf i gur at i on St ate : Di sabl edDynami c RDF Conf i gur at i on Stat e : Enabl edConcurr ent Dynami c RDF Conf i gur at i on : Di sabl ed




4/5/2004

RDF Dat a Mobi l i t y Conf i gur at i on St at e: Di sabl edAccess Cont r ol Conf i gur at i on St ate : Enabl edDevi ce Maski ng ( VCM) Conf i g State : Di sabl edVCMdb Access Rest r i ct ed State : Di sabl edMul t i LRU Devi ce Ass i gnment : BY_NUMBERDi sk Gr oup Assi gnment s : Not i n Use

Par i t y Rai d Conf i gur at i on : RAI D- S ( 7+1)Rai d- 5 Conf i gur at i on : RAI D- 5 ( 7+1)

Devices that are configured as PowerPath®-connected devices provide support for controlling SRDFconsistency groups. This Symmetrix display shows two PowerPath configured devices running PowerPath

software version 4.1.0.

Both the SDDF Configuration State (the ability to track changes and perform incremental updates) and theConfiguration Change State (the state of allowing configuration changes) are enabled. The WORM (Write

Once Read Many) configuration level is also enabled. The Symmetrix Configuration Checksum (2E43F0)

indicates the initial Enginuity program load for this configuration. You can use the symcf g ver i f y

command to determine if the Symmetrix configuration has changed compared to the SYMAPI database.

Switched RDF involves non-blocking switching devices that interconnect two or more nodes, allowing aSymmetrix port pair to run full-duplex. For information about Concurrent RDF, Dynamic RDF, and RDF

Data Mobility, refer to the white paper Using SYMCLI to Perform Control Operations with SRDF Family

Products (P/N 300-000-076). For information about Device Masking and VCMdb Access, refer to the

white paper Using SYMCLI to Perform Device Masking (P/N 300-000-650). For information about Parity

RAID and RAID-5 configuration, refer to the white paper Using the SYMCLI Configuration Manager (P/N300-000-475).

Another useful SYMCLI command to examine Symmetrix connections is symcf g l i st –r a al l .

This command reaches all Symmetrix units that are accessible through RDF links one or two hops away

and displays Remote Link Director information. Information in the Remote SymmID column shows thatSymmetrix units 3264 and 3263 are connected to Symmetrix unit 3265 but that 3263 and 3264 are not

connected to each other. Figure 1 illustrates this Symmetrix configuration.

symcfg list -ra all

Symmet r i x I D: 000000003264 ( Local )

S Y M M E T R I X R D F D I R E C T O R S

Remot e Local Remot eI dent Symb Num Sl ot Type At t r SymmI D RA Gr p RA Gr p St at us

RF- 3A 03A 3 3 RDF- BI - DI R - 000000003265 2 ( 01) 2 ( B) Onl i neRF- 3B 03B 19 3 RDF- BI - DI R - 000000003265 2 ( 01) 2 ( B) Onl i ne

Symmet r i x I D: 000000003263 ( Remot e)



RF- 3A 03A 3 3 RDF- BI - DI R - 000000003265 1 ( 00) 1 ( A) Onl i neRF- 3B 03B 19 3 RDF- BI - DI R - 000000003265 1 ( 00) 1 ( A) Onl i ne




4/5/2004

Symmet r i x I D: 000000003265 ( Remot e)



RF- 3A 03A 3 3 RDF- BI - DI R - 000000003263 1 ( A) 1 ( 00) Onl i neRF- 14A 14A 14 14 RDF- BI - DI R - 000000003264 2 ( B) 2 ( 01) Onl i neRF- 3B 03B 19 3 RDF- BI - DI R - 000000003263 1 ( A) 1 ( 00) Onl i neRF- 3B 03B 30 14 RDF- BI - DI R - 000000003264 2 ( B) 2 ( 01) Onl i ne

Figure 1 illustrates that an RA adapter can be the interface to an RDF link between Symmetrix systems. Inthis case, RDF groups (RA groups) represent an established connection between paired R1 and R2 devices,

forming an SRDF-pair-associated link. The Local RA Grp and Remote RA Grp columns list the RA groupnumbers in the Figure 1 configuration. RA group 2 forms the RDF link between Symmetrix units 3264 and

3265. RA group 1 forms the link between Symmetrix units 3265 and 3263.

R2

Remote Symmetrix3263

CLI-000102

RA Group 2

RA Group 1

Local Symmetrix3264

R1

Remote Symmetrix3265

R2

R1BCV

Host

Figure 1. Symmetrix Configuration Displayed by the symcfg list –ra all Command

Other useful options with the symcf g l i st command are included in Table 1. For a complete list of

options, refer to EMC Solutions Enabler Symmetrix Base Management CLI Product Guide.

Table 1. Useful Options with the symcfg list Command

Option Display

- appl i cat i ons –si d # Symmetrix-registered applications that have accessed a certain Symmetrix.- connect i ons –si d # All hosts that have accessed a certain Symmetrix.

- ser vi ces Network services in the client/SYMAPI server connection.

- di r al l Configuration and status information about all directors in a Symmetrix unit.

- sa al l Configuration of all front-end directors (SA and FA) in a Symmetrix unit.

- l ock Symmetrix units that have a Symmetrix external lock.




4/5/2004

Displaying Information about Symmetrix Devices

SYMCLI provides two commands to list the devices on a Symmetrix unit — one that displays all devices,

and one that displays only host-visible devices (devices that are mapped to the host or have a physical host

device name, or both).

• The symdev l i st command lists all devices in a Symmetrix unit.

• The sympd l i st command lists only those devices in a Symmetrix unit that are visible to your host

(that is, each device has a physical device name that allows the host to access it).

The partial symdev l i st output below displays devices on the local Symmetrix unit by default. To

display devices on a remote Symmetrix unit, include the – si d option with the identifier of the remote

Symmetrix unit. The ellipsis (……) indicates where output was omitted. The first column contains a device’s

Symmetrix device name (the hexadecimal number that the Symmetrix assigns to each physical device), and

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

symdev list

Symmetrix ID: 000000003264

Devi ce Name Di r ect or s Devi ce- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

CapSym Physi cal SA : P DA : I T Conf i g At t r i but e St s ( MB)- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -0000 Not Visible 16A:0 01A:C0 Unprotected N/Grp'd (M) RW 1031

0001 Not Visible 16A:0 02B:D3 Unprotected N/Grp'd (M) RW 1031

0002 Not Visible ???:? 02A:C0 Unprotected N/Grp'd RW 516

0003 Not Visible 16A:0 01B:D3 Unprotected N/Grp'd (m) RW -

0004 Not Visible 16A:0 01B:C0 Unprotected N/Grp'd (m) RW -

0005 Not Visible ???:? 02A:D3 Unprotected N/Grp'd RW 516

…………………………………………………………………………………………………………………………………………………………………………………………………………………

0086 / dev/ r dsk/ c4t0d2s2 16B: 0 01B: C0 2- Way Mi r N/ Gr p' d RW 516

0087 / dev/ r dsk/ c4t0d3s2 16B: 0 02B: C0 2- Way Mi r N/ Gr p' d RW 5160088 / dev/ r dsk/ c4t1d0s2 16B: 0 01A: D0 2- Way BCV Mi r N/ Asst ' d RW 5160089 / dev/ r dsk/ c4t1d1s2 16B: 0 02A: D0 2- Way BCV Mi r N/ Asst ' d RW 516008A / dev/ r dsk/ c4t1d2s2 16B: 0 01B: D0 2- Way BCV Mi r N/ Asst ' d RW 516008B / dev/ r dsk/ c4t1d3s2 16B: 0 02B: D0 2- Way BCV Mi r N/ Asst ' d RW 516

Director information includes the SA front-end director (SCSI adapter) number and port that connects the

device to the host, as well as the DA disk director number and interface that transfers data from the device

to cache. Question marks (???:?) in the SA:P column indicate that this device is not mapped to a front-end

adapter port, or is mapped to multiple ports with no clearly distinguishable primary path.

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),2 its status (read/write or otherwise), and itsstorage capacity in megabytes. A meta head (M), the first device in a meta device, and a meta member (m)

are displayed with these letter notations.

Useful options with the symdev l i st command include –mul t i por t and – f i r s tpor t , which

display devices mapped to multiple front-end adapter ports or to just the first port of information for

2 The attribute Grp’d or Asst’d means that the device belongs to a device group or composite group, or to both a device group and a

composite group.




4/5/2004

devices mapped to more than one port, respectively. Refer to “Example 3: Obtaining More Device

Information” for displays using these options.

The partial sympd l i st output below displays the same information as the symdev l i st output but

only for devices that are visible to the host, listing physical device names in the first column. Any devicewith a 3-megabyte (MB) capacity is a configured gatekeeper device. Note that the “Not Visible” devices

from the previous symdev l i st display are omitted from this display. “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.

sympd list



CapPhysi cal Sym SA : P DA : I T Conf i g At t r i but e St s ( MB)- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -/ dev/ r dsk/ c4t0d0s2 0084 16B: 0 01A: C0 2- Way Mi r N/ Gr p' d RW 516/ dev/ r dsk/ c4t0d1s2 0085 16B: 0 02A: C0 2- Way Mi r N/ Gr p' d RW 516/ dev/ r dsk/ c4t0d2s2 0086 16B: 0 01B: C0 2- Way Mi r N/ Gr p' d RW 516/ dev/ r dsk/ c4t0d3s2 0087 16B: 0 02B: C0 2- Way Mi r N/ Gr p' d RW 516/ dev/ r dsk/ c4t1d0s2 0088 16B: 0 01A: D0 2- Way BCV Mi r N/ Asst ' d RW 516/ dev/ r dsk/ c4t1d1s2 0089 16B: 0 02A: D0 2- Way BCV Mi r N/ Asst ' d RW 516/ dev/ r dsk/ c4t1d2s2 008A 16B: 0 01B: D0 2- Way BCV Mi r N/ Asst ' d RW 516/ dev/ r dsk/ c4t1d3s2 008B 16B: 0 02B: D0 2- Way BCV Mi r N/ Asst ' d RW 516…………………………………………………………………………………………………………………………………………………………………………………………………………………

You can use options with the sympd l i st command to display only devices of specific interest. For

example, use the - powerpat h option to display only the PowerPath devices in a Symmetrix unit.

sympd list -powerpath

Symmet r i x I D: 000185500814

P O W E R P A T H D E V I C E S


CapPhysi cal Sym SA : P DA : I T Conf i g At t r i but e St s ( MB)- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

/ dev/ r dsk/ emcpower0c 041C 02A: D3 Unpr ot ect ed N/ Gr p' d RW 5754/ dev/ vx/ r dmp/ c4t 0d114s2 - 12B: 0 - - - - -/ dev/ r dsk/ c4t 0d114s2 - 05B: 0 - - - - -/ dev/ r dsk/ c5t 0d114s2 - 12B: 0 - - - - -

/ dev/ r dsk/ emcpower1c 041D 15B: D3 Unpr ot ect ed Gr p' d RW 8632/ dev/ vx/ r dmp/ c4t 0d115s2 - 12B: 0 - - - - -/ dev/ r dsk/ c4t 0d115s2 - 05B: 0 - - - - -/ dev/ r dsk/ c5t 0d115s2 - 12B: 0 - - - - -

Each PowerPath device in this display is configured to have multiple physical device names and SA (SCSI

adapter) connections that provide alternate paths for load-balancing and failover capabilities. The physical

device names all represent the same PowerPath device (for example, four physical device names represent




4/5/2004

the PowerPath device 041C). The “emcpower” name is a PowerPath pseudo name; some operating systems

display this name, some do not. Depending on the circumstances, PowerPath determines which path to use.

When determining devices to add to a device group or composite group, you can list devices that have the

same type of configuration. Table 2 lists some common options. For a complete list of options, refer to EMC Solutions Enabler Symmetrix Base Management CLI Product Guide.

Table 2. Useful Options with the symdev list Commands

Option Display

- r1 All RDF1 type (R1) devices.

- bcv All BCV devices.

- dr v All DRV devices.

- met a All meta devices.

- vdev All virtual devices.

- savedev All save devices

- rai ds All RAID-S devices

- rai d5 All RAID-5 devices

- dynami c All devices configured with the capability to become dynamic RDF devices.

- hotspar e All devices that have a dynamic (hot) spare invoked against them.

- r1 - bcv All RDF1 BCV devices (BCVs configured to copy data to a target R2 device).

- si d # - bcv All BCV devices on the Symmetrix identified by its sid number, which is useful forlisting BCVs on a remote Symmetrix while issuing commands from the local host.

- nobcv All standard devices.

- r ange begin: end A range of devices between a beginning device name and an ending device name.

- N # The number of devices to list (for example, –N 9 to list nine devices).

Because the primary purpose of RDF BCV devices is to mirror data from a local Symmetrix on a target

Symmetrix, these BCV devices are usually configured to be not accessible (not visible) to the local host for

read/write access. The following display shows R1 BCV devices that, in this instance, happen to be “NotVisible” to this host. “N/Asst’d” means the devices are not associated with any existing device group orcomposite group.

symdev list -r1 -bcv

Symmet r i x I D: 000184501161


CapSym Physi cal SA : P DA : I T Conf i g At t r i but e St s ( MB)- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -02E0 Not Vi si bl e ???: ? 15A: D5 RDF1- BCV N/ Asst ' d RW 4315

02E1 Not Vi si bl e ???: ? 02A: C5 RDF1- BCV N/ Asst ' d RW 431502E2 Not Vi si bl e ???: ? 02A: D5 RDF1- BCV N/ Asst ' d RW 4315




4/5/2004

The following symdev l i st command invoked from the local host displays BCVs on remote

Symmetrix 505. These remote devices are “Not Visible” to (not accessible for I/O by) the local host.

symdev list –sid 505 -bcv

Symmet r i x I D: 000185500505


CapSym Physi cal SA : P DA : I T Conf i g At t r i but e St s ( MB)- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -02E0 Not Vi si bl e ??? : ? 16B: D5 BCV N/ Asst ' d RW 431502E1 Not Vi si bl e ??? : ? 15B: D5 BCV N/ Asst ' d RW 431502E2 Not Vi si bl e ??? : ? 02B: D5 BCV N/ Asst ' d RW 4315

For detailed configuration information about a specific device, use the sympd show PdevName

command or symdev show SymDevName. The following symdev show command displays the

details of BCV 64, which is an R1 BCV that belongs to a device group named sar. It acquired the logicaldevice name BCV001 by default when it was associated with this device group. Figure 2 at the end of this

display illustrates the configuration in which this device participates.

symdev show 64

Symmet r i x I D: 000185500814

Devi ce Physi cal Name : Not Vi si bl e

Devi ce Symmet r i x Name : 0064Devi ce Ser i al I D : N/ ASymmet r i x I D : 000185500814

Devi ce Gr oup Name : sarDevi ce Logi cal Name : BCV001

Vendor I D : EMCPr oduct I D : SYMMETRI XProduct Revi si on : 5568

Devi ce Emul at i on Type : FBADevi ce Def i ned Label Type: N/ ADevi ce Def i ned Label : N/ ADevi ce Sub Syst em I d : 0x0140

Devi ce Bl ock Si ze : 512

Devi ce Capaci t y

{Cyl i nder s : 9206

Tr acks : 138090512- byt e Bl ocks : 8837760MegaByt es : 4315Ki l oByt es : 4418880}




4/5/2004

Devi ce Conf i gur at i on : RDF1- BCV

“Dynamic Spare Invoked: No” means that no dynamic spare (hot spare) was invoked for a failed disk.

Dynami c Spar e I nvoked : No

The “Service State: Normal” is a setting that relates to mirrors. If the configuration is SRDF family and

partitioned, the service state for SRDF is Degraded. If the configuration is TimeFinder family and the DAis write-disable, the service state is Degraded; if the DA is Not Ready, the service state is Failed.

Devi ce Servi ce St ate : Normal

The “Device Status: Not Ready” means that the host cannot read or write to the device, but it can “see” it(for example, when a BCV is established and goes to an NR state).

Devi ce Stat us : Not Ready ( NR)

The “Device SA Status: N/A” means that the device is not mapped to an SA. Other possible settings whenchecking the read/write status on the SA are Not Ready, Write Disabled, or Ready.

Devi ce SA St atus : N/ A ( N/ A)

Mi r r or Set Type : [ Data, R2 Remote, N/ A, N/ A]

Mi r r or Set DA St atus : [ NR, NR, N/ A, N/ A]

Mi r r or Set I nv. Tr acks : [ 0, 0, 0, 0]

The next section displays Disk Director information related to Symmetrix device 64. The “Hyper Status” of

Not Ready means that the part of the physical disk to which BCV 64 is mapped is not currently accessiblefor reads or writes by its host. Either the BCV device is established (which is the case here) or it is in

trouble (Not Ready) on the DA.

Back End Di sk Di r ect or I nf ormat i on{Hyper Type : Dat aHyper Stat us : Not Ready ( NR)Di sk [ Di r ector, I nt er f ace, TI D] : [ 16A, C, 1]Di sk Di r ect or Vol ume Number : 25Hyper Number : 8Di sk Capaci t y : 70007m

Hyper Type : R2 Remot eHyper Stat us : Not Ready ( NR)Di sk [ Di r ector, I nt er f ace, TI D] : [ N/ A, N/ A, N/ A]Di sk Di r ect or Vol ume Number : N/ AHyper Number : N/ A}

The BCV Pair Information section shows that BCV 64 is paired with local standard device 0000.

BCV Pai r I nf ormat i on{St andar d ( STD) Devi ce Symmet r i x Name : 0000Standard ( STD) Devi ce Ser i al I D : 14000000St andard ( STD) Devi ce Gr oup Name : sar

BCV Devi ce Symmet r i x Name : 0064




4/5/2004

BCV Devi ce Ser i al I D : Not Vi si bl eBCV Devi ce Associ at ed Gr oup Name : sar

The “BCV Device Status: Not Ready” means that currently there is no read/write access to the BCV by its

host. “State of Pair” indicates that the BCV pair is currently in the Synchronized state.

BCV Devi ce Stat us : Not Ready ( NR BCV)

St at e of Pai r ( STD ====> BCV ) : Synchr oni zed Ti me of Last BCV Act i on : Tue Mar 18 14: 28: 02 2003

The “BCV State Flags: (inc)” means that, on the next split operation, data from the BCV’s moving mirror

will be incrementally copied to its fixed mirror. Ordinarily, this setting is displayed on a full establish.

BCV St at e Fl ags : ( i nc)

Number of I nv. Tr acks f or STD Devi ce : 0Number of I nv. Tr acks f or BCV Devi ce : 0}

The RDF Information section of this display shows that BCV 64 is also configured as an SRDF pair with a

remote R2 device (218) on the remote Symmetrix (sid 505).

RDF I nf ormat i on{Devi ce Symmet r i x Name : 0064RDF Type : R1RDF ( RA) Gr oup Number : 2 ( B)

Remot e Devi ce Symmet r i x Name : 0218Remot e Symmet r i x I D : 000185500505

RDF Mode : Synchr onousRDF Adapt i ve Copy : Di sabl ed

RDF Adapt i ve Copy Wr i t e Pendi ng Stat e : N/ ARDF Adapt i ve Copy Skew ( Tr acks) : 65535

RDF Devi ce Domi no : Di sabl ed

RDF Li nk Conf i gur at i on : Di r ect Escon Fi br eRDF Li nk Domi no : Di sabl edPrevent Aut omat i c RDF Li nk Recover y : Di sabl edPr event RAs Onl i ne Upon Power ON : Enabl ed

“Device RDF Status: Ready” is specific to the R1 side, which is almost always Ready except when a deviceis in Domino mode. “Device SA Status: N/A” means that the device is not mapped to any SA. “Device RA

Status: Ready” means that the RA is ready for read/write activity. “Device Link Status: Not Ready” means

that the R1 device’s RDF link to the remote R2 device is currently suspended.

Devi ce RDF Stat us : Ready ( RW)

Devi ce SA St atus : N/ A ( N/ A)Devi ce RA St at us : Ready ( RW)Devi ce Li nk St at us : Not Ready ( NR)




4/5/2004

“Device Suspend State: N/A” means that the device does not belong to an enabled consistency group orthat it does but is synchronized and does not have an R1 suspend state. If the device is part of a tripped

consistency group, its Suspend State can be Pending Offline or Offline.“Device Consistency State:

Disabled” means that the device is not part of an enabled consistency group.

Devi ce Suspend Stat e : N/ ADevi ce Consi st ency St ate : Di sabl ed

“RDF Pair State” indicates that the SRDF pair is currently in the Suspended state, as you would expect

when an R1 BCV is synchronized locally as a BCV pair. (Establishing an R1 BCV in a local BCV pairingrelationship automatically suspends the R1 BCV’s RDF link to its paired R2 device.) “Device RDF State:

Not Ready” is a composite setting that means the R1 device (64) is not currently accessible for copying

data to its R2 device. “Remote Device RDF State” means that the remote R2 device (218) is write disabled

to its host.

Devi ce RDF Stat e : Not Ready ( NR)Remot e Devi ce RDF Stat e : Wr i t e Di sabl ed ( WD)

RDF Pai r Stat e ( R1 <- - > R2 ) : Suspended

The resolution of invalid tracks depends on which operation you perform. For instance, you can haveremote invalids on both the R1 and R2 sides prior to an establish or a restore operation. If so, performing an

establish operation copies modified R1 tracks to the R2 side. A restore operation indicates the opposite —that you want to copy modified R2 tracks to the R1 side. In this display, there are no invalid tracks.

Number of R1 I nval i d Tracks : 0Number of R2 I nval i d Tracks : 0}

Figure 2 shows that BCV 64 (the device previously displayed) is paired with local standard device 0000 as a

BCV pair and with standard device 218 as an SRDF pair. At the time of the show display, BCV 64 was

synchronized with standard 0000 and suspended from standard 218.

Local Symmetrix

814

Remote Symmetrix

505

SRDF

Pair

Standard

Source(R1)

RFD BCV

BCV Pair

0000

0064

Target(R2)

Standard

0218

CLI-000103

Host

Figure 2. Symmetrix Configuration for the symdev show 64 Command




4/5/2004

Displaying Information about SRDF Devices

In an SRDF configuration, you can examine the devices on your local Symmetrix to determine which are sourcedevices (Sym Dev), which are remote target devices (RDev), and whether a device is an R1 or R2 type device.

The symr df l i st command displays this information as well as other relevant data such as RDF group (G),

mode of operation, pair state, invalid tracks, and the state of each device and the RDF links that connect them.

symrdf list

Symmet r i x I D: 000000003264

Local Devi ce Vi ew- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

STATUS MODES RDF S T A T E SSym RDF - - - - - - - - - - - - - - R1 I nv R2 I nv - - - - - - - - - - - - - - - - - - - - - -Dev RDev Typ: G SA RA LNK MDA Tr acks Tr acks Dev RDev Pai r- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

0045 0045 R2: 2 RWWD NR S. . 0 49500 WD RW Suspended0046 0046 R2: 2 ?? WD NR S. . 0 33000 WD RW Suspended0047 0047 R2: 2 ?? WD NR S. . - - WD RW Suspended009C 0054 R1: 2 RW RW RW S. . 0 0 RW NR Synchr oni zed009D 0055 R1: 2 RW RW RW S. . 0 0 RW NR Synchr oni zed009E 0056 R1: 2 RW RW RW S. . 0 0 RW NR Synchr oni zed009F 0057 R1: 2 RW RW RW S. . 0 0 RW NR Synchr oni zed00A0 0058 R1: 2 RW RW RW C. W 0 0 RW NR Synchr oni zed00A1 0059 R1: 2 RW RW RW C. W 0 0 RW NR Synchr oni zed…………………………………………………………………………………………………………………………………………………………………………………………………… Legend f or MODES:

M( ode of Oper at i on) : A = Async, S = Sync, E = Semi - sync, C = Adapt i ve Copy

D( omi no) : X = Enabl ed, . = Di sabl edA( dapt i ve Copy) : D = Di sk Mode, W = WP Mode, . = ACp of f

Entries in the RDF Typ:G column identify the device as either an R1 or R2 device and the RDF (RA) group

number after the colon. The display also shows the state of the SRDF devices and their RDF links. For the

SRDF pairs that are in the Synchronized state, the R1 devices are read-writeable (RW), and the RDF linksare read-writeable (RW). However, the state of their remote devices (Rdev), which are acting as mirrors to

the R1 devices, are not ready (NR) and cannot be written to by the target-side host at this time.

The reverse is true for those SRDF pairs that are in the Suspended state. In this case, the R1 devices are

write disabled (WD), the RDF links are not ready (NR), and the remote devices are read-writeable (RW).

The R2 Ivalid Tracks column indicates the number of tracks that have been written to the R2 side since thesuspension of the RDF links.

The RDF links for these devices are operating either with synchronous replication (S) or Adaptive Copyreplication (C). Domino mode is disabled. The Adaptive Copy type can either Adaptive Copy Disk (D) or

Adaptive Copy Write-Pending (W). Status information about the Front End Director (SA) and Remote LinkDirector (RA) is also displayed.

By default, symr df l i st displays devices by their Symmetrix device name. To display host-visible

devices by their physical device name, include the pd argument on the command line.




4/5/2004

Options such as –r 1, –r 2, –bcv, or –nobcv allow you to display a list of specific interest, such as

just the R1 devices, R2 devices, BCV devices, or standard devices. For a complete list of options for thiscommand, refer to EMC Solutions Enabler Symmetrix SRDF CLI Product Guide.

If the concurrent RDF configuration state is enabled for a Symmetrix unit, use the –concur r ent option

to display devices that are configured as concurrent RDF pairs. For example:

symrdf list -sid 77 -concurrent

Symmet r i x I D: 000185400077



0028 0050 R1: 1 RW RW RW S. . 0 0 RW WD Synchr oni zed0000 R1: 2 RW RW RW S. . 0 0 RW WD Synchr oni zed

0029 0051 R1: 1 RW RW RW S. . 0 0 RW WD Synchr oni zed0001 R1: 2 RW RW RW S. . 0 0 RW WD Synchr oni zed

……………………………………………………………………………………………………………………………………………………………………………………………………

The display shows an R1 source device (0028) paired with two R2 target devices (0050 and 0000);

Symmetrix device 0029 is paired concurrently with devices 0051 and 0001. Note that each of the twoconcurrent devices of an SRDF concurrent pair belongs to a different RDF group (1 and 2).

If the dynamic RDF configuration state is enabled for a Symmetrix unit, you can use the –dynami c

option to display SRDF pairs whose devices have been configured as dynamic RDF devices.

symrdf list -dynamic

Symmet r i x I D: 000184600249



0072 0092 R1: 1 RW RW RW S. . 0 0 RW WD Synchr oni zed0073 0093 R1: 1 RW RW RW S. . 0 0 RW WD Synchr oni zed0074 0094 R1: 1 RW RW RW S. . 0 0 RW WD Synchr oni zed……………………………………………………………………………………………………………………………………………………………………………………………………

You can display subsets of dynamic SRDF pairs by including various options with the command. Including

the –both option displays dynamic SRDF pairs in which the paired devices have been configured to beeither R1 or R2 devices (a requirement for dynamic R1/R2 swap). Including the –r 1 option displays only

dynamic SRDF pairs in which R1 devices cannot become R2 devices. Including the –r 2 option displays

only R2 devices that cannot become R1 devices.




4/5/2004

Displaying Information about BCV Devices

Information about BCV devices is stored in two different locations:

• Information about devices defined in a device group or composite group is stored in your host’s

SYMAPI database file or in a GNS-managed global repository.

• Pairing information about BCV pairs and their current state is stored in the Symmetrix global memory.

When you initially form a device group or composite group, membership information about the group’s

BCVs and standards may differ from the pairing information stored inside the Symmetrix. For example, a

BCV or standard that you add to your device group could have a current pairing relationship with a devicethat does not belong to the device group.

Figure 3 shows that while the standard device 84 and BCV 89 are members of the same device group, therecord in the Symmetrix indicates that the same standard device 84 was last paired with BCV 88 and still

has a pairing relationship with that device. Any attempt to establish an 84/89 pair would fail without the use

of a preferred pair attachment or symmi r – f ul l est abl i sh command options that override the

standard’s prior pairing relationship with BCV 88.

CLI-000101

STD84

BCV89

Device groupdefinitionsstored inSYMAPI

databaseon host

BCV88

Standard/BCVpairing

informationstored in

Symmetrix

Symmetrix

Host

Figure 3. Device Group Memberships that Overlap with BCV Pairing Relationships

If you are creating BCV pairing relationships from devices that have never been paired, the process isrelatively straightforward. However, if previous pairings may exist from old device groups, check the status

of devices before adding them to your group. Even if no old device groups exist, device pairings may have

been made using a device file, or the Symmetrix may still be keeping track of device pairs that belonged toan old device group that was deleted, or devices may have been paired from a different host.




4/5/2004

To check if BCV devices already belong to a device group, use the symdev l i st –bcv command:

symdev list -bcv


Devi ce Name Di r ect or s Devi ce- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -Cap

Sym Physi cal SA : P DA : I T Conf i g At t r i but e St s ( MB)- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

0088 / dev/ r dsk/ c4t1d0s2 16B: 0 01A: D0 2- Way BCV Mi r N/ Asst ' d RW 5160089 / dev/ r dsk/ c4t1d1s2 16B: 0 02A: D0 2- Way BCV Mi r N/ Asst ' d RW 516008A / dev/ r dsk/ c4t 1d2s2 16B: 0 01B: D0 2- Way BCV Mi r Ass t ' d RW 516008B / dev/ r dsk/ c4t 1d3s2 16B: 0 02B: D0 2- Way BCV Mi r Ass t ' d RW 516…………………………………………………………………………………………………………………………………………………………………………………………………………………

“Asst’d” means that BCVs 8A and 8B belong to (are associated with) a device group or composite group

(or both a device group and a composite group). “N/Asst’d” means that BCVs 88 and 89 are not associated

with a group. To determine which group BCVs 8A and 8B belong to, you can use the symdev show 8A and symdev show 8B commands. To check if BCV devices have a current pairing relationship, use the

symbcv l i st command:

symbcv list

Symmet r i x I D: 000187900035

BCV Devi ce Standar d Devi ce Stat us- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

I nv. I nv.Physi cal Sym RDF At t . Tracks Physi cal Sym Tracks BCV <=> STD- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Not Vi si bl e 001A R1 0 N/ A N/ A 0 Never Est abNot Vi si bl e 001B R1 0 N/ A N/ A 0 Never Est abNot Vi si bl e 001C R1 0 Not Vi si bl e 0012 0 Synchr oni zedNot Vi si bl e 001D R1 0 Not Vi si bl e 0013 0 Synchr oni zedNot Vi si bl e 001E R1 + 0 Not Vi si bl e 0014 0 Synchr oni zedNot Vi si bl e 001F R1 + 0 Not Vi si bl e 0015 0 Synchr oni zedNot Vi si bl e 0020 R1 0 Not Vi si bl e 0016 0 Synchr oni zedNot Vi si bl e 0021 R1 0 Not Vi si bl e 0017 0 Synchr oni zedNot Vi si bl e 0022 R1 0 Not Vi si bl e 0018 0 Synchr oni zedNot Vi si bl e 0023 R1 0 Not Vi si bl e 0019 0 Synchr oni zedNot Vi si bl e 0088 ( M) 0 N/ A N/ A 0 Never Est abNot Vi si bl e 0089 ( m) - N/ A N/ A - NeverEst abNot Vi si bl e 008A ( m) - N/ A N/ A - NeverEst ab

…………………………………………………………………………………………………………………………………………………………………………………………………………Not Vi si bl e 0187 R1 + 0 r dmp/ c15t2d4s2* 005B 0 Synchr oni zedNot Vi si bl e 0188 R1 + 0 r dmp/ c15t2d5s2* 005C 0 Synchr oni zedNot Vi si bl e 0189 R1 + 0 r dmp/ c15t2d6s2* 005D 0 Synchr oni zed…………………………………………………………………………………………………………………………………………………………………………………………………………Legend f or t he At t r i but e of BCV Devi ces:

( *) : Associ at ed wi t h a gr oup.( +) : Associ ated wi t h a group and i t s pai r ed STD devi ce i s a member of same.( - ) : Associ ated wi t h a group but i t s pai r ed STD devi ce i s NOT a member of same.




4/5/2004

The Synchronized status of BCVs in the display means that these devices have a current pairing

relationship with a standard device. Symbols described in the Legend of the display indicates if a BCV

belongs to a group and whether a BCV’s paired standard device also belongs to the same group.

The display also shows BCVs that are not visible to the host and those that do not have a current pairingrelationship. NeverEstab means never established. Also, some BCVs constitute a meta device — for

example, a meta head (M) and two meta members (m).

Displaying Information about a Device Group orComposite Group

The symdg l i st command displays a list of any device groups that have already been defined in your

host’s SYMAPI database file or GNS-managed global repository. The symdg show DgName

command displays the membership and configuration details of any existing device group. The commands

symcg l i st and symcg show CgName display the same information for a composite group.

The following display of a device group named RDFGrp1 shows that the group includes seven local

standard devices, seven locally associated BCVs, and seven remotely associated BCVs (devices located on

a remote Symmetrix unit but associated with the device group defined on the local host). Figure 4 in themiddle of this display illustrates this configuration. The device group also includes one gatekeeper device(GK), which means that this gatekeeper device is dedicated to the standard devices in this device group.

symdg show RDFGrp1

Gr oup Name: RDFGr p1

Gr oup Type : REGULARDevi ce Gr oup i n GNS : YesVal i d : YesSymmet r i x I D : 000185500814Gr oup Cr eat i on Ti me : Tue J an 6 12: 08: 17 2004Vendor I D : EMC Cor p

Appl i cat i on I D : SYMCLI

Number of STD Devi ces i n Gr oup : 7Number of Associ at ed GK' s : 1Number of Local l y- associ at ed VDEV' s : 0Number of Local l y- associ ated BCV' s : 7Number of Remot el y- associ at ed BCV' s ( STD RDF) : 0Number of Remot el y- associ at ed BCV' s ( BCV RDF) : 7Number of Remot el y- assoc' d RBCV' s ( RBCV RDF) : 0




4/5/2004

St andard ( STD) Devi ces ( 7) :{- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Sym CapLdevName PdevName Dev At t . St s ( MB)- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -DEV001 / dev/ vx/ r dmp/ c4t 0d107s2 03F7 RW 1031DEV002 / dev/ vx/ r dmp/ c4t 0d108s2 03F8 RW 1031DEV003 / dev/ vx/ r dmp/ c3t 4d3s2 03F9 RW 1031DEV004 / dev/ vx/ r dmp/ c3t 0d0s2 03FA RW 1031DEV005 / dev/ vx/ r dmp/ c3t 0d1s2 03FB ( M) RW 4125DEV006 / dev/ vx/ r dmp/ c3t 0d2s2 03FF ( M) RW 4125DEV007 / dev/ vx/ r dmp/ c3t 0d3s2 0403 ( M) RW 4125}

Associ ated GateKeeper Devi ces (1) :{- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Sym CapLdevName PdevName Dev St s ( MB)

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -N/ A / dev/ vx/ r dmp/ c3t4d2s2 025B RW 3}

BCV Devi ces Local l y- associ at ed ( 7) :{- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Sym CapLdevName PdevName Dev At t . St s ( MB)- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -BCV001 N/ A 0407 NR 1031BCV002 N/ A 0408 NR 1031BCV003 N/ A 0409 NR 1031BCV004 N/ A 040A NR 1031BCV005 N/ A 040B ( M) NR 4125BCV006 N/ A 040F ( M) NR 4125BCV007 N/ A 0413 ( M) NR 4125}

BCV Devi ces Remot el y- associ at ed ( BCV RDF) ( 7) :{- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Sym CapLdevName PdevName Dev At t . St s ( MB)- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -BRBCV001 N/ A 03A0 RW 1031BRBCV002 N/ A 03A1 RW 1031

BRBCV003 N/ A 03A2 RW 1031BRBCV004 N/ A 03A3 RW 1031BRBCV005 N/ A 03A4 ( M) RW 4125BRBCV006 N/ A 03A8 ( M) RW 4125BRBCV007 N/ A 03AC ( M) RW 4125}




4/5/2004

Local Symmetrix

814

Remote Symmetrix

505

CLI-000100

BRBCV

R2Standard

R1

BCV

Host

Figure 4. Symmetrix Configuration for the symdg show RDFGrp1 Command

The first part of the symdg show output displays local information about the device group, including the

names and status of each device belonging to the group. Note that each device has a physical device name

(PdevName), Symmetrix device name (a four-digit hexadecimal number that the Symmetrix assigns to each

physical device)3, and logical device name (LdevName). When you add a device to a device group, a

logical device name is assigned to it by default or by specifying a specific name on the command line.

This second part of the symdg show output displays the device group’s RDF information, including the

identity of each remote Symmetrix unit in the configuration, RDF configuration settings, and the combined

state of all BCV RDF devices in the group and their RDF links.

Devi ce Gr oup BCV RDF I nf or mat i on{RDF Type : R1

RDF ( RA) Gr oup Number : 2 ( 00)

Remot e Symmet r i x I D : 000185500505

R2 Devi ce I s Lar ger Than The R1 Devi ce : Fal se

RDF Mode : Synchr onousRDF Adapt i ve Copy : Di sabl edRDF Adapt i ve Copy Wr i t e Pendi ng Stat e : N/ ARDF Adapt i ve Copy Skew ( Tr acks) : 65535


RDF Li nk Conf i gur at i on : Di r ect Escon Fi br eRDF Li nk Domi no : Di sabl edPrevent Aut omat i c RDF Li nk Recover y : Di sabl edPr event RAs Onl i ne Upon Power ON : Enabl ed


3 Prior to Enginuity version 5568, a Symmetrix device name is a three-digit hexadecimal number.




4/5/2004

Devi ce RA St at us : Ready ( RW)Devi ce Li nk St at us : Not Ready ( NR)

Devi ce Suspend St ate : Of f l i neDevi ce Consi st ency St ate : Di sabl edRDF R2 Not Ready I f I nval i d : Enabl ed

Devi ce RDF Stat e : Not Ready ( NR)Remot e Devi ce RDF St at e : Ready ( RW)

RDF Pai r St at e ( R1 =====> R2 ) : Fai l ed Over


The SYMCLI query argument is a useful means of displaying information about device pairs, especially

real-time status of Symmetrix devices belonging to a device group or composite group. Querying a

TimeFinder device group or composite group displays the state of BCV pairs in a Symmetrix unit.

Querying an SRDF device group or composite group displays the state of SRDF pairs in a configuration in

which data copying occurs over RDF links. Table 3 lists some commands that use the query argument.

Table 3. Useful query Commands

Query Command Displays

symmi r query Status of BCV pairs that belong to a device group or composite group.

symsnap query Status of snap pairs that belong to a device group or composite group.

symcl one quer y Status of clone pairs that belong to a device group or composite group.

symr df query Status of SRDF pairs that belong to a device group or composite group.

symr epl i cate query Status of SRDF/AR copy cycles being processed in the background.

The following symmi r quer y command shows the status of the four BCV pairs in a device group

named ProdBgrp after an establish operation was performed. Two of the pairs are fully synchronized, andtwo are still in progress (the BCV’s Inv Tracks column indicating the number of invalid tracks on the BCV

that still need to be copied from the standard device). An asterisk (*) next to the BCV’s device name meansthat the BCV belongs to the device group. If the asterisk is absent, the BCV is outside the device group.

symmir -g ProdBgrp query

Devi ce Gr oup ( DG) Name: Pr odBgrpDG' s Type : REGULARDG' s Symmet r i x I D : 000000003264

Standar d Devi ce BCV Devi ce St at e- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

I nv. I nv.Logi cal Sym Tracks Logi cal Sym Tracks STD <=> BCV- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

DEV001 0084 0 BCV001 0088 * 0 Synchr oni zedDEV002 0085 0 BCV002 0089 * 0 Synchr oni zedDEV003 0086 0 BCV003 008A * 414 SyncI nPr ogDEV004 0087 0 BCV004 008B * 627 SyncI nPr og……………………………………………………………………………………………………………………………………………………………………………………………………………




4/5/2004

After splitting all BCV pairs in this device group and concurrently establishing DEV001 with BCV003 and

BCV004, a symmi r query command with the –mul t i option displays the DEV001 relationship with

the two concurrent BCVs as well as its prior pairing relationship with BCV001. The DEV002 standard

device still has a pairing relationship with BCV002. However, the prior pairing relationships of DEV003

and DEV004 with their BCVs were superceded by DEV001’s new pairing relationship with those BCVs.

symmir -g ProdBgrp query -multi

Devi ce Gr oup ( DG) Name: Pr odBgrpDG' s Type : REGULARDG' s Symmet r i x I D : 000000003264



DEV001 0084 0 BCV003 008A * 138090 SyncI nPr og0 BCV004 008B * 138090 SyncI nPr og

8 BCV001 0088 * 0 Spl i tDEV002 0085 0 BCV002 0089 * 0 Spl i t

Tot al ( Pr i mar y) - - - - - - - - - - - - - Tr ack( s) 0 138090MB( s) 0. 0 4315. 3

Table 4 lists some of the more commonly used options available with the symmi r query command.

Table 4. Options with the symmir query Command

Option Display

- at t ach The BCV attachment relationship and pairing relationship.

- mul t i All BCVs that can be incrementally established with or restored to the standard device.- bg All BCVs that are still splitting in the background after an instant split.

- percent Used with the –bg option to display what percent of the background split has occurred.

- protect The status of a protected restore operation.

- pr ot bcvest All BCVs that were established with the –protbcvest option (protected BCV).




4/5/2004

The symr df query command displays the state of a device group’s SRDF devices and their RDF

links.

symrdf -g Rdf1Grp query

Devi ce Gr oup (DG) Name: Rdf 1Gr p

DG' s Type : RDF1DG' s Symmet r i x I D : 000000003264

Sour ce ( R1) Vi ew Tar get ( R2) Vi ew MODES- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

ST LI STSt andard A N ALogi cal T R1 I nv R2 I nv K T R1 I nv R2 I nv RDF Pai rDevi ce Dev E Tr acks Tr acks S Dev E Tr acks Tr acks MDA STATE- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

DEV001 009C RW 0 0 RW 0054 WD 0 0 S. . Synchr oni zedDEV002 009D RW 0 830 RW 0055 WD 0 0 S. . SynchI nPr og

Tot al - - - - - - - - - - - - - - - - - - - - - - - - - - - - Tr ack( s) 0 0 0 0MB( s) 0. 0 0. 0 0. 0 0. 0

Legend f or MODES:

M( ode of Oper at i on) : A = Async, S = Sync, E = Semi - sync, C = Adapt i ve CopyD( omi no) : X = Enabl ed, . = Di sabl edA( dapt i ve Copy) : D = Di sk Mode, W = WP Mode, . = ACp of f

The R1 devices are read-writeable, and the RDF links are read-writeable. However, the R2 devices, which

are acting as mirrors to the R1 devices, are write disabled (WD) and cannot be written to by their target-side host(s) at this time. The link is operating with synchronous replication (indicated by S in the M

column). One of the SRDF pairs is fully synchronized and one is still in the process of synchronizing. Onthe SyncInProg pair, 830 R2 invalid tracks on the source (R1) side still remain to be copied to the target

device (0055) to complete the synchronization process. The R2 invalid tracks on the R1 side representthose tracks that are still “owed” to the R2 side.

Table 5 includes some of the more commonly used options with the symr df query command.

Table 5. Options with the symrdf query Command

Option Display

- bcv All RDF BCV devices.

- rdf a State of the SRDF/A devices and the status of the SRDF/A session.

- r df g al l Ensures that the display shows the status of both links of a concurrent SRDF pair.

- r df g # Status of each concurrent R2 mirror whose link is represented by the RDF group number (#).

- i # Redisplays SRDF pair status in intervals specified as a number (#) in seconds, which is

especially useful when monitoring an updat e –unt i l operation.




4/5/2004

Example 1: Verifying that Configuration Information inthe SYMAPI Database Shows the Current Conf iguration

Whenever a Symmetrix configuration is new or has changed, you need to ensure which Symmetrix units

are connected to your host and that the information about these Symmetrix units is current.

The symcf g di scover command builds or rebuilds your host’s SYMAPI database file with the most

current information about the physical devices directly connected to your host. The command scans all buses, collects information about all the devices found, and rebuilds the database with collected

information from all locally and remotely attached Symmetrix devices.

# symcfg discover

Thi s oper at i on may t ake up t o a f ew mi nut es. Pl ease be pat i ent . . .

The symcf g l i st command displays the configuration information from the local host’s SYMAPI

database file.

# symcfg list

S Y M M E T R I X



The symcf g ver i f y command determines if the Symmetrix configuration and the SYMAPI database

file are in sync. If they are out of sync, the verify action returns code 24 (CLI _C_NOT_I N_SYNC). If they

are in sync, the verify action returns code zero (the CLI _C_SUCCESS value) as shown below using the

echo $st at us command.

# symcfg verify -sid 814

The Symmet r i x conf i gur at i on and t he dat abase f i l e ar e i n sync.

# echo $status 0

A new device is now added to local Symmetrix 814, changing the configuration. The ver i f y action is

repeated, and its output shows an out-of-sync condition. The echo $st atus command returns the

value 24, confirming that the configuration and the database configuration information are now out of sync.


The Symmet r i x conf i gur at i on and t he dat abase f i l e ar e NOT i n sync.

# echo $status 24




4/5/2004

The symcf g di scover command rebuilds your host’s SYMAPI database file with the most current

information.

# symcfg discover

Thi s oper at i on may t ake up t o a f ew mi nut es. Pl ease be pat i ent . . .

The symcf g l i st command now displays the updated configuration information from the local host’s

rebuilt SYMAPI database file. Note that the number of Symmetrix devices displayed for Symmetrix 814

has increased from 938 (shown in the previous symcf g l i st command) to 939.

# symcfg list

S Y M M E T R I X


000185500814 Local DMX800 5670 6144 204 939

000185500505 Remot e DMX800 5670 6144 0 763

The symcf g ver i f y command confirms that the configuration and SYMAPI database file are now in

sync again.


The Symmet r i x conf i gur at i on and t he dat abase f i l e ar e i n sync.




4/5/2004

Example 2: Obtaining More Symmetrix Information

This example illustrates some of the more useful symcf g l i st options not described earlier in this

paper.

Using the –connect i ons option with symcf g l i st command allows you to see the host

connections to a Symmetrix unit. Only those hosts that have at least one registered application are listed.The node name hk185500814 is the service processor.

# symcfg list -connections

Symmet r i x I D : 000185500814

Symmet r i x Host- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -Di r ect or Por t Node Name I P Addr ess HW Type OS Name OS Revi si on- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

DA- 1A 0 hk185500814 172. 26. 131. 103 I NTEL Wi nNT 4. 0. 1381

SA- 4A 0 api 183 172. 23. 65. 183 9000/ 800 HPUX B. 11. 00SA- 13A 0 api 183 172. 23. 65. 183 9000/ 800 HPUX B. 11. 00SA- 4B 0 api 212 172. 23. 65. 212 9000/ 800 HPUX B. 11. 00FA- 5B 0 api 179 172. 23. 65. 179 sun4u SunOS 5. 8FA- 12B 0 api 179 172. 23. 65. 179 sun4u SunOS 5. 8

Using the –sort host option with the –connect i ons option and symcf g l i st command allows

you to display the host connections to Symmetrix units by host rather than by Symmetrix ID. The ellipsis

(……) represents truncated output.

# symcfg list -connections -sorthost

Host Symmet r i x- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Node Name I P Addr ess OS Name OS Revi si on I D Di r ect or Por t- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

hk185500814 172. 26. 131. 103 Wi nNT 4. 0. 1381 000185500814 DA- 1A 0

api 179 172. 23. 65. 179 SunOS 5. 8 000185500814 FA- 5B 0000185500814 FA- 12B 0

……………………………………………………………………………………………………………………………………………………………………………………………………………

External locks are used to lock access to the entire Symmetrix unit during critical operations. SYMAPI uses

lock numbers 0 to 15; applications assigned by EMC use lock numbers greater than 15. By default, the

symcf g l i st –l ock command displays what Symmetrix units have a lock number of 0 (used to lock

a Symmetrix during SRDF operations). The display shows two unlocked Symmetrix units.

# symcfg list -lock

S Y M M E T R I X L O C K S

Lock Lock Ti meSymmI D At t achment St at us Number Hel d ( Sec)

000185500814 Local Unl ocked N/ A N/ A000185500505 Remot e Unl ocked N/ A N/ A




4/5/2004

Using the –l ockn option with symcf g l i st displays Symmetrix units that have a specific lock

number. Specifying zero (0) in the following command displays Symmetrix units that currently have an

external lock for SRDF operations. That is, an SRDF control operation was executing when this command

was issued. Using the –l ockn RDF option displays Symmetrix units that have any of the sixteen locks

(0x100 to 0x10F) used during SRDF operations. Using the –l ockn ALL option displays these operation

locks plus other locks used by such applications as Optimizer, device masking, and Configuration Manager.

# symcfg list -lockn 0

S Y M M E T R I X L O C K S

Lock Lock Ti meSymmI D At t achment St at us Number Hel d ( Sec)

000185500814 Local Locked 0 8000185500505 Remot e Locked 0 8

Using the –appl i cat i ons option with symcf g l i st displays all applications that are registered in

a Symmetrix unit and that have accessed that Symmetrix unit. The following display lists such applications

on a Symmetrix unit (sid 814) connected to the local host. An application listed with the –connect i ons option is not listed here if it has never accessed the Symmetrix unit.

# symcfg list -applications

Symmet r i x I D : 000185500814

Host Appl i cat i on- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -Node Name I P Addr ess I D Vendor I D Versi on At t r- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

api 179 172. 23. 65. 179 SYMCLI EMC Cor p 5. 0. 0. 1 -

SYMCLI EMC Cor p 5. 0. 0. 0 -EMCpower EMC Cor p 2. 1. 0. 0 -SYMCLI EMC Cor p 5. 0. 0. 32 -SYMCLI EMC Cor p 5. 0. 0. 29 -

api 180 172. 23. 65. 180 SYMCLI EMC Cor p 5. 0. 0. 32 ( R)

hk185500814 172. 26. 131. 103 OPTI MI ZER EMC Cor p 2. 0. 0. 4 -

Legend f or At t r i but e( s) :

( M) : Appl i cat i on Regi st er ed Remotel y vi a RDF l i nks ( Mul t i - Hop) .( R) : Appl i cat i on Regi st er ed Remotel y vi a RDF l i nks ( One- Hop) .




4/5/2004

Using the –semaphores option with symcf g l i st displays gatekeeper (GK), database (DB), and

lock file (FILE) semaphores.

# symcfg list -semaphores

S Y M A P I S E M A P H O R E S

Lock Pr oc.I D Key St ate Type Wai t Lock Ful l Pat h Speci f i cat i on- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

1 0x45000327 Unl ocked GK 0 / dev/ r dsk/ c4t 0d103s23 0x45000ba7 Unl ocked GK 0 / dev/ r dsk/ emcpower 218c1 0x45000327 Unl ocked DB 0 / var / symapi / db/ symapi _db. bi n0 0x45000246 Unl ocked FI LE 0 / var / symapi / conf i g/ symapi sl ck

Using the –ser vi ces option with symcf g l i st command displays configured network services for

use by the SYMAPI client. These services are listed in the network services file (netcnfg) in the/var/symapi/config directory.

# symcfg list -services

S Y M A P I N E T S E R V I C E S

PortName Domai n Type Node Name Addr ess Number- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

api 182 TCPI P api 182 172. 23. 65. 182 2707




4/5/2004

Example 3: Obtaining More Device Information

This example illustrates some of the more useful symdev l i st options not described earlier in this

paper.

SYMAPI uses device external locks in a Symmetrix unit to lock device pairs during control operations with

TimeFinder family and SRDF family products. The following command displays external locks onstandard devices on Symmetrix 814 during a SRDF/AR operation. That is, the command was issued in themiddle of an SRDF/AR cycle.

# symdev list -lock

Symmet r i x I D: 000185500814

S Y M M E T R I X D E V I C E L O C K S

Devi ce Name Devi ce- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Lock Lock Seconds Lock Devi ce

Sym Physi cal Number Hol der I D Hel d Fl ags At t r i but e- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

03F7 / dev/ vx/ r dmp/ c4t 0d107s2 9 0x10010FE6 111 Long Gr p' d03F8 / dev/ vx/ r dmp/ c4t 0d108s2 9 0x10010FE6 111 Long Gr p' d03F9 / dev/ vx/ r dmp/ c3t 4d3s2 9 0x10010FE6 111 Long Gr p' d03FA / dev/ vx/ r dmp/ c3t 0d0s2 9 0x10010FE6 111 Long Gr p' d

Using the –mul t i por t option with the symdev l i st command displays devices that are mapped to

multiple front-end SCSI (SA) adapter ports. For example, the following display shows Symmetrix device

0000 mapped to SA ports 12B:0 and 05B:0. Other devices (Sym column) are mapped to these same ports.

# symdev list -multiport

Symmet r i x I D: 000185500814

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


CapPhysi cal Sym SA : P DA : I T Conf i g At t r i but e St s ( MB)- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

0000 16B: D1 2- Way Mi r Gr p' d RW 4315/ dev/ vx/ r dmp/ c4t 0d0s2 - 12B: 0 - - - - -/ dev/ vx/ r dmp/ c5t 0d0s2 - 12B: 0 - - - - -/ dev/ r dsk/ emcpower 116c - 05B: 0 - - - - -/ dev/ r dsk/ c4t 0d0s2 - 05B: 0 - - - - -/ dev/ r dsk/ c5t 0d0s2 - 12B: 0 - - - - -

0001 02B: D1 2- Way Mi r Gr p' d RW 4315/ dev/ vx/ r dmp/ c4t 0d1s2 - 12B: 0 - - - - -/ dev/ vx/ r dmp/ c5t 0d1s2 - 12B: 0 - - - - -/ dev/ r dsk/ emcpower 117c - 05B: 0 - - - - -/ dev/ r dsk/ c4t 0d1s2 - 05B: 0 - - - - -/ dev/ r dsk/ c5t 0d1s2 - 12B: 0 - - - - -




4/5/2004

0002 01B: D1 2- Way Mi r Gr p' d RW 4315/ dev/ vx/ r dmp/ c4t 0d2s2 - 12B: 0 - - - - -/ dev/ vx/ r dmp/ c5t 0d2s2 - 12B: 0 - - - - -/ dev/ r dsk/ emcpower 118c - 05B: 0 - - - - -/ dev/ r dsk/ c4t 0d2s2 - 05B: 0 - - - - -/ dev/ r dsk/ c5t 0d2s2 - 12B: 0 - - - - -…………………………………………………………………………………………………………………………………………………………………………………………………………………

00C8 01A: C2 RDF2+Mi r N/ Gr p' d WD 4315Not Vi s i bl e - 05A: 0 - - - - -Not Vi s i bl e - 12A: 0 - - - - -

00C9 15A: C2 RDF2+Mi r N/ Gr p' d WD 4315Not Vi s i bl e - 05A: 0 - - - - -Not Vi s i bl e - 12A: 0 - - - - -

Using the – f i r s tpor t option with the symdev l i st command displays just the first port of

information for devices that are mapped to multiple ports.

# symdev list -firstport

Symmet r i x I D: 000185500814


CapSym Physi cal SA : P DA : I T Conf i g At t r i but e St s ( MB)- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

0000 / dev/ vx/ r dmp/ c4t 0d0s2 12B: 0 16B: D1 2- Way Mi r Gr p' d RW 43150001 / dev/ vx/ r dmp/ c4t 0d1s2 12B: 0 02B: D1 2- Way Mi r Gr p' d RW 43150002 / dev/ vx/ r dmp/ c4t 0d2s2 12B: 0 01B: D1 2- Way Mi r Gr p' d RW 43150003 / dev/ vx/ r dmp/ c4t 0d3s2 12B: 0 16A: D1 2- Way Mi r Gr p' d RW 43150004 / dev/ vx/ r dmp/ c4t 0d4s2 12B: 0 15A: D1 2- Way Mi r Gr p' d RW 4315

0005 / dev/ vx/ r dmp/ c4t 0d5s2 12B: 0 01A: D1 2- Way Mi r Gr p' d RW 4315…………………………………………………………………………………………………………………………………………………………………………………………………………………

Using the –resv option with the sympd l i st command displays all Symmetrix devices that have

SCSI reservations.

# sympd list -resv

Symmet r i x I D: 000000003143

Devi ce Name Devi ce Reser vat i on- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -Physi cal Sym Conf i g I ni t i at or SA : P

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

/ dev/ r hdi sk20 0018 2- Way Mi r 07 01C: 0




4/5/2004

The symdev l i st command with the –met a option shows the meta head member on the meta

device. “Concated” means that the meta device consists of a certain number (“# of Devs”) of concatenated

devices. “Striped” means that the meta device is striped in “Stripe Size” chunks across “# of Devs” devices."Cap MB" is the total capacity of the entire meta device (meta head plus meta members).

# symdev list -meta

Symmet r i x I D: 000185500814

Devi ce Name Devi ce Met a I nf or mat i on- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -Sym Physi cal Conf i g At t r Conf i g St r i pe # of Cap

Si ze Devs ( MB)- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

0268 Not Vi si bl e RDF2+Mi r N/ Gr p' d Concat ed - 2 17263026A Not Vi si bl e RDF2+Mi r N/ Gr p' d St r i ped 960k 3 25895026D Not Vi si bl e RDF2+Mi r N/ Gr p' d St r i ped 3840k 3 258950270 Not Vi si bl e BCV N/ Asst ' d Concat ed - 2 17263

0272 Not Vi si bl e BCV N/ Asst ' d St r i ped 960k 3 258950275 Not Vi si bl e BCV N/ Asst ' d St r i ped 3840k 3 2589503C7 Not Vi si bl e Unpr ot ect ed N/ Gr p' d St r i ped 1920k 4 412503C8 Not Vi si bl e Unpr ot ect ed N/ Gr p' d St r i ped 7680k 4 412503D3 Not Vi si bl e Unpr ot ect ed N/ Gr p' d Concat ed - 4 412503D6 Not Vi si bl e Unpr ot ect ed N/ Gr p' d St r i ped 30720k 4 412503D7 Not Vi si bl e BCV N/ Asst ' d St r i ped 1920k 4 412503D8 Not Vi si bl e BCV N/ Asst ' d Concat ed - 4 412503DF Not Vi si bl e BCV N/ Asst ' d St r i ped 7680k 4 412503E0 Not Vi si bl e BCV N/ Asst ' d St r i ped 1920k 4 412503E2 Not Vi si bl e BCV N/ Asst ' d St r i ped 30720k 4 412503E5 Not Vi si bl e BCV N/ Asst ' d St r i ped 7680k 4 412503F4 Not Vi si bl e BCV N/ Asst ' d Concat ed - 4 412503F5 Not Vi si bl e BCV N/ Asst ' d St r i ped 30720k 4 412503FB / dev/ r dsk/ emcpower229c 2- Way Mi r Gr p' d St r i ped 7680k 4 412503FF / dev/ vx/ r dmp/ c3t 0d2s2 2- Way Mi r Gr p' d Concat ed - 4 41250403 / dev/ vx/ r dmp/ c3t 0d3s2 2- Way Mi r Gr p' d St r i ped 15360k 4 4125040B Not Vi si bl e RDF1- BCV+Mi r Asst ' d St r i ped 7680k 4 4125040F Not Vi si bl e RDF1- BCV+Mi r Asst ' d Concat ed - 4 41250413 Not Vi si bl e RDF1- BCV+Mi r Asst ' d St r i ped 15360k 4 4125




4/5/2004

When a disk fails, a hot spare (a spare disk) is invoked against it. All devices that have mirrors

(hypervolumes) on the failed disk against which the hot spare was invoked, are shown in the

symdev l i st –hot spare display as having a hot spare invoked against them. This display shows

that Symmetrix 120 has not had any hot spares invoked against failed disks, whereas Symmetrix 180 shows

one hot (dynamic) spare invocation against disk 01A:D0. Note that “Unprotected” devices with a hot spare

invoked against them become not ready (NR) because unprotected devices have no mirror to kick in tomirror the spare hypervolume. On the other hand, mirrored devices stay ready (RW) when a hot spare isinvoked against them.

# symdev list -hotspare

Symmet r i x I D: 000184500120

Coul d not sel ect any Symmet r i x devi ces t o l i st .

Symmet r i x I D: 000184500180



0010 Not Vi si bl e ???: ? 01A: D0 Unpr ot ect ed N/ Gr p' d NR 1030098 Not Vi si bl e ???: ? 01A: D0 Unpr ot ect ed N/ Gr p' d NR 4700AE Not Vi si bl e 13A: 0 01A: D0 2- Way Mi r N/ Gr p' d RW 431500C7 Not Vi si bl e ???: ? 01A: D0 Unpr ot ect ed N/ Gr p' d NR 4700DF Not Vi si bl e ???: ? 01A: D0 Unpr ot ect ed N/ Gr p' d NR 4700F5 Not Vi si bl e ???: ? 01A: D0 Unpr ot ected N/ Gr p' d NR 470108 Not Vi si bl e ???: ? 01A: D0 2- Way Mi r N/ Gr p' d RW 469




4/5/2004

Example 4: Obtaining Information about Dynamic RDFDevices

This example looks for devices on a local source Symmetrix unit (sid 814) that are capable of being

dynamic RDF devices. Devices configured for RDF capability can be used to create dynamic SRDF pairs

while the Symmetrix units are in operation (“on the fly”).

The symcf g l i st command displays high-level information on Symmetrix units in this configuration.

# symcfg list

S Y M M E T R I X



With Enginuity version 5568 and higher, the symdev l i st command with the –dynami c optiondisplays devices configured for dynamic RDF capability. This command displays devices that have been

created as, or are capable of being created as, dynamic SRDF pairs using the symr df cr eatepai r

command. When combined with the –r 1 option, symdev l i st - dynami c displays devices

configured for dynamic R1/R24 and R1-only; when combined with the –r 2 option, the command displays

devices configured for dynamic R1/R2 and R2-only. “RDF1+Mir” in the display indicates devices that

have already been created as dynamic RDF devices.

# symdev list -sid 814 –dynamic –r1

Symmet r i x I D: 000185500814

Devi ce Name Di r ect or s Devi ce

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -CapSym Physi cal SA : P DA : I T Conf i g At t r i but e St s ( MB)- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

00F2 / dev/ r dsk/ emcpower224c 04A: 0 15B: C4 Unpr ot ect ed N/ Gr p' d RW 206300F5 / dev/ r dsk/ emcpower227c 04A: 0 01A: D1 Unpr ot ect ed N/ Gr p' d RW 206300FA / dev/ r dsk/ emcpower239c 04A: 0 15A: C4 Unpr ot ect ed N/ Gr p' d RW 20630106 / dev/ r dsk/ emcpower235c 04A: 0 01B: D3 Unpr ot ect ed N/ Gr p' d RW 2063010A / dev/ r dsk/ emcpower237c 04A: 0 15A: D3 Unpr ot ect ed N/ Gr p' d RW 2063010F / dev/ r dsk/ emcpower240c 04A: 0 02B: C2 Unpr ot ect ed N/ Gr p' d RW 20630145 Not Vi si bl e 04A: 0 01A: C1 RDF1+Mi r N/ Gr p' d RW 20630146 Not Vi si bl e 04A: 0 15A: C1 RDF1+Mi r N/ Gr p' d RW 20630147 Not Vi si bl e 04A: 0 02A: C1 RDF1+Mi r N/ Gr p' d RW 20630148 Not Vi si bl e 04A: 0 15A: D1 RDF1+Mi r N/ Gr p' d RW 20630149 Not Vi si bl e 04A: 0 02A: D1 3- Way Mi r N/ Gr p' d RW 2063014A Not Vi si bl e 04A: 0 16B: C4 3- Way Mi r N/ Gr p' d RW 2063014B Not Vi si bl e 04A: 0 02B: C4 3- Way Mi r N/ Gr p' d RW 2063

4 Devices intended for dynamic RDF swap must be configured with the dyn_r df attribute, which allows a device to be either an R1

or an R2 device (refer to the white paper Using the SYMCLI Configuration Manager , P/N 300-000-475).




4/5/2004

Example 5: Obtaining Information about Virtual Devices

The virtual device is a host-addressable Symmetrix device with special attributes created at configuration

time. But unlike the BCV, which contains a full volume of data, the virtual device is a “slim” device that

offers a space-saving way to create instant point-in-time copies of logical volumes. Any updates to a sourcedevice after its activation with a virtual device cause the pre-update image of the changed tracks to be

copied to a save device. The virtual device’s indirect pointer is then updated to point to this original trackdata, preserving a point-in-time image of the volume. TimeFinder/Snap uses this copy-on-first-writetechnique to conserve disk space, since only changes to tracks on the source cause any incremental storage

to be consumed. You use symsnap commands to create and activate a source/target snap pair .

This example looks on the local Symmetrix unit (000000006206) for devices configured as virtual devices.

The symdev l i st command displays devices on the Symmetrix unit that are configured as target

virtual devices (VDEV). Devices with the SV attribute have been configured as save devices. To list

VDEVs only, use symdev l i st –vdev. The ellipsis (……) indicates where superfluous output was

omitted or truncated.

C: \ > symdev list

Symmet r i x I D: 000000006206



0000 Not Vi si bl e ??? : ? 01A: C0 BCV Asst ' d RW 86320001 Not Vi si bl e ??? : ? 16C: D0 BCV Asst ' d RW 86320002 Not Vi si bl e ??? : ? 01B: D0 BCV Asst ' d RW 86320003 Not Vi si bl e ??? : ? 16D: C0 BCV Asst ' d RW 8632…………………………………………………………………………………………………………………………………………………………………………………………………………………

0048 Not Vi si bl e ??? : ? ???: ?? VDEV N/ Gr p' d RW 86320049 Not Vi si bl e ??? : ? ???: ?? VDEV N/ Gr p' d RW 8632004A Not Vi si bl e ??? : ? ???: ?? VDEV N/ Gr p' d RW 8632004B Not Vi si bl e ??? : ? ???: ?? VDEV N/ Gr p' d NR 8632004C Not Vi si bl e ??? : ? ???: ?? VDEV N/ Gr p' d NR 8632004D Not Vi si bl e ???: ? ???: ?? VDEV N/ Gr p' d NR 8632004E Not Vi si bl e ??? : ? ???: ?? VDEV N/ Gr p' d NR 8632004F Not Vi si bl e ??? : ? ???: ?? VDEV N/ Gr p' d NR 86320050 Not Vi si bl e ??? : ? ???: ?? VDEV N/ Gr p' d NR 86320051 Not Vi si bl e ??? : ? ???: ?? VDEV N/ Gr p' d NR 86320052 Not Vi si bl e ???: ? 16B: D1 2- Way Mi r N/ A ( SV) RW 86320053 Not Vi si bl e ???: ? 01C: C0 2- Way Mi r N/ A ( SV) RW 86320054 Not Vi si bl e ???: ? 16B: C0 2- Way Mi r N/ A ( SV) RW 8632

…………………………………………………………………………………………………………………………………………………………………………………………………………………




4/5/2004

The syml d l i st command displays devices that have been added to a device group named 3vdevs. The

source of any snap operation is standard device 0076. The targets can be three virtual devices (004F, 0050,

and 0051) that are paired with the standard device. At different points in time, each virtual device can bethe target of snap operation. The virtual devices do not yet have copy sessions with the standard device

(indicated by their status of NotCreated).

C: \ > symld list

Devi ce Gr oup ( DG) Name: 3vdevsDG' s Type : REGULARDG' s Symmet r i x I D : 000000006206

Standar d Devi ce Name Di r ect or s Devi ce- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

CapLogi cal Physi cal Sym SA : P DA : I T Conf i g At t St s ( MB)- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

DEV001 DRI VE29 0076 04A: 0 16C: D2 2- Way Mi r RW 8632

Legend f or STD devi ces:

( +) : Pai r ed wi t h a BCV devi ce t hat i s associ at ed wi t h t hi s dg.( - ) : Pai r ed wi t h a BCV devi ce t hat i s non- associ at ed wi t h t hi s dg.

Symmet r i x Vi r t ual Devi ces associ ated wi t h t hi s dg:

VDEV Devi ce Source Devi ce Stat us- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Logi cal Sym At t . St s Logi cal Sym SRC <=> VDEV- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

VDEV001 004F NR N/ A N/ A Not Cr eat edVDEV002 0050 NR N/ A N/ A Not Cr eat edVDEV003 0051 NR N/ A N/ A Not Cr eat ed

Legend f or VDEV devi ces:

( +) : VDEV i s pai r ed wi t h a member devi ce.( - ) : VDEV i s pai r ed wi t h a non- member devi ce.

The symsnap l i st command indicates whether there are snap copy sessions running on the

Symmetrix unit. This display shows that there are no copy sessions currently on Symmetrix 6206.

C: \ > symsnap list

Symmet r i x I D: 000000006206

No Snap sessi ons f ound




4/5/2004

The symsnap l i st command with the –savedevs option displays any save devices that have been

configured to hold data for virtual devices. This display indicates a list of save devices and that there has

not yet been any virtual device activity that caused tracks of data to be copied to these save devices.

C: \ > symsnap list -savedevs

Symmet r i x I D: 000000006206

Snap Save Devi ces- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Devi ce Tot al Used Fr ee Per centSym Type Tracks Tracks Tracks Ful l- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -0052 FBA 276210 0 276210 0%0053 FBA 276210 0 276210 0%0054 FBA 276210 0 276210 0%0055 FBA 276210 0 276210 0%0056 FBA 276210 0 276210 0%0057 FBA 276210 0 276210 0%

0058 FBA 276210 0 276210 0%0059 FBA 276210 0 276210 0%005A FBA 276210 0 276210 0%005B FBA 276210 0 276210 0%

Tot al - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Tr acks 2762100 0 2762100 0%

MB( s) 86315. 6 0. 0 86315. 6

The symsnap quer y command displays three snap copy sessions that are controlled within the device

group named 3vdevs. The –mul t i option is required to display multiple sessions.

C: \ > symsnap query –g 3vdevs -multi

Devi ce Gr oup ( DG) Name: 3vdevsDG' s Type : REGULARDG' s Symmet r i x I D : 000000006206

Source Devi ce Tar get Devi ce Stat e Copy- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Pr ot ect ed ChangedLogi cal Sym Tracks Logi cal Sym G Tracks SRC <=> TGT ( %)- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

DEV001 0076 276210 VDEV003 0051 X 0 CopyOnWr i t e 0273902 VDEV002 0050 X 2308 CopyOnWr i t e 0273603 VDEV001 004F X 2607 CopyOnWr i t e 0

Tot al - - - - - - - - - - - - - - - - - - Tr ack( s) 823715 4915MB( s) 25741. 0 153. 7

Legend:

( G) : The Tar get devi ce i s associ ated wi t h t hi s gr oup.




4/5/2004

Example 6: Obtaining More Device Group Information

The symdg l i st command displays a list of any device groups that have already been defined in your

host’s SYMAPI database file or GNS-managed global repository. The symdg show DgName command

displays the membership and configuration details of any existing device group.5 This example illustratesoptions for obtaining device group information not described earlier in this paper.

This display is similar to the symdg show RDFGrp1 display described previously, but shows a

configuration in which five local R1 devices are the source devices and five remotely associated BCVs are

the targets. That is, the R1 devices copy data to their R2 devices, which copy that data to the BCVs located

on the same remote Symmetrix unit.

# symdg show rdf1-grp

Gr oup Name: r df 1- grp

Gr oup Type : RDF1Devi ce Gr oup i n GNS : YesVal i d : Yes

Symmet r i x I D : 000187900035Gr oup Cr eat i on Ti me : Tue J an 6 12: 08: 17 2004Vendor I D : EMC Cor pAppl i cat i on I D : SYMCLI

Number of STD Devi ces i n Gr oup : 5Number of Associ at ed GK' s : 0Number of Local l y- associ ated BCV' s : 0Number of Local l y- associ at ed VDEV' s : 0Number of Remot el y- associ at ed BCV' s ( STD RDF) : 5Number of Remot el y- associ at ed BCV' s ( BCV RDF) : 0Number of Remot el y- assoc' d RBCV' s ( RBCV RDF) : 0

St andard ( STD) Devi ces ( 5) :

{- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Sym CapLdevName PdevName Dev At t . St s ( MB)- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -DEV001 / dev/ vx/ r dmp/ c4t 0d102s2 03C2 RW 4315DEV002 / dev/ vx/ r dmp/ c4t 0d103s2 03C3 RW 4315DEV003 / dev/ vx/ r dmp/ c4t 0d104s2 03C4 RW 4315DEV004 / dev/ vx/ r dmp/ c4t 0d105s2 03C5 RW 4315DEV005 / dev/ vx/ r dmp/ c4t 0d106s2 03C6 RW 4315}

5 The symcg l i st and symcg show commands display the same information for a composite group.




4/5/2004

BCV Devi ces Remot el y- associ at ed ( STD RDF) ( 5) :{- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Sym CapLdevName PdevName Dev At t . St s ( MB)- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -RBCV001 N/ A 02E0 RW 4315RBCV002 N/ A 02E1 RW 4315RBCV003 N/ A 02E2 RW 4315RBCV004 N/ A 02E3 RW 4315RBCV005 N/ A 02E4 RW 4315}

This second part of the symdg show output displays the device group’s RDF information, including the

identity of the remote Symmetrix unit (sid 41), RDF configuration settings (Enabled or Disabled), and the

combined state of all standard RDF devices in the group and their RDF links.

Devi ce Gr oup RDF I nf ormat i on{

RDF Type : R1RDF ( RA) Gr oup Number : 1 ( 00)

Remot e Symmet r i x I D : 000187900041

R2 Devi ce I s Lar ger Than The R1 Devi ce : Fal se

RDF Mode : Synchr onousRDF Adapt i ve Copy : Di sabl edRDF Adapt i ve Copy Wr i t e Pendi ng Stat e : N/ ARDF Adapt i ve Copy Skew ( Tr acks) : 65535


RDF Li nk Conf i gur at i on : Fi br eRDF Li nk Domi no : Di sabl edPrevent Aut omat i c RDF Li nk Recover y : Di sabl edPr event RAs Onl i ne Upon Power ON : Enabl ed


Devi ce RA St at us : Ready ( RW)Devi ce Li nk St at us : Not Ready ( NR)

Devi ce Suspend St ate : Of f l i neDevi ce Consi st ency St ate : Enabl edRDF R2 Not Ready I f I nval i d : Enabl ed

Devi ce RDF Stat e : Ready ( RW)Remot e Devi ce RDF Stat e : Wr i t e Di sabl ed ( WD)

RDF Pai r Stat e ( R1 <- - > R2 ) : Suspended





4/5/2004

It is possible to get device configuration and status information about devices by querying the device group

to which they have been added. The symmi r query command displays the status of BCV pairs in a

device group, Rdf1Grp, that contains one SRDF standard device and one local BCV device. The BCV pairis currently in the Split state.

# symmir -g Rdf1Grp query

Devi ce Gr oup (DG) Name: Rdf 1Gr pDG' s Type : RDF1DG' s Symmet r i x I D : 000185500810



DEV001 010F 0 BCV001 00CD * 0 Spl i t

Tot al - - - - - - - - - - - - - -MB( s) 0. 0 0. 0

Legend:

( *) : The pai r ed BCV devi ce i s associ at ed wi t h t hi s gr oup.

The symr df query command displays the state of the SRDF devices and their RDF links. Under

normal circumstances, the SRDF pair is synchronized. The RDF link is operating with synchronous

replication (indicated by an S in the M column).

# symrdf -g Rdf1Grp query

Devi ce Gr oup (DG) Name: Rdf 1Gr p

DG' s Type : RDF1DG' s Symmet r i x I D : 000000003264

Sour ce ( R1) Vi ew Tar get ( R2) Vi ew MODES- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

ST LI STSt andard A N ALogi cal T R1 I nv R2 I nv K T R1 I nv R2 I nv RDF Pai rDevi ce Dev E Tr acks Tr acks S Dev E Tr acks Tr acks MDA STATE- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

DEV001 009C RW 0 0 RW 0054 WD 0 0 S. . Synchr oni zedDEV002 009D RW 0 0 RW 0055 WD 0 0 S. . Synchr oni zed

Tot al - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Tr ack( s) 0 0 0 0MB( s) 0. 0 0. 0 0. 0 0. 0

Legend f or MODES:

M( ode of Oper at i on) : A = Async, S = Sync, E = Semi - sync, C = Adapt i ve CopyD( omi no) : X = Enabl ed, . = Di sabl edA( dapt i ve Copy) : D = Di sk Mode, W = WP Mode, . = ACp of f




4/5/2004

The symcl one quer y command with the –mul t i option displays a source device and its four clone

targets. The state of the clone operation shows that all four copy operations are currently in progress

(CopyInProg) and that each operation is 6% complete.

# symclone -g multiclone query -multi

Devi ce Gr oup ( DG) Name: mul t i cl oneDG' s Type : REGULARDG' s Symmet r i x I D : 000187900041

Source Devi ce Tar get Devi ce Stat e Copy- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Prot ect edLogi cal Sym Tr acks Logi cal Sym CG SRC <=> TGT ( %)- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

CLONESRC 0215 129275 CLONETGT1 0100 XX CopyI nPr og 6129277 CLONETGT2 0101 XX CopyI nPr og 6129276 CLONETGT3 0102 XX CopyI nPr og 6

129276 CLONETGT4 0103 XX CopyI nPr og 6

Tot al - - - - - - - - Tr ack( s) 517104MB( s) 16159. 5

Legend:

( C) : The backgr ound copy set t i ng i s act i ve f or t hi s pai r .( G) : The Tar get devi ce i s associ ated wi t h t hi s gr oup.

The symdg show command with the –l ock option displays existing device external locks on devices

within the device group named sar. The display shows which devices on the local and remote Symmetrixunits are locked during Symmetrix Automated Replication (that is, in the middle of a SRDF/AR cycle).

# symdg show sar -lock

S Y M M E T R I X D E V I C E G R O U P L O C K S

Gr oup Name: sar

Gr oup Type : REGULARVal i d : YesSymmet r i x I D : 000185500814Gr oup Cr eat i on Ti me : Tue Oct 14 09: 49: 41 2003Vendor I D : EMC Cor pAppl i cat i on I D : SYMCLI

Lock Number : 9

Number of Locked Devi ces i n Gr oup:

STD Devi ces : 16 ( SI D: 000185500814)Remote Mi r r ors of STD' s : 0 ( SI D: N/ A )BCV Devi ces : 16 ( SI D: 000185500814)Remot e Mi r r or s of BCV' s : 16 ( SI D: 000185500505)RBCV Devi ces : 0 ( SI D: N/ A )Remote Mi r r ors of RBCV' s : 0 ( SI D: N/ A )




4/5/2004

BRBCV Devi ces : 16 ( SI D: 000185500505)Remot e Mi r r ors of BRBCV' s : 0 ( SI D: N/ A )

STD Devi ces ( 16) :{- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -Sym Lock Di r ector Seconds LockDev Hol der- I D I ni t i ator Number Hel d Fl ags- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -03F7 0x1001100E 0 05B 12 Long03F8 0x1001100E 0 05B 12 Long03F9 0x1001100E 0 05B 12 Long03FA 0x1001100E 0 05B 12 Long03FB 0x1001100E 0 05B 12 Long03FC 0x1001100E 0 05B 12 Long03FD 0x1001100E 0 05B 12 Long03FE 0x1001100E 0 05B 12 Long03FF 0x1001100E 0 05B 12 Long0400 0x1001100E 0 05B 12 Long0401 0x1001100E 0 05B 12 Long

0402 0x1001100E 0 05B 12 Long0403 0x1001100E 0 05B 12 Long0404 0x1001100E 0 05B 12 Long0405 0x1001100E 0 05B 12 Long0406 0x1001100E 0 05B 12 Long}

BCV Devi ces ( 16) :{- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -Sym Lock Di r ector Seconds LockDev Hol der- I D I ni t i ator Number Hel d Fl ags- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -0407 0x1001100E 0 05B 13 Long0408 0x1001100E 0 05B 13 Long0409 0x1001100E 0 05B 13 Long040A 0x1001100E 0 05B 13 Long040B 0x1001100E 0 05B 13 Long040C 0x1001100E 0 05B 13 Long040D 0x1001100E 0 05B 13 Long040E 0x1001100E 0 05B 13 Long040F 0x1001100E 0 05B 13 Long0410 0x1001100E 0 05B 13 Long0411 0x1001100E 0 05B 13 Long0412 0x1001100E 0 05B 13 Long0413 0x1001100E 0 05B 13 Long0414 0x1001100E 0 05B 13 Long

0415 0x1001100E 0 05B 13 Long0416 0x1001100E 0 05B 13 Long}




4/5/2004

Remote Mi r r ors of BCV' s ( 16) :{- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -Sym Lock Di r ector Seconds LockDev Hol der- I D I ni t i ator Number Hel d Fl ags- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -0390 0x100113A3 0 14B 13 Long0391 0x100113A3 0 14B 13 Long0392 0x100113A3 0 14B 13 Long0393 0x100113A3 0 14B 13 Long0394 0x100113A3 0 14B 13 Long0395 0x100113A3 0 14B 13 Long0396 0x100113A3 0 14B 13 Long0397 0x100113A3 0 14B 13 Long0398 0x100113A3 0 14B 13 Long0399 0x100113A3 0 14B 13 Long039A 0x100113A3 0 14B 13 Long039B 0x100113A3 0 14B 13 Long039C 0x100113A3 0 14B 13 Long

039D 0x100113A3 0 14B 13 Long039E 0x100113A3 0 14B 13 Long039F 0x100113A3 0 14B 13 Long}

BRBCV Devi ces ( 16) :{- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -Sym Lock Di r ector Seconds LockDev Hol der- I D I ni t i ator Number Hel d Fl ags- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -03A0 0x100113A3 0 14B 13 Long03A1 0x100113A3 0 14B 13 Long03A2 0x100113A3 0 14B 13 Long03A3 0x100113A3 0 14B 13 Long03A4 0x100113A3 0 14B 13 Long03A5 0x100113A3 0 14B 13 Long03A6 0x100113A3 0 14B 13 Long03A7 0x100113A3 0 14B 13 Long03A8 0x100113A3 0 14B 13 Long03A9 0x100113A3 0 14B 13 Long03AA 0x100113A3 0 14B 13 Long03AB 0x100113A3 0 14B 13 Long03AC 0x100113A3 0 14B 13 Long03AD 0x100113A3 0 14B 13 Long03AE 0x100113A3 0 14B 13 Long03AF 0x100113A3 0 14B 13 Long

}




4/5/2004

Example 7: Obtaining Disk and Audit Information

This example describes some of the more relevant displays from symdi sk and symaudi t commands.

For more information about these commands, including details about other command options not shown

here, refer to EMC Solutions Enabler Symmetrix Base Management CLI Product Guide.

The symdi sk l i st command displays the configuration and status of the physical disks and theirhypervolumes within a Symmetrix unit. A disk is identified by its DA symbol (Symb), its interface (Int)

and its target ID (TID). To display verbose information about a specific disk (for example, 01A:C3) and its

hypervolumes, use symdi sk l i st –da 01A –i nt er f ace C –t i d 3 –v –hyper s.

# symdisk list

Symmet r i x I D : 000185500814Di sks Sel ect ed : 96

Capaci t y( MB)I dent Symb I nt TI D Vendor Type Hypers Tot al Fr ee- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

DA- 1A 01A C 0 SEAGATE CHET_73 17 70007 446DA- 1A 01A C 1 SEAGATE CHET_73 17 70007 446DA- 1A 01A C 2 SEAGATE CHET_73 16 70007 962DA- 1A 01A C 3 SEAGATE CHET_73 16 70007 962DA- 1A 01A C 4 SEAGATE CHET_73 15 70007 5465DA- 1A 01A C 5 SEAGATE CHET_73 19 70007 5977DA- 1A 01A D 0 SEAGATE CHET_73 17 70007 446DA- 1A 01A D 1 SEAGATE CHET_73 17 70007 446DA- 1A 01A D 2 SEAGATE CHET_73 16 70007 962DA- 1A 01A D 3 SEAGATE CHET_73 16 70007 962DA- 1A 01A D 4 SEAGATE CHET_73 17 70007 1666DA- 1A 01A D 5 SEAGATE CHET_73 16 70007 2697DA- 2A 02A C 0 SEAGATE CHET_73 17 70007 446DA- 2A 02A C 1 SEAGATE CHET_73 17 70007 446

DA- 2A 02A C 2 SEAGATE CHET_73 16 70007 962DA- 2A 02A C 3 SEAGATE CHET_73 16 70007 962DA- 2A 02A C 4 SEAGATE CHET_73 16 70007 5466DA- 2A 02A C 5 SEAGATE CHET_73 19 70007 5977DA- 2A 02A D 0 SEAGATE CHET_73 17 70007 446DA- 2A 02A D 1 SEAGATE CHET_73 16 70007 962DA- 2A 02A D 2 SEAGATE CHET_73 16 70007 962DA- 2A 02A D 3 SEAGATE CHET_73 18 70007 3612DA- 2A 02A D 4 SEAGATE CHET_73 18 70007 1667DA- 2A 02A D 5 SEAGATE CHET_73 18 70007 1667DA- 15A 15A C 0 SEAGATE CHET_73 17 70007 446DA- 15A 15A C 1 SEAGATE CHET_73 17 70007 446DA- 15A 15A C 2 SEAGATE CHET_73 16 70007 962

DA- 15A 15A C 3 SEAGATE CHET_73 16 70007 962DA- 15A 15A C 4 SEAGATE CHET_73 16 70007 5466DA- 15A 15A C 5 SEAGATE CHET_73 19 70007 1664DA- 15A 15A D 0 SEAGATE CHET_73 17 70007 446DA- 15A 15A D 1 SEAGATE CHET_73 16 70007 962DA- 15A 15A D 2 SEAGATE CHET_73 16 70007 962DA- 15A 15A D 3 SEAGATE CHET_73 16 70007 962………………………………………………………………………………………………………………………………………………………………………………




4/5/2004

The symaudi t commands retrieve information from the Symmetrix Audit Log file from data written to

the file during control operations. This information allows you to determine what application on what host

initiated actions that directed Symmetrix behavior. The symaudi t show command below displays the

time period and quantity of data in the Audit Log file that relate to local Symmetrix 814.

# symaudit show

A U D I T L O G D A T A

Symmet r i x I D : 000185500814

St ar t i ng date : 12/ 14/ 2003 14: 53: 10Endi ng dat e : 12/ 17/ 2003 14: 40: 47

St ar t i ng r ecor d number : 1Endi ng r ecor d number : 127

Tot al r ecor d count : 127

The following symaudi t l i st command displays the extracted audit log records for local Symmetrix

814 during the time period that data was collected. The ellipsis (……) indicates where some output wasomitted for brevity.

# symaudit list


Symmet r i x I D : 000185500814


Recor d Funct i on Act i onNumber Dat e Ti me Appl i cat i on Host Cl ass Code- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

1 12/ 14/ 03 14: 53: 10 SYMCLI api 179 RDF Spl i t2 12/ 14/ 03 14: 53: 10 SYMCLI api 179 RDF Spl i t3 12/ 14/ 03 14: 53: 11 SYMCLI api 179 RDF Spl i t4 12/ 14/ 03 14: 53: 16 SYMCLI api 179 RDF I ncEst a5 12/ 14/ 03 14: 53: 16 SYMCLI api 179 RDF I ncEst a6 12/ 14/ 03 14: 53: 17 SYMCLI api 179 RDF I ncEst a

……………………………………………………………………………………………………………………………………………………………………………………………………… 14 12/ 14/ 03 16: 32: 39 SYMCLI api 179 BCV Ful l Est a

15 12/ 14/ 03 16: 32: 39 SYMCLI api 179 BCV Ful l Est a16 12/ 14/ 03 16: 33: 01 SYMCLI api 179 BCV Ful l Est a17 12/ 14/ 03 16: 40: 01 SYMCLI api 179 BCV Spl i t

18 12/ 14/ 03 16: 40: 01 SYMCLI api 179 BCV Spl i t19 12/ 14/ 03 16: 40: 01 SYMCLI api 179 BCV Spl i t

……………………………………………………………………………………………………………………………………………………………………………………………………… 109 12/ 17/ 03 14: 39: 05 SYMCLI api 179 BCV Spl i t

110 12/ 17/ 03 14: 39: 07 SYMCLI api 179 RDF I ncEst a111 12/ 17/ 03 14: 39: 07 SYMCLI api 179 RDF I ncEst a112 12/ 17/ 03 14: 39: 08 SYMCLI api 179 RDF I ncEst a113 12/ 17/ 03 14: 39: 10 SYMCLI api 179 BCV I ncEst a114 12/ 17/ 03 14: 39: 10 SYMCLI api 179 BCV I ncEst a115 12/ 17/ 03 14: 39: 10 SYMCLI api 179 BCV I ncEst a




4/5/2004

116 12/ 17/ 03 14: 39: 10 SYMCLI api 179 BCV I ncEst a117 12/ 17/ 03 14: 39: 24 SYMCLI api 179 BCV I ncEst a118 12/ 17/ 03 14: 39: 24 SYMCLI api 179 BCV I ncEst a119 12/ 17/ 03 14: 39: 24 SYMCLI api 179 BCV I ncEst a120 12/ 17/ 03 14: 39: 24 SYMCLI api 179 BCV I ncEst a121 12/ 17/ 03 14: 39: 24 SYMCLI api 179 BCV I ncEst a122 12/ 17/ 03 14: 39: 42 SYMCLI api 179 BCV I ncEst a123 12/ 17/ 03 14: 40: 44 SYMCLI api 179 BCV Spl i t124 12/ 17/ 03 14: 40: 44 SYMCLI api 179 BCV Spl i t125 12/ 17/ 03 14: 40: 44 SYMCLI api 179 BCV Spl i t126 12/ 17/ 03 14: 40: 44 SYMCLI api 179 BCV Spl i t127 12/ 17/ 03 14: 40: 46 SYMCLI api 179 BCV Spl i t

Using the –t ext option with the symaudi t l i st command displays the text associated with the

audit log record.

# symaudit list -text


Symmet r i x I D : 000185500814

St art i ng date : 12/ 14/ 2003 14: 53: 10Endi ng dat e : 12/ 17/ 2003 14: 40: 47

Recor d Ti me Funct i on Act i onNumber Cl ass Code- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Text- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

1 14: 53: 10 RDF Spl i tSTARTI NG an RDF ' SPLI T' . t ype: Regul ar [ RDF1 BCV] , f l ags:

2 14: 53: 10 RDF Spl i t[ 0407-0416 ]

3 14: 53: 11 RDF Spl i t The RDF ' SPLI T' oper at i on SUCCEEDED.

4 14: 53: 16 RDF I ncEst aSTARTI NG an RDF ' I NCREMENTAL ESTABLI SH' . t ype: Regul ar [ RDF1 BCV] , f l ags:

5 14: 53: 16 RDF I ncEst a[ 0407-0416 ]

6 14: 53: 17 RDF I ncEst a The RDF ' I NCREMENTAL ESTABLI SH' oper at i on SUCCEEDED.

……………………………………………………………………………………………………………………………………………………………………………………………………… 14 16: 32: 39 BCV Ful l Est a

STARTI NG a l ocal ' BCV Ful l Est abl i sh' operat i on f or 1 [ STD- BCV] Pai r :

15 16: 32: 39 BCV Ful l Est a[ 0000-0190 ]

16 16: 33: 01 BCV Ful l Est a' BCV Ful l Establ i sh' . st s: SYMAPI _C_SUCCESS

17 16: 40: 01 BCV Spl i tSTARTI NG a l ocal ' BCV Spl i t ' operat i on f or 1 [ STD- BCV] Pai r :

18 16: 40: 01 BCV Spl i t[ 0000-0190 ]




4/5/2004

19 16: 40: 01 BCV Spl i t' BCV Spl i t ' . st s: SYMAPI _C_SUCCESS

……………………………………………………………………………………………………………………………………………………………………………………………………… 109 14: 39: 05 BCV Spl i t

' BCV Spl i t ' . st s: SYMAPI _C_SUCCESS

110 14: 39: 07 RDF I ncEst aSTARTI NG an RDF ' I NCREMENTAL ESTABLI SH' . t ype: Regul ar [ RDF1 BCV] , f l ags:

111 14: 39: 07 RDF I ncEst a[ 0407-0416 ]

112 14: 39: 08 RDF I ncEst a The RDF ' I NCREMENTAL ESTABLI SH' oper at i on SUCCEEDED.

113 14: 39: 10 BCV I ncEst aSTARTI NG a l ocal ' BCV I nc Est abl i sh' oper ati on f or 16 [ STD- BCV] Pai r s:

114 14: 39: 10 BCV I ncEst a[ 03F7-0407 03F8- 0408 03F9- 0409 03FA- 040A 03FB- 040B 03FC- 040C

115 14: 39: 10 BCV I ncEst a03FD- 040D 03FE- 040E 03FF- 040F 0400- 0410 0401- 0411 0402- 0412

116 14: 39: 10 BCV I ncEst a0403- 0413 0406- 0416 0404- 0415 0405- 0414 ]

117 14: 39: 24 BCV I ncEst a' BCV I nc Establ i sh' . st s: SYMAPI _C_SUCCESS

118 14: 39: 24 BCV I ncEst aSTARTI NG a remote ' BCV I nc Est abl i sh' operat i on f or 16 [ STD- BCV] Pai r s:

119 14: 39: 24 BCV I ncEst a[ 0390- 03A0 0391- 03A1 0392- 03A2 0393- 03A3 0394- 03A4 0395- 03A5

120 14: 39: 24 BCV I ncEst a0396- 03A6 0397- 03A7 0398- 03A8 0399- 03A9 039A- 03AA 039B- 03AB

121 14: 39: 24 BCV I ncEst a039C- 03AC 039F- 03AF 039E- 03AE 039D- 03AD ]

122 14: 39: 42 BCV I ncEst a' BCV I nc Establ i sh' . st s: SYMAPI _C_SUCCESS

123 14: 40: 44 BCV Spl i tSTARTI NG a remote ' BCV Spl i t ' operat i on f or 16 [ STD- BCV] Pai r s:

124 14: 40: 44 BCV Spl i t[ 0390- 03A0 0391- 03A1 0392- 03A2 0393- 03A3 0394- 03A4 0395- 03A5

125 14: 40: 44 BCV Spl i t0396- 03A6 0397- 03A7 0398- 03A8 0399- 03A9 039A- 03AA 039B- 03AB

126 14: 40: 44 BCV Spl i t039C- 03AC 039F- 03AF 039E- 03AE 039D- 03AD ]

127 14: 40: 46 BCV Spl i t' BCV Spl i t ' . st s: SYMAPI _C_SUCCESS




4/5/2004

The following symaudi t l i st command displays detailed information about record number 124

during a TimeFinder split operation (that is, the BCV is being split from its paired standard device). The

“Text” line displays which BCV pairs are being split (for example, device 390 from device 3A0).

# symaudit -v list -record_num 124


Symmet r i x I D : 000185500814


Recor d Number : 124Recor ds i n Seq : 4Of f set i n Seq : 2

Ti me : 12/ 17/ 03 14: 40: 44Vendor I D : EMC Cor pAppl i cat i on I D : SYMCLI

Appl i cat i on Ver si on : 5. 4. 0. 0API Li br ar y : SEKAPI Ver si on : T5. 4. 0. 0 ( Edi t Level : 236)Host Name : api 179OS Name : SunOSOS Revi si on : 5. 8Generi cCl i ent Host :Process I D : 00006670

Task I D : 00000000Funct i on Cl ass : BCVAct i on Code : Spl i t

Text : [ 0390- 03A0 0391- 03A1 0392- 03A2 0393- 03A3 0394- 03A4 0395- 03A5




4/5/2004

Example 8: Obtaining Display Output in XML Format

You can specify an XML output mode for SYMCLI utilities outputs using an environment variable setting

or the –out xml option on the command line. Valid modes are “Standard” or “XML.” The example uses

the symcf g l i st command to illustrate output.

By default, the symcf g l i st command produces a standard mode output display as shown below.

# symcfg list

S Y M M E T R I X


000185500814 Local 8230 5568 4096 757 1097000185500505 Remot e 8230 5568 8192 0 970

The expor t command sets the SYMCLI _OUTPUT_MODE variable to “XML”.

# export SYMCLI_OUTPUT_MODE=xml

The symcf g l i st command now produces the same output in XML format.

# symcfg list

<?xml ver si on="1. 0" st andal one="yes" ?>

<SymCLI _ML><Symmet r i x i d="000185500814" at t achment="Local " model ="8230"

mi cr ocode_ver si on="5568" cache_megabyt es="4096"physi cal _devi ces="757"

devi ces="1097" / >

<Symmet r i x i d="000185500505" at t achment ="Remot e" model ="8230"mi cr ocode_versi on="5568" cache_megabyt es="8192" physi cal _devi ces="0"devi ces="970"/ >

</ SymCLI _ML>

The unset command terminates the previous setting for SYMCLI _OUTPUT_MODE. In effect, this

operation returns the mode setting to standard mode.

# unset SYMCLI_OUTPUT_MODE




4/5/2004

By default, the symcf g l i st command should now produce its output in standard mode. However, the

following command includes the –out XML option to again display output in XML format rather than

standard format.

# symcfg list -out xml

<?xml ver si on="1. 0" st andal one="yes" ?>

<SymCLI _ML><Symmet r i x i d="000185500814" at t achment="Local " model ="8230"

mi cr ocode_ver si on="5568" cache_megabyt es="4096"physi cal _devi ces="757"

devi ces="1097" / ><Symmet r i x i d="000185500505" at t achment ="Remot e" model ="8230"

mi cr ocode_versi on="5568" cache_megabyt es="8192" physi cal _devi ces="0"devi ces="970"/ >

</ SymCLI _ML>




4/5/2004

Example 9: Obtaining Status Information about GNS

Group Name Services (GNS) propagates SYMAPI device group and composite group definitions across

multiple hosts and Symmetrix units. GNS stores device group and composite group definitions in a sharedrepository that is accessible from multiple hosts. Thus, you can perform SYMCLI and SYMAPI control

operations from any host in the Symmetrix environment. If you make a change to a group definition on one

host, that change is visible to other hosts.

The st ordaemon l i st command displays whether the GNS and watchdog daemons are running on

your host.

# stordaemon list

Avai l abl e Daemons ( ' [ *] ' : Cur r ent l y Runni ng) :

st or api d EMC Sol ut i ons Enabl er Base Daemon[ *] st or gnsd EMC Sol ut i ons Enabl er GNS Daemon[ *] st or wat chd EMC Sol ut i ons Enabl er Wat chdog Daemon

st oror ad EMC Sol ut i ons Enabl er SRM Or acl e Daemonst or udbd EMC Sol ut i ons Enabl er SRM UDB Daemonst or i f mxd EMC Sol ut i ons Enabl er SRM I nf ormi x Daemonst or sybs11d EMC Sol ut i ons Enabl er SRM Sybase 11 Daemonst or sybs12d EMC Sol ut i ons Enabl er SRM Sybase 12 Daemonst or sybs12. 5d EMC Sol ut i ons Enabl er SRM Sybase 12. 5 Daemonst or sybs12. 5_64d EMC Sol ut i ons Enabl er SRM Sybase 12. 5 Daemon, 64- bi t

The symdg l i st command with the – i nact i ve option displays device groups that exist currently in

your host’s SYMAPI database. From the GNS-enabled viewpoint, these are inactive device groups.

# symdg list -inactive

I N A C T I V E D E V I C E G R O U P S

Number ofName Type Val i d Symmet r i x I D Devs GKs BCVs VDEVs

79api 179r egul ar REGULAR N/ A 000187700079 23 0 3 035api 179r egul ar REGULAR N/ A 000187900035 22 0 44 0

The symdg act i vat eal l command imports all device groups from your host’s SYMAPI database

into GNS. From the GNS-enabled viewpoint, these are now active device groups

# symdg activateall –noprompt

Act i vat i ng Devi ce Gr oup: ' 79api 179r egul ar ' . . . Succeeded.Act i vat i ng Devi ce Gr oup: ' 35api 179r egul ar ' . . . Succeeded.




4/5/2004

If GNS is enabled on your host, the symdg l i st command displays device groups that are active from

the GNS-enabled viewpoint.

# symdg list

D E V I C E G R O U P S

Number ofName Type Val i d Symmet r i x I D Devs GKs BCVs VDEVs

79api 179r egul ar REGULAR Yes 000187700079 23 0 3 035api 179r egul ar REGULAR Yes 000187900035 22 0 44 0

Documents

Symmetrix Configuration.pdf