Using Symcli To Clean Config Information

Engineering White Paper
Using SYMCLI to Obtain Symmetrix

Configuration Information
Date 3/11/2002
DATE: 03/11/02
Copyright 2002 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 THE
INFORMATION 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.
2
EMC, EMC , and Symmetrix are registered trademarks and Enginuity, PowerPath, SRDF, TimeFinder, and
where information lives are trademarks of EMC Corporation.
All other brand names are trademarks or registered trademarks of their respective owners.
Part Number H606.1

Printed 3/11/2002
Using SYMCLI to Obtain Symmetrix Configuration Information
DATE: 03/11/02
Table of Contents
Introduction .........................................................................................................3
Purpose and Scope................................................................................................................. 3
Related 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 SYMAPI
Database 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
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. 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 that represents a collection of devices
Purpose and Scope

This 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. Standard
displays 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 Documentation
The 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 Uses
Examining Symmetrix configuration data is especially helpful in understanding the configuration of the
Symmetrix 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 subsequent
commands to display more detailed information about that Symmetrix unit, such as a list of SRDF devices
or TimeFinder BCV devices on that Symmetrix unit.
Beginning with SYMCLI version 5.0 (and any Enguinity level supported by SYMAPI), you can use a
symdisk list command to display the configuration and status of the physical disks and their hypers
within a Symmetrix unit. Beginning with Enginuity version 5x68 and higher, you can use a symaudit
list command to retrieve information from the Symmetrix Audit Log file from 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.
DATE: 03/11/02
With SYMCLI version 4.3.1 and higher, 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 hosts 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 units global memory,
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, EMC recommends
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
symcfg verify 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_IN_SYNC). If they are
not 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 symcfg discover command to rebuild your hosts 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 symcfg discover 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 symcfg 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 invoke
the symcfg list command from the host. For example:
symcfg list
S Y M M E T R I X
SymmID
Attachment
000184501161 Local
000185500505 Remote
Model
Mcode
Version
Cache
Size (MB)
8430
8430
5567
5567
16384
8192
Num Phys
Devices
545
0
Num Symm
Devices
967
912
The display shows the configuration from the local hosts point of view. The local host is the controlling
host 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 161 is connected to remote Symmetrix 505. Both Symmetrix units
are running Enginuity version 5567.
The Num Symm Devices column displays the total number of Symmetrix devices configured for a
Symmetrix 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 545 physical
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.
If you issue the symcfg list command from a host connected to Symmetrix 505, then this Symmetrix
unit 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 about
Symmetrix units, such as whether the concurrent RDF and dynamic RDF states are enabled. You can display
details of all Symmetrix units in the configuration or a specific Symmetrix by including its sid on the
command line. For example, to display the details of Symmetrix 233:
symcfg list sid 233 -v
Product Model
Symmetrix ID
: 8130
: 000000005233
Microcode Version (Number)

Microcode Date
: 5567 (15BFAA01)
: 11.12.2001
Microcode Patch Date

Microcode Patch Level
: 11.12.2001
: 37
Cache Size
# of Available Cache Slots
# of PermaCache Slots In Use
Max # of System Write Pending Slots
Max # of DA Write Pending Slots
Max # of Device Write Pending Slots
:
4096 (MB)
: 113821
: 20426
: 91145
: 45572
: 11110
Symmetrix
Symmetrix
Symmetrix
Symmetrix
:
:
:
:
70 days, 03:34:44
Fri Sep 21 09:17:04 2001
Mon Nov 19 11:04:20 2001
Mon Nov 19 11:04:20 2001
Host DB Sync Time

Symmetrix CLI (SYMCLI) Version
Built with SYMAPI Version
SYMAPI Run Time Version
:
:
:
:
Fri Nov 30 09:32:35 2001

V4.3.1.0 (Edit Level: 173)
V4.3.1.0 (Edit Level: 173)
V4.3.1.0 (Edit Level: 173)
Number of Configured (Sym) Devices

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

Powerpath Run Time Version
: 40
: 2.1.0
Total Operating Time

Power ON Time
Last IPL Time (Cold)
Last Fast IPL Time (Hot)
SDDF Configuration State

:
Configuration Change State
:
WORM Configuration Level
:
Symmetrix Configuration Checksum
:
Switched RDF Configuration State
:
Concurrent RDF Configuration State
:
Dynamic RDF Configuration State
:
RDF Data Mobility Configuration State:
Enabled
Enabled
N/A
438DA
Disabled
Disabled
Disabled
Disabled
Devices that are configured as PowerPath-connected devices provide support for controlling SRDF
consistency groups and for performing TimeFinder consistent split operations. This Symmetrix display
shows 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 the
Configuration Change State (the state of allowing configuration changes) are enabled. The WORM (Write
Once Read Many) configuration level is not enabled (N/A) for this Symmetrix unit. The Symmetrix
Configuration 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 changed
compared to the SYMAPI database.
The last four configuration states in the display are all disabled. Switched RDF involves non-blocking
switching 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 paper
Using 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 and
displays Remote Link Director information. Information in the Remote SymmID column shows that
Symmetrix 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
Symmetrix ID: 000000003264 (Local)
S Y M M E T R I X
R D F
Remote
SymmID
Ident Symbolic Numeric Slot Type

RA-3A
RA-3B
03A
03B
3
19
3
3
D I R E C T O R S
RDF-BI-DIR 000000003265
RDF-BI-DIR 000000003265
Local
RA Grp
Remote
RA Grp
Status
2 (B)
2 (B)
2 (B)
2 (B)
Online
Online
Local
RA Grp
Remote
RA Grp
Status
1 (A)
1 (A)
1 (A)
1 (A)
Online
Online
Remote
RA Grp
Status
Symmetrix ID: 000000003263 (Remote)

S Y M M E T R I X
R D F
Remote
SymmID

RA-3A
RA-3B
03A
03B
3
19
3
3
D I R E C T O R S
RDF-BI-DIR 000000003265
RDF-BI-DIR 000000003265
Symmetrix ID: 000000003265 (Remote)

S Y M M E T R I X
R D F
D I R E C T O R S
Remote
SymmID
RA-3A
RA-14A
RA-3B
RA-14B
000000003263
000000003264
000000003263
000000003264
03A
14A
03B
14B
3
14
19
30
3
14
3
14
RDF-BI-DIR
RDF-BI-DIR
RDF-BI-DIR
RDF-BI-DIR
Local
RA Grp
1
2
1
2
(A)
(B)
(A)
(B)
1
2
1
2
(A)
(B)
(A)
(B)
Online
Online
Online
Online
Figure 1 illustrates that an RA adapter can be the interface to an RDF link between Symmetrix systems. In
this 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 group
numbers 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.
DATE: 03/11/02
R1
RA Group 2
R2
Host
RA Group 1
Local Symmetrix
3264
R1
BCV
R2
Remote Symmetrix
3265
Remote Symmetrix
3263
CLI-000019
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 of
options, 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 Devices

SYMCLI provides two commands to list the devices on a Symmetrix unitone 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 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. To
display devices on a remote Symmetrix unit, include the sid option with the identifier of the remote
Symmetrix unit. The ellipsis () indicates where output was omitted. The first column contains a devices
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.
DATE: 03/11/02
symdev list
Symmetrix ID: 000000003264
Device Name
Directors
Device
--------------------------- ------------ -------------------------------------Cap
Sym Physical
SA :P DA :IT Config
Attribute
Sts
(MB)
--------------------------- ------------ -------------------------------------000 Not Visible
16A:0 01A:C0 Unprotected
N/Grp'd (M) RW
1031
001 Not Visible
16A:0 02B:D3 Unprotected
N/Grp'd (M) RW
1031
002 Not Visible
???:? 02A:C0 Unprotected
N/Grp'd
RW
516
003 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
516
16B:0 02A:C0 2-Way Mir
N/Grp'd
RW
516
16B:0 01B:C0 2-Way Mir
N/Grp'd
RW
516
16B:0 02B:C0 2-Way Mir
N/Grp'd
RW
516
16B:0 01A:D0 2-Way BCV Mir N/Asst'd
RW
516
RW
516
08A /dev/rdsk/c4t1d2s2
16B:0 01B:D0 2-Way BCV Mir N/Asst'd
RW
516
08B /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 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 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 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 list command include multiport and firstport, which
display devices mapped to multiple front-end adapter ports or to just the first port of information for devices
mapped to more than one port, respectively. Refer to Example 3: Obtaining More Device Information for
displays using these options.
The partial sympd list output below displays the same information as the symdev list output but
only for devices that are visible to the host, listing physical device names in the first column. Any device
with a 3-megabyte (MB) capacity is a configured gatekeeper device. Note that the Not Visible devices
from the previous symdev list display are omitted from this display. N/Grpd means that a standard
device does not currently belong to a device group. N/Asstd means that a BCV does not belong to (is not
associated with) a device group.
sympd list
Device Name
Directors
Device
--------------------------- ------------ -------------------------------------Cap
Physical
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. For
example, 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
---------------------------- ------------ ------------------------------------Cap
Physical
Attribute
Sts
(MB)
---------------------------- ------------ ------------------------------------/dev/rdsk/emcpower0c
041C
02A:D3 Unprotected
/dev/vx/rdmp/c4t0d114s2
- 12B:0
- /dev/rdsk/c4t0d114s2
- 05B:0
- 12B:0
- -
N/Grp'd
-
RW
-
5754
-
/dev/rdsk/emcpower1c
041D
15B:D3 Unprotected
- 12B:0
- 05B:0
- 12B:0
- -
Grp'd
-
RW
-
8632
-
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
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 SRDF devices or BCV devices or both to add to a device 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 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 devices
configured as capable of being only dynamic R1 devices. When combined with the
r2 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 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 Not
Visible to this host. N/Asstd means the devices are not associated with any existing device group.
symdev list -r1 -bcv
Device Name
Directors
Device
--------------------------- ------------ -------------------------------------Cap
Sym Physical
SA :P DA :IT Config
Attribute
Sts
(MB)
--------------------------- ------------ -------------------------------------2E0 Not Visible
2E1 Not Visible
2E2 Not Visible
???:? 15A:D5 RDF1-BCV

???:? 02A:C5 RDF1-BCV
???:? 02A:D5 RDF1-BCV
N/Asst'd
N/Asst'd
N/Asst'd
RW
RW
RW
4315
4315
4315
The following symdev list 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.
However, if you were to invoke the same command from a remote host connected to Symmetrix 505, the
viewpoint and display would change. From the remote hosts viewpoint, these devices are visible.
symdev list sid 505 -bcv
Device Name
Directors
Device
--------------------------- ------------ -------------------------------------Cap
Sym Physical
SA :P DA :IT Config
Attribute
Sts
(MB)
--------------------------- ------------ -------------------------------------2E0 Not Visible
2E1 Not Visible
2E2 Not Visible
???:? 16B:D5 BCV

???:? 15B:D5 BCV
???:? 02B:D5 BCV
N/Asst'd
N/Asst'd
N/Asst'd
RW
RW
RW
4315
4315
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 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 is
configured. With Enginuity version 5568 and the introduction of full-fledged dynamic RDF, non-SRDF devices are configured such
that they can become dynamic SRDF pairs when you use the symrdf createpair command.
10
DATE: 03/11/02
device 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 0064
Device Physical Name
: Not Visible
Device Symmetrix Name

Device Serial ID
Symmetrix ID
: 0064
: N/A
: 000185500814
Device Group Name

Device Logical Name
: sar
: BCV001
Vendor ID
Product ID
Product Revision
: EMC
: SYMMETRIX
: 5568
Device
Device
Device
Device
Emulation Type
:
Defined Label Type:
Defined Label
:
Sub System Id
:
Device Block Size

Device Capacity
{
Cylinders
Tracks
512-byte Blocks
MegaBytes
KiloBytes
}
Device Configuration
FBA
N/A
N/A
0x0140
: 512
:
:
:
:
:
9206
138090
8837760
4315
4418880
: 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, the
service 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 when
checking the read/write status on the SA are Not Ready, Write Disabled, or Ready.
Device SA Status
: N/A
(N/A)
11
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 Status
of Not Ready means that the part of the physical disk to which BCV 0064 is mapped is not currently
accessible for 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 Disk Director Information
{
Hyper Type
Hyper Status
Disk [Director, Interface, TID]
Disk Director Volume Number
Hyper Number
Disk Capacity
Hyper Type
Hyper Status
Disk [Director, Interface, TID]
Disk Director Volume Number
Hyper Number
}
:
:
:
:
:
:
Data
Not Ready
[16A, C, 1]
25
8
70007m
:
:
:
:
:
R2 Remote
Not Ready
[N/A,N/A,N/A]
N/A
N/A
(NR)
(NR)
The BCV Pair Information section shows that BCV 0064 is paired with local standard device 0000.
BCV Pair Information
{
Standard (STD) Device Symmetrix Name
Standard (STD) Device Serial ID
Standard (STD) Device Group Name
BCV Device Symmetrix Name
BCV Device Serial ID
BCV Device Associated Group Name
: 0000
: 14000000
: sar
: 0064
: Not Visible
: 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 Device Status
: Not Ready
(NR BCV)
State of Pair ( STD ====> BCV )

Time of Last BCV Action
: Synchronized
: Fri Oct 12 13:42:05 2001
The BCV State Flags: (inc) means that, on the next split operation, data from the BCVs moving mirror
will 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

Number of Inv. Tracks for BCV Device
}
: 0
: 0
The RDF Information section of this display shows that BCV 0064 is also configured as an SRDF pair with
a remote R2 device (0218) on the remote Symmetrix (sid 505).
12
DATE: 03/11/02
RDF Information
{
Device Symmetrix Name
RDF Type
RDF (RA) Group Number
: 0064
: R1
: 2
Remote Device Symmetrix Name

Remote Symmetrix ID
: 0218
: 000185500505
RDF
RDF
RDF
RDF
:
:
:
:
Mode
Adaptive Copy
Adaptive Copy Write Pending State
Adaptive Copy Skew (Tracks)
(B)
Synchronous
Disabled
N/A
65535
RDF Device Domino
: Disabled
RDF Link Configuration

RDF Link Domino
Prevent Automatic RDF Link Recovery
Prevent RAs Online Upon Power ON
:
:
:
:
Direct Escon Fibre

Disabled
Disabled
Enabled
Device RDF Status: Ready is specific to the R1 side, which is almost always Ready except when a device
is 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 devices RDF link to the remote R2 device is currently suspended.
Device RDF Status
: Ready
(RW)
Device SA Status
Device RA Status
Device Link Status
: N/A
: Ready
: Not Ready
(N/A)
(RW)
(NR)
Device Suspend State: N/A means that the device does not belong to an enabled consistency group or that
it does but is synchronized and does not have an R1 suspend state. If the device is part of a tripped
consistency group, its 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
Device Consistency State
: N/A
: Disabled
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 pairing
relationship 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 copying
data to its R2 device. Remote Device RDF State means that the remote R2 device (0218) is write disabled
to its host.
Device RDF State
Remote Device RDF State
RDF Pair State ( R1 <-
: Not Ready
: Write Disabled
-> R2 )
(NR)
(WD)
: Suspended
The resolution of invalid tracks depends on which operation you perform. For instance, you can have remote
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.
13
DATE: 03/11/02
Number of R1 Invalid Tracks

: 0
: 0
}
Figure 2 shows that BCV 0064 (the device previously displayed) is paired with local standard device 0000
as a BCV pair and with standard device 0218 as an SRDF pair. At the time of the show display, BCV 0064
was synchronized with standard 0000 and suspended from standard 0218.
0000
Standard
BCV Pair
Host
0064
Source
(R1)
RDF BCV
SRDF
Pair
Local Symmetrix
814
0218
Target
(R2)
Standard
Remote Symmetrix
505
CLI-000017
Figure 2. Symmetrix Configuration for the symdev show 0064 Command
Displaying Information about SRDF Devices

