The name of every event disposition (EventDisp) file is always EventDisp.
Note: In the Windows environment, no file extension is used.
The EventDisp files that support the events provided with CA Spectrum are installed in the following directories:
An EventDisp file in this location defines the processing for all events created by the developer that are global in scope. The vendor_directory variable is the name of the developer, vendor, or manufacturer for which the EventDisp file is used.
Note: In some instances, CA uses something other than the developer name for the developer-specific directory; for example, the IETF directory contains the EventDisp file that specifies the processing for events that result from standard RFC traps.
An EventDisp file in this location defines the processing for all events that are created by the developer whose scope is limited to the model type represented by model_type_name. In this case, vendor_directory is the name of the developer, vendor, or manufacturer for which the model type was created (for example, Cisco).
Note: If an event map entry exists in both a global EventDisp file and a model type-specific EventDisp file, the event map entry in the model type-specific file takes precedence.
If you customize the event processing for the CA Spectrum predefined events, or if you create new custom events using MIB Tools or Event Configuration, a custom EventDisp file is created in the following directory or in one of its subdirectories:
$SPECROOT/custom/Events
Note: The event map entries in a custom EventDisp file override those entries in the predefined CA Spectrum EventDisp files.
|
Copyright © 2014 CA.
All rights reserved.
|
|