Understand Cisco Nexus 1000v deployment and other components – Part 2

Welcome !

Flashback, have a cluster with two nodes and also i added addition standalone ESXi to view it clearly all environment.

Screen Shot 2013-01-15 at 9.16.25 PM

Some documents and videos are old or a few new installations guides are available on cisco but on community very good articles are there i will also add it end of the this article

Okay, go nexus installer up should be on C:\Users\Administrator\Downloads\Nexus1000v.4.2.1.SV1.5.2b\Nexus1000v.4.2.1.SV1.5.2b\VSM\Installer_App folder which name is Nexus1000V-install.jar

I expect that you installed 64 bit java and java.exe is under C:\Program Files\Java\jre7\bin , then run command line tool and go inside related java folder and execute the command

“C:\Program Files\Java\jre7\bin>java -jar C:\Users\Administrator\Downloads\Nexus1000v.4.2.1.SV1.5.2b\Nexus1000v.4.2.1.SV1.5.2b\VSM\Installer_App\Nexus1000V-install.jar VSM”

Log in credentials for install connect vCenter to install VSM

Screen Shot 2013-01-15 at 9.40.22 PM

Choose where to deploy

Screen Shot 2013-01-15 at 9.41.31 PM

Your VSM ova file should be under related folders


First i would like to install standalone and then i will implement second one, give the name of VM and choose the datastore to deploy

Screen Shot 2013-01-15 at 9.51.46 PM

From articles i learned that for debugging purpose its better to use L3 mode and i told you i would like to put VSM on separate vlan and because of ip connectivity enough then if my VEMs can reach the VSM then everything is okay. Also on this configuration i did not choose the control port for L3 connectivity will check the requirement next

Screen Shot 2013-01-15 at 9.57.24 PM

Give a name to your baby, admin pass like 12qwaszxcv!A because of password policy,ip address , mask, gw , domain id and choose the DC and set the native vlan id.

Good explanation about what is native vlan from IBM http://publib.boulder.ibm.com/infocenter/zvm/v5r4/index.jsp?topic=/com.ibm.zvm.v54.hcpa6/hcsc9b3181.htm

Domain id is a tag to understand or to be sure that right VSM and VEM are talking each other, if VEM and VSM domain id different then control packages or communications are dropped.

Screen Shot 2013-01-15 at 10.05.48 PM

Review screen will be appear, no need a screenshot pls check and confirm and go installing ……

Screen Shot 2013-01-15 at 10.10.36 PM

You can check it the installation also from vCenter

Screen Shot 2013-01-15 at 10.11.50 PM

You can check the connectivity

Screen Shot 2013-01-15 at 10.13.04 PM

if you need to migrate something you can go on , but i do not think it

Screen Shot 2013-01-15 at 10.15.05 PM

Click finish and the see the summary of installation and close the window and lets switch to VEM installation
Check the VEMs are already installed or not ! Try ssh you ESXi node, if you an error okay VEM is not installed on ESXi nodes

VMware offers supported, powerful system administration tools.  Please
see http://www.vmware.com/go/sysadmintools for details.

The ESXi Shell can be disabled by an administrative user. See the
vSphere Security documentation for more information.
~ # vem status
-sh: vem: not found
~ #

Before past to the installation need to be something modify, flashback again , previous article i have a screenshot of ESXi nodes networking

Screen Shot 2013-01-15 at 10.26.45 PM

Now i created extra VMK Port which name is nexusvmk we will use it later to move such VMK to Nexus distributed switch port group, i did it also on other node too ! if you want completely you can separate the pNIC for VSM to VEM communication on ESXi.

Screen Shot 2013-01-15 at 10.35.59 PM

Lets continue the installation of the VEM

“C:\Program Files\Java\jre7\bin>java -jar C:\Users\Administrator\Downloads\Nexus1000v.4.2.1.SV1.5.2b\Nexus1000v.4.2.1.SV1.5.2b\VSM\Installer_App\Nexus1000V-install.jar VEM”

Type again vCenter credentials , no need to screenshot and then type the VSM credential

Screen Shot 2013-01-15 at 10.47.46 PM

Choose the hosts want to install/deploy the VEM

Screen Shot 2013-01-15 at 10.48.36 PM

