Release Notes

Windows Firewall Settings on Failover Cluster
If you are using the native Windows firewall on your failover cluster and you want to use the Dell EqualLogic Multipath I/O
DSM, you must configure your firewall to allow ICMP echo requests (pings) for ICMPv4 and ICMPv6. The installation procedure
detects the firewall and gives you the option to amend your firewall configuration automatically.
Use the iSCSI Initiator Properties Page Extension to verify that Multipath I/O is working correctly.
If you do not configure the firewall automatically at installation time but you still want to use multipathing, you must configure
your firewall manually to allow ICMP requests. The following command-line examples show typical firewall configuration rules:
netsh advfirewall firewall add rule name="Dell EqualLogic MPIO Ping IPv4" dir=in
action=allow description="Dell EqualLogic MultiPath I/O Ping rule" enable=yes profile=any
localip=any remoteip=any protocol=icmpv4
netsh advfirewall firewall add rule name="Dell EqualLogic MPIO Ping IPv6" dir=in
action=allow description="Dell EqualLogic MultiPath I/O Ping rule" enable=yes profile=any
localip=any remoteip=any protocol=icmpv6
Refer to the documentation for your version of the Windows operating system for instructions on how to configure a firewall.
Network Folder Repository for Smart Copy Backup Documents
When you run ASM/ME on a Windows failover cluster, you must specify a shared network folder as a repository for the Smart
Copy backup documents. Each node in the cluster must be able to access the folder. In addition, if you are sharing a PS Series
group between several failover clusters, each cluster must have its own shared network folder. You cannot use a single shared
network folder between multiple clusters for storing backup documents.
iSCSI Initiator
This section contains general constraints pertaining to the iSCSI initiator.
iSCSI Initiator Connection Failure
Under rare conditions, the iSCSI Software Initiator might not connect to storage devices, including PS Series volumes and the
vss-control volume, which Microsoft services use to communicate with a PS Series group. Although the login to the volume
appears to succeed, the connection is not established.
For example, the iSCSI initiator console will not show any device details for the target, and the volume will not appear in the
Windows Disk Management utility.
The iSCSI initiator will automatically attempt to correct the problem. However, if the problem persists, you might be able to
correct to it using the following procedure:
1. Double-click the iSCSI initiator icon to open its properties and click the Targets tab.
2. Log out of the affected iSCSI target.
3. From the Discovery tab, remove the group IP address from the list of target portals.
4. Specify the group IP address that you removed from the list of target portals in step 3 as a target portal, then start a new
discovery session to this address.
5. Log in to the volumes.
You might need to click Advanced to specify host bus adapter information or CHAP login credentials.
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.
7