In an SRDF configuration, you can examine the devices on your local Symmetrix to determine which are
source devices (Sym Dev), which are remote target devices (RDev), and whether a device is an R1 or R2
type device. The symrdf list 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
Local Device View
------------------------------------------------------------------------------STATUS
M O D E S
RDF S T A T E S
Sym
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
Suspended
046 046
R2:2 ?? WD NR SYN DIS OFF
0
33000 WD RW
Suspended
047 047
R2:2 ?? WD NR SYN DIS OFF
- WD RW
Suspended
09C 054
R1:2 RW RW RW SYN DIS OFF
0
0 RW NR
Synchronized
09D 055
0
0 RW NR
Synchronized
09E 056
0
0 RW NR
Synchronized
09F 057
0
0 RW NR
Synchronized
0A0 058
R1:2 RW RW RW ACp DIS WP
0
0 RW NR
Synchronized
0A1 059
R1:2 RW RW RW ACp DIS WP
0
0 RW NR
Synchronized
14
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) 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 links
are 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 Invalid Tracks column indicates the number of tracks that have been written to the R2 side since the
suspension 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 Adaptive
Copy 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-visible
devices 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 as
just the R1 devices, R2 devices, BCV devices, or standard devices. For a complete list of options for this
command, 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 option
to display devices that are configured as concurrent RDF pairs. For example:
symrdf list -sid 77 -concurrent
Local Device View
------------------------------------------------------------------------------STATUS
M O D E S
RDF S T A T E S
Sym
RDF
--------- ------------ R1 Inv
--- ---- ----- --------- ------------ ----------- --- ---- -------------028
050
0
0 RW WD
Synchronized
000
0
0 RW WD
Synchronized
029 051
0
0 RW WD
Synchronized
001
0
0 RW WD
Synchronized
The display shows an R1 source device (028) paired with two R2 target devices (050 and 000); Symmetrix
device 029 is paired concurrently with devices 051 and 001. Note that each of the two concurrent 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 dynamic
option to display SRDF pairs whose devices have been configured as dynamic SRDF devices. With
Enginuity version 5567, the following display shows SRDF devices that have been configured for dynamic
swap (fast swap).
15
DATE: 03/11/02
symrdf list -dynamic

Local Device View
------------------------------------------------------------------------------STATUS
M O D E S
RDF S T A T E S
Sym
RDF
--------- ------------ R1 Inv
--- ---- ----- --------- ------------ ----------- --- ---- -------------072 092
0
0 RW WD
Synchronized
073 093
0
0 RW WD
Synchronized
074 094
0
0 RW WD
Synchronized
With Enginuity version 5568, this display will show devices configured for RDF use and created as dynamic
SRDF 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 symrdf
list dynamic command(both, r1, or r2). Including the both option displays dynamic
SRDF pairs in which the paired devices can be either R1 or R2 devices (a requirement for dynamic R1/R2
swap). Including the r1 option displays only dynamic SRDF pairs in which R1 devices cannot become R2
devices. Including the r2 option displays only R2 devices that cannot become R1 devices. Omitting all
three of these options displays all dynamic SRDF pairs, regardless of their device configurations.
Displaying Information about BCV Devices

Information 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 SYMAPI
database 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 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 device that does not belong to
the device group.
Figure 3 shows that while the standard device 084 and BCV 089 are members of the same device group, the
record in the Symmetrix indicates that the same standard device 084 was last paired with BCV 088 and still
has a pairing relationship with that device. Any attempt to establish an 084/089 pair would fail without the
use of a preferred pair attachment or symmir full establish command options that override the
standards prior pairing relationship with BCV 088.
16
DATE: 03/11/02
Device group
Standard/BCV
definitions
pairing
stored in
information BCV
BCV
STD
SYMAPI
stored in
089
084
088
database
Symmetrix
on host
Host
Symmetrix
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 is
relatively 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 to
an 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
Device Name
Directors
Device
--------------------------- ------------ -------------------------------------Cap
Sym Physical
SA :P DA :IT Config
Attribute
Sts
(MB)
--------------------------- ------------ -------------------------------------088 /dev/rdsk/c4t1d0s2
RW
516
RW
516
08A /dev/rdsk/c4t1d2s2
16B:0 01B:D0 2-Way BCV Mir Asst'd
RW
516
08B /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 means
that BCVs 088 and 089 are not associated with a device group. To determine which device group BCVs 08A
and 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:
17
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 NeverEstab
Not Visible
031
(m)
- N/A
N/A
- NeverEstab
c4t1d0s2
088
0 c4t0d0s2
084
0 Split
c4t1d1s2
089
0 c4t0d1s2
085
0 Split
c4t1d2s2
08A
0 c4t0d2s2
086
0 Split
c4t1d3s2
08B
0 c4t0d3s2
087
0 Split
The Split status of BCVs 088, 089, 08A, and 08B means that these devices have a current pairing
relationship with a standard device (084, 085, 086, and 087, respectively). To establish one of these BCVs
with a different standard device would require a symmir command that explicitly overrides the current
pairing relationship.
The display also shows two BCVs (030 and 031) that are not visible to the host and do not have a current
pairing 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 Group

A device group is a user-defined entity that you can use to represent and manage multiple devices. When
you initially create a device group and add devices to it, membership information about the group is stored
in your hosts SYMAPI database file. When BCV pairs or SRDF pairs are established, their pairing status is
stored in Symmetrix global memory. Various SYMCLI commands access both sources of information to
display 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 your
hosts SYMAPI database file. The symdg show DgName command displays the membership and
configuration details of any existing device group2. For example, the following display of an RDF1 type
device group named RDFGrp1 shows that the group includes 7 local standard devices, 7 locally associated
BCVs, and 7 remotely associated BCVs (devices located on a remote Symmetrix unit but associated with the
device 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 is
dedicated to the standard devices in this device group.
symdg show RDFGrp1
Group Name:
RDFGrp1
Group Type
Valid
Symmetrix ID
Group Creation Time
:
:
:
:
REGULAR
Yes
000185500814
Tue Oct 16 09:49:41 2001
The symcg list and symcg show commands display the same information for an SRDF consistency group.
18
DATE: 03/11/02
Vendor ID
Application ID
Number
Number
Number
Number
Number
of
of
of
of
of
: EMC Corp
: SYMCLI
STD Devices in Group

:
Associated GK's
:
Locally-associated BCV's
:
Remotely-associated BCV's (STD RDF):
Remotely-associated BCV's (BCV RDF):
7
1
7
0
7
Standard (STD) Devices (7):

{
-------------------------------------------------------------------Sym
Cap
LdevName
PdevName
Dev Att. Sts
(MB)
-------------------------------------------------------------------DEV001
/dev/vx/rdmp/c4t0d107s2 03F7
RW
1031
DEV002
/dev/vx/rdmp/c4t0d108s2 03F8
RW
1031
DEV003
03F9
RW
1031
DEV004
03FA
RW
1031
DEV005
03FB (M) RW
4125
DEV006
03FF (M) RW
4125
DEV007
0403 (M) RW
4125
}
Associated GateKeeper Devices (1):
{
-------------------------------------------------------------------Sym
Cap
LdevName
PdevName
Dev
Sts
(MB)
-------------------------------------------------------------------N/A
025B
RW
3
}
BCV Devices Locally-associated (7):
{
-------------------------------------------------------------------Sym
Cap
LdevName
PdevName
Dev Att. Sts
(MB)
-------------------------------------------------------------------BCV001
N/A
0407
NR
1031
BCV002
N/A
0408
NR
1031
BCV003
N/A
0409
NR
1031
BCV004
N/A
040A
NR
1031
BCV005
N/A
040B (M) NR
4125
BCV006
N/A
040F (M) NR
4125
BCV007
N/A
0413 (M) NR
4125
}
BCV Devices Remotely-associated (BCV RDF) (7):
{
-------------------------------------------------------------------Sym
Cap
LdevName
PdevName
Dev Att. Sts
(MB)
-------------------------------------------------------------------BRBCV001
N/A
03A0
RW
1031
BRBCV002
N/A
03A1
RW
1031
BRBCV003
N/A
03A2
RW
1031
19
DATE: 03/11/02
BRBCV004
BRBCV005
BRBCV006
BRBCV007
}
N/A
N/A
N/A
N/A
03A3
03A4 (M)
03A8 (M)
03AC (M)
Standard
R2
R1
BCV
BRBCV
Local Symmetrix
814
Remote Symmetrix
505
RW
RW
RW
RW
1031
4125
4125
4125
Host
CLI-000018
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 4-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 groups 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.
Device Group BCV RDF Information
{
RDF Type
: R1
: 2
Remote Symmetrix ID
: 000185500505
RDF
RDF
RDF
RDF
:
:
:
:
Mode
Adaptive Copy
(B)
Synchronous
Disabled
N/A
65535
RDF Device Domino
: Disabled

RDF Link Domino
: Direct Escon Fibre

: Disabled
Prior to Enginuity version 5568, a Symmetrix device name is a 3-digit hexadecimal number.
20
DATE: 03/11/02

: Disabled
: Enabled
Device RDF Status
: Ready
(RW)
Device RA Status
Device Link Status
: Ready
: Not Ready
(RW)
(NR)

RDF R2 Not Ready If Invalid
: Offline
: Disabled
: Enabled
Device RDF State

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

}
: 0
: 0
(NR)
(RW)
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 consistency group. Querying a
TimeFinder device group displays the state of BCV pairs in a Symmetrix unit. Querying an SRDF device
group or consistency group displays the state of SRDF pairs in a configuration in which data copying occurs
over RDF links. Table 3 lists several often used commands that use the query argument.
Table 3. Useful query Commands
Query Command
Displays
symmir 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 after
an 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 be
copied from the standard device). An asterisk (*) next to the BCVs device name means that the BCV
belongs to the device group. If the asterisk is absent, the BCV is outside the device group.
symmir -g ProdBgrp query
Device Group (DG) Name: ProdBgrp
DG's Type
: REGULAR
DG's Symmetrix ID
: 000000003264
Standard Device
BCV Device
State
------------------------- ------------------------------------ -----------Inv.
Inv.
Logical
Sym Tracks Logical
Sym
Tracks STD <=> BCV
------------------------- ------------------------------------ -----------DEV001
DEV002
DEV003
DEV004
084
085
086
087
0
0
0
0
BCV001
BCV002
BCV003
BCV004
088
089
08A
08B
*
*
*
*
0
0
414
627
Synchronized
Synchronized
SyncInProg
SyncInProg
21
DATE: 03/11/02
Total
Track(s)
MB(s)
------0
0.0
------1041
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 and
BCV004, a symmir query command with the multi 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 DEV001s new pairing relationship with those BCVs.
symmir -g ProdBgrp query -multi
Device Group (DG) Name: ProdBgrp
DG's Type
: REGULAR
DG's Symmetrix ID
: 000000003264
Standard Device
BCV Device
State
------------------------- ------------------------------------ -----------Inv.
Inv.
Logical
Sym Tracks Logical
Sym
Tracks STD <=> BCV
------------------------- ------------------------------------ -----------DEV001
084
DEV002
085
Total (Primary)
Track(s)
MB(s)
0
0
8
0
BCV003
BCV004
BCV001
BCV002
08A
08B
088
089
-----0
0.0
* 138090 SyncInProg
* 138090 SyncInProg
*
0 Split
*
0 Split
------138090
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: Rdf1Grp
DG's Type
: RDF1
DG's Symmetrix ID
: 000000003264
Source (R1) View
Target (R2) View
M O D E S
22
DATE: 03/11/02
------------------------------------------------ST
LI
ST
Standard
A
N
A
Logical
T R1 Inv R2 Inv K
T R1 Inv R2 Inv
Device Dev E Tracks Tracks S Dev E Tracks Tracks
----------------------------- -- --------------------DEV001
DEV002
09C RW
09D RW
Total
Track(s)
MB(s)
0
0
0 RW 054 NR
830 RW 055 NR
------- ------0
0
0.0
0.0
0
0
----------M
o
d
e
Dom ACp
-----------
------------
RDF Pair
STATE
------------
0 SYN DIS OFF Synchronized

