Mailing List Archive

https://www.juniper.net/documentation/en_US/junos/topics/reference/configuration-statement/as-path-edit-routing-options.html

On Sun, Nov 8, 2020, 2:09 PM Dario Amaya <darioamaya82@gmail.com> wrote:

> Hello,
>
> Our customer has own ASN from ARIN and want us to take care of all
> routing. We already originate the customer prefix from our ASN. What
> is easiest / recommended way to append customer's ASN to the prefixes
> to make it appear as though it's originated from their ASN without any
> routing equipment / BGP from them? This is on Juniper MX, is L3VPN the
> answer?
> _______________________________________________
> juniper-nsp mailing list juniper-nsp@puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

routing-options {
static {
route xx.xx.xx.0/24 {
next-hop yy.yyy.yy.yy;
as-path {
path 12345;
origin igp;
atomic-aggregate;
}
}
}
}

Where:
- xx.xx.xx.0/24 is their block
- yy.yy.yy.yy is the /31 facing them (assuming they're directly connected to this router)
- 12345 is their ASN

- CK.




> On 9 Nov 2020, at 7:06 am, Dario Amaya <darioamaya82@gmail.com> wrote:
>
> Hello,
>
> Our customer has own ASN from ARIN and want us to take care of all
> routing. We already originate the customer prefix from our ASN. What
> is easiest / recommended way to append customer's ASN to the prefixes
> to make it appear as though it's originated from their ASN without any
> routing equipment / BGP from them? This is on Juniper MX, is L3VPN the
> answer?
> _______________________________________________
> juniper-nsp mailing list juniper-nsp@puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp

_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp