- 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 Nodes in Batches
Scenario
If you need to manage, update, and maintain a large number of edge nodes of the same type, it will be labor-consuming to do so one by one as described in Registering an Edge Node.
IEF provides batch node registration to pre-install required software on edge nodes of the same type so that they can be connected to the network after they are powered on. This one-to-many design improves management efficiency and reduces O&M costs.
Procedure of Registering Nodes in Batches
The procedure for managing edge nodes in batches is as follows:
- Prepare edge nodes that meet certain requirements. Then, configure the environment on the edge nodes by referring to Configuring the Edge Node Environment.
- After creating a batch node registration job, obtain the configuration file and registration software, and pre-install them on the edge nodes. For details, see Managing Edge Nodes in Batches. If the registration command is configured in the startup script, the device will be automatically managed as an edge node of IEF after being powered on and connected to the network.
Creating a Batch Node Registration Job
- Log in to the IEF console.
- In the navigation pane, choose Batch Management > Node Registration Jobs, and click Register Edge Nodes in the upper right corner of the displayed page.
- Configure basic information. The parameters marked with * are mandatory.
- Name: name of the batch node registration job.
- Description: description of the job.
- Tags: Tags can be used to classify resources, facilitating resource management.
- Properties: A property is in key-value pair format. Enter a key and value.
- Click Register in the lower right corner. You can choose to register the edge nodes using a certificate or a token.
- Method 1: registration using a certificate: Download the configuration file, EdgeCore Register, and EdgeCore Installer.
NOTICE:
To enhance node security, you must download the configuration file and tools now. The configuration file and tools cannot be retrieved later.
- Click Download cert_1.tar.gz to download the configuration file.
- Select the CPU architecture of your edge nodes, and click Download Node Registration Tool and Download Node Installation Tool.
- Method 2: registration using a token: Download EdgeCore Register and EdgeCore Installer and save the installation credential.
Figure 1 Downloading EdgeCore Register and EdgeCore InstallerFigure 2 Installation credential
- Select the CPU architecture of your edge nodes, and click Download Node Registration Tool and Download Node Installation Tool.
- Save the identifier field of the installation command.
- Method 1: registration using a certificate: Download the configuration file, EdgeCore Register, and EdgeCore Installer.
- Upload the downloaded file to the edge nodes, and then manage the edge nodes on IEF by referring to Managing Edge Nodes in Batches.
Managing Edge Nodes in Batches
Follow the procedure of the finish step on the Register Edge Nodes page to perform the batch management operation to the edge nodes.
- Log in to an edge node as a user with sudo permissions.
- Upload the configuration files and tools downloaded in step 4 of "Creating a Batch Node Registration Job" to the edge nodes.
- Run the following commands to decompress the configuration file, EdgeCore Register, and EdgeCore Installer:
sudo tar -zxvf edge-installer_1.0.10_x86_64.tar.gz -C /opt
sudo tar -zxvf edge-register_2.0.10_x86_64.tar.gz -C /opt
sudo tar -zxvf cert_batchNodes.tar.gz -C /opt/edge-register/ (This command is not required for registration using a token.)
Replace edge-installer_1.0.10_x86_64.tar.gz, edge-register_2.0.10_x86_64.tar.gz, and cert_batchNodes.tar.gz with the names of the files downloaded in Creating a Batch Node Registration Job.
- (Optional) Customize the node information.
For batch node management, the default configuration will be applied for these edge nodes. Where:
- The node name is the combination of the host name and MAC address of the node, that is, Host name_MAC address.
- The GPU and NPU options are disabled.
- The Docker function is enabled.
If you want to customize node information, configure the nodeinfo file. Run the following commands to open the nodeinfo file:
cd /opt/edge-register
vi nodeinfo
Specify the node information in the nodeinfo file. The following example lists all configurable parameters. You can set the parameters based on site requirements and delete the parameters that do not need to be customized.
Parameters such as the node name, descriptions, GPU enabled or not, NPU, NPU types, attributes, and log configuration are included. For details about the parameters, see API Reference > Registering an Edge Node.{ "name": "nodename", "description": "", "enable_gpu": false, "enable_npu": true, "npu_type": "***", "enable_docker": true, "attributes": [ { "key": "key1", "value": "value1" } ], "log_configs": [ { "component": "app", "type": "local", "level": "debug", "size": 100, "rotate_num": 5, "rotate_period": "daily" } ], "device_infos": [ { "device_ids": ["15696983-5ee6-43b4-9653-5d8512813dcc"], "relation": "camera", "comment": "devicedescription" } ], "mqtt_config": { "enable_mqtt": false, "mqtts": [] }, "tags": [ { "key": "name", "value": "value" } ] }
- Run one of the following commands to manage the edge nodes:
- For edge nodes registered using tokens:
cd /opt/edge-register; ./register --mode=identifier --identifier=Credential for registration using a token
Replace Credential for registration using a token with the value of identifier field of the installation credential saved in Creating a Batch Node Registration Job.
After the command is executed, check whether the node is successfully registered by referring to Viewing Managed Nodes.
You can also add the registration command cd /opt/edge-register; ./register --mode=cert to the startup script. In this way, the edge node can automatically run the registration command when it is powered on.
If the command output is 0, the edge node is successfully registered on IEF.
- For edge nodes registered using tokens:
Viewing Managed Nodes
You can view the nodes managed in batches on the console.
- Log in to the IEF console.
- In the navigation pane, choose Batch Management > Node Registration Jobs, and click a job name on the displayed page.
- You can view the managed nodes on the Nodes tab.
Figure 3 Viewing nodes managed in batches
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