AlliedView™-UM 2.0 USER’S GUIDE AlliedView™-UM 2.
TABLE OF CONTENTS 1 INTRODUCTION ............................................................................................................................................. 5 2 A GUIDED TOUR ............................................................................................................................................. 6 A. LAUNCHING THE APPLICATION ........................................................................................................................ 6 B. CREATING A DEVICE ..
10 CONFIGURATION FILE UPDATE ............................................................................................................... 74 A. CREATING A CONFIGURATION FILE UPDATE PROFILE ..................................................................................... 75 B. SAVING A CONGFIGURATION FILE UPDATE PROFILE ....................................................................................... 77 C. LOADING A CONFIGURATION FILE UPDATE PROFILE ..............................................
19 LICENSE REGISTRATION........................................................................................................................... 122 A. REGISTERING A LICENSE ............................................................................................................................... 122 B. MODIFYING A LICENSE ................................................................................................................................. 124 20 OPTIONS ....................................
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.
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. A. Launching the Application 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.
B. Creating a Device 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. AlliedView™-UM 2.
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. AlliedView™-UM 2.
5. The “Add New Device” dialog box should be displayed. 6. Input the IP address of your device in the IP Address field. 7. In the Login Name field, enter the user account name that AlliedView-UM will use to login to your device. 8. In the Password field, enter the appropriate password for the account you have entered in the previous step. 9. The SNMP Read Community, Timeout and Retries fields already have default values. You may change these if needed. AlliedView™-UM 2.
. 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). 11. Finally, click on the button to add the device. 12. Your new device should now be added.
C. 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 display the Patch Upgrade pane. button on the Operations Selection Pane.
D. 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. 2 A Guided Tour AlliedView™-UM 2.
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. AlliedView™-UM 2.
A. Device Families Pane The Device Families Pane is used to manage the devices that AlliedView-UM can interface with. The root nodes of the Device Families represent the AT Device Families that are currently supported by this application. The AT Device Firmware root node is represented by a ( ) icon followed by the AT Device Family name represented by a ( ). Each AT Device Family node can contain Device Group nodes. A Device Group node is represented by a ( ) icon followed by the Device Group name.
B. Operations Selection Pane The Operations Selection Pane allows you to select an operation profile to create. 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 (AlliedWare) Operations Pane will be displayed. AlliedView™-UM 2.
C. 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 button. D. Operation Logs Pane The Operation Logs Pane displays the status and results of operations performed. 3 Main Window AlliedView™-UM 2.
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. A. Creating a Device Group 1. Click on the 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 AlliedView™-UM 2.0 USER’S GUIDE button.
B. Deleting a Device Group Method 1: 1. On the Device Families Pane, select the device group node to be deleted. 2. Click on the Device->Delete Device Group option. 3. A confirmation dialog box will be displayed. Click on deletion. to proceed with the Method 2: 1. Right click on the device group node to be deleted. A popup menu will appear. AlliedView™-UM 2.
2. Select the Delete option. 3. A confirmation dialog box will be displayed. Click deletion. to proceed with the NOTE: Any device under the deleted device group will be deleted as well. C. Renaming a Device Group Method 1: 1. On the Device Families Pane, select the device group node to be renamed. 2. Click on the Device->Rename Device Group option. AlliedView™-UM 2.
3. The Rename Device Group dialog box will be displayed. The Device Group Name field contains the currently assigned name for that device group. Type in the new name in the Device Group Name field. 4. Finally, click on the button. 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 button. D.
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 E. 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. AlliedView™-UM 2.
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. AlliedView™-UM 2.
3. Select the device group to close. 4. Finally, click on the button. 4 Device Group AlliedView™-UM 2.
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. A. 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. AlliedView™-UM 2.
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. AlliedView™-UM 2.
• • • • • • SNMP Read Community - This is the SNMP Read Community name that AlliedView-UM will use to retrieve the device’s Model, Serial Number, System Name, Device Description and Configuration filename. By default, this value is set to “public”. (This field only applies to devices that use AlliedWare™ and AlliedWare Plus™ management software.
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. AlliedView™-UM 2.
6. Click on the button to add the new device. 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 button. B. Loading/Updating 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.
The following is a sample of a typical CSV file: 192.168.10.9, manager, friend, Main, Used QA Group,public,10,3,Security,tomato.cfg 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,* 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 button.
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 AlliedView™-UM 2.0 USER’S GUIDE button to close the window.
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. C. Discovering New Devices AlliedView™-UM 2.
Another method for adding or updating multiple devices is via the Discover Devices operation. By providing a range of IP addresses, SNMP and Telnet access parameters, AlliedView-UM will be able to do scan for and create device definitions for any supported devices it may find. To perform a Discover Devices operation, select the Tools > Discover Devices menu option. This will display the Device Discovery window. Configuring the Default Access Settings 1.
To add a new network: 1. Enter an IP Address and Netmask in the IP Address and Netmask fields respectively. 2. If you wish to specify a specific range within the IP Address/Netmask pair you've just entered, select the Set of nodes option. You may then enter a Starting and/or Ending IP Address on the Start IP and End IP fields. 3. Finally, click on the button. To modify an existing network: 1. Select the network to be modified by clicking on its entry in the Networks list 2.
To delete an existing network: 1. Select the network to be deleted by clicking on its entry in the Networks list. 2. Click on the button to remove the network. 3. A confirmation box will be displayed. Click on to complete the deletion. To start the device discovery: 1. On the Networks list, you will notice that each entry has a corresponding check box. When checked, the corresponding network will be included in the device discovery scan. When unchecked, the network will be ignored.
5. When the operation is complete, a summary window will be displayed. The summary window indicates range as well as the result of the IP Addresses that were scanned. to close this window. 6. Click on the 7. Devices that were discovered during the operation will be added under the "Default" group under the appropriate Device Family. AlliedView™-UM 2.
D. Viewing Device Definitions Method 1: 1. Click the IP address of the device on the Device Families Pane. 2. Select Device->Edit Device from the main menu. AlliedView™-UM 2.
3. The Edit Device dialog box will be displayed containing information for the selected device. AlliedView™-UM 2.
Method 2: 1. Right click on the IP address of the device on the Device Families Pane. 2. Select edit from the popup menu. 3. The Edit Device dialog box will be displayed containing information for the selected device. Method 3: 1. Double-click the IP address of a device on the Device Families Pane. 2. The Edit Device dialog box will be displayed containing information for the selected device. AlliedView™-UM 2.
E. 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 be 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 4.
F. 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. 3. A confirmation dialog box will be displayed. Click deletion. to proceed with the Method 2: AlliedView™-UM 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. NOTE: AlliedView-UM does not support AT-8000S devices that are configured or setup to be in stacked mode. 5 Device Definitions AlliedView™-UM 2.
6 License List Files This section only applies to devices that use AlliedWare™ and AlliedWare Plus™ management software. A. GENERATING LICENSE REQUEST FILES 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.
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.
B. GENERATING LICENSE LIST FILES After using WEBGEN to generate Release Upgrade or Enable Features passwords, you can use the Generate License List File operation to generate the corresponding license list files. These license list files can then be used to perform the Release Upgrade (AlliedWare) or Enable Features operation. 1. To generate a License List file, select the File > Generate License List File menu option. This will display the Generate License List File dialog box. AlliedView™-UM 2.
2. If you are performing a Release Upgrade (AlliedWare) operation, select the Release License option. Otherwise, select the Feature License option. 3. On the text field, enter the following data: For AlliedWare™: AlliedView™-UM 2.
You must have one entry for each device you wish to include in the License List file. Note that you may not mix Release Upgrade (AlliedWare) and Enable Features entries. Example: Release Upgrade (AlliedWare): 123456790 enable rel=89-291.rez num=1.23456 pass=123456ABCDEF Enable Features: 1234567890 enable feature="multi" pass=1234567890ABCDEFGHIJ1234 Alternatively, instead of manually typing in the required information, you may also copy & paste the data directly from the WEBGEN results page.
For AlliedWare™: AlliedView™-UM 2.
For AlliedWare Plus™: 5. If you chose to generate a Release Upgrade (AlliedWare) License List file, the Release Licenses confirmation dialog box will be displayed. Otherwise, the Feature Licenses confirmation dialog box will be displayed. These dialog boxes will show a list of the licenses that will be included in the license list file. Click on the button to continue. AlliedView™-UM 2.
6. If you are generating a Release Upgrade (AlliedWare) License List file using an ANY License Type, you will also need to specify in the Release Filename field, the filename of the firmware to use (e.g. "89-291.rez"). After specifying the release filename, click on the specified, you may click on the AlliedView™-UM 2.0 USER’S GUIDE button. Once a valid release filename has been button to continue.
7. The Save License List file dialog box will be displayed. 8. Specify the filename for your License List file. 9. Finally, click on the button to generate the License List file. 10. After the License List file has been created, you will offered to proceed to perform a Release Upgrade (AlliedWare) or Enable Features. If you click on the button, you will be taken to the Release Upgrade (AlliedWare) or Enable Features screen with the newly generated License List file already loaded. C.
D.
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 Operations Selection pane. AlliedView™-UM 2.
Devices that do not use AlliedWare™ or AlliedWare Plus™ 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 Operation Selection pane. AlliedView™-UM 2.
A. Creating a Release Upgrade Profile Software Selection and Upload Parameters (AlliedWare) 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. 2. Release Filename - This is a read-only field that displays the filename of the software release file that will be installed on the target device(s). 3.
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. 2. Destination - This sets the location where the new release 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.
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 URL 2. Destination – this sets the location where the new release 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 of TFTP.
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: 1. Clicking the button moves all selected/highlighted IP addresses from the Available Devices list to the Selected Devices list. 2.
B. Saving a Release Upgrade Profile 1. Click on the button. 2. The Save Release Upgrade (AlliedWare), (AlliedWare+) or (Other) Profile dialog box will be displayed. 3. Specify the filename. 4. Finally, click on the button. C. Loading a Release Upgrade Profile 1. Click on the AlliedView™-UM 2.0 USER’S GUIDE button.
2. A confirmation dialog box will be displayed. Click to proceed. 3. The Load Release Upgrade (AlliedWare), (AlliedWare+), or (Other) Profile dialog box will be displayed. Specify the filename of the profile to be loaded. 4. Finally, click on the button. AlliedView-UM will load the specified Release Upgrade Operation profile. NOTE: The Release Upgrade (AlliedWare), (AlliedWare+), or (Other) Operation profile contains the Selected Devices list.
D. Starting the Release Upgrade Operation The Release Upgrade (AlliedWare), (AlliedWare+) or (Other) 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 Release Upgrade operation ends, the Operation Logs pane will be updated to contain detailed information about the operation for each device. 3.
NOTE: Aborting an operation may leave some devices in an undesirable state. 7 Release Upgrade Operation AlliedView™-UM 2.
8 Interim/Maintenance Release Upgrade Operation Devices can be upgraded with a new Interim or Maintanance Release file through the Interim/Maintenance Release Upgrade Operation pane. To display this pane, click on the Operations Selection pane. button on the The Interim/Maintenance Release Upgrade Operation is only applicable to devices that use AlliedWare™ management software. AlliedView™-UM 2.
A. Creating an Interim/ Maintenance Release Upgrade Profile Software Selection 1. Interim/Maintenance Release Filename - Specify the interim/maintenance release file to use. 2. Upload Options - Choose one of the following options: • • • • 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 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. 2. Destination - This sets the location where the new interim/maintenance release file will be stored. This can be set to FLASH or NVS. 3. Protocol - This specifies the protocol that the server supports.
2. The Save Interim/Maintenance Release Upgrade Profile dialog box will be displayed. 3. Specify the filename. 4. Finally, click on the button. C. Loading an Interim/Maintenance Release Upgrade Profile 1. Click on the button. 2. A confirmation box will be displayed. Click AlliedView™-UM 2.0 USER’S GUIDE to proceed.
3. The Load Interim/Maintenance Release Upgrade Profile dialog box will be displayed. Specify the filename of the profile to be loaded. button. AlliedView-UM will load the specified 4. Finally, click on the Interim/Maintenance Release Upgrade Operation profile. NOTE: The Interim/Maintenance Release Upgrade Operation profile contains the Selected Devices list. While loading, AlliedViewUM checks each item in this list against the currently loaded devices in the Device Families Pane.
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. or the button will abort the Interim/Maintenance 3. Clicking 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.
9 Patch Upgrade Operation Devices can be upgraded with patches through the Patch Upgrade Operation pane. To display this pane, click on the Selection pane. button on the Operations The Patch Upgrade Operation is only applicable to devices that use AlliedWare™ management software. AlliedView™-UM 2.
A. 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.
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.
2. The Save Patch Upgrade Profile dialog box will be displayed. 3. When prompted, specify the filename. 4. Finally, click on the button. C. Loading a Patch Upgrade Profile 1. Click on the button. 2. A confirmation box will be displayed. Click AlliedView™-UM 2.0 USER’S GUIDE 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 Upgrade Operation profile. button. AlliedView-UM will load the specified Patch 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.
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”.
10 Configuration File Update Device configurations can be updated through the Configuration File Update Operation pane. To display this pane, click on the Selection pane. AlliedView™-UM 2.
A. 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.
NOTE: For the AT-8000S and AT-8000GS Family, • Choosing “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.
B. Saving a Congfiguration File Update Profile 1. Click on the button. 2. The Save Configuration File Update Profile dialog box will be displayed. 3. Specify the filename. 4. Finally, click on the button. C. Loading a Configuration File Update Profile 1. Click on the AlliedView™-UM 2.0 USER’S GUIDE 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 Configuration File Update Operation profile file. 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.
D. Starting the Configuration File Update Operation The Configuration 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 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 or the button will abort the Configuration File Update operation.
NOTE: Aborting an operation may leave some devices in an undesirable state. 10 Configuration File Update AlliedView™-UM 2.
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 Operations Selection pane. button on the The Execute Script File Operation is only applicable to devices that use AlliedWare™ and AlliedWarePlus™ management software. A. Creating a Execute Script File Profile Script File Selection AlliedView™-UM 2.
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.
B. Saving an Execute Script File Profile 1. Click on the button. 2. The Save Execute Script File Profile dialog box will be displayed. 3. Specify the filename. 4. Finally, click on the button. C. Loading an Execute Script File Profile 1. Click on the AlliedView™-UM 2.0 USER’S GUIDE 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. 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.
D. Starting the Execute Script File Operation The Execute Script File 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 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.
NOTE: Aborting an operation may leave some devices in an undesirable state. 11 Execute Script File AlliedView™-UM 2.
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 Selection pane. button on the Operations The GUI Resource File Update Operation is only applicable to devices that use AlliedWare™ management software. AlliedView™-UM 2.
A. 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: o 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: o Versions 2.5.
• 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.
2. The Save GUI Resource File Update Profile dialog box will be displayed. 3. Specify the filename. 4. Finally, click on the button. C. Loading a GUI Resource File Update Profile 1. Click on the button. 2. A confirmation box will be displayed. Click AlliedView™-UM 2.0 USER’S GUIDE 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. 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.
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.
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 Selection pane. button on the Operations The Help File Update Operation is only applicable to devices that use AlliedWare™ management software. AlliedView™-UM 2.
A. Creating a Help File Update Profile Software Selection 1. Help Filename - Specify the Help file to use. 2. Upload Options - Choose one of the following options: • • 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.
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. B. Saving a Help File Update Profile 1. Click on the button. 2. The Save Help File Update Profile dialog box will be displayed. 3.
C. Loading a Help File Update Profile 1. Click on the 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. 5. Finally, click on the button. AlliedView-UM will load the specified Help File Update Operation profile. AlliedView™-UM 2.
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. D.
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. 13 Help File Update AlliedView™-UM 2.
14 Enable Feature Operations Device features can be enabled through the Enable Features Operation pane. To display this pane, click on the Selection pane. button on the Operations The Enable Features Operation is only applicable to devices that use AlliedWare™ and AlliedWare Plus™ management software. A. Creating an Enable Features Profile Software Selection 1. License List Filename - Specify the license list file to use for this operation.
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. B. Saving an Enable Feature Profile 1. Click on the button. 2.
C. Loading an Enable Features Profile 1. Click on the button. 2. A confirmation box will be displayed. Click to proceed. 3. The Load Enable Features Profile dialog box will be displayed. 4. Specify the filename of the profile to be loaded. 5. Finally, click on the Features Operation profile. AlliedView™-UM 2.0 USER’S GUIDE button.
NOTE: The Enable Features 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 Enable Features pane. A summary window will be displayed indicating which entries were successfully added. D.
3. Clicking the or the button will abort the Enable Features 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. 14 Enable Feature Operations AlliedView™-UM 2.
15 Reboot Device Devices can be rebooted through the Reboot Device Operation pane. To display this pane, click on the Selection pane. button on the Operations A. Creating a Reboot Device Profile Device Selection Device Selection is similar to that of the Release Upgrade Operation pane. B. Saving a Reboot Device Profile 1. Click on the AlliedView™-UM 2.0 USER’S GUIDE button.
2. The Save Reboot Device Profile dialog box will be displayed. 3. Specify the filename. 4. Finally, click on the button. C. Loading a Reboot Device Profile 1. Click on the button. 2. A confirmation box will be displayed. Click AlliedView™-UM 2.0 USER’S GUIDE to proceed.
3. The Load Reboot Device Profile dialog box will be displayed. 4. Specify the filename of the profile to be loaded. button. AlliedView-UM will load the specified 5. Finally, click on the Reboot Device profile. NOTE: The Reboot Device 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.
2. A progress window will be displayed, indicating the overall status of the operation. When the Reboot Device 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 Reboot Device 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”.
16 Audit Trail Each device definition has an audit trail that contains a chronological record of the operations that were performed on it. A. Viewing the Audit Trail To view a device’s audit trail, right-click on a device definition from the Device Families Pane. Select “View Device Audit Trail” from the context menu to display the Device Audit Trail dialog box for that device. Audit Record Each entry in the audit trail is called an Audit Record. An audit record contains the following information: 1.
• • • • • • • • • • • • Release Upgrade (AlliedWare) Release Upgrade (AlliedWare+) Release Upgrade (Other) Patch Upgrade Interim/Maintenance Release Upgrade Configuration File Update Execute Script File GUI Resource File Update Help File Update Enable Features Reboot Device Rollback 3. Operation Properties – These are the parameters that were used for the operation. 4. Result – This is the result of the operation for that device.
17 Schedule Operation Operations can be executed at a specified time using the Operation Scheduling function. A. How to Schedule an Operation To schedule an operation, you must first define an operation profile using the methods discussed in the previous sections of this document. Once you have created your profile, click on the the Schedule Task dialog box. button. This will display On the Task Name field, enter a name for the operation to be scheduled.
B. Viewing Tasks You may view the list of scheduled operations using the View Tasks dialog box. Click on Tools->View Tasks to display the dialog box. Task Each task contains the following information: 1. Task Name – This is the name that was entered in the Task Name field of the Schedule Task dialog box. 2. Operation – This is the operation that will be performed.
• • • • GUI Resource File Update Help File Update Enable Features Reboot Device 3. Operation Properties – These are the parameters that will be used for the operation. 4. Time of Execution – This is the date and time when the task will be started. 5. Status – This is the status of the task. It can be any of the following: • • • • Pending – The task is waiting to be executed. Done – The task has already been executed. Aborted – The user has aborted the task.
2. Click on the button to display the Edit Task dialog. 3. On the Edit Task dialog, there are two ways to modify the task: • Change the execution date and time – You may specify a new date and time for the operation to be executed. After specifying a new date and time, the entry of the scheduled operation will be updated in the task list. • Start Now – Click on the immediately. button to start the operation D. Aborting a Task A task that has a “Pending” status can be aborted.
1. To abort a task, select the task from the task list. 2. After making the selection, click on the 3. A confirmation box will be displayed. Click on AlliedView™-UM 2.0 USER’S GUIDE button. to abort the task.
E. Deleting a Task A task can be removed from the task list. 1. To delete a task, select the task to be removed from the task list. 2. After selecting the task to be deleted, click on the 3. A confirmation box will be displayed. Click on button. to delete the task. 17 Schedule Operations AlliedView™-UM 2.
18 Rollback A. Rollbacks and the Audit Trail Rollbacks are based on the contents of a device’s audit trail. A rollback of an operation can only be performed if the device’s audit trail contains a record of an operation that can be used as a reference to rollback to.
B. Special Rules on Rollbacks If the last entry in the Audit Trail is a Reboot Device operation or an Execute Script File operation, then AlliedView-UM will locate the most recent non-Reboot Device operation entry in the Audit Trail. That entry will be the one to be rolled back.
2. If it is possible to perform a rollback operation, the Device Rollback dialog box will appear. This dialog box will show the following information: • • • Operation – This is the operation that will be rolled back. Current Properties – These are the properties of the operation that will be rolled back. Target Properties – These are the properties of the operation that will be performed for the rollback operation. 3. Click the button to perform the rollback. 4.
D. Performing a Rollback on an Operation Profile It is possible to perform a rollback of the last Operation Profile that was executed. When this is done, a rollback operation will be performed on the devices that were included in the Operation Profile. Please refer to the Performing a Rollback on a Device section. If the last operation performed is a Reboot Operation Profile, Rollback Last Operation Profile or Execute Script File Profile then this type of rollback cannot be performed. 1.
2. This will display the Rollback Last Operation Profile dialog box. This dialog box will display the following information: • • • • • Operation – This is the operation that will be rolled back. Operation Properties – These are the properties of the operation that will be rolled back. Date & Time – This is the date and time when the operation profile was executed. Device – This is the IP Address of the devices that were included in the operation profile.
3. Click the button to perform the rollback operation. 4. When the rollback operation is complete, a summary window will be displayed. It will show the results of the rollback operation for each of the devices. For more details on the results of the Rollback operation, you may view the Operation Logs pane. 18 Rollback AlliedView™-UM 2.
19 License Registration AlliedView-UM application will run in demo mode if a license key has not yet been registered or if a duplicate license key has been detected. A duplicate license is detected if the number of computers currently running AlliedView-UM that are registered with the same license key exceeds the maximum allowed by that license key. There is no expiration period for the demo mode version. To get the full functionality of AlliedView-UM 2.
1. Select the Help->License Registration option from the main menu to display the License Registration window. 2. Click on the button to display the Input License window. 3. Enter the License Key and the Company Name printed on the Software Feature Registration Form or Software Certificate provided to you by an Allied Telesis sales representative and click the button. 4. The License Registration window will now display your registered license.
B. Modifying a License Method 1: 1. On the License Registration window, click on the button. 2. The Modify Lecense window will be displayed. After modifying the License Key and button. the Company Name, click on the 3. The License Registration window will now display your modified License Key and Company Name. You can close this window by clicking on the AlliedView™-UM 2.0 USER’S GUIDE button.
Method 2: 1. On the License Refistration window, double-click on the License window. to display the Modify 2. After modifying the License Key and the Company Name, click on the button. 3. The License Registration window will now display your modified License Key and Company Name. You can close this window by clicking on the button. 19 License Registration AlliedView™-UM 2.
20 Options The Options menu provides functions for customizing the appearance and behavior of the application. A. View Settings The general appearance of the Device Family tree can be modified via the View Settings. By default, the Device Family Tree only displays the IP Addresses of the device definitions. By selecting the Options->Show System Name option, the Device Family Tree will also display the System Names of the device definitions in addition to the IP Addresses.
B. Thread Settings This dialog box allows you to fine tune the performance and resource usage of AlliedView-UM. The No. of Threads field controls the number of active device connections that AlliedView-UM will try to establish during an Operation Profile and Import/Update Operation execution. For instance, if this value is set to 10 then AlliedView-UM will limit the active connections to only 10 sessions. This allows AlliedView-UM to effectively run on environments with low network bandwidth. The No.
© 1998-2009 Allied Telesis K. K. All rights reserved. No part of this publication may be reproduced without prior written permission from Allied Telesis, K. K. Microsoft is a registered trademark of Microsoft Corporation. Netscape Navigator is a registered trademark of Netscape Communications Corporation. All other product names, company names, logos or other designations mentioned herein are trademarks or registered trademarks of their respective owners. Allied Telesis K. K.
