Netgear GS748Tv5 Software Administration Manual - Page 240

GS716Tv3, GS724Tv4, and GS748Tv5 Smart Switches Memory Logs The Memory Log stores messages in memory based upon the settings for message component and severity. Use the Memory Log screen to set the administrative status and behavior of logs in the system buffer. These log messages are cleared when the switch reboots.  To configure the memory log settings: 1. Select Monitoring > Logs > Memory Log. 2. Next to Admin Status, select one of the following radio buttons: • Enable. Enable system logging. • Disable. Prevent the system from logging messages. 3. From the Behavior list, specify the behavior of the log when it is full. • Wrap. When the buffer is full, the oldest log messages are deleted as the system logs new messages. • Stop on Full. When the buffer is full, the system stops logging new messages and preserves all existing log messages. 4. Click the Apply button. The Memory Log table displays on the Memory Log screen. The Total Number of messages displays the number of messages the system has logged in memory. Only the 200 most recent entries are displayed on the screen. The rest of the screen displays the Memory Log messages. The format of the log message is the same for messages that are displayed for the message log, persistent log, or console log. Messages logged to a collector or relay through syslog have the same format as well. The following example shows the standard format for a log message: Mar 24 05:34:05 10.131.12.183-1 UNKN[2176789276]: main_login.c(179) 3855 %% HTTP Session 19 initiated for user admin connected from 10.27.64.122 The number contained in the angle brackets represents the message priority, which is derived from the following values: Priority = (facility value × 8) + severity level. The facility value is usually one, which means it is a user-level message. Therefore, to determine the severity level of the message, subtract eight from the number in the angle brackets. The example log message has a severity level of 6 (informational). For more information about the severity of a log message, see Server Log on page 242. The message was generated on March 24 at 5:34:05 a.m. by the switch with an IP address of 10.131.12.183. The component that generated the message is unknown, but it came from line 179 of the main_login.c file. This is the 3,855th message logged since the switch was last booted. The message indicates that the administrator logged on to the HTTP management interface from a host with an IP address of 10.27.64.122. Monitoring the System 240