IBM Support

ITM TEMS Upgrade When FTO Hub TEMS Mirror is Operational

Question & Answer


Question

What order should the TEMS upgrade proceed when hotstandby is operational?

Answer

The simplest way is 
A) Stop the MIRROR hub TEMS
B) Apply TEMS maintenance to the MIRROR hub TEMS. It will be started and stopped.
C) Start the MIRROR hub TEMS
D) Stop the PRIMARY hub TEMS
E) Wait for about 10 minutes until all the agents and remote TEMSes swap to the MIRROR hub TEMS.
F) Apply TEMS maintenance to the PRIMARY hub TEMS. It will be started and stopped.
G) Start the PRIMARY hub TEMS
H) Stop the MIRROR hub TEMS
I) Wait for about 10 minutes until all the agents and remote TEMS swap to the PRIMARY hub TEMS.
J) Start the MIRROR hub TEMS
There are rare edge cases where this simple process might show issues. For example, if a remote TEMS had communication problems connecting to the MIRROR hub TEMS it could switch back to the PRIMARY hub TEMS during maintenance. If the MIRROR hub TEMS crashed or ran out of storage or the system it is running on failed... that also would cause the remote TEMS to connect to the TEMS under maintenance. You can imagine other rare scenarios. 
If you are worried about that, you could just stop both PRIMARY and MIRROR hub TEMSes and apply maintenance separately. There would be some outage but that is almost unavoidable. That is even true during FTO swapping which often takes 30 minutes or so.

If you have a single TEPS, than it can be upgraded next.

Some installations have duplicate Portal Servers, one for the PRIMARY hub TEMS and one for the MIRROR hub TEMS. In that case update the TEPSes as follows:

1) Stop the TEPS/primary
2) Upgrade the TEPS/primary and also do a migrate-export of the data
3) Start the TEPS primary
4) Stop the TEPS/mirror at this step
5) Upgrade the TEPS/mirror migrate-import to make the two TEPS databases identical.
6) Start the TEPS/mirror.

The migrate-export/migrate-import should be performed regularly anyway to keep the two TEPS database tables in sync.

[{"Product":{"code":"SSTFXA","label":"Tivoli Monitoring"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"ITM Tivoli Enterprise Mgmt Server V6","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"All Versions","Edition":"All Editions","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
09 March 2021

UID

swg21499940