You are on page 1of 31

ICND2 Course

Comprehensive CCNA Lab


Equipment Involved: R1, R2, R3 & R4, SW1, SW2, SW3-1, SW3-2, SW3-3, WS1, WS2, Internet-Router

TOPOLOGY

• 4x2811 (Routers)
• 5x2950 (Layer 2 Switches)
• 2xPC (Workstations)

These devices have all basic parameters configured for these exercises

Lab Exercise 1: Basic Device Configuration


STEP 1: Configure Basic Device Settings on R1 & SW1

• Double click on R1 to open the command line interface window


• Press <enter> to get to user exec mode
• Type en and press <enter> to go into privileged mode
• Enter global configuration mode using the configure terminal command
• Configure the hostname (R1) using the command hostname R1
• Configure a banner using the command banner motd #Welcome to the ICND2 CCNA Lab!#
• Configure console device access on R1 as follows:

o line con 0 (enters console configuration mode)


o privilege level 15 (enters directly into privileged mode without a password)
o no login (no requirement to enter credentials to access the console)

• Configure virtual terminal access on R1 as follows:

o line vty 0 15 (enters vty configuration mode)


o password cisco (sets the vty password)
o login (requires credentials to access the device)
• Configure trunking on interface FastEthernet 0/0 as follows:

o interface FastEthernet 0/0 (enters interface configuration mode)


o no shutdown (enables the interface)
o interface FastEthernet 0/0.1 (creates a logical subinterface)
o encapsulation dot1Q 1 native (sets the trunking type to 802.1q and assigns it to VLAN1 on SW1)
o ip address 192.168.1.1 255.255.255.0 (sets the IPv4 interface address for VLAN1)
o interface FastEthernet 0/0.11 (creates a logical subinterface)
o encapsulation dot1Q 11 (sets the trunking type to 802.1q and assigns it to VLAN11 on SW1)
o ip address 192.168.11.1 255.255.255.0 (sets the IPv4 interface address for VLAN11)

• Type exit twice to return to the command line


• Type copy running-config startup-config (or wr mem) to save the configuration to memory
• When finished, select File > Save on the main Packet Tracer screen in order to save your changes in the
simulator file

• Double click on SW1 to open the command line interface window


• Press <enter> to get to user exec mode
• Type en and press <enter> to go into privileged mode
• Enter global configuration mode using the configure terminal command
• Configure the hostname (SW1) using the command hostname SW1
• Configure a banner using the command banner motd #Welcome to the ICND2 CCNA Lab!#
• Configure console device access on SW1 as follows:

o line con 0 (enters console configuration mode)


o privilege level 15 (enters directly into privileged mode without a password)
o no login (no requirement to enter credentials to access the console)

• Configure virtual terminal access on SW1 as follows:

o line vty 0 15 (enters vty configuration mode)


o password cisco (sets the vty password)
o login (requires credentials to access the device)

• Create VLAN11 by entering the vlan 11 command


• Type exit to return to global configuration mode
• Perform the following configuration tasks to complete the trunking connection to R1

o interface FastEthernet 0/1 (enters interface configuration mode)


o switchport mode trunk (changes from the default of dynamic auto to 802.1q trunking)
o interface vlan 1 (enters interface configuration mode)
o no shutdown (enables the interface)
o ip address 192.168.1.11 255.255.255.0 (sets the IPv4 interface address for VLAN1)
o ip default-gateway 192.168.1.1 (sets the switch gateway to Fa0/0.1 on R1)

• Perform the following configuration tasks to enable WS1 to access VLAN 11

o interface FastEthernet 0/11 (enters interface configuration mode)


o switchport mode access (changes from the default of dynamic auto to 802.1q trunking)
o switchport access vlan 11 (assigns the port to VLAN 11 only)
o spanning-tree portfast (prevents STP processing on the port since it is attached to an endpoint)

• Type exit twice to return to the command line


• Test connectivity to the following addresses using the ping command:

o 192.168.1.1 (FastEthernet0/0.1 interface on R1)


o 192.168.11.11 (WS1 LAN interface on VLAN11)

• Type copy running-config startup-config (or wr mem) to save the configuration to memory
• When finished, select File > Save on the main Packet Tracer screen in order to save your changes in the
simulator file

STEP 2: Configure Basic Device Settings on R2 & SW2

• Double click on R2 to open the command line interface window


• Press <enter> to get to user exec mode
• Type en and press <enter> to go into privileged mode
• Enter global configuration mode using the configure terminal command
• Configure the hostname (R2) using the command hostname R2
• Configure a banner using the command banner motd #Welcome to the ICND2 CCNA Lab!#
• Configure console device access on R2 as follows:

