3COM LOGO
3C015

Waking Up the Tivoli Management Agent

12/08/98

These instructions apply to the patch that updates the Tivoli Management Agent (TMA) that is installed as part of DynamicAccess software v1.5.x.  If you plan to use the TMA, please download the patch from the following 3Com web site:

www.3com.com/dynamicaccess/hotfixes

This patch assumes you are using the TMA installed as part of DynamicAccess software v1.5.  If you have installed the TMA from another source, your TMA installation will not be overwritten and you should ignore this patch.

This hotfix is the first update since the initial release of the Tivoli Management Agent (TMA, also called the endpoint) from Tivoli Systems, Inc. This update includes a fix for the setup process and clearer, more detailed instructions. Please be sure to review the README.TXT file included in the hotfix for information about when to run the TMA hotfix file. Once you have correctly installed the software, follow the instructions below to wake up the endpoint agent.

Tivoli Management Agent Basics

When you install the DynamicAccess software, the TMA (Tivoli Endpoint v3.2) is copied to the end node PC.  The files for the endpoint agent include the Lightweight Client Framework (LCF) executable and the required libraries.

A DynamicAccess software management product will be available in the future to take advantage of the TMA agent.  If you are using a Tivoli Management Environment (TME) 10 at your site, you already have a gateway used by the TME. You need to know the IP address of the gateway for your end nodes, as well as the port number on which the gateway is listening.  As system administrator, you can ensure that the endpoints log into the gateway so they can "join" the enterprise.

 You cannot wake up an endpoint unless the TCP/IP protocol is enabled on that PC.

The TMA runs when you run the LCFD.EXE file located in the TMA installation directory.  LCFD.EXE must be run each time the end node is started.  Although it stays in memory, it consumes very little memory or CPU cycles when it is not in use.  You can configure your end nodes to run LCFD.EXE automatically; instructions on how to do this vary between Windows 95/98 and Windows NT, as described in the sections below. 

Commonly Used Options

To run correctly, the TMA (the LCFD.EXE file) needs to have certain parameters or options specified. These options are explained in the following sections. 

 All of the options are case-sensitive. Options may appear in any order.

Specifying a Working Directory with the -C Option

The -C option specifies the working directory the TMA endpoint will use while running.   This is the \Tivoli\lcf\dat\1 directory on the drive on which the Tivoli endpoint was installed.  For most users, this drive is the C: drive.  An example command line to start the endpoint with the -C option is:

lcfd.exe -Cc:\tivoli\lcf\dat\1

Determining the Gateway Location with the -Dlcs.login_interfaces Option

By default, the endpoint issues a broadcast to UDP port 9494 to determine the location of a gateway.  If your gateway is located on a different subnet than the end node, or if the gateway does not listen on the default port of 9494, you can use the -Dlcs.login_interfaces option to specify the IP address and/or port number of the gateway.  The format for this option is:

-Dlcs.login_interfaces=<gateway IP address>+<gateway port number>

For example, to start the endpoint so that it logs into the gateway located at IP address 10.20.30.40, listening on port 5050, type:

lcfd.exe -Dlcs.login_interfaces=10.20.30.40+5050

Modifying the TMA Port with the -p Option

By default, the endpoint listens on port 9494 when it starts.  If you wish the endpoint to use a different port number, you can specify a different port number through the use of the -p option.  An example command line to start the endpoint listening on port 5050 is:

lcfd.exe -p5050

Displaying Additional Options

Normally, the above three options are the only options you will need.  If you have special needs that are not covered by these three options, you can access the list of available options by typing:

lcfd.exe -s -D?

End Node Operating System Considerations

Starting the TMA at Boot up on a Windows 95 or Windows 98 End Node

To start the endpoint on a Windows 95 or Windows 98 end node upon boot up, you need to add a registry entry to the RunServices key in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CurrentVersion in the system registry.  The entry can be given any name, for example "lcfd," and its value is the command line to be run. 

For example, to run the endpoint specifying the working directory to be c:\tivoli\lcf\dat\1 and listening on port 5050, create a value named "lcfd" in the RunServices key with "c:\tivoli\lcf\bin\win95\mrt\lcfd.exe -Cc:\tivoli\lcf\dat\1 -p5050" as its value.

To specify this entry automatically for all your end nodes, you may consider running this procedure from a login script.  See the sample batch file WAKEUP.BAT in the Putting It All Together section below for an example.

Starting the TMA at Boot up on a Windows NT End Node

