Keyword

ADD_COS_SERVICE_OP

Message text

Added service: $1

Variable fields

$1: Northbound service request body.

Example

Added service:{

"service":{

"serviceName":"dddddddddddddddddsgfdgh",

"description":"",

"packageId":"a473fba9-3c88-48e9-b5d5-7fcf5fe4bce1",

"custom.json":"{\n    \"resourcePool\": \"XXG\"\n}"

}

}

Explanation

A northbound service was added.

Possible failure causes

·     Invalid UUID.

·     The request body cannot be empty.

·     The description can contain up to 512 characters.

·     The custom.json cannot be empty.

·     The name can contain up to 64 characters.

·     Please specify a packageId.

·     Please specify a name.

·     The custom.json contains invalid contents.

·     The specified custom package file does not exist.

·     The custom package file is in use.

·     The custom.json file in the package contains invalid contents.

·     The custom.json file must contain all customized keys.

·     The regist-info.json file does not exist in the package.

·     The regist-info.json file in the package is invalid.

·     The specified python script does not exist in the package.

·     The name must be different in the regist-info.json file in the package.

·     The name and requestMethod cannot be same at the same time in the regist-info.json file in the package.

·     The name is required in the regist-info.json file in the package.

·     The name cannot exceed 64 characters in the regist-info.json file in the package.

·     The pythonPath is required in the regist-info.json file in the package.

·     The pythonPath cannot exceed 512 characters in the regist-info.json file in the package.

·     The uri is required in the regist-info.json file in the package.

·     The uri cannot exceed 512 characters in the regist-info.json file in the package.

·     The requestMethod is required in the regist-info.json file in the package.

·     The requestMethod cannot exceed 10 characters in the regist-info.json file in the package.

·     The requestMethod is invalid in the regist-info.json file in the package.

·     The service interface already exists.

·     Failed to obtain gateway routes.

·     The URLs in the regist-info.json file cannot overlap with the existing gateway routes.

·     Failed to register the gateway route.

·     Failed to register the authentication-free URL.

·     Invalid cron field in the crontabs.json file.

·     The crontabs.json contains invalid contents.

·     The site does not exist.

·     Duplicate sites.

·     Failed to add the service.

·     Internal server error.

·     A service already exists with the specified name.

·     In the regist-info.json custom package file, the value for the uri field must start with a slash (/), and you must specify a hierarchical path.

·     In the regist-info.json custom package file, the hierarchical path specified for the pythonPath field can contain digits, letters, underscores (_), and hyphens (-), and cannot contain spaces.

·     You have no privilege to perform the operation.

·     The background-process.json file in the package is invalid.

·     A name field value cannot exceed 64 characters in the background-process.json file in the package.

·     The name field is required in the background-process.json file in the package.

·     The pythonPath field is required in the background-process.json file in the package.

·     A pythonPath field value cannot exceed 512 characters in the background-process.json file in the package.

·     In the background-process.json custom package file, the hierarchical path specified for the pythonPath field can contain digits, letters, underscores (_), and hyphens (-), and cannot contain spaces.

·     The value of each pythonPath field must be unique in the background-process.json file in the package.

·     An expression description can contain up to 512 characters.

Keyword

UPDATE_COS_SERVICE_OP

Message text

Updated service: $1

Variable fields

$1: UUID of the northbound service.

Example

Updated service: d6c1057d-bded-497d-892d-b6ba13a30892

Explanation

A northbound service was edited.

Possible failure causes

·     Invalid UUID.

·     The service does not exist.

·     The request body cannot be empty.

·     The description can contain up to 512 characters.

·     The custom.json cannot be empty.

·     The custom.json contains invalid contents.

·     The custom.json file must contain all customized keys.

·     Invalid cron field in the crontabs.json file.

·     The crontabs.json contains invalid contents.

·     The site does not exist.

·     Duplicate sites.

·     Failed to update the service.

·     Internal server error.

·     You have no privilege to perform the operation.

Keyword

DEL_COS_SERVICE_OP

Message text

Deleted service: $1

Variable fields

$1: UUID of the northbound service.

Example

Deleted service: 25e0bdb3-7b52-4d4b-a8d8-8691a67d477e

Explanation

A northbound service was deleted.

Possible failure causes

·     Invalid UUID.

·     The service does not exist.

·     Failed to delete the gateway route.

·     Failed to delete the authentication-free URL.

·     Failed to delete the service.

·     Internal server error.

·     You have no privilege to perform the operation.

Keyword

UPLOAD_COS_PACKAGE_OP

Message text

Uploaded package: $1

Variable fields

$1: Name of the custom package.

Example

Uploaded package: SUPER_CONTROLLER_COS_OM-E3103P01.zip

Explanation

A custom package was uploaded.

Possible failure causes

·     The custom.json contains invalid contents.

·     The version.json contains invalid contents.

·     The custom package name cannot be empty.

·     Invalid JSON format.

·     The custom package version is required in the version.json file in the package.

·     The custom package version cannot exceed 64 characters in the version.json file in the package.

·     The description cannot exceed 512 characters in the version.json file in the package.

·     The custom package name cannot exceed 64 characters in the version.json file in the package.

·     Failed to upload the custom package file.

·     The version.json cannot be empty.

·     The custom.json cannot be empty.

·     The custom.json file does not exist in the package.

·     The version.json file does not exist in the package.

·     The name must start with a letter, digit, or underscore (_). The name can contain at signs (@), left parentheses ((), right parentheses ()), plus signs (+), minus signs (-), dots (.), equal signs (=), left braces ({), and right braces (}), and it cannot contain spaces. The name can contain up to 512 characters.

·     Invalid cron field in the crontabs.json file.

·     The custom package must be in the ZIP format.

·     Failed to serialize custom package file.

·     Invalid custom package file.

·     Another custom package already exists with the specified name.

·     Internal server error.

·     You have no privilege to perform the operation.

Keyword

DEL_COS_PACKAGE_OP

Message text

Deleted package: $1

Variable fields

$1: UUID of the custom package.

Example

Deleted package: 99e6a089-e51a-4a22-92d9-9f73d93902b6

Explanation

A custom package was deleted.

Possible failure causes

·     Invalid UUID.

·     The specified custom package file does not exist.

·     The custom package file is in use.

·     Failed to delete the custom package file.

·     Internal server error.

·     You have no privilege to perform the operation.

Keyword

UPGRADE_SERVICE_OP

Message text

Upgraded service: $1

Variable fields

$1: UUID of the custom package.

Example

Upgraded service:{

"service":{

"id":" a123fba9-3c88-48e9-b5d5-7fcf5fe4bce1",

"packageId":"a473fba9-3c88-48e9-b5d5-7fcf5fe4bce1",

"custom.json":"{\n    \"resourcePool\": \"XXG\"\n}"

}

}

Explanation

A custom package was upgraded.

Possible failure causes

·     Please specify a service id.

·     The specified custom package file does not exist.

·     The custom package file is in use.

·     The custom package has been specified for the service.

·     Failed to upgrade the service.

·     Internal server error.

·     You have no privilege to perform the operation.

·     The background-process.json file in the package is invalid.

·     A name field value cannot exceed 64 characters in the background-process.json file in the package.

·     The name field is required in the background-process.json file in the package.

·     The pythonPath field is required in the background-process.json file in the package.

·     A pythonPath field value cannot exceed 512 characters in the background-process.json file in the package.

·     In the background-process.json custom package file, the hierarchical path specified for the pythonPath field can contain digits, letters, underscores (_), and hyphens (-), and cannot contain spaces.

·     The value of each pythonPath field must be unique in the background-process.json file in the package.

·     An expression description can contain up to 512 characters.

Keyword

UPDATE_PARAMETER_CONFIG_OP

Message text

Updated parameter settings: $1

Variable fields

$1: UUID of the custom package.

Example

Updated parameter settings: {

  "configs":[{

    "key": "sftpServerIP",

    "value":"192.158.50.9"

  } ]

}

Explanation

Parameter settings were edited.

Possible failure causes

·     Invalid SFTP server IP address. An IPv4 address must be in dotted decimal notation, and an IPv6 address must be in colon hexadecimal notation.

·     Invalid SFTP server port.

·     SFTP server user name cannot be empty.

·     The SFTP server password failed to be encrypted.

·     Internal server error.

·     You have no privilege to perform the operation.

Keyword

ADD_SNMPv3_SERVER_OP

Message text

Added SNMPv3 server: $1

Variable fields

$1: SNMPv3 server request body.

Example

Added SNMPv3 server: {

        "serverIp": "192.158.50.9",

        "serverPort":"162",

        "securityName":"admin",

        "authProtocol":"MD5",

        "authPassword":"":"********"",

        "privProtocol":"DES",

        "privPassword":"********"

 }

Explanation

An SNMPv3 server was added.

Possible failure causes

