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.

In Dell NativeEdge 4.2.0.0, devices using Telit LTE modems do not display Operator ID or Operator Name under the SIM Details section in the Orchestrator UI. These fields are displayed correctly for Sierra Wireless modems, causing inconsistent behavior across modem types. The issue occurs because ModemManager does not provide Operator ID or Operator Name for Telit modules, and the fields cannot be populated.

When updating to NativeEdge v4.2 EdgeOS and EdgeOS Bundle, Dell NativeEdge enforces Hybrid Mode validation on supported hardware platforms. This affects both PowerEdge servers and Precision Rack systems. If Hybrid Mode is not configured correctly on the device, users may encounter upgrade blocks, error messages, or alerts during onboarding. This validation ensures that the device is running a compatible Hybrid Mode configuration required for proper operation of NativeEdge features.

This KB documents the expected and intentional behavior for the NativeEdge v4.2.0.0 release: To prevent VM disk corruption, NativeEdge disables discard="unmap" on shared datastores. As a result, automatic storage reclamation does not occur until the underlying Ubuntu kernel issue is resolved.

When creating an HA Group in a two‑node NativeEdge cluster with a Witness node, the operation may fail with a 500 Internal Server Error. Investigation shows that the failure occurs because Endpoint and Orchestrator system clocks are not synchronized, causing the HA configuration request sent over NATS to expire before the ECE agent processes it.

When running SCV (System Compatibility Validation) on a PowerEdge R7960 Rack system configured without a PERC controller, the SCV workflow reports an error coming from iDRAC using the GetRemoteServiceStatus API. The Real-Time Status (RTStatus) is returned as "Not Ready." This is expected behavior on configurations without a PERC controller, but SCV treats it as an error, even though NativeEdge supports onboarding such devices.

During device onboarding on NativeEdge SaaS, the process fails at the step "Retrieving host environment configuration template from Edge Orchestrator,” returning a curl: (60) SSL certificate error The error indicates that the server‑side TLS certificate presented by the orchestrator does not contain the required Subject Alternative Name (SAN) for the hostname being accessed. This results in curl rejecting the connection due to failed certificate validation

After upgrading both Dell automation platform orchestrator and EdgeOS, virtual machines deployed using external PowerStore storage over iSCSI may fail to return to an Online state. The VM remains stopped, and manually starting it fails. This behavior is caused by reusing an unclean PowerStore host-volume, which contains stale LVM metadata from previous deployments. The issue originates during earlier releases NativeEdge v4.1.0.0 and is carried forward into NativeEdge v4.2.0.0 during the upgrade flow.

During HA cluster creation, the ECE agent is required to sign a Certificate Signing Request (CSR) using HTTPS against the mTLS Orchestrator endpoint. In affected versions, the CSR signing logic performed only a single attempt with no retry capability. A single transient TCP timeout—often caused by short‑lived HAProxy instability—would immediately fail CSR signing on one node, resulting in entire HA cluster creation failure and triggering full cleanup.

When a 5G modem manager session becomes stale or corrupted on an Edge device, the NativeEdge UI may incorrectly display extra dummy tty* interfaces under Hardware → Network Adapters. In this state, cellular connectivity cannot be enabled, and SIM detection may fail. This is a known behavior, not a software defect. The issue can be fully resolved through a hard power‑cycle reset of the device, which forces correct modem and Modem Manager reinitialization.

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.

NativeEdge Endpoints onboard to NativeEdge Orchestrator (NEO) using the Dell Public Rendezvous (RV) server when they have access to the Internet. This article explains how to troubleshoot RV connectivity issues.

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 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.