Joe has pointed out 2 problems with this event. The original question described
"
Unknown alert received from device T38D1 of type Host_Device. Device Time 0+00:00:00. (Trap type 1.3.6.1.4.1.21066.6.6) Trap var bind data:
......
In my AlertMap file, I have this code :
1.3.6.1.4.1.21066.6.4 0x5e10fffb 1.3.6.1.4.1.21066.6.4.1(100,0)\
"
we can see an obvious mismatch between the oids ending with 21066.6.6 of the incoming trap and 21066.6.4 of the alartMap. If 6.6 was not also mapped, it is unknown in Spectrum.
The 2nd potential problem is that this map was put in the folder read by EventAdmin models and not host devices.
this is discussed in more details here.
AlertMap Files - CA Spectrum - 10.3 - CA Technologies Documentation
AlertMap File Location
Default trap mappings are located in the <$SPECROOT>/SS/CsVendor directory while MIB Tools customized trap mappings are located in the <$SPECROOT>/custom/Events/AlertMap directory. MIB Tools’ customized trap mappings are preserved when you upgrade CA Spectrum, and they take precedence over any existing default trap mappings. For more information about working with custom trap mappings and default trap mappings, see Map Tab.
Global AlertMap files are located in <$SPECROOT>/SS/CsVendor/<developername>/AlertMap, where <developername> is usually the name of the vendor, manufacturer, or developer that is associated with the model type.
In some instances, CA uses something other than the developer name for the directory. For example, the IETF directory contains the AlertMap file that maps standard RFC traps.
If the AlertMap file is specific to the model type, it is located in <$SPECROOT>/SS/CSVendor/<developername>/ <model_type_name>AlertMap, where:
<developername> is the name of the vendor, manufacturer, or developer that is associated with the model type (for example, Compaq). If you are developing your own management module, your developer name is used here.
<model_type_name> is the name of the model type.
If a mapping for a trap exists in both a model type AlertMap file and a global AlertMap file, the model type AlertMap file takes precedence for that particular model type.
When you map traps using MIB Tools, entries are generated in the following file on all SpectroSERVERs in your DSS environment:
<$SPECROOT>/custom/Events/AlertMap
The mapping information for a trap in these files overrides any mapping information that previously existed for that same trap in other files or directories on the SpectroSERVER.
If you have further questions, please open an issue and I will look at this via webex tomorrow.
best regards
Shane