Cisco UCS B-Series Blade Servers Windows Installation Guide...Cisco UCS B-Series Blade Servers Windows Installation Guide First Published: April22,2011Last Modified: March20,2015Americas

Cisco UCS B-Series Blade Servers Windows Installation GuideFirst Published: April 22, 2011

Last Modified: March 20, 2015

Americas HeadquartersCisco Systems, Inc.170 West Tasman DriveSan Jose, CA 95134-1706USAhttp://www.cisco.comTel: 408 526-4000 800 553-NETS (6387)Fax: 408 527-0883

Text Part Number: OL-22764-04

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS,INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND,EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.

THE SOFTWARE LICENSE AND LIMITEDWARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITHTHE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY,CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.

The following information is for FCC compliance of Class A devices: This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to part 15of the FCC rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipmentgenerates, uses, and can radiate radio-frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications.Operation of this equipment in a residential area is likely to cause harmful interference, in which case users will be required to correct the interference at their own expense.

The following information is for FCC compliance of Class B devices: This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to part 15of the FCC rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses and can radiate radiofrequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interferencewill not occur in a particular installation. If the equipment causes interference to radio or television reception, which can be determined by turning the equipment off and on, users areencouraged to try to correct the interference by using one or more of the following measures:

• Reorient or relocate the receiving antenna.

• Increase the separation between the equipment and receiver.

• Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.

• Consult the dealer or an experienced radio/TV technician for help.

Modifications to this product not authorized by Cisco could void the FCC approval and negate your authority to operate the product

The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public domain versionof the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.

NOTWITHSTANDINGANYOTHERWARRANTYHEREIN, ALL DOCUMENT FILES AND SOFTWAREOF THESE SUPPLIERS ARE PROVIDED "AS IS"WITHALL FAULTS.CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OFMERCHANTABILITY, FITNESS FORA PARTICULAR PURPOSEANDNONINFRINGEMENTORARISING FROMACOURSEOFDEALING, USAGE, OR TRADE PRACTICE.

IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUTLIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERSHAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, networktopology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentionaland coincidental.

Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: http://www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnershiprelationship between Cisco and any other company. (1110R)

© 2011-2012 Cisco Systems, Inc. All rights reserved.

http://www.cisco.com/go/trademarks

http://www.cisco.com/go/trademarks

C O N T E N T S

P r e f a c e Preface v

Audience v

Conventions v

Related Cisco UCS Documentation vii

Documentation Feedback vii

C H A P T E R 1 Installation Checklists and Prerequisites 1

Installation Overview Checklist 1

Installation Prerequisites Checklist 2

Service Profile Configuration Prerequisites 3

SAN Boot Topology Example 6

Mounting the Installation ISO Image 6

C H A P T E R 2 Windows Server 2003 Installation 9

Installing Windows Server 2003 on an Internal Drive 9

Installing Windows Server 2003 on a Bootable SAN LUN 11

C H A P T E R 3 Windows Server 2012 and Windows Server 2008 Installation 13

Installing Windows Server 2012 and Windows Server 2008 on an Internal Drive 13

Installing Windows Server 2012 and Windows Server 2008 on a Bootable SAN LUN 15

A P P E N D I X A Installation Driver Information 17

Windows Installation Drivers 17

Viewing Installed Devices 18

Viewing Installed Devices Using the UCS Manager GUI 18

Viewing Installed Interface Cards Using the UCS Manager CLI 18

Viewing Installed Devices Using the KVM Console 19

Cisco UCS B-Series Blade Servers Windows Installation Guide OL-22764-04 iii

Cisco UCS B-Series Blade Servers Windows Installation Guideiv OL-22764-04

Contents

Preface

This preface includes the following sections:

• Audience, page v

• Conventions, page v

• Related Cisco UCS Documentation, page vii

• Documentation Feedback, page vii

AudienceThis guide is intended primarily for data center administrators with responsibilities and expertise in one ormore of the following:

• Server administration

• Storage administration

• Network administration

• Network security

ConventionsIndicationText Type

GUI elements such as tab titles, area names, and field labels appear in this font.

Main titles such as window, dialog box, and wizard titles appear in this font.

GUI elements

Document titles appear in this font.Document titles