Check the summary and click finish

I got an error about installation failed and provided log files find that error is SEVERE: Compatible vib not found on VSM and on community one of the question is unanswered https://communities.cisco.com/message/110675  okay don’t worry about it 😀

I have a update manager 😀  instead of ability to install the VEM vib via CLI i will show you the update manager, maybe its help to you for other kind of installations anybody want to install vib from cli

Go to vCenter home and click Update Manager

Screen Shot 2013-01-16 at 7.42.16 PM

Select Patch Repository and click Import Patch

Screen Shot 2013-01-16 at 7.43.07 PM

Click browse and choose the related VSM for related ESXi version, its under VEM folder

Screen Shot 2013-01-16 at 7.46.16 PM

Patch upload process will be begun

Screen Shot 2013-01-16 at 7.46.33 PM

Pls look the type its a exrenstion

Screen Shot 2013-01-16 at 7.46.45 PM

Now need to create a baseline to apply it to ESXi host for install VEM

Screen Shot 2013-01-16 at 7.42.28 PM

Pls set a name to baseline and type as a externsion

Screen Shot 2013-01-16 at 7.42.45 PM

Pls filter the extensions like below

Screen Shot 2013-01-16 at 7.47.36 PM

Add it

Screen Shot 2013-01-16 at 7.47.58 PM


Screen Shot 2013-01-16 at 7.48.05 PM

and Next after this process over need to assign such baseline to all ESXi nodes via cluster or one by one

Go to one of host last tab and click attach to set the baseline

Screen Shot 2013-01-16 at 7.48.23 PM

Select the baseline what we created , sorry for mismatch i was get the screenshot before as a baseline Install VEM but this is Install , sorry for bad screenshots 😦

Screen Shot 2013-01-16 at 7.48.53 PM

Looks like its attached

Screen Shot 2013-01-16 at 7.49.01 PM

And lest step pls remediate it

Screen Shot 2013-01-16 at 7.49.12 PM

Select the patch

Screen Shot 2013-01-16 at 7.49.20 PM

Select immediately

Screen Shot 2013-01-16 at 7.49.27 PM

Noting to enter maintenance mode , click next

Screen Shot 2013-01-16 at 7.49.34 PM

Some checkboxes are not selected pls fallow the screenshot

Screen Shot 2013-01-16 at 7.49.44 PM

And thats it click finish and fallow the task manager of vCenter

Screen Shot 2013-01-16 at 7.49.50 PM

Now connect to the one of the node to SSH and check the VEM status , if vem agent is running then okay it loaded

Screen Shot 2013-01-17 at 12.06.36 AM

Back to the VSM for shortly , type the command below, VSM is active its on first module and right now no extra module was there

MYVSM# show module

Screen Shot 2013-01-17 at 12.08.20 AM

Check any VEM are missing, of course for now nothing should be missed but such command very important for debug

MYVSM# show module vem missing
No missing module found.

Forgot to check VSM what did when its installed on vCenter , nothing to care about for now, we will create everything ourself

Screen Shot 2013-01-17 at 12.15.11 AM

Now, we need to configure virtual distributed switch, physically every switch should  have a uplink 🙂 to communicate out side
Lets create uplink via VSM , i’m not a network guy but looks like very easy

First pls check the vlans are setted or not

MYVSM# show vlan VLAN

Name Status Ports

—- ——————————– ——— ——————————-

1 default active

770 VLAN0770 active


—- —–

1 enet

770 enet



Primary Secondary Type Ports

——- ——— ————— ——————————————-

Lets add the vLAN 773. In my config, remember nexusvmk on each ESXi nodes should communicate with VSM.

MYVSM# CONfigure T

Enter configuration commands, one per line. End with CNTL/Z.

MYVSM(config)# VLan 773

MYVSM(config-vlan)# name nexusvmkonescinodes

Configure Uplink 🙂  Flashback, i used system clan  773 because ESXi node VSM communcaiton vlan is it and have to specify as a system vlan for provide ability to communicate VEM with VSM when ESXi booted.

MYVSM# configure t
Enter configuration commands, one per line. End with CNTL/Z.

MYVSM(config)# port-profile type ethernet uplink