0 SYN DIS OFF SynchInProg
------- ------0
0
0.0
0.0
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 in synchronous mode (indicated by SYN in the Mode column). One
of the SRDF pairs is fully synchronized and one is still in the process of synchronizing. On the SyncInProg
pair, 830 R2 invalid tracks on the source (R1) side still remain to be copied to the target device (055) to
complete the synchronization process. The R2 invalid tracks on the R1 side represent those tracks that are
still 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.
23
DATE: 03/11/02
Example 1: Verifying that Configuration Information in

the SYMAPI Database Shows the Current Configuration
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 symcfg discover command builds or rebuilds your hosts 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
This operation may take up to a few minutes. Please be patient...
The symcfg list command displays the configuration information from the local hosts SYMAPI
database file.
# symcfg list
S Y M M E T R I X
SymmID
Attachment
000185500814 Local
000185500505 Remote
Model
Mcode
Version
8230
8230
5568
5568
Cache
Size (MB)
4096
8192
Num Phys
Devices
728
0
Num Symm
Devices
1085
970
The symcfg verify 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_IN_SYNC). If they
are in sync, the verify action returns code zero (the CLI_C_SUCCESS value) as shown below using the
echo $status command.
# symcfg verify -sid 814
The Symmetrix configuration and the database file are in sync.
# echo $status
0
A new device is now added to local Symmetrix 814, changing the configuration. The verify action is
repeated, and its output shows an out-of-sync condition. The echo $status command returns the value
24, 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 $status
24
24
DATE: 03/11/02
The symcfg discover command rebuilds your hosts SYMAPI database file with the most current
information.
# 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 hosts
rebuilt SYMAPI database file. Note that the number of Symmetrix devices displayed for Symmetrix 814 has
increased from 1085 (shown in the previous symcfg list) to 1086.
# symcfg list
S Y M M E T R I X
SymmID
Attachment
000185500814 Local
000185500505 Remote
Model
Mcode
Version
8230
8230
5568
5568
Cache
Size (MB)
4096
8192
Num Phys
Devices
728
0
Num Symm
Devices
1086
970
The symcfg verify command confirms that the configuration and SYMAPI database file are now in
sync again.
The Symmetrix configuration and the database file are in sync.
25
DATE: 03/11/02
Example 2: Obtaining More Symmetrix Information

This 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 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
Symmetrix ID : 000185500814
Symmetrix
------------Director Port
-------- ----
Host
----------------------------------------------------------Node Name
IP Address
HW Type OS Name OS Revision
------------- --------------- -------- -------- -----------
DA-1A
SA-4A
SA-13A
SA-4B
FA-5B
FA-12B
hk185500814
api183
api183
api212
api179
api179
0
0
0
0
0
0
172.26.131.103
172.23.65.183
172.23.65.183
172.23.65.212
172.23.65.179
172.23.65.179
INTEL
9000/800
9000/800
9000/800
sun4u
sun4u
WinNT
HPUX
HPUX
HPUX
SunOS
SunOS
4.0.1381
B.11.00
B.11.00
B.11.00
5.8
5.8
Using the sorthost option with the connections option and symcfg list 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
------------------------------------------------Node Name
IP Address
OS Name OS Revision
------------ --------------- -------- -----------
Symmetrix
-------------------------ID
Director Port
------------ -------- ----
hk185500814
172.26.131.103
WinNT
4.0.1381
000185500814 DA-1A
api179
172.23.65.179
SunOS
5.8
000185500814 FA-5B
0
000185500814 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
symcfg list lock 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
SymmID
Attachment
000185500814 Local
000185500505 Remote
L O C K S
Lock
Status
Lock
Number
Time
Held (Sec)
Unlocked
Unlocked
N/A
N/A
N/A
N/A
26
DATE: 03/11/02
Using the lockn option with symcfg list 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 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 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
SymmID
Attachment
000185500814 Local
000185500505 Remote
L O C K S
Lock
Status
Lock
Number
Time
Held (Sec)
Locked
Locked
0
0
8
8
Using the applications option with symcfg list 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 connections
option is not listed here if it has never accessed the Symmetrix unit.
# symcfg list -applications
Symmetrix ID
: 000185500814
Host
---------------------------Node Name
IP Address
------------ ---------------
Application
-----------------------------------------------ID
Vendor ID
Version
Attr
---------------- ---------------- --------------
api179
172.23.65.179
SYMCLI
SYMCLI
EMCpower
SYMCLI
SYMCLI
EMC
EMC
EMC
EMC
EMC
api180
172.23.65.180
SYMCLI
EMC Corp
hk185500814
172.26.131.103
OPTIMIZER
EMC Corp
Corp
Corp
Corp
Corp
Corp
5.0.0.1
5.0.0.0
2.1.0.0
5.0.0.32
5.0.0.29
5.0.0.32 (R)
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), 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 Proc.
ID
Key
State
Type Wait Lock Full Path Specification
------ ---------- -------- ---- ----- ----------------------------
27
DATE: 03/11/02
1
3
1
0
0x45000327
0x45000ba7
0x45000327
0x45000246
Unlocked
Unlocked
Unlocked
Unlocked
GK
GK
DB
FILE
0
0
0
0
/dev/rdsk/c4t0d103s2
/var/symapi/db/symapi_db.bin
/var/symapi/config/symapislck
Using the services option with symcfg list 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
Port
Name
Domain Type
Node Name
Address
Number
------------ ------ -------- -------------------- --------------- -----api182
TCPIP
api182
172.23.65.182
2707
28
DATE: 03/11/02
Example 3: Obtaining More Device Information

