SNMP trap - Element Manager - CS1000 5.0 1

[Tman45]

We are trying to push our SNMP traps out of Element Manager to a location other than OTM. We setup the 2nd location (which happens to be Envision) but for some reason Envision can't see the traps. We are pretty sure it is set properly - we were wondering if you have to reboot Element Manager (the SigServer) in order for the traps to go to the new destination? Has anyone ran into this issue (trying to setup a new trap destination)?

 

[nhphoneguy]

AFAIK, it's the switch that sends the trap, not EM.
You can see the trap destinations if you go in under overlay 117 and prt open_alarm

 

[Avaya911PLM]

Once you make the changes in either the CLI or within Element Manager to the trap destination, you need to do a backup (or edd in LD 43) before that goes active. This is valid for new entries, or adding destinations.


--
Fletch
Avaya E9-1-1 Product Manager

 

[Tman45]

We have not issued an EDD since adding the trap destination, but our PBX does an automatic backup (and LD 43 routine) eery midnight - would that suffice or should we still issue an EDD for it? We are not getting the traps to our Envision, so I wondered if it could be something silly and simple like that - think I might just try it anyway. Any other suggestions?

 

[Avaya911PLM]

You can wait for the mids, but there should be no harm in running it now. The SNMP traps will start to flow as soon as the EDD starts. The first traps you see in fact will be the EDD event.



--
Fletch
Avaya E9-1-1 Product Manager

 

[Tman45]

Well no traps were picked up at EnVision - I don't understand why the EDD is not 'fixing' this.
We know our traps work on OTM we just can't add another site for some crazy reason. Anyone else have an idea?

 

[tikimon7]

http://www.bttsoftware.co.uk/snmptrap.html

There is a simple SNMP trap watcher I use to verify traps are going out. It is freeware and availible at abole link

 

[Tman45]

* for you tikimon7!! I just grabbed that freeware and it works like a champ on my local PC - so I verfied that SNMP is being sent after adding additional trap destinations (that is what I wasn't sure was working from EM). So, must be something with EnVision trying to capture these - but I believe it works VERY similar to this SNMP trap watcher so I don't understand right now
The only thing I see that MAY be suspect is that there are some 'junk' characters in front of the actual trap text - so I don't know if that is the trap watcher freeware or what is actually coming from our PBX - that could be messing with EnVision! Looks almost like a baud rate issue or terminal setting. I was going to post part of the log file but I can't get that piece to work for some reason (strange) - I tried changing the file paths and everything!