Issue the show crypto isakmp sa command again. Issue the show crypto ipsec sa command. How many packets have been transformed between
b. Issue the show crypto isakmp sa command again.
R1 show crypto isakmp sa IPv4 Crypto ISAKMP SA dst src state conn-id slot status 10.2.2.1 10.1.1.1 QM_IDLE 1001 0 ACTIVE c. Why was an SA created between R1 and R3 this time? The source was 192.168.1.1, and the destination was 192.168.3.1. This is interesting traffic based on the ACL 101 definition. An SA is established, and packets travel through the tunnel as encrypted traffic. d. What are the endpoints of the IPsec VPN tunnel? Src: 10.1.1.1 R1 S000, Dst: 10.2.2.1 R3 S001. e. Ping from PC-A to PC-C. Were the pings successful? Yes.f. Issue the show crypto ipsec sa command. How many packets have been transformed between
R1 and R3? Nine: five packets from the R1 to R3 pings, four packets from the PC-A to R3 pings, and one packet for each echo request. The number of packet may vary depending on how many pings have been issued and from where. R1 show crypto ipsec sa interface: Serial000 Crypto map tag: CMAP, local addr 10.1.1.1 protected vrf: none local ident addrmaskprotport: 192.168.1.0255.255.255.000 remote ident addrmaskprotport: 192.168.3.0255.255.255.000 current_peer 10.2.2.1 port 500 PERMIT, flags={origin_is_acl,} pkts encaps: 9, pkts encrypt: 9, pkts digest: 9 pkts decaps: 9, pkts decrypt: 9, pkts verify: 9 pkts compressed: 0, pkts decompressed: 0 pkts not compressed: 0, pkts compr. failed: 0 pkts not decompressed: 0, pkts decompress failed: 0 send errors 0, recv errors 0 local crypto endpt.: 10.1.1.1, remote crypto endpt.: 10.2.2.1 path mtu 1500, ip mtu 1500, ip mtu idb Serial000 current outbound spi: 0xC1DD058203280472 inbound esp sas: spi: 0xDF57120F3747025423 transform: esp-256-aes esp-sha-hmac , in use settings ={Tunnel, } conn id: 2005, flow_id: FPGA:5, crypto map: CMAP sa timing: remaining key lifetime ksec: 4485195877 IV size: 16 bytes replay detection support: Y Status: ACTIVE inbound ah sas: inbound pcp sas: outbound esp sas: spi: 0xC1DD058203280472 transform: esp-256-aes esp-sha-hmac , in use settings ={Tunnel, } CCNA Security All contents are Copyright © 1992 –2012 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 15 of 40 conn id: 2006, flow_id: FPGA:6, crypto map: CMAP sa timing: remaining key lifetime ksec: 4485195877 IV size: 16 bytes replay detection support: Y Status: ACTIVE outbound ah sas: outbound pcp sas: g. The previous example used pings to generate interesting traffic. What other types of traffic would result in an SA forming and tunnel establishment? Any traffic initiated from R1 with a source address in the 192.168.1.024 network and a destination address in the 192.168.3.024 network. On R3, interesting traffic is any traffic with a source address in the 192.168.3.024 network and a destination address in the 192.168.1.024 network. This includes FTP, HTTP, Telnet, and others. Part 3: Configure a Site-to-Site IPsec VPN with CCP In Part 3 of this lab, configure an IPsec VPN tunnel between R1 and R3 that passes through R2. Task 1 will restore the router to the basic settings using your saved configurations. In task 2, configure R1 using Cisco CCP. In Task 3, mirror those settings to R3 using CCP utilities. Finally, review and test the resulting configuration. Task 1: Restore Router R1 and R3 to the Basic Settings To avoid confusion as to what was entered in Part 2 of the lab, start by restoring R1 and R3 to the basic configuration as described in Part 1 of this lab. Step 1: Erase and reload the router. a. Connect to the router console, and enter privileged EXEC mode. b. Erase the startup config and then issue the reload command to restart the router. Step 2: Restore the basic configuration. a. When the router restarts, enter privileged EXEC mode with the enable command, and then enter global config mode. Use the HyperTerminal Transfer Send File function, copy and paste, or use another method to load the basic startup config for R1 and R3 that was created and saved in Part 1 of this lab.b. Save the running config to the startup config for R1 and R3 using the copy run start command.
Parts
» CCNA Security 1.1 Instructor Lab Manual
» Lab A: Researching Network Attacks and Security Audit Tools
» Lab A: Securing the Router for Administrative Access
» Use the username command to create the user ID with the highest possible privilege level and a
» Issue the undebug all or the no debug ntp all command to turn off debugging.
» Click OK in the Commands Delivery Status window.
» Use the show logging command to see the type and level of logging enabled.
» Save the running config to the startup config using the copy run start command.
» Lab A: Securing Administrative Access Using AAA and RADIUS
» Click Send and you should see a Send Access_Request message indicating the server at
» Clear the log on the WinRadius server by choosing Log Clear from the main menu.
» Lab A: Configuring CBAC and Zone-Based Firewalls
» Issue the show run command to review the current basic configuration on R1.
» Display the Extended ACL named autosec_firewall_acl, which is applied to S000 inbound.
» Display the Extended ACL named autosec_firewall_acl that is applied to S000 inbound.
» Click Finish to complete the Firewall wizard.
» Lab A: Configuring an Intrusion Prevention System IPS Using the CLI and CCP
» From the R1 CLI, verify that the directory is present using the dir flash: or dir flash:ipsdir
» Apply the IPS rule to an interface with the ip ips name direction command in interface
» Verify connectivity between R1 and PC-A, the TFTP server, using the ping command.
» Use the show ip ips all command to see an IPS configuration status summary. To which
» For Protocol, select tftp from the drop-down menu. Enter the IP address of the PC-C TFTP server
» Lab A: Securing Layer 2 Switches Instructor Version
» From the router R1 CLI, use the show interface command and record the MAC address of the
» Set the SPAN source interface using the monitor session command in global configuration mode.
» Lab A: Exploring Encryption Methods Instructor
» Lab A: Configuring a Site-to-Site VPN Using Cisco IOS and CCP
» Verify the IKE policy with the show crypto isakmp policy command.
» Save the running config to the startup config for R1 and R3 using the copy run start command.
» Click the Launch the selected task button to begin the CCP Site-to-Site VPN wizard.
» Lab B: Configuring a Remote Access VPN Server and Client
» In the Command Delivery Status window, click OK. How many commands are delivered? 103 with
» Lab C Optional: Configuring a Remote Access VPN Server and Client
» Lab A: Security Policy Development and Implementation
» Verify that R1 and R3 have made an association with R2 using the show ntp associations
» Choose FastEthernet 01 as the Inside Trusted interface and Serial 001 as the Outside Untrusted
» From PC-A, Telnet to R2 at IP address 10.1.1.2 using the vty line password ciscovtypass.
» If the ipsdir directory is not listed, create it.
» Secure the router running configuration and securely archive it in persistent storage flash.
» Lab A: Configuring ASA Basic Settings and Firewall Using CLI
» Display the ASA file system using the show file system command to determine what prefixes are
» Display the current running configuration using the show running-config command.
» You can configure the ASA to accept HTTPS connections using the http command. This allows
» Issue the show route command to display the ASA routing table and the static default route just
» Save the RSA keys to persistent flash memory using either the copy run start or write mem
» Lab B: Configuring ASA Basic Settings and Firewall Using ASDM
» View this Access Rule in ASDM by choosing Configuration Firewall Access Rules. It appears
» Lab C: Configuring Clientless and AnyConnect Remote Access SSL VPNs Using ASDM
» Enable HTTP access to R1 using the ip http server command in global config mode. Also set
» From the Add Bookmark List window, click Add to open the Add Bookmark window. Enter Web Mail as
» Lab D: Configuring a Site-to-Site IPsec VPN Using CCP and ASDM
» Use the reload command to restart the ASA. This will cause the ASA to come up in CLI Setup
» In the Peer Identity section, select Peer with static IP address and enter the IP address of the
Show more