In a Text-based User Interface, text the system displays appears in this font.TUI elements

Terminal sessions and information that the system displays appear in thisfont.

System output

Cisco UCS B-Series Blade Servers Windows Installation Guide OL-22764-04 v

IndicationText Type

CLI command keywords appear in this font.

Variables in a CLI command appear in this font.

CLI commands

Elements in square brackets are optional.[ ]

Required alternative keywords are grouped in braces and separated by verticalbars.

{x | y | z}

Optional alternative keywords are grouped in brackets and separated by verticalbars.

[x | y | z]

A nonquoted set of characters. Do not use quotation marks around the string orthe string will include the quotation marks.

string

Nonprinting characters such as passwords are in angle brackets.< >

Default responses to system prompts are in square brackets.[ ]

An exclamation point (!) or a pound sign (#) at the beginning of a line of codeindicates a comment line.

!, #

Means reader take note. Notes contain helpful suggestions or references to material not covered in thedocument.

Note

Means the following information will help you solve a problem. The tips information might not betroubleshooting or even an action, but could be useful information, similar to a Timesaver.

Tip

Means reader be careful. In this situation, you might perform an action that could result in equipmentdamage or loss of data.

Caution

Means the described action saves time. You can save time by performing the action described in theparagraph.

Timesaver

Cisco UCS B-Series Blade Servers Windows Installation Guidevi OL-22764-04

PrefaceConventions

IMPORTANT SAFETY INSTRUCTIONS

This warning symbol means danger. You are in a situation that could cause bodily injury. Before youwork on any equipment, be aware of the hazards involved with electrical circuitry and be familiar withstandard practices for preventing accidents. Use the statement number provided at the end of each warningto locate its translation in the translated safety warnings that accompanied this device.

SAVE THESE INSTRUCTIONS

Warning

Related Cisco UCS DocumentationDocumentation Roadmaps

For a complete list of all B-Series documentation, see theCiscoUCS B-Series Servers Documentation Roadmapavailable at the following URL: http://www.cisco.com/go/unifiedcomputing/b-series-doc.

For a complete list of all C-Series documentation, see theCiscoUCSC-Series Servers Documentation Roadmapavailable at the following URL: http://www.cisco.com/go/unifiedcomputing/c-series-doc.

Other Documentation Resources

Follow Cisco UCS Docs on Twitter to receive document update notifications.

Documentation FeedbackTo provide technical feedback on this document, or to report an error or omission, please send your commentsto [email protected]. We appreciate your feedback.

Cisco UCS B-Series Blade Servers Windows Installation Guide OL-22764-04 vii

PrefaceRelated Cisco UCS Documentation

http://www.cisco.com/go/unifiedcomputing/b-series-doc

http://www.cisco.com/go/unifiedcomputing/c-series-doc

http://twitter.com/ciscoucsdocs

mailto:[email protected]

Cisco UCS B-Series Blade Servers Windows Installation Guideviii OL-22764-04

PrefaceDocumentation Feedback

C H A P T E R 1Installation Checklists and Prerequisites

This chapter includes the following sections:

• Installation Overview Checklist, page 1

• Installation Prerequisites Checklist, page 2

• Service Profile Configuration Prerequisites, page 3

• SAN Boot Topology Example, page 6

• Mounting the Installation ISO Image, page 6

Installation Overview ChecklistComplete the following tasks to install an operating system (OS) on your Cisco UCS B-Series server.

Additional InformationTaskCompleted?

For more information about installation orlicensing requirements, see the documentationfor the operating system you are going to install.

Complete the prerequisites described inInstallation Prerequisites Checklist, onpage 2.

For more information about service profiles, seethe GUI or CLI configuration guide for theversion of Cisco UCS Manager that you areusing.

Complete the service profile configurationprerequisites described in Service ProfileConfiguration Prerequisites, on page 3.

For details, see Mounting the Installation ISOImage, on page 6.

Launch theKVMConsole and mount theinstallation media.

Cisco UCS B-Series Blade Servers Windows Installation Guide OL-22764-04 1

Additional InformationTaskCompleted?

For details, see one of the following:

• Installing Windows Server 2003 on anInternal Drive, on page 9

• Installing Windows Server 2003 on aBootable SAN LUN, on page 11

• Installing Windows Server 2012 andWindows Server 2008 on an InternalDrive, on page 13

• Installing Windows Server 2012 andWindows Server 2008 on a Bootable SANLUN, on page 15

Complete the installation as described inthe procedure for your OS.

Installation Prerequisites ChecklistBefore you begin installing the operating system (OS), make sure that you have the following items or havecompleted the following tasks:

PrerequisiteCompleted?

Make sure the installation-target server supports the version of the operating system (OS)you plan to install.

For the supported versions, see the appropriate PDF or use the interactive UCS Hardwareand Software Interoperability Utility. Both are available at the following URL: http://www.cisco.com/web/techdoc/ucs/interoperability/matrix/matrix.html.

The interoperability information for a particular release is dependent on third-partycertification testing done after the release has been made public. Therefore, theinteroperability information may not be available until several months after therelease becomes publically available.

Note

Make sure you have a configured IP address for Cisco UCS Manager GUI, as well as alogin account with administration privileges.

Make sure you have the installation media for the OS, either on a DVD or as an ISO image.If the software requires an activation key, make sure you have that information as well.

We recommend that you install the OS from an ISO image that you map as a virtualdevice.

You can also install from a physical disk, but that method requires that you attachan external USB CD/DVD drive to the blade on which you want to install the OSusing a KVM cable with a USB connector. For details, see theHardware InstallationGuide for the blade server that you are using. All hardware installation guides areavailable at the following URL: http://www.cisco.com/en/US/products/ps10477/prod_installation_guides_list.html

Tip

Cisco UCS B-Series Blade Servers Windows Installation Guide2 OL-22764-04

Installation Checklists and PrerequisitesInstallation Prerequisites Checklist

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

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

http://www.cisco.com/en/US/products/ps10477/prod_installation_guides_list.html

http://www.cisco.com/en/US/products/ps10477/prod_installation_guides_list.html

PrerequisiteCompleted?

Make sure you have the Cisco UCS B-Series Drivers DVD or the ISO image of this DVD.If the operating system is to be installed on a drive that is available through iSCSI, you mustchoose the network folder to load the eNIC driver during the installation process becauseiSCSI is available through the Ethernet portion of the VIC.

The Cisco UCS B-Series Drivers DVD ISO image is available from the Cisco.com supportsite under Downloads > Servers - Unified Computing > Cisco UCS B-Series BladeServer Software >Unified Computing System (UCS) Drivers . The direct URL is: http://www.cisco.com/cisco/software/type.html?mdfid=283853163&flowid=25821.

If you download the ISO image, you need to burn the image to a DVD or use athird-party utility to mount the image on a laptop hard drive.

During the installation, you will need to extract the appropriate driver image filefrom this DVD to a location accessible to the server so that it can be mounted asa virtual floppy.

Note

If your server has an LSI MegaRAID controller, configure RAID settings for the drives inyour server. If you do not configure your LSI MegaRAID LUNs before installing the OS,disk discovery failures might occur during the installation and you may see error messagessuch as “No Device Found.”

After you complete these prerequisites, make sure you have a properly-configured service profile availableto associate with the server. For details, see Service Profile Configuration Prerequisites, on page 3.

Service Profile Configuration PrerequisitesRegardless of which version of the OS you install, the installation-target server must be associated with aproperly configured service profile. The service profile contains all of the information and settings that areapplied to the server.

The following checklist provides the minimum configuration settings required in the service profile. Fordetailed instructions about configuring these settings, see the Configuration Guide for the version of CiscoUCS Manager that you are using. The configuration guides are available at the following URL: http://www.cisco.com/en/US/products/ps10281/products_installation_and_configuration_guides_list.html

Additional InformationConfiguration TaskCompleted?

Cisco UCS allows you to define pools forservers, MAC addresses, WWN addresses,UUID suffixes, and management IP addresses.

Use Cisco UCS Manager to configurepools that identify the physical and logicalresources on your network. You selectfrom these pools as you build the serviceprofile for the server.

A named VSAN creates a connection to aspecific external SAN fabric.

Configure one named VSAN for eachuplink fabric to which the target server isnetworked.


Installation Checklists and PrerequisitesService Profile Configuration Prerequisites

http://www.cisco.com/cisco/software/type.html?mdfid=283853163&flowid=25821


http://www.cisco.com/en/US/products/ps10281/products_installation_and_configuration_guides_list.html



For example, associate the VSAN that youcreated for Fabric A with an available physicalport on Fabric Interconnect A.

Associate each VSAN with a physicaluplink port on its corresponding fabricinterconnect.

This vHBA policy defines how the vHBAconnects to the SAN.

Create one vHBA policy for each uplinkfabric to which the target server isnetworked.

If you do not configure your LSI MegaRAIDLUNs before installing the OS, disk discoveryfailures might occur during the installation andyoumay see error messages such as “NoDeviceFound.”

If your server has an LSI MegaRAIDcontroller, configure RAID settings for thedrives in your system by creating a LocalDisk Configuration policy.

If you are installing the OS on an internal drive,define the following Boot Order:

1 CD-ROM

2 Floppy (for Windows 2003 only)

3 Local Disk

If you are installing the OS in a bootable SANLUN, define the following Boot Order:

1 CD-ROM

2 Floppy (for Windows 2003 only)

3 Storage

• SAN Primary

• SAN Secondary

Create a boot policy for the type ofinstallation you are preforming.

If you only associate one vNIC policy with theservice profile, Windows assigns ahardware-based MAC address to the secondNIC.

If you later move the service profile to adifferent server, the hardware-based MACaddress will not move with that profile, and anyprograms that link to the MAC address will notbe able to locate the proper server.

If your server has two network interfacecards (NICs), such as the Cisco UCSCNAM71KR-E, youmust create separate vNICpolicies for each card in order to getuser-defined MAC addresses for bothNICs.

A complete list of the available policies isincluded in the Cisco UCS ManagerConfiguration Guides.

Configure any other policies that yourequire to manage the server.




If you plan to install the same OS on multipleservers, you can also create a service profiletemplate and associate that template with theconfiguration settings you created.

You can then use that template to create aunique service profile for each target server.

Create a new service profile or modify anexisting service profile for the target bladeserver. Make sure this service profile isassociated the network settings andpolicies that you created for the targetserver.

When the target server is rebooted, the settingsin the service profile are assigned to it.

You cannot mount an ISOinstallation or driver image untilafter the server has finishedrebooting and Cisco UCSManagerhas successfully associated theservice profile with the server.

Important

Associate the service profile with the targetserver and reboot the server.



SAN Boot Topology ExampleThe following example shows the topology of a Cisco UCS domain that uses the SAN boot feature.

Figure 1: SAN Boot Topology

Mounting the Installation ISO ImageBefore You Begin

• Make sure you have completed the prerequisites described in Installation Prerequisites Checklist, onpage 2 and Service Profile Configuration Prerequisites, on page 3.

• Make sure you have a Cisco UCS username and password.

• Make sure you know the name of the service profile or the server on which you want to install theoperating system (OS).

• Make sure that the server is associated with a service profile. For details, see the Configuration Guidefor the version of Cisco UCS Manager that you are using. The configuration guides are available at thefollowingURL: http://www.cisco.com/en/US/products/ps10281/products_installation_and_configuration_guides_list.html

You cannot mount an ISO image on the server until it is associated with a service profile.


Installation Checklists and PrerequisitesSAN Boot Topology Example



Procedure

Step 1 In your web browser, type or select the web link for Cisco UCS Manager GUI.

Example:The default web link for HTTP access is http://UCSManager_IP for an IPv4 address, orhttp://UCSManager_IP6 for an IPv6 address. The default web link for HTTPS access ishttps://UCSManager_IP for an IPv4 address, or https://UCSManager_IP6 for an IPv6 address.In a standalone configuration, UCSManager_IP or UCSManager_IP6 are the IPv4 or IPv6 addresses,respectively, for the management port on the fabric interconnect. In a cluster configuration, UCSManager_IPor UCSManager_IP6 are the IPv4 or IPv6 addresses, respectively, assigned to Cisco UCS Manager.

Step 2 On the Cisco UCS Manager launch page, click Launch KVMManager.Step 3 If a Security Alert dialog box appears, click Yes to accept the security certificate and continue.Step 4 On the UCS - KVM Launch Manager Login page, do the following:

a) Enter your Cisco UCS username and password.b) (Optional) If your Cisco UCS implementation includes multiple domains, select the appropriate domain

