Diese Seite ist in Ihrer lokalen Sprache noch nicht verfügbar. Wir arbeiten daran, weitere Sprachversionen hinzuzufügen. Vielen Dank für Ihre Unterstützung.
- What's New
- Function Overview
- Product Bulletin
- Service Overview
- Getting Started
- User Guide
- API Reference
-
Best Practices
- Direct Connect Best Practices
- Connecting an On-Premises Data Center to a VPC over a Single Connection and Using Static Routing to Route Traffic
- Connecting an On-Premises Data Center to a VPC over a Single Connection and Using BGP Routing to Route Traffic
- Connecting an On-Premises Data Center to a VPC over Two Connections in Load Balancing Mode (Virtual Gateway)
- Connecting an On-Premises Data Center to a VPC over Two Connections in an Active/Standby Pair (Virtual Gateway)
- Connecting an On-Premises Data Center to Multiple VPCs that Do Not Need to Communicate with Each Other
- Connecting an On-Premises Data Center to Multiple VPCs in the Same Region Using Direct Connect and VPC Peering
- Using a Public NAT Gateway and Direct Connect to Accelerate Internet Access
- Troubleshooting
-
FAQs
-
Popular Questions
- What Are the Network Requirements for Connections?
- How Do I Select a Carrier When Purchasing a Connection?
- How Will I Be Billed for Direct Connect?
- How Do I Submit a Service Ticket?
- How Do I Test the Network Connectivity Between a Location and the Cloud?
- What Do I Do If I Select the Wrong Carrier When Creating a Connection?
-
Product Consultation
- What Are the Network Requirements for Connections?
- What Are 1GE and 10GE?
- Is BGP Routing Supported in Direct Connect?
- How Do I Submit a Service Ticket?
- What Are the Network Latency and Packet Loss Rate of a Connection?
- Are the Uplink and Downlink Bandwidths of a Direct Connect Connection the Same?
- What Do I Do If I Select the Wrong Carrier When Creating a Connection?
- How Do I Plan the VPCs for a New Connection?
- What Are Local and Remote Gateways (Interconnection IP Addresses)?
- How Do I Configure BFD for a Connection?
- Leased Line
-
Interconnection with the Cloud
- Can I Access the Same VPC over Multiple Connections?
- How Do I Plan the CIDR Blocks for a Connection?
- What Should I Consider When I Use Direct Connect to Access the Cloud?
- Does Direct Connect Support NAT?
- Can the VLAN of the On-premises Network Be Used in the VPC Through Direct Connect?
- Can My On-Premises Data Center Access Multiple VPCs Through One Connection?
- Can Direct Connect Be Used with Similar Services of Other Cloud Service Providers?
-
Networking and Scenarios
- Can Multiple Connections Access the Same VPC?
- Can My On-Premises Data Center Access Multiple VPCs Through One Connection?
- Can Direct Connect Be Used with Similar Services of Other Cloud Service Providers?
- Can I Limit the Bandwidth Available on Each Hosted Connection?
- How Do I Plan the VPCs for a New Connection?
-
Related Console Operations
- How Do I Submit a Service Ticket?
- How Can I Unsubscribe from Direct Connect?
- What Parameters Can Be Modified After I Have Created a Virtual Interface?
- Do I Need to Delete the Virtual Gateway and Virtual Interface Before Deleting a Hosted Connection?
- How Do I Change the Routing Mode of a Connection?
- How Do I Delete a Hosted Connection?
- What Is the BGP ASN Used by Huawei Cloud?
- What Are Local and Remote Gateways (Interconnection IP Addresses)?
- Troubleshooting
- Billing
- Resource Monitoring
- Quota
-
Popular Questions
Network Quality Metrics (Plug-ins Required)
The network quality of connections is monitored using two plug-ins, and there are two key metrics: network latency and packet loss rate.
Direct Connect provides two monitoring plug-ins:
- dc-nqa-collector: monitors the connections requested on the Direct Connect console.
- history-dc-nqa-collector: monitors historical connections.
For details, see Installing the Direct Connect Metric Collection Plug-ins.
- Automated connections are requested using the console and can be self-service or full-service connections. Each connection has at least a virtual gateway and a virtual interface, and their routes are automatically advertised. Connections in most regions are automated connections.
- Historical connections are requested by email or phone. They do not have virtual gateways and virtual interfaces, and their routes must be configured manually. Historical connections exist only in some regions.
Constraints
- For each virtual interface, only one VM can be configured for monitoring, or monitoring data may fail to be reported.
- No images can be configured for the VM where the Direct Connect monitoring plug-ins are installed, or monitoring data may fail to be reported.
- The VM where the Direct Connect monitoring plug-ins are installed must be in the same account and region as the virtual interface.
Procedure
- Configure the Direct Connect plug-ins.
For details, see Installing Direct Connect Metric Collection Plug-ins.
- Configure the return route for the detection source IP address in the on-premises data center.
Example route (A Huawei-developed device is used an example.)
ip route-static 192.168.1.100 255.255.255.255 10.0.0.1
NOTE:
This is to add a return route whose destination is the detection source IP address used in the on-premises data center and next hop is the local gateway configured on the corresponding virtual interface. This ensures that the return packets from the on-premises data center can reach the detection source in the VPC through the correct path.
Metrics
ID |
Metric Name |
Description |
Value Range |
Monitored Object |
Monitoring Interval |
---|---|---|---|---|---|
latency |
Latency |
Network latency of a connection Unit: ms |
≥ 0 ms |
Connections and historical connections |
1 minute |
packet_loss_rate |
Packet Loss Rate |
Packet loss rate of a connection Unit: Percentage |
0–100% |
Connections and historical connections |
1 minute |
Dimensions
Key |
Value |
---|---|
virtual_interface_id |
Virtual interface (associated with an automated connection) |
history_direct_connect_id |
Historical connection |
Helpful Links
You can delete the plugins directory to delete the installed plug-ins based on your service requirements.
Command:
cd /usr/local/uniagent/extension/install/telescope/ rm -rf plugins/
Example:
The plugins directory is automatically created when the plug-ins are installed. Deleting this directory does not affect your services.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.