You are on page 1of 4

1.

PC 110 cannot access R7/R8, fix the problem so that PC 110 can ping R7

2. R17 should have one default route which points to R12 via PPP as shown below
R17# ship route

S* 0.0.0.0/0 via 202.34.7.25


172.16.0.0/16 is variable subnetted, 4 subnets, 3 masks
C 172.16.3.56/30 is directly connected, ethernet 0/0
L 172.16.3.57/32 is dierctly connected, ethernet 0/0
C 172.16.3.88/29 is directly connected via Tunnel 0
L 172.16.3.90/32 is directly connected via Tunnel 0
202 .34.7.0/32 is subnetted. 2 subnets
C 202.34.7.25 is directly connected via Serial 1/0
C 202.34.7.26 is directly connected via Serial 1/0

3. When R1 tries to access the network 134.56.78.48/29 which is between R21 and R22, the traffic
should be load balanced as shown in the exibit.

R1# traceroute 134.56.78.49

1. 123.45.67.25 {mpls: label 26 exp 0} 0 msec


123.45.67.33 [mpls : label 30 exp 0] 0 msec
123.45.67.25 [mpls: label 26 exp 0] 0 msec
2. 123.45.67.17 0msec
123.45.67.1 0 msec
123.45.67.17

4. Traffic from R11 destined to loopback 0 of R14 should be load balanced via EIGRP as shown in
the exibit

R11# traceroute 123.14.14.14


1. 203.34.7.2
203.34.7.13
203.34.7.2
2. 203.34.7.9
203.34.7.6

5. When R12 traces the following routes


194.1.0.0/24
194.1.1.0/24
194.1.2.0/24
194.1.3.0/24

it should get the same result as shown in the following exibit

R12# traceroute 194.1.0.1

1. 202.12.5.1
202.12.5.2
202.12.5.1
2. 123.45.67.57 [AS 12345] [MPLS: Label 27 Exp 0]
123.45.67.49 [AS 12345] [MPLS: Label 27 Exp 0]
123.45.67.57 [AS 12345] [MPLS: Label 27 Exp 0]
3. 123.45.67.41 [AS 12345] [MPLS: Label 27 Exp 0]
4. 123.45.67.33 [AS 12345] [MPLS: Label 28 Exp 0]
5. 123.45.67.17
6. 123.10.1.5
--------------------------------
R12# traceroute 194.1.1.1

1. 202.12.5.1
202.12.5.2
202.12.5.1
2. 123.45.67.57 [AS 12345] [MPLS: Label 25 Exp 0]
123.45.67.49 [AS 12345] [MPLS: Label 25 Exp 0]
123.45.67.57 [AS 12345] [MPLS: Label 25 Exp 0]
3. 123.45.67.41 [AS 12345] [MPLS: Label 25 Exp 0]
4. 123.45.67.25 [AS 12345] [MPLS: Label 26 Exp 0]
5. 123.45.67.1
6. 123.10.1.1
------------------------------------------------

R12# traceroute 194.1.2.1

1. 202.12.5.1
202.12.5.2
202.12.5.1
2. 123.45.67.57 [AS 12345] [MPLS: Label 27 Exp 0]
123.45.67.49 [AS 12345] [MPLS: Label 27 Exp 0]
123.45.67.57 [AS 12345] [MPLS: Label 27 Exp 0]
3. 123.45.67.41 [AS 12345] [MPLS: Label 27 Exp 0]
4. 123.45.67.33 [AS 12345] [MPLS: Label 28 Exp 0]
5. 123.45.67.17
6. 123.10.1.5
-----------------------------------
R12# traceroute 194.1.3.1

1. 202.12.5.1
202.12.5.2
202.12.5.1
2. 123.45.67.57 [AS 12345] [MPLS: Label 27 Exp 0]
123.45.67.49 [AS 12345] [MPLS: Label 27 Exp 0]
123.45.67.57 [AS 12345] [MPLS: Label 27 Exp 0]
3. 123.45.67.41 [AS 12345] [MPLS: Label 27 Exp 0]
4. 123.45.67.33 [AS 12345] [MPLS: Label 28 Exp 0]
5. 123.45.67.17
6. 123.10.1.5

6. PC 103 is not able to ping 2001:0::26/128 located on R26, fix the problem so that the following is
successfull

PC 103 # ping 2001:0::26


!!!!!

7. DMVPN is configured on R15,17,18 and 19. R15 is hub and rest of devices are spokes. fix the
problem so that
server 2 can access PC 107 as shown below

Server2# ping 172.16.3.58


!!!!!

PC108# traceroute 172.16.3.82


1. 172.16.3.65
2. 172.16.3.89
3. 172.16.3.92
4. 172.16.3.82

8. MPLS/VPN
R7 and R8 are configured as backbone for VPN network. R9, R10, PC 104 and PC 106 are VPN clients.
ensure that
the output matches the following exibit.

PC104# ping 172.16.2.18


!!!!!

PC104# traceroute 172.16.2.18

1. 172.16.1.9
2. 172.16.1.1
3. 123.61.1.1
4. 123.45.67.34 [mpls: label 22/16]
5. 123.61.1.2 [mpls: label 16]
6. 123.61.1.1
7. 123.61.1.2
8. 123.45.67.26 [mpls: label 19/16]
9. 123.45.67.42 [mpls: label 19/16]
10. 123.61.2.1 [mpls: label 16]
11. 123.61.2.2
12. 172.16.2.2
13. 172.16.2.18

R1# sh bgp vpnv4 unicast all

RD: 12345:12345

*>i 0.0.0.0 123.3.3.3 0 100 0 61000 i


*i 123.4.4.4 0 100 0 61000 i
*>i 123.61.0.0/30 123.3.3.3 0 100 0 61000 i
*>i 172.9.9.9/32 123.5.5.5 0 100 0 61001 ?
*>i 172.10.10.10/32 123.6.6.6 0 100 0 61002 ?
*>i 172.16.1.0/30 123.5.5.5 0 100 0 61001 ?
*>i 172.16.1.8/30 123.5.5.5 11 100 0 61001 ?
*>i 172.16.2.0/30 123.6.6.6 0 100 0 61002 ?

9. R21 should manage NAS via telnet. Fix the problem so that telnet to NAS is successful as
shown in exibit.

R21# telnet 202.123.1.1 2323


trying 202.123.1.1, 2323....Open

user access vderification


password:
NAS>

10. There is DMVPN configured between R7 (Hub) and R24 (Spoke) via Nat Network (R23).
ensure that PC 109 can access server 1 as shown

PC109# ping 172.16.0.50


!!!!!

PC109# traceroute 172.16.0.50


1. 10.1.1.2
2. 172.16.0.54
3. 172.16.0.10
4. 172.16.0.50

You might also like