MYVSM(config-port-prof)# vmware port-group

MYVSM(config-port-prof)# switchport mode trunk MYVSM(config-port-prof)# switchport trunk allowed vlan all

MYVSM(config-port-prof)# switchport mode access

MYVSM(config-port-prof)# no shutdown

MYVSM(config-port-prof)# system vlan 773

MYVSM(config-port-prof)# state enabled

Check the vCenter Networking section, uplink is there 😀

Screen Shot 2013-01-17 at 1.05.26 AM

Lets create a portgroup to connect nexusvmk interfaces there to communicate VEMs to VSM

MYVSM(config)# port-profile type vethernet l3control773

MYVSM(config-port-prof)# switchport mode access

MYVSM(config-port-prof)# switchport access vlan 773

MYVSM(config-port-prof)# vmware port-group

MYVSM(config-port-prof)# no shutdown

MYVSM(config-port-prof)# capability l3control

Warning: Port-profile ‘l3control773’ is configured with ‘capability l3control’. Also configure the corresponding access vlan as a system vlan in: * Port-profile ‘l3control773’. * Uplink port-profiles that are configured to carry the vlan MYVSM(config-port-prof)# 2013 Jan 17 08:06:00 MYVSM %MSP-1-CAP_L3_CONTROL_CONFIGURED: Profile is configured with capability l3control. Also configure the corresponding VLAN as system VLAN in this port-profile and uplink port-profiles that are configured to carry the VLAN to ensure no traffic loss.

MYVSM(config-port-prof)# system vlan 773

MYVSM(config-port-prof)# state enabled

Okay lets join the ESXi nodes to Cisco Nexus Distributed Switch

Screen Shot 2013-01-17 at 1.15.02 AM

Choose the NICs which are will be uplink for ESXi node and which uplink profile we should add , here it is uplink port profile

Screen Shot 2013-01-17 at 1.16.48 AM

Still i can not understand if everything is working L3 mode then why need to migrate VMK interface to created vmware port-group which name is l3control773

Screen Shot 2013-01-17 at 1.17.54 AM

Overview and its okay.

Screen Shot 2013-01-17 at 1.18.23 AM

You have to get such notification(s) on console of VSM

MYVSM(config-port-prof)# 2013 Jan 17 08:15:52 MYVSM %VEM_MGR-2-VEM_MGR_DETECTED: Host nn1 detected as module 3 2013 Jan 17 08:15:52 MYVSM %VEM_MGR-2-MOD_ONLINE: Module 3 is online

MYVSM# 2013 Jan 17 08:19:19 MYVSM %VEM_MGR-2-VEM_MGR_DETECTED: Host nn2 detected as module 4 2013 Jan 17 08:19:19 MYVSM %VEM_MGR-2-MOD_ONLINE: Module 4 is online

Check the modules

MYVSM# show module

Mod Ports Module-Type Model Status

— —– ——————————– —————— ————

1 0 Virtual Supervisor Module Nexus1000V active *

3 248 Virtual Ethernet Module NA ok

4 248 Virtual Ethernet Module NA ok

Mod Sw Hw

— —————— ————————————————

1 4.2(1)SV1(5.2b) 0.0

3 4.2(1)SV1(5.2b) VMware ESXi 5.1.0 Releasebuild-799733 (3.1)

4 4.2(1)SV1(5.2b) VMware ESXi 5.1.0 Releasebuild-799733 (3.1)

Mod MAC-Address(es) Serial-Num

— ————————————– ———-

1 00-19-07-6c-5a-a8 to 00-19-07-6c-62-a8 NA

3 02-00-0c-00-03-00 to 02-00-0c-00-03-80 NA

4 02-00-0c-00-04-00 to 02-00-0c-00-04-80 NA

Mod Server-IP Server-UUID Server-Name

— ————— ———————————— ——————–


3 00408113-d21d-b211-8000-00215ad4da30 4 00217719-d21d-b211-8000-00237d5e6996 nn2 * this terminal session

Go to Understand Cisco Nexus 1000v deployment and other components – Part 3


Good Links







Posted on 17/01/2013, in Cisco Nexus 1000v and tagged , , , , , , , , . Bookmark the permalink. 1 Comment.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: