DX Unified Infrastructure Management

Hello,

I'm getting ldp lsp up/down traps from Juniper devices in bulk which are generating unnecessary alarms . To ignore these traps i mapped the trap to event code 0 in alert map file. But still getting the event for the same.

Please suggest if i have missed something..

Thanks,

Bijender

Which trap specifically are you referring to?

getting Labeled swiched path up/down traps from oids 1.3.6.1.4.1.2636.4.4.0.1 & 1.3.6.1.4.1.2636.4.4.0.2  and below are the lines which i have added in alartmap file.

.3.6.1.4.1.2636.4.4.0.1      0x0

.3.6.1.4.1.2636.4.4.0.2      0x0

Already updated the event configuration after doing changes in alertmap file.

You wrote:

.3.6.1.4.1.2636.4.4.0.1      0x0

.3.6.1.4.1.2636.4.4.0.2      0x0

Is it really what you have in your AlertMap, or your copy and paste failed partially and you missed the 1:

1.3.6.1.4.1.2636.4.4.0.1      0x0

1.3.6.1.4.1.2636.4.4.0.2      0x0

In which directory have you edited your AlertMap?

Hi Everyone,

Apologies !!

Actually by mistake i missed the 1 while typing in alertmap file. Now its working.

Thanks..

Dear all - please consider that CA Spectrum; once it receives the TRAP will process it. So even you wont see an Event by any specific TRAP the workload could become important. Especially for lsp up/down in a context of high number of devices the network device re-configuration and notifications (by these TRAPs) could become temporarily huge. Most likely this is seen in a context of a high number of these TRAPs from different devices which then sync's up again turning into a stable configuration (by dynamic negotiations). During this time you may find hundrets of TRAPs within 1 or 2 minutes. Therefore - in case you would not like to monitor these TRAPs - you may consider to disable them at device level. From an overall monitoring aspect these TRAPs (once happening on bulk across many devices) could point to a network problem (i.e. seeing this once per night - affecting all devices even you think there is no problem at all ...)   Cheers, Joerg

Maybe Jörg, but Bijender wants to reduce the number of alarms and the event 0x03b10030 from trap 1.3.6.1.4.1.2636.4.4.0.2 generates directly alarms, the other one clears:

0x03b10030 E 50 A 1, 0x03b10030

Sometimes, it is not possible to disable these traps because e.g. a port security solution needs them.

I don't know Bijenders environment and I'm not familiar with Juniper devices and this specific trap.

But, I think, very often is there one case with one device where we miss a trap wich we don't want have for hundred  other devices.

That's why, I would prefer changing the event.disp file instead of the AlertMap.

While we don't need the alarms or any other event handling is

     0x03b1002f

     0x03b10030

enough. The events occur and nothing more will happen. Also the ArchManager has no work with them.

But if you have the EventView open, during the Events occur, you will see them (temporarly).

Sometimes this is helpful.