o line con 0 (enters console configuration mode)


o privilege level 15 (enters directly into privileged mode without a password)
o no login (no requirement to enter credentials to access the console)

• Configure virtual terminal access on R2 as follows:

o line vty 0 15 (enters vty configuration mode)


o password cisco (sets the vty password)
o login (requires credentials to access the device)

• Configure trunking on interface FastEthernet 0/0 as follows:

o interface FastEthernet 0/0 (enters interface configuration mode)


o no shutdown (enables the interface)
o interface FastEthernet 0/0.1 (creates a logical subinterface)
o encapsulation dot1Q 1 native (sets the trunking type to 802.1q and assigns it to VLAN1 on SW2)
o ip address 192.168.2.2 255.255.255.0 (sets the IPv4 interface address for VLAN1)
o interface FastEthernet 0/0.22 (creates a logical subinterface)
o encapsulation dot1Q 22 (sets the trunking type to 802.1q and assigns it to VLAN22 on SW2)
o ip address 192.168.22.2 255.255.255.0 (sets the IPv4 interface address for VLAN22)

• Type exit twice to return to the command line


• Type copy running-config startup-config (or wr mem) to save the configuration to memory
• When finished, select File > Save on the main Packet Tracer screen in order to save your changes in the
simulator file
• Double click on SW2 to open the command line interface window
• Press <enter> to get to user exec mode
• Type en and press <enter> to go into privileged mode
• Enter global configuration mode using the configure terminal command
• Configure the hostname (SW2) using the command hostname SW2
• Configure a banner using the command banner motd #Welcome to the ICND2 CCNA Lab!#
• Configure console device access on SW2 as follows:

o line con 0 (enters console configuration mode)


o privilege level 15 (enters directly into privileged mode without a password)
o no login (no requirement to enter credentials to access the console)

• Configure virtual terminal access on SW2 as follows:

o line vty 0 15 (enters vty configuration mode)


o password cisco (sets the vty password)
o login (requires credentials to access the device)

• Create VLAN22 by entering the vlan 22 command


• Type exit to return to global configuration mode
• Perform the following configuration tasks to complete the trunking connection to R2

o interface FastEthernet 0/2 (enters interface configuration mode)


o switchport mode trunk (changes from the default of dynamic auto to 802.1q trunking)
o interface vlan 1 (enters interface configuration mode)
o no shutdown (enables the interface)
o ip address 192.168.2.22 255.255.255.0 (sets the IPv4 interface address for VLAN1)
o ip default-gateway 192.168.2.2 (sets the switch gateway to Fa0/0.2 on R2)

• Perform the following configuration tasks to enable WS1 to access VLAN 11

o interface FastEthernet 0/22 (enters interface configuration mode)


o switchport mode access (changes from the default of dynamic auto to 802.1q trunking)
o switchport access vlan 22 (assigns the port to VLAN 11 only)
o spanning-tree portfast (prevents STP processing on the port since it is attached to an endpoint)

• Type exit twice to return to the command line


• Test connectivity to the following addresses using the ping command:

o 192.168.2.2 (FastEthernet0/0.1 interface on R2)


o 192.168.22.22 (WS1 LAN interface on VLAN22)

• Type copy running-config startup-config (or wr mem) to save the configuration to memory
• When finished, select File > Save on the main Packet Tracer screen in order to save your changes in the
simulator file

STEP 2: Configure Basic Device Settings on R3, R4, SW3-1, SW3-2 & SW3-3

• Double click on R3 to open the command line interface window


• Press <enter> to get to user exec mode
• Type en and press <enter> to go into privileged mode

• Enter global configuration mode using the configure terminal command


• Configure the hostname (R3) using the command hostname R3
• Configure a banner using the command banner motd #Welcome to the ICND2 CCNA Lab!#
• Configure console device access on R3 as follows:

o line con 0 (enters console configuration mode)


o privilege level 15 (enters directly into privileged mode without a password)
o no login (no requirement to enter credentials to access the console)

• Configure virtual terminal access on R3 as follows:

o line vty 0 15 (enters vty configuration mode)


o password cisco (sets the vty password)
o login (requires credentials to access the device)

• Configure trunking on interface FastEthernet 0/0 as follows:

o interface FastEthernet 0/0 (enters interface configuration mode)


o no shutdown (enables the interface)
o interface FastEthernet 0/0.3 (creates a logical subinterface)
o encapsulation dot1Q 1 native (sets the trunking type to 802.1q and assigns it to VLAN1 on SW3-
1)
o ip address 192.168.3.3 255.255.255.0 (sets the IPv4 interface address for VLAN1)
o interface FastEthernet 0/0.33 (creates a logical subinterface)
o encapsulation dot1Q 33 (sets the trunking type to 802.1q and assigns it to VLAN33 on SW3-1)
o ip address 192.168.33.3 255.255.255.0 (sets the IPv4 interface address for VLAN33)

