1998/09/23

			PMVision 1.3b3 Open Beta Release Note

PMVision(TM) is a configuration and monitoring application for Lucent
PortMaster(R) products based on Sun Microsystem's Java Virtual Machine
version 1.1.4.  Version 1.3b3 of PMVision is available for open beta to
any Lucent customer at no charge.

To use the full capabilities of this beta product, you must have
ComOS(R) 4.0b10 (in closed beta for the PortMaster 4).  PMVision 1.3b3
also works with ComOS 3.7.2c3 and ComOS 3.8b21 on the PortMaster 3, and
with the current releases on other platforms, although not all PMVision
functions are available on older releases.


	  	CONTENTS

Introduction
Contents
Main Functions
New Features
Limitations
System Requirements
Installation
Running PMVision
Debug Log
Technical Support


		MAIN FUNCTIONS

PMVision was designed to do the following:

o  Be portable across operating systems 

o  Manage multiple PortMaster products simultaneously   

o  Extend to allow Wizards and Smart Agents to manage PortMaster
   products

PMVision provides a single document interface (SDI) panel. A control
tree appears on the left, a list of currently open PortMaster products
-- including selection information -- appears at the top center, and
the main function window is in the center.

To access a PortMaster, you select the Connect option from the
PortMaster pull-down menu, or select PortMaster in the control tree.
PMVision allows you to connect to a PortMaster using the default !root
login, or to use RADIUS authenticated administrative logins if the
PortMaster is appropriately configured.  If RADIUS authenticated
administrative logins are used, the password for these logins is
currently sent over the connection in cleartext.

A RADIUS NAS-Prompt-User has limited command rights.  A RADIUS
Administrative-User is equivalent to the !root administrative login.
PMVision treats the RADIUS NAS-Prompt-User administrative user the same
as the RADIUS Administrative-User until ComOS denies access to a
function.  For example, a NAS-Prompt-User level user can use PMVision
to create a user or location record, but creation of that record is
denied when the command is sent to the PortMaster.

You access PMVision functions by clicking them in the menu tree.
PMVision provides the following main functions:

o  Monitoring (requires ComOS 3.8 or later)
o  Graphing (requires ComOS 4.0 or later)
o  Maintenance -- Install/Upgrade and Backup/Restore
o  Debug
o  Configuration


	MONITOR

PMVision provides extensive monitoring capabilities, including the
ability to monitor diagnostic commands.

The Monitor tree item allows you to monitor the chassis, modems,
sessions, lines, and interfaces. You can reset counters in PMVision
only -- not on the PortMaster.  The counters revert to actual values
when you move to another display.

o  Chassis shows power use, fan status, and temperature for each board
   on a PortMaster 4. This feature works only with ComOS 4.0b10 or later.
o  Modem Summary shows the number of modems in each state on a
   PortMaster 4.
o  Modem Details shows the state of modems either for an entire
   PortMaster 3 chassis or for a single PortMaster 4 QuadT1 or TriE1 board.
o  Session Summary shows the number of connections for various
   connection speeds on a PortMaster 4.
o  Session Details shows active sessions either for an entire
   PortMaster 3 chassis or for a single PortMaster 4 QuadT1 or TriE1 board.
o  Lines shows the state of lines for an entire chassis.
o  Interfaces shows active interfaces either for an entire PortMaster 3
   chassis or for a single PortMaster 4 QuadT1 or TriE1 board.


	GRAPH

The Graph tree item allows you to view and log the history of modem and
session summaries.  You can specify the log interval, log file, and
colors for each item in the display.  The colors are saved to a
preferences file.  This feature is currently available only on the
PortMaster 4 running ComOS 4.0b9 or later.

o  Modems shows the Modem Summary information over time.

o  Sessions shows the Session Summary information over time.


	DIAGNOSE

Debug allows you to select a variety of debug information to be
displayed.


	MAINTAIN

Upgrade allows you to upgrade with a ComOS upgrade file.

