Cisco Virtualization Solution for EMC VSPEX with Microsoft Hyper-V 2012 R2 for up to 300 Virtual Machines
Available Languages
Table Of Contents
About Cisco Validated Design (CVD) Program
Cisco Unified Computing System
EMC Storage Technology and Benefits
Memory Configuration Guidelines
Hyper-V Memory Management Concepts
Solution for up to 300 Hyper-V Virtual Machines
Preparing Cisco Nexus Switches
Configure Cisco Nexus Switches
Set Up Initial Cisco Nexus 5548 Switch
Enable Appropriate Cisco Nexus Features
Add Individual Port Descriptions for Troubleshooting
Create Necessary Port Channels
Add Port Channel Configurations
Configure Virtual Port Channels
Link Into Existing Network Infrastructure
Initial Configuration of Cisco Unified Computing System
Logging Into Cisco UCS Manager
Create the VSPEX Environment with Cisco UCS PowerTool
Create the VSPEX Environment with Cisco UCS Manager
Add a Block of IP Addresses for KVM Access
Edit the Chassis Discovery Policy
Enable Quality of Service in Cisco UCS Fabric
Create a Local Disk Configuration Policy
Enable Fabric Interconnect Port Definitions
Create Uplink Port Channels to the Cisco Nexus 5548 Switches
Create Service Profile Templates and Service Profiles
Create EMC VNX5400 LUNs for VSPEX
Configure Zoning on Cisco Nexus 5548 Switches
Create Device Aliases and Create Zone for First Server
Install Initial Microsoft Windows Server 2012 R2
Mask Boot LUNs to Service Profiles
Complete Image Builds from Sysprepped Images
Install EMC Unisphere Host Agent
Create Hyper-V Failover Cluster
Cisco Nexus 1000V Installation
Create Two Virtual Supervisor Module Virtual Machines
Configure Virtual Switch Extension Manager in VMM
Copy Virtual Ethernet Module Installation Packager to the VMM Virtual Machines
Configure a Logical Switch in VMM
Create the Logical Switch on the Hyper-V Hosts
Create a Virtual Machine Network
Configure the Virtual Machine Manager Virtual Machine Properties
Customer Configuration Worksheets
Cisco UCS Network Infrastructure
Cisco 6248 Fabric Interconnect A
Cisco 6248 Fabric Interconnect B
Cisco Unified Computing System Configuration
Determine VNX FCoE Ports and WWNs
Cisco Virtualization Solution for EMC VSPEX with Microsoft Hyper-V 2012 R2 for up to 300 Virtual MachinesLast Updated: January 8, 2014
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.
Prashanto Kochavara, Solutions Engineer, EMC
Prashanto has been working for the EMC solutions group for over 3 years. Prashanto is a SME on EMC Storage and Virtualization technologies including VMware and Hyper-V. He has vast amount of experience in end-to-end solution planning and deployments of VSPEX architectures. Prior to joining the solutions group at EMC, Prashanto has interned as a Systems Engineer (EMC) and Software Developer (MBMS Inc.). Prashanto holds a Bachelor's degree in Computer Engineering from SUNY Buffalo and will be graduating with a Master's Degree in Computer Science from North Carolina State University in December 2013.
Acknowledgments
For their support and contribution to the design, validation, and creation of this Cisco Validated Design, we would like to thank:
•
Mike Mankovsky—Technical Lead, 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 Virtualization Solution for EMC VSPEX with Microsoft Hyper-V 2012 R2 for up to 300 Virtual Machines
Executive Summary
Cisco solution for EMC VSPEX is a pre-validated and modular architecture built with proven best-of-breed technologies to create and complete an end-to-end virtualization solution. The end-to-end solutions enable you to make an informed decision while choosing the hypervisor, compute, storage, and networking layers. VSPEX minimizes the server virtualization planning and configuration burdens. The VSPEX infrastructures accelerate your IT Transformation by enabling faster deployments, greater flexibility of choice, efficiency, and lower risk. This Cisco Validated Design document focuses on the Microsoft Windows Server 2012 R2 Hyper-V architecture for up to 300 virtual machines with Cisco solution for the EMC VSPEX.
Introduction
Virtualization is a key and critical strategic deployment model for reducing the Total Cost of Ownership (TCO) and achieving better utilization of platform components like hardware, software, network, and storage. However, choosing an appropriate platform for virtualization can be challenging. Virtualization platforms should be flexible, reliable, and cost effective to facilitate the deployment of various enterprise applications. In a virtualization platform for compute, network, and storage resources to be used effectively, the ability to slice and dice the underlying platform is essential to size the application requirements. The Cisco solution for the EMC VSPEX provides a very simplistic yet fully integrated and validated infrastructure to deploy VMs in various sizes to suit various application needs.
Target Audience
The reader of this document is expected to have the necessary training and background to install and configure Microsoft Windows Server 2012 R2, EMC VNX5400, Cisco Nexus 5548UP switch, and Cisco Unified Computing (UCS) B200 M3 Blade Servers. External references are provided wherever applicable and it is recommended that the reader be familiar with these documents.
Readers are also expected to be familiar with the infrastructure and database security policies of the customer installation.
Purpose of This Guide
This document describes the overall design goals of the Cisco solution for EMC VSPEX for Microsoft Hyper-V. The document provides an architectural description of the solution for providing up to 300 virtual machines.
Business Needs
The VSPEX solutions are built with proven best-of-breed technologies to create complete virtualization solutions that enable you to make an informed decision in the hypervisor, server, and networking layers. The VSPEX infrastructures accelerate your IT transformation by enabling faster deployments, greater flexibility of choice, efficiency, and lower risk.
Business applications are moving into the consolidated compute, network, and storage environment. The Cisco solution for the EMC VSPEX using Microsoft Hyper-V reduces the complexity of configuring every component of a traditional deployment model. The complexity of integration management is reduced while maintaining the application design and implementation options. Administration is unified, while process separation can be adequately controlled and monitored. The following are the business needs for the Cisco solution for EMC VSPEX using Microsoft Hyper-V architectures:
•
•
•
Solution Overview
The Cisco solution for EMC VSPEX using Microsoft Windows Server 2012 R2 provides an end-to-end architecture with Cisco, EMC, and Microsoft technologies that demonstrate support for up to 300, 600, or 1000 generic virtual machines and provide high availability and server redundancy.
The following are the components used for the design and deployment:
•
•
•
•
•
•
•
•
•
The solution is designed to host scalable and mixed application workloads. The scope of this Cisco Validated Design document is limited to the Cisco solution for EMC VSPEX Microsoft Hyper-V solutions for up to 300 virtual machines only. When the base configuration is in place, it is a simple matter of adding more servers or storage to handle the larger workloads.
Table 1 Components for up to 300, 600, or 1000 Virtual Machines
Technology Overview
Cisco Unified Computing System
The Cisco Unified Computing System is a next-generation data center platform that unites compute, network, and storage access. The platform, optimized for virtual environments, is designed using open industry-standard technologies and aims to reduce total cost of ownership (TCO) and increase business agility. The system integrates a low-latency; lossless 10 Gigabit Ethernet unified network fabric with enterprise-class, x86-architecture servers. It is an integrated, scalable, multi chassis platform in which all resources participate in a unified management domain.
The main components of Cisco Unified Computing System are:
•
•
•
•
•
The Cisco Unified Computing System is designed to deliver:
•
•
•
•
•
Cisco UCS Manager
Cisco UCS Manager provides unified, embedded management of all software and hardware components of the Cisco Unified Computing System through an intuitive GUI, a command line interface (CLI), a Microsoft PowerShell module, or an XML API. The Cisco UCS Manager provides unified management domain with centralized management capabilities and controls multiple chassis and thousands of virtual machines.
Cisco UCS Fabric Interconnect
The Cisco® UCS 6200 Series Fabric Interconnect is a core part of the Cisco Unified Computing System, providing both network connectivity and management capabilities for the system. The Cisco UCS 6200 Series offers line-rate, low-latency, lossless 10 Gigabit Ethernet, Fibre Channel over Ethernet (FCoE), and Fibre Channel functions.
The Cisco UCS 6200 Series provides the management and communication backbone for the Cisco UCS B-Series Blade Servers and Cisco UCS 5100 Series Blade Server Chassis. All chassis, and therefore all blades, attached to the Cisco UCS 6200 Series Fabric Interconnects become part of a single, highly available management domain. In addition, by supporting unified fabric, the Cisco UCS 6200 Series provides both the LAN and SAN connectivity for all blades within its domain.
From a networking perspective, the Cisco UCS 6200 Series uses a cut-through architecture, supporting deterministic, low-latency, line-rate 10 Gigabit Ethernet on all ports, 1 Tb switching capacity, 160 Gbps bandwidth per chassis, independent of packet size and enabled services. The product family supports Cisco low-latency, lossless 10 Gigabit Ethernet unified network fabric capabilities, which increase the reliability, efficiency, and scalability of Ethernet networks. The Fabric Interconnect supports multiple traffic classes over a lossless Ethernet fabric from a blade server through an interconnect. Significant TCO savings come from an FCoE-optimized server design in which network interface cards (NICs), host bus adapters (HBAs), cables, and switches can be consolidated.
The Cisco UCS 6248UP 48-Port Fabric Interconnect is a one-rack-unit (1RU) 10 Gigabit Ethernet, FCoE and Fibre Channel switch offering up to 960-Gbps throughput and up to 48 ports. The switch has 32 1/10-Gbps fixed Ethernet, FCoE, and FC ports and one expansion slot.
Figure 1 Cisco UCS 6248UP Fabric Interconnect
Cisco UCS Fabric Extenders
The Cisco UCS 2200 Series Fabric Extenders multiplex and forward all traffic from blade servers in a chassis to a parent Cisco UCS fabric interconnect over from 10-Gbps unified fabric links. All traffic, even traffic between blades on the same chassis or virtual machines on the same blade, is forwarded to the parent interconnect, where network profiles are managed efficiently and effectively by the fabric interconnect. At the core of the Cisco UCS fabric extender are application-specific integrated circuit (ASIC) processors developed by Cisco that multiplex all traffic.
The Cisco UCS 2204XP Fabric Extender has four 10 Gigabit Ethernet, FCoE-capable, SFP+ ports that connect the blade chassis to the fabric interconnect. Each Cisco UCS 2204XP has sixteen 10 Gigabit Ethernet ports connected through the midplane to each half-width slot in the chassis. Typically configured in pairs for redundancy, two fabric extenders provide up to 80 Gbps of I/O to the chassis.
Figure 2 Cisco UCS 2204XP Fabric Extender
Cisco UCS Blade Chassis
The Cisco UCS 5100 Series Blade Server Chassis is a crucial building block of the Cisco Unified Computing System, delivering a scalable and flexible blade server chassis.
The Cisco UCS 5108 Blade Server Chassis is six rack units (6RU) high and can mount in an industry-standard 19-inch rack. A single chassis can house up to eight half-width Cisco UCS B-Series Blade Servers and can accommodate both half-width and full-width blade form factors.
Four single-phase, hot-swappable power supplies are accessible from the front of the chassis. These power supplies are 92 per cent efficient and can be configured to support non-redundant, N+ 1 redundant, and grid-redundant configurations. The rear of the chassis contains eight hot-swappable fans, four power connectors (one per power supply), and two I/O bays for Cisco UCS 2204XP Fabric Extenders.
A passive mid-plane provides up to 40 Gbps of I/O bandwidth per server slot and up to 80 Gbps of I/O bandwidth for two slots. The chassis is capable of supporting future 40 Gigabit Ethernet standards. The Cisco UCS Blade Server Chassis is shown in Figure 3.
Figure 3 Cisco UCS 5108 Blade Server Chassis (back and front)
Cisco UCS Blade Servers
Delivering performance, versatility, and density without compromise, the Cisco UCS B200 M3 Blade Server addresses the broadest set of workloads, from IT and Web Infrastructure through distributed database to virtualization.
Building on the success of the Cisco UCS B200 M2 blade servers, the enterprise-class Cisco UCS B200 M3 server further extends the capabilities of Cisco's Unified Computing System portfolio in a half blade form factor. The Cisco UCS B200 M3 server harnesses the power and efficiency of the Intel Xeon E5-2600 processor product family, up to 768 GB of RAM, 2 drives or SSDs and up to 2 x 20 GE to deliver exceptional levels of performance, memory expandability, and I/O throughput for nearly all applications. In addition, the Cisco UCS B200 M3 blade server offers a modern design that removes the need for redundant switching components in every chassis in favor of a simplified top of rack design, allowing more space for server resources, providing a density, power, and performance advantage over previous generation servers. The Cisco UCS B200 M3 Server is shown in Figure 4.
Figure 4 Cisco UCS B200 M3 Blade Server
Cisco Nexus 5548UP Switch
The Cisco Nexus 5548UP is a 1RU 1 Gigabit and 10 Gigabit Ethernet switch offering up to 960 gigabits per second throughput and scaling up to 48 ports. It offers 32 1/10 Gigabit Ethernet fixed enhanced Small Form-Factor Pluggable (SFP+) Ethernet/FCoE or 1/2/4/8-Gbps native FC unified ports and three expansion slots. These slots have a combination of Ethernet/FCoE and native FC ports. The Cisco Nexus 5548UP switch is shown in Figure 5.
Figure 5 Cisco Nexus 5548UP Switch
Cisco I/O Adapters
Cisco UCS Blade Servers support various Converged Network Adapter (CNA) options. Cisco UCS Virtual Interface Card (VIC) 1240 is used in this EMC VSPEX solution.
The Cisco UCS Virtual Interface Card 1240 is a 4-port 10 Gigabit Ethernet, Fibre Channel over Ethernet (FCoE)-capable modular LAN on motherboard (mLOM) designed exclusively for the M3 generation of Cisco UCS B-Series Blade Servers. When used in combination with an optional Port Expander, the Cisco UCS VIC 1240 capabilities can be expanded to eight ports of 10 Gigabit Ethernet.
The Cisco UCS VIC 1240 enables a policy-based, stateless, agile server infrastructure that can present up to 256 PCIe standards-compliant interfaces to the host that can be dynamically configured as either network interface cards (NICs) or host bus adapters (HBAs). In addition, the Cisco UCS VIC 1240 supports Cisco Data Center Virtual Machine Fabric Extender (VM-FEX) technology, which extends the Cisco UCS fabric interconnect ports to virtual machines, simplifying server virtualization deployment.
Figure 6 Cisco UCS VIC 1240
Cisco UCS Differentiators
Cisco's Unified Computing System is revolutionizing the way servers are managed in data centers.
Following are the unique differentiators of Cisco UCS and Cisco UCS Manager.
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Microsoft Hyper-V 2012 R2
Microsoft Hyper-V 2012 R2 is a next-generation virtualization solution from Microsoft that builds upon previous releases and provides greater levels of scalability, security, and availability to virtualized environments. Hyper-V 2012 R2 offers improvements in performance and utilization of CPU, memory, and I/O. It also offers users the option to assign up to 64 virtual CPU to a virtual machine—giving system administrators more flexibility in their virtual server farms as processor-intensive workloads continue to increase. Table 2 illustrates the increase in scale from the previous major release.
Table 2 Hyper-V Scale
Microsoft provides System Center 2012 R2 to provide additional management capabilities to a virtualized and physical environment. This Design document assumes the existence of a System Center Virtual Machine Manager server, but Hyper-V provides significant management capabilities without the addition of System Center. Included in the base capabilities of Hyper-V are:
•
•
•
•
•
•
•
•
•
•
EMC Storage Technology and Benefits
The VNX storage series provides both file and block access with a broad feature set, which makes it an ideal choice for any private cloud implementation.
VNX storage includes the following components, sized for the stated reference architecture workload:
•
•
•
•
Note
The Microsoft Hyper-V private cloud solutions for 300, 600, and 1,000 virtual machines described in this document are based on the EMC VNX5400, EMC VNX5600, and the EMC VNX5800 storage arrays, respectively. The VNX5400 array can support a maximum of 250 drives, the VNX5600 can host up to 500 drives, and the VNX5800 can host up to 750 drives.
The VNX series supports a wide range of business-class features that are ideal for the private cloud environment, including:
•
•
•
•
•
•
•
•
•
Features and Enhancements
The EMC VNX flash-optimized unified storage platform delivers innovation and enterprise capabilities for file, block, and object storage in a single, scalable, and easy-to-use solution. Ideal for mixed workloads in physical or virtual environments, VNX combines powerful and flexible hardware with advanced efficiency, management, and protection software to meet the demanding needs of today's virtualized application environments.
VNX includes many features and enhancements designed and built upon the first generation's success. These features and enhancements include:
•
•
•
•
VSPEX is built with the next generation of VNX to deliver even greater efficiency, performance, and scale than ever before.
Flash-Optimized Hybrid Array
VNX is a flash-optimized hybrid array that provides automated tiering to deliver the best performance to your critical data, while intelligently moving less frequently accessed data to lower-cost disks.
In this hybrid approach, a small percentage of flash drives in the overall system can provide a high percentage of the overall IOPS. A flash-optimized VNX takes full advantage of the low latency of flash to deliver cost-saving optimization and high performance scalability. The EMC Fully Automated Storage Tiering Suite (FAST Cache and FAST VP) tiers both block and file data across heterogeneous drives and boosts the most active data to the cache, ensuring that customers never have to make concessions for cost or performance.
FAST VP dynamically absorbs unpredicted spikes in system workloads. As that data ages and becomes less active over time, FAST VP tiers the data from high-performance to high-capacity drives automatically, based on customer-defined policies. This functionality has been enhanced with four times better granularity and with new FAST VP solid-state disks (SSDs) based on enterprise multi-level cell (eMLC) technology to lower the cost per gigabyte. All VSPEX use cases benefit from the increased efficiency.
VSPEX Proven Infrastructures deliver private cloud, end-user computing, and virtualized application solutions. With VNX, customers can realize an even greater return on their investment. VNX provides out-of-band, block-based deduplication that can dramatically lower the costs of the flash tier.
VNX Intel MCx Code Path Optimization
The advent of flash technology has been a catalyst in totally changing the requirements of midrange storage systems. EMC redesigned the midrange storage platform to efficiently optimize multicore CPUs to provide the highest performing storage system at the lowest cost in the market.
MCx distributes all VNX data services across all cores—up to 32, as shown in Figure 7. The VNX series with MCx has dramatically improved the file performance for transactional applications like databases or virtual machines over network-attached storage (NAS).
Figure 7 Next-Generation VNX with multicore optimization
Multicore Cache
The cache is the most valuable asset in the storage subsystem; its efficient use is key to the overall efficiency of the platform in handling variable and changing workloads. The cache engine has been modularized to take advantage of all the cores available in the system.
Multicore RAID
Another important part of the MCx redesign is the handling of I/O to the permanent back-end storage-hard disk drives (HDDs) and SSDs. Greatly increased performance improvements in VNX come from the modularization of the back-end data management processing, which enables MCx to seamlessly scale across all processors.
VNX Performance
Performance enhancements
VNX storage, enabled with the MCx architecture, is optimized for FLASH 1st and provides unprecedented overall performance, optimizing for transaction performance (cost per IOPS), bandwidth performance (cost per GB/s) with low latency, and providing optimal capacity efficiency (cost per GB).
VNX provides the following performance improvements:
•
•
•
•
Active/Active Array Storage Processors
The new VNX architecture provides active/active array storage processors, as shown in the following figure, which eliminate application timeouts during path failover since both paths are actively serving I/O.
Load balancing is also improved and applications can achieve an up to two times improvement in performance. Active/Active for block is ideal for applications that require the highest levels of availability and performance, but do not require tiering or efficiency services like compression, deduplication, or snapshot.
With this VNX release, VSPEX customers can use virtual Data Movers (VDMs) and VNX Replicator to perform automated and high-speed file system migrations between systems. This process migrates all snaps and settings automatically, and enables the clients to continue operation during the migration.
Figure 8 Active/active processors increase performance, resiliency, and efficiency
Unisphere Management Suite
The new Unisphere Management Suite extends Unisphere's easy-to-use, interface to include VNX Monitoring and Reporting for validating performance and anticipating capacity requirements. As shown in the following figure, the suite also includes Unisphere Remote for centrally managing up to thousands of VNX and VNXe systems with new support for XtremSW Cache.
Figure 9 Unisphere Management Suite
Virtualization Management
EMC Storage Integrator
EMC Storage Integrator (ESI) is targeted towards the Windows and Application administrator. ESI is easy to use, delivers end-to end monitoring, and is hypervisor agnostic. Administrators can provision in both virtual and physical environments for a Windows platform, and troubleshoot by viewing the topology of an application from the underlying hypervisor to the storage.
Microsoft Hyper-V
With Windows Server 2012, Microsoft provides Hyper-V 3.0, an enhanced hypervisor for private cloud that can run on NAS protocols for simplified connectivity.
Offloaded Data Transfer
The Offloaded Data Transfer (ODX) feature of Microsoft Hyper-V enables data transfers during copy operations to be offloaded to the storage array, freeing up host cycles. For example, using ODX for a live migration of a SQL Server virtual machine doubled performance, decreased migration time by 50 percent, reduced CPU on the Hyper-V sever by 20 percent, and eliminated network traffic.
EMC Avamar
EMC's Avamar® data deduplication technology seamlessly integrates into virtual environments, providing rapid backup and restoration capabilities. Avamar's deduplication results in vastly less data traversing the network, and greatly reduces the amount of data being backed up and stored; resulting in storage, bandwidth and operational savings.
The following are the two most common recovery requests used in backup and recovery:
•
•
The Avamar System State protection functionality adds backup and recovery capabilities in both of these scenarios.
Architectural Overview
This Cisco Design discusses the deployment model of the Microsoft Hyper-V 2012 R2 solution for up to 300 virtual machines. Understanding the virtual machine workloads vary from customer to customer, Cisco server components can be easily added in single server increments to address the exact workload of the customer.
Table 3 lists the hardware requirements of the designed solution.
Table 3 Hardware Requirements
Table 4 lists the various firmware and software components for this VSPEX design.
Table 4 Firmware and Software Components
Table 5 outlines the Cisco UCS B200 M3 server configuration details.
Table 5 Server Configuration Details
Component
Capacity
Memory (RAM)
192 GB (12 x 16 GB)
Processor
2 x Intel E2650 CPUs, 2.6 GHz, 8 cores, 16 threads
Adapters
Cisco VIC 1240
This architecture assumes there is an existing infrastructure / management network available in which a virtual machine hosting Microsoft System Center Virtual Machine Manager 2012 R2 server and Windows Active Directory/DNS/DHCP server are present. Figure 10 illustrates a high-level Cisco solution for EMC VSPEX Microsoft Hyper-V architecture for up to 300 virtual machines.
Figure 10 Reference Architecture for up to 300 Virtual Machines
The following are the high-level design points of the architecture:
•
•
•
This design does not recommend or require any specific layout of infrastructure network. The Virtual Machine Manager server and AD/DNS/DHCP virtual machines are hosted on the infrastructure network. However, design does require accessibility of certain VLANs from the infrastructure network to reach the servers.
Hyper-V 2012 R2 is used as the hypervisor on each server and is installed on fibre channel SAN. The defined load is 60 virtual machines per Cisco UCS B200 M3 server blade.
Memory Configuration Guidelines
This section provides guidelines for allocating memory to the virtual machines. The guidelines outlined here take into account Hyper-V memory overhead and the virtual machine memory settings.
Hyper-V Memory Management Concepts
Microsoft Hyper-V has a number of advanced features to maximize performance, and overall resource utilization. The most important features relate to memory management. This section describes some of these features, and the items to consider when using these features in the VSPEX environment.
Dynamic Memory
Dynamic Memory was introduced in Windows Server 2008 R2 SP1 to increase physical memory efficiency by treating memory as a shared resource, and dynamically allocating it to virtual machines. The amount of memory used by each virtual machine is adjustable at any time. Dynamic Memory reclaims unused memory from idle virtual machines, which allows more virtual machines to run at any given time. In Windows Server 2012, Dynamic Memory enables administrators to dynamically increase the maximum memory available to virtual machines.
Dynamic memory pools all the physical memory available on a physical host and dynamically distributes it to virtual machines running on that host as the virtual machines need it. As workloads change, virtual machines will be able to dynamically ask for memory if it is needed or dynamically release memory if it is no longer needed without service interruptions.
Dynamic Memory requires that a virtual machine have a minimum and maximum size of virtual memory assigned. The virtual machine will never have less memory assigned to it than what is specified by the minimum and never ask for more than what is specified as the maximum. When a virtual machine is initialized, it is given the minimum amount specified. As processes are loaded, they create a demand for a specific amount of memory. If the virtual machine does not yet have enough physical memory assigned to it based on its demand, the hypervisor and SLAT will allocate more physical memory to ensure optimal performance. If the virtual machine is no longer using memory, it uses a ballooning technique to free up unused physical memory to return to Hyper-V to be allocated to other virtual machines that need the memory.
One of the things that often happens is that when a machine, physical or virtual, is first starting, it may require more physical memory than it would require while it is running its normal tasks. This happens due to the many startup processes that are run to get the system running but then stop once they have performed their function. Therefore, Hyper-V also has a startup RAM setting that can be set larger than the minimum, thereby ensuring more memory at startup for a faster startup time. After the virtual machine has started and has it normal processes running, the ballooning technology will free any excess memory for use by other virtual machines.
In addition to the startup, minimum, and maximum settings offered by Hyper-V, it also allows two other settings to optimize memory usage. One setting is to specify the percentage of memory that Hyper-V should try to reserve as a buffer for the virtual machine. Then when the virtual machine has a demand for more physical memory, it can draw from this buffer instead going through the more intensive route of asking for new physical memory. This ensures a quicker response to memory demands within the virtual machine. The second setting is a memory weight that specifies how to prioritize memory demands for one virtual machine in relationship to the demands of other virtual machines. This allows for high-priority virtual machines to have their memory demands satisfied before lower priority virtual machines.
Smart Paging
Even with Dynamic Memory, Hyper-V allows more virtual machines than the available physical memory can support. In most cases, there is a memory gap between minimum memory and startup memory. Smart Paging is a memory management technique that uses disk resources as temporary memory replacement. It swaps out less-used memory to disk storage, and swaps in when needed. Performance degradation is a potential drawback of Smart Paging. Hyper-V continues to use the guest paging when the host memory is oversubscribed because it is more efficient than Smart Paging.
Non-Uniform Memory Access
Non-Uniform Memory Access (NUMA) is a multi-node computer technology that enables a CPU to access remote-node memory. This type of memory access degrades performance, so Windows Server 2012 employs a process known as processor affinity, which pins threads to a single CPU to avoid remote-node memory access. In previous versions of Windows, this feature is only available to the host. Windows Server 2012 extends this functionality to the virtual machines, which provides improved performance in symmetrical multiprocessor (SMP) environments.
Allocating Memory to Virtual Machines
Memory sizing for a virtual machine in VSPEX architectures is based on many factors. With the number of application services and use cases available determining a suitable configuration for an environment requires creating a baseline configuration, testing, and making adjustments, as discussed later in this paper. Table 6 outlines the resources used by a single virtual machine.
Table 6 Resources for a Single Virtual Machine
The following are some recommended best practices for memory allocation:
•
•
•
•
In addition to accounting for the memory used by the virtual machines, you should also allow the host to have at least 2 GB for the parent partition. This partition includes processes for monitoring and managing the environment and features such as the built-in failover clustering capability. Additionally control information for the running of the virtual machines is also stored in this memory.
Storage Guidelines
VSPEX architecture for Microsoft Hyper-V up to 300 VMs uses Fibre Channel to access storage arrays. The Hyper-V hosts boot from the SAN storage, ensuring stateless configuration for the individual Hyper-V hosts. If one of the Cisco UCS B200 M3 servers becomes unavailable for any reason, the service profile defining that server's configuration can be associated to another Cisco UCS B200 M3 server and boot from the same operating system image on the SAN without any reconfiguration to bring it into service. The shared storage for storing VMs and their data uses the same storage array and protocol, minimizing the management overhead associated with managing VM storage. VMs can access Fibre Channel LUNs directly (optional) using virtual HBAs in the VMs. Highly available failover clusters built with VMs can use either the virtual HBAs or simply shared virtual hard disks (VHDX) stored on the array.
Virtual Server Configuration
Storage for Hyper-V can be categorized into three layers of storage technology:
•
•
–
–
•
–
–
–
Figure 11 illustrates the above explanation.
Figure 11 Hyper-V Storage Virtualization Stack
Storage Protocol Capabilities
The EMC VNX5400 provides Hyper-V and storage administrators with the flexibility to use the storage protocol that meets the requirements or standards of the business. This can be a single protocol datacenter-wide or multiple protocols for tiered scenarios. The EMC VNX5400 can support Fibre Channel, FCoE, iSCSI, and SMB protocols.
The Cisco solution for EMC VSPEX with Microsoft Hyper-V recommends a single protocol, Fibre Channel, throughout in order to simplify the design.
Storage Best Practices
It is recommended that storage administrators become familiar with Microsoft's suggestions for performance tuning. They have published a document that can be found at:
http://msdn.microsoft.com/en-us/library/windows/hardware/jj248719.aspx.
•
•
•
•
•
Storage Layout
Figure 12 shows the physical disk layout. Disk provisioning on the VNX5400 storage array is simplified through the use of wizards, so that administrators do not choose which disks belong to a given storage pool. The wizard may choose any available disk of the proper type, regardless of where the disk physically resides in the array.
Figure 12 Storage Architecture for up to 300 Virtual Machines
The reference architecture uses the following configuration:
•
•
Note
•
•
•
The VNX family storage array is designed for five 9s availability (99.999% uptime) by using redundant components throughout the array. All of the array components are capable of continued operation in case of hardware failure. The RAID disk configuration on the array provides protection against data loss due to individual disk failures, and the available hot spare drives can be dynamically allocated to replace a failing disk.
Storage Building Blocks
VSPEX uses a building block approach to reduce this complexity. A building block is a set of disk spindles that can support a certain number of virtual servers in the VSPEX architecture. Each building block combines several disk spindles to create a storage pool that supports the needs of the private cloud environment. Each building block storage pool, regardless of the size, contains two flash drives with FAST VP storage tiering to enhance metadata operations and performance.
VSPEX solutions have been engineered to provide a variety of sizing configurations which afford flexibility when designing the solution. Customers can start out by deploying smaller configurations and scale up as their needs grow. At the same time, customers can avoid over-purchasing by choosing a configuration that closely meets their needs. To accomplish this, VSPEX solutions can be deployed using one or both of the scale-points below to obtain the ideal configuration while guaranteeing a given performance level.
Building Block for 13 Virtual Servers
The first building block can contain up to 13 virtual servers. It has two flash drives and five SAS drives in a storage pool.
Figure 13 13 Virtual Server Building Block
This is the smallest building block qualified for the VSPEX architecture. This building block can be expanded by adding five SAS drives and allowing the pool to restripe to add support for 13 more virtual servers.
Building Block for 125 Virtual Servers
The second building block can contain up to 125 virtual servers. It contains two flash drives, and 45 SAS drives. The preceding sections outline an approach to grow from 13 virtual machines in a pool to 125 virtual machines in a pool. However, after reaching 125 virtual machines in a pool, do not go to 138. Create a new pool and start the scaling sequence again.
Figure 14 125 Virtual Server Building Block
Each building block for 125 VMs would be presented to the host as two LUNs to be used as CSV for storing 62 or 63 virtual machines.
Implement this building block with all of the resources in the pool initially, or expand the pool over time as the environment grows. Table 7 lists the flash and SAS requirements in a pool for different numbers of virtual servers.
Table 7 Number of disks required for different numbers of virtual machines
Virtual Servers
FlasH Drives
SAS Drives
13
3
5
26
2
10
39
2
15
52
2
20
65
2
25
78
2
30
104
2
35
117
2
45
125
2
45*
Note
To grow the environment beyond 125 virtual servers, create another storage pool using the building block method described here.
Using this building block approach to scalability, the following two diagrams picture the storage layout for 600 and 1000 virtual machines.
Figure 15 VNX5600 Storage for 600 VMs
Figure 16 VNX5800 Storage for 1000 VMs
Networking Guidelines
The following are some recommended best practices for networking with Hyper-V:
•
•
Recommended NICs
The recommended and suggested networking for a Microsoft Hyper-V solution have the following NICs:
•
•
•
–
–
•
Optional NICs
Depending on your business needs, you might be requirements to have additional networks as follows:
•
•
•
Quality of Service
It is recommended to define a quality of service for the Live Migration network to ensure optimal performance. If iSCSI and/or SMB networks are defined, it is recommended to define a quality of service for their use. In general, the QoS defined for storage will be different from the QoS defined for live migration.
Solution for up to 300 Hyper-V Virtual Machines
The key aspects of the Cisco UCS with EMC VNX5400 for up to 300 Hyper-V virtual machines solution are as follows:
•
•
•
•
•
•
Stateless Computing
Cisco UCS Manager (UCSM) provides the concept of a Service Profile for a server running on a physical hardware. A service profile is a logical entity associated to a physical server. Among other things, service profile includes various identities of the server or server components, such as:
•
•
•
•
•
•
All these identities can be assigned to any physical server managed by the Cisco UCS Manager. All other configuration of the service profile is based on templates, pools, and policies, providing immense flexibility to the administrator. This includes firmware and BIOS versions required by the server. These concepts enable Cisco UCS Manager to provide stateless computing across the entire Cisco UCS Manager managed compute hardware. If remote storage is used to boot operating system of the server (such as SAN boot, PXE boot, iSCSI boot, etc.), a given service profile can be associated to any physical server hardware and downtime for migrating such a server can be reduced to few minutes. The solution presented in this CVD makes use of identity pools and SAN storage to simplify the server procurement and provide stateless computing capability.
Sizing Guidelines
In any discussion about virtual infrastructures, it is important to first define a reference workload. Not all servers perform the same tasks, and it is impractical to build a reference that takes into account every possible combination of workload characteristics.
Defining the Reference Workload
To simplify the discussion, a representative customer reference workload is defined as a virtual machine with specific characteristics. By comparing the actual customer usage to this reference workload, one can extrapolate which reference architecture to choose.
For the VSPEX solutions, the reference workload was defined as a single virtual machine. This virtual machine has the following characteristics (Table 8).
Table 8 Reference Virtual Machine Workload
This specification for a virtual machine is not intended to represent any specific application. Rather, it represents a single common point of reference to measure other virtual machines.
Applying the Reference Workload
When considering an existing server which will move into a virtual infrastructure, you have the opportunity to gain efficiency by right-sizing the virtual hardware resources assigned to that system.
The reference architecture creates a pool of resources sufficient to host a target number of reference virtual machines as described above. It is entirely probable that customer virtual machines will not exactly match the specifications above. In that case, you can say that a single specific customer virtual machine is the equivalent of some number of reference virtual machines, and assume that number of virtual machines have been used in the pool. You can continue to provision virtual machines from the pool of resources until it is exhausted. Consider these examples:
Example 1 - Customer Built Application
A small custom-built application server will move into this virtual infrastructure. The physical hardware supporting the application is not being fully utilized at present. A careful analysis of the existing application reveals the application uses only one processor and needs 3 GB of memory to run efficiently. The IO workload ranges between 4 IOPS at idle time to 15 IOPS when busy. The entire application is only using about 30 GB on local hard drive storage.
The following resources are needed from the resource pool to virtualize this application:
•
•
•
•
In this example a single virtual machine uses the resources of two reference virtual machines. When this VM is deployed, the solution's new capability would be 298 VMs.
Example 2 - Point of Sale System
The database server for a customer's point-of-sale system will move into this virtual infrastructure. It is currently running on a physical system with four CPUs and 16 GB of memory. It uses 200 GB storage and generates 200 IOPS during an average busy cycle.
The following resources are needed from the resource pool to virtualize this application:
•
•
•
•
In this example, the one virtual machine uses the resources of eight reference virtual machines. Once this VM is deployed, the solution's new capability would be 292 VMs.
Example 3 - Web Server
The customer's web server will move into this virtual infrastructure. It is currently running on a physical system with two CPUs and 8GB of memory. It uses 25 GB of storage and generates 50 IOPS during an average busy cycle.
The following resources are needed from the resource pool to virtualize this application:
•
•
•
•
In this example the virtual machine would use the resources of four reference virtual machines. Once this VM is deployed, the solution's new capability would be 296 VMs.
Example 4 - Decision Support Database
The database server for a customer's decision support system will move into this virtual infrastructure. It is currently running on a physical system with 10 CPUs and 48 GB of memory. It uses 5 TB of storage and generates 700 IOPS during an average busy cycle.
The following resources are needed from the resource pool to virtualize this application:
•
•
•
•
In this example the one virtual machine uses the resources of fifty reference virtual machines. When this VM is deployed, the solution's new capability would be 250 VMs.
Summary of Examples
The four examples show the flexibility of the resource pool model. In all four cases the workloads simply reduce the number of available resources in the pool. If all four examples were implemented on the same virtual infrastructure, with an initial capacity of up to 300 virtual machines, they would leave a capacity for 236 reference virtual machines in the resource pool.
In more advanced cases, there may be trade-offs between memory and I/O or other relationships where increasing the amount of one resource, decreases the need for another. In these cases, the interactions between resource allocations become highly complex and are out of the scope of this document. However, when a change in the resource balance is observed, and the new level of requirements is known; these virtual machines can be added to the infrastructure using the method described in the above examples.
If the customer does not have a thorough understanding of the resource needs of their particular environment, Microsoft has a free tool, Microsoft Assessment and Planning Toolkit, that can be run against the customer environment to capture the actual characteristics. This tool can be found at www.microsoft.com/map.
Configuration Guidelines
This section provides the procedure to deploy the Cisco solution for EMC VSPEX Hyper-V architecture.
Follow these steps to configure the Cisco solution for EMC VSPEX VMware architectures:
•
•
•
•
•
•
•
•
•
These steps are described in detail in the following sections.
Included in this document are sample PowerShell scripts that can be used to more quickly build out this VSPEX environment. Though the scripts have been tested, no warranty is implied or granted that they do not contain errors. The use of these scripts assumes a 'green field' environment in which nothing else has been previously installed. In any case, each script should be examined before execution in the customer environment. Several of the scripts may have IP addresses hard coded in them that need to be changed to reflect the customer environment.
It is assumed that a person familiar with Microsoft's PowerShell scripting language is available to review these scripts for the customer before execution in the customer environment. In particular, the UcsConfig.xml file contains many variables that should be reviewed with the customer to ensure they reflect the customer environment and naming conventions.
Pre-deployment Tasks
Pre-deployment tasks include procedures that do not directly relate to environment installation and configuration, but whose results will be needed at the time of installation. Examples of pre-deployment tasks are collection of hostnames, IP addresses, VLAN IDs, license keys, installation media, and so on. These tasks should be performed before the customer visit to decrease the time required onsite.
•
•
•
Table 9 Requisite Components
Configuration 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.
Windows 8 (8.1) Workstation
•
•
•
–
•
Windows Server 2012 (2012 R2)
•
•
•
Tools on Both Workstations
•
•
•
•
•
•
You can download all the software listed in the revision table to this workstation. Some of the software, such as distribution media, can be placed into a file share for access by other systems.
There are several PowerShell scripts contained in the Sample PowerShell Scripts section 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 Sample PowerShell Scripts, do the following.
1.
2.
3.
4.
Physical Setup
Physical setup includes the following tasks:
1.
2.
3.
Make use of the appropriate vendor installation guides.
Cisco UCS Components
For information on mounting the hardware, see the Cisco UCS B-Series Hardware Installation Guide.
Care must be taken about efficient cooling and proper airflow while mounting any equipment in the data center. Similarly, you need to pay attention to power requirements of chassis, servers, and fabric interconnects.
Cisco UCS 5108 chassis, including its embedded blade servers and fabric extenders, do not require management connectivity as they are managed by the fabric interconnects. Fabric interconnects are deployed as a pair for high availability. Both the fabric interconnects require 100 Mbps peer connectivity for synchronizing the management plane between them. In addition, both the FIs require 1Gbps out-of-band management connectivity.
Cisco UCS Manager software runs on the Cisco UCS Fabric Interconnects. The Cisco UCS 6000 Series Fabric Interconnects expand the UCS networking portfolio and offer higher capacity, higher port density, and lower power consumption. These interconnects provide the management and communication backbone for the Cisco UCS B-Series Blades and Cisco UCS Blade Server Chassis. All chassis and the blade servers attached to the fabric interconnects are part of a single, highly available management domain. By supporting unified fabric, the Cisco UCS 6000 Series provides the flexibility to support LAN and SAN connectivity for all blade servers within its domain right at the configuration time. Typically deployed in redundant pairs, the Cisco UCS Fabric Interconnect provides uniform access to both network and storage, facilitating a fully virtualized environment.
Initial setup steps of Cisco UCS 6248UP Fabric Interconnects and the Cisco UCS Manager are similar to those of the Nexus 5548UP switches:
1.
2.
3.
4.
5.
Cisco UCS 5108 Chassis, Cisco UCS 2204XP Fabric Extenders and Cisco UCS B200 M3 blade servers would be part of the Cisco UCS Manager (UCSM) management domain, so no special configuration is required for them.
Preparing Cisco Nexus Switches
Cisco Nexus 5548UP switches are 1RU top of the rack 10Gbps Ethernet and Fibre Channel switches.
For information on how to deploy these switches, see Nexus 5548UP Product Documentation.
For initial configuration of these switches, follow these steps:
1.
2.
3.
4.
Preparing EMC VNX5400
Initial configuration and implementation of an EMC VNX5400 is covered in detail from the EMC documentation library. This is accessible at https://mydocs.emc.com/VNX/ and select Install VNX, using the VNX5400 series as the installation type. Installation documentation covers all areas from unpacking VNX storage components, installing in rack, provisioning power requirements and physical cabling.
When physically installed, the VNX should include the Disk Processing Enclosure (DPE) and two additional Disk Array Enclosures (DAEs), cabled as shown in Figure 17.
Figure 17 Cabling Diagram for VNX5400 with Two DAE
To complete software setup of the VNX array, it will be necessary to configure system connectivity including the creation of an Administrative user for the VNX array. The following worksheets (also found in the Installation documentation) list all required information, and can be used to facilitate the initial installation.
VNX Worksheets
With your network administrator, determine the IP addresses and network parameters you plan to use with the storage system, and record the information on the following worksheet. You must have this information to set up and initialize the system. The VNX5400 array is managed through a dedicated LAN port on the Control Station and each storage processor. These ports must share a subnet with the host you use to initialize the system. After initialization, any host on the same network and with a supported browser can manage the system through the management ports. This information can be recorded in Table 10.
Table 10 IPv4 Management Port Information
Note
While it is possible to implement IPv6 settings for the VNX array, the VSPEX implementation does not require it, and it is not implemented.
It is possible to more fully configure management IP addresses for the VNX5400 array. Table 11 lists some of the addresses you can optionally configure.
Table 11 Optional Control Station LAN Settings
An administrative user account is required to be set for the array, and this account can be later utilized for executing NaviSecCLI commands, as well as for the ESI PowerShell environment used to provision LUNs from storage pools, and map those LUNs to hosts. Information required is outlined in Table 12.
Table 12 Login Information for the Storage System Administrator
It is also necessary at this time to install the NaviSecCli command line interface from a supported Windows client environment. The client should have network access to the VNX5400 array for both HTTP/HTTPS access and for remote NaviSecCli command execution.
Installation media for the NaviSecCli utility, as well as ESI, are available by download at http://support.emc.com. The current version of the media should always be utilized. Installation of the utility is implemented through the typical application installation process for Windows-based systems.
After array installation, it will also be possible to connect to the VNX5400 array via the Unisphere graphical user interface at the IP address assigned to either SP-A or SP-B, or the control station in the event that a Unified version of the VNX is being implemented.
After entering appropriate login credentials, the Unisphere home page will be presented, providing an overview of the VNX5400 storage array. Summary alerts and errors will be visible as well as full management capabilities for all array features.
The following configuration also assumes that the array has been configured with:
•
•
•
In the event that the physical configuration of the system differs in regards to the DAE placements, then modifications to the Bus Enclosure naming used subsequently will need to be appropriately altered.
Creating Storage Pools—Unisphere
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
Note
Creating Support for Clone Private LUNs
In the previous step storage pools were defined on the VNX array based on disks within the chassis. Additional RAID Group based LUNs are required to support clone private LUNs in the system. As part of the automation of Virtual Machine deployments, SnapView Clones can be utilized both through scripting and also through the SMI-S integration of System Center Virtual Machine Manager.
The use of clones requires the existence of at least one RAID group on the VNX5400 for storage of the clone private LUNs used in the cloning process. To help ensure proper performance for the number of virtual machines, all available free disks are configured into storage pools. Therefore, it will be necessary to create a RAID group using the system drives and configure just the clone private LUNs, and no others, on this RAID group.
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
Note
16.
17.
18.
19.
20.
21.
22.
23.
Record WWNN and WWPN Values
The Fibre Channel protocol uses Worldwide Node Names (WWNN) and Worldwide Port Names (WWPN) as addresses to uniquely identify endpoints in the Fibre Channel communication. These values must be recorded to be used in other steps in this configuration. For example, the WWPN values need to be entered into the UcsConfig.xml file used to configure UCS.
Obtain the WWPN information from the EMC VNX5400 by using the NaviSecCli that is installed on your Windows management system and record it in the WWNN/WWPN worksheet found in the Customer Configuration Worksheet section. Following is an example for obtaining the WWPNs from the connections to the VNX5400. It may be necessary to provide additional parameters, for login, password and scope options. The example below returns configuration information for all ports configured within the array. The WWPN for any given Fibre Channel port is derived from the last half of the SP UID entry. The first half of the SP UID is the WWNN entry. As an example, the WWNN of the array is 50:06:01:60:88:60:06:A1 and the WWPN of Port 4 on SP-A Port ID 4 is 50:06:01:64:08:60:06:A1.
C:\> naviseccli -address <<IP Address of SP-A or SP-B>> -User <<Admin user>> -Password <<Admin user password>> -Scope 0 port -list -spSP Name: SP ASP Port ID: 4SP UID: 50:06:01:60:88:60:06:A1:50:06:01:64:08:60:06:A1Link Status: UpPort Status: OnlineSwitch Present: YESSwitch UID: 20:02:00:05:73:A1:DA:C1:20:02:00:05:73:A1:DA:C1SP Source ID: 4...(report truncated)Alternatively EMC Storage Integrator (ESI) PowerShell Toolkit can be used to obtain WWPN and IQN information like the following examples.
$targetports = Get-EmcTargetPort$targetports | Where {$_.PortLocation -like "*Module 4*"} | fl PortLocation, @{Expression={$_.Wwn.tostring().substring(0,23)};Label="WWNN"},@{Expression={$_.Wwn.tostring().substring(24)};Label="WWPN"}PortLocation : SP A I/O Module 4 Port 4WWNN : 50:06:01:60:88:60:06:A1WWPN : 50:06:01:64:08:60:06:A1PortLocation : SP A I/O Module 4 Port 5WWNN : 50:06:01:60:88:60:06:A1WWPN : 50:06:01:65:08:60:06:A1PortLocation : SP B I/O Module 4 Port 4WWNN : 50:06:01:60:88:60:06:A1WWPN : 50:06:01:6C:08:60:06:A1PortLocation : SP B I/O Module 4 Port 5WWNN : 50:06:01:60:88:60:06:A1WWPN : 50:06:01:6D:08:60:06:A1Or, the information can be found from EMC Unisphere. You will need to find the SP-Ports that are connected to the Cisco Nexus 5548 switches.
Cable Connectivity
The Customer Configuration Worksheet section of this document contains tables showing the cabling that was used to validate this configuration for up to 300 virtual machines. If a different configuration is implemented, update the worksheets for reference documentation.
Configure Cisco Nexus Switches
The following sections provide a detailed procedure for configuring the Cisco Nexus 5548 switches for use in this solution. Follow these steps precisely because failure to do so could result in an improper configuration. Make use of information captured in the Customer Configuration Worksheets to complete these steps.
In the Sample PowerShell Scripts section is a sample script, UcsConfig.ps1, for configuration UCS to reflect the cabling configuration shown in the Customer Configuration Worksheets. UcsConfig.ps1 reads the information from the UcsConfig.xml file, also contained in the Sample PowerShell Scripts sections. If changes are made to cabling configuration, the XML file will need to be edited to reflect those changes.
Set Up Initial Cisco Nexus 5548 Switch
These steps provide details for the initial Cisco Nexus 5548 Switch setup.
Cisco Nexus 5548 A
On initial boot and connection to the serial or console port of the switch, the NX-OS setup should automatically start.
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
21.
22.
23.
24.
25.
Cisco Nexus 5548 B
On initial boot and connection to the serial or console port of the switch, the NX-OS setup should automatically start.
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
21.
22.
23.
24.
25.
Enable Appropriate Cisco Nexus Features
These commands enable the appropriate Cisco Nexus features.
Nexus A and Nexus B
config tfeature lacpfeature fcoefeature npivfeature vpcfeature fport-channel-trunkfeature interface-vlanspanning-tree port type network defaultspanning-tree port type edge bpduguard defaultspanning-tree port type edge bpdufilter defaultcopy run startConfigure Fibre Channel Ports
These commands configure the necessary FC ports on the Nexus switches.
Nexus A and Nexus B
config tslot 1port 29-32 type fccopy run startreload.The Nexus switch will reboot. This will take several minutes.
Create Necessary VLANs
These steps provide details for creating the necessary VLANs. Note that the SMB (or iSCSI) VLANs are not created on the Nexus switches. The SMB (or iSCSI) connections are made directly from the Fabric Interconnects to the EMC VNX array. The Nexus switches do not see this SMB (or iSCSI)-related traffic.
Nexus A and Nexus B
Following the switch reloads, log in with user admin and the password previously entered.These commands define the minimum VLANs used in this configuration.
config tvlan <MGMT VLAN ID>name Mgmtexitvlan <CSV VLAN ID>name CSVexitvlan <Live Migration VLAN ID>name LiveMigrationexitvlan <VMaccess VLAN ID>name VMaccessexitcopy run startAdd Individual Port Descriptions for Troubleshooting
These add individual port descriptions for troubleshooting activity and verification.
Cisco Nexus 5548 A
config tinterface Eth1/1description <Nexus B:Eth1/1>exitinterface Eth1/2description <Nexus B:Eth1/2>exitinterface Eth1/17description <UCSM A:Eth1/17>exitinterface Eth1/18description <UCSM B:Eth1/17>exitcopy run startCisco Nexus 5548 B
config tinterface Eth1/1description <Nexus A:Eth1/1>exitinterface Eth1/2description <Nexus A:Eth1/2>exitinterface Eth1/17description <UCSM B:Eth1/18>exitinterface Eth1/18description <UCSM A:Eth1/18>exitcopy run startCreate Necessary Port Channels
These commands create the necessary port channels between devices.
Cisco Nexus 5548 A
config tinterface Po10description vPC Peer-Linkexitinterface Eth1/1-2channel-group 10 mode activeno shutdownexitinterface Po201description <VSPEX-UCS-A>exitinterface Eth1/17channel-group 201 mode activeno shutdownexitinterface Po202description <VSPEX-UCS-B>exitinterface Eth1/18channel-group 202 mode activeno shutdownexitcopy run startCisco Nexus 5548 B
config tinterface Po10description vPC Peer-Linkexitinterface Eth1/1-2channel-group 10 mode activeno shutdownexitinterface Po201description <VSPEX-UCS-B>exitinterface Eth1/17channel-group 201 mode activeno shutdownexitinterface Po202description <VSPEX-UCS-A>exitinterface Eth1/18channel-group 202 mode activeno shutdownexitcopy run startAdd Port Channel Configurations
These commands add prot channel configurations.
Cisco Nexus 5548 A
config tinterface Po10switchport mode trunkswitchport trunk native vlan <Native VLAN ID>switchport trunk allowed vlan <MGMT VLAN ID, CSV VLAN ID, LiveMigration VLAN ID, VMaccess VLAN ID, VEM VLAN ID>spanning-tree port type networkno shutdownexitinterface Po201switchport mode trunkswitchport trunk native vlan <MGMT VLAN ID>switchport trunk allowed vlan < MGMT VLAN ID, CSV VLAN ID, LiveMigration VLAN ID, VMaccess VLAN ID, VEM VLAN ID >spanning-tree port type edge trunkno shutexitinterface Po202switchport mode trunkswitchport trunk native vlan <MGMT VLAN ID>switchport trunk allowed vlan < MGMT VLAN ID, CSV VLAN ID, LiveMigration VLAN ID, VMaccess VLAN ID, VEM VLAN ID >spanning-tree port type edge trunkno shutexitcopy run startCisco Nexus 5548 B
config tinterface Po10switchport mode trunkswitchport trunk native vlan <Native VLAN ID>switchport trunk allowed vlan < MGMT VLAN ID, CSV VLAN ID, LiveMigration VLAN ID, VMaccess VLAN ID, VEM VLAN ID >spanning-tree port type networkno shutdownexitinterface Po201switchport mode trunkswitchport trunk native vlan <MGMT VLAN ID>switchport trunk allowed vlan MGMT VLAN ID, CSV VLAN ID, LiveMigration VLAN ID, VMaccess VLAN ID, VEM VLAN ID >spanning-tree port type edge trunkno shutexitInterface Po202switchport mode trunkswitchport trunk native vlan <MGMT VLAN ID>switchport trunk allowed vlan MGMT VLAN ID, CSV VLAN ID, LiveMigration VLAN ID, VMaccess VLAN ID, VEM VLAN ID >spanning-tree port type edge trunkno shutexicopy run startConfigure Virtual Port Channels
These commands configure virtual port channels (vPCs)
Cisco Nexus 5548 A
config tvpc domain <Nexus vPC domain ID>role priority 10peer-keepalive destination <Nexus B mgmt0 IP> source <Nexus A mgmt0 IP>exitinterface Po10vpc peer-linkexitinterface Po201vpc 201exitinterface Po202vpc 202exitcopy run startCisco Nexus 5548 B
config tvpc domain <Nexus vPC domain ID>role priority 20peer-keepalive destination <Nexus A mgmt0 IP> source <Nexus B mgmt0 IP>exitinterface Po10vpc peer-linkexitinterface Po201vpc 201exitinterface Po202vpc 202exitcopy run startConfigure Fibre Channel Ports
Nexus A and Nexus B
config tinterface fc1/29switchport trunk mode offno shutdownexitinterface fc1/30switchport trunk mode offno shutdownexitinterface fc1/31switchport trunk mode offno shutdownexitinterface fc1/32switchport trunk mode offno shutdownexitcopy run startLink Into Existing Network Infrastructure
Depending on the available network infrastructure, several methods and features can be used to uplink the private cloud environment. If an existing Cisco Nexus environment is present, Cisco recommends using vPCs to uplink the Cisco Nexus 5548 switches included in the private cloud environment into the infrastructure. The previously described procedures can be used to create an uplink vPC to the existing environment.
Initial Configuration of Cisco Unified Computing System
The following information provides a detailed procedure for the initial configuration of the Cisco UCS Manager. These steps should be followed precisely because a failure to do so could result in an improper configuration. You will need information captured on the customer configuration worksheets.
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.
Logging Into Cisco UCS Manager
These steps provide details for logging into the Cisco UCS environment:
1.
2.
3.
4.
5.
Create the VSPEX Environment with Cisco UCS PowerTool
Contained in the Sample PowerShell Scripts of this document are the following two files:
•
•
It is recommended that you review and validate these files before running. The script takes about 30 seconds to run to configure Cisco Unified Computing System according to the VSPEX validated design. This validation can save a significant amount of time.
Create the VSPEX Environment with Cisco UCS Manager
The following steps detail the basics for configuring the VSPEX environment by using the Cisco UCS Manager instead of using the UcsConfig.ps1 PowerShell script. It is assumed some basic knowledge of Cisco UCS Manager. For example, when creating VLANs, it shows the basic procedure to create a VLAN, but it does not step through creating every VLAN.
Synchronize Cisco UCS to NTP
These steps provide details for synchronizing the Cisco UCS environment to the NTP server:
1.
2.
3.
4.
5.
6.
Add a Block of IP Addresses for KVM Access
These steps provide details for creating a block of KVM IP addresses for server access in the Cisco UCS environment:
1.
2.
3.
4.
5.
6.
7.
The ext-mgmt pool is the default management pool. By default, IP addresses are assigned to the physical servers as they are recognized. It is also possible to create a separate pool and then assign it Service Profiles (Management IP Address) when they are assigned to a physical server. This is important if you plan on using SMI-S for management of the servers, as then the IP address follows the service profile instead of the physical server.
Edit the Chassis Discovery Policy
These steps provide details for modifying the chassis discovery policy as the base architecture includes two uplinks from each fabric extender installed in the Cisco UCS chassis:
1.
2.
3.
4.
5.
6.
7.
8.
9.
Create an Organization
The following steps provide details for configuring an organization in the Cisco UCS environment. Organizations are used as a means to organize and restrict access to various groups within the IT organization, thereby enabling multi-tenancy of the compute resources.
Note
From the New... menu at the top of the window, select Create Organization.
10.
11.
12.
13.
Enable Quality of Service in Cisco UCS Fabric
These steps provide details for enabling the quality of service in the Cisco UCS Fabric and setting Jumbo frames:
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
Create a Power Control Policy
These steps provide details for creating a Power Control Policy for the Cisco UCS environment:
1.
2.
3.
4.
5.
6.
7.
8.
Create a Scrub Policy
Scrub policies define what is erased when a service profile is disassociated from a server. If the disk field is set to Yes, when a service profile containing this scrub policy is disassociated from a server, all data on the server local drives is completely erased. If this field is set to No, the data on the local drives is preserved, including all local storage configuration.
1.
2.
3.
4.
5.
6.
7.
8.
Create Maintenance Policy
When a service profile is associated with a server, or when changes are made to a service profile that is already associated with a server, the server needs to be rebooted to complete the process. The Reboot Policy field of the maintenance policy determines when the reboot occurs for servers associated with any service profiles that include this maintenance policy.
1.
2.
3.
4.
5.
6.
7.
8.
9.
Create a Local Disk Configuration Policy
These steps provide details for creating a local disk configuration for the Cisco UCS environment, which is necessary if the servers in question do not have a local disk.
Note
1.
2.
3.
4.
5.
6.
7.
8.
Create a Server BIOS Policy
These steps provide details for creating a server BIOS policy for the Cisco UCS environment. It is recommended to have a BIOS policy available that disables quiet boot in order to assist in debugging boot issues.
1.
2.
3.
4.
5.
6.
7.
8.
Enable Fabric Interconnect Port Definitions
These steps provide details for enabling Fibre Channel, server, and uplinks ports:
1.
2.
3.
4.
5.
6.
7.
8.
Create Uplink Port Channels to the Cisco Nexus 5548 Switches
These steps provide details for configuring the necessary Port Channels out of the Cisco UCS environment:
1.
Note
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
Create vNIC Templates
This environment defines six vNIC templates. Depending upon the needs, more or less can be created. A sample creation is shown. It will need to be repeated for each vNIC template. Table 13 shows the values used for creating the vNIC templates in this CVD. The Native VLAN is needed on vNIC templates that will be accessed by the Hyper-V host. It is not selected for vNIC templates that will be accessed by the virtual machines.
Table 13 Values Used to Create the vNIC Template
To create vNIC templates, do the following:
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
Create vHBA Templates
To create vHBA templates, do the following:
1.
2.
Note
3.
4.
5.
6.
7.
8.
Create Boot Policies
Two boot policies need to be created. The first boot policy will be created to boot from Fabric A and the second to boot from Fabric B. Though not absolutely necessary to have two boot policies, having two options helps spread the load and helps ensure that a total failure does not happen if a disaster happens that removes an entire fabric.
For this sample, the following WWPN values are used for the VNX5400. Your ports may vary depending on the configuration of your VNX5400.
To create boot policies, do the following:
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
21.
22.
23.
24.
25.
26.
27.
28.
29.
30.
Create Service Profile Templates and Service Profiles
Two Service Profile Templates can now be created. One should be created to use the Fabric A boot policy and the other should be created with the Fabric B boot policy. Otherwise, all the other pool, template, and policy selections should be the same. Use the Create Service Profile (expert) option and select the pools, templates, and policies just created.
When the two Service Profile Templates have been created, create a Service Profile for each server. Assign half the service profiles to the first service profile template and the other half of the service profiles to the other service profile template. Use the Create Service Profiles From Template option.
Create EMC VNX5400 LUNs for VSPEX
The VSPEX cloud environment implements a boot from SAN environment using the concept of a Master Boot LUN. The Master Boot LUN is a storage area that will be used to maintain an image of a Windows Server 2012 R2 image to be used as a Clone source. This image should be configured as a base image to be used for subsequent installations, so all patching and custom configuration steps should be taken. For example, maybe a desired configuration setting is to ensure that all physical servers are able to be remotely managed. When the image is configured according to customer policy, the Microsoft sysprep utility can be run against this image to prepare it for use as a Clone. The steps to configure this Master Boot LUN image are in the following section.
Clones created from the Master Boot LUN will be presented to the physical servers defined by Service Profiles in the UCS environment. This style of deployment allows Service Profiles to be fully transportable between different physical blades as the boot device is external to the chassis, and also allows for multiple Master Boot images to be implemented providing support for different operating system versions or configurations which may need to be implemented over time.
Management of the boot LUN requires special consideration, and needs to ensure that the LUN ID provided to the LUN, as seen from the host is set to 0 (zero). The ESI (EMC Storage Integrator) PowerShell commands do not allow the manipulation of the LUN ID for devices presented to servers, and simply default to the sequential allocation of LUN IDs as implemented by the VNX array. As a result of this behavior, the boot LUN must be the first device that is mapped to the server (Cisco UCS service profile). If this is incorrectly implemented, then the wrong target will be selected for Windows boot operations on server power-up.
As described, the ESI PowerShell commands or Unisphere are utilized for provisioning of the LUNs required within the environment, and assume that the storage pool creation outlined in the previous section has been completed. For the procedure to set up a Master Boot LUN, a single LUN is created, and is used to install a Windows Server 2012 R2 instance. This server instance subsequently will be processed with Windows sysprep and be removed from the server. All compute nodes will then use a clone of the sysprep image to be customized as individual server instances.
Creation of all necessary LUNs within the Private Cloud environment can be executed with the PowerShell script ProcessStorageRequests.ps1 provided Appendix B. The defined XML configuration file is read by the PowerShell script. This XML configuration file contains five parameters. There are two classes that can be repeated multiple times. The XML class <luns> can be repeated multiple times to define multiple LUNs for a server. The <Server> class can be repeated to create multiple server records.
For the purpose of defining and creating the Master Boot LUN, it is recommended to create a unique XML configuration file that defines only this specific device. Later the format of the XML configuration file can be followed for creating multiple LUNs.
•
•
•
•
•
Here is a sample XML file illustrating the content for creating the Master Boot LUN. It will need to be modified to reflect the customer environment.
<StorageParams><Array>VNX5400</Array><UCSAddress>10.29.130.100</UCSAddress><Servers><Server><ServerName>VSPEX-01</ServerName><IPAddress>10.29.130.21</IPAddress><luns><label>Master_Boot_2012R2</label><pool>VSPEX_Pool_1</pool><size>50GB</size></luns></Server></Servers></StorageParams>In addition to the five parameters listed above that can be repeated, there are two other parameters that are defined only once. The <Array> parameter is the name of the VNX array. The <UCSAddress> parameter is the IP address for accessing the Cisco UCS management console. An example of the contents of a configuration is found in the Sample PowerShell Scripts section in a configuration file called Storage_Luns.xml. This configuration file is used by three different sample scripts.
•
•
•
Alternatively to using the provided PowerShell scripts, EMC Unisphere can be used for the purpose of creating LUNs for the boot from SAN deployment.
To create EMC VNX5400 LUNs for VSPEX, do the following:
1.
2.
3.
4.
5.
6.
7.
After creation of the required LUN, it is necessary to create a storage group containing the LUN and present the storage group to the Service Profile. The example PowerShell script found in the Sample PowerShell Scripts section, PrepMasterBoot_AddViaWWPN.ps1, utilizes both EMC Storage Integrator and the Cisco UCS PowerTool, and expects that both have been successfully installed. After presentation of the storage group to the WWPNs defined within the Service Profile, it will be possible to proceed with Windows Server installation.
An alternative to using ESI PowerShell would be to manually present storage using Unisphere as in the following steps:
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
21.
Configure Zoning on Cisco Nexus 5548 Switches
The following steps detail the procedure for configuring the Cisco UCS environment to boot the blade servers from the EMC VNX5400 SAN.
Gather Necessary Information
After the Cisco UCS service profiles have been created (earlier section), each infrastructure management blade has a unique configuration. To proceed with the deployment, specific information must be gathered from each Cisco UCS blade to enable SAN booting. Insert the required information in the WWNN/WWPN table for Hyper-V servers in the Customer Configuration Worksheets sections. Both WWNN and WWPN from the Cisco UCS service profiles are needed for masking the LUNs on the VNX5400 SAN.
To gather the information for the Cisco UCS servers, launch the Cisco UCS Manager GUI as follows:
1.
2.
3.
4.
5.
Create Device Aliases and Create Zone for First Server
These steps provide details for configuring device aliases for all devices on both Nexus A and Nexus B. It also creates a zone for the primary boot path for the first server that will be installed and used for creating a 'gold image' or Master Boot image. The initial zoning provides a single path to the SAN. If more than one path is defined to the boot volume, and there is no multipath software available, as is the case for an initial installation of Windows Server 2012 R2, data corruption can occur on the disk. After the operating system is installed and configured for MPIO, the secondary boot path can be defined. This configuration assumes the use of the default VSAN 1.
Cisco Nexus 5548 A
device-alias databasedevice-alias name <VSPEX-01-A> pwwn <VSPEX-01 Fabric-A WWPN>device-alias name <VNX5400-SPA-A0> pwwn <SPA-A0 WWPN>device-alias name <VNX5400-SPB-B0> pwwn <SPB-B0 WWPN>device-alias commitzone name <VSPEX-01> vsan 1member device-alias <VSPEX-01-A>member device-alias <VNX5400-SPA-A0>exitzoneset name <VSPEX> vsan 1member <VSPEX-01>exit.zoneset activate name <VSPEX> vsan 1The Nexus should respond with "Zoneset activation initiated. Check zone status."copy run startCisco Nexus 5548 B
Create the device-alias database on Nexus B at this time. Later in the process the zones and zoneset for Nexus B will be created will be created.
device-alias databasedevice-alias name <VSPEX-01-B> pwwn <VSPEX-01 Fabric-B WWPN>device-alias name <VNX5400-SPA-A1> pwwn <SPA-A1 WWPN>device-alias name <VNX5400-SPB-B1> pwwn <SPB-B1 WWPN>device-alias commitzoneset name <VSPEX> vsan 1exitcopy run startInstall Initial Microsoft Windows Server 2012 R2
The following steps provide the details necessary to prepare the host for the installation of Windows Server 2012 R2 Datacenter Edition. It assumes that the SAN has been zoned and the EMC V NX5400 has masked the LUN so only a single path to the server is available.
To speed the process of installing Windows Server 2012 R2 across all the physical hosts, a multiple step process is employed:
•
•
•
•
•
•
•
•
•
Note
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
21.
The installation will start.
22.
23.
24.
Depending upon the distribution you are using, you may or may not see this window. If you are using a Retail copy, you will see this window. If you are using a volume license copy, you will not see this window.
25.
26.
27.
28.
29.
30.
31.
32.
33.
34.
35.
36.
37.
38.
39.
40.
41.
42.
43.
44.
45.
46.
Sysprep the Initial Image
Before you run the sysprep utility against this newly created image, it is a good idea to tailor the image to specific customer needs. This includes adding and/or configuring software that will be common for all systems built from this image. In addition to the tasks listed here, the customer may have their own management software to install. Remember that not all software can be installed before an image is sysprepped, so check with the software vendor before installing.
At this point, if you have a DHCP server installed on your Management Network, the Management Network Interface should come up with an IP address. If you do not have DHCP, use the following steps to determine which Network Interface is on the Management VLAN and configure it with a static IP with connection to the outside world.
Initial Network Configuration
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 step 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.
1.
2.
Gwmi Win32_NetworkAdapter | Where {$_.MACaddress -ne $Null} | FT NetConnectionID, MACaddress
This returns a table of the network names and their associated MAC addresses.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
Common Configuration Tasks
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 via 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. The Sample PowerShell Scripts section contains a sample PowerShell script, Set-UcsHyperVRemoteMgmt.ps1, that sets a number of firewall rules to enable remote management, enables some services to automatically start, and enable remote desktop. Run this script from a PowerShell command window.
.NET Framework 3.5 Feature (optional)
Depending upon the management tools that are deployed in the customer environment, it might make sense to load the .NET Framework 3.5 feature. Doing it once on this image that will be sysprepped will save time in later deployments. This is not necessary in every data center.
Ensure the KVM has the Windows Server 2012 R2 installation media mounted. Assuming the Windows Server installation media is mounted on drive E:, issue the following PowerShell command to add the .NET Framework 3.5 feature.
Install-WindowsFeature -Name NET-Framework-Core -Source E:\sources\sxsRun Windows Update
It is highly recommended to fully patch the server at this time from Windows Update. Depending on the patches, it might be necessary to reboot and check for updates multiple times before the server is completely patched.
Install Windows Roles and Features
The Sample PowerShell Scripts section contains a sample PowerShell script, Add-UcsHyperVFeatures.ps1, which installs the MPIO and Failover Cluster features and the Hyper-V role. Run this script from a PowerShell command window. Installation of the Hyper-V role causes a reboot.
Configure Paging File
By default, Windows allocates and manages a portion of the system disk to be used as a paging file based on the amount of physical memory on a server. Since the workload running on Hyper-V servers really runs in the VMs, the majority of paging occurs within the VMs, minimizing the need for a large page file on the physical server. Therefore, it makes sense to minimize the size of the paging file of the Hyper-V host to minimize the amount of storage on the boot volume that is reserved for the paging file.
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
Note
Note
Configure MPIO
After the server has been configured with the MPIO feature, it is necessary to present the additional paths to the boot LUN and configure MPIO. The goal is to sysprep this operating system image and then clone the LUN for use by all other physical servers, this means MPIO has to be configured only once. Then, since the operating system image that will be used for booting the additional blades will already have MPIO configured, it is possible to configure paths through both Nexus switches for initial boot of the sysprepped image.
The Add-UcsHyperVFeatures.ps1 PowerShell script performed the installation and some configuration of Microsoft's MPIO. From an elevated command prompt issue the command mpclaim -s -d 0 to validate MPIO is configured on your system.
Next, prepare the Cisco Nexus 5548 switches with zones that reflect all paths to the boot LUN.
Cisco Nexus 5548 A
Remember that we had previously configured only a single path on Cisco Nexus 5548 A for the initial installation. Issue the following commands to create the secondary path.
zone name <VSPEX-01> vsan 1member device-alias <VNX5400-SPB-B0>exitzoneset activate name <VSPEX> vsan 1The Nexus should respond with "Zoneset activation initiated. Check zone status."
copy run startCisco Nexus 5548 B
zone name <VSPEX-01> vsan 1member device-alias <VSPEX-01-B>member device-alias <VNX5400-SPB-B1>member device-alias <VNX5400-SPA-A1>exitzoneset name <VSPEX> vsan 1member <VSPEX-01>exit.zoneset activate name <VSPEX> vsan 1The Nexus should respond with "Zoneset activation initiated. Check zone status."
copy run startTo help ensure you have configured WWN correctly issue the command:
Show zoneset activeNotice that an asterisk should appear at the beginning of each line indicating the wwn has been detected.
Present Boot LUN to Additional Paths
When the zones and zonesets have been updated to reflect the multiple paths to the LUN, it is necessary to configure the EMC VNX5400 SAN to present the boot LUN to the additional paths.
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
You should see four entries, similar to what is shown in this screen shot, validating that you have properly configured MPIO.
Run Sysprep
When the image is properly configured for multipath, Microsoft's sysprep utility can be used to create an image that can be used for cloning to quickly provision any additional physical hosts needed in the environment.
1.
Note
2.
3.
4.
5.
When the KVM console shows the physical server has shut down, clones can be made of the LUN for use by all the physical hosts.
Cloning the Sysprepped Image
Removal of the Source Master Image
After installation of the Windows Server instance and execution of the sysprep process, it is necessary to remove the source LUN from the Service Profile that was used to build the image. To remove the LUN from the Service Profile, use Unisphere to remove the Master_Boot LUN and the assigned host from its storage group. You may also want to remove the host initiator entries for the Master_Boot if you are using a different naming convention for production servers.
With the base sysprep image created and the LUN containing the sysprepped image removed from the service profile, clones can be taken in order to replicate the contents of the master LUN for other servers in the environment. Prior to copying the data, target devices need to be created to be associated with the planned clone sessions. The clones can be created with ESI or through Unisphere.
Create Target LUNs with ESI
Run the ProcessStorageRequests.ps1 script to create the appropriate clone target devices. This script uses the Storage_Luns.xml found in the Sample PowerShell Scripts. It must be modified to reflect the number of hosts for which boot LUNs will be created and the naming conventions used by the customer.
Create Target LUNs with Unisphere
Alternatively, EMC Unisphere can be used to create the target LUNs.
Create Clones with ESI
Now that the clone target LUNs are created, the clone process can be run. To automate the clone process, modify the ProcessClones.xml configuration file contents to reflect the customer environment. Run the ProcessClones.ps1 script found in Sample PowerShell Scripts which reads the XML configuration file using ESI and naviseccli.
The script will create concurrent clone copies and wait for 100% synchronization. When the copies are complete, the script will delete the clone relationship and the target LUNs can be used for deployment.
Create Clones with EMC Unisphere
Alternatively, the following process can be executed from Unisphere to create the clone relationships and copy the data from the master LUN to the boot target LUNs.
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
This completes the cloning process.
Note
Boot from Sysprepped LUNs
After a clone of the sysprepped LUN has been created for each physical server to be built, you need to zone and mask the LUN before completing a build from the sysprepped image presented.
Zone the Network
Presenting the LUNs to the various hosts is a combination of configuring the zones and zonesets on the Cisco Nexus 5548 switches and masking the LUNs through Unisphere or naviseccli. The detailed steps for this were shown previously, so they will be summarized here.
Zoning
•
•
•
Figure 18shows the end result of this step will provide a listing of the zoneset. (WWPN values will differ for each environment).
Figure 18 Example Zoneset for Cisco Nexus 5548 A
Mask Boot LUNs to Service Profiles
Following the cloning and zoning processes, the boot LUNs can be presented to their respective service profiles. The same XML configuration file used to create the boot LUNs can be used in conjunction with the PostClone_AddViaWWPN.ps1 script to present the boot LUNs to the servers. The script will also register the appropriate initiators with the storage array and create the necessary storage groups along with presenting the LUNs to the appropriate servers.
An alternative to using the script would be to use the Unisphere management GUI as outlined previously in the "Mask Boot LUN with EMC Unisphere" section. Following the masking operations, start each host and complete the mini-setup to tailor each node with things like name, IP addressing (if fixed IP addresses are used), and join to the domain.
Complete Image Builds from Sysprepped Images
When the sysprep image has been cloned and the LUNs are properly masked so the boot volumes only appear to the owning host, every server must complete its installation. Booting from a sysprep image runs what is referred to as a 'mini-setup'.
Note
1.
2.
3.
4.
5.
The association between the service profile and the blade should have taken effect when you created the service profile, so you should see the first screen of the Windows Server mini-setup. If it is still booting when you connect to it, you may see a series of progress messages display as the system completes the initial setup.
6.
7.
8.
9.
1.
•
•
•
•
2.
3.
At this point, you will have a complete base image. This means you will need to activate Windows, change the name of the system, join to the domain, configure your network settings, and complete any other tailoring required to meet your company requirements for Windows Server installation.
Configure Networks
It is recommended that you rename the network adapters from the Windows default values of "Local Area Connect #x" to reflect the actual network from the Cisco UCS Service Profile. You can use the manual procedure defined earlier in the document, or you can use the sample PowerShell script, Set-UcsHyperVAdapters.ps1, found in Sample PowerShell Scripts. This script requires that the machine domain-joined and the script is being run from a workstation that has the Cisco UCS PowerTool installed.
The Set-UcsHyperVAdapters.ps1 script will assign a fixed IP address to each NIC based on the a 192.168.xx.yy notation where xx is the VLAN read in from Cisco UCS and yy is a specific value assigned so that the last octet of each address is the same on for each server. It also sets each adapter, except the excluded (generally the management) adapter so that it does not register itself in DNS. It is best to have only the primary (management) address register in DNS.
Depending upon your configuration, you might have DHCP set up for every network. In which case, it is not recommended to use this script without first modifying it to not alter IP addresses.
Configure Hyper-V Virtual Switches
To configure Hyper-V virtual switches, do the following:
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
When completed, your Network Connections will like the screenshot below. (Device names will vary)
Network interfaces that have been defined as virtual switches will show Enabled in the Status column.
The two interfaces that were teamed for LiveMigration also show as Enabled.
The Unidentified network entries are networks that are 'private' networks, i.e. not used for accessing the outside network.
For most configurations, you will see only the Mgmt network with internet access.
Unconfigure DNS Registration
If you do not use the Set-UcsHyperVAdapters.ps1 script to rename and partially configure the NICs, it is a good practice to remove all but the management NIC from DNS registration.
1.
2.
3.
4.
5.
6.
Binding Order
It is a good practice to have a proper binding order of NICs.
7.
8.
9.
10.
11.
Install EMC PowerPath
As a part of tailoring each system, EMC PowerPath can be installed for enhanced multi-pathing functionality EMC PowerPath for Windows version 5.7 or higher should be used.
1.
2.
3.
4.
5.
6.
Note
7.
8.
9.
Install EMC Unisphere Host Agent
The Unisphere Host Agent allows for host specific information to be sent to management applications, like Unisphere, for ease of administration. LUN mapping and Operating System information as well as initiator information can be forwarded from a server to the VNX via the agent. Follow the procedure below to install the Unisphere Host Agent on either a physical Windows Server 2012 R2 server or Virtual Machine.
Note
10.
New-NetFirewallRule -Name UniAgent-TCP -DisplayName UniAgent-TCP -Action Allow -Direction Inbound -Protocol TCP -LocalPort 6389
11.
12.
13.
14.
15.
16.
17.
18.
19.
net start "Navisphere Agent"
20.
Create Hyper-V Failover Cluster
When you have completed the build of the servers to SAN boot in a multipath IO environment, have all the network adapters configured the same, and the hosts joined to the Active Directory domain, you will create the failover cluster on which all the virtual machines will be deployed. This cluster can be expanded up to a total of 64 hosts for running VMs within the Microsoft virtualized environment.
Create Shared Storage
Microsoft Failover Clusters use shared storage for storing the VMs. For a 300 VM deployment, 3 storage pools are created with 45 SAS drives and 2 EFDs in two pools and 20 SAS drives and 2 EFDs in the third pool. Two 7TB LUNs will be provisioned from each 45 drive pool and two 3TB LUNs will be provisioned from the 20 drive pool. A small LUN of 1 GB in size must be created on any of the 3 pools to act as the witness disk in the cluster. There will be 7 LUNs created in total.
•
•
•
•
•
•
•
When these LUNs are created, they need to be added to each of the storage groups associated with each node in the Hyper-V cluster. When the same LUN is added to multiple storage groups, the VNX will display an error message cautioning about the possibility of corrupting data. The clustering software controls access to the LUNs, so that is acceptable.
It is recommended that at least one CSV is created for each node in the cluster. A new feature of Windows Server 2012 R2 is to distribute the CSV ownership across the cluster nodes to ensure that management functions are not concentrated on any single node. However, to speed the time it takes to run the Cluster Validation Wizard, you should not present these volumes to the cluster until after the cluster is formed. The Cluster Validation Wizard will create multiple combinations of failover scenarios to be tested. The more disks in the test, the longer it takes to complete the validation. Since the storage array will be tested with the initial two disks, subsequent disks can be added later with the knowledge that the initial disks were configured correctly.
You may also want to create larger or smaller LUNs depending upon the practices in place in the customer environment. The VSPEX reference VM allocates 100 GB per VM, though a typical boot VM is only 50 GB. During normal operations, Hyper-V reserves enough space on disk to capture the memory of the running VM in case of certain types of failures. This space is in addition to the space assigned to the virtual hard drive files. To run 300 VMs on the six nodes of a cluster assumes that 60 reference VMs will run on each of five nodes, with a single node for backup when one of the other nodes needs to be taken out of service. In order for a single CSV to contain all 60 VMs, it is recommended to create the CSV to be 7 TB to allow for a little overage.
Before you can test and form the cluster, it is necessary to format the shared LUNs as NTFS volumes. Perform the following steps on only one node of the cluster to format the drives.
1.
(Alternatively, type compmgmt.msc into a command or PowerShell window.)
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
Note
12.
13.
14.
15.
16.
17.
18.
19.
Before running the Cluster Validation Wizard, it is a good practice to bring the disks online and offline on the other node(s) of the cluster. The Cluster Validation Wizard will do this, too, but checking beforehand will save the time it takes to run the wizard if you need to do some troubleshooting.
Run Cluster Validation Wizard
1.
Test-Cluster F3-Infra01,F3-Infra02
It is not uncommon to have errors or warnings. The first run in the screen shot shows a message of HadFailures. Failures must be fixed before creating the cluster.
The second run shows a test run with no failures, but there were some warnings. Upon investigation, it was determined that the warnings were expected and the cluster can be created.
The last line in yellow gives the location of the report file detailing the test results.
Create Cluster
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
If you are running from one of the nodes, the Failover Cluster Manager will show the cluster. If you are running from the workstation, you will need to use the option to Connect to Cluster and enter the cluster name.
14.
15.
16.
17.
18.
19.
20.
21.
Note
22.
Note
23.
24.
25.
26.
27.
28.
29.
30.
An alternate method to rename the generic network names and assign the proper function to each is to use a PowerShell script with these commands (modified for your environment).
(Get-ClusterNetwork -Cluster VSPEX-Clus01 | ? {$_.Address -like "10.29.130.*" }).Name = "Mgmt"(Get-ClusterNetwork -Cluster VSPEX-Clus01 | ? {$_.Address -like "192.168.12.*" }).Name = "CSV"(Get-ClusterNetwork -Cluster VSPEX-Clus01 | ? {$_.Address -like "192.168.11.*" }).Name = "LiveMigration"(Get-ClusterNetwork -Cluster VSPEX-Clus01 -Name Mgmt).Role = 3(Get-ClusterNetwork -Cluster VSPEX-Clus01 -Name CSV).Role = 1(Get-ClusterNetwork -Cluster VSPEX-Clus01 -Name LiveMigration).Role = 0The cluster is complete.
By default, Hyper-V will store the virtual hard drives for created virtual machines on the system drive. It is easy to set up Hyper-V to default to the Cluster Shared Volumes for storage. This is not an absolute requirement, but it does make management easier. A good practice is to have the same number of Cluster Shared Volumes as you have nodes in the Hyper-V cluster. Each node in the cluster would have a default storage location of one of the Cluster Shared Volumes.
1.
2.
3.
4.
5.
6.
Sample PowerShell Scripts
These sample PowerShell scripts and input files are provided as examples to assist in in the rapid deployment of this VSPEX environment. They should be reviewed for compliance with customer policies and naming conventions. They were tested within the lab environment where this system was configured. Security in your environment may not allow these scripts to run in your environment. No warranty or support is implied by their inclusion within this document. They were included to provide you with a starting point if you want to automate some steps.
Cisco Scripts
UcsConfig.ps1
<#UcsConfig Version=0.14-September-2013Created by Tim Cerlingtcerling@cisco.comExecution string: .\UcsConfig.ps1 -path <path> -validateOnly -toConsole<path> - location of input file UcsConfig.xml-validateOnly - only validate contents of UcsConfig.xml. Does not update UCS-toConsole - output log file to console instead of log file/#>Param([Parameter(Mandatory=$false,Position=0)][String]$path = (Get-Location),[Parameter(Mandatory=$false)][Switch]$validateOnly = $false,[Parameter(Mandatory=$false)][Switch]$toConsole = $false)## Function Definitions## ------------------------------------------------------------------------------# Function to write log information to either log file or consoleFunction Write-Log ($content, $type){$n = (get-pscallstack).Length - 2$lineNum = ((get-pscallstack)[$n].Location -split " line ")[1]switch ($type){Normal{If ($ToConsole){Write-Host -ForegroundColor Green "$lineNum $(Get-Date -Format "HH:mm:ss") - $content"}Else{Add-Content -Path $logFilePath -Value "$lineNum - $(Get-Date -Format g): $content"}}Error{If ($ToConsole){Write-Host -ForegroundColor Red -BackgroundColor Black "ERROR at line $lineNum `n$content"}Else{Add-Content -Path $logFilePath -Value "ERROR at line $lineNum - $(Get-Date -Format g): $content"}}}}## Regular expressions used for validation## ------------------------------------------------------------------------------$validIPAddress = @"^([1-9]|[1-9][0-9]|1[0-9][0-9]|2[0-4][0-9]|25[0-5])(\.([0-9]|[1-9][0-9]|1[0-9][0-9]| 2[0-4][0-9]|25[0-5])){3}$"@$validHex = @"^([A-Fa-f0-9]{2})"@$validMAC = @"^([0-9A-Fa-f]){2}(\:([0-9A-Fa-f]){2}){5}$"@$validWWN = @"^([0-9A-Fa-f]){2}(\:([0-9A-Fa-f]){2}){7}$"@$validUUID = @"^([A-Fa-f0-9]){4}(\-([A-Fa-f0-9]){12})"@$validSuffix = @"^([A-Fa-f0-9:]{5})"@$validNumList = @"^([0-9,-])"@$validDigit = @"^([0-9])"@## Definition of constants## ------------------------------------------------------------------------------$startTime = Get-Date$originalPath = Get-Location$errTag = $False$logFile = "UcsConfig.log"$chassisDiscoveryOptions = @() #Table of chassis discovery options$chassisDiscoveryOptions +=, ("1-link")$chassisDiscoveryOptions +=, ("2-link")$chassisDiscoveryOptions +=, ("4-link")$chassisDiscoveryOptions +=, ("8-link")$chassisDiscoveryOptions +=, ("platform-max")$diskPolicyOptions = @() #Table of local disk policy options$diskPolicyOptions +=, ('any-configuration')$diskPolicyOptions +=, ('no-local-storage')$diskPolicyOptions +=, ('no-raid')$diskPolicyOptions +=, ('raid-striped')$diskPolicyOptions +=, ('raid-mirrored')$diskPolicyOptions +=, ('raid-mirrored-striped')$diskPolicyOptions +=, ('raid-striped-parity')$diskPolicyOptions +=, ('raid-striped-dual-parity')$fiPortRoles = @() #Table of server roles for FI port configuration$fiPortRoles +=, ('server')$fiPortRoles +=, ('uplink')$fiPortRoles +=, ('appliance')$fiPortRoles +=, ('fcoe')$fiPortRoles +=, ('')$poolType = @() #Table of types of pools$poolType +=, ('MAC')$poolType +=, ('UUID')$poolType +=, ('WWNN')$poolType +=, ('WWPN')$objectTable = @() #Table of found objects in ucsConfig.xml file$objectTable +=, ('TimeZone', 0)$objectTable +=, ('NTP', 0)$objectTable +=, ('MgmtIP', 0)$objectTable +=, ('CallHome', 0)$objectTable +=, ('ChassisDiscovery', 0)$objectTable +=, ('SubOrg', 0)$objectTable +=, ('SANWWPN.SPAprimary', 0)$objectTable +=, ('SANWWPN.SPAsecondary', 0)$objectTable +=, ('SANWWPN.SPBprimary', 0)$objectTable +=, ('SANWWPN.SPBsecondary', 0)$objectTable +=, ('QoS', 0)$objectTable +=, ('PowerPolicy', 0)$objectTable +=, ('ScrubPolicy', 0)$objectTable +=, ('MaintenancePolicy', 0)$objectTable +=, ('DiskPolicy', 0)$objectTable +=, ('BIOSPolicy', 0)$objectTable +=, ('PlacementPolicy', 0)$objectTable +=, ('FI', 0)$objectTable +=, ('FCslot1', 0)$objectTable +=, ('FCslot2', 0)$objectTable +=, ('PC', 0)$objectTable +=, ('Pools', 0)$objectTable +=, ('VLANs', 0)$objectTable +=, ('VNICtemplate', 0)$objectTable +=, ('VHBAtemplate', 0)$objectTable +=, ('BootPolicy', 0)$objectTable +=, ('SPTemplate', 0)$objectTable +=, ('ServiceProfile', 0)################################################################################################################################################################## Start of Code## ------------------------------------------------------------------------------# Change to path entered on command lineIf (Test-Path $path -PathType Container){Set-Location $path}Else{$errTag = $TrueWrite-Host "Invalid path" -ForegroundColor Red}# Read input fileIf (Test-Path "$path\ucsconfig.xml"){try {$ucsConfig = [XML] (Get-Content "$path\UcsConfig.xml") }catch {$errTag = $True; Write-Host "Invalid UcsConfig.xml" -ForegroundColor Red}}Else{$errTag = $TrueWrite-Host "Missing UcsConfig.xml" -ForegroundColor Red}# Create a log file in the same directory from which the script is runningIf (!$errTag){If (!$toConsole){$localPath = Split-Path (Resolve-Path $MyInvocation.MyCommand.Path)$logFilePath = Join-Path $localPath $logFileIf (Test-Path($logFilePath)){Write-Host "Deleting existing log file"Remove-Item $logFilePath}Write-Host "Creating new log file $logfilePath"$trash = New-Item -Path $localPath -Name $logFile -ItemType "file"}}# Import required modulesif ((Get-Module |where {$_.Name -ilike "CiscoUcsPS"}).Name -ine "CiscoUcsPS"){Write-Host "Loading Module: Cisco UCS PowerTool Module"Import-Module CiscoUcsPs}$trash = set-ucspowertoolconfiguration -supportmultipledefaultucs $false# Test whether to continue processingIf ($errTag){Set-Location $originalPath$endTime = Get-Date$elapsedTime = New-TimeSpan $startTime $endTimeWrite-Host -ForegroundColor Yellow -BackgroundColor Black "`n`n-----------------------------------------------------------`n"Write-Log "Elapsed time: $($elapsedTime.Hours):$($elapsedTime.Minutes):$($elapsedTime.Seconds)"Write-Log "End of processing.`n"Exit}################################################################################################################################################################# ------------------------------------------------------------------------------## Start validating the UcsConfig.xml file## ------------------------------------------------------------------------------################################################################################$error.Clear()Write-Log "Validating contents of $path\UcsConfig.xml"# Validate UCSM IP address$tmp1 = $ucsConfig.VSPEX.UCSMIP.trim()$tmp = Test-Connection $tmp1 -Count 1 -QuietIf ($tmp){Write-Log "UCSM IP address $tmp1 is reachable." "Normal"}Else{Write-Log "UCSM IP address $tmp1 is unreachable." "Error"$errTag = $True}# Validate Management IP settings$ucsConfig.VSPEX.MgmtIP | ForEach-Object {$_.Pool} | ForEach-Object {$tmp1 = $_If ($tmp1 -ne $null){For ($i=0; $i -lt $objectTable.length; $i++){$obj = $objectTable[$i]If ($obj[0] -eq 'MgmtIP') {$obj[1] = 1; Break}}$tmp2 = $_.Name.trim()$tmp1 | ForEach-Object {$tmp = $False$tmp3 = $_.Order.trim()$tmp4 = $_.Start.trim()$tmp5 = $_.End.trim()$tmp6 = $_.Gateway.trim()$tmp7 = $_.PrimaryDNS.trim()$tmp8 = $_.SecondaryDNS.trim()If (!($tmp3 -eq 'default' -or $tmp3 -eq 'sequential')){Write-Log "Invalid management pool assignment order - Name=$tmp2 Start=$tmp3" "Error"$tmp = $True}If (!($tmp4 -match $validIPaddress)){Write-Log "Invalid management pool start IP address - Name=$tmp2 Start=$tmp4" "Error"$tmp = $True}If (!($tmp5 -match $validIPaddress)){Write-Log "Invalid management pool end IP address - Name=$tmp2 Start=$tmp5" "Error"$tmp = $True}If ($tmp4 -ge $tmp5){Write-Log "Management pool end IP address must be greater than start - Name=$tmp2 Start=$tmp4 End=$tmp5" "Error"$tmp = $True}If (!($tmp6 -match $validIPaddress)){Write-Log "Invalid management pool gateway IP address - Name=$tmp2 Start=$tmp6" "Error"$tmp = $True}If ($tmp7 -ne '0.0.0.0'){If (!($tmp7 -match $validIPaddress)){Write-Log "Invalid management pool primary DNS IP address - Name=$tmp2 Primary=$tmp7" "Error"$tmp = $True}}If ($tmp8 -ne '0.0.0.0'){If (!($tmp8 -match $validIPaddress)){Write-Log "Invalid management pool secondary DNS IP address - Name=$tmp2 Secondary=$tmp8" "Error"$tmp = $True}}If (!$tmp){Write-Log "Management IP pool - Name=$tmp2 Order=$tmp3 Start=$tmp4 End=$tmp5 G/W=$tmp6 Primary=$tmp7 Secondary=$tmp8" "Normal"}Else{Write-Log "Invalid management IP pool - Name=$tmp2 Order=$tmp3 Start=$tmp4 End=$tmp5 G/W=$tmp6 Primary=$tmp7 Secondary=$tmp8" "Error"$errTag = $True}}}}# Validate Chassis discovery setting$tmp1 = $ucsConfig.VSPEX.ChassisDiscoveryIf ($tmp1 -ne $null){For ($i=0; $i -lt $objectTable.length; $i++){$obj = $objectTable[$i]If ($obj[0] -eq 'ChassisDiscovery') {$obj[1] = 1; Break}}$tmp1 = $tmp1.trim()For ($i=0; $i -lt $chassisDiscoveryOptions.length; $i++){If ($tmp1 -eq $chassisDiscoveryOptions[$i]){Write-Log "Valid chassis discovery - $tmp1" "Normal"Break}}If ($i -eq $chassisDiscoveryOptions.length){Write-Log "Invalid chassis discovery option - $tmp1" "Error"$errTag = $True}}# Validate SAN WWPN values$tmp1 = $ucsConfig.VSPEX.SANWWPN.SPAprimaryIf ($tmp1 -ne $null){For ($i=0; $i -lt $objectTable.length; $i++){$obj = $objectTable[$i]If ($obj[0] -eq 'SANWWPN.SPAprimary') {$obj[1] = 1; Break}}$tmp1 = $tmp1.trim()If ($tmp1 -match $validWWN){Write-Log "Valid Port-A Primary WWPN - $tmp1" "Normal"$sanSPAprimary = $tmp1}Else{Write-Log "Invalid Port-A Primary WWPN - $tmp1" "Error"$errTag = $True}}$tmp1 = $ucsConfig.VSPEX.SANWWPN.SPAsecondaryIf ($tmp1 -ne $null){For ($i=0; $i -lt $objectTable.length; $i++){$obj = $objectTable[$i]If ($obj[0] -eq 'SANWWPN.SPAsecondary') {$obj[1] = 1; Break}}$tmp1 = $tmp1.trim()If ($tmp1 -match $validWWN){Write-Log "Valid Port-A Secondary WWPN - $tmp1" "Normal"$sanSPAsecondary = $tmp1}Else{Write-Log "Invalid Port-A Secondary WWPN - $tmp1" "Error"$errTag = $True}}$tmp1 = $ucsConfig.VSPEX.SANWWPN.SPBprimaryIf ($tmp1 -ne $null){For ($i=0; $i -lt $objectTable.length; $i++){$obj = $objectTable[$i]If ($obj[0] -eq 'SANWWPN.SPBprimary') {$obj[1] = 1; Break}}$tmp1 = $tmp1.trim()If ($tmp1 -match $validWWN){Write-Log "Valid Port-B Primary WWPN - $tmp1" "Normal"$sanSPBprimary = $tmp1}Else{Write-Log "Invalid Port-B Primary WWPN - $tmp1" "Error"$errTag = $True}}$tmp1 = $ucsConfig.VSPEX.SANWWPN.SPBsecondaryIf ($tmp1 -ne $null){For ($i=0; $i -lt $objectTable.length; $i++){$obj = $objectTable[$i]If ($obj[0] -eq 'SANWWPN.SPBsecondary') {$obj[1] = 1; Break}}$tmp1 = $tmp1.trim()If ($tmp1 -match $validWWN){Write-Log "Valid Port-B Secondary WWPN - $tmp1" "Normal"$sanSPBsecondary = $tmp1}Else{Write-Log "Invalid Port-B Secondary WWPN - $tmp1" "Error"$errTag = $True}}# Validate Power Control Policies$tmp1 = $ucsConfig.VSPEX.PowerPolicyIf ($tmp1 -ne $null){For ($i=0; $i -lt $objectTable.length; $i++){$obj = $objectTable[$i]If ($obj[0] -eq 'PowerPolicy') {$obj[1] = 1; Break}}$ucsConfig.VSPEX.PowerPolicy | ForEach-Object {$_.Var} | ForEach-Object {$tmp1 = $_.Name.trim()$tmp2 = $_.Priority.trim()$tmp3 = $_.Priority.trim()If ($tmp3 -eq 'no-cap'){Write-Log "Valid Power Control Policy on entry - Name=$tmp1 Priority=$tmp3" "Normal"}Else{If ([int]$tmp2 -ge 1 -and [int]$tmp2 -le 10){Write-Log "Valid Power Control Policy on entry - Name=$tmp1 Priority=$tmp2" "Normal"}Else{Write-Log "Invalid Power Control Policy on entry - Name=$tmp1 Priority=$tmp3" "Error"$errTag = $True}}}}# Validate Scrub Policies$tmp1 = $ucsConfig.VSPEX.ScrubPolicyIf ($tmp1 -ne $null){For ($i=0; $i -lt $objectTable.length; $i++){$obj = $objectTable[$i]If ($obj[0] -eq 'ScrubPolicy') {$obj[1] = 1; Break}}$ucsConfig.VSPEX.ScrubPolicy | ForEach-Object {$_.Var} | ForEach-Object {$tmp1 = $_.Name.trim()$tmp2 = $_.Descr$tmp3 = $_.DiskScrub.trim()$tmp3 = $tmp3.tolower()$tmp4 = $_.BiosScrub.trim()$tmp4 = $tmp4.tolower()If (($tmp3 -eq 'yes' -or $tmp3 -eq 'no') -and ($tmp4 -eq 'yes' -or $tmp4 -eq 'no')){Write-Log "Valid Scrub Policy on entry - Name=$tmp1 Descr=$tmp2 Disk=$tmp3 Bios=$tmp4" "Normal"}Else{Write-Log "Invalid Scrub Policy on entry - Name=$tmp1 Descr=$tmp2 Disk=$tmp3 Bios=$tmp4" "Error"$errTag = $True}}}# Validate Maintenance Policies$tmp1 = $ucsConfig.VSPEX.MaintenancePolicyIf ($tmp1 -ne $null){For ($i=0; $i -lt $objectTable.length; $i++){$obj = $objectTable[$i]If ($obj[0] -eq 'MaintenancePolicy') {$obj[1] = 1; Break}}$ucsConfig.VSPEX.MaintenancePolicy | ForEach-Object {$_.Var} | ForEach-Object {$tmp1 = $_.Name.trim()$tmp2 = $_.Descr.trim()$tmp3 = $_.Policy.trim()$tmp3 = $tmp3.tolower()If ($tmp3 -eq 'immediate' -or $tmp3 -eq 'timer-automatic' -or $tmp3 -eq 'user-ack'){Write-Log "Valid Maintenance Policy on entry - Name=$tmp1 Descr=$tmp2 Policy=$tmp3" "Normal"}Else{Write-Log "Invalid Maintenance Policy on entry - Name=$tmp1 Descr=$tmp2 Policy=$tmp3" "Error"$errTag = $True}}}# Validate Local Disk Policies$tmp1 = $ucsConfig.VSPEX.DiskPolicyIf ($tmp1 -ne $null){For ($i=0; $i -lt $objectTable.length; $i++){$obj = $objectTable[$i]If ($obj[0] -eq 'DiskPolicy') {$obj[1] = 1; Break}}$ucsConfig.VSPEX.DiskPolicy | ForEach-Object {$_.Var} | ForEach-Object {$tmp1 = $_.Name.trim()$tmp2 = $_.Mode.trim()$tmp3 = $_.Protect.trim()For ($i=0; $i -lt $diskPolicyOptions.length; $i++){If (($tmp2 -eq $diskPolicyOptions[$i]) -and ($tmp3 -eq 'yes' -or $tmp3 -eq 'no')){Write-Log "Valid local disk policy - Name=$tmp1 Mode=$tmp2 Protect=$tmp3" "Normal"Break}}If ($i -eq $diskPolicyOptions.Length){Write-Log "Invalid local disk policy - Name=$tmp1 Mode=$tmp2 Protect=$tmp3" "Error"$errTag = $True}}}# Validate FI port definitions - NOTE: this section does not handle FC ports.$tmp1 = $ucsConfig.VSPEX.FI.VarIf ($tmp1 -ne $null){For ($i=0; $i -lt $objectTable.length; $i++){$obj = $objectTable[$i]If ($obj[0] -eq 'FI') {$obj[1] = 1; Break}}$ucsConfig.VSPEX.FI | ForEach-Object {$_.Var} | ForEach-Object {$tmp1 = $_.SlotID.trim()$tmp2 = $_.PortID.trim()$tmp3 = $_.Role.trim()If ($tmp1 -eq '1'){For ($i=0; $i -lt $fiPortRoles.length; $i++){If (([int]$tmp2 -ge 1 -and [int]$tmp2 -le 32) -and ($tmp3 -eq $fiPortRoles[$i])){If ($tmp3 -ne ''){Write-Log "Valid FI port role definition - SlotID=$tmp1 PortID=$tmp2 Role=$tmp3" "Normal"}Break}}If ($i -eq $fiPortRoles.length){Write-Log "Invalid FI port role definition - SlotID=$tmp1 PortID=$tmp2 Role=$tmp3" "Error"$errTag = $True}}If ($tmp1 -eq '2'){For ($i=0; $i -lt $fiPortRoles.length; $i++){If (([int]$tmp2 -ge 1 -and [int]$tmp2 -le 16) -and ($tmp3 -eq $fiPortRoles[$i])){If ($tmp3 -ne ''){Write-Log "Valid FI port role definition - SlotID=$tmp1 PortID=$tmp2 Role=$tmp3" "Normal"}Break}}If ($i -eq $fiPortRoles.length){Write-Log "Invalid FI port role definition - SlotID=$tmp1 PortID=$tmp2 Role=$tmp3" "Error"$errTag = $True}}If ($tmp1 -ne '1' -and $tmp1 -ne '2'){Write-Log "Invalid Slot number - $tmp1" "Error"$errTag = $true}}}# Validate FC port definitions - NOTE: this section handles FC ports.$tmp1 = $ucsConfig.VSPEX.FCslot1.PortIDIf ($tmp1 -ne $null){For ($i=0; $i -lt $objectTable.length; $i++){$obj = $objectTable[$i]If ($obj[0] -eq 'FCslot1') {$obj[1] = 1; Break}}$tmp1 = $tmp1.trim()If ($tmp1 -ne ''){If (($tmp1 % 2 -eq 0) -or ($tmp1 -ge 32)){Write-Log "Invalid Fixed Module FC Port - must not be an even integer or > 31 - $tmp1" "Error"$errTag = $true}Else{Write-Log "Valid Fixed Module FC port starting at - Port=$tmp1" "Normal"}}}$tmp1 = $ucsConfig.VSPEX.FCslot2.PortIDIf ($tmp1 -ne $null){For ($i=0; $i -lt $objectTable.length; $i++){$obj = $objectTable[$i]If ($obj[0] -eq 'FCslot2') {$obj[1] = 1; Break}}$tmp1 = $tmp1.trim()If ($tmp1 -ne ''){If (($tmp1 % 2 -eq 0) -or ($tmp1 -ge 16)){Write-Log "Invalid Expansion Module FC Port - must not be an even integer or > 15 - $tmp1" "Error"$errTag = $true}Else{Write-Log "Valid Expansion Module FC port starting at - Port=$tmp1" "Normal"}}}# Validate Port Channel configuration$tmp = $False$tmp1 = $ucsConfig.VSPEX.PC.AName$tmp2 = $ucsConfig.VSPEX.PC.BName$tmp3 = $ucsConfig.VSPEX.PC.APortID$tmp4 = $ucsConfig.VSPEX.PC.BPortID$tmp5 = $ucsConfig.VSPEX.PC.Slot$tmp6 = $ucsConfig.VSPEX.PC.Port1$tmp7 = $ucsConfig.VSPEX.PC.Port2If ($tmp1 -ne $null -and $tmp2 -ne $null){For ($i=0; $i -lt $objectTable.length; $i++){$obj = $objectTable[$i]If ($obj[0] -eq 'PC') {$obj[1] = 1; Break}}$tmp1 = $tmp1.trim()$tmp2 = $tmp2.trim()$tmp3 = $tmp3.trim()$tmp4 = $tmp4.trim()$tmp5 = $tmp5.trim()$tmp6 = $tmp6.trim()$tmp7 = $tmp7.trim()If ($tmp1 -eq $tmp2){Write-Log "Port Channel names must be different on each fabric - A-Name=$tmp1 B-Name=$tmp2" "Error"$tmp = $True}If ($tmp3 -eq $tmp4){Write-Log "Port Channel PortID must be different on each fabric - A-PortID=$tmp3 B-PortID$tmp4" "Error"$tmp = $True}If ($tmp5 -ne '1' -and $tmp5 -ne '2'){Write-Log "Port Channel Slot must be '1' or '2' - SlitID=$tmp5" "Error"$tmp = $True}Else{Switch ($tmp5){1{If (([int]$tmp6 -lt 1 -or [int]$tmp6 -gt 32) -or ([int]$tmp7 -lt 1 -or [int]$tmp7 -gt 32) -or ($tmp6 -eq $tmp7)){Write-Log "Invalid port number for Slot 1 - Port1=$tmp6 Port2=$tmp7" "Error"$tmp = $True}}2{If (([int]$tmp6 -lt 1 -or [int]$tmp6 -gt 16) -or ([int]$tmp7 -lt 1 -or [int]$tmp7 -gt 16) -or ($tmp6 -eq $tmp7)){Write-Log "Invalid port number for Slot 2 - Port1=$tmp6 Port2=$tmp7" "Error"$tmp = $True}}}}}If (!$tmp){Write-Log "Fabric A VPC - A-Name=$tmp1 A-PortID=$tmp3 Slot=$tmp5 Port1=$tmp6 Port2=$tmp7" "Normal"Write-Log "Fabric B VPC - B-Name=$tmp2 B-PortID=$tmp4 Slot=$tmp5 Port1=$tmp6 Port2=$tmp7" "Normal"}Else{Write-Log "Invalid fabric A VPC - A-Name=$tmp1 A-PortID=$tmp3 Slot=$tmp5 Port1=$tmp6 Port2=$tmp7" "Normal"Write-Log "Invalid fabric B VPC - B-Name=$tmp2 B-PortID=$tmp4 Slot=$tmp5 Port1=$tmp6 Port2=$tmp7" "Normal"$errTag = $True}# Validate the various types of pools$tmp1 = $ucsConfig.VSPEX.PoolsIf ($tmp1 -ne $null){For ($i=0; $i -lt $objectTable.length; $i++){$obj = $objectTable[$i]If ($obj[0] -eq 'Pools') {$obj[1] = 1; Break}}$ucsConfig.VSPEX.Pools | ForEach-Object {$_.Var} | ForEach-Object {$tmp1 = $_.Type.trim()$tmp2 = $_.Name.trim()$tmp3 = $_.From.trim()$tmp4 = $_.To.trim()If ($tmp2 -eq 'default') {$tmp2 = $tmp2.tolower()}For ($i=0; $i -lt $poolType.length; $i++){If ($tmp1 -eq $poolType[$i]){Switch ($tmp1){MAC{If (($tmp3 -match $validMAC -and $tmp4 -match $validMAC) -and ($tmp3 -lt $tmp4)){Write-Log "Valid MAC pool - Name=$tmp2 From=$tmp3 To=$tmp4" "Normal"}Else{Write-Log "Invalid MAC pool - Name=$tmp2 From=$tmp3 To=$tmp4" "Error"$errTag = $True}}UUID{If (($tmp3 -match $validUUID -and $tmp4 -match $validUUID) -and ($tmp3 -lt $tmp4)){Write-Log "Valid UUID pool - Name=$tmp2 From=$tmp3 To=$tmp4" "Normal"}Else{Write-Log "Invalid UUID pool - Name=$tmp2 From=$tmp3 To=$tmp4" "Error"$errTag = $True}}WWNN{If (($tmp3 -match $validWWN -and $tmp4 -match $validWWN) -and ($tmp3 -lt $tmp4)){Write-Log "Valid WWNN pool - Name=$tmp2 From=$tmp3 To=$tmp4" "Normal"}Else{Write-Log "Invalid WWNN pool - Name=$tmp2 From=$tmp3 To=$tmp4" "Error"$errTag = $True}}WWPN{If (($tmp3 -match $validWWPN -and $tmp4 -match $validWWPN) -and ($tmp3 -lt $tmp4)){Write-Log "Valid WWPN pool - Name=$tmp2 From=$tmp3 To=$tmp4" "Normal"}Else{Write-Log "Invalid WWPN pool - Name=$tmp2 From=$tmp3 To=$tmp4" "Error"$errTag = $True}}}Break}}If ($i -eq $poolType.length){Write-Log "Invalid pool type - Type=$tmp1 Name=$tmp2 From=$tmp3 To=$tmp4" "Error"$errTag = $True}}}#Validate VLAN definitions$tmp1 = $ucsConfig.VSPEX.VLANsIf ($tmp1 -ne $null){For ($i=0; $i -lt $objectTable.length; $i++){$obj = $objectTable[$i]If ($obj[0] -eq 'VLANs') {$obj[1] = 1; Break}}$ucsConfig.VSPEX.VLANs | ForEach-Object {$_.Var} | ForEach-Object {$tmp1 = $_.Name.trim()$tmp2 = $_.Fabric.trim()$tmp3 = $_.ATag.trim()$tmp4 = $_.BTag.trim()$tmp5 = $_.DefaultNet.trim()If ($tmp2 -eq 'common' -or $tmp2 -eq 'diff' -or $tmp2 -eq 'faba' -or $tmp2 -eq 'fabb'){$tmp = $FalseIf (!($tmp5 -eq 'yes' -or $tmp5 -eq 'no')){Write-Log "Invalid default net value - Name=$tmp1 DefaultNet=$tmp5" "Error"$tmp = $True}Switch ($tmp2){common{If (!(($tmp3 -eq '') -or ([int]$tmp3 -ge 1 -and [int]$tmp3 -le 4095))){Write-Log "Invalid VLAN tag value - Name=$tmp1 Fabric=$tmp2 ATag=$tmp3" "Error"$tmp = $true}}diff{If (!(($tmp3 -eq '') -or ([int]$tmp3 -ge 1 -and [int]$tmp3 -le 4095))){Write-Log "Invalid VLAN tag value - Name=$tmp1 Fabric=$tmp2 ATag=$tmp3" "Error"$tmp = $True}If (!(($tmp4 -eq '') -or ([int]$tmp4 -ge 1 -and [int]$tmp4 -le 4095))){Write-Log "Invalid VLAN tag value - Name=$tmp1 Fabric=$tmp2 BTag=$tmp4" "Error"$tmp = $true}}faba{If (!(($tmp3 -eq '') -or ([int]$tmp3 -ge 1 -and [int]$tmp3 -le 4095))){Write-Log "Invalid VLAN tag value - Name=$tmp1 Fabric=$tmp2 ATag=$tmp3" "Error"$tmp = $True}}fabb{If (!(($tmp4 -eq '') -or ([int]$tmp4 -ge 1 -and [int]$tmp4 -le 4095))){Write-Log "Invalid VLAN tag value - Name=$tmp1 Fabric=$tmp2 BTag=$tmp4" "Error"$tmp = $true}}}If (!$tmp){Write-Log "Valid VLAN definition - Name=$tmp1 Fabric=$tmp2 ATag=$tmp3 BTag=$tmp4 DefaultNet=$tmp5" "Normal"}Else{Write-Log "Invalid VLAN definition - Name=$tmp1 Fabric=$tmp2 ATag=$tmp3 BTag=$tmp4 DefaultNet=$tmp5" "Error"$errTag = $True}}Else{Write-Log "Invalid fabric configuration - Name=$tmp1 Fabric=$tmp2" "Error"$errTag = $True}}}# Validate VNIC template information$tmp1 = $ucsConfig.VSPEX.VNICTemplateIf ($tmp1 -ne $null){For ($i=0; $i -lt $objectTable.length; $i++){$obj = $objectTable[$i]If ($obj[0] -eq 'VNICTemplate') {$obj[1] = 1; Break}}$ucsConfig.VSPEX.VNICTemplate | ForEach-Object {$_.Var} | ForEach-Object {$tmp = $False$tmp1 = $_.Name$tmp2 = $_.MTU.trim()If (!($tmp2 -eq '1500' -or $tmp2 -eq '9000')){Write-Log "Invalid MTU - should be 1500 or 9000 - Name=$tmp1 MTU=$tmp2" "Error"$tmp = $true}$tmp3 = $_.Fabric.trim()$tmp3 = $tmp3.toupper()If (!($tmp3 -eq 'A-B' -or $tmp3 -eq 'B-A')){Write-Log "Invalid fabric - should be A-B or B-A - Name=$tmp1 Fabric=$tmp3" "Error"$tmp = $true}$tmp4 = $_.Type.trim()$tmp4 = $tmp4.tolower()If (!($tmp4 -eq 'updating-template' -or $tmp4 -eq 'initial-template')){Write-Log "Invalid template type - Name=$tmp1 Type=$tmp4" "Error"$tmp = $true}$tmp5 = $_.Native.trim()$tmp5 = $tmp5.tolower()If (!($tmp5 -eq 'no' -or $tmp5 -eq 'yes')){Write-Log "Invalid native mode - must be yes or no - Native=$tmp5" "Error"$tmp = $true}If (!$tmp){Write-Log "Valid VNIC template - Name=$tmp1 MTU=$tmp2 Fabric=$tmp3 Type=$tmp4 Native=$tmp5" "Normal"}Else{Write-Log "Invalid VNIC template - Name=$tmp1 MTU=$tmp2 Fabric=$tmp3 Type=$tmp4 Native=$tmp5" "Error"$errTag = $True}}}# Validate virtual HBA template# <Var Name='FabChn-A' Descr='Fabric A vHBA' Fabric='A' VSAN='default' Type='updating-template' WWNpool='Pool-AF' Qos='' />$tmp1 = $ucsConfig.VSPEX.VHBATemplateIf ($tmp1 -ne $null){For ($i=0; $i -lt $objectTable.length; $i++){$obj = $objectTable[$i]If ($obj[0] -eq 'VHBATemplate') {$obj[1] = 1; Break}}$ucsConfig.VSPEX.VHBATemplate | ForEach-Object {$_.Var} | ForEach-Object {$tmp = $False$tmp1 = $_.Name.trim()$tmp2 = $_.Fabric.trim()$tmp3 = $_.Type.trim()If ($tmp1 -eq ''){Write-Log "Missing name for vHBA template - Fabric=$tmp2 Type=$tmp3" "Error"$tmp = $True}If (!($tmp2 -eq 'A' -or $tmp2 -eq 'B')){Write-Log "Invalid Fabric for vHBA template - Name=$tmp1 Fabric=$tmp2" "Error"$tmp = $True}If (!($tmp3 -eq 'initial-template' -or $tmp3 -eq 'updating-template')){Write-Log "Invalid template type for vHBA template - Name=$tmp1 Type=$tmp3" "Error"$tmp = $True}If (!$tmp){Write-Log "Valid vHBA template - Name=$tmp1 Fabric=$tmp2 Type=$tmp3" "Normal"}Else{Write-Log "Invalid vHBA template - Name=$tmp1 Fabric=$tmp2 Type=$tmp3" "Normal"$errTag = $True}}}# Validate boot policies$tmp1 = $ucsConfig.VSPEX.BootPolicyIf ($tmp1 -ne $null){For ($i=0; $i -lt $objectTable.length; $i++){$obj = $objectTable[$i]If ($obj[0] -eq 'BootPolicy') {$obj[1] = 1; Break}}$ucsConfig.VSPEX.BootPolicy | ForEach-Object {$_.PolicyName} | ForEach-Object {$tmp1 = $_$tmp2 = $_.Name.trim()$tmp1 | ForEach-Object {$_.Var} | ForEach-Object {$tmp = $False$tmp3 = $_.Type.trim()$tmp4 = $_.Device1.trim()$tmp5 = $_.Device2.trim()$tmp6 = $_.PrimaryFabricIf (!($tmp3 -eq 'Local' -or $tmp3 -eq 'VNIC' -or $tmp3 -eq 'VHBA')){Write-Log "Device type must be Local, VNIC, or VHBA - Name=$tmp2 Type=$tmp3" "Error"$tmp = $True}If ($tmp3 -eq 'Local'){If (!($tmp4 -eq 'localdisk' -or $tmp4 -eq 'cdrom' -or $tmp4 -eq 'floppy')){Write-Log "Local device must be localdisk, cdrom, or floppy - Name=$tmp2 Device1=$tmp4" "Error"$tmp = $True}}If ($tmp5 -ne ''){If (!($tmp6 -eq 'A' -or $tmp6 -eq 'B')){Write-Log "Primary Fabric must be A or B - Name=$tmp2 Device1=$tmp4" "Error"$tmp = $True}}If (!$tmp){Write-Log "Valid boot policy - Name=$tmp2 Type=$tmp3 Device1=$tmp4 Device2=$tmp5" "Normal"}Else{Write-Log "Invalid boot policy - Name=$tmp2 Type=$tmp3 Device1=$tmp4 Device2=$tmp5" "Error"$errTag = $True}}}}# TimeZone - just check for presence - no validation - accept what is there$tmp1 = $ucsConfig.VSPEX.TimeZoneIf ($tmp1 -ne $null){For ($i=0; $i -lt $objectTable.length; $i++){$obj = $objectTable[$i]If ($obj[0] -eq 'TimeZone') {$obj[1] = 1; Break}}}# NTP - just check for presence - no validation - accept what is there$tmp1 = $ucsConfig.VSPEX.NTP.VarIf ($tmp1 -ne $null){For ($i=0; $i -lt $objectTable.length; $i++){$obj = $objectTable[$i]If ($obj[0] -eq 'NTP') {$obj[1] = 1; Break}}}# CallHome - just check for presence - no validation - accept what is there$tmp1 = $ucsConfig.VSPEX.CallHome.InUseIf ($tmp1 -ne $null){For ($i=0; $i -lt $objectTable.length; $i++){$obj = $objectTable[$i]If ($obj[0] -eq 'CallHome') {$obj[1] = 1; Break}}}# SubOrg - just check for presence - no validation - accept what is there$tmp1 = $ucsConfig.VSPEX.SubOrg.VarIf ($tmp1 -ne $null){For ($i=0; $i -lt $objectTable.length; $i++){$obj = $objectTable[$i]If ($obj[0] -eq 'SubOrg') {$obj[1] = 1; Break}}}# QoS - just check for presence - no validation - accept what is there$tmp1 = $ucsConfig.VSPEX.QoSIf ($tmp1 -ne $null){For ($i=0; $i -lt $objectTable.length; $i++){$obj = $objectTable[$i]If ($obj[0] -eq 'QoS') {$obj[1] = 1; Break}}}# BIOSPolicy - just check for presence - no validation - accept what is there$tmp1 = $ucsConfig.VSPEX.BIOSPolicy.VarIf ($tmp1 -ne $null){For ($i=0; $i -lt $objectTable.length; $i++){$obj = $objectTable[$i]If ($obj[0] -eq 'BIOSPolicy') {$obj[1] = 1; Break}}}# PlacementPolicy - just check for presence - no validation - accept what is there$tmp1 = $ucsConfig.VSPEX.PlacementPolicy.VarIf ($tmp1 -ne $null){For ($i=0; $i -lt $objectTable.length; $i++){$obj = $objectTable[$i]If ($obj[0] -eq 'PlacementPolicy') {$obj[1] = 1; Break}}}# SPTemplate - just check for presence - no validation - accept what is there$tmp1 = $ucsConfig.VSPEX.SPTemplate.TemplateIf ($tmp1 -ne $null){For ($i=0; $i -lt $objectTable.length; $i++){$obj = $objectTable[$i]If ($obj[0] -eq 'SPTemplate') {$obj[1] = 1; Break}}}# ServiceProfile - just check for presence - no validation - accept what is there$tmp1 = $ucsConfig.VSPEX.ServiceProfile.VarIf ($tmp1 -ne $null){For ($i=0; $i -lt $objectTable.length; $i++){$obj = $objectTable[$i]If ($obj[0] -eq 'ServiceProfile') {$obj[1] = 1; Break}}}# Display to operator which objects do not have any defined values$tmp = $falseFor ($i=0; $i -lt $objectTable.length; $i++){$obj = $objectTable[$i]If ($obj[1] -eq '0'){$tmp1 = $obj[0]Write-Host "No defined values for object $tmp1"$tmp = $true}}# Test for Validation errors or Validate only run. If found, wrap up and shut down.If ($errTag -or $validateOnly){If ($errTag){Write-Host -ForegroundColor Red -BackgroundColor Black "`n`nProcessing stopped due to detected errors"}Set-Location $originalPath$endTime = Get-Date$elapsedTime = New-TimeSpan $startTime $endTimeWrite-Host -ForegroundColor Yellow -BackgroundColor Black "`n`n-----------------------------------------------------------`n"Write-Log "Elapsed time: $($elapsedTime.Hours):$($elapsedTime.Minutes):$($elapsedTime.Seconds)" "Normal"Write-Log "End of processing." "Normal"Exit}# Missing values is not necessarily an error. Ask if operator wishes to continue.If ($tmp){Write-Host "`nYou have some missing values. Do you wish to continue without them?"$tmp1 = Read-Host "You must enter 'YES' (no quotes) to continue"If ($tmp1 -ne 'YES') {Exit}}################################################################################################################################################################# ------------------------------------------------------------------------------## Configure UCS with the contents of UcsConfig.XML## ------------------------------------------------------------------------------################################################################################# Login to UCSM IP address$ucsmIP = $UcsConfig.VSPEX.UCSMIP.trim()$Error.Clear()Write-Host -BackgroundColor Black -ForegroundColor White "`n`n Enter proper credentials to access UCSM`n"$ucsCreds = Get-Credential$ucsHandle = Connect-Ucs $ucsmIP $ucsCreds$ucsDomain = $ucsHandle.UcsIf ($error.length -lt 1){Write-Log "Successful login to UCS domain $ucsDomain" "Normal"}Else{Write-Log "Invalid login to $ucsmIP" "Error"exit}$orgRoot = Get-UcsOrg -Level root# Set timezone$present = $falseFor ($i=0; $i -lt $objectTable.length; $i++){$obj = $objectTable[$i]If ($obj[0] -eq 'TimeZone' -and $obj[1] -eq '1') {$present = $true; Break}}If ($Present){$error.Clear()$tmp1 = $ucsConfig.VSPEX.TimeZone.trimend(" ")$trash = Get-UcsTimezone | Set-UcsTimezone -AdminState "enabled" -Timezone $tmp1 -ForceIf ($error.length -lt 1){Write-Log "Set timezone to $tmp1" "Normal"}Else{Write-Log "ERROR setting timezone to $tmp1" "Error"$errTag = $True}}# Set NTP servers$present = $falseFor ($i=0; $i -lt $objectTable.length; $i++){$obj = $objectTable[$i]If ($obj[0] -eq 'NTP' -and $obj[1] -eq '1') {$present = $true; Break}}If ($Present){$ucsConfig.VSPEX.NTP | ForEach-Object {$_.Var} | ForEach-Object {$error.Clear()$tmp1 = $_.Name.trim()$trash = Add-UcsNtpServer -Name $tmp1 -ModifyPresentIf ($error.length -lt 1){Write-Log "Set NTP server to $tmp1" "Normal"}Else{Write-Log "ERROR setting NTP server to $tmp1" "Error"$errTag = $True}}}# Set Management IP Pool values$present = $falseFor ($i=0; $i -lt $objectTable.length; $i++){$obj = $objectTable[$i]If ($obj[0] -eq 'MgmtIP' -and $obj[1] -eq '1') {$present = $true; Break}}If ($Present){$ucsConfig.VSPEX.MgmtIP | ForEach-Object {$_.Pool} | ForEach-Object {$error.Clear()$tmp1 = $_$tmp2 = $_.Name.trim()$tmp3 = $_.Descr$tmp1 | ForEach-Object {$tmp = $False$tmp4 = $_.Order.trim()$tmp5 = $_.Start.trim()$tmp6 = $_.End.trim()$tmp7 = $_.Gateway.trim()$tmp8 = $_.PrimaryDNS.trim()$tmp9 = $_.SecondaryDNS.trim()Start-UcsTransaction$mo = $orgRoot | Add-UcsIpPool -Name $tmp2 -Descr $tmp3 -AssignmentOrder $tmp4 -ModifyPresent$trash =$mo | Add-UcsIpPoolBlock -From $tmp5 -To $tmp6 -DefGw $tmp7 -PrimDns $tmp8 -SecDns $tmp9 -ModifyPresentComplete-UcsTransaction | Out-NullIf ($error.length -lt 1){Write-Log "Management IP Pool - Name=$tmp2 Descr=$tmp3 Order=$tmp4" "Normal"Write-Log " - From=$tmp5 To=$tmp6 G/W=$tmp7 Primary=$tmp8 Secondary=$tmp9" "Normal"}Else{Write-Log "ERROR Management IP Pool - Name=$tmp2 Descr=$tmp9 Order=$tmp3" "Error"Write-Log " - From=$tmp4 To=$tmp5 G/W=$tmp6 Primary=$tmp7 Secondary=$tmp8" "Error"$errTag = $True}}}}# Set Call Home values$present = $falseFor ($i=0; $i -lt $objectTable.length; $i++){$obj = $objectTable[$i]If ($obj[0] -eq 'CallHome' -and $obj[1] -eq '1') {$present = $true; Break}}If ($Present){$error.Clear()$tmp1 = $ucsConfig.VSPEX.CallHome.InUse.trim()If ($tmp1 -eq '1'){$tmp1 = $ucsConfig.VSPEX.CallHome.SmtpSrv.trimend(" ")$tmp2 = $ucsConfig.VSPEX.CallHome.Address.trimend(" ")$tmp3 = $ucsConfig.VSPEX.CallHome.ContactName.trimend(" ")$tmp4 = $ucsConfig.VSPEX.CallHome.ContactPhone.trimend(" ")$tmp5 = $ucsConfig.VSPEX.CallHome.ContactEmail.trimend(" ")$tmp6 = $ucsConfig.VSPEX.CallHome.CustomerID.trimend(" ")$tmp7 = $ucsConfig.VSPEX.CallHome.ContractID.trimend(" ")$tmp8 = $ucsConfig.VSPEX.CallHome.SiteID.trimend(" ")$tmp9 = $ucsConfig.VSPEX.CallHome.SmtpFrom.trimend(" ")$tmp10 = $ucsConfig.VSPEX.CallHome.SmtpRecipient.trimend(" ")Start-UcsTransaction$trash = Get-UcsCallhome | Set-UcsCallhome -AdminState on -AlertThrottlingAdminState on -Force$trash = Get-UcsCallhomeSmtp | Set-UcsCallhomeSmtp -Host $tmp1 -Port 25 -Force$trash = Get-UcsCallhomeSource | Set-UcsCallhomeSource -Addr $tmp2 -Contact $tmp3 -Email $tmp5 -Contract $tmp7 -Customer $tmp6 `-From $tmp9 -Phone $tmp4 -ReplyTo $tmp9 -Site $tmp8 -Urgency debug -Force$trash = Get-UcsCallhomeProfile -Name full_txt | Add-UcsCallhomeRecipient -Email $tmp10 -ModifyPresentComplete-UcsTransaction | Out-NullIf ($error.length -lt 1){Write-Log "Set call home for $tmp3" "Normal"}Else{Write-Log "ERROR setting call home for $tmp3" "Error"$errTag = $True}}}# Set Chassis discovery setting$present = $falseFor ($i=0; $i -lt $objectTable.length; $i++){$obj = $objectTable[$i]If ($obj[0] -eq 'ChassisDiscovery' -and $obj[1] -eq '1') {$present = $true; Break}}If ($Present){$error.Clear()$tmp1 = $ucsConfig.VSPEX.ChassisDiscovery.trim()$trash = $orgRoot | Get-UcsChassisDiscoveryPolicy | Set-UcsChassisDiscoveryPolicy -Action $tmp1 `-LinkAggregationPref "port-channel" -Rebalance "user-acknowledged" -ForceIf ($error.length -lt 1){Write-Log "Set chassis discovery policy to $tmp1" "Normal"}Else{Write-Log "ERROR setting chassis discovery policy to $tmp1" "Error"$errTag = $True}# Set Number of Chassis$tmp1 = Get-UcsChassisForEach ($chassis in $tmp1){$error.Clear()$tmp2 = $chassis.ID$trash = Get-UcsChassis -Id $tmp2 | Set-UcsChassis -AdminState "re-acknowledge" -ForceIf ($error.length -lt 1){Write-Log "Chassis $tmp2 acknowledged" "Normal"}Else{Write-Log "ERROR acknowledging chassis $tmp2" "Error"$errTag = $True}}}# Set Organizations$present = $falseFor ($i=0; $i -lt $objectTable.length; $i++){$obj = $objectTable[$i]If ($obj[0] -eq 'SubOrg' -and $obj[1] -eq '1') {$present = $true; Break}}If ($Present){$ucsConfig.VSPEX.SubOrg | ForEach-Object {$_.Var} | ForEach-Object {$error.Clear()$tmp1 = $_.Name$tmp2 = $_.Descr$trash = $orgRoot | Add-UcsOrg -Name $tmp1 -Descr $tmp2 -ModifyPresentIf ($error.length -lt 1){Write-Log "Set organization Name=$tmp1 Description=$tmp2" "Normal"}Else{Write-Log "ERROR setting organization Name=$tmp1 Description=$tmp2" "Error"$errTag = $True}}}# Set QoS Policies$error.Clear()$trash = Get-UcsBestEffortQosClass | Set-UcsBestEffortQosClass -Mtu "9000" -Force | Out-NullIf ($error.length -lt 1){Write-Log "Set Best Effort QoS Class to MTU=9000" "Normal"}Else{Write-Log "ERROR setting Best Effort QoS Class to MTU=9000" "Error"$errTag = $True}$present = $falseFor ($i=0; $i -lt $objectTable.length; $i++){$obj = $objectTable[$i]If ($obj[0] -eq 'QoS' -and $obj[1] -eq '1') {$present = $true; Break}}If ($Present){# Platinum$error.Clear()$tmp1 = $ucsConfig.VSPEX.QoS.Platinum.trim()If ($tmp1 -ne ""){# Start-UcsTransaction$trash = Get-UcsQosClass -Priority "platinum" | Set-UcsQosClass -Mtu "9000" -Force$mo = Add-UcsQosPolicy -Name $tmp1 -ModifyPresent$trash = $mo | Get-UcsVnicEgressPolicy | Set-UcsVnicEgressPolicy -Prio "platinum" -Force# Complete-UcsTransaction | Out-NullIf ($error.length -lt 1){Write-Log "Set platinum QoS Class to MTU=9000" "Normal"}Else{Write-Log "ERROR setting platinum QoS Class to MTU=9000" "Error"$errTag = $True}}# Gold$error.Clear()$tmp1 = $ucsConfig.VSPEX.QoS.Gold.trim()If ($tmp1 -ne ""){# Start-UcsTransaction$trash = Get-UcsQosClass -Priority "gold" | Set-UcsQosClass -Mtu "9000" -Force$mo = Add-UcsQosPolicy -Name $tmp1 -ModifyPresent$trash = $mo | Get-UcsVnicEgressPolicy | Set-UcsVnicEgressPolicy -Prio "gold" -Force# Complete-UcsTransaction | Out-NullIf ($error.length -lt 1){Write-Log "Set gold QoS Class to MTU=9000" "Normal"}Else{Write-Log "ERROR setting gold QoS Class to MTU=9000" "Error"$errTag = $True}}# Silver$error.Clear()$tmp1 = $ucsConfig.VSPEX.QoS.Silver.trim()If ($tmp1 -ne ""){# Start-UcsTransaction$trash = Get-UcsQosClass -Priority "silver" | Set-UcsQosClass -Mtu "9000" -Force$mo = Add-UcsQosPolicy -Name $tmp1 -ModifyPresent$trash = $mo | Get-UcsVnicEgressPolicy | Set-UcsVnicEgressPolicy -Prio silver -Force# Complete-UcsTransaction | Out-NullIf ($error.length -lt 1){Write-Log "Set silver QoS Class to MTU=9000" "Normal"}Else{Write-Log "ERROR setting silver QoS Class to MTU=9000" "Error"$errTag = $True}}# Bronze$error.Clear()$tmp1 = $ucsConfig.VSPEX.QoS.Bronze.trim()If ($tmp1 -ne ""){# Start-UcsTransaction$trash = Get-UcsQosClass -Priority "bronze" | Set-UcsQosClass -Mtu "9000" -Force$mo = Add-UcsQosPolicy -Name $tmp1 -ModifyPresent$trash = $mo | Get-UcsVnicEgressPolicy | Set-UcsVnicEgressPolicy -Prio bronze -Force# Complete-UcsTransaction | Out-NullIf ($error.length -lt 1){Write-Log "Set bronze QoS Class to MTU=9000" "Normal"}Else{Write-Log "ERROR setting bronze QoS Class to MTU=9000" "Error"$errTag = $True}}}# Set Power Control Policies$present = $falseFor ($i=0; $i -lt $objectTable.length; $i++){$obj = $objectTable[$i]If ($obj[0] -eq 'PowerPolicy' -and $obj[1] -eq '1') {$present = $true; Break}}If ($Present){$ucsConfig.VSPEX.PowerPolicy | ForEach-Object {$_.Var} | ForEach-Object {$error.Clear()$tmp1 = $_.Name.trim()$tmp2 = $_.Priority.trim()If ($tmp1 -eq 'Default') {$tmp1 = $tmp1.tolower()}$trash = $orgRoot | Add-UcsPowerPolicy -Name $tmp1 -Prio $tmp2 -ModifyPresentIf ($error.length -lt 1){Write-Log "Set power control policy Name=$tmp1 to Priority=$tmp2" "Normal"}Else{Write-Log "ERROR setting power control policy Name=$tmp1 to Priority=$tmp2" "Error"$errTag = $True}}}# Set Scrub Policies$present = $falseFor ($i=0; $i -lt $objectTable.length; $i++){$obj = $objectTable[$i]If ($obj[0] -eq 'ScrubPolicy' -and $obj[1] -eq '1') {$present = $true; Break}}If ($Present){$ucsConfig.VSPEX.ScrubPolicy | ForEach-Object {$_.Var} | ForEach-Object {$error.Clear()$tmp1 = $_.Name.trim()$tmp2 = $_.Descr$tmp3 = $_.DiskScrub.trim()$tmp3 = $tmp3.tolower()$tmp4 = $_.BiosScrub.trim()$tmp4 = $tmp4.tolower()If ($tmp1 -eq 'Default') {$tmp1 = $tmp1.tolower()}$trash = $orgRoot | Add-UcsScrubPolicy -Name $tmp1 -Descr $tmp2 -DiskScrub $tmp3 -BiosSettingsScrub $tmp4 -PolicyOwner "local" -ModifyPresentIf ($error.length -lt 1){Write-Log "Set scrub policy Name=$tmp1 Desc=$tmp2 Disc=$tmp3 Bios=$tmp4" "Normal"}Else{Write-Log "ERROR setting scrub policy Name=$tmp1 Desc=$tmp2 Disc=$tmp3 Bios=$tmp4" "Error"$errTag = $True}}}# Set Maintenance Policies$present = $falseFor ($i=0; $i -lt $objectTable.length; $i++){$obj = $objectTable[$i]If ($obj[0] -eq 'MaintenancePolicy' -and $obj[1] -eq '1') {$present = $true; Break}}If ($Present){$ucsConfig.VSPEX.MaintenancePolicy | ForEach-Object {$_.Var} | ForEach-Object {$error.Clear()$tmp1 = $_.Name.trim()$tmp2 = $_.Descr.trim()$tmp3 = $_.Policy.trim()$tmp3 = $tmp3.tolower()$trash = $orgRoot | Add-UcsMaintenancePolicy -Name $tmp1 -Descr $tmp2 -UptimeDisr $tmp3 -ModifyPresentIf ($error.length -lt 1){Write-Log "Set maintenance policy Name=$tmp1 Descr=$tmp2 Policy=$tmp3" "Normal"}Else{Write-Log "ERROR setting maintenance policy Name=$tmp1 Descr=$tmp2 Policy=$tmp3" "Error"$errTag = $True}}}# Set Local Disk Policies$present = $falseFor ($i=0; $i -lt $objectTable.length; $i++){$obj = $objectTable[$i]If ($obj[0] -eq 'DiskPolicy' -and $obj[1] -eq '1') {$present = $true; Break}}If ($Present){#Set-UcsQosClass -QosClass (Get-UcsQosClass -Priority gold) -AdminState enabled -Mtu 9000 -Force$ucsConfig.VSPEX.DiskPolicy | ForEach-Object {$_.Var} | ForEach-Object {$error.Clear()$tmp1 = $_.Name.trim()$tmp2 = $_.Mode.trim()$tmp2 = $tmp2.tolower()$tmp3 = $_.Descr.trim()$tmp4 = $_.Protect.trim()$tmp4 = $tmp4.tolower()$trash = $orgRoot | Add-UcsLocalDiskConfigPolicy -Name $tmp1 -Mode $tmp2 -Descr $tmp3 -ProtectConfig $tmp4 -ModifyPresentIf ($error.length -lt 1){Write-Log "Set Local Disk Config Policy Name=$tmp1 Mode=$tmp2 Descr=$tmp3 Protect=$tmp4" "Normal"}Else{Write-Log "ERROR setting Local Disk Config Policy Name=$tmp1 Mode=$tmp2 Descr=$tmp3 Protect=$tmp4" "Error"$errTag = $True}}}# Set BIOS Policy$present = $falseFor ($i=0; $i -lt $objectTable.length; $i++){$obj = $objectTable[$i]If ($obj[0] -eq 'BIOSPolicy' -and $obj[1] -eq '1') {$present = $true; Break}}If ($Present){$ucsConfig.VSPEX.BIOSPolicy | ForEach-Object {$_.Var} | ForEach-Object {$error.Clear()$tmp1 = $_.Name.trim()$tmp2 = $_.Descr$tmp3 = $_.VpQuietBoot.trim()Start-UcsTransaction$mo = $orgRoot | Add-UcsBiosPolicy -Name $tmp1 -Descr $tmp2 -RebootOnUpdate "no" -ModifyPresent$mo | Set-UcsBiosVfQuietBoot -VpQuietBoot $tmp3 -Force | Out-NullComplete-UcsTransaction | Out-NullIf ($error.length -lt 1){Write-Log "Create BIOS Policy - Name=$tmp1 Descr=$tmp2 QuietBoot=$tmp3" "Normal"}Else{Write-Log "ERROR create BIOS Policy - Name=$tmp1 Descr=$tmp2 QuietBoot=$tmp3" "Error"$errTag = $True}}}# Set vNIC/vHBA Placement Policy$present = $falseFor ($i=0; $i -lt $objectTable.length; $i++){$obj = $objectTable[$i]If ($obj[0] -eq 'PlacementPolicy' -and $obj[1] -eq '1') {$present = $true; Break}}If ($Present){$ucsConfig.VSPEX.PlacementPolicy | ForEach-Object {$_.Var} | ForEach-Object {$error.Clear()$tmp1 = $_.Name.trim()$tmp2 = $_.SlotMapping.trim()$tmp3 = $_.Selection.trim()Start-UcsTransaction$mo = $orgRoot | Add-UcsPlacementPolicy -Name $tmp1 -MezzMapping $tmp2 -ModifyPresent$trash = $mo | Add-UcsFabricVCon -Fabric "NONE" -Id "1" -Select $tmp3 -Share "shared" -Transport "ethernet","fc" -ModifyPresent$trash = $mo | Add-UcsFabricVCon -Fabric "NONE" -Id "2" -InstType "auto" -Placement "physical" -Select "all" -Share "shared" -Transport "ethernet","fc" -ModifyPresent$trash = $mo | Add-UcsFabricVCon -Fabric "NONE" -Id "3" -InstType "auto" -Placement "physical" -Select "all" -Share "shared" -Transport "ethernet","fc" -ModifyPresent$trash = $mo | Add-UcsFabricVCon -Fabric "NONE" -Id "4" -InstType "auto" -Placement "physical" -Select "all" -Share "shared" -Transport "ethernet","fc" -ModifyPresentComplete-UcsTransaction | Out-NullIf ($error.length -lt 1){Write-Log "Create vNIC/vHBA Placement Policy - Name=$tmp1 Mapping=$tmp2 Selection=$tmp3" "Normal"}Else{Write-Log "ERROR creating vNIC/vHBA Placement Policy - Name=$tmp1 Mapping=$tmp2 Selection=$tmp3" "Error"$errTag = $True}}}# FI port definitions - assumption that both fabrics are configured identically$present = $falseFor ($i=0; $i -lt $objectTable.length; $i++){$obj = $objectTable[$i]If ($obj[0] -eq 'FI' -and $obj[1] -eq '1') {$present = $true; Break}}If ($Present){$ucsConfig.VSPEX.FI | ForEach-Object {$_.Var} | ForEach-Object {$error.Clear()$tmp1 = $_.SlotID.trim()$tmp2 = $_.PortID.trim()$tmp3 = $_.Role.trim()$tmp4 = $_.UsrLbl$tmp5 = $_.VLAN.trim()$tmp6 = $_.Native.trim()$tmp6 = $tmp6.tolower()$tmp7 = $_.Mode.trim()$tmp7 = $tmp7.tolower()$tmp8 = $_.QoS.trim()$tmp8 = $tmp8.tolower()If ($tmp3 -ne ''){Switch ($tmp3){Appliance{Start-UcsTransaction$trash = Get-UcsApplianceCloud | Get-UcsVlan -Name $tmp5 -LimitScope | Add-UcsVlanMemberPort -SwitchId "A" -SlotId $tmp1 `-PortId $tmp2 -AdminState "enabled" -IsNative $tmp6 -Name "" -ModifyPresent$trash = Get-UcsFabricApplianceCloud -Id "A" | Add-UcsAppliancePort -Slot $tmp1 -PortId $tmp2 -PortMode $tmp7 -Prio $tmp8 `-UsrLbl $tmp4 -AdminSpeed "10gbps" -AdminState "enabled" -FlowCtrlPolicy "default" -Name "" -NwCtrlPolicyName "default" `-PinGroupName "" -ModifyPresent$trash = Get-UcsApplianceCloud | Get-UcsVlan -Name $tmp5 -LimitScope | Add-UcsVlanMemberPort -SwitchId "B" -SlotId $tmp1 `-PortId $tmp2 -AdminState "enabled" -IsNative $tmp6 -Name "" -ModifyPresent$trash = Get-UcsFabricApplianceCloud -Id "B" | Add-UcsAppliancePort -SlotId $tmp1 -PortId $tmp2 -PortMode $tmp7 -Prio $tmp8 `-UsrLbl $tmp4 -AdminSpeed "10gbps" -AdminState "enabled" -FlowCtrlPolicy "default" -Name "" -NwCtrlPolicyName "default" `-PinGroupName "" -ModifyPresentComplete-UcsTransaction | Out-NullIf ($error.length -lt 1){Write-Log "Set fabric port - Slot=$tmp1 Port=$tmp2 Role=$tmp3 UsrLbl=$tmp4" "Normal"Write-Log " - VLAN=$tmp5 Native=$tmp6 Mode=$tmp7 QoS=$tmp8" "Normal"}Else{Write-Log "ERROR setting fabric port - Slot=$tmp1 Port=$tmp2 Role=$tmp3 UsrLbl=$tmp4" "Error"Write-Log " - VLAN=$tmp5 Native=$tmp6 Mode=$tmp7 QoS=$tmp8" "Error"$errTag = $True}}FCoE{$trash = Get-UcsFiSanCloud -Id "A" | Add-UcsFabricFcoeSanEp -SlotId $tmp1 -PortId $tmp2 -UsrLbl $tmp4 -Name "" `-AdminState "enabled" -ModifyPresent$trash = Get-UcsFiSanCloud -Id "B" | Add-UcsFabricFcoeSanEp -SlotId $tmp1 -PortID $tmp2 -UsrLbl $tmp4 -Name "" `-AdminState "enabled" -ModifyPresentIf ($error.length -lt 1){Write-Log "Set fabric port - Slot=$tmp1 Port=$tmp2 Role=$tmp3 UsrLbl=$tmp4" "Normal"}Else{Write-Log "ERROR setting fabric port - Slot=$tmp1 Port=$tmp2 Role=$tmp3 UsrLbl=$tmp4" "Error"$errTag = $True}}Server{$trash = Get-UcsFabricServerCloud -Id "A" | Add-UcsServerPort -SlotId $tmp1 -PortId $tmp2 -UsrLbl $tmp4 -Name "" `-AdminState "enabled" -ModifyPresent$trash = Get-UcsFabricServerCloud -Id "B" | Add-UcsServerPort -SlotId $tmp1 -PortId $tmp2 -UsrLbl $tmp4 -Name "" `-AdminState "enabled" -ModifyPresentIf ($error.length -lt 1){Write-Log "Set fabric port - Slot=$tmp1 Port=$tmp2 Role=$tmp3 UsrLbl=$tmp4" "Normal"}Else{Write-Log "ERROR setting fabric port - Slot=$tmp1 Port=$tmp2 Role=$tmp3 UsrLbl=$tmp4" "Error"$errTag = $True}}Uplink{$trash = Get-UcsFiLanCloud -Id "A" | Add-UcsUplinkPort -SlotId $tmp1 -PortId $tmp2 -UsrLbl $tmp4 -Name "" `-AdminSpeed "10gbps" -AdminState "enabled" -FlowCtrlPolicy "default" -ModifyPresent$trash = Get-UcsFiLanCloud -Id "B" | Add-UcsUplinkPort -SlotId $tmp1 -PortId $tmp2 -UsrLbl $tmp4 -Name "" `-AdminSpeed "10gbps" -AdminState "enabled" -FlowCtrlPolicy "default" -ModifyPresentIf ($error.length -lt 1){Write-Log "Set fabric port - Slot=$tmp1 Port=$tmp2 Role=$tmp3 UsrLbl=$tmp4" "Normal"}Else{Write-Log "ERROR setting fabric port - Slot=$tmp1 Port=$tmp2 Role=$tmp3 UsrLbl=$tmp4" "Error"$errTag = $True}}}}}}# Fibre Channel Port definition$fiA = Get-UcsFiSanCloud -Id "A"$fiB = Get-UcsFiSanCloud -Id "B"$present = $falseFor ($i=0; $i -lt $objectTable.length; $i++){$obj = $objectTable[$i]If ($obj[0] -eq 'FCslot1' -and $obj[1] -eq '1') {$present = $true; Break}}If ($Present){[int]$itmp1 = $ucsConfig.VSPEX.FCslot1.PortIDIf ($itmp1 -ne 0){$error.Clear()$tmp2 = $ucsConfig.VSPEX.FCslot1.UsrLblStart-UcsTransactionFor ($i=32; $i -ge $itmp1; $i--){$trash = $fiA | Add-UcsFcUplinkPort -SlotId 1 -PortId $i -UsrLbl $tmp2 -AdminState "enabled" -Name "" -ModifyPresent}Complete-UcsTransaction | Out-NullStart-UcsTransactionFor ($i=32; $i -ge $itmp1; $i--){$trash = $fiB | Add-UcsFcUplinkPort -SlotId 1 -PortId $i -UsrLbl $tmp2 -AdminState "enabled" -Name "" -ModifyPresent}Complete-UcsTransaction | Out-NullIf ($error.length -lt 1){Write-Log "Set Fixed Module FC Port - Port=$itmp1 UsrLbl=$tmp2" "Normal"}Else{Write-Log "ERROR setting Fixed Module FC Port - Port=$itmp1 UsrLbl=$tmp2" "Error"$errTag = $True}}}$present = $falseFor ($i=0; $i -lt $objectTable.length; $i++){$obj = $objectTable[$i]If ($obj[0] -eq 'FCslot2' -and $obj[1] -eq '1') {$present = $true; Break}}If ($Present){[int]$itmp1 = $ucsConfig.VSPEX.FCslot2.PortIDIf ($itmp1 -ne 0){$error.Clear()$tmp2 = $ucsConfig.VSPEX.FCslot2.UsrLblStart-UcsTransactionFor ($i=16; $i -ge $itmp1; $i--){$trash = $fiA | Add-UcsFcUplinkPort -SlotId 2 -PortId $i -UsrLbl $tmp2 -AdminState "enabled" -Name "" -ModifyPresent}Complete-UcsTransaction | Out-NullStart-UcsTransactionFor ($i=16; $i -ge $itmp1; $i--){$trash = $fiB | Add-UcsFcUplinkPort -SlotId 2 -PortId $i -UsrLbl $tmp2 -AdminState "enabled" -Name "" -ModifyPresent}Complete-UcsTransaction | Out-NullIf ($error.length -lt 1){Write-Log "Set Expansion Module FC Port - Port=$itmp1 UsrLbl=$tmp2" "Normal"}Else{Write-Log "ERROR setting Expansion Module FC Port - Port=$itmp1 UsrLbl=$tmp2" "Error"$errTag = $True}}}# Port Channel$present = $falseFor ($i=0; $i -lt $objectTable.length; $i++){$obj = $objectTable[$i]If ($obj[0] -eq 'PC' -and $obj[1] -eq '1') {$present = $true; Break}}If ($Present){$tmp1 = $ucsConfig.VSPEX.PC.AName.trim()$tmp2 = $ucsConfig.VSPEX.PC.BName.trim()$tmp3 = $ucsConfig.VSPEX.PC.APortID.trim()$tmp4 = $ucsConfig.VSPEX.PC.BPortID.trim()$tmp5 = $ucsConfig.VSPEX.PC.Slot.trim()$tmp6 = $ucsConfig.VSPEX.PC.Port1.trim()$tmp7 = $ucsConfig.VSPEX.PC.Port2.trim()$error.Clear()Start-UcsTransaction$mo = Get-UcsFiLanCloud -Id A | Add-UcsUplinkPortChannel -Name $tmp1 -PortId $tmp3 `-AdminState "enabled" -AdminSpeed "10gbps" -FlowCtrlPolicy "default" -ModifyPresent$trash = $mo | Add-UcsUplinkPortChannelMember -SlotId $tmp5 -PortId $tmp6 -AdminState "enabled" -ModifyPresent$trash = $mo | Add-UcsUplinkPortChannelMember -SlotId $tmp5 -PortId $tmp7 -AdminState "enabled" -ModifyPresentComplete-UcsTransaction | Out-NullIf ($error.length -lt 1){Write-Log "Set Port Channel - Name=$tmp1 PortChannelID=$tmp3 Slot/Port/Port=$tmp5/$tmp6/$tmp7" "Normal"}Else{Write-Log "ERROR Set Port Channel - Name=$tmp1 PortChannelID=$tmp3 Slot/Port/Port=$tmp5/$tmp6/$tmp7" "Error"$errTag = $True}$error.Clear()Start-UcsTransaction$mo = Get-UcsFiLanCloud -Id B | Add-UcsUplinkPortChannel -Name $tmp2 -PortId $tmp4 `-AdminState "enabled" -AdminSpeed "10gbps" -FlowCtrlPolicy "default" -ModifyPresent$trash = $mo | Add-UcsUplinkPortChannelMember -SlotId $tmp5 -PortId $tmp6 -AdminState "enabled" -ModifyPresent$trash = $mo | Add-UcsUplinkPortChannelMember -SlotId $tmp5 -PortId $tmp7 -AdminState "enabled" -ModifyPresentComplete-UcsTransaction | Out-NullIf ($error.length -lt 1){Write-Log "Set Port Channel - Name=$tmp2 PortChannelID=$tmp4 Slot/Port/Port=$tmp5/$tmp6/$tmp7" "Normal"}Else{Write-Log "ERROR Set Port Channel - Name=$tmp2 PortChannelID=$tmp4 Slot/Port/Port=$tmp5/$tmp6/$tmp7" "Error"$errTag = $True}}# Various Pools$present = $falseFor ($i=0; $i -lt $objectTable.length; $i++){$obj = $objectTable[$i]If ($obj[0] -eq 'Pools' -and $obj[1] -eq '1') {$present = $true; Break}}If ($Present){$ucsConfig.VSPEX.Pools | ForEach-Object {$_.Var} | ForEach-Object {$error.Clear()$tmp1 = $_.Type.trim()$tmp2 = $_.Name.trim()$tmp3 = $_.From.trim()$tmp4 = $_.To.trim()$tmp5 = $_.Order.trim()$tmp5 = $tmp5.tolower()$tmp6 = $_.Org.trim()$tmp7 = $_.DescrIf ($tmp2 -eq 'default') {$tmp2 = $tmp2.tolower()}If ($tmp6 -eq "root") {$mo = $orgRoot}Else {$mo = $orgRoot | Get-UcsOrg -Name $tmp6 -LimitScope}Switch ($tmp1){MAC{Start-UcsTransaction$mo_1 = $mo | Add-UcsMacPool -Name $tmp2 -AssignmentOrder $tmp5 -Descr $tmp7 -ModifyPresent$trash = $mo_1 | Add-UcsMacMemberBlock -From $tmp3 -To $tmp4 -ModifyPresentComplete-UcsTransaction | Out-NullIf ($error.length -lt 1){Write-Log "Add MAC Pool - Name=$tmp2 Org=$tmp6 Descr=$tmp7 From/To=$tmp3-$tmp4" "Normal"}Else{Write-Log "ERROR Add MAC Pool - Name=$tmp2 Org=$tmp6 Descr=$tmp7 From/To=$tmp3-$tmp4" "Error"$errTag = $True}}UUID{Start-UcsTransaction$mo_1 = $mo | Add-UcsUuidSuffixPool -Name $tmp2 -AssignmentOrder $tmp5 -Descr $tmp7 -ModifyPresent$trash = $mo_1 | Add-UcsUuidSuffixBlock -From $tmp3 -To $tmp4 -ModifyPresentComplete-UcsTransaction | Out-NullIf ($error.length -lt 1){Write-Log "Add UUID Pool - Name=$tmp2 Org=$tmp6 Descr=$tmp7 From/To=$tmp3-$tmp4" "Normal"}Else{Write-Log "ERROR Add UUID Pool - Name=$tmp2 Org=$tmp6 Descr=$tmp7 From/To=$tmp3-$tmp4" "Error"$errTag = $True}}WWNN{Start-UcsTransaction$mo_1 = $mo | Add-UcsWwnPool -Name $tmp2 -AssignmentOrder $tmp5 -Purpose "node-wwn-assignment" -Descr $tmp7 -ModifyPresent$trash = $mo_1 | Add-UcsWwnMemberBlock -From $tmp3 -To $tmp4 -ModifyPresentComplete-UcsTransaction | Out-NullIf ($error.length -lt 1){Write-Log "Add WWNN Pool - Name=$tmp2 Org=$tmp6 Descr=$tmp7 From/To=$tmp3-$tmp4" "Normal"}Else{Write-Log "ERROR Add WWNN Pool - Name=$tmp2 Org=$tmp6 Descr=$tmp7 From/To=$tmp3-$tmp4" "Error"$errTag = $True}}WWPN{Start-UcsTransaction$mo_1 = $mo | Add-UcsWwnPool -Name $tmp2 -AssignmentOrder $tmp5 -Purpose "port-wwn-assignment" -Descr $tmp7 -ModifyPresent$trash = $mo_1 | Add-UcsWwnMemberBlock -From $tmp3 -To $tmp4 -ModifyPresentComplete-UcsTransaction | Out-NullIf ($error.length -lt 1){Write-Log "Add WWPN Pool - Name=$tmp2 Org=$tmp6 Descr=$tmp7 From/To=$tmp3-$tmp4" "Normal"}Else{Write-Log "ERROR Add WWPN Pool - Name=$tmp2 Org=$tmp6 Descr=$tmp7 From/To=$tmp3-$tmp4" "Error"$errTag = $True}}}}}# VLAN definitions$present = $falseFor ($i=0; $i -lt $objectTable.length; $i++){$obj = $objectTable[$i]If ($obj[0] -eq 'VLANs' -and $obj[1] -eq '1') {$present = $true; Break}}If ($Present){$ucsConfig.VSPEX.VLANs | ForEach-Object {$_.Var} | ForEach-Object {$error.Clear()$tmp1 = $_.Name.trim()$tmp2 = $_.Fabric.trim()$tmp3 = $_.ATag.trim()$tmp4 = $_.BTag.trim()$tmp5 = $_.DefaultNet.trim()Switch ($tmp2){Common{$trash = Get-UcsLanCloud | Add-UcsVlan -Name $tmp1 -Id $tmp3 -DefaultNet $tmp5 -CompressionType "included" -Sharing "none" -ModifyPresent}Diff{$trash = Get-UcsFiLanCloud -Id "A" | Add-UcsVlan -Name $tmp1 -Id $tmp3 -DefaultNet $tmp5 -CompressionType "included" -Sharing "none" -ModifyPresent$trash = Get-UcsFiLanCloud -Id "B" | Add-UcsVlan -Name $tmp1 -Id $tmp4 -DefaultNet $tmp5 -CompressionType "included" -Sharing "none" -ModifyPresent}FabA{$trash = Get-UcsFiLanCloud -Id "A" | Add-UcsVlan -Name $tmp1 -Id $tmp3 -DefaultNet $tmp5 -CompressionType "included" -Sharing "none" -ModifyPresent}FabB{$trash = Get-UcsFiLanCloud -Id "B" | Add-UcsVlan -Name $tmp1 -Id $tmp4 -DefaultNet $tmp5 -CompressionType "included" -Sharing "none" -ModifyPresent}}If ($error.length -lt 1){Write-Log "Add VLAN - Name=$tmp1 Fabric=$tmp2 ATag=$tmp3 BTag=$tmp4 DefaultNet=$tmp5" "Normal"}Else{Write-Log "ERROR Add VLAN - Name=$tmp1 Fabric=$tmp2 ATag=$tmp3 BTag=$tmp4 DefaultNet=$tmp5" "Error"$errTag = $True}}}# VNIC Templates$present = $falseFor ($i=0; $i -lt $objectTable.length; $i++){$obj = $objectTable[$i]If ($obj[0] -eq 'VNICTemplate' -and $obj[1] -eq '1') {$present = $true; Break}}If ($Present){$ucsConfig.VSPEX.VNICTemplate | ForEach-Object {$_.Var} | ForEach-Object {$error.Clear()$tmp1 = $_.Name.trim()$tmp2 = $_.MTU.trim()$tmp3 = $_.Fabric.trim()$tmp3 = $tmp3.toupper()$tmp4 = $_.MACpool.trim()$tmp5 = $_.QoS.trim()$tmp6 = $_.VLAN.trim()$tmp7 = $_.Order.trim()$tmp8 = $_.Type.trim()$tmp8 = $tmp8.tolower()$tmp9 = $_.Native.trim()$tmp9 = $tmp9.tolower()$tmp10 = $_.Org.trim()If ($tmp10 -eq "root") {$org = $orgRoot}Else {$org = $orgRoot | Get-UcsOrg -Name $tmp10 -LimitScope}Start-UcsTransaction$mo = $org | Add-UcsVnicTemplate -Name $tmp1 -Mtu $tmp2 -SwitchId $tmp3 -IdentPoolName $tmp4 `-QosPolicyName $tmp5 -TemplType $tmp8 -ModifyPresent$trash = $mo | Add-UcsVnicInterface -Name $tmp6 -DefaultNet $tmp9 -ModifyPresentComplete-UcsTransaction | Out-NullIf ($error.length -lt 1){Write-Log "Add VNIC template - Name=$tmp1 MTU=$tmp2 Fabric=$tmp3 MACPool=$tmp4 Type=$tmp9" "Normal"}Else{Write-Log "ERROR Add VNIC template - Name=$tmp1 MTU=$tmp2 Fabric=$tmp3 MACPool=$tmp4 Type=$tmp9" "Error"$errTag = $True}}}# vHBA Templates$present = $falseFor ($i=0; $i -lt $objectTable.length; $i++){$obj = $objectTable[$i]If ($obj[0] -eq 'VHBATemplate' -and $obj[1] -eq '1') {$present = $true; Break}}If ($Present){$ucsConfig.VSPEX.VHBATemplate | ForEach-Object {$_.Var} | ForEach-Object {$error.Clear()$tmp1 = $_.Name.trim()$tmp2 = $_.Descr$tmp3 = $_.Fabric.trim()$tmp3 = $tmp3.toupper()$tmp4 = $_.VSAN.trim()$tmp5 = $_.Type.trim()$tmp5 = $tmp5.tolower()$tmp6 = $_.WWNpool.trim()$tmp7 = $_.QoS.trim()$tmp8 = $_.Org.trim()If ($tmp8 -eq "root") {$org = $orgRoot}Else {$org = $orgRoot | Get-UcsOrg -Name $tmp8 -LimitScope}Start-UcsTransaction$mo = $org | Add-UcsVhbaTemplate -Name $tmp1 -Descr $tmp2 -SwitchId $tmp3 -TemplType $tmp5 -IdentPoolName $tmp6 `-MaxDataFieldSize 2048 -PinToGroupName "" -PolicyOwner "local" -QosPolicyName $tmp7 -StatsPolicyName "default" -ModifyPresent$trash = $mo | Add-UcsVhbaInterface -Name $tmp4 -ModifyPresentComplete-UcsTransaction | Out-NullIf ($error.length -lt 1){Write-Log "Add VHBA template - Name=$tmp1 Descr=$tmp2 Fabric=$tmp3 VSAN=$tmp4 Type=$tmp5 Pool=$tmp6 QoS=$tmp7" "Normal"}Else{Write-Log "ERROR Add VHBA template - Name=$tmp1 Descr=$tmp2 Fabric=$tmp3 VSAN=$tmp4 Type=$tmp5 Pool=$tmp6 QoS=$tmp7" "Error"$errTag = $True}}}# Boot Policies$present = $falseFor ($i=0; $i -lt $objectTable.length; $i++){$obj = $objectTable[$i]If ($obj[0] -eq 'BootPolicy' -and $obj[1] -eq '1') {$present = $true; Break}}If ($Present){$ucsConfig.VSPEX.BootPolicy | ForEach-Object {$_.PolicyName} | ForEach-Object {$error.Clear()$i = 0$tmp1 = $_$tmp2 = $_.Name.trim()$tmp3 = $_.Descr$tmp4 = $_.Org.trim()If ($tmp4 -eq "root") {$org = $orgRoot}Else {$org = $orgRoot | Get-UcsOrg -Name $tmp4 -LimitScope}$mo = $org | Add-UcsBootPolicy -Name $tmp2 -Descr $tmp3 -EnforceVnicName "yes" -PolicyOwner "local" `-RebootOnUpdate "no" -ModifyPresent$tmp1 | ForEach-Object {$_.Var} | ForEach-Object {$i++$tmp4 = $_.Type.trim()$tmp5 = $_.Device1.trim()$tmp6 = $_.Device2.trim()$tmp7 = $_.PrimaryFabricSwitch ($tmp4){Local{Switch ($tmp5){cdrom{$trash = $mo | Add-UcsLsbootVirtualMedia -Access "read-only" -Order $i -ModifyPresent}floppy{$trash = $mo | Add-UcsLsbootVirtualMedia -Access "read-write" -Order $i -ModifyPresent}localdisk{$mo_1 = $mo | Add-UcsLsbootStorage -Order $i -ModifyPresent$trash = $mo_1 | Add-UcsLsbootLocalStorage}}}VHBA{If ($tmp7 -eq 'A'){Start-UcsTransaction$mo_2 = $mo | Add-UcsLsbootStorage -Order $i -ModifyPresent$mo_2_1 = $mo_2 | Add-UcsLsbootSanImage -Type "primary" -VnicName $tmp5 -ModifyPresent$trash = $mo_2_1 | Add-UcsLsbootSanImagePath -Lun 0 -Type "primary" -Wwn $sanSPAprimary -ModifyPresent$trash = $mo_2_1 | Add-UcsLsbootSanImagePath -Lun 0 -Type "secondary" -Wwn $sanSPBprimary -ModifyPresent$mo_2_2 = $mo_2 | Add-UcsLsbootSanImage -Type "secondary" -VnicName $tmp6 -ModifyPresent$trash = $mo_2_2 | Add-UcsLsbootSanImagePath -Lun 0 -Type "primary" -Wwn $sanSPAsecondary -ModifyPresent$trash = $mo_2_2 | Add-UcsLsbootSanImagePath -Lun 0 -Type "secondary" -Wwn $sanSPBsecondary -ModifyPresentComplete-UcsTransaction | Out-Null}Else{Start-UcsTransaction$mo_2 = $mo | Add-UcsLsbootStorage -Order $i -ModifyPresent$mo_2_1 = $mo_2 | Add-UcsLsbootSanImage -Type "primary" -VnicName $tmp5 -ModifyPresent$trash = $mo_2_1 | Add-UcsLsbootSanImagePath -Lun 0 -Type "primary" -Wwn $sanSPBprimary -ModifyPresent$trash = $mo_2_1 | Add-UcsLsbootSanImagePath -Lun 0 -Type "secondary" -Wwn $sanSPAprimary -ModifyPresent$mo_2_2 = $mo_2 | Add-UcsLsbootSanImage -Type "secondary" -VnicName $tmp6 -ModifyPresent$trash = $mo_2_2 | Add-UcsLsbootSanImagePath -Lun 0 -Type "primary" -Wwn $sanSPBsecondary -ModifyPresent$trash = $mo_2_2 | Add-UcsLsbootSanImagePath -Lun 0 -Type "secondary" -Wwn $sanSPAsecondary -ModifyPresentComplete-UcsTransaction | Out-Null}}VNIC{$mo_1 = $mo | Add-UcsLsbootLan -Order $i -Prot "pxe" -ModifyPresent$trash = $mo_1 | Add-UcsLsbootLanImagePath -VnicName $tmp5 -BootIpPolicyName "" -ISCSIVnicName "" -ImgPolicyName "" -ImgSecPolicyName "" -ProvSrvPolicyName "" -Type "primary"}}If ($error.length -lt 1){Write-Log "Add boot policy - Name=$tmp2 Descr=$tmp3" "Normal"}Else{Write-Log "ERROR Add boot policy - Name=$tmp1 Descr=$tmp2" "Error"$errTag = $True}}}}# Service Profile Template$present = $falseFor ($i=0; $i -lt $objectTable.length; $i++){$obj = $objectTable[$i]If ($obj[0] -eq 'SPTemplate' -and $obj[1] -eq '1') {$present = $true; Break}}If ($Present){$ucsConfig.VSPEX.SPTemplate | ForEach-Object {$_.Template} | ForEach-Object {$error.Clear()$tmp1 = $_$tmp2 = $_.Name.trim()$tmp3 = $_.DescrStart-UcsTransaction$tmp4 = $_.BIOSProfileName.trim()$tmp5 = $_.BootPolicyName.trim()$tmp6 = $_.LocalDiskPolicy.trim()$tmp7 = $_.MgmtIPPool.trim()$tmp8 = "pooled"If ($tmp7 -eq "") {$tmp8 = "none"}$tmp9 = $_.PowerPolicyName.trim()$tmp10 = $_.ScrubPolicyName.trim()$tmp11 = $_.UUIDpool.trim()$tmp12 = $_.MaintPolicyName.trim()$tmp13 = $_.HostFwPolicyName.trim()$tmp14 = $_.MgmtAccessPolicyName.trim()$tmp15 = $_.MgmtFwPolicyName.trim()$tmp16 = $_.StatsPolicyName.trim()$tmp17 = $_.Org.trim()$tmp18 = $_.WwnnPoolName.trim()If ($tmp17 -eq "root") {$org = $orgRoot}Else {$org = $orgRoot | Get-UcsOrg -Name $tmp17 -LimitScope}$mo = $org | Add-UcsServiceProfile -Name $tmp2 -Type "updating-template" -ModifyPresent `-BiosProfileName $tmp4 -BootPolicyName $tmp5 -LocalDiskPolicyName $tmp6 -ExtIPPoolName $tmp7 -ExtIPState $tmp8 `-PowerPolicyName $tmp6 -ScrubPolicyName $tmp10 -IdentPoolName $tmp11 -MaintPolicyName $tmp12 `-HostFwPolicyName $tmp13 -MgmtAccessPolicyName $tmp14 -MgmtFwPolicyName $tmp15 -StatsPolicyName $tmp16$trash = $mo | Add-UcsVnicFcNode -Addr "pool-derived" -IdentPoolName $tmp18 -ModifyPresent$trash = $mo | Add-UcsServerPoolAssignment -ModifyPresent -Name "All-chassis" -Qualifier "all-chassis" -RestrictMigration "no"$trash = $mo | Set-UcsServerPower -State "admin-up" -Force# Process all the VNICs$tmp100 = $_.VNICs$i = 0$tmp100 | ForEach-Object {$_.Var} | ForEach-Object {$tmp4 = $_.Name.trim()$tmp5 = $_.Templ.trim()$i++$trash = $mo | Add-UcsVnic -Name $tmp4 -NwTemplName $tmp5 -AdaptorProfileName "Windows" -Order $i -ModifyPresent}# Process all the VHBAs$tmp100 = $_.VHBAs$tmp100 | ForEach-Object {$_.Var} | ForEach-Object {$tmp4 = $_.Name.trim()$tmp5 = $_.Templ.trim()$i++$mo_1 = $mo | Add-UcsVhba -Name $tmp4 -NwTemplName $tmp5 -AdaptorProfileName "Windows" -Order $i -ModifyPresent$trash = $mo_1 | Add-UcsVhbaInterface -Name "" -ModifyPresent}Complete-UcsTransaction | Out-NullIf ($error.length -lt 1){Write-Log "Add Service Profile Template - Name=$tmp2 Descr=$tmp3" "Normal"}Else{Write-Log "ERROR Service Profile Template - Name=$tmp1 Descr=$tmp2" "Error"$errTag = $True}}}# Create Service Profiles from Templates$present = $falseFor ($i=0; $i -lt $objectTable.length; $i++){$obj = $objectTable[$i]If ($obj[0] -eq 'ServiceProfile' -and $obj[1] -eq '1') {$present = $true; Break}}If ($Present){$ucsConfig.VSPEX.ServiceProfile | ForEach-Object {$_.Var} | ForEach-Object {$error.Clear()$tmp1 = $_.Name.trim()$tmp2 = $_.Templ.trim()$tmp3 = $_.Org.trim()If ($tmp3 -eq "root") {$org = $orgRoot}Else {$org = $orgRoot | Get-UcsOrg -Name $tmp3 -LimitScope}$mo = Get-UcsServiceProfile -Name $tmp2 -Org $orgIf ($mo -eq $null){Write-Log "ERROR Service Profile - invalid template name - Name=$tmp1 Templ=$tmp2 Org=$tmp3" "Error"$errTag = $True}Else{$trash = $mo | Add-UcsServiceProfileFromTemplate -NewName @($tmp1) -DestinationOrg $org}If ($error.length -lt 1){Write-Log "Add Service Profile - Name=$tmp1 Templ=$tmp2 Org=$tmp3" "Normal"}Else{Write-Log "ERROR Service Profile - Name=$tmp1 Templ=$tmp2 Org=$tmp3" "Error"$errTag = $True}}}# ------------------------------------------------------------------------------## Wrap up processing and close down## ------------------------------------------------------------------------------Disconnect-UcsIf ($errTag){Write-Host -ForegroundColor Red -BackgroundColor Black "`n`nErrors detected."}Set-Location $originalPath$endTime = Get-Date$elapsedTime = New-TimeSpan $startTime $endTimeIf ($toconsole){Write-Log "Elapsed time: $($elapsedTime.Hours):$($elapsedTime.Minutes):$($elapsedTime.Seconds)" "Normal"Write-Log "End of processing." "Normal"}Else{Write-Host -ForegroundColor Yellow -BackgroundColor Black "`n`n-----------------------------------------------------------`n"Write-Host "Elapsed time: $($elapsedTime.Hours):$($elapsedTime.Minutes):$($elapsedTime.Seconds)"Write-Host "End of processing."UcsConfig.xml
<?xml version="1.0" encoding="utf-8"?><!--UcsConfig Version=0.14-September-2013Created by Tim Cerlingtcerling@cisco.comTake care in editing this file. It is better to comment out the detail of anobject rather than deleting it if you do not want to enter values. This willretain the structure of the XML should you want to reuse it with more or differentvalues in the future. For example, if you have already defined Management IPaddresses and do not want to make any additional changes or additions, you coulddo something like this:<MgmtIP># <Pool Name='MgmtIP' Descr='Service Profile management IPs' ># <Order>sequential </Order># <Start>10.5.177.200 </Start># <End>10.5.177.249 </End># <Gateway>10.5.177.1 </Gateway># <PrimaryDNS>0.0.0.0 </PrimaryDNS># <SecondaryDNS>0.0.0.0 </SecondaryDNS># </Pool></MgmtIP>--><VSPEX><!-- UCSM IP address. Can be either FQDN or numeric. --><UCSMIP>10.29.130.100 </UCSMIP><!-- Timezone for this UCS domain --><TimeZone>America/Los_Angeles (Pacific Time) </TimeZone><!-- List of FQDN or IP addresses of NTP servers --><NTP><Var Name='1.ntp.esl.cisco.com' /><Var Name='2.ntp.esl.cisco.com' /></NTP><MgmtIP><Pool Name='MgmtIP' Descr='Service Profile management IPs' ><Order>sequential </Order><Start>10.5.177.200 </Start><End>10.5.177.249 </End><Gateway>10.5.177.1 </Gateway><PrimaryDNS>0.0.0.0 </PrimaryDNS><SecondaryDNS>0.0.0.0 </SecondaryDNS></Pool></MgmtIP><!-- Optional CallHome definitions. To make use of this, define InUse to equal 1 --><CallHome><InUse>0 </InUse> <!-- To define, InUse=1. To not define, InUse=0. --><SmtpSrv>smtprelay.customer.com </SmtpSrv><Address>123 Main Street, Anytown, CA 54321 </Address><ContactName>First Last </ContactName><ContactPhone>+15551234567 </ContactPhone><ContactEmail>contact@customer.com </ContactEmail><CustomerID>12345 </CustomerID><ContractID>12345 </ContractID><SiteID>12345 </SiteID><SmtpFrom>UCSstringCallHome@customer.com </SmtpFrom><SmtpRecipient>contact@customer.com </SmtpRecipient></CallHome><!-- Chassis Discovery - 1-link, 2-link, 4-link, 8-link, platform-max --><ChassisDiscovery>2-link </ChassisDiscovery><!-- Sub-Organizations to create. --><!-- NOTE: Only supports sub-organizations to root. --><SubOrg><Var Name='VSPEX' Descr='For all VSPEX work' /></SubOrg><!--SAN WWPN. Provide EMC SPA/SPB primary and secondary ports WWPNs. Used for creating boot policy. --><SANWWPN><SPAprimary>50:06:01:65:08:60:06:A1 </SPAprimary><SPAsecondary>50:06:01:64:08:60:06:A1 </SPAsecondary><SPBprimary>50:06:01:6D:08:60:06:A1 </SPBprimary><SPBsecondary>50:06:01:6C:08:60:06:A1 </SPBsecondary></SANWWPN><!-- Associate QoS with custom names --><!-- NOTE: assigning a value forces an MTU of 9000 --><QoS><Platinum>LiveMigration </Platinum><Gold>iSCSI </Gold><Silver> </Silver><Bronze> </Bronze></QoS><!-- Power Control Policy --><PowerPolicy><Var Name='default' Priority='no-cap' /><Var Name='Cap_1' Priority='1' /><Var Name='Cap_2' Priority='2' /><Var Name='Cap_3' Priority='3' /><Var Name='Cap_4' Priority='4' /><Var Name='Cap_5' Priority='5' /><Var Name='Cap_6' Priority='6' /><Var Name='Cap_7' Priority='7' /><Var Name='Cap_8' Priority='8' /><Var Name='Cap_9' Priority='9' /><Var Name='Cap_10' Priority='10' /><Var Name='NoCap' Priority='no-cap' /></PowerPolicy><!-- Scrub Policies --><ScrubPolicy><Var Name='NoScrub' Descr='Do not scrub' DiskScrub='no' BiosScrub='no' /><Var Name='DiskScrub' Descr='Scrub disk' DiskScrub='yes' BiosScrub='no' /><Var Name='BiosScrub' Descr='Scrub Bios' DiskScrub='no' BiosScrub='yes' /><Var Name='AllScrub' Descr='Scrub disk and Bios' DiskScrub='yes' BiosScrub='yes' /></ScrubPolicy><!-- Maintenance policies --><MaintenancePolicy><Var Name='Immediate' Descr='Immediately reboot on profile change' Policy='immediate' /><Var Name='UserAck' Descr='User acknowledge reboot on profile change' Policy='user-ack' /><Var Name='Timer-auto' Descr='Timer reboot on default schedule' Policy='timer-automatic' /></MaintenancePolicy><!-- Local Disk Policy --><DiskPolicy><Var Name='AnyConfiguration' Mode='any-configuration' Descr='Any Disk Configuration' Protect='yes' /><Var Name='NoLocal' Mode='no-local-storage' Descr='Ignore local storage' Protect='yes' /><Var Name='NoRAID' Mode='no-raid' Descr='No RAID storage' Protect='yes' /><Var Name='RAID0' Mode='raid-striped' Descr='RAID 0 Striped' Protect='yes' /><Var Name='RAID1' Mode='raid-mirrored' Descr='RAID 1 Mirrored' Protect='yes' /><Var Name='RAID10' Mode='raid-mirrored-striped' Descr='RAID 10 Mirrored and Striped' Protect='yes' /><Var Name='RAID5' Mode='raid-striped-parity' Descr='RAID 5 Striped Parity' Protect='yes' /><Var Name='RAID6' Mode='raid-striped-dual-parity' Descr='RAID 6 Striped Dual Parity' Protect='yes' /></DiskPolicy><!-- BIOS Policy. Currently only No Quiet Boot is programmed. --><!-- NOTE: Do not change this entry. Use UCSM to create different BIOS policies --><BIOSPolicy><Var Name='NoQuietBoot' Descr= 'No quiet boot' VpQuietBoot='disabled' /></BIOSPolicy><!-- vNIC/vHBA Placement Policy. --><!-- NOTE: Do not change this entry. Use UCSM to create different placement policies --><!-- If these entries get changed, the logic will also need to be changed to reflect --><PlacementPolicy><Var Name='AssignedOnly' SlotMapping='round-robin' Selection='assigned-only' /><Var Name='ExcludeDynamic' SlotMapping='round-robin' Selection='exclude-dynamic' /><Var Name='ExcludeUnassign' SlotMapping='round-robin' Selection='exclude-unassigned' /></PlacementPolicy><!-- FI port definitions. Assumed FI-A and FI-B are configured identically. Recommended to include UsrLbl.Defining role as '' causes no change to the configurationLast four variables only applicable to Appliance role for iSCSI and SMB.NOTE: Currently only supports 6248UPNOTE - NOTE - NOTE FC ports are special. They are defined in the FCslot1 and FCslot2 objects, not here.See description for FCslot1 and FCslot2 objects.--><FI><Var SlotID='1' PortID='1' Role='Server' UsrLbl='Blade Server' VLAN='n/a' Native='n/a' Mode='n/a' QoS='n/a' /><Var SlotID='1' PortID='2' Role='Server' UsrLbl='Blade Server' VLAN='n/a' Native='n/a' Mode='n/a' QoS='n/a' /><Var SlotID='1' PortID='3' Role='Server' UsrLbl='Blade Server' VLAN='n/a' Native='n/a' Mode='n/a' QoS='n/a' /><Var SlotID='1' PortID='4' Role='Server' UsrLbl='Blade Server' VLAN='n/a' Native='n/a' Mode='n/a' QoS='n/a' /><Var SlotID='1' PortID='5' Role='' UsrLbl='' VLAN='n/a' Native='n/a' Mode='n/a' QoS='n/a' /><Var SlotID='1' PortID='6' Role='' UsrLbl='' VLAN='n/a' Native='n/a' Mode='n/a' QoS='n/a' /><Var SlotID='1' PortID='7' Role='' UsrLbl='' VLAN='n/a' Native='n/a' Mode='n/a' QoS='n/a' /><Var SlotID='1' PortID='8' Role='' UsrLbl='' VLAN='n/a' Native='n/a' Mode='n/a' QoS='n/a' /><Var SlotID='1' PortID='9' Role='' UsrLbl='' VLAN='n/a' Native='n/a' Mode='n/a' QoS='n/a' /><Var SlotID='1' PortID='10' Role='' UsrLbl='' VLAN='n/a' Native='n/a' Mode='n/a' QoS='n/a' /><Var SlotID='1' PortID='11' Role='' UsrLbl='' VLAN='n/a' Native='n/a' Mode='n/a' QoS='n/a' /><Var SlotID='1' PortID='12' Role='' UsrLbl='' VLAN='n/a' Native='n/a' Mode='n/a' QoS='n/a' /><Var SlotID='1' PortID='13' Role='' UsrLbl='' VLAN='n/a' Native='n/a' Mode='n/a' QoS='n/a' /><Var SlotID='1' PortID='14' Role='' UsrLbl='' VLAN='n/a' Native='n/a' Mode='n/a' QoS='n/a' /><Var SlotID='1' PortID='15' Role='' UsrLbl='' VLAN='n/a' Native='n/a' Mode='n/a' QoS='n/a' /><Var SlotID='1' PortID='16' Role='' UsrLbl='' VLAN='n/a' Native='n/a' Mode='n/a' QoS='n/a' /><Var SlotID='1' PortID='17' Role='Uplink' UsrLbl='Uplink Port' VLAN='n/a' Native='n/a' Mode='n/a' QoS='n/a' /><Var SlotID='1' PortID='18' Role='Uplink' UsrLbl='Uplink Port' VLAN='n/a' Native='n/a' Mode='n/a' QoS='n/a' /><Var SlotID='1' PortID='19' Role='' UsrLbl='' VLAN='n/a' Native='n/a' Mode='n/a' QoS='n/a' /><Var SlotID='1' PortID='20' Role='' UsrLbl='' VLAN='n/a' Native='n/a' Mode='n/a' QoS='n/a' /><Var SlotID='1' PortID='21' Role='' UsrLbl='' VLAN='n/a' Native='n/a' Mode='n/a' QoS='n/a' /><Var SlotID='1' PortID='22' Role='' UsrLbl='' VLAN='n/a' Native='n/a' Mode='n/a' QoS='n/a' /><Var SlotID='1' PortID='23' Role='Appliance' UsrLbl='10 GE SMB' VLAN='SMB' Native='no' Mode='Access' QoS='gold' /><Var SlotID='1' PortID='24' Role='Appliance' UsrLbl='10 GE SMB' VLAN='SMB' Native='no' Mode='Access' QoS='gold' /><Var SlotID='1' PortID='25' Role='' UsrLbl='' VLAN='n/a' Native='n/a' Mode='n/a' QoS='n/a' /><Var SlotID='1' PortID='26' Role='' UsrLbl='' VLAN='n/a' Native='n/a' Mode='n/a' QoS='n/a' /><Var SlotID='1' PortID='27' Role='' UsrLbl='' VLAN='' Native='no' Mode='Access' QoS='n/a' /><Var SlotID='1' PortID='28' Role='' UsrLbl='' VLAN='' Native='no' Mode='Access' QoS='n/a' /><Var SlotID='1' PortID='29' Role='' UsrLbl='' VLAN='n/a' Native='n/a' Mode='n/a' QoS='n/a' /><Var SlotID='1' PortID='30' Role='' UsrLbl='' VLAN='n/a' Native='n/a' Mode='n/a' QoS='n/a' /><Var SlotID='1' PortID='31' Role='' UsrLbl='' VLAN='n/a' Native='n/a' Mode='n/a' QoS='n/a' /><Var SlotID='1' PortID='32' Role='' UsrLbl='' VLAN='n/a' Native='n/a' Mode='n/a' QoS='n/a' /><Var SlotID='2' PortID='1' Role='' UsrLbl='' VLAN='n/a' Native='n/a' Mode='n/a' QoS='n/a' /><Var SlotID='2' PortID='2' Role='' UsrLbl='' VLAN='n/a' Native='n/a' Mode='n/a' QoS='n/a' /><Var SlotID='2' PortID='3' Role='' UsrLbl='' VLAN='n/a' Native='n/a' Mode='n/a' QoS='n/a' /><Var SlotID='2' PortID='4' Role='' UsrLbl='' VLAN='n/a' Native='n/a' Mode='n/a' QoS='n/a' /><Var SlotID='2' PortID='5' Role='' UsrLbl='' VLAN='n/a' Native='n/a' Mode='n/a' QoS='n/a' /><Var SlotID='2' PortID='6' Role='' UsrLbl='' VLAN='n/a' Native='n/a' Mode='n/a' QoS='n/a' /><Var SlotID='2' PortID='7' Role='' UsrLbl='' VLAN='n/a' Native='n/a' Mode='n/a' QoS='n/a' /><Var SlotID='2' PortID='8' Role='' UsrLbl='' VLAN='n/a' Native='n/a' Mode='n/a' QoS='n/a' /><Var SlotID='2' PortID='9' Role='' UsrLbl='' VLAN='n/a' Native='n/a' Mode='n/a' QoS='n/a' /><Var SlotID='2' PortID='10' Role='' UsrLbl='' VLAN='n/a' Native='n/a' Mode='n/a' QoS='n/a' /><Var SlotID='2' PortID='11' Role='' UsrLbl='' VLAN='n/a' Native='n/a' Mode='n/a' QoS='n/a' /><Var SlotID='2' PortID='12' Role='' UsrLbl='' VLAN='n/a' Native='n/a' Mode='n/a' QoS='n/a' /><Var SlotID='2' PortID='13' Role='' UsrLbl='' VLAN='n/a' Native='n/a' Mode='n/a' QoS='n/a' /><Var SlotID='2' PortID='14' Role='' UsrLbl='' VLAN='n/a' Native='n/a' Mode='n/a' QoS='n/a' /><Var SlotID='2' PortID='15' Role='' UsrLbl='' VLAN='n/a' Native='n/a' Mode='n/a' QoS='n/a' /><Var SlotID='2' PortID='16' Role='' UsrLbl='' VLAN='n/a' Native='n/a' Mode='n/a' QoS='n/a' /></FI><!-- Fibre Channel port defintions. Assumes FC ports configured on same ports on each FI.The PortID value is the port number for the first port to be defined as FC. All following portswill be included as FC ports. FCslot1 is for Module 1. FCslot2 is for expansion module 2 and itassumes that it is a unified ports expansion module.--><FCslot1 PortID='' UsrLbl='' /><FCslot2 PortID='' UsrLbl='' /><!-- Port Channel definition. Assumes PC configured on same ports on each FI --><PC><AName>VPC201 </AName><APortID>201 </APortID><BName>VPC202 </BName><BPortID>202 </BPortID><Slot>1 </Slot><Port1>17 </Port1><Port2>18 </Port2></PC><!-- Various pools. Multiple pools of same type can be defined. --><Pools><Var Type='MAC' Name='VSPEX-99-MAC' From='00:25:B5:99:00:00' To='00:25:B5:99:00:FF' Order='sequential' Org='VSPEX' Descr='' /><Var Type='UUID' Name='VSPEX-99-UUID' From='0099-000000000001' To='0099-000000000040' Order='sequential' Org='VSPEX' Descr='' /><Var Type='WWNN' Name='VSPEX-99-WWNN' From='20:00:00:25:B5:99:00:00' To='20:00:00:25:B5:99:00:3F' Order='sequential' Org='VSPEX' Descr='' /><Var Type='WWPN' Name='VSPEX-99-WWPN' From='20:00:00:25:B5:99:00:40' To='20:00:00:25:B5:99:00:FF' Order='sequential' Org='VSPEX' Descr='' /></Pools><!-- VLAN definitions --><!-- Use ATag for common configuration VLAN tag --><!-- Fabric can be defined as Common, Diff, FabA, or FabB --><VLANs><Var Name='Mgmt' Fabric='Common' ATag='1' BTag='' DefaultNet="yes" /><Var Name='VMaccess' Fabric='Common' ATag='10' BTag='' DefaultNet="no" /><Var Name='CSV' Fabric='Common' ATag='12' BTag='' DefaultNet="no" /><Var Name='LiveMigration' Fabric='Common' ATag='11' BTag='' DefaultNet="no" /><Var Name='ClusComm' Fabric='Common' ATag='13' BTag='' DefaultNet="no" /><Var Name='iSCSI' Fabric='Diff' ATag='18' BTag='19' DefaultNet="no" /><Var Name='SMB' Fabric='Diff' ATag='16' BTag='17' DefaultNet="no" /><Var Name='VEM' Fabric='Common' ATag='100' BTag='' DefaultNet="no" /></VLANs><!-- VNIC template definitions --><VNICtemplate><Var Name='Mgmt' MTU='1500' Fabric='A-B' MACpool='VSPEX-99-MAC' Qos='' VLAN='Mgmt' Order='1' Type='updating-template' Native='yes' Org='root' /><Var Name='CSV' MTU='9000' Fabric='A-B' MACpool='VSPEX-99-MAC' Qos='' VLAN='CSV' Order='2' Type='updating-template' Native='yes' Org='root' /><Var Name='LiveMigration' MTU='9000' Fabric='A-B' MACpool='VSPEX-99-MAC' Qos='LiveMigration' VLAN='LiveMigration' Order='3' Type='updating-template' Native='yes' Org='root' /><Var Name='VMaccess' MTU='1500' Fabric='B-A' MACpool='VSPEX-99-MAC' Qos='' VLAN='VMaccess' Order='4' Type='updating-template' Native='no' Org='root' /><Var Name='ClusComm' MTU='1500' Fabric='B-A' MACpool='VSPEX-99-MAC' Qos='' VLAN='ClusComm' Order='5' Type='updating-template' Native='no' Org='root' /><Var Name='iSCSI-A' MTU='9000' Fabric='A-B' MACpool='VSPEX-99-MAC' Qos='iSCSI' VLAN='iSCSI' Order='6' Type='updating-template' Native='no' Org='root' /><Var Name='iSCSI-B' MTU='9000' Fabric='B-A' MACpool='VSPEX-99-MAC' Qos='iSCSI' VLAN='iSCSI' Order='7' Type='updating-template' Native='no' Org='root' /><Var Name='SMB-A' MTU='9000' Fabric='A-B' MACpool='VSPEX-99-MAC' Qos='iSCSI' VLAN='SMB' Order='8' Type='updating-template' Native='no' Org='root' /><Var Name='SMB-B' MTU='9000' Fabric='B-A' MACpool='VSPEX-99-MAC' Qos='iSCSI' VLAN='SMB' Order='9' Type='updating-template' Native='no' Org='root' /><Var Name='VEM' MTU='1500' Fabric='B-A' MACpool='VSPEX-99-MAC' Qos='' VLAN='VEM' Order='10' Type='updating-template' Native='no' Org='root' /></VNICtemplate><!-- Virtual HBA templates --><VHBAtemplate><Var Name='VSPEX-99-FabA' Descr='Fabric A vHBA' Fabric='A' VSAN='default' Type='updating-template' WWNpool='VSPEX-99-WWPN' Qos='' Org='VSPEX' /><Var Name='VSPEX-99-FabB' Descr='Fabric B vHBA' Fabric='B' VSAN='default' Type='updating-template' WWNpool='VSPEX-99-WWPN' Qos='' Org='VSPEX' /></VHBAtemplate><!-- Boot Policy --><!-- Order of Vars specifies order of devices in boot policy --><!-- Type Local can have device1 equal to cdrom, localdisk, or floppy --><BootPolicy><PolicyName Name='VSPEX-SAN-A-Boot' Descr='Fibre Channel Boot Fabric A' Org='VSPEX' ><Var Type='Local' Device1='cdrom' Device2='' PrimaryFabric='' /><Var Type='VHBA' Device1='FabChn-A' Device2='FabChn-B' PrimaryFabric='A' /></PolicyName><PolicyName Name='VSPEX-SAN-B-Boot' Descr='Fibre Channel Boot Fabric B' Org='VSPEX' ><Var Type='Local' Device1='cdrom' Device2='' PrimaryFabric='' /><Var Type='VHBA' Device1='FabChn-B' Device2='FabChn-A' PrimaryFabric='B' /></PolicyName></BootPolicy><!-- Service Profile Template --><SPTemplate><Template><Name>VSPEX-99-BootA </Name><Descr>VSPEX-99 Boot from SAN Fabric A </Descr><BIOSProfileName> </BIOSProfileName><BootPolicyName>VSPEX-SAN-A-Boot </BootPolicyName><LocalDiskPolicy>NoLocal </LocalDiskPolicy><MgmtIPpool>MgmtIP </MgmtIPpool><PowerPolicyName>NoCap </PowerPolicyName><ScrubPolicyName>NoScrub </ScrubPolicyName><UUIDpool>VSPEX-99-UUID </UUIDpool><MaintPolicyName>UserAck </MaintPolicyName><HostFwPolicyName> </HostFwPolicyName><MgmtAccessPolicyName> </MgmtAccessPolicyName><MgmtFwPolicyName> </MgmtFwPolicyName><StatsPolicyName>default </StatsPolicyName><Org>VSPEX </Org><WwnnPoolName>VSPEX-99-WWNN </WwnnPoolName><VNICs><Var Name='Mgmt' Templ='Mgmt' /><Var Name='LiveMigration' Templ='LiveMigration' /><Var Name='CSV' Templ='CSV' /><Var Name='VMaccess' Templ='VMaccess' /><Var Name='ClusComm' Templ='ClusComm' /><Var Name='VEM' Templ='VEM' /></VNICs><VHBAs><Var Name='FabChn-A' Templ='VSPEX-99-FabA'/> <!-- Name must match value of Devicex in boot policy --><Var Name='FabChn-B' Templ='VSPEX-99-FabB'/></VHBAs></Template><Template><Name>VSPEX-99-BootB </Name><Descr>Boot from SAN Fabric B </Descr><BIOSProfileName> </BIOSProfileName><BootPolicyName>VSPEX-SAN-B-Boot </BootPolicyName><LocalDiskPolicy>NoLocal </LocalDiskPolicy><MgmtIPpool>MgmtIP </MgmtIPpool><PowerPolicyName>NoCap </PowerPolicyName><ScrubPolicyName>NoScrub </ScrubPolicyName><UUIDpool>VSPEX-99-UUID </UUIDpool><MaintPolicyName>UserAck </MaintPolicyName><HostFwPolicyName> </HostFwPolicyName><MgmtAccessPolicyName> </MgmtAccessPolicyName><MgmtFwPolicyName> </MgmtFwPolicyName><StatsPolicyName>SPT-Test </StatsPolicyName><Org>VSPEX </Org><WwnnPoolName>VSPEX-99-WWNN </WwnnPoolName><VNICs><Var Name='Mgmt' Templ='Mgmt' /><Var Name='LiveMigration' Templ='LiveMigration' /><Var Name='CSV' Templ='CSV' /><Var Name='VMaccess' Templ='VMaccess' /><Var Name='ClusComm' Templ='ClusComm' /><Var Name='VEM' Templ='VEM' /></VNICs><VHBAs><Var Name='FabChn-B' Templ='VSPEX-99-FabB' />X<Var Name='FabChn-A' Templ='VSPEX-99-FabA' /></VHBAs></Template></SPTemplate><ServiceProfile><Var Name='VSPEX-01' Templ='VSPEX-99-BootA' Org='VSPEX' /><Var Name='VSPEX-02' Templ='VSPEX-99-BootB' Org='VSPEX' /><Var Name='VSPEX-03' Templ='VSPEX-99-BootA' Org='VSPEX' /><Var Name='VSPEX-04' Templ='VSPEX-99-BootB' Org='VSPEX' /><Var Name='VSPEX-05' Templ='VSPEX-99-BootA' Org='VSPEX' /><Var Name='VSPEX-06' Templ='VSPEX-99-BootB' Org='VSPEX' /></ServiceProfile></VSPEX>Add-UcsHyperVFeatures.ps1
#Write-Host ""Write-Host "Install the MPIO and Failover Clustering features and the Hyper-V role"Write-Host ""Write-Host -ForegroundColor Yellow "Installing Hyper-V will cause the system to reboot"Write-Host ""$srvr = Read-Host "Enter computer name of server on which to install MPIO"Write-Host ""Write-Host "Installing the MPIO feature"Install-WindowsFeature -Name Multipath-IO -ComputerName $srvr -IncludeManagementToolsInvoke-Command -ComputerName $srvr -ScriptBlock `{Write-Host "Add new vendor and product IDs for MPIO"# Values for EMC VNX$trash = New-MSDSMSupportedHw -VendorId "DGC" -ProductId "LUNZ"$trash = New-MSDSMSupportedHw -VendorId "DGC" -ProductId "VDISK"$trash = New-MSDSMSupportedHw -VendorId "DGC" -ProductId "RAID 0"$trash = New-MSDSMSupportedHw -VendorId "DGC" -ProductId "RAID 1"$trash = New-MSDSMSupportedHw -VendorId "DGC" -ProductId "RAID 10"$trash = New-MSDSMSupportedHw -VendorId "DGC" -ProductId "RAID 5"$trash = New-MSDSMSupportedHw -VendorId "DGC" -ProductId "VRAID"Write-Host "List of configured vendor and product IDs"Get-MSDSMSupportedHW | Select VendorId, ProductId | ft}Write-Host ""Write-Host "Installing the Failover Clustering feature"Install-WindowsFeature -Name Failover-Clustering -ComputerName $Srvr -IncludeManagementToolsWrite-Host ""Write-Host "Installing the Hyper-V role"Install-WindowsFeature -Name Hyper-V -ComputerName $Srvr -IncludeManagementTools -RestartSet-UcsHyperVAdapters.ps1
# Note that the $ucsIP variable needs to be changed to reflect customer environment$ucsIP = "192.168.14.100"if ((Get-Module | Where {$_.Name -ilike "CiscoUcsPS"}).Name -ine "CiscoUcsPS"){Write-Host "Loading Module: Cisco UCS PowerTool Module"Import-Module CiscoUcsPs}$trash = set-ucspowertoolconfiguration -supportmultipledefaultucs $false# Connect to UCSM$ucsCreds = Get-Credential$UCSMHandle = Connect-Ucs $UcsIP $ucsCredsWrite-Host ""Write-Host -ForegroundColor Yellow "Entered name of host must match case of service profile name"$srvr = Read-Host "Enter the name of the Hyper-V host to target"Write-Host ""[int]$hostNum = Read-Host "Enter a numeric value between 1-254 to use as the host number"Write-Host ""Write-Host "Not all NICs should have their IP address altered, e.g. Mgmt and iSCSI boot NICs"$in = Read-Host "Enter a comma separated list of NICs to ignore"$in2 = $in -replace " ",""$ignoreNic = $in2 -split ","Write-Host ""$org = Read-Host "Enter Sub-Organization name of Service Profile, or 'root'"If ($org.Length -eq 0) {$org = "root"}$orgLevel = Get-UcsOrg -Name $org$svcProfile = $orgLevel.DN + "/" + $srvrWrite-Host ""# Retrieve table of NICs from the UCS Profile$ducsVnics = Get-UcsVnic -ServiceProfile $svcProfileIf ($ducsVnics.length -eq 0){Write-Host -ForegroundColor Red "Invalid Service Profile name - $svcProfile"Disconnect-UcsExit}# This is a special check to remove the dyanmic virtual function vNICs created by having VM-FEX defined$ucsVnics = @()Foreach ($d in $ducsVnics){If ($d.addr -ne "derived"){$ucsVnics +=, $d}}Write-Host "$srvr has the following vNICs"$ucsVnics.Name$vlans = Get-UcsLanCloud | Get-UcsVlan | Select Name, Id$assignedIP = @()# Rename the NICs on the server to match the NIC name of the service profile# If NIC is not one entered to be ignored, change the IP addressForEach ($u in $UcsVnics){$adapterConfig = (Get-WMIobject Win32_NetworkAdapterConfiguration -namespace "root\CIMV2" -computername $srvr | `Where-Object {$_.MACaddress -eq $u.Addr})$hostNic = (Get-WMIobject Win32_NetworkAdapter -computername $srvr | Where-Object {$_.Index -eq $adapterConfig.Index})If ($hostNic.NetconnectionID -ne $u.name){$tmp = $hostNic.NetconnectionID ; $tmp_1 = $u.NameWrite-Host "Changing NIC $tmp to be named $tmp_1"$hostNic.NetconnectionID=$u.Name$trash = $hostNic.Put()}$check = $FALSEForeach ($ig in $ignoreNic){If ($ig -eq $u.Name) {$check = $TRUE}}If (!$check){Foreach ($v in $vlans){If ($v.Name -eq $u.name){$adapterConfig.DHCPenabled = $False$adapterConfig.SetDynamicDNSRegistration($false) | out-null$newIP = "192.168." + $v.Id + "." + $hostNumForeach ($aIP in $assignedIP){If ($newIP -eq $aIP){$octets = ($newIP.split("."))[int]$lastOctet = $octets[3]$lastOctet++$newip = $octets[0] + "." + $octets[1] + "." + $octets[2] + "." + $lastOctet}}$adapterConfig.enablestatic($newIP,"255.255.255.0") | out-null$assignedIP +=, $newIPWrite-Host $u.Name "new IP > $newIP"}}}}Set-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.## To find rule names# Get a list of possible groups# Get-NetFirewallRule | Select DisplayGroup -Unique | Sort DisplayGroup## To list the applicable rules that may be set.# Get-NetFirewallRule | Where { $_.DisplayGroup -Eq "Remote Volume Management"} | Format-Table Name# Ensure Server Manager remoting is enabledConfigure-SMRemoting.exe -Enable# Set some firewall rules# Enable ping requests in and outSet-NetFirewallRule -Name "FPS-ICMP4-ERQ-In" -Enabled True -Profile AnySet-NetFirewallRule -Name "FPS-ICMP6-ERQ-In" -Enabled True -Profile AnySet-NetFirewallRule -Name "FPS-ICMP4-ERQ-Out" -Enabled True -Profile AnySet-NetFirewallRule -Name "FPS-ICMP6-ERQ-Out" -Enabled True -Profile Any# Enable remote volume 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 True -Profile AnySet-NetFirewallRule -Name "RVM-VDSLDR-In-TCP" -Enabled True -Profile AnySet-NetFirewallRule -Name "RVM-RPCSS-In-TCP" -Enabled True -Profile Any# Enable DCOM management requests inSet-NetFirewallRule -Name "ComPlusNetworkAccess-DCOM-In" -Enabled True -Profile Any# Enable remote service managementSet-NetFirewallRule -Name "RemoteSvcAdmin-In-TCP" -Enabled True -Profile AnySet-NetFirewallRule -Name "RemoteSvcAdmin-NP-In-TCP" -Enabled True -Profile AnySet-NetFirewallRule -Name "RemoteSvcAdmin-RPCSS-In-TCP" -Enabled True -Profile Any# Enable Remote Event Log ManagementSet-NetFirewallRule -Name "RemoteEventLogSvc-In-TCP" -Enabled True -Profile AnySet-NetFirewallRule -Name "RemoteEventLogSvc-NP-In-TCP" -Enabled True -Profile AnySet-NetFirewallRule -Name "RemoteEventLogSvc-RPCSS-In-TCP" -Enabled True -Profile Any# Enable Remote Scheduled Tasks ManagementSet-NetFirewallRule -Name "RemoteTask-In-TCP" -Enabled True -Profile AnySet-NetFirewallRule -Name "RemoteTask-RPCSS-In-TCP" -Enabled True -Profile Any# Enable Windows Firewall Remote ManagementSet-NetFirewallRule -Name "RemoteFwAdmin-In-TCP" -Enabled True -Profile AnySet-NetFirewallRule -Name "RemoteFwAdmin-RPCSS-In-TCP" -Enabled True -Profile Any# Enable WMI management requests inSet-NetFirewallRule -Name "WMI-WINMGMT-In-TCP" -Enabled True -Profile Any# Enable Remote ShutdownSet-NetFirewallRule -Name "Wininit-Shutdown-In-Rule-TCP-RPC" -Enabled True -Profile Any# 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(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-Null# Enable Remote Desktop rules for all profilesSet-NetfirewallRule -Name "RemoteDesktop-UserMode-In-TCP" -Enabled True -Profile AnySet-NetfirewallRule -Name "RemoteDesktop-UserMode-In-UDP" -Enabled True -Profile AnyEMC Sample Scripts
Master_Boot_Lun.xml
<StorageParams><Array>VSPEX-VNX5400</Array><UCSAddress>10.5.177.10</UCSAddress><Servers><Server><ServerName>VSPEX-01</ServerName><IPAddress>10.29.130.21</IPAddress><luns><label> Master_Boot_2012R2</label><pool>VSPEX_Pool_01_R5</pool><size>50GB</size></luns></Server></Servers></StorageParams>Storage_Luns.xml
<!-- This configuration file is used by the following three scripts:PrepMasterBoot-AddViaWWPN.ps1ProcessStorageRequests.ps1PostClone_AddViaWWPN.ps1This is just a sample. It must be altered to reflect the customer configuration.Create <Server> objects for each physical blade, plus one extra for the MasterBoot image LUN. It is recommended to alternate the pool used for creating theLUNs so half the servers boot from one pool and the other half boot from theOther.--><StorageParams><Array> VNX5400</Array><UCSAddress>10.5.177.10</UCSAddress><Servers><Server><ServerName>VSPEX-01</ServerName><IPAddress>10.29.130.31</IPAddress><luns><label>VSPEX-01</label><pool>VSPEX_Pool_1</pool><size>50GB</size></luns></Server><Server><ServerName>VSPEX-02</ServerName><IPAddress>10.29.130.32</IPAddress><luns><label>VSPEX-02</label><pool> VSPEX_Pool_2</pool><size>50GB</size></luns></Server><Server><ServerName>VSPEX-03</ServerName><IPAddress>10.29.130.33</IPAddress><luns><label>VSPEX-03</label><pool> VSPEX_Pool_1</pool><size>50GB</size></luns></Server><Server><ServerName>VSPEX-04</ServerName><IPAddress>10.29.130.34</IPAddress><luns><label>VSPEX-04</label><pool> VSPEX_Pool_2</pool><size>50GB</size></luns></Server><Server><ServerName>VSPEX-05</ServerName><IPAddress>10.29.130.35</IPAddress><luns><label>VSPEX-05</label><pool> VSPEX_Pool_1</pool><size>50GB</size></luns></Server><Server><ServerName>VSPEX-06</ServerName><IPAddress>10.29.130.36</IPAddress><luns><label>VSPEX-06</label><pool> VSPEX_Pool_2</pool><size>50GB</size></luns></Server></Servers></StorageParams>PrepMasterBoot-AddViaWWPN.ps1
#----------------------------------------------------------------------------------# Filename: PrepMasterBoot_AddViaWWPN.ps1# Description: Set up Cisco UCS ServiceProfile to do Boot from SAN from VNX5400# Input file: Master_Boot_Lun.xml#----------------------------------------------------------------------------------## Uses an XML file with the following schema. This same schema is used by# - PrepMastBoot-AddViaWWPN.ps1# - Process Storage Requests.ps1# - PostClone_AddViaWWPN.ps1## <StorageParams># <Array>VNX5400</Array># <UCSAddress>10.5.177.10</UCSAddress># <Servers># <Server># <ServerName>VSPEX-01</ServerName># <IPAddress>192.168.10.31</IPAddress># <luns># <label>Master_Boot_2012R2</label># <pool>VSPEX_Pool_1</pool># <size>50GB</size># </luns># </Server># </Servers># </StorageParams>##----------------------------------------------------------------------------------$global:rootPath = Split-Path -Parent $MyInvocation.MyCommand.Path$myxmlfile = $global:rootPath + "\Master_Boot_Lun.xml"Function ReadStorageConfig ([String]$filename) {$xmlConfigFile = [xml](Get-Content $filename )$global:StorageConfig = $xmlConfigFile.SelectSingleNode( '/StorageParams' )}ReadStorageConfig $myxmlfileImport-Module CiscoUcsPSImport-Module ESIPSToolkitFunction LUNExists {param ($TGTLUN)$Val = Get-EmcLUN $TGTLUN -Silentif ($Val -eq $null) {return $false} else {return $true}}Function reghostexists {param ($tgthost)$val = Get-EmcStorageRegisteredHost $tgthostIf ($Val -eq $null) {Return $false}Else {Return $true}}$StorageArray = Get-EMCStorageSystem -ID $global:StorageConfig.Array -SilentIf ($StorageArray -eq $null){Write-Host "ERROR: Array" $Array "is not known or registered under that name."Exit 1}Update-EmcSystem $StorageArray# Prompt user for connection to UCS environmentIf ($UCS -eq $null) {$UCS = Connect-Ucs $global:StorageConfig.UCSAddress}ForEach ($entry in $global:StorageConfig.Servers.Server){ForEach ($lun in $entry.luns){Write-Host $entry.Servername, $lun.label}}# Check for pre-existing LUNIf (LUNExists $global:StorageConfig.Servers.Server.luns.label){ # We present the LUN$MyServiceProfile = Get-UcsServiceProfile | where {$_.Name -eq $global:StorageConfig.Servers.Server.ServerName}If ($MyServiceProfile -eq $null){Write-Host "ERROR: Cannot find ServiceProfile" $global:StorageConfig.Servers.Server.ServerNameexit 1}Else{## Extract out the WWPN initiator information for the Service Profile#$MyvHBAs = Get-UcsVhba -ServiceProfile $MyServiceProfile## Get the Gold Master that we plan to use#$MasterLUN = get-EMCLun -ID $global:StorageConfig.Servers.Server.luns.label -BlockStorageSystem $StorageArray## Add all the initiators from the Service Profile to the Storage Group on the VNX#ForEach ($vHBA in $MyvHBAs){$HostRegistration = $vHBA.NodeAddr + ":" + $vHBA.AddrIf (reghostexists $global:StorageConfig.Servers.Server.ServerName){$rg=get-emcstorageregisteredhost $global:StorageConfig.Servers.Server.ServerNameWrite-Host "New Init" $HostRegistrationNew-EmcStorageRegisteredInitiator -registeredhost $rg -InitiatorIds $HostRegistration}Else{Write-Host "New Host" $HostRegistrationNew-EMCStorageRegisteredHost -StorageSystem $StorageArray -HostName $global:StorageConfig.Servers.Server.ServerName -IpAddress $global:StorageConfig.Servers.Server.IPAddress -HostBusAdapterIds $HostRegistration}}}If (LUNExists $MasterLUN){Write-Host "unmask lun" $masterlunSet-EmcLunAccess -Lun $MasterLUN -InitiatorId $Hostregistration -HostName $global:StorageConfig.Servers.Server.ServerName -HostIPAddress $global:StorageConfig.Servers.Server.IPAddress -Available}Else{ # We Fail, because the LUN cannot be foundWrite-host "ERROR: Cannot find the LUN:" $MasterLUNExit 1}}ProcessStorageRequests.ps1
#----------------------------------------------------------------------------------# Filename: ProcessStorageRequests.ps1# Description: Create LUNs based on xml file# Input file: Storage_Luns.xml##----------------------------------------------------------------------------------## Uses an XML file with the following schema. This same schema is used by# - PrepMastBoot-AddViaWWPN.ps1# - Process Storage Requests.ps1# - PostClone_AddViaWWPN.ps1## <StorageParams># <Array>VNX5400</Array># <UCSAddress>10.5.177.10</UCSAddress># <Servers># <Server># <ServerName>VSPEX-01</ServerName># <IPAddress>192.168.10.31</IPAddress># <luns># <label>VSPEX-01</label># <pool>VSPEX_Pool_1</pool># <size>50GB</size># </luns># </Server># </Servers># </StorageParams>##----------------------------------------------------------------------------------$global:rootPath = Split-Path -Parent $MyInvocation.MyCommand.Path$myxmlfile = $global:rootPath + "\Storage_Luns.xml"function ReadStorageConfig ([String]$filename) {$xmlConfigFile = [xml](Get-Content $filename )$global:StorageConfig = $xmlConfigFile.SelectSingleNode( '/StorageParams' )}ReadStorageConfig $myxmlfileImport-Module ESIPSToolkitfunction LUNExists {param ($TGTLUN)$Val = Get-EmcLUN $TGTLUN -Silentif ($Val -eq $null) {return $false} else {return $true}}$StorageArray = get-EMCStorageSystem -ID $global:StorageConfig.Array -silentif ($StorageArray -eq $null){Write-Host "ERROR: Array" $Array "is not known or registered under that name."exit 1}Update-EmcSystem $StorageArrayfunction createluns {foreach ($entry in $global:StorageConfig.Servers.Server) {foreach ($lun in $entry.luns) {IF (LUNExists $lun.label){ Write-Host "LUN" $lun.label "already exists."}else{# We need to create the LUNwrite-host "Creating LUN" $lun.label$pool = get-emcstoragepool $lun.pool$Size = invoke-expression $lun.size$NewLUN = New-EmcLun -Pool $pool -Name $lun.label -Capacity $Size -Description $lun.label}}}}createlunsProcessClones.ps1
#----------------------------------------------------------------------------------# Filename: ProcessClones.ps1# Description: Create Clones from Source LUN# Input file: ProcessClones.xml##----------------------------------------------------------------------------------## Uses an XML file with the following schema# <StorageParams># <CloneGroupName>BooT_Luns</CloneGroupName># <VNXBlockSPAAddress>10.5.223.128</VNXBlockSPAAddress># <SourceLUN>Master_Boot_2012R2</SourceLUN># <TargetLUNs># <lun>VSPEX-01</lun># <lun>VSPEX-02</lun># <lun>VSPEX-03</lun># <lun>VSPEX-04</lun># <lun>VSPEX-05</lun># <lun>VSPEX-06</lun># </TargetLUNs># </StorageParams>##----------------------------------------------------------------------------------$global:rootPath = Split-Path -Parent $MyInvocation.MyCommand.Path$myxmlfile = $global:rootPath + "\ProcessClones.xml"function ReadStorageConfig ([String]$filename) {$xmlConfigFile = [xml](cat $filename )$global:StorageConfig = $xmlConfigFile.SelectSingleNode( '/StorageParams' )clsif ($global:StorageConfig.TargetLUNs.lun.count -gt "8"){write-host "There are" $StorageConfig.TargetLUNs.lun.count "clone targets, only 8 are supported concurrently"start-sleep 10exit}}ReadStorageConfig $myxmlfilewrite-host "Warning You are about to overwrite the following LUNs:" -foregroundcolor Black -backgroundcolor Yellowforeach ($entry in $global:StorageConfig.TargetLUNs.LUN) {write-host $entry}write-host "With the contents of LUN" $global:StorageConfig.SourceLUN$prompt = Read-Host "Please type 'overwrite' to continue"if ($prompt -ne "overwrite"){write-host $prompt "is not valid, exiting"exit 1}function CloneStart {$clonesource = get-emclun $global:StorageConfig.SourceLUNwrite-host "Creating Clone Group" $global:StorageConfig.CloneGroupNamewrite-host "Adding Source LUN" $clonesourcenaviseccli -address $global:StorageConfig.VNXBlockSPAAddress clone -createclonegroup -name $global:StorageConfig.CloneGroupName -Luns $clonesource.ArrayLunID -oforeach ($entry in $global:StorageConfig.TargetLUNs.LUN){$clonetarget=get-emclun $entrywrite-host "Adding Clone Target LUN" $clonetargetnaviseccli -address $global:StorageConfig.VNXBlockSPAAddress clone -addclone -Name $global:StorageConfig.CloneGroupName -Luns $clonetarget.ArrayLunId -syncrate high -o}}function CloneSyncCheck {$synchronized=naviseccli -address $global:StorageConfig.VNXBlockSPAAddress clone -listclone -name $global:StorageConfig.CloneGroupName -percentsynced | select-string PercentSyncedforeach ($entry in $synchronized){$test=$entry -split ":"foreach ($sentry in $test[1]){$sentry=$sentry.trim()write-host $sentry "% Copied per Clone target"if ($sentry -ne "100"){start-sleep 20CloneSyncCheck}}}}function CloneFracture {$fracture=naviseccli -address $global:StorageConfig.VNXBlockSPAAddress clone -listclone -name $global:StorageConfig.CloneGroupName | select-string CloneIDforeach ($entry in $fracture){$test=$entry -split ":"foreach ($sentry in $test[1]){$sentry=$sentry.trim()write-host "Fracturing Clone Target" $sentrynaviseccli -address $global:StorageConfig.VNXBlockSPAAddress clone -fractureclone -Name $global:StorageConfig.CloneGroupName -CloneId $sentry -o}}}function CloneDelete {$cdelete=naviseccli -address $global:StorageConfig.VNXBlockSPAAddress clone -listclone -name $global:StorageConfig.CloneGroupName | select-string CloneIDforeach ($entry in $cdelete){$test=$entry -split ":"foreach ($sentry in $test[1]){$sentry=$sentry.trim()write-host "Deleting Clone Target" $sentrynaviseccli -address $global:StorageConfig.VNXBlockSPAAddress clone -removeclone -Name $global:StorageConfig.CloneGroupName -CloneId $sentry -o}}}function CloneGroupDelete {write-host "Deleting Clone Group" $global:StorageConfig.CloneGroupName$cdelete=naviseccli -address $global:StorageConfig.VNXBlockSPAAddress clone -destroyclonegroup -name $global:StorageConfig.CloneGroupName -o}CloneStartCloneSyncCheckCloneFractureCloneDeleteCloneGroupDeleteProcessClones.xml
<StorageParams><SourceLUN>Master_Boot_2012R2</SourceLUN><CloneGroupName>Boot_Luns</CloneGroupName><VNXBlockSPAAddress>10.5.223.128</VNXBlockSPAAddress><TargetLUNs><lun>VSEPX-01</lun><lun>VSPEX-02</lun><lun>VSPEX-03</lun><lun>VSPEX-04</lun><lun>VSPEX-05</lun><lun>VSPEX-06</lun></TargetLUNs></StorageParams>PostClone_AddViaWWPN.ps1
#----------------------------------------------------------------------------------# Filename: PostClone_AddViaWWPN.ps1# Description: Set up Cisco UCS ServiceProfile to do Boot From SAN from VNX5400# Input File: Storage_Luns.xml#----------------------------------------------------------------------------------## Uses an XML file with the following schema. This same schema is used by# - PrepMastBoot-AddViaWWPN.ps1# - Process Storage Requests.ps1# - PostClone_AddViaWWPN.ps1## <StorageParams># <Array>VNX5400</Array># <UCSAddress>10.5.177.10</UCSAddress># <Servers># <Server># <ServerName>VSPEX-01</ServerName># <IPAddress>192.168.10.31</IPAddress># <luns># <label>VSPEX-01</label># <pool>VSPEX_Pool_1</pool># <size>50GB</size># </luns># </Server># </Servers># </StorageParams>##----------------------------------------------------------------------------------$global:rootPath = Split-Path -Parent $MyInvocation.MyCommand.Path$myxmlfile = $global:rootPath + "\Storage_Luns.xml"function ReadStorageConfig ([String]$filename) {$xmlConfigFile = [xml](Get-Content $filename )$global:StorageConfig = $xmlConfigFile.SelectSingleNode( '/StorageParams' )}ReadStorageConfig $myxmlfileImport-Module CiscoUcsPSImport-Module ESIPSToolkitfunction LUNExists {param ($TGTLUN)$Val = Get-EmcLUN $TGTLUN -Silentif ($Val -eq $null) {return $false} else {return $true}}function reghostexists {param ($tgthost)$val = get-emcstorageregisteredhost $tgthostif ($Val -eq $null) {return $false} else {return $true}}$StorageArray = get-EMCStorageSystem -ID $global:StorageConfig.Array -silentif ($StorageArray -eq $null){Write-Host "ERROR: Array" $Array "is not known or registered under that name."exit 1}Update-EmcSystem $StorageArray# Prompt user for connection to UCS environmentif ($UCS -eq $null) {$UCS = connect-ucs $global:StorageConfig.UCSAddress}foreach ($entry in $global:StorageConfig.Servers.Server) {foreach ($lun in $entry.luns) {write-host $entry.Servername, $lun.label# Check for pre-existing LUNIF (LUNExists $lun.label){# We present the LUN$MyServiceProfile = Get-UcsServiceProfile | where {$_.Name -eq $entry.ServerName}if ($MyServiceProfile -eq $null){Write-Host "ERROR: Cannot find ServiceProfile" $global:StorageConfig.Servers.Server.ServerNameexit 1}else{## Extract out the WWPN initiator information for the Service Profile#$MyvHBAs = Get-UcsVhba -ServiceProfile $MyServiceProfile## Get the Boot LUN that we plan to use#$BootLUN = get-EMCLun -ID $lun.label -BlockStorageSystem $StorageArray## Add all the initiators from the Service Profile to the Storage Group on the VNX#foreach ($vHBA in $MyvHBAs){$HostRegistration = $vHBA.NodeAddr + ":" + $vHBA.Addrif (reghostexists $entry.ServerName){$rg=get-emcstorageregisteredhost $entry.ServerNamewrite-host "New Init" $HostRegistrationNew-EmcStorageRegisteredInitiator -registeredhost $rg -InitiatorIds $HostRegistration}else{write-host "New Host" $HostRegistrationNew-EMCStorageRegisteredHost -StorageSystem $StorageArray -HostName $entry.ServerName -IpAddress $entry.IPAddress -HostBusAdapterIds $HostRegistration}}}if (LUNExists $BootLUN){write-host "unmask lun" $BootLunSet-EmcLunAccess -Lun $BootLUN -InitiatorId $Hostregistration -HostName $entry.ServerName -HostIPAddress $entry.IPAddress -unAvailable}else{# We Fail, because the LUN cannot be foundWrite-host "ERROR: Cannot find the LUN:" $BootLUNexit 1}}}}Cisco Nexus 1000V Installation
Cisco Nexus 1000V Series Switches provide a comprehensive and extensible architectural platform for virtual machine and cloud networking. The switches are designed to accelerate server virtualization and multi-tenant cloud deployments in a secure and operationally transparent manner for environments like Microsoft's Private Cloud. Download the distribution software from the location specified in the Software Revision table at the beginning of this document and expand it into a temporary directory.
Create Two Virtual Supervisor Module Virtual Machines
The Nexus 1000V runs as a pair of virtual machines for high availability purposes. The Nexus 1000V distribution contains an ISO file (nexus-1000v.5.2.1.SM1.5.1.iso) that is used in the creation of the virtual machines that will run the Nexus 1000V software. Copy it to the Virtual Machine Manager library. (The VMM library is a standard Windows share, so normal procedures for putting simple files into the share work. Refresh the library location after the copy is completed.
1.
Note
Note
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
21.
Configure the VSM
One of the components of the Nexus 1000V distribution media is an ISO file used for installing the software. As one of the first steps of this installation, you should have copied this ISO file to the VMM library.
Note
1.
2.
3.
4.
Note
5.
6.
7.
–
–
8.
9.
10.
11.
12.
13.
The next series of commands are answers similar to configuring a typical Nexus switch for out-of-band management.
14.
15.
16.
17.
18.
19.
20.
21.
22.
23.
Note
24.
25.
26.
27.
28.
29.
30.
Configure Virtual Switch Extension Manager in VMM
1.
2.
3.
4.
5.
Note
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
21.
You will now see a listing for the Virtual Switch Extension Manager within VMM.
22.
23.
24.
Copy Virtual Ethernet Module Installation Packager to the VMM Virtual Machines
Perform the following procedure on each Virtual Machine Manager node.
1.
C:\ProgramData\Switch Extensions Drivers
Configure a Logical Switch in VMM
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
21.
22.
23.
24.
25.
26.
Create the Logical Switch on the Hyper-V Hosts
Perform the following on each clustered Hyper-V node used for Fabric Management.
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
Create a Virtual Machine Network
1.
2.
3.
4.
5.
6.
You can see the definition of the VM network in the VMM console.
Configure the Virtual Machine Manager Virtual Machine Properties
This example shows how to add the network managed by the Nexus 1000V to the VMM virtual machines. The same procedure would be used to add network adapters on this managed network to other virtual machines.
1.
2.
Stop-Computer
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
Stop-Computer -ComputerName <VMM02> -Force
17.
18.
19.
20.
21.
22.
23.
24.
25.
26.
27.
Customer Configuration Worksheets
These worksheets provide a way to capture all the information needed before installation is started. It can also be left with the customer for future reference.
Common Server
Hyper-V Servers
WWNN/WWPN
EMC VNX5400 Array
WWNN/WWPN
Cisco UCS Network Infrastructure
VLAN Information
Service Information
Cabling
Cisco Nexus 5548 A
Cisco Nexus 5548 B
Cisco 6248 Fabric Interconnect A
Cisco 6248 Fabric Interconnect B
Appendix
FCoE Configuration
The following instructions assume a working environment that consists of adding FCoE direct capabilities.
VLANs
Cabling
Nexus Configuration
The following configuration steps assume that the settings are being added into a running configuration.
Configure QoS Policy
Nexus A and Nexus B
policy-map type qos system-qos-policyclass class-fcoeset qos-group 1exitexitpolicy-map type queuing system-queue-in-policyclass type queuing class-fcoebandwidth percent 75class type queuing class-defaultbandwidth percent 25exitexitpolicy-map type queuing system-queue-out-policyclass type queuing class-fcoebandwidth percent 75class type queuing class-defaultbandwidth percent 25exitexitpolicy-map type network-qos system-nwqos-policyclass type network-qos class-fcoepause no-dropmtu 2158class type network-qos class-defaultmtu 9000exitexitsystem qosservice-policy type qos input system-qos-policyservice-policy type queuing input system-queue-in-policyservice-policy type queuing output system-queue-out-policyservice-policy type network-qos system-nwqos-policyexitcopy running-config start-configshow running-config ipqosclass-map type qos class-fcoeclass-map type queuing class-fcoematch qos-group 1class-map type queuing class-all-floodmatch qos-group 2class-map type queuing class-ip-multicastmatch qos-group 2policy-map type qos system-qos-policyclass class-fcoeset qos-group 1class class-defaultpolicy-map type queuing system-queue-in-policyclass type queuing class-fcoebandwidth percent 75class type queuing class-defaultbandwidth percent 25policy-map type queuing system-queue-out-policyclass type queuing class-fcoebandwidth percent 75class type queuing class-defaultbandwidth percent 25class-map type network-qos class-fcoematch qos-group 1class-map type network-qos class-all-floodmatch qos-group 2class-map type network-qos class-ip-multicastmatch qos-group 2policy-map type network-qos jumboclass type network-qos class-defaultmtu 9000multicast-optimizepolicy-map type network-qos system-nwqos-policyclass type network-qos class-fcoepause no-dropmtu 2158class type network-qos class-defaultmtu 9000multicast-optimizesystem qosservice-policy type qos input system-qos-policyservice-policy type queuing input system-queue-in-policyservice-policy type queuing output system-queue-out-policyservice-policy type network-qos system-nwqos-policyVLANs
Nexus A
vlan 101name FCoE-Aexitshow vlanVLAN Name Status Ports---- -------------------------------- --------- -------------------------------1 default active Po10, Po13, Po14,Eth1/1, Eth1/2, Eth1/3, Eth1/4Eth1/5, Eth1/6, Eth1/7, Eth1/8Eth1/9, Eth1/10, Eth1/11Eth1/12, Eth1/13, Eth1/14Eth1/15, Eth1/16, Eth1/17Eth1/18, Eth1/21, Eth1/22Eth1/23, Eth1/24, Eth1/25Eth1/26, Eth1/27, Eth1/2810 VMaccess active Po10, Po13, Po14, Eth1/1Eth1/2, Eth1/17, Eth1/1811 LiveMigration active Po10, Po13, Po14, Eth1/1Eth1/2, Eth1/17, Eth1/1812 CSV active Po10, Po13, Po14, Eth1/1Eth1/2, Eth1/17, Eth1/1813 ClusComm active Po10, Po13, Po14, Eth1/1Eth1/2, Eth1/17, Eth1/1816 SMB-A active Po10, Po13, Po14, Eth1/1Eth1/2, Eth1/17, Eth1/1817 SMB-B active Po10, Po13, Po14, Eth1/1Eth1/2, Eth1/17, Eth1/1818 iSCSI-A active Po10, Po13, Po14, Eth1/1Eth1/2, Eth1/17, Eth1/1819 iSCSI-B active Po10, Po13, Po14, Eth1/1Eth1/2, Eth1/17, Eth1/18101 FCoE-A active200 VEM active Po10, Po13, Po14, Eth1/1Eth1/2, Eth1/17, Eth1/18VLAN Type Vlan-mode---- ----- ----------1 enet CE10 enet CE11 enet CE12 enet CE13 enet CE16 enet CE17 enet CE18 enet CE19 enet CE101 enet CE200 enet CEPrimary Secondary Type Ports------- --------- --------------- -------------------------------------------Nexus B
vlan 102name FCoE-BexitPort Descriptions
Nexus A
interface Ethernet1/19description UCSM-A-Eth1/19-FCoEexitinterface Ethernet1/20description UCSM-A-Eth1/20-FCoEexitinterface Ethernet1/27description SPA-A3:1-FCoEswitchport mode trunkswitchport trunk allowed vlan 101spanning-tree port type edge trunkexitinterface Ethernet1/28description SPB-B3:1-FCoEswitchport mode trunkswitchport trunk allowed vlan 101spanning-tree port type edge trunkexitshow interface description-------------------------------------------------------------------------------Interface Description-------------------------------------------------------------------------------fc1/29 --fc1/30 --fc1/31 --fc1/32 ---------------------------------------------------------------------------------Port Type Speed Description-------------------------------------------------------------------------------Eth1/1 eth 10G Nexus-B:Eth1/1-PeerlinkEth1/2 eth 10G Nexus-B:Eth1/2-PeerlinkEth1/3 eth 10G --Eth1/4 eth 10G --Eth1/5 eth 10G --Eth1/6 eth 10G --Eth1/7 eth 10G --Eth1/8 eth 10G --Eth1/9 eth 10G --Eth1/10 eth 10G --Eth1/11 eth 10G --Eth1/12 eth 10G --Eth1/13 eth 10G --Eth1/14 eth 10G --Eth1/15 eth 10G --Eth1/16 eth 10G --Eth1/17 eth 10G UCSM-A eth1/17Eth1/18 eth 10G UCSM-B eth1/17Eth1/19 eth 10G UCSM-A-Eth1/19-FCoEEth1/20 eth 10G UCSM-A-Eth1/20-FCoEEth1/21 eth 10G --Eth1/22 eth 10G --Eth1/23 eth 10G --Eth1/24 eth 10G --Eth1/25 eth 10G --Eth1/26 eth 10G --Eth1/27 eth 10G SPA-A3:1-FCoEEth1/28 eth 10G SPB-B3:1-FCoE-------------------------------------------------------------------------------Interface Description-------------------------------------------------------------------------------Po10 vPC Peer-linkPo13 UCS-6248-APo14 UCS-6248-BNexus B
interface Ethernet1/19description UCSM-B-Ethernet1/19-FCoEexitinterface Ethernet1/20description UCSM-B-Ethernet1/20-FCoEexitinterface Ethernet1/27description SPA-A3:0-FCoEswitchport mode trunkswitchport trunk allowed vlan 102spanning-tree port type edge trunkexitinterface Ethernet1/28description SPB-B3:0-FCoEswitchport mode trunkswitchport trunk allowed vlan 102spanning-tree port type edge trunkexitCreate Port Channel
Nexus A
interface Ethernet1/19switchport description UCSM-A-Eth1/19-FCoEexitinterface Ethernet1/20switchport description UCSM-A-Eth1/20-FCoEexitinterface Po105switchport description UCSM-A-FCoEexitinterface Ethernet1/19-20channel-group 105 mode activeno shutdownexitcopy running-config start-configshow port-channel summaryFlags: D - Down P - Up in port-channel (members)I - Individual H - Hot-standby (LACP only)s - Suspended r - Module-removedS - Switched R - RoutedU - Up (port-channel)M - Not in use. Min-links not met--------------------------------------------------------------------------------Group Port- Type Protocol Member PortsChannel--------------------------------------------------------------------------------10 Po10(SU) Eth LACP Eth1/1(P) Eth1/2(P)13 Po13(SU) Eth LACP Eth1/17(P)14 Po14(SU) Eth LACP Eth1/18(P)105 Po105(SU) Eth LACP Eth1/19(P) Eth1/20(P)Nexus B
interface Ethernet1/19switchport description UCSM-B-Eth1/19-FCoEexitinterface Ethernet1/20switchport description UCSM-B-Eth1/20-FCoEexitinterface Po106switchport description UCSM-B-FCoEinterface Ethernet1/19-20channel-group 106 mode activeno shutdownexitcopy running-config start-configAdd Port Channel Configuration
Nexus A
interface Po105switchport mode trunkswitchport trunk allowed vlan 101no shutdownexitcopy running-config start-configshow running-config interface port-channel 105interface port-channel105description UCSM-A-FCoEswitchport mode trunkswitchport trunk allowed vlan 101Nexus B
interface Po106switchport mode trunkswitchport trunk allowed vlan 102no shutdownexitcopy running-config start-configConfigure FCoE Fabric
Nexus A
interface vfc101bind interface ethernet1/27switchport trunk allowed vsan 101no shutdownexitinterface vfc102bind interface ethernet1/28switchport trunk allowed vsan 101no shutdownexitvsan databasevsan 101vsan 101 name Fabric_Avsan 101 interface vfc101vsan 101 interface vfc102exitvlan 101fcoe vsan 101exitcopy running-config startup-configshow vsan 101vsan 101 informationname:Fabric_A state:activeinteroperability mode:defaultloadbalancing:src-id/dst-id/oxidoperational state:upshow vsan 101 membershipvsan 101 interfaces:vfc101 vfc102Nexus B
interface vfc101bind interface ethernet1/27switchport trunk allowed vsan 102no shutdownexitinterface vfc102bind interface ethernet1/28switchport trunk allowed vsan 102no shutdownexitvsan databasevsan 102vsan 102 name Fabric_Bvsan 102 interface vfc101vsan 102 interface vfc102exitvlan 102fcoe vsan 102exitcopy running-config startup-configCisco Unified Computing System Configuration
Create FCoE Uplink Ports
Create VSANs
Create a Fibre Channel Policy
Create VHBA Templates
Determine VNX FCoE Ports and WWNs
In order to create boot policies, you need to determine the WWNs assigned to the FCoE ports.
The following table lists the values used in this example.
Feedback