vmware vm-fex ucs configuration guide

80
Cisco UCS Manager VM-FEX for VMware GUI Configuration Guide First Published: September 06, 2011 Last Modified: April 23, 2013 Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387) Fax: 408 527-0883 Text Part Number: OL-25368-01

Upload: loginbullshit

Post on 24-Oct-2015

246 views

Category:

Documents


5 download

DESCRIPTION

VMware VM-FEX UCS Configuration Guide

TRANSCRIPT

Page 1: VMware VM-FEX UCS Configuration Guide

Cisco UCS Manager VM-FEX for VMware GUI Configuration GuideFirst Published: September 06, 2011

Last Modified: April 23, 2013

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-25368-01

Page 2: VMware VM-FEX UCS Configuration Guide

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 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 SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS"WITH ALL 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 used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shownfor illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and 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)

© 2013 Cisco Systems, Inc. All rights reserved.

Page 3: VMware VM-FEX UCS Configuration Guide

C O N T E N T S

P r e f a c e Preface vii

Audience vii

Conventions vii

Related Documentation ix

Obtaining Documentation and Submitting a Service Request ix

C H A P T E R 1 Introduction 1

Overview of Virtualization 1

Overview of Cisco Virtual Machine Fabric Extender 1

Virtualization with a Virtual Interface Card Adapter 2

Virtualization with Network Interface Cards and Converged Network Adapters 2

VM-FEX for VMware Components and Requirements 3

Hypervisor Host 3

Cisco UCS Manager 4

VMware vCenter 6

Modes of Operation 6

Standard Mode 7

High-Performance Mode 7

Configuring VM-FEX for VMware 8

C H A P T E R 2 Configuring a Service Profile with VM-FEX 11

Modifying the VMwarePassThrough Ethernet Adapter Policy 11

Configuring Dynamic vNIC Connection Policies 12

Dynamic vNIC Connection Policy 12

Creating a Dynamic vNIC Connection Policy 12

Changing a Dynamic vNIC Connection Policy 13

Deleting a Dynamic vNIC Connection Policy 14

Cisco UCS Manager VM-FEX for VMware GUI Configuration Guide OL-25368-01 iii

Page 4: VMware VM-FEX UCS Configuration Guide

Viewing Dynamic vNIC Properties in a VM 15

Configuring the VM Lifecycle Policy 15

VM Lifecycle Policy 15

Configuring the VM Lifecycle Policy 16

Creating a BIOS Policy for VM-FEX in High-Performance Mode 17

C H A P T E R 3 Installing the Cisco VEM Software Bundle 19

Cisco VEM Software Bundle Installation Overview 19

Cisco VEM Software Bundle Prerequisites 19

Installing or Upgrading the Cisco VEM Software Bundle Using VUM 20

Upgrading a Host to ESX or ESXi 4.0, Update 3 or to ESX or ESXi 4.1, Update 1 and the

Compatible Cisco VEM Software Bundle 21

Upgrading a Host to ESXi 5.0 and the Compatible Cisco VEM Software Bundle 23

Upgrading a Host to ESXi 5.1 and the Compatible Cisco VEM Software Bundle 24

Installing or Upgrading the Cisco VEM Software Bundle on an ESX or ESXi Host 25

Uninstalling the Cisco VEM Software Bundle 27

C H A P T E R 4 Using the Configure VMware Integration Wizard 29

Overview of the Configure VMware Integration Wizard 29

Configuring the VMware Integration with the Wizard 29

Page 1: Establishing the Connection to vCenter Server 30

Page 2: Defining a VMware vCenter Distributed Virtual Switch 31

Page 3: Defining a Port Profile 33

Page 4: Applying Port Profiles and Configuration to vCenter Server 35

C H A P T E R 5 Connecting Cisco UCS Manager to VMware vCenter 37

Connecting Using the Extension Key 37

(Optional) Modifying the vCenter Extension Key 37

Exporting a vCenter Extension File from Cisco UCS Manager 38

Registering a vCenter Extension File in VMware vCenter 39

Configuring a Certificate for VM-FEX 39

Creating a Certificate for VM-FEX 39

Copying a Certificate to the Fabric Interconnect 40

Deleting a Certificate for VM-FEX 41

Cisco UCS Manager VM-FEX for VMware GUI Configuration Guideiv OL-25368-01

Contents

Page 5: VMware VM-FEX UCS Configuration Guide

C H A P T E R 6 Configuring Distributed Virtual Switches in Cisco UCS 43

Distributed Virtual Switches 43

Overview of Creating a DVS in Cisco UCS Manager 43

Configuring a Distributed Virtual Switch 44

Managing Distributed Virtual Switches 47

Adding a Folder to an Existing vCenter 47

Adding a Datacenter to an Existing vCenter 49

Adding a Folder to a Datacenter 51

Deleting a Folder from a vCenter 53

Deleting a Datacenter 53

Deleting a Folder from a Datacenter 53

C H A P T E R 7 Configuring Port Profiles 55

Port Profiles 55

Creating a Port Profile 56

Modifying the VLANs in a Port Profile 57

Changing the Native VLAN for a Port Profile 58

Adding a VLAN to a Port Profile 58

Removing a VLAN from a Port Profile 59

Deleting a Port Profile 59

Port Profile Clients 59

Creating a Profile Client 60

Modifying a Profile Client 60

Deleting a Profile Client 61

C H A P T E R 8 Managing Pending Deletions of Distributed Virtual Switches 63

Pending Deletions of Distributed Virtual Switches 63

Viewing Pending Deletions 64

Changing the Properties of a Pending Deletion 64

Deleting a Pending Deletion 65

Cisco UCS Manager VM-FEX for VMware GUI Configuration Guide OL-25368-01 v

Contents

Page 6: VMware VM-FEX UCS Configuration Guide

Cisco UCS Manager VM-FEX for VMware GUI Configuration Guidevi OL-25368-01

Contents

Page 7: VMware VM-FEX UCS Configuration Guide

Preface

This preface includes the following sections:

• Audience, page vii

• Conventions, page vii

• Related Documentation, page ix

• Obtaining Documentation and Submitting a Service Request, page ix

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 Manager VM-FEX for VMware GUI Configuration Guide OL-25368-01 vii

Page 8: VMware VM-FEX UCS Configuration Guide

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 Manager VM-FEX for VMware GUI Configuration Guideviii OL-25368-01

PrefaceConventions

Page 9: VMware VM-FEX UCS Configuration Guide

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 DocumentationUCS Documentation 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 .

VM-FEX for VMware Documentation

The following documentation is available for Cisco Virtual Machine Fabric Extender (VM-FEX) for VMware:

• Roadmap that lists all documentation for Cisco Unified Computing System (Cisco UCS) at the followingURL: http://www.cisco.com/go/unifiedcomputing/b-series-doc

• The Unify Virtual and Physical Networking with Cisco Virtual Interface Card White Paper

• The Cisco Unified Computing System with Cisco VM-FEX and VMware VMDirectPath2 DeploymentGuide

Other Documentation Resources

An ISO file containing all B and C-Series documents is available at the following URL: http://www.cisco.com/cisco/software/type.html?mdfid=283853163&flowid=25821. From this page, click Unified ComputingSystem (UCS) Documentation Roadmap Bundle.

The ISO file is updated after every major documentation release.

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

Obtaining Documentation and Submitting a Service RequestFor information on obtaining documentation, submitting a service request, and gathering additional information,see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Ciscotechnical documentation.

Subscribe to theWhat's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feedand set content to be delivered directly to your desktop using a reader application. The RSS feeds are a freeservice and Cisco currently supports RSS version 2.0.

Cisco UCS Manager VM-FEX for VMware GUI Configuration Guide OL-25368-01 ix

PrefaceRelated Documentation

Page 10: VMware VM-FEX UCS Configuration Guide

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

Cisco UCS Manager VM-FEX for VMware GUI Configuration Guidex OL-25368-01

PrefaceObtaining Documentation and Submitting a Service Request

Page 11: VMware VM-FEX UCS Configuration Guide

C H A P T E R 1Introduction

This chapter includes the following sections:

• Overview of Virtualization, page 1

• Overview of Cisco Virtual Machine Fabric Extender, page 1

• Virtualization with a Virtual Interface Card Adapter, page 2

• Virtualization with Network Interface Cards and Converged Network Adapters, page 2

• VM-FEX for VMware Components and Requirements, page 3

• Modes of Operation, page 6

• Configuring VM-FEX for VMware, page 8

Overview of VirtualizationVirtualization allows you to create multiple Virtual Machines (VMs) to run in isolation, side by side on thesame physical machine.

Each virtual machine has its own set of virtual hardware (RAM, CPU, NIC) upon which an operating systemand fully configured applications are loaded. The operating system sees a consistent, normalized set of hardwareregardless of the actual physical hardware components.

In a virtual machine, both hardware and software are encapsulated in a single file for rapid provisioning andmoving between physical servers. You can move a virtual machine, within seconds, from one physical serverto another for zero-downtime maintenance and continuous workload consolidation.

The virtual hardware makes it possible for many servers, each running in an independent virtual machine, torun on a single physical server. The advantages of virtualization include better use of computing resources,greater server density, and seamless server migration.

Overview of Cisco Virtual Machine Fabric ExtenderA virtualized server implementation consists of one or more VMs that run as guests on a single physical server.The guest VMs are hosted and managed by a software layer called the hypervisor or virtual machine manager

Cisco UCS Manager VM-FEX for VMware GUI Configuration Guide OL-25368-01 1

Page 12: VMware VM-FEX UCS Configuration Guide

(VMM). Typically, the hypervisor presents a virtual network interface to each VM and performs Layer 2switching of traffic from a VM to other local VMs or to another interface to the external network.

Working with a Cisco virtual interface card (VIC) adapter, the Cisco Virtual Machine Fabric Extender(VM-FEX) bypasses software-based switching of VM traffic by the hypervisor for external hardware-basedswitching in the fabric interconnect. This method reduces the load on the server CPU, provides faster switching,and enables you to apply a rich set of network management features to local and remote traffic.

VM-FEX extends the IEEE 802.1Qbh port extender architecture to the VMs by providing each VM interfacewith a virtual Peripheral Component Interconnect Express (PCIe) device and a virtual port on a switch. Thissolution allows precise rate limiting and quality of service (QoS) guarantees on the VM interface.

Virtualization with a Virtual Interface Card AdapterA Cisco VIC adapter, such as the Cisco UCS M81KR Virtual Interface Card, is a converged network adapter(CNA) that is designed for both single-OS and VM-based deployments. The VIC adapter supports static ordynamic virtualized interfaces, which includes up to 128 virtual network interface cards (vNICs).

VIC adapters support VM-FEX to provide hardware-based switching of traffic to and from virtual machineinterfaces.

In a VMware environment, VM-FEX supports the standardVMware integrationwithVMware ESX hypervisorsinstalled on the server and all virtual machine management performed through the VMware vCenter.

Virtualization with Network Interface Cards and ConvergedNetwork Adapters

Network interface card (NIC) and converged network adapters support virtualized environments with thestandard VMware integrationwith ESX installed on the server and all virtual machinemanagement performedthrough the VC.

Portability of Virtual Machines

If you implement service profiles you retain the ability to easily move a server identity from one server toanother. After you image the new server, the ESX treats that server as if it were the original.

Communication between Virtual Machines on the Same Server

These adapters implement the standard communications between virtual machines on the same server. If anESX host includes multiple virtual machines, all communications must go through the virtual switch on theserver.

If the system uses the native VMware drivers, the virtual switch is out of the network administrator's domainand is not subject to any network policies. As a result, for example, QoS policies on the network are notapplied to any data packets traveling from VM1 to VM2 through the virtual switch.

If the system includes another virtual switch, such as the Nexus 1000, that virtual switch is subject to thenetwork policies configured on that switch by the network administrator.

Cisco UCS Manager VM-FEX for VMware GUI Configuration Guide2 OL-25368-01

IntroductionVirtualization with a Virtual Interface Card Adapter

Page 13: VMware VM-FEX UCS Configuration Guide

VM-FEX for VMware Components and RequirementsAt a high level, VM-FEX for VMware requires a hypervisor host, Cisco UCSManager, and VMware vCentervirtualization management software.

The following figure shows these three main components and the methods by which they are connected.

Figure 1: Component Connectivity for VM-FEX with VMware

These components must be configured correctly for VM-FEX for VMware to work.

Hypervisor HostThe hypervisor host has these requirements:

• You must install a Cisco UCS M81KR Virtual Interface Card in the server you intend to use as thehypervisor host. For more information about installing a Cisco UCSM81KR Virtual Interface Card, seethe Cisco UCS 5108 Server Chassis Hardware Installation Guide.

• You must install the correct version of VMware ESX or ESXi software on the Cisco UCSManager host.For VM-FEX in standard mode, you must install VMware ESX version 4.0, Update 1 software or laterversions. For VM-FEX in standard mode and high-performance mode, you must install VMware ESXi

Cisco UCS Manager VM-FEX for VMware GUI Configuration Guide OL-25368-01 3

IntroductionVM-FEX for VMware Components and Requirements

Page 14: VMware VM-FEX UCS Configuration Guide

5.0 software or later versions. For information about upgrading these VMware software versions, seeUpgrading a Host to ESX or ESXi 4.0, Update 3 or to ESX or ESXi 4.1, Update 1 and the CompatibleCisco VEM Software Bundle, on page 21 or Upgrading a Host to ESXi 5.0 and the Compatible CiscoVEM Software Bundle, on page 23.

• You must obtain the Cisco VEM software bundle from the Cisco Download Software page:

◦For B-Series from, http://software.cisco.com/download/navigator.html. Select Downloads Home> Products > Servers - Unified Computing > Cisco UCS B-Series Blade Server Software andclick Unified Computing Systems (UCS) Drivers. From this page, click Latest Releases or AllReleases to select the release you want, and click Download to download the ISO image ofUCS-related drivers.

◦For C-Series from, http://software.cisco.com/download/navigator.html. Select Downloads Home> Products > Servers - Unified Computing >Cisco UCSC-Series Rack-Mount UCS-ManagedServer Software and click Unified Computing Systems (UCS) Drivers. From this page, clickLatest Releases or All Releases to select the release you want, and click Download to downloadthe ISO image of UCS-related drivers.

• You must install the correct version of the Cisco VEM software bundle on the hypervisor host. TheCisco VEM software bundle that you install depends on the VMware ESX or ESXi version you haveinstalled on the hypervisor host. For information about the compatible versions of VMware ESX softwareand Cisco VEM software bundles, see VM-FEX Software Interoperability Matrix in Hardware andSoftware Interoperability Matrix for B Series Servers at http://www.cisco.com/en/US/products/ps10477/prod_technical_reference_list.html.

The VEM software bundle is also a component of another product: the Cisco Nexus1000V switch. Do not be concerned if you see references to this product during theinstallation of the VEM bundle. This reference is cosmetic only and does not affect theoutcome of the installation and implementation of VM-FEX.

