IBM Support

IJ14411: VMWARE DISCOVERY DOESN'T WORK WHEN STRICT MODE IS ENABLED

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

  • Problem Description: When strict mode is enabled i.e. when
    property com.ibm.jsse2.sp800-131=strict is set, Vmware discovery
     fails with the error "2018-12-26 12:15:46,291 [Thread: 0]
    2018122612130014#VmwareEsxiComputerSystemSensor-10.68.6.70 DEBUG
     vmware.VMConnectUtil - getDocument
    https://10.68.6.70:443/sdk/vimServi
    
    ce?wsdl
    
    2018-12-26 12:15:46,334 [Thread: 0]
    2018122612130014#VmwareEsxiComputerSystemSensor-10.68.6.70 DEBUG
    sensor.VmwareEsxiComputerSystemSensor - Discovery failed.
    
    java.lang.IllegalArgumentException: Only TLS1.2 protocol can be
    enabled in SP800_131 strict mode".
    
    As a part of this APAR, changes are done in the code to set up
    connection using only TLSv1.2 when strict mode is enabled.
    

Local fix

  • n/a
    

Problem summary

  • When strict mode is enabled i.e. when the
    property:
    com.ibm.jsse2.sp800-131=strict
    is set, Vmware discovery fails with the error :
    2018-12-26 12:15:46,291 [Thread: 0]
    2018122612130014#VmwareEsxiComputerSystemSensor-10.68.6.70 DEBUG
     vmware.VMConnectUtil - getDocument
    https://10.68.6.70:443/sdk/vimService?wsdl
    2018-12-26 12:15:46,334 [Thread: 0]
    2018122612130014#VmwareEsxiComputerSystemSensor-10.68.6.70 DEBUG
    sensor.VmwareEsxiComputerSystemSensor - Discovery failed.
    java.lang.IllegalArgumentException: Only TLS1.2 protocol can be
    enabled in SP800_131 strict mode".
    As a part of this APAR fix, changes are done to set up
    connection using only TLSv1.2 when strict mode is enabled.
    

Problem conclusion

  • The fix for this APAR is contained in the following maintenance
    packages:
    | Fix Pack | 7.3.0-TIV-ITADDM-FP0007
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ14411

  • 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

    2019-03-06

  • Closed date

    2019-05-17

  • Last modified date

    2019-05-17

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Modules/Macros

  • 999
    

Fix information

  • Fixed component name

    APP DEPENDENCY

  • Fixed component ID

    5724N5500

Applicable component levels

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSPLFC","label":"Tivoli Application Dependency Discovery Manager"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"730","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
17 May 2019