• Type exit twice to return to the command line


• Type copy running-config startup-config (or wr mem) to save the configuration to memory
• When finished, select File > Save on the main Packet Tracer screen in order to save your changes in the
simulator file
• Double click on SW3-1 to open the command line interface window
• Press <enter> to get to user exec mode
• Type en and press <enter> to go into privileged mode
• Enter global configuration mode using the configure terminal command
• Configure the hostname (SW3-1) using the command hostname SW3-1
• Configure a banner using the command banner motd #Welcome to the ICND2 CCNA Lab!#
• Configure console device access on SW3-1 as follows:

o line con 0 (enters console configuration mode)


o privilege level 15 (enters directly into privileged mode without a password)
o no login (no requirement to enter credentials to access the console)

• Configure virtual terminal access on SW3-1 as follows:

o line vty 0 15 (enters vty configuration mode)


o password cisco (sets the vty password)
o login (requires credentials to access the device)

• Create VLAN33 by entering the vlan 33 command


• Type exit to return to global configuration mode
• Perform the following configuration tasks to complete the trunking connection to R0, SW3-2 & SW3-3

o interface FastEthernet 0/3 (enters interface configuration mode, Link to R3)


o switchport mode trunk (changes from the default of dynamic auto to 802.1q trunking)
o interface FastEthernet 0/4 (enters interface configuration mode, Link to R4)
o switchport mode trunk (changes from the default of dynamic auto to 802.1q trunking)
o interface FastEthernet 0/19 (enters interface configuration mode, Link to SW3-3)
o switchport mode trunk (changes from the default of dynamic auto to 802.1q trunking)
o interface FastEthernet 0/20 (enters interface configuration mode, Link to SW3-3)
o switchport mode trunk (changes from the default of dynamic auto to 802.1q trunking)
o interface FastEthernet 0/21 (enters interface configuration mode, Link to SW3-2)
o switchport mode trunk (changes from the default of dynamic auto to 802.1q trunking)
o interface FastEthernet 0/22 (enters interface configuration mode, Link to SW3-2)
o switchport mode trunk (changes from the default of dynamic auto to 802.1q trunking)
o interface vlan 1 (enters interface configuration mode)
o no shutdown (enables the interface)
o ip address 192.168.3.31 255.255.255.0 (sets the IPv4 interface address for VLAN1)
o ip default-gateway 192.168.3.3 (sets the switch gateway to Fa0/0.1 on R3)

• Type exit twice to return to the command line


• Test connectivity to the following addresses using the ping command:

o 192.168.3.3 (FastEthernet0/0.3 interface on R3)

• Type copy running-config startup-config (or wr mem) to save the configuration to memory
• When finished, select File > Save on the main Packet Tracer screen in order to save your changes in the
simulator file

• Double click on SW3-2 to open the command line interface window


• Press <enter> to get to user exec mode
• Type en and press <enter> to go into privileged mode
• Enter global configuration mode using the configure terminal command
• Configure the hostname (SW3-2) using the command hostname SW3-2
• Configure a banner using the command banner motd #Welcome to the ICND2 CCNA Lab!#
• Configure console device access on SW3-2 as follows:

o line con 0 (enters console configuration mode)


o privilege level 15 (enters directly into privileged mode without a password)
o no login (no requirement to enter credentials to access the console)

• Configure virtual terminal access on SW3-2 as follows:

o line vty 0 15 (enters vty configuration mode)


o password cisco (sets the vty password)
o login (requires credentials to access the device)
• Type exit to return to global configuration mode
• Perform the following configuration tasks to complete the trunking connection to SW3-1 & 3-3

o interface FastEthernet 0/23 (enters interface configuration mode, Link to SW3-3)


o switchport mode trunk (changes from the default of dynamic auto to 802.1q trunking)
o interface FastEthernet 0/24 (enters interface configuration mode, Link to SW3-3)
o switchport mode trunk (changes from the default of dynamic auto to 802.1q trunking)
o interface FastEthernet 0/21 (enters interface configuration mode, Link to SW3-1)
o switchport mode trunk (changes from the default of dynamic auto to 802.1q trunking)
o interface FastEthernet 0/22 (enters interface configuration mode, Link to SW3-1)
o switchport mode trunk (changes from the default of dynamic auto to 802.1q trunking)
o interface vlan 1 (enters interface configuration mode)
o no shutdown (enables the interface)
o ip address 192.168.3.32 255.255.255.0 (sets the IPv4 interface address for VLAN1)
o ip default-gateway 192.168.3.3 (sets the switch gateway to Fa0/0.1 on R3)

