We have the same "buggy" behavior in Spectrum 9.1.2 that Mark is talking about. It's so bad we had to go back to running 8 on our old server for the time being. In the MIB tools when you go to map events Spectrum would offer up every event to be 0xffffffff and then from that point on when you try to start up the Event Configuration it hangs and crashes. Also, the spectroserver never stops after this, you have to manually kill it. We've been waiting for quite some time for support to help and have not gotten much help. I think we might just be going back to 8 for a long time.
Thanks, Scott From: Mark Serencha [mailto:[email protected]] Sent: Thursday, January 21, 2010 2:10 PM To: spectrum Cc: Rafael Kozlowski Subject: RE: [spectrum] event code numbering Importance: High Hi all, I've seen some buggy behavior with the automatic event code selection in 9.x. Between Event Configuration and MIB tools, there are at least 2 places where OneClick's assumption of the "next valid event ID" can get confused. MIB tools is especially dangerous because mapping MIB traps to events may overwrite a range of previously-built user-defined IDs all at once, and thus overwrite a lot of your custom work. Event Configuration gives you the opportunity to select the new or copied event ID, I recommend that you inspect this ID and verify that you have not used it already. I believe there is an option to select a starting ID in MIB tools as well, but it has been a while since I have used that feature. CA has provided me one patch for this bug already (for release 9.1.0), but the problem came back. We are updating to 9.1.2 next week, will advise the mailing list if this issue is resolved after the patch. Thank you, --Mark S ________________________________ Mark Serencha - Inforonics LLC - (m) +1-781-439-0519 - [email protected] <mailto:[email protected]> - ** Inforonics acquires Vigilant Enterprise Solutions ** <blocked::http://www.businesswire.com/portal/site/home/permalink/?ndmViewId=news_view&newsId=20090818005912&newsLang=en> From: Cutting, Jeremiah [mailto:[email protected]] Sent: Thursday, January 21, 2010 2:45 PM To: spectrum Cc: Rafael Kozlowski Subject: RE: [spectrum] event code numbering This looks like right to me. I added some additional events directly in EventDisp, reloaded events on the VNM in OneClick, and when I went to map a trap afterwards the event code matched the next value in sequence from the EventDisp. Interestingly, after I cancelled the map operation and tried to map again, the event code value automatically increased by 1, even though nothing new was actually added. So OneClick must be reading the value from EventDisp when the events are loaded, and then must track the value independently afterwards. Thanks, Jeremiah From: Rafael Kozlowski [mailto:[email protected]] Sent: Wednesday, January 20, 2010 11:47 PM To: Cutting, Jeremiah Subject: AW: [spectrum] event code numbering The event code value is generated from the default values If you has nothing in the custom/Event - no EventDisp file there so this will be created with the first value 0xfff00000 If you have one EventDisp in custom then the MIB Tool Event generator takes the next free from that EventDisp file Mit freundlichen Grüßen / Kind Regards Rafael Kozlowski DICOS GmbH Kommunikationssysteme Von: Cutting, Jeremiah [mailto:[email protected]] Gesendet: Mittwoch, 20. Januar 2010 22:55 An: spectrum Betreff: [spectrum] event code numbering Does anyone know how Spectrum 9.0 calculates the next event code value when mapping a trap? Is it a value in a database, file, etc.? Thanks, Jeremiah * --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] --- To unsubscribe from spectrum, send email to [email protected] with the body: unsubscribe spectrum [email protected]
