DX OI/O2 - Onpremise HOTFIXES
search cancel

DX OI/O2 - Onpremise HOTFIXES

book

Article ID: 277040

calendar_today

Updated On:

Products

DX Operational Intelligence DX Application Performance Management

Issue/Introduction

The following is the list of the latest DX Operational Observability and AIOps HOTFIXES available from Broadcom Support Download site

NOTE: HOTFIXES is cumulative, this means that latest hotfix include all the fixes included in previous hotfixes.

Environment

  • DX Operational Observability 24.2
  • DX Operational Intelligence 23.*, 24.1
  • DX AIOps 23.*,24.*

Resolution

Table of Contents

DX Operational Observability 24.2

24.2-HF02

Date: November 18, 2024

==============
Hotfix images:
==============
doi-ui:24.11.14-24.2.HF01.2594
normalized-alarm:24.11.14-24.2.HF01.144
readserver-doi:24.11.14-24.2.HF01.644
servicealarm:24.11.14-24.2.HF01.250
servicedecoration:24.11.14-24.2.HF01.250
servicemanagement:24.11.14-24.2.HF01.250
servicemetrics:24.11.14-24.2.HF01.251
servicerepo:24.11.14-24.2.HF01.250
servicestatemanager:24.11.14-24.2.HF01.250
tenantmanagement:24.11.14-24.2.HF01.250
topologycreator:24.11.14-24.2.HF01.250

====
fix:
====
Title:
------
Custom SLI health Roll-up to parent service
   
Description:
------------
Currently, SLI health roll-ups were not considered for parent services.
However, with the introduction of the F133992 feature, the roll-up
functionality now includes the parent service even when the child service
health is calculated through SLI. This update ensures that the parent
service is impacted at the same time the SLI health value is emitted,
reducing delays and aligning with the existing service health calculation
workflow.  This process is fully automated, with no manual configuration
required once SLI-based health is linked to a service.
 
Enahncement:
-----------
F133992: Custom SLI health Roll-up to parent service

Updated images:
---------------
servicealarm
servicedecoration
servicemanagement
servicemetrics
servicerepo
servicestatemanager
tenantmanagement
topologycreator


====
fix:
====
Title:
------
Filter Alarms by Alarm Message/Attributes to Impact Service Health
   
Description:
------------
Currently, service health is assessed when an alarm is triggered on a device
that is part of the service. The health calculation is based on the topology
and its state, which is determined by the severity of alarms. By default,
only critical alarms impact service health. However, you can configure the
service to also consider major and minor alarms by selecting the "Override
Health Alarm Severity" checkbox in the Service edit page. If the alarm
severity is set to major, both major and critical alarms will influence the
service health calculation. If the severity is set to minor, critical,
major, and minor alarms will all affect the service health.
 
With this release, you can now filter which alarms impact service health
using alarm filters, also known as alarm queues. Public alarm queues can be
created on the All Alarms page and linked to services, providing detailed
control over which alarms influence service health and enrichment.
Additionally, an alarm queue can be created for alarms not associated with
any device and linked to the service to include those alarms in the service
health calculation.

 
Enahncement:
------------
F116821: Filter Alarms by Alarm Message/Attributes to Impact Service Health
 
Updated images:
---------------
doi-ui
doi-readserver
normalized-alarm
servicealarm
servicedecoration
servicemanagement
servicemetrics
servicerepo
servicestatemanager
tenantmanagement
topologycreator

24.2-HF01

Date: November 18, 2024

==============
Hotfix images:
==============
doi-ui:24.11.14-24.2.HF01.2594
normalized-alarm:24.11.14-24.2.HF01.144
readserver-doi:24.11.14-24.2.HF01.644
servicealarm:24.11.14-24.2.HF01.250
servicedecoration:24.11.14-24.2.HF01.250
servicemanagement:24.11.14-24.2.HF01.250
servicemetrics:24.11.14-24.2.HF01.251
servicerepo:24.11.14-24.2.HF01.250
servicestatemanager:24.11.14-24.2.HF01.250
tenantmanagement:24.11.14-24.2.HF01.250
topologycreator:24.11.14-24.2.HF01.250

====
fix:
====
Title:
------
Custom SLI health Roll-up to parent service
   
