Tivoli Endpoints

Goto the Tivoli Home Page
This page details problems and issues relating to Tivoli Endpoints.

Can I Stop the NT Endpoint Service from a Command Prompt?

Contributed By: Cliff Hobbs [MVP SMS]
Yes - use the 'net stop lcfd' command to stop the Endpoint service on a Windows NT/2000 Endpoint and the 'net start lcfd' command to start the service.
 

Can I Turn Off the Tivoli Splash Screen when My Users Login?

Contributed By: Cliff Hobbs [MVP SMS]
Yes you can by changing the value of the "lcfep" Registry key stored under  "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run" from:

C:\Tivoli\lcf\bin\w32-ix86\mrt\lcfep.exe

to:

C:\Tivoli\lcf\bin\w32-ix86\mrt\lcfep.exe -x

The "-x" option is an undocumented switch.

If you want to remove the ‘TME’ icon from the System Tray following the instructions in the How Can I Disable/ Turn Off the Tivoli ‘TME’ Icon in the System Tray? article.
 

"Cannot find the file 'C:\Program Files\Tivoli\swdis\1\wdusrprf.bat'" Message Displayed at Login

I'm seeing the following message on some of my NT Endpoints when users login:

Cannot find the file 'C:\Program Files\Tivoli\swdis\1\wdusrprf.bat'

Contributed By: Cliff Hobbs [MVP SMS] and Thierry Nieuviarts
 The "wdusrprf.bat" file is written on the machine the first time you perform a Software Distribution operation to it.  At the same time, the following entry is added to the "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run" Registry key:

SwdisUsrPrg.<machine_name>:REG_SZ:"C:\Program Files\Tivoli\swdis\1\wdusrprf.bat"

which is set to run the "wdusrprf.bat" batch file each time a user logs on the machine.

The "wdusrprf.bat" contains the following lines:

setlocal
set SWDIS_INI_SECTION=<machine_name>
set TISDIR=C:\Program Files\Tivoli\lcf\dat\1
set Path=%Path%;C:\Program Files\Tivoli\lcf\bin\w32-ix86\mrt;
"C:\Program Files\Tivoli\lcf\dat\1\cache\lib\w32-ix86\wdusrprf.exe"
endlocal

The last line of the batch file runs the "wdusrprf.exe" file which is the user profile update program (apparently this program needs to start at each login to check to see if there are any actions that need to be performed for each user that logs into the machine).

If you get the "Cannot find file..." message it means that the key exists in the Registry but the file no longer exists.  You should be able to copy it from another machine and change the "set SWDIS_INI_SECTION=<machine_name>" line accordingly to match the machine name.
 

Changing the NT Account the Endpoint Runs Under

I have an issue here where I install the Endpoint (rebooting if necessary), and make sure it logs into the Gateway. If I then change the NT account the Endpoint runs under from the default of 'Log on As: System Account' to an NT Domain Account then stop/start the Endpoint service it then never logs back into the Gateway again.

I'm assuming this is a timing issue in that I'm not giving the Endpoint sufficient time to finish installing before changing the account.

As a rule of thumb, how long do you guys typically allow for the Endpoint to finish installing? Is there a way of telling how far through the installation process has got by looking in a log file or checking for the existence of a file or directory like there is with SMS?

Is there anyway of using Tivoli to remotely change the account the Endpoint runs under (so rather than doing it from the Endpoint do it from the TMR Server)?

The reason we need to change the account is that we found that some of our packages don't install using the local account (the default the Endpoint is installed and runs under), yet they work fine using an account that is Domain Admin and also a member of the Tivoli_Admin_Privileges account. It is this change of account I'm trying to automate/ make easier.

Contributed By: Leon Adato and Paul Dunkley
 It is possible that the error your seeing is because you have changed the 'Log on as'.

