/opennms-base-assembly/src/main/filtered/etc/events/Cisco.events.xml
XML | 12320 lines | 11882 code | 240 blank | 198 comment | 0 complexity | be3bec15a4e2c424f43634085bed6b43 MD5 | raw file
Large files files are truncated, but you can click here to view the full file
1<events xmlns="http://xmlns.opennms.org/xsd/eventconf"> 2<!-- Start of Cisco Traps --> 3<!-- Start of Cisco MIB: ACCOUNTING-CONTROL-MIB --> 4<event> 5 <mask> 6 <maskelement> 7 <mename>id</mename> 8 <mevalue>.1.3.6.1.4.1.9.10.17.3</mevalue> 9 </maskelement> 10 <maskelement> 11 <mename>generic</mename> 12 <mevalue>6</mevalue> 13 </maskelement> 14 <maskelement> 15 <mename>specific</mename> 16 <mevalue>1</mevalue> 17 </maskelement> 18 </mask> 19 <uei>uei.opennms.org/vendor/Cisco/traps/acctngFileNearlyFull</uei> 20 <event-label>ACCOUNTING-CONTROL-MIB defined trap event: acctngFileNearlyFull</event-label> 21 <descr><p>An indication that the size of the file into which 22 accounting information is currently being collected has 23 exceeded the threshold percentage of its maximum file size. 24 This notification is generated only at the time of the 25 transition from not-exceeding to exceeding.</p><table> 26 <tr><td><b> 27 acctngFileName</b></td><td>%parm[#1]% 28 </td><td><p;></p></td;></tr><tr><td><b> 29 acctngFileMaximumSize</b></td><td>%parm[#2]% 30 </td><td><p;></p></td;></tr><tr><td><b> 31 acctngControlTrapThreshold</b></td><td>%parm[#3]% 32 </td><td><p;></p></td;></tr></table> 33 </descr> 34 <logmsg dest='logndisplay'><p>Cisco Event: Accounting File Size exceeds threshold.</p></logmsg> 35 <severity>Warning</severity> 36 <alarm-data reduction-key="%uei%:%dpname%:%nodeid%" alarm-type="3" auto-clean="false"/> 37</event> 38 39<event> 40 <mask> 41 <maskelement> 42 <mename>id</mename> 43 <mevalue>.1.3.6.1.4.1.9.10.17.3</mevalue> 44 </maskelement> 45 <maskelement> 46 <mename>generic</mename> 47 <mevalue>6</mevalue> 48 </maskelement> 49 <maskelement> 50 <mename>specific</mename> 51 <mevalue>2</mevalue> 52 </maskelement> 53 </mask> 54 <uei>uei.opennms.org/vendor/Cisco/traps/acctngFileFull</uei> 55 <event-label>ACCOUNTING-CONTROL-MIB defined trap event: acctngFileFull</event-label> 56 <descr><p>An indication that the size of the file into which 57 accounting information is currently being collected has 58 transistioned to its maximum file size. This notification 59 is generated at the time of the transition from not-full to 60 full, and periodically thereafter until such time as 61 collection of data is no longer inhibited by the file full 62 condition.</p><table> 63 <tr><td><b> 64 acctngFileName</b></td><td>%parm[#1]% 65 </td><td><p;></p></td;></tr><tr><td><b> 66 acctngFileMaximumSize</b></td><td>%parm[#2]% 67 </td><td><p;></p></td;></tr></table> 68 </descr> 69 <logmsg dest='logndisplay'><p>Cisco Event: Accounting File Size at maximum.</p></logmsg> 70 <severity>Major</severity> 71 <alarm-data reduction-key="%uei%:%dpname%:%nodeid%" alarm-type="3" auto-clean="false"/> 72</event> 73<!-- End of Cisco MIB: ACCOUNTING-CONTROL-MIB --> 74<!-- Start of Cisco MIB: ADSL-LINE-MIB --> 75<event> 76 <mask> 77 <maskelement> 78 <mename>id</mename> 79 <mevalue>.1.3.6.1.2.1.10.94.1.2.1</mevalue> 80 </maskelement> 81 <maskelement> 82 <mename>generic</mename> 83 <mevalue>6</mevalue> 84 </maskelement> 85 <maskelement> 86 <mename>specific</mename> 87 <mevalue>1</mevalue> 88 </maskelement> 89 </mask> 90 <uei>uei.opennms.org/vendor/Cisco/traps/adslAtucPerfLofsThreshTrap</uei> 91 <event-label>ADSL-LINE-MIB defined trap event: adslAtucPerfLofsThreshTrap</event-label> 92 <descr><p>Loss of Framing 15-minute interval threshold reached.</p><table> 93 <tr><td><b> 94 adslAtucThresh15MinLofs</b></td><td>%parm[#1]% 95 </td><td><p;></p></td;></tr></table> 96 </descr> 97 <logmsg dest='logndisplay'><p>Cisco Event: ADSL Loss of Framing threshold reached.</p></logmsg> 98 <severity>Warning</severity> 99</event> 100 101<event> 102 <mask> 103 <maskelement> 104 <mename>id</mename> 105 <mevalue>.1.3.6.1.2.1.10.94.1.2.1</mevalue> 106 </maskelement> 107 <maskelement> 108 <mename>generic</mename> 109 <mevalue>6</mevalue> 110 </maskelement> 111 <maskelement> 112 <mename>specific</mename> 113 <mevalue>2</mevalue> 114 </maskelement> 115 </mask> 116 <uei>uei.opennms.org/vendor/Cisco/traps/adslAtucPerfLossThreshTrap</uei> 117 <event-label>ADSL-LINE-MIB defined trap event: adslAtucPerfLossThreshTrap</event-label> 118 <descr><p>Loss of Signal 15-minute interval threshold reached.</p><table> 119 <tr><td><b> 120 adslAtucThresh15MinLoss</b></td><td>%parm[#1]% 121 </td><td><p;></p></td;></tr></table> 122 </descr> 123 <logmsg dest='logndisplay'><p>Cisco Event: ADSL Loss of Signal threshold reached.</p></logmsg> 124 <severity>Warning</severity> 125</event> 126 127<event> 128 <mask> 129 <maskelement> 130 <mename>id</mename> 131 <mevalue>.1.3.6.1.2.1.10.94.1.2.1</mevalue> 132 </maskelement> 133 <maskelement> 134 <mename>generic</mename> 135 <mevalue>6</mevalue> 136 </maskelement> 137 <maskelement> 138 <mename>specific</mename> 139 <mevalue>3</mevalue> 140 </maskelement> 141 </mask> 142 <uei>uei.opennms.org/vendor/Cisco/traps/adslAtucPerfLprsThreshTrap</uei> 143 <event-label>ADSL-LINE-MIB defined trap event: adslAtucPerfLprsThreshTrap</event-label> 144 <descr><p>Loss of Power 15-minute interval threshold reached.</p><table> 145 <tr><td><b> 146 adslAtucThresh15MinLprs</b></td><td>%parm[#1]% 147 </td><td><p;></p></td;></tr></table> 148 </descr> 149 <logmsg dest='logndisplay'><p>Cisco Event: ADSL Loss of Power threshold reached.</p></logmsg> 150 <severity>Warning</severity> 151</event> 152 153<event> 154 <mask> 155 <maskelement> 156 <mename>id</mename> 157 <mevalue>.1.3.6.1.2.1.10.94.1.2.1</mevalue> 158 </maskelement> 159 <maskelement> 160 <mename>generic</mename> 161 <mevalue>6</mevalue> 162 </maskelement> 163 <maskelement> 164 <mename>specific</mename> 165 <mevalue>4</mevalue> 166 </maskelement> 167 </mask> 168 <uei>uei.opennms.org/vendor/Cisco/traps/adslAtucPerfESsThreshTrap</uei> 169 <event-label>ADSL-LINE-MIB defined trap event: adslAtucPerfESsThreshTrap</event-label> 170 <descr><p>Errored Second 15-minute interval threshold reached.</p><table> 171 <tr><td><b> 172 adslAtucThresh15MinESs</b></td><td>%parm[#1]% 173 </td><td><p;></p></td;></tr></table> 174 </descr> 175 <logmsg dest='logndisplay'><p>Cisco Event: ADSL Errored Second threshold reached.</p></logmsg> 176 <severity>Warning</severity> 177</event> 178 179<event> 180 <mask> 181 <maskelement> 182 <mename>id</mename> 183 <mevalue>.1.3.6.1.2.1.10.94.1.2.1</mevalue> 184 </maskelement> 185 <maskelement> 186 <mename>generic</mename> 187 <mevalue>6</mevalue> 188 </maskelement> 189 <maskelement> 190 <mename>specific</mename> 191 <mevalue>5</mevalue> 192 </maskelement> 193 </mask> 194 <uei>uei.opennms.org/vendor/Cisco/traps/adslAtucRateChangeTrap</uei> 195 <event-label>ADSL-LINE-MIB defined trap event: adslAtucRateChangeTrap</event-label> 196 <descr><p>The ATUCs transmit rate has changed (RADSL mode only)</p><table> 197 <tr><td><b> 198 adslAtucChanCurrTxRate</b></td><td>%parm[#1]% 199 </td><td><p;></p></td;></tr><tr><td><b> 200 adslAtucChanPrevTxRate</b></td><td>%parm[#2]% 201 </td><td><p;></p></td;></tr></table> 202 </descr> 203 <logmsg dest='logndisplay'><p>Cisco Event: ADSL ATUC transmit rate changed.</p></logmsg> 204 <severity>Warning</severity> 205</event> 206 207<event> 208 <mask> 209 <maskelement> 210 <mename>id</mename> 211 <mevalue>.1.3.6.1.2.1.10.94.1.2.1</mevalue> 212 </maskelement> 213 <maskelement> 214 <mename>generic</mename> 215 <mevalue>6</mevalue> 216 </maskelement> 217 <maskelement> 218 <mename>specific</mename> 219 <mevalue>6</mevalue> 220 </maskelement> 221 </mask> 222 <uei>uei.opennms.org/vendor/Cisco/traps/adslAtucPerfLolsThreshTrap</uei> 223 <event-label>ADSL-LINE-MIB defined trap event: adslAtucPerfLolsThreshTrap</event-label> 224 <descr><p>Loss of Link 15-minute interval threshold reached.</p><table> 225 <tr><td><b> 226 adslAtucThresh15MinLols</b></td><td>%parm[#1]% 227 </td><td><p;></p></td;></tr></table> 228 </descr> 229 <logmsg dest='logndisplay'><p>Cisco Event: ADSL Loss of Link threshold reached.</p></logmsg> 230 <severity>Warning</severity> 231</event> 232 233<event> 234 <mask> 235 <maskelement> 236 <mename>id</mename> 237 <mevalue>.1.3.6.1.2.1.10.94.1.2.1</mevalue> 238 </maskelement> 239 <maskelement> 240 <mename>generic</mename> 241 <mevalue>6</mevalue> 242 </maskelement> 243 <maskelement> 244 <mename>specific</mename> 245 <mevalue>7</mevalue> 246 </maskelement> 247 </mask> 248 <uei>uei.opennms.org/vendor/Cisco/traps/adslAtucInitFailureTrap</uei> 249 <event-label>ADSL-LINE-MIB defined trap event: adslAtucInitFailureTrap</event-label> 250 <descr><p>ATUC initialization failed. See adslAtucCurrStatus 251 for potential reasons.</p><table> 252 <tr><td><b> 253 adslAtucCurrStatus</b></td><td>%parm[#1]% 254 </td><td><p;></p></td;></tr></table> 255 </descr> 256 <logmsg dest='logndisplay'><p>Cisco Event: ADSL ATUC initialization failed.</p></logmsg> 257 <severity>Warning</severity> 258</event> 259 260<event> 261 <mask> 262 <maskelement> 263 <mename>id</mename> 264 <mevalue>.1.3.6.1.2.1.10.94.1.2.2</mevalue> 265 </maskelement> 266 <maskelement> 267 <mename>generic</mename> 268 <mevalue>6</mevalue> 269 </maskelement> 270 <maskelement> 271 <mename>specific</mename> 272 <mevalue>1</mevalue> 273 </maskelement> 274 </mask> 275 <uei>uei.opennms.org/vendor/Cisco/traps/adslAturPerfLofsThreshTrap</uei> 276 <event-label>ADSL-LINE-MIB defined trap event: adslAturPerfLofsThreshTrap</event-label> 277 <descr><p>Loss of Framing 15-minute interval threshold reached.</p><table> 278 <tr><td><b> 279 adslAturThresh15MinLofs</b></td><td>%parm[#1]%i 280 </td><td><p;></p></td;></tr></table> 281 </descr> 282 <logmsg dest='logndisplay'><p>Cisco Event: ADSL Loss of Framing threshold reached.</p></logmsg> 283 <severity>Warning</severity> 284</event> 285 286<event> 287 <mask> 288 <maskelement> 289 <mename>id</mename> 290 <mevalue>.1.3.6.1.2.1.10.94.1.2.2</mevalue> 291 </maskelement> 292 <maskelement> 293 <mename>generic</mename> 294 <mevalue>6</mevalue> 295 </maskelement> 296 <maskelement> 297 <mename>specific</mename> 298 <mevalue>2</mevalue> 299 </maskelement> 300 </mask> 301 <uei>uei.opennms.org/vendor/Cisco/traps/adslAturPerfLossThreshTrap</uei> 302 <event-label>ADSL-LINE-MIB defined trap event: adslAturPerfLossThreshTrap</event-label> 303 <descr><p>Loss of Signal 15-minute interval threshold reached.</p><table> 304 <tr><td><b> 305 adslAturThresh15MinLoss</b></td><td>%parm[#1]% 306 </td><td><p;></p></td;></tr></table> 307 </descr> 308 <logmsg dest='logndisplay'><p>Cisco Event: ADSL Loss of Signal threshold reached.</p></logmsg> 309 <severity>Warning</severity> 310</event> 311 312<event> 313 <mask> 314 <maskelement> 315 <mename>id</mename> 316 <mevalue>.1.3.6.1.2.1.10.94.1.2.2</mevalue> 317 </maskelement> 318 <maskelement> 319 <mename>generic</mename> 320 <mevalue>6</mevalue> 321 </maskelement> 322 <maskelement> 323 <mename>specific</mename> 324 <mevalue>3</mevalue> 325 </maskelement> 326 </mask> 327 <uei>uei.opennms.org/vendor/Cisco/traps/adslAturPerfLprsThreshTrap</uei> 328 <event-label>ADSL-LINE-MIB defined trap event: adslAturPerfLprsThreshTrap</event-label> 329 <descr><p>Loss of Power 15-minute interval threshold reached.</p><table> 330 <tr><td><b> 331 adslAturThresh15MinLprs</b></td><td>%parm[#1]% 332 </td><td><p;></p></td;></tr></table> 333 </descr> 334 <logmsg dest='logndisplay'><p>Cisco Event: ADSL Loss of Power threshold reached.</p></logmsg> 335 <severity>Warning</severity> 336</event> 337 338<event> 339 <mask> 340 <maskelement> 341 <mename>id</mename> 342 <mevalue>.1.3.6.1.2.1.10.94.1.2.2</mevalue> 343 </maskelement> 344 <maskelement> 345 <mename>generic</mename> 346 <mevalue>6</mevalue> 347 </maskelement> 348 <maskelement> 349 <mename>specific</mename> 350 <mevalue>4</mevalue> 351 </maskelement> 352 </mask> 353 <uei>uei.opennms.org/vendor/Cisco/traps/adslAturPerfESsThreshTrap</uei> 354 <event-label>ADSL-LINE-MIB defined trap event: adslAturPerfESsThreshTrap</event-label> 355 <descr><p>Errored Second 15-minute interval threshold reached.</p><table> 356 <tr><td><b> 357 adslAturThresh15MinESs</b></td><td>%parm[#1]% 358 </td><td><p;></p></td;></tr></table> 359 </descr> 360 <logmsg dest='logndisplay'><p>Cisco Event: ADSL Errored Second threshold reached.</p></logmsg> 361 <severity>Warning</severity> 362</event> 363 364<event> 365 <mask> 366 <maskelement> 367 <mename>id</mename> 368 <mevalue>.1.3.6.1.2.1.10.94.1.2.2</mevalue> 369 </maskelement> 370 <maskelement> 371 <mename>generic</mename> 372 <mevalue>6</mevalue> 373 </maskelement> 374 <maskelement> 375 <mename>specific</mename> 376 <mevalue>5</mevalue> 377 </maskelement> 378 </mask> 379 <uei>uei.opennms.org/vendor/Cisco/traps/adslAturRateChangeTrap</uei> 380 <event-label>ADSL-LINE-MIB defined trap event: adslAturRateChangeTrap</event-label> 381 <descr><p>The ATURs transmit rate has changed (RADSL mode only)</p><table> 382 <tr><td><b> 383 adslAturChanCurrTxRate</b></td><td>%parm[#1]% 384 </td><td><p;></p></td;></tr><tr><td><b> 385 adslAturChanPrevTxRate</b></td><td>%parm[#2]% 386 </td><td><p;></p></td;></tr></table> 387 </descr> 388 <logmsg dest='logndisplay'><p>Cisco Event: ADSL ATUR transmit rate has changed.</p></logmsg> 389 <severity>Warning</severity> 390</event> 391<!-- End of Cisco MIB: ADSL-LINE-MIB --> 392<!-- Start of Cisco MIB: APPN-MIB --> 393<event> 394 <mask> 395 <maskelement> 396 <mename>id</mename> 397 <mevalue>.1.3.6.1.2.1.34.4</mevalue> 398 </maskelement> 399 <maskelement> 400 <mename>generic</mename> 401 <mevalue>6</mevalue> 402 </maskelement> 403 <maskelement> 404 <mename>specific</mename> 405 <mevalue>1</mevalue> 406 </maskelement> 407 </mask> 408 <uei>uei.opennms.org/vendor/Cisco/traps/alertTrap</uei> 409 <event-label>APPN-MIB defined trap event: alertTrap</event-label> 410 <descr><p>This trap carries a 32-bit SNA Management Services (SNA/MS) 411 Alert ID Number, as specified in SNA/MS Formats.</p><table> 412 <tr><td><b> 413 alertIdNumber</b></td><td>%parm[#1]% 414 </td><td><p;></p></td;></tr><tr><td><b> 415 affectedObject</b></td><td>%parm[#2]% 416 </td><td><p;></p></td;></tr></table> 417 </descr> 418 <logmsg dest='logndisplay'><p>Cisco Event: SNA Alert, ID Number: %parm[#1]%.</p></logmsg> 419 <severity>Warning</severity> 420</event> 421<!-- End of Cisco MIB: APPN-MIB --> 422<!-- Start of Cisco MIB: APPN-TRAP-MIB --> 423<event> 424 <mask> 425 <maskelement> 426 <mename>id</mename> 427 <mevalue>.1.3.6.1.2.1.34.4</mevalue> 428 </maskelement> 429 <maskelement> 430 <mename>generic</mename> 431 <mevalue>6</mevalue> 432 </maskelement> 433 <maskelement> 434 <mename>specific</mename> 435 <mevalue>1</mevalue> 436 </maskelement> 437 </mask> 438 <uei>uei.opennms.org/vendor/Cisco/traps/appnIsrAccountingDataTrap</uei> 439 <event-label>APPN-TRAP-MIB defined trap event: appnIsrAccountingDataTrap</event-label> 440 <descr><p>When it has been enabled, this notification is generated by an 441 APPN node whenever an ISR session passing through the node is 442 taken down, regardless of whether the session went down 443 normally or abnormally. Its purpose is to allow a management 444 application (primarily an accounting application) that is 445 monitoring the ISR counts to receive the final values of these 446 counts, so that the application can properly account for the 447 amounts the counts were incremented since the last time the 448 application polled them. The appnIsInSessUpTime object 449 provides the total amount of time that the session was active. 450 </p><p> 451 This notification is not a substitute for polling the ISR 452 counts. In particular, the count values reported in this 453 notification cannot be assumed to be the complete totals for 454 the life of the session, since they may have wrapped while the 455 session was up. 456 </p><p> 457 The session to which the objects in this notification apply is 458 identified by the fully qualified CP name and PCID that make up 459 the table index. An instance of this notification will contain 460 exactly one instance of each of its objects, and these objects 461 will all belong to the same conceptual row of the 462 appnIsInTable. 463 </p><p> 464 Generation of this notification is controlled by the same 465 object in the APPN MIB, appnIsInGlobeCtrAdminStatus, that 466 controls whether the count objects themselves are being 467 incremented.</p><table> 468 <tr><td><b> 469 appnIsInP2SFmdPius</b></td><td>%parm[#1]% 470 </td><td><p;></p></td;></tr><tr><td><b> 471 appnIsInS2PFmdPius</b></td><td>%parm[#2]% 472 </td><td><p;></p></td;></tr><tr><td><b> 473 appnIsInP2SNonFmdPius</b></td><td>%parm[#3]% 474 </td><td><p;></p></td;></tr><tr><td><b> 475 appnIsInS2PNonFmdPius</b></td><td>%parm[#4]% 476 </td><td><p;></p></td;></tr><tr><td><b> 477 appnIsInP2SFmdBytes</b></td><td>%parm[#5]% 478 </td><td><p;></p></td;></tr><tr><td><b> 479 appnIsInS2PFmdBytes</b></td><td>%parm[#6]% 480 </td><td><p;></p></td;></tr><tr><td><b> 481 appnIsInP2SNonFmdBytes</b></td><td>%parm[#7]% 482 </td><td><p;></p></td;></tr><tr><td><b> 483 appnIsInS2PNonFmdBytes</b></td><td>%parm[#8]% 484 </td><td><p;></p></td;></tr><tr><td><b> 485 appnIsInSessUpTime</b></td><td>%parm[#9]% 486 </td><td><p;></p></td;></tr></table> 487 </descr> 488 <logmsg dest='logndisplay'><p>Cisco Event: APPN Accounting Data.</p></logmsg> 489 <severity>Warning</severity> 490</event> 491 492<event> 493 <mask> 494 <maskelement> 495 <mename>id</mename> 496 <mevalue>.1.3.6.1.2.1.34.4</mevalue> 497 </maskelement> 498 <maskelement> 499 <mename>generic</mename> 500 <mevalue>6</mevalue> 501 </maskelement> 502 <maskelement> 503 <mename>specific</mename> 504 <mevalue>2</mevalue> 505 </maskelement> 506 </mask> 507 <uei>uei.opennms.org/vendor/Cisco/traps/appnLocalTgOperStateChangeTrap</uei> 508 <event-label>APPN-TRAP-MIB defined trap event: appnLocalTgOperStateChangeTrap</event-label> 509 <descr><p>When it has been enabled, this notification makes it possible 510 for an APPN topology application to get asynchronous 511 notifications of local TG operational state changes, 512 and thus to reduce the frequency with which it polls 513 for these changes. 514 </p><p> 515 This notification is sent whenever there is a change to 516 the appnLocalTgOperational object in a row of the 517 appnLocalTgTable. This notification is only sent for row 518 creation if the row is created with a value of 'true' for 519 appnLocalTgOperational. This notification is only sent for 520 row deletion if the last value of appnLocalTgOperational was 521 'true'. In this case, the value of appnLocalTgOperational 522 in the notification shall be 'false', since the deletion of 523 a row indicates that the TG is no longer operational. 524 </p><p> 525 The notification is more than a simple 'poll me now' indication. 526 It carries both a count of local TG topology changes, and the 527 current operational state itself. The count of changes allows an 528 application to detect lost notifications, either when polling 529 or upon receiving a subsequent notification, at which point it 530 knows it must retrieve the entire appnLocalTgTable again. 531 This is the same count as used in the appnLocalCpCpStateChangeTrap. 532 A lost notification could indicate a local TG CP-CP session state 533 change or an operational state change. 534 </p><p> 535 Generation of this notification is controlled by the 536 appnTrapControl object.</p><table> 537 <tr><td><b> 538 appnLocalTgTableChanges</b></td><td>%parm[#1]% 539 </td><td><p;></p></td;></tr><tr><td><b> 540 appnLocalTgOperational</b></td><td>%parm[#2]% 541 </td><td><p;> 542 true(1) false(2)</p> 543 </td;></tr></table> 544 </descr> 545 <logmsg dest='logndisplay'><p>Cisco Event: APPN Operational Status Change.</p></logmsg> 546 <severity>Warning</severity> 547</event> 548 549<event> 550 <mask> 551 <maskelement> 552 <mename>id</mename> 553 <mevalue>.1.3.6.1.2.1.34.4</mevalue> 554 </maskelement> 555 <maskelement> 556 <mename>generic</mename> 557 <mevalue>6</mevalue> 558 </maskelement> 559 <maskelement> 560 <mename>specific</mename> 561 <mevalue>3</mevalue> 562 </maskelement> 563 </mask> 564 <uei>uei.opennms.org/vendor/Cisco/traps/appnLocalTgCpCpChangeTrap</uei> 565 <event-label>APPN-TRAP-MIB defined trap event: appnLocalTgCpCpChangeTrap</event-label> 566 <descr><p>When it has been enabled, this notification makes it possible 567 for an APPN topology application to get asynchronous 568 notifications of local TG control-point to control-point (CP-CP) 569 session state changes, and thus to reduce the 570 frequency with which it polls for these changes. 571 </p><p> 572 This notification is sent whenever there is a change to 573 the appnLocalTgCpCpSession object but NOT the 574 appnLocalTgOperational object in a row of the appnLocalTgTable. 575 This notification is never sent for appnLocalTgTable row 576 creation or deletion. 577 </p><p> 578 The notification is more than a simple 'poll me now' indication. 579 It carries both a count of local TG topology changes, and the 580 current CP-CP session state itself. The count of changes allows 581 an application to detect lost notifications, either when polling 582 or upon receiving a subsequent notification, at which point it 583 knows it must retrieve the entire appnLocalTgTable again. This 584 is the same count as used in the appnLocalTgOperStateChangeTrap. 585 A lost notification could indicate a local TG CP-CP session 586 state change or an operational state change. 587 </p><p> 588 Generation of this notification is controlled by the 589 appnTrapControl object.</p><table> 590 <tr><td><b> 591 appnLocalTgTableChanges</b></td><td>%parm[#1]% 592 </td><td><p;></p></td;></tr><tr><td><b> 593 appnLocalTgCpCpSession</b></td><td>%parm[#2]% 594 </td><td><p;> 595 supportedUnknownStatus(1) supportedActive(2) notSupported(3) supportedNotActive(4)</p> 596 </td;></tr></table> 597 </descr> 598 <logmsg dest='logndisplay'><p>Cisco Event: APPN Local Control-Point Change.</p></logmsg> 599 <severity>Warning</severity> 600</event> 601 602<event> 603 <mask> 604 <maskelement> 605 <mename>id</mename> 606 <mevalue>.1.3.6.1.2.1.34.4</mevalue> 607 </maskelement> 608 <maskelement> 609 <mename>generic</mename> 610 <mevalue>6</mevalue> 611 </maskelement> 612 <maskelement> 613 <mename>specific</mename> 614 <mevalue>4</mevalue> 615 </maskelement> 616 </mask> 617 <uei>uei.opennms.org/vendor/Cisco/traps/appnPortOperStateChangeTrap</uei> 618 <event-label>APPN-TRAP-MIB defined trap event: appnPortOperStateChangeTrap</event-label> 619 <descr><p>When it has been enabled, this notification makes it possible 620 for an APPN topology application to get asynchronous 621 notifications of port operational state changes, and thus to 622 reduce the frequency with which it polls for these changes. 623 This notification is only sent when a appnPortOperState has 624 transitioned to a value of 'active' or 'inactive'. 625 </p><p> 626 This notification is sent whenever there is a appnPortOperState 627 object transition to 'inactive' or 'active' state in the 628 appnPortTable. This notification is only sent for row creation 629 if the row is created with a value of 'active' for 630 appnPortOperState. This notification is only sent for 631 row deletion if the last value of appnPortOperState was 632 'active'. In this case, the value of appnPortOperState 633 in the notification shall be 'inactive', since the deletion of 634 a row indicates that the port is no longer active. 635 </p><p> 636 The notification is more than a simple 'poll me now' indication. 637 It carries both a count of port table changes, and the 638 operational state itself. The count of changes allows an 639 application to detect lost notifications, either when polling 640 or upon receiving a subsequent notification, at which point 641 it knows it must retrieve the entire appnPortTable again. 642 </p><p> 643 Generation of this notification is controlled by the 644 appnTrapControl object.</p><table> 645 <tr><td><b> 646 appnPortTableChanges</b></td><td>%parm[#1]% 647 </td><td><p;></p></td;></tr><tr><td><b> 648 appnPortOperState</b></td><td>%parm[#2]% 649 </td><td><p;> 650 inactive(1) pendactive(2) active(3) pendinact(4)</p> 651 </td;></tr></table> 652 </descr> 653 <logmsg dest='logndisplay'><p>Cisco Event: APPN Port Operational Status Change.</p></logmsg> 654 <severity>Warning</severity> 655</event> 656 657<event> 658 <mask> 659 <maskelement> 660 <mename>id</mename> 661 <mevalue>.1.3.6.1.2.1.34.4</mevalue> 662 </maskelement> 663 <maskelement> 664 <mename>generic</mename> 665 <mevalue>6</mevalue> 666 </maskelement> 667 <maskelement> 668 <mename>specific</mename> 669 <mevalue>5</mevalue> 670 </maskelement> 671 </mask> 672 <uei>uei.opennms.org/vendor/Cisco/traps/appnLsOperStateChangeTrap</uei> 673 <event-label>APPN-TRAP-MIB defined trap event: appnLsOperStateChangeTrap</event-label> 674 <descr><p>When it has been enabled, this notification makes it possible 675 for an APPN topology application to get asynchronous 676 notifications of link station operational state changes, and 677 thus to reduce the frequency with which it polls for these 678 changes. This notification is only sent when a appnLsOperState 679 has transitioned to a value of 'active' or 'inactive'. 680 </p><p> 681 This notification is sent whenever there is a appnLsOperState 682 </p><p> 683 object transition to 'inactive' or 'active' state in the 684 appnLsTable. This notification is only sent for row creation 685 if the row is created with a value of 'active' for 686 appnLsOperState. This notification is only sent for 687 row deletion if the last value of appnLsOperState was 688 'active'. In this case, the value of appnLsOperState 689 in the notification shall be 'inactive', since the deletion of 690 a row indicates that the link station is no longer active. 691 </p><p> 692 The notification is more than a simple 'poll me now' indication. 693 It carries both a count of link station table changes, and the 694 operational state itself. The count of changes allows an 695 application to detect lost notifications, either when polling 696 or upon receiving a subsequent notification, at which point it 697 knows it must retrieve the entire appnLsTable again. 698 </p><p> 699 Generation of this notification is controlled by the 700 appnTrapControl object.</p><table> 701 <tr><td><b> 702 appnLsTableChanges</b></td><td>%parm[#1]% 703 </td><td><p;></p></td;></tr><tr><td><b> 704 appnLsOperState</b></td><td>%parm[#2]% 705 </td><td><p;> 706 inactive(1) sentConnectOut(2) pendXidExch(3) sendActAs(4) sendSetMode(5) otherPendingActive(6) 707 active(7) sentDeactAsOrd(8) sentDiscOrd(9) sentDiscImmed(10) otherPendingInact(11)</p> 708 </td;></tr></table> 709 </descr> 710 <logmsg dest='logndisplay'><p>Cisco Event: APPN Link Station Operational Status Change.</p></logmsg> 711 <severity>Warning</severity> 712</event> 713 714<event> 715 <mask> 716 <maskelement> 717 <mename>id</mename> 718 <mevalue>.1.3.6.1.2.1.34.4</mevalue> 719 </maskelement> 720 <maskelement> 721 <mename>generic</mename> 722 <mevalue>6</mevalue> 723 </maskelement> 724 <maskelement> 725 <mename>specific</mename> 726 <mevalue>6</mevalue> 727 </maskelement> 728 </mask> 729 <uei>uei.opennms.org/vendor/Cisco/traps/dlurDlusStateChangeTrap</uei> 730 <event-label>APPN-TRAP-MIB defined trap event: dlurDlusStateChangeTrap</event-label> 731 <descr><p>When it has been enabled, this notification makes it possible 732 for an APPN topology application to get asynchronous 733 notifications of DLUR-DLUS session changes, and thus to reduce 734 the frequency with which it polls for these changes. 735 </p><p> 736 This notification is sent whenever there is a dlurDlusSessnStatus 737 object transition to 'inactive' or 'active' state in the 738 dlurDlusTable. This notification is only sent for row creation 739 if the row is created with a value of 'active' for 740 dlurDlusSessnStatus. This notification is only sent for 741 row deletion if the last value of dlurDlusSessnStatus was 742 'active'. In this case, the value of dlurDlusSessnStatus 743 in the notification shall be 'inactive', since the deletion of 744 a row indicates that the session is no longer active. 745 </p><p> 746 The notification is more than a simple 'poll me now' indication. 747 It carries both a count of DLUR-DLUS table changes, and the 748 session status itself. The count of changes allows an 749 </p><p> 750 application to detect lost notifications, either when polling 751 or upon receiving a subsequent notification, at which point it 752 knows it must retrieve the entire dlurDlusTable again. 753 </p><p> 754 Generation of this notification is controlled by the 755 appnTrapControl object.</p><table> 756 <tr><td><b> 757 dlurDlusTableChanges</b></td><td>%parm[#1]% 758 </td><td><p;></p></td;></tr><tr><td><b> 759 dlurDlusSessnStatus</b></td><td>%parm[#2]% 760 </td><td><p;> 761 reset(1) pendingActive(2) active(3) pendingInactive(4)</p> 762 </td;></tr></table> 763 </descr> 764 <logmsg dest='logndisplay'><p>Cisco Event: APPN DLUR-DLUS Session Change.</p></logmsg> 765 <severity>Warning</severity> 766</event> 767<!-- End of Cisco MIB: APPN-TRAP-MIB --> 768<!-- Start of Cisco MIB: ATM-SOFT-PVC-MIB --> 769<event> 770 <mask> 771 <maskelement> 772 <mename>id</mename> 773 <mevalue>.1.3.6.1.4.1.353.5.5.1.2.1</mevalue> 774 </maskelement> 775 <maskelement> 776 <mename>generic</mename> 777 <mevalue>6</mevalue> 778 </maskelement> 779 <maskelement> 780 <mename>specific</mename> 781 <mevalue>1</mevalue> 782 </maskelement> 783 </mask> 784 <uei>uei.opennms.org/vendor/Cisco/traps/atmSoftPvcCallFailuresTrap</uei> 785 <event-label>ATM-SOFT-PVC-MIB defined trap event: atmSoftPvcCallFailuresTrap</event-label> 786 <descr><p>A notification indicating that one or more series of 787 call attempts in trying to establish a Soft PVPC or 788 Soft PVCC have failed since the last 789 atmSoftPvcCallFailureTrap was sent. If this trap has 790 not been sent for the last atmSoftPvcNotificationInterval, 791 then it will be sent on the next increment of 792 atmSoftPvcCallFailures.</p><table> 793 <tr><td><b> 794 atmSoftPvcCallFailures</b></td><td>%parm[#1]% 795 </td><td><p;></p></td;></tr><tr><td><b> 796 atmSoftPvcCurrentlyFailingSoftPVccs</b></td><td>%parm[#2]% 797 </td><td><p;></p></td;></tr><tr><td><b> 798 atmSoftPvcCurrentlyFailingSoftPVpcs</b></td><td>%parm[#3]% 799 </td><td><p;></p></td;></tr></table> 800 </descr> 801 <logmsg dest='logndisplay'><p>Cisco Events: ATM Soft PVC call failed.</p></logmsg> 802 <severity>Warning</severity> 803</event> 804<!-- End of Cisco MIB: ATM-SOFT-PVC-MIB --> 805<!-- Start of Cisco MIB: AWCVX-MIB --> 806<event> 807 <mask> 808 <maskelement> 809 <mename>id</mename> 810 <mevalue>.1.3.6.1.4.1.522</mevalue> 811 </maskelement> 812 <maskelement> 813 <mename>generic</mename> 814 <mevalue>6</mevalue> 815 </maskelement> 816 <maskelement> 817 <mename>specific</mename> 818 <mevalue>4</mevalue> 819 </maskelement> 820 </mask> 821 <uei>uei.opennms.org/vendor/Cisco/traps/awcTrapLog</uei> 822 <event-label>AWCVX-MIB defined trap event: awcTrapLog</event-label> 823 <descr><p>SNMP trap corresponding to an event with a Severity 824 Level requiring Notify Disposition while 825 awcEventAlertSNMP is true.</p><table> 826 <tr><td><b> 827 awcEventTime</b></td><td>%parm[#1]% 828 </td><td><p;></p></td;></tr><tr><td><b> 829 awcEventSeverity</b></td><td>%parm[#2]% 830 </td><td><p;> 831 systemFatal(2) protocolFatal(3) portFatal(4) systemAlert(5) protocolAlert(6) portAlert(7) externalAlert(8) 832 systemWarning(9) protocolWarning(10) portWarning(11) externalWarning(12) systemInfo(13) protocolInfo(14) portInfo(15) 833 externalInfo(16)</p> 834 </td;></tr><tr><td><b> 835 awcEventDescription</b></td><td>%parm[#3]% 836 </td><td><p;></p></td;></tr></table> 837 </descr> 838 <logmsg dest='logndisplay'><p>Cisco Event: AWC Event: %parm[#3]%.</p></logmsg> 839 <severity>Warning</severity> 840</event> 841<!-- End of Cisco MIB: AWCVX-MIB --> 842<!-- Start of Cisco MIB: CISCO-5800-HEALTH-MON-MIB --> 843<event> 844 <mask> 845 <maskelement> 846 <mename>id</mename> 847 <mevalue>.1.3.6.1.4.1.9.10.28.3</mevalue> 848 </maskelement> 849 <maskelement> 850 <mename>generic</mename> 851 <mevalue>6</mevalue> 852 </maskelement> 853 <maskelement> 854 <mename>specific</mename> 855 <mevalue>1</mevalue> 856 </maskelement> 857 </mask> 858 <uei>uei.opennms.org/vendor/Cisco/traps/ciscoHealthMonNotification</uei> 859 <event-label>CISCO-5800-HEALTH-MON-MIB defined trap event: ciscoHealthMonNotification</event-label> 860 <descr><p>A ciscoHealthMonNotification is sent if the measured 861 utilization has crossed the threshold value. It will be generated 862 when the value rises above the threshold. ciscoHealthMonShelfId and 863 ciscoHealthMonAddress are optional entries. This entry is valid only 864 if the notification generated for the monitoring types set on the 865 router shelf. This entry will not have anything if notification is 866 generated for the monitoring types set on the system controller.</p><table> 867 <tr><td><b> 868 ciscoHealthMonStatusType</b></td><td>%parm[#1]% 869 </td><td><p;></p></td;></tr><tr><td><b> 870 ciscoHealthMonShelfId</b></td><td>%parm[#2]% 871 </td><td><p;></p></td;></tr><tr><td><b> 872 ciscoHealthMonAddress</b></td><td>%parm[#3]% 873 </td><td><p;></p></td;></tr><tr><td><b> 874 ciscoHealthMonDescr</b></td><td>%parm[#4]% 875 </td><td><p;></p></td;></tr><tr><td><b> 876 ciscoHealthMonValue</b></td><td>%parm[#5]% 877 </td><td><p;></p></td;></tr><tr><td><b> 878 ciscoHealthMonThreshold</b></td><td>%parm[#6]% 879 </td><td><p;></p></td;></tr></table> 880 </descr> 881 <logmsg dest='logndisplay'><p>Cisco Event: Utilization over threshold.</p></logmsg> 882 <severity>Warning</severity> 883 <alarm-data reduction-key="%uei%:%dpname%:%nodeid%" alarm-type="3" auto-clean="false"/> 884</event> 885<!-- End of Cisco MIB: CISCO-5800-HEALTH-MON-MIB --> 886<!-- Start of Cisco MIB: CISCO-6400-CHASSIS-MIB --> 887<event> 888 <mask> 889 <maskelement> 890 <mename>id</mename> 891 <mevalue>.1.3.6.1.4.1.9.10.27.2</mevalue> 892 </maskelement> 893 <maskelement> 894 <mename>generic</mename> 895 <mevalue>6</mevalue> 896 </maskelement> 897 <maskelement> 898 <mename>specific</mename> 899 <mevalue>1</mevalue> 900 </maskelement> 901 </mask> 902 <uei>uei.opennms.org/vendor/Cisco/traps/cisco6400ChassisFailureNotification</uei> 903 <event-label>CISCO-6400-CHASSIS-MIB defined trap event: cisco6400ChassisFailureNotification</event-label> 904 <descr><p>The notification signifies that the agent detects a change in 905 the c64ChassisAlarmTable, the NMS application should start 906 to poll the c64ChassisAlarmTable to get up-to-date alarm 907 information.</p><table> 908 <tr><td><b> 909 c64ChassisFacilityAlarmStatus</b></td><td>%parm[#1]% 910 </td><td><p;></p></td;></tr></table> 911 </descr> 912 <logmsg dest='logndisplay'><p>Cisco Event: Cisco 6400 Chassis Alarm status change.</p></logmsg> 913 <severity>Warning</severity> 914</event> 915<!-- End of Cisco MIB: CISCO-6400-CHASSIS-MIB --> 916<!-- Start of Cisco MIB: Cisco90Series-MIB --> 917<event> 918 <mask> 919 <maskelement> 920 <mename>id</mename> 921 <mevalue>.1.3.6.1.4.1.1570.1</mevalue> 922 </maskelement> 923 <maskelement> 924 <mename>generic</mename> 925 <mevalue>6</mevalue> 926 </maskelement> 927 <maskelement> 928 <mename>specific</mename> 929 <mevalue>1</mevalue> 930 </maskelement> 931 </mask> 932 <uei>uei.opennms.org/vendor/Cisco/traps/frxDownloadTrap</uei> 933 <event-label>Cisco90Series-MIB defined trap event: frxDownloadTrap</event-label> 934 <descr><p>This trap is sent if the Download Config pushbutton 935 on the channel unit faceplate is pushed and frxDefaultTrap 936 is set to 1.</p><table> 937 <tr><td><b> 938 frxBankIndex</b></td><td>%parm[#1]% 939 </td><td><p;></p></td;></tr><tr><td><b> 940 frxChUIndex</b></td><td>%parm[#2]% 941 </td><td><p;></p></td;></tr></table> 942 </descr> 943 <logmsg dest='logndisplay'><p>Cisco Event: Series 90 Download Config activated.</p></logmsg> 944 <severity>Warning</severity> 945</event> 946 947<event> 948 <mask> 949 <maskelement> 950 <mename>id</mename> 951 <mevalue>.1.3.6.1.4.1.1570.1</mevalue> 952 </maskelement> 953 <maskelement> 954 <mename>generic</mename> 955 <mevalue>6</mevalue> 956 </maskelement> 957 <maskelement> 958 <mename>specific</mename> 959 <mevalue>2</mevalue> 960 </maskelement> 961 </mask> 962 <uei>uei.opennms.org/vendor/Cisco/traps/frxUPerfTrap</uei> 963 <event-label>Cisco90Series-MIB defined trap event: frxUPerfTrap</event-label> 964 <descr><p>This trap is sent if a performance monitoring threshold 965 on a channel unit or a BRITE card is exceeded and the 966 corresponding bit in the frxAlertMask is enabled and 967 frxUPerfTrapEnable is enabled. The manager should read 968 and clear all of the threshold condition registers 969 for the specified channel unit to enable the trap to 970 be sent again.</p><table> 971 <tr><td><b> 972 frxBankIndex</b></td><td>%parm[#1]% 973 </td><td><p;></p></td;></tr><tr><td><b> 974 frxChUIndex</b></td><td>%parm[#2]% 975 </td><td><p;></p></td;></tr></table> 976 </descr> 977 <logmsg dest='logndisplay'><p>Cisco Event: Series 90 Performance Monitoring Threshold Exceeded.</p></logmsg> 978 <severity>Warning</severity> 979</event> 980 981<event> 982 <mask> 983 <maskelement> 984 <mename>id</mename> 985 <mevalue>.1.3.6.1.4.1.1570.1</mevalue> 986 </maskelement> 987 <maskelement> 988 <mename>generic</mename> 989 <mevalue>6</mevalue> 990 </maskelement> 991 <maskelement> 992 <mename>specific</mename> 993 <mevalue>3</mevalue> 994 </maskelement> 995 </mask> 996 <uei>uei.opennms.org/vendor/Cisco/traps/frxInsertChUTrap</uei> 997 <event-label>Cisco90Series-MIB defined trap event: frxInsertChUTrap</event-label> 998 <descr><p>This trap is sent when the channel unit is inserted.</p><table> 999 <tr><td><b> 1000 frxBankIndex</b></td><td>%parm[#1]% 1001 </td><td><p;></p></td;></tr><tr><td><b> 1002 frxChUIndex</b></td><td>%parm[#2]% 1003 </td><td><p;></p></td;></tr></table> 1004 </descr> 1005 <logmsg dest='logndisplay'><p>Cisco Event: Series 90 Channel Unit Inserted.</p></logmsg> 1006 <severity>Normal</severity> 1007</event> 1008 1009<event> 1010 <mask> 1011 <maskelement> 1012 <mename>id</mename> 1013 <mevalue>.1.3.6.1.4.1.1570.1</mevalue> 1014 </maskelement> 1015 <maskelement> 1016 <mename>generic</mename> 1017 <mevalue>6</mevalue> 1018 </maskelement> 1019 <maskelement> 1020 <mename>specific</mename> 1021 <mevalue>4</mevalue> 1022 </maskelement> 1023 </mask> 1024 <uei>uei.opennms.org/vendor/Cisco/traps/frxRemoveChUTrap</uei> 1025 <event-label>Cisco90Series-MIB defined trap event: frxRemoveChUTrap</event-label> 1026 <descr><p>This trap is sent when the channel unit is removed.</p><table> 1027 <tr><td><b> 1028 frxBankIndex</b></td><td>%parm[#1]% 1029 </td><td><p;></p></td;></tr><tr><td><b> 1030 frxChUIndex</b></td><td>%parm[#2]% 1031 </td><td><p;></p></td;></tr></table> 1032 </descr> 1033 <logmsg dest='logndisplay'><p>Cisco Event: Series 90 Channel Unit Removed.</p></logmsg> 1034 <severity>Minor</severity> 1035</event> 1036 1037<event> 1038 <mask> 1039 <maskelement> 1040 <mename>id</mename> 1041 <mevalue>.1.3.6.1.4.1.1570.1</mevalue> 1042 </maskelement> 1043 <maskelement> 1044 <mename>generic</mename> 1045 <mevalue>6</mevalue> 1046 </maskelement> 1047 <maskelement> 1048 <mename>specific</mename> 1049 <mevalue>5</mevalue> 1050 </maskelement> 1051 </mask> 1052 <uei>uei.opennms.org/vendor/Cisco/traps/frxDConfigFailed</uei> 1053 <event-label>Cisco90Series-MIB defined trap event: frxDConfigFailed</event-label> 1054 <descr><p>This trap is sent if downloading configuration data 1055 to a channel unit fails.</p><table> 1056 <tr><td><b> 1057 frxBankIndex</b></td><td>%parm[#1]% 1058 </td><td><p;></p></td;></tr><tr><td><b> 1059 frxChUIndex</b></td><td>%parm[#2]% 1060 </td><td><p;></p></td;></tr></table> 1061 </descr> 1062 <logmsg dest='logndisplay'><p>Cisco Event: Series 90 Channel Unit Download Failure.</p></logmsg> 1063 <severity>Minor</severity> 1064</event> 1065<!-- End of Cisco MIB: Cisco90Series-MIB --> 1066<!-- Start of Cisco MIB: CISCO-AAA-SERVER-MIB --> 1067<event> 1068 <mask> 1069 <maskelement> 1070 <mename>id</mename> 1071 <mevalue>.1.3.6.1.4.1.9.10.56.2</mevalue> 1072 </maskelement> 1073 <maskelement> 1074 <mename>generic</mename> 1075 <mevalue>6</mevalue> 1076 </maskelement> 1077 <maskelement> 1078 <mename>specific</mename> 1079 <mevalue>1</mevalue> 1080 </maskelement> 1081 </mask> 1082 <uei>uei.opennms.org/vendor/Cisco/traps/casServerStateChange</uei> 1083 <event-label>CISCO-AAA-SERVER-MIB defined trap event: casServerStateChange</event-label> 1084 <descr><p>An AAA server state change notification is generated 1085 whenever casState changes value. 1086 </p><table> 1087 <tr><td><b> 1088 casState</b></td><td>%parm[#1]% 1089 </td><td><p;> 1090 up(1) dead(2)</p></td;></tr><tr><td><b> 1091 casPreviousStateDuration</b></td><td>%parm[#2]% 1092 </td><td><p;></p></td;></tr><tr><td><b> 1093 casTotalDeadTime</b></td><td>%parm[#3]% 1094 </td><td><p;></p></td;></tr></table> 1095 </descr> 1096 <logmsg dest='logndisplay'><p>Cisco Event: AAA server casStatus change.</p></logmsg> 1097 <severity>Warning</severity> 1098</event> 1099<!-- End of Cisco MIB: CISCO-AAA-SERVER-MIB --> 1100<!-- Start of Cisco MIB: CISCO-ACCESS-ENVMON-MIB --> 1101<event> 1102 <mask> 1103 <maskelement> 1104 <mename>id</mename> 1105 <mevalue>.1.3.6.1.4.1.9.9.61.2</mevalue> 1106 </maskelement> 1107 <maskelement> 1108 <mename>generic</mename> 1109 <mevalue>6</mevalue> 1110 </maskelement> 1111 <maskelement> 1112 <mename>specific</mename> 1113 <mevalue>1</mevalue> 1114 </maskelement> 1115 </mask> 1116 <uei>uei.opennms.org/vendor/Cisco/traps/caemTemperatureNotification</uei> 1117 <event-label>CISCO-ACCESS-ENVMON-MIB defined trap event: caemTemperatureNotification</event-label> 1118 <descr><p>A caemTemperatureNotification is sent if the over temperature 1119 condition is detected in the managed system. 1120 This is a replacement for the ciscoEnvMonTemperatureNotification 1121 trap because the information 'ciscoEnvMonTemperatureStatusValue' 1122 required by the trap is not available in the managed system. 1123 </p><table> 1124 <tr><td><b> 1125 ciscoEnvMonTemperatureStatusDescr</b></td><td>%parm[#1]% 1126 </td><td><p;></p></td;></tr><tr><td><b> 1127 ciscoEnvMonTemperatureState</b></td><td>%parm[#2]% 1128 </td><td><p;> 1129 normal(1) warning(2) critical(3) shutdown(4) notPresent(5)</p> 1130 </td;></tr></table> 1131 </descr> 1132 <logmsg dest='logndisplay'><p>Cisco Event: Device over-temperature.</p></logmsg> 1133 <severity>Major</severity> 1134</event> 1135 1136<event> 1137 <mask> 1138 <maskelement> 1139 <mename>id</mename> 1140 <mevalue>.1.3.6.1.4.1.9.9.61.2</mevalue> 1141 </maskelement> 1142 <maskelement> 1143 <mename>generic</mename> 1144 <mevalue>6</mevalue> 1145 </maskelement> 1146 <maskelement> 1147 <mename>specific</mename> 1148 <mevalue>2</mevalue> 1149 </maskelement> 1150 </mask> 1151 <uei>uei.opennms.org/vendor/Cisco/traps/caemVoltageNotification</uei> 1152 <event-label>CISCO-ACCESS-ENVMON-MIB defined trap event: caemVoltageNotification</event-label> 1153 <descr><p>A caemVoltageNotification is sent if the over voltage 1154 condition is detected and ciscoEnvMonVoltageState is not set 1155 to 'notPresent' in the managed system. 1156 This is a replacement for the ciscoEnvMonVoltageNotification 1157 trap because the information 'ciscoEnvMonVoltageStatusValue' 1158 required by the trap is not available in the managed system. 1159 </p><table> 1160 <tr><td><b> 1161 ciscoEnvMonVoltageStatusDescr</b></td><td>%parm[#1]% 1162 </td><td><p;></p></td;></tr><tr><td><b> 1163 ciscoEnvMonVoltageState</b></td><td>%parm[#2]% 1164 </td><td><p;> 1165 normal(1) warning(2) critical(3) shutdown(4) notPresent(5)</p> 1166 </td;></tr></table> 1167 </descr> 1168 <logmsg dest='logndisplay'><p>Cisco Event: Device over-voltage.</p></logmsg> 1169 <severity>Minor</severity> 1170 <alarm-data reduction-key="%uei%:%dpname%:%nodeid%" alarm-type="3" auto-clean="false"/> 1171</event> 1172<!-- End of Cisco MIB: CISCO-ACCESS-ENVMON-MIB --> 1173<!-- Start of Cisco MIB: CISCO-ALPS-MIB --> 1174<event> 1175 <mask> 1176 <maskelement> 1177 <mename>id</mename> 1178 <mevalue>.1.3.6.1.4.1.9.9.95.2</mevalue> 1179 </maskelement> 1180 <maskelement> 1181 <mename>generic</mename> 1182 <mevalue>6</mevalue> 1183 </maskelement> 1184 <maskelement> 1185 <mename>specific</mename> 1186 <mevalue>1</mevalue> 1187 </maskelement> 1188 </mask> 1189 <uei>uei.opennms.org/vendor/Cisco/traps/alpsPeerStatusChange</uei> 1190 <event-label>CISCO-ALPS-MIB defined trap event: alpsPeerStatusChange</event-label> 1191 <descr><p>This Notification is generated when there is a change in state 1192 for the peer connection, provided alarms are enabled for 1193 that peer.</p><table> 1194 <tr><td><b> 1195 alpsRemPeerState</b></td><td>%parm[#1]% 1196 </td><td><p;> 1197 closed(1) opening(2) opened(3)</p> 1198 </td;></tr></table> 1199 </descr> 1200 <logmsg dest='logndisplay'><p>Cisco Event: ALPS Peer State Change.</p></logmsg> 1201 <severity>Warning</severity> 1202</event> 1203 1204<event> 1205 <mask> 1206 <maskelement> 1207 <mename>id</mename> 1208 <mevalue>.1.3.6.1.4.1.9.9.95.2</mevalue> 1209 </maskelement> 1210 <maskelement> 1211 <mename>generic</mename> 1212 <mevalue>6</mevalue> 1213 </maskelement> 1214 <maskelement> 1215 <mename>specific</mename> 1216 <mevalue>2</mevalue> 1217 </maskelement> 1218 </mask> 1219 <uei>uei.opennms.org/vendor/Cisco/traps/alpsCktStatusChange</uei> 1220 <event-label>CISCO-ALPS-MIB defined trap event: alpsCktStatusChange</event-label> 1221 <descr><p>This Notification has to be generated whenever there is a 1222 state change for the ALPS circuit, provided alarms are 1223 enabled for that circuit</p><table> 1224 <tr><td><b> 1225 alpsCktBaseState</b></td><td>%parm[#1]% 1226 </td><td><p;> 1227 disabled(1) inoperable(2) opening(3) opened(4) cktBusy(5) peerBusy(6) updating(7)</p> 1228 </td;></tr></table> 1229 </descr> 1230 <logmsg dest='logndisplay'><p>Cisco Event: ALPS Circuit Status Change.</p></logmsg> 1231 <severity>Warning</severity> 1232</event> 1233 1234<event> 1235 <mask> 1236 <maskelement> 1237 <mename>id</mename> 1238 <mevalue>.1.3.6.1.4.1.9.9.95.2</mevalue> 1239 </maskelement> 1240 <maskelement> 1241 <mename>generic</mename> 1242 <mevalue>6</mevalue> 1243 </maskelement> 1244 <maskelement> 1245 <mename>specific</mename> 1246 <mevalue>3</mevalue> 1247 </maskelement> 1248 </mask> 1249 <uei>uei.opennms.org/vendor/Cisco/traps/alpsAscuStatusChange</uei> 1250 <event-label>CISCO-ALPS-MIB defined trap event: alpsAscuStatusChange</event-label> 1251 <descr><p>This Notification has to be generated whenever there is a 1252 change in ASCU status, provided alarms are enabled for 1253 that ASCU</p><table> 1254 <tr><t…
Large files files are truncated, but you can click here to view the full file