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.