Halaman ini belum tersedia dalam bahasa lokal Anda. Kami berusaha keras untuk menambahkan lebih banyak versi bahasa. Terima kasih atas dukungan Anda.
- What's New
- Product Bulletin
- Service Overview
- Getting Started
-
User Guide
- Edge Computing with IEF
- Service Instances
-
User Guide (Professional)
- Node Management
-
End Device Management
- End Devices and Device Twins
- Device Templates
- End Devices
- Binding an End Device to an Edge Node
- Device Twin Working Principles
- Migrating Device Data to the Cloud
- Performing Security Authentication Using Certificate
-
MQTT Topics
- Device Twin Update
- Device Twin Delta
- Device Member Update
- Device Property Update
- Device Member Acquisition
- Device Member Acquisition Result
- Device Twin Acquisition
- Device Twin Acquisition Result
- Device Twin Modification
- Device Twin Modification Result
- Encryption Data Request
- Encryption Data Acquisition
- Alarm Reporting
- Alarm Clearance
- Custom Topics
- Containerized Application Management
- Edge-Cloud Messages
- Batch Management
- Auditing
- Permissions Management
-
User Guide (Platinum)
- Node Management
-
End Device Management
- End Devices and Device Twins
- Device Templates
- End Devices
- Binding an End Device to an Edge Node
- Device Twin Working Principles
- Migrating Device Data to the Cloud
- Performing Security Authentication Using Certificate
-
MQTT Topics
- Device Twin Update
- Device Twin Delta
- Device Member Update
- Device Property Update
- Device Member Acquisition
- Device Member Acquisition Result
- Device Twin Acquisition
- Device Twin Acquisition Result
- Device Twin Modification
- Device Twin Modification Result
- Encryption Data Request
- Encryption Data Acquisition
- Alarm Reporting
- Alarm Clearance
- Custom Topics
- Containerized Application Management
- Application Mesh
- Edge-Cloud Messages
- Batch Management
- Auditing
- Permissions Management
- Best Practices
-
API Reference
- Before You Start
- API Overview
- Calling APIs
-
API
-
Edge Node Management
- Registering an Edge Node
- Updating an Edge Node
- Querying Details About an Edge Node
- Querying a List of Edge Nodes
- Deleting an Edge Node
- Starting or Stopping an Edge Node
- Updating End Devices for an Edge Node
- Querying Node Certificates
- Creating a Node Certificate
- Deleting a Node Certificate
- Performing an Edge Node Upgrade Check
- Upgrading Edge Nodes
- End Device Management
- End Device Template Management
-
Application Template Management
- Creating an Application Template
- Updating an Application Template
- Querying Details About an Application Template
- Querying a List of Application Templates
- Deleting an Application Template
- Creating an Application Template Version
- Updating an Application Template Version
- Querying Details About an Application Template Version
- Querying a List of Application Template Versions
- Deleting an Application Version
- Deployment Management
- Tag Management
- ConfigMap Management
- Secret Management
- Endpoint Management
- Rule Management
- System Subscription Event Management
- Batch Node Management
- Batch Job Management
- Quota Management
- Service Management
-
Edge Node Management
- Data Structure
- Permissions Policies and Supported Actions
- Appendix
- Change History
- SDK Reference
-
FAQs
-
Edge Node FAQs
- What Do I Do If an Edge Node Is Faulty?
- What Are the Fault Scenarios of Edge Nodes?
- What Do I Do If Edge Node Management Fails?
- How Do I Obtain the Latest Device Properties After Device Properties Are Updated?
- What Operations Can I Perform After a Device Is Associated with a Node?
- Does an Edge Node Support Multiple GPUs?
- Can I Change the GPU on a Running Edge Node?
- How Is Edge Environment Security Protected?
- Why Cannot I View Monitoring Data on an Edge Node?
- How Can I Restore a Deleted Edge Node?
- What Is the Impact of IP Address Changing on an Edge Node?
- What Do I Do If the NTP Configuration Cannot Be Modified?
- How Do I Synchronize Time with the NTP Server?
- How Do I Obtain the IP Addresses of IEF Cloud Services?
- What Do I Do If the Edge Node Space Is Insufficient?
- How Do I Set Docker Cgroup Driver After Installing Docker on an Edge Node?
-
Edge Application FAQs
- What Do I Do If an Application Fails to Be Delivered to an Edge Node?
- What Do I Do If a Containerized Application Fails to Be Started on an Edge Node?
- What Do I Do If a Containerized Application Fails to Be Upgraded?
- What Do I Do If a Container Image Fails to Be Pulled?
- Why Cannot I View Application Logs and System Logs?
- How Do Applications Schedule GPU Resources?
- How Do I Control the Disk Space Occupied by a Container Engine?
- What Do I Do If a Containerized Application Cannot Access External IP Addresses
- What Do I Do If the Ascend AI Accelerator Card (NPU) Is Abnormal?
-
Edge-Cloud Message FAQs
- What Is Route Management?
- What Is a Message Endpoint in Route Management?
- What Is a Route?
- Why Does a Route Fail to Be Created?
- What Can I Do If a Message Fails to Be Forwarded over a Route?
- What Is the Impact of Disabling a Route?
- What Can I Do If SystemEventBus (MQTT Broker) of an Edge Node Fails to Be Connected?
- Network Management FAQs
- Basic Concept FAQs
-
Others
- Region and AZ
- What Are the Specifications of Edge Nodes Supported by IEF?
- What Are the Differences Between Device Properties and Device Twins?
- What Programming Language Is Required for IEF Development?
- Do I Need to Prepare Edge Nodes by Myself?
- Can I Still Use the Previously Delivered Applications After My Account Is in Arrears?
- What Are the Differences Between IEF and IoT Edge?
- What Do I Do If an Agency Fails to Be Automatically Created?
- How Can I Deal With Insufficient Permissions?
- How Will the Multi-AZ Reconstruction of SWR Application Container Image Data Affect IEF?
-
Edge Node FAQs
-
Edgectl User Guide
- Overview
- Installing edgectl
- Example: Using edgectl to Run Commands
-
edgectl Commands
- Querying the edgectl Version
- Managing the Product Lifecycle
-
Checking an Item
- Checking the Hardware Architecture
- Checking the CPU
- Checking the Memory
- Checking Hard Disks
- Checking the Domain Name Resolution Function
- Checking Docker
- Checking Network Connectivity
- Checking the Installation Status of the IEF Software
- Checking the Running Status of the IEF Software
- Checking GPUs
- Checking NPUs
- Checking Processes
-
Error Codes
- Error Code Overview
- Common Errors
- Permission Errors
-
OS Errors
- ERROR3001 Failed to obtain the hardware architecture
- ERROR3002 Unsupported hardware architecture
- ERROR3101 Failed to obtain the CPU information of the node
- ERROR3102 Failed to obtain the real-time CPU status of the node
- ERROR3103 Insufficient node CPU
- ERROR3201 Failed to obtain the memory information of the node
- ERROR3202 Insufficient node memory
- ERROR3301 Failed to obtain the disk information of the node
- ERROR3302 Insufficient disk space on the node
- ERROR3401 Failed to resolve the domain name
- ERROR3501 Failed to check the network
- ERROR3601 Failed to obtain the process information of the node
- ERROR3602 Failed to obtain the total number of processes on the node
- ERROR3603 Number of remaining processes on the node is insufficient
-
IEF Software Errors
- ERROR5001 Incomplete IEF software installation
- ERROR5002 IEF software is not completely running
- ERROR5003 Failed to read the IEF software configuration file
- ERROR5004 Docker is not enabled for the IEF software
- ERROR5005 Failed to start the IEF software
- ERROR5006 Failed to stop the IEF software
- ERROR5101 No application data found
- ERROR5102 No status data of the application found
- ERROR5103 Container is not started
- ERROR5104 Container exits abnormally
- ERROR5105 Failed to pull the container image
- ERROR5106 Container exits
- Third-Party Dependency Errors
- Data Collection Errors
- Internal Errors
- Videos
- General Reference
Show all
Copied.
What Are the Specifications of Edge Nodes Supported by IEF?
IEF supports the following edge node specifications:
|
Item |
Specifications |
|---|---|
|
OS |
The language of the operating system must be English.
|
|
Memory |
More than 256 MB of memory is recommended as 128 MB of memory is required to run the edge software. |
|
CPU |
≥ 1 core |
|
Hard disk |
≥ 1 GB |
|
GPU (optional) |
The GPU models on the same edge node must be the same.  NOTE:
Currently, NVIDIA Tesla GPUs such as P4, P40, and T4 are supported. If an edge node is equipped with GPUs, you can choose not to enable its GPUs when registering it on IEF. If you choose to enable GPUs of an edge node, the GPU driver has to be installed on the edge node before you can manage it on IEF. Currently, only x86-based GPU nodes can be managed by IEF. |
|
NPU (optional) |
Ascend AI processors NOTE:
Currently, edge nodes integrated with Ascend Processors are supported, such as Atlas 300 inference cards, and Atlas 800 inference servers. Supported NPU specifications include Ascend 310P, 310B, Ascend 310P-share, and virtualization partition NPUs.. If you choose to enable NPUs of an edge node, ensure that the NPU driver has been installed on it. Currently, Ascend 310 supports only firmware versions 1.3.x.x and 1.32.x.x, for example, 1.3.2.B893. You can run the npu-smi info command to view your firmware version.The NPU driver version must be 22.0.4 or later. You can go to the driver path, for example, /usr/local/Ascend/driver, and run the cat version.info command to view your driver version. If the driver is not installed, contact the device manufacturer for assistance. |
|
Container engine |
The Docker version must be later than 17.06. If Docker 1.23 or later is used, set the docker cgroupfs version to 1. Docker HTTP API v2 is not supported. (However, Docker 18.09.0 is not recommended as it has a serious bug. For details, see https://github.com/docker/for-linux/issues/543. If this version has been installed, upgrade it at the earliest possible opportunity. )
NOTICE:
After Docker is installed, configure the Docker process to start at host startup. This configuration prevents system exceptions caused by Docker startup failures after the host is restarted. Docker Cgroup Driver must be set to cgroupfs. For details, see How Do I Set Docker Cgroup Driver After Installing Docker on an Edge Node?. |
|
Glibc |
The Glibc version must be later than 2.17. |
|
Port |
Edge nodes require port 8883, which is the listening port of the built-in MQTT broker on edge nodes. Ensure that this port works properly. |
|
Time synchronization |
The time on an edge node must be consistent with the UTC time. Otherwise, the monitoring data and logs of the edge node may be inaccurate. You can select an NTP server for time synchronization. For details, see How Do I Synchronize Time with the NTP Server? |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot
