November 1999 UserTracker 1.0b2 Release Note   UserTracker is a monitoring and diagnostic application for Lucent PortMaster® products based on the Sun Microsystems Java Virtual Machine 1.1.6. UserTracker uses usernames (user IDs) and telephone numbers (caller IDs) to monitor the Point-to-Point Protocol (PPP) negotiation of particular users and determine where a user is logged in when you are monitoring multiple PortMaster products.   Version 1.0b2 of UserTracker is available for open beta to any Lucent customer at no charge. This beta version of UserTracker works best with the following ComOS® versions and provides equivalent functions:  ComOS 4.1  ComOS 3.9 (in beta)  ComOS 3.8.2   If you are running an older version of ComOS, UserTracker will not function as intended. The UserTracker is being release on an unsupported basis. Please direct all comments and questions to: usertracker-feedback@livingston.com.          Contents  Main Functions  Bugs Fixed  Limitations  System Requirements  Installation  Deinstallation  Running UserTracker  Command Line Options  Debug Log  Contacting Lucent Remote Access Technical Support          Main Functions   The UserTracker panel has two main sections. The top section displays the PortMaster product(s) you are connected to---the Portmaster model, its ComOS version, the time elapsed since its last reboot, and the amount of time you have been connected to it via UserTracker. In this section, you can also select a particular PortMaster 4 slot (board) on which to track users and telephone numbers.   The bottom section is divided into four displays:  The two narrow displays on the left show the user IDs and caller IDs you entered into UserTracker and whose negotiation process you want to track.  The wider displays on the right show what UserTracker finds---the debug messages generated during PPP negotiations for these user IDs and caller IDs and details about these messages. Each line contains a UserTracker message that contains the following information:   ¯ User ID or caller ID that was found   ¯ Hostname of the PortMaster that the ID was found on   ¯ Number of the PortMaster 4 slot (if applicable) that the ID was found on   ¯ Port (if applicable) that the ID was found on   ¯ Modem (if applicable) that the ID was found on   ¯ Time that the ID was found   ¯ Current state of the ID          Bugs Fixed   The following bug is fixed in UserTracker 1.0b2:   The caller ID monitoring function now works properly, rather than displaying all caller IDs you now see only the ones that you have selected.          Limitations   UserTracker 1.0b2 has the following limitations:  When another user telnets into the same PortMaster that UserTracker is monitoring and changes the debug flags or turns debugging off, the UserTracker is affected. You must reconnect UserTracker to the PortMaster on which the debug flags were modified.  When monitoring a PortMaster 4 the current version can only monitor a single board.  The Caller ID monitoring will only work with PRI lines. This feature will not work w/ CT1 or CE1 lines.  The UserTracker will stop working when attempting to monitor over 40 PortMaster 3's.          System Requirements   UserTracker is a Java-based product that runs on any system with Java Development Kit (JDK) or Java Runtime Environment (JRE) version 1.1.6 or later installed. Nondevelopers can use the JRE rather than the JDK.   Currently, JDK 1.1 and JRE 1.1 are available for the following and other platforms at http://www.javasoft.com/products/jdk/1.1/:  Windows NT 4.0  Windows 95  Solaris 2.5.1  Solaris x86 2.5.1  Linux 2.x  FreeBSD  SGI IRIX 6.3  HP-UX 10.02  Alpha Digital UNIX 4.0  IBM AIX 4.1  Macintosh          Installation   To install UserTracker, follow these 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 usertracker10b2_solaris.tar    ¯ For other UNIX systems, enter get  usertracker10b2_unix.tar    ¯ For Windows, enter get usertracker10b2.zip    ¯ For Macintosh, enter get usertracker10b2.sit quit    2. For UNIX systems only, define the path for jre/bin in your .cshrc  file. For example, if you install the JRE in the /usr/local/lib  directory, your .cshrc  file must have the following entry:   set path=(/usr/local/lib/jre/bin $path)   If the JDK has been installed, then change the usertracker script to use the java  command instead of jre .   3. Run the installation.   ¯ For Solaris, enter the following commands on the command line: tar xvf usertracker10b2_solaris.tar ./usertracker_solaris_install   ¯ For other UNIX systems, enter the following commands on the command line (replacing /usr/local  with your desired path): mkdir /usr/local/lucent mkdir /usr/local/lucent/usertracker cp usertracker10b2_unix.tar /usr/local/lucent/usertracker cd /usr/local/lucent/usertracker tar xvf usertracker10b2_unix.tar   ¯ For Windows, unzip the usertracker10b2.zip file, run the usertracker_install.exe  program, and follow its instructions.   ¯ For Macintosh, unstuff the usertracker10b2.sit file, run the usertracker_install  program, and follow its instructions.   4. If you are using a ChoiceNet server, increase to at least 2 and preferably 10 the maximum number of connections allowed into the PortMaster through TCP port 1643. UserTracker uses this port for communication. If only one port is available, ChoiceNet cannot send filters to the PortMaster. To increase the number of connections allowed through this port, log in to your PortMaster through the console or a telnet session and type the following commands: set maximum pmconsole 10 save all          Deinstallation  On a Solaris, Windows, or Macintosh system, an application called Uninstall_UserTracker is placed in the lucent/usertracker or Lucent/UserTracker directory. Run this application to remove UserTracker from your system.  On Solaris, if the local jre directory still exists after you run Uninstall_UserTracker, remove the directory with the command "rm -rf jre".  On other UNIX systems, remove the shell script and jar files to remove UserTracker from your system.          Running UserTracker  On a Windows system, select the UserTracker icon from the Lucent folder in your Start -> Programs menu.  On UNIX systems (including Solaris), you can run UserTracker by typing "usertracker" when you are in the usertracker installation directory. If you have added the usertracker installation directory to your PATH, you can run it from anywhere.          Command Line Options   When running UserTracker, you can use the following command line options   -h <Hostname>   -u <Username>   -p <Password>   -users  <Comma-separated list of user IDs>   Use the -h, -u, and -p options together to force UserTracker to log in to the specified device at startup. For example:   usertracker  -h Hostname  -u "\!root" -p Password    If only -h is specified, the Connect  dialog box is displayed with the hostname filled in.   Use the -users  option to track users when UserTracker starts to run.   For example:   usertracker -h < Hostname> -u "\!root" -p < Password> -users bob, eva, pyda           Debug Log   When running UserTracker, you can use the following debug options on the command line:   -g  <Debug level>   -l  (specifies the local directory)     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 output than you can possibly stand   The -l  option sends all debug output to the directory UserTracker is installed in. By default, all debug output is sent to the Lucent/UserTracker  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\UserTracker c:\users\<username>\Lucent\UserTracker c:\windows\Lucent\UserTracker   If you still cannot find the directory that contains debug output, select Find->File and search for debuglog.txt.          Contacting Lucent Remote Access Technical Support   Please do not contact the Lucent Technologies technical support via voice, fax, or electronic mail. All questions and comments should be directed to usertracker-feedback@livingston.com . Please mention in the email that you are running UserTracker 1.0b2, and include the version of JDK or JRE that you are running, the operating system version ("uname -a" output), and the version of ComOS running on the PortMaster.   The "About UserTracker..." menu item in the Help menu displays the version of UserTracker you are running including the build date, debug level, and location of runtime debug files.