关键字

ADD_COS_SERVICE_OP

日志内容

Added service: $1

参数解释

$1：北向服务请求体实体

举例

Added service:{

"service":{

"serviceName":"dddddddddddddddddsgfdgh",

"description":"",

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

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

}

}

日志说明

用户进行了添加北向服务的操作

失败原因

当操作失败时，可能的原因如下：

·     Invalid UUID：无效的UUID

·     The request body cannot be empty：请求体不能为空

·     The description can contain up to 512 characters：描述最长为512个字符

·     The custom.json cannot be empty：custom.json不能为空

·     The name can contain up to 64 characters：名称最长64个字符

·     Please specify a packageId：packageId不能为空

·     Please specify a name：名称不能为空

·     The custom.json contains invalid contents：custom.json内容无效

·     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：定制包文件内custom.json内容无效

·     The custom.json file must contain all customized keys：定制参数配置（custom.json）中要包含全部定制包中custom.json的key值

·     The regist-info.json file does not exist in the package：定制包文件内指定的regist-info.json不存在

·     The regist-info.json file in the package is invalid：定制包文件内指定的regist-info.json无效

·     The specified python script does not exist in the package.：定制包文件内指定的python脚本不存在

·     The name must be different in the regist-info.json file in the package：定制包文件regist-info.json内name字段不能相同

·     The name and requestMethod cannot be same at the same time in the regist-info.json file in the package：定制包文件regist-info内uri字段和requestMethod字段不能同时相同

·     The name is required in the regist-info.json file in the package：定制包文件regist-info.json内name字段不能为空

·     The name cannot exceed 64 characters in the regist-info.json file in the package：定制包文件regist-info.json内name字段最长64个字符

·     The pythonPath is required in the regist-info.json file in the package：定制包文件regist-info.json内pythonPath字段不能为空

·     The pythonPath cannot exceed 512 characters in the regist-info.json file in the package：定制包文件regist-info.json内pythonPath字段最长512个字符

·     The uri is required in the regist-info.json file in the package：定制包文件regist-info.json内uri字段不能为空

·     The uri cannot exceed 512 characters in the regist-info.json file in the package：定制包文件regist-info.json内uri字段最长512个字符

·     The requestMethod is required in the regist-info.json file in the package：定制包文件regist-info.json内requestMethod字段不能为空

·     The requestMethod cannot exceed 10 characters in the regist-info.json file in the package：定制包文件regist-info.json内requestMethod字段最长10个字符

·     The requestMethod is invalid in the regist-info.json file in the package：定制包文件regist-info.json内requestMethod字段无效

·     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：regist-info.json中的uri和已存在的网关路由路径冲突

·     Failed to register the gateway route：注册网关路由失败

·     Failed to register the authentication-free URL：注册免认证URL失败

·     Invalid cron field in the crontabs.json file：crontabs.json中cron字段不合法

·     The crontabs.json contains invalid contents：crontabs.json内容无效

·     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：定制包文件regist-info.json内uri字段必须以/开头，层级路径不能为空

·     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：定制包文件regist-info.json内pythonPath字段层级路径仅支持数字、字母、下划线和连字符，不支持空格

·     You have no privilege to perform the operation.： 当前用户无权限执行此操作

·     The background-process.json file in the package is invalid：定制包文件内指定的background-process.json无效

·     A name field value cannot exceed 64 characters in the background-process.json file in the package：定制包文件background-process.json内name字段最长64个字符

·     The name field is required in the background-process.json file in the package：定制包文件background-process.json内name字段不能为空

·     The pythonPath field is required in the background-process.json file in the package：定制包文件background-process.json内pythonPath字段不能为空

·     A pythonPath field value cannot exceed 512 characters in the background-process.json file in the package：定制包文件background-process.json内pythonPath字段最长512个字符

·     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：定制包文件background-process.json内pythonPath字段层级路径仅支持数字、字母、下划线和连字符，不支持空格

·     The value of each pythonPath field must be unique in the background-process.json file in the package：定制包文件background-process.json内pythonPath字段不能相同