Note

Cisco UCS Manager

VM-FEX for VMware-Related Policies

You must modify or create several policies in order for VM-FEX for VMware to function optimally:

• VMwarePassThrough Ethernet Adapter Policy (high-performance mode only)

• Dynamic vNIC Connection Policies

• BIOS Policy (high-performance mode only)

• VM Lifecycle Policy

Extension File for Communicating with VMware vCenter

For Cisco UCS domains that use VIC adapters to implement VM-FEX, youmust create and install an extensionfile to establish the relationship and communications between Cisco UCS Manager and VMware vCenter.

Cisco UCS Manager VM-FEX for VMware GUI Configuration Guide4 OL-25368-01

IntroductionCisco UCS Manager

Page 15: VMware VM-FEX UCS Configuration Guide

This extension file is an XML file that contains an extension key and public secure sockets layer (SSL)certificate.

You cannot change an extension key that is being used by a DVS or an external virtualization manager.If you want to use a custom extension key, we recommend that you create and register the custom keybefore you create the DVS in Cisco UCSManager to avoid any possibility of having to delete and recreatethe associated DVS.

Important

Extension Key

Cisco UCS andVMware vCenter must be connected for management integration and network communicationwith the host. To accomplish this connectivity, Cisco UCS provides an extension key that represents the CiscoUCS identity. The extension key must be registered with the external virtualization manager before the CiscoUCS domain can be acknowledged and management and network connectivity can be established.

SSL Certificate

Cisco UCSManager generates a default, self-signed SSL certificate to support communication with a VMwarevCenter. You can also create your own custom certificate to communicate with multiple VMware vCenters.When you create a custom certificate, Cisco UCS Manager recreates the extension files to include the newcertificate. If you subsequently delete the custom certificate, Cisco UCSManager recreates the extension filesto 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 createa certificate for VM-FEX that uses the certificate you copied into Cisco UCS.

Distributed Virtual Switches (DVSes)

The Cisco UCS distributed virtual switch (DVS) is a software-based virtual switch that runs along side thevSwitch in the ESX hypervisor and can be distributed across multiple ESX hosts. Unlike the vSwitch, whichuses its own local port configuration, a DVS that is associated with multiple ESX hosts uses the same portconfiguration across all ESX hosts.

After associating an ESX host to a DVS, you can migrate existing VMs from the vSwitch to the DVS, andyou can create VMs to use the DVS instead of the vSwitch. With the VM-FEX for VMware implementation,when a VM uses the DVS, all VM traffic passes through the DVS and ASIC-based switching is performedby the fabric interconnect.

Port Profiles

Port profiles contain the properties and settings that you can use to configure virtual interfaces in Cisco UCSfor VM-FEX. The port profiles are created and administered in Cisco UCS Manager. After a port profile iscreated, assigned to, and actively used by one or more DVSes, any changes made to the networking propertiesof the port profile in Cisco UCS Manager are immediately applied to those DVSes.

In VMware vCenter, a port profile is represented as a port group. Cisco UCSManager pushes the port profilenames to VMware vCenter, which displays the names as port groups. None of the specific networking propertiesor settings in the port profile are visible in VMware vCenter. You must configure at least one port profileclient for a port profile if you want Cisco UCS Manager to push the port profile to VMware vCenter.

Cisco UCS Manager VM-FEX for VMware GUI Configuration Guide OL-25368-01 5

IntroductionCisco UCS Manager

Page 16: VMware VM-FEX UCS Configuration Guide

Port Profile Clients

The port profile client determines the DVSes to which a port profile is applied. By default, the port profileclient specifies that the associated port profile applies to all DVSes in the VMware vCenter. However, youcan configure the client to apply the port profile to all DVSes in a specific datacenter or datacenter folder oronly to one DVS.

VMware vCenterYou need VMware vCenter (vCenter Server and vSphere Client) for VM-FEX for VMware. The VMwarevCenter must meet the following requirements:

• The Windows-based machine that you install VMware vCenter on must have network connectivity tothe Cisco UCS management port and to the uplink Ethernet port(s) being used by the ESX host. Themanagement port connectivity is used for management plane integration between VMware vCenter andCisco UCSManager; the uplink Ethernet port connectivity is used for communication between VMwarevCenter and the ESX host.

The HTTP and HTTPS ports (normally TCP 80 and 443) must not be blocked betweenvCenter and the Cisco UCS domain.

Note

• A VMware vCenter extension key provided by Cisco UCS Manager must be registered with VMwarevCenter before VMware vCenter acknowledges the Cisco UCS domain.

In addition, you must configure VMware vCenter with the following parameters:

• A datacenter.

• A distributed virtual switch (DVS).

• ESX hosts added to the DVS and configured to migrate to pass-through switching PTS/DVS.

• For each Cisco VIC adapter, two static vNICs (one for each fabric) added to the DVS.

• Virtual machines (VMs) required for the VMs on the server.

• (For VMware vMotion) Hosts with common shared storage (datastore) that are properly configured forvMotion.

• (For VM-FEX in high-performance mode) All guest memory on the VMs must be reserved.

• (For VM-FEX in high-performance mode) The port profiles and VMwarePassThrough Ethernet adapterpolicy that you have previously configured in Cisco UCS Manager must be specified.

For information about how to configure these required components in VMware vCenter, see the VMwareproduct documentation.

Modes of OperationVM-FEX ports can operate in standard mode or high-performance mode.

Cisco UCS Manager VM-FEX for VMware GUI Configuration Guide6 OL-25368-01

IntroductionVMware vCenter

Page 17: VMware VM-FEX UCS Configuration Guide

Standard ModeIn standard mode, traffic to and from a virtual machine passes through the distributed virtual switch (DVS)and the hypervisor.

The following figure shows the traffic paths taken by VM traffic on a Cisco UCS server with a VIC adapterthat has VM-FEX ports in standard mode.

Figure 2: Traffic Paths for VM Traffic with VM-FEX

High-Performance ModeIn high-performance mode, traffic to and from a virtual machine (VM) bypasses the DVS and hypervisor.Traffic travels directly between VMs and the virtual interface card (VIC) adapter.

The benefits of high-performance mode are as follows:

• Increases I/O performance and throughput.

• Decreases I/O latency.

• Improves CPU utilization for virualized I/O-intensive applications.

With VMware, high-performance mode also supports vMotion. During vMotion, the hypervisor reconfigureslinks in high-performance mode to be in standard mode, transitions the link to the new hypervisor, and then

Cisco UCS Manager VM-FEX for VMware GUI Configuration Guide OL-25368-01 7

IntroductionStandard Mode

Page 18: VMware VM-FEX UCS Configuration Guide

reconfigures the link to be in high-performance mode. The following figure shows how VM-FEX operatesin high-performance mode with vMotion.

Figure 3: VM-FEX in High-Performance Mode with VMotion

1 Two VMs are attached to a VIC in high-performance mode.

2 VMotion begins on one VM. This VM transitions to standard mode.

3 The VM migrates to the other host, and standard mode is established.

4 The VM transitions back to high-performance mode.

Configuring VM-FEX for VMwareProcedure

PurposeCommand or Action

You must modify or create several policies in order forVM-FEX for VMware to function optimally:

Configure a Service Profile forVM-FEX for VMware.

Step 1

• VMwarePassThrough Ethernet Adapter Policy(high-performance mode only)

• Dynamic vNIC Connection Policies

• BIOS Policy (high-performance mode only)

• VM Lifecycle Policy

For more information, see Configuring a Service Profile withVM-FEX, on page 11.

You must configure the VMware ESX host and install theCisco VEM software bundle and a VMware vCenter for

Configure the installation of theCisco VEM bundle on thehypervisor host.

Step 2

VM-FEX. For more information, see Installing the Cisco VEMSoftware Bundle, on page 19 and the VMware documentation.

Cisco UCS Manager VM-FEX for VMware GUI Configuration Guide8 OL-25368-01

IntroductionConfiguring VM-FEX for VMware

Page 19: VMware VM-FEX UCS Configuration Guide

PurposeCommand or Action

For simple implementations, you can use the wizard to performthese steps, or for more complex implementations, use theinformation provided in steps 4 through 6 in this procedure.

The wizard does not address every VMware vCenterconfiguration.

Note

(Optional) In Cisco UCS Manager,use the VMware Integration wizardto connect Cisco UCS Manager toVMware vCenter, define adistributed virtual switch, defineport profiles, and apply thisconfiguration to VMware vCenter.

Step 3

For more information, see Using the Configure VMwareIntegration Wizard, on page 29.

You must connect Cisco UCSManager with VMware vCenterto manage the distributed virtual switch (DVS) in Cisco UCS

Connect Cisco UCS Manager toVMware vCenter.

Step 4

Manager. For more information, see Connecting Cisco UCSManager to VMware vCenter, on page 37.

You must create a distributed virtual switch (DVS) to use inplace of the VMware vSwitch. For more information, see

In Cisco UCS Manager, define adistributed virtual switch.

Step 5

Configuring Distributed Virtual Switches in Cisco UCS, onpage 43.

You must create a port profile to define the properties andsettings used to configure the virtual interfaces in the DVS.

In Cisco UCS Manager, define aport profile and (optionally) createa port profile client.

Step 6

Optionally, you can also create a port profile client that definesthe DVSes to which port profiles are assigned. For moreinformation, see Configuring Port Profiles, on page 55.

Cisco UCS Manager VM-FEX for VMware GUI Configuration Guide OL-25368-01 9

IntroductionConfiguring VM-FEX for VMware

Page 20: VMware VM-FEX UCS Configuration Guide

Cisco UCS Manager VM-FEX for VMware GUI Configuration Guide10 OL-25368-01

IntroductionConfiguring VM-FEX for VMware

Page 21: VMware VM-FEX UCS Configuration Guide

C H A P T E R 2Configuring a Service Profile with VM-FEX

This chapter includes the following sections:

• Modifying the VMwarePassThrough Ethernet Adapter Policy, page 11

• Configuring Dynamic vNIC Connection Policies, page 12

• Configuring the VM Lifecycle Policy, page 15

• Creating a BIOS Policy for VM-FEX in High-Performance Mode, page 17

Modifying the VMwarePassThrough Ethernet Adapter PolicyVM-FEX in high-performance mode has a system-provided VMwarePassThrough adapter policy. Most ofthe default settings are sufficient. However, you might need different settings than this policy provides toaccommodate your particular implementation. If you need different settings, we recommend that you createanother Ethernet adapter policy with your specific settings. In particular, you might want to check the followingsettings to make sure that they work with your particular implementation:

• Guest OS requirements

◦Transmit queue

◦Receive queue

◦Completion queues

◦Interrupts

• Maximum number of interfaces per host.

• Maximum number of interfaces in pass-through mode per host.

For more information about configuring an Ethernet adapter policy, see the Cisco UCS Manager GUIConfiguration Guide.

Cisco UCS Manager VM-FEX for VMware GUI Configuration Guide OL-25368-01 11

Page 22: VMware VM-FEX UCS Configuration Guide

Configuring Dynamic vNIC Connection Policies

Dynamic vNIC Connection PolicyThe dynamic vNIC connection policy determines how the connectivity between VMs and dynamic vNICs isconfigured. This policy is required for Cisco UCS domains that include servers with VIC adapters on whichyou have installed VMs and configured dynamic vNICs.

Each dynamic vNIC connection policy includes an Ethernet adapter policy and designates the number ofvNICs that can be configured for any server associated with a service profile that includes the policy.

For VM-FEX that has all ports on a blade in standard mode, you need to use the VMware adapter policy.

For VM-FEX that has at least one port on a blade in high-performance mode, use the VMwarePassThroughadapter policy or create a custom policy. If you need to create a custom policy, the resources provisioned needto equal the resource requirements of the guest OS that needs the most resources and for which you will beusing high-performance mode.

In a VM-FEX deployment, a VM will attach to a dynamic vNIC only if the VIC adapter has two staticvNICs, one for each fabric, attached to the DVS in vCenter. If a server contains more than one VIC adapter,each adapter must have two static vNICs configured.

Note

If you migrate a server that is configured with dynamic vNICs using VMotion, the dynamic interface usedby the vNICs fails and Cisco UCS Manager notifies you of that failure.

When the server comes back up, Cisco UCS Manager assigns new dynamic vNICs to the server. If youare monitoring traffic on the dynamic vNIC, you must reconfigure the monitoring source.

Note

Creating a Dynamic vNIC Connection PolicyYou can create a dynamic vNIC connection policy.

Procedure

Step 1 In the Navigation pane, click the LAN tab.Step 2 On the LAN tab, expand LAN > Policies.Step 3 Expand the node for the organization where you want to create the policy.

If the system does not include multitenancy, expand the root node.

Step 4 Right-click the Dynamic vNIC Connection Policies node and choose Create Dynamic vNIC ConnectionPolicy.

Step 5 In the Create Dynamic vNIC Connection Policy dialog box, complete the following fields:

Cisco UCS Manager VM-FEX for VMware GUI Configuration Guide12 OL-25368-01

Configuring a Service Profile with VM-FEXConfiguring Dynamic vNIC Connection Policies

Page 23: VMware VM-FEX UCS Configuration Guide

DescriptionName

The name of the policy.

This name can be between 1 and 16 alphanumeric characters. Youcannot use spaces or any special characters other than - (hyphen), _(underscore), : (colon), and . (period), and you cannot change this nameafter the object has been saved.

Name field

A description of the policy.We recommend that you include informationabout where and when the policy should be used.

