Netgear GS724TPv2 User Manual - Page 265

Message Log Format, HTTP Session 1 Login success from 172.16.166.231

Get Netgear GS724TPv2 PDF manuals and user guides View all Netgear GS724TPv2 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 265 highlights

NETGEAR 24-Port Gigabit Smart Managed Pro Switch with PoE+ and 2 SFP Ports Model GS724TPv2 The updated configuration is sent to the switch. Configuration changes take effect immediately. The Memory Log table displays on the Memory Log page. The Total number of Messages field displays the number of messages the system logged in memory. Only the 64 most recent entries are displayed on the page. The rest of the page displays the Memory Log messages. The format of the log message is the same for messages that are displayed for the message log, persistent log, or console log. Messages logged to a collector or relay through syslog support the same format as well. The following example shows the standard format for a log message: Jan 01 01:25:47 172.16.166.215-1 HST [75]: weblogin.c(295) 7 %% HTTP Session 1 Login success from 172.16.166.231 The number contained in the angle brackets represents the message priority, which is derived from the following values: Priority = severity level + 8. The facility value is usually 1, which means it is a user-level message. Therefore, to determine the severity level of the message, add 8 to the severity level. The sample log message shows a severity level of 6 (informational). For more information about the severity of a log message, see Manage the Server Log on page 267. The message was generated on Jan 01 01:25:47. The component that generated the message is HST, and it came from line 295 of file weblogin.c. This is the 7th message logged with system IP 172.16.166.215 and task-ID 1. The message indicates that the administrator logged on to the HTTP management interface from a host with an IP address of 172.16.166.231. 10. To refresh the page with the latest information about the switch, click the Update button. 11. To clear the messages from the buffered log in the memory, click the Clear button. Message Log Format This topic applies to the format of all logged messages that are displayed for the message log, persistent log, or console log. Messages logged to a collector or relay through syslog use an identical format: Jan 01 01:25:47 172.16.166.215-1 HST [75]: weblogin.c(295) 7 %% HTTP Session 1 Login success from 172.16.166.231 The example indicates a message with severity 6 (info) on the switch and is generated by component HST running in thread ID 75 on Jan 01 01:25:47 by line 295 of file weblogin.c. This is the 7th message logged with system IP 172.16.166.215 and task-ID 1. Monitor the System 265

  • 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
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
Monitor the System
265
NETGEAR 24-Port Gigabit Smart Managed Pro Switch with PoE+ and 2 SFP Ports Model GS724TPv2
The updated configuration is sent to the switch. Configuration changes take effect
immediately.
The Memory Log table displays on the Memory Log page.
The Total number of Messages field displays the number of messages the system logged
in memory. Only the 64 most recent entries are displayed on the page.
The rest of the page displays the Memory Log messages. The format of the log message
is the same for messages that are displayed for the message log, persistent log, or
console log. Messages logged to a collector or relay through syslog support the same
format as well.
The following example shows the standard format for a log message:
<14> Jan 01 01:25:47 172.16.166.215-1 HST [75]: weblogin.c(295)
7 %% HTTP Session 1 Login success from 172.16.166.231
The number contained in the angle brackets represents the message priority, which is
derived from the following values:
Priority = severity level + 8.
The facility value is usually 1, which means it is a user-level message. Therefore, to
determine the severity level of the message, add 8 to the severity level. The sample log
message shows a severity level of 6 (informational). For more information about the
severity of a log message, see
Manage the Server Log
on page 267.
The message was generated on Jan 01 01:25:47. The component that generated the
message is HST, and it came from line 295 of file weblogin.c. This is the 7th message
logged with system IP 172.16.166.215 and task-ID 1. The message indicates that the
administrator logged on to the HTTP management interface from a host with an IP
address of 172.16.166.231.
10.
To refresh the page with the latest information about the switch, click the
Update
button.
11.
To clear the messages from the buffered log in the memory, click the
Clear
button.
Message Log Format
This topic applies to the format of all logged messages that are displayed for the message
log, persistent log, or console log.
Messages logged to a collector or relay through syslog use an identical format:
<14> Jan 01 01:25:47 172.16.166.215-1 HST [75]: weblogin.c(295) 7 %%
HTTP Session 1 Login success from 172.16.166.231
The example indicates a message with severity 6 (info) on the switch and is generated by
component HST running in thread ID 75 on Jan 01 01:25:47 by line 295 of file weblogin.c.
This is the 7th message logged with system IP 172.16.166.215 and task-ID 1.