IBM Support

IV75063: ITNM DISCOVERY AND META DATA AUDIT TOOL

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Version and Platform independent.
    
    The requirement(Discovery accuracy) of this tool is to shed
    light on areas for improvement and to highlight problems where
    applicable.
    
    As an example, a) the interface missing data (for e.g. ifDescr,
    sysNam etc) and b) how do we fix to prevent missing data.
    It could be either the device just doesn't have the data or we
    can increase snmp retries and timeouts for a specific subnet or
    network segement with least bandwidth links.
    
    Using Meta Data Audit tool, one should be able to:
    
    1. Gain insight into whether there's any meta-data about
    devices or devices with missing data. If there's missing meta
    data, it should generate SQL INSERT templates to help fill any
    gaps (e.g. for successful export of DLA Adapter) as needed.
    
    2. Display the class hierarchy on the command line with the
    number of devices in each class; with a view to identifying
    opportunities for better classify devices.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All users.                                                   *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Implement a new ITNM Discovery & Meta Data Audit Tool -      *
    * Version and Platform independent.                            *
    *                                                              *
    * The requirement(Discovery accuracy) of this tool is to shed  *
    * light on areas for improvement and to highlight problems     *
    * where                                                        *
    * applicable.                                                  *
    *                                                              *
    * As an example, a) the interface missing data (for e.g.       *
    * ifDescr,                                                     *
    * sysNam etc) and b) how do we fix to prevent missing data.    *
    * It could be either the device just doesn't have the data or  *
    * we                                                           *
    * can increase snmp retries and timeouts for a specific subnet *
    * or                                                           *
    * network segement with least bandwidth links.                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * The following fixpacks will contain the fix:                 *
    * | fix pack | 3.9.0-ITNMIP-FP0005                             *
    * | fix pack | 4.1.1-ITNMIP-FP0002                             *
    ****************************************************************
    

Problem conclusion

  • Develop a new script in
    $NCHOME/precision/scripts/perl/scripts/itnmMetaDiscoAudit.pl.
    
    This script (ITNM Discovery & Meta Data Audit Tool) helps -
    1. Gain insight into whether there's any meta-data about devices
    or devices with missing data. If there's missing meta data,
    it'll generate SQL INSERT templates to help fill any gaps as
    needed.
    2. Display the class hierarchy on the command line with the
    number of devices in each class; with a view to identifying
    opportunities for better classify devices.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV75063

  • Reported component name

    TIV NETWK MGR I

  • Reported component ID

    5724S4500

  • Reported release

    390

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-07-13

  • Closed date

    2015-07-31

  • Last modified date

    2015-07-31

  • 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 PSN

       UP

  • R390 PSY

       UP

  • R411 PSN

       UP

  • R411 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:
31 July 2015