• Type exit twice to return to the command line


• Test connectivity to the following addresses using the ping command:

o 192.168.3.3 (FastEthernet0/0.3interface on R3)


o 192.168.3.31 (VLAN 1 interface on SW3-1)

• Type copy running-config startup-config (or wr mem) to save the configuration to memory
When finished, select File > Save on the main Packet Tracer screen in order to save your changes in the
simulator file

• Double click on SW3-3 to open the command line interface window


• Press <enter> to get to user exec mode
• Type en and press <enter> to go into privileged mode
• Enter global configuration mode using the configure terminal command
• Configure the hostname (SW3-3) using the command hostname SW3-3
• Configure a banner using the command banner motd #Welcome to the ICND2 CCNA Lab!#
• Configure console device access on SW3-3 as follows:

o line con 0 (enters console configuration mode)


o privilege level 15 (enters directly into privileged mode without a password)
o no login (no requirement to enter credentials to access the console)

• Configure virtual terminal access on SW3-2 as follows:

o line vty 0 15 (enters vty configuration mode)


o password cisco (sets the vty password)
o login (requires credentials to access the device)

• Type exit to return to global configuration mode


• Perform the following configuration tasks to complete the trunking connection to SW3-2, SW3-3 & R4

o interface FastEthernet 0/4 (enters interface configuration mode, Link to R4)


o switchport mode trunk (changes from the default of dynamic auto to 802.1q trunking)
o interface FastEthernet 0/23 (enters interface configuration mode, Link to SW3-3)
o switchport mode trunk (changes from the default of dynamic auto to 802.1q trunking)
o interface FastEthernet 0/24 (enters interface configuration mode, Link to SW3-3)
o switchport mode trunk (changes from the default of dynamic auto to 802.1q trunking)
o interface FastEthernet 0/19 (enters interface configuration mode, Link to SW3-1)
o switchport mode trunk (changes from the default of dynamic auto to 802.1q trunking)
o interface FastEthernet 0/20 (enters interface configuration mode, Link to SW3-1)
o switchport mode trunk (changes from the default of dynamic auto to 802.1q trunking)
o interface vlan 1 (enters interface configuration mode)
o no shutdown (enables the interface)
o ip address 192.168.3.33 255.255.255.0 (sets the IPv4 interface address for VLAN1)
o ip default-gateway 192.168.3.3 (sets the switch gateway to Fa0/0.1 on R3)

• Type exit twice to return to the command line


• Test connectivity to the following addresses using the ping command:

o 192.168.3.3 (FastEthernet0/0.3interface on R3)


o 192.168.3.31 (VLAN 1 interface on SW3-1)
o 192.168.3.32 (VLAN 1 interface on SW3-2)

• Type copy running-config startup-config (or wr mem) to save the configuration to memory
When finished, select File > Save on the main Packet Tracer screen in order to save your changes in the
simulator file
• Double click on R4 to open the command line interface window
• Press <enter> to get to user exec mode
• Type en and press <enter> to go into privileged mode
• Enter global configuration mode using the configure terminal command
• Configure the hostname (R4) using the command hostname R4
• Configure a banner using the command banner motd #Welcome to the ICND2 CCNA Lab!#
• Configure console device access on R4 as follows:

o line con 0 (enters console configuration mode)


o privilege level 15 (enters directly into privileged mode without a password)
o no login (no requirement to enter credentials to access the console)

• Configure virtual terminal access on R4 as follows:

o line vty 0 15 (enters vty configuration mode)


o password cisco (sets the vty password)
o login (requires credentials to access the device)
• Configure trunking on interface FastEthernet 0/0 as follows:

o interface FastEthernet 0/0 (enters interface configuration mode)


o no shutdown (enables the interface)
o interface FastEthernet 0/0.3 (creates a logical subinterface)
o encapsulation dot1Q 1 native (sets the trunking type to 802.1q and assigns it to VLAN1 on SW3-
3)
o ip address 192.168.3.4 255.255.255.0 (sets the IPv4 interface address for VLAN1)
o interface FastEthernet 0/0.33 (creates a logical subinterface)
o encapsulation dot1Q 33 (sets the trunking type to 802.1q and assigns it to VLAN33 on SW3-1)
o ip address 192.168.33.4 255.255.255.0 (sets the IPv4 interface address for VLAN33)

• Type exit twice to return to the command line


• Type copy running-config startup-config (or wr mem) to save the configuration to memory
When finished, select File > Save on the main Packet Tracer screen in order to save your changes in the
simulator file

Lab Exercise 2: WAN Link Configuration


