18 Nov 10 Return Code for Symcli

Return code handling for Windows and UNIX The following lists the possible status or error codes that can be returned by the various SYMCLI commands on a Windows or UNIX platform and useful for troubleshooting.

0 CLI_C_SUCCESS CLI — call completed successfully.
1 CLI_C_FAIL CLI – call failed.
2 CLI_C_DB_FILE_IS_LOCKED- Another process has an exclusive
lock on the Host database file.
3 CLI_C_SYM_IS_LOCKED – Another process has an exclusive
lock on the Symmetrix.
4 CLI_C_NOT_ALL_SYNCHRONIZED NOT – all of the mirrored pairs are in the ‘Synchronized’ state.
5 CLI_C_NONE_SYNCHRONIZED – NONE of the mirrored pairs are in the ‘Synchronized’ state.
6 CLI_C_NOT_ALL_UPDATED – - NOT all of the mirrored pairs are in the ‘Updated’ state.
7 CLI_C_NONE_UPDATED –NONE of the mirrored pairs are in the ‘Updated’ state.
8 CLI_C_NOT_ALL_PINGED — NOT all of the remote Symmetrix units can be pinged.
9 CLI_C_NONE_PINGED — NONE of the remote Symmetrix units can be pinged.
10 CLI_C_NOT_ALL_SYNCHED — NOT all of the mirrored pairs are in the ‘Synchronized’ state.
11 CLI_C_NONE_SYNCHED — NONE of the mirrored pairs are in the ‘Synchronized’ state.
12 CLI_C_NOT_ALL_RESTORED — NOT all of the pairs are in the ‘Restored’ state.
13 CLI_C_NONE_RESTORED — NONE of the pairs are in the ‘Restored’ state.
14 CLI_C_NOT_ALL_VALID — NOT all of the mirrored pairs are in a valid state.
15 CLI_C_NONE_VALID — NONE of the mirrored pairs are in a valid state.
16 CLI_C_SYM_NOT_ALL_LOCKED — NOT all of the specified Symmetrix units have an exclusive Symmetrix lock.
17 CLI_C_SYM_NONE_LOCKED –NONE of the specified Symmetrix units have an exclusive Symmetrix lock.
18 CLI_C_ALREADY_IN_STATE –The Device(s) is (are) already in the desired state or mode.
19 CLI_C_GK_IS_LOCKED — All GateKeeper devices to the Symmetrix unit are currently locked.
20 CLI_C_WP_TRACKS_IN_CACHE — Operation cannot proceed because the target device has Write Pending I/O in the cache.
21 CLI_C_NEED_MERGE_TO_RESUME –Operation cannot proceed without first performing a merge of the RDF Track Tables.
22 CLI_C_NEED_FORCE_TO_PROCEED –Operation cannot proceed in the current state except if you specify a force flag.
23 CLI_C_NEED_SYMFORCE_TO_PROCEED –Operation cannot proceed in the current state except if you specify a symforce flag.
24 CLI_C_NOT_IN_SYNC — The Symmetrix configuration and the database file are NOT in sync.
25 CLI_C_NOT_ALL_SPLIT — NOT all of the mirrored pairs are in the ‘Split’ state.
26 CLI_C_NONE_SPLIT — NONE of the mirrored pairs are in the ‘Split’ state.
27 CLI_C_NOT_ALL_SYNCINPROG — NOT all of the mirrored pairs are in the ‘SyncInProg’ state.
28 CLI_C_NONE_SYNCINPROG — NONE of the mirrored pairs are in the ‘SyncInProg’ state.
29 CLI_C_NOT_ALL_RESTINPROG — NOT all of the pairs are in the ‘RestInProg’ state.
30 CLI_C_NONE_RESTINPROG — NONE of the pairs are in the ‘RestInProg’ state.
31 CLI_C_NOT_ALL_SUSPENDED — NOT all of the mirrored pairs are in the ‘Suspended’ state.
32 CLI_C_NONE_SUSPENDED — NONE of the mirrored pairs are in the ‘Suspended’ state.
33 CLI_C_NOT_ALL_FAILED_OVER — NOT all of the mirrored pairs are in the ‘Failed Over’ state.
34 CLI_C_NONE_FAILED_OVER — NONE of the mirrored pairs are in the ‘Failed Over’ state.
35 CLI_C_NOT_ALL_UPDATEINPROG — NOT all of the mirrored pairs are in the ‘R1 UpdInProg’ state.
36 CLI_C_NONE_UPDATEINPROG — NONE of the mirrored pairs are in the ‘R1 UpdInProg’ state.
37 CLI_C_NOT_ALL_PARTITIONED — NOT all of the mirrored pairs are in the ‘Partitioned’ state.
38 CLI_C_NONE_PARTITIONED — NONE of the mirrored pairs are in the ‘Partitioned’ state.
39 CLI_C_NOT_ALL_ENABLED — NOT all of the mirrored pairs are in the ‘Enabled’ consistency state.
40 CLI_C_NONE_ENABLED — NONE of the mirrored pairs are in the ‘Enabled’ consistency state.
41 CLI_C_NOT_ALL_SYNCHRONIZED_AND_ENABLED — NOT all of the mirrored pairs are in the ‘Synchronized’ rdf state and the ‘Enabled’ consistency state.
42 CLI_C_NONE_SYNCHRONIZED_AND_ENABLED — NONE of the mirrored pairs are in the ‘Synchronized’ rdf state and in the ‘Enabled’ consistency state.
43 CLI_C_NOT_ALL_SUSP_AND_ENABLED — NOT all of the mirrored pairs are in the ‘Suspended’ rdf state and ‘Enabled’ consistency state.
44 CLI_C_NONE_SUSP_AND_ENABLED — NONE of the mirrored pairs are in the ‘Suspended’ rdf state and the ‘Enabled’ consistency state.
45 CLI_C_NOT_ALL_SUSP_AND_OFFLINE — NOT all of the mirrored pairs are in the ‘Suspended’ rdf state and ‘Offline’ link suspend state.
46 CLI_C_NONE_SUSP_AND_OFFLINE — NONE of the mirrored pairs are in the ‘Suspended’ rdf state and the ‘Offline’ link suspend state.
47 CLI_C_WONT_REVERSE_SPLIT — Performing this operation at this time will not allow you to perform the next BCV split as a reverse split.
48 CLI_C_CONFIG_LOCKED — Access to the configuration server is locked.
49 CLI_C_DEVS_ARE_LOCKED — One or more devices are locked.
50 CLI_C_MUST_SPLIT_PROTECT — If a device was restored with the protect option, it must be split with the protect option.
51 CLI_C_PAIRED_WITH_A_DRV — The function can not be performed since the STD device is already paired with a DRV device.
52 CLI_C_PAIRED_WITH_A_SPARE — NOT all of the Snap pairs are in the ‘Copy in progress’ state.
53 CLI_C_NOT_ALL_COPYINPROG — NOT all of the pairs are in the ‘CopyInProgress’ state.
54 CLI_C_NONE_COPYINPROG –NONE of the pairs are in the ‘CopyInProgress’ state.
55 CLI_C_NOT_ALL_COPIED — NOT all of the pairs are in the ‘Copied’ state.
56 CLI_C_NONE_COPIED — NONE of the pairs are in the ‘Copied’ state.
57 CLI_C_NOT_ALL_COPYONACCESS — NOT all of the pairs are in the ‘CopyonAccess’ state.
58 CLI_C_NONE_COPYONACCESS — NONE of the pairs are in the ‘CopyonAccess’ state.
59 CLI_C_CANT_RESTORE_PROTECT –The protected restore operation can not be completed because there are write pendings or the BCV mirrors are not synchronized.
60 CLI_C_NOT_ALL_CREATED — NOT all of the pairs are in the ‘Created’ state.
61 CLI_C_NONE_CREATED — NONE of the pairs are in the ‘Created’ state.
62 CLI_C_NOT_ALL_READY — NOT all of the BCVs local mirrors are in the ‘Ready’ state.
63 CLI_C_NONE_READY — NONE of the BCVs local mirrors are in the ‘Ready’ state.
64 CLI_C_STD_BKGRND_SPLIT_IN_PROG — The operation cannot proceed because the STD Device is splitting in the Background.
65 CLI_C_SPLIT_IN_PROG — The operation cannot proceed because the pair is splitting.
66 CLI_C_NOT_ALL_COPYONWRITE — NOT all of the pairs are in the ‘CopyOnWrite’ state.
67 CLI_C_NONE_COPYONWRITE — NONE of the pairs are in the ‘CopyOnWrite’ state.
68 CLI_C_NOT_ALL_RECREATED — Not all devices are in the ‘Recreated’ state.
69 CLI_C_NONE_RECREATED — No devices are in the ‘Recreated’ state.
70 CLI_C_NOT_ALL_CONSISTENT — NOT all of the mirrored pairs are in the ‘Consistent’ state.
71 CLI_C_NONE_CONSISTENT– NONE of the mirrored pairs are in the ‘Consistent’ state.
72 CLI_C_MAX_SESSIONS_EXCEEDED– The maximum number of sessions has been exceeded for the specified device.
73 CLI_C_NOT_ALL_PRECOPY — Not all source devices are in the ‘Precopy’ state.
74 CLI_C_NONE_PRECOPY — No source devices are in the ‘Precopy’ state.
75 CLI_C_NOT_ALL_PRECOPY_CYCLED — Not all source devices have completed one precopy cycle.
76 CLI_C_NONE_PRECOPY_CYCLED — No source devices have completed one precopy cycle.
77 CLI_C_CONSISTENCY_TIMEOUT — The operation failed because of a Consistency window timeout.
78 CLI_C_NOT_ALL_FAILED — NOT all of the pairs are in the ‘Failed’ state.
79 CLI_C_NONE_FAILED — NONE of the pairs are in the ‘Failed’ state.
80 CLI_C_CG_NOT_CONSISTENT — CG is NOT RDF-consistent.
81 CLI_C_NOT_ALL_CREATEINPROG — NOT all of the pairs are in the ‘CreateInProg’ state.
82 CLI_C_NONE_CREATEINPROG — None of the pairs are in the ‘CreateInProg’ state.
83 CLI_C_NOT_ALL_RECREATEINPROG — NOT all of the pairs are in the ‘RecreateInProg’ state.
84 CLI_C_NONE_RECREATEINPROG — None of the pairs are in the ‘RecreateInProg’ state.
85 CLI_C_NOT_ALL_TERMINPROG — NOT all of the pairs are in the ‘TerminateInProg’ state.
86 CLI_C_NONE_TERMINPROG — None of the pairs are in the ‘TerminateInProg’ state.
87 CLI_C_NOT_ALL_VERIFYINPROG — NOT all of the pairs are in the ‘VerifyInProg’ state.
88 CLI_C_NONE_VERIFYINPROG — None of the pairs are in the ‘VerifyInProg’ state.
89 CLI_C_NOT_ALL_VERIFIED — NOT all of the pairs are in the requested states.
90 CLI_C_NONE_VERIFIED — NONE of the pairs are in the requested states Note: This message is returned when multiple states are verified at once.
91 CLI_C_RDFG_TRANSMIT_IDLE — RDF group is operating in SRDF/A Transmit Idle.
92 CLI_C_NOT_ALL_MIGRATED — Not all devices are in the ‘ Migrated’ state.
93 CLI_C_NONE_MIGRATED — None of devices are in the ‘Migrated’ state.
94 CLI_C_NOT_ALL_MIGRATEINPROG — Not all devices are in the ‘MigrateInProg’ state.
95 CLI_C_NONE_MIGRATEINPROG — None of devices are in the ‘MigrateInProg’ state.
96 CLI_C_NOT_ALL_INVALID– Not all devices are in the ‘Invalid’ state.
97 CLI_C_NONE_INVALID– None of devices are in the ‘Invalid’ state.