from the Domain drop-down list.c) Click OK.

Step 5 In the Service Profiles table of the KVM Launch Manager, do the following:a) Locate the row containing the service profile and associated server on which you want to install the OS.b) In the Launch KVM column for that server, click Launch.

The KVM console opens in a separate window.

If the Caps Lock key on your keyboard is on when you open a KVM session, and you subsequentlyturn off your Caps Lock key, the KVMConsole may continue to act as if Caps Lock is turned on.To synchronize the KVM Console and your keyboard, press Caps Lock once without the KVMConsole in focus and then press Caps Lock again with the KVM Console in focus.

Tip

Step 6 How you access virtual media depends on the version of theKVMConsole that you are using. Do one of thefollowing to access virtual media:

• Click the Virtual Media tab.

• Click the VM tab.

• Select Tools > Virtual Media.

Step 7 Click Add Image and navigate to the directory containing the installation ISO image.Step 8 Select the ISO image file and click Open.Step 9 In the Client View area, check the check box in theMapped column associated with the ISO file, then wait

for mapping to complete.Click Details to see the mappingprogress.

Tip

What to Do Next

Install the OS as described in the installation procedure that matches the OS you are installing.


Installation Checklists and PrerequisitesMounting the Installation ISO Image


Installation Checklists and PrerequisitesMounting the Installation ISO Image

