Hi,
thanks for your answers, but exactly this rules were used on a 7.1 System without error messages. I will check and give you a response. Gruß Dietmar Freitag Systemengineer Operation Support Systems | Alcatel-Lucent Network Services GmbH Parsevalstrasse 9a | 40468 Duesseldorf | Deutschland T: + 49 211 448 2536 F: + 49 211 448 2944 M: + 49 177 448 2536 E: [EMAIL PROTECTED] Sitz der Gesellschaft: Duesseldorf - Amtsgericht Duesseldorf HRB 55564 Geschaeftsfuehrung: Christian Bruckner, Volker Westphal ________________________________ Von: F J Rutcho [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 28. Oktober 2008 18:24 An: spectrum Betreff: RE: [spectrum] Any differences regarding Event Condition Rule between 7.1 and 8.1 known? Based on your extract, it appears that ffff106, 107, 108, and 109 are keyed wrong. Event codes need to be 8 characters in length when starting with a non-zero. Otherwise a zero is "assumed" at the start of the event. Using the pattern that appears you've established, I would think the events would be ffff1006, 1007, 1008, and 1009. ________________________________ Subject: [spectrum] Any differences regarding Event Condition Rule between 7.1 and 8.1 known? Date: Tue, 28 Oct 2008 14:39:28 +0100 From: [EMAIL PROTECTED] To: [email protected] Hi list, does anybody have problems with Event Condition Rules in the Eventdisp files under 8.1? We have several rules user with 7.1 and they are all working fine. Under 8.1 we want to use the same rules, but in the activated EvenDisp Logfile, the Rules are marked as invalid. "2008/10/28 14:18:48: Error in file CA.EventCondition Error parsing event parameter string ("ffff1005 1-3:1-3"): syntax error" Extract of the Eventdisp File: 0xffff1000 R { 7 } Aprisma.EventCondition, \ "{v 2} == {X 20.0.0.0}", "ffff1002 1-3:1-3", \ "{v 2} == {X 10.0.0.0}", "ffff1003 1-3:1-3", \ "{v 2} == {X 8.0.0.0}", "ffff1004 1-3:1-3", \ "{v 2} == {X 4.0.0.0}", "ffff1005 1-3:1-3", \ "{v 2} == {X 0.01.0.0}", "ffff106 1-3:1-3", \ "{v 2} == {X 0.0.80.0}", "ffff107 1-3:1-3", \ "{v 2} == {X 0.0.20.0}", "ffff108 1-3:1-3", \ "{v 2} == {X 0.0.10.0}", "ffff109 1-3:1-3", \ "{v 2} == {X 24.0.0.0}", "ffff1010 1-3:1-3", \ "{v 2} == {X 28.0.0.0}", "ffff1011 1-3:1-3", \ "{v 2} == {X 32.0.0.0}", "ffff1012 1-3:1-3", \ "{v 2} == {X 10.0.20.0}", "ffff1013 1-3:1-3", \ "{v 2} == {X 10.10.0.0}", "ffff1014 1-3:1-3", \ "{v 2} == {X 14.0.0.0}", "ffff1015 1-3:1-3", \ "{v 2} == {X 0.1.80.0}", "ffff1016 1-3:1-3", \ "{v 2} == {X C.0.0.0}", "ffff1017 1-3:1-3", \ "{v 2} == {X 80.0.0.0}", "ffff1001 1-3:1-3", \ "default", "ffff1099 1-3:1-3" During release update we switched from Solaris to Linux. Gruß Dietmar Freitag * --To unsubscribe from spectrum, send email to [EMAIL PROTECTED] with the body: unsubscribe spectrum [EMAIL PROTECTED] ________________________________ When your life is on the go-take your life with you. Try Windows Mobile® today <http://clk.atdmt.com/MRT/go/115298558/direct/01/> * --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]
