Title | Size | Downloads |
---|---|---|
H3C Super Controller Operation Log Messages Reference-E64xx-5W400-book.pdf | 581.45 KB |
- Table of Contents
- Related Documents
-
|
H3C Super Controller |
Operation Log Messages Reference |
|
|
Document version: 5W400-20230227
Copyright © 2023 New H3C Technologies Co., Ltd. All rights reserved.
No part of this manual may be reproduced or transmitted in any form or by any means without prior written consent of New H3C Technologies Co., Ltd.
Except for the trademarks of New H3C Technologies Co., Ltd., any trademarks that may be mentioned in this document are the property of their respective owners.
The information in this document is subject to change without notice.
Contents
Viewing operation log messages
Synchronize settings from sites
Update resource pool limit settings
Add border gateway access service
Update border gateway access service
Delete border gateway access service
Update transit router connection
Delete transit router connection
Add east-west traffic application
Update east-west traffic application
Delete east-west traffic application
Update transit gateway peering
Delete transit gateway peering
Add direct connect gateway association
Update direct connect gateway association
Delete direct connect gateway association
Updated license usage info for public cloud service
Introduction
Operation logs record system operations and configuration modifications, such as application operations (installing, starting, stopping, or uninstalling an application) and team configuration. Operation log messages include operation description, result, and failure reasons, and provide reference for system analysis and maintenance.
This document assumes that the readers are familiar with data communications technologies and super controller products.
Viewing operation log messages
Select System > Log Center > Operation Log List to enter operation log view. The generated operation log messages are displayed on pages as shown in Figure 1.
Figure 1 Operation log messages
Table 1 Operation log message elements
Element |
Description |
Time |
Date and time when the log message was generated. |
Username |
Name of the user that triggered the log generation. |
User IP |
IP address of the terminal where the user performed the operation. |
Service Name |
Name of the microservice that produced the log message. |
Operation Result |
Operation result: Succeeded or Failed. |
Operation Description |
Text string that contains detailed information about the operation. |
Failure Reason |
Possible reasons for an operation failure. |
Syslog message format
The super controller can send operation logs to syslog servers through the syslog protocol. To set the IP address and port number of a syslog server, select System > Log Settings on the top navigation bar, and then select Operation Log.
By default, super controllers send operation logs in the following format:
<PRI>TIMESTAMP Hostname Service/severity/Keywords CONTENT
Table 2 Syslog message elements
Element |
Description |
<PRI> |
Priority identifier. It is calculated by using the following formula: Priority identifier=facilityx8+severity Where: · Facility represents the programming module defined by syslog. In the current software version, the facility is user-level and its value is 1. · Severity represents the syslog message severity level. For more information, see Table 4. |
TIMESTAMP |
Date and time when the event occurred. |
Hostname |
Name of the container that produced the message. |
Service |
Name of the microservice that produced the message. |
severity |
Severity level of the message. For more information, see Table 5. Two syslog message severity levels, are used. |
Keywords |
Keywords of the message that facilitate searching or memorizing. |
CONTENT |
Text string that contains detailed information about the operation, in the following format: User=username IP=user IP Description=description Result=result Cause=operation failure causes |
Table 3 lists all service modules that might produce operation log messages.
Service module name |
Description |
COS |
COS microservice module. |
DATA_CONSISTENCY |
Data consistency module. |
ICTOM |
ICTOM microservice module. |
NSO_AUDIT |
NSO microservice module |
NSO_PROVISION |
NSO module, super controller supports multi-DC interconnect |
NSO_WAN |
NSO module, super controller supports cloud-network coordination. |
PUBLIC_CLOUD |
Public cloud management and orchestration module. |
Syslog messages are classified into eight severity levels from 0 to 7. The lower the number, the higher the severity, as shown in Table 4.
Table 4 Syslog message severity levels
Level |
Severity |
Description |
0 |
Emergency |
The system is unusable. |
1 |
Alert |
Action must be taken immediately. |
2 |
Critical |
Critical condition. |
3 |
Error |
Error condition. |
4 |
Warning |
Warning condition. |
5 |
Notice |
Normal but significant condition. |
6 |
Informational |
Informational message. |
7 |
Debug |
Debugging message. |
The super controller uses two syslog message severity levels, as shown in Table 5.
Table 5 Operation log message severity levels
Level |
Severity |
Description |
6 |
Informational |
Information message. It indicates that the operation succeeded. |
4 |
Warning |
Warning condition. It indicates that the operation failed. |
Using this document
This document categories operation log messages by service module. This document explains messages in tables. Table 6 describes information provided in these tables.
Table 6 Message explanation table contents
Item |
Content |
Example |
Keyword |
Summary of the message that facilitates searching or memorizing. |
ADD_AUTH_FREEIP_OP |
Message text |
Presents the message description. |
Added an authentication-free IP: $1. |
Variable fields |
Briefly describes the variable fields in the order that they appear in the message text. The variable fields are numbered in the "$Number" form to help you identify their location in the message text. |
$1: Authentication-free user. |
Example |
Provides a real message example. |
Added an authentication-free IP: 192.168.56.13. |
Explanation |
Explains the message. |
An authentication-free user was added. |
Possible failure causes |
Provides possible causes of an operation failure. |
· Invalid IP address. · The IP address already exists. · Unable to read/write database. · Invalid role. · Invalid domain. · Invalid description. |
COS_AUDIT
This section contains COS microservice messages.
Add service
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. |
Update service
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. |
Delete service
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. |
Upload package
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. |
Delete package
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. |
Upgrade service
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. |
Update parameter settings
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. |
Add SNMPv3 server
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. |
Update SNMPv3 server
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. |
Delete SNMPv3 server
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. |
Edit alarm severity mapping
Keyword |
ACTION_UPDATE_ALARM_SEVERITY_RENDER |
Message text |
Edit alarm severity mapping: $1 |
Variable fields |
$1: Alarm severity mapping information. |
Example |
Edit alarm severity mapping: [{ "originSeverity": "1", "renderSeverity":"3" }] |
Explanation |
The alarm severity mapping information was edited. |
Possible failure causes |
· The value range for the original severity level is 0 to 21474836. · The value range for the mapped severity level is 0 to 21474836. |
DATA_CONSISTENCY
This section contains data auditing and data synchronization messages.
Audit data for a site
Keyword |
AUDIT_SITE_OP |
Message text |
Audited data for site $1. |
Variable fields |
$1: Site ID. |
Example |
Audited data for site "1dd6cb3f-3d55-ff1b-5ab0-0dd920dcb9b1". |
Explanation |
The user audited data for a site. |
Possible failure causes |
· The specified site does not exist. · The specified site is not reachable. · The system is auditing or synchronizing data for the site. Please try again later. · This feature is not supported by the current version of the controller. |
Sync data for a site
Keyword |
SYNC_SITE_OP |
Message text |
Synchronized data for site $1. |
Variable fields |
$1: Site ID. |
Example |
Synchronized data for site "1dd6cb3f-3d55-ff1b-5ab0-0dd920dcb9b1". |
Explanation |
The user synchronized data for a site. |
Possible failure causes |
· The specified site does not exist. · The specified site is not reachable. · The system is auditing or synchronizing data for the site. Please try again later. · This feature is not supported by the current version of the controller. |
ICTOM
This section contains ICTOM messages.
Import DC resource
Keyword |
ACTION_IMPORT_DC_RESOURCE |
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. |
NSO_AUDIT
This section contains NSO microservice messages.
Add network
Keyword |
ADD_NSO_NETWORK_OP |
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. |
Update network
Keyword |
UPDATE_NSO_NETWORK_OP |
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. |
Delete network
Keyword |
DEL_NSO_NETWORK_OP |
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. |
Add router
Keyword |
ADD_NSO_ROUTER_OP |
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. |
Update router
Keyword |
UPDATE_NSO_ROUTER_OP |
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. |
Delete router
Keyword |
DEL_NSO_ROUTER_OP |
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. |
Add logical link
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. |
Delete logical link
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. |
Bind subnet to vRouter
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. |
Unbind subnet from vRouter
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. |
Add site
Keyword |
ADD_NSO_SIET_OP |
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. · Failed to apply for the license. · Operation failed, because license is not enough. |
Update site
Keyword |
UPDATE_NSO_SIET_OP |
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. |
Delete site
Keyword |
DEL_NSO_SIET_OP |
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. |
Add subnet
Keyword |
ADD_NSO_SUBNET_OP |
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. |
Update subnet
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. |
Delete subnet
Keyword |
DEL_NSO_SUBNET_OP |
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. |
Synchronize settings from sites
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. |
Add tenant
Keyword |
ADD_NSO_TENANT_OP |
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. |
Update tenant
Keyword |
UPDATE_NSO_TENANT_OP |
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. |
Delete tenant
Keyword |
DEL_NSO_TENANT_OP |
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. |
Add VNI
Keyword |
ADD_NSO_VNI_OP |
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. |
Update VNI
Keyword |
UPDATE_NSO_VNI_OP |
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. |
Delete VNI
Keyword |
DEL_NSO_VNI_OP |
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. |
Update resource pool limit settings
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. |
NSO_PROVISION
This section contains operation log messages about the super controller that supports multi-DC interconnect in the NSO module.
Add transit fabric
Keyword |
ADD_TRANSIT_FABRIC_OP |
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. |
Update transit fabric
Keyword |
UPDATE_TRANSIT_FABRIC_OP |
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. |
Delete transit fabric
Keyword |
DEL_TRANSIT_FABRIC_OP |
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. · You cannot delete the transit fabric, because it contains border ports. |
Add transit router
Keyword |
ADD_NSO_TRANSIT_ROUTER_OP |
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. |
Update transit router
Keyword |
UPDATE_NSO_TRANSIT_ROUTER_OP |
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 from the transit router, because the destination subnet has been specified for a route entry. The route entry might still exist or have been pre-deleted. · 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. · When you create a tenant router access service (Service A) that shares a vRouter with another tenant router access service (Service B), the following items cannot overlap: 1. Remote CIDRs specified for Service A. 2. Remote CIDRs specified for the transit router links associated with the transit router of Service B. Remote CIDRs specified for the transit router links inherits the destination subnets specified for the remote transit router. |
Delete transit router
Keyword |
DEL_NSO_TRANSIT_ROUTER_OP |
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. · You cannot delete the transit router, because it has been used by a VPC VPN. |
Add VPC connection
Keyword |
ADD_VPC_CONNECT_OP |
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. · The transit vRouter is the border gateway group type. You cannot both connect a tenant vRouter to and configure a transit vRouter link for it. · When you create a tenant router access service (Service A) that shares a vRouter with another tenant router access service (Service B), the following items cannot overlap: 1. Remote CIDRs specified for Service A. 2. Local CIDRs specified for the transit router links associated with the transit router of Service B. · When you create a tenant router access service (Service A) that shares a vRouter with another tenant router access service (Service B), the following items cannot overlap: 1. Remote CIDRs specified for Service A. 2. Remote CIDRs specified for the transit router links associated with the transit router of Service B. |
Update VPC connection
Keyword |
UPDATE_VPC_CONNECT_OP |
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. · When you create a tenant router access service (Service A) that shares a vRouter with another tenant router access service (Service B), the following items cannot overlap: 1. Remote CIDRs specified for Service A. 2. Local CIDRs specified for the transit router links associated with the transit router of Service B. · When you create a tenant router access service (Service A) that shares a vRouter with another tenant router access service (Service B), the following items cannot overlap: 1. Remote CIDRs specified for Service A. 2. Remote CIDRs specified for the transit router links associated with the transit router of Service B. |
Delete VPC connection
Keyword |
DEL_VPC_CONNECT_OP |
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. |
Deploy transit fabric
Keyword |
DEPLOY_TRANSIT_FABRIC_OP |
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. |
Add EBGP connection
Keyword |
ADD_NSO_EBGP_CONNECTION_OP |
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. |
Delete EBGP connection
Keyword |
DEL_NSO_EBGP_CONNECTION_OP |
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. |
Add border gateway access service
Keyword |
ADD_GATEWAY_ACCESS_OP |
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. · The border gateway specified for a border gateway access service cannot be a tenant-exclusive border gateway. |
Update border gateway access service
Delete border gateway access service
Keyword |
DEL_GATEWAY_ACCESS_OP |
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. |
Add route entry
Keyword |
ADD_NSO_ROUTE_ENTRY_OP |
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. |
Update route entry
Keyword |
UPDATE_ NSO_ROUTE_ENTRY_OP |
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. |
Delete route entry
Keyword |
DEL_NSO_ROUTE_ENTRY_OP |
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. |
Add vPort
Keyword |
ADD_VPORT_OP |
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. |
Update vPort
Keyword |
UPDATE_VPORT_OP |
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. |
Delete vPort
Keyword |
DEL_VPORT_OP |
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. |
Add floating IP
Keyword |
ADD_FLOATING_IP_OP |
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. |
Update floating IP
Keyword |
UPDATE_FLOATING_IP_OP |
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. |
Delete floating IP
Keyword |
DEL_FLOATING_IP_OP |
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. |
Add transit network
Keyword |
ADD_TRANSIT_ NETWORK _OP |
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. |
Update transit network
Keyword |
UPDATE_ TRANSIT_NETWORK_OP |
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. · 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. |
Delete transit network
Keyword |
DEL_TRANSIT_NETWORK_OP |
Message text |
Deleted transit network $1 |
Variable fields |
$1: Transit network ID. |
Example |
Deleted transit network edfed45a-d3a9-4bb0-bfe4-b5fe5c3c9027 |
Explanation |
A transit network 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. · You cannot delete the specified transit network, because it is bound to a tenant network. |
Add tenant network
Keyword |
ADD_TENANT_NETWORK_OP |
Message text |
Added tenant network, request: $1 |
Variable fields |
$1: Request message body for a tenant network. |
Example |
Added tenant network, request: { " tenant_network": { "name": "TntN-1", "description": "", "site_id": "69a17205-6c32-4498-b5a9-1fa51f277251", "tenant_id": "10ec8773-8b45-46d1-92c3-3c279758f9c5", "network_id": "eeea49fa-3580-4d7f-a20f-78e8ee22aa4a", "transit_network_id": "1d1ffb84-e792-474d-adf8-1d8decbe3ce5", "transit_fabric_id": "4be3cb06-b215-4700-aec4-cc632493aeff" } } |
Explanation |
A tenant network was added. |
Possible failure causes |
· Internal error. · Invalid JSON format. · Invalid UUID. · The value for the sortOrder field can only be asc or desc. · The operation type is invalid. · You cannot directly delete resources specified in a configuration deployment. · The specified transit fabric does not exist. · Please specify a transit fabric ID. · The specified vNetwork does not exist. · The UUID of network is required. · The UUID of transit network is required. · The specified transit network does not exist. · The specified tenant network does not exist. · The tenant network name is required. · A tenant network name must be a case-sensitive string of up to 255 characters and cannot be all spaces. · A tenant network description must be string of up to 255 characters. · A tenant network already exists with the specified name. · The site of the tenant network is not in the specified transit fabric. · The tenant to which the tenant network is bound is not in the specified site. · The vNetwork to which the tenant network is bound does not belong to the specified tenant. · The transit network to which the tenant network is bound does not belong to the specified transit fabric. · The sites of tenant networks on the same transit network cannot be the same. · The transit network to which the tenant network is bound does not exist. |
Update tenant network
Keyword |
UPDATE_TENANT_NETWORK_OP |
Message text |
Updated tenant network, request: $1 |
Variable fields |
$1: Request message body for a tenant network. |
Example |
Updated tenant network, request: { "transit_network ":{ "operation":null } } |
Explanation |
A tenant 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. · This feature is not supported by the current version of the controller. · A tenant network description must be string of up to 255 characters. · To predelete the transit network, make sure all tenant network bound to the transit network have been predeleted. · You cannot change the transit network bound to the tenant network. |
Delete tenant network
Keyword |
DEL_TENANT_NETWORK_OP |
Message text |
Deleted tenant network $1 |
Variable fields |
$1: Tenant network ID. |
Example |
Deleted tenant network edfed45a-d3a9-4bb0-bfe4-b5fe5c3c9027 |
Explanation |
A tenant network 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. |
Add transit router connection
Keyword |
ADD_TRANSIT_ROUTER_CONNECTION_OP |
Message text |
Added a transit router connection, request: $1 |
Variable fields |
$1: Transit router connection request information. |
Example |
Added a transit router connection, request: { "transit_router_connection": { "name": "LINK-0", "description": "", "local_transit_router_id": "b83199c5-db63-43f5-a32b-af01585963c1", "peer_transit_router_id": "7456cd3b-2abd-4f38-8526-7f2f142e07b4", "transit_fabric_id": "91fbe806-8505-4d1e-b37d-ec970b42c5d7", "local_cidrs": ["26.0.0.0/16"], "peer_cidrs": ["15.0.0.0/16"], "master_site_id": "8fa2eb09-b3b7-4751-91a1-4bb97911dca8", "master_site_name": "118.198", "master_firewall_service_id": "d8dbb854-5a37-46ec-89d8-5be49e87d241", "master_firewall_service_name": "1" } } |
Explanation |
A transit router connection was added. |
Possible failure causes |
· Internal error. · Invalid JSON format. · Invalid UUID. · The operation type is invalid. · The name of a transit router link must be a case-sensitive string of up to 255 characters and cannot contain only spaces. · The description cannot exceed 255 characters. · The local transit router and the remote transit router cannot be the same. · The primary and secondary firewall services cannot be in the same site. · Please specify local CIDRs. · Please specify remote CIDRs. · Invalid local CIDRs. · Invalid remote CIDRs. · The local CIDRs cannot overlap. · The remote CIDRs cannot overlap. · A transit router link already exists with the specified name. · The tenant router accesses associated with the transit router cannot be enabled with the firewall service. · When two transit router links use the same local transit router, they must use the same firewall services. · The specified transit routers already have established a transit router link. · The specified transit fabric does not exist. · Please specify a transit fabric ID. · The specified transit router does not exist. · The intercommunication type of the local transit router must be east-west. · Please specify a local transit router ID. · The specified transit router does not exist. · The edge device to external network must be border device for the transit router. · When you specify a site to select the primary or secondary firewall service, make sure the site is not bound to any border gateway access associated with the remote transit router. · Please specify a remote transit router ID. · The site to which the primary firewall service belongs does not exist. · Please specify a site ID before configuring the primary firewall service. · The site to which the secondary firewall service belongs does not exist. · Please specify a primary firewall service ID. · Please first specify the site in which the secondary firewall service exists before specifying the secondary firewall service. · For two transit vRouter links with the same local transit vRouter, make sure their remote CIDRs do not overlap. · The transit vRouter is the border gateway group type. You cannot both connect a tenant vRouter to and configure a transit vRouter link for it. · Please specify the type as VFW and the family as CGSR for the firewall resource. · Please specify a primary firewall resource ID. · The primary firewall resource does not exist in the specified site. · The secondary firewall resource does not exist in the specified site. · Please first specify the site in which the secondary firewall resource exists before specifying the secondary firewall resource. · When two transit router links use the same local transit router, they must use the same firewall resources. · The gateway member bound to the firewall resource must be in a border device group whose network position is border gateway and DCI. · When you create a tenant router access service (Service A) that shares a vRouter with another tenant router access service (Service B), the following items cannot overlap: 1. Remote CIDRs specified for Service A. 2. Local CIDRs specified for the transit router links associated with the transit router of Service B. · When you create a tenant router access service (Service A) that shares a vRouter with another tenant router access service (Service B), the following items cannot overlap: 1. Remote CIDRs specified for Service A. 2. Remote CIDRs specified for the transit router links associated with the transit router of Service B. · When you specify a firewall resource for a border gateway access service, make sure the gateway members associated with that firewall resource do not belong to any tenant-exclusive border gateway. |
Update transit router connection
Keyword |
UPDATE_TRANSIT_ROUTER_CONNECTION_OP |
Message text |
Updated transit router connection, request: $1 |
Variable fields |
$1: Transit router connection request information. |
Example |
Updated transit router connection, request: { "transit_router_connection": { "operation": "DELETE" } } |
Explanation |
A transit router connection 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. · The name of a transit router link must be a case-sensitive string of up to 255 characters and cannot contain only spaces. · The description cannot exceed 255 characters. · When the intercommunication type of the remote transit router is border gateway group, make sure the remote CIDRs are the same as the destination CIDRs of the remote transit router. · A transit router link already exists with the specified name. · For two transit vRouter links with the same local transit vRouter, make sure their remote CIDRs do not overlap. · When you create a tenant router access service (Service A) that shares a vRouter with another tenant router access service (Service B), the following items cannot overlap: 1. Remote CIDRs specified for Service A. 2. Local CIDRs specified for the transit router links associated with the transit router of Service B. · When you create a tenant router access service (Service A) that shares a vRouter with another tenant router access service (Service B), the following items cannot overlap: 1. Remote CIDRs specified for Service A. 2. Remote CIDRs specified for the transit router links associated with the transit router of Service B. |
Delete transit router connection
Keyword |
DEL_TRANSIT_ROUTER_CONNECTION_OP |
Message text |
Deleted transit router connection $1 |
Variable fields |
$1: Transit router connection ID. |
Example |
Deleted transit router connection "255263da-d0f0-4bf6-8cba-46917b35cba3" |
Explanation |
A transit router connection was deleted. |
Possible failure causes |
· Internal error. · The specified resource does not exist. · The transit fabric configuration is being deployed Please try again later. · You cannot directly delete resources specified in a configuration deployment. |
Add IPsec profile
Keyword |
ADD_IPSEC_OP |
Message text |
Added an IPsec profile. Request: $1 |
Variable fields |
$1: IPsec profile request information. |
Example |
Added an IPsec profile. Request: { "vpn_connection": { "transit_fabric_id": "cd75c1a1-c610-435b-8f61-a9511f803a89", "name": "ipsec1", "description": "ipsec1", "local_transit_router_id": "7b8074ce-f6fa-4eac-b8a6-dca42db682a1", "local_network_cidr": "3.1.1.1/24", "local_public_ip": "10.99.3.1", "local_bgp_as": 2345, "ip_version": "IPV4", "remote_transit_router_id": "4a99b69c-8f0a-4239-8bd8-190ec64a92e0", "remote_network_cidr": "4.1.1.1/24", "tunnel_options": [ { "tunnel_number": 1, "id": "2a99b69c-8f0a-4239-8bd8-190ec64a92e1", "pre_share_key": "abcdefg12345", "phase1_encryption_algorithms": [ "AES128" ], "phase1_integrity_algorithms": [ "SHA1" ], "phase1_dh_group_numbers": [ "2" ], "phase2_encryption_algorithms": [ "AES128" ], "phase2_integrity_algorithms": [ "SHA1" ], "phase2_dh_group_numbers": [ "2" ], "phase1_lifetime_seconds": 28800, "phase2_lifetime_seconds": 3600, "ike_versions": [ "ikev1" ], "rekey_margin_time_seconds": 540, "rekey_fuzz_percentage": 100, "replay_window_size": 1024, "dpd_timeout_seconds": 30, "dpd_timeout_action": "clear", "startup_action": "add" }, { "tunnel_number": 2, "id": "2a99b69c-8f0a-4239-8bd8-190ec64a92e2", "pre_share_key": "abcdefg12345", "phase1_encryption_algorithms": [ "AES128" ], "phase1_integrity_algorithms": [ "SHA1" ], "phase1_dh_group_numbers": [ "2" ], "phase2_encryption_algorithms": [ "AES128" ], "phase2_integrity_algorithms": [ "SHA1" ], "phase2_dh_group_numbers": [ "2" ], "phase1_lifetime_seconds": 28800, "phase2_lifetime_seconds": 3600, "ike_versions": [ "ikev1" ], "rekey_margin_time_seconds": 540, "rekey_fuzz_percentage": 100, "replay_window_size": 1024, "dpd_timeout_seconds": 30, "dpd_timeout_action": "clear", "startup_action": "add" } ] } } |
Explanation |
An IPsec profile was added. |
Possible failure causes |
· Internal error. · Invalid JSON format. · Invalid UUID. · The specified local transit router does not exist. · The description of an IPsec profile cannot exceed 255 characters. · The name of an IPsec profile cannot exceed 64 characters. Only letters and digits are supported. · Invalid local CIDRs. · Invalid remote CIDRs. · Invalid public IP address. · Only IPv4 is supported. · The intercommunication type of the local transit router must be south-north. · The IPsec must be configured with options for two and only two tunnels. · The IPsec must be configured with options for two and only two tunnels. · Only one phase 1 encryption algorithm can be configured. · Invalid phase 1 encryption algorithm. · Only one phase 2 encryption algorithm can be configured. · Invalid phase 2 encryption algorithm. · Only one phase 1 authentication algorithm can be configured. · Invalid phase 1 authentication algorithm. · Only one phase 2 authentication algorithm can be configured. · Invalid phase 2 authentication algorithm. · Only one phase 1 DH group number can be configured. · Invalid phase 1 DH group number. · Only one phase 2 DH group number can be configured. · Invalid phase 2 DH group number. · Invalid IKE version. · Only one IKE version can be configured. · The phase 1 lifetime value must be an integer in the range of 900 to 28800. · The phase 2 lifetime value must be an integer in the range of 900 to 3600. · The phase 2 lifetime value must be less than the phase 1 lifetime value. · The DPD timeout value must be an integer equal to or greater than 30. · The value for the rekey margin time (seconds) parameter must be an integer in the range of 60 to half the phase 2 lifetime. · The value for the rekey fuzz (percentage) parameter must be an integer in the range of 0 to 100. · The value for the replay window size (packets) parameter must be an integer in the range of 64 to 2048. · The DPD timeout action can only be clear, restart, or none. · The startup action can only be add or start. · You can specify the IKE version as only IKEv2 when the startup action is Start. · You can specify the IKE version as only IKEv2 when the phase 1 encryption algorithm is AES128-GCM-16 or AES256-GCM-16. · The transit router on the private cloud side bound to the IPsec profile must be a transit router associated with a transit router link and not associated with a tenant router access service. · The transit router bound to a tenant router access service cannot be bound to public VIFs and IPsec profiles. |
Update IPsec profile
Keyword |
UPDATE_IPSEC_OP |
Message text |
Updated IPsec profile “$1”. Request: $2 |
Variable fields |
$1: IPsec profile ID. $2: IPsec profile request information. |
Example |
Updated IPsec profile "c6bfd1a0-67ff-4699-b300-b9732f408772". Request: { "vpn_connection": { "operation": "DELETE", "description": "ipsec1", "name": "ipsec1-0", "local_network_cidr": "3.1.1.1/24", "remote_network_cidr": "4.1.1.1/24", "operation": "UPDATE" } } |
Explanation |
An IPsec profile was edited. |
Possible failure causes |
· Internal error. · Invalid JSON format. · The specified resource does not exist. · The description of an IPsec profile cannot exceed 255 characters. · The name of an IPsec profile cannot exceed 64 characters. Only letters and digits are supported. · Invalid local CIDRs. · Invalid remote CIDRs. |
Delete IPsec profile
Keyword |
DEL_IPSEC_OP |
Message text |
Deleted IPsec profile $1 |
Variable fields |
$1: IPsec profile ID. |
Example |
Deleted IPsec profile edfed45a-d3a9-4bb0-bfe4-b5fe5c3c9027 |
Explanation |
An IPsec profile was deleted. |
Possible failure causes |
· Internal error. · The specified resource does not exist. · Failed to delete the resource. |
Add VPC VPN
Keyword |
ADD_VPC_VPN_OP |
Message text |
Added a VPC VPN. Request: $1 |
Variable fields |
$1: VPC VPN request information. |
Example |
Added a VPC VPN. Request: { "vpc_direct_connection": { "name": "VPCLINK2", "description": "12345", "transit_fabric_id": "91fbe806-8505-4d1e-b37d-ec970b42c5d7", "local_transit_router_id": "8d5fa381-46b0-43af-9dbc-c01fcd6c1565", "border_port_id": "6t5fa381-46b0-43af-9dbc-c01fcd6c1565", "connect_interface_type": "SUB_INTERFACE", "connect_interface_number": 9, "connect_vlan": null, "bgp_password": "23456", "bfd_flag": true, "direct_connect_gateway_id": "13f4ed84-9879-40a1-abae-9fe56894cfc9", "virtual_interface_id": "80e1cd49-aefe-47d0-9c3f-3251ed4756c8", "tgw_id": "013cb035-c89c-46ec-8d66-fab8474d6473", "remote_transit_router_id": "a26743b6-127c-4b30-9713-54335834088d", } } |
Explanation |
A VPC VPN was added. |
Possible failure causes |
· Internal error. · Invalid JSON format. · Invalid UUID. · The site of the border port has been configured with a VPC VPN or public VIF bound to the same transit vRouter. · The virtual interface has been specified for a VPC VPN or public VIF. · For two VPC VPNs or public VIFs using the same transit vRouter, specify different border ports of the same device group in a site or border ports in different sites for them. · Please specify a border port ID. · The specified border port does not exist. · Invalid interconnect interface type. · When the interconnect interface type is VLAN interface, the value for the interconnect VLAN must be an integer in the range of 1 to 4094. · When the interconnect interface type is subinterface. the value for the subinterface number must be an integer in the range of 1 to 4094. · The subinterface number and interconnect VLAN cannot be both specified. · The VPC VPN name cannot exceed 64 characters and only supports letters and digits. · Please specify a VPC VPN name. · The description cannot exceed 255 characters. · The password is case sensitive and cannot exceed 80 characters. Only letters, digits, and special characters except for question marks (?) are supported. · The specified virtual interface does not exist on the public cloud. · The specified VPN gateway does not exist on the public cloud. · The specified transit gateway does not exist on the public cloud. · The specified transit router does not exist on the public cloud. · The port type does not match the specified border port type. · A VPC VPN already exists with the specified name. · The VPN gateway, transit gateway, transit router, and virtual interface must have bindings on the public cloud side. · Processing on the public cloud side failed. · The intercommuncation type of the transit router on the private cloud side bound to the VPC VPN must be east-west. |
Update VPC VPN
Keyword |
UPDATE_VPC_VPN_OP |
Message text |
Updated a VPC VPN “$1”. Request: $2 |
Variable fields |
$1: VPC VPN ID. $2: VPC VPN request information. |
Example |
Updated a VPC VPN “c6bfd1a0-67ff-4699-b300-b9732f408772". Request: { "vpc_direct_connection": { "description": "12345", "bgp_password": "23456", "bfd_flag": true, "operation": "UPDATE" } } |
Explanation |
A VPC VPN was edited. |
Possible failure causes |
· Internal error. · Invalid JSON format. · The specified resource does not exist. · The site of the border port has been configured with a VPC VPN or public VIF bound to the same transit vRouter. · The description cannot exceed 255 characters. · The password is case sensitive and cannot exceed 80 characters. Only letters, digits, and special characters except for question marks (?) are supported. |
Delete VPC VPN
Keyword |
DEL_VPC_VPN_OP |
Message text |
Deleted VPC VPN “$1”. |
Variable fields |
$1: VPC VPN ID. |
Example |
Deleted VPC VPN “edfed45a-d3a9-4bb0-bfe4-b5fe5c3c9027”. |
Explanation |
A VPC VPN was deleted. |
Possible failure causes |
· Internal error. · The specified resource does not exist. |
Add public VIF
Keyword |
ADD_PUBLIC_VIF_OP |
Message text |
Added a public VIF. Request: $1 |
Variable fields |
$1: Public VIF request information. |
Example |
Added a public VIF. Request: { "service_direct_connection": { "name": "SERVICELINK2", "description": "12345", "transit_fabric_id": "91fbe806-8505-4d1e-b37d-ec970b42c5d7", "local_transit_router_id": "8d5fa381-46b0-43af-9dbc-c01fcd6c1565", "border_port_id": "6t5fa381-46b0-43af-9dbc-c01fcd6c1565", "connect_interface_type": "SUB_INTERFACE", "connect_interface_number": 9, "connect_vlan": null, "bgp_password": "23456", "bfd_flag": true, "virtual_interface_id": "80e1cd49-aefe-47d0-9c3f-3251ed4756c8" } } |
Explanation |
A public VIF was added. |
Possible failure causes |
· Internal error. · Invalid JSON format. · Invalid UUID. · The site of the border port has been configured with a VPC VPN or public VIF bound to the same transit vRouter. · To bind a transit vRouter in the private cloud to the public VIF, make sure the vRouter has a vRouter link whose peer end is an east-west transit vRouter. · The virtual interface has been specified for a VPC VPN or public VIF. · For two VPC VPNs or public VIFs using the same transit vRouter, specify different border ports of the same device group in a site or border ports in different sites for them. · Please specify a border port ID. · The specified border port does not exist. · Invalid interconnect interface type. · When the interconnect interface type is VLAN interface, the value for the interconnect VLAN must be an integer in the range of 1 to 4094. · When the interconnect interface type is subinterface. the value for the subinterface number must be an integer in the range of 1 to 4094. · The subinterface number and interconnect VLAN cannot be both specified. · The public VIF name cannot exceed 64 characters and only supports letters and digits. · Please specify a public VIF name. · The password is case sensitive and cannot exceed 80 characters. Only letters, digits, and special characters except for question marks (?) are supported. · A public VIF already exists with the specified name. · The specified virtual interface does not exist on the public cloud. · The port type does not match the specified border port type. · Processing on the public cloud side failed. · The transit router on the private cloud side bound to the public VIF must be an east-west transit router associated with a transit router link and not associated with a tenant router access service. · To bind a transit vRouter in the private cloud to the public VIF, make sure the vRouter has a vRouter link whose peer end is an east-west transit vRouter. · The transit router bound to a tenant router access service cannot be bound to public VIFs and IPsec profiles. |
Update public VIF
Keyword |
UPDATE_PUBLIC_VIF_OP |
Message text |
Updated a public VIF $1. Request: $2 |
Variable fields |
$1: Public VIF ID. $2: Public VIF request information. |
Example |
Updated a public VIF “edfed45a-d3a9-4bb0-bfe4-b5fe5c3c9027”. Request: { "service_direct_connection": { "description": "12345", "bgp_password": "23456", "bfd_flag": true, "operation": "UPDATE" } } |
Explanation |
A public VIF was edited. |
Possible failure causes |
· Internal error. · Invalid JSON format. · The site of the border port has been configured with a VPC VPN or public VIF bound to the same transit vRouter. · To bind a transit vRouter in the private cloud to the public VIF, make sure the vRouter has a vRouter link whose peer end is an east-west transit vRouter. · The specified resource does not exist. · The description cannot exceed 255 characters. · The password is case sensitive and cannot exceed 80 characters. Only letters, digits, and special characters except for question marks (?) are supported. |
Delete public VIF
Keyword |
DEL_PUBLIC_VIF_OP |
Message text |
Deleted public VIF “$1” |
Variable fields |
$1: Public VIF ID. |
Example |
Deleted public VIF "60ede326-144e-4949-a186-65891ae70bf0" |
Explanation |
A public VIF was deleted. |
Possible failure causes |
· Internal error. · The specified resource does not exist. |
Add border port
Keyword |
ADD_BORDER_PORT_OP |
Message text |
Added a border port. Request: $1 |
Variable fields |
$1: Border port request information. |
Example |
Added a border port. Request: { " tenant_network": { "name": "TntN-1", "description": "", "site_id": "69a17205-6c32-4498-b5a9-1fa51f277251", "tenant_id": "10ec8773-8b45-46d1-92c3-3c279758f9c5", "network_id": "eeea49fa-3580-4d7f-a20f-78e8ee22aa4a", "transit_network_id": "1d1ffb84-e792-474d-adf8-1d8decbe3ce5", "IPSEC_id": "4be3cb06-b215-4700-aec4-cc632493aeff" } } |
Explanation |
A border port was added. |
Possible failure causes |
· Internal error. · Invalid JSON format. · Invalid UUID. · Please specify a border port name. · A border port name must be a case-sensitive string of up to 255 characters and cannot be all spaces. · A border port description must be a string of up to 255 characters. · Please specify a port type. · You cannot delete the border port, because it has been used by a VPC VPN or public VIF. · Please specify a device port name. · Please specify a device port type. · The device port type is invalid. · No ports found on the specified device. · Ports of the specified type do not exist on the device. · The device group is bound by a leased line port. · The port on the device has been specified as a border port. |
Update border port
Keyword |
UPDATE_BORDER_PORT_OP |
Message text |
Updated a border port $1. Request: $2 |
Variable fields |
$1: Border port ID. $2: Border port request information. |
Example |
Updated a border port edfed45a-d3a9-4bb0-bfe4-b5fe5c3c9027. Request: { "transit_network ":{ "operation":null } } |
Explanation |
A border port was edited. |
Possible failure causes |
· Internal error. · Invalid JSON format. · The specified resource does not exist. · Please specify a border port name. · A border port name must be a case-sensitive string of up to 255 characters and cannot be all spaces. · A border port description must be a string of up to 255 characters. |
Delete border port
Keyword |
DEL_BORDER_PORT_OP |
Message text |
Deleted border port $1 |
Variable fields |
$1: Border port ID. |
Example |
Deleted border port edfed45a-d3a9-4bb0-bfe4-b5fe5c3c9027 |
Explanation |
A border port was deleted. |
Possible failure causes |
· Internal error. · The specified resource does not exist. · Failed to delete the resource. |
NSO_WAN
This section contains NSO_WAN messages.
Add WAN controller
Keyword |
ADD_WAN_CONTROLLER_OP |
Message text |
Added WAN controller, request: $1 |
Variable fields |
$1: WAN controller request message body. |
Example |
Added WAN controller, request: { "wan": { "id": "98a36a17-2190-919e-0a3f-81d6ee5177e9", "name": "wan1", "description": "wan1", "type": "WAN Carrier", "url": "http://192.168.162.202:30000", "username": "admin", "password": "sdn123456" } } |
Explanation |
A WAN controller was added. |
Possible failure causes |
· Internal error. · Invalid JSON format. · Up to 64 characters. The name cannot contain spaces. · Up to 255 characters. · Invalid WAN controller type. · Up to 255 characters. Spaces are not supported. · 8 to 255 characters. The password must contain characters from at least two of the following categories: digits, uppercase letters, lowercase letters, and special characters. · Invalid WAN controller URL. · The URL of the WAN controller has been used. · A WAN controller already exists with the specified name. · The WAN controller does not exist. |
Update WAN controller
Keyword |
UPDATE_WAN_CONTROLLER_OP |
Message text |
Updated WAN controller “$1”, request: $2 |
Variable fields |
$1: WAN controller ID. $2: WAN controller request message body. |
Example |
Updated WAN controller "c6bfd1a0-67ff-4699-b300-b9732f408772", request: { "wan": { "name": "wan1", "description": "wan1", "url": "http://192.168.162.202:30000", "username": "admin", "password": "sdn123456" } } |
Explanation |
A WAN controller was edited. |
Possible failure causes |
· Internal error. · Invalid JSON format. · Up to 64 characters. The name cannot contain spaces. · Up to 255 characters. · Up to 255 characters. Spaces are not supported. · 8 to 255 characters. The password must contain characters from at least two of the following categories: digits, uppercase letters, lowercase letters, and special characters. · Invalid WAN controller URL. · The URL of the WAN controller has been used. · A WAN controller already exists with the specified name. · The WAN controller does not exist. |
Delete WAN controller
Keyword |
DEL_WAN_CONTROLLER_OP |
Message text |
Deleted WAN controller $1 |
Variable fields |
$1: WAN controller ID. |
Example |
Deleted WAN controller edfed45a-d3a9-4bb0-bfe4-b5fe5c3c9027 |
Explanation |
A WAN controller was deleted. |
Possible failure causes |
· Internal error. · The specified resource does not exist. · You cannot delete the WAN controller when it is bound to a WAN link. |
Add WAN link
Keyword |
ADD_WAN_LINK_OP |
Message text |
Added WAN link, request: $1 |
Variable fields |
$1: WAN link request message body. |
Example |
Added WAN link, request: { "device_groups_wan_link": { "id": "c28993fd-8fa0-88ce-a2e2-13dfe7d67ee6", "name": "link1", "description": "", "site_id": "c28993fd-8fa0-88ce-a2e2-13dfe7d67ee6", "fabric_id": "7b71ae37-e66a-439d-a05e-e1b7b8d6a0f0", "device_groups_id": "7b71ae37-e66a-439d-a05e-e1b7b8d6a0f0", "wan_id": "c28993fd-8fa0-88ce-a2e2-13dfe7d67ee6", "policy_group_id": "c28993fd-8fa0-88ce-a2e2-13dfe7d67ee6" } } |
Explanation |
A WAN link was added. |
Possible failure causes |
· Internal error. · Invalid JSON format. · Invalid UUID. · Internal error. · Please specify a name for the WAN link. · Up to 255 characters. The name cannot contain only spaces. · Up to 255 characters. · The WAN controller does not exist. · Failed to obtain SR policy group information from the WAN controller. · The border device group does not support DC interconnect. · The SR policy group does not exist on the WAN controller. · The border device group is already bound to another WAN link. · A WAN link already exists with the specified name. |
Update WAN link
Keyword |
UPDATE_WAN_LINK_OP |
Message text |
Updated WAN link, request: $1 |
Variable fields |
$1: WAN link request message body. |
Example |
Updated WAN link, request: { "device_groups_wan_link": { "name": "link1", "description": "link1" } } |
Explanation |
A WAN link was edited. |
Possible failure causes |
· Internal error. · Invalid JSON format. · Up to 255 characters. The name cannot contain only spaces. · Up to 255 characters. · The WAN controller does not exist. |
Delete WAN link
Keyword |
DEL_WAN_LINK_OP |
Message text |
Deleted WAN link “$1”. |
Variable fields |
$1: ID of the WAN link. |
Example |
Deleted WAN link “edfed45a-d3a9-4bb0-bfe4-b5fe5c3c9027” |
Explanation |
A WAN link was deleted. |
Possible failure causes |
· Internal error. · The specified resource does not exist. · You cannot delete the WAN link, because it has a minimum of one flow group. |
Add flow group
Keyword |
ADD_FLOW_GROUP_OP |
Message text |
Added flow group, request: $1 |
Variable fields |
$1: Request message body of the application group. |
Example |
Added flow group, request: { "flow_group": { "id": "c28993fd-8fa0-88ce-a2e2-13dfe7d67ee6", "device_groups_wan_link_id": "c28993fd-8fa0-88ce-a2e2-13dfe7d67ee6", "flow_group_id": "c28993fd-8fa0-88ce-a2e2-13dfe7d67ee6", "dscp_type": "dscp-ipv4" } } |
Explanation |
An application group was added. |
Possible failure causes |
· Internal error. · Invalid JSON format. · Invalid UUID. · Invalid flow group DSCP type. · The WAN link does not exist. · The flow group does not exist on the WAN controller. |
Delete flow group
Keyword |
DEL_FLOW_GROUP_OP |
Message text |
Deleted flow group "$1" |
Variable fields |
$1: ID of the application group. |
Example |
Deleted flow group "60ede326-144e-4949-a186-65891ae70bf0" |
Explanation |
An application group was deleted. |
Possible failure causes |
· Internal error. · The specified resource does not exist. |
Add east-west traffic application
Keyword |
ADD_EAST_WEST_APPLICATION_OP |
Message text |
Added east-west traffic application, request: $1 |
Variable fields |
$1: Request message body of the east-west traffic application. |
Example |
Added east-west traffic application, request: { "east_west_application": { "id": "c28993fd-8fa0-88ce-a2e2-13dfe7d67ee6", "description": "", "name": "app1", "transit_router_id": "e28993fd-8fa0-88ce-a2e2-13dfe7d67ee6", "local_site_id": "0fb7f538-9535-45bb-9881-27d71e6c508c", "local_router_id": "0fb7f538-9535-45bb-9881-27d71e6c508c", "local_subnets": [ "4fb7f538-9535-45bb-9881-27d71e6c508c", "1fb7f538-9535-45bb-9881-27d71e6c508c" ], "local_cidrs": [], "wan_flow_group_id": "c28993fd-8fa0-88ce-a2e2-13dfe7d67ee6", "dscp": "20", "peer_site_id": "0fb7f538-9535-45bb-9881-27d71e6c508c", "peer_router_id": "0fb7f538-9535-45bb-9881-27d71e6c508c", "peer_subnets": [ "9fb7f538-9535-45bb-9881-27d71e6c508c", "8fb7f538-9535-45bb-9881-27d71e6c508c" ], "peer_cidrs": [] } } |
Explanation |
An east-west traffic application was added. |
Possible failure causes |
· Internal error. · Invalid JSON format. · The specified transit router does not exist. · The specified local vRouter does not exist. · The specified remote vRouter does not exist. · Please specify a local vRouter ID. · Please specify a remote vRouter ID. · The specified local vRouter is not associated with the transit router or is not deployed in the local site. · The specified remote vRouter is not associated with the transit router or is not deployed in the remote site. · Please specify local subnet IDs or local CIDRs. · Please specify remote subnet IDs. · Some of the specified local subnets do not exist. · Some of the specified remote subnets do not exist. · Some of the specified local subnets are not associated with the transit router. · Some of the specified local CIDRs are not associated with the transit router. · Some of the specified remote subnets are not associated with the transit router. · The border device group in the WAN link associated with the application group is different from that associated with the local vRouter. · Please specify a DSCP value. · The specified DSCP value must be in the valid DSCP value range. · The specified tenant does not have any border gateway binding. · The specified tenant does not have any border gateway binding or the border gateway bound to the specified tenant is not associated with any device groups used for DCI deployment. · The description of an east-west traffic application cannot exceed 255 characters. · The name of an east-west traffic application cannot exceed 255 characters. · Please specify an east-west traffic application name. · Invalid local CIDRs. · Invalid remote CIDRs. · The local CIDRs cannot overlap. · The remote CIDRs cannot overlap. · Please specify a local site ID. · Please specify a remote site ID. · The specified local site does not exist. · The specified remote site does not exist. · The local site and the remote site must be different. · The specified transit router is not deployed. · The interconnect type of the specified transit router must be east-west. · If you do not specify a remote vRouter, you cannot specify remote subnets and you must specify remote CIDRs. · There is no tenant bound to the exit gateway on the specified site. · Remote subnets or remote CIDRs must use the same IP protocols as local subnets or local CIDRs. |
Update east-west traffic application
Keyword |
UPDATE_EAST_WEST_APPLICATION_OP |
Message text |
Updated east-west traffic application "$1", request: $2 |
Variable fields |
$1: ID of the east-west traffic application. $2: Request message body of the east-west traffic application. |
Example |
Updated east-west traffic application "c6bfd1a0-67ff-4699-b300-b9732f408772", request: { { "east_west_application": { "description": "", "name": "app1", "local_subnets": [ "4fb7f538-9535-45bb-9881-27d71e6c508c", "1fb7f538-9535-45bb-9881-27d71e6c508c" ], "local_cidrs": [], "wan_flow_group_id": "c28993fd-8fa0-88ce-a2e2-13dfe7d67ee6", "dscp": "20", "peer_subnets": [ "9fb7f538-9535-45bb-9881-27d71e6c508c", "8fb7f538-9535-45bb-9881-27d71e6c508c" ], "peer_cidrs": [] } } |
Explanation |
An east-west traffic application was edited. |
Possible failure causes |
· Internal error. · Invalid JSON format. · Please specify local subnet IDs or local CIDRs. · Please specify remote subnet IDs. · Some of the specified local subnets do not exist. · Some of the specified remote subnets do not exist. · Some of the specified local subnets are not associated with the transit router. · Some of the specified local CIDRs are not associated with the transit router. · Some of the specified remote subnets are not associated with the transit router. · Please specify a DSCP value. · The specified DSCP value must be in the valid DSCP value range. · The description of an east-west traffic application cannot exceed 255 characters. · The name of an east-west traffic application cannot exceed 255 characters. · Invalid local CIDRs. · Invalid remote CIDRs. · The local CIDRs cannot overlap. · The remote CIDRs cannot overlap. · If you do not specify a remote vRouter, you cannot specify remote subnets and you must specify remote CIDRs. · Remote subnets or remote CIDRs must use the same IP protocols as local subnets or local CIDRs. |
Delete east-west traffic application
Keyword |
DEL_EAST_WEST_APPLICATION_OP |
Message text |
Deleted east-west traffic application $1 |
Variable fields |
$1: ID of the east-west traffic application. |
Example |
Deleted east-west traffic application edfed45a-d3a9-4bb0-bfe4-b5fe5c3c9027 |
Explanation |
An east-west traffic application was deleted. |
Possible failure causes |
· Internal error. · The specified resource does not exist. |
PUBLIC_CLOUD
This section contains public cloud management and orchestration messages.
Add proxy
Keyword |
ADD_PROXY_OP |
Message text |
Added proxy, request: $1 |
Variable fields |
$1: Message body of the request for adding a proxy entry. |
Example |
Added proxy, request: { "proxy": { "id": "57fe85e4-ca2f-4192-b3cd-d5c249d7a211", "enable_proxy": true, "proxy_address": "proxy.sdn.com", "port": 8080, "user_name": "admin", "password": "******" } }} |
Explanation |
An HTTP proxy entry was added. |
Possible failure causes |
· Internal error. · Invalid JSON format. · The specified proxy configuration already exists. · Invalid UUID. · The UUID already exists. |
Update proxy
Keyword |
UPDATE_PROXY_OP |
Message text |
Updated proxy "$1", request: $2 |
Variable fields |
$1: ID of the proxy entry. $2: Message body of the request for editing the proxy entry. |
Example |
Updated proxy " 46585c3a-8ba8-4dbf-8db4-e7205652e674", request: { "id": "46585c3a-8ba8-4dbf-8db4-e7205652e674", "port": 8080, "password": "*********", "enable_proxy": false, "proxy_address": "proxy.sdn.com", "user_name": "z20291" } |
Explanation |
An HTTP proxy entry was edited. |
Possible failure causes |
· Internal error. · Invalid JSON format. · The specified resource does not exist. · The specified proxy configuration does not exist. |
Delete proxy
Keyword |
DEL_PROXY_OP |
Message text |
Deleted proxy $1 |
Variable fields |
$1: ID of the proxy entry. |
Example |
Deleted proxy edfed45a-d3a9-4bb0-bfe4-b5fe5c3c9027 |
Explanation |
An HTTP proxy entry was deleted. |
Possible failure causes |
· Internal error. · The specified resource does not exist. |
Add account
Keyword |
ADD_ACCOUNT_OP |
Message text |
Added account, request: $1 |
Variable fields |
$1: Message body of the request for adding an account. |
Example |
Added account "c3978f64-87a2-4129-9f9d-a8d0047da3b0", request: { "id": "c3978f64-87a2-4129-9f9d-a8d0047da3b0", "vendor": "AWS", "mode": "AK-SK", "description": "aws account", "username": "zjt@h3c.com", "region": ["eu-west-3"], "ak": "*********", "sk": "*********", "state": "normal", "account_id": "490509281347", "sync_state": null, "last_sync_time": null } |
Explanation |
An account was added. |
Possible failure causes |
· Internal error. · Invalid JSON format. · Invalid parameter. · Invalid public cloud type. · Invalid account ID. · Invalid authentication mode. · The account description cannot exceed 255 characters. · Invalid AK. · Invalid SK. · The selected regions must be within the account's region range. · The region list of the account cannot be empty. · Invalid UUID. · The UUID already exists. · A public cloud account already exists with the same account ID. · The public cloud is unreachable. |
Update account
Keyword |
UPDATE_ACCOUNT_OP |
Message text |
Updated account "$1", request: $2 |
Variable fields |
$1: Account ID. $2: Message body of the request for editing an account. |
Example |
Updated account "d29e08ee-a02b-4479-b3c4-bb2c520c7010", request: { "id": "d29e08ee-a02b-4479-b3c4-bb2c520c7010", "vendor": "AWS", "mode": "AK-SK", "description": "aws account", "username": "zjt@h3c.com", "region": ["eu-north-1"], "ak": "*********", "sk": "*********", "state": "normal", "account_id": "490509281347", "sync_state": "success", "last_sync_time": "2022-06-15 18:15:06" } |
Explanation |
An account was edited. |
Possible failure causes |
· Internal error. · Invalid JSON format. · Invalid parameter. · The specified public cloud account does not exist. · Invalid public cloud type. · Invalid account ID. · Invalid authentication mode. · The account description cannot exceed 255 characters. · Invalid AK. · Invalid SK. · The selected regions must be within the account's region range. · The region list of the account cannot be empty. · The public cloud is unreachable. |
Delete account
Keyword |
DEL_ACCOUNT_OP |
Message text |
Deleted account $1 |
Variable fields |
$1: Account ID. |
Example |
Deleted account edfed45a-d3a9-4bb0-bfe4-b5fe5c3c9027 |
Explanation |
An account was deleted. |
Possible failure causes |
· Internal error. · The specified public cloud account does not exist. · A VPC exists under this account. |
Check account
Keyword |
CHECK_ACCOUNT_OP |
Message text |
Checked account, request: $2 |
Variable fields |
$1: Message body of the request for checking an account. |
Example |
Checked account: { "account": { "vendor": "AWS", "mode": "AK-SK", "account_id": "497487339952 ", "username": "awsaccount", "ak": "AKIAXHVEOMGYGYJXOOV6", "sk": "GAYvKzQ9IdtTsGG+ajm2TpdFCr8I7/k4jOLEwa+L" }} |
Explanation |
The account capability was checked. |
Possible failure causes |
· Internal error. · Invalid JSON format. · Invalid parameter. · The specified public cloud account does not exist. · Invalid public cloud type. · Invalid account ID. · Invalid authentication mode. · Invalid AK. · Invalid SK. · Invalid username. · Failed to authenticate to the public cloud by using the AK/SK pair. · The selected regions must be within the account's region range. · The region list of the account cannot be empty. |
Add VPC
Keyword |
PUBLIC_CLOUD_RESOURCE |
Message text |
Executed public cloud resource $1 |
Variable fields |
$1: Message body of the request for adding a VPC. |
Example |
{ "action": "createVpc", "content": { "name": "VPC", "region": "eu-north-1", "description":"vpc111", "cidr_block": "10.0.0.0/24", "ipv6_cidr_source": "AWS", "account_id": "497487339952", "vendor": "AWS", "ipv6_cidr_block_network_border_group": "us-west-2-lax-1" } } |
Explanation |
A VPC was added. |
Possible failure causes |
· Internal error. · Invalid JSON format. · Invalid parameter. · Invalid public cloud type. · Invalid account ID. · Invalid authentication mode. · Invalid VPC name. · The VPC description cannot exceed 255 characters. · The value of region must be within the account's region range. · Invalid IPv6 CIDR source. · You must specify a network border group when an IPv6 CIDR source is specified. · Failed to authenticate to the public cloud by using the AK/SK pair. · The network border group must be within the region. · You can specify a network border group only when the IPv6 CIDR source is specified. · The specified public cloud account does not exist. · The selected regions must be within the account's region range. · Failed to request data from Amazon Web Services. · Invalid UUID. · The UUID already exists. · A VPC name must be 2 to 128 charactersin length and start with a letter or Chinese character. It can contain digits,underscores (_), and hyphens (-). |
Update VPC
Keyword |
UPDATE_VPC_OP |
Message text |
Executed public cloud resource $1 |
Variable fields |
$1: Message body of the request for editing a VPC. |
Example |
{ "action": "updateVpc", "content": { "name": "VPC", "region": "eu-north-1", "description":"vpc111", "cidr_block": "10.0.0.0/24", "ipv6_cidr_source": "AWS", "account_id": "497487339952", "vendor": "AWS", "ipv6_cidr_block_network_border_group": "us-west-2-lax-1" } } |
Explanation |
A VPC was edited. |
Possible failure causes |
· Internal error. · Invalid JSON format. · Invalid parameter. · Invalid public cloud type. · Invalid account ID. · Invalid authentication mode. · The specified public cloud account does not exist. · Invalid VPC name. · The VPC description cannot exceed 255 characters. · The value of region must be within the account's region range. · Invalid IPv6 CIDR source. · You must specify a network border group when an IPv6 CIDR source is specified. · Failed to authenticate to the public cloud by using the AK/SK pair. · The network border group must be within the region. · You can specify a network border group only when the IPv6 CIDR source is specified. · The selected regions must be within the account's region range. · The account to which the public cloud resource belongs is synchronizing data. Please try later. · A VPC name must be 2 to 128 charactersin length and start with a letter or Chinese character. It can contain digits,underscores (_), and hyphens (-). |
Delete VPC
Keyword |
PUBLIC_CLOUD_RESOURCE |
Message text |
Executed public cloud resource $1 |
Variable fields |
$1: VPC information. |
Example |
{ "action": "deleteVpc", "content": { "name": "VPC", "region": "eu-north-1", "description":"vpc111", "cidr_block": "10.0.0.0/24", "ipv6_cidr_source": "AWS", "account_id": "497487339952", "vendor": "AWS", "ipv6_cidr_block_network_border_group": "us-west-2-lax-1" } } |
Explanation |
A VPC was deleted. |
Possible failure causes |
· Internal error. · The specified VPC does not exist. · The specified public cloud account does not exist. · Please delete the gateway resources associated by the specified VPC first. · Please delete the vRouter resources associated by the specified VPC first. · The account to which the public cloud resource belongs is synchronizing data. Please try later. |
Add VPC CIDR
Keyword |
PUBLIC_CLOUD_RESOURCE |
Message text |
Executed public cloud resource $1 |
Variable fields |
$1: Message body of the request for adding a VPC CIDR. |
Example |
{ "action": "createVpcCidr", "content": { "protocolType":"v4", "cidr": { "vpc_id": "57fe85e4-ca2f-4192-b3cd-d5c249d7a21f", "cidr_block": "10.0.0.0/24" } } } or { "action": "createVpcCidr", "content": { "protocolType":"v6", "cidr": { " vpc_id ": "57fe85e4-ca2f-4192-b3cd-d5c249d7a21f", "ipv6_cidr_block_network_border_group": "us-west-2-lax-1", "ipv6_cidr_source": "AWS" } } } |
Explanation |
A VPC CIDR was added. |
Possible failure causes |
· Internal error. · Invalid JSON format. · Invalid parameter. · Invalid public cloud type. · Invalid VPC name. · Invalid IP protocol type. · Invalid IPv4 cidr parameter. · Invalid IPv6 cidr parameter. · The specified VPC does not exist. · Invalid UUID. · The UUID already exists. |
Delete VPC CIDR
Keyword |
PUBLIC_CLOUD_RESOURCE |
Message text |
Executed public cloud resource $1 |
Variable fields |
$1: VPC CIDR information. |
Example |
{ "action": "deleteVpcCidr", "content": { "association_id": "vpc-cidr-assoc-e2a5408b" } } |
Explanation |
A VPC CIDR was deleted. |
Possible failure causes |
· Internal error. · The specified VPC does not exist. · The specified public cloud account does not exist. · The account to which the public cloud resource belongs is synchronizing data. Please try later. |
Add egress gateway
Keyword |
PUBLIC_CLOUD_RESOURCE |
Message text |
Executed public cloud resource $1 |
Variable fields |
$1: Message body of the request for adding a border gateway. |
Example |
{ "action": "CreateExportGateway", "content": { "vpc_id": "57fe85e4-ca2f-4192-b3cd-d5c249d7a21f", "name": "vpc", "description": "gateway--test", "resource_type": "InternetGateway" } } |
Explanation |
A border gateway was added. |
Possible failure causes |
· Internal error. · Invalid JSON format. · Invalid parameter. · The egress gateway description cannot exceed 255 characters. · The egress gateway name cannot exceed 256 characters. · Invalid egress gateway resource type. · Failed to create the egress gateway on the public cloud. · The specified VPC does not exist. · Failed to attach an Internet gateway to the public cloud. · Invalid UUID. · The UUID already exists. |
Update egress gateway
Keyword |
PUBLIC_CLOUD_RESOURCE |
Message text |
Executed public cloud resource $1 |
Variable fields |
$1: Message body of the request for editing a border gateway. |
Example |
{ "action": "UpdateExportGateway", "content": { "id": "57fe85e4-ca2f-4192-b3cd-d5c249d7a21f", "name": "gateway", "description": "gateway—test-modify" } } |
Explanation |
A border gateway was edited. |
Possible failure causes |
· Internal error. · Invalid JSON format. · Invalid parameter. · The egress gateway description cannot exceed 255 characters. · The egress gateway name cannot exceed 256 characters. · Failed to edit the egress gateway on the public cloud. · The specified VPC does not exist. · The specified egress gateway does not exist. · The account to which the public cloud resource belongs is synchronizing data. Please try later. |
Delete egress gateway
Keyword |
PUBLIC_CLOUD_RESOURCE |
Message text |
Executed public cloud resource $1 |
Variable fields |
$1: Message body of the request for deleting a border gateway. |
Example |
{ "action": "DeleteExportGateway", "content": { "id": "57fe85e4-ca2f-4192-b3cd-d5c249d7a21f" } } |
Explanation |
A border gateway was deleted. |
Possible failure causes |
· Internal error. · Invalid JSON format. · Invalid parameter. · The specified egress gateway does not exist. · Failed to detach an Internet gateway from the public cloud. · Please delete the resources associated by the specified gateway first. · Failed to delete the egress gateway from the public cloud. |
Add vRouter
Keyword |
PUBLIC_CLOUD_RESOURCE |
Message text |
Executed public cloud resource $1 |
Variable fields |
$1: Message body of the request for adding a vRouter. |
Example |
{ "action": "CreateVRouter", "content": { "name": "vroute", "description":"vroute", "vpc_id": "57fe85e4-ca2f-4192-b3cd-d5c249d7a211" } } |
Explanation |
A vRouter was added. |
Possible failure causes |
· Internal error. · Invalid JSON format. · Invalid parameter. · The vRouter name cannot exceed 256 characters. · The vRouter description cannot exceed 255 characters. · Failed to create the vRouter on the public cloud. · The specified VPC does not exist. · Invalid UUID. · The UUID already exists. · A vRouter name must be 2 to 128 charactersin length and start with a letter or Chinese character. It can contain digits,underscores (_), and hyphens (-). |
Update vRouter
Keyword |
PUBLIC_CLOUD_RESOURCE |
Message text |
Executed public cloud resource $1 |
Variable fields |
$1: Message body of the request for editing a vRouter. |
Example |
{ "action": "UpdateVRouter", "content": { "id": "57fe85e4-ca2f-4192-b3cd-d5c249d7a21f", "name": "vrouter", "description":"router-modify" } } |
Explanation |
A vRouter was edited. |
Possible failure causes |
· Internal error. · Invalid JSON format. · Invalid parameter. · The vRouter name cannot exceed 256 characters. · The vRouter description cannot exceed 255 characters. · Failed to edit the vRouter on the public cloud. · The specified VPC does not exist. · The account to which the public cloud resource belongs is synchronizing data. Please try later. · A vRouter name must be 2 to 128 charactersin length and start with a letter or Chinese character. It can contain digits,underscores (_), and hyphens (-). |
Delete vRouter
Keyword |
PUBLIC_CLOUD_RESOURCE |
Message text |
Executed public cloud resource $1 |
Variable fields |
$1: Message body of the request for deleting a vRouter. |
Example |
{ "action": "DeleteVRouter", "content": { "id": "57fe85e4-ca2f-4192-b3cd-d5c249d7a21f" } } |
Explanation |
A vRouter was deleted. |
Possible failure causes |
· Internal error. · Invalid JSON format. · Invalid parameter. · The specified vRouter does not exist. · Failed to delete the vRouter from the public cloud. · The account to which the public cloud resource belongs is synchronizing data. Please try later. |
Add route entry
Keyword |
PUBLIC_CLOUD_RESOURCE |
Message text |
Executed public cloud resource $1 |
Variable fields |
$1: Message body of the request for adding a route entry. |
Example |
{ "action": "CreateRouteItem", "content": { "vrouter_id": "67fe85e4-ca2f-4192-b3cd-d5c249d7a211", "destination_cidr_block": "10.0.0.0/24", "destination_ipv6_cidr_block": "", "next_hop_type": "ExportGateway", "next_hop_id": "57fe85e4-ca2f-4192-b3cd-d5c249d7a211" } } |
Explanation |
A route entry was added. |
Possible failure causes |
· Internal error. · Invalid JSON format. · Invalid parameter. · Invalid next hop type. · The request must contain exactly one of destination CIDR Block,destination IPv6 CIDR Block. · Invalid destination IPv4 CIDR Block. · Invalid destination IPv6 CIDR Block. · The specified router item already exists. · Failed to create a router item on the public cloud. · Cannot create IPv4 CIDR Block for an Egress Only Internet Gateway for an IPv4 route. · The specified egress gateway does not exist. · Invalid UUID. · The UUID already exists. |
Delete route entry
Keyword |
PUBLIC_CLOUD_RESOURCE |
Message text |
Executed public cloud resource $1 |
Variable fields |
$1: Message body of the request for deleting a route entry. |
Example |
{ "action": "DeleteRouteItem", "content": { "id": "57fe85e4-ca2f-4192-b3cd-d5c249d7a21f" } } |
Explanation |
A route entry was deleted. |
Possible failure causes |
· Internal error. · Invalid JSON format. · Invalid parameter. · The local main route item cannot be deleted. · The specified router item does not exist. · Failed to delete a router item on the public cloud. · The account to which the public cloud resource belongs is synchronizing data. Please try later. |
Add subnet
Keyword |
PUBLIC_CLOUD_RESOURCE |
Message text |
Executed public cloud resource $1 |
Variable fields |
$1: Message body of the request for adding a subnet. |
Example |
{ "action": "CreateSubnet", "content": { "vpc_id": "57fe85e4-ca2f-4192-b3cd-d5c249d7a21f", "name": "subnet1", "description": "subnet", "availability_zone_id": "use1-az4", "cidr_block": "22.22.22.0/24", "ipv6_cidr_block": "2600:1f16:42b:8210::/64", "vrouter_id": "97fe85e4-ca2f-4192-b3cd-d5c249d7a21f" } } |
Explanation |
A subnet was added. |
Possible failure causes |
· Internal error. · Invalid JSON format. · Invalid parameter. · The specified VPC does not exist. · The subnet description cannot exceed 255 characters. · The subnet name cannot exceed 256 characters. · Failed to create a subnet on the public cloud. · Failed to associate the subnet on the public cloud with the vRouter. · The availability zone specified by the subnet must be within the availability zone of the VPC. · The IPv4 CIDR must be within the IPv4 CIDR range of the specified VPC. · The IPv4 CIDR has been specified for a subnet. · The IPv6 CIDR has been specified for a subnet. · The IPv4 CIDR of this subnet conflicts with the IPv4 CIDR of another subnet in the same VPC. · The IPv6 CIDR of this subnet conflicts with the IPv6 CIDR of another subnet in the same VPC. · The mask length of an IPv4 CIDR must be between 16 and 28. · The prefix length of an IPv6 CIDR must be 64. · Invalid IPv6 CIDR. · Invalid IPv4 CIDR. · The IPv6 CIDR must be within the IPv6 CIDR range of the specified VPC. · The specified network ACL does not exist. · Invalid UUID. · The UUID already exists. · A subnet name must be 2 to 128 charactersin length and start with a letter or Chinese character. It can contain digits,underscores (_), and hyphens (-). |
Update subnet
Keyword |
PUBLIC_CLOUD_RESOURCE |
Message text |
Executed public cloud resource $1 |
Variable fields |
$1: Message body of the request for editing a subnet. |
Example |
{ "action": "UpdateSubnet", "content": { "id": "57fe85e4-ca2f-4192-b3cd-d5c249d7a21f", "name": "subnet1", "description": "subnet1", "ipv6_cidr_block": "2600:1f16:42b:8210::/64", "vrouter_id": "97fe85e4-ca2f-4192-b3cd-d5c249d7a21f" } } |
Explanation |
A subnet was edited. |
Possible failure causes |
· Internal error. · Invalid JSON format. · Invalid parameter. · The specified VPC does not exist. · The subnet description cannot exceed 255 characters. · The subnet name cannot exceed 256 characters. · Failed to update the subnet on the public cloud. · Failed to associate the subnet on the public cloud with the vRouter. · The IPv6 CIDR has been specified for a subnet. · The IPv6 CIDR of this subnet conflicts with the IPv6 CIDR of another subnet in the same VPC. · The prefix length of an IPv6 CIDR must be 64. · Invalid IPv6 CIDR. · The IPv6 CIDR must be within the IPv6 CIDR range of the specified VPC. · The specified network ACL does not exist. · The account to which the public cloud resource belongs is synchronizing data. Please try later. · A subnet name must be 2 to 128 charactersin length and start with a letter or Chinese character. It can contain digits,underscores (_), and hyphens (-). |
Delete subnet
Keyword |
PUBLIC_CLOUD_RESOURCE |
Message text |
Executed public cloud resource $1 |
Variable fields |
$1: Message body of the request for deleting a subnet. |
Example |
{ "action": "DeleteSubnet", "content": { "id": "57fe85e4-ca2f-4192-b3cd-d5c249d7a21f" } } |
Explanation |
A subnet was deleted. |
Possible failure causes |
· Internal error. · Invalid JSON format. · Invalid parameter. · Failed to delete the subnet from the public cloud. · You cannot delete the VPC, because vSubnets exist on the VPC. · The vRouter is already associated with the subnet. · The specified subnet does not exist. · The account to which the public cloud resource belongs is synchronizing data. Please try later. |
Add network ACL
Keyword |
PUBLIC_CLOUD_RESOURCE |
Message text |
Executed public cloud resource $1 |
Variable fields |
$1: Message body of the request for adding a network ACL. |
Example |
{ "action": "CreateNetworkAcl", "content": { "name": "acl", "description":"acl", "vpc_id": "57fe85e4-ca2f-4192-b3cd-d5c249d7a211" } } |
Explanation |
A network ACL was added. |
Possible failure causes |
· Internal error. · Invalid JSON format. · Invalid parameter. · The specified VPC does not exist. · The network ACL name cannot exceed 256 characters. · The network ACL description cannot exceed 255 characters. · The specified network ACL already exists. · Failed to create the network ACL on the public cloud. · Invalid UUID. · The UUID already exists. |
Update network ACL
Keyword |
PUBLIC_CLOUD_RESOURCE |
Message text |
Executed public cloud resource $1 |
Variable fields |
$1: Message body of the request for editing a network ACL. |
Example |
{ "action": "UpdateNetworkAcl", "content": { "id": "57fe85e4-ca2f-4192-b3cd-d5c249d7a211", "name": "acl", "description":"acl" } } |
Explanation |
A network ACL was edited. |
Possible failure causes |
· Internal error. · Invalid JSON format. · Invalid parameter. · The network ACL name cannot exceed 256 characters. · The network ACL description cannot exceed 255 characters. · The specified network ACL does not exist. · Failed to update the network ACL on the public cloud. · The account to which the public cloud resource belongs is synchronizing data. Please try later. |
Delete network ACL
Keyword |
PUBLIC_CLOUD_RESOURCE |
Message text |
Executed public cloud resource $1 |
Variable fields |
$1: Message body of the request for deleting a network ACL. |
Example |
{ "action": "DeleteNetworkAcl", "content": { "id": "57fe85e4-ca2f-4192-b3cd-d5c249d7a21f" } } |
Explanation |
A network ACL was deleted. |
Possible failure causes |
· Internal error. · Invalid JSON format. · Invalid parameter. · The specified network ACL does not exist. · The default network ACL cannot be deleted. · The network ACL has been associated with a subnet and cannot be deleted. · Failed to delete the network ACL from the public cloud. · The account to which the public cloud resource belongs is synchronizing data. Please try later. |
Add ACL rule
Keyword |
PUBLIC_CLOUD_RESOURCE |
Message text |
Executed public cloud resource $1 |
Variable fields |
$1: Message body of the request for adding an ACL rule. |
Example |
{ "action": "CreateAclEntryRule", "content": { "id": "36e6c86b-3efa-44c5-bde4-b179942489c6", "network_acl_id": "9b0019d9-9011-412b-b941-e2d6bfeb2cc8", "egress": true, "rule_num": 17, "protocol": 6, "icmp_type": null, "icmp_code": null, "port_range_from": 1, "port_range_to": 65535, "cidr_block": null, "ipv6_cidr_block": "2a05:d016:3bb:ab00::/56", "rule_action": "allow" } } |
Explanation |
An ACL rule was added. |
Possible failure causes |
· Internal error. · Invalid JSON format. · Invalid parameter. · The specified network ACL does not exist. · Please specify the rule as an outbound or inbound rule. · Only rules with a protocol number of –1, 1, 6, 17, or 58 can be created. · The ICMP type and ICMP code are required if the protocol number is 1 (ICMP) or 58 (ICMPv6). · The rule number must be an integer in the range of 1 to 32766. · The start port must be an integer in the range of 1 to 65535. · The end port must be an integer in the range of 1 to 65535. · The start port must be smaller than or equal to the end port. · The rule action can only be Allow or Deny. · The specified network ACL rule already exists. · Invalid IPv4 CIDR. · Invalid IPv6 CIDR. · You must configure the source address for an inbound rule and make sure the source address is an IPv4 or IPv6 CIDR. · You must configure the source address for an outbound rule and make sure the source address is an IPv4 or IPv6 CIDR. · Failed to create the network ACL rule on the public cloud. · Invalid UUID. · The UUID already exists. |
Delete ACL rule
Keyword |
PUBLIC_CLOUD_RESOURCE |
Message text |
Executed public cloud resource $1 |
Variable fields |
$1: Message body of the request for deleting an ACL rule. |
Example |
{ "action": "DeleteAclEntryRule", "content": { "id": "57fe85e4-ca2f-4192-b3cd-d5c249d7a21f" } } |
Explanation |
An ACL rule was deleted. |
Possible failure causes |
· Internal error. · Invalid JSON format. · Invalid parameter. · The specified network ACL rule does not exist. · The default inbound rule and outbound rule cannot be deleted. · Failed to create the network ACL rule on the public cloud. · The account to which the public cloud resource belongs is synchronizing data. Please try later. |
Add security group
Keyword |
PUBLIC_CLOUD_RESOURCE |
Message text |
Executed public cloud resource $1 |
Variable fields |
$1: Message body of the request for adding a security group. |
Example |
{ "action": "CreateSecurityGroup", "content": { "name": "securityGroup", "description":"securityGroup", "vpc_id": "57fe85e4-ca2f-4192-b3cd-d5c249d7a211" } } |
Explanation |
A security group was added. |
Possible failure causes |
· Internal error. · Invalid JSON format. · Invalid parameter. · Invalid UUID. · The UUID already exists. |
Delete security group
Keyword |
PUBLIC_CLOUD_RESOURCE |
Message text |
Executed public cloud resource $1 |
Variable fields |
$1: Message body of the request for deleting a security group. |
Example |
{ "action": "DeleteSecurityGroup", "content": { "id": "57fe85e4-ca2f-4192-b3cd-d5c249d7a21f" } } |
Explanation |
A security group was deleted. |
Possible failure causes |
· Internal error. · Invalid JSON format. · Invalid parameter. · The account to which the public cloud resource belongs is synchronizing data. Please try later. |
Add security group rule
Keyword |
PUBLIC_CLOUD_RESOURCE |
Message text |
Executed public cloud resource $1 |
Variable fields |
$1: Message body of the request for adding a security group rule. |
Example |
{ "action": "CreateSecurityGroupEntryRule", "content": { "security_group_id": "9b0019d9-9011-412b-b941-e2d6bfeb2cc8", "egress": true, "name": "SG-0", "description": "SG-0", "protocol": "icmp", "icmp_type": 3, "icmp_code": 1, "port_range_from": null, "port_range_to": null, "cidr_block": null, "ipv6_cidr_block": null, "reference_group_id": "97fe85e4-ca2f-4192-b3cd-d5c249d7a21f" } } |
Explanation |
A security group rule was added. |
Possible failure causes |
· Internal error. · Invalid JSON format. · Invalid parameter. · Invalid UUID. · The UUID already exists. |
Delete security group rule
Keyword |
PUBLIC_CLOUD_RESOURCE |
Message text |
Executed public cloud resource $1 |
Variable fields |
$1: Message body of the request for deleting a security group rule. |
Example |
{ "action": "DeleteSecurityGroupEntryRule", "content": { "id": "57fe85e4-ca2f-4192-b3cd-d5c249d7a21f" } } |
Explanation |
A security group rule was deleted. |
Possible failure causes |
· Internal error. · Invalid JSON format. · Invalid parameter. · The account to which the public cloud resource belongs is synchronizing data. Please try later. |
Add endpoint
Keyword |
PUBLIC_CLOUD_RESOURCE |
Message text |
Executed public cloud resource $1 |
Variable fields |
$1: Message body of the request for adding an endpoint node. |
Example |
{ "action": "CreateEndPoint", "content": { "vpc_id": "57fe85e4-ca2f-4192-b3cd-d5c249d7a21f", "name": "endpoint1", "description": "endpoint1", "service_category": "aws", "service_name": "com.amazonaws.eu-west-3.airflow.api", "subnet_associate": [ "56fe85e4-ca2f-4192-b3cd-d5c249d7a21f", "98fe85e4-ca2f-4192-b3cd-d5c249d7a21f" ], "security_group_associate": [ "97fe85e4-ca2f-4192-b3cd-d5c249d7a21f", "65fe85e4-ca2f-4192-b3cd-d5c249d7a21f" ] } } |
Explanation |
An endpoint node was added. |
Possible failure causes |
· Internal error. · Invalid JSON format. · Invalid parameter. · Invalid UUID. · The UUID already exists. |
Update endpoint
Keyword |
PUBLIC_CLOUD_RESOURCE |
Message text |
Executed public cloud resource $1 |
Variable fields |
$1: Message body of the request for editing an endpoint node. |
Example |
{ "action": "UpdateEndPoint", "content": { "id": "57fe85e4-ca2f-4192-b3cd-d5c249d7a21f", "name": "endpoint1", "description": "endpoint1", "subnet_associate": [ "56fe85e4-ca2f-4192-b3cd-d5c249d7a21f", "98fe85e4-ca2f-4192-b3cd-d5c249d7a21f" ], "security_group_associate": [ "97fe85e4-ca2f-4192-b3cd-d5c249d7a21f", "65fe85e4-ca2f-4192-b3cd-d5c249d7a21f" ] } } |
Explanation |
An endpoint node was edited. |
Possible failure causes |
· Internal error. · Invalid JSON format. · Invalid parameter. · The account to which the public cloud resource belongs is synchronizing data. Please try later. |
Delete endpoint
Keyword |
PUBLIC_CLOUD_RESOURCE |
Message text |
Executed public cloud resource $1 |
Variable fields |
$1: Message body of the request for deleting an endpoint node. |
Example |
{ "action": "DeleteEndPoint", "content": { "id": "57fe85e4-ca2f-4192-b3cd-d5c249d7a21f" } } |
Explanation |
An endpoint node was deleted. |
Possible failure causes |
· Internal error. · Invalid JSON format. · Invalid parameter. · The account to which the public cloud resource belongs is synchronizing data. Please try later. |
Sync public cloud resources
Keyword |
PUBLIC_CLOUD_RESOURCE |
Message text |
Executed public cloud resource $1 |
Variable fields |
$1: Message body of the request for synchronizing public cloud resources. |
Example |
Executed public cloud resource "{" action ":" SyncCloudResources "," content ":{" account_id ":" d29e08ee - a02b - 4479 - b3c4 - bb2c520c7010 "}}" |
Explanation |
Public cloud resources were synchronized. |
Possible failure causes |
· Internal error. · The specified public cloud account does not exist. · The specified account is synchronizing data. Please try later. |
Add transit gateway
Keyword |
PUBLIC_CLOUD_RESOURCE |
Message text |
Executed public cloud resource $1 |
Variable fields |
$1: Message body of the request for adding a transit gateway. |
Example |
{ "action": "CreateTransitGateway", "content": { "id": "97fe85e4-ca2f-4192-b3cd-d5c249d7a21f", "name": "TransitGateway1", "description": "TransitGateway1", "account_id": "57fe85e4-ca2f-4192-b3cd-d5c249d7a211", "vendor": "AWS", "region": "eu-north-1", "as": 64512 } } |
Explanation |
A transit gateway was added. |
Possible failure causes |
· Internal error. · Invalid JSON format. · Invalid parameter. · Invalid UUID. · The UUID already exists. · The name of a transit gateway cannot exceed 256 characters. · The description of a transit gateway cannot exceed 255 characters. Only letters, digits, spaces,and special characters(!._-:/()#,@[]+=&;{}$*) are supported. · Invalid AS number. The AS number range is 64512 to 65534 or 4200000000 to 4294967294. · Failed to create a transit gateway on the public cloud. |
Update transit gateway
Keyword |
PUBLIC_CLOUD_RESOURCE |
Message text |
Executed public cloud resource $1 |
Variable fields |
$1: Message body of the request for editing a transit gateway. |
Example |
{ "action": "UpdateTransitGateway", "content": { "id": "57fe85e4-ca2f-4192-b3cd-d5c249d7a21f", "name": "TGW1", "description": "TGW1" } } |
Explanation |
A transit gateway was edited. |
Possible failure causes |
· Internal error. · Invalid JSON format. · Invalid parameter. · The name of a transit gateway cannot exceed 256 characters. · The description of a transit gateway cannot exceed 255 characters. Only letters, digits, spaces,and special characters(!._-:/()#,@[]+=&;{}$*) are supported. · The specified transit gateway does not exist. · Failed to update a transit gateway on the public cloud. |
Delete transit gateway
Keyword |
PUBLIC_CLOUD_RESOURCE |
Message text |
Executed public cloud resource $1 |
Variable fields |
$1: Message body of the request for deleting a transit gateway. |
Example |
{ "action": "DeleteTransitGateway", "content": { "id": "57fe85e4-ca2f-4192-b3cd-d5c249d7a21f" } } |
Explanation |
A transit gateway was deleted. |
Possible failure causes |
· Internal error. · Invalid JSON format. · Invalid parameter. · The specified transit gateway does not exist. · Failed to delete a transit gateway from the public cloud. · You cannot delete the transit gateway, because it has transit router bindings. |
Add transit router
Keyword |
PUBLIC_CLOUD_RESOURCE |
Message text |
Executed public cloud resource $1 |
Variable fields |
$1: Message body of the request for adding a transit router. |
Example |
{ "action": "CreateTransitRouter", "content": { "transit_gateway_id": "97fe85e4-ca2f-4192-b3cd-d5c249d7a21f", "name": "TR1", "description": "TR1" } } |
Explanation |
A transit router was added. |
Possible failure causes |
· Internal error. · Invalid JSON format. · Invalid parameter. · Invalid UUID. · The UUID already exists. · The name of a transit router cannot exceed 256 characters. · The description of a transit router cannot exceed 255 characters. · Failed to create a transit router on the public cloud. |
Update transit router
Keyword |
PUBLIC_CLOUD_RESOURCE |
Message text |
Executed public cloud resource $1 |
Variable fields |
$1: Message body of the request for editing a transit router. |
Example |
{ "action": "UpdateTransitRouter", "content": { "id": "57fe85e4-ca2f-4192-b3cd-d5c249d7a21f", "name": "TR1", "description": "TR1" } } |
Explanation |
A transit router was edited. |
Possible failure causes |
· Internal error. · Invalid JSON format. · Invalid parameter. · The name of a transit router cannot exceed 256 characters. · The description of a transit router cannot exceed 255 characters. · Failed to update a transit router on the public cloud. · The specified transit router does not exist. |
Delete transit router
Keyword |
PUBLIC_CLOUD_RESOURCE |
Message text |
Executed public cloud resource $1 |
Variable fields |
$1: Message body of the request for deleting a transit router. |
Example |
{ "action": "DeleteTransitRouter", "content": { "id": "57fe85e4-ca2f-4192-b3cd-d5c249d7a21f" } } |
Explanation |
A transit router was deleted. |
Possible failure causes |
· Internal error. · Invalid JSON format. · Invalid parameter. · Failed to delete a transit router from the public cloud. · The specified transit router does not exist. |
Add transit route entry
Keyword |
PUBLIC_CLOUD_RESOURCE |
Message text |
Executed public cloud resource $1 |
Variable fields |
$1: Message body of the request for adding a transit route entry. |
Example |
{ "action": "CreateTransitRouteItem", "content": { "id":"77fe85e4-ca2f-4192-b3cd-d5c249d7a211", "transit_router_id": "67fe85e4-ca2f-4192-b3cd-d5c249d7a211", "destination_cidr_block": "10.0.0.0/24", "destination_ipv6_cidr_block": "", "transit_gateway_peering_id": "57fe85e4-ca2f-4192-b3cd-d5c249d7a211" } } |
Explanation |
A transit route entry was added. |
Possible failure causes |
· Internal error. · Invalid JSON format. · Invalid parameter. · Invalid UUID. · The UUID already exists. |
Delete transit route entry
Keyword |
PUBLIC_CLOUD_RESOURCE |
Message text |
Executed public cloud resource $1 |
Variable fields |
$1: Message body of the request for deleting a transit route entry. |
Example |
{ "action": "DeleteTransitRouteItem", "content": { "id": "57fe85e4-ca2f-4192-b3cd-d5c249d7a21f" } } |
Explanation |
A transit route entry was deleted. |
Possible failure causes |
· Internal error. · Invalid JSON format. · Invalid parameter. |
Add transit gateway peering
Keyword |
PUBLIC_CLOUD_RESOURCE |
Message text |
Executed public cloud resource $1 |
Variable fields |
$1: Message body of the request for adding a transit gateway peering. |
Example |
{ "action": "CreateTransitGatewayPeering", "content": { "id": "97fe85e4-ca2f-4192-b3cd-d5c249d7a21f", "name": "TransitGatewayPeering1", "description": "TransitGatewayPeering1", "vendor": "AWS", "local_account_id": "57fe85e4-ca2f-4192-b3cd-d5c249d7a211", "local_region": "eu-north-1", "local_transit_gateway_id": "57fe85e4-ca2f-4192-b3cd-d5c249d7a211", "peer_account_id": "57fe85e4-ca2f-4192-b3cd-d5c249d7a211", "peer_region": "eu-north-1", "peer_transit_gateway_id": "57fe85e4-ca2f-4192-b3cd-d5c249d7a211" } } |
Explanation |
A transit gateway peering was added. |
Possible failure causes |
· Internal error. · Invalid JSON format. · Invalid parameter. · Invalid UUID. · The UUID already exists. · The name of a transit gateway peering cannot exceed 256 characters. · The description of a transit gateway peering cannot exceed 255 characters. · Failed to create a transit gateway peering on the public cloud. · Failed to query transit gateway peering from the public cloud. · The specified local public cloud account does not exist. · The specified remote public cloud account does not exist. · The specified local region must be within the local account's region range. · The specified remote region must be within the remote account's region range. · The name of a transit gateway cannot exceed 256 characters. · The specified local transit gateway does not exist. · The specified remote transit gateway does not exist. · The remote transit gateway cannot be the same as the local transit gateway. · The local transit gateway already has a peering attachment to the remote transit gateway. |
Update transit gateway peering
Keyword |
PUBLIC_CLOUD_RESOURCE |
Message text |
Executed public cloud resource $1 |
Variable fields |
$1: Message body of the request for editing a transit gateway peering. |
Example |
{ "action": "UpdateTransitGatewayPeering", "content": { "id": "57fe85e4-ca2f-4192-b3cd-d5c249d7a21f", "name": "TGWP1", "description": "TGWP1" } } |
Explanation |
A transit gateway peering was edited. |
Possible failure causes |
· Internal error. · Invalid JSON format. · Invalid parameter. · The specified transit gateway peering does not exist. · The name of a transit gateway peering cannot exceed 256 characters. · The description of a transit gateway peering cannot exceed 255 characters. · Failed to update a transit gateway peering on the public cloud. |
Delete transit gateway peering
Keyword |
PUBLIC_CLOUD_RESOURCE |
Message text |
Executed public cloud resource $1 |
Variable fields |
$1: Message body of the request for deleting a transit gateway peering. |
Example |
{ "action": "DeleteTransitGatewayPeering", "content": { "id": "57fe85e4-ca2f-4192-b3cd-d5c249d7a21f" } } |
Explanation |
A transit gateway peering was deleted. |
Possible failure causes |
· Internal error. · Invalid JSON format. · Invalid parameter. · The specified transit gateway peering does not exist. · Failed to delete a transit gateway peering from the public cloud. |
Add vRouter access
Keyword |
PUBLIC_CLOUD_RESOURCE |
Message text |
Executed public cloud resource $1 |
Variable fields |
$1: Message body of the request for adding a vRouter access. |
Example |
{ "action": "CreateVRouterAccess", "content": { "id": "97fe85e4-ca2f-4192-b3cd-d5c249d7a214", "name":"vrouter access", "vpc_id": "47fe85e4-ca2f-4192-b3cd-d5c249d7a21f", "vrouter_id": "91fe85e4-ca2f-4192-b3cd-d5c249d7a21f", "transit_router_id": "93fe85e4-ca2f-4192-b3cd-d5c249d7a21f", "subnets": [ "93fe85e4-ca2f-4192-b3cd-d5c249d7a214", "93fe85e4-ca2f-4192-b3cd-d5c249d7a215" ], "destination_cidrs": [ "10.0.0.0/24", "20.0.0.0/24" ], "destination_ipv6_cidrs": [
] } } |
Explanation |
A vRouter access was added. |
Possible failure causes |
· Internal error. · Invalid JSON format. · Invalid parameter. · Invalid UUID. · The UUID already exists. · The specified transit router does not exist. · The specified vRouter does not exist. · The subnet list cannot be empty. · The specified transit gateway does not exist. · Failed to create a VPC transit gateway attachment on the public cloud. · Failed to associate a transit router with the public cloud. · Failed to propagate a transit router to the public cloud. · A vRouter access already exists with the same VPC, transit gateway, and vRouter. · Failed to obtain information about VPC transit gateway attachments from the public cloud. · The specified subnet does not belong to the specified VPC. · The specified vRouter does not belong to the specified VPC. · The specified subnets must belong to different availability zones. · The specified subnet is not bound to the vRouter specified for the vRouter access. · The vRouter access name cannot exceed 255 characters. · A vRouter access with the same name already exists. · You cannot specify the same availability zone for two vRouter accesses when they meet the following requirements: 1. They have the same VPC binding. 2. The transit routers specified for them run on the same transit gateway. · The transit gateway to which the specified transit router belongs must be in the specified transit gateway peering attachment. · The specified transit router and the specified VPC must belong to the same region. · The vRouter access name cannot exceed 255 characters. · Please specify a name for the vRouter access. · A VPC-TGW attachment can only be associated with one transit router. |
Update vRouter access
Keyword |
PUBLIC_CLOUD_RESOURCE |
Message text |
Executed public cloud resource $1 |
Variable fields |
$1: Message body of the request for editing a vRouter access. |
Example |
{ "action": "UpdateVRouterAccess", "content": { "id": "97fe85e4-ca2f-4192-b3cd-d5c249d7a214", "subnets": [ "93fe85e4-ca2f-4192-b3cd-d5c249d7a214", "93fe85e4-ca2f-4192-b3cd-d5c249d7a215" ], "destination_cidrs": [ "10.0.0.0/24", "20.0.0.0/24" ] } } |
Explanation |
A vRouter access was edited. |
Possible failure causes |
· Internal error. · Invalid JSON format. · Invalid parameter. · The specified vRouter does not exist. · The subnet list cannot be empty. · The specified transit gateway does not exist. · Failed to update a VPC transit gateway attachment on the public cloud. · The specified subnet does not belong to the specified VPC. · The specified subnets must belong to different availability zones. · The specified subnet is not bound to the vRouter specified for the vRouter access. · The vRouter access name cannot exceed 255 characters. · A vRouter access with the same name already exists. · You cannot specify the same availability zone for two vRouter accesses when they meet the following requirements: 1. They have the same VPC binding. 2. The transit routers specified for them run on the same transit gateway. · The specified transit router item already exists. · The vRouter access name cannot exceed 255 characters. · Please specify a name for the vRouter access. |
Delete vRouter access
Keyword |
PUBLIC_CLOUD_RESOURCE |
Message text |
Executed public cloud resource $1 |
Variable fields |
$1: Message body of the request for deleting a vRouter access. |
Example |
{ "action": "DeleteVRouterAccess", "content": { "id": "57fe85e4-ca2f-4192-b3cd-d5c249d7a21f" } } |
Explanation |
A vRouter access was deleted. |
Possible failure causes |
· Internal error. · Invalid JSON format. · Invalid parameter. · Failed to delete a VPC transit gateway attachment from the public cloud. · Failed to disassociate a transit router from the public cloud. · Failed to disable propagate a transit router to the public cloud. · A vRouter access already exists with the same VPC, transit gateway, and vRouter. · The specified vRouter access does not exist. |
Add direct connect gateway
Keyword |
PUBLIC_CLOUD_RESOURCE |
Message text |
Executed public cloud resource $1 |
Variable fields |
$1: Direct connect gateway adding request. |
Example |
{ "action": "CreateDirectConnectGateway", "content": { "id": "97fe85e4-ca2f-4192-b3cd-d5c249d7a21f", "name": "dgw1", "as": 64512, "account_id": "57fe85e4-ca2f-4192-b3cd-d5c249d7a211" } } |
Explanation |
A direct connect gateway was added. |
Possible failure causes |
· Internal error. · Invalid JSON format. · Invalid parameter. · Invalid UUID. · The UUID already exists. · Please specify a direct connect gateway name. · The name of a direct connect gateway cannot exceed 100 characters. Only letters, digits, and hyphens (-) are supported. · The specified public cloud account does not exist. · The AS number must be an integer in the range of 64512 to 65534 or 4200000000 to 4294967294. · Failed to create the direct connect gateway on the public cloud. |
Update direct connect gateway
Keyword |
PUBLIC_CLOUD_RESOURCE |
Message text |
Executed public cloud resource $1 |
Variable fields |
$1: Direct connect gateway update request. |
Example |
{ "action": "UpdateDirectConnectGateway", "content": { "id": "57fe85e4-ca2f-4192-b3cd-d5c249d7a21f", "name": "dwg1" } } |
Explanation |
A direct connect gateway was updated. |
Possible failure causes |
· Internal error. · Invalid JSON format. · Invalid parameter. · Invalid UUID. · The UUID already exists. · Please specify a direct connect gateway name. · The name of a direct connect gateway cannot exceed 100 characters. Only letters, digits, and hyphens (-) are supported. · The specified direct connect gateway does not exist. · Failed to update the direct connect gateway on the public cloud. |
Delete direct connect gateway
Keyword |
PUBLIC_CLOUD_RESOURCE |
Message text |
Executed public cloud resource $1 |
Variable fields |
$1: Direct connect gateway deletion request. |
Example |
{ "action": "DeleteDirectConnectGateway", "content": { "id": "57fe85e4-ca2f-4192-b3cd-d5c249d7a21f" } } |
Explanation |
A direct connect gateway was deleted. |
Possible failure causes |
· Internal error. · Invalid JSON format. · Invalid parameter. · The id must be specified. · The specified direct connect gateway does not exist. · You cannot delete the direct connect gateway, because it has gateway associations. · Failed to delete the direct connect gateway on the public cloud. |
Add direct connect gateway association
Keyword |
PUBLIC_CLOUD_RESOURCE |
Message text |
Executed public cloud resource $1 |
Variable fields |
$1: Gateway association adding request. |
Example |
{ "action": "CreateDirectConnectGatewayAssociation", "content": { "id": "97fe85e4-ca2f-4192-b3cd-d5c249d7a21f", "name": "ass1", "direct_connect_gateway_id": "9caef4c6-1010-42c3-9527-289ceb29a456", "allowed_prefixes": [ "192.168.0.0/24", "192.161.0.0/24" ], associated_gateway: { gateway_id: "695a4331-7fc7-4b7c-bcb9-5d69c2c1e662" } } } |
Explanation |
A gateway association was added. |
Possible failure causes |
· Internal error. · Invalid JSON format. · Invalid parameter. · Invalid UUID. · The UUID already exists. · Please specify a gateway association name. · The name of a gateway association cannot exceed 256 characters and cannot contain only spaces. · The specified direct connect gateway does not exist. · The specified direct connect gateway is not available. · The specified transit gateway does not exist. · The specified transit gateway is not available. · A gateway association already exists with the specified transit gateway. · Please specify allowed prefixes for the gateway association. · Invalid prefixes for the gateway association. · You can specify up to 20 allowed prefixes for a gateway association. · The allowed prefixes of the gateway association cannot exist in any other gateway association. · Failed to create the gateway association on the public cloud. · The BGP AS number of the VPN gateway cannot be the same as that of the transit gateway. |
Update direct connect gateway association
Keyword |
PUBLIC_CLOUD_RESOURCE |
Message text |
Executed public cloud resource $1 |
Variable fields |
$1: Gateway association update request. |
Example |
{ "action": "UpdateDirectConnectGatewayAssociation", "content": { "id": "57fe85e4-ca2f-4192-b3cd-d5c249d7a21f", "allowed_prefixes": [ "192.165.0.0/24", "192.161.0.0/24" ] } } |
Explanation |
A gateway association was updated. |
Possible failure causes |
· Internal error. · Invalid JSON format. · Invalid parameter. · Please specify allowed prefixes for the gateway association. · Invalid prefixes for the gateway association. · You can specify up to 20 allowed prefixes for a gateway association. · The allowed prefixes of the gateway association cannot exist in any other gateway association. · The specified gateway association does not exist. · Failed to update the gateway association from the public cloud. · The BGP AS number of the VPN gateway cannot be the same as that of the transit gateway. |
Delete direct connect gateway association
Keyword |
PUBLIC_CLOUD_RESOURCE |
Message text |
Executed public cloud resource $1 |
Variable fields |
$1: Gateway association deletion request. |
Example |
{ "action": "DeleteDirectConnectGatewayAssociation", "content": { "id": "57fe85e4-ca2f-4192-b3cd-d5c249d7a21f" } } |
Explanation |
A gateway association was deleted. |
Possible failure causes |
· Internal error. · Invalid JSON format. · Invalid parameter. · The id must be specified. · The specified gateway association does not exist. · Failed to delete the gateway association from the public cloud. |
Add virtual interface
Keyword |
PUBLIC_CLOUD_RESOURCE |
Message text |
Executed public cloud resource $1 |
Variable fields |
$1: Virtual interface adding request. |
Example |
{ "action": "CreateVirtualInterface", "content": { "id": "97fe85e4-ca2f-4192-b3cd-d5c249d7a21f", "account_id": "57fe85e4-ca2f-4192-b3cd-d5c249d7a211", "name": "vt1", "description": "vt1", "type": "TRANSIT", "connection_id": "dxcon-fgjn0v0q", "ip_version": "ipv4", "vlan": 111, "mtu": 1500, "customer_address": "10.1.0.1/24", "amazon_address": "10.1.0.5/24", "customer_as": "111", "auth_key": "0xy.wr9h9miV64Sp9PfQU2eL", "route_filter_prefixes": [], "direct_connect_gateway_id": "97fe85e4-ca2f-4192-b3cd-d5c249d7a21f" } } |
Explanation |
A virtual interface was added. |
Possible failure causes |
· Internal error. · Invalid JSON format. · Invalid parameter. · Invalid UUID. · The UUID already exists. · The specified public cloud account does not exist. · The specified direct connect gateway does not exist. · Please specify a virtual interface name. · The name of a virtual interface cannot exceed 100 characters. Only letters, digits, and hyphens (-) are supported. · The description of a virtual interface cannot exceed 255 characters. Only letters, digits, spaces, and special characters(!._-:/()#,@[]+=&;{}$*) are supported. · Invalid type for the virtual interface. · Invalid IP version for the virtual interface. · Please specify a VLAN ID for the virtual interface. · The VLAN ID of a virtual interface must be an integer in the range of 1 to 4094. · Please specify a BGP peer AS number for the virtual interface. · The BGP peer AS number of a virtual interface must be an integer in the range of 1 to 2147493647. · The MTU value for a virtual interface must be 1500 or 8500. · Please specify prefixes for the virtual interface. · You can specify up to 100 prefixes for a virtual interface. · Invalid IP address for the virtual interface. · Invalid BGP peer IP address for the virtual interface. · Failed to create the public virtual interface on the public cloud. · Failed to create the transit virtual interface on the public cloud. · The BGP peer address and the Amazon address must be in the same CIDR of a prefix specified for the virtual interface. · The BGP peer address and the Amazon address must be in the same CIDR. · The IP version of the network prefixes specfied for a virtual interface must be the same as that of the virtual interface. · You can create up to one transit virtual interface for a direct connect. · The virtual interfaces created for the same direct connect must use different VLANs. · The format of the BGP authentication key does not meet the AWS requirements. · The BGP authentication key can contain up to 80 characters. · The prefix length of the IPv6 network address must be smaller than or equal to 64 bits. |
Update virtual interface
Keyword |
PUBLIC_CLOUD_RESOURCE |
Message text |
Executed public cloud resource $1 |
Variable fields |
$1: Virtual interface update request. |
Example |
{ "action": "UpdateVirtualInterface", "content": { "id": "57fe85e4-ca2f-4192-b3cd-d5c249d7a21f", "name": "vt1", "description": "vt1" } } |
Explanation |
A virtual interface was updated. |
Possible failure causes |
· Internal error. · Invalid JSON format. · Invalid parameter. · Please specify a virtual interface name. · The name of a virtual interface cannot exceed 100 characters. Only letters, digits, and hyphens (-) are supported. · The description of a virtual interface cannot exceed 255 characters. Only letters, digits, spaces, and special characters(!._-:/()#,@[]+=&;{}$*) are supported. · The specified virtual interface does not exist. · Failed to update the virtual interface on the public cloud. · Only virtual interfaces in pending or available states can be modified. |
Delete virtual Interface
Keyword |
PUBLIC_CLOUD_RESOURCE |
Message text |
Executed public cloud resource $1 |
Variable fields |
$1: Virtual interface deletion request. |
Example |
{ "action": "DeleteVirtualInterface", "content": { "id": "57fe85e4-ca2f-4192-b3cd-d5c249d7a21f" } } |
Explanation |
A virtual interface was deleted. |
Possible failure causes |
· Internal error. · Invalid JSON format. · Invalid parameter. · The id must be specified. · The specified virtual interface does not exist. · Failed to delete the virtual interface from the public cloud. |
Updated license usage info for public cloud service
Keyword |
SYNC_LICENSE_USED_OP |
Message text |
Updated license usage information for the public cloud service. |
Variable fields |
N/A |
Example |
Updated license usage information for the public cloud service. |
Explanation |
The license usage information was updated. |
Possible failure causes |
· Internal error. · Failed to obtain information about instances from the public cloud. · No licenses are installed for the public cloud service. |
Add VPN connection
Keyword |
ADD_VPN_CONNECTION_OP |
Message text |
Executed public cloud resource: $1 |
Variable fields |
$1: VPN connection adding request. |
Example |
Executed public cloud resource “{ "action": "CreateVpnConnection", "content": { "id": "47fe85e4-ca2f-4192-b3cd-d5c249d7a21f", "customer gateway_id": "b8f07739-68d5-47ba-bf8f-8f8ad05e054a", "name": "vct1", "description": "vct1444444", "region": "eu-north-1", "transit_gateway_id": "03e66305-5440-47a8-aee1-272c02e46219", "custom_gateway_id": "47fe85e4-ca2f-4192-b3cd-d5c249d7a21f", "local_ipv4_network_cidr": "5.0.0.0/24", "remote_ipv4_network_cidr": "6.0.0.0/24", "tunnel_options": [ { "tunnel_number": 1, "tunnel_inside_cidr": "2.2.2.0/24", "pre_share_key": "abcdefg12345", "phase1_encryption_algorithms": [ "AES128" ], "phase1_integrity_algorithms": [ "SHA1" ], "phase1_dh_group_numbers": [ "2" ], "phase2_encryption_algorithms": [ "AES128" ], "phase2_integrity_algorithms": [ "SHA1" ], "phase2_dh_group_numbers": [ "2" ], "ike_versions": [ "ikev1" ], "phase1_lifetime_seconds": 3600, "phase2_lifetime_seconds": 3600, "rekey_margin_time_seconds": 540, "rekey_fuzz_percentage": 100, "replay_window_size": 1024, "dpd_timeout_seconds": 30, "dpd_timeout_action": "clear", "startup_action": "add" }, { "tunnel_number": 2, "tunnel_inside_cidr": "2.2.2.0/24", "pre_share_key": "abcdefg12345", "phase1_encryption_algorithms": [ "AES128" ], "phase1_integrity_algorithms": [ "SHA1" ], "phase1_dh_group_numbers": [ "2" ], "phase2_encryption_algorithms": [ "AES128" ], "phase2_integrity_algorithms": [ "SHA1" ], "phase2_dh_group_numbers": [ "2" ], "ike_versions": [ "ikev1" ], "phase1_lifetime_seconds": 3600, "phase2_lifetime_seconds": 3600, "rekey_margin_time_seconds": 540, "rekey_fuzz_percentage": 100, "replay_window_size": 1024, "dpd_timeout_seconds": 30, "dpd_timeout_action": "clear", "startup_action": "add" } ] } }” |
Explanation |
A VPN connection was added. |
Possible failure causes |
· Internal error. · Invalid JSON format. · Failed to create the VPN connection on the public cloud. · The name of a VPN connection cannot exceed 64 characters. Only letters and digits are supported. · The VPN connection description cannot exceed 255 characters. · Invalid local ipv4 CIDR. · Invalid remote ipv4 CIDR. · The VPN connection must be configured with options for two and only two tunnels. · Only one phase 1 encryption algorithm can be configured. · Invalid phase 1 encryption algorithm. · Only one phase 2 encryption algorithm can be configured. · Invalid phase 2 encryption algorithm. · Only one phase 1 authentication algorithm can be configured. · Invalid phase 1 authentication algorithm. · Only one phase 2 authentication algorithm can be configured. · Invalid phase 2 authentication algorithm. · Only one phase 1 DH group number can be configured. · Invalid phase 1 DH group number. · Only one phase 2 DH group number can be configured. · Invalid phase 2 DH group number. · Invalid IKE version. · Only one IKE version can be configured. · The phase 1 lifetime value must be an integer in the range of 900 to 28800. · The phase 2 lifetime value must be an integer in the range of 900 to 3600. · The phase 2 lifetime value must be less than the phase 1 lifetime value. · The DPD timeout value must be an integer equal to or greater than 30. · The value for the rekey margin time (seconds) parameter must be an integer in the range of 60 to half the phase 2 lifetime. · The value for the rekey fuzz (percentage) parameter must be an integer in the range of 0 to 100. · The value for the replay window size (packets) parameter must be an integer in the range of 64 to 2048. · The DPD timeout action can only be clear, restart, or none. · The startup action can only be add or start. · You can specify the IKE version as only IKEv2 when the startup action is Start. · You can specify the IKE version as only IKEv2 when the phase 1 encryption algorithm is AES128-GCM-16 or AES256-GCM-16. |
Update VPN connection
Keyword |
UPDATE_VPN_CONNECTION_OP |
Message text |
Executed public cloud resource: $1 |
Variable fields |
$1: VPN connection update request. |
Example |
Executed public cloud resource “{ "action": "UpdateVpnConnection", "content": { "id": "57fe85e4-ca2f-4192-b3cd-d5c249d7a21f", "name": "vct1", "description": "vct1", "local_ipv4_network_cidr": "3.1.1.1/24", "remote_ipv4_network_cidr": "4.1.1.1/24" } }” |
Explanation |
A VPN connection was updated. |
Possible failure causes |
· Internal error. · Invalid JSON format. · Failed to update the VPN connection on the public cloud. · The name of a VPN connection cannot exceed 64 characters. Only letters and digits are supported. · The VPN connection description cannot exceed 255 characters. · Invalid local ipv4 CIDR. · Invalid remote ipv4 CIDR. |
Delete VPN connection
Keyword |
DEL_VPN_CONNECTION_OP |
Message text |
Executed public cloud resource: $1 |
Variable fields |
$1: VPN connection deletion request. |
Example |
Executed public cloud resource “{ "action": "DeleteVpnConnection", "content": { "id": "57fe85e4-ca2f-4192-b3cd-d5c249d7a21f" } }” |
Explanation |
A VPN connection was deleted. |
Possible failure causes |
· Internal error. · Invalid JSON format. · The specified VPN connection does not exist. · Failed to delete the VPN connection from the public cloud. |
Add customer gateway
Keyword |
ADD_CUSTOMER_GATEWAY_OP |
Message text |
Executed public cloud resource: $1 |
Variable fields |
$1: Customer gateway adding request. |
Example |
Executed public cloud resource “{ "action": "CreateCustomerGateway", "content": { "id": "47fe85e4-ca2f-4192-b3cd-d5c249d7a211", "account_id": "57fe85e4-ca2f-4192-b3cd-d5c249d7a211", "region": "eu-north-1", "public_ip": "10.1.1.1", "bgp_as": 10 } }” |
Explanation |
A customer gateway was added. |
Possible failure causes |
· Internal error. · Invalid JSON format. · Invalid parameter. · Invalid BGP AS number. · Invalid public IP. · Please specify a public IP. · The specified public cloud account does not exist. · Failed to create a customer gateway to the public cloud. |
Delete customer gateway
Keyword |
DEL_CUSTOMER_GATEWAY_OP |
Message text |
Executed public cloud resource: $1 |
Variable fields |
$1: Customer gateway deletion request. |
Example |
Executed public cloud resource “{ "action": "DeleteCustomerGateway", "content": { "id": "47fe85e4-ca2f-4192-b3cd-d5c249d7a211" } }” |
Explanation |
A customer gateway was deleted. |
Possible failure causes |
· Internal error. · Invalid JSON format. · Failed to delete the customer gateway from the public cloud. · The specified customer gateway does not exist. |
Add route propagation
Keyword |
ADD_ROUTER_PROPAGATION_OP |
Message text |
Executed public cloud resource: $1 |
Variable fields |
$1: Route propagation enabling request. |
Example |
Executed public cloud resource “{ "action": "CreateRoutePropagation", "content": { "id": "47fe85e4-ca2f-4192-b3cd-d5c249d7a211", "transit_router_id": "61fe85e4-ca2f-4192-b3cd-d5c249d7a211", "resource_id": "71fe85e4-ca2f-4192-b3cd-d5c249d7a211", "resource_type": "direct-connect-gateway" } }” |
Explanation |
Route propagation was enabled. |
Possible failure causes |
· Internal error. · Invalid JSON format. · Invalid parameter. · Failed to create a route propagation on the public cloud. · Failed to obtain transit gateway attachments from the public cloud. · Cannot find transit gateway attachment by the specified resource id. · The specified resource does not exist. · The specified resource type is invalid. |
Delete route propagation
Keyword |
DEL_ROUTER_PROPAGATION_OP |
Message text |
Executed public cloud resource: $1 |
Variable fields |
$1: Route propagation disabling request. |
Example |
Executed public cloud resource “{ "action": "DeleteRoutePropagation", "content": { "id": "47fe85e4-ca2f-4192-b3cd-d5c249d7a211" } }” |
Explanation |
Route propagation was disabled. |
Possible failure causes |
· Internal error. · Invalid JSON format. · The specified route propagation does not exist. · Failed to delete the route propagation from the public cloud. |