CCIE Security v5-KB WB PDF
CCIE Security v5-KB WB PDF
CCIE Security v5
Authored By:
Khawar Butt
CCDE # 20110020
Table of Contents
Virtual Private Networks [VPN] Page
Module 1 – Basic VPNs
LAN-To-LAN Tunnel without NAT-T
LAN-To-LAN Tunnel with NAT-T
Point-to-Point GRE
Encrypting GRE Tunnels using IPSec
Configuring a Native IPSec Tunnel Interface using Static-
Virtual Tunnel Interface (S-VTI)
Module 2 – Advanced VPNs
Multipoint GRE (mGRE) Tunnel
Configuring DMVPN – Phase I
Configuring DMVPN – Phase II
Configuring DMVPN – Phase III
Configuring DMVPN Phase III with Dual Hub
Encrypting DMVPN Traffic using IPSec
Configuring GETVPN
Configuring GETVPN with Redundancy
Configuring VRF aware VPN
Configuring a Router as a CA Server
EZVPN – Client Mode
EZVPN – Network Extension Mode
Module 3 – Configuring VPNs using IKEv2
Site-To-Site IPSec VPN using IKEv2 – Crypto Maps
Site-To-Site IPSec VPN using IKEv2 – S-VTI
Module 4 – Configuring Flex VPNs
Site-To-Site IPSec VPN using Flex VPN
Spoke-To-Spoke IPSec VPN using Flex VPN
Server – Client IPSec Flex VPN
Configuring Router & Switch Security Features
Module 1 – Control Plane Management
Configuring Control Plane Policing
Configuring Control Plane Protection for Port Filtering
Module 2 – Configuring Router Security Features
Configuring Anti-Spoofing ACLs & the RPF Feature
Copyrights KBITS Inc 2006-2020
Website: http://www.kbits.in; Email: [email protected]
Page 2 of 404
We will free Kashmir soon. Inshallah - Dawood Ibrahim Siddiqui (CCIE #28842)
R1
F 0/0 (.1)
10.11.11.0/24
G 0/1 (.10)
R4
192.1.40.0/24
ASA G 0/2 (.10) F0/0 (.4)
10.4.4.0/24
G 0/0 (.10)
192.1.20.0/24
F 0/0 (.2)
R2
F 0/1 (.2)
192.1.23.0/24
F 0/0 (.3)
10.3.3.0/24
R3
Lab Scenario:
Open the appropriate Entries in the FW ACL to allow the tunnel to form
Initial Setup:
Configure the IP Addresses based on the Diagram. Set the Security Level
of the DMZ interface (E2) on the Firewall to 50.
o R1 : 10.1.1.0/24
o R3 : 10.3.3.0/24
o R4 : 10.4.4.0/24
R1 R2
! !
Ip route 0.0.0.0 0.0.0.0 192.1.23.2 Ip route 0.0.0.0 0.0.0.0 192.1.40.10
FW
Lab Tasks:
Task 1
Configure an IPSec Tunnel to encrypt traffic from 10.3.3.0/24 on R3 (Loopback
0) to the 10.4.4.0/24 on R4 (Loopback 0) using the following parameters for
IPSec:
ISAKMP Parameters
o Authentication : Pre-shared
o Encryption : 3DES
o Group : 2
o Hash : MD5
o Pre-Shared Key : cisco
IPSec Parameters
o Encryption : ESP-3DES
o Authentication : ESP-SHA-HMAC
R3
Group 2
Encryption 3des
!
Crypto isakmp key cisco address 192.1.40.4
!
crypto ipsec transform-set t-set esp-3des esp-sha-hmac
!
access-list 150 permit ip 10.3.3.0 0.0.0.255 10.4.4.0 0.0.0.255
!
crypto map I-MAP 10 ipsec-isakmp
set peer 192.1.40.4
set transform-set t-set
match address 150
!
Interface F 0/0
Crypto map I-MAP
R4
Task 2
Open the appropriate entries on the Firewall to allow the tunnel to form.
ASA
** As the Tunnel Endpoints are not getting translated, NAT-T will not be
used, hence the data traffic will be transmitted in a ESP packet.
Lab Scenario:
Open the appropriate Entries in the FW ACL to allow the tunnel to form
Initial Setup:
Lab Tasks:
Task 1
R1 should be seen as 192.1.20.1 on the Internet. Configure a static translation
on R1 to accomplish this.
FW
Object network R1
Host 10.11.11.1
Nat (Inside,Outside) static 192.1.20.1
Task 2
Configure an IPSec Tunnel to encrypt traffic from 10.1.1.0/24 on R1 (Loopback
0) to the 10.3.3.0/24 on R3 (Loopback 0) using the following parameters for
IPSec:
ISAKMP Parameters
o Authentication : Pre-shared
o Encryption : 3DES
o Group : 2
o Hash : MD5
o Pre-Shared Key : cisco
IPSec Parameters
o Encryption : ESP-3DES
o Authentication : ESP-SHA-HMAC
R1
Authentication pre-share
Hash md5
Group 2
Encryption 3des
!
Crypto isakmp key cisco address 192.1.23.3
!
crypto ipsec transform-set t-set esp-3des esp-sha-hmac
!
access-list 153 permit ip 10.1.1.0 0.0.0.255 10.3.3.0 0.0.0.255
!
crypto map I-MAP 10 ipsec-isakmp
set peer 192.1.23.3
set transform-set t-set
match address 153
!
Interface F 0/0
Crypto map I-MAP
R3
**As I am using the same ISAKMP & IPSec parameters that were used for my
existing tunnel, I don’t need to re-create them.
Task 3
Open the appropriate entries on the Firewall to allow the tunnel to form.
ASA
R1 R2 R3
192.1.12.0/24 192.1.23.0/24
10.1.1.0/24 10.3.3.0/24
Lab Scenario:
Initial Setup:
R1 R2
Int loopback 0
Ip add 10.3.1.1 255.255.255.0
!
Int loopback 1
Ip add 10.3.2.1 255.255.255.0
!
Int F 0/0
Ip add 192.1.23.3 255.255.255.0
No shut
!
Ip route 0.0.0.0 0.0.0.0 192.1.23.2
Lab Tasks:
Task 1
Configure a Point-to-Point GRE tunnel between R1 and R3. Use
192.168.13.0/24 as the Tunnel Network IP.
R1
Interface Tunnel 1
Ip add 192.168.13.1 255.255.255.0
Tunnel source 192.1.12.1
Tunnel destination 192.1.23.3
R3
Interface Tunnel 1
Ip add 192.168.13.3 255.255.255.0
Tunnel source 192.1.23.3
Tunnel destination 192.1.12.1
Task 2
Configure EIGRP in AS 13 to route the internal networks (Loopbacks) on the
GRE Tunnel between R1 and R3.
R1
Router EIGRP 13
No auto-summary
Network 192.168.13.0
Network 10.0.0.0
R3
Router EIGRP 13
No auto-summary
Network 192.168.13.0
Network 10.0.0.0
Lab Scenario:
Encrypt the traffic passing thru the GRE Tunnel using IPSec
Initial Setup:
Lab Tasks:
Task 1
Configure IPSec to encrypt the traffic passing thru the GRE tunnel. Make sure
the packet does not duplicate the IP addresses in the Header. Use the following
parameters for the IPSec Tunnel:
ISAKMP Parameters
o Authentication : Pre-shared
o Encryption : 3DES
o Group : 2
o Hash : MD5
o Pre-Shared Key : cisco
IPSec Parameters
o Encryption : ESP-3DES
o Authentication : ESP-SHA-HMAC
R1
Interface Tunnel 1
Tunnel protection ipsec profile IPSEC
R3
Initial Setup:
Lab Tasks:
Task 1
Convert the Existing GRE/IPSec tunnel into a Native IPSec tunnel by changing
the Tunnel mode to IPSec.
R1
Interface Tunnel 1
Tunnel mode ipsec ipv4
R3
Interface Tunnel 1
Tunnel mode ipsec ipv4
R1
10.1.1.0/24
10.1.2.0/24
F 0/0 (.1)
192.1.10.0/24
R2 F 0/0 (.5) R4
R5
192.1.20.0/24 192.1.40.0/24
10.2.1.0/24
10.2.2.0/24
F 0/0 (.2) F 0/3 (.5) F 0/0 (.4)
F 0/1 (.5) F 0/2 (.5) 10.4.1.0/24
10.4.2.0/24
192.1.30.0/24
F 0/0 (.3)
10.3.1.0/24
10.3.2.0/24
R3
Lab Scenario:
Configure a Multipoint GRE Tunnel between R1, R2, R3 & R4. R5 is your
Internet Router.
Initial Setup:
R1 R2
Interface F 0/0
Ip address 192.1.10.5 255.255.255.0
No shut
!
Interface F 0/1
Ip address 192.1.20.5 255.255.255.0
No shut
!
Interface F 0/2
Ip address 192.1.30.5 255.255.255.0
No shut
!
Interface F 0/3
Ip address 192.1.40.5 255.255.255.0
No shut
Lab Tasks:
Task 1
Configure a MultiPoint GRE tunnel between R1, R2, R3 & R4. Use
192.168.1.0/24 as the Tunnel Network IP. The NHRP mapping will be done in
the next Task. Use the following parameters for your MGRE Tunnel:
NHRP Parameters
o NHRP ID – 1234
o NHRP Authentication key – cisco
Tunnel Parameters
o Tunnel Authentication Key : 1234
R1
Interface Tunnel 1
Ip address 192.168.1.1 255.255.255.0
Ip nhrp network-id 1234
Ip nhrp authentication cisco
Tunnel source F 0/0
Tunnel mode gre multipoint
Tunnel key 1234
R2
Interface Tunnel 1
Ip address 192.168.1.2 255.255.255.0
Ip nhrp network-id 1234
Ip nhrp authentication cisco
Tunnel source F 0/0
Tunnel mode gre multipoint
Tunnel key 1234
R3
Interface Tunnel 1
Ip address 192.168.1.3 255.255.255.0
Ip nhrp network-id 1234
Ip nhrp authentication cisco
Tunnel source F 0/0
Tunnel mode gre multipoint
Tunnel key 1234
R4
Interface Tunnel 1
Ip address 192.168.1.4 255.255.255.0
Ip nhrp network-id 1234
Copyrights KBITS Inc 2006-2020
Website: http://www.kbits.in; Email: [email protected]
Page 26 of 404
We will free Kashmir soon. Inshallah - Dawood Ibrahim Siddiqui (CCIE #28842)
Task 2
Configure NHRP Mapping allowing all devices to connect to each other directly
for Unicast traffic. Configure Multicast mappings in such a way that all devices
use R1 as the routing hub.
R1
Interface Tunnel 1
Ip nhrp map 192.168.1.2 192.1.20.2
Ip nhrp map 192.168.1.3 192.1.30.3
Ip nhrp map 192.168.1.4 192.1.40.4
Ip nhrp map Multicast 192.1.20.2
Ip nhrp map Multicast 192.1.30.3
Ip nhrp map Multicast 192.1.40.4
R2
Interface Tunnel 1
Ip nhrp map 192.168.1.1 192.1.10.1
Ip nhrp map 192.168.1.3 192.1.30.3
Ip nhrp map 192.168.1.4 192.1.40.4
Ip nhrp map Multicast 192.1.10.1
R3
Interface Tunnel 1
Ip nhrp map 192.168.1.1 192.1.10.1
Ip nhrp map 192.168.1.2 192.1.20.2
Ip nhrp map 192.168.1.4 192.1.40.4
Ip nhrp map Multicast 192.1.10.1
R4
Interface Tunnel 1
Ip nhrp map 192.168.1.1 192.1.10.1
Ip nhrp map 192.168.1.2 192.1.20.2
Ip nhrp map 192.168.1.3 192.1.30.3
Ip nhrp map Multicast 192.1.10.1
Task 3
Configure EIGRP in AS 1234 to route the internal networks (Loopbacks) on the
GRE Tunnel on all the MGRE Routers. Disable Split horizon on R1 to allow it
propagate routes from the Spoke routers to the other spoke routers.
Copyrights KBITS Inc 2006-2020
Website: http://www.kbits.in; Email: [email protected]
Page 27 of 404
We will free Kashmir soon. Inshallah - Dawood Ibrahim Siddiqui (CCIE #28842)
Note: You might need to bounce the Tunnel interface to make the Routing
work. Bring up the Hub router before the Spoke Routers.
R1
Lab Scenario:
Configure DMVPN Phase I. The Spoke to Spoke traffic should use a Hub
as a hop. Use EIGRP as the Routing Protocol.
Initial Setup:
Builds on the previous lab. Disable the Tunnel Interface from the
previous lab
R1 R2
Lab Tasks:
Task 1
Configure a MultiPoint GRE tunnel between R1, R2, R3 & R4. Use
192.168.1.0/24 as the Tunnel Network IP. Tunnel:
NHRP Parameters
o NHRP ID – 1234
o NHRP Authentication key – cisco
o NHS : R1
o Routing Hub: R1 [Configure the multicast mapping to
accommodate routing protocols]
Tunnel Parameters
o Tunnel Authentication Key : 1234
R1
Interface Tunnel 1
Ip address 192.168.1.1 255.255.255.0
Ip nhrp network-id 1234
Ip nhrp authentication cisco
Ip nhrp map multicast dynamic
Tunnel source F 0/0
Tunnel mode gre multipoint
Copyrights KBITS Inc 2006-2020
Website: http://www.kbits.in; Email: [email protected]
Page 29 of 404
We will free Kashmir soon. Inshallah - Dawood Ibrahim Siddiqui (CCIE #28842)
Interface Tunnel 1
Ip address 192.168.1.2 255.255.255.0
Ip nhrp network-id 1234
Ip nhrp authentication cisco
Ip nhrp nhs 192.168.1.1
Ip nhrp map 192.168.1.1 192.1.10.1
Ip nhrp map multicast 192.1.10.1
Tunnel source F 0/0
Tunnel mode gre multipoint
Tunnel key 1234
R3
Interface Tunnel 1
Ip address 192.168.1.3 255.255.255.0
Ip nhrp network-id 1234
Ip nhrp authentication cisco
Ip nhrp nhs 192.168.1.1
Ip nhrp map 192.168.1.1 192.1.10.1
Ip nhrp map multicast 192.1.10.1
Tunnel source F 0/0
Tunnel mode gre multipoint
Tunnel key 1234
R4
Interface Tunnel 1
Ip address 192.168.1.4 255.255.255.0
Ip nhrp network-id 1234
Ip nhrp authentication cisco
Ip nhrp nhs 192.168.1.1
Ip nhrp map 192.168.1.1 192.1.10.1
Ip nhrp map multicast 192.1.10.1
Tunnel source F 0/0
Tunnel mode gre multipoint
Tunnel key 1234
Task 2
Configure EIGRP in AS 1234 to route the internal networks (Loopbacks) on the
GRE Tunnel on all the MGRE Routers. Disable Split horizon on R1 to allow it
propagate routes from the Spoke routers to the other spoke routers.
R1
Interface Tunnel 1
Note: The default behavior of EIGRP is to change the Next-hop to itself while
propagating the spoke routes to other spokes. The result is that the spokes will
use the hub route as the next hop for all spoke-to-spoke traffic. This is
DMVPN Phase I [Hub-n-Spoke forwarding]
Lab Scenario:
Configure DMVPN Phase II. The Spoke-to-Spoke traffic should use a direct
path. Use the Routing Protocol to accomplish this task.
Initial Setup:
Lab Tasks:
Task 1
Disable the Hub from changing the next-hop attribute on the hub.
R1
Interface Tunnel 1
No ip next-hop-self eigrp 1234
Note: Check the Routing table. The next-hop attribute for the Spoke-routes is
unchanged by the hub and is directly pointing to the spoke Tunnel IP. This
causes the spokes to do a NHRP resolution directly for the spoke. Although the
resolution packet will go thru the hub, the actual packet will take the direct
path. Use the traceroute command to verify this.
This is DMVPN Phase II. In this phase, the spoke-to-spoke traffic is forwarded
directly between the spokes. Phase II is accomplished by tweaking the Routing
protocol behavior.
Lab Scenario:
Initial Setup:
Change the Next-hop back to Self. All routes should again have a
next-hop pointing to the Hub [ DMVPN Phase I]
R1
Interface Tunnel 1
ip next-hop-self eigrp 1234
Lab Tasks:
Task 1
Configure NHRP Redirection on the Hub such that the Hub should push down
a dynamic mapping to the spokes for the spoke internal routes. Configure the
spokes to accept the mapping.
R1
Interface Tunnel 1
Ip nhrp redirect
R2
Interface Tunnel 1
Ip nhrp shortcut
R1
Interface Tunnel 1
Ip nhrp shortcut
R1
Interface Tunnel 1
Ip nhrp shortcut
Note: Check the Routing table. The next-hop attribute is pointing to the hun.
Do a traceroute from the R2 to R4. You will notice the first trace goes thru the
Copyrights KBITS Inc 2006-2020
Website: http://www.kbits.in; Email: [email protected]
Page 33 of 404
We will free Kashmir soon. Inshallah - Dawood Ibrahim Siddiqui (CCIE #28842)
hub. This is due to the routing table pointing towards the Hub. The hub
detects that the spokes are both connected on the same tunnel interface, hence
sends a NHRP redirect message to both of them. The NHRP redirect message
contains the mapping for the destination public IP for the internal networks.
The subsequent packets will be forwarded directly from spoke to spoke. If you
check the routing table entry, it still points to the Hub. If you check the NHRP
table, you will see an entry for the destination spoke network with the Spoke
public IP.
Lab Scenario:
Configure R1 & R2 as the NHRP Hub.
Initial Setup:
Lab Tasks:
Task 1
Disable the existing tunnel interface on R2.
R2
No Interface Tunnel 1
Task 2
Configure a Static Tunnel between R1 and R2. R2 should be configured with a
Tunnel IP address of 192.168.1.2/24 using the same Tunnel parameters as the
previous lab.
R2
Interface Tunnel 1
Ip address 192.168.1.2 255.255.255.0
Ip nhrp network-id 1234
Ip nhrp authentication cisco
Ip nhrp map 192.168.1.1 192.1.10.10
Ip nhrp map multicast 192.1.10.1
Tunnel source F 0/0
Tunnel mode gre multipoint
Tunnel key 1234
R1
Interface Tunnel1
Ip nhrp map 192.168.1.2 192.1.20.2
Ip nhrp map multicast 192.1.20.2
Task 2
Copyrights KBITS Inc 2006-2020
Website: http://www.kbits.in; Email: [email protected]
Page 35 of 404
We will free Kashmir soon. Inshallah - Dawood Ibrahim Siddiqui (CCIE #28842)
R2
Interface Tunnel 1
Ip nhrp map multicast dynamic
No ip split-horizon eigrp 1234
Ip nhrp redirect
R3
Interface Tunnel1
Ip nhrp nhs 192.168.1.2
Ip nhrp map 192.168.1.2 192.1.20.2
Ip nhrp map multicast 192.1.20.2
R4
Interface Tunnel1
Ip nhrp nhs 192.168.1.2
Ip nhrp map 192.168.1.2 192.1.20.2
Ip nhrp map multicast 192.1.20.2
Note: You should now see routes from both Routing hubs. Although, it sees 2
entries, the Data path will be direct due to Phase III.
Initial Setup:
Lab Tasks:
Task 1
Configure IPSec to encrypt the traffic passing thru the tunnel. Make sure the
packet does not duplicate the IP addresses in the Header. Use the following
parameters for the IPSec Tunnel:
ISAKMP Parameters
o Authentication : Pre-shared
o Encryption : 3DES
o Group : 2
o Hash : MD5
o Pre-Shared Key : cisco
IPSec Parameters
o Encryption : ESP-3DES
o Authentication : ESP-SHA-HMAC
R1
!
Interface Tunnel 1
Tunnel protection ipsec profile IPSEC
R2
Encryption 3des
!
Crypto isakmp key cisco address 0.0.0.0
!
crypto ipsec transform-set t-set esp-3des esp-sha-hmac
mode transport
!
crypto ipsec profile IPSEC
set transform-set t-set
!
Interface Tunnel 1
Tunnel protection ipsec profile IPSEC
R6
R1
F 0/1 (.1) F 0/0 (.6)
10.1.1.0/24
10.1.11.0/24 192.168.16.0/24
F 0/0 (.1)
192.1.168.10.0/24
R2 F 0/0 (.5) R4
R5
192.168.20.0/24 192.168.40.0/24
10.1.2.0/24
10.1.22.0/24
F 0/0 (.2) F 0/3 (.5) F 0/0 (.4)
F 0/1 (.2) F 0/1 (.5)
F 0/2 (.5) 10.1.4.0/24
10.1.44.0/24
192.168.27.0/24
F 0/0 (.3)
R7
10.1.3.0/24
10.1.33.0/24
R3
Lab Scenario:
Configure GET VPN to encrypt traffic between R1, R2, R3 & R4. R6 is your
Key Server. R1 and R6 are located at the Head quarters. R2, R3 & R4 are
remote sites connecting over a Private WAN.
Initial Setup:
R1 R2
No shut No shut
! !
Int F 0/1 Router EIGRP 100
Ip add 192.168.20.5 255.255.255.0 No auto-summary
No shut Network 192.168.16.0
!
Int F 0/2
Ip add 192.168.30.5 255.255.255.0
No shut
!
Int F 0/3
Ip add 192.168.40.5 255.255.255.0
No shut
!
Router EIGRP 100
No auto-summary
Network 192.168.10.0
Network 192.168.20.0
Network 192.168.30.0
Network 192.168.40.0
R7
Int F 0/0
Ip add 192.168.27.7 255.255.255.0
No shut
!
Router EIGRP 100
No auto-summary
Network 192.168.27.0
Lab Tasks:
Task 1
Configure R6 as the Key Server for your GET VPN to encrypt data between R1,
R2, R3 and R4. Use the following parameters for the KS.
ISAKMP Parameters
o Authentication : Pre-shared
o Encryption : 3DES
o Pre-Shared Key : cisco [Don’t use wildcard mask]
o Group : 2
IPSec Parameters
o Encryption : ESP-3DES
o Authentication : ESP-MD5-HMAC
Key Server Parameters
o Identity Number : 100
o Interesting Traffic : Any traffic on the 10.1.0.0/16 network.
o Local Address : F 0/0
o Rekey Transport : Unicast
o Rekey Key Label : GETVPN
o Rekey key Encryption : 3des
R6
Task 2
Configure R1, R2, R3 and R4 to use R6 as the Key Server. Use the Parameters
listed for the Key server to configure the Devices.
R1
Lab Scenario:
Configure a Coop server to provide fault tolerance to the Key Server.
Initial Setup:
Lab Tasks:
Task 1
Export the RSA keys on R6 so that they can be imported on the Backup server
[R7].
Export Parameters:
o File Type: PEM
o Encryption : 3DES
o Encryption Key: cisco123
o Group : 2
R6
-----------------------------------------------------------------------------------------
% Key name: GETVPN
PjSOnv50zJZWwAUA5vTRRdRffJmi5cn9yH+eTLSg1A5GilKXmT5UhKucVMzHb1ep
XMaBacqt6QiJnib/MEHQAyjrbKSg5Ayvp1hTap+Vw/reOyMJovrDcCRmt3hzynz9
Copyrights KBITS Inc 2006-2020
Website: http://www.kbits.in; Email: [email protected]
Page 46 of 404
We will free Kashmir soon. Inshallah - Dawood Ibrahim Siddiqui (CCIE #28842)
r/LXN/ykNKWeQvCr+YFglzMtptdEwQfhBA1P4eSMLCozP/r8Sd+oABMBIh4Im8kZ
Z3skBIKUT8CiNTmKDA3B/QMe2F1bcEeaA7r0CvoMQNWG9kLwhyQnnZzMjIPZ/yG8
4RrxmpWxrL3VOnAbAXxYu/fe597JKQEcp3XnURYnNHsh4dIphemlAAegPRHLCJQR
pd2an5I/Q4vAuVLaXgRRCuwe75fLUSZtk8UKAJXS3ZiOKbuABQ5QiLFS+S9Unnb2
1MLe3szgMKg6eyswYTFCXRNLauEyNhA4PMSxxLCPDeDaQr4XilB/iKMXy6ROMUhQ
OenT1u3vhjUzqxX+b/2IWYARvlY+rKahA4XkRhXwctsYB2Gs9a+dvuC+nl9JI5ys
zv++hUvrxAPlxfi/YM9tVMN91Rd8kZamIPwGFHgMk7wMwqwmdLljD2Qs+2wa8AtM
q+TvgQNUtqq9il0YHcRDZEiA5NWyNvcFFZKGn/+EqlalSX5VAKfnvdnQEY5RNcN9
BUpP7mLApWOBvAZz7vHC7/ZYaPeHtpabPaEvcqTXGc5mah6HLyPS0YhjWXs3XwRz
1czJ+cnBo6YXkvvTo4HefIfnnZHO+it8Y/chbny+/aVw1/fcdbWQ8l37XL+b6jzG
sdHa5IyBbs+kIeNELJTg9W1NLNaxEUhXjTh525CEXnU=
Task 2
Import the RSA keys from R6 on R7.
R7
zv++hUvrxAPlxfi/YM9tVMN91Rd8kZamIPwGFHgMk7wMwqwmdLljD2Qs+2wa8AtM
q+TvgQNUtqq9il0YHcRDZEiA5NWyNvcFFZKGn/+EqlalSX5VAKfnvdnQEY5RNcN9
BUpP7mLApWOBvAZz7vHC7/ZYaPeHtpabPaEvcqTXGc5mah6HLyPS0YhjWXs3XwRz
1czJ+cnBo6YXkvvTo4HefIfnnZHO+it8Y/chbny+/aVw1/fcdbWQ8l37XL+b6jzG
sdHa5IyBbs+kIeNELJTg9W1NLNaxEUhXjTh525CEXnU=
-----END RSA PRIVATE KEY-----
quit
% Key pair import succeeded.
Task 3
Configure R6 to point to R7 as the Backup redundancy server. R6 should be
the preferred KS. Set the Local Priority to 100 on R6,
R6
Task 4
Configure R7 as the Backup Key Server for your GET VPN to encrypt data
between R1, R2, R3 and R4. Use the following parameters for the KS. These are
the same ones that were specified on R6. Configure redundancy pointing to R6
as the peer. Set the local priority to 50.
ISAKMP Parameters
o Authentication : Pre-shared
o Encryption : 3DES
o Pre-Shared Key : cisco [Don’t use wildcard mask]
o Group : 2
IPSec Parameters
o Encryption : ESP-3DES
o Authentication : ESP-MD5-HMAC
Key Server Parameters
o Identity Number : 100
o Interesting Traffic : Any traffic on the 10.1.0.0/16 network.
o Local Address : F 0/0
o Rekey Transport : Unicast
o Rekey Key Label : GETVPN
o Rekey key Encryption : 3des
R7
R1
10.1.1.0/24
10.1.11.0/24
F 0/0 (.1)
192.1.168.14.0/24
F 0/0 (.4)
R4 R5 R3
10.1.4.0/24 x2 192.168.45.0/24 192.168.35.0/24
10.1.44.0/24 x2
F 0/2 (.4) F 0/1 (.5) F 0/0 (.3)
F 0/1 (.4) F 0/0 (.5)
192.168.24.0/24
F 0/0 (.2)
10.1.2.0/24
10.1.22.0/24
R2
Lab Scenario:
Initial Setup:
R1 R2
Int F 0/0
Ip add 192.168.35.3 255.255.255.0
No shut
!
ip route 0.0.0.0 0.0.0.0 192.1.35.5
R4
Int F 0/0
Ip add 192.168.45.5 255.255.255.0
No shut
!
Int F 0/1
Ip add 192.168.35.5 255.255.255.0
No shut
!
Router EIGRP 100
No auto-summary
Network 192.168.35.0
!
ip route 0.0.0.0 0.0.0.0 192.168.45.4
Lab Tasks:
Task 1
Configure R3 as the Key Server site SITE-1 and SITE-2 using the following
parameters:
SITE-1
o ISAKMP Parameters
Authentication : Pre-shared
Encryption : 3DES
Pre-Shared Key : cisco [Don’t use wildcard mask]
Group : 2
o IPSec Parameters
Encryption : ESP-3DES
Authentication : ESP-MD5-HMAC
o Key Server Parameters
Identity Number : 111
Interesting Traffic: Any traffic on the 10.1.0.0/16 network.
Local Address : F 0/0
SITE-2
o ISAKMP Parameters
Authentication : Pre-shared
Encryption : 3DES
Pre-Shared Key : cisco [Don’t use wildcard mask]
Group : 2
o IPSec Parameters
Encryption : ESP-3DES
Authentication : ESP-MD5-HMAC
o Key Server Parameters
Identity Number : 222
Interesting Traffic : Any traffic on the 10.1.0.0/16 network.
Local Address : F 0/0
R3
!
crypto ipsec transform-set TSET esp-3des esp-md5-hmac
!
access-list 150 permit ip 10.1.0.0 0.0.255.255 10.1.0.0 0.0.255.255
access-list 151 permit ip 10.1.0.0 0.0.255.255 10.1.0.0 0.0.255.255
!
crypto ipsec profile G-PROF
set transform-set TSET
!
crypto gdoi group SITE-1
identity number 111
server local
address ipv4 192.168.35.3
sa ipsec 1
profile G-PROF
match address ipv4 150
!
crypto gdoi group SITE-1
identity number 222
server local
address ipv4 192.168.35.3
sa ipsec 1
profile G-PROF
match address ipv4 150
Task 2
Configure GETVPN for SITE-1 [R1-R4] and SITE-2 [R2-R4]. Use R3 as the Key
Server. Use the Parameters listed for the Key server to configure the Devices.
R1
interface F 0/0
crypto map I-MAP
R2
R1 R2 R3
192.168.12.0/24 192.168.23.0/24
10.1.1.0/24 10.3.3.0/24
F 0/1 (.2) F 0/0 (.3)
F 0/0 (.1) F 0/0 (.2)
Lab Scenario:
Initial Setup:
o R1 : 10.1.1.1/24
o R2 : 10.2.2.2/24
o R3 : 10.3.3.3/24
R1 R2
! Int F 0/1
Router EIGRP 100 Ip add 192.168.23.2 255.255.255.0
No auto-summary No shut
Network 192.168.12.0 !
Network 10.0.0.0 Router EIGRP 100
No auto-summary
Network 192.168.12.0
Network 192.168.23.0
Network 10.0.0.0
R3
Int loopback 0
Ip add 10.3.3.3 255.255.255.0
!
Int F 0/0
Ip add 192.168.23.3 255.255.255.0
No shut
!
Router EIGRP 100
No auto-summary
Network 192.168.23.0
Network 10.0.0.0
Lab Tasks:
Task 1
Assign R2 a domain name of ABC.com. Also set the timezone and clock to the
current timezone and time. Configure R2 to be the CA Server to automatically
grant certificates using the following parameters:
R2
Ip domain-name ABC.com
!
clock timezone IST 5 30
!
clock set 12:00:00 1 May 2009
!
crypto key generate rsa general-keys label IOS-CA
!
Copyrights KBITS Inc 2006-2020
Website: http://www.kbits.in; Email: [email protected]
Page 58 of 404
We will free Kashmir soon. Inshallah - Dawood Ibrahim Siddiqui (CCIE #28842)
ip http server
!
Crypto pki server IOS-CA
database url nvram:
issuer-name CN=IOS-CA.NM.com L=ND C=IN
grant auto
no shut
*** At this point R2 has a Root Certificate that it will use to Sign and
Verify all certificates that it issues.
Task 2
Assign R1 and R3 a domain name of ABC.com. Also set the timezone and clock
to the current timezone and time.
R1
Ip domain-name ABC.com
!
clock timezone IST 5 30
!
clock set 12:00:00 1 May 2009
R3
Ip domain-name ABC.com
!
clock timezone IST 5 30
!
clock set 12:00:00 1 May 2009
Task 3
Generate 512 Bit RSA keys on R1 and R3. Configure R1 & R3 to request a
certificate from R2, the IOS-based CA Server. Use CISCO123 as the recovery
password. Disable CRL checking.
R1
Task 4
Configure an IPSec Tunnel to encrypt traffic between 10.1.1.0 and 10.3.3.0
networks. Use the following parameters for the tunnel:
R1
group 2
hash md5
encr 3des
!
crypto ipsec transform-set TSET esp-3des esp-md5-hmac
!
access-list 155 permit ip 10.3.3.0 0.0.0.255 10.1.1.0 0.0.0.255
!
crypto map I-MAP 10 ipsec-isakmp
set peer 192.168.12.1
set transform-set TSET
match address 155
!
int F 0/0
crypto map I-MAP
Task 5
Configure an IPSec Tunnel to encrypt traffic between 10.2.2.0 and 10.3.3.0
networks. Use the following parameters for the tunnel:
Task 6
As the previous task requires the CA Server to also participate in the Data
encryption, it requires to generate a separate key pair for that and request a
Identity certificate from itself. So Generate a separate RSA key pair and request
a certificate before configuring the IPSec Tunnel.
R2
! As we are using the same set of parameters for ISAKMP and IPSec that
! were used in the previous tunnel, I don’t need to redefine them.
!
access-list 156 permit ip 10.3.3.0 0.0.0.255 10.2.2.0 0.0.0.255
!
crypto map I-MAP 20 ipsec-isakmp
set peer 192.168.23.2
set transform-set TSET
match address 156
R6
F 0/0 (.6)
10.16.16.0/24
F 0/0 (.1)
R1
S 0/0 (.1)
192.1.15.0/24
R2 S 0/0 (.5) R4
192.1.25.0/24
R5 192.1.45.0/24
192.1.35.0/24
S 0/0 (.3)
R3
Lab Scenario:
Initial Setup:
o R1 : 10.1.1.1/24
o R2 : 10.2.2.2/24
o R3 : 10.3.3.3/24
o R4 : 10.4.4.4/24
R1 R2
! !
Ip route 0.0.0.0 0.0.0.0 192.1.35.5 Ip route 192.1.12.0 255.255.255.0 192.1.45.5
R5 R6
Lab Tasks:
Task 1
We will configure R1 as an EZVPN Server. Start by configuring the ISAKMP
policy parameters that will be pushed down to the clients based on the
following:
ISAKMP Parameters
o Authentication : Pre-shared
o Group : 2 (**Minimum requirement for EZVPN)
o Encryption : 3DES
R1
Task 2
Configure the IPSec Transform-set parameters based on the following:
IPSec Parameters
o Encryption : ESP-3DES
o Authentication : ESP-MD5-HMAC
R1
Task 3
Configure a Pool called EZP. This pool will be assigned to EZVPN clients. Use
192.168.11.201 thru 192.168.11.225 as the pool addresses.
R1
Task 4
We will configuring R2 as a EZVPN client. Configure a local username R2 with
a password of cisco123 for Extended Authentication. Configure an ISAKMP
Client Group called EZC with the following parameters:
Key = cisco
Dns address = 192.1.10.49
WINS address = 192.1.10.50
Pool = EZP
R1
Task 5
Configure an IPSec Profile and attach the transform-set created in one of the
previous set to it. This profile will be applied to virtual-template interface.
R1
Task 6
Enable AAA on the router. Configure Local Authentication and Network
Authorization lists that will be used later on in the ISAKMP Profiles to specify
authentication and authorization to be done based on Local Databases.
R1
Aaa new-model
!
aaa authorization network l-author local
aaa authentication login l-authen local
Task 7
Configure a Virtual-Template. Use the Tunnel type for this virtual-template
interface. Use any Interface for the acquiring the IP Address for the Template
interface. This interface should be a template for a Native Tunnel Interface.
The tunnel should encrypt using the IPSec profile that was created in one of
the previous steps
R1
Task 8
Configure an ISAKMP Profile to link the above settings. Configure Extended
Authentication and Authorization to be done based on the Local Database. R1
should respond to client requests for IP Address configurations.
R1
Task 9
Configure R2 as a EZVPN client using the following parameters:
Copyrights KBITS Inc 2006-2020
Website: http://www.kbits.in; Email: [email protected]
Page 67 of 404
We will free Kashmir soon. Inshallah - Dawood Ibrahim Siddiqui (CCIE #28842)
Mode : Client.
Peer Address : 192.1.15.1
Connect : Auto
Group Name : EZC
Key : cisco
Traffic : Network 10.2.2.0/24 (Loopback0) going outside of the S 0/0
interface.
R2
Lab Scenario:
Initial Setup:
Lab Tasks:
Task 1
R3 will be configured as a client in Network Extension mode so that the
10.16.16.0/24 network can access the 10.3.3.0/24 network. R3 should only
encrypt traffic that is destined to the 10.16.16.0/24 network. Configure an
Split-tunnel ACL on R1 to accomplish this. Use the same Virtual-template for
the D-VTI. Do not do any extended authentication for this client. Configure a
separate ISAKMP group and Profile for this.
R1
Task 2
Configure R3 as a EZVPN client using the following parameters:
Group Name : R3
Key : cisco
Traffic : Network 10.3.3.0/24 (Loopback0) going outside of the S 0/0
interface.
R3
Module 3 –
Configuring VPNS Module 3 – Configuring VPNs Using
IKEv2
Using IKEv2
R1
10.1.1.0/24
10.1.2.0/24
F 0/0 (.1)
192.1.10.0/24
R2 F 0/0 (.5) R4
R5
10.2.1.0/24 192.1.20.0/24 192.1.40.0/24
10.2.2.0/24
F 0/0 (.2) F 0/3 (.5) F 0/0 (.4)
F 0/1 (.5) F 0/2 (.5) 10.4.1.0/24
10.4.2.0/24
192.1.30.0/24
F 0/0 (.3)
10.3.1.0/24
10.3.2.0/24
R3
Lab Scenario:
Initial Setup:
R1 R2
Interface F 0/0
Ip address 192.1.10.5 255.255.255.0
No shut
!
Interface F 0/1
Ip address 192.1.20.5 255.255.255.0
No shut
!
Interface F 0/2
Ip address 192.1.30.5 255.255.255.0
No shut
!
Interface F 0/3
Ip address 192.1.40.5 255.255.255.0
No shut
Lab Tasks:
Task 1
Configure a IPSec Tunnel to encrypt traffic from 10.1.0.0/16 on R1 (Loopback
0 & Loopback 1) to the 10.2.0.0/16 on R2 (Loopback 0 & Loopback 1).
Task 2
Use the following Parameters for the Tunnel between R1 and R2:
R1
Initial Setup:
Lab Objectives:
Task 1
Configure a Native IPSec Tunnel to Connect R3 to R4. Use the following
Parameters for the Tunnel between R3 and R4:
R3
!
crypto ikev2 keyring KR_R4
peer R4
address 192.1.40.4
pre-shared local cisco3
pre-shared remote cisco4
!
crypto ikev2 profile PROF1
match identity remote address 192.1.40.4 255.255.255.255
authentication remote pre-share
authentication local pre-share
keyring local KR_R4
!
crypto ipsec transform-set ABC esp-3des esp-md5-hmac
!
crypto ipsec profile ABC
set transform-set ABC
set ikev2-profile PROF1
!
int tunnel 1
ip add 192.168.34.3 255.255.255.0
tunnel source 192.1.30.3
tunnel destination 192.1.40.4
tunnel mode ipsec ipv4
tunnel protection ipsec profile ABC
R4
Task 2
Configure EIGRP in AS 23 between R2 & R3 on the Tunnel Interface. Injecct
the Loopback Networks into EIGRP.
R2
router eigrp 34
network 10.0.0.0
network 192.168.34.0
R3
router eigrp 34
network 10.0.0.0
network 192.168.34.0
R1
10.1.1.0/24
10.1.2.0/24
F 0/0 (.1)
192.1.10.0/24
R2 F 0/0 (.6)
R6 R5
10.2.1.0/24 192.1.20.0/24 192.1.50.0/24
10.2.2.0/24 F 0/1 (.6) F 1/0 (.6)
F 0/0 (.2) F 0/0 (.5)
192.1.30.0/24 192.1.40.0/24
F 0/0 (.3)
F 0/0 (.4)
10.3.1.0/24 10.4.1.0/24
10.3.2.0/24 10.4.2.0/24
R3 R4
Lab Scenario:
Initial Setup:
Configure Default Routes on R1, R2, R3, R4 & R6 towards R5. R5 is acting
as the Internet.
R1 R2
Int loopback 0
Ip add 10.5.1.2 255.255.255.0 Interface F 0/0
! Ip address 192.1.10.6 255.255.255.0
Int loopback 0 No shut
Ip add 10.5.2.5 255.255.255.0 !
! Interface F 0/1
Int F 0/0 Ip address 192.1.20.6 255.255.255.0
Ip add 192.1.50.5 255.255.255.0 No shut
No shut !
! Interface F 0/2
Ip route 0.0.0.0 0.0.0.0 192.1.50.6 Ip address 192.1.30.6 255.255.255.0
No shut
!
Interface F 0/3
Ip address 192.1.40.6 255.255.255.0
No shut
!
Interface F 1/0
Ip addres 192.1.50.6 255.255.255.0
No shut
Lab Tasks:
Task 1
Configure a Site-to-Site Flex VPN to encrypt traffic from 10.1.X.0/24 networks
on R1 (Loopback 0 & Loopback 1) to the 10.5.X.0/24 on R5 (Loopback 0 &
Loopback 1).
Task 2
Use the following Parameters for the Tunnel between R1 and R5:
R1
int loo1
ip add 192.168.1.1 255.255.255.0
!
int virtual-template 1 type tunnel
ip unnumbered Lo11
tunnel source 192.1.10.1
tunnel mode ipsec ipv4
!
crypto ikev2 proposal PROP_1
integrity sha1
group 2
encryption 3des
!
crypto ikev2 policy POL_1
proposal PROP_1
!
crypto ikev2 keyring KR_R5
peer R5
address 192.1.50.5
pre-shared local cisco
pre-shared remote cisco
!
crypto ikev2 profile PROF_1
match identity remote address 192.1.50.5 255.255.255.255
authentication remote pre-share
authentication local pre-share
keyring local KR_R5
!
crypto ipsec transform-set ABC esp-3des esp-md5-hmac
!
crypto ipsec profile ABC
set transform-set ABC
set ikev2-profile PROF_1
!
int virtual-template 1 type tunnel
tunnel protection ipsec profile ABC
!
crypto ikev2 profile PROF_1
virtual-template 1
!
router eigrp 100
network 10.0.0.0
network 192.168.1.0
R5
Initial Setup:
Lab Objectives:
Task 1
Configure a Spoke-to-Spoke IPSec tunnel using Flex VPN to encrypt traffic
between R1, R2 & R3. Use the following parameters:
R1
!
crypto ikev2 keyring KR_ALL
peer ALL
address 0.0.0.0 0.0.0.0
pre-shared-key cisco100
!
aaa new-model
aaa authorization network default local
!
interface Virtual-Template2 type tunnel
ip unnumbered Loopback2
ip nhrp network-id 100
ip nhrp redirect
!
crypto ikev2 profile PROF_R2R3
match identity remote address 192.1.20.2 255.255.255.255
match identity remote address 192.1.30.3 255.255.255.255
authentication remote pre-share
authentication local pre-share
keyring local KR_ALL
aaa authorization group override psk list default default
virtual-template 2
!
crypto ipsec profile R2R3
set transform-set ABC
set ikev2-profile PROF_R2R3
!
router eigrp 100
redistribute static
network 192.168.2.0
!
interface Virtual-Template2 type tunnel
tunnel protection ipsec profile R2R3
no ip next-hop-self eigrp 100
R2
peer ALL
address 0.0.0.0 0.0.0.0
pre-shared-key cisco100
!
aaa new-model
aaa authorization network default local
!
crypto ikev2 authorization policy default
route set interface
!
interface Tunnel2
ip address negotiated
ip nhrp network-id 100
ip nhrp shortcut
ip nhrp redirect
tunnel source 192.1.20.2
tunnel destination 192.1.10.1
!
crypto ikev2 profile PROF_1
match identity remote address 0.0.0.0
authentication remote pre-share
authentication local pre-share
keyring local KR_ALL
aaa authorization group override psk list default default
!
crypto ipsec transform-set ABC esp-3des esp-md5-hmac
!
crypto ipsec profile ABC
set transform-set ABC
set ikev2-profile PROF_1
!
interface Tunnel2
tunnel protection ipsec profile ABC
!
router eigrp 100
no auto-summary
network 10.0.0.0
network 192.168.2.0
R3
Lab Scenario:
Configure a Server Client IPSec Flex VPN between R1 and R4. R1 is the
Server and R4 is the Client.
Initial Setup:
Lab Objectives:
Task 1
Configure a Server – Client IPSec tunnel using Flex VPN to encrypt traffic
between R1 & R4. Use the following parameters:
R1
peer Clients
address 0.0.0.0
pre-shared cisco14
!
crypto ikev2 authorization policy default
pool FLEX
route set interface
route set access-list 1
!
crypto ikev2 profile PROF_CLIENTS
match identity remote address 192.1.40.4 255.255.255.255
authentication remote pre-share
authentication local pre-share
keyring local KR_CLIENTS
aaa authorization group over psk list default default
virtual-template 3
!
Crypto ipsec profile CLIENTS
set transform-set ABC
set ikev2-profile PROF_CLIENTS
!
int virtual-template 3 type tunnel
tunnel protection ipsec profile CLIENTS
R4
aaa new-model
aaa authorization network default local
!
access-list 1 permit 10.4.1.0 0.0.0.255
access-list 1 permit 10.4.2.0 0.0.0.255
!
crypto ikev2 proposal PROP_1
integrity sha1
group 2
encryption 3des
!
crypto ikev2 policy POL_1
proposal PROP_1
!
crypto ikev2 keyring KR_R1
peer R1
address 192.1.10.1
pre-shared cisco14
!
crypto ikev2 authorization policy default
Module 1 – Control
Plane Management
Module 1 – Control Plane Management
R1 SW1 SW2
F 0/0 (.4)
F 0/0 (.2)
R4
R2
F 0/1 (.2)
192.1.23.0/24 VLAN 23
F 0/0 (.3)
R3
Lab Scenario:
Configure the Router for Control Plane Policing for Telnet Traffic.
Initial Setup:
Configure the IP Addresses on the Routers & SW based on the Diagram.
Configure the 2 switches to trunk using dot1q. Configure SW1 as the VTP
Server in domain cisco. Configure SW2 as the VTP Client in domain cisco.
Int F 0/0
Ip add 192.1.10.5 255.255.255.0
No shut
!
Router eigrp 100
No auto-summary
Network 192.1.10.0
SW1
Lab Tasks:
Task 1
R3 has been configured to allow telnet access for management purposes. Using
Control Plane Policing, control the rate of Telnet traffic to 64000 bps.
R3
Initial Setup:
Lab Task:
Task 1
Configure R3 with a port-filter to drop all traffic destined to a custom udp port
11223. It should also drop traffic to all unused port numbers.
R3
Module 2 –
Configuring Router Module 2 – Configuring Router
Security Features
Security Features
R1 SW1 SW2
F 0/0 (.4)
F 0/0 (.2)
R4
R2
F 0/1 (.2)
192.1.23.0/24 VLAN 23
F 0/0 (.3)
R3
Lab Scenario:
R2 should also implement strict RPF to verify that the source is coming in
from the valid interface.
Initial Setup:
Lab Task:
Task 1
Block any RFC 1918 address coming into R2 from R3.
R2
Task 2
Use Strict RPF to prevent IP spoofing using network addresses from the
internal networks. The route could use the default gateway to check for the
source address. Also make sure all packets that are failing the RPF check get
logged.
R2
Lab Scenario:
Configure a Router to acquire the time from a remote Time source using
NTP.
Initial Setup:
Lab Task:
Lab Objectives:
Task 1
Configure R1 as a NTP Master with a stratum of 2. R1 is in New Delhi (+5:30).
Configure the appropriate Time Zone setting. Set the Router clock based on the
current date and time.
R1
Task 2
Configure R2 to receive its clock from R1. R2 is in Dubai (+4). Configure R2
such that it automatically adjusts the clock based on the time zone
R2
Task 3
Configure R3 to receive its clock from R2. R3 is located in Rome (+1). Do not
use the NTP Server command to receive the clock. Do not configure any
commands under the interface to accomplish this task.
R3
Task 4
Authenticate all NTP communications using a key id of 123. The Key string
should be ccie12353.
R1
Lab Scenario:
Initial Setup:
Lab Task:
Task 1
There is a SNMP Management Station located at 192.1.10.50. Configure R2 to
send SNMP Traps for ISAKMP and IPSec only to this management station. It is
using a community name of PublIc.
R2
Task 2
Configure R2 to send traps to the previously configured SNMP Management
station when an ISAKMP tunnel comes up or goes down.
R2
Task 3
Also configure R2 to send traps to the SNMP Management station when an
IPSec tunnel comes up or goes down.
R2
Lab Scenario:
Initial Setup:
Lab Task:
Task 1
Disable R4 from being a DHCP Server.
R4
No service dhcp
Task 2
R2 is sending unreachable messages if a packet is received that it cannot
route. It should not send the icmp unreachable messages. Disable it on the
Interface facing R3.
R2
Interface F 0/1
No ip unreachables
Task 3
R2 is receiving a lot of packets with the IP option fields set. You deem these
packets as attack packets. Drop any packet that has the IP option field set.
R2
Ip options drop
Task 4
R3 is receiving a lot of packets with the IP option fields set. You deem these
packets as attack packets. Drop any packet that has the IP option field set.
Allow traceroute, record-route & timestamp to work on R3.
R3
Task 5
R1 is receiving a lot of packets with the source-route ip option used to control
return paths. Disable this on R1.
R1
No ip source-route
Lab Scenario:
Make sure the passwords do not get displayed when viewing the logged
commands.
Initial Setup:
Lab Task:
Task 1
Configure R1 to create Archives of your configuration files. Store them on a tftp
server located at 192.1.10.100. The name of the archive should be
MyConfigFiles.
R1
archive
path tftp://10.1.1.1/MyConfigFiles
Task 2
R1 should also log changes to the running config. Make sure the password are
suppressed when displaying logged commands.
R1
archive
log config
logging enable
hidekeys
Module 3 –
Configuring Switch
Module 3 – Configuring Switch
Security Features Security Features
R1 SW1 SW2
F 0/0 (.4)
F 0/0 (.2)
R4
R2
F 0/1 (.2)
192.1.23.0/24 VLAN 23
F 0/0 (.3)
R3
Lab Scenario:
Initial Setup:
Lab Task:
Task 1
Configure SW1 such that only R1 F0/0 and R2 F0/0 can connect to Ports F
0/1 and F 0/2 respectively. If another port tries to connect to these ports they
should be shudown.
SW1
Interface F 0/1
Switchport port-security
Switchport port-security mac xxxx.xxxx.xxxx
!
Interface F 0/2
Switchport port-security
Switchport port-security mac xxxx.xxxx.xxxx
Task 2
Configure Port security on Ports F 0/3 – 6. You would like to learn the MAC
address dynamically and copy it to the running-configuration file.
SW1
Task 3
Configure F 0/15 in VLAN 10 on SW1. Enable Port security for this ports such
that 5 MAC address can be connected to it. Configure 2 MAC Address (0001-
1010-AB12 and 0001-10101-AB13) statically. The rest of the MAC addresses
can be learned dynamically.
SW1
Interface F 0/15
Switchport mode access
Switchport access vlan 10
Switchport port-security
Switchport port-security max 5
Switchport port-security mac xxxx.xxxx.xxxx
Switchport port-security mac xxxx.xxxx.xxxx
Switchport port-security mac sticky
Task 4
Configure the Switch such that it tries to bring up the Port-security error
disabled port automatically after 4 minutes.
SW1
Lab Scenario:
Initial Setup:
Lab Task:
Task 1
All the SALES users will be in the SALES VLAN (100). Create this VLAN. Assign
ports F 0/7 – 10 on SW2 to this VLAN.
SW1
VLAN 100
SW2
Task 2
The DHCP server resides on the F 0/18 on SW2. Assign this port to the SALES
VLAN.
SW2
Interface F 0/18
Switchport mode access
Switchport access vlan 100
Task 3
Make sure the switch only allows DHCP replies from port F 0/18 on Switch2.
SW2
Ip dhcp snooping
Ip dhcp snooping vlan 100
!
Interface F 0/18
Ip dhcp snooping trust
Lab Scenario:
Configuring the Switch for Static ARP Inspection to prevent ARP Spoofing
attacks.
Initial Setup:
Lab Task:
Task 1
You have a server VLAN (200). This VLAN contains 3 Servers connected to
ports F 0/11, F 0/12 and F0/13 on SW2. Create this VLAN. Assign ports F
0/11 – 13 on SW2 to this VLAN.
SW1
VLAN 200
SW2
Task 2
This VLAN is under the ARP Spoofing attack. Make sure that ARP Packets are
inspected. The verification should be done based on the following table:
SW2
Lab Scenario:
Initial Setup:
Lab Task:
Task 1
Configure SW2 such that it intercepts all packets received on untrusted ports
in VLAN 100. It should verify valid IP-MAC mappings against the DHCP
Snooping Database. This database was created by enabling DHCP Snooping for
VLAN 100 in a previous lab.
SW2
Lab Scenario:
Initial Setup:
Lab Task:
Task 1
There is a Server connected to port F 0/7 on SW2. Turn on the IP Source
Guard feature on SW2 such that only this server connects up to F 0/7. This
Server has a MAC address of 0001.1010.1020 and an IP address of 192.1.50.7.
SW2
Lab Scenario:
Initial Setup:
Lab Task:
Task 1
Configure the following policy for VLAN 100 on SW1.
Hosts should not be able to use the IGMP and the ICMP protocols.
Task 2
Use a VLAN ACL for this task.
SW1
action forward
!
vlan filter VLAN100 vlan-list 100
on
Module 4 –
Configuring IPv6
Module 4 – Configuring IPv6
Loppback 0 R1 R2 Loppback 0
FD00:1:1:1::1/64 F 0/0 F 0/0 FD00:2.2.2::2/64
FD00:192:1:12::/64
S 0/0
FD00:192:1:23::/64
Lo 0 F 0/0 F 0/0 Lo 0
R4 R3
Lab Scenario:
Initial Setup:
None.
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 – FD00:192:1:12::1 /64
R2 – FD00:192:1:12::2 /64
R3 – FD00:192:1:34::3 /64
R4 – FD00:192:1:34::4 /64
R1 R2
Task 2
Configure the Loopback0 interface on all routers as follows:
R1 – Loopback0 – FD00:1:1:1::1/64
R2 – Loopback0 – FD00:2:2:2::2/64
R3 – Loopback0 – FD00:3:3:3::3/64
R4 – Loopback0 – FD00:4:4:4::4/64
R1
Interface Loopback 0
Ipv6 address FD00:1:1:1::1/64
R2
Interface Loopback 0
ipv6 address FD00:2:2:2::2/64
R3
Interface Loopback 0
Ipv6 address FD00:3:3:3::3/64
R4
Interface Loopback 0
ipv6 address FD00:4:4:4::4/64
Task 3
Configure the Serial Link between R2 and R3 using the folloing IPV6 addresses:
R2 – FD00:192:1:23::2/64
R3 – FD00:192:1:23::3/64
R2
Copyrights KBITS Inc 2006-2020
Website: http://www.kbits.in; Email: [email protected]
Page 121 of 404
We will free Kashmir soon. Inshallah - Dawood Ibrahim Siddiqui (CCIE #28842)
Interface S0/0
ipv6 address FD00:192:1:23::2/64
no shut
R3
Interface S0/0
ipv6 address FD00:192:1:23::3/64
no shut
Task 4
Configure RIPng on all routers to route all loopbacks. Enable RIPng under the
following interfaces:
R1 – F 0/0, Loopback 0
R2 – F 0/0, Loopback 0, S 0/0
R3 – F 0/0, Loopback 0, S 0/0
R4 – F 0/0, Loopback 0
R1 R2
Loppback 0 R1 R2 Loppback 0
FD00:1:1:1::1/64 F 0/0 F 0/0 FD00:2.2.2::2/64
FD00:192:1:12::/64
S 0/0
FD00:192:1:23::/64
Lo 0 F 0/0 F 0/0 Lo 0
R4 R3
Lab Scenario:
Initial Setup:
Based on Previous Lab
Task 1
Disable RIP NG on all routers on all interfaces.
R1 R2
Task 2
Configure EIGRPv6 in AS 100 on all routers to route all loopbacks. Configure
the EIGRP Router-id’s as follows:
R1 – 1.1.1.1
R2 – 2.2.2.2
R3 – 3.3.3.3
R4 – 4.4.4.4
R1 R2
! !
Interface S 0/0 Ipv6 router eigrp 100
Ipv6 eigrp 100 Router-id 4.4.4.4
! No shut
Ipv6 router eigrp 100
Router-id 3.3.3.3
No shut
Task 3
Authenticate the EIGRP Neighbor relationships using MD5 authentication. Use
Cisco as the Key with a key-id of 100.
R1
R4
Loppback 0 R1 R2 Loppback 0
FD00:1:1:1::1/64 F 0/0 F 0/0 FD00:2.2.2::2/64
FD00:192:1:12::/64
S 0/0
FD00:192:1:23::/64
Lo 0 F 0/0 F 0/0 Lo 0
R4 R3
Lab Scenario:
Initial Setup:
Based on Previous Lab
Task 1
Disable EIGRP on all routers on all interfaces. Disable the protocol on the
router as well.
R1 R2
Task 2
Configure the routers in OSPFv3 area 0 and advertise their directly connected
interfaces in this area. Configure the OSPF Router-id’s as follows:
R1 – 1.1.1.1
R2 – 2.2.2.2
R3 – 3.3.3.3
R4 – 4.4.4.4
R1 R2
R3 R4
Task 3
Ensure that the loopback interfaces are advertised with their correct mask.
R1 R2
R3 R4
Task 4
Authenticate & encrypt the OSPF neighbor relationships between R1 and R2
using the following parameters:
Encryption
o IPSec
o SPI : 1234
o Encryption Scheme : 3des
o Key : 123456789ABC123456789ABC123456789ABC123456789ABC
Authentication
o MD5
o Key : 12345678123456781234567812345678
R1
Interface F 0/0
ipv6 ospf encryption ipsec spi 1234 esp 3des
123456789ABC123456789ABC123456789ABC123456789ABC md5
12345678123456781234567812345678
R2
Interface F 0/0
ipv6 ospf encryption ipsec spi 1234 esp 3des
123456789ABC123456789ABC123456789ABC123456789ABC md5
12345678123456781234567812345678
Loppback 0 R1 R2 Loppback 0
FD00:1:1:1::1/64 F 0/0 F 0/0 FD00:2.2.2::2/64
FD00:192:1:12::/64
S 0/0
192.1.23.0/24
Lo 0 F 0/0 F 0/0 Lo 0
R4 R3
Lab Scenario:
Initial Setup:
None.
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 – FD00:192:1:12::1 /64
R2 – FD00:192:1:12::2 /64
R3 – FD00:192:1:34::3 /64
R4 – FD00:192:1:34::4 /64
R1 R2
Task 2
Configure the Loopback0 interface on all routers as follows:
R1 – Loopback0 – FD00:1:1:1::1/64
R2 – Loopback0 – FD00:2:2:2::2/64
R3 – Loopback0 – FD00:3:3:3::3/64
R4 – Loopback0 – FD00:4:4:4::4/64
R1
Interface Loopback 0
Ipv6 address FD00:1:1:1::1/64
R2
Interface Loopback 0
ipv6 address FD00:2:2:2::2/64
R3
Interface Loopback 0
Ipv6 address FD00:3:3:3::3/64
R4
Interface Loopback 0
ipv6 address FD00:4:4:4::4/64
Task 3
Configure RIPng on all routers to route all loopbacks. Enable RIPng under the
following interfaces:
R1 – F 0/0, Loopback 0
R2 – F 0/0, Loopback 0
R3 – F 0/0, Loopback 0
Copyrights KBITS Inc 2006-2020
Website: http://www.kbits.in; Email: [email protected]
Page 132 of 404
We will free Kashmir soon. Inshallah - Dawood Ibrahim Siddiqui (CCIE #28842)
R4 – F 0/0, Loopback 0
R1 R2
R3 R4
Task 4
Configure the Serial Link between R2 and R3 using the folloing IPv4 addresses:
R2 – 192.1.23.2/24
R3 – 192.1.23.3/24
R2
Interface S0/0
ip address 192.1.23.2 255.255.255.0
clock rate 1000000
no shut
R3
Interface S0/0
Ip address 192.1.23.3 255.255.255.0
no shut
Task 5
Create a Tunnel between R2 and R3 Assign it an IPv6 address of
FD00:192:1:23::/64. Set the Tunnel Mode to IPv6. Enable RIPng on the Tunnel
Interface to connect the 2 discontiguous RIP networks.
R2 R3
Lab Scenario:
Initial Setup:
Based on the previous Lab
Task 1
Configure a S-VTI tunnel interface to connect R1 to R4 using the following
parameters:
ISAKMP Policy:
o Authentication – Pre-share
o Hash – MD5
o Encryption – 3des
o Group 2
o Pre-shared key : Cisco
IPSec Parameters:
o Encryption – esp-3des
o Authentication – esp-md5-hmac
Tunnel Parameters:
o IPv6 Address:FD00:192:1:14::/64
o Tunnel Mode : Native IPSec
R1
Task 2
Configure the following Loopbacks on R1 and R4:
R1 – Loopback11 – FD00:11:11:11::11/64
R4 – Loopback11 – FD00:44:44:44::44/64
R1
Interface Loopback 11
Ipv6 address FD00:11:11:11::11/64
R4
Interface Loopback 11
ipv6 address FD00:44:44:44::44/64
Task 3
Configure EIGRPv6 in AS 100 on R1 & R4 to route the new loopbacks
(Loopback 11’s on R1 & R4). Configure the EIGRP Router-id’s as follows:
R1 – 1.1.1.1
R4 – 4.4.4.4
R1 R4
Module 1:
Basic ASA Configurations Module 1 – Basic ASA Configurations
on 9.X on 9.X
R1
F 0/0 (.1)
10.11.11.0/24
E0/1 (.10)
192.168.3.0/24 192.168.4.0/24
R3
F0/0 (.3) E0/2 (.10) E0/3 (.10) F0/0 (.4)
R4
E0/0 ASA
(.10)
192.1.20.0/24
F 0/0 (.2)
R2
Lab Scenario:
Initial Setup:
o R1 : 10.1.1.0/24
o R2 : 10.2.2.0/24
o R3 : 10.3.3.0/24
o R4 : 10.4.4.0/24
R1 R2
Copyrights KBITS Inc 2006-2020
Website: http://www.kbits.in; Email: [email protected]
Page 139 of 404
We will free Kashmir soon. Inshallah - Dawood Ibrahim Siddiqui (CCIE #28842)
Lab Tasks:
Task 1
Configure the ASA with the following IP configuration for the Interfaces:
At this point, the ASA should be able to ping all the surrounding routers.
FW
Interface G 0/0
Nameif Outside
Ip address 192.1.20.10 255.255.255.0
No shut
!
Interface G 0/1
Nameif Inside
Ip address 10.11.11.10 255.255.255.0
No shut
Copyrights KBITS Inc 2006-2020
Website: http://www.kbits.in; Email: [email protected]
Page 140 of 404
We will free Kashmir soon. Inshallah - Dawood Ibrahim Siddiqui (CCIE #28842)
!
Interface G 0/2
Nameif DMZ3
Ip address 192.168.3.10 255.255.255.0
Security-level 50
No shut
!
Interface G 0/3
Nameif DMZ4
Ip address 192.168.4.10 255.255.255.0
Security-level 50
No shut
Task 2
Configure the ASA to give out IP Configuration on the DMZ3 interface using the
following information:
FW
Task 3
Configure the ASA to get the clock from R2. The ASA and R2 are located in New
Delhi (GMT 5 30). R2 should be configured as the Master with a Stratum of 2.
Configure it with a key id of 1 and a MD5 key of cisco.
R2
Ntp authenticate
Ntp authentication-key 1 md5 cisco
Ntp trusted-key 1
Ntp server 192.1.20.2 key 1
Initial Setup:
Lab Task:
Task 1
Configure the Firewall with Static Routes for all internal loopback networks.
Internal Networks include networks off of the Inside, DMZ3 and DMZ4
interfaces.
FW
Task 2
Configure a default route on the Firewall pointing towards R2.
FW
Clear the Static Route configuration on the Routers and the Firewall.
Initial Setup:
Lab Task:
Task 1
Clear all the static routes on the Routers and Firewall. You will be configuring
Dynamic Routing protocols on them to learn routes.
FW
Task 2
Configure RIP v2 on the FW on the DMZ3 and DMZ4 interface. Disable auto-
summarization of routes. Also, configure RIP v2 on R3 and R4. Advertise the
Loopback networks on R3
FW
Router rip
No auto-summary
Version 2
Network 192.168.3.0
Network 192.168.4.0
R3
Router rip
No auto-summary
Version 2
Network 192.168.3.0
Network 10.0.0.0
R4
Router rip
No auto-summary
Version 2
Network 192.168.4.0
Network 10.0.0.0
Task 3
Configure the Firewall, R3 and R4 with RIP v2 authentication using a Key 1
and password of cciesec.
FW
Interface G 0/2
Rip authentication mode md5
Rip authentication key cciesec key_id 1
R3
Initial Setup:
Lab Task:
Task 1
Configure OSPF on the outside interface of the ASA in Area 0. Hard-code the
Router-id as 10.10.10.10. Also, configure OSPF on R2. Hard-code the router-id
as 2.2.2.2. Have R2 advertise the Loopback network in OSPF.
FW
Router OSPF 1
Router-id 10.10.10.10
Network 192.1.20.0 255.255.255.0 area 0
R2
Router OSPF 1
Router-id 2.2.2.2
Network 192.1.20.0 0.0.0.255 area 0
Network 10.2.2.0 0.0.0.255 area 0
Task 2
Configure the Firewall and R2 with a key of 1 and a password of cciesec. For
MD5 authentication.
FW
Interface G 0/0
Ospf authentication message-digest
Ospf message-digeset-key 1 md5 cciesec
R2
Interface F 0/0
Copyrights KBITS Inc 2006-2020
Website: http://www.kbits.in; Email: [email protected]
Page 147 of 404
We will free Kashmir soon. Inshallah - Dawood Ibrahim Siddiqui (CCIE #28842)
Initial Setup:
Lab Task:
Task 1
Configure EIGRP on the inside interface of the Firewall in AS 100 to exchange
routes with R1. Disable Auto-summarization. Advertise the R1 Loopbacks in
EIGRP.
FW
Task 2
Configure the Firewall and R2 with EIGRP authentication using a Key 1 and
password of cciesec.
FW
Interface G 0/1
authentication mode eigrp 100 md5
authentication key eigrp 100 cciesec key-id 1
R1
Key 1
Key-string cciesec
!
Int F 0/0
Ip authentication mode eigrp 100 md5
Ip authentication key-chain eigrp 100 AUTH
Task 3
Perform Route Redistribution such that all devices have a complete picture of
the entire topology.
FW
Router OSPF 1
Redistribute Rip subnets
Redistribute EIGRP 100 subnets
!
Router RIP
Redistribute ospf 1 metric 1
Redistribute EIGRP 100 metric 1
!
Router EIGRP 100
Redistribute ospf 1 metric 1 1 1 1 1
Redistribute RIP metric 1 1 1 1 1
Lab Scenario:
Configure the Firewall for Remote Management using Telnet and SSH.
Initial Setup:
Lab Task:
Task 1
Configure the Firewall for Telnet Management from the Inside interface. The
ASA should allow the 10.11.11.0/24 and the 10.1.1.0/24 networks to access it
for management.
FW
Task 2
Configure the Telnet password as cciesec on the Firewall.
FW
Passwd cciesec
Task 3
Enable SSH on the ASA. Allow R2 to connect to the ASA for Management from
the outside interface using SSH Version 2. The idle timeout for SSH
connections should be 2 minutes.
FW
Domain-name ABC.in
Crypto key generate rsa
!
Ssh version 2
Ssh timeout 2
Ssh 192.1.20.2 255.255.255.255 outside
Task 4
Create a username of ROUTER2 with a password of cciesec. Have the ASA
authenticate against the Local Username database for ssh connections.
FW
Module 2:
NAT & ACLs on 9.X Module 2 – NAT & ACLs on 9.X
R1
F 0/0 (.1)
10.11.11.0/24
192.168.3.0/24
E0/0 (.10)
192.1.20.0/24
F 0/0 (.2)
R2
Lab Scenario:
Initial Setup:
o R2 : 2.2.2.2/24
o R3 : 10.3.3.3/24
R1 R2
Copyrights KBITS Inc 2006-2020
Website: http://www.kbits.in; Email: [email protected]
Page 154 of 404
We will free Kashmir soon. Inshallah - Dawood Ibrahim Siddiqui (CCIE #28842)
R3
Int F 0/0
Ip address 192.168.3.3 255.255.255.0
No shut
!
Int loo0
Ip add 10.3.3.3 255.255.255.0
!
Ip route 0.0.0.0 0.0.0.0 192.168.3.10
Lab Tasks:
Task 1
Configure the ASA with the following IP configuration for the Interfaces:
At this point, the ASA should be able to ping all the surrounding routers.
FW
Interface G 0/0
Nameif Outside
Ip address 192.1.20.10 255.255.255.0
No shut
!
Interface G 0/1
Nameif Inside
Ip address 10.11.11.10 255.255.255.0
No shut
!
Copyrights KBITS Inc 2006-2020
Website: http://www.kbits.in; Email: [email protected]
Page 155 of 404
We will free Kashmir soon. Inshallah - Dawood Ibrahim Siddiqui (CCIE #28842)
Interface G 0/2
Nameif DMZ
Ip address 192.168.3.10 255.255.255.0
Security-level 50
No shut
Task 2
Configure a default route on the Firewall pointing towards R2.
FW
Task 3
The Firewall should translate all traffic going from the DMZ towards the
outside using 192.1.20.111 as the Public Address.
FW
Task 4
The Firewall should translate all traffic going from 10.11.11.0/24 towards the
outside using a pool of 192.1.20.151 – 192.1.20.200.
FW
Task 5
Create a loopback 100 on R1. Assign it an address of 10.1.1.1/24. Configure
the Firewall with a static route for this network. The Firewall should translate
all traffic going from this network towards outside using a pool of
192.1.20.131-192.1.20.149. Back this pool up by using a PAT address of
192.1.20.150.
FW
Interface Loopback100
Ip address 10.1.1.1 255.255.255.0
Task 6
Create a loopback 101 on R1. Assign it an address of 10.2.2.2/24. Configure
the Firewall with a static route for this network. The Firewall should translate
all traffic going from this network towards outside using Outside Interface.
FW
Task 7
Create a loopback 101 on R3. Assign it an address of 192.168.1.1/24.
Configure the Firewall with a static route for this network. The Firewall should
translate all traffic going from this network towards outside using a pool of
192.1.20.121-192.1.20.129. Back this pool up by using a PAT address of the
outside interface.
FW
Initial Setup:
Lab Task:
Task 1
Statically translate R1 such that it is seen as itself on the outside. It should not
get translated.
FW
object network R1
host 10.11.11.1
nat (inside,outside) static 10.11.11.1
Task 2
Statically translate R3 as 192.1.20.3 on the outside. Also, translate an ACS
located at 10.11.11.25 as 192.1.20.25 on the outside.
FW
object network R3
host 192.168.3.3
nat (DMZ,outside) static 192.1.20.3
!
object network ACS
host 10.11.11.25
nat (Inside,outside) static 192.1.20.25
Task 3
Configure Static PAT on the Firewall such that if a request comes from the
outside destined for an IP Address 192.1.20.7 with a port number 25, the
firewall should forward the request to a SMTP server located at 192.168.3.11. If
a request comes into the Firewall destined for an IP Address 192.1.20.7 with a
port number 23, the Firewall should forward the request to a Device located at
192.168.3.12 for 23.
FW
Lab Scenario:
Initial Setup:
Lab Task:
Task 1
There is a Mainframe located on the DMZ at 192.168.3.99. Another Mainframe
(200.1.1.10) from the outside needs to access it; The local Mainframe should be
seen as 192.1.20.29 on the outside. The local Mainframe does not have the
ability to point to a default gateway. Allow the Public Mainframe to access the
local Mainframe as a local device located at 192.168.3.98.
FW
Lab Scenario:
Initial Setup:
Lab Task:
Task 1
Configure the ASA such that when a PC 10.1.1.1 communicates with R2
Loopback0 (2.2.2.2), it is seen as 192.1.20.21 and when it communicates with
R2 F0/0 (192.1.20.2), it is seen as 192.1.20.22.
FW
Lab Scenario:
Allow traffic for the Translations that were configured in the previous lab.
Initial Setup:
Lab Task:
Task 1
Allow traffic in for R3’s translated address 192.1.20.3. You should only allow
traffic for Telnet, SSH and HTTP. Also allow traffic for the ACS server which
was translated to 192.1.20.25 in for HTTP, TACACS+, and the RADIUS ports.
FW
Task 2
Allow traffic destined to an IP Address 192.1.20.7 (already translated) for ports
SMTP and Telnet to come in.
FW
Task 3
Configure the Firewall such that only R2 Loopback 0 should be able to ping R1
F 0/0. You need to configure a static route on R2 for the 10.11.11.0/24
network to accomplish the task.
FW
Task 4
Configure the Firewall such that it should be able to ping outside but nobody
should be able to ping the ASA outside interface.
FW
Task 5
DMZ contains the following Application Servers and Applications:
Task 6
Create static one-on-one translations based on the above table.
FW
!
object network S-203
host 192.168.3.203
nat (DMZ,outside) static 192.1.20.203
!
object network S-204
host 192.168.3.204
nat (DMZ,outside) static 192.1.20.204
!
object network S-205
host 192.168.3.205
nat (DMZ,outside) static 192.1.20.205
!
object network S-206
host 192.168.3.206
nat (DMZ,outside) static 192.1.20.206
!
object network S-207
host 192.168.3.207
nat (DMZ,outside) static 192.1.20.207
Task 7
Allow access to the Application Servers from the following networks:
101.1.1.0/24
150.1.5.0/24
175.4.1.0/24
199.1.33.0/24
215.5.7.0/24
FW
Object-group network PN
Network-object 101.1.1.0 255.255.255.0
Network-object 150.1.5.0 255.255.255.0
Network-object 175.4.1.0 255.255.255.0
Network-object 199.1.33.0 255.255.255.0
Network-object 215.5.7.0 255.255.255.0
!
Object-group network WEB-FTP-N
Network-object host 192.168.3.201
Network-object host 192.168.3.202
Module 3:
Configuring High Module 3 – Configuring High
Availability Features Availability Features
R1
F 0/0 (.1)
10.11.11.0/24
E 0/1 E 0/0
ASA
R2 R3
192.1.24.0/24
192.1.34.0/24
R4
Lab Scenario:
Initial Setup:
Run EIGRP in AS 100 to route between R2, R3 & R4. Advertise the
192.1.20.0/24 network on R2, the 192.1.30.0/24 on R3 and the
4.2.2.0/24 network on R4 in EIGRP.
R1 R2
Lab Tasks:
Task 1
Configure the E 0/0 and E 0/1 as part of Redundant Interface 1 in that order.
Assign it a virtual mac-address of your choice.
ASA-1
Interface Redundant 1
Member-interface E 0/0
Member-interface E 0/1
Mac-address 0001.AB01.1101
!
Interface G 0/0
No shut
!
Interface G 0/1
No shut
Task 2
Configure ASA with the following IP configuration for the Interfaces:
ASA-1
Interface Redundant 1
Nameif inside
Ip address 10.11.11.10 255.255.255.0
!
Interface G 0/2
Nameif outside-2
Ip address 192.1.20.10 255.255.255.0
No shut
!
Interface G 0/3
Nameif outside-3
Ip address 192.1.30.10 255.255.255.0
No shut
Lab Scenario:
Configure Floating static routes to allow the Firewall to pick the R2 as the
Primary ISP and R3 as the secondary IP.
This should be configured with SLA and Object tracking to make sure that
full reachability is there before it uses a particular ISP.
Initial Setup:
Lab Task:
Task 1
Configure the Firewall such that it uses R2 as its primary Default gateway and
R3 as the backup default gateway.
Task 2
If the link between R2 and R4 goes down, the Firewall should use the backup
default gateway to route the packets. Send SLA packet every 3 seconds. Set the
timeout value to 1 second.
ASA-1
R1
F 0/0 (.1)
10.11.11.0/24
ASA-1 ASA-2
192.1.20.0/24
F 0/0 (.2)
R2
Lab Scenario:
Initial Setup:
R1 R2
Lab Tasks:
Task 1
FW-1 and FW-2 will be configured in a Active/Standby Failover Setup. FW-1
will be the Primary Firewall and FW-2 will be the Secondary Firewall. Use the
following parameters for the Failover configurations:
FW-1
Interface G 0/2
No shutdown
!
Failover lan enable (In case of PIX Firewall)
Failover lan interface FC E0/2
Failover interface IP FC 10.10.10.1 255.255.255.0 standby 10.10.10.2
Failover key cisco123
Failover lan unit primary
Failover
FW-2
Interface G 0/2
No shutdown
!
Failover lan enable (In case of PIX Firewall)
Failover lan interface FC E0/2
Failover interface IP FC 10.10.10.1 255.255.255.0 standby 10.10.10.2
Failover key cisco123
Failover lan unit secondary
Failover
Task 2
Configure FW-1 with the following Primary and Standby IP Addresses:
FW-1
Interface G 0/0
Ip address 192.1.20.10 255.255.255.0 standby 192.1.20.11
Nameif Outside
No shut
!
Interface G 0/1
Ip address 10.11.11.10 255.255.255.0 standby 10.11.11.11
Nameif inside
No shut
Task 3
Configure RIP v2 as the routing protocol on both the Routes and the Firewall.
Configure an Loopback interface 10.1.1.1/24 on R1 and 10.2.2.2/24 on R2.
Advertise them under RIP.
R1
Interface Loopback 0
Ip address 10.1.1.1 255.255.255.0
!
Router rip
No auto-summary
Version 2
Network 10.0.0.0
R2
Interface Loopback 0
Ip address 10.2.2.2 255.255.255.0
!
Router rip
No auto-summary
Version 2
Network 10.0.0.0
Network 192.1.20.0
FW-1
Router Rip
Version 2
No auto-summary
Network 10.0.0.0
Network 192.1.20.0
Task 4
Allow the inside networks to go out using a Outside pool of 192.1.20.51 –
192.1.20.100.
FW-1
Lab Scenario:
Initial Setup:
Lab Task:
Task 1
Configure G 0/3 as the Failover link to replicated the State and connection
information from the Active Firewall to the Standby firewall. Configure E 0/3
with an IP Address of 10.20.20.1/24 as the Active Address and 10.20.20.2/24
as the Standby address. Assign it a name of SFF.
FW-1
Interface G 0/3
No shut
!
Failover link G 0/3 SFF
Failover interface IP SFF 10.20.20.1 255.255.255.0 standby 10.20.20.2
***Note : This only needs to be done on the Active device as the
configuration will be replicated to the standby box
R1 F 0/0 (.1)
192.1.100.0/24 VLAN 100
R4
10.40.40.0/24
ASA1-C1 ASA1-C2
F 0/0 (.4) E 0/1.4 (.11)
R2 R3
Lab Scenario:
Initial Setup:
R1 R2
Interface F 0/1
Description Connected to R1
Switchport mode access
Switchport access vlan 100
!
Interface F 0/2
Description Connected to R2
Switchport mode access
Switchport access vlan 20
!
Interface F 0/3
Description Connected to R3
Switchport mode access
Switchport access vlan 30
!
Interface F 0/4
Description Connected to R4
Switchport mode access
Switchport access vlan 40
Lab Tasks:
Task 1
Configure both FW’s for Multiple Contexts. The Second one will be used later
for Active/Active Failover
FW-1 FW-2
Task 2
Bring up the interfaces E0/0 and E 0/1. Split E 0/1 into 3 sub-interfaces
based on the Network diagram on FW-1. Configure the Switch to assign the
Firewall ports to the appropriate VLANs or Trunk Ports.
FW-1
Interface E 0/0
No shut
!
Interface E 0/1
No shut
!
interface E 0/1.2
Vlan 20
interface E 0/1.3
Vlan 30
interface E 0/1.4
Vlan 40
Switch
Interface F 0/10
Description Connected to FW-1 E0/0
Switchport mode access
Switchport access vlan 100
!
Interface F 0/11
Description Connected to FW-1 E0/1
Switchport trunk encapsulation dot1q
Switchport mode trunk
Task 3
Configure two contexts on FW-1. Name them as VFW1 and VFW2. Configure
them with configuration files VFW1.cfg and VFW2.cfg respectively on Flash.
Allocate the appropriate interface to the appropriate contexts based on the
Copyrights KBITS Inc 2006-2020
Website: http://www.kbits.in; Email: [email protected]
Page 179 of 404
We will free Kashmir soon. Inshallah - Dawood Ibrahim Siddiqui (CCIE #28842)
Network Diagram. (Note: Delete any existing .cfg files in flash before creating
the context)
FW-1
Context VFW1
Allocate-interface E0/0
Allocate-interface E0/1.2
Allocate-interface E0/1.4
Config-url flash:VFW1.cfg
!
Context VFW2
Allocate-interface E0/0
Allocate-interface E0/1.3
Config-url flash:VFW2.cfg
Task 4
Configure Virtual-Mac addresses of your choice on the shared interface to allow
the FW to classify the traffic using the MAC- Address. Configure Interfaces in
Context VFW1 as follows:
FW-1
Task 5
FW-1
FW-1
Task 7
Configure VFW2 to allow the inside network access to the outside networks
using Dynamic Translation. Use a pool of 192.1.100.71 – 192.1.100.89.
Backup the NAT pool with a PAT Pool using an IP Address of 192.1.100.90.
Create a Static Translation for R3 as 192.1.100.3 as the Translated address on
the Outside interface.
FW-1
Copyrights KBITS Inc 2006-2020
Website: http://www.kbits.in; Email: [email protected]
Page 181 of 404
We will free Kashmir soon. Inshallah - Dawood Ibrahim Siddiqui (CCIE #28842)
Task 8
Allow R2 to Telnet to R3 and vice versa.
FW-1
Task 9
Configure resource allocation for VFW-2 based on the following:
FW-1
Changeto system
class CM-VFW2
limit-resource Conns 100
limit-resource Telnet 3
limit-resource ASDM 3
limit-resource Xlates 100
!
context VFW2
member CM-VFW2
R1 (.1)
192.1.100.0/24 VLAN 100
ASA-1 C1 C2 ASA-2 C1 C2
R4
(.11)
(.4)
(.12)
R2 R3
Lab Scenario:
Configure Active/Active Failover with VFW1 Active on FW-1 & VFW2 active
on FW-2.
Initial Setup:
Lab Task:
Task 1
Configure FW-2 to back up FW-1 from the previous lab. Configure E 0/2 as the
Failover Link. This interface will be used to transmit Failover control messages.
Assign it a name of FC. Also assign it an active IP address of 10.100.100.1/24
FW-1
Changeto system
Interface E 0/2
No shutdown
!
Failover lan interface FC E0/2
Failover interface IP FC 10.100.100.1 255.255.255.0 standby 10.100.100.2
Failover key cciesec
Failover lan unit primary
ASA-2
Interface E 0/2
No shutdown
!
Failover lan interface FC E0/2
Failover interface IP FC 10.100.100.1 255.255.255.0 standby 10.100.100.2
Failover key cciesec
Failover lan unit secondary
*** Note: We did not enable Failover yet. We will wait until the entire
Active/Active configuration is done before enabling it.
Task 2
Configure Failover in such a way that VFW1 will try to become Active on FW-1
if it is up and VFW2 will try to become Active on FW-2 if it is up.
FW-1
failover group 1
preempt
failover group 2
secondary
preempt
!
Context ASA-C1
Join-failover-group 1
!
Context ASA-C2
Join-failover-group 2
***Note: This configuration only needs to be done on the Active/Primary
box. It will be replicated when Failover is established.
Task 3
Configure E 0/2 also to transmit State and connection information to the
Standby box.
FW-1
Failover
***Note: The Stateful Failover configuration is only done on the
Active/Primary box. Once, we have setup all the failover configuration
commands on the appropriate boxes, we enable failover on both the
boxes. Type Show Failover to make sure that VFW-1 (Group 1) is active
on FW-1 and VFW-2 (Group 2) is active on FW-2.
Task 4
Configure the Switch to assign the appropriate ports to the appropriate VLANS
for FW-2 and the Failover Interface for FW-1.
Switch
Interface F 0/12
Description Connected to FW-1 E0/2
Switchport mode access
Switchport access vlan 110
!
Interface F 0/15
Description Connected to FW-2 E0/0
Switchport mode access
Switchport access vlan 100
!
Interface F 0/16
Description Connected to FW-2 E0/0
Switchport trunk encapsulation dot1q
Switchport mode trunk
!
Interface F 0/17
Description Connected to FW-2 E0/2
Switchport mode access
Switchport access vlan 110
Task 5
Copyrights KBITS Inc 2006-2020
Website: http://www.kbits.in; Email: [email protected]
Page 185 of 404
We will free Kashmir soon. Inshallah - Dawood Ibrahim Siddiqui (CCIE #28842)
FW-1
Task 6
Re-Configure VFW-2 on FW-2 with the following Primary and Standby IP
Addresses for VFW2:
FW-2
R1
F 0/0 (.1)
10.11.11.0/24 VLAN 10
G 0/1 G 0/0
ASA
F 0/0 (.2)
R2
Lab Scenario:
Initial Setup:
R1 R2
Lab Tasks:
Copyrights KBITS Inc 2006-2020
Website: http://www.kbits.in; Email: [email protected]
Page 187 of 404
We will free Kashmir soon. Inshallah - Dawood Ibrahim Siddiqui (CCIE #28842)
Task 1
Configure the E 0/0 and E 0/1 as part of Port Channel 1.
ASA-1
Interface G 0/0
Channel-group 1 mode active
No shut
!
Interface G 0/1
Channel-group 1 mode active
No shut
Task 2
Configure ASA with the following IP configuration for the Interfaces:
ASA-1
Interface Port-Channel 1
Nameif Inside
Ip address 10.11.11.10 255.255.255.0
!
Interface G 0/2
Nameif Outside
Ip address 192.1.20.10 255.255.255.0
No shut
Task 3
Configure the devices in the appropriate VLAN’s on the Switch(s).
SW
R2
F 0/0 (.1)
192.1.20.0/24 – VLAN 20
ASA-1 ASA-2
10.11.11.0/24 – VLAN 10
F 0/0 (.2)
R2
Lab Scenario:
Initial Setup:
Lab Tasks:
Task 1
FW-1 and FW-2 will be configured in a Cluster. FW-1 will be the Master
Firewall and FW-2 will be the Slave Firewall. Use the following parameters for
the Failover configurations:
FW-1
Task 2
Configure Switch ports connecting towards the Gig 0/3 Interfaces of the 2
ASA’s and R2 in VLAN 20. Configure Switch ports connecting towards the Gig
0/1 Interfaces of the 2 ASA’s and R1 in VLAN 10.
SW1
Task 3
Configure FW-1 Interfaces based on the following table:
FW-1
Task 4
Configure EIGRP as the routing protocol is AS 100 on both the Routers and the
Firewall. Configure a Loopback interface 1.1.1.1/24 on R1 and 2.2.2.2/24 on
R2. Advertise them under RIP.
R1
Interface Loopback 0
Ip address 1.1.1.1 255.255.255.0
!
Router EIGRP 100
No auto-summary
Network 10.11.11.0 0.0.0.255
Network 1.0.0.0
R2
Interface Loopback 0
Ip address 10.2.2.2 255.255.255.0
!
Router EIGRP 100
No auto-summary
Network 2.2.2.0 0.0.0.255
Network 192.1.20.0
FW-1
R2
F 0/0 (.1)
192.1.20.0/24 – VLAN 20
PO 20 [.11]
G 0/3 G 0/3
ASA-1 ASA-2
PO 10 [.11]
10.11.11.0/24 – VLAN 10
F 0/0 (.2)
R2
Lab Scenario:
Initial Setup:
R1 R2
!
Ip route 0.0.0.0 0.0.0.0 10.11.11.11
Lab Tasks:
Task 1
FW-1 and FW-2 will be configured in a Cluster. FW-1 will be the Master
Firewall and FW-2 will be the Slave Firewall. Use the following parameters for
the Failover configurations:
FW-1
cluster.
Task 2
Configure FW-1 Ports and the correcponding switch ports in an Port-channel
based on the following table:
FW-1
Interface G 0/1
Channel-group 10 mode active
No shut
!
Interface G 0/3
Channel-group 20 mode active
No shut
SW1
Task 3
Configure FW-1 Port-channel Interfaces based on the following table
FW-1
Interface Port-channel 20
Port-channel span-cluster
Ip address 192.1.20.11 255.255.255.0
Nameif Outside
Mac-address aaaa.bbbb.cc20
No shut
!
Interface Port-channel 10
Port-channel span-cluster
Ip address 10.11.11.11 255.255.255.0
Nameif Inside
Mac-address aaaa.bbbb.cc10
No shut
Task 4
Configure EIGRP as the routing protocol is AS 100 on both the Routers and the
Firewall. Configure a Loopback interface 1.1.1.1/24 on R1 and 2.2.2.2/24 on
R2. Advertise them under RIP.
R1
Interface Loopback 0
Ip address 1.1.1.1 255.255.255.0
!
Router EIGRP 100
No auto-summary
Network 10.11.11.0 0.0.0.255
Network 1.1.1.0 0.0.0.255
R2
Interface Loopback 0
Ip address 10.2.2.2 255.255.255.0
!
Router EIGRP 100
No auto-summary
Network 2.2.2.0 0.0.0.255
Copyrights KBITS Inc 2006-2020
Website: http://www.kbits.in; Email: [email protected]
Page 197 of 404
We will free Kashmir soon. Inshallah - Dawood Ibrahim Siddiqui (CCIE #28842)
Network 192.1.20.0
FW-1
Task 5
Allow the inside networks to go out using a Outside pool of 192.1.20.51 –
192.1.20.100.
FW-1
Module 4:
Deep Packet Inspection
Module 4 – Deep Packet Inspection
R1
F 0/0 (.1)
10.11.11.0/24
ASA
192.1.20.0/24
F 0/0 (.2)
R2
Lab Scenario:
Configure System Based Layer 7 Inspection for FTP & EMSTP on Non-
Standard Ports.
Initial Setup:
o R1 : 200.1.1.0/24
o R2 : 200.2.2.0/24
Copyrights KBITS Inc 2006-2020
Website: http://www.kbits.in; Email: [email protected]
Page 200 of 404
We will free Kashmir soon. Inshallah - Dawood Ibrahim Siddiqui (CCIE #28842)
R1 R2
Int G 0/0
Nameif Outside
Ip add 192.1.20.10 255.255.255.0
No shut
!
Int G 0/1
Nameif Inside
Ip add 10.11.11.10 255.255.255.0
No shut
!
Route outside 0 0 192.1.20.2
Lab Tasks:
Task 1
Configure Dynamic NAT on the Firewall to allow in the inside users to go out
using a pool of 192.1.20.51-192.1.20.100.
FW
Task 2
Configure FTP to be inspected on port 2100 in addition to port 21. Do not use
any access-list for this task.
FW
Class CM4-FTP2100
Match port tcp eq 2100
!
policy-map global_policy
class CM4-FTP2100
inspect ftp
Task 3
Configure SMTP to be inspected on port 2500 in addition to port 25. Do not use
any access-list for this task.
FW
Class CM4-SMTP2500
Match port tcp eq 2500
!
policy-map global_policy
class CM4-SMTP2500
inspect esmtp
Task 4
Enable Application inspection in the Default inspection policy for the ICMP so
that inside users can ping outside the firewall.
ASA
policy-map global_policy
class inspection_default
inspect icmp
Initial Setup:
Lab Task:
Task 1
There is a FTP Server located at 10.11.11.221. Translate this server as
192.1.20.221 on the outside. Allow FTP traffic to this Server from the outside.
FW
Task 2
FTP traffic connections to this server should be reset if they are trying to
execute the following commands:
Put
Rmd
Rnfr
dele
FW
Task 3
There is a HTTP Server located at 10.11.11.222. Translate this server as
192.1.20.222 on the outside. Allow Web traffic to this Server from the outside.
FW
Task 4
Deny any web traffic that has any of the following characteristics coming into
the server:
• The word CMD anywhere in the URL.
• The word BOMB anywhere in the URL.
• If the packet has request header length greater than 250 bytes.
FW
reset
!
access-list HTTP-S permit tcp any host 192.1.20.222 eq 80
!
class CM4-RE-WEB
match access-list HTTP-S
!
policy-map global_policy
class CM4-RE-WEB
inspect http PM7-RE-WEB
Task 5
Configure your firewall to drop all e-mails that are greater the 1 MB in size. Do
not create a new class for this.
FW
Task 6
Configure your firewall to limit the number of ESP connections from the same
client to 25. Do not create a new class for it.
FW
Lab Scenario:
Initial Setup:
Lab Task:
Task 1
Configure a BGP Neighbor relationship between R1 and R2. They should be in
AS 100. They should advertise their local loopback interfaces to each other.
Configure a static route on R2 for the 10.11.11.0 network to provide
connectivity. Also create a static route for the 192.1.20.0 network. Although,
R1 has a default route, BGP needs a static route to build a neighbor
relationship.
R1
R1
To fix it, we modify the default behavior of the TCP Normalization field.
Task 3
Modify the default TCP Randomization parameters to allow the BGP
Authentication to take place.
FW
TCP-map BGPMAP
TCP-options range 19 19 allow
!
class-map BGP
match port tcp eq 179
!
policy-map global_policy
class BGP
set connection random-sequence-number disable
set connection advanced-options BGPMAP
Module 5:
Transparent Firewalls on
9.X Module 5 – Transparent Firewalls on
9.X
R1
F 0/0 (.1)
10.11.11.0/24 VLAN 11
G 0/1 Inside
ASA
G 0/0 Outside
10.11.11.0/24 VLAN 22
F 0/0 (.2)
R2
F 0/1 (.2)
192.1.23.0/24 VLAN 23
F 0/0 (.3)
R3
Lab Scenario:
Initial Setup:
o R1 : 10.1.1.0/24
o R2 : 10.2.2.0/24
o R3 : 3.3.3.3/8
R1 R2
Int loopback 0
Ip add 3.3.3.3 255.255.255.0
!
Int F 0/0
Ip add 192.1.23.3 255.255.255.0
No shut
Lab Tasks:
Task 1
Configure the Firewall as a Transparent Firewall.
FW
Firewall Transparent
Task 2
Configure G 0/0 as the outside interface with a security level of 0. Bring the
Interface up. Configure G 0/1 as the inside interface with a security level of
100. Configure them to be part of the same bridge group. Bring the Interfaces
up.
FW
Interface G 0/0
Nameif outside
Bridge-group 1
No shutdown
Copyrights KBITS Inc 2006-2020
Website: http://www.kbits.in; Email: [email protected]
Page 210 of 404
We will free Kashmir soon. Inshallah - Dawood Ibrahim Siddiqui (CCIE #28842)
!
Interface G 0/1
Nameif inside
Bridge-group 1
No shutdown
Task 3
Configure the devices in the appropriate VLAN’s on the Switch(s).
SW
Lab Scenario:
Initial Setup:
Lab Task:
Task 1
Assign the Firewall an IP address of 10.11.11.10/24 to the bridge-group
created in the previous lab. Configure the Firewall with a default gateway of
10.11.11.2.
FW
Interface BVI 1
IP address 10.11.11.10 255.255.255.0
!
Route outside 0 0 10.11.11.2
Task 2
Allow Management of the Firewall only from VLAN 11 devices. Telnet and SSH
access to the ASA should be allowed from the inside interface only.
FW
Domain-name ABC.in
!
crypto key generate rsa
!
telnet 10.11.11.0 255.255.255.0 inside
ssh 10.11.11.0 255.255.255.0 inside
Initial Setup:
Lab Task:
Task 1
Configure the Firewall to allow R2 and R1 to communicate to each other to
exchange Routing information. Configure R1 and R2 to run RIP v2 as the
routing protocol to exchange the loopback networks.
FW
Router RIP
No auto-summary
Version 2
Net 10.0.0.0
R2
Router RIP
No auto-summary
Version 2
Net 10.0.0.0
Task 2
Allow R1 to Telnet and HTTP into R2.
FW
Copyrights KBITS Inc 2006-2020
Website: http://www.kbits.in; Email: [email protected]
Page 213 of 404
We will free Kashmir soon. Inshallah - Dawood Ibrahim Siddiqui (CCIE #28842)
Task 3
The devices on the inside of the Firewall should be able to go out for Web,
SMTP and DNS traffic only.
FW
Task 4
You will be configuring MPLS-Unicast Routing on R1 and R2 in the future.
Make sure the Firewall allows them to communicate to each other. Also, allow
BPDU packets and packets with a EtherType 0x2111 thru the Firewall.
FW
Initial Setup:
Task 1
Create a loopback 100 on R1. Assign it an address of 10.111.111.111/24.
Configure the Firewall with a static route for this network. The Firewall should
translate all traffic going from this network towards outside using a pool of
192.1.20.151-192.1.20.199. Back this pool up by using a PAT address of
192.1.20.200. Create a static route for 192.1.20.0/24 network on R2 & R3
pointing towards the appropriate next hop. This network was assigned to the
company as the public range.
FW
Task 2
There is a Web server located at 10.111.111.25. This server should be seen as
192.1.20.151 on the Internet. Perform the translation on the Firewall. R1
should be seen as 192.1.20.1 on the Internet. Allow access to these devices
from the Internet.
FW
Module 6:
Configuring the Firewall
Component of FTD
Module 6 – Configuring the Firewall
Component of FTD
R
1
MGMT PC F 0/0 (.1)
10.11.11.0/24
192.168.3.0/24
192.168.1.0/24
192.1.20.0/24
FMC F 0/0 (.2)
R2
Lab Scenario:
Initial Setup:
o R1 : 10.1.1.0/24, 100.1.1.1/2
o R2 : 2.2.2.0/24,199.1.1.1/24,200.1.1.1/24
o R3 : 10.3.3.0/24
R1 R2
Int Loopback 1
Ip add 10.3.3.3 255.255.255.0
!
Int F 0/0
Ip add 192.168.3.3 255.255.255.0
No shut
!
Ip route 0.0.0.0 0.0.0.0 192.168.3.10
Lab Tasks:
Task 1
1. Configure an IP address on the FTD as 192.168.1.46/24 with a Default
Gateway of 192.168.1.1.
FTD CLI
Task 2
Configure the Firepower Management Center [FMC] IP as 192.168.1.45/24
with a default gateway of 192.168.1.1.
FMC CLI
configure-network
Configure the FTD to use the FMC as the Manager Device from CLI
Initial Setup:
Lab Task:
Task 1
Configure the address for the Management FMC along with a secret key of
cisco123
FTD CLI
Task 2
Log into the FMC using a browser [Use IE]The default username is Admin
generally with a password of Sourcefire or Admin123
PC
Solution of AVI
Task 3
Register the FTD. Create a Default Policy that will Block all the Traffic.
PC
Task 4
Set the Time to be synchronized locally:
PC
Lab Scenario:
Initial Setup:
Lab Tasks:
Task 1
Configure the FTD with the following IP configuration for the Interfaces:
At this point, the FTD should be reachable from R1,R2 & R3.
FTD [FMC]
Device -> Device Management -> FTD -> Edit [Pencil] -> Interfaces
Lab Scenario:
Initial Setup:
Lab Task:
Task 1
Configure the FTD with a Static Route to the internal loopback network
100.1.1.0/24.
FTD [FMC]
Device -> Device Management -> FTD -> Edit [Pencil] -> Routing
Task 2
Configure a default route on the FTD pointing towards R2.
FTD [FMC]
Device -> Device Management -> FTD -> Edit [Pencil] -> Routing
Lab Scenario:
Configure RIP v2 on the Firewall.
Initial Setup:
Lab Task:
Task 1
Configure RIP v2 on the FTD on the DMZ interface. Disable auto-
summarization of routes. Also, configure RIP v2 on R3. Advertise the Loopback
network on R3 under RIP.
FTD [FMC]
Device -> Device Management -> FTD -> Edit [Pencil] -> Routing
Click RIP
Router rip
No auto-summary
Version 2
Network 192.168.3.0
Network 10.0.0.0
Task 2
Configure the FTD & R3 with RIP v2 authentication using a Key 1 and
password of cciesec.
FTD [FMC]
Copyrights KBITS Inc 2006-2020
Website: http://www.kbits.in; Email: [email protected]
Page 225 of 404
We will free Kashmir soon. Inshallah - Dawood Ibrahim Siddiqui (CCIE #28842)
Lab Scenario:
Initial Setup:
Lab Task:
Task 1
Configure OSPF on the Inside interface of the FTD in Area 0. Hard-code the
Router-id as 10.10.10.10. Also, configure OSPF on R1. Hard-code the router-id
as 0.0.0.1. Have R1 advertise the Loopback network 10.1.1.0/24 in OSPF.
Have the FTD inject a default route towards the Inside network.
FTD [FMC]
Device -> Device Management -> FTD -> Edit [Pencil] -> Routing
Click OSPF
Router OSPF 1
Router-id 0.0.0.1
Network 10.11.11.0 0.0.0.255 area 0
Network 10.1.1.0 0.0.0.255 area 0
Task 2
Configure the Firewall and R2 with a key of 1 and a password of cciesec. For
MD5 authentication.
FTD [FMC]
Interface F 0/0
ip Ospf authentication message-digest
ip Ospf message-digeset-key 1 md5 cciesec
Initial Setup:
Lab Task:
Task 1
Configure EIGRP on the inside interface of the Firewall in AS 65001 to
exchange routes with R2.. Advertise the R2 Loopbacks in BGP.
FTD [FMC]
Device -> Device Management -> FTD -> Edit [Pencil] -> Routing
Click BGP
Task 2
Configure the FTD and R2 with BGP authentication using a Key of cciesec.
FTD [FMC]
Task 3
Perform Route Redistribution such that all devices have a complete picture of
the entire topology.
FTD [FMC]
Initial Setup:
Lab Task:
Task 1
Allow access to the following servers for the specific ports specified below:
FTD [FMC]
Task 2
Allow access to the following servers for the specific ports specified below:
FTD [FMC]
Initial Setup:
Lab Tasks:
Task 1
Blacklist all Bogon Networks on the Outside Zone. Also, blacklist RFC-1918
address on the Outside Zone. Also, Blacklist Bogon URLs on the Outside Zone.
FTD [FMC]
Task 2
Block all traffic coming in from the Outside zone that is sourced from Russia.
Make it a Mandatory rule.
FTD [FMC]
Task 3
Block all High & Medium Risk applications. This should be applied to traffic
from INSIDE to OUTSIDE Zones. Make it a Mandatory Rule.
FTD [FMC]
Task 4
Add a rule at the top of Default Category to block the following URL Categories.
This should be done for Traffic from the INSIDE zone to the OUTSIDE zone:
Adult & Pornography
Gambling
Keyloggers & Monitoring
FTD [FMC]
Lab Scenario:
Initial Setup:
Lab Task:
Task 1
The Firewall should translate all traffic going from 10.11.11.0/24 towards the
outside using a pool of 192.1.20.151 – 192.1.20.200.
FTD [FMC]
Task 2
The Firewall should translate all traffic going from 10.1.1.0/24 towards the
outside using an IP Address of 192.1.20.9.
FW
FTD [FMC]
Lab Scenario:
Configure Static NAT
Initial Setup:
Lab Task:
Task 1
Statically translate the following devices on the Outside:
FW
FTD [FMC]
Task 2
Statically translate R1-Loopback100 [100.1.1.1/32] such that it is seen as
itself on the outside. It should not get translated.
FW
FTD [FMC]
Lab Scenario:
Initial Setup:
Lab Task:
Task 1
Configure Static PAT on the Firewall such that if a request comes from the
outside destined for an IP Address 192.1.20.7 with a port number 25, the
firewall should forward the request to a SMTP server located at 192.168.3.21
FTD [FMC]
Task 2
. If a request comes into the Firewall destined for an IP Address 192.1.20.7
with a port number 80, the Firewall should forward the request to a Device
located at 192.168.3.22 for 80.
FTD [FMC]
Lab Scenario:
Initial Setup:
Lab Task:
Task 1
Configure the Firewall such that when a PC 10.1.1.1 communicates with R2
Loopback199 (199.1.1.1], it is seen as 192.1.20.31
FTD [FMC]
Task 2
Configure the Firewall such that when a PC 10.1.1.1 communicates with R2
Loopback200 (200.1.1.1], it is seen as 192.1.20.32.
FTD [FMC]
Lab Scenario:
Initial Setup:
Lab Task:
Task 1
There is a Mainframe located on the DMZ at 192.168.3.99. Another Mainframe
(200.1.1.1) from the outside needs to access it; The local Mainframe should be
seen as 192.1.20.29 on the outside. The local Mainframe does not have the
ability to point to a default gateway. Allow the Public Mainframe to access the
local Mainframe as a local device located at 192.168.3.98.
FTD [FMC]
Module 7:
Configuring Intrusion
Prevention on FTD
Module 7 – Configuring Intrusion
Prevention on FTD
Lab Scenario:
Initial Setup:
Lab Task:
Task 1
Configure an Intrusion Policy using the following parameters:
FTD [FMC]
Task 2
All permit rules in the ACP from the previous labs should be checked against
this policy.
FTD [FMC]
Initial Setup:
Lab Task:
Task 1
Tune the IPS-FTD-POL-1 created in the previous Lab to enable the following
signatures:
FTD [FMC]
Task 2
Change the Action of the IMAP signature enabled in the previous task to
Generate Events only.
FTD [FMC]
Task 3
Change the Action of the Skype signature enabled in the previous task to Drop
& Generate Events.
FTD [FMC]
Lab Scenario:
Initial Setup:
Lab Task:
Task 1
The Skype signature enabled in the previous task should not fire for
192.168.1.11 & 10.11.11.1 IP addressess
FTD [FMC]
Lab Scenario:
Initial Setup:
Lab Task:
Task 1
Configure a signature to fire based on a ICMP Packet.
FTD [FMC]
Task 2
Enable the Custom Signature in the IPS-FTD-POL-1 policy. It should drop the
packet and Generate an event.
FTD [FMC]
Lab Scenario:
Initial Setup:
Lab Task:
Task 1
Configure a Network Discovery Policy to discover the Hosts & their
applications. The Network Discovery should only be done on the INSIDE and
DMZ zones.
FTD [FMC]
Task 2
Delete any other policy except for the one that you created in the previous task.
FTD [FMC]
Initial Setup:
Lab Task:
Task 1
Re-Configure the IPS-FTD-POL-1 policy to include Firepower recommendations.
FTD [FMC]
Module 8:
Configuring AMP on FTD
Module 8 – Configuring AMP on FTD
Lab Scenario:
Initial Setup:
Lab Task:
Task 1
Configure a File & Malware Policy called INSIDE-FILE-POLICY to using the
following requirements:
FTD [FMC]
Task 2
Configure a File & Malware Policy called DMZ-FILE-POLICY to using the
following requirements:
Upload of any Executable or Archive Files using any protocol – Block with
Reset.
Upload of any .MDB file - Block
FTD [FMC]
Task 3
Configure all the Permit policies from INSIDE towards the OUTSIDE zone to
check the INSIDE-FILE-POLICY.
FTD [FMC]
Task 4
Configure all the Permit policies from OUTSIDE towards the DMZ zone to check
the DMZ-FILE-POLICY.
FTD [FMC]
Initial Setup:
Lab Task:
Task 1
Re-configure INSIDE-FILE-POLICY AMP Policy to using the following
requirements:
Download of any PDF using any protocol – Block Malware with Reset.
Check using Dynamic & Local Malware Analysis.
Download of any Office Document using any protocol – Block Malware with
Reset. Check using Local Malware Anaylysis only.
FTD [FMC]
Task 2
Re-configure DMZ-FILE-POLICY AMP Policy to using the following
requirements:
Download of any File except for MDB, Executable or Archive files – Block
Malware with Reset. Check using Dynamic & Local Malware Analysis.
FTD [FMC]
Module 9:
Configuring Zone-based
Firewalls Module 9 – Configuring Zone-based
Firewalls
R1
S 0/0 (.1)
192.1.12.0/24 R4
S 0/0 (.2)
F 0/0 (.4)
192.1.24.0/24
F 0/1 (.2)
R2
F 0/0 (.2)
192.1.23.0/24
F 0/0 (.3)
R3
Lab Scenario:
Initial Setup:
R1 R2
Lab Tasks:
Task 1
Configure the zones and apply them based on the following on R2:
R2
Interface S0/0
Zone-member security INTERNET
!
Interface F0/0
Zone-member security LOCAL
!
Interface F0/1
Zone-member security DMZ
Task 2
Allow the Following protocols to go from the LOCAL to the INTERNET zone:
HTTP
HTTPS
DNS
FTP
TFTP
SMTP
ICMP
RDP
R2
Task 3
Allow the Following protocols to go from the LOCAL to the DMZ zone:
HTTP
HTTPS
DNS
SMTP
ICMP
TELNET
R2
Task 4
Allow the Following protocols to go from the INTERNET to the DMZ zone:
R2
Inspect
!
zone-pair security I-D source INTERNET destination DMZ
service-policy type inspect PM-I-D
Initial Setup:
Lab Task:
Task 1
Configure Inspection of RDP from LOCAL to DMZ zone.
R2
Initial Setup:
Lab Task:
Task 1
Configure Access to a server located at 192.1.24.11 for Web Services [HTTP or
HTTPS]
R2
Module 10 –
Configuring VPNs Module 10 – Configuring VPNs on ASA &
on ASA & FTD FTD
R1
F 0/0 (.1)
10.11.11.0/24 VLAN 11
G 0/1 (.11)
FTD
G 0/0 (.11)
192.1.10.0/24
R2 F 0/0.1(.5)
R5
F 0/0 (.2) F 0/0.2 (.5) F 0/0.4(.5) 192.1.40.0/24
192.1.20.0/24
F 0/0.5(.5) F 0/0.3(.5)
F 0/0.6(.5)
Test PC (.15)
ASA-1 ASA-2
10.40.40.0/24 VLAN 40
F 0/0 (.4)
R4
Lab Scenario:
Initial Setup:
Configure the IP Addresses on the Routers & FW based on the Diagram.
Configure the 2 switches to trunk using dot1q. Configure SW1 as the VTP
Server in domain cisco. Configure SW2 as the VTP Client in domain cisco.
Point all the Device to the logical next hop for the Default Gateway.
R1 R2
R3 FTD
Vlan 41
Vlan 42
Note : Port Assignment based on the
Physical Topology
ASA1 ASA2
Lab Tasks:
Task 1
Configure an IPSec Tunnel on ASA1 to encrypt traffic from 10.40.40.0/24 to
the 10.2.2.0/24 on R2 (Loopback 0) using the following parameters for IPSec:
ISAKMP Parameters
o Authentication : Pre-shared
o Encryption : 3DES
o Group : 2
o Hash : MD5
o Pre-Shared Key : cisco
IPSec Parameters
o Encryption : ESP-3DES
o Authentication : ESP-SHA-HMAC
ASA-1
Encryption 3des
!
tunnel-group 192.1.20.2 type ipsec-l2l
tunnel-group 192.1.20.2 ipsec-attributes
pre-shared-key cisco
!
crypto ipsec transform-set T-SET esp-3des esp-sha-hmac
!
access-list 150 permit ip 10.40.40.0 0.0.0.255 10.2.2.0 0.0.0.255
!
crypto map I-MAP 10 set peer 192.1.40.4
crypto map I-MAP 10 set peer 192.1.40.4
crypto map I-MAP 10 set transform-set T-SET
crypto map I-MAP 10 match address 150
!
Crypto map I-MAP Interface Outside
R2
Lab Scenario:
Initial Setup:
Lab Tasks:
Task 1
Configure an IPSec Tunnel on ASA-2 to encrypt traffic from 10.40.40.0/24 to
the 10.3.3.0/24 on R3 (Loopback 0) using the following parameters for IPSec:
IKEv2 Parameters
o Authentication : Pre-shared
o Encryption : AES-256
o Group : 2
o Inegrity : SHA-256
o PRF : SHA-256
o Pre-Shared Key : ASA-2-R3 -> cisco11
o Pre-Shared Key : R3-ASA-2 -> cisco22
IPSec Parameters
o Encryption : ESP-3DES
o Authentication : ESP-SHA-HMAC
ASA-2
Initial Setup:
Lab Tasks:
Task 1
Configure ASA2 as a Local Trustpoint using the information below. Self enroll
the certificate.
FQDN : ASA2.khawarb.com
Trustpoint Name: LOCAL
Subject name=ASA2.khawarb.com
Key Pair name=VPN
ASA-2
domain-name khawarb.com
hostname ASA2
!
crypto key generate rsa label VPN modulus 1024 noconfirm
!
crypto ca trustpoint LOCAL
enrollment self
fqdn ASA2.khawarb.com
subject-name CN=ASA2.khawarb.com
keypair VPN
!
crypto ca enroll LOCAL noconfirm
Task 2
Configure the IKEv2 Profile file as an XML file called IKEv2.xml and upload the
file to ASA-2. The content of the XML is give below.
ASA-2
Copyrights KBITS Inc 2006-2020
Website: http://www.kbits.in; Email: [email protected]
Page 269 of 404
We will free Kashmir soon. Inshallah - Dawood Ibrahim Siddiqui (CCIE #28842)
Task 3
Enable Webvpn on the ASA2. Use the anyconnect file on flash as the image file.
Enable webvn such that the client have the ability to pick the Tunnel group.
Use the anyconnect profile created in the previous Task. Name the Profile as
IKEv2.
ASA-2
webvpn
enable outside
anyconnect image disk0:/anyconnect-win-4.2.01022-k9.pkg
anyconnect enable
tunnel-group-list enable
anyconnect profiles IKEv2 flash:IKEv2.xml
Task 4
Configure the Group Policies using the following information:
Group ADMINS
o VPN-Tunnel-Protocol : IKEv2
o DNS Server: 8.8.8.8
o Anyconnect profile : IKEv2
Group EMPLOYEES
o VPN-Tunnel-Protocol : IKEv2
o DNS Server: 8.8.8.8
o Anyconnect profile : IKEv2
ASA-2
webvpn
anyconnect profiles value IKEv2 type user
Task 5
Configure the Tunnel-group Policies using the following information:
Tunnel-Group ADMINS
o Default-group-policy : ADMINS
o Group-Alias: ADMINS
o VPN Pool – ADMINS : 192.168.51.1 192.168.51.254
Tunnel-Group EMPLOYEES
o Default-group-policy : EMPLOYEES
o Group-Alias: EMPLOYEES
o VPN Pool – EMPLOYEES : 192.168.52.1 192.168.52.254
ASA-2
Task 6
Configure the Usernames based on the following:
ASA-2
Task 7
Configure IKEv2 & IPSec Policies using the information below
Trustpoint : LOCAL
SSL Trustpoint Interface : Outside
username John password Cisco123
IKEv2 Policy:
o Encryption: 3Des
o Integrity & PRF: SHA1
o Group: 2
IPSec Policy:
o Encryption: 3Des
o Integrity & PRF: SHA1
ASA-2
Task 8
Configure a Dynamic Map and link it to a Static Map. Configure reverse-route.
Apply the Map to the Outside Interface.
ASA-2
Task 9
Browse to the Outside Interface IP address of ASA-2 using https. Download &
Install the client. Use the client to establish a IKEv2 VPN to the ASA network.
TEST PC
Initial Setup:
Lab Tasks:
Task 1
Enable Webvpn on the ASA1. Use the anyconnect file on flash as the image file.
Enable webvn such that the client have the ability to pick the Tunnel group.
ASA1
webvpn
enable outside
anyconnect image disk0:/anyconnect-win-4.2.01022-k9.pkg
anyconnect enable
tunnel-group-list enable
Task 2
Configure the Group Policies & the VPN Pool using the following information:
Group ADMINS
o Split-tunnel networks: 10.1.1.0/24 & 10.11.11.0/24
o VPN-Tunnel-Protocol : SSL-Client
Group EMPLOYEES
o Split-tunnel networks: 10.11.11.0/24
o VPN-Tunnel-Protocol : SSL-Client
ASA1
split-tunnel-policy tunnelspecified
split-tunnel-network-list value ADMINS
!
!
access-list EMPLOYEES standard permit 10.11.11.0 255.255.255.0
!
group-policy EMPLOYEES internal
group-policy EMPLOYEES attributes
vpn-tunnel-protocol ssl-client
split-tunnel-policy tunnelspecified
split-tunnel-network-list value EMPLOYEES
Task 3
Configure the Tunnel-group Policies using the following information:
Tunnel-Group ADMINS
o Default-group-policy : ADMINS
o Group-Alias: ADMINS
o VPN Pool – ADMINS : 192.168.51.1 192.168.51.254
Tunnel-Group EMPLOYEES
o Default-group-policy : EMPLOYEES
o Group-Alias: EMPLOYEES
o VPN Pool – EMPLOYEES : 192.168.52.1 192.168.52.254
ASA1
Task 4
Configure the Usernames based on the following:
ASA1
Task 5
Browse to the Outside Interface IP address of ASA-1 using https. Download &
Install the client. Use the client to establish a SSL VPN to the ASA network.
TEST PC
Lab Scenario:
Initial Setup:
Lab Tasks:
Task 1
Configure ASA2 for Clientless WebVPN using the following Parameters:
Group: SALES
o VPN-Tunnel-Protoco: SSL-Clientless
o Banner : Authorized Users Only !!!
o Port-forward: SALES-APPS
30001:10.11.11.1:80
30002:10.11.11.1:23
30003:10.11.11.1:1521
Users:
o Jane – Password – Cisco123
o Group-policy - SALES
ASA2
WebVPN - Basic
webvpn
enable outside
port-forward SALES-APPS 30001 10.11.11.1 80
port-forward SALES-APPS 30002 10.11.11.1 23
port-forward SALES-APPS 30003 10.11.11.2 1521
!
group-policy SALES internal
group-policy SALES attributes
vpn-tunnel-protocol ssl-clientless
banner value "XXXX"
webvpn
port-forward value SALES-APPS
Copyrights KBITS Inc 2006-2020
Website: http://www.kbits.in; Email: [email protected]
Page 277 of 404
We will free Kashmir soon. Inshallah - Dawood Ibrahim Siddiqui (CCIE #28842)
!
username khawar password cisco123
username khawar attributes
vpn-group-policy SALES
Lab Scenario:
Initial Setup:
Lab Tasks:
Task 1
Configure an IPSec Tunnel to encrypt traffic from 10.11.11.0/24 behind FTD to
the 10.2.2.0/24 on R2 (Loopback 0) using the following parameters for IPSec:
ISAKMP Parameters
o Authentication : Pre-shared
o Encryption : 3DES
o Group : 2
o Hash : SHA
o Pre-Shared Key : cisco
IPSec Parameters
o Encryption : ESP-3DES
o Authentication : ESP-SHA-HMAC
FTD [FMC]
Lab Scenario:
Initial Setup:
Lab Tasks:
Task 1
Configure an IPSec Tunnel on FTD to encrypt traffic from 10.11.11.0/24 to the
10.3.3.0/24 on R3 (Loopback 0) using the following parameters for IPSec:
IKEv2 Parameters
o Authentication : Pre-shared
o Encryption : AES-256
o Group : 2
o Inegrity : SHA-256
o PRF : SHA-256
o Pre-Shared Key : FTD-R3 -> cisco11
o Pre-Shared Key : R3-FTD -> cisco22
IPSec Parameters
o Encryption : ESP-3DES
o Authentication : ESP-SHA-HMAC
FTD [FMC]
!
crypto ikev2 profile PROF-2
match identity remote address 192.1.10.11 255.255.255.255
authentication remote pre-share
authentication local pre-share
keyring local KR-1
!
Access-list 151 permit ip 10.3.3.0 0.0.0.255 10.11.11.0 0.0.0.255
!
crypto map I-MAP 20 ipsec-isakmp
set peer 192.1.10.11
set transform-set T-SET
set ikev2-profile PROF-2
match address 151
Module 1 –
Configuring ACS for
Module 1 – Configuring ACS for
Management Management Authentication
Authentication
ASA R1 R3
F 0/1 (.3)
E 0/0 (.10)
R2 R4
Lab Scenario:
Authenticate Telnet & SSH connections based on the ACS using Local
Username database as the backup authentication mechanism.
Initial Setup:
Configure the IP Addresses on the Routers & FW based on the Diagram.
R1 R2
R3 SW1
FW
Interface G 0/1
Nameif inside
Ip add 192.168.43.10 255.255.255.0
No shut
Lab Tasks:
Task 1
Configure R1 and R2 as clients to the ACS Server. R1 should use TACACS+ as
the authentication protocol and R2 should use RADIUS as the authentication
protocol. Both should use ccie-r as the secret key.
ACS
Task 2
Configure a group called R-Admins on the ACS .
ACS
Task 3
Create the following users and make them members of the R-Admin group:
ACS
Task 4
Configure R1 and R2 to communicate with the ACS server for authentication.
Use the key and address in Task 1.
R1
Aaa new-model
Tacacs-server host 192.1.10.25 key ccie-r
** do test aaa group tacacs ruser1 ruser1 legacy.
** This command verifies that the ACS is communicating to the
device
R2
Aaa new-model
radius-server host 192.1.10.25 key ccie-r
** do test aaa group radius ruser1 ruser1 legacy
** This command verifies that the ACS is communicating to the
device
Task 5
Configure Telnet and SSH Authentication to be done based on the ACS server
for R1 & R2. If the ACS server is not available, they should use the Local
database for authentication. Create a user on the router called admin with a
password of admin. Make sure the Console port is not authenticated
R1
Initial Setup:
Lab Task:
Task 1
Configure SW1 as a client to the ACS Server. SW1 should use RADIUS as the
authentication protocol. Use ccie-sw as the secret key.
ACS
Task 2
Configure a group called SW-Admins.
ACS
Task 3
Create the following users and make them members of the SW-Admin group:
ACS
Task 4
Configure SW1 to communicate with the ACS server for authentication. Use the
key and address in Task 1.
SW1
Aaa new-model
radius-server host 192.1.10.25 key ccie-sw
** do test aaa group radius swuser1 swuser1 legacy.
** This command verifies that the ACS is communicating to the
device
Task 5
Configure Telnet Authentication to be done based on the ACS server for SW1. If
the ACS server is not available, it should use the Local database for
authentication. Create a user on the switch called admin with a password of
admin. Make sure the Console port is not authenticated
SW1
Authenticate Telnet & SSH connections based on the ACS using Local
Username database as the backup authentication mechanism.
Initial Setup:
Lab Tasks:
Task 1
Configure the Firewall as a client to the ACS Server. The Firewall should use
TACACS+ as the authentication protocol. It should use ccie-fw as the secret
key.
ACS
Task 2
Configure a group called FW-Admins.
ACS
Task 3
Create the following users and make them members of the FW-Admin group:
ACS
Task 4
Configure the Firewall to communicate with the ACS server for authentication.
Use the key and address in Task 1.
FW
Task 5
Configure the Firewall for SSH. Configure SSH & Telnet Authentication to be
done based on the ACS server. If the ACS server is not available, the Firewall
should use the Local database for authentication. Create a user on the Firewall
called admin with a password of admin.
FW
Task 6
Allow Telnet from the 192.1.10.0 subnet only. Allow SSH from the
192.1.10.0/24 and 192.1.20.0/24 subnets.
FW
Module 2 –
Configuring ACS for
Module 2 – Configuring ACS for
Management Management Authorization
Authorization
ASA R1 R3
F 0/1 (.3)
E 0/0 (.10)
R2 R4
Lab Scenario:
Configure the Router to use the ACS server to assign the Privilege levels to
the user.
Initial Setup:
Lab Task:
Task 1
Ruser1 and Ruser2 should be assigned Privilege Level 15 by the ACS server.
ACS
Task 2
Configure R1 to perform Exec authorization on the VTY lines based on the ACS
server.
R1
aaa authorization exec T-AUTH group tacacs+
!
line vty 0 4
authorization exec T-AUTHOR
Lab Scenario:
Initial Setup:
Lab Task:
Task 1
Configure R5 as client to the ACS Server. R5 should use TACACS+ as the
authentication protocol. It should use ccie-r as the secret key.
ACS
Task 2
Configure R5 to communicate with the ACS server for authentication. Use the
key and address in Task 1.
R5
Aaa new-model
Tacacs-server host 192.1.10.25 key ccie-r
** do test aaa group tacacs ruser1 ruser1 legacy.
** This command verifies that the ACS is communicating to the
device
Task 3
Configure R5 to perform VTY authentication, Exec Authorization and
Command Authorization for Level 15 commands based on the ACS Server.
Assign all the users to Privilege level 15. They should be able to execute
commands in Privilege Exec and Global Configuration modes based on
Command Authorization from the ACS Server.
R5
Task 4
Configure 3 Shell Command Authorization sets on the ACS with the following
commands and capabilities:
RP-ADMIN
o Configure terminal
o Router RIP (Only allow him to enable RIP as a Routing Protocol)
o Execute the Network command for any network
o Execute the Version command; Limit it version 2 only
o Execute the no auto-summary command
SEC-ADMIN
o Configure Terminal
o Any Crypto command with any Arguments
o Authentication command with any Arguments
o Encryption command ; Limit it to 3des only
o Hash command with any Arguments
o Group command ; Limit it to 2 only
o Access-list command with any Arguments
o set command with any Arguments
o match command with any Arguments
o Interface command with any Arguments
SuperAdmin
o Should be allowed all commands.
ACS
Task 5
Assign the Shell Command Authorization Sets to the Users based on the
following:
Ruser1 – SuperAdmin
Ruser2 – RP-ADMIN
Ruser3 – SEC-ADMIN
ACS
Lab Scenario:
Initial Setup:
Lab Task:
Task 1
Configure R5 to allow HTTP Management. It should only allow HTTP
Management from VLAN 10.
R5
Task 2
Authenticate and Authorize the users connecting into R5 for HTTP using the
authentication and authorization lists configured in the previous Lab.
R5
Module 3 –
Configuring ACS for Module 3 – Configuring ACS for
Management Accounting
Management
Accounting
ASA R1 R3
F 0/1 (.3)
E 0/0 (.10)
R2 R4
Lab Scenario:
Configure the Routers to log all Telnet and SSH connections to the ACS
Server.
Initial Setup:
Lab Task:
Task 1
Track logins and logouts thru telnet & SSH into R1 & R5 to the ACS Server.
R1
Task 2
Log all Level 15 commands typed by these users while logged in thru telnet &
SSH.
R1
!
line vty 0 4
accounting commands 15 T-ACCT
Configure the Switch to log all Telnet and SSH connections to the ACS
Server.
Initial Setup:
Lab Task:
Task 1
Track logins and logouts thru telnet & SSH into the Switch to the ACS Server.
SW1
Lab Scenario:
Configure the Firewall to log all Telnet and SSH connections to the ACS
Server.
Initial Setup:
Lab Task:
Task 1
Track logins and logouts thru telnet & SSH into the Firewall to the ACS Server.
FW
Module 1 – Initial
Configuration of
Module 1 – Initial Configuration of the
the WLC & WAP Wireless LAN Controller (WLC) & the
Wireless Access Point (WAP)
R2 R3
F 0/0 (.2) F 0/0 (.3)
192.168.10.0/24 VLAN 10
F 0/1 (.1)
R1
(.50) (.100)
PC WLC WAP
Lab Scenario:
Initial Setup:
Configure the IP Addresses on the Routers based on the Diagram.
No shut
!
Router eigrp 100
No auto-summary
Network 192.168.10.0
Network 192.168.30.0
Lab Tasks:
Task 1
Re-initialize the WLC if required by using the Recover-config command from
the CLI.
WLC
Recover-config
Task 2
Initialize the WLC based on the following parameters:
Hostname : WLC
Admin Username : admin
Admin Password : Cisco123
IP Address : 192.168.123.99
Subnet Mask : 255.255.255.0
Default Gateway : 192.168.123.1
Management VLAN : 123
Physical Interface : 1
Virtual-IP : 100.100.100.100
Mobility Group : MGMT
Management SSID : MGMT
Country : ES
Radio : Enable all Radio
Auto RF : Yes
NTP Server : NO
Manual Time: Set it based on the Current time.
WLC
Task 3
Open a browser. Type https://192.168.123.99. Login using the administrator
name and password created in the previous step. Are you successful??
WLC
Configure R1 as the DHCP Server to give out IP Address for VLAN 100. All
the AP’s will be located on this segment.
Make sure the WAP communicates and registers with the WLC.
Initial Setup:
Lab Task:
Task 1
Configure R1 as the DHCP Server for VLAN 100. It should be configured with
the following parameters:
R1
Task 2
Configure R1 as the DHCP Server for VLAN 10. It should be configured with the
following parameters:
R1
Task 3
Configure R1 as the DHCP Server for VLAN 20. It should be configured with the
following parameters:
R1
Task 4
Configure R1 as the DHCP Server for VLAN 30. It should be configured with the
following parameters:
R1
Task 3
Make sure that the WAP has registered with the WLC.
WLC
Module 2 –
Configuring a Basic Module 2 – Configuring a Basic
Wireless LAN
Wireless LAN
Initial Setup:
Lab Task:
Task 1
Configure a VLAN Interface for VLAN 10 based on the following parameters:
WLC
Task 2
Configure a VLAN Interface for VLAN 20 based on the following parameters:
WLC
Task 3
Configure a VLAN Interface for VLAN 30 based on the following parameters:
WLC
Lab Scenario:
Initial Setup:
Lab Task:
Task 1
Configure a WLAN for the SALES VLAN (20) using the following parameters:
WLC
Task 2
Go to Network Connections; Right-click on the Wireless NIC; Click View
Wireless Networks; Select SALES. Did you connect?
PC
Task 3
Open a command prompt. Type ipconfig. What IP address was assigned to the
wireless client?
PC
Task 4
Open the Command prompt. Type tracert 192.168.30.3. What are the hops
from the Wireless client to the destination?
PC
Initial Setup:
Lab Task:
Task 1
Configure a WLAN for the Marketing VLAN (30) using the following parameters:
WLC
Task 2
Go to Network Connections; Right-click on the Wireless NIC; Click View
Wireless Networks; Select MARKETING. When prompted, type the PSK
configured in the previous step.. Did you connect?
PC
Task 3
Open a command prompt. Type ipconfig. What IP address was assigned to the
wireless client?
PC
Task 4
Open the Command prompt. Type tracert 192.168.20.2. What are the hops
from the Wireless client to the destination?
PC
Initial Setup:
Lab Task:
Task 1
Configure a WLAN for the IT VLAN (10) using the following parameters:
WLAN Name : IT
SSID : IT
Interface : VLAN10
Security : Static WEP
o PSK : 104-bit – C1SCOcisco123
WLC
Task 2
Go to Network Connections; Right-click on the Wireless NIC; Click View
Wireless Networks; Select IT. Did you connect?
PC
Task 3
Open a command prompt. Type ipconfig. What IP address was assigned to the
wireless client?
PC
Task 4
Type tracert 192.168.20.2. What are the hops from the Wireless client to the
destination?
PC
Initial Setup:
Lab Task:
Task 1
Change the configuration of the IT WLAN to also ask for Web Authentication.
WLC
Task 2
Configure a local user with the following attributes:
Username : Khawar
Password : ccie12353
Allowed WLAN : IT
WLC
Task 3
Go to Network Connections; Right-click on the Wireless NIC; Click View
Wireless Networks; Select IT. Did you connect?
PC
Task 4
Open a command prompt. Type ipconfig. What IP address was assigned to the
wireless client?
PC
Task 5
Ping 192.168.10.1. Are you able to ping your default gateway? Why or Why
not?
PC
Task 6
Open your browser and browse to http://192.168.20.2. Does it ask for Web
Authentication? Type the Username credentials created in Task 2. Is the
authentication successful?
PC
Task 6
Ping 192.168.10.1. Are you able to ping your default gateway? Why or Why
not?
PC
Module 1 –
Configuring ISE to
Module 1 – Configuring ISE to
Communicate to Communicate to the Switch & WLC
the Switch & WLC Network Devices
Network Devices
R4
F 0/0 (.4)
192.1.40.0/24 VLAN 40
G 0/0 (.10) F 0/1 (.2) F 0/1 (.3)
R2 R3
F 0/1 (.10)
SW1 SW2
R1
F 0/0 (.1)
WiFi Enabled PC
(.15) (.16)
192.168.123.0/24 VLAN 123
(.35) (.100)
(.50)
Lab Scenario:
Initial Setup:
Configure the IP Addresses on the Routers based on the Diagram.
No shut
!
Router eigrp 100
No auto-summary
Network 192.168.10.0
Network 192.168.30.0
R4 ASA
Lab Tasks:
Task 1
Configure R1 as a DNS Server. It should resolve the following domain-names to
the IP:
Ise.abc.in : 192.168.123.254
R1.abc.in : 192.168.123.1
R1
IP DNS Server
!
IP host ise.ABC.in 192.168.123.35
IP host R1.ABC.in 192.168.123.1
Task 2
Configure R1 as the DHCP Server for VLAN 123. It should be configured with
the following parameters:
R1
Task 3
Configure R1 as the DHCP Server for VLAN 10. It should be configured with the
following parameters:
R1
Task 4
Configure R1 as the DHCP Server for VLAN 20. It should be configured with the
following parameters:
R1
Task 5
Configure R1 as the DHCP Server for VLAN 30. It should be configured with the
following parameters:
R1
Configuring Profiling
Creating Users
Initial Setup:
Lab Task:
Task 1
Open a Browser and browse to https://192.168.123.35. The Username of the
the ISE is admin. The Password was set to Kbits@123.
ISE
Task 2
Change the Deployment Mode to Primary.
ISE
Task 3
Update the Posture Database based on the offline method. The File for the
posture update should be located in the LabFiles Folder.
ISE
Task 4
Turn on Profiling on the ISE appliance for the following probes:
DHCP
DHCP SPAN
RADIUS
ISE
Task 5
Configure the following Endpoint & User Identity Groups on the ISE appliance:
ISE
Initial Setup:
Lab Task:
Task 1
Open the ISE Admin page and configure the SW1 as a Network Device using
cisco123 as the secret key.
ISE
Task 2
Open the ISE Admin page and configure the SW1 as a Network Device using
cisco123 as the secret key.
ISE
Task 3
Configure SW1 to communicate to ISE using RADIUS as the protocol and
cisco123 as the secret key. Also, configure the Switches with a local username
of admin with a password of admin. Configure a enable password of cisco. This
will be used by the ISE to Validate the Config for ISE.
SW1
Aaa new-model
Radius-server host 192.168.123.35 key cisco123
!
Username admin privilege 15 password admin
Copyrights KBITS Inc 2006-2020
Website: http://www.kbits.in; Email: [email protected]
Page 332 of 404
We will free Kashmir soon. Inshallah - Dawood Ibrahim Siddiqui (CCIE #28842)
Task 4
Configure SW2 to communicate to ISE using RADIUS as the protocol and
cisco123 as the secret key. Also, configure the Switches with a local username
of admin with a password of admin. Configure a enable password of cisco. This
will be used by the ISE to Validate the Config for ISE.
SW2
Aaa new-model
Radius-server host 192.168.123.35key cisco123
!
Username admin password admin
Enable secret cisco
Task 5
Use the Config Validation Operation Tool to telnet into SW1 and validate the
config. All the configuration that appears in red needs to be filled up. Use
notepad to do that and paste the config to SW1. Optionally, you can use the
Dot1x Switch config file that I have provided in the Labfiles folder.
ISE
Initial Setup:
Lab Task:
Task 1
Re-initialize the WLC if required by using the Recover-config command from
the CLI.
WLC
Recover-config
Task 2
Initialize the WLC based on the following parameters:
Hostname : WLC
Admin Username : admin
Admin Password : Cisco123
IP Address : 192.168.123.99
Subnet Mask : 255.255.255.0
Default Gateway : 192.168.123.1
Management VLAN : 123
Physical Interface : 1
Virtual-IP : 100.100.100.100
Mobility Group : MGMT
Management SSID : MGMT
Radio : Enable all Radio
Auto RF : Yes
NTP Server : N
Manual : Set it based on Local Time
Copyrights KBITS Inc 2006-2020
Website: http://www.kbits.in; Email: [email protected]
Page 334 of 404
We will free Kashmir soon. Inshallah - Dawood Ibrahim Siddiqui (CCIE #28842)
WLC
Task 3
Open a browser. Type https://192.168.123.99. Login using the administrator
name and password created in the previous step. Are you successful??
WLC
Task 4
In WLC, under the Security Menu, configure the WLC to communicate to ISE
(192.168.123.35) as the authentication and accounting server. Use cisco123
as the secret key.
WLC
Task 5
Open the ISE Admin page and configure the WLC as a Network Device using
cisco123 as the secret key.
ISE
Module 2 –
Configuring 802.1x Module 2 – Configuring 802.1x Using
Using ISE ISE
Lab Scenario:
Initial Setup:
Lab Task:
Task 1
Configure the Default Network Policy Results for authentication to support MS-
CHAP v2. Also, completely disable EAP-TLS for the policy (3 locations).
ISE
Task 2
Configure the following User Identities and assign them to the appropriate
groups:
ISE
Task 3
Under the Authentication page, Change the name of Dot1x Authentication to
Dot1x_Wired. Don’t change any other property. Save the Configuration
change.
ISE
Copyrights KBITS Inc 2006-2020
Website: http://www.kbits.in; Email: [email protected]
Page 337 of 404
We will free Kashmir soon. Inshallah - Dawood Ibrahim Siddiqui (CCIE #28842)
Task 4
Run the services.msc file from the Run menu. Make sure the WiredAutoConfig
service is running. This turns on the Dot1x service on the PC.
PC
Task 5
On the Wired Dot1x client machine, follow the instructions below to make sure
the device is ready for Dot1x authentication.
PC
Task 6
Bounce the LAN Adapter. (Disable and Enable). A ballon near the system tray
will ask ask you for additional credentials. Click on it and Log in using Sales1
as the username with a password of Cisco123. Did you connect??
PC
Task 7
Open the command prompt. Type IPCONFIG. What IP address was assigned to
the User?. It should be from the VLAN that was configured on the Switchport
(VLAN 100).
PC
Task 8
On SW2, type the Show authentication session command to verify the
authentication. You can also use the Show authentication session interface
F X/X to get more detailed information about the authentication.
SW2
Lab Scenario:
Initial Setup:
Lab Task:
Task 1
Configure the Authorization Policies Result sets to assign Users to VLANS.
Configure the following policies:
IT_WIRED_AUTH – VLAN – 10
SALES_WIRED_AUTH – VLAN – 20
MARK_WIRED_AUTH – VLAN – 30
ISE
Task 2
Configure the Authorization Policies based on the following:
Name : IT_DOT1X_WIRED
o Group : IT
o Authentication Type : Wired_802.1x
o Auth. Profile : IT_WIRED_AUTH
Name : SALES_DOT1X_WIRED
o Group : SALES
o Authentication Type : Wired_802.1x
o Auth. Profile : SALES_WIRED_AUTH
Name : MARK_DOT1X_WIRED
o Group : MARK
o Authentication Type : Wired_802.1x
o Auth. Profile : MARK_WIRED_AUTH
Copyrights KBITS Inc 2006-2020
Website: http://www.kbits.in; Email: [email protected]
Page 340 of 404
We will free Kashmir soon. Inshallah - Dawood Ibrahim Siddiqui (CCIE #28842)
ISE
Task 3
Bounce the LAN Adapter. (Disable and Enable). A ballon near the system tray
will ask ask you for additional credentials. Click on it and Log in using IT1 as
the username with a password of Cisco123. Did you connect??
PC
Task 4
Open the command prompt. Type IPCONFIG. What IP address was assigned to
the User?.
PC
Task 5
On SW2, type the Show authentication session command to verify the
authentication. You can also use the Show authentication session interface
F X/X to get more detailed information about the authentication. Also, check
to see the VLAN assignment to the port. Does it match the running config?
SW2
Task 6
Bounce the LAN Adapter. (Disable and Enable). A ballon near the system tray
will ask ask you for additional credentials. Click on it and Log in using Sales1
as the username with a password of Cisco123. Did you connect??
PC
Task 7
Open the command prompt. Type IPCONFIG. What IP address was assigned to
the User?
PC
Copyrights KBITS Inc 2006-2020
Website: http://www.kbits.in; Email: [email protected]
Page 341 of 404
We will free Kashmir soon. Inshallah - Dawood Ibrahim Siddiqui (CCIE #28842)
Task 8
On SW2, type the Show authentication session command to verify the
authentication. You can also use the Show authentication session interface
F X/X to get more detailed information about the authentication. Also, check
to see the VLAN assignment to the port. Does it match the running config?
SW2
Task 9
Bounce the LAN Adapter. (Disable and Enable). A ballon near the system tray
will ask ask you for additional credentials. Click on it and Log in using Mark1
as the username with a password of Cisco123. Did you connect??
PC
Task 10
Open the command prompt. Type IPCONFIG. What IP address was assigned to
the User?
PC
Task 11
On SW2, type the Show authentication session command to verify the
authentication. You can also use the Show authentication session interface
F X/X to get more detailed information about the authentication. Also, check
to see the VLAN assignment to the port. Does it match the running config?
SW2
Lab Scenario:
Initial Setup:
Lab Task:
Task 1
Configure the Authorization Policies Result DACLs to control User traffic.
Configure the following policies:
SALES_WIRED_DACL
o Deny icmp any host 192.168.123.16
o Permit ip any any
MARK_WIRED_DACL
o Deny ip any host 192.168.123.16
o Permit ip any any
ISE
Task 2
Configure/modify the Authorization Policies Result sets to control User traffic
based on DACL. Configure the following policies:
ISE
Task 3
Copyrights KBITS Inc 2006-2020
Website: http://www.kbits.in; Email: [email protected]
Page 343 of 404
We will free Kashmir soon. Inshallah - Dawood Ibrahim Siddiqui (CCIE #28842)
Bounce the LAN Adapter. (Disable and Enable). A ballon near the system tray
will ask ask you for additional credentials. Click on it and Log in using IT1 as
the username with a password of Cisco123. Did you connect??
PC
Task 4
Open the command prompt. Type Ping 192.168.123.16. Are you successful?
Use Putty to telnet to 192.168.123.16. Are you successful?
PC
Task 5
On SW2, type the Show authentication session command to verify the
authentication. You can also use the Show authentication session interface
F X/X to get more detailed information about the authentication.
SW2
Task 6
Bounce the LAN Adapter. (Disable and Enable). A ballon near the system tray
will ask ask you for additional credentials. Click on it and Log in using Sales1
as the username with a password of Cisco123. Did you connect??
PC
Task 7
Open the command prompt. Type Ping 192.168.123.16. Are you successful?
Use Putty to telnet to 192.168.123.16. Are you successful?
PC
Task 8
On SW2, type the Show authentication session command to verify the
authentication. You can also use the Show authentication session interface
Copyrights KBITS Inc 2006-2020
Website: http://www.kbits.in; Email: [email protected]
Page 344 of 404
We will free Kashmir soon. Inshallah - Dawood Ibrahim Siddiqui (CCIE #28842)
F X/X to get more detailed information about the authentication. Also, check
to see the VLAN & DACL assignment to the port. Does it match the running
config?
SW2
Task 9
Bounce the LAN Adapter. (Disable and Enable). A ballon near the system tray
will ask ask you for additional credentials. Click on it and Log in using Mark1
as the username with a password of Cisco123. Did you connect??
PC
Task 10
Open the command prompt. Type Ping 192.168.123.16. Are you successful?
Use Putty to telnet to 192.168.123.16. Are you successful?
PC
Task 11
On SW2, type the Show authentication session command to verify the
authentication. You can also use the Show authentication session interface
F X/X to get more detailed information about the authentication. Also, check
to see the VLAN & DACL assignment to the port. Does it match the running
config?
SW2
Initial Setup:
Lab Task:
Task 1
Configure a VLAN Interface for VLAN 10 based on the following parameters:
Interface Name : IT
VLAN : 10
Physical Interface : 2
IP Configuration
o IP Address : 192.168.10.99
o Subnet : 255.255.255.0
o Default Gateway : 192.168.10.10
DHCP Server : 192.168.10.1
WLC
Task 2
Configure a VLAN Interface for VLAN 20 based on the following parameters:
WLC
Task 3
Configure a VLAN Interface for VLAN 30 based on the following parameters:
WLC
Task 4
Configure a common WLAN for company that will use ISE for VLAN and
Interface assignment. Configure the WLAN based on the following:
WLC
Task 5
Under the Authentication page, Copy the Dot1x_Wired policy. Set the name of
the authentication policy to Dot1x_Wireless. Change the authentication
method condition to Wireless_802.1x. Leave the rest of the parameters the
same. Save the Policy.
ISE
Task 6
Configure the Authorization Policies Result sets to assign Wireless Users to
VLANS. Configure the following policies:
IT_WIRELESS_AUTH – VLAN – 10
SALES_WIRELESS_AUTH – VLAN – 20
MARK_WIRELESS_AUTH – VLAN – 30
ISE
Task 7
Configure the Authorization Policies based on the following:
Name : IT_DOT1X_WIRELESS
o Group : IT
o Authentication Type : Wireless_802.1x
o Auth. Profile : IT_WIRELESS_AUTH
Name : SALES_DOT1X_WIRELESS
o Group : SALES
o Authentication Type : Wireless_802.1x
o Auth. Profile : SALES_WIRELESS_AUTH
Name : MARK_DOT1X_WIRELESS
o Group : MARK
o Authentication Type : Wireless_802.1x
o Auth. Profile : MARK_WIRELESS_AUTH
ISE
Task 8
Go to Network Connections; Right-click on the Wireless NIC; Click View
Wireless Networks; Select ABC_ISE. Login in as IT1. Did you connect?
PC
Task 9
Open a command prompt. Type ipconfig. What IP address was assigned to the
wireless client?
PC
Copyrights KBITS Inc 2006-2020
Website: http://www.kbits.in; Email: [email protected]
Page 348 of 404
We will free Kashmir soon. Inshallah - Dawood Ibrahim Siddiqui (CCIE #28842)
Task 10
Open the Command prompt. Type tracert 192.168.30.3. What are the hops
from the Wireless client to the destination?
PC
Task 11
Bounce the Wireless NIC (Disable & Enable it). Right-click on the Wireless NIC;
Click View Wireless Networks; Select ABC_ISE. Login in as Sales1. Did you
connect?
PC
Task 12
Open a command prompt. Type ipconfig. What IP address was assigned to the
wireless client?
PC
Task 13
Open the Command prompt. Type tracert 192.168.30.3. What are the hops
from the Wireless client to the destination?
PC
Task 14
Bounce the Wireless NIC (Disable & Enable it). Right-click on the Wireless NIC;
Click View Wireless Networks; Select ABC_ISE. Login in as Mark1. Did you
connect?
PC
Task 15
Open a command prompt. Type ipconfig. What IP address was assigned to the
wireless client?
PC
Task 16
Open the Command prompt. Type tracert 192.168.20.2. What are the hops
from the Wireless client to the destination?
PC
Lab Scenario:
Initial Setup:
Lab Task:
Task 1
Under the Authentication page, Change the name of MAB Authentication to
MAB_Wired. Don’t change any other property. Save the Configuration change.
ISE
Task 2
Open the command prompt on the Wired Client PC. Type IPCONFIG /all. Find
out the MAC Address. Copy it into Notepad. Change the format to
XX:XX:XX:XX:XX:XX.
PC
Task 3
Add a Endpoint Identity in ISE. Use the MAC Address of the PC. Assign this
Endpoint to the ADMIN-PC endpoint group.
ISE
Task 4
Configure the Authorization Policy Result sets to assign the ADMIN_PC
Endpoint Group a specific VLAN. Configure the following policy:
Copyrights KBITS Inc 2006-2020
Website: http://www.kbits.in; Email: [email protected]
Page 351 of 404
We will free Kashmir soon. Inshallah - Dawood Ibrahim Siddiqui (CCIE #28842)
ADMIN_PC_WIRED_MAB – VLAN – 10
ISE
Task 5
Configure a new Authorization Policy based on the following:
Name : ADMIN_PC_WIRED_MAB
o Group : ADMIN_PC
o Authentication Type : Wired_MAB
o Auth. Profile : ADMIN_PC_WIRED_MAB
ISE
Task 6
Bounce the LAN Adapter. (Disable and Enable). A ballon near the system tray
will ask ask you for additional credentials. Do NOT put any credentials. Let me
fail to MAB. Check the Switch to make sure the Authentication is success
based on MAB using the Show authentication session interface F X/X
command.
PC
Task 7
Open the command prompt. Type IPCONFIG. What IP address was assigned to
the Device?
PC
Lab Scenario:
Initial Setup:
Lab Task:
Task 1
Under the Authentication page, copy the MAB_WIRED policy. Change the name
to MAB_Wireless. Change the Method to Wireless_MAB. Don’t change any
other property. Save the Configuration change.
ISE
Task 2
Open the command prompt on the Wireless Client PC. Type IPCONFIG /all.
Find out the MAC Address. Copy it into Notepad. Change the format to
XX:XX:XX:XX:XX:XX.
PC
Task 3
Add a Endpoint Identity in ISE. Use the MAC Address of the PC. Assign this
Endpoint to the ADMIN-PC endpoint group.
ISE
Task 4
Configure the Authorization Policy Result sets to assign the ADMIN_PC
Endpoint Group a specific VLAN. Configure the following policy:
ADMIN_PC_WIRELESS_MAB – VLAN – 10
ISE
Task 5
Configure a new Authorization Policy based on the following:
Name : ADMIN_PC_WIRELESS_MAB
o Group : ADMIN_PC
o Authentication Type : Wireless_MAB
o Auth. Profile : ADMIN_PC_WIRELESS_MAB
ISE
Task 6
Bounce the Wireless Adapter. (Disable and Enable). A ballon near the system
tray will ask ask you for additional credentials. Do NOT put any credentials.
Let me fail to MAB. Check the Switch to make sure the Authentication is
success based on MAB using the Show authentication session interface F
X/X command.
PC
Task 7
Open the command prompt. Type IPCONFIG. What IP address was assigned to
the Device?
PC
Lab Scenario:
Initial Setup:
Lab Task:
Task 1
Make sure the IP Phone has been profiled as a IP Phone.
PC
SW1
Task 7
Open the command prompt. Type IPCONFIG. What IP address was assigned to
the Device?
PC
Module 3 –
Configuring Posture
Module 3 – Configuring Posture
Validation Using Validation Using ISE
ISE
Lab Scenario:
Configure the Client Provisiong Resources for the NAC and Web Agents.
Initial Setup:
Lab Task:
Task 1
Add the Client files under the Policy Results for Client Provisioning resources.
ISE
Task 2
Configure a Client Provisioning Policy
ISE
Lab Scenario:
Initial Setup:
Lab Task:
Task 1
Configure the Policy Condition for Symantec
ISE
Task 2
Configure Posture Validaton for Windows PC based on Any Symantic Anit-virus
for the SALES group.
ISE
Task 3
Configure an Authorization Policy Result for the Pre-Auth VLAN with Posture
Validation. Configure the ACL on the Switch.
ISE
Task 4
Configure a Authorization policy for Pre-auth based on Compliant and Non-
compliant. Assign the Pre-Auth Result
ISE
Copyrights KBITS Inc 2006-2020
Website: http://www.kbits.in; Email: [email protected]
Page 358 of 404
We will free Kashmir soon. Inshallah - Dawood Ibrahim Siddiqui (CCIE #28842)
Task 5
Use the Existing Authorization Profile for SALES and change it to add a session
condition of compliant.
ISE
Task 6
Test on PC
ISE
Lab Scenario:
Initial Setup:
Lab Task:
Task 1
Configure the Policy Condition for Notepad under Application Condition
ISE
Task 2
Configure Posture Validaton for Windows PC based on running notepad.exe for
the MARK group.
ISE
Task 3
Use the Existing Authorization Profile for MARK and change it to add a session
condition of compliant.
ISE
Task 6
Test on PC
ISE
Module 4 –
Configuring
Module 4 – Configuring CiscoTrust Sec
CiscoTrust Sec with with SGT Exchange Protocol [SXP]
SGT Exchange
Protocol [SXP]
Lab Scenario:
Initial Setup:
Lab Task:
Task 1
Enable SXP Service on ISE.
ISE
Administration -> System -> Deployment -> Node -> Policy Service ->
Enable SXP Service
Task 2
Configure cisco123 as the Global Password that will be used in the SXP
relationships.
ISE
Task 3
Configure a relationship between the WLC and ISE. WLC should be configured
as a speaker and ISE should be configured as a Listener.
ISE
Work Center -> TrustSec -> SXP -> SXP Devices -> Add
Name : WLC
IP Address: 192.168.123.99
Peer Role: Speaker
Connected PSN : ISE
Password : Default
Version : v4
Select : Enabled
Password : cisco123
Apply
Task 4
Configure a relationship between the ASA Firewall and ISE. ASA should be
configured as a Listener and ISE should be configured as a Speaker.
ISE
Work Center -> TrustSec -> SXP -> SXP Devices -> Add
Name : ASA
IP Address: 192.168.10.10
Peer Role: Listener
Connected PSN : ISE
Password : Default
Version : v4
ASA
Lab Scenario:
Initial Setup:
Lab Task:
Task 1
Configure SGT Configration settings on ISE based on the following information:
ISE
Auto-Naming Options
Task 2
Re-create the Wireless Authorization Policies by duplicating them. Copy to Re-
create policies for MARK & SALES. It should automatically create the SGTs.
Rename the rules to the following:
SXP-MARK-WIRELESS.
SXP-SALES-WIRELESS.
Copyrights KBITS Inc 2006-2020
Website: http://www.kbits.in; Email: [email protected]
Page 366 of 404
We will free Kashmir soon. Inshallah - Dawood Ibrahim Siddiqui (CCIE #28842)
ISE
Task 3
Delete the Old Wireless Rules.
ISE
Initial Setup:
Lab Task:
Task 1
Find the SGT Mapping for SALES and MARK Wireless Authorized Users on ISE.
ISE
Task 2
Configure an ACL on the ASA Firewall based on the following information:
ASA
Task 3
Test on PC
ISE
Module 5 –
Configuring ISE for
Module 1 – Configuring ISE for Device
Device Administration
Administration
Lab Scenario:
Initial Setup:
Based on the previous Lab
Lab Tasks:
Task 1
Enable the Device Administration Service on ISE.
ISE
Task 2
Configure R1 and SW2 as clients to the ACS Server. R1 & SW1 should use
TACACS+ as the authentication protocol. Both should use cisco123 as the
secret key.
ISE
Task 3
Configure the following grousp on ISE:
ISE
Task 4
Create users on ISE based on the following:
ISE
Task 5
Configure R1 and SW2 to communicate with the ACS server for authentication.
Use the key and address in Task 1.
R1
Aaa new-model
Tacacs-server host 192.168.123.35 key cisco123
** do test aaa group tacacs Admin1 Admin1 legacy.
** This command verifies that the ISE is communicating to the
device
SW2
Aaa new-model
Tacacs-server host 192.168.123.35 key cisco123
** do test aaa group tacacs Admin1 Admin1 legacy.
** This command verifies that the ISE is communicating to the
device
Initial Setup:
Lab Task:
Task 1
Configure a Shell Profile that assigns a default privilege level of 15.
ISE
Task 2
Configure 3 Shell Command Authorization sets on the ACS with the following
commands and capabilities:
RP-ADMINS
o Configure terminal
o Router RIP (Only allow him to enable RIP as a Routing Protocol)
o Execute the Network command for any network
o Execute the Version command; Limit it version 2 only
o Execute the no auto-summary command
Sec-ADMINS
o Configure Terminal
o Any Crypto command with any Arguments
o Authentication command with any Arguments
o Encryption command ; Limit it to 3des only
o Hash command with any Arguments
o Group command ; Limit it to 2 only
o Access-list command with any Arguments
o set command with any Arguments
Copyrights KBITS Inc 2006-2020
Website: http://www.kbits.in; Email: [email protected]
Page 373 of 404
We will free Kashmir soon. Inshallah - Dawood Ibrahim Siddiqui (CCIE #28842)
Super-Admins
o Should be allowed all commands.
ISE
Lab Scenario:
Initial Setup:
Lab Task:
Task 1
Configure R1 & SW2 to use ISE for login authentication. Create a local
username with a username of admin with a password of admin. Assign the
local user a privilege levelof 15. Use a Named-list called T-AUTHEN. T-AUTHEN
should use the TACACS+ as the primary authentication choice and Local
Database for fallback authentication.
R1
Task 2
Configure R1 & SW2 to use ISE for Exec authorization. Use a Named-list called
T-AUTHOR. T-AUTHOR should use the TACACS+ as the primary Exec
authorization choice and Local Database for fallback authentication.
R1
SW2
Task 3
Configure R1 & SW2 to use ISE for Command authorization for Level 15
commands. Use a Named-list called T-AUTHOR. T-AUTHOR should use the
TACACS+ as the primary authorization choice for Level 15 commands.
R1
Task 4
Verify the above configured Device administration by Telnetting into R1 & SW2
using the 3 users above.
Module 1 – Initial
Configuration of
Module 1 – Initial Configuration of the
the Web Security Web Filtering Appliance [WSA]
Appliance [WSA]
PC-2
WSA
PC-1 F 0/1 (.2)
R2
M1 (.45) (.50) F 0/0 (.2)
192.168.140.0/24 VLAN 140
ASA R1
F 0/0 (.1)
E 0/0 (.10)
192.1.100.0/24 VLAN 100
F 0/0 (.3)
R3
Lab Scenario:
Initial Setup:
Configure PC-1 & PC-2 with the IP Addresses based on the Diagram. Point
PC-1’s default gateway towards the Firewall. Point PC-2’s default gateway
towards the inside of R2.
Point R2’s default gateway towards R1’s inside interface. Also, point R1
and the Firewall’s default gateway towards R3.
R2
Interface F 0/0
ip address 192.168.140.2 255.255.255.0
no shut
!
Interface F 0/1
ip address 192.168.20.2 255.255.255.0
no shut
!
ip route 0.0.0.0 0.0.0.0 192.168.140.1
R3
Int F 0/0
Ip add 192.1.100.3 255.255.255.0
No shut
!
Ip route 192.168.20.0 255.255.255.0 192.1.100.1
Ip route 192.168.140.0 255.255.255.0 192.1.100.10
!
Ip dns server
Ip host www.facebook.com 192.1.100.3
Ip host www.xxx.com 192.1.100.3
Ip host espn.com 192.1.100.3
Ip host cnn.com 192.1.100.3
!
Clock timezone IST 5 30
Do Clock set 20:30:00 20 April 2013
Ntp master 2
!
Ip http server
FW
Interface E 0/0
Nameif outside
Ip add 192.1.100.10 255.255.255.0
No shut
!
Interface E 0/1
Nameif Inside
Ip add 192.68.140.10 255.255.255.0
No shut
!
Ip route 0.0.0.0 0.0.0.0 192.1.100.3
Lab Tasks:
Task 1
Iniatialize the WSA (Ironport) device using the following parameters:
Hostname : wsa.ABC.in
Dns Server : 192.1.100.3
NTP Server : 192.1.100.3
IP Configuration : 192.168.140.50/24
Default Gateway : 192.168.140.1
Web Cache Transparent device Configuration:
o Web cache Service port : 0
o Router Address : 192.168.140.1
o Password : cciesec
Administrative Password : ironport
System Alert e-mail : [email protected]
SMTP Server : 192.168.140.125
WSA
Configure the WCCP Service on the Firewall to communicate with the WSA
appliance.
Initial Setup:
Lab Task:
Task 1
Configure the Firewall to communicate with the WSA based on WCCP. The
WSA has been configured to communicate to the Firewall with a service id of 5
and a password of cciesec. The IP Address of the WSA is 192.168.140.50. The
Firewall should forward all web traffic from the 192.168.140.0/24 network
towards the WSA.
ASA
Task 2
All Web traffic coming into the inside interface of the ASA should be redirected
towards the WSA.
ASA
Configure the WCCP Service on the Router to communicate with the WSA
appliance.
Initial Setup:
Lab Tasks:
Task 1
Configure the Router to communicate with the WSA located using the following
information:
WCCP Version : 2
WSA Address : 192.168.140.50
Service ID : Web-cache
Web Redirect Traffic : Source : 192.168.20.0/24 Port : 80
Password : cciesec
R1
Ip wccp version 2
!
Access-list 1 permit host 192.168.140.50
Access-list 101 permit ip 192.168.20.0 0.0.0.255 any
!
Ip wccp web-cache group-list 1 redirect-list 101 password cciesecc
Task 2
All Web traffic coming into the inside interface of the Router should be
redirected towards the WSA.
R1
Interface F 0/1
Ip Wccp web-cache redirect in
Task 3
Configure the WSA to communicate to the Router based on the parameters
configured in the previous step.
WSA
Module 2 –
Configuring Web
Module 2 – Configuring Web Filtering
Filtering Using WSA Using WSA
Lab Scenario:
Initial Setup:
Lab Task:
Task 1
Configure the following Identities on the WSA:
WSA
Lab Scenario:
Initial Setup:
Lab Task:
Task 1
Configure the WSA to block the following categories for the VLAN140 Identity:
Adult
Alcohol & Tobacco
Child Porn
Dating
Gambling
Online Trading
Porn
Tasteless Or Obscene
Social Networking
Streaming Media
Shopping
Sports and Recreation
WSA
Task 2
Configure the WSA to block the following categories for the VLAN20 Identity:
Adult
Alcohol & Tobacco
Child Porn
Dating
Gambling
Porn
Tasteless Or Obscene
Streaming Media
Shopping
Sports and Recreation
WSA
Task 3
Open the browser on PC-1. Type in http://www.facebook.com. Are you able to
browse?
PC-1
Task 4
Open the browser on PC-2. Type in http://www.facebook.com. Are you able to
browse?
PC-2
Task 5
Open the browser on PC-1. Type in http://espn.com. Are you able to browse?
PC-1
Task 6
Open the browser on PC-2. Type in http://espn.com. Are you able to browse?
PC-2
Initial Setup:
Lab Task:
Task 1
Open the browser on PC-2. Type in http://cnn.com. Are you able to browse?
PC-2
Task 2
Open the browser on PC-2. Type in http://192.1.100.3. Are you able to
browse?
PC-1
Task 3
Configue a Custom Global Black List that will always block the following
Websites for VLAN20:
Cnn.com
192.1.100.3
Juniper.com
WSA
Task 4
Configue a Custom White List that will always allow access to the following
Websites for VLAN20:
cisco.com
espn.com
ABC.in
WSA
Task 5
Open the browser on PC-2. Type in http://espn.com. Are you able to browse?
PC-2
Task 6
Open the browser on PC-2. Type in http://192.1.100.3. Are you able to
browse?
PC-2
Initial Setup:
Lab Task:
Task 1
Open the browser on PC-1. Type in http://www.facebook.com. Are you able to
browse?
PC-1
Task 2
Configure a policy that is similar to the the policy for VLAN140 except that they
should be allowed to access Social Networking and Sports & Recreational
categories. Make sure this policy get’s precedence over the VLAN 140 policy.
WSA
Lab Scenario:
Initial Setup:
Lab Task:
Task 1
Define a Time Range named WORK_HOURS based on the following:
WSA
Task 2
Open the browser on PC-2. Type in http://www.facebook.com. Are you able to
browse?
PC-2
Task 3
Configure the policy for VLAN20 to block Social Networking sites during work
hours.
WSA
Module 1 – Initial
Configuration of
Module 1 – Initial Configuration of the
the E-Mail Security E-Mail Security Appliance [ESA]
Appliance [ESA]
E-Mail
Server &
Mail Client
192.1.20.0/24 VLAN 20
G 0/1 (.10)
R2
G 0/0 (.10)
192.168..1.0/24 VLAN 10
(.101) (.213)
M (.51)
Lab Scenario:
Initial Setup:
Configure PC-1 & PC-2 with the IP Addresses based on the Diagram.
R2
Interface F 0/0
ip address 192.1.20.2 255.255.255.0
no shut
!
Interface F 0/1
ip address 192.168.1.2 255.255.255.0
no shut
Lab Tasks:
Task 1
Configure/Verify the DNS Server configuration. It should have the following
Domains and Entries:
Domain: homesecurity.com
o PC1 – Host [A] – 192.168.1.101
o IMAP – Host [A] – 192.168.1.101
o SMTP – Host [A] – 192.168.1.101
o Homesecurity.com – MX – SMTP.homesecurity.com [10]
Domain: ciscosecurity.com
o PC1 – Host [A] – 192.1.20.101
o IMAP – Host [A] – 192.1.20.101
o SMTP – Host [A] – 192.1.20.101
o ciscosecurity.com – MX – SMTP.ciscosecurity.com [10]
DNS
Task 2
Configure/Verify the Internal E-mail Server [Homesecurity.com] and Client
Communications based on the following:
Domain: homesecurity.com
o Account : [email protected] Password: Cisco123
o Account : [email protected] Password: Cisco123
Internal Server/PC
Task 3
Configure/Verify the External E-mail Server [Ciscosecurity.com] and Client
Communications based on the following:
Domain: homesecurity.com
o Account : [email protected] Password: Cisco123
o Account : [email protected] Password: Cisco123
External Server/PC
Task 4
Verify the E-Mail setup by sending and receiving E-mails internally and
externally.
Internal Server/PC
Lab Scenario:
Initial Setup:
Lab Tasks:
Task 1
Log into the ESA from the CLI using the default Username of admin and the
default password of ironport.
Task 2
Use the “Interfaceconfig” command to initialize the AS from the CLI using the
following parameters:
Interface : Management
IP Configuration : 192.168.1.51/24
Hostname : ESA.Homesecurity.com
Take the default for all the configuration settings.
ESA
Run the System Setup Wizard to Initialize the ESA from the GUI.
Initial Setup:
Lab Tasks:
Task 1
Run the System Setup Wizard from “System Administration -> System Setup
Wizard”. Use the following information in the Wizard:
ESA
Initial Setup:
Lab Tasks:
Task 1
Configure a Relay Mail Policy to allow ESA to forward messages for the Internal
SMTP Server [smtp.homesecurity.com] using the following Information:
ESA
Task 2
Configure a Sender Group for the HAT Policy to allow the Internal Mail Server
to relay messages:
Name: RELAYLIST
Policy: RELAYED
Server IP: 192.168.1.101
ESA
Task 3
Move the Relay list to the Top of the HAT List
ESA
Task 4
Change the DNS Server Entry for the SMTP Server to the ESA IP Address.
DNS
Task 5
Configure the Internal Server to use the ESA as the SMTP Relay Agent.
E-Mail Server
Task 6
Use the “Tail” command on the ESA to enable Mail Loggin.
ESA
Task 7
Send an e-mail from the Internal E-mail server to the External E-mail. Verify
that the e-mail is getting relayed thru the ESA by checking the logs of the ESA
that were turned on in the previous task.
Module 2 –
Configuring E-Mail
Module 2 – Configuring E-Mail Filtering
Filtering Using ESA Using ESA
Lab Scenario:
Initial Setup:
Lab Task:
Task 1
Configure the following Outgoing Content Filters:
Drop any message that has Credit Card or ABA Routing Numbers.
Bcc any message to [email protected] that has the word
“resume” in the content.
Strip any attachment that has an office document attachment with a
macro in it.
ESA
Task 2
Apply this filter to the default Outgoing Filter
ESA
Lab Scenario:
Initial Setup:
Lab Task:
Task 1
Configure the following Incoming Content Filters:
Bounce any message that has has the word “attack” in the content.
Drop any message that has an attachment greater than 8 MB.
ESA
Task 2
Apply this filter to the default Incoming Filter
ESA