[CCNAv6 S2] 10.2.3.5 Packet Tracer - Configuring Syslog and NTP



Packet Tracer – Configuring Syslog and NTP
Objectives

Part 1: Configure Syslog Service

Part 2: Generate Logged Events

Part 3: Manually Set Switch Clocks

Part 4: Configure NTP Service

Part 5: Verify Timestamped Logs

Scenario

In this activity, you will enable and use the Syslog service and the NTP service so that the network administrator is able to monitor the network more effectively.

Part 1:     Configure Syslog Service
Step 1:     Enable the Syslog service.

a.     Click Syslog, then Services tab.

b.    Turn the Syslog service on and move the window so you can monitor activity.

Step 2:     Configure the intermediary devices to use the Syslog service.

a.     Configure R1 to send log events to the Syslog server.

R1(config)# logging 10.0.1.254
b.    Configure S1 to send log events to the Syslog server.

c.     Configure S2 to send log events to the Syslog server.

Part 2:     Generate Logged Events
Step 1:     Change the status of interfaces to create event logs.

a.     Configure a Loopback 0 interface on R1 then disable it.

b.    Turn off PC1 and PC2. Turn them on again.

Step 2:     Examine the Syslog events.

a.     Look at the Syslog events. Note: All of the events have been recorded; however, the time stamps are incorrect.

b.    Clear the log before proceeding to the next part.

Part 3:     Manually Set Switch Clocks
Step 1:     Manually set the clocks on the switches.

Manually set the clock on S1 and S2 to the current date and approximate time. An example is provided.

S1# clock set 11:47:00 July 10 2013
Step 2:     Enable the logging timestamp service on the switches.

Configure S1 and S2 to send its timestamp with logs it sends to the Syslog server.

S1(config)# service timestamps log datetime msec
Part 4:     Configure NTP Service
Step 1:     Enable the NTP service.

In this activity, we are assuming that the NTP service is being hosted on a public Internet server. If the NTP server was private, authentication could also be used.

a.     Open the Services tab of the NTP server.

b.    Turn the NTP service on and note the date and time that is displayed.

Step 2:     Automatically set the clock on the router.

Set the clock on R1 to the date and time according to the NTP server.

R1(config)# ntp server 64.103.224.2
Step 3:     Enable the logging timestamp service of the router.

Configure R1 to send its timestamp with the logs that it sends to the Syslog server.

Part 5:     Verify Timestamped Logs
Step 1:     Change the status of interfaces to create event logs.

a.     Re-enable and then disable the Loopback 0 interface on R1.

b.    Turn off laptops L1 and L2. Turn them on again.

Step 2:     Examine the Syslog events.

Look at the Syslog events. Note: All of the events have been recorded and the time stamps are correct as configured. Note: R1 uses the clock settings from the NTP server, and S1 and S2 use the clock settings configured by you in Part 3.



Configuration SYSLOG:




Configuration NTP:




Configuration R1:

enable
configure terminal
logging 10.0.1.254
ntp server 64.103.224.2
service timestamps log datetime msec
end
write memory
!

Configuration S1:

enable
configure terminal
logging 10.0.1.254
clock set 11:47:00 July 10 2013
service timestamps log datetime msec
end
write memory
!

Configuration S2:

enable
configure terminal
logging 10.0.1.254
clock set 11:47:00 July 10 2013
service timestamps log datetime msec
end
write memory
!

Nhận xét

Đăng nhận xét

Bài đăng phổ biến từ blog này

[CCNAv6 S4] 8.2.4.14 Packet Tracer - Troubleshooting Enterprise Networks 3

Hình ảnh
Packet Tracer – Troubleshooting Enterprise Networks 3 Addressing Table Background This activity uses a variety of technologies you have encountered during your CCNA studies, including routing, port security, EtherChannel, DHCP, NAT, PPP, and Frame Relay. Your task is to review the requirements, isolate and resolve any issues, and then document the steps you took to verify the requirements. Note: This activity begins with a partial score. Requirements DHCP ·         R1 is the DHCP server for the R1 LAN. Switching Technologies ·         Port security is configured to only allow PC1 to access S1's F0/3 interface. All violations should disable the interface. ·         Link aggregation using EtherChannel is configured on S2, S3, and S4. Routing ·         All routers are configured with OSPF process ID 1 and no routing updates should be sent across interfaces that do n...
Đọc thêm

[CCNAv6 S2] 2.2.2.4 Packet Tracer - Configuring IPv4 Static and Default Routes

Hình ảnh
Packet Tracer - Configuring IPv4 Static and Default Routes Addressing Table Objectives Part 1: Examine the Network and Evaluate the Need for Static Routing Part 2: Configure Static and Default Routes Part 3: Verify Connectivity Background In this activity, you will configure static and default routes. A static route is a route that is entered manually by the network administrator to create a reliable and safe route. There are four different static routes that are used in this activity: a recursive static route, a directly attached static route, a fully specified static route, and a default route. Part 1:     Examine the Network and Evaluate the Need for Static Routing a.     Looking at the topology diagram, how many networks are there in total? b.    How many networks are directly connected to R1, R2, and R3? c.     How many static routes are required by each router to reach networks that are not directly ...
Đọc thêm

[CCNAv6 S2] 7.3.2.4 Packet Tracer - Troubleshooting Standard IPv4 ACLs

Hình ảnh
Packet Tracer – Troubleshooting Standard IPv4 ACLs Addressing Table Objectives Part 1: Troubleshoot ACL Issue 1 Part 2: Troubleshoot ACL Issue 2 Part 3: Troubleshoot ACL Issue 3 Scenario This network is meant to have the following three policies implemented: ·         Hosts from the 192.168.0.0/24 network are unable to access network 10.0.0.0/8. ·         L3 can’t access any devices in network 192.168.0.0/24. ·         L3 can’t access Server1 or Server2. L3 should only access Server3. ·         Hosts from the 172.16.0.0/16 network have full access to Server1, Server2 and Server3. Note: All FTP usernames and passwords are “cisco”. No other restrictions should be in place. Unfortunately, the rules that have been implemented are not working correctly. Your task is to find and fix the errors related to the access lists on R1. Part 1:     Troublesh...
Đọc thêm