·     Failed to add the SNMPv3 server.

·     An SNMPv3 server already exists with the specified IP address.

·     Please specify an IP address.

·     Invalid SNMPv3 server IP address. An IPv4 address must be in dotted decimal notation, and an IPv6 address must be in colon hexadecimal notation.

·     The SNMP server IP must be an IPv4 address in dotted decimal notation.

·     Please specify a port number.

·     Please specify a security name.

·     The port number must be an integer in the range of 1 to 65535.

·     The security name is a string up to 32 characters that can contain only letters, digits, and underscores (_).

·     The encryption algorithm can only be DES, 3DES, AES128, AES192, or AES256.

·     The authentication algorithm can only be MD5, SHA-1, SHA-224, SHA-256, SHA-384, or SHA-512.

·     The encryption password must be a string of 8 to 64 characters that cannot contain chinese characters, wavy lines(~), question marks (?), and spaces.

·     The authentication password must be a string of 8 to 64 characters that cannot contain chinese characters, wavy lines(~), question marks (?), and spaces.

·     The authentication algorithm has been specified. Please specify an authentication password.

·     The encryption algorithm has been specified. Please specify an encryption password.

·     You cannot specify an encryption password if no encryption algorithm is specified.

·     You cannot specify an authentication password if no authentication algorithm is specified.

·     You cannot specify an encryption algorithm if no authentication algorithm is specified.

·     You have no privilege to perform the operation.

Keyword

UPDATE_SNMPv3_SERVER_OP

Message text

Updated SNMPv3 server: $1

Variable fields

$1: SNMPv3 server request body.

Example

Updated SNMPv3 server: {

"id":"e1aeb2f8-0463-40cc-bf8e-4c7e25a157b5",

"serverIp":"3.3.3.3",

"serverPort":"33",

"securityName":"fdsfds",

"authProtocol":"MD5",

"authPassword":"********",

"privProtocol":"AES128",

"privPassword":"********"

}

Explanation

An SNMPv3 server was edited.

Possible failure causes

·     Failed to edit the SNMPv3 server.

·     The specified SNMPv3 server does not exist.

·     Please specify a port number.

·     Please specify a security name.

·     The port number must be an integer in the range of 1 to 65535.

·     The security name is a string up to 32 characters that can contain only letters, digits, and underscores (_).

·     The encryption algorithm can only be DES, 3DES, AES128, AES192, or AES256.

·     The authentication algorithm can only be MD5, SHA-1, SHA-224, SHA-256, SHA-384, or SHA-512.

·     The encryption password must be a string of 8 to 64 characters that cannot contain chinese characters, wavy lines(~), question marks (?), and spaces.

·     The authentication password must be a string of 8 to 64 characters that cannot contain chinese characters, wavy lines(~), question marks (?), and spaces.

·     The authentication algorithm has been specified. Please specify an authentication password.

·     The encryption algorithm has been specified. Please specify an encryption password.

·     You cannot specify an encryption password if no encryption algorithm is specified.

·     You cannot specify an authentication password if no authentication algorithm is specified.

·     You cannot specify an encryption algorithm if no authentication algorithm is specified.

·     You have no privilege to perform the operation.

·     Invalid UUID.

Keyword

DEL_SNMPv3_SERVER_OP

Message text

Deleted SNMPv3 server: $1

Variable fields

$1: UUID of the SNMPv3 server.

Example

Deleted SNMPv3 server: d6c1057d-bded-497d-892d-b6ba13a30892

Explanation

An SNMPv3 server was deleted.

Possible failure causes

·     Failed to delete the SNMPv3 server.

·     The specified SNMPv3 server does not exist.

·     You have no privilege to perform the operation.

·     Invalid UUID.

Message text

Imported DC resource: $1

Variable fields

$1: Request message body.

Example

Imported DC resource: {"siteId":"379c30f1-4059-41c4-b8ae-722d7d187378"}

Explanation

A DC site resource was imported.

Possible failure causes

·     The site with the specified UUID does not exist.

·     Failed to connect to the site.

·     The itom-cmdb-rs-svc service has exceptions.

Message text

Added network “$1”, request: $2

Variable fields

$1: UUID of the vNetwork.

$2: vNetwork request message body.

Example

Added network "2eeafe60-adf0-bab9-61d9-63bb481447d3", request: {"network":{"id":"2eeafe60-adf0-bab9-61d9-63bb481447d3","name":"network222","description":"","tenant_id":"edc2b3ec-ce4c-5576-470a-2813f24fcd46","position_x":104,"position_y":200,"network_type":"VXLAN","external":false}}

Explanation

A vNetwork was created.

Possible failure causes

·     Invalid JSON format.

·     The vNetwork name is required.

·     The number of vNetworks has reached the limit specified in the resource pool.

·     Different vNetworks cannot use the same name.

·     The specified tenant default logical network does not exist.

·     VNI allocation failed.

·     Operation failed. The UUID already exists.

·     Failed to add the resource.

·     No available VNIs.

·     The VNI has been used.

·     DriverManager microservice processing failed.

·     Site “site_info” processing failed.

·     Cannot reach site “site_info”.

·     While the system is deleting a tenant or unbinding a tenant from sites, do not perform any operations on the tenant or its resources.

·     This feature is not supported by the current version of the controller.

Message text

Updated network “$1”, request: $2

Variable fields

$1: UUID of the vNetwork.

$2: vNetwork request message body.

Example

Updated network "2eeafe60-adf0-bab9-61d9-63bb481447d3", request: {"network":{"id":"2eeafe60-adf0-bab9-61d9-63bb481447d3","name":"network2223","description":"","position_x":50,"position_y":200}}

Explanation

A vNetwork was modified.

Possible failure causes

·     Invalid JSON format.

·     The UUID is required.

·     The External network parameter of a vNetwork cannot be modified.

·     The network type of a vNetwork cannot be modified.

·     The segment ID of a vNetwork cannot be modified.

·     The UUID of a tenant cannot be modified.

·     Different vNetworks cannot use the same name.

·     The resource does not exist.

·     Failed to modify the resource.

·     DriverManager microservice processing failed.

·     Site “site_info” processing failed.

·     Cannot reach site “site_info”.

·     The specified resource does not exist.

·     While the system is deleting a tenant or unbinding a tenant from sites, do not perform any operations on the tenant or its resources.

·     This feature is not supported by the current version of the controller.

Message text

Deleted network “$1”.

Variable fields

$1: UUID of the vNetwork.

Example

Deleted network “edfed45a-d3a9-4bb0-bfe4-b5fe5c3c9027”.

Explanation

A vNetwork was deleted.

Possible failure causes

·     The resource does not exist.

·     The vNetwork has vSubnets.

·     Internal error.

·     Failed to delete the resource.

·     DriverManager microservice processing failed.

·     Site “site_info” processing failed.

·     Cannot reach site “site_info”.

·     The vNetwork has been bound to a Layer 2 site interconnection.

·     The specified resource does not exist.

·     This feature is not supported by the current version of the controller.

Message text

Added router “$1”, request: $2

Variable fields

$1: UUID of the vRouter.

$2: vRouter request message body.

Example

Added router "31fd6250-8bcb-d2e5-7a01-8169c0a77674", request: {"router":{"id":"31fd6250-8bcb-d2e5-7a01-8169c0a77674","name":"vrouter","tenant_id":"0e2192de-27c6-40b1-8e9f-3136d2dcc208","position_x":310,"position_y":50}}

Explanation

A vRouter was created.

Possible failure causes

·     Invalid JSON format.

·     The vRouter name is required.

·     The specified tenant default logical network does not exist.

·     The number of vRouters has reached the limit specified in the resource pool.

·     Different vRouters cannot use the same name.

·     Different CIDRs cannot overlap.

·     Failed to add the resource.

·     Operation failed. The UUID already exists.

·     No available VNIs.

·     VNI allocation failed.

·     The VNI has been used.

·     DriverManager microservice processing failed.

·     Site “site_info” processing failed.

·     Cannot reach site “site_info”.

·     While the system is deleting a tenant or unbinding a tenant from sites, do not perform any operations on the tenant or its resources.

·     This feature is not supported by the current version of the controller.

Message text

Updated router “$1”, request: $2

Variable fields

$1: UUID of the vRouter.

$2: vRouter request message body.

Example

Updated router "31fd6250-8bcb-d2e5-7a01-8169c0a77674", request: {"router":{"id":"31fd6250-8bcb-d2e5-7a01-8169c0a77674","name":"vrouter","position_x":100,"position_y":50,"cidrs":[]}}

Explanation

A vRouter was modified.

Possible failure causes

·     Invalid JSON format.

·     The UUID is required.

·     The tenant cannot be modified.

·     The CIDR has been used by a vSubnet.

·     Different CIDRs cannot overlap.

·     Different vRouters cannot use the same name.

·     Internal error.

