All Products
Search
Document Center

Virtual Private Cloud:CreateDefaultVSwitch

Last Updated:Dec 06, 2023

Creates a default vSwitch.

Operation Description

Usage notes

When you call this operation, take note of the following items:

  • The first IP address and last three IP addresses of a default vSwitch CIDR block are reserved. For example, if the CIDR block of a vSwitch is 192.168.1.0/24, the IP addresses 192.168.1.0, 192.168.1.253, 192.168.1.254, and 192.168.1.255 are reserved.

  • The number of instances in the default vSwitch cannot exceed the remaining number of instances supported by the VPC (15,000 minus the number of existing instances).

  • Default vSwitches do not support multicasting or broadcasting.

  • After you create a default vSwitch, you cannot modify its CIDR block.

  • CreateDefaultVSwitch is an asynchronous operation. After a request is sent, the system returns a request ID and runs the task in the background. You can call the DescribeVSwitchAttributes operation to query the status of a default vSwitch:

    • If a default vSwitch is in the Pending state, it is being configured.
    • If a default vSwitch is in the Available state, it is available.
  • If a default vSwitch already exists in a region, you cannot call this operation to create a default vSwitch in this region.

  • Before you create a default vSwitch, make sure that a default VPC is created. You can call the CreateDefaultVpc operation to create a default VPC.

debugging

You can run this interface directly in OpenAPI Explorer, saving you the trouble of calculating signatures. After running successfully, OpenAPI Explorer can automatically generate SDK code samples.

debugging

Authorization information

The following table shows the authorization information corresponding to the API. The authorization information can be used in the Action policy element to grant a RAM user or RAM role the permissions to call this API operation. Description:

  • Operation: the value that you can use in the Action element to specify the operation on a resource.
  • Access level: the access level of each operation. The levels are read, write, and list.
  • Resource type: the type of the resource on which you can authorize the RAM user or the RAM role to perform the operation. Take note of the following items:
    • The required resource types are displayed in bold characters.
    • If the permissions cannot be granted at the resource level, All Resources is used in the Resource type column of the operation.
  • Condition Key: the condition key that is defined by the cloud service.
  • Associated operation: other operations that the RAM user or the RAM role must have permissions to perform to complete the operation. To complete the operation, the RAM user or the RAM role must have the permissions to perform the associated operations.
