| NOTE: Dell recommends
 | that you consult with
 | IBM before setting the
 | LDR_CNTRL=MAXDATA=VAL
 | variable.
 | For VIO Server client hosts, IBM has not yet enhanced the HBA API library to support vSCSI HBAs, therefore syminq hba on a VIO client host does not return HBA information.|
 | Base Management| In a HYPERMAX OS 5977 environment, before deleting a device, it must be de-allocated and the de-allocation process must be completed.|
---|---|---|---
 |  | The sympd list -vm command on an ESX Server 3.0.2 returns N/A for the VM device name.| To correct this, enable the SPC-2 flag. This flag does not need to be enabled on ESX Server 3.5 and later.
 |  | The device serial number format is SSNNNNNDDP. The expanded serial number format for HYPERMAX OS 5977 contains no DDP, that is, the DDP value

is always 000 (SSNNNNN000). The port number

(P) still shows the MSB for devices between 4K and 8K, but can now be ignored because of the expanded serial number format. To determine the correct port number in these cases, subtract 8 from the P field.

|
 | <4K device
 | ●  Device Serial Number: 1800014130
 | ●   SymDevName: 014
 | ● Port: 0
 | >4K, <8K device
 | ●  Device Serial Number: 1801014138
 | ●  SymDevName: 1014
 | ● Port: 0
 | >8K device
 | ●   Device Serial Number: 1802014130
 | ●  SymDevName: 2014
 | ●  Port: 0
 |  | When group names are duplicated across a GNS environment (GNS groups of the same name defined on different arrays), SYMAPI attempts to resolve the conflict by renaming the group with an extension to the duplicate group name (such as changing group MyGroup to MyGroup0003). When group names exceed 24 characters, it becomes difficult for SYMAPI to recover.| It is recommended that you limit GNS group names to fewer than 20 characters to avoid this issue.
 |  | The GNS daemon can be configured using the gns_remote_mirror setting within the daemon_options file, to mirror local device groups to remote Symmetrix arrays. This remote mirroring will not be performed if the remote (via SRDF) Symmetrix is also directly connected to the local host. For example, if local Symmetrix S1 is SRDF-connected to Symmetrix S2 and S2 and is also connected locally to the host, groups on S1 will not be mirrored to S2.|
 |  | Running the storapid daemon makes it possible to allow non-privileged users (UNIX, non-Root; Windows, non-Administrator users) to execute SYMAPI applications. However, these users must be given proper access rights to the SYMAPI configuration database file.|
 |  | When VCM is enabled, and all devices are unmasked (not visible) on a port, the symsan command still returns one record. This is because the SCSI specification states that LUN 0 must always respond to SCSI commands on a given port. In this case, the device will be marked Not Ready and may or may not correspond to a mapped device.|
 |  | Unconfigured (empty) disks do not list properly. When all devices on a disk are removed, the symdisk list command output still shows the disk as not empty.| To fix this issue, delete the database (symapi_db.bin) and issue a discover command.|
---|---|---|---|---
 | Solutions Enabler may not get an updated state for the blinking door LED for up to 60 seconds. As result the state reported may not reflect real state of the LED. If a change occurs within the last 60 seconds, the changed state may not be reported.|  |
 | The symchg command cannot be used for remote operations. In addition, the symchg command fails if the following occurs:|  |

●        On IBM AIX platforms, if a physical device is

a member of a volume group. In this case, AIX places a SCSI reservation on the device, which prevents symchg from opening the device properly.

●  A failed device is encountered. If symchg delete fails, you must apply the command to one device at a time for all devices of the group.
 |
 | Configuration Manager| A change in the Enginuity reporting of Spindles to Solutions Enabler causes very large IDs to

be reported. This causes a significant increase in memory used by Solutions Enabler. The increase is approximately 2 MB for each array.

|  |
 |
 | Device masking| An error may return when masking a device if the Symmetrix array director is nonparticipating.|  |
 |  | Attempting to restore a backup file may fail to restore all masking data after a configuration change that results in empty groups.|  |
 | For example, assume you have a port group that contains an FA that was ACLX-enabled when the backup was created. After a configuration

