NetApp and VMware vSphere Storage Best Practices

Recommendations

Info

10.2 VMKERNEL CONFIGURATION WITH TRADITIONAL ETHERNET If the switches to be used for IP storage networking do not support multi-switch Etherchannel trunking, or virtual port channeling, then the task of providing cross-switch redundancy while making active use of multiple paths becomes more challenging. To accomplish this, each ESX Server must be configured with at least two VMkernel IP storage ports addressed on different subnets. As with the previous option, multiple datastore connections to the storage controller are necessary using different target IP addresses. Without the addition of a second VMkernel port, the VMkernel would simply route all outgoing requests through the same physical interface, without making use of additional VMNICs on the vSwitch. In this configuration, each VMkernel port is set with its IP address on a different subnet. The target storage system is also configured with IP addresses on each of those subnets, so the use of specific VMNIC interfaces can be controlled. ADVANTAGES • Provides two active connections to each storage controller (but only one active path per datastore). • Easily scales to more connections. • Storage controller connection load balancing is automatically managed virtual port load balancing policy. This is a non-Etherchannel solution. DISADVANTAGE • Requires the configuration of at least two VMkernel IP storage ports. In the ESX Server configuration shown in Figure 33, a vSwitch (named vSwitch1) has been created specifically for IP storage connectivity. Two physical adapters have been configured for this vSwitch (in this case vmnic1 and vmnic2). Each of these adapters is connected to a different physical switch. Figure 33) ESX Server physical NIC connections with traditional Ethernet. 52
In vSwitch1, two VMkernel ports have been created (VMkernel 1 and VMkernel 2). Each VMkernel port has been configured with an IP address on a different subnet, and the NIC Teaming properties of each VMkernel port have been configured as follows. • VMkernel 1: IP address set to 192.168.1.101. • VMkernel 1 Port Properties: o Enable the Override vSwitch Failover Order option. o For NFS and iSCSI set Active Adapter to vmnic1. o For NFS set Standby Adapter to vmnic2. o For iSCSI set no Standby Adapters. • VMkernel 2: IP address set to 192.168.2.101. • VMkernel2 Port Properties: o Enable the Override vSwitch Failover Order option. o For NFS and iSCSI set Active Adapter to vmnic2. o For NFS set Standby Adapter to vmnic1. o For iSCSI set no Standby Adapters. Figure 34) ESX Server VMkernel port properties with traditional Ethernet. 53
Page 1 and 2: NETAPP TECHNICAL REPORT NetApp and
Page 3 and 4: 9 ETHERNET STORAGE NETWORKING BEST
Page 5 and 6: 1 EXECUTIVE SUMMARY NetApp® techno
Page 7 and 8: 2.2 STORAGE OVERVIEW: NAS DATASTORE
Page 9 and 10: 2.4 DATASTORE COMPARISON TABLES Dif
Page 11 and 12: 3 NETAPP FAS CONFIGURATION AND SETU
Page 13 and 14: LUNS LUNs are units of storage prov
Page 15 and 16: Figure 5) Identifying WWPN and IQN
Page 17 and 18: Figure 7) Assigning an igroup to a
Page 19 and 20: The default block size of a virtual
Page 21 and 22: CREATE MULTIPLE ISCSI VMKERNELS 1 O
Page 23 and 24: Figure 13) Verifying iSCSI to VMker
Page 25 and 26: Figure 15) Configuring iSCSI dynami
Page 27 and 28: Alternatively iSCSI restrictions ca
Page 29 and 30: 5.2 ENABLING ALUA NetApp and VMware
Page 31 and 32: Figure 20) Listing the active PSP t
Page 33 and 34: MANUALLY SETTING THE PSP FOR A LUN
Page 35 and 36: 6 NFS STORAGE RECOMMENDATIONS 6.1 I
Page 37 and 38: It is common for customers who run
Page 39 and 40: 6.5 CONNECTING NFS DATASTORES TO cr
Page 41 and 42: Figure 27) VMware Add Storage Wizar
Page 43 and 44: 7 THE NETAPP ESX HOST UTILITIES Net
Page 45 and 46: 8 FC AND FCOE STORAGE NETWORKING BE
Page 47 and 48: Figure 29) Configuring flow control
Page 49 and 50: 10 CONFIGURING ETHERNET STORAGE NET
Page 51: Figure 31) ESX vSwitch1 normal mode
Page 55 and 56: THE SINGLE-MODE DESIGN The single-m
Page 57 and 58: 10.5 VMKERNEL CONFIGURATION WITH MU
Page 59 and 60: 10.6 A STORAGE ARCHITECTURE WITH MU
Page 61 and 62: 11 INCREASING STORAGE UTILIZATION V
Page 63 and 64: Figure 43) Storage consumption afte
Page 65 and 66: Traditional provisioning preallocat
Page 67 and 68: Snapshot Auto Delete is a policy-ba
Page 69 and 70: 12.3 ENSURING OPTIMAL STORAGE PERFO
Page 71 and 72: 12.6 CORRECTIVE ACTIONS FOR VMS WIT
Page 73 and 74: CREATING A PROPERLY ALIGNED VMDK FO
Page 75 and 76: It should be noted that this design
Page 77 and 78: Figure 50) Configuring a global loc
Page 79 and 80: RECOMMENDED LAYOUT OPTION 2: LOCATE
Page 81 and 82: 1 Open FilerView (http://filer/na_a
Page 83 and 84: Figure 54) Increasing the size of a
Page 85 and 86: Figure 55) Deleting a VMDK from a V
Page 87 and 88: 15 DISK-BASED SNAPSHOT BACKUPS FOR
Page 89 and 90: 16 TECHNICAL REPORT SUMMARY VMware
Page 91 and 92: lw== ESX SYSTEM SSH CONFIGURATION T
Page 93 and 94: APPENDIX C: DOCUMENT REFERENCES VMW
Page 95 and 96: MISCELLANEOUS REFERENCES Total Cost

NetApp and VMware vSphere Storage Best Practices

Create successful ePaper yourself

Delete template?

Save as template?