Tags: CLI, code, symcli, Symmetrix, unix, windows

08 Oct 10 Symaccess Command

Summary of the most commonly used symaccess commands with examples.

• symaccess -sid 1313 list – List all Initiator,Port and Storage Groups Created for Array 1313
• symaccess -sid 1313 list -v – List all Initiator,Port and Storage Groups Created for Array 1313 along with related Masking Views
• symaccess -sid 1313 list -type storage – List all Storage Groups Created for Array 1313
• symaccess -sid 1313 list -type initiator – List all Initiator Groups Created for Array 1313
• symaccess -sid 1313 list -type port – List all Port Groups Created for Array 1313
• symaccess -sid 1313 list view – List masking views Created for Array 1313 with related groups details
• symaccess -sid 1313 list assignment -dev 9A0:9AF – Shows the masking details of devices from 9A0 to 9AF
• symaccess -sid 1313 list no_assignments -dirport 12f:1 – Shows the devices are mapped to 12f:1 but not masked.
• symaccess -sid 1313 list -name MyGroup – List all groups named MyGroup
• symaccess -sid 1313 list -name MyGroup -v – List all groups named MyGroup and also shows the related Masking Views
• symaccess -sid 1313 list devinfo -ig MyInitiator – List the details of devices assigned to the initiatorgroup MyInitiator
• symaccess -sid 1313 show MyStorageGroup -type storage – Shows the contents of storage group MyStorageGroup Created on Array 1313
• symaccess -sid 1313 show MyInitiatorGroup -type initiator – Shows the contents of initiator group MyInitiatorGroup Created on Array 1313
• symaccess -sid 1313 show MyPortGroup -type port – Shows the contents of port group MyPortGroup Createdon Array 1313
• symaccess -sid 1313 show view MyView – Shows the contents of view MyView Created on Array 1313
• symaccess -sid 1313 -f MyBackup.txt backup – Creates a file MyBackup containing all the group and view information currently on the Symmetrix array 1313
• symaccess -sid 1313 -f MyBackup.txt restore – Restores all the group, view and security information from the specified backupup file
• symaccess -sid 1313 -type initiator -name Host1 create -wwn 1000000000000001 – Creates and initiator group called Host1 by adding the specified wwn
• symaccess -sid 1313 -type initiator -name Host1 add -wwn 1000000000000002 – Add the specified wwn in to the existing initiator group Host1
• symaccess -sid 1313 -type port -name 3E0_4E0_13E0_14E0 -dirport 3e:0,4e:0,13e:0,10e:0 create – Create the portgroup E0_4E0_13E0_14E0 with specified ports
• symaccess -sid 1313 -type storage -name Host1 create devs AAA:AAB – Create the storage group Host1 with specified range of devices
• symaccess -sid 1313 -type storage -name Host1 add devs AAA:AAB – Create the storage group Host1 with specified range of devices
• symaccess -sid 1313 create view -name Host1_Allocation -sg Host1 -pg 3E0_4E0_13E0_14E0 -ig Host1 – Create a masking view combined with specified groups

Tags: EMC, Symaccess, Symmetrix, VMax