Error Codes

Description

If there is an error during API calling, error information is returned. This section describes the error codes contained in the error information for Enterprise Switch APIs.

Response Body Format

{
    "error_msg": "The tunnel number and the remote tunnel IP between the instance's Layer 2 connection are the same",
    "error_code": "l2cg.9935",
    "request_id": "6d09de70c2881ed2a229d512d2342a61"
}

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	Error Message	Description	Solution
Public	409	l2cg.9920	The status of the instance xxx is not active.	The enterprise switch is not running.	Check whether the instance status specified in the request is active. If it is not, try again after the instance status changes to active.
Public	404	l2cg.9923	instance xxx could not be found.	The enterprise switch does not exist.	Check whether the instance ID specified in the request is correct.
Instance	409	l2cg.9907	The instance contains some layer 2 connections, can not be deleted.	The enterprise switch cannot be deleted because it contains Layer 2 connections.	Delete all Layer 2 connections and try again.
	400	l2cg.9941	flavor could not be found: xxx	The enterprise switch flavor does not exist.	Check whether the flavor specified in the request is correct.
	400	l2cg.9901	The instance tunnel ip: xxx is not available.	The tunnel IP address of the enterprise switch is unavailable.	Use an unused IP address and try again.
	409	l2cg.9921	The instance xxx is being built or is being deleted.	The enterprise switch cannot be deleted in the current state.	If the instance status is build, wait until the instance is created and try again.
	409	l2cg.9922	This tunnel subnet: xxx is already used by Layer 2 connection objects: xxx	The tunnel subnet of the enterprise switch cannot be the same as the Layer 2 connection subnet of any enterprise switch.	Replace the tunnel subnet specified in the request body and ensure that the tunnel subnet is not used by any Layer 2 connection.
Layer 2 connection	409	l2cg.9930	The connection xxx is being built and is not allowed to delete.	A Layer 2 connection in the current status cannot be deleted.	Check whether the Layer 2 connection status is pending. If it is, wait until the Layer 2 connection is created and try again.
	404	l2cg.9904	connection xxx in instance xxx could not be found.	The Layer 2 connection does not exist.	Check whether the Layer 2 connection ID in the request is correct.
	403	l2cg.9931	Instance xxx is frozen, not support this operation.	This operation is not allowed because its enterprise switch is frozen.	Wait until the instance status is restored to active and try again.
	409	l2cg.9932	The connection under the instance: xxx has reached its maximum: xxx.	The maximum number of Layer 2 connections on this enterprise switch has been reached.	Use an instance with higher specifications.
	409	l2cg.9933	Layer 2 connection subnet: xxx is the same as the local tunnel subnet in the instance: xxx	This Layer 2 connection subnet cannot be the same as the tunnel subnet of any enterprise switch.	Replace the Layer 2 connection subnet specified in the request body and ensure that the subnet is not used as the tunnel subnet of any enterprise switch.
	409	l2cg.9935	The tunnel number and the remote tunnel IP between the instance's Layer 2 connection are the same	The remote tunnel VNI and tunnel IP address of a Layer 2 connection must be different from any other connection of the same enterprise switch.	Ensure that the remote tunnel VNI and tunnel IP address are different from those of other Layer 2 connections of the same enterprise switch.
	409	l2cg.9936	This subnet: xxx is already used by Layer 2 connection objects: xxx	Each subnet can only be associated with one Layer 2 connection.	Ensure that the subnet specified in the request is not used by other Layer 2 connections.
	404	l2cg.9950	vport xxx could not be found.	The virtual IP address does not exist.	Check whether the virtual IP address specified in the request exists.