IV41655: VALUES SPECIFIED WITH CMA_CONFIG IN THE RESPONSE FILE NOT EFFECTIVE WHEN UPGRADING EXISTING AGENT.

IBM Tivoli Monitoring 6.2.3 Fix Pack 5 (6.2.3-TIV-ITM-FP0005)

APAR status

• Closed as program error.

Error description

• Environment:
  Windows ONLY. Upgrade of 6.2.2 FP9 NT Agent to 6.2.3 FP1 NT
    Agent.
  
  Problem Description:
    When coding new connection parameters the number of protocols
    coded must match the existing number, or residual values will
    remain. Also the agent must be unconfigured before the
    upgrade. See examples that follow to see how the protocols
    work.
  
    Primary Protocols
    protocol1=IP.SPIPE
    protocol2=IP.PIPE
    FTO protocols
    FTO_protocol1=IP.SPIPE
    FTO-protocol2-IP.PIPE
  
    If only IP.SPIPE is coded in the CMA_CONFIG area of the silent
    install file, the IP-PIPE value is retained. However, if
    protocol2 is coded as protocol2=IP.SPIPE and
    FTO_protocol2=IP.SPIPE then only the IP.SPIPE value is
    retained.
  
  
  Recreate Instructions:
    1. Install 6.2.2 FP9 NT agent and configure as follows:
       Primary TEEMS Connection
       protocol1=IP.SPIPE
       protocol2=IP.PIPE
       Configure Secondary TEMS Connection:
       protocol1=IP.SPIPE
       protocol2=IP.PIPE
    2. Upgrade to 6.2.3 FPx where fix is present silently:
       a. Stop the agent
       b. Unconfigure the agent
       c. Add the following to the upgrade silent file
          [CMA_CONFIG]
          Protocol1=IP.SPIPE
          IPSPIPE_Port=3660
          IPSPIPE_Host=TEMSHOSTNAME
          FTO Flag=Y
          FTO_Protocol1=IP.SPIPE
          FTO_IPSPIPE_Host=FTOTEMSHOSTNAME
    3. If the fix is present only 1 protocol will remain for the
       NT agent.
       If the fix is not present, both IP.SPIPE and IP.PIPE
       protocols will be present.
    4. The problem is in the Agent Defaults area. If the defaults
       are going to be used they should reflect the settings in
       the silent install file.
  

Local fix

• To work around this problem code the CMA section as follows:
  
      [CMA_CONFIG]
      Protocol1=IP.SPIPE
      Protocol2=IP.SPIPE
      IPSPIPE_Port=3660
      IPSPIPE_Host=PRIMARYTEMSHOSTNAME
      FTO Flag=Y
      FTO_Protocol1=IP.SPIPE
      FTO_Protocol2=IP.SPIPE
      FTO_IPSPIPE_Host=SECONDARYTEMSHOSTNAME
  
  By making protocol2 match protocol1 only that protocol will be
  retained.
  

Problem summary

• On Windows, a user provides a [CMA_CONFIG] section in their
  silent install upgrade response file to change connection
  properties of the agents being upgraded. The information in the
  [CMA_CONFIG] section may be processed incorrectly during the
  upgrade. For example, if two protocols currently exist and only
  one is desired, the outcome of the configuration can be
  unpredictable.
  

Problem conclusion

• Code was modified to process the response file during upgrade
  when an agent is reconfigured and the [CMA_CONFIG] section is
  present. The fix unconfigures any Primary agent or instances
  upgraded then configures them using the new protocol
  information.
  
  The fix for this APAR is contained in the following maintenance
  packages:
  | fix pack | 6.2.3-TIV-ITM-FP0005
  

Temporary fix

• Reconfigure the agent and any instances using the Manage Tivoli
  Enterprise Monitoring Services tool after the upgrade completes,
   and configure them with the new protocol information.
  

Comments

APAR Information

• 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

  OMEG DIST INSTA

• Fixed component ID

  5608A41CI

Applicable component levels

• R623 PSY

     UP