Implement 4 byte AS support
Bug #1416551 reported by
Nischal Sheth
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
Trunk |
Fix Committed
|
Wishlist
|
Nikhil Bansal |
Bug Description
It is typically not desirable to use public ASN for a cluster.
However there is a need to interoperate with an L3VPN core that
uses a 4-byte AS.
Hence the first phase of the implementation would be to handle
received AS4_PATH attribute and prepend our AS to it. Second
phase would be to allow a 4-byte AS as the local AS for cluster.
https:/
Note that 4 byte AS support is not necessary even if the underlay
uses 4 byte ASes as described below. No interaction is required
between the underlay and the overlay.
https:/
information type: | Proprietary → Public |
description: | updated |
description: | updated |
description: | updated |
To post a comment you must log in.
Review in progress for https:/ /review. opencontrail. org/45094
Submitter: Nikhil Bansal (<email address hidden>)