The local-as feature will indeed allow you to run two eBGP sessions to two different peers using two different AS numbers. You will still have only one BGP process though.
router bgp xyz
nei a.a.a.a remote-as abc
nei b.b.b.b remote-as cde
nei b.b.b.b local-as uvw
In this case, neighbor b.b.b.b would see your AS as uvw instead of xyz. Bear in mind that the xyz would also be part of as path seen by b.b.b.b. If you don't want xyz to be seen at all by b.b.b.b then you need to use the replace-as knob on the neighbor local-as command.
Hope this helps,
Harold Ritter Sr. Technical Leader CCIE 4168 (R&S, SP) email@example.com México móvil: +52 1 55 8312 4915 Cisco México Paseo de la Reforma 222 Piso 19 Cuauhtémoc, Juárez Ciudad de México, 06600 México
Thanks,I am having the issue at present as below,AS xyz is provided by my ISP.I need to change it to uvw,so I can have this peering with my existing ISP and new peering with my 2nd ISP through uvw, which is easy, but the issue come in because I am advertising 8 prefixes to my Crunnent ISP , out of 8 one Prefix is also provided by my ISP,and they only let me advertise that through xyz due to filters in place on their site.
Yes sure, but this feature was intended for migration scenarios not for normal running scenarios, try to design your network as optimum as you can:
"The BGP Support for Dual AS Configuration for Network AS Migrations feature allows you to merge a secondary autonomous system under a primary autonomous system, without disrupting customer peering sessions. The configuration of this feature is transparent to customer networks. This feature allows a router to appear, to external peers, as a member of secondary autonomous system during the autonomous-system migration. This feature allows the network operator to merge the autonomous systems and then later migrate customers to new configurations during normal service windows without disrupting existing peering arrangements."
"BGP prepends the autonomous system number from each BGP network that a route traverses to maintain network reachability information and to prevent routing loops. This feature should be configured only for autonomous-system migration, and should be deconfigured after the transition has been completed. This procedure should be attempted only by an experienced network operator, as routing loops can be created with improper configuration."
Hi everyone, I would like to thank you in advance for any help you can provide a newcomer like myself!
Im studying the 100-105 book by Odom and am currently on the topic of Port security. I purchased a used 2960 and I'm trying to follow a...
While deploying a number of 18xx/2802/3802 model access points (APs), which run AP-COS as their operating platform. It can be observed on some occasions that while many of their access points were able to join the fabric WLC withou...
I am going to design and build an LAN network under a tunnel underground with long distance between the switches.
I will have 2 Catalyst switches and 8 Industrial IE3000, and they will be connected with fiber.
For now I am planning on use Layer-2 s...