How it Works
Allied Telesis
Loading...
ALLIEDVIEW-UM 1.6
User Manual
129 pgs1.64 Mb0

Allied Telesis ALLIEDVIEW-UM 1.6 User Manual

Download
A
LLIEDVIEW-UM 1.6
USER'S GUIDE
PN 613-000381 Rev B Page 1 of 129
User's Guide
Copyright © 2002-2007 Allied Telesis K. K. All rights reserved. No part of this publication may be reproduced without prior written permission from Allied
Telesis K. K. Allied Telesis K. K. reserves the right to make changes in specifications and other information contained in this
document without prior written notice. The information provided herein is subject to change without notice. In no event shall Allied Telesis K. K. be liable for any incidental, special, indirect, or consequential damages whatsoever, including but not limited to lost profits, arising out of or related to this manual or the information contained herein, even if Allied Telesis K. K. has been advised of, known, or should have known, the possibility of such damages.
PN 613-000381 Rev B Page 2 of 129
User's Guide
TABLE OF CONTENTS
1 INTRODUCTION .................................................................................................... 6
1.1 RECOMMENDED READING..................................................................................6
1.2 OTHER REQUIREMENTS.....................................................................................6
2 A GUIDED TOUR ........................................................................................................ 7
2.1 LAUNCHING THE APPLICATION ..........................................................................7
2.2 CREATING A DEVICE..........................................................................................8
2.3 UPGRADING SOFTWARE...................................................................................12
2.4 THE ALLIEDVIEW-UM SYSTEM FOLDERS ...........................................................12
3 MAIN WINDOW....................................................................................................... 13
3.1 DEVICE FAMILIES PANE ...................................................................................13
3.2 OPERATIONS SELECTION PANE........................................................................14
3.3 OPERATIONS PANE..........................................................................................16
3.4 OPERATION LOGS PANE...................................................................................16
4 DEVICE GROUPS...................................................................................................... 18
4.1 CREATING A DEVICE GROUP............................................................................18
4.2 DELETING A DEVICE GROUP ............................................................................18
4.3 RENAMING A DEVICE GROUP ...........................................................................20
4.4 LOADING DEVICE GROUPS...............................................................................21
4.5 CLOSING DEVICE GROUPS ...............................................................................22
5 DEVICE DEFINITIONS ............................................................................................... 24
5.1 CREATING A DEVICE DEFINITION.....................................................................24
5.2 LOADING DEVICE DEFINITIONS FROM A COMMA SEPARATED VALUE (CSV) FILE.29
5.3 VIEWING DEVICE DEFINITIONS........................................................................33
5.4 MODIFYING DEVICE DEFINITIONS....................................................................35
5.5 DELETING DEVICE DEFINITIONS......................................................................37
6 EXPORTING DEVICE SERIAL NUMBERS......................................................................... 38
6.1 LICENSE LIST FILE FOR RELEASE UPGRADE (ALLIEDWARE) OPERATIONS...........40
6.2 LICENSE LIST FILE FOR ENABLE FEATURES OPERATIONS ..................................40
7 RELEASE UPGRADE OPERATION.................................................................................. 42
7.1 CREATING A RELEASE UPGRADE PROFILE.........................................................43
7.2 SAVING A RELEASE UPGRADE PROFILE.............................................................48
7.3 LOADING A RELEASE UPGRADE PROFILE...........................................................49
7.4 STARTING THE RELEASE UPGRADE (ALLIEDWARE) or (OTHER) OPERATION .......51
8 INTERIM/MAINTENANCE RELEASE UPGRADE OPERATION ............................................... 52
8.1 CREATING AN INTERIM/MAINTENANCE RELEASE UPGRADE PROFILE..................53
8.2 SAVING AN INTERIM/MAINTENANCE RELEASE UPGRADE PROFILE......................55
8.3 LOADING AN INTERIM/MAINTENANCE RELEASE UPGRADE PROFILE ...................56
8.4 STARTING THE INTERIM/MAINTENANCE RELEASE UPGRADE OPERATION...........58
9 PATCH UPGRADE OPERATION..................................................................................... 60
9.1 CREATING A PATCH UPGRADE PROFILE............................................................61
9.2 SAVING A PATCH UPGRADE PROFILE................................................................63
PN 613-000381 Rev B Page 3 of 129
User's Guide
9.3 LOADING A PATCH UPGRADE PROFILE..............................................................64
9.4 STARTING THE PATCH UPGRADE OPERATION...................................................66
10 CONFIGURATION FILE UPDATE................................................................................... 67
10.1 CREATING A CONFIGURATION FILE UPDATE PROFILE .......................................68
10.2 SAVING A CONFIGURATION FILE UPDATE PROFILE ...........................................72
10.3 LOADING A CONFIGURATION FILE UPDATE PROFILE .........................................73
10.4 STARTING THE CONFIGURATION FILE UPDATE OPERATION ..............................75
11 EXECUTE SCRIPT FILE............................................................................................... 77
11.1 CREATING AN EXECUTE SCRIPT FILE PROFILE ..................................................78
11.2 SAVING AN EXECUTE SCRIPT FILE PROFILE ......................................................80
11.3 LOADING AN EXECUTE SCRIPT FILE PROFILE....................................................81
11.4 STARTING THE EXECUTE SCRIPT FILE OPERATION ...........................................83
12 GUI RESOURCE FILE UPDATE .................................................................................... 84
12.1 CREATING A GUI RESOURCE FILE UPDATE PROFILE ..........................................85
12.2 SAVING A GUI RESOURCE FILE UPDATE PROFILE ..............................................87
12.3 LOADING A GUI RESOURCE FILE UPDATE PROFILE............................................88
12.4 STARTING THE GUI RESOURCE FILE UPDATE OPERATION .................................90
13 HELP FILE UPDATE................................................................................................... 91
13.1 CREATING A HELP FILE UPDATE PROFILE .........................................................92
13.2 SAVING A HELP FILE UPDATE PROFILE .............................................................94
13.3 LOADING A HELP FILE UPDATE PROFILE...........................................................95
13.4 STARTING THE HELP FILE UPDATE OPERATION ................................................97
14 ENABLE FEATURES ................................................................................................... 98
14.1 CREATING AN ENABLE FEATURES PROFILE .......................................................99
14.2 SAVING AN ENABLE FEATURES PROFILE .........................................................101
14.3 LOADING AN ENABLE FEATURES PROFILE.......................................................102
14.4 STARTING THE ENABLE FEATURES OPERATION .............................................. 104
15 REBOOT DEVICE .................................................................................................... 105
15.1 CREATING A REBOOT DEVICE PROFILE...........................................................106
15.2 SAVING A REBOOT DEVICE PROFILE...............................................................107
15.3 LOADING A REBOOT DEVICE PROFILE ............................................................108
15.4 STARTING THE REBOOT DEVICE OPERATION..................................................110
16 AUDIT TRAIL......................................................................................................... 111
16.1 VIEWING THE AUDIT TRAIL ........................................................................... 111
17 SCHEDULING OPERATIONS ...................................................................................... 113
17.1 HOW TO SCHEDULE AN OPERATION............................................................... 113
17.2 VIEWING TASKS............................................................................................114
17.3 EDITING TASKS.............................................................................................116
17.4 ABORTING A TASK.........................................................................................118
17.5 DELETING A TASK .........................................................................................119
18 ROLLBACK ............................................................................................................ 120
18.1 ROLLBACKS AND THE AUDIT TRAIL ................................................................ 120
PN 613-000381 Rev B
Page 4 of 129
User's Guide
18.2 SPECIAL RULES ON ROLLBACKS...................................................................... 121
18.3 PERFORMING A ROLLBACK ON A DEVICE ........................................................ 122
18.4 PERFORMING A ROLLBACK ON AN OPERATION PROFILE..................................124
19 LICENSE REGISTRATION.......................................................................................... 127
20 OPTIONS.............................................................................................................. 129
20.1 VIEW SETTINGS ............................................................................................129
20.2 THREAD SETTINGS........................................................................................ 129
PN 613-000381 Rev B
Page 5 of 129
User's Guide
1 INTRODUCTION
AlliedView-UM is a Java-based application that allows fast and efficient distribution of Software Upgrades, Patches, GUI Resource files, Help, Configuration files and Script files on Allied Telesis network devices. It provides a batch method of downloading software or a file onto devices via TFTP or HTTP. It also provides the ability to enable the downloaded software or file and enable features on multiple devices.
1.1 RECOMMENDED
AlliedView-UM basically builds upon the CLI commands of Allied Telesis management software. Refer to the Software Reference Manual or CLI User’s Guide that accompanies every AT network device for a better understanding of these commands.
1.2 OTHER
REQUIREMENTS
The user should have some background in network device management specifically for AT Network Devices.
READING
PN 613-000381 Rev B Page 6 of 129
User's Guide
2 A GUIDED TOUR
This section introduces all the basic features of AlliedView-UM. This section is not intended to be a reference and will thus not explain all the details.
2.1 LAUNCHING
To begin the tour, start the application using any of the following methods: For Windows systems: Double-click on the executable file "um.exe" or its corresponding shortcut through Windows
Explorer.
Enter the installation path specified during installation followed by "\bin\um.exe" on the command
line
Click on the application icon in the AlliedView-UM program group
For Solaris and HP-UX systems: Move to the directory where AlliedView-UM was installed, and type "./bin/um" on the command line.
THE APPLICATION
PN 613-000381 Rev B Page 7 of 129
User's Guide
The image below illustrates the initial screen display of AlliedView-UM.
2.2 CREATING
Before you can use the main functions of AlliedView-UM , you will need to add Devices on the Device Families pane. To do that, follow these simple steps.
1. Click on the Device->Add Device Group option. This will display the “Add Device Group” dialog box.
PN 613-000381 Rev B
A DEVICE
Page 8 of 129
User's Guide
2. Click on the “Device Family” dropdown list and select “Rapier”. If you do not have any Rapier devices, select the appropriate device family for the device that you currently have. On the Device
Group Name field, input “Test Group” and click on the
button.
3. Look at the Device Families pane. You should see your newly created group ("Test Group") added under the Rapier Family root node.
4. Click on the Device->Add Device option.
5. The Add New Device dialog box should be displayed.
PN 613-000381 Rev B
Page 9 of 129
User's Guide
7. Input the IP address of your device in the IP Address field.
8. In the Login Name field, enter the user account name that AlliedView-UM will use to login to your device.
9. In the Password field, enter the appropriate password for the account you have entered in the previous step.
10. The SNMP Read Community, Timeout and Retries fields already have default values. You may change these if needed.
PN 613-000381 Rev B
Page 10 of 129
User's Guide
11. Click on the button. If the IP Address, Login Name, Password, and SNMP Read
Community that you specified are correct, then the Device Family, Device Model Serial Number, System Name, System Description and Configuration File fields should now be set. If an error occurs, please re-check the values you entered in steps (6) to (9).
12. Finally, click on the button to add the device.
13. Your new device should now be added. If you check the Device Families pane, you should see the
IP Address of your device under the group called, "Test Group".
PN 613-000381 Rev B
Page 11 of 129
User's Guide
2.3 UPGRADING SOFTWARE
In this section, we will be performing a simple patch upgrade using the Patch Upgrade operation. Before proceeding, make sure you have added one or more devices. If you have not done so, please go back to the previous section, "Creating a Device". You will also need to have access to an appropriate patch upgrade file for your device.
Click on the
button on the Operations Selection Pane. This will display
the Patch Upgrade pane.
Next, locate the upgrade file you will be using by clicking the selected your file, click on the
button. After you have located and
option. Check the
checkbox.
Enter the address of the server where the file is located. Make sure you enter the correct address format. If you have an HTTP server, you should enter a URL address. If you have a TFTP server, enter an IP Address.
Now, select the devices you will be applying the update to. In the "Available Devices" list box, you should see the IP Addresses of the devices you added a while ago and for which the selected patch is
applicable to. Select one of those entries and click on the
button. The IP Address that you
selected should now appear in the "Selected Devices" list box.
To start the upgrade process, click on the
button.
NOTE: Upgrading and rebooting a device will make that device unavailable for the duration of the operation. Make sure that you notify the appropriate groups or people that will be affected before proceeding.
2.4 THE ALLIEDVIEW-UM SYSTEM FOLDERS
Deleting or modifying any of the files under the AlliedView-UM installation folder is not recommended. Doing so will cause the application to function incorrectly.
PN 613-000381 Rev B
Page 12 of 129
User's Guide
3 MAIN WINDOW
After successfully starting the application, the following window will be initially displayed:
The Main Window is divided into 4 major panes (or regions), namely the (1) Device Families Pane, the
(2) Operations Selection Pane, the (3) Operations Pane and the (4) Operation Logs Pane.
3.1 DEVICE
FAMILIES PANE
The Device Families Pane is used to manage the devices that AlliedView-UM can interface with.
PN 613-000381 Rev B Page 13 of 129
User's Guide
The root nodes of the Device Families represent the AT Device Families that are currently supported by this application. The AT Device Family root node is represented by a (
) icon followed by the AT Device
Family name. Each AT Device Family root node can contain Device Group nodes. A Device Group node is represented
by a (
) icon followed by the Device Group name.
Finally, a Device Group node can contain Device nodes. A Device node is represented by a ( ) icon followed by the IP address of that device. A Device node cannot contain any other nodes under it. Double clicking on a node will display the corresponding dialog box that will allow you to perform functions pertaining to that node. For instance, if you double click on a Device Node, the Edit Device dialog box will be displayed. From the Edit Device dialog box you can view and modify some of the device attributes.
3.2 OPERATIONS
The Operations Selection Pane allows you to select an operation profile to create.
SELECTION PANE
PN 613-000381 Rev B
Page 14 of 129
User's Guide
Clicking on any of the buttons in the Operation Selections Pane will display the appropriate Operations Pane. For example, if you click on the
button, the Release
Upgrade Operations Pane will be displayed.
PN 613-000381 Rev B
Page 15 of 129
User's Guide
3.3 OPERATIONS
PANE
This is where operation panes for creating operation profiles are displayed.
For instance, the figure above displays the Release Upgrade (AlliedWare) pane after the user clicks on the
3.4 OPERATION
The Operation Logs Pane displays the status and results of operations performed.
PN 613-000381 Rev B
button.
LOGS PANE
Page 16 of 129
User's Guide
PN 613-000381 Rev B
Page 17 of 129
User's Guide
4 DEVICE GROUPS
A device group represents a logical grouping used to manage devices. A device group must first be created before any device can be defined.
4.1 CREATING
1. Click on the
A DEVICE GROUP
Device->Add Device Group option. This will display the “Add Device Group” dialog box.
2. Select the Device Family where your new Device Group will be added to.
3. Enter the name of your device group in the Device Group Name field.
4. Finally, click on the
button.
4.2 DELETING
A DEVICE GROUP
Method 1:
1. On the Device Families Pane, select the device group node to be deleted.
PN 613-000381 Rev B Page 18 of 129
User's Guide
2. Click on the
Device->Delete Device Group option.
3. A confirmation dialog box will be displayed. Click on
to proceed with the deletion.
Method 2:
1. Right click on the device group node to be deleted. A popup menu will appear.
2. Select the
3. A confirmation dialog box will be displayed. Click
Delete option.
to proceed with the deletion.
NOTE: Any device under the deleted device group will be deleted as well.
PN 613-000381 Rev B
Page 19 of 129
User's Guide
4.3 RENAMING
A DEVICE GROUP
Method 1:
1. On the Device Families Pane, select the device group node to be renamed. The device group pane will be displayed. The Name field contains the currently assigned name for that device group.
2. Click on the
Device->Rename Device Group option.
3. Type in the new name in the Device Group Name field.
4. Finally, click on the
button.
PN 613-000381 Rev B
Page 20 of 129
User's Guide
Method 2:
1. Right click on the Device Group node to be renamed.
2. Select the “Rename” option to display the Rename Device Group dialog box.
3. Rename the device group. Then click on the
4.4 LOADING DEVICE GROUPS
Device groups which have been closed can be reloaded using this function.
1. Click on File->Load Device Groups on the main menu.
button.
PN 613-000381 Rev B
Page 21 of 129
User's Guide
2. Specify the file(s) to be loaded.
3. Click the
button.
4. Once the loading is complete, the device groups with their respective devices will be displayed in the Device Families Pane.
4.5 CLOSING
DEVICE GROUPS
Unlike deleting, closing device groups will only "unload" the device groups. Unloaded device groups can be "reloaded" later using the "Load Device Groups" function.
1. To close a device group, click on File->Close Device Groups on the main menu to display the Close Device Groups dialog box.
2. Set the Family Filter to the device family of the device group to be closed.
PN 613-000381 Rev B
Page 22 of 129
User's Guide
3. Select the device group to close.
4. Finally, click on the
button.
PN 613-000381 Rev B
Page 23 of 129
User's Guide
5 DEVICE DEFINITIONS
Devices must first be defined before they can be included in any operation. Also, TELNET LOGIN support for a device must be enabled in order for AlliedView-UM to interface with
it.
5.1 CREATING
A DEVICE DEFINITION
1. Before you add any new devices, make sure you have already defined a Device Group. If you have not done so, please create one using the steps described in the previous section, Creating a Device Group.
2. Click on the
Device->Add Device option.
PN 613-000381 Rev B Page 24 of 129
User's Guide
3. The Add New Device dialog box will be displayed with the input fields blank or set to a default value:
IP Address - This is the IP Address of the device. Login Name - This is the user account recognized by the device. AlliedView-UM will login to the
device using this account to perform the different operations.
Password - This is the password for the login name. SNMP Read Community – This is the SNMP Read Community name that AlliedView-UM will use
to retrieve the device’s Model, Serial Number, System Description and Configuration file. By default, this value is set to “public”. (This field only applies to devices that use AlliedWare™ management
PN 613-000381 Rev B
Page 25 of 129
User's Guide
software. You may ignore this field when adding devices that use non-AlliedWare™ management software.)
Timeout - When retrieving the device's information, this is the number of seconds AlliedView-UM
will wait for a response before retrying. (This field only applies to devices that use AlliedWare™ management software. You may ignore this field when adding devices that use non-AlliedWare™ management software.)
Retries - This is the number of times AlliedView-UM will try to retrieve the Device Model, Serial
Number, System Description and Configuration file before displaying an error message. (This field only applies to devices that use AlliedWare™ management software. You may ignore this field when adding devices that use non-AlliedWare™ management software.)
System Name - This is an arbitraty name for the device. System Description - This is an abitrary description for the device. Configuration File - This is the configuration file that will be assigned for this device.
PN 613-000381 Rev B
Page 26 of 129
User's Guide
4. Once the fields in step (3) have been set, click on the button.
PN 613-000381 Rev B
Page 27 of 129
User's Guide
5. AlliedView-UM will retrieve the Serial Number and Device Model. If the retrieval is successful, the Device Family, Device Model, Serial Number, System Name, System Description and Configuration File fields will be set to that of the device. (For devices that run on non-AlliedWare™ management software, the Serial Number will be set to "N/A".) The Device Group combo box will also be populated with the groups defined under the device family.
6. Click on the
PN 613-000381 Rev B
button to add the new device.
Page 28 of 129
User's Guide
7. After the device is added, the Device Families Pane will be updated with a new node represented by the IP address of that device.
8. If you decide not to continue adding the device, click on the
5.2 LOADING
DEVICE DEFINITIONS FROM A COMMA SEPARATED VALUE (CSV) FILE
An alternative way of adding or updating multiple devices is by pre-defining them in a Comma Separated Value (CSV) file. AlliedView-UM then imports the definitions contained in this file and adds them to the specified device group.
The format of a CSV device definition is as follows:
IP_Address, login_name, password, system_name, system_description, SNMP_read_community, SNMP_timeout, SNMP_retry, device_group, configuration_file
During the operation, AlliedView-UM will check if the IP_Address field of an entry is already defined in the Device Family Tree. If the entry is already defined, then AlliedView-UM will update the existing device definition with the values from the CSV file entry. Otherwise, if the entry does not exist in the Device Family Tree, then AlliedView-UM will create a new Device Definition.
The system_name, system_description and configuration_file fields may be set to the following values:
<value> - If a value is provided, then AlliedView-UM will use that value for the device definition.
button.
<blank> - When importing a device definition, if the field is blank (no value), then AlliedView-UM
will retrieve the value from the target device. When updating an existing device definion, if the field is blank, then AlliedView-UM will not update the corresponding field in the device definition.
"*" (asterisk) - When updating a device definition, if the field is set to "*", then AlliedView-UM will
retrieve the value from the target device. When importing a device defintion, if this field is set to "*", then AlliedView-UM will also retrieve the value from the target device.
The following is a sample of a typical CSV file:
192.168.10.9, manager, friend, Main, Used by QA Group, public, 10, 3, Security, tomato.cfg
PN 613-000381 Rev B
192.168.10.11, manager, friend, , ,public,10,3,Security,lab.cfg
192.168.10.30, manager, friend, , , , , , 8400_Group,
192.168.10.31, manager, friend, , , , , , 8400_Group,*
Page 29 of 129
User's Guide
1. To load device definitions from a CSV file, click on File->Import/Update Devices on the menu.
2. Specify the file to import and click on the import the CSV format device definition entries it contains.
PN 613-000381 Rev B
button. AlliedView-UM will then open that file and
Page 30 of 129
User's Guide
3. After the import process is completed, AlliedView-UM will display a summary window containing a list of the devices that were imported or updated and those that encountered errors. Click on the
button to close the window.
PN 613-000381 Rev B
Page 31 of 129
User's Guide
4. The IP addresses of the newly imported files will be added to the Device Families Pane under the specified device group.
5. If a device device group is not specified for a device entry in the CSV file, AlliedView-UM will create a group called, "Default" under the appropriate Device Family. It will then assign the device to that group.
PN 613-000381 Rev B
Page 32 of 129
User's Guide
5.3 VIEWING
DEVICE DEFINITIONS
1. Double-click the IP address of a device on the Device Families Pane.
PN 613-000381 Rev B
Page 33 of 129
User's Guide
2. The Edit Device dialog box will be displayed containing information for the selected device.
PN 613-000381 Rev B
Page 34 of 129
User's Guide
5.4 MODIFYING
DEVICE DEFINITIONS
1. Display the Device Definition to be modified. (See the previous section, Viewing Device Definitions)
2. Once the Edit Device dialog box is displayed, the information for the selected device can modified.
3. If you modify the IP Address field, it is highly recommended that you refresh the values of the Device Family, Device Model, Serial Number, System Name, System Description and Configuration File fields by
clicking on the
PN 613-000381 Rev B
button.
Page 35 of 129
User's Guide
4. After modifying the values, click on to apply the changes.
PN 613-000381 Rev B
Page 36 of 129
User's Guide
5.5 DELETING
DEVICE DEFINITIONS
Method 1:
1. Click the IP address of the device on the Device Families Pane.
2. Select Device->Delete Device from the main menu.
1. A confirmation dialog box will be displayed. Click
to proceed with the deletion.
Method 2:
1. Right click on the IP address of the device on the Device Families Pane.
2. Select Delete from the popup menu.
3. Click on the confirmation dialog box to proceed with the deletion.
PN 613-000381 Rev B
Page 37 of 129
User's Guide
6 EXPORTING DEVICE SERIAL NUMBERS
This function only applies to devices that use AlliedWare™ management software. AlliedView-UM has the option to export the Serial Number of devices to a serial number file. The file can
then be uploaded onto WebGen. WebGen reads the serial numbers from the file and generates the corresponding license list file needed for performing a Release Upgrade or an Enable Features operation.
The following is a sample of the contents of a typical License Request file:
12304543
NOTE: As of this time, the WebGen interface for accepting the serial number file from AlliedView-UM to generate a license list file is
not yet available. For the time being, you would need to manually supply WebGen with the device serial numbers to generate the required passwords.
45689321 78916768
You would then have to manually create the corresponding license list file using the formats discussed in the succeeding sections.
1. To generate a Serial Number file, click on File->Export Serial Numbers on the main menu.
PN 613-000381 Rev B Page 38 of 129
User's Guide
2. The Export Serial Numbers dialog box will be displayed. Select the devices by moving their respective IP addresses from the Available Devices list into the Selected Devices list.
3. If there are plenty of devices available, use the Family, Group and Model filters to narrow down the selection process.
4. After making the selection, generate the License Request File by clicking the
button.
5. The Save Serial Numbers dialog box will be displayed.
6. Specify the filename to be used for the Serial Numbers file.
PN 613-000381 Rev B
Page 39 of 129
A
User's Guide
7. Finally, click the button.
6.1 LICENSE
Create a text file containing the following information:
Example:
LIST FILE FOR RELEASE UPGRADE (ALLIEDWARE) OPERATIONS
<upgradeList> <device serialNumber="nnnnnnnnn"> <swFileName>release_filename</swFileName> <swVersion>release version</swVersion> <swLicencePassword>password</swLicencePassword> </device> : : </upgradeList>
<upgradeList> <device serialNumber="12345678"> <swFileName>86s-261.rez</swFileName> <swVersion>2.6.1</swVersion> <swLicencePassword>ABCD12345678</swLicencePassword> </device> <device serialNumber="87654321"> <swFileName>86s-261.rez</swFileName> <swVersion>2.6.1</swVersion> <swLicencePassword>1234AAAABBBB</swLicencePassword> </device> </upgradeList>
6.2 LICENSE
LIST FILE FOR ENABLE FEATURES OPERATIONS
Create a text file containing the following information:
<upgradeList> <device serialNumber="nnnnnnnnn"> <featureName>feature_name</swFileName> <featurePassword>password</swLicencePassword> </device> : : </upgradeList>
Example:
<upgradeList>
PN 613-000381 Rev B
<device serialNumber="12345678"> <featureName>AT-AR-9800FL3UPGRD (Full L3 Upgrade; 9800) – ATI,
T-9800SecPk-00 (Security Pack; 9800) – ATI</swFileName>
<featurePassword>AAAA1234BBBB5678CCCC90</swLicencePassword>
Page 40 of 129
A
User's Guide
</device> <device serialNumber="87654321"> <featureName>AT-AR-9800FL3UPGRD (Full L3 Upgrade; 9800) – ATI,
T-9800SecPk-00 (Security Pack; 9800) – ATI</swFileName> <featurePassword>1234AAAA1234BBBBADBA47</swLicencePassword> </device> </upgradeList>
PN 613-000381 Rev B
Page 41 of 129
User's Guide
7 RELEASE UPGRADE OPERATION
AlliedView-UM provides two types of Release Upgrade Operations: Release Upgrade (AlliedWare) and Release Upgrade (Other).
Devices that use AlliedWare™ software can be upgraded with new software release files through the Release Upgrade (AlliedWare) Operation pane. The software release files for these devices require special licenses in order to be properly installed.
To display this pane, click on the
button on the Operations
Selection pane.
PN 613-000381 Rev B Page 42 of 129
User's Guide
Devices that do not use AlliedWare™ software can be upgraded with new software release files through the Release Upgrade (Other) Operation pane. The software release files for these devices do not require any licenses.
To display this pane, click on the Selection pane.
7.1 CREATING
Software Selection
PN 613-000381 Rev B
button on the Operations
A RELEASE UPGRADE PROFILE
Page 43 of 129
User's Guide
1. License List Filename - Specify the license key list to use for the release. After choosing the License List File, the release file to be used will be displayed in the Release Filename field.
Release Filename - This is a read-only field that displays the filename of the software release file that
2. will be installed on the target device(s).
Upload Options - Choose one of the following options:
3.
Upload - Uploads the release file only.
Upload and enable - Uploads and enables the release file only.
Upload and set as temporary - Uploads, enables, and sets the release file as the temporary release
file.
Upload and set as preferred - Uploads, enables and sets the release file as the preferred release
file.
File Deletion Options
4.
Delete old release files if memory space is insufficient checkbox - If the devices to be upgraded
have limited memory space (e.g. routers), there might be a need to delete the existing release files in order to accommodate the new release file. If a release file cannot be downloaded due to space limitations and this option is checked, AlliedView-UM will delete any release files residing in the device except for the currently installed release. If unchecked, and there is not enough space to accommodate the new release file, AlliedView-UM will fail the operation.
Delete currently installed release 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, AlliedView-UM will also delete the currently installed release file if there is still insufficient space in the device after deleting the other release files.
Reboot device after updating checkbox - If "Upload and set as temporary" or "Upload and set as
5. preferred" is chosen as the Upload Option, this checkbox will be enabled. When checked, AlliedView-UM will reboot the device after a performing the software upgrade.
PN 613-000381 Rev B
Page 44 of 129
User's Guide
1. Release Filename - Specify the software release file to be used.
2. Boot Filename - Specify the boot file to be used. This is only applicable to the AT-8000S Family Devices.
PN 613-000381 Rev B
Page 45 of 129
User's Guide
Upload Parameters
1. Server - This is the address for the server that contains the release 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.
Destination - This sets the location where the new release file will be stored. This can be set to FLASH
2. or NVS.
Protocol - This specifies the protocol that the server supports. This can be set to HTTP or TFTP.
3.
1.
TFTP Server - This is the IP address of the TFTP server that contains the release file. Destination Filename - This is a read-only field displays the name under which the software release file
2. is to be stored on the switch.
Device Selection For devices that use AlliedWare™ management software, a license list file must be specified before
device selection can be performed. After selecting a license list file, the serial numbers contained within will be checked against the serial numbers of the currently loaded devices. The IP Address of each matching pair will be added to the Available Devices list.
For devices that use non-AlliedWare™ management software, a release filename must be specified. After specifying the release file, the Available Devices list will be populated with the IP Addresses of the device definitions that can use the specified software release file.
Device selection is performed as follows:
PN 613-000381 Rev B
Page 46 of 129
User's Guide
1. Clicking the
button moves all selected/highlighted IP addresses from the Available Devices list
to the Selected Devices list.
2. Clicking the
button moves all IP addresses form the Available Devices list to the Selected
Devices list.
3. Clicking the
button moves all the selected/highlighted IP address from the Selected Devices
list to the Available Devices list.
4. Clicking the
button moves all the IP address from the Selected Devices list to the Available
Devices list.
5. The
Family combo box will be populated with the Device Family names applicable to the release file
indicated in the Release Filename field. Clicking on this combo box and selecting a specific
Family will limit the contents of the Available Devices list to that of the IP addresses of the devices that
belong to the selected
6. The
Group combo box will be populated with the device groups defined under the Device Family
selected in the previous step. Clicking on the
Device Family.
Group combo box and selecting a specific device group will
limit the contents of the Available Devices list to that of the IP addresses of the devices that belong to the selected Group. However, the contents of the Selected Devices list will not be affected. For instance, suppose that Selected Devices list contains IP addresses for devices that belong to Group “A”. Then, Group “B” has been chosen in the Device Group combo box. The Available Devices list will now only contain the IP addresses of the devices that belong to Group “B”. However, the Selected Devices list will remain unchanged.
Device
7. The
Model combo box will be populated with the models supported by the Device Family or Group
selected in the previous step. Clicking on the limit the contents of the Available Devices list to that of the IP addresses of the devices that belong to the selected Model. However, the contents of the Selected Devices list will not be affected.
PN 613-000381 Rev B
Model combo box and selecting a specific device model will
Page 47 of 129
User's Guide
7.2 SAVING
1. Click on the button.
A RELEASE UPGRADE PROFILE
2. The Save Release Upgrade (AlliedWare) or (Other) dialog box will be displayed.
3. Specify the filename.
4. Finally, click on the
PN 613-000381 Rev B
button.
Page 48 of 129
User's Guide
7.3 LOADING
1. Click on the
2. A confirmation dialog box will be displayed. Click
A RELEASE UPGRADE PROFILE
button.
to proceed.
3. The Load Release Upgrade (AlliedWare) or (Other) Profile dialog box will be displayed. Specify the
filename of the profile to be loaded.
4. Finally, click on the
Operation profile.
PN 613-000381 Rev B
button. AlliedView-UM will load the specified Release Upgrade
Page 49 of 129
User's Guide
NOTE: The Release Upgrade (AlliedWare) or (Other) Operation profile contains the Selected Devices list. While loading,
AlliedView-UM checks each item in this list against the currently loaded devices in the Device Families Pane. Only entries that have a matching device in the Device Families Pane will be loaded and added to the Selected Devices list in the Release Upgrade pane.
A summary window will be displayed indicating which entries were successfully added.
PN 613-000381 Rev B
Page 50 of 129
User's Guide
7.4 STARTING The Release Upgrade Operation can only be started when the parameters have been properly set.
1. Click on the
THE RELEASE UPGRADE (ALLIEDWARE) OR (OTHER) OPERATION
button.
2. A progress window will be displayed, indicating the overall status of the operation. When the
Release Upgrade operation ends, the Operation Logs pane will be updated to contain detailed information about the operation for each device.
3. Clicking the
or the button will abort the Release Upgrade operation. Depending on the time this button is clicked, the operation may or may not complete for devices that are in progress. Devices that were not able to complete the operation will have a status of “Aborted”.
NOTE: Aborting an operation may leave some devices in an undesirable state.
PN 613-000381 Rev B
Page 51 of 129
User's Guide
8 INTERIM/MAINTENANCE RELEASE UPGRADE OPERATION
Devices can be upgraded with a new Interim or Maintenance Release file through the Interim/Maintenance Release Upgrade Operation pane.
To display this pane, click on the
button on the Operations
Selection pane. The Interim/Maintenance Release Upgrade Operation is only applicable to devices that use AlliedWare™
management software.
PN 613-000381 Rev B Page 52 of 129
User's Guide
8.1 CREATING
Software Selection
1. Interim/Maintenance Release Filename - Specify the interim/maintenance release file to use.
Upload Options - Choose one of the following options:
2.
  