Description:
------------
Currently, SLI health roll-ups were not considered for parent services.
However, with the introduction of the F133992 feature, the roll-up
functionality now includes the parent service even when the child service
health is calculated through SLI. This update ensures that the parent
service is impacted at the same time the SLI health value is emitted,
reducing delays and aligning with the existing service health calculation
workflow.  This process is fully automated, with no manual configuration
required once SLI-based health is linked to a service.
 
Enhancement:
-----------
F133992: Custom SLI health Roll-up to parent service

Updated images:
---------------
servicealarm
servicedecoration
servicemanagement
servicemetrics
servicerepo
servicestatemanager
tenantmanagement
topologycreator


====
fix:
====
Title:
------
Filter Alarms by Alarm Message/Attributes to Impact Service Health
   
Description:
------------
Currently, service health is assessed when an alarm is triggered on a device
that is part of the service. The health calculation is based on the topology
and its state, which is determined by the severity of alarms. By default,
only critical alarms impact service health. However, you can configure the
service to also consider major and minor alarms by selecting the "Override
Health Alarm Severity" checkbox in the Service edit page. If the alarm
severity is set to major, both major and critical alarms will influence the
service health calculation. If the severity is set to minor, critical,
major, and minor alarms will all affect the service health.
 
With this release, you can now filter which alarms impact service health
using alarm filters, also known as alarm queues. Public alarm queues can be
created on the All Alarms page and linked to services, providing detailed
control over which alarms influence service health and enrichment.
Additionally, an alarm queue can be created for alarms not associated with
any device and linked to the service to include those alarms in the service
health calculation.

 
Enhancement:
------------
F116821: Filter Alarms by Alarm Message/Attributes to Impact Service Health
 
Updated images:
---------------
doi-ui
doi-readserver
normalized-alarm
servicealarm
servicedecoration
servicemanagement
servicemetrics
servicerepo
servicestatemanager
tenantmanagement
topologycreator

 

DX Operational Intelligence 24.1

 

24.1-OI-HF05

Date: September 16, 2024

==============
Hotfix images:
==============
alarmpreprocessor:24.06.81
alarmscausality:24.07.04.327
anomalydetection:24.06.133
cpa-ng:24.06.877
cpa-projection:24.06.445
doi-inspector:24.06.25.66
doi-ui:24.08.28-24.1.HF03.1899
doiplatelemetry:24.06.77
dp-ng-nim-sm-api:24.06.25.71
dp-ng-nim-sm:24.06.25.71
incidentmanagement:24.06.25.247
incidentmanagementpollingengine:24.06.25.247
integrationgateway:24.06.25.247
la-alarm-scheduler-processor:24.4.1.3
la-readserver:24.4.1.5
laonboardingapi:24.4.1.3
lautils:24.4.1.4
logenrichment:24.4.1.3
logtelemetry:24.4.1.6
metric-config:24.09.11-24.1.HF04.158
metric-metadata:24.06.100
nass-indexer:24.06.27
normalized-alarm:24.06.28.91
notify-filter:24.06.25.38
odc-connector:24.4.4.198
odc-lifecyclemgmt:24.4.3.82
pi-projection:24.06.5
readserver-doi:24.06.28.438
schedule-policy-executor:24.06.25.28
schedule-policy-poller:24.06.25.28
servicealarm:24.06.433
servicedecoration:24.06.433
servicemanagement:24.06.443
servicemetrics:24.06.435
servicerepo:24.06.435
servicestatemanager:24.06.433
sliaggregation:24.08.28-24.1.HF03.80
tenantmanagement:24.06.433
topology-processor:24.09.16-24.1.HF05.203
topologycreator:24.06.433

====
fix:
====
Title:
------
Memory leak reported in Jackson 2.17.0
 
Description:
------------

Some of the components are reporting memory leak due to a known defect in
Jackson library with 2.17.0 version:

https://github.com/FasterXML/jackson-databind/issues/4500

The impact is that the services will get restarted with OOM error or
components will malfunction. Sometimes it is observed that the pod didn't
restart, but due to not having enough memory, the component did not
functionally process the request as intended.

Defects:
--------
DE601659 - doi-servicealarm pod restarted with hazlecast  exceptions
DE602460 - DOI NAS common pipeline memory heap usage 