C H A P T E R 2Windows Server 2003 Installation


• Installing Windows Server 2003 on an Internal Drive, page 9

• Installing Windows Server 2003 on a Bootable SAN LUN, page 11

Installing Windows Server 2003 on an Internal DriveThis section describes how to install Windows Server 2003 with Service Pack 2 (SP2) x86 or x64 on aninternal drive using Cisco UCS Manager GUI and the KVM Console.

Other versions of Windows Server 2003 are not supported.

Before You Begin

Make sure you have completed the prerequisites described in Installation Prerequisites Checklist, on page2 and Service Profile Configuration Prerequisites, on page 3.

Procedure

Step 1 Find the drivers for your installed devices on the Cisco UCS B-Series Drivers DVD or in the DVD ISO fileand extract them to a location that the server can access.

If you do not know which drivers are required, reboot the server and read the output messages. As thedevices are initialized, the boot process displays information about them. For more information, seeInstallation Driver Information, on page 17.

Tip

Step 2 If you are installing the OS or drivers from virtual media, launch the KVM Console and mount the media asdescribed in Mounting the Installation ISO Image, on page 6.

Step 3 Mount the driver IMG image file for your mass storage controller or SAN HBA device:a) Click Add Image and navigate to the directory containing the driver IMG image file for your device and

