Vxlan mode set to user mode causes the routes that are advertised by control, doesn't have vxlan encapsulation bgp community

Bug #1802425 reported by Arijit Paul
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Juniper Openstack
Status tracked in Trunk
R5.0
Incomplete
High
Arijit Paul
Trunk
Incomplete
High
Arijit Paul

Bug Description

Vxlan mode set to user mode on Contrail controller causes the routes that are advertised by control, do not have vxlan encapsulation bgp community. On receiving these routes the route-reflector marks them as hidden as vxlan community is not present.

manishkn (manishkn)
tags: removed: scale
tags: added: scale
Jeba Paulaiyan (jebap)
tags: added: releasenote
Revision history for this message
Jeba Paulaiyan (jebap) wrote :

Notes:

If VxLAN mode is set to user mode, Contrail controller advertises routes without VxLAN encapsulation BGP community to the Route Reflector. This make the Route Reflector mark those routes as hidden. Hence it is recommended to use VxLAN mode auto.

Jeba Paulaiyan (jebap)
information type: Proprietary → Public
Revision history for this message
Arijit Paul (arijitp) wrote :
Download full text (27.0 KiB)

root@5b11-qfx5> show route summary
Autonomous system number: 64512
Router ID: 5.5.5.5

inet.0: 16 destinations, 16 routes (16 active, 0 holddown, 0 hidden)
              Direct: 5 routes, 5 active
               Local: 4 routes, 4 active
              Static: 7 routes, 7 active

:vxlan.inet.0: 9 destinations, 9 routes (9 active, 0 holddown, 0 hidden)
              Direct: 5 routes, 5 active
               Local: 4 routes, 4 active

bgp.l3vpn.0: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden)
                 BGP: 3 routes, 3 active

inet6.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
              Direct: 1 routes, 1 active
               INET6: 1 routes, 1 active

bgp.rtarget.0: 8 destinations, 11 routes (8 active, 0 holddown, 0 hidden)
                 BGP: 10 routes, 7 active
             RTarget: 1 routes, 1 active

bgp.evpn.0: 8 destinations, 8 routes (2 active, 0 holddown, 6 hidden)
                 BGP: 8 routes, 2 active

{master:0}
root@5b11-qfx5> show route summary
Autonomous system number: 64512
Router ID: 5.5.5.5

inet.0: 16 destinations, 16 routes (16 active, 0 holddown, 0 hidden)
              Direct: 5 routes, 5 active
               Local: 4 routes, 4 active
              Static: 7 routes, 7 active

:vxlan.inet.0: 9 destinations, 9 routes (9 active, 0 holddown, 0 hidden)
              Direct: 5 routes, 5 active
               Local: 4 routes, 4 active

bgp.l3vpn.0: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden)
                 BGP: 3 routes, 3 active

inet6.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
              Direct: 1 routes, 1 active
               INET6: 1 routes, 1 active

bgp.rtarget.0: 8 destinations, 11 routes (8 active, 0 holddown, 0 hidden)
                 BGP: 10 routes, 7 active
             RTarget: 1 routes, 1 active

bgp.evpn.0: 8 destinations, 8 routes (7 active, 0 holddown, 1 hidden)
                 BGP: 8 routes, 7 active

{master:0}
root@5b11-qfx5> show route summary
Autonomous system number: 64512
Router ID: 5.5.5.5

inet.0: 16 destinations, 16 routes (16 active, 0 holddown, 0 hidden)
              Direct: 5 routes, 5 active
               Local: 4 routes, 4 active
              Static: 7 routes, 7 active

:vxlan.inet.0: 9 destinations, 9 routes (9 active, 0 holddown, 0 hidden)
              Direct: 5 routes, 5 active
               Local: 4 routes, 4 active

bgp.l3vpn.0: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden)
                 BGP: 3 routes, 3 active

inet6.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
              Direct: 1 routes, 1 active
               INET6: 1 routes, 1 active

bgp.rtarget.0: 8 destinations, 11 routes (8 active, 0 holddown, 0 hidden)
                 BGP: 10 routes, 7 active
             RTarget: 1 routes, 1 active

bgp.evpn.0: 8 destinations, 8 routes (7 active, 0 holddown, 1 hidd...

Revision history for this message
Narendranath (nkarjala) wrote :

This is not a Bug. User is supposed to set the "VxLAN Identifier" for the network for it to work with the "user configured" mode.

When "VxLAN Identifier Mode" is in Auto mode, VxLAN ID is assigned with the "Network ID". In case of "User Configured" mode, VxLAN ID will be assigned from the "VxLAN Identifier" of the network. This field property is to be configured by the user.

Since the "VxLAN Identifier" wasn't set, and when the system is put to "User configured", the routes aren't advertised.

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.