BGP Allow-AS In Lab

Contents

Images used in lab: VIOS-ADVENTERPRISEK9-M), Version 15.9(3)M2

Topology Interfaces Only

Topology With IP Addressing

The last octet is the router number unless specified otherwise. Example: PE11's G0/0 is 10.10.111.11/24. Access to the initial configs, EVE-NG lab file and solution is below.

Intro

A BGP router will drop the prefix if it sees its own AS number in the AS Path. This is the default eBGP loop prevention behavior. This can cause problems in certain scenarios where multiple offices peer to the service provider using the same AS number. In this lab you’ll see this problem and modify the default behavior by using the BGP Allow-AS in feature. 

Tasks

  • Configure iBGP peerings between PE11 and PE12
  • Configure eBGP peerings between PE11 and CE1.
  • Configure eBGP peerings between PE12 and CE2.
  • Use their directly connected links for each peering.
  • On each CE router, advertise their loopback prefix into BGP.
  • Use next-hop-self to fix any next-hop processing issues.
  • Use the BGP Allow-AS In feature so CE1 and CE2 accept eachothers Loopback prefix in their BGP tables.
  • There must be full reachability between the CE's Loopbacks.

Download Lab

To download the EVE-NG topology file you'll need to be a member. You can register here, It will be right here once you log in.

Initial Configs

Solution

Allow-AS in is very similar to AS Override. Key points to remember: "Allow-AS in" is done on the customer side. "AS Override" is done on the provider side.

Hope you enjoyed this lab. If you have questions or need any help at all please leave a comment below and I’ll get back to you. 

Discussion

You'll need to be a member if you want to participate in the discussion. You can register right here. The discussion will be visible here once you log in.