80 | |
|
|
Note: The
Enabling or Disabling Persistence
Persistence can be enabled or disabled from the Events tabbed page. The persistent log is saved in NVRAM. Even after a reboot, all persistent logs are still reserved in NVRAM.
Note: It should be remembered that enabling Persistence will result in a continuous write operation. There is a risk that this will wear out the Flash element of the AP. You should decide whether enabling Persistence is right for your needs, given the elevated risk of wearing out the flash of the AP.
| Figure 33: Persistence Setting Detail |
|
|
Field | Description |
|
|
Persistence | Choose to either enable or disable Persistence. |
|
|
Severity | You can choose a Severity level of between 0 and 7. |
| Severity 7 is the least severe level and Severity 0 is the most severe level. For more |
| details on Severity Levels, see “Severity”. |
|
|
Depth | You can enter a value between 1 and 128. |
| For more information on Depth, see “Depth”. |
|
|
Severity
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.
If you set the Severity level to 7, all messages with a severity level between 7 and 0 will appear in the Event log. Alternatively, if you want to filter messages, you can set the Severity level to 4. In this instance,