operating system.b) Select the IMG image file and click Open.c) When prompted whether you want to emulate the device as a floppy, click Yes.


d) In the Client View area, check the check box in theMapped column associated with the IMG virtualfloppy, then wait for mapping to complete.

Step 4 Power cycle the server using one of the following methods:

• In the KVM Console, go to the KVM tab and selectMacros > Ctrl-Alt-Del.

• In Cisco UCS Manager GUI, click Reset in the Actions area of the General tab.

• On the physical server, press the Power button.

If the server does not boot from the installation media, verify that the correct boot order is set in theassociated service profile as described in Service Profile Configuration Prerequisites, on page 3.

Tip

Step 5 To override the normal boot order and boot from the installationmedia, in theKVM tab of theKVMConsole,watch the boot messages and press F6 when prompted to enter the Boot Menu.

Step 6 On the Boot Menu screen, do one of the following:

• If you are using an ISO image, select Cisco Virtual CD/DVD and press Enter.

• If you are using a physical install disk, select the disk drive in which that disk resides and press Enter.

The server reboots from the selected device and begins installing the OS from the image or disk.

Step 7 Press Enter when prompted to boot from CD. Watch carefully for the Press F6 to installthird-party drivers prompt that is displayed early in the installation process at the bottom of thewindow.

Do not install the Windows 2003 OS or drivers on any drive listed as “Viking eUSB”. While theOS considers the eUSB drives to be the same as a local drive, Cisco UCS Manager does not letyou specify which local drive the server should use as the boot drive. Instead, it always bootsthe server from the physical local drive and ignores any internal USB (eUSB) drives.