Enter up to 256 characters. You can use any characters or spaces except` (accent mark), \ (backslash), ^ (carat), " (double quote), = (equal sign),> (greater than), < (less than), or ' (single quote).

Description field

The number of dynamic vNICs that this policy affects.

Enter an integer between 0 and 256. The default is 54.

Components of your system might limit this number to fewerthan 256 vNICs.

Note

Number of Dynamic vNICs field

The adapter profile associated with this policy. The profile must alreadyexist to be included in the drop-down list.

Adapter Policy drop-down list

Dynamic vNICs are always protected in Cisco UCS, but this field allowsyou to select a preferred fabric, if any. You can choose one of thefollowing:

• Protected Pref A—Cisco UCS attempts to use fabric A but failsover to fabric B if necessary

• Protected Pref B—Cisco UCS attempts to use fabric B but failsover to fabric A if necessary

• Protected—Cisco UCS uses whichever fabric is available

Protection field

Step 6 Click OK.Step 7 If a confirmation dialog box appears, click Yes.

Changing a Dynamic vNIC Connection PolicyYou can change a dynamic vNIC connection policy.

Cisco UCS Manager VM-FEX for VMware GUI Configuration Guide OL-25368-01 13

Configuring a Service Profile with VM-FEXDynamic vNIC Connection Policy

Page 24: VMware VM-FEX UCS Configuration Guide

Procedure

Step 1 In the Navigation pane, click the LAN tab.Step 2 On the LAN tab, expand LAN > Policies.Step 3 Expand the node for the organization that contains the policy that you want to change.

If the system does not include multitenancy, expand the root node.

Step 4 Expand the Dynamic vNIC Connection Policies node and click the policy that you want to change.Step 5 In theWork pane, click the General tab.Step 6 Change one or more of the following fields:

DescriptionName

A description of the policy. We recommend that youinclude information about where and when the policyshould be used.

Description field

The number of dynamic vNICs that this policy affects.Number of Dynamic vNICs field

The adapter profile associated with this policy. Theprofile must already exist to be included in thedrop-down list.

Adapter Policy drop-down list

You cannot change the other properties of the policy, such as the Name field.

Step 7 Click Save Changes.Step 8 If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes.

Deleting a Dynamic vNIC Connection PolicyYou can delete a dynamic vNIC connection policy.

Procedure

Step 1 In the Navigation pane, click the LAN tab.Step 2 On the LAN tab, expand LAN > Policies > Organization_Name.Step 3 Expand the Dynamic vNIC Connection Policies node.Step 4 Right-click the policy that you want to delete and choose Delete.Step 5 If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes.

Cisco UCS Manager VM-FEX for VMware GUI Configuration Guide14 OL-25368-01

Configuring a Service Profile with VM-FEXDynamic vNIC Connection Policy

Page 25: VMware VM-FEX UCS Configuration Guide

Viewing Dynamic vNIC Properties in a VMYou can view dynamic vNIC properties in a VM.

Before You Begin

The VM must be operational.

Procedure

Step 1 In the Navigation pane, click the VM tab.Step 2 On the VM tab, expand All > VMware.Step 3 Expand Virtual Machines.Step 4 Expand the virtual machine that contains the dynamic vNIC.Step 5 Choose the dynamic vNIC.Step 6 In theWork pane, click the General tab.

In the Properties area, the vNIC properties appear.

Configuring the VM Lifecycle Policy

VM Lifecycle PolicyThe VM lifecycle policy determines how long Cisco UCS Manager retains offline VMs and offline dynamicvNICs in its database. If a VM or dynamic vNIC remains offline after that period, Cisco UCSManager deletesthe object from its database.

All virtual machines (VMs) on Cisco UCS servers are managed by vCenter. Cisco UCS Manager cannotdetermine whether an inactive VM is temporarily shut down, has been deleted, or is in some other state thatrenders it inaccessible. Therefore, Cisco UCS Manager considers all inactive VMs to be in an offline state.

Cisco UCS Manager considers a dynamic vNIC to be offline when the associated VM is shut down, or thelink between the fabric interconnect and the I/O module fails. On rare occasions, an internal error can alsocause Cisco UCS Manager to consider a dynamic vNIC to be offline.

The default VM and dynamic vNIC retention period is 15 minutes. You can configure a retention period ofbetween 1 minute and 7200 minutes (2 days).

The VM database displayed by Cisco UCS Manager is for information and monitoring only. You cannotmanage VMs through Cisco UCS Manager. If you delete a VM from the Cisco UCS Manager database,the VM is not deleted from the server or from vCenter.

Note

Cisco UCS Manager VM-FEX for VMware GUI Configuration Guide OL-25368-01 15

Configuring a Service Profile with VM-FEXConfiguring the VM Lifecycle Policy

Page 26: VMware VM-FEX UCS Configuration Guide

Configuring the VM Lifecycle PolicyYou can configure the VM lifecycle policy.

Procedure

Step 1 In the Navigation pane, click the VM tab.Step 2 On the VM tab, expand the All node.Step 3 On the VM tab, click VMWare.Step 4 In theWork pane, click the Life Cycle Policy tab.Step 5 In the Life Cycle Policy area, complete the following fields:

DescriptionName

The period of time that Cisco UCS Manager retains an offline VM inits database. If a VM remains offline after that period, Cisco UCSManager deletes the VM from its database. This can be one of thefollowing:

• 1 Min

• 1 Hour

• 1 Day

• other—CiscoUCSManager displays theMinutes field that allowsyou to specify a custom retention time.

VM Retention field

Enter an integer between 1 and 7200 minutes (or 5 days).Minutes field

The period of time that Cisco UCSManager retains an offline dynamicvNIC in its database. If a dynamic vNIC remains offline after that period,Cisco UCS Manager deletes the dynamic vNIC from its database. Thiscan be one of the following:

• 1 Min

• 1 Hour

• 1 Day

• other—CiscoUCSManager displays theMinutes field that allowsyou to specify a custom retention time.

vNIC Retention field

Enter an integer between 1 and 7200 minutes (or 5 days).Minutes field

Step 6 Click Save Changes.

Cisco UCS Manager VM-FEX for VMware GUI Configuration Guide16 OL-25368-01

Configuring a Service Profile with VM-FEXConfiguring the VM Lifecycle Policy

Page 27: VMware VM-FEX UCS Configuration Guide

Creating a BIOS Policy for VM-FEX in High-Performance ModeFor VM-FEX in high performance mode, you must configure specific BIOS settings.

Cisco UCSManager pushes BIOS configuration changes through a BIOS policy or default BIOS settingsto the Cisco Integrated Management Controller (CIMC) buffer. These changes remain in the buffer anddo not take effect until the server is rebooted.

We recommend that you verify the support for BIOS settings in the server that you want to configure.Some settings, such as Mirroring Mode and Sparing Mode for RAS Memory, are not supported by allCisco UCS servers.

Note

We recommend that you name this BIOS policy as VMwarePassThru so that you can identify it as being usedfor VM-FEX in high-performance mode.

You must enable these specific parameters in the following BIOS settings:

• Processor—Enable Virtual Technology (VT) and Direct Cache Access.

You must enable VT if you intend to run 64-bit VMs on the ESX/ESXi host. AnESX/ESXi host will not run 64-bit VMs unless VT is enabled.

Note

• Intel Directed IO—Enable the following parameters:

◦VT for Directed IO

◦Interrupt Remap

◦Coherency Support

◦ATS Support

◦Pass Through DMA Support

Configure the remaining BIOS settings, as appropriate.

For more information, see the Cisco UCS Manager GUI Configuration Guide.

Cisco UCS Manager VM-FEX for VMware GUI Configuration Guide OL-25368-01 17

Configuring a Service Profile with VM-FEXCreating a BIOS Policy for VM-FEX in High-Performance Mode

Page 28: VMware VM-FEX UCS Configuration Guide

Cisco UCS Manager VM-FEX for VMware GUI Configuration Guide18 OL-25368-01

Configuring a Service Profile with VM-FEXCreating a BIOS Policy for VM-FEX in High-Performance Mode

Page 29: VMware VM-FEX UCS Configuration Guide

C H A P T E R 3Installing the Cisco VEM Software Bundle

This chapter includes the following sections:

• Cisco VEM Software Bundle Installation Overview, page 19

• Cisco VEM Software Bundle Prerequisites, page 19

• Installing or Upgrading the Cisco VEM Software Bundle Using VUM, page 20

• Upgrading a Host to ESX or ESXi 4.0, Update 3 or to ESX or ESXi 4.1, Update 1 and the CompatibleCisco VEM Software Bundle, page 21

• Upgrading a Host to ESXi 5.0 and the Compatible Cisco VEM Software Bundle, page 23

• Upgrading a Host to ESXi 5.1 and the Compatible Cisco VEM Software Bundle, page 24

• Installing or Upgrading the Cisco VEM Software Bundle on an ESX or ESXi Host, page 25

• Uninstalling the Cisco VEM Software Bundle, page 27

Cisco VEM Software Bundle Installation OverviewTo use the VM-FEX feature with Cisco UCS, you must install the Cisco UCS M81KR Virtual Interface Cardin the Cisco UCS server and install the correct VMware ESX software version and Cisco VEM softwarebundle on it. The software that you install depends on whether you intend to use the VM-FEX feature instandard mode or high-performance mode. For more information, see Cisco VEM Software BundlePrerequisites, on page 19.

Cisco VEM Software Bundle PrerequisitesBefore installing the Cisco VEM software bundle, make sure to satisfy these prerequisites:

• You must install a Cisco UCS M81KR Virtual Interface Card in the server you intend to use as thehypervisor host. For more information about installing a Cisco UCSM81KR Virtual Interface Card, seethe Cisco UCS 5108 Server Chassis Hardware Installation Guide.

• You must install the correct version of VMware ESX or ESXi software on the Cisco UCSManager host.For VM-FEX in standard mode, you must install VMware ESX version 4.0, Update 1 software or later

Cisco UCS Manager VM-FEX for VMware GUI Configuration Guide OL-25368-01 19

Page 30: VMware VM-FEX UCS Configuration Guide

versions. For VM-FEX in standard mode and high-performance mode, you must install VMware ESXi5.0 software or later versions. For information about upgrading these VMware software versions, seeUpgrading a Host to ESX or ESXi 4.0, Update 3 or to ESX or ESXi 4.1, Update 1 and the CompatibleCisco VEM Software Bundle, on page 21 or Upgrading a Host to ESXi 5.0 and the Compatible CiscoVEM Software Bundle, on page 23.

• You must obtain the Cisco VEM software bundle from the Cisco Download Software page:

◦For B-Series from, http://software.cisco.com/download/navigator.html. Select Downloads Home> Products > Servers - Unified Computing > Cisco UCS B-Series Blade Server Software andclick Unified Computing Systems (UCS) Drivers. From this page, click Latest Releases or AllReleases to select the release you want, and click Download to download the ISO image ofUCS-related drivers.

◦For C-Series from, http://software.cisco.com/download/navigator.html. Select Downloads Home> Products > Servers - Unified Computing >Cisco UCSC-Series Rack-Mount UCS-ManagedServer Software and click Unified Computing Systems (UCS) Drivers. From this page, clickLatest Releases or All Releases to select the release you want, and click Download to downloadthe ISO image of UCS-related drivers.

• You must install the correct version of the Cisco VEM software bundle on the hypervisor host. TheCisco VEM software bundle that you install depends on the VMware ESX or ESXi version you haveinstalled on the hypervisor host. For information about the compatible versions of VMware ESX softwareand Cisco VEM software bundles, see VM-FEX Software Interoperability Matrix in Hardware andSoftware Interoperability Matrix for B Series Servers at http://www.cisco.com/en/US/products/ps10477/prod_technical_reference_list.html.

The VEM software bundle is also a component of another product: the Cisco Nexus1000V switch. Do not be concerned if you see references to this product during theinstallation of the VEM bundle. This reference is cosmetic only and does not affect theoutcome of the installation and implementation of VM-FEX.

Note

• You must be aware of any installation caveats. For information, see the Release Notes for Cisco UCSManager.

Installing or Upgrading the Cisco VEM Software Bundle UsingVUM

To install the Cisco VEM software bundle using VMware vSphere Update Manager (VUM), you need to loginto the VMware vSphere client and copy the VM-FEX driver VIBs or bundles from cisco.com locally andimport them in VUM.

For information about configuring VUM, see the VMware product documentation.

Cisco UCS Manager VM-FEX for VMware GUI Configuration Guide20 OL-25368-01

Installing the Cisco VEM Software BundleInstalling or Upgrading the Cisco VEM Software Bundle Using VUM

Page 31: VMware VM-FEX UCS Configuration Guide

Upgrading a Host to ESX or ESXi 4.0, Update 3 or to ESX or ESXi4.1, Update 1 and the Compatible Cisco VEM Software Bundle

You can use this procedure to upgrade a host to ESX or ESXi 4.0, Update 3 or 4.1, Update 1 and simultaneouslyupgrade the Cisco VEM software bundle.

You can also perform this procedure using VMware VUM. For more information, see Installing orUpgrading the Cisco VEM Software Bundle Using VUM, on page 20 and the VMware documentation.

Note

Before You Begin

• You have copied the ESX or ESXi host software and Cisco VEM software bundle to the /tmp directory.

To determine the correct Cisco VEM software bundle for your ESX or ESXi version and Cisco UCSrelease, see the Hardware and Software Interoperability Matrix for B Series Servers.

Procedure

Step 1 Power off the VMs or migrate all VMs to another host.Step 2 Migrate the vmk0 management interface to the vSwitch.Step 3 Remove the host from pass-through switching (PTS) mode.Step 4 If you are upgrading from ESX or ESXi 4.0, Update 1 to ESX or ESXi 4.0, Update 3, uninstall the VIB that

enables pass-through switching (PTS). Otherwise, continue to step 6.a) Enter the following command to identify the Cisco VEM VIB:

esxupdate query --vib-view | grep cross_cisco | grep installed

The output appears showing the VIB package to be removed.

b) Enter the following command to remove the VIB.esxupdate -b VIB_package remove

Example:

[root@serialport -]# esxupdate query --vib-view | grep cross_cisco | grep installed[root@serialport -]# cross_cisco-vem-v100-esx_4.0.4.1.1.31-1.11.11 installed2010-03-11T10:02:29.076573-05:00[root@serialport -]# esxupdate -b cross_cisco-vem-v100-esx_4.0.4.1.1.31-1.11.11 remove

Step 5 If you are upgrading a host from ESX or ESXi 4.0, Update 1 to ESX or ESXi 4.0, Update 3, copy the ESXor ESXi Patch 04 (ESX400-201001001.zip) and the ESX or ESXi Patch 05 (ESX400-201003001.zip) to the/tmp directory and install them, if you have not already installed them. Otherwise, continue to step 6.vihostupdate --install --bundle "[path to VMware Update offline patch]" --server [vsphere host IP address]"

Example:

[root@serialport -]# vihostupdate --install --bundle "/tmp/Patch04/ESX400-201002001.zip"--server 10.10.10.1

Cisco UCS Manager VM-FEX for VMware GUI Configuration Guide OL-25368-01 21

Installing the Cisco VEM Software BundleUpgrading a Host to ESX or ESXi 4.0, Update 3 or to ESX or ESXi 4.1, Update 1 and the Compatible Cisco VEM Software

Bundle

Page 32: VMware VM-FEX UCS Configuration Guide

[root@serialport -]# vihostupdate --install --bundle"/tmp/Patch05/BuiltByVMware/ESX/20100330/ESX400-201003001.zip" --server 10.10.10.1

Step 6 Go to the directory where the ESX or ESXi host software and Cisco VEM software bundle were copied.

Example:

[root@serialport -]# cd tmp[root@serialport tmp]#

Step 7 Put the host in maintenance mode.Step 8 Enter the vihostupdate command:

vihostupdate --install --bundle "[path to VMware Update offline bundle]", "[path to Cisco updated VEMoffline bundle] --server [vsphere host IP address]"

Example:This example shows how to upgrade to ESX 4.0, Update 3 using the vihostupdate command from a client:

[root@serialport tmp]# vihostupdate --install --bundle"/tmp/update-from-esx4.0-4.0_update03.zip", "/root/UPGRADE/BL/VEM400-201101406.zip --server10.10.10.1Enter username: rootEnter password:Please wait installation in progress …The update completed successfully, but the system needs to be rebooted for the changes tobe effective.[root@serialport tmp]#

Example:This example shows how to upgrade to ESX 4.1, Update 1 using the vihostupdate command from a client:

[root@serialport tmp]# vihostupdate --install --bundle"/tmp/update-from-esx4.1-4.1_update01.zip" , "/root/UPGRADE/BL/VEM410-201101407.zip" --server10.10.10.1Enter username: rootEnter password:Please wait patch installation is in progress ...The update completed successfully, but the system needs to be rebooted for the changes tobe effective.

Step 9 Reboot the host.Step 10 Verify that the installation was successful. A successful installation shows the correct ESX or ESXi version

and the correct Cisco VEM software bundle installed.

Example:This example shows how to verify that the correct Cisco VEM software bundle was installed:

[root@serialport tmp]# esxupdate query --vib-view | grep cross_cisco | grep installedcross_cisco-vem-v130-esx_4.2.1.1.4.0.0-1.20.1 installed2011-08-18T00:01:07.104096+00:00[root@serialport tmp]# vmkload_mod -l | grep vemvem-v130-svs-mux 0x418035e73000 0x4000 0x417ff6d1fc40 0x1000 56 Yes

vem-v130-pts 0x418035e77000 0x16000 0x417ff6d193c0 0x1000 57 Yes

This example shows how to verify that ESX 4.0, Update 3 was installed:

[root@serialport tmp]# vmware -vVMware ESX 4.0.0 build-398348[root@serialport tmp]#

Cisco UCS Manager VM-FEX for VMware GUI Configuration Guide22 OL-25368-01

Installing the Cisco VEM Software BundleUpgrading a Host to ESX or ESXi 4.0, Update 3 or to ESX or ESXi 4.1, Update 1 and the Compatible Cisco VEM SoftwareBundle

Page 33: VMware VM-FEX UCS Configuration Guide

This example show how to verify that ESX 4.1, Update 1 was installed:

[root@serialport tmp]# vmware -vVMware ESX 4.1.0 build-348481[root@serialport tmp]#

Step 11 Remove the host from maintenance mode.Step 12 Place the host in pass-through switching (PTS) mode.Step 13 Migrate the vmk0 management interface back to the host.Step 14 Power on the VMs or migrate all VMs back to the original host.

Upgrading a Host to ESXi 5.0 and the Compatible Cisco VEMSoftware Bundle

You can upgrade a host to ESXi 5.0 with the compatible Cisco VEM software bundle using an Interactiveupgrade from CD, DVD, or USB drive or using VMware vSphere Update Manager (VUM) (also known asan online upgrade).

Before You Begin

You have copied the ESXi 5.0 host software and the Cisco VEM software bundle to the /tmp directory. Todetermine the correct Cisco VEM software bundle to use, see the Hardware and Software InteroperabilityMatrix for B Series Servers.

Procedure

Step 1 Upgrade the Cisco UCS to release 1.4 and the ESX or ESXi host to one of the following releases:

• Release 4.0, Update 3 with Cisco VEM software bundle v130-4.2.1.1.4.0.0-1.20.1.vib (orv129-4.2.1.1.4.0.0-1.20.1.vib if VUM was used)◦

◦Release 4.1, Update 1 with Cisco VEM software bundle v130-4.2.1.1.4.0.0-2.0.1.vib (orv129-4.2.1.1.4.0.0-2.0.1.vib if VUM was used)

For more information, see Upgrading a Host to ESX or ESXi 4.0, Update 3 or to ESX or ESXi 4.1, Update1 and the Compatible Cisco VEM Software Bundle, on page 21.

Step 2 Upgrade the Cisco UCS to release 2.0.For more information, see Upgrading Cisco UCS from Release 1.4 to Release 2.0.

Step 3 Because VM-FEX for VMware has Cisco VEMs that require custom .vib files, create a custom ESX installableISO file that includes the Cisco VEM software bundle. This custom ESX installable ISO file is installed aspart of the ESXi 5.0 host upgrade.For more information, see the "Upgrading Hosts That Have Third-Party CustomVIBs" section in the VMwarevSphere Upgrade document for vSphere 5.0.

Step 4 Upgrade the host to ESXi 5.0 and install the custom ESX installable ISO file.For more information, see the VMware vSphere Upgrade document for vSphere 5.0.

Cisco UCS Manager VM-FEX for VMware GUI Configuration Guide OL-25368-01 23

Installing the Cisco VEM Software BundleUpgrading a Host to ESXi 5.0 and the Compatible Cisco VEM Software Bundle

Page 34: VMware VM-FEX UCS Configuration Guide

You can also upgrade the host to ESXi 5.0 using VUM. For more information, see Installing orUpgrading the Cisco VEM Software Bundle Using VUM, on page 20 and the VMwaredocumentation.

Note

Upgrading a Host to ESXi 5.1 and the Compatible Cisco VEMSoftware Bundle

You can upgrade a host to ESXi 5.1 with the compatible Cisco VEM software bundle using an Interactiveupgrade from CD, DVD, or USB drive or using VMware vSphere Update Manager (VUM) (also known asan online upgrade).

Before You Begin

You have copied the ESXi 5.1 host software and the Cisco VEM software bundle to the /tmp directory. Todetermine the correct Cisco VEM software bundle to use, see the Hardware and Software InteroperabilityMatrix for B Series Servers.

Procedure

Step 1 Upgrade the Cisco UCS to release 1.4 and the ESX or ESXi host to one of the following releases:

• Release 4.0, Update 3 with Cisco VEM software bundle v130-4.2.1.1.4.0.0-1.20.1.vib (orv129-4.2.1.1.4.0.0-1.20.1.vib if VUM was used)◦

◦Release 4.1, Update 1 with Cisco VEM software bundle v130-4.2.1.1.4.0.0-2.0.1.vib (orv129-4.2.1.1.4.0.0-2.0.1.vib if VUM was used)

For more information, see Upgrading a Host to ESX or ESXi 4.0, Update 3 or to ESX or ESXi 4.1, Update1 and the Compatible Cisco VEM Software Bundle, on page 21.

Step 2 Upgrade the Cisco UCS to release 2.0.For more information, see Upgrading Cisco UCS from Release 1.4 to Release 2.0.

Step 3 Because VM-FEX for VMware has Cisco VEMs that require custom .vib files, create a custom ESX installableISO file that includes the Cisco VEM software bundle. This custom ESX installable ISO file is installed aspart of the ESXi 5.1 host upgrade.For more information, see the "Upgrading Hosts That Have Third-Party CustomVIBs" section in the VMwarevSphere Upgrade document for vSphere 5.0.

Step 4 Upgrade the host to ESXi 5.1 and install the custom ESX installable ISO file.For more information, see the VMware vSphere Upgrade document for vSphere 5.1.

If the installer displays the warning "DISTRIBUTED_VIRTUAL_SWITCH WARNING: Hostcontains DVS VIB(s) that have no substitute on the ISO," press Enter to continue.

Note

Cisco UCS Manager VM-FEX for VMware GUI Configuration Guide24 OL-25368-01

Installing the Cisco VEM Software BundleUpgrading a Host to ESXi 5.1 and the Compatible Cisco VEM Software Bundle

Page 35: VMware VM-FEX UCS Configuration Guide

You can also upgrade the host to ESXi 5.1 using VUM. For more information, see Installing orUpgrading the Cisco VEM Software Bundle Using VUM, on page 20 and the VMwaredocumentation.

During remediation when upgrading using VUM, check the check box for Remove installedthird-party software that is incompatible with the upgrade, and continue with the remediation.

Note

Installing or Upgrading the Cisco VEM Software Bundle on anESX or ESXi Host

Use this procedure to install the Cisco VEM software bundle on a host.

You can also perform this procedure using VMware VUM. For more information, see Installing orUpgrading the Cisco VEM Software Bundle Using VUM, on page 20 and the VMware documentation.

Note

Before You Begin

• You have copied the ESX or ESXi host software and Cisco VEM software bundle to the /tmp directory.

To determine the correct Cisco VEM software bundle for your ESX or ESXi version and Cisco UCSrelease, see the Hardware and Software Interoperability Matrix for B Series Servers.

Procedure

Step 1 Go to the directory where the ESX or ESXi host software and Cisco VEM software bundle were copied.

Example:

[root@serialport -]# cd tmp[root@serialport tmp]#

Step 2 If the host is at ESXi Release 5, proceed to step 3. If the host is at ESX or ESXi Release 4.0 or 4.1, do one ofthe following :

• If you are performing this installation or upgrade remotely from a client, put the host in maintenancemode and enter the vihostupdate command:

vihostupdate --install --bundle [path to desired offline Cisco VEM software bundle] --server [vspherehost IP address]

Example:The following examples shows how to install or upgrade a Cisco VEM software bundle remotely.

[root@serialport ~]# vihostupdate --install --bundle VEM400-201108405.zip --server 192.0.2.1Enter username: rootEnter password:Please wait patch installation is in progress ...

Cisco UCS Manager VM-FEX for VMware GUI Configuration Guide OL-25368-01 25

Installing the Cisco VEM Software BundleInstalling or Upgrading the Cisco VEM Software Bundle on an ESX or ESXi Host

Page 36: VMware VM-FEX UCS Configuration Guide

Host updated successfully.

• If you are performing this installation or upgrade locally on the ESX or ESXi host, log into the eachhost separately and, from the /tmp directory, use the esxupdate command to install the VEM software.This command loads the software manually onto the host, loads the kernel modules, and starts the VEMAgent on the running system.esxupdate --bundle [VMware offline update bundle] update

Example:The following example shows how to install or upgrade a Cisco VEM software bundle locally on a host.

~ # esxupdate -b cross_cisco-vem-v132-4.2.1.1.4.1.0-1.20.4.vib updatecross_cisco-vem-v132-4.2.1.1.4.1.0-1.20.4.vib############################################################################################[100%]

Unpacking cross_cisco-vem-v132-esx_4.2.1.1.4.1.0-1.20.4.vib############################################################################################[100%]

Installing packages :cross_cisco-vem-v132-esx_4.2.1.1.4.1.0-1.2..############################################################################################[100%]

Running [/usr/sbin/vmkmod-install.sh]...ok.

Step 3 If the host is at ESXi Release 5.0, do one of the following:

• If you are performing this installation or upgrade remotely from a client, put the host in maintenancemode and enter the esxcli command, as follows:

esxcli --server Server-IP-Address software vib install --viburl URL-Path-to-vib

Example:The following example shows how to perform this installation or upgrade remotely from a client.

# esxcli --server 30.20.41.197 software vib install --viburlhttp://192.0.2.1/cross_cisco-vem-v132-4.2.1.1.4.1.0-3.0.4.vibEnter username: rootEnter password:Installation Result

Message: Operation finished successfully.Reboot Required: falseVIBs Installed: Cisco_bootbank_cisco-vem-v132-esx_4.2.1.1.4.1.0-3.0.4VIBs Removed:VIBs Skipped:

• If you are performing this installation or upgrade locally on a host, log into the each host separately andfrom the /tmp directory, enter the following command:esxcli software vib install -v /vib-file

Example:The following example shows how to perform this installation or upgrade locally on a host.

# esxcli software vib install -v /cross_cisco-vem-v132-4.2.1.1.4.1.0-3.0.4.vib

Cisco UCS Manager VM-FEX for VMware GUI Configuration Guide26 OL-25368-01

Installing the Cisco VEM Software BundleInstalling or Upgrading the Cisco VEM Software Bundle on an ESX or ESXi Host

Page 37: VMware VM-FEX UCS Configuration Guide

Installation ResultMessage: Operation finished successfully.Reboot Required: falseVIBs Installed: Cisco_bootbank_cisco-vem-v132-esx_4.2.1.1.4.1.0-3.0.4VIBs Removed:VIBs Skipped:

Step 4 (Optional) Verify that the installation or upgrade of the Cisco VEM software bundle was successful on anESX or ESXi 4.0, 4.1 or 5.0 host, by using the following commands:esxcli software vib get | grep name

vmkload_mod -l |grep pts

Example:The following example shows how to verify that the installation or upgrade of the Cisco VEM software bundlewas successful on an ESX 4.1 host:

~ # esxupdate query --v |grep ciscocross_cisco-vem-v132-esx_4.2.1.1.4.1.0-2.0.4 installed2011-09-04T20:03:24.794110+00:00~ # vmkload_mod -l |grep ptsmptsas 2 256vem-v132-pts 0 132~ ##

Uninstalling the Cisco VEM Software BundleUse this procedure to uninstall the Cisco VEM software bundle from a host. The command that you useremoves the software from the host, removes the kernel modules, and stops the VEM Agent on the runningsystem.

Before You Begin

• Make sure that the host is not part of any DVS by removing all of the following active ports from theDVS:

• VMware kernel NICs

• Virtual switch interfaces

• Virtual NICs

• You are logged in to the ESX or ESXi host remotely by using secure shell (SSH).

Procedure

Step 1 If the host is at ESXi release 5.0, proceed to step 2. If the host is at ESX or ESXi release 4.0 or 4.1, uninstallthe Cisco VEM software bundle by using the esxupdate remove -b VEM_name command.

Example:

Cisco UCS Manager VM-FEX for VMware GUI Configuration Guide OL-25368-01 27

Installing the Cisco VEM Software BundleUninstalling the Cisco VEM Software Bundle

Page 38: VMware VM-FEX UCS Configuration Guide

The following example shows how to remove the Cisco VEM software bundle from a host that is at ESX orESXi release 4.1:

[root@serialport ~]# esxupdate remove -b cross_cisco-vem-v132-esx_4.2.1.1.4.1.0-2.0.4Removing cisco-vem-v132-esx#######################################################################################[100%]

Running [/usr/sbin/vmkmod-install.sh]...ok.[root@serialport ~]# esxupdate query --v |grep ciscocross_cisco-vem-v132-esx_4.2.1.1.4.1.0-2.0.4 uninstalled

2011-09-05T09:04:51.096141-07:00[root@serialport ~]#

Step 2 For an ESXi 5.0 host, uninstall the Cisco VEM software bundle by using the esxcli software vib remove

-n --maintenance-mode [Cisco VEM bundle software name] command.

Example:The following example shows how to remove the Cisco VEM software bundle from a host that is at ESXirelease 5.0:

# esxcli software vib remove --maintenance-mode -n cisco-vem-v132-esxRemoval Result

Message: Operation finished successfully.Reboot Required: falseVIBs Installed:VIBs Removed: Cisco_bootbank_cisco-vem-v132-esx_4.2.1.1.4.1.0-3.0.4VIBs Skipped:

Step 3 If the host is at ESXi release 5.0, proceed to step 4. If the host is at ESX or ESXi release 4.0 or 4.1, verifythat the software was successfully uninstalled by checking the output of the esxupdate query --v |grep

cisco command.

Example:The following example shows how to verify that the Cisco VEM software bundle was successfully uninstalledfrom an ESX or ESXi release 4.1 host:

[root@serialport ~]# esxupdate query --v |grep ciscocross_cisco-vem-v132-esx_4.2.1.1.4.1.0-2.0.4 uninstalled

2011-09-05T09:04:51.096141-07:00[root@serialport ~]#

Step 4 For an ESXi 5.0 host, verify that the software was successfully uninstalled by checking for the output of theesxcli software vib get | grep cisco command.

Example:

~ # esxcli software vib get |grep cisco~ #

Step 5 Reboot the system.

Cisco UCS Manager VM-FEX for VMware GUI Configuration Guide28 OL-25368-01

Installing the Cisco VEM Software BundleUninstalling the Cisco VEM Software Bundle

Page 39: VMware VM-FEX UCS Configuration Guide

C H A P T E R 4Using the Configure VMware Integration Wizard

This chapter includes the following sections:

• Overview of the Configure VMware Integration Wizard, page 29

• Configuring the VMware Integration with the Wizard, page 29

Overview of the Configure VMware Integration WizardTheConfigure VMware Integrationwizard provides a single access to perform the basic configuration stepsthat are specific to Cisco UCS Manager. The wizard does not address every vCenter configuration. Forexample, it does not create a DVS structure that includes a vCenter server folder that contains the datacenter.If you want a folder between the vCenter server and the datacenter, do not use this wizard.

You cannot use this wizard to complete the configuration steps that must be performed in VMware vCenterto complete the integration.

Through the Configure VMware Integration wizard, you can perform the following configuration steps:

1 Export the vCenter extension files to establish a connection to VMware vCenter.

You must register the vCenter extension key as a plug-in in VMware vCenter. You cannot perform thatstep in the Configure VMware Integration wizard.

2 Define the structure for one VMware vCenter Distributed Virtual Switch (DVS), including the vCenterserver, datacenter, DVS folder, and DVS.

3 Define the port profile and profile client.

4 Apply the configuration to VMware vCenter.

When you have completed the integration steps through the wizard, you must log in to VMware vCenter andassociate the VMs and port profiles with the DVS. The port profiles are shown as port groups in VMwarevCenter.

Configuring the VMware Integration with the WizardIf you prefer not to use this wizard, you can perform each of these steps individually.

Cisco UCS Manager VM-FEX for VMware GUI Configuration Guide OL-25368-01 29

Page 40: VMware VM-FEX UCS Configuration Guide

Before You Begin

Before you use the Configure VMware Integration wizard, complete the following:

• Configure the VMware ESX host for VM-FEX.

• Configure a VMware vCenter instance for VM-FEX.

• Configure a certificate for VM-FEX.

Procedure

Step 1 In the Navigation pane, click the VM tab.Step 2 On the VM tab, expand the All node.Step 3 In theWork pane, click the General tab.Step 4 In the Actions area, click Configure VMware Integration.Step 5 In the Configure VMware Integration wizard, complete the following:

• Page 1: Establishing the Connection to vCenter Server

• Page 2: Defining a VMware vCenter Distributed Virtual Switch

• Page 3: Defining a Port Profile, on page 33

• Page 4: Applying Port Profiles and Configuration to vCenter Server

Page 1: Establishing the Connection to vCenter ServerThis procedure directly follows the steps in Configuring the VMware Integration with theWizard. It describeshow to establish a connection to VMware vCenter through the Configure VMware Integration wizard.

You can skip this page and move onto the next page if you have already exported and registered the vCenterextension key files.

Before You Begin

• If you want to use a custom extension key, you must modify the extension key before performing thisstep as described in (Optional) Modifying the vCenter Extension Key.

• The vCenter server must have network connectivity to the Cisco UCSmanagement port and to the uplinkEthernet port(s) being used by the ESX host. Specifically, the HTTP and HTTPS ports (normally TCP80 and 443) must not be blocked by any device or policy in the network path.

Procedure

Step 1 To export the vCenter extension files, click one of the following:

Cisco UCS Manager VM-FEX for VMware GUI Configuration Guide30 OL-25368-01

Using the Configure VMware Integration WizardPage 1: Establishing the Connection to vCenter Server

Page 41: VMware VM-FEX UCS Configuration Guide

DescriptionOption

For VMware vCenter version 4.0 update 1 and later.

Exports a single vCenter Extension Key file.

Export

For VMware vCenter version 4.0.

Exports nine vCenter Extension Key files.

Export Multiple

Step 2 In the Export vCenter Extension dialog box, do the following:a) In the Save Location field, enter the path to the directory where you want to save the extension file or

files.If you do not know the path, click the ... button and browse to the location.

b) Click OK.Cisco UCS Manager generates the extension file(s) and saves them to the specified location.

Step 3 Copy the downloaded file to a location on the VMware vCenter.Step 4 Register the vCenter extension file(s) in VMware vCenter.

For more information, see Registering a vCenter Extension File in VMware vCenter, and the instructions onthis page in the Configure VMware Integration wizard.

Step 5 Click Next.

What to Do Next

Complete the steps in Page 2: Defining a VMware vCenter Distributed Virtual Switch.

Page 2: Defining a VMware vCenter Distributed Virtual SwitchThis procedure directly follows the steps in Page 1: Establishing the Connection to vCenter Server. It describeshow to define the components of a distributed virtual switch in VMware vCenter through the ConfigureVMware Integration wizard.

Procedure

Step 1 In the vCenter Server area, complete the following fields to define the connection to VMware vCenter:DescriptionName

The user-defined name for the vCenter server.

This name can be between 1 and 16 alphanumeric characters. Youcannot use spaces or any special characters other than - (hyphen), _(underscore), : (colon), and . (period), and you cannot change this nameafter the object has been saved.

vCenter Server Name field

Cisco UCS Manager VM-FEX for VMware GUI Configuration Guide OL-25368-01 31

Using the Configure VMware Integration WizardPage 2: Defining a VMware vCenter Distributed Virtual Switch

Page 42: VMware VM-FEX UCS Configuration Guide

DescriptionName

The description of the vCenter server.

Enter up to 256 characters. You can use any characters or spaces except` (accent mark), \ (backslash), ^ (carat), " (double quote), = (equal sign),> (greater than), < (less than), or ' (single quote).

