VersaStack for Data Center Scale Out

Deployment of Cisco Unified Computing System and IBM Storwize V7000 Scale Out with VMware vSphere 5.5
Update 2

NOTE: Works with document’s Advanced Properties “First Published” property. Click File | Properties | Advanced Properties | Custom.

Last Updated: November 25, 2015

NOTE: Works with document’s Advanced Properties “Last Updated” property. Click File | Properties | Advanced Properties | Custom.

                                                                                                                                                                                         

 

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

http://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)

© 2015 Cisco Systems, Inc. All rights reserved.

 

Table of Contents

About Cisco Validated Designs. 2

Executive Summary. 6

VersaStack for Data Center Overview.. 7

Introduction. 7

Audience. 7

Solution Design and Architecture. 8

Architecture. 8

Software Revisions. 10

Configuration Guidelines. 11

VLAN Topology. 11

Virtual Machines. 12

Configuration Variables. 13

VersaStack Cabling. 18

VersaStack Cabling. 18

VersaStack Deployment 25

Cisco Nexus 9000 Initial Configuration Setup. 25

Cisco Nexus A. 25

Cisco Nexus B. 26

Enable Appropriate Cisco Nexus 9000 Features and Settings. 28

Create VLANs for VersaStack Traffic. 28

Configure Virtual Port Channel Domain. 29

Configure Network Interfaces for the VPC Peer Links. 30

Configure Network Interfaces to Cisco UCS Fabric Interconnect 32

Configure Network Interfaces to Cisco UCS Fabric Interconnect 33

Management Plane Access for Servers and Virtual Machines. 35

Cisco Nexus 9000 A & B Using Interface VLAN Example 1. 35

Cisco Nexus 9000 A and B using Port Channel Example 2. 36

Cisco MDS 9148S Initial Configuration Setup. 37

Cisco MDS A. 37

Cisco MDS B. 39

Enable Appropriate Cisco MDS Features and Settings. 41

Enable VSANs and Create Port Channel and Cluster Zone. 41

Storage Configuration. 46

Secure Web Access to the IBM Storwize V7000 Service and Management GUI 46

Prerequisites. 46

IBM Storwize V7000 Initial Configuration. 47

IBM Storwize V7000 Initial Configuration Setup. 50

Optional Storage Mirroring. 73

Server Configuration. 78

VersaStack Cisco UCS Initial Setup. 78

VersaStack Cisco UCS Configuration. 79

Cisco MDS 9148S Compute SAN Zoning. 139

Cisco MDS - A Switch. 139

Cisco MDS - B Switch. 140

Storage LUN Mapping. 142

Adding Hosts and Mapping the Boot Volumes on the IBM Storwize V7000. 142

ESX and vSphere Installation and Setup. 149

VersaStack VMware ESXi 5.5 Update 2 SAN Boot Installation. 149

VMware ESXi Installation. 150

Install ESXi 151

vSphere Setup and ESXi Configuration. 154

Log in to VMware ESXi Hosts Using VMware vSphere Client 154

Set Up VMkernel Ports and Virtual Switch. 155

Map Required VMFS Datastores. 157

VersaStack VMware vCenter 5.5 Update 2. 159

Build Microsoft SQL Server Virtual Machine. 159

Install Microsoft SQL Server 2008 R2. 161

Build and Set Up VMware vCenter Virtual Machine. 167

Install VMware vCenter Server 170

ESXi Dump Collector Setup. 176

Set Up vCenter Server 178

Move VM Swap File Location. 180

Optional: Add Domain Account Permissions. 181

Set Up the Optional Cisco Nexus 1000V Switch Using Cisco Switch Update Manager 183

Cisco Nexus 1000V. 183

Installation Process. 184

Deploy the OVF Template for the Cisco Nexus 1000 Virtual Switch Update Manager 184

Install the VSM through the Cisco Virtual Switch Update Manager 188

Perform Base Configuration of the Primary VSM.. 191

Migrate Networking Components for ESXi Hosts to Cisco Nexus 1000V. 194

Remove the Networking Standard Switch Components for ESXi Hosts. 198

Remove the Redundancy for the NIC in Cisco UCS Manager 201

Backup Management and other Software. 202

IBM Solutions. 202

Bill of Materials. 203

Appendix. 210

Build Windows Active Directory Server Virtual Machines. 210

ESXi Host VM-Host-Infra-01. 210

Cisco Nexus 9000 Example Configurations. 216

Cisco Nexus 9000 A. 216

Cisco Nexus 9000 B. 223

Cisco MDS Example Configurations. 231

About the Authors. 254

Acknowledgments. 254

 

 

This document describes how to install IBM and Cisco infrastructure for a successful VMware deployment. In today's rapid paced IT environment there are many challenges including:

·         Increased OPEX. In a recent poll, 73 percent of all IT spending was used just to keep the current data center running

·         Rapid storage growth has become more and more difficult to manage and costly

·         Existing compute and storage are under utilized

·         IT groups are challenged to meet SLA’s,  dealing with complex troubleshooting

·         IT groups are inundated with  time  consuming data migrations to manage growth and change

In order solve these issues and increase efficiency.  IT department are moving   to converged infrastructure solutions. These solutions offer many benefits, some of which are having the integration testing completed along with thoroughly documented deployment procedures. They also offer increased feature sets and premium support with a single point of contact.  Cisco and IBM have team up to bring the best networking, compute and storage in a single solution named VersaStack. VersaStack offers customers versatility and simplicity, great performance, along with reliability. In this document we will show how to install a scaled out VersaStack setup for a VMware infrastructure that is designed increase IOPS and storage capacity. A brief list of the VersaStack benefits that solve the challenges previously noted include: 

·         Cisco Unified Computing System Manger providing  simplified management for compute and network through a consolidated management tool

·         Cisco USC Service Profiles designed to vastly reduce deployment time and provide consistency in the datacenter

·         Cisco Fabric Interconnects to reduce infrastructure costs and simplify networking

·         IBM Real-time compression to reduce the storage footprint and storage costs

·         IBM Easy Tier to automate optimizing performance while lowing storage costs by automatically placing  infrequently accessed data on cheaper disk, and highly accessed data on faster tiers thereby  reducing costly migrations

·         IBM’s  V7000 Storwize Simplified Storage Management designed to simplify day to day storage tasks 

VersaStack offers customers the ability to reduce OPEX while at the same time helping meet their SLA’s  by simplifying many of the day-to-day IT tasks, as well as consolidating and automating others.

Introduction

The current data center trend, driven by the need to better utilize available resources, is towards virtualization on shared infrastructure. Higher levels of efficiency can be realized on integrated platforms due to the pooling of compute, network and storage resources, brought together by a pre-validated process. Validation eliminates compatibility issues and presents a platform with reliable features that can be deployed in an agile manner. This industry trend and the validation approach used to cater to it, has resulted in enterprise customers moving away from silo architectures. VersaStack serves as the foundation for a variety of workloads, enabling efficient architectural designs that can be deployed quickly and with confidence.

Audience

This document describes the architecture and deployment procedures of an infrastructure composed of Cisco®, IBM ®, and VMware® virtualization that uses IBM Storwize V7000 block protocols. The intended audience for this document includes, but is not limited to, sales engineers, field consultants, professional services, IT managers, partner engineering, and customers who want to deploy the core VersaStack architecture with IBM Storwize V7000.

Architecture

The VersaStack architecture is highly modular or "Pod"-like. There is sufficient architectural flexibility and design options to scale as required with investment protection. The platform can be scaled up (adding re-sources to existing VersaStack units) and/or out (adding more VersaStack units).

Specifically, VersaStack is a defined set of hardware and software that serves as an integrated foundation for both virtualized and non-virtualized solutions. VMware vSphere® built on VersaStack includes IBM Storwize V7000, Cisco networking, the Cisco Unified Computing System™ (Cisco UCS®), Cisco MDS fiber-channel switches and VMware vSphere software in a single package. The design is flexible enough that the networking, computing, and storage can fit in one data center rack or be deployed according to a customer's data center design. Port density enables the networking components to accommodate multiple configurations.

One benefit of the VersaStack architecture is the ability to meet any customer's capacity or performance needs in a cost effective manner. A storage system capable of serving multiple protocols across a single interface allows for customer choice and investment protection because it is a wire-once architecture.

This architecture references relevant criteria pertaining to resiliency, cost benefit, and ease of deployment of all components including IBM Storwize V7000 storage.

The architecture for this solution shown below uses two sets of hardware resources:

1.    Common Infrastructure services on redundant and self-contained hardware.

2.    VersaStack Pod

The common infrastructure services include Active Directory, DNS, DHCP, vCenter, Nexus 1000v virtual supervisor module (VSM) and any other shared service. These components are considered core infrastructure as they provide necessary data-center wide services where the VersaStack Pod resides. Since these services are integral to the deployment and operation of the platform, there is a need to adhere to best practices in their design and implementation. This includes such features as high-availability, appropriate RAID setup and performance and scalability considerations given such services may need to be extended to multiple Pods. At a customer's site, depending on whether this is a new data center, there may not be a need to build this infrastructure piece.

The figure below illustrates the VMware vSphere built on VersaStack components and the network connections for a configuration with IBM Storwize V7000 Storage. This design uses the Cisco Nexus® 9396, and Cisco UCS B-Series with the Cisco UCS virtual interface card (VIC) and the IBM Storwize V7000 storage controllers connected in a highly available design using Cisco Virtual Port Channels (vPCs). This infrastructure is deployed to provide FC-booted hosts with block-level access to shared storage datastores.

 

Figure 1       VersaStack Cabling Overview

 

The reference hardware configuration includes:

·         Two Cisco Nexus 9396 or 9372 switches

·         Two Cisco UCS 6248UP Fabric Interconnects

·         Two Cisco MDS 9148S Fibre-Channel switches

·         Support for 32 Cisco UCS C-Series servers without any additional networking components

·         Support for 8 Cisco UCS B-Series servers without any additional blade server chassis

·         Support for 160 Cisco UCS C-Series and B-Series servers by way of additional fabric extenders and blade server chassis

·         Two IBM Storwize V7000 control enclosures and one V7000 expansion enclosure per control enclosure. Support for up to 504 small form-factor (SFF) disks of any capacity attached to each control enclosure.

For server virtualization, the deployment includes VMware vSphere. Although this is the base design, each of the components can be scaled easily to support specific business requirements. For example, more (or different) servers or even blade chassis can be deployed to increase compute capacity, additional disk shelves can be deployed to improve I/O capability and throughput, and special hardware or software features can be added to introduce new features.

This document guides you through the low-level steps for deploying the base architecture. These procedures cover everything from physical cabling to network, compute and storage device configurations.

For Information regarding the design of VersaStack, please reference the Design guide at:

http://www.cisco.com/c/en/us/solutions/enterprise/data-center-designs-cloud-computing/versastack-designs.html

Software Revisions

The table below details the software revisions used for validating various components of the Cisco Nexus 9000 based VersaStack architecture.  To validate your enic version run the "ethtool -i vmnic0" through the command line of the ESX host. For more information regarding supported configurations, please reference the following Interoperability links:

IBM:

http://www-03.ibm.com/systems/support/storage/ssic/interoperability.wss

Cisco:

http://www.cisco.com/web/techdoc/ucs/interoperability/matrix/matrix.html

Table 1    Software Revisions

Configuration Guidelines

This document provides details on configuring a fully redundant, highly available VersaStack unit with IBM Storwize V7000 storage. Therefore, reference is made at each step to the component being configured as either A or B. For example, Node-A through Node-D are used to identify the IBM storage controllers that are provisioned with this document, and Cisco Nexus A and Cisco Nexus B identify the pair of Cisco Nexus switches that are configured. The Cisco UCS fabric Interconnects are similarly configured. Additionally, this document details the steps for provisioning multiple Cisco UCS hosts, and these are identified sequentially: VM-Host-Infra-01, VM-Host-Infra-02, and so on. Finally, to indicate that you should include information pertinent to your environment in a given step, <text> appears as part of the command structure. See the following example for the network port vlan create command:

Usage:

network port vlan create ?

   [-node] <nodename>                  Node

   { [-vlan-name] {<netport>|<ifgrp>}  VLAN Name

   |  -port {<netport>|<ifgrp>}        Associated Network Port

[-vlan-id] <integer> }              Network Switch VLAN Identifier

Example:

network port vlan –node <node01> -vlan-name i0a-<vlan id

This document is intended to enable you to fully configure the VersaStack Pod in the environment. Various steps require you to insert customer-specific naming conventions, IP addresses, and VLAN schemes, as well as to record appropriate MAC addresses.

VLAN Topology

The tables in this section describe the VLANs, example IP ranges, and the virtual machines (VMs) necessary for deployment. The networking architecture can be unique to each environment. Since the design of this deployment is a POD, the architecture in this document leverages private networks and only the in-band management VLAN traffic routes through the Cisco 9k switches. Other management traffic is routed through a separate Out of Band Management switch. The architecture can vary based on the deployment objectives.  An NFS VLAN is included in this document to allow connectivity to any existing NFS datastores for migration of virtual machines, if required.

Table 2    VLANS

Table 3    Example IP's

Table 4    VLAN Logical View

Virtual Machines

This document assumes that the following infrastructure machines exist or are created during the installation.

Table 5    Machine List

Configuration Variables

Table 6 lists the customer implementation values for the variables which should be identified prior to starting the installation procedure.

Table 6    Customer Variables

 

Table 7 lists the Fibre Channel environment and these variables need to be collected during the installation phase for subsequent use in this document.

Table 7    WWPN Variables

Figure 2 illustrates the VersaStack build process.

Figure 2       VersaStack Build Process

VersaStack Cabling

The information in this section is provided as a reference for cabling the equipment in a VersaStack environment. To simplify cabling requirements, the tables include both local and remote device and port locations.

The tables in this section contain details for the prescribed and supported configuration of the IBM Storwize V7000 running 7.4.0.3.

This document assumes that out-of-band management ports are plugged into an existing management infrastructure at the deployment site. These interfaces will be used in various configuration steps.

It is possible to order IBM Storwize V7000 systems in a different configuration from what is presented in the tables in this section. Before starting, be sure that the configuration matches the descriptions in the tables and diagrams in this section.

Figure 3 illustrates the cabling diagrams for VersaStack configurations using the Cisco Nexus 9000 and IBM Storwize V7000. For SAS cabling information, the V7000 control enclosure and expansion enclosure should be connected according to the cabling guide at the following URL:

http://www01.ibm.com/support/knowledgecenter/ST3FR7_7.3.0/com.ibm.storwize.v7000.730.doc/v3500_qisasca bles_b4jtyu.html?cp=ST3FR7%2F1-3-0-1-3&lang=en

Figure 3       VersaStack Wiring Diagram

Figure 4 shows the Management cabling. The V7000’s have redundant management connections. One path is through the dedicated out-of-band management switch, and the secondary path is through the in-band management path going up through the 9k to the production network.

Figure 4       VersaStack Management Cabling

 The tables below provide the details of the connections in use.

Table 8    Cisco Nexus 9000-A Cabling Information

* The ports can be replaced with E2/11 and E2/12 for 40G connectivity.

Table 9    Cisco Nexus 9000-B Cabling Information

* The ports can be replaced with E2/11 and E2/12 for 40G connectivity.

Table 10      IBM Storwize V7000 Controller Node-A Cabling Information

 

Table 11      IBM Storwize V7000 Controller Node-B Cabling Information

 

Table 12      IBM Storwize V7000 Controller Node-C Cabling Information

 

Table 13      IBM Storwize V7000 Controller Node-D Cabling Information

 

Table 14      Cisco Nexus MDS 9148S-A Cabling Information

 

Table 15      Cisco Nexus MDS 9148S-B Cabling Information

 

Table 16      Cisco UCS Fabric Interconnect A Cabling Information

 

Table 17      Cisco UCS Fabric Interconnect B Cabling Information

 

Table 18      Cisco UCS C-Series with Cisco Nexus 2232PP FEX

 

Table 19      Cisco Nexus Rack FEX A

 

Table 20      Cisco Nexus Rack FEX B

 

Cisco Nexus 9000 Initial Configuration Setup

The steps provided in this section details for the initial Cisco Nexus 9000 Switch setup.

Cisco Nexus A

To set up the initial configuration for the first Cisco Nexus switch complete the following steps:

Abort Auto Provisioning and continue with normal setup ?(yes/no)[n]: y

         ---- System Admin Account Setup ----

Do you want to enforce secure password standard (yes/no) [y]:

    Enter the password for "admin":

  Confirm the password for "admin":

         ---- Basic System Configuration Dialog VDC: 1 ----

This setup utility will guide you through the basic configuration of the system. Setup configures only enough connectivity for management of the system.

Please register Cisco Nexus9000 Family devices promptly with your supplier. Failure to register may affect response times for initial service calls. Nexus9000 devices must be registered to receive entitled support services.

Press Enter at anytime to skip a dialog. Use ctrl-c at anytime to skip the remaining dialogs.

Would you like to enter the basic configuration dialog (yes/no): y

  Create another login account (yes/no) [n]: n

  Configure read-only SNMP community string (yes/no) [n]:

  Configure read-write SNMP community string (yes/no) [n]:

  Enter the switch name : <<var_nexus_A_hostname>>

  Continue with Out-of-band (mgmt0) management configuration? (yes/no) [y]:

 Mgmt0 IPv4 address : <<var_nexus_A_mgmt0_ip>>  

 Mgmt0 IPv4 netmask : <<var_nexus_A_mgmt0_netmask>>  

 Configure the default gateway? (yes/no) [y]:

 IPv4 address of the default gateway : <<var_nexus_A_mgmt0_gw>>  

 Configure advanced IP options? (yes/no) [n]:

 Enable the telnet service? (yes/no) [n]:

 Enable the ssh service? (yes/no) [y]:

    Type of ssh key you would like to generate (dsa/rsa) [rsa]:

    Number of rsa key bits <1024-2048> [1024]: 2048

  Configure the ntp server? (yes/no) [n]: y

    NTP server IPv4 address : <<var_global_ntp_server_ip>> 

 Configure default interface layer (L3/L2) [L2]:

  Configure default switchport interface state (shut/noshut) [noshut]:

  Configure CoPP system profile (strict/moderate/lenient/dense/skip) [strict]:

The following configuration will be applied:

  password strength-check 

switchname <<var_nexus_A_hostname>>

vrf context management

 ip route 0.0.0.0/0 <<var_nexus_A_mgmt0_gw>>

exit

 no feature telnet 

ssh key rsa 2048 force

 feature ssh 

ntp server <<var_global_ntp_server_ip>> 

system default switchport 

 no system default switchport shutdown 

 copp profile strict

interface mgmt0 ip address <<var_nexus_A_mgmt0_ip>><var_nexus_A_mgmt0_netmask>> no shutdown

Would you like to edit the configuration? (yes/no) [n]:

Use this configuration and save it? (yes/no) [y]:

