IBM Support

IV31296: ASSOCADDRESS AGENT TO USE IPADENTADDR VALUE INSTEAD OF THE INDEX FOR THE IPADDRTABLE ENTRY.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Product: Tivoli Network Manager
    Version: 3.8, 3.9
    Component: AssocAddress Agent
    
    Symptom:
    
    The AssocAddress agent use the index of the entry in ipAddrTable
    and according to RFC1213, the index of ipAddrTable should be
    ipAdEntAddr.
    However, in some Alteon ADC and VADC devices, the index of
    ipAddrTable is having a different value than ipAdEntAddr, i.e.
    ipAdEntAddr with index IP.IP.IP.112 is having IP.IP6.IP.114 as
    it's value: ipAdEntAddr.IP.IP.IP.112: IP.IP.IP.114
    
    
    
    Resolution:
    Update the AssocAddress agent to use the actual ipAdEntAddr
    value, instead of using the index of the ipAddrTable entry.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * ITNM-IP 3.9 on all platform, i.e. Windows, Linux, Solaris    *
    * and AIX                                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Unable to discovery Redware Alteon Application Delivery      *
    * Controller (ADC) and VADC (Virtual ADC) properly             *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to ITNM-IP | fix pack | 3.9.0-ITNMIP-FP0004          *
    * | fix pack | 3.8.0-ITNMIP-FP0007                             *
    ****************************************************************
    The AssocAddress agent use the index of the entry in ipAddrTable
    and according to RFC1213, the index of ipAddrTable should be
    ipAdEntAddr. However, in this particular Aldeon ADC device, the
    index of ipAddrTable is having a different value than
    ipAdEntAddr, i.e. ipAdEntAddr with index x.x.x.112 is having
    x.x.x.114 as it's value:
    
    ipAdEntAddr.x.x.x.112: x.x.x.114
    

Problem conclusion

  • Introduce a new option called UseSnmpIpValue for AssocAddres
    agent to use the actual ipAdEntAddr value instead of using the
    index of the ipAddrTable entry, if the device's matches the OID
    filter defined in this flag. By default, the agent will use the
    IP value from ipAdEntAddr column for Alteon devices.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV31296

  • Reported component name

    TIV NETWK MGR I

  • Reported component ID

    5724S4500

  • Reported release

    380

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-11-05

  • Closed date

    2013-05-16

  • Last modified date

    2013-07-29

  • 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

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

Document Information

Modified date:
29 July 2013