IBM PureFlex Solution for SmartCloud Desktop...

IBM PureFlex Solution for SmartCloud Desktop Infrastructure

Installation guide

1


Installation Guide

14 November 2013

IBM Systems and Technology Group ISV Enablement Team

https://twitter.com/IBMSystemsISVs�


Installation guide

2

Table of contents

Introduction .................................................................................................................................3 Installing hardware .....................................................................................................................6

Chassis health check ...............................................................................................................................6 Set IP addressing..................................................................................................................................... 6 Verify network switch configuration ......................................................................................................... 6 Verify compute node configuration .......................................................................................................... 7

Configure Flex System V7000 shared storage .......................................................................10 Add every host ....................................................................................................................................... 10 Create a pool ......................................................................................................................................... 13 Create a volume..................................................................................................................................... 18 Map volume to hosts.............................................................................................................................. 20 Configure Easy Tier ...............................................................................................................................21

Configure ESXi Hypervisor ......................................................................................................23 Install and configure Windows Storage Server......................................................................26

Mount the ISO image............................................................................................................................. 26 Install Windows Storage Server 2012.................................................................................................... 28 Teaming the virtual network ports.......................................................................................................... 28 Join a Windows domain......................................................................................................................... 30 Create cluster DNS name...................................................................................................................... 31 Enable clustering features ..................................................................................................................... 31 Configure scale-out file server role ........................................................................................................ 32 Prepare shared volume in Windows ...................................................................................................... 33 Create clustered resource ..................................................................................................................... 34

Install and configure vSphere..................................................................................................36 Install vSphere Client ............................................................................................................................. 36 Install vCenter database ........................................................................................................................ 36 Install vCenter Server for management VMs......................................................................................... 37 Configure vSphere for management VMs ............................................................................................. 37 Install vCenter Server for user VMs....................................................................................................... 37 Configure vSphere user VMs................................................................................................................. 37

Install VMware View ..................................................................................................................38 Install Citrix XenDesktop..........................................................................................................38 Appendix A: Default IP addresses...........................................................................................39 Resources..................................................................................................................................46 Trademarks and special notices..............................................................................................47


Installation guide

3

Introduction This technical guide provides information on how to install and configure the IBM® PureFlex™ Solution for SmartCloud Desktop Infrastructure (SDI). It does not contain all of the details and has references to IBM

and vendor documentation. It is recommended that IBM GTS or IBM Business Partner® services are used to perform a complete installation. The IBM PureFlex Solution for SDI also defaults to having 10 days of IBM Systems and Technology Group Lab Services time to help with hardware installation and

configuration.

The PureFlex Solution for SDI is based on the IBM PureFlex Enterprise Foundation with the following changes:

Shared storage using the IBM Flex System V7000 Storage Node

Networking using only 10 GbE FCoE (Fibre Channel over Ethernet)

Two IBM Flex System® x240 Compute Nodes for Microsoft® Windows® Storage Server 2012

Seven IBM Flex System x240 Compute Nodes for compute servers or Virtual Desktop Infrastructure (VDI) management

Table 1 shows the list of components with the default, minimum, and maximum count of each. Note that if more than one chassis is used, then top-of-rack (TOR) switches are added for 10 GbE and storage area network (SAN) connectivity. Flex System x240 Compute Nodes must be used for the Windows Storage

Server 2012 and VDI management servers. Flex System x240 or Flex System x222 Compute Nodes are recommended for the compute servers.

Component Description Default Minimum Maximum x240 ESXi servers (compute servers or VDI management) 7 2 33

x222 compute servers 0 0 33

x240 for Windows Storage Server 2012 2 2 2

IBM Flex System Manager 1 1 1

IBM Flex System V7000 Storage Node 1 1 9

IBM Storwize V7000 Expansion Enclosure 0 0 22 IBM System Networking RackSwitch G8052 (TOR) 0 0 2 IBM System Networking RackSwitch G8264 (TOR) 0 0 2 IBM SAN24B-4 switch (TOR) 0 0 2 IBM Flex System Enterprise Chassis 1 1 3

IBM PureFlex System Rack 1 1 2

Table 1: Components in the IBM PureFlex Solution for SmartCloud Desktop Infrastructure


Installation guide

4

The system configuration tool (e-config) allows the following changes to be made to the default configuration:

Update the default configuration of Windows Storage Server 2012 nodes to allow different processors, memory, or local drives. The minimum is 32 GB of memory. Note that it is recommended to change the default configuration for the two Windows Storage Servers so that

the two hard disk drives (HDDs) are factory configured in a RAID 1 array. Update the default configuration of ESXi servers to allow different processor, memory, or local

drives. The minimum is 256 GB of memory and this can be increased to 768 GB. Local solid-state

drives (SSDs) can be added for use by stateless desktops. Addition of up to two more Flex System Enterprise Chassis. Addition of up to eight additional Flex System V7000 storage nodes, although a maximum of four

is the most needed. Addition of up to 22 IBM Storwize® V7000 expansion enclosures. Twenty of the enclosures are

placed into a second rack.

Addition of compute nodes. By removing five of the standard ESXi servers, it is possible to add up to 33 ESXi servers (Flex System x240 or x222 Compute Nodes are recommended). For a balanced configuration, it is likely that at least one more Flex System storage node and one more

