Dell Automation Platform Components

This article explains how to retrieve a log bundle to troubleshoot issues Dell Automation Platform (On Prem)

Dell Automation Platform uses the connection-status application programming interface (API) query on multiple areas of the Orchestrator. If the connection-status API returns an HTTP 500 error, multiple components are affected. The connection-status API returns an HTTP 500 if Secure Remote Services is not configured correctly.

When using the legacy Dell NativeEdge v1 Gateway API POST /rest/v1/jobs to add, update, or delete a host network (endpoint:network:hostNw:*), the request may fail withHTTP 400 and the message property "nwSeg" is missing. This happens when the hostNw payload objects do not include the endpoint id field. The v2 Gateway API is recommended; if v1 must be used, include the endpoint UUID as the id in each hostNw object.

When onboarding nodes in Dell Automation Platform (DAP) version 2.1.1.0, some devices may become stuck in the Onboarding state. This occurs due to a NATS reconnect handling issue in the hzp-inventory service that causes silent message processing failures.

In Dell Automation Platform (DAP) version 2.1.1.0, blueprints downloaded from the catalog incorrectly display as "Not Dell Validated" when they should show as Dell Validated. This issue affects the user experience and may cause confusion about blueprint validation status.

In large-scale Dell Automation Platform (DAP) deployments, endpoint and virtual machine (VM) metrics can stop appearing in dashboards, reports, and the /api/v2/datapoints API while endpoint operations continue. This occurs when the VictoriaMetrics vmstorage database becomes full and switches to read-only mode. New metrics cannot be ingested and recent data cannot be queried until storage is expanded or data is removed. This article describes symptoms, root cause, workarounds, and sizing guidance.

When a Dell Automation Platform (DAP) Orchestrator (DAPO) virtual machine local disk space fills to 90%, Kubernetes evicts pods to prevent node failure. After clearing disk space, applications may not automatically recover due to data corruption from incomplete writes or persistent volume claim failures.

The Dashboard status count does not include clusters with Unknown, Error, or Warning states. This causes a discrepancy between the Dashboard count and the actual number of clusters shown in Infrastructure navigation. This behavior is by design; the Dashboard uses a platform-generic status enum for consistency across providers.

After upgrading to Dell Automation Platform (DAP) 2.1, customers using custom Role-Based Access Control (RBAC) roles (for example, for PowerProtect Data Manager backup and restore operations) may experience failures. This occurs because of a breaking change in IAM policy handling, where permissions are now dynamically generated using a resource provider model, introducing a provider name prefix to permission strings.

Dell Automation Platform Orchestrator (DAPO) may fail to load and return HTTP 500 when the PostgreSQL PVC fills with orphan large objects created by repeated FIDO TO0/Global Rendezvous retries in the est_owner_db database.

This Knowledge Base article documents an intermittent network outage issue observed on nodes equipped with Broadcom BCM 574xx/575xx NICs running VMware ESXi 8.0 Update 3. The condition manifests as vmnics going down, leading to ESXi host unresponsiveness due to a NIC firmware crash.

Dell Automation Platform remediation is available for multiple security vulnerabilities that could be exploited by malicious users to compromise the affected system.

A NativeEdge device shows “No Data Available” in the Dell Automation Platform (DAP) Metrics tab because the telegraf handler depends on a machineID message from the Orchestrator (EO), which may be missing or delayed.

Dell Automation Platform remediation is available for multiple security vulnerabilities that could be exploited by malicious users to compromise the affected system.

During a software bundle deployment, a host firewall may be configured to block traffic on Kubernetes pod network interfaces. This prevents the Container Network Interface (CNI) plugin from communicating. This issue is observed with McAfee Endpoint Security firewall but may occur with any host firewall solution.

The NativeEdge Outcome node firmware bundle is showing Unknown for PowerEdge systems which contain a HBA355i.

Deployments of long-running workloads (example DataRobot deployment, Cohere, ClearML, and so forth) fail when using the Dell Automation Platform (DAP) 1.2 and 2.0.

Customers may encounter warning alerts for EDGE_HZP_DEVICE_CAT0 license exhaustion in Dell Automation Platform environments with PowerStore storage. This is a benign issue caused by storage onboarding incorrectly attempting to consume licenses.

Security Technical Implementation Guide (STIG) Hardening using the Dell Compliance Engine (DCE).

This article addresses an issue in NativeEdge Orchestrator (NEO) version 3.1 and also Dell Automation Platform versions 1.0 - 2.1. The system becomes unavailable due to expired mTLS certificates. The issue affects systems that have been running for longer than one year. The internal mTLS certificate rotation mechanism fails to renew certificates in time, causing widespread pod startup failures and making the NEO user interface inaccessible. This issue was identified as affecting all systems with expiring mTLS certificates approximately one year after initial deployment.

Expected storage volumes (virtual disks) are not created immediately when a DisableRAID job run through the ECE Agent completes with a SUCCESS status on Dell PowerEdge devices with a RAID controller.

Firmware upgrade process for XR5610 systems fails because the systems have firmware versions that do not match the expected firmware lock versions. The Native Edge Orchestrator firmware update service cannot find a valid upgrade path for the devices because the current versions on the systems are not recognized in the available catalog.

This article describes issues seen during an attempted default TLS certificate with a custom certificate using Portal UI.

A user is unable to onboard a NativeEdge Gateway Assets (either the 3200 or 5200 Models) due to Factory OS missing Server Name Indication Header which is required for onboarding.

The deployment fails when Network Time Protocol (NTP) is set using Fully Qualified Domain Name (FQDN) for OVA installation of the Dell Automation Platform 1.x.

A NativeEdge Asset reports an incorrect IP address for its management address.

This article explains an issue where the kernel drivers fail to detect one of the NVIDIA Graphics Processing Units (GPU) in a Unified Extensible Firmware Interface (UEFI) Virtual Machine (VM) configured with multiple GPU passthroughs.

The procedure for generating an access key and PIN to enable connectivity for a Dell Automation Platform orchestrator varies with the environment. The Dell access key and PIN portal have been updated (on 1/12/2026) to present the user with two options for access key and PIN generation for the Dell Automation Platform orchestrator.

The Dell Automation Platform orchestrator displays a critical alert for the modification to the security setup of Orchestrator Microsegmentation. Alert code 0x20010002 is shown.

When attempting to gather logs from a Dell Automation Platform Proxy, log gathering fails if the Proxy is named Oxy.