Cisco 11503 Administration Guide - Page 260

Viewing a Traplog File, Viewing a CSS Disk Log File, logging disk, sendmail, show log

Page 260 highlights

Viewing RMON Information Chapter 6 Configuring Remote Monitoring (RMON) For information on configuring an RMON event, see the "Configuring an RMON Event" section. For information on configuring an RMON alarm, see the "Configuring an RMON Alarm" section. Viewing a Traplog File A traplog file is an ASCII file in the log directory containing generic and enterprise SNMP traps. No configuration is necessary for the traplog file. When an RMON alarm event occurs, a notification of its occurrence is automatically saved in the trap log file on the CSS. Even when traps are disabled, the CSS still produces a log message for any event that would normally generate a trap. When a traplog file reaches its maximum size (50 MB for a hard disk-based CSS, 10 MB for a flash disk-based CSS), the CSS renames the traplog file to traplog.prev as a backup file and starts a new traplog file. The CSS overwrites the backup traplog file when it renames the traplog file. Each time the CSS reboots, it continues to use the existing traplog file until it reaches its maximum size. The traps sent to the traplog file are the same traps sent to an SNMP network management station. Refer to Chapter 5, Configuring Simple Network Management Protocol (SNMP), for information on configuring SNMP. To display all SNMP traps that have occurred on the CSS, enter: # show log traplog Viewing a CSS Disk Log File Before the CSS can send an event to a log location, you must: • Configure the location by using the logging disk, host, line, or sendmail command. • Enable logging for the network management subsystem. To do so, enter: (config)# logging subsystem netman level info-6 Refer to Chapter 4, Using the CSS Logging Features, for details on configuring logging for the CSS. To view the events in a log file on the CSS disk, use the show log log_filename command. To view a log file named log1, enter: # show log log1 6-34 Cisco Content Services Switch Administration Guide OL-5647-02

  • 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

Chapter 6
Configuring Remote Monitoring (RMON)
Viewing RMON Information
6-34
Cisco Content Services Switch Administration Guide
OL-5647-02
For information on configuring an RMON event, see the
“Configuring an RMON
Event”
section. For information on configuring an RMON alarm, see the
“Configuring an RMON Alarm”
section.
Viewing a Traplog File
A traplog file is an ASCII file in the log directory containing generic and
enterprise SNMP traps. No configuration is necessary for the traplog file. When
an RMON alarm event occurs, a notification of its occurrence is automatically
saved in the trap log file on the CSS. Even when traps are disabled, the CSS still
produces a log message for any event that would normally generate a trap.
When a traplog file reaches its maximum size (50 MB for a hard disk-based CSS,
10 MB for a flash disk-based CSS), the CSS renames the traplog file to
traplog.prev as a backup file and starts a new traplog file. The CSS overwrites the
backup traplog file when it renames the traplog file. Each time the CSS reboots,
it continues to use the existing traplog file until it reaches its maximum size.
The traps sent to the traplog file are the same traps sent to an SNMP network
management station. Refer to
Chapter 5, Configuring Simple Network
Management Protocol (SNMP)
, for information on configuring SNMP.
To display all SNMP traps that have occurred on the CSS, enter:
#
show log
traplog
Viewing a CSS Disk Log File
Before the CSS can send an event to a log location, you must:
Configure the location by using the
logging disk
,
host
,
line
, or
sendmail
command.
Enable logging for the network management subsystem. To do so, enter:
(config)#
logging subsystem netman level info-6
Refer to
Chapter 4, Using the CSS Logging Features
, for details on configuring
logging for the CSS.
To view the events in a log file on the CSS disk, use the
show log
log_filename
command. To view a log file named log1, enter:
#
show log log1