Bulk device imports in the Network Configuration Manager (NCM) production environment fail with a DeviceClassConfig error despite working in test environments
Bulk import command fails on the Application Server.
Error logs indicate "DeviceClassConfigNotFound" and "DeviceClassNotFoundException".
When running the importDevices command on the NCM Application Server received the following error message:
ERROR MESSAGE:
"com.powerup.configmgr.util.commandline.CommandException: Unable to import devices, please check the logs: NetworkException. DeviceClassConfig NotFound"
Occurs during the execution of the importDevices command on the NCM Application Server using a CSV seed file.
NCM - All supported releases
The device classes were not included at the Global level in the production environment. This caused a mismatch when the import utility attempted to map devices in the CSV to known configurations.
Verify Device Package existence:
Log into the NCM GUI and verify that Device Package is installed and active.
Log into the NCM GUI
Navigate to Tools > Device Packages and confirm the Device Package is present and its status is Active.
CONFIGURE DEVICE CLASSES AT GLOBAL LEVEL: Review the Global level configuration to ensure device classes are included.
NOTE: If classes are missing at the Global level, the seed file import will fail even if the package is installed.
After confirmation of the above and including device classes at the Global level, execute the importDevices command on the NCM Application Server
The command should complete without "DeviceClassConfig NotFound" errors.