change operation, that same FA is no longer ACLX- enabled. This port will be removed from the port group and any view that contained this group will not be restored. if either the SG or the IG within the view belong to another view that is restored, the masking data is not properly restored.

 |  | symaccess users can explicitly assign the ACLX LUN to the device that has been provisioned by using the -lun option. In addition, the ACLX LUN can be implicitly assigned to a device if none of the ports in the masking view have the show ACLX port flag enabled when the device is initially provisioned to the host. Additional paths provisioned to the host for that device would then continue to use the same LUN (e.g. the ACLX|  |
 |  | LUN). This can cause an ACLX device that was visible to the host on those paths to lose its visibility and may cause the provisioning operation to fail if the ACLX device is being used as the gatekeeper for the operation.|
---|---|---|---
OPT599456| If the array has the FILE guest, the restore operation will not be allowed.|

 | Double Checksum| When using Veritas VxVM with Double Checksum, rejected I/O may cause plexes to become detached.| To return to normal operations, use vxedit to remove the failing status and run vxplex to reattach the plex.
 | The checksum validate option (-validate) does not collapse the extents reported. This may cause the validate action to incorrectly report that too many extents need to be displayed. Typically this would occur in logical volume environments where more than 31 data files are housed in a single volume group.| If the validate action returns an error about the number of extents, it is likely that the enable or disable operations would succeed. Despite this warning, continue with your enable/disable operations.
 | When discard is used, the I/O is processed in 64 kilobyte chunks. If an I/O is rejected, it is rejected in that granularity as well. Therefore, some good blocks may be rejected along with the bad block(s) if they fall within the same chunk.|
 | An operating system patch is required before using Dell Double Checksum on HP-UX 11.23. The patch addresses a retry looping condition when a bad I/O is rejected by the array.| To check and/or fix this problem, consult your HP representative for the Oracle Hard Integrity error patch.

 | HP-UX-specific| For multithreaded environments on HP platforms, you can get a bus error after a pthread_create() call.| Increase your host system stack size setting up to 2 MB or more to circumvent these errors.
 | The syminq hba requires that system log files exist in /var/adm to successfully discover HBAs that are not SNIA compliant. These HBAs may not be reported if the log files are aged, moved, or renamed.| Rebooting the host will refresh HBA information in the system logs, allowing syminq to report the HBA information.
 | Installation and upgrades| When using Native installer commands (such as pkgadd, rpm, swinstall, installp, and setld), uninstall previous versions of Solutions Enabler before upgrading to Solutions Enabler V9.2.4.|
---|---|---|---
 | If the Windows Services Manager application is open while upgrading from a previous version, the installation may fail with the following message: Could not uninstall SYMAPI server.| Closing the Services Manager remedies this problem.
 | When manually creating certificates for secure remote transmissions, there is a possibility that the space in the certificate for server information could be exceeded. Only the hostname can be specified in the Common Name. During the execution of manage_server_cert command you would see the following error: The Common Name may not exceed 55 characters| As a workaround, host names or cluster names can be specified in the -san argument. For

example, you could specify -san a12345678.internal.abc.com. Refer to the EMC VMAX All Flash and VMAX3 Family Security Configuration Guide for details on modifying the certificate.

 | Installation and upgrades| When using Native installer commands (such as pkgadd, rpm, swinstall, installp, and setld), uninstall previous versions of Solutions Enabler before upgrading to Solutions Enabler V9.2.4.|
---|---|---|---
 | If the Windows Services Manager application is open while upgrading from a previous version, the installation may fail with the following message: Could not uninstall SYMAPI server.| Closing the Services Manager remedies this problem.
 | When manually creating certificates for secure remote transmissions, there is a possibility that the space in the certificate for server information could be exceeded. Only the hostname can be specified in the Common Name. During the execution of manage_server_cert command you would see the following error: The Common Name may not exceed 55 characters| As a workaround, host names or cluster names can be specified in the -san argument. For example, you could specify -san a12345678.internal.abc.com. Refer to the EMC VMAX All Flash and VMAX3 Family Security Configuration Guide for details on modifying the certificate.
 | Linux on System z- specific| When running Linux on System z as a z/VM guest, CKD devices must be defined as unsupported DASD and dedicated to the guest. In addition, the module vmcp must be installed so that Solutions enabler is able to query CP as to how a device is defined. Solutions Enabler will not discover any CKD devices not attached in this manner.|
---|---|---|---
 | Linux on System z- specific| When running Linux on System z as a z/VM guest, CKD devices must be defined as unsupported DASD and dedicated to the guest. In addition, the module vmcp must be installed so that Solutions enabler is able to query CP as to how a device is defined. Solutions Enabler will not discover any CKD devices not attached in this manner.|
