This topic describes the IP network considerations for implementing
the SAN File System.
SAN File System supports two to eight metadata servers, each running on
a separate engine. Each engine has at least two IP addresses, one for the
metadata server and one for the RSA:
- Copper or fiber Ethernet adapter is used by the metadata servers to communicate
with each other and the clients through an existing IP network.
- RSA, which uses copper Ethernet cabling, is used to establish
a remote console to the engine from the master console.
To set up an IP network for SAN File System:
- Assess the requirements for the interaction of your existing LANs, with
the SAN File System clients and metadata servers. Your requirements should
include administrative LAN connections to new SAN hardware, storage devices,
and SAN File System engines. SAN File System requires a low latency network
for metadata-server-to-metadata-server and metadata-server-to-client communication.
- Determine if the existing LAN has enough switch ports for the metadata
servers.
- Determine which software modifications will be needed to support the resulting
LAN topology (clients, servers, and switches).
- Determine which hardware modifications, including network interface cards,
cabling, and switches, are needed to support the required LAN topology.
Tip: - The metadata server IP addresses must be on a common subnet.
- The IP network over which the metadata servers and client communicate
must be secure, using physical security or IPSec.