·     An expression description can contain up to 512 characters：表达式说明最长512个字符

关键字

UPDATE_COS_SERVICE_OP

日志内容

Updated service: $1

参数解释

$1：北向服务的UUID

举例

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

日志说明

用户进行了修改北向服务的操作

失败原因

当操作失败时，可能的原因如下：

·     Invalid UUID：无效的UUID

·     The service does not exist：指定的服务不存在

·     The request body cannot be empty：请求体不能为空

·     The description can contain up to 512 characters：描述最长为512个字符

·     The custom.json cannot be empty：custom.json不能为空

·     The custom.json contains invalid contents：custom.json内容无效

·     The custom.json file must contain all customized keys.：定制参数配置（custom.json）中要包含全部定制包中custom.json的key值

·     Invalid cron field in the crontabs.json file：crontabs.json中cron字段不合法

·     The crontabs.json contains invalid contents：crontabs.json内容无效

·     The site does not exist：站点不存在

·     Duplicate sites：站点存在重复

·     Failed to update the service：更新服务失败

·     Internal server error：服务器内部错误

·     You have no privilege to perform the operation.： 当前用户无权限执行此操作

关键字

DEL_COS_SERVICE_OP

日志内容

Deleted service: $1

参数解释

$1：北向服务的UUID

举例

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

日志说明

用户进行了删除北向服务的操作

失败原因

当操作失败时，可能的原因如下：

·     Invalid UUID：无效的UUID

·     The service does not exist：指定的服务不存在

·     Failed to delete the gateway route：删除网关路由失败

·     Failed to delete the authentication-free URL：删除免认证URL失败

·     Failed to delete the service：删除服务失败

·     Internal server error：服务器内部错误

·     You have no privilege to perform the operation.： 当前用户无权限执行此操作

关键字

UPLOAD_COS_PACKAGE_OP

日志内容

Uploaded package: $1

参数解释

$1：定制包的名称

举例

Uploaded package: SUPER_CONTROLLER_COS_OM-E3103P01.zip

日志说明

用户进行了上传定制包的操作

失败原因

当操作失败时，可能的原因如下：

·     The custom.json contains invalid contents：custom.json内容无效

·     The version.json contains invalid contents：version.json内容无效

·     The custom package name cannot be empty：定制包文件名称不能为空

·     Invalid JSON format：无效的JSON格式

·     The custom package version is required in the version.json file in the package：定制包文件version.json内version字段不能为空

·     The custom package version cannot exceed 64 characters in the version.json file in the package：定制包文件version.json内version字段最长64个字符

·     The description cannot exceed 512 characters in the version.json file in the package：定制包文件version.json内description字段最长512个字符

·     The custom package name cannot exceed 64 characters in the version.json file in the package：定制包文件version.json内name字段最长64个字符

·     Failed to upload the custom package file：上传定制包文件失败

·     The version.json cannot be empty：version.json不能为空

·     The custom.json cannot be empty：custom.json不能为空

·     The custom.json file does not exist in the package：定制包文件内指定的custom.json不存在

·     The version.json file does not exist in the package：定制包文件内指定的version.json不存在

·     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：定制包文件名称以字母、数字、下划线开头，可包含特殊符号@()+-.={}，不可包含空格，最长512个字符

·     Invalid cron field in the crontabs.json file：crontabs.json中cron字段不合法

·     The custom package must be in the ZIP format：定制包仅支持ZIP格式

·     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.： 当前用户无权限执行此操作

关键字

DEL_COS_PACKAGE_OP

日志内容

Deleted package: $1

参数解释

$1：定制包的UUID

举例

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

日志说明

用户进行了删除定制包的操作

失败原因

当操作失败时，可能的原因如下：

·     Invalid UUID：无效的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_OP

日志内容

Upgraded service: $1

参数解释

$1：定制包的UUID

举例

Upgraded service:{

"service":{

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

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

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

}

}

日志说明

用户进行了定制包的升级操作

