Enterprise Device Manager configuration files

This section describes how to use Enterprise Device Manager (EDM) to store and retrieve configuration files.

Using EDM, you can store the current ASCII switch configuration file on a TFTP server or a USB storage device, retrieve an ASCII configuration file from a TFTP server or USB storage device to apply to a switch, store or retrieve a binary configuration file, or manually save the current configuration to flash memory.

You can check file upload transfer status of ASCII configuration files in the ScriptLastStatusChange field on the Edit , File System , Ascii Config Script Files tab. During upload transfer, the status is manualUploadInProgress . To check changes to file transfer status, click Refresh. After the file transfer is complete the status displays as either manualUploadPassed or manualUploadFailed .

You can check file download transfer status of ASCII configuration files in the ScriptLastStatusChange field on the Ascii Config Script Files tab. During download transfer, the status is manualDownloadInProgress . To check changes to file transfer status, click Refresh. After the file transfer is complete, the status displays as either manualDownloadPassed or manualDownloadFailed .

You can also designate an ASCII configuration file to download automatically at switch startup.

To control which ASCII configuration files load automatically, at switch startup, use the fields in the table on the Edit , File System , Ascii Config Script Files tab.

The Ascii Config Script Files table provides a way to control which ASCII configuration files are loaded, and in which order, because you can designate the path to an ASCII configuration file, a boot priority value, and a script index priority for each entry in the table.

Depending on which script source you designate for an entry, the system uses the designated paths in the Ascii Config Script Files table in one of the following ways:

In the boot priority column on the Ascii Config Script Files tab, if you designate a non-zero boot priority value for any but the first row, the switch attempts to load the configuration file at startup. The first entry in the configuration files table is assigned a fixed boot priority value of 0 and it is not available to load at startup.

The switch attempts to load each ASCII configuration file with a non-zero priority value, in ascending order, until a script file loads successfully. If ASCII configuration file boot priority values are equal, the switch attempts to load the configuration files according to their script index order.

In the Script Source column on the Ascii Config Script Files table, if you designate a USB device in a standalone switch as the load-on-boot path to the ASCII configuration file, the switch downloads the specified configuration file from the USB port of the switch. If you designate a USB device in a stack unit as the load-on-boot path to the ASCII configuration file entry, the system downloads the specified configuration file from the USB port of the designated unit or, if no unit is designated, from the USB port of the base unit. If the system cannot download the configuration file, or if the script does not execute successfully, the script operational status changes to autoDownloadFailed and the system downloads the next entry in the table. After the configuration file downloads and executes without errors, the operational status for the entry changes to autoDownloadPassed .

You can use the procedures in this section to

Procedures for USB storage devices apply only to switch models with USB ports.