Netgear STM300 STM 150-300-600 Reference Manual (PDF) - Page 181

Table 52., Syslog Settings Continued

Page 181 highlights

ProSecure Web/Email Security Threat Management (STM) Appliance Table 52. Syslog Settings (Continued) Setting Description (or Subfield and Description) Facility Priority The facility indicates from which internal part of the STM the log message originates. For each log that you have selected to be sent to the syslog server (see earlier in this table), select one of the following facilities from the drop-down list: • auth. Security and authorization log messages. • authpriv. Security and authorization log messages for sensitive information. • cron. Clock daemon log messages. • deamon. Other daemon log messages. • ftp. FTP log messages. • kern. Kernel log messages. • local0 through local7. Locally defined log messages (1 through 7). • lpr. Line printer subsystem log messages. • mail. Mail subsystem log messages. • news. Usenet news subsystem log messages. • syslog. Log messages that are generated internally by the syslog server (syslogd). • user. Generic user-level log messages. • uucp. Unix-Unix copy (UUCP) subsystem log messages. For each log that you have selected to be sent to the syslog server (see earlier in this table), select one of the following severities from the drop-down list: • emerg. The STM is unusable. • alert. An action needs to be taken immediately. • crit. There are critical conditions. • err. There are error conditions. • warning. There are warning conditions. • notice. There are normal but significant conditions. • info. Informational messages. • debug. Debug-level messages. Note: All the logs with a severity that is equal to and above the severity that you specify are logged on the specified syslog server. For example, if you select crit as the severity, then the logs with the severities crit, alert, and emerg are logged. 4. Click Apply to save your settings. Chapter 6. Monitoring System Access and Performance | 181

  • 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
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261

Chapter 6.
Monitoring System Access and Performance
|
181
ProSecure Web/Email Security Threat Management (STM) Appliance
4.
Click
Apply
to save your settings.
Facility
The facility indicates from which internal part of the STM the log message originates. For
each log that you have selected to be sent to the syslog server (see earlier in this table),
select one of the following facilities from the drop-down list:
auth
. Security and authorization log messages.
authpriv
. Security and authorization log messages for sensitive information.
cron
. Clock daemon log messages.
deamon
. Other daemon log messages.
ftp
. FTP log messages.
kern
. Kernel log messages.
local0
through
local7
. Locally defined log messages (1 through 7).
lpr
. Line printer subsystem log messages.
mail
. Mail subsystem log messages.
news
. Usenet news subsystem log messages.
syslog
. Log messages that are generated internally by the syslog server (syslogd).
user
. Generic user-level log messages.
uucp
. Unix-Unix copy (UUCP) subsystem log messages.
Priority
For each log that you have selected to be sent to the syslog server (see earlier in this table),
select one of the following severities from the drop-down list:
emerg
. The STM is unusable.
alert
. An action needs to be taken immediately.
crit
. There are critical conditions.
err
. There are error conditions.
warning
. There are warning conditions.
notice
. There are normal but significant conditions.
info
. Informational messages.
debug
. Debug-level messages.
Note:
All the logs with a severity that is equal to and above the severity that you specify are
logged on the specified syslog server. For example, if you select crit as the severity, then the
logs with the severities crit, alert, and emerg are logged.
Table 52.
Syslog Settings (Continued)
Setting
Description (or Subfield and Description)