Transitioning from 25.x to 26.1 On-Premises

Products

• DX Operational Intelligence
• DX Operational Observability
• DX Application Performance Management

Issue/Introduction

What are the key differences from DX Operational Observability 25.1 and 26.1 on premise releases regarding technologies, architecture and features?

Environment

DX O2 25.1 on premise

DX O2 26.1 on premise

Resolution

The 26.1 release marks the definitive end of modular "product-by-product" installations. Broadcom has consolidated the DX O2 (Operational Observability) suite into a singular, containerized engine.

Key Change: In 26.1, you can no longer choose to exclude products like AXA or OI during the initial installation. The platform is deployed as a Unified Data Lake to ensure that AIOps correlation works across all telemetry types (Metrics, Events, Logs, and Traces).

Technical Prerequisites for 26.1
Before deploying DX O2 26.1 on-premises, the following infrastructure must be provisioned:
1. Orchestration (K8s/OpenShift)

• Kubernetes: v1.28 to v1.30+
• OpenShift: v4.12 to v4.15+

2. Resource Sizing (Baseline)

• Compute Minimum 16-32 Cores per Worker Node (Min 3 Nodes)
• Memory 64 GB - 128 GB RAM per Node (Unified stack is memory intensive)
• Storage 1 TB+ High-Performance SSD/NVMe (StorageClass with RWO/RWX support)

3. External Connectivity

• Ingress: NGINX or HAProxy with a Static LoadBalancer IP.
• Registry: Access to internal OCI-compliant registry (Harbor/Artifactory).
• Entitlements: Valid Broadcom Site ID associated with DX O2 for image pulls.