The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter includes the following sections:
The following three main components must be connected for VN-Link in hardware to work:
A server with the VMware ESX installed. It contains a datastore and the virtual machines.
The ESX host must have a Cisco UCS M81KR Virtual Interface Card installed, and it must have uplink data connectivity to the network for communication with VMware vCenter.
Windows-based software used to manage one or more ESX hosts.
VMware vCenter must have connectivity to the UCS management port for management plane integration, and uplink data connectivity to the network for communication with the ESX Host. A vCenter extension key provided by Cisco UCS Manager must be registered with VMware vCenter before the Cisco UCS instance can be acknowledged.
The Cisco UCS management software that integrates with VMware vCenter to handle some of the network-based management tasks.
Cisco UCS Manager must have management port connectivity to VMware vCenter for management plane integration. It also provides a vCenter extension key that represents the Cisco UCS identity. The extension key must be registered with VMware vCenter before the Cisco UCS instance can be acknowledged.
The following figure shows the three main components of VN-Link in hardware and the methods by which they are connected:
Ensure that Virtualization Technology is enabled in BIOS of the UCS server if you intend to run 64-bit VMs on the ESX host. An ESX host will not run 64-bit VMs unless Virtualization Technology is enabled.
Step 1 | If not already present, install a Cisco UCS M81KR Virtual Interface Card in the server you intend to use as the VMware ESX host. For more information about installing a Cisco UCS M81KR Virtual Interface Card, see the Cisco UCS 5108 Server Chassis Hardware Installation Guide. |
Step 2 |
Configure and associate a service profile to the server. The service profile configuration must include the following:
For more information, see the following chapter: Configuring Service Profiles. |
Step 3 | Install VMware ESX 4.0 or later on the blade server. No additional drivers are required during the installation. |
Do one of the following:
Configuring a Certificate for VN-Link in Hardware
Cisco UCS Manager generates a default, self-signed SSL certificate to support communication with vCenter. You can also create your own custom certificate to communicate with multiple vCenter instances. When you create a custom certificate, Cisco UCS Manager recreates the extension files to include the new certificate. If you subsequently delete the custom certificate, Cisco UCS Manager recreates the extension files to include the default, self-signed SSL certificate.
To create a custom certificate, you must obtain and copy an external certificate into Cisco UCS, and then create a certificate for VN-Link in hardware that uses the certificate you copied into Cisco UCS.
The following example uses FTP to copy a certificate (certificate.txt) to the temp folder in the workspace:
UCS-A # connect local-mgmt Cisco UCS 6100 Series Fabric Interconnect TAC support: http://www.cisco.com/tac Copyright (c) 2009, Cisco Systems, Inc. All rights reserved. The copyrights to certain works contained herein are owned by other third parties and are used and distributed under license. Some parts of this software may be covered under the GNU Public License or the GNU Lesser General Public License. A copy of each such license is available at http://www.gnu.org/licenses/gpl.html and http://www.gnu.org/licenses/lgpl.html UCS-A(local-mgmt)# copy ftp://192.168.10.10/certs/certificate.txt workspace:/temp/certificate.txt UCS-A(local-mgmt)#
Create a certificate for VN-Link in hardware.
The following example creates a certificate for VN-Link in hardware, and commits the transaction:
UCS-A# scope system UCS-A /system # scope vm-mgmt UCS-A /system/vm-mgmt # scope vmware UCS-A /system/vm-mgmt/vmware # scope cert-store UCS-A /system/vm-mgmt/vmware/cert-store # create certificate VnLinkCertificate UCS-A /system/vm-mgmt/vmware/cert-store/certificate* # set location workspace path /temp certfile certificate.txt UCS-A /system/vm-mgmt/vmware/cert-store/certificate* # commit-buffer UCS-A /system/vm-mgmt/vmware/cert-store/certificate #
The following example deletes a certificate for VN-Link in hardware, and commits the transaction:
UCS-A# scope system UCS-A /system # scope vm-mgmt UCS-A /system/vm-mgmt # scope vmware UCS-A /system/vm-mgmt/vmware # scope cert-store UCS-A /system/vm-mgmt/vmware/cert-store # delete certificate VnLinkCertificate UCS-A /system/vm-mgmt/vmware/cert-store* # commit-buffer UCS-A /system/vm-mgmt/vmware/cert-store #
Connecting Cisco UCS Manager to VMware vCenter Using the Extension Key
You can modify the vCenter extension key for the following reasons:
Export the vCenter extension file or files from Cisco UCS Manager.
Depending on the version of VMware vCenter you are using, you can either generate one extension file or a set of nine extension files.
Register the vCenter extension file or files in VMware vCenter.
In VMware vCenter, the vCenter extension files are called plug-ins.
Export the vCenter extension file(s) from Cisco UCS Manager. Ensure that the exported vCenter extension files are saved to a location that can be reached by VMware vCenter.
Step 1 | In VMware vCenter, choose . |
Step 2 | Right-click any empty space below the Available Plug-ins section of the Plug-in Manager dialog box and click New Plug-in. |
Step 3 | Click Browse and navigate to the location where the vCenter extension file(s) are saved. |
Step 4 | Choose a vCenter extension file and click Open. |
Step 5 | Click Register Plug-in. |
Step 6 | If the Security Warning dialog box appears, click Ignore. |
Step 7 |
Click OK. The vCenter extension file registers as an available VMware vCenter plug-in. You do not need to install the plug-in, leave it in the available state. If you are registering multiple vCenter extension files, repeat this procedure until all files are registered. |