Cisco Cisco UCS B200 M4 Blade Server Weißbuch
© 2012 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public.
Page 73 of 95
2. To deploy Microsoft Windows 2008 failover cluster mode on Microsoft Windows 2008 R2 guest virtual machine
cluster nodes VMSQLNODE1 and VMSQLNODE2, attach four dynamic vNICs as shown in Figure 55.
a. Attach VMNIC1 with the Cisco Data Center VM-FEX port profile Managementgroup to access the
Microsoft Windows 2008 R2 guest virtual machine for operations.
Microsoft Windows 2008 R2 guest virtual machine for operations.
b. Attach VMNIC2 with the Cisco Data Center VM-FEX port profile SQLAPPDataNetwork for internal and
external clients to access the Microsoft SQL Server 2012 failover cluster server.
external clients to access the Microsoft SQL Server 2012 failover cluster server.
c. Attach VMNIC3 with the Cisco Data Center VM-FEX port profile SQLiSCSIDataNetwork to access the
iSCSI storage NetApp FAS3270HA Controller B VIF target, which hosts cluster LUNs for Microsoft SQL Server
database data files. The LUN is accessed through the Microsoft Windows 2008 guest virtual machine iSCSI
software initiator.
iSCSI storage NetApp FAS3270HA Controller B VIF target, which hosts cluster LUNs for Microsoft SQL Server
database data files. The LUN is accessed through the Microsoft Windows 2008 guest virtual machine iSCSI
software initiator.
d. Attach VMNIC4 with the Cisco Data Center VM-FEX port profile SQLiSCSILogNetwork to access the
iSCSI storage NetApp FAS3270HA Controller A VIF target, which hosts cluster LUNs for Microsoft SQL Server
database log files. It is accessed through the Microsoft Windows 2008 guest virtual machine iSCSI software
initiator.
iSCSI storage NetApp FAS3270HA Controller A VIF target, which hosts cluster LUNs for Microsoft SQL Server
database log files. It is accessed through the Microsoft Windows 2008 guest virtual machine iSCSI software
initiator.
e. Attach the Cisco UCS service profile with two Cisco UCS B230 blades (ESX Host 1 and ESX Host 2),
which have dynamic vNICs VMINC1, MNIC2, VMNIC3, and VMNIC4 to Cisco Data Center VM-FEX port
profiles with VMDirectPath enabled to provide higher performance. Enabling VMDirectPath results in better
VMware ESX utilization by reducing the number of VMware ESX host CPU cycles for handling I/O. For more
information, refer to the section
which have dynamic vNICs VMINC1, MNIC2, VMNIC3, and VMNIC4 to Cisco Data Center VM-FEX port
profiles with VMDirectPath enabled to provide higher performance. Enabling VMDirectPath results in better
VMware ESX utilization by reducing the number of VMware ESX host CPU cycles for handling I/O. For more
information, refer to the section
.
3. Perform the following steps to design the iSCSI NetApp storage target for deploying a Microsoft SQL Server
2012 failure cluster instance on Microsoft Windows 2008 R2 guest virtual machine cluster nodes
VMSQLNODE1 and VMSQLNODE2.
VMSQLNODE1 and VMSQLNODE2.
a. Microsoft Windows 2008 R2 guest virtual machine cluster nodes VMSQLNODE1 and VMSQLNODE2 use
the iSCSI software initiator configured with the VMNIC3 and VMNIC4 network interfaces to access the NetApp
cluster storage iSCSI target VIF (NetApp FAS3270HA Controller B iscsiB and NetApp FAS3270HA Controller
A iscsiA) with multipath enabled to access the Microsoft SQL Server 2012 database data and log LUNs, as
explained in the section
the iSCSI software initiator configured with the VMNIC3 and VMNIC4 network interfaces to access the NetApp
cluster storage iSCSI target VIF (NetApp FAS3270HA Controller B iscsiB and NetApp FAS3270HA Controller
A iscsiA) with multipath enabled to access the Microsoft SQL Server 2012 database data and log LUNs, as
explained in the section
b. On NetApp storage systems (NetApp FAS3270HA Controller A and B), provision cluster LUNs
MS_SQL_Cluster_LUN for storing Microsoft cluster quorum data, and MS_SQL_DB_LUN and
MS_SQL_LOG_LUN for storing shared Microsoft SQL Server 2012 failover cluster database data and log
files. These LUNs are exposed through the iSCSI network on the Microsoft Windows 2008 R2 guest virtual
machine, which is part of the Microsoft Windows server.
MS_SQL_Cluster_LUN for storing Microsoft cluster quorum data, and MS_SQL_DB_LUN and
MS_SQL_LOG_LUN for storing shared Microsoft SQL Server 2012 failover cluster database data and log
files. These LUNs are exposed through the iSCSI network on the Microsoft Windows 2008 R2 guest virtual
machine, which is part of the Microsoft Windows server.
c. Make sure that you create igroups on both NetApp storage controllers, NetApp FAS3270HA Controller A
and NetApp FAS3270HA Controller B, with both the VMSQLNODE1 and VMSQLNODE2 iSCSI initiator IQN
names and map MS_SQL_Cluster_LUN, MS_SQL_DB_LUN and MS_SQL_LOG_LUN to those IQNs as
explained in the section
and NetApp FAS3270HA Controller B, with both the VMSQLNODE1 and VMSQLNODE2 iSCSI initiator IQN
names and map MS_SQL_Cluster_LUN, MS_SQL_DB_LUN and MS_SQL_LOG_LUN to those IQNs as
explained in the section
d. On exposing NetApp storage LUNs to the Microsoft Windows 2008 R2 guest virtual machine
VMSQLNODE1 and VMSQLNODE2 cluster nodes, scan for new disks in the disk manager and format the
disk. Assign the same drive letter to both cluster nodes, as shown in Figure 56.
VMSQLNODE1 and VMSQLNODE2 cluster nodes, scan for new disks in the disk manager and format the
disk. Assign the same drive letter to both cluster nodes, as shown in Figure 56.