Cisco Solution for EMC VSPEX Microsoft Fast Track 3.0
Available Languages
Table Of Contents
About Cisco Validated Design (CVD) Program
Cisco Solution for EMC VSPEX Microsoft Fast Track 3.0
Benefits of Cisco Unified Computing System
Benefits of EMC VNXe3300 Storage Array
Benefits of Microsoft Private Cloud Fast Track Small Implementation
Active Directory Domain Services
Install the Remote Server Administration Toolkit (RSAT) on the Configuration Workstation
Cisco Unified Computing System Deployment Procedure
Initial Cisco UCS Configuration
Scripted Configuration for Fast Track
Initial EMC VNXe3300 Configuration
Cisco UCS Service Profile Creation
Configure MPIO on Windows Server 2012
Configure the iSCSI Sessions to the VNXe
Validate the Host iSCSI Configuration
Configuration of Hyper-V Failover Cluster
Create Additional Virtual Machines
Appendix A: PowerShell Scripts
Example VNXe Unisphere CLI Commands to Change the MTU size on the VNXe
Example Script to Configure Maximum Transmission Unit (MTU) Size on Windows Server 2012
Sample mtu.txt File Used for Input with the MTU Script
Example Script to Configure MPIO
Example Script to Configure iSCSI Sessions on Windows Server 2012
Example Script to Create iSCSI LUNs Using ESI PowerShell
Sample CFG_Storage.txt File Used for Input with the LUN Creation Script
Example Script to Mask iSCSI LUNs to Hosts Using ESI Powershell
Sample CFG_Access.txt File Used for Input with the LUN Masking Script
Cisco Solution for EMC VSPEX Microsoft Fast Track 3.0Microsoft Hyper-V Small ImplementationLast Updated: September 4, 2013
Building Architectures to Solve Business Problems
About the Authors
Tim Cerling, Technical Marketing Engineer, Cisco
Tim Cerling is a Technical Marketing Engineer with Cisco's Datacenter Group, focusing on delivering customer-driven solutions on Microsoft Hyper-V and System Center products. Tim has been in the IT business since 1979. He started working with Windows NT 3.5 on the DEC Alpha product line during his 19 year tenure with DEC, and he has continued working with Windows Server technologies since then with Compaq, Microsoft, and now Cisco. During his twelve years as a Windows Server specialist at Microsoft, he co-authored a book on Microsoft virtualization technologies - Mastering Microsoft Virtualization. Tim holds a BA in Computer Science from the University of Iowa.
Acknowledgments
For their support and contribution to the design, validation, and creation of this Cisco Validated Design, we would like to thank:
•
Mike Mankovsky—Cisco
•
•
About Cisco Validated Design (CVD) Program
The CVD program consists of systems and solutions designed, tested, and documented to facilitate faster, more reliable, and more predictable customer deployments. For more information visit www.cisco.com/go/designzone.
ALL DESIGNS, SPECIFICATIONS, STATEMENTS, INFORMATION, AND RECOMMENDATIONS (COLLECTIVELY, "DESIGNS") IN THIS MANUAL ARE PRESENTED "AS IS," WITH ALL FAULTS. CISCO AND ITS SUPPLIERS DISCLAIM ALL WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE. IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THE DESIGNS, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
THE DESIGNS ARE SUBJECT TO CHANGE WITHOUT NOTICE. USERS ARE SOLELY RESPONSIBLE FOR THEIR APPLICATION OF THE DESIGNS. THE DESIGNS DO NOT CONSTITUTE THE TECHNICAL OR OTHER PROFESSIONAL ADVICE OF CISCO, ITS SUPPLIERS OR PARTNERS. USERS SHOULD CONSULT THEIR OWN TECHNICAL ADVISORS BEFORE IMPLEMENTING THE DESIGNS. RESULTS MAY VARY DEPENDING ON FACTORS NOT TESTED BY CISCO.
CCDE, CCENT, Cisco Eos, Cisco Lumin, Cisco Nexus, Cisco StadiumVision, Cisco TelePresence, Cisco WebEx, the Cisco logo, DCE, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn and Cisco Store are service marks; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0809R)
© 2013 Cisco Systems, Inc. All rights reserved
Cisco Solution for EMC VSPEX Microsoft Fast Track 3.0
Executive Summary
Private cloud technologies have proven themselves in large data centers and hosting organizations. The ability to quickly deploy new virtual machines, make configuration changes to virtual machines, live migrate virtual machines to different hosts before performing maintenance on physical components, and other benefits like this have cut operational expenses.
The benefit has not been quite as easy to attain in smaller configurations. Often the installation of cloud technologies require the purchase of large management infrastructures in order to provide the benefits listed above. With the advent of the improved built-in management capabilities of Windows Server 2012, the improved Hyper-V that comes with it, and the Cisco UCS PowerTool PowerShell module, it is now possible to bring some of the benefits of cloud technologies to small and medium businesses or remote offices of larger businesses.
This guide will provide the steps necessary to configure a Microsoft Fast Track Small Implementation cloud built on EMC VSPEX, which is built on Cisco Unified Computing System and EMC VNXe technologies.
Benefits of Cisco Unified Computing System
Cisco Unified Computing System is the first converged data center platform that combines industry-standard, x86-architecture servers with networking and storage access into a single converged system. The system is entirely programmable using unified, model-based management to simplify and speed deployment of enterprise-class applications and services running in bare-metal, virtualized, and cloud computing environments.
The system's x86-architecture rack-mount and blade servers are powered by Intel Xeon processors. These industry-standard servers deliver world-record performance to power mission-critical workloads. Cisco servers, combined with a simplified, converged architecture, drive better IT productivity and superior price/performance for lower total cost of ownership (TCO). Building on Cisco's strength in enterprise networking, Cisco Unified Computing System is integrated with a standards-based, high-bandwidth, low-latency, virtualization-aware unified fabric. The system is wired when to support the desired bandwidth and carries all Internet protocol, storage, inter-process communication, and virtual machine traffic with security isolation, visibility, and control equivalent to physical networks. The system meets the bandwidth demands of today's multicore processors, eliminates costly redundancy, and increases workload agility, reliability, and performance.
Cisco Unified Computing System is designed from the ground up to be programmable and self-integrating. A server's entire hardware stack, ranging from server firmware and settings to network profiles, is configured through model-based management. With Cisco virtual interface cards, even the number and type of I/O interfaces is programmed dynamically, making every server ready to power any workload at any time. With model-based management, administrators manipulate a model of a desired system configuration, associate a model's service profile with hardware resources, and the system configures itself to match the model. This automation speeds provisioning and workload migration with accurate and rapid scalability. The result is increased IT staff productivity, improved compliance, and reduced risk of failures due to inconsistent configurations.
The power of this programmability is demonstrated in how quickly this configuration can be deployed. Cisco UCS PowerTool is used to configure the converged fabric and define the required pools, templates, and profiles needed to implement a small business or branch implementation of Hyper-V. After editing a text file to define customer specific values, a PowerShell script is run. This takes a few minutes instead of a couple hours working in front of a GUI. It ensures consistency in deployment, while at the same time not requiring a high level of expertise in UCS in order to deploy the solution.
Cisco Fabric Extender technology reduces the number of system components to purchase, configure, manage, and maintain by condensing three network layers into one. It eliminates both blade server and hypervisor-based switches by connecting fabric interconnect ports directly to individual blade servers and virtual machines. Virtual networks are now managed exactly as physical networks are, but with massive scalability. This represents a radical simplification over traditional systems, reducing capital and operating costs while increasing business agility, simplifying and speeding deployment, and improving performance.
Cisco Unified Computing System helps organizations go beyond efficiency: it helps them become more effective through technologies that breed simplicity rather than complexity. The result is flexible, agile, high-performance, self-integrating information technology, reduced staff costs with increased uptime through automation, and more rapid return on investment.
Benefits of EMC VNXe3300 Storage Array
The EMC VNXe series redefines networked storage for the small business to small enterprise user, delivering an unequaled combination of features, simplicity, and efficiency. These unified storage systems provide true storage consolidation capability with seamless management and a unique application driven approach that eliminates the boundaries between applications and their storage. VNXe systems are uniquely capable of delivering unified IP storage for NAS and iSCSI while simplifying operations and reducing management overhead. While for the Fast Track configuration only iSCSI is defined, the system can be extended to include CIFS and NFS to enable NAS environments.
The VNXe3300 is equipped with two controllers for performance, scalability, and redundancy. The high-availability design, including mirrored cache and dual active controllers, is architected to eliminate single points-of-failure. If an outage occurs, data in the VNXe write cache is safely stored in Flash memory, eliminating time-limited battery backup and external power supplies.
The VNXe hardware platforms take advantage of the latest processor technology from Intel, and include features that help meet future needs for growth and change. This includes Flex I/O expansion which provides the capability of adding 1 Gb/s or 10 Gb/s ports to extend connectivity and performance. Also the latest 6 Gb/s serial-attached SCSI (SAS) drives and enclosures are used to enable enterprise performance and end-to-end data integrity features. The VNXe systems also support Flash drives for performance-intensive applications.
The system can grow from as small as 6 drives to as large as 150 to allow for extreme flexibility in growth and performance for changing environments. The drives presented to the system are organized into pools for simple capacity management and ease of expansion. Advanced storage efficiency can be achieved through the use of the VNXe's thin provisioning capability, which enables on-demand allocation of storage. In NAS environments file-level deduplication and compression can be used to reduce physical capacity needs by 50 percent or more.
VNXe systems were designed with a management philosophy in mind: keep it simple. It's storage from the application's point of view with one clear way to handle any task. From initial installation to creating storage for virtual servers, the bottom line is the VNXe management interfaces, including Unisphere, will help to save steps and time. Provisioning storage for 500 mailboxes or 100 GB of virtual server storage can be done in less than 10 minutes. Application-driven provisioning and management enables you to easily consolidate your storage.
Benefits of Microsoft Private Cloud Fast Track Small Implementation
Microsoft Fast Track private cloud solutions, built on Microsoft Windows Server and System Center, dramatically change the way that enterprise customers produce and consume IT services by creating a layer of abstraction over pooled IT resources. But small and medium businesses might not need all the features provided by a full System Center implementation. Enter the Fast Track Small Implementation, a design specifically for small/medium businesses and branch locations of larger businesses.
The Microsoft Hyper-V Cloud Fast Track Program provides a reference architecture for building private clouds on each organization's unique terms. Each fast-track solution helps organizations implement private clouds with increased ease and confidence. Among the benefits of the Microsoft Hyper-V Cloud Fast Track Program are faster deployment, reduced risk, and a lower cost of ownership.
Faster deployment:
•
•
•
•
•
Reduced risk:
•
•
•
Lower cost of ownership:
•
•
•
Audience
This document describes the architecture and deployment procedures of an infrastructure comprised of Cisco, EMC, and Microsoft virtualization. The intended audience of this document includes, but is not limited to, sales engineers, field consultants, professional services, IT managers, partner engineering, and customers who want to deploy the VSPEX architecture.
Architecture
There are two reference architectures for the Fast Track Small Implementation. The first is based on a Cluster-in-a-Box design which utilizes low-cost storage options connected to clustered RAID controllers. The second architecture is built on a storage solution that off-loads storage processing to a SAN. The Cisco/EMC solution is based on the clustered SAN design.
The Clustered SAN design pattern uses the highly available Windows Server 2012 Hyper-V clustered architecture with traditional SAN storage. The Clustered SAN design pattern enables the storage network and network paths to be combined over a single medium, which requires fewer infrastructures by offering a converged network design. The design pattern employs an Ethernet infrastructure that serves as the transport for the management and failover networks, and provides logical separation between these networks.
This topology utilizes a traditional SAN based solution with 2 to 4 server nodes connected and clustered. The virtual machines all run within the Hyper-V cluster and utilize the networking infrastructure; whether using converged or non-converged design as mentioned previously. The requirement of Microsoft's Fast Track architecture maps on top of the VSPEX program of validated configurations of the Cisco UCS Server and EMC VNX storage.
The Cisco/EMC solution uses local on motherboard LAN connections for management of the hosts. All other networking is handled through a converged fabric which configures the redundant connections into multiple, individual LANs for use by the different functions, for example, Live Migration and iSCSI.
Figure 1 Cisco Unified Computing System and EMC Reference Design Pattern
Bill of Materials
This solution is designed to scale from a small configuration of two Cisco UCS C220 M3 servers to a maximum of four servers. The associated VNXe330 Storage Array can also scale from the 22 disks shown in the below table, up to 150 disks, depending on storage requirements.
Cisco Bill of Materials
Table 1lists the bill of materials for Cisco.
Table 1 Cisco Bill of Material
EMC Bill of Materials
Table 2 lists the bill of materials for EMC.
Table 2 EMC Bill of Materials
Configuration Guidelines
This document provides details for configuring a fully redundant, highly-available configuration. Therefore, references are made as to which component is being configured with each step, whether A or B. For example, Fabric Interconnect A and Fabric Interconnect B are used to identify the two Cisco UCS 6248UP Fabric Interconnect switches. Service Process A and Service Processor B (or SP-A and SP-b) are used to identify the two service processors in the EMC VNXe3300 Storage Array. o indicate that the reader should include information pertinent to their environment in a given step, <italicized text> appears as part of the command structure.
This document is intended to allow the reader to fully configure the customer environment. In order to expedite the configuration of the UCS environment, PowerShell command scripts are included in Appendix A. The Create-UcsHyperVFastTrack.ps1 script contains generic values for variables at the beginning of the script. Values for these variables will have to be tailored for the customer environment. The following table can be used to record the appropriate values for the customer installation. Note that many of these values may be used as is, but optionally can be altered.
Table 3 Customer Worksheet for Create-UcsHyperVFastTrack.ps1
A second sample PowerShell script, Create-UcsHyperVIscsi.ps1, creates the service profiles necessary to enable the servers to boot from iSCSI. This script uses the following variables. Again, the customer will have to change values to reflect their environment.
Table 4 Customer Worksheet for Create-UcsHyperVIscsi.ps1
Active Directory Domain Services
Active Directory Domain Services (AD DS) is a required foundational component that is provided as a component of Windows Server 2012. Previous versions are not directly supported for all workflow provisioning and de-provisioning automation. It is assumed that AD DS deployments exist at the customer site and deployment of these services is not in scope for the typical deployment.
•
•
•
The Cisco/EMC solution is designed to integrate with an existing AD DS infrastructure. If this is for a new installation that does not have an AD infrastructure, virtual machines can be built as virtual machines on the cluster hosts. If using a 2008 or earlier AD DS infrastructure, the virtual machines running AD DS should not be configured as highly available virtual machines.
Configure the Workstation
It is recommended to have a Windows 8 or Windows Server 2012 workstation configured with certain pre-requisite software and joined to the same domain as the Hyper-V servers will be joined. Using a properly configured workstation makes the job of installing the solution easier. Here is the recommendation for software to be installed on the workstation.
•
•
–
•
•
•
–
–
You will also need to have copies of the Windows Server 2012 installation media and the Cisco drivers 2.0(4a) for the P81E (www.cisco.com/cisco/software/type.html?mdfid=283862063&flowid=25886). Store these in a directory on your configuration workstation.
Install the Remote Server Administration Toolkit (RSAT) on the Configuration Workstation
There are several PowerShell scripts contained in Appendix A of this document. These are sample scripts. They have been tested, but they are not warranted against errors. They are provided as is, and no support is assumed. But they assist greatly in getting the Hyper-V implementation configured properly and quickly. Some of the scripts will require editing to reflect customer-specific configurations. It is best to create a file share on the configuration workstation and place all the PowerShell scripts on that file share. Most of the scripts will run from the configuration workstation, but there may be some that have to be run locally on the server being configured. Having them available on a file share makes it easier to access them.
For each of the PowerShell scripts contained in Appendix A, do the following:
1.
2.
3.
4.
Deployment
This document details the necessary steps to deploy base infrastructure components as well as provisioning Microsoft Hyper-V as the foundation for virtualized workloads. At the end of these deployment stops, you will be prepared to provision applications on top of a Microsoft Hyper-V virtualized infrastructure. The outlined procedure includes:
•
•
•
•
•
The VSPEX solution provides for a flexible implementation. This guide will provision a basic configuration. Specific customer installations may vary slightly. For example, this guide will show how to configure a two-node Microsoft Server 2012 Hyper-V Failover Cluster. Adding a third and fourth node is just a matter of adding the name of the third and fourth nodes into the cluster configuration wizard or PowerShell commands. Although a specific customer implementation may deviate from the information that follows, the best practices, features, and configurations listed in this section should still be used as a reference for building a customized Cisco UCS with EMC VNXe3300 Microsoft Private Cloud Fast Track Small Implementation.
Cabling Information
The following information is provided as a reference for cabling the physical equipment in a Cisco/EMC VSPEX environment. The tables include both local and remote device and port locations in order to simplify cabling requirements. The PowerShell command file in Appendix A is written to conform to this cabling information. Changes made to the customer cabling need to be reflected in the command file by editing the associated variables.
Table 5 Cisco UCS C220 M3 Server 1 Cabling Information
Table 6 Cisco UCS C220 M3 Server 2 Cabling Information
Table 7 Cisco UCS 2232PP Fabric Extender A Cabling Information
Table 8 Cisco UCS 2232PP Fabric Extender B Cabling Information
Table 9 Cisco UCS 6248UP Fabric Interconnect A Cabling Information
Table 10 Cisco UCS 6248UP Fabric Interconnect B Cabling Information
Table 11 EMC VNXe3300 Service Processor A Cabling Information
•
•
•
•
•
•
•
•
•
•
•
•
Table 12 EMC VNXe3300 Service Processor B Cabling Information
•
•
•
•
•
•
•
•
•
•
•
•
Cisco Unified Computing System Deployment Procedure
Initial Cisco UCS Configuration
The following section provides a detailed procedure for configuring the Cisco Unified Computing System. These steps should be followed precisely because a failure to do so could result in an improper configuration.
Cisco UCS 6248 A
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
Cisco UCS 6248 B
1.
2.
3.
4.
5.
6.
7.
Log into Cisco UCS Manager
These steps provide details for logging into the Cisco UCS environment.
1.
2.
3.
4.
Scripted Configuration for Fast Track
Appendix A contains a PowerShell script that can be run to configure the Microsoft Private Cloud Fast Track Small Implementation environment. It contains default values that should be edited to reflect what has been captured in the customer worksheet shown in Table 3. Only the variables at the beginning of the script should be edited. This script makes extensive use of Cisco UCS PowerTool.
Note
1.
2.
3.
4.
5.
6.
Initial EMC VNXe3300 Configuration
Unpack, Rack, and Install
The VNXe base system included with this Fast Track solution includes one VNXe disk processor enclosure (DPE) and one disk-array enclosures (DAE). The system will also include 30 300GB 15K SAS drives.
The VNXe system package will include the 3U DPE with capacity for 15 disk drives, an adjustable rail kit, power cords, a service cable, and a front bezel with key. The 3U DAE package also has capacity for 15 disk drives, includes an adjustable rail kit, power cords, serial attached SCSI (SAS) cables, and a front bezel with key.
The VNXe System installation guide (available online at http://www.emc.com/vnxesupport) provides detailed information on how to rack, cable, and power-up the VNXe system. At a high level, the process includes the following:
•
•
•
•
•
Connect to the VNXe
Option 1 - Automatic IP Address Assignment for the VNXe Management Port
If you are running the VNXe on a dynamic network that includes DHCP servers, DNS servers, and Dynamic DNS services, the management IP address can be assigned automatically. By default, the VNXe system management port is configured to use DHCP for IP assignment and will accept an IP address broadcast by a network DHCP server.
Perform the following steps to automatically assign an IP address to your VNXe system management port:
After you power up the VNXe system check the status of the SP fault/status LEDs. If the SP fault/status LEDs are solid blue, a management IP address has been assigned. If the fault/status LEDs are blue and flash amber every three seconds, no management IP address has been assigned. If the SP Fault/Status LEDs are blue and flashing, check the connectivity between the system, the DNS server, and the DHCP server.
Open a web browser and access the VNXe management interface specifying the following as a URL in the browser's address bar serial_number.domain.
Where:
Option 2 - Manual Static IP Address Assignment for the VNXe Management Port
To manually assign a static IP address for the VNXe system management port, the VNXe Connection Utility is required. To use the VNXe connection utility to assign a network address to the VNXe system, perform the following steps:
1.
a.
b.
c.
Use the connection utility to assign a management IP address to the VNXe system. After running the utility, select one of the following options
d.
–
–
–
–
e.
–
–
–
Initial VNXe Configuration
Upon connecting to the VNXe system in the previous steps, log into Unisphere using the following credentials
•
•
The first time Unisphere is launched, the Unisphere Configuration wizard will run. The wizard provides the steps necessary to configure the following system settings:
•
•
•
•
•
Storage Pool Considerations
The VNXe 3300 supports a range of drive technologies and RAID protection schemes. For the proposed solution, Cisco and EMC have implemented a base configuration that utilizes a single drive type and RAID protection scheme. The solution implements a total of 30 300 GB 15K RPM SAS drives in a RAID 5 configuration.
In a VNXe 3300 RAID 5 is implemented in multiples of 7 (6 data + 1 parity) drive sets. For a total of 30 drives, there will be 4 X 6+1 RAID 5 sets. The remaining 2 drives are meant to be configured as Hot Spares.
When using the automatically configure pools option, the VNXe will allocate existing disks into capacity, performance and/or extreme performance pools, depending on the number and type of available disks. The rules used are the following:
•
•
•
Instead of configuring the storage pools automatically, custom storage pools can be created with the manually create a new pool option. Custom pools can be used to optimize storage for an application with specific performance, capacity or cost efficiency requirements. The pool RAID types that can be configured, dependent on drive technology, can be seen in the following table:
Table 13 Storage Pool Options
It is recommended to use the automatically configure pools option with the base configuration. If this is not done as a part of the initial VNXe configuration during the first time Unisphere is launched, it can be done with the following steps:
iSCSI Server Configuration
The iSCSI Storage Server is the portal through which storage will be accessed by the hosts within the Fast Track configuration. The goal of the proposed iSCSI server configuration is to provide redundancy, multi-pathing and balanced access across all 10 GE connections and both storage processors. Each 10 GE I/O module will have 2 ports, referred to as eth10 and eth11. Considering there is an I/O module for each service processor, both SPA and SPB will have eth10 and eth11 connections.
iSCSI servers will run on either SPA or SPB. This means storage assigned to a given iSCSI server will only be available to one SP at a given time. To utilize both SPA and SPB concurrently, two iSCSI servers will be created.
With respect to iSCSI server high availability, the eth10 and eth11 connections are paired across the service processors. If an iSCSI server running with an IP address dedicated to eth10 on SP A needs to move to SP B, for maintenance as an example, the IP address will move to the corresponding eth10 port on SPB. Therefore subnet connectivity will need to be the same for the associated eth10 and eth11 connections across the service processors. The following figure shows a logical example of the connections.
Figure 2 Logical Network Connections
The iSCSI server configuration will also have redundant connectivity while running against its respective service processor. This means both Eth10 and Eth11 will be assigned an IP addresses for each iSCSI server. This allows each iSCSI server to have both redundant ports and redundant fabric connections when running on either SPA or SPB. The following table provides an example.
Table 14 Sample IP Configuration
In summary, the key considerations for configuring iSCSI connectivity and the iSCSI storage servers are the following:
•
•
•
To configure iSCSI Storage Servers, do the following:
The Cisco networking environment will have a Maximum Transmission Unit (MTU) size of 9000 for the iSCSI connections to the VNXe. An example script to change the MTU through the VNXe Unisphere CLI is in the appendix. In order to match the configured MTU size through Unisphere, do the following steps:
Note
Licensing
Obtaining a license file as well as uploading and installing the file can be accomplished from within Unisphere: under Settings > More configuration... > Manage Licenses.
Update the VNXe Operating Environment
Depending on availability, please ensure the VNXe Operating Environment is updated to the MR4 release, which is not available as of the writing of this document. If this release is not available, please update the VNXe software as instructed below.
For Windows Server 2012 support with Windows Failover Clustering, the VNXe operating environment must be at MR3 SP1.1 - 2.3.1.20356 and include hotfix 2.3.1.20364.1.2.001.192. More information regarding the required hotfix can be found in knowledge base article emc306921.
VNXe software can be updated from within Unisphere at Settings > More configuration... > Update Software.
First ensure MR3 SP1.1 at a minimum is installed. Then install the aforementioned hotfix.
After the hotfix is installed, file parameters need to be updated on the service processor. Please see emc289415 for details.
Create Host Configurations
In order to present storage from the VNXe to the servers in the Fast Track environment, a host configuration profile must be created on the VNXe. The host profile will define the iSCSI Qualified Name (IQN) used by each server. It will also define the one-way Challenge-Handshake Authentication Protocol (CHAP) secret for the IQN(s) associated with the Host. Follow the next steps to configure the host:
Provisioning Storage
Potentially repetitive tasks, like provisioning storage, can be accomplished through Unisphere or can be scripted. EMC offers PowerShell cmdlets through a free product called EMC Storage Integrator (ESI). The appendix provides an example script on how to use ESI version 2.1 to provision storage. More information on ESI can be found on support.emc.com by searching for "ESI". The following table provides an example on how to use Unisphere to provision storage:
Cisco UCS Service Profile Creation
The Create-UcsHyperVIscsi.ps1 script in Appendix A is used to create service profiles based on the values entered in tables 3 and 4.
This script file is designed to be run from the configuration workstation or server.
•
•
•
•
Server Configuration
Installation of Windows Server 2012 Datacenter Edition
The instruction for install Windows Server 2012 Datacenter Edition presented here make the assumption that this is an installation from the Microsoft installation DVD. If the customer already has an automated deployment process in place, such as Windows Deployment Server, follow the customer installation procedure.
You will install Windows Server 2012 Datacenter Edition to the Cisco UCS C220 M3 servers by working through the UCSM KVM.
Local Configuration Tasks
When the computer has the operating system installed, there are some tasks that are performed to ensure the ability for the hosts to be remotely managed for the rest of these instructions. In an existing customer environment, the customer may handle some of these tasks through Active Directory group policy objects. Setting up these tasks to be handled by group policies is beyond the scope of this document, so they should be reviewed with the customer.
Remote Management
The server needs to be configured to ensure its ability to be remotely managed. This requires setting some specific firewall rules, so the setting of these rules should be agreed to by the customer's security department.
•
•
•
•
•
Assigning Storage To Hosts
If the storage device was created but not assigned to any hosts, access can be specified at a later time through the storage device details area of Unisphere. Additionally, the appendix provides an example script, using ESI, for how to assign storage to a host. The following table provides an example on how to use Unisphere to assign storage.
Modify Windows Server 2012 iSCSI registry parameters
The registry settings in the following table should be modified on each server running iSCSI to the VNXe. The settings apply for both the native Windows Server 2012 MPIO DSM and PowerPath unless otherwise noted.
1.
2.
3.
4.
a.
b.
Table 15 Registry Setting Values
Prepare Disks for Clustering
Earlier iSCSI LUNs were created and zoning/masking performed to present multiple LUNs to the servers for use by the cluster. It is a good practice to ensure each server that is going to participate in the cluster is able to properly access and mount the presented LUNs. Also, Microsoft Failover Cluster Services expects the LUNs to be formatted as NTFS volumes. These steps ensure the disks are ready for use by the cluster and that each node has access to them.
All the following steps should be performed only from the first server that will be a cluster node. These steps prepare the disks for clustering.
On subsequence servers, simply follow the steps to bring the disks online and then take them offline. This ensures that disks are accessible from each node in the cluster. If you run into an error bring the disks online and offline, you will most likely need to troubleshoot your iSCSI configuration for that particular server.
Initial Network Configuration
What is seen in the following sample screen shots may vary significantly from the actual customer environment. This is due to the fact that there are many variables in the potential customer network, and all variations are not covered in these samples. These samples assume that there is no DHCP server (which would make this a little easier, but is beyond the scope of this document). By assuming there is no DHCP server, all NICs will initially be configured with 169.254/16 APIPA addresses. These steps will assign fixed IP addresses to all the NICs.
The first that is necessary is to find the NIC through which host management is performed. This is not the out-of-band NIC used by UCSM, but the NIC dedicated to host management.
Join Computer to Domain
Final Network Configuration
The configuration workstation contains a PowerShell script file that eases the process of renaming the NICs from the generic names assigned during the installation to names that match the Service Profile used on each server. It contains default values for accessing the UCS Manager. These variables will need to be edited to reflect the customer's configuration.
This script file is designed to be run from a domain-joined workstation or server.
1.
2.
3.
4.
When the NIC teams have been renamed, you can configure static IP addresses for the NICs. Set-UcsHyperVIps.ps1 contains a PowerShell script file that will assign a fixed IP address to four NICs. The addresses assigned are in the format 192.168.<vlan>.<hostnum>, where <vlan> is the VLAN tag for the associated network, and <hostnum> is a value fixed across all IP addresses. It keeps things simpler if you assign the same value to <hostnum> as you used for the Mgmt NIC. The script also sets the NICs to not automatically register themselves in DNS.
This script file is designed to be run from a domain-joined workstation or server.
1.
2.
3.
4.
Role and Feature Installation
The Add-UcsHyperVFeatures.ps1 PowerShell script will add the Hyper-V role and the Failover Cluster and MPIO features. MPIO is required to create dual paths to the iSCSI LUNs. Adding the Hyper-V role requires that the server be rebooted. This is handled automatically by the script.
This script can be run from the configuration workstation.
1.
2.
It will take a couple minutes for the features to be added. After the Hyper-V Server has rebooted, the virtual switches need to be created for use by the VMs.
1.
2.
Configure MPIO on Windows Server 2012
MPIO can be configured from either the MPIO GUI after the feature is enabled, or from powershell. To configure the required settings from the MPIO GUI perform the following steps
1.
2.
3.
4.
5.
6.
7.
8.
Note
9.
Alternatively the following PowerShell commands can be used to configure MPIO.
Note
10.
11.
Configure the iSCSI Sessions to the VNXe
The following steps will show how to configure the iSCSI connections to the VNXe through the iSCSI Initiator Properties GUI. The appendix also includes a PowerShell script that can be used to accomplish the same task.
Validate the Host iSCSI Configuration
Configuration of Hyper-V Failover Cluster
At this time you should have configured the physical Cisco UCS C-220 Rack-Mount servers to be ready to create a cluster. Preparation steps on each server included:
•
•
•
•
•
•
•
•
Log on to the configuration workstation with an account that has privileges to create Computer Name Objects in the Active Directory. Definitely the domain administrator account will have these privileges.
Note
Set Cluster Network Purposes
The cluster automatically attempts to determine which network is to be used for which purpose. Though it does a good job most of the time, it is better to ensure that the networks are performing the functions you want them to. Microsoft Failover Clustering assigns a metric value to each network, and that metric value is used to determine each network's use. The network with the lowest metric value is always used for Cluster Shared Volumes. The next lowest metric is always used for the primary Live Migration network.
This script can be run from the configuration workstation. This script assumes that the CSV network is named "CSV" and the live migration network is named "LiveMigration". If your networks have different names, you will need to modify the script to reflect your names.
1.
2.
Create First Virtual Machine
This section describes how to create the first virtual machine. This first virtual machine will be turned into a template that can be used to quickly create additional virtual machines. The steps to build the template are as follows:
1.
2.
3.
4.
5.
The following steps MUST be performed from one of the nodes of the cluster.
Create Additional Virtual Machines
After the template has been made, a PowerShell script can be used to create as many virtual machines as possible. The Create-UcsHyperVSingleVM.ps1 PowerShell script contains the commands necessary to create new VMs. This is a sample script and it may need to be edited to reflect the customer environment.
By default this script copies the VHDX file of a virtual machine that has had sysprep run against it. It copies from CSV volume 1 to CSV volume 2. If these are not the desired locations, the script will need to be edited. It is best to run this script from the cluster that owns CSV volume 2, or other selected destination CSV, due to the way CSV works. It is not a strict requirement to run it from the owning node, but it is more efficient.
This script must be run from a cluster node.
1.
2.
3.
4.
5.
Appendix A: PowerShell Scripts
The following PowerShell scripts are provided as is and are not warranted to work in all situations. They are provided as samples that will have to be modified to reflect each installation. They have been tested and are known to work, but they do not include error checking. Incorrect changes to any one of the files can render the script inoperable, so some experience with PowerShell is recommended on the part of the person making the modifications.
Create-UcsHyperVFastTrack.ps1
# Global Variables - These need to be tailored to the customer environment$ucs = "192.168.171.129"$ucsuser = "Admin"$ucspass = "admin"$mgtippoolblockfrom = "10.29.130.5"$mgtippoolblockto = "10.29.130.12"$mgtippoolgw = "10.29.130.1"$maintpolicy = "immediate" # Possible values "immediate", "timer-automatic", "user-ack"$WarningPreference = "SilentlyContinue"# vNIC information - build an array of values for working with vNICs, vNIC templates, VLANs# Values are: Name, MTU size, SwitchID, VLAN tag, order, QoS Policy$vnicarray = @()$vnicarray +=, ( "CSV" , "9000" , "A-B" , "12" , "5" , "")$vnicarray +=, ( "ClusComm" , "9000" , "A-B" , "16" , "3" , "")$vnicarray +=, ( "LiveMigration" , "9000" , "B-A" , "11" , "4" , "LiveMigration")$vnicarray +=, ( "Mgmt" , "1500" , "A-B" , "1" , "1" , "")$vnicarray +=, ( "VMaccess" , "1500" , "A-B" , "1" , "2" , "")# VLAN information for Appliance ports$iScsiVlanA = "iSCSI-A"$iSCSIVlanAID = 18$iScsiVlanB = "iSCSI-B"$iScsiVlanBID = 19$serverports = 3 , 4 , 5 , 6$applianceport1 = 29$applianceport2 = 30$qoslivemigration = "platinum"$qosiscsi = "gold"############# The following variables are used for Tenant definitions#$tenantname = "FastTrack3" # Used to create sub-organization and resource names$tenantnum = "F3" # Two hex characters to distinguish pool values$macpoolblockfrom = "00:25:B5:" + $tenantnum + ":01:01"$macpoolblockto = "00:25:B5:" + $tenantnum + ":01:FF"$wwpnpoolblockfrom = "20:00:00:25:B5:" + $tenantnum + ":02:01"$wwpnpoolblockto = "20:00:00:25:B5:" + $tenantnum + ":02:10"$wwnnpoolblockfrom = "20:00:00:25:B5:" + $tenantnum + ":03:01"$wwnnpoolblockto = "20:00:00:25:B5:" + $tenantnum + ":03:10"$uuidpoolblockfrom = "00" + $tenantnum + "-000000000001"$uuidpoolblockto = "00" + $tenantnum + "-00000000002F"##### ------------------------------------------------- ####### Start of code# Import Modulesif (( Get-Module | where { $_ .Name -ilike "CiscoUcsPS"}) .Name -ine "CiscoUcsPS"){Write-Host "Loading Module: Cisco UCS PowerTool Module"Import-Module CiscoUcsPs}Set-UcsPowerToolConfiguration -SupportMultipleDefaultUcs $false | Out-NullTry {# Login to UCSWrite-Host "UCS: Logging into UCS Domain: $ucs "$ucspasswd = ConvertTo-SecureString $ucspass -AsPlainText -Force$ucscreds = New-Object System.Management.Automation.PSCredential ( $ucsuser , $ucspasswd)$ucslogin = Connect-Ucs -Credential $ucscreds $ucs$rootorg = Get-UcsManagedObject -Dn "org-root"# Create Server PortsWrite-Host "UCS: Creating Server Ports"$mo = Get-UcsFabricServerCloudForEach ( $srvrprt in $serverports){$mo | Add-UcsServerPort -PortId $srvrprt -SlotId 1 | Out-Null}# Create Management IP PoolWrite-Host "UCS: Creating Management IP Pool"Get-UcsOrg -Level root | Get-UcsIpPool -Name "ext-mgmt" -LimitScope | Add-UcsIpPoolBlock -DefGw $mgtippoolgw -From $mgtippoolblockfrom -To $mgtippoolblockto | Out-Null# Create QoS for Live Migration, iSCSI, and Best EffortWrite-Host "UCS: Creating QoS for Live Migration, iSCSI, and Best Effort"Start-UcsTransaction$mo = Get-UcsQosClass -Priority $qosiscsi | Set-UcsQosClass -AdminState enabled -Mtu 9000 -Force | Out-Null$mo = Get-UcsQosClass -Priority $qoslivemigration | Set-UcsQosClass -AdminState enabled -Mtu 9000 -Force | Out-Null$mo = Get-UcsBestEffortQosClass | Set-UcsBestEffortQosClass -Mtu 9000 -Force | Out-Null$mo = $rootorg | Add-UcsQosPolicy -Name LiveMigration$mo | Set-UcsVnicEgressPolicy -Prio $qoslivemigration -Force | Out-Null$mo = $rootorg | Add-UcsQosPolicy -Name iSCSI$mo | Set-UcsVnicEgressPolicy -Prio $qosiscsi -Force | Out-NullComplete-UcsTransaction | Out-Null# Create any needed VLANsWrite-Host "UCS: Creating VLANs"Start-UcsTransaction$i = 0while ( $i -lt $vnicarray .length){$entry = $vnicarray [ $i ]Get-UcsLanCloud | Add-UcsVlan -Name $entry [ 0 ] -Id $entry [ 3 ] | Out-Null$i ++}Complete-UcsTransaction | Out-Null# Create VLANs for Appliance PortsWrite-Host "UCS: Creating VLANs for Appliance Ports"Start-UcsTransactionGet-UcsFiLanCloud -Id "A" | Add-UcsVlan $iScsiVlanA -Id $iScsiVlanAID -DefaultNet "no" -Sharing "none" | Out-NullGet-UcsFiLanCloud -Id "B" | Add-UcsVlan $iScsiVlanB -Id $iScsiVlanBID -DefaultNet "no" -Sharing "none" | Out-NullGet-UcsFabricApplianceCloud -Id "A" | Add-UcsVlan -Id $iScsiVlanAID -Name $iScsiVlanA | Out-NullGet-UcsFabricApplianceCloud -Id "B" | Add-UcsVlan -Id $iScsiVlanBID -Name $iScsiVlanB | Out-NullComplete-UcsTransaction | Out-Null####### Create Tenant sub-organization, templates, pools, and policies## Create Tenant sub-organizationWrite-Host "UCS: $tenantname - Creating sub-organization"$tenantorg = Add-UcsOrg -Org root -Name $tenantname# Create Local Disk Configuration PolicyWrite-Host "UCS: Creating Local Disk Configuration Policy"$tenantorg | Add-UcsLocalDiskConfigPolicy -Mode "any-configuration" -Name $tenantname -ProtectConfig "yes" | Out-Null# Create Mac PoolWrite-Host "UCS: $tenantname - Creating MAC Pool"Start-UcsTransaction$mo = $tenantorg | Add-UcsMacPool -Name $tenantname$mo | Add-UcsMacMemberBlock -From $macpoolblockfrom -To $macpoolblockto | Out-NullComplete-UcsTransaction | Out-Null# Create WWPN PoolWrite-Host "UCS: $tenantname - Creating WWPN Pool"Start-UcsTransaction$mo = $tenantorg | Add-UcsWwnPool -Name wwpn $tenantname -Purpose "port-wwn-assignment"$mo | Add-UcsWwnMemberBlock -From $wwpnpoolblockfrom -To $wwpnpoolblockto | Out-NullComplete-UcsTransaction | Out-Null# Create WWNN PoolWrite-Host "UCS: $tenantname - Creating WWNN Pool"Start-UcsTransaction$mo = $tenantorg | Add-UcsWwnPool -Name wwnn $tenantname -Purpose "node-wwn-assignment"$mo | Add-UcsWwnMemberBlock -From $wwnnpoolblockfrom -To $wwnnpoolblockto | Out-NullComplete-UcsTransaction | Out-Null# Create UUID Suffix PoolWrite-Host "UCS: $tenantname - Creating UUID Suffix Pool"Start-UcsTransaction$mo = $tenantorg | Add-UcsUuidSuffixPool -Name $tenantname$mo | Add-UcsUuidSuffixBlock -From $uuidpoolblockfrom -To $uuidpoolblockto | Out-NullComplete-UcsTransaction | Out-Null# Create BIOS, Power, and Scrub PoliciesWrite-Host "UCS: $tenantname - Creating BIOS and Scrub Policies"Add-UcsBiosPolicy -Name $tenantname | Set-UcsBiosVfQuietBoot -VpQuietBoot disabled -Force | Out-NullAdd-UcsPowerPolicy -Name $tenantname -Prio "no-cap" | Out-NullAdd-UcsScrubPolicy -org $rootorg -Name $tenantname -BiosSettingsScrub "no" -DiskScrub "no" | Out-NullAdd-UcsMaintenancePolicy -org $rootorg -Name $tenantname -UptimeDisr $maintpolicy | Out-Null# Create Server PoolWrite-Host "UCS: $tenantname - Creating Server Pool"$serverpool = $tenantorg | Add-UcsServerPool -Name $tenantname#???** # Create Server Qualification PolicyWrite-Host "UCS: $tenantname - Creating Server Qualification Policy"Start-UcsTransaction$serverqualpol = $tenantorg | Add-UcsServerPoolQualification -Name $tenantname$serveradaptorqual = $serverqualpol | Add-UcsAdaptorQualification$serveradaptorcapqual = $serveradaptorqual | Add-UcsAdaptorCapQualification -Maximum "unspecified" -Model "N2XX-ACPCI01" -Type "virtualized-eth-if"$serverrackqual = $serverqualpol | Add-UcsRackQualification -MinId 1 -MaxId 8Complete-UcsTransaction | Out-Null# Create Server Pool Policy (for dynamic server pools based on qualification policy)Write-Host "UCS: $tenantname - Creating Server Pool Policy"$serverpoolpol = $tenantorg | Add-UcsServerPoolPolicy -Name $tenantname -PoolDn $serverpool .dn -Qualifier $serverqualpol .Name#Create VNIC templatesWrite-Host "UCS: $tenantname - Creating VNIC templates"Start-UcsTransaction$i = 0while ( $i -lt $vnicarray .length){$entry = $vnicarray [ $i ]$vnictemplate = $tenantorg | Add-UcsVnicTemplate -IdentPoolName $tenantname -Name $entry [ 0 ] -Mtu $entry [ 1 ] -SwitchId $entry [ 2 ] -Target "adaptor" -TemplType "updating-template" -QosPolicyName $entry [ 5 ]Add-UcsVnicInterface -VnicTemplate $vnictemplate -DefaultNet "yes" -Name $entry [ 0 ] | Out-Null$i ++}$mo = $tenantorg | Add-UcsVnicTemplate -IdentPoolName $tenantname -Mtu 9000 -Name $iSCSIVlanA -QosPolicyName "iSCSI" -SwitchId "A" -TemplType "updating-template"$mo | Add-UcsVnicInterface -DefaultNet "yes" -Name $iSCSIVlanA | Out-Null$mo = $tenantorg | Add-UcsVnicTemplate -IdentPoolName $tenantname -Mtu 9000 -Name $iSCSIVlanB -QosPolicyName "iSCSI" -SwitchId "B" -Target "adaptor" -TemplType "updating-template"$mo | Add-UcsVnicInterface -DefaultNet "yes" -Name $iSCSIVlanB | Out-NullComplete-UcsTransaction | Out-Null# Create Appliance Ports for iSCSI connection.Write-Host "UCS: Creating Appliance Ports for iSCSI connectivity"Start-UcsTransactionGet-UcsFabricApplianceCloud -Id "A" | Add-UcsAppliancePort -AdminSpeed "10gbps" -AdminState "enabled" -PortId $applianceport2 -PortMode "trunk" -Prio $qosiscsi -SlotId 1 | Out-NullGet-UcsFabricApplianceCloud -Id "A" | Add-UcsAppliancePort -AdminSpeed "10gbps" -AdminState "enabled" -PortId $applianceport1 -PortMode "trunk" -Prio $qosiscsi -SlotId 1 | Out-NullGet-UcsApplianceCloud | Get-UcsVlan -Name vlan $iScsiVlanA -LimitScope | Add-UcsVlanMemberPort -AdminState "enabled" -PortId $applianceport1 -SlotId 1 -SwitchId "A"Get-UcsApplianceCloud | Get-UcsVlan -Name vlan $iScsiVlanA -LimitScope | Add-UcsVlanMemberPort -AdminState "enabled" -PortId $applianceport2 -SlotId 1 -SwitchId "A"Get-UcsFabricApplianceCloud -Id "B" | Add-UcsAppliancePort -AdminSpeed "10gbps" -AdminState "enabled" -PortId $applianceport2 -PortMode "trunk" -Prio $qosiscsi -SlotId 1 | Out-NullGet-UcsFabricApplianceCloud -Id "B" | Add-UcsAppliancePort -AdminSpeed "10gbps" -AdminState "enabled" -PortId $applianceport1 -PortMode "trunk" -Prio $qosiscsi -SlotId 1 | Out-NullGet-UcsApplianceCloud | Get-UcsVlan -Name vlan $iScsiVlanB -LimitScope | Add-UcsVlanMemberPort -AdminState "enabled" -PortId $applianceport1 -SlotId 1 -SwitchId "B"Get-UcsApplianceCloud | Get-UcsVlan -Name vlan $iScsiVlanB -LimitScope | Add-UcsVlanMemberPort -AdminState "enabled" -PortId $applianceport2 -SlotId 1 -SwitchId "B"Complete-UcsTransaction | Out-Null# Create Service Profile Template (using MAC, WWPN, Server Pools, VLANs, etc. previously created steps) with desired power state to downWrite-Host "UCS: $tenantname - Creating SP Template: $tenantname in UCS org:" $tenantorg .dnStart-UcsTransaction$mo = $tenantorg | Add-UcsServiceProfile -ExtIPState "none" -IdentPoolName $tenantname -LocalDiskPolicyName $tenantname -PowerPolicyName $tenantname -ScrubPolicyName $tenantname -Name $tenantname -Type "updating-template" -Uuid "0"$mo | Add-UcsVnicDefBeh -Action "none" -Type "vhba" | Out-Null$i = 0while ( $i -lt $vnicarray .length){$entry = $vnicarray [ $i ]$mo | Add-UcsVnic -AdaptorProfileName "Windows" -Addr "derived" -AdminVcon "1" -Name $entry [ 0 ] -NwTemplName $entry [ 0 ] -order $entry [ 4 ] | Out-Null$i ++}Complete-UcsTransaction | Out-Null# Logout of UCSWrite-Host "UCS: Logging out of UCS: $ucs "Disconnect-Ucs}Catch{Write-Host "Error occurred in script:"Write-Host ${Error}exit}Create-UcsHyperVIscsi.ps1
# Global Variables - These need to be tailored to the customer environment$ucs = "192.168.171.129"$ucsuser = "Admin"$ucspass = "admin"############# The following variables are used for Tenant definitions#$tenantname = "FastTrack3" # Used to find sub-organization and resource names$tenantfirstIP = 31 # Last digits of first server's IP address. Incremented for subsequent servers.############# The following variables are used for setting up iSCSI booting#$iSCSICiscoIQNPrefix = "iqn.1992-05.com.cisco"$iSCSICiscoIQNSuffix = "be6evmhost"$iSCSICiscoIQNSuffixStartNumber = "1"$iSCSICiscoIQNSuffixCount = "30"$iSCSITargetIPControllerAPort1 = "10.10.18.1"$iSCSITargetIPControllerAPort2 = "10.10.19.1"$iSCSITargetIPControllerBPort1 = "10.10.18.2"$iSCSITargetIPControllerBPort2 = "10.10.19.2"$iSCSITargetIQNA = "iqn.1992-05.com.emc:apm001203006930000-4-vnxe"#$iSCSITargetIQNB = "iqn.1992-05.com.emc:apm001203006930000-4-vnxe"$iSCSITargetIQNB = ""$iSCSIInitiatorIP = "10.10."$iSCSIVlanAID = 18$iScsiVlanBID = 19$iSCSIInitiatorIP_iSCSI_A = $iSCSIInitiatorIP + $iSCSIVlanAId + "."$iSCSIInitiatorIP_iSCSI_B = $iSCSIInitiatorIP + $iSCSIVlanBId + "."$iSCSIIPPoolAStartingIP = "10.10.18.201"$iSCSIIPPoolAEndingIP = "10.10.18.219"$iSCSIIPPoolANetMask = "255.255.255.0"$iSCSIAdapterPolicyName = "Windows-VIC"$iScsiVlanA = "iSCSI-A"$iScsiVlanB = "iSCSI-B"$iSCSIvNICNameA = "iSCSI-A"$iSCSIvNICNameB = "iSCSI-B"$iSCSIOverlayvNicA = "iSCSI-A"$iSCSIOverlayvNicB = "iSCSI-B"$VMHostNamePrefix = "VMHost0"$VMHostCount = 4$VMHostBootLunId = 0 , 1 , 2 , 3##### ------------------------------------------------- ####### Start of code# Import Modulesif (( Get-Module | where { $_ .Name -ilike "CiscoUcsPS"}) .Name -ine "CiscoUcsPS"){Write-Host "Loading Module: Cisco UCS PowerTool Module"Import-Module CiscoUcsPs}Set-UcsPowerToolConfiguration -SupportMultipleDefaultUcs $false | Out-NullTry {# Login to UCSWrite-Host "UCS: Logging into UCS Domain: $ucs "$ucspasswd = ConvertTo-SecureString $ucspass -AsPlainText -Force$ucscreds = New-Object System.Management.Automation.PSCredential ( $ucsuser , $ucspasswd)$ucslogin = Connect-Ucs -Credential $ucscreds $ucs$rootorg = Get-UcsManagedObject -Dn "org-root"$tenantorg = $rootorg | Get-UcsOrg -Name $tenantname# Create Windows iSCSI Adapter Policy for Cisco VICWrite-Host "Creating Windows iSCSI Adapter Policy for Cisco VIC"Start-UcsTransaction$mo = $rootorg | Add-UcsIScsiAdapterPolicy -Name $iSCSIAdapterPolicyName$mo | Set-UcsIScsiAdapterPolicyProperties -BootToTarget "no" -ConnectionTimeOut 0 -DhcpTimeOut 60 -HbaMode "no" -LunBusyRetryCount 0 -TcpTimeStamp "no" -Force | Out-NullComplete-UcsTransaction | Out-Null# Create ISCSI IQN PoolWrite-Host "Creating iSCSI IQN Pool"$tenantorg | Add-UcsIqnPoolPool -Descr "" -Name $tenantname -Prefix $iSCSICiscoIQNPrefix | Out-Null# Create iSCSI IQN BlockWrite-Host "Creating iSCSI IQN Block"$tenantorg | Get-UcsIqnPoolPool -Name $tenantname -LimitScope | Add-UcsIqnPoolBlock -From $iSCSICiscoIQNSuffixStartNumber -Suffix $iSCSICiscoIQNSuffix -To $iSCSICiscoIQNSuffixCount | Out-Null# Create iSCSI Initiator IP PoolWrite-Host "Creating iSCSI Initiator Pool"$rootorg | Get-UcsIpPool -Name "iscsi-initiator-pool" -LimitScope | Add-UcsIpPoolBlock -DefGw $iSCSITargetIPControllerAPort1 -From $iSCSIIPPoolAStartingIP -To $iSCSIIPPoolAEndingIP | Out-Null# Update SP Template with iSCSI boot informationWrite-Host "Updating $tenantname Service Profile Template"Start-UcsTransaction$mo = $tenantorg | Get-UcsServiceProfile -Name $tenantname | Set-UcsServiceProfile -BootPolicyName $tenantname -Force$mo_1 = $mo | Add-UcsVnic -AdaptorProfileName "Windows" -Addr "derived" -AdminVcon "1" -Name $iSCSIVlanA -NwTemplName $iSCSIVlanA -Order "6"$mo_2 = $mo | Add-UcsVnic -AdaptorProfileName "Windows" -Addr "derived" -AdminVcon "1" -Name $iSCSIVlanB -NwTemplName $iSCSIVlanB -Order "7"$mo_3 = $mo | Add-UcsVnicFcNode -Addr "pool-derived" -IdentPoolName "node-default"$mo_4 = $mo | Add-UcsServerPoolAssignment -Name $tenantname -Qualifier $tenantname -RestrictMigration "no"$mo_5 = $mo | Set-UcsServerPower -State "admin-down" -Force$mo_6 = $mo | Add-UcsFabricVCon -Fabric "NONE" -Id "1" -Placement "physical" -Select "all" -Share "shared" -Transport "ethernet" , "fc"$mo_7 = $mo | Add-UcsFabricVCon -Fabric "NONE" -Id "2" -Placement "physical" -Select "all" -Share "shared" -Transport "ethernet" , "fc"$mo_8 = $mo | Add-UcsFabricVCon -Fabric "NONE" -Id "3" -Placement "physical" -Select "all" -Share "shared" -Transport "ethernet" , "fc"$mo_9 = $mo | Add-UcsFabricVCon -Fabric "NONE" -Id "4" -Placement "physical" -Select "all" -Share "shared" -Transport "ethernet" , "fc"Complete-UcsTransaction | Out-Null# Create Boot Policy with iSCSI BootWrite-Host "UCS: Creating Boot Policy: $tenantname "Start-UcsTransaction$mo = $tenantorg | Add-UcsBootPolicy -EnforceVnicName "yes" -Name $tenantname -RebootOnUpdate "no"$mo_1 = $mo | Add-UcsLsbootIScsi -Order "2"$mo_1_1 = $mo_1 | Add-UcsLsbootIScsiImagePath -ISCSIVnicName $iSCSIvNICNameA -Type "primary"$mo_1_2 = $mo_1 | Add-UcsLsbootIScsiImagePath -ISCSIVnicName $iSCSIvNICNameB -Type "secondary"$mo_2 = $mo | Add-UcsLsbootLan -Order "3" -Prot "pxe"$mo_2_1 = $mo_2 | Add-UcsLsbootLanImagePath -Type "primary" -VnicName "Mgmt"$mo_3 = $mo | Add-UcsLsbootVirtualMedia -Access "read-only" -Order "1"Complete-UcsTransaction | Out-Null# Create iSCSI vNIC for Fabric AWrite-Host "Creating iSCSI vNIC for Fabric A"Start-UcsTransaction$mo = Get-UcsServiceProfile -Org $tenantorg .dn -Name $tenantname | Add-UcsVnicIScsi -AdaptorProfileName $iSCSIAdapterPolicyName -Addr "derived" -AdminVcon "any" -AuthProfileName "" -ConfProfileName "" -ExtIPState "none" -IdentPoolName "" -InitiatorName "" -IqnIdentPoolName "" -Name $iSCSIvNICNameA -NwTemplName "" -Order "unspecified" -PinToGroupName "" -QosPolicyName "" -StatsPolicyName "default" -SwitchId "A" -VnicName $iSCSIvNICNameA$mo_1 = $mo | Add-UcsVnicVlan -Name "" -VlanName $iScsiVlanAComplete-UcsTransaction | Out-Null# Create iSCSI vNIC for Fabric BWrite-Host "Creating iSCSI vNIC for Fabric B"Start-UcsTransaction$mo = Get-UcsServiceProfile -Org $tenantorg .dn -Name $tenantname | Add-UcsVnicIScsi -AdaptorProfileName $iSCSIAdapterPolicyName -Addr "derived" -AdminVcon "any" -ExtIPState "none" -Name $iSCSIvNICNameB -Order "unspecified" -QosPolicyName "" -StatsPolicyName "default" -SwitchId "B" -VnicName $iSCSIvNICNameB$mo_1 = $mo | Add-UcsVnicVlan -Name "" -VlanName $iScsiVlanBComplete-UcsTransaction | Out-NullWrite-Host "Setting iSCSI Boot Parameters for Fabric A"Start-UcsTransaction$mo = Get-UcsServiceProfile -Org $tenantorg .dn -Name $tenantname | Add-UcsVnicIScsi -Name $iSCSIvNICNameA -AdaptorProfileName $iSCSIAdapterPolicyName -Addr "derived" -AdminVcon "any" -ExtIPState "none" -IqnIdentPoolName $tenantname -Order "unspecified" -QosPolicyName "" -StatsPolicyName "default" -SwitchId "A" -VnicName $iSCSIvNICNameA -ModifyPresent$mo_1 = $mo | Add-UcsVnicVlan -VlanName $iScsiVlanA -ModifyPresent$mo_1_1 = $mo_1 | Add-UcsVnicIScsiStaticTargetIf -IpAddress $iSCSITargetIPControllerAPort1 -Name $iSCSITargetIQNA -Port 3260 -Priority 1$mo_1_1_1 = $mo_1_1 | Add-UcsVnicLun -Bootable "no" -Id 0 -ModifyPresent$mo_1_2 = $mo_1 | Add-UcsVnicIPv4If -ModifyPresent$mo_1_2_1 = $mo_1_2 | Add-UcsVnicIPv4Dhcp -ModifyPresentComplete-UcsTransaction | Out-NullWrite-Host "Setting iSCSI Boot Parameters for Fabric B"Start-UcsTransaction$mo = Get-UcsServiceProfile -Org $tenantorg .dn -Name $tenantname | Add-UcsVnicIScsi -Name $iSCSIvNICNameB -AdaptorProfileName $iSCSIAdapterPolicyName -Addr "derived" -AdminVcon "any" -ExtIPState "none" -IqnIdentPoolName $tenantname -Order "unspecified" -QosPolicyName "" -StatsPolicyName "default" -SwitchId "B" -VnicName $iSCSIvNICNameB -ModifyPresent$mo_1 = $mo | Add-UcsVnicVlan -VlanName $iScsiVlanB -ModifyPresent$mo_1_1 = $mo_1 | Add-UcsVnicIScsiStaticTargetIf -IpAddress $iSCSITargetIPControllerAPort2 -Name $iSCSITargetIQNA -Port 3260 -Priority 1$mo_1_1_1 = $mo_1_1 | Add-UcsVnicLun -Bootable "no" -Id 0 -ModifyPresent$mo_1_2 = $mo_1 | Add-UcsVnicIPv4If -ModifyPresent$mo_1_2_1 = $mo_1_2 | Add-UcsVnicIPv4Dhcp -ModifyPresentComplete-UcsTransaction | Out-NullWrite-Host "Create Service Profiles from Template"$mo = Get-UcsServiceProfile -Org $tenantorg .dn -Name $tenantname | Add-UcsServiceProfileFromTemplate -Prefix $VMHostNamePrefix -Count $VMHostCount -DestinationOrg $tenantorg .dnWrite-Host "Unbind Service Profiles from Template and set static IP address"Start-UcsTransaction$ProfileIP = $tenantfirstIP$j = 0$i = 1while ( $i -le $VMHostCount){$VMHostName = $VMHostNamePrefix + $i$iSCSIInitiatorIp_iSCSI_A_var = $iSCSIInitiatorIp_iSCSI_A + $profileIP$iSCSIInitiatorIp_iSCSI_B_var = $iSCSIInitiatorIp_iSCSI_B + $profileIP$tenantorg | Get-UcsServiceProfile -Name $VMHostName -LimitScope | Set-UcsServiceProfile -AgentPolicyName "" -BiosProfileName "" -BootPolicyName $tenantname -Descr "" -DynamicConPolicyName "" -ExtIPState "none" -HostFwPolicyName "" -IdentPoolName $tenantname -LocalDiskPolicyName $tenantname -MaintPolicyName "" -MgmtAccessPolicyName "" -MgmtFwPolicyName "" -PowerPolicyName $tenantname -ScrubPolicyName $tenantname -SolPolicyName "" -SrcTemplName "" -StatsPolicyName "default" -UsrLbl "" -VconProfileName "" -Force$mo = $tenantorg | Get-UcsServiceProfile -Name $VMHostName -LimitScope | Add-UcsVnicIScsi -Name $iSCSIvNICNameA -AdaptorProfileName $iSCSIAdapterPolicyName -Addr "derived" -AdminVcon "any" -ExtIPState "none" -IqnIdentPoolName $tenantname -Order "unspecified" -StatsPolicyName "default" -SwitchId "A" -VnicName $iSCSIvNICNameA -ModifyPresent$mo_1 = $mo | Add-UcsVnicVlan -Name "" -VlanName $iScsiVlanA -ModifyPresent$mo_1_1 = $mo_1 | Add-UcsVnicIScsiStaticTargetIf -Priority 1 -IpAddress $iSCSITargetIPControllerAPort1 -Name $iSCSITargetIQNA -Port 3260 -ModifyPresent$mo_1_1_1 = $mo_1_1 | Add-UcsVnicLun -Bootable "no" -Id $VMHostBootLUNID [ $j ] -ModifyPresent$mo_1_2 = $mo_1 | Add-UcsVnicIPv4If -Name "" -ModifyPresent$mo_1_2_1 = Get-UcsOrg -Level root | Get-UcsOrg -Name $tenantname -LimitScope | Get-UcsServiceProfile -Name $VMHostName -LimitScope | Get-UcsVnicIScsi -Name $iSCSIvNICNameA | Get-UcsVnicVlan | Get-UcsVnicIPv4If | Get-UcsVnicIPv4Dhcp | Remove-UcsVnicIPv4Dhcp -Force$mo_1_2_2 = $mo_1_2 | Add-UcsVnicIPv4IscsiAddr -Addr $iSCSIInitiatorIp_iSCSI_A_var -DefGw $iSCSITargetIPControllerAPort1 -PrimDns "0.0.0.0" -SecDns "0.0.0.0" -Subnet "255.255.255.0" -ModifyPresent$mo = $tenantorg | Get-UcsServiceProfile -Name $VMHostName -LimitScope | Add-UcsVnicIScsi -Name $iSCSIvNICNameB -AdaptorProfileName $iSCSIAdapterPolicyName -Addr "derived" -AdminVcon "any" -ExtIPState "none" -IqnIdentPoolName $tenantname -Order "unspecified" -StatsPolicyName "default" -SwitchId "B" -VnicName $iSCSIvNICNameB -ModifyPresent$mo_1 = $mo | Add-UcsVnicVlan -Name "" -VlanName $iScsiVlanB -ModifyPresent$mo_1_1 = $mo_1 | Add-UcsVnicIScsiStaticTargetIf -Priority 1 -AuthProfileName "" -IpAddress $iSCSITargetIPControllerAPort2 -Name $iSCSITargetIQNA -Port 3260 -ModifyPresent$mo_1_1_1 = $mo_1_1 | Add-UcsVnicLun -Bootable "no" -Id $VMHostBootLUNID [ $j ] -ModifyPresent$mo_1_2 = $mo_1 | Add-UcsVnicIPv4If -Name "" -ModifyPresent$mo_1_2_1 = Get-UcsOrg -Level root | Get-UcsOrg -Name $tenantname -LimitScope | Get-UcsServiceProfile -Name $VMHostName -LimitScope | Get-UcsVnicIScsi -Name $iSCSIvNICNameB | Get-UcsVnicVlan | Get-UcsVnicIPv4If | Get-UcsVnicIPv4Dhcp | Remove-UcsVnicIPv4Dhcp -Force$mo_1_2_2 = $mo_1_2 | Add-UcsVnicIPv4IscsiAddr -ModifyPresent -Addr $iSCSIInitiatorIP_iSCSI_B_var -DefGw $iSCSITargetIPControllerAPort2 -PrimDns "0.0.0.0" -SecDns "0.0.0.0" -Subnet "255.255.255.0"$profileIP ++$J ++$i ++}Complete-UcsTransaction# Logout of UCSWrite-Host "UCS: Logging out of UCS: $ucs "$ucslogout = Disconnect-Ucs}Catch{Write-Host "Error occurred in script:"Write-Host ${Error}exit}Rename-UcsHyperVNICs.ps1
<#Rename-UcsHyperVNICs.ps1Script to rename the NICs on the host to match the names on the Service ProfileNOTE: There are some variables that need to be changed to reflect your environment.- change the IP address for accessing UCSMThis script will work running between two systems that are in the same domain or twosystems that are in workgroups. It will not work across domain-workgroup.The following Windows firewall rules must be enabled on the target machine.COM+ Network Access (DCOM-IN)Windows Management Instrumentation (WMI-IN)#># Import required modulesif (( Get-Module | where { $_ .Name -ilike "CiscoUcsPS"}) .Name -ine "CiscoUcsPS"){Write-Host "Loading Module: Cisco UCS PowerTool Module"Import-Module CiscoUcsPs}set-ucspowertoolconfiguration -supportmultipledefaultucs $false### Variables to be tailored to customer environment ###$UcsmAddress = "192.168.1.1"$ucsuser = "admin"$ucspass = "admin"# Connect to UCSM$ucspasswd = ConvertTo-SecureString $ucspass -AsPlainText -Force$ucscreds = New-Object System.Management.Automation.PSCredential ( $ucsuser , $ucspasswd)$UCSMHandle = Connect-Ucs -Credential $ucscreds $UcsmAddress# Get Name of server to work onWrite-Host "Enter server on which to rename default NIC names"Write-Host "The name of the server and the name of the UCS Service Profile must be the same"$Srvr = Read-Host "NOTE: Case must be EXACTLY the same as the UCS Service Profile"$Org = Read-Host "Enter Sub-Organization name of Service Profile, or 'root'"$OrgLevel = Get-UcsOrg -Name $Org$SrvrProfile = $OrgLevel .DN + "/" + $Srvr# Retrieve table of NICs from the UCS Profile$UCSAdapters = Get-UcsVnic -ServiceProfile $SrvrProfileForEach ( $UcsA in $UcsAdapters) {$NICindex = ( Get-WMIobject Win32_NetworkAdapterConfiguration -namespace "root\CIMV2" -computername $Srvr | Where-Object { $_ .MACaddress -eq $UcsA .Addr}) .Index$NIC = ( Get-WMIobject Win32_NetworkAdapter -computername $Srvr | Where-Object { $_ .Index -eq $NICindex})If ( $NIC .NetconnectionID -ne $UcsA .name) {$NIC .NetconnectionID = $UcsA .name$NIC .Put()}}Disconnect-UcsSet-UcsHyperVRemoteMgmt.ps1
## Set-UcsHyperVRemoteMgmt.ps1## This script works on a variety of settings that are easiest done from the local machine to make it# remotely manageable by a management workstation.# Set some firewall rules# Allow ping requests inSet-NetFirewallRule -Name "FPS-ICMP4-ERQ-In" -Enabled True# Allow ping requests outSet-NetFirewallRule -Name "FPS-ICMP4-ERQ-Out" -Enabled True# Allow remote disk management - firewall rules need to be set on both source and destination computers# ***NOTE*** Policy must also be set on system to "Allow remote access to the Plug and Play interface"# This is done with gpedit.msc locally or gpedit for domain policySet-NetFirewallRule -Name "RVM-VDS-In-TCP" -Enabled TrueSet-NetFirewallRule -Name "RVM-VDSLDR-In-TCP" -Enabled TrueSet-NetFirewallRule -Name "RVM-RPCSS-In-TCP" -Enabled True# Allow DCOM management requests inSet-NetFirewallRule -Name "ComPlusNetworkAccess-DCOM-In" -Enabled True# Allow WMI management requets inSet-NetFirewallRule -Name "WMI-WINMGMT-In-TCP" -Enabled True# Set some services to automatically start and start them.Set-Service -Name PlugPlay -StartupType AutomaticStart-Service PlugPlaySet-Service -Name RemoteRegistry -StartupType AutomaticStart-Service RemoteRegistrySet-Service -Name vds -StartupType AutomaticStart-Service vds# Enable Remote Desktop; Do not require NLA( Get-WmiObject Win32_TerminalServiceSetting -Namespace root\cimv2\TerminalServices) .SetAllowTsConnections( 1 , 1) | Out-Null( Get-WmiObject -Class "Win32_TSGeneralSetting" -Namespace root\cimv2\TerminalServices -Filter "TerminalName='RDP-tcp'") .SetUserAuthenticationRequired( 0) | Out-NullSet-UcsHyperVIps.ps1
## Set-UcsHyperVIPs.ps1## This script will set the proper IP configuration values for the following networks# ClusComm# CSV# LiveMigration# VMaccess#Write-Host "This script sets IP configuration for the ClusComm, CSV, LiveMigration, and VMaccess networks."Write-Host "It assumes that the above names are the names of the networks to be set."Write-Host "The addresses are configured as '192.168.vlan.host'. The value for host is used for all networks."Write-Host "The value for vlan is entered for each network."Write-Host " "$target = Read-Host "Enter the name of the Hyper-V host to target"$hostnum = Read-Host "Enter a numeric value between 1-254 to use as the host number"$cluscommID = Read-Host "Enter the VLAN for 'ClusComm'"$csvID = Read-Host "Enter the VLAN for 'CSV'"$livemigrationID = Read-Host "Enter the VLAN for 'LiveMigration'"$vmaccessID = Read-Host "Enter the VLAN for 'VMaccess'"$cluscommIP = "192.168." + $cluscommID + "." + $hostnum$csvIP = "192.168." + $csvID + "." + $hostnum$livemigrationIP = "192.168." + $livemigrationID + "." + $hostnum$vmaccessIP = "192.168." + $vmaccessID + "." + $hostnum$nics = gwmi Win32_NetworkAdapter -ComputerName $target$i = 0While ( $i -le $nics .length - 1) {if ( $nics [ $i ].netconnectionid -eq "ClusComm") {$idx = $nics [ $i ].index$netinf = gwmi Win32_NetworkAdapterConfiguration -ComputerName $target | where { $_ .Index -eq $idx}$netinf .DHCPenabled = $False$netinf .enablestatic( $cluscommIP , "255.255.255.0") | out-null$netinf .SetDynamicDNSRegistration( $false) | out-null}if ( $nics [ $i ].netconnectionid -eq "CSV") {$idx = $nics [ $i ].index$netinf = gwmi Win32_NetworkAdapterConfiguration -ComputerName $target | where { $_ .Index -eq $idx}$netinf .DHCPenabled = $False$netinf .enablestatic( $csvIP , "255.255.255.0") | out-null$netinf .SetDynamicDNSRegistration( $false) | out-null}if ( $nics [ $i ].netconnectionid -eq "LiveMigration") {$idx = $nics [ $i ].index$netinf = gwmi Win32_NetworkAdapterConfiguration -ComputerName $target | where { $_ .Index -eq $idx}$netinf .DHCPenabled = $False$netinf .enablestatic( $livemigrationIP , "255.255.255.0") | out-null$netinf .SetDynamicDNSRegistration( $false) | out-null}if ( $nics [ $i ].netconnectionid -eq "VMaccess") {$idx = $nics [ $i ].index$netinf = gwmi Win32_NetworkAdapterConfiguration -ComputerName $target | where { $_ .Index -eq $idx}$netinf .DHCPenabled = $False$netinf .enablestatic( $vmaccessIP , "255.255.255.0") | out-null$netinf .SetDynamicDNSRegistration( $false) | out-null}$i ++}Add-UcsHyperVFeatures.ps1
$Srvr = Read-Host "Enter computer name of server to receive features"Install-WindowsFeature -Name Failover-Clustering -ComputerName $Srvr -IncludeManagementToolsInstall-WindowsFeature -Name Multipath-IO -ComputerName $Srvr -IncludeManagementToolsInstall-WindowsFeature -Name Hyper-V -ComputerName $Srvr -IncludeManagementTools -RestartCreate-UcsHyperVSwitches.ps1
## Create-UcsHyperVSwitches.ps1### Create the Hyper-V virtual switches on a specific host.## This script may need to be edited to reflect customer naming conventions#$cluscomm = "ClusComm"$iscsia = "iSCSI-A"$iscsib = "iSCSI-B"$vmaccess = "VMaccess"$target = Read-Host "Enter the name of the Hyper-V host on which virtual switches will be created"New-VMSwitch -Name $vmaccess -ComputerName $target -AllowManagementOS $FALSE -NetAdapterName $vmaccess# The following switches are needed only if there are plans for having VM clusters# New-VMSwitch -Name $cluscomm -ComputerName $target -AllowManagementOS $TRUE -NetAdapterName $cluscomm# New-VMSwitch -Name $iscsia -ComputerName $target -AllowManagementOS $TRUE -NetAdapterName $iscsia# New-VMSwitch -Name $iscsib -ComputerName $target -AllowManagementOS $TRUE -NetAdapterName $iscsibSet-UcsClusterMetrics.ps1
$clstr = Read-Host "Enter name of cluster"Get-ClusterNetwork -Cluster $clstr | FT Name , Role , Metric( Get-ClusterNetwork "CSV" -Cluster $clstr) .Metric = 800( Get-ClusterNetwork "LiveMigration" -Cluster $clstr) .Metric = 900Get-ClusterNetwork -Cluster $clstr | FT Name , Role , MetricCreate-UcsHyperVSingleVM.ps1
# This script is meant to be run from a clustered host.#Import required modulesif (( Get-Module | Where { $_ .Name -ilike "FailoverClusters"}) .Name -ine "FailoverClusters"){Write-Host "Loading Module: FailoverClusters"Import-Module FailoverClusters}if (( Get-Module | Where { $_ .Name -ilike "ServerManager"}) .Name -ine "ServerManager"){Write-Host "Loading Module: ServerManager"Import-Module ServerManager}if (( Get-Module | Where { $_ .Name -ilike "Hyper-V"}) .Name -ine "Hyper-V"){Write-Host "Loading Module: Hyper-V"Import-Module Hyper-V}# Source for template VHDX file. Ensure this matches customer environment.$TemplateSrc = "C:\ClusterStorage\Volume1\Template\Virtual Hard Disks\Template.vhdx"# Destination directory for target VHDX. Ensure this matches customer environment.$TemplateDst = "C:\ClusterStorage\Volume2\" + $VMname + "\Virtual Hard Disks\"# Get the name of the VM to be created.$VMname = Read-Host "Enter name of VM to create"$NicName = Read-Host "Enter name of vNIC to add to VM (name is same as virtual switch)"$DestVhd = $TemplateDst + $VMname + ".vhdx"# Create a VM with no vhd. Capture VMinfo to pipe to other commands$VMinfo = New-VM $VMname -Path C:\ClusterStorage\Volume2 -NoVhd# Create Virtual Hard Disks subdirectory; Suppress the console outputmd $TemplateDst | Out-Null# Copy and rename the Template vhdx to the new locationWrite-Host "Copying the base VHD. This takes a few minutes."Copy-Item $TemplateSrc $DestVhd# Add the just copied vhdx file to the VM$VMinfo | Add-VMHardDiskDrive -ControllerType IDE -ControllerNumber 0 -Path $DestVhd#Remove the default "Network Adapter"$VMinfo | Remove-VMNetworkAdapter -Name "Network Adapter"# Add appropriate network adapters; one per line$VMinfo | Add-VMNetworkAdapter -Name $NicName -SwitchName $NicName# Enable Dynamic Memory$VMinfo | Set-VMMemory -DynamicMemoryEnabled $True# Make the VM highly available by adding to cluster$VMinfo | Add-ClusterVirtualMachineRolempclaim.bat
@echo offrem Display current storage devices that MS MPIO currently claimsmpclaim.exe -hrem Check the existing devices claimed by Microsoft MPIO DSMmpclaim.exe -s -drem Display the vendor product ID string for the connected arraympclaim.exe -erem Add addition device IDs in case they are needed in the futurerem Reboot on last changempclaim.exe -n -i -d "DGC DISK"mpclaim.exe -n -i -d "DGC LUNZ"mpclaim.exe -n -i -d "DGC RAID 0"mpclaim.exe -n -i -d "DGC RAID 1"mpclaim.exe -n -i -d "DGC RAID 10"mpclaim.exe -n -i -d "DGC RAID 5"mpclaim.exe -r -i -d "DGC VRAID"Example VNXe Unisphere CLI Commands to Change the MTU size on the VNXe
#Specifying mtu for SPA ports will also change the SPB portuemcli -d 10.0.0.1 -u Local/admin -p <password> /net/port -id eth10_SPA set -mtuSize 9000uemcli -d 10.0.0.1 -u Local/admin -p <password> /net/port -id eth11_SPA set -mtuSize 9000Example Script to Configure Maximum Transmission Unit (MTU) Size on Windows Server 2012
$Contents = get-content mtu.txtWrite-Host "There are" $Contents .Count "entries in the mtu configuration file."foreach ( $Line in $Contents){$hostname , $alias , $mtuval , $addfam = [ regex ]::split( $Line , '\s+')#Write-Host "Hostname:" $Hostname "Interface Alias:" $alias "MTU:" $mtuval "IP Family:" $addfaminvoke-command -computername $hostname -scriptblock { param( $1 , $2 , $3) set-netipinterface -InterfaceAlias $1 -NlMtuBytes $2 -AddressFamily $3} -argumentlist $alias , $mtuval , $addfam$?#Invoke-Command -ComputerName $hostname -ScriptBlock {param($1,$2) Get-NetIpInterface -InterfaceAlias $1 -AddressFamily $2} -argumentlist $alias, $addfam}Sample mtu.txt File Used for Input with the MTU Script
EMCFT301 10Gb_1 9000 IPV4EMCFT301 10Gb_2 9000 IPV4EMCFT302 10Gb_1 9000 IPV4EMCFT302 10Gb_2 9000 IPV4Example Script to Configure MPIO
Enable-WindowsOptionalFeature -Online -FeatureName MultipathIOWnable-MsdsmAutomaticClaim -BusType iSCSI#Ensure there are 5 spaces after EMC and 9 spaces after CelerraNew-MsdsmSupportedHw -VendorID "EMC Celerra "Example Script to Configure iSCSI Sessions on Windows Server 2012
#Variables$hostinitA1 = "192.168.15.100"$hostinitA2 = "192.168.16.100"$VNXetargetA1 = "192.168.15.10"$VNXetargetA2 = "192.168.16.10"$iscsitarget = "iqn.1992-05.com.emc:apm001221019710000-3-vnxe"$ChapNameA = "iqn.1991-05.com.microsoft:emcft301.rdcrpw.eng.emc.com"$ChapPasswordA = "EMCFT3021234"#iSCSI serviceSet-Service -Name msiscsi -StartupType automaticStart-Service msiscsi#iscsi targetsNew-IscsiTargetPortal -TargetPortalAddress $VNXetargetA1 -InitiatorPortalAddress $hostinitA1New-IscsiTargetPortal -TargetPortalAddress $VNXetargetA2 -InitiatorPortalAddress $hostinitA2#Following connect string commented out due to automatic session created during boot time#connect-iscsitarget -nodeaddress $iscsitarget -AuthenticationType ONEWAYCHAP -ChapUserName $ChapNameA -ChapSecret $ChapPasswordA -InitiatorPortalAddress $hostinitA1 -TargetPortalAddress $VNXetargetA1 -IsMultipathEnabled $true -IsPersistent $trueConnect-IscsiTarget -NodeAddress $iscsitarget -AuthenticationType ONEWAYCHAP -ChapUserName $ChapNameA -ChapSecret $ChapPasswordA -InitiatorPortalAddress $hostinitA2 -TargetPortalAddress $VNXetargetA2 -IsMultipathEnabled $true -IsPersistent $trueExample Script to Create iSCSI LUNs Using ESI PowerShell
#Script assumes the VNXe was registered with ESI using:#get-emcstoragesystemcredential | connect-emcsystem# Script created using ESI V2.1$Contents = Get-Content CFG_STORAGE.txt$MyArray = "FTVNXe"Function PoolExists {Param ( $TGTPool)$Val = Get-EmcStoragePool $TGTPool -Silentif ( $Val -eq $null) { return $false} else { return $true}}Function LUNExists {Param ( $TGTLUN)$Val = Get-EmcLUN $TGTLUN -Silentif ( $Val -eq $null) { return $false} else { return $true}}$StorageArray = Get-EMCStorageSystem -ID $MyArrayUpdate-EmcSystem $StorageArrayif ( $Contents) { Write-Host "There are" $Contents .Count "entries in the storage configuration file."}foreach ( $Line in $Contents){$LUN , $Pool , $Size , $Servicenodeiqn = [ regex ]::split( $Line , '\s+')if ( $Contents) { Write-Host "Name of LUN: " $LUN "Name of Pool:" $Pool "Size of LUN:" $Size "IQN:" $Servicenodeiqn}if (( $TGTServer -eq $null) -or ( $TGTServer -eq $Server)){If ( PoolExists $Pool){$MyPool = Get-EmcStoragePool $Pool -Silent# Check for pre-existing LUNIF ( LUNExists $LUN) { Write-Host "LUN" $LUN "already exists."}else{ # We need to create the LUN$ssn = Get-EmcStorageSystem -id $MyArray | Get-EmcStorageServiceNode | where { $_ .DisplayText -match $servicenodeiqn}$Size = Invoke-Expression $Size$NewLUN = New-EmcLun -Pool $MyPool [ 0 ] -Name $LUN -Capacity $Size -Description $LUN -StorageServiceNode $ssn}}else{# Pool not found, so we errorif ( $DEBUG){Write-Host "ERROR: Pool" $Pool "does not exist in the array"}exit 1}}}Sample CFG_Storage.txt File Used for Input with the LUN Creation Script
Witness Performance 10gb iqn.1992-05.com.emc:apm001221019710000-3-vnxeCSV01 Performance 1000gb iqn.1992-05.com.emc:apm001221019710000-4-vnxeCSV02 Performance 1000gb iqn.1992-05.com.emc:apm001221019710000-3-vnxeCSV03 Performance 1000gb iqn.1992-05.com.emc:apm001221019710000-4-vnxeExample Script to Mask iSCSI LUNs to Hosts Using ESI Powershell
#Script assumes hosts were registered with ESI using:#Get-EmcHostSystemCredential | Connect-EmcSystem#Script assumes the VNXe was registered with ESI using:#Get-EmcStorageSystemCredential | Connect-EmcSystem# Script created using ESI V2.1$Contents = Get-Content CFG_access.txt$MyArray = "FTVNXe"$StorageArray = Get-EMCStorageSystem -ID $MyArrayUpdate-EmcSystem $StorageArrayif ( $Contents) { Write-Host "There are" $Contents .Count "entries in the access configuration file."}foreach ( $Line in $Contents){$LUN , $ESIHost , $IQN = [ regex ]::split( $Line , '\s+')if ( $Contents) { Write-Host "Name of LUN: " $LUN "Name of ESI Host:" $ESIHost "Host IQN:" $iqn}$ESIHost = Get-EmcHostSystem $ESIHost$LUN = Get-EmcLun $LUN$SetAccess = Set-EMCLunAccess -LUN $LUN -InitiatorID $IQN -HostName $ESIHost -HostIpAddress $ESIHost -Available}Sample CFG_Access.txt File Used for Input with the LUN Masking Script
Witness EMCFT301 iqn.1991-05.com.microsoft:emcft301.rdcrpw.eng.emc.comCSV01 EMCFT301 iqn.1991-05.com.microsoft:emcft301.rdcrpw.eng.emc.comCSV02 EMCFT301 iqn.1991-05.com.microsoft:emcft301.rdcrpw.eng.emc.comCSV03 EMCFT301 iqn.1991-05.com.microsoft:emcft301.rdcrpw.eng.emc.comWitness EMCFT302 iqn.1991-05.com.microsoft:emcft302.rdcrpw.eng.emc.comCSV01 EMCFT302 iqn.1991-05.com.microsoft:emcft302.rdcrpw.eng.emc.comCSV02 EMCFT302 iqn.1991-05.com.microsoft:emcft302.rdcrpw.eng.emc.comCSV03 EMCFT302 iqn.1991-05.com.microsoft:emcft302.rdcrpw.eng.emc.com
Feedback