Hi Elio,
Firstly - as a more elegant solution - I think you should be able to use
Spectrum's Southbound Gateway (SBGW)  mechanism - with the ACE as the
EventAdmin model - and map the incoming traps so that resultant events are
posted to the appropriate target  EventModel.  It requires  one of the
varbinds  in the inbound trap being  the name or some way of identifying
the target.  (But this must be the case anyway I think from what you say).
You create a custom AlertMap that maps all those varbinds to new variables
(from var 100 upwards) except for the one that is the name of the target
(which you map into var 7 , or possibly var 10, or  var 16*).   This way
you wouldn't need all that stuff with a Notifier setcript regenerating a
trap back into Spectrum.  The info you would need to get to grips with this
is detailed in the SBGW manual.

 (* There are a quite few different ways available to you,  of specifying
the target model -  depending on how the varbind identifies your target -
see the Event Data Template section in the SBGW manual)

However, just to continue with the solution you are working on *now* with
the Notifier and trap-sending utility - and to answer your question:
You say you have loaded the MIB that contains the definition for the trap.
In mibtools did you proceed to the step of having it create the trap
definition?  Once you do that  it will  add that trap's definition to your
custom AlertMap** in $SPECROOT/custom/Events.  It will have automatically
created a mapping from each of the trap's varbinds to a corresponding event
variable numbered from var 1 upwards. You can then use the Event Config
Editor to create some events and alarms that use those variables.

(**In the case you used my first suggestion  - it is here  where you would
edit this AlertMap to map the varbinds to the values as specified by the
Event Data Template rules in the SBGW manual instead of just leaving them
as var 1, 2, 3 etc).

Hope this helps.
Cheers
Dan.



*Dan White*
Senior Consultant
Service Assurance
[image: Devoteam]

 *Mob. : *+44 (0)7973 533671
[email protected]

Follow us : [image: Linked In]
<http://www.linkedin.com/company/4160?trk=null> [image: Twitter]
<http://twitter.com/#!/devoteam> [image: Youtube]
<http://www.youtube.com/user/devoteam>

CONNECTING BUSINESS & TECHNOLOGY

On 22 October 2014 15:54, Elio Frongia <[email protected]>
wrote:

>  Hi everyone,
>
> I’m using Live Exceptions to monitor some virtual servers (within virtual
> contexts in Cisco ACE devices) and there’s no model in Spectrum that
> represent them, so I created Event Models in Spectrum to do so. The thing
> is that I configured a notifier rule that executes a script that grabs all
> the information of the element and the alarm, and sends a trap to Spectrum
> so that it can individualize each alarm for each Event Model (instead of
> assigning all the traps to the model of the ACE).
>
> So, Spectrum receives a trap with 26 variables (custom MIB, already
> uploaded with MIB Tools). How can I get the values for each OID to use them
> in the Event Message? Do I have to create an event table? I’m not getting
> the idea from the Event Configuration guide, which indicates this:
>
>
>
> {Y <event table file name> #}
>
> Inserts a text string that is associated with an OID. The association
> between the attribute value and the text string is defined in an event
> table file that is automatically created by MIB Tools when you map the trap
> to the event. For more information, see Referencing OIDs (see page38).
>
>
>
> If a variable binding that is sent with a trap contains an OID, you can
> use it in an event
>
> message. To do so, you must use the proper syntax and reference the
> following:
>
> ■
>
> The event variable to which the OID of the variable binding is mapped.
>
> ■
>
> The event table file that contains the enumerated OID values and the
> associated
>
> text strings to use in event messages. (Event table files are
> automatically created by
>
> MIB Tools when you map traps to new CA Spectrum events.)
>
> As an example, assume you have an event table file named NewTable that
> associates
>
> the following attribute values with corresponding text strings:
>
> 1.3.6.1.4.1.1563.1.2.1.1.3.2.36.2.6 dot6
>
> 1.3.6.1.4.1.1563.1.2.1.1.3.2.36.2.5 dot15
>
> 1.3.6.1.4.1.1563.1.2.1.1.3.2 dot7
>
> To reference these values in an event message, use the following syntax:
>
> {Y NewTable 2}
>
>
>
> Regards
>
>
>
> *[image: cid:[email protected]]*
> <http://www.netsol-international.com/>
>
>
>
> *Elio Frongia*
>
> *Presales Consultant*
>
>
>
>    Esmeralda 684, Piso 10
>
> (C1007ABF)
>
> Ciudad de Buenos Aires
>
> Argentina
>
> Web:
>
> E-mail:
>
> Tel:
>
> Móvil:
>
> PIN:
>
> http://www.netsol-international.com <http://netsol-international.com/>
>
> [email protected] <[email protected]>
>
> +54 11 5031 1162 interno 107
>
> +54 911 6548 2609
>
> 27015BAC
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> [image: cid:[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]

Reply via email to