Objectives:
The network shown on the diagram above doesn't have a full connectivity by itself. The full connectivity isn't needed for this lab because all actions should happen in AS 5500 on routers R1, R2 and R3. You don't need to perform a ping test to check the result caused by configuration changes. The output of "show ip route" command is going to be enough to check the results.
- Perform all necessary configuration changes on routers R1, R2 and R3 in order for router R1 to receive routes to 150.1.50.0/24, 150.2.50.0/24, 200.50.2.0/24 and 200.60.2.0/24 networks;
- Using Cisco proprietary attribute called "WEIGHT" influence R1's BGP path decisioning - it should take a path to networks 200.50.2.0/24 and 200.60.2.0/24 via R4;
- Using an attribute "LOCAL_PREF" influence R1's BGP path decisioning only for 150.2.50.0/24 - R1 should take a path to this network via R5;
Note:
BGP Route Decision
- Ignore routes with an inaccessible next hop address
- Prefer the path with the highest WEIGHT.
- Prefer the path with the highest LOCAL_PREF.
- Prefer the path that was locally originated via a network command
- Prefer the path with the shortest ASPATH.
- Prefer the path with the lowest origin type.
- Prefer the path with the lowest multi-exit discriminator (MED).
- Prefer eBGP over iBGP paths.
- Prefer the path with the lowest IGP metric to the BGP next hop.
- Determine if multiple paths require installation in the routing table for BGP Multipath. ID.
- When both paths are external, prefer the path that was received first (the oldest one).
- Prefer the route that comes from the BGP router with the lowest router ID.
- If the originator or router ID is the same for multiple paths, prefer the path with the minimum cluster list length.
- Prefer the path that comes from the lowest neighbor address.
Комментариев нет:
Отправить комментарий