All Products
Search

This Product

    Virtual Private Cloud:CreateRouteEntry

    Document Center

    Virtual Private Cloud:CreateRouteEntry

    Last Updated:Jun 17, 2026

    Membuat entri rute kustom pada vRouter atau Virtual Border Router (VBR).

    Deskripsi operasi

    • Operasi CreateRouteEntry bersifat asinkron. Setelah Anda mengirim permintaan, sistem mengembalikan ID instans, tetapi entri rute kustom belum dibuat. Sistem terus menjalankan node di latar belakang. Anda dapat memanggil DescribeRouteEntryList untuk mengueri status rute:

      • Jika rute dalam status Creating, rute sedang dibuat.

      • Jika rute dalam status Created, rute telah dibuat.

    • Operasi CreateRouteEntry tidak mendukung pembuatan entri rute kustom secara bersamaan dalam VPC yang sama atau VBR yang sama.

    • Operasi CreateRouteEntry dapat mengembalikan kode kesalahan TaskConflict dalam skenario bersamaan. Coba ulang operasi sesuai kebutuhan.

    Perhatikan hal-hal berikut saat Anda menggunakan operasi ini untuk menambahkan entri rute kustom ke tabel rute vRouter:

    Catatan

    Jika rute yang akan ditambahkan adalah rute daftar prefiks, kuota perutean dihitung berdasarkan jumlah rute yang ada dan jumlah maksimum entri dalam rute daftar prefiks. Jumlah total tidak boleh melebihi kuota perutean.

    • Sebuah tabel rute dapat berisi hingga 200 entri rute kustom.

    • Blok CIDR tujuan (DestinationCidrBlock) dari entri rute kustom tidak boleh sama dengan blok CIDR vSwitch dalam VPC. Blok CIDR tujuan dapat mencakup blok CIDR vSwitch tetapi tidak boleh tercakup oleh blok CIDR vSwitch.

    • Blok CIDR tujuan (DestinationCidrBlock) dari entri rute kustom dapat berupa blok CIDR yang lebih spesifik daripada blok CIDR rute sistem layanan cloud 100.64.0.0/10, tetapi tidak boleh sama dengan blok CIDR tersebut.

      Penting Rute sistem dengan blok CIDR tujuan 100.64.0.0/10 digunakan untuk komunikasi antar layanan cloud dalam VPC. Berhati-hatilah saat Anda mengonfigurasi rute yang lebih spesifik. Konfigurasi yang salah dapat menyebabkan layanan cloud tidak dapat diakses.
      .

    • Blok CIDR tujuan (DestinationCidrBlock) dari entri rute dalam tabel rute yang sama harus unik.

    • Jika blok CIDR tujuan (DestinationCidrBlock) yang ditentukan adalah alamat IP, blok tersebut diperlakukan sebagai blok CIDR dengan mask 32-bit.

    • Beberapa entri rute kustom dapat mengarah ke next hop (NextHopId) yang sama.

    • Next hop (NextHopId) dari entri rute kustom harus berada dalam VPC yang sama dengan tabel rute.

    • Anda dapat mengonfigurasi perutean ECMP menggunakan pengaturan parameter NextHopList:

      • Untuk menambahkan rute kustom non-ECMP, tentukan parameter DestinationCidrBlock, NextHopType, dan NextHopId. Jangan tentukan parameter NextHopList.

      • Untuk menambahkan rute ECMP, tentukan parameter DestinationCidrBlock dan NextHopList. Jangan tentukan parameter NextHopType atau NextHopId.

    Perhatikan hal-hal berikut saat Anda menggunakan operasi ini untuk menambahkan entri rute kustom ke tabel rute Virtual Border Router (VBR):.

    • Sebuah tabel rute dapat berisi hingga 200 entri rute kustom.

    • Parameter NextHopList tidak didukung.

    • Blok CIDR tujuan (DestinationCidrBlock) dari entri rute kustom dapat berupa blok CIDR yang lebih spesifik daripada blok CIDR rute sistem layanan cloud 100.64.0.0/10, tetapi tidak boleh sama dengan blok CIDR tersebut.

      Penting Rute sistem dengan blok CIDR tujuan 100.64.0.0/10 digunakan untuk komunikasi antar layanan cloud dalam VPC. Berhati-hatilah saat Anda mengonfigurasi rute yang lebih spesifik. Konfigurasi yang salah dapat menyebabkan layanan cloud tidak dapat diakses.

    • Blok CIDR tujuan (DestinationCidrBlock) dari entri rute dalam tabel rute yang sama harus unik.

    • Jika blok CIDR tujuan (DestinationCidrBlock) yang ditentukan adalah alamat IP, blok tersebut diperlakukan sebagai blok CIDR dengan mask 32-bit.

    • Beberapa entri rute kustom dapat mengarah ke next hop (NextHopId) yang sama.

    • Next hop (NextHopId) dari entri rute kustom harus berupa antarmuka vRouter yang terkait dengan VBR.

    • Anda dapat membuat entri rute pada VBR hanya jika VBR dalam status Active, sirkuit Express Connect yang sesuai dalam status Enabled, dan sirkuit tidak dalam kunci pembayaran tertunggak.

    • Hanya entri rute non-ECMP yang didukung. Tentukan parameter DestinationCidrBlock, NextHopType, dan NextHopId. Jangan tentukan parameter NextHopList.

    Coba sekarang

    Coba API ini di OpenAPI Explorer tanpa perlu penandatanganan manual. Panggilan yang berhasil akan secara otomatis menghasilkan contoh kode SDK sesuai dengan parameter Anda. Unduh kode tersebut dengan kredensial bawaan yang aman untuk penggunaan lokal.

    Test

    RAM authorization

    Tabel berikut menjelaskan otorisasi yang diperlukan untuk memanggil API ini. Anda dapat menentukannya dalam kebijakan Resource Access Management (RAM). Kolom pada tabel dijelaskan sebagai berikut:

    • Action: Aksi yang dapat digunakan dalam elemen Action pada pernyataan kebijakan izin RAM untuk memberikan izin guna melakukan operasi tersebut.

    • API: API yang dapat Anda panggil untuk melakukan aksi tersebut.

    • Access level: Tingkat akses yang telah ditentukan untuk setiap API. Nilai yang valid: create, list, get, update, dan delete.

    • Resource type: Jenis resource yang mendukung otorisasi untuk melakukan aksi tersebut. Ini menunjukkan apakah aksi tersebut mendukung izin tingkat resource. Resource yang ditentukan harus kompatibel dengan aksi tersebut. Jika tidak, kebijakan tersebut tidak akan berlaku.

      • Untuk API dengan izin tingkat resource, jenis resource yang diperlukan ditandai dengan tanda bintang (*). Tentukan Nama Sumber Daya Alibaba Cloud (ARN) yang sesuai dalam elemen Resource pada kebijakan.

      • Untuk API tanpa izin tingkat resource, ditampilkan sebagai All Resources. Gunakan tanda bintang (*) dalam elemen Resource pada kebijakan.

    • Condition key: Kunci kondisi yang didefinisikan oleh layanan. Kunci ini memungkinkan kontrol granular, berlaku baik hanya untuk aksi maupun untuk aksi yang terkait dengan resource tertentu. Selain kunci kondisi spesifik layanan, Alibaba Cloud menyediakan serangkaian common condition keys yang berlaku di semua layanan yang didukung RAM.

    • Dependent action: Aksi dependen yang diperlukan untuk menjalankan aksi tersebut. Untuk menyelesaikan aksi tersebut, pengguna RAM atau role RAM harus memiliki izin untuk melakukan semua aksi dependen.

    Action

    Access level

    Resource type

    Condition key

    Dependent action

    vpc:CreateRouteEntry

    create

    *RouteTable

    acs:vpc:{#regionId}:{#accountId}:routetable/{#RouteTableId}

    		 None None

    Parameter permintaan

    Parameter

    Type

    Required

    Description

    Example
    RegionId

    string

    No

    ID wilayah tabel rute.

    Anda dapat memanggil operasi DescribeRegions untuk mengueri ID wilayah.

    cn-hangzhou
    RouteTableId

    string

    Yes

    ID tabel rute yang ingin Anda tambahkan entri rute kustom.

    vtb-bp145q7glnuzd****
    DestinationCidrBlock

    string

    Yes

    Blok CIDR tujuan dari entri rute kustom. Blok CIDR IPv4, blok CIDR IPv6, blok CIDR tujuan daftar prefiks, dan ID instans daftar prefiks didukung. Persyaratan berikut harus dipenuhi:

    • Blok CIDR tujuan tidak boleh mengarah ke atau tercakup oleh 100.64.0.0/10.

    • Blok CIDR tujuan dari entri rute yang berbeda dalam tabel rute yang sama harus unik.

    192.168.0.0/24
    NextHopId

    string

    No

    ID instans next hop dari entri rute kustom.

    Catatan

    Jika Anda mengatur NextHopType ke ECR, Anda dapat memanggil operasi DescribeExpressConnectRouterAssociation untuk mendapatkan AssociationId sebagai ID next hop. -.

    i-j6c2fp57q8rr4jlu****
    ClientToken

    string

    No

    Token klien yang digunakan untuk memastikan idempotensi permintaan.

    Buat nilai parameter dari klien Anda. Pastikan nilainya unik di antara permintaan yang berbeda. Nilai ClientToken hanya dapat berisi karakter ASCII.

    Catatan

    Jika Anda tidak menentukan parameter ini, sistem menggunakan RequestId dari permintaan API sebagai ClientToken. RequestId mungkin berbeda untuk setiap permintaan API.

    02fb3da4-130e-11e9-8e44-001****
    RouteEntryName

    string

    No

    Nama entri rute kustom yang akan ditambahkan.

    Nama harus terdiri dari 1 hingga 128 karakter dan tidak boleh dimulai dengan http:// atau https://.

    test
    Description

    string

    No

    Deskripsi entri rute kustom.

    Deskripsi harus terdiri dari 1 hingga 256 karakter dan tidak boleh dimulai dengan http:// atau https://.

    test
    NextHopType

    string

    No

    Jenis next hop dari entri rute kustom. Nilai yang valid:

    • Instance (default): Instans ECS.

    • HaVip: alamat IP virtual ketersediaan tinggi.

    • RouterInterface: antarmuka vRouter.

    • NetworkInterface: pengontrol antarmuka jaringan (NIC).

    • VpnGateway: gateway VPN.

    • IPv6Gateway: gateway IPv6.

    • NatGateway: gateway NAT.

    • Attachment: transit router.

    • VpcPeer: koneksi peering VPC.

    • Ipv4Gateway: gateway IPv4.

    • GatewayEndpoint: gateway endpoint.

    • Ecr: Express Connect Router (ECR).

    • GatewayLoadBalancerEndpoint: Gateway Load Balancer endpoint (GWLBe).

    Valid values:

    • HaVip :

      HaVip

    • VpnGateway :

      VpnGateway

    • GatewayLoadBalancerEndpoint :

      GatewayLoadBalancerEndpoint

    • VpcPeer :

      VpcPeer

    • Instance :

      Instance

    • NetworkInterface :

      NetworkInterface

    • NatGateway :

      NatGateway

    • Attachment :

      Attachment

    • Ipv4Gateway :

      Ipv4Gateway

    • GatewayEndpoint :

      GatewayEndpoint

    • Ecr :

      Ecr

    • RouterInterface :

      RouterInterface

    • IPv6Gateway :

      IPv6Gateway

    RouterInterface
    NextHopList

    array<object>

    No

    Informasi tentang next hop.

    object

    No

    Informasi tentang next hop.

    NextHopId

    string

    No

    ID instans next hop dari rute ECMP.

    ri-2zeo3xzyf3cd8r4****
    Weight

    integer

    No

    Bobot next hop dari rute ECMP.

    10
    NextHopType

    string

    No

    Jenis next hop dari rute ECMP. Nilai yang valid: RouterInterface (antarmuka router).

    RouterInterface
    DryRun

    boolean

    No

    Menentukan apakah akan melakukan dry run. Nilai yang valid:

    • true: melakukan dry run. Sistem memeriksa parameter yang diperlukan, format permintaan, dan batasan bisnis. Jika permintaan gagal dalam dry run, kesalahan yang sesuai dikembalikan. Jika permintaan lolos dry run, kode kesalahan DryRunOperation dikembalikan.

    • false (default): mengirim permintaan normal, melewati dry run, dan mengembalikan kode status HTTP 2xx. Rute langsung dibuat.

    false

    Elemen respons

    Element

    Type

    Description

    Example

    object

    ID entri rute kustom.

    RouteEntryId

    string

    ID entri rute kustom.

    rte-sn6vjkioxte1gz83z****
    RequestId

    string

    ID permintaan.

    0ED8D006-F706-4D23-88ED-E11ED28DCAC0

    Contoh

    Respons sukses

    JSONformat

    {
  "RouteEntryId": "rte-sn6vjkioxte1gz83z****",
  "RequestId": "0ED8D006-F706-4D23-88ED-E11ED28DCAC0"
}

    Kode kesalahan

    HTTP status code

    Error code

    Error message

    Description
    400 IllegalParam.CidrBlock The specified CidrBlock is illegal. The CidrBlock parameter is invalid.
    400 QuotaExceeded Route entry quota exceeded in this route table.
    400 MissingParameter Miss mandatory parameter.
    400 InvalidCidrBlock.Malformed Specified CIDR block is not valid.
    400 InvalidCIDRBlock.Duplicate Specified CIDR block is already exists.
    400 IncorrectVpcStatus Current VPC status does not support this operation.
    400 IncorrectInstanceStatus Current instance status does not support this operation.
    400 IncorrectRouteEntryStatus Some route entry status blocked this operation.
    400 IncorrectVSwitchStatus The current virtual switch status does not support this operation. The vSwitch is in the pending state and cannot be deleted.
    400 InvalidCidrBlock Specified CIDR block is not valid. Possible causes: 1. You are not in the whitelist of the 10.0.0.0/8 route CIDR block, so you cannot use this CIDR block. 2. The destination CIDR block of the added custom route cannot belong to the CIDR block of all vSwitches under the same VPC. 3. Because 100.64.0.0/10 is a cloud service address, you cannot add this CIDR block pointing to an on-premises IDC. 4. In addition to 100.64.0.0/10, more specific route CIDR blocks such as 100.64.0.0/11 and 100.96.0.0/11 cannot be used for on-premises IDCs.
    400 InvalidNextHop.NotFound Specified next hop does not exist.
    400 InvalidVRouter.NotFound vRouter not exists.
    400 InvalidVPC.NotFound vpc not exists.
    400 InvalidNexthopTypeAndList.BothNull both nexthopType and nextHopList are null.
    400 InvalidNexthopTypeAndList.BothNotNull both nexthopType and nextHopList are not null.
    400 InvalidRouterInterface invalid router interface.
    400 InvalidOppositeRouterType nexthop list cannot only contain router interface whose opposite router interface is on vbr.
    400 InvalidNexthopListSize nexthop size is illegal. Must be between 2 and 4. You must specify 2 to 4 router interfaces as next hops.
    400 InvalidEntryRuleQuota.NotFound Route entry quota rule not exists.
    400 Forbidden.CheckEntryRuleQuota Route entry quota rule check error.
    400 InvalidVBRStatus invalid virtual border router status.
    400 InvalidPhysicalConnectionBusinessStatus invalid physical connection business status.
    400 InvalidRouterType Cannot specify nexthop list in vbr's route table. The specified next hop does not exist in the VBR route table.
    400 IncorrectHaVipStatus This operation is denied because satus of the specified HaVip is neither Available nor InUse. The operation cannot be performed because the HAVIP is in the Available or InUse state.
    400 CountLimitExceed.HaVipRouteEntry The count of route entry to HaVip in one route table is exceeded. The number of routes that point to HAVIPs in the same route table exceeds the upper limit.
    400 InvalidRouteEntry.Duplicate The route entry already exist.
    400 InvalidParam The Ecmp routerEntry with router interfaces local vgw vip not match.
    400 INVALID_WEIGHT_PARAM Specified value of weight invalid
    400 FORBIDDEN_USE_VPC_AS_INTERNET_GATEWAY The Specified CIDR must be in vpc CIDR.
    400 InvalidNexthop The Specified nexthop illegal.
    400 INVALID_VPC_ID The Specified VpcId not match. The VPC does not exist. Check whether the VPC you specified is valid.
    400 InvalidRouteEntrySize The Specified routerEntry size not legal. Equal-cost multi-path (ECMP) routes require 2 to 4 router interfaces as next hops.
    400 TaskConflict The operation is too frequent, please wait a moment and try again. The operation is too frequent. Wait a moment and try again.
    400 InvalidRouteEntry Specified routeEntry not exist.
    400 InvalidDestinationCidrBlock The specified destinationCidrBlock must not included in black list cidr.
    400 Forbidden.VRouterNotFound Specified virtual switch is not found during access authentication.
    400 DefaultValidate.Error validte fail.
    400 Region.NotSupport The specified region does not currently support nextHopType for networkInterface
    400 OperationFailed.NotifyCenCreate Failed to notify cen when create route entry.
    400 Forbidden.PrivateIpNotFound Private ip address not exist.
    400 OperationUnsupported.InactiveMode Vpc multi scope route only support active standby.
    400 InvalidRouteEntryName.Malformed Specified RouteEntry name is not valid. The modification cannot be performed because the specified route entry name is invalid.
    400 IncorrectStatus.MultiScopeRiRouteEntry MultiScope ri status must not in idle.
    400 OperationUnsupported.MoreThanOneVpnOrHavip MultiScope can not support more than one vpn/havip.
    400 OperationUnsupported.EcmpRiTypeOrNumber Emcp entry not supported if vpc-vbr or vbr-vlan ri does not exist.
    400 Duplicated.VpcNextHop Route entry nexthop duplicate. Duplicate next hop of the route entry.
    400 OperationUnsupported.SubRouteTableECMP Vpc subRouteTable don't support ecmp or multiScope.
    400 InvalidNexthop.NotFound VRouterEntry nexthop does not exist.
    400 IllegalParam.NextHopId Instance not exists or not vpc vm.
    400 QuotaExceeded.HaVipRouteEntry Vpc havip route entry quota exceed.
    400 InvalidNexthop.DirectEni The direct Eni cannot be nexthop. A pass-through ENI cannot be used as a next hop.
    400 OperationFailed.InvalidNexthop vpc multi scope route must has a enable nexthop.
    400 OperationFailed.NotifyCenDelete Failed to notify cen when delete route entry.
    400 InvalidNatGateway.NotFound Natgateway not exist.
    400 OperationFailed.CxpRouteExist Cxp route alreay existed.
    400 OperationFailed.GetEniInfo Failed to get networkInterface info.
    400 OperationUnsupported.InvalidRouterInterfaceType Only vpc vbr interface support ecmp route.
    400 InvalidHaVip.NotFound The specified HaVip does not exist in the specified region.
    400 OperationFailed.MultiScopeType The specified nexthop type is not support in multiScope.
    400 OperationFailed.DistibuteLock Distibute lock fail. The operation is locked by another request.
    400 QuotaExceeded.VpnRouteEntry Vpn route entry quota exceeded. Failed to create the route entry because the number of VPN route entries exceeds the upper limit.
    400 InvalidAttachment.NotFound The attachment is not found. The attachment does not exist.
    400 OperationFailed.ActiveNetworkInterfaceNotFound No active network interface is found on the attachment. No available ENI is found on the attachment.
    400 InvalidNetworkInterface.NotFound The network interface is not found on the attachment. The ENI on the attachment does not exist.
    400 OperationFailed.QueryAttachmentInfo Failed to query attachment information. Failed to query the attachment information.
    400 IllegalParam.AttachmentId The attachment is invalid. The attachment is invalid.
    400 OperationFailed.NotSupportIPV6 The specified next hop does not support IPv6. The specified next hop does not support IPv6.
    400 IncorrectStatus.Ipv6Address The IPv6 address of the specified next hop is being assigned or deleted. The IPv6 address of the specified next hop is being created or deleted.
    400 OperationUnsupported.Ipv6EntryOnPrimaryNetworkInterface You cannot create IPv6 route entries on a primary network interface. You cannot create an IPv6 route whose next hop is a primary ENI.
    400 OperationUnsupported.SpecifyIpOnIpv6Entry You cannot specify the private IP address when you create IPv6 route entries. You cannot specify the private IP parameter when you create an IPv6 route.
    400 OperationUnsupported.MutipleIpv6Address You cannot specify a next hop that has bound multiple IPv6 addresses. You cannot specify a next hop that has multiple IPv6 addresses bound to it.
    400 OperationDenied.Ipv6EntryOnCustomTable You cannot create any IPv6 route entry on a custom route table. You cannot create an IPv6 route on a custom route table.
    400 OperationDenied.CloudBoxVbrEntryAllowedInCustomRouteTable The operation is not allowed because only the custom routing table can add a routing entry with the next hop pointing to the cloud box type VBR. The operation is not allowed because only a custom route table can add a route entry whose next hop points to a Cloud Box-type VBR.
    400 OperationDenied.RouteTableAssociateNotCloudBoxVSwitch The operation is not allowed because of the routing table is bound to a non-cloud box type vswitch, and routing entries pointing to the cloud box VBR cannot be added. The operation is not allowed because the route table is bound to a non-Cloud Box vSwitch, and route entries that point to a Cloud Box VBR cannot be added.
    400 OperationDenied.VbrMisMatchCloudBox The operation is not allowed because the routing table is bound to a cloud box vswitch, and routing entries pointing to other cloud box VBRs cannot be added. The operation is not allowed because the route table is bound to a Cloud Box vSwitch, and route entries that point to other Cloud Box VBRs cannot be added.
    400 OperationDenied.VbrIdle The operation is not allowed because the next hop of the added routing entry is a VBR type RI at the opposite end, which cannot be in an idle state. The operation is not allowed because the next hop of the added route entry is a router interface (RI) whose peer is a VBR, and it cannot be in the idle state.
    400 OperationDenied.RouterInterfaceToDifferentVpc The operation is not allowed because the router interface is connected to different VPCs. The operation is not allowed because the router interface is connected to different VPCs.
    400 OperationDenied.RouterInterfaceFromDifferentZones The operation is not allowed because the router interface resides in different zones. The operation is not allowed because the router interfaces reside in different zones.
    400 OperationFailed.PconnTrafficNotEnable The operation is failed because of PconnTrafficNotEnable. The operation failed because outbound traffic is not enabled.
    400 ResourceNotFound.VpcPeer The specified resource of %s is not found. The specified VPC peering connection cannot be found.
    400 IncorrectStatus.VpcPeer The status of %s [%s] is incorrect. The status of %s [%s] is incorrect.
    400 OperationDenied.RouteTableTypeNotPermitted The operation is not allowed because the type of route table is not permitted. The specified type of route table does not allow you to create route entries.
    400 OperationDenied.GatewayRouteTableNotPermitted The operation is not allowed to create a route pointing to this nextHop type on gateway route table. A gateway route table does not support creating a route entry that points to this type of instance.
    400 UnsupportedFeature.VpcPeerIpv6 IPv6 route entries for VPC peering connections cannot be created in this region. The peer of this router interface is a VPC. The current region does not support creating an IPv6 route for this type of next hop.
    400 OperationDenied.VpcIpv6NotEnabled IPv6 has not been enabled for the VPC. The operation is denied because the VPC does not have IPv6 enabled.
    400 IncorrectStatus.Ipv4Gateway The status of Ipv4Gateway is incorrect.
    400 ResourceNotFound.PrefixList The specified resource of prefixList is not found. The specified prefixList does not exist.
    400 UnsupportedFeature.CreatePrefixListEcmpRouteEntry The feature of creating ecmp route entry with prefixList is not supported. Creating an ECMP route by using a prefix list is not currently supported.
    400 OperationDenied.RouterInterfaceIpv6NotEnabled Routerinterface does not support IPv6. The router interface does not support IPv6.
    400 OperationDenied.NextHopTypeNotPermitted The operation is not allowed because the nextHop type is invalid. You cannot create a route whose next hop is of this type.
    400 ResourceAlreadyAssociated.PrefixList The operation failed because the specified prefixList route entry already exists. The operation failed because the prefix list route already exists.
    400 OperationFailed.CidrConflictWithPrefixList The specified CIDR block already exists in a prefixList route entry. The route CIDR block conflicts with an existing prefix list route.
    400 ResourceNotFound.Ipv4Gateway Specified Ipv4Gateway does not exist. The specified IPv4 gateway instance does not exist.
    400 Mismatch.HaVipIdAndRouteTableId The HaVip and RouteTable are mismatched. The specified HAVIP and route table do not belong to the same VPC.
    400 OperationFailed.OperationLocked The operation failed because the nextHop instance is in the O&M lock state. The next hop instance of the route is in the O&M lock state, so the operation cannot be performed.
    400 Mismatch.Ipv4GatewayIdAndRouteTableId The specified IPv4Gateway and RouteTable are not matched. The operation failed because the specified IPv4 gateway and route table do not belong to the same VPC.
    400 OperationUnsupported.DestinationCidrBlockOverlapWithVSwitch The destination IPv6 network segment specified in the route entry overlaps with the vSwitch network segment. The destination IPv6 CIDR block specified in the route entry overlaps with the vSwitch CIDR block.
    400 ResourceNotAssociated.Cen The Vpc and Cen are not associated. The operation failed because the VPC is not attached to this CEN.
    400 IncorrectStatus.CenRelation The status of Vpc in Cen is incorrect. The operation failed because the status of the VPC in the CEN is not stable.
    400 OperationDenied.CenTypeInvalid The operation is not allowed because of Cen type is invalid.. Creating a route in the route table that points to this type of CEN is not supported.
    400 ResourceNotFound.Cen The specified resource of Cen is not found. The operation failed because the specified CEN resource does not exist.
    400 ResourceNotFound.NetworkInterface The specified resource of network interface is not found. The specified ENI does not exist.
    400 RouteConflict.AlreadyExist Route conflict exists in routing table. A route conflict exists in the route table.
    400 IncorrectStatus.RouterInterface The specified RouterInterface status is invalid. The status of the router interface is abnormal.
    400 InvalidNexthop.UnsupportedEniBizType The biz type of NetworkInterface is illegal. The business type of the ENI used as the next hop of the route is invalid.
    400 OperationDenied.RouterInterfaceIpv6 RouterInterface does not support IPv6. The RouterInterface does not support IPv6.
    400 InvalidNextHopType Specified parameter "NextHopType" is not valid. The NextHopType parameter is invalid.
    400 OperationDenied.VbrAttachEcrInMiddleStatus The operation is not allowed because of VBR attach or detach ECR in middle status. The operation cannot be performed because the VBR is in the process of attaching or detaching an ECR. Please try again later.
    400 ResourceNotAssociated.Ecr The ECR is not associated. The current resource is not associated with an ECR, so this operation cannot be performed. Verify the configuration and try again.
    400 UnsupportedFeature.RouterInterfaceIpv6 The feature of ipv6 is not supported for the routerInterface. This router interface does not support IPv6.
    400 InvalidVpnInstanceId.NotFound The specified VPN was not found. The specified VPN instance cannot be found.
    400 OperationFailed.ScopeActiveRouteEntryType Operation failed because the type of the active route entry is not supported. The operation failed because the type of the active route entry is not supported.
    400 OperationFailed.ScopeStandbyRouteEntryQuota Operation failed because the quota for standby route entries in the scope has been exceeded. The operation failed because the quota for standby route entries has been exceeded.
    400 OperationFailed.ScopeActiveRouteEntryQuota Operation failed because the quota for active route entries in the scope has been exceeded. The operation failed because the quota for active route entries has been exceeded.
    400 OperationUnsupported.ScopeInvalidRouteType The specified route type is unsupported. This route type is not supported.
    400 OperationFailed.EcmpInvalidRouterInterfaceOppositeType Operation failed because the opposite type of the router interface is invalid for ECMP configuration. The operation failed because the peer type of the RI is invalid for ECMP.
    400 OperationUnsupported.Ipv6EcmpRouteEntry The EcmpRouteEntry is not supported for IPv6. IPv6 does not support ECMP routes.
    400 OperationUnsupported.Ipv6CidrBlock The specified IPv6 CIDR block is unsupported. This IPv6 CIDR block is not supported.
    400 OperationUnsupported.Ipv6ForVBR IPv6 route entry is not supported for VirtualBorderRouter. VBRs do not support IPv6 routes.
    400 IncorrectStatus.RouteTableStatus The status of the specified RouteTable is incorrect. The specified route table is not in a stable state.
    400 OperationFailed.InvalidNextHopType Operation failed because Ecmp routeEntry has more than one ri entry and can only support one non-ri entry. Failed to create the route entry because an ECMP (Equal-Cost Multipath Routing) route supports only one non-RI entry as the next hop.
    400 UnsupportedRegion The feature is not supported in current region. This feature is not supported in the current region.
    400 UnsupportedFeature.VpcAdvancedFeature The VPC does not support some advanced features. This VPC does not support some advanced features. Submit a ticket for assistance.
    400 OperationDenied.CreateEcmpForPublishedRouteEntry Operation denied because of can not create EcmpRouteEntry for published RouteEntry. A published route does not support creating an active/standby route or a load balancing route.
    400 OperationDenied.TrAttachmentIpv6Disabled The operation is not allowed because tr attachment Ipv6 is disabled. IPv6 is not enabled on the TR attachment.
    400 Mismatch.EniIdAndRouteTableId The operation is not allowed because eni and route table not in same vpc. The operation failed because the specified ENI and route table do not belong to the same VPC.
    400 InvalidDescription.Malformed The Description is illegal. The format of the specified resource description is invalid. The description must be 2 to 256 characters in length and cannot start with http:// or https://.
    400 OperationFailed.InstanceDismatchCurrentVpc The specified instance does not exist in current vpc.
    400 OperationDenied.RouterInterfaceStatusNotAllowed The operation is not allowed because of RouterInterfaceStatusNotAllowed. The status of the router interface is abnormal.
    400 OperationFailed.Ipv6AddressNotBind The specified next hop has no IPv6 address. The next hop of the IPv6 route does not have an IPv6 address.
    400 OperationUnsupported.MultipleIpv6Address Operation unsupported because specific route next hop instance has multiple IPv6 address. 操作不支持，因为指定的路由下一跳实例绑定了多个IPv6地址
    500 VPC.ERROR error code 500,Internal server error.
    500 InternalError The request processing has failed due to some unknown error, exception or failure. An internal error occurred.
    500 IncorrectStatus.Ipv4Gateway The status of Ipv4Gateway is incorrect. The Ipv4Gateway is in an unstable state.
    403 IncorrectInstanceStatus The current status of the resource does not support this operation.
    404 InvalidParameter Instance not exists or not vpc vm
    404 InvalidNatGatewayId.NotFound Specified value of NatGatewayId is not found in our record.
    404 InvalidInstanId.NotFound Specified instance does not exist.
    404 InvalidNextHopId.NotFound Specified next hop does not exist.
    404 InvalidRouteTableId.NotFound Specified route table does not exist.
    404 InvalidHaVipId.NotFound The specified HaVip does not exist in the specified VPC. The HAVIP does not exist in the VPC.
    404 InvalidNetworkInterface.NotFound The specified networkInterface does not exist.
    404 InvalidVpc.NotFound Specified vpc is not found in our record.
    404 InvalidIpv6Gateway.NotFound Specified Ipv6Gateway does not exist.
    404 ResourceNotFound.GatewayLoadBalancerEndpoint GatewayLoadBalancerEndpoint instance not found. The GatewayLoadBalancerEndpoint instance cannot be found.

    Lihat Error Codes untuk daftar lengkap.

    Catatan rilis

    Lihat Release Notes untuk daftar lengkap.