Documente Academic
Documente Profesional
Documente Cultură
Version 4.0
Authored By:
Khawar Butt
CCIE # 12353
(R/S, Security, SP, Voice)
1 of 241
2 of 241
S 0/0
R2
S 0/0
Frame-Relay
R3
S 0/0
Task 1
Configure the Frame-relay switch to connect R1, R2 & R3. R1 should act
as the hub to connect for R2 and R3. Use the following for the DLCI
assignments:
R1
R1
R2
R3
>
>
>
>
R2
R3
R1
R1
102
103
201
302
3 of 241
Frame-Relay Switch
Frame-relay switching
!
Interface S0/1
Description Connection to R1
Encap frame-relay
Frame-relay intf-type dce
Clock rate 64000
Frame-relay route 102 interface
Frame-relay route 103 interface
No shut
!
Interface S0/2
Description Connection to R2
Encap frame-relay
Frame-relay intf-type dce
Clock rate 64000
Frame-relay route 201 interface
No shut
!
Interface S0/3
Description Connection to R3
Encap frame-relay
Frame-relay intf-type dce
Clock rate 64000
Frame-relay route 301 interface
No shut
S0/2 201
S0/3 301
S0/1 102
S0/1 103
4 of 241
Task 2
Configure the R1, R2 and R3 to communicate to each other. Use the
following IP Addressing scheme. Make sure that Inverse-ARP is not used
to setup the Frame-relay mappings. Make sure routing protocols can run
between the Hub and Spokes. All devices should be able to Ping each
other and their local interfaces:
R1 192.1.123.1/24
R2 192.1.123.2/24
R3 192.1.123.3/24
R1
Interface Serial0/0
Ip address 192.1.123.1 255.255.255.0
Encapsulation frame
No frame-relay inverse-arp
Frame-relay map ip 192.1.123.2 102 Broadcast
Frame-relay map ip 192.1.123.3 103 Broadcast
Frame-relay map ip 192.1.123.4 102
No shut
R2
Interface Serial0/0
Ip address 192.1.123.2 255.255.255.0
Encapsulation frame
No frame-relay inverse-arp
Frame-relay map ip 192.1.123.1 201 Broadcast
Frame-relay map ip 192.1.123.3 201
Frame-relay map ip 192.1.123.2 201
No shut
R3
Interface Serial0/0
Ip address 192.1.123.3 255.255.255.0
Encapsulation frame
No frame-relay inverse-arp
Frame-relay map ip 192.1.123.1 301 Broadcast
Frame-relay map ip 192.1.123.2 301
Frame-relay map ip 192.1.123.3 301
No shut
5 of 241
R1
R2
Interface Loopback0
Ip address 1.1.1.1 255.0.0.0
R3
Interface Loopback0
Ip address 2.2.2.2 255.0.0.0
Interface Loopback0
Ip address 3.3.3.3 255.0.0.0
Task 2
Configure RIPv2 on R1, R2 & R3. Make sure all routes are getting
propagated.
R1
R2
Router RIP
Version 2
No auto-summary
Network 1.0.0.0
Network 192.1.123.0
R3
Router RIP
Version 2
No auto-summary
Network 2.0.0.0
Network 192.1.123.0
Router RIP
Version 2
No auto-summary
Network 3.0.0.0
Network 192.1.123.0
Note:
Although Split-horizon should have blocked R1 propagating R2 routes
towards R3 and vice-versa, it is not. The reason behind it is that when
you enable Frame-relay on a Physical interface, it automatically disables
Split-horizon on the interface for Distance Vector Routing protocols. This
Copyrights Netmetric Solutions FZC 2006-2010
Website: http://www.netmetricsolutionsfzc.com; Email: khawarb@khawarb.com
6 of 241
behaviour is only for Physical interfaces and not for Multipoint Subinterfaces.
7 of 241
R2
No Router RIP
R3
No Router RIP
No Router RIP
Task 2
Configure EIGRP on R1, R2 & R3 in AS 123. Make sure all routes are
getting propagated.
R1
R2
8 of 241
S 0/0 .123
R2
S 0/0 .14
S 0/0 .14
S 0/0
R4
Frame-Relay
S 0/0
R3
Task 1
Configure the routers connected to the frame-relay cloud as follows:
o R1 (The HUB) must be configured with two sub-interfaces, one
of the two sub-interfaces must be configured to connect R1 to
R4, this sub-interface should be configured in a point-to-point
manner using the following IP addressing:
R1 = 192.1.14.1 /24
R4 = 192.1.14.4 /24.
o The second sub-interface on R1 must be configured in a
multipoint manner, and this sub-interface must be configured
to connect R1 to routers R2 and R3 using the following IP
addressing:
R1 = 192.1.123.1 /24
R2 = 192.1.123.2 /24
Copyrights Netmetric Solutions FZC 2006-2010
Website: http://www.netmetricsolutionsfzc.com; Email: khawarb@khawarb.com
9 of 241
R3 = 192.1.123.3 /24
o R2 is not a Cisco router. Set the encapsulation accordingly.
o Routers R2, R3 should not be configured with a sub-interface
and these routers should NOT rely on Inverse-arp.
o R4 should be configured with a sub-interface in a point-to-point
manner.
o The routers connecting to the frame-relay cloud should be
configured in a hub and spoke, with R1 being the hub and R2,
R3 and R4 the spokes.
o Ensure that the routers on the 192.1.123.0/24 network can
ping every IP address including their own within their IP
address space.
R1
Interface Serial0/0
Encapsulation frame-relay
No frame-relay inverse
No shut
!
Int S0/0.14 point-to-point
Ip address 192.1.14.1 255.255.255.0
Frame-relay interface-dlci 104
!
Int S0/0.123 multipoint
Ip address 192.1.123.1 255.255.255.0
Frame-relay map ip 192.1.123.2 102 ietf broadcast
Frame-relay map ip 192.1.123.3 103 broadcast
Frame-relay map ip 192.1.123.1 103
R2
Int S0/0
Ip address 192.1.123.2 255.255.255.0
Encapsulation frame ietf
No frame-relay inverse
Frame-relay map ip 192.1.123.1 201 broadcast
Frame-relay map ip 192.1.123.3 201
Frame-relay map ip 192.1.123.2 201
No shut
10 of 241
R3
Int S0/0
Encapsulation frame
Ip address 192.1.123.3 255.255.255.0
Frame-relay map ip 192.1.123.1 301 broadcast
Frame-relay map ip 192.1.123.2 301 ietf
Frame-relay map ip 192.1.123.3 301
No frame-relay inverse
No shut
R4
Int S0/0
Encap frame
No frame-relay inverse
No shut
!
Inter S0/0.14 point-to-point
Ip address 192.1.14.4 255.255.255.0
Frame-relay interface-dlci 401
Task 2
Ensure that R1 and R4 use CHAP authentication using Cisco as the
password. These routers must authenticate each other before they can
communicate.
R1
Username R4 password Cisco
Interface S0/0.14
No ip address
Inter virtual-template 1
Ip address 192.1.14.1 255.255.255.0
Ppp authentication chap
Int S0/0.14
Frame-relay interface-dlci 104 ppp virtual-template 1
R4
Username R1 password Cisco
Inter S0/0.14
No ip address
Copyrights Netmetric Solutions FZC 2006-2010
Website: http://www.netmetricsolutionsfzc.com; Email: khawarb@khawarb.com
11 of 241
Inter virtual-template 1
Ip address 192.1.14.4 255.255.255.0
Ppp authentication chap
Int S0/0.41
Frame-relay interface-dlci 401 ppp virtual-template 1
12 of 241
13 of 241
R5
F 0/0 (.5)
192.1.15.0/24 VLAN 10
F 0/0.1 (.1)
R1
F 0/0.2 (.1)
192.1.13.0/24 VLAN 20
F0/0.1 (.3)
R3
F0/0.2 (.3)
192.1.34.0/24 VLAN 30
VLAN 30 (.15)
F 0/0 (.4)
R4
SW1
VLAN 40 (.15)
192.1.2.0/24 VLAN 40
F 0/0 (.2)
R2
Task 1
Configure Switch1 as the VTP Server and the other Switch(s) as VTP
Clients. Use CCIE as the Domain name. Authenticate the relationship
using CCIERS as the password.
SW1
SW2
14 of 241
Task 2
Ensure that you can enhance network bandwidth use through the trunk
ports by reducing the unnecessary traffic flooding of VLANs throughout
the switches in your network.
All Switches
Vtp pruning
Task 3
Ensure that the Trunk ports of your Rack are statically configured to
trunk using an industry standard protocol. Configure these ports such
that they will trunk even if the negotiation fails. Also make sure to
disable DTP on the trunk interfaces.
All Switches
Interface range F0/XX XX
Switchport trunk encapsulation dot1q
Switchport mode trunk
Switchport nonegotiate
Task 4
Assign Ports to the appropriate VLANs based on the Network Diagram.
Use the physical topology diagram for your rack to accomplish this. Make
sure the ports are either set to Trunk or Access statically.
SW1
VLAN 10
VLAN 20
VLAN 30
VLAN40
SWx
interface F0/XX
Switchport mode access
Switchport access vlan XX
!
Copyrights Netmetric Solutions FZC 2006-2010
Website: http://www.netmetricsolutionsfzc.com; Email: khawarb@khawarb.com
15 of 241
interface F0/XX
Switchport trunk encapsulation dot1q
Swithcport mode trunk
Task 5
Test by pinging directly connected interfaces on each router and on the
Switch1.
16 of 241
Module 3 RIP V2
17 of 241
R2
Router Rip
Version 2
No auto-summary
Network 1.0.0.0
Network 192.1.13.0
Network 192.1.15.0
R3
Router Rip
Version 2
No auto-summary
Network 2.0.0.0
Network 192.1.2.0
Router Rip
Version 2
No auto-summary
Network 3.0.0.0
Network 192.1.34.0
Network 192.1.13.0
R5
Router Rip
Version 2
No auto-summary
Network 4.0.0.0
Network 192.1.34.0
Router Rip
Version 2
No auto-summary
Network 5.0.0.0
Network 192.1.15.0
IP Routing
!
Router RIP
Version 2
No auto-summary
Network 15.0.0.0
Network 192.1.2.0
Network 192.1.34.0
R4
Switch1
18 of 241
R5
Task 2
Configure MD5 authentication for all links except the previously
configured link between R1 and R5. Use the same key and key-string.
R1
R2
Interface F 0/0.2
Ip rip authentication key-chain
AUTH
IP rip authentication mode MD5
R3
Key chain AUTH
Key 1
Key-string ccie
!
Interface F 0/0.1
Ip rip authentication key-chain
AUTH
IP rip authentication mode MD5
!
Interface F 0/0.2
Ip rip authentication key-chain
19 of 241
AUTH
IP rip authentication mode MD5
SW1
Key chain AUTH
Key 1
Key-string ccie
!
Interface VLAN 30
Ip rip authentication
AUTH
Ip rip authentication
!
Interface VLAN 40
Ip rip authentication
AUTH
Ip rip authentication
key-chain
mode MD5
key-chain
mode MD5
20 of 241
21:
22:
23:
24:
25:
26:
201.1.1.1/24
201.1.2.1/24
201.1.3.1/24
201.1.4.1/24
201.1.5.1/24
201.1.6.1/24
R3
Interface loopback 21
Ip address 201.1.1.1 255.255.255.0
Interface loopback 22
Ip address 201.1.2.1 255.255.255.0
Interface loopback 23
Ip address 201.1.3.1 255.255.255.0
Interface loopback 24
Ip address 201.1.4.1 255.255.255.0
Interface loopback 25
Ip address 201.1.5.1 255.255.255.0
Interface loopback 26
Ip address 201.1.6.1 255.255.255.0
Task 2
R1 should only receive routes from the 201.1.X.0 range that have an
even number in the 3rd Octet. Use the minimum number of lines possible
to accomplish this task. No configuration should be done on R1. Make
sure R4 and Switch1 receive all 201.1.X.0 routes.
R3
Access-list 2 deny 201.1.1.0 0.0.254.255
Access-list 2 permit any
!
Router RIP
Network 201.1.1.0
Network 201.1.2.0
Network 201.1.3.0
Copyrights Netmetric Solutions FZC 2006-2010
Website: http://www.netmetricsolutionsfzc.com; Email: khawarb@khawarb.com
21 of 241
Network 201.1.4.0
Network 201.1.5.0
Network 201.1.6.0
Distribute-list 2 out F0/0.1
22 of 241
21:
22:
23:
24:
25:
26:
150.50.1.1/24
150.50.2.1/24
150.50.3.1/24
205.1.1.33/27
206.1.1.17/28
107.1.1.1/16
R5
Interface loopback 21
Ip address 150.50.1.1 255.255.255.0
Interface loopback 22
Ip address 150.50.2.1 255.255.255.0
Interface loopback 23
Ip address 150.50.3.1 255.255.255.0
Interface loopback 24
Ip address 205.1.1.33 255.255.255.224
Interface loopback 25
Ip address 206.1.1.1 255.255.255.240
Interface loopback 26
Ip address 107.1.1.1 255.255.0.0
!
Router Rip
Network 150.50.0.0
Network 205.1.1.0
Network 206.1.1.0
Network 107.0.0.0
Task 2
R1 should only receive prefixes with a prefix-length of 8 to 24 from R5.
Configure the Filtering on R1.
R1
ip prefix-list PLIST permit 0.0.0.0/0 ge 8 le 24
!
Copyrights Netmetric Solutions FZC 2006-2010
Website: http://www.netmetricsolutionsfzc.com; Email: khawarb@khawarb.com
23 of 241
Router RIP
distribute-list prefix PLIST in F0/0.1
24 of 241
41:
42:
43:
44:
45:
46:
47:
48:
154.1.8.1/24
154.1.9.1/24
154.1.10.1/24
154.1.11.1/24
154.1.12.1/24
154.1.13.1/24
154.1.14.1/24
154.1.15.1/24
SW1
Interface loopback 41
Ip address 154.1.8.1 255.255.255.0
Interface loopback 42
Ip address 154.1.9.1 255.255.255.0
Interface loopback 43
Ip address 154.1.10.1 255.255.255.0
Interface loopback 44
Ip address 154.1.11.1 255.255.255.0
Interface loopback 45
Ip address 154.1.12.1 255.255.255.0
Interface loopback 46
Ip address 154.1.13.1 255.255.255.0
Interface loopback 47
Ip address 154.1.14.1 255.255.255.0
Interface loopback 48
Ip address 154.1.15.1 255.255.255.0
!
Router Rip
Network 154.1.0.0
Task 2
Ensure that all routers except R2 only get a summary route from
Switch1 for the new Loopback interfaces that were created in Task 1. R2
should get all the specific routes. Do not enable auto summary on SW1.
SW1
Copyrights Netmetric Solutions FZC 2006-2010
Website: http://www.netmetricsolutionsfzc.com; Email: khawarb@khawarb.com
25 of 241
int VLAN 30
ip summary-address rip 154.1.8.0 255.255.248.0
26 of 241
Module 4 EIGRP
27 of 241
R1
Loopback 0
R2
F 0/0
F 0/0
Loopback 0
S 0/0
S 0/0
Loopback 0
F 0/0
F 0/0
Loopback 0
R4
R3
IP Address
1.1.1.1
192.1.12.1
Subnet Mask
255.0.0.0
255.255.255.0
IP Address
2.2.2.2
192.1.12.2
192.1.23.2
Subnet Mask
255.0.0.0
255.255.255.0
255.255.255.0
IP Address
3.3.3.3
192.1.23.3
192.1.34.3
Subnet Mask
255.0.0.0
255.255.255.0
255.255.255.0
R2
Interface
Loopback 0
F 0/0
S 0/0
R3
Interface
Loopback 0
S 0/0
F 0/0
28 of 241
R4
Interface
Loopback 0
F 0/0
IP Address
4.4.4.4
192.1.34.4
Subnet Mask
255.0.0.0
255.255.255.0
Task 1
Configure the interfaces with the appropriate addresses. Configure the
Serial interfaces between R2 and R3 using Frame Relay. Configure the
interface as a Regular Frame Relay interface. Configure the Frame Relay
mapping manually.
R1
R2
Interface Loopback 0
Ip address 1.1.1.1 255.0.0.0
!
Interface F 0/0
Ip address 192.1.12.1 255.255.255.0
No shut
Interface Loopback 0
Ip address 2.2.2.2 255.0.0.0
!
Interface F 0/0
Ip address 192.1.12.2 255.255.255.0
No shut
!
Interface S 0/0
Ip address 192.1.23.2 255.255.255.0
Encap frame-relay
No frame-relay inverse-arp
Frame-relay map ip 192.1.23.3 203 broad
No shut
R4
R3
Interface Loopback 0
Ip address 3.3.3.3 255.0.0.0
!
Interface F 0/0
Ip address 192.1.34.3 255.255.255.0
No shut
!
Interface S 0/0
Ip address 192.1.23.3 255.255.255.0
Encap frame-relay
No frame-relay inverse-arp
Frame-relay map ip 192.1.23.2 302 broad
No shut
Interface Loopback 0
Ip address 4.4.4.4 255.0.0.0
!
Interface F 0/0
Ip address 192.1.34.4 255.255.255.0
No shut
Task 2
Configure EIGRP on all 4 routers in AS 12353. Disable Auto-summary.
Copyrights Netmetric Solutions FZC 2006-2010
Website: http://www.netmetricsolutionsfzc.com; Email: khawarb@khawarb.com
29 of 241
R1
R2
R3
Router EIGRP 12353
No auto-summary
Network 3.0.0.0
Network 192.1.34.0
Network 192.1.23.0
30 of 241
31 of 241
32 of 241
R2
Task 2
Change the administrative distance of all internal and external EIGRP
networks to be 95.
R1
R2
Task 3
Ensure that R2 never uses more than 45% of the bandwidth for EIGRP
updates; you should use an EIGRP specific command to accomplish this
task.
R2
Interface S 0/0
ip bandwidth-percent eigrp 12353 45
Interface F 0/0
ip bandwidth-percent eigrp 12353 45
33 of 241
21:
22:
23:
24:
25:
26:
201.1.1.1/24
201.1.2.1/24
201.1.3.1/24
201.1.4.1/24
201.1.5.1/24
201.1.6.1/24
R2
Interface loopback 21
Ip address 201.1.1.1 255.255.255.0
Interface loopback 22
Ip address 201.1.2.1 255.255.255.0
Interface loopback 23
Ip address 201.1.3.1 255.255.255.0
Interface loopback 24
Ip address 201.1.4.1 255.255.255.0
Interface loopback 25
Ip address 201.1.5.1 255.255.255.0
Interface loopback 26
Ip address 201.1.6.1 255.255.255.0
Task 2
R1 should only receive routes from the 201.1.X.0 range that have an
even number in the 3rd Octet. Use the minimum number of lines possible
to accomplish this task. No configuration should be done on R1. Make
sure R3 and R4 receive all 201.1.X.0 routes.
R2
Access-list 2 deny 201.1.1.0 0.0.254.255
Access-list 2 permit any
!
Router EIGRP 12353
Network 201.1.1.0
Network 201.1.2.0
Network 201.1.3.0
Network 201.1.4.0
Copyrights Netmetric Solutions FZC 2006-2010
Website: http://www.netmetricsolutionsfzc.com; Email: khawarb@khawarb.com
34 of 241
Network 201.1.5.0
Network 201.1.6.0
Distribute-list 2 out F 0/0
35 of 241
21:
22:
23:
24:
25:
26:
150.50.1.1/24
150.50.2.1/24
150.50.3.1/24
205.1.1.33/27
206.1.1.17/28
107.1.1.1/16
R3
Interface loopback 21
Ip address 150.50.1.1 255.255.255.0
Interface loopback 22
Ip address 150.50.2.1 255.255.255.0
Interface loopback 23
Ip address 150.50.3.1 255.255.255.0
Interface loopback 24
Ip address 205.1.1.33 255.255.255.224
Interface loopback 25
Ip address 206.1.1.1 255.255.255.240
Interface loopback 26
Ip address 107.1.1.1 255.255.0.0
!
Router EIGRP 12353
Network 150.50.0.0
Network 205.1.1.0
Network 206.1.1.0
Network 107.0.0.0
Task 2
R4 should only receive prefixes with a prefix-length of 8 to 24 from R3.
R4
ip prefix-list ABC permit 0.0.0.0/0 ge 8 le 24
!
Router EIGRP 12353
distribute-list prefix ABC in F0/0
Copyrights Netmetric Solutions FZC 2006-2010
Website: http://www.netmetricsolutionsfzc.com; Email: khawarb@khawarb.com
36 of 241
41:
42:
43:
44:
45:
46:
47:
48:
194.1.8.1/24
194.1.9.1/24
194.1.10.1/24
194.1.11.1/24
194.1.12.1/24
194.1.13.1/24
194.1.14.1/24
194.1.15.1/24
R3
Interface loopback 41
Ip address 194.1.8.1 255.255.255.0
Interface loopback 42
Ip address 194.1.9.1 255.255.255.0
Interface loopback 43
Ip address 194.1.10.1 255.255.255.0
Interface loopback 44
Ip address 194.1.11.1 255.255.255.0
Interface loopback 45
Ip address 194.1.12.1 255.255.255.0
Interface loopback 46
Ip address 194.1.13.1 255.255.255.0
Interface loopback 47
Ip address 194.1.14.1 255.255.255.0
Interface loopback 48
Ip address 194.1.15.1 255.255.255.0
!
Router EIGRP 12353
Network 194.1.8.0
Network 194.1.9.0
Network 194.1.10.0
Network 194.1.110
Network 194.1.12.0
Network 194.1.13.0
Copyrights Netmetric Solutions FZC 2006-2010
Website: http://www.netmetricsolutionsfzc.com; Email: khawarb@khawarb.com
37 of 241
Network 194.1.14.0
Network 194.1.150
Task 2
Ensure that all routers only get a summary route from R3 for the new
Loopback interfaces that were created in Task 1. R3 should NOT enable
auto summary.
R3
int F 0/0
ip summary-address eigrp 12353 194.1.8.0 255.255.248.0
!
int S 0/0
ip summary-address eigrp 12353 194.1.8.0 255.255.248.0
38 of 241
39 of 241
Module 5 OSPF
40 of 241
R1
L0 2.2.2.2/8
L0 1.1.1.1/8
F 0/0 (.2)
F 0/0 (.1)
L0 192.1.100.0/24
F 0/0 (.4)
F 0/0 (.3)
L0 3.3.3.3/8
L0 4.4.4.4/8
R3
R4
IP Address
1.1.1.1
192.1.100.1
Subnet Mask
255.0.0.0
255.255.255.0
IP Address
2.2.2.2
192.1.100.2
Subnet Mask
255.0.0.0
255.255.255.0
IP Address
3.3.3.3
192.1.100.3
Subnet Mask
255.0.0.0
255.255.255.0
IP Address
4.4.4.4
192.1.100.4
Subnet Mask
255.0.0.0
255.255.255.0
R2
Interface
Loopback 0
F 0/0
R3
Interface
Loopback 0
F 0/0
R4
Interface
Loopback 0
F 0/0
41 of 241
R2
Router OSPF 1
Router-id 11.11.11.11
Network 1.1.1.1 0.0.0.0 area 0
Network 192.1.100.1 0.0.0.0 area 0
R3
Router OSPF 1
Router-id 22.22.22.22
Network 2.2.2.2 0.0.0.0 area 0
Network 192.1.100.2 0.0.0.0 area 0
R4
Router OSPF 1
Router-id 33.33.33.33
Network 3.3.3.3 0.0.0.0 area 0
Network 192.1.100.3 0.0.0.0 area 0
Router OSPF 1
Router-id 44.44.44.44
Network 4.4.4.4 0.0.0.0 area 0
Network 192.1.100.4 0.0.0.0 area 0
Task 2
Configure the routers such that R1 becomes the DR and R2 as the BDR
on the 100 Network.
R1
R2
Interface E 0/0
Ip ospf priority 100
Interface E 0/0
Ip ospf priority 50
Note: Issue the Clear ip ospf process command to reset the OSPF
process for the change to take effect.
42 of 241
R1
R2
R4
Frame-Relay
R3
Task 1
Configure the following loopback on all the routers:
R1 Loopback 0 1.1.1.1/8
R2 Loopback 0 2.2.2.2/8
R3 Loopback 0 3.3.3.3/8
R4 Loopback 0 4.4.4.4/8
R1
R2
Interface Loopback 0
Ip address 1.1.1.1 255.0.0.0
R3
Interface Loopback 0
Ip address 2.2.2.2 255.0.0.0
R4
Interface Loopback 0
Ip address 3.3.3.3 255.0.0.0
Interface Loopback 0
Ip address 4.4.4.4 255.0.0.0
43 of 241
Task 2
Configure the link between R1 and R4 using Frame Relay. Keep in mind
that R1 will also be connected to R2 and R3 over a Multipoint interface.
Do not create any sub-interfaces on R4. Do not rely on Inverse ARP for
Frame Relay mappings. Do not use the Frame-relay map command on
R1 for this task. Use 192.1.14.0/24 as the network for this link.
R1
R4
Interface S 0/0
Encap frame-relay
No frame-relay inverse-ARP
No shut
Interface S0/0.14 point-to-point
Ip address 192.1.14.1 255.255.255.0
Frame-relay interface-dlci 104
Interface S0/0
Ip address 192.1.14.4 255.255.255.0
Encap frame-relay
No frame-relay inverse-arp
Frame-relay map ip 192.1.14.1 401 broad
No shut
Task 3
Configure the link between R1, R2 and R3 using Frame Relay. This link
should be a multipoint link Do not create any sub-interfaces on R2 and
R3. Do not rely on Inverse ARP for Frame Relay mappings. Use
192.1.123.0/24 as the network for this link. All routers should be able to
ping each other and their own local frame-relay interfaces.
R1
Interface S0/0.23 multipoint
Ip address 192.1.123.1 255.255.255.0
Frame-relay map ip 192.1.123.1 102 broad
Frame-relay map ip 192.1.123.2 102 broad
Frame-relay map ip 192.1.123.3 103
R2
Interface S0/0
Ip address 192.1.123.2 255.255.255.0
Encap frame-relay
No frame-relay inverse-arp
Frame-relay map ip 192.1.123.1 201 broad
Frame-relay map ip 192.1.123.2 201
Frame-relay map ip 192.1.123.3 201
No shut
R3
Interface S0/0
Ip address 192.1.123.3 255.255.255.0
Copyrights Netmetric Solutions FZC 2006-2010
Website: http://www.netmetricsolutionsfzc.com; Email: khawarb@khawarb.com
44 of 241
Encap frame-relay
No frame-relay inverse-arp
Frame-relay map ip 192.1.123.1 301 broad
Frame-relay map ip 192.1.123.2 301
Frame-relay map ip 192.1.123.3 301
No shut
Task 4
Configure OSPF in Area 0 as the routing protocol between R1, R2, R3
and R4. All loopback networks should be visible in all routing tables.
They should be using a /8 mask. Hard-code the router ID based on the
Loopback 0 addresses. Do not use the OSPF network type broadcast on
any of the Frame Relay links.
R1
Interface S0/0.23
Ip ospf network point-to-multipoint
!
Interface Loopback 0
Ip ospf network point-to-point
!
Router OSPF 1
Router-id 1.1.1.1
Network 1.0.0.0 0.255.255.255 area 0
Network 192.1.123.0 0.0.0.255 area 0
Network 192.1.14.0 0.0.0.255 area 0
R2
Interface S0/0
Ip ospf network point-to-multipoint
!
Interface Loopback 0
Ip ospf network point-to-point
!
Router OSPF 1
Router-id 2.2.2.2
Network 2.0.0.0 0.255.255.255 area 0
Network 192.1.123.0 0.0.0.255 area 0
R3
Interface S0/0
Ip ospf network point-to-multipoint
!
Interface Loopback 0
Copyrights Netmetric Solutions FZC 2006-2010
Website: http://www.netmetricsolutionsfzc.com; Email: khawarb@khawarb.com
45 of 241
46 of 241
R1
Lo 0
R2
F 0/0
Lo 0
F 0/0
192.1.12.0/24
S 0/0
R4
192.1.234.0/24
Switch 1
S 0/0
192.1.3.0/24
Lo 0
VLAN 3
Lo 0
F 0/0
R3
VLAN 5
F 0/0
192.1.5.0/24
R5
R1
Interface
Loopback 0
F 0/0
IP Address
1.1.1.1
192.1.12.1
Subnet Mask
255.0. 0.0
255.255.255.0
IP Address
192.1.12.2
192.1.234.2
2.2.2.2
Subnet Mask
255.255.255.0
255.255.255.0
255.0.0.0
IP Address
192.1.234.3
192.1.3.3
3.3.3.3
Subnet Mask
255.255.255.0
255.255.255.0
255.0.0.0
R2
Interface
F 0/0
S 0/0
Loopback 0
R3
Interface
S 0/0
F 0/0
Loopback 0
47 of 241
R4
Interface
Loopback 0
S 0/0
IP Address
4.4.4.4
192.1.234.4
Subnet Mask
255.0.0.0
255.255.255.0
IP Address
5.5.5.5
192.1.5.5
Subnet Mask
255.0.0.0
255.255.255.0
IP Address
55.55.55.55
192.1.3.33
192.1.5.55
Subnet Mask
255.0.0.0
255.255.255.0
255.255.255.0
R5
Interface
Loopback 0
F 0/0
SW1
Interface
Loopback 0
VLAN 3
VLAN 5
Interface Configuration
R1
interface Loopback0
ip address 1.1.1.1 255.0.0.0
!
interface F 0/0
ip address 192.1.12.1 255.255.255.0
no shutdown
R2
interface Loopback0
ip address 2.2.2.2 255.0.0.0
!
Interface F0/0
ip address 192.1.12.2 255.255.255.0
no shut down
!
interface Serial0/0
ip address 192.1.234.2 255.255.255.0
encapsulation frame-relay
frame-relay map ip 192.1.234.3 203 broadcast
frame-relay map ip 192.1.234.4 204 broadcast
no frame-relay inverse-arp
no shutdown
Copyrights Netmetric Solutions FZC 2006-2010
Website: http://www.netmetricsolutionsfzc.com; Email: khawarb@khawarb.com
48 of 241
R3
interface Loopback0
ip address 3.3.3.3 255.0.0.0
!
interface F 0/0
ip address 192.1.3.3 255.255.255.0
no shutdown
!
interface Serial0/0
ip address 192.1.234.3 255.255.255.0
encapsulation frame-relay
frame-relay map ip 192.1.234.2 302 broadcast
frame-relay map ip 192.1.234.4 302
no frame-relay inverse-arp
no shutdown
R4
interface Loopback0
ip address 4.4.4.4 255.0.0.0
!
interface Serial0/0
ip address 192.1.234.4 255.255.255.0
encapsulation frame-relay
frame-relay map ip 192.1.234.2 402 broadcast
frame-relay map ip 192.1.234.3 402
no frame-relay inverse-arp
no shutdown
R5
Switch
interface Loopback0
ip address 5.5.5.5 255.0.0.0
!
interface F 0/0
ip address 192.1.5.5 255.255.255.0
no shutdown
interface Loopback0
ip address 55.55.55.55 255.0.0.0
!
interface Vlan3
ip address 192.1.3.33 255.255.255.0
no shutdown
!
interface Vlan5
ip address 192.1.5.55 255.255.255.0
no shutdown
Task 1
Run OSPF as your Routing Protocol on all Routers and the Switch.
Advertise the networks in the following areas:
Copyrights Netmetric Solutions FZC 2006-2010
Website: http://www.netmetricsolutionsfzc.com; Email: khawarb@khawarb.com
49 of 241
R4
router ospf 1
network 4.0.0.0 0.255.255.255
area 10
network 192.1.234.0 0.0.0.255
area 10
!
interface S 0/0
ip ospf network point-tomulitpoint
router ospf 1
network 5.0.0.0 0.255.255.255 area 100
network 192.1.5.0 0.0.0.255 area 100
SW1
router ospf 1
network 55.0.0.0 0.255.255.255 area 100
network 192.1.3.0 0.0.0.255 area 100
network 192.1.5.0 0.0.0.255 area 100
Copyrights Netmetric Solutions FZC 2006-2010
Website: http://www.netmetricsolutionsfzc.com; Email: khawarb@khawarb.com
50 of 241
51 of 241
52 of 241
R1
Lo 0
R2
F 0/0
Lo 0
F 0/0
192.1.12.0/24
S 0/0
R4
192.1.234.0/24
Switch 1
S 0/0
192.1.3.0/24
Lo 0
VLAN 3
Lo 0
F 0/0
R3
VLAN 5
F 0/0
192.1.5.0/24
R5
R1
Interface
Loopback 0
F 0/0
IP Address
1.1.1.1
192.1.12.1
Subnet Mask
255.0. 0.0
255.255.255.0
IP Address
192.1.12.2
192.1.234.2
2.2.2.2
Subnet Mask
255.255.255.0
255.255.255.0
255.0.0.0
IP Address
192.1.234.3
192.1.3.3
Subnet Mask
255.255.255.0
255.255.255.0
R2
Interface
F 0/0
S 0/0
Loopback 0
R3
Interface
S 0/0
F 0/0
53 of 241
Loopback 0
3.3.3.3
255.0.0.0
IP Address
4.4.4.4
192.1.234.4
Subnet Mask
255.0.0.0
255.255.255.0
IP Address
5.5.5.5
192.1.5.5
Subnet Mask
255.0.0.0
255.255.255.0
IP Address
55.55.55.55
192.1.3.33
192.1.5.55
Subnet Mask
255.0.0.0
255.255.255.0
255.255.255.0
R4
Interface
Loopback 0
S 0/0
R5
Interface
Loopback 0
F 0/0
SW1
Interface
Loopback 0
VLAN 3
VLAN 5
Interface Configuration
R1
interface Loopback0
ip address 1.1.1.1 255.0.0.0
!
interface F 0/0
ip address 192.1.12.1 255.255.255.0
no shutdown
R2
interface Loopback0
ip address 2.2.2.2 255.0.0.0
!
Interface F0/0
ip address 192.1.12.2 255.255.255.0
no shut down
!
interface Serial0/0
ip address 192.1.234.2 255.255.255.0
encapsulation frame-relay
frame-relay map ip 192.1.234.3 203 broadcast
frame-relay map ip 192.1.234.4 204 broadcast
Copyrights Netmetric Solutions FZC 2006-2010
Website: http://www.netmetricsolutionsfzc.com; Email: khawarb@khawarb.com
54 of 241
no frame-relay inverse-arp
no shutdown
R3
interface Loopback0
ip address 3.3.3.3 255.0.0.0
!
interface F 0/0
ip address 192.1.3.3 255.255.255.0
no shutdown
!
interface Serial0/0
ip address 192.1.234.3 255.255.255.0
encapsulation frame-relay
frame-relay map ip 192.1.234.2 302 broadcast
frame-relay map ip 192.1.234.4 302
no frame-relay inverse-arp
no shutdown
R4
interface Loopback0
ip address 4.4.4.4 255.0.0.0
!
interface Serial0/0
ip address 192.1.234.4 255.255.255.0
encapsulation frame-relay
frame-relay map ip 192.1.234.2 402 broadcast
frame-relay map ip 192.1.234.3 402
no frame-relay inverse-arp
no shutdown
R5
Switch
interface Loopback0
ip address 5.5.5.5 255.0.0.0
!
interface F 0/0
ip address 192.1.5.5 255.255.255.0
no shutdown
interface Loopback0
ip address 55.55.55.55 255.0.0.0
!
interface Vlan3
ip address 192.1.3.33 255.255.255.0
no shutdown
!
interface Vlan5
ip address 192.1.5.55 255.255.255.0
no shutdown
55 of 241
Task 1
Run OSPF as your Routing Protocol on all Routers and the Switch.
Configure the Frame Relay links as Point-to-multipoint network types.
Advertise the networks in the following areas:
Area 0 R2 S 0/0, R3 S 0/0, R3 Loop 0, R4 S 0/0, R4 Loop 0
Area 10 R1 Loopback 0, R1 F 0/0, R2 F 0/0, R2 Loop 0
Area 100 R3 F 0/0, SW VLAN 3, SW Loop 0
R1
router ospf 1
network 1.0.0.0 0.255.255.255 area 10
network 192.1.12.0 0.0.0.255 area 10
R2
router ospf 1
router-id 2.2.2.2
network 2.0.0.0 0.255.255.255 area 10
network 192.1.12.0 0.0.0.255 area 10
network 192.1.234.0 0.0.0.255 area 0
!
interface S 0/0
ip ospf network point-to-mulitpoint
R3
router ospf 1
router-id 3.3.3.3
network 3.0.0.0 0.255.255.255 area 100
network 192.1.3.0 0.0.0.255 area 100
network 192.1.234.0 0.0.0.255 area 0
!
interface S 0/0
ip ospf network point-to-mulitpoint
R4
router ospf 1
network 4.0.0.0 0.255.255.255 area 0
network 192.1.234.0 0.0.0.255 area 0
!
interface S 0/0
ip ospf network point-to-mulitpoint
SW1
router ospf 1
Copyrights Netmetric Solutions FZC 2006-2010
Website: http://www.netmetricsolutionsfzc.com; Email: khawarb@khawarb.com
56 of 241
Switch
router rip
version 2
no auto-summary
network 5.0.0.0
network 192.1.5.0
router rip
version 2
no auto-summary
network 192.1.5.0
redistribute ospf 1 metric 1
!
router ospf 1
redistribute rip subnets
Task 3
Create the following Loopbacks on R2:
Loopback 21 12.1.1.1/24
Loopback 22 12.1.2.1/24
Advertise these newly created loopbacks in OSPF using the network
command. Make sure they appear in the routing table using a /24 mask.
Filter these routes going into Area 10. The configuration needs to be done
on R2.
R2
interface Loopback21
ip address 12.1.1.1 255.255.255.0
ip ospf network point-to-point
!
interface Loopback21
ip address 12.1.2.1 255.255.255.0
ip ospf network point-to-point
!
Ip prefix-list A10-IN deny 12.1.1.0/24
Ip prefix-list A10-IN deny 12.1.2.0/24
Ip prefix-list A10-IN permit 0.0.0.0/0 le 32
!
Copyrights Netmetric Solutions FZC 2006-2010
Website: http://www.netmetricsolutionsfzc.com; Email: khawarb@khawarb.com
57 of 241
Router OSPF 1
Network 12.1.1.0 0.0.0.255 area 0
Network 12.1.2.0 0.0.0.255 area 0
Area 10 filter-list prefix A10-IN in
Task 4
Create the following Loopbacks on R4:
Loopback
Loopback
Loopback
Loopback
41
42
43
44
44.1.1.1/24
44.1.2.1/24
44.1.3.1/24
44.1.4.1/24
58 of 241
R1
R2
router ospf 1
area 10 stub
router ospf 1
area 10 stub no-summary
Task 6
Area 100 should not receive any Inter Area or External Routes from the
Backbone. It should have full connectivity to all routes. It Should
maintain connectivity to routes learned via RIP and propagate these
routes to other Areas.
SW1
R3
router ospf 1
area 100 nssa
router ospf 1
area 100 nssa no-summary
59 of 241
201
202
203
204
201.1.4.1/24
201.1.5.1/24
201.1.6.1/24
201.1.7.1/24
60 of 241
Task 2
Create the following Loopbacks on R4:
Loopback
Loopback
Loopback
Loopback
205
206
207
208
202.1.4.1/24
202.1.5.1/24
202.1.6.1/24
202.1.7.1/24
61 of 241
R1
Lo 0
R2
F 0/0
Lo 0
F 0/0
192.1.12.0/24
S 0/0
R4
192.1.234.0/24
Switch 1
S 0/0
192.1.3.0/24
Lo 0
VLAN 3
Lo 0
F 0/0
R3
VLAN 5
F 0/0
192.1.5.0/24
R5
R1
Interface
Loopback 0
F 0/0
IP Address
1.1.1.1
192.1.12.1
Subnet Mask
255.0. 0.0
255.255.255.0
IP Address
192.1.12.2
192.1.234.2
2.2.2.2
Subnet Mask
255.255.255.0
255.255.255.0
255.0.0.0
IP Address
192.1.234.3
192.1.3.3
3.3.3.3
Subnet Mask
255.255.255.0
255.255.255.0
255.0.0.0
R2
Interface
F 0/0
S 0/0
Loopback 0
R3
Interface
S 0/0
F 0/0
Loopback 0
62 of 241
R4
Interface
Loopback 0
S 0/0
IP Address
4.4.4.4
192.1.234.4
Subnet Mask
255.0.0.0
255.255.255.0
IP Address
5.5.5.5
192.1.5.5
Subnet Mask
255.0.0.0
255.255.255.0
IP Address
55.55.55.55
192.1.3.33
192.1.5.55
Subnet Mask
255.0.0.0
255.255.255.0
255.255.255.0
R5
Interface
Loopback 0
F 0/0
SW1
Interface
Loopback 0
VLAN 3
VLAN 5
Interface Configuration
R1
interface Loopback0
ip address 1.1.1.1 255.0.0.0
!
interface F 0/0
ip address 192.1.12.1 255.255.255.0
no shutdown
R2
interface Loopback0
ip address 2.2.2.2 255.0.0.0
!
Interface F0/0
ip address 192.1.12.2 255.255.255.0
no shut down
!
interface Serial0/0
ip address 192.1.234.2 255.255.255.0
encapsulation frame-relay
frame-relay map ip 192.1.234.3 203 broadcast
frame-relay map ip 192.1.234.4 204 broadcast
no frame-relay inverse-arp
Copyrights Netmetric Solutions FZC 2006-2010
Website: http://www.netmetricsolutionsfzc.com; Email: khawarb@khawarb.com
63 of 241
no shutdown
R3
interface Loopback0
ip address 3.3.3.3 255.0.0.0
!
interface F 0/0
ip address 192.1.3.3 255.255.255.0
no shutdown
!
interface Serial0/0
ip address 192.1.234.3 255.255.255.0
encapsulation frame-relay
frame-relay map ip 192.1.234.2 302 broadcast
frame-relay map ip 192.1.234.4 304
no frame-relay inverse-arp
no shutdown
R4
interface Loopback0
ip address 4.4.4.4 255.0.0.0
!
interface Serial0/0
ip address 192.1.234.4 255.255.255.0
encapsulation frame-relay
frame-relay map ip 192.1.234.2 402 broadcast
frame-relay map ip 192.1.234.3 403
no frame-relay inverse-arp
no shutdown
R5
Switch
interface Loopback0
ip address 5.5.5.5 255.0.0.0
!
interface F 0/0
ip address 192.1.5.5 255.255.255.0
no shutdown
interface Loopback0
ip address 55.55.55.55 255.0.0.0
!
interface Vlan3
ip address 192.1.3.33 255.255.255.0
no shutdown
!
interface Vlan5
ip address 192.1.5.55 255.255.255.0
no shutdown
64 of 241
Task 1
Create the following Loopbacks on R1. Run RIP V2 as the Routing
Protocol between R1 and R2. Advertise all directly connected networks
including the newly created loopbacks in RIP. Advertise the Loopback
and the F 0/0 Interface on R2 in RIP.
Loopback
Loopback
Loopback
Loopback
Loopback
Loopback
Loopback
Loopback
1
2
3
4
5
6
7
8
192.2.1.1/24
192.2.2.1/24
192.2.3.1/24
192.2.4.1/24
192.2.5.1/24
192.2.6.1/24
192.2.7.1/24
192.2.8.1/24
R1
interface Loopback1
ip address 192.2.1.1
!
interface Loopback2
ip address 192.2.2.1
!
interface Loopback3
ip address 192.2.3.1
!
interface Loopback4
ip address 192.2.4.1
!
interface Loopback5
ip address 192.2.5.1
!
interface Loopback6
ip address 192.2.6.1
!
interface Loopback7
ip address 192.2.7.1
!
interface Loopback8
ip address 192.2.8.1
!
router rip
version 2
network 1.0.0.0
network 192.1.12.0
255.255.255.0
255.255.255.0
255.255.255.0
255.255.255.0
255.255.255.0
255.255.255.0
255.255.255.0
255.255.255.0
65 of 241
network 192.2.1.0
network 192.2.2.0
network 192.2.3.0
network 192.2.4.0
network 192.2.5.0
network 192.2.6.0
network 192.2.7.0
network 192.2.8.0
no auto-summary
R2
router rip
version 2
network 2.0.0.0
network 192.1.12.0
no auto-summary
Task 2
Run EIGRP in AS 234 as the Routing Protocol between R2, R3 and R4.
Advertise all directly connected networks on R4 in EIGRP. Advertise the
S 0/0 interfaces on R2 and R3 in EIGRP. Also advertise the Loopback 0
network of R3 in EIGRP.
R2
R3
66 of 241
router ospf 1
network 192.1.3.0 0.0.0.255 area 0
R5
router ospf 1
network 5.0.0.0 0.255.255.255 area 0
network 192.1.5.0 0.0.0.255 area 0
Switch
router ospf 1
network 55.0.0.0 0.255.255.255 area 0
network 192.1.3.0 0.0.0.255 area 0
network 192.1.5.0 0.0.0.255 area 0
Task 4
Configure Mutual redistribution between RIP and EIGRP at the
appropriate router. Configure Mutual redistribution between EIGRP and
OSPF at the appropriate router. Make sure OSPF adds the cost of the
links in the OSPF metric for the External Routes.
R2
router eigrp 234
redistribute rip metric 1 1 1 1 1
!
router rip
redistribute eigrp 234 metric 5
R3
router eigrp 234
redistribute ospf 1 metric 1 1 1 1 1
!
router ospf 1
redistribute eigrp 234 metric 150 metric-type 1 subnets
Task 5
The RIP routes should not be leaked to OSPF and OSPF routes should
not be leaked to RIP. Do not use the Distribute-list or Prefix-list
command to accomplish this task. You might have to re-configure the
redistribution from the previous task to accomplish this.
R2
Route-map R-2-E per 10
Copyrights Netmetric Solutions FZC 2006-2010
Website: http://www.netmetricsolutionsfzc.com; Email: khawarb@khawarb.com
67 of 241
68 of 241
Module 6 BGP
69 of 241
Loopback 0
R1
R2
F 0/0
Loopback 0
F 0/0
Loopback 1
Loopback 1
S 0/0
Loopback 1
S 0/0
Loopback 1
Loopback 0
Loopback 0
F 0/0
F 0/0
R3
R4
AS 1
AS 2
R2
R1
R4
R3
AS 4
AS 3
70 of 241
IP Address
1.1.1.1
11.1.0.1
192.1.12.1
Subnet Mask
255.0.0.0
255.255.0.0
255.255.255.0
R2
Interface
Loopback 0
Loopback 1
E 0/0
S 0/0
IP Address
2.2.2.2
12.1.0.1
192.1.12.2
192.1.23.2
Subnet Mask
255.0.0.0
255.255.0.0
255.255.255.0
255.255.255.0
IP Address
3.3.3.3
13.1.0.1
192.1.23.3
192.1.34.3
Subnet Mask
255.0.0.0
255.255.0.0
255.255.255.0
255.255.255.0
IP Address
4.4.4.4
14.1.0.1
192.1.34.4
Subnet Mask
255.0.0.0
255.255.0.0
255.255.255.0
R3
Interface
Loopback 0
Loopback 1
S 0/0
E 0/0
R4
Interface
Loopback 0
Loopback 1
E 0/0
Task 1
Configure a BGP neighbor relationship between R1 and R2. R1 should be
in AS 1 and R2 should be in AS 2. Advertise the loopback networks in
BGP. Hard-code the Router ID for the BGP routers as 11.11.11.11 for R1
and 22.22.22.22 for R2.
R1
R2
Router BGP 1
bgp router-id 11.11.11.11
Network 1.0.0.0
Network 11.1.0.0 mask 255.255.0.0
Router BGP 2
bgp router-id 22.22.22.22
Network 2.0.0.0
Network 12.1.0.0 mask 255.255.0.0
71 of 241
Task 2
Configure a BGP neighbor relationship between R2 and R3. R2 should
already be configured in AS 2 and R3 should be in AS 3. Advertise the
loopback network of R3 in BGP. Hard-code the Router ID for R3 as
33.33.33.33
R2
R3
Router BGP 2
Neighbor 192.1.23.3 remote-as 3
Router BGP 3
bgp router-id 33.33.33.33
Network 3.0.0.0
Network 13.1.0.0 mask 255.255.0.0
Neighbor 192.1.23.2 remote-as 2
Task 3
Configure a BGP neighbor relationship between R3 and R4. R3 should
already be configured in AS 3 and R4 should be in AS 4. Advertise the
loopback network of R4 in BGP. Hard-code the Router ID for R4 as
44.44.44.44. Establish the neighbor relationship based on Loopback 0
addresses. You are allowed to create a static route on each router to
accomplish this task.
R3
R4
72 of 241
R2
Router BGP 1
Neighbor 192.1.12.2 pass cciers
Router BGP 2
Neighbor 192.1.12.1 password cciers
Task 2
Configure MD5 Authentication between R2 and R3 using a password of
cciesec.
R2
R3
Router BGP 2
Neighbor 192.1.23.3 pass cciesec
Router BGP 3
Neighbor 192.1.23.2 password cciesec
Task 3
Configure MD5 Authentication between R3 and R4 using a password of
cciers.
R3
R4
Router BGP 3
Neighbor 4.4.4.4 password cciers
Router BGP 4
Neighbor 3.3.3.3 password cciers
73 of 241
L0 1.1.1.1/8
R1
S 0/0(.1)
R2
192.1.12.0/24
L0 2.2.2.2/8
S 0/0 (.2)
L1 12.1.0.1/16
F 0/0 (.2)
R5
192.1.23.0/24
F 0/0 (.5)
192.1.45.0/24
S 0/0(.4)
F 0/0 (.4)
L0 4.4.4.4/8
F 0/0 (.3)
192.1.34.0/24
L0 3.3.3.3/8
S 0/0 (.3)
R4
R3
L1 13.1.0.1/16
R3
AS 5
AS 1
AS 234
R1
R2
R4
R5
74 of 241
IP Address
1.1.1.1
192.1.12.1
Subnet Mask
255.0.0.0
255.255.255.0
R2
Interface
Loopback 0
Loopback 1
S 0/0
F 0/0
IP Address
2.2.2.2
12.1.0.1
192.1.12.2
192.1.23.2
Subnet Mask
255.0.0.0
255.255.0.0
255.255.255.0
255.255.255.0
IP Address
3.3.3.3
13.1.0.1
192.1.23.3
192.1.34.3
Subnet Mask
255.0.0.0
255.255.0.0
255.255.255.0
255.255.255.0
IP Address
4.4.4.4
192.1.34.4
192.1.45.4
Subnet Mask
255.0.0.0
255.255.255.0
255.255.255.0
IP Address
5.5.5.5
192.1.45.5
Subnet Mask
255.0.0.0
255.255.255.0
R3
Interface
Loopback 0
Loopback 1
F 0/0
S 0/0
R4
Interface
Loopback 0
S 0/0
F 0/0
R5
Interface
Loopback 0
F 0/0
Task 1
Configure a neighbor relationship between R1 and R2 based on the
Logical diagram. Advertise the Loopback networks on both Routers.
Hard-code the Router ID for the BGP routers as 11.11.11.11 for R1 and
22.22.22.22 for R2.
R1
R2
Copyrights Netmetric Solutions FZC 2006-2010
Website: http://www.netmetricsolutionsfzc.com; Email: khawarb@khawarb.com
75 of 241
Router BGP 1
bgp router-id 11.11.11.11
Network 1.0.0.0
Neighbor 192.1.12.2 remote-as 234
Task 2
Configure EIGRP in AS 234 as the routing protocol within AS 234. Only
advertise the internal physical link in EIGRP on R2, R3 and R4. Do not
advertise the 192.1.12.0 and the 192.1.45.0 networks in EIGRP.
R2
R3
R4
Router EIGRP 234
no auto-summary
Network 192.1.34.0
Task 3
Configure neighbor relationships between R2 and R3 and another one
between R3 and R4. Do not configure a neighbor relationship between R2
and R4. Advertise the Loopback networks under BGP. Make sure routes
from R1 can get propagated to R3 and R4. Do not use a Confederation to
accomplish this.
R2
Router BGP 234
Network 2.0.0.0
Network 12.1.0.0 mask 255.255.0.0
Neighbor 192.1.23.3 remote-as 234
Neighbor 192.1.23.3 next-hop-self
R3
Router BGP 234
Network 3.0.0.0
Network 13.1.0.0 mask 255.255.0.0
Neighbor 192.1.23.2 remote-as 234
Neighbor 192.1.23.2 route-reflector-client
Copyrights Netmetric Solutions FZC 2006-2010
Website: http://www.netmetricsolutionsfzc.com; Email: khawarb@khawarb.com
76 of 241
R5
Router BGP 5
bgp router-id 55.55.55.55
Network 5.0.0.0
Neighbor 192.1.45.4 remote-as 234
77 of 241
1
2
3
4
5
6
7
8
192.2.1.1/24
192.2.2.1/24
192.2.3.1/24
192.2.4.1/24
192.2.5.1/24
192.2.6.1/24
192.2.7.1/24
192.2.8.1/24
R2
interface Loopback1
ip address 192.2.1.1
!
interface Loopback2
ip address 192.2.2.1
!
interface Loopback3
ip address 192.2.3.1
!
interface Loopback4
ip address 192.2.4.1
!
interface Loopback5
ip address 192.2.5.1
!
interface Loopback6
ip address 192.2.6.1
!
interface Loopback7
ip address 192.2.7.1
!
interface Loopback8
ip address 192.2.8.1
255.255.255.0
255.255.255.0
255.255.255.0
255.255.255.0
255.255.255.0
255.255.255.0
255.255.255.0
255.255.255.0
78 of 241
Task 2
Advertise the newly created routes in BGP. Do not use the network
command to accomplish this. These routes should have an origin code of
igp.
R2
Access-list 1 permit 192.2.1.1 0.0.0.255
Access-list 1 permit 192.2.2.1 0.0.0.255
Access-list 1 permit 192.2.3.1 0.0.0.255
Access-list 1 permit 192.2.4.1 0.0.0.255
Access-list 1 permit 192.2.5.1 0.0.0.255
Access-list 1 permit 192.2.6.1 0.0.0.255
Access-list 1 permit 192.2.7.1 0.0.0.255
Access-list 1 permit 192.2.8.1 0.0.0.255
!
Route-map redcon permit 10
Match address 1
Set origin igp
!
Router bgp 234
Redistribute connected route-map redcon
Task 3
Configure R2 such that it blocks all the 192.2.X.0 routes that have an
odd number in the third octet from propagating outside the local AS. Use
the distribute-list command to accomplish this task.
R2
Access-list 2 deny 192.2.1.0 0.0.254.255
Access-list 2 permit any
!
Router bgp 234
Neighbor 192.1.12.1 distribute-list 2 out
Task 4
Configure R4 such that it blocks all the 192.2.X.0 routes that have an
even number in the third octet from coming in. Make sure that even if in
the future that a neighbor relationship is established between R2 and R4
these routes dont come into R4. Use the distribute-list command to
accomplish this task.
R4
Copyrights Netmetric Solutions FZC 2006-2010
Website: http://www.netmetricsolutionsfzc.com; Email: khawarb@khawarb.com
79 of 241
80 of 241
1
2
3
4
5
6
7
150.3.16.1/20
150.3.36.1/22
150.3.40.1/22
150.3.50.1/23
150.3.65.1/24
150.13.0.1/16
150.14.64.1/18
R3
interface Loopback1
ip address 150.3.16.1 255.255.240.0
!
interface Loopback2
ip address 150.3.36.1 255.255.252.0
!
interface Loopback3
ip address 150.3.40.1 255.255.252.0
!
interface Loopback4
ip address 150.3.50.1 255.255.254.0
!
interface Loopback5
ip address 150.3.65.1 255.255.255.0
!
interface Loopback6
ip address 150.13.0.1 255.255.0.0
!
interface Loopback7
ip address 150.14.64.1 255.255.192.0
Task 2
Advertise the newly created routes in BGP using the Network command.
R3
Router bgp 234
Network 150.3.16.0 mask 255.255.240.0
Copyrights Netmetric Solutions FZC 2006-2010
Website: http://www.netmetricsolutionsfzc.com; Email: khawarb@khawarb.com
81 of 241
Network
Network
Network
Network
Network
Network
Task 3
Configure R2 such that it blocks all the 150.X.X.0 routes that have a
subnet mask between 17 and 23 bits.
R2
IP Prefix-list PLIST deny 150.0.0.0/8 ge 17 le 23
IP Prefix-list PLIST permit 0.0.0.0/0 le 32
!
Router bgp 234
Neighbor 192.1.23.3 prefix-list PLIST in
82 of 241
L0 1.1.1.1/8
R1
S 0/0(.1)
R2
192.1.12.0/24
L0 2.2.2.2/8
S 0/0 (.2)
L1 12.1.0.1/16
F 0/0 (.2)
R5
192.1.23.0/24
F 0/0 (.5)
192.1.45.0/24
S 0/0(.4)
F 0/0 (.4)
L0 4.4.4.4/8
F 0/0 (.3)
192.1.34.0/24
L0 3.3.3.3/8
S 0/0 (.3)
R4
R3
L1 13.1.0.1/16
R3
AS 5
AS 1
AS 234
R1
R2
R4
R5
83 of 241
R1
Interface
Loopback 0
S 0/0
IP Address
1.1.1.1
192.1.12.1
Subnet Mask
255.0.0.0
255.255.255.0
R2
Interface
Loopback 0
Loopback 1
S 0/0
F 0/0
IP Address
2.2.2.2
12.1.0.1
192.1.12.2
192.1.23.2
Subnet Mask
255.0.0.0
255.255.0.0
255.255.255.0
255.255.255.0
IP Address
3.3.3.3
13.1.0.1
192.1.23.3
192.1.34.3
Subnet Mask
255.0.0.0
255.255.0.0
255.255.255.0
255.255.255.0
IP Address
4.4.4.4
192.1.34.4
192.1.45.4
Subnet Mask
255.0.0.0
255.255.255.0
255.255.255.0
IP Address
5.5.5.5
192.1.45.5
Subnet Mask
255.0.0.0
255.255.255.0
R3
Interface
Loopback 0
Loopback 1
F 0/0
S 0/0
R4
Interface
Loopback 0
S 0/0
F 0/0
R5
Interface
Loopback 0
F 0/0
Task 1
Configure a neighbor relationship between R1 and R2 based on the
Logical diagram. Advertise the Loopback networks on both Routers.
Hard-code the Router ID for the BGP routers as 11.11.11.11 for R1 and
22.22.22.22 for R2.
R1
R2
Router BGP 1
84 of 241
Task 2
Configure EIGRP in AS 234 as the routing protocol within AS 234. Only
advertise the internal physical link in EIGRP on R2, R3 and R4. Do not
advertise the 192.1.12.0 and the 192.1.45.0 networks in EIGRP.
R2
R3
R4
Router EIGRP 234
no auto-summary
Network 192.1.34.0
Task 3
Configure neighbor relationships between R2 and R3 and another one
between R3 and R4. Do not configure a neighbor relationship between R2
and R4. Advertise the Loopback networks under BGP. Make sure routes
from R1 can get propagated to R3 and R4. Do not use a Confederation to
accomplish this.
R2
Router BGP 234
Network 2.0.0.0
Network 12.1.0.0 mask 255.255.0.0
Neighbor 192.1.23.3 remote-as 234
Neighbor 192.1.23.3 next-hop-self
R3
Router BGP 234
Network 3.0.0.0
Network 13.1.0.0 mask 255.255.0.0
Neighbor 192.1.23.2 remote-as 234
Neighbor 192.1.23.2 route-reflector-client
Neighbor 192.1.34.4 remote-as 234
Neighbor 192.1.34.4 route-reflector-client
Copyrights Netmetric Solutions FZC 2006-2010
Website: http://www.netmetricsolutionsfzc.com; Email: khawarb@khawarb.com
85 of 241
R4
Router BGP 234
Network 4.0.0.0
Network 14.1.0.0 mask 255.255.0.0
Neighbor 192.1.34.3 remote-as 234
Task 4
Configure a neighbor relationship between R4 and R5 based on the
Logical diagram. Advertise the Loopback network on R5 in BGP. Hardcode the Router ID for R5 as 55.55.55.55.
R4
R5
Router BGP 5
bgp router-id 55.55.55.55
Network 5.0.0.0
Neighbor 192.1.45.4 remote-as 234
Task 5
Configure BGP such that AS 5 does not use AS 234 as a transit AS.
Configuration should be done in AS 5.
R5
Ip as-path access-list 1 permit ^234$
!
Router BGP 5
Neighbor 192.1.45.4 filter-list 1 in
Task 6
Configure BGP such that AS 1 does not use AS 234 to get AS 5 routes.
Configuration should be done in AS 234. You are only allowed a single
line in the AS-path filter.
R2
Ip as-path access-list 1 permit ^$
!
Router BGP 234
Neighbor 192.1.12.1 filter-list 1 out
86 of 241
1
2
3
4
203.1.4.1/24
203.1.5.1/24
203.1.6.1/24
203.1.7.1/24
R3
interface Loopback1
ip address 203.1.4.1
!
interface Loopback2
ip address 203.1.5.1
!
interface Loopback3
ip address 203.1.6.1
!
interface Loopback4
ip address 203.1.7.1
!
Router BGP 234
Network 203.1.4.0
Network 203.1.5.0
Network 203.1.6.0
Network 203.1.7.0
255.255.255.0
255.255.255.0
255.255.255.0
255.255.255.0
Task 2
Configure Route Aggregation on R3 such that these routes are
summarized as a single route. Only the Summary route should be send
to R3s neighbors.
R3
Router bgp 234
Aggregate-address 203.1.4.0 255.255.252.0 summary-only
Task 3
Create the following Loopbacks on R4 and advertise them under BGP:
Copyrights Netmetric Solutions FZC 2006-2010
Website: http://www.netmetricsolutionsfzc.com; Email: khawarb@khawarb.com
87 of 241
Loopback
Loopback
Loopback
Loopback
1
2
3
4
204.1.4.1/24
204.1.5.1/24
204.1.6.1/24
204.1.7.1/24
R4
interface Loopback1
ip address 204.1.4.1
!
interface Loopback2
ip address 204.1.5.1
!
interface Loopback3
ip address 204.1.6.1
!
interface Loopback4
ip address 204.1.7.1
!
Router BGP 234
Network 204.1.4.0
Network 204.1.5.0
Network 204.1.6.0
Network 204.1.7.0
255.255.255.0
255.255.255.0
255.255.255.0
255.255.255.0
Task 4
Configure Route Aggregation on R4 such that these routes are
summarized as a single route. Only the Summary route should be send
to R4s neighbor. The routes should not be seen as suppressed on R4.
Use the minimum number of lines in your filtering mechanism.
R4
IP Prefix-list PLIST deny 204.1.4.0/22 ge 24
IP Prefix-list PLIST permit 0.0.0.0/0 le 32
!
Router bgp 234
Aggregate-address 204.1.4.0 255.255.252.0
Neighbor 192.1.34.3 prefix-list PLIST out
Neighbor 192.1.45.5 prefix-list PLIST out
Task 5
Create the following Loopbacks on R2 and advertise them under BGP:
Copyrights Netmetric Solutions FZC 2006-2010
Website: http://www.netmetricsolutionsfzc.com; Email: khawarb@khawarb.com
88 of 241
Loopback
Loopback
Loopback
Loopback
1
2
3
4
202.1.4.1/24
202.1.5.1/24
202.1.6.1/24
202.1.7.1/24
R2
interface Loopback1
ip address 202.1.4.1
!
interface Loopback2
ip address 202.1.5.1
!
interface Loopback3
ip address 202.1.6.1
!
interface Loopback4
ip address 202.1.7.1
!
Router BGP 234
Network 202.1.4.0
Network 202.1.5.0
Network 202.1.6.0
Network 202.1.7.0
255.255.255.0
255.255.255.0
255.255.255.0
255.255.255.0
Task 6
Configure Route Aggregation on R2 such that these routes are
summarized as a single route. Only the Summary route and the
202.1.5.0 route should be send to R2s neighbor.
R2
Access-list 5 permit 202.1.5.0 0.0.0.255
!
Route-map SUPMAP deny 10
Match address 5
Route-map SUPMAP permit 20
!
Router bgp 234
Aggregate-address 202.1.4.0 255.255.252.0 supress-map SUPMAP
89 of 241
Loopback 0
R1
R2
F 0/0
Loopback 0
F 0/0
Loopback 1
Loopback 1
S 0/0
Loopback 1
S 0/0
Loopback 1
Loopback 0
Loopback 0
F 0/0
F 0/0
R3
R4
R2
AS 65002
AS 4
AS 123
R1
R3
AS 65003
AS 65001
R4
90 of 241
IP Address
1.1.1.1
192.1.12.1
Subnet Mask
255.0.0.0
255.255.255.0
R2
Interface
Loopback 0
F 0/0
S 0/0
IP Address
2.2.2.2
192.1.12.2
192.1.23.2
Subnet Mask
255.0.0.0
255.255.255.0
255.255.255.0
IP Address
3.3.3.3
192.1.23.3
192.1.34.3
Subnet Mask
255.0.0.0
255.255.255.0
255.255.255.0
IP Address
4.4.4.4
192.1.34.4
Subnet Mask
255.0.0.0
255.255.255.0
R3
Interface
Loopback 0
S 0/0
F 0/0
R4
Interface
Loopback 0
F 0/0
Task 1
Configure RIP V2 as the routing protocol between R1, R2 and R3. Only
advertise the R1-R2 and R2-R3 links in RIP on the appropriate routers.
R1
R2
Router RIP
No auto-summary
Version 2
Network 192.1.12.0
Router RIP
No auto-summary
Version 2
Network 192.1.12.0
Network 192.1.23.0
R3
Router RIP
No auto-summary
Version 2
Copyrights Netmetric Solutions FZC 2006-2010
Website: http://www.netmetricsolutionsfzc.com; Email: khawarb@khawarb.com
91 of 241
Network 192.1.23.0
Task 2
Configure AS 65001, AS 65002 and AS 65003 are Sub Autonomous
Systems of a Larger AS 123 using Confederations. Advertise the
Loopback 0 networks under BGP in AS 65001, AS 65002 and AS 65003.
Configure a Neighbor relationship between AS 65001 and AS 65002 and
another Neighbor relationship between AS 65002 and AS 65003.
R1
R2
R3
Router BGP 65003
Network 3.0.0.0
Neighbor 192.1.23.2 remote-as 2
bgp confederation identifier 123
bgp confederation peers 65002
Task 3
Configure a neighbor relationship between R3 and R4. R4 is in AS 4. It
peers with R3 in the confederation AS 123. Advertise the loopback 0
interface under BGP in AS 4.
R3
Router BGP 65003
Neighbor 192.1.34.4 remote-as 4
R4
Router BGP 4
Network 4.0.0.0
Neighbor 192.1.34.3 remote-as 123
92 of 241
Loopback 0
R1
R2
F 0/0
Loopback 1
Loopback 1
Loopback 0
F 0/0
Loopback 1
S 0/0
S 0/0
S 0/0
S 0/0
Loopback 1
Loopback 0
Loopback 0
F 0/0
F 0/0
R3
R4
R2
AS 1
AS 234
R3
R1
R4
93 of 241
IP Address
1.1.1.1
192.1.12.1
192.1.14.1
Subnet Mask
255.0.0.0
255.255.255.0
255.255.255.0
R2
Interface
Loopback 0
F 0/0
S 0/0
IP Address
2.2.2.2
192.1.12.2
192.1.23.2
Subnet Mask
255.0.0.0
255.255.255.0
255.255.255.0
IP Address
3.3.3.3
192.1.23.3
192.1.34.3
Subnet Mask
255.0.0.0
255.255.255.0
255.255.255.0
IP Address
4.4.4.4
192.1.34.4
192.1.14.4
Subnet Mask
255.0.0.0
255.255.255.0
255.255.255.0
R3
Interface
Loopback 0
S 0/0
F 0/0
R4
Interface
Loopback 0
F 0/0
S 0/0
Task 1
Run RIP V2 as the IGP in AS 234. Advertise the directly connected links
under RIP. Do not advertise the external links (192.1.12.0, 192.1.14.0) or
the Loopbacks in RIP.
R2
R3
Router RIP
Version 2
No auto-summary
Network 192.1.23.0
Router RIP
Version 2
No auto-summary
Network 192.1.23.0
Network 192.1.34.0
R4
Copyrights Netmetric Solutions FZC 2006-2010
Website: http://www.netmetricsolutionsfzc.com; Email: khawarb@khawarb.com
94 of 241
Router RIP
Version 2
No auto-summary
Network 194.1.34.0
Task 2
Configure the routers under BGP based on the Logical diagram.
Configure the Neighbor relationships also based on the Logical diagram.
Advertise Loopback 0 Networks on all routers under BGP. Make sure the
1.0.0.0 gets put into the routing table of R3. Also make sure that Routes
from R2 are getting propagated to R4 and vice versa.
R1
R2
Router BGP 1
No auto-summary
No sync
Network 1.0.0.0
Neighbor 192.1.12.2 remote-as
234
Neighbor 192.1.14.4 remote-as
234
R3
remote-as
routeremote-as
route-
95 of 241
Task 3
All ingress (incoming) traffic to AS 234 should use the path thru R4
using the MED attribute. Configure the MED on R2 to 100. R4s MED is
0 by default. Lower MED will be preferred.
R2
Route-map SETMED permit 10
Set metric 100
!
Router BGP 234
Neighbor 192.1.12.1 route-map SETMED out
96 of 241
97 of 241
98 of 241
99 of 241
R5
F 0/0 (.5)
192.1.15.0/24 VLAN 10
F 0/0.1 (.1)
R1
F 0/0.2 (.1)
192.1.13.0/24 VLAN 20
F0/0.1 (.3)
R3
F0/0.2 (.3)
192.1.34.0/24 VLAN 30
VLAN 30 (.15)
F 0/0 (.4)
R4
SW1
VLAN 40 (.15)
192.1.2.0/24 VLAN 40
F 0/0 (.2)
R2
Task 1
Configure the Switches with Hostnames of SW1 and SW2 respectively.
SW1
SW2
Hostname SW1
Hostname SW2
Task 2
Configure both switches to be in a VTP Domain CISCO. SW1 should be
configured as a Server and SW2 as a Client.
Copyrights Netmetric Solutions FZC 2006-2010
Website: http://www.netmetricsolutionsfzc.com; Email: khawarb@khawarb.com
100 of 241
SW1
SW2
Task 3
The CISCO VTP Domain should be password protected using NETMET as
the Password.
SW1
SW2
Task 4
Configure Trunking between SW1 and SW2 on all ports that connect the
switches to each other. Use an Industry standard encapsulation
mechanism.
SW1
SW2
Task 5
Create VLANs based on the Diagram. Assign the appropriate ports to the
appropriate VLANs based on the Logical Diagram. Use an industry
standard encapsulation wherever required.
SW1
VLAN 10
VLAN 20
VLAN 30
VLAN 40
!
interface F0/1 , F0/3
Switchport Trunk Encap dot1q
Switchport mode trunk
!
interface F0/2
Switchport access vlan 40
Switchport mode access
!
Copyrights Netmetric Solutions FZC 2006-2010
Website: http://www.netmetricsolutionsfzc.com; Email: khawarb@khawarb.com
101 of 241
Interface F0/4
Switchport access vlan 30
Switchport mode access
!
Interface F0/5
Switchport access vlan 10
Switchport mode access
Task 6
Configure the Routers and SW1 with the Appropriate IP addresses based
on the Logical Diagram.
R1
R2
Interface F 0/0
No shut
!
Interface F 0/0.1
Encapsulation dot1q 10
IP Address 192.1.15.1 255.255.255.0
!
Interface F0/0.2
Encapsulation dot1q 20
IP Address 192.1.13.1 255.255.255.0
R3
Interface F 0/0
IP Address 192.1.2.2 255.255.255.0
No shut
Interface F 0/0
No shut
!
Interface F 0/0.1
Encapsulation dot1q 20
IP Address 192.1.13.3 255.255.255.0
!
Interface F0/0.2
Encapsulation dot1q 30
IP Address 192.1.34.3 255.255.255.0
R5
Interface F 0/0
IP Address 192.1.34.4 255.255.255.0
No shut
Interface F 0/0
IP Address 192.1.15.5 255.255.255.0
No shut
R4
SW1
IP Routing
!
Interface VLAN 30
IP Address 192.1.34.15 255.255.255.0
!
Interface VLAN 40
IP Address 192.1.2.15 255.255.255.0
102 of 241
Task 7
Configure a Loopback 0 interface on each Rotuer with an IP Address of
X.X.X.X/8 (where X is the Router # - R1=1, R2=2 .). Loopback 0 on
SW1 as 15.15.15.15/8. Run RIP v2 on all the routers and SW1 such that
all networks are reachable from all devices.
R1
R2
Interface Loopback 0
IP Address 1.1.1.1 255.0.0.0
!
Router RIP
Version 2
No auto-summary
Network 192.1.15.0
Network 192.1.13.0
Network 1.0.0.0
R3
Interface Loopback 0
IP Address 2.2.2.2 255.0.0.0
!
Router RIP
Version 2
No auto-summary
Network 192.1.2.0
Network 2.0.0.0
Interface Loopback 0
IP Address 3.3.3.3 255.0.0.0
!
Router RIP
Version 2
No auto-summary
Network 192.1.13.0
Network 192.1.34.0
Network 3.0.0.0
R5
Interface Loopback 0
IP Address 4.4.4.4 255.0.0.0
!
Router RIP
Version 2
No auto-summary
Network 192.1.34.0
Network 4.0.0.0
R4
SW1
Interface Loopback 0
IP Address 15.15.15.15 255.0.0.0
!
Router RIP
Version 2
No auto-summary
Network 192.1.34.0
Network 192.1.2.0
Network 15.0.0.0
Interface Loopback 0
IP Address 5.5.5.5 255.0.0.0
!
Router RIP
Version 2
No auto-summary
Network 192.1.15.0
Network 1.0.0.0
103 of 241
SW2
Task 2
Configure the Load Balancing mechanism method to be done based on a
combination of the Source and Destination IP.
SW1
Port-channel load-balance src-dst-ip
SW2
Port-channel load-balance src-dst-ip
Task 3
Verify the Etherchannel status.
SW1
Show etherchannel 1 port-channel
Port-channels in the group:
--------------------------Port-channel: Po1 (Primary Aggregator)
-----------Age of the Port-channel = 00d:00h:01m:09s
Logical slot/port = 1/0 Number of ports = 0
HotStandBy port = null
Port state = Port-channel Ag-Not-Inuse
Protocol = LACP
104 of 241
Explanation:
An EtherChannel consists of individual Fast Ethernet or Gigabit
Ethernet links bundled into a single logical link.
If a link within an EtherChannel fails, traffic previously carried over that
failed link changes to the remaining links within the EtherChannel. A
trap is sent for a failure, identifying the switch, the EtherChannel, and
the failed link.
Inbound broadcast and multicast packets on one link in an
EtherChannel are blocked from returning on any other link of the
EtherChannel.
NOTE: All interfaces in each Etherchannel must be the same speed and
duplex, same trunking encapsulation or the same access vlan ID, also
the STP cost for each port must be the same and none of the
Etherchannel ports can be involved in SPAN, RSPAN configuration or
neither 802.1X.
Understanding Port-Channel Interfaces
You create an EtherChannel for Layer 2 interfaces differently from Layer
3 interfaces. Both configurations involve logical interfaces.
With Layer 3 interfaces, you manually create the logical interface by
using the interface port-channel global configuration command.
With Layer 2 interfaces, the logical interface is dynamically created.
With both Layer 3 and 2 interfaces, you manually assign an interface
to the EtherChannel by using the channel-group interface configuration
command. This command binds the physical and logical ports together
An Etherchannel cannot be configured in both the PAgP and LACP
modes.
105 of 241
SW2
Task 2
Configure Multi-instance of Spanning Tree on the switches as follows:
There should be two instances of STP, instance 1 and 2
Instance 1 should handle VLANs 10 and 20
Instance 2 should handle VLAN 30 and 40
SW1 should be the root bridge for the first instance
SW2 should be the root bridge for the second instance
MST configuration should use the following:
o Name : CISCO
o Revision : 1
Instance 1 should use the lower Trunk Interface as the Primary
forwarding port
Instance 2 should use the higher Trunk Interface as the Primary
forwarding port
SW1
SW2
106 of 241
107 of 241
108 of 241
Vlan
!
Vlan
Vlan
Vlan
Vlan
VLAN10
VLAN20
VLAN30
VLAN40
vlan-list
vlan-list
vlan-list
vlan-list
10
20
30
40
109 of 241
110 of 241
SW1
SW2
VLAN 80
VLAN 90
SW4
VLAN 80
SW3
VLAN 90
Subnet Mask
255.255.255.0
255.255.255.0
IP Address
150.1.80.4
150.1.90.4
Subnet Mask
255.255.255.0
255.255.255.0
Task 1
Only Keep 1 Trunk link up between the switches. Also, make sure only
the following links are up:
SW1 SW3
SW1 SW2
SW2 SW4
SW1
!
Interface range F0/X Y
Copyrights Netmetric Solutions FZC 2006-2010
Website: http://www.netmetricsolutionsfzc.com; Email: khawarb@khawarb.com
111 of 241
Shutdown
Description All trunk ports on SW1
!
Interface range F 0/A , F 0/B
No shutdown
Description One Trunk link towards SW1
SW2
!
Interface range F0/X Y
Shutdown
Description All trunk ports on SW2
!
Interface range F 0/A , F 0/B
No shutdown
Description One Trunk each towards SW1 and SW3
SW3
!
Interface range F0/X Y
Shutdown
Description All trunk ports on SW3
!
Interface F 0/A
No shutdown
Description One Trunk each towards SW2 and SW4
SW4
!
Interface range F0/X Y
Shutdown
Description All trunk ports on SW4
!
Interface F 0/A
No shutdown
Description One Trunk link towards SW3
Task 2
Configure Q-in-Q tunneling on SW2 and SW3 in such a way that allows
customer VLANs to cross the trunk linkds without alteration in the
Customer switches. Also, allow VLAN overlapping between other Service
Provider Customers. Change the MTU size to accommodate Q-in-Q
tunneling. Assign the Customer to a VLAN 120.
112 of 241
SW2
System mtu 1504
!*** requires a reload***
VLAN 120
!
Interface F0/A
Description Trunk ports connecting towards SW1-Customer Switch
Switchport access vlan 120
Switchport mode dot1q-tunnel
!
Interface F0/B
Description Trunk port towards the other Service Provider Switch(s)
Switchport trunk encap dot1q
Switchport mode trunk
SW3
System mtu 1504
! *** requires a reload***
VLAN 120
!
Interface F0/A
Description Trunk ports connecting towards SW4-Customer Switch
Switchport access vlan 120
Switchport mode dot1q-tunnel
!
Interface F0/B
Description Trunk port towards the other Service Provider Switch(s)
Switchport trunk encap dot1q
Switchport mode trunk
Task 3
Configure the Customer Side Switches with Dot1Q trunking
encapsulation.
SW1
Interface F0/B
Description Trunk port towards the Service Provider Cloud
Switchport trunk encap dot1q
Switchport mode trunk
SW4
Interface F0/B
Copyrights Netmetric Solutions FZC 2006-2010
Website: http://www.netmetricsolutionsfzc.com; Email: khawarb@khawarb.com
113 of 241
114 of 241
R1
192.1.15.0/24 VLAN 10
VLAN 10 Primary
F 0/0 (.1)
192.1.100.0/24
F 0/0 (.2)
R2
F 0/0 (.4)
F0/0 (.3)
R3
VLAN 20 Community
R4
F 0/0 (.5)
R5
VLAN 30 Isolated
Address
192.1.100.1
Subnet Mask
255.255.255.0
R2
Interface IP
F 0/0
Address
192.1.100.2
Subnet Mask
255.255.255.0
R3
Interface IP
F 0/0
Address
192.1.100.3
Subnet Mask
255.255.255.0
115 of 241
R4
Interface IP
F 0/0
Address
192.1.100.4
Subnet Mask
255.255.255.0
R5
Interface IP
F 0/0
Address
192.1.100.5
Subnet Mask
255.255.255.0
Task 1
Configure VTP Transparent mode in SW1 and create the following
configuration:
Vlan 10 as Private-Vlan Primary
Vlan 20 as Private-Vlan Community
Vlan 30 as Private-Vlan Isolated
SW1
Vtp mode transparent
!
Vlan 10
Private-vlan primary
!
Vlan 20
Private-vlan community
!
Vlan 30
Private-vlan isolated
!
Vlan 10
Private-vlan association add 20, 30
Task 2
Configure SW1 such that the following is accomplished keeping the VLAN
designations from Task1:
116 of 241
SW1
Interface F0/1
Switchport mode private-vlan promiscuous
Switchport private-vlan mapping 10 add 20 , 30
!
Interface range F0/2 3
Switchport mode private-vlan host
Switchport private-vlan host-assoc 10 20
!
Interface range F0/4 5
Switchport mode private-vlan host
Switchport private-vlan host-assoc 10 30
erface on SW1 Private-vlan Mode Primary Vlan Secondary Vlans
117 of 241
Explanation:
Private VLANs provide Layer 2 isolation between ports within the same
private VLAN. There are
three types of private VLAN ports:
PromiscuousA promiscuous port can communicate with all
interfaces, including the community and isolated ports within a private
VLAN.
IsolatedAn isolated port has complete Layer 2 separation from other
ports within the same private VLAN except for the promiscuous port.
Private VLANs block all traffic to isolated ports except traffic from
promiscuous ports. Traffic received from an isolated port is forwarded
only to promiscuous ports.
CommunityCommunity ports communicate among themselves and
with their promiscuous ports. These interfaces are isolated at Layer 2
from all other interfaces in other communities or isolated ports within
their private VLAN.
NOTE: Because trunks can support the VLANs carrying traffic between
isolated, community, and promiscuous ports, isolated and community
port traffic might enter or leave the switch through a trunk interface.
Private VLAN ports are associated with a set of supporting VLANs that
are used to create the private VLAN structure. A private VLAN uses
VLANs three ways:
Primary VLANCarries traffic from promiscuous ports to isolated,
community, and other promiscuous ports.
Isolated VLANCarries traffic from isolated ports to promiscuous
ports.
Community VLANCarries traffic between community ports and to
promiscuous ports. You can configure multiple community VLANs in a
private VLAN.
NOTE: Isolated and community VLANs are both called secondary
VLANs.
A promiscuous port can serve only one primary VLAN and can serve as
many isolated or community VLANs as desired
118 of 241
119 of 241
Explanation:
Forwarding delay is the time spent by a port in the learning and
listening states.
By default it has a value of 15 seconds so a normal port without portfast
enable on it usually takes 50 seconds to start forwarding packets
because it goes through learning (15 seconds) plus listening (15 seconds)
and maximum age time (which is 20 seconds by default) when changing
the forwarding delay to 8 the time the port for the first time a desktop is
plugged into a port in a switch it would take 8 + 8 + 20 (if its using the
default value) so it would takes 36 seconds instead of 50 seconds in that
case.
120 of 241
blocking
listening
learning
forwarding
disabled
STP dictates that the port starts out blocking, and then immediately
moves through the listening and learning phases.
By default, the port spends approximately 15 seconds listening and 15
seconds learning.
During the listening state, the switch tries to determine where the port
fits in
the spanning tree topology. The switch especially wants to know whether
this port is part of a physical loop. If the port is part of a loop, the port
can be chosen to go into blocking mode.
The blocking state means that the port does not send or receive user
data in order to eliminate loops.
Copyrights Netmetric Solutions FZC 2006-2010
Website: http://www.netmetricsolutionsfzc.com; Email: khawarb@khawarb.com
121 of 241
If the port is not part of a loop, the port proceeds to the learning state, in
which the port learns which MAC addresses live off this port. This entire
STP initialization process takes about 30 seconds.
If you connect a workstation or a server with a single NIC card or an IP
phone to a switch port, the connection cannot create a physical loop.
These connections are considered leaf nodes. There is no reason to make
the workstation wait 30 seconds while the switch checks for loops if the
workstation cannot cause a loop.
Cisco added the PortFast or fast-start feature. With this feature,
the STP for this port assumes that the port is not part of a loop and
immediately moves to the forwarding state and does not go through the
blocking, listening, or learning states. This command does not turn STP
off. This command makes STP skip a few initial steps (unnecessary
steps, in this circumstance) on the selected port.
NOTE: Never use the PortFast feature on switch ports that connect to
other switches, hubs, or routers. These connections can cause physical
loops, and spanning tree must go through the full initialization
procedure in these situations. A spanning tree loop can bring your
network down. If
you turn on PortFast for a port that is part of a physical loop, there can
be a window of time when packets are continuously forwarded (and can
even multiply) in such a way that the network cannot recover.
At the global level, you enable BPDU guard on Port Fast-enabled NNIs by
using the spanning-tree portfast bpduguard default global
configuration command. Spanning tree shuts down NNIs that are in a
Port Fast-operational state if any BPDU is received on those NNIs.
In a valid configuration, Port Fast-enabled NNIs do not receive BPDUs.
Receiving a BPDU on a Port Fastenabled NNI signals an invalid
configuration, such as the connection of an unauthorized device,and the
BPDU guard feature puts the interface in the error-disabled state.
At the interface level, you enable BPDU guard on any NNI by using the
spanning-tree bpduguard enable interface configuration command
without also enabling the Port Fast feature. When the NNI receives a
BPDU, it is put in the error-disabled state.
122 of 241
123 of 241
Explanation:
Port Fast-enabled ports do not receive BPDUs. Receiving a BPDU on a
Port Fast-enabled port signals an invalid configuration, such as the
connection of an unauthorized device, and the BPDU guard feature puts
the port in the error-disabled state.
The BPDU guard feature provides a secure response to invalid
configurations because you must manually put the port back in service.
Use the BPDU guard feature in a service-provider network to prevent an
access port
from participating in the spanning tree.
Use the spanning-tree portfast default global configuration command
to globally enable the Port Fast feature on all nontrunking ports.
Configure Port Fast only on ports that connect to end stations; otherwise,
an accidental topology loop could cause a data packet loop and disrupt
switch and network operation. A Port Fast-enabled port moves directly to
the spanning-tree
forwarding state when linkup occurs without waiting for the standard
forward-delay time.
You can also configure bpduguard under an interface using the
command spanning-tree bpduguard.
124 of 241
125 of 241
Output of command:
SW
show spanning-tree summary
Switch is in pvst mode
Root bridge for: none
EtherChannel misconfig guard is enabled
Extended system ID is enabled
Portfast Default is disabled
PortFast BPDU Guard Default is disabled
Portfast BPDU Filter Default is enabled
Loopguard Default is disabled
UplinkFast is disabled
BackboneFast is disabled
Configured Pathcost method used is short
126 of 241
127 of 241
128 of 241
Explanation:
BackboneFast is initiated when a root port or blocked port on a switch
eceives inferior BPDUs from its designated bridge.
An inferior BPDU identifies one switch as both the root bridge and the
designated bridge. When a switch receives an inferior BPDU, it indicates
that a link to which the switch is not directly connected (an indirect link)
has failed (that is, the designated bridge has lost its connection to the
root bridge). Under normal spanning-tree rules, the switch ignores
inferior BPDUs for the configured maximum aging time, as specified by
the agingtime variable.
The switch tries to determine if it has an alternate path to the root
bridge. If the inferior BPDU arrives on a blocked port, the root port and
other blocked ports on the switch become alternate paths to the root
bridge. (Self-looped ports are not considered alternate paths to the root
bridge.)If the inferior BPDU arrives on the root port, all blocked ports
become alternate paths to the rootbridge.
If the inferior BPDU arrives on the root port and there are no blocked
ports, the switch assumes that it has lost connectivity to the root bridge,
causes the maximum aging time on the root to expire, and becomes the
root switch according to normal spanning-tree rules.
If the switch has alternate paths to the root bridge, it uses these
alternate paths to transmit a new kind of PDU called the Root Link
Query PDU. The switch sends the Root Link Query PDU out all
alternate paths to the root bridge.
If the switch determines that it still has an alternate path to the root, it
causes the maximum aging time on the ports on which it received the
inferior BPDU to expire. If all the alternate paths to the root bridge
indicate that the switch has lost connectivity to the root bridge, the
switch causes the maximum aging times on the ports on which it
received an inferior BPDU to expire.
If one or more alternate paths can still connect to the root bridge, the
switch makes all ports on which it received an inferior BPDU its
designated ports and moves them out of the blocking state (if they were
in blocking state), through the listening and learning states, and into the
forwarding state.
129 of 241
130 of 241
Module 8 IPv6
131 of 241
R1
Lo 0
R2
F 0/0
Lo 0
F 0/0
2001:1:1:12::/64
S 0/0
2001:1:1:23::/64
S 0/0
2001:1:1:34::/64
Lo 0
F 0/0
Lo 0
F 0/0
R4
R3
Task 1
Enable IPv6 routing on R1,R2, R3 and R4. Assign IPv6 addresses to the F
0/0 interface of the routers as follows:
R1
R2
R3
R4
2001:1:1:12::1
2001:1:1:12::2
2001:1:1:34::3
2001:1:1:34::4
/64
/64
/64
/64
R1
R2
ipv6 unicast-routing
Interface F 0/0
ipv6 address 2001:1:1:12::1/64
no shut
R3
Ipv6 unicast-routing
Interface F 0/0
Ipv6 address 2001:1:1:12::2/64
No shut
R4
ipv6 unicast-routing
Interface F 0/0
ipv6 address 2001:1:1:34::3/64
no shut
Ipv6 unicast-routing
Interface F 0/0
Ipv6 address 2001:1:1:34::4/64
No shut
Task 2
Configure the Loopback0 interface on all routers as follows:
Copyrights Netmetric Solutions FZC 2006-2010
Website: http://www.netmetricsolutionsfzc.com; Email: khawarb@khawarb.com
132 of 241
R1
R2
R3
R4
Loopback0
Loopback0
Loopback0
Loopback0
2000:1:1:1::/64
2000:2:2:2::/64
2000:3:3:3::/64
2000:4:4:4::/64
R1
Interface Loopback 0
Ipv6 address 2000:1:1:1::/64 eui-64
R2
Interface Loopback 0
ipv6 address 2000:2:2:2::/64 eui-64
R3
Interface Loopback 0
Ipv6 address 2000:3:3:3::/64 eui-64
R4
Interface Loopback 0
ipv6 address 2000:4:4:4::/64 eui-64
Task 3
Configure Frame-relay between R2 and R3 using the folloing IPV6
addresses:
R2 2000:1:1:23::2/64
R3 2000:1:1:23::3/64
Ensure that the routers can ping each others serial interface. Also allow
R2 and R3 to ping their own IP addresses. Use a sun-interface on R2 and
R3 for the Frame relay configuration.
R2
Interface S0/0
Encap frame-relay
No shut
!
Interface S 0/0.3 point-to-point
ipv6 address 2001:1:1:23::2/64
frame-relay interface-dlci 203
R3
Copyrights Netmetric Solutions FZC 2006-2010
Website: http://www.netmetricsolutionsfzc.com; Email: khawarb@khawarb.com
133 of 241
Interface S0/0
Encap frame-relay
no shut
!
Interface S 0/0.2 point-to-point
ipv6 address 2001:1:1:23::3/64
frame-relay interface-dlci 302
Task 4
Configure RIPng on all routers to route all loopbacks. Enable RIPng
under the following interfaces:
R1
R2
R3
R4
F
F
F
F
0/0,
0/0,
0/0,
0/0,
Loopback
Loopback
Loopback
Loopback
0
0, S 0/0.3
0, S 0/0.2
0
R1
R2
Interface Loopback 0
ipv6 rip 100 enable
Interface Loopback 0
ipv6 rip 100 enable
Interface F 0/0
ipv6 rip 100 enable
Interface S 0/0.3
ipv6 rip 100 enable
!
Interface F 0/0
ipv6 rip 100 enable
R4
R3
Interface Loopback 0
ipv6 rip 100 enable
!
Interface F 0/0
ipv6 rip 100 enable
!
Interface S0/0.2
ipv6 rip 100 enable
Interface Loopback 0
ipv6 rip 100 enable
Interface F 0/0
ipv6 rip 100 enable
134 of 241
R2
No ipv6 unicast-routing
!
ipv6 unicast-routing
R3
No ipv6 unicast-routing
!
ipv6 unicast-routing
R4
No ipv6 unicast-routing
!
ipv6 unicast-routing
No ipv6 unicast-routing
!
ipv6 unicast-routing
Task 2
Configure the routers in OSPFv3 area 0 and advertise their directly
connected interfaces in this area
R1
R2
135 of 241
R3
R4
Task 3
Ensure that the loopback interfaces are advertised with their correct
mask.
R1
R2
Interface Loopback0
ipv6 ospf network point-to-point
Interface Loopback0
ipv6 ospf network point-to-point
R3
R4
Interface Loopback0
ipv6 ospf network point-to-point
Interface Loopback0
ipv6 ospf network point-to-point
136 of 241
R1
Lo 0
R2
F 0/0
Lo 0
F 0/0
2001:1:1:12::/64
S 0/0
192.1.23.0/24
S 0/0
2001:1:1:34::/64
Lo 0
F 0/0
Lo 0
F 0/0
R4
R3
Task 1
Enable IPv6 routing on R1,R2, R3 and R4. Assign IPv6 addresses to the F
0/0 interface of the routers as follows:
R1
R2
R3
R4
2001:1:1:12::1
2001:1:1:12::2
2001:1:1:34::3
2001:1:1:34::4
/64
/64
/64
/64
R1
R2
ipv6 unicast-routing
Interface F 0/0
ipv6 address 2001:1:1:12::1/64
no shut
R3
Ipv6 unicast-routing
Interface F 0/0
Ipv6 address 2001:1:1:12::2/64
No shut
R4
ipv6 unicast-routing
Interface F 0/0
ipv6 address 2001:1:1:34::3/64
no shut
Ipv6 unicast-routing
Interface F 0/0
Ipv6 address 2001:1:1:34::4/64
No shut
Task 2
Copyrights Netmetric Solutions FZC 2006-2010
Website: http://www.netmetricsolutionsfzc.com; Email: khawarb@khawarb.com
137 of 241
R1
R2
R3
R4
Loopback0
Loopback0
Loopback0
Loopback0
2000:1:1:1::/64
2000:2:2:2::/64
2000:3:3:3::/64
2000:4:4:4::/64
R1
R2
Interface Loopback 0
Ipv6 address 2000:1:1:1::/64 eui-64
R3
Interface Loopback 0
ipv6 address 2000:2:2:2::/64 eui-64
R4
Interface Loopback 0
Ipv6 address 2000:3:3:3::/64 eui-64
Interface Loopback 0
ipv6 address 2000:4:4:4::/64 eui-64
Task 3
Configure RIPng between R1 and R2. Enable RIPng under the following
interfaces:
R1 F 0/0, Loopback 0
R2 F 0/0, Loopback 0
R1
R2
Interface Loopback 0
ipv6 rip 100 enable
!
Interface F 0/0
ipv6 rip 100 enable
Interface Loopback 0
ipv6 rip 100 enable
!
Interface F 0/0
ipv6 rip 100 enable
Task 4
Configure RIPng between R3 and R4. Enable RIPng under the following
interfaces:
R3 F 0/0, Loopback 0
R4 F 0/0, Loopback 0
R3
R4
Interface Loopback 0
ipv6 rip 100 enable
!
Interface F 0/0
ipv6 rip 100 enable
Interface Loopback 0
ipv6 rip 100 enable
!
Interface F 0/0
ipv6 rip 100 enable
138 of 241
Task 5
Configure the Frame Relay link between R2 and R3 as an IPv4 Link on
the 192.1.23.0/24 network.
R2
Interface S0/0
Ip address 192.1.23.2 255.255.255.0
Encap frame-relay
No frame-relay inverse-arp
Frame-relay map ip 192.1.23.3 203 broadcast
No shut
R3
Interface S0/0
Ip address 192.1.23.3 255.255.255.0
Encap frame-relay
No frame-relay inverse-arp
Frame-relay map ip 192.1.23.2 302 broadcast
No shut
Task 6
Create a Tunnel between R2 and R3 Assign it an IPv6 address of
2001:23:23:23::/64. Set the Tunnel Mode to IPv6. Enable RIPng on the
Tunnel Interface.
R2
R3
Interface Tunnel 23
Tunnel source S 0/0
Tunnel destination 192.1.23.3
Ipv6 address 2001:23:23:23::2/64
Ipv6 enable
Ipv6 rip CCIERS enable
Tunnel mode IPV6IP
No shut
Interface Tunnel 23
Tunnel source S 0/0
Tunnel destination 192.1.23.2
Ipv6 address 2001:23:23:23::3/64
Ipv6 enable
Ipv6 rip CCIERS enable
Tunnel mode IPV6IP
No shut
139 of 241
S 0/0 .123
R2
S 0/0 .14
S 0/0
S 0/0
R4
Frame-Relay
S 0/0
R3
IPv6 Address
2001:1:1:1::1
2001:1:1:123::1
2001:1:1:14::1
Subnet Mask
/64
/64
/64
IPv6 Address
2001:2:2:2::2
2001:1:1:123::2
Subnet Mask
/64
/64
R2
Interface
Loopback 0
S 0/0
140 of 241
R3
Interface
Loopback 0
S 0/0
IPv6 Address
2001:3:3:3::3
2001:1:1:123::3
Subnet Mask
/64
/64
IPv6 Address
2001:4:4:4::4
2001:1:1:14::4
Subnet Mask
/64
/64
R4
Interface
Loopback 0
S 0/0
Task 1
Configure the routers connected to the frame-relay cloud as follows:
o R1 (The HUB) must be configured with two sub-interfaces. The
first one of the two sub-interfaces must be configured to
connect R1 to R4. Configure the interface based on the IPv6
addressing table
o The second sub-interface on R1 must be configured in a
multipoint manner. This sub-interface must be configured to
connect R1 to routers R2 and R3 using the IPv6 addressing
table.
o Routers R2, R3 should not be configured with a sub-interface
and these routers should NOT rely on Inverse-arp.
141 of 241
R1
Ipv6 unicast-routing
Int S0/0
Encapsulation frame-relay
No frame-relay inverse
No shut
!
Int S0/0.14 point-to-point
Ipv6 enable
Ipv6 address 2001:1:1:14::1/64
Frame-relay interface-dlci 104
!
Int S0/0.123 multipoint
Ipv6 enable
Ipv6 address 2001:1:1:123::1/64
Frame-relay map ipv6 2001:1:1:123::2 102 broadcast
Frame-relay map ipv6 2001:1:1:123::3 103 broadcast
R2
Ipv6 unicast-routing
Int S0/0
Ipv6 enable
Ipv6 address 2001:1:1:123::2/64
Encapsulation frame
No frame-relay inverse
Frame-relay map ipv6 2001:1:1:123::1 201 broadcast
Frame-relay map ipv6 2001:1:1:123::3 201
No shut
Exit
142 of 241
R3
Ipv6 unicast-routing
Int S0/0
Encapsulation frame
Ipv6 enable
Ipv6 address 2001:1:1:123::3/64
Frame-relay map ipv6 2001:1:1:123::1 301 broadcast
Frame-relay map ipv6 2001:1:1:123::2 301 broadcast
No frame-relay inverse
No shut
R4
Ipv6 unicast-routing
Ipv6 unicast-routing
Int S0/0
Encapsulation frame
Ipv6 enable
Ipv6 address 2001:1:1:14::4/64
Frame-relay map ipv6 2001:1:1:14::1 401 broadcast
No frame-relay inverse
No shut
Task 2
Configure the routers in OSPFv3 area 0 and advertise their directly
connected interfaces in this area. Also Configure Loopbacks on all 4
Routers using the 2001:X:X:X::X/64 format
143 of 241
R1
IPv6 router ospf 1
router-id 1.1.1.1
!
Interface Loopback 0
ipv6 address 2001:1:1:1::1/64
ipv6 ospf 1 area 0
!
Interface S 0/0.14
ipv6 ospf 1 area 0
!
Interface S 0/0.123
ipv6 ospf 1 area 0
Frame-relay map ipv6 Link-Local 102
Frame-relay map ipv6 Link-Local 103
ipv6 ospf network point-to-multipoint
Note: Find the Link-Local Address for R2 and R3 by using Show IPv6 int
brief on R2 and R3 respectively. This is required for OSPFv3 Neighbor
relationship to be established
R2
IPv6 router ospf 1
router-id 2.2.2.2
!
Interface Loopback 0
ipv6 address 2001:2:2:2::2/64
ipv6 ospf 1 area 0
!
Interface S 0/0
ipv6 ospf 1 area 0
Frame-relay map ipv6 Link-Local 201
ipv6 ospf network point-to-multipoint
Note: Find the Link-Local Address for R1 by using Show IPv6 int brief
on R1. This is required for OSPFv3 Neighbor relationship to be
established.
144 of 241
R3
IPv6 router ospf 1
router-id 3.3.3.3
!
Interface Loopback 0
ipv6 address 2001:3:3:3::3/64
ipv6 ospf 1 area 0
!
Interface S 0/0
ipv6 ospf 1 area 0
Frame-relay map ipv6 Link-Local 301
ipv6 ospf network point-to-multipoint
Note: Find the Link-Local Address for R1 by using Show IPv6 int brief
on R1. This is required for OSPFv3 Neighbor relationship to be
established.
R4
IPv6 router ospf 1
router-id 4.4.4.4
!
Interface Loopback 0
ipv6 address 2001:4:4:4::4/64
ipv6 ospf 1 area 0
!
Interface S 0/0
ipv6 ospf 1 area 0
Frame-relay map ipv6 Link-Local 401
ipv6 ospf network point-to-point
Note: Find the Link-Local Address for R1 by using Show IPv6 int brief
on R1. This is required for OSPFv3 Neighbor relationship to be
established.
Task 3
Ensure that the loopback interfaces are advertised with their correct
mask.
R1
R2
Interface Loopback 0
Ipv6 ospf network point-to-point
R3
Interface Loopback 0
Ipv6 ospf network point-to-point
R4
145 of 241
Interface Loopback 0
Ipv6 ospf network point-to-point
Interface Loopback 0
Ipv6 ospf network point-to-point
146 of 241
147 of 241
R1
F 0/0 (.1)
192.1.11.0/24 VLAN 11
F 0/0 (.3)
F 0/0 (.4)
R4
R3
F 0/1(.3)
F 0/1 (.4)
192.1.22.0/24 VLAN 22
F0/0(.2)
R2
F 0/1(.2)
192.1.33.0/24 VLAN 33
F 0/0 (.5)
R5
IP Address
1.1.1.1
192.1.11.1
Subnet Mask
255.0.0.0
255.255.255.0
IP Address
2.2.2.2
192.1.22.2
192.1.33.2
Subnet Mask
255.0.0.0
255.255.255.0
255.255.255.0
IP Address
Subnet Mask
R2
Interface
Loopback 0
F 0/0
F 0/1
R3
Interface
148 of 241
Loopback 0
F 0/0
F 0/1
3.3.3.3
192.1.11.3
192.1.22.3
255.0.0.0
255.255.255.0
255.255.255.0
IP Address
4.4.4.4
192.1.11.4
192.1.22.4
Subnet Mask
255.0.0.0
255.255.255.0
255.255.255.0
IP Address
5.5.5.5
192.1.33.5
Subnet Mask
255.0.0.0
255.255.255.0
R4
Interface
Loopback 0
F 0/0
F 0/1
R5
Interface
Loopback 0
F 0/0
Task 1
R1 is the ISP Router. It is simulating the Internet. R3 & R4 should point
to R1 as the default gateway. R1, R3 and R4 should also run EIGRP in
AS 11. R1 should advertise its loopback in EIGRP 11.
R1
Router eigrp 11
No auto-summary
Network 192.1.11.0
Network 1.0.0.0
R3
R4
Task 2
Configure Multigroup HSRP between R3 and R4 on the 192.1.22.0
segment. R3 should be the Active router and R4 should be the Standby
router for Standby Group 1. Group 1 should use 192.1.22.11 as the
Standby address. Set the Priority for R3 as 105 for this group. Make sure
R3 is the Active router whenever it is up. Configure a authenticated
HSRP connection between the routers. Use ccie as the password. If the
active HSRP router for this group loses the 1.0.0.0 route from the routing
Copyrights Netmetric Solutions FZC 2006-2010
Website: http://www.netmetricsolutionsfzc.com; Email: khawarb@khawarb.com
149 of 241
table, it should decrement the priority by 20 and the other router should
become the Active HSRP router.
R3
track 1 ip route 1.0.0.0/8 reachability
!
Interface F 0/1
Standby 1 ip 192.1.22.11
Standby 1 priority 105
Standby 1 preempt
Standby 1 authentication ccie
Standby 1 track 1 decrement 20
R4
track 1 ip route 1.0.0.0/8 reachability
!
Interface F 0/1
Standby 1 ip 192.1.22.11
Standby 1 preempt
Standby 1 authentication ccie
Standby 1 track 1 decrement 20
Task 3
Configure Multigroup HSRP between R3 and R4 on the 192.1.22.0
segment. R4 should be the Active router and R3 should be the Standby
router for Standby Group 2. Group 2 should use 192.1.22.12 as the
Standby address. Set the Priority for R4 as 105 for this group. Make sure
R4 is the Active router whenever it is up. Configure a authenticated
HSRP connection between the routers. Use ccie as the password. If the
F0/0 interface goes down on the active HSRP router for this group, it
should decrement the priority by 20 and the other router should become
the Active HSRP router.
R3
Interface F 0/1
Standby 2 ip 192.1.22.12
Standby 2 preempt
Standby 2 authentication ccie
Standby 2 track Fast 0/0 20
R4
Interface F 0/1
Standby 2 ip 192.1.22.12
Copyrights Netmetric Solutions FZC 2006-2010
Website: http://www.netmetricsolutionsfzc.com; Email: khawarb@khawarb.com
150 of 241
Standby
Standby
Standby
Standby
2
2
2
2
preempt
priority 105
authentication ccie
track Fast 0/0 20
151 of 241
IP ADDRESS : 192.1.22.0
WINS ADDRESS : 192.1.22.5
DNS ADDRESS : 192.1.22.6, 192.1.22.7
DEFAULT GATEWAY : 192.1.22.11
LEASE TIME : 3 Days 12 hours
Excluded addresses : 192.1.22.2 4 & 192.1.22.34
R3
ip dhcp excluded-address 192.1.22.2 192.1.22.4
ip dhcp excluded-address 192.1.22.11
!
ip dhcp pool VLAN22
network 192.1.22.0 255.255.255.0
netbios-name-server 192.1.22.5
dns-server 192.1.22.6 192.1.22.7
default-router 192.1.22.11
lease 3 12
Task 2
Disable the DHCP server service on R4
R4
No service dhcp
152 of 241
153 of 241
154 of 241
155 of 241
156 of 241
157 of 241
IP ADDRESS : 192.1.33.0
WINS ADDRESS : 192.1.22.5
DNS ADDRESS : 192.1.22.6, 192.1.22.7
DEFAULT GATEWAY : 192.1.33.2
LEASE TIME : 3 Days 12 hours
Excluded addresses : 192.1.33.2 & 192.1.33.5
R3
ip dhcp excluded-address 192.1.33.2
ip dhcp excluded-address 192.1.33.5
!
ip dhcp pool VLAN33
network 192.1.33.0 255.255.255.0
netbios-name-server 192.1.22.5
dns-server 192.1.22.6 192.1.22.7
default-router 192.1.33.2
lease 3 12
Task 2
Configure R2 to forward incoming DHCP Address request broadcasts to
R3, which is the DHCP Server.
R2
Interface F 0/1
Ip helper-address 192.1.22.3
158 of 241
R4
Task 2
Configure R3 and R4 as GLBP AVGs for VLAN 22. Use 22 as the GLBP
Group number and .34 as the Virtual IP Address. R4 should be the
preferred AVG.
R3
Interface F 0/1
GLBP 22 ip 192.1.22.34
R4
Interface F 0/1
GLBP 22 ip 192.1.22.34
GLBP 22 priority 102
GLBP 22 preempt
159 of 241
Module 10 Security
160 of 241
R1
F 0/0 (.1)
192.1.11.0/24 VLAN 11
F 0/0 (.3)
F 0/0 (.4)
R4
R3
F 0/1(.3)
F 0/1 (.4)
192.1.22.0/24 VLAN 22
F0/0(.2)
VLAN 22 (.15)
R2
SW1
F 0/1(.2)
192.1.33.0/24 VLAN 33
F 0/0 (.5)
R5
IP Address
1.1.1.1
192.1.11.1
Subnet Mask
255.0.0.0
255.255.255.0
IP Address
2.2.2.2
192.1.22.2
192.1.33.2
Subnet Mask
255.0.0.0
255.255.255.0
255.255.255.0
R2
Interface
Loopback 0
F 0/0
F 0/1
161 of 241
R3
Interface
Loopback 0
F 0/0
F 0/1
IP Address
3.3.3.3
192.1.11.3
192.1.22.3
Subnet Mask
255.255.255.0
255.255.255.0
255.255.255.0
IP Address
4.4.4.4
192.1.11.4
192.1.22.4
Subnet Mask
255.255.255.0
255.255.255.0
255.255.255.0
IP Address
5.5.5.5
192.1.33.5
Subnet Mask
255.0.0.0
255.255.255.0
IP Address
15.15.15.15
192.1.22.15
Subnet Mask
255.0.0.0
255.255.255.0
R4
Interface
Loopback 0
F 0/0
F 0/1
R5
Interface
Loopback 0
F 0/0
SW1
Interface
Loopback 0
VLAN 22
Task 1
Configure EIGRP in AS 100 on all routers and SW1 to route all networks.
R1
R2
162 of 241
Network 3.0.0.0
R5
Network 4.0.0.0
SW1
Task 2
Configure Telnet on SW1 based on the following requirements:
SW1
Aaa new-model
!
Username admin password admin
!
Aaa authentication login L-AUTHEN local
Aaa authentication login NO-AUTHEN none
!
access-list 5 permit 1.0.0.0 0.255.255.255
access-list 5 permit 192.1.11.0 0.0.0.255
access-list 5 permit 192.1.22.0 0.0.0.255
!
line vty 0 4
access-class 5 in
login authentication L-AUTHEN
transport output none
!
line console 0
login authentication NO-AUTHEN
transport output none
Copyrights Netmetric Solutions FZC 2006-2010
Website: http://www.netmetricsolutionsfzc.com; Email: khawarb@khawarb.com
163 of 241
164 of 241
165 of 241
166 of 241
queue-limit 200
control-plane host
service-policy type queue-threshold input QT-POLICY
167 of 241
168 of 241
Lab 6Lab
Configuring
IP TCP
Intercept
4 Blocking Attacks
using NBAR
(Optional)
(Builds on Lab 5)
Task 1
The Web Server at 192.1.33.55 is getting overwhelmed by syn-attacks.
R2 should watch the traffic and if it does not complete the TCP
handshake in 10 seconds, it should drop the packets.
R2
Access-list 161 permit tcp any host 192.1.33.55 eq www
!
Ip tcp intercept mode watch
Ip tcp intercept watch-timeout 10
Ip tcp intercept list 161
169 of 241
170 of 241
Module 11 MPLS
171 of 241
R2
R3
F 0/0.23 (.2)
F 0/0.23 (.3)
192.1.23.0/24 VLAN 23
F 0/0.12 (.2)
F 0/0.34 (.3)
192.1.12.0/24 VLAN 12
192.1.34.0/24 VLAN 34
SP Core
AS 12353
OSPF Area 0
F 0/0.12 (.1)
F 0/0.34 (.4)
R1
R4
F 0/0.15 (.1)
F 0/0.47 (.4)
F 0/0.48 (.4)
F 0/0.16 (.1)
192.1.15.0/24
VLAN 15
F 0/0 (.5)
R5
C1-Site1
192.1.47.0/24
VLAN 47
192.1.16.0/24
VLAN 16
F 0/0.16 (.6)
F 0/0.47 (.7)
R6
R7
C2-Site1
192.1.48.0/24
VLAN 48
F 0/0 (.8)
R8
C2-Site2
C1-Site2
172 of 241
IP Address
1.1.1.1
11.11.11.11
192.1.12.1
192.1.15.1
192.1.16.1
Subnet Mask
255.0.0.0
255.255.0.0
255.255.255.0
255.255.255.0
255.255.255.0
Interface
Loopback 0
F 0/0.12
F 0/0.23
R3
IP Address
2.2.2.2
192.1.12.2
192.1.23.2
Subnet Mask
255.0.0.0
255.255.255.0
255.255.255.0
Interface
Loopback 0
F 0/0.23
F 0/0.34
R4
IP Address
3.3.3.3
192.1.23.3
192.1.34.3
Subnet Mask
255.0.0.0
255.255.255.0
255.255.255.0
Interface
Loopback 0
Loopback 1
F 0/0.34
F 0/0.47
F 0/0.48
R5
IP Address
4.4.4.4
44.44.44.44
192.1.34.4
192.1.47.4
192.1.48.4
Subnet Mask
255.0.0.0
255.255.0.0
255.255.255.0
255.255.255.0
255.255.255.0
Interface
Loopback 0
F 0/0
IP Address
10.5.5.5
192.1.15.5
Subnet Mask
255.255.255.0
255.255.255.0
173 of 241
R6
Interface
Loopback 0
F 0/0.16
R7
IP Address
10.6.6.6
192.1.16.6
Subnet Mask
255.255.255.0
255.255.255.0
Interface
Loopback 0
F 0/0.47
IP Address
10.7.7.7
192.1.47.7
Subnet Mask
255.255.255.0
255.255.255.0
IP Address
10.8.8.8
192.1.48.8
Subnet Mask
255.255.255.0
255.255.255.0
R8
Interface
Loopback 0
F 0/0
Task 1
Configure OSPF between all the SP routers (R1, R2, R3, R4). OSPF
process should use Loopback0 on each router as the router-id. Advertise
all links in OSPF except Loopack 1s on R1 and R4. Loopback 0s should
appear with a /8 mask in the routing table.
R1
R2
Interface Loopback 0
Ip ospf network point-to-point
!
Router ospf 1
Router-id 1.1.1.1
Network 1.1.1.1 0.0.0.0 area 0
Network 192.1.12.1 0.0.0.0 area 0
Interface Loopback 0
Ip ospf network point-to-point
!
Router ospf 1
Router-id 2.2.2.2
Network 2.2.2.2 0.0.0.0 area 0
Network 192.1.12.2 0.0.0.0 area 0
Network 192.1.23.2 0.0.0.0 area 0
R4
R3
Interface Loopback 0
Ip ospf network point-to-point
!
Router ospf 1
Router-id 3.3.3.3
Network 3.3.3.3 0.0.0.0 area 0
Network 192.1.23.3 0.0.0.0 area 0
Network 192.1.34.3 0.0.0.0 area 0
Interface Loopback 0
Ip ospf network point-to-point
!
Router ospf 1
Router-id 4.4.4.4
Network 4.4.4.4 0.0.0.0 area 0
Network 192.1.34.4 0.0.0.0 area 0
Task 2
Copyrights Netmetric Solutions FZC 2006-2010
Website: http://www.netmetricsolutionsfzc.com; Email: khawarb@khawarb.com
174 of 241
R4
Task 3
Configure MPLS on all the physical links in the SP Network. Use LDP to
distribute labels. The LDP neighbour relationships should be formed
based on the most reliable interface. The Labels should be assigned from
the range X00 X99, where X is the router number.
R1
R2
R3
Mpls ldp router-id Loopback0
Mpls label protocol LDP
Mpls label range 300 399
!
Interface F 0/0.23
Mpls ip
!
Interface F 0/0.34
Mpls ip
175 of 241
R2
176 of 241
R4
Task 2
Configure a VRF CUST-A with a RD value of 1:100 on R1 and R4. Use
the same extended community for your Route-target import and export.
Assign this VRF to the links that connect to C1 sites on R1 and R4.
R1
R4
ip vrf CUST-A
rd 1:100
route-target both 1:100
!
Interface F 0/0.15
Ip vrf forwarding CUST-A
Ip address 192.1.15.1 255.255.255.0
ip vrf CUST-A
rd 1:100
route-target both 1:100
!
Interface F 0/0.48
Ip vrf forwarding CUST-A
Ip address 192.1.48.4 255.255.255.0
Task 3
Configure a static route on R1 in the CUST-A vrf to reach the 10.5.5.0 on
R5. Inject this route into BGP such that it should be reachable from
CUST-A VRF on R4. Configure a default Route on R5 towards R1.
Copyrights Netmetric Solutions FZC 2006-2010
Website: http://www.netmetricsolutionsfzc.com; Email: khawarb@khawarb.com
177 of 241
R1
ip route vrf CUST-A 10.5.5.0 255.255.255.0 192.1.15.5
!
Router BGP 12353
!
Address-family ipv4 vrf CUST-A
Redistribute static
R5
ip route 0.0.0.0 0.0.0.0 192.1.15.1
Task 4
Configure a static route on R4 in the CUST-A vrf to reach the 10.8.8.0 on
R8. Inject this route into BGP such that it should be reachable from
CUST-A VRF on R1. Configure a default Route on R8 towards R4.
R4
ip route vrf CUST-A 10.8.8.0 255.255.255.0 192.1.48.8
!
Router BGP 12353
!
Address-family ipv4 vrf CUST-A
Redistribute static
R8
ip route 0.0.0.0 0.0.0.0 192.1.48.4
Task 5
Configure a VRF CUST-B with a RD value of 1:200 on R1 and R4. Use
the same extended community for your Route-target import and export.
Assign this VRF to the links that connect to C2 sites on R1 and R4.
R1
R4
ip vrf CUST-B
rd 1:200
route-target both 1:200
!
Interface F 0/0.16
Ip vrf forwarding CUST-B
Ip address 192.1.16.1 255.255.255.0
ip vrf CUST-B
rd 1:200
route-target both 1:200
!
Interface F 0/0.47
Ip vrf forwarding CUST-B
Ip address 192.1.47.4 255.255.255.0
Task 6
Copyrights Netmetric Solutions FZC 2006-2010
Website: http://www.netmetricsolutionsfzc.com; Email: khawarb@khawarb.com
178 of 241
179 of 241
R4
Task 2
Configure a VRF CUST-A with a RD value of 1:100 on R1 and R4. Use
the same extended community for your Route-target import and export.
Assign this VRF to the links that connect to C1 sites on R1 and R4.
R1
R4
ip vrf CUST-A
rd 1:100
route-target both 1:100
!
Interface F 0/0.15
Ip vrf forwarding CUST-A
Ip address 192.1.15.1 255.255.255.0
ip vrf CUST-A
rd 1:100
route-target both 1:100
!
Interface F 0/0.48
Ip vrf forwarding CUST-A
Ip address 192.1.48.4 255.255.255.0
Task 3
Configure RIPv2 as the Routing Protocol between R5 and R1-vrf CUST-A.
Advertise all the routes on R5 in RIP. Advertise the VRF link in RIP on R1
under the appropriate address family. Make sure the VRF CUST-A on R4
has reachability to routes learned from R5.
Copyrights Netmetric Solutions FZC 2006-2010
Website: http://www.netmetricsolutionsfzc.com; Email: khawarb@khawarb.com
180 of 241
R1
Router RIP
!
Address-family ipv4 vrf CUST-A
Version 2
No auto-summary
Network 192.1.15.0
Redistribute BGP 12353 metric 1
!
Router BGP 12353
!
Address-family ipv4 vrf CUST-A
Redistribute rip
R5
Router RIP
Version 2
No auto-summary
Network 192.1.15.0
Network 10.0.0.0
Task 4
Configure RIPv2 as the Routing Protocol between R4 and R8-vrf CUST-A.
Advertise all the routes on R8 in RIP. Advertise the VRF link in RIP on R4
under the appropriate address family. Make sure the VRF CUST-A on R1
has reachability to routes learned from R8.
R4
Router RIP
!
Address-family ipv4 vrf CUST-A
Version 2
No auto-summary
Network 192.1.48.0
Redistribute BGP 12353 metric 1
!
Router BGP 12353
!
Address-family ipv4 vrf CUST-A
Redistribute rip
R8
Router RIP
Copyrights Netmetric Solutions FZC 2006-2010
Website: http://www.netmetricsolutionsfzc.com; Email: khawarb@khawarb.com
181 of 241
Version 2
No auto-summary
Network 192.1.48.0
Network 10.0.0.0
Task 5
Configure a VRF CUST-B with a RD value of 1:200 on R1 and R4. Use
the same extended community for your Route-target import and export.
Assign this VRF to the links that connect to C2 sites on R1 and R4.
R1
R4
ip vrf CUST-B
rd 1:200
route-target both 1:200
!
Interface F 0/0.16
Ip vrf forwarding CUST-B
Ip address 192.1.16.1 255.255.255.0
ip vrf CUST-B
rd 1:200
route-target both 1:200
!
Interface F 0/0.47
Ip vrf forwarding CUST-B
Ip address 192.1.47.4 255.255.255.0
Task 6
Configure RIPv2 as the Routing Protocol between R6 and R1-vrf CUST-B.
Advertise all the routes on R6 in RIP. Advertise the VRF link in RIP on R1
under the appropriate address family. Make sure the VRF CUST-B on R4
has reachability to routes learned from R6.
R1
Router RIP
!
Address-family ipv4 vrf CUST-B
Version 2
No auto-summary
Network 192.1.16.0
Redistribute BGP 12353 metric 1
!
Router BGP 12353
!
Address-family ipv4 vrf CUST-B
Redistribute rip
R6
Router RIP
Version 2
No auto-summary
Copyrights Netmetric Solutions FZC 2006-2010
Website: http://www.netmetricsolutionsfzc.com; Email: khawarb@khawarb.com
182 of 241
Network 192.1.16.0
Network 10.0.0.0
Task 7
Configure RIPv2 as the Routing Protocol between R7 and R4-vrf CUST-B.
Advertise all the routes on R7 in RIP. Advertise the VRF link in RIP on R4
under the appropriate address family. Make sure the VRF CUST-B on R1
has reachability to routes learned from R7.
R4
Router RIP
!
Address-family ipv4 vrf CUST-B
Version 2
No auto-summary
Network 192.1.47.0
Redistribute BGP 12353 metric 1
!
Router BGP 12353
!
Address-family ipv4 vrf CUST-B
Redistribute rip
R7
Router RIP
Version 2
No auto-summary
Network 192.1.47.0
Network 10.0.0.0
NOTE:
Reload the Routers without saving the configs. This will setup the
topology for the next lab.
183 of 241
R4
Task 2
Configure a VRF CUST-A with a RD value of 1:100 on R1 and R4. Use
the same extended community for your Route-target import and export.
Assign this VRF to the links that connect to C1 sites on R1 and R4.
R1
R4
ip vrf CUST-A
rd 1:100
route-target both 1:100
!
Interface F 0/0.15
Ip vrf forwarding CUST-A
Ip address 192.1.15.1 255.255.255.0
ip vrf CUST-A
rd 1:100
route-target both 1:100
!
Interface F 0/0.48
Ip vrf forwarding CUST-A
Ip address 192.1.48.4 255.255.255.0
Task 3
Configure EIGRP 100 as the Routing Protocol between R5 and R1-vrf
CUST-A. Advertise all the routes on R5 in EIGRP. Advertise the VRF link
in RIP on R1 under the appropriate address family. Make sure the VRF
CUST-A on R4 has reachability to routes learned from R5.
Copyrights Netmetric Solutions FZC 2006-2010
Website: http://www.netmetricsolutionsfzc.com; Email: khawarb@khawarb.com
184 of 241
R1
Router EIGRP 12353
!
Address-family ipv4 vrf CUST-A
Autonomous-system 100
No auto-summary
Network 192.1.15.0
Redistribute BGP 12353 metric 1 1 1 1 1
!
Router BGP 12353
!
Address-family ipv4 vrf CUST-A
Redistribute eigrp 100
R5
Router EIGRP 100
No auto-summary
Network 192.1.15.0
Network 10.0.0.0
Task 4
Configure EIGRP 100 as the Routing Protocol between R4 and R8-vrf
CUST-A. Advertise all the routes on R8 in EIGRP. Advertise the VRF link
in RIP on R4 under the appropriate address family. Make sure the VRF
CUST-A on R1 has reachability to routes learned from R8.
R4
Router EIGRP 12353
!
Address-family ipv4 vrf CUST-A
Autonomous-system 100
No auto-summary
Network 192.1.48.0
Redistribute BGP 12353 metric 1 1 1 1 1
!
Router BGP 12353
!
Address-family ipv4 vrf CUST-A
Redistribute eigrp 100
R8
Router EIGRP 100
No auto-summary
Copyrights Netmetric Solutions FZC 2006-2010
Website: http://www.netmetricsolutionsfzc.com; Email: khawarb@khawarb.com
185 of 241
Network 192.1.48.0
Network 10.0.0.0
Task 5
Configure a VRF CUST-B with a RD value of 1:200 on R1 and R4. Use
the same extended community for your Route-target import and export.
Assign this VRF to the links that connect to C2 sites on R1 and R4.
R1
R4
ip vrf CUST-B
rd 1:200
route-target both 1:200
!
Interface F 0/0.16
Ip vrf forwarding CUST-B
Ip address 192.1.16.1 255.255.255.0
ip vrf CUST-B
rd 1:200
route-target both 1:200
!
Interface F 0/0.47
Ip vrf forwarding CUST-B
Ip address 192.1.47.4 255.255.255.0
Task 6
Configure EIGRP 200 as the Routing Protocol between R6 and R1-vrf
CUST-B. Advertise all the routes on R6 in EIGRP 200. Advertise the VRF
link in RIP on R1 under the appropriate address family. Make sure the
VRF CUST-B on R4 has reachability to routes learned from R6.
R1
Router EIGRP 12353
!
Address-family ipv4 vrf CUST-B
Autonomous-system 200
No auto-summary
Network 192.1.16.0
Redistribute BGP 12353 metric 1 1 1 1 1
!
Router BGP 12353
!
Address-family ipv4 vrf CUST-B
Redistribute eigrp 200
R6
Router EIGRP 200
No auto-summary
Network 192.1.16.0
Network 10.0.0.0
Copyrights Netmetric Solutions FZC 2006-2010
Website: http://www.netmetricsolutionsfzc.com; Email: khawarb@khawarb.com
186 of 241
Task 7
Configure RIPv2 as the Routing Protocol between R7 and R4-vrf CUST-B.
Advertise all the routes on R7 in RIP. Advertise the VRF link in RIP on R4
under the appropriate address family. Make sure the VRF CUST-B on R1
has reachability to routes learned from R7.
R4
Router EIGRP 12353
!
Address-family ipv4 vrf CUST-B
Autonomous-system 200
No auto-summary
Network 192.1.47.0
Redistribute BGP 12353 metric 1 1 1 1 1
!
Router BGP 12353
!
Address-family ipv4 vrf CUST-B
Redistribute eigrp 200
R7
Router EIGRP 200
No auto-summary
Network 192.1.47.0
Network 10.0.0.0
NOTE:
Reload the Routers without saving the configs. This will setup the
topology for the next lab.
187 of 241
R4
Task 2
Configure a VRF CUST-A with a RD value of 1:100 on R1 and R4. Use
the same extended community for your Route-target import and export.
Assign this VRF to the links that connect to C1 sites on R1 and R4.
R1
R4
ip vrf CUST-A
rd 1:100
route-target both 1:100
!
Interface F 0/0.15
Ip vrf forwarding CUST-A
Ip address 192.1.15.1 255.255.255.0
ip vrf CUST-A
rd 1:100
route-target both 1:100
!
Interface F 0/0.48
Ip vrf forwarding CUST-A
Ip address 192.1.48.4 255.255.255.0
Task 3
Cust-A is running BGP in AS 100. Advertise all the routes on R5 in BGP.
Configure R1-R5 neighbor relationship in the appropriate address family.
Make sure the VRF CUST-A on R4 has reachability to routes learned
from R5.
Copyrights Netmetric Solutions FZC 2006-2010
Website: http://www.netmetricsolutionsfzc.com; Email: khawarb@khawarb.com
188 of 241
R1
Router BGP 12353
!
Address-family ipv4 vrf CUST-A
Neighbor 192.1.15.5 remote-as 100
Neighbor 192.1.15.5 activate
Neighbor 192.1.15.5 as-override
Redistribute connected
R5
Router BGP 100
Neighbor 192.1.15.1 remote-as 12353
Network 10.5.5.0 mask 255.255.255.0
Task 4
Cust-A is running BGP in AS 100. Advertise all the routes on R8 in BGP.
Configure R4-R8 neighbor relationship in the appropriate address family.
Make sure the VRF CUST-A on R1 has reachability to routes learned
from R8.
R4
Router BGP 12353
!
Address-family ipv4 vrf CUST-A
Neighbor 192.1.48.8 remote-as 100
Neighbor 192.1.48.8 activate
Neighbor 192.1.48.8 as-override
Redistribute connected
R8
Router BGP 100
Neighbor 192.1.48.4 remote-as 12353
Network 10.8.8.0 mask 255.255.255.0
Task 5
Configure a VRF CUST-B with a RD value of 1:200 on R1 and R4. Use
the same extended community for your Route-target import and export.
Assign this VRF to the links that connect to C2 sites on R1 and R4.
R1
R4
ip vrf CUST-B
rd 1:200
ip vrf CUST-B
rd 1:200
189 of 241
Task 6
Cust-B is running BGP in AS 200. Advertise all the routes on R6 in BGP.
Configure R1-R6 neighbor relationship in the appropriate address family.
Make sure the VRF CUST-A on R4 has reachability to routes learned
from R6.
R1
Router BGP 12353
!
Address-family ipv4 vrf CUST-B
Neighbor 192.1.16.6 remote-as 200
Neighbor 192.1.16.6 activate
Neighbor 192.1.16.6 as-override
Redistribute connected
R6
Router BGP 200
Neighbor 192.1.16.1 remote-as 12353
Network 10.6.6.0 mask 255.255.255.0
Task 7
Cust-B is running BGP in AS 200. Advertise all the routes on R7 in BGP.
Configure R4-R7 neighbor relationship in the appropriate address family.
Make sure the VRF CUST-A on R4 has reachability to routes learned
from R7.
R4
Router BGP 12353
!
Address-family ipv4 vrf CUST-B
Neighbor 192.1.47.7 remote-as 200
Neighbor 192.1.47.7 activate
Neighbor 192.1.47.7 as-override
Redistribute connected
R7
Copyrights Netmetric Solutions FZC 2006-2010
Website: http://www.netmetricsolutionsfzc.com; Email: khawarb@khawarb.com
190 of 241
191 of 241
R4
Task 2
Configure a VRF CUST-A with a RD value of 1:100 on R1 and R4. Use
the same extended community for your Route-target import and export.
Assign this VRF to the links that connect to C1 sites on R1 and R4.
R1
R4
ip vrf CUST-A
rd 1:100
route-target both 1:100
!
Interface F 0/0.15
Ip vrf forwarding CUST-A
Ip address 192.1.15.1 255.255.255.0
ip vrf CUST-A
rd 1:100
route-target both 1:100
!
Interface F 0/0.48
Ip vrf forwarding CUST-A
Ip address 192.1.48.4 255.255.255.0
Task 3
Configure OSPF using process ID of 2 as the Routing Protocol between
R5 and R1-vrf CUST-A. Advertise all the routes on R5 in OSPF. Advertise
the VRF link in OSPF on R1 under the appropriate address family. Make
sure the VRF CUST-A on R4 has reachability to routes learned from R5.
R1
Router ospf 2 vrf CUST-A
redistribute bgp 12353 subnets
network 192.1.15.0 0.0.0.255 area 0
Copyrights Netmetric Solutions FZC 2006-2010
Website: http://www.netmetricsolutionsfzc.com; Email: khawarb@khawarb.com
192 of 241
!
Router BGP 12353
!
Address-family ipv4 vrf CUST-A
Redistribute ospf 2
R5
Router ospf 2
Network 192.1.15.0 0.0.0.255 area 0
Network 10.0.0.0 0.255.255.255 area 0
Task 4
Configure OSPF using process ID of 2 as the Routing Protocol between
R8 and R4-vrf CUST-A. Advertise all the routes on R8 in OSPF. Advertise
the VRF link in OSPF on R4 under the appropriate address family. Make
sure the VRF CUST-A on R1 has reachability to routes learned from R8.
R4
Router ospf 2 vrf CUST-A
Network 192.1.48.0 0.0.0.255 area 0
Redistribute BGP 12353 subnets
!
Router BGP 12353
!
Address-family ipv4 vrf CUST-A
Redistribute ospf 2
R8
Router ospf 2
Network 192.1.48.0 0.0.0.255 area 0
Network 10.0.0.0 0.255.255.255 area 0
Task 5
Configure a VRF CUST-B with a RD value of 1:200 on R1 and R4. Use
the same extended community for your Route-target import and export.
Assign this VRF to the links that connect to C2 sites on R1 and R4.
R1
R4
ip vrf CUST-B
rd 1:200
route-target both 1:200
!
Interface F 0/0.16
ip vrf CUST-B
rd 1:200
route-target both 1:200
!
Interface F 0/0.47
193 of 241
Task 6
Configure OSPF using process ID of 3 as the Routing Protocol between
R6 and R1-vrf CUST-B. Advertise all the routes on R6 in OSPF. Advertise
the VRF link in OSPF on R1 under the appropriate address family. Make
sure the VRF CUST-B on R4 has reachability to routes learned from R6.
R1
Router ospf 3 vrf CUST-B
Network 192.1.16.0 0.0.0.255 area 0
Redistribute BGP 12353 subnets
!
Router BGP 12353
!
Address-family ipv4 vrf CUST-B
Redistribute ospf 3
R6
Router ospf 3
Network 192.1.16.0 0.0.0.255 area 0
Network 10.0.0.0 0.255.255.255 area 0
Task 7
Configure OSPF using process ID of 3 as the Routing Protocol between
R7 and R4-vrf CUST-B. Advertise all the routes on R7 in OSPF. Advertise
the VRF link in OSPF on R4 under the appropriate address family. Make
sure the VRF CUST-B on R1 has reachability to routes learned from R7.
R4
Router ospf 3 vrf CUST-B
Network 192.1.47.0 0.0.0.255 area 0
Redistribute BGP 12353 subnets
!
Router BGP 12353
!
Address-family ipv4 vrf CUST-B
Redistribute ospf 3
R7
Router ospf 3
Network 192.1.47.0 0.0.0.255 area 0
Copyrights Netmetric Solutions FZC 2006-2010
Website: http://www.netmetricsolutionsfzc.com; Email: khawarb@khawarb.com
194 of 241
195 of 241
R4
Interface F 0/0.67
Encapsulation dot1q 67
Ip address 192.1.67.6 255.255.255.0
!
Router OSPF 3
Network 192.1.67.0 0.0.0.255 area 0
Interface F 0/0.67
Encapsulation dot1q 67
Ip address 192.1.67.7 255.255.255.0
!
Router OSPF 3
Network 192.1.67.0 0.0.0.255 area 0
Task 2
Configure a new loopback each on R1 and R4. This newly created
loopback should be part of vrf CUST-B. Advertise this loopback under
BGP for the CUST-B vrf. The Loopback information is as follows:
R1 Loopback 67 10.67.67.1/32
R4 Loopback 67 10.67.67.4/32
R1
Interface Loopback 67
Ip vrf forwarding CUST-B
Ip address 10.67.67.1 255.255.255.255
!
Router BGP 12353
!
Address-family ipv4 vrf CUST-B
Network 10.67.67.1 mask 255.255.255.255
R4
Interface Loopback 67
Ip vrf forwarding CUST-B
Ip address 10.67.67.4 255.255.255.255
!
Router BGP 12353
!
Address-family ipv4 vrf CUST-B
Copyrights Netmetric Solutions FZC 2006-2010
Website: http://www.netmetricsolutionsfzc.com; Email: khawarb@khawarb.com
196 of 241
R4
Interface F 0/0.67
Ip ospf cost 200
Interface F 0/0.67
Ip ospf cost 200
197 of 241
198 of 241
R1
Lo 0
R2
F 0/0
Lo 0
F 0/0
S 0/0
192.1.12.0/24
Frame
192.1.23.0/24
S 0/0
192.1.34.0/24
Lo 0
F 0/0
Lo 0
F 0/0
R4
R3
R1
Interface
Loopback 0
F 0/0
IP Address
1.1.1.1
192.1.12.1
Subnet Mask
255.0. 0.0
255.255.255.0
IP Address
192.1.12.2
192.1.23.2
2.2.2.2
Subnet Mask
255.255.255.0
255.255.255.0
255.0.0.0
IP Address
192.1.23.3
192.1.34.3
3.3.3.3
Subnet Mask
255.255.255.0
255.255.255.0
255.0.0.0
R2
Interface
F 0/0
S 0/0
Loopback 0
R3
Interface
S 0/0
F 0/0
Loopback 0
199 of 241
R4
Interface
Loopback 0
F 0/0
IP Address
4.4.4.4
192.1.34.4
Subnet Mask
255.0.0.0
255.255.255.0
Task 1
Run OSPF as the Routing protocol on all routers
R1
R2
router ospf 1
network 0.0.0.0 255.255.255.255 area 0
R3
router ospf 1
network 0.0.0.0 255.255.255.255 area 0
R4
router ospf 1
network 0.0.0.0 255.255.255.255 area 0
router ospf 1
network 0.0.0.0 255.255.255.255 area 0
Task 2
Make sure that OSPF packets between R2 and R3 are not Discard
Eligible.
R2
R3
Task 3
Configure the R2 Frame Relay interface for rate limiting by configuring
the parameters CIR, Bc, Be and MINCIR, considering the following:
Your interface speed is 768000 bps. The router should send at a rate of
384000 bps. During congestion, your provider will mark any traffic in
excess of 48kbps as discard eligible, make sure your throughput changes
accordingly based upon BECNs received only and throttle down to
192000 bps upon the receipt of BECNs. Allow the Router to double the
speed if it has tokens available. Your token bucket interval is 125 ms.
Use a "map-class" to apply this feature to all PVCs.
R2
Copyrights Netmetric Solutions FZC 2006-2010
Website: http://www.netmetricsolutionsfzc.com; Email: khawarb@khawarb.com
200 of 241
201 of 241
202 of 241
SSH Traffic = 15% of the bandwidth. SSH traffic should use LLQ.
R4
Access-list 106 permit tcp any any eq 22
!
class-map SSH
match access-group 106
!
policy-map QoS
Copyrights Netmetric Solutions FZC 2006-2010
Website: http://www.netmetricsolutionsfzc.com; Email: khawarb@khawarb.com
203 of 241
class SSH
priority percent 15
204 of 241
205 of 241
1.0.0.0 0.255.255.255 eq 80
1.0.0.0 0.255.255.255 eq 443
1.0.0.0 0.255.255.255 eq 20
1.0.0.0 0.255.255.255 eq 21
206 of 241
207 of 241
13 Multicasting
208 of 241
192.1.12.0/24
R2
R1
F 0/0
S 0/0
Frame
S 0/0
F 0/0
R1
Interface
F 0/0
S 0/0
Loopback0
IP Address
10.1.1.1
192.1.12.1
1.1.1.1
Subnet Mask
255.255.255.0
255.255.255.0
255.0.0.0
IP Address
192.1.12.2
10.2.2.2
2.2.2.2
Subnet Mask
255.255.255.0
255.255.255.0
255.0.0.0
R2
Interface
S 0/0
F 0/0
Loopback0
Task 1
Configure PIM dense mode on the routers.
R1
R2
Ip multicast-routing
Ip multicast-routing
Int F 0/0
Ip pim dense-mode
Int F 0/0
Ip pim dense-mode
Int S 0/0
Ip pim dense-mode
Int S 0/0
Ip pim dense-mode
209 of 241
Task 2
Configure R1 to join the multicast group 224.11.11.11 and R2 to join the
multicast group 224.22.22.22 on the Ethernet interfaces.
R1
R2
Int F 0/0
Ip igmp join-group 224.11.11.11
Int F 0/0
Ip igmp join-group 224.22.22.22
210 of 241
192.1.12.0/24
R2
R1
F 0/0
S 0/0
S 0/0
Frame
F 0/0
R1
Interface
F 0/0
S 0/0
Loopback0
IP Address
10.1.1.1
192.1.12.1
1.1.1.1
Subnet Mask
255.255.255.0
255.255.255.0
255.0.0.0
IP Address
192.1.12.2
10.2.2.2
2.2.2.2
Subnet Mask
255.255.255.0
255.255.255.0
255.0.0.0
R2
Interface
S 0/0
F 0/0
Loopback0
Task 1
Configure RIPv2 on both routers and advertise your directly connected
interfaces.
R1
R2
Router RIP
Version 2
No auto-summary
Network 192.1.12.0
Network 1.0.0.0
Router RIP
Version 2
No auto-summary
Network 192.1.12.0
Network 2.0.0.0
211 of 241
Network 10.0.0.0
Network 10.0.0.0
Task 2
Configure R1 to be the RP for all groups. Use the most reliable interface.
R1
R2
Interface loopback0
Ip pim sparse-mode
Ip multicast-routing
Ip pim rp-address 1.1.1.1
Ip multicast-routing
Ip pim rp-address 1.1.1.1
Int F 0/0
Ip pim sparse-mode
Int F 0/0
Ip pim sparse-mode
Int S 0/0
Ip pim sparse-mode
Int S 0/0
Ip pim sparse-mode
Task 3
Have R2 F 0/0 to join the multicast group 224.12.3.53
R2
Int F 0/0
Ip igmp join-group 224.12.3.53
212 of 241
R1
Lo 0
R2
F 0/0
Lo 0
F 0/0
192.1.12.0/24
S 0/0
Frame
192.1.23.0/24
S 0/0
192.1.34.0/24
Lo 0
F 0/0
Lo 0
F 0/0
R4
R3
R1
Interface
Loopback 0
F 0/0
IP Address
1.1.1.1
192.1.12.1
Subnet Mask
255.0. 0.0
255.255.255.0
IP Address
192.1.12.2
192.1.23.2
2.2.2.2
Subnet Mask
255.255.255.0
255.255.255.0
255.0.0.0
IP Address
192.1.23.3
192.1.34.3
3.3.3.3
Subnet Mask
255.255.255.0
255.255.255.0
255.0.0.0
R2
Interface
F 0/0
S 0/0
Loopback 0
R3
Interface
S 0/0
F 0/0
Loopback 0
213 of 241
R4
Interface
Loopback 0
F 0/0
IP Address
4.4.4.4
192.1.34.4
Subnet Mask
255.0.0.0
255.255.255.0
Task 1
Configure RIP V2 on all routers and advertise all the directly connected
networks.
R1
R2
Router RIP
Version 2
No auto-summary
Network 1.0.0.0
Network 192.1.12.0
Router RIP
Version 2
No auto-summary
Network 2.0.0.0
Network 192.1.12.0
Network 192.1.23.0
R4
R3
Router RIP
Version 2
No auto-summary
Network 192.1.23.0
Network 192.1.34.0
Network 3.0.0.0
Router RIP
Version 2
No auto-summary
Network 192.1.34.0
Network 4.0.0.0
Task 2
Configure R1 to be the RP for Multicast groups 224.1.1.1 2, and R4 to
be the RP for the groups 224.4.4.1 2. These two RPs should use their
Loopback 0 interface for this purpose.
R1
R2
Ip multicast-routing
!
Ip pim rp-address 1.1.1.1 10
Ip pim rp-address 4.4.4.4 20
!
Access-list 10 permit 224.1.1.1
Access-list 10 permit 224.1.1.2
!
Access-list 20 permit 224.4.4.1
Access-list 20 permit 224.4.4.2
Ip multicast-routing
!
Ip pim rp-address 1.1.1.1 10
Ip pim rp-address 4.4.4.4 20
!
Access-list 10 permit 224.1.1.1
Access-list 10 permit 224.1.1.2
!
Access-list 20 permit 224.4.4.1
Access-list 20 permit 224.4.4.2
214 of 241
R3
R4
Ip multicast-routing
!
Ip pim rp-address 1.1.1.1 10
Ip pim rp-address 4.4.4.4 20
!
Access-list 10 permit 224.1.1.1
Access-list 10 permit 224.1.1.2
!
Access-list 20 permit 224.4.4.1
Access-list 20 permit 224.4.4.2
Ip multicast-routing
!
Ip pim rp-address 1.1.1.1 10
Ip pim rp-address 4.4.4.4 20
!
Access-list 10 permit 224.1.1.1
Access-list 10 permit 224.1.1.2
!
Access-list 20 permit 224.4.4.1
Access-list 20 permit 224.4.4.2
Task 3
Configure R1 Loopback 0 and R4 loopback to to join the following
Multicast groups:
R1 224.1.1.1, 224.1.1.2, 224.1.1.3
R4 224.4.4.1, 224.4.4.2, 224.4.4.3
R1
R4
Interface Loopback0
Ip igmp join-group 224.1.1.1
Ip igmp join-group 224.1.1.2
Ip igmp join-group 224.1.1.3
Interface Loopback0
Ip igmp join-group 224.4.4.1
Ip igmp join-group 224.4.4.2
Ip igmp join-group 224.4.4.3
Task 4
Configure PIM on the physical and loopback interfaces in such a way
that all routers have access to all the multicast groups, including the
ones that are not configured for RPs.
R1
R2
Interface F 0/0
Ip pim sparse-dense-mode
!
Interface Loopback0
Ip pim sparse-dense-mode
R3
Interface F 0/0
Ip pim sparse-dense-mode
!
Interface S 0/0
Ip pim sparse-dense-mode
R4
Interface F 0/0
Ip pim sparse-dense-mode
!
Interface S 0/0
Interface F 0/0
Ip pim sparse-dense-mode
!
Interface Loopback0
215 of 241
Ip pim sparse-dense-mode
Ip pim sparse-dense-mode
216 of 241
R1
Lo 0
R2
F 0/0
Lo 0
F 0/0
192.1.12.0/24
S 0/0
Frame
192.1.23.0/24
S 0/0
192.1.34.0/24
Lo 0
F 0/0
Lo 0
F 0/0
R4
R3
R1
Interface
Loopback 0
F 0/0
IP Address
1.1.1.1
192.1.12.1
Subnet Mask
255.0. 0.0
255.255.255.0
IP Address
192.1.12.2
192.1.23.2
2.2.2.2
Subnet Mask
255.255.255.0
255.255.255.0
255.0.0.0
IP Address
192.1.23.3
192.1.34.3
3.3.3.3
Subnet Mask
255.255.255.0
255.255.255.0
255.0.0.0
R2
Interface
F 0/0
S 0/0
Loopback 0
R3
Interface
S 0/0
F 0/0
Loopback 0
R4
Copyrights Netmetric Solutions FZC 2006-2010
Website: http://www.netmetricsolutionsfzc.com; Email: khawarb@khawarb.com
217 of 241
Interface
Loopback 0
F 0/0
IP Address
4.4.4.4
192.1.34.4
Subnet Mask
255.0.0.0
255.255.255.0
Task 1
Configure RIP V2 on all routers and advertise all the directly connected
networks.
R1
R2
Router RIP
Version 2
No auto-summary
Network 1.0.0.0
Network 192.1.12.0
Router RIP
Version 2
No auto-summary
Network 2.0.0.0
Network 192.1.12.0
Network 192.1.23.0
R4
R3
Router RIP
Version 2
No auto-summary
Network 192.1.23.0
Network 192.1.34.0
Network 3.0.0.0
Router RIP
Version 2
No auto-summary
Network 192.1.34.0
Network 4.0.0.0
Task 2
Configure IP Multicast Sparse Mode on R1 (Loopback0, F 0/0), R2 (F
0/0, S 0/0) and R3 (S 0/0, Loopback0). Configure R2 Loopback0 to be
the RP for multicast groups 224.3.3.1 and 224.3.3.2 only. Ensure that is
sends its RP-announcements every 10 seconds with a TTL of 5. Do not
configure any Static RP on any router. R1 should join the multicast
groups 224.3.3.1 and 224.3.3.2 on the F 0/0 interface. All multicast
routers should be able to ping all R3 multicast routes.
R2
Interface loopback 0
Ip pim sparse-mode
Ip multicast-routing
Ip pim autorp listener
!
access-list 1 permit 224.3.3.1
access-list 1 permit 224.3.3.2
!
Copyrights Netmetric Solutions FZC 2006-2010
Website: http://www.netmetricsolutionsfzc.com; Email: khawarb@khawarb.com
218 of 241
R3
Ip multicast-routing
Ip pim autorp listener
!
Interface loopback 0
Ip pim sparse-mode
!
Interface F 0/0
Ip pim sparse-mode
Ip igmp join-group 224.3.3.1
Ip igmp join-group 224.3.3.2
Ip multicast-routing
Ip pim autorp listener
!
Interface S0/0
Ip pim sparse-mode
!
Interface Loopback0
Ip pim sparse-mode
219 of 241
220 of 241
Super Lab
221 of 241
Super Lab I
Layer 3 Diagram
BB1
F 0/0(.100)
F 0/0.100 (.5)
R5
F0/0.56 (.5)
192.1.56.0/24 VLAN 56
F0/0.56 (.6)
R6
F0/0.46 (.6)
192.1.46.0/24 VLAN 46
F 0/0 (.4)
SW2
R4
S 0/0.134 (.4)
S 0/0.24 (.4)
VLAN 20
(.22)
R1
F 0/0 (.1)
F 0/0 (.2)
192.1.24.0/24
S 0/0 (.1)
S 0/0 (.2)
Frame Relay
R2
192.1.20.0/24
VLAN 20
192.1.134.0/24
192.1.10.0/24
VLAN 10
SW1
S 0/0 (.3)
VLAN 10
(.21)
192.1.40.0/24
VLAN 40
R3
F 0/0.40 (.3)
F 0/0.30 (.3)
VLAN 40
(.24)
SW4
BB2
VLAN 200
(.24)
F 0/0 (.200)
192.1.30.0/24 VLAN 30
192.1.200.0/24
VLAN 200
VLAN 30 (.23)
SW3
222 of 241
IP Addressing
Device
Port
IP Address
R1
F 0/0
192.1.10.1/24
S 0/0
192.1.134.1/24
Loopback 0
1.1.1.1/8
F 0/0
192.1.20.2/24
S 0/0
192.1.24.2/24
Loopback 0
2.2.2.2/8
S 0/0
192.1.134.3/24
F 0/0.30
192.1.30.3/24
F 0/0.40
192.1.40.3/24
Loopback 0
3.3.3.3/8
F 0/0
192.1.46.4/24
S 0/0.134
192.1.134.4/24
S 0/0.24
192.1.24.4/24
Loopback 0
4.4.4.4/8
F 0/0.56
192.1.56.5/24
F 0/0.100
192.1.100.5/24
Loopback 0
5.5.5.5 / 8
F 0/0.46
192.1.46.6/24
F 0/0.56
192.1.56.6/24
Loopback 0
6.6.6.6/8
SW1
VLAN 10
192.1.10.21/24
SW2
VLAN 20
192.1.20.22/24
SW3
VLAN 30
192.1.30.23/24
SW4
VLAN 40
192.1.40.24/24
VLAN 200
192.1.200.24/24
R2
R3
R4
R5
R6
223 of 241
RIP V2 Configuration
BB1
R5
OSPF Configuration
R5
Area 0
R6
R4
R6
R1
R2
Area 100
Area 10
R3
SW4
224 of 241
EIGRP Configuration
SW3
1
SW4
1
AS 200
AS 300
BB2
R3
BGP Configuration
R4
AS 100
R1
R3
R2
SW4
BB2
AS 150
AS 200
225 of 241
R4
AS 100
R1
R2
R3
Cust A
Site 1
Cust A
Site 2
SW1
SW2
226 of 241
227 of 241
228 of 241
229 of 241
230 of 241
R1 11.11.11.11
R2 22.22.22.22
R3 33.33.33.33
R4 44.44.44.44
R5 55.55.55.55
R6 66.66.66.66
SW4 24.24.24.24
231 of 241
232 of 241
Inject these routes into OSPF as well. Dont use the network
command to accomplish this task. Only send a summarized route
into OSPF.
Configure the following loopbacks on R5:
o Loopback 201: 205.1.20.1/24
o Loopback 202: 205.1.21.1/24
o Loopback 203: 205.1.22.1/24
o Loopback 204: 205.1.23.1/24
Advertise the newly created loopbacks under OSPF on R5.
These routes should be summarized on R6.
233 of 241
234 of 241
235 of 241
236 of 241
237 of 241
IP ADDRESS : 192.1.100.0/24
WINS ADDRESS : 192.1.100.5
DNS ADDRESS : 192.1.100.6
DEFAULT GATEWAY : 192.1.100.1
LEASE TIME : 6 Days
Exclude-addresses : 192.1.100.1-192.1.100.10 and
192.1.100.100
238 of 241
239 of 241
240 of 241
Interface
Loopback 100
S 0/0
Loopback 100
S 0/0.24
Loopback 100
F 0/0.56
Loopback 100
F 0/0.56
IPv6 Address
2000:2222:2222:2222::/64
2000:192:1:24::2/64
2000:4444:4444:4444::/64
2222: 192:1:24::4/64
2000:5555:5555:5555::/64
2000:192:1:56::5/64
2000:6666:6666:6666::/64
2000:192:1:56::6/64
241 of 241