Cisco 11503 Administration Guide - Page 145

Interpreting sys.log Log Messages

Page 145 highlights

Chapter 4 Using the CSS Logging Features Interpreting sys.log Log Messages • ip_or_host - The IP address or host name of the TFTP server to receive the file. Enter an IP address in dotted-decimal notation (for example, 192.168.11.1) or in mnemonic host-name format (for example, myhost.mydomain.com). If you wish to use a host name, you must first set up a host table using the host command. • filename - The name you want to assign to the file on the TFTP server. Include the full path to the file. Enter an unquoted text string with no spaces and a maximum of 32 characters. For example, to copy the starlog log file to a TFTP server: # copy log starlog tftp tftpserv1 starlogthurs Interpreting sys.log Log Messages The following example shows a sys.log message. This section describes the parts of a log message using this example. FEB 16 14:01:13 5/1 2453 VLANMGR-7: Transmit sfm STP BPDU on bPort 1, egressLp 0x1f00 VlanLpSend() ret:0 A log message consists of the following components: • The time stamp indicates when the log message event occurred. In this example, the time stamp is FEB 16 14:01:13. • The physical interface indicates the slot/subslot (for example, 5/1) where the event occurred in the CSS. • The counter records the incremental occurrence of each message. The count of this message is 2,453. • The subsystem name and level is the CSS subsystem assigned to the message and the level of the message. Because this example is a subsystem message, the subsystem is the VLAN Manager and the log level is 7, which is a debug level (VLANMGR-7). See the "Configuring Logging for a Subsystem" section for a list of CSS subsystems. • The log message indicating the event has occurred. The remaining string in the example is the event that occurred. Transmit sfm STP BPDU on bPort 1, egressLp 0x1f00 VlanLpSend() ret:0 You can define a log message for a subsystem at a particular logging level through the cliLogMessage subsystem command. For more information, see the "Configuring a Log Message for a Subsystem at a Logging Level" section. OL-5647-02 Cisco Content Services Switch Administration Guide 4-25

  • 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
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328
  • 329
  • 330
  • 331
  • 332
  • 333
  • 334
  • 335
  • 336
  • 337
  • 338
  • 339
  • 340
  • 341
  • 342
  • 343
  • 344
  • 345
  • 346
  • 347
  • 348
  • 349
  • 350
  • 351
  • 352
  • 353
  • 354
  • 355
  • 356
  • 357
  • 358
  • 359
  • 360
  • 361
  • 362
  • 363
  • 364
  • 365
  • 366
  • 367
  • 368
  • 369
  • 370
  • 371
  • 372
  • 373
  • 374
  • 375
  • 376
  • 377
  • 378
  • 379
  • 380
  • 381
  • 382
  • 383
  • 384
  • 385
  • 386
  • 387
  • 388
  • 389
  • 390
  • 391
  • 392

4-25
Cisco Content Services Switch Administration Guide
OL-5647-02
Chapter 4
Using the CSS Logging Features
Interpreting sys.log Log Messages
ip_or_host
- The IP address or host name of the TFTP server to receive the
file. Enter an IP address in dotted-decimal notation (for example,
192.168.11.1) or in mnemonic host-name format (for example,
myhost.mydomain.com). If you wish to use a host name, you must first set up
a host table using the
host
command.
filename
- The name
you want to assign to
the file on the TFTP server.
Include the full path to the file. Enter an unquoted text string with no spaces
and a maximum of 32 characters.
For example, to copy the
starlog
log file to a TFTP server:
#
copy log starlog tftp tftpserv1 starlogthurs
Interpreting sys.log Log Messages
The following example shows a sys.log message. This section describes the parts
of a log message using this example.
FEB 16 14:01:13 5/1 2453 VLANMGR-7: Transmit sfm STP BPDU on bPort 1,
egressLp 0x1f00 VlanLpSend() ret:0
A log message consists of the following components:
The time stamp indicates when the log message event occurred. In this
example, the time stamp is FEB 16 14:01:13.
The physical interface indicates the
slot
/
subslot
(for example, 5/1) where the
event occurred in the CSS.
The counter records the incremental occurrence of each message. The count
of this message is 2,453.
The subsystem name and level is the CSS subsystem assigned to the message
and the level of the message. Because this example is a subsystem message,
the subsystem is the VLAN Manager and the log level is 7, which is a debug
level (VLANMGR-7). See the
“Configuring Logging for a Subsystem”
section for a list of CSS subsystems.
The log message indicating the event has occurred. The remaining string in
the example is the event that occurred.
Transmit sfm STP BPDU on bPort 1, egressLp 0x1f00 VlanLpSend()
ret:0
You can define a log message for a subsystem at a particular logging level through
the
cliLogMessage subsystem
command. For more information, see the
“Configuring a Log Message for a Subsystem at a Logging Level”
section
.