Untranslated traps from the Exchange Agent

[agmontes]

Hi,

We´ve recently installed the manager for the Exchange management option in a TND server. After installin the Exchange agent in an Exchange Server and discover it we find that most of the traps (not all) sent by the agent are not transtaled and appear raw as this:

%CATD_I_060, SNMPTRAP: -c public 791 10.25.15.2 morcl51.ree.es 6 7 00:00:00 1 OID: 1.3.6.1.4.1.791.2.10.2.5.8.6.1.11.37.92.77.83.69.120.99.104.97.110.103.101.73.83.92.65.99.116.105.118.101.32.67.111.110.110.101.99.116.105.111.110.32.67.111.117.110.116 .iso.org.dod.internet.private.enterprises.791.2.10.2.5.8.6.1.11.37.92.77.83.69.120.99.104.97.110.103.101.73.83.92.65.99.116.105.118.101.32.67.111.110.110.101.99.116.105.111.110.32.67.111.117.110.116 VALUE: 3

Another traps are correctly translated, as the ones relatives to exchange services.

Any idea how to solve this?

 

[JonnoGT]

It may be that you are recieving both - the translated trap and the raw trap.
There is a cfg file on your DSM server in tng\caiuser dir called catrapd.cfg

If the trap OID is not specified in this file you will receive the raw trap, even if it is being translated correctly.
EG: this line will mask out W2k agent traps (the DSM will still send a formatted message)
*:*:*:*:1.3.6.1.4.1.791.2.10.2.43 ignore # Windows2000 System Agent (caiW2kOs)

Alternatively, it could be that the version of exchange that you are on is not 100% compatible with the exchange agents mib on the DSM server.
I would try using mibbrowser or objectview to drill down and try to find to Agent area that this OID relates to. That should help you identify whether or not you need the trap.

 

[miteshlad2003]

Don't know if you can help me but i can't seem to even get the Exchange agents working.....

We are getting Dr Watsons when trying to start the exchange agents and also all the other agents processes are running except the agent process...

Any tips would really help!

Thanks

Miteshlad2003

 

[UberGeek27]

Another thing to check is the DSM_Server and DSM_Address instance-level properties in Worldview for this particular agent. They should be populated with either localhost/127.0.0.1 or the correct DSM name & address...

You might also want to look at aws_sadmin.cfg/access.cfg on the agent, and make sure that the DSM is authorized to manage the agent.

Have you ldatp'd the Agent Technology policy file for the Exchange agent? If you have, and the atp is in the proper location ($AGENTWORKS_DIR/services/config/aws_nsm/dm), a resetdsm might be in order to clean out your DSM store.