Nexus 1000v SNMP

I had a few of folks ask me about snmp configuration on 1000v last so am reusing the content I sent them for this post. This is basically a 5 minute configuration of Nexus 1000v SNMP monitoring with SolarWinds NPM.

Software Versions used:

Nexus 1000v version 4.0(4)SV1(3b)

Nexus 1000v version 4.0(4)SV1(4)

SolarWinds Orion NPM 10.2

Network Topology:
SolarWinds NPM was running in a VM on the same cluster as the VSM. Basically they were connected to the same physical Nexus 5020 and on the same vlan. So a very flat backend network topology and no firewall in between. before you begin make sure you can ping from Nexus 1000v to the NMS.

Configuration Steps:

Step 1.
Configure Nexus 1000v SNMP to send traps to the NMS.

Here we are using user xxxxxx to send traps to the NMS using management interface.

snmp-server contact [email protected]
snmp-server location SJSV-iLAB
snmp-server user admin network-admin auth md5 Cisco123 priv aes-128 Cisco123
snmp-server user admin enforcePriv
snmp-server user xxxxxx network-admin auth md5 Cisco123 priv aes-128 Cisco123
snmp-server user xxxxxx enforcePriv
snmp-server host 172.16.165.134 traps version 3 priv xxxxxx
snmp-server host 172.16.165.134 use-vrf management

Step 2. Configuration On SolarWinds
Step 2(a).
Select Add Node and Type in the Nexus 1000v VSM IP Address

Step 2(b).
Type in the user authorized to send snmp trap on the VSM


The SNMPv3 Password can be either just the password you configured (“Cisco123”)or its localized key (“0x81558f44c057276fca90f3b757465c7c”) from show run snmp. If you are using the localized key make sure you check “Password is a key”, as shown in the following screen shot.
For example:snmp-server user xxxxxx network-admin auth md5 Cisco123 priv aes-128 Cisco123
Becomes:
snmp-server user xxxxxx network-admin auth md5 0x81558f44c057276fca90f3b757465
c7c priv aes-128 0x81558f44c057276fca90f3b757465c7c localizedkey

Step 2(c).
Repeat the same steps, same username and password.

Step 2(d).

Now Click “Test” and it should be successful.

Step 2(e).Now go through the steps and add the interfaces to monitors, I went with all :)

Step 2(f).
Select what pollers to add to the node, here some like power supply, temp are not relevant for a VSM running on a ESX host, so pick and choose the ones you want to poll.

Click Next.

Step 2(g).


Now Click on “OK, ADD NODE” and voila “Node was successfully added”.

Cisco Nexus 1000v manual VEM upgrade to Release 4.2(1) SV1(4)

Note 1: Even though Cisco fully supports VUM based upgrades we generally recommend the CLI for VEM upgrades as it provides more granular control on what gets upgraded when.

Note 2: If you plan on manually upgrading the VEM modules make sure you have disabled VMware Update Manager (VUM) service so that it does not automatically roll back changes we make. Once the vem upgrade is complete we can start it back up.

Step 0 Run a “show mod” to check the status of the modules

switch#  show mod
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
5    248    Virtual Ethernet Module           NA                  ok
6    248    Virtual Ethernet Module           NA                  ok

Mod  Sw               Hw
---  ---------------  ------
1    4.0(4)SV1(3b)     0.0
3    4.0(4)SV1(3b)     1.11
4    4.0(4)SV1(3b)     1.11
5    4.0(4)SV1(3b)     1.11
6    4.0(4)SV1(3b)     1.11 

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
5    02-00-0c-00-05-00 to 02-00-0c-00-05-80  NA
6    02-00-0c-00-06-00 to 02-00-0c-00-06-80  NA

Mod  Server-IP        Server-UUID                           Server-Name
---  ---------------  ------------------------------------  --------------------
1    172.16.165.55    NA                                    NA
3    172.16.165.91    dcedbaac-1dc0-11df-0000-00000000000e  172.16.165.91
4    172.16.165.92    dcedbaac-1dc0-11df-0000-00000000000d  172.16.165.92
5    172.16.165.93    dcedbaac-1dc0-11df-0000-00000000000c  172.16.165.93
6    172.16.165.94    dcedbaac-1dc0-11df-0000-00000000000b  172.16.165.94
* this terminal session

This is looking good, with one active VSM and multiple VEM modules and all running the same version.

Step 1 Download the Nexus1000v.4.2.1.SV1.4.zip file from Cisco.com and unzip it and you will find the new 4.2(1) SV1(4) vem images bundle vem-release_final.tar.gz under the VEM folder. Copy this file to the VSM bootflash.

switch# copy scp://[email protected]/srv/Cisco/Nexus1000v.4.2.1.SV1.4/VEM/vem-release_final.tar.gz bootflash:

Step 2 Update the VSM with the latest VEM modules

