هذه الصفحة غير متوفرة حاليًا بلغتك المحلية. نحن نعمل جاهدين على إضافة المزيد من اللغات. شاكرين تفهمك ودعمك المستمر لنا.

Compute
Elastic Cloud Server
Huawei Cloud Flexus
Bare Metal Server
Auto Scaling
Image Management Service
Dedicated Host
FunctionGraph
Cloud Phone Host
Huawei Cloud EulerOS
Networking
Virtual Private Cloud
Elastic IP
Elastic Load Balance
NAT Gateway
Direct Connect
Virtual Private Network
VPC Endpoint
Cloud Connect
Enterprise Router
Enterprise Switch
Global Accelerator
Management & Governance
Cloud Eye
Identity and Access Management
Cloud Trace Service
Resource Formation Service
Tag Management Service
Log Tank Service
Config
OneAccess
Resource Access Manager
Simple Message Notification
Application Performance Management
Application Operations Management
Organizations
Optimization Advisor
IAM Identity Center
Cloud Operations Center
Resource Governance Center
Migration
Server Migration Service
Object Storage Migration Service
Cloud Data Migration
Migration Center
Cloud Ecosystem
KooGallery
Partner Center
User Support
My Account
Billing Center
Cost Center
Resource Center
Enterprise Management
Service Tickets
HUAWEI CLOUD (International) FAQs
ICP Filing
Support Plans
My Credentials
Customer Operation Capabilities
Partner Support Plans
Professional Services
Analytics
MapReduce Service
Data Lake Insight
CloudTable Service
Cloud Search Service
Data Lake Visualization
Data Ingestion Service
GaussDB(DWS)
DataArts Studio
Data Lake Factory
DataArts Lake Formation
IoT
IoT Device Access
Others
Product Pricing Details
System Permissions
Console Quick Start
Common FAQs
Instructions for Associating with a HUAWEI CLOUD Partner
Message Center
Security & Compliance
Security Technologies and Applications
Web Application Firewall
Host Security Service
Cloud Firewall
SecMaster
Anti-DDoS Service
Data Encryption Workshop
Database Security Service
Cloud Bastion Host
Data Security Center
Cloud Certificate Manager
Edge Security
Situation Awareness
Managed Threat Detection
Blockchain
Blockchain Service
Web3 Node Engine Service
Media Services
Media Processing Center
Video On Demand
Live
SparkRTC
MetaStudio
Storage
Object Storage Service
Elastic Volume Service
Cloud Backup and Recovery
Storage Disaster Recovery Service
Scalable File Service Turbo
Scalable File Service
Volume Backup Service
Cloud Server Backup Service
Data Express Service
Dedicated Distributed Storage Service
Containers
Cloud Container Engine
Software Repository for Container
Application Service Mesh
Ubiquitous Cloud Native Service
Cloud Container Instance
Databases
Relational Database Service
Document Database Service
Data Admin Service
Data Replication Service
GeminiDB
GaussDB
Distributed Database Middleware
Database and Application Migration UGO
TaurusDB
Middleware
Distributed Cache Service
API Gateway
Distributed Message Service for Kafka
Distributed Message Service for RabbitMQ
Distributed Message Service for RocketMQ
Cloud Service Engine
Multi-Site High Availability Service
EventGrid
Dedicated Cloud
Dedicated Computing Cluster
Business Applications
Workspace
ROMA Connect
Message & SMS
Domain Name Service
Edge Data Center Management
Meeting
AI
Face Recognition Service
Graph Engine Service
Content Moderation
Image Recognition
Optical Character Recognition
ModelArts
ImageSearch
Conversational Bot Service
Speech Interaction Service
Huawei HiLens
Video Intelligent Analysis Service
Developer Tools
SDK Developer Guide
API Request Signing Guide
Terraform
Koo Command Line Interface
Content Delivery & Edge Computing
Content Delivery Network
Intelligent EdgeFabric
CloudPond
Intelligent EdgeCloud
Solutions
SAP Cloud
High Performance Computing
Developer Services
ServiceStage
CodeArts
CodeArts PerfTest
CodeArts Req
CodeArts Pipeline
CodeArts Build
CodeArts Deploy
CodeArts Artifact
CodeArts TestPlan
CodeArts Check
CodeArts Repo
Cloud Application Engine
MacroVerse aPaaS
KooMessage
KooPhone
KooDrive
Help Center/ Enterprise Switch/ Getting Started/ Step 2: Buy an Enterprise Switch
Updated on 2024-12-09 GMT+08:00

Step 2: Buy an Enterprise Switch

Scenarios