---|---|---|---
 | NDM| After a symdm commit, the VMAX devices are permanently assigned the VMAX3 and VMAX ALL FLASH device identity (WWN). If the VMAX devices are subsequently deleted and recreated, then the devices will continue to have the VMAX3 and VMAX ALL FLASH device identity, however, the effective device identity will be incorrectly reported by the SYMCLI and Unisphere as having the VMAX device identity.| Once the VMAX device is masked to a host, the reporting of the effective device identity will correctly show the VMAX3 and VMAX ALL FLASH device identity.
---|---|---|---
 | NDM| After a symdm commit, the VMAX devices are permanently assigned the VMAX3 and VMAX ALL FLASH device identity (WWN). If the VMAX devices are subsequently deleted and recreated, then the devices will continue to have the VMAX3 and VMAX ALL FLASH device identity, however, the effective device identity will be incorrectly reported by the SYMCLI and Unisphere as having the VMAX device identity.| Once the VMAX device is masked to a host, the reporting of the effective device identity will correctly show the VMAX3 and VMAX ALL FLASH device identity.
---|---|---|---
17439068| STP| Statistics affected by an ePack are incorrectly reported after the update.| Restart the STP daemon to correctly process statistics after the update.
---|---|---|---
 | TimeFinder| When locally performing a symmir query out to a remote array, the command always returns a 0

value for the invalid tracks of the remote standard device(s) when these devices are in the split state.

|
---|---|---|---
 | When a restore to the R1 device is ready on the link, the -remote option must be specified to acknowledge the remote copy.|
 | When the SYMAPI_WAIT_FOR_BCV_SYNCH

option is set to TRUE and large devices are

in use, a timeout error can result, during a full or incremental establish, or incremental restore operation.

|
 | When operations are performed on a device group, with the -exact option, the pairings of the devices are preserved as they were entered in the device group.

However, when operations are performed on the local devices in a composite group with

the -exact option, the exact pairing operation considers the context of the local array when performing the exact pairing of the standard and BCV devices.

When operations are performed on the remote devices in a composite groups with the -exact option, the exact pairing operation considers the context of the array and associated SRDF group when performing the exact pairing of the standard and BCV devices.

|
 | For proper TimeFinder/Mirror operations with Veritas (VxVM) environments, you must run: vxdctl enable|
 | For Informix environments, symmir and symrdb list actions might ignore showing physical devices that have empty database tables or indexes.|
 | The Enginuity Consistency Assist (ECA) feature can be used to perform consistent split operations. This feature is implemented using the

-consistent option with the symmir split, symclone activate, symclone establish, and symrcopy activate.

The symclone activate command takes advantage of the consistency feature.

To consistently split BCV pairs using ECA you must have either a control host where you are not running data write I/O, or a database host with a dedicated channel to perform the consistent split.

Once the symmir split -consistent

command is issued, I/O to the device group is frozen and a 30 second Enginuity protection timer begins and opens an ECA window. After 30 seconds, the I/O channels are thawed, granting (pent up) operations access to the standard devices. Splits across all devices in a group are considered consistent if the BCV split execution is performed within that window. If for some unknown host or I/O channel reason, not all devices are split within the 30 second window,symmir returns the following at completion:
Consistency window was closed on some devices before the operation completed.
At this point, the final successful split outside the window is no longer considered consistent in execution across the device group. For consistency and reliability, you should re-establish the device group and then (later) attempt the consistent split again.
There are possible instances in a client/server environment that the return error message for a failed TimeFinder operation is vague or incomplete, as shown in the following example with no text after the colon: “BCV Library error is:”
When this occurs, view the SYMAPI log file on the server for the complete error message statement.
When using symmir -rrbcv to verify the states with a LDEV list, always specify the standard and target pairs. Only specifying the standard devices in the LDEV list may not return the correct result.

|
 |  | TimeFinder clone copy session in nocopy mode — In HYPERMAX OS 5977 or higher, when activated, the clone nocopy session shares tracks with source and hence will not initiate any copy when reading from target device. Only when writing to the source or target device is the copy initiated.|
---|---|---|---
 | Virtual Provisioning| Following an allocate operation on a device, the total written track counters incorrectly show the entire device as having been written to.|
