BGP Fundamentals
Last updated
Last updated
The following is pre-configured:
IPv4 and IPv6 addressing
IGP in AS100 and AS200
BGP peering sessions between the ISPs (AS1, AS2, AS3)
BGP peering sessions to the customers (AS100 and AS200) on XR5 and R6 only
Configure a full iBGP mesh in AS 100 and AS 200. Use Lo0 for peering. Use one peering address per address family.
Configure eBGP peering on R2, R3, XR7 and XR8.
On R1 advertise the four prefixes shown in the diagram. Do the same on XR9.
Ensure that R1 can ping prefixes in AS200
4. Before moving on, run clear bgp ipv4 uni * and clear bgp ipv6 uni * on R4. We need to ensure that R4 chooses the best route via XR5 due to the lowest RID. Without clearing, R4 may prefer R6 for routes it learned from R6 first. This is because oldest eBGP routes are preferred before using the RID tiebreaker.
All BGP routes have a nexthop of XR5
5. AS100 wants to receive traffic inbound from AS 3. Find two different ways to do this by only making changes on R2 and R3. You can look at the ISP routers but may not make changes to them. XR5 and R4 should have a best path to AS100 prefixes via R6.
Do the same exercise above for AS200.
6. R1 wants to ensure that outgoing traffic is forwarded towards AS 3. Find two separate ways to achieve this by only making changes on R1.
Revert the changes above, and find two ways to achieve this by only making changes to R2.
Do the same exercise above for AS200.
7. Find a way to make 100.0.0.0/23 appear to originate from AS 2 on R4. You can configure any router. Find a way to make 2001:db8:200::/63 originate from AS 3.
2. Make sure to use route-policies on XR7 and XR8 for the eBGP sessions. By default, all routes received and sent are blocked on an eBGP session. However for an iBGP session, all routes are permitted by default
3. You must ensure R2, R3, XR7, and XR8 are using next-hop-self for the iBGP peering to R1 and XR9. Without it, R1 and XR9 will have an unreachable next-hop for the routes.
5. You can either prepend the AS-PATH on routes advertised out R2 twice (so it has an AS_PATH length of 3), or use the community 2:90 to set LP low on XR5 so it will prefer the path via R6 which has a default LP of 100. If you only set LP on R6 high, XR5 will still choose its own directly connected path. Remember to use send-community on the neighbor statement. Do the same on XR8.
6. You can set weight on routes from R3 to a value of at least 1. You can set LP on routes from R3 to a value above 100. This is not the ideal way to do it though. On R2 you can set local pref low (below 100) on routes from XR5, or prepend them once with XR5’s AS number. You can also do this on R3 by setting local pref high (above 100) on routes from R6. In the real world, LP is the way you should handle this.
7. Configure aggregate-addresses on XR5 and R6 without using as-set. To achieve the goal we want to lose the original AS path information. With as-set we would preserve the original AS path information.
