Debugging problems with device type overrides in CA Performance Management

Products

• CA Performance Management
• Network Observability

Issue/Introduction

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

We Override the Device Types and Context Types by editing the DeviceTypes.xml file on the Data Aggregator.

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

Environment

All supported DX NetOps Performance Management releases

Resolution

To enable this debug complete the following depending on the release being utilized.

1. For all Performance Management release 21.2.1 and older follow these steps:
   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. 
2. For all Performance Management releases 21.2.2 and newer follow these steps:
   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:

      • log4j2.logger.DeviceTypeServiceImpl.name = com.ca.im.dm.certs.snmp.DeviceTypeServiceImpl
        log4j2.logger.DeviceTypeServiceImpl.level = DEBUG
        log4j2.logger.DeviceTypeServiceImpl.additivity = false
        log4j2.logger.DeviceTypeServiceImpl.appenderRef.DiscoveryLog.ref = DiscoveryLog
        log4j2.logger.SNMPDeviceServicesFunction.name = com.ca.im.dm.certs.snmp.SNMPDeviceServicesFunction
        log4j2.logger.SNMPDeviceServicesFunction.level = DEBUG
        log4j2.logger.SNMPDeviceServicesFunction.additivity = false
        log4j2.logger.SNMPDeviceServicesFunction.appenderRef.DiscoveryLog.ref = DiscoveryLog

   3. Reproduce the issue to generate the debug logging.
      • The logging is stored in the (default path shown) /opt/IMDataCollector/apache-karaf-<version>/log/DiscoveryLog.log file.
   4. Disable the debug by commenting out (use # symbols) the lines, or removing them, from the org.ops4j.pax.logging.cfg file. Save the changes to other file and the debug is disabled.
   5. Provide the logging to support via a diagnostics logging package from the Data Collector host.
      • Generate the logging package using the re.sh script.
      • Steps to run the script are in the Unable to Resolve Issue documentation topic.

Additional Information

This is debug that was first introduced in the GA r3.6 release and the r3.5 April Monthly Update kit release.