using symcli to clean config information

Using SYMCLI to Obtain SymmetrixConfiguration Information

Date 3/11/2002

Engineering White Paper

DATE: 03/11/02

Using SYMCLI to Obtain Symmetrix Configuration Information 1

Copyright 2002 EMC Corporation. All rights reserved.

EMC believes the information in this publication is accurate as of its publication date. The information issubject to change without notice.THE INFORMATION IN THIS PUBLICATION IS PROVIDED AS IS. EMC CORPORATIONMAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THEINFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIEDWARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Use, copying, and distribution of any EMC software described in this publication requires an applicablesoftware license.

EMC, EMC2, and Symmetrix are registered trademarks and Enginuity, PowerPath, SRDF, TimeFinder, andwhere information lives are trademarks of EMC Corporation.

All other brand names are trademarks or registered trademarks of their respective owners.

Part Number H606.1Printed 3/11/2002

DATE: 03/11/02


Table of Contents

Introduction .........................................................................................................3Purpose and Scope................................................................................................................. 3Related Documentation........................................................................................................... 3

Practical Uses......................................................................................................3

Displaying Information about a Symmetrix Unit...............................................4

Displaying Information about Symmetrix Devices ...........................................7

Displaying Information about SRDF Devices .................................................14

Displaying Information about BCV Devices....................................................16

Displaying Information about a Device Group................................................18

Example 1: Verifying that Configuration Information in the SYMAPIDatabase Shows the Current Configuration ...................................................24

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

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

Example 4: Obtaining Information about Dynamic SRDF Devices ..............33

Example 5: Obtaining More Device Group Information ................................34

Example 6: Obtaining Disk and Audit Information........................................40

Example 7: Obtaining Display Output in XML Format ..................................45

DATE: 03/11/02


IntroductionEMC Solutions Enabler (SYMCLI) maintains configuration and status information about every deviceinside the Symmetrix units that are accessible from your host. This information is stored in a SYMAPIdatabase file that resides on the host. You can use SYMCLI commands to display in standard or XMLformat 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 that represents a collection of devices

Purpose and ScopeThis paper describes using SYMCLI commands to obtain Symmetrix configuration and status information.Its focus is on information that will help you perform SRDF and TimeFinder control operations. Standarddisplays were obtained while the Symmetrix units were running either Enginuity version 5567 or 5568.Most information described here is supported by and is applicable to versions 5x63 to 5x68.

Related DocumentationThe following manuals and white papers provide information related to the concepts in this paper:

EMC Solutions Enabler SYMCLI Base Component Product Guide (P/N 300-000-434) EMC Solutions Enabler SYMCLI SRDF Component Product Guide (P/N 300-000-444) EMC Solutions Enabler SYMCLI TimeFinder Component Product Guide (P/N 300-000-443) Using SYMCLI to Perform SRDF Control Operations (P/N 300-000-076) Using SYMCLI to Set Up TimeFinder BCV Pairs (P/N 300-000-072) Using SYMCLI to Set Up TimeFinder Multiple BCVs and Concurrent BCVs (P/N 300-000-073) Using SYMCLI to Perform TimeFinder Control Operations (P/N 300-000-074)

Practical UsesExamining 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 aSymmetrix ID (sid). A listing of Symmetrix units accessible to your host provides the sid for eachSymmetrix 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 devicesor TimeFinder BCV devices on that Symmetrix unit.

Beginning with SYMCLI version 5.0 (and any Enguinity level supported by SYMAPI), you can use asymdisk list command to display the configuration and status of the physical disks and their hyperswithin a Symmetrix unit. Beginning with Enginuity version 5x68 and higher, you can use a symauditlist command to retrieve information from the Symmetrix Audit Log file from data written to the fileduring control operations. This audit information allows you to determine what application on what hostinitiated actions that directed Symmetrix behavior.

DATE: 03/11/02


With SYMCLI version 4.3.1 and higher, you can set an environment variable or include the out XMLoption on a command line to produce display output in XML format rather than standard format.

Your hosts SYMAPI database file stores information about the device group and the standard devices andBCVs included in it. But information about BCV pairs is also stored in the Symmetrix units global memory,meaning that the Symmetrix remembers previous device pairing relationships that may no longer beactive. Consequently, a BCV or standard device that you add to your device group may have an existingpairing relationship with a device that does not belong to your device group. Thus, to avoid any confusionwhen trying to create new BCV pairs from devices that you added to your device group, EMC recommendsthat you examine device status information first.

Displaying Information about a Symmetrix UnitWhenever a Symmetrix configuration is new or has changed, you need to ensure which Symmetrix units areconnected to your host and that the information about these Symmetrix units is current. You can use thesymcfg verify command to determine if the Symmetrix configuration and the SYMAPI database fileare in sync. If they are out of sync, the verify action returns code 24 (CLI_C_NOT_IN_SYNC). If they arenot in sync, you should run either a discover operation or a full sync (see Example 1: Verifying ThatConfiguration Information in the SYMAPI Database Shows the Current Configuration).

