Error Codes
Description
If an error occurs when an API is called, error information is returned. This section describes the error information for VPC APIs (excluding native OpenStack APIs).
Example of Returned Error Information
{
"code": "VPC.0002",
"message": "Available zone Name is null."
} Error Code Description
If an error code starting with APIGW is returned after you call an API, rectify the fault by referring to the instructions provided in Error Codes.
| Module | Status Code | Error Code | Message | Description | Handling Measure |
|---|---|---|---|---|---|
| Public | 400 | VPC.0002 | AZ name is null. | The AZ is left blank. | Check whether the availability_zone field in the request body for creating a subnet is left blank. |
| 404 | VPC.0003 | VPC does not exist. | The VPC does not exist. | Check whether the VPC ID is correct or whether the VPC exists under the tenant. | |
| 400 | VPC.0004 | VPC is not active. Try again later. | The VPC status is abnormal. | Try again later or contact technical support. | |
| 401 | VPC.0005 | Lack of user authority. | User restricted. | Check whether the account is in arrears or has not applied for the OBT permission. | |
| 401 | VPC.0009 | Real-name authentication failed. | Real-name authentication fails. | Contact technical support. | |
| Public | 400 | VPC.0007 | Inconsistent tenant IDs. | Inconsistent tenant IDs. | The tenant ID in the URL is different from that parsed in the token. |
| 401 | VPC.0008 | Invalid token in the header. | Invalid token. | Check whether the token in the request header is valid. | |
| 403 | VPC.2701 | Token is not allowed to do this action. | You do not have permission to perform this operation, or your account balance is insufficient. | Check whether the account balance is insufficient or whether your account has been frozen. | |
| Public | 403 | VPC.0010 | Insufficient permissions to call the underlying system. | Insufficient permissions to make calls to the underlying system. | Obtain the required permissions. |
| 403 | VPC.2201 | Policy doesn't allow <x:x:x> to be performed | Insufficient fine-grained permissions. | Obtain the required permissions. | |
| Public | 400 | VPC.0014 | The enterprise project is unavailable. | The enterprise project is unavailable. | Use the ID of another available enterprise project. |
| 400 | VPC.0011 | Invalid enterprise project ID. | Invalid enterprise project ID. | Enter a valid enterprise project ID. | |
| Creating a port | 400 | VPC.2500 | Invalid parameter. | Invalid port parameter. | Check whether the parameter values are valid based on the returned error message and API reference document. |
| 409 | VPC.0701 | IP is in use | The IP address of the port has been used. | Change the IP address. | |
| 409 | VPC.2511 | Quota exceeded for resources: ['vip']. | The maximum number of virtual IP addresses has been reached. | Delete virtual IP addresses that are no longer required. | |
| 500 | VPC.2502 | The system error. | Calling the backend service fails. | Try again later or contact technical support. | |
| Querying a port | 404 | VPC.2502 | Port xx not found | The port does not exist. | Check whether the port exists. |
| 500 | VPC.2502 | The system error. | An error is returned for the failure to call the backend service. | Check whether the Neutron service is normal or contact technical support. | |
| Querying ports | 404 | VPC.2502 | Port xx not found | The port does not exist. | Check whether the port exists. |
| 500 | VPC.2502 | The system error. | An error is returned for the failure to call the backend service. | Check whether the Neutron service is normal or contact technical support. | |
| Deleting a port | 400 | VPC.2500 | Port's device_id is not empty. | Invalid parameters. | Check whether the parameter values are valid based on the returned error message. |
| 404 | VPC.2502 | Port xx not found | Invalid parameters. | Check whether the port exists. | |
| 500 | VPC.2502 | Neutron Error. | Calling the backend service fails. | Try again later or contact technical support. | |
| Creating a VPC | 400 | VPC.0101 | Invalid VPC parameter values. | VPC parameters are incorrect. | Check whether the parameter values are valid based on the returned error message and API reference document. |
| 409 | VPC.0114 | Quota exceeded for resources: ['router']. | The number of VPCs has reached the maximum allowed limit specified by the quota. | Clear VPC resources that no longer will be used or apply for expanding the VPC resource quota. | |
| 400 | VPC.0115 | The router name exists. | The VPC name already exists. | Change the VPC name. | |
| Querying a VPC | 400 | VPC.0101 | getVpc error vpcId is invalid. | VPC parameters are incorrect. | Ensure that the specified VPC ID is correct. |
| 404/500 | VPC.0105 | Neutron error. | Calling the backend service fails. | Check whether the Neutron service is normal or contact technical support. | |
| 500 | VPC.0106 | get router is null. | An error is returned for the failure to call the backend service. | Check whether the Neutron service is normal or contact technical support. | |
| Querying VPCs | 400 | VPC.0101 | Query vpc list error. | Failed to query the VPCs. | Check whether the parameter values are valid based on the returned error message. |
| 500 | VPC.0105 | Neutron error. | Calling the backend service fails. | Check whether the Neutron service is normal or contact technical support. | |
| 500 | VPC.0106 | The response of router query or getList is null. | The response result of calls to the IaaS OpenStack system is null or empty. | Check whether the Neutron service is normal or contact technical support. | |
| Deleting a VPC | 400/404 | VPC.0101 | Delete router error xx is invalid. | Invalid parameters. | Check whether the parameter values are valid based on the returned error message. |
| 500 | VPC.0102 | Router deletion failed. | The interface fails to obtain the routing resources. | Contact technical support. | |
| 409 | VPC.0103 | Resource status is busy, try it again later. | The VPC cannot be deleted because it is being created. | Contact technical support. | |
| 409 | VPC.0104 | Router contains subnets, please delete subnet first. | The VPC cannot be deleted because it contains subnets. | Delete the subnet in the VPC. | |
| 404/500 | VPC.0105 | Neutron error. | Calling the backend service fails. | Check whether the Neutron service is normal or contact technical support. | |
| 409 | VPC.0107 | Delete the firewall first before deleting the router. | Failed to delete the VPC because it has network ACLs associated. | Delete the network ACLs of the tenant first. | |
| 409 | VPC.0108 | Router is being used and cannot be deleted. | Failed to delete the VPC because it has EIPs associated. | Delete the EIPs of the tenant first. | |
| 409 | VPC.0110 | The VPC cannot be deleted because it is not in the stable status. | The VPC cannot be deleted because its status is unstable. | Contact technical support. | |
| 500 | VPC.0111 | Database error. | An internal VPC exception occurs. | Contact technical support. | |
| 409 | VPC.0112 | Delete the security group first before deleting the router. | The VPC cannot be deleted because it contains security groups. | Delete security groups of the tenant. | |
| 409 | VPC.0118 | ELB exists under this router. Delete ELB first. | The VPC cannot be deleted because it contains load balancers. | Delete load balancers in the VPC. | |
| 500 | VPC.0119 | ELB error. | An error occurred when the VPC service makes calls to the ELB service. | Check whether the ELB service is normal or contact technical support. | |
| 409 | VPC.0120 | Extension routes exist under this router. Delete the routes first. | The VPC cannot be deleted because it contains extension routes. | Delete extension routes in the VPC. | |
| Deleting a VPC | 409 | VPC.0109 | Router is being used and cannot be deleted. | Failed to delete the VPC because one or more VPNs have been created for it. | Delete VPNs of the tenant. |
| Updating a VPC | 400 | VPC.0101 | Update router xx is invalid. | Invalid parameters. | Check whether the parameter values are valid based on the returned error message. |
| 404/500 | VPC.0105 | Neutron error. | Calling the backend service fails. | Check whether the Neutron service is normal or contact technical support. | |
| 500 | VPC.0113 | Router status is not active. | The VPC cannot be updated because the status of the VPC is abnormal. | Try again later or contact technical support. | |
| 400 | VPC.0115 | The router name exists. | The VPC name already exists. | Change the VPC name. | |
| 400 | VPC.0117 | VPC CIDR block cannot contain the subnet CIDR block. | The subnet parameters are invalid. The VPC CIDR block does not contain all its subnet CIDR blocks. | Change the CIDR block of the VPC. | |
| Creating a subnet | 400 | VPC.0201 | Subnet name is invalid. | Incorrect subnet parameters. | Check whether the parameter values are valid based on the returned error message and API reference document. |
| 500 | VPC.0202 | Create subnet failed. | An internal error occurs in the subnet. | Contact technical support. | |
| 400 | VPC.0203 | Subnet is not in the range of VPC. | The CIDR block of the subnet is not in the range of the VPC. | Change the CIDR block of the subnet. | |
| 400 | VPC.0204 | The subnet already exists in the VPC or conflicts with an existing VPC subnet. | The CIDR block of the subnet already exists in the VPC. | Change the CIDR block of the subnet. | |
| 400 | VPC.0212 | Invalid subnet CIDR block. | Invalid subnet CIDR block. | Check whether the subnet CIDR block is valid. | |
| Querying a subnet | 400 | VPC.0201 | Subnet ID is invalid. | Invalid subnet ID. | Check whether the subnet ID is valid. |
| 404/500 | VPC.0202 | Query subnet fail. | Failed to query the subnet. | Contact technical support. | |
| Querying subnets | 400 | VPC.0201 | Query subnets list error. | Failed to query the subnets. | Check whether the parameter values are valid based on the returned error message. |
| 500 | VPC.0202 | List subnets error. | Failed to query the subnets. | Contact technical support. | |
| Deleting a subnet | 400 | VPC.0201 | Subnet ID is invalid. | Invalid subnet ID. | Check whether the parameter values are valid based on the returned error message. |
| 404/500 | VPC.0202 | Neutron error. | An internal error occurs in the subnet. | Contact technical support. | |
| 400 | VPC.0207 | Subnet does not belong to the VPC. | This operation is not allowed because the subnet does not belong to the VPC. | Check whether the subnet is in the VPC. | |
| 500 | VPC.0208 | The subnet cannot be deleted because it has private IP addresses that are being used. | The subnet cannot be deleted because it is being used by the private IP address. | Delete the private IP address of the subnet. | |
| 500 | VPC.0209 | The subnet is being used by an ECS or a load balancer. | The subnet cannot be deleted because it is being used by an ECS or load balancer. | Delete the ECS or load balancer in the subnet. | |
| 500 | VPC.0210 | Subnet has been used by routes, please remove the routes first and try again. | The subnet cannot be deleted because it is being used by the custom route. | Delete the custom route. | |
| 500 | VPC.0211 | The subnet is being used by a load balancer. | The subnet cannot be deleted because it is being used by load balancers. | Delete load balancers in the subnet. | |
| Deleting a subnet | 500 | VPC.0206 | Subnet has been used by VPN, please remove the subnet from the VPN and try again. | The subnet cannot be deleted because it is being used by the VPN. | Delete the subnet that is used by the VPN. |
| Updating a subnet | 400 | VPC.0201 | xx is invalid. | Incorrect subnet parameters. | Check whether the parameter values are valid based on the returned error message. |
| 404/500 | VPC.0202 | Neutron error. | An internal error occurs in the subnet. | Contact technical support. | |
| 500 | VPC.0205 | Invalid subnet status. Try again later. | The subnet cannot be updated because it is being processed. | Try again later or contact technical support. | |
| 400 | VPC.0207 | Subnet does not belong to the VPC. | This operation is not allowed because the subnet does not belong to the VPC. | Check whether the subnet is in the VPC. | |
| Querying quotas | 400 | VPC.1207 | Invalid resource type. | The specified resource type does not exist. | Use an existing resource type. |
| Assigning a private IP address | 500 | VPC.0701 | The IP address is in use. | The private IP address already exists. | Change another private IP address and try again. |
| 400 | VPC.0705 | Invalid IP address for the specified subnet. | Invalid private IP address | Check whether the specified IP address in the request body is within the subnet CIDR block. | |
| 404 | VPC.2204 | Resource query by ID failed. | The resource does not exist or the permission is insufficient. | Check whether the specified subnet in the request body exists or the current account has the permission to query the subnet. | |
| 409 | VPC.0703 | No more IP addresses available on network xxx. | Insufficient IP addresses. | Check whether the subnet has sufficient IP addresses. | |
| Querying a Private IP Address | 404 | VPC.0704 | Resource query by ID failed. | The private IP address does not exist. | Check whether the private IP address exists. |
| Querying Private IP Addresses | 400 | VPC.0702 | Private IP address query error. | Invalid parameters. | Check whether the parameter values are valid based on the returned error message. |
| Releasing a Private IP Address | 404 | VPC.0704 | Resource query by ID failed. | The private IP address does not exist. | Check whether the private IP address exists. |
| 500 | VPC.0706 | Deleting port failed. | An error occurs when the private IP address is being released. | Try again later or contact technical support. | |
| 409 | VPC.0707 | Private IP address is in use. | The private IP address is in use. | Check whether the private IP address is being used by other resource. | |
| Creating a security group | 400 | VPC.0601 | Invalid security group name. | The parameters of the security group are incorrect. | Check whether the parameter values are valid based on the returned error message and API reference document. |
| 500 | VPC.0602 | Add security group fail. | An internal error occurs in the security group. | Check whether the Neutron service is normal or contact technical support. | |
| 409 | VPC.0604 | Quota exceeded for resources: ['security_group']. | Insufficient security group quota. | Delete the security group that is no longer required or apply for increasing the quota. | |
| Querying a security group | 400 | VPC.0601 | Securitygroup id is invalid. | The parameters of the security group are incorrect. | Check whether the security group ID is valid. |
| 500 | VPC.0602 | Query security group fail. | An internal error occurs in the security group. | Check whether the Neutron service is normal or contact technical support. | |
| 404 | VPC.0603 | Security group does not exist. | The security group does not exist. | Check whether the security group ID is correct or whether the security group exists under the tenant. | |
| 404/500 | VPC.0612 | Neutron error. | An internal error occurs in the security group. | Contact technical support. | |
| Querying security groups | 400 | VPC.0601 | Query security groups error limit is invalid. | The parameters of the security group are incorrect. | Check whether the parameter values are valid based on the returned error message and API reference document. |
| 500 | VPC.0602 | Query security groups fail. | An internal error occurs in the security group. | Check whether the Neutron service is normal or contact technical support. | |
| Creating a security group rule | 409 | VPC.0602 | 1.Security group rule already exists. 2.Quota exceeded for resources: ['security_group_rule']. 3.Failed to create the security group rule concurrently. The rule already exists. | The security group rule already exists. Insufficient security group rule quota. Failed to create the security group rule concurrently. The rule already exists. | Change the request body for creating a security group rule. Delete the security group rule that is no longer required or apply for increasing the quota. Check whether the security group rules created concurrently are different from each other. |
| Route table | 400 | VPC.2800 | Invalid route table ID. | Invalid route table parameters. | Ensure that the request parameters are correct. |
| 400/500 | VPC.2801 | Neutron error. | Internal route table error. | Check the request parameters or contact technical support. | |
| 404 | VPC.2802 | Route table not found. | The route table could not be found. | Check whether the route table exists. | |
| 400 | VPC.2803 | Neutron error. | The destination of the route overlaps the subnet. | The destination of the route in the request parameters already exists. | |
| 409 | VPC.2804 | Route table associated with a subnet cannot be deleted. | Failed to delete the route table because it is associated with one or more subnets. | Disassociate the subnets from the route table and try again. | |
| 500 | VPC.2805 | Neutron error. | Failed to change the next hop of the route. | Contact technical support. | |
| 500 | VPC.2806 | Querying subnet ID by network ID failed for illegal argument. | Failed to associate subnets with or disassociate them from the route table. | Contact technical support. | |
| 400 | VPC.2807 | Subnet does not exist or belong to the VPC. Associating route table failed. | The subnet to be associated with the route table does not exist or does not belong to the VPC. | Check the request parameters or change the subnet to one in the VPC of the route table. | |
| 404 | VPC.2808 | Route table not found. | The route table could not be found. | Check whether the route table exists. | |
| 400 | VPC.2809 | Neutron error. | The destination of the route overlaps with that of a system route. | Ensure that the destination in each route is unique. | |
| 400 | VPC.2810 | The VPC cannot support a custom route table. | The current VPC does not support the custom route function. | Change the VPC or contact technical support. | |
| 400 | VPC.2811 | Invalid virtual gateway for route gateway. | The virtual gateway of the current Direct Connect connection has not been associated with any device and the route cannot be delivered. | Select another Direct Connect connection. | |
| 400 | VPC.2812 | Route destination already exists. | The route destination already exists. | Use an available destination. | |
| 400 | VPC.2813 | Insufficient route quota per route table. | The route quota is insufficient. | Increase the route quota or select another route table. | |
| 500 | VPC.2814 | Internal server error. | An internal processing error occurs in the route table. | Contact technical support. | |
| 400 | VPC.2815 | Duplicated destination. | The route destination already exists. | Use an available destination. | |
| 400 | VPC.2816 | Subnet is already bound to the route table. | The subnet has already been associated to a route table. | Disassociate the subnet, and then associate it with another route table. | |
| Resource tags | 400 | VPC.1801 | resource id is invalid. | Incorrect resource ID. | Use a correct resource ID. |
| 400 | VPC.1801 | action is invalid. | Invalid action value. | Ensure that the value of action is create or delete. | |
| 400 | VPC.1801 | Tag length is invalid. The key length must be in range [1,36] and value in range [0,43] | Invalid key length. The key can contain 1 to 36 characters. | Use a valid key value. | |
| 400 | VPC.1801 | Tag length is invalid. The key length must be in range [1,36] and value in range [0,43] | Invalid value length. The value can contain 0 to 43 characters. | Use a value of valid length. | |
| 400 | VPC.1801 | Resource_type xxx is invalid. | Incorrect resource type. | Ensure that the value of resource_type is vpcs. | |
| 400 | VPC.1801 | Tag can not be null. | The tag list contains value null. | Use valid tags. | |
| 400 | VPC.1801 | The list of matches contains null. | The matches list contains value null. | Use valid matches. | |
| 400 | VPC.1801 | Tag value can not be null. | The tags exist, but their values are null. | Use valid tags. | |
| 400 | VPC.1801 | The value of Matches in resourceInstancesReq is null. | The matches exist, and the value is null. | Use valid matches. | |
| 400 | VPC.1801 | number of tags exceeds max num of 10. | The tag list contains more than 10 keys. | Use valid tags. | |
| 400 | VPC.1801 | Tag key is repeated. | The tag list contains duplicate keys. | Use valid tags. | |
| 400 | VPC.1801 | Value of tags in resourceInstancesReq is duplicate. | There are duplicate tag values in the tag list. | Use valid tags. | |
| 400 | VPC.1801 | number of tags exceeds max num of 10. | The tag in the tag list has more than 10 tag values. | Use valid tags. | |
| 400 | VPC.1801 | The key of matches is invalid. | The key in matches is not the resource name. | Use valid matches. | |
| 400 | VPC.1801 | Limit in resourceInstancesReq is invalid. Offset in resourceInstancesReq is invalid. | Invalid limit or offset value. | Use valid limit and offset values. | |
| 400 | VPC.1801 | ResourceInstancesReq is null or invalid. | The tags dictionary structure is missing. | Use a valid tags dictionary structure. | |
| 400 | VPC.1801 | Tag length is invalid. The key length must be in range [1,36] and value in range [0,43] | The key in tags exceeds the maximum length or is left blank. | Use valid keys in tags. | |
| 400 | VPC.1801 | Tag length is invalid. The key length must be in range [1,36] and value in range [0,43] | A value in tags exceeds the maximum length. | Use valid values in tags. | |
| 400 | VPC.1801 | ResourceInstancesReq is null or invalid. | The matches dictionary structure is missing. | Use a valid matches dictionary structure. | |
| 400 | VPC.1801 | The number of Matches in resourceInstancesReq is 0. | The matches are an empty list. | Use a valid matches list. | |
| 400 | VPC.1801 | The value's length of Matches in resourceInstancesReq is more than 255. | The matches list contains tag values that contain more than 255 Unicode characters. | Use a valid matches list. | |
| 500 | VPC.1801 | Invalid input. | Incorrect request body format. | Use the correct request body format. | |
| 404 | VPC.2204 | Query subnet by id fail. | The resource does not exist or the permission is insufficient. | Use an existing resource or obtain required permission. | |
| Querying the network IP address usage | 400 | VPC.2301 | Invalid parameter network_id. | The request parameter is incorrect. | Enter a valid network ID. |
| 400 | VPC.2302 | Network xxx could not be found. | The network is not found. | Ensure that the network ID exists. | |
| Creating a VPC flow log | 400 | VPC.3001 | resource_type/log_store_type/traffic_type/log_group_id/log_topic_id is invalid | Incorrect type or ID. | Check whether the type is supported or whether the ID format is correct. |
| 400 | VPC.3002 | Port does not support flow log, port id : xxx | The VPC flow log does not support this type of port. | Check whether the port is an S3, C3, or M3 ECS NIC port. | |
| 404 | VPC.3002 | Port/Network/Vpc xxx could not be found. | The resource does not exist. | Check whether the resource exists. | |
| 409 | VPC.3004 | Content of flow log is duplicate: resource type xxx, resource id xxx, traffic type all, log group id xxx, log topic id xxx, log store type xxx, log store name xxx. | This VPC flow log already exists. | Modify the parameters of the VPC flow log. | |
| 500 | VPC.3002 | Create flow log by xxx(tenant_id) fail. | Calling the backend service fails. | Try again later or contact technical support. | |
| Querying VPC flow logs | 404 | VPC.3001 | resource could not be found, xxx(listParam) is invalid | Invalid parameters. | Check whether the parameter format is correct. |
| 500 | VPC.3002 | Neutron Error. | Calling the backend service fails. | Try again later or contact technical support. | |
| Querying a VPC flow log | 404 | VPC.3001 | resource could not be found, flowlog id is invalid. | Invalid VPC flow log ID. | Check whether the VPC flow log ID format is correct. |
| 404 | VPC.3002 | Flow log xxx could not be found. | The VPC flow log does not exist. | Check whether the VPC flow log exists or whether its ID is correct. | |
| Updating a VPC flow log | 404 | VPC.3001 | resource could not be found, flowlog id is invalid. | Invalid VPC flow log ID. | Check whether the VPC flow log ID format is correct. |
| 404 | VPC.3005 | Flow log xxx could not be found. | The VPC flow log does not exist. | Check whether the VPC flow log exists or whether its ID is correct. | |
| 500 | VPC.3002 | Update flow log by xxx(tenant_id) fail. | Calling the backend service fails. | Try again later or contact technical support. | |
| Deleting a VPC flow log | 404 | VPC.3001 | resource could not be found, flowlog id is invalid. | Invalid VPC flow log ID. | Check whether the VPC flow log ID format is correct. |
| 404 | VPC.3005 | Flow log xxx could not be found. | The VPC flow log does not exist. | Check whether the VPC flow log exists or whether its ID is correct. | |
| 500 | VPC.3002 | Delete flow log by xxx(tenant_id) fail. | Calling the backend service fails. | Try again later or contact technical support. | |
| Querying a VPC (V3) | 404 | VPC.9904 | Vpc xxx could not be found. | The queried VPC does not exist. | Check whether the VPC to be queried exists. |
| Adding a secondary CIDR block to a VPC (V3) | 400 | VPC.9911 | Invalid CIDR block format. | Invalid CIDR block format. | Enter a valid CIDR block. |
| 400 | VPC.9912 | The number of secondary CIDR blocks to be added exceeds the upper limit. | The number of secondary CIDR blocks to be added exceeds the upper limit. | Check whether there are too many secondary CIDR blocks in the VPC. | |
| 409 | VPC.9914 | The secondary CIDR block conflicts with an existing CIDR block. | The secondary CIDR block conflicts with an existing CIDR block. | Enter a different secondary CIDR block. | |
| 400 | VPC.9916 | The secondary CIDR block overlaps with a blacklisted CIDR block. | The secondary CIDR block overlaps with a blacklisted CIDR block. | Enter a secondary CIDR block that is not blacklisted. For details about the secondary CIDR block blacklist, see the API Reference. | |
| Removing a secondary CIDR block from a VPC (V3) | 404 | VPC.9915 | The secondary CIDR block to be removed not found. | The secondary CIDR block to be removed does not exist. | Enter an existing secondary CIDR block. |
| Querying an IP address group | 404 | VPC.9904 | Address_group xxx could not be found. | The IP address group does not exist. | Check whether the IP address group exists. |
| Creating an IP address group | 400 | VPC.9901 | Duplicate ip_set in request body xxx. | The ip_set request body contains duplicate data. | Ensure that the ip_set request body does not contain duplicate data. |
| 400 | VPC.9901 | Invalid ip_set:xxx parameter in request body. | Invalid data in the value of parameter ip_set. | Ensure that the data in the value of parameter ip_set is valid. | |
| 409 | VPC.9905 | Quota exceeded for resources: 'address_group'. | Insufficient IP address group quota. | Delete the address groups that are not required or increase the quota. | |
| Updating an IP address group | 400 | VPC.9901 | Duplicate ip_set in request body xxx. | The ip_set request body contains duplicate data. | Ensure that the ip_set request body does not contain duplicate data. |
| 400 | VPC.9901 | Invalid ip_set:xxx parameter in request body. | Invalid data in the value of parameter ip_set. | Ensure that the data in the value of parameter ip_set is valid. | |
| 404 | VPC.9904 | Address_group xxx could not be found. | The IP address group to be updated does not exist. | Check whether the IP address group exists. | |
| 409 | VPC.9905 | Quota exceeded for resources: ['address_group_contain_ipset']. | Insufficient IP address group rule quota. | Delete rules that are not required from the IP address group or increase the rule quota. | |
| Deleting an IP address group | 404 | VPC.9904 | Address_group xxx could not be found. | The IP address group to be deleted does not exist. | Check whether the IP address group exists. |
| 409 | VPC.9907 | 1. The IP address group is used by a security group rule.\n2. The IP address group is used by a network ACL rule. | 1. The IP address group is used by a security group rule. 2. The IP address group is used by a network ACL rule. | Check whether the security group rule or network ACL rule is required. If not, use the API for forcibly deleting the IP address group. | |
| Querying a security group (V3) | 404 | VPC.9904 | Security group xxx does not exist. | The security group to be queried does not exist. | Check whether the security group to be queried exists. |
| Creating a security group (V3) | 409 | VPC.9905 | Quota exceeded for resources: security_group. | Insufficient security group quota. | Delete the security groups that are not required or increase the quota. |
| Updating a security group (V3) | 404 | VPC.9904 | Security group xxx could not be found. | The security group to be updated does not exist. | Check whether the security group to be queried exists. |
| Deleting a security group (V3) | 404 | VPC.9904 | Security_group xxx could not be found. | The security group to be deleted does not exist. | Check whether the security group exists. |
| 409 | VPC.9902 | Security group xxx is in use. | The security group to be deleted is associated with a port. | Disassociate the port from the security group and try again. | |
| Querying a security group rule (V3) | 404 | VPC.9904 | Security_group_rule xxx could not be found. | The security group rule to be queried does not exist. | Check whether the security group rule exists. |
| Creating a security group rule (V3) | 409 | VPC.9905 | Quota exceeded for resources: ['security_group_rule']. | Insufficient security group rule quota. | Delete the security group rules that are not required or increase the quota. |
| 404 | VPC.9904 | security_group_id xxx could not be found. | The security group defined by security_group_id does not exist. | Check whether the security group information is correct. | |
| 404 | VPC.9904 | remote security group xxx could not be found. | The security group defined by remote_group_id does not exist. | Check whether the security group information is correct. | |
| 404 | VPC.9904 | Address group xxx does not exist. | The IP address group defined by remote_address_group_id does not exist. | Check whether the IP address group information is correct. | |
| 400 | VPC.9902 | Security group rule for ethertype xxx not supported. Allowed values are [IPv4, IPv6]. | Invalid ethertype value. | Modify the request parameter. Enter a valid ethertype value. Supported values are IPv4 and IPv6, which are case insensitive. | |
| 400 | VPC.9902 | Ethertype xxx and address_group ip_version xxx not match | The ethertype value in the request is inconsistent with the IP version of the IP address group. | Check the IP version of the IP address group defined by remote_address_group_id. The IP address version must be the same as the ethertype value. | |
| 409 | VPC.9902 | Security group rule already exists. Rule id is xxx. | The security group rule already exists. | Ensure that the specified security group rule does not conflict with existing rules. | |
| Deleting a security group rule (V3) | 404 | VPC.9904 | Security_group_rule xxx could not be found. | The security group rule to be queried does not exist. | Check whether the security group rule exists. |
| Inserting a network ACL rule (API V3) | 409 | VPC.9948 | Quota exceeded for composite rule: 'firewall_policy_contain_ipv4_composite_rules'. The number of rules with address_group/discontinuous_ports specified exceeds limit: xxx | The number of IPv4 network ACL rules configured with IP address groups or non-consecutive ports in one direction exceeds the limit. | Delete the network ACL rules that are not required or request a quota increase. |
| 409 | VPC.9949 | Quota exceeded for composite rule: 'firewall_policy_contain_ipv6_composite_rules'. The number of rules with address_group/discontinuous_ports specified exceeds limit: xxx | The number of IPv6 network ACL rules configured with IP address groups or non-consecutive ports in one direction exceeds the limit. | Delete the network ACL rules that are not required or request a quota increase. |
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