Bai Tap
Bai Tap
VLAN Table
Objectives
Part 1: Build the Network and Configure Basic Device Settings
Part 2: Configure and verify two DHCPv4 Servers on R1
Part 3: Configure and verify a DHCP Relay on R2
Background / Scenario
The Dynamic Host Configuration Protocol (DHCP) is a network protocol that lets
network administrators manage and automate the assignment of IP addresses.
Without DHCP for IPv4, the administrator must manually assign and configure IP
addresses, preferred DNS servers, and default gateways. As the network grows in
size, this becomes an administrative problem when devices are moved from one
internal network to another.
In this scenario, the company has grown in size, and the network administrators can
no longer assign IP addresses to devices manually. Your job is to configure the R1
router to assign IPv4 addresses on two different subnets.
Note: The routers used with CCNA hands-on labs are Cisco 4221 with Cisco IOS XE
Release 16.9.4 (universalk9 image). The switches used in the labs are Cisco Catalyst
2960s with Cisco IOS Release 15.2(2) (lanbasek9 image). Other routers, switches,
and Cisco IOS versions can be used. Depending on the model and Cisco IOS version,
the commands available and the output produced might vary from what is shown in
the labs. Refer to the Router Interface Summary Table at the end of the lab for the
correct interface identifiers.
Note: Ensure that the routers and switches have been erased and have no startup
configurations. If you are unsure contact your instructor.
Instructor Note: Refer to the Instructor Lab Manual for the procedures to initialize
and reload devices
Required Resources
2 Routers (Cisco 4221 with Cisco IOS XE Release 16.9.4 universal image or
comparable)
2 Switches (Cisco 2960 with Cisco IOS Release 15.2(2) lanbasek9 image or
comparable)
2 PCs (Windows with a terminal emulation program, such as Tera Term)
Console cables to configure the Cisco IOS devices via the console ports
Ethernet cables as shown in the topology
Instructions
Part 1: Build the Network and Configure Basic Device Settings
In Part 1, you will set up the network topology and configure basic settings on the
PC hosts and switches.
Step 1: Establish an addressing scheme
Subnet the network 192.168.1.0/24 to meet the following requirements:
a. One subnet, “Subnet A”, supporting 58 hosts (the client VLAN at R1).
Subnet A:
192.168.1.0/26 (.1 -.63)
Record the first IP address in the Addressing Table for R1 G0/0/1.100. Record the
second IP address in the Address Table for S1 VLAN 200 and enter the associated
default gateway.
b. One subnet, “Subnet B”, supporting 28 hosts (the management VLAN at R1).
Subnet B:
192.168.1.64/27 (.65-.95)
Record the first IP address in the Addressing Table for R1 G0/0/1.200. Record the
second IP address in the Address Table for S1 VLAN 1 and enter the associated
default gateway.
c. One subnet, “Subnet C”, supporting 12 hosts (the client network at R2).
Subnet C:
192.168.1.96/28 (.97-.111)
Record the first IP address in the Addressing Table for R2 G0/0/1.
Step 2: Cable the network as shown in the topology.
Attach the devices as shown in the topology diagram, and cable as necessary.
Step 3: Configure basic settings for each router.
a. Assign a device name to the router.
router(config)# hostname R1
b. Disable DNS lookup to prevent the router from attempting to translate incorrectly
entered commands as though they were host names.
R1(config)# no ip domain-lookup
c. Assign class as the privileged EXEC encrypted password.
R1(config)# enable secret class
d. Assign cisco as the console password and enable login.
R1(config)# line console 0
R1(config-line)# password cisco
R1(config-line)# login
e. Assign cisco as the VTY password and enable login.
R1(config)# line vty 0 4
R1(config-line)# password cisco
R1(config-line)# login
f. Encrypt the plaintext passwords.
R1(config)# service password-encryption
g. Create a banner that warns anyone accessing the device that unauthorized
access is prohibited.
R1(config)# banner motd $ Authorized Users Only! $
h. Save the running configuration to the startup configuration file.
R1# copy running-config startup-config
i. Set the clock on the router to today’s time and date.
R1# clock set 15:30:00 27 Aug 2019
Note: Use the question mark (?) to help with the correct sequence of parameters
needed to execute this command.
Step 4: Configure Inter-VLAN Routing on R1
a. Activate interface G0/0/1 on the router.
R1(config)# interface g0/0/1
R1(config-if)# no shutdown
R1(config-if)# exit
b. Configure sub-interfaces for each VLAN as required by the IP addressing table. All
sub-interfaces use 802.1Q encapsulation and are assigned the first usable address
from the IP address pool you have calculated. Ensure the sub-interface for the
native VLAN does not have an IP address assigned. Include a description for each
sub-interface.
R1(config)# interface g0/0/1.100
R1(config-subif)# description Client Network
R1(config-subif)# encapsulation dot1q 100
R1(config-subif)# ip address 192.168.1.1 255.255.255.192
R1(config-subif)# interface g0/0/1.200
R1(config-subif)# encapsulation dot1q 200
R1(config-subif)# description Management Network
R1(config-subif)# ip address 192.168.1.65 255.255.255.224
R1(config-subif)# interface g0/0/1.1000
R1(config-subif)# encapsulation dot1q 1000 native
R1(config-subif)# description Native VLAN
c. Verify the sub-interfaces are operational.
R1# show ip interface brief
Interface IP-Address OK? Method Status Protocol
GigabitEthernet0/0/0 unassigned YES unset administratively down down
GigabitEthernet0/0/1 unassigned YES unset up up
Gi0/0/1.100 192.168.1.1 YES manual up up
Gi0/0/1.200 192.168.1.65 YES manual up up
Gi0/0/1.1000 unassigned YES unset up up
Step 5: Configure G0/0/1 on R2, then G0/0/0 and static routing for both
routers
a. Configure G0/0/1 on R2 with the first IP address of Subnet C you calculated
earlier.
R2(config)# interface g0/0/1
R2(config-if)# ip address 192.168.1.97 255.255.255.240
R2(config-if)# no shutdown
R2(config-if)# exit
b. Configure interface G0/0/0 for each router based on the IP Addressing table
above.
R1(config)# interface g0/0/0
R1(config-if)# ip address 10.0.0.1 255.255.255.252
R1(config-if)# no shutdown
g. Next, configure the second DHCPv4 Pool using the pool name R2_Client_LAN and
the calculated network, default-router and use the same domain name and lease
time from the previous DHCP pool.
R1(config)# ip dhcp excluded-address 192.168.1.97 192.168.1.101
R1(config)# ip dhcp pool R2_Client_LAN
R1(dhcp-config)# network 192.168.1.96 255.255.255.240
R1(dhcp-config)# default-router 192.168.1.97
R1(dhcp-config)# domain-name ccna-lab.com
R1(dhcp-config)# lease 2 12 30
Step 2: Save your configuration
Save the running configuration to the startup configuration file.
R1# copy running-config startup-config
Step 3: Verify the DHCPv4 Server configuration
a. Issue the command show ip dhcp pool to examine the pool details.
b. Issue the command show ip dhcp bindings to examine established DHCP
address assignments.
c. Issue the command show ip dhcp server statistics to examine DHCP
messages.
Step 4: Attempt to acquire an IP address from DHCP on PC-A
a. Open a command prompt on PC-A and issue the command ipconfig /renew.
Packet Tracer: Configure host PC-A to receive their IP addresse from a DHCP server.
b. Once the renewal process is complete, issue the command ipconfig to view the
new IP information.
c. Test connectivity by pinging R1’s G0/0/1 interface IP address.
ip default-gateway 192.168.1.65
!
ip http server
ip http secure-server
!
banner motd ^C Authorized Users Only! ^C
!
line con 0
password 7 060506324F41
login
line vty 0 4
password 7 060506324F41
login
line vty 5 15
login
!
vlan 100
name Clients
vlan 200
name Management
vlan 999
name Parking_Lot
vlan 1000
name Native
exit
!
end
Switch S2
S2# show run
Building configuration...
2001:db8:acad:2::1 /64
G0/0/0 fe80::1
2001:db8:acad:1::1/64
R1 G0/0/1 fe80::1
2001:db8:acad:2::2/64
G0/0/0 fe80::2
2001:db8:acad:3::1 /64
R2 G0/0/1 fe80::1
Device Interface IPv6 Address
Objectives
Part 1: Build the Network and Configure Basic Device Settings
Part 2: Verify SLAAC address assignment from R1
Part 3: Configure and verify a Stateless DHCPv6 Server on R1
Part 4: Configure and verify a Stateful DHCPv6 Server on R1
Part 5: Configure and verify a DHCPv6 Relay on R2
Background / Scenario
The dynamic assignment of IPv6 global unicast addresses (GUA) can be configured
the following three ways:
Stateless Address Auoconfiguration (SLACC)
Stateless Dynamic Host Configuration Protocol for IPv6 (DHCPv6)
Stateful DHCPv6
When using SLACC to assign IPv6 addresses to hosts a DHCPv6 server is not used.
Because a DHCPv6 server is not used when implementing SLACC, hosts are unable
to receive additional critical network information, including a domain name server
(DNS) address as well as a domain name.
When using Stateless DHCPv6 to assign IPv6 addresses to host, a DHCPv6 server is
used to assign the additional critical network information, however the IPv6 address
is assigned using SLACC.
When implementing Stateful DHCPv6, a DHCPv6 server assigns all network
information, including the IPv6 address.
The determination of how hosts obtain they dynamic IPv6 addressing is dependent
on flag setting contain within the router advertisement (RA) messages.
In this scenario, the company has grown in size, and the network administrators can
no longer assign IP addresses to devices manually. Your job is to configure the R2
router to assign IPv6 addresses on two different subnets connected to router R1.
Note: The routers used with CCNA hands-on labs are Cisco 4221 with Cisco IOS XE
Release 16.9.4 (universalk9 image). The switches used in the labs are Cisco Catalyst
2960s with Cisco IOS Release 15.2(2) (lanbasek9 image). Other routers, switches,
and Cisco IOS versions can be used. Depending on the model and Cisco IOS version,
the commands available and the output produced might vary from what is shown in
the labs. Refer to the Router Interface Summary Table at the end of the lab for the
correct interface identifiers.
Note: Ensure that the routers and switches have been erased and have no startup
configurations. If you are unsure contact your instructor.
Instructor Note: Refer to the Instructor Lab Manual for the procedures to initialize
and reload devices
Required Resources
2 Routers (Cisco 4221 with Cisco IOS XE Release 16.9.4 universal image or
comparable)
2 Switches (Cisco 2960 with Cisco IOS Release 15.2(2) lanbasek9 image or
comparable) – Optional
2 PCs (Windows with a terminal emulation program, such as Tera Term)
Console cables to configure the Cisco IOS devices via the console ports
Ethernet cables as shown in the topology
Instructions
Part 1: Build the Network and Configure Basic Device Settings
In Part 1, you will set up the network topology and configure basic settings on the
PC hosts and switches.
Step 1: Cable the network as shown in the topology.
Attach the devices as shown in the topology diagram, and cable as necessary.
Step 2: Configure basic settings for each switch. (Optional)
a. Assign a device name to the switch.
switch(config)# hostname S1
switch(config)# hostname S2
b. Disable DNS lookup to prevent the router from attempting to translate incorrectly
entered commands as though they were host names.
S1(config)# no ip domain-lookup
S2(config)# no ip domain-lookup
c. Assign class as the privileged EXEC encrypted password.
S1(config)# enable secret class
S2(config)# enable secret class
d. Assign cisco as the console password and enable login.
S1(config)# line console 0
S1(config-line)# password cisco
S1(config-line)# login
router(config)# hostname R2
b. Disable DNS lookup to prevent the router from attempting to translate incorrectly
entered commands as though they were host names.
R1(config)# no ip domain-lookup
R2(config)# no ip domain-lookup
c. Assign class as the privileged EXEC encrypted password.
R1(config)# enable secret class
R2(config)# enable secret class
d. Assign cisco as the console password and enable login.
R1(config)# line console 0
R1(config-line)# password cisco
R1(config-line)# login
R2(config)# exit
R2# copy running-config startup-config
Step 4: Configure interfaces and routing for both routers.
a. Configure the G0/0/0 and G0/0/1 interfaces on R1 and R2 with the IPv6 addresses
specified in the table above.
R1(config)# interface g0/0/1
R1(config-if)# ipv6 address fe80::1 link-local
R1(config-if)# ipv6 address 2001:db8:acad:1::1/64
R1(config-if)# no shutdown
R1(config)# interface g0/0/0
R1(config-if)# ipv6 address fe80::1 link-local
R1(config-if)# ipv6 address 2001:db8:acad:2::1/64
R1(config-if)# no shutdown