Configure a StorNext DLC Client with a Single Network Interface

The scenario above is supported if your StorNext appliance is running StorNext 6.2 or higher.

Note: The StorNext client can run StorNext 6.x or StorNext 5.x.

The fsnamservers file on the appliance contains the IP addresses of the private metadata network. The fsnameservers file on the clients contains the public IP address of the appliance. This covers the metadata traffic between the clients and the MDCs, which are also configured to be coordinators for the cluster.

The DLC client must have connectivity to a DLC gateway. It is common to have the MDCs to be configured as gateways. It is also common to have additional StorNext nodes configured as gateways. All gateways must have access to the file system disks, usually connected via fibre channel. It is also common that these gateways would have connectivity to the private metadata network for the MDCs. The dpserver file on the gateways is used to configure which addresses are advertised to DLC clients. The gateways could advertise both the private IP address and the public IP address. The client with only access to the public network would connect to the gateway using the public address. The client winds up with a TCP connection to the active FSM and a TCP connection to every gateway. Metadata traffic goes to and from the active FSM. Data traffic is load balanced among all available gateways.

For example:

MDC1 fsnameservers

MDC2 fsnameservers

Client fsnameserver

MDC1 dpserver

MDC2 dpserver

Note: The DLC client does not require DLC configuration.