IBM Support

IV75592: SETAGENTCONNECTION DOES NOT WORK FOR MULTIPLE PROTOCOLS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Approver Initials:    RL
    Severity:             3
    Reported Release:     630
    
    PROBLEM DESCRIPTION:
    Specifying the following command,
    
    tacmd setagentconnection -n c25x0064:LZ -a -p
    SERVER=c25a0267.toronto.ca.ibm.com PROTOCOL1=IP.PIPE
    PROTOCOL2=IP.SPIPE
    IP_PIPE_PORT=1918 IP_SPIPE_PORT=3660
    BSERVER=C25A0268.toronto.ca.ibm.com
    BPROTOCOL1=IP.PIPE BPROTOCOL2=IP.SPIPE BIP_PIPE_PORT=1918
    BIP_SPIPE_PORT=3660 BACKUP=YES
    
    fails to correctly configure the target agent to point to the
    desired server.
    
    
    RECREATE INSTRUCTIONS:
    a.  Install agents (NT, R3) and upgrade to 63FP2
    b.  Run "tacmd setagentconnection" to change TEMS for agent
        and specify PROTOCOL1, PROTOCOL2, etc...
    
    =====================================================
    [root@itmmtvm364:/opt/IBM/ITM]
    # ./bin/tacmd listsystems -n Primary:ITMMTVM103:NT
    Managed System Name   Product Code Version     Status
    inst1:ITMMTVM103:R3   R3           06.30.02.00 N
    Primary:ITMMTVM103:NT NT           06.30.02.00 Y
    
    [root@itmmtvm364:/opt/IBM/ITM]
    # ./bin/tacmd setagentconnection -n Primary:ITMMTVM103:NT -t r3
    -p
    SERVER=itmmtvm364 PROTOCOL1=IP.PIPE IP_PIPE_PORT=1918
    PROTOCOL2=IP.SPIPE
    IP_SPIPE_PORT=4660 BSERVER=itmmtvm234 BPROTOCOL1=IP.PIPE
    BIP_PIPE_PORT=1918 BPROTOCOL2=IP.SPIPE BIP_SPIPE_PORT=4660
    BACKUP=Y
    
    Content of envCfg.rsp on itmmtvm103
    [CMA_CONFIG]
    FTO_IPPipe_Port=1918
    IPPIPE_Port=1918
    Protocol1=IP.PIPE
    Protocol2=IP.SPIPE
    FTO_Protocol1=IP.PIPE
    IPSPIPE_Host=itmmtvm364
    FTO_Protocol2=IP.SPIPE
    FTO_IPSPipe_Port=4660
    FTO_IPSPIPE_Host=ITMMTVM234
    FTO Flag=Y
    IPSPIPE_Port=4660
    [Override Local Settings]
    
    It's missing the HOSTNAME for IPPIPE_Host and FTO_IPPIPE_Host
    variables.
    
    I see the command complete successfully, but the configuration
    did not change the TEMS to itmmtvm364.
    
    
    Below is a snippet of the
    <CANDLEHOME>/TMAITM6_x64/agentdepot/1433207031396281869191531353
    -R3_CfgInstall.trc file
    
    06-01-2015 20:04:08 [MIN]: CKinConfigApp::DocumentFile:
    -Config-
    CT_CMSLIST=IP.PIPE:itmmtvm234;IP.SPIPE:itmmtvm364;IP.PIPE:;IP.SP
    IPE:ITMM
    TVM234  <==== Wrong IP.PIPE TEMS and missing FTO TEMS
    06-01-2015 20:04:08 [MIN]: CKinConfigApp::DocumentFile:
    -Config-
    KDC_FAMILIES=IP.PIPE PORT:1918 IP.SPIPE PORT:4660 IP use:n SNA
    use:n IP6
    use:n IP6.PIPE use:n IP6.SPIPE use:n
    06-01-2015 20:04:08 [MIN]: CKinConfigApp::DocumentFile:
    -Config-
    CTIRA_HIST_DIR=C:\IBM\ITM\TMAITM6\logs\History\KR3\inst1
    
    There is no problem when specified only PROTOCOL1 and
    BPROTOCOL1.  The
    tacmd setagentconnection would configure the agent correctly
    

Local fix

  • Configure the Agent locally.
    

Problem summary

  • The CLI command setagentconnection does not properly set the
    configuration of a target agent when the user specifies two
    protocols for the Primary and Secondary Servers.  The command
    incorrectly does not set the required parameters to configure
    the agent for the Secondary Server.
    
    
    The component responsible for parsing the user's command
    parameters does not detect the presence of a Secondary Server
    when there are multiple protocols defined for that Secondary
    Server.  The resulting configuration file produced by this
    component does not include the Keywords IPPIPE_Host and
    FTO_IPPIPE_Host and their values.
    

Problem conclusion

  • Changed the command parsing algorithm such that it correctly
    detects each parameter specified by the user when multiple
    Protocols are specified.
    
    The fix for this APAR is contained in the following maintenance
    packages:
    
      | fix pack | 6.3.0-TIV-ITM-FP0006
    

Temporary fix

  • Configure the agent locally, or use the -e (Environment
    Variable) option to set the CT_CMSLIST environment variable for
    the target agent to the desired Server and protocol values.
    
    For example  -e  CT_CMSLIST=<Primary TEMS hostname>:<primary
    protocol>:<primary protocol port>:<secondary
    protocol>:<secondary protocol port>;
    <Secondary TEMS hostname>:<primary protocol>:<primary protocol
    port>:<secondary protocol>:<secondary protocol port>
    

Comments

APAR Information

  • APAR number

    IV75592

  • Reported component name

    TEMS

  • Reported component ID

    5724C04MS

  • Reported release

    630

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2015-07-31

  • Closed date

    2015-08-12

  • Last modified date

    2015-12-10

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    TEMS

  • Fixed component ID

    5724C04MS

Applicable component levels

  • R630 PSY

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"}, "Product":{"code":"SSCTLMP","label":"ITM Tivoli Enterprise Mgmt Server V6"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"630","Edition":""}]

Document Information

Modified date:
10 December 2015