D-Link DWL-8500AP Product Manual - Page 93

Configuring Persistent Logging Options, Events, Update

Page 93 highlights

9 Viewing Access Point Status your local time. For information on setting the network time protocol, see "Enabling the Network Time Protocol Server" on page 79. Configuring Persistent Logging Options If the system unexpectedly reboots, log messages can be useful to diagnose the cause. However, log messages are erased when the system reboots unless you enable persistent logging. CAUTION: Enabling persistent logging can wear out the non-volatile (flash) memory and degrade network performance. You should only enable persistent logging to debug a problem. Make sure you disable persistent logging after you finish debugging the problem. To configure persistent logging on the Events page, set the persistence, severity, and depth options as described in Table 26, and then click Update. Table 25. Logging Options Field Description Persistence Severity Depth Choose Enabled to save system logs to non-volatile memory so that the logs are not erased when the AP reboots. Choose Disabled to save system logs to volatile memory. Logs in volatile memory are deleted when the system reboots. Specify the severity level of the log messages to write to non-volatile memory. For example, if you specify 2, critical, alert, and emergency logs are written to non-volatile memory. Error messages with a severity level of 3-7 are written to volatile memory. • 0-emergency • 1-alert • 2-critical • 3-error • 4-warning • 5-notice • 6-info • 7-debug You can store up to 128 messages in non-volatile memory. Once the number you configure in this field is reached, the oldest log event is overwritten by the new log event. NOTE: To apply your changes, click Update. Changing some access point settings might cause the AP to stop and restart system processes. If this happens, wireless clients will temporarily lose connectivity. We recommend that you change access point settings when WLAN traffic is low. Viewing Events Logs 93

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168

Viewing Events Logs
93
9
Viewing Access Point Status
your local time. For information on setting the network time protocol, see
“Enabling the Network Time Protocol Server”
on page 79.
Configuring Persistent Logging Options
If the system unexpectedly reboots, log messages can be useful to diagnose the cause.
However, log messages are erased when the system reboots unless you enable persistent
logging.
CAUTION:
Enabling persistent logging can wear out the non-volatile (flash) memory
and degrade network performance. You should only enable persistent
logging to debug a problem. Make sure you disable persistent logging
after you finish debugging the problem.
To configure persistent logging on the
Events
page, set the persistence, severity, and depth
options as described in
Table 26
, and then click
Update
.
NOTE:
To apply your changes, click
Update
. Changing some access point settings
might cause the AP to stop and restart system processes. If this happens,
wireless clients will temporarily lose connectivity. We recommend that you
change access point settings when WLAN traffic is low.
Table 25.
Logging Options
Field
Description
Persistence
Choose
Enabled
to save system logs to non-volatile memory so that the logs are
not erased when the AP reboots. Choose
Disabled
to save system logs to volatile
memory. Logs in volatile memory are deleted when the system reboots.
Severity
Specify the severity level of the log messages to write to non-volatile memory.
For example, if you specify 2, critical, alert, and emergency logs are written to
non-volatile memory. Error messages with a severity level of 3-7 are written to
volatile memory.
0—emergency
1—alert
2—critical
3—error
4—warning
5—notice
6—info
7—debug
Depth
You can store up to 128 messages in non-volatile memory. Once the number you
configure in this field is reached, the oldest log event is overwritten by the new
log event.