switch# vmware vem upgrade update-vibs bootflash:vem-release_final.tar.gz

Step 3 Notify vCenter Server/VUM that a latter version of VEM is available for upgrade.

switch# vmware vem upgrade notify
switch# show vmware vem upgrade status

Step 4 Confirm that VMware Update Manager is disabled (note 2) and then Go the vCenter Server, Home -> Inventory -> Networking and Select the Nexus 1000v swtich and Click the DVS Summary tab to check for the availability of a software upgrade and accept it. Now come back to VSM and check the status. And since we are planning to upgrade the VEM modules manually you can ahead and do “vmware vem upgrade proceed” and then complete the process.

switch# show vmware vem upgrade proceed
switch# show vmware vem upgrade status
switch# vmware vem upgrade complete
switch# show vmware vem upgrade staus

So far we let VSM, vCenter Server and by extension VMware update manager know that there is an VEM update available. Now we have to go ahead and actually install the VEM modules on the ESX hosts.

Step 5 Copy the VEM bundle to the ESX hosts /tmp folder or to a shared vmfs volume . Which VEM bundle to copy and install will depend on the build number of your ESX host, see the VEM compatibility table here for more details. Then depending on whether you are using the .vib or .zip files, you run either of the following command to install the VEM modules on the ESX hosts.

esx-host-2# esxupdate -b ./cross_cisco-vem-v130-4.2.1.1.3.9.0-1.9.1.vib update
esx-host-2# esxupdate --bundle VEM410-201101108-BG.zip update

Step 6 Now repeat the same steps on all the ESX hosts until you have, this on show mod.

switch#show mod
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
5    248    Virtual Ethernet Module           NA                  ok
6    248    Virtual Ethernet Module           NA                  ok

Mod  Sw                Hw
---  ----------------  ------------------------------------------------
1    4.0(4)SV1(3b)      0.0
3    4.2(1)SV1(4)      VMware ESXi 4.1.0 Releasebuild-320137 (2.0)
4    4.2(1)SV1(4)      VMware ESXi 4.1.0 Releasebuild-320137 (2.0)
5    4.2(1)SV1(4)      VMware ESXi 4.1.0 Releasebuild-320137 (2.0)
6    4.2(1)SV1(4)      VMware ESXi 4.1.0 Releasebuild-320137 (2.0)

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
5    02-00-0c-00-05-00 to 02-00-0c-00-05-80  NA
6    02-00-0c-00-06-00 to 02-00-0c-00-06-80  NA

Mod  Server-IP        Server-UUID                           Server-Name
---  ---------------  ------------------------------------  --------------------
1    172.16.165.55    NA                                    NA
3    172.16.165.91    dcedbaac-1dc0-11df-0000-00000000000e  172.16.165.91
4    172.16.165.92    dcedbaac-1dc0-11df-0000-00000000000d  172.16.165.92
5    172.16.165.93    dcedbaac-1dc0-11df-0000-00000000000c  172.16.165.93
6    172.16.165.94    dcedbaac-1dc0-11df-0000-00000000000b  172.16.165.94

Step 7 Once you confirm that all your ESX hosts have the latest VEM modules, Go ahead and start your VSM upgrade :)

Cisco Nexus 1000v Standalone VSM upgrade to Release 4.2(1) SV1(4)

Cisco Nexus team released the update to the Nexus 1000v product taking it to release 4.2(1) SV1(4). They did a great job of documenting the entire upgrade process both in docs and in a series of screencasts. Check it out it’s really worth your time.

However one obvious thing that they have missed so far is how to upgrade if your VSM is in standalone mode. Part of the problem is the Upgrade application (GUI) does not support standalone mode and the upgrade document does not address the manual upgrade (CLI) method for standalone VSM.

Here is a quick guide on how to upgrade your standalone VSM from 4.0(4) SV1(3, 3a, or 3b) to 4.2(1) SV1(4).

Before you start make sure you have run the pre-upgrade check script against your 1000v configuration to make sure you don’t run into the 7 configurations that are incompatible with Nexus 4.0.x to 4.2.x code.

Now the actual steps:

Step 0 Do a show mod and make sure you have already upgraded all the VEM modules. Remember this has changed from earlier releases. You HAVE to upgrade the VEM first and VSM second to upgrade to release 4.2(1) SV1(4).

show mod
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
5    248    Virtual Ethernet Module           NA                  ok
6    248    Virtual Ethernet Module           NA                  ok

Mod  Sw                Hw
---  ----------------  ------------------------------------------------
1    4.0(4)SV1(3b)      0.0
3    4.2(1)SV1(4)      VMware ESXi 4.1.0 Releasebuild-320137 (2.0)
4    4.2(1)SV1(4)      VMware ESXi 4.1.0 Releasebuild-320137 (2.0)
5    4.2(1)SV1(4)      VMware ESXi 4.1.0 Releasebuild-320137 (2.0)
6    4.2(1)SV1(4)      VMware ESXi 4.1.0 Releasebuild-320137 (2.0)

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
5    02-00-0c-00-05-00 to 02-00-0c-00-05-80  NA
6    02-00-0c-00-06-00 to 02-00-0c-00-06-80  NA