Updated images:
---------------
alarmpreprocessor
alarmscausality
anomalydetection
cpa-ng
cpa-projection
doi-inspector
doi-ui
doiplatelemetry
dp-ng-nim-sm-api
dp-ng-nim-sm
incidentmanagement
incidentmanagementpollingengine
integrationgateway
la-alarm-scheduler-processor
la-readserver
laonboardingapi
lautils
logenrichment
logtelemetry
metric-config
metric-metadata
nass-indexer
normalized-alarm
notify-filter
odc-connector
odc-lifecyclemgmt
pi-projection
readserver-doi
schedule-policy-executor
schedule-policy-poller
servicealarm
servicedecoration
servicemanagement
servicemetrics
servicerepo
servicestatemanager
sliaggregation
tenantmanagement
topology-processor
topologycreator


====
fix:
====
Title:
------
Handling Spectrum maintenance alarms with isManaged attribute

Description:
------------
Added support for handling maintenance mode from the Spectrum product using
the isManaged attribute.

Defects:
--------
US970313 - Handling Spectrum maintenance alarms with isManaged attribute

Updated images:
---------------
readserver-doi
normalized-alarm


====
fix:
====
Title:
------
Situations pod has null pointer and string conversion errors and new situations
are not forming

Description:
------------
For some APM alerts there can be null pointer and string conversion errors in
the Situations pod. With this fix situations pod should be able to successfully
process these alerts and generate new situations.

Defects:
--------
DE607812 - Situations pod has null pointer and string conversion errors and new
           situations are not forming.

Updated images:
---------------
alarmscausality


====
fix:
====
Title:
------
User is unable to override the compaction rule from API.

Description:
------------
Currently Topology Processor is failing to override the compaction rule.
Fix will allow the user to override the compaction rule.

Defects:
--------
DE608047 : How to reconfigure topology compaction to use Hostname and FQDN
           for UIM Inventory.

Updated images:
----------------------
topology-processor


====
fix:
====
Title:
------
The service_health metrics are not available in the SLI calculation.

Description:
------------
The service health metrics are expressed as a percentage, which means they
do not fall into a numeric category. As a result, service health metrics
were not included in the SLI calculation. 

As part of this fix, a provision has been made in the SLI calculation logic
to process service_health metrics.

Defects:
--------
DE613685 : Allow service_health metric rollup for SLI computation

Updated images:
----------------------
doi-ui
metric-config
sliaggregation


====
fix:
====
Title:
------
SLI Metric filter in UI is not working when using metadata attribute filter.

Description:
------------
SLI metric filter is not working when using metric metadata attribute in
combination with Source/Metric filters. This results in an incorrect metric
list when refining metrics at an individual SLI level.

Defects:
--------
DE614682: SLI Metric filter not working after applying 24.1 hotfix 03

Updated images:
----------------------
metric-config


====
fix:
====
Title:
------
Missing Edges/Relationships between the compacted vertices.

Description:
------------
It was noted that in certain cases, the edges between the compacted vertices
are missing.  Fix will create the missing edges between the compacted
vertices.

Defects:
--------
DE610543: Devices links/pipes are missing in DX OI Topology view compared
          with Spectrum Topology

Updated images:
----------------------
topology-processor

 

DX Operational Intelligence 23.3

 

23.3-OI-HF02

Date: Feb 28, 2024
 
==============
Hotfix images:
==============
dxi-adminui:23.12.14.3389-23.3.HF01
doi-adminui:23.3.HF01.366
doi-readserver:24.2.27-23.3.HF02.240
normalized-alarm:24.1.19-23.3.HF01.48
 
 
====
fix:
====
Title:
------
"Header Too Large" error message for LDAP/SAML users.
 
Description:
------------
An http response error message stating 'Header Too Large' may be generated
when navigating into the 'DX Operational Intelligence' application tile
from cloudmanagement when the user's groups are larger than an expected
size.
 
This fix now allows the successful launch of OI and AXA products from
cloudmanagement without experiencing the above error message.
 
Defects:
--------
DE585079 - Error 400 /oi/v2/sa/settings/get AND 'Header Too Large' message
DE583276 - DX platform not allowing user to navigate for LDAP users
 
Updated images:
---------------
dxi-adminui
doi-adminui
 
 
====
fix:
====
Title:
------
Some OI Metric Browser graphs only show a single data point when expected
to see a data series.
 
