Non-file serving interfaces
NAS servers provide non-file serving physical interfaces. These interfaces use standard RJ45 connectors.
The servers use auto-negotiation for speed/duplex/flow control by default. We recommend a 1Gbps speed for the switch uplink port for the non-file serving interfaces with full duplex, bi-directional flow control enabled.
A non-file serving interface must be connected to access the internal NAS Manager and to use the following features:
- V2I
- VASA Provider
- Data Migrator to Cloud (DM2C)
NAS module
These models provide a single 10/100/1000 Ethernet non-file serving interface. It is possible to connect to this interface as follows:
- SSH to either the "Unified Management IP Address" (shown in the IP Addresses page of the NAS Manager) or the address shown on the maintenance utility "Network Settings" page.
- SSC to either the "Unified Management IP Address" or the address shown on the maintenance utility "Network Settings" page.
Connecting to the NAS module using these IP addresses provides the user with a command line interface. See the CLI Reference manual for available commands.
To access the NAS Manager in a Web browser, use the "Unified Management IP Address" appended with the port number 20443. The browser connection must be secure (HTTPS).
HNAS server
These models provide two 10/100/1000 Ethernet non-file serving interfaces as follows:
- eth1
- eth0
eth1
This interface is mandatory and enables users to communicate with the NAS Manager, any auxiliary devices, and the non-file serving interfaces of other HNAS servers. During initial setup of the HNAS server, this interface is configured with an IP address. This interface can also be configured with a separate cluster node IP address if the server is intended to be part of a cluster.
eth0
This interface is optional and enables the user to configure file services on the server as well as create and configure Enterprise Virtual Servers (EVSs). For example, when using SyncDR, the Admin EVS needs to be on eth0.
During initial setup of the HNAS server, this interface is configured with an IP address. Connecting to the HNAS server using this IP address enables direct access to the server management interface and provides users with a command line interface. See the CLI Reference manual for available commands.
Aggregate Linux interfaces
The NAS server provides the ability to access the file serving interfaces (agX) from Linux, using a virtual Linux network interface (eth-agX), which is bound to a specific agX interface as shown below:
Using an aggregate Linux interface (instead of eth0 or eth1) provides a potentially faster route for data and management traffic. It also enables the non-file serving interfaces (eth0 and eth1) and the file serving aggregations to be physically separate while providing Linux access to both sets of interfaces.
Example
For the scenario below:
The Administrator can create eth-ag1 over ag1 as shown below:
aggregate-linux-interface-create --interface ag1
Now, any functionality that is available on eth0 and eth1, is also available on the file serving interfaces. This can include using SSH with the Admin EVS IP address.
For information on how to manage the eth-agX interfaces, see the following CLI commands:
- aggregate-linux-interfaces
- aggregate-linux-interface-show
- aggregate-linux-interface-create
- aggregate-linux-interface-delete
Typical non-file serving interface configurations: NAS module
There are two typical configurations for the NAS module non-file serving interface:
- Single network for both management and file-serving functionality
- Separate networks for management and file-serving functionality
All NAS module configurations use the embedded SMU.
Single network for both management and file-serving functionality
In this configuration, the NAS module is connected to a single LAN and both the file-serving interfaces and the non-file serving interface connect to this network.
Separate networks for management and file-serving functionality
In this configuration, the non-file serving interface on the NAS module is connected to the management network and the file-serving interfaces are connected to a data network.
Typical non-file serving configurations: HNAS servers
There are three typical configurations for non-file serving interfaces on a NAS Platform Series 4000 and NAS Platform Series 5000 :
- Single HNAS server (embedded SMU)
- Single HNAS server (external SMU)
- Clustered HNAS servers (external SMU)
Single HNAS server (embedded SMU)
In this configuration, the HNAS server uses an embedded SMU (NAS Manager) where eth1 is connected to the private management network and eth0 is connected to the public management network.
Single HNAS server (external SMU)
In this configuration, the HNAS server uses an external SMU. This is necessary when maintaining external configuration backups and also when preparing the HNAS server to join a cluster. In this case, eth1 on the HNAS server and eth1 on the SMU are connected to the same private management network, and eth0 on the HNAS server is optionally connected to the public management network.
Clustered HNAS servers (external SMU)
In this configuration, the HNAS server is part of a cluster with an external SMU. In this case, eth1 on each HNAS server and eth1 on the SMU are connected to the same private management network, and eth0 on each HNAS is optionally connected to the public management network.
