I need to install and configure a software TIM remotely on a Linux OS. Does anyone have a guide for this? I'm concerned with how I'll reconnect once the server reboots, among other things.
I just remembered that the 9.6 TIM is certified with APM 9.5.3 EMs out of the box, so you can install the 9.6 TIM per Barry's advice and use it with your 9.5.3 APM cluster.
What version are you installing? If it's really the software TIM - version 9.6 or later - then there shouldn't be any problem as you don't need to reboot the server, and if it does you can just ssh to the same host/ip. I'd say you're really only going to install the TIM remotely via ssh.
If you're looking for step by step instructions I can post those here as well - I'm working out simplified steps now.
I'm doing the 9.5.3 version of APM. What do you think?
That makes things more tricky because of the required initial OS install.
As you maybe aware pre-9.6 TIMs are software appliances where we supply the Kickstart image for the RHEL OS. whereas in 9.6 the end user supplies the OS.
From previous history that I checked a remote Kickstart via Virtual CD/DVD does not appear to be feasible i.e. the Kickstart image has to be burned onto a physical CD/DVD and the subsequent boot process has to be run from the actual server console.
Once the OS is installed the TIM software itself can be installed remotely using the UI for the Apache web server that is installed with the OS.
Not the information you were probably hoping for, but hopefully it helps your planning
I saw an email from Chris Kline that says a hotfix needs to be installed in order to make a 9.6 TIM work with 9.5.3 APM. I opened a support ticket to ask about this but so far support has no idea what I'm talking about and Chris has yet to reply to my email. Can you confirm? Ultimately I need details and documentation about this hotfix and I can't find anything.
If you still have Chris Kline's email can you please send it to me? (it seems like Chris is travelling this week so that is why his reply is delayed.)
There is a new TLS 1.1/1.2 feature which will be delivered in APM 9.8 that has been back ported to a 9.6 TIM HotFix and that does require a corresponding 9.5.3 EM HotFix.
However if that feature is not required it is my understanding that the 9.6 TIM is compatible with the 9.5.3 EM OOTB, as long a the default ports are used when the 9.6 TIM is installed (I will double check this & get back to you)
I think you might be right and others might be confused by Chris's email (below). It seems to relate specifically to TLS and not simply "running a 9.6 TIM with 9.5.3 APM." But if you could confirm ootb functionality that would be great.
Recently there have been inquires from a number of customers regarding TLS 1.1/1.2 support for CEM. GA support for TLS is presently targeted as new functionality (this is not a defect) for APM 9.8 and is on track at this time. New functionality is not traditionally back ported into GA releases; there are heavy testing costs that divert focus from the building of new and innovative functionality. If conferring with a customer on this topic, please explain using those terms, as this helps set appropriate expectations.
However, recent publicized events caused many customers to discontinue using SSL and TLS 1.0 protocols for their applications; we are therefore providing a hot fix to assist customers with TLS 1.1/1.2 functionality in the interim. The following list describes what functionality might be made available for various CA APM versions:
TIM 9.5.x does not work for TLS 1.1/1.2 with this version. Must be TIM as Software (9.6+).
See note below about TIM 9.6.0 working with 9.5.1+ EM's
TIM 9.6.0 works with hotfix (request from support), has already been provided to some customers with success
TIM 9.6.0 hotfix’d together with normal 9.6 EM should be OK, but also will require field certification (not fully QA’d)
TIM 9.6.0 hotfix’d can work with 9.5.3 EM’s and has been QA'd.
Instructions clarify that it only supports the ports that 9.5.3 understands (not port-configurable like 9.6+).
Also requires a hotfix on EM side as well.
Can be used for situations where customer is on 9.5.1+ EM and isn’t ready to upgrade to 9.6+.
9.5.1, 9.5.2, 9.5.6 EM should work the same as the above but it has not been QA’d and would be field certified.
Customer-friendly explanation: Interim TLS 1.1/1.2 support requires a 9.6.0 TIM but can work with 9.5.x Enterprise Managers (EM). There was a major change in how the TIM was built and delivered at 9.6 and customers need to move to the 9.6 TIM in order to take advantage of the hotfix. Beginning with TIM 9.6 (for standalone TIM only, not MTP), the new TIM-as-software format will require a re-image of the TIM appliance and the customer’s own RedHat or CentOS linux image (the TIM is simply installed as a package now instead of provided as a soft appliance). Presales should be able to assist with these steps if necessary. Contact CA Support for the hotfix, which will be applied as an updated TIM image via the GUI. In addition, there is also a hotfix for the Enterprise Managers at 9.5.x that should be applied. These hot fixes have been tested/certified against EM release 9.5.3, so if a customer is at 9.5.2 (for example) it will function as a field certification as opposed to something that was previously QA’d. Though we expect success, Enterprise Managers may need to be upgraded to the tested version should unforeseen issues arise. If possible, this should be completed in a test environment prior to production.
TIM 9.6.1 hotfix not planned, recommendation to work with 9.7
TIM 9.7.0 hotfix creation is already in process (should be requested from support); won’t be internally QA’d and would need to validate with customer and then field certified (no CGR planned)
TIM 9.7.1 Too late to slipstream into the release itself (already in final testing). Therefore customer should use 9.7.0 or wait for 9.8.0.
TIM 9.8.0 GA TLS 1.1/1.2 support.
MTP. Hot fixes apply equally to MTP and standalone TIM. MTP TIM is deployed differently but will use the same package. Instructions in the hotfix may pertain to the standalone TIM and might need to be manually accommodated for MTP installation.
You may socialize this information with customers who ask, but the standard answer is to focus on the GA support at APM 9.8.
I have confirmed that if the new TLS 1.1/1.2 functionality is not required then the 9.6 TIM is compatible with the 9.5.3 EM OOTB, as long a the default ports are used when the 9.6 TIM is installed
As Lynn says, with 9.5.3 it is a full RHEL OS install, but there are a couple of scenarios where you can do it remotely nonetheless.
First, see if the hardware you're using supports ILO (Integrated Lights Out) or IPMI (Intelligent Platform Management Interface). Both are out-of-band tools that give you remote consoles and access to power the system on, BIOS, etc., and both usually allow you to remotely mount either a an ISO or a physical CD on your local desktop/laptop. I've done this with ILO (I think that is HP/Compaq) and while it wasn't exactly smooth it did work. I've also used IPMI to remotely manage our own MTPs, and the interface is pretty **** cool.
Also, if the TIM you're installing on is running in a VMware environment - likely only if this is for a lab or POC - then you can use the vSphere tools just like you would for any OS install.
Either way it's worth asking. If this is a server class machine in a data center there's a pretty good chance it has ILO or IPMI.
Thanks guys. If the 9.6 TIM software will work with APM 9.5.3 and run on the customer supplied OS, that's what I'll do. Sound good?
Yes, that should definitely be your easiest option.
Thanks Lynn. Do you recommend the 9.6.0 or 9.6.1 version of the TIM software? I'm using 9.5.3 mom and collectors.
I am checking on whether the same compatibility of 9.5.3 EMs with the 9.6 TIM also applies for the 9.6.1 TIM
However looking at the 9.6.x WIKI Release Notes there are no changes to the TIM between 9.6 and 9.6.1 so I think you may as well as stick with the 9.6 version.
Retrieving data ...