01-30-2009 05:45 AM - edited 03-04-2019 01:02 AM
We have a connection to Verizon MPLS via BGP.
My main branch ASA# is 65001.
We are upgrading out connection from X6 t1 Multilink to 15M DS3.
My loca AS# is 65001.
Verizon has given me the same AS# for my new connection into the MPLS cloud.
So the config would look something like this:
router bgp 65001
no synchronization
bgp log-neighbor-changes
network 0.0.0.0
neighbor 199.220.159.29 remote-as 65001
neighbor 199.220.159.29 version 4
neighbor 199.220.159.29 soft-reconfiguration inbound
Will this work?
01-30-2009 06:09 AM
BGP Internet AS numbers are unique identifier (http://www.bgp4.as/). My guess here is that your BGP AS number is not registered and you are using for your internal environment.
Regards,
01-30-2009 06:14 AM
Hello Richard,
I've seen other example of providers presenting to customer with a private AS number.
Actually, the Verizon router can pretend to be in private AS 65001 but it can have a real AS number that is one of Verizon public AS numbers or it is using another private AS number if it is in a BGP confederation.
I would expect the setup to work but to be sure you should contact Verizon.
For sure Verizon will give you the same private AS number even if you change type of links usually an AS number is associated to a customer
Hope to help
Giuseppe
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide