Resetting version numbers for the Universal Agent
If you reinstall a Universal agent without running a cleanup the revision numbers will be incremented away from the original 00 versions and the old agent will still be shown as offline. Additionally any BAROC definitions you have made will be incorrect. To avoid this use the um_cleanup script as provided by IBM.
- For Windows operating systems run um_cleanup.bat
- For UNIX operating systems run um_cleanup
Before you run either of these scripts, you must shut down the IBM Tivoli Universal Agent and manually delete the existing IBM Tivoli Universal Agent managed systems from the Tivoli Enterprise Portal Managed System Status workspace.
After you run the cleanup script, you must recycle the Tivoli Enterprise Monitoring Server and the Tivoli Enterprise Monitoring Server and then restart the IBM Tivoli Universal Agent to activate the new 00 version suffixes.
If your Universal Agent is logging into a remote TEMS you will also need to update the ATR and CAT files from the Remote TEMS to the Hub TEMS.
Finally, you may need to fix the TEP queries and remove the ODI files in order to view data correctly in the TEP. This is described in the tip Fixing TEP after resetting Universal Agent version numbers
Manually deleting managed systems
Perform the following steps to delete the existing managed systems:
- Stop the IBM Tivoli Universal Agent so all its managed systems go offline.
- From the Tivoli Enterprise Portal client Physical Navigator view, right-click on Enterprise and select Workspace → Managed System Status.
- Highlight all the IBM Tivoli Universal Agent managed systems.
- Right-click and select Remove Managed System.
- The Apply Pending Updates icon is highlighted in the Tivoli Enterprise Portal client.
- Select the Apply Pending Updates icon to collapse the Navigator tree. When you re-expand the Navigator tree, your IBM Tivoli Universal Agent managed systems no longer appear in the tree.
Running the cleanup program
You need to run the cleanup script several times, once for each component:
- Agent
- Tivoli Enterprise Monitoring Server (Hub and Remote)
- Tivoli Enterprise Portal Server
To run the cleanup script, enter the following in a command window on the appropriate system:
For Unix systems
um_cleanup <CANDLEHOME> <BINARCH> <TEMSNAME> <COMPONENT>
For Windows systems
um_cleanup <CANDLEHOME> <COMPONENT> [<WORKDIR>]
where:
<CANDLEHOME>
The base directory where your IBM Tivoli components are installed. Note that on Windows this should not include the drive letter (“C:”) part.
<BINARCH>
The architecture code for you ITM 6 Unix platform e.g. aix516, hp11. You can determine this using the itmcmd config command, such as
$BINARCH=`itmcmd config -A -g um | grep BINARCH`;
<TEMSNAME>
The name of your TEMS server e.g HUB_`hostname` or REM_`hostname`.
<COMPONENT>
| Type | Component |
| Agent | UA |
| Tivoli Enterprise Monitoring Server | CMS |
| Tivoli Enterprise Portal Server | CNPS |
Note : These should always be entered in capitals
<WORKDIR>
Only applies to cleaning the windows UA component. Only required if the work directory is not the default IBMITMTMAITM6work.
Examples
Agent
um_cleanup $CANDLEHOME aix516 HUB_scooby UA
um_cleanup IBMITM UA (Windows)
TEMS
um_cleanup $CANDLEHOME aix516 HUB_scooby CMS
um_cleanup IBMITM CMS (Windows)
TEPS
um_cleanup $CANDLEHOME aix516 HUB_scooby CNPS (Unix)
um_cleanup IBMITM CNPS (Windows)
Updating the Hub TEMS
If your Universal Agent is logging into a remote TEMS you will need to update the ATR and CAT files from the Remote TEMS to the Hub TEMS.
Unix TEMS
| Source on Remote TEMS | Destination on Hub TEMS |
|---|---|
|
$CANDLEHOME/tables /REM_<hostname>/ATTRLIB/<xxx>ATR00 |
$CANDLEHOME/tables /HUB_<hostname>/ATTRLIB |
|
$CANDLEHOME/tables /REM_<hostname>/RKDSCATL/<xxx>CAT00 |
$CANDLEHOME/tables /HUB_<hostname>/RKDSCATL |
Windows TEMS
| Source on Remote TEMS | Destination on Hub TEMS |
|---|---|
| %CANDLEHOME%/cms/ATTRLIB/<xxx>ATR00 | %CANDLEHOME%/cms/ATTRLIB |
| %CANDLEHOME%/cms/RKDSCATL/<xxx>CAT00 | %CANDLEHOME%/cms/RKDSCATL |
Hits: 61