5.0.1: BGPaaS local-as. local-as is passed on from contrail cluster to outside. local-as should be removed when the route moves out of the cluster

[Shashikiran H]

R5.0.1 master 153 ocata

Have below topo:

bgpass vm --- local as --- contrail --- ibgp --- mx

mx has 2 routing instance (left and right).
contrail has to 2 vns corresponding to each mx vrf(left and right).

bgpaas vm has 2 legs correspong to left and right VN and 2 groups with different local-as values to contrail corresponding to each VN leg.
I use bgpaas vm to move routes from left VN local-as to right VN local-as. Routes then go to contrail right vrf, and then back to mx.

When mx receives them, they still have the local-as values in ASPATH bgp attrbute. contrail has to remove these local-as values, otherwise the user is only limited to using public ASN value, which may not be feasible. Or a policy has to be used on mx everytime the route is moved from contrail domain to outside.

[Ananth Suryanarayana (anantha-l)]

Are you referring to remove-private AS equivalent feature ? Did you try enabling that for the peer towards MX ?

[Shashikiran H (skiranh)]

Hey Ananth,

I have tried using "private-as-action" set to "remove" in bgp-router-ref for mx on control node. That does not work. Also, "remove-all" also does not work.

[Shashikiran H (skiranh)]

The remove-private is meant to work with BGP standard private as range and not contrail local-as. Will have to try a few scenarios with this new info. Will move it back to DEV if this does not work. Assigning to myself and removing beta-blocker.

[Shashikiran H (skiranh)]

Confirmed that "remove" and "replace-all" works as written in comment #3. They are for BGP standard private as range and not local-as. Closing this bug.