Administrator Guide

• All EqualLogic SAN ports by way of the EqualLogic Group IP
• NAS cluster SAN Management Virtual IP (VIP) address
• Physical SAN ports on every NAS controller and SAN IP address
NOTE: Ports referred to here are physical and do not refer to TCP/IP port numbers opened through the TCP/IP stack
using an application.
Table 51. TCP/IP Port Numbers shows the ports that must be open on the rewall.
Table 51. TCP/IP Port Numbers
Function Protocol Port Number(s)
Replication setup ports SSH, TCP 22, 26, and 3260
Replication data ports TCP 2-Controller Cluster: 10560-10568
4-Controller Cluster: 10560-10576
Ephemeral ports TCP 40000 - 65535
NOTE: The ephemeral port range denes the range of TCP ports allocated by the TCP/IP stack on EqualLogic arrays and
FS Series NAS appliances for initiating communications to other EqualLogic arrays or FS Series NAS appliances. For
example, when conguring replication between two NAS clusters, an ephemeral port (from the range in table above),
such as 41020, is selected on the source NAS cluster and establishes a connection to TCP port 22 on the destination
NAS cluster.
NAS Replication WAN Network Requirements
Replication is possible over a WAN only when the partner system is accessible through a gateway to the Internet or private WAN.
When replicating over a WAN, you must have a static route in addition to the regular partnership setup. The WAN can be the public
Internet or a private network. Because NAS replication transfers data over the SAN network, you have to have static routes to route
replication packets through the designated gateway on the SAN network.
A static route provides a network path for the NAS cluster and the NAS controllers to the SAN IP addresses for the partnered NAS
cluster and NAS controllers.
When you congure NAS replication between two clusters, static routes are added on both clusters automatically from the list of
default gateways on members in the EQL group. Optionally, you can change the automatically specied static routes. You can specify
a dierent gateway for the static route or add or delete static routes for replication if the automatic method fails for any reason. The
number of static routes that can be congured is not limited. If a static route needs to be modied, delete the static route and then
add the static route back with the updated information.
NOTE: You can manually congure the NAS static routes only using the CLI. You cannot congure static routes using the
Group Manager GUI.
If you modify the SAN network settings of a cluster, the software tries to automatically update all the partner clusters. However, to
ensure continued operation, static routes on all the partner clusters should be veried by the administrators.
NOTE:
• The static routes need to be updated on partner clusters, not the cluster whose SAN network changed.
• Jumbo frames are not required when connecting over a WAN network.
You can use the following SAN network CLI commands to add, delete, or show static routes:
• nas-cluster select network select static-route add
• nas-cluster select network select static-route delete
• nas-cluster select network select static-route show
For more information about these CLI commands, see the Dell EqualLogic Group Manager CLI Reference Guide.
About Data Recovery
281