Description:
------------
Within the OI Metric Browser, a data point only shows if the cursor happens
to sit over a data point.  The problem affects some metrics which have been
ingested from a connector.  When the mouse is moved away from the graph, the
data point goes away resulting in an empty graph.
 
Defects:
--------
DE585456 - Some graphs only show single data points, we expect to see a
           data series
 
Updated images:
---------------
doi-readserver
 
 
====
fix:
====
Title:
------
Unable to assign a user to an alarm, LDAP users are not populated in the
"Assign to" listbox
 
Description:
------------
For a tenant configured with LDAP, unable to assign an alarm to a user in
DX Operational Intelligence.
 
This fix allows assignment of user to an alarm.
 
Defects:
--------
DE587215 - Unable to assign a user to an alarm, LDAP users are not populated
           in the "Assign to" listbox
 
Updated images:
---------------
doi-readserver
 
 
====
fix:
====
Title:
------
Duplicate tenant entries are created in ao_dxi_tenants elasticsearch index
 
Description:
------------
For tenants in ao_dxi_tenants index, duplicate entries are created on
doi-readserver restart. This may cause doi-readserver not startup
successfully.
 
Defects:
--------
DE585640 - Duplicate tenant entries in dxi_tenants index
 
Updated images:
---------------
doi-readserver
 
 
====
fix:
====
Title:
------
Refresh Normalized Alarm Service externalId and correlated external Id
cache periodically
 
Description:
------------
The current cache in normalized-alarm service is static and loaded at
startup time.  The cache is refreshed upon an update to a correlated
externalId (such as addition or removal notification from TAS).
 
In some cases, the TAS notification is not sent resulting in NAS having
old references to correlated externalIds which causes downstream service
enrichment failures.
 
To handle this scenario, refresh the normalized-alarm service cache
periodically based upon a configurable time interval.
 
Defects:
--------
US916039 - Refresh Normalized Alarm Service externalId and correlated
           external Id cache periodically
 
Updated images:
---------------
normalized-alarm
 
 
====
fix:
====
Title:
------
Unable to export DX OI Alarms to Excel
 
Description:
------------
When trying to export the DX OI Alarms to Excel in the UI, the error
is shown. This can happen if installed using UID other than 1010.
 
This fix allows to successfully export DX OI Alarms to Excel.
 
Defects:
--------
DE592462 - Unable to export DX OI Alarms to Excel
 
Updated images:
---------------
doi-readserver
 
 
 
 
 

DX Operational Intelligence 23.2

23.2-OI-HF02

Date: Jan 08, 2024
 
==============
Hotfix images:
==============
dxi-adminui:23.12.05.3332-23.2.HF01
doi-adminui:23.2.1233
doi-readserver:23.2.HF02.496
 
 
====
fix:
====
Title:
------
"Header Too Large" error message for LDAP/SAML users.
 
Description:
------------
An http response error message stating 'Header Too Large' may be generated
when navigating into the 'DX Operational Intelligence' application tile
from cloudmanagement when the user's groups are larger than an expected
size.
 
This fix now allows the successful launch of OI and AXA products from
cloudmanagement without experiencing the above error message.
 
Defects:
--------
DE585079 - Error 400 /oi/v2/sa/settings/get AND 'Header Too Large' message
DE583276 - DX platform not allowing user to navigate for LDAP users
 
Updated images:
---------------
dxi-adminui
doi-adminui
 
 
====
fix:
====
Title:
------
Some OI Metric Browser graphs only show a single data point when expected
to see a data series.
 
Description:
------------
Within the OI Metric Browser, a data point only shows if the cursor happens
to sit over a data point.  The problem affects some metrics which have been
ingested from a connector.  When the mouse is moved away from the graph, the
data point goes away resulting in an empty graph.
 
Defects:
--------
DE585456 - Some graphs only show single data points, we expect to see a
           data series
 
Updated images:
---------------
doi-readserver
 
 
====
fix:
====
Title:
------
Unable to assign a user to an alarm, LDAP users are not populated in the
"Assign to" listbox
 
Description:
------------
For a tenant configured with LDAP, unable to assign an alarm to a user in
DX Operational Intelligence.
 
This fix allows assignment of user to an alarm.
 
Defects:
--------
DE587215 - Unable to assign a user to an alarm, LDAP users are not populated
           in the "Assign to" listbox
 
Updated images:
---------------
doi-readserver

 

Powered by Wolken Software