IBM Support

IZ63639: HUB TO RTEMS CONNECT FAILS AFTER RTEMS EPHEMERAL ADDR CHANGE

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When the addressing mode of a remote TEMS changes and the HUB
    is not
      re-cycled with the remote TEMS to affect that change, the HUB
    fails
      to communicate back to the remote TEMS for distributed
    requests.  An
      address mode change is defined as the addition or removal of
      EPHEMERAL:Y on the KDE_TRANSPORT statement of the remote TEMS
    config.
    
    Detailed Recreation Procedure:
      Configure a HUB, remote TEMS and one agent reporting to the
    remote
      TEMS.  Configure the remote TEMS with the EPHEMERAL:Y keyword
    on
      the remote TEMS KDE_TRANSPORT environment variable.  Use the
    TEPS
      to distribute a request to the agent connected  to that remote
    TEMS.
      Assure the situation fires and data is seen at the TEPS.
      Reconfigure the remote TEMS by removing the EPHEMERAL:Y
    keyword.
      When restarting the remote TEMS with this addressing mode
    change,
      do NOT re-cycle the HUB.  Perform the TEPS query to the agent
    on
      the remote TEMS.  The query will fail.  The HUB TEMS RAS1 log
    has
      this message assocuated with the TEPS query failure:
      RUL11STM - Remote request communication failed ....
      and the message will contain the old, ephemeral:y address,
      0.0.0.1 for example.
    

Local fix

  • Recycle the TEMS
    

Problem summary

  • When the addressing mode of a remote management server changes
    and the HUB management server is not re-cycled with the remote
    management server to affect that change, the HUB management
    server may fail to communicate back to the remote management
    server for distributed requests.
    
    The following message may appear in the management server RAS1
    trace log:
    
       RUL11STM - Remote request communication failed ....
    

Problem conclusion

  • The problem occurs because the HUB management server retains the
    addressing information related to the remote management server
    until the HUB management server is recycled.
    
    The communication code has been altered to cause the old address
    information associated with the remote management server to be
    removed from the HUB management server.
    
    
    The fix for this APAR is included in the following maintenance
    vehicle:
        | fix pack | 6.2.1-TIV-ITM-FP0002
        | fix pack | 6.2.2-TIV-ITM-FP0002
    

Temporary fix

  • Recycle the HUB management server.
    

Comments

APAR Information

  • APAR number

    IZ63639

  • Reported component name

    TEMS

  • Reported component ID

    5724C04MS

  • Reported release

    610

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-10-21

  • Closed date

    2010-02-12

  • Last modified date

    2010-06-02

Fix information

  • Fixed component name

    TEMS

  • Fixed component ID

    5724C04MS

Applicable component levels

  • R621 PSY

       UP

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSCTLMP","label":"ITM Tivoli Enterprise Mgmt Server V6"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"610","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
02 June 2010