Route reflector not setting originator_id
Hello, I have a very simple setup with one rr and one rr client. Im not seeing ORIGINATOR_ID nor CLUSTER_LIST attributes appended to the updates sent to the rr client. Aren't those supposed to be mandatory per RFC 4456 ? filter wr1_import { reject; } filter wr1_export prefix set te_internal; { te_internal = [ 10.0.0.0/8 ]; if (net ~ te_internal) then reject; accept; } protocol bgp bgp_wr1_v4 { description "something"; import filter wr1_import; export filter wr1_export; multihop 2; password "pass"; local as my_as; neighbor X.X.X.X as my_as; source address x.x.x.x; rr client; rr cluster id 1.1.1.1; }
On Thu, Jul 16, 2015 at 04:29:12PM -0700, Evelio VILA wrote:
Hello,
I have a very simple setup with one rr and one rr client.
Im not seeing ORIGINATOR_ID nor CLUSTER_LIST attributes appended to the updates sent to the rr client. Aren't those supposed to be mandatory per RFC 4456 ?
Hello I am not sure what is your exact setting, but ORIGINATOR_ID and CLUSTER_LIST are set when the route is reflected on route reflector. They are not set when the route is locally originated on a route reflector. AFAIK RFC 4456 does not specify such case, but it probably makes sense to add these attributes even in this case. -- Elen sila lumenn' omentielvo Ondrej 'Santiago' Zajicek (email: santiago@crfreenet.org) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."
participants (2)
-
Evelio VILA -
Ondrej Zajicek