ccna 200 301 review

ccna 200 301 review.Trap logging: level informational, 13 message linesloggedLog Buffer (8192 bytes):.Dec18 17:10:14.079: %LINK-3-UPDOWN: Interface FastEthernetO/O, changed state to down*Dec18 17:10:15.079: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernetO/O, changed state to downNote the first two lines of the shaded section, which tell us about the logging service. The first line indicates that this router is logged into the console and contains debug messages, which in fact means that it contains debug level and all lower level messages. See Table 19-3 for a list of levels. The output also indicates that ten such messages have been logged. The second line indicates that this router logged into an internal buffer.Because this router initiated logging to the internal buffer, the showlogging command also lists the messages in the buffer. You can view some of the logged system messages at the end of the example. Configure the router to send system messages to the Syslog server, where the messages can be stored, filtered, and analyzed. This is a simple task. Step 1 First configure the destination host name, or the IP address of the Syslog server: rl(config)#logging 192.168.1.101 Step 2 Then, you can control which messages are sent here. For example, to limit messages to level 4 and lower (0 to 4), use the following command: Rl(config)#logging trap 4Tip: Please note that if you specify the highest level (lowest severity), this includes all levels (higher severity). Also, this command accepts the name of the level, so you can use logging trap wamingoUsing the Syslog serverLogging is most efficiently handled by caching the logs inside the device, but the most common method is to log the messages in the Syslog server soft