Hi all, just wanted to let you know that I found a solution that fits my needs perfectly: With $SPECROOT/SS/CsVendor/Cabletron/EventDisp, I create "generic" events for any creation and clearance of a CRITICAL alarm (using Events 10701h, 10702h and 10706h and EventCondition rules), one for the assertion, another one with a different eventcode for deletion. At night, I browse all events for the ones in the time range from yesterday midnight to 11:59pm that match the handles I created for my generic events (this is done using mysql CLI, which is pretty fast). For I need only a time stamp, a modelhandle and my eventhandle value, there seems to be no better way.
The rest is some simple spaghetti shell scripting. If anyone is interested in details please contact me off-list. Freundliche Grüße / Best regards Christian Fieres Mainova AG Planung und Betrieb Infrastruktur (M3-ON2) Service Operation Center Solmsstraße 38 60623 Frankfurt Telefon / Phone (069) 2 13-2 36 17 Mobil / Mobile (0170) 5 60 15 63 Telefax / Facsimile (069) 2 13-9 62 36 17 E-Mail [EMAIL PROTECTED] Mainova Aktiengesellschaft - Solmsstraße 38 - D-60623 Frankfurt am Main Vorsitzende des Aufsichtsrates: Oberbürgermeisterin Dr. h. c. Petra Roth - Vorstand: Dr. Constantin Alsheimer, Lothar Herbst, Joachim Zientek Sitz der Aktiengesellschaft: Frankfurt am Main - Amtsgericht Frankfurt HRB 7173 - USt-ID-Nr. DE 114184034 ----- Weitergeleitet von Christian Fieres/M3-ON/MAINOVA/DE am 21.10.2008 14:09 ----- [EMAIL PROTECTED] 13.10.2008 14:45 Bitte antworten an [EMAIL PROTECTED] An "spectrum" <[email protected]> Kopie [EMAIL PROTECTED] Thema [spectrum] Outage Report(Virengetestet -> ok) Hi All, I need a CSV report (generated daily to import into Excel) that says which models were alarmed critical from which time on for how long during yesterday (i.e. an outage report which was AFAIR part of the old Report Generator). As easy as it seems, I have come along a few problems and need a little push into the right direction. My first idea was to browse via CLI all events for contact lost and re-gain and calculate everything myself with a little scripting. Too bad events for bad link alarms, Fanout alarms and Device alarms are all but the same. Second idea was to browse through all models periodically using a cron'ed CLI script looking for Condition values of 7 and have a look at those models next time my cronjob runs. Problem is that in a Fault Tolerant setup, I would have to do synchronizing. Third idea was to add two watches that trigger and log condition changes from 0 to 7 and vice versa and browse those events the next day, calculation done afterwards within the script. All solutions have their advantages and disadvantages and are surely not the gentleman way. Does anyone have an idea how to handle this with out-of-the-box features? I would need to further specify to ignore models that don't match a specific attribute=value condition, so a customizable solution via script is in favour. Maybe I am missing the most simple solution here? Freundliche Grüße / Best regards Christian Fieres Mainova AG Planung und Betrieb Infrastruktur (M3-ON2) Service Operation Center Solmsstraße 38 60623 Frankfurt Telefon / Phone (069) 2 13-2 36 17 Mobil / Mobile (0170) 5 60 15 63 Telefax / Facsimile (069) 2 13-9 62 36 17 E-Mail [EMAIL PROTECTED] Mainova Aktiengesellschaft - Solmsstraße 38 - D-60623 Frankfurt am Main Vorsitzende des Aufsichtsrates: Oberbürgermeisterin Dr. h. c. Petra Roth - Vorstand: Dr. Constantin Alsheimer, Lothar Herbst, Joachim Zientek Sitz der Aktiengesellschaft: Frankfurt am Main - Amtsgericht Frankfurt HRB 7173 - USt-ID-Nr. DE 114184034 --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]
