BGP ASN - Best practice??

Unanswered Question

Dear friends,

I need to know the best practice for the following scenario.

I am Service Provider... and i have a Customer with lets say with 10 branches (which communicates with each other) and are terminating on 10 different Nodes (PE) in my core network.

1) Should i give different AS Number (private as numbers) to each branch ??

2) Should i give same AS number (private as numbers) to each branch and use as-override??

which approach is better, secure and less prone to mistakes.???

i have similar setup for customers both on MPLS (L3VPN) and IP only.

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
hamalawy1 Thu, 09/23/2010 - 00:47

well, it cuts down to the customer routing.. because having different ASs will definitly change his routing, but let's say that that doesn't matter.

giving each site a different AS will make the configuration easier because this will be the default behaviour of BGP.. which is good in some cases..

of course when it comes to having the same autonomous system in multiple sites, or in a hub and spoke topology. it will surely increase the complexity of it as one mistake can really spin the network around.. but i'm sure as you might know that you can use SOO to prevent loops from happening..

it really drops down to the network itself more than anything..


This Discussion