Thank you
On Apr 13, 2014, at 4:09 PM, Dan White <dan.wh...@devoteam.com> wrote:
>
> Dan White
> Senior Consultant
> Service Assurance
>
>
> Mob. : +44 (0)7973 533671
> dan.wh...@devoteam.com
>
> Follow us :
>
> CONNECTING BUSINESS & TECHNOLOGY
>
>
> ---------- Forwarded message ----------
> From: Dan White <dan.wh...@devoteam.com>
> Date: 13 April 2014 19:20
> Subject: Re: [spectrum] Need a bit of assistance with some rather long-winded
> event code.
> To: "Franck, Raphael" <raphael.fra...@computacenter.com>
>
>
> Dave,
> It's a while since you posted so you've either solved it or given up by now -
> sorry! (yes as Raphael said - event procedures would be needed to do
> something like the upper case and prepend text. )
>
> I just wanted to add that - no - you don't have to *manually* configure the
> event that's got the evproc individually on all your other landscapes...
>
> 1. do it manually just on your MLS by editing your custom/Events/EventDisp,
> then
>
> 2. Give the the MLS's SS a poke to re-read its event config via OneClick
> (e.g. VNM -> Information ->Spectroserver Control -> Update Event
> Configuration).
>
> 3. Refresh the Event Config Editor - Make sure "conflict" column is
> displayed. There'll be a *conflict* now for this event as the MLS's event
> def for this event is now different to the others landscapes so both versions
> of it will be listed.
> 4. Select File->synchnronise in the ECE (and then maybe save I think). Thus
> it will broadcast the MLS's event config for the new event to the rest of
> your SSs - including your event with the clever evproc in it.
>
> (Word of warning:
> I don't know about 9.3.x, but prior to that, if you use the ECE to edit
> *anything at all* about an event that's got an eventproc in its Rules - it
> truncates the eventproc bit thus corrupting it. So get everything else right
> about that event's config *before* you add in the evproc and do the above.
> You don't want to be editing it afterwards via ECE!).
>
> Cheers, Dan.
>
>
>
>
> Dan White
> Senior Consultant
> Service Assurance
>
>
> Mob. : +44 (0)7973 533671
> dan.wh...@devoteam.com
>
> Follow us :
>
> CONNECTING BUSINESS & TECHNOLOGY
>
>
> On 5 March 2014 08:01, Franck, Raphael <raphael.fra...@computacenter.com>
> wrote:
> Hi Dave, list,
>
>
> Do I need to create secondary events from the bff,cff,dff etc. events just to
> munge the alarm title?
> => yes, from my point of view
>
> And can it be done easily in ECE rather than via manual editing of the
> EventDisp which means I'd have to manually copy it to 25+ DSS landscapes?
> => not that I'm aware of since you probably need to make use of
> EventProcedures, which can't be configured using ECE.
>
> EventProcedures that might suit your needs:
>
> ${SPECROOT}/SS/CsVendor/CA/Procedures/
> Append.xml
> ToUpper.xml
>
> By the way, ECE will not destroy manual changes to EventDisp but remove any
> "nice" formatting.
>
> Mit freundlichen Gruessen - Yours sincerely
>
> Raphael Franck
> Consultant
> Global Infrastructure Operations
>
> Computacenter AG & Co oHG
> Services & Solutions
>
> Europaring 34-40, 50170 Kerpen, Germany
> E-Mail: raphael.fra...@computacenter.com
> WWW: www.computacenter.de
>
> Von: David Game [mailto:david.g...@uk.logicalis.com]
> Gesendet: Dienstag, 4. März 2014 18:55
> An: spectrum
> Betreff: [spectrum] Need a bit of assistance with some rather long-winded
> event code.
>
> I've been asked to make the ISDN disconnect alarm more useful as we were
> getting Critical alarms for something as simple as a normal call termination,
> leading to a lot of false positives.
>
> I've created what is essentially the Event Condition From Hell and have the
> original event generating one of 4 different severity events based on the
> disconnect code. Each of those 4 events (including the "no criticality,
> event only" one!) sets the alarm title dynamically from varbind 5 which is
> the "Plain Text" version of the disconnect code.
>
> What I'd like to do is that instead of just blindly passing the varbind into
> attribute 76620, I'd like to append it with "ISDN CALL FAILURE - " and also
> convert the text to upper case. So instead of, for example, "No
> circuit/channel available" it reads "ISDN CALL FAILURE - NO CIRCUIT/CHANNEL
> AVAILABLE"
>
> Here is the rather garbled code I currently have in EventDisp which was
> generated by ECE.
>
> 0x210b90 E 70 R { 6 } CA.EventCondition, "({v 6} == {S \"0x2\"} || {v 6} ==
> {S \"0x3\"} || {v 6} == {S \"0x6\"} || {v 6} == {S \"0x1D\"} || {v 6} == {S
> \"0x21\"} || {v 6} == {S \"0x22\"} || {v 6} == {S \"0x24\"} || {v 6} == {S
> \"0x2C\"} || {v 6} == {S \"0x2F\"} || {v 6} == {S \"0x3A\"} || {v 6} == {S
> \"0x3F\"} || {v 6} == {S \"0x41\"} || {v 6} == {S \"0x42\"} || {v 6} == {S
> \"0x43\"} || {v 6} == {S \"0x44\"} || {v 6} == {S \"0x45\"} || {v 6} == {S
> \"0x46\"} || {v 6} == {S \"0x4F\"} || {v 6} == {S \"0x52\"} || {v 6} == {S
> \"0x5B\"} || {v 6} == {S \"0x5C\"} || {v 6} == {S \"0x5F\"} || {v 6} == {S
> \"0x60\"})" , "0xff210bff 1-4:1-4,5:76620,6-8:6-8","({v 6} == {S \"0x4\"} ||
> {v 6} == {S \"0x5\"} || {v 6} == {S \"0x8\"} || {v 6} == {S \"0x9\"} || {v 6}
> == {S \"0xA\"} || {v 6} == {S \"0x15\"} || {v 6} == {S \"0x16\"} || {v 6} ==
> {S \"0x17\"} || {v 6} == {S \"0x18\"} || {v 6} == {S \"0x1B\"} || {v 6} == {S
> \"0x1C\"} || {v 6} == {S \"0x23\"} || {v 6} == {S \"0x25\"} || {v 6} == {S
> \"0x27\"} || {v 6} == {S \"0x28\"} || {v 6} == {S \"0x29\"} || {v 6} == {S
> \"0x2B\"} || {v 6} == {S \"0x2D\"} || {v 6} == {S \"0x2E\"} || {v 6} == {S
> \"0x31\"} || {v 6} == {S \"0x32\"} || {v 6} == {S \"0x33\"} || {v 6} == {S
> \"0x34\"} || {v 6} == {S \"0x35\"} || {v 6} == {S \"0x36\"} || {v 6} == {S
> \"0x37\"} || {v 6} == {S \"0x38\"} || {v 6} == {S \"0x39\"} || {v 6} == {S
> \"0x51\"} || {v 6} == {S \"0x53\"} || {v 6} == {S \"0x54\"} || {v 6} == {S
> \"0x55\"} || {v 6} == {S \"0x56\"} || {v 6} == {S \"0x58\"} || {v 6} == {S
> \"0x5D\"} || {v 6} == {S \"0x61\"} || {v 6} == {S \"0x62\"} || {v 6} == {S
> \"0x63\"} || {v 6} == {S \"0x64\"} || {v 6} == {S \"0x65\"} || {v 6} == {S
> \"0x66\"} || {v 6} == {S \"0x67\"} || {v 6} == {S \"0x6F\"} || {v 6} == {S
> \"0x7F\"})" , "0xff210cff 1-4:1-4,5:76620,6-8:6-8","({v 6} == {S \"0x11\"} ||
> {v 6} == {S \"0x12\"} || {v 6} == {S \"0xB\"} || {v 6} == {S \"0x13\"} || {v
> 6} == {S \"0x19\"} || {v 6} == {S \"0x1A\"} || {v 6} == {S \"0x1E\"} || {v 6}
> == {S \"0x57\"} || {v 6} == {S \"0x59\"} || {v 6} == {S \"0x5A\"})" ,
> "0xff210dff 1-4:1-4,5:76620,6-8:6-8","({v 6} == {S \"0x1\"} || {v 6} == {S
> \"0x7\"} || {v 6} == {S \"0x10\"} || {v 6} == {S \"0x1F\"})" , "0xff210eff
> 1-4:1-4,5:76620,6-8:6-8"
>
> 0xff210bff A 3,0xff210bff,8
> 0xff210cff A 2,0xff210cff,8
> 0xff210dff A 1,0xff210dff,8
> 0xff210eff
>
> Do I need to create secondary events from the bff,cff,dff etc. events just to
> munge the alarm title? And can it be done easily in ECE rather than via
> manual editing of the EventDisp which means I'd have to manually copy it to
> 25+ DSS landscapes? I'd rather not create a different condition for the
> original with manually input alarm titles and have 40+ custom alarm cause
> codes!
>
> Thanks & regards
>
> Dave
>
> David K. Game
> Consultant - Managed Service Centre (EU)
> Logicalis UK Ltd
>
> +44 (0) 7967 464365
> +44 (0) 1753 560553 / 777363
> +1 646 797 3283
> sip:david.g...@uk.logicalis.com
>
>
> 110 Buckingham Avenue, Slough, Berkshire, SL1 4PF
>
> Cisco Gold Partner Award 2013 (UK & Ireland)
> CA Technologies Partner for Impact Award 2013 (UK)
> HP Gold Certified Converged Infrastructure Specialist 2013 (UK)
> VMware Premier Solution Provider Partner 2013 (UK)
> _________________________________________________________________
>
>
>
>
> This email communication does not create or vary any contractual relationship
> between Logicalis and you. Internet communications are not secure and
> accordingly Logicalis does not accept any legal liability for the contents of
> this message. The contents of this email are confidential to the intended
> recipient at the email address to which it has been addressed. It may not be
> disclosed to or used by anyone other than this addressee, nor may it be
> copied in any way. If received in error, please contact Logicalis on the
> above switchboard number quoting the name of the sender and the addressee and
> then delete it from your system. Please note that neither Logicalis nor the
> sender accepts any responsibility for viruses and it is your responsibility
> to scan the email and attachments (if any).
>
> Please be aware that Logicalis UK Ltd may monitor email traffic data and also
> email content for security purposes.
>
> Logicalis UK Ltd, Registered in England and Wales No: 3732397, Registered
> Office: 110 Buckingham Avenue, Slough. Berkshire, SL1 4PF
>
> ______________________________________________________________________
> This email has been scanned by the Symantec Email Security.cloud service.
> For more information please visit http://www.symanteccloud.com
> ______________________________________________________________________
> . --To unsubscribe from spectrum, send email to lists...@unc.edu with the
> body: unsubscribe spectrum raphael.fra...@computacenter.com
>
>
> -----------------------------------
> Computacenter AG & Co. oHG, mit Sitz in Kerpen (Amtsgericht Köln HRA 18096)
> Vertretungsberechtigte Gesellschafter:
> Computacenter Aktiengesellschaft, mit Sitz in Köln (Amtsgericht Köln HRB
> 28384)
> Vorstand: Tony Conophy
> Aufsichtsrat: Michael Norris (Vorsitzender)
> Computacenter Management GmbH, mit Sitz in Köln (Amtsgericht Köln HRB 28284)
> Geschäftsführer: Dr. Karsten Freihube, Dr. Christine Haupt, Reiner Louis,
> Thomas Jescheck, Nils Scheller
> Visit us on the Internet: http://www.computacenter.de
> Visit our Online-Shop: https://shop.computacenter.de
>
> This email is confidential. If you are not the intended recipient, you must
> not disclose or use the information contained in it. If you have received
> this mail in error, please tell us immediately by return email and delete the
> document.
> -----------------------------------
>
>
> ---
> To unsubscribe from spectrum, send email to lists...@unc.edu with the body:
> unsubscribe spectrum dan.wh...@devoteam.com
>
>
> --To unsubscribe from spectrum, send email to lists...@unc.edu with the body:
> unsubscribe spectrum dwight.spe...@xassurance.com
---
To unsubscribe from spectrum, send email to lists...@unc.edu with the body:
unsubscribe spectrum arch...@mail-archive.com