VDI management server are required. That leaves up to 28 ESXi servers (or 56 for the Flex System x222 Compute Node) which can be used for user VMs.

Networking is an important part of any SDI solution. The PureFlex Solution for SDI comes pre-configured

from the factory with all of the FCoE networking in place. It is only necessary to change the networking to suit the customer’s environment.

For a single-chassis solution, the customer can plug directly into the IBM Flex System CN4093 switches at

the back of the chassis to access both the management and data virtual local area networks (VLANs). The CN4093 switch is configured for three VLANs:

Management VLAN 4091

Data VLAN 4092

FCoE VLAN 1002

Top-of-rack switches are employed for solutions with more than one chassis. The TOR switches carry the

following traffic:

G8052: Infrastructure VLAN 4093 for systems management

G8264: Management VLAN 4091 and data VLAN 4092

SAN24B-4: Fibre Channel (FC) traffic for access to Flex System V7000 storage nodes.

Inside the chassis is FCoE, and outside, it is split into separate 10 Gb Ethernet and FC. In this case, the CN4093 switches are configured in the pass-through mode for the SAN fabric.


Installation guide

5

Figure 1 shows the network connectivity for a three-chassis solution. The detail shown for chassis 1 is abbreviated for clarity in chassis 2 and chassis 3. Not shown on this diagram is VLAN 4093 and how the

Chassis Management Module (CMM) is connected into the G8052 TOR switches.

A single-chassis solution is similar but without all the TOR switches and external chassis wiring except for the inter-switch link (ISL) connection between the two CN4093 switches. All chassis management can be

done through the CMM or IBM Flex System Manager™ (FSM).

.

Flex Chassis 1

Flex V7000 Storage Node

Controller 0 Controller 1

CN4054 with LOM

Port 0

CN40

93 S

witc

h

vLAN 4092(Data)

vLAN 4091(Manage)

vLAN 1002(FCoE)

FC2

Windows Storage Servers VDI Management Servers or Compute Servers (VMs)

721

vNic

0

3

G8264 TOR Switch

vNic

4

15 16

SAN24B-4 TOR Switch

CN40

93 S

witc

h

vLAN 4092(Data)

vLAN 4091(Manage)

vLAN 1002(FCoE)

721 3

G8264 TOR Switch

15 16

SAN24B-4 TOR Switch

FC0

FC1

FC0

FC1

CMM

Flex Chassis 2 Flex Chassis 3

40GbE40GbE

40GbE 40GbE

FCFC

FCFC

FCFC

40GbE ISL

vNic

6

Port 1

vNic

1

FC3

vNic

5

vNic

7

CN4054 with LOM

Port 0

FC2

vNic

0

vNic

4

vNic

6

Port 1

vNic

1

FC3

vNic

5

vNic

7

V7000 Expansion Enclosure

V7000 Expansion Enclosure

SAS SAS

40GbE40GbE

40GbE (ISL)

Figure 1: IBM PureFlex Solution for SDI – network connectivity


Installation guide

6

Installing hardware The hardware for the PureFlex Solution for SDI comes from the factory prewired and preconfigured. Installation of the hardware mainly consists of verifying that everything is correct and modifying IP

addresses to match the customer’s environment.

Chassis health check

After powering on the hardware, connect to the CMM web interface using the default IP address of each chassis and perform the following steps:

1. Review the system hardware using the CMM hardware topology page.

2. Verify that the system status and all the components are properly operational (green light check). The Events tab lists any outstanding errors or warnings.

3. Save the default CMM configuration for each chassis.

4. Validate the CMM security policy using the Mgt Module Management menu item, Security.

Set IP addressing

If needed, set the customer IP address of each Chassis Management Module. Each Chassis Management

Module can now be restarted using the Mgt Module Management menu item, Restart.

After adding the G8052 switches into the customer’s network, the Chassis Management Modules should now be addressable within the customer’s network. All remaining work on the hardware can now be

carried out from a remote location, that is, not in front of the hardware.

If needed, set the IP address of each compute node, switch, FSM, and Flex System V7000 storage node in the chassis using the IP addresses provided by the customer. Appendix A gives the default IP

addresses of every component.

Verify network switch configuration

Connect to each CN4093 switch and save the configuration file. Verify the following details for each switch:

1. Make sure that the dump from each switch has a unique (and logical) name.

2. VLANs are set correctly on the ports using UFP.

3. Spanning-tree is set correctly.

4. Trunks (aggregation groups) are set up correctly.

5. Network Time Protocol (NTP) is configured correctly.

6. Aliases, zones, and zone set are correct or set to the pass-through mode.


Installation guide

7

Connect to each G8264 TOR switch, if it exists, and verify the following details for each switch:

1. VLANs are set correctly.

2. Spanning-tree is set correctly.

3. Trunks (aggregation groups) are set up correctly.

4. NTP is configured correctly.

Connect to each SAN24B-4 TOR switch, if it exists, and verify that it is zoned correctly with access to Flex System V7000 Storage Nodes from every compute node.

Verify compute node configuration

Each compute node must be configured correctly for FCoE and the VLANs to work correctly. This can be verified as follows:

