IBM Support

IV22997: DISCOVERY CRASHED IN PHASE 4 DUE TO THE HUGE CISCOBGPTELNET RETURNS.(IV22977)

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Basic issue is when we return device A we include all the local
    neighbour records separately and similarly for the remote
    neighbours. This was by design to simplify processing.  e.g. if
    we have device A with four interfaces, each with 2 neighbours
    we'd return 13 records.
    
     A
     A.int1
     A.int1.remA
     A.int1.remB
     A.int2
     A.int2.remC
     A.int2.remD
     A.int3
     A.int3.remE
     A.int3.remF
     A.int4
     A.int4.remG
     A.int4.remH
    
     The problem is there are a lot of BGP which has a lot of BGP
    information in the local neighbour record and quite a few remote
    neighbours. This means that for each remote neighbor the BGP
    data is needlessly repeated. e.g.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Users with BGP agents enabled.                               *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * DISCOVERY CRASHED IN PHASE 4 DUE TO THE HUGE CISCOBGPTELNET  *
    * RETURNS.                                                     *
    * Basic issue is when we return device A we include all the    *
    * local neighbour records separately and similarly for the     *
    * remote                                                       *
    * neighbours. This was by design to simplify processing.       *
    *                                                              *
    * The problem is if there are a lot of BGP which has a lot of  *
    * BGP information in the local neighbour record and quite a    *
    * few remote                                                   *
    * neighbours. This means that for each remote neighbor the BGP *
    * data is needlessly repeated.                                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Apply testfix for BGP agents libraries or upgrade to fixpack *
    * 2.                                                           *
    * | fix pack | 3.9.0-ITNMIP-FP0002                             *
    ****************************************************************
    

Problem conclusion

  • If an interface has multiple remoteNbrs, trim the BGP data in
    local neighbour on all the remote neighbour records other than
    the first one on a particular local neighbour.
    
    The following fixpacks will contain the fix:
    | fix pack | 3.9.0-ITNMIP-FP0002
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV22997

  • Reported component name

    NC/PREC DISCOVY

  • Reported component ID

    5724O52DS

  • Reported release

    390

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-06-13

  • Closed date

    2012-06-21

  • Last modified date

    2012-06-21

  • 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

    NC/PREC DISCOVY

  • Fixed component ID

    5724O52DS

Applicable component levels

  • R390 PSN

       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:
21 June 2012