STEP 1: Configure Frame-Relay Device Settings on R1, R2 & R3

• Double click on R1 to open the command line interface window


• Press <enter> to get to user exec mode
• Type en and press <enter> to go into privileged mode
• Enter global configuration mode using the configure terminal command
• Enable the Serial 0/0/0 interface for frame-relay using the following commands:

o interface Serial0/0/0 (enters interface configuration mode)


o no shutdown (enables the interface)
o encapsulation frame-relay (sets the encapsulation to frame-relay)
• Issue the command do show frame-relay pvc and confirm that PVC 102 & 103 are listed

• Configure frame-relay subinterfaces as follows:

o interface Serial0/0/0.102 point-to-point


o ip address 172.16.12.1 255.255.255.0
o frame-relay interface-dlci 102

o interface Serial0/0/0.103 point-to-point


o ip address 172.16.13.1 255.255.255.0
o frame-relay interface-dlci 103

• Type exit twice to return to the command line


• Type copy running-config startup-config (or wr mem) to save the configuration to memory
When finished, select File > Save on the main Packet Tracer screen in order to save your changes in the
simulator file

• Double click on R2 to open the command line interface window


• Press <enter> to get to user exec mode
• Type en and press <enter> to go into privileged mode
• Enter global configuration mode using the configure terminal command
• Enable the Serial 0/0/0 interface for frame-relay using the following commands:

o interface Serial0/0/0 (enters interface configuration mode)


o no shutdown (enables the interface)
o encapsulation frame-relay (sets the encapsulation to frame-relay)

• Issue the command do show frame-relay pvc and confirm that PVC 201 & 203 are listed
• Configure frame-relay subinterfaces as follows:

o interface Serial0/0/0.201 point-to-point


o ip address 172.16.12.2 255.255.255.0
o frame-relay interface-dlci 201

o interface Serial0/0/0.203 point-to-point


o ip address 172.16.23.2 255.255.255.0
o frame-relay interface-dlci 203

• Issue the command ping 172.16.12.1 and confirm that connectivity to R1 is functional
• Type exit twice to return to the command line
• Type copy running-config startup-config (or wr mem) to save the configuration to memory
When finished, select File > Save on the main Packet Tracer screen in order to save your changes in the
simulator file

• Double click on R3 to open the command line interface window


• Press <enter> to get to user exec mode
• Type en and press <enter> to go into privileged mode
• Enter global configuration mode using the configure terminal command
• Enable the Serial 0/0/0 interface for frame-relay using the following commands:

o interface Serial0/0/0 (enters interface configuration mode)


o no shutdown (enables the interface)
o encapsulation frame-relay (sets the encapsulation to frame-relay)

• Issue the command do show frame-relay pvc and confirm that PVC 301 & 302 are listed
• Configure frame-relay subinterfaces as follows:

o interface Serial0/0/0.301 point-to-point


o ip address 172.16.13.3 255.255.255.0
o frame-relay interface-dlci 301

o interface Serial0/0/0.302 point-to-point


o ip address 172.16.23.3 255.255.255.0
o frame-relay interface-dlci 302

• Issue the command ping 172.16.13.1 and ping 172.16.23.2 and confirm that connectivity to R1 & R2 is
functional
• Type exit twice to return to the command line
• Type copy running-config startup-config (or wr mem) to save the configuration to memory
When finished, select File > Save on the main Packet Tracer screen in order to save your changes in the
simulator file

STEP 2: Configure a Point-to-Point Line Frame-Relay Device Settings on R1 & R3

• Double click on R1 to open the command line interface window


• Press <enter> to get to user exec mode
• Type en and press <enter> to go into privileged mode
• Enter global configuration mode using the configure terminal command
• Enable the Serial 0/1/0 interface for frame-relay using the following commands:

o interface Serial0/1/0 (enters interface configuration mode)


o no shutdown (enables the interface)
o encapsulation ppp (sets the encapsulation to ppp)
o ip address 172.17.13.1 255.255.255.0 (sets IPv4 addressing on the link)

• Type exit twice to return to the command line


• Type copy running-config startup-config (or wr mem) to save the configuration to memory
When finished, select File > Save on the main Packet Tracer screen in order to save your changes in the
simulator file

• Double click on R3 to open the command line interface window


• Press <enter> to get to user exec mode
• Type en and press <enter> to go into privileged mode
• Enter global configuration mode using the configure terminal command
• Enable the Serial 0/1/0 interface for frame-relay using the following commands:

o interface Serial0/1/0 (enters interface configuration mode)


o no shutdown (enables the interface)
o encapsulation ppp (sets the encapsulation to ppp)
o ip address 172.17.13.3 255.255.255.0 (sets IPv4 addressing on the link)