·     Failed to modify the resource.

·     The resource does not exist.

·     DriverManager microservice processing failed.

·     Site “site_info” processing failed.

·     Cannot reach site “site_info”.

·     The specified resource does not exist.

·     While the system is deleting a tenant or unbinding a tenant from sites, do not perform any operations on the tenant or its resources.

·     This feature is not supported by the current version of the controller.

Message text

Deleted router “$1”.

Variable fields

$1: UUID of the vRouter.

Example

Deleted router “edfed45a-d3a9-4bb0-bfe4-b5fe5c3c9027”.

Explanation

A vRouter was deleted.

Possible failure causes

·     The resource does not exist.

·     The vRouter has been bound to vSubnets.

·     Failed to delete the resource.

·     DriverManager microservice processing failed.

·     Site “site_info” processing failed.

·     Cannot reach site “site_info”.

·     Internal error.

·     The specified resource does not exist.

·     This feature is not supported by the current version of the controller.

Keyword

ADD_NSO_LOGICALLINK_OP

Message text

Added a logical link between vRouter $1 and vNetwork $2, request: $3

Variable fields

$1: UUID of the vRouter.

$2: UUID of the vNetwork.

$3: Logical link request message body.

Example

Added a logical link between vRouter 1aa4547a-3e74-8922-b154-0c3f6b7d7a24 and vNetwork 42f5acef-31aa-c310-a1b4-d0c6f1102707, request: {"input":{"router_id":"1aa4547a-3e74-8922-b154-0c3f6b7d7a24","network_id":"42f5acef-31aa-c310-a1b4-d0c6f1102707"}}

Explanation

A logical link was added.

Possible failure causes

·     Invalid JSON format.

·     The vRouter does not exist.

·     The vNetwork does not exist.

·     The vNetwork does not have vSubnets.

·     The vNetwork has been bound to a vRouter.

·     The vSubnet has been bound to a vRouter.

·     The vSubnet is not configured with a gateway IP.

·     The vRouter and vSubnet does not belong to the same tenant.

·     Subnets in the same vNetwork must be bound to the same vRouter.

·     The CIDRs of vSubnets bound to a vRouter cannot overlap.

·     The number of vRouters bound to the site has reached the limit.

·     While the system is deleting a tenant or unbinding a tenant from sites, do not perform any operations on the tenant or its resources.

·     This feature is not supported by the current version of the controller.

Keyword

DEL_NSO_LOGICALLINK_OP

Message text

Deleted a logical link between vRouter $1 and vNetwork $2, request: $3

Variable fields

$1: UUID of the vRouter.

$2: UUID of the vNetwork.

$3: Logical link request message body.

Example

Deleted a logical link between vRouter 1aa4547a-3e74-8922-b154-0c3f6b7d7a24 and vNetwork 42f5acef-31aa-c310-a1b4-d0c6f1102707, request: {"input":{"router_id":"1aa4547a-3e74-8922-b154-0c3f6b7d7a24","network_id":"42f5acef-31aa-c310-a1b4-d0c6f1102707"}}

Explanation

A logical link was deleted.

Possible failure causes

·     Invalid JSON format.

·     The vRouter does not exist.

·     The vNetwork does not exist.

·     The vNetwork is not bound to a vRouter.

·     This feature is not supported by the current version of the controller.

Keyword

BOUND_SUBNET_VROUTER_OP

Message text

Bound subnet $1 to vRouter $2, request: $3

Variable fields

$1: UUID of the vNetwork.

$2: UUID of the vRouter.

$3: Message body of the request for binding the subnet to the vRouter.

Example

Bound subnet f374ec27-5da3-42f6-0c24-e58b05832cde to vRouter 1aa4547a-3e74-8922-b154-0c3f6b7d7a24, request: {"input":{"router_id":"1aa4547a-3e74-8922-b154-0c3f6b7d7a24","subnet_id":"f374ec27-5da3-42f6-0c24-e58b05832cde"}}

Explanation

A subnet was bound to a vRouter.

Possible failure causes

·     Invalid JSON format.

·     The vRouter does not exist.

·     The vSubnet does not exist.

·     The vSubnet has been bound to a vRouter.

·     The vSubnet is not configured with a gateway IP.

·     The vRouter and vSubnet does not belong to the same tenant.

·     Subnets in the same vNetwork must be bound to the same vRouter.

·     The CIDRs of vSubnets bound to a vRouter cannot overlap.

·     The number of vRouters bound to the site has reached the limit.

·     While the system is deleting a tenant or unbinding a tenant from sites, do not perform any operations on the tenant or its resources.

·     This feature is not supported by the current version of the controller.

Keyword

UNBOUND_SUBNET_VROUTER_OP

Message text

Unbound subnet $1 from vRouter $2, request: $3

Variable fields

$1: UUID of the vNetwork.

$2: UUID of the vRouter.

$3: Message body of the request for unbinding the subnet from the vRouter.

Example

Unbound subnet f374ec27-5da3-42f6-0c24-e58b05832cde from vRouter 1aa4547a-3e74-8922-b154-0c3f6b7d7a24, request: {"input":{"router_id":"1aa4547a-3e74-8922-b154-0c3f6b7d7a24","subnet_id":"f374ec27-5da3-42f6-0c24-e58b05832cde"}}

Explanation

A subnet was unbound from a vRouter.

Possible failure causes

·     Invalid JSON format.

·     The vRouter does not exist.

·     The vSubnet does not exist.

·     The vSubnet is not bound to a vRouter.

·     The subnet has been bound to a Layer 3 site interconnection.

·     This feature is not supported by the current version of the controller.

Message text

Added site “$1”, request: $2

Variable fields

$1: UUID of the site.

$2: Site request message body.

Example

Added site "1dd6cb3f-3d55-ff1b-5ab0-0dd920dcb9b1", request:

{"site":{"id":"1dd6cb3f-3d55-ff1b-5ab0-0dd920dcb9b1","name":"site","description":"","url":"192.168.132.81",

"user_name":"admin","pass_word":"*********","position_x":417,"position_y":199,"driver_id":"F124E6AC-0C3E-4413-88B4-6258F2948FEA","custom_property":"[]"}}

Explanation

A site was added.

Possible failure causes

·     Invalid JSON format.

·     The site name is required.

·     The URL is required.

·     The username is required.

·     The password is required.

·     The driver type is required.

·     The license capacity is insufficient.

·     Invalid request.

·     Internal error.

·     Failed to add the resource.

·     Operation failed. The UUID already exists.

·     The site name has been used.

·     The url has been used.

·     Failed to deploy site resources to the DriverManager microservice.

·     Invalid site address.

·     The URL format is http(s)://IPv4 address|[IPv6 address]:port number. The IPv4 address is in dotted decimal notation and cannot be a broadcast, loopback, multicast, or reserved IP address. The IPv6 address is in colon hexadecimal notation and must be a global unicast address. The port number is an integer in the range of 1 to 65535.

Message text

Updated site “$1”, request: $2

Variable fields

$1: UUID of the site.

$2: Site request message body.

Example

Updated site "1dd6cb3f-3d55-ff1b-5ab0-0dd920dcb9b1", request: {"site":{"url":"192.168.132.81","user_name":"admin1","id":"1dd6cb3f-3d55-ff1b-5ab0-0dd920dcb9b1","custom_property":"[]"}}

Explanation

A site was modified.

Possible failure causes

·     Invalid JSON format.

·     The UUID is required.

·     The site name cannot be modified.

·     The custom settings of a site cannot be modified.

·     Invalid request.

·     The site has been bound to tenants.

·     Failed to update site resources on the DriverManager microservice.

·     Internal error.

·     The resource does not exist.

·     The url has been used.

·     The maximum number of vRouters that can be bound to the site is smaller than the number of existing vRouters bound to the site.

·     The maximum number of vNetworks that can be bound to the site is smaller than the number of existing vNetworks bound to the site.

·     The maximum number of vSubnets that can be bound to the site is smaller than the number of existing vSubnets bound to the site.

·     The site has been synchronized. The URL cannot be modified.

·     Failed to modify the resource.

·     Synchronizing settings from sites.

·     The specified resource does not exist.

·     Invalid site address.

·     The URL format is http(s)://IPv4 address|[IPv6 address]:port number. The IPv4 address is in dotted decimal notation and cannot be a broadcast, loopback, multicast, or reserved IP address. The IPv6 address is in colon hexadecimal notation and must be a global unicast address. The port number is an integer in the range of 1 to 65535.

Message text

Deleted site “$1”.

Variable fields

$1: UUID of the site.

Example

Deleted site “edfed45a-d3a9-4bb0-bfe4-b5fe5c3c9027”.

Explanation

A site was deleted.

Possible failure causes

·     Invalid request.

·     The site has been bound to tenants.

·     The resource does not exist.

·     Failed to delete the resource.

