Cisco Cisco Nexus 1000V Switch Troubleshooting Guide

Page of 4
Nexus 1000V VM Registration Troubleshoot
Document ID: 117615
Contributed by Joey Ristaino, Cisco TAC Engineer.
Apr 09, 2014
Contents
Introduction
Troubleshoot
Introduction
In order for a VM to come online and receive proper programming from the Virtualized Services Module
(VSM), there are a few necessary steps. This document explains how to determine if the proper steps were
taken by the software in order to get a virtual machine (VM) properly registered and programmed.
Troubleshoot
Here are the necessary steps in order for a VM to come online:
The VM has proper port−profile information and the network adapter is enabled.
1. 
VMkernel enables the port and associates the interface with a dvPort ID.
2. 
The Virtual Ethernet Module (VEM) gets a CONNECT notification from the kernel and sends an
attach notification to the VSM.
3. 
The VSM gets the notification and sends the VEM the programming that it needs based on the
dvport−group.
4. 
The VM comes online.
5. 
You might need to debug the code. Use these debugs to check this:
vemlog debug vssnet all: shows the DISCONNECT/CONNECT messages from the kernel
• 
echo debug sfportagent all > /tmp/dpafifo: shows the attach/detach notifications from the VEM
• 
Complete the steps:
Enable the adapter on the VM.
1.