Lab - Configure and Verify Extended IPv4 ACLs

Topology

Addressing Table
Device Interface IP Address Subnet Mask Default Gateway

YourLastName_R1 G0/0/1 N/A N/A N/A

N/A

R1
G0/0/1.X 10.X.0.1 255.255.255.0
N/A

R1
G0/0/1.Y 10.Y.0.1 255.255.255.0
N/A

R1
G0/0/1.Z 10.Z.0.1 255.255.255.0
N/A

R1
G0/0/1.1000 N/A N/A
N/A

R1
Loopback1 100.100.100.1 255.255.255.0
YourLastName_R2 G0/0/1 10.X.0.4 255.255.255.0 N/A
YourLastName_S1 VLAN X 10.X.0.2 255.255.255.0 10.X.0.1
YourLastName_S2 VLAN X 10.X.0.3 255.255.255.0 10.X.0.1
PC-A NIC 10.Y.0.10 255.255.255.0 10.Y.0.1
PC-B NIC 10.Z.0.10 255.255.255.0 10.Z.0.1

© 2017 - 2025 Cisco and/or its affiliates. All rights reserved. Cisco Public Page 1 of 6 www.netacad.com
Lab - Configure and Verify Extended IPv4 ACLs

VLAN Table
VLAN Name Interface Assigned

X Management S2: F0/5

Y Operations S1: F0/4
Z Sales S2: F0/12
S1: F0/2-3, F0/6-24, G0/1-2
999 ParkingLot S2: F0/2-4, F0/6-11, F0/13-24, G0/1-2
1000 Native N/A
Note:
• X is the last digit of your student ID + 2.
• Y is the last digit of your student ID + 3.
• Z is the last digit of your student ID + 4.

Objectives
Part 1: Build the Network and Configure Basic Device Settings
Part 2: Configure and Verify Extended Access Control Lists

Background / Scenario
You have been tasked with configuring access control lists on small company’s network. ACLs are one of the
simplest and most direct means of controlling layer 3 traffic. R1 will be hosting an internet connection (simulated
by interface Loopback 1) and sharing the default route information to R2. After initial configuration is complete,
the company has some specific traffic security requirements that you are responsible for implementing.
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.

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

© 2017 - 2025 Cisco and/or its affiliates. All rights reserved. Cisco Public Page 2 of 6 www.netacad.com
Lab - Configure and Verify Extended IPv4 ACLs

Instructions

Part 1: Build the Network and Configure Basic Device Settings.

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 router.

Open configuration window

a. Assign a device name to the router.

b. Disable DNS lookup to prevent the router from attempting to translate incorrectly entered commands as
though they were host names.
c. Assign cisco as the privileged EXEC encrypted password.
d. Assign cisco as the console password and enable login.
e. Assign cisco as the VTY password and enable login.
f. Encrypt the plaintext passwords.
g. Create a banner that warns anyone accessing the device that unauthorized access is prohibited.
h. Save the running configuration to the startup configuration file.
Close configuration window

Step 3: Configure basic settings for each switch.

Open configuration window

a. Assign a device name to the switch.

b. Disable DNS lookup to prevent the router from attempting to translate incorrectly entered commands as
though they were host names.
c. Assign cisco as the privileged EXEC encrypted password.
d. Assign cisco as the console password and enable login.
e. Assign cisco as the VTY password and enable login.
f. Encrypt the plaintext passwords.
g. Create a banner that warns anyone accessing the device that unauthorized access is prohibited.
h. Save the running configuration to the startup configuration file.
Close configuration window

Part 2: Configure VLANs on the Switches

Step 1: Create VLANs on both switches.
Open configuration window

a. Create and name the required VLANs on each switch from the table above.
b. Configure the management interface and default gateway on each switch using the IP address information
in the Addressing Table.
c. Assign all unused ports on the switch to the Parking Lot VLAN, configure them for static access mode, and
administratively deactivate them.
Note: The interface range command is helpful to accomplish this task with as few commands as necessary.

Step 2: Assign VLANs to the correct switch interfaces.

a. Assign used ports to the appropriate VLAN (specified in the VLAN table above) and configure them for
static access mode.

© 2017 - 2025 Cisco and/or its affiliates. All rights reserved. Cisco Public Page 3 of 6 www.netacad.com
Lab - Configure and Verify Extended IPv4 ACLs

b. Issue the show vlan brief command and verify that the VLANs are assigned to the correct interfaces. Take
a full screenshot of the output
Close configuration window

Part 3: Configure Trunking

Step 1: Manually configure trunk interface F0/1.
Open configuration window

a. Change the switchport mode on interface F0/1 to force trunking. Make sure to do this on both switches.
b. As a part of the trunk configuration, set the native vlan to 1000 on both switches. You may see error
messages temporarily while the two interfaces are configured for different native VLANs.
c. As another part of trunk configuration, specify that VLANs X, Y, Z, 999, and 1000 are allowed to cross the
trunk.
d. Issue the show interfaces trunk command to verify trunking ports, the Native VLAN and allowed VLANs
across the trunk. Take a full screenshot of the output

