IBM Support

IJ45573: ON TADDM FP9, AFTER VIRTUAL CENTER SERVER DISCOVERY, FQDN IS MISSING FOR THE ESX SERVER WHICH RUNNING ON A DELL INC, POWEREDGE

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

  • On TADDM FP9 ,After Virtual Center Server discovery, FQDN values
    coming as blank for the ESX server which running on a Dell Inc,
    PowerEdge host.
    And due to which the display name for the ESX server read as
    "Dell Inc.:PowerEdge R730:<serial number>" where the end is the
    serial number.
    
    In sensor logs we did not found any specific error/exception
    there.
    On DMP only for ESX servers ,the FQDN values shown as blank and
    wrong display name created like this "Dell Inc.:PowerEdge
    R730:<serial number>"
    
    After analysis of relevant code module , we found FQDN values
    getting set in the result object on the basis of few conditions
    
    and it seems condition did not satisfy , due to which FQDN did
    not set.
    
    In order to resolve this problem,
    we need to modify the condition statement according to the
    Client ESX server details ,so FQDN set properly for their ESX
    servers.
    

Local fix

  • N/A
    ###########################################
    

Problem summary

  •  With TADDM 7.3.0.9 for the VirtualCenter
    Server discovery, FQDN values discovered as blank for the ESX
    server running on a Dell Inc, PowerEdge host. As a result On DMP
    for ESX servers the FQDN values are shown as blank and due to
    this the wrong display name is created, for example:
    "Dell Inc.:PowerEdge R730:<serial number>"
    

Problem conclusion

  •  Code has been corrected to modify the
    condition in ESX discovery code so that the FQDN attrribute
    is correctly discovered and set for ESX servers.
    The fix for this APAR is contined in the following maintenance
    packages: | Fix Pack| 7.3.0-TIV-ITADDM-FP0011
    

Temporary fix

  •  n/a
    

Comments

APAR Information

  • APAR number

    IJ45573

  • Reported component name

    APP DEPENDENCY

  • Reported component ID

    5724N5500

  • Reported release

    730

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2023-02-23

  • Closed date

    2023-06-01

  • Last modified date

    2023-06-01

  • 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

    APP DEPENDENCY

  • Fixed component ID

    5724N5500

Applicable component levels

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSPLFC","label":"Tivoli Application Dependency Discovery Manager"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"730","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
02 June 2023