B. saving a gui resource file update profile, Aving a, Esource – Allied Telesis AlliedView-UM 2.0 User Manual
Page 89: Pdate, Rofile

•
Delete currently used GUI Resource file if memory space is insufficient
checkbox - This option will only be enabled if the above option is checked.
Otherwise, it will be grayed out. When this option is checked, the
AlliedView-UM will also delete the currently set GUI Resource file if there is
still insufficient space in the device after deleting the other GUI Resource
files.
4. Reboot device after updating checkbox - If an old GUI Resource File is specified,
this option will be enabled. Otherwise if the specified GUI Resource File is new,
this checkbox will only be enabled if “Upload and set as temporary” or “Upload and
set as preferred” is chosen for the Upload Option. When checked, AlliedView-UM
will reboot the device after performing the update.
Upload Parameters
1. Server - This is the address for the server that contains the GUI Resource file. If the
server is a TFTP server, the server address should be specified as an IP address.
If the server is an HTTP server, the server address should be specified as a URL.
2. Destination - This sets the location where the new GUI Resource file will be stored.
This can be set to FLASH or NVS.
3. Protocol - This specifies the protocol that the server supports. This can be set to
HTTP or TFTP.
Device Selection
Before device selection can be performed, a GUI Resource file must be specified. After
selecting a GUI Resource file, the Available Devices list will be populated with the IP
addresses of the devices to which the specified GUI Resource file can be applied to.
Except for the above mentioned process, device selection is similar to that of the Release
Upgrade Operation pane.
B. Saving a GUI Resource File Update Profile
1. Click on the
button.
AlliedView™-UM 2.0 USER’S GUIDE
Page 89 of 128