IBM Support

IV89191: F5 DEVICE IS NOT STITCHED TO HUAWEI NE40E ROUTER USING LLDP ON CROSS DOMAIN.

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • In an environment that has a F5 hardware load balancer
    connected  to a Huawei NE40E router. Both device has been
    enabled snmp discovery, when trying to get these two elements
    stitched via the LLDP protocol(cross domain) and have enabled
    both DefaultLLDP and  LLDP agents in ITNM, also confirmed that
    LLDP has been enabled  on the Huawei router and it can see the
    F5 as it's LLDP neighbor.
    
    However F5 Device is not stitched to Huawei NE40E router using
    LLDP.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Network Manager, all platforms, specifically when            *
    * discovering networks using LLDP                              *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * The layer 2 topology may be incorrect because LLDP links can *
    * be left unresolved if the device at one end of an LLDP link  *
    * isn't discovered by an LLDP agent.                           *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to  fix pack 4.2.0-ITNMIP-FP0002                     *
    ****************************************************************
    

Problem conclusion

  • Fied in fix pack 4.2.0-ITNMIP-FP0002.
    The LLDP stitcher can now use non-LLDP data to resolve links
    (e.g. sysName). This results in a more complete layer 2 topology
    in cases where the LLDP agents may not have discovered both ends
    of a link.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV89191

  • Reported component name

    TIV NETWK MGR I

  • Reported component ID

    5724S4500

  • Reported release

    420

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-09-16

  • Closed date

    2016-10-13

  • Last modified date

    2016-10-13

  • 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

  • R420 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":"420","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
13 October 2016