Dell Solutions Enabler 10.0.1 Release Notes

PDF

Limitations

This section includes any known limitations the customers may experience in certain environments.

Table 1. Solutions Enabler V10.0.1 Limitations
Functional area	Limitation
Access Control	Use of the Symmetrix Access Control feature requires the help of Dell Customer Service to initially set up your array. For more information, contact your Dell Representative and refer to the Dell Solutions Enabler Array Controls and Management CLI User Guide.
Access Control	CREATEDV access can only be granted to ALL devices or on !INPOOLS when there are no accpools defined.
	Symmetrix ACLs (symacl) are not supported on PowerMax 2500 and PowerMax 8500 arrays.

AIX-specific	Renaming disk names for AIX is not supported.

Base Management	The device label/relabel feature using the symlabel command is restricted to Windows devices only.
	The following are limitations when using a remote SYMAPI server: SYMCLI command symchg is not supported. When using the database mapping commands of SYMCLI (unless they are set on the client side), you must set Oracle variables ORACLE_HOME and ORACLE_SID for networked services on the server side. SYMCLI command symmir with the instant split -vxfs option is not supported in a client/server environment.
	When using the GNS daemon and the gns_remote_mirror capability, any groups defined as type RDF2 must not contain devices whose remote R1 mirrors are also BCVs.
	On UNIX, either read or read/write access to this file is required, depending on the types of operations you wish to allow the user to perform. For example, if the user will be making changes to the database file, such as in a discover operation or defining a SYMAPI group, the user would require read/write access.
	On Windows, read/write access to the file is required regardless of the type of operation being performed.
	For non-root or non administrator users to be able to make use of the Solutions Enabler daemons, their names must be listed in the .../config/daemon_users file.
	When using the symstat -type memio command, the destaged value will always show zero.
	Dedicated spare disks are not reported for arrays running HYPERMAX OS 5977 or above. For arrays running HYPERMAX OS 5977 or above, spare coverage information is reported at the Disk Group/Engine Spindle Group level. The symdisk list -dskgrp_summary -by_engine CLI display provides this information and is described in the Dell Solutions Enabler Array Controls and Management CLI User Guide.

Configuration Manager	The symcfg list command displays the RAID 5 and RAID 6 configuration on the array. It is not intended to provide a breakdown of all the RAID types in all the SRP’s (in the case of Multiple SRP’s one with RAID 5 and RAID 6 and the one with RAID 1).
	Before issuing a symconfigure command to Symmetrix arrays containing both open system and mainframe devices, you must verify that the mainframe Missing Interrupt Handler (MIH) period is set to at least two minutes.
	Before changing the IP address of a GigE front-end port with a configuration change operation, you have to take the port offline.
	For non-dynamic SRDF devices, before converting SRDF devices to non-SRDF devices, ensure that the SRDF pair devices being converted are in the split state or failed over. If the devices are failed over, the R1 devices must be unmapped.
	When swapping the personality of ESCON directors, be aware that FarPoint buffer settings cannot be adjusted using Configuration Manager. If your FarPoint buffers are set to anything other than default values, Dell EMC Customer Service will need to be engaged to set the buffers after the swap has taken place.
	The symconfigure command (remove external_disk) to remove externally provisioned disks has a recommended upper limit of 500 requests in a single CLI (or) command file in the preview mode.

Device Masking	If the Solutions Enabler configuration contains a RecoverPoint cluster, a restore operation will not be allowed.

Double Checksum	Dell Double Checksum and Generic SafeWrite are not supported with concurrent and cascaded SRDF devices.
	The Logical Volume Manager (LVM) is not supported for Double Checksum on AIX.
	Veritas RAID5 volumes are not supported when creating an Oracle tablespace, where the device has the checksum flag turned on and `db_block_checksum=TRUE`. For the symchksum enable CLI command, the -tbs TBSNAME -reject_io option returns the following error message: `VxVM RAID-5 is not currently supported`. NOTE: The reject_io feature is not supported at this time because Veritas incorrectly handles failed writes.
	Oracle ASM is not supported for Double Checksum.

HP-UX-specific	Soft partition volumes are not supported.
HP-UX-specific	The swverify command is not supported for Solutions Enabler on the HP-UX platform.

