Define BGP community
Bug #1613934 reported by
Vishal Nagaonkar
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Juniper Openstack |
New
|
Undecided
|
Unassigned | ||
Bug Description
If BGP community values are automatically generated. The first field (AS field) should have the ability to be designated at the discretion of the customer to avoid duplication in a multiple controller environment within the same AS. Cox wants to be able to define the AS field. This would prevent communities clashing and duplication. Cox wants to be able to define a numeric value in the community field. They want to be able to map the identity of the controller to the community. Cox policy is to tag traffic on the PE not transit nodes. Community values are tagged at the PE. The core then takes action on these tags.
| Changed in juniperopenstack: | |
| assignee: | nobody → Vishal Nagaonkar (vnagaonkar) |
| assignee: | Vishal Nagaonkar (vnagaonkar) → nobody |
| information type: | Proprietary → Public |
Revision history for this message
| Aniket Daptari (adaptari) wrote | #1 |
To post a comment you must log in.
High Level Requirements
Because of certain issues (customer hasn't elaborated on the issues faced), customer wants to use iBGP in a DCI scenario. In that case, they want greater control in assigning the ASN portion of the community to avoid duplicate community values between the multiple controllers. 2 separate contrail controllers and use iBGP. Want to be able to modify the AS portion of the community field to identify which controller it came from.
Workaround to tag routes on the MX when you receive them was suggested, however, customer does not have practice to tag routes in transit.
Customer Use-case
In DCI scenarios, they want to be able to identify the individual controller
Business Case / Customer Requested Timeline
Cox Communications Q4 2016
Engineering Response / Inputs:
Engineering (Ashish) suggested to file a bug.