October 2009

AlliedView-UM v2.0 SP2


This file contains important information about AlliedView-UM SP2.  The topics
discussed in this file are summarized in the Contents section.


Contents
========

   A. Resolved Issues
   B. Service Pack Installation


A. Resolved Issues
==================

AlliedView-UM 2.0 SP2 resolves the following issues:

1. AlliedView-UM 2.0 SP2 resolves an issue relating to the feature licenses generation
   for AlliedWare and AlliedWare Plus devices. AlliedView-UM could not generate 
   feature licences if the license key or the feature name contains special characters.
   (JIRA Key: ATPE-143)
   
2. AlliedView-UM 2.0 SP2 resolves an issue relating to the device detection routines 
   for AlliedWare devices. AlliedWare devices could not be added or detected if 
   the configuration filename being used has an extension of ".scp".
   (JIRA Key: ATPE-149)

AlliedView-UM 2.0 SP2 now supports 64-bit feature license for AlliedWare
Plus devices.

AlliedView-UM 2.0 SP2 also includes the fixes to AlliedView-UM 2.0 SP1.
There is no need to apply AlliedView-UM 2.0 SP1 prior to applying
AlliedView-UM 2.0 SP2.

B. Service Pack Installation
============================

AlliedView-UM 2.0 must already be installed before an attempt is made to apply
the service pack.

Windows
-------
1. Make sure that you have administrator privileges and that AlliedView-UM 2.0
   is not running.
2. Using Windows Explorer, navigate to the folder where AlliedView-UM 2.0 is
   installed.  If you installed AlliedView-UM 2.0 using the default directory,
   the AlliedView-UM folder will be located in C:\Program Files\Allied Telesis.
3. From the AlliedView-UM folder, go to the \lib folder.
4. Disable the "Read-only" attribute of the "atum.jar" file.
      * Right click on the "atum.jar" file and select "Properties".
      * Uncheck the "Read-only" attribute.
      * Click on the "OK" button.
5. Run AVUM202.exe by double clicking the file.
6. Extract the file from the archive to the \lib folder.  This will replace the
   current "atum.jar" file with the new one.


Solaris 
-------
1. Make sure that you have administrator privileges and that AlliedView-UM 2.0
   is not running.
2. Using a terminal window, navigate to the folder where AlliedView-UM 2.0 is
   installed.  If you installed AlliedView-UM 2.0 using the default directory,
   the AlliedView-UM folder will be located in /opt/AlliedTelesis.
3. From the AlliedView-UM folder, go to the /lib folder.
4. Copy the AVUM202S.tar file into this folder.
5. Extract the file from the archive using the tar command:
   
        tar -xvf AVUM202S.tar
        
   This will replace the current "atum.jar" file with the new one.


HP-UX
-----
1. Make sure that you have administrator privileges and that AlliedView-UM 2.0
   is not running.
2. Using a terminal window, navigate to the folder where AlliedView-UM 2.0 is
   installed.  If you installed AlliedView-UM 2.0 using the default directory,
   the AlliedView-UM folder will be located in /opt/AlliedTelesis.
3. From the AlliedView-UM folder, go to the /lib folder.
4. Copy the AVUM202H.tar file into this folder.
5. Extract the file from the archive using the tar command:
   
        tar -xvf AVUM202H.tar
        
   This will replace the current "atum.jar" file with the new one.

--------------------------------------------------------------------------------
Copyright (C) 2009 by Allied Telesis K.K. 
All rights reserved.

PN 613-001076 Rev C