Mod  Server-IP        Server-UUID                           Server-Name
---  ---------------  ------------------------------------  --------------------
1    172.16.165.55    NA                                    NA
3    172.16.165.91    dcedbaac-1dc0-11df-0000-00000000000e  172.16.165.91
4    172.16.165.92    dcedbaac-1dc0-11df-0000-00000000000d  172.16.165.92
5    172.16.165.93    dcedbaac-1dc0-11df-0000-00000000000c  172.16.165.93
6    172.16.165.94    dcedbaac-1dc0-11df-0000-00000000000b  172.16.165.94

Step 1 Copy the new software release system image and kickstart image files to the bootflash file system of the VSM.

switch# copy scp:[email protected]/srv/n1kv-images/nexus-1000v-mz.4.2.1.SV1.4.bin bootflash:
switch# copy scp:[email protected]/srv/n1kv-imagess/nexus-1000v-kickstart.mz.4.2.1.SV1.4.bin bootflash:

Step 2 Use the install all command to update the boot variables to release 4.2(1)SV1(4) images.

switch# install all system bootflash: nexus-1000v-mz.4.2.1.SV1.4.bin kickstart bootflash:nexus-1000v-kickstart-mz.4.2.1.SV1.4.bin
Boot variables are updated to running configuration.

Step 3 Save your configuration by copying the running configuration to the startup configuration.

switch# copy running-config startup-config
[########################################] 100%

Step 4 Reload VSM.

switch# reload
This command will reboot the system. (y/n)? [n] y
switch#show mod
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
5    248    Virtual Ethernet Module           NA                  ok
6    248    Virtual Ethernet Module           NA                  ok

Mod  Sw                Hw
---  ----------------  ------------------------------------------------
1    4.2(1)SV1(4)      0.0
3    4.2(1)SV1(4)      VMware ESXi 4.1.0 Releasebuild-320137 (2.0)
4    4.2(1)SV1(4)      VMware ESXi 4.1.0 Releasebuild-320137 (2.0)
5    4.2(1)SV1(4)      VMware ESXi 4.1.0 Releasebuild-320137 (2.0)
6    4.2(1)SV1(4)      VMware ESXi 4.1.0 Releasebuild-320137 (2.0)

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
5    02-00-0c-00-05-00 to 02-00-0c-00-05-80  NA
6    02-00-0c-00-06-00 to 02-00-0c-00-06-80  NA

Mod  Server-IP        Server-UUID                           Server-Name
---  ---------------  ------------------------------------  --------------------
1    172.16.165.55    NA                                    NA
3    172.16.165.91    dcedbaac-1dc0-11df-0000-00000000000e  172.16.165.91
4    172.16.165.92    dcedbaac-1dc0-11df-0000-00000000000d  172.16.165.92
5    172.16.165.93    dcedbaac-1dc0-11df-0000-00000000000c  172.16.165.93
6    172.16.165.94    dcedbaac-1dc0-11df-0000-00000000000b  172.16.165.94

That’s it the VSM upgrade is complete to 4.2(1)SV1(4).

As an aside. These steps compare extremely well when contrasted with the HA based VSM manual upgrade which is 22+ steps. I actually had the VSMs in a HA pair and deleted the secondary, upgraded the primary as a standalone and deployed a new 4.2(1)SV1(4) VSM VM using the OVF files and powered it up and called it secondary and it happily synced with the primary and the upgrade is complete.

Slackware Virtual Machine v13.1

I have been meaning to update the linux virtual machine images with newer versions but have been too busy so far, however managed to get a breather at work thanks to the post Holidays slump :) So here is an vm with the latest version of Slackware 64bit v13.1.

Slackware Linux VM Configuration
Distribution: 13.1
Linux Kernel: 2.6.33
Installation Type: Base+X+XFCE
Desktop Environment: XFCE
Networking: DHCP
Root Password: “vmware”

Continue reading

Consolidating my blogs

After a lot of thinking :) I have decided to merge my two blogs previously at www.vmwhere.net and jayakumar.co.in into a single site/blog here at www.jayakumar.org.

The reason was simple, am lazy and do not want to maintain two sites. Plus after I moved out of VMware late last year I don’t feel the need maintain a separate blog for VMware so as maintain that thin distinction between work (VMware) and personal (linux/networking) stuff. Also since I have joined Cisco I wanted to blog bout Nexus 1000v and Cisco UCS products, but the mere thought of setting up and maintaining another blog kept that idea far. So theoretically I have merged 3 blogs into one.

Continue reading