![]() |
![]() |
[ Bottom of Page | Previous Page | Next Page | Contents ]
After you have upgraded the agent code for any interim fix, it is possible for an agent to become "out-of-sync" with the available kernel extension on the runtime server, and to be forced to run without a kernel extension. This happens when an agent requests a new kernel extension and the version of the agent code on the agent does not match the version of the agent code on the runtime server.
This problem impacts the agent's ability to perform license enforcement, and perform usage monitoring on AIX(R) platforms.
A full description of how this problem can occur, and the measures you can take to avoid it and to correct affected agents, is provided in IBM Tivoli License Manager: Release Notes (revised December 2003), which will be available from mid-December from the Tivoli Software Information Center Web site. The Tivoli Software Information Center is located by using the following Web address:
http://www.ibm.com/software/tivoli/library/
An important aspect of recovering from this problem is discovering which agents are affected. After you have installed this fix, every time a runtime server is unable to supply an agent with a kernel extension file, a flag will be set in the agent database. This information will be propagated to the administration server, in the normal way. A value of zero in this flag indicates that the agent is running with the correct kernel extension; all other values indicate that the agent does not have a kernel extension, and give an indication of the reason.
If you issue the following SQL command from the DB2(R) command line on the administration server, you will list the agents that are running without a kernel extension:
select hostname,ip_address,os_version,storage as kernel_status from adm.agent where storage <> 0
This query displays a table showing the following data:
[ Top of Page | Previous Page | Next Page | Contents ]