aboutsummaryrefslogtreecommitdiffstats
path: root/CCNP/ROUTE/BGP/GNS3Vault/Advanced/BGP ADVANCED.txt
blob: 37daa85a9b0c198e28c9cb08efabba751192c6e8 (about) (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
BGP ADVANCED
WRITTEN BY RENE MOLENAAR ON�24 JUNE 2010. POSTED IN�BGP
SCENARIO:
You have been working for a service provider called "FreedomBits" for quite some time and you have been responsible for the operation of all IGP's. Your�BGP�expert/colleague has won the X-factor competition and decided to start a singing career...it's up to you to upgrade your skills and become the new BGP guru in town. You have heard alot about BGP and even did some basic configurations but never tried anything with confederations or route-reflectors...time for a change!
GOAL:
All IP addresses have been preconfigured for you in the following order:

R1 - R2: 192.168.12.X
R1 - R3: 192.168.13.X
R3 - R4: 192.168.34.X

(Where X = Router number)

And so on...

Every router has a Loopback0 interface:
X.X.X.X

(Where X = Router number)
* Configure each Autonomous System (AS) with a different IGP:
AS100:�RIP
AS300:�OSPF
AS200:�EIGRP
AS400: OSPF
* Do not configure the IGP on the interfaces connecting to another AS. For example; R3 should not send any RIP routing updates towards R4.
* Make sure the loopbacks are advertised in the IGP's.
* Configure BGP on every router, make sure you have the right�IBGP�and�EBGP�configurations. AS300 has to be configured as a confederation.
* R1 has to be configured as a�route-reflector�for R2 and R3.
* Configure on all routers that BGP updates are sourced from the Loopback0 interface.
* Configure BGP authentication between R7 and R11, use password VAULT
* Make sure all BGP neighbor relationships are working before you continue with the next steps.
* Advertise all physical and loopback interfaces in BGP, you are not allowed to use the "network" command to achieve this.
* Achieve full connectivity, every IP address should be pingable. Use a�TCLSH�script to do this.
* When R4 sends a ping to the loopback interface of R1 it should choose the path through R2. You are only allowed to make changes on R3.
* Create another loopback interface on R1 with ip address 172.16.1.1 /24, advertise this in RIP.
* When R4 sends a ping to the 172.16.1.1 address it should take the path through R3, you are only allowed to make changes on R4.
* When R6 sends a ping towards the loopback interface on R11 it should go through AS300.
* R7 should prefer the path through R11 for all external networks except for 172.16.1.1.

It took me 1000s of hours reading books and doing labs, making mistakes over and over again until I mastered all the routing protocols for CCNP.
Would you like to be a�master of routing�too? In a short time without having to read 900 page books or google the answers to your questions and browsing through forums?
I collected all my knowledge and created a single ebook�for you�that has everything you need to know to become amaster of routing.
You will learn all the�secrets�about�OSPF,�EIGRP, BGP and more.
Does this sound interesting to you?�Take a look here and let me show you how to Master CCNP ROUTE
IOS:
c3640-jk9s-mz.124-16.bin