This section describes how to buy an enterprise switch. An enterprise switch allows Layer 2 communication between an on-premises data center and a VPC based on VPN or Direct Connect.

Prerequisites

  • You have planned the resources required both on the cloud and on premises. For details about resource planning, see How Enterprise Switches Work.
  • An enterprise switch establishes a Layer 2 network based on a Layer 3 network between an on-premises data center and a VPC created by Direct Connect or VPN. You need to create a Direct Connect or VPN connection first by referring to Step 1: Use Direct Connect or VPN to Communicate at Layer 3.

Notes and Constraints

  • The switch in an on-premises data center must support VXLAN because the enterprise switch needs to establish a VXLAN tunnel to the data center at Layer 2.
  • The local tunnel subnet must have three IP addresses reserved for the enterprise switch.

Procedure

  1. Go to the Buy Enterprise Switch page.
  2. Configure the parameters as prompted. For details, see Table 1.
    Table 1 Parameters for creating an enterprise switch

    Parameter

    Description

    Example Value

    Billing Mode

    Mandatory

    Enterprise switches can be billed on a yearly/monthly or pay-per-use basis.

    • If you buy a yearly/monthly enterprise switch, you need to make a one-off payment for the enterprise switch in your selected period.
    • If you buy a pay-per-use enterprise switch, your enterprise switch is billed by the second but settled by the hour. If the usage is less than an hour, you are billed based on the actual duration consumed.
    NOTE:

    The yearly/monthly billing mode is available only in regions LA-Santiago and AF-Johannesburg.

    Pay-per-use

    Region

    Mandatory

    Select the region nearest to you to ensure the lowest latency possible.

    LA-Santiago

    Active AZ

    Mandatory

    Enterprise switches are deployed in active/standby mode. Select the AZ where the active node is deployed.

    An active AZ carries traffic. You can set the AZ to the one where your ECSs that need to communicate with an on-premises data center are deployed to ensure quick and uninterrupted access to ECSs.

    AZ1

    Standby AZ

    Mandatory

    Enterprise switches are deployed in active/standby mode. Select the AZ where the standby node is deployed.

    A standby AZ is used for backup and disaster recovery. The standby AZ must be different from the active AZ.

    AZ2

    Specifications

    Mandatory

    Currently, the following enterprise switch specifications are supported:
    • Small
      • Maximum Bandwidth: 3 Gbit/s
      • Maximum PPS: 500,000
      • Connected Subnets: 1
    • Medium
      • Maximum Bandwidth: 5 Gbit/s
      • Maximum PPS: 1,000,000
      • Connected Subnets: 3
    • Large
      • Maximum Bandwidth: 10 Gbit/s
      • Maximum PPS: 2,000,000
      • Connected Subnets: 6

    The specifications cannot be changed after the enterprise switch is created.

    Large

    VPC

    Mandatory

    VPC that the enterprise switch belongs to.

    If Tunnel Connection is set to Direct Connect or VPN, the VPC is set to the one that the Direct Connect virtual gateway or VPN gateway belongs to by default.

    vpc-01

    Tunnel Subnet

    Mandatory

    Subnet of the VPC that the enterprise switch belongs to. It is the local tunnel subnet.

    Local and remote tunnel subnets communicate with each other at Layer 3 over Direct Connect or VPN. Enterprise switches allow communications between cloud and on-premises networks at Layer 2 based on the Layer 3 network between tunnel subnets.

    subnet-01

    Local Tunnel IP Address

    Mandatory

    IP address in the local tunnel subnet, which can be automatically assigned or manually specified.

    If an enterprise switch establishes a VXLAN tunnel with an on-premises data center at Layer 2, each end of the VXLAN tunnel requires a tunnel IP address (the local and remote tunnel IP addresses). The two IP addresses must be different.

    Automatically assign IP address

    Name

    Mandatory

    Enter the name of the enterprise switch. The name:
    • Must contain 1 to 64 characters.
    • Can contain letters, digits, underscores (_), hyphens (-), and periods (.).

    esw-01

    Description

    Optional

    Enter the description of the enterprise switch in the text box as required.

    -

    Required Duration

    Specifies how long an enterprise switch will be used. This parameter is mandatory in yearly/monthly subscriptions.

    2 months

  3. Click Next.
  4. Confirm the enterprise switch information and click Submit.

    This operation takes 3 to 6 minutes to complete. If the status is Running, the enterprise switch is created.

Follow-Up Operations

After an enterprise switch is created, you need to create a Layer 2 connection and configure a remote tunnel gateway. For details, see Getting Started.

We use cookies to improve our site and your experience. By continuing to browse our site you accept our cookie policy. Find out more