Device definitions identify AOS units to n-Command allowing it to correctly populate device specific information and perform management functions on the unit. Previous to version 8.1.1, n-Command MSP device definitions were only updated upon release of a new version of software. With version 8.1.1, device definitions may now be updated at any time utilizing a device definitions file that can be updated and loaded to n-Command MSP. This file can be automatically or manually uploaded to add support for AOS and ASE units that have been released after the latest n-Command MSP version is released.
Sections Included in This Document
Hardware and Software Requirements
Device Definition Considerations
Updating Device Definitions
Useful Links
Hardware and Software Requirements
The Device Definitions feature requires MSP version 8.1.1 or higher.
Device Definition Considerations
Though recently released AOS units will be able to connect and communicate with n-Command MSP, essential information regarding the unit pertaining to the device type and allowing the user to run jobs on the unit will not be available. Device definitions allow n-Command MSP to recognize these units and utilize all the management functionality on them quickly without having to upgrade n-Command MSP.
It is important to remember that though n-Command MSP will now properly recognize a new device type and all job functions will be available when it connects, the n-Command MSP release will not have been fully tested with that unit. Full support and testing of the device type will be completed in a future MSP software release. Though many or all functions may work properly, these devices could experience unintended issues until an MSP version is released noting full support for the product. This will be notated in the release notes for the MSP software release.
Updating Device Definitions
n-Command MSP will automatically query an ADTRAN repo for device definition updates once per day if the server has a rout-able public internet connection and can query a live DNS server. If an update is found, it will be automatically downloaded and added to the n-Command device database. If the server cannot reach the internet, device definitions will have to be manually updated by downloading the file from the <<<<ADTRAN website>>>>, or by upgrading n-Command MSP to a newer release with support for the unit if available.
If your n-Command MSP unit has a rout-able public internet connection, device definitions will be automatically updated once they are released and require no manual intervention by a user.
If a new device definition file has been released but the newly supported devices still show a device type of "unknown", see the below section to attempt to fix these devices.
If your n-Command MSP unit cannot reach the internet, device definitions can be downloaded here and manually added to the server. Do this by logging in and going to Open Tab -> Devices. On the device page, click Manage in the top left corner and select Update Device Definitions. The resulting window will allow you to select and upload the device definitions file. Any previously unsupported units that have already connected to your server will need to be resolved using the section below.
n-Command MSP classifies units and pulls all of the relevant device information used to categorize the device when it is first discovered. If a device is discovered before a definition exists for it, the Device Type will be listed as "unknown", many device parameters will be blank, and most job types will be unavailable. If a device you are adding a definition for with a new device definitions file has already been discovered by n-Command MSP, the devices will need to be deleted and allowed to reconnect to be properly categorized once the definition has been added. A device can be deleted by selecting the device from the Devices page and selecting Delete from the top menu.
If an error is received when deleting the device, verify there are no pending or past run jobs in the Job History menu that include this device. If there are, delete these jobs from the history and attempt to re-delete the device.
Once a device has been deleted, it will be rediscovered on the devices next check-in (the device needs no manual intervention). Alternatively, you can use the Discover Devices option to re-discover the device.
Useful Links
