ccie bgp case studies - routing tcp/ip vol2

Moderator: mike

Post Reply
taborn
Posts: 3
Joined: Mon Nov 27, 2017 6:03 am

ccie bgp case studies - routing tcp/ip vol2

Post by taborn » Wed Dec 06, 2017 11:12 am

BGP communities lab may be found here:
viewtopic.php?f=10&t=1359

########################################################################################################################################
BGP peer groups LAB - pg 265

topology
https://imgur.com/a/PFICc

tasks
1/ Using bgp peer groups (peer group name 'CLIENTS') on router Colorado, form neighbours with Utah, Vermont, California, Nevada, NewHampshire and R3

2/ BONUS
a) using as-path acl and filter lists, advertise any route that originated from Colorado to all EBGP neighbours
b) using as-path acl and filter lists, only accept networks from AS200,300,400,500,600

3/ Using bgp peer groups (peer group name 'LOCAL') on router Colorado, form neighbours with ibgp peers with NewMexico and Idaho. Apply remote-as 100, next-hop-self to the LOCAL peer group.

4/ BONUS
a) using as-path acl and filter lists, advertise routes from Utah, California and NewHampshire to Idaho and NewMexico

########################################################################################################################################

BGP Private AS lab - pg 284

topology
https://imgur.com/a/8r2v0

tasks
1/ utah, Vermont, California, Nevada and NewHampshire are all clients of AS100. Therefore, in order to conserve PUBLIC AS numbers, the clients should employ private AS numbers as seen in the topology. With the current configurations, we see that the public internet (Austria) can see all the private AS numbers

2/ On router Idaho, configure bgp in such a way that the private AS numbers are removed (i.e. we are advertising networks from AS100 and the private AS's as if they all originate from AS100)
You do not have the required permissions to view the files attached to this post.

Post Reply

Who is online

Users browsing this forum: No registered users and 2 guests