RR is not configured with l3vpn signalling
Bug #1802420 reported by
venu kolli
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | ||
|---|---|---|---|---|---|---|
| Juniper Openstack | Status tracked in Trunk | |||||
| R5.0 |
New
|
High
|
Rishabh Tulsian | |||
| Trunk |
New
|
High
|
Rishabh Tulsian | |||
Bug Description
Build : 5.0-341
RR is not configured with l3vpn signalling .
MX which is a spine is connected to RR .
Created a network marked as external with FIP pool and extended to MX
VM is launched in pvt and associated FIP to it .
I don't see routes being advertised to mx which is connected to RR (qfx spine)
| tags: |
added: fabric overlay removed: blocker |
Revision history for this message
| Ananth Suryanarayana (anantha-l) wrote | #1 |
| tags: | added: releasenote |
| tags: | added: blocker |
| tags: | removed: blocker |
Revision history for this message
| venu kolli (vkolli) wrote | #2 |
| information type: | Proprietary → Public |
To post a comment you must log in.
if RR needs to be also gateway, we need for overlay-bgp
1. inet-vpn unicast (and inet6-vpn unicast) must be also be configured bgp peering
2. resolution-ribs in inet.0 may be necessary as RR may not be in data-path for l3vpn routes
or this
3. set groups __contrail_overlay_ routing-options rib inet.3 static route 0/0 discard
Not sure.. But needs changes in the play-book