CA Performance Management provides a method where the discovered devices can be set to use different Device Type assignments than the product uses by default.

If this isn't working as expected we can enable debug to track the messaging for the function in search of a cause.

Previous to the new releases of CA Performance Management there was no way to debug this function. As of the r3.6 release, and also available in the r3.5 April Monthly Update kit a new set of debug tools were added for this function.

CA Performance Management releases:

• r3.5 April Monthly Update kit or newer
• r3.6 or newer

To enable this debug complete the following:

1. Edit the /opt/IMDataCollector/apache-karaf-2.4.3/etc/org.ops4j.pax.logging.cfg file. 
2. Add the following lines to the file:
   • log4j.logger.com.ca.im.dm.certs.snmp.DeviceTypeServiceImpl=DEBUG,DiscoveryLog
   • log4j.logger.com.ca.im.dm.certs.snmp.SNMPDeviceServicesFunction=DEBUG,DiscoveryLog
3. Reproduce the issue and provide CA Remote Engineer (CARE) re.sh script output from the CA Data Collector server. 

NOTE: CA Remote Engineer (CARE) re.sh script instructions can be found in the latest r3.6 documentation here:

https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-enterprise-software/it-operations-management/performance-management/3-6/troubleshooting/unable-to-resolve-issue.html

See here for r3.7 instructions which are slightly different from r3.6 re.sh run steps.

https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-enterprise-software/it-operations-management/performance-management/3-7/troubleshooting/unable-to-resolve-issue.html