Dell Automation Platform Components

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.

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.

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.

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.

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.

When updating a deployment the Deployment_id input update requires manual change of the deployment to allow the update to complete.

Upload of Dell Private Cloud Zip bundle to Orchestrator fails with "Invalid blueprint" error.

A NativeEdge Virtual Machine (VM) which is imported from VMware vCenter with multiple disks can fail to boot.

This article describes a rare issue where the Deployments and Blueprints pages fail to load, resulting in a 504 Gateway Time-out error. The error is potentially related to the nginx server. A workaround is provided to resolve the issue.

This article describes the solution for Dell Automation Platform Upgrade Issues, when Portal Vault pods are not coming up.

Unable to assign a voucher downloaded from Dell Digital Locker to the Orchestrator.

This article is designed to aid a user to determine the container sizing requirements for Orchestrator External Connection vCenter.

When connecting a NativeEdge External Connection for vCenter, under certain conditions hosts and or virtual machines (VMs) may not connect to the orchestrator.

The installation may fail when installing DAP 1.x and when using a cookie domain of local.edge.

In rare circumstances, a NativeEdge Gateway with a 5g modem disconnects and is unable to reconnect until the device is rebooted.

In rare circumstances, it is possible that the device's staging partition free space is fully consumed.