Important

Step 8 Install the mass storage controller or HBA device drivers from the virtual floppy:a) Press F6 when prompted to install third-party drivers. Continue to watch the installation process until you

are prompted to specify an additional device.b) Press S when prompted to specify an additional device.c) Select your device from the list and press Enter.

The drivers are installed from the virtual floppy.

Step 9 Complete the installation according to the requirements and standards of your company by continuing tomonitor the installation progress and answering prompts as required.After the Windows installation is complete, Windows reboots the server again and you are prompted to pressCtrl-Alt-Del and log in to access the Windows desktop. Use the login credentials that you supplied during theWindows installation process.

At this point, Windows still needs device drivers installed for devices such as the server chipset andEthernet controllers. In theWindows Device Manager, devices that still need drivers are markedwith yellow flags.

Note

Step 10 UseWindows File Manager to navigate to the folder into which you extracted the Cisco drivers in Step 1.For details about the driver DVD folder structure, see Windows Installation Drivers, on page 17.

Step 11 Launch theWindows Device Manager and look for any devices that still have yellow flags. For each suchdevice, install the driver manually through the Device Manager.


Windows Server 2003 InstallationInstalling Windows Server 2003 on an Internal Drive

Installing Windows Server 2003 on a Bootable SAN LUNThis procedure describes how to install Windows Server 2003 with Service Pack 2 (SP2) x86 or x64 on abootable SAN LUN using Cisco UCS Manager GUI and the KVM Console.

Before You Begin


• Configure a LUN or RAID volume on your SAN, then connect to the SAN and verify that one (and onlyone) path exists from the SAN HBA to the LUN.

Procedure



Tip


Step 3 Mount the driver IMG image file for your mass storage controller or SAN HBA device:a) Click Add Image and navigate to the directory containing the driver IMG image file for your device and

operating system.b) Select the IMG image file and click Open.c) When prompted whether you want to emulate the device as a floppy, click Yes.d) In the Client View area, check the check box in theMapped column associated with the IMG virtual

floppy, then wait for mapping to complete.






Tip






Windows Server 2003 InstallationInstalling Windows Server 2003 on a Bootable SAN LUN


Step 7 Press Enter when prompted to boot from CD. Watch carefully for the Press F6 to installthird-party drivers prompt that is displayed early in the installation process at the bottom of thewindow.

Do not install the Windows 2003 OS or drivers on any drive listed as “Viking eUSB”. While theOS considers the eUSB drives to be the same as a local drive, Cisco UCS Manager does not letyou specify which local drive the server should use as the boot drive. Instead, it always bootsthe server from the physical local drive and ignores any internal USB (eUSB) drives.

Important

Step 8 Install the mass storage controller or HBA device drivers from the virtual floppy:a) Press F6 when prompted to install third-party drivers. Continue to watch the installation process until you

are prompted to specify an additional device.b) Press S when prompted to specify an additional device.c) Select your device from the list and press Enter.

The drivers are installed from the virtual floppy.



Note




Windows Server 2003 InstallationInstalling Windows Server 2003 on a Bootable SAN LUN

C H A P T E R 3Windows Server 2012 and Windows Server 2008Installation


• Installing Windows Server 2012 and Windows Server 2008 on an Internal Drive, page 13

• Installing Windows Server 2012 and Windows Server 2008 on a Bootable SAN LUN, page 15

Installing Windows Server 2012 and Windows Server 2008 onan Internal Drive

This procedure describes how to installWindows Server 2012,Windows Server 2008 x64, orWindows Server2008 R2 x64 and required drivers on an internal drive using Cisco UCSManager GUI and theKVMConsole.

Before You Begin

Make sure you have completed the prerequisites described in Installation Prerequisites Checklist, on page2 and Service Profile Configuration Prerequisites, on page 3.

Procedure



Tip








Tip






Step 6 Press Enter when prompted to boot from CD. Answer the installation questions according to the requirementsand standards of your company until theWhere do you want to install Windows? screen displays, then goto the next step.