• Use the ping 172.17.13.1 command to verify connectivity back to R1


• Type exit twice to return to the command line
• Type copy running-config startup-config (or wr mem) to save the configuration to memory
• When finished, select File > Save on the main Packet Tracer screen in order to save your changes in the
simulator file

Lab Exercise 3: OSPF Configuration


STEP 1: Configure OSPF routing on R1

• Double click on R1 to open the command line interface window


• Press <enter> to get to user exec mode
• Type en and press <enter> to go into privileged mode
• Enter global configuration mode using the configure terminal command

• Create a loopback interface to serve as the OSPF Router-ID as follows:

o interface Loopback0
o ip address 10.1.1.1 255.255.255.255

• Enable the OSPF routing process on R1 using the router ospf 1 command
• Set Loopback 0 as the router-id using the command router-id 10.1.1.1
• Place the following interfaces into Area 0 using these commands:
o Loopback 0: network 10.1.1.1 0.0.0.0 area 0
o FastEthernet 0/0.1 network 192.168.1.0 0.0.0.255 area 0
o FastEthernet 0/0.11 network 192.168.11.0 0.0.0.255 area 0
o Serial 0/0/0.102 network 172.16.12.0 0.0.0.255 area 0

• Type exit twice to return to the command line


• Execute the show ip ospf interface and verify that the above interfaces are a part of the process
• Type copy running-config startup-config (or wr mem) to save the configuration to memory
• When finished, select File > Save on the main Packet Tracer screen in order to save your changes in the
simulator file

STEP 2: Configure OSPF routing on R2

• Double click on R2 to open the command line interface window


• Press <enter> to get to user exec mode
• Type en and press <enter> to go into privileged mode
• Enter global configuration mode using the configure terminal command

• Create a loopback interface to serve as the OSPF Router-ID as follows:

o interface Loopback0
o ip address 10.2.2.2 255.255.255.255

• Enable the OSPF routing process on R1 using the router ospf 1 command
• Set Loopback 0 as the router-id using the command router-id 10.2.2.2
• Place the following interfaces into Area 0 using these commands:

o Loopback 0: network 10.2.2.2 0.0.0.0 area 0


o FastEthernet 0/0.2 network 192.168.2.0 0.0.0.255 area 1
o FastEthernet 0/0.22 network 192.168.22.0 0.0.0.255 area 1
o Serial 0/0/0.201 network 172.16.12.0 0.0.0.255 area 0
o Serial 0/0/0.203 network 172.16.23.0 0.0.0.255 area 1

• R1 should come up as an OSPF neighbor


• Type exit twice to return to the command line
• Execute the show ip ospf interface and verify that the above interfaces are a part of the process
• Type copy running-config startup-config (or wr mem) to save the configuration to memory
• When finished, select File > Save on the main Packet Tracer screen in order to save your changes in the
simulator file

STEP 3: Configure OSPF routing on R3

• Double click on R3 to open the command line interface window


• Press <enter> to get to user exec mode
• Type en and press <enter> to go into privileged mode
• Enter global configuration mode using the configure terminal command

• Create a loopback interface to serve as the OSPF Router-ID as follows:

o interface Loopback0
o ip address 10.3.3.3 255.255.255.255

• Enable the OSPF routing process on R1 using the router ospf 1 command
• Set Loopback 0 as the router-id using the command router-id 10.3.3.3
• Place the following interfaces into Area 0 using these commands:

o Loopback 0: network 10.3.3.3 0.0.0.0 area 1


o FastEthernet 0/0.3 network 192.168.3.0 0.0.0.255 area 1
o FastEthernet 0/0.33 network 192.168.33.0 0.0.0.255 area 1
o Serial 0/0/0.203 network 172.16.23.0 0.0.0.255 area 1

• R2 should come up as an OSPF neighbor


• Type exit twice to return to the command line
• Execute the show ip ospf interface and verify that the above interfaces are a part of the process
• Type copy running-config startup-config (or wr mem) to save the configuration to memory
• When finished, select File > Save on the main Packet Tracer screen in order to save your changes in the
simulator file

STEP 3: Configure OSPF routing on R4

• Double click on R4 to open the command line interface window


• Press <enter> to get to user exec mode
• Type en and press <enter> to go into privileged mode
• Enter global configuration mode using the configure terminal command

• Create a loopback interface to serve as the OSPF Router-ID as follows:

o interface Loopback0
o ip address 10.4.4.4 255.255.255.255

• Configure interface FastEthernet0/1 which will supply Internet access:

o interface FastEthernet0/1
o ip address 192.168.254.99 255.255.255.0

