debug信息存放位置.pptVIP

Where is log The ERX router can send log messages to a variety of locations. By default, due to the low severity level and low verbosity level, a very limited number of log messages are stored in volatile memory on the SRP. A sophisticated algorithm is used by the logging process so that no one category can monopolize the logging process and starve other categories from inserting log messages into volatile memory. As of release 3.2 persistent logging has been implemented between system reloads. This means that log messages in the SRP volatile memory will be retained through a system reload unless the ERX system is power cycled or the system detects any problems. Log messages will also be stored in non-volatile memory in a file on the flash called system.log. Only severity levels 0-2 or EMERGENCY, ALERT and CRITICAL log messages will be stored in system.log. This ASCII file can have a maximum size of approximately 64K. When the maximum size is reached, the file is circular in nature and operates in a FIFO manner. The file can be copied to a PC and read by any text editor. The log messages can also be sent to the console in real-time. The console also has a severity level associated with it. By default, only messages that have a severity level of WARNING or higher are sent to the console. These same messages can also be directed to a Telnet/SSH session. By default, if NOTICE, INFO OR DEBUG log messages occur,they are not directed to the console. This behavior is configurable.Finally, log messages can also be directed to syslog. By default, the severity level for syslog is DEBUG. Multiple syslog hosts can be configured. For each syslog host, it is possible to configure which facility (0-7) syslog messages are sent. Direct debug message to Telnet Session To view the pppPacket DEBUG log messages in real-time on the console, use the configuration command log destination console severity debug. DEBUG messages will only be sent to the console session directly attached to