Hi Hari, 

Does build 93 have the fix? I just upgraded to 93 build last week. 

Thanks,

Sharon


________________________________________
From: <email address hidden> <email address hidden> on behalf of Hari Prasad Killi <email address hidden>
Sent: Friday, September 04, 2015 10:11 PM
To: Sharon Zhang
Subject: [Bug 1491644] Re: BMS ping BMS failed due to arp respond from vhost0

R2.21 is not officially yet released officially. Fix for this issue is
in dev build 94.

--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1491644

Title:
  BMS ping BMS  failed due to arp respond from vhost0

Status in Juniper Openstack:
  New

Bug description:

  The test setup has BMSes connected to Opus TOR, Opus are connected to MX GW, and Contrail Vrouters are also connected to MX gateway.

  Ping from Contrail VM to BMS works fine, but ping between two BMS in
  the same VN  failed.

  The detail topology will be attached to this PR.


  Captured the packets, it shows that the arp request from BMS1 got 3 respond for the same host (BMS2).

  BMS1: IP 101.1.1.20  MAC: 00:10:94:00:00:19
  BMS2: IP 101.1.1.21 MAC: 00:10:94:00:00:17

  Ping from BMS1 to BMS2: got arp respond from three hosts:

  BMS2: 101.1.1.20 at 00:10:94:00:00:19
  vhost0 on vrouter1 (sdn-st-dellpc-c):  101.1.1.20 at 14:fe:b5:cc:73:f2
  vhost0 on vrouter2(sdn-st-dellpc-e): 101.1.1.20 at 14:fe:b5:cc:74:dc

  The capture file  on both BMS1 and BMS2 will be attached to the PR.


  root@sdn-st-dellpc-e:~# ifconfig |grep 14:fe
  em1       Link encap:Ethernet  HWaddr 14:fe:b5:cc:74:da
  em2       Link encap:Ethernet  HWaddr 14:fe:b5:cc:74:dc
  vhost0    Link encap:Ethernet  HWaddr 14:fe:b5:cc:74:dc
  root@sdn-st-dellpc-e:~# ifconfig vhost0
  vhost0    Link encap:Ethernet  HWaddr 14:fe:b5:cc:74:dc
            inet addr:192.14.1.10  Bcast:192.14.1.255  Mask:255.255.255.0
            inet6 addr: fe80::16fe:b5ff:fecc:74dc/64 Scope:Link
            UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
            RX packets:6690600 errors:0 dropped:196 overruns:0 frame:0
            TX packets:8191847 errors:0 dropped:0 overruns:0 carrier:0
            collisions:0 txqueuelen:1000
            RX bytes:1381280714 (1.3 GB)  TX bytes:9748573454 (9.7 GB)


  root@sdn-st-dellpc-e:/home/regress# ifconfig em2
  em2       Link encap:Ethernet  HWaddr 14:fe:b5:cc:74:dc
            inet6 addr: fe80::16fe:b5ff:fecc:74dc/64 Scope:Link
            UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
            RX packets:2989936882 errors:0 dropped:29942 overruns:0 frame:0
            TX packets:105124710 errors:0 dropped:0 overruns:0 carrier:0
            collisions:0 txqueuelen:1000
            RX bytes:432178728813 (432.1 GB)  TX bytes:20840328168 (20.8 GB)


  root@sdn-st-dellpc-c:/var/tmp# ifconfig |grep 14:fe
  em1       Link encap:Ethernet  HWaddr 14:fe:b5:cc:73:f0
  em2       Link encap:Ethernet  HWaddr 14:fe:b5:cc:73:f2
  vhost0    Link encap:Ethernet  HWaddr 14:fe:b5:cc:73:f2
  root@sdn-st-dellpc-c:/var/tmp# ifconfig vhost0
  vhost0    Link encap:Ethernet  HWaddr 14:fe:b5:cc:73:f2
            inet addr:192.11.1.10  Bcast:192.11.1.255  Mask:255.255.255.0
            inet6 addr: fe80::16fe:b5ff:fecc:73f2/64 Scope:Link
            UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
            RX packets:15223755 errors:0 dropped:585 overruns:0 frame:0
            TX packets:19568275 errors:0 dropped:0 overruns:0 carrier:0
            collisions:0 txqueuelen:1000
            RX bytes:2160613933 (2.1 GB)  TX bytes:21182898261 (21.1 GB)

  root@sdn-st-dellpc-c:/var/tmp# ifconfig em2
  em2       Link encap:Ethernet  HWaddr 14:fe:b5:cc:73:f2
            inet6 addr: fe80::16fe:b5ff:fecc:73f2/64 Scope:Link
            UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
            RX packets:3933896038 errors:0 dropped:69008 overruns:0 frame:0
            TX packets:660320590 errors:0 dropped:0 overruns:0 carrier:0
            collisions:0 txqueuelen:1000
            RX bytes:551879637126 (551.8 GB)  TX bytes:93958780865 (93.9 GB)


  Since the last respond is from vrouter vhost0, hence ping will failed.  Ping will go through sometime if the real bms host is the last one to respond the arp.


  The contrail has 10VMs on the same VN, and the IP address for the VM is from 101.1.1.1-101.1.1.11

  This is very critical issue. I tried to capture the packets on vhost0
  interface on vrouter, but could not get the arp packets.

  Which interface should I use to capture the packets from BMS?

  ›

To manage notifications about this bug go to:
https://bugs.launchpad.net/juniperopenstack/+bug/1491644/+subscriptions