交换机 : Cisco Nexus 1000V 系列交换机

连结1000V VM注册排除故障

2015 年 8 月 28 日 - 机器翻译
其他版本: PDFpdf | 英语 (2015 年 4 月 23 日) | 反馈

简介

为了VM能来联机和请接收适当编程从虚拟化服务模块(VSM),那里是一些个必要的步骤。本文解释如何确定适当的步骤是否由软件采取为了获得虚拟机适当地注册和被编程。

贡献用Joey Ristaino, Cisco TAC工程师。

故障排除

这是必要的步骤为了VM能来联机:

  1. VM有适当的波尔特配置文件信息,并且网络适配器启用。
  2. VMkernel启用端口并且连结接口与dvPort ID。
  3. 虚拟以太网模块(VEM)从内核获得连接通知并且发送附上通知对VSM。
  4. VSM获得通知并且发送编程该它需要基于dvport组的VEM。
  5. VM来联机。

您也许需要调试代码。请使用这些调试检查此:

  • vemlog调试vssnet全部:表示从内核的DISCONNECT/CONNECT消息
  • 响应调试sfportagent all> /tmp/dpafifo :显示附上/从VEM分开通知

完成步骤:

  1. 启用在VM的适配器。



  2. 查看vemlog内容显示all命令

    检查在/var/log的vmkernel.log文件连接:

    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. 检索调试日志并且检查已连接和链路恢复通知:

    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. 保证您看到从VEM的附上通知到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. 验证VEM接收从VSM的notfication :

    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. 验证VM联机:

    ~ # 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


    现在您能设置调试回到正常:

    • vemlog调试全部默认
    • 响应调试sfportagent默认> /tmp/dpafifo

相关的思科支持社区讨论

思科支持社区是您提问、解答问题、分享建议以及与工作伙伴协作的论坛。


Document ID: 117615