Back Up allows you to save certain parts of your configuration to a
file. This configuration is saved in ASCII file format.  Restore allows
you to restore a previously saved configuration file.  When doing a
restore, PMVision is not just performing an erase and restore
operation.  Instead, the configuration file overwrites the specific
configuration information that is being restored from the file.

NOTE: Any items that are not overwritten by restore are left unchanged.

WARNING: Backing up the user table fails to recover the individual user
passwords. For this reason, restoring a user table from a PMVision
backup produces null passwords in the user table.  If a user entry has
a null password, the PortMaster does not prompt the user for a password
at login.  As a result, the user might be unable to log in.  In
addition, an unauthorized user might gain access to the user account
because no password is required. After a backup and restore operation,
you must add user passwords through either PMVision or the command line
interface.

WARNING: The administrative (!root) password and RADIUS and ChoiceNet
secrets are not saved by the backup operation.  Unless you add the
administrative password and RADIUS and ChoiceNet secrets to the backup
file, they are not restored and the previous password and secrets
remain in effect.

PMVision does not read or restore binary backup files. However, you
can use Upgrade to send binary backup files created by pmreadconf to a 
PortMaster.

CAUTION:  The binary backup file format is heavily dependent on ComOS
version, and restoring a file saved from one version onto another is
not recommended.


	COMMAND

Command provides a command window for entering ComOS commands and
viewing command output.


	CONFIGURE

Configure allows you to enter, view, and update configuration
information for the PortMaster.

When controlling a PortMaster running a ComOS release earlier than 3.8,
PMVision does not provide configuration for SNMP, the host table, or
static routes.



		NEW FEATURES

Following is a list of the new features in PMVision 1.3b3:

o  A new monitoring option, Chassis, shows a summary of power use, fan
   status, and temperature for a PortMaster 4. Power is shown both as
   an overall demand for the chassis and on a per board basis.
   Temperature is shown on a per board basis.

o  The monitor legend has been removed from the main Monitor panel and
   placed in a dialog accessible from the Legend button at the bottom
   of that panel.  The legend has been modified to be model specific
   with more detailed annotations.



		LIMITATIONS

Following is a list of the known limitations in PMVision 1.3b3:

o  The Interfaces monitoring option does not show the point-to-point
   interfaces on the PortMaster 4.

o  Debug through PMVision does not work with the PortMaster 4.

o  You cannot currently add DLCI entries to a QuadT1 or TriE1 board.

o  Configure Routes has been removed in this release.

o  Although hypertext links in the help system work under Sun's JRE
   1.1.4, they do not work under JRE 1.1.5. This bug is fixed in Sun's
   JRE 1.1.6.

o  The backup operation (Maintain --> Back Up) does not save the
   administrative password, RADIUS secret, ChoiceNet secret, user
   passwords, OSPF interface configuration, and BGP configuration.

o  Do not connect to more than five PortMaster 3 products unless you
   have more than 32MB of RAM in the computer running PMVision.

o  Monitor --> Modems shows different call and retrain counts than a
   "show modem" command done at the command line.

o  Modem information is not always displayed in the correct order.
   Click the column name to sort the column correctly.

o  During configuration, an invalid entry is changed to a valid value
   on some Configuration panels. In a future release of PMVision, an
   invalid input will be tagged so that you can change it to a valid
   value.

o  On the Diagnose --> Debug panel, the debug options do not always
   turn off correctly after you deselect them, and might continue to
   display debug information. Turn off all debug options to stop the
   display of all debug information.

o  Because ComOS has only one set of debug flags, changing the debug
   settings on the command line affects the debug messages displayed in
   the PMVision debug panel.

o  In Microsoft Windows, the "hourglass" cursor remains visible after
   PMVision completes an operation. Move the mouse to change the cursor.

o  The scroll bar might not work correctly if you have JDK or JRE
   version 1.1.3 or earlier.  Use JDK or JRE 1.1.4 or later.

o  When PMVision is run under Motif or OpenWindows the following text
   might appear but does not indicate any runtime problems in PMVision:

   Warning: 
       Name: scrollbar
       Class: XmScrollBar
       The scrollbar page increment is less than 1.