Description field

The hostname or IP address of the vCenter server.

If you use a hostname rather than an IP address, you mustconfigure a DNS server. If the Cisco UCS domain is notregistered with Cisco UCS Central or DNS management is setto local, configure a DNS server in Cisco UCSManager. If theCisco UCS domain is registered with Cisco UCS Central andDNS management is set to global, configure a DNS server inCisco UCS Central.

Note

vCenter Server Hostname or IPAddress field

Step 2 In the Datacenter area, complete the following fields to create the datacenter in VMware vCenter:DescriptionName

The name of the vCenter Datacenter.

This name can be between 1 and 16 characters. You can use spaces andany other ASCII characters except for ` (accent), \ (back slash), ^ (carat)," (double quote), / (forward slash), > (greater than), < (less than), or '(single quote).

vCenter Datacenter Name field

The user-defined description of the Datacenter.

Enter up to 256 characters. You can use any characters or spaces except` (accent mark), \ (backslash), ^ (carat), " (double quote), = (equal sign),> (greater than), < (less than), or ' (single quote).

Description field

Step 3 In the DVS Folder area, complete the following fields to create a folder to contain the distributed virtualswitch in VMware vCenter:

DescriptionName

The name of the folder that contains the distributed virtual switch (DVS).

This name can be between 1 and 16 characters. You can use spaces andany other ASCII characters except for ` (accent), \ (back slash), ^ (carat)," (double quote), / (forward slash), > (greater than), < (less than), or '(single quote).

Folder Name field

The user-defined description of the folder.

Enter up to 256 characters. You can use any characters or spaces except` (accent mark), \ (backslash), ^ (carat), " (double quote), = (equal sign),> (greater than), < (less than), or ' (single quote).

