After completing all the documented steps to integrate Nimsoft and Spectrum, we may see all the Nimsoft traps being placed on UIM Server model instead of the trap source model in Spectrum. The following is an example of an incomplete Nimsoft trap in Spectrum placed on the UIM Server.
Unknown alert received from device uimserver.ca.com of type NimsoftHostServer. Device Time 0+00:00:00. (Trap type 220.127.116.11.4.1.4055.1.6.5)
Trap var bind data:
OID: 18.104.22.168.22.214.171.124.0 Value: NimBUS/SNMP gateway
OID: 126.96.36.199.4.1.4055.1.1.0 Value: 0
OID: 188.8.131.52.4.1.4055.1.2.0 Value: 1.1.2
OID: 184.108.40.206.4.1.4055.1.3.0 Value: smss.exe: Process smss.exe is running with process id = 268.
OID: 220.127.116.11.4.1.4055.1.12.0 Value: ZY13071548-00101
Why are Nimsoft events are incorrectly placed on the UIM server model in my Spectrum integration?
CA Spectrum 9.4 with CA UIM 8.1, 8.2
The SNMP gateway probe in Nimsoft needs to be adjusted from default to include extra trap variables needed in Spectrum.
In the image below we see the snmpgtw probe setup tab modified to include trap variable as follows
e.g. the source and origin of the alert have been included so that Spectrum can place the event on the correct model.
This solution along with other required configuration changes needed in Nimsoft are discussed in detail and published to the communities as: