Introduction
It has been two years since the TIM Administration model last changed. This new series discusses the changing responsibilities for APM administrators since the transition.
.Since there are new readers to these Tech Tips (welcome!), it is best to review where we have been and are now.
Three Phases of APM TIM Administration Responsibilities
The paradigm of TIM and MTP Administration has gone through three distinct phases:
1) TIM as an Appliance (CEM 1-4.x) and MTP as an appliance (1-10.5).
What happened:
- The hardware, operating system, and TIM software were provided to the customer.
- The customer would open a support case to deal with security, operating system, and third-party concerns.
- The system was not to be modified unless given the okay by Support.
- Customer did not have to plan for TIM sizing but simply determine how many TIM appliances. were needed.
2) TIM was no longer an appliance -- aka "TimSoft". (APM 9.0-9.5)
What happened:
- The operating system and TIM software was supplied to customers
- Customers had to plan spend time determining TIM sizing .
- The customer would open a support case to deal with security, operating system, and third-party concerns.
- The compatibility guide specified a list of hardware choices. The hardware market changed at a faster pace than the certification of TIM servers.
- The system was not to be modified unless given the okay by Support.
3) TIM as software only (APM 9.6 onward) /MTP as software only (vMTP 10.6 onward)
- This was documented in APM 9.6 New Unofficial Rules
The documentation noted the transition as the following:
TIM installation is now available as software. Because the TIM is no longer a "software appliance", it is easier for you to maintain and upgrade the software.
TIM installation is now available as software that can be installed on any hardware that complies with the security policies of your organization. You can hence maintain and control the underlying operating system according to your IT policies
The vMTP April 2016 release notes talk about the product change only and little on the corresponding administration model change.
This is a new, non-appliance product that provides a similar kind of traffic monitoring to CA Multi-Port Monitor (CA MTP). It runs on a user-managed CentOS 6 system, running on third-party supplied hardware.
What happened:
- Only the TIM or MTP software only was provided
- Customers are responsible for providing the Linux OS and necessary license.
- Customers had the freedom to install the third-party and security updates on their TIMs provided it did not interfere with/slow down TIM performance.
-There should be less of a need to open Support cases because customers were responsible for operating system, security, and third-party software/hardware.
- But other customers had to deal with for the first time obtaining Linux resources and becoming Linux administrators.
- Customers provided their own hardware. For MTP, the hardware choices are
specified such as the TIM second phase.
- Customers are responsible for providing the Linux OS and necessary license.
- Customers had to ensure that their server met the necessary software pre-requisites:
TIM: https://docops.ca.com/ca-apm/10-3/en/installing/apm-installation-and-upgrade/install-and-configure-tim-for-ca-cem
vMTP: https://docops.ca.com/ca-virtual-multi-port-monitor/en/installing/software-specifications
Next time we will discuss the impact of the "software-only TIM" administration model.
Questions for Discussion:
1. What TIM administration model worked best for your site?
2. What are the tradeoffs for your site in TIM administrator responsibilities
3. What other topics would you like me to cover?