Description field

Cisco UCS Manager VM-FEX for VMware GUI Configuration Guide32 OL-25368-01

Using the Configure VMware Integration WizardPage 2: Defining a VMware vCenter Distributed Virtual Switch

Page 43: VMware VM-FEX UCS Configuration Guide

Step 4 In the DVS area, complete the following fields to create the distributed virtual switch in VMware vCenter:DescriptionName

The name of the DVS.

This name can be between 1 and 16 characters. You can use spaces andany other ASCII characters except for ` (accent), \ (back slash), ^ (carat)," (double quote), / (forward slash), > (greater than), < (less than), or '(single quote).

DVS Name field

The user-defined description of the DVS.

Enter up to 256 characters. You can use any characters or spaces except` (accent mark), \ (backslash), ^ (carat), " (double quote), = (equal sign),> (greater than), < (less than), or ' (single quote).

Description field

This can be one of the following:

• disable

• enable

If you disable the DVS, Cisco UCS Manager does not push anyconfiguration changes related to the DVS to VMware vCenter.

DVS field

Step 5 Click Next.

What to Do Next

Complete the steps in Page 3: Defining a Port Profile, on page 33.

Page 3: Defining a Port ProfileThis procedure directly follows the steps in Page 2: Defining a VMware vCenter Distributed Virtual Switch.It describes how to define the components of a distributed virtual switch in VMware vCenter through theConfigure VMware Integration wizard.

Procedure

Step 1 In the Port Profile area, complete the following fields to define the port profile:DescriptionName

The user-defined name for the port profile.

This name can be between 1 and 31 ASCII alphanumeric characters.You cannot use spaces or any special characters other than - (hyphen),_ (underscore), and : (colon), and you cannot change this name afterthe object has been saved.

Name field

Cisco UCS Manager VM-FEX for VMware GUI Configuration Guide OL-25368-01 33

Using the Configure VMware Integration WizardPage 3: Defining a Port Profile

Page 44: VMware VM-FEX UCS Configuration Guide

DescriptionName

The user-defined description for the port profile.

Enter up to 256 characters. You can use any characters or spaces except` (accent mark), \ (backslash), ^ (carat), " (double quote), = (equal sign),> (greater than), < (less than), or ' (single quote).

Description field

The quality of service policy associated with this port profile.QoS Policy drop-down list

The network control policy associated with this port profile.Network Control Policydrop-down list

The maximum number of ports that can be associated with this portprofile. The default is 64 ports.

The maximum number of ports that can be associated with a singledistributed virtual switch (DVS) is 4096. If the DVS has only oneassociated port profile, that port profile can be configured with up to4096 ports. However, if the DVS has more than one associated portprofile, the total number of ports associated with all of those port profilescombined cannot exceed 4096.

Max Ports field

This can be one of the following:

• None—Traffic to and from a virtual machine passes through theDVS.

• High Performance— Traffic to and from a virtual machinebypasses the DVS and hypervisor and travels directly between thevirtual machines and a virtual interface card (VIC) adapter.

Host Network IO Performancefield

The pin group associated with this port profile.Pin Group drop-down list

Step 2 In the VLANs area, do the following to assign one or more VLANs to the port profile:a) In the Select column, check the check box in the appropriate row for each VLAN that you want to use in

the port profile.b) In the Native VLAN column, click the radio button in the appropriate row for the VLAN that you want

to designate as the native VLAN.

Step 3 In the Client Profile area, do the following to create a profile client for the port profile:DescriptionName

The user-defined name for the profile client.

This name can be between 1 and 16 ASCII alphanumeric characters.You cannot use spaces or any special characters other than - (hyphen),_ (underscore), and : (colon), and you cannot change this name afterthe object has been saved.

Name field

Cisco UCS Manager VM-FEX for VMware GUI Configuration Guide34 OL-25368-01

Using the Configure VMware Integration WizardPage 3: Defining a Port Profile

Page 45: VMware VM-FEX UCS Configuration Guide

DescriptionName

The user-defined description of the client.

Enter up to 256 characters. You can use any characters or spaces except` (accent mark), \ (backslash), ^ (carat), " (double quote), = (equal sign),> (greater than), < (less than), or ' (single quote).

Description field

Choose a datacenter from the drop-down list or chooseAll if this profileclient applies to all datacenters.

Datacenter drop-down list

Choose a folder from the drop-down list or choose All if this profileclient applies to all folders.

Folder drop-down list

Choose a virtual switch from the drop-down list or choose All if thisprofile client applies to all virtual switches.

Distributed Virtual Switchdrop-down list

Step 4 Click Next.

What to Do Next

Complete the configuration of the virtual machines in VMware vCenter.

Page 4: Applying Port Profiles and Configuration to vCenter ServerThis procedure directly follows the steps in Page 3: Defining a Port Profile, on page 33. It describes how toapply the port profiles to vCenter Server through the Configure VMware Integration wizard.

Procedure

Step 1 Review the text on the page in the Configure VMware Integration wizard.Step 2 Click Finish.

Cisco UCS Manager connects to the vCenter Server, creates the specified DVS, and applies the port profiles.

What to Do Next

In VMware vCenter, associate the VMs and port profiles with the DVS. The port profiles are shown as portgroups in VMware vCenter.

Cisco UCS Manager VM-FEX for VMware GUI Configuration Guide OL-25368-01 35

Using the Configure VMware Integration WizardPage 4: Applying Port Profiles and Configuration to vCenter Server

Page 46: VMware VM-FEX UCS Configuration Guide

Cisco UCS Manager VM-FEX for VMware GUI Configuration Guide36 OL-25368-01

Using the Configure VMware Integration WizardPage 4: Applying Port Profiles and Configuration to vCenter Server

Page 47: VMware VM-FEX UCS Configuration Guide

C H A P T E R 5Connecting Cisco UCS Manager to VMwarevCenter

This chapter includes the following sections:

• Connecting Using the Extension Key, page 37

• (Optional) Modifying the vCenter Extension Key, page 37

• Exporting a vCenter Extension File from Cisco UCS Manager , page 38

• Registering a vCenter Extension File in VMware vCenter, page 39

• Configuring a Certificate for VM-FEX, page 39

• Creating a Certificate for VM-FEX, page 39

• Copying a Certificate to the Fabric Interconnect, page 40

• Deleting a Certificate for VM-FEX, page 41

Connecting Using the Extension Key

(Optional) Modifying the vCenter Extension KeyYou can modify the vCenter extension key to be more meaningful than the default ID string. This providesbetter system identification.

Cisco UCS Manager VM-FEX for VMware GUI Configuration Guide OL-25368-01 37

Page 48: VMware VM-FEX UCS Configuration Guide

Procedure

Step 1 In the Navigation pane, click the VM tab.Step 2 On the VM tab, expand the All node.Step 3 On the VM tab, click VMWare.Step 4 In theWork pane, click the General tab.Step 5 In the Actions area, clickModify Extension Key.Step 6 In theModify Extension Key dialog box, do the following:

