IBM Support

OA49273: TEBS: PORT POOLS FOR LOOPBACK DEVICE SOCKET ALLOCATIONS

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as new function.

Error description

  • The KDE_TRANSPORT POOL: keyword does not permit configuration of
    socket port pools on the LOOPBACK device. To accommodate this ,
    a new environment variable, KDE_LOOPBACK_POOL , can be used to
    configure a pool of available ports associated with the
    loopback device from which all Tivoli Monitoring socket
    requests are satisfied.  The semantics of KDE_LOOPBACK_POOL are
    the same as the KDE_TRANSPORT POOL: keyword as it applied to
    the loopback device but the syntax differs. The usage is
    KDE_LOOPBACK_POOL=NNNNN-KKKKK , where NNNNN is the start of the
    port pool range, KKKKK is the end of the port pool range, and
    KKKKK - NNNNN <= 1024 .  KDE_LOOPBACK_POOL resides in the same
    Tivoli product configuration file as does KDE_TRANSPORT.
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All ITM/ENGINE users.                        *
    ****************************************************************
    * PROBLEM DESCRIPTION: TIVOLI MONITORING CONFIGURATION OF      *
    *                      SOCKET PORT POOLS IS NOT PERMITTED ON   *
    *                      THE LOOPBACK DEVICE.                    *
    ****************************************************************
    * RECOMMENDATION: Apply the PTF.                               *
    ****************************************************************
    The Tivoli Monitoring KDE_TRANSPORT environment variable
    'POOL:' keyword does not permit configuration of socket port
    pools on the LOOPBACK device.
    
    In order for this APAR to be properly implemented in your
    environment, a new environment variable has been added.  See
    the "Install Actions" section of the APAR conclusion for
    more details.
    

Problem conclusion

Temporary fix

Comments

  • Install Actions:
    Code has been added to support a new Tivoli Monitoring
    environment variable, KDE_LOOPBACK_POOL.  KDE_LOOPBACK_POOL
    can be used to configure a pool of available ports
    associated with the loopback device from which all Tivoli
    Monitoring socket requests are satisfied.
    
    The semantics of KDE_LOOPBACK_POOL are the same as the
    KDE_TRANSPORT environment variable 'POOL:' keyword as it
    applied to the loopback device but the syntax differs. The
    usage is KDE_LOOPBACK_POOL=NNNNN-KKKKK , where NNNNN is the
    start of the port pool range, KKKKK is the end of the port
    pool range, and KKKKK - NNNNN <= 1024 .  KDE_LOOPBACK_POOL
    resides in the same Tivoli product configuration file as
    does KDE_TRANSPORT.
    

APAR Information

  • APAR number

    OA49273

  • Reported component name

    CT/ENGINE

  • Reported component ID

    5608A41CE

  • Reported release

    630

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2015-11-03

  • Closed date

    2015-12-01

  • Last modified date

    2016-01-04

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

    OA48117

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

Modules/Macros

  •    KDELIB   KDE1LNKP
    

Fix information

  • Fixed component name

    CT/ENGINE

  • Fixed component ID

    5608A41CE

Applicable component levels

  • R630 PSY UA79952

       UP15/12/16 P F512

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSC6ML7","label":"IBM Tivoli OMEGAMON CT\/ENGINE"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"630","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
04 January 2016