aboutsummaryrefslogtreecommitdiffstats
path: root/CCNP/ROUTE/EIGRP/GNS3vault/EIGRP MULTIPOINT BANDWIDTH PACING.txt
blob: b681f38d4cad8a0701c01c8726dbfcd27a543ca0 (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
EIGRP MULTIPOINT BANDWIDTH PACING
WRITTEN BY RENE MOLENAAR ON�26 AUGUST 2011. POSTED IN�EIGRP
SCENARIO:
A large international ISP has hired you as one of their network engineers. The ISP still has a fairly large customer that is using an older�frame-relay�network. All of your colleagues are too busy working with�MPLS�and you are the only one who is capable of fixing frame-relay problems. The network is experiencing congestion especially when router Paris is sending traffic to router New York. Can you fix this network?
GOAL:
* All IP addresses have been preconfigured for you as specified in the topology picture.
* Every router has a loopback0 interface:
Tilburg: 1.1.1.1 /24
NewDelhi: 2.2.2.2 /24
Berlin: 3.3.3.3 /24
Paris: 4.4.4.4 /24
NewYork: 5.5.5.5 /24
* You are not allowed to make any changes to the frame-relay configurations.
* The ISP has configured the following CIR for each PVC:
NewDelhi: 128kbps
Berlin: 128kbps
Paris: 256kbps
NewYork: 64kbps
* Configure�EIGRP�AS 1 on all routers and make sure you have full connectivity.
* Configure your network so the bandwidth reflects the CIR on the PVCs and there are no congestion problems with EIGRP.
IOS:
c3640-jk9s-mz.124-16.bin
TOPOLOGY: