Cisco Nexus 7000 Design Manual page 51

•
•
•
For information on the cluster interconnect switch configuration provided by NetApp, see:
Note
https://library.netapp.com/ecm/ecm_get_file/ECMP1115327
The solution defines a single infrastructure Vserver to own and export the necessary data to run the
VMware vSphere infrastructure. This Vserver specifically owns the following flexible volumes:
•
•
•
•
•
•
•
The NFS datastores are mounted on each VMware ESXi host in the VMware cluster and are provided
by NetApp clustered Data ONTAP through NFS over the 10GbE network.
The Vserver essentially has a minimum of one LIF per protocol per node to maintain volume availability
across the cluster nodes. The LIFs use failover groups, which are network polices defining the ports or
interface groups available to support a single LIF migration or a group of LIFs migrating within or across
nodes in a cluster. Remember, multiple LIFs may be associated with a network port or interface group.
In addition to failover groups, the clustered Data ONTAP system uses failover policies. Failover polices
define the order in which the ports in the failover group are prioritized. Failover policies define migration
policy in the event of port failures, port recoveries, or user-initiated requests.
The most basic possible storage failover scenarios in this cluster are as follows:
•
•
The remaining node network connectivity failures are addressed through the redundant port, interface
groups, and logical interface abstractions afforded by the clustered Data ONTAP system.
FlexPod Discrete Uplink Design with Data ONTAP Operating in 7-Mode
Figure 23
storage controllers with shared media. 7-Mode does not scale beyond a single pair of controllers as
compared to the clustered Data ONTAP. From a design perspective, the Cisco Nexus and Cisco UCS
component configurations are identical to the previously defined FlexPod configuration with clustered
Data ONTAP. The differences reside only with the NetApp storage domain.
Ports c0a and c0b on each node support the HA interconnect processes. These connections do not
support any data traffic but only control processes.
Ports e1a and e2a are cluster interconnect ports for data traffic. These ports connect to each of the
Cisco Nexus 5596 cluster interconnect switches.
The Cisco Nexus cluster interconnect switches support a single ISL port channel (Po1).
Root volume—A flexible volume that contains the root of the Vserver namespace.
Root volume load-sharing mirrors—A mirrored volume of the root volume to accelerate reads
throughput. In this instance it is labeled root_vol_m01 and root_vol_m02.
Boot volume—A flexible volume that contains ESXi boot LUNs. These ESXi boot LUNs are
exported through FC/FCoE to the Cisco UCS servers.
Infrastructure datastore volume—A flexible volume that is exported through NFS to the ESXi
host and is used as the infrastructure NFS datastore to store VM files.
Infrastructure swap volume—A flexible volume that is exported through NFS to each ESXi host
and used to store VM swap data.
OnCommand_DB—A flexible volume supporting a Fibre Channel LUN for OnCommand services.
RDM_MAP—A flexible volume supporting a Fibre Channel–accessible VMFS datastore for
storing Raw Device Mapping (RDM) files.
Node1 fails, and Node2 takes over Node1's storage.
Node2 fails, and Node1 takes over Node2's storage.
shows the FlexPod with Data ONTAP operating in 7-Mode. 7-Mode consists of only two
VMware vSphere 5.1 on FlexPod with Nexus 7000 Using FCoE
FlexPod Implementation and Design
51