1. Use the Integrated Management Module (IMM) remote console facility and start the system into

the Unified Extensible Firmware Interface (UEFI) basic I/O system (BIOS).

2. Go to System Settings, then Network and click the first device in Network Device List.

3. Press Enter.


Installation guide

8

4. Set Advanced Mode to Enable, set Personality to FCoE, and set Multichannel Mode to IBM

Unified Fabric Protocol Mode.

5. Verify that the firmware version of the adapter is at least 4.6.281.15.


Installation guide

9

6. Exit the System Configuration, save the settings, and reboot.

7. After the reboot, press F1 and enter the BIOS screen.

8. Select System Settings and then Storage to check the FCoE adapter list.

9. Select the first adapter, press Enter, and verify that the CEE mode is selected.

10. Select Scan for Fibre Devices which registers the worldwide port name (WWPN) with the CN4093 switch. If zoning, hosts and host volumes are configured on the Flex System V7000 Storage Node, then this lists the volumes and is a good way to verify that everything is configured

correctly end to end.

11. Press Esc to return to the previous screen of adapters.

12. Select the second adapter, press Enter, and verify that the CEE mode is selected.

13. Select Scan for Fibre Devices to register the WWPN with the second CN4093 switch.


Installation guide

10

Configure Flex System V7000 shared storage This section describes how to configure each Flex System V7000 Storage Node for use in the PureFlex Solution for SDI. Refer to the IBM Flex System V7000 Storage Node Introduction and Implementation

Guide (at ibm.com/redbooks/abstracts/SG248068.html) for more details.

It is assumed that the FCoE configuration and zoning is complete. Each Flex System V7000 Storage Node must be able to see the initiator worldwide names (WWNs) and each initiator (host compute node) must be

able to see the Flex System V7000 Storage Node target WWNs.

The various disks on each Flex System V7000 Storage Node need to be configured into pools and shared volumes available to the various hosts. You might need to refer back to the original system design

document to understand how to configure the various disks. For example, two SSDs can be used for desktop images, an array of 10K drives are used for user folders and profile data that is only accessed by the Windows storage server nodes, the 15K rpm drives are used for remote desktops, and the remainder

of the SSDs are used by IBM Easy Tier®.

You need to perform the following steps to configure each Flex System V7000 Storage Node.

1. Add every host.

2. Create a pool.

3. Create a volume.

4. Map volume to hosts.

5. Configure Easy Tier.

Repeat steps 2 to 4 for each pool and volume that needs to be created. Repeat step 5 for each pool that needs Easy Tier drives attached to it.

Add every host

The hosts corresponding to initiators in the SAN fabric need to be explicitly added to the Flex System V7000 Storage Node. Note that the VMware vSphere client can be used to determine the WWNs for each ESXi host.


Installation guide

11

You need to perform the following steps to add every host.

1. Logon on to the Flex System V7000 Storage Node GUI and click the Hosts option on the Hosts

menu.

2. Click Add New Host and then click Fibre Channel Host.


Installation guide

12

3. Type the name of the host.

4. Select the first WWN that corresponds to the host from the list.

5. Click Add Port to List.

6. Select the second WWN that corresponds to the host from the list.

7. Click Add Port to List.

8. Retain the default settings for the other options and then click Create Host.


Installation guide

13

Create a pool

Perform the following steps to create a pool.

1. Click Internal Storage on the Pools menu.


Installation guide

14

2. Select the Select a different configuration option and select the drive class you want to

configure.


Installation guide

15

3. Select a RAID type from the Preset list. Use RAID 1 for images on two SSDs and RAID 10 for other types of storage.

4. Choose the pool configuration.

If you choose Optimize for Performance, this allows the Flex System V7000 Storage System to

determine the optimal managed disk (MDisk) size (usually eight disks per MDisk). But if you do not specify a multiple of this size, a pool will be created with a specific number of disks for maximum performance which is not necessarily what was specified in the Number of drives to provision

field.


Installation guide

16

5. To ensure that a pool is created based on the number of drives requested, select Optimize for Capacity.


Installation guide

17

6. Click Next.

7. Retain the default setting, Create one or more new pools. The other option, Expand an existing pool, is used for Easy Tier configuration.

8. Name the pool. A useful naming convention is as follows:

<Flex System V7000 name>_<number of drives><drive type>_R<RAID level>

For example: S74_12HDD_R10 or S74_2SDD_R1


Installation guide

18

9. Click Finish and the pool of MDisks is created.

Create a volume

Perform the following steps to create a volume.

1. Click Volumes on the Volumes menu.

2. Click New volume on the pool just created and select a preset volume type. Normally,

Thin-Provision is used.


Installation guide

19

3. Type in a volume name.

4. The size is normally the whole pool. More volumes can be added if appropriate. Click Create to create the volume. Or, click Create and Map to Host to combine the steps of creating the volume and mapping it to one or more hosts.


Installation guide

20

Map volume to hosts

All hosts except the Windows Storage Servers need access to all volumes except the user folder volume. Equally, the Windows Storage Servers only need access to the user folder volume, that is, the volume that

will be shared using Common Internet File System (CIFS) or Network File System (NFS).

1. Click Volumes by Host on the Volumes menu.

