IBM Support

IV40185: DEVICES MISSING COLLECTOR DISCOVERY COLLECTORADDRESSTRANSLATION COLLECTORADDRESSTRANSLATION

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • ITNM 3.9 fp3
    Customer has collector only discovery.
    Missing device is in CollectorDetails.returns
    seen in CollectorInventory.returns, but is missing an entry
     for it's own IP address in the
    
    'm_ExtraInfo' => {
                                 'm_AssocAddress' => [
    
    section.
    
    so ip is not found here
    select * from translations.collectorUniqueToWorkAddress where
    m_WorkAddress =
    or
    select * from translations.collectorUniqueToWorkAddress where
    m_UniqueAddress=
    
    and missing from scratchTopology.
    

Local fix

  • stitcher is available updated to process CollectorInventory
    that is missing it's own IP.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Users use collector discovery.                               *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Devices missing when using collector discovery only. Missing *
    * device is in CollectorDetails.returns                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Apply updated CollectorAddressTranslation.stch stitcher.     *
    *                                                              *
    * The following fixpacks will contain the fix:                 *
    * | fix pack | 3.9.0-ITNMIP-FP0004                             *
    ****************************************************************
    

Problem conclusion

  • The CollectorAddressTranslation.stch stitcher assumes that the
    initial discovered IP (m_UniqueAddress) which was defined in
    collector would always appears in the m_AssocAddress list. (see
    collector.associatedAddresses which is created and populated by
    that stitcher). The IP may not be in m_AssocAddress list.
    To fix that stitcher to make sure it adds the m_UniqueAddess to
    collector.associatedAddresses if it doesn't see it in the
    m_AssocAddress list.
    
    The following fixpacks will contain the fix:
    | fix pack | 3.9.0-ITNMIP-FP0004
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV40185

  • Reported component name

    TIV NETWK MGR I

  • Reported component ID

    5724S4500

  • Reported release

    390

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-04-18

  • Closed date

    2013-08-09

  • Last modified date

    2013-08-09

  • 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

    TIV NETWK MGR I

  • Fixed component ID

    5724S4500

Applicable component levels

  • R390 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSSHRK","label":"Tivoli Network Manager IP Edition"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.9","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
09 August 2013