---|---|---|---
 | On arrays running HYPERMAX OS 5977 or higher, you can disable devices that have allocated tracks, as long as number of the devices does not exceed twenty percent of the total number of enabled devices (disabled devices are not counted as part of devices in the pool).|

 | z/OS-specific| Do not delete the default Access Control group called UnknwGrp. In addition, the access IDs and access groups should not be removed from the UnknwGrp group. If these items are removed, the Symmetrix array will not be properly discovered.|
 | During the SSL handshake process, the SSL- enabled client does a reverse lookup of host name using the IP address of the Solutions Enabler server to which it is connecting. If the fully qualified host name from the lookup does not match the host’s fully qualified name, an SSL handshake error will occur.| To resolve this, the z/OS certificates may be generated with additional hostnames when the zoscert command is run.

For example, add an alternate hostname like this when prompted by the zoscert command:

To resolve this, the z/OS certificates may be generated with additional
hostnames when the zoscert command is run.
For example, add an alternate hostname like this when prompted by
the zoscert command:

Limitations

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

Table 9. Solutions Enabler V10.0.1 Limitations

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.
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.
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 _ _RPclustername _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.
---|---
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.

Environment and system requirements

Solutions Enabler runs on a wide range of 64-bit operating systems and works with certain HYPERMAX and
PowerMax array versions. For detailed interoperability information, refer to E-Lab Interoperability Navigator at https://elabnavigator.dell.com/eln/elnhome.

Compatibility with older versions
Solutions Enabler V10.0.1 and higher has restrictions added to limit the interoperability/compatibility with older versions of Solutions Enabler. The following new limitations are enforced in V10.0.1 and higher:

• Database files that were originally written by Solutions Enabler versions earlier than V9.0 cannot be read. Database files earlier than V9.0 must be rebuilt. For details on rebuilding the SYMAPI database see Knowledgebase article 000335959.
• CLI compatibility mode only extends back as far as the V9.0 release (-mode V90).
• Client connections to servers older than Solutions Enabler V10.0.1 are rejected.
• The server rejects connections from clients older than Solutions Enabler V9.0.
• Auto provisioning backup files that were originally written by Solutions Enabler versions older than V9.0 are not supported.

NOTE: Due to architectural changes in PowerMaxOS 10, it is recommended to use Solutions Enabler V10.0 or higher clients to manage arrays running PowerMaxOS 10.0 or higher. More information can be found in the KB article 000212258.

Only the following values are supported using the –mode option or the SYMCLI_MODE environment variable:

• V90
• V91
• V92
• V921 – There were changes in CLI output introduced in Solutions Enabler V9.2.1. To satisfy customer needs to see output compatible with V9.2.1 changes, support for V921 compatibility mode was added to Solutions Enabler V10.0 and higher.
• V100

Solutions Enabler support deprecation
The following tables list the features and platforms that are no longer supported in Solutions Enabler V10.0.1.

Table 10. General feature deprecation

deprecated in PowerMaxOS 10. For details, see table symconfigure deprecation for PowerMaxOS 10.
Map/Unmap of CKD devices via symdev is not supported on z/OS and z/VM platforms
Platform deprecation| Windows 2008 and 2008 R2 support deprecated in Solutions Enabler V10.0.
Solaris support is deprecated in Solutions Enabler V10.0.
Feature deprecation| SMI-S Provider is not supported.
 | VSS Provider is not supported.
---|---
SRDF CE is not supported.
PAM support for Authentication is not supported.
Open Migrator is not supported.
symstat functionality has been removed. Unisphere and REST provide performance information.
STP client/server collection on the z/OS platform is deprecated.
STP back-end device stats are deprecated. Solutions Enabler V10.0 does not report TDATs on arrays running PowerMaxOS 10 (6079) and higher.
Reporting total enabled, free and used tracks in the thin pool stats are deprecated.
ORS Port and Device stats are deprecated for arrays running PowerMaxOS 10 (6079) and higher.
Solutions Enabler SRM support is deprecated.
symconfigure device reservation is deprecated.
TimeFinder/Mirror, TimeFinder/VP Snap, TimeFinder/Snap are deprecated.
Write pacing is deprecated.
Support for FTS is removed.
Storstpd is deprecated on the IBM mainframe z/OS platform.
Dynamic Cache Partition (DCP, also known as QOS) stats are deprecated.
SRDF Write Pacing Metrics are deprecated.
Symmetrix Access Control (symacl) is not supported on PowerMax 2500 and PowerMax 8500 arrays.
symreplicate is deprecated in Solutions Enabler V10.0.
Virtual Appliance (vApp) is deprecated in Solutions Enabler V10.0.
Platform deprecation| ViPR Controller is not supported.
Managing arrays running Enginuity 5876 using Solutions Enabler and U4V is deprecated.
Managing arrays running HYPERMAX OS 5977 versions lower than HYPERMAX OS 5977.1131.1131 using Solutions Enabler and U4V is deprecated.
Native support of Sun OS is deprecated.
Native support of BS2000 is deprecated.
Native support of OVMS is deprecated.
Solutions Enabler support on Linux Itanium IA 64 is deprecated.
Native support of LINUX__2_6_PPC64 (Linux PowerPC 64bit) is deprecated.
Support of Redhat 6.9 is deprecated.

