Once the configuration on Cisco VIC adapter is done, we need to do certain configuration settings on Nexus switch to enable VM-FEX. In this section we discuss more on the configuration settings that needs to be done specifically on on Nexus 5000 Series switch to enable VM-FEX. We also discuss on settings that needs to be done on ESXi to enable VMFEX.
A VM-FEX license is required for Cisco Nexus device. The license package name is VMFEX_ FEATURE_PKG. Incase if you are just interested in experimenting with this cool feature, a grace period of 120 days starts when you first configure this feature.
We have to do the following configuration on Nexus 5000 switch:
- Enable VM-FEX and other related services
- Define port profiles for dynamic Virtual Machine ports
- Enable vntag on applicable ports
- Install Cisco_nexus_vmfex plugin in vCenter
- Configure SVS connection to vCenter
- Activate and verify the SVS connection
Sick and tired of managing physical and virtual network for your data center from different management interfaces? VMFEX is Cisco’s answer to your problem. Cisco Virtual Machine Fabric Extender (VM-FEX) technology extends cisco’s fabric extender technology to virtual machines. In simpler words, with VMFEX you will be able to manage both physical and virtual network ports from your Nexus 5000.
The objective of this article is to help users setup a VMFEX solution very easily in their virtualized environment with Cisco Rack Servers. This document has been divided into 3 parts.
Part 1: Introduction and VIC configurations
Part2: Nexus 5000 configuration
Part 3: ESXi and vCenter configuration
By default there is no NTP client installed in vSphere Management Assistannt 5.0. This post contais the steps for installing and configuring NTP client in vMA 5.0. Login to the vMA admin portal from browser and configure the proxy if … Continue reading