211 | |
|
|
36 | |
channel | 36 |
Property | Value |
100 | |
up | |
100 | |
2347 | |
2346 | |
no | |
no | |
0 | |
0 | |
off | |
off | |
frequency | 5180 |
wme | off |
off | |
50 | |
75 |
Get Status on Events
|
| |
number priority time | daemon | message |
1 | info | Jan | 1 00:04:51 | login[289] | root login on `ttyS0' |
2 | notice | Jan | 1 00:02:07 | syslog | Device boot up |
3 | info | Jan | 1 00:02:06 | dropbear[277] | Not forking |
Get Status on Persistence
If Persistence is enabled, all logs become persistent and are written to NVRAM and after a reboot, all logs are recoverable from your system.
Enable or Disable Persistence
In the above example Persistence is disabled. Suppose you want to enable Persistence to ensure that logs are written to NVRAM. Use the following command to enable Persistence:
Alternatively, if you wanted to disable Persistence, use the following CLI command:
Specify the Severity of Messages to be Displayed in the Event Log
The purpose of severity configuration is to filter or limit the security messages that are displayed in the Event log. It is unlikely that you will want to see a list of all messages. Those of less severity or significance can be filtered using the Severity Configuration feature.