OperationAccess levelResource typeCondition keyAssociated operation
vpc:CreateDefaultVSwitchWrite
  • VSwitch
    acs:vpc:{#regionid}:{#accountId}:vswitch/*
    none
none

Request parameters

ParameterTypeRequiredDescriptionExample
ZoneIdstringYes

The zone ID of the default vSwitch.

You can call the DescribeZones operation to query the most recent zone list.

cn-hangzhou-b
RegionIdstringYes

The region ID of the default vSwitch.

You can call the DescribeRegions operation to query the most recent region list.

cn-hangzhou
Ipv6CidrBlockintegerNo

The last eight bits of the IPv6 CIDR block of the vSwitch. Valid values: 0 to 255.

12
ClientTokenstringNo

The client token that is used to ensure the idempotence of the request.

You can use the client to generate the token, but you must make sure that the token is unique among different requests. The token can contain only ASCII characters.

Note If you do not set this parameter, the system automatically uses the request ID as the client token. The request ID may be different for each request.
0c593ea1-3bea-11e9-b96b-88e9fe63****

Response parameters

ParameterTypeDescriptionExample
object

The ID of the default vSwitch.

VSwitchIdstring

The ID of the default vSwitch.

vsw-bp1a4b5qhmxftjimq****
RequestIdstring

The request ID.

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

Examples

Sample success responses

JSONformat

{
  "VSwitchId": "vsw-bp1a4b5qhmxftjimq****",
  "RequestId": "0ED8D006-F706-4D23-88ED-E11ED28DCAC0"
}

Error codes

HTTP status codeError codeError messageDescription
400InvalidDescription.MalformedInvalid description.-
400InvalidVSwitchName.MalformedSpecified virtual switch name is not valid.The format of the specified vSwitch name is invalid. Specify the name in the valid format.
400InvalidVSwitchDiscription.MalformedSpecified virtual switch description is not valid.The vSwitch description is invalid.
400Abs.Vpc.InvalidDescription.MalformedSpecified virtual switch name is not valid.-
400ResourceNotAvailableResource you requested is not available in this region or zone.You cannot create a vSwitch in the current region or zone.
400InvalidParameterSpecified CIDR block is not valid in VPC.The CIDR block does not fall within the VPC CIDR block.
400InvalidCidrBlock.OverlappedSpecified CIDR block overlapped with other subnets.The vSwitch CIDR block overlaps with another vSwitch CIDR block or with the destination CIDR block of a custom route entry. Try a different CIDR block that is not in use.
400InvalidCidrBlock.OverlappedSpecified CIDR block overlapped with other entry.The specified CIDR block overlaps the CIDR block of another VPC or a custom routing destination. Select a CIDR block that is not used.
400QuotaExceeded.VSwitchVirtual switch quota exceeded.The number of vSwitches has reached the upper limit. Reduce the number of vSwitches and try again later.
400IncorrectRouteEntryStatusSome route entry status blocked this operation.The operation is not supported because the route table contains routes in the Pending or Modifying state.
400IncorrectVSwitchStatusSome virtual switch is modifying within the same VPC.Multiple vSwitches are in the Modifying state in the same VPC. Try again later.
400InvalidCirdrBlock.MaskLengthSpecified CIDR block is not valid .Invalid CIDR block.
400IncorrectVpcStatusCurrent VPC status does not support this operation.This operation cannot be performed when the VPC is in the current state.
400CreateVSwitch.IncorrectStatus.cbnStatusCurrent CBN status does not support this operation.You cannot create a vSwitch when the CEN instance is in the current state.
400InvalidCidrBlock.MalformedSpecified CIDR block is not valid.The format of the CIDR block is invalid.
400MissingParameterMiss mandatory parameter.Some required parameters are not specified. Specify all required parameters and try again.
400IncorrectVSwitchStatusVSwitch Creation simultaneously is not supported.The system failed to create the vSwitch and one or more vSwitches that belong to the VPC are in the Creating state.
400TaskConflictThe operation is too frequent, TaskConflict.The system is unavailable. Try again later.
400VPC.SWITCH.RULE.QUOTA.NOT.EXISTSvSwitch quota rule not exists.-
400Forbidden.VpcNotFoundSpecified VPC can not found.The specified VPC does not exist.
400RouteConflict.AlreadyExistRoute conflict exists in routing table.Route conflicts exist in the route table.
400OperationFailed.CidrAcrossClassic link instance cidr must not across.-
400Duplicated.ClientToken%s-
400OperationFailed.Ipv6CidrBlockExisted%s-
400IllegalParam.Ipv6CidrBlock%s-
400OperationFailed.VpcIpv6Disabled%s-
400IncorrectStatus.cbnStatusCurrent CBN status does not support this operation.The status of the CEN instance is invalid.
400OperationFailed.DefaultVpcNotExist%s-
400UnsupportedFeature.CloudBoxIpv6The IPv6 feature is not supported by cloud box.You cannot create an IPv6 address for a CloudBox instance.
400OperationDenied.VpcPeerExistThe operation is not allowed because the VPC peer exists.The operation failed because VPC peering connections exist.
400OperationDenied.CenAttachedThe operation is not allowed because the VPC is attached to CEN.The operation is not allowed because the VPC is attached to a CEN instance.
400OperationDenied.NatgwExistThe operation is not allowed because the NAT gateway exists in VPC.The operation is not allowed because NAT gateways exist in the VPC.
400OperationDenied.OtherSubnetCreatingother subnet is creating-
400OperationFailed.DefaultVSwitchExistA default vSwitch already exists in the zone.The error message returned because the default vSwitch already exists in the current zone.
404Invalid.NotExistwitch mask rule not exists.-
404InvalidStatus.RouteEntryRouteEntry status error.-
404InvalidZoneId.NotFoundSpecified zone does not exist.The zone ID is invalid.
404InvalidVpcId.NotFoundSpecified VPC does not exist.The specified VPC does not exist.

For a list of error codes, visit the Service error codes.