AN INTERIM/MAINTENANCE RELEASE UPGRADE PROFILE
Upload - Uploads the interim/maintenance release file only. Upload and enable - Uploads and enables the interim/maintenance release file only. Upload and set as temporary - Uploads, enables, and sets the interim/maintenance release file
as the temporary release file.
Upload and set as preferred - Uploads, enables and sets the interim/maintenance release file
as the preferred release file.
File Deletion Options
3.
Delete old release files if memory space is insufficient checkbox - If the devices to be
upgraded have limited memory space (e.g. routers), there might be a need to delete the existing release files in order to accommodate the new release file. If a release file cannot be downloaded due to space limitations and this option is checked, AlliedView-UM will delete any release files residing in the device except for the currently installed release. If unchecked, and there is not enough space to accommodate the new release file, AlliedView-UM will fail the operation.
Delete currently installed release 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, AlliedView-UM will also delete the currently installed release file if there is still insufficient space in the device after deleting the other release files.
Reboot device after updating checkbox - If "Upload and set as temporary" or "Upload and set
as preferred" is chosen as the Upload Option, this checkbox will be enabled. When checked, AlliedView-UM will reboot the device after a performing the software upgrade.
PN 613-000381 Rev B
Page 53 of 129
User's Guide
Upload Parameters
1.
Server - This is the address for the server that contains the interim/maintenance release 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.
Destination - This sets the location where the new interim/maintenance release file will be stored.
2. This can be set to FLASH or NVS.
Protocol - This specifies the protocol that the server supports. This can be set to HTTP or TFTP.
3.
Device Selection Before device selection can be performed, an Interim/Maintenance Release File must be specified. After
selecting an Interim/Maintenance Release File, the Available Devices list will be populated with the IP addresses of the devices to which the specified interim release file can be applied to.
Except for the above mentioned process, device selection is similar to that of the Release Upgrade Operation pane.
PN 613-000381 Rev B
Page 54 of 129
User's Guide
8.2 SAVING
1. Click on the
AN INTERIM/MAINTENANCE RELEASE UPGRADE PROFILE
button.
2. The Save Interim/Maintenance Release Upgrade Profile dialog box will be displayed.
3. Specify the filename.
4. Finally, click on the
PN 613-000381 Rev B
button.
Page 55 of 129
User's Guide
8.3 LOADING
1. Click on the
2. A confirmation box will be displayed. Click
AN INTERIM/MAINTENANCE RELEASE UPGRADE PROFILE
button.
to proceed.
3. The Load Interim/Maintenance Release Upgrade Profile dialog box will be displayed. Specify the filename of the profile to be loaded.
4. Finally, click on the Release Upgrade Operation profile.
PN 613-000381 Rev B
button. AlliedView-UM will load the specified Interim/Maintenance
Page 56 of 129
T
User's Guide
NOTE:
he Interim/Maintenance Release Upgrade Operation profile contains the Selected Devices list. While loading, the AlliedView-UM checks each item in this list against the currently loaded devices in the Device Families Pane. Only entries that have a matching device in the Device Families Pane will be loaded and added to the Selected Device list in the Interim/Maintenance Release Upgrade pane.
A summary window will be displayed indicating which entries were successfully added.
PN 613-000381 Rev B
Page 57 of 129
User's Guide
8.4 STARTING
The Interim/Maintenance Release Upgrade Operation can only be started when the parameters have been properly set.
1. Click on the button.
THE INTERIM/MAINTENANCE RELEASE UPGRADE OPERATION
2. A progress window will be displayed, indicating the overall status of the operation. When the Interim/Maintenance Release Upgrade operation ends, the Operation Logs pane will be updated to contain detailed information about the operation for each device.
3. Clicking the operation. Depending on the time this button is clicked, the operation may or may not complete for devices that are in progress. Devices that were not able to complete the operation will have a status of “Aborted”.
PN 613-000381 Rev B
or the button will abort the Interim/Maintenance Release Upgrade
Page 58 of 129
User's Guide
NOTE: Aborting an operation may leave some devices in an undesirable state.
PN 613-000381 Rev B
Page 59 of 129
User's Guide
9 PATCH UPGRADE OPERATION
Devices can be upgraded with patches through the Patch Upgrade Operation pane.
To display this pane, click on the
button on the Operations Selection
pane. The Patch Upgrade Operation is only applicable to devices that use AlliedWare™ management software.
PN 613-000381 Rev B Page 60 of 129
User's Guide
9.1 CREATING
A PATCH UPGRADE PROFILE
Software Selection
1. Patch Filename - Specify the Patch file to use.
2. Upload Options - Choose one of the following options:
Upload - Uploads the Patch file only. Upload and set as temporary - Uploads, enables, and sets the Patch file as the temporary Patch
file.
Upload and set as preferred - Uploads, enables and sets the Patch file as the preferred Patch
file.
3. File Deletion Options Delete old patch files if memory space is insufficient checkbox - If the devices to be
upgraded have limited memory space (e.g. routers), there might be a need to delete the existing patch files in order to accommodate the new patch file. If a patch file cannot be downloaded due to space limitations and this option is checked, AlliedView-UM will delete any patch files residing in the device except for the currently installed patch. If unchecked, and there is not enough space to accommodate the new patch file, AlliedView-UM will fail the operation.
Delete currently installed patch 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, AlliedView-UM will also delete the currently installed patch file if there is still insufficient space in the device after deleting the other patch files.
Reboot device after updating checkbox - If "Upload and set as temporary" or "Upload and set
as preferred" is chosen for the Upload Option, this checkbox will be enabled. When checked, AlliedView-UM will reboot the device after a performing the software upgrade.
PN 613-000381 Rev B
Page 61 of 129
User's Guide
Upload Parameters
1. Server - This is the address for the server that contains the Patch 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 Patch 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, an patch file must be specified. After specifying a patch file, the Available Devices list will be populated with the IP addresses of the devices to which the specified patch file can be applied to.
Except for the above mentioned process, device selection is similar to that of the Release Upgrade Operation pane.
PN 613-000381 Rev B
Page 62 of 129
User's Guide
9.2 SAVING
1. Click on the button.
A PATCH UPGRADE PROFILE
2. The Save Patch Upgrade Profile dialog box will be displayed.
3. When prompted, specify the filename.
4. Finally, click on the
PN 613-000381 Rev B
button.
Page 63 of 129
User's Guide
9.3 LOADING
1. Click on the button.
2. A confirmation box will be displayed. Click
A PATCH UPGRADE PROFILE
to proceed.
3. The Load Patch Upgrade Profile dialog box will be displayed. Specify the filename of the profile to be
loaded.
4. Finally, click on the
Operation profile.
PN 613-000381 Rev B
button. AlliedView-UM will load the specified Patch Upgrade
Page 64 of 129
User's Guide
NOTE: The Patch Upgrade Operation profile contains the Selected Devices list. While loading, AlliedView-UM checks each item in this
list against the currently loaded devices in the Device Families Pane. Only entries that have a matching device in the Device Families Pane will be loaded and added to the Selected Devices list in the Patch Upgrade Operation pane.
A summary window will be displayed indicating which entries were successfully added.
PN 613-000381 Rev B
Page 65 of 129
User's Guide
9.4 STARTING THE PATCH UPGRADE OPERATION
The Patch Upgrade Operation can only be started when the parameters have been properly set.
1. Click on the button.
2. A progress window will be displayed, indicating the overall status of the operation. When the Patch
Upgrade operation ends, the Operation Logs pane will be updated to contain detailed information about the operation for each device.
3. Clicking the
or the button will abort the Patch Upgrade operation. Depending on the time this button is clicked, the operation may or may not complete for devices that are in progress. Devices that were not able to complete the operation will have a status of “Aborted”.
NOTE: Aborting an operation may leave some devices in an undesirable state.
PN 613-000381 Rev B
Page 66 of 129
User's Guide
10 CONFIGURATION FILE UPDATE
Device configurations can be updated through the Configuration File Update Operation pane.
To display this pane, click on the
button on the Operations Selection
pane.
PN 613-000381 Rev B Page 67 of 129
User's Guide
10.1 CREATING
A CONFIGURATION FILE UPDATE PROFILE
Update Options
1. Upload Options - Choose one of the following options:
Upload - Uploads the Configuration file only. Upload and set - Uploads and sets the configuration file as the Configuration to be used by the
device.
2. File Deletion Options
Delete old configuration files if memory space is insufficient checkbox - If the devices to
be upgraded have limited memory space (e.g. routers), there might be a need to delete the existing Configuration files in order to accommodate the new configuration file. If a Configuration file cannot be downloaded due to space limitations and this option is checked, AlliedView-UM will delete any Configuration files residing in the device except for the currently set Configuration file. If unchecked, and there is not enough space to accommodate the new Configuration file, AlliedView-UM will fail the operation.
Delete currently used configuration 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, AlliedView-UM will also delete the currently set Configuration file if there is still insufficient space in the device after deleting the other configuration files.
3. Reboot device after updating checkbox - If the “Upload and set” is chosen for the Upload Option, this checkbox will be enabled. When checked, AlliedView-UM will reboot the device after performing the update.
NOTE: All elements defined in Upload Options panel are disregarded for the AT-8000 family, AT-8300GB family, AT-9000 family,
AT-9410GB and AT-9700 families.
NOTE: All elements defined in Upload Options panel except "Upload" and "Upload and set" are disregarded for the AT-8400 family,
AT-8500 and AT-9400 families. All other update options apply only to devices that use AlliedWare™ management software. During the Configuration File Update operation, AlliedView-UM will ignore the options that are not applicable.
PN 613-000381 Rev B
Page 68 of 129
User's Guide
NOTE: For the AT-8000S Family,
• Choosing the “Upload” means that the contents of the specified configuration file will be added to those in the
running configuration of the device, thus, the loaded configuration will take effect as soon as the operation ends. However, the loaded configuration will not be copied to the startup configuration which might be erased after rebooting the device.
• Choosing the “Upload and Set” means that the contents of the specified configuration file will replace the startup
configuration of the device, thus, the loaded configuration will take effect after rebooting the device.
• The “Delete old configuration files if memory space is insufficient” and “Delete currently used configuration file if
memory space is insufficient” options are disregarded by the application.
PN 613-000381 Rev B
Page 69 of 129
User's Guide
Upload Parameters
1. Server - This is the address for the server that contains the Configuration 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 Configuration 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.
NOTE: The Destination field is not applicable to devices that use non-AlliedWare™ management software and will be ignored during
the Configuration File Update operation. Since devices that use non-AlliedWare™ management software only support TFTP, the Protocol field will also be ignored but
will internally be set to "TFTP" during the Configuration File Update operation.
PN 613-000381 Rev B
Page 70 of 129
User's Guide
Device Selection
The Available Devices list will be initially populated with the IP addresses of the devices which have a Configuration file specified in its device definition.
Except for the above mentioned process, device selection is similar to that of the Release Upgrade Operation pane.
PN 613-000381 Rev B
Page 71 of 129
User's Guide
10.2 SAVING
1. Click on the button.
A CONFIGURATION FILE UPDATE PROFILE
2. The Save Configuration File Update Profile dialog box will be displayed.
3. Specify the filename.
4. Finally, click on the
PN 613-000381 Rev B
button.
Page 72 of 129
User's Guide
10.3 LOADING
1. Click on the button.
2. A confirmation box will be displayed. Click
A CONFIGURATION FILE UPDATE PROFILE
to proceed.
3. When prompted, specify the filename of the profile to load.
4. Finally, click on the
Update Operation profile file.
PN 613-000381 Rev B
button. AlliedView-UM will load the specified Configuration File
Page 73 of 129
User's Guide
NOTE: The Configuration File Update profile contains the Selected Devices list. While loading, AlliedView-UM checks each item in this
list against the currently loaded devices in the Device Families Pane. Only entries that have a matching device in the Device Families Pane will be loaded and added to the Selected Devices list in the Configuration File Update Operation pane.
A summary window will be displayed indicating which entries were successfully added.
PN 613-000381 Rev B
Page 74 of 129
User's Guide
10.4 STARTING
The Configuration File Update Operation can only be started when the parameters have been properly set.
1. Click on the button.
THE CONFIGURATION FILE UPDATE OPERATION
2. A progress window will be displayed, indicating the overall status of the operation. When the
Configuration File Update operation ends, the Operation Logs pane will be updated to contain detailed information about the operation for each device.
3. Clicking the
Depending on the time this button is clicked, the operation may or may not complete for devices that are in progress. Devices that were not able to complete the operation will have a status of “Aborted”.
PN 613-000381 Rev B
or the button will abort the Configuration File Update operation.
Page 75 of 129
User's Guide
NOTE: Aborting an operation may leave some devices in an undesirable state.
PN 613-000381 Rev B
Page 76 of 129
User's Guide
11 EXECUTE SCRIPT FILE
Script files can be uploaded and executed on target devices through the Execute Script File Operation Pane
To display this pane, click on the
button on the Operations
Selection pane. The Execute Script File Operation is only applicable to devices that use AlliedWare™ management
software.
PN 613-000381 Rev B Page 77 of 129
User's Guide
11.1 CREATING
AN EXECUTE SCRIPT FILE PROFILE
Script File Selection
1. Script Filename - Specify the Script file to use.
2. Upload Options - Choose one of the following options:
Upload - Uploads the Script file only. Upload and execute - Uploads and executes the script file.
3. File Deletion Options Overwrite existing script file checkbox - When this option is checked and the device already
has a script file with the same filename, then the script file on the device will be overwritten with the new script file. Otherwise, if this option is un-checked, and the same condition occurs, then AlliedView-UM will fail the operation.
Delete old script files if memory space is insufficient checkbox - When this option is
checked, and the device cannot accomodate the new script file due to lack of memory space, AlliedView-UM will also delete the all script files (*.scp) if there is insufficient space in the device. Otherwise, if this option is un-checked and there is insufficient memory space, then AlliedView-UM will fail the operation.
Upload Parameters
1. Server - This is the address for the server that contains the Script 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 Script 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
The Available Devices list will be initially populated with IP addresses of applicable AlliedWare devices.
PN 613-000381 Rev B
Page 78 of 129
User's Guide
Except for the above mentioned process, device selection is similar to that of the Reboot Device Operation pane.
PN 613-000381 Rev B
Page 79 of 129
User's Guide
11.2 SAVING
1. Click on the
AN EXECUTE SCRIPT FILE PROFILE
button.
2. The Save Execute Script File Profile dialog box will be displayed.
3. Specify the filename.
4. Finally, click on the
button.
PN 613-000381 Rev B
Page 80 of 129
User's Guide
11.3 LOADING
1. Click on the
AN EXECUTE SCRIPT FILE PROFILE
button.
2. A confirmation box will be displayed. Click
to proceed.
3. When prompted, specify the filename of the profile to load.
4. Finally, click on the
button. AlliedView-UM will load the specified Execute Script File
Operation profile file.
PN 613-000381 Rev B
Page 81 of 129
User's Guide
NOTE: The Execute Script File profile contains the Selected Devices list. While loading, AlliedView-UM checks each item in this list
against the currently loaded devices in the Device Families Pane. Only entries that have a matching device in the Device Families Pane will be loaded and added to the Selected Devices list in the Execute Script File Operation pane.
A summary window will be displayed indicating which entries were successfully added.
PN 613-000381 Rev B
Page 82 of 129
User's Guide
11.4 STARTING
The Execute Script File Operation can only be started when the parameters have been properly set.
1. Click on the
THE EXECUTE SCRIPT FILE OPERATION
button.
2. A progress window will be displayed, indicating the overall status of the operation. When the Execute Script File operation ends, the Operation Logs pane will be updated to contain detailed information about the operation for each device.
3. Clicking the
or the button will abort the Execute Script File operation. Depending on the time this button is clicked, the operation may or may not complete for devices that are in progress. Devices that were not able to complete the operation will have a status of “Aborted”.
NOTE: Aborting an operation may leave some devices in an undesirable state.
PN 613-000381 Rev B
Page 83 of 129
User's Guide
12 GUI RESOURCE FILE UPDATE
Device GUI Resources can be updated through the GUI Resource File Update Operation pane.
To display this pane, click on the pane.
The GUI Resource File Update Operation is only applicable to devices that use AlliedWare™ management software.
PN 613-000381 Rev B
button on the Operations Selection
Page 84 of 129
User's Guide
12.1 CREATING
A GUI RESOURCE FILE UPDATE PROFILE
Software Selection
1.
GUI Resource Filename - Specify the GUI Resource file to use. There are two types of GUI Resource
files:
Old Type – These are GUI Resource files for the following software releases:
2. Versions 2.4.1 and below for the AT-AR410, AT-AR700 Series, SwitchBlade Series, AT-9800 Series, and Rapier Series
New Type – These are GUI Resource files for the following software releases:
3. Versions 2.5.1 and above for the AT-AR410, AT-AR700 Series, SwitchBlade Series, AT-9800 Series, and Rapier Series
4. Upload Options - Choose one of the following options:
Upload - Uploads the GUI Resource file only. Upload and set as temporary - Uploads and sets the GUI Resource file as temporary. (This
option will be disabled if an old GUI Resource file is specified.)
Upload and set as preferred - Uploads and sets the GUI Resource file as preferred. (This option
will be disabled if an old GUI Resource file is specified.)
5. File Deletion Options Delete old GUI Resource files if memory space is insufficient checkbox - If the devices to
be upgraded have limited memory space (e.g. routers), there might be a need to delete the existing GUI Resource files in order to accommodate the new GUI Resource file. If a GUI Resource file cannot be downloaded due to space limitations and this option is checked, the AlliedView-UM will delete any GUI Resource files residing in the device except for the currently set GUI Resource file. If unchecked, and there is not enough space to accommodate the new GUI Resource file, AlliedView-UM will fail the operation.
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.
6. 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.
PN 613-000381 Rev B
Page 85 of 129
User's Guide
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.
PN 613-000381 Rev B
Page 86 of 129
User's Guide
12.2 SAVING
1. Click on the
A GUI RESOURCE FILE UPDATE PROFILE
button.
2. The Save GUI Resource File Update Profile dialog box will be displayed.
3. Specify the filename.
4. Finally, click on the
button.
PN 613-000381 Rev B
Page 87 of 129
User's Guide
12.3 LOADING
1. Click on the
A GUI RESOURCE FILE UPDATE PROFILE
button.
2. A confirmation box will be displayed. Click
to proceed.
3. The Load GUI Resource File Update Profile dialog box will be displayed.
4. Specify the filename of the profile to be loaded.
PN 613-000381 Rev B
Page 88 of 129
User's Guide
5. Finally, click on the button. AlliedView-UM will load the specified GUI Resource File Update Operation profile.
NOTE: The GUI Resource File Update operation profile contains the Selected Devices list. While loading, AlliedView-UM checks each
item in this list against the currently loaded devices in the Device Families Pane. Only entries that have a matching device in the Device Families Pane will be loaded and added to the Selected Devices list in the GUI Resource File Update Operation pane.
A summary window will be displayed indicating which entries were successfully added.
PN 613-000381 Rev B
Page 89 of 129
User's Guide
12.4 STARTING THE GUI RESOURCE FILE UPDATE OPERATION
The GUI Resource File Update Operation can only be started when the parameters have been properly set.
1. Click on the button.
2. A progress window will be displayed, indicating the overall status of the operation. When the GUI Resource File Update operation ends, the Operation Logs pane will be updated to contain detailed information about the operation for each device.
3. Clicking the
or the button will abort the GUI Resource File Update operation. Depending on the time this button is clicked, the operation may or may not complete for devices that are in progress. . Devices that were not able to complete the operation will have a status of “Aborted”.
NOTE: Aborting an operation may leave some devices in an undesirable state.
PN 613-000381 Rev B
Page 90 of 129
User's Guide
13 HELP FILE UPDATE
The Command Line Interface Help of the devices can be updated through the Help File Update Operation pane.
To display this pane, click on the pane.
The Help File Update Operation is only applicable to devices that use AlliedWare™ management software.
PN 613-000381 Rev B
button on the Operations Selection
Page 91 of 129
User's Guide
13.1 CREATING
A HELP FILE UPDATE PROFILE
Software Selection
1.
Help Filename - Specify the Help file to use. Upload Options - Choose one of the following options:
2.
Upload - Uploads the Help file only. Upload and set - Uploads and sets the Help file.
3. File Deletion Options Delete old help files if memory space is insufficient checkbox - If the devices to be
upgraded have limited memory space (e.g. routers), there might be a need to delete the existing Help files in order to accommodate the new Help file. If a Help file cannot be downloaded due to space limitations and this option is checked, AlliedView-UM will delete any Help files residing in the device except for the currently set Help file. If unchecked, and there is not enough space to accommodate the new Help file, AlliedView-UM will fail the operation.
Delete currently used help 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, AlliedView-UM will also delete the currently set Help file if there is still insufficient space in the device after deleting the other Help files.
Upload Parameters
1. Server - This is the address for the server that contains the Help 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 Help 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.
PN 613-000381 Rev B
Page 92 of 129
User's Guide
Device Selection
Before device selection can be performed, a Help file must be specified. After specifying a Help file, the Available Devices list will be populated with the IP addresses of the devices to which the Help file can be applied to.
Except for the above mentioned process, device selection is similar to that of the Release Upgrade Operation pane.
PN 613-000381 Rev B
Page 93 of 129
User's Guide
13.2 SAVING
1. Click on the
A HELP FILE UPDATE PROFILE
button.
2. The Save Help File Update Profile dialog box will be displayed.
3. Specify the filename.
4. Finally, click on the
PN 613-000381 Rev B
button.
Page 94 of 129
User's Guide
13.3 LOADING
1. Click on the
A HELP FILE UPDATE PROFILE
button.
2. A confirmation box will be displayed. Click
to proceed.
3. The Load Help File Update Profile dialog box will be displayed.
4. Specify the filename of the profile to be loaded.
PN 613-000381 Rev B
Page 95 of 129
User's Guide
5. Finally, click on the button. AlliedView-UM will load the specified Help File Update Operation profile.
NOTE: The Help File Update Operation profile contains the Selected Devices list. While loading, AlliedView-UM checks each item in
this list against the currently loaded devices in the Device Families Pane. Only entries that have a matching device in the Device Families Pane will be loaded and added to the Selected Devices list in the Help File Update pane.
A summary window will be displayed indicating which entries were successfully added.
PN 613-000381 Rev B
Page 96 of 129
User's Guide
13.4 STARTING
THE HELP FILE UPDATE OPERATION
The Help File Update Operation can only be started when the parameters have been properly set.
1. Click on the button.
2. A progress window will be displayed, indicating the overall status of the operation. When the Help File Update operation ends, the Operation Logs pane will be updated to contain detailed information about the operation for each device.
3. Clicking the
or the button will abort the Help File Update Operation. Depending on the time this button is clicked, the operation may or may not complete for devices that are in progress. Devices that were not able to complete the operation will have a status of “Aborted”.
NOTE: Aborting an operation may leave some devices in an undesirable state.
PN 613-000381 Rev B
Page 97 of 129
User's Guide
14 ENABLE FEATURES
Device features can be enabled through the Enable Features Operation pane.
To display this pane, click on the
button on the Operations Selection
pane. The Enable Features Operation is only applicable to devices that use AlliedWare™ management
software.
PN 613-000381 Rev B Page 98 of 129
User's Guide
14.1 CREATING Software Selection
1.
License List Filename - Specify the license list file to use for this operation. After choosing the License
List File, the features to be enabled will be displayed in the Feature field.
Feature – This is a read-only field that displays the name of the feature that will be enabled on the target
2. device(s).
AN ENABLE FEATURES PROFILE
PN 613-000381 Rev B
Page 99 of 129
User's Guide
Device Selection
Before device selection can be performed, a license list file must be specified. After selecting a license list file, the serial numbers contained within will be checked against the serial numbers of the currently loaded devices. The IP Address of each matching pair will be added to the Available Devices list.
Except for the above mentioned process, device selection is similar to that of the Release Upgrade Operation pane.
PN 613-000381 Rev B
Page 100 of 129
Loading...
Buy Points How it Works FAQ Contact Us Questions and Suggestions Privacy Policy Cookie Policy Terms of Use