Step 2: Manually configure S1’s trunk interface F0/5.

a. Configure S1’s interface F0/5 with the same trunk parameters as F0/1. This is the trunk to the router.
b. Save the running configuration to the startup configuration file.
c. Issue the show interfaces trunk command to verify trunking. Take a full screenshot of the output
Close configuration window

Part 4: Configure Routing

Step 1: Configure Inter-VLAN Routing on R1.
Open configuration window

a. Activate interface G0/0/1 on the router.

b. Configure sub-interfaces for each VLAN as specified in the IP addressing table. All sub-interfaces use
802.1Q encapsulation. Ensure the sub-interface for the native VLAN does not have an IP address assigned.
Include a description for each sub-interface.
c. Configure interface Loopback 1 on R1 with addressing from the table above.
d. Use the show ip interface brief command to verify the sub-interfaces are operational. Take a full
screenshot of the output

Step 2: Configure the R2 interface g0/0/1 using the address from the table and a default route
with the next hop 10.X.0.1
Close configuration window

Part 5: Configure Remote Access

Step 1: Configure all network devices for basic SSH support on R1
Open configuration window

a. Create a local user with the username YourFirstName and the encrypted password $cisco123!
b. Use YourLastName.com as the domain name.
c. Generate crypto keys using a 1024-bit modulus.
d. Configure the first five VTY lines on each device to support SSH connections only and to authenticate to
the local user database.

© 2017 - 2025 Cisco and/or its affiliates. All rights reserved. Cisco Public Page 4 of 6 www.netacad.com
Lab - Configure and Verify Extended IPv4 ACLs

Step 2: Enable secure, authenticated web services on R1.

a. Enable the HTTPS server on R1. Note: The following commands may not be supported on CPT. If you
are using CPT, you can skip this part of the lab.
R1(config)# ip http secure-server
b. Configure R1 to authenticate users attempting to connect to the web server.
R1(config)# ip http authentication local
Close configuration window

Part 6: Verify Connectivity

Step 1: Configure PC hosts.
Refer to the Addressing Table for PC host address information.

Step 2: Complete the following tests. All should be successful.

Note: You may have to disable the PC firewall for pings to be successful. Take a full screenshot of the
output for each command.

From Protocol Destination

PC-A Ping 10.Z.0.10

PC-A Ping 10.X.0.1
PC-B Ping 10.Y.0.10
PC-B Ping 10.X.0.1
PC-B Ping 100.100.100.1
PC-B HTTPS 10.X.0.1
PC-B HTTPS 100.100.100.1
PC-B SSH 10.X.0.1
PC-B SSH 100.100.100.1

Part 7: Configure and Verify Extended Access Control Lists.

When basic connectivity is verified, the company requires the following security policies to be implemented:
• Policy 1: The Sales Network is not allowed to SSH to the Management Network (but other SSH is allowed).
• Policy 2: The Sales Network is not allowed to access IP addresses in the Management network using any
web protocol (HTTP/HTTPS). The Sales Network is also not allowed to access R1 interfaces using any
web protocol. All other web traffic is allowed (note – Sales can access the Loopback 1 interface on R1).
• Policy 3: The Sales Network is not allowed to send ICMP echo-requests to the Operations or Management
Networks. ICMP echo requests to other destinations are allowed.
• Policy 4: The Operations network is not allowed to send ICMP echo-requests to the Sales network. ICMP
echo requests to other destinations are allowed.

© 2017 - 2025 Cisco and/or its affiliates. All rights reserved. Cisco Public Page 5 of 6 www.netacad.com
Lab - Configure and Verify Extended IPv4 ACLs

Step 1: Analyze the network and the security policy requirements to plan ACL implementation.
Step 2: Develop and apply extended access lists that will meet the security policy statements.
Step 3: Verify security policies are being enforced by the deployed access lists.
Run the following tests. The expected results are shown in the table: Take a full screenshot of the output for
each command.

From Protocol Destination Result

PC-A Ping 10.Z.0.10 Fail

PC-A Ping 10.X.0.1 Success
PC-B Ping 10.Y.0.10 Fail
PC-B Ping 10.X.0.1 Fail
PC-B Ping 100.100.100.1 Success
PC-B HTTPS 10.X.0.1 Fail
PC-B HTTPS 100.100.100.1 Success
PC-B SSH 10.X.0.1 Fail
PC-B SSH 100.100.100.1 Success
End of document

Reflection
1. What challenges did you encounter while setting up ACLs, and how did you overcome them?

2. How might you apply the skills learned in this lab to improve network security or manage traffic flow in a real-
world environment?

© 2017 - 2025 Cisco and/or its affiliates. All rights reserved. Cisco Public Page 6 of 6 www.netacad.com