Do not install the Windows OS or drivers on any drive listed as “Viking eUSB”. While the OSconsiders the eUSB drives to be the same as a local drive, Cisco UCS Manager does not let youspecify which local drive the server should use as the boot drive. Instead, it always boots theserver from the physical local drive and ignores any internal USB (eUSB) drives.

Important

Step 7 When Windows displays theWhere do you want to install Windows? screen, mount the Cisco driver ISOimage so that you can install the basic drivers before you install Windows. To do so:a) Return to the VM tab or Virtual Media Session dialog box in the KVM Console.b) Because you can only have one virtual CD/DVD mapped at a time, unmap any existing virtual CD/DVD

connections by clearing the check box associated with that connection.To verify that you can create a new connection, look at theDetails table. The first line should showthat the Virtual CD/DVD is not mapped.

Tip

c) ClickAdd Image and navigate to the directory containing the Cisco driver ISO image for you mass storageor HBA device.

d) Select the ISO image file and click Open.e) In the Client View area, check the check box in theMapped column associated with the ISO file, then

wait for mapping to complete.f) Return to the Windows installation prompt in the KVM tab.

Step 8 Install the drivers:a) In theWhere do you want to install Windows? screen, click the Load Driver link below the table.b) In the Load Driver dialog box, click Browse.c) Navigate to the appropriate folder on the virtual DVD device that you just mapped and select the drivers

you want to install.d) Click OK.

When Windows has finished loading the drivers, it displays the Select the driver to install dialog boxwith the new drivers listed.

e) Select the driver for your device and clickNext. Wait until the driver installation is complete, as indicatedby the Windows status bar.

Step 9 (Optional) If you are installing Windows from an ISO image file, unmap the driver ISO image and remapthe Windows installation image:a) Return to the VM tab or Virtual Media Session dialog box in the KVM Console.


Windows Server 2012 and Windows Server 2008 InstallationInstalling Windows Server 2012 and Windows Server 2008 on an Internal Drive

b) In the Client View area, clear the check box in theMapped column that corresponds to the driver ISOfile.

c) Check the check box in theMapped column that corresponds to your Windows installation image, thenwait for mapping to complete.

d) Return to the Windows installation prompt in the KVM tab.e) (Optional) If the installation procedure displays an error stating that it cannot continue because it cannot

find the installation disk, clickRefresh at the bottom of the screen to have the installation procedure refreshthe connection with the installation ISO image.

Step 10 In theWhere do you want to install Windows? screen, select the disk or partition in which you want toinstall Windows and click Next.



Note



Installing Windows Server 2012 and Windows Server 2008 ona Bootable SAN LUN

This section describes how to install Windows Server 2012, Windows Server 2008 x64, or Windows Server2008 R2 x64 and required drivers on a bootable SAN LUN using Cisco UCS Manager GUI and the KVMConsole.

Before You Begin


• Configure a LUN or RAID volume on your SAN, then connect to the SAN and verify that one (and onlyone) path exists from the SAN HBA to the LUN.

Procedure



Windows Server 2012 and Windows Server 2008 InstallationInstalling Windows Server 2012 and Windows Server 2008 on a Bootable SAN LUN


Tip







Tip






Step 6 Press Enter when prompted to boot from CD. Answer the installation questions according to the requirementsand standards of your company until theWhere do you want to install Windows? screen displays, then goto the next step.

Do not install the Windows OS or drivers on any drive listed as “Viking eUSB”. While the OSconsiders the eUSB drives to be the same as a local drive, Cisco UCS Manager does not let youspecify which local drive the server should use as the boot drive. Instead, it always boots theserver from the physical local drive and ignores any internal USB (eUSB) drives.

Important



Note




Windows Server 2012 and Windows Server 2008 InstallationInstalling Windows Server 2012 and Windows Server 2008 on a Bootable SAN LUN

A P P E N D I X AInstallation Driver Information

This appendix includes the following sections:

• Windows Installation Drivers, page 17

• Viewing Installed Devices, page 18

Windows Installation DriversThe required installation drivers and detailed driver information is available on theCisco UCS B-Series DriversDVD.

The Cisco UCS B-Series Drivers DVD ISO image is available from the Cisco.com support site underDownloads > Servers - Unified Computing > Cisco UCS B-Series Blade Server Software > UnifiedComputing System (UCS) Drivers . The direct URL is: http://www.cisco.com/cisco/software/type.html?mdfid=283853163&flowid=25821.