The following table details the symconfigure command changes (replaced by symcfg/symdev commands) for PowerMaxOS 10.

Table 11. symconfigure deprecation for PowerMaxOS 10

Planned deprecation

Table 12. Planned future support deprecation in Solutions Enabler

and

9.1 is planned to be deprecated in the 10.1 release of Solutions Enabler.

Support for RHEL 8.0 is planned to be deprecated in the 10.1 release of Solutions Enabler.
SuSe Linux 12 SP 4 and earlier versions are planned to be deprecated in the next release of Solutions Enabler.

Installation and upgrade considerations

Detailed installation and upgrade procedures for Solutions Enabler V10.0.1 are provided in the Dell Solutions Enabler Installation and Configuration Guide.

Where to get help
You can use these resources to find more information about this product, get support and provide feedback.

Related documentation

Dell Solutions Enabler Release Notes
Describes new features and any known limitations.

Dell Solutions Enabler Installation and Configuration Guide
Provides host-specific installation instructions.

Dell Solutions Enabler CLI Reference Guide
Documents the SYMCLI commands, daemons, error codes and option file parameters provided with the Solutions Enabler man pages.

Dell Solutions Enabler Array Controls and Management CLI User Guide
Describes how to configure array control, management, and migration operations using SYMCLI commands for arrays running HYPERMAX OS and PowerMaxOS.

Dell Solutions Enabler SRDF Family CLI User Guide
Describes how to configure and manage SRDF environments using SYMCLI commands.

Dell Solutions Enabler SRDF Family State Tables Guide
Describes the applicable pair states for various SRDF operations.

SRDF Interfamily Connectivity Information
Defines the versions of PowerMaxOS, HYPERMAX OS and Enginuity that can make up valid SRDF replication and SRDF/Metro configurations, and can participate in Non-Disruptive Migration (NDM).

Dell SRDF Introduction
Provides an overview of SRDF, its uses, configurations, and terminology.

Dell Solutions Enabler TimeFinder SnapVX CLI User Guide
Describes how to configure and manage TimeFinder SnapVX environments using SYMCLI commands.

Dell Solutions EnablerTimeFinder Clone CLI User Guide
Describes how to configure and manage TimeFinder Clone environments for HYPERMAX OS and PowerMaxOS using SYMCLI commands.

Dell SRDF/Metro vWitness Configuration Guide
Describes how to install, configure, and manage SRDF/Metro using vWitness.

Dell Events and Alerts for PowerMax and HYPERMAX User Guide
Documents the SYMAPI daemon messages, asynchronous errors and message events, SYMCLI return codes, and how to configure event logging.

Where to find product documentation

• https://www.dell.com/support/home/en-ie
• https://www.dell.com/en-us/dt/documentation/vmax-all-flash-family.htm

Where to find the support matrix
For the latest support information, consult the Dell Support Matrix. It is available at https://elabnavigator.dell.com.

Where to get support
Dell support, product, and licensing information can be obtained on the Dell Online Support site as described next.

NOTE: To open a service request through the Dell Online Support site, you must have a valid support agreement. Contact your Dell sales representative for details about obtaining a valid support agreement or to answer any questions about your account.

Your comments
Your suggestions help improve the accuracy, organization, and overall quality of the documentation. Send your comments and feedback to: powermaxcontentfeedback@dell.com

Notes, cautions, and warnings

NOTE: A NOTE indicates important information that helps you make better use of your product.

CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem.

WARNING: A WARNING indicates a potential for property damage, personal injury, or death.

© 2023 Dell Inc. or its subsidiaries. All rights reserved. Dell Technologies, Dell, and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be trademarks of their respective owners.

Read User Manual Online (PDF format)

Read User Manual Online (PDF format)  >>

Download This Manual (PDF format)

Download this manual  >>