You can use the symcfg discover command to rebuild your hosts SYMAPI database file with themost current information about the physical devices directly connected to your host. The command scans allbuses, collects information about all the devices found, and rebuilds the database with collected informationfrom all locally and remotely attached Symmetrix devices. If you have disconnected a Symmetrix unit fromthe configuration since the last discover process, a subsequent symcfg discover does notautomatically remove outdated Symmetrix information from the database file unless you first set theenvironment variable SYMCLI_REMOVE_SYMS to a value of 1. (You can also use the symcfg removecommand 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 symcfg list command from the host. For example:

symcfg list

S Y M M E T R I X

Mcode Cache Num Phys Num SymmSymmID Attachment Model Version Size (MB) Devices Devices

000184501161 Local 8430 5567 16384 545 967000185500505 Remote 8430 5567 8192 0 912

The display shows the configuration from the local hosts 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 tothe 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 161 is connected to remote Symmetrix 505. Both Symmetrix unitsare running Enginuity version 5567.

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 hostand/or have a physical host device name. The local host has access (read/write capability) to 545 physicaldevices on the local Symmetrix unit. The local host (or point-of-view host in this case) cannot accessdevices on the remote Symmetrix, which accounts for the zero value under Num Phys Devices.

If you issue the symcfg list command from a host connected to Symmetrix 505, then this Symmetrixunit is displayed as the Local Symmetrix, and Symmetrix 161 is the Remote unit.

DATE: 03/11/02


You can add the verbose option (-v) to the symcfg list command to obtain detailed information aboutSymmetrix units, such as whether the concurrent RDF and dynamic RDF states are enabled. You can displaydetails of all Symmetrix units in the configuration or a specific Symmetrix by including its sid on thecommand line. For example, to display the details of Symmetrix 233:

symcfg list sid 233 -v

Product Model : 8130Symmetrix ID : 000000005233

Microcode Version (Number) : 5567 (15BFAA01)Microcode Date : 11.12.2001

Microcode Patch Date : 11.12.2001Microcode Patch Level : 37

Cache Size : 4096 (MB)# of Available Cache Slots : 113821# of PermaCache Slots In Use : 20426Max # of System Write Pending Slots : 91145Max # of DA Write Pending Slots : 45572Max # of Device Write Pending Slots : 11110

Symmetrix Total Operating Time : 70 days, 03:34:44Symmetrix Power ON Time : Fri Sep 21 09:17:04 2001Symmetrix Last IPL Time (Cold) : Mon Nov 19 11:04:20 2001Symmetrix Last Fast IPL Time (Hot) : Mon Nov 19 11:04:20 2001

Host DB Sync Time : Fri Nov 30 09:32:35 2001Symmetrix CLI (SYMCLI) Version : V4.3.1.0 (Edit Level: 173)Built with SYMAPI Version : V4.3.1.0 (Edit Level: 173)SYMAPI Run Time Version : V4.3.1.0 (Edit Level: 173)

Number of Configured (Sym) Devices : 90Number of Visible (Host) Devices : 86Number of Configured Actual Disks : 32

Number of Powerpath Devices : 40Powerpath Run Time Version : 2.1.0

SDDF Configuration State : EnabledConfiguration Change State : EnabledWORM Configuration Level : N/ASymmetrix Configuration Checksum : 438DASwitched RDF Configuration State : DisabledConcurrent RDF Configuration State : DisabledDynamic RDF Configuration State : DisabledRDF Data Mobility Configuration State: Disabled

Devices that are configured as PowerPath-connected devices provide support for controlling SRDFconsistency groups and for performing TimeFinder consistent split operations. This Symmetrix displayshows 40 PowerPath configured devices running PowerPath software version 2.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 (WriteOnce Read Many) configuration level is not enabled (N/A) for this Symmetrix unit. The SymmetrixConfiguration Checksum (438DA) indicates the initial microcode program load for this configuration. You

DATE: 03/11/02


can use the symcfg verify command to determine if the Symmetrix configuration has changedcompared to the SYMAPI database.

The last four configuration states in the display are all disabled. Switched RDF involves non-blockingswitching devices that interconnect two or more nodes, allowing a Symmetrix port pair to run full-duplex.For information about Concurrent RDF, Dynamic RDF, and RDF Data Mobility, refer to the white paperUsing SYMCLI to Perform SRDF Control Operations (P/N 300-000-076).Another useful SYMCLI command to examine Symmetrix connections is symcfg list ra all.This command reaches all Symmetrix units that are accessible through RDF links one or two hops away anddisplays 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 notconnected to each other. Figure 1 illustrates this Symmetrix configuration.

symcfg list -ra all

Symmetrix ID: 000000003264 (Local)

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

Remote Local RemoteIdent Symbolic Numeric Slot Type SymmID RA Grp RA Grp Status

RA-3A 03A 3 3 RDF-BI-DIR 000000003265 2 (B) 2 (B) OnlineRA-3B 03B 19 3 RDF-BI-DIR 000000003265 2 (B) 2 (B) Online

Symmetrix ID: 000000003263 (Remote)



RA-3A 03A 3 3 RDF-BI-DIR 000000003265 1 (A) 1 (A) OnlineRA-3B 03B 19 3 RDF-BI-DIR 000000003265 1 (A) 1 (A) Online

Symmetrix ID: 000000003265 (Remote)



RA-3A 03A 3 3 RDF-BI-DIR 000000003263 1 (A) 1 (A) OnlineRA-14A 14A 14 14 RDF-BI-DIR 000000003264 2 (B) 2 (B) OnlineRA-3B 03B 19 3 RDF-BI-DIR 000000003263 1 (A) 1 (A) OnlineRA-14B 14B 30 14 RDF-BI-DIR 000000003264 2 (B) 2 (B) Online

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 and3265. RA group 1 forms the link between Symmetrix units 3265 and 3263.

DATE: 03/11/02


R2

Host

Local Symmetrix3264

Remote Symmetrix3265

R2

Remote Symmetrix3263

CLI-000019

RA Group 2

RA Group 1

R1

R1BCV

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

Other useful options with the symcfg list command are included in Table 1. For a complete list ofoptions, refer to EMC Solutions Enabler SYMCLI Base Component Product Guide (P/N 300-000-434).

Table 1. Useful Options with the symcfg list Command

Option Display-applications sid # Symmetrix-registered applications that have accessed a certain Symmetrix.-connections sid # All hosts that have accessed a certain Symmetrix.-services Network services in the client/SYMAPI server connection.-dir all Configuration and status information about all directors in a Symmetrix unit.-sa all Configuration of all front-end directors (SA and FA) in a Symmetrix unit.-lock Symmetrix units that have a Symmetrix external lock.

Displaying Information about Symmetrix DevicesSYMCLI provides two commands to list the devices on a Symmetrix unitone that displays all devices, andone that displays only host-visible devices (devices that are mapped to the host or have a physical hostdevice name, or both). The symdev list command lists all devices in a Symmetrix unit.

The sympd list 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 list output below displays devices on the local Symmetrix unit by default. Todisplay devices on a remote Symmetrix unit, include the sid option with the identifier of the remoteSymmetrix unit. The ellipsis () indicates where output was omitted. The first column contains a devicesSymmetrix device name (the hexadecimal number that the Symmetrix assigns to each physical device), andthe second column contains its physical device name (host name) if the device is visible to the host.

DATE: 03/11/02


symdev list

Symmetrix ID: 000000003264

Device Name Directors Device--------------------------- ------------ --------------------------------------

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

000 Not Visible 16A:0 01A:C0 Unprotected N/Grp'd (M) RW 1031001 Not Visible 16A:0 02B:D3 Unprotected N/Grp'd (M) RW 1031002 Not Visible ???:? 02A:C0 Unprotected N/Grp'd RW 516003 Not Visible 16A:0 01B:D3 Unprotected N/Grp'd (m) RW -004 Not Visible 16A:0 01B:C0 Unprotected N/Grp'd (m) RW -005 Not Visible ???:? 02A:D3 Unprotected N/Grp'd RW 516

084 /dev/rdsk/c4t0d0s2 16B:0 01A:C0 2-Way Mir N/Grp'd RW 516085 /dev/rdsk/c4t0d1s2 16B:0 02A:C0 2-Way Mir N/Grp'd RW 516086 /dev/rdsk/c4t0d2s2 16B:0 01B:C0 2-Way Mir N/Grp'd RW 516087 /dev/rdsk/c4t0d3s2 16B:0 02B:C0 2-Way Mir N/Grp'd RW 516088 /dev/rdsk/c4t1d0s2 16B:0 01A:D0 2-Way BCV Mir N/Asst'd RW 516089 /dev/rdsk/c4t1d1s2 16B:0 02A:D0 2-Way BCV Mir N/Asst'd RW 51608A /dev/rdsk/c4t1d2s2 16B:0 01B:D0 2-Way BCV Mir N/Asst'd RW 51608B /dev/rdsk/c4t1d3s2 16B:0 02B:D0 2-Way BCV Mir N/Asst'd RW 516

Director information includes the SA front-end director (SCSI adapter) number and port that connects thedevice to the host, as well as the DA disk director number and interface that transfers data from the device tocache. Question marks (???:?) in the SA:P column indicate that this device is not mapped to a front-endadapter port, or is mapped to multiple ports with no clearly distinguishable primary path.

Device information includes a devices configuration, whether it currently belongs to a device group(N/Grpd or N/Asstd means it does not), its status (read/write or otherwise), and its storage capacity inmegabytes. A meta head (M), the first device in a meta device, and a meta member (m) are displayed withthese letter notations.

Useful options with the symdev list command include multiport and firstport, whichdisplay devices mapped to multiple front-end adapter ports or to just the first port of information for devicesmapped to more than one port, respectively. Refer to Example 3: Obtaining More Device Information fordisplays using these options.

The partial sympd list output below displays the same information as the symdev list output butonly 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 devicesfrom the previous symdev list display are omitted from this display. N/Grpd means that a standarddevice does not currently belong to a device group. N/Asstd means that a BCV does not belong to (is notassociated with) a device group.sympd list



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

/dev/rdsk/c4t0d0s2 084 16B:0 01A:C0 2-Way Mir N/Grp'd RW 516/dev/rdsk/c4t0d1s2 085 16B:0 02A:C0 2-Way Mir N/Grp'd RW 516/dev/rdsk/c4t0d2s2 086 16B:0 01B:C0 2-Way Mir N/Grp'd RW 516

DATE: 03/11/02


/dev/rdsk/c4t0d3s2 087 16B:0 02B:C0 2-Way Mir N/Grp'd RW 516/dev/rdsk/c4t1d0s2 088 16B:0 01A:D0 2-Way BCV Mir N/Asst'd RW 516/dev/rdsk/c4t1d1s2 089 16B:0 02A:D0 2-Way BCV Mir N/Asst'd RW 516/dev/rdsk/c4t1d2s2 08A 16B:0 01B:D0 2-Way BCV Mir N/Asst'd RW 516/dev/rdsk/c4t1d3s2 08B 16B:0 02B:D0 2-Way BCV Mir N/Asst'd RW 516

You can use options with the sympd list command to display only devices of specific interest. Forexample, use the -powerpath option to display only the PowerPath devices in a Symmetrix unit.

sympd list -powerpath


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

Device Name Directors Device---------------------------- ------------ -------------------------------------

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

/dev/rdsk/emcpower0c 041C 02A:D3 Unprotected N/Grp'd RW 5754/dev/vx/rdmp/c4t0d114s2 - 12B:0 - - - - -/dev/rdsk/c4t0d114s2 - 05B:0 - - - - -/dev/rdsk/c5t0d114s2 - 12B:0 - - - - -

/dev/rdsk/emcpower1c 041D 15B:D3 Unprotected Grp'd RW 8632/dev/vx/rdmp/c4t0d115s2 - 12B:0 - - - - -/dev/rdsk/c4t0d115s2 - 05B:0 - - - - -/dev/rdsk/c5t0d115s2 - 12B:0 - - - - -

Each PowerPath device in this display is configured to have multiple physical device names and SA (SCSIadapter) connections that provide alternate paths for load-balancing and failover capabilities. The physicaldevice names all represent the same PowerPath device (for example, four physical device names representthe PowerPath device 041C). The emcpower name is a PowerPath pseudo name; some operating systemsdisplay this name, some do not. Depending on the circumstances, PowerPath determines which path to use.

When determining SRDF devices or BCV devices or both to add to a device group, you can list devices thathave the same type of configuration. Table 2 lists some common options. For a complete list of options,refer to EMC Solutions Enabler SYMCLI Base Component Product Guide (P/N 300-000-434).

Table 2. Useful Options with the symdev list Commands

Option Display-r1 All RDF1 type (R1) devices.-bcv All BCV devices.-drv All DRV devices.-meta All meta devices.-hotspare 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).-sid # -bcv All BCV devices on the Symmetrix identified by its sid number, which is useful for

