The interoperability information for a particular release is dependent on third-party certification testing done after the release has been made public. Therefore, the interoperability information may not be available until several months after the release becomes publically available.
Make sure you have a configured IP address for Cisco UCS Manager GUI, as well as a login 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 virtual device.
You can also install from a physical disk, but that method requires that you attach an external USB CD/DVD drive to the blade on which you want to install the OS using a KVM cable with a USB connector. For details, see the Hardware Installation Guide for the blade server that you are using. All hardware installation guides are available at the following URL: http://www.cisco.com/en/US/products/ps10477/prod_installation_guides_list.html
If your server has an LSI MegaRAID controller, configure RAID settings for the drives in your 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 messages such as “No Device Found.”
Regardless of which version of the OS you install, the installation-target server must be associated with a properly configured service profile. The service profile contains all of the information and settings that are applied to the server.
Use Cisco UCS Manager to configure pools that identify the physical and logical resources on your network. You select from these pools as you build the service profile for the server.
Cisco UCS allows you to define pools for servers, MAC addresses, WWN addresses, UUID suffixes, and management IP addresses.
Configure one named VSAN for each uplink fabric to which the target server is networked.
A named VSAN creates a connection to a specific external SAN fabric.
Associate each VSAN with a physical uplink port on its corresponding fabric interconnect.
For example, associate the VSAN that you created for Fabric A with an available physical port on Fabric Interconnect A.
Create one vHBA policy for each uplink fabric to which the target server is networked.
This vHBA policy defines how the vHBA connects to the SAN.
If your server has an LSI MegaRAID controller, configure RAID settings for the drives in your system by creating a Local Disk Configuration policy.
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 messages such as “No Device Found.”
Create a boot policy for the type of installation you are preforming.
If you are installing the OS on an internal drive, define the following Boot Order:
If you are installing the OS in a bootable SAN LUN, define the following Boot Order:
Configure any other policies that you require to manage the server.
A complete list of the available policies is included in the Cisco UCS Manager Configuration Guides.
Create a new service profile or modify an existing service profile for the target blade server. Make sure this service profile is associated the network settings and policies that you created for the target server.
If you plan to install the same OS on multiple servers, you can also create a service profile template and associate that template with the configuration settings you created.
You can then use that template to create a unique service profile for each target server.
Associate the service profile with the target server and reboot the server.
When the target server is rebooted, the settings in the service profile are assigned to it.
You cannot mount an ISO installation or driver image until after the server has finished rebooting and Cisco UCS Manager has successfully associated the service profile with the server.
SAN Boot Topology Example
The following example shows the topology of a Cisco UCS domain that uses the SAN boot feature.
In your web browser, type or select the web link for Cisco UCS Manager GUI.
The default web link is http://UCSManager_IP or https://UCSManager_IP. In a standalone configuration, UCSManager_IP is the IP address for the management port on the fabric interconnect. In a cluster configuration, UCSManager_IP is the IP address assigned to Cisco UCS Manager.
On the Cisco UCS Manager launch page, click Launch KVM Manager.
If a Security Alert dialog box appears, click Yes to accept the security certificate and continue.
On the UCS - KVM Launch Manager Login page, do the following:
Enter your Cisco UCS username and password.
Optional: If your Cisco UCS implementation includes multiple domains, select the appropriate domain from the Domain drop-down list.
In the Service Profiles table of the KVM Launch Manager, do the following:
Locate the row containing the service profile and associated server on which you want to install the OS.
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 subsequently turn off your Caps Lock key, the KVM console 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 KVM console in focus and then press Caps Lock again with the KVM console in focus.
How you access virtual media depends on the version of the KVM Console that you are using. Do one of the following to access virtual media:
Click the Virtual Media tab.
Click the VM tab.
Select Tools > Virtual Media.
Click Add Image and navigate to the directory containing the installation ISO image.
Select the ISO image file and click Open.
In the Client View area, check the check box in the Mapped column associated with the ISO file, then wait for mapping to complete.
Click Details to see the mapping progress.
What to Do Next
Install the OS as described in the installation procedure that matches the OS you are installing.