Hi.. we are not seeing this behavior, as we do get the trap, event etc.. it is the varbind data not being translated properly and sometimes there is incomplete information being displayed. Someone from CA has suggested building event procedures, but looks pretty difficult considering number variables with in the mibs that needs to be queried.. Regards, John
________________________________ From: Mark Serencha [mailto:[email protected]] Sent: 2010, November, 05 12:34 PM To: spectrum Subject: RE: [spectrum] Cisco Entity and FRU Control Trap translation Hi list, I just ran into a known bug in 9.1 H12 where SNMP v2 traps from Cisco devices (and perhaps other devices) are not decoded properly. Spectrum will log an event 0x10801 (unknown trap) for any SNMP v2 trap (including but not limited to link down, link up, cold start, warm start, auth failure, Cisco syslog, and other Cisco related traps). And I think event code 0x01801 is not set to log itself to the DDM database, so if you are not watching your device's Events tab when it comes in, you won't see it after it occurs. Workaround - have your Cisco devices trap with SNMP v1. Annoying but effective. Fix - Apply 9.1 H14. I have tested and confirmed the fix in my lab, scheduling production patch now. However H14 also updates the minimum JRE requirement from 1.6.0_U7 to 1.6.0_U17 This is something to consider before pushing out H14. HTH, --Mark S ________________________________ Mark Serencha - Inforonics LLC - (m) +1-781-439-0519 - (w) +1-978-698-7418 - Mark.Serencha_AT_inforonics.com <mailto:[email protected]> From: Sobrinho, John [mailto:[email protected]] Sent: Friday, November 05, 2010 11:54 AM To: spectrum Subject: [spectrum] Cisco Entity and FRU Control Trap translation Hi All. Just wanted to know if any one has successfully created Event Procedures, or any other work around for Spectrum to properly interpret the trap messages into a more human readable format. ? Seems in my testbed, A simpler freeware utility is able to interpret correctly with the mibs loaded, but no luck with Spectrum. _______________________________________________________________________ This e-mail may be privileged and/or confidential, and the sender does not waive any related rights and obligations. Any distribution, use or copying of this e-mail or the information it contains by other than an intended recipient is unauthorized. If you received this e-mail in error, please advise me (by return e-mail or otherwise) immediately. Ce courriel peut contenir des renseignements protégés et confidentiels. Lexpéditeur ne renonce pas aux droits et obligations qui sy rapportent. Toute diffusion, utilisation ou copie de ce courriel ou des renseignements quil contient par une personne autre que le destinataire désigné est interdite. Si vous recevez ce courriel par erreur, veuillez men aviser immédiatement, par retour de courriel ou par un autre moyen. * --To unsubscribe from spectrum, send email to [email protected] with the body: unsubscribe spectrum [email protected] * --To unsubscribe from spectrum, send email to [email protected] with the body: unsubscribe spectrum [email protected] --- To unsubscribe from spectrum, send email to [email protected] with the body: unsubscribe spectrum [email protected]
