GarrettCom MNS-6K-SECURE 14.1.4 Switch User Manual


 
MAGNUM 6K SWITCHES, MNS-6K USER GUIDE
272
System Events
All events occurring on the Magnum 6K family of switches are logged. The events can be
escription
as shown below
Code D
0 Emergency (or Fatal) system is unusable – called “fatal” in show
log command
1 Alert: action must be taken immediately
2 Critical: critical conditions
3 nditions Error: error co
4 Warning: warning conditions
5 Notice: normal but significant condition – called “note” in show log
command
6 Informational: informational messages
7 Debug: debug-level messages
A few nt to
y def
The event log is now automatically saved to flash, so rebooting will not loose
the event logs are written on the flash, once the flash
poi note about logs
B ault, the logging is limited to the first six levels
them. NOTE – since
memory is full, the logs stop writing. It is important to erase the log periodically
or use syslog capability to download the logs to a syslog server (syslog is available
on MNS-6K-SECURE only)
The event log now includes more information, because of the additional
flexibility built into the log engine. For example, it now logs the IP address and
user name of a remote user login
The log size parameter is now redefined as the max size of the log that is saved to
flash. More events might appear in the log as they happen, but the whole list will
be trimmed to the specified max size when a save command is issued, or the
system rebooted.
These logs are in compliance with the definitions of RFC 3164, though not all the nuances
of the syslog are implemented as specified by the RFC.
The ‘show log’ command displays the log information and the ‘clear log’ command
clears the log entries.