Installation	The HP-UXIA native installation package for Solutions Enabler SYMCLI contains two sets of file sets. One set gets installed under /opt/emc (default install root directory) and the other gets installed under /usr/emc (default working root directory). These default directories can also be changed during installation. Since there are two installation directories for the same package, after installation, the swlist command will show two entries for SYMCLI as shown in the following example: # swlist \| grep SYMCLI SYMCLI V10.0.1.0 Dell Inc. or its subsidiaries. SYMCLI V10.0.1.0 Dell Inc. or its subsidiaries. The Solutions Enabler kit is installed using native installation utilities. Therefore, to install an earlier version of Solutions Enabler, you must uninstall Solutions Enabler before reinstalling the earlier version.
	In a Windows environment, Solutions Enabler requires the Microsoft Windows Installer V3.1 redistributable package, WindowsInstaller-KB893803-v2-x86.exe. NOTE:If you have previous pre-release versions of Visual C++ 2005 or Visual Studio 2005, such as Beta 1, Beta 2, or Community Technical Preview (CTP) builds installed on the host, you must uninstall these versions through Add/Remove Programs in Control Panel before installing V3.1.
	Solutions Enabler requires GNU Compiler Collection (GCC) standard C++ library /usr/lib/libstdc++.so.5 for its dynamically linked C++ binaries. This generally comes with libstdc++ rpm. Some new versions of Linux (RH Enterprise Linux Server release 5, SUSE 10, some RH Enterprise Linux Server 4 and SUSE 9) come with /usr/lib/libstdc++.so.6. This is found in systems with GCC version 3.4 and above or systems with libstdc++ version 3.4 and above. In these systems, make sure that compat-libstdc++ rpm (compat-libstdc++-33 in Redhat Linux) is installed before installing Solutions Enabler. compat-libstdc++ rpm provides compatible C++ libraries. Run the following command to check for compatibility: rpm -qa \| grep libstdc++ libstdc++-4.1.1-52.el5 libstdc++-devel-4.1.1-52.el5 compat-libstdc++-33-3.2.3-61 rpm -ql compat-libstdc++-33-3.2.3-61 /usr/lib/libstdc++.so.5 /usr/lib/libstdc++.so.5.0.7 If you do not have the correct version installed, obtain and install it before proceeding with the Solutions Enabler installation. The library can be installed by running the following command: rpm -ivh compat-libstdc++*.rpm For proper TimeFinder/Mirror operations with Veritas (VxVM) environments, you must run: vxdctl enable
	SSL subject certificates can be generated using the industry standard Subject Alternative Name feature (SAN). SANs are primarily used to represent multiple identities for a given host, in the cases where a host is multi-homed, participates as part of a cluster, or is a member of more than one domain. Because of the support for SANs, Solutions Enabler certificates can no longer specify more than one name in the Common Name (CN) field of a certificate. In previous releases, a list of names could be specified following the create verb of the manage_server_cert command.
	AIX does not allow changes to the destination path during installation. All binaries and libraries are installed under /opt/emc. If there is insufficient disk space under /opt, create a soft link to /opt/emc/ as shown below and run the installer: ln -s NewInstallationDir /opt/emc The root must have write permission on the NewInstallationDir
	The length of a database daemon binary name along with its corresponding environment variable for the instance name cannot exceed 32 characters. For example, if users are running 64 bit Sybase Server version 12.5, the corresponding daemon’s binary name is storsybs12.5_64d, and the corresponding environment variable for the instance name is DSQUERY. If DSQUERY is set to the value SYSBASE_HOST1, the combined length of storsybs12.5_64dSYSBASE_HOST1 cannot exceed 32 characters.

Linux on System z-specific	The FBA devices mapped to the connected port and generated on the VM side can be added to the guest and be used regardless of masking. So adding devices to the guest systems shows to be controlled by the VM and not the VCM.
	There are no PDEVs for CKD DASD devices not in an active state as reported by lsdasd.
	Support for Open Replicator is for FBA devices only.
	Mini disks are not supported.

Linux Red Hat/SUSE-specific	When you install a 64-bit Solutions Enabler kit, the 64-bit libdevmapper libraries should also be installed. Just as for the 32-bit libraries, a symbolic link is required to point to the correct version of the libdevmapper library. For example, create the link using the command: ln -s /lib64/libdevmapper.so.1.02 /lib64/libdevmapper.so NOTE:The libdevmapper libraries could be installed in /usr/lib64, therefore adjust the ln command accordingly.

Open Replicator	The Open Replicator for array operations are limited to FBA type devices that can be mapped to the host through Fibre Channel directors. The following device types that could be mapped to the host are not supported: CKD Copying device data from one device to another must execute across a network (SAN) with a switch in the network path. You cannot copy device-to-device within the same array.
	Copying is device-based (no extent copying supported). You cannot make device configuration changes during an Open Replicator session, as making device changes may lead to inconsistent data on the local device if pulling, or on the remote device if pushing data.
	The Open Replicator cannot detect changes to a remote device during, or between incremental copies. Before each session, check to ensure there are no changes being made to the remote device.
	Open Replication blocks the following operations: TimeFinder establish (full or incremental) when the BCV device is in a push session in the restored state with donor update. TimeFinder establish (full or incremental) when the BCV device is in a push session in the created, recreated or failed state. TimeFinder restore when the STD device is in a push session in the restored state with donor update. TimeFinder restore when the STD device is in a push session in the created, recreated or failed state. Clone create, recreate, incremental establish or full establish when the BCV device is in a push session in the restored state with donor update. Clone create, recreate, incremental establish or full establish when the BCV device is in a push session in the created, recreated or failed state. To rename, remove, recreate, restore, terminate or create a session on the same control device when the session has the -donor_update option enabled, you must use the -force option.
	Setting the session pace for the CopyInProg, RecreateInProg, and RestInProg states is not supported for arrays running HYPERMAX OS 5977 or higher.
	ORS with user geometry is not supported. Solutions Enabler does not allow clearing the user geometry when the device is mapped.

RecoverPoint	At the time of device creation, non-RecoverPoint devices can be added to the reserved RecoverPoint storage group _RP_clustername_SG. While these non-RecoverPoint devices cannot be removed from the SG, they can be removed using CLI by placing the devices into a storage group, protect the storage group and then unprotect it.

SRDF	SRDF control operations will not work on an SRDF2 composite group that contains both remote mirrors of a single concurrent RDF R1 device.
SRDF	You should perform an SRDF establish and not a SRDF failback operation on the non-SA mapped R1 devices if one the following criteria is met after a split operation: The R1 device(s) or device group contain one or more R1 devices that are not mapped to an SA, and you do not want to restore R2 data changes back to the R1 sources.