This 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 operations
and SRDF pairs during SRDF control operations. The following command displays external locks on
standard 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
Device
Sym Physical
Number Holder ID Held
Flags Attribute
---------------------------- ----------------------------------------------03F7
03F8
03F9
03FA
9
9
9
9
0x10010FE6
0x10010FE6
0x10010FE6
0x10010FE6
111
111
111
111
Long
Long
Long
Long
Grp'd
Grp'd
Grp'd
Grp'd
Using the multiport option with the symdev list 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
M U L T I - P O R T
D E V I C E S
Device Name
Directors
Device
---------------------------- ------------ ------------------------------------Cap
Physical
Attribute
Sts
(MB)
---------------------------- ------------ ------------------------------------0000
16B:D1 2-Way Mir
Grp'd
RW
4315
- 12B:0
- /dev/vx/rdmp/c5t0d0s2
- 12B:0
- /dev/rdsk/emcpower116c
- 05B:0
- 05B:0
- 12B:0
- -
/dev/rdsk/c4t0d1s2
/dev/rdsk/c5t0d1s2
0001
-
12B:0
12B:0
05B:0
05B:0
12B:0
02B:D1
-
2-Way Mir
-
Grp'd
-
RW
-
29
4315
-
DATE: 03/11/02
0002
01B:D1 2-Way Mir
Grp'd
RW
4315
- 12B:0
- /dev/vx/rdmp/c5t0d2s2
- 12B:0
- /dev/rdsk/emcpower118c
- 05B:0
- 05B:0
- 12B:0
-
Not Visible
Not Visible
00C8
01A:C2 RDF2+Mir
- 05A:0
- - 12A:0
- -
N/Grp'd
-
WD
-
4315
-
Not Visible
Not Visible
00C9
15A:C2 RDF2+Mir
- 05A:0
- - 12A:0
- -
N/Grp'd
-
WD
-
4315
-
Using the firstport option with the symdev list command displays just the first port of
information for devices that are mapped to multiple ports.
# symdev list -firstport
Device Name
Directors
Device
---------------------------- ------------ ------------------------------------Cap
Sym Physical
SA :P DA :IT Config
Attribute
Sts
(MB)
---------------------------- ------------ ------------------------------------0000 /dev/vx/rdmp/c4t0d0s2
12B:0 16B:D1 2-Way Mir
Grp'd
RW
4315
0001 /dev/vx/rdmp/c4t0d1s2
Grp'd
RW
4315
Grp'd
RW
4315
12B:0 16A:D1 2-Way Mir
Grp'd
RW
4315
Grp'd
RW
4315
Grp'd
RW
4315
Using the resv option with the sympd list command displays all Symmetrix devices that have
SCSI reservations.
# sympd list -resv
Device Name
Device
Reservation
---------------------------- ------------- -----------------Physical
Sym Config
Initiator SA :P
---------------------------- ------------- -----------------/dev/rhdisk20
0018 2-Way Mir
07
01C:0
30
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. "Cap
MB" 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
Cap
Size
Devs
(MB)
---------------------------- ---------------------- --------------------------0268
026A
026D
0270
0272
0275
03C7
03C8
03D3
03D6
03D7
03D8
03DF
03E0
03E2
03E5
03F4
03F5
03FB
03FF
0403
040B
040F
0413
Not Visible
Not Visible
Not Visible
Not Visible
Not Visible
Not Visible
Not Visible
Not Visible
Not Visible
Not Visible
Not Visible
Not Visible
Not Visible
Not Visible
Not Visible
Not Visible
Not Visible
Not Visible
Not Visible
Not Visible
Not Visible
RDF2+Mir
RDF2+Mir
RDF2+Mir
BCV
BCV
BCV
Unprotected
Unprotected
Unprotected
Unprotected
BCV
BCV
BCV
BCV
BCV
BCV
BCV
BCV
2-Way Mir
2-Way Mir
2-Way Mir
RDF1-BCV+Mir
RDF1-BCV+Mir
RDF1-BCV+Mir
N/Grp'd
N/Grp'd
N/Grp'd
N/Asst'd
N/Asst'd
N/Asst'd
N/Grp'd
N/Grp'd
N/Grp'd
N/Grp'd
N/Asst'd
N/Asst'd
N/Asst'd
N/Asst'd
N/Asst'd
N/Asst'd
N/Asst'd
N/Asst'd
Grp'd
Grp'd
Grp'd
Asst'd
Asst'd
Asst'd
Concated
Striped
Striped
Concated
Striped
Striped
Striped
Striped
Concated
Striped
Striped
Concated
Striped
Striped
Striped
Striped
Concated
Striped
Striped
Concated
Striped
Striped
Concated
Striped
960k
3840k
960k
3840k
1920k
7680k
30720k
1920k
7680k
1920k
30720k
7680k
30720k
7680k
15360k
7680k
15360k
2
3
3
2
3
3
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
31
17263
25895
25895
17263
25895
25895
4125
4125
4125
4125
4125
4125
4125
4125
4125
4125
4125
4125
4125
4125
4125
4125
4125
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) on
the failed disk against which the hot spare was invoked, are shown in the symdev list hotspare
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 to mirror the spare hyper. On the other
hand, mirrored devices stay ready (RW) when a hot spare is invoked against them.
# symdev list -hotspare
Could not select any Symmetrix devices to list.
Device Name
Directors
Device
---------------------------- ------------ ------------------------------------Cap
Sym Physical
SA :P DA :IT Config
Attribute
Sts
(MB)
---------------------------- ------------ ------------------------------------0010
0098
00AE
00C7
00DF
00F5
0108
Not
Not
Not
Not
Not
Not
Not
Visible
Visible
Visible
Visible
Visible
Visible
Visible
???:?
???:?
13A:0
???:?
???:?
???:?
???:?
01A:D0
01A:D0
01A:D0
01A:D0
01A:D0
01A:D0
01A:D0
Unprotected
Unprotected
2-Way Mir
Unprotected
Unprotected
Unprotected
2-Way Mir
N/Grp'd
N/Grp'd
N/Grp'd
N/Grp'd
N/Grp'd
N/Grp'd
N/Grp'd
NR
NR
RW
NR
NR
NR
RW
32
103
47
4315
47
47
47
469
DATE: 03/11/02
Example 4: Obtaining Information about Dynamic SRDF

Devices
This example examines a local source Symmetrix unit (sid 810) connected via RDF links to a remote
Symmetrix unit (sid 506). Both Symmetrix units are running Enginuity version 5568. The example shows
how to display devices that are configured for RDF capability. These devices can be used to create dynamic
SRDF 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
SymmID
Attachment
000185500810 Local
000185500506 Remote
Model
Mcode
Version
Cache
Size (MB)
8430
8430
5568
5568
32760
32760
Num Phys
Devices
198
0
Num Symm
Devices
325
326
With Enginuity version 5568 and higher, the symdev list command with the dynamic option
displays devices that have been created as, or are capable of being created as, dynamic SRDF devices using
the symrdf createpair command. Devices on Symmetrix 810 that are visible to the host are capable
of being dynamically paired as either R1 or R2 devices. When combined with the r1 option, symdev
list 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 the
display have already been created as dynamic R1 devices, but are still capable of being either an R1 or R2
device (a requirement for dynamic R1/R2 swap).
# symdev list -dynamic -sid 810
Device Name
Directors
Device
---------------------------- ------------ ------------------------------------Cap
Sym Physical
SA :P DA :IT Config
Attribute
Sts
(MB)
---------------------------- ------------ ------------------------------------00F2
00F5
00FA
0106
010A
010F
0145
0146
0147
0148
0149
014A
014B
Not Visible
Not Visible
Not Visible
Not Visible
Not Visible
Not Visible
Not Visible
04A:0
04A:0
04A:0
04A:0
04A:0
04A:0
04A:0
04A:0
04A:0
04A:0
04A:0
04A:0
04A:0
15B:C4
01A:D1
15A:C4
01B:D3
15A:D3
02B:C2
01A:C1
15A:C1
02A:C1
15A:D1
02A:D1
16B:C4
02B:C4
Unprotected
Unprotected
Unprotected
Unprotected
Unprotected
Unprotected
RDF1+Mir
RDF1+Mir
RDF1+Mir
RDF1+Mir
3-Way Mir
3-Way Mir
3-Way Mir
N/Grp'd
N/Grp'd
N/Grp'd
N/Grp'd
N/Grp'd
N/Grp'd
N/Grp'd
N/Grp'd
N/Grp'd
N/Grp'd
N/Grp'd
N/Grp'd
N/Grp'd
RW
RW
RW
RW
RW
RW
RW
RW
RW
RW
RW
RW
RW
33
2063
2063
2063
2063
2063
2063
2063
2063
2063
2063
2063
2063
2063
DATE: 03/11/02
Example 5: Obtaining More Device Group Information