失败原因

当操作失败时，可能的原因如下：

·     Please specify a service id：请指定服务的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：定制包文件内指定的background-process.json无效

·     A name field value cannot exceed 64 characters in the background-process.json file in the package：定制包文件background-process.json内name字段最长64个字符

·     The name field is required in the background-process.json file in the package：定制包文件background-process.json内name字段不能为空

·     The pythonPath field is required in the background-process.json file in the package：定制包文件background-process.json内pythonPath字段不能为空

·     A pythonPath field value cannot exceed 512 characters in the background-process.json file in the package：定制包文件background-process.json内pythonPath字段最长512个字符

·     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：定制包文件background-process.json内pythonPath字段层级路径仅支持数字、字母、下划线和连字符，不支持空格

·     The value of each pythonPath field must be unique in the background-process.json file in the package：定制包文件background-process.json内pythonPath字段不能相同

·     An expression description can contain up to 512 characters：表达式说明最长512个字符

关键字

UPDATE_PARAMETER_CONFIG_OP

日志内容

Updated parameter settings: $1

参数解释

$1：定制包的UUID

举例

Updated parameter settings: {

  "configs":[{

    "key": "sftpServerIP",

    "value":"192.158.50.9"

  } ]

}

日志说明

用户进行了修改参数设置的操作

失败原因

当操作失败时，可能的原因如下：

·     SFTP Server IP不符合IP格式。IPv4地址为点分十进制格式，IPv6地址为冒分十六进制格式：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服务器端口范围仅支持1～65535的整数

·     SFTP server user name cannot be empty：SFTP服务器的名称不能为空

·     The SFTP server password failed to be encrypted：SFTP Server密码加密失败

·     Internal server error：服务器内部错误

·     You have no privilege to perform the operation：当前用户无权限执行此操作

关键字

ADD_SNMPv3_SERVER_OP

日志内容

Added SNMPv3 server: $1

参数解释

$1：SNMPv3 server请求体实体

举例

Added SNMPv3 server: {

        "serverIp": "192.158.50.9",

        "serverPort":"162",

        "securityName":"admin",

        "authProtocol":"MD5",

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

        "privProtocol":"DES",

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

 }

日志说明

用户进行了新增SNMPv3 server的操作

失败原因

当操作失败时，可能的原因如下：

·     Failed to add the SNMPv3 server：新增SNMPv3 Server失败

·     An SNMPv3 server already exists with the specified IP address：指定IP地址的SNMPV3 Server已存在

·     Please specify an IP address：serverIp不能为空

·     Invalid SNMPv3 server IP address. An IPv4 address must be in dotted decimal notation, and an IPv6 address must be in colon hexadecimal notation：SNMPv3 Server IP不符合IP格式。IPv4地址为点分十进制格式，IPv6地址为冒分十六进制格式

·     Please specify a port number：serverPort不能为空

·     Please specify a security name：securityName不能为空

·     The port number must be an integer in the range of 1 to 65535：serverPort取值范围为1~65535的整数

·     The security name is a string up to 32 characters that can contain only letters, digits, and underscores (_)：securityName最长32个字符，仅支持字母、数字和下划线

·     The encryption algorithm can only be DES, 3DES, AES128, AES192, or AES256：privProtocol取值仅支持DES、3DES、AES128、AES192和AES256

·     The authentication algorithm can only be MD5, SHA-1, SHA-224, SHA-256, SHA-384, or SHA-512：authProtocol取值仅支持 MD5、SHA-1、SHA-224、SHA-256、SHA-384和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：privPassword有效长度为8~64位字符，不支持中文、~、?和空格

·     The authentication password must be a string of 8 to 64 characters that cannot contain chinese characters, wavy lines(~), question marks (?), and spaces：authPassword有效长度为8~64位字符，不支持中文、~、?和空格

·     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_OP

日志内容

Updated SNMPv3 server: $1

参数解释

$1：SNMPv3 server请求体实体

举例