listing BCVs on a remote Symmetrix while issuing commands from the local host.-nobcv All standard devices.

DATE: 03/11/02


Option Display-range 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).-dynamic Displays devices that are configured as capable of being either dynamic R1 or R2

devices1. When combined with the r1 option, the display is limited to devicesconfigured as capable of being only dynamic R1 devices. When combined with ther2 option, the display shows devices capable of being only dynamic R2 devices.

Because the primary purpose of RDF BCV devices is to mirror data from a local Symmetrix on a targetSymmetrix, these BCV devices are usually configured to be not accessible (not visible) to the local host forread/write access. The following display shows R1 BCV devices that, in this instance, happen to be NotVisible to this host. N/Asstd means the devices are not associated with any existing device group.

symdev list -r1 -bcv




2E0 Not Visible ???:? 15A:D5 RDF1-BCV N/Asst'd RW 43152E1 Not Visible ???:? 02A:C5 RDF1-BCV N/Asst'd RW 43152E2 Not Visible ???:? 02A:D5 RDF1-BCV N/Asst'd RW 4315

The following symdev list command invoked from the local host displays BCVs on remoteSymmetrix 505. These remote devices are Not Visible to (not accessible for I/O by) the local host.However, if you were to invoke the same command from a remote host connected to Symmetrix 505, theviewpoint and display would change. From the remote hosts viewpoint, these devices are visible.

symdev list sid 505 -bcv




2E0 Not Visible ???:? 16B:D5 BCV N/Asst'd RW 43152E1 Not Visible ???:? 15B:D5 BCV N/Asst'd RW 43152E2 Not Visible ???:? 02B:D5 BCV N/Asst'd RW 4315

For detailed configuration information about a specific device, use the sympd show PdevNamecommand or symdev show SymDevName. The following symdev show command displays thedetails of BCV 0064, which is an R1 BCV that belongs to a device group named sar. It acquired the logical

1 With Enginuity version 5567, SRDF devices are configured for dynamic R1/R2 swap (fast swap) when a Symmetrix unit isconfigured. With Enginuity version 5568 and the introduction of full-fledged dynamic RDF, non-SRDF devices are configured suchthat they can become dynamic SRDF pairs when you use the symrdf createpair command.

DATE: 03/11/02


device name BCV001 by default when it was associated with this device group. Figure 2 at the end of thisdisplay illustrates the configuration in which this device participates.

symdev show 0064


Device Physical Name : Not Visible

Device Symmetrix Name : 0064Device Serial ID : N/ASymmetrix ID : 000185500814

Device Group Name : sarDevice Logical Name : BCV001

Vendor ID : EMCProduct ID : SYMMETRIXProduct Revision : 5568

Device Emulation Type : FBADevice Defined Label Type: N/ADevice Defined Label : N/ADevice Sub System Id : 0x0140

Device Block Size : 512

Device Capacity{Cylinders : 9206Tracks : 138090512-byte Blocks : 8837760MegaBytes : 4315KiloBytes : 4418880}

Device Configuration : RDF1-BCV

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

The Service State: Normal is a setting that relates to mirrors. If the configuration is SRDF and partitioned,the service state for SRDF is Degraded. If the configuration is TimeFinder and the DA is write-disable, theservice state is Degraded; if the DA is Not Ready, the service state is Failed.

Device Service State : 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).

Device Status : 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.

Device SA Status : N/A (N/A)

DATE: 03/11/02


Mirror Set Type : [Data,R2 Remote,N/A,N/A]

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

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

The next section displays Disk Director information related to Symmetrix device 0064. The Hyper Statusof Not Ready means that the part of the physical disk to which BCV 0064 is mapped is not currentlyaccessible for reads or writes by its host. Either the BCV device is established (which is the case here) or itis in trouble (Not Ready) on the DA.

Back End Disk Director Information{Hyper Type : DataHyper Status : Not Ready (NR)Disk [Director, Interface, TID] : [16A, C, 1]Disk Director Volume Number : 25Hyper Number : 8Disk Capacity : 70007m

Hyper Type : R2 RemoteHyper Status : Not Ready (NR)Disk [Director, Interface, TID] : [N/A,N/A,N/A]Disk Director Volume Number : N/AHyper Number : N/A}

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

BCV Pair Information{Standard (STD) Device Symmetrix Name : 0000Standard (STD) Device Serial ID : 14000000Standard (STD) Device Group Name : sar

BCV Device Symmetrix Name : 0064BCV Device Serial ID : Not VisibleBCV Device Associated Group Name : sar

The BCV Device Status: Not Ready means that currently there is no read/write access to the BCV by itshost. State of Pair indicates that the BCV pair is currently in the Synchronized state.

BCV Device Status : Not Ready (NR BCV)

State of Pair ( STD ====> BCV ) : SynchronizedTime of Last BCV Action : Fri Oct 12 13:42:05 2001

The BCV State Flags: (inc) means that, on the next split operation, data from the BCVs moving mirrorwill be incrementally copied to its fixed mirror. Ordinarily, this setting is displayed on a full establish.

BCV State Flags : (inc)

Number of Inv. Tracks for STD Device : 0Number of Inv. Tracks for BCV Device : 0}

The RDF Information section of this display shows that BCV 0064 is also configured as an SRDF pair witha remote R2 device (0218) on the remote Symmetrix (sid 505).

DATE: 03/11/02


RDF Information{Device Symmetrix Name : 0064RDF Type : R1RDF (RA) Group Number : 2 (B)

Remote Device Symmetrix Name : 0218Remote Symmetrix ID : 000185500505

RDF Mode : SynchronousRDF Adaptive Copy : DisabledRDF Adaptive Copy Write Pending State : N/ARDF Adaptive Copy Skew (Tracks) : 65535

RDF Device Domino : Disabled

RDF Link Configuration : Direct Escon FibreRDF Link Domino : DisabledPrevent Automatic RDF Link Recovery : DisabledPrevent RAs Online Upon Power ON : Enabled

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 RAStatus: Ready means that the RA is ready for read/write activity. Device Link Status: Not Ready meansthat the R1 devices RDF link to the remote R2 device is currently suspended.

Device RDF Status : Ready (RW)

Device SA Status : N/A (N/A)Device RA Status : Ready (RW)Device Link Status : Not Ready (NR)

Device Suspend State: N/A means that the device does not belong to an enabled consistency group or thatit does but is synchronized and does not have an R1 suspend state. If the device is part of a trippedconsistency 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.

Device Suspend State : N/ADevice Consistency State : Disabled

RDF Pair State indicates that the SRDF pair is currently in the Suspended state, as you would expect whenan R1 BCV is synchronized locally as a BCV pair. (Establishing an R1 BCV in a local BCV pairingrelationship automatically suspends the R1 BCVs RDF link to its paired R2 device.) Device RDF State:Not Ready is a composite setting that means the R1 device (0064) is not currently accessible for copyingdata to its R2 device. Remote Device RDF State means that the remote R2 device (0218) is write disabledto its host.

Device RDF State : Not Ready (NR)Remote Device RDF State : Write Disabled (WD)

RDF Pair State ( R1 R2 ) : Suspended

The resolution of invalid tracks depends on which operation you perform. For instance, you can have remoteinvalids on both the R1 and R2 sides prior to an establish or a restore operation. If so, performing anestablish 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.

DATE: 03/11/02


Number of R1 Invalid Tracks : 0Number of R2 Invalid Tracks : 0}

Figure 2 shows that BCV 0064 (the device previously displayed) is paired with local standard device 0000as a BCV pair and with standard device 0218 as an SRDF pair. At the time of the show display, BCV 0064was synchronized with standard 0000 and suspended from standard 0218.

Standard

Source(R1)

RDF BCV

Target(R2)

Standard

Host

Local Symmetrix814

Remote Symmetrix505

SRDFPair

BCV Pair

0000

0064 0218

CLI-000017

Figure 2. Symmetrix Configuration for the symdev show 0064 Command

Displaying Information about SRDF DevicesIn an SRDF configuration, you can examine the devices on your local Symmetrix to determine which aresource devices (Sym Dev), which are remote target devices (RDev), and whether a device is an R1 or R2type device. The symrdf list command displays this information as well as other relevant data such asRDF group (G), mode of operation, pair state, invalid tracks, and the state of each device and the RDF linksthat connect them.

symrdf list


Local Device View-------------------------------------------------------------------------------