This 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 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 RDFGrp2
Group Name:
RDFGrp2
Group Type
Valid
Symmetrix ID
Group Creation Time
Vendor ID
Application ID
Number
Number
Number
Number
Number
of
of
of
of
of
:
:
:
:
:
:
STD Devices in Group

:
Associated GK's
:
Locally-associated BCV's
:
Remotely-associated BCV's (STD RDF):
Remotely-associated BCV's (BCV RDF):
RDF1
Yes
000185500814
Thu Nov 29 14:11:05 2001
EMC Corp
SYMCLI
5
0
0
5
0
Standard (STD) Devices (5):

{
-------------------------------------------------------------------Sym
Cap
LdevName
PdevName
Dev Att. Sts
(MB)
-------------------------------------------------------------------DEV001
/dev/vx/rdmp/c4t0d102s2 03C2
RW
4315
DEV002
RW
4315
DEV003
RW
4315
DEV004
RW
4315
DEV005
RW
4315
}
BCV Devices Remotely-associated (STD RDF) (5):
{
-------------------------------------------------------------------Sym
Cap
LdevName
PdevName
Dev Att. Sts
(MB)
-------------------------------------------------------------------RBCV001
N/A
02E0
RW
4315
RBCV002
N/A
02E1
RW
4315
RBCV003
N/A
02E2
RW
4315
RBCV004
N/A
02E3
RW
4315
RBCV005
N/A
02E4
RW
4315
}
34
DATE: 03/11/02
This second part of the symdg show output displays the device groups RDF information, including the
identity of the remote Symmetrix unit (sid 505), RDF configuration settings (Enabled or Disabled), and the
combined state of all standard RDF devices in the group and their RDF links (ReadyRead/Write enabled or
Write Disabled).
Device Group RDF Information
{
RDF Type
: R1
: 2
Remote Symmetrix ID
: 000185500505
RDF
RDF
RDF
RDF
:
:
:
:
Mode
Adaptive Copy
(B)
Adaptive Copy
Enabled: Disk Mode
N/A
65535
RDF Device Domino
: Disabled

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

RDF R2 Not Ready If Invalid
: N/A
: Disabled
: Enabled
Device RDF State

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

}
Direct Escon Fibre

Enabled
Enabled
Enabled
(RW)
(WD)
: 0
: 0
35
DATE: 03/11/02
It is possible to get device configuration and status information about devices by querying the device group
to which they have been added. The symmir 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 pair is
currently in the Split state.
# symmir -g Rdf1Grp query
DG's Type
: RDF1
DG's Symmetrix ID
: 000185500810
Standard Device
BCV Device
State
-------------------------- ------------------------------------- -----------Inv.
Inv.
Logical
Sym Tracks Logical
Sym
Tracks STD <=> BCV
-------------------------- ------------------------------------- -----------DEV001
010F
Total
MB(s)
0 BCV001
00CD *
------0.0
0 Split
------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 source
device (010F) is currently suspended from its R2 target device (00BF).
# symrdf -g Rdf1Grp query
DG's Type
: RDF1
DG's Symmetrix ID
: 000185500810
Source (R1) View
Target (R2) View
------------------------------------------------ST
LI
ST
Standard
A
N
A
Logical
T R1 Inv R2 Inv K
T R1 Inv R2 Inv
Device Dev
E Tracks Tracks S Dev
E Tracks Tracks
----------------------------- -- --------------------DEV001
Total
MB(s)
010F RW
66000 NR 00BF WD
------ -----0.0 2062.0
M O D E S
----------M
o
d
e
Dom ACp
-----------
------------
RDF Pair
STATE
------------
66000 SYN DIS OFF Suspended
------ -----0.0 2062.0
36
DATE: 03/11/02
The symdg show command with the lock option displays existing device external locks on devices
within the device group named sar. The display shows which devices on the local and remote Symmetrix
units 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
Group Name:
D E V I C E
G R O U P
L O C K S
sar
Group Type
: REGULAR
Valid
: Yes
Symmetrix ID
: 000185500814
Group Creation Time : Tue Oct 16 09:49:41 2001
Vendor ID
: EMC Corp
Application ID
: SYMCLI
Lock Number
: 9
Number of Locked Devices in Group:
STD Devices
Remote Mirrors
BCV Devices
Remote Mirrors
RBCV Devices
Remote Mirrors
BRBCV Devices
Remote Mirrors
:
:
:
of BCV's
:
:
of RBCV's :
:
of BRBCV's :
of STD's
16
0
16
16
0
0
16
0
(SID:
(SID:
(SID:
(SID:
(SID:
(SID:
(SID:
(SID:
000185500814)
N/A
)
000185500814)
000185500505)
N/A
)
N/A
)
000185500505)
N/A
)
STD Devices (16):

{
----------------------------------------------------Sym
Lock
Director Seconds
Lock
Dev
Holder-ID Initiator Number
Held
Flags
----------------------------------------------------03F7 0x1001100E
0
05B
12
Long
03F8 0x1001100E
0
05B
12
Long
03F9 0x1001100E
0
05B
12
Long
03FA 0x1001100E
0
05B
12
Long
03FB 0x1001100E
0
05B
12
Long
03FC 0x1001100E
0
05B
12
Long
03FD 0x1001100E
0
05B
12
Long
03FE 0x1001100E
0
05B
12
Long
03FF 0x1001100E
0
05B
12
Long
0400 0x1001100E
0
05B
12
Long
0401 0x1001100E
0
05B
12
Long
0402 0x1001100E
0
05B
12
Long
0403 0x1001100E
0
05B
12
Long
0404 0x1001100E
0
05B
12
Long
0405 0x1001100E
0
05B
12
Long
0406 0x1001100E
0
05B
12
Long
}
37
DATE: 03/11/02
BCV Devices (16):

{
----------------------------------------------------Sym
Lock
Director Seconds
Lock
Dev
Held
Flags
----------------------------------------------------0407 0x1001100E
0
05B
13
Long
0408 0x1001100E
0
05B
13
Long
0409 0x1001100E
0
05B
13
Long
040A 0x1001100E
0
05B
13
Long
040B 0x1001100E
0
05B
13
Long
040C 0x1001100E
0
05B
13
Long
040D 0x1001100E
0
05B
13
Long
040E 0x1001100E
0
05B
13
Long
040F 0x1001100E
0
05B
13
Long
0410 0x1001100E
0
05B
13
Long
0411 0x1001100E
0
05B
13
Long
0412 0x1001100E
0
05B
13
Long
0413 0x1001100E
0
05B
13
Long
0414 0x1001100E
0
05B
13
Long
0415 0x1001100E
0
05B
13
Long
0416 0x1001100E
0
05B
13
Long
}
Remote Mirrors of BCV's (16):
{
----------------------------------------------------Sym
Lock
Director Seconds
Lock
Dev
Held
Flags
----------------------------------------------------0390 0x100113A3
0
14B
13
Long
0391 0x100113A3
0
14B
13
Long
0392 0x100113A3
0
14B
13
Long
0393 0x100113A3
0
14B
13
Long
0394 0x100113A3
0
14B
13
Long
0395 0x100113A3
0
14B
13
Long
0396 0x100113A3
0
14B
13
Long
0397 0x100113A3
0
14B
13
Long
0398 0x100113A3
0
14B
13
Long
0399 0x100113A3
0
14B
13
Long
039A 0x100113A3
0
14B
13
Long
039B 0x100113A3
0
14B
13
Long
039C 0x100113A3
0
14B
13
Long
039D 0x100113A3
0
14B
13
Long
039E 0x100113A3
0
14B
13
Long
039F 0x100113A3
0
14B
13
Long
}
38
DATE: 03/11/02
BRBCV Devices (16):

