[EVPN VXLAN] WHen LIF is moving to new VN control node is not sending evpn route

Bug #1732576 reported by chhandak
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Juniper Openstack
Status tracked in Trunk
R4.1
Invalid
High
Nischal Sheth
Trunk
Invalid
High
Nischal Sheth

Bug Description

Description:
WHen LIF is moving to new VN control node is not sending evpn route

Details:
Lif was initially part of vn-test1. When moving the VN to vn-test2, QFX is subscribing for new VN route target. But CN is not sending any evpn route to QFX.

Workaround:
If we clear the BGP neighbor all routes are send my CN correctly

root@5b11-qfx2> show route table bgp.rtarget.0 advertising-protocol bgp 172.16.180.101

bgp.rtarget.0: 8 destinations, 15 routes (8 active, 0 holddown, 0 hidden)
  Prefix Nexthop MED Lclpref AS path
  0:0:0/0
* Self 100 I
  65000:65000:1/96
* Self 100 I
  65000:65000:8000002/96
* Self 100 I
  65000:65000:8000003/96 >>>>>>>>>>>>>>>>>>>>>New VN Rt
*
  65000:65000:268435460/96
* Self 100 I
  65000:65000:268435461/96
* Self 100 I
  65000:#0602020100000506/96
* Self 100 I

root@5b11-qfx2# run show route table default-switch.evpn.0 | grep 3:
3:172.16.2.1:1::4::172.16.2.1/248 IM
3:172.16.3.1:1::4::172.16.3.1/248 IM
3:172.16.180.102:2::4::172.16.180.102/248 IM
3:172.16.180.103:2::4::172.16.180.103/248 IM

chhandak (chhandak)
Changed in juniperopenstack:
importance: Undecided → Critical
importance: Critical → High
assignee: nobody → Nischal Sheth (nsheth)
milestone: none → r4.1.0.0-fcs
information type: Proprietary → Public
Revision history for this message
Nischal Sheth (nsheth) wrote :

As discussed offline, this is due to the 0:0:0/0 prefix in bgp.rtarget.0
advertised by QFX. Will mark the bug as Invalid.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.