STATUS M O D E S RDF S T A T E SSym RDF --------- ------------ R1 Inv R2 Inv -----------------------Dev RDev Typ:G SA RA LNK Mode Dom ACp Tracks Tracks Dev RDev Pair--- ---- ----- --------- ------------ ------ ------ --- ---- --------------

045 045 R2:2 RW WD NR SYN DIS OFF 0 49500 WD RW Suspended046 046 R2:2 ?? WD NR SYN DIS OFF 0 33000 WD RW Suspended047 047 R2:2 ?? WD NR SYN DIS OFF - - WD RW Suspended09C 054 R1:2 RW RW RW SYN DIS OFF 0 0 RW NR Synchronized09D 055 R1:2 RW RW RW SYN DIS OFF 0 0 RW NR Synchronized09E 056 R1:2 RW RW RW SYN DIS OFF 0 0 RW NR Synchronized09F 057 R1:2 RW RW RW SYN DIS OFF 0 0 RW NR Synchronized0A0 058 R1:2 RW RW RW ACp DIS WP 0 0 RW NR Synchronized0A1 059 R1:2 RW RW RW ACp DIS WP 0 0 RW NR Synchronized

DATE: 03/11/02


Entries in the RDF Typ:G column identify the device as either an R1 or R2 device and the RDF (RA) groupnumber after the colon. The display also shows the state of the SRDF devices and their RDF links. For theSRDF 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 tothe 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 arewrite disabled (WD), the RDF links are not ready (NR), and the remote devices are read-writeable (RW).The R2 Invalid 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 in synchronous mode (SYN) or Adaptive Copy mode(ACp). Domino mode is disabled (DIS). When in Adaptive Copy mode, the modes type is either AdaptiveCopy Disk (AD) or Adaptive Copy Write-Pending (WP). Status information about the Front End Director(SA) and Remote Link Director (RA) is also displayed.

By default, symrdf list displays devices by their Symmetrix device name. To display host-visibledevices by their physical device name, include the pd argument on the command line.

Options such as r1, r2, bcv, or nobcv allow you to display a list of specific interest, such asjust the R1 devices, R2 devices, BCV devices, or standard devices. For a complete list of options for thiscommand, refer to EMC Solutions Enabler SYMCLI SRDF Component Product Guide (P/N 300-000-444).

If the concurrent RDF configuration state is enabled for a Symmetrix unit, use the concurrent optionto display devices that are configured as concurrent RDF pairs. For example:

symrdf list -sid 77 -concurrent




028 050 R1:1 RW RW RW SYN DIS OFF 0 0 RW WD Synchronized000 R1:2 RW RW RW SYN DIS OFF 0 0 RW WD Synchronized

029 051 R1:1 RW RW RW SYN DIS OFF 0 0 RW WD Synchronized001 R1:2 RW RW RW SYN DIS OFF 0 0 RW WD Synchronized

The display shows an R1 source device (028) paired with two R2 target devices (050 and 000); Symmetrixdevice 029 is paired concurrently with devices 051 and 001. Note that each of the two concurrent devices ofan 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 dynamicoption to display SRDF pairs whose devices have been configured as dynamic SRDF devices. WithEnginuity version 5567, the following display shows SRDF devices that have been configured for dynamicswap (fast swap).

DATE: 03/11/02


symrdf list -dynamic




072 092 R1:1 RW RW RW SYN DIS OFF 0 0 RW WD Synchronized073 093 R1:1 RW RW RW SYN DIS OFF 0 0 RW WD Synchronized074 094 R1:1 RW RW RW SYN DIS OFF 0 0 RW WD Synchronized

With Enginuity version 5568, this display will show devices configured for RDF use and created as dynamicSRDF pairs using the symrdf createpair command. Once you have created dynamic SRDF pairs,you can display all, or subsets of, these pairs by omitting or including various options with the symrdflist dynamic command(both, r1, or r2). Including the both option displays dynamicSRDF pairs in which the paired devices can be either R1 or R2 devices (a requirement for dynamic R1/R2swap). Including the r1 option displays only dynamic SRDF pairs in which R1 devices cannot become R2devices. Including the r2 option displays only R2 devices that cannot become R1 devices. Omitting allthree of these options displays all dynamic SRDF pairs, regardless of their device configurations.

Displaying Information about BCV DevicesInformation about TimeFinder BCV devices is stored in two different locations:

Information about a device group and the devices defined in it are stored in your hosts SYMAPIdatabase file.

Information about BCV pairs and their current state is stored in the Symmetrix global memory.

When you initially form a device group, membership information about the groups BCVs and standardsmay differ from the pairing information stored inside the Symmetrix. For example, a BCV or standard thatyou add to your device group could have a current pairing relationship with a device that does not belong tothe device group.

Figure 3 shows that while the standard device 084 and BCV 089 are members of the same device group, therecord in the Symmetrix indicates that the same standard device 084 was last paired with BCV 088 and stillhas a pairing relationship with that device. Any attempt to establish an 084/089 pair would fail without theuse of a preferred pair attachment or symmir full establish command options that override thestandards prior pairing relationship with BCV 088.

DATE: 03/11/02


Host

Symmetrix

Device groupdefinitionsstored inSYMAPIdatabaseon host

Standard/BCVpairing

informationstored in

SymmetrixBCV089

STD084

BCV088

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 statusof devices before adding them to your group. Even if no old device groups exist, device pairings may havebeen 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.

To check if BCV devices already belong to a device group, use the symdev list bcv command:

symdev list -bcv




088 /dev/rdsk/c4t1d0s2 16B:0 01A:D0 2-Way BCV Mir N/Asst'd RW 516089 /dev/rdsk/c4t1d1s2 16B:0 02A:D0 2-Way BCV Mir N/Asst'd RW 51608A /dev/rdsk/c4t1d2s2 16B:0 01B:D0 2-Way BCV Mir Asst'd RW 51608B /dev/rdsk/c4t1d3s2 16B:0 02B:D0 2-Way BCV Mir Asst'd RW 516

Asstd means that BCVs 08A and 08B belong to (are associated with) a device group. N/Asstd meansthat BCVs 088 and 089 are not associated with a device group. To determine which device group BCVs 08Aand 08B belong to, you can use the symdev show 08A and symdev show 08B commands.

To check if BCV devices have a current pairing relationship, use the symbcv list command:

DATE: 03/11/02


symbcv list


BCV Device Standard Device Status------------------------------------ --------------------------- -----------

Inv. Inv.Physical Sym RDF Att. Tracks Physical Sym Tracks BCV STD------------------------------------ --------------------------- -----------

Not Visible 030 (M) 0 N/A N/A 0 NeverEstabNot Visible 031 (m) - N/A N/A - NeverEstab

c4t1d0s2 088 0 c4t0d0s2 084 0 Splitc4t1d1s2 089 0 c4t0d1s2 085 0 Splitc4t1d2s2 08A 0 c4t0d2s2 086 0 Splitc4t1d3s2 08B 0 c4t0d3s2 087 0 Split

The Split status of BCVs 088, 089, 08A, and 08B means that these devices have a current pairingrelationship with a standard device (084, 085, 086, and 087, respectively). To establish one of these BCVswith a different standard device would require a symmir command that explicitly overrides the currentpairing relationship.

The display also shows two BCVs (030 and 031) that are not visible to the host and do not have a currentpairing relationship. NeverEstab means never established. Also, these two BCVs constitute a meta device a meta head (M) and a meta member (m).

Displaying Information about a Device GroupA device group is a user-defined entity that you can use to represent and manage multiple devices. Whenyou initially create a device group and add devices to it, membership information about the group is storedin your hosts SYMAPI database file. When BCV pairs or SRDF pairs are established, their pairing status isstored in Symmetrix global memory. Various SYMCLI commands access both sources of information todisplay configuration, status, and performance data on the collective devices within the device group.

The symdg list command displays a list of any device groups that have already been defined in yourhosts SYMAPI database file. The symdg show DgName command displays the membership andconfiguration details of any existing device group2. For example, the following display of an RDF1 typedevice group named RDFGrp1 shows that the group includes 7 local standard devices, 7 locally associatedBCVs, and 7 remotely associated BCVs (devices located on a remote Symmetrix unit but associated with thedevice group defined on the local host). Figure 4 in the middle of this display illustrates this configuration.The device group also includes one gatekeeper device (GK), which means that this gatekeeper device isdedicated to the standard devices in this device group.

symdg show RDFGrp1

Group Name: RDFGrp1

Group Type : REGULARValid : YesSymmetrix ID : 000185500814Group Creation Time : Tue Oct 16 09:49:41 2001

2 The symcg list and symcg show commands display the same information for an SRDF consistency group.

DATE: 03/11/02


Vendor ID : EMC CorpApplication ID : SYMCLI

