หน้านี้ยังไม่พร้อมใช้งานในภาษาท้องถิ่นของคุณ เรากำลังพยายามอย่างหนักเพื่อเพิ่มเวอร์ชันภาษาอื่น ๆ เพิ่มเติม ขอบคุณสำหรับการสนับสนุนเสมอมา
- 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.
Connecting Edge Nodes to IEF Through Direct Connect or VPN
Scenario
If an edge node cannot access IEF through a public network, it can connect to Huawei Cloud Virtual Private Cloud (VPC) through Direct Connect or Virtual Private Network (VPN), and then connect VPC to IEF through the private and secure channel provided by a VPC endpoint.
Connection Solution
Before deploying applications on an edge node, ensure that the edge node can communicate with IEF, SWR and OBS. If the edge node cannot connect to IEF through a public network, connect the edge node to Huawei Cloud VPC through VPN or Direct Connect, and then enable VPC to access IEF, SWR and OBS through VPC endpoints. Figure 1 shows the connection solution.
To connect edge nodes to IEF, you need to create the following three endpoints.
- ief-placement: for managing and upgrading edge nodes
- ief-edgeaccess: for sending messages between edge nodes and cloud services
- ief-telemetry: for uploading monitoring data and logs on edge nodes
To connect edge nodes to SWR, you need to create one endpoint. To connect edge nodes to OBS, you need to create an OBS endpoint and a DNS endpoint. (OBS can only be accessed through the domain name when the OBS address is dynamically resolved by DNS.)
Procedure
- Create a VPC.
For details, see Creating a VPC.
You can also use an existing VPC.
NOTICE:
The VPC CIDR block cannot overlap the IDC CIDR block.
- Connect the edge node to a VPC through Direct Connect or VPN.
For details, visit the following links:
- Create IEF endpoints to enable the connection between the edge node and IEF.
You need to create three endpoints: ief-placement, ief-edgeaccess, and ief-telemetry. The procedure is as follows:
- Log in to the VPC Endpoint console and click Buy VPC Endpoint in the upper right corner.
- Select the IEF endpoints and VPC.
Figure 2 Creating IEF endpoints
- Click Next, confirm the information, and click Submit.
- Create an SWR endpoint so that the edge node can pull container images from SWR.
The procedure is the same as that of creating IEF endpoints.Figure 3 Creating an SWR endpoint
- Create DNS and OBS endpoints for edge nodes to access OBS.
For details, see Accessing OBS.
- Add the hosts configuration for the edge node.
Query the four IP addresses of IEF and SWR endpoints and add them in the /etc/hosts file of the edge node.
Figure 4 Querying IP addresses of the endpointsOpen the /etc/hosts file and add the IP addresses at the end of the file so that the domain names for accessing IEF and SWR point to the IP addresses of the corresponding endpoints.
NOTICE:
Change the IP addresses and domain names based on the site requirements. The IP addresses are the ones obtained in the preceding step, and the domain names vary depending on the region. For details, see Domain Name.
192.168.2.20 ief2-placement.cn-north-1.myhuaweicloud.com 192.168.2.142 ief2-edgeaccess.cn-north-1.myhuaweicloud.com 192.168.2.106 ief2-telemetry.cn-north-1.myhuaweicloud.com 192.168.2.118 swr.cn-north-1.myhuaweicloud.com
- Register the edge node and use IEF to manage the edge node. For details, see Edge Node Overview.
Domain Name
ief-edgeaccess of the platinum edition has an independent address, which is the value of Access Domain on the Dashboard page of the IEF console.
Region |
Name |
Domain Name |
---|---|---|
CN North-Beijing1 |
ief-placement |
ief2-placement.cn-north-1.myhuaweicloud.com |
ief-edgeaccess |
ief2-edgeaccess.cn-north-1.myhuaweicloud.com |
|
ief-telemetry |
ief2-telemetry.cn-north-1.myhuaweicloud.com |
|
swr |
swr.cn-north-1.myhuaweicloud.com |
|
CN North-Beijing4 |
ief-placement |
ief2-placement.cn-north-4.myhuaweicloud.com |
ief-edgeaccess |
ief2-edgeaccess.cn-north-4.myhuaweicloud.com |
|
ief-telemetry |
ief2-telemetry.cn-north-4.myhuaweicloud.com |
|
swr |
swr.cn-north-4.myhuaweicloud.com |
|
CN South-Guangzhou |
ief-placement |
ief-placement.cn-south-1.myhuaweicloud.com |
ief-edgeaccess |
ief-edgeaccess.cn-south-1.myhuaweicloud.com |
|
ief-telemetry |
ief-telemetry.cn-south-1.myhuaweicloud.com |
|
swr |
swr.cn-south-1.myhuaweicloud.com |
|
CN East-Shanghai1 |
ief-placement |
ief-placement.cn-east-3.myhuaweicloud.com |
ief-edgeaccess |
ief-edgeaccess.cn-east-3.myhuaweicloud.com |
|
ief-telemetry |
ief-telemetry.cn-east-3.myhuaweicloud.com |
|
swr |
swr.cn-east-3.myhuaweicloud.com |
|
CN East-Shanghai2 |
ief-placement |
ief2-placement.cn-east-2.myhuaweicloud.com |
ief-edgeaccess |
ief2-edgeaccess.cn-east-2.myhuaweicloud.com |
|
ief-telemetry |
ief2-telemetry.cn-east-2.myhuaweicloud.com |
|
swr |
swr.cn-east-2.myhuaweicloud.com |
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