{
----------------------------------------------------Sym
Lock
Director Seconds
Lock
Dev
Held
Flags
----------------------------------------------------03A0 0x100113A3
0
14B
13
Long
03A1 0x100113A3
0
14B
13
Long
03A2 0x100113A3
0
14B
13
Long
03A3 0x100113A3
0
14B
13
Long
03A4 0x100113A3
0
14B
13
Long
03A5 0x100113A3
0
14B
13
Long
03A6 0x100113A3
0
14B
13
Long
03A7 0x100113A3
0
14B
13
Long
03A8 0x100113A3
0
14B
13
Long
03A9 0x100113A3
0
14B
13
Long
03AA 0x100113A3
0
14B
13
Long
03AB 0x100113A3
0
14B
13
Long
03AC 0x100113A3
0
14B
13
Long
03AD 0x100113A3
0
14B
13
Long
03AE 0x100113A3
0
14B
13
Long
03AF 0x100113A3
0
14B
13
Long
}
39
DATE: 03/11/02
Example 6: Obtaining Disk and Audit Information

This 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 shown
here, 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 their
hypers 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 hypers,
use symdisk list da 01A interface C tid 3 v hypers.
# symdisk list
Symmetrix ID
Disks Selected
: 000185500814
: 96
Capacity(MB)
Ident Symb Int TID Vendor
Type
Hypers
Total
Free
------ ---- --- --- ---------- ---------- ------ -------- -------DA-1A 01A
C
0 SEAGATE
CHET_73
17
70007
446
DA-1A 01A
C
1 SEAGATE
CHET_73
17
70007
446
DA-1A 01A
C
2 SEAGATE
CHET_73
16
70007
962
DA-1A 01A
C
3 SEAGATE
CHET_73
16
70007
962
DA-1A 01A
C
4 SEAGATE
CHET_73
15
70007
5465
DA-1A 01A
C
5 SEAGATE
CHET_73
19
70007
5977
DA-1A 01A
D
0 SEAGATE
CHET_73
17
70007
446
DA-1A 01A
D
1 SEAGATE
CHET_73
17
70007
446
DA-1A 01A
D
2 SEAGATE
CHET_73
16
70007
962
DA-1A 01A
D
3 SEAGATE
CHET_73
16
70007
962
DA-1A 01A
D
4 SEAGATE
CHET_73
17
70007
1666
DA-1A 01A
D
5 SEAGATE
CHET_73
16
70007
2697
DA-2A 02A
C
0 SEAGATE
CHET_73
17
70007
446
DA-2A 02A
C
1 SEAGATE
CHET_73
17
70007
446
DA-2A 02A
C
2 SEAGATE
CHET_73
16
70007
962
DA-2A 02A
C
3 SEAGATE
CHET_73
16
70007
962
DA-2A 02A
C
4 SEAGATE
CHET_73
16
70007
5466
DA-2A 02A
C
5 SEAGATE
CHET_73
19
70007
5977
DA-2A 02A
D
0 SEAGATE
CHET_73
17
70007
446
DA-2A 02A
D
1 SEAGATE
CHET_73
16
70007
962
DA-2A 02A
D
2 SEAGATE
CHET_73
16
70007
962
DA-2A 02A
D
3 SEAGATE
CHET_73
18
70007
3612
DA-2A 02A
D
4 SEAGATE
CHET_73
18
70007
1667
DA-2A 02A
D
5 SEAGATE
CHET_73
18
70007
1667
DA-15A 15A
C
0 SEAGATE
CHET_73
17
70007
446
DA-15A 15A
C
1 SEAGATE
CHET_73
17
70007
446
DA-15A 15A
C
2 SEAGATE
CHET_73
16
70007
962
DA-15A 15A
C
3 SEAGATE
CHET_73
16
70007
962
DA-15A 15A
C
4 SEAGATE
CHET_73
16
70007
5466
DA-15A 15A
C
5 SEAGATE
CHET_73
19
70007
1664
DA-15A 15A
D
0 SEAGATE
CHET_73
17
70007
446
DA-15A 15A
D
1 SEAGATE
CHET_73
16
70007
962
DA-15A 15A
D
2 SEAGATE
CHET_73
16
70007
962
DA-15A 15A
D
3 SEAGATE
CHET_73
16
70007
962
40
DATE: 03/11/02
The symaudit 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 symaudit 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
Symmetrix ID
: 000185500814
Starting date
Ending date
: 12/14/2001 14:53:10
: 12/17/2001 14:40:47
Starting record number

Ending record number
Total record count
:
:
:
1
127
127
The following symaudit list 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 was
omitted for brevity.
# symaudit list
A U D I T
L O G
D A T A
Symmetrix ID
: 000185500814
Starting date
Ending date
: 12/14/2001 14:53:10
: 12/17/2001 14:18:36
Record
Number
------
Date
Time
-------- --------
Function Action
Application
Host
Class
Code
---------------- ------------ -------- ---------
1 12/14/01 14:53:10 SYMCLI

api179
RDF
Split
2 12/14/01 14:53:10 SYMCLI
api179
RDF
Split
3 12/14/01 14:53:11 SYMCLI
api179
RDF
Split
4 12/14/01 14:53:16 SYMCLI
api179
RDF
IncEsta
5 12/14/01 14:53:16 SYMCLI
api179
RDF
IncEsta
6 12/14/01 14:53:17 SYMCLI
api179
RDF
IncEsta
14 12/14/01 16:32:39 SYMCLI

api179
BCV
FullEsta
15 12/14/01 16:32:39 SYMCLI
api179
BCV
FullEsta
16 12/14/01 16:33:01 SYMCLI
api179
BCV
FullEsta
17 12/14/01 16:40:01 SYMCLI
api179
BCV
Split
18 12/14/01 16:40:01 SYMCLI
api179
BCV
Split
19 12/14/01 16:40:01 SYMCLI
api179
BCV
Split
109 12/17/01 14:39:05 SYMCLI