a) In the Key field, modify the key as needed.A vCenter extension key can have a maximum length of 33 characters. These characters can be letters,numbers, or hyphens. No other characters or spaces are permitted in the extension key.

b) Click OK.

What to Do Next

Export the vCenter extension file or files from Cisco UCS Manager.

Exporting a vCenter Extension File from Cisco UCS ManagerDepending on the version of VMware vCenter you are using, you can either generate one extension file or aset of nine extension files.

Procedure

Step 1 In the Navigation pane, click the VM tab.Step 2 On the VM tab, expand the All node.Step 3 On the VM tab, click VMWare.Step 4 In theWork pane, click the General tab.Step 5 In the Actions area, click one of the following links:

DescriptionOption

For vCenter version 4.0 update 1 and later versions.Export vCenter Extension

For vCenter version 4.0.Export Multiple vCenter Extensions

Step 6 In the Export vCenter Extension dialog box, do the following:a) In the Save Location field, enter the path to the directory where you want to save the extension file or

files.If you do not know the path, click the ... button and browse to the location.

b) Click OK.

Cisco UCS Manager VM-FEX for VMware GUI Configuration Guide38 OL-25368-01

Connecting Cisco UCS Manager to VMware vCenterExporting a vCenter Extension File from Cisco UCS Manager

Page 49: VMware VM-FEX UCS Configuration Guide

Cisco UCS Manager generates the extension file(s) and saves them to the specified location.

What to Do Next

Register the vCenter extension file or files in VMware vCenter.

Registering a vCenter Extension File in VMware vCenterIn VMware vCenter, the vCenter extension files are called plug-ins.

Before You Begin

Export the vCenter extension file(s) from Cisco UCS Manager. Ensure that the exported vCenter extensionfiles are saved to a location that can be reached by VMware vCenter.

Procedure

Step 1 In VMware vCenter, choose Plug-ins >Manage Plug-ins.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 theplug-in; instead, leave it in the available state. If you are registering multiple vCenter extension files, repeatthis procedure until all files are registered.

Configuring a Certificate for VM-FEX

Creating a Certificate for VM-FEXBefore You Begin

Copy a certificate to the fabric interconnect.

Cisco UCS Manager VM-FEX for VMware GUI Configuration Guide OL-25368-01 39

Connecting Cisco UCS Manager to VMware vCenterRegistering a vCenter Extension File in VMware vCenter

Page 50: VMware VM-FEX UCS Configuration Guide

Procedure

Step 1 In the Navigation pane, click the VM tab.Step 2 On the VM tab, expand the All node.Step 3 On the VM tab, click VMWare.Step 4 In theWork pane, click the Certificates tab.Step 5 On the icon bar to the right of the table, click +.

If the + icon is disabled, click an entry in the table to enable it.

Step 6 In the Create Key Ring dialog box, complete the following fields:DescriptionName

The name of the key ring.

Enter up to 510 ASCII characters. This name cannot be changed afterthe object has been saved.

Name field

This can be one of the following:

•Workspace

• Volatile

Protocol field

The name of the certificate file associated with this key ring.Certificate File field

The path to the certificate file on the server.Path field

Step 7 Click OK.

Copying a Certificate to the Fabric InterconnectBefore You Begin

Obtain a certificate.

Procedure

PurposeCommand or Action

Enters local management mode.UCS-A# connect local-mgmtStep 1

Copies the certificate from its source location to its destinationlocation. For the from-filesystem: argument, use one of thefollowing syntax:

UCS-A(local-mgmt)# copyfrom-filesystem: [ from-path ]filename to-filesystem: [ to-path ]filename

Step 2

• ftp:// username@server-ip-addr

Cisco UCS Manager VM-FEX for VMware GUI Configuration Guide40 OL-25368-01

Connecting Cisco UCS Manager to VMware vCenterCopying a Certificate to the Fabric Interconnect

Page 51: VMware VM-FEX UCS Configuration Guide

PurposeCommand or Action

• scp:// username@server-ip-addr

• sftp:// username@server-ip-addr

• tftp:// server-ip-addr : port-num

For the to-filesystem: argument, use one of the followingsyntax:

• Volatile:

•Workspace:

The following shows how to use FTP to copy a certificate (certificate.txt) to the temp folder in the workspace:UCS-A # connect local-mgmtCisco 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 byother third parties and are used and distributed under license.Some parts of this software may be covered under the GNU PublicLicense or the GNU Lesser General Public License. A copy ofeach such license is available athttp://www.gnu.org/licenses/gpl.html andhttp://www.gnu.org/licenses/lgpl.html

UCS-A(local-mgmt)# copy ftp://192.168.10.10/certs/certificate.txtworkspace:/temp/certificate.txtUCS-A(local-mgmt)#

What to Do Next

Create a certificate for VM-FEX.

Deleting a Certificate for VM-FEXProcedure

Step 1 In the Navigation pane, click the VM tab.Step 2 On the VM tab, expand the All node.Step 3 On the VM tab, click VMWare.Step 4 In theWork pane, click the Certificates tab.Step 5 In the Key Rings table, click the certificate you want to delete.Step 6 Right-click the certificate you want to delete and select Delete.Step 7 If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes.

Cisco UCS Manager VM-FEX for VMware GUI Configuration Guide OL-25368-01 41

Connecting Cisco UCS Manager to VMware vCenterDeleting a Certificate for VM-FEX

Page 52: VMware VM-FEX UCS Configuration Guide

Cisco UCS Manager VM-FEX for VMware GUI Configuration Guide42 OL-25368-01

Connecting Cisco UCS Manager to VMware vCenterDeleting a Certificate for VM-FEX

Page 53: VMware VM-FEX UCS Configuration Guide

C H A P T E R 6Configuring Distributed Virtual Switches in CiscoUCS

This chapter includes the following sections:

• Distributed Virtual Switches, page 43

• Overview of Creating a DVS in Cisco UCS Manager, page 43

• Configuring a Distributed Virtual Switch, page 44

• Managing Distributed Virtual Switches, page 47

Distributed Virtual SwitchesThe Cisco UCS distributed virtual switch (DVS) is a software-based virtual switch that runs along side thevSwitch in the ESX hypervisor and can be distributed across multiple ESX hosts. Unlike the vSwitch, whichuses its own local port configuration, a DVS that is associated with multiple ESX hosts uses the same portconfiguration across all ESX hosts.

After associating an ESX host to a DVS, you can migrate existing VMs from the vSwitch to the DVS, andyou can create VMs to use the DVS instead of the vSwitch. With the VM-FEX for VMware implementation,when a VM uses the DVS, all VM traffic passes through the DVS and ASIC-based switching is performedby the fabric interconnect.

Overview of Creating a DVS in Cisco UCS ManagerTo create a distributed virtual switch (DVS) in Cisco UCSManager, youmust first create a vCenter, a datacenterunder the vCenter, and a datacenter folder under the datacenter. You can then create a DVS in the datacenterfolder. The vCenter name you specify in Cisco UCS Manager does not need to match the vCenter namespecified in VMware vCenter; however, the datacenter name you specify in Cisco UCS Manager must matchthe datacenter name specified in VMware vCenter. The datacenter folder and DVS you create in Cisco UCSManager are pushed to VMware vCenter.

Cisco UCS Manager VM-FEX for VMware GUI Configuration Guide OL-25368-01 43

Page 54: VMware VM-FEX UCS Configuration Guide

Configuring a Distributed Virtual SwitchBefore You Begin

You must first create a datacenter in VMware vCenter. Do not create the folder inside the datacenter or theDVS in VMware vCenter.

Procedure

Step 1 In the Navigation pane, click the VM tab.Step 2 On the VM tab, expand the All node.Step 3 Right-click the VMWare node and choose Configure vCenter.Step 4 On the Configure vCenter page, do the following:

a) Complete the following fields:DescriptionName

The name of the vCenter folder.

This name can be between 1 and 16 characters. You can use spacesand any other ASCII characters except for ` (accent), \ (back slash),^ (carat), " (double quote), / (forward slash), > (greater than), < (lessthan), or ' (single quote).

Name field

A user-defined description of the folder.

Enter up to 256 characters. You can use any characters or spacesexcept ` (accent mark), \ (backslash), ^ (carat), " (double quote), =(equal sign), > (greater than), < (less than), or ' (single quote).

Description field

b) Click Next.

Step 5 On the Create Folder page, click one of the following:DescriptionOption

Moves to the next page. Choose this option if the vCenter structure does not requireyou to include the datacenter in a high-level folder.

If you choose this option, continue with Step 7.

Next

Opens the Create Folder dialog box, where you can add a high-level folder abovethe datacenter.

If you choose this option, continue with Step 6.

Add

Step 6 (Optional) In the Create Folder dialog box, do the following:a) Complete the following fields:

Cisco UCS Manager VM-FEX for VMware GUI Configuration Guide44 OL-25368-01

Configuring Distributed Virtual Switches in Cisco UCSConfiguring a Distributed Virtual Switch

Page 55: VMware VM-FEX UCS Configuration Guide

DescriptionName

The name of the vCenter folder.

This name can be between 1 and 16 characters. You can use spacesand any other ASCII characters except for ` (accent), \ (back slash),^ (carat), " (double quote), / (forward slash), > (greater than), < (lessthan), or ' (single quote).

Name field

A user-defined description of the folder.

Enter up to 256 characters. You can use any characters or spacesexcept ` (accent mark), \ (backslash), ^ (carat), " (double quote), =(equal sign), > (greater than), < (less than), or ' (single quote).

Description field

b) Click Next.

Step 7 On the Create Datacenter page, do the following:a) Click Add.b) In the Create Datacenter dialog box, complete the following fields:

DescriptionName

The name of the datacenter.

This name can be between 1 and 16 characters. You can use spacesand any other ASCII characters except for ` (accent), \ (back slash),^ (carat), " (double quote), / (forward slash), > (greater than), < (lessthan), or ' (single quote).

The datacenter name that you specify in Cisco UCS Manager mustmatch the name of the datacenter previously created in VMwarevCenter.

Name field

The user-defined description of the datacenter.

Enter up to 256 characters. You can use any characters or spacesexcept ` (accent mark), \ (backslash), ^ (carat), " (double quote), =(equal sign), > (greater than), < (less than), or ' (single quote).

Description field

c) Click Next.

Step 8 In the Create Folder page, do the following to create a folder in the datacenter:a) Click Add.b) In the Create Folder dialog box, complete the following fields:

Cisco UCS Manager VM-FEX for VMware GUI Configuration Guide OL-25368-01 45

Configuring Distributed Virtual Switches in Cisco UCSConfiguring a Distributed Virtual Switch

Page 56: VMware VM-FEX UCS Configuration Guide

DescriptionName

The name of the vCenter folder.

This name can be between 1 and 16 characters. You can use spacesand any other ASCII characters except for ` (accent), \ (back slash),^ (carat), " (double quote), / (forward slash), > (greater than), < (lessthan), or ' (single quote).

Name field

A user-defined description of the folder.

Enter up to 256 characters. You can use any characters or spacesexcept ` (accent mark), \ (backslash), ^ (carat), " (double quote), =(equal sign), > (greater than), < (less than), or ' (single quote).

Description field

c) Click Next.

Step 9 On the Create Distributed Virtual Switches page, do the following to create a distributed virtual switch inthe folder:a) Click Add to add a distributed virtual switch to the folder.b) In the Create Distributed Virtual Switches dialog box, complete the following fields:

DescriptionName

The name of the distributed virtual switch.

This name can be between 1 and 16 characters. You can use spacesand any other ASCII characters except for ` (accent), \ (back slash),^ (carat), " (double quote), / (forward slash), > (greater than), < (lessthan), or ' (single quote).

Name field

The user-defined description of the distributed virtual switch.

Enter up to 256 characters. You can use any characters or spacesexcept ` (accent mark), \ (backslash), ^ (carat), " (double quote), =(equal sign), > (greater than), < (less than), or ' (single quote).

Description field

This can be one of the following:

• Enabled

• Disabled

If you disable the DVS, Cisco UCS Manager does not push anyconfiguration changes related to the DVS to VMware vCenter.

Admin State field

c) Click OK.

Step 10 Click Finish if you have finished adding all datacenters, folders, and DVSes to the vCenter.You may need to click Finish more than once to exit the wizard. You can stop at any page to add anotherdatacenter, folder, or DVS.

Cisco UCS Manager VM-FEX for VMware GUI Configuration Guide46 OL-25368-01

Configuring Distributed Virtual Switches in Cisco UCSConfiguring a Distributed Virtual Switch

Page 57: VMware VM-FEX UCS Configuration Guide

Managing Distributed Virtual Switches

Adding a Folder to an Existing vCenterYou can add a folder inside an existing vCenter and place your datacenters inside the folder. However, thisfolder is optional.

Procedure

Step 1 In the Navigation pane, click the VM tab.Step 2 On the VM tab, expand the VMWare node.Step 3 Right-click the vCenter to which you want to add a datacenter and choose Create Folder.Step 4 (Optional) In the Create Folder dialog box, do the following:

a) Complete the following fields:DescriptionName

The name of the vCenter folder.

This name can be between 1 and 16 characters. You can use spacesand any other ASCII characters except for ` (accent), \ (back slash),^ (carat), " (double quote), / (forward slash), > (greater than), < (lessthan), or ' (single quote).

Name field

A user-defined description of the folder.

Enter up to 256 characters. You can use any characters or spacesexcept ` (accent mark), \ (backslash), ^ (carat), " (double quote), =(equal sign), > (greater than), < (less than), or ' (single quote).

Description field

b) Click Next.

Step 5 On the Create Datacenter page, do the following:a) Click Add.b) In the Create Datacenter dialog box, complete the following fields:

Cisco UCS Manager VM-FEX for VMware GUI Configuration Guide OL-25368-01 47

Configuring Distributed Virtual Switches in Cisco UCSManaging Distributed Virtual Switches

Page 58: VMware VM-FEX UCS Configuration Guide

DescriptionName

The name of the datacenter.

This name can be between 1 and 16 characters. You can use spacesand any other ASCII characters except for ` (accent), \ (back slash),^ (carat), " (double quote), / (forward slash), > (greater than), < (lessthan), or ' (single quote).

The datacenter name that you specify in Cisco UCS Manager mustmatch the name of the datacenter previously created in VMwarevCenter.

Name field

The user-defined description of the datacenter.

Enter up to 256 characters. You can use any characters or spacesexcept ` (accent mark), \ (backslash), ^ (carat), " (double quote), =(equal sign), > (greater than), < (less than), or ' (single quote).

Description field

c) Click Next.

Step 6 In the Create Folder page, do the following to create a folder in the datacenter:a) Click Add.b) In the Create Folder dialog box, complete the following fields:

DescriptionName

The name of the vCenter folder.

