IBM Support

IJ17406: CHANGES IN VCENTER AND COMMON DSM CAN CAUSE TLS SYSLOG LOG SOURCE LEGACY CONFIGURATION UI PAGE TO NOT LOAD CORRECTLY

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

  • It has been identified that changes made in the Vcenter and
    Common DSM can cause the TLS Syslog Log Source configuration
    page in the QRadar User Interface to not load as expected.
    The affected Log Sources continue to function normally but
    users are not able to edit or add new TLS log sources with the
    legacy User Interface.
    

Local fix

  • 1) Where possible, use the Log Source Managment App to add and
    edit TLS configurations.
    2) There is another possible workaround that is suggested to be
    performed by QRadar Support. Please log a Support case if
    needed.
    

Problem summary

  • ERROR DESCRIPTION:
    It has been identified that changes made in the Vcenter and
    Common DSM can cause the TLS Syslog Log Source configuration
    page in the QRadar User Interface to not load as expected.
    The affected Log Sources continue to function normally but
    users are not able to edit or add new TLS log sources with the
    legacy User Interface.
    

Problem conclusion

  • Resolves an issue in the VMware vCenter Device Support Module
    (DSM) to select the default protocol option for new log sources
    created by administrators. This release also resolves a problem
    where the VMware vCenter DSM could impact what was protocol
    options were displayed to users creating new log sources.
    Several users reported that TLS Syslog was missing from the
    Protocol drop-down list when creating non-VMware log sources as
    described in APAR IJ17406. Users who do not have the VMware
    vCenter DSM installed or do selective DSM installs can also get
    this fix by updating to the latest version of DSM Common to
    resolve APAR IJ17406
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ17406

  • Reported component name

    QRADAR SOFTWARE

  • Reported component ID

    5725QRDSW

  • Reported release

    731

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-07-03

  • Closed date

    2019-07-18

  • Last modified date

    2019-07-18

  • 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

    QRADAR SOFTWARE

  • Fixed component ID

    5725QRDSW

Applicable component levels

[{"Business Unit":{"code":"BU048","label":"IBM Software"}, "Product":{"code":"SSBQAC","label":"IBM Security QRadar SIEM"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"731","Edition":""}]

Document Information

Modified date:
18 July 2019