·     Synchronizing settings from sites.

·     The site has been used to create a site connection.

·     The specified resource does not exist.

·     Failed to delete site resources from the DriverManager microservice.

Message text

Added subnet “$1”, request: $2

Variable fields

$1: UUID of the vSubnet.

$2: VSubnet request message body.

Example

Added subnet "b87dc586-dcf6-dd52-d3e5-f5dbc521179d", request: {"subnet":

{"id":"b87dc586-dcf6-dd52-d3e5-f5dbc521179d","name":"subnet231","network_id":"b82247b8-7b0c-a729-fa48-e6aa7ecce4d8","cidr":"22.3.3.3/16","ip_version":"ipv4","position_x":344,"position_y":350,

"enable_dhcp":false,"gateway_ip":"22.3.3.3","siteResources":["zjt-transit"]}}

Explanation

A vSubnet was created.

Possible failure causes

·     The vSubnet name is required.

·     The vNetwork UUID is required.

·     The IP version is required.

·     Invalid JSON format.

·     Different vSubnets cannot use the same name.

·     Internal error.

·     The specified vNetwork does not exist.

·     Failed to add the resource.

·     Operation failed. The UUID already exists.

·     The gateway IP address is required when the vNetwork is an external network.

·     The gateway IP address doesn’t belong to the subnet.

·     The CIDR overlaps with another CIDR in the same vNetwork.

·     Invalid DHCP address pool.

·     Only sites specified for the tenant are available.

·     DriverManager microservice processing failed.

·     Site “site_info” processing failed.

·     Cannot reach site “site_info”.

·     The gateway IP address is required when the DHCP is enabled.

·     The gateway IP address conflicts with the subnet broadcast address.

·     An IPv4 subnet cannot be configured with the IPv6 address mode or the IPv6 RA mode.

·     The IPv6 address mode and the IPv6 RA mode must be the same.

·     When the IPv6 address mode is SLAAC or Stateless DHCPv6, the subnet mask must be 64.

·     When the IPv6 address mode is Stateful DHCPv6, Stateless DHCPv6 or SLAAC, DHCP must be enabled.

·     The gateway IP address conflicts with the subnet address.

·     Invalid CIDR.

·     The number of vSubnets has reached the limit specified in the resource pool.

·     While the system is deleting a tenant or unbinding a tenant from sites, do not perform any operations on the tenant or its resources.

·     This feature is not supported by the current version of the controller.

Keyword

UPDATE_NSO_SUBNET_OP

Message text

Updated subnet “$1”, request: $2

Variable fields

$1: UUID of the vSubnet.

$2: VSubnet request message body.

Example

Updated subnet "cc2450f7-4184-a904-7bca-2d99093b4e63", request: {"subnet":{"id":"cc2450f7-4184-a904-7bca-2d99093b4e63","name":"subnet2311","gateway_ip":"203.3.3.6","position_x":100,

"position_y":350,"siteResources":["zjt-transit"]}}

Explanation

A subnet was modified.

Possible failure causes

·     The UUID is required.

·     Cannot change the tenant of a vSubnet.

·     Cannot change the link layer network of a vSubnet.

·     The CIDR can be modified only when the subnet is undeployed.

·     The IP version can be modified only when the subnet is undeployed.

·     The DHCP state can be modified only when the subnet is undeployed.

·     The address pool can be modified only when the subnet is undeployed.

·     The resource does not exist.

·     Internal error.

·     Different vSubnets cannot use the same name.

·     Cannot modify the gateway IP address for the subnet, because the subnet is bound a vRouter.

·     The gateway IP address doesn’t belong to the subnet.

·     The number of sites bound to a vSubnet cannot be reduced when the vSubnet has vPorts.

·     The specified site does not exist.

·     Failed to modify the resource.

·     DriverManager microservice processing failed.

·     Site “site_info” processing failed.

·     Cannot reach site “site_info”.

·     The gateway IP address conflicts with the subnet broadcast address.

·     The IPv6 RA mode can be modified only when the subnet is undeployed.

·     The IPv6 address mode can be modified only when the subnet is undeployed.

·     The gateway IP address conflicts with the subnet address.

·     The vSubnet has vPorts.

·     The subnet has been bound to a Layer 3 site interconnection.

·     The vNetwork to which the subnet belongs has been bound to a Layer 2 site interconnection.

·     You cannot delete the gateway IP address for the subnet, because the subnet has been bound to a vRouter.

·     The specified resource does not exist.

·     While the system is deleting a tenant or unbinding a tenant from sites, do not perform any operations on the tenant or its resources.

·     This feature is not supported by the current version of the controller.

Message text

Deleted subnet “$1”.

Variable fields

$1: UUID of the vSubnet.

Example

Deleted subnet “edfed45a-d3a9-4bb0-bfe4-b5fe5c3c9027”.

Explanation

A vSubnet was deleted.

Possible failure causes

·     Invalid request.

·     The resource does not exist.

·     Internal error.

·     The vSubnet has been bound to a vRouter.

·     The vSubnet has vPorts.

·     Failed to delete the resource.

·     DriverManager microservice processing failed.

·     Site “site_info” processing failed.

·     Cannot reach site “site_info”.

·     The vNetwork to which the subnet belongs has been bound to a Layer 2 site interconnection.

·     The specified resource does not exist.

·     This feature is not supported by the current version of the controller.

Keyword

CONTROLLED_NSO_SITE_OP

Message text

Synchronized settings from sites "$1".

Variable fields

$1: Site name.

Example

Synchronized settings from sites "site1".

Explanation

Synchronized settings from sites.

Possible failure causes

·     Invalid JSON format.

·     Internal error.

·     Site 'site_name' does not exist.

·     Settings of site 'site_name' has been synchronized.

·     Synchronization failed. Tenant name conflict occurs on site 'site_name'.

·     Synchronization failed. vRouter 'vRouter_name' of site 'site_name' is not configured with a segment ID.

·     The VNI has been used.

·     VNI allocation failed.

·     DriverManager microservice processing failed.

·     Cannot reach site “site_info”.

·     Site “site_info” processing failed.

·     The vNetwork to which the subnet belongs has been bound to a Layer 2 site interconnection.

·     The specified resource does not exist.

·     Synchronizing settings from sites.

·     Synchronization failed. The parameters of the subnet “subnet_info” on the site “site_info” is invalid.

·     Synchronization failed. The name of the subnet on the site “site_info” cannot exceed 255 characters.

·     Synchronization failed. The parameters of the vNetwork “network_info” on the site “site_info” is invalid.

·     Synchronization failed. The name of the vNetwork on the site “site_info” cannot exceed 255 characters.

·     Synchronization failed. The parameters of the vRouter “router_info” on the site “site_info” is invalid.

·     Synchronization failed. The name of the vRouter on the site “site_info” cannot exceed 255 characters.

·     Failed to process the request. Please check whether the plugin matches the version of Super Controller.

Message text

Added tenant “$1”, request: $2

Variable fields

$1: UUID of the tenant.

$2: Tenant request message body.

Example

