Provider Communities (XRv)

Topology: bgp-mh-xr

configure
load bootflash:communities.init.cfg
commit r
y

This lab is the same as the previous "Provider Communities" lab, just with XRv nodes instead of IOL nodes.

  • All links are in the format 100.X.Y.X/24.

    • For example, the link between R4 and R7 is 100.4.7.0/24.

  • Lo0 is X.X.X.X/32 and is used for iBGP

  • Lo1 is <AS>.0.0.X/32 and is used as a public IP address that is pingable. The public Lo1 addresses are aggregated into a /8 at each edge router.

  • eBGP and iBGP is fully preconfigured.

Configure communities in AS20 to accomplish the following:

  • AS10 is an upstream provider, AS40 is a transit peer, and AS50 is a customer. Only advertise customer and local routes to transit peers and providers. Do not let transit routes leak to upstream providers, and upstream routes leak to transit providers.

  • Allow AS50 to control their inbound traffic using the following table:

Community

Action

20:80

LP=80

20:90

LP=90

20:110

LP=110

20:120

LP=120

20:1

Prepend AS20 one additional time on advertisements to upstreams

20:2

Prepend AS20 two additional times on advertisements to upstreams

20:3

Prepend AS20 three additional times on advertisements to upstreams

Answer

Verification is the same as the previous lab which uses IOL nodes.

Last updated