View Cart
0 Items | Total: US$0.00
Welcome,      Register

You are here

RS0020 - Nexus 1000V Layer 3 VSM VEM Installation (Manual and VUM) (Part 1)

Rating: 
5
Average: 5 (2 votes)
Difficulty Level: 
0
Lab Document: 
<Please login to see the content>

The video walks you through Cisco Nexus 1000V installation in Layer 3 mode. We will explore various methods to install both VSM and VEM so you can be aware of steps involved and determine which method will work best in your deployment. This lab takes what we have discussed on the Nexus 1000V introduction video, and applies them into actual implementation. 

In part 1, we will be installing VSM from an .ova file and configure port-profiles.
You can also find detailed discussion on deployment options and more extensive comparison between Layer 2 and Layer 3 mode at the link below.
 
Topic includes
  • Nexus 1000V Layer 3 Mode
  • VSM Install
    • Primary VSM using OVA (Manually Configure) 
    • Secondary VSM using OVA (Nexus 1000V Secondary)
  • VEM Install (Manual and VMware Update Manager)
  • Port-Profile
  • Control, Management VLAN
  • System Vlan
  • VEM Control (VMkernel) Interface with 'capability l3control'
Prerequisite
  • ESXi Hosts Added to vCenter
  • VMware Update Manager Installed
  • Download N1KV Software Package from cisco.com
  • Installation Parameters
    • vCenter - IP, Username,Password
    • N1KV - Hostname, Password, Mgmt IP, Subnet, GW,(Crtl,Mgmt) Vlan, Domain ID, Layer2/3 etc.

About Author

Metha Cheiwanichakorn, CCIE#23585 (RS, Sec, SP), is a Cisco networking enthusiast with years of experience in the industry. He is currently working as a consulting engineer for a Cisco partner. As a founder of and an instructor at labminutes.com, Metha enjoys learning and challenges himself with new Cisco technologies.

2 comments

amazing tutorial. one thing i got stack at... how to have on a newly created vmkernel gateway different from that on the management vmkernel (in the video right at the last minute) for Control routable vmkernel.

You will find that changing VMkernel DGW effect other VMkernel interfaces like management as well (so be careful as you might lose connectivity to it). You can just leave it alone and if you test, it should work just fine and even be able to ping the IP from a different subnet. Not exactly sure how it works. I can only guess that it uses proxy ARP.

Lab Minutes Classifieds