TechNetBuddy

Objectives

The simulator ticks each one as soon as the network meets it.

  1. On R1, build route-policy TAG: node 10 gives 10.1.1.0/24 community 100:1, node 20 gives 10.1.2.0/24 community no-export, node 30 permits the rest. Apply it to peer 10.0.12.2 export.
  2. On R1, peer 10.0.12.2 advertise-community: display bgp routing-table community on R2 shows both tags.
  3. On R2, ip community-filter basic C100 permit 100:1, and an import policy for peer 10.0.12.1 that sets local-preference 300 for it (node 20 permits the rest).
  4. R3 has 10.1.1.0/24 but not 10.1.2.0/24: R2 honours no-export at the AS border.
  5. R3 pings 10.1.1.1 from its loopback (ping -a 10.3.3.3 10.1.1.1).