OS Agent does not install and a message indicates it was
already installed
About this task
The file
status.properties
, located in
$DBDIR/AMX/data/
is not deleted when you
uninstall the Upgrade Toolkit. The Upgrade Toolkit refers to the old
status.properties
file that contains information indicating there the OS Agent was
installed. You might experience this problem if you do the following in the order
listed:
1.
Upgrade an endpoint.
2.
Uninstall the Upgrade Toolkit.
3.
Clean the endpoint manually.
4.
Reinstall the Upgrade Toolkit.
5.
Attempt to upgrade the endpoint you previously upgrade in step 1.
Take the following steps to verify that information in the
status.properties
file is
causing this problem:
1.
Open the
status.properties
,
2.
Look for an entry like the following example:
#Copyright IBM Corporation 2005 #Wed Sep 14 15:54:43 CDT 2005 @Endpoint\:
\:east@EndpointClass\:TMF_Endpoint\:\:Endpoint=COMPLETE @Monitor\:Coast\
:120401@Threshold\:critical=COMPLETE
In this example, the status of the endpoint "east" is COMPLETE, which
indicates that it was upgraded successfully. The witmupgrade command does
not upgrade any item with the COMPLETE status and reports that it was
already upgraded.
To upgrade the endpoint, the status for the endpoint "east" must be the
INCOMPLETE, such as in the following example:
@Endpoint\:\:east@EndpointClass\:TMF_Endpoint\:\:Endpoint=INCOMPLETE
The only way to change the endpoint status in the
status.properties
file to
INCOMPLETE is to perform a rollback on the upgrade of the item. See the
IBM
Tivoli Monitoring: Upgrading from Tivoli Distributed Monitoring
.
Rolling back the upgrade:
About this task
You can use the rollback option (–r option) of the
witmupgrade
command to remove
the new IBM Tivoli Monitoring resources that you created. This is a necessary step
if you want to repeat the test scenario. Rolling back the upgrade for the test
scenario removes the Windows OS monitoring agent from the Windows endpoint
and also removes the new situations and managed system list.
Follow these steps to roll back the upgrade:
1.
Change to the
$DBDIR/AMX/shared/analyze
directory:
cd $DBDIR/AMX/shared/analyze
2.
Type the following command to roll back the upgrade:
witmupgrade -x profilemanagers/DM_TEST_PM.xml -r -f scans/baseline.xml
where:
Chapter 5. Installation and configuration troubleshooting
71
Summary of Contents for E027SLL-H - Tivoli Monitoring - PC
Page 1: ...IBM Tivoli Monitoring Version 6 2 3 FP1 Troubleshooting Guide GC32 9458 05...
Page 2: ......
Page 3: ...IBM Tivoli Monitoring Version 6 2 3 FP1 Troubleshooting Guide GC32 9458 05...
Page 14: ...xii IBM Tivoli Monitoring Troubleshooting Guide...
Page 16: ...xiv IBM Tivoli Monitoring Troubleshooting Guide...
Page 18: ...xvi IBM Tivoli Monitoring Troubleshooting Guide...
Page 22: ...4 IBM Tivoli Monitoring Troubleshooting Guide...
Page 82: ...64 IBM Tivoli Monitoring Troubleshooting Guide...
Page 144: ...126 IBM Tivoli Monitoring Troubleshooting Guide...
Page 164: ...146 IBM Tivoli Monitoring Troubleshooting Guide...
Page 188: ...170 IBM Tivoli Monitoring Troubleshooting Guide...
Page 240: ...222 IBM Tivoli Monitoring Troubleshooting Guide...
Page 262: ...244 IBM Tivoli Monitoring Troubleshooting Guide...
Page 274: ...256 IBM Tivoli Monitoring Troubleshooting Guide...
Page 276: ...258 IBM Tivoli Monitoring Troubleshooting Guide...
Page 284: ...266 IBM Tivoli Monitoring Troubleshooting Guide...
Page 288: ...270 IBM Tivoli Monitoring Troubleshooting Guide...
Page 302: ...284 IBM Tivoli Monitoring Troubleshooting Guide...
Page 308: ...290 IBM Tivoli Monitoring Troubleshooting Guide...
Page 309: ......
Page 310: ...Printed in USA GC32 9458 05...