api179
BCV
Split
110 12/17/01 14:39:07 SYMCLI
api179
RDF
IncEsta
111 12/17/01 14:39:07 SYMCLI
api179
RDF
IncEsta
112 12/17/01 14:39:08 SYMCLI
api179
RDF
IncEsta
113 12/17/01 14:39:10 SYMCLI
api179
BCV
IncEsta
114 12/17/01 14:39:10 SYMCLI
api179
BCV
IncEsta
115 12/17/01 14:39:10 SYMCLI
api179
BCV
IncEsta
41
DATE: 03/11/02
116
117
118
119
120
121
122
123
124
125
126
127
12/17/01
12/17/01
12/17/01
12/17/01
12/17/01
12/17/01
12/17/01
12/17/01
12/17/01
12/17/01
12/17/01
12/17/01
14:39:10
14:39:24
14:39:24
14:39:24
14:39:24
14:39:24
14:39:42
14:40:44
14:40:44
14:40:44
14:40:44
14:40:46
SYMCLI
SYMCLI
SYMCLI
SYMCLI
SYMCLI
SYMCLI
SYMCLI
SYMCLI
SYMCLI
SYMCLI
SYMCLI
SYMCLI
api179
api179
api179
api179
api179
api179
api179
api179
api179
api179
api179
api179
BCV
BCV
BCV
BCV
BCV
BCV
BCV
BCV
BCV
BCV
BCV
BCV
IncEsta
IncEsta
IncEsta
IncEsta
IncEsta
IncEsta
IncEsta
Split
Split
Split
Split
Split
Using the text option with the symaudit list command displays the text associated with the
audit log record.
# symaudit list -text
A U D I T
L O G
D A T A
Symmetrix ID
: 000185500814
Starting date
Ending date
: 12/14/2001 14:53:10
: 12/17/2001 14:18:36
Record
Number
-------
Time
Function
Class
--------
Action
Code
--------
-------Text
-----------------------------------------------------14:53:10 RDF
Split
STARTING an RDF 'SPLIT'. type: Regular [RDF1 BCV], flags:
14:53:10 RDF
[ 0407-0416
Split
]
14:53:11 RDF
Split
The RDF 'SPLIT' operation SUCCEEDED.
14:53:16 RDF
IncEsta
STARTING an RDF 'INCREMENTAL ESTABLISH'. type: Regular [RDF1 BCV], flags:
14:53:16 RDF
[ 0407-0416
IncEsta
]
14:53:17 RDF
IncEsta
The RDF 'INCREMENTAL ESTABLISH' operation SUCCEEDED.
14
16:32:39 BCV
FullEsta
STARTING a local 'BCV Full Establish' operation for 1 [STD-BCV] Pair:
15
16:32:39 BCV
[ 0000-0190 ]
16
16:33:01 BCV
FullEsta
'BCV Full Establish'. sts: SYMAPI_C_SUCCESS
17
16:40:01 BCV
Split
STARTING a local 'BCV Split' operation for 1 [STD-BCV] Pair:
16:40:01 BCV
Split
[ 0000-0190 ]
18
FullEsta
42
DATE: 03/11/02
19
16:40:01 BCV
Split
'BCV Split'. sts: SYMAPI_C_SUCCESS
109
14:39:05 BCV
Split
110
14:39:07 RDF
IncEsta
STARTING an RDF 'INCREMENTAL ESTABLISH'. type: Regular [RDF1 BCV], flags:
111
14:39:07 RDF
[ 0407-0416
IncEsta
]
112
14:39:08 RDF
IncEsta
The RDF 'INCREMENTAL ESTABLISH' operation SUCCEEDED.
113
14:39:10 BCV
IncEsta
STARTING a local 'BCV Inc Establish' operation for 16 [STD-BCV] Pairs:
114
14:39:10 BCV
IncEsta
[ 03F7-0407 03F8-0408 03F9-0409 03FA-040A 03FB-040B 03FC-040C
115
14:39:10 BCV
IncEsta
03FD-040D 03FE-040E 03FF-040F 0400-0410 0401-0411 0402-0412
116
14:39:10 BCV
IncEsta
0403-0413 0406-0416 0404-0415 0405-0414 ]
117
14:39:24 BCV
IncEsta
'BCV Inc Establish'. sts: SYMAPI_C_SUCCESS
118
14:39:24 BCV
IncEsta
STARTING a remote 'BCV Inc Establish' operation for 16 [STD-BCV] Pairs:
119
14:39:24 BCV
IncEsta
[ 0390-03A0 0391-03A1 0392-03A2 0393-03A3 0394-03A4 0395-03A5
120
14:39:24 BCV
IncEsta
0396-03A6 0397-03A7 0398-03A8 0399-03A9 039A-03AA 039B-03AB
121
14:39:24 BCV
IncEsta
039C-03AC 039F-03AF 039E-03AE 039D-03AD ]
122
14:39:42 BCV
IncEsta
'BCV Inc Establish'. sts: SYMAPI_C_SUCCESS
123
14:40:44 BCV
Split
STARTING a remote 'BCV Split' operation for 16 [STD-BCV] Pairs:
124
14:40:44 BCV
Split
[ 0390-03A0 0391-03A1 0392-03A2 0393-03A3 0394-03A4 0395-03A5
125
14:40:44 BCV
Split
0396-03A6 0397-03A7 0398-03A8 0399-03A9 039A-03AA 039B-03AB
126
14:40:44 BCV
Split
039C-03AC 039F-03AF 039E-03AE 039D-03AD ]
127
14:40:46 BCV
Split
43
DATE: 03/11/02
The following symaudit list 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 0390 from device 03A0).
# symaudit -v list -record_num 124
A U D I T
L O G
D A T A
Symmetrix ID
: 000185500814
Starting date
Ending date
: 12/17/2001 14:40:44
: 12/17/2001 14:40:46
Record Number
Records in Seq
Offset in Seq
Time
Vendor ID
Application ID
Application Version
API Library
API Version
Host Name
OS Name
OS Revision
Client Host
Process ID
Task ID
Function Class
Action Code
Text
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
124
4
2
12/17/01 14:40:44
EMC Corp
SYMCLI
5.0.0.0
SEK
T5.0.0.0 (Edit Level: 236)
api179
SunOS
5.8Generic
00006670
00000000
BCV
Split
[ 0390-03A0 0391-03A1 0392-03A2 0393-03A3 0394-03A4 0395-03A5
44
DATE: 03/11/02
Example 7: Obtaining Display Output in XML Format

With SYMCLI version 4.3.1 and higher, 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 symcfg list command to illustrate output.
By default, the symcfg list command produces a standard mode output display as shown below.
# symcfg list
S Y M M E T R I X
SymmID
Attachment
000185500814 Local
000185500505 Remote
Model
Mcode
Version
8230
8230
5568
5568
Cache
Size (MB)
4096
8192
Num Phys
Devices
757
0
Num Symm
Devices
1097
970
The export command sets the SYMCLI_OUTPUT_MODE variable to XML.

# export SYMCLI_OUTPUT_MODE=xml
The symcfg list command now produces the same output in XML format.
# symcfg list
<?xml version="1.0" standalone="yes" ?>
<SymCLI_ML>
<Symmetrix id="000185500814" attachment="Local" model="8230"
microcode_version="5568" cache_megabytes="4096"
physical_devices="757"
devices="1097"/>
<Symmetrix id="000185500505" attachment="Remote" model="8230"
microcode_version="5568" cache_megabytes="8192" physical_devices="0"
devices="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
By default, the symcfg list 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 version="1.0" standalone="yes" ?>
<SymCLI_ML>
<Symmetrix id="000185500814" attachment="Local" model="8230"
microcode_version="5568" cache_megabytes="4096"
physical_devices="757"
devices="1097"/>
45
DATE: 03/11/02
<Symmetrix id="000185500505" attachment="Remote" model="8230"

microcode_version="5568" cache_megabytes="8192" physical_devices="0"
devices="970"/>
</SymCLI_ML>
46

Using Symcli To Clean Config Information

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Using Symcli To Clean Config Information

Hochgeladen von

Copyright:

Verfügbare Formate

Engineering White Paper

Using SYMCLI to Obtain Symmetrix

Copyright 2002 EMC Corporation. All rights reserved.

Part Number H606.1

Using SYMCLI to Obtain Symmetrix Configuration Information

Using SYMCLI to Obtain Symmetrix Configuration Information

Symmetrix units attached to the host

Devices within each Symmetrix unit

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

Purpose and Scope

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 Perform TimeFinder Control Operations (P/N 300-000-074)

Using SYMCLI to Obtain Symmetrix Configuration Information

Displaying Information about a Symmetrix Unit

Using SYMCLI to Obtain Symmetrix Configuration Information

Microcode Version (Number)

Microcode Patch Date

Host DB Sync Time

Fri Nov 30 09:32:35 2001

Number of Configured (Sym) Devices

Number of Powerpath Devices

Total Operating Time

SDDF Configuration State

Using SYMCLI to Obtain Symmetrix Configuration Information

Ident Symbolic Numeric Slot Type

Symmetrix ID: 000000003263 (Remote)

Ident Symbolic Numeric Slot Type

Symmetrix ID: 000000003265 (Remote)

Ident Symbolic Numeric Slot Type

Using SYMCLI to Obtain Symmetrix Configuration Information

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

Symmetrix-registered applications that have accessed a certain Symmetrix.

All hosts that have accessed a certain Symmetrix.

Network services in the client/SYMAPI server connection.

Configuration and status information about all directors in a Symmetrix unit.

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

Symmetrix units that have a Symmetrix external lock.

Displaying Information about Symmetrix Devices

The symdev list command lists all devices in a Symmetrix unit.

Using SYMCLI to Obtain Symmetrix Configuration Information

Using SYMCLI to Obtain Symmetrix Configuration Information

All RDF1 type (R1) devices.

All BCV devices.

All DRV devices.

All meta devices.

All standard devices.

Using SYMCLI to Obtain Symmetrix Configuration Information

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

Displays devices that are configured as capable of being either dynamic R1 or R2

???:? 15A:D5 RDF1-BCV

???:? 16B:D5 BCV

Using SYMCLI to Obtain Symmetrix Configuration Information

Device Symmetrix Name

Device Group Name

Device Block Size

Using SYMCLI to Obtain Symmetrix Configuration Information

Mirror Set Type

Mirror Set DA Status

Mirror Set Inv. Tracks

State of Pair ( STD ====> BCV )

Number of Inv. Tracks for STD Device

Using SYMCLI to Obtain Symmetrix Configuration Information