QTECH QSW-8300 Инструкция по настройке - Manual (Page 360)

+7(495) 797-3311 www.qtech.ru
Москва, Новозаводская ул., 18, стр. 1
359
emergencies will be outputted.
Follow table summarized the log information severity level and brief description. Note: these
severity levels are in accordance with the standard UNIX/LINUX syslog.
Severity of the loginformation
Severity Value Description
emergencies 0 System is unusable
alerts 1 Action must be taken immediately
critical 2 Critical conditions
errors 3 Error conditions
warnings 4 Warning conditions
notifications 5 Normal but significant condition
informational 6 Informational messages
debugging 7 Debug-level messages
Right now the switch can generate information of following four levels
Restart the switch, mission abnormal, hot plug on the CHASSIS switch chips are classified
critical
Up/down interface, topology change, aggregate port state change of the interface are
notifications warnings
Outputted information from the CLI command is classified informational
Information from the debugging of CLI command is classified debugging
Log information can be automatically sent to corresponding channels with regard to respective
severity levels. Amongst the debugging information can only be sent to the monitor. Those with
the Informational level can only be sent to current monitor terminal, such as the information
from the Telnet terminal configuration command can only be transmitted to the Telnet terminal.
Warnings information can be sent to all terminal with also saved in the SDRAM log buffer zone.
And the critical information can be save both in SDRAM and the NVRAM (if exists) besides
sent to all terminals. To check the log save in SDRAM and the NVRAM, we can use the show
logging buffered command. To clear the log save in NVRAM and SDRAM log buffer zone, we
can use the clear logging command.
43.7.2 System Log Configuration
System Log Configuration Task Sequence:
1. Display and clear log buffer zone
2. Configure the log host output channel
3. Enable/disable the log executed-commands
4. Display the log source
5. Display executed-commands state