IBM Support

Tacmd setagentconnection is not restarting all agents when the -a option is used

Question & Answer


Question


During tests it was noted that tacmd setagentconnection command when used with "-a" option did not restart all agents present on the host. Only the OS Agent was restarted.
For example:
- You have HD, SY and the OS agent running and issue the following tacmd command to update the TLS and cipher settings...
- tacmd setagentconnection -a -n Primary:yourhost:NT -e KDEBE_TLS10_ON=NO KDEBE_TLS11_ON=NO KDEBE_TLSV12_CIPHER_SPECS='TLS_RSA_WITH_AES_128_CBC_SHA256,TLS_RSA_WITH_AES_256_CBC_SHA256'
- Wait until the deployment finishes with SUCCESS

Results
On the host with Windows OS Agent:
- The changes set in the "-e" option are made in all ini files but only KNT is restarted during deployment.
All other agents are stopped but not started during the deployment process.

[{"Type":"MASTER","Line of Business":{"code":"LOB67","label":"IT Automation \u0026 App Modernization"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSTFXA","label":"Tivoli Monitoring"},"ARM Category":[{"code":"a8m3p000000hBWhAAM","label":"ITM Command Line Interface\/CLI"},{"code":"a8m3p000000hBW3AAM","label":"ITM Communications"}],"ARM Case Number":"TS008699707","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]

Log InLog in to view more of this document

This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.

Product Synonym

Tivoli Monitoring; ITM

Document Information

Modified date:
10 July 2024

UID

ibm16587038