Click OK in the Commands Delivery Status window.
g. Click OK in the Commands Delivery Status window.
h. Open a console connection to the router, and verify the associations and time on R1 after it has made an association with R2. It might take some time for the NTP association to form. R1 show ntp associations address ref clock st when poll reach delay offset disp ~10.1.1.2 127.127.1.1 3 14 64 3 0.000 -280073 3939.7 sys.peer, selected, +candidate, -outlyer, x falseticker, ~ configured R1 show clock 20:12:24.859 UTC Wed Dec 17 2008 Task 3: Configure syslog Support on R1 and PC-A Step 1: Install the syslog server. The Kiwi Syslog Daemon is a dedicated syslog server. Another application is Tftpd32, which includes a TFTP server, TFTP client, and a syslog server and viewer. You can use either with this lab. Both are available as a free version and run with Microsoft Windows. If a syslog server is not currently installed on the host, download the latest version of Kiwi from http:www.kiwisyslog.com or Tftpd32 from http:tftpd32.jounin.net and install it on your desktop. If it is already installed, go to Step 2. Note: This lab uses the Kiwi syslog server. Step 2: Configure R1 to log messages to the syslog server using the CLI. a. Verify that you have connectivity between R1 and the host by pinging the R1 Fa01 interface IP address 192.168.1.1. If it is not successful, troubleshoot as necessary before continuing. b. NTP was configured in Task 2 to synchronize the time on the network. Displaying the correct time and date in syslog messages is vital when using syslog to monitor a network. If the correct time and date of a message is not known, it can be difficult to determine what network event caused the message. Verify that the timestamp service for logging is enabled on the router using the show run command. Use the following command if the timestamp service is not enabled. R1config service timestamps log datetime msec c. Configure the syslog service on the router to send syslog messages to the syslog server. R1config logging host 192.168.1.3 Step 3: Configure the logging severity level on R1. Logging traps can be set to support the logging function. A trap is a threshold that when reached triggers a log message. The level of logging messages can be adjusted to allow the administrator to determine what kinds of messages are sent to the syslog server. Routers support different levels of logging. The eight levels range from 0 emergencies, indicating that the system is unstable, to 7 debugging, which sends messages that include router information. CCNA Security All contents are Copyright © 1992 –2012 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 27 of 57 Note: The default level for syslog is 6, informational logging. The default for console and monitor logging is 7, debugging.a. Use the logging trap command to determine the options for the command and the various trap
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