9 3 2 13 Lab Configuring and Verifying Extended ACLs PDF
9 3 2 13 Lab Configuring and Verifying Extended ACLs PDF
9 3 2 13 Lab Configuring and Verifying Extended ACLs PDF
Topology
2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 1 of 8
Lab Configuring and Verifying Extended ACLs
Addressing Table
Objectives
Part 1: Set Up the Topology and Initialize Devices
Part 2: Configure Devices and Verify Connectivity
Configure basic settings on PCs, routers, and switches.
Configure EIGRP routing on R1, ISP, and R3.
Part 3: Configure and Verify Extended Numbered and Named ACLs
Configure, apply, and verify a numbered extended ACL.
Configure, apply, and verify a named extended ACL.
Part 4: Modify and Verify Extended ACLs
Background / Scenario
Extended access control lists (ACLs) are extremely powerful. They offer a much greater degree of control
than standard ACLs as to the types of traffic that can be filtered, as well as where the traffic originated and
where it is going.
In this lab, you will set up filtering rules for two offices represented by R1 and R3. Management has
established some access policies between the LANs located at R1 and R3, which you must implement. The
ISP router between R1 and R3 does not have any ACLs placed on it. You would not be allowed any
administrative access to an ISP router as you can only control and manage your own equipment.
Note: The routers used with CCNA hands-on labs are Cisco 1941 Integrated Services Routers (ISRs) with
Cisco IOS Release 15.2(4)M3 (universalk9 image). The switches used are Cisco Catalyst 2960s with Cisco
IOS Release 15.0(2) (lanbasek9 image). Other routers, switches, and Cisco IOS versions can be used.
2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 2 of 8
Lab Configuring and Verifying Extended ACLs
Depending on the model and Cisco IOS version, the commands available and 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: Make sure that the routers and switches have been erased and have no startup configurations. If you
are unsure, contact your instructor.
Required Resources
3 Routers (Cisco 1941 with Cisco IOS Release 15.2(4)M3 universal image or comparable)
2 Switches (Cisco 2960 with Cisco IOS Release 15.0(2) lanbasek9 image or comparable)
2 PCs (Windows 7, Vista, or XP with terminal emulation program, such as Tera Term)
Console cables to configure the Cisco IOS devices via the console ports
Ethernet and serial cables as shown in the topology
2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 3 of 8
Lab Configuring and Verifying Extended ACLs
2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 4 of 8
Lab Configuring and Verifying Extended ACLs
Step 1: Configure a numbered extended ACL on R1 for security policy numbers 1 and 2.
You will use a numbered extended ACL on R1. What are the ranges for extended ACLs?
a. Configure the ACL on R1. Use 100 for the ACL number.
R1(config)# access-list 100 remark Allow Web & SSH Access
R1(config)# access-list 100 permit tcp host 192.168.10.3 host 10.2.2.1 eq 22
R1(config)# access-list 100 permit tcp any any eq 80
2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 5 of 8
Lab Configuring and Verifying Extended ACLs
2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 6 of 8
Lab Configuring and Verifying Extended ACLs
2) Open up a web browser on PC-C and access http://209.165.200.225 (the ISP router). It should be
successful; troubleshoot, if not.
3) From PC-C, open a web session to http://10.1.1.1 (R1). It should be successful; troubleshoot, if not.
4) From PC-C, open a web session to http://209.165.201.1 (ISP router). It should fail; troubleshoot, if
not.
5) From a PC-C command prompt, ping PC-A. What was your result and why?
Destination was unreachable because we didn't permit the IP traffic
2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 7 of 8
Lab Configuring and Verifying Extended ACLs
Reflection
1. Why is careful planning and testing of ACLs required?
to make sure we are properly allowing or blocking the correct IP address's so that we do not make the
network unsafe or unusable.
3. Why are EIGRP hello packets and routing updates not blocked by the implicit deny any access control entry
(ACE) or ACL statement of the ACLs applied to R1 and R3?
because we specifically allowed tcp packets to travel through the network.
Router Model Ethernet Interface #1 Ethernet Interface #2 Serial Interface #1 Serial Interface #2
1800 Fast Ethernet 0/0 Fast Ethernet 0/1 Serial 0/0/0 (S0/0/0) Serial 0/0/1 (S0/0/1)
(F0/0) (F0/1)
1900 Gigabit Ethernet 0/0 Gigabit Ethernet 0/1 Serial 0/0/0 (S0/0/0) Serial 0/0/1 (S0/0/1)
(G0/0) (G0/1)
2801 Fast Ethernet 0/0 Fast Ethernet 0/1 Serial 0/1/0 (S0/1/0) Serial 0/1/1 (S0/1/1)
(F0/0) (F0/1)
2811 Fast Ethernet 0/0 Fast Ethernet 0/1 Serial 0/0/0 (S0/0/0) Serial 0/0/1 (S0/0/1)
(F0/0) (F0/1)
2900 Gigabit Ethernet 0/0 Gigabit Ethernet 0/1 Serial 0/0/0 (S0/0/0) Serial 0/0/1 (S0/0/1)
(G0/0) (G0/1)
Note: To find out how the router is configured, look at the interfaces to identify the type of router and how many
interfaces the router has. There is no way to effectively list all the combinations of configurations for each router
class. This table includes identifiers for the possible combinations of Ethernet and Serial interfaces in the device.
The table does not include any other type of interface, even though a specific router may contain one. An
example of this might be an ISDN BRI interface. The string in parenthesis is the legal abbreviation that can be
used in Cisco IOS commands to represent the interface.
2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 8 of 8