Updated SNMPv3 server: {

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

"serverIp":"3.3.3.3",

"serverPort":"33",

"securityName":"fdsfds",

"authProtocol":"MD5",

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

"privProtocol":"AES128",

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

}

日志说明

用户进行了修改SNMPv3 server的操作

失败原因

当操作失败时，可能的原因如下：

·     Failed to edit the SNMPv3 server：修改SNMPv3 Server失败

·     The specified SNMPv3 server does not exist：指定的SNMPv3 Server不存在。

·     Please specify a port number：serverPort不能为空

·     Please specify a security name：securityName不能为空

·     The port number must be an integer in the range of 1 to 65535：serverPort取值范围为1~65535的整数

·     The security name is a string up to 32 characters that can contain only letters, digits, and underscores (_)：securityName最长32个字符，仅支持字母、数字和下划线

·     The encryption algorithm can only be DES, 3DES, AES128, AES192, or AES256：privProtocol取值仅支持DES、3DES、AES128、AES192和AES256

·     The authentication algorithm can only be MD5, SHA-1, SHA-224, SHA-256, SHA-384, or SHA-512：authProtocol取值仅支持 MD5、SHA-1、SHA-224、SHA-256、SHA-384和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：privPassword有效长度为8~64位字符，不支持中文、~、?和空格

·     The authentication password must be a string of 8 to 64 characters that cannot contain chinese characters, wavy lines(~), question marks (?), and spaces：authPassword有效长度为8~64位字符，不支持中文、~、?和空格

·     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：无效的UUID

关键字

DEL_SNMPv3_SERVER_OP

日志内容

Deleted SNMPv3 server: $1

参数解释

$1：SNMPv3 server的UUID

举例

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

日志说明

用户进行了删除SNMPv3 server的操作

失败原因

当操作失败时，可能的原因如下：

·     Failed to delete the SNMPv3 server：删除SNMPv3 Server失败

·     The specified SNMPv3 server does not exist：指定的SNMPv3 Server不存在。

·     You have no privilege to perform the operation：当前用户无权限执行此操作

·     Invalid UUID：无效的UUID

关键字

ACTION_UPDATE_ALARM_SEVERITY_RENDER

日志内容

Edit alarm severity mapping: $1

参数解释

$1：告警转换对应信息

举例

Edit alarm severity mapping: [{

        "originSeverity": "1",

        "renderSeverity":"3"

 }]

日志说明

用户进行了告警信息转换变更的操作

失败原因

当操作失败时，可能的原因如下：

·     The value range for the original severity level is 0 to 21474836：原始告警级别范围为0~21474836

·     The value range for the mapped severity level is 0 to 21474836：映射告警级别范围为0~21474836

关键字

ACTION_IMPORT_DC_RESOURCE

日志内容

Imported DC resource: $1

参数解释

$1：站点的请求消息体

举例

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

日志说明

用户进行了导入数据中心站点资源的操作

失败原因

当操作失败时，可能的原因如下：

·     The site with the specified UUID does not exist：指定的站点不存在

·     Failed to connect to the site：指定的站点连接失败

·     The itom-cmdb-rs-svc service has exceptions：itom-cmdb-rs-svc服务存在异常

关键字

ADD_NSO_NETWORK_OP

日志内容

Added network “$1”, request: $2

参数解释

$1：虚拟链路层网络的ID

$2：虚拟链路层网络请求消息体

举例

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}}

日志说明

用户进行了添加虚拟链路层网络的操作

失败原因

当操作失败时，可能的原因如下：

·     Invalid JSON format：无效的JSON格式

·     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：VNI分配失败

·     Operation failed. The UUID already exists：创建失败，UUID已存在

·     Failed to add the resource：添加配置项失败

·     No available VNIs：VNI已耗尽

·     The VNI has been used：VNI已被使用

·     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_NSO_NETWORK_OP

日志内容

Updated network “$1”, request: $2

参数解释

$1：虚拟链路层网络的ID

$2：虚拟链路层网络请求消息体

举例

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

日志说明

