NativeEdge

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

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

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

When viewing long‑range metrics (7, 30, or 90 days) in NativeEdge, the graph may appear continuous even on days where the endpoint was disconnected and no telemetry should exist. This behavior can lead users to assume the system is incorrectly displaying data continuity. This behavior is expected and is not a product defect.

Dell Automation Platform 1.2, Virtual Machines (VMs) fail to obtain an IP address using DHCP when connected to a bridge Virtual Network Segment (VNS) backed by a heterogeneous bond interface (a bond consisting of Ethernet and Wi-Fi). This behavior is the result of a deliberate architectural design choice to ensure broad compatibility with wireless networks.

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.

This article describes a deployment scenario that has been observed to cause memory oversubscription on a NativeEdge Virtual Machine (VM). Memory oversubscription may result in loss of access to the affected VMs.

This article explains common configurations with a NativeEdge Endpoint that prevent the configuration of a network bond.

This article describes a condition with a NativeEdge Endpoint incorrectly reporting its IP address. The situation may be observed after the Endpoint's provisioning, or after a reboot.

This article describes an issue that may occur during the boot process of a NativeEdge Virtual Machine (VM) running Windows after it was shut down. Sometimes, the VM may stop responding during POST due to a specific Windows configuration setting.

This article describes an endpoint state that occurs when a USB Factory Reset Image is inserted into the wrong endpoint. This halt state is triggered during the endpoint’s reboot or power‑on sequence following a shutdown.

In current NativeEdge releases, the Controller ID and Status fields for MegaRAID‑based storage controllers do not display correctly in the user interface → Hardware Inventory → MegaRAID Controller section. The Controller ID column appears blank, despite the corresponding data being properly returned by backend inventory services. This issue has been observed primarily on Dell Precision Tower devices using MegaRAID-based hard drives.

This article explains the procedure to open a Service Request (SR) using the Dell support page. Get help fast for your Dell device. No more waiting on hold. No more tech headaches. Dell makes it simple to fix problems, schedule repairs, or get support—right from your device or our support website.

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

This article explains how to assign an Initial Company Administrator.

This article explains how to promote Company Administrators.

Blueprint deployment taking more than expected time and getting higher CPU utilization and performance issue on fluent bit pod. This article explains how to performance tuned or work around the issue to increase the overall blueprint processing time.

This article explains Dell guidelines on company administrator assignment.

This article explains why a Litmus Edge deployment fails at the step Install_init_config and how to resolve the issue.

Dell NativeEdge Orchestrator's Container Metrics do not contain any network information.

When integrating Dell NativeEdge (v4.1.0.0, orchestrator 1.2.0.0) with Dell PowerProtect Data Manager (PowerProtect Data Manager), virtual machine discovery can fail on environments upgraded from DAP 1.0. PowerProtect Data Manager logs show a validation error indicating a missing disks.storageSources.externalId. This occurs because the disk ID field was introduced in DAP 1.1. VMs created on DAP 1.0 (and earlier) do not have this value populated after upgrade, which prevents PowerProtect Data Manager from persisting and discovering those VMs.

When deploying a Windows virtual machine (VM) on a PowerEdge R7715 with NVIDIA L40S GPU passthrough is configured, the VM may fail to connect to any network, regardless of whether NAT or Bridge mode is selected. The root cause is that Windows does not include native VirtIO network drivers, resulting in a VM with no functional network interface card (NIC). The network issue does not stem from GPU passthrough or hardware limitations.

On NativeEdge gateways, virtual machine Universal Serial Bus (USB) passthrough may fail or the guest operating system (OS) may not initialize the device correctly. A hotfix for this issue is available in the NativeEdge 3.2.0.0 release, and the behavior is also resolved in NativeEdge 4.1.0.0. Customers must enable USB controller passthrough using the advanced hypervisor parameter when running 4.1.0.0.

In Dell NativeEdge version 4.1.0.0, cluster storage may enter a degraded state unexpectedly during operations. This behavior has been observed linked to clock skew between cluster nodes exceeding the configured tolerance.

In Dell NativeEdge version 4.0.0.0, disabling a storage network bond on one node in a three-node cluster caused the remaining two nodes to panic almost simultaneously, resulting in cluster outage. This issue is linked to network configuration where management and storage bonds share the same subnet without Virtual Local Area Network (VLAN) isolation.

Initiating Maintenance Mode manually while a virtual machine-related job (such as Restore or Deployment) is in progress can cause the job to fail. This occurs because Maintenance Mode triggers immediate virtual machine migration, interrupting ongoing operations.

Newly mapped volumes in the PowerVault may not appear under Virtual Disks after performing an iSCSI target rescan when connecting a NativeEdge device to a PowerVault external storage system in Dell Automation Platform Orchestrator running NativeEdge v4.1.0.0. This issue occurs if no volumes were mapped to the NativeEdge device before the connection was established. If at least one volume is already mapped prior to the connection, subsequent volumes are displayed correctly after the rescan. This issue occurs only on PowerVault device and not on PowerStore device.

In Dell NativeEdge version 4.1.0.0, the Radius server certificate name was not displayed in the side panel as expected. Users can now view complete Radius certificate details from the Certificate page under the Security section.

When Dell Automation Platform Orchestrator (DAPO) is upgraded from version 1.0.0.0 to 1.2.0.0, Brownfield devices onboarded using older Brownfield Execution Bundles (for example, version 3.2.0.0) may remain fully operational even though the versions are incompatible. This issue allows day-2 operations that should be blocked.

Cluster-level upgrade may fail if the cluster hosts many virtual machines when upgrading Dell NativeEdge from version 3.2.0.0 or 4.0.0.0 to 4.1.0.0. This issue is resolved in version 4.1.0.0.