This name can be between 1 and 16 characters. You can use spacesand any other ASCII characters except for ` (accent), \ (back slash),^ (carat), " (double quote), / (forward slash), > (greater than), < (lessthan), or ' (single quote).

Name field

A user-defined description of the folder.

Enter up to 256 characters. You can use any characters or spacesexcept ` (accent mark), \ (backslash), ^ (carat), " (double quote), =(equal sign), > (greater than), < (less than), or ' (single quote).

Description field

c) Click Next.

Step 7 On the Create Distributed Virtual Switches page, do the following to create a distributed virtual switch inthe folder:a) Click Add to add a distributed virtual switch to the folder.b) In the Create Distributed Virtual Switches dialog box, complete the following fields:

Cisco UCS Manager VM-FEX for VMware GUI Configuration Guide48 OL-25368-01

Configuring Distributed Virtual Switches in Cisco UCSAdding a Folder to an Existing vCenter

Page 59: VMware VM-FEX UCS Configuration Guide

DescriptionName

The name of the distributed virtual switch.

This name can be between 1 and 16 characters. You can use spacesand any other ASCII characters except for ` (accent), \ (back slash),^ (carat), " (double quote), / (forward slash), > (greater than), < (lessthan), or ' (single quote).

Name field

The user-defined description of the distributed virtual switch.

Enter up to 256 characters. You can use any characters or spacesexcept ` (accent mark), \ (backslash), ^ (carat), " (double quote), =(equal sign), > (greater than), < (less than), or ' (single quote).

Description field

This can be one of the following:

• Enabled

• Disabled

If you disable the DVS, Cisco UCS Manager does not push anyconfiguration changes related to the DVS to VMware vCenter.

Admin State field

c) Click OK.

Step 8 Click Finish if you have finished adding all datacenters, folders, and DVSes to the folder.You may need to click Finish more than once to exit the wizard. You can stop at any page to add anotherdatacenter, folder, or DVS.

Adding a Datacenter to an Existing vCenter

Before You Begin

You must first create a datacenter in VMware vCenter. Do not create the folder inside the datacenter or theDVS in VMware vCenter.

Procedure

Step 1 In the Navigation pane, click the VM tab.Step 2 On the VM tab, expand the VMWare node.Step 3 Right-click the vCenter to which you want to add a datacenter and choose Create Datacenter.Step 4 On the Create Datacenter page, do the following:

a) Click Add.b) In the Create Datacenter dialog box, complete the following fields:

Cisco UCS Manager VM-FEX for VMware GUI Configuration Guide OL-25368-01 49

Configuring Distributed Virtual Switches in Cisco UCSAdding a Datacenter to an Existing vCenter

Page 60: VMware VM-FEX UCS Configuration Guide

DescriptionName

The name of the datacenter.

This name can be between 1 and 16 characters. You can use spacesand any other ASCII characters except for ` (accent), \ (back slash),^ (carat), " (double quote), / (forward slash), > (greater than), < (lessthan), or ' (single quote).

The datacenter name that you specify in Cisco UCS Manager mustmatch the name of the datacenter previously created in VMwarevCenter.

Name field

The user-defined description of the datacenter.

Enter up to 256 characters. You can use any characters or spacesexcept ` (accent mark), \ (backslash), ^ (carat), " (double quote), =(equal sign), > (greater than), < (less than), or ' (single quote).

Description field

c) Click Next.

Step 5 In the Create Folder page, do the following to create a folder in the datacenter:a) Click Add.b) In the Create Folder dialog box, complete the following fields:

DescriptionName

The name of the vCenter folder.

This name can be between 1 and 16 characters. You can use spacesand any other ASCII characters except for ` (accent), \ (back slash),^ (carat), " (double quote), / (forward slash), > (greater than), < (lessthan), or ' (single quote).

Name field

A user-defined description of the folder.

Enter up to 256 characters. You can use any characters or spacesexcept ` (accent mark), \ (backslash), ^ (carat), " (double quote), =(equal sign), > (greater than), < (less than), or ' (single quote).

Description field

c) Click Next.

Step 6 On the Create Distributed Virtual Switches page, do the following to create a distributed virtual switch inthe folder:a) Click Add to add a distributed virtual switch to the folder.b) In the Create Distributed Virtual Switches dialog box, complete the following fields:

Cisco UCS Manager VM-FEX for VMware GUI Configuration Guide50 OL-25368-01

Configuring Distributed Virtual Switches in Cisco UCSAdding a Datacenter to an Existing vCenter

Page 61: VMware VM-FEX UCS Configuration Guide

DescriptionName

The name of the distributed virtual switch.

This name can be between 1 and 16 characters. You can use spacesand any other ASCII characters except for ` (accent), \ (back slash),^ (carat), " (double quote), / (forward slash), > (greater than), < (lessthan), or ' (single quote).

Name field

The user-defined description of the distributed virtual switch.

Enter up to 256 characters. You can use any characters or spacesexcept ` (accent mark), \ (backslash), ^ (carat), " (double quote), =(equal sign), > (greater than), < (less than), or ' (single quote).

Description field

This can be one of the following:

• Enabled

• Disabled

If you disable the DVS, Cisco UCS Manager does not push anyconfiguration changes related to the DVS to VMware vCenter.

Admin State field

c) Click OK.

Step 7 Click Finish if you have finished adding all folders and distributed virtual switches to the datacenter.You may need to click Finish more than once to exit the wizard. You can stop at any page to add anotherfolder or DVS to the datacenter.

Adding a Folder to a Datacenter

Procedure

Step 1 In the Navigation pane, click the VM tab.Step 2 On the VM tab, expand the VMWare node.Step 3 Expand the vCenter that includes the datacenter to which you want to add a folder.Step 4 Right-click the datacenter to which you want to add a folder and choose Create Folder.Step 5 On the Create Folder page, do the following to add a folder to the datacenter:

a) Complete the following fields:

Cisco UCS Manager VM-FEX for VMware GUI Configuration Guide OL-25368-01 51

Configuring Distributed Virtual Switches in Cisco UCSAdding a Folder to a Datacenter

Page 62: VMware VM-FEX UCS Configuration Guide

DescriptionName

The name of the vCenter folder.

This name can be between 1 and 16 characters. You can use spacesand any other ASCII characters except for ` (accent), \ (back slash),^ (carat), " (double quote), / (forward slash), > (greater than), < (lessthan), or ' (single quote).

Name field

A user-defined description of the folder.

Enter up to 256 characters. You can use any characters or spacesexcept ` (accent mark), \ (backslash), ^ (carat), " (double quote), =(equal sign), > (greater than), < (less than), or ' (single quote).

Description field

b) • Click Next and continue with Step 6 to create a DVS in the folder.

• Continue with Step 7 if you do not want to create a DVS in the folder.

Step 6 On the Create Distributed Virtual Switches page, do the following to create a distributed virtual switch inthe folder:a) Click Add to add a distributed virtual switch to the folder.b) In the Create Distributed Virtual Switches dialog box, complete the following fields:

DescriptionName

The name of the distributed virtual switch.

This name can be between 1 and 16 characters. You can use spacesand any other ASCII characters except for ` (accent), \ (back slash),^ (carat), " (double quote), / (forward slash), > (greater than), < (lessthan), or ' (single quote).

Name field

The user-defined description of the distributed virtual switch.

Enter up to 256 characters. You can use any characters or spacesexcept ` (accent mark), \ (backslash), ^ (carat), " (double quote), =(equal sign), > (greater than), < (less than), or ' (single quote).

Description field

This can be one of the following:

• Enabled

• Disabled

If you disable the DVS, Cisco UCS Manager does not push anyconfiguration changes related to the DVS to VMware vCenter.

Admin State field

c) Click OK.

Step 7 Click Finish if you have finished adding all folders and DVSes to the datacenter.

Cisco UCS Manager VM-FEX for VMware GUI Configuration Guide52 OL-25368-01

Configuring Distributed Virtual Switches in Cisco UCSAdding a Folder to a Datacenter

Page 63: VMware VM-FEX UCS Configuration Guide

You may need to click Finish more than once to exit the wizard. You can stop at any page to add anotherfolder or DVS.

Deleting a Folder from a vCenterIf the folder contains a datacenter, Cisco UCSManager also deletes that datacenter and any folders and DVSesit contains.

Procedure

Step 1 In the Navigation pane, click the VM tab.Step 2 On the VM tab, expand All > VMWare.Step 3 Expand the node for the vCenter that contains the folder you want to delete.Step 4 Right-click the folder and choose Delete.Step 5 If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes.

Deleting a DatacenterIf the datacenter contains a folder, Cisco UCS Manager also deletes that folder and any DVS it contains.

Procedure

Step 1 In the Navigation pane, click the VM tab.Step 2 On the VM tab, expand All > VMWare.Step 3 If the datacenter that you want to delete is contained in a higher level folder, expand the node for that folder.Step 4 Right-click the datacenter and choose Delete.Step 5 If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes.

Deleting a Folder from a DatacenterIf the folder contains a DVS, Cisco UCS Manager also deletes that DVS.

Cisco UCS Manager VM-FEX for VMware GUI Configuration Guide OL-25368-01 53

Configuring Distributed Virtual Switches in Cisco UCSDeleting a Folder from a vCenter

Page 64: VMware VM-FEX UCS Configuration Guide

Procedure

Step 1 In the Navigation pane, click the VM tab.Step 2 On the VM tab, expand All > VMWare.Step 3 If the datacenter that you want to modify is contained in a higher level folder, expand the node for that folder.Step 4 Expand the node for the datacenter that contains the folder you want to delete.Step 5 Right-click the folder and choose Delete.Step 6 If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes.

Cisco UCS Manager VM-FEX for VMware GUI Configuration Guide54 OL-25368-01

Configuring Distributed Virtual Switches in Cisco UCSDeleting a Folder from a Datacenter

Page 65: VMware VM-FEX UCS Configuration Guide

C H A P T E R 7Configuring Port Profiles

This chapter includes the following sections:

• Port Profiles, page 55

• Creating a Port Profile, page 56

• Modifying the VLANs in a Port Profile, page 57

• Changing the Native VLAN for a Port Profile, page 58

• Adding a VLAN to a Port Profile, page 58

• Removing a VLAN from a Port Profile, page 59

• Deleting a Port Profile, page 59

• Port Profile Clients, page 59

• Creating a Profile Client, page 60

• Modifying a Profile Client, page 60

• Deleting a Profile Client, page 61

Port ProfilesPort profiles contain the properties and settings that you can use to configure virtual interfaces in Cisco UCSfor VM-FEX. The port profiles are created and administered in Cisco UCS Manager. After a port profile iscreated, assigned to, and actively used by one or more DVSes, any changes made to the networking propertiesof the port profile in Cisco UCS Manager are immediately applied to those DVSes.

In VMware vCenter, a port profile is represented as a port group. Cisco UCSManager pushes the port profilenames to VMware vCenter, which displays the names as port groups. None of the specific networking propertiesor settings in the port profile are visible in VMware vCenter. You must configure at least one port profileclient for a port profile if you want Cisco UCS Manager to push the port profile to VMware vCenter.

Cisco UCS Manager VM-FEX for VMware GUI Configuration Guide OL-25368-01 55

Page 66: VMware VM-FEX UCS Configuration Guide

Creating a Port Profile

If you are configuring VMDirectPath Gen 2, you need to set the Host Network IO Performance fieldto High Performance.

Note

Procedure

Step 1 In the Navigation pane, click the VM tab.Step 2 On the VM tab, expand the All node.Step 3 Right-click the Port Profiles node and choose Create Port Profile.Step 4 In the Create Port Profile dialog box, complete the following fields:

DescriptionName

The user-defined name for the port profile.

This name can be between 1 and 31 ASCII alphanumeric characters.You cannot use spaces or any special characters other than - (hyphen),_ (underscore), and : (colon), and you cannot change this name afterthe object has been saved.

Name field

The user-defined description for the port profile.

Enter up to 256 characters. You can use any characters or spaces except` (accent mark), \ (backslash), ^ (carat), " (double quote), = (equal sign),> (greater than), < (less than), or ' (single quote).

Description field

The quality of service policy associated with this port profile.QoS Policy drop-down list

The network control policy associated with this port profile.Network Control Policydrop-down list

The maximum number of ports that can be associated with this portprofile. The default is 64 ports.

The maximum number of ports that can be associated with a singledistributed virtual switch (DVS) is 4096. If the DVS has only oneassociated port profile, that port profile can be configured with up to4096 ports. However, if the DVS has more than one associated portprofile, the total number of ports associated with all of those port profilescombined cannot exceed 4096.

Max Ports field

Cisco UCS Manager VM-FEX for VMware GUI Configuration Guide56 OL-25368-01

Configuring Port ProfilesCreating a Port Profile

Page 67: VMware VM-FEX UCS Configuration Guide

DescriptionName

This can be one of the following:

• None—Traffic to and from a virtual machine passes through theDVS.

• High Performance— Traffic to and from a virtual machinebypasses the DVS and hypervisor and travels directly between thevirtual machines and a virtual interface card (VIC) adapter.

Host Network IO Performancefield

The pin group associated with this port profile.Pin Group drop-down list

Step 5 In the VLANs area, complete the following fields:DescriptionName

Check the check box in this column for each VLAN that you want touse.

Select column

The name of the VLAN.Name column

To designate one of the VLANs as the native VLAN, click the radiobutton in this column.

Native VLAN column

Step 6 Click OK.

Modifying the VLANs in a Port ProfileProcedure

Step 1 In the Navigation pane, click the VM tab.Step 2 On the VM tab, expand All > Port Profiles.Step 3 Right-click the port profile for which you want to modify the VLANs and chooseModify VLANs.Step 4 In theModify VLANs dialog box, change one or more of the following:

DescriptionName

Check the check box in this column for each VLAN that you want touse.

Select column

The name of the VLAN.Name column

Cisco UCS Manager VM-FEX for VMware GUI Configuration Guide OL-25368-01 57

Configuring Port ProfilesModifying the VLANs in a Port Profile

Page 68: VMware VM-FEX UCS Configuration Guide

DescriptionName

To designate one of the VLANs as the native VLAN, click the radiobutton in this column.

Native VLAN column

Click this link if you want to create a VLAN.Create VLAN link

Step 5 Click OK.

Changing the Native VLAN for a Port ProfileProcedure

Step 1 In the Navigation pane, click the VM tab.Step 2 On the VM tab, expand All > Port Profiles.Step 3 Right-click the port profile for which you want to change the native VLAN and chooseModify VLANs.Step 4 In theModify VLANs dialog box, do the following:

a) In the Native VLAN column, click the radio button in the row for the VLAN that you want to becomethe native VLAN.

b) Click OK.

Adding a VLAN to a Port ProfileProcedure

Step 1 In the Navigation pane, click the VM tab.Step 2 On the VM tab, expand All > Port Profiles.Step 3 Right-click the port profile to which you want to add a VLAN and chooseModify VLANs.Step 4 In theModify VLANs dialog box, do the following:

a) In the Select column, check the check box in the row for the VLAN that you want to add to the port profile.b) (Optional) If you want this VLAN to be the native VLAN, click the radio button in the Native VLAN

column.c) Click OK.

Cisco UCS Manager VM-FEX for VMware GUI Configuration Guide58 OL-25368-01

Configuring Port ProfilesChanging the Native VLAN for a Port Profile

Page 69: VMware VM-FEX UCS Configuration Guide

Removing a VLAN from a Port ProfileYou can remove a VLAN from a port profile or change the VLAN that you have assigned as the native VLAN.

Procedure

Step 1 In the Navigation pane, click the VM tab.Step 2 On the VM tab, expand All > Port Profiles.Step 3 Right-click the port profile from which you want to remove a VLAN and chooseModify VLANs.Step 4 In theModify VLANs dialog box, do the following:

a) In the Select column, uncheck the check box in the row for the VLAN that you want to remove from theport profile.

b) (Optional) You can change the native VLAN to a different VLAN by clicking the radio button in theNative VLAN column for a different VLAN.

c) Click OK.

Deleting a Port ProfileYou cannot delete a port profile if a VM is actively using that port profile.

Procedure

Step 1 In the Navigation pane, click the VM tab.Step 2 On the VM tab, expand All > Port Profiles.Step 3 Right-click the port profile you want to delete and choose Delete.Step 4 If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes.Step 5 Click OK.

Cisco UCS Manager deletes the port profile and all associated port profile clients.

Port Profile ClientsThe port profile client determines the DVSes to which a port profile is applied. By default, the port profileclient specifies that the associated port profile applies to all DVSes in the VMware vCenter. However, youcan configure the client to apply the port profile to all DVSes in a specific datacenter or datacenter folder oronly to one DVS.

Cisco UCS Manager VM-FEX for VMware GUI Configuration Guide OL-25368-01 59

Configuring Port ProfilesRemoving a VLAN from a Port Profile

Page 70: VMware VM-FEX UCS Configuration Guide

Creating a Profile ClientYou can create a profile client.

Procedure

Step 1 In the Navigation pane, click the VM tab.Step 2 On the VM tab, expand All > Port Profiles.Step 3 Right-click the port profile for which you want to create a profile client and choose Create Profile Client.Step 4 In the Create Profile Client dialog box, complete the following fields:

DescriptionName

The user-defined name for the profile client.

This name can be between 1 and 16 ASCII alphanumeric characters.You cannot use spaces or any special characters other than - (hyphen),_ (underscore), and : (colon), and you cannot change this name afterthe object has been saved.

Name field

The user-defined description of the client.

Enter up to 256 characters. You can use any characters or spaces except` (accent mark), \ (backslash), ^ (carat), " (double quote), = (equal sign),> (greater than), < (less than), or ' (single quote).

