Blogs

About this blog

Welcome to the Application Performance Management Blog, where you can read the perspectives from APM experts. This Blog provides insights into the Application Performance Management solution, as well as technical details about specific IBM products.

·When PRIMARY HUB TEMS starts
the upgrade, all RTEMS should FTO to the Secondary HUB TEMS, run ITMSuper
after FTO to validate all connections

·Validate that
the parameters are set in all Agents for the RECONNECT/
FALLBACK (Please add the your specified
parameters)

a.CTIRA_HEARTBEAT=

b.CTIRA_RECONNECT_WAIT=

c.CTIRA_PRIMARY_FALLBACK_INTERVAL=

Validating the Automated Script Package Install

To validate the package install was upgraded steps:

1. ./CandleHOME/bin directory and run
./cinfo

Verify that all ITM level components are at the upgraded
version

2. ./CandleHOME/registry/ verify the ITM component
version files

are showing the upgraded ITM version

3.On the Tivoli Enterprise Portal Server you should be able to
verify that the product and product support has been upgraded in the Manage
System Status Workspace

4.Run ITMSuper and verify the TEMS Server and validate the
catalog comparison are the same in the PRIMARY HUB TEMS, RTEMS, and
SECONDARY HUB TEMS. You can also verify the TEP installed version using
the same steps in ITMSuper and registry version files

Upgrade Scenario TESTS

1.Upgrade Scenarios for the Tivoli Monitoring Server (TEMS)

After upgrade has completed:

·Verify all ITM Components are
running (ps -eaf | grep /CandleHOME )

·Verify that the ./cinfo shows the upgraded
level of ITM

·Verify correct version level upgraded
- cd /CandleHome/registry open tms version file to
verify the upgraded ITM level is listed

·Restart the PRIMARY HUB TEMS , wait for
the PRIMARY HUB TEMS becomes the Secondary HUB TEMS, then shutdown the
Secondary HUB TEMS, Your PRIMARY HUB TEMS will not become the Acting HUB
TEMS and all RTEMS/Agents will reconnect to the PRIMARY HUB TEMS.

·Run ITMSuper, go to TOPOLOGY view and
validate the upgraded ITM level in the view. If you need to validate all
systems have reconnected to the PRIMARY HUB TEMS you can compare the ITMSuper
Topology view you ran before the upgrade with the new view

·Verify situations created prior to
upgrade have not been removed or changed

·Verify customization on previous
situations are still working (ex: Omnibus is still enabled,
TEC is still enabled, situations are still sending events to the SEC /
Omnibus Server, TEC and Take Action commands are still functioning

·To verify the Situation Event Forwarder
is communicating with the TEMS (acknowledge a situations event on the
Omnibus Server Console and make sure it shows acknowledged on the TEP

·Access the situation editor and create a
simple situation from the OS Situation list

·Set the Formula to trigger a condition:
integer (!=1) or string (!="dummy")

·Set the Sampling Interval to 30 seconds

·Distribute the situation to one managed
node then save it

·Wait until situation sends an event

·Open ITMSuper and validate the
distributions of the agents are sending events and you do not have a list of
offline events

·Modify threshold of situation to prevent
it from sending events

·Wait one minute or more to verify the
situation does not send an event

·Delete a situation (verify
situation is removed form the SEC and does not send an event to the TEP/SEC

·Create a few situations with EIF
enabled and verify events have been sent to Omnibus with the correct output

·Verify all Agents have been upgraded to
the correct ITM level
/CandleHome/registry open os version file to verify components are
at the upgraded ITM level or you can run ITMSuper – Topology
view and validate all agents are connected to correct RTEMS and shows the
correct upgraded ITM level.

·After the deployment has completed , log
into the PRIMARY HUB TEMS /tacmd login -s <HUB_NAME> -
run the ./tacmd listsystems and verify all agents show online