- 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
Copied.
Registering an Edge Node
Registering an edge node is the process of creating an edge node on IEF and obtaining the node configuration file and EdgeCore Installer.
Constraints
- NPUs on the same node support only the same partition specification.
- You cannot perform virtualization partition on the NPU of an IEF-managed edge node by simply upgrading the NPU plug-in to v2.1.0. Uninstall and reinstall the node, manually partition the NPU, and then manage the node on IEF again.
- The NPU driver version must be later than 22.0. 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 you enable the NPU sharing mode, you need to set the container sharing mode for all chips on the NPU.
- NPU virtualization partition is not supported if the D310P-share is used.
Registering an Edge Node
- Log in to the IEF console.
- In the navigation pane, choose Managed Resources > Edge Nodes. Then, click Register Edge Node in the upper right corner.
- Configure basic edge node information.
Figure 1 Basic edge node information (1)
- Node Name: name of an edge node. The name can contain 1 to 64 characters, including letters, digits, hyphens (-), and underscores (_).
- Description: Optional. Enter the description of the edge node.
- Tags: Tags can be used to classify resources, facilitating resource management.
- AI Accelerator Card
Ascend AI accelerator card: supports edge nodes that support Ascend processors. If you need to use Ascend 310, 310B, first select the AI accelerator card and then select the NPU type. Table 1 lists the NPU types supported by Ascend AI accelerator cards.
NVIDIA GPU: Select this option if your edge node is equipped with an NVIDIA GPU.
Not installed: Select this option if your edge node does not use any AI accelerator card.
NOTE:
If you select NVIDIA GPU but your edge node is not equipped with any NVIDIA GPU, the edge node cannot be managed by IEF.
If your edge node has been equipped with a GPU, install and configure the GPU driver on the edge node before you can manage it on IEF. For details, see Installing and Configuring a GPU Driver.
- Bind Device: Bind an end device to the edge node. If you have not registered an end device, register one by referring to End Device Management. If you do not bind an end device in this step, you can bind one after the edge node is registered.
- Docker: After Docker is enabled, containerized applications can be deployed.
- Listening Address
The address on which the built-in MQTT broker of the edge node listens. It is used for edge-cloud messaging. For details about edge-cloud messaging, see Edge-Cloud Message Overview.
By default, local NICs lo (localhost) and docker0 are listened to. You can specify an NIC name or IP address to set the NIC to be listened to. Multiple NICs or IP addresses can be added.
Figure 2 Basic edge node information (2)Currently, system and application logs can be collected from edge nodes.
- System Logs: logs generated by the IEF software (such as edge-core, edge-logger, and edge-monitor) installed on edge nodes.
- Application Logs: logs generated by applications deployed on edge nodes.
Set the following parameters for both system and application logs:
- Maximum Log Size (MB): maximum size of a log file, in MB. The default value is 50. The value range is 10–1000. If a log file reaches the size specified here, the system compresses the log file and dumps it to a specified directory on the host.
- System logs are stored in the /var/IEF/sys/log/ directory on edge nodes and will be dumped to AOM when the maximum log size is reached.
- Application logs include the standard output of containers and the logs mounted to /var/IEF/app/log on the edge node. These logs will be dumped to AOM when the maximum log size is reached.
- Log Rotation: log dump interval. You can select Daily, Weekly, Monthly, or Yearly. Log files will be dumped when either Maximum Log Size (MB) or Log Rotation is reached.
- Logs Saved: maximum number of logs being retained at a specified period. The default value is 5. The value range is 1–10. Once this number is reached, when new log files are dumped in, old log files will be deleted on a first-in first-out (FIFO) basis.
- Save Logs to AOM
You can enable or disable log uploading to AOM. If it is enabled, you can view the logs in AOM. For details, see Viewing Logs on AOM.
- Select I have read and agree to the Huawei Cloud Service Level Agreement. Click Register in the lower right corner. You can choose to register the edge node using a certificate or a token.
Registration using a certificate: Download the configuration file and EdgeCore Installer, which will be used in Managing an Edge Node.Figure 3 Downloading the configuration file and EdgeCore Installer
- Click Download Edge node name.tar.gz.
- Select the CPU architecture of your edge node, and click Download EdgeCore Installer.
- In the lower right corner, select I've finished downloading and click Finish.
The edge node is in the Unconnected state because the EdgeCore Installer downloaded in Registering an Edge Node has not been installed. For details, see Managing an Edge Node.
Figure 4 Unconnected edge node
Follow-up Procedure
After the registration is complete, you need to manage the edge node. For details, see Managing an Edge Node.
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