NativeEdge

本文档提供有关通过 ISO 介质安装 Ubuntu 24.04 LTS 服务器并将其配置为 Dell NativeEdge 见证节点的分步说明。安装使用最少的软件包来优化性能和安全性。 安装 Dell NativeEdge 见证节点的常用推荐方法是使用 NativeEdge 蓝图目录中提供的免费蓝图。本手动安装指南面向因特定原因必须手动创建 Witness 节点而非使用自动蓝图部署的用户。

Dell Automation Platform Orchestrator 会针对修改 Orchestrator 微分段的安全设置显示严重警报。显示警报代码 0x20010002。

本文介绍在尝试使用门户 UI 使用自定义证书管理默认 TLS 证书期间出现的问题。

Dell Native Edge Orchestrator (EO) remediation is available for multiple security vulnerabilities that could be exploited by malicious users to compromise the affected system.

本文介绍如何检索日志包以对问题进行故障处理 戴尔自动化平台（本地）

在软件捆绑包部署期间，主机防火墙可以配置为阻止 Kubernetes pod 网络接口上的流量。这会阻止容器网络接口 （CNI） 插件进行通信。McAfee Endpoint Security 防火墙已观察到此问题，但任何主机防火墙解决方案都可能发生此问题。

对于包含 HBA355i的 PowerEdge 系统，NativeEdge 成果节点固件捆绑包显示未知

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.