用户进行了修改虚拟链路层网络的操作

失败原因

当操作失败时，可能的原因如下：

·     Invalid JSON format：无效的JSON格式

·     The UUID is required：UUID不能为空

·     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：虚拟链路层网络的Segment ID不允许修改

·     The UUID of a tenant cannot be modified：租户的UUID不允许修改

·     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：当前控制组件版本不支持该功能

关键字

DEL_NSO_NETWORK_OP

日志内容

Deleted network “$1”.

参数解释

$1：虚拟链路层网络的ID

举例

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

日志说明

用户进行了删除虚拟链路层网络的操作

失败原因

当操作失败时，可能的原因如下：

·     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_NSO_ROUTER_OP

日志内容

Added router “$1”, request: $2

参数解释

$1：虚拟路由器的ID

$2：虚拟路由器请求消息体

举例

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}}

日志说明

用户进行了添加虚拟路由器的操作

失败原因

当操作失败时，可能的原因如下：

·     Invalid JSON format：无效的JSON格式

·     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：CIDR不能相互重叠

·     Failed to add the resource：添加配置项失败

·     Operation failed. The UUID already exists：创建失败，UUID已存在

·     No available VNIs：VNI已耗尽

·     VNI allocation failed：VNI分配失败

·     The VNI has been used：VNI已被使用

·     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_NSO_ROUTER_OP

日志内容

Updated router “$1”, request: $2

参数解释

$1：虚拟路由器的ID

$2：虚拟路由器请求消息体

举例

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

日志说明

用户进行了修改虚拟路由器的操作

失败原因

当操作失败时，可能的原因如下：

·     Invalid JSON format：无效的JSON格式

·     The UUID is required：UUID不能为空

·     The tenant cannot be modified：租户不允许修改

·     The CIDR has been used by a vSubnet：CIDR网段已被虚拟子网使用

·     Different CIDRs cannot overlap：CIDR不能相互重叠

·     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：当前控制组件版本不支持该功能

关键字

DEL_NSO_ROUTER_OP

日志内容

Deleted router “$1”.

参数解释

$1：虚拟路由器的ID

举例

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

日志说明

用户进行了删除虚拟路由器的操作

失败原因

当操作失败时，可能的原因如下：

·     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_NSO_LOGICALLINK_OP

日志内容

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

参数解释

$1：虚拟路由器的ID

$2：虚拟链路层网络的ID

$3：逻辑链路请求消息体

举例

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"}}

日志说明

用户进行了添加逻辑链路的操作

失败原因

当操作失败时，可能的原因如下：

·     Invalid JSON format：无效的JSON格式

·     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：虚拟子网未配置网关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：同一个虚拟路由器的虚拟子网CIDR不能重叠

·     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：当前控制组件版本不支持该功能

关键字

DEL_NSO_LOGICALLINK_OP

日志内容

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

参数解释

$1：虚拟路由器的ID

$2：虚拟链路层网络的ID

$3：逻辑链路请求消息体

举例

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"}}

日志说明

用户进行了删除逻辑链路的操作

失败原因

当操作失败时，可能的原因如下：

·     Invalid JSON format：无效的JSON格式

·     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：当前控制组件版本不支持该功能

关键字

BOUND_SUBNET_VROUTER_OP

日志内容

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

参数解释

$1：虚拟链路层网络的ID

$2：虚拟路由器的ID

$3：虚拟子网绑定至虚拟路由器请求消息体

举例

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"}}

日志说明

用户进行了虚拟子网绑定至虚拟路由器的操作

失败原因

当操作失败时，可能的原因如下：

·     Invalid JSON format：无效的JSON格式

·     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：虚拟子网未配置网关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：同一个虚拟路由器的虚拟子网CIDR不能重叠

·     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：当前控制组件版本不支持该功能

关键字

UNBOUND_SUBNET_VROUTER_OP

日志内容

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

参数解释

$1：虚拟链路层网络的ID

$2：虚拟路由器的ID

$3：虚拟子网解除绑定虚拟路由器请求消息体

举例

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"}}

日志说明

用户进行了虚拟子网解除绑定虚拟路由器的操作

失败原因

当操作失败时，可能的原因如下：

·     Invalid JSON format：无效的JSON格式

·     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_NSO_SIET_OP

日志内容

Added site “$1”, request: $2

参数解释

$1：站点的ID

$2：站点请求消息体

举例

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":"[]"}}

日志说明

用户进行了添加站点的操作

失败原因

当操作失败时，可能的原因如下：

·     Invalid JSON format：无效的JSON格式

·     The site name is required：站点名称不能为空

·     The URL is required：站点的URL不能为空

·     The username is required：站点的用户名不能为空

·     The password is required：站点的用户密码不能为空

·     The driver type is required：站点的Driver类型不能为空

·     The license capacity is insufficient：License不足

·     Invalid request：无效的请求

·     Internal error：内部错误

·     Failed to add the resource：添加配置项失败

·     Operation failed. The UUID already exists：创建失败，UUID已存在

·     The site name has been used：站点名称已被占用

·     The url has been used：该URL对应的站点已存在

·     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：http(s):// IPv4|[IPv6]:端口，IPv4地址为点分十进制格式，不支持广播地址、环回地址、组播地址和保留地址；IPv6地址为冒分十六进制格式，仅支持全球单播地址；端口范围为1～65535的整数

·     Failed to apply for the license：申请授权失败

·     Operation failed, because license is not enough：操作失败，License不足

关键字

UPDATE_NSO_SIET_OP

日志内容

Updated site “$1”, request: $2

参数解释

$1：站点的ID

$2：站点请求消息体

举例

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":"[]"}}

日志说明

用户进行了修改站点的操作

失败原因

当操作失败时，可能的原因如下：

·     Invalid JSON format：无效的JSON格式

·     The UUID is required：UUID不能为空

·     The site name cannot be modified：站点名称不允许修改

·     The custom settings of a site cannot be modified：站点的自定义配置不允许修改

·     Invalid request：无效的请求

·     The site has been bound to tenants：该站点已被租户使用

·     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：该URL对应的站点已存在

·     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：该站点已经被纳管，URL不可修改

·     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：http(s):// IPv4|[IPv6]:端口，IPv4地址为点分十进制格式，不支持广播地址、环回地址、组播地址和保留地址；IPv6地址为冒分十六进制格式，仅支持全球单播地址；端口范围为1～65535的整数

关键字

DEL_NSO_SIET_OP

日志内容

Deleted site “$1”.

参数解释

$1：站点的ID

举例

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

日志说明

用户进行了删除站点的操作

失败原因

当操作失败时，可能的原因如下：

·     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_NSO_SUBNET_OP

日志内容

Added subnet “$1”, request: $2

参数解释

$1：虚拟子网的ID

$2：虚拟子网请求消息体

举例

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"]}}

日志说明

用户进行了增加虚拟子网的操作

失败原因

当操作失败时，可能的原因如下：

·     The vSubnet name is required：虚拟子网名称不能为空

·     The vNetwork UUID is required：虚拟链路层网络UUID不能为空

·     The IP version is required：IP版本不能为空

·     Invalid JSON format：无效的JSON格式

·     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：创建失败，UUID已存在

·     The gateway IP address is required when the vNetwork is an external network：虚拟链路层网络为外部网络时，网关IP地址不能为空

·     The gateway IP address doesn’t belong to the subnet：网关IP地址与子网不在同一网段

·     The CIDR overlaps with another CIDR in the same vNetwork：CIDR与虚拟链路层网络下的其他CIDR重叠

·     Invalid DHCP address pool：无效的DHCP地址池

·     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：启用DHCP时，网关IP地址不能为空

·     The gateway IP address conflicts with the subnet broadcast address：网关IP地址和子网广播IP地址冲突

·     An IPv4 subnet cannot be configured with the IPv6 address mode or the IPv6 RA mode：IPv4版本的子网不允许配置IPv6地址模式和IPv6 RA模式

