I’m trying to get 2.2.2.0/24 advertised to Internet#1 under AS456 but whenever I do I am seeing it advertised under AS123. I’ve tried a lot of different combinations but I think I’m just missing something basic.
I’ve tried changing settings in the BGP Instances and Peers and well as Routing Filters. I haven’t been able to find any examples of this type of setup. Is anyone able to point me in the right direction?
I’m not 100% clear on your topology and desired behavior…
From the above quote, it sounds like you have two ASNs on your network.
That would be pretty unusual. The whole idea of an ASN is a unified policy - even if you send different communities, AS-prepends, etc to different providers to affect your routing policy, it’s still all just one ASN… (in most circumstances)
Are you using private ASNs from each provider? If so, and you’re multi-homed, then you should get your own ASN.
To clarify essentially I have two separate entities - both of which I have control of their networks. They need separate ASNs for a number of reasons.
We’re using private ASNs from each Internet provider. At one point there was only one entity (AS123), which had these same connections and was using these connections to be multi-homed. Now I’m introducing AS456 which will peer directly with Internet#2 and also share routes with AS123. I want the AS-Path for traffic going to 2.2.2.0/24 to hit AS123 before it hits AS456.
