Dell VNXe3300 VNXe Series Using a VNXe System with VMware - Page 10

Requirements for setting up a host to use VNXe VMware NFS datastores, VNXe system requirements

Page 10 highlights

Setting Up a Host to Use VNXe VMware NFS Datastores Requirements for setting up a host to use VNXe VMware NFS datastores Before you can set up a host to use VNXe NFS datastores, the following VNXe system and network requirements described in this section must be met. VNXe system requirements ◆ You have installed and configured the VNXe system using the VNXe Configuration Wizard, as described in the EMC VNXe3100 System Installation Guide, the EMC VNXe3150 Installation Guide, or the EMC VNXe3300 System Installation Guide. ◆ You have used Unisphere or the VNXe CLI to perform basic configuration of one or more VNXe Shared Folder Servers on the VNXe system. Network requirements The host must be in a LAN environment with the VNXe Shared Folder Storage Server. Users can store files on a VNXe Shared Folder Server in a Network Information Service (NIS) environment, but you cannot configure a VNXe Shared Folder Server as an NIS client. Using network high availability The VNXe system provides network high-availability or redundancy with Fail-Safe Networks (FSNs) that extend link failover out into the network by providing switch-level redundancy. On a VNXe system, each port on a storage processor (SP) is configured in an FSN with the corresponding port on the peer SP. When you assign a port to a VNXe Shared Folder Server interface, the VNXe automatically designates that port on the SP where the Shared Folder Server resides as the primary port in the FSN and the port on the peer SP as the secondary port in the FSN. You cannot create, delete, or change the configuration of the VNXe FSNs. For these reasons, to take advantage of FSN in a VNXe3100 system with two SPs, a VNXe3150 with two SPs, or a VNXe3300 system, the Ethernet (eth) ports on each SP must be cabled identically. For example if you cable eth2 and eth4 ports on SP A and create a separate storage server on each port, you must cable eth2 and eth4 ports on SP B the same way. In addition, the VNXe system supports link aggregations that allows up to four Ethernet ports connected to the same physical or logical switch to be combined into a single logical link. This behavior is called link aggregation. To configure link aggregation on a VNXe system, each storage processor (SP) must have the same type and number of Ethernet ports because configuring link aggregation actually creates two link aggregations - one on each SP. This provides high availability as follows. 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 all the ports in the aggregation fail, FSN fails over to the corresponding link aggregation on the peer SP so that network traffic continues. If you add an Ethernet I/O module to each SP in a VNXe 3100, 3150, or 3300 system, you can create one additional link aggregation group on the set of ports in the I/O module. The rest of this section describes: ◆ "Fail-Safe Networks" on page 11 ◆ "Link aggregations" on page 12 10 Using a VNXe System with VMware NFS or VMware VMFS

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34

10
Using a VNXe System with VMware NFS or VMware VMFS
Setting Up a Host to Use VNXe VMware NFS Datastores
Requirements for setting up a host to use VNXe VMware NFS
datastores
Before you can set up a host to use VNXe NFS datastores, the following VNXe system and
network requirements described in this section must be met.
VNXe system requirements
Y
ou have installed and configured the VNXe system using the VNXe Configuration
Wizard, as described in the
EMC VNXe3100 System Installation Guide
, the
EMC
VNXe3150 Installation Guide
, or the
EMC VNXe3300 System Installation Guide
.
You have used Unisphere or the VNXe CLI to perform basic configuration of one or
more VNXe Shared Folder Servers on the VNXe system.
Network requirements
The host must be in a LAN environment with the VNXe Shared Folder Storage Server.
Users can store files on a VNXe Shared Folder Server in a Network Information Service
(NIS) environment, but you cannot configure a VNXe Shared Folder Server as an NIS client.
Using network high availability
The VNXe system provides network high-availability or redundancy with Fail-Safe
Networks (FSNs) that extend link failover out into the network by providing switch-level
redundancy. On a VNXe system, each port on a storage processor (SP) is configured in an
FSN with the corresponding port on the peer SP. When you assign a port to a VNXe Shared
Folder Server interface, the VNXe automatically designates that port on the SP where the
Shared Folder Server resides as the primary port in the FSN and the port on the peer SP as
the secondary port in the FSN. You cannot create, delete, or change the configuration of
the VNXe FSNs. For these reasons, to take advantage of FSN in a VNXe3100 system with
two SPs, a VNXe3150 with two SPs, or a VNXe3300 system, the Ethernet (eth) ports on
each SP must be cabled identically. For example if you cable eth2 and eth4 ports on SP A
and create a separate storage server on each port, you must cable eth2 and eth4 ports on
SP B the same way.
In addition, the VNXe system supports link aggregations that allows up to four Ethernet
ports connected to the same physical or logical switch to be combined into a single logical
link. This behavior is called link aggregation. To configure link aggregation on a VNXe
system, each storage processor (SP) must have the same type and number of Ethernet
ports because configuring link aggregation actually creates two link aggregations — one
on each SP. This provides high availability as follows. 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 all the ports in the aggregation fail, FSN fails over to the corresponding link
aggregation on the peer SP so that network traffic continues. If you add an Ethernet I/O
module to each SP in a VNXe 3100, 3150, or 3300 system, you can create one additional
link aggregation group on the set of ports in the I/O module.
The rest of this section describes:
“Fail-Safe Networks” on page 11
“Link aggregations” on page 12