To start the endpoint on an NT end node upon boot up, run the LCFD.EXE file with the additional option, -i.  The -i option tells LCFD.EXE to identify itself as a Windows NT Service, which causes the TMA to be started automatically when the system starts.  Any additional options you give to LCFD.EXE will also be used when the service is started.  For example, to run the endpoint specifying the working directory to be c:\tivoli\lcf\dat\1 and listening on port 5050, enter:

c:\tivoli\lcf\bin\w32-ix86\mrt\lcfd.exe -i -Cc:\tivoli\lcf\dat\1 -p5050

You may customize this command and put it in login scripts so that your Windows NT end nodes will all have the TMA enabled.  See the sample batch file WAKEUP.BAT in the Putting It All Together section below for an example.

Putting It All Together

In this section, we provide the sample batch file, WAKEUP.BAT, which will enable the TMA endpoint on Windows 9x and Windows NT workstations from a login script.   The batch file is commented so that you may customize it for your own use.

@echo off

REM This batch file is intended to "wake up" the TMA on Windows 95/98 and
REM Windows NT end nodes.
REM It will pass any command-line parameters as parameters to LCFD.EXE.
REM It adds the -C option to the command-line parameters. It does not
REM check to see whether that option was already present.

REM Silently abort if not running Windows
if "%windir%" == "" goto end

if "%OS%" == "Windows_NT" goto NT
REM Assuming running Windows 95/98; this may be a bad assumption!
REM Attempt to determine Windows drive.  Sets SystemDrive environment variable,
REM which may cause "out of environment" errors.
cd %TEMP%
dir %windir% /ad > .\hack.bat
echo @echo off > .\volume.bat
echo set SystemDrive=%%3%%:>> .\volume.bat
call .\hack.bat
del .\hack.bat
del .\volume.bat

if not exist %SystemDrive%\Tivoli\lcf\bin\win95\mrt\lcfd.exe goto alert
if not exist %windir%\regedit.exe goto alert

REM Start the TMA first
%SystemDrive%\Tivoli\lcf\bin\win95\mrt\lcfd.exe -C%SystemDrive%\Tivoli\lcf\dat\1\ %1 %2 %3 %4 %5 %6 %7 %8 %9

REM Now make sure it'll start at every boot
echo REGEDIT4 > .\lcfini.reg
echo. >> .\lcfini.reg
echo [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\RunServices] >> .\lcfini.reg
echo "lcfd"="%SystemDrive%\\Tivoli\\lcf\\bin\\win95\\mrt\\lcfd.exe -C%SystemDrive%\\Tivoli\\lcf\\dat\\1 %1 %2 %3 %4 %5 %6 %7 %8 %9" >> .\lcfini.reg
echo. >> .\lcfini.reg

%windir%\regedit.exe /s .\lcfini.reg
REM Note that this script doesn't delete the temporary registry file it created.
REM This is because the command interpreter can't be trusted to run regedit
REM synchronously, even if ERRORLEVEL is checked, in every version of Windows 9x.

goto end

:NT
if not exist %SystemDrive%\Tivoli\lcf\bin\w32-ix86\mrt\lcfd.exe goto alert

set LCFOPTS=%1 %2 %3 %4 %5 %6 %7 %8 %9
set LCFDIR=%SystemDrive%\Tivoli\lcf

REM Start the TMA and install it as a service
%LCFDIR%\bin\w32-ix86\mrt\lcfd.exe -i -C%LCFDIR%\dat\1 %LCFOPTS%

set LCFOPTS=
set LCFDIR=

goto end

:alert
echo Could not find the files needed to start the Tivoli TMA.
echo Please contact your System Administrator.
goto end

:end

Stopping the Tivoli Management Agent

If you no longer wish to run the Tivoli Management Agent, you may stop it by typing:

lcfd.exe -r lcfd

This command sequence stops the agent.  In Windows NT, it also removes the Windows NT Service for the agent so that the agent is not restarted upon rebooting the end node PC.  To prevent the agent from being restarted in Windows 95 or Windows 98, remove the registry entry in the RunServices key which starts it.  (See the instructions for starting the agent at bootup in Windows 95 or 98.)


Copyright ©1998, 3Com Corporation.  All rights reserved.
Unless otherwise indicated, 3Com registered trademarks are registered in the United States and may or may not be registered in other countries. 3Com, and DynamicAccess are registered trademarks of 3Com Corporation. Tivoli and TME 10 are registered trademarks of Tivoli Systems, Inc.