There was a summary warning log message indicating a

This preview shows page 7 - 10 out of 14 pages.

____________________________________________________________________________________ ____________________________________________________________________________________ ____________________________________________________________________________________ ____________________________________________________________________________________ There was a summary warning log message indicating a change in the interface state. The addition of the interface was not enough to trigger and send more detailed informational messages to the syslog server at level 4. e. Change the logging severity level to 6. R2(config)# logging trap informational or R2(config)# logging trap 6 f. Clear the syslog entries on PC-B. Click Clearin the Tftpd32 dialog box. g. Create the Loopback 1 interface on R2. R2(config)# interface lo 1Jul 5 10:05:46.650: %LINK-3-UPDOWN: Interface Loopback1, changed state to up Jul 5 10:05:47.650: %LINEPROTO-5-UPDOWN: Line protocol on Interface Loopback1, changed state to uph. Remove the Loopback 1 interface from R2. R2(config-if)# no interface lo 1
Lab Configuring Syslog and NTP © 2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 8of 14R2(config-if)#Jul 5 10:08:29.742: %LINK-5-CHANGED: Interface Loopback1, changed state to administratively down Jul 5 10:08:30.742: %LINEPROTO-5-UPDOWN: Line protocol on Interface Loopback1, changed state to down i. Observe the syslog server output. Compare this result with the results at trapping level 4. What is your observation? ____________________________________________________________________________________ ____________________________________________________________________________________ ____________________________________________________________________________________ More log messages were trapped when the severity was set to 6 (informational) than when it was set at 4 (warnings). Reflection What is the problem with setting the level of severity too high (lowest level number) or too low (highest level number) for syslog? _______________________________________________________________________________________ _______________________________________________________________________________________ _______________________________________________________________________________________ When the severity level is set too high (lowest level number), the generated log could be missing important, but not critical messages. However, setting it too low (highest level number), it can generate too many entries and fill the logs with unnecessary information.
Lab Configuring Syslog and NTP © 2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 9of 14Router Interface Summary Table Router Interface Summary Router Model Ethernet Interface #1 Ethernet Interface #2 Serial Interface #1 Serial Interface #2 1800 Fast Ethernet 0/0 (F0/0) Fast Ethernet 0/1 (F0/1) Serial 0/0/0 (S0/0/0) Serial 0/0/1 (S0/0/1) 1900 Gigabit Ethernet 0/0 (G0/0) Gigabit Ethernet 0/1 (G0/1) Serial 0/0/0 (S0/0/0) Serial 0/0/1 (S0/0/1) 2801 Fast Ethernet 0/0 (F0/0) Fast Ethernet 0/1 (F0/1) Serial 0/1/0 (S0/1/0) Serial 0/1/1 (S0/1/1) 2811 Fast Ethernet 0/0 (F0/0) Fast Ethernet 0/1 (F0/1) Serial 0/0/0 (S0/0/0) Serial 0/0/1 (S0/0/1) 2900 Gigabit Ethernet 0/0 (G0/0) Gigabit Ethernet 0/1 (G0/1) Serial 0/0/0 (S0/0/0) Serial 0/0/1 (S0/0/1) Note: To find out how the router is configured, look at the interfaces to identify the type of router and how many interfaces the router has. There is no way to effectively list all the combinations of configurations for each router class. This table includes identifiers for the possible combinations of Ethernet and Serial interfaces in the device.

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture