Symptoms
Attempting to create devices with symconfigure and this fails with the error:
symconfigure -sid xxx -cmd "create dev count=1, size=100, emulation=FBA, config=TDEV, sg=SG_NAME;" preview -nop
A Configuration Change operation is in progress. Please wait... Establishing a configuration change session...............Established. Error occurred while Defining change number 1: The specified object does not exist. Terminating the configuration change session..............Done.The configuration change session has failed.The symapi log shows:
1 EMC:SYMCONFIGURE iSymConfigChangeSess Starting a remote CfgChg session for SID 0005979xxxxx, symapi V9.2-2631 (2.0) ucode 5978
Establishing session with Remote cfg srvr (0005979xxxxx)..Established.
Session ID 16806656 (0x01007300)
1 EMC:SYMCONFIGURE cfgValidateAddDevsTo Call to emcValidateAddDevsToStorGrp failed with status = 3596 (The specified object does not exist)
SymConfigChange Define error in dfn 1:
create dev count=1, size=100, emulation=FBA, config=TDEV, sg=SG_NAME;
The specified object does not exist.
1 EMC:SYMCONFIGURE User Generated The specified object does not exist.
Terminating session with configuration server.............Done.
The SG is seen in the "symsg list" command output.
Cause
This issue appears to be caused by the Storage Group having an association with a Snapshot Policy. You can see in the 'symsg show SG_NAME' output:
symsg -sid 63 show SG_NAME
Name: SG_NAME
Symmetrix ID : 0005979xxxxx
Last updated at : Thu Mar 31 13:30:03 2022
Masking Views : Yes
FAST Managed : Yes
Service Level Name : Optimized
Workload :
SRP Name : SRP_1
VP Saved (%) : 74.5
Compression Enabled : No
Compression Ratio : N/A
Host I/O Limit : None
Host I/O Limit MB/Sec : N/A
Host I/O Limit IO/Sec : N/A
Dynamic Distribution : N/A
Number of Gatekeepers : 0
Policies (1):
{
---------------------------------------------------------------
Suspension
Policy Name Type SG PSG Pol
---------------------------------------------------------------
Policy-10min Snapshot - Yes No
}
There appears to be a conflict when a snapshot policy is assigned to the storage group.
Resolution
Workaround: Create the devices without specifying a sg= value and then manually add the device(s) to the storage group