o  Occasionally, the initial overview screen might not be shown. Resize
   the window to display the screen.

o  If a PortMaster running a release older than ComOS 3.8 is sent
   unsupported commands, a Command Error dialog box is displayed. Click
   Done to dismiss the box and return PMVision to a normal state.



		SYSTEM REQUIREMENTS

PMVision is a Java based product that can run on any system with JDK or 
JRE (Java Runtime Environment) version 1.1.4 or later installed.
Nondevelopers can use JRE rather than JDK.  Currently, JDK 1.1
and JRE 1.1 are available for the following platforms.

o  Windows NT 4.0       http://www.javasoft.com/products/jdk/1.1/
o  Windows 95           http://www.javasoft.com/products/jdk/1.1/
o  Solaris 2.5.1        http://www.javasoft.com/products/jdk/1.1/
o  Solaris x86 2.5.1    http://www.javasoft.com/products/jdk/1.1/
o  Linux 2.x            ftp://lagrange.la.asu.edu/pub/Linux_jdk/
o  FreeBSD              http://www.freebsd.org/java/
o  SGI IRIX 6.3		http://www.sgi.com/Products/DevMagic/products/java.html
o  HP-UX 10.02          http://www.hp.com/esy/go/java.html
o  Alpha Digital Unix 4.0
http://www.digital.com/java/download/jdk_du/1.1.5/index.html
o  IBM AIX 4.1          http://www.ibm.com/java/tools/jdk.html
o  All other platforms  http://java.sun.com/cgi-bin/java-ports.cgi


		INSTALLATION

To install PMVision use the following steps:

1.  Download files from ftp.livingston.com as follows:
    ftp ftp.livingston.com
    (Enter "anonymous".)
    (Enter your email address; it will not echo.)
    binary
    cd pub/le/software/java
    - For Solaris, enter
    get pmvision13b3_solaris.tar
    - For other UNIX systems, enter
    get pmvision13b3_unix.tar
    - For Windows, enter
    get pmvision13b3.zip
    quit

2. For UNIX systems (including Solaris), define the path for
   jre1.1.4/bin in your .cshrc file.  For example:  If you install
   jre1.1.4 in the /usr/local/lib directory, your .cshrc file should
   have the following entry:

   set path=( /usr/local/lib/jre1.1.4/bin $path )

3. For Windows NT 4.0 and Windows 95, installing JRE or JDK 1.1.5 sets the
   correct values for PATH and CLASSPATH.

  - For JRE or JDK 1.1.4 on Windows 95, edit c:\autoexec.bat and add
  path=%PATH%;<<JAVADIR>\bin

  Replace <<JAVADIR> with the location where the Java runtime
  environment was installed.  Note that if the JDK is installed instead
  of the JRE, the scripts need to be edited.

  - For Windows NT 4.0, define the path for jre1.1.4 in the System
  Environment as follows:

  a. Open the Control Panel.
  b. Click the System icon.
  c. Click the Environment.
  d. On the display window, highlight and click the line with the
     word Path.
  e. Enter the installation path of the JDK or JRE on the Value window. 
  f. Click the Set button. 

  Typically, the JDK or JRE is installed on C:\jdk1.1.4 or
  C:\jre1.1.4.  In this case, the correct path for JDK and JRE is
  C:\jdk1.1.4\bin or C:\jre1.1.4\bin.

4. Run the installation.

  - Previous PMVision users must enter the following command on the
  command line, in the directory where they previously installed
  pmvision.jar.gz:

  gunzip pmvision.jar.gz

  Then replace the old pmvision.jar file in your installation directory
  with the newer unzipped jar file after extracting it from the tar file.

  If you do not have gunzip, it is available as part of the Free Software
  Foundation's gzip package at ftp://ftp.gnu.org/pub/gnu/.

  - For Solaris users, enter the following commands on the command line:

  tar xvf pmvision13b3_solaris.tar
  ./pmvision_install.bin

  - For other UNIX users, enter the following commands on the command line:

  tar xvf pmvision13b3_unix.tar
  jre -cp pmvision_install.zip install

  - For Windows users, unzip the pmvision13b2.zip file, run the
  pmvision_install.exe program, and follow its instructions.