[########################################] 100% Copy complete.

Cisco Nexus B

To set up the initial configuration for the second Cisco Nexus switch complete the following steps:

Abort Auto Provisioning and continue with normal setup ?(yes/no)[n]: y

         ---- System Admin Account Setup ----

Do you want to enforce secure password standard (yes/no) [y]:

    Enter the password for "admin":

  Confirm the password for "admin":

         ---- Basic System Configuration Dialog VDC: 1 ---This setup utility will guide you through the basic configuration of the system. Setup configures only enough connectivity for management of the system.

Please register Cisco Nexus9000 Family devices promptly with your supplier. Failure to register may affect response times for initial service calls. Nexus9000 devices must be registered to receive entitled support services.

Press Enter at anytime to skip a dialog. Use ctrl-c at anytime to skip the re-maining dialogs.

Would you like to enter the basic configuration dialog (yes/no): y

  Create another login account (yes/no) [n]: n

  Configure read-only SNMP community string (yes/no) [n]:

  Configure read-write SNMP community string (yes/no) [n]:

  Enter the switch name : <<var_nexus_B_hostname>>

  Continue with Out-of-band (mgmt0) management configuration? (yes/no) [y]:

    Mgmt0 IPv4 address : <<var_nexus_B_mgmt0_ip>>

    Mgmt0 IPv4 netmask : <<var_nexus_B_mgmt0_netmask>>  

Configure the default gateway? (yes/no) [y]:

    IPv4 address of the default gateway : <<var_nexus_B_mgmt0_gw>>

  Configure advanced IP options? (yes/no) [n]:

  Enable the telnet service? (yes/no) [n]:

  Enable the ssh service? (yes/no) [y]:

    Type of ssh key you would like to generate (dsa/rsa) [rsa]:

    Number of rsa key bits <1024-2048> [1024]: 2048

  Configure the ntp server? (yes/no) [n]: y

    NTP server IPv4 address : <<var_global_ntp_server_ip>>

  Configure default interface layer (L3/L2) [L2]:

  Configure default switchport interface state (shut/noshut) [noshut]:

  Configure CoPP system profile (strict/moderate/lenient/dense/skip) [strict]:

The following configuration will be applied: 

password strength-check

switchname <<var_nexus_B_hostname>>

vrf context management

ip route 0.0.0.0/0 <<var_nexus_B_mgmt0_gw>>

exit

 no feature telnet 

ssh key rsa 2048 force

 feature ssh 

ntp server <<var_global_ntp_server_ip>> 

system default switchport 

 no system default switchport shutdown 

 copp profile strict

interface mgmt0 ip address <<var_nexus_B_mgmt0_ip>><<var_nexus_B_mgmt0_netmask>> no shutdown

Would you like to edit the configuration? (yes/no) [n]:

Use this configuration and save it? (yes/no) [y]:

[########################################] 100% Copy complete.

Enable Appropriate Cisco Nexus 9000 Features and Settings

Cisco Nexus 9000 A and Cisco Nexus 9000 B

The following commands enable the IP switching feature and set default spanning tree behaviors:

1.    On each Nexus 9000, enter the configuration mode:

 config terminal

2.    Use the following commands to enable the necessary features:

feature udld

feature lacp

feature vpc

3.    Configure the spanning tree and save the running configuration to start-up:

spanning-tree port type network default

spanning-tree port type edge bpduguard default

spanning-tree port type edge bpdufilter default

copy run start

Create VLANs for VersaStack Traffic

Cisco Nexus 9000 A and Cisco Nexus 9000 B

To create the necessary virtual local area networks (VLANs), complete the following step on both switches:

1.    From the configuration mode, run the following commands:

vlan <<var_ib-mgmt_vlan_id>>

name IB-MGMT-VLAN

vlan <<var_native_vlan_id>>

name Native-VLAN

vlan <<var_nfs_vlan_id>>

name NFS-VLAN

vlan <<var_vmotion_vlan_id>>

name vMotion-VLAN

vlan <<var_vm_traffic_vlan_id>>

name VM-Traffic-VLAN

exit    

copy run start

Configure Virtual Port Channel Domain

Cisco Nexus 9000 A

To configure virtual port channels (vPCs) for switch A, complete the following steps:

1.    From the global configuration mode, create a new vPC domain:

vpc domain <<var_nexus_vpc_domain_id>>

2.    Make the Nexus 9000A the primary vPC peer by defining a low priority value:

 role priority 10

3.    Use the management interfaces on the supervisors of the Nexus 9000s to establish a keepalive link:

peer-keepalive destination <<var_nexus_B_mgmt0_ip>>  source <<var_nexus_A_mgmt0_ip>>

4.    Enable the following features for this vPC domain:

peer-switch

delay restore 150

peer-gateway

ip arp synchronize

auto-recovery

copy run start

Cisco Nexus 9000 B

To configure vPCs for switch B, complete the following steps:

1.    From the global configuration mode, create a new vPC domain:

vpc domain <<var_nexus_vpc_domain_id>>

2.    Make the Nexus 9000A the primary vPC peer by defining a low priority value:

 role priority 20

3.    Use the management interfaces on the supervisors of the Nexus 9000s to establish a keepalive link:

peer-keepalive destination <<var_nexus_A_mgmt0_ip>> source <<var_nexus_B_mgmt0_ip>>

4.    Enable the following features for this vPC domain:

peer-switch

delay restore 150

peer-gateway

ip arp synchronize

auto-recovery

copy run start

Configure Network Interfaces for the VPC Peer Links

Cisco Nexus 9000 A

1.    Define a port description for the interfaces connecting to VPC Peer <var_nexus_B_hostname>>. 

interface Eth1/47

description VPC Peer <<var_nexus_B_hostname>>:1/47

interface Eth1/48

description VPC Peer <<var_nexus_B_hostname>>:1/48

2.    Apply a port channel to both VPC Peer links and bring up the interfaces.

interface Eth1/47,Eth1/48

channel-group 10  mode active

no shutdown

3.    Define a description for the port-channel connecting to <<var_nexus_B_hostname>>.

interface Po10

description vPC peer-link

4.    Make the port-channel a switchport, and configure a trunk to allow in-band management, NFS, VM traffic, and the native VLAN.

switchport

switchport mode trunk

switchport trunk native vlan <<var_native_vlan_id>>

switchport trunk allowed vlan <<var_ib-mgmt_vlan_id>>, <<var_nfs_vlan_id>>,<<var_vmotion_vlan_id>>, <<var_vm_traffic_vlan_id>>,

5.    Make this port-channel the VPC peer link and bring it up.

vpc peer-link

no shutdown

copy run start

Cisco Nexus 9000 B

1.    Define a port description for the interfaces connecting to VPC Peer <var_nexus_A_hostname>>.  

interface Eth1/47

description VPC Peer <<var_nexus_A_hostname>>:1/47

interface  Eth1/48

description VPC Peer <<var_nexus_A_hostname>>:1/48

2.    Apply a port channel to both VPC Peer links and bring up the interfaces.

interface Eth1/47,Eth1/48

channel-group 10 mode active

no shutdown

3.    Define a description for the port-channel connecting to <<var_nexus_A_hostname>>.

interface Po10

description vPC peer-link

4.    Make the port-channel a switchport, and configure a trunk to allow in-band management, NFS, VM traffic, and the native VLAN.

switchport

switchport mode trunk

switchport trunk native vlan <<var_native_vlan_id>>

switchport trunk allowed vlan <<var_ib-mgmt_vlan_id>>, <<var_nfs_vlan_id>>,

<<var_vmotion_vlan_id>>, <<var_vm_traffic_vlan_id>>,

5.    Make this port-channel the VPC peer link and bring it up.

vpc peer-link

no shutdown

copy run start

Configure Network Interfaces to Cisco UCS Fabric Interconnect

Cisco Nexus 9000 A

1.    Define a description for the port-channel connecting to <<var_ucs_clustername>>-A.

interface Po13

description <<var_ucs_clustername>>-A

2.    Make the port-channel a switchport, and configure a trunk to allow in-band management, NFS, VM traffic, and the native VLANs.

switchport

switchport mode trunk

switchport trunk native vlan <<var_native_vlan_id>>

switchport trunk allowed vlan <<var_ib-mgmt_vlan_id>>, <<var_nfs_vlan_id>>,<<var_vmotion_vlan_id>>, <<var_vm_traffic_vlan_id>>,

3.    Make the port channel and associated interfaces spanning tree edge ports.

spanning-tree port type edge trunk

4.    Set the MTU to be 9216 to support jumbo frames.

mtu 9216 

5.    Make this a VPC port-channel and bring it up.

vpc 13

no shutdown

6.    Define a port description for the interface connecting to <<var_ucs_clustername>>-A.

interface Eth1/25

description <<var_ucs_clustername>>-A:1/25

7.    Apply it to a port channel and bring up the interface.

channel-group 13 force mode active

no shutdown

8.    Define a description for the port-channel connecting to <<var_ucs_clustername>>-B

interface Po14

description <<var_ucs_clustername>>-B

9.    Make the port-channel a switchport, and configure a trunk to allow InBand management, NFS, and VM traffic VLANs and the native VLAN.

switchport

switchport mode trunk

switchport trunk native vlan <<var_native_vlan_id>>

switchport trunk allowed vlan <<var_ib-mgmt_vlan_id>>, <<var_nfs_vlan_id>>, <<var_vmotion_vlan_id>>, <<var_vm_traffic_vlan_id>>

10.  Make the port channel and associated interfaces spanning tree edge ports.

spanning-tree port type edge trunk

11.  Set the MTU to be 9216 to support jumbo frames.

mtu 9216

12.  Make this a VPC port-channel and bring it up.

vpc 14

no shutdown

13.  Define a port description for the interface connecting to <<var_ucs_clustername>>-B

interface Eth1/26

description <<var_ucs_clustername>>-B:1/26

14.  Apply it to a port channel and bring up the interface.

channel-group 14 force  mode active

no shutdown

copy run start

Configure Network Interfaces to Cisco UCS Fabric Interconnect

Cisco Nexus 9000 B

1.    Define a description for the port-channel connecting to <<var_ucs_clustername>>-B

interface Po14

description <<var_ucs_clustername>>-B

2.    Make the port-channel a switchport, and configure a trunk to allow in-band management, NFS, VM traffic, and the native VLANs.

switchport

switchport mode trunk

switchport trunk native vlan <<var_native_vlan_id>>

switchport trunk allowed vlan <<var_ib-mgmt_vlan_id>>, <<var_nfs_vlan_id>>, <<var_vmotion_vlan_id>>, <<var_vm_traffic_vlan_id>>

3.    Make the port channel and associated interfaces spanning tree edge ports.

spanning-tree port type edge trunk

4.    Set the MTU to 9216 to support jumbo frames.

mtu 9216

5.    Make this a VPC port-channel and bring it up.

vpc 14

no shutdown

6.    Define a port description for the interface connecting to <<var_ucs_clustername>>-B

interface Eth1/25

description <<var_ucs_clustername>>-B:1/25

7.    Apply it to a port channel and bring up the interface.

channel-group 14 force mode active

no shutdown

8.    Define a description for the port-channel connecting to <<var_ucs_clustername>>-A

interface Po13

description <<var_ucs_clustername>>-A

9.    Make the port-channel a switchport, and configure a trunk to allow InBand management, NFS, and VM traffic VLANs and the native VLAN.

switchport

switchport mode trunk

switchport trunk native vlan <<var_native_vlan_id>>

switchport trunk allowed vlan <<var_ib-mgmt_vlan_id>>, <<var_nfs_vlan_id>>, <<var_vmotion_vlan_id>>, <<var_vm_traffic_vlan_id>>,

10.  Make the port channel and associated interfaces spanning tree edge ports.

spanning-tree port type edge trunk

11.  Set the MTU to be 9216 to support jumbo frames.

mtu 9216

12.  Make this a VPC port-channel and bring it up.

vpc 13

no shutdown

13.  Define a port description for the interface connecting to <<var_ucs_clustername>>-A

interface Eth1/26

description <<var_ucs_clustername>>-A:1/26

14.  Apply it to a port channel and bring up the interface.

channel-group 13 force  mode active

no shutdown

copy run start

Management Plane Access for Servers and Virtual Machines

There are multiple ways to configure the switch to uplink to your separate management switch. There are two examples shown below. These examples are provide to help show a method about  how the configuration could be setup, however, since networking configurations can vary, it is recommended that you  consult your local network personal for the optimal configuration.  In the first example provided in this section, a single switch is top of rack and the Cisco Nexus 9000 series switches are both connected to it through its ports 36. The Cisco 9k switches use a 1 gig SFP to convert the connected to Cat-5 copper connecting to the top of  rack switch, however, connection types can vary. The 9k’s are configured with the interface-vlan option and each 9k switch has a unique IP for its VLAN. The traffic required to route from the 9k is the in-band management traffic, so use the VLAN 3175 and set the port to access mode. The top of rack switch also has its ports set to access mode. In the second example, leverage the port channel, which maximizes upstream connectivity.  In the second example, the top of rack switch will have the port channel configured as well.

Cisco Nexus 9000 A & B Using Interface VLAN Example 1

On the Nexus A switch, type the following commands detailed below. Notice the VLAN IP is different on each switch.

Cisco Nexus 9000 A

int Eth1/36

description IB-management-access

switchport mode access

spanning-tree port type network

switchport access vlan <<var_ib-mgmt_vlan_id>>

no shut

feature interface-vlan

int Vlan <<var_ib-mgmt_vlan_id>>

ip address <<var_switch_A_inband_mgmt_ip_address>>/<<var_inband_mgmt_netmask>>

no shut

ip route 0.0.0.0/0 <<var_inband_mgmt_gateway>>

copy run start

Cisco Nexus 9000 B

int Eth1/36

description Ib-management-access

switchport mode access

spanning-tree port type network

switchport access vlan <<var_ib-mgmt_vlan_id>>

no shut

feature interface-vlan

int Vlan <<var_ib-mgmt_vlan_id>>

ip address <<var_switch_B_inband_mgmt_ip_address>>/<<var_inband_mgmt_netmask>>

no shut

ip route 0.0.0.0/0 <<var_inband_mgmt_gateway>>

copy run start

Cisco Nexus 9000 A and B using Port Channel Example 2

To enable management access across the IP switching environment leveraging port channel in config mode run the following commands:

1.    Define a description for the port-channel connecting to management switch.

interface po9

description IB-MGMT

2.    Configure the port as an access VLAN carrying the InBand management VLAN traffic.

switchport

switchport mode access

switchport access vlan <<var_ib-mgmt_vlan_id>>

3.    Make the port channel and associated interfaces normal spanning tree ports.

 spanning-tree port type normal

4.    Make this a VPC port-channel and bring it up.

vpc 9

no shutdown

5.    Define a port description for the interface connecting to the management plane.

interface Eth1/36

description IB-MGMT-SWITCH_uplink

6.    Apply it to a port channel and bring up the interface.

channel-group 9 force mode active

no shutdown

7.    Save the running configuration to start-up in both Nexus 9000s  and run commands  to look at  port and port channel.

Copy run start

sh int eth1/36 br

sh port-channel summary

Cisco MDS 9148S Initial Configuration Setup

The steps in this section provide the details for the initial Cisco MDS Fibre Channel Switch setup. Zone the storage prior to creating the Storwize cluster so the nodes can communicate to each other.

Cisco MDS A

To set up the initial configuration for the first Cisco MDS switch, complete the following steps:

1.    On initial boot and connection to the serial or console port of the switch, the MDS setup should automatically start and attempt to enter Power on Auto Provisioning.

Abort Auto Provisioning and continue with normal setup ?(yes/no)[n]: y

         ---- System Admin Account Setup ----

Do you want to enforce secure password standard (yes/no) [y]:

      Enter the password for "admin":

  Confirm the password for "admin":

         ---- Basic System Configuration Dialog ----

This setup utility will guide you through the basic configuration of

the system. Setup configures only enough connectivity for management of the system.

Please register Cisco MDS 9000 Family devices promptly with your supplier. Failure to register may affect response times for initial service calls. MDS devices must be registered to receive entitled support services.

Press Enter at anytime to skip a dialog. Use ctrl-c at anytime to skip the remaining dialogs.

Would you like to enter the basic configuration dialog (yes/no): y 

 Create another login account (yes/no) [n]:

  Configure read-only SNMP community string (yes/no) [n]:

  Configure read-write SNMP community string (yes/no) [n]:

  Enter the switch name : <<var_MDS_A_hostname>>

  Continue with Out-of-band (mgmt0) management configuration? (yes/no) [y]:

    Mgmt0 IPv4 address : <<var_MDS_A_mgmt0_ip>>

    Mgmt0 IPv4 netmask : <<var_MDS_A_mgmt0_netmask>>  

    Configure the default gateway? (yes/no) [y]:

    IPv4 address of the default gateway : <<var_MDS_A_mgmt0_gw>>  

    Configure advanced IP options? (yes/no) [n]:

  Enable the ssh service? (yes/no) [y]:

    Type of ssh key you would like to generate (dsa/rsa) [rsa]:

    Number of rsa key bits <1024-2048> [1024]: 2048  

    Enable the telnet service? (yes/no) [n]:

  Configure congestion/no_credit drop for fc interfaces? (yes/no)     [y]:   Enter the type of drop to configure congestion/no_credit drop? (con/no) [c]:

    Enter milliseconds in multiples of 10 for congestion-drop for port mode F     in range (<100-500>/default), where default is 500.  [d]:   

 Congestion-drop for port mode E must be greater than or equal to     Conges-tion-drop for port mode F. Hence, Congestion drop for port     mode E will be set as default.

  Enable the http-server? (yes/no) [y]:

 Configure clock? (yes/no) [n]:

 Configure timezone? (yes/no) [n]: y

Enter timezone config [PST/MST/CST/EST] : <<var_timezone>>

Enter Hrs offset from UTC [-23:+23] : <<var_UTC_offset>>

Enter Minutes offset from UTC [0-59] :

Configure summertime? (yes/no) [n]:

Configure the ntp server? (yes/no) [n]: y

NTP server IPv4 address : <<var_global_ntp_server_ip>>  

Configure default switchport interface state (shut/noshut) [shut]:

  Configure default switchport trunk mode (on/off/auto) [on]:

  Configure default switchport port mode F (yes/no) [n]:

  Configure default zone policy (permit/deny) [deny]:

  Enable full zoneset distribution? (yes/no) [n]:

  Configure default zone mode (basic/enhanced) [basic]:

The following configuration will be applied:

  password strength-check 

 switchname <<var_MDS_A_hostname>>

   interface mgmt0

    ip address <<var_MDS_A_mgmt0_ip>> <<var_MDS_A_mgmt0_netmask>>     no shutdown  

ip default-gateway <<var_MDS_A_mgmt0_gw>>  

ssh key rsa 2048 force  

feature ssh 

 no feature telnet   system timeout congestion-drop default mode F   system timeout congestion-drop default mode E  

feature http-server

clock timezone PST 0 0

ntp server <<var_global_ntp_server_ip>>  

system default switchport shutdown 

system default switchport trunk mode on

no system default zone default-zone permit  

no system default zone distribute full 

no system default zone mode enhanced

Would you like to edit the configuration? (yes/no) [n]:

Use this configuration and save it? (yes/no) [y]:

[########################################] 100% Copy complete.

Cisco MDS B

To set up the initial configuration for the second Cisco  MDS switch, complete the following steps:

1.    On initial boot and connection to the serial or console port of the switch, the MDS setup should automatically start and attempt to enter Power on Auto Provisioning.

Abort Auto Provisioning and continue with normal setup ?(yes/no)[n]: y

         ---- System Admin Account Setup ----

Do you want to enforce secure password standard (yes/no) [y]:

      Enter the password for "admin":

  Confirm the password for "admin":

         ---- Basic System Configuration Dialog ----

This setup utility will guide you through the basic configuration of the system. Setup configures only enough connectivity for management of the system.

Please register Cisco MDS 9000 Family devices promptly with your supplier. Failure to register may affect response times for initial service calls. MDS devices must be registered to receive entitled support services.

Press Enter at anytime to skip a dialog. Use ctrl-c at anytime to skip the remaining dialogs.

Would you like to enter the basic configuration dialog (yes/no): y  

Create another login account (yes/no) [n]:

  Configure read-only SNMP community string (yes/no) [n]:

  Configure read-write SNMP community string (yes/no) [n]:

  Enter the switch name : <<var_MDS_B_hostname>>

  Continue with Out-of-band (mgmt0) management configuration? (yes/no) [y]:

    Mgmt0 IPv4 address : <<var_MDS_B_mgmt0_ip>>

    Mgmt0 IPv4 netmask : <<var_MDS_B_mgmt0_netmask>> 

 Configure the default gateway? (yes/no) [y]:

    IPv4 address of the default gateway : <<var_MDS_B_mgmt0_gw>> 

 Configure advanced IP options? (yes/no) [n]:

  Enable the ssh service? (yes/no) [y]:

    Type of ssh key you would like to generate (dsa/rsa) [rsa]:

    Number of rsa key bits <1024-2048> [1024]: 2048 

 Enable the telnet service? (yes/no) [n]:

  Configure congestion/no_credit drop for fc interfaces? (yes/no)     [y]:

  Enter the type of drop to configure congestion/no_credit drop? (con/no) [c]:

    Enter milliseconds in multiples of 10 for congestion-drop for port mode F     in range (<100-500>/default), where default is 500.  [d]:    

Congestion-drop for port mode E must be greater than or equal to     Congestion-drop for port mode F. Hence, Congestion drop for port     mode E will be set as default.

  Enable the http-server? (yes/no) [y]:

 Configure clock? (yes/no) [n]:

 Configure timezone? (yes/no) [n]: y

Enter timezone config [PST/MST/CST/EST] : <<var_timezone>>

Enter Hrs offset from UTC [-23:+23] : <<var_UTC_offset>>

Enter Minutes offset from UTC [0-59] :

Configure summertime? (yes/no) [n]:

Configure the ntp server? (yes/no) [n]: y

NTP server IPv4 address : <<var_global_ntp_server_ip>>  

Configure default switchport interface state (shut/noshut) [shut]:

Configure default switchport trunk mode (on/off/auto) [on]:

  Configure default switchport port mode F (yes/no) [n]:

  Configure default zone policy (permit/deny) [deny]:

  Enable full zoneset distribution? (yes/no) [n]:

  Configure default zone mode (basic/enhanced) [basic]:

The following configuration will be applied:

  password strength-check  

switchname : <<var_MDS_B_hostname>>

interface mgmt0  

  ip address <<var_MDS_B_mgmt0_ip>> <<var_MDS_B_mgmt0_netmask>>

   no shutdown

  ip default-gateway <<var_MDS_B_mgmt0_gw>>

  ssh key rsa 2048 force  

feature ssh 

 no feature telnet 

 system timeout congestion-drop default mode F  

system timeout congestion-drop default mode E 

feature http-server  clock timezone PST 0 0

       ntp server <<var_global_ntp_server_ip>>  

      system default switchport shutdown  

      system default switchport trunk mode on  

       no system default zone default-zone permit  

       no system default zone distribute full  

       no system default zone mode enhanced

Would you like to edit the configuration? (yes/no) [n]:

Use this configuration and save it? (yes/no) [y]: [########################################] 100% Copy complete.

Enable Appropriate Cisco MDS Features and Settings

Cisco MDS A and B

1.    The following commands enable feature on both switches:

config

feature npiv

feature fport-channel-trunk

Enable VSANs and Create Port Channel and Cluster Zone

Cisco MDS A 

1.    Create a Port Channel that will be uplinked to the fabric interconnect 

interface port-channel 1

2.    Create a VSAN and assign interfaces to it. Ports assigned to the port channel will also be in this Vsan. Configure the ports up.

vsan database

vsan <<var_vsan_a_id>>

vsan <<var_vsan_a_id>>  interface fc1/3-6

vsan <<var_vsan_a_id>>  interface po1

interface fc1/3-6

no shut

3.    Activate the port channel.

interface port-channel 1

channel mode active

switchport rate-mode dedicated

4.    Assign interfaces to the port channel and save the config.

interface fc1/1-2 

port-license acquire

channel-group 1 force 

no shutdown

exit

copy run start

5.    Run show flogi database to obtain the WWPN’s for the Storwize nodes . Copy the 4 WWPN’s for the IBM Storewize system to create a zone for the cluster         

sh flogi database

 

6.    Input the WWPN’s into the variable table provided.  Nodes are identified by their assigned switch ports.

7.    Create a dev alias database for each PWWN using the port assignments.

device-alias database

device-alias name VersaStack-NodeA  pwwn var_wwpn_FC_NodeA-fabricA

device-alias name VersaStack-NodeB  pwwn var_wwpn_FC_NodeB-fabricA

device-alias name VersaStack-NodeC  pwwn var_wwpn_FC_NodeC-fabricA

device-alias name VersaStack-NodeD  pwwn var_wwpn_FC_NodeD-fabricA

device-alias commit

8.    Create the zone for the Storwize Cluster.

zone name versastack vsan <<var_vsan_a_id>>   

member device-alias VersaStack-NodeA

member device-alias VersaStack-NodeB

member device-alias VersaStack-NodeC

member device-alias VersaStack-NodeD

exit  

9.    Create the zoneset  for the VersaStack configuration  and add the zone. 

zoneset name versastackzoneset vsan <<var_vsan_a_id>>  

member versastack

zoneset activate name  versastackzoneset vsan <<var_vsan_a_id>>

sh zoneset active  

copy run start

Cisco MDS B

1.    Create Port Channel that will be uplinked to the fabric interconnect. 

interface port-channel 2

2.    Create a VSAN and assign interfaces to it. Ports assigned to the port channel will also be in this vsan.

vsan  database

vsan <<var_vsan_b_id>>

vsan <<var_vsan_b_id>> interface fc1/3-6

vsan <<var_vsan_b_id>> interface po2

interface fc1/3-6

no shut

3.    Activate  the port channel.

interface port-channel 2

channel mode active

switchport rate-mode dedicated

4.    Assign interfaces to the port channel  and save the config.

interface fc1/1-2

port-license acquire

channel-group 2 force 

no shutdown

exit

copy run start

5.    Run show flogi database to obtain the WWPN’s for the Storwize cluster. Copy the 4 WWPN’s for the IBM Storewize system to create a zone for the cluster.    

sh flogi database

6.    Input the fabric B WWPN’s into  the variable table identified by their assigned switch port.

7.    Create a dev alias database for each PWWN using the port assignments

device-alias database

device-alias name VersaStack-NodeA  pwwn var_wwpn_FC_NodeA-fabricB

device-alias name VersaStack-NodeB  pwwn var_wwpn_FC_NodeB-fabricB

device-alias name VersaStack-NodeC  pwwn var_wwpn_FC_NodeC-fabricB

device-alias name VersaStack-NodeD  pwwn var_wwpn_FC_NodeD-fabricB

device-alias commit

8.    Create the zone for the Storwize Cluster.

zone name versastack vsan <<var_vsan_b_id>>   

member device-alias VersaStack-NodeA

member device-alias VersaStack-NodeB

member device-alias VersaStack-NodeC

member device-alias VersaStack-NodeD

exit  

9.    Create the zoneset  for the VersaStack configuration and add the zone. 

zoneset name versastackzoneset vsan <<var_vsan_b_id>>  

member versastack

zoneset activate name  versastackzoneset vsan <<var_vsan_b_id>>

sh zoneset active

copy run start

Storage Configuration

In this section the storage will be configured. As an example, the required planning is completed and in this configuration, the IBM Easy Tier is leveraged to automatically move frequently accessed “hot” data to SSD disk. Easy tier will be leveraged with three tiers with the first tier being fast SSD, a middle tier of 10k and 15k RPM enterprise SAS drives, and the third tier consisting of larger capacity slower 7200 RPM drives known as Nearline. Rarely accessed data also known as “cold” data is moved to the third Nearline tier automatically. Moving cold data off the SAS or SSD disks to Nearline reduces storage operating costs while improving performance for the other tiers. Money saved leveraging the less expensive Nearline storage will be used to offset the cost of faster SSD disks.  Encryption will be used to increase security and to save cost when disposing of drives. The IBM Real-time compression is leveraged to reduce OPEX by reducing our storage footprint, and mirroring for fault tolerance. Proper planning can optimize your performance and help reduce operational costs for your VersaStack.  

Secure Web Access to the IBM Storwize V7000 Service and Management GUI

Browser access to all system and service IPs is automatically configured to connect securely using HTTPS and SSL. Attempts to connect through HTTP will get redirected to HTTPS.

The system generates its own self-signed SSL certificate. Upon first connection to the system, your browser may present a security exception because it does not trust the signer; you should allow the connection to proceed.

Prerequisites

Since you will be implementing encryption during the setup, you will need the licenses for this feature for both storage controllers. There is no trial license. You will also need 6 USB keys for the two control enclosures, three installed on each control enclosure to allow us to complete the setup operation. The USB keys can be removed from the system after setup and kept in a secure location. Whenever an encryption-enabled V7000 system is powered on, it requires a USB key containing the correct encryption key to be plugged into a control enclosure. As such, it is recommended that one USB key is to remain installed in each system if you plan to allow automatic rebooting of the system should it be shut down for any reason. Alternatively, you would need to re-insert 1 USB key to reboot.

 

Figure 5        Three USB Drives Installed in the V7000

 

IBM Storwize V7000 Initial Configuration

Complete the following steps for the v7000 setup only on node A.  If you are connecting multiple control enclosures for scale, the additional nodes will communicate through the Fibre Channel connection for initial discovery.  

1.    Configure an Ethernet port of a PC/laptop to allow DHCP to configure its IP address and DNS.

2.    Connect an Ethernet cable from the PC/laptop Ethernet port to the Ethernet port labelled "T" on the rear of either node canister in the V7000 control enclosure.

 

3.    A few moments after the connection is made, the node will use DHCP to configure the IP address and DNS settings of the laptop/PC.

4.    Open a browser and go to address https://install which will direct you to the initialization wizard.

5.    When asked how the node will be used, select "As the first node in a new system." Click Next.

6.    Follow the instructions that are presented by the initialization tool to configure the system with a management IP address <<var_cluster_mgmt_ip>>,<<var_cluster_mgmt_mask>> and <<var_cluster _mgmt_gateway>>, then click Next.

7.    Click Close when the task is completed.

 

8.    Click Next.

 

9.    After you complete the initialization process, disconnect the cable as directed, between the PC/laptop and the technician port, and re-connect to your network with your previous settings. Your browser will be redirected the management GUI, at the IP address you configured.

IBM Storwize V7000 Initial Configuration Setup

1.    Read and accept the license agreement.

 

2.    Login as superuser with password of passw0rd.

3.    Change the password for superuser and then click Log In.

4.    On the welcome to system setup screen click Next.

5.    Enter the System Name and click Apply and Next to proceed.

6.    Select NTP Server and enter the address of the server then select Apply and click Next, then click Close.

7.    Enter the number of licenses and click Apply and click Next, and then click Close.

8.    Select Yes for Encryption.

9.    Click Actions and select Activate License Manually.

10.  Enter the License key for encryption, click Activate then click Close, then click Next.

11.  Validate the Detected Enclosures and click Apply and click Next, then click Close.

 

12.  Click Yes for Email Event Notification and click Next. 

13.  Fill out system location and contact details  <<var_org>> <<var_street_address>>, <<var_city>> <<var_state>>  <<var_zip>> <<var_country_code>>, then click Next.

14.  Insert Contact Details  <<var_contact_name>> <<var_email_contact>><<var_admin_phone>><<var_city>>    then click Apply and click Next and click Close.

15.  Input the email server IP address  <<var_mailhost_ip>> and change the port if necessary, then click Apply and click Next, then click Close.

 

16.  Enter the email addresses for all administrators that should be notified when issues occur as well and any other parties that need info or inventory <<var_email_contact>>. Click Apply and click Next then click Close.

17.  Review the Summary and screen and click Finish, then click Close after tasks have completed.

18.  Click the Enable Encryption popup dialog.

19.  The dialog states you will need three USB flash drives. This is per storage controller, so make sure you have a total of six installed, three per enclosure if you are setting up two control enclosures.  Click Next.

 

20.  Wait for the Encryption Key updates to complete then click Next.

 

21.  Click Commit to enable Encryption then click Close.

          

 

22.  Click Cancel to the add hosts popup as they will be added later in this document.

 

23.  Click the top left icon and select System.

 

24.  Select the actions pane in the top left of the screen and click Add Enclosure. 

 

 

25.  Select the enclosure detected and click Next.

26.  Highlight the new enclosure that is not licensed for encryption, click Actions, and select License manually. 

27.  Enter the license key and click Activate then click Close.

28.  Click Next to continue.

29.  Leave the Automatic button selected for the raid configuration and click Finish. This will take a few minutes for the process of control enclosure completion. Click Close, then click Close again when it completes.

  

30.  In the left side menu, hover over each of the icons to become familiar with the GUI options. Select the Setting icon and choose Network. 

 

31.  On the Network screen, highlight the Management IP Addresses section. Then click the number 1 interface on the left had side to bring up the Ethernet port IP menu. Change the IP address if necessary and click OK. If you are applying change to the interface you are connected to, the application will prompt you to close so it can redirect you to the new IP interface you have chosen.

 

32.  While still on the Network screen, highlight the Service IP Addresses section and click interface 1. Change the IP address  if necessary and click OK.

33.  Select the Node Canister drop-down and select Left. 

 

34.  Click interface 1. Change the IP address  if necessary and click OK.

35.  Change Control enclosure selection by selecting the Control Enclosure: dropdown and choosing the secondary enclosure ID. Repeat the process for the other service IP addresses as required so you have 1 service IP for each node.

36.  Click the lock Access icon in the left pane and select Users to access the Users screen.

37.  Select Create User.

 

38.  Enter and new name for an alternative admin account. Leave Security Admin default, and input the new password then click Create.

 

39.  Logout the superuser account and log back in as the new account you created.

. 

40.  Click Cancel if you are prompted to add host or volumes, and select the Pools icon one the left screen and select Volumes by Pool.

41.  Click the Create Volumes selection.

 

42.  Select a preset that you want for the ESXi boot volume and select the Pool for the first control enclosure.

43.  Input quantity 2, capacity 40GB, and name VM-Host-Infra-0. In addition, change the starting ID to 1. Click Create and then click Close.

 

44.  Click create volume again and select the disk preset, and the Pool for the first enclosure. Enter quantity 1, capacity 500GB, and name infra_datastore_1. Click Create, and then click Close.

45.  Click create  volume again and select the disk preset, and the Pool for the first enclosure. Enter quantity 1, capacity 100GB, and name infra_swap. Click Create and then click Close.

 

46.  Validate the volumes created volumes.

Optional Storage Mirroring

In order to protect against a managed disk failure or expansion enclosure failure, leverage the mirrored volume copies. If you desire to separate the storage between control enclosures, it is important to validate which managed disks are assigned to which pools and their associated control enclosure. In the following example, the storage pool mdiskgrp0 reside on hardware nodes A and B. The validated the pools, managed disks and their member drives are all owned by the correct enclosure. The same process is done to validate the storage pool mdiskgrp1 residing on the hardware for node C and D, which is the other control enclosure. 

Prior to deploying Mirroring, consider your design objectives and the desired behavior.

For example, while the volume copies are mirrored within the system, you can also use Global Mirror or Metro Mirror to replicate volumes to a separate Storwize system. Below are two deployment options as an example, one with mirroring and one without. 

 

Complete the following steps to enable mirroring in your VersaStack to protect again expansion enclosure failure, or multiple disk failure.

1.    Click the Pools icon in the left pane and select Volume by Pool.

2.    Make sure you have the first pool selected in the left column. Right-click the column titles in the right side and select the check box for pool to display a pool name column.

 

3.    Highlight a volume, right-click and select volume copy action, then add mirrored copy.

4.    Select a Volume Type and a Pool that resides on the second control enclosure and click Add Copy, then click Close.

 

5.    Repeat the Add Mirror Copy process for all volumes that were created. VM-Host-Infra-01, VM-Host-Infra-02, in-fra_datastore_1, and infra_swap, and validate that each volume has one copy on a disk pool on for the first control enclosures, and the other copy on the pool for the second enclosure.

6.    Right-click the first volume and click Properties.

 

7.    Click Edit and set the Mirror Sync Rate to 100% and select both Accessible I/O Groups, then click Save then click Close and click Close again.

 

8.    Repeat the property settings for Sync Rate and Accessible I/O Groups for the remaining volumes.

Server Configuration

VersaStack Cisco UCS Initial Setup

Perform Initial Setup of Cisco UCS 6248 Fabric Interconnect for VersaStack Environments

This section provides detailed procedures for configuring the Cisco Unified Computing System for use in a VersaStack environment. The steps are necessary to provision the Cisco UCS C-Series and B-Series servers and should be followed precisely to avoid improper configuration.

Cisco UCS 6248 A

To configure the Cisco UCS for use in a VersaStack environment, complete the following steps:

1.    Connect to the console port on the first Cisco UCS 6248 fabric interconnect.

Enter the configuration method: console 

Enter the setup mode; setup newly or restore from backup.(setup/restore)? Setup

You have chosen to setup a new fabric interconnect? Continue? (y/n): y

Enforce strong passwords? (y/n) [y]: y

Enter the password for "admin": <<var_password>>

Enter the same password for "admin": <<var_password>> 

Is this fabric interconnect part of a cluster (select 'no' for standalone)?

(yes/no) [n]: y

Which switch fabric (A|B): A

Enter the system name: <<var_ucs_clustername>>

Physical switch Mgmt0 IPv4 address: <<var_ucsa_mgmt_ip>>

Physical switch Mgmt0 IPv4 netmask: <<var_ucsa_mgmt_mask>>

IPv4 address of the default gateway: <<var_ucsa_mgmt_gateway>>

Cluster IPv4 address: <<var_ucs_cluster_ip>>

Configure DNS Server IPv4 address? (yes/no) [no]: y

DNS IPv4 address: <<var_nameserver_ip>>

Configure the default domain name? y

Default domain name: <<var_dns_domain_name>>

Join centralized management environment (UCS Central)? (yes/no) [n]: Enter

2.    Review the settings printed to the console. If they are correct, answer yes to apply and save the configuration.

3.    Wait for the login prompt to make sure that the configuration has been saved prior to proceeding to step 4.

Cisco UCS 6248 B

To configure the Cisco UCS for use in a VersaStack environment, complete the following steps:

1.    Power on the second module and connect to the console port on the second Cisco UCS 6248 fabric interconnect.

Enter the configuration method: console 

Installer has detected the presence of a peer Fabric interconnect. This Fabric interconnect will be added to the cluster.  Do you want to continue {y|n}? y

Enter the admin password for the peer fabric interconnect: <<var_password>>

Physical switch Mgmt0 IPv4 address: <<var_ucsb_mgmt_ip>>

Apply and save the configuration (select ‘no’ if you want to re-enter)? (yes/no): y

VersaStack Cisco UCS Configuration

Log in to Cisco UCS Manager

To log in to the Cisco Unified Computing System (UCS) environment, complete the following steps:

1.    Open a web browser and navigate to the Cisco UCS 6248 Fabric Interconnect cluster address.

2.    Click the Launch UCS Manager link to download the Cisco UCS Manager software.

3.    If prompted to accept security certificates, accept as necessary.

4.    When prompted, enter admin as the user name and enter the administrative password. <<var_password>>

5.    Click Login to log in to Cisco UCS Manager.

6.    Enter the information for the Anonymous Reporting if desired and click OK.

Upgrade Cisco UCS Manager Software to Version 2.2(3g)

This document assumes the use of Cisco UCS Manager Software version 2.2(3g). To upgrade the Cisco UCS Manager software and the UCS 6248 Fabric Interconnect software to version 2.2(3g), refer to Cisco UCS Manager Install and Upgrade Guides.

Add Block of IP Addresses for KVM Access

To create a block of IP addresses for server Keyboard, Video, Mouse (KVM) access in the Cisco UCS environment, complete the following steps:

1.    In Cisco UCS Manager, click the LAN tab in the navigation pane.

2.    Select Pools > root > IP Pools > IP Pool ext-mgmt.

3.    In the Actions pane, select Create Block of IP Addresses.

4.    Enter the starting IP address of the block and the number of IP addresses required, and the subnet and gateway information. <<var_In-band_mgmtblock_net>>

5.    Click OK to create the IP block.

6.    Click OK in the confirmation message.

 

Synchronize Cisco UCS to NTP

To synchronize the Cisco UCS environment to the NTP server, complete the following steps:

1.    In Cisco UCS Manager, click the Admin tab in the navigation pane.

2.    Select All > Timezone Management.

3.    In the Properties pane, select the appropriate time zone in the Timezone menu.

4.    Click Save Changes, and then click OK.

5.    Click Add NTP Server.

6.    Enter <<var_global_ntp_server_ip>> and click OK.

7.    Click OK.

 

Edit Chassis Discovery Policy

Setting the discovery policy simplifies the addition of B-Series Cisco UCS chassis and of additional fabric extenders for further C-Series connectivity. To modify the chassis discovery policy, complete the following steps:

1.    In Cisco UCS Manager, click the Equipment tab in the navigation pane and select Equipment in the list on the left.

2.    In the right pane, click the Policies tab.

3.    Under Global Policies, set the Chassis/FEX Discovery Policy to match the number of uplink ports that are cabled between the chassis or fabric extenders (FEXes) and the fabric interconnects.

4.    Set the Link Grouping Preference to Port Channel.

5.    Click Save Changes.

6.    Click OK.

 

Enable Server and Uplink Ports

To enable server and uplink ports, complete the following steps:

1.    In Cisco UCS Manager, click the Equipment tab in the navigation pane.

2.    Select Equipment > Fabric Interconnects > Fabric Interconnect A (primary) > Fixed Module.

3.    Expand Ethernet Ports.

4.    Select the ports that are connected to the chassis and to the Cisco 2232 FEX (two per FEX), right-click them, and select Configure as Server Port.

 

5.    Click Yes to confirm server ports and click OK.

6.    Verify that the ports connected to the chassis and / or to the Cisco 2232 FEX are now configured as server ports.

 

7.    Select ports 25 and 26 that are connected to the Cisco Nexus switches, right-click them, and select Configure as Uplink Port.

8.    Click Yes to confirm uplink ports and click OK.

9.    Select Equipment > Fabric Interconnects > Fabric Interconnect B (subordinate) > Fixed Module.

10.  Expand Ethernet Ports.

11.  Select the ports that are connected to the chassis and to the Cisco 2232 FEX (two per FEX), right-click them, and select Configure as Server Port.

12.  Click Yes to confirm server ports and click OK.

13.  Select ports 25 and 26 that are connected to the Cisco Nexus switches, right-click them, and select Configure as Uplink Port.

14.  Click Yes to confirm the uplink ports and click OK.

Enable Fibre Channel Ports

To enable server and FC uplink ports, complete the following steps making sure you first reconfigure on the subordinate switch to save time:

1.    On the equipment tab, select the Fabric Interconnect B which should be the subordinate FI, and in the Actions pane, select Configure Unified Ports, and then click Yes.

 

2.    Slide the lever to change the ports 31-32 to change the ports to Fiber Channel. Click Finish then click Yes to the reboot message. Click OK.

 

3.    When the subordinate has completed reboot, select the Fabric Interconnect A, (primary), then select Configure Unified Ports, and click Yes.

4.    Slide the Bar to the left to select ports 31-32 for FC (purple), click Finish, and click Yes to the reboot message. You will need to re-login to the client after the reboot of the FI completes.

Create VSAN for the Fibre Channel Interfaces

To configure the necessary virtual storage area networks (VSANs) for FC uplinks for the Cisco UCS environment, complete the following steps:

1.    In Cisco UCS Manager, click the SAN tab in the navigation pane.

2.    Expand the SAN > SAN Cloud tree. Then fabric A.

3.    Right-click VSANs.

4.    Choose Create VSAN.

5.    Enter VSAN_A as the name of the VSAN for fabric A.

6.    Keep the Disabled option selected for FC Zoning.

7.    Click the Fabric A radio button.

8.    Enter <<var_vsan_a_id>> as the VSAN ID for fabric A.

9.    Enter <<var_fabric_a_fcoe_vlan_id>>as the FCoE VLAN ID for fabric A. and click OK, and click OK again.

 

10.  On the SAN tab, expand SAN, SAN Cloud, Fabric-B and right-click VSANs.

11.  Right-click VSANs and choose Create VSAN.

12.  Enter VSAN_B as the name of the VSAN for fabric B.

13.  Keep the Disabled option selected for FC Zoning.

14.  Click the Fabric B radio button.

15.  Enter <<var_vsan_b_id>> as the VSAN ID for fabric B. Enter <<var_fabric_b_fcoe_vlan_id>> as the FCoE VLAN ID for fabric B, click OK and then click OK again.

 

Create Port Channels for the Fibre Channel Interfaces

To configure the necessary port channels for the Cisco UCS environment, complete the following steps:

Fabric-A

1.    In the navigation pane, under SAN > SAN Cloud, expand the Fabric A tree.

2.    Right-click FC  Port Channels

3.    Choose Create Port Channel.

4.    Enter 1 for the port channel ID and Po1 for the port channel name.

5.    Click Next then choose ports 31 and 32 and click >> to add the ports to the port channel. Click Finish.

 

6.    Check the check box for Show Navigator for FC Port-Channel 1 (Fabric A) and click OK.

 

7.    Under the Vsan drop-down, select vsan 101.

 

8.    Click Apply, and then click OK.

9.    Click OK to close the navigator.

Fabric-B

1.    Click the SAN tab. In the navigation pane, under SAN > SAN Cloud, expand the Fabric B tree.

2.    Right-click FC Port Channels.

3.    Choose Create Port Channel.

4.    Enter 2 for the port channel ID and Po2 for the port channel name.

 

5.    Click Next.

6.    Choose ports 31 and 32 and click >> to add the ports to the port channel.

7.    Click Finish.

8.    Check the check box for Show Navigator for FC Port-Channel 2 (Fabric B).

9.    Under the Vsan drop-down, select VSAN 102, click Apply, and click OK.

10.  To initialize a quick sync of the connections to the MDS switch, right-click the port channel created, and select disable port channel, then re-enable the port channel. Repeat this step for the port channel created for Fabric-A.

 

Acknowledge Cisco UCS Chassis and FEX

To acknowledge all Cisco UCS chassis and external 2232 FEX modules, complete the following steps:

1.    In Cisco UCS Manager, click the Equipment tab in the navigation pane.

2.    Expand Chassis and select each chassis that is listed.

3.    Right-click each chassis and select Acknowledge Chassis, click Yes, then click OK.

 

4.    If C-Series servers are part of the configuration, expand Rack Mounts and FEX.

5.    Right-click each FEX that is listed and select Acknowledge FEX.

 

Create Uplink Port Channels to Cisco Nexus Switches

To configure the necessary port channels out of the Cisco UCS environment, complete the following steps:

1.    In Cisco UCS Manager, click the LAN tab in the navigation pane.

2.    Under LAN > LAN Cloud, expand the Fabric A tree.

3.    Right-click Port Channels.

4.    Select Create Port Channel.

5.    Enter 13 as the unique ID of the port channel.

6.    Enter vPC-13-Nexus as the name of the port channel.

7.    Click Next.

 

8.    Select the following ports to be added to the port channel:

—     Slot ID 1 and port 25

—     Slot ID 1 and port 26

9.    Click >> to add the ports to the port channel.

10.  Click Finish to create the port channel.

11.  Click OK.

12.  In the navigation pane, under LAN > LAN Cloud, expand the fabric B tree.

13.  Right-click Port Channels.

14.  Select Create Port Channel.

15.  Enter 14 as the unique ID of the port channel.

16.  Enter vPC-14-NEXUS as the name of the port channel.

17.  Click Next.

18.  Select the following ports to be added to the port channel:

—     Slot ID 1 and port 25

—     Slot ID 1 and port 26

19.  Click >> to add the ports to the port channel.

20.  Click Finish to create the port channel.

21.  Click OK.

Create MAC Address Pools

To configure the necessary MAC address pools for the Cisco UCS environment, complete the following steps:

1.    In Cisco UCS Manager, click the LAN tab in the navigation pane.

2.    Select Pools > root.

3.    Right-click MAC Pools under the root organization.

4.    Select Create MAC Pool to create the MAC address pool.

 

5.    Enter MAC_Pool_A as the name of the MAC pool.

6.    Optional: Enter a description for the MAC pool.

7.    Click Next.

8.    Click Add.

9.    Specify a starting MAC address.

10.  Specify a size for the MAC address pool that is sufficient to support the available blade or server resources.

 

11.  Click OK.

12.  Click Finish.

13.  In the confirmation message, click OK.

14.  Right-click MAC Pools under the root organization.

15.  Select Create MAC Pool to create the MAC address pool.

16.  Enter MAC_Pool_B as the name of the MAC pool.

17.  Optional: Enter a description for the MAC pool.

18.  Click Next.

19.  Click Add.

20.  Specify a starting MAC address.

21.  Specify a size for the MAC address pool that is sufficient to support the available blade or server resources.

 

22.  Click OK.

23.  Click Finish.

24.  In the confirmation message, click OK.

Create UUID Suffix Pool

To configure the necessary universally unique identifier (UUID) suffix pool for the Cisco UCS environment, complete the following steps:

1.    In Cisco UCS Manager, click the Servers tab in the navigation pane.

2.    Select Pools > root.

3.    Right-click UUID Suffix Pools.

4.    Select Create UUID Suffix Pool.

5.    Enter UUID_Pool as the name of the UUID suffix pool.

6.    Optional: Enter a description for the UUID suffix pool.

7.    Keep the prefix at the derived option.

8.    Click Next.

9.    Click Add to add a block of UUIDs.

10.  Keep the From field at the default setting.

11.  Specify a size for the UUID block that is sufficient to support the available blade or server resources.

 

12.  Click OK.

13.  Click Finish.

14.  Click OK.

Create Server Pool

To configure the necessary server pool for the Cisco UCS environment, complete the following steps:

1.    In Cisco UCS Manager, click the Servers tab in the navigation pane.

2.    Select Pools > root.

3.    Right-click Server Pools.

4.    Select Create Server Pool.

5.    Enter Infra_Pool as the name of the server pool.

6.    Optional: Enter a description for the server pool.

7.    Click Next.

8.    Select two (or more) servers to be used for the VMware management cluster and click >> to add them to the Infra_Pool server pool.

9.    Click Finish.

10.  Click OK.

Create VLANs

To configure the necessary virtual local area networks (VLANs) for the Cisco UCS environment, complete the following steps:

1.    In Cisco UCS Manager, click the LAN tab in the navigation pane.

2.    Select LAN > LAN Cloud.

3.    Right-click VLANs.

4.    Select Create VLANs.

5.    Enter IB-MGMT-VLAN as the name of the VLAN to be used for management traffic.

6.    Keep the Common/Global option selected for the scope of the VLAN.

7.    Enter <<var_ib-mgmt_vlan_id>> as the ID of the management VLAN.

8.    Keep the Sharing Type as None.

9.    Click OK and then click OK again.

 

10.  Right-click VLANs.

11.  Select Create VLANs.

12.  Enter NFS-VLAN as the name of the VLAN to be used for NFS.

13.  Keep the Common/Global option selected for the scope of the VLAN.

14.  Enter the <<var_nfs_vlan_id>> for the NFS VLAN.

15.  Keep the Sharing Type as None.

16.  Click OK, and then click OK again.

17.  Right-click VLANs.

18.  Select Create VLANs.

19.  Enter vMotion-VLAN as the name of the VLAN to be used for vMotion.

20.  Keep the Common/Global option selected for the scope of the VLAN.

21.  Enter the <<var_vmotion_vlan_id>> as the ID of the vMotion VLAN.

22.  Keep the Sharing Type as None.

23.  Click OK, and then click OK again.

24.  Right-click VLANs.

25.  Select Create VLANs.

26.  Enter VM-Traffic-VLAN as the name of the VLAN to be used for the VM traffic.

27.  Keep the Common/Global option selected for the scope of the VLAN.

28.  Enter the <<var_vm-traffic_vlan_id>> for the VM Traffic VLAN.

29.  Keep the Sharing Type as None.

30.  Click OK, and then click OK again.

31.  Right-click VLANs.

32.  Select Create VLANs.

33.  Enter Native-VLAN as the name of the VLAN to be used as the native VLAN.

34.  Keep the Common/Global option selected for the scope of the VLAN.

35.  Enter the <<var_native_vlan_id>> as the ID of the native VLAN.

36.  Keep the Sharing Type as None.

37.  Click OK and then click OK again.

38.  Expand the list of VLANs in the navigation pane, right-click the newly created Native-VLAN and select Set as Native VLAN.

39.  Click Yes and then click OK.

Create Host Firmware Package

Firmware management policies allow the administrator to select the corresponding packages for a given server con-figuration. These policies often include packages for adapter, BIOS, board controller, FC adapters, host bus adapter (HBA) option ROM, and storage controller properties. To create a firmware management policy for a given server configuration in the Cisco UCS environment, complete the following steps:

1.    In Cisco UCS Manager, click the Servers tab in the navigation pane.

2.    Select Policies > root.

3.    Right-click Host Firmware Packages.

4.    Select Create Host Firmware Package

5.    Enter VM-Host-Infra as the name of the host firmware package.

6.    Leave Simple selected.

7.    Select the version 2.2(3g) for both the Blade and Rack Packages.

8.    Click OK to create the host firmware package.

9.    Click OK.

 

Set Jumbo Frames in Cisco UCS Fabric

To configure jumbo frames and enable quality of service in the Cisco UCS fabric, complete the following steps:

1.    In Cisco UCS Manager, click the LAN tab in the navigation pane.

2.    Select LAN > LAN Cloud > QoS System Class.

3.    In the right pane, click the General tab.

4.    On the Best Effort row, enter 9216 in the box under the MTU column.

5.    Click Save Changes in the bottom of the window.

6.    Click OK.

 

Create Local Disk Configuration Policy (Optional)

A local disk configuration for the Cisco UCS environment is necessary if the servers in the environment do not have a local disk.

To create a local disk configuration policy, complete the following steps:

1.    In Cisco UCS Manager, click the Servers tab in the navigation pane.

2.    Select Policies > root.

3.    Right-click Local Disk Config Policies.

4.    Select Create Local Disk Configuration Policy.

5.    Enter SAN-Boot as the local disk configuration policy name.

6.    Change the mode to No Local Storage.

7.    Click OK to create the local disk configuration policy.

8.    Click OK.

 

Create Network Control Policy for Cisco Discovery Protocol

To create a network control policy that enables Cisco Discovery Protocol (CDP) on virtual network ports, complete the following steps:

1.    In Cisco UCS Manager, click the LAN tab in the navigation pane.

2.    Select Policies > root.

3.    Right-click Network Control Policies.

4.    Select Create Network Control Policy.

5.    Enter Enable_CDP as the policy name.

6.    For CDP, select the Enabled option.

7.    Click OK to create the network control policy.

 

8.    Click OK.

Create Power Control Policy

To create a power control policy for the Cisco UCS environment, complete the following steps:

1.    In Cisco UCS Manager, click the Servers tab in the navigation pane.

2.    Select Policies > root.

3.    Right-click Power Control Policies.

4.    Select Create Power Control Policy.

5.    Enter No-Power-Cap as the power control policy name.

6.    Change the power capping setting to No Cap.

7.    Click OK to create the power control policy.

8.    Click OK.

 

Create Server Pool Qualification Policy (Optional)

To create an optional server pool qualification policy for the Cisco UCS environment, complete the following steps:

1.    In Cisco UCS Manager, click the Servers tab in the navigation pane.

2.    Select Policies > root.

3.    Right-click Server Pool Policy Qualifications.

4.    Select Create Server Pool Policy Qualification.

5.    Enter UCSB-B200-M4 as the name for the policy.

6.    Select Create Server PID Qualifications.

7.    Enter UCSB-B200-M4 as the PID.

8.    Click OK to create the server pool qualification policy.

9.    Click OK and then click OK again.

Create Server BIOS Policy

To create a server BIOS policy for the Cisco UCS environment, complete the following steps:

1.    In Cisco UCS Manager, click the Servers tab in the navigation pane.

2.    Select Policies > root.

3.    Right-click BIOS Policies.

4.    Select Create BIOS Policy.

5.    Enter VM-Host-Infra as the BIOS policy name.

6.    Change the Quiet Boot setting to Disabled.

7.    Click Next.

8.    Change Turbo Boost to Enabled.

9.    Change Enhanced Intel Speedstep to Enabled.

10.  Change Hyper Threading to Enabled.

11.  Change Core Multi Processing to all.

12.  Change Execution Disabled Bit to Enabled.

13.  Change Virtualization Technology (VT) to Enabled.

14.  Change Direct Cache Access to Enabled.

15.  Change CPU Performance to Enterprise.

 

16.  Click next to go the Intel Directed IO Screen.

17.  Change the VT for Direct IO to Enabled.

18.  Click next to go the RaS Memory screen.

19.  Change the Memory RAS Config to maximum performance.

20.  Change NUMA to Enabled.

21.  Change LV DDR Mode to performance-mode.

22.  Click Finish to create the BIOS policy.

23.  Click OK.

Create vNIC/vHBA Placement Policy for Virtual Machine Infrastructure Hosts

To create a vNIC/vHBA placement policy for the infrastructure hosts, complete the following steps:

1.    In Cisco UCS Manager, click the Servers tab in the navigation pane.

2.    Select Policies > root.

3.    Right-click vNIC/vHBA Placement Policies.

4.    Select Create Placement Policy.

5.    Enter VM-Host-Infra as the name of the placement policy.

6.    Click 1 and select Assigned Only.

7.    Click OK and then click OK again.

 

Update Default Maintenance Policy

To update the default Maintenance Policy, complete the following steps:

1.    In Cisco UCS Manager, click the Servers tab in the navigation pane.

2.    Select Policies > root.

3.    Select Maintenance Policies > default.

4.    Change the Reboot Policy to User Ack.

5.    Click Save Changes.

6.    Click OK to accept the change.

 

Create vNIC Templates

To create multiple virtual network interface card (vNIC) templates for the Cisco UCS environment, complete the following steps:

1.    In Cisco UCS Manager, click the LAN tab in the navigation pane.

2.    Select Policies > root.

3.    Right-click vNIC Templates.

4.    Select Create vNIC Template.

5.    Enter vNIC_Template_A as the vNIC template name.

6.    Keep Fabric A selected.

7.    Select the Enable Failover checkbox.

8.    Under Target, make sure that the VM checkbox is not selected.

9.    Select Updating Template as the Template Type.

10.  Under VLANs, select the checkboxes for IB-MGMT-VLAN, NFS-VLAN, Native-VLAN, VM-Traffic-VLAN, and vMotion-VLAN.

11.  Set Native-VLAN as the native VLAN.

12.  For MTU, enter 9000.

13.  In the MAC Pool list, select MAC_Pool_A.

14.  In the Network Control Policy list, select Enable_CDP.

15.  Click OK to create the vNIC template.

16.  Click OK.

 

17.  In the navigation pane, select the LAN tab.

18.  Select Policies > root.

19.  Right-click vNIC Templates.

20.  Select Create vNIC Template.

21.  Enter vNIC_Template_B as the vNIC template name.

22.  Select Fabric B.

23.  Select the Enable Failover checkbox.

24.  Select Updating Template as the template type.

25.  Under VLANs, select the checkboxes for IB-MGMT-VLAN, NFS-VLAN, Native-VLAN, VM-Traffic-VLAN, and vMotion-VLAN.

26.  Set Native-VLAN as the native VLAN.

27.  For MTU, enter 9000.

28.  In the MAC Pool list, select MAC_Pool_B.

29.  In the Network Control Policy list, select Enable_CDP.

30.  Click OK to create the vNIC template.

31.  Click OK.

Create WWNN Pools

To configure the necessary World Wide Node Name (WWNN) pools for the Cisco UCS environment, complete the following steps:

1.    In Cisco UCS Manager, click the SAN tab in the navigation pane.

2.    Choose Pools > root.

3.    Right-click WWNN Pools.

4.    Choose Create WWNN Pool.

5.    Enter WWNN_Pool as the name of the WWNN pool.

6.    (Optional) Add a description for the WWNN pool.

7.    Click Next.

8.    Click Add to add a block of WWNNs.

9.    Keep the default block of WWNNs, or specify a base WWNN.

10.  Specify a size for the WWNN block that is sufficient to support the available blade or server resources.

11.  Click OK.

12.  Click Finish.

13.  Click OK.

 

Create WWPN Pools

To configure the necessary World Wide Port Name (WWPN) pools for the Cisco UCS environment, complete the following steps:

1.    In Cisco UCS Manager, click the SAN tab in the navigation pane.

2.    Choose Pools > root.

3.    Right-click WWPN Pools.

4.    Choose Create WWPN Pool.

5.    Enter WWPN_Pool_A as the name of the WWPN pool for fabric A.

6.    (Optional) Enter a description for this WWPN pool.

7.    Click Next.

8.    Click Add to add a block of WWPNs.

9.    Specify the starting WWPN in the block for fabric A.

10.  Specify a size for the WWPN block that is sufficient to support the available blade or server resources.

11.  Click OK.

12.  Click Finish to create the WWPN pool.

13.  Click OK.

 

14.  Right-click WWPN Pools.

15.  Choose Create WWPN Pool.

16.  Enter WWPN_Pool_B as the name for the WWPN pool for fabric B.

17.  (Optional) Enter a description for this WWPN pool.

18.  Click Next.

19.  Click Add to add a block of WWPNs.

20.  Enter the starting WWPN address in the block for fabric B.

21.  Specify a size for the WWPN block that is sufficient to support the available blade or server resources.

22.  Click OK.

23.  Click Finish.

24.  Click OK.

Create vHBA Templates for Fabric A and Fabric B

To create multiple virtual host bus adapter (vHBA) templates for the Cisco UCS environment, follow these steps:

1.    In Cisco UCS Manager, click the SAN tab in the navigation pane.

2.    Choose Policies > root.

3.    Right-click vHBA Templates.

4.    Choose Create vHBA Template.

5.    Enter vHBA_Template_A as the vHBA template name.

6.    Click the radio button Fabric A.

7.    In the Select VSAN list, Choose VSAN_A.

8.    In the WWPN Pool list, Choose WWPN_Pool_A.

9.    Click OK to create the vHBA template.

10.  Click OK.

 

11.  In the navigation pane, click the SAN tab.

12.  Choose Policies > root.

13.  Right-click vHBA Templates.

14.  Choose Create vHBA Template.

15.  Enter vHBA_Template_B as the vHBA template name.

16.  Click the radio button Fabric B.

17.  In the Select VSAN list, Choose VSAN_B.

18.  In the WWPN Pool, Choose WWPN_Pool_B.

19.  Click OK to create the vHBA template.

20.  Click OK.

 

Create Boot Policies

This procedure applies to a Cisco UCS environment in which two FC interfaces are used on the IBM V7000 Storwize cluster node 1 and two FC interfaces are used on cluster node 2. In addition, it is assumed that the A interfaces are connected to fabric A and the B interfaces are connected to fabric B.

Two boot policies are configured in this procedure. The first policy configures the primary target to be fcp_lif01a and the second boot policy configures the primary target to be fcp_lif01b.

To create boot policies for the Cisco UCS environment, complete the following steps:

1.    In Cisco UCS Manager, click the Servers tab in the navigation pane.

2.    Choose Policies > root.

3.    Right-click Boot Policies.

4.    Choose Create Boot Policy.

5.    Enter Boot-Fabric-A as the name of the boot policy.

6.    (Optional) Enter a description for the boot policy.

7.    Keep the Reboot on Boot Order Change check box unchecked.

8.    Expand the Local Devices drop-down menu and Choose Add CD/DVD (you should see local and remote greyed out).

 

9.    Expand the vHBAs drop-down menu and Choose Add SAN Boot.

10.  In the Add SAN Boot dialog box, enter Fabric-A in the vHBA field.

11.  Make sure that the Primary radio button is selected as the SAN boot type.

12.  Click OK to add the SAN boot initiator.

 

13.  From the vHBA drop-down menu, choose Add SAN Boot Target.

14.  Keep 0 as the value for Boot Target LUN.

15.  Enter the WWPN for node 1 going to switch A  << var_wwpn_FC_NodeA-fabricA >>.

16.  Keep the Primary radio button selected as the SAN boot target type.

17.  Click OK to add the SAN boot target.

 

18.  From the vHBA drop-down menu, choose Add SAN Boot Target.

19.  Keep 0 as the value for Boot Target LUN.

20.  Enter the WWPN for node 2 going to switch A  << var_wwpn_FC_NodeC-fabricA >>.

21.  Click OK to add the SAN boot target.

 

22.  From the vHBA drop-down menu, choose Add SAN Boot.

23.  In the Add SAN Boot dialog box, enter Fabric-B in the vHBA box.

24.  The SAN boot type should automatically be set to Secondary.

25.  Click OK to add the SAN boot initiator.

 

26.  From the vHBA drop-down menu, choose Add SAN Boot Target.

27.  Keep 0 as the value for Boot Target LUN.

28.  Enter the WWPN  for node C switch  B  << var_wwpn_FC_NodeC-fabricB >>.

29.  Keep Primary as the SAN boot target type.

30.  Click OK to add the SAN boot target.

 

31.  From the vHBA drop-down menu, choose Add SAN Boot Target.

32.  Keep 0 as the value for Boot Target LUN.

33.  Enter the WWPN for  Node A switch B << var_wwpn_FC_NodeA-fabricB >>.

34.  Click OK to add the SAN boot target.

 

35.  Click OK, and then click OK again to create the boot policy.

36.  Right-click Boot Policies again.

37.  Choose Create Boot Policy.

38.  Enter Boot-Fabric-B as the name of the boot policy.

39.  (Optional) Enter a description of the boot policy.

40.  Keep the Reboot on Boot Order Change check box unchecked.

41.  From the Local Devices drop-down menu choose Add CD/DVD.

42.  From the vHBA drop-down menu, choose Add SAN Boot.

43.  In the Add SAN Boot dialog box, enter Fabric-B in the vHBA box.

44.  Make sure that the Primary radio button is selected as the SAN boot type.

45.  Click OK to add the SAN boot initiator.

46.  From the vHBA drop-down menu, choose Add SAN Boot Target.

47.  Keep 0 as the value for Boot Target LUN.

48.  Enter the WWPN for var NodeA Switch-B. << var_wwpn_FC_NodeA-fabricB >>.

49.  Keep Primary as the SAN boot target type.

50.  Click OK to add the SAN boot target.

51.  From the vHBA drop-down menu, choose Add SAN Boot Target.

52.  Keep 0 as the value for Boot Target LUN.

53.  Enter the WWPN for Node C Switch-B << var_wwpn_FC_NodeC-fabricB >>

54.  Click OK to add the SAN boot target.

55.  From the vHBA menu, choose Add SAN Boot.

56.  In the Add SAN Boot dialog box, enter Fabric-A in the vHBA box.

57.  The SAN boot type should automatically be set to Secondary, and the Type option should be unavailable.

58.  Click OK to add the SAN boot initiator.

59.  From the vHBA menu, choose Add SAN Boot Target.

60.  Keep 0 as the value for Boot Target LUN.

61.  Enter the WWPN for Node C Switch A  << var_wwpn_FC_NodeC-fabricA >>

62.  Keep Primary as the SAN boot target type.

63.  Click OK to add the SAN boot target.

64.  From the vHBA drop-down menu, choose Add SAN Boot Target.

65.  Keep 0 as the value for Boot Target LUN.

66.  Enter the WWPN for  Node A SwitchA. << var_wwpn_FC_NodeA-fabricA >>.

67.  Click OK to add the SAN boot target.

68.  Click OK and then click OK again to create the boot policy.

 

Create Service Profile Templates

In this procedure, two service profile templates are created: one for fabric A boot and one for fabric B boot. The first profile is created and then cloned and modified for the second host.

To create service profile templates, follow these steps:

1.    In Cisco UCS Manager, click the Servers tab in the navigation pane.

2.    Choose Service Profile Templates > root.

3.    Right-click root.

4.    Choose Create Service Profile Template to open the Create Service Profile Template wizard.

5.    Identify the Service Profile Template:

a.     Enter VM-Host-Infra-Fabric-A as the name of the service profile template. This service profile template is configured to boot from node 1 on fabric A.

b.    Click the Updating Template radio button.

c.     Under UUID, choose UUID_Pool as the UUID pool.

d.    Click Next.

 

6.    Configure the Networking options:

a.     Keep the default setting for Dynamic vNIC Connection Policy.

b.    Click the Expert radio button to configure the LAN connectivity.

c.     Click Add to add a vNIC to the template.

d.    In the Create vNIC dialog box, enter vNIC-A as the name of the vNIC.

e.    Check the Use vNIC Template check box.

f.      In the vNIC Template list, choose vNIC_Template_A.

g.    In the Adapter Policy list, choose VMWare.

h.     Click OK to add this vNIC to the template.

 

i.      On the Networking page of the wizard, click Add to add another vNIC to the template.

j.      In the Create vNIC box, enter vNIC-B as the name of the vNIC.

k.     Check the Use vNIC Template check box.

l.      In the vNIC Template list, choose vNIC_Template_B.

m.   In the Adapter Policy list, choose VMWare.

n.     Click OK to add the vNIC to the template.

o.    Review the table in the Networking page to make sure that both vNICs were created.

p.    Click Next.

 

7.    Configure the Storage options:

a.     Choose a local disk configuration policy:

b.    If the server in question has local disks, choose default in the Local Storage list.

c.     If the server in question does not have local disks, choose SAN-Boot.

d.    Click the Expert radio button to configure the SAN connectivity.

e.    In the WWNN Assignment list, choose WWNN_Pool.

 

f.      Click Add at the bottom of the page to add a vHBA to the template.

g.    In the Create vHBA dialog box, enter Fabric-A as the name of the vHBA.

h.     Check the Use vHBA Template check box.

i.      In the vHBA Template list, choose vHBA_Template_A.

j.      In the Adapter Policy list, choose VMware.

k.     Click OK to add this vHBA to the template.

 

l.      On the Storage page of the wizard, click Add at the bottom of the page to add another vHBA to the template.

m.   In the Create vHBA dialog box, enter Fabric-B as the name of the vHBA.

n.     Check the check box for Use HBA Template.

o.    In the vHBA Template list, choose vHBA_Template_B.

p.    In the Adapter Policy list, choose VMware.

q.    Click OK to add the vHBA to the template.

r.     Review the table in the Storage page to verify that both A and B vHBAs were created.

s.     Click Next.

 

8.    Set no Zoning options and click Next.

9.    Set the vNIC/vHBA placement options.

a.     In the Select Placement list, choose the VM-Host-Infra placement policy.

b.    Choose vCon1 and assign the vHBAs/vNICs to the virtual network interfaces policy in the following order:

—     vHBA Fabric-A

—     vHBA Fabric-B

—     vNIC-A

—     vNIC-B

c.     Review the table to verify that all vNICs and vHBAs were assigned to the policy in the appropriate order.

d.    Click Next.

 

10.  Click next to bypass the vMedia policy screen.

11.  Set the Server Boot Order:

a.     In the Boot Policy list, choose Boot-Fabric-A.

b.    Review the table to verify that all boot devices were created and identified. Verify that the boot devices are in the correct boot sequence.

c.     Click Next.

 

12.  Add a Maintenance Policy:

a.     Choose the Default Maintenance Policy.

b.    Click Next.

 

13.  Specify the Server Assignment:

a.     In the Pool Assignment list, choose Infra_Pool.

b.    (Optional) Choose a Server Pool Qualification policy.

c.     Choose Down as the power state to be applied when the profile is associated with the server.

d.    Expand Firmware Management at the bottom of the page and choose VM-Host-Infra from the Host Firmware list.

e.    Click Next.

 

14.  Add Operational Policies:

a.     In the BIOS Policy list, choose VM-Host-Infra.

b.    Expand Power Control Policy Configuration and choose No-Power-Cap in the Power Control Policy list.

 

15.  Click Finish to create the service profile template.

16.  Click OK in the confirmation message.

17.  Click the Servers tab in the navigation pane.

18.  Choose Service Profile Templates > root.

19.  Right-click the previously created VM-Host-Infra-Fabric-A template.

20.  Choose Create a Clone.

21.  In the dialog box, enter VM-Host-Infra-Fabric-B as the name of the clone, choose the root Org, and click OK.

 

22.  Click OK.

23.  Choose the newly cloned service profile template and click the Boot Order tab.

 

24.  Click Modify Boot Policy.

25.  In the Boot Policy list, choose Boot-Fabric-B.

 

26.  Click OK and then click OK again.

27.  In the right pane, click the Network tab and then click Modify vNIC/HBA Placement.

28.  Select VM-Host-Infra and Expand vCon 1 and move vHBA Fabric-B ahead of vHBA Fabric-A in the placement order.

29.  Click OK and then click OK again.

Create Service Profiles

To create service profiles from the service profile template, complete the following steps:

1.    In Cisco UCS Manager, click the Servers tab in the navigation pane.

2.    Choose Service Profile Templates > root > Service Template VM-Host-Infra-Fabric-A.

3.    Right-click VM-Host-Infra-Fabric-A and choose Create Service Profiles from Template.

4.    Enter VM-Host-Infra-0 as the service profile prefix.

5.    Enter 1 as the Name Suffix Staring Number.

6.    Enter 1 as the Number of Instances.

7.    Click OK to create the service profile.

 

8.    Click OK in the confirmation message.

9.    Choose Service Profile Templates > root > Service Template VM-Host-Infra-Fabric-B.

10.  Right-click VM-Host-Infra-Fabric-B and choose Create Service Profiles from Template.

11.  Enter VM-Host-Infra-0 as the service profile prefix.

12.  Enter 2 as the Name Suffix Staring Number.

13.  Enter 1 as the Number of Instances.

14.  Click OK to create the service profile.

 

15.  Click OK in the confirmation message.

16.  Verify that the service profiles VM-Host-Infra-01 and VM-Host-Infra-02 have been created. The service profiles are automatically associated with the servers in their assigned server pools.

17.  (Optional) Choose each newly created service profile and enter the server host name or the FQDN in the User Label field in the General tab. Click Save Changes to map the server host name to the service profile name.

Backup the Cisco UCS Manager Configuration

It is recommended that you backup your Cisco UCS Configuration. Please refer to the link below for additional information:

http://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/sw/gui/config/guide/2-2/b_UCSM_GUI_Configuration_Guide_2_2/b_UCSM_GUI_Configuration_Guide_2_2_chapter_0101010.html

Adding Servers

Additional server pools, service profile templates, and service profiles can be created in the respective organizations to add more servers to the Pod unit. All other pools and policies are at the root level and can be shared among the organizations.

Gather Necessary WWPN Information

After the Cisco UCS service profiles have been created, each infrastructure blade in the environment will have a unique configuration. To proceed with the SAN-BOOT deployment, specific information must be gathered from each Cisco UCS blade and from the IBM controllers. Insert the required information in the table below.

1.    To gather the vHBA WWPN information, launch the Cisco UCS Manager GUI. In the navigation pane, click the Servers tab. Expand Servers > Service Profiles > root. Click each service profile and expand to see vHBAs.

2.    Click vHBA Fabric-A, in the general tab right-click the WWPN and click Copy.

 

 

3.    Record the WWPN information that is displayed for both the Fabric A vHBA and the Fabric B vHBA for each service profile into the WWPN variable table provided.

          

Cisco MDS 9148S Compute SAN Zoning

The steps provided in this section will configure zoning for the WWPN's from the server and the StorwizeV7000. You will use the WWPN information collected in the previous steps for both the storage setup, and for server profile creation. There are three zones created, two for servers and one zone for cluster communication. If adding more Storwize V7000 control nodes, you will add the WWPN's to the cluster communication zone used below named V7000-cluster-comm.

Cisco MDS - A Switch

1.    Log in to the  MDS switch and complete the following steps to create the WWPN aliases:

config

Enter configuration commands, one per line.  End with CNTL/Z.

device-alias database

device-alias name VM-Host-Infra-01-A pwwn var_wwpn_VM-Host-Infra-01-A

device-alias name VM-Host-Infra-02-A pwwn var_wwpn_VM-Host-Infra-02-A

device-alias commit

2.    Create the zones and add device-alias members for the 2 blade servers and 1  zone for V7000 cluster  communications.

zone name  VM-Host-Infra-01-A vsan 101

member device-alias  VM-Host-Infra-01-A

member device-alias VersaStack-NodeA

member device-alias VersaStack-NodeB

member device-alias VersaStack-NodeC

member device-alias VersaStack-NodeD

exit

zone name  VM-Host-Infra-02-A vsan 101

member device-alias  VM-Host-Infra-02-A

member device-alias VersaStack-NodeA

member device-alias VersaStack-NodeB

member device-alias VersaStack-NodeC

member device-alias VersaStack-NodeD

exit

3.    Add zones to  zoneset.

zoneset name versastackzoneset vsan 101

member VM-Host-Infra-01-A

member VM-Host-Infra-02-A

exit

4.    Activate the zoneset.

zoneset activate  name versastackzoneset vsan 101

5.    Validate all powered on systems HBA's are logged into the switch through the show zoneset command.

sh zoneset active 

 

6.    Save the configuration.

copy run start

Cisco MDS - B Switch

1.    Log in to the MDS switch and complete the following steps to create the WWPN aliases:

config

Enter configuration commands, one per line.  End with CNTL/Z.

device-alias database

device-alias name VM-Host-Infra-01-B pwwn var_wwpn_VM-Host-Infra-01-B 

device-alias name VM-Host-Infra-02-B pwwn var_wwpn_VM-Host-Infra-02-B

device-alias commit

2.    Create the zones and add device-alias members for the two blade servers and one zone for V7000 cluster communications.

zone name  VM-Host-Infra-01-B vsan 102

member device-alias  VM-Host-Infra-01-B

member device-alias VersaStack-NodeA

member device-alias VersaStack-NodeB

member device-alias VersaStack-NodeC

member device-alias VersaStack-NodeD

exit

zone name  VM-Host-Infra-02-B vsan 102

member device-alias  VM-Host-Infra-02-B

member device-alias VersaStack-NodeA

member device-alias VersaStack-NodeB

member device-alias VersaStack-NodeC

member device-alias VersaStack-NodeD

exit

3.    Add zones to  zoneset.

zoneset name versastackzoneset vsan 102

member VM-Host-Infra-01-B

member VM-Host-Infra-02-B

4.    Activate the zoneset.

zoneset activate  name versastackzoneset vsan 102

5.    Validate the all powered on systems HBA's are logged into the switch.

sh zoneset active

6.    Save the configuration.

copy run start

Storage LUN Mapping

In this section, you will add the host mappings for the host profiles created through the Cisco UCS Manager to the V7000 storage, connecting to the boot LUNs, and doing the initial ESXi install. The WWPN's for the hosts will be required to complete this section.

Adding Hosts and Mapping the Boot Volumes on the IBM Storwize V7000

To add hosts and to map the boot volumes on the IBM Storwize V7000, complete the following steps:

1.    Open the Storwize V7000 management GUI by navigating to <<var_cluster_mgmt_ip>>and log in with your superuser or admin account.

2.    In the left pane click Host icon, and click the Hosts menu item.

3.    Click Add Host in the upper left menu to bring up the Host wizard. Select the Fiber Channel Host option.

4.    Input Host Name VM-Host-Infra-01.

5.    For Fibre Channel Ports open the drop-down menu and select or input the WWPN's for the A path vHBA's,  <<var_wwpn_VM-Host-infra-01-a>>, and click Add Port to List.

6.    Click the drop-down menu again, and select or Input the host B port <<wwpn_VM-Host-infra-01-b>> and click add port to list.

7.    Leave Advanced Settings as default and click Add Host, then click Close.

8.    Click Add Host to create the second host.

9.    Select the Fiber Channel Host option.

10.  For Host Name input VM-Host-Infra-02.

11.  For Fibre Channel Ports open the drop-down menu and select the WWPN's for the A path vHBA's,  <<var_wwpn_VM-Host-infra-02-a>>, and click Add Port to List.

12.  Select the B port by selecting the var for the B path <<wwpn_VM-Host-infra-02-b>> and click Add Port To List. Leave the Advanced Settings as default and click Add Host, then click Close.

 

13.  Click the Volumes icon in the left pane, then click the volumes menu item to display the created volumes.

14.  Right-click the volume VM-Host-Infra-01 and select Map to Host.

 

15.  In the drop-down, leave ALL I/O  Groups enabled, and  select VM-Host-Infra-01.

 

16.  Select Map Volumes then click Close.

 

17.  Right-click the volume VM-Host-Infra-02 and click Map to host.

18.  In the drop-down, leave ALL I/O  Groups enabled, and  select VM-Host-Infra-02.

 

19.  Select Map Volumes and then click Close.

 

ESX and vSphere Installation and Setup

VersaStack VMware ESXi 5.5 Update 2 SAN Boot Installation

This section provides detailed instructions for installing VMware ESXi 5.5 Update 2 in a VersaStack environment. After the procedures are completed, two San-booted ESXi hosts will be provisioned. These deployment procedures are customized to include the environment variables.

https://my.vmware.com/web/vmware/details?downloadGroup=OEM-ESXI55U2-CISCO&productId=353

Log in to Cisco UCS 6200 Fabric Interconnect

Cisco UCS Manager

The IP KVM enables the administrator to begin the installation of the operating system (OS) through remote media. It is necessary to log in to the Cisco UCS environment to run the IP KVM.

To log in to the Cisco UCS environment, complete the following steps:

1.    Download the Cisco Custom ISO for ESXi from the VMware website.

2.    Open a web browser and enter the IP address for the Cisco UCS cluster address. This step launches the Cisco UCS Manager application.

3.    Log in to Cisco UCS Manager by using the admin user name and password.

4.    From the main menu, click the Servers tab.

5.    Select Servers > Service Profiles > root > VM-Host-Infra-01.

6.    Right-click VM-Host-Infra-01 and select KVM Console.

7.    Select Servers > Service Profiles > root > VM-Host-Infra-02.

8.    Right-click VM-Host-Infra-02 and select KVM Console Actions > KVM Console.

 

VMware ESXi Installation

ESXi Hosts VM-Host-Infra-01 and VM-Host-Infra-02

To prepare the server for the OS installation, complete the following steps on each ESXi host:

1.    In the KVM window, click Virtual Media.

2.    Click Activate Virtual Devices, select Accept this Session, then Apply.

3.    Select Virtual Media, Map CD/DVD, then browse to the ESXi installer ISO image file and click Open.

4.    Select the Map Device to map the newly added image.

 

5.    Select Reset, then Ok and allow a power cycle and click the KVM tab to monitor the server boot.

6.    As an alternate method if the server is powered on, first shutdown the server, then boot the server by selecting Boot Server and clicking OK, then click OK again.

Install ESXi

ESXi Hosts VM-Host-Infra-01 and VM-Host-Infra-02

To install VMware ESXi to the SAN-bootable LUN of the hosts, complete the following steps on each host:

1.    On boot, the machine detects the presence of the ESXi installation media. Select the ESXi installer from the menu that is displayed.

2.    After the installer is finished loading, press Enter to continue with the installation.

3.    Read and accept the end-user license agreement (EULA). Press F11 to accept and continue.

4.    Select the IBM LUN that was previously set up as the installation disk for ESXi and press Enter to continue with the installation.

5.    Select the appropriate keyboard layout and press Enter.

6.    Enter and confirm the root password and press Enter.

7.    The installer issues a warning that existing partitions will be removed from the volume. Press F11 to continue with the installation.

8.    After the installation is completes, hitting Enter will reboot the server. The ISO is automatically unmapped

Set Up Management Networking for ESXi Hosts

Adding a management network for each VMware host is necessary for managing the host. To add a management network for the VMware hosts, complete the following steps on each ESXi host as detailed in this section.

ESXi Host VM-Host-Infra-01

To configure the VM-Host-Infra-01 ESXi host with access to the management network, complete the following steps:

1.    After the server has finished rebooting, press F2 to customize the system.

2.    Log in as root and enter the corresponding password.

3.    Select the Configure the Management Network option and press Enter.

4.    Select the VLAN (Optional) option and press Enter.

5.    Enter the <<var_ib-mgmt_vlan_id>> and press Enter.

6.    From the Configure Management Network menu, select IP Configuration and press Enter.

7.    Select the Set Static IP Address and Network Configuration option by using the space bar.

8.    Enter the IP address for managing the first ESXi host: <<var_vm_host_infra_01_ip>>.

9.    Enter the subnet mask for the first ESXi host.

10.  Enter the default gateway for the first ESXi host.

11.  Press Enter to accept the changes to the IP configuration.

12.  Select the IPv6 Configuration option and press Enter.

13.  Using the spacebar, unselect Enable IPv6 (restart required) and press Enter.

14.  Select the DNS Configuration option and press Enter.

15.  Enter the IP address of the primary DNS server.

16.  Optional: Enter the IP address of the secondary DNS server.

17.  Enter the fully qualified domain name (FQDN) for the first ESXi host.

18.  Press Enter to accept the changes to the DNS configuration.

19.  Press Esc to exit the Configure Management Network submenu.

20.  Press Y to confirm the changes and restart the host.

21.  The ESXi host reboots. After reboot, press F2 and log back in as root.

22.  Select Test Management Network to verify that the management network is set up correctly and press Enter.

23.  Press Enter to run the test.

24.  Press Enter to exit the window.

25.  Press Esc to log out of the VMware console.

ESXi Host VM-Host-Infra-02

To configure the VM-Host-Infra-02 ESXi host with access to the management network, complete the following steps:

1.    After the server has finished rebooting, press F2 to customize the system.

2.    Log in as root and enter the corresponding password.

3.    Select the Configure the Management Network option and press Enter.

4.    Select the VLAN (Optional) option and press Enter.

5.    Enter the <<var_ib-mgmt_vlan_id>> and press Enter.

6.    From the Configure Management Network menu, select IP Configuration and press Enter.

7.    Select the Set Static IP Address and Network Configuration option by using the space bar.

8.    Enter the IP address for managing the second ESXi host: <<var_vm_host_infra_02_ip>>.

9.    Enter the subnet mask for the second ESXi host.

10.  Enter the default gateway for the second ESXi host.

11.  Press Enter to accept the changes to the IP configuration.

12.  Select the IPv6 Configuration option and press Enter.

13.  Using the spacebar, unselect Enable IPv6 (restart required) and press Enter.

14.  Select the DNS Configuration option and press Enter.

15.  Enter the IP address of the primary DNS server.

16.  Optional: Enter the IP address of the secondary DNS server.

17.  Enter the FQDN for the second ESXi host.

18.  Press Enter to accept the changes to the DNS configuration.

19.  Press Esc to exit the Configure Management Network submenu.

20.  Press Y to confirm the changes and restart the host.

21.  The ESXi host reboots. After reboot, press F2 and log back in as root.

22.  Select Test Management Network to verify that the management network is set up correctly and press Enter.

23.  Press Enter to run the test.

24.  Press Enter to exit the window.

25.  Press Esc to log out of the VMware console.

vSphere Setup and ESXi Configuration

In this section, you will set up the VSphere environment using Windows 2008 and SQL server. The Virtual machines used in this procedure is installed on a local Datastore one VersaStack for any Greenfield deployments, however these could be install on a different ESX clustered system or physical hardware if desired. This procedure will use the volumes previously created for VMFS Datastores.

Download VMware vSphere Client and vSphere Remote CLI

To download the VMware vSphere Client and install Remote CLI, complete the following steps:

1.    Open a web browser on the management workstation and navigate to the VM-Host-Infra-01 management IP address.

2.    Download and install both the vSphere Client and the Windows version of vSphere Remote Command Line.

Log in to VMware ESXi Hosts Using VMware vSphere Client

ESXi Host VM-Host-Infra-01

To log in to the VM-Host-Infra-01 ESXi host by using the VMware vSphere Client, complete the following steps:

1.    Open the recently downloaded VMware vSphere Client and enter the IP address of VM-Host-Infra-01 as the host you are trying to connect to:<<var_vm_host_infra_01_ip>>.

2.    Enter root for the user name.

3.    Enter the root password.

4.    Click Login to connect.

ESXi Host VM-Host-Infra-02

To log in to the VM-Host-Infra-02 ESXi host by using the VMware vSphere Client, complete the following steps:

1.    Open the recently downloaded VMware vSphere Client and enter the IP address of VM-Host-Infra-02 as the host you are trying to connect to: <<var_vm_host_infra_02_ip>>.

2.    Enter root for the user name.

3.    Enter the root password.

4.    Click Login to connect.

Set Up VMkernel Ports and Virtual Switch

ESXi Host VM-Host-Infra-01

To set up the VMkernel ports and the virtual switches on the VM-Host-Infra-01 ESXi host, complete the following steps:

1.    From each vSphere Client, select the host in the inventory.

2.    Click the Configuration tab.

3.    Click Networking in the Hardware pane.

4.    Click Properties on the right side of vSwitch0.

5.    Select the vSwitch configuration and click Edit.

6.    From the General tab, change the MTU to 9000.

7.    Click OK to close the properties for vSwitch0.

8.    Select the Management Network configuration and click Edit.

9.    Change the network label to VMkernel-MGMT and select the Management Traffic checkbox.

10.  Click OK to finalize the edits for Management Network.

11.  Select the VM Network configuration and click Edit.

12.  Change the network label to IB-MGMT Network and enter <<var_ib-mgmt_vlan_id>> in the VLAN ID (Optional) field.

13.  Click OK to finalize the edits for VM Network.

14.  Click Add to add a network element.

15.  Select VMkernel and click Next.

16.  Change the network label to VMkernel-NFS and enter <<var_nfs_vlan_id>> in the VLAN ID (Optional) field.

17.  Click Next to continue with the NFS VMkernel creation.

18.  Enter the IP address <<var_nfs_vlan_id_ip_host-01>> and the subnet mask <<var_nfs_vlan_id_mask_host01>> for the NFS VLAN interface for VM-Host-Infra-01.

19.  Click Next to continue with the NFS VMkernel creation.

20.  Click Finish to finalize the creation of the NFS VMkernel interface.

21.  Select the VMkernel-NFS configuration and click Edit.

22.  Change the MTU to 9000.

23.  Click OK to finalize the edits for the VMkernel-NFS network.

24.  Click Add to add a network element.

25.  Select VMkernel and click Next.

26.  Change the network label to VMkernel-vMotion and enter <<var_vmotion_vlan_id>> in the VLAN ID (Optional) field.

27.  Select the Use This Port Group for vMotion checkbox.

28.  Click Next to continue with the vMotion VMkernel creation.

29.  Enter the IP address <<var_vmotion_vlan_id_ip_host-01>> and the subnet mask <<var_vmotion_vlan_id_mask_host-01>> for the vMotion VLAN interface for VM-Host-Infra-01.

30.  Click Next to continue with the vMotion VMkernel creation.

31.  Click Finish to finalize the creation of the vMotion VMkernel interface.

32.  Select the VMkernel-vMotion configuration and click Edit.

33.  Change the MTU to 9000.

34.  Click OK to finalize the edits for the VMkernel-vMotion network.

35.  Click add and select Virtual Machine Network, then click Next.

36.  Change the network label to VM-Traffic and enter <<var_vmtraffic_vlan_id>> in the VLAN ID (Optional) field

37.  Click next, click finish to complete the creation of the VM-traffic network.

38.  Close the dialog box to finalize the ESXi host networking setup.

 

Map Required VMFS Datastores

Map the VMFS Datastores to the First ESXi Host

1.    Log in to the IBM Storwize V7000 management GUI.

2.    Select the volumes icon on the left side screen and click the Volumes menu item.

3.    Right-click the infra_datastore_1 volume and click map to host

4.    Choose host VM-Host-Infra-1, leave All I/O Groups selected then click Map Volumes , then click Close.

5.    Right-click the infra_swap volume and click map to host.

6.    Choose host VM-Host-Infra-1, leave All I/O Groups selected then click Map Volumes, then click Close.

ESXi Hosts VM-Host-Infra-01

To mount the required datastores, complete the following steps on the first ESXi host:

1.    From the vSphere Client, select the host VM-Host-Infra-01 in the inventory.

2.    Click the Configuration tab to enable configurations.

3.    Click Storage in the Hardware pane.

4.    From the Datastore area, click Add Storage to open the Add Storage wizard.

5.    Select Disk/Lun and click Next.

6.    Select the 500GB Datastore lun and click Next.

7.    Accept default VMFS setting and click Next.

8.    Click next for the disk layout.

9.    Enter infra_datastore_1 as the datastore name.

10.  Click Next to retain maximum available space.

11.  Click finish.

12.  Click Add Storage to open the Add Storage wizard.

13.  Select Disk/Lun and click Next.

14.  Select the 100GB  swap lun and click Next.

15.  Accept default VMFS setting and click Next.

16.  Click next for the disk layout.

17.  Enter infra_swap as the datastore name.

18.  Click Next to retain maximum available space.

19.  Click Finish.

ESXi Hosts VM-Host-Infra-01 and VM-Host-Infra-02

To configure Network Time Protocol (NTP) on the ESXi hosts, complete the following steps on each host:

1.    From each vSphere Client, select the host in the inventory.

2.    Click the Configuration tab to enable configurations.

3.    Click Time Configuration in the Software pane.

4.    Click Properties at the upper right side of the window.

5.    At the bottom of the Time Configuration dialog box, click Options.

6.    In the NTP Daemon Options dialog box, complete the following steps:

a.     Click General in the left pane, select Start, and stop with host.

b.    Click NTP Settings in the left pane and click Add.

7.    In the Add NTP Server dialog box, enter <<var_global_ntp_server_ip>> as the IP address of the NTP server and click OK.

8.    In the NTP Daemon Options dialog box, select the Restart NTP Service to Apply Changes checkbox and click OK.

9.    In the Time Configuration dialog box, complete the following steps:

a.     Select the NTP Client Enabled checkbox and click OK.

b.    Verify that the clock is now set to approximately the correct time.

VersaStack VMware vCenter 5.5 Update 2

The procedures in the following subsections provide detailed instructions for installing VMware vCenter.

5.5 Update 1 in a VersaStack environment. After the procedures are completed, a VMware vCenter Server will be configured along with a Microsoft SQL Server database to provide database support to vCenter. These deployment procedures are customized to include the environment variables.

This procedure focuses on the installation and configuration of an external Microsoft SQL Server 2008 R2 database, but other types of external databases are also supported by vCenter. To use an alternative database, refer to the VMware vSphere 5.5 documentation.

To install VMware vCenter 5.5 Update 1, an accessible Windows Active Directory® (AD) Domain is necessary. If an existing AD Domain is not available, an AD virtual machine, or AD pair, can be set up in this VersaStack environment. Refer to the Appendix.

Build Microsoft SQL Server Virtual Machine

ESXi Host VM-Host-Infra-01

To build a SQL Server virtual machine (VM) for the VM-Host-Infra-01 ESXi host, complete the following steps:

1.    Log in to the host by using the VMware vSphere Client.

2.    In the vSphere Client, select the host in the inventory pane.

3.    Right-click the host and select New Virtual Machine.

4.    Select Custom and click Next.

5.    Enter a name for the VM. Click Next.

6.    Select infra_datastore_1. Click Next.

7.    Select Virtual Machine Version: 8. Click Next.

8.    Verify that the Windows option and the Microsoft Windows Server® 2008 R2 (64-bit) version are selected. Click Next.

9.    Select two virtual sockets and one core per virtual socket. Click Next.

10.  Select 8GB of memory. Click Next.

11.  Select one network interface card (NIC).

12.  For NIC 1, select the IB-MGMT Network option and the VMXNET 3 adapter. Click Next.

13.  Keep the LSI Logic SAS option for the SCSI controller selected. Click Next.

14.  Keep the Create a New Virtual Disk option selected. Click Next.

15.  Make the disk size at least 60GB. Click Next.

16.  Click Next.

17.  Select the checkbox for Edit the Virtual Machine Settings Before Completion. Click Continue.

18.  Click the Options tab.

19.  Select Boot Options.

20.  Select the Force BIOS Setup checkbox.

21.  Click Finish.

22.  From the left pane, expand the host field by clicking the plus sign (+).

23.  Right-click the newly created SQL Server VM and click Open Console.

24.  Click the third button (green right arrow) to power on the VM.

25.  Click the ninth button (CD with a wrench) to map the Windows Server 2008 R2 SP1 ISO, and then select Connect to ISO Image on Local Disk.

26.  Navigate to the Windows Server 2008 R2 SP1 ISO, select it, and click Open.

27.  Click in the BIOS Setup Utility window and use the right arrow key to navigate to the Boot menu. Use the down arrow key to select CD-ROM Drive. Press the plus (+) key twice to move CD-ROM Drive to the top of the list. Press F10 and Enter to save the selection and exit the BIOS Setup Utility.

28.  The Windows Installer boots. Select the appropriate language, time and currency format, and keyboard. Click Next.

29.  Click Install Now.

30.  Make sure that the Windows Server 2008 R2 Standard (Full Installation) option is selected. Click Next.

31.  Read and accept the license terms and click Next.

32.  Select Custom (Advanced). Make sure that Disk 0 Unallocated Space is selected. Click Next to allow the Windows installation to complete.

33.  After the Windows installation is complete and the VM has rebooted, click OK to set the Administrator password.

34.  Enter and confirm the Administrator password and click the blue arrow to log in. Click OK to confirm the password change.

35.  After logging in to the VM desktop, from the VM console window, select the VM menu. Under Guest, select Install/Upgrade VMware Tools. Click OK.

36.  If prompted to eject the Windows installation media before running the setup for the VMware tools, click OK, then click OK.

37.  In the dialog box, select Run setup64.exe.

38.  In the VMware Tools installer window, click Next.

39.  Make sure that Typical is selected and click Next.

40.  Click Install.

41.  Click Finish.

42.  Click Yes to restart the VM.

43.  After the reboot is complete, select the VM menu. Under Guest, select Send Ctrl+Alt+Del and then enter the password to log in to the VM.

44.  Set the time zone for the VM, IP address, gateway, and host name.

45.  Log back in to the VM, download, and install all required Windows updates.

46.  Add the VM to the Windows AD domain.

47.  If necessary, activate Windows.

48.  Log back in to the VM, download, and install any additional required Windows updates.

Install Microsoft SQL Server 2008 R2

vCenter SQL Server Virtual Machine

In our setup, we have enabled Remote Desktop connection on the server to simplify the following procedure. To install SQL Server on the vCenter SQL Server VM, complete the following steps:

1.    Connect to an AD Domain Controller in the VersaStack Windows Domain and add an admin user for the VersaStack using the Active Directory Users and Computers tool. This user should be a member of the Domain Administrators security group.

2.    Log in to the vCenter SQL Server VM as the VersaStack admin user and open Server Manager.

3.    Expand Features and click Add Features.

4.    Expand .NET Framework 3.5.1 Features and select only .NET Framework 3.5.1.

 

5.    Click Next.

6.    Click Install.

7.    Click Close.

8.    Open Windows Firewall with Advanced Security by navigating to Start > Administrative Tools > Windows Firewall with Advanced Security.

9.    Select Inbound Rules and click New Rule.

10.  Select Port and click Next.

11.  Select TCP and enter the specific local port 1433. Click Next.

12.  Select Allow the Connection. Click Next, and then click Next again.

13.  Name the rule SQL Server and click Finish.

14.  Close Windows Firewall with Advanced Security.

15.  In the vCenter SQL Server VMware console, click the ninth button (CD with a wrench) to map the Microsoft SQL Server 2008 R2 ISO. Select Connect to ISO Image on Local Disk.

16.  Navigate to the SQL Server 2008 R2 ISO, select it, and click Open.

17.  In the dialog box, click Run setup.exe.

18.  In the SQL Server Installation Center window, click Installation on the left.

19.  Select New Installation or Add Features to an Existing Installation.

20.  Click OK.

21.  Select Enter the Product Key. Enter a product key and click Next.

22.  Read and accept the license terms and choose whether to select the second checkbox. Click Next.

23.  Click Install to install the setup support files.

24.  Address any warnings except for the Windows firewall warning. Click Next.

25.  Select SQL Server Feature Installation and click Next.

26.  Under Instance Features, select only Database Engine Services.

27.  Under Shared Features, select Management Tools - Basic and Management Tools - Complete. Click Next.

 

28.  Click Next.

29.  Keep the Default Instance selected. Click Next.

 

30.  Click Next for Disk Space Requirements.

31.  For the SQL Server Agent service, click in the first cell in the Account Name column and then click  <<Browse…>>.

32.  Select Locations and select the local machine.

33.  Enter the local machine administrator name (for example, systemname\Administrator), click Check Names, and click OK.

34.  Enter the administrator password in the first cell under Password.

35.  Change the startup type for SQL Server Agent to Automatic.

36.  For the SQL Server Database Engine service, select Administrator in the Account Name column and enter the administrator password again. Click Next.

 

37.  Select Mixed Mode (SQL Server Authentication and Windows Authentication).

38.  Enter and confirm the password for the SQL Server system administrator (sa) account.

39.  Click Add Current User and click Next.

 

40.  Choose whether to send error reports to Microsoft. Click Next.

41.  Click Next.

42.  Click Install.

43.  After the installation is complete, click Close to close the SQL Server installer.

44.  Close the SQL Server Installation Center.

45.  Install all available Microsoft Windows updates by navigating to Start > All Programs > Windows Update.

46.  Open the SQL Server Management Studio by selecting Start > All Programs > Microsoft SQL Server 2008 R2 > SQL Server Management Studio.

47.  Under Server Name, enter the local machine name. Under Authentication, select SQL Server Authentication. Enter sa in the Login field and enter the sa password. Click Connect.

48.  Click New Query.

49.  Run the following script, substituting the vpxuser password for <Password> and changing the database and log paths if desired:

use [master]

go

CREATE DATABASE [VCDB] ON PRIMARY

(NAME = N'vcdb', FILENAME = N'C:\VCDB.mdf', SIZE = 20000KB, FILEGROWTH = 10% )

LOG ON

(NAME = N'vcdb_log', FILENAME = N'C:\VCDB.ldf', SIZE = 1000KB, FILEGROWTH = 10%)

COLLATE SQL_Latin1_General_CP1_CI_AS

go

use VCDB

go

sp_addlogin @loginame=[vpxuser], @passwd=N'<Password>', @defdb='VCDB',

@deflanguage='us_english'

go

ALTER LOGIN [vpxuser] WITH CHECK_POLICY = OFF

go

CREATE USER [vpxuser] for LOGIN [vpxuser]

go

use MSDB

go

CREATE USER [vpxuser] for LOGIN [vpxuser]

go

use VCDB

go

sp_addrolemember @rolename = 'db_owner', @membername = 'vpxuser'

go

use MSDB

go

sp_addrolemember @rolename = 'db_owner', @membername = 'vpxuser'

go

50.  Click Execute and verify that the query executes successfully.

51.  Close Microsoft SQL Server Management Studio.

52.  Disconnect the Microsoft SQL Server 2008 R2 ISO from the SQL Server VM.

Build and Set Up VMware vCenter Virtual Machine

Build VMware vCenter VM

To build the VMware vCenter VM, complete the following steps:

1.    Build a VMware vCenter VM with the following configuration in the<<var_ib-mgmt_vlan_id>> VLAN:

—     4GB RAM

—     Two CPUs

—     One virtual network interface

2.    Start the VM, install VMware Tools, and assign an IP address and host name to it in the Active Directory domain.

Set Up VMware vCenter Virtual Machine

To set up the newly built VMware vCenter VM, complete the following steps:

1.    Log in to the vCenter VM as the VersaStack admin user and open Server Manager.

2.    Expand Features and click Add Features.

3.    Expand .NET Framework 3.5.1 Features and select only .NET Framework 3.5.1.

4.    Click Next.

5.    Click Install.

6.    Click Close to close the Add Features wizard.

7.    Close Server Manager.

8.    Download and install the client components of the Microsoft SQL Server 2008 R2 Native Client from the Microsoft Download Center.

9.    Create the vCenter database data source name (DSN). Open Data Sources (ODBC) by selecting Start > Administrative Tools > Data Sources (ODBC).

10.  Click the System DSN tab.

11.  Click Add.

12.  Select SQL Server Native Client 10.0 and click Finish.

13.  Name the data source VCDB. In the Server field, enter the IP address of the vCenter SQL server. Click Next.

 

14.  Select With SQL Server authentication using a login ID and password entered by the user. Enter vpxuser as the login ID and the vpxuser password. Click Next.

 

15.  Select Change the Default Database To and select VCDB from the list. Click Next.

 

16.  Click Finish.

17.  Click Test Data Source. Verify that the test completes successfully.

 

18.  Click OK and then click OK again.

19.  Click OK to close the ODBC Data Source Administrator window.

20.  Install all available Microsoft Windows updates by navigating to Start > All Programs > Windows Update.

Install VMware vCenter Server

vCenter Server Virtual Machine

To install vCenter Server on the vCenter Server VM, complete the following steps:

1.    In the vCenter Server VMware console, click the ninth button (CD with a wrench) to map the VMware vCenter ISO and select Connect to ISO Image on Local Disk.

2.    Navigate to the VMware vCenter 5.5 Update 2 (VIMSetup) ISO, select it, and click Open.

3.    In the dialog box, click Run autorun.exe.

4.    In the VMware vCenter Installer window, make sure that VMware vCenter Simple Install is selected and click Install.

 

5.    Click Yes if there is a User Account Control warning.

6.    Click Next to install vCenter Single Sign On.

 

7.    Accept the terms of the license agreement and click Next.

8.    Click Next on Perquisites screen.

 

9.    Enter and confirm <<var_password>> for administrator. Click Next.

 

10.  Click Next on Site screen.

11.  Accept Default HTTPS port and click Next.

 

12.  Click Next

13.  Review the screen and click Install. This process can take approximately 20 minutes during which time multiple windows will launch.

 

14.  Enter yes if a SSL popup is displayed.

 

15.  Enter the license Key.

 

16.  Change the radio button selection to use and existing instance.

17.  Select VCDB and click Next.

 

18.  Enter the password  <<var_password>> for vpxuser.

 

19.  Click Next and read and click OK in the warning message (you will need to take separate action for backup of the SQL database).

 

20.  Click Next to use the SYSTEM Account.

 

21.  Click Next to accept the default ports.

 

22.  Select the appropriate inventory size. Click Next.

23.  Click Install. A new installer window will start and complete in approximately 10 minutes.

24.  Click Finish, then click OK.

ESXi Dump Collector Setup

1.    In the VMware vCenter Installer window, under vCenter Support Tools, select VMware VSphere ESXi Dump Collector.

2.    On the right, click Install.

3.    Click Yes.

4.    Select the appropriate language and click OK.

5.    In the vSphere ESXi Dump Collector Installation Wizard, click Next.

6.    Click Next.

7.    Accept the terms in the License Agreement and click Next.

8.    Click Next to accept the default Destination Folders.

9.    Click Next to accept a Standalone installation.

10.  Click Next to accept the default ESXi Dump Collector Server Port (6500).

11.  Select the VMware vCenter Server IP address from the drop-down menu. Click Next.

12.  Click Install to complete the installation.

13.  Click Finish.

14.  Click Exit in the VMware vCenter Installer window.

15.  Disconnect the VMware vCenter ISO from the vCenter VM.

16.  Install all available Microsoft Windows updates by navigating to Start > All Programs > Windows Updates.

17.  A restart might be required.

18.  Back on the Management Workstation, open the VMware vSphere CLI command prompt.

19.  Set each ESXi Host to core dump to the ESXi Dump Collector by running the following commands:

esxcli -s <<var_vm_host_infra_01_ip>> -u root -p <<var_password>> system coredump network set --interface-name vmk0 --server-ipv4 <<var_vcenter_server_ip> --server-port 6500

esxcli -s <<var_vm_host_infra_02_ip>> -u root -p <<var_password>> system coredump network set --interface-name vmk0 --server-ipv4 <<var_vcenter_server_ip> --server-port 6500

esxcli -s <<var_vm_host_infra_01_ip>> -u root -p <<var_password>> system coredump network set --enable true

esxcli -s <<var_vm_host_infra_02_ip>> -u root -p <<var_password>> system coredump network set --enable true

esxcli -s <<var_vm_host_infra_01_ip>> -u root -p <<var_password>> system coredump network check

esxcli -s <<var_vm_host_infra_02_ip>> -u root -p <<var_password>> system coredump network check

 

Set Up vCenter Server

vCenter Server Virtual Machine

To set up vCenter Server on the vCenter Server VM, complete the following steps:

1.    Using the vSphere Client, log in to the newly created vCenter Server as the VersaStack admin user or administrator@vsphere.local and password.

2.    Click File, New, and Datacenter to create a data center. 

3.    Right-click to rename the datacenter Enter VersaStack_DC_1 as the data center name.

4.    Right-click the newly created VersaStack_DC_1 data center and select New Cluster.

5.    Name the cluster VersaStack_Management and select the checkboxes for Turn On vSphere HA and Turn on vSphere DRS. Click Next.

 

6.    Accept the defaults for vSphere DRS. Click Next.

7.    Accept the defaults for Power Management. Click Next.

8.    Accept the defaults for vSphere HA. Click Next.

9.    Accept the defaults for Virtual Machine Options. Click Next.

10.  Accept the defaults for VM Monitoring. Click Next.

11.  Accept the defaults for VMware EVC. Click Next.

12.  Select “Store the swapfile in the datastore specified by the host”. Click Next.

13.  Click Finish.

14.  Right-click the newly created VersaStack_Management cluster and select Add Host.

15.  In the Host field, enter either the IP address or the host name of the VM-Host-Infra_01 host.

16.  Enter root as the user name and the root password for this host. Click Next.

17.  Click Yes.

18.  Click Next.

19.  Select Assign a New License Key to the Host. Click Enter Key and enter a vSphere license key.

20.  Click OK and then click Next.

21.  Click Next.

22.  Click Next.

23.  Click Finish. VM-Host-Infra-01 is added to the cluster.

24.  Repeat this procedure to add VM-Host-Infra-02 to the cluster.

Map the Datastores on the IBM Storwize V7000 Second Host After Enabling the Cluster

To map the datastores, complete the following steps:

1.    Open the web client to the Storwize V7000.

2.    Click the volumes button in the left pane and select volume to open the volumes screen.

3.    Right-click the volume infra_datastore_1 and select map to host.

4.    Choose host VM-Host-Infra-02, and leave All I/O Groups default and select Map Volumes.

5.    Click Map All volumes on the warning popup click close.

6.    Right-click the volume infra_swap and leave All I/O Groups default and select map to host.

7.    Choose host VM-Host-Infra-02 and select Map Volumes.

8.    Click Map All volumes on the warning popup click Close.

9.    In vSphere in the left pane right-click the cluster VersaStack_Management, and click rescan for datastores.

Move VM Swap File Location

ESXi Hosts VM-Host-Infra-01 and VM-Host-Infra-02

To move the VM swap file location, complete the following steps on each ESXi host:

1.    From each vSphere Client, select the host in the inventory.

2.    Click the Configuration tab to enable configurations.

3.    Click Virtual Machine Swapfile Location in the Software pane.

4.    Click Edit at the upper right side of the window.

5.    Select Store the swapfile in a swapfile datastore selected below.

6.    Select infra_swap as the datastore in which to house the swap files.

7.    Click OK to finalize moving the swap file location.

Optional: Add Domain Account Permissions

In this section, you will add a user to provide admin and login permissions in the vSphere client

1.    In the vSphere client, log in as the local administrator account and right-click the appropriate level for permissions and click Add Permissions.

 

2.    Select Add.

3.    Select the domain.

4.    Highlight a user and click Add, then click OK.

 

 

5.    Change the assigned role to the correct group, and click OK.

6.    Log off as administrator and back in as that domain user.

 

Set Up the Optional Cisco Nexus 1000V Switch Using Cisco Switch Update Manager

Cisco Nexus 1000V

The Cisco Nexus 1000V is a distributed virtual switch solution that is fully integrated within the VMware virtual infrastructure, including VMware vCenter, for the virtualization administrator. This solution offloads the configuration of the virtual switch and port groups to the network administrator to enforce a consistent data center network policy. The Cisco Nexus 1000V is compatible with any upstream physical access layer switch that is compliant with Ethernet standard, Cisco Nexus switches, and switches from other network vendors. The Cisco Nexus 1000V is compatible with any server hardware that is listed in the VMware Hardware Compatibility List (HCL).

The Cisco Nexus 1000V has the following components:

·         Virtual Supervisor Module (VSM)—The control plane of the switch and a VM that runs Cisco NX-OS.

·         Virtual Ethernet Module (VEM)—A virtual line card that is embedded in each VMware vSphere (ESXi) host. The VEM is partly inside the kernel of the hypervisor and partly in a user-world process, called the VEM Agent.

Cisco Nexus 1000V Architecture

Figure 6 illustrates the Cisco Nexus 1000V architecture.

Figure 6       Cisco Nexus 1000V Architecture

 

Layer 3 control mode is the preferred method of communication between the VSM and the VEMs. In Layer 3 control mode, the VEMs can be in a different subnet than the VSM and from each other. Active and standby VSM control ports should be Layer 2 adjacent. These ports are used to communicate the HA protocol between the active and standby VSMs. Each VEM needs a designated VMkernel NIC interface that is attached to the VEM that communicates with the VSM. This interface, which is called the Layer 3 Control vmknic, must have a system port profile applied to it (see System Port Profiles and System VLANs), so the VEM can enable it before contacting the VSM.

Installation Process

To create network redundancy for the migration, create a temporary VMkernel, and complete the following steps:

ESXi Host VM-Host-Infra-01

1.    From each vSphere Client, select the host in the inventory.

2.    Click the Configuration tab.

3.    Click Networking in the Hardware then Properties.

 

4.    Click Add.

5.    Select VMkernel and click Next.

6.    Change the network label to VMkernel-MGMT-2 and enter <<var_ib-mgmt_vlan_id>> in the VLAN ID (Optional) field.

7.    Select Use this port group for management traffic.

8.    Click Next to continue with the VMkernel creation.

9.    Enter the IP address <<var_vmhost_infra_01_2nd_ip>> and the subnet mask for the VLAN interface for VM-Host-Infra-01.

10.  Click Next to continue with the VMkernel creation.

11.  Click Finish to finalize the creation of the new VMkernel interface.

Deploy the OVF Template for the Cisco Nexus 1000 Virtual Switch Update Manager

 To deploy the OVF template, complete the following steps:

1.    Log in and Download the Cisco Nexus 1000V installation software from www.cisco.com.

 

2.    Unzip the package.

3.    From the vSphere client, click File, Deploy OVF Template and browse to the unzipped ova file.

 

4.    Click Next, then click Next again.

5.    Review the license agreement. Click Next.

6.    Click Next on the Name and Location screen.

7.    Select VersaStack_Management as the Host Cluster and click Next.

8.    Select VM-Host-Infra-1 as the Datastore and click Next.

9.    Choose a disk format and click Next.

10.  For Network Mapping make sure you have Management Mapped to IB-Mgmt and click Next.

 

11.  On the Properties screen, input <<var_vsm_updatemgr_mgmt_ip>> <<var_vsm_mgmt_mask>> <<var_vsm_mgmt_gateway>> <<var_nameserver_ip>>.

12.  Enter the vCenter IP and login information. For domain accounts, use the Administrator@Vsphere.local login format and do not use domainname\user account format.

13.  Accept default ports and click Next.

 

14.  Review the summary screen, click Power on after deployment and click Finish.

 

15.  After the VM boots in a few minute the Plugin is registered. Validate the plugin in the vSphere client by clicking Plug-ins, then Manage plug-ins in the top menu bar and look under Available Plug-ins.

Install the VSM through the Cisco Virtual Switch Update Manager

The VSUM will deploy the VSM primary and secondary to the ESXi hosts through the GUI install. You will have a VSM primary running on 1 ESXi host and a secondary running on the other ESXi host. Both of these are installed at them same time through the host selection. Complete the following steps to deploy the VSM.

1.    Launch the vSphere Web client interface https://<<Vshpere_host_ip>>:9443/vsphere-client and login.

2.    Select the home tab and click Cisco Virtual Switch Update Manager.

 

3.    Click the Nexus 1000V button then click Install.

 

4.    Click the VersaStack datacenter in the right screen.

5.    Keep the default for deploy new VSM and High Availability Pair. Select IB-Mgmt for the control and Management VLAN.

 

6.    For the Host Selection, click the Suggest button and choose the Datastores.

 

7.    Enter a domain ID for the switch configuration section.

 

8.    Enter the following information for the VSM configuration <<var_vsm_hostname>>  <<var_vsm_mgmt_ip>>, <<var_vsm_mgmt_mask>>  <<var_vsm_mgmt_gateway>> <<var_password>>, then click Finish.  You can launch a second VSphere Client to monitor the progress. Click Tasks in the left pane. It will take a few minutes to complete.

 

 

Perform Base Configuration of the Primary VSM

To perform the base configuration of the primary VSM, complete the following steps:

1.    Use an SSH client, log in to the primary Cisco Nexus 1000V VSM as admin.

2.    Run the following configuration commands.

config t

ntp server <<var_global_ntp_server_ip>> use-vrf management

vlan <<var_ib-mgmt_vlan_id>>

name IB-MGMT-VLAN

vlan <<var_nfs_vlan_id>>

name NFS-VLAN

vlan <<var_vmotion_vlan_id>>

name vMotion-VLAN

vlan <<var_vm-traffic_vlan_id>>

name VM-Traffic-VLAN

vlan <<var_native_vlan_id>>

name Native-VLAN

exit

port-profile type ethernet system-uplink

vmware port-group

switchport mode trunk

switchport trunk native vlan <<var_native_vlan_id>>

switchport trunk allowed vlan <<var_ib-mgmt_vlan_id>>, <<var_nfs_vlan_id>>,

<<var_vmotion_vlan_id>>, <<var_vm-traffic_vlan_id>>

channel-group auto mode on mac-pinning

no shutdown

system vlan <<var_ib-mgmt_vlan_id>>, <<var_nfs_vlan_id>>, <<var_vmotion_vlan_id>>, <<var_vm-traffic_vlan_id>>

system mtu 9000

state enabled

exit

 

port-profile type vethernet IB-MGMT-VLAN

vmware port-group

switchport mode access

switchport access vlan <<var_ib-mgmt_vlan_id>>

no shutdown

system vlan <<var_ib-mgmt_vlan_id>>

state enabled

exit

port-profile type vethernet NFS-VLAN

vmware port-group

switchport mode access

switchport access vlan <<var_nfs_vlan_id>>

no shutdown

system vlan <<var_nfs_vlan_id>>

state enabled

exit

port-profile type vethernet vMotion-VLAN

vmware port-group

switchport mode access

switchport access vlan <<var_vmotion_vlan_id>>

no shutdown

system vlan <<var_vmotion_vlan_id>>

state enabled

exit

port-profile type vethernet VM-Traffic-VLAN

vmware port-group

switchport mode access

switchport access vlan <<var_vm-traffic_vlan_id>>

no shutdown

system vlan <<var_vm-traffic_vlan_id>>

state enabled

exit

port-profile type vethernet n1kv-L3

capability l3control

vmware port-group

switchport mode access

switchport access vlan <<var_ib-mgmt_vlan_id>>

no shutdown

system vlan <<var_ib-mgmt_vlan_id>>

state enabled

exit

 

copy run start

Migrate Networking Components for ESXi Hosts to Cisco Nexus 1000V

vSphere Client Connect to vCenter

To migrate the networking components for the ESXi hosts to the Cisco Nexus 1000V, complete the following steps:

1.    In the vSphere web client, click the Home tab and click the Cisco Virtual Switch Update Manager.

 

2.    Click the Nexus 1000v and click Configure.

 

3.    Click Datacenter, then click Distributed Virtual Switch and select manage.

 

4.    Click the Add Host tab then select the plus sign next to Versastack_Management, then click the top check box to both Hosts.

 

5.    Click Suggest.

 

6.    Select the Physical NIC Migration, and select the Unused Nic vmnic1 for migration. Select system uplink in the middle pane.

 

7.    For the VM Kernel NIC Setup, deselect vmk3, which is the temporary management kernel we created for this migration.

 

8.    For VM migration click the button next to the virtual machine to expand the target profile and chose the correct profile that should be IB-MGMT-VLAN. Repeat this for each Virtual Machine.

 

9.    Click Finish.

10.  When the migration completes, click Settings then click Topology and expand the virtual machines to view the network connections.

 

Remove the Networking Standard Switch Components for ESXi Hosts

In this section, the unused standard switch components will be removed and the second VIC will be assigned.

ESXi Host VM-Host-Infra-01

1.    From each vSphere Client, select the host in the inventory.

2.    Click the Configuration tab.

3.    Click Networking.

4.    Select the VSphere Standard switch, and then click Properties.

 

5.    Click the temporary network VMkernel-MGMT-2 created for the migration and click Remove.

6.    Click Yes, then click Yes again.

 

7.    Click Close.

8.    Validate you still are focused on the VSphere standard switch and click Remove to remove this switch. 

9.    Click Yes to the warning popup.

 

10.  After vSwitch0 has disappeared from the screen, click vSphere Distributed Switch at the top next to View.

11.  Click Manage Physical Adapters.

12.  Scroll down to the system-uplink box and click Add NIC.

13.  Choose vmnic0 and click OK, then click OK again.

 

14.  Validate there are no warnings for the ESX nodes. From each vSphere Client, select the Hosts and Clusters in the inventory section, click the Summary tab.

15.  If there are warnings, right-click each node and click Reconfigure for vSphere HA.

 

Remove the Redundancy for the NIC in Cisco UCS Manager

While creating the ESXi vNIC template settings, the default was to enable hardware failover on the vNIC. When you have deployed the N1kV that setting is no longer required and should be disabled. To remove the redundancy for the NIC, complete the following steps:

1.    Launch UCS Manager and click the LAN tab.

2.    Click Policies, root, vNIC templates.

3.    Click vNic_Template_A, and on the General Tab uncheck enable failover.

4.    Click Save Changes, then Yes, then ok.

5.    Repeat action for vNic_Template_B.

For more information about the 1000v switch, including how to update the software after installation, please visit the web site: http://www.cisco.com/c/en/us/products/switches/nexus-1000v-switch-vmware-vsphere/index.html

IBM Solutions

IBM is well known for management software. Added value to this solution can be obtained by installing IBM's Storage Management Console for VMware vCenter. Please visit the IBM website to obtain the latest version at http://www.ibm.com/us/en/.

For details about IBM backup and disaster recovery solutions, please refer to: http://www-03.ibm.com/systems/storage/solutions/backup-and-disaster-recovery/

 

 

 

 

 

 

 

 

 

 

Build Windows Active Directory Server Virtual Machines

ESXi Host VM-Host-Infra-01

To build an Active Directory Server virtual machine (VM) for the VM-Host-Infra-01 ESXi host, complete the following steps:

1.    Log in to the host by using the VMware vSphere Client.

2.    In the vSphere Client, select the host in the inventory pane.

3.    Right-click the host and select New Virtual Machine.

4.    Select Custom and click Next.

5.    Enter a name for the VM. Click Next.

6.    Select infra_datastore_1. Click Next.

7.    Select Virtual Machine Version: 10. Click Next.

8.    Verify that the Windows option and the Microsoft Windows Server 2008 R2 (64-bit) version are selected. Click Next.

9.    Select two virtual sockets and one core per virtual socket. Click Next.

10.  Select 4GB of memory. Click Next.

11.  Select one network interface card (NIC).

12.  For NIC 1, select the IB-MGMT Network option and the VMXNET 3 adapter. Click Next.

13.  Keep the LSI Logic SAS option for the SCSI controller selected. Click Next.

14.  Keep the Create a New Virtual Disk option selected. Click Next.

15.  Make the disk size at least 60GB. Click Next.

16.  Click Next.

17.  Select the checkbox for Edit the Virtual Machine Settings Before Completion. Click Continue.

18.  Click the Options tab.

19.  Select Boot Options.

20.  Select the Force BIOS Setup checkbox.

21.  Click Finish.

22.  From the left pane, expand the host field by clicking the plus sign (+).

23.  Right-click the newly created AD Server VM and click Open Console.

24.  Click the third button (green right arrow) to power on the VM.

25.  Click the ninth button (CD with a wrench) to map the Windows Server 2008 R2 SP1 ISO, and then select Connect to ISO Image on Local Disk.

26.  Navigate to the Windows Server 2008 R2 SP1 ISO, select it, and click Open.

27.  Click in the BIOS Setup Utility window and use the right arrow key to navigate to the Boot menu. Use the down arrow key to select CD-ROM Drive. Press the plus (+) key twice to move CD-ROM Drive to the top of the list. Press F10 and Enter to save the selection and exit the BIOS Setup Utility.

28.  The Windows Installer boots. Select the appropriate language, time and currency format, and keyboard. Click Next.

29.  Click Install now.

30.  Make sure that the Windows Server 2008 R2 Standard (Full Installation) option is selected. Click Next.

31.  Read and accept the license terms and click Next.

32.  Select Custom (Advanced). Make sure that Disk 0 Unallocated Space is selected. Click Next to allow the Windows installation to complete.

33.  After the Windows installation is complete and the VM has rebooted, click OK to set the Administrator password.

34.  Enter and confirm the Administrator password and click the blue arrow to log in. Click OK to confirm the password change.

35.  After logging in to the VM desktop, from the VM console window, select the VM menu. Under Guest, select Install/Upgrade VMware Tools. Click OK.

36.  If prompted to eject the Windows installation media before running the setup for the VMware tools, click OK, then click OK.

37.  In the dialog box, select Run setup64.exe.

38.  In the VMware Tools installer window, click Next.

39.  Make sure that Typical is selected and click Next.

40.  Click Install. 41. Click Finish.

41.  Click Yes to restart the VM.

42.  After the reboot is complete, select the VM menu. Under Guest, select Send Ctrl+Alt+Del. Then enter the password to log in to the VM.

43.  Set the time zone for the VM, IP address, gateway, and host name.

44.  If necessary, activate Windows.

45.  Download and install all required Windows updates.

46.  Open Server Manager.

47.  On the left, click Roles, the select Add Roles on the right.

48.  Click Next.

49.  In the list, select the checkbox next to Active Directory Domain Services. 51. In the popup, click Add Required Features to add .NET Framework 3.5.1.

 

50.  Click Next.

51.  Click Next.

52.  Click Install.

 

 

53.  In the middle of the window, click Close this wizard and launch the Active Directory Domain Services Installation Wizard (dcpromo.exe).

54.  In the Active Directory Domain Services Installation Wizard, click Next.

55.  Click Next.

56.  Select "Create a new domain in a new forest" and click Next.

 

57.  Type the FQDN of the Windows domain for this VersaStack and click Next.

 

58.  Select the appropriate forest functional level and click Next.

59.  Keep DNS server selected and click Next.

 

60.  If one or more DNS servers exist that this domain can resolve from, select Yes to create a DNS delegation. If this AD server is being created on an isolated network, select No, to not create a DNS delegation. The remaining steps in this procedure assume a DNS delegation is not created. Click Next.

61.  Click Next to accept the default locations for database and log files.

62.  Enter and confirm <<var_password>> for the Directory Services Restore Mode Administrator Password. Click Next.

63.  Review the Summary information and click Next. Active Directory Domain Services will install.

64.  Click Finish.

65.  Click Restart Now to restart the AD Server.

66.  After the machine has rebooted, log in as the domain Administrator.

67.  Open the DNS Manager by clicking Start > Administrative Tools > DNS.

68.  Optional: Add Reverse Lookup Zones for your IP address ranges.

69.  Expand the Server and Forward Lookup Zones. Select the zone for the domain. Right-click and select New Host (A or AAAA). Populate the DNS Server with Host Records for all components in the VersaStack.

70.  Optional: Build a second AD server VM. Add this server to the newly created Windows Domain and activate Windows. Install Active Directory Domain Services on this machine. Launch dcpromo.exe at the end of this installation. Choose to add a domain controller to a domain in an existing forest. Add this domain controller to the domain created earlier. Complete the installation of this second domain controller. After vCenter Server is installed, affinity rules can be created to keep the two AD servers running on different hosts.

Cisco Nexus 9000 Example Configurations

Cisco Nexus 9000 A

9396A# sh running-config

 

!Command: show running-config

!Time: Mon Jun  8 18:59:29 2015

 

version 6.1(2)I3(1)

switchname 9396A

vdc 9396A id 1

  allocate interface Ethernet1/1-48

  allocate interface Ethernet2/1-12

  limit-resource vlan minimum 16 maximum 4094

  limit-resource vrf minimum 2 maximum 4096

  limit-resource port-channel minimum 0 maximum 512

  limit-resource u4route-mem minimum 248 maximum 248

  limit-resource u6route-mem minimum 96 maximum 96

  limit-resource m4route-mem minimum 58 maximum 58

  limit-resource m6route-mem minimum 8 maximum 8

 

cfs eth distribute

feature udld

feature interface-vlan

feature lacp

feature vpc

 

username admin password 5 $1$6Cm25cUf$RjGW41DWnpifL29SeZrY//  role network-admin

no password strength-check

ssh key rsa 2048

ip domain-lookup

copp profile strict

snmp-server user admin network-admin auth md5 0x5d6fe1bd95f50f45df28b5e5c73a352b

 priv 0x5d6fe1bd95f50f45df28b5e5c73a352b localizedkey

rmon event 1 log trap public description FATAL(1) owner PMON@FATAL

rmon event 2 log trap public description CRITICAL(2) owner PMON@CRITICAL

rmon event 3 log trap public description ERROR(3) owner PMON@ERROR

rmon event 4 log trap public description WARNING(4) owner PMON@WARNING

rmon event 5 log trap public description INFORMATION(5) owner PMON@INFO

ntp server 171.68.38.66

 

ip route 0.0.0.0/0 10.29.151.1

vlan 1-2,3172-3175

vlan 2

  name Native-VLAN

vlan 3172

  name NFS-VLAN

vlan 3173

  name vMotion-VLAN

vlan 3174

  name VM-Traffic-VLAN

vlan 3175

  name IB-MGMT-VLAN

 

spanning-tree port type edge bpduguard default

spanning-tree port type edge bpdufilter default

spanning-tree port type network default

vrf context management

  ip route 0.0.0.0/0 10.29.151.1

vpc domain 10

  peer-switch

  role priority 10

  peer-keepalive destination 10.29.151.15 source 10.29.151.14

  delay restore 150

  peer-gateway

  auto-recovery

  ip arp synchronize

 

 

interface Vlan1

 

interface Vlan3175

  no shutdown

  no ip redirects

  ip address 10.29.151.253/24

  no ipv6 redirects

 

interface port-channel10

  description vPC peer-link

  switchport mode trunk

  switchport trunk native vlan 2

  switchport trunk allowed vlan 3172-3175

  spanning-tree port type network

  vpc peer-link

 

interface port-channel13

  description FI-A

  switchport mode trunk

  switchport trunk native vlan 2

  switchport trunk allowed vlan 3172-3175

  spanning-tree port type edge trunk

  mtu 9216

  vpc 13

 

interface port-channel14

  description FI-B

  switchport mode trunk

  switchport trunk native vlan 2

  switchport trunk allowed vlan 3172-3175

  spanning-tree port type edge trunk

  mtu 9216

  vpc 14

 

interface Ethernet1/1

 

interface Ethernet1/2

 

interface Ethernet1/3

 

interface Ethernet1/4

 

interface Ethernet1/5

 

interface Ethernet1/6

 

interface Ethernet1/7

 

interface Ethernet1/8

 

interface Ethernet1/9

 

interface Ethernet1/10

 

interface Ethernet1/11

 

interface Ethernet1/12

 

interface Ethernet1/13

 

interface Ethernet1/14

 

interface Ethernet1/15

 

interface Ethernet1/16

 

interface Ethernet1/17

 

interface Ethernet1/18

 

interface Ethernet1/19

 

interface Ethernet1/20

 

interface Ethernet1/21

 

interface Ethernet1/22

 

interface Ethernet1/23

 

interface Ethernet1/24

 

interface Ethernet1/25

  description FI-a

  switchport mode trunk

  switchport trunk native vlan 2

  switchport trunk allowed vlan 3172-3175

  mtu 9216

  channel-group 13 mode active

 

interface Ethernet1/26

  description Fi-B

  switchport mode trunk

  switchport trunk native vlan 2

  switchport trunk allowed vlan 3172-3175

  mtu 9216

  channel-group 14 mode active

 

interface Ethernet1/27

 

interface Ethernet1/28

 

interface Ethernet1/29

 

interface Ethernet1/30

 

interface Ethernet1/31

 

interface Ethernet1/32

 

interface Ethernet1/33

 

interface Ethernet1/34

 

interface Ethernet1/35

 

interface Ethernet1/36

  description IB-MGMT-SWITCH_uplink

  switchport access vlan 3175

  spanning-tree port type network

  speed 1000

 

interface Ethernet1/37

 

interface Ethernet1/38

 

interface Ethernet1/39

 

interface Ethernet1/40

 

interface Ethernet1/41

 

interface Ethernet1/42

 

interface Ethernet1/43

 

interface Ethernet1/44

 

interface Ethernet1/45

 

interface Ethernet1/46

 

interface Ethernet1/47

  description VPC Peer 1/47

  switchport mode trunk

  switchport trunk native vlan 2

  switchport trunk allowed vlan 3172-3175

  channel-group 10 mode active

 

interface Ethernet1/48

  description VPC Peer 1/48

  switchport mode trunk

  switchport trunk native vlan 2

  switchport trunk allowed vlan 3172-3175

  channel-group 10 mode active

 

interface Ethernet2/1

 

interface Ethernet2/2

 

interface Ethernet2/3

 

interface Ethernet2/4

 

interface Ethernet2/5

 

interface Ethernet2/6

 

interface Ethernet2/7

 

interface Ethernet2/8

 

interface Ethernet2/9

 

interface Ethernet2/10

 

interface Ethernet2/11

 

interface Ethernet2/12

 

interface mgmt0

  vrf member management

  ip address 10.29.151.14/24

line console

line vty

boot nxos bootflash:/n9000-dk9.6.1.2.I3.1.bin

 

 

9396A#

Cisco Nexus 9000 B

9696B# sh running-config

 

!Command: show running-config

!Time: Mon Jun  8 19:00:53 2015

 

version 6.1(2)I3(1)

switchname 9696B

vdc 9696B id 1

  allocate interface Ethernet1/1-48

  allocate interface Ethernet2/1-12

  limit-resource vlan minimum 16 maximum 4094

  limit-resource vrf minimum 2 maximum 4096

  limit-resource port-channel minimum 0 maximum 512

  limit-resource u4route-mem minimum 248 maximum 248

  limit-resource u6route-mem minimum 96 maximum 96

  limit-resource m4route-mem minimum 58 maximum 58

  limit-resource m6route-mem minimum 8 maximum 8

 

cfs eth distribute

feature udld

feature interface-vlan

feature lacp

feature vpc

 

username admin password 5 $1$5lqE6rDA$iiMDmjQ5MuWf6dT5FNJxy.  role network-admin

no password strength-check

ssh key rsa 2048

ip domain-lookup

copp profile strict

snmp-server user admin network-admin auth md5 0x68b3526bc88278c113d036f24e3afdb0

 priv 0x68b3526bc88278c113d036f24e3afdb0 localizedkey

rmon event 1 log trap public description FATAL(1) owner PMON@FATAL

rmon event 2 log trap public description CRITICAL(2) owner PMON@CRITICAL

rmon event 3 log trap public description ERROR(3) owner PMON@ERROR

rmon event 4 log trap public description WARNING(4) owner PMON@WARNING

rmon event 5 log trap public description INFORMATION(5) owner PMON@INFO

ntp server 171.68.38.66

 

ip route 0.0.0.0/0 10.29.151.1

vlan 1-2,3172-3175

vlan 2

  name Native-VLAN

vlan 3172

  name NFS-VLAN

vlan 3173

  name vMotion-VLAN

vlan 3174

  name VM-Traffic-VLAN

vlan 3175

  name IB-MGMT-VLAN

 

spanning-tree port type edge bpduguard default

spanning-tree port type edge bpdufilter default

spanning-tree port type network default

vrf context management

  ip route 0.0.0.0/0 10.29.151.1

vpc domain 10

  peer-switch

  role priority 20

  peer-keepalive destination 10.29.151.14 source 10.29.151.15

  delay restore 150

  peer-gateway

  auto-recovery

  ip arp synchronize

 

 

interface Vlan1

 

interface Vlan3175

  no shutdown

  no ip redirects

  ip address 10.29.151.254/24

  no ipv6 redirects

 

interface port-channel10

  description vPC peer-link

  switchport mode trunk

  switchport trunk native vlan 2

  switchport trunk allowed vlan 3172-3175

  spanning-tree port type network

  vpc peer-link

 

interface port-channel13

  description FI-A

  switchport mode trunk

  switchport trunk native vlan 2

  switchport trunk allowed vlan 3172-3175

  spanning-tree port type edge trunk

  mtu 9216

  vpc 13

 

interface port-channel14

  description FI-B

  switchport mode trunk

  switchport trunk native vlan 2

  switchport trunk allowed vlan 3172-3175

  spanning-tree port type edge trunk

  mtu 9216

  vpc 14

 

interface Ethernet1/1

 

interface Ethernet1/2

 

interface Ethernet1/3

 

interface Ethernet1/4

 

interface Ethernet1/5

 

interface Ethernet1/6

 

interface Ethernet1/7

 

interface Ethernet1/8

 

interface Ethernet1/9

 

interface Ethernet1/10

 

interface Ethernet1/11

 

interface Ethernet1/12

 

interface Ethernet1/13

 

interface Ethernet1/14

 

interface Ethernet1/15

 

interface Ethernet1/16

 

interface Ethernet1/17

 

interface Ethernet1/18

 

interface Ethernet1/19

 

interface Ethernet1/20

 

interface Ethernet1/21

 

interface Ethernet1/22

 

interface Ethernet1/23

 

interface Ethernet1/24

 

interface Ethernet1/25

  description FI-B

  switchport mode trunk

  switchport trunk native vlan 2

  switchport trunk allowed vlan 3172-3175

  mtu 9216

  channel-group 14 mode active

 

interface Ethernet1/26

  description Fi-A

  switchport mode trunk

  switchport trunk native vlan 2

  switchport trunk allowed vlan 3172-3175

  mtu 9216

  channel-group 13 mode active

 

interface Ethernet1/27

 

interface Ethernet1/28

 

interface Ethernet1/29

 

interface Ethernet1/30

 

interface Ethernet1/31

 

interface Ethernet1/32

 

interface Ethernet1/33

 

interface Ethernet1/34

 

interface Ethernet1/35

 

interface Ethernet1/36

  description IB-MGMT-SWITCH_uplink

  switchport access vlan 3175

  spanning-tree port type network

  speed 1000

 

interface Ethernet1/37

 

interface Ethernet1/38

 

interface Ethernet1/39

 

interface Ethernet1/40

 

interface Ethernet1/41

 

interface Ethernet1/42

 

interface Ethernet1/43

 

interface Ethernet1/44

 

interface Ethernet1/45

 

interface Ethernet1/46

 

interface Ethernet1/47

  description VPC Peer 1/47

  switchport mode trunk

  switchport trunk native vlan 2

  switchport trunk allowed vlan 3172-3175

  channel-group 10 mode active

 

interface Ethernet1/48

  description VPC Peer 1/48

  switchport mode trunk

  switchport trunk native vlan 2

  switchport trunk allowed vlan 3172-3175

  channel-group 10 mode active

 

interface Ethernet2/1

 

interface Ethernet2/2

 

interface Ethernet2/3

 

interface Ethernet2/4

 

interface Ethernet2/5

 

interface Ethernet2/6

 

interface Ethernet2/7

 

interface Ethernet2/8

 

interface Ethernet2/9

 

interface Ethernet2/10

 

interface Ethernet2/11

 

interface Ethernet2/12

 

interface mgmt0

  vrf member management

  ip address 10.29.151.15/24

line console

line vty

boot nxos bootflash:/n9000-dk9.6.1.2.I3.1.bin

 

 

9696B#

Cisco MDS Example Configurations

MDS 9148S A

mds-a# sh running-config

 

!Command: show running-config

!Time: Mon Jun  8 19:02:49 2015

 

version 6.2(9)

power redundancy-mode redundant

feature npiv

feature fport-channel-trunk

role name default-role

  description This is a system defined role and applies to all users.

  rule 5 permit show feature environment

  rule 4 permit show feature hardware

  rule 3 permit show feature module

  rule 2 permit show feature snmp

  rule 1 permit show feature system

username admin password 5 $1$d7Mw7dUa$gTewLv6kKZacjd2FHd.JW/  role network-admin

no password strength-check

ssh key rsa 2048

ip domain-lookup

ip host mds-a  10.29.151.18

aaa group server radius radius

snmp-server user admin network-admin auth md5 0xf86163beb9502bf154007d0d6f8f367e

 priv 0xf86163beb9502bf154007d0d6f8f367e localizedkey

rmon event 1 log trap public description FATAL(1) owner PMON@FATAL

rmon event 2 log trap public description CRITICAL(2) owner PMON@CRITICAL

rmon event 3 log trap public description ERROR(3) owner PMON@ERROR

rmon event 4 log trap public description WARNING(4) owner PMON@WARNING

rmon event 5 log trap public description INFORMATION(5) owner PMON@INFO

ntp server 72.163.32.43

vsan database

  vsan 101

device-alias database

  device-alias name VersaStack-NodeA pwwn 50:05:07:68:0b:23:20:fc

  device-alias name VersaStack-NodeB pwwn 50:05:07:68:0b:23:20:fd

  device-alias name VersaStack-NodeC pwwn 50:05:07:68:0b:21:20:86

  device-alias name VersaStack-NodeD pwwn 50:05:07:68:0b:31:20:c6

  device-alias name VM-Host-Infra-01-A pwwn 20:00:00:25:b5:00:0a:0f

  device-alias name VM-Host-Infra-02-A pwwn 20:00:00:25:b5:00:0a:1f

 

device-alias commit

 

fcdomain fcid database

  vsan 1 wwn 20:20:00:2a:6a:cd:fd:00 fcid 0x6f0000 dynamic

  vsan 1 wwn 20:1f:00:2a:6a:cd:fd:00 fcid 0x6f0100 dynamic

  vsan 1 wwn 50:05:07:68:0b:23:20:fc fcid 0x6f0200 dynamic

!            [VersaStack-NodeA]

  vsan 1 wwn 50:05:07:68:0b:22:20:fd fcid 0x6f0300 dynamic

  vsan 1 wwn 50:05:07:68:0b:24:20:fd fcid 0x6f0400 dynamic

  vsan 1 wwn 50:05:07:68:0b:21:20:fc fcid 0x6f0500 dynamic

  vsan 1 wwn 50:05:07:68:0b:23:20:fd fcid 0x6f0a00 dynamic

!            [VersaStack-NodeB]

  vsan 101 wwn 50:05:07:68:0b:23:20:fd fcid 0x580000 dynamic

!              [VersaStack-NodeB]

  vsan 101 wwn 50:05:07:68:0b:23:20:fc fcid 0x580100 dynamic

!              [VersaStack-NodeA]

  vsan 101 wwn 50:05:07:68:0b:31:20:c6 fcid 0x580200 dynamic

!              [VersaStack-NodeD]

  vsan 101 wwn 50:05:07:68:0b:21:20:86 fcid 0x580300 dynamic

!              [VersaStack-NodeC]

  vsan 101 wwn 24:01:00:2a:6a:cd:fd:00 fcid 0x580400 dynamic

  vsan 101 wwn 20:00:00:25:b5:00:0a:0f fcid 0x580401 dynamic

!              [VM-Host-Infra-01-A]

  vsan 101 wwn 20:00:00:25:b5:00:0a:1f fcid 0x580402 dynamic

!              [VM-Host-Infra-02-A]

  vsan 1 wwn 50:05:07:68:0b:23:20:c6 fcid 0x6f0600 dynamic

  vsan 1 wwn 50:05:07:68:0b:33:20:86 fcid 0x6f0700 dynamic

  vsan 1 wwn 50:05:07:68:0b:21:20:86 fcid 0x6f0800 dynamic

!            [VersaStack-NodeC]

  vsan 1 wwn 50:05:07:68:0b:31:20:c6 fcid 0x6f0900 dynamic

!            [VersaStack-NodeD]

 

 

interface port-channel1

  channel mode active

  switchport rate-mode dedicated

vsan database

  vsan 101 interface port-channel1

  vsan 101 interface fc1/3

  vsan 101 interface fc1/4

  vsan 101 interface fc1/5

  vsan 101 interface fc1/6

clock timezone pst 0 0

switchname mds-a

line console

line vty

boot kickstart bootflash:/m9100-s5ek9-kickstart-mz.6.2.9.bin

boot system bootflash:/m9100-s5ek9-mz.6.2.9.bin

interface fc1/1

interface fc1/2

interface fc1/3

interface fc1/4

interface fc1/5

interface fc1/6

interface fc1/7

interface fc1/8

interface fc1/9

interface fc1/10

interface fc1/11

interface fc1/12

interface fc1/13

interface fc1/14

interface fc1/15

interface fc1/16

interface fc1/17

interface fc1/18

interface fc1/19

interface fc1/20

interface fc1/21

interface fc1/22

interface fc1/23

interface fc1/24

interface fc1/25

interface fc1/26

interface fc1/27

interface fc1/28

interface fc1/29

interface fc1/30

interface fc1/31

interface fc1/32

interface fc1/33

interface fc1/34

interface fc1/35

interface fc1/36

interface fc1/37

interface fc1/38

interface fc1/39

interface fc1/40

interface fc1/41

interface fc1/42

interface fc1/43

interface fc1/44

interface fc1/45

interface fc1/46

interface fc1/47

interface fc1/48

interface fc1/1

interface fc1/2

!Active Zone Database Section for vsan 101

zone name versastack vsan 101

    member pwwn 50:05:07:68:0b:23:20:fc

!               [VersaStack-NodeA]

    member pwwn 50:05:07:68:0b:23:20:fd

!               [VersaStack-NodeB]

    member pwwn 50:05:07:68:0b:21:20:86

!               [VersaStack-NodeC]

    member pwwn 50:05:07:68:0b:31:20:c6

!               [VersaStack-NodeD]

 

zone name VM-Host-Infra-01-A vsan 101

    member pwwn 20:00:00:25:b5:00:0a:0f

!               [VM-Host-Infra-01-A]

    member pwwn 50:05:07:68:0b:23:20:fc

!               [VersaStack-NodeA]

    member pwwn 50:05:07:68:0b:23:20:fd

!               [VersaStack-NodeB]

    member pwwn 50:05:07:68:0b:21:20:86

!               [VersaStack-NodeC]

    member pwwn 50:05:07:68:0b:31:20:c6

!               [VersaStack-NodeD]

 

zone name VM-Host-Infra-02-A vsan 101

    member pwwn 20:00:00:25:b5:00:0a:1f

!               [VM-Host-Infra-02-A]

    member pwwn 50:05:07:68:0b:23:20:fc

!               [VersaStack-NodeA]

    member pwwn 50:05:07:68:0b:23:20:fd

!               [VersaStack-NodeB]

    member pwwn 50:05:07:68:0b:21:20:86

!               [VersaStack-NodeC]

    member pwwn 50:05:07:68:0b:31:20:c6

!               [VersaStack-NodeD]

 

zoneset name versastackzoneset vsan 101

    member versastack

    member VM-Host-Infra-01-A

    member VM-Host-Infra-02-A

 

zoneset activate name versastackzoneset vsan 101

do clear zone database vsan 101

!Full Zone Database Section for vsan 101

zone name versastack vsan 101

    member pwwn 50:05:07:68:0b:23:20:fc

!               [VersaStack-NodeA]

    member pwwn 50:05:07:68:0b:23:20:fd

!               [VersaStack-NodeB]

    member pwwn 50:05:07:68:0b:21:20:86

!               [VersaStack-NodeC]

    member pwwn 50:05:07:68:0b:31:20:c6

!               [VersaStack-NodeD]

 

zone name VM-Host-Infra-01-A vsan 101

    member pwwn 20:00:00:25:b5:00:0a:0f

!               [VM-Host-Infra-01-A]

    member pwwn 50:05:07:68:0b:23:20:fc

!               [VersaStack-NodeA]

    member pwwn 50:05:07:68:0b:23:20:fd

!               [VersaStack-NodeB]

    member pwwn 50:05:07:68:0b:21:20:86

!               [VersaStack-NodeC]

    member pwwn 50:05:07:68:0b:31:20:c6

!               [VersaStack-NodeD]

 

zone name VM-Host-Infra-02-A vsan 101

    member pwwn 20:00:00:25:b5:00:0a:1f

!               [VM-Host-Infra-02-A]

    member pwwn 50:05:07:68:0b:23:20:fc

!               [VersaStack-NodeA]

    member pwwn 50:05:07:68:0b:23:20:fd

!               [VersaStack-NodeB]

    member pwwn 50:05:07:68:0b:21:20:86

!               [VersaStack-NodeC]

    member pwwn 50:05:07:68:0b:31:20:c6

!               [VersaStack-NodeD]

 

zoneset name versastackzoneset vsan 101

    member versastack

    member VM-Host-Infra-01-A

    member VM-Host-Infra-02-A

 

 

interface fc1/1

  port-license acquire

  channel-group 1 force

  no shutdown

 

interface fc1/2

  port-license acquire

  channel-group 1 force

  no shutdown

 

interface fc1/3

  port-license acquire

  no shutdown

 

interface fc1/4

  port-license acquire

  no shutdown

 

interface fc1/5

  port-license acquire

  no shutdown

 

interface fc1/6

  port-license acquire

  no shutdown

 

interface fc1/7

  port-license acquire

  no shutdown

 

interface fc1/8

  port-license acquire

  no shutdown

 

interface fc1/9

  port-license acquire

 

interface fc1/10

  port-license acquire

 

interface fc1/11

  port-license acquire

 

interface fc1/12

  port-license acquire

 

interface fc1/13

 

interface fc1/14

 

interface fc1/15

 

interface fc1/16

 

interface fc1/17

 

interface fc1/18

 

interface fc1/19

 

interface fc1/20

 

interface fc1/21

 

interface fc1/22

 

interface fc1/23

 

interface fc1/24

 

interface fc1/25

 

interface fc1/26

 

interface fc1/27

 

interface fc1/28

 

interface fc1/29

 

interface fc1/30

 

interface fc1/31

 

interface fc1/32

 

interface fc1/33

 

interface fc1/34

 

interface fc1/35

 

interface fc1/36

 

interface fc1/37

 

interface fc1/38

 

interface fc1/39

 

interface fc1/40

 

interface fc1/41

 

interface fc1/42

 

interface fc1/43

 

interface fc1/44

 

interface fc1/45

 

interface fc1/46

 

interface fc1/47

 

interface fc1/48

 

interface mgmt0

  ip address 10.29.151.18 255.255.255.0

ip default-gateway 10.29.151.1

 

mds-a#

MDS 9148S B

mds-b# sh running-config

 

!Command: show running-config

!Time: Mon Jun  8 19:04:25 2015

 

version 6.2(9)

power redundancy-mode redundant

feature npiv

feature fport-channel-trunk

role name default-role

  description This is a system defined role and applies to all users.

  rule 5 permit show feature environment

  rule 4 permit show feature hardware

  rule 3 permit show feature module

  rule 2 permit show feature snmp

  rule 1 permit show feature system

username admin password 5 $1$Oy0N2ldp$2/ScO0.PkZgJRMJpmWWhr.  role network-admin

no password strength-check

ssh key rsa 2048

ip domain-lookup

ip host mds-b  10.29.151.19

aaa group server radius radius

snmp-server user admin network-admin auth md5 0xc5f10206775e4335bf0afa53d7f33a10

 priv 0xc5f10206775e4335bf0afa53d7f33a10 localizedkey

rmon event 1 log trap public description FATAL(1) owner PMON@FATAL

rmon event 2 log trap public description CRITICAL(2) owner PMON@CRITICAL

rmon event 3 log trap public description ERROR(3) owner PMON@ERROR

rmon event 4 log trap public description WARNING(4) owner PMON@WARNING

rmon event 5 log trap public description INFORMATION(5) owner PMON@INFO

ntp server 171.68.38.66

vsan database

  vsan 102

device-alias database

  device-alias name VersaStack-NodeA pwwn 50:05:07:68:0b:24:20:fc

  device-alias name VersaStack-NodeB pwwn 50:05:07:68:0b:24:20:fd

  device-alias name VersaStack-NodeC pwwn 50:05:07:68:0b:22:20:86

  device-alias name VersaStack-NodeD pwwn 50:05:07:68:0b:32:20:c6

  device-alias name VM-Host-Infra-01-B pwwn 20:00:00:25:b5:00:0b:0f

  device-alias name VM-Host-Infra-02-B pwwn 20:00:00:25:b5:00:0b:1f

 

device-alias commit

 

fcdomain fcid database

  vsan 1 wwn 20:20:00:2a:6a:cd:ff:80 fcid 0xbb0000 dynamic

  vsan 1 wwn 20:1f:00:2a:6a:cd:ff:80 fcid 0xbb0100 dynamic

  vsan 1 wwn 50:05:07:68:0b:22:20:fc fcid 0xbb0200 dynamic

  vsan 1 wwn 50:05:07:68:0b:24:20:fc fcid 0xbb0300 dynamic

!            [VersaStack-NodeA]

  vsan 1 wwn 50:05:07:68:0b:23:20:fd fcid 0xbb0400 dynamic

  vsan 1 wwn 50:05:07:68:0b:21:20:fd fcid 0xbb0500 dynamic

  vsan 102 wwn 50:05:07:68:0b:24:20:fc fcid 0xae0000 dynamic

!              [VersaStack-NodeA]

  vsan 102 wwn 50:05:07:68:0b:24:20:fd fcid 0xae0100 dynamic

!              [VersaStack-NodeB]

  vsan 102 wwn 50:05:07:68:0b:22:20:86 fcid 0xae0200 dynamic

!              [VersaStack-NodeC]

  vsan 102 wwn 50:05:07:68:0b:32:20:c6 fcid 0xae0300 dynamic

!              [VersaStack-NodeD]

  vsan 1 wwn 24:02:00:2a:6a:cd:ff:80 fcid 0xbb0600 dynamic

  vsan 102 wwn 24:02:00:2a:6a:cd:ff:80 fcid 0xae0400 dynamic

  vsan 102 wwn 20:00:00:25:b5:00:0b:0f fcid 0xae0401 dynamic

!              [VM-Host-Infra-01-B]

  vsan 102 wwn 20:00:00:25:b5:00:0b:1f fcid 0xae0402 dynamic

!              [VM-Host-Infra-02-B]

  vsan 1 wwn 50:05:07:68:0b:24:20:c6 fcid 0xbb0700 dynamic

  vsan 1 wwn 50:05:07:68:0b:34:20:86 fcid 0xbb0800 dynamic

  vsan 1 wwn 50:05:07:68:0b:22:20:86 fcid 0xbb0900 dynamic

!            [VersaStack-NodeC]

  vsan 1 wwn 50:05:07:68:0b:32:20:c6 fcid 0xbb0a00 dynamic

!            [VersaStack-NodeD]

 

 

interface port-channel2

  channel mode active

  switchport rate-mode dedicated

vsan database

  vsan 102 interface port-channel2

  vsan 102 interface fc1/3

  vsan 102 interface fc1/4

  vsan 102 interface fc1/5

  vsan 102 interface fc1/6

clock timezone PST 0 0

switchname mds-b

line console

line vty

boot kickstart bootflash:/m9100-s5ek9-kickstart-mz.6.2.9.bin

boot system bootflash:/m9100-s5ek9-mz.6.2.9.bin

interface fc1/1

interface fc1/2

interface fc1/3

interface fc1/4

interface fc1/5

interface fc1/6

interface fc1/7

interface fc1/8

interface fc1/9

interface fc1/10

interface fc1/11

interface fc1/12

interface fc1/13

interface fc1/14

interface fc1/15

interface fc1/16

interface fc1/17

interface fc1/18

interface fc1/19

interface fc1/20

interface fc1/21

interface fc1/22

interface fc1/23

interface fc1/24

interface fc1/25

interface fc1/26

interface fc1/27

interface fc1/28

interface fc1/29

interface fc1/30

interface fc1/31

interface fc1/32

interface fc1/33

interface fc1/34

interface fc1/35

interface fc1/36

interface fc1/37

interface fc1/38

interface fc1/39

interface fc1/40

interface fc1/41

interface fc1/42

interface fc1/43

interface fc1/44

interface fc1/45

interface fc1/46

interface fc1/47

interface fc1/48

interface fc1/1

interface fc1/2

!Active Zone Database Section for vsan 102

zone name versastack vsan 102

    member pwwn 50:05:07:68:0b:24:20:fc

!               [VersaStack-NodeA]

    member pwwn 50:05:07:68:0b:24:20:fd

!               [VersaStack-NodeB]

    member pwwn 50:05:07:68:0b:22:20:86

!               [VersaStack-NodeC]

    member pwwn 50:05:07:68:0b:32:20:c6

!               [VersaStack-NodeD]

 

zone name VM-Host-Infra-01-B vsan 102

    member pwwn 20:00:00:25:b5:00:0b:0f

!               [VM-Host-Infra-01-B]

    member pwwn 50:05:07:68:0b:24:20:fc

!               [VersaStack-NodeA]

    member pwwn 50:05:07:68:0b:24:20:fd

!               [VersaStack-NodeB]

    member pwwn 50:05:07:68:0b:22:20:86

!               [VersaStack-NodeC]

    member pwwn 50:05:07:68:0b:32:20:c6

!               [VersaStack-NodeD]

 

zone name VM-Host-Infra-02-B vsan 102

    member pwwn 20:00:00:25:b5:00:0b:1f

!               [VM-Host-Infra-02-B]

    member pwwn 50:05:07:68:0b:24:20:fc

!               [VersaStack-NodeA]

    member pwwn 50:05:07:68:0b:24:20:fd

!               [VersaStack-NodeB]

    member pwwn 50:05:07:68:0b:22:20:86

!               [VersaStack-NodeC]

    member pwwn 50:05:07:68:0b:32:20:c6

!               [VersaStack-NodeD]

 

zoneset name versastackzoneset vsan 102

    member versastack

    member VM-Host-Infra-01-B

    member VM-Host-Infra-02-B

 

zoneset activate name versastackzoneset vsan 102

do clear zone database vsan 102

!Full Zone Database Section for vsan 102

zone name versastack vsan 102

    member pwwn 50:05:07:68:0b:24:20:fc

!               [VersaStack-NodeA]

    member pwwn 50:05:07:68:0b:24:20:fd

!               [VersaStack-NodeB]

    member pwwn 50:05:07:68:0b:22:20:86

!               [VersaStack-NodeC]

    member pwwn 50:05:07:68:0b:32:20:c6

!               [VersaStack-NodeD]

 

zone name VM-Host-Infra-01-B vsan 102

    member pwwn 20:00:00:25:b5:00:0b:0f

!               [VM-Host-Infra-01-B]

    member pwwn 50:05:07:68:0b:24:20:fc

!               [VersaStack-NodeA]

    member pwwn 50:05:07:68:0b:24:20:fd

!               [VersaStack-NodeB]

    member pwwn 50:05:07:68:0b:22:20:86

!               [VersaStack-NodeC]

    member pwwn 50:05:07:68:0b:32:20:c6

!               [VersaStack-NodeD]

 

zone name VM-Host-Infra-02-B vsan 102

    member pwwn 20:00:00:25:b5:00:0b:1f

!               [VM-Host-Infra-02-B]

    member pwwn 50:05:07:68:0b:24:20:fc

!               [VersaStack-NodeA]

    member pwwn 50:05:07:68:0b:24:20:fd

!               [VersaStack-NodeB]

    member pwwn 50:05:07:68:0b:22:20:86

!               [VersaStack-NodeC]

    member pwwn 50:05:07:68:0b:32:20:c6

!               [VersaStack-NodeD]

 

zoneset name versastackzoneset vsan 102

    member versastack

    member VM-Host-Infra-01-B

    member VM-Host-Infra-02-B

 

 

interface fc1/1

  port-license acquire

  channel-group 2 force

  no shutdown

 

interface fc1/2

  port-license acquire

  channel-group 2 force

  no shutdown

 

interface fc1/3

  port-license acquire

  no shutdown

 

interface fc1/4

  port-license acquire

  no shutdown

 

interface fc1/5

  port-license acquire

  no shutdown

 

interface fc1/6

  port-license acquire

  no shutdown

 

interface fc1/7

  port-license acquire

 

interface fc1/8

  port-license acquire

 

interface fc1/9

  port-license acquire

 

interface fc1/10

  port-license acquire

 

interface fc1/11

  port-license acquire

 

interface fc1/12

  port-license acquire

 

interface fc1/13

 

interface fc1/14

 

interface fc1/15

 

interface fc1/16

 

interface fc1/17

 

interface fc1/18

 

interface fc1/19

 

interface fc1/20

 

interface fc1/21

 

interface fc1/22

 

interface fc1/23

 

interface fc1/24

 

interface fc1/25

 

interface fc1/26

 

interface fc1/27

 

interface fc1/28

 

interface fc1/29

 

interface fc1/30

 

interface fc1/31

 

interface fc1/32

 

interface fc1/33

 

interface fc1/34

 

interface fc1/35

 

interface fc1/36

 

interface fc1/37

 

interface fc1/38

 

interface fc1/39

 

interface fc1/40

 

interface fc1/41

 

interface fc1/42

 

interface fc1/43

 

interface fc1/44

 

interface fc1/45

 

interface fc1/46

 

interface fc1/47

 

interface fc1/48

 

interface mgmt0

  ip address 10.29.151.19 255.255.255.0

ip default-gateway 10.29.151.1

 

mds-b#

 

Figure 7       Ports on Storwize Control Enclosure (Model 2076-524

 

Key

·         1, 2: 1GbE management, iSCSI and IP replication ports

·         3: 1GbE iSCSI and IP replication port

·         4-7: 8GbE fibre channel ports

 

 

Jeff Fultz, Technical Marketing Engineer, Server Access Virtualization Business Unit, Cisco Systems, Inc.

Jeff has over 20 years of experience in Information Systems and Application Development focusing on data center management, backup, and virtualization optimization related technologies. As a member of multiple engineering solution teams, Jeff has deployed, designed and tested a wide variety of enterprise solutions encompassing Cisco, VMware, HyperV, SQL, and Microsoft Exchange to name a few. Jeff is a Microsoft Certified System Engineer with multiple patents filed in the datacenter solutions space.

Sally Neate, Test Architect, Systems and Technology Group, IBM

Sally has over 10 years of engineering experience in IBM's Systems and Technology group, and has been involved in the development of the Storwize product range from its inception. As system test lead for the Storwize and SAN Volume Controller 7.2 and 7.3 releases, Sally has designed and tested systems to meet the demands of a wide range of mid-range and enterprise environments.

Acknowledgments

The authors would like to acknowledge the following for their support and contribution to the design, validation and creation of this Cisco Validated Design (CVD):

·         Adam Reid – Test Specialist, System Test and Technology Group, IBM

NOTE: Available paragraph styles are listed in the Quick Styles Gallery in the Styles group on the Home tab. Alternatively, they can be accessed via the Styles window (press Alt + Ctrl + Shift + S).