I've been setting this up for first time also... the example and the southbound 
manauls are pretty vague...here is what I found as best as I can explain it.

have a look at this file and it might become more obvious how it works 
/SS-Tools/GSADEMO/MergeVendorFiles.cus

this runs as part of the packaging deployment to cat any evd or eml files to 
the right places to make the eventdisp for eventadmin and eventmodel and 
alertmap... but when testing you can just edit the files...

referring to the sbgw manual pages the files are:

/SS/CsVendor/gen_app_gw/EventDisp
on page 65 this is the "EventModel EventDisp file"
this should have the real events you want generated with logic for the 
eventmodel.
if you want eventmodels created (not just default) yhou have to make this file.

/SS/CsVendor/gen_app_gw/EventAdmin/EventDisp
this is the EventAdmin EventDisp File on page 64
this should have a single eventid only for any event that triggers sbgw. no 
logic or event rules.

but the real crunch is:
/SS/CsVendor/gen_app_gw/EventAdmin/AlertMap

in manual page 64 this is the "EventAdmin AlertMap file" also called the "Event 
Data Template" on page 30 (it took me hours to figure this out!)
"Correctly choosing the Event Data Template variable ID values is important 
because they enable essential functions of the Southbound Gateway integration. 
The values you choose determine how a target model for the incoming event is 
identified. You can control whether a new EventModel is created to handle an 
incoming event. You also have the option of specifying variable ID values which 
specify whether to use a network address or model name as the event target 
search criteria."

if you want dynamic named eventmodels cerated on fly map varbinds from trap to 
fields 1-6. e.g map say a hostname from your trap to varbind 1 and leave 2-99 
blank, then map any other varbinds to 100+

other fields from manual describe how mapping other varbinds make sbgw do 
different stuff.


---
To unsubscribe from spectrum, send email to [email protected] with the body: 
unsubscribe spectrum [email protected]

Reply via email to