- For other systems, untar the pmvision13b3_unix.tar file and move the 
  pmvision.jar file into the appropriate directory to be used with Java.



		RUNNING PMVision

- On a Windows NT system,  select the PMVision icon from the Lucent
folder in your Start, Programs menu.

- On UNIX systems (including Solaris), you can run PMVision by typing
"pmvision" when you are in the pmvision installation directory.  If you
have added the pmvision installation directory to your PATH, you can
run it from anywhere.



		DEBUG LOG

When running PMVision, you can use the following options:

-h <<Hostname>
-u <<Username>
-p <<Password>
-g <<Debug level>
-l (specifies the local directory)

Use -h, -u, -p options together to force PMVision to log in to the
specified PortMaster at startup. For example:

pmvision -h xxxxxx -u \!root -p xxxxx

If only -h is specified, the Connect dialog box is displayed with the
hostname filled in.

The -g <<Debug level> option specifies the debug level.  Valid debug
level values are the following:

 0 - NONE - No debug output
10 - FATAL_ERRORS - Debug output for fatal errors only
20 - ALL_ERRORS - Debug output for all errors (the default)
30 - DEBUG - Useful debug information
40 - VERBOSE - More debug than you can possibly stand

The -l option sends all debug output to the directory PMVision is
installed in.  By default, all debug output is sent to the
Lucent\PMVision directory created in your home directory. On UNIX
machines, the default works properly.  However the concept of a home
directory is not so clear on PCs and seems to differ for each vendor's
Virtual Machine. Try looking for one of the following:

c:\java\Lucent\PMVision
c:\users\<<username>\Lucent\PMVision
c:\windows\Lucent\PMVision

If you still cannot find the directory that contains debug output, do a
Find, File for debuglog.txt.

Send your questions, comments, and suggestions regarding this beta
software to support@livingston.com. Mention that you are running
PMVision 1.3b3, and include the version of JDK or JRE that you are
running, the operating system version ("uname -a" output), and the
version of ComOS on the PortMaster.

The "About PMVision..." menu item in the Help menu displays the version
of PMVision you are running including the build date, debug level, and
location of runtime debug files.

__________________________________________________________________________

		Copyright and Trademarks

Copyright 1998 Lucent Technologies, Inc.  All rights reserved.
PortMaster, ComOS, and ChoiceNet are registered trademarks of Lucent
Technologies, Inc. RADIUS ABM, PMVision, PMconsole, and IRX are
trademarks of Lucent Technologies, Inc. ProVision is a service mark of
Lucent Technologies, Inc. All other marks are the property of their
respective owners.

		Notices

Lucent Technologies, Inc. makes no representations or warranties with
respect to the contents or use of this publication, and specifically
disclaims any express or implied warranties of merchantability or
fitness for any particular purpose. Further, Lucent Technologies.,
Inc.  reserves the right to revise this publication and to make changes
to its content, any time, without obligation to notify any person or
entity of such revisions or changes.

		Contacting Technical Support

Lucent Technologies Remote Access Business Unit (previously Livingston
Enterprises) provides technical support via voice, fax, electronic
mail, or through the World Wide Web at http://www.livingston.com/.
Please specify that you are running PMVision 1.3b3 when reporting
problems with this release.

Internet service providers (ISPs) and other end users in Europe, the
Middle East, Africa, India, and Pakistan should contact their
authorized Lucent Remote Access sales channel partner for technical
support; see http://www.livingston.com/International/EMEA/distributors.html.

For North and South America and Asia Pacific customers, technical
support is available Monday through Friday from 7 a.m. to 5 p.m. U.S.
Pacific Time (GMT -8).  Dial 1-800-458-9966 within the United States
(including Alaska and Hawaii), Canada, and the Caribbean, or
1-925-737-2100 from elsewhere, for voice support. Otherwise, fax to
1-925-737-2110, or send email to support@livingston.com
(asia-support@livingston.com for Asia Pacific customers).

