Consider 2 bgpaas-clients in the same VN that are configured with the
same ASN. Routes sent by one client will not be advertised to the other
client by default since CN implements a sender side AS loop check.
CN needs to implement equivalent of JUNOS as-override knob in order to
work around this issue. RibOut AS is replaced by CN AS in the AS Path.
Pending items:
- Schema and config parsing changes to enable AS override
- Do not advertise routes back to peer even if as override is enabled
Reviewed: https:/ /review. opencontrail. org/18357 github. org/Juniper/ contrail- controller/ commit/ feeb4238fcad940 6f22e611441381d 4163f4b471
Committed: http://
Submitter: Zuul
Branch: master
commit feeb4238fcad940 6f22e611441381d 4163f4b471
Author: Nischal Sheth <email address hidden>
Date: Fri Mar 11 11:45:04 2016 -0800
BGPaaSv2: Implement AS override functionality
Consider 2 bgpaas-clients in the same VN that are configured with the
same ASN. Routes sent by one client will not be advertised to the other
client by default since CN implements a sender side AS loop check.
CN needs to implement equivalent of JUNOS as-override knob in order to
work around this issue. RibOut AS is replaced by CN AS in the AS Path.
Pending items:
- Schema and config parsing changes to enable AS override
- Do not advertise routes back to peer even if as override is enabled
Change-Id: I963a8cb6cdbdf4 ed27cd18726371e 9a8bb19dd39
Partial-Bug: 1552952