Added tenant "e1bace90-5972-db07-b4d6-56471fba2148", request: {"tenant":{"id":"e1bace90-5972-db07-b4d6-56471fba2148","name":"tenant-zjt4","description":"","siteResources":["zjt-transit"],"tenant_type":"local-create"}

Explanation

A tenant was created.

Possible failure causes

·     Invalid JSON format.

·     The tenant name is required.

·     Invalid request.

·     The specified site does not exist.

·     Failed to add the resource.

·     Invalid tenant type.

·     Operation failed. The UUID already exists.

·     The tenant name has been used.

·     Before creating tenants, you must create sites.

·     The number of tenant has reached the limit specified in the resource pool.

·     DriverManager microservice processing failed.

·     Cannot reach site “site_info”.

·     Site “site_info” processing failed.

·     You cannot create a tenant named default.

·     Failed to process the request. Please check whether the plugin matches the version of Super Controller.

·     This feature is not supported by the current version of the controller.

Message text

Updated tenant “$1”, request: $2

Variable fields

$1: UUID of the tenant.

$2: Tenant request message body.

Example

Updated tenant "e1bace90-5972-db07-b4d6-56471fba2148", request: {"tenant":{"id":"e1bace90-5972-db07-b4d6-56471fba2148","name":"tenant-zjt4","description":"2222","siteResources":["zjt-transit"]}}

Explanation

A tenant was modified.

Possible failure causes

·     Invalid JSON format.

·     The UUID is required.

·     The tenant type cannot be modified.

·     The username of the tenant administrator cannot be modified.

·     The password of the tenant administrator cannot be modified.

·     Invalid request.

·     The specified site does not exist.

·     The resource does not exist.

·     The tenant name has been used.

·     Failed to modify the resource.

·     DriverManager microservice processing failed.

·     Cannot reach site “site_info”.

·     Site “site_info” processing failed.

·     You cannot delete this site, because it has device groups incorporated on the transit fabric and tenants bound to transit vRouters.

·     The specified resource does not exist.

·     You cannot remove the tenant from the specified site, because the tenant is used by a tenant router access service.

·     While the system is deleting a tenant or unbinding a tenant from sites, do not perform any operations on the tenant or its resources.

·     You cannot edit the name of the default tenant.

·     Failed to process the request. Please check whether the plugin matches the version of Super Controller.

·     This feature is not supported by the current version of the controller.

·     You cannot update a tenant named default.

Message text

Deleted tenant “$1”, request: $2

Variable fields

$1: UUID of the tenant.

$2: Tenant request message body.

Example

Deleted tenant "acd1062f-2685-bc0f-2517-cac834373b24", request: {"id":"acd1062f-2685-bc0f-2517-cac834373b24","suc_only":true}

Explanation

A tenant was deleted.

Possible failure causes

·     The tenant has vPorts.

·     Invalid request.

·     The resource does not exist.

·     Failed to delete the resource.

·     DriverManager microservice processing failed.

·     Cannot reach site “site_info”.

·     Site “site_info” processing failed.

·     The tenant has transit routers.

·     The specified resource does not exist.

·     You cannot delete the tenant, because the tenant is used by a tenant router access service.

·     While the system is deleting a tenant or unbinding a tenant from sites, do not perform any operations on the tenant or its resources.

·     Failed to process the request. Please check whether the plugin matches the version of Super Controller.

·     This feature is not supported by the current version of the controller.

Message text

Added VNI “$1”, request: $2

Variable fields

$1: UUID of the global resource pool.

$2: Global resource pool request message body.

Example

Added VNI "8ce6420d-a74e-51df-ce8d-78607a3df794", request: {"vni":{"id":"8ce6420d-a74e-51df-ce8d-78607a3df794","name":"vni2","description":"","vni_type":"VXLAN","range"

:[{"start_seg_id":"2000","end_seg_id":"3000"}]}}

Explanation

A global resource pool was created.

Possible failure causes

·     Invalid JSON format.

·     Invalid request.

·     The VNI name is required.

·     The VNI range is required.

·     Invalid VNI range.

·     Internal error.

·     Failed to add the resource.

·     Operation failed. The UUID already exists.

·     The VNI name has been used.

Message text

Updated VNI “$1”, request: $2

Variable fields

$1: UUID of the global resource pool.

$2: Global resource pool request message body.

Example

Updated VNI "8ce6420d-a74e-51df-ce8d-78607a3df794", request: {"vni":{"id":"8ce6420d-a74e-51df-ce8d-78607a3df794","range":[{"start_seg_id":2000,"end_seg_id":"3001"}]}}

Explanation

A global resource pool was modified.

Possible failure causes

·     The UUID is required.

·     The VNI name cannot be modified.

·     The VNI type cannot be modified.

·     Invalid JSON format.

·     Invalid request.

·     The resource does not exist.

·     Internal error.

·     Invalid VNI range.

·     The VNI has been used and cannot be modified.

·     Different VNI ranges cannot overlap.

·     Failed to modify the resource.

·     The specified resource does not exist.

Message text

Deleted VNI “$1”.

Variable fields

$1: UUID of the global resource pool.

Example

Deleted VNI “edfed45a-d3a9-4bb0-bfe4-b5fe5c3c9027”.

Explanation

A global resource pool was deleted.

Possible failure causes

·     Invalid request.

·     The resource does not exist.

·     Internal error.

·     Failed to delete the resource.

·     The specified resource does not exist.

Keyword

UPDATE_NSO_CONFIG_OP

Message text

Updated resource pool limit settings, request: $1.

Variable fields

$1: Maximum numbers for different types of resource pools.

Example

Updated resource pool limit settings, request: {"webresourcelimitsetting":{"limit_setting": [{"setting-type":"ROUTER","setting-value":1000}, {"setting-type":"PORT","setting-value":500},{"setting-type":"SUBNET","setting-value":500}, {"setting-type":"TENANT","setting-value":500}, {"setting-type":"NETWORK","setting-value":500}]}}.

Explanation

The maximum numbers for different types of resource pools were modified.

Possible failure causes

·     Invalid JSON format.

·     Invalid request.

·     Internal error.

·     The value must be an integer greater than or equal to -1.

Message text

Added transit fabric, request: $1

Variable fields

$1: Request message body for a transit fabric.

Example

Added transit fabric, request: {

         "transit_fabric":{

                   "name":"2",

                   "description":"2",

                   "device_groups":[

                   ]

         }

}

Explanation

A transit fabric was added.

Possible failure causes

·     Internal error.

·     Invalid JSON format.

·     Invalid UUID.

·     Please specify a transit fabric name.

·     A transit fabric already exists with the specified name.

·     Please specify a site ID for the device group.

·     Failed to find a device group with the specified device group ID in the transit fabric.

·     The specified site ID does not match that of the device group with the specified device group ID in the transit fabric.

·     The site bound to the device group does not exist.

·     The specified device group does not exist.

·     The description cannot exceed 255 characters.

·     Please specify a device group ID.

·     Please specify a site ID for the device group.

·     Failed to add the resource.

·     You can create up to one transit fabric.

·     Make sure at least one of the selected device groups is used for DC interconnect.

·     A transit fabric name must be a string of up to 64 characters without spaces.

·     This feature is not supported by the current version of the controller.

Message text

Updated transit fabric “$1”, request: $2

Variable fields

$1: Transit fabric ID.

$2: Request message body for a transit fabric.

Example

Updated transit fabric "c6bfd1a0-67ff-4699-b300-b9732f408772", request: {

         "transit_fabric":{

                   "description":"1",

                   "device_groups":[

                            {

                                 "id":"c6bfd1a0-67ff-4699-b300-b9732f408772",

                                 "site_id":"98390f34-8169-0d14-0d7d-b5245a42e225"

                            }

                   ]

         }

}

Explanation

A transit fabric was edited.

Possible failure causes

·     Internal error.

·     Invalid JSON format.

·     The specified resource does not exist.

·     The specified device group does not exist.

·     The specified transit fabric does not exist.

·     The description cannot exceed 255 characters.

·     Please specify a device group ID.

·     Please specify a site ID for the device group.

·     Failed to modify the resource.

·     You cannot edit the transit fabric name.

·     Make sure at least one of the selected device groups is used for DC interconnect.

·     You cannot edit the name of the transit fabric or its device group settings, because it has completed service orchestration.

·     The site of the device group has been bound to a tenant router access.

·     This feature is not supported by the current version of the controller.

Message text

Deleted transit fabric $1

Variable fields

$1: Transit fabric ID.

Example

Deleted transit fabric edfed45a-d3a9-4bb0-bfe4-b5fe5c3c9027

Explanation

A transit fabric was deleted.

Possible failure causes

·     Internal error.

·     The specified resource does not exist.

·     Failed to delete the resource.

·     You cannot delete the transit fabric, because it has completed service orchestration.

·     You cannot delete this device group, because the site of the device group has been bound to a border gateway access service.

·     This feature is not supported by the current version of the controller.

Message text

Added transit router, request: $1

Variable fields

$1: Request message body for a transit router.

Example

Added transit router, request: {

         "transit_router":{

                   "name":"TR-1",

                   "description":"654",

                   "tenant_id":"d960e576-cb33-453e-96ba-77aceb5be7fd",

                   "vrf_mode":"MANUAL",

                   "vrf_name":"654",

                   "vni_mode":"MANUAL",

                   "l3_vni":"100002",

                   "transit_site_id":"23340cb1-8a95-4bd3-b081-67b480d71824"

         }

}

Explanation

A transit router was added.

Possible failure causes

·     Internal error.

·     Invalid JSON format.

·     Invalid UUID.

·     VNI allocation failed.

·     The VNI has been used.

·     VNI allocation failure: No VNIs available.

·     The description cannot exceed 255 characters.

·     The specified transit fabric does not exist.

·     A transit router name must be a case-sensitive string of up to 255 characters and cannot be all spaces.

·     A transit router already exists with the specified name.

·     A VRF name must be a case-sensitive string of up to 31 characters. Valid characters are letters and digits.

·     The specified tenant does not exist.

·     Please specify a VRF mode.

·     You do not need to specify a VRF name when the value for the vrf_mode field is auto.

·     You must specify a VRF name when the value for the vrf_mode field is manual.

·     The value for the vrf_mode field can only be auto or manual.

·     A VRF already exists with the specified name.

·     The operation type is invalid.

·     Failed to add the resource.

·     Please specify the vni_mode field.

·     The value for the vni_mode field can only be auto or manual.

·     You do not need to specify an L3VNI when the value for the vni_mode field is auto.

·     You must specify an L3VNI when the value for the vni_mode field is manual.

·     Please specify this parameter.

·     The specified tenant must exist on all sites of the specified transit fabric.

·     The specified transit fabric does not have device groups.

·     The automatically generated VRF name and the existing VRF name cannot be the same. Please specify the VRF name manually.

·     The specified transit fabric does not exist.

·     The value range of L3VNI is an integer from 1 to 16777215.

·     Invalid transit router type.

·     Please specify external CIDRs.

·     Invalid external CIDRs.

·     The destination subnets overlap.

·     This feature is not supported by the current version of the controller.

Message text

Updated transit router, request: $1

Variable fields

$1: Request message body for a transit router.

Example

Updated transit router, request: {

         "transit_router":{

                   "operation":null

         }

}

Explanation

A transit router was edited.

Possible failure causes

·     Internal error.

·     Invalid JSON format.

·     The specified resource does not exist

·     The operation type is invalid.

·     Please specify the operation field.

·     Failed to modify the resource.

·     You cannot edit the %s parameter.

·     To predelete the transit router, make sure all tenant router accesses bound to the transit router have been predeleted.

·     You cannot delete the destination subnet of the transit router, because it has been specified for a route entry.

·     To predelete the transit router, make sure no border gateway access services are bound to the transit router or all gateway access services bound to the transit router have been predeleted.

·     This feature is not supported by the current version of the controller.

Message text

Deleted transit router “$1”.

Variable fields

$1: Transit router ID.

Example

Deleted transit router “edfed45a-d3a9-4bb0-bfe4-b5fe5c3c9027”.

Explanation

A transit router was deleted.

Possible failure causes

·     Internal error.

·     The specified resource does not exist.

·     Failed to delete the resource.

·     You cannot directly delete resources specified in a configuration deployment.

·     You cannot delete the specified transit router, because it is bound to a tenant router access.

·     You cannot delete the transit router, because it has been bound to border gateway access services.

·     This feature is not supported by the current version of the controller.

Message text

Added VPC connection, request: $1

Variable fields

$1: Request message body for a VPC connection.

Example

Added VPC connection, request: {

         "vpc_connection":{

                   "transit_router_id":"41dfff94-8a96-43eb-af0e-7b325a8505d1",

                   "site_id":"98390f34-8169-0d14-0d7d-b5245a42e225",

                   "tenant_id":"d960e576-cb33-453e-96ba-77aceb5be7fd",

                   "router_id":"5e761ce1-c87d-4efc-b1fa-f2f480fc5289",

                   "fw_enable":false,

                   "is_local_all":true,

                   "is_peer_all":true,

                   "local_subnets":[

                   ],

                   "local_cidrs":[

                   ],

                   "peer_cidrs":[

                   ],

                   "transit_site_id":"23340cb1-8a95-4bd3-b081-67b480d71824"

         }

}

Explanation

A VPC connection was added.

Possible failure causes

·     Internal error.

·     Invalid JSON format.

·     Invalid UUID.

·     The specified transit fabric does not exist.

·     No transit routers exist in the transit fabric.

·     The specified resource does not exist in the specified fabric.

·     Please specify a peer CIDR.

·     The site in the tenant router access is not in the specified transit fabric.

·     The specified site does not exist.

·     The tenant list is empty in the specified site in the tenant router access.

·     The specified site does not have the tenant bound to the tenant router access.

·     The vRouter bound to the tenant router access does not belong to the specified tenant.

·     The specified subnet is not attached to the vRouter bound to the tenant router access.

·     The specified vSubnet of tenant router access does not exist.

·     The specified device group does not exist.

·     The operation type is invalid.

·     The specified tenant does not exist.

·     Please specify the is_local_all field.

·     Please specify the is_peer_all field.

·     Please specify either the local_subnets field or local_cidrs field, or both.

·     You must specify both local CIDRs and remote CIDRs, because the firewall feature is disabled for the tenant router access.

·     You cannot bind the transit vRouter to the tenant router access, because the transit vRouter has been bound to another tenant router access using the same tenant router.

·     The transit fabric has not incorporated the device groups used in the gateway for the specified tenant router.

·     The vRouter to be bound to the tenant router access does not exist.

·     The transit router to be bound to the tenant router access does not exist.

·     A tenant router access already exists between the specified vRouter and transit router.

·     The VRF name of the tenant router access cannot be the same as that of the transit routers in the same transit fabric.

·     For tenant router accesses attached to the same transit router in the site, enable all of them to pass through the firewall or disable the setting for them.

·     Failed to add the resource.

·     Please specify this parameter.

·     Invalid local CIDR.

·     Invalid remote CIDRs.

·     The specified tenant of tenant router access does not exist.

·     The transit fabric has not incorporated the device groups used in the gateway for the specified vRouter.

·     Different local CIDR cannot overlap.

·     The remote CIDRs cannot overlap.

·     The specified transit fabric does not have device groups.

·     A tenant router access already exists with the specified name.

·     A tenant router access name must be a case-sensitive string of up to 255 characters and cannot be all spaces.

·     The tenant of the transit router does not exist on the site of the tenant router access.

·     Please specify a transit router ID.

·     This feature is not supported by the current version of the controller.

Message text

Updated VPC connection, request: $1

Variable fields

$1: Request message body for a VPC connection.

Example

Updated VPC connection, request: {

         "vpc_connection":{

                   "operation":"UPDATE"

         }

}

Explanation

A VPC connection was edited.

Possible failure causes

·     Internal error.

·     Invalid JSON format.

·     The specified resource does not exist.

·     The operation type is invalid.

·     Invalid UUID.

·     The specified resource does not exist in the specified site.

·     Please specify the operation field.

·     You cannot change the transit router bound to the tenant router access.

·     Failed to modify the resource.

·     You cannot edit the %s parameter.

·     Invalid local CIDR.

·     Invalid remote CIDRs.

·     Different local CIDR cannot overlap.

·     The remote CIDRs cannot overlap.

·     To predelete the transit router, make sure all tenant router accesses bound to the transit router have been predeleted.

·     The tenant of the transit router does not exist on the site of the tenant router access.

·     Please specify a transit router ID.

·     Please predelete all tenant router access services bound to the transit router first.

·     If remote firewall is enabled, the transit router type must be border gateway group.

·     If local firewall is enabled and the transit router type is border gateway group, you cannot specify remote CIDRs.

·     If local firewall is enabled and the transit router type is east-west, you must specify remote CIDRs.

·     This feature is not supported by the current version of the controller.

Message text

Deleted VPC connection “$1”

Variable fields

$1: VPC connection ID.

Example

Deleted VPC connection "60ede326-144e-4949-a186-65891ae70bf0"

Explanation

A VPC connection was deleted.

Possible failure causes

·     Internal error.

·     The specified resource does not exist.

·     Failed to delete the resource.

·     You cannot directly delete resources specified in a configuration deployment.

·     This feature is not supported by the current version of the controller.

Message text

Deployed transit fabric “$1”

Variable fields

$1: Transit fabric ID.

Example

Deployed transit fabric "60ede326-144e-4949-a186-65891ae70bf0"

Explanation

A transit fabric was deployed.

Possible failure causes

·     Internal error.

·     The specified resource does not exist.

·     No transit routers exist in the transit fabric.

·     The transit fabric does not have resources to be deployed.

·     This feature is not supported by the current version of the controller.

Message text

Added an EBGP connection, request: $1

Variable fields

$1: Request message body for an EBGP connection.

Example

Added an EBGP connection, request: {

    "ebgp_connection": {

        "transit_fabric_id": "9029f283-39ed-4b4e-9db0-4f2b42c74dd9",

        "local_device_info": {

            "site_id": "d633b903-bf47-80e3-f83e-b23656175437",

            "group_id": "a28ad0cf-adf5-465d-bb10-ea1dc58094ee",

            "device_id": "1872f0ab-8229-4434-804d-ce34790f6f2f",

            "dci_vtep_ip": "2.3.4.12",

            "as_number": "4294967295"

        },

        "peer_device_info": {

            "site_id": "19290154-3cd0-f8d2-f9a7-59831a48e984",

            "group_id": "973c512b-d802-4b6f-91dc-ece8a8d633a9",

            "device_id": "f873a1af-8bf0-49fd-a7fa-efa9358cb83a",

            "dci_vtep_ip": "55.3.2.5",

            "as_number": "22"

        }

    }

}

Explanation

An EBGP connection was added.

Possible failure causes

·     Internal error.

·     Invalid JSON format.

·     Invalid UUID.

·     The specified resource does not exist.

·     The specified transit fabric does not exist.

·     The page_size value must be an integer in the range of 1 to 100.

·     The page value must be an integer in the range of 1 to 21474836.

·     Please specify complete local device information.

·     Please specify complete remote device information.

·     The local site is not incorporated.

·     The remote site is not incorporated.

·     The local device group is not in the specified transit fabric.

·     The remote device group is not in the specified transit fabric.

·     The specified device group is not in the transit fabric.

·     The device groups in the local site are not on the transit fabric.

·     The device groups in the remote site are not on the transit fabric.

·     The local site is not on the transit fabric.

·     The remote site is not on the transit fabric.

·     No border devices found in the local site.

·     No border devices found in the remote site.

·     The local device group is not in the specified site.

·     The remote device group is not in the specified site.

·     The local device is not in the device group.

·     The remote device is not in the device group.

·     The local device is not in the site or is not a border device.

·     The remote device is not in the site or is not a border device.

·     The specified VTEP IP is different from that of the local device.

·     The specified VTEP IP is different from that of the remote device.

·     The VTEP IP of the local device does not exist.

·     The VTEP IP of the remote device does not exist.

·     The specified AS number is different from that of the local device.

·     The specified AS number is different from that of the remote device.

·     Please specify a transit fabric ID.

·     The AS number of the local device does not exist.

·     The AS number of the remote device does not exist.

·     The local site and the remote site must be different.

·     The specified BGP neighbor already exists.

·     Invalid AS number.

·     You cannot delete the transit fabric, because it has BGP neighbors configured.

·     You cannot delete the device group from the transit fabric, because the border devices in the device group have BGP neighbors.

·     No DCI VTEP IP is configured for the local device.

·     No DCI VTEP IP is configured for the remote device.

·     This feature is not supported by the current version of the controller.

Message text

Deleted EBGP connection $1

Variable fields

$1: EBGP connection ID.

Example

Deleted EBGP connection "827e594e-3234-4dee-8195-e6a8f23ccfb3"

Explanation

An EBGP connection was deleted.

Possible failure causes

·     Internal error.

·     The specified resource does not exist.

·     Failed to delete the resource.

·     This feature is not supported by the current version of the controller.

Message text

Added a border gateway access service, request: $1

Variable fields

$1: Request message body for a border gateway access service.

Example

Added a border gateway access service, request: {

         "gateway_access": {

                   "name": "GW-0",

                   "description": "",

                   "transit_router_id": "d28c4a13-2a30-407a-9931-9646f28f0148",

                   "site_id": "fcedab4b-3527-4462-bf98-4840cf77fef9",

                   "gateway_id": "5898d22f-9358-41fe-9a63-177a0d3fd043",

                   "role": "Master",

                   "firewall_enable": false,

                   "subnets": [{

                            "id": "9d90c3df-c7d6-4a3c-b7b1-f8d27c6c4f68"

                   }, {

                            "id": "567ff798-e7b5-4600-80c2-1b40c71ec21a"

                   }],

                   "transit_fabric_id": "7085f455-4e04-4c0b-9c20-7fb624849d60"

         }

}

Explanation

A border gateway access service was added.

Possible failure causes

·     Internal error.

·     Invalid JSON format.

·     Invalid UUID.

·     The specified border gateway does not exist on the specified transit router for the site.

·     Invalid border gateway access role.

·     The tenant of the transit router does not exist on the site specified for the border gateway access service.

·     The external network does not exist on the specified site.

·     The subnet does not exist in the specified site.

·     The subnet does not exist in the specified external network.

·     The transit router to be bound to the border gateway access service does not exist.

·     A border gateway access service already exists with the specified name.

·     A border gateway access service name must be a case-sensitive string of up to 255 characters and cannot contain only spaces.

·     The external network type must be exclusive when the firewall is disabled.

·     The tenant of the specified transit router does not exist.

·     The transit router bound to the border gateway access service must be the border gateway group type.

·     You cannot configure the border gateway access service role as secondary, because no primary border gateway access service has been configured for the transit router.

·     The transit router already has a primary border gateway access service.

·     The transit router already has a primary border gateway access service and a secondary one.

·     Only transit routers of the border gateway group type support border gateway access services.

·     Please specify a firewall, because the firewall feature is enabled.

·     Please specify a firewall service, because the firewall feature is enabled.

·     Please specify an external network, because the firewall feature is enabled.

·     The border gateway access services bound to the same transit router cannot belong to the same site.

·     The specified firewall does not exist at the site.

·     The specified firewall service does not exist at the site.

·     The mode setting for the firewall must be CGSR.

·     When the firewall feature is enabled, the operating mode for the external network can only be indirectly connected.

·     The firewall must be enabled or disabled on both the primary and secondary border gateway access services.

·     Make sure the primary and secondary border gateway access services are bound to the same subnet and use the same gateway IP address.

·     Please specify the type as VFW and the family as CGSR for the firewall service.

·     Please specify an external network subnet.

·     The specified site does not exist.

·     You cannot create the border gateway access service, because the transit router has predelete border gateway access service.

·     This feature is not supported by the current version of the controller.

Message text

Updated border gateway access service, request: $1

Variable fields

$1: Request message body for a border gateway access service.

Example

Updated border gateway access service, request: {

         "gateway_access": {

                  "description": "extgw1"

         }

}

Explanation

A border gateway access service was edited.

Possible failure causes

·     Internal error.

·     Invalid JSON format.

·     The specified border gateway access service does not exist.

·     Invalid border gateway access role.

·     The operation type is invalid.

·     You cannot restore the secondary border gateway access service when the primary border gateway access service is waiting to be deleted.

·     You cannot update the primary border gateway access service, because the secondary border gateway access service has been predeleted.

·     Please bind border gateway access services that are not predeleted to the transit router first.

Message text

Deleted border gateway access service “$1”

Variable fields

$1: ID of a border gateway access service.

Example

Deleted border gateway access service “edfed45a-d3a9-4bb0-bfe4-b5fe5c3c9027”

Explanation

A border gateway access service was deleted.

Possible failure causes

·     Internal error.

·     The specified border gateway access service does not exist.

·     You cannot delete the primary border gateway access service when the secondary border gateway access service exists.

·     Failed to delete the border gateway access service, because the transit router have tenant router accesses.

·     This feature is not supported by the current version of the controller.

Message text

Added a route entry, request: $1

Variable fields

$1: Request message body for a route entry.

Example

Added a route entry, request: {

         "route": {

                  "gateway_access_id": "8f6cd217-0313-434d-846e-4b8cb137c15f",

                  "destination_cidr": "10.1.1.0/24",

                  "next_hop_type": "IPv4",

                  "next_hop_ip": "20.1.1.1"

         }

}

Explanation

A route entry was added.

Possible failure causes

·     Internal error.

·     Invalid JSON format.

·     Invalid UUID.

·     Invalid next hop type for the route entry.

·     Invalid next hop type for the IPv4 route entry.

·     Invalid next hop type for the IPv6 route entry.

·     Please specify an ID for the border gateway access service.

·     Please specify CIDRs.

·     Please specify the destination subnet for the transit router bound to the border gateway access service.

·     Invalid CIDRs.

·     Please specify the next hop type for the route entry.

·     Please specify the next hop for the route entry.

·     The route entry already exists.

·     The specified manual NQA profile does not exist.

Message text

Updated route entry “$1”, request: $2

Variable fields

$1: Route entry ID.

$2: Request message body for the route entry.

Example

Updated route entry "c6bfd1a0-67ff-4699-b300-b9732f408772", request: {

         " route": {

                 "operation": "UPDATE"

         }

}

Explanation

A route entry was edited.

Possible failure causes

·     Internal error.

·     Invalid JSON format.

·     The specified resource does not exist.

·     The specified border gateway access service does not exist.

·     The operation type is invalid.

·     The specified manual NQA profile does not exist.

Message text

Deleted route entry $1

Variable fields

$1: Route entry ID.

Example

Deleted route entry edfed45a-d3a9-4bb0-bfe4-b5fe5c3c9027

Explanation

A route entry was deleted.

Possible failure causes

·     Internal error.

·     The specified resource does not exist.

Message text

Added a vPort, request: $1

Variable fields

$1: Request message body for a vPort.

Example

Added a vPort, request: {

    "port": {

        "gateway_access_id": "8f6cd217-0313-434d-846e-4b8cb137c15f",

        "external_network_id": "edd60212-54b7-4382-865a-16036a35da64",

        "fixed_ips": [{

            "ip_address": "16.16.16.160"

        }],

        "operation": "CREATE",

        "binding:profile": {

            "enable_snat": true,

            "external_snat_ips": [

                "16.16.16.100"

            ]

        }

    } }

Explanation

A vPort was added.

Possible failure causes

·     Internal error.

·     Invalid JSON format.

·     Invalid UUID.

·     Please specify an IP address for the vPort.

·     You can specify a maximum of two IP addresses for the vPort.

·     Invalid vPort IP address.

·     The extended SNAT IP address cannot be the same as a vPort IP address.

·     The subnet for the extended SNAT IP address was not found.

·     The extended SNAT IP address of the extended external vPort must be in the same subnet as a vPort IP address.

·     Invalid extended SNAT IP address.

·     The subnet of the vPort IP address does not exist.

·     Please specify the border gateway access ID.

·     You can configure vPort settings only when the firewall feature is enabled for the border gateway access service.

·     You cannot configure extended SNAT IP addresses for a vPort, because the vPort does not have an IPv4 address.

·     The vPort IP address cannot be the same as the gateway IP address.

·     The extended SNAT IP address cannot be the same as the gateway IP address.

·     Make sure the vPort IP addresses belong to different subnets.

·     This feature is not supported by the current version of the controller.

Message text

Updated port “$1”, request: $2

Variable fields

$1: vPort ID.

$2: Request message body for the vPort.

Example

Updated port "c3f8e282-342e-4ab8-b7bb-8bbdca9adc73", request: {

    "port": {

        "id": "c3f8e282-342e-4ab8-b7bb-8bbdca9adc73",

        "gateway_access_id": "b2fcd6e5-a1f5-4c19-aa6b-f454f86a08cf",

        "external_network_id": "e3092c89-bf16-4627-b197-690f63fb1f5d",

        "external_network_name": "zjt0628",

        "operation": "UPDATE",

        "fixed_ips": [{

            "ip_address": "12::22"

        }, {

            "ip_address": "12.0.0.16"

        }],

        "binding:profile": {

            "enable_snat": false,

            "fw_enabled": true,

            "external_snat_ips": ["13.0.0.33"]

        },

        "dataStatus": "modified",

        "modify": true

    }

}

Explanation

A vPort was edited.

Possible failure causes

·     Internal error.

·     Invalid JSON format.

·     The specified resource does not exist.

·     The operation type is invalid.

·     You cannot configure extended SNAT IP addresses for a vPort, because the vPort does not have an IPv4 address.

·     The external network does not exist on the specified site.

·     The extended SNAT IP address cannot be the same as the gateway IP address.

·     The subnet for the extended SNAT IP address was not found.

·     Please specify an external network subnet.

·     This feature is not supported by the current version of the controller.

Message text

Deleted vPort $1

Variable fields

$1: vPort ID.

Example

Deleted vPort edfed45a-d3a9-4bb0-bfe4-b5fe5c3c9027

Explanation

A vPort was deleted.

Possible failure causes

·     Internal error.

·     The specified resource does not exist.

·     The operation type is invalid.

Message text

Added a floating IP, request: $1

Variable fields

$1: Request message body for a floating IP.

Example

Added a floating IP, request: {

    "floatingip": {

        "external_network_id": "edd60212-54b7-4382-865a-16036a35da64",

        "subnet_id": "edd60212-54b7-4382-865a-16036a35da64",      

        "floating_ip_address": "22.22.22.18",

        "port_number": null,

        "fixed_ip_address": "22.22.22.16",

        "local_port_number": null,

        "exclude_ports": [{

            "protocol": "TCP",

            "dest_portrange_min": "0",

            "dest_portrange_max": "65535"

        }],

        "dataStatus": "added",

        "gateway_access_id": "f17f8479-de6e-4604-af2e-3d0dfc87966e"

    }

}

Explanation

A floating IP was added.

Possible failure causes

·     Internal error.

·     Invalid JSON format.

·     Invalid UUID.

·     The operation type is invalid.

·     Please specify an ID for the border gateway access service.

·     The specified border gateway access service does not exist.

·     The floating IP address is not in the specified subnet segment.

·     You can create a floating IP only when the edge device to external network for the transit router is firewall.

·     Invalid network protocol type.

·     Invalid internal IP address.

·     The internal IP address conflicts with another floating IP address.

·     The port number must be an integer in the range of 1 to 65535.

·     Invalid internal port number.

·     After you specify an internal port number, the network protocol type must be TCP or UDP.

·     Invalid floating IP address.

·     You cannot specify both protocol type and excluded ports for a floating IP address.

·     The excluded transport protocol type is invalid.

·     Both the maximum port number and the minimum port number in an excluded port range must be an integer in the range of 0 to 65535.

·     The minimum port number cannot be greater than the maximum port number in an excluded port range.

·     The excluded port ranges added for a floating IP cannot be exactly the same.

·     You must enter a floating IP address.

·     The floating IP address conflicts with another floating IP address.

·     The external network does not exist on the specified site.

·     Please specify an external network subnet.

·     The subnet to which the floating IP address belongs does not exist.

·     The floating IP address conflicts with the gateway IP address of the corresponding subnet.

·     The specified site does not exist.

·     Make sure the two border gateway access services are bound to the same subnet and use the same gateway IP address.

·     If you specify a port number for a floating IP, the network protocol type must be TCP or UDP.

·     The specified QoS policy does not exist in the site.

·     This feature is not supported by the current version of the controller.

Message text

Updated floating IP $1, request: $2

Variable fields

$1: Floating IP ID.

$2: Request message body for the floating IP.

Example

Updated floating IP "71aa63cd-4e96-4a56-a91c-06e8e370e04c", request: {

    "floatingip": {

        "id": "71aa63cd-4e96-4a56-a91c-06e8e370e04c",

        "gateway_access_id": "f17f8479-de6e-4604-af2e-3d0dfc87966e",

        "external_network_id": "edd60212-54b7-4382-865a-16036a35da64",

        "subnet_id": "edd60212-54b7-4382-865a-16036a35da64",      

        "qos_id": "b0710ea7-0b80-45d7-8128-1246ccbe9ffa",

        "qos_name": "2qos",

        "floating_ip_address": "22.22.22.18",

        "protocol": null,

        "port_number": null,

        "fixed_ip_address": "22.22.22.16",

        "local_port_number": null,

        "exclude_ports": [{

            "protocol": "TCP",

            "dest_portrange_min": "2231",

            "dest_portrange_max": "65535"

        }],

        "operation": "CREATE",

        "dataStatus": "modified"

    }

}

Explanation

A floating IP was edited.

Possible failure causes

·     Internal error.

·     Invalid JSON format.

·     The specified resource does not exist.

·     The operation type is invalid.

·     The specified border gateway access service does not exist.

·     You cannot specify both protocol type and excluded ports for a floating IP address.

·     The excluded transport protocol type is invalid.

·     Both the maximum port number and the minimum port number in an excluded port range must be an integer in the range of 0 to 65535.

·     The minimum port number cannot be greater than the maximum port number in an excluded port range.

·     The excluded port ranges added for a floating IP cannot be exactly the same.

·     The specified QoS policy does not exist in the site.

·     This feature is not supported by the current version of the controller.

Message text

Deleted floating IP $1

Variable fields

$1: Floating IP ID.

Example

Deleted floating IP edfed45a-d3a9-4bb0-bfe4-b5fe5c3c9027

Explanation

A floating IP was deleted.

Possible failure causes

·     Internal error.

·     The specified resource does not exist.

·     The operation type is invalid.

·     You cannot directly delete resources specified in a configuration deployment.

·     The specified border gateway access service does not exist.

Message text

Added transit network, request: $1

Variable fields

$1: Request message body for a transit network.

Example

Added transit network, request: {

    "transit_network": {

        "name": "TN-0",

        "description": "765",

        "transit_fabric_id": "8f4d7c4a-09f6-4032-9e66-7f13fe4d4cc4",

        "vni_mode": "MANUAL",

        "vni": 100,

        "import_rts": [

            "0:100"

        ],

        "export_rts": [

            "0:100"

        ]

    }

}

Explanation

A transit network was added.

Possible failure causes

·     Internal error.

·     Invalid JSON format.

·     Invalid UUID.

·     VNI allocation failed.

·     The VNI has been used.

·     VNI allocation failure: No VNIs available.

·     The description cannot exceed 255 characters.

·     The specified transit fabric does not exist.

·     A transit network name must be a case-sensitive string of up to 255 characters and cannot be all spaces.

·     A transit network already exists with the specified name.

·     The operation type is invalid.

·     Failed to add the resource.

·     Please specify the vni_mode field.

·     The value for the vni_mode field can only be AUTO or MANUAL.

·     You do not need to specify a VNI when the value for the vni_mode field is AUTO.

·     You must specify a VNI when the value for the vni_mode field is MANUAL.

·     The transit network name is required.

·     The value range of VNI is an integer from 1 to 16777215.

Message text

Updated transit network, request: $1

Variable fields

$1: Request message body for a transit network.

Example

Updated transit network, request: {

         "transit_network ":{

                   "operation":null

         }

}

Explanation

A transit network was edited.

Possible failure causes

·     Internal error.

·     Invalid JSON format.

·     The specified resource does not exist.

·     The operation type is invalid.

·     Please specify the operation field.

·     Failed to edit the resource.

·     You cannot edit the %s parameter.

·     This feature is not supported by the current version of the controller.

·     The description cannot exceed 255 characters.