2. Right-click a volume and click Map to Host.

3. Select the host to apply the mapping to.


Installation guide

21

4. Select volumes and use the arrow button to map or unmap them to the specified host. Click Map Volumes to apply the changes.

5. Acknowledge the warning message when a volume is mapped to more than one host.

Configure Easy Tier

To configure Easy Tier, a pool of SSDs is used to expand an existing pool. Create a pool of SSDs

following the steps in the “Create a pool” section on page 17 but in step 7, select the Expand an existing pool option and select the required pool from the list. Click Finish to complete the operation.


Installation guide

22

By clicking Volumes by Pool on the Volumes menu, the pool with Easy Tier has a modified icon and indicates Easy Tier Active.

At this point, the name of the pool can be changed to indicate that it has Easy Tier active.


Installation guide

23

Configure ESXi Hypervisor Each compute node, except the two for Windows Storage Servers, should have a Universal Serial Bus (USB) key with VMware ESXi 5.1 update 1. This version of ESXi is the minimum version and the build

number (shown at boot time) should be at least 1065491. The ESXi hypervisor instance on each compute node end-point is configured using the following steps:

1. Add the proposed host name for the node to the Active Directory and Domain Name System

(DNS) server.

2. Use the Remote Console feature of the IMM and select Boot to start the ESXI hypervisor. The hypervisor version number appears during boot and on the final screen after a successful boot.

3. Press F2 and log on to the ESXi hypervisor using the default user of root. The password is not set at this time and does not need to be entered.


Installation guide

24

4. Select Configure Password and follow the prompts to enter a new password for root.

5. Select Configure Management Network and proceed to set up the network as follows:

a. Select the first two network adapters, labeled vmnic0 and vmnic1, which correspond to virtual network interface card (vNIC) 0 for each CN4093 chassis switch. There should be pairs of vNICs for each VLAN. Note that vmnic2 and vmnic3 are missing and correspond to the VLAN

for FCoE.

b. Type in the IP address, mask, and gateway IP address for this node.

c. Disable or use IPv6 as required.

d. Type in the IP address of the primary DNS server and the alternate one, if available. Add the fully qualified DNS host name for this node.

e. Press Esc and save the network configuration.


Installation guide

25

6. Select Restart Management Network and follow the prompts.

7. Select Test Management Network to verify that the gateway address and DNS servers are

accessible and can resolve the host name.

8. If remote SSH access into the hypervisor is needed, select Troubleshooting Options and click Disable ESXi Shell to change the setting to Enable ESXi Shell. Do the same for Enable SSH and press Esc to save the options. Do not turn on this option if high security is needed.

9. Press Esc to log out.

Repeat the steps for all of the other EXSi hosts. Note that each Flex System x222 Compute Node has two ESXi hosts to be configured.


Installation guide

26

Install and configure Windows Storage Server Two compute nodes in the system are reserved for a Windows Storage Server 2012 cluster. This cluster exposes CIFS or NFS file shares, which can be used to store user folders, shared folders, or user profile