Note

The drivers are organized into top-level folders by operating system, and each operating system folder has ahierarchically structured series of subfolders that become increasing specific so that you can find the exactdrivers you need.When you navigate to a folder that contains drivers, it will also contain one or more READMEfiles that describes what those particular drivers are used for.

An example of the folder structure for Windows follows:Windows

ChipSetvendor

blade-model-numberOS-version-number

Allia64Lang (contains language subfolders)Vistax64

MgmtEmulex

model-numberElxPlus

OS-version-numberx64

Network




vendormodel-number


SecurityTPM


Storagevendor

model-numberOS-version-number

x64Video

MatroxG200e


For example, the Windows Server 2008 Release 2 drivers for the Cisco UCS M81KR Virtual Interface Cardcan be found in the folder Windows/Network/Cisco/M81KR/W2K8R2/x64.

Viewing Installed Devices

Viewing Installed Devices Using the UCS Manager GUI

Procedure

Step 1 In the Navigation pane, click the Equipment tab.Step 2 On the Equipment tab, expand Equipment > Chassis > Chassis Number > Servers > Server Number >

Adapter.Step 3 Look at the Adapters tab in theWork pane.

All adapters installed in the selected server are displayed in the table.

Viewing Installed Interface Cards Using the UCS Manager CLI

Procedure

Step 1 Use Telnet or SSH to connect to the UCS system.Step 2 UCS-A# scope server chassis-id / server-id

Enters chassis server mode for the specified server in the specified chassis.

Step 3 UCS-A /chassis/server # show adapterDisplays the list of interface cards installed in the server by their PID number.


Installation Driver InformationViewing Installed Devices

switch-A # scope chassis-2 server10switch-A /chassis-2 # show adapter

Server 1/1:Adapter PID Vendor Serial Operational State------- ---------- ----------------- ------------ -----------------1 N20-AE0002 Cisco Systems Inc EXM12510017 Operable2 N20-AE0003 Cisco Systems Inc EXM12510018 Operable

switch-A /server-qual #

Viewing Installed Devices Using the KVM Console

Procedure

Step 1 In your web browser, type or select the web link for Cisco UCS Manager GUI.

Example:The default web link for HTTP access is http://UCSManager_IP for an IPv4 address, orhttp://UCSManager_IP6 for an IPv6 address. The default web link for HTTPS access ishttps://UCSManager_IP for an IPv4 address, or https://UCSManager_IP6 for an IPv6 address.In a standalone configuration, UCSManager_IP or UCSManager_IP6 are the IPv4 or IPv6 addresses,respectively, for the management port on the fabric interconnect. In a cluster configuration, UCSManager_IPor UCSManager_IP6 are the IPv4 or IPv6 addresses, respectively, assigned to Cisco UCS Manager.

Step 2 On the Cisco UCS Manager launch page, click Launch KVMManager.Step 3 If a Security Alert dialog box appears, click Yes to accept the security certificate and continue.Step 4 On the UCS - KVM Launch Manager Login page, do the following:

a) Enter your Cisco UCS username and password.b) (Optional) If your Cisco UCS implementation includes multiple domains, select the appropriate domain

from the Domain drop-down list.c) Click OK.

Step 5 In the Service Profiles table of the KVM Launch Manager, do the following:a) Locate the row containing the service profile and associated server on which you want to view the installed

devices.b) In the Launch KVM column for that server, click Launch.

The KVM console opens in a separate window.

If the Caps Lock key on your keyboard is on when you open a KVM session, and you subsequentlyturn off your Caps Lock key, the KVMConsole may continue to act as if Caps Lock is turned on.To synchronize the KVM Console and your keyboard, press Caps Lock once without the KVMConsole in focus and then press Caps Lock again with the KVM Console in focus.

Tip

Step 6 Reboot the server and observe the information about the installed devices on the console screen during bootup.


Installation Driver InformationViewing Installed Devices Using the KVM Console


Installation Driver InformationViewing Installed Devices Using the KVM Console

Documents

Cisco UCS B-Series Blade Servers Windows Installation Guide...Cisco UCS B-Series Blade Servers Windows Installation Guide First Published: April22,2011Last Modified: March20,2015Americas