Number of STD Devices in Group : 7Number of Associated GK's : 1Number of Locally-associated BCV's : 7Number of Remotely-associated BCV's (STD RDF): 0Number of Remotely-associated BCV's (BCV RDF): 7

Standard (STD) Devices (7):{--------------------------------------------------------------------

Sym CapLdevName PdevName Dev Att. Sts (MB)--------------------------------------------------------------------

DEV001 /dev/vx/rdmp/c4t0d107s2 03F7 RW 1031DEV002 /dev/vx/rdmp/c4t0d108s2 03F8 RW 1031DEV003 /dev/vx/rdmp/c3t4d3s2 03F9 RW 1031DEV004 /dev/vx/rdmp/c3t0d0s2 03FA RW 1031DEV005 /dev/vx/rdmp/c3t0d1s2 03FB (M) RW 4125DEV006 /dev/vx/rdmp/c3t0d2s2 03FF (M) RW 4125DEV007 /dev/vx/rdmp/c3t0d3s2 0403 (M) RW 4125}

Associated GateKeeper Devices (1):{--------------------------------------------------------------------

Sym CapLdevName PdevName Dev Sts (MB)--------------------------------------------------------------------

N/A /dev/vx/rdmp/c3t4d2s2 025B RW 3}

BCV Devices Locally-associated (7):{--------------------------------------------------------------------


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 Devices Remotely-associated (BCV RDF) (7):{--------------------------------------------------------------------


BRBCV001 N/A 03A0 RW 1031BRBCV002 N/A 03A1 RW 1031BRBCV003 N/A 03A2 RW 1031

DATE: 03/11/02


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

Standard

BRBCV

R2

Host

Local Symmetrix814

Remote Symmetrix505

CLI-000018

R1BCV

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 thenames and status of each device belonging to the group. Note that each device has a physical device name(PdevName), Symmetrix device name (a 4-digit hexadecimal number that the Symmetrix assigns to eachphysical device)3, and logical device name (LdevName). When you add a device to a device group, a logicaldevice 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 groups RDF information, including theidentity of each remote Symmetrix unit in the configuration, RDF configuration settings, and the combinedstate of all BCV RDF devices in the group and their RDF links.

Device Group BCV RDF Information{RDF Type : R1RDF (RA) Group Number : 2 (B)

Remote Symmetrix ID : 000185500505

RDF Mode : SynchronousRDF Adaptive Copy : DisabledRDF Adaptive Copy Write Pending State : N/ARDF Adaptive Copy Skew (Tracks) : 65535


RDF Link Configuration : Direct Escon FibreRDF Link Domino : Disabled

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

DATE: 03/11/02


Prevent Automatic RDF Link Recovery : DisabledPrevent RAs Online Upon Power ON : Enabled


Device RA Status : Ready (RW)Device Link Status : Not Ready (NR)

Device Suspend State : OfflineDevice Consistency State : DisabledRDF R2 Not Ready If Invalid : Enabled

Device RDF State : Not Ready (NR)Remote Device RDF State : Ready (RW)

RDF Pair State ( R1 =====> R2 ) : Failed Over


The SYMCLI query argument is a useful means of displaying information about device pairs, especiallyreal-time status of Symmetrix devices belonging to a device group or consistency group. Querying aTimeFinder device group displays the state of BCV pairs in a Symmetrix unit. Querying an SRDF devicegroup or consistency group displays the state of SRDF pairs in a configuration in which data copying occursover RDF links. Table 3 lists several often used commands that use the query argument.

Table 3. Useful query Commands

Query Command Displayssymmir query Status of TimeFinder BCV pairs that belong to a device group.symrdf query Status of SRDF pairs that belong to a device group or consistency group.symreplicate query Status of SAR copy cycles being processed in the background.

The following symmir query command shows the status of the four BCV pairs in the device group afteran establish operation was performed. Two of the pairs are fully synchronized, and two are still in progress(the BCVs Inv Tracks column indicating the number of invalid tracks on the BCV that still need to becopied from the standard device). An asterisk (*) next to the BCVs device name means that the BCVbelongs to the device group. If the asterisk is absent, the BCV is outside the device group.

symmir -g ProdBgrp query

Device Group (DG) Name: ProdBgrpDG's Type : REGULARDG's Symmetrix ID : 000000003264

Standard Device BCV Device State------------------------- ------------------------------------ ------------

Inv. Inv.Logical Sym Tracks Logical Sym Tracks STD BCV------------------------- ------------------------------------ ------------

DEV001 084 0 BCV001 088 * 0 SynchronizedDEV002 085 0 BCV002 089 * 0 SynchronizedDEV003 086 0 BCV003 08A * 414 SyncInProgDEV004 087 0 BCV004 08B * 627 SyncInProg

DATE: 03/11/02


Total ------- -------Track(s) 0 1041MB(s) 0.0 32.5

Legend:

(*): The paired BCV device is associated with this group.

After splitting all BCV pairs in this device group and concurrently establishing DEV001 with BCV003 andBCV004, a symmir query command with the multi option displays the DEV001 relationship withthe two concurrent BCVs as well as its prior pairing relationship with BCV001. The DEV002 standarddevice still has a pairing relationship with BCV002. However, the prior pairing relationships of DEV003 andDEV004 with their BCVs were superceded by DEV001s new pairing relationship with those BCVs.

symmir -g ProdBgrp query -multi

Device Group (DG) Name: ProdBgrpDG's Type : REGULARDG's Symmetrix ID : 000000003264

Standard Device BCV Device State------------------------- ------------------------------------ ------------

Inv. Inv.Logical Sym Tracks Logical Sym Tracks STD BCV------------------------- ------------------------------------ ------------

DEV001 084 0 BCV003 08A * 138090 SyncInProg0 BCV004 08B * 138090 SyncInProg8 BCV001 088 * 0 Split

DEV002 085 0 BCV002 089 * 0 Split

Total (Primary) ------ -------Track(s) 0 138090MB(s) 0.0 4315.3

Table 4 lists options available with the symmir query command.

Table 4. Options with the symmir query Command

Option Display-attach The BCV attachment relationship and pairing relationship.-multi 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.

The symrdf query command displays the state of a device groups SRDF devices and their RDF links.

symrdf -g Rdf1Grp query

Device Group (DG) Name: Rdf1GrpDG's Type : RDF1DG's Symmetrix ID : 000000003264

Source (R1) View Target (R2) View M O D E S

DATE: 03/11/02


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

ST LI ST MStandard A N A oLogical T R1 Inv R2 Inv K T R1 Inv R2 Inv d RDF PairDevice Dev E Tracks Tracks S Dev E Tracks Tracks e Dom ACp STATE----------------------------- -- --------------------- ----------- ------------

DEV001 09C RW 0 0 RW 054 NR 0 0 SYN DIS OFF SynchronizedDEV002 09D RW 0 830 RW 055 NR 0 0 SYN DIS OFF SynchInProg

Total ------- ------- ------- -------Track(s) 0 0 0 0MB(s) 0.0 0.0 0.0 0.0

The R1 devices are read-writeable, and the RDF links are read-writeable. However, the R2 devices, whichare acting as mirrors to the R1 devices, are write disabled (WD) and cannot be written to by their target-sidehost(s) at this time. The link is operating in synchronous mode (indicated by SYN in the Mode column). Oneof the SRDF pairs is fully synchronized and one is still in the process of synchronizing. On the SyncInProgpair, 830 R2 invalid tracks on the source (R1) side still remain to be copied to the target device (055) tocomplete the synchronization process. The R2 invalid tracks on the R1 side represent those tracks that arestill owed to the R2 side.

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

Table 5. Options with the symrdf query Command

Option Display-bcv All RDF BCV devices that are members of a device groups SRDF pairs.-rdfg all Ensures that the display shows the status of both links of a concurrent SRDF pair.-rdfg # 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 update until operation.

DATE: 03/11/02


Example 1: Verifying that Configuration Information inthe SYMAPI Database Shows the Current ConfigurationWhenever a Symmetrix configuration is new or has changed, you need to ensure which Symmetrix units areconnected to your host and that the information about these Symmetrix units is current.

The symcfg discover command builds or rebuilds your hosts SYMAPI database file with the mostcurrent information about the physical devices directly connected to your host. The command scans allbuses, collects information about all the devices found, and rebuilds the database with collected informationfrom all locally and remotely attached Symmetrix devices.

# symcfg discover

This operation may take up to a few minutes. Please be patient...

The symcfg list command displays the configuration information from the local hosts SYMAPIdatabase file.

# symcfg list

S Y M M E T R I X


000185500814 Local 8230 5568 4096 728 1085000185500505 Remote 8230 5568 8192 0 970

The symcfg verify command determines if the Symmetrix configuration and the SYMAPI databasefile are in sync. If they are out of sync, the verify action returns code 24 (CLI_C_NOT_IN_SYNC). If theyare in sync, the verify action returns code zero (the CLI_C_SUCCESS value) as shown below using theecho $status command.

# symcfg verify -sid 814

The Symmetrix configuration and the database file are in sync.

# echo $status0

A new device is now added to local Symmetrix 814, changing the configuration. The verify action isrepeated, and its output shows an out-of-sync condition. The echo $status command returns the value24, confirming that the configuration and the database configuration information are now out of sync.


The Symmetrix configuration and the database file are NOT in sync.

# echo $status24

DATE: 03/11/02


The symcfg discover command rebuilds your hosts SYMAPI database file with the most currentinformation.

# symcfg discover

This operation may take up to a few minutes. Please be patient...

The symcfg list command now displays the updated configuration information from the local hostsrebuilt SYMAPI database file. Note that the number of Symmetrix devices displayed for Symmetrix 814 hasincreased from 1085 (shown in the previous symcfg list) to 1086.# symcfg list

S Y M M E T R I X


000185500814 Local 8230 5568 4096 728 1086000185500505 Remote 8230 5568 8192 0 970

The symcfg verify command confirms that the configuration and SYMAPI database file are now insync again.


The Symmetrix configuration and the database file are in sync.

DATE: 03/11/02


Example 2: Obtaining More Symmetrix InformationThis example illustrates some of the more useful symcfg list options not described earlier in this paper.

Using the connections option with symcfg list command allows you to see the hostconnections to a Symmetrix unit. Only those hosts that have at least one registered application are listed. Thenode name hk185500814 is the service processor.

# symcfg list -connections

Symmetrix ID : 000185500814

Symmetrix Host------------- -----------------------------------------------------------

Director Port Node Name IP Address HW Type OS Name OS Revision-------- ---- ------------- --------------- -------- -------- -----------

DA-1A 0 hk185500814 172.26.131.103 INTEL WinNT 4.0.1381SA-4A 0 api183 172.23.65.183 9000/800 HPUX B.11.00SA-13A 0 api183 172.23.65.183 9000/800 HPUX B.11.00SA-4B 0 api212 172.23.65.212 9000/800 HPUX B.11.00FA-5B 0 api179 172.23.65.179 sun4u SunOS 5.8FA-12B 0 api179 172.23.65.179 sun4u SunOS 5.8

Using the sorthost option with the connections option and symcfg list command allowsyou 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 Symmetrix------------------------------------------------- --------------------------

Node Name IP Address OS Name OS Revision ID Director Port------------ --------------- -------- ----------- ------------ -------- ----

hk185500814 172.26.131.103 WinNT 4.0.1381 000185500814 DA-1A 0

api179 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 useslock numbers 0 to 15; applications assigned by EMC use lock numbers greater than 15. By default, thesymcfg list lock command displays what Symmetrix units have a lock number of 0 (used to lock aSymmetrix 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 TimeSymmID Attachment Status Number Held (Sec)

000185500814 Local Unlocked N/A N/A000185500505 Remote Unlocked N/A N/A

DATE: 03/11/02


Using the lockn option with symcfg list displays Symmetrix units that have a specific locknumber. Specifying zero (0) in the following command displays Symmetrix units that currently have anexternal lock for SRDF operations. That is, an SRDF control operation was executing when this commandwas issued. Using the lockn RDF option displays Symmetrix units that have any of the sixteen locks(0x100 to 0x10F) used during SRDF operations. Using the lockn ALL option displays these operationlocks 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 TimeSymmID Attachment Status Number Held (Sec)

000185500814 Local Locked 0 8000185500505 Remote Locked 0 8

Using the applications option with symcfg list displays all applications that are registered in aSymmetrix unit and that have accessed that Symmetrix unit. The following display lists such applications ona Symmetrix unit (sid 814) connected to the local host. An application listed with the connectionsoption is not listed here if it has never accessed the Symmetrix unit.

# symcfg list -applications


Host Application---------------------------- ------------------------------------------------

Node Name IP Address ID Vendor ID Version Attr------------ --------------- ---------------- ---------------- --------------

api179 172.23.65.179 SYMCLI EMC Corp 5.0.0.1 -SYMCLI EMC Corp 5.0.0.0 -EMCpower EMC Corp 2.1.0.0 -SYMCLI EMC Corp 5.0.0.32 -SYMCLI EMC Corp 5.0.0.29 -

api180 172.23.65.180 SYMCLI EMC Corp 5.0.0.32 (R)

hk185500814 172.26.131.103 OPTIMIZER EMC Corp 2.0.0.4 -

Legend for Attribute(s):

(M) : Application Registered Remotely via RDF links (Multi-Hop).(R) : Application Registered Remotely via RDF links (One-Hop).

Using the semaphores option with symcfg list displays gatekeeper (GK), database (DB), andlock file (FILE) semaphores.# symcfg list -semaphores

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

Lock Proc.ID Key State Type Wait Lock Full Path Specification------ ---------- -------- ---- ----- ----------------------------

DATE: 03/11/02


1 0x45000327 Unlocked GK 0 /dev/rdsk/c4t0d103s23 0x45000ba7 Unlocked GK 0 /dev/rdsk/emcpower218c1 0x45000327 Unlocked DB 0 /var/symapi/db/symapi_db.bin0 0x45000246 Unlocked FILE 0 /var/symapi/config/symapislck

Using the services option with symcfg list displays configured network services for useby 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 Domain Type Node Name Address Number------------ ------ -------- -------------------- --------------- ------

api182 TCPIP api182 172.23.65.182 2707

DATE: 03/11/02


Example 3: Obtaining More Device InformationThis example illustrates some of the more useful symdev list options not described earlier in this paper.

SYMAPI uses device external locks in a Symmetrix unit to lock BCV pairs during TimeFinder operationsand SRDF pairs during SRDF control operations. The following command displays external locks onstandard devices on Symmetrix 814 during a Symmetrix Automated Replication (SAR) operation. That is,the command was issued in the middle of a SAR cycle.

# symdev list -lock


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

Device Name Device---------------------------- -----------------------------------------------

Lock Lock Seconds Lock DeviceSym Physical Number Holder ID Held Flags Attribute---------------------------- -----------------------------------------------

03F7 /dev/vx/rdmp/c4t0d107s2 9 0x10010FE6 111 Long Grp'd03F8 /dev/vx/rdmp/c4t0d108s2 9 0x10010FE6 111 Long Grp'd03F9 /dev/vx/rdmp/c3t4d3s2 9 0x10010FE6 111 Long Grp'd03FA /dev/vx/rdmp/c3t0d0s2 9 0x10010FE6 111 Long Grp'd

Using the multiport option with the symdev list command displays devices that are mapped tomultiple front-end SCSI (SA) adapter ports. For example, the following display shows Symmetrix device0000 mapped to SA ports 12B:0 and 05B:0. Other devices (Sym column) are mapped to these same ports.# symdev list -multiport


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


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

0000 16B:D1 2-Way Mir Grp'd RW 4315/dev/vx/rdmp/c4t0d0s2 - 12B:0 - - - - -/dev/vx/rdmp/c5t0d0s2 - 12B:0 - - - - -/dev/rdsk/emcpower116c - 05B:0 - - - - -/dev/rdsk/c4t0d0s2 - 05B:0 - - - - -/dev/rdsk/c5t0d0s2 - 12B:0 - - - - -


DATE: 03/11/02



00C8 01A:C2 RDF2+Mir N/Grp'd WD 4315Not Visible - 05A:0 - - - - -Not Visible - 12A:0 - - - - -

00C9 15A:C2 RDF2+Mir N/Grp'd WD 4315Not Visible - 05A:0 - - - - -Not Visible - 12A:0 - - - - -

Using the firstport option with the symdev list command displays just the first port ofinformation for devices that are mapped to multiple ports.

# symdev list -firstport



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

0000 /dev/vx/rdmp/c4t0d0s2 12B:0 16B:D1 2-Way Mir Grp'd RW 43150001 /dev/vx/rdmp/c4t0d1s2 12B:0 02B:D1 2-Way Mir Grp'd RW 43150002 /dev/vx/rdmp/c4t0d2s2 12B:0 01B:D1 2-Way Mir Grp'd RW 43150003 /dev/vx/rdmp/c4t0d3s2 12B:0 16A:D1 2-Way Mir Grp'd RW 43150004 /dev/vx/rdmp/c4t0d4s2 12B:0 15A:D1 2-Way Mir Grp'd RW 43150005 /dev/vx/rdmp/c4t0d5s2 12B:0 01A:D1 2-Way Mir Grp'd RW 4315

Using the resv option with the sympd list command displays all Symmetrix devices that haveSCSI reservations.

# sympd list -resv


Device Name Device Reservation---------------------------- ------------- ------------------

Physical Sym Config Initiator SA :P---------------------------- ------------- ------------------

/dev/rhdisk20 0018 2-Way Mir 07 01C:0

DATE: 03/11/02


The symdev list command with the meta 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. "CapMB" is the total capacity of the entire meta device (meta head plus meta members).# symdev list -meta


Device Name Device Meta Information---------------------------- ---------------------- ---------------------------

Sym Physical Config Attr Config Stripe # of CapSize Devs (MB)

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

0268 Not Visible RDF2+Mir N/Grp'd Concated - 2 17263026A Not Visible RDF2+Mir N/Grp'd Striped 960k 3 25895026D Not Visible RDF2+Mir N/Grp'd Striped 3840k 3 258950270 Not Visible BCV N/Asst'd Concated - 2 172630272 Not Visible BCV N/Asst'd Striped 960k 3 258950275 Not Visible BCV N/Asst'd Striped 3840k 3 2589503C7 Not Visible Unprotected N/Grp'd Striped 1920k 4 412503C8 Not Visible Unprotected N/Grp'd Striped 7680k 4 412503D3 Not Visible Unprotected N/Grp'd Concated - 4 412503D6 Not Visible Unprotected N/Grp'd Striped 30720k 4 412503D7 Not Visible BCV N/Asst'd Striped 1920k 4 412503D8 Not Visible BCV N/Asst'd Concated - 4 412503DF Not Visible BCV N/Asst'd Striped 7680k 4 412503E0 Not Visible BCV N/Asst'd Striped 1920k 4 412503E2 Not Visible BCV N/Asst'd Striped 30720k 4 412503E5 Not Visible BCV N/Asst'd Striped 7680k 4 412503F4 Not Visible BCV N/Asst'd Concated - 4 412503F5 Not Visible BCV N/Asst'd Striped 30720k 4 412503FB /dev/rdsk/emcpower229c 2-Way Mir Grp'd Striped 7680k 4 412503FF /dev/vx/rdmp/c3t0d2s2 2-Way Mir Grp'd Concated - 4 41250403 /dev/vx/rdmp/c3t0d3s2 2-Way Mir Grp'd Striped 15360k 4 4125040B Not Visible RDF1-BCV+Mir Asst'd Striped 7680k 4 4125040F Not Visible RDF1-BCV+Mir Asst'd Concated - 4 41250413 Not Visible RDF1-BCV+Mir Asst'd Striped 15360k 4 4125

DATE: 03/11/02


When a disk fails, a hot spare (a spare disk) is invoked against it. All devices that have mirrors (hypers) onthe failed disk against which the hot spare was invoked, are shown in the symdev list hotsparedisplay as having a hot spare invoked against them. This display shows that Symmetrix 120 has not had anyhot spares invoked against failed disks, whereas Symmetrix 180 shows one hot (dynamic) spare invocationagainst disk 01A:D0. Note that Unprotected devices with a hot spare invoked against them become notready (NR) because unprotected devices have no mirror to kick in to mirror the spare hyper. On the otherhand, mirrored devices stay ready (RW) when a hot spare is invoked against them.# symdev list -hotspare


Could not select any Symmetrix devices to list.




0010 Not Visible ???:? 01A:D0 Unprotected N/Grp'd NR 1030098 Not Visible ???:? 01A:D0 Unprotected N/Grp'd NR 4700AE Not Visible 13A:0 01A:D0 2-Way Mir N/Grp'd RW 431500C7 Not Visible ???:? 01A:D0 Unprotected N/Grp'd NR 4700DF Not Visible ???:? 01A:D0 Unprotected N/Grp'd NR 4700F5 Not Visible ???:? 01A:D0 Unprotected N/Grp'd NR 470108 Not Visible ???:? 01A:D0 2-Way Mir N/Grp'd RW 469

DATE: 03/11/02


Example 4: Obtaining Information about Dynamic SRDFDevicesThis example examines a local source Symmetrix unit (sid 810) connected via RDF links to a remoteSymmetrix unit (sid 506). Both Symmetrix units are running Enginuity version 5568. The example showshow to display devices that are configured for RDF capability. These devices can be used to create dynamicSRDF pairs while the Symmetrix units are in operation (on the fly).

The symcfg list command displays high-level information on Symmetrix units in this configuration.

# symcfg list

S Y M M E T R I X


000185500810 Local 8430 5568 32760 198 325000185500506 Remote 8430 5568 32760 0 326

With Enginuity version 5568 and higher, the symdev list command with the dynamic optiondisplays devices that have been created as, or are capable of being created as, dynamic SRDF devices usingthe symrdf createpair command. Devices on Symmetrix 810 that are visible to the host are capableof being dynamically paired as either R1 or R2 devices. When combined with the r1 option, symdevlist dynamic displays only devices capable of being dynamic R1 devices; when combined with the r2 option, only devices capable of being dynamic R2 devices are displayed. RDF1+Mir devices in thedisplay have already been created as dynamic R1 devices, but are still capable of being either an R1 or R2device (a requirement for dynamic R1/R2 swap).# symdev list -dynamic -sid 810




00F2 /dev/rdsk/emcpower224c 04A:0 15B:C4 Unprotected N/Grp'd RW 206300F5 /dev/rdsk/emcpower227c 04A:0 01A:D1 Unprotected N/Grp'd RW 206300FA /dev/rdsk/emcpower239c 04A:0 15A:C4 Unprotected N/Grp'd RW 20630106 /dev/rdsk/emcpower235c 04A:0 01B:D3 Unprotected N/Grp'd RW 2063010A /dev/rdsk/emcpower237c 04A:0 15A:D3 Unprotected N/Grp'd RW 2063010F /dev/rdsk/emcpower240c 04A:0 02B:C2 Unprotected N/Grp'd RW 20630145 Not Visible 04A:0 01A:C1 RDF1+Mir N/Grp'd RW 20630146 Not Visible 04A:0 15A:C1 RDF1+Mir N/Grp'd RW 20630147 Not Visible 04A:0 02A:C1 RDF1+Mir N/Grp'd RW 20630148 Not Visible 04A:0 15A:D1 RDF1+Mir N/Grp'd RW 20630149 Not Visible 04A:0 02A:D1 3-Way Mir N/Grp'd RW 2063014A Not Visible 04A:0 16B:C4 3-Way Mir N/Grp'd RW 2063014B Not Visible 04A:0 02B:C4 3-Way Mir N/Grp'd RW 2063

DATE: 03/11/02


Example 5: Obtaining More Device Group InformationThis example illustrates some options for obtaining device group information not described earlier in this paper.

This display is similar to the symdg show RDFGrp1 display on page 19, but shows a configuration inwhich five local R1 devices are the source devices and five remotely associated BCVs are the targets. Thatis, the R1 devices copy data to their R2 devices, which copy that data to the BCVs located on the sameremote Symmetrix unit.

# symdg show RDFGrp2

Group Name: RDFGrp2

Group Type : RDF1Valid : YesSymmetrix ID : 000185500814Group Creation Time : Thu Nov 29 14:11:05 2001Vendor ID : EMC CorpApplication ID : SYMCLI

Number of STD Devices in Group : 5Number of Associated GK's : 0Number of Locally-associated BCV's : 0Number of Remotely-associated BCV's (STD RDF): 5Number of Remotely-associated BCV's (BCV RDF): 0

Standard (STD) Devices (5):{--------------------------------------------------------------------


DEV001 /dev/vx/rdmp/c4t0d102s2 03C2 RW 4315DEV002 /dev/vx/rdmp/c4t0d103s2 03C3 RW 4315DEV003 /dev/vx/rdmp/c4t0d104s2 03C4 RW 4315DEV004 /dev/vx/rdmp/c4t0d105s2 03C5 RW 4315DEV005 /dev/vx/rdmp/c4t0d106s2 03C6 RW 4315}

BCV Devices Remotely-associated (STD RDF) (5):{--------------------------------------------------------------------


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}

DATE: 03/11/02


This second part of the symdg show output displays the device groups RDF information, including theidentity of the remote Symmetrix unit (sid 505), RDF configuration settings (Enabled or Disabled), and thecombined state of all standard RDF devices in the group and their RDF links (ReadyRead/Write enabled orWrite Disabled).

Device Group RDF Information{RDF Type : R1RDF (RA) Group Number : 2 (B)

Remote Symmetrix ID : 000185500505

RDF Mode : Adaptive CopyRDF Adaptive Copy : Enabled: Disk ModeRDF Adaptive Copy Write Pending State : N/ARDF Adaptive Copy Skew (Tracks) : 65535


RDF Link Configuration : Direct Escon FibreRDF Link Domino : EnabledPrevent Automatic RDF Link Recovery : EnabledPrevent RAs Online Upon Power ON : Enabled


Device RA Status : Ready (RW)Device Link Status : Ready (RW)

Device Suspend State : N/ADevice Consistency State : DisabledRDF R2 Not Ready If Invalid : Enabled

Device RDF State : Ready (RW)Remote Device RDF State : Write Disabled (WD)

RDF Pair State ( R1 R2 ) : Synchronized


DATE: 03/11/02


It is possible to get device configuration and status information about devices by querying the device groupto which they have been added. The symmir query command displays the status of BCV pairs in adevice group, Rdf1Grp, that contains one SRDF standard device and one local BCV device. The BCV pair iscurrently in the Split state.

# symmir -g Rdf1Grp query


Standard Device BCV Device State-------------------------- ------------------------------------- ------------

Inv. Inv.Logical Sym Tracks Logical Sym Tracks STD BCV-------------------------- ------------------------------------- ------------

DEV001 010F 0 BCV001 00CD * 0 Split

Total ------- -------MB(s) 0.0 0.0

Legend:

(*): The paired BCV device is associated with this group.

The symrdf query command displays the status of SRDF pairs in the device group. The R1 sourcedevice (010F) is currently suspended from its R2 target device (00BF).# symrdf -g Rdf1Grp query


Source (R1) View Target (R2) View M O D E S----------------------------- --------------------- ----------- ------------

ST LI ST MStandard A N A oLogical T R1 Inv R2 Inv K T R1 Inv R2 Inv d RDF PairDevice Dev E Tracks Tracks S Dev E Tracks Tracks e Dom ACp STATE----------------------------- -- --------------------- ----------- ------------

DEV001 010F RW 0 66000 NR 00BF WD 0 66000 SYN DIS OFF Suspended

Total ------ ------ ------ ------MB(s) 0.0 2062.0 0.0 2062.0

DATE: 03/11/02


The symdg show command with the lock option displays existing device external locks on deviceswithin 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 SAR 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

Group Name: sar

Group Type : REGULARValid : YesSymmetrix ID : 000185500814Group Creation Time : Tue Oct 16 09:49:41 2001Vendor ID : EMC CorpApplication ID : SYMCLILock Number : 9

Number of Locked Devices in Group:

STD Devices : 16 (SID: 000185500814)Remote Mirrors of STD's : 0 (SID: N/A )BCV Devices : 16 (SID: 000185500814)Remote Mirrors of BCV's : 16 (SID: 000185500505)RBCV Devices : 0 (SID: N/A )Remote Mirrors of RBCV's : 0 (SID: N/A )BRBCV Devices : 16 (SID: 000185500505)Remote Mirrors of BRBCV's : 0 (SID: N/A )

STD Devices (16):{-----------------------------------------------------

Sym Lock Director Seconds LockDev Holder-ID Initiator Number Held Flags-----------------------------------------------------

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 Long0402 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}

DATE: 03/11/02


BCV Devices (16):{-----------------------------------------------------


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 Long0415 0x1001100E 0 05B 13 Long0416 0x1001100E 0 05B 13 Long}

Remote Mirrors of BCV's (16):{-----------------------------------------------------


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 Long039D 0x100113A3 0 14B 13 Long039E 0x100113A3 0 14B 13 Long039F 0x100113A3 0 14B 13 Long}

DATE: 03/11/02


BRBCV Devices (16):{-----------------------------------------------------


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}

DATE: 03/11/02


Example 6: Obtaining Disk and Audit InformationThis example describes some of the more relevant displays from symdisk and symaudit commands.For more information about these commands, including details about other command options not shownhere, refer to EMC Solutions Enabler SYMCLI Base Component Product Guide (P/N 300-000-434).

The symdisk list command displays the configuration and status of the physical disks and theirhypers within a Symmetrix unit. A disk is identified by its DA symbol (Symb), its interface (Int) and itstarget ID (TID). To display verbose information about a specific disk (for example, 01A:C3) and its hypers,use symdisk list da 01A interface C tid 3 v hypers.

# symdisk list

Symmetrix ID : 000185500814Disks Selected : 96

Capacity(MB)Ident Symb Int TID Vendor Type Hypers Total Free------ ---- --- --- ---------- ---------- ------ -------- --------

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 446DA-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 962DA-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

DATE: 03/11/02


The symaudit commands retrieve information from the Symmetrix Audit Log file from data written tothe file during control operations. This information allows you to determine what application on what hostinitiated actions that directed Symmetrix behavior. The symaudit show command below displays thetime 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


Starting date : 12/14/2001 14:53:10Ending date : 12/17/2001 14:40:47

Starting record number : 1Ending record number : 127Total record count : 127

The following symaudit list command displays the extracted audit log records for local Symmetrix814 during the time period that data was collected. The ellipsis () indicates where some output wasomitted for brevity.

# symaudit list




Record Function ActionNumber Date Time Application Host Class Code------ -------- -------- ---------------- ------------ -------- ---------

1 12/14/01 14:53:10 SYMCLI api179 RDF Split2 12/14/01 14:53:10 SYMCLI api179 RDF Split3 12/14/01 14:53:11 SYMCLI api179 RDF Split4 12/14/01 14:53:16 SYMCLI api179 RDF IncEsta5 12/14/01 14:53:16 SYMCLI api179 RDF IncEsta6 12/14/01 14:53:17 SYMCLI api179 RDF IncEsta

14 12/14/01 16:32:39 SYMCLI api179 BCV FullEsta15 12/14/01 16:32:39 SYMCLI api179 BCV FullEsta16 12/14/01 16:33:01 SYMCLI api179 BCV FullEsta17 12/14/01 16:40:01 SYMCLI api179 BCV Split18 12/14/01 16:40:01 SYMCLI api179 BCV Split19 12/14/01 16:40:01 SYMCLI api179 BCV Split

109 12/17/01 14:39:05 SYMCLI api179 BCV Split110 12/17/01 14:39:07 SYMCLI api179 RDF IncEsta111 12/17/01 14:39:07 SYMCLI api179 RDF IncEsta112 12/17/01 14:39:08 SYMCLI api179 RDF IncEsta113 12/17/01 14:39:10 SYMCLI api179 BCV IncEsta114 12/17/01 14:39:10 SYMCLI api179 BCV IncEsta115 12/17/01 14:39:10 SYMCLI api179 BCV IncEsta

DATE: 03/11/02


116 12/17/01 14:39:10 SYMCLI api179 BCV IncEsta117 12/17/01 14:39:24 SYMCLI api179 BCV IncEsta118 12/17/01 14:39:24 SYMCLI api179 BCV IncEsta119 12/17/01 14:39:24 SYMCLI api179 BCV IncEsta120 12/17/01 14:39:24 SYMCLI api179 BCV IncEsta121 12/17/01 14:39:24 SYMCLI api179 BCV IncEsta122 12/17/01 14:39:42 SYMCLI api179 BCV IncEsta123 12/17/01 14:40:44 SYMCLI api179 BCV Split124 12/17/01 14:40:44 SYMCLI api179 BCV Split125 12/17/01 14:40:44 SYMCLI api179 BCV Split126 12/17/01 14:40:44 SYMCLI api179 BCV Split127 12/17/01 14:40:46 SYMCLI api179 BCV Split

Using the text option with the symaudit list command displays the text associated with theaudit log record.

# symaudit list -text




Record Time Function ActionNumber Class Code------- -------- -------- --------

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

1 14:53:10 RDF SplitSTARTING an RDF 'SPLIT'. type: Regular [RDF1 BCV], flags:

2 14:53:10 RDF Split[ 0407-0416 ]

3 14:53:11 RDF SplitThe RDF 'SPLIT' operation SUCCEEDED.

4 14:53:16 RDF IncEstaSTARTING an RDF 'INCREMENTAL ESTABLISH'. type: Regular [RDF1 BCV], flags:

5 14:53:16 RDF IncEsta[ 0407-0416 ]

6 14:53:17 RDF IncEstaThe RDF 'INCREMENTAL ESTABLISH' operation SUCCEEDED.

14 16:32:39 BCV FullEstaSTARTING a local 'BCV Full Establish' operation for 1 [STD-BCV] Pair:

15 16:32:39 BCV FullEsta[ 0000-0190 ]

16 16:33:01 BCV FullEsta'BCV Full Establish'. sts: SYMAPI_C_SUCCESS

17 16:40:01 BCV SplitSTARTING a local 'BCV Split' operation for 1 [STD-BCV] Pair:

18 16:40:01 BCV Split[ 0000-0190 ]

DATE: 03/11/02


19 16:40:01 BCV Split'BCV Split'. sts: SYMAPI_C_SUCCESS

using symcli to clean config information

Documents

symmetrix information

device information

status information

audit information

device group information

andwhere information

symmetrix devices

symmetrix units