data on the Flex System V7000 shared storage. Refer to Microsoft Windows Storage Server Overview (at http://technet.microsoft.com/en-us/library/jj643303) for more details.

If the customer has an existing solution for file I/O then that can be used instead if it was deemed sufficient

when the PureFlex Solution for SDI was designed and ordered.

It is assumed at this stage that the customer already has a high availability Active Directory (AD) solution and the AD servers are accessible from the PureFlex System.

It is assumed that the Windows Storage Servers arrive with a RAID 1 configuration for the two HDDs. This needs to be verified in the IMM and configured correctly before installing Windows Storage Server 2012 on each Compute Node.

Each compute node for Windows Storage Server 2012 is included with a Microsoft license. This section describes how to install and configure the Windows Storage Server cluster for use in the PureFlex Solution for SDI. The steps are:

1. Mount the ISO image.

2. Install Windows Storage Server 2012.

3. Team the virtual network ports.

4. Join a Windows domain.

5. Create cluster DNS name.

6. Enable clustering features.

7. Configure scale-out file server role.

8. Prepare a volume in Windows.

9. Create the clustered resource.

Mount the ISO image

Installing Windows Storage Server 2012 consists of creating an ISO image and installing that ISO image onto the two Compute Nodes which are nodes 3 and 4 on the first chassis. For a multi-chassis system it may be preferable to have these two nodes in separate chassis to provide an additional degree of higher

availability.

1. Use your favorite utility to create an ISO image from the Windows Storage Server 2012 DVD.

2. Assuming that the node has been left started in the IMM from the previous steps, log on to the

IMM for the node you plan to install the operating system onto.

http://technet.microsoft.com/en-us/library/jj643303


Installation guide

27

3. On the main menu, click Server Management Remote Control.

4. Select the client you need to use to open a remote console (Active X or Java™) and then click Start remote control in single-user mode.

5. If you plan to install the operating system using a local ISO file or a bootable device, on the remote console click Tool Launch Virtual Media.

Note: You can also connect a bootable USB or a USB optical drive physically to the node. If you choose to do so, you can skip this step as well as steps 6 and 7.

6. A small pop-up window appears populating the physical drives on your workstation. If you are not

starting from an ISO file, you need to click Add Image from the set of buttons on the right and select your ISO file to add it to the list of bootable media.


Installation guide

28

7. Select the Map check box for the bootable media you need to install your operating system from and click Mount Selected.

Note: Do not close the virtual media window or the drive and ISO you mounted will unmount.

Install Windows Storage Server 2012

Follow the usual steps to install the Windows OS including several reboots of the compute node. The mounted image is automatically dismounted on the first reboot and is no longer needed.

After the OS is successfully installed, log on with the administrator account and the password that was

entered during install. The Server Manager is displayed. Select Local Server and use customer standards to perform basic configuration of items such as:

Computer name

Time zone

System date and time or NTP server

Remote desktop enabling and configuration

Firewall

Repeat the IMM image mount and OS installation for the second node.

Teaming the virtual network ports

Navigate to the Network Connections panel and notice that the virtual network ports are listed. There

should be two for the 4091 management VLAN and two for the 4092 data VLAN. Any additional customer requested VLANs might also be listed, such as VLAN 4083 as shown in the following figure.


Installation guide

29

The virtual network ports are summarized in Table 2.

Adapter name MAC address IP address VLAN Network type

vNIC 1 Port 1 – vNIC11 6C-AE-8B-2D-4E-30 N/A 4091 MGMT Network

vNIC 1 Port 2 – vNIC12 6C-AE-8B-2D-4E-34 N/A 4091 MGMT Network

vNIC 3 Port 1 – vNIC31 6C-AE-8B-2D-4E-32 N/A 4092 DATA Network

vNIC 3 Port 2 – vNIC32 6C-AE-8B-2D-4E-36 N/A 4092 DATA Network

Table 2: Summary table of virtual NICs

Note that vNIC 2 Port 1 and vNIC 2 Port 2 have been used for FCoE traffic. Table 3 shows the three teamed virtual ports need to be created.

Adapter name MAC address IP address VLAN Network type

MGMT_VLAN 4091 6C-AE-8B-2D-4E-30 N/A 4091 MGMT Network

DATA_VLAN 4092 6C-AE-8B-2D-4E-32 N/A 4092 DATA Network

Table 3: Teamed virtual NICs

You need to perform the following steps to team the virtual network ports. Refer to the Windows Server

2012 NIC Teaming (LBFO) Deployment and Management (http://www.microsoft.com/en-

us/download/details.aspx?id=30160) document for more details.

1. The NIC Teaming GUI can be invoked from Server Manager or by invoking lbfoadmin.exe at a

command prompt.

http://www.microsoft.com/en-us/download/details.aspx?id=30160



Installation guide

30

2. These networks can be configured to suit the customer’s environment. The Windows Storage Server cluster network in this case uses the DATA_VLAN 4092 Teamed adapter for both private

and cluster connections.

3. Change the network adapter binding order to ensure that the internet network adapter is the first.

a. Open the following path: Control Panel\Network and Internet\Network Connections.

b. Press Alt to display the menu bar.

c. Click Advanced Advanced Settings.

d. Modify the binding order to ensure that the data network is at the top.

4. Depending on the customer connectivity to the Internet, it is now possible for Windows Storage Server 2012 to be automatically activated from the Microsoft website. This can be verified by

displaying the Properties window of My Computer.

Repeat for the second node.

Join a Windows domain

Assuming Active Directory is already configured, the server can be joined to a domain. Ensure that DNS is set up correctly to communicate with the proper server. Note that Windows Storage Server cannot act as a domain controller itself but it can have Active Directory installed on it if not already elsewhere in the

customer’s environment.


Installation guide

31

Joining a domain forces the user to log in again. After this is working, log off and all future interaction can be done using Remote Desktop connection manager rather than the IMM console.

Before going further, it is advisable to check for updates and allow the OS to be updated either automatically or manually depending on the chosen option. Ensure that the Failover Cluster Manager GUI KB2803748 is applied.

Repeat for the second node.

Create cluster DNS name

To enable the cluster on each Windows Storage Server node, first create a DNS host record for the cluster

name and assign an IP address for the cluster in the customer’s DATA domain.

Enable clustering features

Refer to the Windows Server 2012 Creating a Failover Cluster (http://technet.microsoft.com/en-

us/library/dn505754.aspx) document for more details. The steps to enable a storage cluster using the

Server Manager are:

1. Open the Add Roles and Features wizard.

2. Ensure that the File and iSCSI Services role is selected and select File Server.

3. Select the Failover Clustering Feature.

4. Open Failover Clustering Manager.

5. Click Create Cluster on the Actions menu.

6. Add both Windows Storage Server compute names to the Selected Servers list.

http://technet.microsoft.com/en-us/library/dn505754.aspx



Installation guide

32

7. Run cluster validation and the validate configuration wizard is opened.

8. Click Run all tests.

9. Review test results, take an appropriate and recommended action and re-run the validation until the cluster is found suitable. If storage has not been attached to the WSS nodes, those tests will not run, however, the cluster can still be created. One common problem is adapters that are

enabled but not configured.

10. Next, the access point needs to be defined. Enter a cluster name.

11. Select the internal network and enter the IP address for the cluster. Note that networks which are

missing a gateway are not listed.

Repeat the steps for the second node.

Configure scale-out file server role

Configure the scale-out file server role using the Server Manager as follows:

1. Click Configure Role to start the wizard.

2. Click File Server role and click Next.

3. Select Scale-Out File Server and click Next.


Installation guide

33

4. Type the name for the role and click Next.

5. Review the summary and click Next.

The scale-out file server cluster is now configured.

Prepare shared volume in Windows

Each disk to be shared needs to be prepared as a Windows volume.

1. From one of the Windows Storage Server nodes, navigate to Computer Manager Disk

Management.

2. Perform a rescan operation for new disks. If no disks are found, then recheck the SAN fabric and zoning.

3. Set any discovered disks to online.

4. Initialize a volume.

5. Format the volume with the required allocation unit size and for consistency, set the volume label

to be the same as the cluster volume name. Do not use a drive letter or mount point.


Installation guide

34

Create clustered resource

Finally, create a clustered resource for each of the volumes:

1. Open Failover Cluster Manager on one of the Windows Storage Server nodes and navigate to

Storage Disks.

2. Click Add Disk from the right tree.

3. Right-click the new disk and set it as offline.


Installation guide

35

4. Right-click the new disk and click Add to Cluster Shared Volumes.

5. Right-click the disk and set it to online.

6. Navigate to the Roles page and select the Scale-Out File Server Role

7. On the right tree, click Add File Share.

8. Complete the File Share wizard using the following details.

a. SMB Share = Quick

b. Server = Select the name of the scale-out file server role

c. Share Location = Select the new clustered share volume

d. Share Name = Enter the new share name

9. Evaluate the summary page and then click Create.


Installation guide

36

Install and configure vSphere VMware vSphere is used to manage the ESXi hypervisor instances and the virtual machines running under those hypervisors. This documentation provides an overview of what is needed. Refer to the

VMware vSphere 5.1 documentation (http://pubs.vmware.com/vsphere-51/index.jsp) for more details.

The vCenter Server is used to manage a group of VMs. The server needs only limited high availability and it is sufficient to use VMware failover whereby if a VM goes down, it is restarted on another node in the

cluster. It is recommended to have one or more vCenter Servers for each set of user VMs (up to 2000 VMs) and also one vCenter Server for the management VMs. Note that the database should be on shared storage and the same database can be used by multiple vCenter Servers.

The steps to install and configure the vSphere management tools are:

1. Install vSphere Client.

2. Install vCenter Database Server.

3. Install vCenter Server for management VMs.

4. Configure vSphere for management VMs.

5. Install vCenter Server for user VMs.

6. Configure vSphere for user VMs.

Repeat steps 5 and 6 for as many vCenter Servers that are needed.

Install vSphere Client

The vSphere Client provides the simplest way to manage the ESXi hosts. This client can be installed on any machine in the network such as the Windows Storage Servers or an external machine that is connected to the ESXi hosts. The vSphere web client can also be installed.

Refer to the following documentation page for more details: http://pubs.vmware.com/vsphere-

51/topic/com.vmware.vsphere.install.doc/GUID-BBD3580E-4034-4E05-9558-D88D74E5D1D7.html

Install vCenter database

Log on to one of the management hosts using the vCenter client and configure the storage location for

VMs on that host. Repeat the steps for the second management host.

Create a new VM using the vCenter client. The minimum requirements are four virtual processors, 4 GB of memory, and 15 GB for the image. Refer to the following documentation for more details:

http://pubs.vmware.com/vsphere-51/topic/com.vmware.vsphere.vm_admin.doc/GUID-7834894B-DD17-

4D59-A9BF-A33D02478521.html

Install Microsoft Windows Server 2008 R2, license the OS, and perform the updates. This VM can now be

used as a template for other instances of Microsoft 2008 R2. Note that recently released Microsoft 2012 R2 might be preferred.

http://pubs.vmware.com/vsphere-51/index.jsp

http://pubs.vmware.com/vsphere-51/topic/com.vmware.vsphere.install.doc/GUID-BBD3580E-4034-4E05-9558-D88D74E5D1D7.html

http://pubs.vmware.com/vsphere-51/topic/com.vmware.vsphere.install.doc/GUID-BBD3580E-4034-4E05-9558-D88D74E5D1D7.html

http://pubs.vmware.com/vsphere-51/topic/com.vmware.vsphere.vm_admin.doc/GUID-7834894B-DD17-4D59-A9BF-A33D02478521.html

http://pubs.vmware.com/vsphere-51/topic/com.vmware.vsphere.vm_admin.doc/GUID-7834894B-DD17-4D59-A9BF-A33D02478521.html


Installation guide

37

Alternatively, if a template already exists, then a VM can be cloned from the template. Refer to the following documentation for more details: http://pubs.vmware.com/vsphere-

51/topic/com.vmware.vsphere.vm_admin.doc/GUID-F40130B0-0194-4A41-91FA-1A967721924B.html

vSphere supports several different databases including IBM DB2®, Microsoft SQL Server, and Oracle. The database can be in local or remote data stores.

Create an instance of a Windows 2008 R2 VM and install the database server of choice. Refer to the following documentation for more details: http://pubs.vmware.com/vsphere-

51/topic/com.vmware.vsphere.install.doc/GUID-55F7FFDB-01B8-4C18-AA89-DC28BD9B1E9F.html

Install vCenter Server for management VMs

In the case for the management VMs, vCenter Server can be installed using the Simple Install method as documented at: http://pubs.vmware.com/vsphere-51/topic/com.vmware.vsphere.install.doc/GUID-

3CAC53FB-ECAA-434D-A711-B428F6220807.html

Configure vSphere for management VMs

Connect to a vSphere Server using the vSphere Client or vSphere Web Client and perform the following steps:

1. Add licenses for vCenter and ESXi.

2. Create a host cluster for management and add the two management hosts. Note that in larger user configurations, it might be necessary to have a third-management host to provide scalability and failover of the management nodes, that is, all the users need to be managed by the remaining

two hosts if one goes down.

3. Configure the high availability for the management hosts.

Install vCenter Server for user VMs

In the case for the user VMs, it is recommended to have separate VMs for the various functions of vCenter

Server – do not use the Simple Install method. That is to separately install vCenter Single Sign-On, vCenter Inventory Service, and vCenter Server as documented at: http://pubs.vmware.com/vsphere-

51/index.jsp#com.vmware.vsphere.install.doc/GUID-595E62F1-4D32-4A09-81F4-BE59B9217A51.html

Multiple VMs are needed in this case and can be cloned from the template previously created.

Configure vSphere user VMs

Connect to a vSphere Server using the vSphere Client or vSphere Web Client and perform the following

steps:

1. Add licenses for vCenter and ESXi.

http://pubs.vmware.com/vsphere-51/topic/com.vmware.vsphere.vm_admin.doc/GUID-F40130B0-0194-4A41-91FA-1A967721924B.html

http://pubs.vmware.com/vsphere-51/topic/com.vmware.vsphere.vm_admin.doc/GUID-F40130B0-0194-4A41-91FA-1A967721924B.html

http://pubs.vmware.com/vsphere-51/topic/com.vmware.vsphere.install.doc/GUID-55F7FFDB-01B8-4C18-AA89-DC28BD9B1E9F.html

http://pubs.vmware.com/vsphere-51/topic/com.vmware.vsphere.install.doc/GUID-55F7FFDB-01B8-4C18-AA89-DC28BD9B1E9F.html

http://pubs.vmware.com/vsphere-51/topic/com.vmware.vsphere.install.doc/GUID-3CAC53FB-ECAA-434D-A711-B428F6220807.html

http://pubs.vmware.com/vsphere-51/topic/com.vmware.vsphere.install.doc/GUID-3CAC53FB-ECAA-434D-A711-B428F6220807.html

http://pubs.vmware.com/vsphere-51/index.jsp#com.vmware.vsphere.install.doc/GUID-595E62F1-4D32-4A09-81F4-BE59B9217A51.html

http://pubs.vmware.com/vsphere-51/index.jsp#com.vmware.vsphere.install.doc/GUID-595E62F1-4D32-4A09-81F4-BE59B9217A51.html


Installation guide

38

2. Create a host cluster for users and the user hosts. Note that more than one cluster might be needed depending on the number of supported users.

3. Create a user VM and install the User OS (Windows XP or Windows 7).

4. License the VM and install OS updates.

5. Create a template for the user VM.

6. Configure the virtual networking for the user hosts and test VMware vMotion of the management VMs.

Install VMware View The PureFlex Solution for SDI has a default of 500 user licenses of VMware Horizon View 5.2, which can

be changed when the hardware is being configured before ordering.

Because there are many variations and considerations for installing VMware View, which are version and feature dependent, it is best to use an experienced installer such as IBM GTS or a Business Partner. You

can find the VMware documentation at: http://www.vmware.com/support/pubs/view_pubs.html.

Install Citrix XenDesktop Because there are many variations and considerations for installing Citrix XenDesktop, which are version and feature dependent, it is best to use an experienced installer such as IBM GTS or a Business Partner.

You can find the documentation for Citrix XenDesktop at: http://support.citrix.com/proddocs/topic/xendesktop/xd-library-wrapper.html

http://www.vmware.com/support/pubs/view_pubs.html

http://support.citrix.com/proddocs/topic/xendesktop/xd-library-wrapper.html


Installation guide

39

Appendix A: Default IP addresses The following table list the default IP addresses for every component in the PureFlex Solution for SDI.

Chassis Component IPv4 IPv6 VLAN Username / Password

CMM

CMM #1 192.168.93.100 fd8c:215d:178e:c0de 4093 USERID/Passw0rd Chassis 1

CMM #2 192.168.93.100 fd8c:215d:178e:c0de 4093 USERID/Passw0rd

CMM #1 192.168.93.102 fd8c:215d:178e:c0de 4093 USERID/PASSW0RD Chassis 2

CMM #2 192.168.93.102 fd8c:215d:178e:c0de 4093 USERID/PASSW0RD

CMM #1 192.168.93.104 fd8c:215d:178e:c0de 4093 USERID/PASSW0RD Chassis 3

CMM #2 192.168.93.104 fd8c:215d:178e:c0de 4093 USERID/PASSW0RD

IOM

IOM #1 192.168.93.120 fd8c:215d:178e:c0de 4093 USERID/Passw0rd


IOM #3 192.168.93.122 fd8c:215d:178e:c0de 4093 USERID/Passw0rd Chassis 1










FSM

eth0 N/A fd8c:215d:178e:c0de 4093 USERID/Passw0rd Chassis 1

eth1 10.91.0.2 fd8c:215d:178e:c0de 4091 USERID/Passw0rd

Node

IMM 192.168.93.150 fd8c:215d:178e:c0de 4093 Same as CMM Chassis 1: Node 1.0

ESXi 10.91.0.2 N/A 4091 root/Passw0rd




Installation guide

40


























IMM 192.168.93.157 fd8c:215d:178e:c0de 4093 Same as CMM Chassis 1: Node 8


IMM 192.168.94.157 fd8c:215d:178e:c0de 4093 Same as CMM Chassis 1: Node 8




Chassis 1: IMM 192.168.94.158 fd8c:215d:178e:c0de 4093 Same as CMM


Installation guide

41


Node 9.1 ESXi 10.91.32.3 N/A 4091 root/Passw0rd
































Installation guide

42


































Installation guide

43


































Installation guide

44


































Installation guide

45











Flex System V7000 Storage Node

Canister #1 192.168.93.210 fd8c:215d:178e:c0d 4093 superuser/passw0rd


V7000 #1

Cluster #1 192.168.93.213 fd8c:215d:178e:c0d 4093 superuser/passw0rd



V7000 #2


V7000 #3 Canister #1 192.168.93.226 fd8c:215d:178e:c0d 4093 superuser/passw0rd



V7000 #4 Canister #1 192.168.93.229 fd8c:215d:178e:c0d 4093 superuser/passw0rd



Top of rack components

G8264 #1 Management 192.168.93.220 fd8c:215d:178e:c0d 4093 USERID/Passw0rd


SAN24B #1 Management 192.168.93.222 fd8c:215d:178e:c0d 4093 USERID/Passw0rd

SAN24B #2 Management 192.168.93.223 fd8c:215d:178e:c0d 4093 USERID/Passw0rd




Installation guide

46

Resources IBM SmartCloud Desktop Infrastructure offering home page

ibm.com/systems/virtualization/desktop-virtualization

IBM PureFlex System and IBM Flex System Products and Technology

ibm.com/redbooks/abstracts/sg247984.html

IBM Flex System V7000 Storage Node Introduction and Implementation Guide

ibm.com/redbooks/abstracts/SG248068.html

Microsoft Windows Storage Server Overview


Windows Server 2012 NIC Teaming (LBFO) Deployment and Management


Windows Server 2012 Creating a Failover Cluster


vSphere 5.1 Documentation Center


Deploying IBM Storwize V7000 in VMware Environments – Best Practices

ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP101760

VMware (Horizon) View Documentation


Citrix XenDesktop Documentation


https://twitter.com/IBMSystemsISVs�

http://www.ibm.com/systems/virtualization/desktop-virtualization





http://www-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP101760




Installation guide

47

Trademarks and special notices © Copyright IBM Corporation 2013.

References in this document to IBM products or services do not imply that IBM intends to make them

available in every country.

IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. If these and other IBM trademarked

terms are marked on their first occurrence in this information with a trademark symbol (® or ™), these symbols indicate U.S. registered or common law trademarks owned by IBM at the time this information was published. Such trademarks may also be registered or common law trademarks in other countries. A

current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.

Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or

its affiliates.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.

Other company, product, or service names may be trademarks or service marks of others.

Information is provided "AS IS" without warranty of any kind.

All customer examples described are presented as illustrations of how those customers have used IBM

products and the results they may have achieved. Actual environmental costs and performance characteristics may vary by customer.

Information concerning non-IBM products was obtained from a supplier of these products, published

announcement material, or other publicly available sources and does not constitute an endorsement of such products by IBM. Sources for non-IBM list prices and performance numbers are taken from publicly available information, including vendor announcements and vendor worldwide homepages. IBM has not

tested these products and cannot confirm the accuracy of performance, capability, or any other claims related to non-IBM products. Questions on the capability of non-IBM products should be addressed to the supplier of those products.

All statements regarding IBM future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only. Contact your local IBM office or IBM authorized reseller for the full text of the specific Statement of Direction.

Some information addresses anticipated future capabilities. Such information is not intended as a definitive statement of a commitment to specific levels of performance, function or delivery schedules with respect to any future products. Such commitments are only made in IBM product announcements. The information is

presented here to communicate IBM's current investment and development activities as a good faith effort to help with our customers' future planning.

http://www.ibm.com/legal/copytrade.shtml


Installation guide

48

Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput or performance that any user will experience will vary depending upon

considerations such as the amount of multiprogramming in the user's job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve throughput or performance improvements equivalent to the ratios stated here.

Photographs shown are of engineering prototypes. Changes may be incorporated in production models.

Any references in this information to non-IBM websites are provided for convenience only and do not in any manner serve as an endorsement of those websites. The materials at those websites are not part of

the materials for this IBM product and use of those websites is at your own risk.

Date post:	07-Oct-2020
Category:	Documents
Upload:	others
View:	23 times
Download:	0 times

IBM PureFlex Solution for SmartCloud Desktop...

Documents