Release Notes

Table Of Contents
If you are unable to correct the iSCSI connection failure, try the following steps:
a. Reboot the computer.
b. Use the Windows Device Manager and look for devices that appear to be having problems.
For those devices, reinstall the existing driver (use the default response no at the prompts) and then reboot the server.
Windows OS Error When iSCSI Session Limit Reached
A maximum limit of 255 iSCSI sessions is permitted by the Windows operating system. When you reach this limit, the operating
system displays the following iSCSI error:
SDSC_TOO_MANY_SESSIONS: Unspecified Error 0xefff001e
Connecting a Host With HBAs to a PS Series Group on a Dedicated Network
If your host system uses HBAs on a dedicated network to access your PS Series groups, configure ASM/ME to register the
discovery address using only these HBAs. In the ASM/ME GUI, click Settings PS Group Access. Select the checkbox for Use
Host Bus Adapters when you configure the PS Series group access. This checkbox appears only if the HIT host has HBAs
installed, or an initiator other than the default software initiator.
If a HIT host has HBAs and default network interfaces, the iSCSI traffic is restricted to only the HBA network interfaces, and
you select the checkbox to verify the connection to the group, you might see the following error:
Error saving PS Group group_name: Specified group WKAddress is not reachable.
If the Verify connection checkbox is not selected, ASM will add the new group entry but subsequent attempts to edit it will fail.
With the Use Host Bus Adapters option set, if the ping test fails, ASM will ignore the failure and attempt to register the new PS
Series group. If one HBA succeeds, the group is added.
General Operational
The following operational usage constraints apply in this release for all supported operating systems.
ASM/ME
ASM/ME does not support Dell Storage Center arrays. Using ASM/ME, you cannot set up a cross-platform replication to a
volume on an SC array because ASM/ME does not recognize the SC array as a replication partner.
Remote Verification
To perform remote verification for clones, the remote verification server must have access to the corresponding volume.
To perform remote verification for replicas, the remote verification server must have access to the replication partner group.
The remote server must not have any access to the source volumes. If the remote server accesses the original volume, data
corruption can occur.
Remote Host Settings for Exchange Replica Smart Copy Verification
One of the options to verify a replica Smart Copy of an Exchange component is to promote the replica set to a recovery volume
and perform verification. To use this option, the remote host only needs access to the replication partner group. The remote
host must not have any access to the source volumes. If the remote host accesses the original volume, data corruption can
occur.
Remote Host Settings for Verifying Snapshots and Clones
To verify snapshots and clones on the remote host, the remote host must have access to the corresponding volumes.
8