[j-nsp] Junos labeled-unicast announces unusable routes, certainly this is a bug

[Krasimir Avramski]

You CAN configure both AFI=1 SAFI=1 and AFI=1 SAFI=4 on the same BGP
session by specifying inet.3 for labeled-unicast routes:
family inet {
        unicast;
        labeled-unicast {
            rib {
                inet.3;
            }
        }
    }


And redistributing LDP/RSVP routes from inet.3 makes perfect LSP stitching
through BGP-LU by label swapping.

Best Regards,
Krasi

On Mon, Jan 21, 2013 at 12:59 PM, Jeff Wheeler <jsw at inconcepts.biz> wrote:

> On Mon, Jan 21, 2013 at 4:27 AM, Alex Arseniev <alex.arseniev at gmail.com>
> wrote:
> > 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=1 SAFI=1 and
> AFI=1 SAFI=4 on the same BGP session.  If it worked as documented, the
> above behavior would not happen, and AFI=1 SAFI=1 would be available
> to use for these routes.  That is not the case.
>
> --
> Jeff S Wheeler <jsw at inconcepts.biz>
> Sr Network Operator  /  Innovative Network Concepts
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>