• Create a default route pointing to the Internet router with the command ip route 0.0.0.0 0.0.0.0
192.168.254.1 (IPv4 address on the Internet Router)
• Enable the OSPF routing process on R1 using the router ospf 1 command
• Set Loopback 0 as the router-id using the command router-id 10.4.4.4
• Place the following interfaces into Area 0 using these commands:
o Loopback 0: network 10.4.4.4 0.0.0.0 area 1
o FastEthernet 0/0.3 network 192.168.3.0 0.0.0.255 area 1
o FastEthernet 0/0.33 network 192.168.33.0 0.0.0.255 area 1
o FastEthernet 0/1 network 172.16.23.0 0.0.0.255 area 1

• Redistribute the default route into OSPF using the OSPF router mode commands as follows:

o redistribute static metric-type 1 subnets


o default-information originate

• R3 should come up as an OSPF neighbor (twice) as well as the Internet Router


• Type exit twice to return to the command line
• Execute the show ip ospf interface and verify that the above interfaces are a part of the process
• Enter the show ip route ospf command to review the IPv4 routing table. Verify that the following
routes/addresses appear in the table:

o 10.1.1.1
o 10.2.2.2
o 10.3.3.3
o 192.168.1.0
o 192.168.11.0
o 192.168.2.0
o 192.168.22.0
o 172.16.12.0
o 172.16.23.0

• Test connectivity by sending ping commands to the following addresses:

o 10.1.1.1
o 10.2.2.2
o 10.3.3.3
o 192.168.1.1
o 192.168.11.1
o 192.168.2.2
o 192.168.22.2
o 172.16.12.2
o 172.16.23.2

• Type copy running-config startup-config (or wr mem) to save the configuration to memory
• When finished, select File > Save on the main Packet Tracer screen in order to save your changes in the
simulator file

Lab Exercise 4: EIGRP Configuration


STEP 1: Configure EIGRP routing on R1

• Double click on R1 to open the command line interface window


• Press <enter> to get to user exec mode
• Type en and press <enter> to go into privileged mode
• Enter global configuration mode using the configure terminal command

• Enable the EIGRP routing process on R1 using the router eigrp 100 command
• Disable automatic network summarization with the no auto-summary command
• Place the following interfaces into EIGRP using these commands:

o Serial 0/0/0.103 network 172.16.13.0 0.0.0.255


o Serial 0/1/0 network 172.17.13.0 0.0.0.255

• Type exit twice to return to the command line


• Execute the show ip eigrp interface and verify that the above interfaces are a part of the process
• Type copy running-config startup-config (or wr mem) to save the configuration to memory
• When finished, select File > Save on the main Packet Tracer screen in order to save your changes in the
simulator file

STEP 1: Configure EIGRP routing on R3

• Double click on R3 to open the command line interface window


• Press <enter> to get to user exec mode
• Type en and press <enter> to go into privileged mode
• Enter global configuration mode using the configure terminal command

• Enable the EIGRP routing process on R1 using the router eigrp 100 command
• Disable automatic network summarization with the no auto-summary command Place the following
interfaces into EIGRP using these commands:

o Serial 0/0/0.301 network 172.16.13.0 0.0.0.255


o Serial 0/1/0 network 172.17.13.0 0.0.0.255

• Neighbor relationships will come up twice between R1 and R3


• Type exit twice to return to the command line
• Execute the show ip eigrp interface and verify that the above interfaces are a part of the process
• Type copy running-config startup-config (or wr mem) to save the configuration to memory
When finished, select File > Save on the main Packet Tracer screen in order to save your changes in the
simulator file

• Double click on R1 to open the command line interface window


• Press <enter> to get to user exec mode
• Type en and press <enter> to go into privileged mode
• Verify full reachability for the lab on R1 by using the ping command to the following addresses:

o 10.1.1.1
o 10.2.2.2
o 10.3.3.3
o 10.4.4.4
o 192.168.1.1
o 192.168.11.1
o 192.168.11.11
o 192.168.2.2
o 192.168.22.2
o 192.168.22.22
o 192.168.3.3
o 192.168.3.4
o 192.168.33.3
o 192.168.33.4
o 172.16.12.1
o 172.16.12.2
o 172.16.23.2
o 172.16.23.3
o 172.16.13.1
o 172.16.13.2
o 172.17.13.1
o 172.17.13.3

Lab Exercise 5: IPv6 Configuration


STEP 1: Configure IPv6 Addressing & EIGRP Routing on R2

• Double click on R2 to open the command line interface window


• Press <enter> to get to user exec mode
• Type en and press <enter> to go into privileged mode
• Enter global configuration mode using the configure terminal command

• Enable IPv6 routing capabilities on R2 by entering the command ipv6 unicast-routing


