certainly this is a bug MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable
I see someone beat me to it but you can specifying inet.3. The docs on this stuff are really poor but that is how you would want to do it so you know known MPLS destinations are being advertised. Now if you want to advertise non MPLS destinations as labeled unicast it does work as well, nothing says it has to be MPLS switched on the advertising router. Phil From: Jeff Wheeler Sent: =E2=80=8E1/=E2=80=8E21/=E2=80=8E2013 6:05 To: Alex Arseniev Cc: juniper-nsp Subject: Re: [j-nsp] Junos labeled-unicast announces unusable routes, certainly this is a bug On Mon, Jan 21, 2013 at 4:27 AM, Alex Arseniev <[email protected]> wr= ote: > Probably not what you want to hear at the moment but it "is working as > designed". No, it isn't. Junos BGP is announcing routes it knows, for sure, are invalid. It knows that because BGP is making up a wrong label (2^20-1) because it hasn't allocated one, and it can't announce the route without a label. This is an inexcusable bug that is very far from "working as designed." The documentation is wrong, you cannot configure both AFI=3D1 SAFI=3D1 and AFI=3D1 SAFI=3D4 on the same BGP session. If it worked as documented, the above behavior would not happen, and AFI=3D1 SAFI=3D1 would be available to use for these routes. That is not the case. -- Jeff S Wheeler <[email protected]> Sr Network Operator / Innovative Network Concepts _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
