To resolve this we will have to set up a custom DeviceTypes.xml file that will over-ride the current product behavior.
Add the following section to the /opt/IMDataAggregator/apache*/custom/devicetypes/DeviceTypes.xml file.
Save the changes to the file and wait 2 minutes. This ensures the one minute refresh cycle in the DA code has a chance to re-read that file for the new changes.
After the DA has had time to read in the new file changes, run a Discovery Profile with one IP address for an affected device as a test. This should result in an updated device based on the custom file changes.
After reviewing the results after testing for a single IP address, if it shows better results, move forward with a Discovery Profile run that updates and resolves any remaining devices that are incorrectly classified.