User guide
File Administration File Keys to Identify Downloadable Files
63
AlliedView NMS Administration Guide
3.6 File Keys to Identify Downloadable Files
3.6.1 Overview
As explained in Section 5.3.9, Software Configuration is an MDTI application that downloads OS releases onto supported
devices/components. Since there are many steps and constraints involved in this operation, the MDTI application is a
considerable simplification of the process, especially when downloading to multiple devices. The application uses a file on the
NMS to identify the files that can be downloaded on devices according to their device types. This file also encodes file
relationship constraints.
In previous releases, the data store was static within an NMS release, which meant new OS releases delivered after a
particular NMS release could not be downloaded to existing devices. The Custom Software Download feature gives users a
safe way to modify the data so newer OS releases can be downloaded to existing devices without waiting for a new NMS
release or patch.
Note: NMS applications are not necessarily expected to support devices running advanced releases but will make a best effort in
order to do so.
Using the Custom Software Download feature, explained in Section 5.3.10, the user can modify the file that stores the OS
release files. These custom (usually newer) release files must be already loaded in the following path; NMS-HOME/
swdownload
The file properties consist of required file keys and their names. The names are OS release files and their required resources,
if any. The required file keys vary according to the specific device type.
In using the Custom Software Download feature, the user selects an existing device type (new device types are not
supported). The user then selects file names from the files in the above paths for each type-specific file key. See Table 3-2 for
example supported device types and their required file keys.
If the Load already contains an entry for the selected device type, its file properties will be replaced by the new selections,
otherwise the new entry will be added to the selected Load.
Caution: Devices will fail if the wrong file is used for the wrong purpose when downloading a new release. Standard loads have been
tested for correct configurations. Moreover, software upgrades may require updating of loads in a specific sequence to
ensure data configuration integrity. Custom loads are usually created and used by Network Administrators, and they must
use this feature with extra caution
Note: If a Rapier or Switchblade type is added, manual WebgenImport will have to be used to enable the release on the target
devices.