There is not a command within Framework to change the 'log on as' (or at least there wasn't ). The Tivoli Agent runs as a System account, any methods run on the endpoint will run as TMERSVD (an unprivileged account) or where the method requires Privileged access the method will run as whatever is setup in WIDMAP (using WIDMAP you can change who the privileged user is).

To change the Privileged account the Framework uses you need to use WIDMAP. Using WIDMAP you can change the account to any Domain or local Account, the easy way is to create a Domain account and add it to both Domain Administrators and Domain Tivoli_Admin_Privileges.

The downside (depending on what applications you are using for example Distributed Monitoring (classic)), is that you will then experience a lot of logon/logoffs. Using WIDMAP if you specify an account that is just 'Account' as opposed to 'DOMAIN\Account' then the TAP will look for a local account first and the go to the Domain for that account.

Just to point out that if you specify a DOMAIN account, any version of Tivoli prior to 3.7.1 will ONLY AUTHENTICATE AGAINST THE PDC!!

I emphasize this because in larger environments you could see hundreds or thousands of Endpoints hitting the PDC across WAN links even though a BDC may be right in the same sight with them. This is true even if you are running Windows 2000 and using the 'AvoidPdcOnWan' functionality. Tivoli uses a lower-level TCP/IP function to find the PDC, not the Windows API.

I have read (but not tested) that this is resolved in 3.7.1.

So before you go specifying a domain account, be aware that it could mean an impact on your network and especially on your PDC activity.

To Change the Account an NT Endpoint runs under:

  1. Install the Endpoint and make sure it logs into the Gateway.
     
  2. On the Endpoint, stop the "Tivoli Endpoint" service from Control Panel or use the "net stop lcfd" command from a Command Line.
     
  3. Delete all of the files in the "C:\Program Files\Tivoli\lcf\dat\1" directory EXCEPT for the DLL files. Do not delete any other files or directories.
     
  4. Delete the Endpoint from the relevant Gateway in Tivoli.
     
  5. From "Control Panel | Services", click on the "Tivoli Endpoint" service and press the "Startup…" button.
     
  6. Click on the "This Account:" radio button in the "Log On As:" section of the "Service" screen.
     
  7. Either type the name of the account in the "This Account:" field in "Domainname\account" format or use the browse button (denoted by three dots (…)) next to the "This Account:" field.
     
  8. If you used the browse button in the above step double-click on the relevant account from the "Add User" box then click on the "OK" button.  If you see the following message press the "OK" button:

    The account <Domain_name>\<name_of_your_account> has been granted the Log On As a Service right.
     
  9. Click on the "OK" button to close the "Service" screen.
     
  10. Close Control Panel.

"Data was not received because the connection was reset by the peer." Error when Running "wadminep <ep_name> view_version"

Contributed By: Gary Hamilton and Cliff Hobbs [MVP SMS]
 If you’re seeing the above error when trying to run a command such as 'wadminep' or you’re finding that Software Distributions aren’t working then read on… [Go to the article]
 

Disabling Broadcasts on Endpoints

It seems the issue of Endpoint broadcasting seems more complicated the more Redbooks and Knowledgebase articles I try to read. I standardly install Endpoints without specifying the 'bcast_disable=1' option on the WINSTLCF command, and *do* specify a seed gateway for the Endpoint to use. Our select_gateway_policy then subsequently sets a primary gateway and one or more alternate gateways. If I do not retrospectively set 'bcast_disable=1' and leave the default of 'bcast_disable=0', am I risking my Endpoints migrating between TMRs in some circumstances ? and will setting this option prevent deleted Endpoints (without LCF.DAT) attempting another initial login if the LCFD process is inadvertently restarted?

Contributed By: Ken Wood
It depends on how your environment is setup. This should only be a possibility if there is a Gateway in your subnet for another TMR. If the Gateway(s) you want an Endpoint to log in to is not in its subnet, disable broadcast. Broadcast assumes one or more Gateways serve a subnet. If that is the case then an Endpoint can broadcast for initial login and if the Gateway(s) are unavailable.

This can ease disaster recovery for a Gateway. However, broadcasts can also produce network issues (especially in a dynamic environment).
 

Endpoint can't find Gateway

I've installed a new Windows 2000 Endpoint which is alive but after rebooting it fails. According to the 'LCFD.LOG' the Endpoint tries the last known Gateway and fails, then tries logging into a new Gateway but fails as well. The errors I'm seeing are:

Jan 15 22:02:47 1 lcfd gw login failure: i=2147483647 : ../../src/comm/netio.c:374 [cti_create_client or cti_timed_create_client] : loc=3, cls=2, dec=999, sys=10060, tli=0, evt=0

Jan 15 22:03:08 1 lcfd gw login failure: i=0 : ../../src/comm/netio.c:374 [cti_create_client or cti_timed_create_client] : loc=3, cls=2, dec=999, sys=10060, tli=0, evt=0

Contributed By: Gary Hamilton
Increase the debug level on the 'LCFD.LOG' to '3' so you can which IP address and port the Endpoint is trying to communicate on by using any of the following methods:

  • Change the value of the 'log_threshold=' line in the 'LAST.CFG' from '1' to '3'
  • Use the 'lcfd -d <level>' command e.g. 'lcfd -d 3'
  • Use 'wep set_config' - on later versions this is activated without having to restart the Endpoint. On previous versions, you have to restart the Endpoint to get the new debug level recognised.

In addition to changing the debug level on the Endpoint, you should also increase the debug level on the Gateway to '6', so you can see what the Gateway's response is to the Endpoint's login request.  To change the debug level on the Gateway use the 'wgateway <name> set_debug_level 6' command.

You might also want to check out the My Endpoints Won't Login to My Gateway article as well.
 

Endpoint Error "28" When Executing Tasks

Has anyone ever seen the following error during executing tasks:

=============================================
KT-sp1n08-ep (Endpoint): The task failed to execute.
KT-sp1n08-ep (Endpoint):
write(...) failed (errno = 28)
->
Debug Log:
Entering LogInitAppend
Entering mrt_run
argv: session_id=210c8545
Communication timeout set: 120.
Entering comm_reconnect
inherited fd. return from net_associated_fd. ipc=536882424, netfd=0
Entering

Contributed By: Ren Maddox
 'errno 28' is probably:

#define ENOSPC 28 /* No space left on device */
 

"gateway_boot: epact_bdb_open failed: 22: Invalid argument" Error in Gatelog

Contributed By: Gary Hamilton
 If you’ve got problems with your Endpoints not being able to log into your Gateways and you’re seeing the error above in your Gatelog then here’s how to fix it… [Go to the article]
 

How Can I Disable/ Turn Off the Tivoli ‘TME’ Icon in the System Tray?

Contributed By: Cliff Hobbs [MVP SMS]
 Wondering if and how you can get rid of the 'TME' status icon in the System Tray?  You'll find the answer to your questions here… [Go to the article]
 

How Can I Tell Which Version Of The Endpoint Code Will Be Installed On New NT Endpoints?

Contributed By: Cliff Hobbs [MVP SMS]
To determine which version of the Endpoint will be installed by Tivoli on any new Endpoints open the 'EPUPG.INF' file which is located in the 'Tivoli\bin\lcf_bundle.40\bin\w32-ix86\upgrade' directory on your TMR server.

The value at the end of the ‘current_version’ line is the version number that any new Endpoints will be installed at.
 

How Can I Tell Which Version Of The Endpoint Code My NT  Endpoint Is Running?

Contributed By: Doug Sutherland
 To check which version of the Endpoint software an Endpoint is running:

  1. Load a web browser such as Internet Explorer.
     

  2. Type 'http://127.0.0.1:9495' in the 'Address' field and press [RETURN] to display the 'TMA Daemon Status Page'.
     

  3. The ‘Version:’ field displays the version of the Endpoint code the Endpoint is running.

How Do I Tell Which Version Of LCF WINSTLCF Will Install?

How do I tell which version of lcf the command winstlcf will install if I have different versions on my TMR?  (I have different versions because SIS put them on the box). Or is it going to install the version that matches the version of Framework I have on the TMR. Also how do I tell what version number the lcf is?

Contributed By: Cliff Hobbs [MVP SMS]
 The "wlsinst" command will install the current LCF bundles that are installed on you TMR. SIS has no bearing on this at all. Thus if you have Framework 3.6 with no patches, wlinstlcf will install version 5. If you have Framework 3.6.1 with no patches, wlinstlcf will install version 20.

Use the "wadminep [endpoint label] view_version" command to get the version number of the LCF code on that Endpoint. This information is also available when Endpoints login to the gateways. You would have to research what output you are generating from your endpoint policy (i.e. login_policy).
 

How Do I Uninstall the 3.6 Endpoint?

Contributed By: Cliff Hobbs [MVP SMS]
 To uninstall the 3.6 Endpoint from the Endpoint itself:

  1. Stop the Endpoint service.

  2. Delete the following Registry keys:

    "    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\lcfd"

    "    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run\lcfep"

  3. Go to the directory where the Endpoint is installed for example "C:\apps\Tivoli\lcf\bin\w32-ix86\mrt" directory.

  4. Run the "lcfd -r" command to uninstall the Endpoint service.

  5. Run the "lcfep -s" command to remove the Tivoli icon from the System Tray and from the Registry.

  6. Delete the "Tivoli" directory.

How Do I Upgrade The Version Of The TMA Software On An NT Endpoint?

Contributed By: Cliff Hobbs [MVP SMS]
If any of the Endpoints installed in your environment are running the wrong version of the Endpoint code they can be upgraded via the Tivoli CLI as follows:

  1. Load the Tivoli CLI.
     

  2. Type the following command where ‘<endpoint>’ is the name of the Endpoint you wish to upgrade:

    wadminep <endpoint> upgrade
    You will see the following lines as the Endpoint is upgraded:

    Performing administrative mode 'upgrade'
    Upgrading endpoint '<endpoint>'
    Endpoint interpreter = w32-ix86
    SUCCESSFULLY upgraded endpoint '<endpoint>'

To check that the Endpoint software has been upgraded:

  1. Load a web browser such as Internet Explorer.
     

  2. Type 'http://127.0.0.1:9495' in the 'Address' field and press [RETURN] to display the 'TMA Daemon Status Page'

    or

    If the '    TMA Daemon Status Page' is already loaded press 'F5' to refresh it.
     

  3. The ‘Version:’ field should now display the correct version of the Endpoint software.

Installing NT Endpoints using the "winstlcf -d" command

I'm a bit confused over using the "winstlcf -d <directory_name>" switch to install an Endpoint on NT.

If you look in the 3.7B Reference Manual is says if you don't use the "-d <directory_name>" switch then the Endpoint gets installed in the "c:\Tivoli\lcf" directory yet if you run the "winstlcf" command without any switches from the Tivoli CLI the help says it will be installed in the "Program Files" directory.

Can anyone clarify which one is right?

Contributed By: Tim Grafton, Cliff Hobbs [MVP SMS]
 It looks like there's a typo error in both the 3.7B and 3.7.1 Reference Manuals as if you don't use the "-d" option the Endpoint is installed in the "c:\Program Files\Tivoli\lcf" directory (this is from experience of  installing about 500 Endpoints over the last two weekends using winstlcf without using the "-d" option).
 

"lcfd Connection refused...errno='79'" in LCFD.LOG

When I get to a magic number of around 300 Endpoints on a Gateway several endpoints begin exhibiting the following behaviour - this was taken from the 'LCFD.LOG':

Aug 28 10:58:08 1 lcfd exception: gw connect ../../src/comm/netio.c:374 [cti_create_client or cti_timed_create_client] : loc=3, cls=2, dec=7, sys=79, tli=0, evt=0
Aug 28 10:58:08 1 lcfd Connection retry attempts exhausted
Aug 28 10:58:08 1 lcfd node_login: listener addr '1.1.1.2+9495'
Aug 28 10:58:08 1 lcfd Trying last known gateway ...
Aug 28 10:58:08 Q lcfd login_to_gw: Attempting to send login packet to appropriate GWs
Aug 28 10:58:08 Q lcfd login_gw -> 5.6.9.8+9494
Aug 28 10:58:08 3 lcfd get_local_interface: bind address '1.1.1.5'
Aug 28 10:58:08 2 lcfd Connection refused...errno='79'.

Contributed By: Gary Hamilton
 Try increasing the 'max_concurrent_jobs' parameter on the Gateways. The default is 200.

This parameter determines the number of pthreads a gateway has available to process jobs on its jobq max_jobs is no longer used. Its obsolete.

'rpc_maxthreads' is the gateway RPC thread parameter and determines the number of RPC threads are available to the gateway process 'rpc_max_threads' is the parameter that controls the number of RPC threads available to the oserv and is a TMR wide parameter.

There is a relationship between the RPC thread parameters. Each gateway RPC thread uses an oserv RPC thread. Different types of gateway methods use RPC threads, and others are run using pthreads, and therefore run from the jobq. Login upcalls are handled by pthreads, therefore 'max_concurrent_jobs' is the correct parameter to adjust. When you are having trouble with your gateways it is a good idea to change the logstatus interval on the gateway to a smaller value than the default. Set it to 300 seconds (or maybe even as low as 60 seconds), so you have an idea of the work load on your gateway and you can determine what it needs to process the work it is being asked to do. This will write to the gatelog (independent of debug level) a line indicating what gateway resources are in use. It looks like:

 2002/09/09 14:32:54 01027640: STATUS DATA: jobqq= 0 jobqr= 0 reqdq= 0 gwmethods= 0

The fields are

  • jobqq - number of jobs in the jobq.
  • jobqr - number of jobs that are running. The maximum value this can attain is max_concurrent_jobs, because that is the maximum number of pthreads available to process jobs.
  • reqdq - number of TCP comms that have not yet been processed by the reader thread. When these are processed, they are placed on the jobq.
  • gwmethods - number of methods using tmf_dispatch threads. These use gateway rpc threads and oserv rpc threads, one of each.

A lot of this is explained in the TME10 Endpoint Gateway field guide.
 

My Endpoints Won't Login to My Gateway

I've installed an Endpoint but it won't login to the Gateway.

Contributed By: Cliff Hobbs [MVP SMS]
Try adding the following line to the end of the 'last.cfg' file in the 'C:\Program Files\Tivoli\lcf\dat\1' directory:

lcs.login_interfaces=<Gateway_IP_address>+<port_number>

For example if the IP address of your Gateway is 192.168.11.5 and you're using the default port of 9494 then you would add the following line:

lcs.login_interfaces=192.168.11.5+9494

Save the file and then Stop/ Start the Tivoli Endpoint service on the Endpoint.

Update 3/2/03 Contributed By: Chris Cox
 The other alternative to adding the 'lcs.login_interfaces=<Gateway_IP_address>+<port_number>' line to 'last.cfg' is to:

  1. On the Endpoint, stop the 'Tivoli Endpoint' service from Control Panel or use the 'net stop lcfd' command from a Command Line.
     
  2. Delete all of the files in the 'C:\Program Files\Tivoli\lcf\dat\1' directory EXCEPT for the DLL files.
     
  3. Delete the 'Cache' and 'Codeset' subdirectories.
     
  4. Delete the Endpoint from the relevant Gateway in Tivoli.
     
  5. Add the following line to the end of the 'last.cfg' file in the 'C:\Program Files\Tivoli\lcf\dat\1':

    lcs.gateway_address=<Gateway_IP_address>+<port_number>
     
  6. On the Endpoint, start the 'Tivoli Endpoint' service from Control Panel or use the 'net start lcfd' command from a Command Line.
    7.

Previously Working Endpoint Now Won't Login to My Gateway

I have an Endpoint that previously has signed into my Gateway and now for some reason doesn't anymore.

Contributed By: Cliff Hobbs [MVP SMS]
You could try adding the 'lcs.login_interfaces=TMR_IP_address' line to the end of the 'last.cfg' file on the Endpoint as detailed in My Endpoints Won't Login to My Gateway to point it in the right direction.

If this fails try deleting the 'lcf.dat' and 'lcf.id' files from the 'C:\Program Files\Tivoli\lcf\dat\1' directory and then stopping and starting the 'Tivoli Endpoint' service on the Endpoint. By deleting these files, when the Endpoint service starts up and detects these files are missing it re-performs the initial installation.

If anything on the Endpoint has changed (such as it's IP address), then you will need to delete the Endpoint out of the Tivoli database, then delete the 'lcf.dat' and 'lcf.id' files and then Stop/ Start the 'Tivoli Endpoint' service (if you're using DHCP in you environment you might want to read the Tivoli Not Being Updated with DHCP IP Address Changes thread).

The next thing to try is:

  1. Delete the Endpoint out of the Tivoli database.
     
  2. Run the Endpoint uninstall routine ('Program Files\Tivoli\lcf\uninst.bat' by default).
     
  3. Make sure that the 'lcf' directory has been deleted (kept in 'Program Files\Tivoli' by default).
     
  4. Check that the 'Tivoli Endpoint' service has disappeared from Control Panel.
     
  5. Run Regedt32 and make sure any keys beginning 'lcfd' aren't present in 'HKLM\SYSTEM\CurrentControlSet\Services'.
     
  6. Rename the '%SYSTEMROOT%\system32\TivoliAP.DLL' file - you can't delete the file as it's loaded at boot time.
     
  7. Reboot the machine.
     
  8. Delete the file that you renamed from 'TivoliAP.DLL'
     
  9. Try installing the Endpoint.  You might want to consider typing the address of the Gateway you want the Endpoint to login to if you're installing the Endpoint manually (enter the IP address of the Gateway in the 'Other' field of the 'Advanced Configuration' screen).
     
  10. Reboot the Endpoint post installation if prompted to.
     
  11. Load a browser and make sure the Endpoint has logged into the Gateway by typing 'http://127.0.0.1:9495' in the 'Address' field.  It may take a while for the status to show as 'running'.

If this still doesn't work, you might want to consider changing the level of logging performed by the Endpoint to help you troubleshoot the problem.  There are two ways to change this:

  • From the Endpoint itself by changing the value of the "log_threshold" entry in the "LAST.CFG" file (for troubleshooting Tivoli recommend changing it to 2 or 3, then changing it back to 1 afterwards).
     
  • From the Tivoli CLI using the "lcfd -d <level> -n <endpoint_name>" command

Further details on the lcfd command and it's usage can be found in the Framework Reference Guide.
 

Running Dual Framework Environments

I have an issue here that I'd appreciate some help/ guidance on. We are going to be installing two TMRs here to create and test packages on.

  • TMR1 - Framework 3.7B + Software Distribution 4.0 + Endpoint version 83
  • TMR2 - Framework 3.7.1 + Software Distribution 4.1 + Endpoint version 98

Both of the TMRs will be in the same 'test' domain which uses DHCP.

The reason for the two environments is the difference in Software Distribution version - one customer is using 4.0 the other 4.1. There may be a possibility of upgrading the 4.0 customer to 4.1 but this has yet to be decided so is some way off.

The plan for our Packaging team when building a package is to load the appropriate customer's workstation image on their machine, package the application using the relevant version of Package Editor, then reload the machine and test deploying the software through Tivoli.

The big issue I can see with this is how do I control which TMR server the Endpoint logs into based on which customer build is loaded (for example I don't want version 83 of the Endpoint installed and an Endpoint to report to TMR1 when I want to create a package for TMR2)?

Is there anyway I can tell Endpoints to report to a TMR based on workstation name so for example if the workstation name begins 'CUST1' report to TMR 1 whereas if it's 'CUST2' report to TMR2? (The other angle to this is could I get the TMRs to only accept Endpoints with certain names)?

As the number of packages being developed and therefore the number of rebuilds that are going to be required is going to be high, I need as slick and robust a process as possible.

If anyone out there is already doing who can offer me help and advice I'd be very grateful .

Contributed By: James Bale, Martin Creswell, Trevor Dennis, Cliff Hobbs [MVP SMS]
You have several options here.

If the Endpoint code is installed in the customer build modify the "LAST.CFG" by adding the "lcs.login_interfaces=<tmr/gway_IP_address>+9494" line to the end of this file where "<tmr/gway_IP_address>" is the IP address of the relevant Gateway. In this way, regardless of what the machine name is, that build will force it to log into the TMR you want.

The other option is to use the "select_gateway_policy", as described on page 114 of the All About Tivoli Management Agents Redbook.

Probably the best option is to modify the "SETUP.ISS" file that is included as part of the Endpoint installation to specifically attach an Endpoint to the TMR you want it to use.  If you edit the file, under the "[SdShowDlgEdit3-0]" section is a line that begins "szEdit3".  Simply add the "-g <tmr/gway_IP_address>" text to the end of this line to specify the Gateway you want the Endpoint to use, for example the following line specifies to use a Gateway with an IP address of 10.5.1.3:

szEdit3=-g 10.5.1.3

Once you edited the file simply run SETUP.EXE with the "-s" switch (so the command line should be "setup.exe -s") to run the installation in silent mode (in other words no dialog boxes are displayed).

If you're not comfortable with editing the file or if you want to customise the settings either further simply run SETUP.EXE with the "-r" switch as detailed in the Creating InstallShield Response Files section of the Tivoli Enterprise Installation Guide.

To add the "-g <tmr/gway_IP_address>" line to "SETUP.ISS" file when recording your response file simply type the "-g <tmr/gway_IP_address>" entry in the "Other" box on the "Advanced Configuration" screen.

You can find an explanation of the "SETUP.ISS" on Page 61 onwards of the All About Tivoli Management Agents Redbook.

Once you've got your "SETUP.ISS" files created simply put a modified copy of "SETUP.ISS" file along with the rest of the Endpoint installation files on an NT share on each TMR to point the Endpoint in the right direction.

One key point is that if the machine gets rebuilt, it will need to be deleted from Tivoi before the endpoint is re-installed.
 

Tivoli Not Being Updated with DHCP IP Address Changes

I'm using DHCP in my environment and on some of my machines the IP addresses are changing without the machine being rebooted (the IP address is being released and a new address obtained). The end result is that I'm spending a lot of time having to delete Endpoints from Tivoli and then re-install them to get the Endpoint into Tivoli with the right address.

Contributed By: Cliff Hobbs [MVP SMS]
Firstly you should ALWAYS use fixed IP addresses for servers.  As for Endpoints, you might want to consider setting a value for the "address_notif_interval" setting.  This setting is designed for environments such as yours where DHCP is used for IP addressing and the IP address is changed without the Endpoint service being restarted (a typical example being where users suspend their laptops, move to a different site then unsuspend and expect Tivoli to be happy about it).  This setting forces the Endpoint to wakeup and notify the Gateway of it's IP address. There are two ways to change this:

  • From the Endpoint itself by add the following line to the end of the "LAST.CFG" file:

     address_notif_interval=<value_in_seconds>
     
  • From the Tivoli CLI using the "lcfd -D address_notif_interval=<value_in_seconds" command.

The default value for this setting is "0" (disabled) and the Tivoli recommendation is to set it to 300 seconds (which is only 5 minutes - you might want to consider setting this to a higher value depending on your lease times).

Further details on the lcfd command and it's usage can be found in the Framework Reference Guide.
 

© FAQShop.com 2003 - 2005

Goto the Tivoli Home Page

 Email the Author