NativeEdge

This document provides step-by-step instructions for installing Ubuntu 24.04 LTS Server from ISO media and configuring it as a Dell NativeEdge Witness Node. The installation uses minimal packages to optimize performance and security. The usual and recommended method for installing a Dell NativeEdge Witness Node is to use the free blueprint provided in the NativeEdge blueprint catalog. This manual installation guide is intended for users who, for specific reasons, must create a witness node manually instead of using the automated blueprint deployment.

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

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

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.

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.

This article explains Dell guidelines on company administrator assignment.

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.

This article explains how to assign an Initial Company Administrator.

This article explains how to promote Company Administrators.

Java-based containerized applications (such as Keycloak) may experience unexpected termination due to out-of-memory (OOM) errors when running on Linux Kernel 6.12 or later. This issue stems from changes in how the kernel exposes "cgroup" memory limits. These changes affect the Java Virtual Machine's (JVM) ability to detect and respect container memory constraints correctly.

On-Premises Dell Automation Platform installation fails with error: chunk N does not exist. (In this case, N represents a number. The number can be different per attempt.)

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

Attempting NativeEdge Endpoint 3.1 Server Firmware upgrade after upgrading the NativeEdge Endpoint Operating Environment (NEOE) to 3.1, can result in a Trusted Platform Module (TPM) resealing error.

Upgrading from NativeEdge endpoint firmware 2.2.0.0 to 3.0.0.0 triggers a stamping fallback to 2.2.0.0 due to a missing catalog in 3.0.0.0. This issue causes no functional impact.

This article aims to help with Troubleshooting Dell NativeEdge Installation: Resolving Pod Startup Issues

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.

This article helps to troubleshoot the reasons for the stalled or stopped responding upload during the reset or recovery image for the NativeEdge endpoint.

This article helps with guiding a user to gather the correct logs for troubleshooting issues.

NativeEdge Endpoints use QEMU/LibVirt as their virtualization technology. A Virtual Machine (VM) on a NativeEdge Endpoint may show a network interface speed of 1 Gbps, but this is not the actual speed.

When upgrading the NativeEdge Orchestrator (NEO) from 3.0 to 3.1 release, the upgrade fails due to a missing Kubernetes secret eo-registry-secret.

On the Endpoints > Endpoint detail > Metrics tab, metrics do not display if there are many endpoints connecting to a NativeEdge Orchestrator.

Troubleshoot and recover NativeEdge systems with an HTTP 500 status during reset or recovery image creation.

This article outlines issues seen when updating the default NativeEdge Orchestrator (NEO) certificates.

NativeEdge Orchestrator bundle upload and validation have failed. Error code: 0x019020004/0x01903000B