Setting up a host to use Unity VMware NFS datastores
Requirements for setting up a host
These system and network requirements must be met before setting up a host to use Unity storage.
Before you can set up a host to use Unity storage, the following storage system and network requirements must be met.
This topic lists the network requirements for a host attaching to a Unity system.
Ensure that you meet these network requirements:
- The host (client) is in the same LAN environment as the Unity NAS server.
- If the NAS server is enabled for multiprotocol (CIFS and NFS), you have connected it to an NIS server or an LDAP server. The Unisphere online help describes how to configure Unix Directory Service (either NIS or LDAP) on the system.
Note: Users can store files on a Unity NAS server in a Network Information Service (NIS) environment, but you cannot configure a Unity NAS server as an NIS client.
Using network high availability
This topic describes how to use link aggregation for high availability configurations.
The Unity system supports link aggregations that allow up to four Ethernet ports connected to the same physical or logical switch to be combined into a single logical link. To configure link aggregation on the system, each storage processor (SP) must have the same type and number of Ethernet ports as link aggregation actually creates two link aggregations — one on each SP. This provides high availability. If one of the ports in the link aggregation fails, the system directs the network traffic to one of the other ports in the aggregation. If you add an Ethernet I/O module to each SP in the system, you can create one additional link aggregation group (LAG) on the set of ports in the I/O module.
This topic describes the advantages and function of link aggregations.
Link aggregations use the Link Aggregation Control Protocol (LACP) IEEE 802.3ad standard.
Note: Link Aggregation does not apply to iSCSI interfaces.
A link aggregation appears as a single Ethernet link with these advantages:
- High availability of network paths to and from the Unity system — If one physical port in a link aggregation fails, the system does not lose connectivity.
- Possible increased overall throughput — Because multiple physical ports are bonded into one logical port with network traffic distributed between the multiple physical ports.
Although link aggregations can provide more overall bandwidth than a single port, the connection to any single client runs through one physical port and is therefore limited by the port’s bandwidth. If the connection to one port fails, the switch automatically switches traffic to the remaining ports in the group. When the connection is restored, the switch automatically resumes using the port as part of the group.
On the Unity system, you can configure up to four ports in a link aggregation. When you configure a link aggregation, you are configuring two link aggregations — one on each SP. If one of the ports in an aggregation fails, the system directs network traffic to one of the other ports in the group.
This topic describes switch requirements when using link aggregation.
If the Unity ports are connected to different network switches, you should configure all switch ports connected to these ports to immediately switch from blocking mode to forwarding mode and not pass through spanning tree states of listening and learning when an interface comes up. On Cisco switches, this means that you must enable the portfast capability for each switch port connected to a Unity port to guarantee that the switch forwards the Ethernet frame that the storage system generates when a physical link is enabled. You enable the portfast capability on a port-to-port basis. When enabled, the portfast variable causes the port to immediately switch from blocking to forwarding mode. Do not use portfast on switch-to-switch connections.
For link aggregation, network switches must have IEEE 802.3ad protocol support and guarantee that packets from a single TCP connection always go through the same link in a single direction.
Configuring a link aggregation
This topic describes link aggregation configuration and lists the required configuration tasks.
For link aggregation, you have at least one 802.3ad-compliant switch, each with an available port for each switch port you want to connect to a Unity port in the aggregation.
The term NIC teaming refers to all NIC redundancy schemes, including link aggregation with 802.3ad.
For link aggregation, you need to perform two sets of configuration tasks:
- Configure a link aggregation from the switch to the Unity system
- Configure a link aggregation from the host to the switch
Configuring link aggregation from the switch to the Unity system
Learn how to configure the switch ports and join them into a link aggregation.
- Configure the switch ports, which are connected to the Unity system, for LACP in active mode. Refer to the documentation provided with your switch for details.
- Join the ports into a link aggregation using Unisphere. To do this:
- Select the Settings icon, then select .
- Select an Ethernet port, then select .
- Select the ports for the link aggregation, then select Create.
Configuring link aggregation from the ESXi host to the switch
- Configure the switch ports for link aggregation.
Note: Depending on the type of NIC teaming used, you may not need to configure these switch ports for link aggregation. For more information, refer to your VMware documentation.
- On an ESXi host, you create a NIC team by creating a virtual switch with two or more physical NICs. For information on creating a virtual switch, refer to the VMware documentation for the version of ESXi running on the host.
Configuring Unity NFS datastores for the host
Use the Unisphere UI or CLI to:
- Discover VMware ESXi hosts.
- Create NFS datastores.
When you create NFS datastores for discovered VMware ESXi hosts, the Unity system automatically configures the hosts to use the datastores. If you select multiple hosts to have access to the NFS datastore, all the selected hosts are configured automatically.Note: The Unity system automatically mounts NFS datastores as NFSv3.0. NAS servers using Kerberos security use NFSv4.1. In order to use NAS servers enabled for Kerberos or NFSv4 for Unity NFS datastores, you must manually mount the datastores. Refer to Configuring Unity NFS datastores for the host
For more information on performing these tasks, refer to the Unisphere online help or Unisphere CLI User Guide.
Manually setting up the connection to a Unity NFS datastore
Manually set up the connection to an NFS datastore if you are using generic host objects, or if you want to mount NFS datastores as NFSv4 and later.
- In Unisphere, find the IP address of the NAS server for the NFS datastore.
- Under Storage, select .
- Select the NFS datastore and click the Edit icon to view its properties. On the General tab, note the Export Paths.
For example, for Export Path 10.0.0.1/nfsdatastore123, 10.0.0.1 is the IP address of the NAS server for NFS datastore nfsdatastore123.
- Log into vSphere as an administrator.
- For each NFS datastore:
- On the Inventory panel, select the host and click the Configuration tab.
- On the Hardware panel, click Storage, then Add Storage.
- Select Network File System as the file storage type.
- Enter the following information:
- For server, enter the IP address of the Unity NAS server.
- For folder, enter the path to the Unity share.
- For name, enter the name of the new VMware datastore.