Description field

Choose a datacenter from the drop-down list or chooseAll if this profileclient applies to all datacenters.

Datacenter drop-down list

Choose a folder from the drop-down list or choose All if this profileclient applies to all folders.

Folder drop-down list

Choose a virtual switch from the drop-down list or choose All if thisprofile client applies to all virtual switches.

Distributed Virtual Switchdrop-down list

Step 5 Click OK.

What to Do Next

Complete the configuration of the virtual machines in VMware vCenter.

Modifying a Profile ClientYou can modify a profile client.

Cisco UCS Manager VM-FEX for VMware GUI Configuration Guide60 OL-25368-01

Configuring Port ProfilesCreating a Profile Client

Page 71: VMware VM-FEX UCS Configuration Guide

Procedure

Step 1 In the Navigation pane, click the VM tab.Step 2 On the VM tab, expand All > Port Profiles.Step 3 Click the port profile for which you want to modify the profile client.Step 4 In theWork pane, click the Profile Clients tab.Step 5 Right-click the profile client you want to modify and choose Show Navigator.Step 6 In the Navigator for the profile client, change the values for one or more of the following fields:

DescriptionName

The user-defined name for the profile client.Name field

The user-defined description of the client.

Enter up to 256 characters. You can use any characters or spaces except` (accent mark), \ (backslash), ^ (carat), " (double quote), = (equal sign),> (greater than), < (less than), or ' (single quote).

Description field

A regular expression used to select the appropriate datacenter.Datacenter field

A regular expression used to select the appropriate datacenter folder.Folder field

A regular expression used to select the appropriate virtual switch.Distributed Virtual Switch field

Step 7 Click OK.

Deleting a Profile ClientYou cannot delete a port profile client if a VM is actively using the port profile with which the client isassociated.

Procedure

Step 1 In the Navigation pane, click the VM tab.Step 2 On the VM tab, expand All > Port Profiles.Step 3 Click the port profile from which you want to delete a profile client.Step 4 In theWork pane, click the Profile Clients tab.Step 5 Right-click the profile client that you want to delete and choose Delete.Step 6 If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes.Step 7 Click Save Changes.

Cisco UCS Manager VM-FEX for VMware GUI Configuration Guide OL-25368-01 61

Configuring Port ProfilesDeleting a Profile Client

Page 72: VMware VM-FEX UCS Configuration Guide

Cisco UCS Manager VM-FEX for VMware GUI Configuration Guide62 OL-25368-01

Configuring Port ProfilesDeleting a Profile Client

Page 73: VMware VM-FEX UCS Configuration Guide

C H A P T E R 8Managing Pending Deletions of DistributedVirtual Switches

This chapter includes the following sections:

• Pending Deletions of Distributed Virtual Switches, page 63

• Viewing Pending Deletions, page 64

• Changing the Properties of a Pending Deletion, page 64

• Deleting a Pending Deletion, page 65

Pending Deletions of Distributed Virtual SwitchesWhen you delete a distributed virtual switch (DVS) from Cisco UCSManager, either explicitly or by deletingany parent object in the hierarchy, Cisco UCS Manager initiates a connection with VMware vCenter to startthe process of deleting the DVS. Until the DVS is successfully deleted from VMware vCenter, Cisco UCSManager places the DVS in a pending deletion list.

However, Cisco UCS Manager cannot successfully delete a DVS from VMware vCenter if certain situationsoccur, including the following:

• VMware vCenter database was corrupted

• VMware vCenter was uninstalled

• The IP address for VMware vCenter was changed

If the DVS cannot be successfully deleted from VMware vCenter, the DVS remains in the pending deletionlist until the pending deletion is deleted in Cisco UCS Manager or the properties for that pending deletion arechanged in a way that allows the DVS to be successfully deleted from VMware vCenter. When you delete apending deletion, the DVS is deleted from Cisco UCS Manager but is not deleted from VMware vCenter. Ifthe DVS remains in VMware vCenter, you must delete the DVS manually.

You can view the pending deletion list, delete a pending deletion, or change the properties for a pendingdeletion in Cisco UCS Manager. For example, you can correct the VMware vCenter IP address for a pendingdeletion so that Cisco UCSManager can successfully initiate a connection and delete the DVS from VMwarevCenter. You cannot cancel the deletion of a DVS from Cisco UCS Manager.

Cisco UCS Manager VM-FEX for VMware GUI Configuration Guide OL-25368-01 63

Page 74: VMware VM-FEX UCS Configuration Guide

Viewing Pending DeletionsProcedure

Step 1 In the Navigation pane, click the VM tab.Step 2 On the VM tab, expand the All node.Step 3 On the VM tab, click VMWare.Step 4 In theWork pane, click the Deletion Tasks tab.

Changing the Properties of a Pending DeletionYou can change the properties of a pending deletion, if necessary, to ensure that Cisco UCS Manager cansuccessfully initiate a connection and delete the DVS from VMware vCenter.

Procedure

Step 1 In the Navigation pane, click the VM tab.Step 2 On the VM tab, expand the All node.Step 3 On the VM tab, click VMWare.Step 4 In theWork pane, click the Deletion Tasks tab.Step 5 Click the pending deletion for which you want to change the properties.Step 6 Right-click the pending deletion and choose Show Navigator.Step 7 In the Properties dialog box, change one or more of the following properties to ensure that Cisco UCS

Manager can connect to VMware vCenter:DescriptionName

The host on which the datacenter resides.Hostname field

The name of the datacenter.Datacenter field

The datacenter protocol.Protocol field

The folder that is to be deleted.Folder field

Step 8 Click OK.Cisco UCS Manager attempts to connect with VMware vCenter and delete the DVS.

Cisco UCS Manager VM-FEX for VMware GUI Configuration Guide64 OL-25368-01

Managing Pending Deletions of Distributed Virtual SwitchesViewing Pending Deletions

Page 75: VMware VM-FEX UCS Configuration Guide

Deleting a Pending DeletionWhen you delete a pending deletion, the DVS is deleted from Cisco UCS Manager but is not deleted fromVMware vCenter. If the DVS remains in VMware vCenter, you must delete the DVS manually.

Procedure

Step 1 In the Navigation pane, click the VM tab.Step 2 On the VM tab, expand the All node.Step 3 On the VM tab, click VMWare.Step 4 In theWork pane, click the Deletion Tasks tab.Step 5 Click the pending deletion that you want to delete.Step 6 Right-click the pending deletion and choose Delete.Step 7 If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes.

Cisco UCS Manager VM-FEX for VMware GUI Configuration Guide OL-25368-01 65

Managing Pending Deletions of Distributed Virtual SwitchesDeleting a Pending Deletion

Page 76: VMware VM-FEX UCS Configuration Guide

Cisco UCS Manager VM-FEX for VMware GUI Configuration Guide66 OL-25368-01

Managing Pending Deletions of Distributed Virtual SwitchesDeleting a Pending Deletion

Page 77: VMware VM-FEX UCS Configuration Guide

I N D E X

A

adapters 2NIC 2VIC 2virtualization 2

B

BIOS 17creating policy 17

C

certificate 39, 40VM-FEX 40VN-Link in hardware 39

creating 39Cisco UCS 3

Cisco M81KR VIC 3Cisco UCS Manager 3, 4

components 4Cisco VEM software bundle 27

uninstalling 27Cisco VM-FEX 1components 3Configure VMware Integration 29

wizard 29converged network adapters 2

virtualization 2

D

datacenters 49, 53adding to vCenters 49deleting 53deleting folders 53

deletion tasks 63, 64, 65about 63changing properties 64deleting 65viewing 64

distributed virtual switches 4, 43definition 4

DVS 4, 44configuring 44definition 4

dynamic vNIC 15viewing properties 15

dynamic vNIC connection policy 12, 13, 14about 12changing 13creating 12deleting 14

E

ESX 5.0 23upgrade procedure 23

ESX 5.1 24upgrade procedure 24

ESX software 3ESX/ESXi hosts 21

upgrading with Cisco VEM software bundle using CLI 21Ethernet adapter policies 11

modifying 11exporting 38

extension files 38extension files 37, 38

exporting 38modifying key 37

extension key 3, 4definition 4

external virtualization manager 3

Cisco UCS Manager VM-FEX for VMware GUI Configuration Guide OL-25368-01 IN-1

Page 78: VMware VM-FEX UCS Configuration Guide

F

folders 47, 51, 53adding to datacenters 51adding to vCenter 47deleting 53

H

high-performance mode 7hosts 23, 24

upgrading to ESXi 5.0 with Cisco VEM software bundle 23upgrading to ESXi 5.1 with Cisco VEM software bundle 24

hypervisor host 3, 6VMware ESX host 6

definition 6

I

IEEE 802.1Qbh 1

M

modes 7high-performance 7standard 7

modifying extension key 37

N

NIC adapters 2virtualization 2

P

Palo adapter 37, 38extension files 37, 38

exporting 38modifying key 37

pending deletions 63, 64, 65about 63changing properties 64deleting 65viewing 64

policies 4, 12, 13, 14, 15, 16, 17BIOS 17dynamic vNIC connection 12, 13, 14

about 12

policies (continued)dynamic vNIC connection (continued)

changing 13creating 12deleting 14

VM lifecycle 15, 16VM-FEX for VMware 4

port profile 4definition 4

port profile client 4definition 4

port profiles 55, 56, 57, 58, 59, 60, 61about 55adding VLANs 58, 59changing native VLAN 58clients 59creating 56creating profile clients 60deleting 59deleting profile clients 61modifying profile clients 60modifying VLANs 57

profile clients 60, 61creating 60deleting 61modifying 60

profiles 55, 59port 55, 59

S

servers 17BIOS policy 17

software 19VEM bundle installation 19virtual interface cards 19

VEM bundle installation on 19standard mode 7switches 43

distributed virtual switches 43DVSes 43

T

traffic 7standard mode 7

Cisco UCS Manager VM-FEX for VMware GUI Configuration GuideIN-2 OL-25368-01

Index

Page 79: VMware VM-FEX UCS Configuration Guide

V

vCenters 47, 49, 51, 53adding datacenters 49adding folders 47, 51deleting folders 53

VEM 27uninstalling 27

VEM bundle 3VEM software bundle 19, 21, 23, 24

prerequisites 19upgrading on ESX/ESXi hosts using CLI 21upgrading with ESXi 5.0 23upgrading with ESXi 5.1 24

VEM software bundle installation 20using VUM 20

VEM software installation 19introduction 19

VIC adapters 2virtualization 2

virtual machines 1virtualization 1, 2, 3, 6, 15, 16, 37, 38, 39, 40, 63, 64

about 1components 3

Cisco UCS Manager 3extension key 3external virtualization manager 3hypervisor host 3

converged network adapters 2NIC adapters 2Palo adapter 37, 38

extension file 38extension key 37

VIC adapter 2VM lifecycle policy 15, 16VM-FEX 1, 40, 64

about 1copying certificate 40

virtualization (continued)VM-FEX (continued)

deletion tasks 64VN-Link in hardware 39, 63

certificate 39pending deletions 63

virtualization manager 6VMware vCenter 6

definition 6VM lifecycle policy 15, 16

about 15configuring 16

VM-FEX 1, 6, 40, 59, 64about 1, 6copying certificate 40pending deletions 64port profiles 59

VMware 6, 37, 38components 6extension files 38extension key 37

VMware ESX host 6definition 6

VMware ESX software 3VMware vCenter 6

definition 6VMware, configuring integration 29VN-Link in hardware 39, 63

certificate 39creating 39

pending deletions 63VN-Link in Harware 29

configuring with wizard 29vNICs 12, 15

dynamic vNIC connection policy 12viewing dynamic vNIC properties 15

VUM 20using to install VEM software bundle 20

Cisco UCS Manager VM-FEX for VMware GUI Configuration Guide OL-25368-01 IN-3

Index

Page 80: VMware VM-FEX UCS Configuration Guide

Cisco UCS Manager VM-FEX for VMware GUI Configuration GuideIN-4 OL-25368-01

Index