• Configure IPv6 on Loopback 0 using the following commands:

o interface loopback0
o ipv6 enable
o ipv6 address ipv6 address 2001:2222:2222:2222::2/128

• Configure IPv6 on interface Serial0/0/0.203 using the following commands:

o interface loopback0
o ipv6 enable
o ipv6 address ipv6 address 2001:23:23:23::2/64

• Enable EIGRP for IPv6 using an AS number of 100, as follows:

o ipv6 router eigrp 100


o router-id 10.2.2.2
o no shutdown

• Enable EIGRP on the previously configured interfaces using the command ipv6 eigrp 100
• Type exit twice to return to the command line
• Execute the command show ipv6 eigrp interfaces and verify that Loopback0 and Serial0/0/0.203 are
part of the IPv6 EIGRP routing process
• Type copy running-config startup-config (or wr mem) to save the configuration to memory
• When finished, select File > Save on the main Packet Tracer screen in order to save your changes in the
simulator file

STEP 2: Configure IPv6 Addressing & EIGRP Routing on R3

• Double click on R3 to open the command line interface window


• Press <enter> to get to user exec mode
• Type en and press <enter> to go into privileged mode
• Enter global configuration mode using the configure terminal command

• Enable IPv6 routing capabilities on R2 by entering the command ipv6 unicast-routing


• Configure IPv6 on Loopback 0 using the following commands:

o interface loopback0
o ipv6 enable
o ipv6 address ipv6 address 2001:3333:3333::3/128

• Configure IPv6 on interface Serial0/0/0.302 using the following commands:

o interface loopback0
o ipv6 enable
o ipv6 address ipv6 address 2001:23:23:23::3/64

• Enable EIGRP for IPv6 using an AS number of 100, as follows:

o ipv6 router eigrp 100


o router-id 10.3.3.3
o no shutdown

• Enable EIGRP on the previously configured interfaces using the command ipv6 eigrp 100
• Type exit twice to return to the command line
• IPv6 neighbor R2 should establish a neighbor relationship
• Use the show ipv6 route command to display the contents of the IPv6 routing table (see below). The
Loopback 0 interface of R2 should appear
• Use the ping command to verify connectivity between R3 and R3
• Type copy running-config startup-config (or wr mem) to save the configuration to memory
• When finished, select File > Save on the main Packet Tracer screen in order to save your changes in the
simulator file
Lab Exercise 5: NAT/PAT Configuration
STEP 1: Configure NAT Overload/PAT on R4

• Double click on R4 to open the command line interface window


• Press <enter> to get to user exec mode
• Type en and press <enter> to go into privileged mode
• Enter global configuration mode using the configure terminal command

• Identify the traffic to be translated using a standard access-list; include all of the internal/private
addresses in use on the network, as follows:

o access-list 1 permit host 10.1.1.1


o access-list 1 permit host 10.2.2.2
o access-list 1 permit host 10.3.3.3
o access-list 1 permit host 10.4.4.4
o access-list 1 permit 192.168.1.0 0.0.0.255
o access-list 1 permit 192.168.11.0 0.0.0.255
o access-list 1 permit 192.168.2.0 0.0.0.255
o access-list 1 permit 192.168.22.0 0.0.0.255
o access-list 1 permit 192.168.3.0 0.0.0.255
o access-list 1 permit 192.168.33.0 0.0.0.255
o access-list 1 permit 172.16.12.0 0.0.0.255
o access-list 1 permit 172.16.13.0 0.0.0.255
o access-list 1 permit 172.16.23.0 0.0.0.255
o access-list 1 permit 172.17.13.0 0.0.0.255

• Identify all interfaces on R4 that will carry addressing from the ranges to be translated (inside local)
using the command ip nat inside on these interface:

o Loopback 0
o FastEthernet 0/0.3
o FastEthernet 0/0.33

• Identify the interface on R4 receiving globally routable traffic by entering the command ip nat outside
on FastEthernet 0/1
• Finally, map the inside and outside settings using the following statement: ip nat inside source list 1
interface FastEthernet 0/1 overload
• Type exit to return to the command line. Do not close the router terminal session
• Type copy running-config startup-config (or wr mem) to save the configuration to memory
• When finished, select File > Save on the main Packet Tracer screen in order to save your changes in the
simulator file

STEP 2: Verify NAT Settings by Generating Traffic from the Inside Network

• Double click on R3 to open the command line interface window


• Press <enter> to get to user exec mode
• Type en and press <enter> to go into privileged mode
• Create traffic from the 192.168.3.0 network by issuing the command ping 216.145.1.2
• Return to the R4 terminal session and enter the show ip nat translations command and note the
presence of mapping created by the ICMP packets