·     The IPv6 address mode and the IPv6 RA mode must be the same：IPv6地址模式和IPv6 RA模式不一致

·     When the IPv6 address mode is SLAAC or Stateless DHCPv6, the subnet mask must be 64：IPv6地址模式为SLAAC和无状态DHCPv6类型时，子网掩码必须是为64

·     When the IPv6 address mode is Stateful DHCPv6, Stateless DHCPv6 or SLAAC, DHCP must be enabled：IPv6地址模式为有状态DHCPv6，无状态DHCPv6和SLAAC时，必须使能DHCP

·     The gateway IP address conflicts with the subnet address：网关IP地址和子网IP地址冲突

·     Invalid CIDR：无效的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_NSO_SUBNET_OP

日志内容

Updated subnet “$1”, request: $2

参数解释

$1：虚拟子网的ID

$2：虚拟子网请求消息体

举例

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"]}}

日志说明

用户进行了修改虚拟子网的操作

失败原因

当操作失败时，可能的原因如下：

·     The UUID is required：UUID不能为空

·     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：仅当子网处于未部署状态时才可修改CIDR

·     The IP version can be modified only when the subnet is undeployed：仅当子网处于未部署状态时才可修改IP版本

·     The DHCP state can be modified only when the subnet is undeployed：仅当子网处于未部署状态时才可修改DHCP状态

·     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：该子网已被虚拟路由器绑定，不允许修改网关IP地址

·     The gateway IP address doesn’t belong to the subnet：网关IP地址与子网不在同一网段

·     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：网关IP地址和子网广播IP地址冲突

·     The IPv6 RA mode can be modified only when the subnet is undeployed：仅当子网处于未部署状态时才可修改IPv6的RA模式

·     The IPv6 address mode can be modified only when the subnet is undeployed：仅当子网处于未部署状态时才可修改IPv6的地址模式

·     The gateway IP address conflicts with the subnet address：网关IP地址和子网IP地址冲突

·     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：已绑定虚拟路由器的子网不允许删除网关IP地址

·     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：当前控制组件版本不支持该功能

关键字

DEL_NSO_SUBNET_OP

日志内容

Deleted subnet “$1”.

参数解释

$1：虚拟子网的ID

举例

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

日志说明

用户进行了删除虚拟子网的操作

失败原因

当操作失败时，可能的原因如下：

·     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：当前控制组件版本不支持该功能

关键字

CONTROLLED_NSO_SITE_OP

日志内容

Synchronized settings from sites "$1".

参数解释

$1：站点名称

举例

Synchronized settings from sites "site1".

日志说明

用户进行了反向纳管站点的操作

失败原因

当操作失败时，可能的原因如下：

·     Invalid JSON format：无效的JSON格式

·     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：纳管失败，站点'站点名称'的虚拟路由器'虚拟路由器名称'未配置Segment ID

·     The VNI has been used：VNI已被使用

·     VNI allocation failed：VNI分配失败

·     DriverManager microservice processing failed：插件处理失败

·     Cannot reach site “site_info”：站点“站点信息”不可达

·     Site “site_info” processing failed：站点“站点信息”处理失败

·     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：纳管失败，站点“站点信息”的子网名称不能超过255个字符

·     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：纳管失败，站点“站点信息”的虚拟链路层网络名称不能超过255个字符

·     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：纳管失败，站点“站点信息”的虚拟路由器名称不能超过255个字符

·     Failed to process the request. Please check whether the plugin matches the version of Super Controller：请求处理失败，请检查插件与Super Controller版本是否配套

关键字

ADD_NSO_TENANT_OP

日志内容

Added tenant “$1”, request: $2

参数解释

$1：租户的ID

$2：租户请求消息体

举例

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"}}

日志说明

用户进行了添加租户的操作

失败原因

当操作失败时，可能的原因如下：

·     Invalid JSON format：无效的JSON格式

·     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：创建失败，UUID已存在

·     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：不允许创建名称为default的租户

·     Failed to process the request. Please check whether the plugin matches the version of Super Controller：请求处理失败，请检查插件与Super Controller版本是否配套

·     This feature is not supported by the current version of the controller：当前控制组件版本不支持该功能

关键字

UPDATE_NSO_TENANT_OP

日志内容

Updated tenant “$1”, request: $2

参数解释

$1：租户的ID

$2：租户请求消息体

举例

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

日志说明

用户进行了修改租户的操作

失败原因

当操作失败时，可能的原因如下：

·     Invalid JSON format：无效的JSON格式

·     The UUID is required：UUID不能为空

·     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：站点的设备组已被Transit Fabric纳管，并且站点上的租户已被Transit Router绑定，不允许删除该站点

·     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：指定站点的租户已被租户Router接入使用，不允许从指定站点移除

·     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：default类型租户的名称不允许修改

·     Failed to process the request. Please check whether the plugin matches the version of Super Controller：请求处理失败，请检查插件与Super Controller版本是否配套

·     This feature is not supported by the current version of the controller：当前控制组件版本不支持该功能

·     You cannot update a tenant named default：租户名称不允许修改为default

关键字

DEL_NSO_TENANT_OP

日志内容

Deleted tenant “$1”, request: $2

参数解释

$1：租户的ID

$2：租户请求消息体

举例

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

日志说明

用户进行了删除租户的操作

失败原因

当操作失败时，可能的原因如下：

·     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：该租户已被Transit Router使用

·     The specified resource does not exist：指定的资源不存在

·     You cannot delete the tenant, because the tenant is used by a tenant router access service：租户已被租户Router接入使用，不允许删除

·     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：请求处理失败，请检查插件与Super Controller版本是否配套

·     This feature is not supported by the current version of the controller：当前控制组件版本不支持该功能

关键字

ADD_NSO_VNI_OP

日志内容

Added VNI “$1”, request: $2

参数解释

$1：全局资源池的ID

$2：全局资源池请求消息体

举例

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"}]}}

日志说明

用户进行了新增全局资源池的操作

失败原因

当操作失败时，可能的原因如下：

·     Invalid JSON format：无效的JSON格式

·     Invalid request：无效的请求

·     The VNI name is required：VNI名称不能为空

·     The VNI range is required：VNI范围不能为空

·     Invalid VNI range：无效的VNI范围

·     Internal error：内部错误

·     Failed to add the resource：添加配置项失败

·     Operation failed. The UUID already exists：创建失败，UUID已存在

·     The VNI name has been used：VNI名称已被占用

关键字

UPDATE_NSO_VNI_OP

日志内容

Updated VNI “$1”, request: $2

参数解释

$1：全局资源池的ID

$2：全局资源池请求消息体

举例

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

日志说明

用户进行了修改全局资源池的操作

失败原因

当操作失败时，可能的原因如下：

·     The UUID is required：UUID不能为空

·     The VNI name cannot be modified：VNI名称不允许修改

·     The VNI type cannot be modified：VNI类型不允许修改

·     Invalid JSON format：无效的JSON格式

·     Invalid request：无效的请求

·     The resource does not exist：配置项不存在

·     Internal error：内部错误

·     Invalid VNI range：无效的VNI范围

·     The VNI has been used and cannot be modified：VNI已被使用，不允许修改

·     Different VNI ranges cannot overlap：VNI范围不能重叠

·     Failed to modify the resource：修改配置项失败

·     The specified resource does not exist：指定的资源不存在

关键字

DEL_NSO_VNI_OP

日志内容

Deleted VNI “$1”.

参数解释

$1：全局资源池的ID

举例

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

日志说明

用户进行了删除全局资源池的操作

失败原因

当操作失败时，可能的原因如下：

·     Invalid request：无效的请求

·     The resource does not exist：配置项不存在

·     Internal error：内部错误

·     Failed to delete the resource：删除配置项失败

·     The specified resource does not exist：指定的资源不存在

关键字

UPDATE_NSO_CONFIG_OP

日志内容