Guest

Cisco Nexus 1000V Switch for VMware vSphere

Nexus 1000V VM Registration Troubleshoot

Document ID: 117615

Updated: Apr 09, 2014

Contributed by Joey Ristaino, Cisco TAC Engineer.

   Print

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:

  1. The VM has proper port-profile information and the network adapter is enabled.
  2. VMkernel enables the port and associates the interface with a dvPort ID.
  3. The Virtual Ethernet Module (VEM) gets a CONNECT notification from the kernel and sends an attach notification to the VSM.
  4. The VSM gets the notification and sends the VEM the programming that it needs based on the dvport-group.
  5. The VM comes online.

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:

  1. Enable the adapter on the VM.



  2. View the contents of vemlog show all command.

    Check the vmkernel.log file in /var/log for the connection:

    2014-02-27T20:00:22.558Z cpu11:198971)Net: 1858: connected Win2K8.eth1
    eth1 to vDS, portID 0x3000019

    2014-02-27T20:00:22.558Z cpu11:198971)Net: 2260: associated dvPort 133 with
    portID 0x3000019
    2014-02-27T20:00:22.558Z cpu11:198971)NetPort: 2747: resuming traffic on
    DVport 133
    2014-02-27T20:00:22.558Z cpu11:198971)NetPort: 1380: enabled port
    0x3000019 with mac 00:50:56:bc:27:ac


  3. Retrieve the debug logs and check for the CONNECTED and LINKUP notifications:

    Feb 27 20:00:22.558061        3 11   1  16   Debug     state:          0  
    CONNECTED
    Feb 27 20:00:22.558062 4 11 1 16 Debug porttype: 1
    Feb 27 20:00:22.558062 5 11 1 16 Debug portID: 50331673
    Feb 27 20:00:22.558063 6 11 1 16 Debug svs_netif_port_state_cb:
    Called with SF_PORT_CONNECTED


    Feb 27 20:00:22.558347       33 11   1  16   Debug svs_netif_port_state_cb: 
    Found the following from portstate:
    Feb 27 20:00:22.558348 34 11 1 16 Debug state: 2 LINKUP
    Feb 27 20:00:22.558349 35 11 1 16 Debug porttype: 1
    Feb 27 20:00:22.558350 36 11 1 16 Debug portID: 50331673
    Feb 27 20:00:22.558351 37 11 1 16 Debug svs_netif_port_state_cb:
    SF_PORT_LINKUP found non-l2device


  4. Ensure that you see the attach notification from the VEM to VSM:

    Feb 27 20:00:22.558372       51 11   1  16   Debug Sending notification with the
    following data:
    Feb 27 20:00:22.558372 52 11 1 16 Debug uuid_type: 1
    Feb 27 20:00:22.558372 53 11 1 16 Debug alias_type: 2
    Feb 27 20:00:22.558373 54 11 1 16 Debug attach_op: 1
    Feb 27 20:00:22.558373 55 11 1 16 Debug port_index: 3
    Feb 27 20:00:22.558374 56 11 1 16 Debug DVS portID: 85
    Feb 27 20:00:22.558374 57 11 1 16 Debug portID:
    3000019
    Feb 27 20:00:22.558375 58 11 1 16 Debug MAC:
    0:50:56:bc:27:ac
    Feb 27 20:00:22.558375 59 11 1 16 Debug UUID:
    50 3c 7f 1e b3 f0 88 f6-f9 a9 41 1d a6 f0 c4 5a
    Feb 27 20:00:22.558376 60 11 1 16 Debug VM Name:
    Win2K8
    Feb 27 20:00:22.558377 61 11 1 16 Debug Profile Alias:
    dvportgroup-2275
    Feb 27 20:00:22.558377 62 11 1 16 Debug Connected nic number 1
    Feb 27 20:00:22.558388 63 11 1 16 Debug Updating attach_status to 0
    for portID[3000019], ltl[52]
    Feb 27 20:00:22.558389 64 11 1 16 Debug svs_set_pod_seq_flag: ltl -
    52 value - 4
    Feb 27 20:00:22.607033 65 0 99 16 Debug Processing attach notification
    Feb 27 20:00:22.607049 66 0 99 16 Debug MAC: 0:50:56:bc:27:ac
    Feb 27 20:00:22.607057 67 0 99 16 Debug slot=2 ls_port_num=3
    ds_port_num=133
    Feb 27 20:00:22.607072 68 0 99 16 Debug ds_uuid=ee 63 3c 50 04
    b1 6d d6-58 61 ff ba 56 05 14 fd
    Feb 27 20:00:22.607076 69 0 99 16 Debug profile_alias=dvportgroup
    -2275
    Feb 27 20:00:22.607080 70 0 99 16 Debug UUID: 50 3c 7f 1e b3 f0
    88 f6-f9 a9 41 1d a6 f0 c4 5a
    Feb 27 20:00:22.607084 71 0 99 16 Debug VM NAME: Win2K8
    Feb 27 20:00:22.607088 72 0 99 16 Debug ifindex: 0x1b020030


  5. Verify that the VEM receives the notfication from the VSM:

    Feb 27 20:00:22.607102      74  0  99  16   Debug sf_port_process_attach_notify:
    LTL 52: Set uuid: 503c 7f 1e b3 f0 88 f6-f9 a9 41 1d a6 f0 c4 5a
    Feb 27 20:00:22.607111 75 0 99 16 Debug sf_port_process_attach_notify:
    ifname: lveth3/4
    Feb 27 20:00:22.607129 76 0 99 16 Debug sf_port_process_attach_notify:
    Before : ltl (52), veth_ifindex (0x0)
    Feb 27 20:00:22.607137 77 0 99 16 Debug sf_port_process_attach_notify:
    After : ltl (52), veth_ifindex (0x1c000100)
    Feb 27 20:00:22.607142 78 0 99 16 Debug sf_port_process_attach_notify:
    Created attach info for lveth3/4 (cookie=13)
    Feb 27 20:00:22.607153 79 0 99 16 Debug sf_port_check_attach:
    VSM Attach for 00:50:56:bc:6a:3d cookie 13 attempt 1
    Feb 27 20:00:22.607171 80 0 99 16 Debug sf_send_attach_pending_notify:
    Sending attach pending notify for lveth3/4

    Feb 27 20:00:22.610126 81 0 99 16 Debug Rcvd attach ack for lveth3/4
    Feb 27 20:00:22.610140 82 0 99 16 Debug sf_attach_veth(1b020030,
    1c000100) success!


  6. Verify that the VM is online:

    ~ # vemcmd show port
    LTL VSM Port Admin Link State PC-LTL SGID Vem Port Type
    17 Eth3/1 UP UP FWD 561 0 vmnic0
    18 Eth3/2 UP UP FWD 561 1 vmnic1
    49 Veth3 UP UP FWD 0 0 vmk0
    50 Veth4 UP UP FWD 0 1 vmk1
    51 Veth11 UP UP FWD 0 0 vmk2 VXLAN
    52 Veth17 UP UP FWD 0 1 Win2K8.eth1
    53 DOWN UP BLK 0 Win2K8.eth0
    561 Po2 UP UP FWD 0


    Now you can set the debugs back to normal:

    • vemlog debug all default
    • echo debug sfportagent default > /tmp/dpafifo
Updated: Apr 09, 2014
Document ID: 117615