- 产品与解决方案
- 行业解决方案
- 服务
- 支持
- 合作伙伴
- 关于我们
手册下载
操作日志信息参考
资料版本：6W508-20240531
Copyright © 2024 新华三技术有限公司 版权所有，保留一切权利。
非经本公司书面许可，任何单位和个人不得擅自摘抄、复制本文档内容的部分或全部，并不得以任何形式传播。
除新华三技术有限公司的商标外，本手册中出现的其它公司的商标、产品标识及商品名称，由各自权利人拥有。
本文档中的信息可能变动，恕不另行通知。
2.1 Create network change simulation task
2.2 Delete network change simulation task
2.10 Update link configuration
2.12 Delete manually added link
2.13 Update device configuration
2.14 Reset device configuration
3.11 Modify access relationship
3.12 Delete access relationship
3.20 Change provisioning for application
3.21 Revert changes for application
3.22 Deprovision network for application
3.24 Intent execution task rollback
4.9 Synchronized injected route configuration and learned route configuration to vBGP
5.1 Create mapping table of access network
5.2 Update mapping table of access network
5.3 Delete mapping table of access network
5.4 Modify inspection port status
5.5 Bound working port to mapping table
5.6 Unbound working port to mapping table
5.8 Delete default access VLAN
5.9 Create mapping table of service network
5.10 Update mapping table of service network
5.11 Delete mapping table of service network
5.12 Bound mapping table to device
5.13 Updated binding relationship between mapping table and device
5.14 Delete bindings between mapping table and all devices
5.15 Bound port to mapping table
5.16 Update binding relationship between port and mapping table
5.17 Deleted bindings between mapping table and all ports
6.1 Execute capacity simulation task
6.2 Get simulation config change task
6.3 Interrupt capacity simulation task
7.1 Register SeerAnalyzer info
8.4 Activate a certificate for a service
8.5 Deactivate certificates for a service
10.1 Change thresholds for a CPU
10.2 Change thresholds for all CPUs
11.6 Devices change to fail-safe mode
11.7 Devices change to normal mode
11.8 Modify interface status by interface index
11.9 Single device change to fail-safe mode
11.10 Single device change to normal mode
11.11 Bulk switched to fail-safe mode
11.12 Bulk switched to normal mode
13.7 Update BGP session settings
13.11 Delete OSPF network route
14.4 Start scanning traditional NE
14.5 Stop scanning traditional NE
15.9 Modify alert log remote transmission mode
15.10 Modify audit log transmission mode
17.6 Clear events on all devices
17.10 Create inter-device link
17.11 Delete inter-device link
17.12 Import inter-device link
19.4 Created device group model
19.5 Updated device group model
19.6 Deleted device group model
19.10 Created interconnect model
19.11 Updated interconnect model
19.12 Deleted interconnect model
19.19 Created control protocol template
19.20 Updated control protocol template
19.21 Deleted control protocol template
19.26 Deleted interconnect list
19.27 Downloaded variable instance
19.28 Imported variable instance
19.29 Assigned variable resource
19.30 Updated variable instance
19.32 Restore configure generation
21.4 Create custom outgoing external flow
21.5 Update custom outgoing external flow
21.6 Delete custom outgoing external flow
21.7 Create custom service flow
21.8 Update custom service flow
21.9 Delete custom service flow
22.1 Create contingency plan template
22.2 Update contingency plan template
22.3 Delete contingency plan template
22.4 Execute contingency plan template
22.6 Execute composite template
22.7 Create composite template
22.8 Update composite template
22.9 Delete composite template
24.4 Create firewall object group
24.5 Update firewall object group
24.6 Delete firewall object group
24.25 Upload IPS signature library from local device
24.32 Upload virus library from local device
24.33 Upload application library from local device
24.34 Create attack defense policy
24.35 Update attack defense policy
24.36 Delete attack defense policy
24.37 Create URL filter category
24.38 Update URL filter category
24.39 Delete URL filter category
24.43 Create URL filter policy
24.44 Update URL filter policy
24.45 Delete URL filter policy
25.1 Update global configuration
26.5 Modify configuration file
26.6 Delete configuration file
26.7 Deploy configuration snippets
26.9 Start automatic configuration process
26.10 Stop automatic configuration process
26.15 Update aggregate interface
26.16 Configure aggregate interface
26.17 Add automated configuration template
26.18 Add automation parameters
26.23 Add automatic device replacement task
26.24 Add fabric and deploy resource pool
26.25 Create device configuration fragment
26.26 Update device configuration fragment
26.27 Delete device configuration fragment
26.28 Import device configuration fragment list
26.29 Delete device configuration fragment list
26.31 Start device automation process
26.32 Stop device automation process
26.33 Sync device automation process
26.38 Delete an interface description
26.41 Deleted an aggregate interface
27.1 IP isolation configuration
27.2 ARP filter module configuration
29.1 Create application assurance task
29.2 Update application assurance task
29.3 Delete application assurance task
31.1 Create elephant/mice flow policy
31.2 Update elephant/mice flow policy
31.3 Delete elephant/mice flow policy
32.1 Create application description
32.2 Update application description
32.3 Delete application description
32.7 Update NBAC global settings
33.1 Create VLAN-VXLAN mapping table
33.2 Update VLAN-VXLAN mapping table
33.3 Delete VLAN-VXLAN mapping table
33.4 Create QinQ-VXLAN mapping table
33.5 Update QinQ-VXLAN mapping table
33.6 Delete QinQ-VXLAN mapping table
33.7 Bind VLAN-VXLAN mapping table
33.8 Update VLAN-VXLAN mapping table binding
33.9 Delete VLAN-VXLAN mapping table binding
33.10 Bind ports to VLAN-VXLAN mapping table
33.11 Update bindings between ports and VLAN-VXLAN mapping table
33.12 Update bindings between ports and VLAN-VXLAN mapping table (new binding)
33.13 Update bindings between ports and VLAN-VXLAN mapping table (remove binding)
33.14 Delete bindings between ports and VLAN-VXLAN mapping table
33.15 Bind ports to QinQ-VXLAN mapping table
33.16 Update bindings between ports and QinQ-VXLAN mapping table
33.17 Delete bindings between ports and QinQ-VXLAN mapping table
33.18 Create VLAN-network mapping table
33.19 Update VLAN-network mapping table
33.20 Delete VLAN-network mapping table
33.21 Bind ports to VLAN-network mapping table
33.22 Update bindings between ports and VLAN-VXLAN mapping table
33.23 Delete bindings between ports and VLAN-VXLAN mapping table
33.30 Create device group VLAN range
33.31 Update device group VLAN range
33.32 Delete device group VLAN range
33.40 Batch export physical NEs
33.41 Start scanning physical NE
33.42 Stop scanning physical NE
33.43 Start migration on physical gateway
33.44 Complete migration on physical gateway
33.45 Start data synchronization on physical NE
33.46 Start configuration auditing on physical NE
33.47 Start reseting on physical NE
33.48 Start data synchronization on virtual NE
33.49 Start configuration auditing on virtual NE
33.51 Create NETCONF default user
33.53 Configure default MAC address
33.54 Delete default MAC address
33.57 Configure reserved option
33.64 Configure gateway network
33.67 Router unbound to gateway
33.69 Delete vRouter from resource
33.70 Create LAG interface member
33.71 Update LAG interface member
33.72 Delete LAG interface member
33.73 Delete M-LAG LAG interface member
33.77 Create global LAG interface configuration
33.78 Update global LAG interface configuration
33.79 Delete global LAG interface configuration
33.81 Create connection limit rule
33.82 Update connection limit rule
33.83 Delete connection limit rule
33.84 Create device deployment template
33.85 Update device deployment template
33.86 Delete device deployment template
33.87 Create control protocol template
33.88 Update control protocol template
33.89 Delete control protocol template
33.90 Create deploy resource pool
33.91 Update deploy resource pool
33.92 Delete deploy resource pool
33.97 Update Security global setting
33.106 Create tenant-gateway binding relationship
33.107 Update tenant-gateway binding relationship
33.108 Delete tenant-gateway binding relationship
33.115 Created interconnect interface
33.116 Updated interconnect interface
33.117 Deleted interconnect interface
33.118 Create auto deployment device information
33.119 Update auto deployment device information
33.120 Delete auto deployment device information
33.121 Create link information
33.122 Update link information
33.123 Delete link information
33.126 Synchronization device bridgeMac and serialNumber info
33.127 Synchronization device port info
33.131 Create replacement task
33.132 Delete replacement task
33.136 Create border interface
33.137 Update border interface
33.138 Delete border interface
33.139 Created cloud private line
33.140 Updated cloud private line
33.141 Deleted cloud private line
33.145 Create L2 multicast network
33.146 Update L2 multicast network
33.147 Delete L2 multicast network
33.154 Create SSM mapping rule
33.155 Delete SSM mapping rule
33.156 Create multicast source
33.157 Delete multicast source
33.164 Create BUM multicast replication profile
33.165 Update BUM multicast replication profile
33.166 Delete BUM multicast replication profile
33.167 Create interface-specific multicast network
33.168 Update interface-specific multicast network
33.169 Delete interface-specific multicast network
33.179 Create M-LAG group ID range
33.180 Update M-LAG group ID range
33.181 Delete M-LAG group ID range
33.182 Start fine-grained data synchronization on physical device
33.189 Create User-Defined Device Info
33.190 Delete User-Defined Device Info
33.194 Create address prefix rule
33.195 Update address prefix rule
33.196 Delete address prefix rule
33.200 Create routing policy node
33.201 Update routing policy node
33.202 Delete routing policy node
33.215 Enabled OSPF route redistribution rule
33.216 Update OSPF route redistribution rule
33.217 Disabled OSPF route redistribution rule
33.218 Enabled OSPFv3 route redistribution rule
33.219 Update OSPFv3 route redistribution rule
33.220 Disabled OSPFv3 route redistribution rule
33.221 Create OSPF interface policy
33.222 Update OSPF interface policy
33.223 Delete OSPF interface policy
33.224 Create OSPFv3 interface policy
33.225 Update OSPFv3 interface policy
33.226 Delete OSPFv3 interface policy
33.227 Create OSPF policy application
33.228 Delete OSPF policy application
33.229 Create OSPFv3 policy application
33.231 Delete OSPFv3 policy application
33.232 Update policy application
33.233 Delete policy application
33.234 Create configuration audit task
33.235 Update configuration audit task
33.236 Delete configuration audit task
33.237 Execute one-off configuration audit task
33.238 Manually trigger periodic configuration audit task once
33.239 Create third-party service device
33.240 Update third-party service device
33.241 Delete third-party service device
33.248 Clear auto discovered device list
33.249 Refreshed lock configuration successfully
33.250 Failed to refresh lock configuration because of parameter errors
33.251 Failed to refresh lock configuration because of module service conflicts
33.252 Locked multiple devices in bulk successfully
33.253 Failed to lock multiple devices in bulk because of parameter errors
33.254 Failed to lock device because of module service conflicts
33.255 Unlocked multiple devices in bulk successfully
33.256 Failed to unlock multiple devices in bulk because of parameter errors
33.257 Failed to unlock device because of module service conflicts
33.258 Create M-LAG group plan
33.259 Update M-LAG group plan
33.260 Delete M-LAG group plan
33.261 Bulk delete M-LAG group plans
33.262 Create M-LAG routed peer link
33.263 Update M-LAG routed peer link
33.264 Delete M-LAG routed peer link
33.271 Delete Unmanaged device
33.272 Allocate IPv4 address from NGFW address pool
33.273 Release IPv4 address in NGFW address pool
33.274 Allocate IPv6 address from NGFW address pool
33.275 Release IPv6 in NGFW address pool
33.276 Create security IP address pool
33.277 Update security IP address pool
33.278 Delete security IP address pool
33.279 Create Address Pool Set
33.280 Update Address Pool Set
33.281 Delete Address Pool Set
33.290 Bulk create VLAN-Network mappings
33.291 Bulk update VLAN-Network mappings
33.292 Bulk delete VLAN-Network mappings
33.293 Bulk export VLAN-VXLAN mappings
33.294 Bulk create PVLAN mappings
33.295 Bulk update PVLAN mappings
33.296 Bulk delete PVLAN mappings
33.297 Bulk export PVLAN mappings
33.303 Create OSPF resource pool
33.304 Update OSPF resource pool
33.305 Delete OSPF resource pool
33.306 Allocate OSPF router ID
33.310 Create downlink interfaces
33.311 Delete downlink interfaces
33.312 Import downlink interfaces
33.313 Synchronize device info to basic network management module
33.314 Bulk create VLAN-VXLAN mappings
33.315 Bulk update VLAN-VXLAN mappings
33.316 Bulk delete VLAN-VXLAN mappings
33.317 Bulk export VLAN-VXLAN mappings
33.318 Bulk import QinQ mappings
33.319 Bulk export QinQ mappings
33.320 Bulk import VLAN-VXLAN mappings
33.321 Bulk export VLAN-VXLAN mappings
33.322 Bulk create VLAN-network mappings Ports
33.323 Bulk delete VLAN-network mappings Ports
33.324 Bulk export VLAN-network mappings Ports
33.325 Bulk create VLAN-VXLAN mappings Ports
33.326 Bulk delete VLAN-VXLAN mappings Ports
33.327 Bulk export VLAN-VXLAN mappings Ports
33.328 Bulk create PVLAN mappings Ports
33.329 Bulk delete PVLAN mappings Ports
33.330 Bulk export PVLAN mappings Ports
33.332 Create or update permit VLANs
33.336 Create M-LAG system plan
33.337 Update M-LAG system plan
33.338 Delete M-LAG system plan
33.339 Bulk delete M-LAG system plans
33.340 Bulk create M-LAG routed peer links
33.341 Bulk update M-LAG routed peer links
33.342 Bulk delete M-LAG routed peer links
33.343 Bulk export M-LAG routed peer links
33.344 Bulk export Audit Result infos
33.346 Bulk delete VXLAN pools
33.347 Bulk delete VLAN-VXLAN mapping tables
33.348 Bulk delete QinQ mapping tables
33.349 Bulk delete PVLAN mapping tables
33.350 Create FW service resource NQA binding
33.351 Delete FW service resource NQA binding
33.352 Create LB service resource NQA binding
33.353 Delete LB service resource NQA binding
33.354 Update resource alarm thresholds
33.355 Migrate Link Configuration
33.356 Check M-LAG group consistency
33.357 Deploy configuration to device through SSH
34.1 Create network relocation
34.2 Update network relocation
34.3 Delete network relocation
35.3 Set YANG files identifier
36.4 Start data synchronization on device
36.5 Start configuration audit on device
36.15 Create L4-L7 device group
36.16 Update L4-L7 device group
36.17 Delete L4-L7 device group
37.1 Create radar detection task
37.2 Delete radar detection task
37.3 Clear periodic radar detection tasks
37.9 Retrieve device disk partitions
37.15 Configure scheduled upgrade
37.16 Delete scheduled upgrade
37.20 Create configuration file backup task
37.23 Configure scheduled backup
37.27 Modify interface status by interface index
37.28 Create connectivity detection task
37.29 Delete connectivity detection task
37.40 Update snapshot parameters
37.41 Update auto snapshot schedule
37.45 Update SSH connection parameters
37.46 Update SSH fingerprint parameters
38.1 Create resource access template
38.2 Delete resource access template
39.1 Unbind server network address plan
39.2 Import server network address plan
39.3 Export server network address plan
39.5 Delete server configuration
40.4 Create data type attributes
40.5 Update data type attribute
40.6 Delete data type attribute
40.15 Create action model properties
40.16 Update action model property
40.17 Delete action model property
40.21 Batch process action steps
40.23 Unpublish action package
40.24 Create action package version
40.30 Create process package properties
40.31 Update process package property
40.32 Delete process package property
40.36 Create process dependences
40.37 Delete process dependences
40.38 Designed process outputs assignment policy
40.40 Unpublish process package
40.41 Create process package version
40.42 Exporte process packages
40.45 Change process package status
40.46 Create process package case
40.47 Update process package case
40.48 Delete process package case
40.49 Create process package case instance
40.50 Execute process package case instance task
40.51 Rollback process package case instance task
40.52 Delete process package case instance
40.58 Rollback process instance
40.60 Execute process instance
41.1 Create rate limit template
41.2 Update rate limit template
41.3 Delete rate limit template
41.4 Create mirroring destination template
41.5 Update mirroring destination template
41.6 Delete mirroring destination template
41.13 Create physical port policy
41.14 Update physical port policy
41.15 Delete physical port policy
41.16 Create mirroring profile
41.17 Update mirroring profile
41.18 Delete mirroring profile
41.20 Create congestion management profile
41.21 Update congestion management profile
41.22 Delete congestion management profile
41.32 Update device optimization configuration
41.33 Update interface optimization configuration
41.40 Update gRPC common information
41.41 Create data collection policy
41.42 Update data collection policy
41.43 Delete data collection policy
41.44 Created data collection template
41.45 Updated data collection template
41.46 Deleted data collection template
41.47 Updated sensor path library
41.57 Create telemetry stream profile
41.58 Update telemetry stream profile
41.59 Delete telemetry stream profile
41.60 Add intelligent analytics
41.61 Delete intelligent analytics
43.11 Update service chain settings for a tenant
43.12 Update service chain settings
44.1 Create network-wide impact analysis task
44.2 Create connectivity test task
44.4 Enable tenant design mode
44.5 Disable tenant design mode
44.6 Receive request to deploy services to tenant
44.7 Deploy services to tenant
44.14 Orchestrated simulation resource
46.1 Created simulation network
46.2 Deleted simulation network
46.7 Upload configuration information file
46.8 Upload link information file
46.9 Clear configuration information
49.1 Create third-party service device
49.2 Update third-party service device
49.3 Delete third-party service device
49.4 Create third-party service
49.5 Update third-party service
49.6 Delete third party service
52.21 Create VDS distributed port group
52.22 Update VDS distributed port group
52.23 Delete VDS distributed port group
52.25 Sync vPort data of vCenter
52.26 Updated auto audit and sync settings of vCenter
52.28 Export vCenter difference details
52.29 Create interface availability zone
52.30 Delete interface availability zone
52.31 Update interface availability zone
52.32 Discover data of vCenter
52.33 Pull and incorporate data from vCenter
52.43 Pull and incorporate data from RHVM
52.44 Update auto audit and sync settings of RHVM
52.45 Create OpenStack-based cloud platform
52.46 Update OpenStack-based cloud platform
52.47 Delete OpenStack-based cloud platform
52.48 Sync data of OpenStack-based cloud platform
52.49 Update auto audit and sync settings of OpenStack-based cloud platform
52.50 Audit data of OpenStack-based cloud platform
52.60 Check southbound device state upon router interface deletion
52.64 Check southbound device state upon QoS policy update
52.68 Check southbound device state upon floating IP update
52.72 Check southbound device state upon vPort deletion
52.73 Check southbound device state upon vPort update
52.74 Check southbound device state upon tap flow
52.79 Check southbound device state upon vNnetwork deletion
52.80 Create mirroring destination template
52.81 Update mirroring destination template
52.82 Delete mirroring destination template
52.83 Create mirroring profile
52.84 Update mirroring profile
52.85 Delete mirroring profile
52.90 Delete extended route entry
52.106 Create security group rule
52.107 Update security group rule
52.108 Delete security group rule
52.109 Create VLAN-VXLAN mapping
52.110 Delete VLAN-VXLAN mapping
52.114 Check southbound device state upon subnet deletion
52.118 Setting platform isolate state
52.126 Audit data for System Center
52.127 Sync data for System Center
52.128 Update auto audit and sync settings of System Center
52.134 Synchronized Kubernetes
54.10 Create IPsec Site Connections
54.11 Delete IPsec Site Connection
54.12 Update IPsec Site Connections
54.13 Create IPsec site connection peer CIDR
54.14 Delete IPsec site connection peer CIDR
55.35 Authenticate with vCenter
55.66 Updated the global configuration of the controller
55.76 Configured batch vSwitch deployment parameters
55.93 Update global default action
55.104 Track flow entry of IP packet
55.105 Track flow entry of ARP packet
55.107 Start synchronization to host
55.108 Start auditing OVSDB configuration on host
55.109 Start synchronization OVSDB configuration on host
55.110 Start auditing DHCP configuration on host
55.111 Start synchronization DHCP configuration to host
55.114 Create vRouter interconnection
55.115 Update vRouter interconnection
55.116 Delete vRouter interconnection
55.117 Create Layer 2 DC interconnection
55.118 Update Layer 2 DC interconnection
55.119 Delete Layer 2 DC interconnection
55.120 Create Layer 3 DC interconnection
55.121 Update Layer 3 DC interconnection
55.122 Delete Layer 3 DC interconnection
55.123 Create Layer 3 DC interconnection extra
55.124 Update Layer 3 DC interconnection extra
55.125 Delete Layer 3 DC interconnection extra
55.126 Add subnet to Layer 3 DC interconnection
55.127 Delete Layer 3 DC interconnection subnet
55.128 Upload the vSwitch license file
55.129 Updated host load limit
55.138 Update Network Cloud feature
55.139 Download audit difference
55.145 Create DHCP resource pool
55.146 Update DHCP resource pool
55.147 Delete DHCP resource pool
55.148 Add DHCP host group to DHCP resource pool
55.149 Delete DHCP host group from DHCP resource pool
55.150 Update uplink port name
55.154 Update the auto identification of vPorts without host IDs in network overlay feature
55.162 Deployed bypass link flow entries for bypass link
55.163 Audited all bypass links
55.169 Bulk create external networks
55.170 Bulk update external networks
55.171 Bulk delete external networks
55.172 Bulk export external networks
55.185 Bulk create floating IPs
55.186 Bulk update floating IPs
55.187 Bulk delete floating IPs
55.188 Bulk export floating IPs
55.189 Bulk create routing tables
55.190 Bulk update routing tables
55.191 Bulk delete routing tables
55.192 Bulk export routing tables
55.193 Update route reduction configuration
55.197 Create network ACL rule
55.198 Update network ACL rule
55.199 Delete network ACL rule
55.200 Bulk create network ACL
55.201 Bulk update network ACL
55.202 Bulk delete network ACL
55.203 Bulk export network ACL
操作日志记录的是用户进行的系统操作、配置更改等事件，例如应用操作（安装、卸载和删除应用）、用户配置等。操作日志信息包含日志的操作时间、操作描述、操作结果和失败原因等，为用户进行系统诊断和维护提供参考。
本文假设您已具备数据通信技术知识，并熟悉控制组件产品。
登录统一数字底盘页面，单击[系统>日志管理 > 操作日志列表]菜单项，进入操作日志列表页面。操作日志列表将分页显示系统生成的用户操作日志信息，如图1-1所示。
表1-1 日志字段说明
|
字段 |
描述 |
|
日期/时间 |
生成操作日志信息的日期和时间 |
|
用户名称 |
触发生成操作日志的用户名称 |
|
用户IP |
执行操作时，用户所在终端的IP地址 |
|
用户姓名 |
用户名称对应的操作员全称 |
|
组织机构 |
用户所属的组织机构名称 |
|
服务名称 |
生成操作日志的服务名称 |
|
操作结果 |
用户操作的结果，成功或失败 |
|
操作描述 |
操作日志具体内容，描述用户进行的操作事件 |
|
失败原因 |
当用户操作失败时，将显示可能的具体失败原因 |
统一数字底盘支持将操作日志通过Syslog协议发送至Syslog日志服务器。Syslog日志服务器的IP地址和端口号可以通过[系统 > 日志管理 > 日志配置 > 操作日志]页面进行设置。
缺省情况下，统一数字底盘以Syslog协议发送的操作日志信息格式如下：
<PRI>TIMESTAMP Hostname Origin/severity/Keywords CONTENT
表1-2 Syslog日志字段说明
|
字段 |
描述 |
|
<PRI> |
优先级标识符，优先级的计算公式为：facility×8＋severity · facility表示Syslog定义的程序模块，目前SNA Center发送Syslog日志的facility一般为user-level，取值为1 · severity表示Syslog协议定义的日志严重等级，具体说明请参见表1-4 |
|
TIMESTAMP |
时间戳记录了日志信息产生的时间，方便用户查看和定位操作事件 |
|
Hostname |
生成该日志信息的容器名称 |
|
Origin |
生成该操作日志信息的业务模块的名称 |
|
severity |
SNA Center定义的操作日志信息的等级，具体说明请参见表1-5，该等级与Syslog协议定义的日志严重等级之间的对应关系如表1-6所示 |
|
Keywords |
关键字，本字段为该日志信息的概述，用于搜索或助记 |
|
CONTENT |
该日志的具体内容，格式如下： -Module="模块名称"-UserIp="用户IP"-UserName="用户名称"-OperResult="操作结果"-Reason="失败原因" |
表1-3列出了可能生成操作日志信息的业务模块。
|
业务模块名称 |
说明 |
|
Auto Deployment |
新建Fabric模块 |
|
BGP |
BGP模块 |
|
BSM |
裸金属模块 |
|
CLOSE_LOOP |
闭环控制模块 |
|
CON_AUTH |
认证管理模块 |
|
CON_CERTM |
证书管理模块 |
|
CON_LISTENER |
监听器模块 |
|
CON_NetworkMonitor |
网络健康监控模块 |
|
CON_OPENFLOW |
OpenFlow模块 |
|
CON_REGION |
Region模块 |
|
CON_ROUTERCONFIGS |
路由配置模块 |
|
CON_SNMP |
SNMP模块 |
|
CON_SYSTEM |
系统管理模块 |
|
CON_TEAM |
集群模块 |
|
CON_TOPOLOGY |
拓扑管理模块 |
|
CON_USER |
用户管理模块 |
|
DataCheck |
数据检查模块 |
|
DNEC |
DNEC模块 |
|
Fabric |
Fabric模块 |
|
FWaaS |
防火墙服务模块 |
|
Global |
全局配置模块 |
|
IDM |
综合部署模块 |
|
IW |
智能向导入口模块 |
|
LBaaS |
负载均衡服务模块 |
|
NBAC |
NBAC模块 |
|
NEM |
承载网络模块 |
|
NEYANGM |
网元YANG Manager模块 |
|
NGFWM |
NGFW Manager模块 |
|
OAM |
OAM模块 |
|
RCAM |
资源接入模板模块 |
|
SEERENGINE |
SEERENGINE模块 |
|
ServiceChain |
服务链模块 |
|
SSLVPNaaS |
SSL VPN服务模块 |
|
Tenant |
租户管理模块 |
|
TPaaS |
第三方服务模块 |
|
TPFW |
第三方防火墙模块 |
|
VMM |
云对接模块 |
|
VPNaaS |
IPsec VPN服务模块 |
|
VSM |
虚拟网络模块 |
|
ROCE_NETWORK |
ROCENETWORK模块 |
Syslog协议定义的日志严重等级如表1-4所示，各等级的严重性依照数值从0～7依次降低。
表1-4 Syslog日志严重等级说明
|
级别 |
严重等级 |
描述 |
|
0 |
Emergency |
表示紧急信息，可能导致系统不可用 |
|
1 |
Alert |
表示必须立即修复的状态 |
|
2 |
Critical |
表示严重信息 |
|
3 |
Error |
表示错误信息 |
|
4 |
Warning |
表示警告信息 |
|
5 |
Notice |
表示正常出现但是重要的信息 |
|
6 |
Informational |
表示需要记录的通知信息 |
|
7 |
Debug |
表示调试过程产生的信息 |
控制组件定义的操作日志信息的等级如表1-5所示。
|
级别 |
严重等级 |
描述 |
|
0 |
Info |
操作成功时，操作日志信息的级别为Info，表示该日志为需要记录的通知信息 |
|
1 |
Warning |
操作失败时，操作日志信息的级别为Warning，表示该日志为警告信息 |
控制组件定义的操作日志信息的等级与Syslog协议定义的日志严重等级之间的对应关系如表1-6所示。
表1-6 日志等级对应关系
|
控制组件定义的操作日志信息等级 |
Syslog协议定义的日志严重等级 |
|
0 |
6 |
|
1 |
4 |
本文将操作日志信息按照业务模块分类，以表格的形式对日志信息进行介绍。有关表中各项的含义请参考表1-7。
|
表项 |
说明 |
举例 |
|
关键字 |
日志信息的概述，用于搜索或助记 |
UPLOAD_APP_OP |
|
日志内容 |
显示日志信息的具体内容 |
Uploaded application: $1. |
|
参数解释 |
按照参数在日志中出现的顺序对参数进行解释 参数顺序用“$数字”表示，例如“$1”表示在该日志中出现的第一个参数 |
$1：应用的安装包名称 |
|
举例 |
日志信息举例 |
Uploaded application: arp-2156.zip. |
|
日志说明 |
描述日志所表达的操作事件 |
用户进行了上传应用的操作 |
|
失败原因 |
列举操作失败时可能的原因 |
当操作失败时，可能的原因如下： · Unsigned or untrusted jars contained within：JAR包签名失败或应用程序包含不信任的JAR包 · The application already exists：相同名称的应用程序已存在 |
本节介绍ADUN模块输出的操作日志信息。
|
关键字 |
CREATE_ADUN_TASK_OP |
|
日志内容 |
Created network change simulation task: $1. |
|
参数解释 |
$1：网络变更推演任务信息 |
|
举例 |
Created network change simulation task: { ID:[ c352f537-ad49-48eb-ab05-1c6b8cb92233] State: [init] Fabric ID: [a321d537-ad49-48eb-ab05-1c6b8cb95566] Fabric Name: [fabric01] }. |
|
日志说明 |
用户创建了一个网络变更推演任务 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · Database access errors：数据库访问异常 · The specified resource already exists：指定的资源已经存在 |
|
关键字 |
DELETE_ADUN_TASK_OP |
|
日志内容 |
Deleted network change simulation task: $1 |
|
参数解释 |
$1：网络变更推演任务的UUID |
|
举例 |
Deleted network change simulation task: [ c352f537-ad49-48eb-ab05-1c6b8cb92233] |
|
日志说明 |
用户删除了指定的网络变更推演任务 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · Database access errors：数据库访问异常 · You cannot perform this operation in the current task state：当前任务状态下，无法进行该操作 |
|
关键字 |
BEGAN_COLLECT_INTENT_OP |
|
日志内容 |
Began collecting intent: $1 |
|
参数解释 |
$1：网络变更推演任务信息 |
|
举例 |
Began collecting intent: { ID:[ c352f537-ad49-48eb-ab05-1c6b8cb92233] State: [collectintent] Fabric ID: [a321d537-ad49-48eb-ab05-1c6b8cb95566] Fabric Name: [fabric01] }. |
|
日志说明 |
网络变更推演任务进入变更意图采集状态，完成变更意图采集相关数据表的初始化 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · Database access errors：数据库访问异常 · You cannot perform this operation in the current task state：当前任务状态下，无法进行该操作 |
|
关键字 |
BUILT_SIMULATION_NETWORK_OP |
|
日志内容 |
Built simulation network: $1 |
|
参数解释 |
$1：网络变更推演任务信息 |
|
举例 |
Built simulation network: { ID:[ c352f537-ad49-48eb-ab05-1c6b8cb92233] State: [buildingnetwork] Fabric ID: [a321d537-ad49-48eb-ab05-1c6b8cb95566] Fabric Name: [fabric01] }. |
|
日志说明 |
网络变更推演任务进入构建仿真网络状态，进行构建仿真网络和状态更新操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · Database access errors：数据库访问异常 |
|
关键字 |
LOAD_INTENT_OP |
|
日志内容 |
Loaded intent: $1 |
|
参数解释 |
$1：网络变更推演任务信息 |
|
举例 |
Loaded intent: { ID:[ c352f537-ad49-48eb-ab05-1c6b8cb92233] State: [loadingintent] Fabric ID: [a321d537-ad49-48eb-ab05-1c6b8cb95566] Fabric Name: [fabric01] }. |
|
日志说明 |
用户进行了加载变更意图并更新状态的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · Database access errors：数据库访问异常 |
|
关键字 |
ADJUST_INTENT_OP |
|
日志内容 |
Adjusted intent: $1 |
|
参数解释 |
$1：网络变更推演任务信息 |
|
举例 |
Adjusted intent: { ID:[ c352f537-ad49-48eb-ab05-1c6b8cb92233] State: [unloadingintent] Fabric ID: [a321d537-ad49-48eb-ab05-1c6b8cb95566] Fabric Name: [fabric01] }. |
|
日志说明 |
用户进行了调整变更意图并更新状态的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · Database access errors：数据库访问异常 |
|
关键字 |
START_UNDERLAY_SIMULATION_OP |
|
日志内容 |
Started underlay simulation: $1 |
|
参数解释 |
$1：网络变更推演任务信息 |
|
举例 |
Started underlay simulation: { ID:[ c352f537-ad49-48eb-ab05-1c6b8cb92233] State: [underlaysimulating] Fabric ID: [a321d537-ad49-48eb-ab05-1c6b8cb95566] Fabric Name: [fabric01] }. |
|
日志说明 |
用户进行了启动Underlay仿真并更新状态的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · Database access errors：数据库访问异常 |
|
关键字 |
START_OVERLAY_SIMULATION_OP |
|
日志内容 |
Started overlay simulation: $1 |
|
参数解释 |
$1：网络变更推演任务信息 |
|
举例 |
Started overlay simulation: { ID:[ c352f537-ad49-48eb-ab05-1c6b8cb92233] State: [overlaysimulating] Fabric ID: [a321d537-ad49-48eb-ab05-1c6b8cb95566] Fabric Name: [fabric01] }. |
|
日志说明 |
用户进行了启动Overlay仿真并更新状态的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · Database access errors：数据库访问异常 |
|
关键字 |
MANUALLY_CREAT_LINK_OP |
|
日志内容 |
Manually created link: $1 |
|
参数解释 |
$1：手动增加的链路的信息 |
|
举例 |
Manually created link: { ID:[ c352f537-ad49-48eb-ab05-1c6b8cb92233] Local Device IP: [192.168.1.1] Local Interface: [WGE1/0/5] Remote Device IP: [192.168.1.2] Remote Interface: [WGE1/0/10] Status: [active] Source: [add] Local CMD: [*****] Remote CMD: [*****] }. |
|
日志说明 |
用户进行了手动增加链路的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · Database access errors：数据库访问异常 · You cannot perform this operation in the current task state：当前任务状态下，无法进行该操作 · The local device is inactive：本端设备处于Inactive状态 · The remote device is inactive：对端设备处于Inactive状态 · The local interface is in use：本端接口已被占用 · The remote interface is in use：对端接口已被占用 |
|
关键字 |
UPDATE_ADUN_LINK_OP |
|
日志内容 |
Updated link configuration: $1 |
|
参数解释 |
$1：链路信息 |
|
举例 |
Updated link configuration: { ID:[ c352f537-ad49-48eb-ab05-1c6b8cb92233] Local Device IP: [192.168.1.1] Local Interface: [WGE1/0/5] Remote Device IP: [192.168.1.2] Remote Interface: [WGE1/0/10] Status: [active] Source: [modify] Local CMD: [*****] Remote CMD: [*****] }. |
|
日志说明 |
用户进行了修改链路配置的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · Database access errors：数据库访问异常 · You cannot perform this operation in the current task state：当前任务状态下，无法进行该操作 · The specified link does not exist：指定的链路不存在 · The link has been modified. To modify it again, please first restore it to the original configuration：链路仅允许被修改一次，如需再次修改，请先恢复为初始配置 · The link is active：该链路已经为连接状态 · The local interface and the peer interface have not changed, and the link config update is not supported：本端接口和对端接口没有变化，不支持更新链路配置 · The local interface is in use：本端接口已被占用 · The remote interface is in use：对端接口已被占用 |
|
关键字 |
RESET_ADUN_LINK_OP |
|
日志内容 |
Reset link configuration: $1 |
|
参数解释 |
$1：链路信息 |
|
举例 |
Reset link configuration: { ID:[ c352f537-ad49-48eb-ab05-1c6b8cb92233] Local Device IP: [192.168.1.1] Local Interface: [WGE1/0/5] Remote Device IP: [192.168.1.2] Remote Interface: [WGE1/0/10] Status: [active] Source: [original] Local CMD: [*****] Remote CMD: [*****] }. |
|
日志说明 |
用户对指定链路进行了恢复初始配置的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · Database access errors：数据库访问异常 · You cannot perform this operation in the current task state：当前任务状态下，无法进行该操作 · The specified link does not exist：指定的链路不存在 · The link has not been modified. You cannot restore it to the original configuration：链路未被修改过，不支持恢复为初始配置 |
|
关键字 |
DELETE_MANUALLY_ADUN_LINK_OP |
|
日志内容 |
Deleted manually added link: $1 |
|
参数解释 |
$1：手工增加的链路的UUID |
|
举例 |
Deleted manually added link: [ c352f537-ad49-48eb-ab05-1c6b8cb92233] |
|
日志说明 |
用户进行了删除手工增加的链路的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · Database access errors：数据库访问异常 · You cannot perform this operation in the current task state：当前任务状态下，无法进行该操作 · The specified link does not exist：指定的链路不存在 |
|
关键字 |
UPDATE_ADUN_DEVICE_OP |
|
日志内容 |
Updated device configuration: $1 |
|
参数解释 |
$1：设备信息 |
|
举例 |
Updated device configuration: { ID:[ c352f537-ad49-48eb-ab05-1c6b8cb92233] Device IP: [192.168.1.1] Device Name: [deviceName] Role: [DTN_SPINE] Status: [Active] Type: [DTN_GW] Config: [*****] }. |
|
日志说明 |
用户进行了修改设备配置、设备上电或设备下电的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · Database access errors：数据库访问异常 · You cannot perform this operation in the current task state：当前任务状态下，无法进行该操作 · The specified device does not exist：指定的设备不存在 · You cannot modify the configuration of the device, because it is inactive：Inactive状态的设备不允许修改其配置 · The device's configuration has been modified. To power off it, please first restore it to the original configuration：指定设备已被修改配置，如需下电，请先恢复为初始配置 · The specified device is already inactive：指定的设备已处于Inactive状态 · The specified device is already active：指定的设备已处于Active状态 |
|
关键字 |
RESET_ADUN_DEVICE_OP |
|
日志内容 |
Reset device configuration: $1 |
|
参数解释 |
$1：设备信息 |
|
举例 |
Reset device configuration: { ID:[ c352f537-ad49-48eb-ab05-1c6b8cb92233] Device IP: [192.168.1.1] Device Name: [deviceName] Role: [DTN_SPINE] Status: [Active] Type: [DTN_GW] Config: [*****] }. |
|
日志说明 |
用户对指定设备进行了恢复初始配置的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · Database access errors：数据库访问异常 · You cannot perform this operation in the current task state：当前任务状态下，无法进行该操作 |
|
关键字 |
RESET_ADUN_INTENT_OP |
|
日志内容 |
Reset intent. |
|
参数解释 |
无 |
|
举例 |
Reset intent. |
|
日志说明 |
用户进行了重置变更意图的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · Database access errors：数据库访问异常 · You cannot perform this operation in the current task state：当前任务状态下，无法进行该操作 |
本节介绍网络业务向导模块（又称为应用上下线模块）输出的操作日志信息。
|
关键字 |
ACTION_CREATE_SECURITY_AREA |
|
日志内容 |
Added security zone:$1. |
|
参数解释 |
$1：安全分区的配置信息 |
|
举例 |
Added security zone: { "name": "area", "appId": "dac0ed95-12a5-49f8-bad7-4635a05adcd5", "deployFabricIds": ["45ab4561-09d6-4a89-8287-27c28054b2e1"], "cidrList": [{ "id": "06111b01-16ad-4da0-8255-208b12db2e8b", "ipVersion": "4", "cidr": "16.1.1.1/16", "mask": 16, "securityAreaId": "0f0ce03d-d40a-4a1b-b745-cb1d9944f3ac" }] } |
|
日志说明 |
用户进行了增加安全分区的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request body cannot be empty：请求体不能为空 · Please specify the application ID (appID)：应用ID不能为空 · Invalid application ID (appId)：应用ID无效 · The name is required：名称不能为空 · The name can be up to 32 characters, case sensitive：名称最长32位字符，区分大小写 · Please specify the deployFabricIds value for the security zone：fabric不能为空 · Invalid fabric ID：fabric ID无效 · The deployFabricIds value for a fabric must be unique：指定的fabric 重复 · Please specify a minimum of one CIDR for the security zone：网段资源池列表（cidrList）不能为空 · Please specify an IP version：IP版本不能为空 · Please specify a mask：mask不能为空 · Please specify a CIDR：CIDR不能为空 · Invalid IP version：IP版本无效 · Invalid CIDR：CIDR无效 · Invalid mask：Mask无效 · Make sure the CIDRs do not overlap：CIDR重叠 · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · A security zone already exists with the specified name：指定名称的安全分区已经存在 · The specified fabric does not exist：指定的fabric 不存在 · The CIDR for this security zone overlaps with the CIDR for another security zone：当前安全分区的CIDR和其他安全分区的cidr重叠 · Failed to add the security zone：新增安全分区失败 |
|
关键字 |
ACTION_UPDATE_SECURITY_AREA |
|
日志内容 |
Edited security zone:$1. |
|
参数解释 |
$1：安全分区的配置信息 |
|
举例 |
Edited security zone: { "name": "area11", "deployFabricIds": ["45ab4561-09d6-4a89-8287-27c28054b2e1"], "cidrList": [{ "id": "06111b01-16ad-4da0-8255-208b12db2e8b", "ipVersion": "4", "cidr": "16.1.1.1/16", "mask": 16 }, { "id": "623ee2a3-7dfe-40d2-9041-d7067fd0eeef", "ipVersion": "4", "cidr": "17.1.1.1/16", "mask": 16 }] } |
|
日志说明 |
用户进行了修改安全分区的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request body cannot be empty：请求体不能为空 · Invalid UUID：无效的UUID · The specified security zone does not exist：安全分区不存在 · The specified security zone and application do not match：安全分区不属于指定的应用 · The specified CIDR has been used for a service and cannot be deleted：指定的CIDR已经被服务使用，无法进行删除 · Failed to update the security zone：修改安全分区失败 · The input params cannot be empty： 参数不能为空 · The application does not exist： 指定的应用不存在 · AppOnline status in db is illegal： 状态机功能异常 · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · A security zone already exists with the specified name：指定名称的安全分区已经存在 · The CIDR for this security zone overlaps with the CIDR for another security zone：当前安全分区的CIDR和其他安全分区的CIDR重叠 · Invalid CIDR： CIDR无效 · The name is required：名称不能为空 · The name can be up to 32 characters, case sensitive：名称最长32位字符，区分大小写 · Please specify the deployFabricIds value for the security zone：fabric不能为空 · Invalid fabric ID：fabric ID无效 · The deployFabricIds value for a fabric must be unique：指定的fabric 重复 · Please specify a minimum of one CIDR for the security zone：网段资源池列表（cidrList）不能为空 · Please specify an IP version：IP版本不能为空 · Please specify a mask：mask不能为空 · Please specify a CIDR：CIDR不能为空 · Invalid IP version：IP版本无效 · Invalid mask：Mask无效 · Make sure the CIDRs do not overlap：CIDR重叠 · The specified fabric does not exist：指定的fabric 不存在 |
|
关键字 |
ACTION_DELETED_SECURITY_AREA |
|
日志内容 |
Deleted security zone:$1. |
|
参数解释 |
$1：安全分区的ID |
|
举例 |
Deleted security zone:0f0ce03d-d40a-4a1b-b745-cb1d9944f3ac |
|
日志说明 |
用户进行了删除安全分区的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid UUID：无效的UUID · The input params cannot be empty： 参数不能为空 · The application does not exist： 指定的应用不存在 · AppOnline status in db is illegal： 状态机功能异常 · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · The specified security zone does not exist：安全分区不存在 · The security zone contains services：安全分区下存在服务资源 · Failed to delete the security zone：删除安全分区失败 |
|
关键字 |
ACTION_CREATE_SERVICE |
|
日志内容 |
Added service:$1. |
|
参数解释 |
$1：服务的配置信息 |
|
举例 |
Added service: { "id": "8cc2758e-cb9d-4a1d-be7a-848913eb017b", "name": "service", "description": "", "instanceNum": 11, "ipVersion": "4", "cidr": "1.1.0.0/16", "mappings": [{ "id": "625b12b9-f1b3-4e77-bde2-d568fae543eb", "vlan": "1211", "devices": [{ "id": "41ef609b-f419-4341-8407-86e64c76f26f", "ports": ["Twenty-FiveGigE1/0/9"] }] }], "securityAreaId": "5e596adc-9f9d-42be-a810-90d66fa00a85" } |
|
日志说明 |
用户进行了新增服务的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid UUID：无效的UUID · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · The input params cannot be empty：参数不能为空 · The application does not exist：指定的应用不存在 · AppOnline status in db is illegal：状态机功能异常 · The request body cannot be empty：请求体不能为空 · Please specify a service name：服务名称不能为空 · The service name can be up to 32 characters, case sensitive：名称最长32位字符，区分大小写 · The description can be up to 255 characters：描述最长255位字符 · Please specify the UUID of the security zone in the securityAreaId field：securityAreaId字段中的安全分区UUID不能为空 · Invalid security zone UUID for the securityAreaId field：securityAreaId字段中的安全分区UUID无效 · Please specify an IP version in the ipVersion field for the service：IP版本不能为空 · Invalid service IP version：IP版本无效 · Please specify the number of service instances：实例数不能为空 · The number of instances specified in the instanceNum field is out of the range (1 to 2000)：实例数超出取值范围 · The cidr field for a service cannot be empty：为服务分配的CIDR不能为空 · Invalid service CIDR：为服务分配的CIDR无效 · The number of instances (instanceNum) exceeds the number of assignable addresses in the subnet：实例数超过网段可分配地址个数 · Please specify a minimum of one mapping in the mappings element：上线位置信息不能为空 · The devices element cannot be empty：devices字段不能为空 · The devices element contains duplicate information：指定的设备信息重复 · Invalid device ID value：无效的设备ID · Please specify a minimum of one port on the device：设备端口不能为空 · Make sure the specified ports are unique：设备端口重复 · VLANs for the service overlap with VLANs planned or deployed for another service on the specified interface：指定接口上此服务的VLAN映射与另一服务已经规划或下发的VLAN映射重叠 · The specified security zone and application do not match：安全分区不属于指定的应用 · A service already exists with the same name：指定名称的服务已经存在 · The CIDR for the service is not in the list of CIDRs for the security zone：指定的服务CIDR不在服务所属安全分区的网段资源池内 · The CIDR for the service is used by another service：服务CIDR已经被使用 · A nonexistent device port was specified：设备端口不存在 · Failed to add the service：新增服务失败 · No CIDRs are available for this IP version：当前IP版本没有可用的CIDR · The CIDR for the service is not within the scope of CIDRs for the security zone：为服务分配的CIDR不在安全分区关联的CIDR范围内 · The DHCPv6 value can be set only to true or false：服务的IP版本包含IPv6时，DHCPv6取值仅支持true和false · IPv6 address configuration mode can be set only to null (the default), slaac, dhcpv6-stateful, or dhcpv6-stateless：服务的IP版本包含IPv6时，IPv6地址模式取值仅支持null（缺省）、slaac、dhcpv6-stateful和dhcpv6-stateless · You must enable DHCPv6 if slaac, dhcpv6-stateful, or dhcpv6-stateless is used for IPv6 address configuration：IPv6地址模式为slaac、dhcpv6-stateful或dhcpv6-stateless时，必须启用DHCPv6 · If SLAAC or stateless DHCPv6 is used for IPv6 address configuration, the mask length for IPv6 CIDR subnetting must be set to 64 bits：IPv6地址模式为SLAAC或无状态DHCPv6类型时，IPv6网段掩码必须为64位 |
|
关键字 |
ACTION_UPDATE_SERVICE |
|
日志内容 |
Edited service:$1. |
|
参数解释 |
$1：服务的配置信息 |
|
举例 |
Edited service: { "id": "8cc2758e-cb9d-4a1d-be7a-848913eb017b", "name": "service1", "description": "dsad", "instanceNum": 111, "ipVersion": "4", "cidr": "1.1.0.0/16", "mappings": [{ "id": "625b12b9-f1b3-4e77-bde2-d568fae543eb", "vlan": "1211", "devices": [{ "id": "41ef609b-f419-4341-8407-86e64c76f26f", "ports": ["Twenty-FiveGigE1/0/9"] }] }, { "id": "49c2cbfa-cc29-44ca-bc7e-3092d03c82a4", "vlan": "1213", "devices": [{ "id": "41ef609b-f419-4341-8407-86e64c76f26f", "ports": ["Twenty-FiveGigE1/0/8"] }] }], "securityAreaId": "5e596adc-9f9d-42be-a810-90d66fa00a85", "appId": "dac0ed95-12a5-49f8-bad7-4635a05adcd5" } |
|
日志说明 |
用户进行了修改服务的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid UUID：无效的UUID · The input params cannot be empty：参数不能为空 · The application does not exist：指定的应用不存在 · AppOnline status in db is illegal：状态机功能异常 · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · The service does not exist：服务不存在 · The service does not belong to the application：服务不属于该应用 · VLANs for the service overlap with VLANs planned or deployed for another service on the specified interface：指定接口上此服务的VLAN映射与另一服务已经规划或下发的VLAN映射重叠 · A service already exists with the same name：指定名称的服务已经存在 · The specified security zone does not exist：安全分区不存在 · The CIDR for the service is not within the scope of CIDRs for the security zone：为服务分配的CIDR不在安全分区关联的CIDR范围内 · The CIDR for the service is used by another service：服务CIDR已经被使用 · Failed to edit the service：修改服务失败 · No CIDRs are available for this IP version：当前IP版本没有可用的CIDR · Make sure the specified ports are unique：设备端口重复 · The devices element contains duplicate information：指定的设备信息重复 · Please specify a minimum of one port on the device：设备端口不能为空 · A nonexistent device port was specified：设备端口不存在 · The devices element cannot be empty：devices字段不能为空 · Invalid device ID value：无效的设备ID · The CIDR for the service is not in the list of CIDRs for the security zone：指定的服务CIDR不在服务所属安全分区的网段资源池内 · Please specify a minimum of one mapping in the mappings element：上线位置信息不能为空 · The cidr field for a service cannot be empty：为服务分配的CIDR不能为空 · Services in a service-service access relationship must have the same IP version setting：服务间互访关系两端的IP版本配置必须保持一致 · When you edit the configuration for the service in a service-exNetwork access relationship, please make sure the external network has subnets of the same IP versions as those specified for the service：修改服务和外部网络互访关系中服务侧的配置时，请保证服务的IP版本与外网子网的IP版本兼容 · The DHCPv6 value can be set only to true or false：服务的IP版本包含IPv6时，DHCPv6取值仅支持true和false · IPv6 address configuration mode can be set only to null (the default), slaac, dhcpv6-stateful, or dhcpv6-stateless：服务的IP版本包含IPv6时，IPv6地址模式取值仅支持null（缺省）、slaac、dhcpv6-stateful和dhcpv6-stateless · You must enable DHCPv6 if slaac, dhcpv6-stateful, or dhcpv6-stateless is used for IPv6 address configuration：IPv6地址模式为slaac、dhcpv6-stateful或dhcpv6-stateless时，必须启用DHCPv6 · If SLAAC or stateless DHCPv6 is used for IPv6 address configuration, the mask length for IPv6 CIDR subnetting must be set to 64 bits：IPv6地址模式为SLAAC或无状态DHCPv6类型时，IPv6网段掩码必须为64位 |
|
关键字 |
ACTION_DELETED_SERVICE |
|
日志内容 |
Deleted service:$1. |
|
参数解释 |
$1：服务的ID |
|
举例 |
Deleted service:8cc2758e-cb9d-4a1d-be7a-848913eb017b |
|
日志说明 |
用户进行了删除服务的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid UUID：无效的UUID · The input params cannot be empty：参数不能为空 · The application does not exist：指定的应用不存在 · AppOnline status in db is illegal：状态机功能异常 · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · The service does not exist：服务不存在 · The service does not belong to the application：服务不属于指定的应用 · The service has been bound to an access relationship：服务存在互访关系 · Failed to delete the service：删除服务失败 |
|
关键字 |
ACTION_ADD_EXTERNAL_NETWORK |
|
日志内容 |
Added external network :$1. |
|
参数解释 |
$1：外部网络的配置信息 |
|
举例 |
Added external network: { "id": "2494c1f4-2fba-45e1-b321-18b2fbf95bda", "appId": "dac0ed95-12a5-49f8-bad7-4635a05adcd5", "externalNetworkId": "ce0cd9f8-5907-4565-8b2a-b80856c114fe", "gatewayIds": ["127ba629-4826-4a5d-804a-c49d2d7df362", "3af43a77-5bc5-443e-86d8-c9a9ce0562d0"] } |
|
日志说明 |
用户进行了添加外部网络的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request body cannot be empty：请求体不能为空 · Failed to add the external network, because an invalid application ID was specified：应用ID不合法，外部网络添加失败 · The input params cannot be empty：参数不能为空 · The application does not exist：指定的应用不存在 · AppOnline status in db is illegal：状态机功能异常 · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · Failed to add the external network, because an invalid external network ID was specified：外部网络ID不合法，外部网络添加失败 · Failed to add the external network, because an invalid gateway ID was specified：出口网关ID不合法，外部网络添加失败 · Invalid JSON format：JSON格式错误 · Failed to add the external network, because the border gateway bound to it does not belong to the current tenant：添加外部网络失败，外部网络绑定的出口网关不属于当前租户 · The specified external network does not exist：指定的外部网络不存在 · The operating mode of the external network is not indirectly connected：外部网络的工作模式不是共享型 · A border gateway has been bound to the external network：外部网络已绑定出口网关The border gateway bound to the external network does not belong to the current tenant：外部网络绑定的出口网关不属于当前租户 · Failed to add the external network, because the border gateway bound to it does not belong to the current tenant：添加外部网络失败，外部网络绑定的出口网关不属于当前租户 · A nonexistent gateway was specified：指定的出口网关不存在 · Failed to create the external network：创建外部网络失败 |
|
关键字 |
ACTION_MODIFY_EXTERNAL_NETWORK |
|
日志内容 |
Modified external network:$1. |
|
参数解释 |
$1：外部网络的配置信息 |
|
举例 |
Modified external network: { "exNetworkId": "ce0cd9f8-5907-4565-8b2a-b80856c114fe", "gatewayIds": ["127ba629-4826-4a5d-804a-c49d2d7df362"] } |
|
日志说明 |
用户进行了修改外部网络的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request body cannot be empty：请求体不能为空 · The application does not exist：指定的应用不存在 · The input params cannot be empty：参数不能为空 · The application does not exist：指定的应用不存在 · AppOnline status in db is illegal：状态机功能异常 · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · A nonexistent gateway was specified：出口网关ID不合法，外部网络添加失败 · Invalid JSON format：JSON格式错误 · The specified external network does not exist：指定的外部网络不存在 · The operating mode of the external network is not indirectly connected：外部网络的工作模式不是共享型 · A border gateway has been bound to the external network：外部网络已绑定出口网关 · The border gateway bound to the external network does not belong to the current tenant：外部网络绑定的出口网关不属于当前租户 · Failed to update the external network：更新外部网络失败 · You cannot change the border gateway, because itsassociated FW resource is being used for an access relationship：出口网关关联的FW资源被互访关系使用，不允许进行网关修改 |
|
关键字 |
ACTION_DELETE_NETWORK |
|
日志内容 |
Removed external network |
|
参数解释 |
无 |
|
举例 |
Removed external network |
|
日志说明 |
用户将外部网络从应用中删除 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request body cannot be empty：请求体不能为空 · The application does not exist：指定的应用不存在 · The input params cannot be empty：参数不能为空 · The application does not exist：指定的应用不存在 · AppOnline status in db is illegal：状态机功能异常 · The specified resource does not exist：指定的资源不存在 · An access relationship with the external network already exists：外部网络已存在互访关系 · Failed to delete the external network：删除外部网络失败 |
|
关键字 |
ACTION_ADD_CONNECTION |
|
日志内容 |
Added access relationship :$1. |
|
参数解释 |
$1：互访关系的配置信息 |
|
举例 |
Added access relationship: { "peerId": "9a50a313-7e53-4aab-8d27-e72abecf5f89", "fwResources": "", "appId": "04bf6fdb-bcd6-4232-ad8e-a48366a1c862", "name": "1", "action": "permit", "id": "9af1885d-8369-41b9-b47b-e649a45ab0db", "peerType": "service", "localId": "71ef33b2-0f28-4f55-9f27-67bae84000a9", "addValue": "false", "localType": "externalNetwork" } |
|
日志说明 |
用户进行了增加互访关系的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request body cannot be empty：请求体不能为空 · Invalid UUID：无效的UUID · The input params cannot be empty：参数不能为空 · The application does not exist：指定的应用不存在 · AppOnline status in db is illegal：状态机功能异常 · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · Please specify a name：名称不能为空The name can be up to 32 characters, case sensitive：名称最长32位字符，区分大小写 · The specified name has been used：指定名称已存在 · The value-added services option (addValue) cannot be empty：增值服务开关取值不能为空 · The value-added services option (addValue) cannot be empty：增值服务开关取值不能为空 · Please specify firewall resources：FW资源不能为空 · The firewall service (fwResource) field must be empty when the value-added services option (addValue) field is set to off (false)：增值服务开关（addValue）如果为关闭（false），则防火墙资源（fwResource）字段不允许有值 · Invalid type of access relationship. Only services can establish access relationships with an external network：互访类型不合法，只有服务能与外部网络建立互访关系 · Invalid type of access relationship. The two ends of an access relationship cannot be both external networks：互访类型不合法。互访关系的两端不能同时为外部网络 · Invalid action type. The action can only be permit or deny：动作类型只能为permit（放通），deny（拒绝） · The two ends already have an access relationship：本端和对端已存在互访关系 · You must bind border gateways to services at the two ends of an access relationship with value-added services enabled：跨安全分区的服务互访关系开启增值服务时，互访关系两端的服务必须绑定出口网关 · You must bind border gateways to services at the two ends of an access relationship with value-added services enabled：跨安全分区的服务互访关系两端的增值服务开关设置需保持一致一个FW · The value-added services option must have the same setting for the service-exNetwork access relationships established for services in the same security zone：同一安全分区内的不同服务和外部网络建立的互访关系，增值服务开关必须一致 · The services in the same security zone can establish access relationships only with the same external network：同一安全分区内的不同服务只能和同一外部网络建立互访关系 · If two security zones have a service-service access relationship with value-added services enabled, you must select the same firewall service for all access relationships with value-added services enabled in these two zones：跨安全分区的服务间互访关系如果开启增值服务，则这两个安全分区所有开启增值服务的互访关系选择的FW服务必须相同 · Failed to create the access relationship：创建互访关系失败 · A service can establish access relationship with only one external network：一个服务只能与一个外部网络建立互访关系 · The specified FW resource must be the one assigned to thespecified border gateway：FW资源只能设置为与指定出口网关关联的FW资源 |
|
关键字 |
ACTION_MODIFY_CONNECTION |
|
日志内容 |
Modified access relationship |
|
参数解释 |
无 |
|
举例 |
Modified access relationship |
|
日志说明 |
用户进行了修改互访关系的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request body cannot be empty：请求体不能为空 · The input params cannot be empty：参数不能为空 · The application does not exist：指定的应用不存在 · AppOnline status in db is illegal：状态机功能异常 · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · Invalid UUID：无效的UUID · Please specify a name：名称不能为空The name can be up to 32 characters, case sensitive：名称最长32位字符，区分大小写 · The specified name has been used：指定名称已存在 · The value-added services option (addValue) cannot be empty：增值服务开关取值不能为空 · The value-added services option (addValue) cannot be empty：增值服务开关取值不能为空 · Please specify firewall resources：FW资源不能为空 · The firewall service (fwResource) field must be empty when the value-added services option (addValue) field is set to off (false)：增值服务开关（addValue）如果为关闭（false），则防火墙资源（fwResource）字段不允许有值 · Invalid type of access relationship. Only services can establish access relationships with an external network：互访类型不合法，只有服务能与外部网络建立互访关系 · Invalid type of access relationship. The two ends of an access relationship cannot be both external networks：互访类型不合法。互访关系的两端不能同时为外部网络 · Invalid action type. The action can only be permit or deny：动作类型只能为permit（放通），deny（拒绝） · The two ends already have an access relationship：本端和对端已存在互访关系 · You must bind border gateways to services at the two ends of an access relationship with value-added services enabled：跨安全分区的服务互访关系开启增值服务时，互访关系两端的服务必须绑定出口网关 · You must bind border gateways to services at the two ends of an access relationship with value-added services enabled：跨安全分区的服务互访关系两端的增值服务开关设置需保持一致一个FW · The value-added services option must have the same setting for the service-exNetwork access relationships established for services in the same security zone：同一安全分区内的不同服务和外部网络建立的互访关系，增值服务开关必须一致 · If two security zones have a service-service access relationship with value-added services enabled, you must select the same firewall service for all access relationships with value-added services enabled in these two zones：跨安全分区的服务间互访关系如果开启增值服务，则这两个安全分区所有开启增值服务的互访关系选择的FW服务必须相同 · The services in the same security zone can establish access relationships only with the same external network：同一安全分区内的不同服务只能和同一外部网络建立互访关系 · A service can establish access relationship with only one external network：一个服务只能与一个外部网络建立互访关系 · Failed to modify the access relationship：修改互访关系失败 · The specified FW resource must be the one assigned to the specified border gateway：FW资源只能设置为与指定出口网关关联的FW资源 |
|
关键字 |
ACTION_DELETE_CONNECTION |
|
日志内容 |
Deleted access relationship |
|
参数解释 |
无 |
|
举例 |
Deleted access relationship |
|
日志说明 |
用户进行了删除互访关系的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The input params cannot be empty：参数不能为空 · The application does not exist：指定的应用不存在 · AppOnline status in db is illegal：状态机功能异常 · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · The specified access relationship does not exist：指定的互访关系不存在 · The specified access relationship cannot be associated with the application：指定的互访关系和应用关联不上 · Failed to delete the access relationship：删除互访关系失败 |
|
关键字 |
ACTION_RECOMMEND_PROGRAM |
|
日志内容 |
Solution recommendation :$1. |
|
参数解释 |
$1：应用ID |
|
举例 |
Solution recommendation : c0054fe5-6b4c-4e37-a006-b490a012b564 |
|
日志说明 |
用户进行了方案推荐的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid UUID：无效的UUID · The input params cannot be empty：参数不能为空 · The application does not exist：指定的应用不存在 · AppOnline status in db is illegal：状态机功能异常 · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · No security zone resources have been assigned to the application：当前应用下没有安全分区资源 · No service resources have been assigned to the security zone：指定的安全分区下没有服务资源 · The specified external network does not have any access relationships：指定的外部网络不存在互访关系 · Solution recommendation failed：方案推荐失败 |
|
关键字 |
ACTION_SELECT_RECOMMEND |
|
日志内容 |
Selected solution:$1. |
|
参数解释 |
$1：应用ID |
|
举例 |
Selected solution: c0054fe5-6b4c-4e37-a006-b490a012b564 |
|
日志说明 |
用户进行了方案选择的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Simulation resources are in use：仿真资源被占用 · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · Invalid UUID：无效的UUID · Solution selection failed：方案选择失败 · Internal Server Error：内部系统错误 |
|
关键字 |
ACTION_OPERATE_RESOURCE |
|
日志内容 |
Operated logical resource:$1. |
|
参数解释 |
$1：资源的配置信息 |
|
举例 |
OperateLogicResource: ResourceDTO { resourceId='f958e93b-f17b-40a4-8f0b-3e3d21440010'resourceType='firewall', requestUrl='/fw/v1.0/firewalls/', requestMethod='POST', requestParam='{ "firewall": { "name": "fw-1", "tenant_id": "bef823b4-6c98-4e62-9cb2-d2f638f78c4b", "description": "22", "shared": false, "mode": "CGSR", "forward_policy_id": null, "backward_policy_id": null, "forward_atk_policy_id": null, "backward_atk_policy_id": null, "routers": [{ "router_id": "7fb8e914-e654-4e3b-8f70-ebf125365141" }], "origin": "ApplicationOnline_04bf6fdb-bcd6-4232-ad8e-a48366a1c862" } }' } |
|
日志说明 |
用户进行了方案设计的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid UUID：无效的UUID · The input params cannot be empty：参数不能为空 · The application does not exist：指定的应用不存在 · AppOnline status in db is illegal：状态机功能异常 · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · The request body cannot be empty：请求体不能为空 · HTTP method not allowed：HTTP方法不支持 · Invalid resource type：资源类型无效 · The request URL is required：请求URL不能为空 · Invalid JSON format：JSON格式错误 · Resource ID is required：资源ID不能为空 · Simulation resources are in use：仿真资源被占用 · Invalid access relationship：非法的互访关系 · Failed to build the simulation network：构建仿真失败 · Failed to delete the simulation network：删除仿真失败 · Failed to enable simulation for the tenant：开启租户仿真失败 · Simulation resource request failed：请求仿真资源失败 · DC resource request failed：请求DC资源失败 |
|
关键字 |
DISTRIBUTION_CREATED |
|
日志内容 |
Deployed configuration:$1. |
|
参数解释 |
$1：配置下发的元素：应用上线ID、意图管理中心任务ID |
|
举例 |
Deployed configuration: { "taskId": "d784b0b4-e5d0-4c43-b573-ba268152904e", "appId": "96ce49de-0422-429d-ae80-ea43defb84e8" } |
|
日志说明 |
用户进行了配置下发的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid UUID：无效的UUID · The input params cannot be empty：参数不能为空 · The application does not exist：指定的应用不存在 · AppOnline status in db is illegal：状态机功能异常 · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · The simulation network has not been built：当前仿真网络未构建 · This operator is not the owner of the specified simulation network instance：当前仿真网络实例不属于该操作者 · Invalid JSON format：JSON格式错误 · Failed to create the intent execution task：创建意图任务失败 · Simulation resource request failed：请求仿真资源失败 · Inner error：内部系统错误 · The input params cannot be empty：参数不能为空 · No services are to be deployed：不存在未部署的业务 |
|
关键字 |
ACTION_ADD_TEMPLATE |
|
日志内容 |
Added template :$1. |
|
参数解释 |
$1：应用案例的配置信息 |
|
举例 |
Added template: { "name": "test_model1", "appId": "b49e8034-1181-4584-8841-3f0fa9fa1003" } |
|
日志说明 |
用户进行了增加意图模型案例的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request body cannot be empty：请求体不能为空 · Invalid UUID：无效的UUID · The input params cannot be empty：参数不能为空 · The application does not exist：指定的应用不存在 · AppOnline status in db is illegal：状态机功能异常 · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · Please specify a name：名称不能为空 · The name can be up to 32 characters, case sensitive：名称最长32位字符，区分大小写 · Duplicate names were specified：名称重复 · To create a template, make sure a minimum of one security zone or external network exists：至少有一个安全分区或者外部网网络才可以创建模板 |
|
关键字 |
ACTION_DELETE_TEMPLATE |
|
日志内容 |
Deleted template |
|
参数解释 |
无 |
|
举例 |
Deleted template |
|
日志说明 |
用户进行了删除意图模型案例的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The specified resource does not exist：指定资源不存在 |
|
关键字 |
ACTION_ADD_APP |
|
日志内容 |
Added application:$1 |
|
参数解释 |
应用的配置信息 |
|
举例 |
Added application: { "name": "sadfd", "tenantId": "bef823b4-6c98-4e62-9cb2-d2f638f78c4b", "templateId": "8ff46cb2-404f-4e2f-a1db-31492d2d6467" } |
|
日志说明 |
用户进行了增加应用的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request body cannot be empty：请求体不能为空 · The name is required：名称不能为空 · The maximum name length is 32 characters：名称最长32位字符 · Please specify a tenant ID in the tenantId field：租户ID不能为空 · Invalid case template ID for the templateId field：无效的模板ID · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · The specified tenant does not exist：租户不存在 · An application already exists with the specified name：指定名称的应用已经存在 · The specified case template does not exist：指定的模板不存在 · AppOnline status in db is illegal：状态机功能异常 · Failed to add the application：新增应用失败 · Please first configure a VDS for the tenant：该租户未配置VDS · The case template contains nonexistent external networks：案例模板中包含不存在的外部网络 · The case template contains border gateways that do not belong to the tenant：案例模板中包含不属于当前租户的出口网关 |
|
关键字 |
ACTION_CHANGE_APP |
|
日志内容 |
Changed provisioning for application:$1 |
|
参数解释 |
$1：应用的ID |
|
举例 |
Change provisioning for application:04bf6fdb-bcd6-4232-ad8e-a48366a1c862 |
|
日志说明 |
用户进行了应用变更的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid UUID：无效的UUID · The input params cannot be empty：参数不能为空 · The application does not exist：指定的应用不存在 · AppOnline status in db is illegal：状态机功能异常 · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · The specified resource does not exist：指定资源不存在 |
|
关键字 |
ACTION_ROLLBACK_CHANGE_APP |
|
日志内容 |
Reverted changes for application:$1 |
|
参数解释 |
$1：应用的ID |
|
举例 |
Reverted changes for application:04bf6fdb-bcd6-4232-ad8e-a48366a1c862 |
|
日志说明 |
用户进行了应用变更撤回的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid UUID：无效的UUID · The input params cannot be empty：参数不能为空 · The application does not exist：指定的应用不存在 · AppOnline status in db is illegal：状态机功能异常 · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · Simulation resources are in use：仿真资源被占用 · The specified resource does not exist：指定资源不存在 |
|
关键字 |
ACTION_OFFLINE_APP |
|
日志内容 |
Deprovisioned network for application:$1 |
|
参数解释 |
应用的ID |
|
举例 |
Deprovisioned network for application:04bf6fdb-bcd6-4232-ad8e-a48366a1c862 |
|
日志说明 |
用户进行了应用下线的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid UUID：无效的UUID · The input params cannot be empty：参数不能为空 · The application does not exist：指定的应用不存在 · AppOnline status in db is illegal：状态机功能异常 · Deprovisioning failed for the application：应用下线失败 |
|
关键字 |
ACTION_DELTED_APP |
|
日志内容 |
Deleted application:$1 |
|
参数解释 |
应用的ID |
|
举例 |
Deleted application:dac0ed95-12a5-49f8-bad7-4635a05adcd5 |
|
日志说明 |
用户进行了删除的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid UUID：无效的UUID · The input params cannot be empty：参数不能为空 · The application does not exist：指定的应用不存在 · AppOnline status in db is illegal：状态机功能异常 · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · The application does not exist：指定的应用不存在 · Failed to delete the simulation network：删除仿真网络失败 · Failed to delete the application：应用删除失败 |
|
关键字 |
ACTION_ROLLBACK_TASK |
|
日志内容 |
Intent execution task rollback:$1 |
|
参数解释 |
应用的ID |
|
举例 |
Intent execution task rollback:f83375b7-39d5-4e85-9c0f-906bd5cf13e7 |
|
日志说明 |
用户进行了应用任务回滚的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid UUID：无效的UUID · The input params cannot be empty：参数不能为空 · The application does not exist：指定的应用不存在 · AppOnline status in db is illegal：状态机功能异常 · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · No configuration record exists for the specified task：没有此任务对应的配置记录 · The specified tenant does not exist：租户不存在 · Intent execution task rollback failed：意图任务回滚失败 · The segment ID segmentID is already used：Segment ID segmentID 已经被使用 |
本节介绍BGP模块输出的操作日志信息
|
关键字 |
CREATE_BGP_CLUSTER_OP |
|
日志内容 |
Created BGP cluster: $1 |
|
参数解释 |
$1：BGP集群的信息 |
|
举例 |
Created BGP cluster: name: [BGPcluster1] member_ips: [“1.1.1.1”,”1.1.1.2”] |
|
日志说明 |
用户进行了创建BGP集群的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The BGP clusters created in bulk cannot use the same ID：批量创建BGP集群时，存在重复的UUID · The management IP is required：管理IP不能为空 · The management IP is invalid：无效的管理IP · Member IPs are required：集群成员IP不能为空 · A maximum of two member IPs are supported：集群成员IP个数最多支持2个 · The member IPs cannot be identical：集群成员IP不能重复 · The request is invalid：无效的请求 · Unknown error：未知错误 · The parameter (%s) is required：(parameters)参数为必选项 · The parameter (%s) is invalid：(parameters)参数是无效的 · The parameter (%s) can't exceed 255 characters：(parameters)参数不能超过255个字符 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · You have no privilege to perform this operation：用户无权限执行此操作 · Invalid ID：无效的ID · Please specify an integer in the range of 10 to 4095：集群探测周期的取值范围为10～4095的整数 |
|
关键字 |
UPDATE_BGP_CLUSTER_OP |
|
日志内容 |
Updated BGP cluster: $1. |
|
参数解释 |
$1：BGP集群的信息 |
|
举例 |
Updated BGP cluster: name: [BGPcluster1] member_ips: [“1.1.1.1”,”1.1.1.2”] |
|
日志说明 |
用户进行了修改BGP集群的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The management IP is required：管理IP不能为空 · The management IP is invalid：无效的管理IP · Member IPs are required：集群成员IP不能为空 · A maximum of two member IPs are supported：集群成员IP个数最多支持2个 · The member IPs cannot be identical：集群成员IP不能重复 · A minimum of one master IP is required：集群成员中必须至少包含一个Master成员IP · The request is invalid：无效的请求 · Unknown error：未知错误 · The parameter (%s) can't be modified：(parameters)参数不允许被修改 · The parameter (%s) is required：(parameters)参数为必选项 · The parameter (%s) is invalid：(parameters)参数是无效的 · The parameter (%s) can't exceed 255 characters：(parameters)参数不能超过255个字符 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · You have no privilege to perform this operation：用户无权限执行此操作 · The BGP cluster is in shared mode and has been bound to a BGP instance. You cannot change its sharing mode to exclusive：BGP集群下绑定了实例，则该集群不允许从共享切换成独享模式 · Please specify an integer in the range of 10 to 4095：集群探测周期的取值范围为10～4095的整数 |
|
关键字 |
DELETE_BGP_CLUSTER_OP |
|
日志内容 |
Deleted BGP cluster: $1 |
|
参数解释 |
$1：BGP集群的名称 |
|
举例 |
Deleted BGP cluster: 218b5f2f-e435-4365-a1ab-0eaa03b7fa19 |
|
日志说明 |
用户进行了删除指定BGP集群的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · You have no privilege to perform this operation：用户无权限执行此操作 · You cannot delete this cluster. It has been bound to a BGP instance：该集群已被BGP实例绑定，不允许删除 |
|
关键字 |
CREATE_BGP_INSTANCE_OP |
|
日志内容 |
Created BGP instance: $1 |
|
参数解释 |
$1：BGP实例的信息 |
|
举例 |
Created BGP instance: bgp_instance_name: [default] bgp_as_number: [65535] graceful_restart_timer: [15] bgp_peer_ip: [1.1.1.1] bgp_peer_as_number: [65535] graceful_restart_timer_extra: [no-limit] fabric_id: [7ffdcfab-3312-41ae-82cd-1a0547b359c1] |
|
日志说明 |
用户进行了创建BGP实例的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The BGP instances created in bulk cannot use the same ID：批量创建BGP实例时，存在重复的UUID · The BGP instance ID is invalid：无效的BGP实例ID · The BGP peer IP is invalid：无效的BGP对等体IP · The AS number is an integer in the range of 1 to 4294967295：AS号取值范围为1~4294967295的整数 · The BGP instance name is required：BGP实例名称不能为空 · The fabric ID is required：Fabric ID不允许为空 · The fabric doesn’t exist：指定ID的Fabric不存在 · The BGP instance name is invalid：无效的BGP实例名称 · The BGP instance name can't exceed 31 characters：BGP实例名称不能超过31个字符 · The GR timer is in the range of 3 to 600：BGP会话重连等待时间的取值范围为3～600 · The GR timer is invalid：无效的BGP会话重连等待时间 · The Extra GR timer is in the range of 0 to 86400：BGP会话重连额外等待时间的取值范围为0～86400 · The Extra GR timer is invalid：无效的BGP会话重连额外等待时间 · Only one BGP instance is supported：当前仅只支持创建一个BGP实例 · The request is invalid：无效的请求 · Unknown error：未知错误 · The parameter (%s) can't be modified：(parameters)参数不允许被修改 · The parameter (%s) is required：(parameters)参数为必选项 · The parameter (%s) is invalid：(parameters)参数是无效的 · The parameter (%s) can't exceed 255 characters：(parameters)参数不能超过255个字符 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · You have no privilege to perform this operation：用户无权限执行此操作 · The BGP instance has been bound to a shared cluster. The maximum number of optimal routes must be equal to or higher than the number of BGP peers in the instance：共享模式下，BGP优选路由的个数必须大于等于BGP对等体中Fabric的个数 · The specified BGP cluster does not exist：指定的BGP集群不存在 · The cluster has been bound to another BGP instance：该集群已被其他BGP实例绑定 · The AS number has been assigned to another BGP instance or BGP peer：该BGP实例的AS号已被其他BGP实例或BGP对等体使用 · Invalid fabric ID：无效的Fabric ID · The fabric has been bound to another BGP instance or BGP peer：该Fabric已被其他BGP实例或BGP对等体绑定 · Invalid ID. 无效的ID · The peer IP address already exists in the BGP instance：同一个BGP实例中，对等体IP不能重复 · You cannot configure the ebgp_max_hop field when the sharing mode of the cluster is exclusive：集群模式为独享模式时，不支持配置ebgp_max_hop参数 · The value for the ebgp_max_hop field must be an integer in the range of 1 to 255：ebgp_max_hop参数取值范围为1～255的整数 · The BGP instance is bound to a shared cluster. You can configure the maximum number of hops to a peer only if it uses a different AS number than any one of its BGP peers：BGP实例绑定的集群为共享模式时，BGP实例的AS号和对等体的AS号不一致才允许配置EBGP连接最大跳数 · The cluster bound to the BGP instance is in shared mode.In this mode,make sure all BGP peers bound to the BGP instance have the same fabric ID and AS number. Alternatively, make sure each of the peers has a unique fabric ID and AS number：集群模式为共享模式时，相同BGP实例下的多个BGP对等体绑定的Fabric和AS号要么都一样，要么都不一样 · Please make sure the AS number of the BGP peer is unique among all BGP instances bound to exclusive clusters and all BGP peers bound to shared clusters：该BGP实例绑定的集群是共享模式时，BGP对等体的AS号不能与其他独享模式集群绑定的BGP实例AS号、共享模式集群绑定的对等体AS号重复 · Please make sure the AS number of the BGP instance is unique among all BGP instances bound to exclusive clusters and all BGP peers bound to shared clusters：该BGP实例绑定的BGP集群是独享模式时，BGP实例的AS号不能与其他独享模式集群绑定的BGP实例AS号、共享模式集群绑定的对等体AS号重复 · The system has more than one BGP instance. Please bind this BGP instance to a BGP cluster：已存在BGP实例，该实例必须绑定集群 · Two or more BGP clusters exist. Please bind the BGP instance to a BGP cluster：存在2个及以上集群，该实例必须绑定集群 · The overlay BGP AS number of fabric is required：指定Fabric的Overlay路由协议BGP AS号不能为空 |
|
关键字 |
UPDATE_BGP_INSTANCE_OP |
|
日志内容 |
Updated BGP instance: $1. |
|
参数解释 |
$1：BGP实例的名称 |
|
举例 |
Updated BGP instance: bgp_instance_name: [default] bgp_as_number: [65535] graceful_restart_timer: [150] bgp_peer_ip: [1.1.1.1] bgp_peer_as_number: [65535] graceful_restart_timer_extra: [no-limit] fabric_id: [7ffdcfab-3312-41ae-82cd-1a0547b359c1] |
|
日志说明 |
用户进行了修改BGP实例的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The BGP instance ID is invalid：无效的BGP实例ID · The BGP peer IP is invalid：无效的BGP对等体IP · The AS number is an integer in the range of 1 to 4294967295：AS号取值范围为1~4294967295的整数 · The BGP instance name is required：BGP实例名称不能为空 · The fabric ID is required：Fabric ID不允许为空 · The fabric doesn’t exist：指定ID的Fabric不存在 · The BGP instance name is invalid：无效的BGP实例名称 · The BGP instance name can't exceed 31 characters：BGP实例名称不能超过31个字符 · The GR timer is in the range of 3 to 600：BGP会话重连等待时间的取值范围为3～600 · The GR timer is invalid：无效的BGP会话重连等待时间 · The Extra GR timer is in the range of 0 to 86400：BGP会话重连额外等待时间的取值范围为0～86400 · The Extra GR timer is invalid：无效的BGP会话重连额外等待时间 · The request is invalid：无效的请求 · Unknown error：未知错误 · The parameter (%s) can't be modified：(parameters)参数不允许被修改 · The parameter (%s) is required：(parameters)参数为必选项 · The parameter (%s) is invalid：(parameters)参数是无效的 · The parameter (%s) can't exceed 255 characters：(parameters)参数不能超过255个字符 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · You have no privilege to perform this operation：用户无权限执行此操作 · The BGP instance has been bound to a shared cluster. The maximum number of optimal routes must be equal to or higher than the number of BGP peers in the instance：共享模式下，BGP优选路由的个数必须大于等于BGP对等体中Fabric的个数 · Invalid fabric ID： 无效的Fabric ID · The fabric has been bound to another BGP instance or BGP peer：该Fabric已被其他BGP实例或BGP对等体绑定 · The peer IP address already exists in the BGP instance：同一个BGP实例中，对等体IP不能重复。 · You cannot configure the ebgp_max_hop field when the sharing mode of the cluster is exclusive：集群模式为独享模式时，不支持配置ebgp_max_hop参数 · The value for the ebgp_max_hop field must be an integer in the range of 1 to 255：ebgp_max_hop参数取值范围为1～255的整数 · The BGP instance is bound to a shared cluster. You can configure the maximum number of hops to a peer only if it uses a different AS number than any one of its BGP peers：BGP实例绑定的集群为共享模式时，BGP实例的AS号和对等体的AS号不一致才允许配置EBGP连接最大跳数 · The cluster bound to the BGP instance is in shared mode.In this mode,make sure all BGP peers bound to the BGP instance have the same fabric ID and AS number. Alternatively, make sure each of the peers has a unique fabric ID and AS number：集群模式为共享模式时，相同BGP实例下的多个BGP对等体绑定的Fabric和AS号要么都一样，要么都不一样 · Please make sure the AS number of the BGP peer is unique among all BGP instances bound to exclusive clusters and all BGP peers bound to shared clusters：该BGP实例绑定的集群是共享模式时，BGP对等体的AS号不能与其他独享模式集群绑定的BGP实例AS号、共享模式集群绑定的对等体AS号重复 · Please make sure the AS number of the BGP instance is unique among all BGP instances bound to exclusive clusters and all BGP peers bound to shared clusters：该BGP实例绑定的BGP集群是独享模式时，BGP实例的AS号不能与其他独享模式集群绑定的BGP实例AS号、共享模式集群绑定的对等体AS号重复 · The overlay BGP AS number of fabric is required：指定Fabric的Overlay路由协议BGP AS号不能为空 |
|
关键字 |
Delete BGP instance |
|
日志内容 |
Deleted BGP instance: $1 |
|
参数解释 |
$1：BGP实例的名称 |
|
举例 |
Deleted BGP instance: [218b5f2f-e435-4365-a1ab-0eaa03b7fa19] |
|
日志说明 |
用户进行了删除指定BGP实例的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
SYNC_ROUTE_OP |
|
日志内容 |
Synchronized routes. |
|
参数解释 |
无 |
|
举例 |
Synchronized routes: node management ip: [1.1.1.1] instance name: [default] |
|
日志说明 |
用户进行了控制组件向vBGP平滑配置和路由的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The management IP is invalid：管理IP是无效的 · The BGP instance name is invalid：BGP实例名称是无效的 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_BGPNQAC_OP |
|
日志内容 |
Updated NQA: $1 |
|
参数解释 |
$1：NQA的配置信息 |
|
举例 |
Updated NQA: Northbound IP detection: on Probe timeout:"14" Frequency:"14" Probe failure consecutive times:"14". |
|
日志说明 |
用户进行了更新NQA配置的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Token aged：Token已老化 · Cannot edit the NQA parameters when northbound IP detection is disabled：北向IP探测开关关闭后，不允许修改NQA下的所有参数 · The controller is not the active leader：该控制组件不是主Leader · Please specify a probe timeout value：超时时间不能为空 · The timeout value must be an integer in the range of 10 to 3600000：超时时间的取值范围为10~3600000的整数 · Please specify a frequency value：探测频率不能为空 · The frequency must be an integer in the range of 0 to 604800000：探测频率的取值范围为0~604800000的整数 · Please specify the number of probe failure consecutive times：探测失败次数不能为空 · The number of probe failure consecutive times must be an integer in the range of 1 to 16：探测失败次数的取值范围为1~16的整数 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
SMOOTH_INJECTED_LEARNED_ROUTE_OP |
|
日志内容 |
Synchronized injected route configuration and learned route configuration to vBGP cluster $1. |
|
参数解释 |
$1：vBGP集群名称 |
|
举例 |
Synchronized injected route configuration and learned route configuration to vBGP cluster test1. |
|
日志说明 |
控制组件向指定的vBGP集群同步注入路由和订阅路由的配置 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · The BGP cluster can contain only one primary node：当前BGP集群存在两个主节点 · The NETCONF session to the BGP node is not up：BGP节点的NETCONF会话状态必须为UP |
本节介绍裸金属管理模块输出的操作日志信息。
|
关键字 |
CREATE_BSM_ACCESS_NETWORK_OP |
|
日志内容 |
Created a VLAN-VXLAN mapping table for the access network: $1. |
|
参数解释 |
$1：裸金属接入端网络的映射表配置信息 |
|
举例 |
Created a VLAN-VXLAN mapping table for the access network: Type: [VXLAN] Network: [INSPECTION] Default_PVID: [null] Domain: [ Name: [aaa] ID: [29577831-31d1-46e7-a33a-40f6ae6f4179] VLAN: [10] VXLAN: [100] ]. |
|
日志说明 |
用户创建了裸金属接入端网络的映射表 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · Internal server error：内部错误 · Please perform the operation on the active leader：请在主Leader上进行操作 · Configuration recovery is in progress：配置正在恢复过程中 · Invalid mapping table name：无效的映射表名称 · The VLAN ID is invalid or out of range：VLAN值无效或超出范围 · The VXLAN ID is invalid or out of range：VXLAN值无效或超出范围 · The mapping table already exists：映射表已存在 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_BSM_ACCESS_NETWORK_OP |
|
Updated a VLAN-VXLAN mapping table of the access network: $1. |
|
|
参数解释 |
$1：裸金属接入端网络的映射表配置信息 |
|
举例 |
Updated a VLAN-VXLAN mapping table of the access network: Type: [VXLAN] Network: [WORKING] Default_PVID: [null] Domain: [ Name: [new_name] ID: [3a24b5b8-8fd1-492d-b867-88976c198d17] VLAN: [30] VXLAN: [300] ]. |
|
日志说明 |
用户修改了裸金属接入端网络的映射表 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · Internal server error：内部错误 · Please perform the operation on the active leader：请在主Leader上进行操作 · Configuration recovery is in progress：配置正在恢复过程中 · The mapping table does not exist：映射表不存在 · Invalid mapping table name：无效的映射表名称 · The VLAN ID is invalid or out of range：VLAN值无效或超出范围 · The VXLAN ID is invalid or out of range：VXLAN值无效或超出范围 · The reserved VLAN ID conflicts with a VLAN ID of an VLAN-VXLAN mapping：存储VLAN与VLAN-VXLAN映射冲突 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_BSM_ACCESS_NETWORK_OP |
|
日志内容 |
Deleted a VLAN-VXLAN mapping table from the access network: $1. |
|
参数解释 |
$1：裸金属接入端网络的映射表ID |
|
举例 |
Deleted a VLAN-VXLAN mapping table from the access network: 3a24b5b8-8fd1-492d-b867-88976c198d17. |
|
日志说明 |
用户删除了裸金属接入端网络的映射表 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · Internal server error：内部错误 · Please perform the operation on the active leader：请在主Leader上进行操作 · Configuration recovery is in progress：配置正在恢复过程中 · The mapping table does not exist：映射表不存在 · The mapping table has been bound to devices：该映射表已绑定设备 · The mapping table has been bound to interfaces：该映射表已绑定接口 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
MODIFY_BSM_INSPECT_STATUS_OP |
|
日志内容 |
Modified states of inspection network interfaces: $1. |
|
参数解释 |
$1：Inspection网络端口的状态信息 |
|
举例 |
Modified states of inspection network interfaces: Port_status: [INACTIVE] Port_list: [ Device_type: [DEVICE_NAME], device_value: [TOR1], port_name: [GigabitEthernet1/0/1] ]. |
|
日志说明 |
用户修改了Inspection网络端口的状态 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · Internal server error：内部错误 · Please perform the operation on the active leader：请在主Leader上进行操作 · Configuration recovery is in progress：配置正在恢复过程中 · Invalid interface list：无效的接口列表 · Invalid interface names exist：存在无效的接口名称 · Nonexistent devices are specified：设备不存在 · Invalid device MAC addresses exist：无效的设备MAC地址 · Invalid device names exist：存在无效的设备名称 · Non-VTEP interfaces exist：存在非VTEP接口 · Interfaces not bound to the inspection network exist：接口未绑定在Inspection网络上 · Interfaces bound to non-inspection networks exist：接口已被绑定在非Inspection网络上 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_BSM_WORK_PORTBIND_OP |
|
Bound working network interfaces to a VLAN-VXLAN mapping table: $1. |
|
|
参数解释 |
$1：Working网络端口的绑定信息 |
|
举例 |
Bound working network interfaces to a VLAN-VXLAN mapping table: VLAN: [100] VXLAN: [1000] Domain_ID: [49df9c11-b06d-4910-bc54-5992a4459959] Domain_name: [working_100_1000] Port_list: [ Bond_mode: [4], info: [ Device_type: [DEVICE_NAME], device_value: [TOR1], port_name: [GigabitEthernet1/0/2] Device_type: [DEVICE_NAME], device_value: [TOR1], port_name: [GigabitEthernet1/0/3] ] Bond_mode: [4], info: [ Device_type: [DEVICE_NAME], device_value: [TOR2], port_name: [GigabitEthernet1/0/2] Device_type: [DEVICE_NAME], device_value: [TOR2], port_name: [GigabitEthernet1/0/3] ] ]. |
|
日志说明 |
用户增加了Working网络端口的绑定关系 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · Internal server error：内部错误 · Please perform the operation on the active leader：请在主Leader上进行操作 · Configuration recovery is in progress：配置正在恢复过程中 · The VLAN ID is invalid or out of range：VLAN值无效或超出范围 · The VXLAN ID is invalid or out of range：VXLAN值无效或超出范围 · Invalid interface list：无效的接口列表 · Invalid interface names exist：存在无效的接口名称 · Nonexistent devices are specified：设备不存在 · Invalid device MAC addresses exist：存在无效的设备MAC地址 · Invalid device names exist：存在无效的设备名称 · The default access VLAN does not exist：默认接入VLAN不存在 · Invalid interface list：无效的接口列表 · Non-VTEP interfaces exist：存在非VTEP接口 · Interfaces bound to other VLAN-VXLAN mapping tables exist：接口已被绑定 · Duplicate interfaces exist：存在重复的接口 · Interfaces already bound to the VLAN-VXLAN mapping table exist：接口绑定已存在 · Interfaces bound to the inspection network exist：接口已被绑定在Inspection网络上 · You have no privilege to perform this operation：用户无权限执行此操作 · The specified interface already exists in an interface and PVID mapping：指定的接口已存在于配置PVID中 |
|
关键字 |
DELETE_BSM_WORK_PORTBIND_OP |
|
日志内容 |
Unbound working network interfaces from a VLAN-VXLAN mapping table: $1. |
|
参数解释 |
$1：Working网络端口的绑定信息 |
|
举例 |
Unbound working network interfaces from a VLAN-VXLAN mapping table: VLAN: [100] VXLAN: [1000] Domain_ID: [null] Domain_name: [null] Port_list: [ Bond_mode: [4], info: [ Device_type: [DEVICE_NAME], device_value: [TOR1], port_name: [GigabitEthernet1/0/2] Device_type: [DEVICE_NAME], device_value: [TOR1], port_name: [GigabitEthernet1/0/3] ] Bond_mode: [4], Info: [ Device_type: [DEVICE_NAME], device_value: [TOR2], port_name: [GigabitEthernet1/0/2] Device_type: [DEVICE_NAME], device_value: [TOR2], port_name: [GigabitEthernet1/0/3] ] ]. |
|
日志说明 |
用户删除了working网络端口的绑定关系 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · Internal server error：内部错误 · Please perform the operation on the active leader：请在主Leader上进行操作 · Configuration recovery is in progress：配置正在恢复过程中 · The VLAN ID is invalid or out of range：VLAN值无效或超出范围 · The VXLAN ID is invalid or out of range：VXLAN值无效或超出范围 · Invalid interface list：无效的接口列表 · Invalid interface names exist：无效的接口名称 · Nonexistent devices are specified：设备不存在 · Invalid device MAC addresses exist：无效的设备MAC地址 · Invalid device names exist：无效的设备名称 · The default access VLAN does not exist：默认接入VLAN不存在 · Invalid interface list：无效的接口列表 · Duplicate interfaces exist：存在重复的接口 · The mapping table does not exist：映射表不存在 · Interfaces not bound to the working network exist：接口未绑定在Working网络上 · Interfaces not bound to the VLAN-VXLAN mapping table exist：接口绑定不存在 · Non-VTEP interfaces exist：存在非VTEP接口 · Duplicate interfaces exist：存在重复的接口 · The mapping table has been bound to devices：该映射表已绑定设备 · The mapping table has been bound to interfaces：该映射表已绑定接口 · You have no privilege to perform this operation：用户无权限执行此操作 · Failed to obtain the device through its MAC address. Please verify that the device MAC address is correct and the leader controller and the device can communicate with each other normally：根据设备MAC无法查询到设备，请检查设备MAC是否正确以及Leader控制器和设备是否正常通信 |
|
关键字 |
CREATE_BSM_WORKING_VLAN_OP |
|
日志内容 |
Added a default access VLAN for the working network: $1. |
|
参数解释 |
$1：默认接入VLAN |
|
举例 |
Added a default access VLAN for the working network: VLAN: [100]. |
|
日志说明 |
用户进行了配置Working网络的默认接入VLAN的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · Internal server error：内部错误 · Please perform the operation on the active leader：请在主Leader上进行操作 · Configuration recovery is in progress：配置正在恢复过程中 · The VLAN ID is invalid or out of range：VLAN值无效或超出范围 · The working network has been configured with a default access VLAN：默认接入VLAN已存在 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_BSM_WORKING_VLAN_OP |
|
日志内容 |
Deleted the default access VLAN from the working network. |
|
参数解释 |
无 |
|
举例 |
Deleted the default access VLAN from the working network. |
|
日志说明 |
用户进行了删除Working网络的默认接入VLAN的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · Internal server error：内部错误 · Please perform the operation on the active leader：请在主Leader上进行操作 · Configuration recovery is in progress：配置正在恢复过程中 · The default access VLAN does not exist：默认接入VLAN不存在 · The default access VLAN is being used：默认接入VLAN已被占用 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_BSM_VLAN_DOMAIN_OP |
|
日志内容 |
Created a VLAN-VXLAN mapping table for the service network: $1. |
|
参数解释 |
$1：裸金属服务端的映射表配置信息 |
|
举例 |
Created a VLAN-VXLAN mapping table for the service network: Domain_name: [domain1] ID: [5473e36e-5b34-4e9d-9d20-206310d1d478] Mappings: [ Start_VLAN: [50], end_VLAN: [60], start_VXLAN: [310], end_VXLAN: [310], access_mode: [ETHERNET] ]. |
|
日志说明 |
用户创建了裸金属服务端的映射表 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · Internal server error：内部错误 · Please perform the operation on the active leader：请在主Leader上进行操作 · Configuration recovery is in progress：配置正在恢复过程中 · Invalid mapping table name：无效的映射表名称 · The VLAN ID is invalid or out of range：VLAN值无效或超出范围 · The VXLAN ID is invalid or out of range：VXLAN值无效或超出范围 · Overlapping mappings exist：映射关系存在重叠 · The mapping table already exists：映射表已存在 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_BSM_VLAN_DOMAIN_OP |
|
日志内容 |
Updated a VLAN-VXLAN mapping table of the service network: $1. |
|
参数解释 |
$1：裸金属服务端的映射表配置信息 |
|
举例 |
Updated a VLAN-VXLAN mapping table of the service network: Domain_name: [domain2] ID: [5473e36e-5b34-4e9d-9d20-206310d1d478] Mappings: [ Start_VLAN: [50], end_VLAN: [60], start_VXLAN: [320], end_VXLAN: [320], access_mode: [ETHERNET] ]. |
|
日志说明 |
用户修改了裸金属服务端的映射表 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · Internal server error：内部错误 · Please perform the operation on the active leader：请在主Leader上进行操作 · Configuration recovery is in progress：配置正在恢复过程中 · The mapping table does not exist：映射表不存在 · Invalid mapping table name：无效的映射表名称 · The VLAN ID is invalid or out of range：VLAN值无效或超出范围 · The VXLAN ID is invalid or out of range：VXLAN值无效或超出范围 · Overlapping mappings exist：映射关系存在重叠 · The reserved VLAN ID conflicts with a VLAN ID of an VLAN-VXLAN mapping：存储VLAN与VLAN-VXLAN映射冲突 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_BSM_VLAN_DOMAIN_OP |
|
日志内容 |
Deleted a VLAN-VXLAN mapping table from the service network: $1. |
|
参数解释 |
$1：裸金属服务端的映射表ID |
|
举例 |
Deleted a VLAN-VXLAN mapping table from the service network: 5473e36e-5b34-4e9d-9d20-206310d1d478. |
|
日志说明 |
用户删除了裸金属服务端的映射表 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · Internal server error：内部错误 · Please perform the operation on the active leader：请在主Leader上进行操作 · Configuration recovery is in progress：配置正在恢复过程中 · The mapping table does not exist：映射表不存在 · The mapping table has been bound to devices：该映射表已绑定设备 · The mapping table has been bound to interfaces：该映射表已绑定接口 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_BSM_VLAN_DOMAIN_BIND_OP |
|
日志内容 |
Bound devices to a VLAN-VXLAN mapping table: $1. |
|
参数解释 |
$1：VLAN-VXLAN映射表与设备绑定信息 |
|
举例 |
Bound devices to a VLAN-VXLAN mapping table: Domain_ID: [29577831-31d1-46e7-a33a-40f6ae6f4179] Name: [aaa] Device_list: [ Device_ID: [ffd1efeb-5582-40af-b378-910d8e68bd6d], device_name: [TOR2] Device_ID: [bc96fa18-0888-474e-979d-9cf18f0433dd], device_name: [TOR1] ]. |
|
日志说明 |
用户进行了VLAN-VXLAN映射表与设备绑定的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · Internal server error：内部错误 · Please perform the operation on the active leader：请在主Leader上进行操作 · Configuration recovery is in progress：配置正在恢复过程中 · Devices already bound to the mapping table exist：设备绑定已存在 · Nonexistent devices are specified：设备不存在 · Duplicate devices exist：存在重复的设备 · Devices bound to other mapping tables exist：该设备已被绑定 · The mapping table does not exist：映射表不存在 · The port on the specified device has been bound to a QinQ-VXLAN mapping table：指定设备下的接口已被QinQ-VXLAN映射表绑定 · The reserved VLAN ID conflicts with a VLAN ID of an VLAN-VXLAN mapping：存储VLAN与VLAN-VXLAN映射冲突 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_BSM_VLAN_DOMAIN_BIND_OP |
|
日志内容 |
Updated binding relationships between a VLAN-VXLAN mapping table and devices: $1. |
|
参数解释 |
$1：VLAN-VXLAN映射表与设备绑定信息 |
|
举例 |
Updated binding relationships between a VLAN-VXLAN mapping table and devices: Domain_ID: [29577831-31d1-46e7-a33a-40f6ae6f4179] Name: [aaa] Device_list: [ Device_ID: [ffd1efeb-5582-40af-b378-910d8e68bd6d], device_name: [TOR2] Device_ID: [bc96fa18-0888-474e-979d-9cf18f0433dd], device_name: [TOR1] ]. |
|
日志说明 |
用户进行了修改VLAN-VXLAN映射表与设备绑定的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · Internal server error：内部错误 · Please perform the operation on the active leader：请在主Leader上进行操作 · Configuration recovery is in progress：配置正在恢复过程中 · Devices not bound to the mapping table exist：该绑定关系不存在 · Nonexistent devices are specified：设备不存在 · Duplicate devices exist：设备存在重复 · Devices bound to other mapping tables exist：该设备已被绑定 · The mapping table does not exist：映射表不存在 · The port on the specified device has been bound to a QinQ-VXLAN mapping table：指定设备下的接口已被QinQ-VXLAN映射表绑定 · The reserved VLAN ID conflicts with a VLAN ID of an VLAN-VXLAN mapping：存储VLAN与VLAN-VXLAN映射冲突 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_BSM_VLAN_DOMAIN_BIND_OP |
|
日志内容 |
Deleted binding relationships between a VLAN-VXLAN mapping table and all devices: $1. |
|
参数解释 |
$1：VLAN-VXLAN映射表ID |
|
举例 |
Deleted binding relationships between a VLAN-VXLAN mapping table and all devices: 29577831-31d1-46e7-a33a-40f6ae6f4179. |
|
日志说明 |
用户进行了删除VLAN-VXLAN映射表与所有设备的绑定关系的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · Internal server error：内部错误 · Please perform the operation on the active leader：请在主Leader上进行操作 · Configuration recovery is in progress：配置正在恢复过程中 · Devices already unbound from the mapping table exist：该绑定关系不存在 · The mapping table does not exist：映射表不存在 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_BSM_PORT_VLAN_DOMAIN_BIND_OP |
|
日志内容 |
Bound interfaces to a VLAN-VXLAN mapping table: $1. |
|
参数解释 |
$1：VLAN-VXLAN映射表与接口绑定信息 |
|
举例 |
Bound interfaces to a VLAN-VXLAN mapping table: Domain_ID: [29577831-31d1-46e7-a33a-40f6ae6f4179] Name: [aaa] Bind_port_list: [ Device_ID: [bc96fa18-0888-474e-979d-9cf18f0433dd], device_name: [TOR1], port_name: [GigabitEthernet1/0/1], PVID: [30], port_status: [ACTIVE] ]. |
|
日志说明 |
用户进行了把VLAN-VXLAN映射表与接口绑定的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · Internal server error：内部错误 · Please perform the operation on the active leader：请在主Leader上进行操作 · Configuration recovery is in progress：配置正在恢复过程中 · Invalid interface list：无效的接口列表 · Invalid interface names exist：无效的接口名称 · Nonexistent devices are specified：设备不存在 · Invalid device MAC addresses exist：无效的设备MAC地址 · Invalid device names exist：无效的设备名称 · The VLAN ID is invalid or out of range：VLAN值无效或超出范围 · Interfaces already bound to the mapping table exist：接口绑定已存在 · Duplicate interfaces exist：存在重复的接口 · Non-VTEP interfaces exist：存在非VTEP接口 · Interfaces bound to the inspection network exist：接口已被绑定在Inspection网络上 · Interfaces bound to other mapping tables exist：接口已被绑定 · The mapping table does not exist：映射表不存在 · The reserved VLAN ID conflicts with a VLAN ID of an VLAN-VXLAN mapping：存储VLAN与VLAN-VXLAN映射冲突 · You have no privilege to perform this operation：用户无权限执行此操作 · The specified interface already exists in an interface and PVID mapping：指定的接口已存在于配置PVID中 |
|
关键字 |
UPDATE_BSM_PORT_VLAN_DOMAIN_BIND_OP |
|
日志内容 |
Updated binding relationships between interfaces and a VLAN-VXLAN mapping table: $1. |
|
参数解释 |
$1：VLAN-VXLAN映射表与接口绑定信息 |
|
举例 |
Updated binding relationships between interfaces and a VLAN-VXLAN mapping table: Domain_ID: [29577831-31d1-46e7-a33a-40f6ae6f4179] Name: [aaa] Bind_port_list: [ Device_ID: [bc96fa18-0888-474e-979d-9cf18f0433dd], device_name: [TOR1], port_name: [GigabitEthernet1/0/1], PVID: [30], port_status: [ACTIVE] ]. |
|
日志说明 |
用户进行了修改VLAN-VXLAN映射表与接口绑定的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · Internal server error：内部错误 · Please perform the operation on the active leader：请在主Leader上进行操作 · Configuration recovery is in progress：配置正在恢复过程中 · Invalid interface list：无效的接口列表 · Invalid interface names exist：无效的接口名称 · Nonexistent devices are specified：设备不存在 · Invalid device MAC addresses exist：无效的设备MAC地址 · Invalid device names exist：无效的设备名称 · The VLAN ID is invalid or out of range：VLAN值无效或超出范围 · Interfaces not bound to the mapping table exist：接口绑定不存在 · Duplicate interfaces exist：存在重复的接口 · Non-VTEP interfaces exist：存在非VTEP接口 · Interfaces bound to the inspection network exist：接口已被绑定在Inspection网络上 · Interfaces bound to other mapping tables exist：接口已被绑定 · The mapping table does not exist：映射表不存在 · The reserved VLAN ID conflicts with a VLAN ID of an VLAN-VXLAN mapping：存储VLAN与VLAN-VXLAN映射冲突 · You have no privilege to perform this operation：用户无权限执行此操作 · The specified interface already exists in an interface and PVID mapping：指定的接口已存在于配置PVID中 · You cannot delete the aggregate interface. It is in an M-LAG group：聚合口已加入M-LAG组，不允许删除 |
|
关键字 |
DELETE_BSM_PORT_VLAN_DOMAIN_BIND_OP |
|
日志内容 |
Deleted binding relationships between a VLAN-VXLAN mapping table and all interfaces: $1. |
|
参数解释 |
$1：VLAN-VXLAN映射表ID |
|
举例 |
Deleted binding relationships between a VLAN-VXLAN mapping table and all interfaces: 29577831-31d1-46e7-a33a-40f6ae6f4179. |
|
日志说明 |
用户进行了删除VLAN-VXLAN映射表与所有接口的绑定关系的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · Internal server error：内部错误 · Please perform the operation on the active leader：请在主Leader上进行操作 · Configuration recovery is in progress：配置正在恢复过程中 · Interfaces already unbound from the mapping table exist：接口绑定不存在 · The mapping table does not exist：映射表不存在 · You have no privilege to perform this operation：用户无权限执行此操作 · You cannot delete the aggregate interface. It is in an M-LAG group：聚合口已加入M-LAG组，不允许删除 |
本节介绍CAPACITY容量仿真模块输出的操作日志信息。
|
关键字 |
EXECUTE_CAPACITY_SIMULATION_TASK_OP |
|
日志内容 |
Executed capacity simulation task: $1. |
|
参数解释 |
$1：容量仿真任务的UUID |
|
举例 |
Execute capacity simulation task: aae71a62-889b-47e7-9f1a-e73c32c61004. |
|
日志说明 |
用户进行了容量仿真任务 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · Invalid XML format：无效的XML格式 · Invalid parameter：非法参数 · The request body cannot be empty：请求体不能为空 · The (parameter) parameter cannot be empty：参数(parameter)不能为空 · Internal error：内部错误 · The service does not exist：指定的服务不存在 · Thread is interrupted: 线程任务终止 · The (parameter) parameter value does not match the regular expression：参数(parameter)不匹配正则表达式 · The value for the type parameter can only be AC, VSI, VSI-Interface, VRF, Route：参数type取值范围必须为AC、VSI、VSI-Interface、VRF、Route · The NETCONF configuration file does not exist：指定的NETCONF配置文件不存在 · The NETCONF configuration file is empty or has no valid resources：指定的NETCONF配置文件为空或没有合法资源 · The NETCONF configuration file content does not match the regular expression：指定的NETCONF配置文件内容不符合正则表达式 · Failed to obtain command configuration from the device：查询设备命令行配置失败 · Failed to connect to the database：建立数据库连接失败 · The specified {resourceType} with {indexType} values {indexValue} does not exist：（indexType）等于（indexValue）对应的（resourceType）值在数据库中不存在 · Failed to query tenant design：查询租户设计表失败 · Another user is processing this resource. Please try again later：其他用户正在操作，请稍后再试 · Executor reject to execute task：线程池拒绝执行线程任务 · The simulated device is not found in the real network：指定的设备在真实组网中不存在 · Cannot find the specified device：找不到指定的设备 · The system service does not respond：内部系统错误 · Failed to obtain capacity information from the device：查询设备容量信息失败 · The capacity simulation task does not exist：指定的容量仿真任务不存在 · The specified device is offline on the production network：指定的设备在生产网络中已下线 · No simulation network is built for the tenant：该租户未构建仿真网络 · You cannot perform this operation, because all simulated devices are inactive：当前所有仿真设备都处于Inactive状态，无法执行当前操作 |
|
关键字 |
GET_SIMULATION_CONFIG_ALTER_OP |
|
日志内容 |
Get simulation configuration changes. |
|
参数解释 |
无参数 |
|
举例 |
Get simulation configuration changes. |
|
日志说明 |
用户进行了查询仿真配置变更的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid parameter：非法参数 · Invalid XML format：无效的XML格式 · Cannot find the specified device：找不到指定的设备 · Another user is processing this resource. Please try again later：其他用户正在操作，请稍后再试 · Get redis lock exception：获取redis锁异常 · The NETCONF configuration file does not exist：指定的NETCONF配置文件不存在 · The NETCONF configuration file content does not match the regular expression：指定的NETCONF配置文件内容不符合正则表达式 · Internal error：内部错误 · Failed to obtain command configuration from the device：查询设备命令行配置失败 · The specified {resourceType} with {indexType} values {indexValue} does not exist：（indexType）等于（indexValue）对应的（resourceType）值在数据库中不存在 · The system service does not respond：内部系统错误 · No simulation network is built for the tenant：该租户未构建仿真网络 |
|
关键字 |
INTERRUPT_CAPACITY_SIMULATION_TASK_OP |
|
日志内容 |
Interrupt capacity simulation task: $1. |
|
参数解释 |
$1：容量仿真任务的UUID |
|
举例 |
Interrupt capacity simulation task: aae71a62-889b-47e7-9f1a-e73c32c61004. |
|
日志说明 |
用户进行了中断容量仿真任务的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid parameter：非法参数 · The capacity simulation task does not exist：指定的容量仿真任务不存在 · No simulation network is built for the tenant：该租户未构建仿真网络 |
本节介绍闭环控制模块输出的操作日志信息。
|
关键字 |
REGISTER_SEERANALYSIS_OP |
|
日志内容 |
Registered SeerAnalyzer info:$1. |
|
参数解释 |
$1：分析组件的配置信息 |
|
举例 |
Register SeerAnalyzer info: { ID: f3b3a9e6-b3ef-4da6-95c7-ebee6042568e Name: outer-sa URL: https://192.158.25.20:10443 Username: admin Password: ****** }. |
|
日志说明 |
用户进行了连接分析组件的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Please specify all required parameters：参数不能为空 · Please specify an analyzer name：分析组件名称不能为空 · Invalid analyzer name length：无效的分析组件名称长度 · Please specify a URL for the analyzer：分析组件的URL不能为空 · Invalid URL length：无效的分析组件URL长度 · Invalid URL format：无效的分析组件URL格式 · Please specify a username：分析组件的用户名不能为空 · Invalid username length：无效的分析组件用户名长度 · Invalid username format：无效的分析组件用户名格式 · Please specify a password：分析组件密码不能为空 · Password encryption failed：加密失败 · Password decryption failed：解密失败 · Invalid password length：无效的分析组件密码长度 · Invalid password format：无效的分析组件密码格式 · The analyzer is not available：分析组件不可用 · Another user is processing, Please try later：其他用户正在操作，请稍后重试 · The system service does not respond：系统服务未响应 · Failed to connect to the analyzer：连接分析组件失败 · The analyzer name or address already exists：分析组件名称或地址已经存在 |
|
关键字 |
UPDATE_SEERANALYSIS_OP |
|
日志内容 |
Updated SeerAnalyzer info: $1 |
|
参数解释 |
$1：分析组件的配置信息 |
|
举例 |
Updated SeerAnalyzer info: { ID: f3b3a9e6-b3ef-4da6-95c7-ebee6042568e Name: outer-sa URL: https://192.158.25.20:10443 Username: admin Password: ****** }. |
|
日志说明 |
用户进行了修改分析组件信息的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The specified resource does not exist：指定的资源不存在 · Please specify all required parameters：参数不能为空 · Please specify a UUID：UUID不能为空 · Invalid UUID：无效的UUID · Please specify an oldpassword：分析组件旧密码不能为空 · Incorrect old password：旧密码不正确 · Please specify an analyzer name：分析组件名称不能为空 · Invalid analyzer name length：无效的分析组件名称长度 · Please specify a URL for the analyzer：分析组件的URL不能为空 · Invalid URL length：无效的分析组件URL长度 · Invalid URL format：无效的分析组件URL格式 · Please specify a username：分析组件的用户名不能为空 · Invalid username length：无效的分析组件用户名长度 · Invalid username format：无效的分析组件用户名格式 · Please specify a password：分析组件密码不能为空 · Invalid password length：无效的分析组件密码长度 · Invalid password format：无效的分析组件密码格式 · Password encryption failed：加密失败 · Password decryption failed：解密失败 · Oldpassword decryption failed：旧密码解密失败 · The analyzer is not available：分析组件不可用 · Another user is processing, Please try later：其他用户正在操作，请稍后重试 · The system service does not respond：系统服务未响应 · Failed to connect to the analyzer：连接分析组件失败 · The analyzer name or address already exists：分析组件名称或地址已经存在 |
|
关键字 |
DELETE_SEERANALYSIS_OP |
|
日志内容 |
Deleted SeerAnalyzer info: $1 |
|
参数解释 |
$1：分析组件的ID |
|
举例 |
Deleted SeerAnalyzer info: f3b3a9e6-b3ef-4da6-95c7-ebee6042568e. |
|
日志说明 |
用户进行了删除分析组件信息的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid UUID：无效的UUID · The specified resource does not exist：指定的资源不存在 |
|
关键字 |
CLOSE_FAULT_OP |
|
日志内容 |
Closed event: $1 |
|
参数解释 |
$1：故障事件的UUID |
|
举例 |
Closed event: f3b3a9e6-b3ef-4da6-95c7-ebee6042568e |
|
日志说明 |
用户进行了关闭故障事件的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The specified resource does not exist：指定的资源不存在 · Please specify a UUID for the event：闭环事件UUID不允许为空 · Invalid UUID for the event：无效的闭环事件UUID · The analyzer is not available：分析组件不可用 · Another user is processing, Please try later：其他用户正在被操作，请稍后再试 · The specified event has been closed：指定的闭环事件已关闭 · Please undeploy the solution before closing the event：必须先回退已经下发的预案，才可以进行关闭操作 · The comment on the close action cannot exceed 120 characters：关闭原因长度不能超过120 · The system service does not respond：系统服务未响应 · You have no privilege to perform the operation：当前用户无权限执行此操作 · Failed to find the analyzer based on the event source IP. The analyzer might have not registered with the controller：根据分析组件事件来源IP查找分析组件失败，分析组件可能未注册 · Cannot find the analyzer that reported the issue. The controller has multiple registered analyzers, but the issue does not contain analyzer address information：该故障事件为单分析组件场景数据，不支持多分析组件场景 · The analyzer is not registered with the controller：分析组件未注册 |
|
关键字 |
IMPLEMENT_PROPOSAL_OP |
|
日志内容 |
Deployed solution:$1. |
|
参数解释 |
$1：预案信息参数 |
|
举例 |
Deployed solution: { "faultId": "bb8bb083-c4a4-45eb-b5dc-2b251a7921f3", "planId": "118bb083-c4a4-45eb-b5dc-2b251a7921f3", "detailId": "333bb083-c4a4-45eb-b5dc-2b251a7921f3", "customData": { "resetRouterId": "1.2.2.2" } }. |
|
日志说明 |
用户进行了下发预案的操作 customData字段包含预案中用户自定义的数据。如果用户未设置自定义数据，则此字段取值为null |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · The specified resource does not exist：指定的资源不存在 · Please specify a UUID for the event：闭环事件的UUID不能为空 · Please specify a planId：事件预案UUID不能为空 · Invalid value for the planId field：无效的planId字段 · Please specify a detailId：事件预案详情UUID不能为空 · Invalid value for the detailId field：无效的detailId字段 · Another user is processing, Please try later：其他用户正在被操作，请稍后再试 · The deploy action is available only for active events：只有活跃状态的事件才可以下发预案 · The fault event type isn't isolation or recovery can not be issued：非预案类或恢复类不允许下发 · Other plans for specified event have been issued：故障事件已有其他预案下发 · The solution with the specified UUID does not exist：指定UUID的预案不存在 · The solution detail with the specified UUID does not exist：指定UUID的预案详情不存在 · The analyzer is not available：分析组件不可用 · Failed to isolate the port：隔离端口失败 · Failed to add the device configuration fragment：添加设备配置片段失败 · Failed to obtain the switch interface information：查询交换机接口信息失败 · Failed to deploy the device configuration fragment：下发设备配置片段失败 · The system service does not respond：系统服务未响应 · The specified solution detail has been deployed：指定的预案已经被下发 · Failed to synchronize solution to the analyzer：同步分析组件失败 · You have no privilege to perform the operation：当前用户无权限执行此操作 · Failed to obtain failure event information from SeerAnalyzer：查询分析组件上的故障事件状态服务异常 · Cannot find the failure event on SeerAnalyzer. The controller will close the failure event automatically：该故障事件在分析组件上不存在，当前事件将自动关闭 · The failure event is already closed on SeerAnalyzer. The controller will close the failure event automatically：该故障事件在分析组件上已关闭，当前事件将自动关闭 · Failed to deploy the device configuration netconf：下发设备NETCONF配置失败 · Failed to find the analyzer based on the event source IP. The analyzer might have not registered with the controller：根据分析组件事件来源IP查找分析组件失败，分析组件可能未注册 · Cannot find the analyzer that reported the issue. The controller has multiple registered analyzers, but the issue does not contain analyzer address information：该故障事件为单分析组件场景数据，不支持多分析组件场景 · The analyzer is not registered with the controller：分析组件未注册 · The value for the resetRouterId field must be in dotted decimal notation and cannot be 0.0.0.0：resetRouterId字段取值必须为点分十进制，且不能为0.0.0.0 · Failed to obtain OSPF policy application information：查询OSPF策略应用信息失败 · The setting was deployed by the OSPF service module and is not editable. Please change the conflicting Router ID manually configured on another device：此Router ID为控制组件OSPF业务下发，不允许重设。请修改另一设备上手工配置的冲突ID · Router ID has been used：Router ID已被使用 |
|
关键字 |
FALLBACK_PROPOSAL_OP |
|
日志内容 |
Undeployed solution: $1 |
|
参数解释 |
$1：预案信息参数 |
|
举例 |
Undeployed solution: { "faultId": "bb8bb083-c4a4-45eb-b5dc-2b251a7921f3", "planId": "118bb083-c4a4-45eb-b5dc-2b251a7921f3", "detailId": "333bb083-c4a4-45eb-b5dc-2b251a7921f3", "customData": null }. |
|
日志说明 |
用户进行了回退预案的操作 customData为预案回退时用户自定义的数据。如果用户未设置自定义数据，则此字段取值为null |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · The specified resource does not exist：指定的资源不存在 · Please specify a UUID for the event：闭环事件的UUID不能为空 · Please specify a planId：事件预案UUID不能为空 · Invalid value for the planId field：无效的planId字段 · Please specify a detailId：事件预案详情UUID不能为空 · Invalid value for the detailId field.：无效的detailId字段 · The solution with the specified UUID does not exist：指定UUID的预案不存在 · The solution detail with the specified UUID does not exist：指定UUID的预案详情不存在 · Another user is processing, Please try later：其他用户正在被操作，请稍后再试 · The specified event has been closed：指定的闭环事件已关闭 · The undeploy action is supported only for events that have solutions deployed：只有预案类的事件才可以回退预案 · The analyzer is not available：分析组件不可用 · The solution has not been deployed：指定的预案没有被下发 · The system service does not respond：系统服务未响应 · Failed to isolate the port：隔离端口失败 · Failed to add the device configuration fragment：添加设备配置片段失败 · Failed to obtain the switch interface information：查询交换机接口信息失败 · Failed to deploy the device configuration fragment：下发设备配置片段失败 · Failed to synchronize solution to the analyzer：同步分析组件失败 · You have no privilege to perform the operation：当前用户无权限执行此操作 · Failed to deploy the device configuration netconf：下发设备NETCONF配置失败 · Failed to obtain failure event information from SeerAnalyzer：查询分析组件上的故障事件状态服务异常 · Cannot find the failure event on SeerAnalyzer. The controller will close the failure event automatically：该故障事件在分析组件上不存在，当前事件将自动关闭 · The failure event is already closed on SeerAnalyzer. The controller will close the failure event automatically：该故障事件在分析组件上已关闭，当前事件将自动关闭 · Failed to find the analyzer based on the event source IP. The analyzer might have not registered with the controller：根据分析组件事件来源IP查找分析组件失败，分析组件可能未注册 · Cannot find the analyzer that reported the issue. The controller has multiple registered analyzers, but the issue does not contain analyzer address information：该故障事件为单分析组件场景数据，不支持多分析组件场景 · The analyzer is not registered with the controller：分析组件未注册 |
本节介绍证书管理模块输出的操作日志信息。
|
关键字 |
IMPORT_CERTIFICATE_OP |
|
日志内容 |
Import a certificate: ID=$1, name=$2, type=$3, service =$4. $5 |
|
参数解释 |
$1：证书ID $2：证书名称 $3：证书类型 $4：服务名称 $5：主题信息 |
|
举例 |
Import a certificate: ID=98b770b1-ed38-462e-8191-d45ee3e8a273, name=keystore.jks, type=keystore, service=OpenFlow. With subject "CN=*.h3c.com, OU=SDN, O=H3C, ST=ZJ, C=CN". |
|
日志说明 |
用户进行了对指定服务导入证书的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The user role doesn't provide the permission to perform the operation：用户权限不足 · The system is not responding：系统服务未响应 · Invalid service：无效的服务 · This function is not supported：目前不支持本功能 · The certificate type is not specified：缺少证书类型 · Invalid certificate：无效的证书 · Invalid certificate name：无效的证书名 · The certificate file size cannot exceed 50 KB：证书文件过大 · Invalid certificate type：无效的证书类型 · The certificate is not valid yet：证书还未生效 · The certificate has expired：证书已过期 · The specified service does not exist：指定的服务不存在 · A certificate already exists with the specified name：指定的证书名称已存在 · The fingerprint has been used in another certificate：指纹重复 · The certificate file in CER format cannot be of the private key type：.cer格式的证书文件不允许为密钥类型 |
|
关键字 |
DELETE_CERTIFICATE_OP |
|
日志内容 |
Delete a certificate: ID=$1, name=$2, type=$3, service=$4. |
|
参数解释 |
$1：证书ID $2：证书名称 $3：证书类型 $4：服务名称 |
|
举例 |
Delete a certificate: ID=ed42ec14-d74c-4940-a0c1-ae7aba8694dc, name=keystore.jks, type=keystore, service=OpenFlow. |
|
日志说明 |
用户进行了删除证书的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The user role doesn't provide the permission to perform the operation：用户权限不足 · The system is not responding：系统服务未响应 · The resource doesn't exist：指定的资源不存在 · The certificate is in use：证书使用中 |
|
关键字 |
EXPORT_CERTIFICATE_OP |
|
日志内容 |
Export a certificate: ID=$1, name=$2, type=$3, service =$4. |
|
参数解释 |
$1：证书ID $2：证书名称 $3：证书类型 $4：服务名称 |
|
举例 |
Export a certificate: ID=8032909d-47a1-4715-90af-5153ffe39899, name =ca.pem, type=keystore, service=OpenFlow. |
|
日志说明 |
用户进行了导出证书的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The system is not responding：系统服务未响应 · The resource doesn't exist：指定的资源不存在 |
|
关键字 |
ACTIVE_CERTIFICATE_OP |
|
日志内容 |
Activate a certificate: ID=$1, name=$2, type=$3, service=$4. |
|
参数解释 |
$1：证书ID $2：证书名称 $3：证书类型 $4：证书所属服务 |
|
举例 |
Activate a certificate: ID=3156d95b-3292-4d0e-a314-284a820118be, name=truststore.jks, type=truststore, service=OpenFlow. |
|
日志说明 |
用户进行了为指定服务激活证书的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The user role doesn't provide the permission to perform the operation：用户权限不足 · The system is not responding：系统服务未响应 · This function is not supported：目前不支持本功能 · The specified service does not exist：证书所属服务不存在 |
|
关键字 |
INACTIVE_CERTIFICATE_OP |
|
日志内容 |
Deactivate a certificate: ID=$1, name=$2, type=$3, service=$4. |
|
参数解释 |
$1：证书ID $2：证书名称 $3：证书所属服务 |
|
举例 |
Deactivate a certificate: ID=b29d3356-95b8-451b-bd86-1d35916dfe5f, name=github.cer, type=truststore, service=OpenFlow. |
|
日志说明 |
用户进行了为指定服务去激活证书的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The user role doesn't provide the permission to perform the operation：用户权限不足 · The system is not responding：系统服务未响应 · This function is not supported：目前不支持本功能 · The specified service does not exist：证书所属服务不存在 |
|
关键字 |
UPDATE_ALARM_CONFIG_OP |
|
日志内容 |
Update the alarm configuration: $1 |
|
参数解释 |
$1：告警配置信息 |
|
举例 |
Update the alarm configuration: { "period": 1, "threshold": 90 } |
|
日志说明 |
用户进行了更新告警配置的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid certificate check interval：无效的检查周期 · Invalid certificate expiration reminder value：无效的告警阈值 · The user role doesn't provide the permission to perform the operation：用户权限不足 · The system is not responding：系统服务未响应 · Invalid JSON format：JSON格式不合法 |
本节介绍监听器模块输出的操作日志信息。
|
关键字 |
REGISTER_ LISTENER_OP |
|
日志内容 |
Registered alert topic listener: $1. |
|
参数解释 |
$1：监听器配置信息 |
|
举例 |
Registered alert topic listener: { "alert": { "url": "http://192.168.16.2/vnetcontroller/alter", "level": "warn", "subject": ["tunnel", "session"], "app_name": "vnetcontroller", "push_history": true } } |
|
日志说明 |
用户进行了注册监听器的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · A listener with the same app_name has already been registered：指定名称的监听器已经存在 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_LISTENER_OP |
|
日志内容 |
Updated alert topic listener: $1. |
|
参数解释 |
$1：监听器配置信息 |
|
举例 |
Updated alert topic listener: { "alert": { "app_name": "vnetcontroller", "level": "warn", "subject": ["tunnel", "session"] } } |
|
日志说明 |
用户进行了修改监听器的操作 |
|
失败原因 |
You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
REMOVE_LISTENER_OP |
|
日志内容 |
Removed alert topic listener: $1. |
|
参数解释 |
$1：监听器名称 |
|
举例 |
Removed alert topic listener: vnetcontroller |
|
日志说明 |
用户进行了删除监听器的操作 |
|
失败原因 |
You have no privilege to perform this operation：用户无权限执行此操作 |
本节介绍网络健康监控模块输出的操作日志信息。
|
关键字 |
CHANGE_THRESHOLDS_OP |
|
日志内容 |
Changed network monitor thresholds for CPU $1 in slot $2 of chassis $3 on device $4: $5 |
|
参数解释 |
$1：设备的CPU ID $2：设备的槽位号 $3：设备的机框号 $4：设备的IP地址 $5：设备的阈值信息 |
|
举例 |
Changed network monitor thresholds for CPU 1 in slot 1 of chassis 1 on device 192.168.150.21: { cpuRecoveryThreshold: 10 cpuMinorThreshold: 20 cpuWarningThreshold: 40 memorySecureThreshold: 10 memoryEarlyWarningThreshold: 20 memoryNormalThreshold: 30 memoryMinorThreshold: 30 memorySevereThreshold: 40 memoryCriticalThreshold: 50 aclMinorThreshold: 50 aclSevereThreshold: 60 acMinorThreshold: 20 acSevereThreshold: 40 vsiMinorThreshold: 20 vsiSevereThreshold: 40 vlanMinorThreshold: 20 vlanSevereThreshold: 40 } |
|
日志说明 |
用户进行了修改设备指定告警阈值的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader: 该控制组件不是主Leader · The device is not a physical device：该设备的设备类型不是物理网元设备 · The device is offline：该设备未上线 · The device does not exist：该设备不存在 · The device does not support configuring CPU usage threshold：该设备暂不支持配置CPU使用率门限 · The device does not support configuring memory usage threshold：该设备暂不支持配置内存使用率门限 · The device does not support configuring ACL resource usage threshold：该设备暂不支持配置ACL使用率门限 · The device does not support configuring AC resource usage threshold：该设备暂不支持配置AC使用率门限 · The device does not support configuring VSI interface resource usage threshold：该设备暂不支持配置VSI接口使用率门限 · The device does not support configuring VLAN interface resource usage threshold：该设备暂不支持配置VLAN接口使用率门限 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CHANGE_THRESHOLDS_ALL_OP |
|
日志内容 |
Changed network monitor thresholds for all CPUs on device $1: $2 |
|
参数解释 |
$1：设备的IP地址 $2：设备的阈值信息 |
|
举例 |
Changed network monitor thresholds for all CPUs on device 192.168.150.21: { cpuRecoveryThreshold: 10 cpuMinorThreshold: 20 cpuWarningThreshold: 40 memorySecureThreshold: 10 memoryEarlyWarningThreshold: 20 memoryNormalThreshold: 30 memoryMinorThreshold: 30 memorySevereThreshold: 40 memoryCriticalThreshold: 50 aclMinorThreshold: 50 aclSevereThreshold: 60 acMinorThreshold: 20 acSevereThreshold: 40 vsiMinorThreshold: 20 vsiSevereThreshold: 40 vlanMinorThreshold: 20 vlanSevereThreshold: 40 } |
|
日志说明 |
用户进行了修改设备所有告警阈值的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · The device is not a physical device：该设备的设备类型不是物理网元设备 · The device is offline：该设备未上线 · The device does not exist：该设备不存在 · The device does not support configuring CPU usage threshold：该设备暂不支持配置CPU使用率门限 · The device does not support configuring memory usage threshold：该设备暂不支持配置内存使用率门限 · The device does not support configuring ACL resource usage threshold：该设备暂不支持配置ACL使用率门限 · The device does not support configuring AC resource usage threshold：该设备暂不支持配置AC使用率门限 · The device does not support configuring VSI interface resource usage threshold：该设备暂不支持配置VSI接口使用率门限 · The device does not support configuring VLAN interface resource usage threshold：该设备暂不支持配置VLAN接口使用率门限 · You have no privilege to perform this operation：用户无权限执行此操作 |
本节介绍OpenFlow模块输出的操作日志信息。
|
关键字 |
CREATE_FLOWTABLE_OP |
|
日志内容 |
A flow table entry was added |
|
参数解释 |
无 |
|
举例 |
A flow table entry was added |
|
日志说明 |
用户进行了添加流表项的操作 |
|
失败原因 |
You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
MODIFY_FLOWTABLE_OP |
|
日志内容 |
A flow table entry was modified |
|
参数解释 |
无 |
|
举例 |
A flow table entry was modified |
|
日志说明 |
用户进行了修改流表项的操作 |
|
失败原因 |
You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_FLOWTABLE_OP |
|
日志内容 |
A flow table entry was deleted on device $1: $2 |
|
参数解释 |
$1：设备IP地址 $2：流表信息 |
|
举例 |
A flow table entry was deleted on device 192.168.133.68: { "flow": { "table_id": 1, "duration_sec": 7, "duration_nsec": 4294967295, "priority": 61000, "idle_timeout": 0, "hard_timeout": 0, "cookie": "0x2c324757415057", "packet_count": 24, "byte_count": 0, "match": [ {"eth_type": "ipv4"}, {"ip_proto": "udp"}, {"udp_src": 67}, {"udp_dst": 68}], "flow_mod_flags": ["send_flow_rem"], "instructions": null, "flow_mod_cmd": "delete_strict" ] } } |
|
日志说明 |
用户进行了删除流表项的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · No such device: Datapath ID：OpenFlow网络设备已断开 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_GROUPTABLE_OP |
|
日志内容 |
A group table entry was deleted on device $1: $2 |
|
参数解释 |
$1：设备IP地址 $2：组表ID信息 |
|
举例 |
A group table entry was deleted on device 192.168.133.68: {“group_id: 3”} |
|
日志说明 |
用户进行了删除组表的操作 |
|
失败原因 |
You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_METERTABLE_OP |
|
日志内容 |
A meter table entry was deleted on device $1: $2 |
|
参数解释 |
$1：设备IP地址 $2：Meter表ID信息 |
|
举例 |
A meter table entry was deleted on device 192.168.133.68: {“meter_id: 3”} |
|
日志说明 |
用户进行了删除Meter表的操作 |
|
失败原因 |
You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CHANGE_DEVICE_FAILSAFE_OP |
|
日志内容 |
Devices changed to fail-safe mode. All controllers in the team are disallowed to accept OpenFlow connection requests. |
|
参数解释 |
无 |
|
举例 |
Devices changed to fail-safe mode. All controllers in the team are disallowed to accept OpenFlow connection requests. |
|
日志说明 |
用户进行了一键逃生的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Abnormal connections between the active leader and other controllers in the team：集群内主Leader控制组件与其他控制组件连接异常 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CHANGE_DEVICE_NORMAL_OP |
|
日志内容 |
Devices changed to normal mode. All controllers in the team are allowed to accept OpenFlow connection requests. |
|
参数解释 |
无 |
|
举例 |
Devices changed to normal mode. All controllers in the team are allowed to accept OpenFlow connection requests. |
|
日志说明 |
用户进行了一键恢复的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Abnormal connections between the active leader and other controllers in the team：集群内主Leader控制组件与其他控制组件连接异常 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
MODIFY_INTERFACE_STATUS_BY_INDEX_OP |
|
日志内容 |
Modified interface status by index: $1 |
|
参数解释 |
$1：端口信息 |
|
举例 |
Modified interface status by index: IP: [1.1.1.1] Interface Index: [1, 2, 3] Shutdown: [true] |
|
日志说明 |
用户通过端口号查询到指定端口，并对该端口进行了打开或关闭的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置恢复未完成 · The is_shut_down parameter is required：接口上下线参数不允许为空 · Invalid IP address：IP地址不合法 · Internal server error：内部错误 · Invalid JSON format：无效的JSON格式 · The is_shut_down parameter value must be true or false, which is case insensitive：接口开启关闭参数的取值为true或false，且不区分大小写 · The controller is not the active leader：该控制组件不是主Leader · The port ID is required：端口号不允许为空 · Invalid port ID：无效的端口号 · Unsupported device type：该设备的设备类型不支持 · The specified device doesn't exist：指定的设备不存在 · You have no privilege to perform this operation：用户无权限执行此操作 · The specified port doesn't exist：指定的端口不存在 |
|
关键字 |
CHANGE_SINGLE_DEVICE_FAILSAFE_OP |
|
日志内容 |
OpenFlow device with data path ID $1 and IP $2 switched to fail-safe mode. |
|
参数解释 |
$1: Datapath ID $2: 设备的IP地址 |
|
举例 |
OpenFlow device with data path ID 00:03:00:0c:29:43:67:ce and IP 98.0.50.19 switched to fail-safe mode. |
|
日志说明 |
用户对指定OpenFlow设备进行了逃生的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Abnormal connections between the active leader and other controllers in the team：集群内主Leader控制组件与其他控制组件连接异常 · Please specify the device data path ID：设备Datapath ID不能为空 · Invalid device data path ID：无效的设备Datapath ID · Invalid JSON format：无效的JSON格式 · The request is invalid：传入的JSON串错误 · The value of the is_connect field can only be true or false：is_connect字段取值仅支持true和false · Failed to synchronize data on controllers {IP} to the database：控制组件{IP}向数据库中同步数据失败 · Cannot perform operations on devices when the fail-safe mode is enabled：逃生模式下不允许对设备进行操作 · The controller is not the active leader：该控制组件不是主Leader · Invalid device ID：无效的设备ID · Invalid IP address：无效的IP地址 · Internal server error：内部错误 |
|
关键字 |
CHANGE_SINGLE_DEVICE_NORMAL_OP |
|
日志内容 |
OpenFlow device with data path ID $1 and IP $2 switched to normal mode. |
|
参数解释 |
$1: Datapath ID $2: 设备的IP地址 |
|
举例 |
OpenFlow device with data path ID 00:03:00:0c:29:43:67:ce and IP 98.0.50.19 switched to normal mode. |
|
日志说明 |
用户对指定OpenFlow设备进行了恢复的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Abnormal connections between the active leader and other controllers in the team：集群内主Leader控制组件与其他控制组件连接异常 · Please specify the device data path ID：设备Datapath ID不能为空 · Invalid device data path ID：无效的设备Datapath ID · Invalid JSON format：无效的JSON格式 · The request is invalid：传入的JSON串错误 · The value of the is_connect field can only be true or false：is_connect字段取值仅支持true和false · Failed to synchronize data on controllers {IP} to the database：控制组件{IP}向数据库中同步数据失败 · Cannot perform operations on devices when the fail-safe mode is enabled：逃生模式下不允许对设备进行操作 · The controller is not the active leader：该控制组件不是主Leader · Invalid device ID：无效的设备ID · Invalid IP address：无效的IP地址 · Internal server error：内部错误 |
|
关键字 |
CHANGE_DEVICES_FAILSAFE_OP |
|
日志内容 |
Bulk switched to fail-safe mode:$1. |
|
参数解释 |
$1：批量操作信息 |
|
举例 |
Bulk switched to fail-safe mode: totalNum:[40], successNum:[1], failedNum:[39]. |
|
日志说明 |
用户进行了批量逃生OpenFlow设备的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Abnormal connections between the active leader and other controllers in the team：集群内主Leader控制组件与其他控制组件连接异常 · Failed to synchronize data on controllers {IP} to the database：控制组件{IP}向数据库中同步数据失败 · Cannot perform operations on devices when the fail-safe mode is enabled：逃生模式下不允许对设备进行操作 · The controller is not the active leader：该控制组件不是主Leader · Internal server error：内部错误 · Invalid JSON format：无效的JSON格式 · The value of the is_connect field can only be true or false：is_connect字段取值仅支持true和false · The is_connect parameter cannot be empty：is_connect字段不能为空 · The is_escape parameter value must be true or false：is_escape字段取值仅支持true和false · The is_escape parameter cannot be empty：is_escape字段不能为空 · The device_ip parameter is invalid：device_ip字段非法 · The device_ip parameter cannot be empty：device_ip字段不能为空 · The dpid parameter is invalid：dpid字段非法 · The dpid parameter cannot be empty：dpid字段不能为空 · The specified devices have been disconnected from the controller：指定设备已断开连接 · The connections to the specified devices have restored：指定设备已恢复连接 · Failed to configure the blackhole route：黑洞路由配置失败 |
|
关键字 |
CHANGE_DEVICES_NORMAL_OP |
|
日志内容 |
Bulk switched to normal mode:$1. |
|
参数解释 |
$1：批量操作信息 |
|
举例 |
Bulk switched to normal mode: totalNum:[40], successNum:[1], failedNum:[39]. |
|
日志说明 |
用户进行了批量恢复OpenFlow设备的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Abnormal connections between the active leader and other controllers in the team：集群内主Leader控制组件与其他控制组件连接异常 · Failed to synchronize data on controllers {IP} to the database：控制组件{IP}向数据库中同步数据失败 · Cannot perform operations on devices when the fail-safe mode is enabled：逃生模式下不允许对设备进行操作 · The controller is not the active leader：该控制组件不是主Leader · Internal server error：内部错误 · Invalid JSON format：无效的JSON格式 · The value of the is_connect field can only be true or false：is_connect字段取值仅支持true和false · The is_connect parameter cannot be empty：is_connect字段不能为空 · The is_escape parameter value must be true or false：is_escape字段取值仅支持true和false · The is_escape parameter cannot be empty：is_escape字段不能为空 · The device_ip parameter is invalid：device_ip字段非法 · The device_ip parameter cannot be empty：device_ip字段不能为空 · The dpid parameter is invalid：dpid字段非法 · The dpid parameter cannot be empty：dpid字段不能为空 · The specified devices have been disconnected from the controller：指定设备已断开连接 · The connections to the specified devices have restored：指定设备已恢复连接 · Failed to configure the blackhole route：黑洞路由配置失败 |
本节介绍Region模块输出的操作日志信息。
|
关键字 |
CREATE_REGION_OP |
|
日志内容 |
Created region: $1 |
|
参数解释 |
$1：Region配置信息 |
|
举例 |
Created region: Name:region1 Region ID:fdd9f2d3-d2b2-4afe-942f-e6943b54e259 DenyvSwitch:false Master:192.168.56.153 Subordinate: 192.168.56.154 ManagedNodeSubnets: 192.168.38.25/24 192.168.39.25/24 |
|
日志说明 |
用户进行了创建Region的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The team doesn't exist：Team未创建 · Incorrect controller IP address：Region内控制组件的IP地址不正确 · The region name is already used：指定的Region名称已存在 · The controller was already in a region：控制组件已经属于某一Region，不能属于其它Region · The controller is not the active leader：该控制组件不是主Leader · Incorrect JSON format：Request请求中JSON串格式不正确 · The request can't be null：Request请求为空 · Incorrect controller name：控制组件名称不正确 · The master IP address must be different from the subordinate IP address：Region中主用控制组件IP地址和备用控制组件IP地址相同 · Incorrect IP address or mask format for the managed node subnets：管理设备网段的IP地址或掩码格式错误 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_REGION_OP |
|
日志内容 |
Deleted region:$1 |
|
参数解释 |
$1：Region配置信息 |
|
举例 |
Deleted region: Name: region1 Region ID: fdd9f2d3-d2b2-4afe-942f-e6943b54e259 DenyvSwitch:false Master:192.168.56.153 Subordinate: 192.168.56.154 ManagedNodeSubnets: 192.168.38.25/24 192.168.39.25/24 |
|
日志说明 |
用户进行了删除Region的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Incorrect JSON format：request请求中JSON串格式不正确 · The region does not exist：Region不存在 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_REGION_OP |
|
日志内容 |
Updated region:$1 |
|
参数解释 |
$1：Region配置信息 |
|
举例 |
Updated region: Name: region1 Region ID: fdd9f2d3-d2b2-4afe-942f-e6943b54e259 DenyvSwitch:false Master:192.168.56.153 Subordinate: 192.168.56.154 ManagedNodeSubnets: 192.168.38.25/24 192.168.39.25/24 |
|
日志说明 |
用户进行了更新Region的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The region does not exist：Region不存在 · The controller is not the active leader：该控制组件不是主Leader · Incorrect JSON format：request请求中JSON串格式不正确 · The request can't be null：request请求为空 · The input region information was incorrect ：输入Region信息不匹配 · Incorrect IP address or mask format for the managed node subnets：管理设备网段的IP地址或掩码格式错误 · You have no privilege to perform this operation：用户无权限执行此操作 |
本节介绍路由配置模块输出的操作日志信息。
|
关键字 |
ADD_BGP_INSTANCE_OP |
|
日志内容 |
Added BGP instance: $1. |
|
参数解释 |
$1：BGP实例信息 |
|
举例 |
Added BGP instance: { "router_id":"1.1.1.1", "as":"1", "keepalive":60, "hold_time":180, "controller":"192.168.109.202" }. |
|
日志说明 |
用户进行了配置控制组件的BGP实例的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Please specify a controller IP address：必须指定控制组件IP · Invalid IP address：无效的IP · Please specify a router ID：Router ID必选 · Invalid router ID：无效的Router ID · Please specify an AS number：AS必选 · Invalid AS number：无效的AS · Invalid keepalive interval：无效的会话保活时间 · Invalid hold time：无效的会话保持时间 · The hold time must be at least three times the keepalive interval：会话保持时间必须大于会话保活时间的3倍 · Failed to issue configuration to Quagga：Quagga下发配置失败 · The BGP instance already exists：BGP实例已存在 · Internal system error：系统内部错误 · Operation failed because the user role doesn't have the permission：当前用户无权限执行此操作 |
|
关键字 |
DEL_BGP_INSTANCE_OP |
|
日志内容 |
Deleted BGP instance from $1 |
|
参数解释 |
$1：目标控制组件IP |
|
举例 |
Deleted BGP instance from 192.168.109.202. |
|
日志说明 |
用户进行了删除控制组件的BGP配置的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid IP address：无效的IP · The BGP instance does not exist：BGP实例不存在 · Failed to issue configuration to Quagga：Quagga下发配置失败 · Internal system error：系统内部错误 · Operation failed because the user role doesn't have the permission：当前用户无权限执行此操作 |
|
关键字 |
ADD_BGP_NETWORK_OP |
|
日志内容 |
Added BGP network route: $1. |
|
参数解释 |
$1：Network信息 |
|
举例 |
Added BGP network route: { "controller":"192.168.109.202", "network":"3.3.3.3/24" }. |
|
日志说明 |
用户进行了增加BGP发布的本地网段路由的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Please specify a controller IP address：必须指定控制组件IP · Invalid IP address：无效的IP · Please specify a network address：Network IP必选 · Invalid network address：无效的Network · Invalid network mask：无效的掩码 · The specified network already exists：指定的Network已存在 · The BGP instance does not exist：BGP实例不存在 · Failed to issue configuration to Quagga：Quagga下发配置失败 · Internal system error：系统内部错误 · Operation failed because the user role doesn't have the permission：当前用户无权限执行此操作 |
|
关键字 |
DELETE_BGP_NETWORK_OP |
|
日志内容 |
Deleted BGP network route: $1. |
|
参数解释 |
$1：Network信息 |
|
举例 |
Deleted BGP network route: { "controller":"192.168.109.202", "network":"3.3.3.0/24" }. |
|
日志说明 |
用户进行了删除控制组件的BGP发布的本地网段路由的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Please specify a controller IP address：必须指定控制组件IP · Invalid IP address：无效的IP · Please specify a network address：Network IP必选 · Invalid network address：无效的Network · Invalid network mask：无效的掩码 · The specified network does not exist：指定的Network不存在 · The BGP instance does not exist：BGP实例不存在 · Failed to issue configuration to Quagga：Quagga下发配置失败 · Internal system error：系统内部错误 · Operation failed because the user role doesn't have the permission：当前用户无权限执行此操作 |
|
关键字 |
ADD_BGP_NEIGHBOR_OP |
|
日志内容 |
Added BGP neighbor: $1. |
|
参数解释 |
$1：BGP邻居信息 |
|
举例 |
Added BGP neighbor: { "controller":"192.168.109.202", "ip":"12.0.0.0", "remote_as":3, "filter":"in" }. |
|
日志说明 |
用户进行了配置BGP邻居的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Please specify a controller IP address：必须指定控制组件IP · Invalid IP address：无效的IP · Please specify a neighbor IP address：Neighbor IP必选 · Invalid neighbor IP address：无效的Neighbor IP · Please specify the remote AS number for the neighbor：邻居的远端AS必选 · Invalid remote AS number for the neighbor：无效的邻居远端AS · Please specify the filtering policy setting for the neighbor：邻居filter-list必选 · Invalid filtering policy setting for the neighbor：无效的邻居filter-list · The BGP neighbor already exists：BGP邻居已存在 · The BGP instance does not exist：BGP实例不存在 · Failed to issue configuration to Quagga：Quagga下发配置失败 · Internal system error：系统内部错误 · Operation failed because the user role doesn't have the permission：当前用户无权限执行此操作 |
|
关键字 |
DELETE_BGP_NEIGHBOR_OP |
|
日志内容 |
Deleted BGP neighbor: $1. |
|
参数解释 |
$1：BGP邻居信息 |
|
举例 |
Deleted BGP neighbor: { "controller":"192.168.109.202", "ip":"12.0.0.0" }. |
|
日志说明 |
用户进行了删除控制组件BGP邻居的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Please specify a controller IP address：必须指定控制组件IP · Invalid IP address：无效的IP · Please specify a neighbor IP address：Neighbor IP必选 · The BGP neighbor does not exist：BGP邻居不存在 · The BGP instance does not exist：BGP实例不存在 · Failed to issue configuration to Quagga：Quagga下发配置失败 · Internal system error：系统内部错误 · Operation failed because the user role doesn't have the permission：当前用户无权限执行此操作 |
|
关键字 |
UPDATE_BGP_SESSION_OP |
|
日志内容 |
Updated BGP session settings: $1. |
|
参数解释 |
$1：BGP会话配置 |
|
举例 |
Updated BGP session settings: { "keepalive":"32", "hold_time":"50000", "controller":"192.168.109.202" }. |
|
日志说明 |
用户进行了更新控制组件BGP会话配置的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Please specify a controller IP address：必须指定控制组件IP · Invalid IP address：无效的IP · Invalid keepalive interval：无效的会话保活时间 · Invalid hold time：无效的会话保持时间 · The hold time must be at least three times the keepalive interval：会话保持时间必须大于会话保活时间的3倍 · The BGP instance does not exist：BGP实例不存在 · Failed to issue configuration to Quagga：Quagga下发配置失败 · Internal system error：系统内部错误 · Operation failed because the user role doesn't have the permission：当前用户无权限执行此操作 |
|
关键字 |
ADD_OSPF_INSTANCE_OP |
|
日志内容 |
Added OSPF instance: $1. |
|
参数解释 |
$1：OSPF实例信息 |
|
举例 |
Added OSPF instance: { "router_id": "192.168.109.89", "auth": "MD5", "keyId": "2", "passwd": "MjM0NTY3OA==", "controller": "109.168.10.2" }. |
|
日志说明 |
用户进行了配置控制组件OSPF实例的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Please specify a controller IP address：必须指定控制组件IP · Invalid IP address：无效的IP · Please specify a router ID：Router ID必选 · Invalid router ID：无效的Router ID · You must select an authentication mode for the OSPF instance：验证模式必选 · Invalid authentication mode：无效的验证模式 · You must enter a password when the authentication mode is MD5：MD5验证模式下必须配置密码 · You must enter a key ID when the authentication mode is MD5：MD5验证模式下密钥ID必选 · The key ID must be an integer in the range of 1 to 255：无效的密钥ID · The OSPF instance already exists：OSPF实例已存在 · Failed to issue configuration to Quagga：Quagga下发配置失败 · Internal system error：系统内部错误 · Operation failed because the user role doesn't have the permission：当前用户无权限执行此操作 |
|
关键字 |
DEL_OSPF_INSTANCE_OP |
|
日志内容 |
Deleted OSPF instance from $1. |
|
参数解释 |
$1：控制组件IP |
|
举例 |
Deleted OSPF instance from 192.168.109.202. |
|
日志说明 |
用户进行了删除控制组件OSPF配置的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid IP address：无效的IP · The OSPF instance does not exist：OSPF实例不存在 · Failed to issue configuration to Quagga：Quagga下发配置失败 · Internal system error：系统内部错误 · Operation failed because the user role doesn't have the permission：当前用户无权限执行此操作 |
|
关键字 |
ADD_OSPF_NETWORK_OP |
|
日志内容 |
Added OSPF network route: $1. |
|
参数解释 |
$1：OSPF Network信息 |
|
举例 |
Added OSPF network route: { "area":"76756", "ifname":"", "network":"2.0.0.0/8", "controller":"192.168.109.201" }. |
|
日志说明 |
用户进行了配置控制组件的OSPF网段路由的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Please specify a controller IP address：必须指定控制组件IP · Invalid IP address：无效的IP · Please specify an area ID：Area必选 · Invalid area ID：无效的Area · Please specify a network address：Network IP必选 · Invalid network address：无效的Network · Invalid network mask：无效的掩码 · Please specify an interface：接口必选 · Invalid interface：无效的接口 · The OSPF instance does not exist：OSPF实例不存在 · The specified network already exists：指定的Network已存在 · Failed to issue configuration to Quagga：Quagga下发配置失败 · Internal system error：系统内部错误 · Operation failed because the user role doesn't have the permission：当前用户无权限执行此操作 |
|
关键字 |
DEL_OSPF_NETWORK_OP |
|
日志内容 |
Deleted OSPF network route: $1. |
|
参数解释 |
$1：OSPF Network信息 |
|
举例 |
Deleted OSPF network route: { "network":"2.0.0.0/8", "controller":"192.168.109.201" }. |
|
日志说明 |
用户进行了删除控制组件的OSPF网段路由的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Please specify a controller IP address：必须指定控制组件IP · Invalid IP address：无效的IP · Please specify a network address：Network IP必选 · Invalid network address：无效的Network · Invalid network mask：无效的掩码 · Please specify an interface：接口必选 · Invalid interface：无效的接口 · The OSPF instance does not exist：OSPF实例不存在 · The specified network does not exist：指定的Network不存在 · Failed to issue configuration to Quagga：Quagga下发配置失败 · Internal system error：系统内部错误 · Operation failed because the user role doesn't have the permission：当前用户无权限执行此操作 |
|
关键字 |
ADD_OSPF_AREA_OP |
|
日志内容 |
Added OSPF area: $1. |
|
参数解释 |
$1：OSPF Area信息 |
|
举例 |
Added OSPF area: { "area": "1.1.1.1", "enableAuth": true, "nssa": "translate-candidate", "controller": "192.168.0.1" }. |
|
日志说明 |
用户进行了配置控制组件的OSPF区域的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Please specify a controller IP address：必须指定控制组件IP · Invalid IP address：无效的IP · Please specify an area ID：Area必选 · Invalid area ID：无效的Area · Please specify the NSSA setting for the area：Area的NSSA必选 · Invalid NSSA setting for the area：无效的Area NSSA · The OSPF instance does not exist：OSPF实例不存在 · The area already exists：Area已经存在 · You must select an option other than None for NSSA when the authentication mode is none：验证模式为None的情况下NSSA不允许为none · Failed to issue configuration to Quagga：Quagga下发配置失败 · Internal system error：系统内部错误 · Operation failed because the user role doesn't have the permission：当前用户无权限执行此操作 |
|
关键字 |
DEL_OSPF_AREA_OP |
|
日志内容 |
Deleted OSPF area: $1. |
|
参数解释 |
$1：OSPF Area信息 |
|
举例 |
Deleted OSPF area: { "area":"3.47.53.27", "controller":"192.168.109.201" }. |
|
日志说明 |
用户进行了删除控制组件的OSPF区域的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Please specify a controller IP address：必须指定控制组件IP · Invalid IP address：无效的IP · Please specify an area ID：Area必选 · Invalid area ID：无效的Area · The area does not exist：Area不存在 · Failed to issue configuration to Quagga：Quagga下发配置失败 · Internal system error：系统内部错误 · Operation failed because the user role doesn't have the permission：当前用户无权限执行此操作 |
本节介绍SNMP模块输出的操作日志信息。
|
关键字 |
CREATE_TRADITIONAL_NE_OP |
|
日志内容 |
Created traditional NE: $1 |
|
参数解释 |
$1：传统网元的配置信息 |
|
举例 |
Created traditional NE: IP: 192.168.9.198 MAC: 74:25:8a:c4:e2:de Read community: public Write community: private Controller IP: 192.168.89.155 Access attribute: access Status: Inactive |
|
日志说明 |
用户进行了增加传统网元的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Invalid network element IP address：无效的网元IP地址 · The traditional network element at X.X.X.X already exists：网元IP地址为X.X.X.X的传统网元已存在 · Invalid controller IP address：无效的控制组件IP地址 · The controller IP address doesn't exist in the team：指定的控制组件IP地址在集群内不存在 · The IP address for a controller in standalone mode must be 127.0.0.1：独立运行模式下，控制组件IP地址只能为127.0.0.1 · Invalid access attribute：无效的接入属性 · The traditional network element has been added to the controller by using X.X.X.X：该传统网元已通过IP地址X.X.X.X增加到控制组件 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_TRADITIONAL_NE_OP |
|
日志内容 |
Updated traditional NE: $1 |
|
参数解释 |
$1：传统网元的配置信息 |
|
举例 |
Updated traditional NE: IP: 192.168.9.198 MAC: 74:25:8a:c4:e2:de Read community: public Write community: private Controller IP: 192.168.89.155 Access attribute: access Status: Inactive |
|
日志说明 |
用户进行了修改传统网元的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Invalid network element IP address：无效的网元IP地址 · The network element IP address doesn't exist：指定的网元IP地址不存在 · Invalid controller IP address：无效的控制组件IP地址 · The controller IP address doesn't exist in the team：指定的控制组件IP在集群内不存在 · The IP address for a controller in standalone mode must be 127.0.0.1：独立运行模式下，控制组件IP地址只能为127.0.0.1 · Invalid access attribute：无效的接入属性 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_TRADITIONAL_NE_OP |
|
日志内容 |
Deleted traditional NE: $1 |
|
参数解释 |
$1：传统网元的IP地址 |
|
举例 |
Deleted traditional NE: 192.168.9.198 |
|
日志说明 |
用户进行了删除传统网元的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Invalid network element IP address：无效的网元IP地址 · The network element IP address doesn't exist：指定的网元IP地址不存在 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
START_SCAN_TRADITIONAL_NE_OP |
|
日志内容 |
Started scanning traditional NEs: $1 |
|
参数解释 |
$1：传统网元的自动发现配置 |
|
举例 |
Started scanning traditional NEs: Start IP: 192.168.125.0 End IP: 192.168.125.255 SNMP read community: public SNMP write community: private |
|
日志说明 |
用户进行了自动发现传统网元的操作 |
|
失败原因 |
You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
STOP_SCAN_TRADITIONAL_NE_OP |
|
日志内容 |
Stopped scanning traditional NEs |
|
参数解释 |
无 |
|
举例 |
Stopped scanning traditional NEs |
|
日志说明 |
用户进行了停止自动发现传统网元的操作 |
|
失败原因 |
You have no privilege to perform this operation：用户无权限执行此操作 |
本节介绍系统管理模块输出的操作日志信息。
|
关键字 |
BACKUP_OP |
|
日志内容 |
Backed up the configuration. |
|
参数解释 |
$1：备份的Session名，是用于标识本次备份操作的标识码 |
|
举例 |
Backed up the configuration. |
|
日志说明 |
用户进行了配置备份的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The operation requires the administrator privilege：需要管理员角色才能执行此操作 · Failed to create the backup file：生成备份文件失败 · The system is recovering the configuration：系统正在恢复配置 · The team to which the controller belongs has no active leader：当前控制组件所在集群不存在主Leader · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPLOAD_BACKUPFILE_OP |
|
日志内容 |
Uploaded the backup file. |
|
参数解释 |
无 |
|
举例 |
Uploaded the backup file. |
|
日志说明 |
用户进行了备份文件上传的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · The operation requires the administrator privilege：需要管理员角色才能执行此操作 · Invalid backup file format：上传的备份文件格式有误 · Invalid backup file content：上传的备份文件内容有误 · The active leader can't send the backup file to other controllers due to network errors：由于网络原因，主Leader控制组件将备份文件发送到其他控制组件失败 · The system is recovering the configuration：系统正在恢复配置 · The team to which the controller belongs has no active leader：当前控制组件所在集群不存在主Leader · Can’t upload the backup file because some controllers are down: $1, $2, $3：控制组件：$1，$2，$3状态为down，无法上传备份文件 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
RESTORE_OP |
|
日志内容 |
Restored the configuration. |
|
参数解释 |
无 |
|
举例 |
Restored the configuration |
|
日志说明 |
用户进行了配置恢复的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · The operation requires the administrator privilege：需要管理员角色才能执行此操作 · The backup file doesn't exist：指定的备份文件不存在 · The backup file doesn't include the required files：备份文件中不包含必须的文件 · The controller's IP address is not included in the team settings of the backup file：备份文件的集群配置中不包含本控制组件IP · The active leader can't restore the configuration of other controllers due to network errors：由于网络原因，主Leader控制组件不能对其它控制组件进行配置恢复 · The system is recovering the configuration：系统正在恢复配置 · The team to which the controller belongs has no active leader：当前控制组件所在集群不存在主Leader · Can’t perform configuration recovery because some controllers are down: $1, $2, $3：控制组件：$1，$2，$3状态为down，无法进行备份恢复操作 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DOWNLOAD_BACKUPFILE_OP |
|
日志内容 |
Downloaded the backup file. |
|
参数解释 |
无 |
|
举例 |
Downloaded the backup file. |
|
日志说明 |
备份文件下载成功 |
|
失败原因 |
当操作失败时，可能的原因如下： · The backup file doesn't exist：待下载的备份文件不存在 · The system is recovering the configuration：系统正在恢复配置 · The team to which the controller belongs has no active leader：当前控制组件所在集群不存在主Leader · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
MODIFY_BACKUPSET_OP |
|
日志内容 |
Modified settings for configuration backup. $1 |
|
参数解释 |
$1：备份参数配置信息 |
|
举例 |
Modified settings for configuration backup. {backupPath:"/opt/sdn/backupHistory/", reservation:"30", remoteIP:"192.168.138.60", prefix:"AAAA", status:"open", frequency:"PER_MONTH", week:"1", date:"15", time:"8:30"} |
|
日志说明 |
用户修改了备份功能的配置信息 |
|
失败原因 |
当操作失败时，可能的原因如下： · Illegal backup settings：修改的配置参数不合法 · The operation requires the administrator privilege：需要管理员角色才能执行此操作 · The controller is not the active leader：该控制组件不是主Leader · Not permitted to access the backup path：修改的备份路径，控制组件用户无权限访问 · Failed to save the settings：保存配置信息失败 · The system is recovering the configuration：系统正在恢复配置 · The team to which the controller belongs has no active leader：当前控制组件所在集群不存在主Leader · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
MODIFY_CONFIG_OP |
|
日志内容 |
Modified configuration: $1. |
|
参数解释 |
$1：组件名及配置项 |
|
举例 |
Modified configuration: Authentication Manager { ConnPoolMaxActive=4 AuthenticationProtocol=PAP SharedKey=****** AuthMode=local AAAServerIP=192.168.56.19 ConnPoolMaxIdle=1 CachedTokenIdle=900 }. |
|
日志说明 |
用户进行了修改组件配置项的操作。如果组件中包括密钥或密码配置项，该配置项的值以“******”表示 |
|
失败原因 |
当操作失败时，可能的原因如下： · Failed to update the configuration file：更新配置文件失败 · The existing team token must be deleted before you configure a new one：集群Token已存在，请先删除再修改集群Token · Invalid value for parameter $1：输入的配置项的值（$1）不合法 · Failed to encrypt the password or key：密钥或密码参数加密失败 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
RESTORE_CONFIG_OP |
|
日志内容 |
Restored configuration: $1. |
|
参数解释 |
$1：组件名及配置项。如果重置组件所有配置项的值，则只显示组件名 |
|
举例 |
Restored configuration: Authentication Manager { ConnPoolMaxActive=4 AuthenticationProtocol=PAP SharedKey=****** AuthMode=local AAAServerIP=192.168.56.19 ConnPoolMaxIdle=1 CachedTokenIdle=900 }. |
|
日志说明 |
用户进行了重置组件配置项为默认值的操作。如果组件中包括密钥或密码配置项，该配置项的值以“******”表示 |
|
失败原因 |
当操作失败时，可能的原因如下： · Can't delete the team token in team mode：集群模式下，无法删除集群Token · Failed to update the configuration file：更新配置文件失败 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPGRADE_PREPARE_OP |
|
日志内容 |
Prepared for upgrade: $1 |
|
参数解释 |
$1：进行升级准备的控制组件IP地址 |
|
举例 |
Prepared for upgrade |
|
日志说明 |
用户进行了升级准备的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid request：请求参数不合法 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
MODIFY_ALERTLOG_TRANSMISSION_OP |
|
日志内容 |
The alert log remote transmission mode was set to sending logs to the syslog server. |
|
参数解释 |
无 |
|
举例 |
The alert log remote transmission mode was set to sending logs to the syslog server. |
|
日志说明 |
用户进行系统日志配置修改的操作，开启Syslog日志服务器功能，系统日志将被发送到指定的日志服务器 |
|
失败原因 |
You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
MODIFY_AUDITLOG_TRANSMISSION_OP |
|
日志内容 |
The audit log remote transmission mode was set to sending logs to the syslog server. |
|
参数解释 |
无 |
|
举例 |
The audit log remote transmission mode was set to sending logs to the syslog server. |
|
日志说明 |
用户进行操作日志配置修改的操作，开启Syslog日志服务器功能，操作日志将被发送到指定的日志服务器 |
|
失败原因 |
You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
ENTER_UPGRADE_MODE_OP |
|
日志内容 |
Enter upgrade mode. |
|
参数解释 |
无 |
|
举例 |
Enter upgrade mode. |
|
日志说明 |
用户进行了进入升级模式的操作 |
|
失败原因 |
You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
QUIT_UPGRADE_MODE_OP |
|
日志内容 |
Quit upgrade mode. |
|
参数解释 |
无 |
|
举例 |
Quit upgrade mode. |
|
日志说明 |
用户进行了退出升级模式的操作 |
|
失败原因 |
You have no privilege to perform this operation：用户无权限执行此操作 |
本节介绍集群模块输出的操作日志信息。
|
关键字 |
CREATE_TEAM_OP |
|
日志内容 |
Created team: $1 |
|
参数解释 |
$1：集群配置信息 |
|
举例 |
Created team: Name: TestCluster1 IP: 192.168.40.40 Mask: 255.255.255.0 Mode:1 Version: 1404159495844 Team ID: f892866f-0ec9-4ef0-a0a8-6df783ef7b19 Leaders: [ {Name: leader1, IP: 192.168.56.147, Priority: 200, Network_device: eth0, Server ID: 1}, {Name: leader2, IP: 192.168.56.148, Priority: 100, Network_device: eth1, Server ID: 2} ] Members: [ {Name: member, IP: 192.168.40.146, Priority: 1016, Network_device: , Server ID: 5} ] |
|
日志说明 |
用户进行了创建集群的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The team contained only one leader：无法创建只有一个Leader的集群 · The controller was not a leader：当前所操作的控制组件没有配置为Leader · Team IP address and member IP address must be different：集群IP地址和成员控制组件IP地址不能相同 · Member IP addresses must be different：成员控制组件IP地址不能相同 · Member names must be different：成员名称不能相同 · Leader priorities must be different：Leader角色控制组件优先级不能相同 · The number of controllers exceeded the upper limit (32)：控制组件数目超过32的上限数 · Server processing error：服务器处理失败 · The versions of the controllers are inconsistent：用于创建集群的各控制组件版本不完全一致 · The team token is not configured for the controller：控制组件未配置集群Token · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_TEAM_OP |
|
日志内容 |
Deleted team: $1 |
|
参数解释 |
$1：集群配置信息 |
|
举例 |
Deleted team: Name: TestCluster1 IP: 192.168.40.40 |
|
日志说明 |
用户进行了删除集群的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The team didn't exist：不存在该集群 · The controller was not the active leader：该控制组件不是主Leader · Server processing error：服务器处理失败 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
MODIFY_TEAM_OP |
|
日志内容 |
Modified team: $1 |
|
参数解释 |
$1：集群配置修改信息 |
|
举例 |
Modified team: Name:TestCluster1->TestCluster2 IP:192.168.35.11->192.168.35.12 Mask:255.255.255.0->255.255.0.0 |
|
日志说明 |
用户进行了修改集群的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller was not the active leader：该控制组件不是主Leader · The team didn't exist：不存在该集群 · Server processing error：服务器处理失败 · The team name is invalid：集群名称无效 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
ADD_MEMBER_OP |
|
日志内容 |
Added member: $1 |
|
参数解释 |
$1：成员信息 |
|
举例 |
Added member: Name:leader1 IP:192.168.56.147 |
|
日志说明 |
用户进行了添加集群成员的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller was not the active leader：该控制组件不是主Leader · The team didn't exist：不存在该集群 · The member IP address must be different from the team IP address：成员控制组件IP地址和集群IP地址不能相同 · The member IP address was already used：成员控制组件IP地址和已有成员控制组件IP地址相同 · The member name was already used：成员控制组件名称和已有成员名称相同 · Server processing error：服务器处理失败 · The version of the selected controller is different than the team：待加入集群的控制组件版本与集群已有成员控制组件版本不一致 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_MEMBER_OP |
|
日志内容 |
Deleted member: $1 |
|
参数解释 |
$1：成员信息 |
|
举例 |
Deleted member: Name:leader1 IP:192.168.56.147 |
|
日志说明 |
用户进行了删除集群成员的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller was not the active leader or the member to be deleted：请登录主Leader或需退出集群的控制组件，进行控制组件的删除操作 · The member didn't exist：不存在该成员控制组件 · A leader can't be deleted：无法删除该Leader控制组件 · The member was in a region：集群成员控制组件处于Region中 · Server processing error：服务器处理失败 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
MODIFY_MEMBER_OP |
|
日志内容 |
Modified member: $1 |
|
参数解释 |
$1：成员修改信息 |
|
举例 |
Modified member: Name:member1->member2 IP:192.168.35.11 Network_device:eth0->eth1 |
|
日志说明 |
用户进行了修改集群成员的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller was not the active leader：该控制组件不是主Leader · NIC for the member can't be changed：无法在Member角色控制组件上修改NIC属性 · Server processing error：服务器处理失败 · The controller name is invalid：控制组件名称无效 · The member name was already used：成员控制组件名称和已有成员名称相同 · You have no privilege to perform this operation：用户无权限执行此操作 |
本节介绍拓扑管理模块输出的操作日志信息。
|
关键字 |
UPDATE_DEVICE_INFO_OP |
|
日志内容 |
Updated device: $1 |
|
参数解释 |
$1：设备信息 |
|
举例 |
Updated device: IP address: 192.168.9.198 Datapath ID: 00:00:74:25:8a:c4:e2:de Asset number: 201605181600 Device description: H3C Comware Platform Software, Software Version 7.1.070, ESS 2505P01 Location: A13-A13 Function: core Remarks: description Device name: 201-98 Status: Inactive |
|
日志说明 |
用户进行了修改设备清单中设备信息的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The device doesn't exist：该设备不存在 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_DEVICE_LAYER_OP |
|
日志内容 |
Updated the layer for device (IP address $1 and datapath ID $2): $3. |
|
参数解释 |
$1：设备的IP地址 $2：设备的Datapath ID $3：设备的接入属性，取值包括：access、convergence、core |
|
举例 |
Updated the layer for device (IP address 192.168.9.198 and datapath ID 00:00:74:25:8a:c4:e2:de): core. |
|
日志说明 |
用户进行了修改物理拓扑页面指定设备的接入属性的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The device doesn't exist：该设备不存在 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_INACTIVE_LINK_OP |
|
日志内容 |
Deleted an inactive link. Link information: $1 |
|
参数解释 |
$1：设备的下线链路信息 |
|
举例 |
Deleted an inactive link. Link information: From: Port GigabitEthernet1/0/3 on device (IP address 192.168.150.44 and datapath ID 00:00:68 b:10 a:04:00). To: Port GigabitEthernet1/0/5 on device (IP address 192.168.150.42 and datapath ID 00:00:94:e2:4e:53:02:00). |
|
日志说明 |
用户进行了删除设备的下线链路的操作 |
|
失败原因 |
You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_PORT_THRESHOLD_OP |
|
日志内容 |
Updated port thresholds: $1 |
|
参数解释 |
$1：接口阈值信息 |
|
举例 |
Updated port monitor thresholds: Inbound bandwidth usage: 12% Outbound bandwidth usage: 32% Inbound error packet rate: 43% Outbound error packet rate: 43% Inbound packet loss rate: 54% Outbound packet loss rate: 65% |
|
日志说明 |
用户进行了修改设备接口阈值的操作 |
|
失败原因 |
You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CLEAR_DEVICE_EVENTS_OP |
|
日志内容 |
Clear events on device: $1. |
|
参数解释 |
$1：设备的IP地址 |
|
举例 |
Clear events on device: 192.168.5.3. |
|
日志说明 |
用户进行了清除指定设备的事件的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The device doesn't exist：该设备不存在 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CLEAR_ALL_DEVICES_EVENTS_OP |
|
日志内容 |
Clear events on all devices. |
|
参数解释 |
无 |
|
举例 |
Clear events on all devices. |
|
日志说明 |
用户进行了清除所有设备的事件的操作 |
|
失败原因 |
You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_SERVER_LINK_OP |
|
日志内容 |
Created server link: $1 |
|
参数解释 |
$1：服务器链路的信息 |
|
举例 |
Created server link: device_name: [1] system_name: [2] mac: [52:5c:60:1d:08:00] phy_port: [3] port_name: [GE2/0/3] |
|
日志说明 |
用户进行了增加服务器链路的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · You have no privilege to perform this operation：用户无权限执行此操作 · The specified server link already exists：指定的服务器链路已存在 · Internal error：内部错误 |
|
关键字 |
DEL_SERVER_LINK_OP |
|
日志内容 |
Deleted server link: $1 |
|
参数解释 |
$1：服务器链路的信息 |
|
举例 |
Deleted server link: device_name: [1] system_name: [2] mac: [52:5c:60:1d:08:00] phy_port: [3] |
|
日志说明 |
用户进行了删除服务器链路的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · You have no privilege to perform this operation：用户无权限执行此操作 · The specified server link does not exist：指定的服务器链路不存在 · Internal error：内部错误 |
|
关键字 |
IMPORT_SERVER_LINK_OP |
|
日志内容 |
Imported server links from “$1”, successfully imported links: $2, failed imported links: $3. |
|
参数解释 |
$1：模板名称 $2：导入服务器链路的成功数 $3：导入服务器链路的失败数 |
|
举例 |
Imported server links from "批量导入服务器链路样例import.xlsx", successfully imported links: 5, failed imported links: 19. |
|
日志说明 |
用户进行了导入服务器链路的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · You have no privilege to perform this operation：用户无权限执行此操作 · The specified server link does not exist：指定的服务器链路不存在 · Internal error：内部错误 · Failed to parse the file：文件解析失败 · The uploaded file content is invalid：上传的文件内容无效 · The uploaded file type is invalid：上传的文件类型无效 · The file content is required：文件内容不能为空 · Invalid template. Please download the latest template：模板不匹配，请使用最新模板 |
|
关键字 |
CREATE_LINK_OP |
|
日志内容 |
Created inter-device link: $1 |
|
参数解释 |
$1：设备间链路的信息 |
|
举例 |
Created inter-device link: Local device:[103] Local interface:[WGE1/0/1] Remote device:[102] Remote interface:[WGE1/0/2]. |
|
日志说明 |
用户进行了增加设备间链路的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · You have no privilege to perform this operation：用户无权限执行此操作 · Internal error：内部错误 |
|
关键字 |
DEL_LINK_OP |
|
日志内容 |
Deleted inter-device link: $1 |
|
参数解释 |
$1：设备间链路的信息 |
|
举例 |
Deleted inter-device link: Local device:[102] Local interface:[WGE1/0/19] Remote device:[103] Remote interface:[WGE1/0/15]. |
|
日志说明 |
用户进行了删除设备间链路的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · You have no privilege to perform this operation：用户无权限执行此操作 · Internal error：内部错误 |
|
关键字 |
IMPORT_DEVICE_LINK_OP |
|
日志内容 |
Imported device links from “$1”, successfully imported links: $2, failed imported links: $3. |
|
参数解释 |
$1：模板名称 $2：导入设备间链路的成功数 $3：导入设备间链路的失败数 |
|
举例 |
Imported device links from "Deviceimport设备链路.xlsx", successfully imported links: 6, failed imported links: 18. |
|
日志说明 |
用户进行了导入设备间链路的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · You have no privilege to perform this operation：用户无权限执行此操作 · Internal error：内部错误 · Failed to parse the file：文件解析失败 · The uploaded file content is invalid：上传的文件内容无效 · The uploaded file type is invalid：上传的文件类型无效 · The file content is required：文件内容不能为空 · Invalid template. Please download the latest template：模板不匹配，请使用最新模板 |
本节介绍用户管理模块输出的操作日志信息。
|
关键字 |
ADD_USER_OP |
|
日志内容 |
Added a user:$1. |
|
参数解释 |
$1：增加用户的用户名 |
|
举例 |
Added a user:11. |
|
日志说明 |
用户进行了增加用户的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid username：输入的用户名无效 · Invalid role：输入的用户角色无效 · The username already exists：该用户名已存在 · The password length is out of range or the password contains only letters, digits, or special characters：密码长度范围不正确或未包含数字、字母和特殊字符中的两种类型 · The controller is not the active leader：当前设备不是Leader控制组件，无法进行此操作 · Incorrect format：格式错误 · Failed to add the user：用户添加失败 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_USER_OP |
|
日志内容 |
Deleted a user: $1. |
|
参数解释 |
$1：删除用户的用户名 |
|
举例 |
Deleted a user: 11. |
|
日志说明 |
用户进行了删除用户的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid username：输入的用户名无效 · No permission to delete itself：当前用户不能执行删除自己操作 · The controller is not the active leader：当前设备不是Leader控制组件，无法进行此操作 · Can't delete an online user：不允许删除在线用户 · Token aged：Token已老化 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CHANGE_PASSWORD_OP |
|
日志内容 |
Changed user $1's password. |
|
参数解释 |
$1：修改密码的用户 |
|
举例 |
Changed user 11's password. |
|
日志说明 |
用户进行了修改密码的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid username：输入的用户名无效 · Invalid old password：输入的旧密码无效 · The password length is out of range or the password contains only letters, digits, or special characters：密码长度范围不正确或未包含数字、字母和特殊字符中的两种类型 · Can't modify another user's password due to permission limit：权限不足，无法修改其他用户的密码 · The controller is not the active leader：当前设备不是Leader控制组件，无法进行此操作 · Token aged：Token已老化 · The user doesn’t exist：用户不存在 · Failed to update the user’s password：修改用户密码失败 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_USER_OP |
|
日志内容 |
Updated user configuration: $1 |
|
参数解释 |
$1：用户配置信息 |
|
举例 |
Updated user configuration: Username: sdn Password: ****** Role: sdn-admin Service logs to display: ARP, CON, NEM, VSM Lock state: unlock |
|
日志说明 |
用户进行了修改用户配置的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The user does not exist：用户不存在 · Invalid parameter for locking the user：输入的锁定值无效 · Invalid user role：输入的用户角色无效 · Invalid old password：输入的旧密码无效 · Invalid username：输入的用户名无效 · Incorrect format：格式错误 · The controller is not the active leader：该设备不是Leader控制组件，无法进行此操作 · Can't modify another user's configuration due to permission limit：权限不足，无法修改其他用户的配置 · Can't lock the current user：当前用户不能对自身执行锁定操作 · Can't modify the role of the current user.：当前用户不能对自身执行角色修改操作 · Can't change the types of service logs to display due to permission limit：权限不足，无法修改可查看业务日志类型 · The password length is out of range or the password contains only letters, digits, or special characters：密码长度范围不正确或未包含数字、字母和特殊字符中的两种类型 · Token aged：Token已老化 · Failed to update the user：修改用户失败 · Can't modify the configuration of other online users：不允许修改其它在线用户的配置 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
ADD_ROLE_OP |
|
日志内容 |
Added a role: $1. |
|
参数解释 |
$1：角色名称 |
|
举例 |
Added a role: role1. |
|
日志说明 |
用户进行了增加角色的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid role name：输入的角色名无效 · Invalid role rule：输入的权限规则无效 · Invalid description：输入的描述无效 · The role already exists：该角色名已存在 · You have no privilege to perform the operation：当前用户无权限执行此项操作 · The controller is not the active leader：当前设备不是Leader控制组件，无法进行此操作 · Incorrect format：格式错误 · Failed to add the role：角色添加失败 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_ROLE_OP |
|
日志内容 |
Updated role configuration: $1 |
|
参数解释 |
$1：角色配置信息 |
|
举例 |
Updated role configuration: Rolename: test2, Description:, RoleRules: { "rolerules": { "/lb/v2.0": { "details": [ { "access": "POST", "controlled": "/loadbalancers" } ], "module": "LBaaS v2.0", "type": "REST" }, "c-NetworkService": { "details": [ { "access": "R", "controlled": "n-LoadBalance" } ], "type": "UI" } } } |
|
日志说明 |
用户进行了修改角色配置的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · You have no privilege to perform the operation：当前用户无权限执行此项操作 · Incorrect format：格式错误 · The controller is not the active leader：当前设备不是Leader控制组件，无法进行此操作 · Invalid role name：输入的角色名无效 · Invalid role rule：输入的权限规则无效 · Invalid description：输入的描述信息无效 · Can't modify default roles：系统默认角色不允许修改 · The role doesn’t exist：该角色不存在 · Failed to update the role：修改角色失败 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_ROLE_OP |
|
日志内容 |
Deleted a role: $1. |
|
参数解释 |
$1：删除角色的角色名 |
|
举例 |
Deleted a role: 11. |
|
日志说明 |
用户进行了删除角色的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid role name：输入的角色名无效 · The controller is not the active leader：当前设备不是Leader控制组件，无法进行此操作 · Can't delete system default roles：系统默认角色不允许删除 · Can’t delete the role because it is already assigned to users：该角色已被授权给用户，不能删除 · You have no privilege to perform this operation：用户无权限执行此操作 |
本节介绍CZTP模块输出的操作日志信息。
|
关键字 |
ADD_NETWORK_MODEL_OP |
|
日志内容 |
Created network model: $1. |
|
参数解释 |
$1：网络模型信息 |
|
举例 |
Created network model { ID: [4ea337ff-d28d-42e0-bc90-dd398811d4bc] name: [network1] description: [] }. |
|
日志说明 |
用户创建了一个网络模型 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · The service does not exist.：指定的服务不存在 · The controller is not the active leader：该控制组件不是主Leader · ID is Invalid：无效的ID · The UUID already exists：UUID已存在 · The network model name already exists：网络模型名称已存在 · Please specify a name, a case-sensitive string of up to 255 characters. The name cannot contain only spaces. The name cannot start or end with a space：名称必选，最长255个字符，区分大小写，不允许全空格 · The description is case-sensitive string of up to 255 characters：描述最长255个字符，区分大小写 · The string is of up to 255 characters, and does not support less-than signs (<) or greater-than signs (>), and cannot contain only spaces：最长255个字符，不支持“<”和“>”，不支持全空格 · Please specify the valid type：类型字段不能为空 · Duplicate variable name：变量名重复 · You cannot edit or delete the model, because it has been specified in list planning：存在关联的清单规划，不允许修改或删除模型 · The specified model has been used by online template：指定模型被上线模板引用 · The network model name already exists：网络模型名称已存在 · A variable in a device group model already exists with the same name：存在变量名与设备组模型中变量名重复 · A variable in a device model already exists with the same name：存在变量名与设备模型中变量名重复 · A variable in an interconnect model already exists with the same name：存在变量名与互通模型中变量名重复 |
|
关键字 |
MOD_NETWORK_MODEL_OP |
|
日志内容 |
Updated network model: $1 |
|
参数解释 |
$1：网络模型信息 |
|
举例 |
Updated network model { ID: [4ea337ff-d28d-42e0-bc90-dd398811d4bc] name: [network1] description: [it is a network model] }. |
|
日志说明 |
用户修改了一个网络模型 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · The service does not exist.：指定的服务不存在 · The controller is not the active leader：该控制组件不是主Leader · ID is Invalid：无效的ID · Please specify a name, a case-sensitive string of up to 255 characters. The name cannot contain only spaces. The name cannot start or end with a space：名称必选，最长255个字符，区分大小写，不允许全空格 · The description is case-sensitive string of up to 255 characters：描述最长255个字符，区分大小写 · The string is of up to 255 characters, and does not support less-than signs (<) or greater-than signs (>), and cannot contain only spaces：最长255个字符，不支持“<”和“>”，不支持全空格 · Please specify the valid type：类型字段不能为空 · Duplicate variable name：变量名重复 · The configuration item does not exist：配置项不存在 · You cannot edit or delete the model, because it has been specified in list planning：存在关联的清单规划，不允许修改或删除模型 · The specified model has been used by online template：指定模型被上线模板引用 · The network model name already exists：网络模型名称已存在 · A variable in a device group model already exists with the same name：存在变量名与设备组模型中变量名重复 · A variable in a device model already exists with the same name：存在变量名与设备模型中变量名重复 · A variable in an interconnect model already exists with the same name：存在变量名与互通模型中变量名重复 · Variables referenced by device models or interconnect models cannot be deleted or renamed：被设备配置或互通配置引用的变量，不允许删除或修改名称 |
|
关键字 |
DEL_NETWORK_MODEL_OP |
|
日志内容 |
Deleted network model ID: [$1]. |
|
参数解释 |
$1：网络模型的UUID |
|
举例 |
Deleted network model ID: [45757617-d19e-42ad-a146-7918a3d74f28]. |
|
日志说明 |
用户删除了一个网络模型 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · The service does not exist.：指定的服务不存在 · The controller is not the active leader：该控制组件不是主Leader · The configuration item does not exist：配置项不存在 · You cannot delete the network model, because it contains device group models：该网络模型中存在未删除的设备组模型，不允许删除 · You cannot delete the network model, because it contains device models：该网络模型中存在未删除的设备模型，不允许删除 · You cannot delete the network model, because it contains interconnect models：该网络模型中存在未删除的互通模型，不允许删除 · Variables referenced by device models or interconnect models cannot be deleted or renamed：被设备配置或互通配置引用的变量，不允许删除或修改名称 · You cannot edit or delete the model, because it has been specified in list planning：存在关联的清单规划，不允许修改或删除模型 · The specified model has been used by online template：指定模型被上线模板引用 |
|
关键字 |
ADD_DEVICE_GROUP_MODEL_OP |
|
日志内容 |
Created device group model: $1 |
|
参数解释 |
$1：设备组模型信息 |
|
举例 |
Created device group model { ID: [ccf19104-4091-408e-871a-bd0ba0ba96f9] name: [leaf-group1] description: [] network_model_id: [45757617-d19e-42ad-a146-7918a3d74f28] device_role: [leaf] }. |
|
日志说明 |
用户创建了一个设备组 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · The service does not exist.：指定的服务不存在 · The controller is not the active leader：该控制组件不是主Leader · ID is Invalid：无效的ID · Please specify a name, a case-sensitive string of up to 255 characters. The name cannot contain only spaces. The name cannot start or end with a space：名称必选，最长255个字符，区分大小写，不允许全空格 · The description is case-sensitive string of up to 255 characters：描述最长255个字符，区分大小写 · Please specify the device role：设备角色不能为空 · The string is of up to 255 characters, and does not support less-than signs (<) or greater-than signs (>), and cannot contain only spaces：最长255个字符，不支持“<”和“>”，不支持全空格 · Please specify the valid type：类型字段不能为空 · Duplicate variable names exist in the device group model：设备组模型中存在重复的变量名 · For an IP pair allocation rule, you must specify existing variables in a model and make sure the variables are IP resource pool type：IP成对分配规则中的变量应该都是模型中变量，且类型只能是IP资源池类型 · The config param is not null and cannot exceed 255 characters：配置参数不能为空且不能超过255个字符 · You can configure IP pair allocation rules for variables only if they are the same type, which can be either IPv4 or IPv6 address pool：只有变量类型相同且为IPv4或者IPv6地址池中的一种时，可以为变量配置IP成对分配规则 · Format: IPv4 subnet mask as an integer (24-31) or IPv6 prefix length as an integer (112-127)：对于IPv4地址，掩码取值范围为24~31的整数；对于IPv6地址，前缀长度为112~127的整数 · The UUID already exists：指定的UUID已存在 · The specified network model does not exist：指定的网络模型不存在 · You cannot edit or delete the model, because it has been specified in list planning：存在关联的清单规划，不允许修改或删除模型 · The specified model has been used by online template：指定模型被上线模板引用 · The device group model name already exists：设备组模型名称已存在 · A global variable already exsits with the same name：存在变量名和全局变量名重复 · A variable in a device model already exists with the same name：存在变量名与设备模型中变量名重复 |
|
关键字 |
MOD_DEVICE_GROUP_MODEL_OP |
|
日志内容 |
Updated device group model: $1 |
|
参数解释 |
$1：设备组模型信息 |
|
举例 |
Updated device group model { ID: [ccf19104-4091-408e-871a-bd0ba0ba96f9] name: [leaf-group1] description: [desc] network_model_id: [45757617-d19e-42ad-a146-7918a3d74f28] device_role: [leaf] }. |
|
日志说明 |
用户修改了设备组模型 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · The service does not exist.：指定的服务不存在 · The controller is not the active leader：该控制组件不是主Leader · ID is Invalid：无效的ID · Please specify a name, a case-sensitive string of up to 255 characters. The name cannot contain only spaces. The name cannot start or end with a space：名称必选，最长255个字符，区分大小写，不允许全空格 · The description is case-sensitive string of up to 255 characters：描述最长255个字符，区分大小写 · Please specify the device role：设备角色不能为空 · The string is of up to 255 characters, and does not support less-than signs (<) or greater-than signs (>), and cannot contain only spaces：最长255个字符，不支持“<”和“>”，不支持全空格 · Please specify the valid type：类型字段不能为空 · Duplicate variable names exist in the device group model：设备组模型中存在重复的变量名 · For an IP pair allocation rule, you must specify existing variables in a model and make sure the variables are IP resource pool type：IP成对分配规则中的变量应该都是模型中变量，且类型只能是IP资源池类型 · The config param is not null and cannot exceed 255 characters：配置参数不能为空且不能超过255个字符 · You can configure IP pair allocation rules for variables only if they are the same type, which can be either IPv4 or IPv6 address pool：只有变量类型相同且为IPv4或者IPv6地址池中的一种时，可以为变量配置IP成对分配规则 · Format: IPv4 subnet mask as an integer (24-31) or IPv6 prefix length as an integer (112-127)：对于IPv4地址，掩码取值范围为24~31的整数；对于IPv6地址，前缀长度为112~127的整数 · The configuration item does not exist：指定的配置项不存在 · The specified network model does not exist：指定的网络模型不存在 · You cannot edit or delete the model, because it has been specified in list planning：存在关联的清单规划，不允许修改或删除模型 · The specified model has been used by online template：指定模型被上线模板引用 · The device group model name already exists：设备组模型名称已存在 · A global variable already exsits with the same name：存在变量名和全局变量名重复 · A variable in a device model already exists with the same name：存在变量名与设备模型中变量名重复 · network model can not be modified：网络模型不能被修改 · The device group model is already referenced by a device model. You cannot change the device role：该设备组模型已被设备模型引用，不允许修改设备角色 · Variables referenced by device models or interconnect models cannot be deleted or renamed：被设备配置或互通配置引用的变量，不允许删除或修改名称 · You cannot edit or delete the variables, because one or multiple of them are used by the management IP of the device model.：有变量被设备模型的管理IP引用 · The variable has been referneced by interconnect variable：被互通模型变量引用的变量，不允许修改或删除 · Variables referenced by device models or interconnect models cannot be deleted or renamed：被设备配置或互通配置引用的变量，不允许删除或修改名称 |
|
关键字 |
DEL_DEVICE_GROUP_MODEL_OP |
|
日志内容 |
Deleted device group model ID: [$1]. |
|
参数解释 |
$1：设备组模型的UUID |
|
举例 |
Deleted device group model ID: [ccf19104-4091-408e-871a-bd0ba0ba96f9]. |
|
日志说明 |
用户删除了设备组模型 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · The service does not exist.：指定的服务不存在 · The controller is not the active leader：该控制组件不是主Leader · ID is Invalid：无效的ID · The configuration item does not exist：指定的配置项不存在 · You cannot edit or delete the model, because it has been specified in list planning：存在关联的清单规划，不允许修改或删除模型 · The specified model has been used by online template：指定模型被上线模板引用 · You cannot delete the device group model, because it is associated with a device model：存在关联的设备模型，不允许删除 |
|
关键字 |
ADD_DEVICE_MODEL_OP |
|
日志内容 |
Created device model: $1 |
|
参数解释 |
$1：设备模型的信息 |
|
举例 |
Created device model { ID: [041f9974-4ca8-4f3b-8f2c-bf160ba708ce] name: [leaf1] description: [] network_model_id: [45757617-d19e-42ad-a146-7918a3d74f28] device_group_id: [ccf19104-4091-408e-871a-bd0ba0ba96f9] device_group_name: [leaf-group1] device_role: [leaf] management_ip: [leafIp1] }. |
|
日志说明 |
用户创建了一个设备模型 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · The service does not exist.：指定的服务不存在 · The controller is not the active leader：该控制组件不是主Leader · ID is Invalid：无效的ID · Please specify a name, a case-sensitive string of up to 255 characters. The name cannot contain only spaces. The name cannot start or end with a space：名称必选，最长255个字符，区分大小写，不允许全空格 · The description is case-sensitive string of up to 255 characters：描述最长255个字符，区分大小写 · device model management ip must be specified.：设备模型管理ip必须要指定。 · device cfg must be specified：设备配置脚本必须要指定 · The variable type for the management IP must be IP address, IPv4 address pool, or IPv6 address pool：管理IP的变量类型，必须是IP地址、IPv4地址池、IPv6地址池中的一种 · A single device group variable can only be the management IP variable in a device model.：单个设备组变量只能在一个设备模型中做管理IP变量 · The management IP variable must be a variable in the current device model or associated device group model, and the variable type must be IP address, IPv4 resource pool, or IPv6 resource pool：管理IP变量必须是当前设备模型或关联设备组模型中的变量，且变量类型为IP地址、IPv4资源池、IPv6资源池中的一种 · The string is of up to 255 characters, and does not support less-than signs (<) or greater-than signs (>), and cannot contain only spaces：最长255个字符，不支持“<”和“>”，不支持全空格 · Please specify the valid type：类型字段不能为空 · Duplicate variable names exist in the device model.：设备模型中存在重复的变量名。 · For an IP pair allocation rule, you must specify existing variables in a model and make sure the variables are IP resource pool type.：IP成对分配规则中的变量应该都是模型中变量，且类型只能是IP资源池类型 · The config param is not null and cannot exceed 255 characters：配置参数不能为空且不能超过255个字符 · You can configure IP pair allocation rules for variables only if they are the same type, which can be either IPv4 or IPv6 address pool：只有变量类型相同且为IPv4或者IPv6地址池中的一种时，可以为变量配置IP成对分配规则 · Format: IPv4 subnet mask as an integer (24-31) or IPv6 prefix length as an integer (112-127)：对于IPv4地址，掩码取值范围为24~31的整数；对于IPv6地址，前缀长度为112~127的整数 · You cannot edit or delete the model, because it has been specified in list planning：存在关联的清单规划，不允许修改或删除模型 · The specified model has been used by online template：指定模型被上线模板引用 · The device model name already exists：设备模型名称已存在 · A global variable already exsits with the same name：存在变量名和全局变量名重复 · The specified device group does not exist：指定的设备组模型不存在 · Make sure the device model has the same role as the associated device group model：设备模型和设备组模型的设备角色不一样 · A variable in a device group model already exists with the same name：存在变量名与设备组模型中变量名重复 · The configuration script contains undefined variables：配置文件中存在未定义的变量 |
|
关键字 |
MOD_DEVICE_MODEL_OP |
|
日志内容 |
Updated device model: $1 |
|
参数解释 |
$1：设备模型的信息 |
|
举例 |
Updated device model { ID: [041f9974-4ca8-4f3b-8f2c-bf160ba708ce] name: [leaf1] description: [desc] network_model_id: [45757617-d19e-42ad-a146-7918a3d74f28] device_group_id: [ccf19104-4091-408e-871a-bd0ba0ba96f9] device_group_name: [leaf-group1] device_role: [leaf] management_ip: [leafIp1] }. |
|
日志说明 |
用户修改了设备模型 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · The service does not exist.：指定的服务不存在 · The controller is not the active leader：该控制组件不是主Leader · ID is Invalid：无效的ID · Please specify a name, a case-sensitive string of up to 255 characters. The name cannot contain only spaces. The name cannot start or end with a space：名称必选，最长255个字符，区分大小写，不允许全空格 · The description is case-sensitive string of up to 255 characters：描述最长255个字符，区分大小写 · The variable type for the management IP must be IP address, IPv4 address pool, or IPv6 address pool：管理IP的变量类型，必须是IP地址、IPv4地址池、IPv6地址池中的一种 · A single device group variable can only be the management IP variable in a device model.：单个设备组变量只能在一个设备模型中做管理IP变量 · The management IP variable must be a variable in the current device model or associated device group model, and the variable type must be IP address, IPv4 resource pool, or IPv6 resource pool：管理IP变量必须是当前设备模型或关联设备组模型中的变量，且变量类型为IP地址、IPv4资源池、IPv6资源池中的一种 · The string is of up to 255 characters, and does not support less-than signs (<) or greater-than signs (>), and cannot contain only spaces：最长255个字符，不支持“<”和“>”，不支持全空格 · Please specify the valid type：类型字段不能为空 · Duplicate variable names exist in the device model.：设备模型中存在重复的变量名。 · For an IP pair allocation rule, you must specify existing variables in a model and make sure the variables are IP resource pool type.：IP成对分配规则中的变量应该都是模型中变量，且类型只能是IP资源池类型 · The config param is not null and cannot exceed 255 characters：配置参数不能为空且不能超过255个字符 · You can configure IP pair allocation rules for variables only if they are the same type, which can be either IPv4 or IPv6 address pool：只有变量类型相同且为IPv4或者IPv6地址池中的一种时，可以为变量配置IP成对分配规则 · Format: IPv4 subnet mask as an integer (24-31) or IPv6 prefix length as an integer (112-127)：对于IPv4地址，掩码取值范围为24~31的整数；对于IPv6地址，前缀长度为112~127的整数 · The configuration item does not exist：指定的配置项不存在 · You cannot edit or delete the model, because it has been specified in list planning：存在关联的清单规划，不允许修改或删除模型 · The specified model has been used by online template：指定模型被上线模板引用 · The device model name already exists：设备模型名称已存在 · A global variable already exsits with the same name：存在变量名和全局变量名重复 · The specified device group does not exist：指定的设备组模型不存在 · Make sure the device model has the same role as the associated device group model：设备模型和设备组模型的设备角色不一样 · A variable in a device group model already exists with the same name：存在变量名与设备组模型中变量名重复 · The configuration script contains undefined variables：配置文件中存在未定义的变量 · You cannot edit the associated device group for the device model, because it has been used in an interconnect model.：设备模型被互通模型引用，设备组字段不允许修改 · Variables referenced by device models or interconnect models cannot be deleted or renamed.：被设备配置或互通配置引用的变量，不允许删除或修改名称 · The variable has been referneced by interconnect variable：被互通模型变量引用的变量，不允许修改或删除 |
|
关键字 |
DEL_DEVICE_MODEL_OP |
|
日志内容 |
Deleted device model ID: [$1]. |
|
参数解释 |
$1：设备模型的UUID |
|
举例 |
Deleted device model ID: [dda916ec-c5a9-495e-944e-51309ee60821]. |
|
日志说明 |
用户删除了设备模型 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · The service does not exist.：指定的服务不存在 · The controller is not the active leader：该控制组件不是主Leader · ID is Invalid：无效的ID · The configuration item does not exist.：配置项不存在 · You cannot delete the device model, because it is associated with an interconnect model：存在关联的互通模型，不允许删除 · You cannot edit or delete the model, because it has been specified in list planning：存在关联的清单规划，不允许修改或删除模型 · The specified model has been used by online template：指定模型被上线模板引用 · The variable has been referneced by interconnect variable：被互通模型变量引用的变量，不允许修改或删除 |
|
关键字 |
ADD_INTERCONNECT_MODEL_OP |
|
日志内容 |
Created interconnect model: $1 |
|
参数解释 |
$1：互通模型的信息 |
|
举例 |
Created interconnect model { ID: [c77f3cf9-d90d-452e-9d42-8d8ed05a1516] name: [link1] description: [] network_model_id: [45757617-d19e-42ad-a146-7918a3d74f28] device_model_id_A: [041f9974-4ca8-4f3b-8f2c-bf160ba708ce] device_model_id_B: [dda916ec-c5a9-495e-944e-51309ee60821] }. |
|
日志说明 |
用户创建了一个互通模型 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · The service does not exist.：指定的服务不存在 · The controller is not the active leader：该控制组件不是主Leader · ID is Invalid：无效的ID · Please specify a name, a case-sensitive string of up to 255 characters. The name cannot contain only spaces. The name cannot start or end with a space：名称必选，最长255个字符，区分大小写，不允许全空格 · The description is case-sensitive string of up to 255 characters：描述最长255个字符，区分大小写 · device cfg must be specified.设备配置脚本必须要指定。 · Up to 10000 characters, case sensitive. The config cannot contain only spaces.：最长一万字符，不支持全空格 · The string is of up to 255 characters, and does not support less-than signs (<) or greater-than signs (>), and cannot contain only spaces：最长255个字符，不支持“<”和“>”，不支持全空格 · Please specify the valid type：类型字段不能为空 · If you specify the referenced variable source, you must also specify the referenced variable name and the name cannot exceed 255 characters：当变量引用来源被指定时，引用变量不能为空，且不能超过255个字符 · If you specify the referenced variable name, You must also specify the referenced variable source and the referenced variable source can only be device A, device B, device group A, or device group B：引用变量必须同时指定变量名和引用来源，且引用变量来源只包含 deviceA,deviceB,deviceGroupA,deviceGroupB · Duplicate variable names exist in the interconnect model：互通模型中存在重复的变量名 · For an IP pair allocation rule, you must specify existing variables in a model and make sure the variables are IP resource pool type.： IP成对分配规则中的变量应该都是模型中变量，且类型只能是IP资源池类型 · The config param is not null and cannot exceed 255 characters：配置参数不能为空，且不能超过255个字符 · For an IP pair allocation rule in an interconnect model, you can specify only non-referenced variables defined in this interconnect model：互通模型中的IP成对分配规则对不能引用其他模型中的变量 · You can configure IP pair allocation rules for variables only if they are the same type, which can be either IPv4 or IPv6 address pool：只有变量类型相同且为IPv4或者IPv6地址池中的一种时，可以为变量配置IP成对分配规则 · Format: IPv4 subnet mask as an integer (24-31) or IPv6 prefix length as an integer (112-127)：对于IPv4地址，掩码取值范围为24~31的整数；对于IPv6地址，前缀长度为112~127的整数 · The UUID already exists：指定的UUID已存在 · The specified network model does not exist：指定的网络模型不存在 · You cannot edit or delete the model, because it has been specified in list planning：存在关联的清单规划，不允许修改或删除模型 · The specified model has been used by online template：指定模型被上线模板引用 · The variable has been referneced by interconnect variable：被互通模型变量引用的变量，不允许修改或删除 · The specified device model does not exist：指定的设备模型不存在 · The device model A and the device model B cannot be the same：设备模型A和设备模型B不能相同 · The interconnect model name already exists：互通模型名称已存在 · The interConnectModel exists.：两个设备模型之间不支持创建多个互通模型 · A global variable already exsits with the same name：存在变量名和全局变量名重复 · The reference variable must originate from the device model or device group model：引用变量来源必须是互通模型两端的设备模型或设备模型关联的设备组模型 · The interconnect model variable and the specified variable are of different types.：互通模型变量和引用变量类型不一致 · The specified device group does not exist：指定的设备组模型不存在 · The reference variable must originate from the device model or device group model：引用变量来源必须是互通模型两端的设备模型或设备模型关联的设备组模型 · The configuration script contains undefined variables：配置文件中存在未定义的变量 |
|
关键字 |
MOD_INTERCONNECT_MODEL_OP |
|
日志内容 |
Updated interconnect model: $1 |
|
参数解释 |
$1：互通模型的信息 |
|
举例 |
Updated interconnect model { ID: [c77f3cf9-d90d-452e-9d42-8d8ed05a1516] name: [link1] description: [desc] network_model_id: [45757617-d19e-42ad-a146-7918a3d74f28] device_model_id_A: [041f9974-4ca8-4f3b-8f2c-bf160ba708ce] device_model_id_B: [dda916ec-c5a9-495e-944e-51309ee60821] }. |
|
日志说明 |
用户修改了互通模型 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · The service does not exist：指定的服务不存在 · The controller is not the active leader：该控制组件不是主Leader · ID is Invalid：无效的ID · Please specify a name, a case-sensitive string of up to 255 characters. The name cannot contain only spaces. The name cannot start or end with a space：名称必选，最长255个字符，区分大小写，不允许全空格 · The description is case-sensitive string of up to 255 characters：描述最长255个字符，区分大小写 · device cfg must be specified.设备配置脚本必须要指定 · Up to 10000 characters, case sensitive. The config cannot contain only spaces.：最长一万字符，不支持全空格 · The string is of up to 255 characters, and does not support less-than signs (<) or greater-than signs (>), and cannot contain only spaces.：最长255个字符，不支持“<”和“>”，不支持全空格 · Please specify the valid type：类型字段不能为空 · If you specify the referenced variable source, you must also specify the referenced variable name and the name cannot exceed 255 characters：当变量引用来源被指定时，引用变量不能为空，且不能超过255个字符 · If you specify the referenced variable name, You must also specify the referenced variable source and the referenced variable source can only be device A, device B, device group A, or device group B：引用变量必须同时指定变量名和引用来源，且引用变量来源只包含 deviceA,deviceB,deviceGroupA,deviceGroupB · Duplicate variable names exist in the interconnect model：互通模型中存在重复的变量名 · For an IP pair allocation rule, you must specify existing variables in a model and make sure the variables are IP resource pool type：IP成对分配规则中的变量应该都是模型中变量，且类型只能是IP资源池类型 · The config param is not null and cannot exceed 255 characters：配置参数不能为空，且不能超过255个字符 · For an IP pair allocation rule in an interconnect model, you can specify only non-referenced variables defined in this interconnect model：互通模型中的IP成对分配规则对不能引用其他模型中的变量 · You can configure IP pair allocation rules for variables only if they are the same type, which can be either IPv4 or IPv6 address pool：只有变量类型相同且为IPv4或者IPv6地址池中的一种时，可以为变量配置IP成对分配规则 · Format: IPv4 subnet mask as an integer (24-31) or IPv6 prefix length as an integer (112-127)：对于IPv4地址，掩码取值范围为24~31的整数；对于IPv6地址，前缀长度为112~127的整数 · The specified network model does not exist.：指定的网络模型不存在 · You cannot edit or delete the model, because it has been specified in list planning：存在关联的清单规划，不允许修改或删除模型 · The specified model has been used by online template：指定模型被上线模板引用 · The variable has been referneced by interconnect variable：被互通模型变量引用的变量，不允许修改或删除 · The specified device model does not exist：指定的设备模型不存在 · The device model A and the device model B cannot be the same：设备模型A和设备模型B不能相同 · The interconnect model name already exists：互通模型名称已存在 · The interConnectModel exists.：两个设备模型之间不支持创建多个互通模型 · A global variable already exsits with the same name：存在变量名和全局变量名重复 · The reference variable must originate from the device model or device group model：引用变量来源必须是互通模型两端的设备模型或设备模型关联的设备组模型 · The interconnect model variable and the specified variable are of different types.：互通模型变量和引用变量类型不一致 · The specified device group does not exist：指定的设备组模型不存在 · The reference variable must originate from the device model or device group model：引用变量来源必须是互通模型两端的设备模型或设备模型关联的设备组模型 · The configuration script contains undefined variables：配置文件中存在未定义的变量 · The configuration item does not exist：指定的配置项不存在 |
|
关键字 |
DEL_INTERCONNECT_MODEL_OP |
|
日志内容 |
Deleted interconnect model ID: [$1]. |
|
参数解释 |
$1：互通模型的UUID |
|
举例 |
Deleted interconnect model ID: [c77f3cf9-d90d-452e-9d42-8d8ed05a1516]. |
|
日志说明 |
用户删除了互通模型 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · The service does not exist.：指定的服务不存在 · The controller is not the active leader：该控制组件不是主Leader · ID is Invalid：无效的ID · The configuration item does not exist.：配置项不存在 · You cannot edit or delete the model, because it has been specified in list planning：存在关联的清单规划，不允许修改或删除模型 · The specified model has been used by online template：指定模型被上线模板引用 |
|
关键字 |
ADD_NUMBER_RANGES_OP |
|
日志内容 |
Created number ranges: $1 |
|
参数解释 |
$1：数字资源池信息 |
|
举例 |
Created number ranges { ID: [4c41504c-68d1-45e4-8670-650cd780a18a] name: [1000] description: [] }. |
|
日志说明 |
用户创建了一个数字资源池 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · The service does not exist.：指定的服务不存在 · The controller is not the active leader：该控制组件不是主Leader · ID is Invalid：无效的ID · Please specify a name, a case-sensitive string of up to 255 characters. The name cannot contain only spaces. The name cannot start or end with a space：名称必选，最长255个字符，区分大小写，不允许全空格 · The description is case-sensitive string of up to 255 characters：描述最长255个字符，区分大小写 · Please specify the number resource pool range.：请指定数字资源池范围 · The number resource pool has been used：数字资源池已被使用 · number resource pool range invalid.：无效的数字资源池范围 · The number resource pools contain overlapping ranges：数字资源池范围存在重叠 · The UUID already exists：指定的UUID已存在 · A number resource pool already exists with the specified name.：数字资源池名称已存在 · There is annother operation doing：有其他操作正在执行，请稍后重试 |
|
关键字 |
MOD_NUMBER_RANGES_OP |
|
日志内容 |
Updated number ranges: $1 |
|
参数解释 |
$1：数字资源池信息 |
|
举例 |
Updated number ranges { ID: [4c41504c-68d1-45e4-8670-650cd780a18a] name: [1000] description: [desc] }. |
|
日志说明 |
用户修改了数字资源池 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · The service does not exist.：指定的服务不存在 · The controller is not the active leader：该控制组件不是主Leader · ID is Invalid：无效的ID · Please specify a name, a case-sensitive string of up to 255 characters. The name cannot contain only spaces. The name cannot start or end with a space：名称必选，最长255个字符，区分大小写，不允许全空格 · The description is case-sensitive string of up to 255 characters：描述最长255个字符，区分大小写 · Please specify the number resource pool range.：请指定数字资源池范围 · The number resource pool has been used：数字资源池已被使用 · The number resource pools contain overlapping ranges：数字资源池范围存在重叠 · The configuration item does not exist：指定的配置项不存在 · A number resource pool already exists with the specified name.：数字资源池名称已存在 · There is annother operation doing.：有其他操作正在执行，请稍后重试 |
|
关键字 |
DEL_NUMBER_RANGES_OP |
|
日志内容 |
Deleted number ranges ID: [$1]. |
|
参数解释 |
$1：数字资源池的UUID |
|
举例 |
Deleted number ranges ID: [4c41504c-68d1-45e4-8670-650cd780a18a]. |
|
日志说明 |
用户删除了数字资源池 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · The service does not exist.：指定的服务不存在 · The controller is not the active leader：该控制组件不是主Leader · ID is Invalid：无效的ID · The configuration item does not exist.：配置项不存在 · The number resource pool has been used：数字资源池已被使用 · The specified number resource pool is referenced by a device deployment template and cannot be deleted：指定的数字资源池已被设备上线模板引用，不允许删除 · There is annother operation doing.：有其他操作正在执行，请稍后重试 |
|
关键字 |
ADD_ONLINE_TEMPLATE_OP |
|
日志内容 |
Created online template: $1 |
|
参数解释 |
$1：上线模板信息 |
|
举例 |
Created online template { id: [f1751e07-7c27-40af-befd-7f6d2538b5d7] name: [fabric-A_template.template] fabric_id: [eb18e5dd-992a-4e98-b519-a08560dbd0e7] fabric_name: [fabric-A] protocol_template_id: [ffffffff-0000-0000-0000-000000000001] protocol_template_name: [default_protocol_template] online_pool_id: [334f22b8-926f-4293-86dd-28ec2c4b008b] online_pool_name: [auto-1] network_model_id: [45757617-d19e-42ad-a146-7918a3d74f28] network_model_name: [network1] }. |
|
日志说明 |
用户创建了一个上线模板 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · The service does not exist.：指定的服务不存在 · The controller is not the active leader：该控制组件不是主Leader · ID is Invalid：无效的ID · The specified fabric already exist online template：当前Fabric已存在上线模板 · On boarding status can not set value.：上线状态为只读字段，不可设置属性 · The specified fabric does not exist：指定的Fabric不存在 · The UUID already exists：指定的UUID已存在 · The specified fabric already exist online template.：当前fabirc已存在上线模板 · The network model does not exist.：网络模型不存在 · The current network model does not have device models.：当前网络模型中没有设备模型 · Up to 23 characters, case sensitive. Valid characters are letters, digits, underscores (_), and hyphens (-).The name is required and cannot start or end with a space.：最长23个字符，大小写敏感，只支持字母，数字，下划线和连字符，名称不能以空格开始或结束 · Template name can not be empty, and must end with .template.：上线模板名称不可为空，且必须以.template结尾 · The configuration template name already exists.：已存在相同名称的上线模板 · A deployment template already exists with the specified name on the Data Center Networks > Auto Deployment > Automation Templates page.：自动化部署中存在相同名称的上线模板 · Protocol template can not be empty：控制协议模板不可为空 · The control protocol template does not exist：控制协议模板不存在 · Online pool can not be empty：自动化上线地址池不可为空 · The auto deployment IP pool does not exist：自动化上线地址池不存在 · Online pool not PHY_MANAGE：自动化上线地址池类型不是物理管理网络 · An IP pool for auto deployment cannot contain the management IP address of a device：自动化上线地址池不允许包含设备管理IP地址 · The auto deployment address pool has been referenced by a device deployment template in the Custom Network module：自动化上线地址池已被自定义网络上线模板引用 · The auto deployment IP pool overlaps with the subnet of the auto deployment IP pool in another deployment template：自动化上线地址池与其他上线模板中的自动化上线地址池，子网重叠 · The auto deployment address pool has been used by an address pool set for auto deployment.：自动化上线地址池已被Fabrics下自动化部署里自动化模板的地址池集使用 · The auto deployment address pool overlaps with an address pool used by an address pool set for auto deployment：上线地址池与自动化部署里地址池集中地址池，子网重叠 · Invalid role, spine、leaf、aggr or access.：软件版本指定相应角色不可为空，取值为spine、leaf或aggr · There cant not be more than 1 software for same role.：同一角色最多只能有一个软件版本 · There cant not be more than 1 patch for same role.：同一角色最多只能有一个软件补丁 · Invalid device version type.：软件类型不可为空，取值为software或者patch · Resource pool variables do not match the variables in the network model.：资源池变量和网络模型中的变量不匹配 · The device model does not exist.：指定设备模型不存在 · The interconnect model does not exist.：指定互通模型不存在 · param pool resource id is null.变量资源池的ID不能为空 · The specified IP address pool does not exist.：指定IP地址池不存在 · IP Pool must be general manage.：IP资源池关联的地址池，只能是通用地址池 · The specified number resource pool does not exist.：指定的数字资源池不存在 · You must specify the same resource for the two variables in an IP pair allocation rule.：有IP成对分配规则约束的两个变量，必须指定同一个资源 · There is annother operation doing.：有其他操作正在执行，请稍后重试 |
|
关键字 |
MOD_ONLINE_TEMPLATE_OP |
|
日志内容 |
Updated online template: $1 |
|
参数解释 |
$1：上线模板信息 |
|
举例 |
Updated online template { id: [f1751e07-7c27-40af-befd-7f6d2538b5d7] name: [fabric-A_template.template] fabric_id: [eb18e5dd-992a-4e98-b519-a08560dbd0e7] fabric_name: [fabric-A] protocol_template_id: [192ca688-aff9-419b-b814-acf9aef9d9be] protocol_template_name: [test_协议模板] online_pool_id: [334f22b8-926f-4293-86dd-28ec2c4b008b] online_pool_name: [auto-1] network_model_id: [45757617-d19e-42ad-a146-7918a3d74f28] network_model_name: [network1] }. |
|
日志说明 |
用户修改了上线模板 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · The service does not exist.：指定的服务不存在 · The controller is not the active leader：该控制组件不是主Leader · ID is Invalid：无效的ID · The configuration item does not exist.：配置项不存在 · You cannot edit the network model, because it is associated with list planning：存在清单规划时，不允许修改网络模型 · Fabric can not be changed.：Fabric不可变更 · Name can not be changed.：名称不可变更 · On boarding status can not set value.：上线状态为只读字段，不可设置属性 · The specified fabric does not exist：指定的Fabric不存在 · The device deployment is in progress. You cannot edit the device deployment template.：上设备上线中，不允许修改上线模板 · You cannot edit the network model, because it is associated with list planning.：存在清单规划时，不允许修改网络模型 · You cannot edit the resource pool, because it is associated with list planning.：存在清单规划时，不允许修改资源池信息 · You cannot change the template name.：模板名称不能被修改 · The specified fabric already exist online template.：当前fabirc已存在上线模板 · The network model does not exist.：网络模型不存在 · The specified fabric does not exist：指定的Fabric不存在 · Invalid device role for vlan fabric.：vlan类型fabric绑定的网络模型，只能包含spine模型和leaf模型 · The current network model does not have device models.：当前网络模型中没有设备模型 · Protocol template can not be empty.：控制协议模板不可为空 · The control protocol template does not exist.：控制协议模板不存在 · Online pool can not be empty.：自动化上线地址池不可为空 · The auto deployment IP pool does not exist.：自动化上线地址池不存在 · Online pool not PHY_MANAGE.：自动化上线地址池类型不是物理管理网络 · An IP pool for auto deployment cannot contain the management IP address of a device.：自动化上线地址池不允许包含设备管理IP地址 · The auto deployment address pool has been referenced by a device deployment template in the Custom Network module：自动化上线地址池已被自定义网络上线模板引用 · The auto deployment IP pool overlaps with the subnet of the auto deployment IP pool in another deployment template.：自动化上线地址池与其他上线模板中的自动化上线地址池，子网重叠。 · The auto deployment address pool has been used by an address pool set for auto deployment.：自动化上线地址池已被Fabrics下自动化部署里自动化模板的地址池集使用 · The auto deployment address pool overlaps with an address pool used by an address pool set for auto deployment.：上线地址池与自动化部署里地址池集中地址池，子网重叠 · Invalid role, spine、leaf、aggr or access.：软件版本指定相应角色不可为空，取值为spine、leaf或aggr · There cant not be more than 1 software for same role.：同一角色最多只能有一个软件版本 · There cant not be more than 1 patch for same role.：同一角色最多只能有一个软件补丁 · Invalid device version type.：软件类型不可为空，取值为software或者patch · Resource pool variables do not match the variables in the network model.：资源池变量和网络模型中的变量不匹配 · The device model does not exist.：指定设备模型不存在 · The interconnect model does not exist.：指定互通模型不存在 · param origin only be global, device_group, device, interconnect.：变量来源只能是global, device_group,device和interconnect · The specified IP address pool does not exist.：指定ip地址池不存在 · IP Pool must be general manage.：IP资源池关联的地址池，只能是通用地址池 · The specified number resource pool does not exist.：指定的数字资源池不存在 · You must specify the same resource for the two variables in an IP pair allocation rule.：有IP成对分配规则约束的两个变量，必须指定同一个资源。 · There is annother operation doing.：有其他操作正在执行，请稍后重试 |
|
关键字 |
DEL_ONLINE_TEMPLATE_OP |
|
日志内容 |
Deleted online template ID: [$1]. |
|
参数解释 |
$1：上线模板的UUID |
|
举例 |
Deleted online template ID: [f1751e07-7c27-40af-befd-7f6d2538b5d7]. |
|
日志说明 |
用户删除了上线模板 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · The service does not exist.：指定的服务不存在 · The controller is not the active leader：该控制组件不是主Leader · ID is Invalid：无效的ID · The configuration item does not exist：配置项不存在 · You cannot delete the deployment template, because it is associated with list planning：存在清单规划，不允许删除 · A device in the deployment template is being deployed.：当前上线模板存在正在自动化上线设备 · There is annother operation doing.：有其他操作正在执行，请稍后重试 |
|
关键字 |
ADD_CONTROL_PROTOCOL_TEMPLATE_OP |
|
日志内容 |
Created control protocol template: $1 |
|
参数解释 |
$1：控制协议模板信息 |
|
举例 |
Created control protocol template { "control_protocol_template": { "id": "3bd65a72-0ee8-4934-8e9c-5eac28dea35f", "name": "protocol", "netconf": { "password": "******", "user_name": "admin" }, "snmp": null } } |
|
日志说明 |
用户创建了一个控制协议模板 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · The service does not exist.：指定的服务不存在 · The controller is not the active leader：该控制组件不是主Leader · ID is Invalid：无效的ID · The UUID already exists.：配置项已存在 · The control protocol template name is required.：未指定设备协议模板名称 · Invalid control protocol template name.：指定的设备协议模板名称格式不正确 · A control protocol template already exists with the same name：指定控制协议模板名称已存在 · The NETCONF configuration is required.：未指定设备控协议模板Netconf协议 · The NETCONF username cannot exceed 55 characters, cannot be upper-case or lower-case a, al, or all, and cannot contain spaces or back slash or any of the following specicial characters: |/:*?<>@.：NETCONF用户名不能超过55个字符，不能是大写或小写的a、al或all，并且不能包含空格、反斜杠或以下任何特殊字符：|/:*?<>@。 · Up to 63 characters,the password must contain a minimum of 10 characters from at least two of the following categories:digits, uppercase letters, lowercase letters, and special characters.The password cannot contain a username or the reverse letters of a username.Chinese characters are not supported，and cannot contain “?” 、space.：密码必须包含至少10个来自以下至少两个类别的字符：数字、大写字母、小写字母和特殊字符。密码不能包含用户名或用户名的反向字母。不支持中文字符，也不能包含“?”或空格。 · The NETCONF password cannot contain a username or the reverse letters of a username.：NETCONF密码不允许包含用户名或用户名的倒序 · The snmp version is required.：未指定snmp版本 · Invalid SNMPv2c parameters.：指定的SNMPv2参数不合法 · Invalid SNMPv3 parameters.：指定的SNMPv3参数不合法 · The SNMP read community name can contain up to 32 characters, and cannot be all-spaces. Chinese characters are not supported.：SNMP读团体名可以包含多达32个字符，不能全部为空格。不支持中文字符 · The SNMP write community name can contain up to 32 characters, and cannot be all-spaces. Chinese characters are not supported.：SNMP写团体名可以包含多达32个字符，不能全部为空格。不支持中文字符 · A username is required in SNMPv3.：SNMPv3版本必须指定用户名： · The SNMPv3 username must be a case-sensitive string of up to 32 characters. Chinese characters, question marks (?), and spaces are not allowed.：SNMPv3用户名最长32个字符，区分大小写，不支持中文、问号和空格 · The value for the SNMPv3 authentication algorithm field can only be NONE, MD5, or SHA.：指定的SNMPv3的认证协议仅支持NONE、MD5和SHA · The value for the SNMPv3 encryption algorithm field can only be NONE, DES, AES128, AES192, AES256, or 3DES.：指定的SNMPv3的加密协议仅支持NONE、DES、AES128、AES192、AES256和3DES · You must specify both the authentication algorithm and password or none of them.：认证协议和认证密码必须同时配置或同时不配置 · Invalid security model.：安全模式不合法。 · You must specify both the authentication algorithm and password or none of them.：认证协议和认证密码必须同时配置或同时不配置 · You must specify both the encryption algorithm and password or none of them.：加密协议和加密密码必须同时配置或同时不配置 · Up to 64 characters,the authentication password must contain a minimum of 10 characters from at least two of the following categories: digits, uppercase letters, lowercase letters, and special characters.The password cannot contain a username or the reverse letters of a username.Chinese characters are not supported，and cannot contain “?” 、space.：认证密码必须包含至少两种字符类型（数字、大写字母、小写字母、特殊字符）中的任意10个字符，最多64个字符。密码不能包含用户名或用户名的反向字母。不支持中文字符，也不能包含“？”或空格。 · Up to 64 characters,the encryption password must contain a minimum of 10 characters from at least two of the following categories: digits, uppercase letters, lowercase letters, and special characters.The password cannot contain a username or the reverse letters of a username.Chinese characters are not supported，and cannot contain “?” 、space.：加密密码必须包含至少两种以下类别的最少10个字符：数字、大写字母、小写字母和特殊字符。密码不能包含用户名或用户名的反向字母。不支持中文字符，也不能包含“?”和空格。 · There is annother operation doing.：有其他操作正在执行，请稍后重试 |
|
关键字 |
MOD_CONTROL_PROTOCOL_TEMPLATE_OP |
|
日志内容 |
Updated control protocol template: $1 |
|
参数解释 |
$1：控制协议模板信息 |
|
举例 |
Updated control protocol template { "control_protocol_template": { "id": "3bd65a72-0ee8-4934-8e9c-5eac28dea35f", "name": "protocol", "netconf": { "password": "******", "user_name": "admin1" }, "snmp": null } }. |
|
日志说明 |
用户修改了上线模板 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · The service does not exist.：指定的服务不存在 · The controller is not the active leader：该控制组件不是主Leader · ID is Invalid：无效的ID · The specified control protocol template does not exist.：指定设备设备控制模板不存在 · The control protocol template name cannot be modified.：指定的控制协议模板名称不允许修改 · The control protocol template id cannot be modified.：指定的控制协议模板id不允许修改 · The snmp version is required.：未指定snmp版本 · The NETCONF configuration is required.：未指定设备控协议模板Netconf协议 · The NETCONF username cannot exceed 55 characters, cannot be upper-case or lower-case a, al, or all, and cannot contain spaces or back slash or any of the following specicial characters: |/:*?<>@.：NETCONF用户名不能超过55个字符，不能是大写或小写的a、al或all，并且不能包含空格、反斜杠或以下任何特殊字符：|/:*?<>@。 · Up to 63 characters,the password must contain a minimum of 10 characters from at least two of the following categories:digits, uppercase letters, lowercase letters, and special characters.The password cannot contain a username or the reverse letters of a username.Chinese characters are not supported，and cannot contain “?” 、space.：密码必须包含至少10个来自以下至少两个类别的字符：数字、大写字母、小写字母和特殊字符。密码不能包含用户名或用户名的反向字母。不支持中文字符，也不能包含“?”或空格。 · The NETCONF password cannot contain a username or the reverse letters of a username.：NETCONF密码不允许包含用户名或用户名的倒序 · You cannot edit the NETCONF or SNMP settings for the control protocol template, because it has been used by a deployment template with ongoing deployment tasks：当前控制协议模板已被状态为“上线中”的上线模板引用，netconf或snmp不允许修改 · Invalid SNMPv2c parameters.：指定的SNMPv2参数不合法 · Invalid SNMPv3 parameters.：指定的SNMPv3参数不合法 · The SNMP read community name can contain up to 32 characters, and cannot be all-spaces. Chinese characters are not supported.：SNMP读团体名可以包含多达32个字符，不能全部为空格。不支持中文字符 · The SNMP write community name can contain up to 32 characters, and cannot be all-spaces. Chinese characters are not supported.：SNMP写团体名可以包含多达32个字符，不能全部为空格。不支持中文字符 · A username is required in SNMPv3.：SNMPv3版本必须指定用户名： · The SNMPv3 username must be a case-sensitive string of up to 32 characters. Chinese characters, question marks (?), and spaces are not allowed.：SNMPv3用户名最长32个字符，区分大小写，不支持中文、问号和空格 · The value for the SNMPv3 authentication algorithm field can only be NONE, MD5, or SHA.：指定的SNMPv3的认证协议仅支持NONE、MD5和SHA · The value for the SNMPv3 encryption algorithm field can only be NONE, DES, AES128, AES192, AES256, or 3DES.：指定的SNMPv3的加密协议仅支持NONE、DES、AES128、AES192、AES256和3DES · You must specify both the authentication algorithm and password or none of them.：认证协议和认证密码必须同时配置或同时不配置 · Invalid security model.：安全模式不合法。 · You must specify both the authentication algorithm and password or none of them.：认证协议和认证密码必须同时配置或同时不配置 · You must specify both the encryption algorithm and password or none of them.：加密协议和加密密码必须同时配置或同时不配置 · Up to 64 characters,the authentication password must contain a minimum of 10 characters from at least two of the following categories: digits, uppercase letters, lowercase letters, and special characters.The password cannot contain a username or the reverse letters of a username.Chinese characters are not supported，and cannot contain “?” 、space.：认证密码必须包含至少两种字符类型（数字、大写字母、小写字母、特殊字符）中的任意10个字符，最多64个字符。密码不能包含用户名或用户名的反向字母。不支持中文字符，也不能包含“？”或空格。 · Up to 64 characters,the encryption password must contain a minimum of 10 characters from at least two of the following categories: digits, uppercase letters, lowercase letters, and special characters.The password cannot contain a username or the reverse letters of a username.Chinese characters are not supported，and cannot contain “?” 、space.：加密密码必须包含至少两种以下类别的最少10个字符：数字、大写字母、小写字母和特殊字符。密码不能包含用户名或用户名的反向字母。不支持中文字符，也不能包含“?”和空格。 · There is annother operation doing.：有其他操作正在执行，请稍后重试 |
|
关键字 |
DEL_CONTROL_PROTOCOL_TEMPLATE_OP |
|
日志内容 |
Deleted control protocol template ID: [$1]. |
|
参数解释 |
$1：控制协议模板的UUID |
|
举例 |
Deleted control protocol template ID: [3bd65a72-0ee8-4934-8e9c-5eac28dea35f]. |
|
日志说明 |
用户删除了上线模板 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · The service does not exist.：指定的服务不存在 · The controller is not the active leader：该控制组件不是主Leader · ID is Invalid：无效的ID · The specified control protocol template does not exist.：指定设备设备控制模板不存在 · The specified control protocol template has been used：指定控制协议模板已被使用 · Default protocol template cannot be deleted.：默认控制协议模板不允许删除 · There is annother operation doing.：有其他操作正在执行，请稍后重试 |
|
关键字 |
IMPORT_PLAN_LIST_OP |
|
日志内容 |
Imported plan list success. |
|
参数解释 |
无 |
|
举例 |
Imported plan list success. |
|
日志说明 |
用户导入了清单信息 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · The service does not exist.：指定的服务不存在 · The controller is not the active leader：该控制组件不是主Leader · ID is Invalid：无效的ID · The specified fabric does not exist：指定的Fabric不存在 · The fabric is not specified in any deployment template：指定Fabric无上线模板 · The device onboarding task is in progress. You cannot perform this operation：上线任务未结束，不允许操作 · Invalid list planning template：无效的清单规划模板 · The device group number must be an integer in the range of 1 to 2147483647：设备组编号范围是1~2147483647的整数 · The specified device serial number already exists in fabric {f1}：指定的设备序列号在 f1中已存在 · The fabric-associated network model does not contain the specified device model：当前Fabric关联的网络模型中没有指定的设备模型 · The device group model is not correct：设备组模型不匹配 · When specifying a device group model, you must specify the device group number：指定设备组模型时，设备组编号必选 · Different device group models cannot use the same device group number：不同设备组模型，不允许使用相同的设备组编号 · You must specify both the device group and its number or neither of them：设备组和设备组编号同时指定或者都不指定 · The serial number of device is exist in white list：自动部署中存在相同序列号的设备信息 · The specified device list does not exist：指定的设备清单不存在 · Please specify a device serial number：设备序列号必选 · The device information is referenced by interconnect information and cannot be modified or deleted.：有互通信息引用了该设备清单，不允许被修改或者删除 · The specified device index number already exists in fabric {f1}：指定的设备索引号在 f1 中已存在 · Please specify a device index：设备索引必选 · The fabric-associated network model does not contain the specified interconnect model：当前Fabric关联的网络模型中没有指定的互通模型 · The device models in the specified interconnect model do not match those in the current interconnect information.：互通清单中的设备模型与设备清单中的模型不一致 · The UUID already exists：指定的UUID已存在 · The specified interconnect model does not exist：指定的互通模型不存在 · The associated deployment template does not exist：关联的上线模板不存在 · The resource pool associated with the variable does not exist：资源池变量关联的资源池不存在 · The device index number is a string of up to 63 characters that contains only digits, letters, dots (.), underscores (_), and hyphens (-)：最长63字符,只支持数字，字母，点号，下划线和连字符 · The device serial number is a string of up to 63 characters that can contain only digits and letters：最长63字符,只支持数字和字母 · The uploaded file cannot contain hyperlinks：上传文件中不能含有超链接格式 · There is annother operation doing：有其他操作正在执行，请稍后重试 |
|
关键字 |
DOWNLOAD_PLAN_LIST_OP |
|
日志内容 |
Download plan list success. |
|
参数解释 |
无 |
|
举例 |
Download plan list success. |
|
日志说明 |
用户下载了清单信息模板 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · The service does not exist：服务不存在 |
|
关键字 |
MOD_DEVICE_LIST_OP |
|
日志内容 |
Updated device list: $1 |
|
参数解释 |
$1：设备信息 |
|
举例 |
Updated device list { id: [679b91b9-7fda-4d99-a949-a23e708b1726] fabric_id: [eb18e5dd-992a-4e98-b519-a08560dbd0e7] device_index: [leaf1] device_serial_number: [210235A3JSH189000231] device_group_model_id: [ccf19104-4091-408e-871a-bd0ba0ba96f9] device_group_model_name: [leaf-group1] device_group_number: [167] device_model_id: [041f9974-4ca8-4f3b-8f2c-bf160ba708ce] device_model_name: [leaf1] }. |
|
日志说明 |
用户修改了设备信息 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · The service does not exist.：指定的服务不存在 · The controller is not the active leader：该控制组件不是主Leader · ID is Invalid：无效的ID · The specified device list does not exist.：指定的设备清单不存在 · The specified fabric does not exist：指定的Fabric不存在 · The fabric is not specified in any deployment template.：设备上线模板不存在 · The device onboarding task is in progress. You cannot perform this operation：上线任务未结束，不允许操作 · Please specify a device model.：设备模型不可为空 · Fabric can not be changed：Fabric不可变更 · Device index can not be changed.：设备索引不可变更 · The specified device model does not exist：指定的设备模型不存在 · The device group model is not correct：设备组模型不匹配 · When specifying a device group model, you must specify the device group number：指定设备组模型时，设备组编号必选 · The device group number must be an integer in the range of 1 to 2147483647.：设备组编号范围是1~2147483647的整数。 · Different device group models cannot use the same device group number.：不同设备组模型，不允许使用相同的设备组编号 · When specifying a device group model, you must specify the device group number.：指定设备组模型时，设备组编号必选 · The serial number of device is exist in white list.：自动部署中存在相同序列号的设备信息 · Please specify a device serial number：设备序列号必选 · The specified device serial number already exists in fabric {f1}：指定的设备序列号在{f1}中已存在 · The device information is referenced by interconnect information and cannot be modified or deleted：该设备信息已被互通信息引用，不允许修改或者删除 · The specified device group model does not exist：指定的设备组模型不存在 · The associated deployment template does not exist：关联的上线模板不存在。 · The resource pool associated with the variable does not exist：资源池变量关联的资源池不存在 · There is annother operation doing：有其他操作正在执行，请稍后重试 |
|
关键字 |
DEL_DEVICE_LIST_OP |
|
日志内容 |
Deleted device list ID: [$1]. |
|
参数解释 |
$1：设备信息的UUID |
|
举例 |
Deleted device list ID: [ec336e70-5739-45f4-a35d-f4ac1b813964]. |
|
日志说明 |
用户删除了设备信息 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · The service does not exist.：指定的服务不存在 · The controller is not the active leader：该控制组件不是主Leader · ID is Invalid：无效的ID · The specified device list does not exist.：指定的设备清单不存在 · The specified fabric does not exist：指定的Fabric不存在 · The fabric is not specified in any deployment template：设备上线模板不存在 · The device onboarding task is in progress. You cannot perform this operation：上线任务未结束，不允许操作 · You cannot delete the device information entry, because it has been used by an interconnect information entry：该设备信息已被互通信息使用 · The device information is referenced by interconnect information and cannot be modified or deleted：该设备信息已被互通信息引用，不允许修改或者删除 · The specified device group model does not exist.：指定的设备组模型不存在 · The associated deployment template does not exist：关联的上线模板不存在 · The resource pool associated with the variable does not exist：资源池变量关联的资源池不存在 · There is annother operation doing：有其他操作正在执行，请稍后重试 |
|
关键字 |
DEL_INTERCONNECT_LIST_OP |
|
日志内容 |
Deleted interconnect list ID: [$1]. |
|
参数解释 |
$1：互通信息的UUID |
|
举例 |
Deleted interconnect list ID: [1e348bd8-039a-4388-bc34-bfd09e43e7c4]. |
|
日志说明 |
用户删除了互通信息 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · The service does not exist：指定的服务不存在 · The controller is not the active leader：该控制组件不是主Leader · ID is Invalid：无效的ID · The specified interconnect list does not exist：指定的互通模型不存在 · The specified fabric does not exist：指定的Fabric不存在 · The fabric is not specified in any deployment template：设备上线模板不存在 · The device onboarding task is in progress. You cannot perform this operation：上线任务未结束，不允许操作 · The specified device group model does not exist：指定的设备组模型不存在 · The associated deployment template does not exist：关联的上线模板不存在 · The resource pool associated with the variable does not exist：资源池变量关联的资源池不存在 · There is annother operation doing：有其他操作正在执行，请稍后重试 |
|
关键字 |
DOWNLOAD_VARIABLE_INSTANCE_OP |
|
日志内容 |
Downloaded variable instance success. |
|
参数解释 |
无 |
|
举例 |
Downloaded variable instance success. |
|
日志说明 |
用户下载了用于导入变量实例的模板 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · The service does not exist.：指定的服务不存在 · The controller is not the active leader：该控制组件不是主Leader · There is annother operation doing：有其他操作正在执行，请稍后重试 |
|
关键字 |
IMPORT_VARIABLE_INSTANCE_OP |
|
日志内容 |
Imported variable instance success. |
|
参数解释 |
无 |
|
举例 |
Imported variable instance success. |
|
日志说明 |
用户导入了变量实例 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · The service does not exist：指定的服务不存在 · The controller is not the active leader：该控制组件不是主Leader · Failed to read the file content：读取文件内容失败 · No list planning is available for the specified fabric：指定的Fabric没有清单规划 · Invalid variable instance template：无效的变量实例模板 · The specified fabric does not exist：指定的Fabric不存在 · The fabric is not specified in any deployment template：设备上线模板不存在 · The device onboarding task is in progress. You cannot perform this operation：上线任务未结束，不允许操作 · Invalid type or value：非法的变量类型或变量值 · The uploaded file cannot contain hyperlinks：上传文件中不能含有超链接格式 · There is annother operation doing：有其他操作正在执行，请稍后重试 |
|
关键字 |
ASSIGN_VARIABLE_RESOURCE_OP |
|
日志内容 |
Assigned variable resource, fabric id:$1. |
|
参数解释 |
$1：Fabric的UUID |
|
举例 |
Assigned variable resource, fabric id:56712e77-14e3-4251-8149-bf4c7f49f1b3. |
|
日志说明 |
用户分配了资源池变量 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · The service does not exist：指定的服务不存在 · The controller is not the active leader：该控制组件不是主Leader · The specified fabric does not exist：指定的Fabric不存在 · No list planning is available for the specified fabric：指定的Fabric没有清单规划 · The fabric is not specified in any deployment template.：设备上线模板不存在 · The resource pool associated with the variable does not exist：资源池变量关联的资源池不存在 · If two variables specified in an IP pair allocation rule are the IP resource pool type, you must specify the same resource pool for them：一对IP成对分配规则中的两个变量是IP资源池类型，请关联同一个资源池 · Resource allocation failed due to resource insufficiency：存在资源池中资源不足的情况，无法分配 · Resource allocation failed due to resource insufficiency：存在资源池中资源不足的情况，无法分配 · There is annother operation doing：有其他操作正在执行，请稍后重试 |
|
关键字 |
MOD_VARIABLE_INSTANCE_OP |
|
日志内容 |
Updated variable instance:$1. |
|
参数解释 |
$1：变量实例的信息 |
|
举例 |
Updated variable instance { ID: [bc07dfa6-bd11-47b4-9a31-0794620cec86] fabric_id: [eb18e5dd-992a-4e98-b519-a08560dbd0e7] instance_type: [DEVICE] variable_name: [sys-name] variable_type: [STRING] value: [leaf2] device_model_id: [dda916ec-c5a9-495e-944e-51309ee60821] device_model_name: [leaf2] device_index: [leaf2] }. |
|
日志说明 |
用户修改了变量实例 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · The service does not exist：指定的服务不存在 · The controller is not the active leader：该控制组件不是主Leader · You must specify a variable instance type.：必须指定变量实例类型 · The specified variable instance does not exist：指定的变量实例不存在 · The resource variable instance can not be changed：资源池类型变量实例不允许修改 · Invalid IP Address：非法的IP · The values in a number resource pool must be integers in the range of 0 to 4294967295：数字资源池范围是0~4294967295的整数。 · Maximum 255 characters.：最大为255个字符 · Please specify the valid type：类型字段不能为空 · Please specify the value, a string of up to 255 characters. The value cannot contain only spaces：变量值不能为空，最长255个字符，不支持全空格 · You can only modify instance value：只允许修改变量值字段 · No list planning is available for the specified fabric：指定的Fabric没有清单规划 · There is annother operation doing：有其他操作正在执行，请稍后重试 |
|
关键字 |
CONFIGURE_GENERATION_OP |
|
日志内容 |
Config generation fabric id: $1. |
|
参数解释 |
$1：Fabric的UUID |
|
举例 |
Config generation ,fabric id:eb18e5dd-992a-4e98-b519-a08560dbd0e7. |
|
日志说明 |
用户生成了设备的配置 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · The service does not exist.：指定的服务不存在 · The controller is not the active leader：该控制组件不是主Leader · The specified fabric does not exist：指定的Fabric不存在 · The fabric is not specified in any deployment template：设备上线模板不存在 · The device onboarding task is in progress. You cannot perform this operation：上线任务未结束，不允许操作 · No list planning is available for the specified fabric.：指定的Fabric没有清单规划 · Make sure each variable is assigned a value：存在未赋值的变量 · There is annother operation doing.：有其他操作正在执行，请稍后重试 |
|
关键字 |
RESTORE_CONFIGURE_GENERATION_OP |
|
日志内容 |
Restore configure generation ,fabric id: $1. |
|
参数解释 |
$1：Fabric的UUID |
|
举例 |
Restore configure generation ,fabric id:eb18e5dd-992a-4e98-b519-a08560dbd0e7. |
|
日志说明 |
用户清空了变量实例化以及设备配置 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · The service does not exist：指定的服务不存在 · The controller is not the active leader：该控制组件不是主Leader · The specified fabric does not exist：指定的Fabric不存在 · The resource pool associated with the variable does not exist：资源池变量关联的资源池不存在 · The fabric is not specified in any deployment template：设备上线模板不存在 · The device onboarding task is in progress. You cannot perform this operation：上线任务未结束，不允许操作 · No list planning is available for the specified fabric：指定的Fabric没有清单规划 · The associated deployment template does not exist：关联的上线模板不存在 · The resource pool associated with the variable does not exist：资源池变量关联的资源池不存在 · There is annother operation doing.：有其他操作正在执行，请稍后重试 |
|
关键字 |
START_ONLINE_OP |
|
日志内容 |
Started online ,fabric id: $1. |
|
参数解释 |
$1：Fabric的UUID |
|
举例 |
Started online ,fabric id:eb18e5dd-992a-4e98-b519-a08560dbd0e7. |
|
日志说明 |
用户开始上线 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · The service does not exist.：指定的服务不存在 · The controller is not the active leader：该控制组件不是主Leader · ID is Invalid：无效的ID · The specified fabric does not exist：指定的Fabric不存在 · The fabric network type is not User-Defined.：Fabric的类型不是User-Defined · No list planning is available for the specified fabric：指定的Fabric没有清单规划 · A device list that does not have configuration files generated exists, causing device onboarding failure：存在未生成配置文件的设备信息，无法进行设备上线 · The fabric is not specified in any deployment template：设备上线模板不存在 · The manage IP must use the same IP version as the controller IP：管理IP和控制组件IP的IP版本必须一致 · A management IP conflict exists. Make sure {1.1.1.1} meet the following requirements:1. It does not conflict with the management IP of any device that is incorporated or is in the device list. 2. It is not in any address pool for automated deployment：管理IP存在冲突，请确保1.1.1.1和已纳管设备或设备清单中的管理IP不冲突，且不在自动化上线地址池范围内 · Management IP conflict exists: {1.1.1.1}：存在冲突的管理IP: 1.1.1.1 · You cannot perform this operation, because the deployment task is in progress：正在执行上线任务，不允许该操作 · The operation is not permitted while devices are onboarding：存在上线中设备，不允许该操作 · The UUID already exists：指定的UUID已存在 · There is annother operation doing：有其他操作正在执行，请稍后重试 |
|
关键字 |
STOP_ONLINE_OP |
|
日志内容 |
Stoped online ,fabric id: $1. |
|
参数解释 |
$1：Fabric的UUID |
|
举例 |
Stoped online ,fabric id:eb18e5dd-992a-4e98-b519-a08560dbd0e7. |
|
日志说明 |
用户停止上线 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · The service does not exist：指定的服务不存在 · The controller is not the active leader：该控制组件不是主Leader · ID is Invalid.：无效的ID · The specified fabric does not exist：指定的Fabric不存在 · The fabric network type is not User-Defined：Fabric的类型不是User-Defined · The fabric is not specified in any deployment template.：设备上线模板不存在 · A device in the fabric is being deployed：指定Fabric下有正在上线的设备 · There is annother operation doing：有其他操作正在执行，请稍后重试 |
|
关键字 |
DEL_ONLINE_OP |
|
日志内容 |
Deleted online ID: [$1]. |
|
参数解释 |
$1：上线任务的UUID |
|
举例 |
Deleted online ID: [ded9c788-918b-4928-81a7-670720433424]. |
|
日志说明 |
用户删除了一个上线任务 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · The service does not exist.：指定的服务不存在 · The controller is not the active leader：该控制组件不是主Leader · The configuration item does not exist：指定的配置项不存在 · You cannot perform this operation, because the deployment task is in progress：正在执行上线任务，不允许该操作 · The operation is not permitted while devices are onboarding：存在上线中设备，不允许该操作 · There is annother operation doing：有其他操作正在执行，请稍后重试 |
本节介绍数据检查模块输出的操作日志。
|
关键字 |
START_DATA_CHECK_OP |
|
日志内容 |
Started data check for module [$1]. |
|
参数解释 |
$1：模块名称 |
|
举例 |
Started data check for module [VSM]. |
|
日志说明 |
用户执行了开始数据检查的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller has not finished initialization：当前控制组件SCM状态未完全恢复 · Administrator privileges required：当前用户无权限执行此操作，请使用管理员身份登录 · The JSON string cannot be empty：JSON串不能为空 · Please specify the module：模块不能为空 · Invalid module：无效的模块 · Please specify the data check UUID：数据检查任务UUID不能为空 · Invalid data check UUID：无效的数据检查任务UUID · Cannot start the data check because the previous data check is not finished：开始数据检查失败，当前已存在数据检查任务 · Unknown error：未知错误 |
|
关键字 |
STOP_DATA_CHECK_OP |
|
日志内容 |
Stopped data check. |
|
参数解释 |
无 |
|
举例 |
Stopped data check. |
|
日志说明 |
用户执行了停止数据检查的操作 |
|
失败原因 |
无 |
本节介绍DNEC模块输出的操作日志信息。
|
关键字 |
CREATE_UC_SITE_CUSTOM |
|
日志内容 |
Created custom U-Center site. |
|
参数解释 |
无 |
|
举例 |
Created custom U-Center site. |
|
日志说明 |
用户进行了创建站点的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request message body is empty：请求体为空 · The site name is required：站点名称必选 · Please specify a site name：站点名称不能为空 · Invalid site name：无效的站点名称 · A site already exists with the specified name：指定的站点名称已存在 · The specified area already has a local data center：指定的地区已存在本地数据中心 · Please select the province where the site is located：请选择站点所在的省份 · A district already exists with a site：该地区已存在定制站点 · Please select the local_data parameter and set its value to true or false：必须选择是否为本地数据中心 · The total number of devices supported must be an integer in the range of 0 to 99999：设备总数仅支持取值范围为0～99999的整数 · Please select the city where the site is located：站点所在的市不能为空 · The district does not exist：该区不存在 · Please select the district where the site is located：请选择站点所在的区 · The system service does not respond：系统服务未响应 |
|
关键字 |
UPDATE_UC_SITE_CUSTOM |
|
日志内容 |
Updated custom U-Center site. |
|
参数解释 |
无 |
|
举例 |
Updated custom U-Center site. |
|
日志说明 |
用户进行了修改站点的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The UUID is invalid：无效的UUID · The request message body is empty：请求体为空 · A site already exists with the specified name：指定的站点名称已存在 · The specified area already has a local data center：指定的地区已存在本地数据中心 · Please select the province where the site is located：请选择站点所在的省份 · A district already exists with a site：该地区已存在定制站点 · Please select the local_data parameter and set its value to true or false：必须选择是否为本地数据中心 · The total number of devices supported must be an integer in the range of 0 to 99999：设备总数仅支持取值范围为0～99999的整数 · Please select the city where the site is located：站点所在的市不能为空 · The district does not exist：该区不存在 · Please select the district where the site is located：请选择站点所在的区 · The system service does not respond：系统服务未响应 |
|
关键字 |
DELETE_UC_SITE_CUSTOM |
|
日志内容 |
Deleted custom U-Center site. |
|
参数解释 |
无 |
|
举例 |
Deleted custom U-Center site. |
|
日志说明 |
用户进行了删除站点的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The UUID is invalid：无效的UUID · The specified site does not exist：指定的站点名称不存在 · The system service does not respond：系统服务未响应 |
|
关键字 |
CREATE_UC_OUT_NETWORK_TRAFFIC_CUSTOM |
|
日志内容 |
Created custom U-Center outgoing external flow. |
|
参数解释 |
无 |
|
举例 |
Created custom U-Center outing external flow. |
|
日志说明 |
用户进行了创建出外网流量的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · The external network traffic has been bound：同设备端口已被用户绑定 · The fabric ID is required：Fabric ID必选 · Please specify a fabric ID：Fabric ID不能为空 · Invalid fabric ID：无效的Fabric ID · The fabric name is required：Fabric Name必选 · Please specify a fabric name：Fabric Name不能为空 · Invalid fabric name：无效的Fabric Name · The group ID is required：Group ID必选 · Please specify a group ID：Group ID不能为空 · Invalid group ID：无效的Group ID · The device ID is required：无效的Device ID · Please specify a device ID：Device ID不能为空 · Invalid device ID：无效的Device ID · The device IP is required：Device IP必选 · Please specify a device IP：Device IP不能为空 · Invalid device IP：无效的Device IP · The device name is required：Device Name必选 · Please specify a device name：Device Name不能为空 · Invalid device name：无效的Device Name · The interface name is required：Interface Name必选 · The interface name is required：Interface Name必选 · Invalid interface name：无效的Interface Name · The specified fabric ID does not exist：指定的Fabric ID不存在 · The specified group ID does not exist：指定的Group ID不存在 · The specified fabric name does not exist：指定的Fabric Name不存在 · The specified device ID does not exist：指定的Device ID不存在 · The specified device IP does not exist：指定的Device IP不存在 · The specified device name does not exist：指定的Device Name不存在 · The specified interface name does not exist：指定的Interface Name不存在 · DataCenter service is not available：DC服务不可用 · The system service does not respond：系统服务未响应 |
|
关键字 |
UPDATE_UC_OUT_NETWORK_TRAFFIC_CUSTOM |
|
日志内容 |
Updated custom U-Center outgoing external flow. |
|
参数解释 |
无 |
|
举例 |
Updated custom U-Center outgoing external flow. |
|
日志说明 |
用户进行了修改出外网流量的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · The UUID is invalid：无效的UUID · The fabric ID is required：Fabric ID必选 · Please specify a fabric ID：Fabric ID不能为空 · Invalid fabric ID：无效的Fabric ID · The fabric name is required：Fabric Name必选 · Please specify a fabric name：Fabric Name不能为空 · Invalid fabric name：无效的Fabric Name · The group ID is required：Group ID必选 · Please specify a group ID：Group ID不能为空 · Invalid group ID：无效的Group ID · The device ID is required：无效的Device ID · Please specify a device ID：Device ID不能为空 · Invalid device ID：无效的Device ID · The device IP is required：Device IP必选 · Please specify a device IP：Device IP不能为空 · Invalid device IP：无效的Device IP · The device name is required：Device Name必选 · Please specify a device name：Device Name不能为空 · Invalid device name：无效的Device Name · The interface name is required：Interface Name必选 · The interface name is required：Interface Name必选 · Invalid interface name：无效的Interface Name · The specified fabric ID does not exist：指定的Fabric ID不存在 · The specified groupID does not exist：指定的Group ID不存在 · The specified fabric name does not exist：指定的Fabric Name不存在 · The specified device ID does not exist：指定的Device ID不存在 · The specified device IP does not exist：指定的Device IP不存在 · The specified device name does not exist：指定的Device Name不存在 · The specified interface name does not exist：指定的Interface Name不存在 · The DC service is unavailable：DC服务不可用 · The custom info does not exist：定制信息不存在 · The system service does not respond：系统服务未响应 |
|
关键字 |
CREATE_UC_OUT_NETWORK_TRAFFIC_CUSTOM |
|
日志内容 |
Deleted custom U-Center outgoing external flow. |
|
参数解释 |
无 |
|
举例 |
Deleted custom U-Center outgoing external flow. |
|
日志说明 |
用户进行了删除出外网流量的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The UUID is invalid：无效的UUID · The custom info does not exist.：定制信息不存在 · The system service does not respond：系统服务未响应 |
|
关键字 |
CREATE_UC_SERVICE_TRAFFIC_CUSTOM |
|
日志内容 |
Created custom U-Center service flow. |
|
参数解释 |
无 |
|
举例 |
Created custom U-Center service flow. |
|
日志说明 |
用户进行了创建流量个性化配置的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request message body is empty：请求体为空 · The traffic type must be LB or FW：流量类型必须为LB或FW · The traffic type is required：流量类型必选 · The traffic attribute is required：流量属性必选 · The traffic attribute must be incoming traffic or outgoing traffic：流量属性必须为入流量或出流量 · Invalid tenant name：无效的租户名称 · The specified tenant name does not exist：指定的租户名称不存在 · A flow of the specified type already exists：该类型的流量已存在个性化配置 · The DC service is unavailable：DC服务不可用 · The system service does not respond：系统服务未响应 |
|
关键字 |
UPDATE_UC_SERVICE_TRAFFIC_CUSTOM |
|
日志内容 |
Updated custom U-Center service flow. |
|
参数解释 |
无 |
|
举例 |
Updated custom U-Center service flow. |
|
日志说明 |
用户进行了修改流量个性化配置的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The UUID is invalid：无效的UUID · The request message body is empty：请求体为空 · The traffic type must be LB or FW：流量类型必须为LB或FW · The traffic type is required：流量类型必选 · The traffic attribute is required：流量属性必选 · The traffic attribute must be incoming traffic or outgoing traffic：流量属性必须为入流量或出流量 · Invalid tenant name：无效的租户名称 · The specified tenant name does not exist：指定的租户名称不存在 · The DC service is unavailable：DC服务不可用 · The system service does not respond：系统服务未响应 |
|
关键字 |
DELETE_UC_SERVICE_TRAFFIC_CUSTOM |
|
日志内容 |
Deleted custom U-Center service flow. |
|
参数解释 |
无 |
|
举例 |
Deleted custom U-Center service flow. |
|
日志说明 |
用户进行了删除流量个性化配置的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The UUID is invalid：无效的UUID · The custom info does not exist：定制信息不存在 · The system service does not respond：系统服务未响应 |
本节介绍故障应急预案模板模块输出的操作日志信息。
|
关键字 |
CREATE_EMERGENCY_PLAN_TEMPLATE_OP |
|
日志内容 |
Created contingency plan template: $1. |
|
参数解释 |
$1：故障应急预案模板的配置信息 |
|
举例 |
Created contingency plan template: { "templates":[ { "description":"dsafsadsad", "name":"adsfad", "operations":[ { "action":"PortShutdown", "enableRevert":true, "objectData":"XGE3/0/45,XGE3/0/46,XGE3/0/47", "objectId":"09a6e5b4-4932-4a84-98de-ee6ef685d323", "objectType":"PORT" } ], "type":"PortTemplate" } ] } |
|
日志说明 |
用户进行了创建故障应急预案模板的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid parameter：无效的参数 · Invalid name：无效的名称 · Invalid description：无效的描述 · Invalid template type：无效的模板类型 · Invalid action：无效的操作 · Invalid object type：无效的操作对象类型 · The template name already exists：模板名称已存在 · Please specify execution actions：执行动作不能为空 · Please specify a template name: 预案模板名称不能为空 · Please specify template type: 模板类型不能为空 · The template type and the object type do not match：预案模板类型与操作对象类型不匹配 · The action and the object type do not match：操作与操作对象类型不匹配 · The configuration contains repeated content：配置信息中存在重复的内容 · Invalid JSON format：无效的JSON格式 · The system does not respond：系统服务未响应 · Invalid UUID for the template：无效的模板UUID · The template ID already exists：指定的模板ID已存在 · Invalid template ID：无效的预案模板ID · Invalid action ID：无效的操作ID · The action ID already exists：指定的操作ID已存在 · Invalid target objects：无效的操作对象 · Please specify target objects：操作对象类型不能为空 · Invalid target object ID：无效的操作对象ID · Up to 128 ports can be added to an action：一个执行动作最多允许添加128个端口 · Some actions are not supported by the template：执行动作列表中存在与预案模版不匹配的动作 · Up to 10 actions can be added to a contingency plan template：预案模板最多允许添加10个动作 · Duplicate port names：端口列表中存在名称重复的端口 · The specified object ID doesn't exist：指定的操作对象ID不存在 · Up to 5000 templates can be added：最多允许添加5000个预案模板 |
|
关键字 |
UPDATE_EMERGENCY_PLAN_TEMPLATE_OP |
|
日志内容 |
Updated contingency plan template: $1 |
|
参数解释 |
$1：故障应急预案模板的配置信息 |
|
举例 |
Updated contingency plan template: { "template": { "description":"dsafsadsad", "id":"59576db2-97d3-446d-94c8-82d9c099028e", "operations":[ { "action":"PortShutdown", "enableRevert":true, "objectData":"XGE3/0/45,XGE3/0/46,XGE3/0/47", "objectId":"09a6e5b4-4932-4a84-98de-ee6ef685d323", "objectType":"PORT", "operationId":"90c9790a-33c3-4367-9340-fb0662c5d309" } ] } } |
|
日志说明 |
用户进行了修改故障应急预案模板的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid parameter：无效的参数 · Invalid description：无效的描述 · Invalid action：无效的操作 · Invalid template type: 无效的模板类型 · Invalid object type：无效的操作对象类型 · Execution action cannot be empty：执行动作不能为空 · The template type and the object type do not match：预案模板类型与操作对象类型不匹配 · The action and the object type do not match：操作与操作对象类型不匹配 · The configuration contains repeated content：配置信息中存在重复的内容 · Invalid JSON format：无效的JSON格式 · The system does not respond：系统服务未响应 · Cannot edit the template name：预案模板名称不允许修改 · Cannot edit the template type：预案模板类型不允许修改 · The specified template doesn't exist：指定的预案模板不存在 · You cannot edit the template ID：预案模板ID不允许修改 · The specified template is being excused, cannot update it：指定的预案模板正在执行动作，不允许修改 · Invalid target objects：无效的操作对象 · Please specify an action: 动作不能为空 · Please specify target objects：端口模版的操作对象不能为空 · Invalid target object ID：无效的操作对象ID · The specified object ID doesn't exist: 指定的操作对象ID不存在 · Up to 128 ports can be added to an action：一个执行动作最多允许添加128个端口 · Some actions are not supported by the template：执行动作列表中存在与预案模版不匹配的动作 · Up to 10 actions can be added to a contingency plan template：预案模板最多允许添加10个动作 · Duplicate port names：端口列表中存在名称重复的端口 · You cannot specify an action to isolate the peer port on the remote device for an atom template that has been added to a composite template：已被绑定的原子模板中不允许包含对端设备互连接口隔离的执行动作 |
|
关键字 |
DELETE_EMERGENCY_PLAN_TEMPLATE_OP |
|
日志内容 |
Deleted contingency plan template: $1 |
|
参数解释 |
$1：故障应急预案模板的配置信息 |
|
举例 |
Deleted contingency plan template: { "description":"dsafsadsad", "id":"59576db2-97d3-446d-94c8-82d9c099028e", "name":"adsfad", "operations":[ { "action":"PortShutdown", "enableRevert":true, "objectData":"XGE3/0/45,XGE3/0/46,XGE3/0/47", "objectId":"09a6e5b4-4932-4a84-98de-ee6ef685d323", "objectType":"PORT", "operationId":"90c9790a-33c3-4367-9340-fb0662c5d309" } ], "revertOperations":[ { "action":"PortUndoShutdown", "enableRevert":true, "objectData":"XGE3/0/45,XGE3/0/46,XGE3/0/47", "objectId":"09a6e5b4-4932-4a84-98de-ee6ef685d323", "objectType":"PORT", "operationId":"90c9790a-33c3-4367-9340-fb0662c5d309" } ], "type":"PortTemplate" } |
|
日志说明 |
用户进行了删除故障应急预案模板的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The specified atom template doesn't exist：指定的原子模板不存在 · The specified template is being excused, cannot delete it：指定的模板正在执行动作，不允许删除 · The specified atom template has been bound to another composite template：指定的原子模板已被其他集成模板绑定 |
|
关键字 |
EXCUTE_EMERGENCY_PLAN_TEMPLATE_OP |
|
日志内容 |
Executed contingency plan template: $1 |
|
参数解释 |
$1：故障应急预案模板的配置信息 |
|
举例 |
Executed contingency plan template: { "operations":[ { "operationId":"ab202e04-3e4d-46d4-ba50-ad3d4832bc02", "objectData":"PORT", "objectType":"2594:GE1/0/1,GE1/0/2,GE1/0/3", "objectId":"f4a9db90-4c42-438d-b856-a5a436fab8a7" } |
|
日志说明 |
用户进行了执行故障应急预案模板的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Please specify all required parameters：参数不能为空 · Please specify a template ID：预案模板ID不能为空 · Invalid template ID：无效的预案模板ID · The specified template ID does not exist：指定的预案模板ID不存在 · Please specify an action ID：操作ID不能为空 · Invalid action ID：无效的操作ID · Please specify target objects：操作对象不能为空 · Invalid target objects：无效的操作对象 · Please specify a target object type：操作对象类型不能为空 · Invalid target object type：无效的操作对象类型 · Please specify a target object ID：操作对象ID不能为空 · Invalid target object ID：无效的操作对象ID · Please specify actions：执行动作列表不能为空 · Some actions are not supported by the template：执行动作列表中存在与预案模版不匹配的动作 · Failed to add the device configuration fragments：添加配置片段失败 · Failed to deploy the device configuration fragments：下发配置片段失败 · Failed to deploy the NETCONF configuration：下发NETCONF配置失败 · The system service does not respond：系统服务未响应 · The object ID is already expired：操作对象已过期，请重新绑定 · Failed to execute the virtual machine manager template：虚拟化软件平台模板执行失败 · Failed to isolate the virtual machine manager template：虚拟化软件平台模板隔离失败 · Failed to restore the virtual machine manager template：虚拟化软件平台模板恢复失败 |
|
关键字 |
REVERT_HISTORY_OP |
|
日志内容 |
Reverted history operation: $1. |
|
参数解释 |
$1：历史预案模板的配置信息 |
|
举例 |
Reverted history operation: { "id": "c23918bf-8b52-4a90-89e3-cde81c16b5c7", "templateId": "b4ba9201-0524-44e9-9c6d-9ade3455c792", "templateName": "device-template", "templateType": "DeviceTemplate", "objectId": "33ab8ea34-1478-4708-b3b4-7f2f4f5d9b33", "objectData": "s3333", "objectType": "DEVICE", "enableRevert": true, "action": "UndoDeviceIsolation", "actionSource" : "0", "revertedAction": true, "executeStatus": 2, "startTime": "2018-02-02 22:56:27", "endTime": "2018-02-02 22:57:27" }. |
|
日志说明 |
用户进行了还原历史预案模板的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Please specify a history action ID：历史操作ID不能为空 · Invalid history action ID：无效的历史操作ID · The specified history action does not exist：指定的历史记录不存在 · The history action cannot be reverted：指定动作不支持回退 · The specified history action has been reverted：指定历史操作已回退 · The history action in a state where it cannot be reverted：历史记录的执行状态不支持回退 · Failed to add the device configuration fragments：添加配置片段失败 · Failed to deploy the device configuration fragments：下发配置片段失败 · Failed to deploy the NETCONF configuration：下发NETCONF配置失败 · The system service does not respond：系统服务未响应 · Failed to isolate the virtual machine manager template：虚拟化软件平台模板隔离失败 · Failed to restore the virtual machine manager template：虚拟化软件平台模板恢复失败 |
|
关键字 |
EXCUTE_EMERGENCY_PLAN_COMPOUND_TEMPLATE_OP |
|
日志内容 |
Executed contingency plan composite template: $1 |
|
参数解释 |
$1：故障应急预案集成模板的配置信息 |
|
举例 |
Executed contingency plan composite template: { "templates": [ { "templateId": "d3ab8ea34-1478-4708-b3b4-7f2f4f5d9b33", "operations": [ { "operationId": "33ab8ea34-1478-4708-b3b4-7f2f4f5d9b33", "objectType": "PORT", "objectId": "7e69f76e-75f9-4ffd-82f0-f35572ebb66a", "objectData": "HGE1/0/5,HGE1/0/6" } ] } ] } |
|
日志说明 |
用户进行了执行故障应急预案集成模板的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Please specify all required parameters：参数不能为空 · Please specify a template ID：原子模板ID不能为空 · Invalid template ID：无效的原子模板ID · The specified template ID does not exist：指定的原子模板ID不存在 · Please specify an action ID：操作ID不能为空 · Invalid action ID：无效的操作ID · Please specify target objects：操作对象不能为空 · Invalid target objects：无效的操作对象 · Please specify a target object type：操作对象类型不能为空 · Invalid target object type：无效的操作对象类型 · Please specify a target object ID：操作对象ID不能为空 · Invalid target object ID：无效的操作对象ID · Please specify actions：执行动作列表不能为空 · Some actions are not supported by the template：执行动作列表中存在与原子模版不匹配的动作 · Failed to add the device configuration fragments：添加配置片段失败 · Failed to deploy the device configuration fragments：下发配置片段失败 · Failed to deploy the NETCONF configuration：下发NETCONF配置失败 · The system service does not respond：系统服务未响应 · Please specify composite template ID：集成模板ID不能为空 · You cannot specify an action to isolate the peer port on the remote device for an atom template that has been added to a composite template：已被绑定的原子模板中不允许包含对端设备互连接口隔离的执行动作 |
|
关键字 |
ACTION_CREATE_COMPOUND_TEMPLATE |
|
日志内容 |
Created contingency composite template: $1. |
|
参数解释 |
$1：故障应急预案集成模板的配置信息 |
|
举例 |
Created contingency composite template: { "compoundTemplates": [ { "name": "port compound template ", "description": "template description", "templates": [ { "templateId": "00000000-0000-0000-0000-000000000001", "order": 1 }, { "templateId": "00000000-0000-0000-0000-000000000002", "order": 2 } ] } ] } |
|
日志说明 |
用户进行了创建故障应急预案集成模板的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Please specify all required parameters：参数不能为空 · Please specify a name for the composite template：集成模板名称不能为空 · A composite template already exists with the specified name：集成模板名称已存在 · Invalid UUID for the template：无效的模板UUID · The value range for the order parameter is 1 to 10：order参数取值范围为1~10 · The specified template doesn't exist：指定的预案模板不存在 · Please add a minimum of one atom templates to the composite template. A composite template can contain a maximum of 10 atom templates：集成模板必须绑定原子模板，至少绑定1个，且最多绑定10个 · Duplicate value for the order field in the atom template：原子模板order字段取值重复 · A atom template already exists with the specified UUID：指定UUID的原子模板已存在 · The atom template contains an action to isolate the peer port on the remote device and cannot be added to the composite template：该原子模板包含对端设备互连接口隔离动作，不能被集成模板绑定 |
|
关键字 |
ACTION_UPDATE_COMPOUND_TEMPLATE |
|
日志内容 |
Updated contingency composite template: $1. |
|
参数解释 |
$1：故障应急预案集成模板的配置信息 |
|
举例 |
Updated contingency composite template: { "compoundTemplates": [ { "description": "template description", "templates": [ { "templateId": "00000000-0000-0000-0000-000000000001", "order": 1 }, { "templateId": "00000000-0000-0000-0000-000000000002", "order": 2 } ] } ] } |
|
日志说明 |
用户进行了创建故障应急预案集成模板的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Please specify all required parameters：参数不能为空 · You cannot edit the name of a composite template：集成模板名称不允许修改 · The ID for the composite template is invalid：无效的集成模板ID · The specified composite template does not exist：指定的集成模板不存在 · Invalid UUID for the template：无效的模板UUID · A atom template already exists with the specified UUID：指定UUID的原子模板已存在 · The value range for the order parameter is 1 to 10：order参数取值范围为1~10 · Duplicate value for the order field in the atom template：原子模板order字段取值重复 · The atom template contains an action to isolate the peer port on the remote device and cannot be added to the composite template：该原子模板包含对端设备互连接口隔离动作，不能被集成模板绑定 · A atom template already exists with the specified UUID：指定UUID的原子模板已存在 |
|
关键字 |
ACTION_DELETE_COMPOUND_TEMPLATE |
|
日志内容 |
Deleted contingency composite template: $1. |
|
参数解释 |
$1：故障应急预案集成模板的ID |
|
举例 |
Deleted contingency composite template: baa895f1-f361-4310-b004-10812e7830be |
|
日志说明 |
用户进行了创建故障应急预案集成模板的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The UUID for the composite template is invalid：无效的集成模板UUID · The specified composite template does not exist：指定的集成模板不存在 |
本节介绍Fabrics模块输出的操作日志信息。
|
关键字 |
CREATE_FABRIC_OP |
|
日志内容 |
Created fabric: $1 |
|
参数解释 |
$1：Fabric的名称 |
|
举例 |
Created fabric: “fabric1”. |
|
日志说明 |
用户进行了创建Fabric的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置正在恢复过程中 · The service has not been found：服务未启动 · The controller is not the active leader：该控制组件不是主Leader · The fabric already exists：指定的Fabric已存在 · The fabric name already exists：指定的Fabric名称已存在 · Parameters (parameters) are required：(parameters)参数为必选项 · Unknown error：未知错误 · The request is invalid：无效的请求 · Failed to create the fabric：Fabric创建失败 · The fabric name cannot exceed 255 characters：Fabric名称长度不能超过255个字符 · The VTEP IP allocation mode is incorrect：VTEP IP分配方式有误 · The underlay protocol is invalid：无效的Underlay协议 · The AS number is invalid：无效的AS号 · The AS number already exists：指定的AS号已存在 · Invalid ARP configuration：无效的ARP配置 · Invalid ARP proxy configuration：无效的ARP代答配置 · Invalid ARP flooding configuration：无效的ARP泛洪配置 · Invalid ARP to controller configuration：无效的ARP上送控制组件配置 · Invalid RARP configuration：无效的RARP配置 · Invalid RARP to controller configuration：无效的RARP上送控制组件配置 · Invalid RARP flooding configuration：无效的RARP泛洪配置 · Invalid DHCP configuration：无效的DHCP配置 · Invalid DHCP to controller configuration：无效的DHCP上送控制组件配置 · Invalid ND configuration：无效的ND配置 · Invalid ND proxy configuration：无效的ND代答配置 · Invalid NSNA flooding configuration：无效的NSNA泛洪配置 · Invalid NSNA to controller configuration：无效的NSNA报文上送控制组件配置 · Invalid RSRA to controller configuration：无效的RSRA报文上送控制组件配置 · Invalid RSRA flooding configuration：无效的RSRA报文泛洪配置 · Invalid DHCPv6 configuration：无效的DHCPv6配置 · Invalid DHCPv6 to controller configuration：无效的DHCPv6报文上送控制组件配置 · Invalid mac advertising configuration：无效的MAC地址通告开关 · The RR MAC address list contains invalid MAC addresses：RR设备的MAC地址列表中存在不合法地址 · You must create an auto deployment device information for the fabric when the underlay protocol is IS-IS and the master spine is configured to assign VTEP IPs：当Underlay协议为ISIS时且VTEP IP的分配方式为Master Spine时，Fabric必须创建自动化部署的设备信息 · The default fabric ID cannot be used：不允许使用默认Fabric ID · The fabric name is default fabric name：指定修改的Fabric名称为默认Fabric名称 · The VTEP IP allocation mode is incorrect：VTEP IP分配方式有误 · You have no privilege to perform this operation：用户无权限执行此操作 · Failed to change the AS number, because the new AS number introduces RT conflicts：指定的AS号存在RT冲突，不允许修改 · The MTU must be an integer in the range of 68 to 9216：MTU取值范围为68～9216的整数 · Invalid ARP standard forwarding configuration：无效的ARP普通转发配置 · Invalid ND standard forwarding configuration：无效的ND普通转发配置 · If a fabric has a full-mesh fabric connection, you cannot enable the IPv6 multicast network feature for that fabric：存在全互联的Fabric连接时，不支持开启IPv6组播网络 · When you specify an overlay BGP AS number, make sure the RT generated based on that AS number is different from any RT of an existing Layer 2 DC interconnect, Layer 3 DC interconnect or vRouter：Overlay路由协议BGP AS号所产生的RT和数据中心二层互联、数据中心三层互联或虚拟路由器的RT存在重叠 · The old and new AS numbers are inconsistent：新旧AS号字段不一致 |
|
关键字 |
UPDATE_FABRIC _OP |
|
日志内容 |
Updated fabric: $1 |
|
参数解释 |
$1：Fabric的名称 |
|
举例 |
Updated fabric: “fabric1”. |
|
日志说明 |
用户进行了修改Fabric的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置正在恢复过程中 · The service has not been found：服务未启动 · The controller is not the active leader：该控制组件不是主Leader · The fabric does not exist：指定的Fabric不存在 · The fabric name already exists：指定的Fabric名称已存在 · Parameters (parameters) cannot be modified：(parameters)参数不允许修改 · Unknown error：未知错误 · The request is invalid：无效的请求 · The fabric name cannot exceed 255 characters：Fabric名称长度不能超过255个字符 · The VTEP IP allocation mode is incorrect：VTEP IP分配方式有误 · The underlay protocol is invalid：无效的Underlay协议 · Invalid ARP configuration：无效的ARP配置 · Invalid ARP proxy configuration：无效的ARP代答配置 · Invalid ARP flooding configuration：无效的ARP泛洪配置 · Invalid ARP to controller configuration：无效的ARP上送控制组件配置 · Invalid RARP configuration：无效的RARP配置 · Invalid RARP to controller configuration：无效的RARP上送控制组件配置 · Invalid RARP flooding configuration：无效的RARP泛洪配置 · Invalid DHCP configuration：无效的DHCP配置 · Invalid DHCP to controller configuration：无效的DHCP上送控制组件配置 · Invalid ND configuration：无效的ND配置 · Invalid ND proxy configuration：无效的ND代答配置 · Invalid NSNA flooding configuration：无效的NSNA泛洪配置 · Invalid NSNA to controller configuration：无效的NSNA报文上送控制组件配置 · Invalid RSRA to controller configuration：无效的RSRA报文上送控制组件配置 · Invalid RSRA flooding configuration：无效的RSRA报文泛洪配置 · Invalid DHCPv6 configuration：无效的DHCPv6配置 · Invalid DHCPv6 to controller configuration：无效的DHCPv6报文上送控制组件配置 · Invalid mac advertising configuration：无效的MAC地址通告开关 · The underlay protocol is used by a deployment resource pool, and cannot be modified：Underlay协议已被管理部署资源池使用，不允许修改 · The underlay protocol is used by a device deployment template, and cannot be modified：Underlay协议已被设备上线模板使用，不允许修改 · The RR MAC cannot be modified because the corresponding device is active：当前RR MAC地址对应的设备处于激活状态，MAC地址不允许修改 · You must create an auto deployment device information for the fabric when the underlay protocol is IS-IS and the master spine is configured to assign VTEP IPs：当Underlay协议为ISIS时且VTEP IP的分配方式为Master Spine时，Fabric必须创建自动化部署的设备信息 · The VTEP IP allocation method has been bound to an address pool, and cannot be modified：VTEP IP分配方式已绑定地址池，不允许修改 · The VTEP IP allocation method has been bound to a device deployment template, and cannot be modified：VTEP IP分配方式已绑定设备上线模板，不允许修改 · The fabric name is default fabric name：指定修改的Fabric名称为默认Fabric名称 · The default fabric name cannot be modified：默认Fabric名称不允许修改 · Failed to update the default fabric：修改默认Fabric失败 · The VTEP IP allocation method has been bound to an address pool, and cannot be modified：VTEP IP分配方式已绑定地址池，不允许修改 · The VTEP IP allocation method has been bound to a device deployment template, and cannot be modified：VTEP IP分配方式已绑定设备上线模板，不允许修改 · Cannot modify the AS number of the fabric in which the border devices already have DC connections established.：Fabric中的边界设备已建立数据中心连接，不允许修改AS号 · You have no privilege to perform this operation：用户无权限执行此操作 · Cannot enable multicast network capabilities because the fabric has been added to a fabric connection：指定的Fabric已经创建了Fabric连接，不允许开启组播网络 · Failed to change the AS number, because the new AS number introduces RT conflicts：指定的AS号存在RT冲突，不允许修改 · The MTU must be an integer in the range of 68 to 9216：MTU取值范围为68～9216的整数 · Invalid ARP standard forwarding configuration：无效的ARP普通转发配置 · Invalid ND standard forwarding configuration：无效的ND普通转发配置 · You cannot enable the IPv6 multicast network capability of the fabric, because the fabric is already added to a fabric connection：指定的Fabric已经创建了Fabric连接，不允许开启IPv6组播网络 · You cannot change the value for the AS number, because it has been specified in a device configuration template：指定的AS号已被设备配置模板使用，不允许非等值修改 · The old and new AS numbers are inconsistent：新旧AS号字段不一致 |
|
关键字 |
DELETE_FABRIC _OP |
|
日志内容 |
Deleted fabric: $1 |
|
参数解释 |
$1：Fabric的名称 |
|
举例 |
Deleted fabric: “fabric1”. |
|
日志说明 |
用户进行了删除Fabric的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置正在恢复过程中 · The service has not been found：服务未启动 · The controller is not the active leader：该控制组件不是主Leader · The fabric does not exist：指定的Fabric不存在 · Unknown error：未知错误 · The request is invalid：无效的请求 · The fabric has devices：Fabric中存在已被纳管的设备 · The fabric has device groups：Fabric中存在已被纳管的设备组 · The fabric is being used by a host：Fabric正在被主机使用 · The fabric is being used by a DHCP host group：Fabric正在被DHCP主机组使用 · The fabric is used by a deployment template, and cannot be deleted：Fabric已被设备上线模板引用，不允许删除 · The fabric is used by a device control protocol template, and cannot be deleted：Fabric已被设备控制协议模板引用，不允许删除 · The fabric is used by a deployment resource pool, and cannot be deleted：Fabric已被管理部署资源池引用，不允许删除 · You have no privilege to perform this operation：用户无权限执行此操作 · You cannot delete the fabric. It has been bound to a BGP peer：该Fabric已被BGP对等体绑定，不允许删除 · The fabric is used by a bgp instance, and cannot be deleted：该Fabric已被BGP实例引用，不允许删除 · The fabric is being used by a fabric connection：Fabric正在被Fabric连接使用 · The fabric is used by an auto deployment device information, and cannot be deleted：Fabric已被自动化部署的设备信息引用，不允许删除 |
|
关键字 |
SEARCH_FABRIC _OP |
|
日志内容 |
Searched fabric: $1 |
|
参数解释 |
$1：Fabric的UUID，当不指定该参数时表示查询所有Fabric信息 |
|
举例 |
Searched fabric: 218b5f2f-e435-4365-a1ab-0eaa03b7fa19 |
|
日志说明 |
用户进行了查询Fabric信息的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置正在恢复过程中 · The service has not been found：服务未启动 · The controller is not the active leader：该控制组件不是主Leader · The fabric does not exist：指定的Fabric不存在 · Unknown error：未知错误 · The request is invalid：无效的请求 · The page number must be an integer in the range of 1 to 2147483647：页数取值范围为1～2147483647的整数 · The number of items per page must be an integer in the range of 1 to 2147483647：每页显示个数的取值范围为1～2147483647的整数 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_FABRIC_CONNECTION_OP |
|
日志内容 |
Created fabric connection: $1 |
|
参数解释 |
$1：Fabric连接的配置信息 |
|
举例 |
Created fabric connection: ID:[e7f605c0-2336-4e4a-8586-69cd543455bc] Name:[e7f605c0-2336-4e4a-8586-69cd543455bc] VDS ID:[ffffffff-0000-0000-0000-000000000001] Connection type:[DEFINED] Default fabric connection:[false] ED groups:[ Local ED ID: d4dd289e-ae05-43c3-b2ee-16be09a01f3f Peer ED ID: b1b2003c-dbe0-43f4-bea2-40c76edd1a32 Local ED ID: d4dd289e-ae05-43c3-b2ee-16be09a01f3f Peer ED ID: c20e22a7-3c95-4f3a-8a70-fb8b8d2b6576 Local ED ID: b1b2003c-dbe0-43f4-bea2-40c76edd1a32 Peer ED ID: c20e22a7-3c95-4f3a-8a70-fb8b8d2b6576 ] |
|
日志说明 |
用户进行了创建Fabric连接的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · Invalid JSON format：无效的JSON格式 · The service is disabled：服务未启动 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Please specify the VDS ID：未指定VDS ID · The VDS does not exist：指定的VDS不存在 · The VDS already has a fabric connection：指定的VDS已与其他Fabric连接绑定 · The fabric connection already exists：Fabric连接已存在 · The fabric connection name already exists：Fabric连接的名称已经存在 · The fabric connection type is required：未指定连接类型 · Invalid name：无效的名称 · The fabric connection type is invalid：无效的连接类型 · The VSM service does not exist：VSM服务不存在 · Invalid VDS ID：无效的VDS ID · The ED group settings are invalid：无效的ED组配置 · Invalid local or peer ED exist：ED组中的本端或对端ED无效 · Cannot configure ED group settings when the fabric connection type is ALLCONNECT：当Fabric连接类型为全互联时不允许指定ED组配置 · The ED group settings are required when the fabric connection type is DEFINED：当Fabric连接类型为自定义时，必须指定ED组配置 · Cannot specify nonexistent EDs：本端或对端ED对应的网元不存在 · The local and peer EDs cannot be the same：本端和对端ED不允许相同 · The local and peer EDs in an ED group cannot belong to the same fabric：本端和对端ED不允许属于同一个Fabric · The local or peer ED is not added to a DC interconnection device group：本端ED或者对端ED未加入到DC互联类型的设备组中 · Unknown internal server error：未知的内部服务器错误 · You have no privilege to perform this operation：用户无权限执行此操作 · Cannot configure a fabric connection because multicast network capabilities have been enabled for the fabric：指定Fabric下已开启组播网络，不允许配置Fabric连接 · The source and destination devices must use the same version of VTEP IP addresses to establish a fabric connection：源设备和目的设备的VTEP IP版本不一致 · You cannot add the fabric connection, because the specified fabrics are already enabled with the IPv6 multicast network capability：指定Fabric已开启IPv6组播网络，不允许配置Fabric连接 |
|
关键字 |
UPDATE_FABRIC_CONNECTION_OP |
|
日志内容 |
Updated fabric connection: $1 |
|
参数解释 |
$1：Fabric连接的配置信息 |
|
举例 |
Updated fabric connection: ID:[e7f605c0-2336-4e4a-8586-69cd543455bc] Connection type:[DEFINED] Default fabric connection:[false] ED groups:[ Local ED ID: d4dd289e-ae05-43c3-b2ee-16be09a01f3f Peer ED ID: b1b2003c-dbe0-43f4-bea2-40c76edd1a32 Local ED ID: d4dd289e-ae05-43c3-b2ee-16be09a01f3f Peer ED ID: c20e22a7-3c95-4f3a-8a70-fb8b8d2b6576 Local ED ID: b1b2003c-dbe0-43f4-bea2-40c76edd1a32 Peer ED ID: c20e22a7-3c95-4f3a-8a70-fb8b8d2b6576 ] |
|
日志说明 |
用户进行了修改Fabric连接的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · Invalid JSON format：无效的JSON格式 · The service is disabled：服务未启动 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · The fabric connection already exists：Fabric连接已存在 · The fabric connection name already exists：Fabric连接的名称已经存在 · The fabric connection type is required：未指定连接类型 · Read-only parameters cannot be modified：修改时不允许携带只读字段 · Invalid name：无效的名称 · The fabric connection type is invalid：无效的连接类型 · The VSM service does not exist：VSM服务不存在 · Invalid VDS ID：无效的VDS ID · The ED group settings are invalid：无效的ED组配置 · Invalid local or peer ED exist：ED组中的本端或对端ED无效 · Cannot configure ED group settings when the fabric connection type is ALLCONNECT：当Fabric连接类型为全互联时不允许指定ED组配置 · The ED group settings are required when the fabric connection type is DEFINED：当Fabric连接类型为自定义时，必须指定ED组配置 · Cannot specify nonexistent EDs：本端或对端ED对应的网元不存在 · The local and peer EDs cannot be the same：本端和对端ED不允许相同 · The local and peer EDs in an ED group cannot belong to the same fabric：本端和对端ED不允许属于同一个Fabric · The local or peer ED is not added to a DC interconnection device group：本端ED或者对端ED未加入到DC互联类型的设备组中 · Unknown internal server error：未知的内部服务器错误 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_FABRIC_CONNECTION_OP |
|
日志内容 |
Deleted fabric connection: $1 |
|
参数解释 |
$1：Fabric连接的UUID |
|
举例 |
Deleted fabric connection: 218b5f2f-e435-4365-a1ab-0eaa03b7fa19 |
|
日志说明 |
用户进行了删除Fabric连接的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · Invalid JSON format：无效的JSON格式 · The service is disabled：服务未启动 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · The fabric connection UUID is required：未指定Fabric连接的UUID · The fabric connection does not exist：指定的Fabric连接不存在 · Unknown internal server error：未知的内部服务器错误 · You have no privilege to perform this operation：用户无权限执行此操作 |
本节介绍防火墙服务模块输出的操作日志信息。
|
关键字 |
CREATE_TIMERANGE_OP |
|
日志内容 |
Created time range $1. |
|
参数解释 |
$1：时间段配置信息 |
|
举例 |
Created time range ID: 9a83d713-8e79-4ca8-a2e9-8df29daf5fd6 Tenant ID: ffffffff-0000-0000-0000-000000000001 Name: tr Description: time range Shared: false In use: false Periodic range list: Position: 1 Start time: 00:00 End time: 24:00 Days of week: [MON, TUE, WED, THU, FRI, SAT] Absolute range list: Position: 1 Start time: 00:00 Start date: 2014-08-02 End time: 24:00 End date: 2100-12-31. |
|
日志说明 |
用户进行了创建时间段的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The configuration item already exists：配置项已存在 · The tenant specified for the configuration item doesn't exist：配置项指定的租户不存在 · The number of configuration items exceeded the limit：配置项个数超出限制 · The controller is not the active leader：该控制组件不是主Leader · The operation requires the administrator privilege：您需要管理员权限才能执行此操作 · Configuration recovery is in progress：配置正在恢复过程中 · The firewall service has not been found：防火墙服务未启动 · The inused field should be read only：时间段状态为只读字段 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_TIMERANGE_OP |
|
日志内容 |
Updated time range $1. |
|
参数解释 |
$1：时间段配置信息 |
|
举例 |
Updated time range ID: 9a83d713-8e79-4ca8-a2e9-8df29daf5fd6 Tenant ID: ffffffff-0000-0000-0000-000000000001 Name: tr Description: time range Shared: false In use: false Periodic range list: Position: 1 Start time: 00:00 End time: 20:00 Days of week: [MON, TUE, WED, THU, FRI, SAT] Absolute range list: Position: 1 Start time: 00:00 Start date: 2014-08-02 End time: 24:00 End date: 2100-12-30. |
|
日志说明 |
用户进行了修改时间段的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · The operation requires the administrator privilege：您需要管理员权限才能执行此操作 · Configuration recovery is in progress：配置正在恢复过程中 · The firewall service has not been found：防火墙服务未启动 · The configuration item doesn’t exist：配置项不存在 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_TIMERANGE_OP |
|
日志内容 |
Deleted time range $1. |
|
参数解释 |
$1：时间段名称 |
|
举例 |
Deleted time range tr. |
|
日志说明 |
用户进行了删除时间段的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The configuration item is in use：配置项正在被使用 · The configuration item doesn’t exist：配置项不存在 · The controller is not the active leader：该控制组件不是主Leader · The operation requires the administrator privilege：您需要管理员权限才能执行此操作 · Configuration recovery is in progress：配置正在恢复过程中 · The firewall service has not been found：防火墙服务未启动 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_FWOBJECTGROUP_OP |
|
日志内容 |
Created firewall object group $1. |
|
参数解释 |
$1：防火墙对象组的配置信息 |
|
举例 |
Created firewall object group ID: b52fff79-7bcf-4bff-9340-68c5f6c1c495 Tenant ID: ffffffff-0000-0000-0000-000000000001 Name: fw_objectgroup Description: firewall object group Type: IPv4. |
|
日志说明 |
用户进行了创建防火墙对象组的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid json format：无效的JSON格式 · The configuration item already exists：配置项已存在 · The tenant specified for the configuration item doesn't exist：配置项指定的租户不存在 · No tenant ID is specified：未指定租户ID · The controller is not the active leader：该控制组件不是主Leader · The operation requires the administrator privilege：您需要管理员权限才能执行此操作 · Configuration recovery is in progress：配置正在恢复过程中 · The firewall service has not been found：防火墙服务未启动 · No object group type is specified：没有指定对象组的类型 · The tenant name is read only：租户名称为只读字段 · The rules field is read only：规则为只读字段 · The objects field is read only：对象为只读字段 · The policies field is read only：策略为只读字段 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_FWOBJECTGROUP_OP |
|
日志内容 |
Updated firewall object group $1. |
|
参数解释 |
$1：防火墙对象组的配置信息 |
|
举例 |
Updated firewall object group ID: b52fff79-7bcf-4bff-9340-68c5f6c1c495 Tenant ID: ffffffff-0000-0000-0000-000000000001 Name: fw_objectgroup Description: firewall object group Type: IPv4 Audited: true. |
|
日志说明 |
用户进行了修改防火墙对象组的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid json format：无效的JSON格式 · The tenant ID is read only：租户ID为只读字段 · The object group type is read only：对象组类型为只读字段 · The tenant name is read only：租户名称为只读字段 · The ID is read only：ID为只读字段 · The object group name is read only：对象组名称为只读字段 · The controller is not the active leader：该控制组件不是主Leader · The operation requires the administrator privilege：您需要管理员权限才能执行此操作 · Configuration recovery is in progress：配置正在恢复过程中 · The firewall service has not been found：防火墙服务未启动 · The configuration item doesn't exist：配置项不存在 · The rules field is read only：规则为只读字段 · The objects field is read only：对象为只读字段 · The policies field is read only：策略为只读字段 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_FWOBJECTGROUP_OP |
|
日志内容 |
Deleted firewall object group $1. |
|
参数解释 |
$1：防火墙对象组名称 |
|
举例 |
Deleted firewall object group fw_objectgroup. |
|
日志说明 |
用户进行了删除防火墙对象组的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid UUID string: asd-+：指定的UUID“asd-+”无效 · The configuration item is in use：配置项正在被使用 · The configuration item doesn't exist：配置项不存在 · The controller is not the active leader：该控制组件不是主Leader · The operation requires the administrator privilege：您需要管理员权限才能执行此操作 · Configuration recovery is in progress：配置正在恢复过程中 · The firewall service has not been found：防火墙服务未启动 · Invalid json format：无效的JSON格式 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_FWOBJECT_OP |
|
日志内容 |
Created firewall object $1. |
|
参数解释 |
$1：防火墙对象的配置信息 |
|
举例 |
Created firewall object ID: b52fff79-7bcf-4bff-9340-68c5f6c1c495 Name: fw_object Sequence: 0 Protocol: TCP Source port: 100:200 Destination port: 300:400 Object group ID: 9a83d713-8e79-4ca8-a2e9-8df29daf5fd6. |
|
日志说明 |
用户进行了创建防火墙对象的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid json format：无效的JSON格式 · No object group ID is specified：未指定对象组ID · The object group specified for the configuration item doesn't exist：配置项指定的对象组不存在 · The configuration item already exists：配置项已存在 · The IPv4 address is available only when the object group type is IPv4：仅对象组类型为IPv4地址时支持配置IPv4地址 · The source port, destination port, and protocol are available only when the object group type is service：仅对象组类型为服务时支持配置源端口、目的端口和协议 · The name is required：名称不能为空 · The IPv4 address is required：IPv4地址不能为空 · The protocol is required：协议不能为空 · The number of configuration items exceeded the limit：配置项个数超出限制 · The controller is not the active leader：该控制组件不是主Leader · The operation requires the administrator privilege：您需要管理员权限才能执行此操作 · Configuration recovery is in progress：配置正在恢复过程中 · The firewall service has not been found：防火墙服务未启动 · The sequence number is read only：序号为只读字段 · Invalid protocol：无效的协议 · The IPv6 address is required：IPv6地址不能为空 · Invalid IPv6 address：无效的IPv6地址 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_FWOBJECT_OP |
|
日志内容 |
Updated firewall object $1. |
|
参数解释 |
$1：防火墙对象的配置信息 |
|
举例 |
Updated firewall object ID: b52fff79-7bcf-4bff-9340-68c5f6c1c495 Name: fw_object Sequence: 0 Protocol: TCP Source port: 100:200 Destination port: 300:400 Object group ID: 9a83d713-8e79-4ca8-a2e9-8df29daf5fd6. |
|
日志说明 |
用户进行了修改防火墙对象的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid json format：无效的JSON格式 · The ID is read only：ID为只读字段 · The object name is read only：对象名称为只读字段 · The sequence number is read only：序号为只读字段 · The object group ID is read only：对象组ID为只读字段 · The IPv4 address is available only when the object group type is IPv4：仅对象组类型为IPv4地址时支持配置IPv4地址 · The source port, destination port, and protocol are available only when the object group type is service：仅对象组类型为服务时支持配置源端口、目的端口和协议 · The controller is not the active leader：该控制组件不是主Leader · The operation requires the administrator privilege：您需要管理员权限才能执行此操作 · Configuration recovery is in progress：配置正在恢复过程中 · The firewall service has not been found：防火墙服务未启动 · The configuration item doesn't exist：配置项不存在 · Unknown error：未知错误 · The number of configuration items exceeded the limit：配置项个数超出限制 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_FWOBJECT_OP |
|
日志内容 |
Deleted firewall object $1. |
|
参数解释 |
$1：防火墙对象的名称 |
|
举例 |
Deleted firewall object fw_object. |
|
日志说明 |
用户进行了删除防火墙对象的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid UUID string: asd-+：指定的UUID“asd-+”无效 · The configuration item doesn't exist：配置项不存在 · The controller is not the active leader：该控制组件不是主Leader · The operation requires the administrator privilege：您需要管理员权限才能执行此操作 · Configuration recovery is in progress：配置正在恢复过程中 · The firewall service has not been found：防火墙服务未启动 · Invalid json format：无效的JSON格式 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_FWRULE_OP |
|
日志内容 |
Created firewall rule $1. |
|
参数解释 |
$1：防火墙规则配置信息 |
|
举例 |
Created firewall rule ID: b52fff79-7bcf-4bff-9340-68c5f6c1c495 Tenant ID: ffffffff-0000-0000-0000-000000000001 Name: fw_rule Description: firewall rule Shared: true Protocol: null IP version: IPv4 Source IP address: 22.2.2.2 Destination IP address: 11.1.1.1 Source port: 100:200 Destination port: 300:400 Position: null Action: INSPECT Enabled: true Time range ID: 9a83d713-8e79-4ca8-a2e9-8df29daf5fd6 App profile ID: 62214486-42a8-455a-ae6c-90853038fd0a IPS policy ID: 00000000-0000-0000-0000-000000000000 URL filter policy ID: 230f47be-63f4-4ae0-a488-b72a8d841b1f AV policy ID: 00000000-0000-0000-0000-000000000000. |
|
日志说明 |
用户进行了创建防火墙规则的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The configuration item already exists：配置项已存在 · The tenant specified for the configuration item doesn't exist：配置项指定的租户不存在 · The tenant IDs for the configuration items are different：配置项租户ID不匹配 · The time range specified for the rule doesn't exist：规则指定的时间段不存在 · The controller is not the active leader：该控制组件不是主Leader · The operation requires the administrator privilege：您需要管理员权限才能执行此操作 · Configuration recovery is in progress：配置正在恢复过程中 · The firewall service has not been found：防火墙服务未启动 · The match rules for virtual firewalls do not support the reject action：防火墙规则的动作不支持配置为reject · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_FWRULE_OP |
|
日志内容 |
Updated firewall rule $1. |
|
参数解释 |
$1：防火墙规则配置信息 |
|
举例 |
Updated firewall rule ID: b52fff79-7bcf-4bff-9340-68c5f6c1c495 Tenant ID: ffffffff-0000-0000-0000-000000000001 Name: fw_rule Description: firewall rule Shared: true Protocol: TCP IP version: IPv4 Source IP address: 22.2.2.2 Destination IP address: 11.1.1.1 Source port: 1222:1222 Destination port: 1333:1333 Position: null Action: INSPECT Enabled: true Time range ID: 9a83d713-8e79-4ca8-a2e9-8df29daf5fd6 App profile ID: 62214486-42a8-455a-ae6c-90853038fd0a IPS policy ID: 00000000-0000-0000-0000-000000000000 URL filter policy ID: 230f47be-63f4-4ae0-a488-b72a8d841b1f AV policy ID: 00000000-0000-0000-0000-000000000000. |
|
日志说明 |
用户进行了修改防火墙规则的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The time range specified for the rule doesn't exist：规则指定的时间段不存在 · The tenant IDs for the configuration items are different：配置项租户ID不匹配 · The controller is not the active leader：该控制组件不是主Leader · The operation requires the administrator privilege：您需要管理员权限才能执行此操作 · Configuration recovery is in progress：配置正在恢复过程中 · The firewall service has not been found：防火墙服务未启动 · The configuration item doesn’t exist：配置项不存在 · The match rules for virtual firewalls do not support the reject action：防火墙规则的动作不支持配置为reject · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_FWRULE_OP |
|
日志内容 |
Deleted firewall rule $1. |
|
参数解释 |
$1：防火墙规则名称 |
|
举例 |
Deleted firewall rule fw_rule. |
|
日志说明 |
用户进行了删除防火墙规则的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The configuration item is in use：配置项正在被使用 · The configuration item doesn’t exist：配置项不存在 · The controller is not the active leader：该控制组件不是主Leader · The operation requires the administrator privilege：您需要管理员权限才能执行此操作 · Configuration recovery is in progress：配置正在恢复过程中 · The firewall service has not been found：防火墙服务未启动 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_FWPOLICY_OP |
|
日志内容 |
Created firewall policy $1. |
|
参数解释 |
$1：防火墙策略配置信息 |
|
举例 |
Created firewall policy ID: 70dc3186-ac5b-4ba1-ac7f-7a27ef566efb Tenant ID: ffffffff-0000-0000-0000-000000000001 Name: fw_policy Description: firewall policy Shared: false Rule list: [1510d574-ac17-4078-9a60-719ac7740f84] Audited: true. |
|
日志说明 |
用户进行了创建防火墙策略的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The configuration item already exists：配置项已存在 · The tenant specified for the configuration item doesn't exist：配置项指定的租户不存在 · The tenant IDs for the configuration items are different：配置项租户ID不匹配 · The rule specified for the policy doesn't exist：策略指定的规则不存在 · The rule is already used by another policy：策略指定的规则已被其它策略引用 · The number of rules specified for the policy exceeded the limit：策略引用的规则数量超过上限 · The controller is not the active leader：该控制组件不是主Leader · The operation requires the administrator privilege：您需要管理员权限才能执行此操作 · Configuration recovery is in progress：配置正在恢复过程中 · The firewall service has not been found：防火墙服务未启动 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_FWPOLICY_OP |
|
日志内容 |
Updated firewall policy $1. |
|
参数解释 |
$1：防火墙策略配置信息 |
|
举例 |
Updated firewall policy ID: 70dc3186-ac5b-4ba1-ac7f-7a27ef566efb Tenant ID: ffffffff-0000-0000-0000-000000000001 Name: fw_policy Description: firewall policy Shared: false Rule list: [1510d574-ac17-4078-9a60-719ac7740f84] Audited: false. |
|
日志说明 |
用户进行了修改防火墙策略的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The tenant IDs for the configuration items are different：配置项租户ID不匹配 · The rule specified for the policy doesn't exist：策略指定的规则不存在 · The rule is already used by another policy：策略指定的规则已被其它策略引用 · The number of rules specified for the policy exceeded the limit：策略引用的规则数量超过上限 · The controller is not the active leader：该控制组件不是主Leader · The operation requires the administrator privilege：您需要管理员权限才能执行此操作 · Configuration recovery is in progress：配置正在恢复过程中 · The firewall service has not been found：防火墙服务未启动 · The configuration item doesn’t exist：配置项不存在 · You have no privilege to perform this operation：用户无权限执行此操作 · Total firewall rules reached the limit：防火墙规则总数达到上限 · Please specify a position for the rule：请指定规则的移动位置 · Maximum number of firewall rules already reached：防火墙规则已达到设备上限 · The specified rule is not bound to the security policy：指定的规则未被策略引用 |
|
关键字 |
DELETE_FWPOLICY_OP |
|
日志内容 |
Deleted firewall policy $1. |
|
参数解释 |
$1：防火墙策略名称 |
|
举例 |
Deleted firewall policy fw_policy. |
|
日志说明 |
用户进行了删除防火墙策略的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The configuration item is in use：配置项正在被使用 · The configuration item doesn’t exist：配置项不存在 · The controller is not the active leader：该控制组件不是主Leader · The operation requires the administrator privilege：您需要管理员权限才能执行此操作 · Configuration recovery is in progress：配置正在恢复过程中 · The firewall service has not been found：防火墙服务未启动 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_FW_OP |
|
日志内容 |
Created firewall $1. |
|
参数解释 |
$1：防火墙配置信息 |
|
举例 |
Created firewall ID: 6835896c-5152-4bed-a2ab-092c9980e2b8 Tenant ID : ffffffff-0000-0000-0000-000000000001 Name: fw Description: firewall Status: DOWN Shared: true Forward firewall policy ID: d233005f-22bd-4e2b-8ac0-bdef810f533a Backward firewall policy ID: c133005f-23bd-5a6b-7bb0-dbef710f524c Forward attack defense policy ID: d233005f-22bd-4e2b-8ac0-bdef810f533e Backward attack defense policy ID: d233005f-22bd-4e2b-8ac0-bdef810f533f Router ID: 78dce1d6-8ba5-4bb4-b909-0d83659c40b2. |
|
日志说明 |
用户进行了创建防火墙的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The configuration item already exists：配置项已存在 · The tenant specified for the configuration item doesn't exist：配置项指定的租户不存在 · The tenant IDs for the firewall and the specified forward firewall policy are different：防火墙和指定的正向防火墙策略的租户ID不匹配 · The tenant IDs for the firewall and the specified backward firewall policy are different：防火墙和指定的反向防火墙策略的租户ID不匹配 · The tenant IDs for the firewall and the specified vRouter are different：防火墙和指定的虚拟路由器的租户ID不匹配 · The tenant IDs for the firewall and the specified network resource are different：防火墙和指定的网络资源的租户ID不匹配 · The forward firewall policy specified for the firewall doesn't exist：防火墙指定的正向防火墙策略不存在 · The backward firewall policy specified for the firewall doesn't exist：防火墙指定的反向防火墙策略不存在 · The forward firewall policy is already used by another firewall：正向防火墙策略已被其他防火墙引用 · The backward firewall policy is already used by another firewall：反向防火墙策略已被其他防火墙引用 · The forward attack defense policy is already used by another firewall：正向攻击检测及防范策略已被其他防火墙引用 · The backward attack defense policy is already used by another firewall：反向攻击检测及防范策略已被其他防火墙引用 · The vRouter specified for the firewall doesn't exist：防火墙指定的虚拟路由器不存在 · The vRouter is already used by another firewall：虚拟路由器已被其他防火墙引用 · The type of the network resource specified for the firewall is not vFW：防火墙指定的网络资源不支持防火墙功能 · The network resource specified for the firewall doesn't exist：防火墙指定的网络资源不存在 · The number of firewalls bound to the resource exceeded the limit：单个资源绑定的防火墙个数超出限制 · The controller is not the active leader：该控制组件不是主Leader · The operation requires the administrator privilege：您需要管理员权限才能执行此操作 · Configuration recovery is in progress：配置正在恢复过程中 · The firewall service has not been found：防火墙服务未启动 · The specified resource is not associated with any resource access template or the associated resource access template is unavailable：指定的资源未关联资源接入模板或关联的资源接入模板不可用 · You have no privilege to perform this operation：用户无权限执行此操作 · Total firewall rules reached the limit：防火墙规则总数达到上限 · Make sure the access device in the resource access template and the service chain firewall use the same connection mode：服务链使用场景下，指定服务资源对应的资源接入模板的连接模式与防火墙的连接模式不匹配 · You cannot specify a connection mode for the gateway firewall：网关使用场景下，不允许指定连接模式 · The firewall is configured for service chaining, please specify a connection mode：服务链使用场景下，连接模式不能为空 · You cannot specify an outbound attack prevention policy for a one-arm firewall to be used as a service chain node：服务链使用场景单臂连接模式下，不允许配置出方向攻击防范策略 · You cannot specify an outbound security policy for a one-arm firewall to be used as a service chain node：服务链使用场景单臂连接模式下，不允许配置出方向安全策略 |
|
关键字 |
UPDATE_FW_OP |
|
日志内容 |
Updated firewall $1. |
|
参数解释 |
$1：防火墙配置信息 |
|
举例 |
Updated firewall ID: 6835896c-5152-4bed-a2ab-092c9980e2b8 Tenant ID: ffffffff-0000-0000-0000-000000000001 Name: fw Description: firewall Status: ACTIVE Shared: true Forward firewall policy ID: 572744ad-6bda-4617-aef2-78b58a068f93 Backward firewall policy ID: c133005f-23bd-5a6b-7bb0-dbef710f524c Forward attack defense policy ID: d233005f-22bd-4e2b-8ac0-bdef810f533e Backward attack defense policy ID: d233005f-22bd-4e2b-8ac0-bdef810f533f Mode: GATEWAY Router ID: 2bdbafbf-f899-42af-b2ce-e21122ad1d1b. |
|
日志说明 |
用户进行了修改防火墙的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The tenant IDs for the firewall and the specified forward firewall policy are different：防火墙和指定的正向防火墙策略的租户ID不匹配 · The tenant IDs for the firewall and the specified backward firewall policy are different：防火墙和指定的反向防火墙策略的租户ID不匹配 · The tenant IDs for the firewall and the specified vRouter are different：防火墙和指定的虚拟路由器的租户ID不匹配 · The tenant IDs for the firewall and the specified network resource are different：防火墙和指定的网络资源的租户ID不匹配 · The forward firewall policy specified for the firewall doesn't exist：防火墙指定的正向防火墙策略不存在 · The backward firewall policy specified for the firewall doesn't exist：防火墙指定的反向防火墙策略不存在 · The forward firewall policy is already used by another firewall：正向防火墙策略已被其他防火墙引用 · The backward firewall policy is already used by another firewall：反向防火墙策略已被其他防火墙引用 · The forward attack defense policy is already used by another firewall：正向攻击检测及防范策略已被其他防火墙引用 · The backward attack defense policy is already used by another firewall：反向攻击检测及防范策略已被其他防火墙引用 · The vRouter specified for the firewall doesn't exist：防火墙指定的虚拟路由器不存在 · The vRouter is already used by another firewall：虚拟路由器已被其他防火墙引用 · The type of the network resource specified for the firewall is not vFW：防火墙指定的网络资源不支持防火墙功能 · The network resource specified for the firewall doesn't exist：防火墙指定的网络资源不存在 · The number of firewalls bound to the resource exceeded the limit：单个资源绑定的防火墙个数超出限制 · The controller is not the active leader：该控制组件不是主Leader · The operation requires the administrator privilege：您需要管理员权限才能执行此操作 · Configuration deletion is in progress：配置正在删除 · Configuration recovery is in progress：配置正在恢复过程中 · The firewall service has not been found：防火墙服务未启动 · The configuration item doesn’t exist：配置项不存在 · The specified resource is not associated with any resource access template or the associated resource access template is unavailable：指定的资源未关联资源接入模板或关联的资源接入模板不可用 · You have no privilege to perform this operation：用户无权限执行此操作 · Total firewall rules reached the limit：防火墙规则总数达到上限 · You cannot change the connection mode of the firewall, because it has been bound to a service path：防火墙已被绑定，该连接模式不允许修改 · You cannot unbind the resource, because the firewall has been bound to a service chain or service path：该防火墙已被服务链或服务路径绑定，不允许解绑资源 · Make sure the access device in the resource access template and the service chain firewall use the same connection mode：服务链使用场景下，指定服务资源对应的资源接入模板的连接模式与防火墙的连接模式不匹配 · You cannot specify a connection mode for the gateway firewall：网关使用场景下，不允许指定连接模式 · The firewall is configured for service chaining, please specify a connection mode：服务链使用场景下，连接模式不能为空 · You cannot specify an outbound attack prevention policy for a one-arm firewall to be used as a service chain node：服务链使用场景单臂连接模式下，不允许配置出方向攻击防范策略 · You cannot specify an outbound security policy for a one-arm firewall to be used as a service chain node：服务链使用场景单臂连接模式下，不允许配置出方向安全策略 |
|
关键字 |
DELETE_FW_OP |
|
日志内容 |
Deleted firewall $1. |
|
参数解释 |
$1：防火墙名称 |
|
举例 |
Deleted firewall fw. |
|
日志说明 |
用户进行了删除防火墙的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The configuration item is in use：配置项正在被使用 · The configuration item doesn’t exist：配置项不存在 · The controller is not the active leader：该控制组件不是主Leader · The operation requires the administrator privilege：您需要管理员权限才能执行此操作 · Configuration deletion is in progress：配置正在删除 · Configuration recovery is in progress：配置正在恢复过程中 · The firewall service has not been found：防火墙服务未启动 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_IPSPOLICY_OP |
|
日志内容 |
Created IPS policy $1. |
|
参数解释 |
$1：IPS策略的配置信息 |
|
举例 |
Created IPS policy ID: 70dc3186-ac5b-4ba1-ac7f-7a27ef566efb Tenant ID: ffffffff-0000-0000-0000-000000000001 Name: IPS Description: ips policy. |
|
日志说明 |
用户进行了增加IPS策略的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · No signature library is uploaded：未加载特征库 · The tenant name is read only：租户名称为只读字段 · Invalid JSON format：无效的JSON串格式 · No tenant ID is specified：未指定租户ID · The specified tenant doesn't exist：配置项指定的租户不存在 · The configuration item already exists：配置项已存在 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · The service has not been found：服务未启动 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_IPSPOLICY_OP |
|
日志内容 |
Updated IPS policy $1. |
|
参数解释 |
$1：IPS策略的配置信息 |
|
举例 |
Updated IPS policy ID: 70dc3186-ac5b-4ba1-ac7f-7a27ef566efb Tenant ID: ffffffff-0000-0000-0000-000000000001 Name: IPS Description: ips policy. |
|
日志说明 |
用户进行了修改IPS策略的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The IPS policy ID can't be modified：IPS策略ID不允许修改 · The tenant ID can't be modified：租户ID不允许修改 · The tenant name is read only：租户名称为只读字段 · Invalid JSON format：无效的JSON串格式 · The configuration item doesn't exist：配置项不存在 · The predefined IPS policy can't be modified：预定义IPS策略不允许修改 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · The service has not been found：服务未启动 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_IPSPOLICY_OP |
|
日志内容 |
Deleted IPS policy $1. |
|
参数解释 |
$1：IPS策略的名称 |
|
举例 |
Deleted IPS policy IPS. |
|
日志说明 |
用户进行了删除IPS策略的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The configuration item doesn't exist：配置项不存在 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · The service has not been found：服务未启动 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_IPSTEMPLATE_OP |
|
日志内容 |
Created IPS template $1. |
|
参数解释 |
$1：IPS模板的配置信息 |
|
举例 |
Created IPS template ID: 70dc3186-ac5b-4ba1-ac7f-7a27ef566efb Tenant ID: ffffffff-0000-0000-0000-000000000001 Name: IPS Description: ips template. |
|
日志说明 |
用户进行了增加IPS模板的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · No signature library is uploaded：未加载特征库 · The tenant name is read only：租户名称为只读字段 · The template type is read only：IPS模板类型为只读字段 · Invalid JSON format：无效的JSON串格式 · No tenant ID is specified：未指定租户ID · The specified tenant doesn't exist：配置项指定的租户不存在 · The configuration item already exists：配置项已存在 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · The service has not been found：服务未启动 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_IPSTEMPLATE_OP |
|
日志内容 |
Updated IPS template $1. |
|
参数解释 |
$1：IPS模板的配置信息 |
|
举例 |
Updated IPS template ID: 70dc3186-ac5b-4ba1-ac7f-7a27ef566efb Tenant ID: ffffffff-0000-0000-0000-000000000001 Name: IPS Description: ips template. |
|
日志说明 |
用户进行了修改IPS模板的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The IPS template ID can't be modified：IPS模板ID不允许修改 · The tenant ID can't be modified：租户ID不允许修改 · The tenant name is read only：租户名称为只读字段 · The template type is read only：IPS模板类型为只读字段 · Invalid JSON format：无效的JSON串格式 · The configuration item doesn't exist：配置项不存在 · The predefined IPS template can't be modified：预定义IPS模板不允许修改 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · The service has not been found：服务未启动 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_IPSTEMPLATE_OP |
|
日志内容 |
Deleted IPS template $1. |
|
参数解释 |
$1：IPS模板的名称 |
|
举例 |
Deleted IPS template IPS. |
|
日志说明 |
用户进行了删除IPS模板的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The configuration item doesn't exist：配置项不存在 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · The service has not been found：服务未启动 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPLOAD_IPSSIGNATURE_OP |
|
日志内容 |
Uploaded IPS signature library $1 from local device. |
|
参数解释 |
$1：IPS特征库名称 |
|
举例 |
Uploaded IPS signature library V7-IPS-1.0.15.dat from local device. |
|
日志说明 |
用户进行了本地加载特征库的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The IPS signature library file is invalid or fails to parse the IPS signature library file：无效的IPS特征库文件或解析IPS特征库文件失败 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · The service has not been found：服务未启动 · Uploading aborted because of abnormal firewall service：防火墙服务异常导致上传中断 · Signature Library service has not been found：特征库服务未启动 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_AVPOLICY_OP |
|
日志内容 |
Created AV policy $1. |
|
参数解释 |
$1：防病毒策略的配置信息 |
|
举例 |
Created AV policy ID: 70dc3186-ac5b-4ba1-ac7f-7a27ef566efb Tenant ID: ffffffff-0000-0000-0000-000000000001 Name: AV Description: av policy. |
|
日志说明 |
用户进行了增加防病毒策略的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · No virus library is uploaded：未加载病毒库 · The tenant name is read only：租户名称为只读字段 · Invalid JSON format：无效的JSON串格式 · No tenant ID is specified：未指定租户ID · The specified tenant doesn't exist：配置项指定的租户不存在 · The configuration item already exists：配置项已存在 · The application library must be uploaded before the application exceptions are added：请先加载应用库，再增加应用例外 · The virus library must be uploaded before the virus exceptions are added：请先加载病毒库，再增加病毒例外 · The application exception is not included in the application library：应用例外不包含在应用库中 · The virus exception is not included in the virus library：病毒例外不包含在病毒库中 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · The service has not been found：服务未启动 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_AVPOLICY_OP |
|
日志内容 |
Updated AV policy $1. |
|
参数解释 |
$1：防病毒策略的配置信息 |
|
举例 |
Updated AV policy ID: 70dc3186-ac5b-4ba1-ac7f-7a27ef566efb Tenant ID: ffffffff-0000-0000-0000-000000000001 Name: AV Description: av policy. |
|
日志说明 |
用户进行了修改防病毒策略的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The antivirus policy ID can't be modified：防病毒策略ID不允许修改 · The tenant ID can't be modified：租户ID不允许修改 · The tenant name is read only：租户名称为只读字段 · Invalid JSON format：无效的JSON串格式 · The configuration item doesn't exist：配置项不存在 · The predefined antivirus policy can't be modified：预定义防病毒策略不允许修改 · The application library must be uploaded before the application exceptions are added：请先加载应用库，再增加应用例外 · The virus library must be uploaded before the virus exceptions are added：请先加载病毒库，再增加病毒例外 · The application exception is not included in the application library：应用例外不包含在应用库中 · The virus exception is not included in the virus library：病毒例外不包含在病毒库中 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · The service has not been found：服务未启动 · Invalid virus exceptions exist：存在已失效的病毒例外 · Invalid application exceptions exist：存在已失效的应用例外 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_AVPOLICY_OP |
|
日志内容 |
Deleted AV policy $1. |
|
参数解释 |
$1：防病毒策略的名称 |
|
举例 |
Deleted AV policy AV. |
|
日志说明 |
用户进行了删除防病毒策略的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The configuration item doesn't exist：配置项不存在 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · The service has not been found：服务未启动 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_AVTEMPLATE_OP |
|
日志内容 |
Created AV template $1. |
|
参数解释 |
$1：防病毒模板的配置信息 |
|
举例 |
Created AV template ID: 70dc3186-ac5b-4ba1-ac7f-7a27ef566efb Tenant ID: ffffffff-0000-0000-0000-000000000001 Name: AV Description: av template. |
|
日志说明 |
用户进行了增加防病毒模板的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · No virus library is uploaded：未加载病毒库 · The tenant name is read only：租户名称为只读字段 · The antivirus template type is read only：防病毒模板类型为只读字段 · Invalid JSON format：无效的JSON串格式 · No tenant ID is specified：未指定租户ID · The specified tenant doesn't exist：配置项指定的租户不存在 · The configuration item already exists：配置项已存在 · The application library must be uploaded before the application exceptions are added：请先加载应用库，再增加应用例外 · The virus library must be uploaded before the virus exceptions are added：请先加载病毒库，再增加病毒例外 · The application exception is not included in the application library：应用例外不包含在应用库中 · The virus exception is not included in the virus library：病毒例外不包含在病毒库中 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · The service has not been found：服务未启动 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_AVTEMPLATE_OP |
|
日志内容 |
Updated AV template $1. |
|
参数解释 |
$1：防病毒模板的配置信息 |
|
举例 |
Updated AV template ID: 70dc3186-ac5b-4ba1-ac7f-7a27ef566efb Tenant ID: ffffffff-0000-0000-0000-000000000001 Name: AV Description: av template. |
|
日志说明 |
用户进行了修改防病毒模板的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The antivirus template ID can't be modified：防病毒模板的ID不允许修改 · The tenant ID can't be modified：租户ID不允许修改 · The tenant name is read only：租户名称为只读字段 · The antivirus template type is read only：防病毒模板类型为只读字段 · Invalid JSON format：无效的JSON串格式 · The configuration item doesn't exist：配置项不存在 · The predefined antivirus template can't be modified：预定义防病毒模板不允许修改 · The application library must be uploaded before the application exceptions are added：请先加载应用库，再增加应用例外 · The virus library must be uploaded before the virus exceptions are added：请先加载病毒库，再增加病毒例外 · The application exception is not included in the application library：应用例外不包含在应用库中 · The virus exception is not included in the virus library：病毒例外不包含在病毒库中 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · The service has not been found：服务未启动 · Invalid virus exceptions exist：存在已失效的病毒例外 · Invalid application exceptions exist：存在已失效的应用例外 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_AVTEMPLATE_OP |
|
日志内容 |
Deleted AV template $1. |
|
参数解释 |
$1：防病毒模板的名称 |
|
举例 |
Deleted AV template AV. |
|
日志说明 |
用户进行了删除防病毒模板的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The configuration item doesn't exist：配置项不存在 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · The service has not been found：服务未启动 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPLOAD_VIRUSLIBRARY_OP |
|
日志内容 |
Uploaded virus library $1 from local device. |
|
参数解释 |
$1：病毒库的名称 |
|
举例 |
Uploaded virus library V7-AV-1.0.15.dat from local device. |
|
日志说明 |
用户进行了本地加载病毒库的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The virus library file is invalid or fails to parse the virus library file：无效的病毒库文件或解析病毒库文件失败 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · The service has not been found：服务未启动 · Uploading aborted because of abnormal firewall service：防火墙服务异常导致上传中断 · Signature Library service has not been found：特征库服务未启动 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
|
UPLOAD_APPLIBRARY_OP |
|
日志内容 |
Uploaded application library $1 from local device. |
|
参数解释 |
$1：应用库的名称 |
|
举例 |
Uploaded application library V7-APP-1.0.41.dat from local device. |
|
日志说明 |
用户进行了本地加载应用库的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The application library file is invalid or fails to parse the application library file：无效的应用库文件或解析应用库文件失败 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · The service has not been found：服务未启动 · Uploading aborted because of abnormal firewall service：防火墙服务异常导致上传中断 · Signature Library service has not been found：特征库服务未启动 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_ATKDEFPOLICY_OP |
|
日志内容 |
Created attack defense policy $1. |
|
参数解释 |
$1：攻击检测及防范策略的配置信息 |
|
举例 |
Created attack defense policy ID: 70dc3186-ac5b-4ba1-ac7f-7a27ef566efb Name: fw_policy Tenant ID: ffffffff-0000-0000-0000-000000000001 Description: policy |
|
日志说明 |
用户进行了创建攻击检测及防范策略的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · No tenant ID is specified：未指定租户ID · No policy name is specified：未指定策略名称 · Invalid JSON format：无效的JSON串格式 · The value of the threshold must be an integer in the range of 1 to 1000000：触发阈值的取值范围为1～1000000的整数 · The configuration item already exists：配置项已存在 · The specified tenant doesn't exist：配置项指定的租户不存在 · The controller is not the active leader：该控制组件不是主Leader · The large ICMP packet length is an integer in the range of 28 to 65534：Large ICMP的取值范围为28～65534的整数 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_ATKDEFPOLICY_OP |
|
日志内容 |
Updated attack defense policy $1. |
|
参数解释 |
$1：攻击检测及防范策略的配置信息 |
|
举例 |
Updated attack defense policy ID: 5f206f6d-e400-4f25-896f-791678132664 Name: policy Tenant ID: ffffffff-0000-0000-0000-000000000001 Description: ABCDEFG. |
|
日志说明 |
用户进行了修改攻击检测及防范策略的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON串格式 · The value of the threshold must be an integer in the range of 1 to 1000000：触发阈值的取值范围为1～1000000的整数 · The controller is not the active leader：该控制组件不是主Leader · The configuration item doesn't exist：配置项不存在 · The large ICMP packet length is an integer in the range of 28 to 65534：Large ICMP的取值范围为28～65534的整数 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_ATKDEFPOLICY_OP |
|
日志内容 |
Deleted attack defense policy $1. |
|
参数解释 |
$1：攻击检测及防范策略的名称 |
|
举例 |
Deleted attack defense policy atk_policy. |
|
日志说明 |
用户进行了删除攻击检测及防范策略的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The configuration item is in use：配置项正在被使用 · The configuration item doesn’t exist：配置项不存在 · The controller is not the active leader：该控制组件不是主Leader · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_URL_CATEGORY_OP |
|
日志内容 |
Created URL filter category $1. |
|
参数解释 |
$1：URL过滤分类的配置信息 |
|
举例 |
Created URL filter category ID: 0ad7e32e-f163-4fb9-b272-f9e2977d40be Name: category1 Tenant ID: ffffffff-0000-0000-0000-000000000001 Tenant name: default Severity: 1000 Description: category1 URL filter rules: []. |
|
日志说明 |
用户进行了创建URL过滤分类的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The configuration item already exists：配置项已存在 · The tenant specified for the configuration item doesn't exist：配置项指定的租户不存在 · The controller is not the active leader：该控制组件不是主Leader · Invalid JSON format：无效的JSON串格式 · The URL filter categories created for the sane tenant must have different severity levels：同一租户下的不同URL过滤分类的严重级别不能相同 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_URL_CATEGORY_OP |
|
日志内容 |
Updated URL filter category $1. |
|
参数解释 |
$1：URL过滤分类的配置信息 |
|
举例 |
Updated URL filter category ID: 0ad7e32e-f163-4fb9-b272-f9e2977d40be Name: category1 Tenant ID: ffffffff-0000-0000-0000-000000000001 Tenant name: default Severity: 1000 Description: category1 URL filter rules: []. |
|
日志说明 |
用户进行了修改URL过滤分类的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · The configuration item doesn’t exist：配置项不存在 · Invalid JSON format：无效的JSON串格式 · The URL filter categories created for the sane tenant must have different severity levels：同一租户下的不同URL过滤分类的严重级别不能相同 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_URL_CATEGORY_OP |
|
日志内容 |
Deleted URL filter category $1. |
|
参数解释 |
$1：URL过滤分类名称 |
|
举例 |
Deleted URL filter category category1. |
|
日志说明 |
用户进行了删除URL过滤分类的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The configuration item is in use：配置项正在被使用 · The configuration item doesn’t exist：配置项不存在 · The controller is not the active leader：该控制组件不是主Leader · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_URL_RULE_OP |
|
日志内容 |
Created URL filter rule $1. |
|
参数解释 |
$1：URL过滤规则的配置信息 |
|
举例 |
Created URL filter rule ID: 954a1680-fd27-4cc1-b5ec-8f530c81f57a Category ID: f600c3fc-3c53-4b31-bc30-bfdd7177660b Rule ID: 1 Host filter type: TEXT Host name: 1234 URI filter type: REGEX URI: 12345 |
|
日志说明 |
用户进行了创建URL过滤规则的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The configuration item already exists：配置项已存在 · The tenant specified for the configuration item doesn't exist：配置项指定的租户不存在 · The controller is not the active leader：该控制组件不是主Leader · Invalid JSON format：无效的JSON串格式 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_URL_RULE_OP |
|
日志内容 |
Updated URL filter rule $1. |
|
参数解释 |
$1：URL过滤规则的配置信息 |
|
举例 |
Updated URL filter rule ID: 954a1680-fd27-4cc1-b5ec-8f530c81f57a Category ID: f600c3fc-3c53-4b31-bc30-bfdd7177660b Rule ID: 1 Host filter type: TEXT Host name: 1234 URI filter type: REGEX URI: 12345.. |
|
日志说明 |
用户进行了修改URL过滤规则的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · The configuration item doesn’t exist：配置项不存在 · Invalid JSON format：无效的JSON串格式 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_URL_RULE_OP |
|
日志内容 |
Deleted URL filter rule $1. |
|
参数解释 |
$1：URL过滤规则的ID |
|
举例 |
Deleted URL filter rule 954a1680-fd27-4cc1-b5ec-8f530c81f57a. |
|
日志说明 |
用户进行了删除URL过滤规则的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The configuration item is in use：配置项正在被使用 · The configuration item doesn’t exist：配置项不存在 · The controller is not the active leader：该控制组件不是主Leader · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_URL_POLICY_OP |
|
日志内容 |
Created URL filter policy $1. |
|
参数解释 |
$1：URL过滤策略的配置信息 |
|
举例 |
Created URL filter policy ID: e9c2d8b7-1a6f-49db-b36a-b86ed8ca3a04 Name: policy1 Tenant ID: 28a270bd-fd71-455d-b337-6281f9175bd9 Tenant name: ht Description: null |
|
日志说明 |
用户进行了创建URL过滤策略的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The configuration item already exists：配置项已存在 · The tenant specified for the configuration item doesn't exist：配置项指定的租户不存在 · The selected URL filter categories contain invalid categories：已选分类中存在无效分类 · The controller is not the active leader：该控制组件不是主Leader · Invalid JSON format：无效的JSON串格式 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_URL_POLICY_OP |
|
日志内容 |
Updated URL filter policy $1. |
|
参数解释 |
$1：URL过滤策略的配置信息 |
|
举例 |
Updated URL filter policy ID: e9c2d8b7-1a6f-49db-b36a-b86ed8ca3a04 Name: policy1 Tenant ID: 28a270bd-fd71-455d-b337-6281f9175bd9 Tenant name: ht Description: null |
|
日志说明 |
用户进行了修改URL过滤策略的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · The configuration item doesn’t exist：配置项不存在 · The selected URL filter categories contain invalid categories：已选分类中存在无效分类 · Invalid JSON format：无效的JSON串格式 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_URL_POLICY_OP |
|
日志内容 |
Deleted URL filter policy $1. |
|
参数解释 |
$1：URL过滤策略名称 |
|
举例 |
Deleted URL filter policy policy1. |
|
日志说明 |
用户进行了删除URL过滤策略的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The configuration item is in use：配置项正在被使用 · The configuration item doesn’t exist：配置项不存在 · The controller is not the active leader：该控制组件不是主Leader · You have no privilege to perform this operation：用户无权限执行此操作 |
本节介绍全局配置输出的操作日志信息。
|
关键字 |
UPDATE_GLOBAL_OP |
|
日志内容 |
Updated global configuration: $1. |
|
参数解释 |
$1：全局配置信息 |
|
举例 |
Updated global configuration: vxlanPoolId: [4cc5eb74-8495-4bf6-bbb7-b631ce0695fc]. |
|
日志说明 |
用户进行了修改全局配置的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置正在恢复中 · The controller is not the active leader：该控制组件不是主Leader · The VXLAN pool doesn't exists：指定的VXLAN池不存在 · You have no privilege to perform this operation：用户无权限执行此操作 |
本节介绍IDM模块输出的操作日志信息。
|
关键字 |
ADD_NETCONF_TEMPLATE_OP |
|
日志内容 |
Added a NETCONF template: id: $1 templateName: $2 vender: $3 description:$4 createType: $5 netConfProtocolList: [ { id: $6 type: $7, netConfInfo: $8 tempId: $9 } ]. |
|
参数解释 |
$1：NETCONF模板ID $2：NETCONF模板名称 $3：设备厂商的名称 $4：协议模板描述 $5：创建类型，其中0代表页面增加的模版，1代表普通创建，为自动化模版使用，2代表为设备单独创建 $6：NETCONF协议ID $7：NETCONF协议模板的类型，其中0代表HTTP，1代表HTTPS。目前只支持HTTPS $8：NETCONF协议信息 $9：模板ID |
|
举例 |
Added a NETCONF template: id: [1] templateName: [TEST_NETCONF] vender: [1] description: [] createType: [0] netConfProtocolList: [ { id: [1] type: [1] netConfInfo:[ type=1%%accessType=SOAP/HTTPS%%protocol=HTTPS%% port=832%%rootPath=/soap/netconf/%%userName=adg%% password=cbjaLmV3o4lxV+CzQPCumA==%%] tempId: [1] } ] |
|
日志说明 |
用户进行了添加NETCONF模板的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The NETCONF template parameters cannot be empty：NETCONF模板参数不允许为空 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · The NETCONF template name is required：NETCONF模板的名称不允许为空 · The NETCONF template name already exists：NETCONF模板名称已存在 · The value of the protocol type field can only be 1：协议类型值只能为1 · The protocol type is required：协议类型不允许为空 · The NETCONF template protocol type must be the same as that in the NETCONF information：NETCONF模板的协议类型与相对应的协议信息的协议类型保持一致 · The NETCONF information must contain a username and a password：NETCONF信息字段中必须存在用户名和密码 · The NETCONF information is required：NETCONF信息字段不允许为空 · The value of the NETCONFtemplate ID is an integer in the range of 1 to 2147483647：NETCONF模板ID的取值范围为1～2147483647的整数 · The value of the protocol ID is an integer in the range of 1 to 2147483647：协议ID的取值范围为1～2147483647的整数 · A maximum of one protocol is supported in the NETCONF protocol list：NETCONF协议列表中仅支持一组协议配置 · The value of the creation type field can only be 0, 1, or 2：创建类型字段值仅支持0、1和2 · The vender is required：设备厂商名不允许为空 · The value of the vender is an integer in the range of 1 to 2147483647：设备厂商名字的取值范围为1～2147483647的整数 · The netConfProtocolList cannot be null：NETCONF协议列表字段为必填字段 · Failed to synchronize information from the primary controller to the backup controller：主控制组件向备控制组件同步信息失败 · The netConfInfo field can contain up to 255 characters：NETCONF协议信息字段最长255个字符 · The description field can contain up to 255 characters：NETCONF模板描述信息字段最长255个字符 · The NETCONF template name field can contain up to 255 characters：NETCONF模板名称最长255个字符 · Unknown system error：系统未知错误 · Invalid JSON format：无效的JSON格式 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_NETCONF_TEMPLATE_OP |
|
日志内容 |
Update a NETCONF template $1: id: $2 templateName: $3 vender: $4 description:$5 createType: $6 netConfProtocolList: [ { id: $7 , type: $8, netConfInfo: $9, tempId: $10 } ] |
|
参数解释 |
$1：待修改的模板ID $2：NETCONF模板ID $3：NETCONF模板名称 $4：设备厂商的名称 $5：协议模板描述 $6：创建类型，其中0代表页面增加的模版，1代表普通创建，为自动化模版使用，2代表为设备单独创建 $7：NETCONF协议ID $8：NETCONF协议模板的类型，其中0代表HTTP，1代表HTTPS，目前只支持HTTPS $9：NETCONF协议信息 $10：模板ID |
|
举例 |
Updated NETCONF template 1: id: [1], templateName: [TEST_NETCONF], vender: [1] description: [] createType: [0] netConfProtocolList: [ { id: [1] type: [1] netConfInfo:[ type=1%%accessType=SOAP/HTTPS%%protocol=HTTPS%% port=832%%rootPath=/soap/netconf/%%userName=adg%% password=cbjaLmV3o4lxV+CzQPCumA==%%] tempId: [1] } ] |
|
日志说明 |
用户进行了修改NETCONF模板的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The NETCONF template parameters cannot be empty：NETCONF模板参数不允许为空 · The controller was not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · The value of the protocol type field can only be 1：协议类型值只能为1 · The protocol type is required：协议类型不允许为空 · The NETCONF template protocol type must be the same as that in the NETCONF information：NETCONF模板的协议类型与相对应的协议信息的协议类型保持一致 · The NETCONF information must contain a username and a password：NETCONF信息字段中必须存在用户名和密码 · The NETCONF information is required：NETCONF信息字段不允许为空 · The value of the NETCONF template ID is an integer in the range of 1 to 2147483647：NETCONF模板ID的取值范围为1～2147483647的整数 · The value of the protocol ID is an integer in the range of 1 to 2147483647：协议ID的取值范围为1～2147483647的整数 · A maximum of one protocol is supported in the NETCONF protocol list：NETCONF协议列表中仅支持一组协议配置 · The value of the creation type field can only be 0, 1, or 2：创建类型字段值仅支持0、1和2 · The vender is required：设备厂商名不允许为空 · The value of the vender is an integer in the range of 1 to 2147483647：设备厂商名字的取值范围为1～2147483647的整数 · Failed to synchronize information from the primary controller to the backup controller：主控制组件向备控制组件同步信息失败 · Unknown system error：系统未知错误 · The NETCONF template ID must be the same as that in the NETCONF information：NETCONF模板的ID与相对应的协议信息的tempId必须一致 · The protocol ID does not exist：NETCONF协议ID不存在 · The netConfProtocolList cannot be null：NETCONF协议列表字段为必填字段 · The protocol ID cannot be null：NETCONF协议ID不允许为空 · Invalid JSON format：无效的JSON格式 · The netConfInfo field can contain up to 255 characters：NETCONF协议信息字段最长255个字符 · The description field can contain up to 255 characters：NETCONF模板描述信息字段最长255个字符 · The NETCONF template name field can contain up to 255 characters：NETCONF模板名称最长255个字符 · The NETCONF template ID is required in NETCONF protocol list：NETCONF协议列表中的模板ID不能为空 · The NETCONF template ID does not exist：NETCONF模板ID不存在 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_NETCONF_TEMPLATE_OP |
|
日志内容 |
Deleted NETCONF template: $1. |
|
参数解释 |
$1：需要删除的NETCONF模板ID |
|
举例 |
Deleted NETCONF template: 1. |
|
日志说明 |
用户进行了删除NETCONF模板的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller was not the active leader ：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Failed to synchronize information from the primary controller to the backup controller：主控制组件向备控制组件同步信息失败 · Unknown system error：系统未知错误 · The value of the NETCONF template ID is an integer in the range of 1 to 2147483647：NETCONF模板ID的取值范围为1～2147483647的整数 · The NETCONF template ID does not exist：NETCONF模板ID不存在 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
ADD_CONF_FILE_OP |
|
日志内容 |
Added a configuration file: confFileName:$1 confFileType:$2 cfgFileParent:$3 appliedDevices:$4 |
|
参数解释 |
$1：配置文件名称 $2：配置文件类型，取值包括-1、1、2，其中-1表示文件夹类型；1表示配置文件类型；2表示配置片段类型 $3：文件所在的文件夹ID $4：配置文件适配的设备ID |
|
举例 |
Added a configuration file: confFileName:[test_json_4.cfg] confFileType:[-1] cfgFileParent:[-1] appliedDevices:[1] |
|
日志说明 |
用户进行了增加配置文件的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Failed to add the configuration file. The values of the configuration file type and folder ID fields can contain only digits：增加配置文件失败，配置文件类型和文件夹ID仅支持数字 · The configuration file does not folder：不是文件夹类型 · Failed to synchronize information from the primary controller to the backup controller：主控制组件向备控制组件同步信息失败 · Configuration recovery is in progress：配置正在恢复过程中 · The configuration file name is required：配置文件名称不允许为空 · The configuration file type is required：配置文件类型不允许为空 · The value of the configuration file type can only be –1,1 or 2：配置文件类型仅支持-1、1、2 · The confFileName field can contain up to 255 characters：confFileName字段最长255个字符 · The confFilePath field can contain up to 255 characters：confFilePath字段最长255个字符 · The appliedDevices field can contain up to 255 characters：appliedDevices字段最长255个字符 · The configuration file contents are required：配置文件内容不允许为空 · The configuration file folder is required：配置文件夹不允许为空 · The configuration file folder does not exist：配置文件夹不存在 · The configuration file name already exists：配置文件名称已存在 · Unknown system error：系统未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
MODIFIED_CONF_FILE_OP |
|
日志内容 |
Modified a configuration file: confFileName: $1 confFileType: $2 cfgFileParent: $3 appliedDevices: $4 |
|
参数解释 |
$1：配置文件名称 $2：配置文件类型，取值包括-1、1、2，其中-1表示文件夹类型；1表示配置文件类型；2表示配置片段类型 $3：文件所在的文件夹ID $4：配置文件适配的设备ID |
|
举例 |
Modified a configuration file: confFileName: [test_json_4.cfg] confFileType: [-1] cfgFileParent: [-1] appliedDevices: [1] |
|
日志说明 |
用户进行了修改配置文件的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Failed to synchronize information from the primary controller to the backup controller：主控制组件向备控制组件同步信息失败 · Unknown system error：系统未知错误 · The configuration file name already exists：配置文件名称已存在 · The configuration file does not exist：文件不存在 · The parameters are empty：参数为空 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_CONF_FILE_OP |
|
日志内容 |
Deleted configuration file $1. |
|
参数解释 |
$1：配置文件ID |
|
举例 |
Deleted configuration file 1. |
|
日志说明 |
用户进行了删除配置文件的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Failed to synchronize information from the primary controller to the backup controller：主控制组件向备控制组件同步信息失败 · The configuration file ID is invalid：配置文件ID不合法 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · The configuration file does not exist：文件不存在 · Unknown system error：系统未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DEPLOY_CONF_SNIPPET_OP |
|
日志内容 |
Deployed configuration snippets to the device:$1 |
|
参数解释 |
$1：下发到设备的配置片段相关信息 |
|
举例 |
Deployed configuration snippets to the device: confFileId:[3] deviceIds:[1] confFilePath:[/] confFileName:[test_json_4.cfg] |
|
日志说明 |
用户进行了下发配置片段的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · The configuration file ID is invalid：配置文件ID不合法 · The configuration file folder does not exist：配置文件夹不存在 · The file must be a configuration snippet file：该文件类型只允许为配置片段类型 · When the confFileId is empty, the confFilePath and confFileName fields are required：confFileId为空时，confFilePath和confFileName不允许为空 · The configuration snippet does not exist：配置片段不存在 · Deployment failed：下发配置片段失败 · Partially succeeded：下发配置片段部分成功 · Invalid device ID：设备ID不合法 · The device ID does not exist：设备ID不存在 · The request is invalid：传入的JSON串错误 · The configuration file name is required：文件名不允许为空 · The parameters are empty：参数为空 · Unknown system error：系统未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DEPLOY_COMMAND_OP |
|
日志内容 |
Deployed commands to the device:$1 |
|
参数解释 |
$1：下发命令行到设备并执行相关信息 |
|
举例 |
Deployed commands to the device: deviceId:[2] |
|
日志说明 |
用户进行了下发并执行命令行的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · The request is invalid：传入的JSON串错误 · The parameters are empty：参数为空 · Invalid device ID：设备ID不合法 · The device ID does not exist：设备ID不存在 · The configuration list that the controller deployed to the device is empty：控制组件向设备下发的配置列表为空 · Unknown system error：系统未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
START_DEVICE_AUTO_CFG_OP |
|
日志内容 |
Started the automatic configuration process for device $1. |
|
参数解释 |
$1：设备ID |
|
举例 |
Started the automatic configuration process for device 1011. |
|
日志说明 |
开启设备的自动化配置进程 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · Service not started：服务未启动 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Invalid device ID：无效的设备ID · The asset information does not exist：资产信息不存在 · The device IP corresponding to the device ID does not exist：设备ID对应的设备IP不存在 · The configuration list that the controller deployed to the device is empty：控制组件向设备下发的配置列表为空 · The IP address of the master node is invalid：Master节点的IP地址无效 · Internal error：内部错误 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
STOP_DEVICE_AUTO_CFG_OP |
|
日志内容 |
Stopped the automatic configuration process for device $1. |
|
参数解释 |
$1：设备ID |
|
举例 |
Stopped the automatic configuration process for device 1011. |
|
日志说明 |
停止设备的自动化配置进程 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · Service not started：服务未启动 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Invalid device ID：无效的设备ID · The asset information does not exist：资产信息不存在 · The device IP corresponding to the device ID does not exist：设备ID对应的设备IP不存在 · The configuration list that the controller deployed to the device is empty：控制组件向设备下发的配置列表为空 · The IP address of the master node is invalid：Master节点的IP地址无效 · Internal error：内部错误 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
ADD_SNMP_TEMPLATE_OP |
|
日志内容 |
Added an SNMP template:$1 |
|
参数解释 |
$1：SNMP协议模板信息 |
|
举例 |
Added an SNMP template: |
|
日志说明 |
用户进行了创建SNMP协议模板的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid json format：无效的JSON格式 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · The SNMP template name already exists： SNMP协议模板的名称已存在 · The SNMP template ID is invalid：SNMP协议模板的ID不合法 · The SNMP template name cannot exceed 64 characters： SNMP协议模板的名称不允许超过64个字符 · The value of the version field can only be 2：SNMP协议模板的版本号仅支持数字2 · The value of the timeout is an integer in the range of 1 to 60 (seconds)：超时时间取值范围为1～60的整数 · The value of the retries is an integer in the range of 1 to 20：重试次数取值范围为1～20的整数 · The timeout is required：超时时间字段不允许为空 · The retries is required：重试次数字段不允许为空 · The value of the isAutodiscoverTemp field can only be 1 or 2：是否自动发现字段仅支持数字1和2 · The value of the accessType field can only be 1：模板类型仅支持数字1 · The value of the type field can only be 0 or 1：type字段仅支持数字0和1 · Failed to synchronize information from the primary controller to the backup controller：主控制组件向备控制组件同步信息失败 · Unknown error：未知错误 · The snmpPort value is an integer in the range of 1 to 65535：SNMP端口号的取值范围为1～65535的整数 · The roCommunity field can contain up to 96 characters：只读团体名字段最长96个字符 · The rwCommunity field can contain up to 96 characters：读写团体名字段最长96个字符 · The creator field can contain up to 255 characters：创建者字段最长255个字符 · The operatorGroupStr field can contain up to 255 characters：操作组名称字段最长255个字符 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_SNMP_TEMPLATE_OP |
|
日志内容 |
Deleted SNMP template: $1. |
|
参数解释 |
$1：SNMP协议模板ID |
|
举例 |
Deleted SNMP template: 2. |
|
日志说明 |
用户进行了删除SNMP协议模板的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · The SNMP template ID is invalid：SNMP协议模板ID不合法 · The SNMP template ID does not exist：SNMP协议模板ID不存在 · The default template cannot be deleted：默认模板不允许删除 · Failed to synchronize information from the primary controller to the backup controller：主控制组件向备控制组件同步信息失败 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_SNMP_TEMPLATE_OP |
|
日志内容 |
Updated SNMP template $1:$2 |
|
参数解释 |
$1：SNMP协议模板的ID $2：SNMP协议模板的相关信息 |
|
举例 |
Updated SNMP template 2: name: [test] |
|
日志说明 |
用户进行了修改SNMP协议模板的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · The SNMP template name already exists：SNMP协议模板的名称已存在 · The SNMP template ID is invalid：SNMP协议模板的ID不合法 · The SNMP template name cannot exceed 64 characters：SNMP协议模板的名称不允许超过64个字符 · The value of the version field can only be 2：SNMP协议模板的版本号仅支持数字2 · The value of the timeout is an integer in the range of 1 to 60 (seconds)：超时时间取值范围为1～60的整数 · The value of the retries is an integer in the range of 1 to 20：重试次数取值范围为1～20的整数 · The timeout is required：超时时间字段不允许为空 · The number is required：重试次数字段不允许为空 · The value of the isAutodiscoverTemp field can only be 1 or 2：是否自动发现字段仅支持数字1和2 · The value of the accessType field can only be 1：模板类型仅支持数字1 · The value of the type field can only be 0 or 1：type字段仅支持数字0和1 · Failed to synchronize information from the primary controller to the backup controller：主控制组件向备控制组件同步信息失败 · Unknown error：未知错误 · The SNMP template ID does not exist：指定的模板ID不存在 · The default template name cannot be modified：默认模板名称不允许修改 · The snmpPort value is an integer in the range of 1 to 65535：SNMP端口号的取值范围为1～65535的整数 · The roCommunity field can contain up to 96 characters：只读团体名字段最长96个字符 · The rwCommunity field can contain up to 96 characters：读写团体名字段最长96个字符 · The creator field can contain up to 255 characters：创建者字段最长255个字符 · The operatorGroupStr field can contain up to 255 characters：操作组名称字段最长255个字符 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
ADD_AGGRE_INTERFACE_OP |
|
日志内容 |
Added an aggregate interface:$1 |
|
参数解释 |
$1：聚合口配置信息 |
|
举例 |
Added an aggregate interface: deviceId: [1] aggregateInterface: [Bridge-Aggregation11] physicalInterface: [WGE1/0/38,WGE1/0/39] |
|
日志说明 |
用户进行了创建聚合口的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · The device ID doesn't exist：指定的网元设备ID不存在 · The aggregate interface ID is invalid：无效的聚合接口编号 · The group index cannot be a reserved index：指定的聚合组编号不能属于聚合组预留编号范围内 · The group index has been used by another group：指定的聚合组编号已被其他聚合组使用 · The aggregation group member already exists on the device：该聚合组成员在指定的网元上已存在 · The device ID is required：指定的网元设备ID不允许为空 · Invalid deviceId value：无效的网元设备ID · aggregateInterface is empty：聚合口名称不允许为空 · Invalid aggregateInterface value：聚合口名称不合法 · physicalInterface is empty：物理口列表名称不允许为空 · Invalid physicalInterface value：物理口列表名称不合法 · Unknown error：未知错误 · The request timed out：Requst请求超出时间 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_AGGRE_INTERFACE_OP |
|
日志内容 |
Updated aggregate interface: $1 |
|
参数解释 |
$1：聚合口配置信息 |
|
举例 |
Updated aggregate interface: deviceId: [1] interfaces: [ Bridge-Aggregation6, Bridge-Aggregation7] model: [1] |
|
日志说明 |
配置聚合组工作模式或配置聚合组成员 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · The aggregation group doesn’t exist：该聚合组不存在 · The aggregation group member doesn’t exist：该聚合组成员不存在 · Unknown error：未知错误 · The value of the interfaces field is invalid：无效的接口名称列表 · Invalid deviceId value：无效的网元设备ID · The value of the model field must be 1, 2, or 3：聚合组工作模式仅支持数字1、2、3 · The device ID doesn't exist：指定的网元设备ID不存在 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CONFIG_AGGRE_INTERFACE_OP |
|
日志内容 |
Configured aggregate interfaces:$1 |
|
参数解释 |
$1：聚合口配置信息 |
|
举例 |
Configured aggregate interfaces: deviceId: [2] model: [1] aggregate: [Bridge-Aggregation1010,Bridge-Aggregation1012|Ten-GigabitEthernet2/2/0/15,Bridge-Aggregation1011|Ten-GigabitEthernet2/2/0/10|Ten-GigabitEthernet2/2/0/11|Ten-GigabitEthernet2/2/0/9|Ten-GigabitEthernet2/2/0/8, Bridge-Aggregation1013] physical: [Ten-GigabitEthernet2/2/0/9||1,Ten-GigabitEthernet2/2/0/8|bbbbb|,Ten-GigabitEthernet2/2/0/11,Ten-GigabitEthernet2/2/0/10|aaaaaaaaaaaa|1,Ten-GigabitEthernet2/2/0/15|CCCCCCCC] |
|
日志说明 |
用户进行了配置聚合口的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid deviceId value：无效的网元设备ID · The value of the model field must be 1, 2, or 3：聚合组工作模式仅支持数字1、2、3 · Port configuration error：端口信息配置错误 · The aggregation and physical fields cannot both be empty：聚合口列表和物理口列表不允许同时为空 · The aggregation group member doesn't exist：该聚合组成员不存在 · The aggregation group ID is out of range：聚合组编号超出范围 · The device ID does not exist：指定的网元设备ID不存在 · The group index has been used by another group：指定的聚合组编号已被其他聚合组使用 · The aggregation group member already exists on the device：该聚合组成员在指定的网元上已存在 · Invalid aggregateInterface value：聚合口名称不合法 · Invalid physicalInterface value：物理口列表名称不合法 · Unknown Error：未知错误 · The request timed out：Requst请求超出时间 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
ADD_AUTOCFG_TEMPLATE_OP |
|
日志内容 |
Added an automated configuration template:$1 |
|
参数解释 |
$1：增加自动化配置信息 |
|
举例 |
Added an automated configuration template: perspectiveId:[1] gatewayScheme:[2] roleType:[$2] underlayType:[1] fabricId:[ffffffff-0000-0000-0000-000000000001] name:[underlay_ll.template] desc:[testdesc] segment:[] "openOptional": [false], "vtepIpAssignWay": [1], "autoCfgRequiredMap": [ { paraName:[username] paraValue:[admin] paraTip:[用户名。字母、数字或者-_，有效长度1~55。（同一个dc里，请保持spine和leaf的用户名和密码一致。 ] required:[true] }, { paraName:[master_spine_mac] paraValue:[C4CA-D930-5D6E] paraTip:[MASTER SPINE MAC。MAC地址格式为“xxxx-xxxx-xxxx”，不允许全0全f；不允许是组播MAC，第二个数不能为奇数；允许输入多个地址，地址间以英文逗号分隔。 ] required:[true] }, { paraName:[irf_disable] paraValue:[False] paraTip:[是否IRF堆叠。可选值：False，True。] required:[true] }, { paraName:[bgp_as] paraValue:[100] paraTip:[BGP AS号。数字，范围[1-4294967295]。该值只用于Overlay BGP。] required:[true] }, { paraName:[ntp_server] paraValue:[11.100.65.111] paraTip:[NTP服务地址。IPv4，点分十进制格式。] required:[true] }, { paraName:[password] paraValue:[******] paraTip:[密码。字母、数字或者-_，有效长度3~64。（同一个dc里，请保持spine和leaf的用户名和密码一致）。 ] required:[true] } ] "autoCfgOptionalMap": [ { paraName:[evpn] paraValue:[True] paraTip:[EVPN 控制。可选值：True，False。] required:[false] }, { paraName:[mlag] paraValue:[True] paraTip:[是否开启mlag。可选值：True，False。] required:[false] }, { paraName:[dr_create_mode] paraValue:[manual] paraTip:[DR接口创建方式。可选值：manual，auto。] required:[false] }, { paraName:[dr_link_mode] paraValue:[dynamic] paraTip:[DR接口聚合模式。可选值：dynamic，static。] required:[false] }, { paraName:[dr_group_id_range] paraValue:[1-20] paraTip:[跨设备聚合编号范围。格式为x-y，最小值和最大值的取值范围为1~1024。] required:[false] }, { paraName:[ keep_alive_link_type] paraValue:[direct_link] paraTip:[keepalive链路。仅在有peerlink场景下有效，取值仅支持mgmt_link与direct_link，分别对应管理网链路与直连链路。] required:[false] }, { paraName:[ escape_vlan_id] paraValue:[3] paraTip:[逃生VLAN ID。仅在有peerlink场景下有效，long类型数字，无缺省值，范围2-4094。] required:[false] }, { paraName:[ reserved_vxlan_id] paraValue:[1000] paraTip:[保留VXLAN。仅在无peerlink场景下有效，long类型数字，无缺省值，范围1-16777215。] required:[false] } ] |
|
日志说明 |
用户进行了增加自动化配置的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · The value of the vtepIpAssignWay field can only be 1 or 2：VTEP IP分配方式仅支持数字1和2 · The default fabric does not exist in the controller：控制组件中不存在默认Fabric的UUID · The value of the openOptional field is invalid：无效的openOptional字段 · The underlay protocol type of the fabric must be the same as that specified by the underlayType field：指定Fabric下的Underlay协议类型必须和underlayType字段中数字代表的协议类型一致 · The VTEP IP allocation mode of the fabric must be the same as that specified by the vtepIpAssignWay field：指定Fabric的VTEP IP分配方式必须和vtepIpAssignWay字段中数字代表的分配方式一致 · The EVPN state of the fabric must be compatible with the gateway mode specified by the gatewayScheme field：指定Fabric的EVPN开关必须和gatewayScheme字段中数字代表的网关方案一致 · The requested perspectiveId is invalid：无效的UCD视图ID · The requested perspectiveId is required：UCD视图ID不允许为空 · The requested gatewayScheme is invalid：无效的的网关方案 · The requested gatewayScheme is required：网关方案不允许为空 · The requested roleType is invalid：无效的角色类型 · The requested roleType is required：角色类型不允许为空 · The requested underlayType is invalid：无效的Underlay 协议 · The requested underlayType is required：Underlay协议不允许为空 · You have no privilege to perform this operation：用户无权限执行此操作 · A deployment template of the role already exists in the same fabric：同一Fabric下指定角色的设备上线模板已存在 · Invalid interface aggregation mode：接口聚合模式取值无效 · Please specify the M-LAG group ID range：必须指定M-LAG组编号范围 · Comma-separated list of integers (1 to 1024) and integer ranges (x-y, x must be smaller than y). Example: 200,201-205. The integer ranges cannot overlap;The length cannot exceed 255：取值范围为1~1024的整数或区间，例如200或201-255；当取值为区间时，起始值必须小于结束值。如需输入多个整数或区间，中间需用“,”隔开；跨设备聚合编号范围不能重叠；长度不能大于255 · Invalid keepalive link type：Keepalive链路取值无效 · The critical VLAN ID must be an integer in the range of 2 to 4094：取值范围为2～4094的整数 · The reserved VXLAN ID must be an integer in the range of 1 to 16777215：取值范围为1～16777215的整数 · Auto downlink aggregation cannot be enabled when distributed relay is enabled and IRF stacking is disabled：使能跨设备聚合且不使能IRF堆叠时，不允许使能下行口自动聚合 |
|
关键字 |
ADD_AUTOPARAM_OP |
|
日志内容 |
Added automation parameters:$1 |
|
参数解释 |
$1：增加自动化参数信息 |
|
举例 |
Added automation parameters: name:[test] snmpTempId:[1] netconfTempId:[4] netconfTempType:[1] fabricId:[a1fb8545-0b41-4299-8c2d-fdb32bba961b] |
|
日志说明 |
用户进行了增加自动化参数的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · The NETCONF template ID does not exist：NETCONF模板ID不存在 · The NETCONF template type does not exist：NETCONF模板类型不存在 · The NETCONF template ID is required：NETCONF模板ID不允许为空 · The NETCONF template type is required：NETCONF模板类型不允许为空 · The SNMP template ID is required：SNMP模板ID不允许为空 · The SNMP template ID does not exist：SNMP模板ID不存在 · The default fabric does not exist in the controller：控制组件中不存在默认Fabric的UUID · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
ADD_AUTOPOLICY_OP |
|
日志内容 |
Added an automation policy:$1 |
|
参数解释 |
$1：增加自动化策略信息 |
|
举例 |
Added an automation policy: name:[test] executeCondition:[4] autoCfgId:[250f362f-de09-4c28-ab01-586451b897a5] autoParamId:[d5c1d35e-62f5-4259-a905-98183d9fd065] softwareId:[bc790ff8-bafe-4c5b-bb39-837a1b16532e] softwarePatchId:[bc790ff8-bafe-4c5b-bb39-837a1b16531e] |
|
日志说明 |
用户进行了增加自动化策略的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · The automation policy name is required：自动化策略名称不能为空 · The policy name is invalid：无效的策略名称 · The execute condition is invalid：无效的的执行条件 · The executeCondition field cannot be empty：执行条件不能为空 · The automated configuration template ID is required：自动化配置ID不能为空 · The automated configuration template ID is invalid：无效的自动化配置ID · The automation parameters are required：自动化参数ID不能为空 · The automation parameter ID is invalid：无效的自动化参数ID · The software version or patch is invalid：无效的软件版本或者软件补丁 · Configuration recovery is in progress：配置正在恢复过程中 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
BRINGUP_INTERFACE_OP |
|
日志内容 |
Brought up interfaces:$1 |
|
参数解释 |
$1：启动端口的信息 |
|
举例 |
Brought up interfaces: begin:[FortyGigE1/0/49] deviceId:[1] end:[FortyGigE1/0/50] |
|
日志说明 |
用户执行了启动端口的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid request：请求不合法 · Service not started：服务未启动 · Invalid JSON format：无效的JSON格式 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · The start interface name is required：必须指定起始端口名称 · The start interface name is invalid：起始端口名称不合法 · The end interface name is required：必须指定结束端口名称 · The end interface name is invalid：结束端口名称不合法 · The device ID is required：必须指定设备ID · Invalid device ID：设备ID不合法 · Internal server error：内部错误 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
SHUTDOWN_INTERFACE_OP |
|
日志内容 |
Shut down interfaces:$1 |
|
参数解释 |
$1：关闭的端口信息 |
|
举例 |
Shut down interfaces: begin:[FortyGigE1/0/49] deviceId:[1] end:[FortyGigE1/0/50] |
|
日志说明 |
用户执行了关闭端口的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid request：请求不合法 · Service not started：服务未启动 · Invalid JSON format：无效的JSON格式 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · The start interface name is required：必须指定起始端口名称 · The start interface name is invalid：起始端口名称不合法 · The end interface name is required：必须指定结束端口名称 · The end interface name is invalid：结束端口名称不合法 · The device ID is required：必须指定设备ID · Invalid device ID：设备ID不合法 · Internal server error：内部错误 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CFG_INTERFACE_OP |
|
日志内容 |
Configured an interface:$1 |
|
参数解释 |
$1：配置端口的信息 |
|
举例 |
Configured an interface: interfaceName:[FortyGigE1/0/49] deviceId:[1] portDesc:[ FortyGigE1/0/49 desc] edgedPort:[stp edged-port] |
|
日志说明 |
用户执行了配置端口的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid request：请求不合法 · Service not started：服务未启动 · Invalid JSON format：无效的JSON格式 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · The interface name is required：必须指定端口名称 · The interface name is invalid：端口名称不合法 · The device ID is required：必须指定设备ID · Invalid device ID：设备ID不合法 · Invalid edge interface configuration：边缘端口配置不合法 · The description cannot exceed 255 characters：描述信息字段最长255个字符 · Internal server error：内部错误 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
ADD_AUTO_REPLACE_TASK_OP |
|
日志内容 |
Added an automatic device replacement task:$1 |
|
参数解释 |
$1：增加自动化替换任务 |
|
举例 |
Added an automatic device replacement task: newDevId: [1] fileId: [2] replaceType: [3] taskName: [testTask] devSn: [13212adasd2q321dadsa] faultDevId: [6] masterSpineMac: [01-23-45-67-89-ab] stackMemberId: [7] startCfgName: [10.100.0.2_20190611093442_startup.cfg] |
|
日志说明 |
用户进行了增加自动化替换任务的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · The task name is required：任务名称字段不存在 · The device serial number is required：设备序列号为必填字段 · The failed device ID is required：故障设备ID为必填字段 · The replacement type is required：替换类型为必填字段 · The replacement type is invalid：替换类型不合法 · The master spine MAC does not exist：Master Spine MAC地址不存在 · The master spine MAC is invalid：Master Spine MAC地址不合法 · The fault device does not in asset information：故障设备不存在资产信息中 · The fault device is same as replacement device：故障设备和替换设备不能为同一台设备 · The fault device is UN_MANAGED：故障设备未被控制组件纳管 · Failed to create member ID：指定设备的成员ID创建失败 · Failed to obtain the maximum stacking capability of the device：未能获取到设备的最大堆叠能力 · Failed to obtain the master device ID：未能获取到主设备ID · Failed to obtain the replacement device ID：未能获取到替换设备ID · Unknown system error：系统未知错误 · Failed to obtain information about the IRF fabric：获取堆叠设备信息失败 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
ADD_FABRIC_AND_DEPLOY_RESOURCE_POOL_OP |
|
日志内容 |
Added a fabric and a deploy resource pool:$1 |
|
参数解释 |
$1：Fabric和管理/部署资源池的信息 |
|
举例 |
Added a fabric and a deploy resource pool: fabric:[ id: [edfed45a-d3a9-4bb0-bfe3-b5fe5c2c9018] name: [fabric1] underlayProtocol: [BGP] vtepIpAssignWay: [MASTER_SPINE_ALLOC] evpn: [true] arpCtrl: [ arpFlooding: [false] arpProxy: [false] arpToController: [false] ] dhcpCtrl: [ dhcpToController: [false] ] rarpCtrl: [ rarpFlooding: [false] rarpToController: [false] ] ndCtrl: [ ndProxy: [true] nsnaFlooding: [false] nsnaToController: [true] rsraToController: [true] rsraFlooding: [false] ] dhcpv6Ctrl: [ dhcpv6ToController: [true] ] macAdvertising: [false] lldpToController: [false] asNumber: [100] defaultFabric: [false] needWhiteList: [false] rrMacList: [00:01:00:01:00:02 ]], deploy_resource_pool=[ Type: [out-of-band] Fabric ID: [edfed45a-d3a9-4bb0-bfe3-b5fe5c2c9018] DHCP server settings:[ ID: [14ed05b2-2a52-4f04-aa4e-6f215e622a39] ] VTEP IP pool list:[ VTEP IP pool settings :[ ID: [4d43be3b-0f7d-42c2-a5a0-2bbfcdb9dfa1] ] ] Loopback1 pool list:[ loopback1 pool settings :[ ID: [4d43be3b-0f7d-42c2-a5a0-2bbfcdb9dfa2] ] ] Management IP pool list :[ Management IP pool settings :[ ID: [4d43be3b-0f7d-42c2-a5a0-2bbfcdb9dfae] ] ] Vlan1 IP pool list:[ Vlan1 IP pool settings :[ ID: [4d43be3b-0f7d-42c2-a5a0-2bbfcdb9dfa3] ] ] vlan4094PoolConfigs IP pool list:[ vlan4094 IP pool settings :[ ID: [4d43be3b-0f7d-42c2-a5a0-2bbfcdb9dfa3] ] ] ]] |
|
日志说明 |
用户进行了增加Fabric和管理/部署资源池的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · The system VDS does not exist：系统VDS不存在 · The default DHCP server does not exist：系统默认DHCP不存在 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_DEVICE_CONFIG_FRAGMENT_OP |
|
日志内容 |
Created configuration fragment: $1 |
|
参数解释 |
$1：配置片段信息 |
|
举例 |
Created configuration fragment: name: [命令片段1] deviceIp: [10.10.10.10] description: 端口描述信息及限速 |
|
日志说明 |
用户进行了创建指定设备配置片段的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The specified configuration fragment already exists：指定ID的设备配置片段已存在 · The configuration fragment name can not be empty：设备配置片段名称不可为空 · The name cannot exceed 255 characters：设备配置片段名称最长255个字符 · Duplicate configuration fragment name in memory：指定名称的设备配置片段已存在 · The configuration fragment IP can not be empty：设备配置片段的IP不能为空 · Invalid configuration fragment IP：无效的设备配置片段IP · The configuration fragment can not be empty：设备配置片段不能为空 · The description cannot exceed 255 characters：描述信息最长255个字符 |
|
关键字 |
UPDATE_DEVICE_CONFIG_FRAGMENT _OP |
|
日志内容 |
Updated configuration fragment: $1 |
|
参数解释 |
$1：设备配置片段信息 |
|
举例 |
Updated configuration fragment: name:[命令片段1] deviceIp:[10.10.10.10] description:端口描述信息及限速 |
|
日志说明 |
用户进行了修改指定设备配置片段的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The specified configuration fragment is not found：指定的设备配置片段不存在 · The specified configuration fragment is being deployed：指定的设备配置片段正在下发 · The configuration fragment name can not be empty：设备配置片段名称不能为空 · The description cannot exceed 255 characters：描述信息最长255个字符 · The configuration fragment does not exist：配置片段不存在 |
|
关键字 |
DELETE_DEVICE_CONFIG_FRAGMENT _OP |
|
日志内容 |
Deleted configuration fragment: $1 |
|
参数解释 |
$1：配置片段名称 |
|
举例 |
Deleted configuration fragment: 配置片段1 |
|
日志说明 |
用户进行了删除指定设备配置片段的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · Invalid configuration fragment ID：无效的设备配置片段ID · The specified configuration fragment is not found：指定的设备配置片段不存在 · The specified configuration fragment is being deployed：指定的设备配置片段正在下发 |
|
关键字 |
IMPORT_DEVICE_CONFIG_FRAGMENT_LIST_OP |
|
日志内容 |
Imported configuration fragment list: $1 |
|
参数解释 |
$1：配置片段的条数 |
|
举例 |
Imported configuration fragment list: 100 |
|
日志说明 |
用户进行了批量导入设备配置片段的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · Duplicate configuration fragment name in the file：设备配置文件中存在重复的名称 · Failed to read the Excel file. Reason: $1：Excel文件读取失败，原因为$1 $1：文件读取失败的的原因 ¡ The hyperlink for cell $2 references relation $3, but that didn't exist：单元格$2的超链接引用关系$3不存在 |
|
关键字 |
DELETE_DEVICE_CONFIG_FRAGMENT_LIST_OP |
|
日志内容 |
Deleted configuration fragment list: $1 |
|
参数解释 |
$1：设备配置片段的条数 |
|
举例 |
Deleted configuration fragment list: 100 |
|
日志说明 |
用户进行了批量删除设备配置片段的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · Failed to delete some configuration fragments：部分设备配置片段删除失败 |
|
关键字 |
UPDATE_PORT_PERMIT_VLAN_OP |
|
日志内容 |
Updated port permitted VLAN:$1 |
|
参数解释 |
$1：靶场端口放行信息 |
|
举例 |
Updated port permitted VLAN: Device IP: [1.1.1.1] NETCONF username: [admin] NETCONF password: [******] Deleted VLAN: [true] VLAN list: [ { VLAN: [100] Port list: [Ten-GigabitEthernet1/0/2, Ten-GigabitEthernet1/0/3] } { VLAN: [200] Port list: [Ten-GigabitEthernet1/0/1, Ten-GigabitEthernet1/0/2] } ] |
|
日志说明 |
用户进行了修改靶场端口放行信息的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · The request is invalid：请求的无效 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · Invalid device IP address：无效的IP地址 · The device IP address is required：设备的IP地址不允许为空 · The NETCONF username and password is required：必须指定设备的NETCONF用户名和密码 · The VLAN must be in the range of 1 to 4094：VLAN的取值范围为1～4094的整数 · Configuration distribution failed, because the VLAN list contains non-trunk ports or ports with invalid names：配置下发失败，可能的原因：VLAN列表中存在非Trunk端口；VLAN列表中存在名称不合法的端口 · The VLAN is requeired：VLAN不允许为空 · Duplicate VLANs exist：存在重复的VLAN · Failed to establish an NETCONF connection between the controller and the device：控制组件与设备建立NETCONF连接失败 · Please specify a VLAN list：VLAN列表不允许为空 · Please specify a port list for each newly added VLAN：更新端口放行时，新增VLAN下的端口列表不允许为空 · The device is assigning ports to their respective VLANs：当前设备正在处理端口放行任务 · The current user is not authorized to perform this operation：当前用户无权限执行此操作 |
|
关键字 |
START_AUTOMATIONSWITCH_OP |
|
日志内容 |
Started the automation process for a device: $1 |
|
参数解释 |
$1：设备信息 |
|
举例 |
Started the automation process for a device: ID: [7f577a47-0108-499d-8fca-298051c45cef] Name: [spine-162.162.163.2] IP: [162.162.163.2] |
|
日志说明 |
用户进行了运行设备自动化进程的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · Failed to obtain the state of the device automation process for the device：获取设备的自动化状态失败 · The specified device automation process does not exist：指定的设备自动化进程不存在 · The specified device does not exist：指定的设备不存在 · The specified device is in Inactive state or is not an automatically deployed device：指定的设备为Inactive状态或不是通过自动化上线的设备 |
|
关键字 |
STOP_AUTOMATIONSWITCH_OP |
|
日志内容 |
Stopped the automation process for a device: $1 |
|
参数解释 |
$1：设备信息 |
|
举例 |
Stopped the automation process for a device: ID: [7f577a47-0108-499d-8fca-298051c45cef] Name: [spine-162.162.163.2] IP: [162.162.163.2] |
|
日志说明 |
用户进行了停止设备自动化进程的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · Failed to obtain the state of the device automation process for the device：获取设备的自动化状态失败 · The specified device automation process does not exist：指定的设备自动化进程不存在 · The specified device does not exist：指定的设备不存在 · The specified device is in Inactive state or is not an automatically deployed device：指定的设备为Inactive状态或不是通过自动化上线的设备 |
|
关键字 |
SYNC_AUTOMATIONSWITCH_OP |
|
日志内容 |
Synced the automation process for a device: $1 |
|
参数解释 |
$1：设备信息 |
|
举例 |
Synced the automation process for a device: ID: [7f577a47-0108-499d-8fca-298051c45cef] Name: [spine-162.162.163.2] IP: [162.162.163.2] |
|
日志说明 |
用户进行了同步设备自动化进程的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · Failed to obtain the state of the automation process for the device：获取设备的自动化状态失败 · The specified device does not exist：指定的设备不存在 · The specified device is in Inactive state or is not an automatically deployed device：指定的设备为Inactive状态或不是通过自动化上线的设备 |
|
关键字 |
ISOLATED_IP_CONFIG_OP |
|
日志内容 |
Failed to issue the isolating IP configuration $1. Successfully issued the isolating IP configuration $2. |
|
参数解释 |
$1：预案的相关信息 $2：预案的相关信息 |
|
举例 |
举例1： Failed to issue the isolating IP configuration { "deviceIp": "192.158.0.1", "interfaceName": "XGE1/0/1", "ifIndex": "121212", "direction": "1", "action": "issued", "aclRule":[{ "action": "1", "source": "1.1.1.12" }]} 举例2： Successfully issued the isolating IP configuration { "aclName":"b2309e53-45c5-416e-955e-38c213cb5272", "deviceIp":"192.158.30.12", "interfaceName":"Ten-GigabitEthernet2/0/4", "ifIndex":"198", "direction":1, "action":"issued", "aclRule":[{ "ruleId":"0", "action":1, "source":"15.4.5.4" }]} |
|
日志说明 |
用户进行了应用隔离IP预案的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The system service does not respond：系统服务未响应 · The request is required：请求参数不能为空 · Invalid request parameter：请求参数不合法 · Invalid ACL rule ID：无效的ACL规则ID · The source IP is required：源IP不能为空 · The direction is required：流量方向不能为空 · Invalid direction：无效的流量方向 · The ACL name is invalid：ACL名称不合法 · The device IP is required：设备IP不能为空 · Invalid IP address：无效的IP地址 · The interface name is required：接口名称不能为空 · Invalid interface name：无效的接口名称 · The interface index is required：接口索引不能为空 · Invalid interface index：无效的接口索引 · The action field is required：action字段不能为空 · Invalid action field：无效的action字段 · The ACL rule is required ACL：规则不能为空 · Invalid ACL rule：无效的ACL规则 · The ACL name is required：ACL名称不能为空 · The ACL rule ID is required：ACL规则ID不能为空 · Netconf command issued failed：netconf下发失败 · Netconf configuration delivery failed：netconf调用失败 |
|
关键字 |
ISOLATED_SINGLE_BOARD_OP |
|
日志内容 |
Failed to issue the isolating card configuration $1. Successfully issued the isolating card configuration $2. |
|
参数解释 |
$1：预案的相关信息 $2：预案的相关信息 |
|
举例 |
举例1： Failed to issue the isolating card configuration { "deviceIp":"192.158.30.12", "chassisNumber":"0", "slotNumber":"3", "action":"rollback" } 举例2： Successfully issued the isolating card configuration { "deviceIp":"192.158.30.12", "chassisNumber":"0", "slotNumber":"12", "action":"issued" } |
|
日志说明 |
用户进行了应用隔离单板预案的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is required：请求参数不能为空 · Invalid request parameter：请求参数不合法 · The system service does not respond：系统服务未响应 · The device IP is required：设备IP不能为空 · Invalid device IP：无效的设备IP · Invalid slot number：无效的槽位号 · Invalid chassis number：无效的机箱号 · The chassis number is required：机箱号不能为空 · The action field is required：action字段不能为空 · Invalid action field：无效的action字段 · Netconf command issued failed：netconf下发失败 · Netconf configuration delivery failed：netconf调用失败 |
|
关键字 |
REBOOT_SINGLE_BOARD_OP |
|
日志内容 |
Failed to issue the reboot card configuration $1. Successfully issued the reboot card configuration $2. |
|
参数解释 |
$1：预案的相关信息 $2：预案的相关信息 |
|
举例 |
举例1： Failed to issue the reboot card configuration { "deviceIp":"192.158.30.12", "chassisNumber":"0", "slotNumber":"3" } 举例2： Successfully issued the reboot card configuration { "deviceIp":"192.158.30.12", "chassisNumber":"0", "slotNumber":"3" } |
|
日志说明 |
用户进行了应用重启单板预案的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is required：请求参数不能为空 · Invalid request parameter：请求参数不合法 · The device IP is required：设备IP不能为空 · Invalid device IP：无效的设备IP · Invalid slot number：无效的槽位号 · Invalid chassis number：无效的机箱号 · The chassis number is required：机箱号不能为空 · The system service does not respond：系统服务未响应 · Netconf command issued failed：netconf下发失败 · Netconf configuration delivery failed：netconf调用失败 |
|
关键字 |
ISOLATED_NET_BOARD_CONFIG_OP |
|
日志内容 |
Failed to issue the isolating fabric module configuration $1. Successfully issued the isolating fabric module configuration $2. |
|
参数解释 |
$1：预案的相关信息 $2：预案的相关信息 |
|
举例 |
举例1： Failed to issue the isolating fabric module configuration { "deviceIp":"192.158.30.12", "chassisNumber":"0", "slotNumber":"12", "action":"rollback" }. 举例2： Successfully issued the isolating fabric module configuration { "deviceIp":"192.158.30.12", "chassisNumber":"0", "slotNumber":"3", "action":"issued" }. |
|
日志说明 |
用户进行了应用隔离网板预案的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is required：请求参数不能为空 · Invalid request parameter：请求参数不合法 · The device IP is required：设备IP不能为空 · Invalid device IP：无效的设备IP · Invalid slot number：无效的槽位号 · Invalid chassis number：无效的机箱号 · The chassis number is required：机箱号不能为空 · The system service does not respond：系统服务未响应 · The chassis number is required：机箱号不能为空 · The action field is required：action字段不能为空 · Netconf command issued failed：netconf下发失败 · Netconf configuration delivery failed：netconf调用失败 |
|
关键字 |
DELETE_PORT_DESC_OP |
|
日志内容 |
Deleted an interface description: deviceId: $1 interfaceName: $2 |
|
参数解释 |
$1：设备ID $2：接口名称 |
|
举例 |
Delete an interface description: deviceId: [2] interfaceName: [Ten-GigabitEthernet1/0/33] |
|
日志说明 |
用户进行了删除接口描述的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid request：请求不合法 · Service not started：服务未启动 · Invalid JSON format：无效的JSON格式 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · The interface name is invalid：端口名称不合法 · Invalid device ID：设备ID不合法 · Internal server error：内部错误 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_EDGE_PORT_OP |
|
日志内容 |
Deleted an edge port: deviceId: $1 interfaceName: $2 |
|
参数解释 |
$1：设备ID $2：边缘接口名称 |
|
举例 |
Delete an edge port: deviceId: [2] interfaceName: [Ten-GigabitEthernet1/0/33] |
|
日志说明 |
用户进行了删除边缘接口的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid request：请求不合法 · Service not started：服务未启动 · Invalid JSON format：无效的JSON格式 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · The interface name is invalid：端口名称不合法 · Invalid device ID：设备ID不合法 · Internal server error：内部错误 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_LACP_FAST_OP |
|
日志内容 |
Deleted lacp fast: deviceId: $1 interfaceName: $2 |
|
参数解释 |
$1：设备ID $2：物理接口名称 |
|
举例 |
Deleted lacp fast: deviceId: [2] interfaceName: [Ten-GigabitEthernet1/0/33] |
|
日志说明 |
用户进行了删除聚合组成员口的Lacpfast配置的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · The aggregation group member doesn’t exist：该聚合组成员不存在 · Unknown error：未知错误 · The device ID doesn't exist：指定的设备ID不存在 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_AGGRE_INTERFACE_OP |
|
日志内容 |
Deleted an aggregate interface: deviceId: $1 interfaceName: $2 |
|
参数解释 |
$1：设备ID $2：聚合口名称 |
|
举例 |
Deleted an aggregate interface: deviceId: [2] interfaceName: [Bridge-Aggregation6] |
|
日志说明 |
用户进行了删除聚合口的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · The aggregation group doesn’t exist：该聚合组不存在 · Unknown error：未知错误 · The device ID doesn't exist：指定的设备ID不存在 · You have no privilege to perform this operation：用户无权限执行此操作 |
本节介绍Issue模块输出的操作日志信息。
|
关键字 |
ISOLATED_IP_CONFIG_OP |
|
日志内容 |
IP isolation configuration: $1. |
|
参数解释 |
$1：IP隔离的配置，包括下发隔离规则的接口、接口索引、规则应用方向、需要隔离的源IP地址、IP版本、对匹配流量的操作等 |
|
举例 |
IP isolation configuration: { "aclName":"b357c104-7160-4b76-9bd4-ae941d6b83d2", "deviceIp":"192.158.25.98", "interfaceName":"Twenty-FiveGigE1/0/49", "ifIndex":"81", "direction":1, "action":"issued", "aclRule":[ { "ruleId":"0", "action":1, "source":"2001:0:0:1A::10", "ipVersion":"6", "vpnName":"" } ] } |
|
日志说明 |
用户下发或删除了IP隔离的配置 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid request parameter：无效的请求参数 · The aclName is required：aclName必填 · Invalid aclName：无效的aclName · The device IP is required：device ip必填 · Invalid device IP：无效的device ip · The direction is required：direction必填 · Invalid direction：无效的direction · The action field is required：action字段必填 · Invalid action field：无效的action字段 · The ACL rule ID is required：rule Id必填 · Invalid ACL rule ID：无效的rule Id · The ACL rule is required：无效的分析组件密码格式 · The ACL rule action is required：acl rule action必填 · Invalid ACL rule action：无效的acl rule action · The source IP is required：source ip必填 · Invalid ACL rule source IP：无效的source ip · The vpnName length can't exceed 31：vpnName字段长度不能超过31 · Netconf configuration delivery failed：Netconf配置传递失败 · Netconf command deployment failed：Netconf命令下发失败 |
|
关键字 |
ISSUED_ARP_FILTER_CONFIG_OP |
|
日志内容 |
ARP filter module configuration: $1 |
|
参数解释 |
$1：为指定接口启用或关闭ARP网关保护相关信息，包括设备IP地址，网关IP地址，以及接口索引等 |
|
举例 |
ARP filter module configuration: { "deviceIp":"192.158.25.97", "gatewayIp":"3.1.1.6", "ifIndex":"3", "action":"issued" } |
|
日志说明 |
用户进行了ARP网关保护配置操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid request parameter：无效的请求参数 · The device IP is required：device ip必填 · Invalid device IP：无效的device ip · The gateway IP is required：gateway IP必填 · Invalid IP address：无效的IP地址 · The interface index is required：interface index必填 · Invalid interface index：无效的interface index · The action field is required：action字段必填 · Invalid action field：无效的action字段 · Netconf configuration delivery failed：Netconf配置传递失败 · Netconf command deployment failed：Netconf命令下发失败 |
|
关键字 |
ISOLATED_SINGLE_BOARD_OP |
|
日志内容 |
Isolated card: $1 |
|
参数解释 |
$1：单板所在位置信息，包括单板所在设备的IP地址、框号以及槽位号 |
|
举例 |
Isolated card: { "deviceIp": "192.158.0.1", "slotNumber": "1", "chassisNumber": "0", "action": "issued" } |
|
日志说明 |
用户进行隔离单板的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid request parameter：无效的请求参数 · The device IP is required：device ip必填 · Invalid device IP：无效的device ip · The chassis number is required：chassis number必填 · Invalid classis number：无效的chassis number · Invalid slot number：无效的slot number · The action field is required：action字段必填 · Invalid action field：无效的action字段 · Netconf configuration delivery failed：Netconf配置传递失败 · Netconf command deployment failed：Netconf命令下发失败 |
|
关键字 |
REBOOT_SINGLE_BOARD_OP |
|
日志内容 |
Rebooted card: $1 |
|
参数解释 |
$1：单板所在位置信息，包括单板所在设备的IP地址、框号以及槽位号 |
|
举例 |
Rebooted card: { "deviceIp": "192.158.0.1", "slotNumber": "1", "chassisNumber": "0" } |
|
日志说明 |
用户进行重启单板的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid request parameter：无效的请求参数 · The device IP is required：device ip必填 · Invalid device IP：无效的device ip · The chassis number is required：chassis number必填 · Invalid classis number：无效的chassis number · Invalid slot number：无效的slot number · Netconf configuration delivery failed：Netconf配置传递失败 · Netconf command deployment failed：Netconf命令下发失败 |
|
关键字 |
ISOLATED_NET_BOARD_CONFIG_OP |
|
日志内容 |
Isolated fabric module: $1 |
|
参数解释 |
$1：隔离网板所在的位置信息，包括网板所在的设备IP地址，框号以及槽位号 |
|
举例 |
Isolated fabric module: { "deviceIp": "192.158.0.1", "slotNumber": "1", "chassisNumber": "0", "action": "issued" } |
|
日志说明 |
用户进行隔离网板的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid request parameter：无效的请求参数 · The device IP is required：device ip必填 · Invalid device IP：无效的device ip · The chassis number is required：chassis number必填 · Invalid classis number：无效的chassis number · Invalid slot number：无效的slot number · The action field is required：action字段必填 · Invalid action field：无效的action字段 · Netconf configuration delivery failed：Netconf配置传递失败 · Netconf command deployment failed：Netconf命令下发失败 |
|
关键字 |
RESET_OSPF_ROUTER_ID_OP |
|
日志内容 |
Re-set OSPF router ID: $1 |
|
参数解释 |
$1： OSPF Router ID重设的相关信息，包括设备IP地址、OSPF进程号、重设的Router ID、IP版本号，以及VPN实例名称等 |
|
举例 |
Re-set OSPF router ID: { "deviceIp": "192.158.0.1", "instanceId": "10", "routerId": "1.2.5.5", "ipVersion": 4, "vpnName": null } |
|
日志说明 |
用户进行OSPF Router ID重设的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid request parameter：无效的请求参数 · The device IP is required：device ip必填 · Invalid device IP：无效的device ip · Netconf configuration delivery failed：Netconf配置传递失败 · Netconf command deployment failed：Netconf命令下发失败 |
本节介绍IW模块输出的操作日志信息。
|
关键字 |
DELETE_TASK |
|
日志内容 |
Delete task: $1 |
|
参数解释 |
$1：任务ID |
|
举例 |
Delete task: abd2d9f6-36d9-45b8-b7e3-7a793b3a6f2c. |
|
日志说明 |
用户进行了删除意图任务的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · The specified task does not exist：指定任务不存在 · Internal error：内部错误 · Please specify the parameter：参数不能为空 · Service not found：服务未发现 · Invalid JSON format：非法的JSON格式 |
本节介绍应用保障输出的操作日志信息。
|
关键字 |
CREATE_KFM_TASK_OP |
|
日志内容 |
Created application assurance task: $1. |
|
参数解释 |
$1：应用保障任务信息 |
|
举例 |
Created application assurance task: ID:[e34c4f83-587b-4276-9f15-d2c49a66f899] Task Type:[app_inner] Protocol:[tcp,udp] Enable:[false] Src App Id:[96c4ff9f-3366-4a06-bc6f-0c206b154c44] Dst App Id:[96c4ff9f-3366-4a06-bc6f-0c206b154c44] Src Service Id:[28f8d23a-c385-468c-856b-fef5528444f1] Dst Service Id:[40618b5c-7e1d-491c-ad9c-039b88f327b3] Src Subnet Id:[3af5fcb9-25c6-445d-a787-054bbb6a8f49] Dst Subnet Id:[c4ace85d-dcdf-4a05-b0b5-3fd7acc3cc5f] Src Cidr:[113.113.98.0/24] Dst Cider:[113.113.193.0/24] Src Vpn:[19sgqpopd18nha1lerlajojrgi] Dst Vpn:[19sgqpopd18nha1lerlajojrgi] Src Port:[100] Dst Port:[200] |
|
日志说明 |
用户创建了一个应用保障任务 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · Database access errors：数据库访问异常 · The specified source subnet does not exist：指定的源子网信息不存在 · The specified destination subnet does not exist：指定的目的子网信息不存在 · An assurance task is already configured for the specified flow：指定流已存在保障任务 · The analyzer has failed to create the assurance task：分析组件创建保障任务失败 · The ID is read only：ID字段只读 · Invalid protocol：无效的protocol格式 · enable is required：使能字段必选 · src app id is required：源应用必选 · dst app id is required：目的应用必选 · src service id is required：源服务必选 · dst service id is required：目的服务必选 · src subnet id is required：源子网必选 · dst subnet id is required：目的子网必选 · src subnet cidr is required：源子网网段必选 · dst subnet cidr is required：目的子网网段必选 · src vrouter id is required：源虚拟路由器必选 · dst vrouter id is required：目的虚拟路由器必选 · src vpn is required：源vpn必选 · dst vpn is required：目的vpn必选 · src port is required：源端口必选 · dst port is required：目的端口必选 · Invalid port format：无效的port格式 · Failed to obtain source service information：获取源服务信息失败 · The application information associated with the source service does not match the specified application：指定源服务关联的应用信息不准确 · Failed to obtain destination service information：获取目的服务信息失败 · The application information associated with the destination service does not match the specified application：指定目的服务关联的应用信息不准确 · The source and destination applications in an assurance task must be the same：应用内保障任务的源应用和目的应用必须一致 · You cannot perform this operation in the current app state：当前应用状态下，无法进行该操作 · The source subnet must be different from the destination subnet.The IP version of the source subnet must be the same as that of the destination subnet：源子网和目的子网不能相同，并且IP版本必须相同 |
|
关键字 |
UPDATE_KFM_TASK_OP |
|
日志内容 |
Updated application assurance task: $1 |
|
参数解释 |
$1：应用保障任务信息 |
|
举例 |
UPDATE application assurance task: ID:[e34c4f83-587b-4276-9f15-d2c49a66f899] Task Type:[app_inner] Protocol:[tcp,udp] Enable:[true] Src App Id:[96c4ff9f-3366-4a06-bc6f-0c206b154c44] Dst App Id:[96c4ff9f-3366-4a06-bc6f-0c206b154c44] Src Service Id:[28f8d23a-c385-468c-856b-fef5528444f1] Dst Service Id:[40618b5c-7e1d-491c-ad9c-039b88f327b3] Src Subnet Id:[3af5fcb9-25c6-445d-a787-054bbb6a8f49] Dst Subnet Id:[c4ace85d-dcdf-4a05-b0b5-3fd7acc3cc5f] Src Cidr:[113.113.98.0/24] Dst Cider:[113.113.193.0/24] Src Vpn:[19sgqpopd18nha1lerlajojrgi] Dst Vpn:[19sgqpopd18nha1lerlajojrgi] Src Port:[100] Dst Port:[200] |
|
日志说明 |
用户更新了指定的应用保障任务 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · Database access errors：数据库访问异常 · The specified assurance task does not exist：指定的保障任务不存在 · The analyzer has failed to create the assurance task：分析组件创建保障任务失败 · Failed to delete the assurance task from the analyzer：删除分析组件中的保障任务失败 · The specified assurance task is already enabled：指定的保障任务已使能 · The specified assurance task is already disabled：指定的保障任务已去使能 · You cannot perform this operation in the current app state：当前应用状态下，无法进行该操作 |
|
关键字 |
DELETE_KFM_TASK_OP |
|
日志内容 |
Deleted application assurance task: $1 |
|
参数解释 |
$1：应用保障任务的UUID |
|
举例 |
Deleted application assurance task: [c352f537-ad49-48eb-ab05-1c6b8cb92233] |
|
日志说明 |
用户删除了指定的应用保障任务 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · Database access errors：数据库访问异常 · The specified assurance task does not exist：指定的保障任务不存在 · Failed to delete the assurance task from the analyzer：删除分析组件中的保障任务失败 · You cannot perform this operation in the current app state：当前应用状态下，无法进行该操作 |
本节介绍负载均衡服务模块输出的操作日志信息。
|
关键字 |
CREATE_LB_OP |
|
日志内容 |
Created load balancer $1. |
|
参数解释 |
$1：负载均衡器配置信息 |
|
举例 |
Created load balancer ID: 41e38478-da02-49e3-986e-6356ddd304f8 Tenant ID: ffffffff-0000-0000-0000-000000000001 Name: 9 Description: Type: SERVER Mode: GATEWAY Router ID: 5f96684a-5368-433c-bd26-158d351affd4 Status: DOWN Listener IDs: [ 4914ac1e-4acf-4966-b7de-c5c495751da9 ] Version: LB_V2. |
|
日志说明 |
用户进行了创建负载均衡器的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复中 · The service has not been found：服务未启动 · The configuration item already exists：配置项已存在 · The tenant specified for the configuration item doesn't exist：配置项指定的租户不存在 · The load balancer mode can only be GATEWAY, CGSR, or SERVICE_CHAIN：负载均衡器仅支持GATEWAY、CGSR和SERVICE_CHAIN三种模式 · The resource specified for the load balancer doesn't exist：负载均衡指定的资源不存在 · The pool specified for the load balancer doesn't exist：负载均衡器引用的实服务器组不存在 · The pool is already used by another the load balancer：实服务器组已被其它负载均衡器引用 · The tenant IDs for the load balancer and the specified pool are different：负载均衡器和指定实服务器组的租户ID不匹配 · The VIP address must belong to the subnet of the pool：虚服务器的IP地址必须属于实服务器组的子网 · The load balancers in the same VIP must have the same mode：引用同一虚服务器的负载均衡器的模式必须相同 · The subnet for the VIP and member are different：虚服务器与成员的子网不匹配 · Only the SERVICE_CHAIN type load balancers support server pool list configuration：仅SERVICE_CHAIN模式的负载均衡器支持配置实服务器组列表 · The VIP corresponding to the specified pool is enabled with SNAT and cannot be used by the SERVICE_CHAIN type load balancers：指定的实服务器组对应的虚服务器已开启源IP地址转换功能，不允许被SERVICE_CHAIN模式的负载均衡器引用 · The listener specified for the load balancer doesn't exist：负载均衡器引用的监听器不存在 · The listener is already used by another the load balancer：监听器已被其它负载均衡器引用 · The tenant IDs for the load balancer and the specified listener are different：负载均衡器和指定监听器的租户ID不匹配 · Only the SERVICE_CHAIN type load balancers support listener list configuration：仅SERVICE_CHAIN模式的负载均衡器支持配置监听器列表 · The listeners using the same VIP can be used only by the load balancers of the same mode：引用同一虚服务器的监听器只能被模式相同的负载均衡器引用 · The specified listener is already enabled with SNAT. The pool cannot be applied to a SERVICE_CHAIN type load balancer：指定的监听器已开启源IP地址转换功能，不允许被SERVICE_CHAIN模式的负载均衡器引用 · The tenant ID must be specified：租户ID必须被指定 · The status is read only：状态为只读字段 · The tenant name is read only：租户名称为只读字段 · The resource name is read only：资源名称为只读字段 · The pool name is read only：实服务器组名称为只读字段 · Failed to add the configuration item：添加配置项失败 · The resource ID can not be specified in gateway mode：资源ID在gateway模式中不能被指定 · The load balancer in service chain mode supports only network resources of the LB type：服务链模式的负载均衡仅支持 LB类型的资源 · The router ID is read only：虚拟路由器ID为只读字段 · The router name is read only：虚拟路由器名称为只读字段 · Only SERVER type load balancer supported：目前只支持创建SERVER类型负载均衡 · The specified pool is not referenced by any listener：指定的实服务器组未被监听器引用 · The load balancer can not have pools and listeners at one time：实服务器组和监听器不能同时指定 · The specified resource is not associated with any resource access template or the associated resource access template is unavailable：指定的资源未关联资源接入模板或关联的资源接入模板不可用 · The port number and associated virtual server IP address of one listener cannot both be the same as the port number and associated virtual server IP address of another listener：关联多个监听器时，两个监听器的监听端口和关联的虚服务器IP地址不能同时相同 · The IP addresses and port numbers of virtual servers associated with two server pools cannot both be the same：两个实服务器组关联的虚服务器的IP地址和端口号不能同时相同 · You have no privilege to perform this operation：用户无权限执行此操作 · Load balancers do not support the one-arm connection mode：负载均衡不支持单臂连接模式 · In EVPN networking environment, listeners using the same pool cannot be bound to multiple service-chain load balancers：EVPN组网环境下，绑定到不同服务链负载均衡器的监听器不能指定相同的实服务组 |
|
关键字 |
UPDATE_LB_OP |
|
日志内容 |
Updated load balancer $1. |
|
参数解释 |
$1：负载均衡器配置信息 |
|
举例 |
Updated load balancer ID: 41e38478-da02-49e3-986e-6356ddd304f8 Tenant ID: ffffffff-0000-0000-0000-000000000001 Name: 9 Description: Type: SERVER Mode: GATEWAY Router ID: 5f96684a-5368-433c-bd26-158d351affd4 Status: DOWN Listener IDs: [ 4914ac1e-4acf-4966-b7de-c5c495751da9 ] Version: LB_V2. |
|
日志说明 |
用户进行了修改负载均衡器的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复中 · The service has not been found：服务未启动 · The configuration item doesn't exist：配置项不存在 · The resource specified for the load balancer doesn't exist：负载均衡指定的资源不存在 · The pool specified for the load balancer doesn't exist：负载均衡器引用的实服务器组不存在 · The pool is already used by another the load balancer：实服务器组已被其它负载均衡器引用 · The tenant IDs for the load balancer and the specified pool are different：负载均衡器和指定实服务器组的租户ID不匹配 · The VIP address must belong to the subnet of the pool：虚服务器的IP地址必须属于实服务器组的子网 · The subnet for the VIP and member are different：虚服务器与成员的子网不匹配 · Only the SERVICE_CHAIN type load balancers support server pool list configuration：仅SERVICE_CHAIN模式的负载均衡器支持配置实服务器组列表 · The VIP corresponding to the specified pool is enabled with SNAT and cannot be used by the SERVICE_CHAIN type load balancers：指定的实服务器组对应的虚服务器已开启源IP地址转换功能，不允许被SERVICE_CHAIN模式的负载均衡器引用 · The listener specified for the load balancer doesn't exist：负载均衡器引用的监听器不存在 · The listener is already used by another the load balancer：监听器已被其它负载均衡器引用 · The tenant IDs for the load balancer and the specified listener are different：负载均衡器和指定监听器的租户ID不匹配 · Only the SERVICE_CHAIN type load balancers support listener list configuration：仅SERVICE_CHAIN模式的负载均衡器支持配置监听器列表 · The specified listener is already enabled with SNAT. The pool cannot be applied to a SERVICE_CHAIN type load balancer：指定的监听器已开启源IP地址转换功能，不允许被SERVICE_CHAIN模式的负载均衡器引用 · The listeners using the same VIP can be used only by the load balancers of the same mode：引用同一虚服务器的监听器只能被模式相同的负载均衡器引用 · When the LB SNAT type is default SNAT pool address, to create a CGSR-type load balancer with SNAT enabled, make sure the address pool contains addresses that have the same IP version as the load balancer：当LB用户源地址转换使用默认SNAT地址池模式，创建开启SNAT的服务网关类型LB服务时，该地址池里必须有与LB服务协议一致的地址 · The status is read only：状态为只读字段 · The tenant name is read only：租户名称为只读字段 · The resource name is read only：资源名称为只读字段 · The pool name is read only：实服务器组名称为只读字段 · The ID can not be modified：ID不允许被修改 · The mode can not be modified：模式不允许被修改 · The tenant ID can not be modified：租户ID不允许被修改 · Failed to modify the configuration item：修改配置项失败 · The resource ID can not be specified in gateway mode：资源ID在gateway模式中不能被指定 · The load balancer in service chain mode supports only network resources of the LB type：服务链模式的负载均衡仅支持LB类型的资源 · The router ID is read only：虚拟路由器ID为只读字段 · The router name is read only：虚拟路由器名称为只读字段 · The specified pool is not referenced by any listener：指定的实服务器组未被监听器引用 · The load balancer can not have pools and listeners at one time：实服务器组和监听器不能同时指定 · The specified resource is not associated with any resource access template or the associated resource access template is unavailable：指定的资源未关联资源接入模板或关联的资源接入模板不可用 · The port number and associated virtual server IP address of one listener cannot both be the same as the port number and associated virtual server IP address of another listener：关联多个监听器时，两个监听器的监听端口和关联的虚服务器IP地址不能同时相同 · The IP addresses and port numbers of virtual servers associated with two server pools cannot both be the same：两个实服务器组关联的虚服务器的IP地址和端口号不能同时相同 · You have no privilege to perform this operation：用户无权限执行此操作 · You cannot unbind the resource, because the load balancer has been bound to a service chain or service path：该负载均衡已被服务链或服务路径绑定，不允许解绑资源 · Load balancers do not support the one-arm connection mode：负载均衡不支持单臂连接模式 · In EVPN networking environment, listeners using the same pool cannot be bound to multiple service-chain load balancers：EVPN组网环境下，绑定到不同服务链负载均衡器的监听器不能指定相同的实服务组 |
|
关键字 |
DELETE_LB_OP |
|
日志内容 |
Deleted load balancer $1. |
|
参数解释 |
$1：负载均衡器名称 |
|
举例 |
Deleted load balancer lb70. |
|
日志说明 |
用户进行了删除负载均衡器的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · The operation requires the administrator privilege：您需要管理员权限才能执行此操作 · Configuration recovery is in progress：配置正在恢复中 · The service has not been found：服务未启动 · The configuration item doesn't exist：配置项不存在 · The configuration item is in use：配置项正在被使用 · Failed to delete the configuration item：删除配置项失败 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_VIRTUALIP_OP |
|
日志内容 |
Created VIP $1. |
|
参数解释 |
$1：虚服务器配置信息 |
|
举例 |
Created VIP ID: 6db0736e-4557-4062-b17e-820dfccc54d4 Name: virly Description: Tenant ID: ffffffff-0000-0000-0000-000000000001 Subnet ID: 97e33f9d-da04-4caa-808d-e48a82718b2f IP address: 10.10.10.10 Admin state up: true Status: DOWN |
|
日志说明 |
用户进行了创建负载均衡V2的虚服务器的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复中 · Invalid JSON format：无效的JSON格式 · The service has not been found：服务未启动 · The configuration item already exists：配置项已存在 · The tenant specified for the configuration item doesn't exist：配置项指定的租户不存在 · The IP address already exists：指定的IP地址已存在 · The IP address doesn't belong to the subnet：指定的IP地址不在子网网段内 · The subnet specified for the VIP doesn’t exist：指定的子网不存在 · The tenant IDs for the VIP and the specified subnet are different：指定的子网所属租户与虚服务器所属租户不一致 · The specified VIP address conflicts with a vPort IP, gateway IP, APP cluster VIP, or available address pair：虚服务器的IP地址与虚拟端口IP地址、网关IP地址或应用集群虚IP地址冲突 · The tenant ID must be specified：租户ID必须被指定 · Only an IPv4 subnet can be specified：仅支持指定IPv4子网 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_VIRTUALIP_OP |
|
日志内容 |
Updated VIP $1. |
|
参数解释 |
$1：虚服务器配置信息 |
|
举例 |
Updated VIP ID: 6db0736e-4557-4062-b17e-820dfccc54d4 Name: virly Description: Tenant ID: ffffffff-0000-0000-0000-000000000001 Subnet ID: 97e33f9d-da04-4caa-808d-e48a82718b2f IP address: 10.10.10.10 Admin state up: true Status: DOWN. |
|
日志说明 |
用户进行了修改负载均衡V2的虚服务器的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复中 · The service has not been found：服务未启动 · The configuration item doesn't exist：配置项不存在 · The IP address already exists：指定的IP地址已存在 · The VIP ID is read-only：虚服务器ID为只读字段 · The VIP name is read-only：虚服务器名称为只读字段 · The subnet ID is read-only：子网ID为只读字段 · The virtual port ID is read-only：虚服务器对应的虚拟端口ID为只读字段 · The IP address doesn't belong to the subnet：指定的IP地址不在子网网段内 · The tenant IDs for the VIP and the specified subnet are different：指定的子网所属租户与虚服务器所属租户不一致 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_VIRTUALIP_OP |
|
日志内容 |
Deleted VIP $1. |
|
参数解释 |
$1：虚服务器名称 |
|
举例 |
Deleted VIP virtualip60. |
|
日志说明 |
用户进行了删除负载均衡V2的虚服务器的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复中 · The service has not been found：服务未启动 · The configuration item doesn't exist：配置项不存在 · The configuration item is in use：配置项正在被使用 · Failed to delete the configuration item：删除配置项失败 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_LISTENER_OP |
|
日志内容 |
Created listener $1. |
|
参数解释 |
$1：监听器配置信息 |
|
举例 |
Created listener ID: ab8121f1-65b6-4709-8153-43695b83a187 Name: listener60 Description: Tenant ID: 00000000-0000-0000-0000-000000000000 Default pool ID: 5ba4d32a-8373-423c-b1e9-78de52f0733d Protocol: HTTP Protocol port: 6 Admin state up: true Connection limit: 0 VirtualIp ID: d686f86b-78a5-4c08-85aa-aa4c8803857d Enable snat: false Status: DOWN Idle timeout: 300 Insert XforwardedFor: false TCP option transparent: true TCP option number: 33 Bandwidth limit: 0 Bandwidth measure unit: KB Redirect up: true Redirect protocol: HTTP Redirect port: 33. |
|
日志说明 |
用户进行了创建监听器的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复中 · The service has not been found：服务未启动 · The configuration item already exists：配置项已存在 · The configuration item doesn't exist：配置项不存在 · The tenant specified for the configuration item doesn't exist：配置项指定的租户不存在 · The tenant IDs for the listener and the specified VIP are different：监听器和指定虚服务器的租户ID不匹配 · The port number is used by another listener using the same VIP：指定的端口号已被引用同一虚服务器的其他监听器占用 · The tenant IDs for the listener and the specified default pool are different：该监听器和默认实服务器组的租户ID不匹配 · The VIP for the specified default pool is different from the VIP used by the listener：指定的默认实服务器组关联的虚服务器与监听器引用的虚服务器不同 · The vRouters for the default pool and the VIP are different for the listener：指定的默认实服务器组与监听器引用的虚服务器所属的虚拟路由器不同 · The tenant name is read only：租户名称为只读字段 · The pool name is read only：实服务器组名称为只读字段 · The tenant ID must be specified：租户ID必须被指定 · The protocol must be specified：协议必须被指定 · The protocol port must be specified：协议端口必须被指定 · The connection limit must be specified：连接数限制必须被指定 · Failed to add the configuration item：添加配置项失败 · The virtual IP specified for the configuration item doesn't exist：配置项指定的虚服务器不存在 · The defaultPoolId specified for the configuration item doesn't exist：配置项指定的默认实服务器组不存在 · The virtualIp ID must be specified：虚服务器ID必须被指定 · The policy can be bound only to the listener whose protocol type is HTTP or HTTPS：策略只能绑定协议类型为HTTP或HTTPS的监听器 · A TCP-type or UDP-type listener doesn't support enabling XFF：协议类型为TCP或UDP的监听器不支持开启XFF功能 · Only HTTPS-type listeners support SSL certificate and SSL key configuration：只有HTTPS协议类型的监听器才能配置SSL证书和SSL密钥 · The SSL certificate and SSL key must be both specified or both left unspecified：SSL证书和SSL密钥必须同时指定或不指定 · To enable XFF for a listener whose protocol is HTTPS, you must specify SSL settings first：当监听器协议类型为HTTPS时，需先指定SSL相关配置才能开启XFF功能 · Invalid SSL certificate：无效的SSL证书 · Invalid SSL key：无效的SSL密钥 · You must configure a digital certificate when the listening protocol is HTTPS and multi-pool policies have been added：该监听器的监听协议为HTTPS，且已添加多实服务组分发策略，必须配置数字证书 · You must configure a digital certificate when the listening protocol is HTTPS and XFF is enabled该监听器的监听协议为HTTPS，且已开启XFF功能，必须配置数字证书 · A TCP-type or UDP-type listener doesn't support enabling redirect to URL：TCP或UDP类型的监听器不支持开启重定向到URL功能 · When redirecting to URL is enabled, the redirect protocol and redirect port must be specified：当开启重定向到URL功能，必须指定重定向协议和端口 · Only HTTPS-type listeners support enabling mutual authentication configuration：仅HTTPS类型的监听器支持开启双向认证功能 · A UDP-type listener doesn't support enabling TCP source IP transparent transmission：UDP类型的监听器不支持开启TCP源IP透传功能 · Listeners with port number 0 do not support enabling TCP source IP transparent transmission：端口号为0的监听器不支持开启TCP源IP透传功能 · The TCP option number ranges from 6, 7, 9 to 18, 22 to 254：TCP选项类型编号取值范围为<6-7,9-18,22-254> · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_LISTENER_OP |
|
日志内容 |
Updated listener $1. |
|
参数解释 |
$1：监听器配置信息 |
|
举例 |
Updated listener ID: ab8121f1-65b6-4709-8153-43695b83a187 Name: listener60 Description: Tenant ID: 00000000-0000-0000-0000-000000000000 Default pool ID: 5ba4d32a-8373-423c-b1e9-78de52f0733d Protocol: HTTP Protocol port: 6 Admin state up: true Connection limit: 0 VirtualIp ID: d686f86b-78a5-4c08-85aa-aa4c8803857d Enable snat: false Status: DOWN Idle timeout: 300 Insert XforwardedFor: false TCP option transparent: true TCP option number: 33 Bandwidth limit: 0 Bandwidth measure unit: KB Redirect up: true Redirect protocol: HTTP Redirect port: 33. |
|
日志说明 |
用户进行了修改监听器的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复中 · The service has not been found：服务未启动 · The configuration item doesn't exist：配置项不存在 · The tenant IDs for the VIP and the specified listener are different：监听器和指定虚服务器的租户ID不匹配 · The tenant IDs for the listener and the specified default pool are different：该监听器和指定默认实服务器组的租户ID不匹配 · The VIP for the specified default pool is different from the VIP used by the listener：指定的默认实服务器组关联的虚服务器与监听器引用的虚服务器不同 · The vRouters for the default pool and the VIP are different for the listener：指定的默认实服务器组与监听器引用的虚服务器所属的虚拟路由器不同 · The virtualIp specified for the configuration item doesn't exist：配置项指定的虚服务器不存在 · The defaultPoolId specified for the configuration item doesn't exist：配置项指定的默认实服务器组不存在 · The virtualIp ID must be specified：虚服务器ID必须被指定 · The default pool name can not be modified：实服务器组名称不允许被修改 · The virtualip ID can not be modified：虚服务器ID不允许被修改 · A TCP-type or UDP-type listener doesn't support enabling XFF：协议类型为TCP或UDP的监听器不支持开启XFF功能 · Only HTTPS-type listeners support SSL certificate and SSL key configuration：只有HTTPS协议类型的监听器才能配置SSL证书和SSL密钥 · The SSL certificate and SSL key must be both specified or both left unspecified：SSL证书和SSL密钥必须同时指定或不指定 · To enable XFF for a listener whose protocol is HTTPS, you must specify SSL settings first：当监听器协议类型为HTTPS时，需先指定SSL相关配置才能开启XFF功能 · Invalid SSL certificate：无效的SSL证书 · Invalid SSL key：无效的SSL密钥 · SSL-related configuration can’t be deleted if the listener of the HTTPS protocol type has been bound with a policy：当协议类型为HTTPS的监听器已被策略绑定时，SSL相关配置不允许删除 · You must configure a digital certificate when the listening protocol is HTTPS and multi-pool policies have been added：该监听器的监听协议为HTTPS，且已添加多实服务组分发策略，必须配置数字证书 · You must configure a digital certificate when the listening protocol is HTTPS and XFF is enabled该监听器的监听协议为HTTPS，且已开启XFF功能，必须配置数字证书 · A TCP-type or UDP-type listener doesn't support enabling redirect to URL：TCP或UDP类型的监听器不支持开启重定向到URL功能 · When redirecting to URL is enabled, the redirect protocol and redirect port must be specified：当开启重定向到URL功能，必须指定重定向协议和端口 · Only HTTPS-type listeners support enabling mutual authentication configuration：仅HTTPS类型的监听器支持开启双向认证功能 · A UDP-type listener doesn't support enabling TCP source IP transparent transmission：UDP类型的监听器不支持开启TCP源IP透传功能 · Listeners with port number 0 do not support enabling TCP source IP transparent transmission：端口号为0的监听器不支持开启TCP源IP透传功能 · The TCP option number ranges from 6, 7, 9 to 18, 22 to 254：TCP选项类型编号取值范围为<6-7,9-18,22-254> · When the LB SNAT type is default SNAT pool address, to create a CGSR-type load balancer with SNAT enabled, make sure the address pool contains addresses that have the same IP version as the load balancer：当LB用户源地址转换使用默认SNAT地址池模式，创建开启SNAT的服务网关类型LB服务时，该地址池里必须有与LB服务协议一致的地址 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_LISTENER_OP |
|
日志内容 |
Deleted listener $1. |
|
参数解释 |
$1：监听器名称 |
|
举例 |
Deleted listener listener60. |
|
日志说明 |
用户进行了删除监听器的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复中 · The service has not been found：服务未启动 · The configuration item doesn't exist：配置项不存在 · The configuration item is in use：配置项正在被使用 · Failed to delete the configuration item：删除配置项失败 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_LBPOLICY_OP |
|
日志内容 |
Created policy $1. |
|
参数解释 |
$1：策略配置信息 |
|
举例 |
Created policy ID: 0f4777cb-724d-4298-b2dd-1700f4183399 Name: l7test Description: Tenant ID: ffffffff-0000-0000-0000-000000000001 Listener ID: eeed4b2e-f42c-4f03-b9f0-acfe2cfea565 Priority: 1 Actions: { Type: Redirect to URL Redirect URL: aaa } Admin state up: true. |
|
日志说明 |
用户进行了创建策略的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Invalid JSON format：无效的JSON格式 · The configuration item already exists：配置项已存在 · Configuration recovery is in progress：配置正在恢复中 · The service has not been found：服务未启动 · The configuration item doesn't exist：配置项不存在 · The tenant ID must be specified：租户ID必须被指定 · The actions is required：actions不能为空 · The listener ID is required：监听器ID不能为空 · The tenant specified for the configuration item doesn't exist：配置项指定的租户不存在 · Invalid URL：无效的URL · The listener specified for the policy doesn't exist：策略引用的监听器不存在 · The tenant IDs for the specified listener and the specified pool are different：指定监听器和指定实服务器组的租户ID不匹配 · A listener can be bound to a maximum of 5000 policies：与同一监听器绑定的策略最多为5000个 · The VIP for the specified pool is different from the VIP used by the listener bound with the policy：指定的实服务器组关联的虚服务器与策略绑定的监听器引用的虚服务器不一致 · The vRouters for the pool and the listener are different for the policy：指定的实服务器组与策略绑定的监听器所属的虚拟路由器不一致 · The policy can be bound only to the listener whose protocol type is HTTP or HTTPS：策略只能绑定协议类型为HTTP或HTTPS的监听器 · A policy can contain only one action：一个策略中只能配置一个动作 · The tenant IDs for the specified pool and the policy are different：指定实服务器组和该策略的租户ID不一致 · The action type is required：动作类型不能为空 · When the action type is REDIRECT_TO_POOL, you must specify the pool ID：当动作类型为重定向到实服务器组时，必须指定实服务器组ID · When the action type is REDIRECT_TO_URL, you must specify the URL：当动作类型为重定向到URL时，必须指定URL · The specified pool doesn't exist：指定的实服务器组不存在 · No VIP is specified for the listener：指定的监听器没有关联虚服务器 · The tenant IDs for the specified listener and the policy are different：指定监听器和该策略的租户ID不匹配 · The policy is required：策略不能为空 · Failed to add the configuration item：添加配置项失败 · You have no privilege to perform this operation：用户无权限执行此操作 · In EVPN networking environment, listeners using the same pool cannot be bound to multiple service-chain load balancers：EVPN组网环境下，绑定到不同服务链负载均衡器的监听器不能指定相同的实服务组 |
|
关键字 |
UPDATE_LBPOLICY_OP |
|
日志内容 |
Updated policy $1. |
|
参数解释 |
$1：策略配置信息 |
|
举例 |
Updated policy ID: 0f4777cb-724d-4298-b2dd-1700f4183399 Name: l7test Description: Admin state up: true Tenant ID: ffffffff-0000-0000-0000-000000000001 Listener ID: eeed4b2e-f42c-4f03-b9f0-acfe2cfea565 Priority: 1 Actions: { Type: Redirect to URL Redirect URL: aaa }. |
|
日志说明 |
用户进行了修改策略的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Invalid JSON format：无效的JSON格式 · Configuration recovery is in progress：配置正在恢复中 · The service has not been found：服务未启动 · The configuration item doesn't exist：配置项不存在 · The ID can not be modified：ID不允许被修改 · The tenant ID can not be modified：租户ID不允许被修改 · The listener ID can not be modified：监听器ID不允许被修改 · The pool specified for the configuration item doesn't exist：配置项指定的实服务器组不存在 · Failed to modify the configuration item：修改配置项失败 · Invalid URL：无效的URL · The tenant IDs for the specified listener and the specified pool are different：指定监听器和指定实服务器组的租户ID不匹配 · The VIP for the specified pool is different from the VIP used by the listener bound with the policy：指定的实服务器组关联的虚服务器与策略绑定的监听器引用的虚服务器不同 · The vRouters for the pool and the listener are different for the policy：指定的实服务器组与策略绑定的监听器所属的虚拟路由器不同 · The actions is required：actions不能为空 · The policy name is read only：策略名称为只读字段 · A policy can contain only one action：一个策略中只能配置一个动作 · The tenant IDs for the specified pool and the policy are different：指定实服务器组和该策略的租户ID不一致 · The action type is required：动作类型不能为空 · When the action type is REDIRECT_TO_POOL, you must specify the pool ID：当动作类型为重定向到实服务器组时，必须指定实服务器组ID · When the action type is REDIRECT_TO_URL, you must specify the URL：当动作类型为重定向到URL时，必须指定URL · No VIP is specified for the listener：指定的监听器没有关联虚服务器 · Failed to modify the configuration item：修改配置项失败 · You have no privilege to perform this operation：用户无权限执行此操作 · In EVPN networking environment, listeners using the same pool cannot be bound to multiple service-chain load balancers：EVPN组网环境下，绑定到不同服务链负载均衡器的监听器不能指定相同的实服务组 |
|
关键字 |
DELETE_LBPOLICY_OP |
|
日志内容 |
Deleted policy $1. |
|
参数解释 |
$1：策略名称 |
|
举例 |
Deleted policy L7test. |
|
日志说明 |
用户进行了删除策略的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · The configuration item doesn't exist：配置项不存在 · The service has not been found：服务未启动 · Failed to delete the configuration item：删除配置项失败 · Configuration recovery is in progress：配置正在恢复中 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_LBRULE_OP |
|
日志内容 |
Created rule $1. |
|
参数解释 |
$1：规则配置信息 |
|
举例 |
Created rule ID: 3390118d-b9b7-4a3b-8f7c-d9d240bbf881 Type: HTTP cookie Invert: false Match item: aabb Match type: Equal to Match value: html Policy ID: 3ecfaa2e-9086-4c1c-ac8f-0c8d08e66fcc Admin state up: true. |
|
日志说明 |
用户进行了创建规则的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复中 · The service has not been found：服务未启动 · Invalid JSON format：无效的JSON格式 · The configuration item already exists：配置项已存在 · The policy ID is required：策略ID不能为空 · The type is required：规则类型不能为空 · The key is required：key不能为空 · The value is required：value不能为空 · The compare_type is required：compare_type不能为空 · The policy doesn't exist：指定的策略不存在 · When the type is FILE_TYPE, the match type only can be EQUAL_TO：当规则类型为文件类型时，匹配方式仅支持等于 · Invalid value：无效的value · Invalid key：无效的key · The key is not required when the type is FILE_TYPE, HOST_NAME, or PATH：当规则类型为文件类型、主机名或URI路径时，无需指定key · A policy can contain a maximum of 256 rules：一个策略中最多可配置256条规则 · Invalid compare_type：无效的compare_type · Invalid type：无效的规则类型 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_LBRULE_OP |
|
日志内容 |
Updated rule $1. |
|
参数解释 |
$1：规则的内容 |
|
举例 |
Updated rule ID: 3390118d-b9b7-4a3b-8f7c-d9d240bbf881 Type: HTTP cookie Invert: False Match item: aabb Match type: Equal to Match value: html Policy ID: 3ecfaa2e-9086-4c1c-ac8f-0c8d08e66fcc Admin state up: true. |
|
日志说明 |
用户进行了修改规则的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复中 · The service has not been found：服务未启动 · Invalid JSON format：无效的JSON格式 · The ID can not be modified：ID不允许被修改 · The configuration item doesn't exist：配置项不存在 · When the type is FILE_TYPE, the match type only can be EQUAL_TO：当规则类型为文件类型时，匹配方式仅支持等于 · Invalid value：无效的value · Invalid key：无效的key · The key is not required when the type is FILE_TYPE, HOST_NAME, or PATH：当规则类型为文件类型、主机名或URI路径时，无需指定匹配项 · Failed to modify the configuration item：修改配置项失败 · The policy ID is read only：策略ID为只读字段 · The key is required：key不能为空 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_LBRULE_OP |
|
日志内容 |
Deleted rule $1. |
|
参数解释 |
$1：规则的ID |
|
举例 |
Deleted rule 3390118d-b9b7-4a3b-8f7c-d9d240bbf881. |
|
日志说明 |
用户进行了删除规则的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复中 · The service has not been found：服务未启动 · The configuration item doesn't exist：配置项不存在 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_POOL_OP |
|
日志内容 |
Created pool $1. |
|
参数解释 |
$1：实服务器组配置信息 |
|
举例 |
Created pool ID: 5ba4d32a-8373-423c-b1e9-78de52f0733d Tenant ID: 00000000-0000-0000-0000-000000000000 Name: pool70 Description: pool 70 LB method: ROUND_ROBIN Session persistence type: SOURCE_IP Session persistence cookie name: Admin state up: true Status: DOWN Version: LB_V2. |
|
日志说明 |
用户进行了创建实服务器组的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复中 · The service has not been found：服务未启动 · The configuration item already exists：配置项已存在 · The tenant specified for the configuration item doesn't exist：配置项指定的租户不存在 · The tenant IDs for the pool and the specified listener are different：实服务器组和指定监听器的租户ID不一致 · The listener ID must be specified：监听器ID不能为空 · The protocol types of the pool and the specified listener are different：该实服务器组的协议类型和指定监听器的协议类型不同 · All listeners bound with the pool must specify the same VIP：该实服务器组绑定的所有监听器必须引用同一虚服务器 · The vRouters for the specified listeners and the pool are different：指定的监听器与该实服务器组所属的虚拟路由器不同 · Invalid listener IDs exist in the listener list：监听器列表中存在无效的监听器ID · The status is read only：状态为只读字段 · The tenant name is read only：租户名称为只读字段 · The subnet name is read only：子网名称为只读字段 · The health monitor name is read only：健康检测名称为只读字段 · The member ID is read only：成员ID为只读字段 · The tenant ID must be specified：租户ID必须被指定 · The tenant specified for the configuration item doesn't exist：配置项指定的租户不存在 · The specified subnet doesn't exist：指定的子网不存在 · The tenant IDs for the pool and the specified subnet are different：实服务器组和指定子网的租户ID不一致 · The health monitor specified for the pool doesn't exist：实服务器组指定的健康检测不存在 · The tenant IDs for the pool and the specified health monitor are different：实服务器组和指定健康检测的租户ID不一致 · Failed to add the configuration item：添加配置项失败 · The subnet id is read only：子网ID为只读字段 · The members of pool are read only：实服务器组的成员为只读字段 · The member ip is read only：成员IP为只读字段 · The method of pool must be specified：实服务器组的负载均衡方式必须被指定 · Only an IPv4 subnet can be specified：仅支持指定IPv4子网 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_POOL_OP |
|
日志内容 |
Updated pool $1. |
|
参数解释 |
$1：实服务器组配置信息 |
|
举例 |
负载均衡V1版本的日志如下（仅REST API支持） Updated pool ID: 5ba4d32a-8373-423c-b1e9-78de52f0733d Tenant ID: 00000000-0000-0000-0000-000000000000 Name: pool70 Description: pool 70 LB method: ROUND_ROBIN Session persistence type: SOURCE_IP Session persistence cookie name Admin state up: true Status: DOWN Version: LB_V2. 负载均衡V2版本的日志如下 Updated pool ID: 5ba4d32a-8373-423c-b1e9-78de52f0733d Tenant ID: 00000000-0000-0000-0000-000000000000 Name: pool70 Description: pool 70 LB method: ROUND_ROBIN Session persistence type: SOURCE_IP Session persistence cookie name Admin state up: true Status: DOWN Version: LB_V2. |
|
日志说明 |
用户进行了修改实服务器组的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复中 · The service has not been found：服务未启动 · The configuration item doesn't exist：配置项不存在 · All listeners bound with the pool must specify the same VIP：该实服务器组绑定的所有监听器必须引用同一虚服务器 · The VIP for the specified pool is different from the VIP used by the listeners：指定的监听器引用的虚服务器与该实服务器组关联的虚服务器不同 · The vRouters for the specified listeners and the pool are different：指定的监听器与该实服务器组所属的虚拟路由器不同 · The tenant IDs for the pool and the specified listener are different：实服务器组和指定监听器的租户ID不一致 · The listener ID is read-only：监听器ID为只读字段 · Invalid listener IDs exist in the listener list：监听器列表中存在无效的监听器ID · The status is read only：状态为只读字段 · The members of pool are read only：实服务器组的成员为只读字段 · The tenant name is read only：租户名称为只读字段 · The subnet name is read only：子网名称为只读字段 · The health monitor name is read only：健康检测名称为只读字段 · The member ID is read only：成员ID为只读字段 · The ID can not be modified：ID不允许被修改 · The tenant ID can not be modified：租户ID不允许被修改 · The listener id can not be modified：监听器ID不允许被修改 · The health monitor specified for the pool doesn't exist：实服务器组指定的健康检测不存在 · The tenant IDs for the pool and the specified health monitor are different：实服务器组和指定健康检测的租户ID不一致 · Failed to modify the configuration item：修改配置项失败 · The subnet id can not be modified：子网ID不允许被修改 · The specified subnet doesn't exist：指定的子网不存在 · The tenant IDs for the pool and the specified subnet are different：实服务器组和指定子网的租户ID不一致 · The member ip is read only：成员IP为只读字段 · The members of pool are read only：实服务器组的成员为只读字段 · The subnet id is read only：子网ID为只读字段 · The pool is used by the SERVICE_CHAIN mode load balancer, and it must contain member IP addresses on the specified subnet：该实服务器组已被SERVICE_CHAIN模式的负载均衡器引用，指定的子网必须包含其成员IP地址 · Only an IPv4 subnet can be specified：仅支持指定IPv4子网 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_POOL_OP |
|
日志内容 |
Deleted pool $1. |
|
参数解释 |
$1：实服务器组名称 |
|
举例 |
Deleted pool pool70. |
|
日志说明 |
用户进行了删除实服务器组的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复中 · The service has not been found：服务未启动 · The configuration item doesn't exist：配置项不存在 · The configuration item is in use：配置项正在被使用 · Failed to delete the configuration item：删除配置项失败 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_VIP_OP |
|
日志内容 |
Created VIP $1. |
|
参数解释 |
$1：虚服务器配置信息 |
|
举例 |
Created VIP ID: ab8121f1-65b6-4709-8153-43695b83a187 Tenant ID: 00000000-0000-0000-0000-000000000000 Name: vip60 Description: Protocol: HTTPS Pool ID: e5c2996e-36d6-4e80-aa2b-deedac360468 Port ID: 09296b20-1f8d-4b17-9862-b920884e34dc Address: 60.0.0.90 Protocol port: 6 Connection limit: 0 Session persistence type: SOURCE_IP Session persistence cookie name: Admin state up: true Status: DOWN. |
|
日志说明 |
用户进行了创建负载均衡V1的虚服务器的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复中 · The service has not been found：服务未启动 · The configuration item already exists：配置项已存在 · The tenant specified for the configuration item doesn't exist：配置项指定的租户不存在 · The protocol types of the VIP and the pool are different：虚服务器的协议类型和实服务器组的协议类型不匹配 · The pool is already used by another VIP：实服务器组已被其它虚服务器引用 · The tenant IDs for the VIP and the specified pool are different：虚服务器和指定实服务器组的租户ID不匹配 · The specified subnet doesn't exist：指定的子网不存在 · The VIP address conflicts with the IP address of a vPort or the subnetsof the VIP address and member IP addresses belong to different virtual link layer networks：虚服务器IP地址与虚拟端口IP地址冲突，或虚服务器IP地址所在子网与成员IP地址所在子网不属于同一虚拟链路层网络 · The pool specified for the VIP doesn't exist：虚服务器引用的实服务器组不存在 · The IP address is already used by another VIP：IP地址已被其它虚服务器使用 · The VIP address must belong to the subnet of the pool：虚服务器的IP地址必须属于实服务器组的子网 · The IP address doesn't belong to the subnet：IP地址不在子网范围内 · The pool used by the VIP is used by the SERVICE_CHAIN type load balancers and cannot be enabled with SNAT：该虚服务器引用的实服务器组已被SERVICE_CHAIN模式的负载均衡器引用，不允许开启源IP地址转换功能 · The tenant ID must be specified：租户ID必须被指定 · Only an IPv4 subnet can be specified：仅支持指定IPv4子网 · The server pool has been referenced by a load balancer, and the IP address and port number cannot both be the same as the IP address and port number of a virtual server associated with any other server pool referenced by the load balancer：指定的实服务器组已被负载均衡器引用，IP地址和端口号不能与负载均衡器关联的其他实服务器组下的虚服务器的IP地址和端口号相同 · A virtual server of the TCP type or bound with a TCP-type server farm doesn't support enabling XFF：协议类型为TCP或绑定TCP类型实服务器组的虚服务器不支持开启XFF功能 · Only virtual servers of the TCP type or bound with a TCP-type server farm support SSL certificate and SSL key configuration：协议类型为TCP或绑定TCP类型实服务器组的虚服务器才能配置SSL证书和SSL密钥 · To enable XFF for a virtual server whose protocol is HTTPS, you must specify SSL settings first：当虚服务器协议类型为HTTPS时，需先指定SSL相关配置才能开启XFF功能 · The SSL certificate and SSL key must be both specified or both left unspecified：SSL证书和SSL密钥必须同时指定或不指定 · Invalid SSL certificate：无效的SSL证书 · Invalid SSL key：无效的SSL密钥 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_VIP_OP |
|
日志内容 |
Updated VIP $1. |
|
参数解释 |
$1：虚服务器配置信息 |
|
举例 |
Updated VIP ID: ab8121f1-65b6-4709-8153-43695b83a187 Tenant ID: 00000000-0000-0000-0000-000000000000 Name: vip60 Description: Protocol: HTTPS Pool ID: e5c2996e-36d6-4e80-aa2b-deedac360468 Port ID: 09296b20-1f8d-4b17-9862-b920884e34dc Address: 60.0.0.90 Protocol port: 6 Connection limit: 0 Session persistence type: SOURCE_IP Session persistence cookie name: Admin state up: true Status: DOWN. |
|
日志说明 |
用户进行了修改负载均衡V1的虚服务器的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复中 · The service has not been found：服务未启动 · The configuration item doesn't exist：配置项不存在 · The protocol types of the VIP and the pool are different：虚服务器的协议类型和实服务器组的协议类型不匹配 · The pool is already used by another VIP：实服务器组已被其它虚服务器引用 · The tenant IDs for the VIP and the specified pool are different：虚服务器和指定实服务器组的租户ID不匹配 · The pool specified for the VIP doesn't exist：虚服务器引用的实服务器组不存在 · The IP address is already used by another VIP：IP地址已被其它虚服务器使用 · The pool used by the VIP is used by the SERVICE_CHAIN type load balancers and cannot be enabled with SNAT：该虚服务器引用的实服务器组已被SERVICE_CHAIN模式的负载均衡器引用，不允许开启源IP地址转换功能 · Only an IPv4 subnet can be specified：仅支持指定IPv4子网 · The server pool has been referenced by a load balancer, and the IP address and port number cannot both be the same as the IP address and port number of a virtual server associated with any other server pool referenced by the load balancer：指定的实服务器组已被负载均衡器引用，IP地址和端口号不能与负载均衡器关联的其他实服务器组下的虚服务器的IP地址和端口号相同 · A virtual server of the TCP type or bound with a TCP-type server farm doesn't support enabling XFF：协议类型为TCP或绑定TCP类型实服务器组的虚服务器不支持开启XFF功能 · Only virtual servers of the TCP type or bound with a TCP-type server farm support SSL certificate and SSL key configuration：协议类型为TCP或绑定TCP类型实服务器组的虚服务器才能配置SSL证书和SSL密钥 · To enable XFF for a virtual server whose protocol is HTTPS, you must specify SSL settings first：当虚服务器协议类型为HTTPS时，需先指定SSL相关配置才能开启XFF功能 · The SSL certificate and SSL key must be both specified or both left unspecified：SSL证书和SSL密钥必须同时指定或不指定 · Invalid SSL certificate：无效的SSL证书 · Invalid SSL key：无效的SSL密钥 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_VIP_OP |
|
日志内容 |
Deleted VIP $1. |
|
参数解释 |
$1：虚服务器名称 |
|
举例 |
Deleted VIP vip60. |
|
日志说明 |
用户进行了删除负载均衡V1的虚服务器的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复中 · The service has not been found：服务未启动 · The configuration item doesn't exist：配置项不存在 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_MEMBER_OP |
|
日志内容 |
Created member $1. |
|
参数解释 |
$1：实服务器组成员配置信息 |
|
举例 |
Created member ID: 9f421f95-5772-4127-b8e4-47dfe5a7d43e Tenant ID: 00000000-0000-0000-0000-000000000000 Name: 9f421f95-5772-4127-b8e4-47dfe5a7d43e Pool ID: f8472b01-3aa2-4a6c-a292-80e7872ceca3 Subnet ID: f8472b01-3aa2-4a6c-a292-80e7872cec11 Address: 60.0.0.11 Protocol port: 2 Weight: 1 Admin state up: true Status: DOWN. |
|
日志说明 |
用户进行了创建实服务器组成员的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复中 · The service has not been found：服务未启动 · The configuration item already exists：配置项已存在 · The tenant specified for the configuration item doesn't exist：配置项指定的租户不存在 · The pool specified for the member doesn't exist：实服务器引用的实服务器组不存在 · The tenant IDs for the member and the specified pool are different：成员和指定实服务器组的租户ID不匹配 · The VIP address must belong to the subnet of the pool：虚服务器的IP地址必须属于实服务器组的子网 · The IP address is already used by another VIP：IP地址已被其它虚服务器使用 · The vRouters for the member and the VIP are different：成员所在子网关联的虚拟路由器和虚服务器所在子网关联的虚拟路由器不同 · The subnet for the VIP and member are different：虚服务器与成员的子网不匹配 · The specified subnet doesn't exist：指定的子网不存在 · The tenant IDs for the member and the specified subnet are different：指定的子网所属租户与成员所属租户不一致 · The vRouters for the pool and the subnet are different for the member：该成员所在子网关联的虚拟路由器与实服务器组关联的虚拟路由器不同 · The status is read only：状态为只读字段 · The tenant name is read only：租户名称为只读字段 · The pool name is read only：实服务器组名称为只读字段 · The tenant ID must be specified：租户ID必须被指定 · The pool ID must be specified：实服务器组ID必须被指定 · The address must be specified：地址必须被指定 · The IP address doesn't belong to the subnet：指定的IP地址不在子网网段内 · Failed to add the configuration item：添加配置项失败 · The subnet ID is required if no listeners are bound to the pool：当指定的实服务器组未绑定监听器时，子网ID不能为空 · Only an IPv4 subnet can be specified：仅支持指定IPv4子网 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_MEMBER_OP |
|
日志内容 |
Updated member $1. |
|
参数解释 |
$1：实服务器配置信息 |
|
举例 |
Updated member ID: 9f421f95-5772-4127-b8e4-47dfe5a7d43e Tenant ID: 00000000-0000-0000-0000-000000000000 Name: 9f421f95-5772-4127-b8e4-47dfe5a7d43e Pool ID: f8472b01-3aa2-4a6c-a292-80e7872ceca3 Subnet ID: f8472b01-3aa2-4a6c-a292-80e7872cec11 Address: 60.0.0.11 Protocol port: 2 Weight: 1 Admin state up: true Status: DOWN. |
|
日志说明 |
用户进行了修改实服务器的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复中 · The service has not been found：服务未启动 · The configuration item doesn't exist：配置项不存在 · The pool specified for the member doesn't exist：实服务器引用的实服务器组不存在 · The tenant IDs for the member and the specified pool are different：成员和指定实服务器组的租户ID不匹配 · The VIP address must belong to the subnet of the pool：虚服务器的IP地址必须属于实服务器组的子网 · The pool ID is read-only：实服务器组ID为只读字段 · The subnet for the VIP and member are different：虚服务器与成员的子网不匹配 · The specified subnet doesn't exist：指定的子网不存在 · The member and the subnet belong to different tenants：指定的子网所属租户与成员所属租户不一致 · The vRouters for the pool and the subnet are different for the member：该成员所在子网关联的虚拟路由器与实服务器组关联的虚拟路由器不同 · Invalid JSON format：无效的JSON串格式 · The status is read only：状态为只读字段 · The tenant name is read only：租户名称为只读字段 · The pool name is read only：实服务器组名称为只读字段 · The ID can not be modified：ID不允许被修改 · The tenant ID can not be modified：租户ID不允许被修改 · The address can not be modified：地址不允许被修改 · The subnet id can not be modified：子网ID不允许被修改 · The protocol port can not be modified：协议端口不允许被修改 · The subnet for the VIP and member are different：虚服务器与成员的子网不一致 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
DELETE_MEMBER_OP |
|
|
日志内容 |
Deleted member $1. |
|
参数解释 |
$1：实服务器配置信息 |
|
举例 |
Deleted member IP address: 204.1.1.11 Protocol port: 223 Pool ID: f8472b01-3aa2-4a6c-a292-80e7872ceca3. |
|
日志说明 |
用户进行了删除实服务器的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复中 · The service has not been found：服务未启动 · The configuration item doesn't exist：配置项不存在 · Failed to delete the configuration item：删除配置项失败 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_HEALTH_MONITOR_OP |
|
日志内容 |
Created health monitor $1. |
|
参数解释 |
$1：健康检测配置信息 |
|
举例 |
Created health monitor ID: 0711c857-2729-41f2-b213-dc4e715bf9bd Tenant ID: 00000000-0000-0000-0000-000000000000 Pool ID: 00000000-0000-0000-0000-000000000010 Name: hm Type: HTTPS Timeout: 11 Delay: 10 Max retries: 12 HTTP method: GET URL path: / Expected codes: 233 Status: DOWN. |
|
日志说明 |
用户进行了创建健康检测的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复中 · The service has not been found：服务未启动 · The configuration item already exists：配置项已存在 · The tenant specified for the configuration item doesn't exist：配置项指定的租户不存在 · The tenant IDs for the health monitor and the specified pool are different：健康监测和指定实服务器组的租户ID不匹配 · The expected_data_type, expected_data and expected_offset parameters are available only when the monitor type is HTTP or HTTPS：仅检测类型为HTTP或HTTPS时支持配置期望应答内容的格式，期望应答内容和应答报文偏移量 · Invalid JSON format：无效的JSON串格式 · The status is read only：状态为只读字段 · The tenant name is read only：租户名称为只读字段 · The tenant ID must be specified：租户ID必须被指定 · The type must be specified：类型必须被指定 · The delay must be specified：检测间隔必须被指定 · The timeout must be specified：超时时间必须被指定 · The max retries must be specified：连续检测失败次数必须被指定 · The method can not be specified when type is not http or https：当类型不是HTTP或者HTTPS的时候，操作方式不能被指定 · The url path can not be specified when type is not http or https：当类型不是HTTP或者HTTPS的时候，url路径不能被指定 · The monitor port parameter is available only when the monitor type is TCP or UDP ：当健康检测类型是TCP或UDP的时候，检测端口参数是可用的 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_HEALTH_MONITOR_OP |
|
日志内容 |
Updated health monitor $1. |
|
参数解释 |
$1：健康检测配置信息 |
|
举例 |
Updated health monitor ID: 0711c857-2729-41f2-b213-dc4e715bf9bd Tenant ID: 00000000-0000-0000-0000-000000000000 Pool ID: 00000000-0000-0000-0000-000000000010 Name: hm Type: HTTPS Timeout: 11 Delay: 10 Max retries: 12 HTTP method: GET URL path: / Expected codes: 233 Status: DOWN. |
|
日志说明 |
用户进行了修改健康检测的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复中 · The service has not been found：服务未启动 · The configuration item doesn't exist：配置项不存在 · The expected_data_type, expected_data and expected_offset parameters are available only when the monitor type is HTTP or HTTPS：仅检测类型为HTTP或HTTPS时支持配置期望应答内容的格式，期望应答内容和应答报文偏移量 · Invalid JSON format：无效的JSON串格式 · The status is read only：状态为只读字段 · The tenant name is read only：租户名称为只读字段 · The ID can not be modified：ID不允许被修改 · The tenant ID can not be modified：租户ID不允许被修改 · The type can not be modified：类型不允许被修改 · The method can not be specified when type is not http or https：当类型不是HTTP或者HTTPS的时候，操作方式不能被指定 · The url path can not be specified when type is not http or https：当类型不是HTTP或者HTTPS的时候，url路径不能被指定 · The monitor port parameter is available only when the monitor type is TCP or UDP：当健康检测类型是TCP或UDP的时候，检测端口参数是可用的 · The monitor port exceed limit：检测端口超过上限 · The timeout exceed limit：超时时间超过上限 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_HEALTH_MONITOR_OP |
|
日志内容 |
Deleted health monitor $1. |
|
参数解释 |
$1：健康检测名称 |
|
举例 |
Deleted health monitor hm. |
|
日志说明 |
用户进行了删除健康检测的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复中 · The service has not been found：服务未启动 · The configuration item doesn't exist：配置项不存在 · The configuration item is in use：配置项正在被使用 · Failed to delete the configuration item：删除配置项失败 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
BIND_HEALTH_MONITOR_OP |
|
日志内容 |
Bound health monitor: $1 |
|
参数解释 |
$1：健康检测UUID |
|
举例 |
Bound health monitor: ID: [380e1f64-4722-4039-8aec-af1643d10be6] |
|
日志说明 |
用户进行了为指定实服务器组关联一个健康检测的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · Invalid JSON format：无效的JSON格式 · The service is disabled：服务未启动 · Configuration recovery is in progress：配置正在恢复中 · The controller is not the active leader：该控制组件不是主Leader · The configuration item doesn't exist：配置项不存在 · The health monitor specified for the pool doesn't exist：实服务器组引用的健康检测不存在 · The tenant IDs for the pool and the specified health monitor are different：实服务器组和指定健康检测的租户ID不匹配 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UNBIND_HEALTH_MONITOR_OP |
|
日志内容 |
Unbound health monitor: $1 |
|
参数解释 |
$1：健康检测UUID |
|
举例 |
Unbound health monitor: ID: [380e1f64-4722-4039-8aec-af1643d10be6] |
|
日志说明 |
用户进行了为指定实服务器组解除关联健康检测的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · Invalid JSON format：无效的JSON格式 · The service is disabled：服务未启动 · Configuration recovery is in progress：配置正在恢复中 · The controller is not the active leader：该控制组件不是主Leader · The configuration item doesn't exist：配置项不存在 · The health monitor specified for the pool doesn't exist：实服务器组引用的健康检测不存在 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_SNATPOOL_OP |
|
日志内容 |
Created SNAT pool $1. |
|
参数解释 |
$1：SNAT Pool地址池配置信息 |
|
举例 |
Created SNAT pool ID : 3007d55a-9d8e-43dd-b9e6-64823728f1cc Name : DEFAULT_LB_SNAT_POOL Description : DEFAULT_LB_SNAT_POOL NeedBind : false IpPoolList: [ 1.1.1.1, 2.2.2.2-2.2.2.5] Ipv6PoolList: [ 1::1, 2::2-2::5]. |
|
日志说明 |
用户进行了创建SNAT Pool地址池的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复中 · The service has not been found：服务未启动 · The configuration item already exists：配置项已存在 · Failed to add the configuration item：添加配置项失败 · The default SNAT address pool already exists：默认SNAT地址池已存在 · The number of addresses in the SNAT address pool exceed the limit. You can add a maximum of 16 IPv4 addresses and a maximum of 16 IPv6 addresses to the pool： SNAT地址数量超出上限，IPv4和IPv6地址段上限皆为16 · Invalid IP address：无效的IP地址 · The start IP address is higher than the end IP address：地址池起始IP地址大于结束IP地址 · A same IP address already exists in the address pool：指定地址与地址池的其它IP地址重叠 · When the LB SNAT type is default SNAT pool address, make sure the address pool contains addresses that have the same IP version as CGSR-type load balancers with SNAT enabled：当LB用户源地址转换使用默认SNAT地址池模式时，该地址池里必须有与开启SNAT的服务网关类型LB服务协议一致的地址 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_SNATPOOL_OP |
|
日志内容 |
Updated SNAT pool $1. |
|
参数解释 |
$1：SNAT Pool地址池配置信息 |
|
举例 |
Updated SNAT pool ID : 3007d55a-9d8e-43dd-b9e6-64823728f1cc Name : DEFAULT_LB_SNAT_POOL Description : DEFAULT_LB_SNAT_POOL NeedBind : false IpPoolList: [ 2.2.2.2-2.2.2.5, 3.3.3.3] Ipv6PoolList: [ 2::2-2::5, 3::3]. |
|
日志说明 |
用户进行了修改SNAT Pool地址池的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复中 · The service has not been found：服务未启动 · The configuration item doesn't exist：配置项不存在 · The ID can not be modified：ID不允许被修改 · Failed to modify the configuration item：修改配置项失败 · The default SNAT address pool already exists：默认SNAT地址池已存在 · The number of addresses in the SNAT address pool exceed the limit. You can add a maximum of 16 IPv4 addresses and a maximum of 16 IPv6 addresses to the pool： SNAT地址数量超出上限，IPv4和IPv6地址段上限皆为16 · Invalid IP address：无效的IP地址 · The start IP address is higher than the end IP address：地址池起始IP地址大于结束IP地址 · A same IP address already exists in the address pool：指定地址与地址池的其它IP地址重叠 · When the LB SNAT type is default SNAT pool address, make sure the address pool contains addresses that have the same IP version as CGSR-type load balancers with SNAT enabled：当LB用户源地址转换使用默认SNAT地址池模式时，该地址池里必须有与开启SNAT的服务网关类型LB服务协议一致的地址 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_SNATPOOL_OP |
|
日志内容 |
Deleted SNAT pool $1. |
|
参数解释 |
$1：SNAT Pool地址池名称 |
|
举例 |
Deleted SNAT pool snatpoolname. |
|
日志说明 |
用户进行了删除负载均衡器的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · The operation requires the administrator privilege：您需要管理员权限才能执行此操作 · Configuration recovery is in progress：配置正在恢复中 · The service has not been found：服务未启动 · The configuration item doesn't exist：配置项不存在 · When the LB SNAT type is default SNAT pool address, make sure the address pool contains addresses that have the same IP version as CGSR-type load balancers with SNAT enabled：当LB用户源地址转换使用默认SNAT地址池模式时，该地址池里必须有与开启SNAT的服务网关类型LB服务协议一致的地址 · The configuration item is in use：配置项正在被使用 · Failed to delete the configuration item：删除配置项失败 · You have no privilege to perform this operation：用户无权限执行此操作 |
本节介绍Mice Elephant Flow模块输出的操作日志信息。
|
关键字 |
CREATE_MICE_ELEPHANT_FLOW_OP |
|
日志内容 |
Created MiceElephantFlow policy: $1 |
|
参数解释 |
$1：大小流调度策略信息 |
|
举例 |
Created MiceElephantFlow policy MiceElephantFlow[ id=Id[value=3218141b-0627-448b-92a3-22fc6daf4860], name=1, deviceIpList=[192.168.67.207], elephantFlowRate=1, rateUnit=KBPS, elephantFlowSize=3, sizeUnit=BYTES, precedenceMode=DROP, precedenceValue=2, agileBufferEnable=false ] |
|
日志说明 |
用户进行了增加大小流调度策略的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The name is required and cannot exceed 255 characters：名称必选并且长度不能超过255个字符 · Please specify the deviceips parameter：交换设备IP地址不能为空 · Please specify an integer in the range of 1 to 1000 for the elephant_flow_rate paramter：大流速率为整形且取值范围为1～1000 · Please specify the rate_unit parameter, which can be kbps, mbps, or gbps：大流速率单位不能为空且取值仅支持kbps、mbps和gbps · You must specify the size_unit parameter if the elephant_flow_size parameter is specified：大流尺寸不为空时，尺寸单位必填 · Please specify an integer in the range of 1 to 1000 for the elephant_flow_size parameter：大流尺寸为整形且取值范围为1～1000 · Please specify the precedence_mode parameter, which can be drop, dot1p, or local：优先级模式不能为空且取值必须为丢弃优先级、dot1p和本地优先级 · Please specify an integer for the precedence_value parameter：优先级取值不能为空且必须为整数 · When the value for the precedence_mode paramter is drop, the value range for the precedence_value parameter is 0 to 2：当优先级模式为丢弃时，优先级取值范围为0～2的整数 · When the value for the precedence_mode parameter is dot1p or local, the value range for the precedence_value parameter is 0 to 7：当优先级模式为dot1p或本地优先级时，优先级取值范围为0～7的整数 · The switching device does not exist：指定的交换设备不存在 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · The switching device has been bound to another elephant flow policy：指定的交换设备已应用了大小流调度策略 · The UUID already exists：重复的UUID · Invalid IP address：无效的IP地址 · The adaptive buffer function is only allowed to be enabled when the priority mode of large flow actions is local priority：大流动作优先级模式为本地优先级，才允许使能自适应缓存功能 |
|
关键字 |
UPDATE_MICE_ELEPHANT_FLOW_OP |
|
日志内容 |
Updated elephant/mice flow policy: $1 |
|
参数解释 |
$1：大小流调度策略信息 |
|
举例 |
Updated MiceElephantFlow policy MiceElephantFlow [ id=Id[value=3218141b-0627-448b-92a3-22fc6daf4860], name=1, deviceIpList=[192.168.67.207, 192.168.67.204], elephantFlowRate=1, rateUnit=KBPS, elephantFlowSize=3, sizeUnit=BYTES, precedenceMode=DROP, precedenceValue=2, agileBufferEnable=true ]. |
|
日志说明 |
用户进行了修改大小流调度策略的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The configuration item does not exist：指定的配置项不存在 · The name is required and cannot exceed 255 characters：名称必选并且长度不能超过255个字符 · Please specify the deviceips parameter：交换设备IP地址不能为空 · Please specify an integer in the range of 1 to 1000 for the elephant_flow_rate paramter：大流速率为整形且取值范围为1～1000 · Please specify the rate_unit parameter, which can be kbps, mbps, or gbps：大流速率单位不能为空且取值仅支持kbps、mbps和gbps · You must specify the size_unit parameter if the elephant_flow_size parameter is specified：大流尺寸不为空时，尺寸单位必填 · Please specify an integer in the range of 1 to 1000 for the elephant_flow_size parameter：大流尺寸为整形且取值范围为1～1000 · Please specify the precedence_mode parameter, which can be drop, dot1p, or local：优先级模式不能为空且取值必须为丢弃优先级、dot1p和本地优先级 · Please specify an integer for the precedence_value parameter：优先级取值不能为空且必须为整数 · When the value for the precedence_mode paramter is drop, the value range for the precedence_value parameter is 0 to 2：当优先级模式为丢弃时，优先级取值范围为0～2的整数 · When the value for the precedence_mode parameter is dot1p or local, the value range for the precedence_value parameter is 0 to 7：当优先级模式为dot1p或本地优先级时，优先级取值范围为0～7的整数 · The switching device does not exist：指定的交换设备不存在 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · The switching device has been bound to another elephant flow policy：指定的交换设备已应用了大小流调度策略 · Invalid IP address：无效的IP地址 · The adaptive buffer function is only allowed to be enabled when the priority mode of large flow actions is local priority：大流动作优先级模式为本地优先级，才允许使能自适应缓存功能 |
|
关键字 |
DELETE_MICE_ELEPHANT_FLOW_OP |
|
日志内容 |
Deleted MiceElephantFlow policy $1. |
|
参数解释 |
$1：大小流调度策略信息 |
|
举例 |
Deleted MiceElephantFlow policy Id[value=8404ff24-cb2e-49bd-87c6-cad4b6f688cc]. |
|
日志说明 |
用户进行了删除大小流调度策略的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The configuration item does not exist：指定的配置项不存在 · The switching device does not exist：指定的交换设备不存在 · Southbound devices at the following IP addresses were disconnected: {IP addresses} ：{IP地址集合}对应的南向设备已断开连接 |
本节介绍NBAC模块输出的操作日志。
|
关键字 |
CREATE_APPLICATION_DESCIRIPTION_OP |
|
日志内容 |
Created application description $1 |
|
参数解释 |
$1：应用策略信息 |
|
举例 |
Created application description appDescs: [{ ID: 57367f82-7098-47c7-91bd-04ddae3ccca0 Name: 应用策略1 VRouter name: router100 Policy name: Deny All Auto router link: false Exception rules: [{ Number: 1 IP version: 4 Protocol: IP Source name: net10 Destination name: net11 Action: redirect Direction: both Service chain name: graph0001 }] }]. |
|
日志说明 |
用户进行了创建应用策略的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The application description name already exists：应用策略名称已存在 · The tenant ID must be specified：租户ID不能为空 · The source EPG is required：源EPG不能为空 · The destination EPG is required：目的EPG不能为空 · The source EPG does not exist：源EPG不存在 · The destination EPG does not exist：目的EPG不存在 · The source EPG type is required：源EPG类型不能为空 · The destination EPG type is required：目的EPG类型不能为空 · Invalid source EPG type：无效的源EPG类型 · Invalid destination EPG type：无效的目的EPG类型 · The policy ID does not exist：指定的策略ID不存在 · The specified policy does not match the policy type：指定的策略与其类型不匹配 · The policy direction is required：策略方向不能为空 · The policy direction is invalid：无效的策略方向 · The exception policy does not exist：例外策略不存在 · The policy type is invalid：无效的策略类型 · An application description cannot be bound to an exception policy that contains rules：应用策略无法绑定已有规则的例外策略 · The exception policy has been bound to another application description：例外策略已绑定其他应用策略 · The application description ID already exists：应用策略ID已存在 · The parameter is required：未指定参数 · The parameter can't be modified：参数不支持修改 · Internal server error：未知错误 · Request parameter error：请求参数错误 · This operation is not allowed：没有访问权限 · This operation has no permissions：禁止访问 · This operation is conflict：操作冲突 · Unknown error code：未知的错误码 · The service is disabled：服务未启动 · You have no privilege to perform this operation：用户无权限执行此操作 · You cannot specify a vRouter generated upon PBR service chain creation：PBR类型的虚拟路由器不能被引用 · When the action is redirect, make sure the source or destination EPG is not Any or Ungrouped：当动作为重定向时，源和目的EPG不能为Any或未分组EPG · Invalid IP version：无效的IP版本 · Please specify a direction：方向不能为空 · Invalid direction：无效的方向 · When the action is redirect, make sure both directions are specified：当动作为重定向时，方向必须为双向 · When the action is permit or deny, make sure the service chain UUID is not specified：当动作是Permit或者Deny时，服务链UUID必须为空 · You cannot specify an EPG automatically generated upon service path creation：服务路径自动生成的EPG不能被引用 · Make sure the exception rule and service path use the same IP version：例外规则的IP版本和服务路径的IP版本必须一致 · Check the vSubnets of the vRouter bound to the source EPG. Make sure none of them contains the vPort IP addresses of any service nodes：源EPG所属虚拟路由器下的子网不能包含服务节点对应的虚拟端口IP地址 · Check the vSubnets of the vRouter bound to the destination EPG. Make sure none of them contains the vPort IP addresses of any service nodes：目的EPG所属虚拟路由器下的子网不能包含服务节点对应的虚拟端口IP地址 · Make sure the source EPG and service instances in the service path are bound to different vRouters：源EPG绑定的虚拟路由器不能与服务实例绑定的虚拟路由器相同 · Make sure the destination EPG and service instances in the service path are bound to different vRouters：目的EPG绑定的虚拟路由器不能与服务实例绑定的虚拟路由器相同 · When the action is redirect, you cannot specify an external EPG as the source or destination EPG：当动作为Redirect时，源和目的EPG不能为External类型 · Cannot configure IPv4 or IPv4&IPv6 application policies for the vRouter, because the vRouter has been configured with service chains：同一虚拟路由器下不可同时配置服务链和IPv4或IPv4&IPv6的应用策略 · The routers of application description and source EPG are different：应用策略与源EPG不属于同一个虚拟路由器 · The routers of application description and destination EPG are different：应用策略与目的EPG不属于同一个虚拟路由器 · The vRouter bound to the application policy has only one gateway member or external subnet. Make sure the EPGs in the exception rule use the single gateway deployment mode：该应用策略绑定的虚拟路由器有一个出口网关成员或一个外网子网时，例外规则使用的EPG出口模式必须为单出口 · The vRouter bound to the application policy has two gateway members or two external subnets. Make sure the EPGs in the exception rule use the primary/backup gateway deployment mode：该应用策略绑定的虚拟路由器有两个出口网关成员或两个外网子网时，例外规则使用的EPG出口模式必须为主备出口 · Please specify two and only two external subnets for the external EPG. This is required because the EPG uses primary/backup gateway deployment mode and the edge device to the external network in the vRouter for the EPG is the border device：主备出口模式下，如果虚拟路由器的出外网设备是边界设备，External类型的EPG必须指定两个外网子网 · Please specify one and only one external subnets for the external EPG. This is required because the EPG uses single gateway deployment mode and the edge device to the external network in the vRouter for the EPG is the border device：单出口模式下，如果虚拟路由器的出外网设备是边界设备，External类型的EPG必须指定一个外网子网 · The destination EPG cannot be external when the service type is PBRLoadbalance：当指定PBRLoadbalance类型的服务实例时，目的EPG不能为External · The types of the source and destination EPGs cannot both be external：源和目的EPG不能同时为External · The external EPG is specified in multiple application policies. Make sure the application policies use the same default action setting：External类型的EPG被多个应用策略引用时，默认动作必须一致 · When the protocol type is IP, ICMP, ICMPv6, or ICMP&ICMPv6, you cannot specify source ports or destination ports：当协议类型是IP，ICMP，ICMPv6，ICMP&ICMPv6时，不能设置源端口和目的端口 · When the protocol type is TCP or UDP, you must specify at least one source port or one destination port：当协议类型是TCP、UDP时，源端口和目的端口至少指定一个 · The value for the source_port field cannot exceed 255 characters：源端口的字段长度最长255个字符 · The value for the destination_port field cannot exceed 255 characters：目的端口的字段长度最长255个字符 · Invalid source ports exist：源端口不合法 · Duplicate source ports exist：指定的源端口已经被使用 · Invalid destination ports exist：目的端口不合法 · Duplicate destination ports exist：指定的目的端口已经被使用 · Invalid parameters：无效的配置参数 · When the source and destination EPGs and source and destination ports are the same, make sure the service path contains only a one-arm service node：当源EPG、源端口和目的EPG、目的端口相同时，服务路径的服务节点必须为单臂连接模式 · When the source and destination EPGs and source and destination ports are different, make sure the service path does not contain any one-arm service nodes：当源EPG、源端口和目的EPG、目的端口不同时，服务路径的服务节点不能为单臂连接模式 · When the source and destination EPGs and source and destination ports are the same, make sure the action is redirect：当源EPG、源端口和目的EPG、目的端口相同时，动作必须为Redirect · Without the source and destination ports specified, the exception rule cannot use the same set of source EPG, destination EPG, or protocol setting as an existing exception rule：当无需指定源和目的端口号时，源EPG、目的EPG和协议不能存在重复 · Invalid protocol type：无效的协议类型 · The protocol type does not match the IP version：IP版本和协议类型不匹配 · The specified service path does not exist：指定的服务路径不存在 · When multiple service nodes exist in the service path, make sure all service nodes use the two-arm connection mode：当服务路径存在多个服务节点时，服务节点的连接模式必须都为双臂 · When the source or destination EPG is an external EPG, the service path can contain only two-arm service nodes：当源EPG或目的EPG为External类型时，服务路径的服务节点必须为双臂连接模式 · The service path has a third-party service node with IPsec settings. You can specify the service path only in exception rules that contain an external source or destination EPG：指定服务路径已使用配置了IPsec功能的第三方服务节点，只能应用于源或目的EPG为External类型的例外规则 · The service path has a third-party service node with IPsec or NAT settings and an external EPG. You cannot add LB service nodes between them：服务路径中，已配置IPsec或NAT功能的第三方服务节点与External类型的EPG之间不允许存在LB类型的服务节点 · Make sure the service node and the resource access template use the same connection mode：服务节点的连接模式和资源接入模板的连接模式必须相同 · A resource is required to be bound with each PBRFirewall or PBRLoadbalance service instance：每个PBR类型（PBRFirewall和PBRLoadbalance）的服务实例均需绑定资源 · The resource access template corresponding to the PBRFirewall or PBRLoadbalance service instance has configuration errors or does not exist：PBR类型（PBRFirewall和PBRLoadbalance）的服务实例对应的资源接入模板配置错误或不存在 · The vRouter must be a normal vRouter：指定的虚拟路由器只能选择NORMAL类型 · The specified tenant doesn't exist：指定的租户不存在 · The specified vRouter doesn't exist：指定的虚拟路由器不存在 · The router is not matching tenant：指定的虚拟路由器不属于指定租户 · The edge device to the external network for the vRouter is a border device. Please specify external subnets for the external EPG：指定虚拟路由器的外网出口设备为边界设备，External类型的EPG的外部网络子网不能为空 · Please specify the vrouter_id or router_list field, but not both：vrouter_id和router_list字段有且只能存在一个 · Please specify a rule for the inter-vRouter EPG policy：跨虚拟路由器EPG间策略规则不能为空 · You cannot specify Any or Ungrouped EPGs or external EPG members in the inter-vRouter EPG policy：跨虚拟路由器EPG间策略引用的EPG不能为Any或未分组EPG且EPG类型不能为External · Please specify the router_list field for inter-vRouter EPG policy：跨虚拟路由器EPG间策略的router_list不能为空 · The router_list field for the inter-vRouter EPG policy can contain only two vRouters：跨虚拟路由器EPG间策略的router_list只能有两个元素 · You cannot specify the same vRouter for both the source and destination EPGs in an inter-vRouter EPG policy：跨虚拟路由器EPG间策略引用的源和目的EPG的虚拟路由器不能相同 · You cannot specify an EPG as both the source EPG and destination EPG in the inter-vRouter EPG policy：跨虚拟路由器EPG间策略引用的EPG源和目的不能相同 · The value for the auto_router_link field is invalid：auto_router_link 字段填入了非法值 · You cannot specify the policy_id field for the inter-vRouter EPG policy：跨虚拟路由器EPG间策略不可填入策略ID · You cannot specify the auto_router_link field for an intra-vRouter policy：虚拟路由器内策略不能指定auto_router_link字段 · Southbound devices at the following IP addresses were disconnected: {%s}：{IP地址集合}对应的南向设备已断开连接 · Make sure the subnets attached to the vRouters bound to the source and destination EPGs do not overlap：源EPG所属虚拟路由器下的子网不能和目的EPG所属虚拟路由器下的子网网段重叠 · Make sure the source or destination EPG members do not overlap with any subnets of the vRouter bound to the service node：源或目的EPG的成员与服务节点绑定的虚拟路由器下的子网存在重叠 · Failed to create a vRouter link in the application policy, because the associated vRouters have already established a vRouter link of the normal type：应用策略生成的虚拟路由器连接与已存在的虚拟路由器连接冲突 · The method for service chain traffic routing must be null or pbr in an intra-vRouter policy：虚拟路由器内策略的服务链导流方式的取值只能为null或pbr · The method for service chain traffic routing must be null, pbr, or static_route in an inter-vRouter EPG policy：跨虚拟路由器EPG间策略的服务链导流方式取值只能为null、pbr或static_route · The method for service chain traffic routing must be null, pbr, or static_route in an inter-tenant EPG policy：跨租户EPG间策略的服务链导流方式取值只能为null、pbr或static_route · You cannot specify an EPG for both an intra-vRouter policy and a service chain whose traffic routing method is static route：一个EPG不能同时在以下两种场景中使用：1、虚拟路由器内策略。2、引流方式为静态路由的服务链 · If the method for service chain traffic routing is static route, you cannot specify the same EPG for both a redirection rule and a permit or deny rule：服务链引流方式为静态路由时，重定向规则和黑白名单不能使用相同的EPG · If the method for service chain traffic routing is static route, the service path specified in a redirection exception rule can contain only one node, and the node type must be FW, LB, third-party FW, or third-party LB：服务链引流方式为静态路由时，重定向例外规则引用的服务路径只能包含一个节点，并且节点类型为FW、LB、第三方FW或第三方LB · You cannot specify the same pair of vRouters in both of the following settings:1.Inter-tenant or inter-vRouter EPG policy whose method for service chain traffic routing is static route.2.vRouter link of the normal type：两个虚拟路由器不能同时在以下两种场景中使用： 1、服务链引流方式为静态路由，创建跨租户或者跨虚拟路由器EPG间策略。2、创建Normal的虚拟路由器连接 · In an application policy that uses static route-based service chain traffic routing, to use an EPG in multiple rules, make sure that: 1. The EPG is specified as either the source or destination EPG in the rules. 2. The rules are specified in the same service path：在一个应用策略内，若服务链引流方式选择静态路由，一个EPG被不同规则使用时必须作为同一源/目的EPG，且服务路径必须相同 · In an inter-vRouter EPG policy or inter-tenant EPG policy, make sure the source (or destination) EPG members do not conflict with any subnets or members of the vRouter associated with the destination (source) EPG：跨虚拟路由器EPG间策略或跨租户EPG间策略中，源（目的）EPG成员与目的（源）EPG所属虚拟路由器下的子网和EPG成员不能存在重复 · The static route issued by the application policy that uses static route-based service chain traffic routing conflicts with the routes learned by the created vRouter links：引流方式为静态路由的应用策略下发的静态路由和创建虚拟路由器连接学习到的路由存在冲突 · You cannot specify a service path enabled with the bypass feature in an application policy that uses static route-based service chain traffic routing：静态路由引流的应用策略不能引用已开启旁路功能的服务路径 · When the application policy uses static route-based service chain traffic routing, make sure the protocol for the redirect rule is IP：应用策略使用静态路由引流时，重定向规则的协议类型必须为IP · The Advertise EPG to Peer vRouter option has been enabled for another application policy. Turning on this option might result in repeated configuration deployment：已存在应用策略开启自动同步EPG到对端开关，下发的配置重复 · In two application policies that use static route-based service chain traffic routing and have the same vRouter specified, if the EPGs associated with the remaining two vRouters have overlapping subnets, make sure that: 1. The EPGs are specified as either the source or destination EPGs in the application policies. 2. The EPGs are specified in the same service path：服务链引流方式选择静态路由时，两个不同的应用策略选择同一虚拟路由器，且另外两个虚拟路由器的EPG存在子网重叠，则这两个EPG必须均作为源（目的）EPG，且服务路径必须相同 · For the same router, you cannot configure both an intra-vRouter policy and an inter-vRouter or inter-tenant EPG policy that uses static route-based service chain traffic routing：一个虚拟路由器不能同时配置虚拟路由器内策略和使用静态路由引流的跨虚拟路由器/跨租户EPG间策略 · In the rules of an inter-vRouter EPG policy or inter-tenant EPG policy, make sure the EPG members of one vRouter do not conflict with any members of any EPGs for the other vRouter：跨虚拟路由器EPG间策略或跨租户EPG间策略中，虚拟路由器1（虚拟路由器2）下被规则引用的EPG成员与虚拟路由器2（虚拟路由器1）下的EPG成员存在重叠 · In the rules of an inter-vRouter EPG policy or inter-tenant EPG policy, make sure the EPG members of both vRouters do not contain conflicting subnets：跨虚拟路由器EPG间策略或跨租户EPG间策略中，两个虚拟路由器下被规则引用的EPG 成员之间存在子网重叠 · In the rules of an inter-vRouter EPG policy or inter-tenant EPG policy, make sure the EPG members of one vRouter do not conflict with any subnets of the other vRouter：跨虚拟路由器EPG间策略或跨租户EPG间策略中，虚拟路由器1（虚拟路由器2）下被规则引用的EPG成员与虚拟路由器2（虚拟路由器1）下的子网存在子网重叠 · The specified rule is the same as an existing rule：指定的规则已存在 · The vRouter specified for the source EPG does not exist：源EPG指定的虚拟路由器不存在 · The vRouter specified for the destination EPG does not exist：目的EPG指定的虚拟路由器不存在 · The static route issued by the application policy that uses static route-based service chain traffic routing conflicts with the routes learned by the created vRouter links：引流方式为静态路由的应用策略下发的静态路由和创建虚拟路由器连接学习到的路由存在冲突 · A service chain ID can be specified only when the action is redirect：仅当动作为重定向时，才允许指定服务链ID · The application description id has already been existed：应用策略ID已存在 · When the action is redirect, the service chain ID cannot be empty：当动作为重定向时，服务链ID不允许为空 · The name is required：名称不能为空 · The name cannot exceed 255 characters：名称最长255个字符 · The rule ID already exists：指定的规则ID已经被使用 · On a vRouter, members of an EPG overlap with those of another EPG, because the EPG is automatically generated upon service path creation and is advertised to the peer vRouter by default：指定服务路径自动生成的EPG因默认开启自动同步EPG到对端，使得该EPG成员与同一虚拟路由器下的其他EPG成员存在重复 · You can specify only the redirect action for the rule exceptions in an application policy in which a transit vRouter is specified：使用transit类型虚拟路由器的应用策略，例外规则仅支持Redirect动作 · You can specify only the static route-based service chain traffic routing method for an application policy in which a transit vRouter is specified：使用transit类型虚拟路由器的应用策略，引流方式仅支持静态路由 · Make sure the two vRouters specified in an inter-tenant or inter-vRouter application policy are both the transit or normal type：跨租户/跨虚拟路由器应用策略选择的虚拟路由器仅支持选择两个transit类型或者两个normal类型 · The standby service path can only be used for the cross-virtual router/cross-tenant EPG policy that uses the static route of the transit type virtual router to divert traffic：备服务路径只能用于使用transit类型虚拟路由器的静态路由引流的跨虚拟路由器/跨租户EPG间策略 · Please select a service path of the same tenant：请选择同租户下的服务路径 · Please select a service path of a tenant bound to the vRouter：请选择虚拟路由器所属租户下的服务路径 · Application policy configuration is not supported, because the nodes in the controller cluster are synchronizing EPG service chain configuration：控制组件集群节点间正在同步微分段服务链配置，不允许配置应用策略 · The vRouter already has an application policy：该虚拟路由器已被其它应用策略使用 · The rule number is out of range：例外规则序号超出范围 · If you specify two transit vRouters in an application policy, you can configure one primary service path, one secondary service path, or both for the source and destination EPGs in a rule of that application policy：使用transit类型虚拟路由器的应用策略，规则中指定的源和目的EPG之间只能配置一条主服务路径、一条备服务路径或一主一备 |
|
关键字 |
UPDATE_APPLICATION_DESCIRIPTION_OP |
|
日志内容 |
Updated application description $1. |
|
参数解释 |
$1：应用策略信息 |
|
举例 |
Updated application description { ID: 57367f82-7098-47c7-91bd-04ddae3ccca0 Name: 应用策略00001 VRouter name: router100 Policy name: Deny All Auto router link: false Exception rules: [{ Number: 1 IP version: 4 Protocol: IP Source name: net10 Destination name: net11 Action: redirect Direction: both Service chain name: graph0001 }] }. |
|
日志说明 |
用户进行了修改应用策略的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The policy cannot be modified：策略不允许修改 · The policy cannot be edited：策略不允许修改 · Policy direction cannot be changed：策略方向不允许修改 · The tenant cannot be modified：租户不允许修改 · The vRouter cannot be modified：虚拟路由器不允许修改 · The vRouter ID is required：虚拟路由器ID不能为空 · The source EPG is required：源EPG不能为空 · The destination EPG is required：目的EPG不能为空 · The source EPG does not exist：源EPG不存在 · The destination EPG does not exist：目的EPG不存在 · The source EPG type is required：源EPG类型不能为空 · An exception rule already exists for the source and destination EPG pair：源和目的EPG与已存在的例外规则不能相同 · The specified application description does not exist：指定的应用策略不存在 · The policy direction is required：策略方向不能为空 · The policy direction is invalid：无效的策略方向 · The specified exception policy ID does not exist：例外策略ID不存在 · The exception policy has been bound to another application description：例外策略已绑定其他应用策略 · The parameter is required：未指定参数 · The parameter can't be modified：参数不支持修改 · Internal server error：未知错误 · Request parameter error：请求参数错误 · This operation is not allowed：没有访问权限 · This operation has no permissions：禁止访问 · This operation is conflict：操作冲突 · Unknown error code：未知的错误码 · The service is disabled：服务未启动 · You have no privilege to perform this operation：用户无权限执行此操作 · You cannot specify a vRouter generated upon PBR service chain creation：PBR类型的虚拟路由器不能被引用 · When the action is redirect, make sure the source or destination EPG is not Any or Ungrouped：当动作为重定向时，源和目的EPG不能为Any或未分组EPG · Invalid IP version：无效的IP版本 · Invalid direction：无效的方向 · When the action is redirect, make sure both directions are specified：当动作为重定向时，方向必须为双向 · When the action is permit or deny, make sure the service chain UUID is not specified：当动作是Permit或者Deny时，服务链UUID必须为空 · You cannot specify an EPG automatically generated upon service path creation：服务路径自动生成的EPG不能被引用 · Make sure the exception rule and service path use the same IP version：例外规则的IP版本和服务路径的IP版本必须一致 · Check the vSubnets of the vRouter bound to the source EPG. Make sure none of them contains the vPort IP addresses of any service nodes：源EPG所属虚拟路由器下的子网不能包含服务节点对应的虚拟端口IP地址 · Check the vSubnets of the vRouter bound to the destination EPG. Make sure none of them contains the vPort IP addresses of any service nodes：目的EPG所属虚拟路由器下的子网不能包含服务节点对应的虚拟端口IP地址 · Make sure the source EPG and service instances in the service path are bound to different vRouters：源EPG绑定的虚拟路由器不能与服务实例绑定的虚拟路由器相同 · Make sure the destination EPG and service instances in the service path are bound to different vRouters：目的EPG绑定的虚拟路由器不能与服务实例绑定的虚拟路由器相同 · When the source and destination EPGs are the same, make sure the action is redirect：源EPG和目的EPG相同时，动作必须为Redirect · When the action is redirect, you cannot specify an external EPG as the source or destination EPG：当动作为Redirect时，源和目的EPG不能为External类型 · When the source and destination EPGs are the same, make sure the service chain contains only a one-arm service node：当源EPG和目的EPG相同时，服务链的服务节点必须为单臂连接模式 · When the source and destination EPGs are different, make sure the service chain does not contain any one-arm service nodes：当源EPG和目的EPG不同时，服务链的服务节点不能为单臂连接模式 · Cannot configure IPv4 or IPv4&IPv6 application policies for the vRouter, because the vRouter has been configured with service chains：同一虚拟路由器下不可同时配置服务链和IPv4或IPv4&IPv6的应用策略 · The routers of application description and source EPG are different：应用策略与源EPG不属于同一个虚拟路由器 · The routers of application description and destination EPG are different：应用策略与目的EPG不属于同一个虚拟路由器 · The vRouter bound to the application policy has only one gateway member or external subnet. Make sure the EPGs in the exception rule use the single gateway deployment mode：该应用策略绑定的虚拟路由器有一个出口网关成员或一个外网子网时，例外规则使用的EPG出口模式必须为单出口 · The vRouter bound to the application policy has two gateway members or two external subnets. Make sure the EPGs in the exception rule use the primary/backup gateway deployment mode：该应用策略绑定的虚拟路由器有两个出口网关成员或两个外网子网时，例外规则使用的EPG出口模式必须为主备出口 · Please specify two and only two external subnets for the external EPG. This is required because the EPG uses primary/backup gateway deployment mode and the edge device to the external network in the vRouter for the EPG is the border device：主备出口模式下，如果虚拟路由器的出外网设备是边界设备，External类型的EPG必须指定两个外网子网 · Please specify one and only one external subnets for the external EPG. This is required because the EPG uses single gateway deployment mode and the edge device to the external network in the vRouter for the EPG is the border device：单出口模式下，如果虚拟路由器的出外网设备是边界设备，External类型的EPG必须指定一个外网子网 · The destination EPG cannot be external when the service type is PBRLoadbalance：当指定PBRLoadbalance类型的服务实例时，目的EPG不能为External · The types of the source and destination EPGs cannot both be external：源和目的EPG不能同时为External · The external EPG is specified in multiple application policies. Make sure the application policies use the same default action setting：External类型的EPG被多个应用策略引用时，默认动作必须一致 · When multiple service nodes exist in the service path, make sure all service nodes use the two-arm connection mode：当服务路径存在多个服务节点时，服务节点的连接模式必须都为双臂 · When the source or destination EPG is an external EPG, the service path can contain only two-arm service nodes：当源EPG或目的EPG为External类型时，服务路径的服务节点必须为双臂连接模式 · The service path has a third-party service node with IPsec settings. You can specify the service path only in exception rules that contain an external source or destination EPG：指定服务路径已使用配置了IPsec功能的第三方服务节点，只能应用于源或目的EPG为External类型的例外规则 · The service path has a third-party service node with IPsec or NAT settings and an external EPG. You cannot add LB service nodes between them：服务路径中，已配置IPsec或NAT功能的第三方服务节点与External类型的EPG之间不允许存在LB类型的服务节点 · Make sure the service node and the resource access template use the same connection mode：服务节点的连接模式和资源接入模板的连接模式必须相同 · A resource is required to be bound with each PBRFirewall or PBRLoadbalance service instance：每个PBR类型（PBRFirewall和PBRLoadbalance）的服务实例均需绑定资源 · The resource access template corresponding to the PBRFirewall or PBRLoadbalance service instance has configuration errors or does not exist：PBR类型（PBRFirewall和PBRLoadbalance）的服务实例对应的资源接入模板配置错误或不存在 · The vRouter must be a normal vRouter：指定的虚拟路由器只能选择NORMAL类型 · Without the source and destination ports specified, the exception rule cannot use the same set of source EPG, destination EPG, or protocol setting as an existing exception rule：当无需指定源和目的端口号时，源EPG、目的EPG和协议不能存在重复 · The edge device to the external network for the vRouter is a border device. Please specify external subnets for the external EPG：指定虚拟路由器的外网出口设备为边界设备，External类型的EPG的外部网络子网不能为空 · Please specify the vrouter_id or router_list field, but not both：vrouter_id和router_list字段有且只能存在一个 · Please specify a rule for the inter-vRouter EPG policy：跨虚拟路由器EPG间策略规则不能为空 · You cannot specify Any or Ungrouped EPGs or external EPG members in the inter-vRouter EPG policy：跨虚拟路由器EPG间策略引用的EPG不能为Any或未分组EPG且EPG类型不能为External · Please specify the router_list field for inter-vRouter EPG policy：跨虚拟路由器EPG间策略的router_list不能为空 · The router_list field for the inter-vRouter EPG policy can contain only two vRouters：跨虚拟路由器EPG间策略的router_list只能有两个元素 · You cannot specify the same vRouter for both the source and destination EPGs in an inter-vRouter EPG policy：跨虚拟路由器EPG间策略引用的源和目的EPG的虚拟路由器不能相同 · You cannot specify an EPG as both the source EPG and destination EPG in the inter-vRouter EPG policy：跨虚拟路由器EPG间策略引用的EPG源和目的不能相同 · The value for the auto_router_link field is invalid：auto_router_link 字段填入了非法值 · You cannot specify the policy_id field for the inter-vRouter EPG policy：跨虚拟路由器EPG间策略不可填入策略ID · You cannot specify the auto_router_link field for an intra-vRouter policy：虚拟路由器内策略不能指定auto_router_link字段 · Southbound devices at the following IP addresses were disconnected: {%s}：{IP地址集合}对应的南向设备已断开连接 · Make sure the subnets attached to the vRouters bound to the source and destination EPGs do not overlap：源EPG所属虚拟路由器下的子网不能和目的EPG所属虚拟路由器下的子网网段重叠 · Make sure the source or destination EPG members do not overlap with any subnets of the vRouter bound to the service node：源或目的EPG的成员与服务节点绑定的虚拟路由器下的子网存在重叠 · Failed to create a vRouter link in the application policy, because the associated vRouters have already established a vRouter link of the normal type：应用策略生成的虚拟路由器连接与已存在的虚拟路由器连接冲突 · The method for service chain traffic routing must be null or pbr in an intra-vRouter policy：虚拟路由器内策略的服务链导流方式的取值只能为null或pbr · The method for service chain traffic routing must be null, pbr, or static_route in an inter-vRouter EPG policy：跨虚拟路由器EPG间策略的服务链导流方式取值只能为null、pbr或static_route · The method for service chain traffic routing must be null, pbr, or static_route in an inter-tenant EPG policy：跨租户EPG间策略的服务链导流方式取值只能为null、pbr或static_route · You cannot specify an EPG for both an intra-vRouter policy and a service chain whose traffic routing method is static route：一个EPG不能同时在以下两种场景中使用：1、虚拟路由器内策略。2、引流方式为静态路由的服务链 · If the method for service chain traffic routing is static route, you cannot specify the same EPG for both a redirection rule and a permit or deny rule：服务链引流方式为静态路由时，重定向规则和黑白名单不能使用相同的EPG · If the method for service chain traffic routing is static route, the service path specified in a redirection exception rule can contain only one node, and the node type must be FW, LB, third-party FW, or third-party LB：服务链引流方式为静态路由时，重定向例外规则引用的服务路径只能包含一个节点，并且节点类型为FW、LB、第三方FW或第三方LB · You cannot specify the same pair of vRouters in both of the following settings:1.Inter-tenant or inter-vRouter EPG policy whose method for service chain traffic routing is static route.2.vRouter link of the normal type：两个虚拟路由器不能同时在以下两种场景中使用： 1、服务链引流方式为静态路由，创建跨租户或者跨虚拟路由器EPG间策略。2、创建Normal的虚拟路由器连接 · In an application policy that uses static route-based service chain traffic routing, to use an EPG in multiple rules, make sure that: 1. The EPG is specified as either the source or destination EPG in the rules. 2. The rules are specified in the same service path：在一个应用策略内，若服务链引流方式选择静态路由，一个EPG被不同规则使用时必须作为同一源/目的EPG，且服务路径必须相同 · In an inter-vRouter EPG policy or inter-tenant EPG policy, make sure the source (or destination) EPG members do not conflict with any subnets or members of the vRouter associated with the destination (source) EPG：跨虚拟路由器EPG间策略或跨租户EPG间策略中，源（目的）EPG成员与目的（源）EPG所属虚拟路由器下的子网和EPG成员不能存在重复 · The static route issued by the application policy that uses static route-based service chain traffic routing conflicts with the routes learned by the created vRouter links：引流方式为静态路由的应用策略下发的静态路由和创建虚拟路由器连接学习到的路由存在冲突 · You cannot specify a service path enabled with the bypass feature in an application policy that uses static route-based service chain traffic routing：静态路由引流的应用策略不能引用已开启旁路功能的服务路径 · When the application policy uses static route-based service chain traffic routing, make sure the protocol for the redirect rule is IP：应用策略使用静态路由引流时，重定向规则的协议类型必须为IP · The Advertise EPG to Peer vRouter option has been enabled for another application policy. Turning on this option might result in repeated configuration deployment：已存在应用策略开启自动同步EPG到对端开关，下发的配置重复 · In two application policies that use static route-based service chain traffic routing and have the same vRouter specified, if the EPGs associated with the remaining two vRouters have overlapping subnets, make sure that: 1. The EPGs are specified as either the source or destination EPGs in the application policies. 2. The EPGs are specified in the same service path：服务链引流方式选择静态路由时，两个不同的应用策略选择同一虚拟路由器，且另外两个虚拟路由器的EPG存在子网重叠，则这两个EPG必须均作为源（目的）EPG，且服务路径必须相同 · For the same router, you cannot configure both an intra-vRouter policy and an inter-vRouter or inter-tenant EPG policy that uses static route-based service chain traffic routing：一个虚拟路由器不能同时配置虚拟路由器内策略和使用静态路由引流的跨虚拟路由器/跨租户EPG间策略 · In the rules of an inter-vRouter EPG policy or inter-tenant EPG policy, make sure the EPG members of one vRouter do not conflict with any members of any EPGs for the other vRouter：跨虚拟路由器EPG间策略或跨租户EPG间策略中，虚拟路由器1（虚拟路由器2）下被规则引用的EPG成员与虚拟路由器2（虚拟路由器1）下的EPG成员存在重叠 · In the rules of an inter-vRouter EPG policy or inter-tenant EPG policy, make sure the EPG members of both vRouters do not contain conflicting subnets：跨虚拟路由器EPG间策略或跨租户EPG间策略中，两个虚拟路由器下被规则引用的EPG 成员之间存在子网重叠 · In the rules of an inter-vRouter EPG policy or inter-tenant EPG policy, make sure the EPG members of one vRouter do not conflict with any subnets of the other vRouter：跨虚拟路由器EPG间策略或跨租户EPG间策略中，虚拟路由器1（虚拟路由器2）下被规则引用的EPG成员与虚拟路由器2（虚拟路由器1）下的子网存在子网重叠 · The vRouter specified for the source EPG does not exist：源EPG指定的虚拟路由器不存在 · The vRouter specified for the destination EPG does not exist：目的EPG指定的虚拟路由器不存在 · The static route issued by the application policy that uses static route-based service chain traffic routing conflicts with the routes learned by the created vRouter links：引流方式为静态路由的应用策略下发的静态路由和创建虚拟路由器连接学习到的路由存在冲突 · A service chain ID can be specified only when the action is redirect：仅当动作为重定向时，才允许指定服务链ID · The application description id has already been existed：应用策略ID已存在 · When the action is redirect, the service chain ID cannot be empty：当动作为重定向时，服务链ID不允许为空 · The rule ID already exists：指定的规则ID已经被使用 · On a vRouter, members of an EPG overlap with those of another EPG, because the EPG is automatically generated upon service path creation and is advertised to the peer vRouter by default：指定服务路径自动生成的EPG因默认开启自动同步EPG到对端，使得该EPG成员与同一虚拟路由器下的其他EPG成员存在重复 · You can specify only the redirect action for the rule exceptions in an application policy in which a transit vRouter is specified：使用transit类型虚拟路由器的应用策略，例外规则仅支持Redirect动作 · You can specify only the static route-based service chain traffic routing method for an application policy in which a transit vRouter is specified：使用transit类型虚拟路由器的应用策略，引流方式仅支持静态路由 · The standby service path can only be used for the cross-virtual router/cross-tenant EPG policy that uses the static route of the transit type virtual router to divert traffic：备服务路径只能用于使用transit类型虚拟路由器的静态路由引流的跨虚拟路由器/跨租户EPG间策略 · Please select a service path of the same tenant：请选择同租户下的服务路径 · Please select a service path of a tenant bound to the vRouter：请选择虚拟路由器所属租户下的服务路径 · Application policy configuration is not supported, because the nodes in the controller cluster are synchronizing EPG service chain configuration：控制组件集群节点间正在同步微分段服务链配置，不允许配置应用策略 · The rule number is out of range：例外规则序号超出范围 · If you specify two transit vRouters in an application policy, you can configure one primary service path, one secondary service path, or both for the source and destination EPGs in a rule of that application policy：使用transit类型虚拟路由器的应用策略，规则中指定的源和目的EPG之间只能配置一条主服务路径、一条备服务路径或一主一备 |
|
关键字 |
DELETE_APPLICATION_DESCIRIPTION_OP |
|
日志内容 |
Deleted application description $1. |
|
参数解释 |
$1：应用策略信息 |
|
举例 |
Deleted application description { ID: 57367f82-7098-47c7-91bd-04ddae3ccca0 Name: 应用策略00001 VRouter name: router100 Policy name: Deny All Exception rules: [{ Number: 1 IP version: 4 Protocol: IP Source name: net10 Destination name: net11 Action: redirect Direction: both Service chain name: graph0001 }] }. |
|
日志说明 |
用户进行了删除应用策略的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The specified application description does not exist：指定的应用策略不存在 · The parameter is required：未指定参数 · The parameter can't be modified：参数不支持修改 · Internal server error：未知错误 · Request parameter error：请求参数错误 · This operation is not allowed：没有访问权限 · This operation has no permissions：禁止访问 · This operation is conflict：操作冲突 · Unknown error code：未知的错误码 · The service is disabled：服务未启动 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {%s}：{IP地址集合}对应的南向设备已断开连接 · Application policy configuration is not supported, because the nodes in the controller cluster are synchronizing EPG service chain configuration：控制组件集群节点间正在同步微分段服务链配置，不允许配置应用策略 |
|
关键字 |
CREATE_EPG_OP |
|
日志内容 |
Created EPG $1 |
|
参数解释 |
$1：EPG的信息 |
|
举例 |
Created EPG ID: a89144ff-08cc-4239-b646-ffbf80ec0459 Name: net10 Router ID: 5867a83a-cb23-47cb-95ee-99ef5aea135f Base: type: NETWORK Networks: [ 4d6c0aa4-15bf-497c-bea7-6d137317ee0f] Intra isolation: false Flag: false |
|
日志说明 |
用户进行了创建EPG的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service is disabled：服务未启动 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The tenant name cannot be modified：租户名称不允许修改 · The tenant ID is required：租户ID不能为空 · The vRouter ID is required：虚拟路由器ID不能为空 · The name is required：名称不能为空 · The EPG type is required：EPG类型不能为空 · Invalid JSON format：无效的JSON格式 · The name cannot exceed 255 characters：名称最长255个字符 · The network ID already exists：网络ID已存在 · The subnet ID already exist：子网ID已存在 · The external CIDR already exists：外网IP地址已存在 · Invalid external network address：无效的外网IP · Duplicated external network addresses exist：外网IP不能重复 · The terminal IP address already exists：IP地址已存在 · Invalid IP address：无效的IP地址 · This type of EPG supports only endpoint IP members：此类型仅支持配置terminal_ips字段 · This type of EPG supports only subnet members：此类型仅支持配置subnets字段 · This type of EPG supports only network members：此类型仅支持配置networks字段 · This type of EPG supports only external CIDR members：此类型仅支持配置external_cidrs字段 · The specified tenant doesn't exist：指定的租户不存在 · The specified vRouter doesn't exist：指定的虚拟路由器不存在 · The router is not matching tenant：指定的虚拟路由器不属于指定租户 · The specified vSubnet doesn't exist：指定的子网不存在 · The specified vSubnet must have the same tenant ID as the EPG：EPG和子网的租户ID必须相同 · The specified vSubnet must have the same vRouter ID as the EPG：EPG和子网的虚拟路由器ID必须相同 · The subnet resource cannot be used because it is used in a PBR service chain：PBR类型的子网不能作为EPG成员 · The specified vNetwork doesn't exist：指定的网络不存在 · The specified vNetwork must have the same tenant ID as the EPG：EPG和网络的租户ID必须相同 · The specified vNetwork must have the same vRouter ID as the EPG：EPG和网络的虚拟路由器ID必须相同 · The network resource cannot be used because it is used in a PBR service chain：PBR类型的网络不能作为EPG · An external EPG cannot contain members in any other EPGs if it is not bound to a vRouter：不指定虚拟路由器的External类型EPG，其成员不能与其他EPG的成员重复 · The EPG already exists：EPG已存在 · Failed to add the EPG：添加EPG失败 · You have no privilege to perform this operation：用户无权限执行此操作 · The vRouter bound to the source EPG, destination EPG or third-party service instance does not exist：源EPG、目的EPG或服务实例绑定的虚拟路由器不存在 · You cannot create a vRouter link of the normal, PBR, or NBAC type, because the local or remote vRouter on the link has been bound to both a centralized vNetwork and an IPv6 subnet：当虚拟路由器连接为Normal、PBR或NBAC类型时，本端和对端虚拟路由器下不能同时绑定集中式虚拟链路层网络和IPv6子网 · The vPort ID already exists：虚拟端口ID已存在 · You must specify the VM match rule when the EPG type is terminal and the terminal filter setting is VM：Terminal VM类型下，VM匹配规则不能为空 · You must specify the VM filter when the EPG type is terminal and the terminal filter setting is VM：Terminal VM类型下，VM匹配条件不能为空 · Please specify the VM string：VM信息不能为空 · The VM string already exists：VM信息已存在 · The VM filter and match rule settings already exist：VM匹配条件和规则已存在 · The specified vPort does not exist：虚拟端口不存在 · The tenant IDs for the EPG and the specified vPort are different：EPG与指定虚拟端口的租户ID不匹配 · The vPort resource cannot be used because it is created by PBR service chain：PBR类型的vPort不能作为EPG成员 · The router ID for the EPG and the specified vPort are different：EPG与指定虚拟端口的虚拟路由器ID不匹配 · The VM string is case sensitive and cannot exceed 255 characters：VM信息最长255个字符，区分大小写 · For the exact match rule, make sure the MAC address format is XX:XX:XX:XX:XX:XX. For any other match rules, make sure the MAC address format is XX, XX:XX, XX:XX:XX, XX:XX:XX:XX, XX:XX:XX:XX:XX, or XX:XX:XX:XX:XX:XX：全词匹配规则下，MAC地址格式为XX:XX:XX:XX:XX:XX；非全词匹配规则下，MAC地址格式为XX、XX:XX、XX:XX:XX、XX:XX:XX:XX、XX:XX:XX:XX:XX或XX:XX:XX:XX:XX:XX · The edge device to the external network for the vRouter is a firewall. Do not specify any external subnets for the EPG：指定虚拟路由器的外网出口设备为防火墙，外部网络子网必须为空 · The vRouter uses a border device as its edge device to the external network and the EPG uses the primary/backup gateway deployment mode. You can specify only two IPv4 external subnets, two IPv6 external subnets, or two IPv4 and two IPv6 external subnets for the EPG：当虚拟路由器的外网出口设备为边界设备时，主备出口模式下，只能绑定两个IPv4、两个IPv6或同时绑定两个IPv4和IPv6外网子网 · The vRouter uses a border device as its edge device to the external network and the EPG uses the single gateway deployment mode. You can specify only one IPv4 external subnet, one IPv6 external subnet, or one IPv4 and one IPv6 external subnet for the EPG：当虚拟路由器的外网出口设备为边界设备时，单出口模式下，只能绑定一个IPv4、一个IPv6或同时绑定一个IPv4和IPv6外网子网 · The edge device to the external network for the vRouter is a border device. Please specify external subnets for the EPG：当虚拟路由器未指定时，外部网络子网不能为空 · The specified external subnet does not exist：指定的外网子网不存在 · The value for flag can only be true (On) or false (Off)：自动同步EPG到对端的取值仅支持设置true和false · Failed to bind the vRouter to the EPG, because the vRouter has been used by a service chain with two contexts. One context is the external type without external network CIDRs specified, and the other context is the non-external type associated with this vRouter：EPG绑定虚拟路由器失败，该虚拟路由器已被一个流量特征组为External类型且不指定外网网段，另一个流量特征组对应的虚拟路由器为该虚拟路由器的服务链使用 · Invalid private network CIDR：无效的私有网段地址 · Duplicated private network CIDRs exist：私有网段地址重复 · The private network CIDR already exists：私有网段地址已存在 · The vRouter must be a normal vRouter：指定的虚拟路由器只能选择NORMAL类型 · You must specify terminal_ips, port_ids, or terminal_attr when the EPG type is terminal：Terminal类型仅支持terminal_ips、port_ids或者terminal_attr · Southbound devices at the following IP addresses were disconnected: {%s}：{IP地址集合}对应的南向设备已断开连接 · External-type EPGs cannot have the same members if some of their associated external subnets belong to the same external network：如果同一外部网络下有多个External类型EPG，它们所包含的成员不能重复 · The vRouter has been specified in an inter-vRouter EPG policy or inter-tenant EPG policy. Make sure the source (or destination) EPG members do not conflict with any subnets or members of the vRouter associated with the destination (source) EPG：指定的虚拟路由器已创建跨虚拟路由器EPG间策略或跨租户EPG间策略，源（目的）EPG成员与目的（源）EPG所属虚拟路由器下的子网和EPG成员不能存在重复 · Make sure the source or destination EPG members do not overlap with any subnets of the vRouter bound to the service node：源或目的EPG的成员与服务节点绑定的虚拟路由器下的子网存在重叠 · The static route issued by the application policy that uses static route-based service chain traffic routing conflicts with the routes learned by the created vRouter links：引流方式为静态路由的应用策略下发的静态路由和创建虚拟路由器连接学习到的路由存在冲突 · In two application policies that use static route-based service chain traffic routing and have the same vRouter specified, if the EPGs associated with the remaining two vRouters have overlapping subnets, make sure that: 1. The EPGs are specified as either the source or destination EPGs in the application policies. 2. The EPGs are specified in the same service path：服务链引流方式选择静态路由时，两个不同的应用策略选择同一虚拟路由器，且另外两个虚拟路由器的EPG存在子网重叠，则这两个EPG必须均作为源（目的）EPG，且服务路径必须相同 · In an application policy that uses static route-based service chain traffic routing, to use an EPG in multiple rules, make sure that: 1. The EPG is specified as either the source or destination EPG in the rules. 2. The rules are specified in the same service path：在一个应用策略内，若服务链引流方式选择静态路由，一个EPG被不同规则使用时必须作为同一源/目的EPG，且服务路径必须相同 · In the rules of an inter-vRouter EPG policy or inter-tenant EPG policy, make sure the EPG members of both vRouters do not contain conflicting subnets：跨虚拟路由器EPG间策略或跨租户EPG间策略中，两个虚拟路由器下被规则引用的EPG 成员之间存在子网重叠 · A member cannot be added to different EPGs on the same vRouter：同一虚拟路由器下不同EPG的成员不能重复 · 指定EPG的私有网段地址和EPG成员之间存在重复：The private network CIDRs of the specified EPG cannot have overlapping addresses with an EPG member · Member {$1} of the EPG has been specified for EPG {$2}：指定EPG的成员{$1}和EPG{$2}的成员存在重复 · The specified NQA policy does not exist：指定的NQA策略不存在 · You cannot bind the EPG to an NQA profile when the auto NQA profile mode is used：当NQA策略配置为自动时，EPG不能绑定该NQA策略 · Make sure the selected external subnets have been bound to the vRouter specified for the EPG：外网子网成员必须绑定EPG指定的虚拟路由器 |
|
关键字 |
UPDATE_EPG_OP |
|
日志内容 |
Updated EPG $1 |
|
参数解释 |
$1：EPG的信息 |
|
举例 |
Updated EPG ID: a89144ff-08cc-4239-b646-ffbf80ec0459 Name: net10 Router ID: 5867a83a-cb23-47cb-95ee-99ef5aea135f Base: type: NETWORK Networks: [ 4d6c0aa4-15bf-497c-bea7-6d137317ee0f] Intra isolation: false Flag: false |
|
日志说明 |
用户进行了修改EPG的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service is disabled：服务未启动 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · Invalid UUID：无效的UUID · The specified resource doesn't exist：指定的资源不存在 · The tenant name cannot be modified：租户名称不允许修改 · The tenant ID is required：租户ID不能为空 · The vRouter ID is required：虚拟路由器ID不能为空 · The name is required：名称不能为空 · The EPG type is required：EPG类型不能为空 · The tenant ID cannot be modified：租户ID不允许修改 · The ID can not be modified：ID不允许修改 · The router ID can not be modified：虚拟路由器ID不允许修改 · Invalid JSON format：无效的JSON格式 · The name cannot exceed 255 characters：名称最长255个字符 · The network ID already exists：网络ID已存在 · The subnet ID already exist：子网ID已存在 · The external CIDR already exists：外网IP地址已存在 · Invalid external network address：无效的外网IP · Duplicated external network addresses exist：外网IP不能重复 · The terminal IP address already exists：IP地址已存在 · Invalid IP address：无效的IP地址 · This type of EPG supports only endpoint IP members：此类型仅支持配置terminal_ips字段 · This type of EPG supports only subnet members：此类型仅支持配置subnets字段 · This type of EPG supports only network members：此类型仅支持配置networks字段 · This type of EPG supports only external CIDR members：此类型仅支持配置external_cidrs字段 · The specified vSubnet doesn't exist：指定的子网不存在 · The specified vSubnet must have the same tenant ID as the EPG：EPG和子网的租户ID必须相同 · The specified vSubnet must have the same vRouter ID as the EPG：EPG和子网的虚拟路由器ID必须相同 · The subnet resource cannot be used because it is used in a PBR service chain：PBR类型的子网不能作为EPG成员 · The specified vNetwork doesn't exist：指定的网络不存在 · The specified vNetwork must have the same tenant ID as the EPG：EPG和网络的租户ID必须相同 · The specified vNetwork must have the same vRouter ID as the EPG：EPG和网络的虚拟路由器ID必须相同 · The network resource cannot be used because it is used in a PBR service chain：PBR类型的网络不能作为EPG · An external EPG cannot contain members in any other EPGs if it is not bound to a vRouter：不指定虚拟路由器的External类型EPG，其成员不能与其他EPG的成员重复 · Member {$1} of the EPG has been specified for EPG {$2}：指定EPG的成员{$1}和EPG{$2}的成员存在重复 · Failed to edit the EPG：修改EPG失败 · You have no privilege to perform this operation：用户无权限执行此操作 · You cannot edit an EPG automatically generated upon service path creation：服务路径自动生成的EPG不允许修改 · The vPort ID already exists：虚拟端口ID已存在 · You must specify the VM match rule when the EPG type is terminal and the terminal filter setting is VM：Terminal VM类型下，VM匹配规则不能为空 · You must specify the VM filter when the EPG type is terminal and the terminal filter setting is VM：Terminal VM类型下，VM匹配条件不能为空 · Please specify the VM string：VM信息不能为空 · The VM string already exists：VM信息已存在 · The VM filter and match rule settings already exist：VM匹配条件和规则已存在 · The specified vPort does not exist：虚拟端口不存在 · The tenant IDs for the EPG and the specified vPort are different：EPG与指定虚拟端口的租户ID不匹配 · The vPort resource cannot be used because it is created by PBR service chain：PBR类型的vPort不能作为EPG成员 · The router ID for the EPG and the specified vPort are different：EPG与指定虚拟端口的虚拟路由器ID不匹配 · The VM string is case sensitive and cannot exceed 255 characters：VM信息最长255个字符，区分大小写 · For the exact match rule, make sure the MAC address format is XX:XX:XX:XX:XX:XX. For any other match rules, make sure the MAC address format is XX, XX:XX, XX:XX:XX, XX:XX:XX:XX, XX:XX:XX:XX:XX, or XX:XX:XX:XX:XX:XX：全词匹配规则下，MAC地址格式为XX:XX:XX:XX:XX:XX；非全词匹配规则下，MAC地址格式为XX、XX:XX、XX:XX:XX、XX:XX:XX:XX、XX:XX:XX:XX:XX或XX:XX:XX:XX:XX:XX · The edge device to the external network for the vRouter is a firewall. Do not specify any external subnets for the EPG：指定虚拟路由器的外网出口设备为防火墙，外部网络子网必须为空 · The vRouter uses a border device as its edge device to the external network and the EPG uses the primary/backup gateway deployment mode. You can specify only two IPv4 external subnets, two IPv6 external subnets, or two IPv4 and two IPv6 external subnets for the EPG：当虚拟路由器的外网出口设备为边界设备时，主备出口模式下，只能绑定两个IPv4、两个IPv6或同时绑定两个IPv4和IPv6外网子网 · The vRouter uses a border device as its edge device to the external network and the EPG uses the single gateway deployment mode. You can specify only one IPv4 external subnet, one IPv6 external subnet, or one IPv4 and one IPv6 external subnet for the EPG：当虚拟路由器的外网出口设备为边界设备时，单出口模式下，只能绑定一个IPv4、一个IPv6或同时绑定一个IPv4和IPv6外网子网 · The edge device to the external network for the vRouter is a border device. Please specify external subnets for the EPG：当虚拟路由器未指定时，外部网络子网不能为空 · The specified external subnet does not exist：指定的外网子网不存在 · You cannot change the EGP type to External. This is because the EPG is used in one of the exception rules in an application policy, and the service path in that rule contains PBRLoadbalance service instances：EPG已被应用策略中的例外规则引用，且该例外规则引用的服务路径包含PBRLoadbalance类型的服务实例，EPG类型不能修改为External · The value for flag can only be true (On) or false (Off)：自动同步EPG到对端的取值仅支持设置true和false · Failed to bind the vRouter to the EPG, because the vRouter has been used by a service chain with two contexts. One context is the external type without external network CIDRs specified, and the other context is the non-external type associated with this vRouter：EPG绑定虚拟路由器失败，该虚拟路由器已被一个流量特征组为External类型且不指定外网网段，另一个流量特征组对应的虚拟路由器为该虚拟路由器的服务链使用 · Invalid private network CIDR：无效的私有网段地址 · Duplicated private network CIDRs exist：私有网段地址重复 · The private network CIDR already exists：私有网段地址已存在 · Operation failed. The EPG is used in the service path in one of the exception rules in an application policy. The source or destination EPG in the service path must be external type, because the path has a third-party service node with IPsec settings：EPG类型修改失败，指定EPG已被应用策略使用。例外规则的服务路径已使用IPsec功能的第三方服务节点，源或目的EPG只能为External类型 · The EPG is used in the service path in one of the exception rules in an application policy. You cannot change it to external type, because the service path has LB service nodes between it and a third-party service node with IPsec or NAT settings：EPG类型修改失败，指定EPG已被应用策略使用。例外规则的服务路径中，已配置IPsec或NAT功能的第三方服务节点与External类型的EPG之间不允许存在LB类型的服务节点 · The EPG cannot be external type. It has been used as the source or destination EPG in a service path that contains a firewall node in one-arm connection mode：EPG类型修改失败，指定EPG已被应用策略使用，且服务路径的服务节点使用了单臂连接模式，源或目的EPG不能为External类型 · Failed to change the type of the EPG to external, because it has been used in an application policy that already contains an external EPG：EPG类型修改失败，指定EPG已被应用策略使用，源和目的EPG不能同时为External类型 · The gateway deployment mode cannot be edited, because the EPG has been bound to an application policy：该EPG已被应用策略使用，出口模式不允许修改 · The vRouter must be a normal vRouter：指定的虚拟路由器只能选择NORMAL类型 · The EPG type cannot be changed：不允许修改EPG的类型 · You must specify terminal_ips, port_ids, or terminal_attr when the EPG type is terminal：Terminal类型仅支持terminal_ips、port_ids或者terminal_attr · You cannot specify external EPG members in the inter-vRouter EPG policy：跨虚拟路由器EPG间策略引用的EPG类型不能为External · Southbound devices at the following IP addresses were disconnected: {%s}：{IP地址集合}对应的南向设备已断开连接 · Make sure the members of an EPG specified in an application policy do not overlap with any subnets of the vRouter bound to the service node：被应用策略使用的EPG，其成员不能与服务节点绑定的虚拟路由器下的子网存在重叠 · The EPG has been specified for an application policy, and it uses the single gateway deployment mode. To replace an external subnet bound to a border gateway for the EPG, make sure the new subnet is bound to a border gateway：该EPG已被应用策略使用且为单出口，指定的外网子网已绑定出口网关，该外网子网不允许修改为未绑定出口网关的外网子网 · External-type EPGs cannot have the same members if some of their associated external subnets belong to the same external network：如果同一外部网络下有多个External类型EPG，它们所包含的成员不能重复 · The vRouter has been specified in an inter-vRouter EPG policy or inter-tenant EPG policy. Make sure the source (or destination) EPG members do not conflict with any subnets or members of the vRouter associated with the destination (source) EPG：指定的虚拟路由器已创建跨虚拟路由器EPG间策略或跨租户EPG间策略，源（目的）EPG成员与目的（源）EPG所属虚拟路由器下的子网和EPG成员不能存在重复 · Turning on the Advertise EPG to Peer vRouter option might result in repeated configuration deployment：开启自动同步EPG到对端下发的配置存在重复 · In two application policies that use static route-based service chain traffic routing and have the same vRouter specified, if the EPGs associated with the remaining two vRouters have overlapping subnets, make sure that: 1. The EPGs are specified as either the source or destination EPGs in the application policies. 2. The EPGs are specified in the same service path：服务链引流方式选择静态路由时，两个不同的应用策略选择同一虚拟路由器，且另外两个虚拟路由器的EPG存在子网重叠，则这两个EPG必须均作为源（目的）EPG，且服务路径必须相同 · Make sure the source or destination EPG members do not overlap with any subnets of the vRouter bound to the service node：源或目的EPG的成员与服务节点绑定的虚拟路由器下的子网存在重叠 · The static route issued by the application policy that uses static route-based service chain traffic routing conflicts with the routes learned by the created vRouter links：引流方式为静态路由的应用策略下发的静态路由和创建虚拟路由器连接学习到的路由存在冲突 · In two application policies that use static route-based service chain traffic routing and have the same vRouter specified, if the EPGs associated with the remaining two vRouters have overlapping subnets, make sure that: 1. The EPGs are specified as either the source or destination EPGs in the application policies. 2. The EPGs are specified in the same service path：服务链引流方式选择静态路由时，两个不同的应用策略选择同一虚拟路由器，且另外两个虚拟路由器的EPG存在子网重叠，则这两个EPG必须均作为源（目的）EPG，且服务路径必须相同 · In an application policy that uses static route-based service chain traffic routing, to use an EPG in multiple rules, make sure that: 1. The EPG is specified as either the source or destination EPG in the rules. 2. The rules are specified in the same service path：在一个应用策略内，若服务链引流方式选择静态路由，一个EPG被不同规则使用时必须作为同一源/目的EPG，且服务路径必须相同 · In the rules of an inter-vRouter EPG policy or inter-tenant EPG policy, make sure the EPG members of both vRouters do not contain conflicting subnets：跨虚拟路由器EPG间策略或跨租户EPG间策略中，两个虚拟路由器下被规则引用的EPG 成员之间存在子网重叠 · A member cannot be added to different EPGs on the same vRouter：同一虚拟路由器下不同EPG的成员不能重复 · 指定EPG的私有网段地址和EPG成员之间存在重复：The private network CIDRs of the specified EPG cannot have overlapping addresses with an EPG member · The specified NQA policy does not exist：指定的NQA策略不存在 · You cannot bind the EPG to an NQA profile when the auto NQA profile mode is used：当NQA策略配置为自动时，EPG不能绑定该NQA策略 · Make sure the source and destination EPG members in the intra-vRouter policy do not contain overlapping subnets：虚拟路由器内策略中源EPG成员与目的EPG成员不能存在子网重叠 · An intra-vRouter policy has been created for the vRouter. Make sure the source and destination EPG members in the intra-vRouter policy do not contain overlapping subnets：指定的虚拟路由器已创建虚拟路由器内策略，源EPG成员与目的EPG成员不能存在子网重叠 |
|
关键字 |
DELETE_EPG_OP |
|
日志内容 |
Deleted EPG $1. |
|
参数解释 |
$1：EPG的名称 |
|
举例 |
Deleted EPG net10. |
|
日志说明 |
用户进行了删除EPG的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service is disabled：服务未启动 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · Invalid UUID：无效的UUID · The specified resource doesn't exist：指定的资源不存在 · Failed to delete the EPG：删除EPG失败 · The EPG is being used by an application policy：指定的EPG正在被应用策略使用 · You have no privilege to perform this operation：用户无权限执行此操作 · You cannot delete an EPG automatically generated upon service path creation：服务路径自动生成的EPG不允许删除 · Southbound devices at the following IP addresses were disconnected: {%s}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
UPDATE_NBAC_GLOBAL_OP |
|
日志内容 |
Updated NBAC global settings $1 |
|
参数解释 |
$1：应用策略全局配置的信息 |
|
举例 |
Updated NBAC global settings preconfigured: false |
|
日志说明 |
用户进行了修改应用策略全局配置的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service is disabled：服务未启动 · The controller is not the active leader：该控制器不是主Leader · Configuration recovery is in progress：配置恢复未完成 · Invalid JSON format：无效的JSON格式 · You have no privilege to perform this operation：用户无权限执行此操作 · Unknown error code：未知的错误码 |
本节介绍承载网络模块输出的操作日志信息。
|
关键字 |
CREATE_VLAN-VXLAN_OP |
|
日志内容 |
Created VLAN-VXLAN mapping table: $1 |
|
参数解释 |
$1：VLAN-VXLAN映射表配置信息 |
|
举例 |
Created VLAN-VXLAN mapping table: ID: [218b5f2f-e435-4365-a1ab-0eaa03b7fa19] Name: [table] VLAN-VXLAN mappings: [ VLAN: [2--13], VXLAN: [4--4], Assignment only: [false], Access mode: [VLAN] ] |
|
日志说明 |
用户进行了创建VLAN-VXLAN映射表的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · Invalid JSON format：无效的JSON格式 · The service is disabled：服务未启动 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Invalid name：无效的名称 · The VLAN ID is invalid or out of range：无效的VLAN ID或者VLAN ID范围错误 · Invalid VXLAN ID：无效的VXLAN ID · The mapping table already exists：该映射表已存在 · No name is specified：未指定名称 · Two same mappings exist in the mapping table：映射表中有两个完全相同的映射关系 · Overlapped mappings exist in the mapping table：映射关系存在重叠 · All mappings in the same mapping table must be the same type：同一个映射表的所有映射关系类型必须一致 · Inconsistent mapping table type and mapping type：映射表的类型和映射关系的类型不一致 · vlanif mapping tables do not support the start_cvlan, end_cvlan, and rewrite_rules parameters：vlanif类型的映射表不支持配置start_cvlan、end_cvlan和rewrite_rules参数 · The reserved VLAN ID conflicts with a VLAN ID of an VLAN-VXLAN mapping：存储VLAN与VLAN-VXLAN映射冲突 · Unknown internal server error：未知的内部服务器错误 · You have no privilege to perform this operation：用户无权限执行此操作 · You have selected interfaces on an inactive device (management IP: management IP)：正在绑定的接口所属设备中存在未激活设备(管理IP：管理IP) · A global VLAN-VXLAN mapping supports only the Ethernet type：全局VLAN-VXLAN映射只支持Ethernet类型 · A global VLAN-VXLAN mapping does not support mapping multiple VLANs to one VXLAN：全局VLAN-VXLAN映射不支持多对一映射 · The VLAN pool overlaps with a global VLAN-VXLAN mapping：全局VLAN-VXLAN映射VLAN与VLAN池范围冲突 · The segment ID of a external network conflicts with a VLAN ID of a global VLAN-VXLAN mapping：全局VLAN-VXLAN映射VLAN与外网的Segment ID冲突 · You cannot rewrite rules for a global VLAN-VXLAN mapping：全局VLAN-VXLAN映射不支持写入规则 · A default encapsulation mapping supports only Ethernet access modeDefault封装类型映射关系仅支持Ethernet接入模式 · A VLAN-VXLAN or VLAN-network mapping table supports only one default encapsulation mapping：同一个VLAN-VXLAN/VLAN-Network映射表仅支持配置一个Default封装类型映射关系 · An interface can be bound to one default encapsulation mapping：同一个接口仅支持绑定一个Default封装类型映射关系 · A default encapsulation mapping does not support rewrite_rules：Default封装类型映射关系不支持配置rewrite_rules信息 · A default encapsulation mapping does not support SVLAN or CVLAN IDs：Default封装类型映射关系不支持填写SVLAN、CVLAN · The start and end VXLAN IDs in a default encapsulation mapping must be identical：Default封装类型映射关系起始VXLAN ID与结束VXLAN ID必须相等 · The encapsulation type in a VLAN-VXLAN or VLAN-network mapping supports only default and Dot1q encapsulation：VLAN-VXLAN/VLAN-Network映射关系封装类型仅支持取值为Default和Dot1q · A VLAN-VXLAN or VLAN-network mapping in VLAN access mode does not support rewrite_rules：接入模式为VLAN的VLAN-VXLAN/VLAN-Network映射关系不支持配置rewrite_rules信息 · A VLAN-VXLAN or VLAN-network mapping supports only inbound rewrite_rules：VLAN-VXLAN/VLAN-Network映射关系配置的rewrite_rules信息仅支持入方向规则 · The rewrite_rules in a VLAN-VXLAN or VLAN-network mapping supports only the STRIP_SVLAN processing method：VLAN-VXLAN/VLAN-Network映射关系配置的rewrite_rules信息仅支持规则处理方式为STRIP_SVLAN · The value of the symmetric parameter must be true for the inbound rewrite_rules in a VLAN-VXLAN or VLAN-network mapping：VLAN-VXLAN/VLAN-Network映射关系配置的rewrite_rules信息入方向规则的symmetric参数只能配置为true · A default encapsulation mapping supports only interface-specific mapping binding：Default封装类型映射关系仅支持接口级映射绑定 · The VLAN-VXLAN mapping, which effective location is VLAN, only supports the Dot1q type：生效位置为VLAN的VLAN-VXLAN映射只支持Dot1q封装类型 |
|
关键字 |
UPDATE_VLAN-VXLAN_OP |
|
日志内容 |
Updated VLAN-VXLAN mapping table: $1 |
|
参数解释 |
$1： VLAN-VXLAN映射表配置信息 |
|
举例 |
Updated VLAN-VXLAN mapping table: ID: [218b5f2f-e435-4365-a1ab-0eaa03b7fa19] Name: [table] VLAN-VXLAN mappings: [ VLAN: [2--13], VXLAN: [4--4], Assignment only: [false], Access mode: [VLAN] ] |
|
日志说明 |
用户进行了修改VLAN-VXLAN映射表的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · Invalid JSON format：无效的JSON格式 · The service is disabled：服务未启动 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Invalid name：无效的名称 · The VLAN ID is invalid or out of range：无效的VLAN ID或者VLAN ID范围错误 · Invalid VXLAN ID：无效的VXLAN ID · No name is specified：未指定名称 · Two same mappings exist in the mapping table：映射表中有两个完全相同的映射关系 · Overlapped mappings exist in the mapping table：映射关系存在重叠 · The mapping table does not exist：该映射表不存在 · All mappings in the same mapping table must be the same type：同一个映射表的所有映射关系类型必须一致 · Inconsistent mapping table type and mapping type：映射表的类型和映射关系的类型不一致 · The mapping table is created through the bare metal module and cannot be modified：该映射表通过裸金属管理模块创建，不允许修改 · The mapping table is created through the resource access template module and cannot be modified：该映射表通过资源接入模板创建，不允许修改 · The reserved VLAN ID conflicts with a VLAN ID of an VLAN-VXLAN mapping：存储VLAN与VLAN-VXLAN映射冲突 · Unknown internal server error：未知的内部服务器错误 · You have no privilege to perform this operation：用户无权限执行此操作 · You have selected interfaces on an inactive device (management IP: management IP)：正在绑定的接口所属设备中存在未激活设备(管理IP：管理IP) · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · You cannot edit the apply_scope parameter for a global VLAN-VXLAN mapping：全局VLAN-VXLAN映射 apply_scope字段不允许修改 · A global VLAN-VXLAN mapping supports only the Ethernet type：全局VLAN-VXLAN映射只支持Ethernet类型 · A global VLAN-VXLAN mapping does not support mapping multiple VLANs to one VXLAN：全局VLAN-VXLAN映射不支持多对一映射 · The VLAN pool overlaps with a global VLAN-VXLAN mapping：全局VLAN-VXLAN映射VLAN与VLAN池范围冲突 · The segment ID of a external network conflicts with a VLAN ID of a global VLAN-VXLAN mapping：全局VLAN-VXLAN映射VLAN与外网的Segment ID冲突 · You cannot rewrite rules for a global VLAN-VXLAN mapping：全局VLAN-VXLAN映射不支持写入规则 · A default encapsulation mapping supports only Ethernet access modeDefault封装类型映射关系仅支持Ethernet接入模式 · A VLAN-VXLAN or VLAN-network mapping table supports only one default encapsulation mapping：同一个VLAN-VXLAN/VLAN-Network映射表仅支持配置一个Default封装类型映射关系 · An interface can be bound to one default encapsulation mapping：同一个接口仅支持绑定一个Default封装类型映射关系 · A default encapsulation mapping does not support rewrite_rules：Default封装类型映射关系不支持配置rewrite_rules信息 · A default encapsulation mapping does not support SVLAN or CVLAN IDs：Default封装类型映射关系不支持填写SVLAN、CVLAN · The start and end VXLAN IDs in a default encapsulation mapping must be identical：Default封装类型映射关系起始VXLAN ID与结束VXLAN ID必须相等 · The encapsulation type in a VLAN-VXLAN or VLAN-network mapping supports only default and Dot1q encapsulation：VLAN-VXLAN/VLAN-Network映射关系封装类型仅支持取值为Default和Dot1q · A VLAN-VXLAN or VLAN-network mapping in VLAN access mode does not support rewrite_rules：接入模式为VLAN的VLAN-VXLAN/VLAN-Network映射关系不支持配置rewrite_rules信息 · A VLAN-VXLAN or VLAN-network mapping supports only inbound rewrite_rules：VLAN-VXLAN/VLAN-Network映射关系配置的rewrite_rules信息仅支持入方向规则 · The rewrite_rules in a VLAN-VXLAN or VLAN-network mapping supports only the STRIP_SVLAN processing method：VLAN-VXLAN/VLAN-Network映射关系配置的rewrite_rules信息仅支持规则处理方式为STRIP_SVLAN · The value of the symmetric parameter must be true for the inbound rewrite_rules in a VLAN-VXLAN or VLAN-network mapping：VLAN-VXLAN/VLAN-Network映射关系配置的rewrite_rules信息入方向规则的symmetric参数只能配置为true · A default encapsulation mapping supports only interface-specific mapping binding：Default封装类型映射关系仅支持接口级映射绑定 · The VLAN-VXLAN mapping, which effective location is VLAN, only supports the Dot1q type：生效位置为VLAN的VLAN-VXLAN映射只支持Dot1q封装类型 |
|
关键字 |
DELETE_VLAN-VXLAN_OP |
|
日志内容 |
Deleted VLAN-VXLAN mapping table: $1 |
|
参数解释 |
$1：VLAN-VXLAN映射表ID |
|
举例 |
Deleted VLAN-VXLAN mapping table: 218b5f2f-e435-4365-a1ab-0eaa03b7fa19 |
|
日志说明 |
用户进行了删除VLAN-VXLAN映射表的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · Invalid JSON format：无效的JSON格式 · The service is disabled：服务未启动 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · The mapping table is already bound to ports：该映射表已绑定接口 · The mapping table is already bound to physical access devices：该映射表已绑定物理接入设备 · The mapping table does not exist：该映射表不存在 · The mapping table is created through the bare metal module and cannot be deleted：该映射表通过裸金属管理模块创建，不允许删除 · The mapping table is created through the resource access template module and cannot be deleted：该映射表通过资源接入模板创建，不允许删除 · Unknown internal server error：未知的内部服务器错误 · You have no privilege to perform this operation：用户无权限执行此操作 · You have selected interfaces on an inactive device (management IP: management IP)：正在绑定的接口所属设备中存在未激活设备(管理IP：管理IP) |
|
关键字 |
CREATE_QINQ-VXLAN_OP |
|
日志内容 |
Created QinQ-VXLAN mapping table: $1 |
|
参数解释 |
$1：QinQ-VXLAN映射表配置信息 |
|
举例 |
Created QinQ-VXLAN mapping table: ID: [218b5f2f-e435-4365-a1ab-0eaa03b7fa19] Name: [table] QinQ-VXLAN mappings: [ [ SVLAN: [1--1], CVLAN: [2--3], VXLAN: [3--3], Assignment only: [false], Access mode: [Ethernet] Rewrite rule list: [ Direction: [inbound], Type: [NEST], SVLAN: [1], CVLAN: [2], Symmetric: [false] ] ] ] |
|
日志说明 |
用户进行了创建QinQ-VXLAN映射表的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · Invalid JSON format：无效的JSON格式 · The service is disabled：服务未启动 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Invalid name：无效的名称 · The VLAN ID is invalid or out of range：无效的VLAN ID或者VLAN ID范围错误 · Invalid VXLAN ID：无效的VXLAN ID · The mapping table already exists：指定的映射表已存在 · No name is specified：未指定名称 · Overlapped mappings exist in the mapping table：映射关系存在重叠 · The QinQ-VXLAN mapping range must be the same as the SVLAN or CVLAN mapping range：VXLAN映射区间宽度必须等于SVLAN或CVLAN映射区间宽度 · The symmetric parameter can only be configured as false in the outbound rule：出方向规则的symmetric参数只能配置为false · A maximum of one rewrite rule can be configured in one direction of a QinQ-VXLAN mapping：一条QinQ-VXLAN映射关系的一个方向最多配置一条处理规则 · No outbound rule can be configured if the symmetric parameter has been configured as true for an inbound rule：入方向规则的symmetric参数配置为true和配置出方向规则冲突 · The rewrite_svlan_id parameter is required when the rewrite rule in the inbound direction is NEST：入方向规则的处理方式为NEST时，rewrite_svlan_id为必选 · The rewrite_cvlan_id and rewrite_svlan_id parameters cannot be both empty if the rewrite rule is REMARK_ONE：规则处理方式为REMARK_ONE时，rewrite_cvlan_id和rewrite_svlan_id不能同时为空 · The rewrite_cvlan_id and rewrite_svlan_id parameters cannot be both empty if the rewrite rule is REMARK_TWO：规则处理方式为REMARK_TWO时，rewrite_cvlan_id和rewrite_svlan_id不能同时为空 · The rewrite_svlan_id parameter is required when the rewrite rule in the inbound direction is REMARK_ONE：入方向规则的处理方式为REMARK_ONE时，rewrite_svlan_id为必选 · The symmetric cannot be configured as true when the rewrite rule in the inbound direction is REMARK_ONE and the rewrite_cvlan_id is greater than 0：入方向规则的处理方式为REMARK_ONE且rewrite_cvlan_id大于0时，不支持配置symmetric为true · The symmetric cannot be configured as true when the rewrite rule in the inbound direction is REMARK_TWO and both the rewrite_cvlan_id and rewrite_svlan_id are greater than 0：入方向规则的处理方式为REMARK_TWO且rewrite_cvlan_id和rewrite_svlan_id都大于0时，不支持配置symmetric为true · The rewrite_svlan_id parameter is required when the rewrite rule in the outbound direction is NEST：出方向规则的处理方式为NEST时，rewrite_svlan_id为必选 · The rewrite_svlan_id parameter is required when the rewrite rule in the outbound direction is REMARK_ONE：出方向规则的处理方式为REMARK_ONE时，rewrite_svlan_id为必选 · The SVLAN mapping range and CVLAN mapping range cannot be both greater than 1：SVLAN映射区间和CVLAN映射区间不能同时大于1 · Invalid rewrite direction：无效的规则处理方向 · The rewrite_cvlan_id and rewrite_svlan_id parameters are not required if the rewrite rule is STRIP：规则处理方式为STRIP时，不需配置rewrite_cvlan_id和rewrite_svlan_id · All mappings in the same mapping table must be the same type：同一个映射表的所有映射关系类型必须一致 · The SVLAN and CVLAN mapping ranges of all mappings in the same mapping table must be the same：同一个映射表的所有映射关系的SVLAN和CVLAN的映射区间长度必须一致 · Inconsistent mapping table type and mapping type：映射表的类型和映射关系的类型不一致 · QinQ-VXLAN mapping tables with the VLAN access mode do not support the rewrite_rules parameter：接入模式为VLAN的QinQ-VXLAN映射表不能配置rewrite_rules信息 · The gaps between the start IDs and end IDs of the SVLAN mapping range, CVLAN mapping range, and VXLAN mapping range cannot be all greater than 1：SVLAN、CVLAN和VXLAN的映射区间不能同时大于1 · Unknown internal server error：未知的内部服务器错误 · The reserved VLAN ID conflicts with a VLAN ID of an VLAN-VXLAN mapping：存储VLAN与VLAN-VXLAN映射冲突 · You have no privilege to perform this operation：用户无权限执行此操作 · You have selected interfaces on an inactive device (management IP: management IP)：正在绑定的接口所属设备中存在未激活设备(管理IP：管理IP) · If you map multiple VLANs to one VXLAN in VLAN access mode, you must set the SVLAN range length and CVLAN range length to the same value：当QinQ映射配置为多对一映射场景和VLAN接入模式时，SVLAN和CVLAN的映射区间宽度必须一致 |
|
关键字 |
UPDATE_QINQ-VXLAN_OP |
|
日志内容 |
Updated QinQ-VXLAN mapping table: $1 |
|
参数解释 |
$1：QinQ-VXLAN映射表配置信息 |
|
举例 |
Updated QinQ-VXLAN mapping table: ID: [218b5f2f-e435-4365-a1ab-0eaa03b7fa19] Name: [table] QinQ-VXLAN mappings: [ [ SVLAN: [1--1], CVLAN: [2--3], VXLAN: [3--3], Assignment only: [false], Access mode: [Ethernet] Rewrite rule list: [ Direction: [inbound], Type: [NEST], SVLAN: [1], CVLAN: [2], Symmetric: [false] ] ] ] |
|
日志说明 |
用户进行了修改QinQ-VXLAN映射表的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · Invalid JSON format：无效的JSON格式 · The service is disabled：服务未启动 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Invalid name：无效的名称 · The VLAN ID is invalid or out of range：无效的VLAN ID或者VLAN ID范围错误 · Invalid VXLAN ID：无效的VXLAN ID · Overlapped mappings exist in the mapping table：映射关系存在重叠 · The mapping table does not exist：该映射表不存在 · The QinQ-VXLAN mapping range must be the same as the SVLAN or CVLAN mapping range：VXLAN映射区间必须等于SVLAN或CVLAN映射区间 · The symmetric parameter can only be configured as false in the outbound rule：出方向规则的symmetric参数只能配置为false · A maximum of one rewrite rule can be configured in one direction of a QinQ-VXLAN mapping：一条QinQ-VXLAN映射关系的一个方向最多配置一条处理规则 · No outbound rule can be configured if the symmetric parameter has been configured as true for an inbound rule：入方向规则的symmetric参数配置为true和配置出方向规则冲突 · The rewrite_svlan_id parameter is required when the rewrite rule in the inbound direction is NEST：入方向规则的处理方式为NEST时，rewrite_svlan_id为必选 · The rewrite_cvlan_id and rewrite_svlan_id parameters cannot be both empty if the rewrite rule is REMARK_ONE： 规则处理方式为REMARK_ONE时，rewrite_cvlan_id和rewrite_svlan_id不能同时为空 · The rewrite_cvlan_id and rewrite_svlan_id parameters cannot be both empty if the rewrite rule is REMARK_TWO：规则处理方式为REMARK_TWO时，rewrite_cvlan_id和rewrite_svlan_id不能同时为空 · The rewrite_svlan_id parameter is required when the rewrite rule in the inbound direction is REMARK_ONE：入方向规则的处理方式为REMARK_ONE时，rewrite_svlan_id为必选 · The symmetric cannot be configured as true when the rewrite rule in the inbound direction is REMARK_ONE and the rewrite_cvlan_id is greater than 0：入方向规则的处理方式为REMARK_ONE且rewrite_cvlan_id大于0时，不支持配置symmetric为true · The symmetric cannot be configured as true when the rewrite rule in the inbound direction is REMARK_TWO and both the rewrite_cvlan_id and rewrite_svlan_id are greater than 0：入方向规则的处理方式为REMARK_TWO且rewrite_cvlan_id和rewrite_svlan_id都大于0时，不支持配置symmetric为true · The rewrite_svlan_id parameter is required when the rewrite rule in the outbound direction is NEST：出方向规则的处理方式为NEST时，rewrite_svlan_id为必选 · The rewrite_svlan_id parameter is required when the rewrite rule in the outbound direction is REMARK_ONE：出方向规则的处理方式为REMARK_ONE时，rewrite_svlan_id为必选 · The SVLAN mapping range and CVLAN mapping range cannot be both greater than 1：SVLAN映射区间和CVLAN映射区间不能同时大于1 · Invalid rewrite direction：无效的规则处理方向 · The rewrite_cvlan_id and rewrite_svlan_id parameters are not required if the rewrite rule is STRIP：规则处理方式为STRIP时，不需配置rewrite_cvlan_id和rewrite_svlan_id · All mappings in the same mapping table must be the same type：同一个映射表的所有映射关系类型必须一致 · The SVLAN and CVLAN mapping ranges of all mappings in the same mapping table must be the same：同一个映射表的所有映射关系的SVLAN和CVLAN的映射区间长度必须一致 · Inconsistent mapping table type and mapping type：映射表的类型和映射关系的类型不一致 · QinQ-VXLAN mapping tables with the VLAN access mode do not support the rewrite_rules parameter：接入模式为VLAN的QinQ-VXLAN映射表不能配置rewrite_rules信息 · The gaps between the start IDs and end IDs of the SVLAN mapping range, CVLAN mapping range, and VXLAN mapping range cannot be all greater than 1：SVLAN、CVLAN和VXLAN的映射区间不能同时大于1 · Unknown internal server error：未知的内部服务器错误 · The reserved VLAN ID conflicts with a VLAN ID of an VLAN-VXLAN mapping：存储VLAN与VLAN-VXLAN映射冲突 · You have no privilege to perform this operation：用户无权限执行此操作 · You have selected interfaces on an inactive device (management IP: management IP)：正在绑定的接口所属设备中存在未激活设备(管理IP：管理IP) · If you map multiple VLANs to one VXLAN in VLAN access mode, you must set the SVLAN range length and CVLAN range length to the same value：当QinQ映射配置为多对一映射场景和VLAN接入模式时，SVLAN和CVLAN的映射区间宽度必须一致 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
DELETE_QINQ-VXLAN_OP |
|
日志内容 |
Deleted QinQ-VXLAN mapping table: $1 |
|
参数解释 |
$1：QinQ-VXLAN映射表ID |
|
举例 |
Deleted QinQ-VXLAN mapping table: 218b5f2f-e435-4365-a1ab-0eaa03b7fa19 |
|
日志说明 |
用户进行了删除QinQ-VXLAN映射表的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · Invalid JSON format：无效的JSON格式 · The service is disabled：服务未启动 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · The mapping table is already bound to ports：该映射表已绑定接口 · The mapping table is already bound to physical access devices：该映射表已绑定物理接入设备 · The mapping table does not exist：该映射表不存在 · Unknown internal server error：未知的内部服务器错误 · You have no privilege to perform this operation：用户无权限执行此操作 · You have selected interfaces on an inactive device (management IP: management IP)：正在绑定的接口所属设备中存在未激活设备(管理IP：管理IP) |
|
关键字 |
BIND_VLAN-VXLAN_OP |
|
日志内容 |
Bound VLAN-VXLAN mapping table: $1 |
|
参数解释 |
$1：VLAN-VXLAN映射表绑定物理接入设备配置信息 |
|
举例 |
Bound VLAN-VXLAN mapping table: ID: [218b5f2f-e435-4365-a1ab-0eaa03b7fa19] Name: [table] Physical access device: [ c1a3e882-51ad-4847-8dbb-d7d972a5934f ] |
|
日志说明 |
用户进行了把VLAN-VXLAN映射表与设备绑定的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · Invalid JSON format：无效的JSON格式 · The service is disabled：服务未启动 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Invalid name：无效的名称 · The mapping table does not exist：该映射表不存在 · The physical access device does not exist：指定的物理接入设备不存在 · The physical access device is already bound to a VLAN-VXLAN mapping table：指定的物理接入设备已绑定其它VLAN-VXLAN映射表 · No physical access device ID list is specified for the VLAN-VXLAN mapping table：未指定物理接入设备ID列表 · The device type doesn't match：指定设备的类型不匹配 · Duplicate physical access device IDs：物理接入设备ID重复 · The port on the specified device has been bound to a QinQ-VXLAN mapping table：指定设备下的接口已被QinQ-VXLAN映射表绑定 · The QinQ-VXLAN mapping table does not support device binding：QinQ-VXLAN映射表不支持设备级绑定 · Unknown internal server error：未知的内部服务器错误 · You have no privilege to perform this operation：用户无权限执行此操作 · You cannot bind a VLAN-network mapping table to the device：VLAN-Network类型的VLAN-VXLAN映射表不支持设备级绑定 · The VLAN-VXLAN, VLAN-network, or QinQ mapping conflicts with a PVLAN mapping on the VNID pools page：VLAN映射和静态的PVLAN映射冲突 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · VLAN-VXLAN mappings cannot be applied to a device group whose position is service leaf：网络位置为Service Leaf的设备组不可用于设备级VLAN-VXLAN映射 · To configure a global VLAN-VXLAN mapping, you must first enable VXLAN service preconfiguration：网元绑定全局VLAN-VXLAN类型映射表时下不允许切换VXLAN转发预配置开关 · To bind a global VLAN-VXLAN mapping, make sure the global IPv6 option is turned off for the device：绑定全局VLAN-VXLAN映射的设备必须关闭全局IPv6开关 · You cannot bind a global VLAN-VXLAN mapping, because the device is already configured with a donwlink interface：网元已经配置了下行口,不允许绑定全局VLAN-VXLAN映射 · In the network cloud scenario, you cannot configure a global VLAN-VXLAN mapping：网络云场景不支持配置全局VLAN-VXLAN映射绑定 · The device type does not support binding interfaces：该类型的设备不支持接口绑定 · This device type does not support binding VLAN-VXLAN mappings whose effective location is VLAN：当前类型的设备不支持绑定生效位置为VLAN的VLAN-VXLAN映射 · To configure a global VLAN-VXLAN mapping, you must first enable VXLAN service preconfiguration：绑定全局VLAN-VXLAN映射的设备必须开启VXLAN转发预配置开关 · The binding already exists：绑定的设备已存在 · A default encapsulation mapping supports only interface-specific mapping binding：Default封装类型映射关系仅支持接口级映射绑定 · You cannot bind the device to a global VLAN-VXLAN mapping, because subnet gatewayhas been enabled for a device group in the fabric：Fabric内已存在开启子网网关的设备组，不允许绑定全局VLAN-VXLAN映射 |
|
关键字 |
UPDATE_VLAN-VXLAN_BINDING_OP |
|
日志内容 |
Updated VLAN-VXLAN mapping table binding: $1 |
|
参数解释 |
$1：VLAN-VXLAN映射表绑定物理接入设备配置信息 |
|
举例 |
Updated VLAN-VXLAN mapping table binding: ID: [218b5f2f-e435-4365-a1ab-0eaa03b7fa19] Name: [table] Physical access device: [ c1a3e882-51ad-4847-8dbb-d7d972a5934f ] |
|
日志说明 |
用户进行了修改VLAN-VXLAN映射表与设备的绑定关系的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · Invalid JSON format：无效的JSON格式 · The service is disabled：服务未启动 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Invalid name：无效的名称 · The mapping table does not exist：该映射表不存在 · The physical access device does not exist：指定物理接入设备不存在 · The physical access device is already bound to a VLAN-VXLAN mapping table：指定物理接入设备已绑定VLAN-VXLAN映射表 · No physical access device ID list is specified for the VLAN-VXLAN mapping table：未指定物理接入设备ID列表 · The device type doesn't match：指定设备的类型不匹配 · Duplicate physical access device IDs：物理接入设备ID重复 · The port on the specified device has been bound to a QinQ-VXLAN mapping table：指定设备下的接口已被QinQ-VXLAN映射表绑定 · The QinQ-VXLAN mapping table does not support device binding：QinQ-VXLAN映射表不支持设备级绑定 · Unknown internal server error：未知的内部服务器错误 · You have no privilege to perform this operation：用户无权限执行此操作 · You cannot bind a VLAN-network mapping table to the device：VLAN-Network类型的VLAN-VXLAN映射表不支持设备级绑定 · You cannot edit the PVID, because it is not originated from this mapping：PVID不来源于此映射，不允许修改 · The VLAN-VXLAN, VLAN-network, or QinQ mapping conflicts with a PVLAN mapping on the VNID pools page：VLAN映射和静态的PVLAN映射冲突 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · To configure a global VLAN-VXLAN mapping, you must first enable VXLAN service preconfiguration：网元绑定全局VLAN-VXLAN类型映射表时下不允许切换VXLAN转发预配置开关 · To bind a global VLAN-VXLAN mapping, make sure the global IPv6 option is turned off for the device：绑定全局VLAN-VXLAN映射的设备必须关闭全局IPv6开关 · You cannot bind a global VLAN-VXLAN mapping, because the device is already configured with a donwlink interface：网元已经配置了下行口,不允许绑定全局VLAN-VXLAN映射 · In the network cloud scenario, you cannot configure a global VLAN-VXLAN mapping：网络云场景不支持配置全局VLAN-VXLAN映射绑定 · The device type does not support binding interfaces：该类型的设备不支持接口绑定 · This device type does not support binding VLAN-VXLAN mappings whose effective location is VLAN：当前类型的设备不支持绑定生效位置为VLAN的VLAN-VXLAN映射 · To configure a global VLAN-VXLAN mapping, you must first enable VXLAN service preconfiguration：绑定全局VLAN-VXLAN映射的设备必须开启VXLAN转发预配置开关 · The binding does not exist：指定的绑定关系不存在 · A default encapsulation mapping supports only interface-specific mapping binding：Default封装类型映射关系仅支持接口级映射绑定 · You cannot bind the device to a global VLAN-VXLAN mapping, because subnet gatewayhas been enabled for a device group in the fabric：Fabric内已存在开启子网网关的设备组，不允许绑定全局VLAN-VXLAN映射 |
|
关键字 |
DELETE_VLAN-VXLAN_BINDING_OP |
|
日志内容 |
Deleted VLAN-VXLAN mapping table binding: $1 |
|
参数解释 |
$1：VLAN-VXLAN映射表ID |
|
举例 |
Deleted VLAN-VXLAN mapping table binding: 218b5f2f-e435-4365-a1ab-0eaa03b7fa19 |
|
日志说明 |
用户进行了删除VLAN-VXLAN映射表与所有设备的绑定关系的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · The service is disabled：服务未启动 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · The mapping table does not exist：该映射表不存在 · The binding doesn't exist：该绑定关系不存在 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
CREATE_PORTBIND_OP |
|
日志内容 |
Bound ports to VLAN-VXLAN mapping table: $1 |
|
参数解释 |
$1：VLAN-VXLAN映射表绑定接口配置信息 |
|
举例 |
Bound ports to VLAN-VXLAN mapping table: Mapping table ID: [fe17ff86-82c2-417f-bb2d-47500aad4113] Mapping table name: [1] Device port list: [ [ Device ID: 1a310715-255d-444d-a321-da98764c53ee Device name: 125 Port name: FortyGigE3/4/0/2 Port num: 0x30fa Port untagged VLAN ID: null ] ] |
|
日志说明 |
用户进行了把VLAN-VXLAN映射表与接口绑定的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · Invalid JSON format：无效的JSON格式 · The service is disabled：服务未启动 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Invalid name：无效的名称 · The mapping table does not exist：该映射表不存在 · The physical access device does not exist：指定的物理接入设备不存在 · The port has been bound to another mapping table：指定的设备接口已绑定其它的映射表 · The device type doesn't match：指定设备的类型不匹配 · Duplicate physical access device IDs：物理接入设备ID重复 · Unknown internal server error：未知的内部服务器错误 · Duplicated interfaces exist：已选接口中存在重复的接口 · You have no privilege to perform this operation：用户无权限执行此操作 · A VLAN range has been bound to another vNetwork：存在VLAN范围已被其他虚拟链路层网络绑定 · The VLAN-VXLAN, VLAN-network, or QinQ mapping conflicts with a PVLAN mapping on the VNID pools page：VLAN映射和静态的PVLAN映射冲突 · The PVLAN mapping conflicts with a VLAN-VXLAN, VLAN-network, or QinQ mapping on the VNID pools page：PVLAN映射和静态的VLAN映射冲突 · You cannot bind a vNetwork to both a PVLAN and a VLAN-VXLAN mapping：虚拟链路层网络不能同时绑定PVLAN和VLAN-VXLAN映射 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · The interface of the service leaf device is bound to a resource access template. You cannot apply VLAN-related mappings to the interface：Service Leaf设备的接口被资源接入模板绑定时，不可用于其他映射 · You can bind only VLAN-network mappings to member ports of an edge aggregate interface：聚合边缘接口下的成员接口仅支持绑定VLAN-Network类型映射 · The physical access device already binding a global VLAN-VXLAN mapping cannot binding other VLAN-VXLAN binding：设备已经绑定全局VLAN-VXLAN映射，不允许再绑定其他映射 · The global VLAN-VXLAN mapping cannot binding port：全局VLAN-VXLAN映射不允许绑定接口 · The VLAN ID is invalid or out of range：无效的VLAN ID或者VLAN ID范围错误 · An interface can be bound to one default encapsulation mapping：同一个接口仅支持绑定一个Default封装类型映射关系 · The binding already exists：接口绑定已存在 |
|
关键字 |
UPDATE_PORTBIND_OP |
|
日志内容 |
Updated bindings between ports and QinQ-VXLAN mapping table: $1 |
|
参数解释 |
$1：VLAN-VXLAN映射表绑定接口配置信息 |
|
举例 |
Updated bindings between ports and QinQ-VXLAN mapping table: Mapping table ID: [fe17ff86-82c2-417f-bb2d-47500aad4113] Mapping table name: [1] Device port list: [ [ Device ID: 1a310715-255d-444d-a321-da98764c53ee Device name: 125 Port name: FortyGigE3/4/0/2 Port num: 0x30fa Port untagged VLAN ID: null ] ] |
|
日志说明 |
用户进行了修改VLAN-VXLAN映射表与接口的绑定关系的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · Invalid JSON format：无效的JSON格式 · The service is disabled：服务未启动 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Invalid name：无效的名称 · The mapping table does not exist：该映射表不存在 · The port has been bound to another mapping table：指定的设备接口已绑定其它的映射表 · The physical access device does not exist：指定物理接入设备不存在 · The device type doesn't match：指定设备的类型不匹配 · Duplicate physical access device IDs：物理接入设备ID重复 · The binding between the mapping table and ports doesn't exist：该映射表与接口的绑定关系不存在 · Unknown internal server error：未知的内部服务器错误 · Duplicated interfaces exist：已选接口中存在重复的接口 · You have no privilege to perform this operation：用户无权限执行此操作 · The VLAN-VXLAN, VLAN-network, or QinQ mapping conflicts with a PVLAN mapping on the VNID pools page：VLAN映射和静态的PVLAN映射冲突 · The PVLAN mapping conflicts with a VLAN-VXLAN, VLAN-network, or QinQ mapping on the VNID pools page：PVLAN映射和静态的VLAN映射冲突 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · The interface of the service leaf device is bound to a resource access template. You cannot apply VLAN-related mappings to the interface：Service Leaf设备的接口被资源接入模板绑定时，不可用于其他映射 · The physical access device already binding a global VLAN-VXLAN mapping cannot binding other VLAN-VXLAN binding：设备已经绑定全局VLAN-VXLAN映射，不允许再绑定其他映射 · The global VLAN-VXLAN mapping cannot binding port：全局VLAN-VXLAN映射不允许绑定接口 · An interface can be bound to one default encapsulation mapping：同一个接口仅支持绑定一个Default封装类型映射关系 |
|
关键字 |
UPDATE_PORTBIND_OP |
|
日志内容 |
Updated bindings between ports and QinQ-VXLAN mapping table: $1 |
|
参数解释 |
$1：VLAN-VXLAN映射表绑定接口配置信息 |
|
举例 |
Updated bindings between ports and QinQ-VXLAN mapping table: Mapping table ID: [fe17ff86-82c2-417f-bb2d-47500aad4113] Mapping table name: [1] Device port list: [ [ Device ID: 1a310715-255d-444d-a321-da98764c53ee Device name: 125 Port name: FortyGigE3/4/0/2 Port num: 0x30fa Port untagged VLAN ID: null ] ] |
|
日志说明 |
用户进行了修改VLAN-VXLAN映射表与接口的绑定关系的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · Invalid JSON format：无效的JSON格式 · The service is disabled：服务未启动 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Invalid name：无效的名称 · The mapping table does not exist：该映射表不存在 · The physical access device does not exist：指定物理接入设备不存在 · The device type doesn't match：指定设备的类型不匹配 · Duplicate physical access device IDs：物理接入设备ID重复 · The binding between the mapping table and ports doesn't exist：该映射表与接口的绑定关系不存在 · Unknown internal server error：未知的内部服务器错误 · Duplicated interfaces exist：已选接口中存在重复的接口 · You have no privilege to perform this operation：用户无权限执行此操作 · The VLAN-VXLAN mapping table has been bound to the device. You cannot bind the VLAN-network mapping table to interfaces on the device：VLAN-VXLAN类型的VLAN-VXLAN映射表设备级绑定与VLAN-Network类型的VLAN-VXLAN映射表接口级绑定存在冲突 · You can bind the VLAN-network mapping table only to a device in the fabric for the vNetwork：VLAN-Network类型的VLAN-VXLAN映射表，只允许绑定该虚拟链路层网络对应的Fabric下的设备 · There are ports that are bound to the mapping table：存在端口已绑定到该映射表 · The VLAN-VXLAN, VLAN-network, or QinQ mapping conflicts with a PVLAN mapping on the VNID pools page：VLAN映射和静态的PVLAN映射冲突 · The PVLAN mapping conflicts with a VLAN-VXLAN, VLAN-network, or QinQ mapping on the VNID pools page：PVLAN映射和静态的VLAN映射冲突 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · Non-Downlink interfaces exist：存在非下行口 · The interface of the service leaf device is bound to a resource access template. You cannot apply VLAN-related mappings to the interface：Service Leaf设备的接口被资源接入模板绑定时，不可用于其他映射 · The physical access device already binding a global VLAN-VXLAN mapping cannot binding other VLAN-VXLAN binding：设备已经绑定全局VLAN-VXLAN映射，不允许再绑定其他映射 · The global VLAN-VXLAN mapping cannot binding port：全局VLAN-VXLAN映射不允许绑定接口 · An interface can be bound to one default encapsulation mapping：同一个接口仅支持绑定一个Default封装类型映射关系 |
|
关键字 |
UPDATE_PORTBIND_OP |
|
日志内容 |
Updated bindings between ports and QinQ-VXLAN mapping table: $1 |
|
参数解释 |
$1：VLAN-VXLAN映射表绑定接口配置信息 |
|
举例 |
Updated bindings between ports and QinQ-VXLAN mapping table: Mapping table ID: [fe17ff86-82c2-417f-bb2d-47500aad4113] Mapping table name: [1] Device port list: [ [ Device ID: 1a310715-255d-444d-a321-da98764c53ee Device name: 125 Port name: FortyGigE3/4/0/2 Port num: 0x30fa Port untagged VLAN ID: null ] ] |
|
日志说明 |
用户进行了修改VLAN-VXLAN映射表与接口的绑定关系的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · Invalid JSON format：无效的JSON格式 · The service is disabled：服务未启动 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Invalid name：无效的名称 · The mapping table does not exist：该映射表不存在 · The physical access device does not exist：指定物理接入设备不存在 · The device type doesn't match：指定设备的类型不匹配 · Duplicate physical access device IDs：物理接入设备ID重复 · The binding between the mapping table and ports doesn't exist：该映射表与接口的绑定关系不存在 · Unknown internal server error：未知的内部服务器错误 · Duplicated interfaces exist：已选接口中存在重复的接口 · You have no privilege to perform this operation：用户无权限执行此操作 · The VLAN-VXLAN mapping table has been bound to the device. You cannot bind the VLAN-network mapping table to interfaces on the device：VLAN-VXLAN类型的VLAN-VXLAN映射表设备级绑定与VLAN-Network类型的VLAN-VXLAN映射表接口级绑定存在冲突 · You can bind the VLAN-network mapping table only to a device in the fabric for the vNetwork：VLAN-Network类型的VLAN-VXLAN映射表，只允许绑定该虚拟链路层网络对应的Fabric下的设备 · There are ports that are not bound to the mapping table：存在端口未绑定到该映射表 · The VLAN-VXLAN, VLAN-network, or QinQ mapping conflicts with a PVLAN mapping on the VNID pools page：VLAN映射和静态的PVLAN映射冲突 · The PVLAN mapping conflicts with a VLAN-VXLAN, VLAN-network, or QinQ mapping on the VNID pools page：PVLAN映射和静态的VLAN映射冲突 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · The physical access device already binding a global VLAN-VXLAN mapping cannot binding other VLAN-VXLAN binding：设备已经绑定全局VLAN-VXLAN映射，不允许再绑定其他映射 · The global VLAN-VXLAN mapping cannot binding port：全局VLAN-VXLAN映射不允许绑定接口 |
|
关键字 |
DEL_PORTBIND_OP |
|
日志内容 |
Deleted bindings between ports and VLAN-VXLAN mapping table: $1 |
|
参数解释 |
$1：VLAN-VXLAN映射表ID |
|
举例 |
Deleted bindings between ports and VLAN-VXLAN mapping table: e866fcca-6df6-4c4d-8eb7-418ef487732a |
|
日志说明 |
用户进行了删除VLAN-VXLAN映射表与所有接口的绑定关系的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · The service is disabled：服务未启动 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · The mapping table does not exist：该映射表不存在 · The binding between the mapping table and ports doesn't exist：该映射表与接口的绑定关系不存在 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
BIND_QINQ-VXLAN_PORT_OP |
|
日志内容 |
Bound ports to QinQ-VXLAN mapping table: $1 |
|
参数解释 |
$1：QinQ-VXLAN映射表绑定接口配置信息 |
|
举例 |
Bound ports to QinQ-VXLAN mapping table: Mapping table ID: [fe17ff86-82c2-417f-bb2d-47500aad4113] Mapping table name: [1] Device port list: [ [ Device ID: 1a310715-255d-444d-a321-da98764c53ee Device name: 125 Port name: FortyGigE3/4/0/2 Port num: 0x30fa Port untagged VLAN ID: null ] ] |
|
日志说明 |
用户进行了把QinQ-VXLAN映射表与接口绑定的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · Invalid JSON format：无效的JSON格式 · The service is disabled：服务未启动 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Invalid name：无效的名称 · The mapping table does not exist：该映射表不存在 · The physical access device does not exist：指定的物理接入设备不存在 · The port has been bound to another mapping table：指定的设备接口已绑定其它的映射表 · The device type doesn't match：指定设备的类型不匹配 · Duplicate physical access device IDs：物理接入设备ID重复 · The port has been bound to another QinQ-VXLAN mapping table：指定的接口已被其他QinQ-VXLAN映射表绑定 · A device binding exists on the device to which the specified port belongs：指定接口所属设备已经存在了设备级绑定 · Unknown internal server error：未知的内部服务器错误 · Duplicated interfaces exist：已选接口中存在重复的接口 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · The physical access device already binding a global VLAN-VXLAN mapping cannot binding other VLAN-VXLAN binding：设备已经绑定全局VLAN-VXLAN映射，不允许再绑定其他映射 |
|
关键字 |
UPDATE_QINQ-VXLAN_PORTBIND_OP |
|
日志内容 |
Updated bindings between ports and QinQ-VXLAN mapping table: $1 |
|
参数解释 |
$1：QinQ-VXLAN映射表绑定接口配置信息 |
|
举例 |
Updated bindings between ports and QinQ-VXLAN mapping table: Mapping table ID: [fe17ff86-82c2-417f-bb2d-47500aad4113] Mapping table name: [1] Device port list: [ [ Device ID: 1a310715-255d-444d-a321-da98764c53ee Device name: 125 Port name: FortyGigE3/4/0/2 Port num: 0x30fa Port untagged VLAN ID: null ] ] |
|
日志说明 |
用户进行了修改QinQ-VXLAN映射表与接口绑定关系的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · Invalid JSON format：无效的JSON格式 · The service is disabled：服务未启动 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Invalid name：无效的名称 · The mapping table does not exist：该映射表不存在 · The port has been bound to another mapping table：指定的设备接口已绑定其它的映射表 · The physical access device does not exist：指定物理接入设备不存在 · The device type doesn't match：指定设备的类型不匹配 · Duplicate physical access device IDs：物理接入设备ID重复 · The port has been bound to another QinQ-VXLAN mapping table：指定的接口已被其他QinQ-VXLAN映射表绑定 · A device binding exists on the device to which the specified port belongs：指定接口所属设备已经存在了设备级绑定 · The binding between the mapping table and ports doesn't exist：该映射表与接口的绑定关系不存在 · Unknown internal server error：未知的内部服务器错误 · Duplicated interfaces exist：已选接口中存在重复的接口 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · The interface of the service leaf device is bound to a resource access template. You cannot apply VLAN-related mappings to the interface：Service Leaf设备的接口被资源接入模板绑定时，不可用于其他映射 · The physical access device already binding a global VLAN-VXLAN mapping cannot binding other VLAN-VXLAN binding：设备已经绑定全局VLAN-VXLAN映射，不允许再绑定其他映射 |
|
关键字 |
DELETE_QINQ-VXLAN_PORTBIND_OP |
|
日志内容 |
Deleted bindings between ports and QinQ-VXLAN mapping table: $1 |
|
参数解释 |
$1：QinQ-VXLAN映射表ID |
|
举例 |
Deleted bindings between ports and QinQ-VXLAN mapping table: e866fcca-6df6-4c4d-8eb7-418ef487732a |
|
日志说明 |
用户进行了删除QinQ-VXLAN映射表与所有接口的绑定关系的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · The service is disabled：服务未启动 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · The mapping table does not exist：该映射表不存在 · The binding between the mapping table and ports doesn't exist：该映射表与接口的绑定关系不存在 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
CREATE_VLAN-VXLAN_OP |
|
日志内容 |
Created VLAN-network mapping table: $1 |
|
参数解释 |
$1：VLAN-VXLAN映射表配置信息 |
|
举例 |
Created VLAN-network mapping table: ID: [218b5f2f-e435-4365-a1ab-0eaa03b7fa19] Name: [table] VLAN-network mappings: [ VLAN: [2--13], VXLAN: [4--4], Assignment only: [false], Access mode: [VLAN] ] |
|
日志说明 |
用户进行了创建VLAN-Network映射表的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · Invalid JSON format：无效的JSON格式 · The service is disabled：服务未启动 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Invalid name：无效的名称 · You cannot configure both the vNetwork UUID and the VXLAN ID：虚拟链路层网络UUID与VXLAN存在冲突 · You can bind the VLAN-network mapping table only to a device in the fabric for the vNetwork：无效的虚拟链路层网络UUID · The vNetwork does not exist：指定的虚拟链路层网络不存在 · You cannot configure VXLAN-network mappings for vNetworks automaticallycreated by PBR or NBAC：不允许基于PBR或者NBAC业务创建的虚拟链路层网络配置VLAN-Network映射 · A default encapsulation mapping supports only Ethernet access modeDefault封装类型映射关系仅支持Ethernet接入模式 · A VLAN-VXLAN or VLAN-network mapping table supports only one default encapsulation mapping：同一个VLAN-VXLAN/VLAN-Network映射表仅支持配置一个Default封装类型映射关系 · An interface can be bound to one default encapsulation mapping：同一个接口仅支持绑定一个Default封装类型映射关系 · A default encapsulation mapping does not support rewrite_rules：Default封装类型映射关系不支持配置rewrite_rules信息 · A default encapsulation mapping does not support SVLAN or CVLAN IDs：Default封装类型映射关系不支持填写SVLAN、CVLAN · The start and end VXLAN IDs in a default encapsulation mapping must be identical：Default封装类型映射关系起始VXLAN ID与结束VXLAN ID必须相等 · The encapsulation type in a VLAN-VXLAN or VLAN-network mapping supports only default and Dot1q encapsulation：VLAN-VXLAN/VLAN-Network映射关系封装类型仅支持取值为Default和Dot1q · A VLAN-VXLAN or VLAN-network mapping in VLAN access mode does not support rewrite_rules：接入模式为VLAN的VLAN-VXLAN/VLAN-Network映射关系不支持配置rewrite_rules信息 · A VLAN-VXLAN or VLAN-network mapping supports only inbound rewrite_rules：VLAN-VXLAN/VLAN-Network映射关系配置的rewrite_rules信息仅支持入方向规则 · The rewrite_rules in a VLAN-VXLAN or VLAN-network mapping supports only the STRIP_SVLAN processing method：VLAN-VXLAN/VLAN-Network映射关系配置的rewrite_rules信息仅支持规则处理方式为STRIP_SVLAN · The value of the symmetric parameter must be true for the inbound rewrite_rules in a VLAN-VXLAN or VLAN-network mapping：VLAN-VXLAN/VLAN-Network映射关系配置的rewrite_rules信息入方向规则的symmetric参数只能配置为true · A default encapsulation mapping supports only interface-specific mapping binding：Default封装类型映射关系仅支持接口级映射绑定 · The mapping table source is not supported：暂不支持配置该类型的映射表来源 |
|
关键字 |
UPDATE_VLAN-VXLAN_OP |
|
日志内容 |
Updated VLAN-VXLAN mapping table: $1 |
|
参数解释 |
$1：VLAN-Network映射表配置信息 |
|
举例 |
Updated VLAN-VXLAN mapping table: ID: [218b5f2f-e435-4365-a1ab-0eaa03b7fa19] Name: [table] VLAN-network mappings: [ VLAN: [2--13], VXLAN: [4--4], Assignment only: [false], Access mode: [VLAN] ] |
|
日志说明 |
用户进行了修改VLAN-Network映射表的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · Invalid JSON format：无效的JSON格式 · The service is disabled：服务未启动 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Invalid name：无效的名称 · The VLAN ID is invalid or out of range：无效的VLAN ID或者VLAN ID范围错误 · No name is specified：未指定名称 · Two same mappings exist in the mapping table：映射表中有两个完全相同的映射关系 · Overlapped mappings exist in the mapping table：映射关系存在重叠 · The mapping table does not exist：该映射表不存在 · All mappings in the same mapping table must be the same type：同一个映射表的所有映射关系类型必须一致 · Inconsistent mapping table type and mapping type：映射表的类型和映射关系的类型不一致 · The reserved VLAN ID conflicts with a VLAN ID of a VLAN-VXLAN mapping：存储VLAN与VLAN-VXLAN映射冲突 · Unknown internal server error：未知的内部服务器错误 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · You cannot edit the apply_scope parameter for a global VLAN-VXLAN mapping：全局VLAN-VXLAN映射apply_scope字段不允许修改 · A default encapsulation mapping supports only Ethernet access modeDefault封装类型映射关系仅支持Ethernet接入模式 · A VLAN-VXLAN or VLAN-network mapping table supports only one default encapsulation mapping：同一个VLAN-VXLAN/VLAN-Network映射表仅支持配置一个Default封装类型映射关系 · An interface can be bound to one default encapsulation mapping：同一个接口仅支持绑定一个Default封装类型映射关系 · A default encapsulation mapping does not support rewrite_rules：Default封装类型映射关系不支持配置rewrite_rules信息 · A default encapsulation mapping does not support SVLAN or CVLAN IDs：Default封装类型映射关系不支持填写SVLAN、CVLAN · The start and end VXLAN IDs in a default encapsulation mapping must be identical：Default封装类型映射关系起始VXLAN ID与结束VXLAN ID必须相等 · The encapsulation type in a VLAN-VXLAN or VLAN-network mapping supports only default and Dot1q encapsulation：VLAN-VXLAN/VLAN-Network映射关系封装类型仅支持取值为Default和Dot1q · A VLAN-VXLAN or VLAN-network mapping in VLAN access mode does not support rewrite_rules：接入模式为VLAN的VLAN-VXLAN/VLAN-Network映射关系不支持配置rewrite_rules信息 · A VLAN-VXLAN or VLAN-network mapping supports only inbound rewrite_rules：VLAN-VXLAN/VLAN-Network映射关系配置的rewrite_rules信息仅支持入方向规则 · The rewrite_rules in a VLAN-VXLAN or VLAN-network mapping supports only the STRIP_SVLAN processing method：VLAN-VXLAN/VLAN-Network映射关系配置的rewrite_rules信息仅支持规则处理方式为STRIP_SVLAN · The value of the symmetric parameter must be true for the inbound rewrite_rules in a VLAN-VXLAN or VLAN-network mapping：VLAN-VXLAN/VLAN-Network映射关系配置的rewrite_rules信息入方向规则的symmetric参数只能配置为true · A default encapsulation mapping supports only interface-specific mapping binding：Default封装类型映射关系仅支持接口级映射绑定 |
|
关键字 |
DELETE_VLAN-VXLAN_OP |
|
日志内容 |
Deleted VLAN-VXLAN mapping table: $1 |
|
参数解释 |
$1：VLAN-Network映射表ID |
|
举例 |
Deleted VLAN-network mapping table: 218b5f2f-e435-4365-a1ab-0eaa03b7fa19 |
|
日志说明 |
用户进行了删除VLAN-Network映射表的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · Invalid JSON format：无效的JSON格式 · The service is disabled：服务未启动 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · The mapping table is already bound to ports：该映射表已绑定接口 · The mapping table is already bound to physical access devices：该映射表已绑定物理接入设备 · The mapping table does not exist：该映射表不存在 · Unknown internal server error：未知的内部服务器错误 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_PORTBIND_OP |
|
日志内容 |
Bound ports to VLAN-network mapping table: $1 |
|
参数解释 |
$1：VLAN-Network映射表绑定接口配置信息 |
|
举例 |
Bound ports to VLAN-network mapping table: Mapping table ID: [fe17ff86-82c2-417f-bb2d-47500aad4113] Mapping table name: [1] Device port list: [ [ Device ID: 1a310715-255d-444d-a321-da98764c53ee Device name: 125 Port name: FortyGigE3/4/0/2 Port num: 0x30fa Port untagged VLAN ID: null ] ] |
|
日志说明 |
用户进行了把VLAN-Network映射表与接口绑定的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · Invalid JSON format：无效的JSON格式 · The service is disabled：服务未启动 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Invalid name：无效的名称 · The mapping table does not exist：该映射表不存在 · The physical access device does not exist：指定的物理接入设备不存在 · The device type doesn't match：指定设备的类型不匹配 · Duplicate physical access device IDs：物理接入设备ID重复 · Unknown internal server error：未知的内部服务器错误 · Duplicated interfaces exist：已选接口中存在重复的接口 · You have no privilege to perform this operation：用户无权限执行此操作 · The VLAN-VXLAN mapping table has been bound to the device. You cannot bind the VLAN-network mapping table to interfaces on the device：VLAN-VXLAN类型的VLAN-VXLAN映射表设备级绑定与VLAN-Network类型的VLAN-VXLAN映射表接口级绑定存在冲突 · You can bind the VLAN-network mapping table only to a device in the fabric for the vNetwork：VLAN-Network类型的VLAN-VXLAN映射表，只允许绑定该虚拟链路层网络对应的Fabric下的设备 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · You can bind only VLAN-network mappings to member ports of an edge aggregate interface：聚合边缘接口下的成员接口仅支持绑定VLAN-Network类型映射 · The physical access device already binding a global VLAN-VXLAN mapping cannot binding other VLAN-VXLAN binding：设备已经绑定全局VLAN-VXLAN映射，不允许再绑定其他映射 · An interface can be bound to one default encapsulation mapping：同一个接口仅支持绑定一个Default封装类型映射关系 |
|
关键字 |
UPDATE_PORTBIND_OP |
|
日志内容 |
Updated bindings between ports and QinQ-VXLAN mapping table: $1 |
|
参数解释 |
$1：VLAN-VXLAN映射表绑定接口配置信息 |
|
举例 |
Updated bindings between ports and QinQ-VXLAN mapping table: Mapping table ID: [fe17ff86-82c2-417f-bb2d-47500aad4113] Mapping table name: [1] Device port list: [ [ Device ID: 1a310715-255d-444d-a321-da98764c53ee Device name: 125 Port name: FortyGigE3/4/0/2 Port num: 0x30fa Port untagged VLAN ID: null ] ] |
|
日志说明 |
用户进行了修改VLAN-VXLAN映射表与接口的绑定关系的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · Invalid JSON format：无效的JSON格式 · The service is disabled：服务未启动 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Invalid name：无效的名称 · The mapping table does not exist：该映射表不存在 · The physical access device does not exist：指定物理接入设备不存在 · The device type doesn't match：指定设备的类型不匹配 · Duplicate physical access device IDs：物理接入设备ID重复 · The binding between the mapping table and ports doesn't exist：该映射表与接口的绑定关系不存在 · Unknown internal server error：未知的内部服务器错误 · Duplicated interfaces exist：已选接口中存在重复的接口 · You have no privilege to perform this operation：用户无权限执行此操作 · The VLAN-VXLAN mapping table has been bound to the device. You cannot bind the VLAN-network mapping table to interfaces on the device：VLAN-VXLAN类型的VLAN-VXLAN映射表设备级绑定与VLAN-Network类型的VLAN-VXLAN映射表接口级绑定存在冲突 · You can bind the VLAN-network mapping table only to a device in the fabric for the vNetwork：VLAN-Network类型的VLAN-VXLAN映射表，只允许绑定该虚拟链路层网络对应的Fabric下的设备 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · The interface of the service leaf device is bound to a resource access template. You cannot apply VLAN-related mappings to the interface：Service Leaf设备的接口被资源接入模板绑定时，不可用于其他映射 · The physical access device already binding a global VLAN-VXLAN mapping cannot binding other VLAN-VXLAN binding：设备已经绑定全局VLAN-VXLAN映射，不允许再绑定其他映射 · The global VLAN-VXLAN mapping cannot binding port：全局VLAN-VXLAN映射不允许绑定接口 · An interface can be bound to one default encapsulation mapping：同一个接口仅支持绑定一个Default封装类型映射关系 |
|
关键字 |
DEL_PORTBIND_OP |
|
日志内容 |
Deleted bindings between ports and VLAN-network mapping table: $1 |
|
参数解释 |
$1：VLAN-Network映射表ID |
|
举例 |
Deleted bindings between ports and VLAN-network mapping table: e866fcca-6df6-4c4d-8eb7-418ef487732a |
|
日志说明 |
用户进行了删除VLAN-Network映射表与所有接口的绑定关系的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · The service is disabled：服务未启动 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · The mapping table does not exist：该映射表不存在 · The binding between the mapping table and ports doesn't exist：该映射表与接口的绑定关系不存在 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
CREATE_GWGROUP_OP |
|
日志内容 |
Created device group: $1 |
|
参数解释 |
$1：设备组配置信息 |
|
举例 |
Created device group: ID:[8032909d-47a1-4715-90af-5153ffe39899] Name:[group] MAC:[3c:8c:40:4e:dd:46] Description:[A] Type:[GROUPCGSR] Members:[ ] VTEP IP:[[168.0.0.26]] Connect mode:[VLAN] Firewall for only external traffic:[false] Firewall for external traffic:[false] Firewall for internal traffic:[true] isBind IpPool:[true] isBind VlanRange:[true] Export gateway:[true] DC interconnection:[false] Fabric ID:[9c1d2a72-22fb-4410-b39f-2bdd2db05279] bindIpPools:[ IpPoolName: 承载网 IpPoolName: 防火墙 IpPoolName: 负载分担 IpPoolName: 路由器互通 IpPoolName: 安全内网 IpPoolName: 虚拟设备管理 ] bindVlanRanges:[ VlanRangeName: vlan池 ] Control mode:[EVPN] |
|
日志说明 |
用户进行了创建设备组的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · The service is disabled：服务未启动 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · Unknown internal server error：未知的内部服务器错误 · The device group already exists：该设备组已存在 · Invalid name：无效的名称 · Invalid parameter：无效的配置参数 · Invalid description：无效的描述信息 · Invalid IP address：无效的IP地址 · Invalid IP address pool name：无效的地址池名称 · The device type and the border device control mode do not match：成员设备类型与设备组的控制模式不匹配 · The device group's MAC address conflicts with the VM's MAC address：设备组的MAC地址与虚拟机的MAC地址冲突 · The IP address pool does not exist：指定的地址池不存在 · The IP address pool has been bound to another device group：指定的地址池已绑定其他设备组 · The default IP address pool cannot be bound to device groups：设备组不能绑定默认地址池 · The VLAN pool does not exist：指定的VLAN池不存在 · The VLAN pool has been bound to another device group：指定的VLAN池已绑定其他设备组 · The default VLAN pool cannot be bound to device groups：设备组不能绑定默认VLAN池 · Device groups that use the default IP address pool cannot be bound to other IP address pools：使用默认地址池的设备组不能再绑定其他地址池 · Device groups that use the default VLAN pool cannot be bound to other VLAN pools：使用默认VLAN池的设备组不能再绑定其他VLAN池 · Do not set the MAC address to reserved MAC address for the controller：控制组件保留的MAC地址不允许使用 · The device group's MAC address conflicts with the NE’s default MAC address：设备组的MAC地址与网元的默认MAC地址冲突 · A device group can be bound to only one IP address pool of each type：每种类型的地址池设备组只能绑定一个 · The gateway group is not bound to the specified type of IP address pool：未绑定指定类型的地址池，不能满足基本组网需求 · Device groups cannot be bound to security external IP address pools：设备组不能绑定安全外网地址池 · The network element is being deleted or being removed from the gateway group：该网元正在删除或从设备组中移出 · No fabric is specified for the device group：设备组未指定Fabric · The NE and the device group to which the NE belongs must be in the same fabric：网元设备和所属设备组的Fabric必须相同 · You must set the value of the export gateway field, the value of the DC interconnection field, or both values to true：出口网关和DC互联需至少有一个取值为true · You must specify the export gateway, DC interconnection, or both：出口网关和DC互联至少要指定一个 · Cannot specify a VTEP IP address in the VTEP IP address pool：指定的VTEP IP地址在VTEP IP地址池范围内，不允许配置 · Cannot edit the subnet gateway feature for device groups on the fabric when asymmetric IRB is enabled：当Fabric的非对称IRB转发开关开启时，不允许修改设备组的子网网关开关 · You have no privilege to perform this operation：用户无权限执行此操作 · Not enough IP address pools：地址池个数不足 · The VTEP IP already exists：指定的VTEP IP地址已存在 · The third-party firewall deployment mode is invalid：无效的边界设备对接第三方防火墙参数 · The third-party firewall option must be set to Off when the network cloud feature is enabled：网络云场景开启时，边界设备第三方防火墙不允许配置为开启状态 · The network position must be border gateway when the device group is a remote device group：当设备组为远端设备组时，网络位置参数的取值必须为出口网关 · The connection mode must be IPs from different networks when the device group is a remote device group：当设备组为远端设备组时，连接方式参数的取值必须为VLAN跨网段 · The connection mode cannot be edited when the device group is a remote device group：当设备组为远端设备组时，连接方式不允许修改 · When the device group is a remote device group, the value for the firewall service parameter must be IPv4 External Traffic：远端设备组仅支持外网流量做防火墙业务 · Please select a Tenant Carrier FW Internal Network address pool：未绑定租户承载防火墙内网地址池 · You can select only one custom Tenant Carrier FW Internal Network address pool：只能绑定一个自定义的租户承载防火墙内网地址池 · An API request cannot contain the third_fw_security_option parameter together with the third_fw_status or fw_access_mode parameter：对接第三方防火墙安全模式参数与第三方防火墙参数或防火墙接入模式参数冲突 · The value for the third-party firewall option is invalid：无效的第三方防火墙状态开关参数 · The value for the firewall deployment mode is invalid：无效的防火墙接入模式参数 · Only DC Interconnection is selected for the position of the device group. You cannot configure remote device group, subnet gateway, third-party firewall deployment mode, or multi-active HA mode：当设备组的网络位置仅为DC间互联时，不支持配置远端设备组，子网网关和对接第三方防火墙模式，不支持配置HA模式为多活 · The VLAN pool name is invalid：无效的VLAN池名称 · The MAC address conflicts with the network MAC address：MAC地址与虚拟链路网络的MAC地址冲突 · The value for the M-LAG route backup parameter is invalid：无效的M-LAG路由备份参数 · You can enable M-LAG route backup for a device group only when its HA mode is M-LAG：当设备组的HA部署模式非M-LAG时，不允许开启设备组的M-LAG路由备份开关 · You must specify a MAC address if the HA mode is M-LAG：HA部署模式为M-LAG时，MAC地址不能为空 · You must disable the third-party firewall when the position of the device group is service leaf：创建设备组的网络位置为Service Leaf时，第三方防火墙必须关闭 · You cannot select any other position when the position of the device group is service leaf：设备组的网络位置为Service Leaf时，不支持选择其他网络位置 · The firewall deployment mode must be hairpin when the position of the device group is service leaf：设备组的网络位置为Service Leaf时，防火墙接入模式必须为旁挂 · You must disable DRNI route backup when the position of the device group is service leaf：设备组的网络位置为Service Leaf时，DRNI路由备份必须为关闭 · You must disable the subnet gateway feature when the position of the device group is service leaf：设备组的网络位置为Service Leaf时，子网网关必须为关闭 · You cannot set the HA mode to multi-active when the position of the device group is service leaf：设备组的网络位置为Service Leaf时，HA部署模式不支持多活 · You cannot enable the third-party firewall when the position of the device group is service leaf：设备组的网络位置为Service Leaf时，第三方防火墙不允许配置为开启状态 · You cannot enable the third-party firewall when the position of the device group is border gateway and the firewall deployment mode is disabled：设备组的网络位置为出口网关且防火墙接入模式为关闭时，第三方防火墙不允许配置为开启状态 · You cannot configure the IP address pool or VLAN pool, because the position of the device group is service leaf or border gateway with the firewall deployment mode disabled：设备组的网络位置为Service Leaf或网络位置为出口网关且防火墙接入模式为关闭时，不支持配置地址池和VLAN池 · The connection mode must be IPs from different networks when the position of the device group is service leaf or border gateway with the firewall deployment mode disabled：设备组的网络位置为Service Leaf或网络位置为出口网关且防火墙接入模式为关闭时，连接方式必须为VLAN跨网段 · The network position of a remote device group must be border gateway or service leaf：当设备组为远端设备组时，网络位置参数的取值必须为出口网关或者Service Leaf · You cannot specify a device group for service leaf deployment in the network cloud scenario：网络云场景开启时，设备组网络位置不允许配置为Service Leaf · In the network cloud scenario, you cannot set firewall deployment to off for a device group used for border gateway deployment：网络云场景开启时，网络位置为出口网关的设备组不允许配置防火墙接入模式为关闭 · A fabric can have only one device group enabled with fabric interconnection：Fabric中只能添加一个Fabric间互通设备组 · If the position of a device group is set to fabric interconnection, you must specify the AS for the fabric：设备组所属网络位置为Fabric间互通，其所属Fabric必须指定AS号 · The specified Loopback0 IP has been used by another auto deployment device information：指定的VTEP IP地址不允许在自动化部署的设备信息列表中 · You cannot enable subnet gateway for the device group, because some devices in thefabric have been bound to global VLAN-VXLAN mappings：Fabric内已有设备绑定全局VLAN-VXLAN映射，不允许开启子网网关 · The fw_for_external and fw_for_internal fields cannot both be set to false：fw_for_external和fw_for_internal字段不能同时为false |
|
关键字 |
UPDATE_GWGROUP_OP |
|
日志内容 |
Updated device group: $1 |
|
参数解释 |
$1：设备组配置信息 |
|
举例 |
Updated device group: ID:[8032909d-47a1-4715-90af-5153ffe39899] Name:[group] MAC:[3c:8c:40:4e:dd:46] Description:[A] Type:[GROUPCGSR] Members:[ ] VTEP IP:[[168.0.0.26]] Connect mode:[VLAN] Firewall for only external traffic:[false] Firewall for external traffic:[false] Firewall for internal traffic:[true] isBind IpPool:[true] isBind VlanRange:[true] Export gateway:[true] DC interconnection:[false] Fabric ID:[9c1d2a72-22fb-4410-b39f-2bdd2db05279] bindIpPools:[ IpPoolName: 承载网 IpPoolName: 防火墙 IpPoolName: 负载分担 IpPoolName: 路由器互通 IpPoolName: 安全内网 IpPoolName: 虚拟设备管理 ] bindVlanRanges:[ VlanRangeName: vlan池 ] Control mode:[EVPN] |
|
日志说明 |
用户进行了修改设备组的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · The service is disabled：服务未启动 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · Unknown internal server error：未知的内部服务器错误 · Invalid description：无效的描述信息 · Invalid parameter：无效的配置参数 · Invalid IP address pool name：无效的地址池名称 · The device group is in use：设备组正在使用 · The device group doesn't exist：设备组不存在 · The device type and the border device control mode do not match：成员设备类型与设备组的控制模式不匹配 · The device group's MAC address conflicts with the VM's MAC address：设备组的MAC地址与虚拟机的MAC地址冲突 · The IP address pool does not exist：指定的地址池不存在 · The IP address pool has been bound to another device group：指定的地址池已绑定其他设备组 · The default IP address pool cannot be bound to device groups：设备组不能绑定默认地址池 · The VLAN pool does not exist：指定的VLAN池不存在 · The VLAN pool has been bound to another device group：指定的VLAN池已绑定其他设备组 · The default VLAN pool cannot be bound to device groups：设备组不能绑定默认VLAN池 · Device groups that use the default IP address pool cannot be bound to other IP address pools：使用默认地址池的设备组不能再绑定其他地址池 · Device groups that use the default VLAN pool cannot be bound to other VLAN pools：使用默认VLAN池的设备组不能再绑定其他VLAN池 · Do not set the MAC address to reserved MAC address for the controller：控制组件保留的MAC地址不允许使用 · The device group's MAC address conflicts with the NE’s default MAC address：设备组的MAC地址与网元的默认MAC地址冲突 · A device group can be bound to only one IP address pool of each type：每种类型的地址池设备组只能绑定一个 · The gateway group is not bound to the specified type of IP address pool：未绑定指定类型的地址池，不能满足基本组网需求 · Device groups cannot be bound to security external IP address pools：设备组不能绑定安全外网地址池 · Please make sure none of the selected IP address pools contains allocated IP addresses：设备组不能解绑已经分配IP地址的地址池 · Please make sure none of the selected VLAN pools contains allocated VLANs：设备组不能解绑已经分配VLAN的VLAN池 · The network element is being deleted or being removed from the gateway group：该网元正在删除或从设备组中移出 · Cannot modify the work mode of a device group with the EVPN network type：无法修改EVPN网络类型的设备组的工作模式 · The export gateway cannot be edited：出口网关不能修改 · The DC interconnection cannot be edited：DC互联不允许修改 · Cannot unbind the device group from the fabric because some member devices in the group have been bound to the fabric：设备组的成员设备已绑定Fabric，设备组不允许与Fabric解绑 · Before binding a device group to a fabric, unbind the group from its original fabric：修改设备组绑定的Fabric时，需先解绑再进行重新绑定操作 · Cannot disable the subnet gateway feature for device groups on the fabric when asymmetric IRB is enabled：当Fabric的非对称IRB转发开关开启时,不允许关闭设备组的子网网关开关 · You have no privilege to perform this operation：用户无权限执行此操作 · Not enough IP address pools：地址池个数不足 · The VTEP IP already exists：指定的VTEP IP地址已存在 · The third-party firewall option must be set to Off when the network cloud feature is enabled：网络云场景开启时，边界设备第三方防火墙不允许配置为开启状态 · Please select a Tenant Carrier FW Internal Network address pool：未绑定租户承载防火墙内网地址池 · You can select only one custom Tenant Carrier FW Internal Network address pool：只能绑定一个自定义的租户承载防火墙内网地址池 · Cannot change the third-party firewall deployment mode. The border gateway to which the device group belongs has been bound to a vRouter：设备组所属的出口网关已绑定虚拟路由器，不允许修改边界设备对接第三方防火墙开关 · The is_remote_group field cannot be edited：设备组的is_remote_group字段不允许修改 · An API request cannot contain the third_fw_security_option parameter together with the third_fw_status or fw_access_mode parameter：对接第三方防火墙安全模式参数与第三方防火墙参数或防火墙接入模式参数冲突 · In the network cloud scenario, the firewall deployment mode cannot be edited：在网络云场景下，防火墙接入模式不允许修改 · The firewall deployment mode for a vRouter-attached device group cannot be hairpin mode when the IP addresses or subnets in the vRouter-attached external network use different firewall settings：虚拟路由器绑定的同一外部网络下的外网子网流量是否过防火墙的行为不一致时，虚拟路由器绑定的设备组的防火墙接入模式不能为旁挂 · The device group is a border gateway member. You cannot use the device group for DCI, because the tenant already has a border gateway that contains a member used for DCI：当设备组对应的租户下存在成员开启DC间互联功能的出口网关时，其网络位置不支持开启DC间互联功能 · The device group cannot be used for DCI, because it is used in a border gateway that contains multiple members：当设备组对应的出口网关存在多个成员时，其网络位置不支持开启DC间互联功能 · The VLAN pool name is invalid：无效的VLAN池名称 · The MAC address conflicts with the network MAC address：MAC地址与虚拟链路网络的MAC地址冲突 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · The value for the M-LAG route backup parameter is invalid：无效的M-LAG路由备份参数 · You can enable M-LAG route backup for a device group only when its HA mode is M-LAG：当设备组的HA部署模式非M-LAG时，不允许开启设备组的M-LAG路由备份开关 · You can add a maximum of two member devices to the device group if the HA mode is M-LAG：HA部署模式为M-LAG时，设备组不能配置超过两个成员 · Cannot switch the HA mode of a device group from multi-active or M-LAG to IRF：当设备组HA模式为多活或M-LAG时，不能切换为IRF模式 · You can switch between the IRF, multi-active, and M-LAG HA modes：HA部署模式仅支持在IRF、多活和M-LAG间切换 · The service leaf position cannot be edited：Service Leaf网络位置不能修改 · You cannot disable the firewall feature for a device group when its firewall deployment mode is hairpin or inline and its network position is border gateway：防火墙接入模式为旁挂或直连且网络位置为出口网关的设备组不可将防火墙接入模式修改成关闭 · You cannot edit the firewall deployment mode for a device group when its firewall feature is disabled and its network position is border gateway：防火墙接入模式为关闭且网络位置为出口网关的设备组不允许修改防火墙接入模式 · If the network positions of a device group include fabric interconnection, you cannot cancel this network position：具备Fabric间互通能力的设备组不能取消勾选Fabric间互通网络位置 · You cannot set the value for the fw_for_internal field to true for a device group, because its positions include border gateway and fabric interconnection or border gateway and DC interconnection：出口网关和Fabric间互通或者出口网关和DC间互联同时取值为true时不可指定内网流量 · If SNAT is disabled for the listener associated with a load balancer, you cannot set the network position of the device group associated with that load balancer as follows: 1. Border gateway and fabric interconnection. 2. Border gateway, fabric interconnection, and DC interconnection：负载均衡器的监听器用户源地址转换开关关闭时，不允许出口网关设备组的网络位置修改为出口网关和Fabric间互通或者出口网关+Fabric间互通+DC间互联 · If SNAT is disabled for the listener associated with a load balancer, you cannot set the network positions of the device group associated with that load balancer to border gateway and fabric interconnection：负载均衡器的监听器用户源地址转换开关关闭时，不允许出口网关设备组的网络位置修改为出口网关和Fabric间互通 · If the network positions of a device group include DC interconnection, you cannot cancel this network position：具备DC间互联能力的设备组不能取消勾选DC间互联网络位置 · A fabric can have only one device group enabled with fabric interconnection：Fabric中只能添加一个Fabric间互通设备组 · When the network positions of a device group include fabric interconnection, each of its member devices must have a VTEP IP address：当设备组的网络位置为Fabric间互通时，其成员设备的VTEP IP不能为空 · If the position of a device group is set to fabric interconnection, you must specify the AS for the fabric：设备组所属网络位置为Fabric间互通，其所属Fabric必须指定AS号 · A border gateway in IRF HA mode can have only one member：IRF模式的设备组只能存在一个成员 · When the HA mode of the device group is multi-active or M-LAG, switching the HA mode is not supported：当设备组HA部署模式为多活或M-LAG时，不支持切换HA部署模式 · The specified Loopback0 IP has been used by another auto deployment device information：指定的VTEP IP地址不允许在自动化部署的设备信息列表中 · You cannot enable subnet gateway for the device group, because some devices in thefabric have been bound to global VLAN-VXLAN mappings：Fabric内已有设备绑定全局VLAN-VXLAN映射，不允许开启子网网关 |
|
关键字 |
DELETE_GWGROUP_OP |
|
日志内容 |
Deleted device group: $1 |
|
参数解释 |
$1：设备组ID |
|
举例 |
Deleted device group: 741f1414-d71e-4775-acf9-d68bbb55e803 |
|
日志说明 |
用户进行了删除设备组的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · The service is disabled：服务未启动 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · The device group doesn't exist：设备组不存在 · The device group is in use：设备组正在使用 · The device group is being used by DC connection：设备组正在被数据中心连接使用 · You have no privilege to perform this operation：用户无权限执行此操作 · Failed to delete the device group because some members in the group are M-LAG system members：设备组删除失败，该设备组中存在已经创建了M-LAG系统的设备成员 · You cannot delete a service leaf device or remove the device from the device group if the following conditions exist:The device is already bound to a resource access template.The service leaf firewall associated with the device is already bound to a vRouter：Service Leaf设备已被资源接入模板绑定或该设备关联的Service Leaf防火墙已被虚拟路由器绑定，该设备不允许删除或者解关联设备组 · You cannot delete the device group, because some members in the group have interconnect interface bindings：设备组的设备关联了互联接口，不允许删除设备组 · Failed to delete the device group because some members in the group have been bound to border gateways：设备组删除失败，该设备组中存在绑定了外网出口的设备组成员 |
|
关键字 |
CREATE_IPPOOL_OP |
|
日志内容 |
Created IP address pool: $1 |
|
参数解释 |
$1：地址池配置信息 |
|
举例 |
Created IP address pool: ID: [b12059c8-4f72-4efd-af06-8707d836f275] Name: [huha_lb] Type: [TENANT_SUPPORT_LB] CIDR: [19.19.19.0/24] Allocated: [false] Can be bound: [false] Address range list [ { Start IP: [19.19.19.1] End IP: [19.19.19.4] Status: [false] } { Start IP: [19.19.19.6] End IP: [19.19.19.10] Status: [false] } ] IPv6 address range list [ { Start IP: [34:0:0:0:0:0:0:10] End IP: [34:0:0:0:0:0:0:20] Status: [false] Assigned addresses: [[]] } { Start IP: [34:0:0:0:0:0:0:1] End IP: [34:0:0:0:0:0:0:3] Status: [false] Assigned addresses: [[]] } ] |
|
日志说明 |
用户进行了创建地址池的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · The service is disabled：服务未启动 · The controller is not the active leader：该控制组件不是主Leader · Invalid JSON format：无效的JSON格式 · Invalid name：无效的名称 · Invalid CIDR：无效的网段地址 · The IP address pool is already used：地址池正在使用 · The IP address pool ID already exists：地址池ID已经存在 · The CIDR of the IP address pool is invalid：地址池指定的子网无效 · Configuration recovery is in progress：配置正在恢复过程中 · The IP address pool type is already exist：地址池类型已经存在 · The IP address pool name already exists：地址池名称已经存在 · The gateway address must belong to the specified network：网关地址不在网段地址范围内 · The start IP address and end IP address must belong to the specified network：起始IP地址或结束IP地址不在网段地址范围内 · The IP address range overlaps with another one：该地址段与其它地址段的IP地址重叠 · The status field is read only：状态字段为只读字段 · The start IP address or end IP address cannot be a broadcast address or network address：起始IP地址和结束IP地址不能为广播地址和网络地址 · The gateway address cannot be a broadcast address or network address：网关地址不能为广播地址和网络地址 · Unknown internal server error：未知的内部服务器错误 · For each IP address pool type, only one default address pool is allowed：每种类型的默认地址池只能添加一个 · The network address overlaps with a network address in another IP address pool：该网段地址与其他地址池的网段地址重叠 · Network addresses cannot be configured for this type of address pools：该类型地址池不支持配置网段地址 · Address ranges are required for this type of address pools：该类型地址池的地址段不能为空 · The team can have only one vRouter interconnection IP pool and the pool must be configured as the default IP pool：一个集群内只能创建一个虚拟路由器互通网络类型的地址池，且该地址池必须为默认地址池 · Only one address range can be configured for a management network address pool：管理网地址池仅支持配置单个地址范围 · The next hop is required：未指定下一跳 · A physical management network IP address pool cannot contain any management IP addresses：物理管理网络类型的IP地址池不允许包含已存在的管理IP · Cannot create a default address pool for security external networks when a FW service resource is bound to a vRouter：存在已被虚拟路由器绑定的防火墙服务资源，不能创建默认安全外网地址池 · You have no privilege to perform this operation：用户无权限执行此操作 · The system supports only one multicast address pool and the multicast address pool must be the default IP address pool：仅允许有一个组播地址池且只能为默认IP地址池 · The multicast address pool can contain only multicast addresses, which cannot be permanent group addresses：地址段中的所有地址必须为组播地址且不能包含永久组的组播地址 · The default group or data group cannot be a multicast address in the multicast address pool：L3组播中手动配置的默认组和数据组地址不允许在组播地址池中 · Failed to apply the management IP pool. Please make sure none of the added IP ranges contains network addresses, broadcast addresses, or anycast addresses：虚拟管理网络和物理管理网络类型地址池的地址段不支持网络地址、广播地址或任播地址 · Subnet mask and prefix length are not configurable for this type of IP address pools：该类型IP地址池不支持配置掩码/前缀长度 · When you specify an address range for an address pool, make sure none of the interconnect interface addresses belong to that address range：IP地址池的网段不能与互联接口的网段冲突 |
|
关键字 |
MODIFY_IPPOOL_OP |
|
日志内容 |
Updated IP address pool: $1 |
|
参数解释 |
$1：地址池配置信息 |
|
举例 |
Updated IP address pool: ID: [4272f686-1faf-4587-b7a2-2f68246666e2] Name: [1222] Type: [NGFW_MANAGE] CIDR: [10.1.1.0/24] Nexthop: [10.0.0.254] Allocated: [false] Can be bound: [false] Address range list [ { Start IP: [19.19.19.1] End IP: [19.19.19.4] Status: [false] } { Start IP: [19.19.19.6] End IP: [19.19.19.10] Status: [false] } ] IPv6 address range list [ { Start IP: [34:0:0:0:0:0:0:10] End IP: [34:0:0:0:0:0:0:20] Status: [false] Assigned addresses: [[]] } { Start IP: [34:0:0:0:0:0:0:1] End IP: [34:0:0:0:0:0:0:3] Status: [false] Assigned addresses: [[]] } ] |
|
日志说明 |
用户进行了修改地址池的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · The service is disabled：服务未启动 · The controller is not the active leader：该控制组件不是主Leader · Invalid name：无效的名称 · Invalid JSON format：无效的JSON格式 · The CIDR of the IP address pool is invalid：地址池指定的子网无效 · The IP address pool name already exists：地址池名称已经存在 · The IP address pool is already used：不允许修改正在使用的地址池 · The IP address range overlaps with another one：该地址段与其它地址段的IP地址重叠 · The network address field is read only：网段地址为只读字段 · The status field is read only：状态字段为只读字段 · The start IP address and end IP address must belong to the specified network：起始IP地址或结束IP地址不在网段地址范围内 · The start IP address or end IP address cannot be a broadcast address or network address：起始IP地址和结束IP地址不能为广播地址和网络地址 · Address ranges are required for this type of address pools：该类型地址池的地址段不能为空 · Unknown internal server error：未知的内部服务器错误 · The VTEP IP address pool has been used and cannot be expanded：VTEP类型的地址池已被使用，不允许扩容 · The management network address pool has been used by the deployment resource pool and cannot be modified：已被管理部署资源池引用的管理网地址池不允许修改 · Only one address range can be configured for a management network address pool：管理网地址池仅支持配置单个地址范围 · Address ranges are required for this type of address pools：该类型地址池的地址段不能为空 · You have no privilege to perform this operation：用户无权限执行此操作 · The multicast address pool can contain only multicast addresses, which cannot be permanent group addresses：地址段中的所有地址必须为组播地址且不能包含永久组的组播地址 · The default group or data group cannot be a multicast address in the multicast address pool：L3组播中手动配置的默认组和数据组地址不允许在组播地址池中 · Failed to apply the management IP pool. Please make sure none of the added IP ranges contains network addresses, broadcast addresses, or anycast addresses：虚拟管理网络和物理管理网络类型地址池的地址段不支持网络地址、广播地址或任播地址 · The gateway address is assigned to an IP address pool used for automatic deployment：网关地址与其它自动化上线地址池网关地址冲突 · Subnet mask and prefix length are not configurable for this type of IP address pools：该类型IP地址池不支持配置掩码/前缀长度 · Make sure the IP address pool of the general network type specified for the resource access template does not overlap with any subnets of the vRouter associated with the service leaf firewall bound to the resource access template：Service Leaf资源接入模板使用的通用网络地址池地址段不能与使用该资源接入模板的Service Leaf类型防火墙关联的虚拟路由器的子网网段重叠 · When you specify an address range for an address pool, make sure none of the interconnect interface addresses belong to that address range：IP地址池的网段不能与互联接口的网段冲突 |
|
关键字 |
DELETE_IPPOOL_OP |
|
日志内容 |
Deleted IP address pool: $1 |
|
参数解释 |
$1：地址池ID |
|
举例 |
Deleted IP address pool: 4272f686-1faf-4587-b7a2-2f68246666e2 |
|
日志说明 |
用户进行了删除地址池的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · Invalid JSON format：无效的JSON格式 · The service is disabled：服务未启动 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · The IP address pool doesn't exist：地址池不存在 · The IP address pool is already used：不允许删除正在使用的地址池 · Unknown internal server error：未知的内部服务器错误 · Failed to delete the security external IP address pool. The pool has been bound to a VNF virtual gateway resource：该安全外网地址池已被VNF虚拟网关资源绑定，不允许删除 · The address pool has been used by the deployment resource pool and cannot be deleted：已被管理部署资源池引用的地址池不允许删除 · You have no privilege to perform this operation：用户无权限执行此操作 · The address pool that has been referenced by the resource access template is not allowed to be deleted：已被资源接入模板引用的地址池不允许删除 |
|
关键字 |
CREATE_GWVLANRANGE_OP |
|
日志内容 |
Created device group VLAN range: $1 |
|
参数解释 |
$1：VLAN池配置信息 |
|
举例 |
Created device group VLAN range: VLAN range ID: [445dd33e-3b27-44a5-b7f1-c6fb0a859311] VLAN range name: [newRange] Start VLAN: [11] End VLAN: [4011] VLAN allocated: [false] VLAN needBind: [false] |
|
日志说明 |
用户进行了创建VLAN池的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · The service is disabled：服务未启动 · The controller is not the active leader：该控制组件不是主Leader · Invalid JSON format：无效的JSON格式 · Invalid name：无效的名称 · The VLAN pool is already used：VLAN池正在使用 · The VLAN pool ID already exists：VLAN池ID已经存在 · The VLAN pool name already exists：VLAN池名字已经存在 · The VLAN pool overlaps with another one：VLAN池与其他重叠 · The VLAN ID is invalid or out of range：VLAN ID无效或超范围 · The vRouter interconnection network VLAN pool already exists：虚拟路由器互通网络类型的VLAN池已存在 · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · The VLAN range cannot contain the VLAN IDs already assigned to cloud private lines：VLAN范围不能包含云专线指定的VLAN ID · You have no privilege to perform this operation：用户无权限执行此操作 · Cannot specify both the range and range_list parameters：range和range_list不能同时配置 · The end VLAN ID must be greater than or equal to the start VLAN ID：结束值必须大于等于起始值 · VLAN range conflicts exist：存在VLAN范围冲突 · The VLAN ID cannot be identical to the VLAN ID configured for the M-LAG routed peer-link between two border devices：VLAN ID不能与边界设备的M-LAG互联链路下的VLAN ID冲突 · The VLAN ID pool cannot include the VLAN ID or subinterface number of any interconnect interface：VLAN ID不能与互联接口的互联VLAN或子接口编号冲突 · The VLAN pool overlaps with a global VLAN-VXLAN mapping：全局VLAN-VXLAN映射VLAN与VLAN池范围冲突 |
|
关键字 |
UPDATE_GWVLANRANGE_OP |
|
日志内容 |
Updated device group VLAN range: $1 |
|
参数解释 |
$1：VLAN池配置信息 |
|
举例 |
Updated border device VLAN range: VLAN range ID: [445dd33e-3b27-44a5-b7f1-c6fb0a859311] VLAN range name: [newRange] Start VLAN: [12] End VLAN: [4011] VLAN allocated: [false] VLAN needBind: [false] |
|
日志说明 |
用户进行了修改VLAN池的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · The service is disabled：服务未启动 · The controller is not the active leader：该控制组件不是主Leader · Invalid JSON format：无效的JSON格式 · The VLAN ID is invalid or out of range：VLAN ID无效或超范围 · Invalid name：无效的名称 · The VLAN pool is already used：不允许修改正在使用的VLAN池 · The VLAN pool doesn't exist：VLAN池不存在 · Unknown internal server error：未知的内部服务器错误 · The VLAN pool overlaps with another VLAN pool bound to the same device group：该VLAN池与其绑定到同一设备组的VLAN池范围重叠 · The new VLAN range of the vRouter interconnection network VLAN pool must include the original VLAN range of the pool：修改后的虚拟路由器互通网络类型的VLAN池范围必须包含原有的VLAN池范围 · The VLAN range cannot contain the VLAN IDs already assigned to cloud private lines：VLAN范围不能包含云专线指定的VLAN ID · You have no privilege to perform this operation：用户无权限执行此操作 · You can use only the range_list parameter to edit VLAN ranges when multiple VLAN ranges exist：已存在多个VLAN范围，不允许使用range字段进行修改 · Cannot specify both the range and range_list parameters：range和range_list不能同时配置 · The end VLAN ID must be greater than or equal to the start VLAN ID：结束值必须大于等于起始值 · VLAN range conflicts exist：存在VLAN范围冲突 · The VLAN ID cannot be identical to the VLAN ID configured for the M-LAG routed peer-link between two border devices：VLAN ID不能与边界设备的M-LAG互联链路下的VLAN ID冲突 · The VLAN ID pool cannot include the VLAN ID or subinterface number of any interconnect interface：VLAN ID不能与互联接口的互联VLAN或子接口编号冲突 · The VLAN pool overlaps with a global VLAN-VXLAN mapping：全局VLAN-VXLAN映射VLAN与VLAN池范围冲突 |
|
关键字 |
DELETE_GWVLANRANGE_OP |
|
日志内容 |
Deleted device group VLAN range: $1 |
|
参数解释 |
$1：VLAN池ID |
|
举例 |
Deleted device group VLAN range: 8688051f-5095-4b27-93c1-89922ff9b0b6 |
|
日志说明 |
用户进行了删除VLAN池的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · Invalid JSON format：无效的JSON格式 · The service is disabled：服务未启动 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · The VLAN pool doesn't exist：VLAN池不存在 · The VLAN pool is already used：不允许删除正在使用的VLAN池 · The VLAN pool is already used by device group：VLAN池正在被设备组使用 · vRouter interconnection network VLAN pools cannot be deleted：虚拟路由器互通网络类型的VLAN池不可删除 · Unknown internal server error：未知的内部服务器错误 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
ACTION_CREATE_VXLANPOOL |
|
日志内容 |
Created VXLAN pool: $1 |
|
参数解释 |
$1：VXLAN池配置信息 |
|
举例 |
Created VXLAN pool: VXLAN pool ID:[8ca117d1-b2ea-4538-9464-6a924f7fdf89] VXLAN pool name:[B] Start VNI:[3] End VNI:[3] VXLAN pool allocated:[false] |
|
日志说明 |
用户进行了创建VXLAN池的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · Invalid JSON format：无效的JSON格式 · The service is disabled：服务未启动 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · Invalid name：无效的名称 · Invalid start VNI value：无效的起始值 · Invalid end VNI value：无效的结束值 · VNI value is out of range：起始值或结束值超出范围 · The name is required：名称不能为空 · The range is required：range字段不能为空 · The start value is required：起始值不能为空 · The end value is required：结束值不能为空 · The VXLAN pool name already exists,：VXLAN池名称已存在 · The VXLAN pool ID already exists：VXLAN池ID已存在 · The end VXLAN ID must be greater than or equal to the start VXLAN ID：结束值必须大于等于起始值 · The VXLAN pool overlaps with another VXLAN pool.：VXLAN池与其他VXLAN池重叠 · The VXLAN range cannot contain existing segment IDs or mapping segment IDs：VXLAN池范围与segment ID或映射segment ID重叠 · You have no privilege to perform this operation：用户无权限执行此操作 · Cannot specify both the range and range_list parameters：range和range_list不能同时配置 · VXLAN range conflicts exist：存在VXLAN范围冲突 · The VXLAN range contains the reserved VXLAN ID configured for the device deployment template or the M-LAG system：指定的VXLAN范围与自动化模板或M-LAG系统的保留VXLAN重叠 · The smoothEnd field is read-only. You cannot configure it：smooEnd是只读字段，不可指定 |
|
关键字 |
ACTION_UPDATE_VXLANPOOL |
|
日志内容 |
Updated VXLAN pool: $1 |
|
参数解释 |
$1：VXLAN池配置信息 |
|
举例 |
Updated VXLAN pool: VXLAN pool ID:[8ca117d1-b2ea-4538-9464-6a924f7fdf89] VXLAN pool name:[BA] Start VNI:[334] End VNI:[3344] VXLAN allocated:[false] |
|
日志说明 |
用户进行了修改VXLAN池的操作 |
|
失败原因 |
· 当操作失败时，可能的原因如下： · Invalid license：无效的License · Invalid JSON format：无效的JSON格式 · The service is disabled：服务未启动 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · Invalid name：无效的名称 · Invalid start VNI value：无效的起始值 · Invalid end VNI value：无效的结束值 · The name is required：名称不能为空 · The range is required：range字段不能为空 · The start value is required：起始值不能为空 · The end value is required：结束值不能为空 · VNI value is out of range：起始值或结束值超出范围 · The VXLAN pool does not exist：VXLAN池不存在 · The VXLAN pool name already exists：VXLAN池名称已存在 · VXLAN pools in use cannot be modified or deleted：不允许修改或删除正在使用的VXLAN池 · The end VXLAN ID must be greater than or equal to the start VXLAN ID.：结束值必须大于等于起始值 · The VXLAN pool overlaps with another VXLAN pool：VXLAN池与其他VXLAN池重叠 · The VXLAN range cannot contain existing segment IDs or mapping segment IDs：VXLAN池范围与segment ID或映射segment ID重叠 · You have no privilege to perform this operation：用户无权限执行此操作 · Cannot specify both the range and range_list parameters：range和range_list不能同时配置 · You can use only the range_list parameter to edit VXLAN ranges when multiple VXLAN ranges exist：已存在多个VXLAN范围，不允许使用range字段进行修改 · VXLAN range conflicts exist：存在VXLAN范围冲突 · The VXLAN range contains the reserved VXLAN ID configured for the device deployment template or the M-LAG system：指定的VXLAN范围与自动化模板或M-LAG系统的保留VXLAN重叠 · The smoothEnd field is read-only. You cannot configure it：smooEnd是只读字段，不可指定 · The VXLAN pool is being synchronized. You cannot edit or delete it：VXLAN池平滑中，不允许修改或删除 |
|
关键字 |
ACTION_DELETE_VXLANPOOL |
|
日志内容 |
Deleted VXLAN pool: $1 |
|
参数解释 |
$1：VXLAN池ID |
|
举例 |
Deleted VXLAN pool: 8ca117d1-b2ea-4538-9464-6a924f7fdf89 |
|
日志说明 |
用户进行了删除VXLAN池的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · Invalid JSON format：无效的JSON格式 · The service is disabled：服务未启动 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · The VXLAN pool does not exist：VXLAN池不存在 · VXLAN pools in use cannot be modified or deleted：不允许修改或删除正在使用的VXLAN池 · You have no privilege to perform this operation：用户无权限执行此操作 · The VXLAN pool is being synchronized. You cannot edit or delete it：VXLAN池平滑中，不允许修改或删除 |
|
关键字 |
CREATE_PHYNE_OP |
|
日志内容 |
Created physical NE: $1 |
|
参数解释 |
$1：设备配置信息 |
|
举例 |
Created physical NE: NE ID: [5986bede-08f2-4d4e-bd01-9e7907272e5d] NE name: [l2vtep] NE type: [L2GW] VTEP IP6: [22:0:0:0:0:0:0:11] VDS ID: [ffffffff-0000-0000-0000-000000000001] NETCONF username: [sdn] NETCONF password: [123456] Provider type: [PHY_DEVICE] NE capability: [L2GW] Vrf: [mgmt] Reserved tunnel ID: [256] Supporting autoconfiguration: [true] Supporting VTEP: [true] Service migration: [false] PreCfgVxlanService: [false] OpenflowPermitPort: [false] PreStatVxlanService: [false] openflowControllerPort: [null] openflowSslPolicyName: [null] openflowSslAccessControlPolicyName:[dcp] Clear configuration: [false] Data synchronization: [DEFAULT] externalInfoList: [
] isDeleting: [false] Role name: [leaf] Serial number: [210235A2C4H187000881] Fabric ID: [b07f126a-54bb-480a-ba4c-a98fe1153d14] Gateway: [false] Read community: [public] Write community: [private] Under deployment: [false] Loopback1 IP: ] NE status:[INACTIVE] Inactive reason:[DEVICE_INACTIVE_REASON_DEVICE_IS_NO_FINISH_AUTOMAIN_ON_LINE] |
|
日志说明 |
用户进行了创建物理网元的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · The service is disabled：服务未启动 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · Unknown internal server error：未知的内部服务器错误 · Invalid name：无效的名称 · The NE ID already exists：设备ID已存在 · The NE name already exists：设备名称已存在 · The management IP address already exists：指定的管理IP地址已存在 · Invalid description：无效的描述信息 · Invalid parameter：无效的配置参数 · The device group doesn't exist：设备组不存在 · Physical gateway service devices can be bound only to BIND_PHY type device groups：物理网关服务设备只能绑定BIND_PHY类型的设备组 · The device group is already bound to a gateway service device：设备组已绑定网关服务设备 · Invalid IP address：无效的IP地址 · The VTEP IP has been used：指定的VTEP IP地址已被使用 · The NETCONF username or password is not configured：没有配置NETCONF用户名或密码 · Invalid NETCONF username：无效的NETCONF用户名 · Invalid NETCONF password：无效的NETCONF密码 · The VSM service is disabled：VSM服务未启动 · Invalid VDS ID：无效的VDS ID · The preferred region doesn't exist：指定的优选Region不存在 · Invalid tunnel ID：无效的隧道ID · The number of physical NEs exceeds the limit of the overlay hardware entity license：物理网元个数超过Overlay硬件网元功能License限制 · The management IP address conflicts with the host IP：管理IP与主机IP地址冲突 · Invalid BGP instance name：无效的BGP实例名称 · The reserved VLAN ID conflicts with a VLAN ID of an VLAN-VXLAN mapping：存储VLAN与VLAN-VXLAN映射冲突 · Invalid serial number：无效的设备序列号 · The alias cannot exceed 63 characters：别名信息不能超过63个字符 · The device MAC address already exists：指定的设备MAC地址已存在 · The device serial number already exists：指定的设备序列号已存在 · The DC interconnection IP address is required：DC互联IP不能为空 · The DC interconnection IP address cannot be configured：不允许配置DC互联IP
· The system IDs of different NEs in a fabric cannot be the same：同一Fabric下，各个网元设备指定的网络实体ID中System ID不能相同 · The fabric ID is required：未指定Fabric ID · The software version is read only：软件版本号为只读字段 · The device type field is read only：设备类型为只读字段 · Invalid device type：无效的设备类型 · The NETCONF username is required：未指定NETCONF的用户名 · The NETCONF password is required：未指定NETCONF的密码 · The SNMP read community name is required：未指定SNMP的读团体名 · The SNMP write community name is required：未指定SNMP的写团体名 · An NE can be added to a device group only after it is bound to a fabric：未绑定Fabric的网元设备不允许加入设备组 · The device model cannot be edited：设备型号不允许修改 · The fabric does not exist：指定的Fabric不存在 · The VTEP IP of the specified device has already been used by a device on the auto deployment device information：指定设备的VTEP IP已被自动化部署的设备信息中的设备使用 · Cannot specify a VTEP IP address in the underlay address pool：指定的VTEP IP地址不允许在Underlay互通地址段范围内 · The VTEP IP already exists：指定的VTEP IP地址已存在 · The VTEP IP cannot belong to the underlay IP range or loopback1 IP range：VTEP IP不允许在Underlay IP范围或Loopback1 IP范围内 · The underlay address pool cannot contain existing VTEP IP addresses：Underlay互通地址段范围内不允许包含已经存在的VTEP IP地址 · The DCI VTEP IP already exists：DCI VTEP IP已存在 · The VTEP IP cannot be the same as the DCI VTEP IP of the peer device in the DC connection：VTEP IP和数据中心连接中对端设备的DCI VTEP IP冲突 · The DCI VTEP IP cannot be the same as the DCI VTEP IP of the peer device in the DC connection：DCI VTEP IP和数据中心连接中的对端设备DCI VTEP IP冲突 · Only border device support the DCI VTEP IP configuration：仅边界设备支持配置DCI VTEP IP · The DCI VTEP IP cannot be the same as the VTEP IP address of a device：DCI VTEP IP地址与其他设备的VTEP IP地址冲突 · The VTEP IP cannot be the same as the DCI VTEP IP address of a device： VTEP IP地址与其他设备的DCI VTEP IP地址冲突 · The management IP address has already been added to a device autodeploy list：指定的管理IP已加入设备清单中 · The management IP address has been used：管理IP地址已经被分配 · The management IP address cannot belong to any existing address pools except for the management address pool：管理IP地址不允许属于除管理网地址池外的其他地址池 · In multi-active mode, you must configure one IPv4 VTEP address or one IPv6 VTEP address, but not both：多活模式下，VTEP IP和VTEP IPv6必填且仅支持配置一个 · You must configure one IPv4 VTEP address or one IPv6 VTEP address, but not both：VTEP IP和VTEP IPv6必填且仅支持配置一个 · You have no privilege to perform this operation：用户无权限执行此操作 · The certificate-based access control policy name cannot exceed 31 characters：证书访问控制策略名称最长31个字符 · To configure the certificate-based access control policy name, please first configure the SSL policy name：未配置SSL策略名称时，不允许配置证书访问控制策略名称 · The value for the remote device parameter must be false for non-border switching devices：非边界设备类型的交换设备远端设备字段只能为false · Remote device group members must be remote devices：当设备组为远端设备组时，设备组成员必须是远端设备 · Remote devices cannot be used as service device group members：当设备组不是远端设备组时，设备组成员不允许为远端设备 · Failed to assign IP addresses to devices, because the IP addresses in the primary IP allocation are insufficient：为设备分配IP失败，主IP所在子网地址不足 · The specified management IP address is the IP address of a L4-L7 device. Please select another IP address：指定的管理IP与已经存在的L4-L7设备IP重复 · You can reserve loopback interface numbers only for access devices and border devices：仅接入和边界设备支持配置LoopBack接口预留编号 · The list of reserved loopback interface numbers cannot exceed 255 characters：LoopBack接口预留编号最长255个字符 · Make sure each reserved loopback interface number is an integer in the range of 50 to 1000：LoopBack接口预留编号取值范围为50~1000的整数或区间 · The label can contain up to 64 characters, and cannot be all-spaces：标签信息最长64个字符,且不允许全部输入空格 · Please specify a device type：设备类型不能为空 · The setting for smooth flag is incorrect：平滑开关取值错误 · The management IPv6 address already exists：指定的管理IPv6地址已存在 · The device model is read only：设备型号为只读字段 · The NE serial number is read only：网元序列号为只读字段 · The underlay IP is read only：Underlay互通IP地址为只读字段 · Please configure device-specific NETCONF settings, default NETCONF settings for switching devices, or both：设备的NETCONF信息和交换机缺省配置的NETCONF信息至少配置一项 · You cannot create devices in isolated state：不允许创建隔离状态的设备 · When the service network type for a fabric is VLAN, you can add only underlay physical devices：Fabric的业务网络类型为VLAN时，只能纳管Underlay物理设备 · When the service network type of the fabric is VLAN, the device role cannot be aggregation：Fabric的业务网络类型为VLAN时，设备角色不支持Aggregation · Only traditional and underlay devices support the device role aggr：仅传统设备和Underlay物理设备支持aggr的设备角色 · Only traditional and underlay devices support the device role access：仅传统设备和Underlay物理设备支持access的设备角色 · The device type of a member does not match the control mode of the device group：网元类型与设备组控制模式不匹配 · The device is not bound to the fabric：网元设备未绑定Fabric · No fabric is specified for the device group：设备组没有指定Fabric · The NE and the device group to which the NE belongs must be in the same fabric：网元设备和设备组的Fabric不同 · A border gateway in IRF HA mode can have only one member：IRF模式的设备组只能存在一个成员 · You can add a maximum of two member devices to the border device group if the HA mode is M-LAG：HA部署模式为M-LAG时，边界设备组不能配置超过两个成员 · The Telnet authentication mode is required：未指定Telnet的认证模式 · Invalid Telnet authentication mode：无效的Telnet认证模式 · Invalid Telnet password：无效的Telnet密码 · Invalid Telnet username：无效的Telnet用户名 · The Telnet username is required：未指定Telnet的用户名 · Invalid openflow controller port：无效的OpenFlow端口号 · Invalid openflow ssl policy name：无效的SSL策略名称 · Invalid VRF name：无效的VRF名称 · The SNMP read community name can contain up to 32 characters. Chinese characters are not supported：指定的SNMP读团体名最长32个字符，不支持中文 · The SNMP write community name can contain up to 32 characters. Chinese characters are not supported：指定的SNMP写团体名最长32个字符，不支持中文 · The sysname can contain up to 64 characters, and cannot be all-spaces：系统名称最长64个字符，且不允许全部输入空格 · The label can contain up to 64 characters, and cannot be all-spaces：标签信息最长64个字符，且允许全部输入空格 · Invalid role name：角色名称无效 · Invalid reserved VLANs：无效的存储VLAN · The VTEP IP address cannot be identical to another IP address specified in the M-LAG system plan：指定的VTEP IP不能M-LAG系统已规划的IP相同 · The management IP address has already been added to a device autodeploy list：指定的管理IP已加入设备清单中 · The management IP address cannot belong to the IP pool for auto deployment：管理IP不允许属于自动化上线地址池 · The management IP address has been used：管理IP地址已经被分配 · When the management mode is in-band, you must configure an OpenFlow in-band management VLAN for devices to be automatically deployed：带内自动化上线的设备，必须配置OpenFlow带内管理VLAN · The device name already exists in the device information list of the device list：指定的设备名称在设备清单的设备信息列表中已存在 · Invalid name：无效的设备名称 · A border gateway in IRF HA mode can have only one member：IRF模式的设备组只能存在一个成员 · Only traditional devices can be marked as third-party devices：仅传统设备支持配置为第三方设备 · Third-party devices do not support NETCONF configuration：第三方设备不支持配置NETCONF · Please specify an SSH username：SSH用户名必填 · Please specify an SSH password：SSH密码必填 · The SSH username can contain up to 32 characters and cannot start or end with a whitespace character：SSH用户名最长32个字符，不支持首尾输入空白符 · The SSH password can contain up to 64 characters, Chinese characters are not supported：SSH密码最长64个字符，不支持中文 |
|
关键字 |
UPDATE_PHYNE_OP |
|
日志内容 |
Updated physical NE: $1 |
|
参数解释 |
$1：设备配置信息 |
|
举例 |
Updated physical NE: NE ID: [00dbdaab-8cdc-46cd-88e0-9a86e1269853] NE name: [deviceGate] Description: [A] NE type: [L3GW] VTEP IP6: [22:0:0:0:0:0:0:11] NETCONF username: [sdn] NETCONF password: [******] Provider type: [PHY_DEVICE] NE capability: [L3GW] Vrf: [mgmt] Reserved tunnel ID: [256] Supporting autoconfiguration: [true] Supporting VTEP: [true] Service migration: [false] PreCfgVxlanService: [false] OpenflowPermitPort: [false] PreStatVxlanService: [false] openflowControllerPort: [null] openflowSslPolicyName: [null] openflowSslAccessControlPolicyName:[dcp] Clear configuration: [false] Data synchronization: [DEFAULT] externalInfoList: [
] isDeleting: [false] Role name: [spine] Serial number: [45039507705P06] Fabric ID: [889933a9-c49b-4e8c-b56d-037830062601] Gateway: [true] asNumber is: [0] Under deployment: [false] Loopback1 IP: ] NE status:[INACTIVE] Inactive reason:[DEVICE_NOT_IN_GROUP] |
|
日志说明 |
用户进行了修改物理网元的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · The service is disabled：服务未启动 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · Unknown internal server error：未知的内部服务器错误 · The NE doesn't exist：该设备不存在 · Invalid description：无效的描述信息 · Invalid parameter：无效的配置参数 · The device group doesn't exist：设备组不存在 · Physical gateway service devices can be bound only to BIND_PHY type device groups：物理网关服务设备只能绑定BIND_PHY类型的设备组 · The device group is already bound to a gateway service device：设备组已绑定网关服务设备 · Invalid IP address：无效的IP地址 · The VTEP IP already exists：指定的VTEP IP已存在 · Invalid NETCONF username：无效的NETCONF用户名 · Invalid NETCONF password：无效的NETCONF密码 · The network element is being deleted or being removed from the gateway group：该网元正在删除或从设备组中移出 · The reserved VLAN ID conflicts with a VLAN ID of an VLAN-VXLAN mapping：存储VLAN与VLAN-VXLAN映射冲突 · The NE has been bound to a device group. It cannot be unbound from the fabric：网元设备已绑定设备组，不允许与Fabric解绑 · The DC interconnection IP address cannot be configured：不允许配置DC互联IP · The fabric ID has been used：指定的Fabric ID已被绑定 · The NE type specified in the fabric must be the same as the NE type of the device：Fabric中指定的网元类型与设备的网元类型不一致，请修改设备配置 · The role name cannot be edited because the NE has been bound to a fabric：网元已与Fabric绑定，角色名称不允许修改 · The gateway cannot be edited because the NE has been bound to a fabric：网元已与Fabric绑定，网关能力不允许修改 · The network entity ID cannot be edited：网络实体ID字段不允许修改 · Before binding a device group to a fabric, unbind the group from its original fabric. 修改网元设备绑定的Fabric时，需先解绑再进行重新绑定操作 · An NE can be added to a device group only after it is bound to a fabric：未绑定Fabirc的网元设备不允许加入设备组 · The device model cannot be edited：设备型号不允许修改 · The software version field is read only：软件版本号为只读字段 · The device type field is read only：设备类型为只读字段 · The fabric does not exist：指定的Fabric不存在 · Before binding a device to a fabric, unbind the device from its original fabric：修改网元设备绑定的Fabric时，需先解绑再进行重新绑定操作 · The DCI VTEP IP already exists：DCI VTEP IP已存在 · Cannot modify the DCI VTEP IP of the device that has a DC connection established：设备已被数据中心连接使用，不允许修改DCI VTEP IP · Cannot remove the device from the device group because the device has a DC connection established：设备已被数据中心连接使用，不允许从设备组中移除 · The DCI VTEP IP cannot be the same as the DCI VTEP IP of the peer device in the DC connection：DCI VTEP IP和数据中心连接中的对端设备DCI VTEP IP冲突 · Only border device support the DCI VTEP IP configuration：仅边界设备支持配置DCI VTEP IP · The DCI VTEP IP cannot be the same as the VTEP IP address of a device：DCI VTEP IP地址与其他设备的VTEP IP地址冲突 · The VTEP IP cannot be the same as the DCI VTEP IP address of a device： VTEP IP地址与其他设备的DCI VTEP IP地址冲突 · You must configure one IPv4 VTEP address or one IPv6 VTEP address, but not both：VTEP IP和VTEP IPv6必填且仅支持配置一个 · The vtepIP version of group and device are not same：设备组和设备的vtepIp版本不一致 · You have no privilege to perform this operation：用户无权限执行此操作 · The certificate-based access control policy name cannot exceed 31 characters：证书访问控制策略名称最长31个字符 · To configure the certificate-based access control policy name, please first configure the SSL policy name：未配置SSL策略名称时，不允许配置证书访问控制策略名称 · The is_remote parameter for switching devices cannot be edited：交换设备的is_remote字段不允许修改 · Remote device group members must be remote devices：当设备组为远端设备组时，设备组成员必须是远端设备 · Remote devices cannot be used as service device group members：当设备组不是远端设备组时，设备组成员不允许为远端设备 · Failed to assign IP addresses to devices, because the IP addresses in the primary IP allocation are insufficient：为设备分配IP失败，主IP所在子网地址不足 · The reserved loopback interface numbers cannot be edited：LoopBack接口预留编号不允许修改 · You cannot edit the enabling status of VXLAN service preconfiguration for this device type：指定设备类型不允许修改VXLAN转发预配置开关 · You cannot edit the enabling status of VXLAN service preconfiguration on a device group member used for fabric interconnection：当设备是Fabric间互通的设备组成员时，不允许关闭VXLAN转发预配置开关 · You cannot edit the enabling status of VXLAN service preconfiguration when the device has QinQ mappings on its interfaces：设备存在接口绑定QinQ映射，不允许修改VXLAN转发预配置开关 · You cannot change the state of the VXLAN service preconfiguration feature when the network cloud feature is enabled：网络云场景下不允许切换VXLAN转发预配置开关 · You cannot edit the name of this device：指定的设备类型不允许修改设备名称 · The label for a physical device cannot be edited：标签不允许修改 · The setting for smooth flag is incorrect：平滑开关取值错误 · You can add a maximum of two member devices to the device group if the HA mode is M-LAG：HA部署模式为M-LAG时，设备组不能配置超过两个成员 · You can add only border-type leaf devices to a device group for service-leaf deployment：Service Leaf网络位置设备组只支持绑定Leaf角色的边界设备 · You cannot delete a service leaf device or remove the device from the device group if the following conditions exist:The device is already bound to a resource access template.The service leaf firewall associated with the device is already bound to a vRouter：Service Leaf设备已被资源接入模板绑定或该设备关联的Service Leaf防火墙已被虚拟路由器绑定，该设备不允许删除或者解关联设备组 · The device model is read only：设备型号为只读字段 · The NE serial number is read only：网元序列号为只读字段 · The underlay IP is read only：Underlay互通IP地址为只读字段 · The management IP address cannot be modified：管理IP地址不允许修改 · The fabric ID cannot be modified：网元设备的Fabric ID不允许修改 · The role name cannot be edited：角色名称不允许修改 · The gateway cannot be edited：网关能力不允许修改 · Invalid name：无效的设备名称 · The NE name already exists：设备名称已存在 · The device name already exists in the device information list of the device list：指定的设备名称在设备清单的设备信息列表中已存在 · When the management mode is in-band, you must configure an OpenFlow in-band management VLAN for devices to be automatically deployed：带内自动化上线的设备，必须配置OpenFlow带内管理VLAN · The sysname can contain up to 64 characters, and cannot be all-spaces：系统名称最长64个字符，且不允许全部输入空格 · The label can contain up to 64 characters, and cannot be all-spaces：标签信息最长64个字符，且允许全部输入空格 · Invalid role name：角色名称无效 · The SNMP read community name can contain up to 32 characters. Chinese characters are not supported：指定的SNMP读团体名最长32个字符，不支持中文 · The SNMP write community name can contain up to 32 characters. Chinese characters are not supported：指定的SNMP写团体名最长32个字符，不支持中文 · Once configured, the VTEP IP address cannot be modified：VTEP IP配置完成后不允许修改 · A VTEP IP address is required for a member in a device group if the group is enabled with the fabric link feature：当设备组的网络位置为Fabric互通时，其成员设备的VTEP IP不能为空 · The VTEP IP already exists：指定的VTEP IP地址已存在 · The VTEP IP has been used：指定的VTEP IP地址已被使用 · Cannot specify a VTEP IP address in the underlay address pool：指定的VTEP IP地址不允许在Underlay互通地址段范围内 · The VTEP IP of the specified device has already been used by a device on the auto deployment device information：指定设备的VTEP IP已被自动化部署的设备信息中的设备使用 · The VTEP IP address cannot be identical to another IP address specified in the M-LAG system plan：指定的VTEP IP不能M-LAG系统已规划的IP相同 · The VTEP IP cannot belong to the underlay IP range or loopback1 IP range：VTEP IP不允许在Underlay IP范围或Loopback1 IP范围内 · Failed to remove the device from the device group. Border interfaces exist on the device：指定设备移出设备组成员失败，设备下存在外网出口 · Cannot delete the device. It is a member of an M-LAG system：设备是M-LAG系统成员，不允许删除 · You cannot remove the device from the device group, because the device has VLAN-VXLAN mappings：设备下存在VLAN-VXLAN映射，不允许解绑设备组 · The device type of a member does not match the control mode of the device group：网元类型与设备组控制模式不匹配 · The device is not bound to the fabric：网元设备未绑定Fabric · No fabric is specified for the device group：设备组没有指定Fabric · The NE and the device group to which the NE belongs must be in the same fabric：网元设备和设备组的Fabric不同 · You cannot edit the NETCONF username. The device has been locked：设备已加锁，不允许修改NETCONF用户名 · Invalid reserved VLANs：无效的存储VLAN · You cannot unbind the device from the device group, because the device has an interconnect interface binding：设备关联了互联接口，不允许该设备解绑设备组 · When the network positions of a device group include fabric interconnection, each of its member devices must have a VTEP IP address：当设备组的网络位置为Fabric间互通时，其成员设备的VTEP IP不能为空 · A border gateway in IRF HA mode can have only one member：IRF模式的设备组只能存在一个成员 · You cannot change the VXLAN service preconfiguration state, because the device has been bound to a global VLAN-VXLAN mapping：网元绑定全局VLAN-VXLAN类型映射表时下不允许切换VXLAN转发预配置开关 · The current device type does not support editing the reservedTunnelId field：该设备类型不支持修改VXLAN预留隧道编号 · If a dhcp-type vPort exists and its network node access policy is VXLAN, you cannot edit the reservedTunnelId field：存在网络节点接入策略为VXLAN的dhcp类型虚拟端口时，不允许修改VXLAN预留隧道编号 · Only traditional devices can be marked as third-party devices：仅传统设备支持配置为第三方设备 · Third-party devices do not support NETCONF configuration：第三方设备不支持配置NETCONF · Please specify an SSH username：SSH用户名必填 · Please specify an SSH password：SSH密码必填 · The SSH username can contain up to 32 characters and cannot start or end with a whitespace character：SSH用户名最长32个字符，不支持首尾输入空白符 · The SSH password can contain up to 64 characters, Chinese characters are not supported：SSH密码最长64个字符，不支持中文 |
|
关键字 |
DELETE_PHYNE_OP |
|
日志内容 |
Deleted physical NE: ID: $1 Name: $2 Management IP: $3 |
|
参数解释 |
$1：物理网元的ID $2：物理网元的名称 $3：物理网元的管理IP |
|
举例 |
Deleted physical NE: ID: [f10dbcef-b96a-48ad-8613-47fc7fe9f4e8] Name: [125] Management IP: [97.0.1.12] |
|
日志说明 |
用户进行了删除物理网元的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · The service is disabled：服务未启动 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · The NE doesn't exist：该设备不存在 · The NE is migrating services：设备正在迁移 · The network element is being deleted or being removed from the gateway group：该网元正在删除或从设备组中移出 · Cannot delete the device because the device has a DC connection established：设备已被数据中心连接使用，不允许删除 · You have no privilege to perform this operation：用户无权限执行此操作 · The main ip pool not enough：主IP地址不足 · The reserved loopback interface numbers cannot be edited：LoopBack接口预留编号不允许修改 · The device is in an M-LAG system and cannot be deleted：该设备已经组建M-LAG系统，不允许删除 · Cannot delete the device. It is a member of an M-LAG system：设备是M-LAG系统成员，不允许删除 · You cannot delete the device, because M-LAG group ID ranges have been configured for it：该设备已被M-LAG组编号范围引用，不允许删除 · You cannot delete a service leaf device or remove the device from the device group if the following conditions exist:The device is already bound to a resource access template.The service leaf firewall associated with the device is already bound to a vRouter：Service Leaf设备已被资源接入模板绑定或该设备关联的Service Leaf防火墙已被虚拟路由器绑定，该设备不允许删除或者解关联设备组 · You cannot remove the device, because the device has an interconnect interface binding：设备关联了互联接口，不允许删除该设备 |
|
关键字 |
BATCH_ADD_PHYNE_OP |
|
日志内容 |
Batch added physical NEs: Added NEs: $1 Ignored NEs: $2 |
|
参数解释 |
$1：添加的物理网元数 $2：忽略的物理网元数。当工作表中的物理网元信息与控制组件上已有物理网元信息重复时，控制组件将会忽略该物理网元，不把该物理网元添加到控制组件 |
|
举例 |
Batch added physical NEs: Added NEs: 10 Ignored NEs: 5 |
|
日志说明 |
用户进行了批量添加物理网元的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Information about the NE in row m of sheet n is invalid：第n个工作表的第m条网元信息无效 · Information about the NE in row m of sheet n conflicts with that of an NE on the controller：第n个工作表的第m条网元信息和控制组件上已有网元信息冲突 · Failed to import the device data in row m of sheet n. The number of physical devices has exceeded the limit allowed by the overlay hardware entity license：第n个工作表的第m条设备信息导入失败。物理设备个数超过Overlay硬件网元功能License限制 · Failed to import the device data in row m of sheet n. The number of devices has exceeded the limit required by the node license：第n个工作表的第m条设备信息导入失败。设备数量已达节点License允许创建的最大值 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
BATCH_EXPORT_PHYNE_OP |
|
日志内容 |
Batch exported physical NEs: $1. |
|
参数解释 |
$1：批量导出文件名 |
|
举例 |
Batch exported physical NEs: 交换设备-2022-09-26 21-48-27.xlsx |
|
日志说明 |
用户进行了批量导出物理网元操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · Failed to export the file：Excel文件导出失败 · An import or export task is in progress. Please try again later：正在进行导入或导出任务，请稍后再试 |
|
关键字 |
START_SCAN_PHYNE_OP |
|
日志内容 |
Started scanning physical NEs: $1 |
|
参数解释 |
$1：物理网元的自动发现配置 |
|
举例 |
Started scanning physical NEs: Start management IP: [192.168.125.0] End management IP: [192.168.125.10] NETCONF username: [admin] NETCONF password: [admin] |
|
日志说明 |
用户进行了自动发现物理网元的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service is disabled：服务未启动 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
STOP_SCAN_PHYNE_OP |
|
日志内容 |
Stopped scanning physical NEs |
|
参数解释 |
无 |
|
举例 |
Stopped scanning physical NEs |
|
日志说明 |
用户进行了停止自动发现物理网元的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service is disabled：服务未启动 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
START_MIGRATION_PHYGW_OP |
|
日志内容 |
Started migration on physical gateway: $1 |
|
参数解释 |
$1：物理网关设备ID |
|
举例 |
Started migration on physical gateway: f10dbcef-b96a-48ad-8613-47fc7fe9f4e8 |
|
日志说明 |
用户进行了物理网关设备业务迁移的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · The service is disabled：服务未启动 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · The device doesn't exist：该设备不存在 · The device is inactive：设备处于未激活状态 · The device is migrating services：设备正在迁移 · The network element is being deleted or being removed from the gateway group：该网元正在删除或从设备组中移出 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
COMPLETE_MIGRATION_PHYGW_OP |
|
日志内容 |
Completed migration on physical gateway: $1 |
|
参数解释 |
$1：物理网关设备ID |
|
举例 |
Completed migration on physical gateway: f10dbcef-b96a-48ad-8613-47fc7fe9f4e8 |
|
日志说明 |
用户进行了物理网关设备业务恢复的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · The service is disabled：服务未启动 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · The device doesn't exist：该设备不存在 · Only physical gateway devices support migration：只有物理网关设备支持迁移 · The device has already completed migration：设备迁移已结束 · The network element is being deleted or being removed from the gateway group：该网元正在删除或从设备组中移出 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
START_DATA_SYNCHRONIZATION_OP |
|
日志内容 |
Started data synchronization on physical NE: $1 |
|
参数解释 |
$1：物理网元的ID |
|
举例 |
Started data synchronization on physical NE: 28424135-36f5-4dde-ad2e-29580411de8d |
|
日志说明 |
用户进行了手动触发指定物理网元进行数据同步的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · The service is disabled：服务未启动 · The device doesn't exist：该设备不存在 · The device is inactive：设备处于未激活状态 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · The device does not support this function：此设备不支持本功能 · The network element is being deleted or being removed from the gateway group：该网元正在删除或从设备组中移出 · The system is performing data synchronization or configuration auditing for the network element：该网元正在进行数据同步或配置审计 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
START_PHYNE_CONFIG_AUDIT_OP |
|
日志内容 |
Started configuration auditing on physical NE $1 |
|
参数解释 |
$1：物理网元的ID |
|
举例 |
Started configuration auditing on physical NE 28424135-36f5-4dde-ad2e-29580411de8d |
|
日志说明 |
用户进行了手动触发指定物理网元进行配置审计的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · The service is disabled：服务未启动 · The device doesn't exist：该设备不存在 · The device is inactive：设备处于未激活状态 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · The device does not support this function：此设备不支持本功能 · The network element is being deleted or being removed from the gateway group：该网元正在删除或从设备组中移出 · The system is performing data synchronization or configuration auditing for the network element：该网元正在进行数据同步或配置审计 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
START_PHYNE_RESET_OP |
|
日志内容 |
Start reseting on physical NE $1 |
|
参数解释 |
$1：物理网元的ID |
|
举例 |
Start reseting on physical NE 28424135-36f5-4dde-ad2e-29580411de8d |
|
日志说明 |
用户进行了清空指定物理网元配置，重新自动化上线的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · The service is disabled：服务未启动 · The device doesn't exist：该设备不存在 · The device is inactive：设备处于未激活状态 · Configuration recovery is in progress：配置正在恢复过程中 · Please perform the operation on the active leader：请在主Leader上进行操作 · The device does not support this function：此设备不支持本功能 · The network element is being deleted or being removed from the gateway group：该网元正在删除或从设备组中移出 · You have no privilege to perform this operation：用户无权限执行此操作 · Failed to delete the device because the device has been bound to boarder interfaces：设备删除失败，该设备已经绑定了外网出口 · The device is used by fabric connection：设备正在被Fabric连接使用 · The device is in an M-LAG system：设备是M-LAG系统成员 · The device already is an M-LAG system member：设备是M-LAG系统成员 · Configuration auditing or synchronization cannot be performed on isolated devices：被隔离的设备不允许进行审计平滑操作 · The device is being used by a configuration audit：设备正在被配置审计使用 |
|
关键字 |
START_VIRTUAL_NE_DATA_SYNCHRONIZATION_OP |
|
日志内容 |
Started data synchronization on virtual NE $1 |
|
参数解释 |
$1：虚拟网元的ID |
|
举例 |
Started data synchronization on virtual NE 28424135-36f5-4dde-ad2e-29580411de8d |
|
日志说明 |
用户进行了手动触发指定虚拟网元进行数据同步的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · The service is disabled：服务未启动 · The device doesn't exist：该设备不存在 · The device is inactive：设备处于未激活状态 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · The system is performing data synchronization or configuration auditing for the network element：该网元正在进行数据同步或配置审计 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
START_VIRTUAL_NE_CONFIG_AUDIT_OP |
|
日志内容 |
Started configuration auditing on virtual NE $1 |
|
参数解释 |
$1：虚拟网元的ID |
|
举例 |
Started configuration auditing on virtual NE 28424135-36f5-4dde-ad2e-29580411de8d |
|
日志说明 |
用户进行了手动触发指定虚拟网元进行配置审计的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · The service is disabled：服务未启动 · The device doesn't exist：该设备不存在 · The device is inactive：设备处于未激活状态 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · The system is performing data synchronization or configuration auditing for the network element：该网元正在进行数据同步或配置审计 · The virtual network function node doesn't exist：该虚拟网络功能节点不存在 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_VNF_OP |
|
日志内容 |
Updated VNF device : $1 |
|
参数解释 |
$1：VNF设备信息 |
|
举例 |
Updated VNF device : NE ID: [aa3431ec-08af-4e0d-93a6-b0c01d2ae5f9] NE name: [VFW_0377248511] NE MAC: [3c:8c:40:4e:dd:49] Description: [Reth1] NE type: [VLANSN] Gateway group name: [Reth2] NETCONF username: [admin] NETCONF password: [null] Management IP: [98.0.87.5] Provider type: [VNGFW] NE capability: [FW] Reserved tunnel ID: [256] Supporting autoconfiguration: [true] Supporting VTEP: [true] Service migration: [false] PreCfgVxlanService: [false] OpenflowPermitPort: [false] PreStatVxlanService: [false] openflowControllerPort: [null] openflowSslPolicyName: [null] Clear configuration: [false] Data synchronization: [DEFAULT] externalInfoList: [
] isDeleting: [false] Data Path Id:[00:01:74:25:8a:e3:a3:6c] connect interface name:[Reth3] Fabric ID: [null] Gateway: [false] Under deployment: [false] Is Auto Create: [false] ] devSnList: [
] Region ID:[d284da7f-5393-46e2-903e-f1e42f3fc7e4] Region name:[re... |
|
日志说明 |
用户进行了修改VNF设备信息的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · The service is disabled：服务未启动 · Netconf session is down：Netconf session没有起来 · Invalid NETCONF password：无效的NETCONF密码 · The virtual network function node doesn't exist：该虚拟网络功能节点不存在 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Failed to update the NETCONF username or password：NETCONF用户名或密码修改失败 · Failed to save the configuration of the device：设备保存配置失败 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_NETCONF_DEFAULT_USER_OP |
|
日志内容 |
Created NETCONF default user: $1 |
|
参数解释 |
$1：NETCONF缺省用户信息 |
|
举例 |
Created NETCONF default user: Username: [admin] Password: [******] |
|
日志说明 |
用户进行了配置NETCONF缺省用户的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · The service is disabled：服务未启动 · Invalid parameter：无效的配置参数 · Invalid JSON format：无效的JSON格式 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_DEVICE_DEFAULT_BFD_OP |
|
日志内容 |
Edited BFD settings in the switching device default settings: $1 $2 $3 $4 |
|
参数解释 |
$1：多跳echo报文的最小时间间隔 $2：多跳检测的BFD检测时间倍数 $3：发送多跳control报文的最小时间间隔 $4：接收多跳control报文的最小时间间隔 |
|
举例 |
Edited BFD settings in the switching device default settings: Min multihop echo-mode detection interval:[400] Multihop detection time multiplier:[40] Min Interval for Sending Multihop BFD Control Packets:[400] Min Interval for Receiving Multihop BFD Control Packets:[400] |
|
日志说明 |
用户进行了修改缺省BFD配置的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · The service is disabled：服务未启动 · Invalid JSON format：无效的JSON格式 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · You have no privilege to perform this operation：用户无权限执行此操作 · Unknown internal server error：未知的内部服务器错误 · The minimum multihop echo-mode detection interval must be 0 or a multiple of 10 in the range of 3 to 10000：多跳echo报文的最小时间间隔取值范围为0，3~10000的整数且为10的倍数 · The multihop detection time multiplier must be an integer in the range of 3 to 50：多跳检测的BFD检测时间倍数取值范围为3~50的整数 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · The minimum interval for sending multihop BFD control packets must be 0 or an integer in the range of 3 to 10000：发送多跳control报文的最小时间间隔取值范围为0，3~10000的整数 · The minimum interval for receiving multihop BFD control packets must be 0 or an integer in the range of 3 to 10000：接收多跳control报文的最小时间间隔取值范围为0，3~10000的整数 |
|
关键字 |
CONFIGURE_DEFAULT_MAC_ADDRESS_OP |
|
日志内容 |
Configured default MAC address: $1 |
|
参数解释 |
$1：默认MAC地址 |
|
举例 |
Configured default MAC address: 6A:12:7C:5F:2D:2C |
|
日志说明 |
用户进行了配置默认MAC地址的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown internal server error：未知的内部服务器错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · The service is disabled：服务未启动 · Invalid default MAC address：无效的默认MAC地址 · The default MAC address conflicts with the VM's MAC address：默认MAC地址与虚拟机的MAC地址冲突 · The default MAC address conflicts with the device group's MAC address：默认MAC地址与设备组的MAC地址冲突 · Do not set the MAC address to reserved MAC address for the controller：控制组件保留的MAC地址不允许使用 · You have no privilege to perform this operation：用户无权限执行此操作 · The MAC address conflicts with the network MAC address：MAC地址与虚拟链路网络的MAC地址冲突 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
DELETE_DEFAULT_MAC_ADDRESS_OP |
|
日志内容 |
Deleted default MAC address: $1, configured default MAC address: 54:c6:ff:cb:e3:10. |
|
参数解释 |
$1：默认MAC地址 |
|
举例 |
Deleted default MAC address: A6:12:7B:5F:D2:2C, configured default MAC address: 54:c6:ff:cb:e3:10. |
|
日志说明 |
用户进行了删除默认MAC地址的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown internal server error：未知的内部服务器错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · The default MAC address doesn't exist：默认MAC地址不存在 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
CREATE_THIRD_PARTY_NE_OP |
|
日志内容 |
Created third party NE: $1 |
|
参数解释 |
$1：第三方网元配置信息 |
|
举例 |
Created third party NE: ID: [8032909d-47a1-4715-90af-5153ffe39899] Name: [IPS1] Description: [thirdPartyIPS] Access device ID: [8032909d-47a1-4715-90af-5153ffe39811] Access device name: [6800] Access device VTEP IP: [12.1.1.1] Ingress port ID: [151] Egress port ID: [153] VLAN of ingress port: [100] VLAN of egress port: [100] |
|
日志说明 |
用户进行了创建第三方网元的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · The service is disabled：服务未启动 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · Unknown internal server error：未知的内部服务器错误 · Invalid name：无效的名称 · Invalid description：无效的描述信息 · Invalid parameter：无效的配置参数 · The number of virtual service nodes exceeds the license limit：虚拟服务节点个数已超过License限制 · The service chain license is not available：Service-Chain License不可用 · The ingress port doesn't exist：指定的入接口不存在 · The egress port doesn't exist：指定的出接口不存在 · Invalid VLAN ID of the ingress port：入接口所属的VLAN无效 · Invalid VLAN ID of the egress port：出接口所属的VLAN无效 · Invalid ingress port ID：无效的入接口ID · Invalid egress port ID：无效的出接口ID · The ID of the third party NE already exists：第三方网元ID不能重复 · The name of the third party NE already exists：第三方网元名称不能重复 · The IDs of the third party NE and physical access device must be different：第三方网元ID与引用的物理接入设备ID不能重复 · The ingress port is already used：入接口已经被占用 · The egress port is already used：出接口已经被占用 · The name of the physical access device is read only：物理接入设备的名称为只读属性 · The VTEP IP of the physical access device is read only：物理接入设备的VTEP IP为只读属性 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_THIRD_PARTY_NE_OP |
|
日志内容 |
Deleted third party NE: $1 |
|
参数解释 |
$1：第三方网元ID |
|
举例 |
Deleted third party NE: 8032909d-47a1-4715-90af-5153ffe39899 |
|
日志说明 |
用户进行了删除第三方网元的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · The service is disabled：服务未启动 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · The third party NE doesn't exist：该第三方网元不存在 · Failed to delete the third party network element because it is used by a service chain：该第三方网元正在被服务链引用，不允许删除 · The service chain service is disabled：服务链服务未启动 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CONFIGURE_RESERVE_OPTION_OP |
|
日志内容 |
Configured reserved option: $1 |
|
参数解释 |
$1：预留选项配置信息 |
|
举例 |
Configured reserved option: Reserved option: [true] |
|
日志说明 |
用户进行了配置预留选项的操作。当取值为true时表示打开预留选项开关，物理网关设备可以通过BGP发布Overlay子网路由；当取值为false时表示关闭预留选项开关，物理网关设备不可以通过BGP发布Overlay子网路由 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · The service is disabled：服务未启动 · Invalid JSON format：无效的JSON格式 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · You have no privilege to perform this operation：用户无权限执行此操作 · You cannot enable the network cloud feature when the third-party firewall deployment mode of the device group is hairpin or inline：设备组的对接第三方防火墙开关取值为旁挂或直连时，不允许开启网络云场景开关 |
|
关键字 |
CREATE_ADDRPOOL_OP |
|
日志内容 |
Created address pool: $1 |
|
参数解释 |
$1：地址池配置信息 |
|
举例 |
Created address pool: Address pool ID: [aa68bc06-8e30-468d-a805-d4f48952c646] Address pool name: [a] Start IP address: [10.1.1.1] End IP address: [10.1.1.100] IP address allocated: [false] |
|
日志说明 |
用户进行了创建VTEP地址池的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · The service is disabled：服务未启动 · The controller is not the active leader：该控制组件不是主Leader · Invalid JSON format：无效的JSON格式 · Configuration recovery is in progress：配置正在恢复过程中 · The address pool ID is already used：地址池ID已经存在 · No IP address is specified for the address pool：该地址池未配置IP地址 · Invalid name：无效的名称 · The address pool name is already used：地址池名称已经存在 · The start IP address is higher than the end IP address：地址池起始IP地址大于结束IP地址 · The address pool contains special or reserved IP addresses：地址池包含特殊或保留IP地址 · The IP range of the address pool overlaps with that of another address pool：该地址池与其它地址池的IP地址重叠 · Unknown internal server error：未知的内部服务器错误 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_ADDRPOOL_OP |
|
日志内容 |
Updated address pool: $1 |
|
参数解释 |
$1：地址池的配置信息 |
|
举例 |
Updated address pool: Address pool ID: [aa68bc06-8e30-468d-a805-d4f48952c646] Address pool name: [a] Start IP address: [10.1.1.1] End IP address: [10.1.1.100] IP address allocated: [false] |
|
日志说明 |
用户进行了修改VTEP地址池的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · The service is disabled：服务未启动 · The controller is not the active leader：该控制组件不是主Leader · Invalid JSON format：无效的JSON格式 · Configuration recovery is in progress：配置正在恢复过程中 · The address pool doesn't exist：地址池不存在 · Invalid name：无效的名称 · The address pool name is already used：地址池名称已经存在 · The start IP address is higher than the end IP address：地址池起始IP地址大于结束IP地址 · The address pool contains special or reserved IP addresses：地址池包含特殊或保留IP地址 · The address pool is in use：不允许修改正在使用的地址池 · The IP range of the address pool overlaps with that of another address pool：该地址池与其它地址池的IP地址重叠 · Unknown internal server error：未知的内部服务器错误 · The VTEP IP address pool has been used and cannot be expanded：VTEP类型的地址池已被使用，不允许扩容 · The address pool has been used by the deployment resource pool and cannot be deleted：已被管理部署资源池引用的地址池不允许删除 · The management network address pool has been used by the deployment resource pool and cannot be expanded：已被管理部署资源池引用的管理网地址池不允许扩容 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_ADDRPOOL_OP |
|
日志内容 |
Deleted address pool: $1 |
|
参数解释 |
$1：地址池ID |
|
举例 |
Deleted address pool: 0e447abc-9716-4171-902c-ecb8a090cebb |
|
日志说明 |
用户进行了删除VTEP地址池的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · The service is disabled：服务未启动 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · The address pool doesn't exist：地址池不存在 · The address pool is in use：不允许删除正在使用的地址池 · Unknown internal server error：未知的内部服务器错误 · The address pool has been used by the deployment resource pool and cannot be deleted：已被管理部署资源池引用的地址池不允许删除 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
ADD_RESOURCE_OP |
|
日志内容 |
Added resource: $1 |
|
参数解释 |
$1：资源的配置信息 |
|
举例 |
Added resource: Resource ID: [94f94495-d510-4872-b221-294098a6a247] Resource name: [VSR_6232412828] Tenant ID: [ffffffff-0000-0000-0000-000000000001] Tenant name: [default] Resource feature: [GW+GWSN] Resource family: [NFV] Resource type: [VSR] Supporting VTEP: [true] Supporting share: [false] Supporting HA: [true] NF list: [ { NF ID: [fb1671e4-496c-446a-8b4e-1ae834ba8546] NF name: [VSR_6463834061] NF management IP: [8.8.8.1] Data synchronization: [DEFAULT] } ] VNF template name: [test] Gateway member ID: 8032909d-47a1-4715-90af-5153ffe39861, Auto created: true |
|
日志说明 |
用户进行了创建资源的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · The service is disabled：服务未启动 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · The resource already exists：该资源已存在 · Invalid parameter：无效的配置参数 · Unknown internal server error：未知的内部服务器错误 · The number of virtual service nodes exceeds the license limit：虚拟服务节点个数已超过License限制 · The service chain license is not available：Service-Chain License不可用 · The VNFM is not configured：未配置VNF Manager · Invalid name：资源名称不合法 · The tenant doesn't exist：租户不存在 · The network function ID is already used：网络功能ID已经被使用 · The network function ID doesn't exist：网络功能ID不存在 · The management IP address is already used：管理IP地址已经被使用 · No network function list is specified for the physical resource：该物理资源未指定网络功能列表 · The device group doesn't exist：设备组不存在 · The VTEP address pool is not configured or doesn't have enough assignable IP addresses：未配置VTEP地址池或VTEP地址池中的剩余IP地址不足 · Duplicate network function IDs：网络功能的ID重复 · Duplicate management IP addresses：网络功能的管理IP地址重复 · Failed to get resources from the VNFM：从VNF Manager获取资源失败 · No physical gateway resource is configured for the tenant：该租户未配置物理网关资源 · A physical gateway resource is already configured for the tenant：该租户已配置物理网关资源 · The resource family conflicts with the gateway network type：该资源与租户网关的组成方式冲突 · The physical gateway resource has only one network function node：物理网关资源仅有一个网络功能节点 · Physical gateway devices can't be separately used as resources：物理网关设备不能单独作为资源 · No physical gateway service node is bound to the device group：设备组未绑定物理网关服务设备 · Physical gateway service nodes can't be used as resources：物理网关服务设备不能单独作为创建资源 · Physical access devices can't be used as resources：物理接入设备不能作为资源 · The tenant service is disabled：租户服务未启动 · The NGFWM service is not started：NGFWM服务未启动 · Server processing error：服务器处理失败 · No permission to add the resource：该用户没有权限创建资源 · The VNFM service is not loaded：未加载VNFM应用 · Before creating resources through VNFM3.0, delete all resources created through VNFM2.0：通过VNFM3.0创建资源前，请删除所有通过VNFM2.0创建的资源 · Switch to VNFM2.0 and then create resources through VNFM2.0：通过VNFM2.0创建资源前，请切换VNFM版本到VNFM2.0 · The management IP address for the virtual NE doesn't exist：该虚拟网元的管理IP不存在 · The management IP address conflicts with the host IP：管理IP与主机IP地址冲突 · The tenant is not bound to a service device group resource：该租户未绑定服务设备组资源 · The two tenants bound to different device groups can't share a service resource of the GATEWAY_SERVICE type：绑定不同设备组的两个租户不能复用GATEWAY_SERVICE类型的服务资源 · The tenant has GATEWAY_SERVICE service resources. Please bind the tenant to a service device group that uses the default address pool and default VLAN pool：该租户下已创建GATEWAY_SERVICE类型的服务资源，请绑定使用默认地址池和默认VLAN池的服务设备组 · A tenant bound to a device group using a non-default address pool or non-default VLAN pool cannot share GATEWAY_SERVICE service resources with a tenant not bound to any gateway resources：绑定的设备组使用非默认地址池或非默认VLAN池的租户与未绑定网关资源的租户之间无法复用GATEWAY_SERVICE类型的服务资源 · The gateway member does not exist：网关成员不存在 · The resource parameters and gateway member parameters do not match：网关资源参数与网关成员参数不匹配 · The gateway to which the gateway member belongs does not exist：指定的网关成员对应的出口网关不存在 · The tenant of the gateway to which the gateway member belongs is different from the tenant of the resource：指定的网关成员对应的出口网关所属租户与资源所属租户不一致 · The tenant does not support automatic service resource creation：当前租户不允许自动创建服务资源 · The gateway member has been bound to another resource：指定的网关成员已存在所属的网关资源 · You have no privilege to perform this operation：用户无权限执行此操作 · The network function for this resource has been used by a resource that differs from this resource in service type：复用已有资源的网络功能时，该资源的服务类型和新增资源的服务类型不一致 · The network function for this resource has been used by a resource in a different resource family：复用已有资源的网络功能时，该资源的资源类型和新增资源的资源类型不一致 · You can specify only one network function for a service resource：创建服务资源时，网络功能只能创建一个 · You can specify only an existing custom resource access template：资源接入模板必须存在且必须为自定义类型 · Integer (1 to 65535)：取值范围为1~65535之间的整数 · Service leaf service resources do not support gateway member configuration：Service Leaf类型服务资源不支持配置出口网关成员参数 · In the network cloud scenario, you cannot create service resources attached to service leaf nodes：网络云场景开启时，不允许创建Service Leaf类型服务资源 |
|
关键字 |
DELETE_RESOURCE_OP |
|
日志内容 |
Deleted resource: $1 |
|
参数解释 |
$1：资源的ID |
|
举例 |
Deleted resource: 0e447abc-9716-4171-902c-ecb8a090cebb |
|
日志说明 |
用户进行了删除资源的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · The service is disabled：服务未启动 · Invalid parameter：无效的配置参数 · Invalid JSON format：无效的JSON格式 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · The VNFM is not configured：未配置VNF Manager · The resource is already bound to the extranet：该资源已经绑定外网 · The NGFWM service is not started：NGFWM服务未启动 · Server processing error：服务器处理失败 · The configuration item does not exist：指定的配置项不存在 · Failed to delete the NGFW resource. Please manually delete the NGFW resource：删除NGFW资源失败，请在设备上手动删除 · The virtual gateway resource still exists：虚拟网关资源仍然存在 · No permission to delete the resource：该用户没有权限删除资源 · The vRouter bound to the resource has been bound to the sharing external IP：该资源绑定的虚拟路由器中已绑定共享的外网IP · The service gateway group resource cannot be deleted because the address pool of the resource is being used by the GATEWAY_SERVICE service resource of the tenant：服务网关组资源的地址池正在被租户内的GATEWAY_SERVICE类型的服务资源使用，不允许删除该服务网关组资源 · You have no privilege to perform this operation：用户无权限执行此操作 · You cannot delete the service resource, because it has been bound to a firewall that is used in a service chain：服务资源已被防火墙绑定，并且该防火墙已被服务链使用 · You cannot delete the service resource, because it has been bound to an NQA profile：存在绑定NQA策略，不允许删除 |
|
关键字 |
CONFIGURE_VNFM_OP |
|
日志内容 |
Configured VNFM: $1 |
|
参数解释 |
$1：VNF Manager配置信息 |
|
举例 |
Configured VNFM: IP address: [3.3.3.3] Port number: [8080] Username: [admin] Password: [******] Version: [VNFM2.0] |
|
日志说明 |
用户进行了增加或修改VNF Manager配置信息的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · The service is disabled：服务未启动 · Invalid parameter：无效的配置参数 · Invalid JSON format：无效的JSON格式 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · The port number is not in the range of 0 to 65535：端口号范围必须为0～65535 · The VNFM address or port is incorrect：VNFM的地址或端口不正确 · The VNFM username or password is incorrect：VNFM的用户名或密码不正确 · Unknown internal server error：未知的内部服务器错误 · The VNFM version must be VNFM3.0 or VNFM2.0：VNFM的版本必须为VNFM3.0或VNFM2.0 · Before modifying the VNFM version, please delete all VNF resources：切换VNFM版本前，请删除所有VNF资源 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CONFIGURE_GWNETWORK_OP |
|
日志内容 |
Configured gateway network: $1 |
|
参数解释 |
$1：网关组成方式的配置信息 |
|
举例 |
Configured gateway network: Tenant ID: [ffffffff-0000-0000-0000-000000000001] Gateway network type: [GROUP] Status: [UNUSABLE] |
|
日志说明 |
用户进行了配置租户的网关组成方式的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · The service is disabled：服务未启动 · Invalid parameter：无效的配置参数 · Invalid JSON format：无效的JSON格式 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · The tenant doesn't exist：租户不存在 · The gateway network type is already specified for the tenant：该租户已指定了网关的组成方式 · No permission to specify the gateway network for the tenant：该用户没有权限指定租户的网关组成方式 · Unknown internal server error：未知的内部服务器错误 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_GWNETWORK_OP |
|
日志内容 |
Updated gateway network: $1 |
|
参数解释 |
$1：网关组成方式的配置信息 |
|
举例 |
Updated gateway network: Tenant ID: [ffffffff-0000-0000-0000-000000000001] Gateway network type: [GROUP] Status: [UNUSABLE] |
|
日志说明 |
用户进行了修改租户的网关组成方式的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · The service is disabled：服务未启动 · Invalid parameter：无效的配置参数 · Invalid JSON format：无效的JSON格式 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · The tenant doesn't exist：租户不存在 · Resources are already allocated for the tenant：已为该租户分配了资源 · No permission to modify the gateway network for the tenant：该用户没有权限修改租户的网关组成方式 · Unknown internal server error：未知的内部服务器错误 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
BIND_ROUTER_GW_OP |
|
日志内容 |
Router bound to gateway: $1 |
|
参数解释 |
$1：虚拟路由器的ID |
|
举例 |
Router bound to gateway: aa68bc06-8e30-468d-a805-d4f48952c646 |
|
日志说明 |
用户进行了虚拟路由器绑定网关的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · The service is disabled：服务未启动 · Invalid parameter：无效的配置参数 · Invalid JSON format：无效的JSON格式 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · The virtual router doesn't exist：该虚拟路由器不存在 · No gateway network type is specified for the tenant：该租户未指定网关的组成方式 · The gateway is unavailable：该租户的网关不可用 · The virtual router is already bound to a gateway resource：该虚拟路由器已经绑定了网关资源 · No permission to bind the virtual router to the gateway：该用户没有权限进行虚拟路由器绑定网关的操作 · The vRouters using the public VRF can not be bound to the same service device group：使用公网VRF的虚拟路由器不能绑定同一个服务设备组 · The vRouter has been used to create a Layer 3 DC interconnection and can be bound to only one single-member border gateway. The device group used as the gateway member must include border gateway and DC interconnection：虚拟路由器已创建Transit VPC互通，只能绑定一个单成员的出口网关，且网关成员对应设备组的网络位置必须包含出口网关和DC间互联 · The vRouter link to which the vRouter belongs is enabled with the firewall feature. You can bind only a single-member border gateway to the vRouter：该虚拟路由器所属的虚拟路由器连接已启用防火墙，只能绑定一个出口网关，且出口网关只能为单成员 · The vRouter can be bound to only one border gateway because it has been bound to more than one load balancing service resource：虚拟路由器已绑定负载均衡服务资源，只能绑定一个出口网关 · Unknown internal server error：未知的内部服务器错误 · Cannot configure a priority for the gateway resource. For more information, see the online help：该网关资源不支持配置优先级，具体情况请查看联机帮助 · The vRouter can be bound to only one border gateway：指定的虚拟路由器只能绑定一个出口网关 · You have no privilege to perform this operation：用户无权限执行此操作 · You cannot bind the vRouter to any other border gateways. The vRouter uses a firewall as the edge device to the external network and has been bound to a border gateway that uses a device group enabled with third-party firewall deployment：外网出口设备为防火墙的虚拟路由器不支持对接第三方防火墙做主备业务 · The border gateway specified for the vRouter contains members with the third-party firewall option enabled. This is not allowed, because the external network bound to this vRouter is also bound to vRouters that use border devices as edge devices：当外部网络同时绑定外网出口设备为边界设备和防火墙的虚拟路由器时，外网出口设备为防火墙的虚拟路由器绑定的出口网关的边界设备第三方防火墙取值不能开启 · The vRouter has been bound to the same external network and border device as some other vRouters. Please make sure the gateway selected for this vRouter uses the same device groups as those vRouters：使用共享IP的虚拟路由器绑定的网关的设备组必须一致 · The extranet IP has been used by another gateway resource：该外网IP地址已被其他网关资源占用 · The vRouter has been bound to the same external network and border device as some other vRouters. Please make sure the gateway selected for this vRouter uses the same device groups as those vRouters：使用共享IP的虚拟路由器绑定的网关的设备组必须一致 · Failed to assign IP addresses to devices attached to the border gateway, because the IP addresses in the primary IP allocation are insufficient：为出口网关下的设备分配IP失败，主IP所在子网地址不足 · Check the directly connected external networks and the border interfaces in the device group bound to this vRouter with the same segment ID. Make sure only one primary IPv4 address exists for the border interface：虚拟路由器绑定的设备组中的外网出口和该虚拟路由器下的独享型外网子网使用相同Segment ID时，最多只允许有一个主IP · The third-party firewall option must be set to Off when the vRouter is bound to an external network with network segmentation enabled：虚拟路由器已绑定配置网络分段的外部网络时，边界设备第三方防火墙不允许配置为开启状态 · The firewall deployment mode for a vRouter-attached device group cannot be hairpin mode when the IP addresses or subnets in the vRouter-attached external network use different firewall settings：虚拟路由器绑定的同一外部网络下的外网子网流量是否过防火墙的行为不一致时，虚拟路由器绑定的设备组的防火墙接入模式不能为旁挂 · The gateway contains members that enable the third-party firewall option. You cannot bind it to the vRouter, because the vRouter has a different setting for its firewall option than any vRouter-attached external vPorts：指定的虚拟路由器绑定的外部网络虚拟端口与该虚拟路由器的流量是否过防火墙行为不一致，不允许绑定对接第三方防火墙的设备组 · The（resource）does not exist or the resources are insufficient：（资源）不存在或资源不足 · The（resource）does not exist or the resources are insufficient, device group name（name）：（资源）不存在或资源不足，设备组名称（名称） · The vRouter is on a vRouter link disabled with the firewall feature. The border gateway for the vRouter must be bound to the same device group as the remote vRouter in the vRouter link：防火墙关闭场景下，该虚拟路由器所属的虚拟路由器连接本端和对端虚拟路由器所绑定的出口网关必须绑定相同的设备组 · The vRouter is bound to an application policy, and the EPGs in the exception rule use the primary/backup gateway deployment mode. You can bind the vRouter to only two gateway members or external subnets：该虚拟路由器已被应用策略绑定，例外规则使用的EPG为主备出口模式，虚拟路由器只能绑定两个出口网关成员或两个外网子网 · The vRouter has been used to create a transit VPC connection. You can bind the vRouter to only one single-member border gateway, and make sure the positions of the associated device group must include border gateway and DC interconnection：虚拟路由器已创建Transit VPC互通，只能绑定一个单成员的出口网关，且网关成员对应设备组的网络位置必须包含出口网关和DC间互联 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · You can bind only one border gateway to an external transit vRouter and the border gateway must have only one gateway member：EXTERNALTRANSIT类型的虚拟路由器只能绑定一个出口网关，且网关成员必须为单成员 · If the edge device to external networks for an external transit vRouter is firewall, the device group position of the border gateways bound to the vRouter must include border gateway and DC interconnection：EXTERNALTRANSIT虚拟路由器外网出口设备为防火墙时，必须绑定设备组网络位置包含出口网关和DC间互联的出口网关 · You can bind only shared border gateways to the local vRouter in a centralized-mode vRouter link when the remote vRouter is an external transit vRouter and has a default subnet included in its external subnets：EXTERNALTRANSIT类型集中式虚拟路由器连接的对端虚拟路由器配置的多数据中心外网网段包含默认网段时，本端虚拟路由器只能绑定共享的出口网关 · The vRouter is bound to a gateway whose firewall deployment mode is off and method to deploy basic external connectivity settings is manual. You cannot bind the vRouter to an external network that does not have gateway bindings or has vPort-vRouter bindings without a gateway specified：当虚拟路由器绑定设备组防火墙接入模式为关闭且外网转发基础配置为手动预配置的出口网关时，不可同时绑定未指定出口网关的外部网络，或者未指定出口网关的已被虚拟路由器外网虚拟端口绑定的外部网络 · When the routing tables created for a vRouter contain a route to 0.0.0.0/0 or ::/0 and the route does not have a next hop, you cannot bind that vRouter to any non-shared border gateway：虚拟路由器关联的路由表中存在路由表项未指定下一跳且目的地址为0.0.0.0/0或::/0，不允许绑定非共享出口网关 · Only transit vRouters support binding tenant-exclusive border gateways and a tenant-exclusive border gateway can have only one transit vRouter binding：租户独占的出口网关只能被一个TRANSIT类型的虚拟路由器绑定 · You can bind only one tenant-exclusive border gateway to a transit vRouter：TRANSIT类型虚拟路由器只能绑定一个租户独占的出口网关 · If you bind a vRouter to a border gateway of the manual deployment type with the external route reduction feature enabled, that vRouter cannot have the same internal subnet address as any of the other vRouters bound to that border gateway：虚拟路由器绑定预配置且外网路由精简开启的出口网关时，不允许该虚拟路由器与该出口网关绑定的其他虚拟路由器存在网段相同的内网子网 · The position of the device group for the border gateway bound to the transit vRouter must be border gateway and DC interconnect：TRANSIT虚拟路由器必须绑定设备组网络位置为出口网关和DC间互联的出口网关 |
|
关键字 |
UNBIND_ROUTER_GW_OP |
|
日志内容 |
Router unbound to gateway: RouterGatewayConfig [routerId=$1, gatewayIdList=[$2]] |
|
参数解释 |
$1：虚拟路由器的ID $2：网关的ID |
|
举例 |
Router unbound to gateway: RouterGatewayConfig [routerId=2b693f0e-70ed-4ef6-ae59-a8fb5272f473, gatewayIdList=[5093467e-158c-4a17-b1b5-710c7bf0da47]] |
|
日志说明 |
用户进行了虚拟路由器解绑网关的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · The service is disabled：服务未启动 · Invalid parameter：无效的配置参数 · Invalid JSON format：无效的JSON格式 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · The virtual router doesn't exist：该虚拟路由器不存在 · The router already has service resource：vRouter已经绑定了服务资源 · The gateway has been used by an MSDP peer：指定的出口网关已经被MSDP使用 · The vRouter is bound to an application policy, and the EPGs in the exception rule use the primary/backup gateway deployment mode. You can bind the vRouter to only two gateway members or external subnets：该虚拟路由器已被应用策略绑定，例外规则使用的EPG为主备出口模式，虚拟路由器只能绑定两个出口网关成员或两个外网子网 · The gateway has been used by a vRouter link that uses the normal firewall mode. Please first delete that vRouter link：该网关已被防火墙模式为NORMAL类型的虚拟路由器连接使用，请先删除虚拟路由器连接 · The tenant contains a transit VPC connection. Please first delete the VPC connection：租户下存在Transit VPC互通，请先删除VPC互通 · The vRouter has bound the external network of the specified gateway：虚拟路由器已经绑定了指定出口网关的外部网络 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · The gateway is bound to an centralized external transit vRouter link that has the local firewall enabled and is operating in centralized mode, Please delete the vRouter link first：该网关已被过墙的EXTERNALTRANSIT类型集中式虚拟路由器连接使用，请先删除该虚拟路由器连接 · If the following conditions exist, you must first unbind the tenant-exclusive border gateways or all service resources from a vRouter when you unbind border gateways from the vRouter: 1. The vRouter has service resource bindings. 2. The vRouter is bound to both a tenant-exclusive border gateway and a non-tenant-exclusive border gateway. 3. The gateway member of the tenant-exclusive border gateway and a gateway member of the non-tenant-exclusive border gateway are associated with the same device group：虚拟路由器绑定了服务资源，同时也绑定了租户独占的出口网关和非租户独占的出口网关，且两个出口网关的出口网关成员关联了同一个设备组，需要虚拟路由器先解绑租户独占的出口网关或者所有的服务资源 · You cannot unbind a border gateway from a vRouter when the border gateway is bound to an interconnect interface that has a BGP neighbor binding：虚拟路由器不允许解绑互联接口被BGP邻居绑定的出口网关 · The gateway has been used by another Anycast-RP：指定的出口网关已经被Anycast-RP使用 |
|
关键字 |
UNBIND_VROUTER_OP |
|
日志内容 |
Deleted vRouter $1 from resource $2. |
|
参数解释 |
$1：虚拟路由器的名称 $2：服务资源的ID |
|
举例 |
Deleted vRouter route1 from resource aa68bc06-8e30-468d-a805-d4f48952c646. |
|
日志说明 |
用户进行了虚拟路由器解绑服务资源的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · The service is disabled：服务未启动 · Invalid parameter：无效的配置参数 · Invalid JSON format：无效的JSON格式 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · The virtual router doesn't exist：该虚拟路由器不存在 · Unknown internal server error：未知的内部服务器错误 · You have no privilege to perform this operation：用户无权限执行此操作 · The vRouter has been used for a transit VPC connection. Please first delete the VPC connection：虚拟路由器已被Transit VPC互通使用，请先删除VPC互通 · The firewall has been used by a vRouter link that uses the normal firewall mode. Please first delete that vRouter link：该防火墙资源已被防火墙模式为NORMAL类型的虚拟路由器连接使用，请先删除虚拟路由器连接 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · The firewall is already used by a centralized external transit vRouter link. Please delete that vRouter link first：该防火墙已被EXTERNALTRANSIT类型集中式虚拟路由器连接使用，请先删除集中式虚拟路由器连接 |
|
关键字 |
CREATE_LAG_INTERFACE_MEMBER_OP |
|
日志内容 |
Created LAG interface member: $1 |
|
参数解释 |
$1：聚合接口成员的配置信息 |
|
举例 |
Created LAG interface member: ID: [beea3a3d-685d-4e22-b64c-44b1a360b19c] Name: [ceshi] Description: [Description] Device ID: [fc8bbc44-76a6-4654-a0eb-1e6cdb642b95] Device name: [68] Group ID: [9f42cc59-80a6-4d52-98d7-847b4c360882] LACP short period enable: [False] Member port: [FortyGigE1/0/49] Interface number: [7] Group mode: [1] Member port priority: [123] Selected status: [0] Unselected reason: [0] |
|
日志说明 |
用户进行了创建聚合接口成员的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · The service is disabled：服务未启动 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Invalid name：无效的名称 · Invalid description：无效的描述信息 · Unknown internal server error：未知的内部服务器错误 · The LAG interface member already exists on the device：该聚合接口成员在指定的网元上已存在 · The LAG interface member already exists：该聚合接口成员已存在 · The device ID doesn't exist：指定的网元ID不存在 · The LAG interface doesn't exist on the device：指定的网元上不存在该聚合接口 · Invalid interface priority：无效的接口优先级 · The device ID cannot be null：指定的网元ID不能为空 · No LAG interface ID is specified：未指定聚合接口ID · No name is specified：未指定名称 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · The LAG interface member configuration is mutually exclusive with interface-permitted VLAN configuration：指定的聚合接口成员与接口Permit VLAN冲突 |
|
关键字 |
UPDATE_LAG_INTERFACE_MEMBER_OP |
|
日志内容 |
Updated LAG interface member: $1 |
|
参数解释 |
$1：聚合接口成员的配置信息 |
|
举例 |
Updated LAG interface member: ID: [beea3a3d-685d-4e22-b64c-44b1a360b19c] Name: [ceshi] Description: [Change] Device ID: [fc8bbc44-76a6-4654-a0eb-1e6cdb642b95] Device name: [68] Group ID: [9f42cc59-80a6-4d52-98d7-847b4c360882] LACP short period enable: [False] Member port: [FortyGigE1/0/49] Interface number: [7] Group mode: [1] Member port priority: [456] Selected status: [0] Unselected reason: [0] |
|
日志说明 |
用户进行了修改聚合接口成员的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · The service is disabled：服务未启动 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Invalid name：无效的名称 · Invalid description：无效的描述信息 · Unknown internal server error：未知的内部服务器错误 · The LAG interface member doesn't exist：该聚合接口成员不存在 · The LAG interface and member interface are different types：该聚合接口成员的接口类型与指定聚合接口所对应的聚合接口类型不一致 · Invalid interface priority：无效的接口优先级 · The LAG interface ID doesn't exist：指定的聚合接口ID不存在 · The LAG interface member is created through the bare metal module and cannot be modified：该聚合接口成员通过裸金属管理模块创建，不允许修改 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
DELETE_LAG_INTERFACE_MEMBER_OP |
|
日志内容 |
Deleted LAG interface member: $1 |
|
参数解释 |
$1：聚合接口成员的ID |
|
举例 |
Deleted LAG interface member: beea3a3d-685d-4e22-b64c-44b1a360b19c |
|
日志说明 |
用户进行了删除聚合接口成员的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service is disabled：服务未启动 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · The LAG interface member doesn't exist：该聚合接口成员不存在 · The LAG interface member is created through the bare metal module and cannot be deleted：该聚合接口成员通过裸金属管理模块创建，不允许删除 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
DELETE_M-LAG_LAG_INTERFACE_MEMBER_OP |
|
日志内容 |
Deleted M-LAG LAG interface member: $1 |
|
参数解释 |
$1：聚合接口成员的ID |
|
举例 |
Deleted M-LAG LAG interface member: beea3a3d-685d-4e22-b64c-44b1a360b19c |
|
日志说明 |
用户进行了删除M-LAG聚合接口成员的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown internal server error：未知的内部服务器错误 |
|
关键字 |
CREATE_LAG_INTERFACE_OP |
|
日志内容 |
Created LAG interface: $1 |
|
参数解释 |
$1：聚合接口的配置信息 |
|
举例 |
Created aggregation group: ID: [9f42cc59-80a6-4d52-98d7-847b4c360882] Name: [test] Device ID: [fc8bbc44-76a6-4654-a0eb-1e6cdb642b95] Device name: [68] Interface number: [7] Link mode: [Dynamic] Link type: [TRUNK] LACP edge enable: [False] Load sharing mode type: [Default] VTEP enable: [False] |
|
日志说明 |
用户进行了创建聚合接口的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · The service is disabled：服务未启动 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Invalid name：无效的名称 · Invalid description：无效的描述信息 · Unknown internal server error：未知的内部服务器错误 · Duplicate LAG interface ID：该聚合接口已存在 · The device ID doesn't exist：指定的网元ID不存在 · The LAG interface ID is invalid：无效的聚合接口编号 · The LAG interface cannot be used as an access interface：该聚合接口对应的聚合接口不能作为接入接口 · The LAG interface already exists on the device：该聚合接口在指定的网元上已存在 · The LAG interface doesn't exist：该聚合接口不存在 · No available LAG interface numbers：无可分配的聚合组编号 · The global LAG interface settings are not configured：未配置聚合接口全局配置 · The LAG interface number cannot be a reserved number：指定的聚合接口编号不能属于聚合接口预留编号范围内 · The LAG interface number has been used by another group：指定的聚合接口编号已被其他聚合接口使用 · You have no privilege to perform this operation：用户无权限执行此操作 · Invalid link type：无效的链路类型 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · The LAG interface configuration conflicts with interface-permitted VLAN configuration：指定的聚合接口与接口Permit VLAN配置有冲突 · No LAG interface number is assigned：没有分配到聚合接口编号 · The LAG interface number on a device is in the range of 1 to 16384. It cannot use the default peer-link LAG interface number 256 or exceed the maximum number supported by the device：设备内聚合接口编号范围为1-16384，不可占用peer link聚合接口默认编号256，且不可超过设备支持的最大编号 · The specified LAG interface number on the device is in use：指定设备内聚合接口编号已经被使用 · You cannot configure downlink interfaces for the device, because the device has been bound to a global VLAN-VXLAN mapping：设备已绑定全局VLAN-VXLAN映射，不允许配置下行口 |
|
关键字 |
UPDATE_LAG_INTERFACE_OP |
|
日志内容 |
Updated LAG interface: $1 |
|
参数解释 |
$1：聚合接口的配置信息 |
|
举例 |
Updated LAG interface: ID: [ff9f1d56-507f-4190-bc52-70da3fe96dc5] Name: [test] Description: [B] Device ID: [fc8bbc44-76a6-4654-a0eb-1e6cdb642b95] Device name: [68] Interface number: [7] Link mode: [Dynamic] Link type: [TRUNK] LACP edge enable: [False] Load sharing mode type: [Default] VTEP enable: [True] |
|
日志说明 |
用户进行了修改聚合接口的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · The service is disabled：服务未启动 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Invalid description：无效的描述信息 · Unknown internal server error：未知的内部服务器错误 · The LAG interface doesn't exist：该聚合接口不存在 · The LAG interface is created through the bare metal module and cannot be modified：该聚合接口通过裸金属管理模块创建，不允许修改 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · VLAN-network mappings are bound to member ports of the edge aggregate interface. You cannot change the edge aggregate interface to a non-edge aggregate interface：聚合边缘接口下成员接口已绑定VLAN-Network类型映射，不支持切换为非聚合边缘接口 |
|
关键字 |
DELETE_LAG_INTERFACE_OP |
|
日志内容 |
Deleted LAG interface: $1 |
|
参数解释 |
$1：聚合接口的ID |
|
举例 |
Deleted LAG interface: ID: [e354314c-ea82-4edf-9f6c-a779449a3fd5] Name: [11] Index: [256] |
|
日志说明 |
用户进行了删除聚合接口的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service is disabled：服务未启动 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · The LAG interface doesn't exist：该聚合接口不存在 · The LAG interface is created through the bare metal module and cannot be deleted：该聚合接口通过裸金属管理模块创建，不允许删除 · You cannot delete the LAG interface, because it has been used by a resource access template：该设备内聚合接口已被资源接入模板引用，不允许删除 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · To delete the LAG interface, first delete interface-permitted VLAN configuration on the LAG interface：接口Permit VLAN已关联该聚合接口，请先删除接口Permit VLAN · The aggregate interface has been configured with a PVID. Please first delete the PVID configuration on the interface：聚合接口已配置PVID，请先删除接口PVID配置 · VLAN-network mappings are bound to member ports of the edge aggregate interface. Please first delete the VLAN-network mappings from the member ports：聚合边缘接口下成员接口绑定了VLAN-Network类型映射,请先删除成员接口的映射 · The LAG interface is already used by an interconnect interface：聚合接口已被互联接口使用 |
|
关键字 |
CREATE_GLOBAL_LAG_INTERFACE_CONFIG_OP |
|
日志内容 |
Created global LAG interface configuration: $1 |
|
参数解释 |
$1：聚合接口全局配置信息 |
|
举例 |
Created global LAG interface configuration: ID: [b57f56eb-bb3f-4908-bb68-1e1c4508a210] Name: [test] Description: [666] Device ID: [fc8bbc44-76a6-4654-a0eb-1e6cdb642b95] Device name: [68] System priority: [32768] Load sharing mode: [0] Reserved group indexes: [1-16384] |
|
日志说明 |
用户进行了创建聚合接口全局配置的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · The service is disabled：服务未启动 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Invalid name：无效的名称 · Invalid description：无效的描述信息 · Unknown internal server error：未知的内部服务器错误 · The global LAG interface configuration already exists：指定的网元上已存在聚合接口全局配置 · Duplicate global LAG interface configuration：该聚合接口全局配置已存在 · Invalid reserved LAG interface numbers：无效的聚合接口预留编号 · You have no privilege to perform this operation：用户无权限执行此操作 · The NE doesn't exist：该物理网元不存在 · The device type does not support binding interfaces：网元类型不匹配 · The UUID of the reserved LAG interface number range already exists：指定的聚合接口预留编号范围的UUID已存在 · A reserved LAG interface number range has been configured for the device. You can configure only one reserved LAG interface number range for a device：一台设备仅允许配置一个聚合接口预留编号范围，指定设备已配置了聚合接口预留编号范围 · Invalid reserved LAG interface number range：无效的聚合接口预留编号范围 · A LAG interface exists on the device. You cannot create a reserved LAG interface number range：指定的设备已存在设备内聚合接口时，不允许创建聚合接口预留编号范围 |
|
关键字 |
UPDATE_GLOBAL_LAG_INTERFACE_CONFIG_OP |
|
日志内容 |
Updated global LAG interface configuration: $1 |
|
参数解释 |
$1：聚合接口全局配置信息 |
|
举例 |
Updated global LAG interface configuration: ID: [b57f56eb-bb3f-4908-bb68-1e1c4508a210] Name: [test] Description: [66666666] Device ID: [fc8bbc44-76a6-4654-a0eb-1e6cdb642b95] Device name: [68] System priority: [32768] Load sharing mode: [0] Reserved group indexes: [1-16384] |
|
日志说明 |
用户进行了修改聚合接口全局配置的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · The service is disabled：服务未启动 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Invalid description：无效的描述信息 · Unknown internal server error：未知的内部服务器错误 · The global LAG interface configuration doesn't exist：该聚合接口全局配置不存在 · You have no privilege to perform this operation：用户无权限执行此操作 · The UUID of the reserved LAG interface number range does not exist：指定的聚合接口预留编号范围的UUID不存在 |
|
关键字 |
DELETE_GLOBAL_LAG_INTERFACE_CONFIG_OP |
|
日志内容 |
Deleted global LAG interface configuration: $1 |
|
参数解释 |
$1：聚合接口全局配置的ID |
|
举例 |
Deleted global LAG interface configuration: 7c3bcda6-7bec-4318-bd7b-3e49fc96c54e |
|
日志说明 |
用户进行了删除聚合接口全局配置的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service is disabled：服务未启动 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · The global aggregation group configuration doesn't exist：该聚合接口全局配置不存在 · The device is configured with LAG interfaces. Cannot delete the global LAG interface settings：设备上存在聚合接口，无法删除聚合接口全局配置 · You have no privilege to perform this operation：用户无权限执行此操作 · LAG interfaces exist on the device. You cannot delete the reserved LAG interface number range：指定的设备已存在设备内聚合接口时，不允许删除聚合接口预留编号范围 · The UUID of the reserved LAG interface number range does not exist：指定的聚合接口预留编号范围的UUID不存在 |
|
关键字 |
DELETE_NE_TUNNEL_OP |
|
日志内容 |
Deleted NE VXLAN tunnels: NE ID: $1 Tunnels: $2 |
|
参数解释 |
$1：网元的ID $2：VXLAN隧道列表 |
|
举例 |
Deleted NE VXLAN tunnels: NE ID: 28424135-36f5-4dde-ad2e-29580411de8d Tunnels: [ { Source IP: 98.0.57.16 Destination IP: 6.6.6.3 } ] |
|
日志说明 |
用户进行了删除控制组件内存中指定网元上指定VXLAN隧道的操作，但设备上对应的VXLAN隧道不会被删除 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · The service is disabled：服务未启动 · The NE doesn't exist：该设备不存在 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Invalid JSON format：无效的JSON格式 · Unknown internal server error：未知的内部服务器错误 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_CONNECTIONLIMIT_OP |
|
日志内容 |
Created connection limit rule: $1 |
|
参数解释 |
$1：连接数限制规则的配置信息 |
|
举例 |
Created connection limit rule: ID: [fecaab1f-2dc4-4cb0-b77a-2a4dbdfb9da8] Name: [connlimit] Description: [conn-vsr] Tenant ID: [ffffffff-0000-0000-0000-000000000001] AE type: [subnet] Per-service connection limit: [true] Per-source connection limit: [false] Per-destination connection limit: [true] Upper limit connection limit: [100] Lower limit connection limit: [100] AE list: [ { AE ID: [f98344e9-927e-4697-a6df-1170ed08eb4b] Limit direction: [ALL] } ] |
|
日志说明 |
用户进行了创建连接数限制规则的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · The service is disabled：服务未启动 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · The lower connection limit cannot be larger than the upper connection limit：连接数上限不能小于连接数下限 · Please select at least one of the per-service, per-source, and per-destination connection limit filtering methods：服务限制、源IP限制和目的IP限制三种限制方式至少开启一种 · A virtual subnet or vPort can be bound to only one connection limit rule：每个虚拟子网或虚拟端口只能被引用一次 · The virtual subnet or vPort doesn't exist：指定的虚拟子网或虚拟端口不存在 · The virtual subnet or vPort doesn't belong to the tenant：虚拟子网或虚拟端口不属于该租户 · The limit direction must be IN, OUT, or ALL：应用方向的取值必须是出方向、入方向和全部方向中的一种 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_CONNECTIONLIMIT_OP |
|
日志内容 |
Updated connection limit rule: $1 |
|
参数解释 |
$1：连接数限制规则的配置信息 |
|
举例 |
Updated connection limit rule: ID: [fecaab1f-2dc4-4cb0-b77a-2a4dbdfb9da8] Name: [connlimit] Description: [conn-vsr] Tenant ID: [ffffffff-0000-0000-0000-000000000001] AE type: [subnet] Per-service connection limit: [true] Per-source connection limit: [false] Per-destination connection limit: [true] Upper limit connection limit: [100] Lower limit connection limit: [100] AE list: [ { AE ID: [f98344e9-927e-4697-a6df-1170ed08eb4b] Limit direction: [ALL] } ] |
|
日志说明 |
用户进行了修改连接数限制规则的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · The service is disabled：服务未启动 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · The lower connection limit cannot be larger than the upper connection limit：连接数上限不能小于连接数下限 · The virtual subnet or vPort doesn't exist：指定的虚拟子网或虚拟端口不存在 · The virtual subnet or vPort doesn't belong to the tenant：虚拟子网或虚拟端口不属于该租户 · The limit direction must be IN, OUT, or ALL：应用方向的取值必须是出方向、入方向和全部方向中的一种 · Please select at least one of the per-service, per-source, and per-destination connection limit filtering methods：服务限制、源IP限制和目的IP限制三种限制方式至少开启一种 · A virtual subnet or vPort can be bound to only one connection limit rule：每个虚拟子网或虚拟端口只能被引用一次 · The AE type field is read only：应用类型字段为只读字段 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_CONNECTIONLIMIT_OP |
|
日志内容 |
Deleted connection limit rule: $1 |
|
参数解释 |
$1：连接数限制规则的ID |
|
举例 |
Deleted connection limit rule: fecaab1f-2dc4-4cb0-b77a-2a4dbdfb9da8 |
|
日志说明 |
用户进行了删除连接数限制规则的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service is disabled：服务未启动 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · The connection limit rule doesn't exist：该连接数限制规则不存在 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_CONFIGURE_TEMPLATE_OP |
|
日志内容 |
Created device deployment template: $1 |
|
参数解释 |
$1：设备上线模板的配置信息 |
|
举例 |
Created device deployment template: ID:[95ef9fd6-e3b5-4238-8215-2e21082772dd] Fabric ID:[7b892fe9-4227-49f0-94ed-f3be16c3d4b2] File path:[null] Name:[11.template] Description:[null] CommandSegment:[null] Role name:[spine] Username:[null] Password:[******] NTP server address:[null] Control protocol template ID:[f6cfecf8-a967-4e75-a900-fa2857a01679] Software ID:[null] Software name:[null] Software version:[null] Patch ID:[null] Patch name:[null] Patch version:[null] Patch size:[null] Aggregation mode:[null] IRF stacking:[true] Border IRF stacking:[false] Enable aggregation:[null] Enable mlag:[false] Mlag mode:[null] M-LAG group ID range:[null] Master spine MAC:[null] BGP RR MAC:[22:22:22:22:22:22] ECMP configure:[null] IS-IS name:[null] IS-IS password:[******] Spine BGP AS Number:[null] Leaf BGP AS number:[null] BGP MD5 password:[******] Border MAC:[null] EVPN control:[null] OSPF ID:[11] OSPF area:[11] IS-IS ID:[null] Underlay IP range:[null] LoopBack1 IP range:[null] Backup server:[null] Access capability:[false] BFD mad:[true] Needwhitelist:[true] CustomizedDeviceInfo:[null] Reserved LAG interface number range:[1-25] restoreDelay:[55] |
|
日志说明 |
用户进行了创建设备上线模板的操作 |
|
失败原因 |
· Invalid JSON format：无效的JSON格式 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · Invalid template name：无效的设备上线模板名称 · A deployment template of a specific role has existed in the same fabric：同一Fabric下指定角色的设备上线模板已存在 · The fabric doesn't exist：指定的Fabric不存在 · ECMP is not supported when the underlay protocol is OSPF：Underlay路由协议为OSPF时不支持配置ECMP功能 · ECMP must be configured when the underlay protocol is IS-IS or EBGP：Underlay路由协议为ISIS或EBGP时必须配置ECMP功能 · The deployment template name already exists：指定名称的设备上线模板已存在 · The BGP AS number in the deployment template is different from the BGP AS number in the fabric to which the deployment template belongs：当前设备上线模板的BGP AS号与所属Fabric的BGP AS号不一致 · The BGP route reflector MAC can be configured only when EVPN is enabled：仅在EVPN开启时才可配置BGP路由反射器的MAC地址 · Invalid BGP route reflector MAC：BGP路由反射器的MAC地址无效 · Invalid role name：无效的角色名称 · The control protocol template doesn't exist：指定的设备控制协议模板不存在 · The deployment template name for all devices in the same fabric must be the same：同一Fabric下所有设备上线模板的名称必须一致 · The fabric ID is required：未指定Fabric ID · The NTP server IP address is required：NTP服务器IP地址不能为空 · The username and password are required：用户名和密码不能为空 · The username and password must be the same for roles in the same fabric：同一Fabric下不同角色的用户名和密码必须相同 · A border can be configured to operate in IRF mode only when the underlay protocol is OSPF or EBGP and EVPN is enabled：仅当Underlay路由协议为OSPF或EBGP且EVPN开启时才能配置Border为IRF模式 · The BGP RR MAC is required when EVPN is enabled：EVPN开启时必须指定BGP路由反射器的MAC地址 · Interface aggregation mode can be enabled for leaf devices only when the underlay protocol is IS-IS and EVPN is disabled：仅当Underlay路由协议为ISIS且EVPN关闭时，Leaf角色的设备上线模板才可开启接口聚合模式 · Invalid interface aggregation mode：无效的接口聚合模式 · Interface aggregation mode can be enabled for spine devices only when the underlay protocol is IS-IS and EVPN is enabled：仅当Underlay路由协议为ISIS且EVPN开启时，Spine角色的设备上线模板才可配置接口聚合模式 · The IS-IS username and password are required when the underlay protocol is IS-IS：Underlay路由协议为ISIS时需指定ISIS用户名和对称密钥 · The ISIS username and password can be configured only when the underlay protocol is IS-IS：仅当Underlay路由协议为ISIS时才可指定ISIS用户名和对称密钥 · The leaf/spine AS number is required when the underlay protocol is EBGP：Underlay路由协议为EBGP时，Leaf角色的设备上线模板必须指定Leaf BGP AS号和Spine BGP AS号 · The Loopback1 IP range is required when the underlay protocol is EBGP, and the role name is spine：仅当Underlay路由协议为EBGP时，Spine角色的设备上线模板才可指定Underlay管理地址池的IP地址范围 · Invalid border MAC：无效的Border MAC地址 · The border MAC is required when EVPN and optional parameter configuration are enabled：EVPN开启且可选配置开关开启时必须配置Border MAC地址 · The deployment template file already exists：指定的设备上线模板文件已存在 · The EVPN control feature can be configured only when EVPN is disabled：当EVPN功能关闭时，可以配置设备上线模板中的EVPN控制功能 · Invalid description：设备描述格式不正确 · A command line in the template can contain a maximum of 512 characters. Chinese characters are not supported：设备上线模板中命令行最长支持512个字符，不支持中文 · Invalid IS-IS host name or neighbor authentication password：无效的ISIS主机名称或邻居关系验证密码 · Invalid BGP MD5 password：指定BGP的MD5认证密码无效 · Invalid ECMP settings：无效的ECMP配置 · In the deployment template, the BGP AS number, the BGP AS number for a spine device, and the BGP AS number for a leaf device must be different when the underlay protocol is EBGP：Underlay路由协议为EBGP时，设备上线模板中BGP AS号、Spine配置BGP AS号和Leaf配置的BGP AS号均不能相同 · the leaf bgp as num or spine bgp as num can configure only when the protocol is EBGP：仅当Underlay路由协议为EBGP时，Leaf角色的设备上线模板才可配置Leaf BGP AS号和Spine BGP AS号 · The BGP MD5 password can be configured only when you enable optional parameter configuration：仅当进行可选配置时，才需指定BGP的MD5密码 · The border MAC address can be configured only when you enable both EVPN and optional parameter configuration：仅当EVPN开启且可选配置开关开启时才可配置Border MAC地址 · The template file name must end with character string .template：设备上线模板文件名称必须以.template结尾 · Invalid BGP AS number：无效的BGP AS号 · The fabric doesn't exsit：指定Fabric不存在 · The BGP AS number cannot be modified because the fabric has network elements：指定Fabric下存在网元设备，设备上线模板中的BGP AS无法修改 · The NTP server address is required when the underlay protocol is OSPF or EBGP：当Underlay路由协议为OSPF或EBGP时，必须指定NTP服务器地址 · The NTP server address cannot be configured when the underlay protocol is IS-IS and EVPN is disabled：Underlay路由协议为ISIS且EVPN关闭时，不能配置NTP服务器地址 · The template does not exist：指定UUID的设备上线模板不存在 · The template cannot be modified：导入的设备上线模板不支持修改 · The master or spine MAC address is required：未指定Master或Spine MAC地址 · The device deployment template name is required：未指定设备上线模板的名称 · The software version or patch does not exist：指定的软件版本或软件补丁不存在 · The role name is required：未指定角色名称 · The template file path is required：未指定上传设备上线模板文件的路径 · The Loopback1 IP range is required when the underlay protocol is EBGP, and the role name is spine：Underlay路由协议为EBGP时，Spine角色的设备上线模板必须指定Underlay管理地址池的IP地址范围 · The fabric ID of the deployment template and the fabric ID of the used control protocol template must be the same：设备上线模板的Fabric ID和引用的设备控制协议模板的Fabric ID必须一致 · The fabric ID is required：未指定Fabric ID · Invalid NTP server address：无效的NTP服务器IP地址 · Invalid master spine MAC address：无效的Master Spine MAC地址 · The IS-IS process ID is required when the underlay protocol is IS-IS：当Underlay路由协议为ISIS时，必须指定ISIS的进程ID。 · The border MAC is required when EVPN is enabled：EVPN开启时必须配置Border MAC地址 · Invalid command line：无效的命令行 · Invalid is-is name or password：无效的ISIS用户名和密码 · A border can be configured to operate in IRF mode only when the underlay protocol is OSPF or EBGP and EVPN is enabled：仅当Underlay路由协议为OSPF或EBGP且EVPN开启时才能配置Border为IRF模式。 · The spine BGP AS number cannot be the same as the leaf BGP AS number：Spine角色和Leaf角色设备的BGP AS号不能相同 · The leaf BGP AS number and spine BGP AS number can be configured only when the protocol is BGP：仅当协议为BGP时，Spine角色和Leaf角色的设备才可配置AS号 · The Loopback1 IP range can be configured only when the underlay protocol is EBGP, and the role name is spine：仅当Underlay路由协议为EBGP时，Spine角色的设备上线模板才可指定Underlay管理地址池的IP地址范围。色必须指定Loopback1的IP地址范围 · The loopback1 ip range must require when the protocol is bgp and the role is spine：只有BGP协议下，Spine角色必须指定 loopback1 ip地址范围 · The OSPF process ID is required when the underlay protocol is OSPF：当Underlay路由协议为OSPF时，必须指定OSPF的进程ID。Invalid OSPF process ID：无效的OSPF进程ID。 · Invalid IS-IS process ID：无效的ISIS进程ID。 · The OSPF process ID can be configured only when the underlay protocol is OSPF：仅当Underlay路由协议为OSPF时才可配置OSPF进程ID。 · The IS-IS process ID can be configured only when the underlay protocol is IS-IS：仅当Underlay路由协议为ISIS时才可配置ISIS进程ID。 · The OSPF process IDs in the deployment templates of all devices in a fabric must be the same.：同一Fabric下设备上线模板中的OSPF进程ID必须相同。The IS-IS process IDs in the deployment templates of all devices in a fabric must be the same：同一Fabric下设备上线模板中ISIS进程ID必须相同。 · The NTP server address is required when the underlay protocol is OSPF or EBGP：当Underlay路由协议为OSPF或EBGP时，必须指定NTP服务器地址。 · The NTP server address cannot be configured when the underlay protocol is IS-IS and EVPN is disabled：Underlay路由协议为ISIS且EVPN关闭时，不能配置NTP服务器地址 · The role name is required：未指定角色名称 · The template file path is required：未指定上传设备上线模板文件的路径。 · The master or spine MAC address is required：未指定Master或Spine MAC地址 · The CIDR is required：没有携带CIDR · Invalid CIDR：无效的CIDR · The Loopback1 IP range can be configured for the spine deployment template only when the underlay protocol is EBGP：仅当Underlay路由协议为EBGP时，Spine角色的配置模板才可指定Loopback1 IP地址范围 · Cannot configure the underlay IP range when the fabric allocation mode is controller allocation：Fabric分配方式为控制组件分配时，不允许配置 Underlay IP地址范围 · Cannot configure the Loopback1 IP range when the fabric allocation mode is controller allocation：Fabric分配方式为控制组件分配时，不允许配置 Loopback1 IP地址范围 · The underlay IP range is required when the fabric allocation mode is master spine allocation：Fabric分配方式为Master Spine分配时，必须配置Underlay IP地址范围 · The Loopback1 IP range is required when the fabric allocation mode is master spine allocation：Fabric分配方式为Master Spine分配时，必须配置Loopback1 IP地址范围 · The underlay IP range can be specified only for spine devices：仅Spine角色可以指定Underlay IP地址范围 · The underlay IP range cannot contain existing VTEP IPs：Underlay IP范围不允许包含已存在的VTEP IP · The loopback1 IP range cannot contain existing VTEP IPs：Loopback1 IP范围不允许包含已存在的VTEP IP · The underlay IP range overlaps with an existing IP range：Underlay IP范围与当前已有IP 范围重叠 · The loopback1 IP range overlaps with an existing IP range：Loopback1 IP范围与当前已有IP 范围重叠 · The underlay IP range overlaps with loopback1 IP range：Underlay IP地址范围与Loopback1 IP地址池范围重叠 · The underlay routing protocol can only be OSPF for an aggregation device：设备角色为aggregation时，Underlay路由协议仅支持OSPF · You cannot assign a BGP AS number to an aggregation device：设备角色为aggregation时不支持配置BGP AS号 · An aggregation device does not support border IRF stacking：设备角色为aggregation时不支持Border IRF堆叠 · You cannot configure EVPN for an aggregation device：设备角色为aggregation时不支持配置EVPN · BGP RR MAC is not configurable because an aggregation device cannot act as a BGP RR：设备角色为aggregation时不支持配置BGP RR MAC · You cannot set a BGP MD5 password for an aggregation device：设备角色为aggregation时不支持配置BGP MD5密码 · Border MAC is not configurable because you cannot configure an aggregation device as a border device：设备角色为aggregation时不支持配置Border MAC · You have no privilege to perform this operation：用户无权限执行此操作 · Please specify a NETCONF username and password for the default protocol template：default_protocol_template模板的NETCONF用户名密码不能为空 · The OSPF area ID is required when the underlay protocol is OSPF：当Underlay路由协议为OSPF时，必须指定OSPF Area ID · Invalid OSPF area ID：无效的OSPF Area ID · The OSPF area ID can be configured only when the underlay protocol is OSPF：仅当Underlay路由协议为OSPF时才可配置OSPF Area ID · The OSPF area ID in the deployment templates of all devices in a fabric must be the same：同一Fabric下设备上线模板中的OSPF Area ID必须相同 · An access device does not support border IRF stacking：设备角色为Access时不支持Border IRF堆叠 · An access device does not support IRF stacking：设备角色为Access时不支持IRF堆叠 · Please do not configure ECMP settings for an access device：设备角色为Access时不需要配置ECMP功能 · Please do not configure IS-IS settings for an access device：设备角色为Access时不需要指定ISIS相关配置 · Please do not configure OSPF settings for an access device：设备角色为Access时不需要指定OSPF相关配置 · Please do not configure BGP settings for an access device：设备角色为Access时不需要指定BGP相关配置 · An access device does not support EVPN settings：设备角色为Access时不支持配置EVPN · An access device does not support a border MAC：设备角色为Access时不支持配置Border MAC · The critical VLAN ID must be an integer in the range of 2 to 4094：取值范围为2～4094的整数 · The reserved VXLAN ID must be an integer in the range of 1 to 16777215：取值范围为1～16777215的整数 · Invalid keepalive link type：Keepalive链路取值无效 · Please specify a keepalive link type：Keepalive链路取值不能为空 · Make sure the reserved VXLAN is not in any existing VXLAN pool：设备上线模板的保留VXLAN不允许和已存在的VXLAN池重叠 · Invalid M-LAG group ID range：无效的M-LAG组编号范围 · Invalid interface aggregation mode：无效的接口聚合模式 · Please specify the M-LAG group ID range：必须指定M-LAG组编号范围 · Invalid management VPN instance name：无效的管理网VPN实例名称 · The management VPN instance name conflicts with the name of the VPN instance for the M-LAG keepalive link：管理网VPN实例名称与跨设备聚合Keepalive链路的VPN实例名称冲突 · When network mode is M-LAG, you must configure the SNMP version in the control protocol template. Available options are SNMP_v2c and SNMP_v3. If you select SNMP_v2c, you must also configure a read community name：当使能跨设备聚合时，设备控制协议模板中的SNMP版本必选，SNMP版本支持取值为SNMP_v2c或SNMP_v3，且SNMP版本为SNMP_v2c时，读团体名不能为空 · Only leaf devices support automatic configuration of downlink interfaces：仅Leaf设备支持配置使能下行口配置自动下发 · If fabric service network type is vlan, automatic configuration of downlink interfaces is not supported：VLAN类型的Fabric不支持配置使能下行口配置自动下发 · The reserved LAG interface number range must de comma-separated list of integers (1 to 16384) or integer ranges (x-y, x can’t be greater than y). Up to 255 characters. Example: 200,201-205：聚合接口预留编号范围取值范围为1～16384的整数或区间，例如：200或201-205；当取值为区间时，起始值不能大于结束值。如需输入多个整数或区间，中间需用","隔开且输入长度不能超过255个字符 · Invalid network mode. Please specify the network mode as MLAG, IRF, or STAND_ALONE：无效的组网模式，组网模式不可为空，取值为MLAG、IRF或STAND_ALONE · The data restoration delay must be an integer in the range of 1 to 3600：延迟恢复时间取值范围为1~3600的整数 · Invalid bgp as number：无效的BGP AS号 · Invalid spine bgp as number：无效的Spine BGP AS号 · Invalid aggregation bgp as number：无效的Aggregation BGP AS号 · Invalid leaf bgp as number：无效的Leaf BGP AS号 · The old and new bgp as numbers are inconsistent：新旧BGP AS号字段不一致 · The old and new spine bgp as numbers are inconsistent：新旧Spine BGP AS号字段不一致 · The old and new aggregation bgp as numbers are inconsistent：新旧Aggregation BGP AS号字段不一致 · The old and new leaf bgp as numbers are inconsistent：新旧Leaf BGP AS号字段不一致 |
|
关键字 |
UPDATE_CONFIGURE_TEMPLATE_OP |
|
日志内容 |
Updated device deployment template: $1 |
|
参数解释 |
$1：设备上线模板的配置信息 |
|
举例 |
Updated device deployment template: ID:[95ef9fd6-e3b5-4238-8215-2e21082772dd] Fabric ID:[7b892fe9-4227-49f0-94ed-f3be16c3d4b2] File path:[null] Name:[11.template] Description:[null] CommandSegment:[null] Role name:[spine] Username:[null] Password:[******] NTP server address:[null] Control protocol template ID:[f6cfecf8-a967-4e75-a900-fa2857a01679] Software ID:[null] Software name:[null] Software version:[null] Patch ID:[null] Patch name:[null] Patch version:[null] Patch size:[null] Aggregation mode:[null] IRF stacking:[true] Border IRF stacking:[false] Enable aggregation:[null] Enable mlag:[false] Mlag mode:[null] M-LAG group ID range:[null] Master spine MAC:[null] BGP RR MAC:[22:22:22:22:22:22] ECMP configure:[null] IS-IS name:[null] IS-IS password:[******] Spine BGP AS Number:[null] Leaf BGP AS number:[null] BGP MD5 password:[******] Border MAC:[null] EVPN control:[null] OSPF ID:[11] OSPF area:[11] IS-IS ID:[null] Underlay IP range:[null] LoopBack1 IP range:[null] Backup server:[null] Access capability:[false] BFD mad:[true] Needwhitelist:[true] CustomizedDeviceInfo:[null] Reserved LAG interface number range:[1-25] restoreDelay:[55] |
|
日志说明 |
用户进行了修改设备上线模板的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · The fabric doesn't exist：指定的Fabric不存在 · The control protocol template doesn't exist：指定的设备控制协议模板不存在 · Invalid description：设备描述格式不正确 · The NTP server IP address is required：NTP服务器IP地址不能为空 · The username and password are required：用户名和密码不能为空 · The username and password must be the same for roles in the same fabric：同一Fabric下不同角色的用户名和密码必须相同 · A border can be configured to operate in IRF mode only when the underlay protocol is OSPF or EBGP and EVPN is enabled：仅当Underlay路由协议为OSPF或EBGP且EVPN开启时才能配置Border为IRF模式 · The BGP RR MAC is required when EVPN is enabled：EVPN开启时必须指定BGP路由反射器的MAC地址 · Interface aggregation mode can be enabled for leaf devices only when the underlay protocol is IS-IS and EVPN is disabled：仅当Underlay路由协议为ISIS且EVPN关闭时，Leaf角色的设备上线模板才可开启接口聚合模式 · Invalid interface aggregation mode：无效的接口聚合模式 · Interface aggregation mode can be enabled for spine devices only when the underlay protocol is IS-IS and EVPN is enabled：仅当Underlay路由协议为ISIS且EVPN开启时，Spine角色的设备上线模板才可配置接口聚合模式 · The IS-IS username and password are required when the underlay protocol is IS-IS：Underlay路由协议为ISIS时需指定ISIS用户名和对称密钥 · The ISIS username and password can be configured only when the underlay protocol is IS-IS：仅当Underlay路由协议为ISIS时才可指定ISIS用户名和对称密钥 · The leaf/spine AS number is required when the underlay protocol is EBGP：Underlay路由协议为EBGP时，Leaf角色的设备上线模板必须指定Leaf BGP AS号和Spine BGP AS号 · The Loopback1 IP range is required when the underlay protocol is EBGP, and the role name is spine：Underlay路由协议为EBGP时，Spine角色的设备上线模板必须指定Underlay管理地址池的IP地址范围 · The Loopback1 IP range can be configured only when the underlay protocol is EBGP, and the role name is spine：仅当Underlay路由协议为EBGP时，Spine角色的设备上线模板才可指定Underlay管理地址池的IP地址范围 · The deployment template file already exists：指定的设备上线模板文件已存在 · The EVPN control feature can be configured only when EVPN is disabled：当EVPN功能关闭时，可以配置设备上线模板中的EVPN控制功能 · Invalid description：设备描述格式不正确 · Invalid IS-IS host name or neighbor authentication password：无效的ISIS主机名称或邻居关系验证密码 · Invalid BGP MD5 password：指定BGP的MD5认证密码无效 · Invalid ECMP settings：无效的ECMP配置 · In the deployment template, the BGP AS number, the BGP AS number for a spine device, and the BGP AS number for a leaf device must be different when the underlay protocol is EBGP：Underlay路由协议为EBGP时，设备上线模板中BGP AS号、Spine配置BGP AS号和Leaf配置的BGP AS号均不能相同 · the leaf bgp as num or spine bgp as num can configure only when the protocol is EBGP：仅当Underlay路由协议为EBGP时，Leaf角色的设备上线模板才可配置Leaf BGP AS号和Spine BGP AS号 · The template file name must end with character string .template：设备上线模板文件名称必须以.template结尾 · Invalid BGP AS number：无效的BGP AS号 · The BGP AS number cannot be modified because the fabric has network elements：指定Fabric下存在网元设备，设备上线模板中的BGP AS无法修改 · The NTP server address is required when the underlay protocol is OSPF or EBGP：当Underlay路由协议为OSPF或EBGP时，必须指定NTP服务器地址 · The NTP server address cannot be configured when the underlay protocol is IS-IS and EVPN is disabled：Underlay路由协议为ISIS且EVPN关闭时，不能配置NTP服务器地址 · The template does not exist：指定UUID的设备上线模板不存在 · The master or spine MAC address is required：未指定Master或Spine MAC地址 · The template name is required：未指定设备上线模板名称 · The software version or patch does not exist：指定的软件版本或软件补丁不存在 · The role name is required：未指定角色名称 · The template file path is required：未指定上传设备上线模板文件的路径 · The request json include read only field：请求json串包含只读字段 · ECMP is not supported when the underlay protocol is OSPF：Underlay路由协议为OSPF时不支持配置ECMP功能 · ECMP must be configured when the underlay protocol is IS-IS or EBGP：Underlay路由协议为ISIS或EBGP时必须配置ECMP功能 · The BGP route reflector MAC can be configured only when EVPN is enabled：仅在EVPN开启时才可配置BGP路由反射器的MAC地址 · Invalid BGP route reflector MAC：BGP路由反射器的MAC地址无效 · The fabric ID of the deployment template and the fabric ID of the used control protocol template must be the same：设备上线模板的Fabric ID和引用的设备控制协议模板的Fabric ID必须一致 · Invalid NTP server address：无效的NTP服务器IP地址 · Invalid master spine MAC address：无效的Master Spine MAC地址 · Invalid border MAC：无效的Border MAC地址 · The border MAC is required when EVPN is enabled：EVPN开启时必须配置Border MAC地址 · Invalid parameter：无效的参数 · Invalid command line：无效的命令行 · The border irf stacking can not be configured when the underlayprotocol is OSPF or BGP and evpn is disabled：仅Underlay路由协议是OSPF或BGP，且关闭EVPN时，不需要配置border堆叠 · The spine BGP AS number cannot be the same as the leaf BGP AS number：Spine角色和Leaf角色设备的BGP AS号不能相同 · The leaf BGP AS number and spine BGP AS number can be configured only when the protocol is BGP：仅当协议为BGP时，Spine角色和Leaf角色的设备才可配置AS号 · The Loopback1 IP range can be configured only when the underlay protocol is EBGP, and the role name is spine：仅当Underlay路由协议为EBGP时，Spine角色的设备上线模板才可指定Underlay管理地址池的IP地址范围。 · The BGP AS number cannot be edited when the fabric has NEs：Fabric下存在网元设备时，不允许修改BGP的AS号 · The NTP server address is required when the underlay protocol is OSPF or EBGP：当Underlay路由协议为OSPF或EBGP时，必须指定NTP服务器地址。 · The NTP server address cannot be configured when the underlay protocol is IS-IS and EVPN is disabled：Underlay路由协议为ISIS且EVPN关闭时，不能配置NTP服务器地址。 · The configure template doesn't exist：指定模板不存在 · The import configure template can not modify：导入设备模板不支持修改 · The CIDR is required：没有携带CIDR · Invalid CIDR：无效的CIDR · The underlay IP range overlaps with loopback1 IP range：Underlay IP地址范围与Loopback1 IP地址池范围重叠 · Cannot modify the Loopback1 IP range or underlay IP range of the template because the template has been bound to devices：该模板已绑定设备，Loopback1 IP范围和Underlay IP范围不允许修改 · The underlay IP range cannot contain existing VTEP IPs：Underlay IP范围不允许包含已存在的VTEP IP · The loopback1 IP range cannot contain existing VTEP IPs：Loopback1 IP范围不允许包含已存在的VTEP IP · The underlay IP range overlaps with an existing IP range：Underlay IP范围与当前已有IP范围重叠 · The loopback1 IP range overlaps with an existing IP range：Loopback1 IP范围与当前已有IP范围重叠 · An aggregation device does not support border IRF stacking：设备角色为aggregation时不支持Border IRF堆叠 · You cannot configure EVPN for an aggregation device：设备角色为aggregation时不支持配置EVPN · BGP RR MAC is not configurable because an aggregation device cannot act as a BGP RR：设备角色为aggregation时不支持配置BGP RR MAC · You cannot set a BGP MD5 password for an aggregation device：设备角色为aggregation时不支持配置BGP MD5密码 · Border MAC is not configurable because you cannot configure an aggregation device as a border device：设备角色为aggregation时不支持配置Border MAC · The RR MAC cannot be modified because the corresponding device is active：当前RR MAC地址对应的设备处于激活状态，MAC地址不允许修改 · You have no privilege to perform this operation：用户无权限执行此操作 · Please specify a NETCONF username and password for the default protocol template：default_protocol_template模板的NETCONF用户名密码不能为空 · An access device does not support border IRF stacking：设备角色为Access时不支持Border IRF堆叠 · An access device does not support IRF stacking：设备角色为Access时不支持IRF堆叠 · Please do not configure ECMP settings for an access device：设备角色为Access时不需要配置ECMP功能 · Please do not configure IS-IS settings for an access device：设备角色为Access时不需要指定ISIS相关配置 · Please do not configure OSPF settings for an access device：设备角色为Access时不需要指定OSPF相关配置 · Please do not configure BGP settings for an access device：设备角色为Access时不需要指定BGP相关配置 · An access device does not support EVPN settings：设备角色为Access时不支持配置EVPN · An access device does not support a border MAC：设备角色为Access时不支持配置Border MAC · The critical VLAN ID must be an integer in the range of 2 to 4094：取值范围为2～4094的整数 · The reserved VXLAN ID must be an integer in the range of 1 to 16777215：取值范围为1～16777215的整数 · Invalid keepalive link type：Keepalive链路取值无效 · Please specify a keepalive link type：Keepalive链路取值不能为空 · Make sure the reserved VXLAN is not in any existing VXLAN pool：设备上线模板的保留VXLAN不允许和已存在的VXLAN池重叠 · Invalid M-LAG group ID range：无效的M-LAG组编号范围 · Invalid interface aggregation mode：无效的接口聚合模式 · Please specify the M-LAG group ID range：必须指定M-LAG组编号范围 · Invalid management VPN instance name：无效的管理网VPN实例名称 · The management VPN instance name conflicts with the name of the VPN instance for the M-LAG keepalive link：管理网VPN实例名称与跨设备聚合Keepalive链路的VPN实例名称冲突 · When M-LAG is enabled, you must select SNMPv2c and specify a read community name in the control protocol template：当使能跨设备聚合时，设备控制协议模板中SNMP协议版本必选，且版本为SNMP_v2c时，读团体名不能为空 · Only leaf devices support automatic configuration of downlink interfaces：仅Leaf设备支持配置使能下行口配置自动下发 · If fabric service network type is vlan, automatic configuration of downlink interfaces is not supported：VLAN类型的Fabric不支持配置使能下行口配置自动下发 · The reserved LAG interface number range must de comma-separated list of integers (1 to 16384) or integer ranges (x-y, x can’t be greater than y). Up to 255 characters. Example: 200,201-205：聚合接口预留编号范围取值范围为1～16384的整数或区间，例如：200或201-205；当取值为区间时，起始值不能大于结束值。如需输入多个整数或区间，中间需用","隔开且输入长度不能超过255个字符 · Invalid network mode. Please specify the network mode as MLAG, IRF, or STAND_ALONE：无效的组网模式，组网模式不可为空，取值为MLAG、IRF或STAND_ALONE · The data restoration delay must be an integer in the range of 1 to 3600：延迟恢复时间取值范围为1~3600的整数 · Invalid bgp as number：无效的BGP AS号 · Invalid spine bgp as number：无效的Spine BGP AS号 · Invalid aggregation bgp as number：无效的Aggregation BGP AS号 · Invalid leaf bgp as number：无效的Leaf BGP AS号 · The old and new bgp as numbers are inconsistent：新旧BGP AS号字段不一致 · The old and new spine bgp as numbers are inconsistent：新旧Spine BGP AS号字段不一致 · The old and new aggregation bgp as numbers are inconsistent：新旧Aggregation BGP AS号字段不一致 · The old and new leaf bgp as numbers are inconsistent：新旧Leaf BGP AS号字段不一致 |
|
关键字 |
DELETE_CONFIGURE_TEMPLATE_OP |
|
日志内容 |
Deleted device deployment template $1. |
|
参数解释 |
$1：设备上线模板的ID |
|
举例 |
Deleted device deployment template 54dfc6cc-5110-4bf8-b23c-b5a84692bf43. |
|
日志说明 |
用户进行了删除设备上线模板的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · The device deployment template doesn't exist：指定的设备上线模板不存在 · The asset list doesn't exist：指定的资产清单不存在 · Failed to delete the template. The address pool in the fabric of the template is not released：模板删除失败，同一Fabric下的地址池未释放 · You have no privilege to perform this operation：用户无权限执行此操作 · The fabric contains automatically deployed devices：指定Fabric下存在已经自动化上线完成的设备 |
|
关键字 |
CREATE_CONTROL_PROTOCOL_TEMPLATE_OP |
|
日志内容 |
Created control protocol template: $1 |
|
参数解释 |
$1：设备控制协议模板的配置信息 |
|
举例 |
Created control protocol tempate: ID: [d23575f4-aa11-4683-855a-68d9edb95702] Name:[sdq] Fabric ID:[457fce6f-a17c-4f06-ad29-ef08d2f7777c] NETCONF settings:[ Username: admin Password: ****** ] SNMP settings:[ Read community: ****** Write community: ****** ] FTP settings:[ Username: sdn Password: ****** Timeout: 10 ] |
|
日志说明 |
用户进行了创建设备控制协议模板的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · The service is disabled：服务未启动 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · The control protocol template name already exists：指定名称的设备控制协议模板已存在 · The control protocol template name is required：未指定设备控制协议模板名称 · The NETCONF configuration is required：未指定设备控制协议模板的NETCONF配置 · The SNMP configuration is required：未指定设备控制协议模板的SNMP配置 · The NETCONF username cannot exceed 55 characters, and cannot be all-spaces：指定的NETCONF用户名不能超过55个字符，且不允许全部输入空格 · The NETCONF password cannot exceed 63 characters. Chinese characters are not supported, and cannot be all-spaces：指定的NETCONF密码最长63个字符，不支持中文，且不允许全部输入空格 · The SNMP read community is required：未指定SNMP的读团体名 |
|
|
· The control protocol template with the UUID already exists：指定UUID的设备控制协议模板已存在 · Invalid control protocol template name：无效的设备控制协议模板名称 · The control protocol template with the UUID already exists.：指定UUID的设备控制协议模板已存在 · The fabric ID is required：未指定设备控制协议模板所属Fabric的ID · You have no privilege to perform this operation：用户无权限执行此操作 · The NETCONF password cannot contain a username or the reverse letters of a username：NETCONF密码不允许包含用户名或用户名的倒序 · The SNMP read community name can contain up to 32 characters, Chinese characters, question marks (?), quotation marks ("), and spaces are not allowed：指定的SNMP读团体名最长32个字符，不支持中文，不能包含“?”、引号和空格 · The SNMP write community name can contain up to 32 characters, Chinese characters, question marks (?), quotation marks ("), and spaces are not allowed：指定的SNMP写团体名最长32个字符，不支持中文，不能包含“?”、引号和空格 · The SNMPv3 username must be a case-sensitive string of up to 32 characters. Chinese characters, question marks (?), quotation marks ("), and spaces are not allowed：SNMPv3用户名最长32个字符，区分大小写，不支持中文、问号、引号和空格 · Up to 64 characters,the authentication password must contain a minimum of 10 characters from at least two of the following categories: digits, uppercase letters, lowercase letters, and special characters.The password cannot contain a username or the reverse letters of a username.Chinese characters, question marks (?), quotation marks (\"), and spaces are not allowed：认证密码取值为8~64个字符，至少包含数字、大写字母、小写字母和特殊字符中的两种类型，不支持中文，不能包含“?”、引号和空格，不允许包含用户名和用户名的倒序 · Up to 64 characters,the encryption password must contain a minimum of 10 characters from at least two of the following categories: digits, uppercase letters, lowercase letters, and special characters.The password cannot contain a username or the reverse letters of a username. Chinese characters, question marks (?), quotation marks (\"), and spaces are not allowed：加密密码取值为8~64个字符，至少包含数字、大写字母、小写字母和特殊字符中的两种类型，不支持中文，不能包含“?”、引号和空格，不允许包含用户名和用户名的倒序 |
|
关键字 |
UPDATE_CONTROL_PROTOCOL_TEMPLATE_OP |
|
日志内容 |
Updated control protocol tempate: $1 |
|
参数解释 |
$1：设备控制协议模板的配置信息 |
|
举例 |
Updated control protocol tempate: ID: [d23575f4-aa11-4683-855a-68d9edb95702] Name:[sdq] Fabric ID:[457fce6f-a17c-4f06-ad29-ef08d2f7777c] NETCONF settings:[ Username: admin Password: ****** ] SNMP settings:[ Read community: ****** Write community: ****** ] FTP settings:[ Username: sdn Password: ****** Timeout: 1 ] |
|
日志说明 |
用户进行了修改设备控制协议模板的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · The service is disabled：服务未启动 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · The NETCONF username cannot exceed 55 characters, and cannot be all-spaces：指定的NETCONF用户名不能超过55个字符，且不允许全部输入空格 · The NETCONF password cannot exceed 63 characters. Chinese characters are not supported, and cannot be all-spaces：指定的NETCONF密码最长63个字符，不支持中文，且不允许全部输入空格 · The SNMP read community is required：未指定SNMP的读团体名 |
|
|
· The control protocol template name cannot be modified：指定的设备控制协议模板名称不允许修改 · The fabric ID cannot be modified：Fabric ID不允许修改 · The control protocol template name cannot be modified.：指定的设备控制协议模板名称不允许修改 · The control protocol template doesn't exist：指定的设备控制协议模板不存在 · You have no privilege to perform this operation：用户无权限执行此操作 · The NETCONF password cannot contain a username or the reverse letters of a username：NETCONF密码不允许包含用户名或用户名的倒序 · The SNMP read community name can contain up to 32 characters, Chinese characters, question marks (?), quotation marks ("), and spaces are not allowed：指定的SNMP读团体名最长32个字符，不支持中文，不能包含“?”、引号和空格 · The SNMP write community name can contain up to 32 characters, Chinese characters, question marks (?), quotation marks ("), and spaces are not allowed：指定的SNMP写团体名最长32个字符，不支持中文，不能包含“?”、引号和空格 · The SNMPv3 username must be a case-sensitive string of up to 32 characters. Chinese characters, question marks (?), quotation marks ("), and spaces are not allowed：SNMPv3用户名最长32个字符，区分大小写，不支持中文、问号、引号和空格 · Up to 64 characters,the authentication password must contain a minimum of 10 characters from at least two of the following categories: digits, uppercase letters, lowercase letters, and special characters.The password cannot contain a username or the reverse letters of a username.Chinese characters, question marks (?), quotation marks (\"), and spaces are not allowed：认证密码取值为8~64个字符，至少包含数字、大写字母、小写字母和特殊字符中的两种类型，不支持中文，不能包含“?”、引号和空格，不允许包含用户名和用户名的倒序 · Up to 64 characters,the encryption password must contain a minimum of 10 characters from at least two of the following categories: digits, uppercase letters, lowercase letters, and special characters.The password cannot contain a username or the reverse letters of a username. Chinese characters, question marks (?), quotation marks (\"), and spaces are not allowed：加密密码取值为8~64个字符，至少包含数字、大写字母、小写字母和特殊字符中的两种类型，不支持中文，不能包含“?”、引号和空格，不允许包含用户名和用户名的倒序 |
|
关键字 |
DELETE_CONTROL_PROTOCOL_TEMPLATE_OP |
|
日志内容 |
Deleted control protocol tempate $1. |
|
参数解释 |
$1：设备控制协议模板的ID |
|
举例 |
Deleted control protocol template d23575f4-aa11-4683-855a-68d9edb95702. |
|
日志说明 |
用户进行了删除设备控制协议模板的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · The service is disabled：服务未启动 · The default control protocol template cannot be deleted：默认的设备控制协议模板不允许删除 · The control protocol template is in use：指定的设备控制协议模板已被使用 · The control protocol template doesn't exist：指定的设备控制协议模板不存在 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_DEPLOY_RESOURCEPOOL_OP |
|
日志内容 |
Created deployment resource pool: $1. |
|
参数解释 |
$1：管理部署资源池的配置信息 |
|
举例 |
Created deployment resource pool[ Type: [out-of-band] Fabric ID: [d51aa540-40ec-4d68-9abd-623f884cc227] DHCP server settings:[ ID: [902dcff2-fc8a-48fb-91bb-9a99943a4e69] ] VTEP IP pool list: [ VTEP IP pool settings :[ ID: [a943dff1-61b5-4f35-b0de-6ecb007af11b] ] ] Loopback1 pool list: [ ] Management IP pool list :[ Management IP pool settings :[ ID: [73faf202-9225-4e23-b235-38d3ca4bf7cc] ] ] Temp management IP pool list :[ Temp management IP pool settings :[ ID: [e6f7f40b-4b77-4793-bd9b-b59eab103bc8] ] ] Remote management IP pool list :[ Remote management pool settings :[ ID: [c8f024b1-9c07-4f71-ab54-cca7d49b0745] ] ] Remote temp management IP pool list :[ Remote temp management pool settings :[ ID: [65c2e8fc-e830-4b09-9602-b4b94a1060fc] ] ] Remote VTEP IP pool list :[ Remote VTEP IP pool settings :[ ID: [65c2e8fc-e830-4b09-9602-b4b94a1060xc] ] ] |
|
日志说明 |
用户进行了创建管理部署资源池的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · The management mode is required：未指定管理类型 · Invalid management mode：无效的管理类型 · The DHCP server is required：未指定DHCP服务器 · The DHCP server doesn't exist：指定的DHCP服务器不存在 · The management network is required：未指定管理IP地址池 · The management address pool doesn't exist：指定的管理IP地址池不存在 · The management address pool is used by another fabric：指定的管理IP地址池已被其它Fabric使用 · The VTEP IP address pool is required：未指定管理网VTEP地址池 · The VTEP IP address pool doesn't exist：指定的管理网VTEP地址池不存在 · The VTEP IP address pool has been used：指定的管理网VTEP地址池已经被使用 · The deployment resource pool already exists：指定UUID的管理部署资源池已存在 · Invalid management network type：无效的管理网络类型 · Invalid VTEP IP type：无效的VTEP IP类型 · The fabric ID is required：所属Fabric ID不能为空 · The fabric does not exist：指定的Fabric不存在 · The fabric has been bound to another resource pool：指定的Fabric已与其他管理部署资源池绑定 · The server network list contains invalid networks：服务器网段列表中存在无效网段 · The VLAN1 address pool is invalid：VLAN1类型的地址池无效 · The VLAN4094 address pool is invalid：VLAN4094类型的地址池无效 · The specified VLAN pool does not exist：指定的VLAN池不存在 · The VLAN1 address pool requires a management network：必须指定VLAN1类型地址池的管理网络 · The specified VLAN pool has been bound to another fabric：指定的VLAN池已绑定其他Fabric · The VLAN4094 address pool requires a management network：必须指定VLAN4094类型地址池的管理网络 · The server network list contains invalid networks：服务器网段列表中存在无效网段 · Cannot configure a VTEP IP address pool when the fabric allocation mode is master spine allocation：Fabric分配方式为Master Spine分配时，不允许配置VTEP IP地址池 · Cannot configure an underlay address pool when the fabric allocation mode is master spine allocation：Fabric分配方式为Master Spine分配时，不允许配置Underlay互通地址池 · The default DHCP server does not exist：系统默认DHCP不存在 · An underlay address pool cannot contain loopback0 interface IP addresses of auto deployment device information：Underlay互通地址池范围不允许包含自动化部署的设备信息的Loopback0 IP地址 · The VTEP IP pool conflicts with the underlay IP range specified in the device deployment template：VTEP IP地址池与设备上线模板的Underlay IP范围冲突 · The VTEP IP pool conflicts with the loopback1 IP range specified in the device deployment template：VTEP IP地址池与设备上线模板的Loopback1 IP范围冲突 · The underlay IP pool conflicts with the underlay IP range specified in the device deployment template：Underlay互通地址池与设备上线模板的Underlay IP范围冲突 · The underlay IP pool conflicts with the loopback1 IP range specified in the device deployment template：Underlay互通地址池与设备上线模板的Loopback1 IP范围冲突 · The IP pool for auto deployment does not exist：指定的自动化上线地址池不存在 · The IP pool for auto deployment has been bound to another fabric：指定的自动化上线地址池已被其他Fabric绑定 · Invalid IP pool for auto deployment：无效的自动化上线地址池 · An IP pool for auto deployment cannot contain the management IP address of a device：自动化上线地址池不允许包含设备管理IP地址 · An IP pool for auto deployment cannot contain the IP address of a managed device：自动化上线地址池不允许包含已纳管设备的IP · You can specify only one address pool of each pool type：每种类型的地址池仅支持指定一个 · The management address pool and the IP pool for auto deployment must be different：管理IP地址池和自动化上线地址池不允许指定相同的IP地址池 · You have no privilege to perform this operation：用户无权限执行此操作 · You can configure a remote address pool only when the underlay protocol is OSPF：当Underlay物理协议为OSPF时，才支持配置远端地址池 · To configure a remote address pool, you must first configure a remote management IP pool：当配置远端地址池时，远端管理IP地址池不能为空 · To configure a remote address pool, you must first configure a remote IP pool for auto deployment：当配置远端地址池时，远端自动化上线地址池不能为空 · To configure a remote address pool, you must first configure a remote VTEP IP pool：当配置远端地址池时，远端VTEP IP地址池不能为空 · The remote management network address pool and the remote auto deployment address pool must have the same gateway address：远端管理IP地址池网关必须与远端自动化上线地址池网关相同 · The local and remote management network address pools cannot reside in the same network：远端管理IP地址池不可与本地管理IP地址池在同一网段 · The remote management network address pool and local auto deployment address pool cannot reside in the same network：远端管理IP地址池不可与本地自动化上线地址池在同一网段 · The remote auto deployment address pool and local management network address pool cannot reside in the same network：远端自动化上线地址池不可与本地管理IP地址池在同一网段 · The local and remote auto deployment address pools cannot reside in the same network：远端自动化上线地址池不可与本地自动化上线地址池网在同一网段 · The specified remote management IP pool has been bound to another fabric：指定的远端管理IP地址池已被其他Fabric绑定 · The specified remote IP pool for auto deployment has been bound to another fabric：指定的远端自动化上线地址池已被其他Fabric绑定 · The specified remote VTEP IP pool has been bound to another fabric：指定的远端VTEP IP地址池已被其他Fabric绑定 · Invalid remote management IP pool：无效的远端管理IP地址池 · Invalid remote IP pool for auto deployment：无效的远端自动化上线地址池 · Make sure the remote auto deployment IP pool contains only one address range：远端自动化上线地址池引用的物理管理网地址池必须有且仅有一个地址段 · Invalid remote VTEP IP pool：无效的远端VTEP IP地址池 · The remote IP pool for auto deployment cannot contain IP addresses in the device list：远端自动化上线地址池不允许包含设备清单IP地址 · The remote IP pool for auto deployment cannot contain IP addresses of incorporated devices：远端自动化上线地址池不允许包含已纳管设备的IP地址 · The specified remote management IP pool does not exist：远端自动化上线地址池不允许包含已纳管设备的IP地址 · he specified remote management IP pool does not exist：指定的远端管理地址池不存在 · The specified remote IP pool for auto deployment does not exist：指定的远端自动化上线地址池不存在 · The specified remote VTEP IP pool does not exist：指定的远端VTEP IP地址池不存在 · The local management IP pool and the remote management IP pool must be different：管理IP地址池和远端管理IP地址池不允许指定相同的IP地址池 · The local management IP pool and the remote IP pool for auto deployment must be different：管理IP地址池和远端自动化上线地址池不允许指定相同的IP地址池 · The local IP pool for auto deployment and the remote management IP pool must be different：自动化上线地址池和远端管理IP地址池不允许指定相同的IP地址池 · The local IP pool for auto deployment and the remote IP pool for auto deployment must be different：自动化上线地址池和远端自动化上线地址池不允许指定相同的IP地址池 · The remote management IP pool and the remote IP pool for auto deployment must be different：远端管理IP地址池和远端自动化上线地址池不允许指定相同的IP地址池 · The local VTEP IP pool and the remote VTEP IP pool must be different：VTEP IP地址池和远端VTEP IP地址池不允许指定相同的IP地址池 · The local management IP pool cannot contain any management IP addresses in the remote device list：本地管理IP地址池和远端设备清单的管理IP地址冲突 · The remote management IP pool cannot contain any management IP addresses in the local device list：远端管理IP地址池和本地设备清单的管理IP地址冲突 |
|
关键字 |
UPDATE_DEPLOY_RESOURCEPOOL_OP |
|
日志内容 |
Updated deployment resource pool: $1. |
|
参数解释 |
$1：管理部署资源池的配置信息 |
|
举例 |
Updated deployment resource pool[ ID: [b6ff4eb8-6a12-45f3-891e-3e77be157df8] DHCP server settings:[ ID: [ad5c2c16-9861-4d8d-9ad4-60e54d19abc4 ] ] ] |
|
日志说明 |
用户进行了修改管理部署资源池的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · The management mode cannot be modified：管理类型不允许修改 · The IP address of the DHCP server cannot be modified：DHCP服务器IP不允许修改 · The name of the DHCP server cannot be modified：DHCP服务器名称不允许修改 · The fabric ID cannot be modified：Fabric ID不允许修改 · Subnets of the management network cannot be modified.：管理IP地址池的子网不允许修改 · The gateway address of the management network cannot be modified：管理IP地址池的网关IP地址不允许修改 · Subnet addresses specified in the VTEP address pool cannot be modified.：VTEP地址池的子网不允许修改 · The VTEP IP address pool cannot be modified：VTEP地址池不允许修改 · The DHCP server doesn't exist：指定的DHCP服务器不存在 · The VTEP IP address pool doesn't exist：指定的管理网VTEP地址池不存在 · The management address pool is used by another fabric：指定的管理IP地址池已被其它Fabric使用 · The deployment resource pool doesn't exist.：指定的管理部署资源池不存在 · Invalid management network type：无效的管理网络类型 · The fabric ID is required：所属Fabric ID不能为空 · The server network list contains invalid networks：服务器网段列表中存在无效网段 · The VLAN1 address pool is invalid：VLAN1类型的地址池无效 · The VLAN4094 address pool is invalid：VLAN4094类型的地址池无效 · The specified VLAN pool does not exist：指定的VLAN池不存在 · The specified VLAN pool has been bound to another fabric：指定的VLAN池已绑定其他Fabric · The subnet bound to the VLAN pool cannot be modified：VLAN池指定的子网不允许修改 · The server network list contains invalid networks：服务器网段列表中存在无效网段 · Cannot modify the management address pool because IP addresses in the management address pool have been used：管理地址池中的IP地址已被使用，不允许修改 · Cannot delete or edit the IP pool for auto deployment. It is being used：指定的自动化上线地址池正在被使用，不允许删除或修改 · The IP pool for auto deployment does not exist：指定的自动化上线地址池不存在 · The IP pool for auto deployment has been bound to another fabric：指定的自动化上线地址池已被其他Fabric绑定 · Cannot edit the address ranges in an IP pool for auto deployment：自动化上线地址池的地址段不允许修改 · Cannot edit the gateway address in an IP pool for auto deployment：自动化上线地址池的网关地址不允许修改 · Invalid IP pool for auto deployment：无效的自动化上线地址池 · An IP pool for auto deployment cannot contain the management IP address of a device：自动化上线地址池不允许包含设备管理IP地址 · An IP pool for auto deployment cannot contain the IP address of a managed device：自动化上线地址池不允许包含已纳管设备的IP · You can specify only one address pool of each pool type：每种类型的地址池仅支持指定一个 · The management address pool and the IP pool for auto deployment must be different：管理IP地址池和自动化上线地址池不允许指定相同的IP地址池 · The IP pool for auto deployment cannot be edited：自动化上线地址池不允许修改 · You have no privilege to perform this operation：用户无权限执行此操作 · The local management IP pool and the remote management IP pool must be different：管理IP地址池和远端管理IP地址池不允许指定相同的IP地址池 · The local management IP pool and the remote IP pool for auto deployment must be different：管理IP地址池和远端自动化上线地址池不允许指定相同的IP地址池 · The local IP pool for auto deployment and the remote management IP pool must be different：自动化上线地址池和远端管理IP地址池不允许指定相同的IP地址池 · The local IP pool for auto deployment and the remote IP pool for auto deployment must be different：自动化上线地址池和远端自动化上线地址池不允许指定相同的IP地址池 · The remote management IP pool and the remote IP pool for auto deployment must be different：远端管理IP地址池和远端自动化上线地址池不允许指定相同的IP地址池 · The local VTEP IP pool and the remote VTEP IP pool must be different：VTEP IP地址池和远端VTEP IP地址池不允许指定相同的IP地址池 · The remote management IP pool cannot be edited：远端管理IP地址池不允许修改 · The remote VTEP IP pool cannot be edited：远端VTEP IP地址池不允许修改 · Please specify a remote IP pool for auto deployment：远端自动化上线地址池不能为空 · Please specify a remote management IP pool：远端管理IP地址池不能为空 · Please specify a remote VTEP IP pool：远端VTEP IP地址池不能为空 · You cannot edit the IP pool for auto deployment, because the fabric contains devices that are being deployed automatically：存在正在自动化上线的设备，不允许修改自动化上线地址池 · You cannot edit the remote IP pool for auto deployment, because the fabric contains devices that are being deployed automatically：存在正在自动化上线的设备，不允许修改远端自动化上线地址池 |
|
关键字 |
DELETE_DEPLOY_RESSOURCEPOOL_OP |
|
日志内容 |
Deleted deployment resource pool $1. |
|
参数解释 |
$1：deploy resource pool的ID |
|
举例 |
Deleted deployment resource pool cc06ca44-5b72-49c2-af36-5834970b8ab4. |
|
日志说明 |
用户进行了删除管理部署资源池的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · The deployment resource pool doesn't exist：指定的管理部署资源池不存在 · Cannot delete a VTEP IP address pool in use：VTEP IP地址池正在使用，不允许删除 · Cannot delete the management address pool because IP addresses in the management address pool have been used：管理地址池中的IP地址已被使用，不允许删除 · Cannot delete or edit the IP pool for auto deployment. It is being used：指定的自动化上线地址池正在被使用，不允许删除或修改 · You have no privilege to perform this operation：用户无权限执行此操作 · The fabric contains devices that are being deployed automatically：指定Fabric下的存在正在自动化上线的设备 |
|
关键字 |
CREATE_AUTO_DISCOVERY_OP |
|
日志内容 |
Created auto discovery task: $1 |
|
参数解释 |
$1：自动发现任务的配置信息 |
|
举例 |
Created auto discovery task: Username:[admin] Name:[null] Start IP:[98.0.19.92] End IP:[98.0.19.92] NETCONF username:[sdn] NETCONF password:[123456] Read community:[null] Write community:[null] |
|
日志说明 |
用户进行了创建自动发现任务的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · The number of IP addresses must be in range of 1 to 1000：指定IP地址范围内IP地址个数不能超过1000个 · The start IP address is required：未指定起始IP地址 · The end IP address is required：未指定结束IP地址 · NETCONF and SNMP cannot be both empty：SNMP和NETCONF配置不能同时为空 · The SNMP read and write communities must be both configured or both empty：SNMP的读团体名和写团体名必须同时指定或不指定 · The NETCONF username and password must be both configured or both empty：NETCONF用户名和密码必须同时指定或不指定 · The start IP address must be lower than the end IP address：自动发现任务中IP地址范围的起始IP地址不能大于结束IP地址 · Invalid IP address：无效的IP地址 · The SNMP read community name is required：读团体名不能为空 · The SNMP write community name is required：写团体名不能为空 · The NETCONF username is required：Netconf用户名不能为空 · The NETCONF password is required：Netconf密码不能为空 · The username is required：用户名不能为空 · Invalid username：无效的用户名 · The NETCONF username cannot exceed 55 characters: 指定的NETCONF用户名不能超过55个字符 · The NETCONF password cannot exceed 63 characters. Chinese characters are not supported：指定的NETCONF的密码格式不正确 · The SNMP read community name can contain up to 32 characters. Chinese characters are not supported: 指定的SNMP读团体名最长32个字符，不支持中文 · The SNMP write community name can contain up to 32 characters. Chinese characters are not supported: 指定的SNMP写团体名最长32个字符，不支持中文 · The specified user does not exist：指定名称的用户不存在 · The current user is not authorized to perform this operation：当前用户无权限执行此操作 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
STOP_AUTO_DISCOVERY_OP |
|
日志内容 |
Stopped auto discovery task: $1. |
|
参数解释 |
$1：自动发现任务的停止状态 |
|
举例 |
Stopped auto discovery task: true. |
|
日志说明 |
用户进行了停止自动发现任务的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · The auto-detection task has stopped：自动发现任务已停止 · The auto-detection task doesn't exist：指定用户名的自动发现任务不存在 · Invalid username：无效的用户名 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_AUTO_DISCOVERY_OP |
|
日志内容 |
Deleted auto discovery task $1. |
|
参数解释 |
$1：自动发现任务的用户名称 |
|
举例 |
Deleted auto discovery task admin. |
|
日志说明 |
用户进行了删除自动发现任务的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · The auto-detection task is not completed and cannot be deleted：自动发现任务未完成，无法删除 · The auto-detection task doesn't exist：指定用户名的自动发现任务不存在 · Invalid username：无效的用户名 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_GLOBAL_SETTING_OP |
|
日志内容 |
Updated global setting: $1 |
|
参数解释 |
$1：定时备份整网设备启动配置文件的配置信息 |
|
举例 |
Updated global setting: Auto backup: [false] TftpServerAddress: [98.0.31.100] Frequency: [1] Time: [12:00] Week: [1] Date: [0] MaxCfgNum: [1] |
|
日志说明 |
用户进行了修改定时备份整网设备启动配置文件（startup.cfg）功能开关的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_SECURITY_GLOBAL_CONFIG_OP |
|
日志内容 |
Updated security global config: $1 |
|
参数解释 |
$1：安全业务全局配置 |
|
举例 |
Updated security global config: FipToIfSubAddrEnable: true FipUseNatServerEnable: true FipIpSecVpnEnable: true IpLastHopHoldEnable: true Ipv6LastHopHoldEnable: false ForbiddenSecExternalNetworkEnable: false QosOptimizationEnable: false NatRateLimitingUseAvcEnable: false LbIdleTimeoutEnable: true LbUseSnatPoolFirstEnable: false SnatpoolUseLb2GwIpEnable: false |
|
日志说明 |
用户进行了修改安全业务全局配置开关的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · You have no privilege to perform this operation：用户无权限执行此操作 · Cannot disable NAT server mappings for floating IPs：浮动IP使用NAT Server配置开关开启后，不允许修改 · The floating IPs using NAT server mappings to support IPsec VPNs feature cannot be disabled once it is enabled：浮动IP使用NAT Server配置支持IPSec VPN开关开启后，不允许修改 · Cannot disable LB idle timeout：使能负载均衡空闲超时后，不允许关闭 · When the LB SNAT type is default SNAT pool address, make sure the address pool contains addresses that have the same IP version as CGSR-type load balancers with SNAT enabled：当LB用户源地址转换使用默认SNAT地址池模式时，该地址池里必须有与开启SNAT的服务网关类型LB服务协议一致的地址 |
|
关键字 |
CREATE_DHCP_SERVER_OP |
|
日志内容 |
Created DHCP server $1/$2. |
|
参数解释 |
$1：DHCP服务器的名称 $2：DHCP服务器的IP地址 |
|
举例 |
Created DHCP server Vsr-26.72/98.0.26.72. |
|
日志说明 |
用户进行了创建DHCP服务器的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · The DHCP server name is required：未指定DHCP服务器名称 · The DHCP server name cannot exceed 255 characters：DHCP服务器名称不能超过255个字符 · The DHCP server IP is required：未指定DHCP服务器IP地址 · Invalid IP address：无效的IP地址 · The DHCP server NETCONF username is required：未指定DHCP服务器的NETCONF用户名 · The DHCP server NETCONF name cannot exceed 55 characters：DHCP服务器的NETCONF用户名长度不能超过55个字符 · The DHCP server NETCONF password is required：未指定DHCP服务器的NETCONF密码 · The DHCP server NETCONF password cannot exceed 63 characters：DHCP服务器的NETCONF密码长度不能超过63个字符 · The DHCP server already exists：指定UUID的DHCP服务器已存在 · The DHCP server name is already used：指定名称的DHCP服务器已存在 · The DHCP server IP is already used：指定IP地址的DHCP服务器已存在 · The request is invalid：无效的请求 · Unknown error：未知错误 · The DHCP server type is invalid：无效的DHCP服务器类型 · The DHCP server status field is read only：DHCP服务器状态字段为只读字段 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_DHCP_SERVER_OP |
|
日志内容 |
Updated DHCP server $1/$2. |
|
参数解释 |
$1：DHCP服务器的名称 $2：DHCP服务器的IP地址 |
|
举例 |
Updated DHCP server Vsr-26.72/98.0.26.72. |
|
日志说明 |
用户进行了修改DHCP服务器的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · The request is invalid：无效的请求 · Unknown error：未知错误 · The specified resource doesn't exist：指定资源不存在 · The DHCP server status field is read only：DHCP服务器状态字段为只读字段 · The DHCP server IP field is read only：DHCP服务器IP字段为只读字段 · The DHCP server name field is read only：DHCP服务器名称字段为只读字段 · The DHCP server type field cannot be edited：DHCP服务器类型字段不允许修改 · The DHCP server NETCONF username is required：未指定DHCP服务器的NETCONF用户名 · The DHCP server NETCONF name cannot exceed 55 characters：DHCP服务器的NETCONF用户名长度不能超过55个字符 · The DHCP server NETCONF password is required：未指定DHCP服务器的NETCONF密码 · The DHCP server NETCONF password cannot exceed 63 characters：DHCP服务器的NETCONF密码长度不能超过63个字符 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_DHCP_SERVER_OP |
|
日志内容 |
Deleted DHCP server $1/$2. |
|
参数解释 |
$1：DHCP服务器的名称 $2：DHCP服务器的IP地址 |
|
举例 |
Deleted DHCP server Vsr-26.72/98.0.26.72. |
|
日志说明 |
用户进行了删除DHCP服务器的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Can't delete the DHCP server. The DHCP server has address pools：DHCP服务器下存在IP地址池，不允许删除 · Unknown error：未知错误 · The specified resource doesn't exist：指定资源不存在 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPLOAD_SOFTWARE_OP |
|
日志内容 |
Uploaded software package: $1 |
|
参数解释 |
$1：软件/补丁的配置信息 |
|
举例 |
Uploaded software package: Software ID: [6b5f0ea1-590f-421d-9675-c3bbe9a39c0b] Software FTP path: [ftp://sdn:[email protected]/6800.ipe] Software name: [6800.ipe] Software size: [135473152] Software version: [R2612] Software description: [s6800] Software type: [ipe] Software release date: [2018-08-17] Software import time: [2018-10-30 07:59:04] Device: [S6800] Device version: [Release 2612] Software platform version: [7.1.070 ] Software state: [ready] ] |
|
日志说明 |
用户进行了创建软件/补丁上传的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · The service is disabled：服务未启动 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · The software name already exists：指定名称的软件已存在 · The software already exists：指定软件的UUID已存在 · Invalid FTP path：无效的FTP路径 · Invalid release date：无效的软件发布日期 · Invalid type of software：无效的软件类型 · Invalid software name：无效的软件名称 · Length of file name should be less than 63：文件名称长度不能超过63个字符 · Unknown error code：未知错误 · The FTP path is required：未指定FTP路径 · The software name is required：软件名称未指定 · The software size field is read only：软件大小为只读字段 · The import_time attribute is read only：版本或者补丁上传时间为只读字段 · The available devices field is read only：可用设备列表为只读字段 · The version field is read only.：版本信息只读字段 · The software type is requested：未指定软件类型 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_SOFTWARE_OP |
|
日志内容 |
Updated software package: $1 |
|
参数解释 |
$1：软件/补丁的配置信息 |
|
举例 |
Updated software package: Software ID: [6b5f0ea1-590f-421d-9675-c3bbe9a39c0b] Software FTP path: [ftp://sdn:[email protected]/6800.ipe] Software name: [6800.ipe] Software size: [0] Software version: [null] Software description: [s6800] Software type: [ipe] Software release date: [2018-08-17] Software import time: [2018-10-30 07:59:04] Device: [null] Device version: [null] Software platform version: [null] Software state: [ftp failed] ] |
|
日志说明 |
用户进行了修改软件/补丁配置信息的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · The service is disabled：服务未启动 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · The applicable devices are read only and cannot be modified：适配设备列表为只读字段，无法修改 · The software does not exist：指定UUID的软件不存在 · The software type cannot be modified：软件类型不允许修改 · Invalid release date：无效的软件发布日期 · Unknown error code：未知错误 · The software size field is read only：软件大小为只读字段 · The available devices field is read only：可用设备列表为只读字段 · The import time field is read only：软件导入时间为只读字段 · The version field is read only：版本为只读字段 · The software is uploading, can not operate it：软件正在上传中，禁止操作 · The software is upgrading, can not operate it：软件正在升级使用中，禁止操作 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_SOFTWARE_OP |
|
日志内容 |
Deleted software package $1. |
|
参数解释 |
$1：软件/补丁的ID |
|
举例 |
Deleted software package 52db1e10-e09c-45c5-b7df-08bed8fbc474. |
|
日志说明 |
用户进行了删除软件/补丁上传与升级的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service is disabled：服务未启动 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · Cannot delete the software. The software is being used：指定的软件正在被使用，无法删除 · The software does not exist：指定UUID的软件不存在 · Failed to delete the software：删除软件失败 · Unknown error code：未知错误 · The software is uploading, can not operate it：软件正在上传中，禁止操作 · The software is upgrading, can not operate it：软件正在升级使用中，禁止操作 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CONFIGURE_SOFTWARE_UPGRADE |
|
日志内容 |
Upgraded software package: $1 |
|
参数解释 |
$1：软件/补丁升级的配置信息 |
|
举例 |
Upgraded software package: Software ID: [cc4af032-5e4b-430d-9be1-5228717b48f7] Device information: [ Device ID: [2b48fee5-c261-4721-a740-53a073264e64] Software path: [flash:/] Space check flag: [true] Restart flag: [true]] |
|
日志说明 |
用户进行了升级软件/补丁的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · The service is disabled：服务未启动 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · Invalid boot path：无效的软件加载路径 · The software does not exist：软件不存在 · The device is required：未指定设备 · The device is not active：待升级设备处于未激活状态，无法升级 · Unknown error code：未知错误 · The software ID is required:未指定软件的ID · The device ID is required：未指定设备ID · The software storage path is required：未指定软件存储路径 · Invalid boot path：无效的软件加载路径 · The device name is read only：设备名称只读 · The software is uploading, can not operate it：软件正在上传中，禁止操作 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
REPLACE_PHYNE_OP |
|
日志内容 |
Replaced physical NE: $1 |
|
参数解释 |
$1：设备的配置信息 |
|
举例 |
Replaced physical NE: NE ID: [5986bede-08f2-4d4e-bd01-9e7907272e5d] NE name: [l2vtep] NE type: [L2GW] VTEP IP: [[68.0.0.15]] VDS ID: [ffffffff-0000-0000-0000-000000000001] NETCONF username: [sdn] NETCONF password: [123456] Provider type: [PHY_DEVICE] NE capability: [L2GW] VRF: [mgmt] Reserved tunnel ID: [256] Supporting auto configuration: [true] Supporting VTEP: [true] Service migration: [false] PreCfgVxlanService: [false] OpenflowPermitPort: [false] PreStatVxlanService: [false] OpenFlow controller port: [null] OpenFlow SSL policy name: [null] Clear configuration: [false] Data synchronization: [DEFAULT] externalInfoList: [
] Being deleted: [false] Role name: [leaf] Serial number: [210235A2C4H187000881] Fabric ID: [b07f126a-54bb-480a-ba4c-a98fe1153d14] Gateway: [false] Read community: [public] Write community: [private] Under deployment: [false] ] NE state:[INACTIVE] Inactive reason:[DEVICE_INACTIVE_REASON_DEVICE_IS_NO_FINISH_AUTOMAIN_ON_LINE] |
|
日志说明 |
用户进行了替换设备的操作，将故障设备的配置信息重新迁移到其他正常设备上以替换故障设备 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · Invalid JSON format：无效的JSON格式 · The service is disabled：服务未启动 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · The replacement device is no activate：指定的替换设备处于未激活状态 · The device is not bound to the fabric：网元设备未绑定Fabric · The replacement device is not bound to the fabric：替换设备未绑定Fabric · The faulty device and the replacement device must belong to the same fabric：故障设备和替换设备所绑定的Fabric必须相同 · The device and replace device role are not same：故障设备和替换设备的角色必须相同 · The backup start configuration file for the faulty device does not exist：故障设备的备份启动配置文件不存在 · No deployment template is configured for the fabric to which the replacement device is bound.：替换设备绑定的Fabric未配置设备上线模板 · FTP is not configured for the control protocol template associated with the replacement device：替换设备引用的设备控制协议模板未配置FTP · A faulty underlay device cannot be replaced：Underlay类型的故障设备不允许替换 · The replacement device type cannot be Underlay：替换设备类型不允许为Underlay · The device with the specified serial number has been incorporated and cannot be used as a replacement device：序列号无效，该设备已被纳管，无法替换 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_TENANT_BIND_GATEWAY_OP |
|
日志内容 |
Updated tenant-gateway binding relationship: $1 |
|
参数解释 |
$1：租户与网关的绑定关系配置信息 |
|
举例 |
Updated tenant-gateway binding relationship: ID:[ade5d887-818d-4555-a336-7f72a547fb1a] Tenant:[ffffffff-0000-0000-0000-000000000001] Default gateway:[fc8e40f9-d609-4ac6-ac0d-4f61875b86aa] Gateway list:[fc8e40f9-d609-4ac6-ac0d-4f61875b86aa] |
|
日志说明 |
用户进行了修改租户与网关绑定关系的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · Invalid JSON format：无效的JSON格式 · The service is disabled：服务未启动 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · The tenant-gateway binding relationship does not exist：指定的租户与网关绑定关系不存在 · The tenant-gateway binding relationship already exists：指定的租户与网关绑定关系已存在 · The tenant has been used by another tenant-gateway binding relationship：已绑定网关的租户不允许修改 · The gateway list cannot contain duplicated gateways：网关列表中不允许存在重复的网关 · Cannot specify nonexistent gateways：指定的网关不存在 · The default gateway has been bound to a resource and cannot be modified：默认网关已绑定资源，不允许修改 · Invalid parameter：无效的参数 · Only gateways in the gateway list can be specified as the default gateway：指定的默认网关不属于租户绑定的网关 · You have no privilege to perform this operation：用户无权限执行此操作 · The gateway has been used by a vRouter link that uses the normal firewall mode. Please first delete that vRouter link：该网关已被防火墙模式为NORMAL类型的虚拟路由器连接使用，请先删除虚拟路由器连接 · You cannot delete the binding between the tenant and the egress gateway. The vRouter of the tenant has been bound to the external network attached to the egress gateway：该租户下的虚拟路由器已经绑定了指定出口网关的外部网络，不允许删除租户与出口网关的绑定关系 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · The gateway is already used by a centralized external transit vRouter link. Please delete that vRouter link first：该网关资源已被EXTERNALTRANSIT类型集中式虚拟路由器连接使用，请先删除集中式虚拟路由器连接 · The tenant has an external transit vRouter that is already bound to a border gateway. Please unbind the border gateway from that vRouter first：租户下存在EXTERNALTRANSIT类型的虚拟路由器已绑定出口网关，请先解绑该虚拟路由器的出口网 · You cannot unbind the border gateway from the tenant, because the border gateway is bound to an interconnect interface that has a BGP neighbor binding：租户不允许解绑互联接口被BGP邻居绑定的出口网关 · If a border gateway is in tenant-exclusive mode, you can bind it to only one tenant：租户独占的出口网关只允许绑定一个租户 · Tenant-exclusive border gateways cannot be configured as the tenant's default gateway：租户独占的出口网关不允许配置为租户的默认网关 · You cannot unbind a border gateway from a tenant if you have configured resource priorities or role for that gateway when you bind it to a vRouter：出口网关在虚拟路由器上配置了优先级或配置角色时，租户不能解绑该出口网关 |
|
关键字 |
DELETE_TENANT_BIND_GATEWAY_OP |
|
日志内容 |
Deleted tenant-gateway binding relationship: $1 |
|
参数解释 |
$1：租户与网关绑定关系的UUID |
|
举例 |
Deleted tenant-gateway binding relationship: 218b5f2f-e435-4365-a1ab-0eaa03b7fa19 |
|
日志说明 |
用户进行了删除租户与网关绑定关系的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · Invalid JSON format：无效的JSON格式 · The service is disabled：服务未启动 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · The tenant-gateway binding relationship does not exist： 指定的租户与网关绑定关系不存在 · The default gateway has been bound to a resource and cannot be modified：默认网关已绑定资源，不允许修改 · Invalid parameter：无效的参数 · You have no privilege to perform this operation：用户无权限执行此操作 · The gateway has been used by an MSDP peer：指定的出口网关已经被MSDP使用 · The gateway has been used by a vRouter link that uses the normal firewall mode. Please first delete that vRouter link：该网关已被防火墙模式为NORMAL类型的虚拟路由器连接使用，请先删除虚拟路由器连接 · You cannot delete the binding between the tenant and the egress gateway. The vRouter of the tenant has been bound to the external network attached to the egress gateway：该租户下的虚拟路由器已经绑定了指定出口网关的外部网络，不允许删除租户与出口网关的绑定关系 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · You cannot unbind the border gateway from the tenant, because the border gateway is bound to an interconnect interface that has a BGP neighbor binding：租户不允许解绑互联接口被BGP邻居绑定的出口网关 · You cannot unbind a border gateway from a tenant if you have configured resource priorities or role for that gateway when you bind it to a vRouter：出口网关在虚拟路由器上配置了优先级或配置角色时，租户不能解绑该出口网关 |
|
关键字 |
CREATE_GATEWAY_OP |
|
日志内容 |
Created gateway : $1 |
|
参数解释 |
$1：出口网关配置信息 |
|
举例 |
Created gateway : ID: [741f1414-d71e-4775-acf9-d68bbb55e803] Name: [gatewayName]] Description: [create gateway] Fw_Export_Default_Route_Advertise_Always:[false] Type: [GROUP] Gateway member list: [ 5da35b42-1e37-4c3f-928b-0afc77fcfd34 ffd8176c-820a-4dc5-94a9-5f4c4fbff0c5 ] |
|
日志说明 |
用户进行了创建出口网关的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service is disabled：服务未启动 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · Unknown internal server error：未知的内部服务器错误 · Invalid description：无效的描述 · Invalid name：无效的名称 · Invalid parameter：无效的参数 · The gateway already exists：指定的出口网关已存在 · Invalid gateway type：无效的出口网关类型 · The gateway name already exists：出口网关名称已存在 · You can specify a maximum of two gateway members when the gateway type is GROUP：当出口网关类型为GROUP时最多可指定两个网关成员 · You can specify only one gateway member when the gateway type is VIRTUAL：当出口网关类型为VIRTUAL时仅能指定一个网关成员 · Cannot specify nonexistent gateway members：出口网关成员不存在 · The gateway type and gateway member type do not match：出口网关类型和网关成员类型不匹配 · Duplicated gateway members exist：指定的出口网关成员重复 · The gateway members of a gateway must belong to different device groups：指定的出口网关成员不允许属于相同设备组 · The gateway members must belong to the same type of device groups：指定的出口网关成员所属的设备组类型必须相同 · The device groups to which the gateway members belong must have the same fw_for_external parameter value：指定的出口网关成员所属的两个设备组是否允许外网流量做防火墙业务开关必须相同 · The device groups to which the gateway members belong must have the same fw_only_for_external parameter value：指定的出口网关成员所属的两个设备组是否允许非外网流量做防火墙业务开关必须相同 · The device groups to which the gateway members belong must have the same fw_for_internal parameter value：指定的出口网关成员所属的两个设备组是否允许内网流量做防火墙业务开关必须相同 · The device groups to which the gateway members belong must have the same connection type：指定的出口网关成员所属的两个设备组连接方式必须相同 · You can specify only one gateway member when the fabric of the device group is not enabled with EVPN：设备组对应Fabric的EVPN开关为关时，出口网关只能存在一个网关成员 · The fabrics of the device groups to which the gateway members belong must have the same EVPN state：指定的出口网关成员所属两个设备组对应Fabric的EVPN开关必须一致 · The gateway member has been bound to another gateway：指定的网关成员已被其他出口网关绑定 · The gateway member must have different priorities：出口网关成员的优先级不允许相同 · You have no privilege to perform this operation：用户无权限执行此操作 · You cannot specify a VRF name when the method to deploy basic external connectivity settings is set to manual for the border gateway and the firewall deployment mode is disabled for the gateway member's device group：出口网关的外网转发基础配置为手动预配置且成员设备组的防火墙接入模式为关闭时，VRF名称必须为空 · You can specify only one gateway member when the method to deploy basic external connectivity settings is set to manual for the border gateway and the firewall deployment mode is disabled for the gateway member's device group：出口网关的外网转发基础配置为手动预配置且成员设备组的防火墙接入模式为关闭时，只允许配置一个出口网关成员 · The network cloud scenario does not support configuring tenant-exclusive border gateways：网络云场景不支持配置租户独占的出口网关 · When you add a gateway member for a tenant-exclusive border gateway, make sure the device group specified for that gateway member has border gateway and DCI capabilities：租户独占的出口网关的出口网关成员的设备组应具有出口网关和DC间互联功能 · Only tenant-exclusive border gateways support interconnect interface bindings：仅支持租户独占的出口网关绑定互联接口 · You can bind up to 48 interconnect interfaces to a tenant-exclusive border gateway：租户独占的出口网关绑定互联接口的数量最多为48个 · When you configure the tenant-exclusive mode parameter of a border gateway, only OPEN and CLOSE are supported：出口网关的租户独占配置项仅支持开启或关闭 · The interconnect interface specified for the border gateway does not exist：出口网关绑定的互联接口不存在 · When you bind an interconnect interface to a tenant-exclusive border gateway, make sure the border gateway already has gateway members：租户独占的出口网关绑定互联接口时，必须绑定出口网关成员 · The interconnect interface is already bound to another tenant-exclusive border gateway：互联接口已被其他租户独占的出口网关绑定 · When you bind an interconnect interface to a tenant-exclusive border gateway, make sure the device associated with the interconnect interface belongs to the device group specified for a gateway member of that tenant-exclusive border gateway：互联接口关联的设备必须属于租户独占的出口网关的出口网关成员的设备组 · When you bind multiple interconnect interfaces of the same device to a border gateway, make sure these interconnect interfaces use different IP addresses：同一出口网关绑定多个同一设备的互联接口，互联接口的IP不能冲突 · When you bind interconnect interfaces to a tenant-exclusive border gateway, make sure these interconnect interfaces are different from each other：租户独占的出口网关绑定的互联接口重复 · You can configure only one gateway member for a tenant-exclusive border gateway：租户独占的出口网关仅支持配置一个出口网关成员 · The method to deploy basic external connectivity settings cannot be Manual for a tenant-exclusive border gateway：租户独占的出口网关不允许外网转发基础配置为手动预配置 · Make sure the devices bound to the border gateway use different interconnect port IP addresses：出口网关绑定不同设备的互联接口IP不能相同 · Only border gateways of the manual deployment type support external route reduction：仅手动预配置类型出口网关支持配置外网路由精简 · When the network cloud feature is enabled, external route reduction is not supported：网络云场景不支持配置出口网关的外网路由精简 |
|
关键字 |
UPDATE_GATEWAY_OP |
|
日志内容 |
Updated gateway: $1 |
|
参数解释 |
$1：出口网关配置信息 |
|
举例 |
Updated gateway: ID: [741f1414-d71e-4775-acf9-d68bbb55e803] Name: [gatewayName]] Description: [create gateway] Fw_Export_Default_Route_Advertise_Always:[false] Type: [GROUP] Gateway member list: [ 5da35b42-1e37-4c3f-928b-0afc77fcfd34 ] |
|
日志说明 |
用户进行了修改出口网关的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service is disabled：服务未启动 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · Unknown internal server error：未知的内部服务器错误 · Invalid description：无效的描述 · Invalid name：无效的名称 · Invalid parameter：无效的参数 · The gateway does not exist：指定的出口网关不存在 · The gateway is being used：指定的出口网关正在被使用 · The gateway name already exists：出口网关名称已存在 · The gateway type cannot be edited：出口网关类型不允许修改 · You can specify a maximum of two gateway members when the gateway type is GROUP：当出口网关类型为GROUP时最多可指定两个网关成员 · You can specify only one gateway member when the gateway type is VIRTUAL：当出口网关类型为VIRTUAL时仅能指定一个网关成员 · Cannot specify nonexistent gateway members：出口网关成员不存在 · The gateway type and gateway member type do not match：出口网关类型和网关成员类型不同 · Duplicated gateway members exist：成员重复 · The gateway members of a gateway must belong to different device groups：设备组重复 · The gateway members must belong to the same type of device groups：指定的出口网关成员所属的设备组类型必须相同 · The device groups to which the gateway members belong must have the same fw_for_external parameter value：指定的出口网关成员所属的两个设备组是否允许外网流量做防火墙业务开关必须相同 · The device groups to which the gateway members belong must have the same fw_only_for_external parameter value：指定的出口网关成员所属的两个设备组是否允许非外网流量做防火墙业务开关必须相同 · The device groups to which the gateway members belong must have the same fw_for_internal parameter value：指定的出口网关成员所属的两个设备组是否允许内网流量做防火墙业务开关必须相同 · The device groups to which the gateway members belong must have the same connection type：指定的出口网关成员所属的两个设备组连接方式必须相同 · You can specify only one gateway member when the fabric of the device group is not enabled with EVPN：设备组对应Fabric的EVPN开关为关时，出口网关只能存在一个网关成员 · The fabrics of the device groups to which the gateway members belong must have the same EVPN state：指定的出口网关成员所属两个设备组对应Fabric的EVPN开关必须一致 · The gateway member has been bound to another gateway：指定的网关成员已被其他出口网关绑定 · The gateway member must have different priorities：出口网关成员的优先级不允许相同 · You have no privilege to perform this operation：用户无权限执行此操作 · You cannot bind the vRouter to the border gateway, because the positions of the associated device group include only DC interconnection or fabric interconnection and DC interconnection：虚拟路由器不支持绑定设备组的网络位置仅为DC间互联或者Fabric间互通+DC间互联的出口网关 · The positions of the gateway members include only DC interconnection or fabric interconnection and DC interconnection. You cannot configure gateway sharing or method to deploy basic external connectivity settings for the border gateway：当出口网关成员的网络位置仅为DC间互联或者Fabric间互通+DC间互联时，出口网关不支持配置共享网关和外网转发基础配置 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · You cannot change the name of the border gateway, because the border gateway is already bound to a vRouter in the network cloud scenario：网络云场景下，虚拟路由器已绑定该出口网关，不允许修改出口网关名称 · If the following conditions exist, you cannot change the device group setting of a border gateway member: 1. A member of the device group specified for the border gateway member is associated with an interconnect interface. 2. The interconnect interface is already bound to a tenant-exclusive border gateway：出口网关成员的设备组关联的互联接口已被租户独占出口网关绑定，出口网关成员的设备组不允许修改 · When you add a gateway member for a tenant-exclusive border gateway, make sure the device group specified for that gateway member has border gateway and DCI capabilities：租户独占的出口网关的出口网关成员的设备组应具有出口网关和DC间互联功能 · You cannot change the tenant-exclusive mode setting of a border gateway：出口网关的租户独占配置项不支持修改 · Only tenant-exclusive border gateways support interconnect interface bindings：仅支持租户独占的出口网关绑定互联接口 · You can bind up to 48 interconnect interfaces to a tenant-exclusive border gateway：租户独占的出口网关绑定互联接口的数量最多为48个 · The interconnect interface specified for the border gateway does not exist：出口网关绑定的互联接口不存在 · When you bind an interconnect interface to a tenant-exclusive border gateway, make sure the border gateway already has gateway members：租户独占的出口网关绑定互联接口时，必须绑定出口网关成员 · The interconnect interface is already bound to another tenant-exclusive border gateway：互联接口已被其他租户独占的出口网关绑定 · When you bind an interconnect interface to a tenant-exclusive border gateway, make sure the device associated with the interconnect interface belongs to the device group specified for a gateway member of that tenant-exclusive border gateway：互联接口关联的设备必须属于租户独占的出口网关的出口网关成员的设备组 · When you bind multiple interconnect interfaces of the same device to a border gateway, make sure these interconnect interfaces use different IP addresses：同一出口网关绑定多个同一设备的互联接口，互联接口的IP不能冲突 · You cannot unbind a gateway member from a border gateway when a member of the device group associated with that member already has an interconnect interface binding：出口网关成员关联的设备组中的设备已被互联接口所关联，出口网关不允许解绑该出口网关成员 · After you bind an interconnect interface associated with a member of a device group to a border gateway, you cannot unbind the gateway member associated with the device group from that border gateway：出口网关新绑定的互联接口关联的设备对应设备组关联的出口网关成员不允许被解绑 · When you bind interconnect interfaces to a tenant-exclusive border gateway, make sure these interconnect interfaces are different from each other：租户独占的出口网关绑定的互联接口重复 · You can configure only one gateway member for a tenant-exclusive border gateway：租户独占的出口网关仅支持配置一个出口网关成员 · After you bind an interconnect interface associated with a member of a device group to a border gateway, you cannot change the device group setting of the gateway member associated with the device group：出口网关新绑定的互联接口关联的设备对应设备组关联的出口网关成员不允许修改设备组 · After you bind an interconnect interface associated with a member of a device group to a border gateway, you cannot delete the gateway member associated with the device group from that border gateway：出口网关新绑定的互联接口关联的设备对应设备组关联的出口网关成员不允许被删除 · Make sure the devices bound to the border gateway use different interconnect port IP addresses：出口网关绑定不同设备的互联接口IP不能相同 · Only border gateways of the manual deployment type support external route reduction：仅手动预配置类型出口网关支持配置外网路由精简 · When the network cloud feature is enabled, external route reduction is not supported：网络云场景不支持配置出口网关的外网路由精简 · After you enable external route reduction for a border gateway, vRouters bound to that border gateway cannot have the same internal subnet address：切换外网路由精简为开启时，不允许该出口网关绑定的虚拟路由器存在网段相同的内网子网 |
|
关键字 |
DELETE_GATEWAY_OP |
|
日志内容 |
Deleted gateway: $1 |
|
参数解释 |
$1：网关UUID |
|
举例 |
Deleted gateway: [741f1414-d71e-4775-acf9-d68bbb55e803] |
|
日志说明 |
用户进行了删除出口网关的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service is disabled：服务未启动 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid parameter：无效的参数 · The gateway does not exist：指定的出口网关不存在 · The gateway is being used by an external network：出口网关已被外部网络使用 · The gateway is being used by a tenant：出口网关已被租户使用 · The gateway is being used by a vRouter：出口网关已被虚拟路由器使用 · The gateway has gateway members：出口网关中存在网关成员 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_GATEWAY_MEMBER_OP |
|
日志内容 |
Created gateway member: $1 |
|
参数解释 |
$1：网关成员配置信息 |
|
举例 |
Created gateway member: ID: [741f1414-d71e-4775-acf9-d68bbb55e803] Name: [gwMemberName]] Description: [create gateway member] Family:[PHY_DEV ] Group ID:[ as1f1414-d71e-4775-acf9-d68bbb55e632] Priority: 0 |
|
日志说明 |
用户进行了创建出口网关成员的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service is disabled：服务未启动 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · Unknown internal server error：未知的内部服务器错误 · Invalid description：无效的描述 · Invalid name：无效的名称 · Invalid parameter：无效的参数 · No network function list is specified for the physical resource：组合网关成员没有设备组 · The management IP address conflicts with the host IP：管理IP和主机IP冲突 · Invalid NETCONF username：无效的NETCONF 用户名 · Invalid NETCONF password：无效的NETCONF密码 · The IP address pool doesn't exist：这安全外网地址池不存在 · The VNFM service is not loaded：这VNFM服务没有加载 · The device group doesn't exist：设备组不存在 · The default VLAN pool does not exist：默认VLAN池不存在 · The device group is not bound to the specified type of default IP address pool:服务设备组没有绑定指定的默认地址池 · The gateway member already exists：指定的网关成员已存在 · The resource type is required：未指定资源类型 · The gateway member name already exists：网关成员名称已存在 · A virtual gateway member can be bound to only one resource pool：虚拟网关成员只允许绑定一个资源池 · NGFW gateway members cannot be bound to VNF templates：NGFW类型的网关成员不允许绑定VNF模板 · A virtual gateway member can be bound to only one VNF template：虚拟网关成员只允许绑定一个VNF模板 · NFV gateway members cannot be bound to resource pools：NFV类型的网关成员不允许绑定资源池 · The device group is not enabled with the gateway feature：设备组未开启出口网关开关 · Cannot specify priorities for virtual gateway members：虚拟网关成员不允许指定优先级 · Network parameters are required：创建网关成员时未指定相应的网络功能参数 · The management IP address already exists：指定的管理IP地址已存在 · Only NFV gateway members support the sec_ext_ip_pool parameter：只有NFV类型的资源支持配置安全外网参数 · You have no privilege to perform this operation：用户无权限执行此操作 · When a member of a border gateway is bound to a remote device group, the border gateway can be bound to only one member：当出口网关成员绑定远端设备组时，出口网关只能绑定一个成员 · The VPN instance is already used：指定的VPN实例已存在 · The setting for smooth flag is incorrect：平滑开关取值错误 · You cannot configure a service resource pool for members of a border gateway with the firewall deployment mode disabled：防火墙接入模式为关闭的出口网关成员不允许配置服务资源池 · The border gateway member cannot be bound to a device group whose position is service leaf：出口网关成员不支持绑定网络位置为Service Leaf的设备组 |
|
关键字 |
UPDATE_GATEWAY_MEMBER_OP |
|
日志内容 |
Updated gateway member: $1 |
|
参数解释 |
$1：网关成员配置信息 |
|
举例 |
Updated gateway member: ID: [741f1414-d71e-4775-acf9-d68bbb55e803] Name: [gwMemberNameUpdate]] Description: [update gateway member] Family: [PHY_DEV ] Group ID:[ fs1f1414-d71e-4775-acf9-d68bbb55e639] Priority: 0 |
|
日志说明 |
用户进行了修改出口网关成员的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service is disabled：服务未启动 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · Unknown internal server error：未知的内部服务器错误 · Invalid description：无效的描述 · Invalid name：无效的名称 · Invalid parameter：无效的参数 · No network function list is specified for the physical resource：组合网关成员没有设备组 · The gateway group doesn't exist：设备组不存在 · The management IP address conflicts with the host IP：管理IP和主机IP冲突 · Invalid NETCONF username：无效的NETCONF 用户名 · Invalid NETCONF password：无效的NETCONF密码 · The IP address pool doesn't exist：这安全外网地址池不存在 · The VNFM service is not loaded：这VNFM服务没有加载 · The device group doesn't exist：设备组不存在 · The default VLAN pool does not exist：默认VLAN池不存在 · The device group is not bound to the specified type of default IP address pool:服务设备组没有绑定指定的默认地址池 · The gateway member is being using：网关成员正在被使用 · The resource type is required：未指定资源类型 · The gateway member name already exists：网关成员名称已存在 · A virtual gateway member can be bound to only one resource pool：虚拟网关成员只允许绑定一个资源池 · NGFW gateway members cannot be bound to VNF templates：NGFW类型的网关成员不允许绑定VNF模板 · A virtual gateway member can be bound to only one VNF template：虚拟网关成员只允许绑定一个VNF模板 · NFV gateway members cannot be bound to resource pools：NFV类型的网关成员不允许绑定资源池 · The device group is not enabled with the gateway feature：设备组未开启出口网关开关 · Cannot specify priorities for virtual gateway members：虚拟网关成员不允许指定优先级 · Network parameters are required：创建网关成员时未指定相应的网络功能参数 · The management IP address already exists：指定的管理IP地址已存在 · Only NFV gateway members support the sec_ext_ip_pool parameter：只有NFV类型的资源支持配置安全外网参数 · You have no privilege to perform this operation：用户无权限执行此操作 · The VPN instance is already used：指定的VPN实例已存在 · The setting for smooth flag is incorrect：平滑开关取值错误 · You cannot configure a service resource pool for members of a border gateway with the firewall deployment mode disabled：防火墙接入模式为关闭的出口网关成员不允许配置服务资源池 · If the following conditions exist, you cannot change the device group setting of a border gateway member: 1. A member of the device group specified for the border gateway member is associated with an interconnect interface. 2. The interconnect interface is already bound to a tenant-exclusive border gateway：出口网关成员的设备组关联的互联接口已被租户独占出口网关绑定，出口网关成员的设备组不允许修改 · Cannot edit the vpnInstance field for the gateway member because the gateway member has been used by a vRouter：该网关成员已被虚拟路由器引用，vpnInstance字段不允许被修改 |
|
关键字 |
DELETE_GATEWAY_MEMBER_OP |
|
日志内容 |
Deleted gateway member: $1 |
|
参数解释 |
$1：出口网关成员UUID |
|
举例 |
Deleted gateway member: 741f1414-d71e-4775-acf9-d68bbb55e803 |
|
日志说明 |
用户进行了删除出口网关成员的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service is disabled：服务未启动 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid parameter：无效的参数 · The gateway member does not exist：指定的网关成员不存在 · The gateway member is being using：网关成员正在被使用 · You have no privilege to perform this operation：用户无权限执行此操作 · You cannot delete a gateway member from a border gateway when a member of the device group associated with that gateway member already has an interconnect interface binding：出口网关成员关联的设备组中的设备已被互联接口所关联，不允许删除该出口网关成员 |
|
关键字 |
CREATE_INTERCONNECT_INTERFACE _OP |
|
日志内容 |
Created interconnect interface : $1 |
|
参数解释 |
$1：互联接口信息 |
|
举例 |
Created interconnect interface: ID:[20362bcb-0416-4761-9aac-d7b4f7e98857] Name:[123] connectVlan:[123] connectInterfaceType:[VLAN_INTERFACE] connectMainIp:[1.2.3.5/24] connectIpv6List:[1::1/64]] deviceId:[e405b1eb-820b-4327-9ec3-a5ea26b25126] devicePorts:[[Ten-GigabitEthernet1/0/1]] |
|
日志说明 |
用户进行了创建互联接口的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service is disabled：服务未启动 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · Unknown internal server error：未知的内部服务器错误 · Invalid name：无效的名称 · Invalid parameter：无效的参数 · You must configure an IPv4 address or an IPv6 address, or both of them for the interconnect interface：互联接口的IPv4主IP地址或IPv6地址至少配置其中之一 · The specified interconnect VLAN ID or subinterface number cannot be the same as the segment ID of any external network and cannot be included in the VLAN ID pools of tenant carrier network type or vRouter interconnection network type：互联VLAN/子接口编号不能和外部网络的Segment ID相同且不允许在租户承载网和虚拟路由器互通网络类型的VLAN池中 · An interconnect interface can have a maximum of one IPv6 address：互联接口最多只能配置一个IPv6地址 · Please specify a device interface：设备接口不能为空 · You can specify up to 48 device interfaces：设备接口数量不能超过48个 · Do not specify some device interfaces repeatedly：设备接口重复 · When the interconnect interface type is subinterface, you can configure only one device interface：互联接口类型为子接口时，设备接口只能配置一个 · Interconnect interface configuration is not supported in the network cloud scenario： 网络云场景下不支持配置互联接口 · An interconnect interface already exists with the specified name：互联接口名称已存在 · Please specify a device ID for the interconnect interface：未指定互联接口的device_id字段 · Please specify a VLAN ID for the interconnect interface：未指定互联接口的connect_vlan字段 · Please specify an interconnect interface name：未指定互联接口的name字段 · Invalid interconnect interface type：无效的互联接口类型 · The interconnect subinterface is already configured for the device：该设备已配置了相同的子接口 · When the interconnect interface type is VLAN interface, the specified device interfaces must be trunk ports：互联接口类型为VLAN_INTERFACE时，设备接口必须是Trunk类型 · The device interfaces specified for the interconnect interface must be available Layer 2 interfaces：互联接口指定的设备接口不是可用的二层接口 · The device interfaces specified for the interconnect interface must be available Layer 3 interfaces：互联接口指定的设备接口不是可用的三层接口 · The IP address of an interconnect interface cannot be included in the address pools of the following types: tenant carrier network, tenant carrier FW internal network, tenant carrier LB internal network, and DC interconnection network：互联接口的IP不能与租户承载、租户承载防火墙内网、租户承载负载分担内网、数据中心互联网络类型的地址池中的IP冲突 · An interconnect interface already exists with the specified UUID：互联接口UUID已存在 · When you associate a device with an interconnect interface, make sure the device is a border device：互联接口关联的设备必须是边界设备 · When you associate a border device with an interconnect interface, make sure the border device belongs to a device group enabled with border gateway and DCI capabilities：互联接口关联的边界设备须已添加到具备出口网关和DC间互联功能的设备组中 · The interconnect interfaces associated with the same device must use different interconnect VLAN IDs：同设备的互联接口的互联VLAN不能重复 · Up to 255 characters, case sensitive：参数不能超过255个字符，区分大小写 · Invalid IP address：无效的IP地址 · Invalid IPv6 address：无效的IPv6地址 · The VLAN ID is invalid or out of range：无效的VLAN ID或者VLAN ID范围错误 · An interconnect interface cannot use Route-Aggregation256. This is reserved for the keepalive LAG interface：互联接口不可占用keepalive聚合接口Route-Aggregation256 |
|
关键字 |
UPDATE_CONNECT_INTERFACE _OP |
|
日志内容 |
Updated interconnect interface VLAN : $1 |
|
参数解释 |
$1：互联接口信息 |
|
举例 |
Updated interconnect interface: ID:[20362bcb-0416-4761-9aac-d7b4f7e98857] Name:[123] connectVlan:[123] connectInterfaceType:[VLAN_INTERFACE] connectMainIp:[1.2.3.4/24] connectIpv6List:[[1::1/64]] deviceId:[e405b1eb-820b-4327-9ec3-a5ea26b25126] devicePorts:[[Ten-GigabitEthernet1/0/1]] |
|
日志说明 |
用户进行了修改互联接口的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service is disabled：服务未启动 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · Unknown internal server error：未知的内部服务器错误 · The specified interconnect interface does not exist：互联接口不存在 · The UUID of an interconnect interface is not editable：互联接口UUID不允许修改 · You cannot change the type of an interconnect interface：互联接口类型不允许修改 · You cannot change the VLAN ID or subinterface number of an interconnect interface：互联接口VLAN/子接口编号不允许修改 · You cannot change the device association of an interconnect interface：互联接口关联的设备不允许修改 · When the interconnect interface type is subinterface, you cannot change its device interface setting：互联接口为子接口类型时，设备接口不允许修改 · When the interconnect interface type is VLAN interface, the specified device interfaces must be trunk ports：互联接口类型为VLAN_INTERFACE时，设备接口必须是Trunk类型 · The device interfaces specified for the interconnect interface must be available Layer 2 interfaces：互联接口指定的设备接口不是可用的二层接口 · The IP address of an interconnect interface cannot be included in the address pools of the following types: tenant carrier network, tenant carrier FW internal network, tenant carrier LB internal network, and DC interconnection network：互联接口的IP不能与租户承载、租户承载防火墙内网、租户承载负载分担内网、数据中心互联网络类型的地址池中的IP冲突 · Please specify a device interface：设备接口不能为空 · You can specify up to 48 device interfaces：设备接口数量不能超过48个 · Do not specify some device interfaces repeatedly：设备接口重复 · The interconnect interfaces associated with the same device must use different interconnect VLAN IDs：同设备的互联接口的互联VLAN不能重复 · Up to 255 characters, case sensitive：参数不能超过255个字符，区分大小写 · Invalid IP address：无效的IP地址 · Invalid IPv6 address：无效的IPv6地址 |
|
关键字 |
DELETE_CONNECT_INTERFACE _OP |
|
日志内容 |
Deleted interconnect interface: $1 |
|
参数解释 |
$1：互联接口的UUID |
|
举例 |
Deleted interconnect interface: 20362bcb-0416-4761-9aac-d7b4f7e98857 |
|
日志说明 |
用户进行了删除互联接口的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service is disabled：服务未启动 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · Unknown internal server error：未知的内部服务器错误 · The specified interconnect interface does not exist：互联接口不存在 · You cannot delete the interconnect interface, because it already has a border gateway binding：互联接口被出口网关绑定时，不允许删除 · You cannot delete the interconnect interface, because it already has a BGP neighbor binding：互联接口被BGP邻居绑定时，不允许删除 |
|
关键字 |
CREATE_DEVICE_INFORMATION_OP |
|
日志内容 |
Created auto deployment device information: $1 |
|
参数解释 |
$1：自动化部署的设备信息的配置信息 |
|
举例 |
Created auto deployment device information: ID:[deb8c576-9871-4224-b3fb-1d43988cf01c] Serial number:[spine] Index number:[spine] Role name:[spine] Management IP:[2.1.1.1] Gateway:[false] Fabric ID:[d51aa540-40ec-4d68-9abd-623f884cc227] Fabric name:[fabric] MLAG:[false] Remote:[false] |
|
日志说明 |
用户进行了创建自动化部署的设备信息的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · Invalid device serial number：无效的设备序列号 · To create an auto deployment device information, you must specify a device serial number：创建自动化部署的设备信息时，必须指定设备序列号 · Invalid role name：无效的角色名称 · The system name cannot exceed 64 characters：系统名称最长64个字符 · Invalid network entity ID：无效的网络实体ID · Invalid parameter：无效的参数 · Invalid IP address：无效的IP地址 · An aggregation device cannot provide gateway services：设备角色为aggregation时，设备不具有网关能力 · Failed to add device to the device list. It is already managed by the controller：设备已经被控制组件纳管，不允许加入设备清单 · The specified Management IP has been used by another auto deployment device information：指定的管理IP地址不允许在自动化部署的设备信息列表中 · The Management IP on the specified whitelist has been used by a managed device：指定的管理IP地址不允许在已纳管网元列表中 · The management IP address has been used：管理IP地址已经被分配 · Please first configure an IP pool for auto deployment：请先配置自动化上线地址池 · The management IP address cannot belong to any existing address pools except for the management address pool：管理IP地址不允许属于除管理IP地址池外的其他地址池 · The management IP address cannot belong to the IP pool for auto deployment：管理IP地址不允许属于自动化上线址池 · You have no privilege to perform this operation：用户无权限执行此操作 · An access device cannot provide gateway services：设备角色为Access时，设备不具有网关能力 · You cannot enable M-LAG on an access device. Please set the M-LAG parameter to false：设备角色为Access时，不允许使能跨设备聚合 · Only leaf border devices can be configured as remote devices：仅支持Leaf边界设备作为远端设备 · The management IP address cannot belong to the IP pool for remote auto deployment：管理IP地址不允许属于远端自动化上线址池 · The management IP address of local device cannot belong to the remote management IP pool：本地设备管理IP地址不允许属于远端管理IP地址池 · The management IP address of remote device cannot belong to the local management IP pool：远端设备管理IP地址不允许属于本地管理IP地址池 · Downlink interfaces cannot exceed 255 characters：下行口长度不能超过255个字符 · Invalid downlink interfaces：无效的下行口 · When the service network type of the fabric is VLAN, the device type must be underlay and the device role must be spine or leaf for automatic onboarding：当Fabric的业务网络类型为VLAN时，仅支持自动化上线Spine、Leaf角色的Underlay物理设备 · When the service network type for a fabric is VLAN, you cannot configure the IRF fabric settings：当Fabric的业务网络类型为VLAN时，不支持配置IRF堆叠信息 · When the service network type of the fabric is VXLAN, not support the device type is underlay and the device role id leaf for automatic onboarding：当Fabric业务网络类型为VXLAN时，不支持自动化上线Leaf角色的Underlay物理设备 · The VTEP IP is in use：VTEP IP已经被使用 · The DCI VTEP IP is in use：DCI VTEP IP已经被使用 · The VTEP IP cannot be the same as the management IP：VTEP IP不能和管理IP相同 · The DCI VTEP IP cannot be the same as the management IP：DCI VTEP IP不能和管理IP相同 · Do not assign the same IP address to VTEP IP and DCI VTEP IP：DCI VTEP IP不能和VTEP IP相同 · The VTEP IP address has been configured as the virtual VTEP IP address of an M-LAG system：VTEP IP已被M-LAG系统虚拟VTEP IP使用 · The VTEP IP address has been configured as a critical VLAN interface IP address on an M-LAG system：VTEP IP已被M-LAG系统逃生VLAN IP使用 · On the device with the specified SN, the downlink interface conflicts with the device port in the M-LAG group plan：指定序列号的设备信息下行口与M-LAG组规划的设备端口冲突 |
|
关键字 |
UPDATE_DEVICE_INFORMATION_OP |
|
日志内容 |
Updated auto deployment device information: $1 |
|
参数解释 |
$1：自动化部署的设备信息的配置信息 |
|
举例 |
Updated auto deployment device information: ID:[ d5c1d35e-62f5-4259-a905-98183d9fd065] Serial number:[210235A2C4H187000881] Role name:[leaf] Sysname:[68-95] Management IP:[12.12.12.1] NetworkEntity ID:[ab.cdef.1234.5678.9abc.00] Loopback IP:[68.0.0.15] Gateway:[false] |
|
日志说明 |
用户进行了修改自动化部署的设备信息的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · The specified auto deployment device information does not exist.：指定的自动化部署的设备信息不存在 · Invalid device serial number：无效的设备序列号 · Invalid role name：无效的角色名称 · The system name cannot exceed 64 characters：系统名称最长64个字符 · Invalid network entity ID：无效的网络实体ID · Invalid parameter：无效的参数 · Invalid IP address：无效的IP地址 · An aggregation device cannot provide gateway services：设备角色为aggregation时，设备不具有网关能力 · Failed to add device to the device list. It is already managed by the controller：设备已经被控制组件纳管，不允许加入设备清单 · The specified Management IP has been used by another auto deployment device information：指定的管理IP地址不允许在自动化部署的设备信息列表中 · The Management IP on the specified whitelist has been used by a managed device：指定的管理IP地址不允许在已纳管网元列表中 · The management IP address has been used：管理IP地址已经被分配 · Please first configure an IP pool for auto deployment：请先配置自动化上线地址池 · The management IP address cannot belong to any existing address pools except for the management address pool：管理IP地址不允许属于除管理IP地址池外的其他地址池 · The management IP address cannot belong to the IP pool for auto deployment：管理IP地址不允许属于自动化上线址池 · You have no privilege to perform this operation：用户无权限执行此操作 · An access device cannot provide gateway services：设备角色为Access时，设备不具有网关能力 · You cannot enable M-LAG on an access device. Please set the M-LAG parameter to false：设备角色为Access时，不允许使能跨设备聚合 · Only leaf border devices can be configured as remote devices：仅支持Leaf边界设备作为远端设备 · The device type field in the device list cannot be edited, because the device list has been used by a edge link：指定的设备清单已被边缘链路使用，设备类型不能修改 · The remote device field in the device list cannot be edited, because the device list has been used by a link：指定的设备清单已被链路信息使用，远端设备字段不能修改 · The management IP address cannot belong to the IP pool for remote auto deployment：管理IP地址不允许属于远端自动化上线址池 · The management IP address of local device cannot belong to the remote management IP pool：本地设备管理IP地址不允许属于远端管理IP地址池 · The management IP address of remote device cannot belong to the local management IP pool：远端设备管理IP地址不允许属于本地管理IP地址池 · You cannot edit the NETCONF username. The device has been locked：设备已加锁，不允许修改NETCONF用户名 · Downlink interfaces cannot exceed 255 characters：下行口长度不能超过255个字符 · Invalid downlink interfaces：无效的下行口 · When the service network type of the fabric is VLAN, the device type must be underlay and the device role must be spine or leaf for automatic onboarding：当Fabric的业务网络类型为VLAN时，仅支持自动化上线Spine、Leaf角色的Underlay物理设备 · When the service network type for a fabric is VLAN, you cannot configure the IRF fabric settings：当Fabric的业务网络类型为VLAN时，不支持配置IRF堆叠信息 · When the service network type of the fabric is VXLAN, not support the device type is underlay and the device role id leaf for automatic onboarding：当Fabric业务网络类型为VXLAN时，不支持自动化上线Leaf角色的Underlay物理设备 · The VTEP IP is in use：VTEP IP已经被使用 · The DCI VTEP IP is in use：DCI VTEP IP已经被使用 · The VTEP IP cannot be the same as the management IP：VTEP IP不能和管理IP相同 · The DCI VTEP IP cannot be the same as the management IP：DCI VTEP IP不能和管理IP相同 · Do not assign the same IP address to VTEP IP and DCI VTEP IP：DCI VTEP IP不能和VTEP IP相同 · The VTEP IP address has been configured as the virtual VTEP IP address of an M-LAG system：VTEP IP已被M-LAG系统虚拟VTEP IP使用 · The VTEP IP address has been configured as a critical VLAN interface IP address on an M-LAG system：VTEP IP已被M-LAG系统逃生VLAN IP使用 · On the device with the specified SN, the downlink interface conflicts with the device port in the M-LAG group plan：指定序列号的设备信息下行口与M-LAG组规划的设备端口冲突 |
|
关键字 |
DELETE_DEVICE_INFORMATION_OP |
|
日志内容 |
Deleted auto deployment device information: $1 |
|
参数解释 |
$1：自动化部署的设备信息的ID |
|
举例 |
Deleted auto deployment device information: d5c1d35e-62f5-4259-a905-98183d9fd065 |
|
日志说明 |
用户进行了删除自动化部署的设备信息的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · The auto deployment device information doesn't exist：指定的自动化部署的设备信息不存在 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_LINK_INFORMATION_OP |
|
日志内容 |
Created link information: $1 |
|
参数解释 |
$1：链路信息的配置信息 |
|
举例 |
Created link information [ ID=3b55e8b8-45eb-4513-8e53-d67a810bba51, Serial number 4A=210235A1TXH165000106, Index number 4A=localSpine, Port 4A=xge1/0/1, Serial number 4B=210235A1TYH178000044, Index number 4B=remoteLeaf, Port 4B=xge1/0/5, Usage=edge_link, Fabric ID=97e73e1a-aac6-4583-be3f-20edfb1b666f, Fabric name=null ] |
|
日志说明 |
用户进行了创建链路信息的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · You have no privilege to perform this operation：用户无权限执行此操作 · Please specify a link type：链路类型不能为空 · Invalid link type：无效的链路类型 · To create a edge link, you must specify a spine device and a leaf device：当链路类型为边缘链路时，链路必须由设备角色为Spine和Leaf的两台设备组成 · To create a edge link, you must configure the leaf device as a border device：当链路类型为边缘链路时，Leaf角色的设备必须是边界设备 · A local device cannot be specified in a edge link：本地设备不可用于边缘链路 · A remote device cannot be specified in a local link：远端设备不可用于本地链路 |
|
关键字 |
UPDATE_LINK_INFORMATION_OP |
|
日志内容 |
Update link information: $1 |
|
参数解释 |
$1：链路信息的配置信息 |
|
举例 |
Updated link information [ ID=3b55e8b8-45eb-4513-8e53-d67a810bba51, Serial number 4A=210235A1TXH165000106, Index number 4A=localSpine, Port4A=xge1/0/1, Serial number 4B=210235A1TYH178000044, Index number 4B=remoteLeaf, Port 4B=xge1/0/5, Usage=edge_link, Fabric ID=97e73e1a-aac6-4583-be3f-20edfb1b666f, Fabric name=null ] |
|
日志说明 |
用户进行了修改链路信息的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · You have no privilege to perform this operation：用户无权限执行此操作 · Please specify a link type：链路类型不能为空 · Invalid link type：无效的链路类型 · To create a edge link, you must specify a spine device and a leaf device：当链路类型为边缘链路时，链路必须由设备角色为Spine和Leaf的两台设备组成 · To create a edge link, you must configure the leaf device as a border device：当链路类型为边缘链路时，Leaf角色的设备必须是边界设备 · A local device cannot be specified in a edge link：本地设备不可用于边缘链路 · A remote device cannot be specified in a local link：远端设备不可用于本地链路 |
|
关键字 |
DELETE_LINK_INFORMATION_OP |
|
日志内容 |
Deleted link information: $1 |
|
参数解释 |
$1：链路信息的ID |
|
举例 |
Deleted link information: ID:[3b55e8b8-45eb-4513-8e53-d67a810bba51] Index number4A:[localSpine Index number4B:[remoteLeaf] |
|
日志说明 |
用户进行了删除链路信息的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
IMPORT_DEVICE_LIST_OP |
|
日志内容 |
Bulk added devices to the device list: $1 |
|
参数解释 |
$1：设备清单的配置信息 |
|
举例 |
Bulk added devices to the device list: Added devices: 0, Added links: 0, Added MLAGs: 0 Ignored devices: 2, Ignored links: 1, Ignored MLAGs: 1 |
|
日志说明 |
用户进行了导入设备清单的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · You have no privilege to perform this operation：用户无权限执行此操作 · Please specify a link type：链路类型不能为空 · Invalid link type：无效的链路类型 · To create a edge link, you must specify a spine device and a leaf device：当链路类型为边缘链路时，链路必须由设备角色为Spine和Leaf的两台设备组成 · To create a edge link, you must configure the leaf device as a border device：当链路类型为边缘链路时，Leaf角色的设备必须是边界设备 · A local device cannot be specified in a edge link：本地设备不可用于边缘链路 · A remote device cannot be specified in a local link：远端设备不可用于本地链路 · Only leaf border devices can be configured as remote devices：仅支持Leaf边界设备作为远端设备 · The management IP address cannot belong to the IP pool for remote auto deployment：管理IP地址不允许属于远端自动化上线址池 · The management IP address of local device cannot belong to the remote management IP pool：本地设备管理IP地址不允许属于远端管理IP地址池 · The management IP address of remote device cannot belong to the local management IP pool：远端设备管理IP地址不允许属于本地管理IP地址池 · Downlink interfaces cannot exceed 255 characters：下行口长度不能超过255个字符 · Invalid downlink interfaces：无效的下行口 · When the service network type of the fabric is VLAN, the device type must be underlay and the device role must be spine or leaf for automatic onboarding：当Fabric的业务网络类型为VLAN时，仅支持自动化上线Spine、Leaf角色的Underlay物理设备 · When the service network type for a fabric is VLAN, you cannot configure the IRF fabric settings：当Fabric的业务网络类型为VLAN时，不支持配置IRF堆叠信息 · When the service network type of the fabric is VXLAN, not support the device type is underlay and the device role id leaf for automatic onboarding：当Fabric业务网络类型为VXLAN时，不支持自动化上线Leaf角色的Underlay物理设备 · Failed to read the Excel file. Reason: $1：Excel文件读取失败，原因为$1 $1：文件读取失败的的原因 ¡ The hyperlink for cell $2 references relation $3, but that didn't exist：单元格$2的超链接引用关系$3不存在 |
|
关键字 |
DELETE_ASSETLIST_OP |
|
日志内容 |
Deleted assetlist: $1 |
|
参数解释 |
$1：资产信息ID |
|
举例 |
Deleted assetlist: c6c1d35e-62f5-4259-a905-98183d9fd065 |
|
日志说明 |
用户进行了删除资产清单的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · The specified asset list does not exist：指定的资产清单不存在 · Only unmanaged assets can be deleted：只允许删除未纳管状态的资产 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
START_SYNCHRONIZATION_BRIDGEMAC_SERIALNUMBER_OP |
|
日志内容 |
· Started to synchronize physical NE bridgeMac and serialNumber info: [$1] · Started to synchronize all physical NE bridgeMac and serialNumber info. |
|
参数解释 |
$1：设备UUID |
|
举例 |
· Started to synchronize physical NE bridgeMac and serialNumber info: deviceList: [ 0dfc800f-8489-4efc-9e4d-c5efdd8795cd, ] reversRefresh:[true] · Started to synchronize all physical NE bridgeMac and serialNumber info. |
|
日志说明 |
控制组件同步网元设备的桥MAC和序列号信息 |
|
失败原因 |
当操作失败时，可能的原因如下： · A device synchronization task is in progress. Cannot create device synchronization tasks：控制组件正在同步信息，无法创建新的同步任务 · Unknown internal server error：未知的内部服务器错误 · Failed to obtain information about the IRF fabric：获取堆叠设备信息失败 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
START_SYNCHRONIZATION_PORT_OP |
|
日志内容 |
· Started to synchronize physical NE port info: [$1] · Started to synchronize all physical NE port info. |
|
参数解释 |
$1：设备UUID |
|
举例 |
· Started to synchronize physical NE port info: deviceList: [ 0dfc800f-8489-4efc-9e4d-c5efdd8795cd, ] reversRefresh:[true] · Started to synchronize all physical NE port info. |
|
日志说明 |
控制组件同步网元设备的端口信息 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown internal server error：未知的内部服务器错误 · You have no privilege to perform this operation：用户无权限执行此操作 · Please perform the operation on the active leader：请在主Leader上进行操作 |
|
关键字 |
CREATE_DC_CONNECTION_OP |
|
日志内容 |
Created DC connection: $1 |
|
参数解释 |
$1：数据中心连接信息 |
|
举例 |
Created DC connection: ID:[17dce0ce-4e46-425d-9aeb-fe39e8933b04] localDeviceId:[5512a2df-51ad-46d9-82d8-f7676ceab2af] peerDeviceInfo: [ deviceName: a dciVtepIp: 2.2.2.4 asNumber: 24 ] |
|
日志说明 |
用户进行了创建数据中心连接的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · Invalid JSON format：无效的JSON格式 · The service is disabled：服务未启动 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · Invalid parameter：无效参数 · Invalid name：无效的名称 · The local device does not exist：本端边界设备不存在 · DC interconnect must be enabled for the device group to which the local devices belong：本端边界设备所属的设备组必须开启DC间互联功能 · Invalid AS number of the peer device info：无效的对端设备AS号 · Invalid device name of the peer device info：无效的对端设备名称 · The DC connection already exists：数据中心连接已存在 · The DC connection name already exists：数据中心连接名称已存在 · The DCI VTEP IP of the peer device cannot be the same as the VTEP IP of any device of the local controller：对端设备的DCI VTEP IP和本端控制组件中设备的VTEP IP冲突 · The DCI VTEP IP of the local device is required：本端设备的DCI VTEP IP不能为空 · A DC connection already exists between the local and remote devices：本端设备和对端设备间已建立数据中心连接 · The DCI VTEP IP of the peer device cannot be the same as the DCI VTEP IP of any device of the local controller：对端设备的DCI VTEP IP和本端控制组件中设备的DCI VTEP IP冲突 · The AS number of the fabric to which the local device belongs cannot be empty：本端设备所属Fabric的AS号不能为空 · The AS number of the fabric to which the local device belongs cannot be the same as the AS number of the fabric to which the peer device belongs：本端设备所属Fabric的AS号与对端设备所属Fabric的AS不能相同 · Invalid IP address：无效的IP地址 · You have no privilege to perform this operation：用户无权限执行此操作 · The source and destination devices must use the same version of VTEP IP addresses to establish a DCI connection：源设备和目的设备的DCI VTEP IP版本不一致 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · The old and new AS numbers are inconsistent：新旧AS号字段不一致 |
|
关键字 |
UPDATE_DC_CONNECTION_OP |
|
日志内容 |
Updated DC connection: $1 |
|
参数解释 |
$1：数据中心连接信息 |
|
举例 |
Updated DC connection: ID:[23f1465b-574d-4a51-8ff5-59041ae19467] Name:[aa] localDeviceId:[5512a2df-51ad-46d9-82d8-f7676ceab2af] peerDeviceInfo: [ deviceName: a dciVtepIp: 1.1.1.8 asNumber: 8 ] |
|
日志说明 |
用户进行了修改数据中心连接的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · Invalid JSON format：无效的JSON格式 · The service is disabled：服务未启动 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · Invalid name：无效名字 · Invalid parameter：无效参数 · There are non-modifiable fields in this parameter：传入参数中有不可修改字段 · The DC connection does not exist：数据中心连接不存在 · The DC connection name already exists：数据中心连接名称已存在 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_DC_CONNECTION_OP |
|
日志内容 |
Deleted DC connection: $1. |
|
参数解释 |
$1：数据中心连接ID |
|
举例 |
Deleted DC connection:23f1465b-574d-4a51-8ff5-59041ae19467. |
|
日志说明 |
用户进行了删除数据中心连接的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · Invalid JSON format：无效的JSON格式 · The service is disabled：服务未启动 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Invalid parameter：无效参数 · Unknown internal server error：未知的内部服务器错误 · The DC connection does not exist：数据中心连接不存在 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
CREATE_REPLACE_TASK_OP |
|
日志内容 |
Created replacement task: $1 |
|
参数解释 |
$1：替换设备任务信息 |
|
举例 |
Created replacement task: replaceDeviceId:[ bbc199ca-8792-4656-8bab-5a16fc52c806] replaceType:[1] faultDevId:[bbc199ca-8792-4656-8bab-5a16fc52c806] devSn:[13212adasd2q321dadsa] masteSpineMac:[01-23-45-67-89-ab] startCfgName:[10.100.0.2_20190611093442_startup.cfg] faultDeviceSn:[13212adasd2q321dadss] |
|
日志说明 |
用户进行了创建设备替换任务的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · A master spine MAC is required when the replacement type is master spine：替换类型为Master Spine替换时，必须指定Master Spine MAC · The master spine MAC is invalid： 无效的Master Spine MAC · The number of running replacement tasks cannot exceed 5：正在执行的替换任务数最多支持5个 · A master spine device supports only the master spine replacement type：Master Spine设备仅支持Master Spine替换方式 · The backup configuration file of the failed device does not exist：故障设备的备份配置文件不存在 · The replacement device does not exist.：替换设备不存在 · The serial number of the replacement device is invalid：替换设备的序列号无效 · The replacement device and failed device cannot be the same：替换设备与故障设备不允许相同 · Replacement device with the specified serial number has been specified in another replacement task：指定序列号的替换设备已经被其他替换任务使用 · If you specify a replacement device by its serial number, make sure the device is not managed by the controller：通过序列号指定替换设备时，指定的设备不能加入控制组件 · Cannot replace a standalone device with an IRF fabric：不允许使用堆叠设备替换单体设备 · Failed device with the specified serial number does not exist:指定的故障设备序列号不存在 · The replacement device type cannot be underlay：替换的设备不允许为Underlay类型 · The failed device is not bound to a fabric.：故障设备未与Fabric绑定 · The replacement device is not bound to a fabric.：替换设备未与Fabric绑定 · The replacement device must belong to the same fabric as the failed device：故障设备和替换设备所属的Fabric必须相同 · The replacement device is not activated：替换设备未激活 · The replacement device must have the same role as the failed device：故障设备和替换设备的角色必须相同 · Internal error.：下发配置到设备失败 · The replacement task already exists：替换任务已存在 · The specified failed device does not exist.：指定故障设备不存在 · The failed device is being deleted：故障设备正在被删除 · Failed device with the specified ID does not exist.：指定ID的故障设备不存在 · The replacement device must have the same role as the failed device：故障设备与替换设备的角色不同。 · The replacement device must belong to same fabric as the failed device：故障设备与替换设备必须属于相同Fabric · The fault device has been in another replacement task：该故障设备存在于其他替换任务中 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_REPLACE_TASK_OP |
|
日志内容 |
Deleted replacement task: $1. |
|
参数解释 |
$1：替换设备的UUID |
|
举例 |
Deleted replacement task: fa906566-87d5-4480-b7e7-12dc20bc6173. |
|
日志说明 |
用户进行了删除设备替换任务的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · The specified replacement task does not exist：指定的替换设备任务不存在 · The current stage of the replacement task does not support deletion：当前替换任务流程不允许删除 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_BGP_NEIGHBOR_OP |
|
日志内容 |
Created BGP neighbor: $1. |
|
参数解释 |
$1：BGP邻居信息 |
|
举例 |
Created BGP neighbor: ID: [c962169b-1a71-449c-8407-a36e938916ec] Router ID: [94e28779-629f-4159-a7c6-261a57241658] Tenant ID: [28ebfffc-865f-4784-a7d5-33938daf8db1] BGP neighbor description:[] IP version:[4] Local AS number:[30] BGP neighbor name:[tt] Peer AS number:[31] Peer IP address:[31.1.1.1] Source IP: [[30.0.0.1]] Suppress:[false] Cloud region name: region auth:[BgpNeighborAuth [authType=AuthType{type=2, typeName='password'}]] bfd:[false] |
|
日志说明 |
用户进行了创建BGP邻居的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · Invalid JSON format：无效的JSON格式 · The service is disabled：服务未启动 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Invalid parameter：无效参数 · Unknown internal server error：未知的内部服务器错误 · A name is required for the BGP instance：BGP实例的名称不允许为空 · A tenant ID is required：租户ID不允许为空 · A router ID is required for the BGP instance：BGP实例的Router ID不允许为空 · Specify either a source IP address or an external subnet ID：指定源IP地址和外部子网ID只允许填一个 · A local AS number is required：本地AS号不允许为空 · Invalid local AS number：无效的本地AS号 · Invalid IP version：无效的IP版本 · The IP address of the BGP peer must be the same version as the source IP address：BGP对等体的IP地址必须和源IP地址版本一致 · An AS number is required for the BGP peer：BGP对等体的AS号不允许为空 · The AS number of the BGP peer is invalid：BGP对等体的AS号无效 · The BGP peer UUID already exists：指定的BGP对等体ID已存在 · An IP address is required for the BGP peer：BGP对等体的IP地址不允许为空 · The source IP address or external subnet ID is invalid：源IP地址或者外部子网ID无效 · A name is required：未指定name · A UUID is required for the BGP peer：BGP对等体的ID不允许为空 · An external subnet ID is required：外部子网的ID不允许为空 · An IP version is required：IP版本不允许为空 · The IP address of the BGP peer is invalid：无效的BGP对等体的IP地址 · An IP address is required for the BGP peer：BGP对等体的IP地址不允许为空 · An AS number is required for the BGP peer：BGP对等体的AS号不允许为空 · The specified BGP peer has already been bound to the vRouter：指定的虚拟路由器下已经绑定了BGP对等体 · The specified subnet is not an external subnet：指定的子网不是外网类型 · The connection type of the external network must be Directly Connected：外部网络的模式必须为独享模式 · The external subnet type must be VLAN：外网子网的类型必须是VLAN类型 · The specified external subnet has not been bound to a vRouter：指定UUID的外网子网没有绑定虚拟路由器 · The vRouter to which the external subnet is bound is different from the vRouter specified by the router_id parameter：外网子网对应的虚拟路由器和router_id对应的虚拟路由器不一致 · When the HA mode is multi-active, you must specify two different source IP addresses for the BGP neighbor：HA部署模式为多活时，BGP邻居的源IP地址最多只能配置两个，且不能相同 · You have no privilege to perform this operation：用户无权限执行此操作 · When the Network Cloud feature is disabled, you cannot create BGP peers：网络云开关关闭时，不允许创建BGP邻居 · BGP peer with the specified IP address already exists：指定BGP对等体的IP地址已存在 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · Up to 255 characters, case sensitive：参数不能超过255个字符，区分大小写 · The password is case sensitive and cannot exceed 80 characters. Only letters, digits, and special characters except for question marks (?) are supported：密码长度最长80个字符，区分大小写，仅支持英文、数字和特殊字符（英文问号除外） · When you configure a border interface in a non-network cloud scenario, you must specify a minimum of one external subnet：非网络云场景外部子网不能为空 · When you configure a BGP neighbor in a non-network cloud scenario, you cannot specify a source IP：非网络云场景不允许指定源IP · In a non-network cloud scenario, you cannot disable BGP route advertisement to the controller：非网络云场景，不支持配置抑制BGP路由发布到DC开关 · In a non-network cloud scenario, you cannot bind both a BGP peer and a BGP neighbor to a vRouter if the peer IP address configured for the BGP neighbor is the same as the neighbor IP/network address configured for the BGP peer：非网络云场景，同一个虚拟路由器下，BGP邻居的对端对等体IP与BGP对等体IP地址/网段不能重叠 · BFD cannot be enabled in the network cloud scenario：网络云场景下，不支持开启BFD探测功能 · In the network cloud scenario, BGP neighbors do not support binding interconnect interfaces：网络云场景BGP邻居不支持绑定互联接口 · You must bind an interconnect interface or an external subnet to a BGP neighbor：BGP邻居必须绑定外部子网和互联接口其中之一 · The specified interconnect interface does not exist：互联接口不存在 · When you bind an interconnect interface to a BGP neighbor, make sure the interconnect interface has a border gateway binding：BGP邻居绑定的互联接口未绑定出口网关 · When you bind an interconnect interface to a BGP neighbor, make sure the border gateway associated with that interconnect interface has a vRouter binding：BGP邻居绑定的互联接口关联的出口网关未绑定虚拟路由器 |
|
关键字 |
UPDATE_BGP_NEIGHBOR_OP |
|
日志内容 |
Updated BGP neighbor: $1. |
|
参数解释 |
$1：BGP邻居信息 |
|
举例 |
Updated BGP neighbor: ID: [c962169b-1a71-449c-8407-a36e938916ec] Router ID: [94e28779-629f-4159-a7c6-261a57241658] Tenant ID: [28ebfffc-865f-4784-a7d5-33938daf8db1] BGP neighbor description:[] IP version:[4] Local AS number:[30] BGP neighbor name:[tt] Peer AS number:[31] Peer IP address:[31.1.1.1] Source IP: [[30.0.0.1]] Suppress:[false] Cloud region name: region auth:[BgpNeighborAuth [authType=AuthType{type=2, typeName='password'}]] bfd:[false] |
|
日志说明 |
用户进行了修改BGP邻居的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · Invalid JSON format：无效的JSON格式 · The service is disabled：服务未启动 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Invalid parameter：无效参数 · Unknown internal server error：未知的内部服务器错误 · The BGP peer UUID does not exist：BGP对等体的ID不存在。 · The BGP peer UUID cannot be modified：BGP对等体的ID不允许修改。 · The tenant ID cannot be modified：租户的ID不允许修改。 · The router ID of the BGP instance cannot be modified：BGP实例的Router ID不允许修改。 · The local AS number cannot be modified：本地AS号不允许修改。 · The IP version cannot be modified：IP版本不允许修改。 · The IP address of the BGP peer cannot be modified：BGP对等体的IP地址不允许修改。 · The AS number of the BGP peer cannot be modified：BGP对等体的AS号不允许修改。 · You have no privilege to perform this operation：用户无权限执行此操作 · When the Network Cloud feature is disabled, you cannot edit BGP peers：网络云开关关闭时，不允许修改BGP邻居 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · You cannot edit or delete the cloud region name：云区域名称不允许修改或删除 · Up to 255 characters, case sensitive：参数不能超过255个字符，区分大小写 · The password is case sensitive and cannot exceed 80 characters. Only letters, digits, and special characters except for question marks (?) are supported：密码长度最长80个字符，区分大小写，仅支持英文、数字和特殊字符（英文问号除外） · When you configure a border interface in a non-network cloud scenario, you must specify a minimum of one external subnet：非网络云场景外部子网不能为空 · When you configure a BGP neighbor in a non-network cloud scenario, you cannot specify a source IP：非网络云场景不允许指定源IP · In a non-network cloud scenario, you cannot disable BGP route advertisement to the controller：非网络云场景，不支持配置抑制BGP路由发布到DC开关 · In a non-network cloud scenario, you cannot bind both a BGP peer and a BGP neighbor to a vRouter if the peer IP address configured for the BGP neighbor is the same as the neighbor IP/network address configured for the BGP peer：非网络云场景，同一个虚拟路由器下，BGP邻居的对端对等体IP与BGP对等体IP地址/网段不能重叠 · BFD cannot be enabled in the network cloud scenario：网络云场景下，不支持开启BFD探测功能 · You cannot change the interconnect interface binding of a BGP neighbor：BGP邻居绑定的互联接口不允许修改 |
|
关键字 |
DELETE_BGP_NEIGHBOR_OP |
|
日志内容 |
Deleted BGP neighbor: $1. |
|
参数解释 |
$1：BGP邻居的ID |
|
举例 |
Deleted BGP neighbor: c962169b-1a71-449c-8407-a36e938916ec |
|
日志说明 |
用户进行了删除BGP邻居的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · Invalid JSON format：无效的JSON格式 · The service is disabled：服务未启动 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Invalid parameter：无效参数 · Unknown internal server error：未知的内部服务器错误 · The BGP peer UUID does not exist：BGP对等体的ID不存在 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
CREATE_PHYSICAL_NETWORK_INTERFACE_OP |
|
日志内容 |
Created physical network interface: $1. |
|
参数解释 |
$1：外网出口信息 |
|
举例 |
Created physical network interface: ID: [586682ac-8f9b-4016-a03e-f879213102cd] Device ID: [e62b5d9a-b9e3-44d5-9e1e-9f53d350a7f8] Port name: [GigabitEthernet1/0/1] Segments : [ Segment ID : [100] IP ranges: [26.0.0.0/24] |
|
日志说明 |
用户进行了创建外网出口的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · Invalid JSON format：无效的JSON格式 · The service is disabled：服务未启动 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Invalid parameter：无效参数 · Unknown internal server error：未知的内部服务器错误 · The border interface name already exists：指定名称的外网出口已存在 · The border interface name is required：未指定外网出口名称 · The NE doesn't exist：设备不存在 · The border interface device is not gateway：外网出口绑定的设备不是网关设备 · The border interface port name already exists：外网出口端口名称已存在 · The border interface segments is required：未指定外网出口的segments · The border interface port name is required：未指定外网出口的端口名称配置 · Invalid border interface name：无效的外网出口名称 · Invalid border interface port name：无效的外网出口端口名称 · Invalid border interface name：指定的端口名称不允许修改 · You have no privilege to perform this operation：用户无权限执行此操作 · When the Network Cloud feature is disabled, you cannot create border interfaces：网络云开关关闭时，不允许创建外网出口 · Check the directly connected external networks and the border interfaces in the device group bound to this vRouter with the same segment ID. Make sure only one primary IPv4 address exists for the border interface：虚拟路由器绑定的设备组中的外网出口和该虚拟路由器下的独享型外网子网使用相同Segment ID时，最多只允许有一个主IP · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · A physical device already exists with the specified name：指定名称的物理设备已存在 · You cannot use a physical interface as a border interface in a non-network cloud scenario：非网络云场景不允许配置物理接口 · In a non-network cloud scenario, you cannot specify a border interface for the device group bound to a shared external network：非网络云场景，共享型外部网络不允许指定设备组的外网出口 · In a non-network-cloud scenario, specify a physical interface if the router interface feature is enabled：非网络云场景，路由接口开关开启，需配置物理接口 · In a non-network-cloud scenario, you cannot specify a physical interface if the router interface feature is disabled：非网络云场景，路由接口开关关闭，不允许配置物理接口 |
|
关键字 |
UPDATE_PHYSICAL_NETWORK_INTERFACE_OP |
|
日志内容 |
Updated physical network interface: $1. |
|
参数解释 |
$1：外网出口信息 |
|
举例 |
ID: [586682ac-8f9b-4016-a03e-f879213102cd] Device ID: [e62b5d9a-b9e3-44d5-9e1e-9f53d350a7f8] Port name: [GigabitEthernet1/0/1] modSegments : [ Segment ID : [100] IP ranges: [26.0.0.0/24] |
|
日志说明 |
用户进行了修改外网出口的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · Invalid JSON format：无效的JSON格式 · The service is disabled：服务未启动 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Invalid parameter：无效参数 · Unknown internal server error：未知的内部服务器错误 · You have no privilege to perform this operation：用户无权限执行此操作 · When the Network Cloud feature is disabled, you cannot edit border interfaces：网络云开关关闭时，不允许修改外网出口 · Check the directly connected external networks and the border interfaces in the device group bound to this vRouter with the same segment ID. Make sure only one primary IPv4 address exists for the border interface：虚拟路由器绑定的设备组中的外网出口和该虚拟路由器下的独享型外网子网使用相同Segment ID时，最多只允许有一个主IP · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · A physical device already exists with the specified name：指定名称的物理设备已存在 · You cannot use a physical interface as a border interface in a non-network cloud scenario：非网络云场景不允许配置物理接口 · In a non-network cloud scenario, you cannot specify a border interface for the device group bound to a shared external network：非网络云场景，共享型外部网络不允许指定设备组的外网出口 · The segment ID does not exist：指定的Segment ID不存在 · The router interface feature cannot be edited：路由接口开关不允许修改 |
|
关键字 |
DELETE_PHYSICAL_NETWORK_INTERFACE_OP |
|
日志内容 |
Deleted physical network interface: $1. |
|
参数解释 |
$1：外网出口的ID |
|
举例 |
Deleted physical network interface: 23f1465b-574d-4a51-8ff5-59041ae19467. |
|
日志说明 |
用户进行了删除物理网络端口的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · Invalid JSON format：无效的JSON格式 · The service is disabled：服务未启动 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Invalid parameter：无效参数 · Unknown internal server error：未知的内部服务器错误 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
CREATE_CLOUD_PL_OP |
|
日志内容 |
Created cloud private line:$1 |
|
参数解释 |
$1：云专线信息 |
|
举例 |
Created cloud private line: UUID:[a31eb312-012e-4ecf-826c-76c69772cbba] Router_ID:[a8c10620-460d-4351-b8f8-98983fa65abe] Cloud private line CIDRs:[[33.23.23.0/24]] IP_address:[23.23.23.23] Subnet mask:[255.255.255.0] Gateway_IP:[23.23.23.2] VLAN_ID:90 |
|
日志说明 |
用户进行了创建云专线的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · Invalid parameter.：无效的配置参数 · The virtual router doesn't exist：虚拟路由器不存在 · The VLAN ID is already in a VLAN pool：VLAN ID不能在已创建的VLAN池范围内 · Invalid IP address：无效的IP地址 · Invalid subnet mask：无效的子网掩码 · The VLAN ID is invalid or out of range：VLAN ID无效或者超出范围 · The VLAN ID is already assigned to a cloud private line：VLAN ID已经被其他云专线使用 · The local network has already been bound to the vRouter：本地网段地址已与该虚拟路由器绑定 · The CIDR already exists：CIDR已存在 · The local IP address has already been bound to the vRouter：本端IP地址已经被虚拟路由器绑定。 · Invalid subnet：无效子网 · You have no privilege to perform this operation：用户无权限执行此操作 · Failed to create the cloud private line, because the specified vRouter is already bound to a service leaf firewall：指定的虚拟路由器已绑定Service Leaf防火墙，不支持创建云专线 |
|
关键字 |
UPDATE_CLOUD_PL_OP |
|
日志内容 |
Updated cloud private line:$1 |
|
参数解释 |
$1：云专线信息 |
|
举例 |
Updated cloud private line: UUID:[a31eb312-012e-4ecf-826c-76c69772cbba] Router_ID:[a8c10620-460d-4351-b8f8-98983fa65abe] Cloud private line CIDRs:[[33.23.23.0/24]] IP_address:[23.23.23.23] Subnet mask:[255.255.255.0] Gateway_IP:[23.23.23.2] VLAN_ID:90 |
|
日志说明 |
用户进行了修改云专线的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · Invalid parameter.：无效的配置参数 · The virtual router doesn't exist：虚拟路由器不存在 · The VLAN ID is already in a VLAN pool：VLAN ID不能在已创建的VLAN池范围内 · Invalid IP address：无效的IP地址 · Invalid subnet mask：无效的子网掩码 · The VLAN ID is invalid or out of range：VLAN ID无效或者超出范围 · The VLAN ID is already assigned to a cloud private line：VLAN ID已经被其他云专线使用 · The local network has already been bound to the vRouter：本地网段地址已与该虚拟路由器绑定 · The CIDR already exists：CIDR已存在 · The local IP address has already been bound to the vRouter：本端IP地址已经被虚拟路由器绑定。 · Invalid subnet：无效子网 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_CLOUD_PL_OP |
|
日志内容 |
Deleted cloud private line:$1. |
|
参数解释 |
$1：云专线的ID |
|
举例 |
Deleted cloud private line:a31eb312-012e-4ecf-826c-76c69772cbba |
|
日志说明 |
用户进行了删除云专线的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · Invalid JSON format：无效的JSON格式 · The service is disabled：服务未启动 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Invalid parameter：无效参数 · Unknown internal server error：未知的内部服务器错误 · The cloud private line does not exist：云专线不存在 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_MULTICAST_OP |
|
日志内容 |
Created multicast: $1. |
|
参数解释 |
$1：L3组播信息 |
|
举例 |
Created multicast: LogicMulticastConfig [ id=68dafdfe-b2eb-4be5-9554-9b184d30dec1, name=test2, ipVersion=IPv4, rpAddress=2.3.5.4, vrouterId=636d12f7-700a-4c3f-a079-706a54b1b346, mdtConfig=MdtConfig [ defaultGroup=null, defaultGroupAuto=false, dataGroup=null, dataGroupAuto=false, autoDataNUm=null, sourcePort=null, dataDelay=null, aclId=null, sourceActive=false ], pimTemplateConfig=PimTemplateConfig [ protocol=PIM-SM, helloInterval=null, helloHoldtime=null, joinPruneInterval=null, joinPruneHoldtime=null, lanDelay=null, overrideInterval=null, passive=false, ssmPolicy=null ], pimPolicyConfig=PimPolicyConfig [ neighborPolicy=null, joinPolicy=null ], igmpTemplateConfig=IgmpTemplateConfig [ version=V2, robustCount=null, queryInterval=null, maxResponseTime=null, lastMemberQueryInterval=null, otherQuerierPresent=null, ssmMappingId=null, proxyEnable= true ], igmpPolicyConfig=IgmpPolicyConfig [groupPolicy=null], multicastResources=[], externalVpn=false, external_network_id=d3d2ae8a-9081-4177-9091-8a15ba6ad8bg, ext_segment_uuid=646d12f7-700a-4c3f-a079-706a54b1b346 ] |
|
日志说明 |
用户进行了创建L3组播信息的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · Invalid parameter：无效参数 · The multicast already exist：指定的L3组播已存在 · The name is required：组播名称是需要的 · Invalid name：名称非法 · The router is required：虚拟路由器是需要的 · The VSM service is not available：VSM服务不可用 · The specified router does not exist：指定的虚拟路由器不存在 · The vrouter does not enable multicast：指定的虚拟路由器未使能组播 · The multicast with the name is already exist：指定名称的虚拟路由器已存在 · The multicast with the vrouter is already exist：指定虚拟路由器的L3组播已存在 · The multicast network feature is not enabled for the external network：外部网络未使能组播网络 · You must select a network segment, because the selected external network is enabled with network segmentation：指定的外部网络已开启网络分段，网络分段ID不能为空 · The external network has been bound to a Layer 3 multicast network：该外部网络已绑定了其他的L3组播 · The specified external network does not exist：指定的外部网络不存在 · The specified network segment does not exist：指定的网络分段不存在 · The network segment is not bound to the external network：网络分段和外部网络不是绑定关系 · Invalid IP address：非法IP · The RP address is required：RP地址必需 · Invalid pim protocol：PIM协议非法 · Invalid default group：默认组非法 · The default group is null, but data group not null：默认组为空时，数据组不为空 · Invalid data group：数据组非法 · The switchover delay is out of range：切换延时超过取值范围 · The ACL doesn't exist：指定的策略不存在 · The mdt ACL is must advanced ACL：MDT策略需是高级类型 · The SSM policy cannot has with PIM-SM protocol：PIM-SM时，SSM组播组范围不可以赋值 · The hello interval is out of range：Hello报文发送频率超过取值范围 · The hello holdtime is out of range：Hello报文保持时间超过取值范围 · The join or prune interval is out of range：Join/Prune报文发送时间超过取值范围 · The join or prune holdtime is out of range：Join/Prune报文保持时间超过取值范围 · The propagation delay is out of range：传输延时时间超过取值范围 · The override interval is out of range：剪枝否决时间超过取值范围 · The SSM policy ACL must be basic ACL：SSM组播组策略需为基础策略 · The neighbor policy ACL is must basic ACL：邻居过滤策略需为基础策略 · The join policy ACL is must basic ACL：Join信息过滤策略需为基础策略 · The IGMP version is invalid：IGMP版本非法 · The SSM mapping is not null when IGMP version is V3：IGMP版本为V3时，SSM mapping不填 · The IGMP querier’s robustness variable is out of range：查询器健壮系数超过取值范围 · The IGMP query interval is out of range：普通组查询报文发送频率超过取值范围 · The IGMP max response time is out of range：普通组查询报文最大时间超过取值范围 · The IGMP last member query interval is out of range：IGMP特定组/源组查询报文发送时间间隔超过取值范围 · The other querier present time is out of range：其它IGMP查询器的存活时间超过取值范围 · The SSM mapping doesn't exist：指定的SSM mapping策略不存在 · The default group and data group is overlap：默认组和数据组重叠 · The default group or data group conflicts with before or multicast pool：默认组、数据组不能与已有的组播MDT、BUM组播复制中的组播组地址或组播地址池重复 · The multicast address pool does not exist：组播地址池不存在 · The multicast address pool does not have enough addresses for allocation：组播地址池的IP地址不足 · Cannot specify the default group when auto default group allocation is enabled：使能自动分配默认组后，不允许手动配置默认组 · Invalid number of data groups to be automatically allocated：无效的自动分配数据组数目 · The other querier present time must be greater than the general query interval：其它IGMP查询器的存活时间应大于普遍组查询报文发送频率 · The general query interval must be greater than the max response time.：普遍组查询报文发送频率应大于普遍组查询报文最大响应时间 · Cannot set the max response time when the IGMP version is v1：IGMP协议为V1版本时，普遍组查询报文最大响应时间不填 · Cannot set the last member query interval when the IGMP version is v1：IGMP协议为V1版本时，IGMP最后组成员查询间隔不填 · Cannot set the other querier present time when the IGMP version is v1：IGMP协议为V1版本时，其它IGMP查询器的存活时间不填 · The general query interval must be less than the default value for the other querier present time (255)：普遍组查询报文发送频率取值必须小于其它IGMP查询器存活时间默认值(255) · The other querier present time must be greater than the default general query interval (125)：其它IGMP查询器的存活时间必须大于普遍组查询报文发送频率默认值(125) · The general query interval must be greater than the default max response time (10)：普遍组查询报文发送频率必须大于普遍组查询报文最大响应时间默认值(10) · The max response time must be less than the default general query interval (125)：普遍组查询报文最大响应时间必须小于普遍组查询报文发送频率默认值(125) · The SSM Mapping field must be empty if PIM-SM is used：当PIM协议为PIM-SM时，SSM Mapping必须为空 · The IGMP version must be v3 if PIM-SM is used：当PIM协议为PIM-SSM时，IGMP版本必须为V3 · You have no privilege to perform this operation：用户无权限执行此操作 · The PIM-SM domain border cannot be enabled when external services are disabled：当外网业务关闭时，pim边界开关不允许开启 · The value for the PIM-SM domain border field can only be true or false：PIM边界网关取值必须为true或false · You must disable the publishing multicast source information by default option if auto default group assignment is disabled and no default group is specified：当不自动分配默认组且未配置默认组时，默认发布组播源信息开关必须关闭 · You cannot select an network segment when the external network service is disabled：外网业务关闭时，网络分段取值必须为空 · The specified network segment has already been bound to another Layer 3 multicast network：绑定该网络分段的L3组播已存在 · You cannot edit the ID of the network segment：网络分段ID不允许修改 · You cannot edit the ID of the external network：外部网络ID不允许修改 · You cannot select an external network when the external network service is disabled：外网业务关闭时，外部网络取值必须为空 · Please select an external network：未指定外部网络 · You cannot enable IGMP proxying when external services are enabled：当外网业务开启时，IGMP代理开关不允许开启 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · Cannot configure the MLD protocol and MLD policy for IPv4 multicast：IPv4组播不支持MLD协议和策略 · Cannot configure IGMP protocol and IGMP policy for IPv6 multicast：IPv6组播不支持IGMP协议和策略 · Invalid multicast type.：无效的组播版本 · Layer 3 multicast network bound to the same VPN must have the same default group：绑定相同VPN的L3组播必须配置相同的默认组 · Layer 3 multicast network bound to the same VPN must have the same source port：绑定相同VPN的L3组播必须配置相同的源端口 · The multicast policy bound by MDT is invalid：MDT绑定的组播策略非法 · The MLD querier's robustness variable is out of range：MLD查询健壮系数超出取值范围 · The MLD general query interval is out of range：MLD普遍组查询报文的发送时间间隔超出取值范围 · The MLD max response time is out of range：MLD普遍组查询报文的最大响应时间超出取值范围 · The MLD last member query interval is out of range：MLD最后组成员查询间隔 · The MLD other querier present time is out of range：其它MLD查询器的存活时间超出取值范围 · The MLD version is invalid：MLD版本须为V1或V2 · Please enable IPv6 multicast capabilities for the vNetwork：指定的虚拟链路层网络必须使能IPv6组播网络 · The IPv6 multicast network feature is not enabled for the external network：外部网络未使能IPv6组播网络 · The MLD version must be v2 if PIM-SSM is used：当PIM协议为PIM-SSM时，MLD版本必须为V2 · MDT cannot be configured, because external route redistribution has been disabled for the specified external network：指定的外部网络未开启引入外网路由，MDT不允许配置 |
|
关键字 |
UPDATE_MULTICAST_OP |
|
日志内容 |
Updated multicast: $1. |
|
参数解释 |
$1：L3组播信息 |
|
举例 |
Updated multicast: LogicMulticastConfig [ id=68dafdfe-b2eb-4be5-9554-9b184d30dec1, name=test2, rpAddress=2.3.5.4, vrouterId=636d12f7-700a-4c3f-a079-706a54b1b346, mdtConfig=MdtConfig [ defaultGroup=null, defaultGroupAuto=false, dataGroup=null, dataGroupAuto=false, autoDataNUm=null, sourcePort=null, dataDelay=null, aclId=null, sourceActive=false ], pimTemplateConfig=PimTemplateConfig [ protocol=PIM-SM, helloInterval=null, helloHoldtime=null, joinPruneInterval=null, joinPruneHoldtime=null, lanDelay=null, overrideInterval=null, passive=false, ssmPolicy=null ], pimPolicyConfig=PimPolicyConfig [ neighborPolicy=null, joinPolicy=null ], igmpTemplateConfig=IgmpTemplateConfig [ version=V2, robustCount=null, queryInterval=null, maxResponseTime=null, lastMemberQueryInterval=null, otherQuerierPresent=null, ssmMappingId=null, proxyEnable= true ], igmpPolicyConfig=IgmpPolicyConfig [groupPolicy=null], multicastResources=[], externalVpn=false ] |
|
日志说明 |
用户进行了更新L3组播的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · The multicast id is required when put：修改时L3组播ID必需 · The multicast name cannot be modified：L3组播名称不允许被修改 · The vrouter id cannot be modified：虚拟路由器ID不允许被修改 · Invalid IP address：非法IP · The RP address is required：RP地址必需 · Invalid pim protocol：PIM协议非法 · Invalid default group：默认组非法 · The default group is null, but data group not null：默认组为空时，数据组不为空 · Invalid data group：数据组非法 · The switchover delay is out of range：切换延时超过取值范围 · The ACL doesn't exist：指定的策略不存在 · The mdt ACL is must advanced ACL：MDT策略需是高级类型 · The SSM policy cannot has with PIM-SM protocol：PIM-SM时，SSM组播组范围不可以赋值 · The hello interval is out of range：Hello报文发送频率超过取值范围 · The hello holdtime is out of range：Hello报文保持时间超过取值范围 · The join or prune interval is out of range：Join/Prune报文发送时间超过取值范围 · The join or prune holdtime is out of range：Join/Prune报文保持时间超过取值范围 · The propagation delay is out of range：传输延时时间超过取值范围 · The override interval is out of range：剪枝否决时间超过取值范围 · The SSM policy ACL must be basic ACL：SSM组播组策略需为基础策略 · The neighbor policy ACL is must basic ACL：邻居过滤策略需为基础策略 · The join policy ACL is must basic ACL：Join信息过滤策略需为基础策略 · The IGMP version is invalid：IGMP版本非法 · The SSM mapping is not null when IGMP version is V3：IGMP版本为V3时，SSM mapping不填 · The IGMP querier’s robustness variable is out of range：查询器健壮系数超过取值范围 · The IGMP query interval is out of range：普通组查询报文发送频率超过取值范围 · The IGMP max response time is out of range：普通组查询报文最大时间超过取值范围 · The IGMP last member query interval is out of range：IGMP特定组/源组查询报文发送时间间隔超过取值范围 · The other querier present time is out of range：其它IGMP查询器的存活时间超过取值范围 · The SSM mapping doesn't exist：指定的SSM mapping策略不存在 · The default group and data group is overlap：默认组和数据组重叠 · The multicast doesn't exist：指定的L3组播不存在 · The multicast name cannot be modified：L3组播名称不允许修改 · Invalid source port：无效的源端口 · Failed to change the PIM protocol. The receiver end and the multicast source must use the same PIM protocol：修改PIM协议失败。接收端组播的PIM协议必须和组播源端的PIM协议相同 · You must specify a distributed RP, because the Layer 3 multicast network is used by an MSDP peer：指定的L3组播组播已被MSDP对等体使用，分布式RP不能为空 · Please specify a default group and a source port：指定的默认组或源端口不能为空 · If you do not specify a data group, you must leave the switchover delay and multicast policy empty：当数据组为空时,切换延时和组播策略都必须为空 · The default group or data group conflicts with before or multicast pool：默认组、数据组不能与已有的组播MDT、BUM组播复制中的组播组地址或组播地址池重复 · The multicast address pool does not exist：组播地址池不存在 · The multicast address pool does not have enough addresses for allocation：组播地址池的IP地址不足 · Cannot specify the default group when auto default group allocation is enabled：使能自动分配默认组后，不允许手动配置默认组 · Invalid number of data groups to be automatically allocated：无效的自动分配数据组数目 · Cannot edit the status of external services for an existing Layer 3 multicast network：外网业务的开关不允许修改 · The other querier present time must be greater than the general query interval：其它IGMP查询器的存活时间应大于普遍组查询报文发送频率 · The general query interval must be greater than the max response time.：普遍组查询报文发送频率应大于普遍组查询报文最大响应时间 · Cannot set the max response time when the IGMP version is v1：IGMP协议为V1版本时，普遍组查询报文最大响应时间不填 · Cannot set the last member query interval when the IGMP version is v1：IGMP协议为V1版本时，IGMP最后组成员查询间隔不填 · Cannot set the other querier present time when the IGMP version is v1：IGMP协议为V1版本时，其它IGMP查询器的存活时间不填 · The general query interval must be less than the default value for the other querier present time (255)：普遍组查询报文发送频率取值必须小于其它IGMP查询器存活时间默认值(255) · The other querier present time must be greater than the default general query interval (125)：其它IGMP查询器的存活时间必须大于普遍组查询报文发送频率默认值(125) · The general query interval must be greater than the default max response time (10)：普遍组查询报文发送频率必须大于普遍组查询报文最大响应时间默认值(10) · The max response time must be less than the default general query interval (125)：普遍组查询报文最大响应时间必须小于普遍组查询报文发送频率默认值(125) · The SSM Mapping field must be empty if PIM-SM is used：当PIM协议为PIM-SM时，SSM Mapping必须为空 · The IGMP version must be v3 if PIM-SM is used：当PIM协议为PIM-SSM时，IGMP版本必须为V3 · You have no privilege to perform this operation：用户无权限执行此操作 · The PIM-SM domain border cannot be enabled when external services are disabled：当外网业务关闭时，pim边界开关不允许开启 · The value for the PIM-SM domain border field can only be true or false：PIM边界网关取值必须为true或false · The Layer 3 multicast network and its multicast network interfaces must run the same PIM protocol：L3组播和组播接口的PIM协议类型要保持一致 · You must disable the publishing multicast source information by default option if auto default group assignment is disabled and no default group is specified：当不自动分配默认组且未配置默认组时，默认发布组播源信息开关必须关闭 · You cannot enable IGMP proxying when external services are enabled：当外网业务开启时，IGMP代理开关不允许开启 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · You cannot edit the multicast type parameter：组播版本不允许修改 · Layer 3 multicast network bound to the same VPN must have the same default group：绑定相同VPN的L3组播必须配置相同的默认组 · Layer 3 multicast network bound to the same VPN must have the same source port：绑定相同VPN的L3组播必须配置相同的源端口 · The multicast policy bound by MDT is invalid：MDT绑定的组播策略非法 · The MLD querier's robustness variable is out of range：MLD查询健壮系数超出取值范围 · The MLD general query interval is out of range：MLD普遍组查询报文的发送时间间隔超出取值范围 · The MLD max response time is out of range：MLD普遍组查询报文的最大响应时间超出取值范围 · The MLD last member query interval is out of range：MLD最后组成员查询间隔 · The MLD other querier present time is out of range：其它MLD查询器的存活时间超出取值范围 · The MLD version is invalid：MLD版本须为V1或V2 · The MLD version must be v2 if PIM-SSM is used：当PIM协议为PIM-SSM时，MLD版本必须为V2 · MDT cannot be configured, because external route redistribution has been disabled for the specified external network：指定的外部网络未开启引入外网路由，MDT不允许配置 |
|
关键字 |
DELETE_MULTICAST_OP |
|
日志内容 |
Deleted multicast: $1. |
|
参数解释 |
$1：L3组播的UUID |
|
举例 |
Deleted multicast: 694aae52-b4b3-48a1-9829-6e4ba6673cf5. |
|
日志说明 |
用户进行了删除L3组播的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置正在恢复过程中 · Invalid license：无效的License · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · The specified replacement task does not exist：指定的替换设备任务不存在 · Invalid parameter：非法参数 · You cannot delete this Layer 3 multicast network, because it is used by an MSDP peer：L3组播被MSDP对等体使用，不允许删除 · You cannot delete the Layer 3 multicast network, because it has multicast source bindings：指定的L3组播已绑定组播源，不允许删除 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
CREATE_LAYER_2_MULTICAST_OP |
|
日志内容 |
Created layer 2 multicast network: $1. |
|
参数解释 |
$1：L2组播信息 |
|
举例 |
Created layer 2 multicast network: L2MulticastConfig { id=7cac7c86-8338-4936-8f41-49564c0524e4, name=1, ipVersion=IPv4, vNetworkId=107790d4-8d6e-4005-94a2-0dbcbc6b0438, igmpSnoopingConfig=IGMPSnoopingConfig { dropUnknown=true, querierElection=true, generalSourceIp=1.2.3.6 }, pimSnoopingConfig=PIMSnoopingConfig {enable=true} } |
|
日志说明 |
用户进行了创建L2组播信息的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · The Layer 2 multicast network already exists：指定的L2组播已存在 · The name is required：名称必填 · Invalid name：名称非法 · The VSM service is not available：VSM服务不可用 · Please specify a vNetwork：虚拟链路层网络不能为空 · The vNetwork does not exist：指定的虚拟链路层网络不存在 · Please enable multicast capabilities for the vNetwork：指定的虚拟链路层网络必须使能组播网络 · The vNetwork cannot be an external network：虚拟链路层网络不能为外部网络 · A Layer 2 multicast network already exists with the specified name：指定名称的L2组播已存在 · A Layer 2 multicast network already exists with the specified vNetwork：指定虚拟链路层网络的L2组播已存在 · Invalid source IP for IGMP general queries：无效的IGMP普遍组查询报文源IP · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · IPv6 Layer 2 multicast does not support IGMP snooping configuration：IPv6版本的L2组播不支持配置IGMP Snooping · IPv4 Layer 2 multicast does not support MLD snooping configuration：IPv4版本的L2组播不支持配置MLD Snooping · The specified vNetwork must support IPv6 multicast network：指定的虚拟链路层网络必须使能IPv6组播网络 · Invalid multicast type：无效的组播版本 |
|
关键字 |
UPDATE_LAYER_2_MULTICAST_OP |
|
日志内容 |
Updated layer 2 multicast network: $1. |
|
参数解释 |
$1：L2组播信息 |
|
举例 |
Updated layer 2 multicast network: L2MulticastConfig { id=7cac7c86-8338-4936-8f41-49564c0524e4, name=1, vNetworkId=107790d4-8d6e-4005-94a2-0dbcbc6b0438, igmpSnoopingConfig=IGMPSnoopingConfig { dropUnknown=true, querierElection=true, generalSourceIp=1.2.3.6 }, pimSnoopingConfig=PIMSnoopingConfig {enable=true} } |
|
日志说明 |
用户进行了更新L2组播的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · You have no privilege to perform this operation：用户无权限执行此操作 · Invalid JSON format：无效的JSON格式 · The Layer 2 multicast network does not exist：L2组播不存在 · Please specify an L2 multicast network ID：L2组播ID不能为空 · You cannot edit the name of the Layer 2 multicast network：L2组播名称不允许修改 · Cannot edit the ID of the vNetwork：虚拟链路层网络ID不能被修改 · Invalid source IP for IGMP general queries：无效的IGMP普遍组查询报文源IP · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · You cannot edit the multicast type parameter：组播版本不允许修改 · IPv6 Layer 2 multicast does not support IGMP snooping configuration：IPv6版本的L2组播不支持配置IGMP Snooping · IPv4 Layer 2 multicast does not support MLD snooping configuration：IPv4版本的L2组播不支持配置MLD Snooping |
|
关键字 |
DELETE_LAYER_2_MULTICAST_OP |
|
日志内容 |
Deleted layer 2 multicast network: $1. |
|
参数解释 |
$1：L2组播的UUID |
|
举例 |
Deleted layer 2 multicast network: 4fee8fa0-6588-46ca-9378-ce1ac4757503. |
|
日志说明 |
用户进行了删除L2组播的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · Invalid UUID:parameter：无效的UUID · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
CREATE_ACL_OP |
|
日志内容 |
Created ACL: $1. |
|
参数解释 |
$1：组播策略信息 |
|
举例 |
Created ACL: MulticastAcl [id=7149c617-672f-4c10-9413-7b9243394799, name=acl_basic3, ipVersion=IPv4, desc=null, aclType=BASIC, aclRules=[MulticastAclRule [id=af7ae0c7-d3a9-42f5-bdb6-255b8494084a, aclId=7149c617-672f-4c10-9413-7b9243394799, ruleId=null, sourceIP=19.3.3.3, destinationIP=null, action=PERMIT]]] |
|
日志说明 |
用户进行了创建组播策略信息的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · Invalid acl name：非法的组播策略名称 · The ACL with the same name already exists：同名组播策略已存在 · Invalid description：非法描述信息 · You have no privilege to perform this operation：用户无权限执行此操作 · The specified ACL does not exist：指定的组播策略不存在 · An ACL already exists with the specified ID：指定ID的ACL已存在 · Invalid rule ID：序号不合法 · Duplicate rule ID：存在重复的ACL规则序号 · In the same ACL, you must specify rule IDs for all or none of the rules：相同组播策略下的ACL规则序号必须同时配置或同时不配置 · Invalid multicast type：无效的组播版本 · Duplicated ACL rules exist：存在冲突的ACL规则 |
|
关键字 |
DELETE_ACL_OP |
|
日志内容 |
Deleted ACL: $1. |
|
参数解释 |
$1：组播策略的UUID |
|
举例 |
Deleted ACL: ab498204-5a8d-46cd-b4af-e1740fc2c374. |
|
日志说明 |
用户进行了删除组播策略的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置正在恢复过程中 · Invalid license：无效的License · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · Failed to delete the ACL because it is being used：指定的组播策略正在被使用无法删除 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_ACL_RULE_OP |
|
日志内容 |
Created ACL rule: $1. |
|
参数解释 |
$1：组播策略规则信息 |
|
举例 |
Created ACL: MulticastAcl [id=7149c617-672f-4c10-9413-7b9243394799, name=acl_basic3, ipVersion=Ipv4, desc=null, aclType=BASIC, aclRules=[MulticastAclRule [id=af7ae0c7-d3a9-42f5-bdb6-255b8494084a, aclId=7149c617-672f-4c10-9413-7b9243394799, ruleId=null, sourceIP=19.3.3.3, destinationIP=null, action=PERMIT]]] |
|
日志说明 |
用户进行了创建组播策略信息的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · The ACL for the specified UUID doesn’t exist：指定的组播策略id不存在 · The ACL with the same name already exists：同名组播策略已存在 · The ACL IDs of all rules are not same：组播策略规则对应的组播策略id不相同息 · Invalid source IP address：非法源IP地址 · Invalid destination IP address：非法目的IP地址 · The specified ACL rule already exists：特定的组播策略规则已存在 · The specified ACL rule conflicts with existed rule：特定的组播策略规则与已存在规则冲突 · The ACL rule list parameter contains duplicated rules：组播策略规则列表有重复规则 · The ACL rule number must be in the range of 1 to 1000：组播策略规则数量范围为1~1000 · You have no privilege to perform this operation：用户无权限执行此操作 · Invalid rule ID：序号不合法 · Duplicate rule ID：存在重复的ACL规则序号 · In the same ACL, you must specify rule IDs for all or none of the rules：相同组播策略下的ACL规则序号必须同时配置或同时不配置 · Invalid IP version：IP version非法 |
|
关键字 |
DELETE_ACL_RULE_OP |
|
日志内容 |
Deleted ACL rule: $1. |
|
参数解释 |
$1：组播策略规则的UUID |
|
举例 |
Deleted ACL rule: abdde559-3a97-4984-ac67-e3e0de363fd7. |
|
日志说明 |
用户进行了删除组播策略的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置正在恢复过程中 · Invalid license：无效的License · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_SSM_MAPPING_OP |
|
日志内容 |
Created SSM mapping: $1. |
|
参数解释 |
$1：SSM mapping信息 |
|
举例 |
Created SSM mapping:[ id:178d9370-884a-4538-b75b-51b0a42ffaf5, name:ssm_maapping1, ipVersion:IPv4 Desc:. ] |
|
日志说明 |
用户进行了创建SSM mapping信息的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · Invalid SSM mapping name：非法的SSM mapping名称 · The SSM Mapping name already exists：同名SSM mapping已存在 · Invalid description：非法描述信息 · You have no privilege to perform this operation：用户无权限执行此操作 · A SSM mapping already exists with the specified ID：指定ID的SSM Mapping已存在 · Invalid multicast type：无效的组播版本 |
|
关键字 |
DELETE_SSM_MAPPING_OP |
|
日志内容 |
Deleted SSM mapping: $1. |
|
参数解释 |
$1：SSM mapping的UUID |
|
举例 |
Deleted SSM mapping: 178d9370-884a-4538-b75b-51b0a42ffaf5. |
|
日志说明 |
用户进行了删除SSM mapping的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置正在恢复过程中 · Invalid license：无效的License · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · Failed to delete the SSM Mapping because it is being used：指定的SSM mapping正在被使用无法删除 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_SSM_MAPPING_RULE_OP |
|
日志内容 |
Created SSM mapping rule: $1. |
|
参数解释 |
$1：SSM mapping规则信息 |
|
举例 |
Created SSM mapping rule:[ id:d96b4ede-1781-43f0-8de2-01fb07e78c6a, ssmMappingId:178d9370-884a-4538-b75b-51b0a42ffaf5, SourceIp:192.168.10.10, GroupIp:225.1.1.0/24 ]. |
|
日志说明 |
用户进行了创建SSM mapping规则信息的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · The SSM Mapping does not exist：指定的ssm mapping不存在 · Invalid source IP address：非法源IP地址 · Invalid group ip：非法组播组地址 · The SSM Mapping rule already exists：指定的ssm mapping规则已存在 · The SSM Mapping rule list parameter contains duplicated rules：ssm mapping规则列表包含重复规则 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_SSM_MAPPING_RULE_OP |
|
日志内容 |
Deleted SSM mapping rule: $1. |
|
参数解释 |
$1：SSM mapping规则的UUID |
|
举例 |
Deleted SSM mapping: 178d9370-884a-4538-b75b-51b0a42ffaf5. |
|
日志说明 |
用户进行了删除SSM mapping规则的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置正在恢复过程中 · Invalid license：无效的License · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_MULTICAST_SOURCE_OP |
|
日志内容 |
Created multicast source:$1 |
|
参数解释 |
$1：组播源信息 |
|
举例 |
Created multicast source: MulticastSourceConfig [id=eef1860b-b0b9-467e-a37a-64ee75a8ee83, sourceIp=115.3.2.0/24, groupIp=225.3.3.0/24, vrouterId=e94e8c6a-be65-4008-9ce9-07622a82043c, externalVpn=true, multicastId=567d5dad-ab7d-4adb-94a5-32c917324170, external_network_id=d3d2ae8a-9081-4177-9091-8a15ba6ad8bg, ext_segment_uuid=646d12f7-700a-4c3f-a079-706a54b1b346] |
|
日志说明 |
用户进行了创建组播源信息的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · Invalid UUID:parameter：无效的UUID · Invalid parameter：参数错误 · The vRouter does not enable multicast：虚拟路由器没有使能组播 · The multicast source already exists：指定的组播源已存在 · Please specify the multicast source address：组播源地址不能为空 · Invalid multicast source address：无效的组播源地址 · The multicast doesn't exist：指定的L3组播不存在 · Invalid IP address：无效的IP地址 · Please select a vRouter that has been bound to a Layer 3 multicast network for the multicast source：源端虚拟路由器未绑定L3组播 · The multicast network feature is not enabled for the external network：外部网络未使能组播网络 · You must select a network segment, because the selected external network is enabled with network segmentation：指定的外部网络已开启网络分段，网络分段ID不能为空 · The specified network segment does not exist：指定的网络分段不存在 · A Layer 3 multicast network must be configured for the source end：创建组播源时，源端组播不能为空 · Invalid multicast group address：无效的组播组地址 · The specified vRouter does not exist：指定的虚拟路由器不存在 · The device netconf session doesn't up：该设备的通用netconf通道不是up状态 · Internal server error：内部错误 · Please perform the operation on the active leader：请在主Leader上进行操作 · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · The VSM service is disabled：VSM服务未启动 · The service is disabled：服务未启动 · Please specify the multicast group address：组播组地址不能为空 · Operation failed. The receiver end and the multicast source must use the same PIM protocol：添加组播源失败。接收端组播的PIM协议必须和组播源端的PIM协议相同 · The multicast source addresses in a Layer 3 multicast network can overlap but they must be different：相同组播中的组播源地址可以重叠，但不允许完全相同 · The multicast group addresses in a Layer 3 multicast network can't overlap：相同组播中的组播组地址不可以重叠 · The multicast source's vRouter is required：源端虚拟路由器必选 · The multicast's id is required：L3组播的id必选 · The multicast source address is required：组播源地址必选 · The multicast group address is required：组播组地址必选 · The Layer 3 multicast network and its multicast sources cannot be both used for external network service：组播和组播源不能同时使能外网业务 · You have no privilege to perform this operation：用户无权限执行此操作 · Make sure the specified network segment has been bound to the vRouter：指定的网络分段与对应的虚拟路由器必须是绑定关系 · You cannot select an network segment when the external network service is disabled：外网业务关闭时，外部网络取值必须为空 · You cannot edit the ID of the network segment：网络分段ID不允许修改 · You cannot edit the ID of the external network：外部网络ID不允许修改 · Please select an external network：未指定外部网络 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · The IPv6 multicast network feature is not enabled for the external network：外部网络未使能IPv6组播网络 · For the same Layer 3 multicast network, the multicast source address ranges cannot be the same if the segments bound to the corresponding multicast sources overlap：相同L3组播下，若不同组播源绑定的网络分段间存在重叠的设备，则组播源地址不允许相同 · For the same Layer 3 multicast network, the multicast group address ranges cannot overlap if the segments bound to the corresponding multicast sources overlap：相同L3组播下，若不同组播源绑定的网络分段间存在重叠的设备，则组播组地址不允许重叠 |
|
关键字 |
DELETE_MULTICAST_SOURCE_OP |
|
日志内容 |
Deleted multicast source: $1. |
|
参数解释 |
$1：组播源的UUID |
|
举例 |
Deleted multicast source:a563fa7f-19ef-4fba-908f-37a486027f8b |
|
日志说明 |
用户进行了删除组播源的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置正在恢复过程中 · Invalid license：无效的License · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · Invalid parameter：非法参数 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
CREATE_MULTICAST_MSDP_OP |
|
日志内容 |
Created MSDP peer: $1 |
|
参数解释 |
$1：MSDP对等体信息 |
|
举例 |
Created MSDP peer:MulticastMsdpConfig [ id:[d3d2ae8a-9081-4177-9091-8a15ba6ad8fc] vRouterId:[636d12f7-700a-4c3f-a079-706a54b1b346] name:[msdp] peerAddress:[115.1.1.1] retryInterval:[1] keepAlive:[2] holdTime:[3] msdpAuthType:[simple_password] simplePassword:[xxxx] external_network_id: [d3d2ae8a-9081-4177-9091-8a15ba6ad8bg] ext_segment_uuid: [646d12f7-700a-4c3f-a079-706a54b1b346]] |
|
日志说明 |
用户进行了创建MSDP对等体信息的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · Configuration recovery is in progress：配置正在恢复过程中 · Invalid UUID:parameter：无效的UUID · Invalid parameter：参数错误 · Invalid MSDP peer name：无效的MSDP对等体名称 · The MSDP peer already exists：指定的MSDP对等体已存在 · The vRouter has been bound to another MSDP peer：指定虚拟路由器已绑定其他的MSDP对等体 · A MSDP peer already exists with the specified name：MSDP对等体名称已存在 · Please specify the IP address of the MSDP peer：MSDP对端IP不能为空 · The MSDP connection retry interval must be in the range of 1 to 60 seconds：MSDP对等体连接重试周期的取值范围为1～60秒 · The MSDP peer hold time must be in the range of 1 to 65535 seconds：MSDP对等体会话保持时间的取值范围为1～65535秒 · The MSDP session keepalive interval must be in the range of 1 to 21845 seconds：MSDP对等体会话保活时间的取值范围为1～21845秒 · The MSDP peer hold time must be less than the MSDP session keepalive interval：对等体会话保活时间必须小于对等体会话保持时间 · Please specify both the MSDP peer hold time and the MSDP keepalive interval：对等体会话保活时间和对等体会话保持时间必须同时存在 · Invalid authentication mode for MSDP：无效的MSDP认证方式 · Invalid password：无效的密码 · Please assign an IP address to the loopback interface：LoopBack IP地址不能为空 · The device and the vRouter must be associated with the same VDS：指定的设备和其绑定的虚拟路由器必须属于相同的虚拟分布式交换机 · The MSDP peer does not exist：指定的MSDP对等体不存在 · The Layer 3 multicast network with the external network enabled does not exist.：指定的开启外网业务的L3组播不存在 · You have no privilege to perform this operation：用户无权限执行此操作 · The MSDP session keepalive interval must be in the range of 1 to 21845 seconds：MSDP对等体会话保活时间的取值范围为1～21845秒 · The network segment is already in use：指定的网络分段已被使用 · The network segment is not bound to the external network：网络分段和外部网络不是绑定关系 · You cannot specify an network segment, because network segmentation is not enabled for the external network：指定的外部网络未开启了网络分段，网络分段取值必须为空 · Please select an external network：未指定外部网络 · The specified network segment does not exist：指定的网络分段不存在 · You cannot select the gateway for the MSDP peer, because the gateway uses the same device group as the gateway of an existing MSDP peer：指定的出口网关和已存在的MSDP对等体下出口网关存在相同的设备 · The Layer 3 multicast network with external network disabled does not exist：指定的关闭外网业务的L3组播不存在 · Please specify a distributed RP for the Layer 3 multicast network：指定L3组播的分布式RP不能为空 · The external network is already in use by the MSDP peer：指定的外部网络已被MSDP对等体绑定 · Please specify a border gateway：未指定出口网关 · You must select a vRouter or external network：虚拟路由器和外部网络必须指定一个 · The specified network segment is not bound to the external network：指定的网络分段与外部网络不是绑定关系 · The specified network segment does not exist：指定的网络分段不存在 · The specified external network does not exist：指定的外部网络不存在 · The specified border gateway does not exist：指定的出口网关不存在 · You must select a network segment, because the selected external network is enabled with network segmentation：指定的外部网络已开启网络分段，网络分段ID不能为空 · The border gateway is not bound to the selected vRouter：指定的出口网关未绑定对应的虚拟路由器 · You cannot select both a border gateway and a segmented external network for the MSDP peer：出口网关和开启了网络分段的外部网络不允许同时指定 · Failed to create the MSDP peer, because the vPort enable the firewall or the external network has been bound to a vRouter with a firewall specified as the edge device：虚拟端口开启了防火墙或指定的外部网络已被出口设备为防火墙的虚拟路由器绑定，不允许创建MSDP对等体 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
UPDATE_MULTICAST_MSDP_OP |
|
日志内容 |
Updated MSDP peer: $1. |
|
参数解释 |
$1：MSDP对等体的信息 |
|
举例 |
Updated MSDP peer:MulticastMsdpConfig [ id:[d3d2ae8a-9081-4177-9091-8a15ba6ad8fc] vRouterId:[636d12f7-700a-4c3f-a079-706a54b1b346] name:[msdp] peerAddress:[115.1.1.1] retryInterval:[1] keepAlive:[2] holdTime:[3] msdpAuthType:[simple_password] simplePassword:[xxxx]] |
|
日志说明 |
用户进行了更新MSDP对等体信息的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置正在恢复过程中 · Invalid license：无效的License · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · Invalid parameter：非法参数 · Invalid MSDP peer name：无效的MSDP对等体名称 · A MSDP peer already exists with the specified name：MSDP对等体名称已存在 · The MSDP with the vrouter already exist：指定虚拟路由器的MSDP已存在 · Please specify the IP address of the MSDP peer：MSDP对端IP不能为空 · The MSDP connection retry interval must be in the range of 1 to 60 seconds：MSDP对等体连接重试周期的取值范围为1～60秒 · The MSDP peer hold time must be in the range of 1 to 65535 seconds：MSDP对等体会话保持时间的取值范围为1～65535秒 · The MSDP session keepalive interval must be in the range of 1 to 21845 seconds：MSDP对等体会话保活时间的取值范围为1～21845秒 · The MSDP peer hold time must be less than the MSDP session keepalive interval：对等体会话保活时间必须小于对等体会话保持时间 · Please specify both the MSDP peer hold time and the MSDP keepalive interval：对等体会话保活时间和对等体会话保持时间必须同时存在 · Invalid authentication mode for MSDP：无效的MSDP认证方式 · Invalid password：无效的密码 · Please assign an IP address to the loopback interface：LoopBack IP地址不能为空 · The device and the vRouter must be associated with the same VDS：指定的设备和其绑定的虚拟路由器必须属于相同的虚拟分布式交换机 · The MSDP does not exist：指定的MSDP不存在 · There are non-modifiable fields in this parameter：传入参数中有不可修改字段 · You have no privilege to perform this operation：用户无权限执行此操作 · The MSDP session keepalive interval must be in the range of 1 to 21845 seconds：MSDP对等体会话保活时间的取值范围为1～21845秒 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
DELETE_MULTICAST_MSDP_OP |
|
日志内容 |
Deleted MSDP peer: $1. |
|
参数解释 |
$1：MSDP对等体的UUID |
|
举例 |
Deleted MSDP peer: 0b532731-429c-4ae0-bf01-43c314777017 |
|
日志说明 |
用户进行了删除MSDP对等体的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置正在恢复过程中 · Invalid license：无效的License · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · Invalid parameter：非法参数 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
CREATE_MULTICAST_ANYCAST_RP_OP |
|
日志内容 |
Created Anycast-RP: $1 |
|
参数解释 |
$1：Anycast-RP信息 |
|
举例 |
Created Anycast-RP: MulticastAnycsatRpConfig [id:[636b01e1-35e9-48be-a9d6-a8fc32a84085] vRouterId:[4ab7eb28-415a-4c4e-8e88-c76d2181a9b9] externalNetworkId:[] extSegmentUuid:[] gatewayId:[a0f8da17-e085-438f-bc8b-aeea953ca5cf] name:[1] anycastRp:[13:0:0:0:0:0:0:0] memberAddress:[[12:0:0:0:0:0:0:0, 19:0:0:0:0:0:0:0]]] |
|
日志说明 |
用户进行了创建Anycast-RP信息的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · Configuration recovery is in progress：配置正在恢复过程中 · Invalid UUID:parameter：无效的UUID · Invalid parameter：参数错误 · Invalid Anycast-RP name：无效的Anycast-RP名称 · An Anycast-RP already exists with the specified name：指定名称的Anycast-RP已存在 · An Anycast-RP already exists with the specified ID：指定ID的Anycast-RP已存在。 · Please specify an Anycast-RP：Anycast-RP地址不能为空 · Invalid Anycast-RP address：无效的Anycast-RP地址 · Invalid Anycast-RP member address：无效的Anycast-RP成员地址 · The Anycast-RP address cannot be the same as the IP address of its member：Anycast-RP地址与其成员地址不能相同 · The Anycast-RP member address already exists：Anycast-RP成员地址存在重复地址 · The vRouter has been used by another Anycast-RP：指定的虚拟路由器已被Anycast-RP使用 · The external network is already bound to another Anycast-RP：指定的外部网络已被Anycast-RP绑定 · The gateway has been used by another Anycast-RP：指定的出口网关已经被Anycast-RP使用 · The network segment has been used by another Anycast-RP：指定的网络分段已被Anycast-RP使用 · You cannot select the gateway for the Anycast-RP, because the gateway uses the same border device group as the gateway of the Anycast-RP：指定的出口网关和已存在的Anycast-RP下出口网关存在相同的设备 · The Anycast-RP does not exist：指定的Anycast-RP不存在 · Please specify Anycast-RP member address：Anycast-RP成员地址不能为空 · Failed to create the Anycast-RP, because the vPort enable the firewall or the external network has been bound to a vRouter with a firewall specified as the edge device：虚拟端口开启了防火墙或指定的外部网络已被出口设备为防火墙的虚拟路由器绑定，不允许创建Anycast-RP。 · You have no privilege to perform this operation：用户无权限执行此操作 · The specified vRouter does not exist：指定的router不存在 · The network segment is already in use：指定的网络分段已被使用 · The network segment is not bound to the external network：网络分段和外部网络不是绑定关系 · You cannot specify an network segment, because network segmentation is not enabled for the external network：指定的外部网络未开启了网络分段，网络分段取值必须为空 · Please select an external network：未指定外部网络 · The specified network segment does not exist：指定的网络分段不存在 · An Anycast-RP cannot have the same address as a distributed RP bound to the same VPN：Anycast-RP地址不能与L3组播下绑定相同VPN的分布式RP相同 · The Layer 3 multicast network with external network disabled does not exist：指定的关闭外网业务的L3组播不存在 · Please specify a distributed RP for the Layer 3 multicast network：指定L3组播的分布式RP不能为空 · An Anycast-RP member cannot have the same address as a distributed RP bound to the same VPN：Anycast-RP成员地址不能与L3组播下绑定相同VPN的分布式RP相同 · Please specify a border gateway：未指定出口网关 · You must select a vRouter or external network：虚拟路由器和外部网络必须指定一个 · The specified network segment is not bound to the external network：指定的网络分段与外部网络不是绑定关系 · The specified network segment does not exist：指定的网络分段不存在 · The specified external network does not exist：指定的外部网络不存在 · The specified border gateway does not exist：指定的出口网关不存在 · You must select a network segment, because the selected external network is enabled with network segmentation：指定的外部网络已开启网络分段，网络分段ID不能为空 · The border gateway is not bound to the selected vRouter：指定的出口网关未绑定对应的虚拟路由器 · You cannot select both a border gateway and a segmented external network for the Anycast-RP：出口网关和开启了网络分段的外部网络不允许同时指定 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
UPDATE_MULTICAST_ANYCAST_RP_OP |
|
日志内容 |
Updated Anycast-RP: $1. |
|
参数解释 |
$1：Anycast-RP的信息 |
|
举例 |
Updated Anycast-RP: MulticastAnycastRpConfig [id:[636b01e1-35e9-48be-a9d6-a8fc32a84085] vRouterId:[4ab7eb28-415a-4c4e-8e88-c76d2181a9b9] externalNetworkId:[] extSegmentUuid:[] gatewayId:[a0f8da17-e085-438f-bc8b-aeea953ca5cf] name:[1] anycastRp:[13:0:0:0:0:0:0:0] memberAddress:[[12:0:0:0:0:0:0:0, 19:0:0:0:0:0:0:0]]] |
|
日志说明 |
用户进行了更新Anycast-RP信息的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置正在恢复过程中 · Invalid license：无效的License · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · Invalid parameter：非法参数 · Invalid Anycast-RP name：无效的Anycast-RP名称 · An Anycast-RP already exists with the specified name：指定名称的Anycast-RP已存在 · The vRouter has been used by another Anycast-RP：指定的虚拟路由器已被Anycast-RP使用 · Please specify an Anycast-RP：Anycast-RP地址不能为空 · Invalid Anycast-RP address：无效的Anycast-RP地址 · Invalid Anycast-RP member address：无效的Anycast-RP成员地址 · The Anycast-RP address cannot be the same as the IP address of its member：Anycast-RP地址与其成员地址不能相同 · The Anycast-RP member address already exists：Anycast-RP成员地址存在重复地址 · The Anycast-RP does not exist：指定的Anycast-RP不存在 · There are non-modifiable fields in this parameter：传入参数中有不可修改字段 · You have no privilege to perform this operation：用户无权限执行此操作 · An Anycast-RP cannot have the same address as a distributed RP bound to the same VPN：Anycast-RP地址不能与L3组播下绑定相同VPN的分布式RP相同 · An Anycast-RP member cannot have the same address as a distributed RP bound to the same VPN.：Anycast-RP成员地址不能与L3组播下绑定相同VPN的分布式RP相同 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
DELETE_MULTICAST_ANYCAST_RP_OP |
|
日志内容 |
Deleted Anycast-RP: $1. |
|
参数解释 |
$1：Anycast-RP的UUID |
|
举例 |
Deleted Anycast-RP: 0b532731-429c-4ae0-bf01-43c314777017 |
|
日志说明 |
用户进行了删除Anycast-RP的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置正在恢复过程中 · Invalid license：无效的License · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · Invalid parameter：非法参数 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
CREATE_MULTICAST_BUM_OP |
|
日志内容 |
Created BUM multicast replication profile: $1 |
|
参数解释 |
$1：BUM组播复制的信息 |
|
举例 |
Created BUM multicast replication profile: MulticastBumConfig [name=dd, id=b413566b-0a6c-4399-ba66-dd7541ef030b, vnetworkId=f89acc82-c8b4-4980-b970-b3f7efb8fdc6, groupIpAuto=false, groupIp=234.2.2.2] |
|
日志说明 |
用户进行了创建BUM组播复制信息的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · Invalid parameter：无效参数 · Configuration recovery is in progress：配置正在恢复过程中 · A BUM multicast replication profile already exists with the specified name：指定名称的BUM组播复制已存在 · The BUM multicast replication profile already exists：指定的BUM组播复制已存在 · The vNetwork has already been bound to a BUM multicast replication profile：该虚拟链路层网络已被BUM组播复制绑定 · The specified network does not exist：指定的虚拟链路层网络不存在 · Please specify a vNetwork：虚拟链路层网络不能为空 · Please specify the name of a BUM multicast replication profile：BUM组播复制名称不能为空 · The vNetwork cannot be an external network：虚拟链路层网络不能为外部网络 · The multicast address pool does not have enough addresses for allocation：缺省组播地址池中的IP地址不足 · Cannot specify the group address when auto group address allocation is enabled：使能自动分配组播组地址后，不允许手动配置组播组地址 · Please specify a multicast group that is not in the multicast address pool：组播组地址不能在组播地址池内 · Invalid multicast group address：无效的组播组地址 · Please specify the multicast group address：组播组地址不能为空 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
UPDATE_MULTICAST_BUM_OP |
|
日志内容 |
Updated BUM multicast replication profile: $1. |
|
参数解释 |
$1：BUM组播复制的信息 |
|
举例 |
Updated BUM multicast replication profile: MulticastBumConfig [name=dd, id=b413566b-0a6c-4399-ba66-dd7541ef030b, vnetworkId=f89acc82-c8b4-4980-b970-b3f7efb8fdc6, groupIpAuto=false, groupIp=234.2.2.2] |
|
日志说明 |
用户进行了更新BUM组播复制的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置正在恢复过程中 · Invalid license：无效的License · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · Invalid parameter：非法参数 · Invalid JSON format：无效的JSON格式 · Cannot edit the name of the BUM multicast replication profile：BUM组播复制名称不允许修改 · The vNetwork cannot be an external network：虚拟链路层网络不能为外部网络 · Please specify the ID of the BUM multicast replication profile：BUM组播复制ID不能为空 · Cannot edit the ID of the vNetwork：虚拟链路层网络ID不允许修改 · The specified network does not exist：指定的虚拟链路层网络不存在 · The BUM multicast replication profile does not exist：指定的BUM组播复制不存在 · The multicast address pool does not have enough addresses for allocation：缺省组播地址池中的IP地址不足 · Cannot specify the group address when auto group address allocation is enabled：使能自动分配组播组地址后，不允许手动配置组播组地址 · Please specify a multicast group that is not in the multicast address pool：组播组地址不能在组播地址池内 · Invalid multicast group address：无效的组播组地址 · Please specify the multicast group address：组播组地址不能为空 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
DELETE_MULTICAST_BUM_OP |
|
日志内容 |
Deleted BUM multicast replication profile: $1. |
|
参数解释 |
$1：BUM组播复制的UUID |
|
举例 |
Deleted BUM multicast replication profile: 0b532731-429c-4ae0-bf01-43c314777017 |
|
日志说明 |
用户进行了删除BUM组播复制的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置正在恢复过程中 · Invalid license：无效的License · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · Invalid parameter：非法参数 · The BUM multicast replication profile does not exist：指定的BUM组播复制不存在 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
CREATE_INTERFACE_MULTICAST_OP |
|
日志内容 |
Created interface-specific multicast network: $1 |
|
参数解释 |
$1：接口组播信息 |
|
举例 |
Created interface-specific multicast network: InterfaceMulticastConfig{id=9a44bd22-4934-4841-bfd4-fbfa453c5b1c, name='11', multicastId='43882183-4b5d-46a2-bda3-a97b50ad480a', belongerNetworkId='f4afb793-3fa2-4dbb-9477-faf3ddf2de8c', pimTemplateConfig=PimTemplateConfig [protocol=PIM-SM, helloInterval=22, helloHoldtime=22, joinPruneInterval=21, joinPruneHoldtime=22, lanDelay=22, overrideInterval=22, passive=false, ssmPolicy=null], pimPolicyConfig=PimPolicyConfig [neighborPolicy=null, joinPolicy=null], igmpTemplateConfig=IgmpTemplateConfig [version=V2, robustCount=null, queryInterval=null, maxResponseTime=null, lastMemberQueryInterval=null, otherQuerierPresent=null, ssmMappingId=null], igmpPolicyConfig=IgmpPolicyConfig [groupPolicy=null]} |
|
日志说明 |
用户进行了创建接口组播信息的操作 |
|
· 失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · Configuration recovery is in progress：配置正在恢复过程中 · Invalid UUID:parameter：无效的UUID · Invalid parameter：参数错误 · The hello interval is out of range：Hello报文发送频率超过取值范围 · The hello holdtime is out of range：Hello报文保持时间超过取值范围 · The join or prune interval is out of range：Join/Prune报文发送时间超过取值范围 · The join or prune holdtime is out of range：Join/Prune报文保持时间超过取值范围 · The propagation delay is out of range：传输延时时间超过取值范围 · The override interval is out of range：剪枝否决时间超过取值范围 · The neighbor policy ACL must be basic ACL：邻居过滤策略需为基础策略 · The join policy ACL must be basic ACL：Join信息过滤策略需为基础策略 · The IGMP version is invalid：IGMP版本非法 · The IGMP querier’s robustness variable is out of range：查询器健壮系数超过取值范围 · The IGMP query interval is out of range：普通组查询报文发送频率超过取值范围 · The IGMP max response time is out of range：普通组查询报文最大时间超过取值范围 · The IGMP last member query interval is out of range：IGMP特定组/源组查询报文发送时间间隔超过取值范围 · The other querier present time is out of range：其它IGMP查询器的存活时间超过取值范围 · The interface-specific multicast network already exists：基于接口的组播网络已存在 · Invalid interface-specific multicast network name：基于接口的组播网络名称无效 · An interface-specific multicast network already exists with the specified name：基于接口的组播网络名称已存在 · Invalid multicast network ID：无效的组播ID · Cannot configure an interface-specific multicast network in the Layer 3 multicast network.The Layer 3 multicast network has been configured to provide external services：基于接口的组播网络所属组播不能开启外网业务 · Invalid vNetwork ID：无效的虚拟链路层网络ID · The VSM service is not available：VSM服务不可用 · The vNetwork does not exist：指定的虚拟链路层网络不存在 · Cannot configure an interface-specific multicast network with external vNetWork：接口组播不支持外部网络 · Please enable multicast capabilities for the vNetwork：指定的虚拟链路层网络必须使能组播网络 · The vNetwork has been bound to another interface-specific multicast network：指定的虚拟链路层网络已被其他基于接口的组播网络使用 · Please specify a vNetwork that is bound to the same vRouter with the interface-specific multicast network：指定的虚拟链路层网络必须绑定接口组播所属组播的的虚拟路由器 · Please set the PIM protocol to PIM-SM：PIM协议必须为PIM-SM协议 · Please leave the SSM multicast group range empty：SSM组播组不能有值 · Please leave the SSM mapping empty：SSM Mapping必须为空 · The join or prune interval must be less than the joined or pruned state holdtime：Join/Prune报文发送时间必须小于Join/Prune报文保持时间 · The joined or pruned state hold time must be greater than the default join or prune interval (60)：Join/Prune报文保持时间必须大于Join/Prune报文发送时间默认值60 · The join or prune interval must be less than the default joined or pruned state hold time (210)：Join/Prune报文发送时间必须小于Join/Prune报文保持时间默认值210 · Cannot set the max response time when the IGMP version is v1：IGMP协议为V1时普通组查询报文最大响应时间不能有值 · Cannot set the last member query interval when the IGMP version is v1：IGMP协议为V1时IGMP最后组成员查询间隔不能有值 · Cannot set the other querier present time when the IGMP version is v1：IGMP协议为V1时其它IGMP查询器的存活时间不能有值 · The other querier present time must be greater than the general query interval：其它IGMP查询器的存活时间应大于普遍组查询报文发送频率 · The other querier present time must be greater than the default general query interval (125)：其它IGMP查询器的存活时间必须大于普遍组查询报文发送频率默认值125 · The general query interval must be less than the default value for the other querier present time (255)：普遍组查询报文发送频率取值必须小于其它IGMP查询器存活时间默认值255 · The general query interval must be greater than the max response time：普遍组查询报文发送频率应大于普遍组查询报文最大响应时间 · The max response time must be less than the default general query interval (125)：普遍组查询报文最大响应时间必须小于普遍组查询报文发送频率默认值125 · The general query interval must be greater than the default max response time (10)：普遍组查询报文发送频率必须大于普遍组查询报文最大响应时间默认值10 · The Layer 3 multicast network does not exist：指定的组播不存在 · You have no privilege to perform this operation：用户无权限执行此操作 · The IGMP version must be v3 if PIM-SM is used：当PIM协议为PIM-SSM时，IGMP版本必须为V3 · The Layer 3 multicast network and its multicast network interfaces must run the same PIM protocol：L3组播和组播接口的PIM协议类型要保持一致 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · The MLD querier's robustness variable is out of range：MLD查询健壮系数超出取值范围 · The MLD general query interval is out of range：MLD普遍组查询报文的发送时间间隔超出取值范围 · The MLD max response time is out of range：MLD普遍组查询报文的最大响应时间超出取值范围 · The MLD last member query interval is out of range：MLD最后组成员查询间隔 · The MLD other querier present time is out of range：其它MLD查询器的存活时间超出取值范围 · The MLD version is invalid：MLD版本须为V1或V2 · The specified vNetwork must support IPv6 multicast network：指定的虚拟链路层网络必须使能IPv6组播网络 · The MLD version must be v2 if PIM-SSM is used：当PIM协议为PIM-SSM时，MLD版本必须为V2 |
|
关键字 |
UPDATE_INTERFACE_MULTICAST_OP |
|
日志内容 |
Updated interface-specific multicast network: $1. |
|
参数解释 |
$1：接口组播的信息 |
|
举例 |
Updated interface-specific multicast network: InterfaceMulticastConfig{id=9a44bd22-4934-4841-bfd4-fbfa453c5b1c, name='11', multicastId='43882183-4b5d-46a2-bda3-a97b50ad480a', belongerNetworkId='f4afb793-3fa2-4dbb-9477-faf3ddf2de8c', pimTemplateConfig=PimTemplateConfig [protocol=PIM-SM, helloInterval=33, helloHoldtime=22, joinPruneInterval=21, joinPruneHoldtime=22, lanDelay=22, overrideInterval=22, passive=false, ssmPolicy=null], pimPolicyConfig=PimPolicyConfig [neighborPolicy=null, joinPolicy=null], igmpTemplateConfig=IgmpTemplateConfig [version=V2, robustCount=null, queryInterval=null, maxResponseTime=null, lastMemberQueryInterval=null, otherQuerierPresent=null, ssmMappingId=null], igmpPolicyConfig=IgmpPolicyConfig [groupPolicy=null]} |
|
日志说明 |
用户进行了更新接口组播的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置正在恢复过程中 · Invalid license：无效的License · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · Invalid parameter：非法参数 · The hello interval is out of range：Hello报文发送频率超过取值范围 · The hello holdtime is out of range：Hello报文保持时间超过取值范围 · The join or prune interval is out of range：Join/Prune报文发送时间超过取值范围 · The join or prune holdtime is out of range：Join/Prune报文保持时间超过取值范围 · The propagation delay is out of range：传输延时时间超过取值范围 · The override interval is out of range：剪枝否决时间超过取值范围 · The neighbor policy ACL must be basic ACL：邻居过滤策略需为基础策略 · The join policy ACL must be basic ACL：Join信息过滤策略需为基础策略 · The IGMP version is invalid：IGMP版本非法 · The IGMP querier’s robustness variable is out of range：查询器健壮系数超过取值范围 · The IGMP query interval is out of range：普通组查询报文发送频率超过取值范围 · The IGMP max response time is out of range：普通组查询报文最大时间超过取值范围 · The IGMP last member query interval is out of range：IGMP特定组/源组查询报文发送时间间隔超过取值范围 · The other querier present time is out of range：其它IGMP查询器的存活时间超过取值范围 · Please set the PIM protocol to PIM-SM：PIM协议必须为PIM-SM协议 · Please leave the SSM multicast group range empty：SSM组播组不能有值 · Please leave the SSM mapping empty：SSM Mapping必须为空 · The join or prune interval must be less than the joined or pruned state holdtime：Join/Prune报文发送时间必须小于Join/Prune报文保持时间 · The joined or pruned state hold time must be greater than the default join or prune interval (60)：Join/Prune报文保持时间必须大于Join/Prune报文发送时间默认值60 · The join or prune interval must be less than the default joined or pruned state hold time (210)：Join/Prune报文发送时间必须小于Join/Prune报文保持时间默认值210 · Cannot set the max response time when the IGMP version is v1：IGMP协议为V1时普通组查询报文最大响应时间不能有值 · Cannot set the last member query interval when the IGMP version is v1：IGMP协议为V1时IGMP最后组成员查询间隔不能有值 · Cannot set the other querier present time when the IGMP version is v1：IGMP协议为V1时其它IGMP查询器的存活时间不能有值 · The other querier present time must be greater than the general query interval：其它IGMP查询器的存活时间应大于普遍组查询报文发送频率 · The other querier present time must be greater than the default general query interval (125)：其它IGMP查询器的存活时间必须大于普遍组查询报文发送频率默认值125 · The general query interval must be less than the default value for the other querier present time (255)：普遍组查询报文发送频率取值必须小于其它IGMP查询器存活时间默认值255 · The general query interval must be greater than the max response time：普遍组查询报文发送频率应大于普遍组查询报文最大响应时间 · The max response time must be less than the default general query interval (125)：普遍组查询报文最大响应时间必须小于普遍组查询报文发送频率默认值125 · The general query interval must be greater than the default max response time (10)：普遍组查询报文发送频率必须大于普遍组查询报文最大响应时间默认值10 · Cannot edit the ID of a Layer 3 multicast network：L3组播ID不能修改 · Cannot edit the ID of a vNetwork：虚拟链路层网络ID不能修改 · Cannot edit the name of an interface-specific multicast network：基于接口的组播网络名称不能修改 · Please specify the ID of the interface-specific multicast network：基于接口的组播网络ID不能为空 · You have no privilege to perform this operation：用户无权限执行此操作 · The IGMP version must be v3 if PIM-SM is used：当PIM协议为PIM-SSM时，IGMP版本必须为V3 · The Layer 3 multicast network and its multicast network interfaces must run the same PIM protocol：L3组播和组播接口的PIM协议类型要保持一致 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · The MLD querier's robustness variable is out of range：MLD查询健壮系数超出取值范围 · The MLD general query interval is out of range：MLD普遍组查询报文的发送时间间隔超出取值范围 · The MLD max response time is out of range：MLD普遍组查询报文的最大响应时间超出取值范围 · The MLD last member query interval is out of range：MLD最后组成员查询间隔 · The MLD other querier present time is out of range：其它IGMP查询器的存活时间超出取值范围 · The MLD version is invalid：MLD版本须为V1或V2 · Please enable IPv6 multicast capabilities for the vNetwork：指定的虚拟链路层网络必须使能IPv6组播网络 · The MLD version must be v2 if PIM-SSM is used：当PIM协议为PIM-SSM时，MLD版本必须为V2 |
|
关键字 |
DELETE_INTERFACE_MULTICAST_OP |
|
日志内容 |
Deleted interface-specific multicast network: $1. |
|
参数解释 |
$1：接口组播的UUID |
|
举例 |
Deleted interface-specific multicast network: 9a44bd22-4934-4841-bfd4-fbfa453c5b1c |
|
日志说明 |
用户进行了删除接口组播的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置正在恢复过程中 · Invalid license：无效的License · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · Invalid parameter：非法参数 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
CREATE_PIM_TEMPLATE_OP |
|
日志内容 |
Created PIM template: $1. |
|
参数解释 |
$1：组播PIM配置模板信息 |
|
举例 |
Created PIM template: PimTemplate [id=0eff3238-7210-468f-bdae-032a17b23758, name=PimTest, ipVersion=IPv4,pimTemplateConfig=PimTemplateConfig [protocol=PIM-SM, helloInterval=5, helloHoldtime=5, joinPruneInterval=4, joinPruneHoldtime=5, lanDelay=5, overrideInterval=5, passive=false]. |
|
日志说明 |
用户进行了创建组播PIM配置模板的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · Invalid PIM template name：PIM配置模板名称无效 · A PIM template already exists with the specified name：指定名称的PIM配置模板已存在 · Invalid PIM passive mode：无效的PIM消极模式 · Invalid PIM protocol：PIM协议非法 · The hello interval is out of range：Hello报文发送频率超过取值范围 · The hello holdtime is out of range：Hello报文保持时间超过取值范围 · The join or prune interval is out of range：Join/Prune报文发送时间超过取值范围 · The join or prune holdtime is out of range：Join/Prune报文保持时间超过取值范围 · The propagation delay is out of range：传输延时时间超过取值范围 · The override interval is out of range：剪枝否决时间超过取值范围 · The join or prune interval must be less than the joined or pruned state holdtime：Join/Prune报文发送时间必须小于Join/Prune报文保持时间 · The joined or pruned state hold time must be greater than the default join or prune interval (60)：Join/Prune报文保持时间必须大于Join/Prune报文发送时间默认值(60) · The join or prune interval must be less than the default joined or pruned state hold time (210)：Join/Prune报文发送时间必须小于Join/Prune报文保持时间默认值(210) · You have no privilege to perform this operation：用户无权限执行此操作 · A PIM template already exists with the specified ID：指定ID的PIM配置模板已存在 · Invalid multicast type：无效的组播版本 |
|
关键字 |
UPDATE_PIM_TEMPLATE_OP |
|
日志内容 |
Updated PIM template: $1. |
|
参数解释 |
$1：组播PIM配置模板信息 |
|
举例 |
Updated PIM template:PimTemplate [id=0eff3238-7210-468f-bdae-032a17b23758, name=PimTest, ipVersion=IPv4,pimTemplateConfig=PimTemplateConfig [protocol=PIM-SM, helloInterval=5, helloHoldtime=5, joinPruneInterval=4, joinPruneHoldtime=5, lanDelay=6, overrideInterval=5, passive=false]]. |
|
日志说明 |
用户进行了更新组播PIM配置模板的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · The PIM template does not exist：指定的PIM配置模板不存在 · Please specify the ID of the PIM template：PIM配置模板ID不能为空 · Cannot edit the name of the PIM template：PIM配置模板名称不允许修改 · Invalid PIM passive mode：无效的PIM消极模式 · Invalid PIM protocol：PIM协议非法 · The hello interval is out of range：Hello报文发送频率超过取值范围 · The hello holdtime is out of range：Hello报文保持时间超过取值范围 · The join or prune interval is out of range：Join/Prune报文发送时间超过取值范围 · The join or prune holdtime is out of range：Join/Prune报文保持时间超过取值范围 · The propagation delay is out of range：传输延时时间超过取值范围 · The override interval is out of range：剪枝否决时间超过取值范围 · The join or prune interval must be less than the joined or pruned state holdtime：Join/Prune报文发送时间必须小于Join/Prune报文保持时间 · The joined or pruned state hold time must be greater than the default join or prune interval (60)：Join/Prune报文保持时间必须大于Join/Prune报文发送时间默认值(60) · The join or prune interval must be less than the default joined or pruned state hold time (210)：Join/Prune报文发送时间必须小于Join/Prune报文保持时间默认值(210) · You have no privilege to perform this operation：用户无权限执行此操作 · You cannot edit the multicast type parameter：组播版本不允许修改 |
|
关键字 |
DELETE_PIM_TEMPLATE_OP |
|
日志内容 |
Deleted PIM template: $1. |
|
参数解释 |
$1：组播PIM配置模板信息 |
|
举例 |
Deleted PIM template:0eff3238-7210-468f-bdae-032a17b23758. |
|
日志说明 |
用户进行了删除组播PIM配置模板的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置正在恢复过程中 · Invalid license：无效的License · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_IGMP_TEMPLATE_OP |
|
日志内容 |
Created IGMP template: $1. |
|
参数解释 |
$1：组播IGMP配置模板信息 |
|
举例 |
Created IGMP template: IgmpTemplate [id=3007347f-d41a-4726-ac29-530109877156, name=igmp_template, igmpTemplateConfig=IgmpTemplateConfig [version=V2, robustCount=11, queryInterval=22, maxResponseTime=11, lastMemberQueryInterval=23, otherQuerierPresent=44, proxyEnable=true]] |
|
日志说明 |
用户进行了创建组播IGMP配置模板的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · Invalid name：无效的名称 · The name is required：名称必填 · The IGMP version is invalid：IGMP版本须为V1或V2或V3 · An IGMP template already exists with the specified name：指定的IGMP配置模板已存在 · The other querier present time must be greater than the general query interval：其它IGMP查询器的存活时间应大于普遍组查询报文发送频率 · The general query interval must be greater than the max response time：普遍组查询报文发送频率应大于普遍组查询报文最大响应时间 · Cannot set the max response time when the IGMP version is v1：IGMP协议为V1版本时，普遍组查询报文最大响应时间不填 · Cannot set the last member query interval when the IGMP version is v1：IGMP协议为V1版本时，IGMP最后组成员查询间隔不填 · Cannot set the other querier present time when the IGMP version is v1：IGMP协议为V1版本时，其它IGMP查询器的存活时间不填 · The IGMP querier’s robustness variable is out of range：IGMP查询健壮系数超出取值范围 · The IGMP query interval is out of range：IGMP普遍组查询报文的发送时间间隔超出取值范围 · The IGMP max response time is out of range：IGMP普遍组查询报文的最大响应时间超出取值范围 · The IGMP last member query interval is out of range：IGMP最后组成员查询间隔超出取值范围 · The other querier present time is out of range：其它IGMP查询器的存活时间超出取值范围 · The general query interval must be less than the default value for the other querier present time (255)：普遍组查询报文发送频率取值必须小于其它IGMP查询器存活时间默认值(255) · The other querier present time must be greater than the default general query interval (125)：其它IGMP查询器的存活时间必须大于普遍组查询报文发送频率默认值(125) · The general query interval must be greater than the default max response time (10)：普遍组查询报文发送频率必须大于普遍组查询报文最大响应时间默认值(10) · The max response time must be less than the default general query interval (125)：普遍组查询报文最大响应时间必须小于普遍组查询报文发送频率默认值(125) · You have no privilege to perform this operation：用户无权限执行此操作 · An IGMP template already exists with the specified ID：指定ID的IGMP配置模板已存在 |
|
关键字 |
UPDATE_IGMP_TEMPLATE_OP |
|
日志内容 |
Updated IGMP template: $1. |
|
参数解释 |
$1：组播IGMP配置模板信息 |
|
举例 |
Updated IGMP template: IgmpTemplate [id=3007347f-d41a-4726-ac29-530109877156, name=igmp_template, igmpTemplateConfig=IgmpTemplateConfig [version=V2, robustCount=11, queryInterval=22, maxResponseTime=11, lastMemberQueryInterval=23, otherQuerierPresent=44, proxyEnable=false]] |
|
日志说明 |
用户进行了更新组播IGMP配置模板的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · The IGMP template does not exist：指定的IGMP配置模板不存在 · Please specify the ID of the IGMP template：IGMP配置模板ID不能为空 · Cannot edit the name of the IGMP template：IGMP配置模板名称不能修改 · The IGMP version is invalid：IGMP版本须为V1或V2或V3 · The other querier present time must be greater than the general query interval：其它IGMP查询器的存活时间应大于普遍组查询报文发送频率 · The general query interval must be greater than the max response time：普遍组查询报文发送频率应大于普遍组查询报文最大响应时间 · Cannot set the max response time when the IGMP version is v1：IGMP协议为V1版本时，普遍组查询报文最大响应时间不填 · Cannot set the last member query interval when the IGMP version is v1：IGMP协议为V1版本时，IGMP最后组成员查询间隔不填 · Cannot set the other querier present time when the IGMP version is v1：IGMP协议为V1版本时，其它IGMP查询器的存活时间不填 · The IGMP querier’s robustness variable is out of range：IGMP查询健壮系数超出取值范围 · The IGMP query interval is out of range：IGMP普遍组查询报文的发送时间间隔超出取值范围 · The IGMP max response time is out of range：IGMP普遍组查询报文的最大响应时间超出取值范围。 · The IGMP last member query interval is out of range：IGMP最后组成员查询间隔超出取值范围 · The other querier present time is out of range：其它IGMP查询器的存活时间超出取值范围 · The general query interval must be less than the default value for the other querier present time (255)：普遍组查询报文发送频率取值必须小于其它IGMP查询器存活时间默认值(255) · The other querier present time must be greater than the default general query interval (125)：其它IGMP查询器的存活时间必须大于普遍组查询报文发送频率默认值(125) · The general query interval must be greater than the default max response time (10)：普遍组查询报文发送频率必须大于普遍组查询报文最大响应时间默认值(10) · The max response time must be less than the default general query interval (125)：普遍组查询报文最大响应时间必须小于普遍组查询报文发送频率默认值(125) · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_IGMP_TEMPLATE_OP |
|
日志内容 |
Deleted IGMP template: $1. |
|
参数解释 |
$1：组播IGMP配置模板的UUID |
|
举例 |
Deleted IGMP template：349f858b-4b34-470c-b5af-e98de3ff71ff. |
|
日志说明 |
用户进行了删除组播IGMP配置模板的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置正在恢复过程中 · Invalid license：无效的License · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_MLD_TEMPLATE_OP |
|
日志内容 |
Created MLD template: $1. |
|
参数解释 |
$1：组播MLD配置模板信息 |
|
举例 |
Created MLD template: MldTemplate [id=3007347f-d41a-4726-ac29-530109877156, name=mld_template, mldTemplateConfig=mldTemplateConfig [version=V2, robustCount=11, queryInterval=22, maxResponseTime=11, lastMemberQueryInterval=23, otherQuerierPresent=44]] |
|
日志说明 |
用户进行了创建组播MLD配置模板的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · Invalid name：无效的名称 · The name is required：名称必填 · The MLD version is invalid：MLD协议须为V1或V2 · An MLD template already exists with the specified name：指定的MLD配置模板已存在 · The other querier present time must be greater than the general query interval：其它MLD查询器的存活时间应大于普遍组查询报文发送频率 · The general query interval must be greater than the max response time：普遍组查询报文发送频率应大于普遍组查询报文最大响应时间 · The MLD querier’s robustness variable is out of range：MLD查询健壮系数超出取值范围 · The MLD query interval is out of range：MLD普遍组查询报文的发送时间间隔超出取值范围 · The MLD max response time is out of range：MLD普遍组查询报文的最大响应时间超出取值范围 · The MLD last member query interval is out of range：MLD最后组成员查询间隔超出取值范围 · The MLD other querier present time is out of range：其它MLD查询器的存活时间超出取值范围 · The general query interval must be less than the default value for the other querier present time (255)：普遍组查询报文发送频率取值必须小于其它MLD查询器存活时间默认值(255) · The other querier present time must be greater than the default general query interval (125)：其它MLD查询器的存活时间必须大于普遍组查询报文发送频率默认值(125) · The general query interval must be greater than the default max response time (10)：普遍组查询报文发送频率必须大于普遍组查询报文最大响应时间默认值(10) · The max response time must be less than the default general query interval (125)：普遍组查询报文最大响应时间必须小于普遍组查询报文发送频率默认值(125) · You have no privilege to perform this operation：用户无权限执行此操作 · An MLD template already exists with the specified ID：指定ID的MLD配置模板已存在 |
|
关键字 |
UPDATE_MLD_TEMPLATE_OP |
|
日志内容 |
Updated MLD template: $1. |
|
参数解释 |
$1：组播MLD配置模板信息 |
|
举例 |
Updated MLD template: MldTemplate [id=3007347f-d41a-4726-ac29-530109877156, name=mld_template, mldTemplateConfig=MldTemplateConfig [version=V2, robustCount=11, queryInterval=22, maxResponseTime=11, lastMemberQueryInterval=23, otherQuerierPresent=44]] |
|
日志说明 |
用户进行了更新组播MLD配置模板的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · The MLD template does not exist：指定的MLD配置模板不存在 · Please specify the ID of the MLD template：MLD配置模板ID不能为空 · Cannot edit the name of the MLD template：MLD配置模板名称不能修改 · The MLD version is invalid：MLD版本须为V1或V2 · The other querier present time must be greater than the general query interval：其它MLD查询器的存活时间应大于普遍组查询报文发送频率 · The general query interval must be greater than the max response time：普遍组查询报文发送频率应大于普遍组查询报文最大响应时间 · The MLD querier’s robustness variable is out of range：MLD查询健壮系数超出取值范围 · The MLD query interval is out of range：MLD普遍组查询报文的发送时间间隔超出取值范围 · The MLD max response time is out of range：MLD普遍组查询报文的最大响应时间超出取值范围。 · The MLD last member query interval is out of range：MLD特定组/源组查询报文的发送时间间隔超出取值范围 · The MLD other querier present time is out of range：其它MLD查询器的存活时间超出取值范围 · The general query interval must be less than the default value for the other querier present time (255)：普遍组查询报文发送频率取值必须小于其它MLD查询器存活时间默认值(255) · The other querier present time must be greater than the default general query interval (125)：其它MLD查询器的存活时间必须大于普遍组查询报文发送频率默认值(125) · The general query interval must be greater than the default max response time (10)：普遍组查询报文发送频率必须大于普遍组查询报文最大响应时间默认值(10) · The max response time must be less than the default general query interval (125)：普遍组查询报文最大响应时间必须小于普遍组查询报文发送频率默认值(125) · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_MLD_TEMPLATE_OP |
|
日志内容 |
Deleted MLD template: $1. |
|
参数解释 |
$1：组播MLD配置模板的UUID |
|
举例 |
Deleted MLD template：349f858b-4b34-470c-b5af-e98de3ff71ff. |
|
日志说明 |
用户进行了删除组播MLD配置模板的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置正在恢复过程中 · Invalid license：无效的License · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_M-LAG_GROUP_ID_RANGE_OP |
|
日志内容 |
Created an M-LAG group ID range: $1 |
|
参数解释 |
$1：M-LAG组编号范围配置信息 |
|
举例 |
Created an M-LAG group ID range: Id:f471887b-6831-4119-92d4-4aa5c2102685, device1:d480fe8f-42ba-46cd-bff8-39a3393bc159, device2:3230fc37-1dd5-4f0f-a576-8bc4a6876c4b, numberrange:3-69 |
|
日志说明 |
用户进行了添加M-LAG组编号范围的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · M-LAG group ID ranges have been configured for the specified devices：指定的设备已创建M-LAG组编号范围 · The specified device does not exist：指定的设备不存在 · M-LAG group ID range error：指定的M-LAG组编号范围错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown system error：系统未知错误 · Invalid JSON format：无效的JSON格式 · The member devices of the M-LAG system must have the same device type：创建M-LAG系统的成员设备必须设备类型一致 · The member devices of the M-LAG system must belong to the same fabric：两个成员设备必须在相同Fabric下 · You have no privilege to perform this operation：用户无权限执行此操作 · The M-LAG group ID range cannot exceed 255 characters：指定的M-LAG组编号范围长度最长255个字符 · The M-LAG member devices must be access or border devices：组成M-LAG系统的成员设备必须是接入设备或边界设备 · The M-LAG member devices must have the same device role and device type：组成M-LAG系统的成员设备必须是相同的设备角色和设备类型 · You can only expand the M-LAG group ID range：不支持缩小M-LAG组编号范围 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
UPDATE_M-LAG_GROUP_ID_RANGE_OP |
|
日志内容 |
Updated an M-LAG group ID range: $1 |
|
参数解释 |
$1：M-LAG组编号范围配置信息 |
|
举例 |
Updated an M-LAG group ID range: Id:f471887b-6831-4119-92d4-4aa5c2102685, device1:d480fe8f-42ba-46cd-bff8-39a3393bc159, device2:3230fc37-1dd5-4f0f-a576-8bc4a6876c4b, number range:3-69 |
|
日志说明 |
用户进行了更新M-LAG组编号范围的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · M-LAG group ID range error：指定的M-LAG组编号范围错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown system error：系统未知错误 · Invalid JSON format：无效的JSON格式 · You have no privilege to perform this operation：用户无权限执行此操作 · The M-LAG group ID range cannot exceed 255 characters：指定的M-LAG组编号范围长度最长255个字符 · You can only expand the M-LAG group ID range：不支持缩小M-LAG组编号范围 · The M-LAG group ID range does not exist：该M-LAG组编号范围不存在 · You cannot delete or edit an existing M-LAG group ID range. You can only add M-LAG group ID ranges：不允许删除或修改已有的M-LAG组编号范围，只允许追加M-LAG组编号范围 |
|
关键字 |
DELETE_M-LAG_GROUP_ID_RANGE_OP |
|
日志内容 |
Deleted an M-LAG group ID range: $1 |
|
参数解释 |
$1：需要删除的M-LAG组编号范围的ID |
|
举例 |
Deleted an M-LAG group ID range: f471887b-6831-4119-92d4-4aa5c2102685 |
|
日志说明 |
用户进行了删除M-LAG组编号范围的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown system error：系统未知错误 · The M-LAG group ID range is in use：该M-LAG组编号范围正在被使用 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
START_FINE_GRAINED_DATA_SYNCHRONIZATION_OP |
|
日志内容 |
Started fine-grained data synchronization on physical device: $1 |
|
参数解释 |
$1：物理设备的UUID |
|
举例 |
Started fine-grained data synchronization on physical device: 28424135-36f5-4dde-ad2e-29580411de8d |
|
日志说明 |
用户进行了手动触发指定物理设备进行精细化数据同步的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · The service is disabled：服务未启动 · The device doesn't exist：该设备不存在 · The device is inactive：设备处于未激活状态 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · The device does not support this function：此设备不支持本功能 · The device is being deleted or being removed from the gateway group：该设备正在删除或从设备组中移出 · The system is performing data synchronization or configuration auditing for the device：该设备正在进行数据同步或配置审计 · You have no privilege to perform this operation：用户无权限执行此操作 · Invalid JSON format：无效的JSON格式 |
|
关键字 |
CREATE_MLAG_SYSTEM_OP |
|
日志内容 |
Created an M-LAG System: “$1” |
|
参数解释 |
$1：M-LAG系统信息 |
|
举例 |
Created an M-LAG system: MlagGroupListConfig [mlagGroupConfigs=[ id: [f3092d9f-105f-482d-a903-c47e36d51bed] name: [11] description: [null] fabric id: [682545c2-8e82-48da-a3a0-32ac22e93769] fabric name: [1] join type: [USER_CREATE] device member list: [[ device id: [49065e4b-8177-4122-bd87-a806e4b56210] device name: [67.190] management ip: [192.168.67.190] ipp lagg id: [62451b5d-fd44-46e7-abf5-3758be76cd42] lagg info list: [[]] exclude mad interface: [[]], device id: [b68259d0-ef5d-4739-bec8-c5a0c34b872a] device Name: [67.195] management ip: [192.168.67.195] ipp lagg id: [a86331b3-4fe1-4758-97a9-17bd3671beda] lagg info list: [[]] exclude mad interface: [[]] ]] mlag mode: [dynamic] mlag type: [has_peer_link] underlay protocol: [OSPF] ospf id: [1] ospf area: [2] isis id: [null] bgp instance: [null] keep alive link type: [mgmt_link] escape vlan id: [null] reserved vxlan id: [null] mlag link mode: [dynamic] restore delay: [22] ]] |
|
日志说明 |
用户进行了创建M-LAG系统的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · You have no privilege to perform this operation：用户无权限执行此操作 · Unknown internal server error：未知的内部服务器错误 · The M-LAG system name already exists：M-LAG系统的名称已存在 · The M-LAG system name cannot be empty：M-LAG系统名称不能为空 · To use a direct link as the keepalive link, make sure a peer-link and the keepalive link have been set up between the M-LAG member devices：Keepalive链路取值为直连链路时，设备间必须存在peer-link和Keepalive链路 · To use a management link as the keepalive link, make sure a peer-link has been set up between the M-LAG member devices：Keepalive链路取值为管理网链路时，设备间必须存在peer-link链路 · The M-LAG system name cannot exceed 255 characters：M-LAG系统名称最长255个字符 · The M-LAG system description cannot exceed 255 characters：M-LAG系统描述信息最长255个字符 · The device ID is not specified：未指定设备ID · The device does not exist：指定的设备不存在 · The device does not belong to the fabric：指定的设备不在Fabric内 · The device ID is exist in M-LAG system：设备已加入M-LAG系统 · The value of join_type must be USER_CREATE or AUTO_ONLINE：join_type取值仅支持USER_CREATE和AUTO_ONLINE · The vtep pool of deploy resource pool is not existed：设备所属Fabric下对应的部署资源池中不存在VTEP地址池 · Invalid ID：无效的ID · The M-LAG system ID already exists：M-LAG系统的ID已存在 · The M-LAG system does not exist：指定的M-LAG系统不存在 · Failed to assign IP addresses from the physical VTEP network address pool：物理VTEP地址池分配IP地址失败 · Failed to check the availability of the highest tunnel ID：检查最大Tunnel是否被使用失败 · Failed to establish an NETCONF connection between the controller and the device：控制组件与设备建立NETCONF连接失败 · The M-LAG member devices must have the same device role and device type：组成M-LAG系统的成员设备必须是相同的设备角色和设备类型 · The M-LAG member devices must be leaf access devices, leaf border devices, or spine border devices：组成M-LAG系统的成员设备仅支持Leaf接入设备、Leaf边界设备和Spine边界设备 · The M-LAG member devices must belong to the same device group：M-LAG系统设备是边界设备时，M-LAG系统设备必须加入同一个设备组 · To establish an M-LAG system, make sure both devices are in Active state：M-LAG系统设备的状态必须为Active · Invalid critical VLAN ID：无效的critical VLAN ID · Please specify a scene：场景不能为空 · Invalid scene：无效的场景 · Please specify the interface aggregation mode：接口聚合模式不能为空 · Invalid interface aggregation mode：无效的接口聚合模式 · Do not specify an M-LAG address pool for automatic device deployment：当设备自动化上线时，不允许指定M-LAG地址池 · You must specify an M-LAG address pool for manual device deployment：当设备手动上线时，必须指定M-LAG地址池 · The specified M-LAG address pool does not exist：指定的M-LAG地址池不存在 · The M-LAG address pool has been used for automatic deployment：指定的M-LAG地址池已被部署资源池使用 · The M-LAG member devices must have the same deployment mode：M-LAG系统设备上线方式必须相同 · Please specify a keepalive link type：Keepalive链路取值不能为空 · Invalid keepalive link type：Keepalive链路取值无效 · If the peer-link is a tunnel, the keepalive link must be a management link：当场景为隧道peer-link时，Keepalive链路只能是管理网链路 · Please specify an underlay protocol：Underlay路由协议不能为空 · The underlay protocol must be OSPF, IS-IS, or EBGP：Underlay路由协议取值必须为OSPF、ISIS和EBGP · You must select the underlay protocol used on the fabric：Underlay路由协议取值必须和Fabric一致 · Please specify an OSPF ID：OSPF ID不能为空 · Please specify an OSPF area：OSPF Area不能为空 · Invalid OSPF area ID：无效的OSPF Area ID · You must enter the OSPF ID configured in the automation template：OSPF ID必须和自动化模板配置的一致 · The OSPF ID must be in the range of 1 to 65536：OSPF ID取值范围为1～65536 · You must select the OSPF area configured in the automation template：OSPF Area必须和自动化模板配置的一致 · Please specify an IS-IS ID：ISIS ID不能为空 · You must enter the IS-IS ID configured in the automation template：ISIS ID必须和自动化模板配置的一致 · The IS-IS ID must be in the range of 1 to 65536：ISIS ID的取值范围为1～65536 · Please specify a BGP instance：BGP实例不能为空 · Invalid BGP instance：无效的BGP实例 · Please specify an M-LAG group ID range：未配置M-LAG组编号范围 · Failed to obtain the highest tunnel ID：获取设备上最大的Tunnel失败 · The highest tunnel ID is in use：设备上最大Tunnel已经被使用 · Please first configure a critical VLAN ID in the automation template：请先在自动化模板中配置逃生VLAN ID · Please specify a reserved VXLAN ID：保留VXLAN ID不能为空 · The reserved VXLAN ID must be an integer in the range of 1 to 16777215：保留VXLAN的取值范围为1～16777215的整数 · Make sure the reserved VXLAN is not in any existing VXLAN pool：M-LAG系统的保留VXLAN不允许和已存在的VXLAN池重叠 · Please first configure a reserved VXLAN ID in the automation template：请先在自动化模板中配置保留VXLAN ID · The fabric ID is required：未指定Fabric ID · The specified fabric doesn't exist：指定的Fabric不存在 · Failed to obtain the EVPN global MAC address：获取EVPN的全局MAC地址失败 · The VXLAN range contains the reserved VXLAN ID configured for the device deployment template or the M-LAG system：指定的VXLAN范围与自动化模板或M-LAG系统的保留VXLAN重叠 · The reserved VXLAN ID cannot be identical to the segment ID of a vNetwork or vRouter：保留VXLAN ID不能与虚拟链路层网络和虚拟路由器的Segment ID相同 · If the peer link is a tunnel, the M-LAG system does not support excluding interfaces from the shutdown action by M-LAG MAD：当场景为隧道peer-link时，M-LAG系统不支持配置例外接口 · The interface name format is invalid：无效的例外接口名称格式 · The specified interface is already an excluded interface：指定的例外接口已存在 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · The data restoration delay must be an integer in the range of 1 to 3600：延迟恢复时间取值范围为1~3600的整数 · The interface is already a downlink interface. Port name %s：指定接口%s已经是下行口 |
|
关键字 |
UPDATE_MLAG_SYSTEM_OP |
|
日志内容 |
Updated an M-LAG system : “$1” |
|
参数解释 |
$1：M-LAG系统信息 |
|
举例 |
Updated an M-LAG system: ID:[9b6fd1fe-975b-40e9-bce4-6cb4e3c9f215] Name:[mlag] Description:[null] JoinType:[USER_CREATE] restore delay: [22] |
|
日志说明 |
用户进行了修改M-LAG系统的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · You have no privilege to perform this operation：用户无权限执行此操作 · Unknown internal server error：未知的内部服务器错误 · The M-LAG system name already exists：M-LAG系统的名称已存在 · The M-LAG system name cannot be empty：M-LAG系统名称不能为空 · The M-LAG system name cannot exceed 255 characters：M-LAG系统名称最长255个字符 · The M-LAG system description cannot exceed 255 characters：M-LAG系统描述信息最长255个字符 · The device ID is not specified：未指定设备ID · The device does not exist：指定的设备不存在 · The M-LAG system does not exist：指定的M-LAG系统不存在 · Please specify the interface aggregation mode：接口聚合模式不能为空 · Invalid interface aggregation mode：无效的接口聚合模式 · If the peer link is a tunnel, the M-LAG system does not support excluding interfaces from the shutdown action by M-LAG MAD：当场景为隧道peer-link时，M-LAG系统不支持配置例外接口 · The interface name format is invalid：无效的例外接口名称格式 · The specified interface is already an excluded interface：指定的例外接口已存在 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · The data restoration delay must be an integer in the range of 1 to 3600：延迟恢复时间取值范围为1~3600的整数 |
|
关键字 |
DELETE_MLAG_SYSTEM_OP |
|
日志内容 |
Deleted M-LAG system “$1”. |
|
参数解释 |
$1：M-LAG系统信息 |
|
举例 |
Deleted M-LAG system: ID: [9b6fd1fe-975b-40e9-bce4-6cb4e3c9f215] Name: [mlag] Description: [无peer link mlag] joinType: [USER_CREATE] |
|
日志说明 |
用户进行了删除M-LAG系统的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · You have no privilege to perform this operation：用户无权限执行此操作 · Unknown internal server error：未知的内部服务器错误 · The M-LAG system does not exist：指定的M-LAG系统不存在 · Cannot delete the M-LAG system. It contains M-LAG groups：指定的M-LAG系统下存在M-LAG组，不允许删除 · Cannot delete the M-LAG system. It contains LAG groups：指定的M-LAG系统下存在设备内聚合接口，不允许删除 · The M-LAG group does not exist：指定的M-LAG组不存在 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
UPGRADE_MLAG_SYSTEM_OP |
|
日志内容 |
Upgraded an M-LAG system : “$1” |
|
参数解释 |
$1：M-LAG系统信息 |
|
举例 |
Upgraded an M-LAG system: ID:[9b6fd1fe-975b-40e9-bce4-6cb4e3c9f215] Name:[mlag] |
|
日志说明 |
用户进行了升级M-LAG系统的keepalive物理接口为聚合接口的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · You have no privilege to perform this operation：用户无权限执行此操作 · Unknown internal server error：未知的内部服务器错误 · The M-LAG system does not exist：指定的M-LAG系统不存在 · You cannot upgrade the keepalive link if it is a management link：Keepalive链路取值为管理网链路时，M-LAG系统不支持升级keepalive接口 · The keepalive interfaces of the MLAG system are already aggregate interfaces：M-LAG系统的Keepalive接口已是聚合接口 |
|
关键字 |
CREATE_MLAG_GROUP_OP |
|
日志内容 |
Created M-LAG group: “$1” |
|
参数解释 |
$1：M-LAG组信息 |
|
举例 |
Created M-LAG group: { "id": "fd6e250a-ab65-4b80-98b7-8a6d607d7a36", "data_source": "AUTO_ONLINE", "member_list": [ "5b1ae1a2-a26a-4625-8656-20d9dc62a27a", "1fe507b0-af05-40ef-9156-1a61542326c9" } |
|
日志说明 |
用户进行了创建M-LAG组的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · Bridge aggregation must be dynamic：二层聚合接口必须是动态聚合模式 · You must specify two different member devices for an M-LAG system：创建M-LAG系统设备不能是同一个设备 · The device already is an M-LAG system member：指定的设备已经和其他设备跨设备聚合 · The LAG interface does not exist：指定的设备内聚合接口不存在 · Please specify the M-LAG group ID range：没有指定M-LAG组编号范围 · The M-LAG system ID already exists：M-LAG系统的ID已存在 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · Failed to assign the specified M-LAG group ID：分配指定的M-LAG组编号失败 · The M-LAG group ID is in the range of 1 to 1024, and cannot exceed the maximum number supported by the device：M-LAG组编号范围为1-1024，且不可超过设备支持的最大编号 · All M-LAG group IDs have been assigned：M-LAG组编号已经全部分配完 · The specified M-LAG group ID is not in the configured M-LAG group ID range：指定的M-LAG组编号不在配置的M-LAG组编号范围内 · The specified M-LAG group ID has been assigned：指定的M-LAG组编号已经被占用 |
|
关键字 |
DELETE_MLAG_GROUP_OP |
|
日志内容 |
Deleted M-LAG group “$1”. |
|
参数解释 |
$1：M-LAG组ID |
|
举例 |
Deleted M-LAG group:ID:[7c6e2439-c245-44d7-a063-6a3dc8a12079]. |
|
日志说明 |
用户进行了删除M-LAG组操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · Unknown error：未知错误 · The LAG interface does not exist：指定的设备内聚合接口不存在 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
CREATE_CUSTOMIZED_DEVICE_INFO_OP |
|
日志内容 |
Customized configuration of $1 devices: $2 |
|
参数解释 |
$1：设备角色，包括Spine、Leaf、Aggregation、Access $2：用户自定义的设备定制信息 |
|
举例 |
Customized configuration of spine devices: [ [H3CS6800] driver = 6800 ##VXLAN resources ##Riot-mode start _vxlan_resource = l3gw40k _border_vxlan_resource = border40k ##Riot-mode end ##Switch-mode resources _switch_mode = 4 [H3CS125] driver = 125AF _vxlan_resource = normal [H3CS5560X] driver = 5560X _switch_mode = 1 _ecmp_num = 4 ]. |
|
日志说明 |
用户对指定设备进行了自定义设备定制信息的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The device does not exist：指定的设备不存在 · You have no privilege to perform this operation：用户无权限执行此操作 · The device role can only be spine, leaf, aggregation, or access：设备角色仅支持Spine、Leaf、Aggregation和Access |
|
关键字 |
DELETE_CUSTOMIZED_DEVICE_INFO_OP |
|
日志内容 |
Deleted configuration file $1 for $2 devices. |
|
参数解释 |
$1：文件名称 $2：设备角色，包括Spine、Leaf、Aggregation、Access |
|
举例 |
Deleted configuration file spine.config for spine devices. |
|
日志说明 |
用户进行了删除指定设备.config文件的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The device does not exist：指定的设备不存在 · You have no privilege to perform this operation：用户无权限执行此操作 · The device role can only be spine, leaf, aggregation, or access：设备角色仅支持Spine、Leaf、Aggregation和Access |
|
关键字 |
CREATE_IPPREFIX_OP |
|
日志内容 |
Created address prefix: $1 |
|
参数解释 |
$1：地址前缀配置信息 |
|
举例 |
Created address prefix: [ ipPrefix UUID:[1459ae05-70bf-44ef-8aa9-328838611ace] ipPrefix name:[111] ipPrefix ipVersion:[4] ipPrefix description:[] ipPrefix tenantId:[3d2c2819-1106-4e81-867d-38907a2bd20b] ipPrefix rules:[[]]] |
|
日志说明 |
用户进行了添加地址前缀的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · Invalid JSON format：无效的JSON格式 · The address prefix already exists：地址前缀已存在 · Invalid name：无效的名称 · Invalid description：无效的描述 · Duplicate name exists：存在重复的名称 · Invalid IP version：无效的IP版本 · Invalid tenant ID：无效的租户ID · You have no privilege to perform this operation：用户无权限执行此操作 · The address prefix ID already exists：地址前缀ID已存在 |
|
关键字 |
UPDATE_IPPREFIX_OP |
|
日志内容 |
Updated address prefix: $1 |
|
参数解释 |
$1：地址前缀配置信息 |
|
举例 |
Updated address prefix: ipPrefix UUID:[66132e94-22fb-443c-9472-4d2e55c1ac0a] ipPrefix name:[1] ipPrefix ipVersion:[4] ipPrefix description:[] ipPrefix tenantId:[ef7fbcf5-aecd-45f6-9f69-fee7329b208d] ipPrefix rules:[[ ipPrefixRule UUID:[23e6d07e-ca28-4925-93c0-46003e7da0eb] ipPrefixRule prefixId:[66132e94-22fb-443c-9472-4d2e55c1ac0a] ipPrefixRule indexNumber:[1] ipPrefixRule permit:[true] ipPrefixRule ipPrefix:[0.0.0.0] ipPrefixRule mask:[1] ipPrefixRule lessEqual:[1] ipPrefixRule greatEqual:[1]]] |
|
日志说明 |
用户进行了更新地址前缀的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · Invalid JSON format：无效的JSON格式 · The specified address prefix does not exist：指定的地址前缀不存在 · Invalid description：无效的描述 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
DELETE_IPPREFIX_OP |
|
日志内容 |
Deleted address prefix: $1 |
|
参数解释 |
$1：地址前缀配置信息 |
|
举例 |
Deleted address prefix: ipPrefix UUID:[960e15c4-4274-499a-9643-a22da32a64ae] ipPrefix name:[ip_prefix] ipPrefix ipVersion:[4] ipPrefix description:[ip_prefix] ipPrefix tenantId:[4607eb06-0b5d-45b0-bf13-6d94344ac3df] ipPrefix rules: [ [ ipPrefixRule UUID:[a8134e8f-084b-44bb-bd73-8778a216bd1d] ipPrefixRule prefixId:[960e15c4-4274-499a-9643-a22da32a64ae] ipPrefixRule indexNumber:[22] ipPrefixRule permit:[true] ipPrefixRule ipPrefix:[22.22.0.0] ipPrefixRule mask:[16] ipPrefixRule lessEqual:[18] ipPrefixRule greatEqual:[22] ] ] |
|
日志说明 |
用户进行了删除地址前缀的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · The specified address prefix does not exist：指定的地址前缀不存在 · Cannot delete the address prefix because it has been bound to a routing policy：地址前缀已被路由策略绑定，不允许删除 · Cannot delete the address prefix because it has prefix rules configured：地址前缀存在前缀规则，不允许删除 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_IPPREFIXRULE_OP |
|
日志内容 |
Created address prefix rule: $1 |
|
参数解释 |
$1：地址前缀规则配置信息 |
|
举例 |
Created address prefix rule: [ ipPrefixRule UUID:[23e6d07e-ca28-4925-93c0-46003e7da0eb] ipPrefixRule prefixId:[66132e94-22fb-443c-9472-4d2e55c1ac0a] ipPrefixRule indexNumber:[1] ipPrefixRule permit:[true] ipPrefixRule ipPrefix:[0.0.0.0] ipPrefixRule mask:[0] ipPrefixRule lessEqual:[1] ipPrefixRule greatEqual:[1]] |
|
日志说明 |
用户进行了添加地址前缀规则的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · Invalid JSON format：无效的JSON格式 · The specified address prefix does not exist：指定的地址前缀不存在 · Duplicate index exists：存在重复的索引 · Please specify an address prefix UUID：地址前缀UUID不能为空 · Please specify a mode：模式不能为空 · Invalid mode：无效的模式 · Invalid network address：无效的前缀网段 · Please specify an ID：索引不能为空 · Invalid index：无效的索引 · The ID already exists：索引已存在 · Invalid minimum prefix length：无效的最小前缀长度 · Invalid maximum prefix length：无效的最大前缀长度 · Different prefix rules cannot have the same match criteria：存在重复匹配条件的前缀规则 · A prefix rule with the same match criteria already exists：已存在相同匹配条件的前缀规则 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · The address prefix rule ID already exists：地址前缀规则ID已存在 |
|
关键字 |
UPDATE_IPPREFIXRULE_OP |
|
日志内容 |
Updated address prefix rule: $1 |
|
参数解释 |
$1：地址前缀规则配置信息 |
|
举例 |
Updated address prefix rule: ipPrefixRule UUID:[23e6d07e-ca28-4925-93c0-46003e7da0eb] ipPrefixRule prefixId:[66132e94-22fb-443c-9472-4d2e55c1ac0a] ipPrefixRule indexNumber:[1] ipPrefixRule permit:[true] ipPrefixRule ipPrefix:[0.0.0.0] ipPrefixRule mask:[1] ipPrefixRule lessEqual:[1] ipPrefixRule greatEqual:[1] |
|
日志说明 |
用户进行了更新地址前缀规则的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · Invalid JSON format：无效的JSON格式 · The specified prefix rule does not exist：指定的前缀规则不存在 · Invalid mode：无效的模式 · Invalid network address：无效的前缀网段 · Invalid minimum prefix length：无效的最小前缀长度 · Invalid maximum prefix length：无效的最大前缀长度 · A prefix rule with the same match criteria already exists：已存在相同匹配条件的前缀规则 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
DELETE_IPPREFIXRULE_OP |
|
日志内容 |
Deleted address prefix rule: $1 |
|
参数解释 |
$1：地址前缀规则配置信息 |
|
举例 |
Deleted address prefix rule: ipPrefixRule UUID:[4fa579be-a6bb-49d6-b589-c19b11c7e9c2] ipPrefixRule prefixId:[960e15c4-4274-499a-9643-a22da32a64ae] ipPrefixRule indexNumber:[23] ipPrefixRule permit:[true] ipPrefixRule ipPrefix:[22.22.0.0] ipPrefixRule mask:[15] ipPrefixRule lessEqual:[16] ipPrefixRule greatEqual:[19] |
|
日志说明 |
用户进行了删除地址前缀规则的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · The specified prefix rule does not exist：指定的前缀规则不存在 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
CREATE_ROUTE_POLICY_OP |
|
日志内容 |
Created routing policy: $1 |
|
参数解释 |
$1：路由策略配置信息 |
|
举例 |
Created routing policy:[ id: bff339b7-07f0-4caa-82ed-d642c0394284 name: adads description: tenantId: c4468dbb-ab73-4c35-b3eb-bb09715e6f90 nodes: []] |
|
日志说明 |
用户进行了添加路由策略的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · Invalid JSON format：无效的JSON格式 · Invalid parameter：无效的参数 · Invalid description：无效的描述 · Invalid name：无效的名称 · The specified tenant does not exist：指定的租户不存在 · Please specify a mode：模式不能为空 · A routing policy already exists with the specified name：路由策略名称已存在 · Please specify a name：名称不能为空 · Invalid tenant ID：无效的租户ID · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_ROUTE_POLICY_OP |
|
日志内容 |
Updated routing policy: $1 |
|
参数解释 |
$1：路由策略配置信息 |
|
举例 |
Updated routing policy: id: 5ebe31ca-b07a-4d28-8ece-f43a790e8b57 name: route description: route tenantId: c4468dbb-ab73-4c35-b3eb-bb09715e6f90 nodes: [ id: c7133f3c-46d0-4446-b93b-e9cbfa108aee type: address-prefix permit: false number: 123 ipv4PrefixId: ed43ae0f-fe4b-495e-9206-06104ad70256 policyId: 5ebe31ca-b07a-4d28-8ece-f43a790e8b57] |
|
日志说明 |
用户进行了更新路由策略的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · Invalid JSON format：无效的JSON格式 · Invalid parameter：无效的参数 · Invalid description：无效的描述 · Cannot edit the routing policy UUID：路由策略UUID不允许修改 · The specified routing policy does not exist：指定的路由策略不存在 · Cannot edit the routing policy name：路由策略名称不允许修改 · The specified resource does not exist：指定的资源不存在 · The tenant ID cannot be modified：租户ID不允许修改 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
DELETE_ROUTE_POLICY_OP |
|
日志内容 |
Deleted routing policy: $1 |
|
参数解释 |
$1：路由策略配置信息 |
|
举例 |
Deleted routing policy: { "RoutePolicyConfig": { "id":498ce629-7839-4225-b7e3-d9628e6df7d1, "decodeId":null, "name":"router_policy", "tenantId":4607eb06-0b5d-45b0-bf13-6d94344ac3df, "desc":"router policy", "ipVersion":4, "nodes":[] } } |
|
日志说明 |
用户进行了删除路由策略的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · The specified routing policy does not exist：指定的路由策略不存在 · Cannot delete the routing policy because it has nodes configured：路由策略存在节点，不允许删除 · Cannot delete the routing policy because it has been bound to an OSPF policy：路由策略已被OSPF策略绑定，不允许删除 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_ROUTE_POLICY_NODE_OP |
|
日志内容 |
Created routing policy node: $1 |
|
参数解释 |
$1：路由策略节点配置信息 |
|
举例 |
Created routing policy node:[ id: 774a9a81-eabe-4f06-8f05-1e7e7f64fbe3 type: permit: false number: 0 ipv4PrefixId: policyId: bff339b7-07f0-4caa-82ed-d642c0394284] |
|
日志说明 |
用户进行了添加路由策略节点的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · Invalid JSON format：无效的JSON格式 · Invalid parameter：无效的参数 · Invalid match rule：无效的匹配规则 · Please specify a node number：节点序列号不能为空 · The specified routing policy does not exist：指定的路由策略不存在 · Please specify a routing policy ID：路由策略ID不能为空 · Duplicate node number exists：存在重复的节点序列号 · The routing policy node already exists：路由策略节点已存在 · The specified node number already exists：指定的节点序列号已存在 · The specifiedaddress prefix does not exist：指定的地址前缀不存在 · Invalid number：无效的路由策略节点序列号 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
UPDATE_ROUTE_POLICY_NODE_OP |
|
日志内容 |
Updated routing policy node: $1 |
|
参数解释 |
$1：路由策略节点配置信息 |
|
举例 |
Updated routing policy node: id: 3cdd1179-239a-4705-9cb8-427fceb0733d type: permit: false number: 0 ipv4PrefixId: policyId: 850f2fce-c246-4fad-84c6-b565c4d31b1d |
|
日志说明 |
用户进行了更新路由策略节点的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · Invalid JSON format：无效的JSON格式 · Invalid parameter：无效的参数 · Invalid match rule：无效的匹配规则 · annot edit the routing policy UUID：路由策略UUID不允许修改 · The specifiedaddress prefix does not exist：指定的地址前缀不存在 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
DELETE_ROUTE_POLICY_NODE_OP |
|
日志内容 |
Deleted routing policy node: $1 |
|
参数解释 |
$1：路由策略节点配置信息 |
|
举例 |
Deleted routing policy node: { "RoutePolicyNodeConfig": { "id":"d5fabf1b-8ac8-4503-b0e4-c5c5a63250f1", "policyId":498ce629-7839-4225-b7e3-d9628e6df7d1, "type":"address-prefix", "permit":true, "number":21, "ipv4PrefixId":"960e15c4-4274-499a-9643-a22da32a64ae", "ipv6PrefixId":"null" } } |
|
日志说明 |
用户进行了删除路由策略节点的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · The specified resource does not exist：指定的资源不存在 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
CREATE_OSPF_POLICY_OP |
|
日志内容 |
Created OSPF policy: $1 |
|
参数解释 |
$1：OSPF策略配置信息 |
|
举例 |
Created OSPF policy: [{"OspfPolicyConfig":{"id":be246f5f-1945-4aaf-a189-eecc3d61234e, "name":"ccccz", "tenantId":ffffffff-0000-0000-0000-000000000001, "description":"", "ipVersion":4, "nsr":false, "fabricImportOspfRoutePolicy":null, "fabricImportOspfRoutePolicyName":"null", "loopbackDetection":false, "ospfAreaConfigs":[], "ospfImportRouteConfigs":[], "ospfInterfacePolicyConfigs":[]}}] |
|
日志说明 |
用户进行了添加OSPF策略的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · ion recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · Invalid JSON format：无效的JSON格式 · Invalid parameter：无效的参数 · Invalid name：无效的名称 · Invalid description：无效的描述 · The specified tenant does not exist：指定的租户不存在 · Invalid IP version：无效的IP版本 · The specified routing policy does not exist：指定的路由策略不存在 · The OSPF policy name already exists：OSPF策略名称已存在 · An OSPF policy already exists with the specified name：存在重复的OSPF策略名称 · Invalid tenant ID：无效的租户ID · You have no privilege to perform this operation：用户无权限执行此操作 · IP version mismatch：IP版本不一致 · The OSPF policy ID already exists：OSPF策略ID已存在 |
|
关键字 |
UPDATE_OSPF_POLICY_OP |
|
日志内容 |
Updated OSPF policy: $1 |
|
参数解释 |
$1：OSPF策略配置信息 |
|
举例 |
Updated OSPF policy:{"OspfPolicyConfig":{ "id":3d416fc0-5846-4693-863b-3115f54c37dd, "name":"shw_ospf_2", "tenantId":fa580b08-9f94-4ccb-b53f-8e84841df8f2, "description":"", "ipVersion":4, "nsr":false, "routerId":"1.1.1.1", "fabricImportOspfRoutePolicy":null, "fabricImportOspfRoutePolicyName":"null", "loopbackDetection":false, "ospfAreaConfigs":[], "ospfImportRouteConfigs":[], "ospfInterfacePolicyConfigs":[]}} |
|
日志说明 |
用户进行了更新OSPF策略的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · Invalid JSON format：无效的JSON格式 · Invalid parameter：无效的参数 · Invalid description：无效的描述 · The specified OSPF or OSPFv3 policy does not exist：指定的OSPF或OSPFv3策略不存在 · The specified routing policy does not exist：指定的路由策略不存在 · Cannot edit the OSPF policy name：OSPF策略名称不允许修改 · You have no privilege to perform this operation：用户无权限执行此操作 · IP version mismatch：IP版本不一致 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
DELETE_OSPF_POLICY_OP |
|
日志内容 |
Deleted OSPF policy: $1 |
|
参数解释 |
$1：OSPF策略配置信息 |
|
举例 |
Deleted OSPF policy: { "OspfPolicyConfig": { "id":5a53d2e1-e939-40e1-b7ce-2eb0ef761010, "name":"ospf_policy", "tenantId":4607eb06-0b5d-45b0-bf13-6d94344ac3df, "description":"ospf policy", "ipVersion":4, "nsr":true, "fabricImportOspfRoutePolicy":498ce629-7839-4225-b7e3-d9628e6df7d1, "fabricImportOspfRoutePolicyName":"router_policy", "loopbackDetection":false, "ospfAreaConfigs":[], "ospfImportRouteConfigs":[], "ospfInterfacePolicyConfigs":[] } } |
|
日志说明 |
用户进行了删除OSPF策略的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · The specified OSPF policy does not exist：指定的OSPF策略不存在 · Cannot delete the OSPF policy because it contains area, route redistribution, or interface policy settings：OSPF策略下存在区域、路由引入或接口策略，不允许删除 · Cannot delete the OSPF policy because it has been bound：OSPF策略被绑定，不允许删除 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_OSPFV3_POLICY_OP |
|
日志内容 |
Created OSPFv3 policy: $1 |
|
参数解释 |
$1：OSPFv3策略配置信息 |
|
举例 |
Created OSPFv3 policy:[{ "OspfPolicyConfig":{ "id":bf97cd8e-4e46-4554-9366-469301279f1c, "name":"fds", "tenantId":null, "description":"", "ipVersion":6, "nsr":false, "fabricImportOspfRoutePolicy":null, "fabricImportOspfRoutePolicyName":"null", "loopbackDetection":false, "ospfAreaConfigs":[], "ospfImportRouteConfigs":[], "ospfInterfacePolicyConfigs":[] } }] |
|
日志说明 |
用户进行了添加OSPFv3策略的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · ion recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · Invalid JSON format：无效的JSON格式 · Invalid parameter：无效的参数 · Invalid name：无效的名称 · Invalid description：无效的描述 · The specified tenant does not exist：指定的租户不存在 · Invalid IP version：无效的IP版本 · The specified routing policy does not exist：指定的路由策略不存在 · The OSPFv3 policy name already exists：OSPv3策略名称已存在 · An OSPFv3 policy already exists with the specified name：存在重复的OSPFv3策略名称 · Invalid tenant ID：无效的租户ID · You have no privilege to perform this operation：用户无权限执行此操作 · IP version mismatch：IP版本不一致 |
|
关键字 |
UPDATE_OSPFV3_POLICY_OP |
|
日志内容 |
Updated OSPFv3 policy: $1 |
|
参数解释 |
$1：OSPFv3策略配置信息 |
|
举例 |
Updated OSPFv3 policy:[{ "OspfPolicyConfig":{ "id":224318aa-8a75-488e-a030-4fae5a1fdd23, "name":"testv6", "tenantId":null, "description":"", "ipVersion":6, "nsr":false, "fabricImportOspfRoutePolicy":null, "fabricImportOspfRoutePolicyName":"null", "loopbackDetection":false, "ospfAreaConfigs":[], "ospfImportRouteConfigs":[], "ospfInterfacePolicyConfigs":[{ "OspfInterfacePolicyConfig":{ "id":0835de81-4459-446e-9860-b2f5c6bdb7e6, "ospfPolicyId":224318aa-8a75-488e-a030-4fae5a1fdd23, "name":"2", "vsiName":"null", "description":"null", "networkType":null, "interfaceCost":null, "bfdEnable":false, "deadTimer":2, "drPriority":1, "helloTimer":null, "ospfInstanceName":null, "authentications":[] } }] |
|
日志说明 |
用户进行了更新OSPFv3策略的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · Invalid JSON format：无效的JSON格式 · Invalid parameter：无效的参数 · Invalid description：无效的描述 · The specified OSPF or OSPFv3 policy does not exist：指定的OSPF或OSPFv3策略不存在 · The specified routing policy does not exist：指定的路由策略不存在 · Cannot edit the OSPFv3 policy name：OSPFv3策略名称不允许修改 · You have no privilege to perform this operation：用户无权限执行此操作 · IP version mismatch：IP版本不一致 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
DELETE_OSPFV3_POLICY_OP |
|
日志内容 |
Deleted OSPFv3 policy: $1 |
|
参数解释 |
$1：OSPFv3策略配置信息 |
|
举例 |
Deleted OSPFv3 policy: { "OspfPolicyConfig": { "id":5a53d2e1-e939-40e1-b7ce-2eb0ef761010, "name":"ospfv3_policy", "tenantId":4607eb06-0b5d-45b0-bf13-6d94344ac3df, "description":"ospfv3 policy", "ipVersion":6, "nsr":true, "fabricImportOspfRoutePolicy":498ce629-7839-4225-b7e3-d9628e6df7d1, "fabricImportOspfRoutePolicyName":"router_policy", "loopbackDetection":false, "ospfAreaConfigs":[], "ospfImportRouteConfigs":[], "ospfInterfacePolicyConfigs":[] } } |
|
日志说明 |
用户进行了删除OSPFv3策略的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · The specified OSPF or OSPFv3 policy does not exist：指定的OSPF或者OSPFv3策略不存在 · Cannot delete the OSPFv3 policy because it contains area, route redistribution, or interface policy settings：OSPFv3策略下存在区域、路由引入或接口策略，不允许删除 · Cannot delete the OSPFv3 policy because it has been bound：OSPFv3策略被绑定，不允许删除 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_OSPF_AREA_OP |
|
日志内容 |
Created OSPF area: $1 |
|
参数解释 |
$1：OSPF区域配置信息 |
|
举例 |
Created OSPF area:[{"OspfAreaConfig":{ "id":1220cc43-9bee-4204-b445-ff98f1ed7cfd, "ospfPolicyId":ba460ae5-483d-4698-aca1-45b27a090024, "type":0, "areaId":"23.24.24.5", "network":"null", "mask":null, "tenantID":null}}] |
|
日志说明 |
用户进行了添加OSPF区域的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · Invalid JSON format：无效的JSON格式 · Invalid parameter：无效的参数 · Invalid network address：无效的网络地址 · Invalid area type：无效的区域类型 · Invalid area ID：无效的区域ID · The specified OSPF policy does not exist：指定的OSPF策略不存在 · The area newtork overlaps with another area newtork：区域网络重叠 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
UPDATE_OSPF_AREA_OP |
|
日志内容 |
Updated OSPF area: $1 |
|
参数解释 |
$1：OSPF区域配置信息 |
|
举例 |
Updated OSPF area:{"OspfAreaConfig":{ "id":076aec50-2f8c-4832-bb1e-3553f2f55138, "ospfPolicyId":5289f321-6ee2-40ef-9124-08d5010b4843, "type":0, "areaId":"0.0.0.0", "network":"52.1.1.0", "mask":24, "tenantID":null}} |
|
日志说明 |
用户进行了更新OSPF区域的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · Invalid JSON format：无效的JSON格式 · Invalid parameter：无效的参数 · Invalid network address：无效的网络地址 · Invalid area type：无效的区域类型 · The area newtork overlaps with another area newtork：区域网络重叠 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
DELETE_OSPF_AREA_OP |
|
日志内容 |
Deleted OSPF area: $1 |
|
参数解释 |
$1：OSPF区域配置信息 |
|
举例 |
Deleted OSPF area: { "OspfAreaConfig": { "id":e02dcb2a-3fea-4811-ac31-0527a53d13f8, "ospfPolicyId":5a53d2e1-e939-40e1-b7ce-2eb0ef761010, "type":0, "areaId":"0.0.0.0" } } |
|
日志说明 |
用户进行了删除OSPF区域的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · The specified OSPF area does not exist：指定的OSPF区域不存在 · Cannot delete the area because it has been bound to an interface policy：区域已被接口策略绑定，不允许删除 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
CREATE_OSPFV3_AREA_OP |
|
日志内容 |
Created OSPFv3 area: $1 |
|
参数解释 |
$1：OSPFv3区域配置信息 |
|
举例 |
Created OSPFv3 area:[{"OspfAreaConfig":{ "id":1220cc43-9bee-4204-b445-ff98f1ed7cfd, "ospfPolicyId":ba460ae5-483d-4698-aca1-45b27a090024, "type":0, "areaId":"23.24.24.5", "network":"null", "mask":null, "tenantID":null}}] |
|
日志说明 |
用户进行了添加OSPFv3区域的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · Invalid JSON format：无效的JSON格式 · Invalid parameter：无效的参数 · Invalid network address：无效的网络地址 · Invalid area type：无效的区域类型 · Invalid area ID：无效的区域ID · The specified OSPF policy does not exist：指定的OSPF策略不存在 · The area newtork overlaps with another area newtork：区域网络重叠 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
UPDATE_OSPFV3_AREA_OP |
|
日志内容 |
Updated OSPFv3 area: $1 |
|
参数解释 |
$1：OSPFv3区域配置信息 |
|
举例 |
Updated OSPFv3 area:{"OspfAreaConfig":{ "id":076aec50-2f8c-4832-bb1e-3553f2f55138, "ospfPolicyId":5289f321-6ee2-40ef-9124-08d5010b4843, "type":0, "areaId":"0.0.0.0", "network":"52.1.1.0", "mask":24, "tenantID":null}} |
|
日志说明 |
用户进行了更新OSPFv3区域的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · Invalid JSON format：无效的JSON格式 · Invalid parameter：无效的参数 · Invalid network address：无效的网络地址 · Invalid area type：无效的区域类型 · The area newtork overlaps with another area newtork：区域网络重叠 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
DELETE_OSPFV3_AREA_OP |
|
日志内容 |
Deleted OSPFv3 area: $1 |
|
参数解释 |
$1：OSPFv3区域配置信息 |
|
举例 |
Deleted OSPFv3 area: { "OspfAreaConfig": { "id":e02dcb2a-3fea-4811-ac31-0527a53d13f8, "ospfPolicyId":5a53d2e1-e939-40e1-b7ce-2eb0ef761010, "type":0, "areaId":"0.0.0.0" } } |
|
日志说明 |
用户进行了删除OSPFv3区域的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · The specified OSPF area does not exist：指定的OSPF区域不存在 · Cannot delete the area because it has been bound to an interface policy：区域已被接口策略绑定，不允许删除 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
ENABLED_OSPF_IMPORT_ROUTE_OP |
|
日志内容 |
Enabled OSPF route redistribution rule: $1 |
|
参数解释 |
$1：OSPF路由引入配置信息 |
|
举例 |
Enabled OSPF route redistribution rule:[{"OspfImportRouteConfig":{ "id":5cb92655-8a6b-4847-9fec-75b9ed331f00, "ospfPolicyId":50724bf4-9367-4941-af47-a98ce0dcfa06, "cost":"2", "protocol":"bgp", "asNumber":"1", "allowIbgp":true, "routePolicyId":null, "routePolicyName":"null"}}] |
|
日志说明 |
用户进行了添加OSPF路由引入的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · Invalid JSON format：无效的JSON格式 · Invalid parameter：无效的参数 · Invalid protocol：无效的引入协议 · The protocol has already been specified：存在重复的引入协议 · Invalid route cost：无效的路由开销 · Invalid allow_ibgp：无效的引入IBGP值 · Invalid process ID：无效的引入进程号 · The specified OSPF policy does not exist：指定的OSPF策略不存在 · The specified routing policy does not exist：指定的路由策略不存在 · Invalid OSPF policy UUID：无效的OSPF策略UUID · You have no privilege to perform this operation：用户无权限执行此操作 · IP version mismatch：IP版本不一致 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · Invalid value for the redistribtution_method field：redistribtution_method字段取值无效 · The ID already exists：指定的ID已存在 · The route redistribution ID already exists：路由引入ID已存在 |
|
关键字 |
UPDATE_OSPF_IMPORT_ROUTE_OP |
|
日志内容 |
Updated OSPF route redistribution rule: $1 |
|
参数解释 |
$1：OSPF路由引入配置信息 |
|
举例 |
Updated OSPF route redistribution rule:{"OspfImportRouteConfig":{ "id":dbb18f11-1d43-4498-89ef-0ef661d92676, "ospfPolicyId":5af962ab-fefe-43f9-8d5f-f0c77c5cf4d0, "cost":"1", "protocol":"bgp", "asNumber":"1", "allowIbgp":true, "routePolicyId":850f2fce-c246-4fad-84c6-b565c4d31b1d, "routePolicyName":"2"}} |
|
日志说明 |
用户进行了更新OSPF路由引入的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · Invalid JSON format：无效的JSON格式 · Invalid parameter：无效的参数 · Invalid protocol：无效的引入协议 · The protocol has already been specified：存在重复的引入协议 · Invalid route cost：无效的路由开销 · Invalid allow_ibgp：无效的引入IBGP值 · Invalid process ID：无效的引入进程号 · The specified routing policy does not exist：指定的路由策略不存在 · Invalid OSPF policy UUID：无效的OSPF策略UUID · The specified resource does not exist：指定的资源不存在 · You have no privilege to perform this operation：用户无权限执行此操作 · IP version mismatch：IP版本不一致 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · Invalid value for the redistribtution_method field：redistribtution_method字段取值无效 |
|
关键字 |
DISABLED_OSPF_IMPORT_ROUTE_OP |
|
日志内容 |
Disabled OSPF route redistribution rule: $1 |
|
参数解释 |
$1：OSPF路由引入配置信息 |
|
举例 |
Disabled OSPF route redistribution rule: { "OspfImportRouteConfig": { "id":9178924a-8d3a-4651-9fd1-e33ac01b73aa, "ospfPolicyId":5a53d2e1-e939-40e1-b7ce-2eb0ef761010, "cost":"22", "protocol":"bgp", "asNumber":"22", "allowIbgp":true, "routePolicyId":498ce629-7839-4225-b7e3-d9628e6df7d1, "routePolicyName":"router_policy" } } |
|
日志说明 |
用户进行了删除OSPF路由引入的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · The specified resource does not exist：指定的资源不存在 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
ENABLED_OSPFV3_IMPORT_ROUTE_OP |
|
日志内容 |
Enabled OSPFv3 route redistribution rule: $1 |
|
参数解释 |
$1：OSPFv3路由引入配置信息 |
|
举例 |
Enabled OSPFv3 route redistribution rule:[{"OspfImportRouteConfig":{ "id":5cb92655-8a6b-4847-9fec-75b9ed331f00, "ospfPolicyId":50724bf4-9367-4941-af47-a98ce0dcfa06, "cost":"2", "protocol":"bgp", "asNumber":"1", "allowIbgp":true, "routePolicyId":null, "routePolicyName":"null"}}] |
|
日志说明 |
用户进行了添加OSPFv3路由引入的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · Invalid JSON format：无效的JSON格式 · Invalid parameter：无效的参数 · Invalid protocol：无效的引入协议 · The protocol has already been specified：存在重复的引入协议 · Invalid route cost：无效的路由开销 · Invalid allow_ibgp：无效的引入IBGP值 · Invalid process ID：无效的引入进程号 · The specified OSPF policy does not exist：指定的OSPF策略不存在 · The specified routing policy does not exist：指定的路由策略不存在 · Invalid OSPF policy UUID：无效的OSPF策略UUID · You have no privilege to perform this operation：用户无权限执行此操作 · IP version mismatch：IP版本不一致 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · The ID already exists：指定的ID已存在 |
|
关键字 |
UPDATE_OSPFV3_IMPORT_ROUTE_OP |
|
日志内容 |
Updated OSPFv3 route redistribution rule: $1 |
|
参数解释 |
$1：OSPFv3路由引入配置信息 |
|
举例 |
Updated OSPFv3 route redistribution rule:{"OspfImportRouteConfig":{ "id":dbb18f11-1d43-4498-89ef-0ef661d92676, "ospfPolicyId":5af962ab-fefe-43f9-8d5f-f0c77c5cf4d0, "cost":"1", "protocol":"bgp", "asNumber":"1", "allowIbgp":true, "routePolicyId":850f2fce-c246-4fad-84c6-b565c4d31b1d, "routePolicyName":"2"}} |
|
日志说明 |
用户进行了更新OSPFv3路由引入的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · Invalid JSON format：无效的JSON格式 · Invalid parameter：无效的参数 · Invalid protocol：无效的引入协议 · The protocol has already been specified：存在重复的引入协议 · Invalid route cost：无效的路由开销 · Invalid allow_ibgp：无效的引入IBGP值 · Invalid process ID：无效的引入进程号 · The specified routing policy does not exist：指定的路由策略不存在 · Invalid OSPF policy UUID：无效的OSPF策略UUID · The specified resource does not exist：指定的资源不存在 · You have no privilege to perform this operation：用户无权限执行此操作 · IP version mismatch：IP版本不一致 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
DISABLED_OSPFV3_IMPORT_ROUTE_OP |
|
日志内容 |
Disabled OSPFv3 route redistribution rule: $1 |
|
参数解释 |
$1：OSPFv3路由引入配置信息 |
|
举例 |
Disabled OSPFv3 route redistribution rule: { "OspfImportRouteConfig": { "id":9178924a-8d3a-4651-9fd1-e33ac01b73aa, "ospfPolicyId":5a53d2e1-e939-40e1-b7ce-2eb0ef761010, "cost":"22", "protocol":"bgp", "asNumber":"22", "allowIbgp":true, "routePolicyId":498ce629-7839-4225-b7e3-d9628e6df7d1, "routePolicyName":"router_policy" } } |
|
日志说明 |
用户进行了删除OSPFv3路由引入的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · The specified resource does not exist：指定的资源不存在 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
CREATE_OSPF_INTERFACE_POLICY_OP |
|
日志内容 |
Created OSPF interface policy: $1 |
|
参数解释 |
$1：OSPF接口策略配置信息 |
|
举例 |
Created OSPF interface policy:[{"OspfInterfacePolicyConfig":{ "id":bdc309e3-2158-478a-9563-70cc00836d43, "ospfPolicyId":ba460ae5-483d-4698-aca1-45b27a090024, "name":"22", "vsiName":"null", "description":"null", "networkType":1, "areaId":"23.24.24.5", "interfaceCost":null, "bfdEnable":false, "deadTimer":null, "drPriority":1, "helloTimer":null, "ospfInstanceName":null}}] |
|
日志说明 |
用户进行了添加OSPF接口策略的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · Invalid JSON format：无效的JSON格式 · Invalid parameter：无效的参数 · Invalid network type：无效的接口网络类型 · The interface policy name already exists：接口策略名称已存在 · Invalid name：无效的名称 · Invalid interface cost：无效的接口开销 · Invalid description：无效的描述 · Invalid hello interval：无效的HELLO报文间隔 · Invalid dead interval：无效的邻居失效时间 · Invalid router priority：无效的路由器优先级 · The specified OSPF policy does not exist：指定的OSPF策略不存在 · The specified OSPF area does not exist：指定的OSPF区域不存在 · Invalid area ID：无效的区域ID · You have no privilege to perform this operation：用户无权限执行此操作 · The interface policy ID already exists：接口策略ID已存在 |
|
关键字 |
UPDATE_OSPF_INTERFACE_POLICY_OP |
|
日志内容 |
Updated OSPF interface policy: $1 |
|
参数解释 |
$1：OSPF接口策略配置信息 |
|
举例 |
Updated OSPF interface policy:[{"OspfInterfacePolicyConfig":{ "id":bdc309e3-2158-478a-9563-70cc00836d43, "ospfPolicyId":ba460ae5-483d-4698-aca1-45b27a090024, "name":"22", "vsiName":"null", "description":"null", "networkType":1, "areaId":"23.24.24.5", "interfaceCost":null, "bfdEnable":false, "deadTimer":null, "drPriority":1, "helloTimer":null, "ospfInstanceName":null}}] |
|
日志说明 |
用户进行了更新OSPF接口策略的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · Invalid JSON format：无效的JSON格式 · Invalid parameter：无效的参数 · Invalid network type：无效的接口网络类型 · Invalid interface cost：无效的接口开销 · Invalid description：无效的描述 · Invalid hello interval：无效的HELLO报文间隔 · Invalid dead interval：无效的邻居失效时间 · Invalid router priority：无效的路由器优先级 · The specified OSPF area does not exist：指定的OSPF区域不存在 · Invalid area ID：无效的区域ID · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
DELETE_OSPF_INTERFACE_POLICY_OP |
|
日志内容 |
Deleted OSPF interface policy: $1 |
|
参数解释 |
$1：OSPF接口策略配置信息 |
|
举例 |
Deleted OSPF interface policy: { "OspfInterfacePolicyConfig": { "id":a20ea450-2628-42b8-9d8e-ade68c2eab14, "ospfPolicyId":5a53d2e1-e939-40e1-b7ce-2eb0ef761010, "name":"interface_policy", "vsiName":"null", "description":"interface policy", "networkType":1, "interfaceCost":22, "bfdEnable":false, "deadTimer":22, "drPriority":1, "helloTimer":22, "ospfInstanceName":null, "authentications": [ { "OspfInterfaceAuthentication": { "id":7b3173a9-3191-4aae-ae97-42dd45921a6c, "authenticationMode":1, "keyId":22, "cipher":2, "password":"********" } } ] } } |
|
日志说明 |
用户进行了删除OSPF接口策略的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · The specified interface policy does not exist：指定的接口策略不存在 · Cannot delete the interface policy because it has been bound：OSPF接口策略被绑定，不允许删除 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_OSPFV3_INTERFACE_POLICY_OP |
|
日志内容 |
Created OSPFv3 interface policy: $1 |
|
参数解释 |
$1：OSPFv3接口策略配置信息 |
|
举例 |
Created OSPFv3 interface policy:[{"OspfInterfacePolicyConfig":{ "id":bdc309e3-2158-478a-9563-70cc00836d43, "ospfPolicyId":ba460ae5-483d-4698-aca1-45b27a090024, "name":"22", "vsiName":"null", "description":"null", "networkType":1, "areaId":"23.24.24.5", "interfaceCost":null, "bfdEnable":false, "deadTimer":null, "drPriority":1, "helloTimer":null, "ospfInstanceName":null}}] |
|
日志说明 |
用户进行了添加OSPFv3接口策略的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · Invalid JSON format：无效的JSON格式 · Invalid parameter：无效的参数 · Invalid network type：无效的接口网络类型 · The interface policy name already exists：接口策略名称已存在 · Invalid name：无效的名称 · Invalid interface cost：无效的接口开销 · Invalid description：无效的描述 · Invalid hello interval：无效的HELLO报文间隔 · Invalid dead interval：无效的邻居失效时间 · Invalid router priority：无效的路由器优先级 · The specified OSPF policy does not exist：指定的OSPF策略不存在 · The specified OSPF area does not exist：指定的OSPF区域不存在 · Invalid area ID：无效的区域ID · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_OSPFV3_INTERFACE_POLICY_OP |
|
日志内容 |
Updated OSPFv3 interface policy: $1 |
|
参数解释 |
$1：OSPFv3接口策略配置信息 |
|
举例 |
Updated OSPFv3 interface policy:[{"OspfInterfacePolicyConfig":{ "id":bdc309e3-2158-478a-9563-70cc00836d43, "ospfPolicyId":ba460ae5-483d-4698-aca1-45b27a090024, "name":"22", "vsiName":"null", "description":"null", "networkType":1, "areaId":"23.24.24.5", "interfaceCost":null, "bfdEnable":false, "deadTimer":null, "drPriority":1, "helloTimer":null, "ospfInstanceName":null}}] |
|
日志说明 |
用户进行了更新OSPFv3接口策略的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · Invalid JSON format：无效的JSON格式 · Invalid parameter：无效的参数 · Invalid network type：无效的接口网络类型 · Invalid interface cost：无效的接口开销 · Invalid description：无效的描述 · Invalid hello interval：无效的HELLO报文间隔 · Invalid dead interval：无效的邻居失效时间 · Invalid router priority：无效的路由器优先级 · The specified OSPF area does not exist：指定的OSPF区域不存在 · Invalid area ID：无效的区域ID · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
DELETE_OSPFV3_INTERFACE_POLICY_OP |
|
日志内容 |
Deleted OSPFv3 interface policy: $1 |
|
参数解释 |
$1：OSPFv3接口策略配置信息 |
|
举例 |
Deleted OSPFv3 interface policy: { "OspfInterfacePolicyConfig": { "id":a20ea450-2628-42b8-9d8e-ade68c2eab14, "ospfPolicyId":5a53d2e1-e939-40e1-b7ce-2eb0ef761010, "name":"interface_policy", "vsiName":"null", "description":"interface policy", "networkType":1, "interfaceCost":22, "bfdEnable":false, "deadTimer":22, "drPriority":1, "helloTimer":22, "ospfInstanceName":null, "authentications": [ { "OspfInterfaceAuthentication": { "id":7b3173a9-3191-4aae-ae97-42dd45921a6c, "authenticationMode":1, "keyId":22, "cipher":2, "password":"********" } } ] } } |
|
日志说明 |
用户进行了删除OSPFv3接口策略的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · The specified interface policy does not exist：指定的接口策略不存在 · Cannot delete the interface policy because it has been bound：OSPF接口策略被绑定，不允许删除 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_OSPF_POLICY_APPLY_OP |
|
日志内容 |
Created OSPF policy application: $1 |
|
参数解释 |
$1：OSPF策略应用配置信息 |
|
举例 |
Created OSPF policy application:[{"OspfPolicyApplyConfig":{ "id":6211c04b-5717-4b19-9f20-52dab4fdb8f7, "object":1, "sourceName":"zsx_ext", "ospfPolicyId":10d1ae6b-73ab-4700-b84a-65a1617c29ca, "tenantId":null, "policyName":"zsx_ospfv2", "networkId":1dba9379-4d7d-46c9-b355-a7459627b4f3, "vni":1300, "ospfAreaId":"1.1.1.3", "description":"null", "ospfInterfacePolicyId":dd8bce61-7830-40dd-b079-9f1c120f0d92, "interfaceName":"interface1", "deviceInterface":"null", "instanceId":null, "ospfProcessConfigs":[], "routerId":null, "ipVersion":4, "vpnInstance":, "ospfApplyInterfaceConfigs":[] }}] |
|
日志说明 |
用户进行了添加OSPF策略应用的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · Invalid JSON format：无效的JSON格式 · Invalid parameter：无效的参数 · Invalid tenant ID：无效的租户ID · Please specify an OSPF policy UUID：OSPF策略UUID不能为空 · The ospf policy apply already exists：OSPF策略应用已存在 · Invalid OSPF policy UUID：无效的OSPF策略UUID · Invalid interface policy UUID：无效的接口策略UUID · Invalid OSPF process ID：无效的OSPF进程号 · The process ID already exists：OSPF进程号已存在 · You cannot bind an OSPF policy to a vNetwork generated upon PBR service chain creation：来源为PBR的虚拟链路层网络不允许绑定OSPF策略 · You have no privilege to perform this operation：用户无权限执行此操作 · IP version mismatch：IP版本不一致 · Invalid router ID：无效的路由器ID · The specified device has been bound to the OSPF policy：指定设备已绑定过该OSPF策略，不支持重复绑定 · The VPN instance does not exist：指定的VPN实例不存在 · Some of the specified interfaces have already been bound to an interface policy：列表中存在已绑定接口策略的接口 · An interface can be specified only once：存在重复的设备接口 · The device information cannot be empty：指定设备信息不能为空 · You cannot specify duplicate devices：指定设备不能重复 · If you enable selective OSPF deployment, the area ID must be null：指定设备后OSPF策略应用区域ID必须为null · If you enable selective OSPF deployment, the area type must be null：指定设备后OSPF策略应用区域类型必须为null · If you enable selective OSPF deployment, the interface policy ID must be null：指定设备后OSPF策略应用接口策略ID必须为null · The selective OSPF deployment control state cannot be changed：指定设备下发OSPF配置开关不允许修改 · The object type does not support selective OSPF deployment：指定的应用对象类型不支持开启指定设备下发OSPF配置开关 · The device ID doesn't exist：指定的设备不存在 · Invalid area ID：无效的区域ID · You cannot bind an OSPF or OSPFv3 policy to a directly connected external network：外部网络的工作模式为独享时，不支持绑定OSPF或OSPFv3策略 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · An external transit vRouter has been bound to the external network. You cannot add any OSPF or OSPFv3 policy application：外部网络已绑定EXTERNALTRANSIT类型的虚拟路由器，不支持创建OSPF/OSPFv3策略应用 · The OSPF policy application ID already exists：OSPF策略应用ID已存在 |
|
日志内容 |
Updated OSPF policy application: $1 |
|
参数解释 |
$1：OSPF策略应用配置信息 |
|
举例 |
Updated OSPF policy application:{"OspfPolicyApplyConfig":{ "id":6211c04b-5717-4b19-9f20-52dab4fdb8f7, "object":1, "sourceName":"zsx_ext", "ospfPolicyId":10d1ae6b-73ab-4700-b84a-65a1617c29ca, "tenantId":null, "policyName":"zsx_ospfv2", "networkId":1dba9379-4d7d-46c9-b355-a7459627b4f3, "vni":1300, "ospfAreaId":"1.1.1.2", "description":"null", "ospfInterfacePolicyId":dd8bce61-7830-40dd-b079-9f1c120f0d92, "interfaceName":"interface1", "deviceInterface":"null", "instanceId":null, "ospfProcessConfigs":[], "routerId":null, "ipVersion":4, "vpnInstance":, "ospfApplyInterfaceConfigs":null }} |
|
日志说明 |
用户进行了更新OSPF策略应用的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · Invalid JSON format：无效的JSON格式 · Invalid parameter：无效的参数 · The ospf policy apply already exists：OSPF策略应用已存在 · Invalid OSPF policy UUID：无效的OSPF策略UUID · Invalid interface policy UUID：无效的接口策略UUID · The specified OSPF or OSPFv3 policy application does not exist：指定的OSPF或OSPFv3策略应用不存在 · You have no privilege to perform this operation：用户无权限执行此操作 · IP version mismatch：IP版本不一致 · Invalid router ID：无效的路由器ID · The OSPF policy is not editable：OSPF策略不允许修改 · The VPN instance is not editable：VPN实例不允许修改 · Some of the specified interfaces have already been bound to an interface policy：列表中存在已绑定接口策略的接口 · An interface can be specified only once：存在重复的设备接口 · The device information cannot be empty：指定设备信息不能为空 · You cannot specify duplicate devices：指定设备不能重复 · If you enable selective OSPF deployment, the area ID must be null：指定设备后OSPF策略应用区域ID必须为null · If you enable selective OSPF deployment, the area type must be null：指定设备后OSPF策略应用区域类型必须为null · If you enable selective OSPF deployment, the interface policy ID must be null：指定设备后OSPF策略应用接口策略ID必须为null · The selective OSPF deployment control state cannot be changed：指定设备下发OSPF配置开关不允许修改 · The object type does not support selective OSPF deployment：指定的应用对象类型不支持开启指定设备下发OSPF配置开关 · The device ID doesn't exist：指定的设备不存在 · Invalid area ID：无效的区域ID · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
DELETE_OSPF_POLICY_APPLY_OP |
|
日志内容 |
Deleted OSPF policy application: $1 |
|
参数解释 |
$1：OSPF策略应用配置信息 |
|
举例 |
Deleted OSPF policy application:{"OspfPolicyApplyConfig":{ "id":6211c04b-5717-4b19-9f20-52dab4fdb8f7, "object":1, "sourceName":"zsx_ext", "ospfPolicyId":10d1ae6b-73ab-4700-b84a-65a1617c29ca, "tenantId":null, "policyName":"zsx_ospfv2", "networkId":1dba9379-4d7d-46c9-b355-a7459627b4f3, "vni":1300, "ospfAreaId":"1.1.1.2", "description":"null", "ospfInterfacePolicyId":dd8bce61-7830-40dd-b079-9f1c120f0d92, "interfaceName":"interface1", "deviceInterface":"null", "instanceId":null, "ospfProcessConfigs":[], "routerId":null, "ipVersion":4, "vpnInstance":, "ospfApplyInterfaceConfigs":null }} |
|
日志说明 |
用户进行了删除OSPF策略应用的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · You have no privilege to perform this operation：用户无权限执行此操作 · The specified OSPF or OSPFv3 policy application does not exist：指定的OSPF或OSPFv3策略应用不存在 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
CREATE_OSPFV3_POLICY_APPLY_OP |
|
日志内容 |
Created OSPFv3 policy application: $1 |
|
参数解释 |
$1：OSPFv3策略应用配置信息 |
|
举例 |
Created OSPFv3 policy application:[{"OspfPolicyApplyConfig":{ "id":9725798d-c6e7-4133-8967-3484af75910f, "object":1, "sourceName":"zsx_ext", "ospfPolicyId":9531be0d-85c0-4661-8646-4410742be18b, "tenantId":null, "policyName":"zsx_ospfv3", "networkId":1dba9379-4d7d-46c9-b355-a7459627b4f3, "vni":1300, "ospfAreaId":"1.1.1.2", "description":"null", "ospfInterfacePolicyId":f4d7bcd1-fcdc-4ed4-be81-23cd1a0d0aaa, "interfaceName":"interface1", "deviceInterface":"null", "instanceId":null, "ospfProcessConfigs":[], "routerId":15.12.12.12, "ipVersion":6, "vpnInstance":, "ospfApplyInterfaceConfigs":[] }}] |
|
日志说明 |
用户进行了添加OSPFv3策略应用的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · Invalid JSON format：无效的JSON格式 · Invalid parameter：无效的参数 · Invalid tenant ID：无效的租户ID · Please specify an OSPF policy UUID：OSPF策略UUID不能为空 · The ospfv3 policy apply already exists：OSPFv3策略应用已存在 · Invalid OSPF policy UUID：无效的OSPF策略UUID · Invalid interface policy UUID：无效的接口策略UUID · Invalid OSPF process ID：无效的OSPF进程号 · The process ID already exists：OSPF进程号已存在 · You cannot bind an OSPF policy to a vNetwork generated upon PBR service chain creation：来源为PBR的虚拟链路层网络不允许绑定OSPF策略 · You have no privilege to perform this operation：用户无权限执行此操作 · IP version mismatch：IP版本不一致 · Invalid router ID：无效的路由器ID · The specified device has been bound to the OSPFv3 policy：指定设备已绑定过该OSPFv3策略，不支持重复绑定 · The VPN instance does not exist：指定的VPN实例不存在 · Some of the specified interfaces have already been bound to an interface policy：列表中存在已绑定接口策略的接口 · An interface can be specified only once：存在重复的设备接口 · The device information cannot be empty：指定设备信息不能为空 · You cannot specify duplicate devices：指定设备不能重复 · If you enable selective OSPF deployment, the area ID must be null：指定设备后OSPF策略应用区域ID必须为null · If you enable selective OSPF deployment, the area type must be null：指定设备后OSPF策略应用区域类型必须为null · If you enable selective OSPF deployment, the interface policy ID must be null：指定设备后OSPF策略应用接口策略ID必须为null · The selective OSPF deployment control state cannot be changed：指定设备下发OSPF配置开关不允许修改 · The object type does not support selective OSPF deployment：指定的应用对象类型不支持开启指定设备下发OSPF配置开关 · The device ID doesn't exist：指定的设备不存在 · Invalid area ID：无效的区域ID · You cannot bind an OSPF or OSPFv3 policy to a directly connected external network：外部网络的工作模式为独享时，不支持绑定OSPF或OSPFv3策略 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · An external transit vRouter has been bound to the external network. You cannot add any OSPF or OSPFv3 policy application：外部网络已绑定EXTERNALTRANSIT类型的虚拟路由器，不支持创建OSPF/OSPFv3策略应用 |
|
关键字 |
UPDATE_OSPFV3_POLICY_APPLY_OP |
|
日志内容 |
Updated OSPFv3 policy application: $1 |
|
参数解释 |
$1：OSPFv3策略应用配置信息 |
|
举例 |
Updated OSPFv3 policy application:{"OspfPolicyApplyConfig":{ "id":9725798d-c6e7-4133-8967-3484af75910f, "object":1, "sourceName":"zsx_ext", "ospfPolicyId":9531be0d-85c0-4661-8646-4410742be18b, "tenantId":null, "policyName":"zsx_ospfv3", "networkId":1dba9379-4d7d-46c9-b355-a7459627b4f3, "vni":1300, "ospfAreaId":"1.1.1.3", "description":"null", "ospfInterfacePolicyId":c2127a1f-9ca5-45cc-83f0-17da26b12712, "interfaceName":"interface2", "deviceInterface":"null", "instanceId":null, "ospfProcessConfigs":[], "routerId":15.12.12.12, "ipVersion":6, "vpnInstance":, "ospfApplyInterfaceConfigs":null }} |
|
日志说明 |
用户进行了更新OSPFv3策略应用的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · Invalid JSON format：无效的JSON格式 · Invalid parameter：无效的参数 · The ospfv3 policy apply already exists：OSPFv3策略应用已存在 · Invalid OSPF policy UUID：无效的OSPF策略UUID · Invalid interface policy UUID：无效的接口策略UUID · The specified OSPF or OSPFv3 policy application does not exist：指定的OSPF或OSPFv3策略应用不存在 · You have no privilege to perform this operation：用户无权限执行此操作 · IP version mismatch：IP版本不一致 · Invalid router ID：无效的路由器ID · The OSPFv3 policy is not editable：OSPFv3策略不允许修改 · The VPN instance is not editable：VPN实例不允许修改 · Some of the specified interfaces have already been bound to an interface policy：列表中存在已绑定接口策略的接口 · An interface can be specified only once：存在重复的设备接口 · The device information cannot be empty：指定设备信息不能为空 · You cannot specify duplicate devices：指定设备不能重复 · If you enable selective OSPF deployment, the area ID must be null：指定设备后OSPF策略应用区域ID必须为null · If you enable selective OSPF deployment, the area type must be null：指定设备后OSPF策略应用区域类型必须为null · If you enable selective OSPF deployment, the interface policy ID must be null：指定设备后OSPF策略应用接口策略ID必须为null · The selective OSPF deployment control state cannot be changed：指定设备下发OSPF配置开关不允许修改 · The object type does not support selective OSPF deployment：指定的应用对象类型不支持开启指定设备下发OSPF配置开关 · The device ID doesn't exist：指定的设备不存在 · Invalid area ID：无效的区域ID · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
DELETE_OSPFV3_POLICY_APPLY_OP |
|
日志内容 |
Deleted OSPFv3 policy application: $1 |
|
参数解释 |
$1：OSPFv3策略应用配置信息 |
|
举例 |
Deleted OSPFv3 policy application:{"OspfPolicyApplyConfig":{ "id":9725798d-c6e7-4133-8967-3484af75910f, "object":1, "sourceName":"zsx_ext", "ospfPolicyId":9531be0d-85c0-4661-8646-4410742be18b, "tenantId":null, "policyName":"zsx_ospfv3", "networkId":1dba9379-4d7d-46c9-b355-a7459627b4f3, "vni":1300, "ospfAreaId":"1.1.1.3", "description":"null", "ospfInterfacePolicyId":c2127a1f-9ca5-45cc-83f0-17da26b12712, "interfaceName":"interface2", "deviceInterface":"null", "instanceId":null, "ospfProcessConfigs":[], "routerId":15.12.12.12, "ipVersion":6, "vpnInstance":, "ospfApplyInterfaceConfigs":null }} |
|
日志说明 |
用户进行了删除OSPFv3策略应用的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · The specified OSPF or OSPFv3 policy application does not exist：指定的OSPF或OSPFv3策略应用不存在 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
UPDATE_POLICY_APPLY_OP |
|
日志内容 |
Updated policy application: $1 |
|
参数解释 |
$1：策略应用配置信息 |
|
举例 |
Updated policy application:{ "OspfPolicyApplyConfig":{ "id":e68226e8-ee93-42f0-b3ae-b634a65911d0, "object":1, "sourceName":"zsx_ext", "ospfPolicyId":4afc27dd-d6b7-4b8d-98da-681a8733d4ca, "tenantId":null, "policyName":"all-null-ospfv333", "networkId":5ef0f18b-2fe2-46c0-8d97-59751ade49cb, "vni":1300, "ospfAreaId":"12.13.14.15", "description":"null", "ospfInterfacePolicyId":47eeb4c6-ca60-4355-90c0-0d187b2ef6d0, "interfaceName":"003", "deviceInterface":"null", "instanceId":1, "ospfProcessConfigs":[ { "OspfProcessConfig":{ "id":"031a2e80-e146-4bef-8a8e-877ab9ceacdc", "deviceId":"e46508d9-a119-4982-a1ec-7bfb1c50f360", "instanceId":2 } } } ], "routeId":29.3.3.32, "ipVersion":6 } } |
|
日志说明 |
用户进行了更新策略应用的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · Invalid JSON format：无效的JSON格式 · Invalid parameter：无效的参数 · The ospfv3 policy apply already exists：OSPFv3策略应用已存在 · Invalid OSPF policy UUID：无效的OSPF策略UUID · Invalid interface policy UUID：无效的接口策略UUID · The specified OSPF or OSPFv3 policy application does not exist：指定的OSPF或OSPFv3策略应用不存在 · You have no privilege to perform this operation：用户无权限执行此操作 · IP version mismatch：IP版本不一致 · Invalid router ID：无效的路由器ID · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
DELETE_POLICY_APPLY_OP |
|
日志内容 |
Deleted policy application: $1 |
|
参数解释 |
$1：策略应用UUID |
|
举例 |
Deleted policy application: 110dceec-f498-4316-ac5667228e6bfa9e |
|
日志说明 |
用户进行了删除策略应用的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · The specified OSPF or OSPFv3 policy application does not exist：指定的OSPF或OSPFv3策略应用不存在 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
CREATE_CONFIG_AUDIT_OP |
|
日志内容 |
Created configuration audit task: $1 |
|
参数解释 |
$1：配置审计信息 |
|
举例 |
Created configuration audit task: [ ID:[39811f54-30fc-4519-8eed-ffbc52afb96b] Name:[配置审计] Description:[description] Object type:[Fabric] Audit At:[ Time: [12]:[30]:[00] Date: Days:[*] Months:[*] Days of week:[?]] Objects to audit:[ { Fabric ID:[eca72cea-91ea-4177-95fd-923e0552ac69] Fabric name:[fabric1] } ] Enabled:[true]] |
|
日志说明 |
用户进行了添加配置审计的操作 |
|
· 失败原因 |
· 当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · Invalid JSON format：无效的JSON格式 · Invalid parameter：无效的参数 · Invalid audited object type：无效的审计对象 · Invalid audit task UUID：无效的审计任务UUID · Please specify fabric UUIDs or device UUIDs：未指定Fabric UUID或设备UUID · Some device UUIDs do not belong to the specified fabric：指定的设备UUID不属于Fabric · Check the device name and device UUID pairs for mismatches：设备名称不属于指定的设备 · Some of the specified devices do not exist：指定的设备不存在 · Cannot specify device UUIDs or names when the audited object type is fabric：当审计对象为Fabric时，不允许配置设备UUID或名称 · Some of the specified fabrics do not exist：指定的Fabric不存在 · Check the fabric name and fabric UUID pairs for mismatches：Fabric名称不属于指定的Fabric · The audit task UUID already exists：该配置审计任务ID已存在 · Invalid Cron expression parameters：无效的Cron表达式参数 · The audit task failed to start the scheduler：配置审计任务调度失败 · Please specify Cron expression parameters：Cron表达式参数不能为空 · Duplicated devices exist：审计对象列表中已存在该设备 · You have no privilege to perform this operation：用户无权限执行此操作 · You cannot create a default configuration audit task：用户不允许创建默认配置审计任务 · The maximum number of concurrent device audit tasks must be an integer in the range of 10 to 200：审计最大并发数的取值范围为10~200的整数 |
|
关键字 |
UPDATE_CONFIG_AUDIT_OP |
|
日志内容 |
Updated configuration audit task: $1 |
|
参数解释 |
$1：配置审计信息 |
|
举例 |
Updated configuration audit task: ID:[39811f54-30fc-4519-8eed-ffbc52afb96b] Name:[配置审计] Description:[description] Object type:[Fabric] Audit At:[ Time: [12]:[30]:[00] Date: Days:[?] Months:[*] Days of week:[2,3]] Objects to audit:[ { Fabric ID:[eca72cea-91ea-4177-95fd-923e0552ac69] Fabric name:[fabric1] } ] Enabled:[true] |
|
日志说明 |
用户进行了更新配置审计的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · Invalid JSON format：无效的JSON格式 · Invalid parameter：无效的参数 · Invalid audited object type：无效的审计对象 · Invalid audit task UUID：无效的审计任务UUID · Please specify fabric UUIDs or device UUIDs：未指定Fabric UUID或设备UUID · Some device UUIDs do not belong to the specified fabric：指定的设备UUID不属于Fabric · Check the device name and device UUID pairs for mismatches：设备名称不属于指定的设备 · Some of the specified devices do not exist：指定的设备不存在 · Cannot specify device UUIDs or names when the audited object type is fabric：当审计对象为Fabric时，不允许配置设备UUID或名称 · Some of the specified fabrics do not exist：指定的Fabric不存在 · Check the fabric name and fabric UUID pairs for mismatches：Fabric名称不属于指定的Fabric · The audit task UUID already exists：该配置审计任务ID已存在 · Invalid Cron expression parameters：无效的Cron表达式参数 · The audit task failed to start the scheduler：配置审计任务调度失败 · Please specify Cron expression parameters：Cron表达式参数不能为空 · The configuration audit task does not exist：该配置审计任务不存在 · Duplicated devices exist：审计对象列表中已存在该设备 · You have no privilege to perform this operation：用户无权限执行此操作 · The maximum number of concurrent device audit tasks must be an integer in the range of 10 to 200：审计最大并发数的取值范围为10~200的整数 · You cannot change the value for the default_trigger field：不允许修改default_trigger字段 |
|
关键字 |
DELETE_CONFIG_AUDIT_OP |
|
日志内容 |
Deleted configuration audit task: $1 |
|
参数解释 |
$1：配置审计的UUID |
|
举例 |
Deleted configuration audit task: 39811f54-30fc-4519-8eed-ffbc52afb96b |
|
日志说明 |
用户进行了删除配置审计的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · Invalid audit task UUID：无效的审计任务UUID · The configuration audit task does not exist：该配置审计任务不存在 · You have no privilege to perform this operation：用户无权限执行此操作 · You cannot delete the default configuration audit task：不允许删除默认配置审计任务 |
|
关键字 |
PERFORM_CONFIG_AUDIT_OP |
|
日志内容 |
Executed one-off configuration audit task: $1 |
|
参数解释 |
$1：配置审计信息 |
|
举例 |
Executed one-off configuration audit task: ID:[88b8634e-917e-41c1-9318-02035944408d] Object type:[Fabric] Objects to audit:[ { Fabric ID:[eca72cea-91ea-4177-95fd-923e0552ac69] Fabric name:[fabric1] } ] Enabled:[true] |
|
日志说明 |
用户进行了立即配置审计的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · Invalid JSON format：无效的JSON格式 · Invalid parameter：无效的参数 · Invalid audited object type：无效的审计对象 · Please specify fabric UUIDs or device UUIDs：未指定Fabric UUID或设备UUID · Some device UUIDs do not belong to the specified fabric：指定的设备UUID不属于Fabric · Check the device name and device UUID pairs for mismatches：设备名称不属于指定的设备 · Some of the specified devices do not exist：指定的设备不存在 · Cannot specify device UUIDs or names when the audited object type is fabric：当审计对象为Fabric时，不允许配置设备UUID或名称 · Some of the specified fabrics do not exist：指定的Fabric不存在 · Check the fabric name and fabric UUID pairs for mismatches：Fabric名称不属于指定的Fabric · The audit task UUID already exists：该配置审计任务ID已存在 · Invalid Cron expression parameters：无效的Cron表达式参数 · The audit task failed to start the scheduler：配置审计任务调度失败 · Please specify Cron expression parameters：Cron表达式参数不能为空 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
TRIGGER_CONFIG_AUDIT_OP |
|
日志内容 |
Manually triggered periodic configuration audit task once: $1 |
|
参数解释 |
$1：配置审计信息 |
|
举例 |
Manually triggered periodic configuration audit task once: 39811f54-30fc-4519-8eed-ffbc52afb96b |
|
日志说明 |
用户进行了触发一条配置审计的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · Invalid JSON format：无效的JSON格式 · Invalid parameter：无效的参数 · Invalid audit task UUID：无效的审计任务UUID · The configuration audit task does not exist：该配置审计任务不存在 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_THIRD_PARTY_SERVICE_DEVICE_OP |
|
日志内容 |
Created third-party service device $1 |
|
参数解释 |
$1：第三方服务设备信息 |
|
举例 |
Created third-party service device ID: 510bfaf1-92df-43f1-8743-45aeafaeee9d Name: 7 Access type: auto Ingress vxlan: 72 Ingress IP: 72.0.0.2 Egress vxlan: 73 Egress IP: 73.0.0.2 VIP: [ 72.0.0.72] SNAT IP: [ 73.0.0.73] IPSECs: [{ Local address: 1.1.1.1 Peer address: 2.2.2.2 Local cidrs: [ 10.0.0.0/16] Peer cidrs: [ 20.0.0.0/16] }] |
|
日志说明 |
用户进行了创建第三方服务设备的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · The service is disabled：服务未启动 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · Unknown internal server error：未知的内部服务器错误 · Invalid name：无效的名称 · Invalid description：无效的描述信息 · Invalid parameter：无效的配置参数 · The ID of the third party service device already exists：第三方服务设备ID重复 · The name of the third party service device already exists：第三方服务设备名称重复 · Failed to create third party service device because the ingress port is invalid：第三方服务设备入接口不正确 · Failed to create third party service device because the egress port is invalid：第三方服务设备出接口不正确 · Failed to create third party service device because either ingress or egress port is in use：第三方服务设备入接口或出接口使用中 · The ingress vPort IP address is required：入虚拟端口IP地址不能为空 · The egress vPort IP address is required：出虚拟端口IP地址不能为空 · The ingress vPort VXLAN ID is required：入虚拟端口VXLAN ID不能为空 · The egress vPort VXLAN ID is required：出虚拟端口VXLAN ID不能为空 · The ingress vPort ID is required：入虚拟端口vPort ID不能为空 · The egress vPort ID is required：出虚拟端口vPort ID不能为空 · The ingress port does not exist：入虚拟端口不存在 · The egress port does not exist：出虚拟端口不存在 · The VXLAN ID is invalid or out of range：入虚拟端口VXLAN ID或出虚拟端口VXLAN ID超出可用范围 · When the ingress virtual port has the same VXLAN ID and IP address settings as the egress virtual port, you can't set vip_list and snat_ip_list：当入虚拟端口VXLAN ID、IP地址与出虚拟端口的VXLAN ID、IP地址一致时，不允许配置VIP、SNAT IP参数 · Invalid IP address：无效的IP地址 · Make sure the egress and ingress vPort IP addresses use the same IP version：出入虚拟端口地址IP版本不一致 · Make sure the VIPs and the egress and ingress vPort IP addresses use the same IP version：VIP与出入虚拟端口地址IP版本不一致 · Make sure the SNAT IP addresses and the egress and ingress vPort IP addresses use the same IP version：SNAT IP与出入虚拟端口地址IP版本不一致 · Make sure the VXLAN IDs for the ingress and egress vPorts are different when the third-party service device is deployed in two-arm mode：双臂部署模式下出入虚拟端口VXLAN ID不能相同 · Make sure the IP addresses for the ingress and egress vPorts are different when the third-party service device is deployed in two-arm mode：双臂部署模式下出入虚拟端口IP地址不能相同 · You have no privilege to perform this operation：用户无权限执行此操作 · Invalid local IP address：无效的本端地址 · Invalid peer IP address无效的对端地址 · The DNAT IP address cannot be edited：DNAT IP地址不支持修改 · Make sure the DNAT IP addresses and the egress and ingress vPort IP addresses use the same IP version：DNAT IP与出入虚拟端口地址IP版本不一致 · Duplicate DNAT IP addresses exist：DNAT IP地址重复 · You cannot configure both VIP and DNAT IP addresses：VIP和DNAT IP不能同时配置 · Make sure the same IP version is used for the local IP address, peer IP address, local subnets, and peer subnets in one IPsec profile：同一个IPsec的本端地址、对端地址、本端子网、远端子网的IP版本必须一致 · Make sure the IPsec settings and the egress and ingress vPort IP addresses use the same IP version ：IPsec与出入虚拟端口地址IP版本必须一致 · The address pair specified in each IPsec profile is bidirectional. If two addresses have been specified in one profile, you cannot use both of them in any other profiles：一条IPsec信息的本端地址、对端地址与其他IPsec信息的本端地址、对端地址不能完全一致或互换 · The subnet pair specified in each IPsec profile is bidirectional. If two subnets have been specified in one profile, you cannot use both of them in any other profiles：一条IPsec信息的本端子网、远端子网与其他IPsec信息的本端子网、远端子网不能完全一致或互换 |
|
关键字 |
UPDATE_THIRD_PARTY_SERVICE_DEVICE_OP |
|
日志内容 |
Updated third-party service device $1 |
|
参数解释 |
$1：第三方服务设备信息 |
|
举例 |
Updated third-party service device ID: 510bfaf1-92df-43f1-8743-45aeafaeee9d Name: 7 Access type: auto Ingress vxlan: 72 Ingress IP: 72.0.0.2 Egress vxlan: 73 Egress IP: 73.0.0.2 VIP: [ 72.0.0.72] SNAT IP: [ 73.0.0.73] IPSECs: [{ Local address: 1.1.1.1 Peer address: 2.2.2.2 Local cidrs: [ 10.0.0.0/16] Peer cidrs: [ 20.0.0.0/16] }] |
|
日志说明 |
用户进行了更新第三方服务设备的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · The service is disabled：服务未启动 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · Unknown internal server error：未知的内部服务器错误 · Invalid name：无效的名称 · Invalid description：无效的描述信息 · Invalid parameter：无效的配置参数 · The third party service device tenant id is read only：租户为只读字段 · The access mode field is read only：接入方式为只读字段 · The third party service device ingress ip is read only：入虚拟端口IP地址为只读字段 · The third party service device ingress port is read only：入虚拟端口为只读字段 · The third party service device ingress vxlan is read only：入虚拟端口VXLAN ID为只读字段 · The third party service device egress ip is read only：出虚拟端口IP地址为只读字段 · The third party service device egress port is read only：出虚拟端口为只读字段 · The third party service device egress vxlan is read only：出虚拟端口VXLAN ID为只读字段 · The third party service device inuse is read only：第三方服务设备inuse为只读属性 · The VIP list cannot be modified：VIP列表不允许修改 · The SNAT IP list cannot be modified：SNAT IP地址列表不允许修改 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_THIRD_PARTY_SERVICE_DEVICE_OP |
|
日志内容 |
Deleted third-party service device $1 |
|
参数解释 |
$1：第三方服务设备名称 |
|
举例 |
Deleted third-party service device third1 |
|
日志说明 |
用户进行了删除第三方服务设备的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · The service is disabled：服务未启动 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Failed to delete the third party service device because it is used by a third party service function：该第三方服务设备已被第三方服务资源使用 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
START_RESOURCE_BIND_NQA_OP |
|
日志内容 |
Started resource bind nqa, resourceid : $1 |
|
参数解释 |
$1：服务资源的ID |
|
举例 |
Started resource bind nqa, resourceid : b1e045fd-9de1-4347-8dae-30bb14b68a78 |
|
日志说明 |
用户进行了服务资源绑定NQA的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The specified NQA profile does not exist：指定的NQA策略不存在 · Cannot bind the subnet to an NQA profile. The border gateway in the subnet has been bound to a track entry：绑定NQA失败，服务资源绑定的网关成员已配置了Track项 · You can bind a service resource to only one NQA profile：同一个服务资源仅允许绑定一个NQA策略 · The specified NQA profile has been bound to another service resource of the same type：指定的NQA策略已被其他同类型服务资源绑定 · The specified NQA profile has been bound to another external network：指定的NQA策略已经被其他外部网络绑定 · You cannot bind the service resource to an NQA profile when the auto NQA profile mode is used：当NQA策略配置为自动时，服务资源不能绑定NQA策略 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · Service resources created for service chain scenarios or service leaf scenarios cannot be bound to NQA profiles：服务链类型和Service Leaf服务网关类型的服务资源不支持绑定NQA策略 · You can bind vFW service resources from a resource pool to only one NQA profile of a specific binding type：同一个资源池分配的虚拟防火墙服务资源，相同类型的联动NQA，只能配置同一个NQA策略 · You can specify only one NQA profile of a specific binding type for the same service resource：同一服务资源绑定的每种NQA策略仅支持配置一个 · The NQA profile has been bound to a service path：该NQA策略已经被服务路径绑定 |
|
关键字 |
START_RESOURCE_UNBIND_NQA_OP |
|
日志内容 |
Started resource unbind nqa, resourceid : $1 |
|
参数解释 |
$1：服务资源的ID |
|
举例 |
Started resource unbind nqa, resourceid :b1e045fd-9de1-4347-8dae-30bb14b68a78 |
|
日志说明 |
用户进行了服务资源解绑NQA的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Please specify an NQA profile for the service resource：指定的服务资源必须绑定NQA策略 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
CREATE_PORTPVID_OP |
|
日志内容 |
Created interface and PVID mapping: $1 |
|
参数解释 |
$1：接口PVID信息 |
|
举例 |
Created interface and PVID mapping: [ ID: 20035139-964d-458a-9cd2-138cc15dd06f Device ID: 9790e274-423f-40ed-b502-210a35aab9bb Device name: 100.115 Port name: GigabitEthernet1/0/4 Port number: 0x5 Port PVID: 78 Data source:DEFAULT Port VLAN domain ID:null, ID: f3783346-0601-45af-bb1f-71d3b215d537 Device ID: 9790e274-423f-40ed-b502-210a35aab9bb Port name: GigabitEthernet1/0/12 Port number: 0xd Port PVID: 78 Data source:DEFAULT Port VLAN domain ID:null] |
|
日志说明 |
用户进行了添加接口PVID的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · Invalid JSON format：无效的JSON格式 · You have no privilege to perform this operation：用户无权限执行此操作 · Invalid parameter：无效的参数 · The device_ID cannot be null：设备ID不能为空 · Please specify interfaces：接口名称不能为空 · Some of the specified PVIDs are invalid or out of range：无效的PVID或者超出范围 · Please specify PVIDs：接口PVID不能为空 · The device type doesn't match：设备类型不匹配 · The device to which the interface belongs or the device to which a bound interface belongs is inactive：正在绑定的接口所属设备或已绑定的接口所属设备中存在未激活设备 · Non-Downlink interfaces exist：存在非下行口 · Duplicated interfaces exist：设备端口重复 · You cannot edit the interface and PVID mappings for bare metal servers：裸金属接口PVID不允许修改 · The device does not exist：指定的设备不存在 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · The interface of the service leaf device is bound to a resource access template. You cannot apply VLAN-related mappings to the interface：Service Leaf设备的接口被资源接入模板绑定时，不可用于其他映射 · The device interfaces do not exist. Please synchronize device interfaces to obtain the most recent interface information：设备接口不存在，请同步设备接口以获取最新接口 |
|
关键字 |
MODIFY_PORTPVID_OP |
|
日志内容 |
Edited interface and PVID mapping: $1 |
|
参数解释 |
$1：接口PVID信息 |
|
举例 |
Edited interface and PVID mapping: ID: a94ff6ba-be13-4d31-a19b-0f0c76a8856b Device ID: 89aa65a3-13f5-41be-aa26-823ef0ab976d Port name: Route-Aggregation200 Port number: 0x51d Port PVID: 2312 Data source:DEFAULT Port VLAN domain ID:null |
|
日志说明 |
用户进行了更新接口PVID的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · Invalid JSON format：无效的JSON格式 · Invalid parameter：无效的参数 · You have no privilege to perform this operation：用户无权限执行此操作 · The device_ID cannot be null：设备ID不能为空 · Please specify interfaces：接口名称不能为空 · Some of the specified PVIDs are invalid or out of range：无效的PVID或者超出范围 · Please specify PVIDs：接口PVID不能为空 · The device type doesn't match：设备类型不匹配 · The device to which the interface belongs or the device to which a bound interface belongs is inactive：正在绑定的接口所属设备或已绑定的接口所属设备中存在未激活设备 · Non-Downlink interfaces exist：存在非下行口 · Duplicated interfaces exist：设备端口重复 · The specified interface and PVID mapping does not exist：接口PVID不存在 · You cannot edit the interface and PVID mappings for bare metal servers：裸金属接口PVID不允许修改 · The device does not exist：指定的设备不存在 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · The interface of the service leaf device is bound to a resource access template. You cannot apply VLAN-related mappings to the interface：Service Leaf设备的接口被资源接入模板绑定时，不可用于其他映射 · The device interfaces do not exist. Please synchronize device interfaces to obtain the most recent interface information：设备接口不存在，请同步设备接口以获取最新接口 |
|
关键字 |
DELETE_PORTPVID_OP |
|
日志内容 |
Deleted interface and PVID mapping: $1 |
|
参数解释 |
$1：接口PVID的信息 |
|
举例 |
Deleted interface and PVID mapping: Deleted [3] interface and PVID mappings from device [leaf1]. |
|
日志说明 |
用户进行了删除接口PVID的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · Invalid JSON format：无效的JSON格式 · Invalid parameter：无效的参数 · You have no privilege to perform this operation：用户无权限执行此操作 · Please specify PVIDs：接口PVID不能为空 · The device_ID cannot be null：设备ID不能为空 · Please specify interfaces：接口名称不能为空 · You cannot delete the interface and PVID mappings for bare metal servers on the current page：裸金属配置的接口PVID不允许删除 · You cannot delete the interface and PVID mappings for service chains on the current page：服务链配置的接口PVID不允许删除 · When bulk deleting interface and PVID mappings, you cannot both delete all mappings of a device and delete the specific mappings of the device：批量删除时，一个设备不允许同时删除设备和接口 · The specified interface and PVID mapping does not exist：接口PVID配置不存在 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
DELETE_PORTPVID_OP |
|
日志内容 |
Deleted interface and PVID mapping: $1 |
|
参数解释 |
$1：配置接口PVID的UUID |
|
举例 |
Deleted interface and PVID mapping: ID : [a02c1e04-2e9c-4488-9da9-752e9578d0cc] |
|
日志说明 |
用户进行了删除接口PVID的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · Invalid parameter：无效的参数 · You have no privilege to perform this operation：用户无权限执行此操作 · Please specify PVIDs：接口PVID不能为空 · The device_ID cannot be null：设备ID不能为空 · Please specify interfaces：接口名称不能为空 · You cannot delete the interface and PVID mappings for bare metal servers on the current page：裸金属配置的接口PVID不允许删除 · You cannot delete the interface and PVID mappings for service chains on the current page：服务链配置的接口PVID不允许删除 · The specified interface and PVID mapping does not exist：接口PVID配置不存在 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
CLEAR_AUTO_DISCOVERED_DEVICE_OP |
|
日志内容 |
User $1 cleared the auto-discovered device list. |
|
参数解释 |
$1：自动发现任务的用户名称 |
|
举例 |
User admin cleared the auto-discovered device list. |
|
日志说明 |
用户进行了清除自动发现设备列表的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · The auto-detection task is not completed and cannot be deleted：自动发现任务未完成，无法删除 · The auto-detection task doesn't exist：指定用户名的自动发现任务不存在 · Invalid username：无效的用户名 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
REFRESH_DEV_LOCK_SUCC_OP |
|
日志内容 |
Refreshed lock configuration for $1 devices successfully, UUIDs of devices: $2 |
|
参数解释 |
$1：批量操作成功的设备个数 $2：批量操作成功的设备UUID列表 |
|
举例 |
Refreshed lock configuration for 2 devices, UUIDs of devices: [be111c50-493c-42de-bf9a-20e7cb7cdadb, f7554d87-1a30-4e47-83ec-f1d3a290bc33] |
|
日志说明 |
用户成功执行刷新锁状态操作 |
|
失败原因 |
无 |
|
关键字 |
REFRESH_DEV_LOCK_FAIL_PARAMETER_OP |
|
日志内容 |
Failed to refresh lock configuration for $1 devices: $2 |
|
参数解释 |
$1：批量操作失败的设备个数 $2：批量执行刷新操作的设备UUID列表 |
|
举例 |
Failed to refresh lock configuration for 2 devices: [be111c50-493c-42de-bf9a-20e7cb7cdadb, f7554d87-1a30-4e47-83ec-f1d3a290bc33] |
|
日志说明 |
用户执行刷新锁状态操作参数校验失败 |
|
失败原因 |
当操作失败时，可能的原因如下： · The device is inactive：设备未激活 · Invalid parameter：参数无效 · The device_ID cannot be null：设备ID不能为空 · The physical access device does not exist：设备不存在 · Invalid JSON format：无效的JSON格式 · The device does not support lock management：指定类型的设备不支持配置锁管理 · The network element is being deleted or being removed from the device group or being removed from the fabric：设备正在删除中 · The controller does not contain lock data about the device：指定设备的锁管理信息不存在 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
REFRESH_DEV_LOCK_FAIL_BUSINESS_OP |
|
日志内容 |
Failed to refresh lock configuration for device: $1 |
|
参数解释 |
$1：单个执行刷新操作的设备UUID |
|
举例 |
Failed to refresh lock configuration for device: 965e8b6a-c651-4d71-9cda-7cdedc30f41d |
|
日志说明 |
用户执行刷新锁状态操作因模块间业务影响导致失败 |
|
失败原因 |
当操作失败时，可能的原因如下： · The device_ID cannot be null：设备ID不能为空 · The physical access device does not exist：设备不存在 · The controller does not contain lock data about the device：指定设备的锁管理信息不存在 |
|
关键字 |
LOCK_DEV_LOCK_SUCC_OP |
|
日志内容 |
Locked $1 devices in bulk successfully, UUIDs of devices: $2 |
|
参数解释 |
$1：批量加锁操作成功的设备个数 $2：批量操作成功的设备UUID列表 |
|
举例 |
Locked 2 devices in bulk successfully, UUIDs of devices: [be111c50-493c-42de-bf9a-20e7cb7cdadb, f7554d87-1a30-4e47-83ec-f1d3a290bc33] |
|
日志说明 |
用户成功执行批量加锁操作 |
|
失败原因 |
无 |
|
关键字 |
LOCK_DEV_LOCK_FAIL_PARAMETER_OP |
|
日志内容 |
Failed to lock $1 devices: $2 |
|
参数解释 |
$1：批量执行加锁操作的设备UUID列表 |
|
举例 |
Failed to lock 2 devices: [be111c50-493c-42de-bf9a-20e7cb7cdadb, f7554d87-1a30-4e47-83ec-f1d3a290bc33] |
|
日志说明 |
用户执行批量加锁操作参数校验失败 |
|
失败原因 |
当操作失败时，可能的原因如下： · The device is inactive：设备未激活 · Invalid parameter：参数无效 · The device_ID cannot be null：设备ID不能为空 · The physical access device does not exist：设备不存在 · Invalid JSON format：无效的JSON格式 · The device does not support lock management：指定类型的设备不支持配置锁管理 · The network element is being deleted or being removed from the device group or being removed from the fabric：设备正在删除中 · The controller does not contain lock data about the device：指定设备的锁管理信息不存在 · Please do not select locked devices：已加锁的设备不支持再进行加锁操作 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
LOCK_DEV_LOCK_FAIL_BUSINESS_OP |
|
日志内容 |
Failed to lock device: $1 |
|
参数解释 |
$1：单个执行加锁操作的设备UUID |
|
举例 |
Failed to lock device: 965e8b6a-c651-4d71-9cda-7cdedc30f41d |
|
日志说明 |
用户执行加锁操作因模块间业务影响导致失败 |
|
失败原因 |
当操作失败时，可能的原因如下： · The device_ID cannot be null：设备ID不能为空 · The physical access device does not exist：设备不存在 · The controller does not contain lock data about the device：指定设备的锁管理信息不存在 |
|
关键字 |
UNLOCK_DEV_LOCK_SUCC_OP |
|
日志内容 |
Unlocked $1 devices in bulk successfully, UUIDs of devices: $2 |
|
参数解释 |
$1：批量操作成功的设备个数 $2：批量操作成功的设备UUID列表 |
|
举例 |
Unlocked 2 devices in bulk successfully, UUIDs of devices: [be111c50-493c-42de-bf9a-20e7cb7cdadb, f7554d87-1a30-4e47-83ec-f1d3a290bc33] |
|
日志说明 |
用户成功执行批量解锁操作 |
|
失败原因 |
无 |
|
关键字 |
UNLOCK_DEV_LOCK_FAIL_PARAMETER_OP |
|
日志内容 |
Failed to unlock $1 devices : $2 |
|
参数解释 |
$1：批量执行操作的设备UUID列表 |
|
举例 |
Failed to unlock 2 devices: [be111c50-493c-42de-bf9a-20e7cb7cdadb, f7554d87-1a30-4e47-83ec-f1d3a290bc33] |
|
日志说明 |
用户执行批量解锁操作参数校验失败 |
|
失败原因 |
当操作失败时，可能的原因如下： · The device is inactive：设备未激活 · Invalid parameter：参数无效 · The device_ID cannot be null：设备ID不能为空 · The physical access device does not exist：设备不存在 · Invalid JSON format：无效的JSON格式 · The device does not support lock management：指定类型的设备不支持配置锁管理 · The network element is being deleted or being removed from the device group or being removed from the fabric：设备正在删除中 · The controller does not contain lock data about the device：指定设备的锁管理信息不存在 · Please do not select unlocked devices：已解锁的设备不支持再进行解锁操作 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UNLOCK_DEV_LOCK_FAIL_BUSINESS_OP |
|
日志内容 |
Failed to unlock device: $1 |
|
参数解释 |
$1：单个执行解锁操作的设备UUID |
|
举例 |
Failed to unlock device: 965e8b6a-c651-4d71-9cda-7cdedc30f41d |
|
日志说明 |
用户执行解锁操作因模块间业务影响导致失败 |
|
失败原因 |
当操作失败时，可能的原因如下： · The device_ID cannot be null：设备ID不能为空 · The physical access device does not exist：设备不存在 · The controller does not contain lock data about the device：指定设备的锁管理信息不存在 |
|
关键字 |
CREATE_MLAG_GROUP_PLAN_OP |
|
日志内容 |
Created M-LAG group plan: $1 |
|
参数解释 |
$1：M-LAG组规划 |
|
举例 |
Created M-LAG group plan: ID: [adc7bbf7-2187-4c5b-9164-8df5c3689afb] SN of Device A: [88] Ports of Device A: [Ten-GigabitEthernet1/0/2] SN of Device B: [888] Ports of Device B: [Ten-GigabitEthernet1/0/2] Access Service: [false] LAG Int ID on Device A: [66] LAG Int ID on Device B: [66] M-LAG Group ID: [66] LAG Int desc on Device A: [edd] LAG Int desc on Device B: [eee] |
|
日志说明 |
用户进行了增加M-LAG组规划的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · Invalid JSON format：无效的JSON格式 · You have no privilege to perform this operation：用户无权限执行此操作 · Invalid parameter：无效的参数 · The serial number cannot be empty：设备序列号不能为空 · Invalid serial number：无效的设备序列号 · Please specify different serial numbers for Device A and Device B：A设备序列号和B设备序列号不允许相同 · Invalid port name：无效的端口名 · You must configure the port names：端口名不能为空 · Duplicated Device port：该设备端口重复 · The port has been specified for M-LAG group plan use：指定设备的端口名已经被使用 · Invalid ID：无效的ID · The serial number has been configured on another M-LAG group plan：设备序列号已被其他M-LAG组规划使用 · On the device with the specified SN, the downlink interface conflicts with the device port in the M-LAG group plan：指定序列号的设备信息下行口与M-LAG组规划的设备端口冲突 · The description of an LAG interface cannot exceed 251 bytes. The description is a case-sensitive string. You cannot enter question marks (?)：聚合接口描述信息最长251个字节，区分大小写，不支持“?” |
|
关键字 |
UPDATE_MLAG_GROUP_PLAN_OP |
|
日志内容 |
Updated M-LAG group plan: $1 |
|
参数解释 |
$1：M-LAG组规划 |
|
举例 |
Updated M-LAG group plan: ID: [adc7bbf7-2187-4c5b-9164-8df5c3689afb] SN of Device A: [88] Ports of Device A: [Ten-GigabitEthernet1/0/2] SN of Device B: [888] Ports of Device B: [Ten-GigabitEthernet1/0/2] Access Service: [false] LAG Int ID on Device A: [66] LAG Int ID on Device B: [66] M-LAG Group ID: [67] LAG Int desc on Device A: [edd] LAG Int desc on Device B: [eee] |
|
日志说明 |
用户进行了更新M-LAG组规划的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · Invalid JSON format：无效的JSON格式 · Invalid parameter：无效的参数 · You have no privilege to perform this operation：用户无权限执行此操作 · The serial number cannot be empty：设备序列号不能为空 · Invalid serial number：无效的设备序列号 · Please specify different serial numbers for Device A and Device B：A设备序列号和B设备序列号不允许相同 · Invalid port name：无效的端口名 · You must configure the port names：端口名不能为空 · Duplicated Device port：该设备端口重复 · The port has been specified for M-LAG group plan use：指定设备的端口名已经被使用 · Invalid ID：无效的ID · The serial number has been configured on another M-LAG group plan：设备序列号已被其他M-LAG组规划使用 · On the device with the specified SN, the downlink interface conflicts with the device port in the M-LAG group plan：指定序列号的设备信息下行口与M-LAG组规划的设备端口冲突 · The description of an LAG interface cannot exceed 251 bytes. The description is a case-sensitive string. You cannot enter question marks (?)：聚合接口描述信息最长251个字节，区分大小写，不支持“?” |
|
关键字 |
DELETE_MLAG_GROUP_PLAN_OP |
|
日志内容 |
Deleted M-LAG group plan: $1 |
|
参数解释 |
$1：M-LAG组规划 |
|
举例 |
Deleted M-LAG group plan: ID: [adc7bbf7-2187-4c5b-9164-8df5c3689afb] SN of Device A: [88] Ports of Device A: [Ten-GigabitEthernet1/0/2] SN of Device B: [888] Ports of Device B: [Ten-GigabitEthernet1/0/2] |
|
日志说明 |
用户进行了删除M-LAG组规划的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · Invalid JSON format：无效的JSON格式 · Invalid parameter：无效的参数 · You have no privilege to perform this operation：用户无权限执行此操作 · The specified resource is not found：指定的M-LAG组规划不存在 |
|
关键字 |
BATCH_DELETE_MLAG_GROUP_PLAN_OP |
|
日志内容 |
Bulk deleted M-LAG group plans: $1 |
|
参数解释 |
$1：M-LAG组规划的列表 |
|
举例 |
Bulk deleted M-LAG group plans: [ ID: [4f852174-73d8-498d-bb9c-37f2ed4c56d7] SN of Device A: [77] Ports of Device A: [Ten-GigabitEthernet1/0/1] SN of Device B: [7778] Ports of Device B: [Ten-GigabitEthernet1/0/1] Access Service: [false] LAG Int ID on Device A: [66] LAG Int ID on Device B: [66] M-LAG Group ID: [66] LAG Int desc on Device A: [66] LAG Int desc on Device B: [66] ] |
|
日志说明 |
用户进行了批量删除M-LAG组规划的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · Invalid parameter：无效的参数 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
ACTION_CREATE_ROUTER_ESCAPE_OP |
|
日志内容 |
Created M-LAG routed peer link: $1 |
|
参数解释 |
$1：M-LAG互联链路的信息 |
|
举例 |
Created M-LAG routed peer link: [M-LAG routed peer-link：{ ID:” 555a3407-73d4-4614-8ce1-346525a14924”, Name:"test1", Description:"", Router ID:"12faf8ab-88d8-4ae8-bd52-426d47860607", VLAN ID:44, Device list:[ M-LAG routed peer-link device:{ Device ID:"662ee793-51f0-4ccc-a38c-fc184b62fca1", IPv4 address:"1.1.1.1/31", IPv6 address:"" }, M-LAG routed peer-link device: { Device ID:"3f7686cc-f1ea-4983-867e-052440aa83f4", IPv4 address:"1.1.1.2/31", IPv6 address:"" }] } ] |
|
日志说明 |
用户进行了创建M-LAG互联链路的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · Invalid JSON format：无效的JSON格式 · The service is disabled：服务未启动 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · Invalid name：无效的名称 · You have no privilege to perform this operation ：用户无权限执行此操作 · You must specify two devices in the device_list：device_list下仅支持指定2台设备 · The device_list contains invalid device IDs：device_list下存在无效的设备ID · The device_list must contain a minimum of one IP version：device_list下至少指定一个IP版本 · The IP addresses of the two devices in the device_list do not match：device_list下存在不匹配的IP地址 · The VLAN ID range is 1 to 4094：互联VLAN的取值为1～4094 · Invalid router_id value：router_id字段无效 · Invalid description ：无效的描述信息 · Invalid IP address：无效的IP地址 · Invalid IPv6 address ：无效的IPv6地址 · Invalid Mask：无效的掩码 · The device configuration on the controller is inconsistent with the actual device configuration：指定的设备和已存在的设备不匹配 · The device type is not supported：不支持的设备类型 · The vRouter doesn't exist：指定的虚拟路由器不存在 · The VLAN ID cannot be identical to a segment ID or in a VLAN ID pool for a tenant carrier network：互联VLAN ID不能和外部网络的Segment ID相同，且不允许在租户承载网类型的VLAN池中 · The device is not a border gateway. To specify a border device, make sure it is in a device group whose position is border gateway：指定设备为边界设备，该设备必须加入到出口网关设备组中 · You must configure the same mask for the local and peer devices：本端设备和对端设备的掩码必须一致 · The device does not exist：指定的设备不存在 · The resource already exists：该资源已存在 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · The M-LAG routed peer-link ID is invalid：无效的M-LAG互联链路ID · When you set up an M-LAG routed peer-link for a vRouter, make sure no M-LAG routed peer-link exists on the specified devices：相同虚拟路由器下，指定的设备只能被一条M-LAG互联链路使用 · The devices at the two ends of the M-LAG routed peer-link cannot have the same IP address：M-LAG互联链路连接的两个设备不允许有相同的IP地址 · The M-LAG routed peer-link does not exist：指定的M-LAG互联链路不存在 · The IP addresses used for setting up the M-LAG routed peer-link must belong to the same subnet：组成M-LAG互联链路的两个设备接口IP必须在相同网段 · If the device has multiple M-LAG routed peer-links, make sure the VLAN IDs configured for the peer-links are unique：当一台设备被多个M-LAG互联链路使用时，所有的互联VLAN不允许相同 · The devices at the two ends of the M-LAG routed peer-link must be different：M-LAG路由peer-link两端的设备不能为同一台设备 · In an M-LAG routed peer link, the interconnect address of the local or remote device cannot be any source address that the device uses for peer relationship establishment：M-LAG互联链路本端或对端互联地址不能与BGP对等体中相同设备的源IP地址相同 |
|
关键字 |
ACTION_UPDATE_ROUTER_ESCAPE_OP |
|
日志内容 |
Updated M-LAG routed peer link: $1 |
|
参数解释 |
$1：M-LAG互联链路的信息 |
|
举例 |
Updated M-LAG routed peer link: M-LAG routed peer-link：{ ID:” 555a3407-73d4-4614-8ce1-346525a14924” Name:"test1", Description:"", Device list:[ M-LAG routed peer-link device:{ Device ID:"662ee793-51f0-4ccc-a38c-fc184b62fca1", IPv4 address:"1.1.1.1/31", IPv6 address:"" }, M-LAG routed peer-link device: { Device ID:"3f7686cc-f1ea-4983-867e-052440aa83f4", IPv4 address:"1.1.1.2/31", IPv6 address:"" }] } |
|
日志说明 |
用户进行了修改M-LAG互联链路的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · Invalid JSON format：无效的JSON格式 · The service is disabled：服务未启动 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · You have no privilege to perform this operation：用户无权限执行此操作 · Invalid name：无效的名称 · Invalid description：无效的描述信息 · Invalid IP address：无效的IP地址 · Invalid IPv6 address：无效的IPv6地址 · Invalid Mask：无效的掩码 · You must specify two devices in the device_list：device_list下仅支持指定2台设备 · The device_list contains invalid device IDs：device_list下存在无效的设备ID · The device_list must contain a minimum of one IP version：device_list下至少指定一个IP版本 · The IP addresses of the two devices in the device_list do not match：device_list下存在不匹配的IP地址 · The VLAN ID range is 1 to 4094：互联VLAN的取值为1～4094 · Invalid router_id value：router_id字段无效 · The device_list must contain a minimum of one IP version：device_list下至少指定一个IP版本 · The IP addresses of the two devices in the device_list do not match：device_list下存在不匹配的IP地址 · The device configuration on the controller is inconsistent with the actual device configuration：指定的设备和已存在的设备不匹配 · The device type is not supported：不支持的设备类型 · he VLAN ID cannot be identical to a segment ID or in a VLAN ID pool for a tenant carrier network：互联VLAN ID不能和外部网络的Segment ID相同，且不允许在租户承载网类型的VLAN池中 · The device is not a border gateway. To specify a border device, make sure it is in a device group whose position is border gateway：指定设备为边界设备，该设备必须加入到出口网关设备组中 · You must configure the same mask for the local and peer devices：本端设备和对端设备的掩码必须一致 · The device does not exist：指定的设备不存在 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · The M-LAG routed peer-link ID is invalid：无效的M-LAG互联链路ID · When you set up an M-LAG routed peer-link for a vRouter, make sure no M-LAG routed peer-link exists on the specified devices：相同虚拟路由器下，指定的设备只能被一条M-LAG互联链路使用 · The devices at the two ends of the M-LAG routed peer-link cannot have the same IP address：M-LAG互联链路连接的两个设备不允许有相同的IP地址 · The M-LAG routed peer-link does not exist：指定的M-LAG互联链路不存在 · The IP addresses used for setting up the M-LAG routed peer-link must belong to the same subnet：组成M-LAG互联链路的两个设备接口IP必须在相同网段 · If the device has multiple M-LAG routed peer-links, make sure the VLAN IDs configured for the peer-links are unique：当一台设备被多个M-LAG互联链路使用时，所有的互联VLAN不允许相同In an M-LAG routed peer link, the interconnect address of the local or remote device cannot be any source address that the device uses for peer relationship establishment：M-LAG互联链路本端或对端互联地址不能与BGP对等体中相同设备的源IP地址相同 |
|
关键字 |
ACTION_DELETE_ROUTER_ESCAPE_OP |
|
日志内容 |
Deleted M-LAG routed peer link $1. |
|
参数解释 |
$1：M-LAG互联链路的ID |
|
举例 |
Deleted M-LAG routed peer link 747cf8c8-8ab4-4a02-9550-0878dcc4ca5a. |
|
日志说明 |
用户进行了删除M-LAG互联链路的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · Invalid JSON format：无效的JSON格式 · The service is disabled：服务未启动 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
ACTION_CREATE_BGP_NETWORK_OP |
|
日志内容 |
Create BGP Network: $1 |
|
参数解释 |
$1：BGP Network的信息 |
|
举例 |
Create BGP Network:[BGP Network:{ ID: c4cce82c-980d-45b6-935d-274d08221a63 CIDR: 43.4.4.0/24 Router ID: 237fa40d-7118-4502-a985-81c1decf5271 IP Version: IPv4 Device list: [[BGP Network device: { Device ID: 6973d2a2-a736-45d6-9630-34879b960cf9 } ]] }] |
|
日志说明 |
用户进行了创建BGP Network的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · Invalid JSON format：无效的JSON格式 · The service is disabled：服务未启动 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · The BGP local network UUID is invalid：无效的BGP本地网段路由UUID · You must specify a vRouter UUID for the BGP local network：BGP本地网段路由所属的虚拟路由器UUID不能为空 · The vRouter UUID for the BGP local network is invalid：BGP本地网段路由所属的虚拟路由器UUID无效 · The device list contains devices without a UUID：设备列表中存在未配置UUID的设备 · Devices with invalid UUIDs exist：设备列表中存在无效UUID的设备 · Devices with the same UUID exist：设备列表中存在重复UUID的设备 · The specified device does not exist：指定的设备不存在 · Only border devices and access devices are supported：设备类型仅支持边界设备和接入设备 · You must specify an IP version for the BGP local network：BGP本地网段路由的IP版本不能为空 · The IP version of the BGP local network is invalid：无效的BGP本地网段路由的IP版本 · You must specify a CIDR mask for the BGP local network：BGP本地网段路由的CIDR不能为空 · The BGP local network and its CIDR mask must be the same IP version：BGP本地网段路由的CIDR和IP版本不一致 · A BGP local network already exists with the specified UUID：BGP本地网段路由UUID已存在 · The vRouter for the BGP local network does not exist：BGP本地网段路由所属的虚拟路由器不存在 · The vRouter has BGP local networks with the same CIDR mask：虚拟路由器下存在相同CIDR的BGP本地网段路由 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · Invalid IP address：无效的IP地址 · Colon hexadecimal notation, Only global unicast addresses are supported：冒分十六进制格式，仅支持全球单播地址 |
|
关键字 |
ACTION_UPDATE_BGP_NETWORK_OP |
|
日志内容 |
Update BGP Network:$1 |
|
参数解释 |
$1：BGP Network的信息 |
|
举例 |
Update BGP Network:BGP Network:{ ID: b15a0329-644f-494e-ad86-0b66b33f8adf CIDR: 9::7/128 Router ID: 237fa40d-7118-4502-a985-81c1decf5271 IP Version: IPv6 Device list: [[BGP Network device: { Device ID: 6973d2a2-a736-45d6-9630-34879b960cf9 } , BGP Network device: { Device ID: e8754b47-2759-4fc6-8627-a4804b20ba4a } ]] } |
|
日志说明 |
用户进行了修改BGP Network的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · Invalid JSON format：无效的JSON格式 · The service is disabled：服务未启动 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · You have no privilege to perform this operation：用户无权限执行此操作 · The device list contains devices without a UUID：设备列表中存在未配置UUID的设备 · Devices with invalid UUIDs exist：设备列表中存在无效UUID的设备 · Devices with the same UUID exist：设备列表中存在重复UUID的设备 · The specified BGP local network UUID does not exist：指定的BGP本地网段路由UUID不存在 · The specified device does not exist：指定的设备不存在 · Only border devices and access devices are supported：设备类型仅支持边界设备和接入设备 · The CIDR mask, IP version, and vRouter UUID for a BGP local network cannot be edited：BGP本地网段路由CIDR、IP版本和路由UUID不允许修改 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · The user does not have permission to update the resources created by the application's online and offline：用户无权限更新应用上下线创建的资源 |
|
关键字 |
ACTION_DELETE_BGP_NETWORK_OP |
|
日志内容 |
Delete BGP Network: $1. |
|
参数解释 |
$1：BGP Network的ID |
|
举例 |
Delete BGP Network:29e3d995-13cd-417e-9d21-bb0e4c419f49 |
|
日志说明 |
用户进行了删除BGP Network的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · The service is disabled：服务未启动 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · The user does not have permission to delete the resources created by the application's online and offline：用户无权限删除应用上下线创建的资源 |
|
关键字 |
CREATE_TOPOLOGY_PLAN_OP |
|
日志内容 |
Created topology plan: $1 |
|
参数解释 |
$1：规划方式信息 |
|
举例 |
Created topology plan: DevicePlanConfig [ id=ad175a08-cead-40b4-a3a8-9118897f9491, planType=Device Num, fabricId=0709a2bb-4f9a-4e17-93e2-64abad239607, type=BorderSpine, borderNum=1, spineNum=1, aggregationNum=2, leafNum=2, accessNum=0 ] |
|
日志说明 |
用户进行了创建规划方式的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · The service is disabled：服务未启动 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · You have no privilege to perform this operation：当前用户无权限执行此操作 · Invalid JSON format：无效的JSON格式 · Fabric is not exsit：指定的Fabric不存在 · A topology plan has been created for the fabric：该Fabric已进行拓扑规划 · Invalid topology plan type：无效的规划方式 · The border type is invalid：无效的border类型 · The number of border nodes must be in the range of 0 to 4：无效的Border个数，个数必须在0～4之间 · The number of spine nodes must be in the range of 1 to 10：无效的Spine个数，个数必须在1～10之间 · The number of aggregation nodes must be in the range of 0 to 300. If the number of aggregation nodes is not 0, the number of aggregation nodes must be equal to or higher than the number of spine nodes：无效的Aggregation数量，数量必须在0～300之间，且Aggregation不为0时，要求大于等于Spine的数量 · The number of leaf nodes must be in the range of 1 to 300：无效的Leaf个数，个数必须在1～300之间 · The number of access nodes must be in the range of 0 to 300：无效的Access个数，个数必须在0～300之间 · When the border type is border spine, the number of border devices cannot be higher than the number of spine devices：Border类型为Border Spine时，Border个数不能多于Spine个数 · When the border type is border leaf, the number of border devices must be smaller than the number of leaf devices：Border类型为Border Leaf时，Border个数必须少于Leaf个数 · The number of leaf devices cannot be smaller than the number of aggregation devices：Leaf个数不能少于Aggregation个数 · The number of leaf devices cannot be smaller than the number of spine devices：Leaf个数不能少于Spine个数 |
|
关键字 |
UPDATE_TOPOLOGY_PLAN_OP |
|
日志内容 |
Updated topology plan: $1 |
|
参数解释 |
$1：规划方式信息 |
|
举例 |
Updated topology plan:DevicePlanConfig [ id=a1848d1b-cc3f-4639-bdd7-d195f573b31f, planType=Device Info, fabricId=9bcb3cee-c166-47d4-ba99-a5cb70b0862f, type=BorderSpine, borderNum=0, spineNum=0, aggregationNum=0, leafNum=0, accessNum=0 ] |
|
日志说明 |
用户进行了更新指定UUID规划方式的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · The service is disabled：服务未启动 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · You have no privilege to perform this operation：当前用户无权限执行此操作 · Invalid JSON format：无效的JSON格式 · The topology plan does not exist：指定的规划方式记录未找到 · Fabric is not exsit：指定的Fabric不存在 · A topology plan has been created for the fabric：该Fabric已进行拓扑规划 · Invalid topology plan type：无效的规划方式 · The border type is invalid：无效的border类型 · The number of border nodes must be in the range of 0 to 4：无效的Border个数，个数必须在0～4之间 · The number of spine nodes must be in the range of 1 to 10：无效的Spine个数，个数必须在1～10之间 · The number of aggregation nodes must be in the range of 0 to 300. If the number of aggregation nodes is not 0, the number of aggregation nodes must be equal to or higher than the number of spine nodes：无效的Aggregation数量，数量必须在0～300之间，且Aggregation不为0时，要求大于等于Spine的数量 · The number of leaf nodes must be in the range of 1 to 300：无效的Leaf个数，个数必须在1～300之间 · The number of access nodes must be in the range of 0 to 300：无效的Access个数，个数必须在0～300之间 · When the border type is border spine, the number of border devices cannot be higher than the number of spine devices：Border类型为Border Spine时，Border个数不能多于Spine个数 · When the border type is border leaf, the number of border devices must be smaller than the number of leaf devices：Border类型为Border Leaf时，Border个数必须少于Leaf个数 · The number of leaf devices cannot be smaller than the number of aggregation devices：Leaf个数不能少于Aggregation个数 · The number of leaf devices cannot be smaller than the number of spine devices：Leaf个数不能少于Spine个数 |
|
关键字 |
DELETED_TOPOLOGY_PLAN_OP |
|
日志内容 |
Deleted topology plan: $1 |
|
参数解释 |
$1：规划方式的UUID信息 |
|
举例 |
Deleted topology plan: id:[a1848d1b-cc3f-4639-bdd7-d195f573b31f] |
|
日志说明 |
用户进行了删除指定规划方式的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · The service is disabled：服务未启动 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · You have no privilege to perform this operation：当前用户无权限执行此操作 · Invalid JSON format：无效的JSON格式 · The topology plan doesn't exist：指定的规划方式不存在 |
|
关键字 |
DELETE_UNMANAGED_DEVICE_OP |
|
日志内容 |
Deleted unmanaged device: $1 |
|
参数解释 |
$1：未纳管设备UUID |
|
举例 |
Deleted unmanaged device: 6baed8a7-1220-48ad-aa23-8a1aa502cf01 |
|
日志说明 |
用户进行了删除未纳管设备的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · Invalid JSON format：无效的JSON格式 · Invalid parameter：无效的参数 · You have no privilege to perform this operation：用户无权限执行此操作 · The unmanaged device does not exist：指定的未纳管设备不存在 · The device is managed by the controller and can't be deleted：该设备正在被纳管，无法删除 |
|
关键字 |
ALLOC_IPV4_NGFW_POOL_OP |
|
日志内容 |
Allocated an IPv4 address from the NGFW address pool: $1. |
|
参数解释 |
$1：申请到的IP信息 |
|
举例 |
Allocated an IPv4 address from the NGFW address pool: [ IP:[1.1.1.1] Mask:[255.255.255.0] Gateway:[1.1.1.3] ] |
|
日志说明 |
用户在虚拟管理网络申请到一个IPv4地址 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · The IP address pool does not exist：IP地址池不存在 · Failed to obtain resources from NGFWM：从NGFWM获取资源失败 |
|
关键字 |
REKEASE_NGFW_POOL_IPV4_OP |
|
日志内容 |
Released IPv4 address $1 in the NGFW address pool. |
|
参数解释 |
$1：需要释放的IP地址 |
|
举例 |
Released IPv4 address [3.3.3.3] in the NGFW address pool. |
|
日志说明 |
用户在虚拟管理网络释放一个IPv4地址 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · Invalid IP address：无效的IP地址 |
|
关键字 |
ALLOC_IPV6_NGFW_POOL_OP |
|
日志内容 |
Allocated an IPv6 address from the NGFW address pool: $1 |
|
参数解释 |
$1：申请到的IP信息 |
|
举例 |
Allocated an IPv6 address from the NGFW address pool: [ IP:[ 5AA::1] Mask:[ FFFF:FFFF:FFFF:FFFF:0:0:0:0] Gateway:[ 5AA::12] ] |
|
日志说明 |
用户在虚拟管理网络申请到一个IPv6地址 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · The IP address pool does not exist：IP地址池不存在 · Failed to obtain resources from NGFWM：从NGFWM获取资源失败 |
|
关键字 |
REKEASE_NGFW_POOL_IPV6_OP |
|
日志内容 |
Released IPv6 address $1 in the NGFW address pool. |
|
参数解释 |
$1：需要释放的IP地址 |
|
举例 |
Released IPv6 address [5AA::1] in the NGFW address pool. |
|
日志说明 |
用户在虚拟管理网络释放一个IPv6地址 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · Invalid IP address：无效的IP地址 |
|
关键字 |
CREATE_SECIPPOOL_OP |
|
日志内容 |
Created security IP address pool: $1 |
|
参数解释 |
$1：安全IP地址池信息 |
|
举例 |
Created security IP address pool: IP pool ID:[b4514438-8487-4209-9106-af197c458422] IP pool name:[DEFAULT_SEC_DEV_INNER_NETWORK] IP pool type:[SEC_DEV_INNER_NETWORK] IP pool allocated:[false] IP pool needBind:[false] Address range list: [ { Pool addrStart is:[96.0.0.1] Pool addrEnd is:[96.0.0.100] Pool mask is:[0] Pool isuse is:[false] Pool allocatedIpList is:[null] } { Start IP:[96::1] End IP:[96::100] Status:[false] Mask:[0] Assigned addresses:[[]] } ] IPv6 address range list: [ { Start IP:[96::1] End IP:[96::100] Status:[false] Mask:[0] Assigned addresses:[[]] } ] |
|
日志说明 |
用户进行了创建安全IP地址池的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · The service is disabled：服务未启动 · Invalid parameter：无效的配置参数 · Invalid JSON format：无效的JSON格式 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Operation failed because the user role doesn't have the permission：用户无权限执行此操作 · Invalid address pool type：无效的地址池类型 · Invalid name：无效的名称 · The IP address pool ID already exists：地址池ID已经存在 · The CIDR of the IP address pool is invalid：地址池指定的子网无效 · The IP address pool type is already exist：地址池类型已经存在 · The IP address pool name already exists：地址池名称已经存在 · The start IP address and end IP address must belong to the specified network：起始IP地址或结束IP地址不在网段地址范围内 · The IP address range overlaps with another one：该地址段与其它地址段的IP地址重叠 · The start IP address or end IP address cannot be a broadcast address or network address：起始IP地址和结束IP地址不能为广播地址和网络地址 · Unknown internal server error：未知的内部服务器错误 · For each IP address pool type, only one default address pool is allowed：每种类型的默认地址池只能添加一个 · The network address overlaps with a network address in another IP address pool：该网段地址与其他地址池的网段地址重叠 · Address ranges are required for this type of address pools：该类型地址池的地址段不能为空 |
|
关键字 |
UPDATE_SECIPPOOL_OP |
|
日志内容 |
Updated security IP address pool: $1 |
|
参数解释 |
$1：安全IP地址池信息 |
|
举例 |
Updated security IP address pool: IP pool ID:[2a0084f9-b53e-4386-9d43-7945511f7385] IP pool name:[DEFAULT_SEC_DEV_INNER_NETWORK] IP pool type:[SEC_DEV_INNER_NETWORK] IP pool allocated:[false] IP pool needBind:[false] Address range list: [ { Pool addrStart is:[97.0.0.1] Pool addrEnd is:[97.0.0.100] Pool mask is:[0] Pool isuse is:[false] Pool allocatedIpList is:[null] } { Start IP:[96::1] End IP:[96::100] Status:[false] Mask:[0] Assigned addresses:[[]] } { Start IP:[97::1] End IP:[97::100] Status:[false] Mask:[0] Assigned addresses:[[]] } ] IPv6 address range list: [ { Start IP:[96::1] End IP:[96::100] Status:[false] Mask:[0] Assigned addresses:[[]] } { Start IP:[97::1] End IP:[97::100] Status:[false] Mask:[0] Assigned addresses:[[]] } ] |
|
日志说明 |
用户进行了修改安全IP地址池的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · The service is disabled：服务未启动 · The controller is not the active leader：该控制组件不是主Leader · Invalid name：无效的名称 · Invalid JSON format：无效的JSON格式 · You have no privilege to perform this operation：用户无权限执行此操作 · The IP address pool name already exists：地址池名称已经存在 · The IP address pool is already used：不允许修改正在使用的地址池 · The IP address range overlaps with another one：该地址段与其它地址段的IP地址重叠 · The network address field is read only：网段地址为只读字段 · The status field is read only：状态字段为只读字段 · The start IP address and end IP address must belong to the specified network：起始IP地址或结束IP地址不在网段地址范围内 · The start IP address or end IP address cannot be a broadcast address or network address：起始IP地址和结束IP地址不能为广播地址和网络地址 · Address ranges are required for this type of address pools：该类型地址池的地址段不能为空 · Unknown internal server error：未知的内部服务器错误 · Address ranges are required for this type of address pools：该类型地址池的地址段不能为空 |
|
关键字 |
DELETE_SECIPPOOL_OP |
|
日志内容 |
Deleted security IP address pool: $1 |
|
参数解释 |
$1：安全IP地址池UUID |
|
举例 |
Deleted security IP address pool: 4272f686-1faf-4587-b7a2-2f68246666e2 |
|
日志说明 |
用户进行了安全IP地址池的删除操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · Invalid JSON format：无效的JSON格式 · The service is disabled：服务未启动 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · The IP address pool doesn't exist：地址池不存在 · The IP address pool is already used：不允许删除正在使用的地址池 · Unknown internal server error：未知的内部服务器错误 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_ADDRESS_POOL_SET_OP |
|
日志内容 |
Created address pool set: “$1” |
|
参数解释 |
$1：地址池集信息 |
|
举例 |
Created address pool set: [ ID: [ffce2917-f9a6-4070-b695-c875724ec4c9] Name: [remote59] Type: [out-of-band] Fabric ID: [137ce4cc-ae72-4570-903c-bca9f93cd313] VTEP IP Pool: [[ ID: [49826d9b-bac4-424e-8c3c-99362a96a7d9] ] ] Underlay IP Pool: [[ ID: [1699948f-6022-4f9f-ba16-7a73cdf0b23b] ] ] Management IP Pool:[[ ID: [e79c43a9-bb31-4ae7-98e6-05660aae96fe] ] ] Auto Deployment IP Pool:[[ ID: [195714f3-079e-4ace-a111-a32b55bd6b8a] ] ] Remote: [true] ] |
|
日志说明 |
用户进行了创建地址池集的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · You have no privilege to perform this operation：用户无权限执行此操作 · Unknown internal server error：未知的内部服务器错误 · The management IP pool is required：The management IP pool is required · The management address pool doesn't exist：指定的管理网地址池不存在 · The management address pool is used by another address pool set：指定管理网络已被其它地址池集使用 · The IP pool for auto deployment does not exist：指定的自动化上线地址池不存在 · The IP pool for auto deployment has been bound to another address pool set：指定的自动化上线地址池已被其他地址池集绑定 · The VTEP IP(Loopback IP) pool is required：未指定管理网VTEP地址池 · The underlay IP pool is required：未指定Underlay互通地址池 · The VTEP IP(Loopback IP) pool does not exist：指定的管理网VTEP地址池不存在 · The underlay IP pool does not exist：指定的Underlay互通地址池不存在 · The VTEP IP(Loopback IP) pool has been used：指定的管理网VTEP地址池已经被使用 · The underlay IP pool has been used：指定的Underlay互通地址池已被使用 · The underlay IP pool contains a VTEP IP that has already been used：指定的Underlay互通地址段中包含了已被使用的VTEP IP地址 · The address pool set already exists：指定UUID的地址池集已存在 · Invalid management network type：无效的管理网络类型 · Invalid IP pool for auto deployment：无效的自动化上线地址池 · Invalid VTEP IP type：无效的VTEP IP类型 · Invalid underlay pool type：无效的Underlay互通地址池 · The fabric ID is required：所属Fabric ID不能为空 · The fabric does not exist：指定的Fabric不存在 · The underlay address pool cannot contain existing VTEP IP addresses：Underlay互通地址段范围内不允许包含已经存在的VTEP IP地址 · An underlay address pool cannot contain loopback0 interface IP addresses of auto deployment device information：Underlay互通地址池范围不允许包含自动化部署的设备信息的Loopback0 IP地址 · The underlay IP pool conflicts with the underlay IP range specified in the device deployment template：Underlay互通地址池与设备上线模板的Underlay IP范围冲突 · The underlay IP pool conflicts with the loopback1 IP range specified in the device deployment template：Underlay互通地址池与设备上线模板的Loopback1 IP范围冲突 · The VTEP IP(Loopback IP) pool conflicts with the loopback1 IP range specified in the device deployment template：VTEP IP(Loopback IP)地址池与设备上线模板的Loopback1 IP范围冲突 · The VTEP IP(Loopback IP) pool conflicts with the underlay IP range specified in the device deployment template：VTEP IP(Loopback IP)地址池与设备上线模板的Underlay IP范围冲突 · The management address pool and the IP pool for auto deployment must be different：管理网地址池和自动化上线地址池不允许指定相同的IP地址池 · You can configure a remote address pool set only when the underlay protocol is OSPF：当Underlay物理协议为OSPF时，才支持配置远端地址池集 · The temp manage address pool IP version is inconsistent whith the control IP version：自动化上线地址池，只能配置IPV4或者IPV6 · The manage address pool IP version is inconsistent whith the control IP version:管理网地址池，只能配置IPV4或者IPV6 · The vtep address pool IP version is inconsistent whith the control IP version:vtep地址池，只能配置IPV4或者IPV6 · The underlay address pool IP version is inconsistent whith the control IP version:underlay地址池，只能配置IPV4或者IPV6 · The underlay address pool IP version is inconsistent whith the control IP version:不同地址池集间的网关地址不能相同 · Please specify an auto deployment address pool for the remote address pool set：远端地址池集的自动化上线地址池不能为空 · The address pool set name cannot exceed 255 characters：地址池集的名称最长255个字符 · An address pool set already exists with the specified name：指定地址池集的名称已存在 · Each fabric can have only one local address pool set：Fabric下只支持配置一个本地地址池类型的地址池集 · If EBGP is used as the underlay routing protocol in an IPv6 environment, only dedicated IP allocation is supported for interconnect ports：IPv6环境Underlay路由协议使用EBGP时，互联口地址配置方式仅支持独立地址 · Remote address pools do not support assigning dedicated IP addresses to interconnect ports：远端地址池不支持互联口地址配置方式为独立地址 |
|
关键字 |
UPDATE_ADDRESS_POOL_SET_OP |
|
日志内容 |
Updated address pool set: “$1” |
|
参数解释 |
$1：地址池集信息 |
|
举例 |
Updated address pool set: [ ID: [ffce2917-f9a6-4070-b695-c875724ec4c9] Name: [remote59] Type: [out-of-band] Fabric ID: [137ce4cc-ae72-4570-903c-bca9f93cd313] VTEP IP Pool: [[ ID: [09a3d61a-9307-4b7a-874b-8ab370697d72] ] ] Underlay IP Pool: [[ ID: [1699948f-6022-4f9f-ba16-7a73cdf0b23b] ] ] Management IP Pool:[[ ID: [e79c43a9-bb31-4ae7-98e6-05660aae96fe] ] ] Auto Deployment IP Pool:[[ ID: [195714f3-079e-4ace-a111-a32b55bd6b8a] ] ] Remote: [true] ] |
|
日志说明 |
用户进行了修改地址池集的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · You have no privilege to perform this operation：用户无权限执行此操作 · Unknown internal server error：未知的内部服务器错误 · The management IP pool is required：The management IP pool is required · The management address pool doesn't exist：指定的管理网地址池不存在 · The management address pool is used by another address pool set：指定管理网络已被其它地址池集使用 · The IP pool for auto deployment does not exist：指定的自动化上线地址池不存在 · The IP pool for auto deployment has been bound to another address pool set：指定的自动化上线地址池已被其他地址池集绑定 · The underlay IP pool is required：未指定Underlay互通地址池 · The VTEP IP(Loopback IP) pool does not exist：指定的管理网VTEP地址池不存在 · The underlay IP pool does not exist：指定的Underlay互通地址池不存在 · The VTEP IP(Loopback IP) pool has been used：指定的管理网VTEP地址池已经被使用 · The underlay IP pool has been used：指定的Underlay互通地址池已被使用 · The underlay IP pool contains a VTEP IP that has already been used：指定的Underlay互通地址段中包含了已被使用的VTEP IP地址 · The management mode cannot be edited：管理类型不允许修改 · The address pool set doesn't exist：指定的地址池集不存在 · The fabric ID cannot be modified：Fabric ID不允许修改 · Invalid management network type：无效的管理网络类型 · Invalid IP pool for auto deployment：无效的自动化上线地址池 · Invalid VTEP IP type：无效的VTEP IP类型 · Invalid underlay pool type：无效的Underlay互通地址池 · The underlay address pool cannot contain existing VTEP IP addresses：Underlay互通地址段范围内不允许包含已经存在的VTEP IP地址 · An underlay address pool cannot contain loopback0 interface IP addresses of auto deployment device information：Underlay互通地址池范围不允许包含自动化部署的设备信息的Loopback0 IP地址 · The management address pool and the IP pool for auto deployment must be different：管理网地址池和自动化上线地址池不允许指定相同的IP地址池 · The temp manage address pool IP version is inconsistent whith the control IP version：自动化上线地址池，只能配置IPV4或者IPV6 · The manage address pool IP version is inconsistent whith the control IP version:管理网地址池，只能配置IPV4或者IPV6 · The vtep address pool IP version is inconsistent whith the control IP version:vtep地址池，只能配置IPV4或者IPV6 · The underlay address pool IP version is inconsistent whith the control IP version:underlay地址池，只能配置IPV4或者IPV6 · The underlay address pool IP version is inconsistent whith the control IP version:不同地址池集间的网关地址不能相同 · Please specify an auto deployment address pool for the remote address pool set：远端地址池集的自动化上线地址池不能为空 · You cannot edit the IP pool for auto deployment, because the address pool set contains devices that are being deployed automatically：存在正在自动化上线的设备，不允许修改自动化上线地址池 · The address pool set name cannot exceed 255 characters：地址池集的名称最长255个字符 · An address pool set already exists with the specified name：指定地址池集的名称已存在 · If EBGP is used as the underlay routing protocol in an IPv6 environment, only dedicated IP allocation is supported for interconnect ports：IPv6环境Underlay路由协议使用EBGP时，互联口地址配置方式仅支持独立地址 · Remote address pools do not support assigning dedicated IP addresses to interconnect ports：远端地址池不支持互联口地址配置方式为独立地址 |
|
关键字 |
DELETE_ADDRESS_POOL_SET_OP |
|
日志内容 |
Deleted address pool set: “$1”. |
|
参数解释 |
$1：地址池集信息 |
|
举例 |
Deleted address pool set: ID: [ab29572d-a88a-4600-af70-c4c01972ab0e] Fabric name: [ospf] |
|
日志说明 |
用户进行了删除地址池集的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · You have no privilege to perform this operation：用户无权限执行此操作 · Unknown internal server error：未知的内部服务器错误 · The address pool set doesn't exist：指定的地址池集不存在 · The address pool set contains devices that are being deployed automatically：指定地址池集下的存在正在自动化上线的设备 |
|
关键字 |
IMPORT_TENANT_OP |
|
日志内容 |
Bulk created tenants: $1. |
|
参数解释 |
$1：批量操作信息 |
|
举例 |
Bulk created tenants: fileName:[租户创建模板.xlsx], totalNum:[1], successNum:[0], failedNum:[1]. |
|
日志说明 |
用户进行了批量创建租户操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · Incorrect file name：文件名错误 · Failed to read the Excel file：Excel文件读取失败 · Failed to parse data：数据解析错误 |
|
关键字 |
IMPORT_UPDATE_TENANT_OP |
|
日志内容 |
Bulk updated tenants: $1. |
|
参数解释 |
$1：批量操作信息 |
|
举例 |
Bulk updated tenants: fileName: [租户更新模板.xlsx], totalNum:[1], successNum:[0], failedNum:[1]. |
|
日志说明 |
用户进行了批量更新租户操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · Incorrect file name：文件名错误 · Failed to read the Excel file：Excel文件读取失败 · Failed to parse data：数据解析错误 |
|
关键字 |
IMPORT_DELETE_TENANT_OP |
|
日志内容 |
Bulk deleted tenants: $1. |
|
参数解释 |
$1：批量操作信息 |
|
举例 |
Bulk deleted tenants: nfileName: [租户删除模板.xlsx], totalNum:[1], successNum:[0], failedNum:[1]. |
|
日志说明 |
用户进行了批量删除租户操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · Incorrect file name：文件名错误 · Failed to read the Excel file：Excel文件读取失败 · Failed to parse data：数据解析错误 |
|
关键字 |
EXPORT_TENANT_OP |
|
日志内容 |
Bulk exported tenants: $1. |
|
参数解释 |
$1：批量操作信息 |
|
举例 |
Bulk exported tenants: 租户-2021-06-04 09-27-59.xlsx |
|
日志说明 |
用户进行了批量导出租户操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · Failed to export the file：Excel文件导出失败 |
|
关键字 |
IMPORT_GATEWAY_OP |
|
日志内容 |
Bulk created gateways: $1. |
|
参数解释 |
$1：批量操作信息 |
|
举例 |
Bulk created gateways: fileName: [出口网关创建模板.xlsx], totalNum:[1], successNum:[0], failedNum:[1]. |
|
日志说明 |
用户进行了批量创建出口网关操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · Incorrect file name：文件名错误 · Failed to read the Excel file：Excel文件读取失败 · Failed to parse data：数据解析错误 · The value for the Reduce External Routes parameter is invalid：无效的外网路由精简配置参数 · Only border gateways of the manual deployment type support external route reduction：仅手动预配置类型出口网关支持配置外网路由精简 · When the network cloud feature is enabled, external route reduction is not supported：网络云场景不支持配置出口网关的外网路由精简 |
|
关键字 |
IMPORT_UPDATE_GATEWAY_OP |
|
日志内容 |
Bulk updated gateways: $1. |
|
参数解释 |
$1：批量操作信息 |
|
举例 |
Bulk updated gateways: fileName:[ 出口网关更新模板.xlsx], totalNum:[1], successNum:[0], failedNum:[1]. |
|
日志说明 |
用户进行了批量更新出口网关操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · Incorrect file name：文件名错误 · Failed to read the Excel file：Excel文件读取失败 · Failed to parse data：数据解析错误 · The value for the Reduce External Routes parameter is invalid：无效的外网路由精简配置参数 · Only border gateways of the manual deployment type support external route reduction：仅手动预配置类型出口网关支持配置外网路由精简 · When the network cloud feature is enabled, external route reduction is not supported：网络云场景不支持配置出口网关的外网路由精简 · After you enable external route reduction for a border gateway, vRouters bound to that border gateway cannot have the same internal subnet address：切换外网路由精简为开启时，不允许该出口网关绑定的虚拟路由器存在网段相同的内网子网 · Cannot edit the vpnInstance field for the gateway member because the gateway member has been used by a vRouter：该网关成员已被虚拟路由器引用，vpnInstance字段不允许被修改 |
|
关键字 |
IMPORT_DELETE_GATEWAY_OP |
|
日志内容 |
Bulk deleted gateways: $1. |
|
参数解释 |
$1：批量操作信息 |
|
举例 |
Bulk deleted gateways: fileName:[ 出口网关删除模板.xlsx], totalNum:[1], successNum:[0], failedNum:[1]. |
|
日志说明 |
用户进行了批量删除出口网关操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · Incorrect file name：文件名错误 · Failed to read the Excel file：Excel文件读取失败 · Failed to parse data：数据解析错误 |
|
关键字 |
EXPORT_GATEWAY_OP |
|
日志内容 |
Bulk exported gateways: $1. |
|
参数解释 |
$1：批量操作信息 |
|
举例 |
Bulk exported gateways: 出口网关-2021-06-04 09-27-59.xlsx |
|
日志说明 |
用户进行了批量导出出口网关操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · Failed to export the file：Excel文件导出失败 |
|
关键字 |
BATCH_ADD_VLAN_VXLAN_INTERFACE_OP |
|
日志内容 |
Bulk created VLAN-Network mappings: $1. |
|
参数解释 |
$1：批量操作信息 |
|
举例 |
Bulk created VLAN-Network mappings: fileName:[VLAN-NETWORK映射创建模板.xlsx], totalNum:[1], successNum:[0], failedNum:[1]. |
|
日志说明 |
用户进行了批量创建VLAN-Network映射操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · Incorrect file name：文件名错误 · Failed to read the Excel file：Excel文件读取失败 · Failed to parse data：数据解析错误 · The interface of the service leaf device is bound to a resource access template. You cannot apply VLAN-related mappings to the interface：Service Leaf设备的接口被资源接入模板绑定时，不可用于其他映射 · QinQ mapping and VLAN-network mapping do not support global VLAN-VXLAN mappings：QinQ映射和VLAN-Network映射不支持全局VLAN-VXLAN映射 |
|
关键字 |
BATCH_UPDATE_VLAN_VXLAN_INTERFACE_OP |
|
日志内容 |
Bulk updated VLAN-Network mappings: $1. |
|
参数解释 |
$1：批量操作信息 |
|
举例 |
Bulk updated VLAN-Network mappings: fileName:[ VLAN-NETWORK映射更新模板.xlsx], totalNum:[1], successNum:[0], failedNum:[1]. |
|
日志说明 |
用户进行了批量更新VLAN-Network映射操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · Incorrect file name：文件名错误 · Failed to read the Excel file：Excel文件读取失败 · Failed to parse data：数据解析错误 · The interface of the service leaf device is bound to a resource access template. You cannot apply VLAN-related mappings to the interface：Service Leaf设备的接口被资源接入模板绑定时，不可用于其他映射 · You cannot edit the apply_scope parameter for a global VLAN-VXLAN mapping：全局VLAN-VXLAN映射apply_scope字段不允许修改 · The physical access device already binding a global VLAN-VXLAN mapping cannot binding other VLAN-VXLAN binding：设备已经绑定全局VLAN-VXLAN映射，不允许再绑定其他映射 |
|
关键字 |
BATCH_DELETE_VLAN_VXLAN_INTERFACE_OP |
|
日志内容 |
Bulk deleted VLAN-Network mappings: $1. |
|
参数解释 |
$1：批量操作信息 |
|
举例 |
Bulk deleted VLAN-Network mappings: nfileName:[ VLAN-NETWORK映射删除模板.xlsx], totalNum:[1], successNum:[0], failedNum:[1]. |
|
日志说明 |
用户进行了批量删除VLAN-Network映射操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · Incorrect file name：文件名错误 · Failed to read the Excel file：Excel文件读取失败 · Failed to parse data：数据解析错误 |
|
关键字 |
BATCH_EXPORT_VLAN_VXLAN_INTERFACE_OP |
|
日志内容 |
Bulk exported VLAN-VXLAN mappings: $1. |
|
参数解释 |
$1：批量操作信息 |
|
举例 |
Bulk exported VLAN-VXLAN mappings: VLAN-NETWORK映射-2021-06-04 09-27-59.xlsx |
|
日志说明 |
用户进行了批量导出VLAN-Network映射操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · Failed to export the file：Excel文件导出失败 |
|
关键字 |
BATCH_ADD_PVLAN_INTERFACE_OP |
|
日志内容 |
Bulk created PVLAN mappings: $1. |
|
参数解释 |
$1：批量操作信息 |
|
举例 |
Bulk created PVLAN mappings: fileName:[PVLAN映射创建模板.xlsx], totalNum:[1], successNum:[0], failedNum:[1]. |
|
日志说明 |
用户进行了批量创建PVLAN映射操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · Incorrect file name：文件名错误 · Failed to read the file：Excel文件读取失败 · Failed to parse data：数据解析错误 · The interface of the service leaf device is bound to a resource access template. You cannot apply VLAN-related mappings to the interface：Service Leaf设备的接口被资源接入模板绑定时，不可用于其他映射 |
|
关键字 |
BATCH_UPDATE_PVLAN_INTERFACE_OP |
|
日志内容 |
Bulk updated PVLAN mappings: $1. |
|
参数解释 |
$1：批量操作信息 |
|
举例 |
Bulk updated PVLAN mappings: fileName:[ PVLAN映射更新模板.xlsx], totalNum:[1], successNum:[0], failedNum:[1]. |
|
日志说明 |
用户进行了批量更新PVLAN映射操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · Incorrect file name：文件名错误 · Failed to read the file：Excel文件读取失败 · Failed to parse data：数据解析错误 · The interface of the service leaf device is bound to a resource access template. You cannot apply VLAN-related mappings to the interface：Service Leaf设备的接口被资源接入模板绑定时，不可用于其他映射 · The physical access device already binding a global VLAN-VXLAN mapping cannot binding other VLAN-VXLAN binding：设备已经绑定全局VLAN-VXLAN映射，不允许再绑定其他映射 |
|
关键字 |
BATCH_DELETE_PVLAN_INTERFACE_OP |
|
日志内容 |
Bulk deleted PVLAN mappings: $1. |
|
参数解释 |
$1：批量操作信息 |
|
举例 |
Bulk deleted PVLAN mappings: nfileName:[ PVLAN映射删除模板.xlsx], totalNum:[1], successNum:[0], failedNum:[1]. |
|
日志说明 |
用户进行了批量删除PVLAN映射操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · Incorrect file name：文件名错误 · Failed to read the file：Excel文件读取失败 · Failed to parse data：数据解析错误 · The interface of the service leaf device is bound to a resource access template. You cannot apply VLAN-related mappings to the interface：Service Leaf设备的接口被资源接入模板绑定时，不可用于其他映射 |
|
关键字 |
BATCH_EXPORT_PVLAN_INTERFACE_OP |
|
日志内容 |
Bulk exported PVLAN mappings: $1. |
|
参数解释 |
$1：批量操作信息 |
|
举例 |
Bulk exported PVLAN mappings: PVLAN映射-2021-06-04 09-27-59.xlsx |
|
日志说明 |
用户进行了批量导出PVLAN映射操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · Failed to export the file：Excel文件导出失败 |
|
关键字 |
CREATE_PVLAN_OP |
|
日志内容 |
Created PVLAN mapping : $1 |
|
参数解释 |
$1：PVLAN映射的信息 |
|
举例 |
Created PVLAN mapping : ID: [8c4a9985-e165-480c-8b41-a1e9a4f08003] Name:[sadf] Primary VLAN: [1] Primary VLAN domain ID: [7a9aedbb-4057-405a-9c17-e003ad1d48e1] Primary Network ID: [e0c4b9b3-ec1c-4a18-a3df-4bedda166a38] Data Source: [DEFAULT] SecondMaps: [[ Type: [ISOLATED] VLAN:[12] VXLAN: [202] Network ID: [8f087554-db41-4ba3-82c9-3a0a2727a189] VLan Domain ID : [134798d2-01ca-4ea3-9733-cd74fa1bddb3] ]]] ] |
|
日志说明 |
用户进行了创建PVLAN映射的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · Invalid JSON format：无效的JSON格式 · The service is disabled：服务未启动 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · Invalid name：无效的名称 · You have no privilege to perform this operation：用户无权限执行此操作 · A PVLAN already exists with the specified UUID：PVLAN UUID已存在 · A PVLAN already exists with the specified name：PVLAN名称已存在 · The vNetwork specified for the PVLAN does not exist：PVLAN的虚拟链路层网络不存在 · The PVLAN data source must be default：PVLAN的来源必须为默认 · The PVLAN data source must be VMM：PVLAN的来源必须为VMM · Invalid PVLAN UUID：无效的PVLAN UUID · Please specify a primary VLAN for the PVLAN：PVLAN的主VLAN不能为空 · The primary VLAN ID must be in the range of 1 to 4094：PVLAN的主VLAN取值范围为1-4094的整数 · Please specify a vNetwork by its UUID for the PVLAN：PVLAN的虚拟链路层网络UUID不能为空 · Invalid vNetwork UUID for the PVLAN：无效的PVLAN的虚拟链路层网络UUID · A VLAN-network mapping already exists for the specified vNetwork：指定的虚拟链路层网络已有VLAN-Network映射 · You cannot specify a vNetwork by its name for the PVLAN：不允许指定虚拟链路层网络名称 · You cannot specify a tenant by its UUID for the PVLAN：不允许指定租户UUID · You cannot specify a VLAN-network mapping UUID for the primary VLAN：不允许指定主VLAN映射UUID · Please specify a secondary VLAN：从VLAN不能为空 · You can specify only one secondary VLAN：只支持配置一个从VLAN · You can specify only an isolated-type secondary VLAN：只支持隔离类型的从VLAN · Please specify a secondary VLAN ID：从VLAN的VLAN取值不能为空 · The secondary VLAN ID must be in the range of 1 to 4094：从VLAN的VLAN取值范围为1-4094的整数 · You cannot specify a VXLAN for the secondary VLAN：不允许指定从VLAN的VXLAN · You cannot specify a vNetwork by its UUID for the secondary VLAN：不允许指定从VLAN的虚拟链路层网络UUID · You cannot bind a VLAN-network mapping derived from a PVLAN to interfaces when asymmetric IRB is enabled on the fabric：当Fabric开启非对称IRB转发功能时，则不允许PVLAN派生的VLAN-Network映射进行接口级绑定 · You can bind only VLAN-network mappings to member ports of an edge aggregate interface：聚合边缘接口下的成员接口仅支持绑定VLAN-Network类型映射 |
|
关键字 |
UPDATE_PVLAN_OP |
|
日志内容 |
Updated PVLAN mapping : $1 |
|
参数解释 |
$1：PVLAN映射的信息 |
|
举例 |
Updated PVLAN mapping: ID: [8c4a9985-e165-480c-8b41-a1e9a4f08003] Name:[sadf] Primary VLAN: [1] Primary VLAN domain ID: [7a9aedbb-4057-405a-9c17-e003ad1d48e1] Primary Network ID: [e0c4b9b3-ec1c-4a18-a3df-4bedda166a38] Data Source: [DEFAULT] SecondMaps: [[ Type: [ISOLATED] VLAN:[33] VXLAN: [202] Network ID: [8f087554-db41-4ba3-82c9-3a0a2727a189] VLAN Domain ID : [134798d2-01ca-4ea3-9733-cd74fa1bddb3] ]]] ] |
|
日志说明 |
用户进行了修改PVLAN映射的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · Invalid JSON format：无效的JSON格式 · The service is disabled：服务未启动 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · You have no privilege to perform this operation：用户无权限执行此操作 · Invalid name：无效的名称 · Please specify a PVLAN UUID：PVLAN的UUID不能为空 · You cannot edit the primary VLAN：主VLAN不允许修改 · You cannot edit the vNetwork UUID for the primary VLAN：主VLAN的虚拟链路层网络UUID不允许修改 · The specified PVLAN does not exist：指定的PVLAN不存在 · Insufficient resources in the VXLAN pool：VXLAN池资源不足 · You cannot edit the VLAN-network mappings derived from a PVLAN：PVLAN派生的VLAN-Network映射不允许修改 · A PVLAN already exists with the specified name：PVLAN名称已存在 · The primary VLAN ID must be in the range of 1 to 4094：PVLAN的主VLAN取值范围为1-4094的整数 · You can specify only one secondary VLAN：只支持配置一个从VLAN · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
DELETE_PVLAN_OP |
|
日志内容 |
Deleted PVLAN mapping $1. |
|
参数解释 |
$1：PVLAN映射的ID |
|
举例 |
Deleted PVLAN mapping 747cf8c8-8ab4-4a02-9550-0878dcc4ca5a. |
|
日志说明 |
用户进行了删除PVLAN映射的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · Invalid JSON format：无效的JSON格式 · The service is disabled：服务未启动 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · You have no privilege to perform this operation：用户无权限执行此操作 · The specified PVLAN does not exist：指定的PVLAN不存在 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
ACTION_UPLOAD_INTERFACES |
|
日志内容 |
Uploaded interfaces: $1. |
|
参数解释 |
$1：上传的EXCEL文件名称 |
|
举例 |
Uploaded interfaces: 上传接口配置样例.xlsx |
|
日志说明 |
用户进行了上传接口配置文件的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Only XLS and XLSX files are supported：文件类型仅支持XLS、XLSX类型的Excel文件 · Invalid file：无效的文件 · Please perform the operation on the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Please specify an OSPF policy UUID：OSPF策略UUID不能为空 · Invalid OSPF policy UUID：无效的OSPF策略UUID · The specified OSPF or OSPFv3 policy does not exist：指定的OSPF策略或OSPFv3策略不存在 · The specified OSPF policy or OSPFv3 policy must belong to a tenant：指定的OSPF策略或OSPFv3策略必须在某个租户下 · You have no privilege to perform the operation：用户无权限此操作 |
|
关键字 |
ACTION_IMPORT_INTERFACES |
|
日志内容 |
Imported interfaces: $1. |
|
参数解释 |
$1：导入文件的UUID |
|
举例 |
Imported interfaces: 7bbe4051-4e5d-4f47-bde5-9da97ef55a20.xlsx. |
|
日志说明 |
用户进行了导入配置文件的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Please specify an OSPF policy UUID：OSPF策略UUID不能为空 · Invalid OSPF policy UUID：无效的OSPF策略UUID · The specified OSPF or OSPFv3 policy does not exist：指定的OSPF策略或OSPFv3策略不存在 · The specified OSPF policy or OSPFv3 policy must belong to a tenant：指定的OSPF策略或OSPFv3策略必须在某个租户下 · You have no privilege to perform the operation：用户无权限此操作 · Please perform the operation on the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · The file name cannot be empty：文件名称不能为空 · The import file doesn`t exists：导入文件不存在 · Import template invalid：无效的导入模板 · Invalid device UUID：无效的设备UUID · The device does not exist：指定的设备不存在 · Check the device name and device UUID pairs for mismatches：设备名称不属于指定的设备 · The management IP and device UUID do not match：管理IP和设备UUID不匹配 · Invalid area ID：无效的区域ID · Invalid area type：无效的区域类型 · The interface policy name does not match the OSPFv3 policy UUID：接口策略名称和OSPF策略UUID不匹配 · The interface policy name does not match the OSPF policy UUID：接口策略名称和OSPFv3策略UUID不匹配 · Invalid file：无效的文件 |
|
关键字 |
CREATE_ROUTER_ID_POOL_OP |
|
日志内容 |
Created OSPF resource pool : $1 |
|
参数解释 |
$1：OSPF资源池的信息 |
|
举例 |
Created OSPF resource pool: Resoruce pool configuration { UUID is 691f3eff-e9da-4814-b002-b502367c95e8, Start address is [2.2.2.2] End address is [2.2.2.2], priority is 12} |
|
日志说明 |
用户进行了创建OSPF资源池的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · Invalid name：无效的名称 · The controller is not an active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · Configuration recovery is in progress：配置正在恢复过程中 · Only IPv4 addresses in dotted decimal notation are supported：仅支持IPv4地址，IPv4为点分十进制格式 · Please enter an integer in the range of 1 to 255：取值范围为1-255的整数 · The OSPF resource pool contains overlapping router ID ranges：OSPF资源池范围存在冲突 · This field supports only digits：仅支持数字 · The end router ID cannot be lower than the start router ID：结束Router ID不得小于起始Router ID · The OSPF resource pool ID already exists：OSPF资源池ID已存在 |
|
关键字 |
MODIFY_ROUTER_ID_POOL_OP |
|
日志内容 |
Updated OSPF resource pool : $1 |
|
参数解释 |
$1：OSPF资源池的信息 |
|
举例 |
Updated OSPF resource pool: Resource pool configuration { UUID is 691f3eff-e9da-4814-b002-b502367c95e8, Start address is [2.2.2.2] End address is [2.2.2.2], priority is 123} |
|
日志说明 |
用户进行了修改OSPF资源池的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · Invalid name：无效的名称 · The controller is not an active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · Configuration recovery is in progress：配置正在恢复过程中 · This field supports only digits：仅支持数字 · The specified OSPF resource pool does not exist：指定OSPF资源池不存在 · The start and end router IDs cannot be edited：禁止修改起始RouterID和结束RouterID |
|
关键字 |
DELETE_ROUTER_ID_POOL_OP |
|
日志内容 |
Deleted OSPF resource pool : $1 |
|
参数解释 |
$1：OSPF资源池的信息 |
|
举例 |
Deleted OSPF resource pool: Resource pool configuration { UUID is 691f3eff-e9da-4814-b002-b502367c95e8, Start address is [2.2.2.2] End address is [2.2.2.2], priority is 123} |
|
日志说明 |
用户进行了删除OSPF资源池的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · Invalid name：无效的名称 · The controller is not an active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · Configuration recovery is in progress：配置正在恢复过程中 · The specified OSPF resource pool is in use and cannot be deleted：指定的OSPF资源池已被使用 · The specified OSPF resource pool does not exist：指定OSPF资源池不存在 · The specified router ID does not exist：指定Router ID不存在 |
|
关键字 |
CREATE_ROUTER_ID_POOL_OP |
|
日志内容 |
Allocated OSPF router ID : $1 |
|
参数解释 |
$1：设备分配Router ID的信息 |
|
举例 |
Allocated OSPF router ID: [OSPF router ID configuration { ID=b9c379b1-3740-48e9-bd2b-4acbe0423a1f, device ID='4b402405-36fb-4ec8-8853-e32395491a0f, resource pool ID='d16b4a72-9216-4e02-bc2e-07dcbd43f301', router ID='1.1.1.1, allocation mode='manual}] |
|
日志说明 |
用户进行了手动分配Router ID的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · Invalid name：无效的名称 · The controller is not an active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · Configuration recovery is in progress：配置正在恢复过程中 · Only IPv4 addresses in dotted decimal notation are supported：仅支持IPv4地址，IPv4为点分十进制格式 · The specified router ID is in use：Router ID已被使用 · The specified OSPF resource pool does not exist：指定OSPF资源池不存在 · Failed to manually assign the router ID, because the router ID is not in the OSPF resource pool：手动分配Router ID失败， 该Router ID不在OSPF资源池内 · A device can be bound to only one router ID：设备只允许绑定唯一的Router ID · A router ID can be bound to only one device：一个Router ID只允许绑定唯一的设备 |
|
关键字 |
DELETE_ROUTER_ID_POOL_OP |
|
日志内容 |
Reclaimed OSPF router ID: $1 |
|
参数解释 |
$1：设备分配Router ID的信息 |
|
举例 |
Reclaimed OSPF router ID: OSPF router ID configuration { ID=b9c379b1-3740-48e9-bd2b-4acbe0423a1f, device ID='4b402405-36fb-4ec8-8853-e32395491a0f, resource pool ID='d16b4a72-9216-4e02-bc2e-07dcbd43f301', router ID='1.1.1.1, allocation mode='manual} |
|
日志说明 |
用户进行了清除手动分配Router ID的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · Invalid name：无效的名称 · The controller is not an active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · Configuration recovery is in progress：配置正在恢复过程中 · The specified router ID is in use：Router ID已被使用 · The specified router ID does not exist：指定Router ID不存在 |
|
关键字 |
UPLOAD_ROUTER_ID_OP |
|
日志内容 |
Uploaded router IDs: $1. |
|
参数解释 |
$1：上传的Excel文件名称 |
|
举例 |
Uploaded router IDs: 上传Router ID配置样例.xlsx |
|
日志说明 |
用户进行了上传Router ID配置文件的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Only XLS and XLSX files are supported：文件类型仅支持XLS、XLSX类型的Excel文件 · Invalid file：无效的文件 · Please perform the operation on the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 |
|
关键字 |
IMPORT_ROUTER_ID_OP |
|
日志内容 |
Imported router IDs: $1. |
|
参数解释 |
$1：导入文件的名称 |
|
举例 |
Imported router IDs: 7bbe4051-4e5d-4f47-bde5-9da97ef55a20.xlsx. |
|
日志说明 |
用户进行了导入Router ID配置文件的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Please perform the operation on the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · The import file doesn`t exists：导入文件不存在 · Import template invalid：EXCEL格式不匹配 · The device does not exist：指定的设备不存在 · Invalid file：无效的文件 · Only IPv4 addresses in dotted decimal notation except for 0.0.0.0 are supported：仅支持IPv4地址，IPv4为点分十进制格式 · Failed to manually assign the router ID, because the router ID is not in the OSPF resource pool：手动分配Router ID失败，该Router ID不在OSPF资源池内 · A device can be bound to only one router ID：设备只允许绑定唯一的Router ID · A router ID can be bound to only one device：一个Router ID只允许绑定唯一的设备 · The router ID is required：Router ID不能为空 · The device name is required：设备名称不能为空 |
|
关键字 |
CREATE_DOWNLINKPORT_OP |
|
日志内容 |
OperResult=$1-Reason=$2 |
|
参数解释 |
$1：操作结果 $2：操作失败原因 |
|
举例 |
OperResult="Failed"-Reason="[ExtDownLinkPortCfg [deviceName=55.17, portName=Bridge-Aggregation60, optionResult=false, errorMsg=Interface {Bridge-Aggregation60} cannot be configured as a downlink interface, because it is not an available Layer 2 physical interface.], ExtDownLinkPortCfg [deviceName=55.17, portName=Bridge-Aggregation61, optionResult=false, errorMsg=Interface {Bridge-Aggregation61} cannot be configured as a downlink interface, because it is not an available Layer 2 physical interface.], ExtDownLinkPortCfg [deviceName=55.17, portName=Bridge-Aggregation62, optionResult=false, errorMsg=Interface {Bridge-Aggregation62} cannot be configured as a downlink interface, because it is not an available Layer 2 physical interface.]]" |
|
日志说明 |
用户进行了批量创建下行口的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown internal server error：未知的内部服务器错误 · You have no privilege to perform this operation：用户无权限执行此操作 · The device type does not support binding interfaces：设备类型不匹配 · Invalid JSON format：无效的JSON格式 · Invalid parameter：无效的参数 · The physical access device does not exist：指定的设备不存在 · Interface %s cannot be configured as a downlink interface, because it is a member of an aggregate interface：接口%s为聚合成员接口，不能添加为下行口 · Interface %s cannot be configured as a downlink interface, because it is not an available Layer 2 physical interface：接口%s不是二层物理接口，不能添加为下行口 · The device is inactive：设备处于未激活状态 · Operation not allowed. It would cause the number of downlink ports on the device to exceed the upper limit (1000)：本次操作后，设备所容纳下行口数超出上限，设备所容纳下行口数为上限1000 · You cannot configure downlink interfaces for the device, because the device has been bound to a global VLAN-VXLAN mapping：设备已绑定全局VLAN-VXLAN映射，不允许配置下行口 |
|
关键字 |
DELETE_DOWNLINKPORT_OP |
|
日志内容 |
OperResult=$1-Reason=$2 |
|
参数解释 |
$1：操作结果 $2：导入失败原因 |
|
举例 |
OperResult="Failed"-Reason="[ExtDownLinkPortCfg [deviceName=55.30, portName=Twenty-FiveGigE1/0/21, optionResult=false, errorMsg=Interface {Twenty-FiveGigE1/0/21} cannot be deleted, because a VLAN-VXLAN mapping entry has been applied to it.], ExtDownLinkPortCfg [deviceName=55.30, portName=Twenty-FiveGigE1/0/20, optionResult=false, errorMsg=Interface {Twenty-FiveGigE1/0/20} cannot be deleted, because a VLAN-VXLAN mapping entry has been applied to it.]]" |
|
日志说明 |
用户进行了导入下行口配置文件的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · You have no privilege to perform this operation：用户无权限执行此操作 · Unknown internal server error：未知的内部服务器错误 · Invalid JSON format：无效的JSON格式 · Invalid parameter：无效的参数 · The physical access device does not exist：指定的设备不存在 · Interface %s cannot be deleted, because a VLAN-VXLAN mapping entry has been applied to it：接口%s已绑定VLAN-VXLAN映射，不支持删除 · Interface %s cannot be deleted, because a VLAN-VXLAN mapping entry created from BSM has been applied to the interface：接口%s已绑定BSM创建的VLAN-VXLAN映射，不支持删除 · Interface %s cannot be deleted, because a QinQ mapping entry has been applied to it：接口%s已绑定QinQ映射，不支持删除 · Interface %s cannot be deleted, because a hierarchical binding entry has been applied to the interface：接口%s为层次化绑定接口，不支持删除 · Interface %s cannot be deleted, because a hierarchical QinQ mapping entry has been applied to the interface：接口%s为层次化QinQ绑定接口，不支持删除 · You cannot delete the downlink interface %s, because it has been bound to a resource access template：当前下行口%s已经被资源接入模板绑定,不允许删除 · The device is inactive：设备处于未激活状态 |
|
关键字 |
BATCH_ADD_DOWNLINLPORT_CONFIG_OP |
|
日志内容 |
OperResult=$1-Reason=$2 |
|
参数解释 |
$1：操作结果 $2：导入失败原因 |
|
举例 |
OperResult="Failed"-Reason="[ExtDownLinkPortCfg [deviceName=55.30, portName=Twenty-FiveGigE1/0/21, optionResult=false, errorMsg=Interface {Twenty-FiveGigE1/0/21} cannot be deleted, because a VLAN-VXLAN mapping entry has been applied to it.], ExtDownLinkPortCfg [deviceName=55.30, portName=Twenty-FiveGigE1/0/20, optionResult=false, errorMsg=Interface {Twenty-FiveGigE1/0/20} cannot be deleted, because a VLAN-VXLAN mapping entry has been applied to it.]]" |
|
日志说明 |
用户进行了导入下行口配置文件的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The template format is invalid：模板格式不符 · Unknown internal server error：未知的内部服务器错误 · You have no privilege to perform this operation：用户无权限执行此操作 · The device type does not support binding interfaces：设备类型不匹配 · Invalid JSON format：无效的JSON格式 · Invalid parameter：无效的参数 · The physical access device does not exist：指定的设备不存在 · Interface %s cannot be configured as a downlink interface, because it is a member of an aggregate interface：接口%s为聚合成员接口，不能添加为下行口 · Interface %s cannot be configured as a downlink interface, because it is not an available Layer 2 physical interface：接口%s不是二层物理接口，不能添加为下行口 · The device is inactive：设备处于未激活状态 · Operation not allowed. It would cause the number of downlink ports on the device to exceed the upper limit (1000)：本次操作后，设备所容纳下行口数超出上限，设备所容纳下行口数为上限1000 · You cannot configure downlink interfaces for the device, because the device has been bound to a global VLAN-VXLAN mapping：设备已绑定全局VLAN-VXLAN映射，不允许配置下行口 |
|
关键字 |
SYNCHORNIZE_DEVICE_TO_NETWORK |
|
日志内容 |
· Synchronized all physical device information to the basic network management module on Unified Platform. · Synchronized physical device information to the basic network management module on Unified Platform. [$1] |
|
参数解释 |
$1：网元设备UUID |
|
举例 |
· Synchronized all physical device information to basic network management module on Unified Platform. · Synchronized physical device information to the basic network management module on Unified Platform. [52b5cbe9-d0f8-4d1f-9642-e8d69b98b697,3a11e3c7-1ae5-46be-ba46-fad6d606ce3b] |
|
日志说明 |
用户进行了基础网管设备信息同步的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Please perform the operation on the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · The basic network management module is not available：基础网管组件不存在 |
|
关键字 |
BATCH_ADD_VLAN_VXLAN_INTERFACE_OP |
|
日志内容 |
Bulk created VLAN-VXLAN mappings: $1. |
|
参数解释 |
$1：批量操作信息 |
|
举例 |
Bulk created VLAN-VXLAN mappings: fileName: [VLAN-VXLAN映射创建模板.xlsx], totalNum: [1], successNum: [0], failedNum: [1]. |
|
日志说明 |
用户进行了批量创建VLAN-VXLAN映射操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · Incorrect file name：文件名错误 · Failed to read the Excel file：Excel文件读取失败 · Failed to parse data：数据解析错误 · A global VLAN-VXLAN mapping supports only the Ethernet type：全局VLAN-VXLAN映射只支持Ethernet类型 · A global VLAN-VXLAN mapping does not support mapping multiple VLANs to one VXLAN：全局VLAN-VXLAN映射不支持多对一映射 · The VLAN pool overlaps with a global VLAN-VXLAN mapping：全局VLAN-VXLAN映射VLAN与VLAN池范围冲突 · The segment ID of a external network conflicts with a VLAN ID of a global VLAN-VXLAN mapping：全局VLAN-VXLAN映射VLAN与外网的Segment ID冲突 · You cannot rewrite rules for a global VLAN-VXLAN mapping：全局VLAN-VXLAN映射不支持写入规则 |
|
关键字 |
BATCH_UPDATE_VLAN_VXLAN_INTERFACE_OP |
|
日志内容 |
Bulk updated VLAN-VXLAN mappings: $1. |
|
参数解释 |
$1：批量操作信息 |
|
举例 |
Bulk updated VLAN-VXLAN mappings: fileName: [VLAN-VXLAN映射更新模板.xlsx], totalNum: [1], successNum: [0], failedNum: [1]. |
|
日志说明 |
用户进行了批量更新VLAN-VXLAN映射操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · Incorrect file name：文件名错误 · Failed to read the Excel file：Excel文件读取失败 · Failed to parse data：数据解析错误 · You cannot edit the apply_scope parameter for a global VLAN-VXLAN mapping：全局VLAN-VXLAN映射apply_scope字段不允许修改 · A global VLAN-VXLAN mapping supports only the Ethernet type：全局VLAN-VXLAN映射只支持Ethernet类型 · A global VLAN-VXLAN mapping does not support mapping multiple VLANs to one VXLAN：全局VLAN-VXLAN映射不支持多对一映射 · The physical access device already binding a global VLAN-VXLAN mapping cannot binding other VLAN-VXLAN binding：设备已经绑定全局VLAN-VXLAN映射，不允许再绑定其他映射 · The global VLAN-VXLAN mapping cannot binding port：全局VLAN-VXLAN映射不允许绑定接口 · The VLAN pool overlaps with a global VLAN-VXLAN mapping：全局VLAN-VXLAN映射VLAN与VLAN池范围冲突 · The segment ID of a external network conflicts with a VLAN ID of a global VLAN-VXLAN mapping：全局VLAN-VXLAN映射VLAN与外网的Segment ID冲突 · You cannot rewrite rules for a global VLAN-VXLAN mapping：全局VLAN-VXLAN映射不支持写入规则 |
|
关键字 |
BATCH_DELETE_VLAN_VXLAN_INTERFACE_OP |
|
日志内容 |
Bulk deleted VLAN-VXLAN mappings: $1. |
|
参数解释 |
$1：批量操作信息 |
|
举例 |
Bulk deleted VLAN-VXLAN mappings: fileName: [VLAN-VXLAN映射删除模板.xlsx], totalNum: [1], successNum: [0], failedNum: [1]. |
|
日志说明 |
用户进行了批量删除VLAN-VXLAN映射操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · Incorrect file name：文件名错误 · Failed to read the Excel file：Excel文件读取失败 · Failed to parse data：数据解析错误 |
|
关键字 |
BATCH_EXPORT_VLAN_VXLAN_INTERFACE_OP |
|
日志内容 |
Bulk exported VLAN-VXLAN mappings: $1. |
|
参数解释 |
$1：批量操作信息 |
|
举例 |
Bulk exported VLAN-VXLAN mappings: VLAN-VXLAN映射-2021-06-04 09-27-59.xlsx. |
|
日志说明 |
用户进行了批量导出VLAN-VXLAN映射操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · Failed to export the file：Excel文件导出失败 |
|
关键字 |
BATCH_IMPORT_QINQ_INTERFACE_OP |
|
日志内容 |
Bulk imported QinQ mappings: $1. |
|
参数解释 |
$1：导入操作信息 |
|
举例 |
Bulk imported QinQ mappings: fileName: [QinQ映射导入模板.xlsx], totalNum: [1], successNum: [0], failedNum: [1]. |
|
日志说明 |
用户进行了导入QinQ映射操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · Incorrect file name：文件名错误 · Failed to read the Excel file：Excel文件读取失败 · Failed to parse data：数据解析错误 · QinQ mapping and VLAN-network mapping do not support global VLAN-VXLAN mappings：QinQ映射和VLAN-Network映射不支持全局VLAN-VXLAN映射 |
|
关键字 |
BATCH_EXPORT_QINQ_INTERFACE_OP |
|
日志内容 |
Bulk exported QinQ mappings: $1. |
|
参数解释 |
$1：导出操作信息 |
|
举例 |
Bulk exported QinQ mappings: QinQ映射-2021-06-04 09-27-59.xlsx. |
|
日志说明 |
用户进行了导出QinQ映射操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · Failed to export the file：Excel文件导出失败 |
|
关键字 |
BATCH_IMPORT_ VLAN_VXLAN _INTERFACE_OP |
|
日志内容 |
Bulk imported VLAN-VXLAN mappings: $1. |
|
参数解释 |
$1：导入操作信息 |
|
举例 |
Bulk imported VLAN-VXLAN mappings: fileName: [VLAN-VXLAN映射导入模板.xlsx], totalNum: [1], successNum: [0], failedNum: [1]. |
|
日志说明 |
用户进行了导入VLAN-VXLAN映射操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · Incorrect file name：文件名错误 · Failed to read the Excel file：Excel文件读取失败 · Failed to parse data：数据解析错误 |
|
关键字 |
BATCH_EXPORT_VLAN_VXLAN_INTERFACE_OP |
|
日志内容 |
Bulk exported VLAN-VXLAN mappings: $1. |
|
参数解释 |
$1：导出操作信息 |
|
举例 |
Bulk exported VLAN-VXLAN mappings: VLAN-VXLAN映射-2021-06-04 09-27-59.xlsx. |
|
日志说明 |
用户进行了导出VLAN-VXLAN映射操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · Failed to export the file：Excel文件导出失败 |
|
关键字 |
BATCH_ADD_VLAN_NETWORK_MAPPINGS_PORTS_INTERFACE_OP |
|
日志内容 |
Bulk created VLAN-network mappings Ports: $1. |
|
参数解释 |
$1：批量操作信息 |
|
举例 |
Bulk created VLAN-network mappings Ports: fileName:[ VLAN-Network映射端口创建模板], totalNum:[1], successNum:[0], failedNum:[1]. |
|
日志说明 |
用户进行了批量创建VLAN-Network映射端口操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · Incorrect file name：文件名错误 · Failed to read the file：Excel文件读取失败 · Failed to parse data：数据解析错误 · The physical access device already binding a global VLAN-VXLAN mapping cannot binding other VLAN-VXLAN binding：设备已经绑定全局VLAN-VXLAN映射，不允许再绑定其他映射 |
|
关键字 |
BATCH_DELETE_VLAN_NETWORK_MAPPINGS_PORTS_INTERFACE_OP |
|
日志内容 |
Bulk deleted VLAN-network mappings Ports: $1. |
|
参数解释 |
$1：批量操作信息 |
|
举例 |
Bulk deleted VLAN-network mappings Ports: fileName:[ VLAN-Network映射端口删除模板.xlsx], totalNum:[1], successNum:[0], failedNum:[1]. |
|
日志说明 |
用户进行了批量删除VLAN-Network映射端口操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · Incorrect file name：文件名错误 · Failed to read the file：Excel文件读取失败 · Failed to parse data：数据解析错误 |
|
关键字 |
BATCH_EXPORT_VLAN_NETWORK_MAPPINGS_PORTS_INTERFACE_OP |
|
日志内容 |
Bulk exported VLAN-network mappings Ports: $1. |
|
参数解释 |
$1：批量操作信息 |
|
举例 |
Bulk exported VLAN-network mappings Ports: VLAN-Network映射端口-2021-06-04 09-27-59.xlsx |
|
日志说明 |
用户进行了批量导出VLAN-Network映射端口操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · Failed to export the file：Excel文件导出失败 |
|
关键字 |
BATCH_ADD_VLAN_VXLAN_MAPPINGS_PORTS_INTERFACE_OP |
|
日志内容 |
Bulk created VLAN-VXLAN mappings Ports: $1. |
|
参数解释 |
$1：批量操作信息 |
|
举例 |
Bulk created VLAN-VXLAN mappings Ports: fileName:[ VLAN-VXLAN映射端口创建模板], totalNum:[1], successNum:[0], failedNum:[1]. |
|
日志说明 |
用户进行了批量创建VLAN-VXLAN映射端口操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · Incorrect file name：文件名错误 · Failed to read the file：Excel文件读取失败 · Failed to parse data：数据解析错误 · The physical access device already binding a global VLAN-VXLAN mapping cannot binding other VLAN-VXLAN binding：设备已经绑定全局VLAN-VXLAN映射，不允许再绑定其他映射 · The global VLAN-VXLAN mapping cannot binding port：全局VLAN-VXLAN映射不允许绑定接口 |
|
关键字 |
BATCH_DELETE_VLAN_VXLAN_MAPPINGS_PORTS_INTERFACE_OP |
|
日志内容 |
Bulk deleted VLAN-VXLAN mappings Ports: $1. |
|
参数解释 |
$1：批量操作信息 |
|
举例 |
Bulk deleted VLAN-VXLAN mappings Ports: fileName:[ VLAN-VXLAN映射端口删除模板.xlsx], totalNum:[1], successNum:[0], failedNum:[1]. |
|
日志说明 |
用户进行了批量删除VLAN-VXLAN映射端口操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · Incorrect file name：文件名错误 · Failed to read the file：Excel文件读取失败 · Failed to parse data：数据解析错误 |
|
关键字 |
BATCH_EXPORT_VLAN_VXLAN_MAPPINGS_PORTS_INTERFACE_OP |
|
日志内容 |
Bulk exported VLAN-VXLAN mappings Ports: $1. |
|
参数解释 |
$1：批量操作信息 |
|
举例 |
Bulk exported VLAN-VXLAN mappings Ports: VLAN-VXLAN映射端口-2021-06-04 09-27-59.xlsx |
|
日志说明 |
用户进行了批量导出VLAN-VXLAN映射端口操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · Failed to export the file：Excel文件导出失败 |
|
关键字 |
BATCH_ADD_PVLAN_MAPPINGS_PORTS_INTERFACE_OP |
|
日志内容 |
Bulk created PVLAN mappings Ports: $1. |
|
参数解释 |
$1：批量操作信息 |
|
举例 |
Bulk created PVLAN mappings Ports: fileName:[PVLAN映射端口创建模板], totalNum:[1], successNum:[0], failedNum:[1]. |
|
日志说明 |
用户进行了批量创建PVLAN映射端口操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · Incorrect file name：文件名错误 · Failed to read the file：Excel文件读取失败 · Failed to parse data：数据解析错误 · The physical access device already binding a global VLAN-VXLAN mapping cannot binding other VLAN-VXLAN binding：设备已经绑定全局VLAN-VXLAN映射，不允许再绑定其他映射 |
|
关键字 |
BATCH_DELETE_PVLAN_MAPPINGS_PORTS_INTERFACE_OP |
|
日志内容 |
Bulk deleted PVLAN mappings Ports: $1. |
|
参数解释 |
$1：批量操作信息 |
|
举例 |
Bulk deleted PVLAN mappings Ports: fileName:[ PVLAN映射端口删除模板.xlsx], totalNum:[1], successNum:[0], failedNum:[1]. |
|
日志说明 |
用户进行了批量删除PVLAN映射端口操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · Incorrect file name：文件名错误 · Failed to read the file：Excel文件读取失败 · Failed to parse data：数据解析错误 |
|
关键字 |
BATCH_EXPORT_PVLAN_MAPPINGS_PORTS_INTERFACE_OP |
|
日志内容 |
Bulk exported PVLAN mappings Ports: $1. |
|
参数解释 |
$1：批量操作信息 |
|
举例 |
Bulk exported PVLAN mappings Ports: PVLAN映射端口-2021-06-04 09-27-59.xlsx |
|
日志说明 |
用户进行了批量导出PVLAN映射端口操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · Failed to export the file：Excel文件导出失败 |
|
关键字 |
CREATE_PERMIT_VLAN_OP |
|
日志内容 |
Created permit VLAN : $1 |
|
参数解释 |
$1：接口Permit VLAN信息 |
|
举例 |
Created permit VLAN : [ Permit VLAN { id = 39811f54-30fc-4519-8eed-ffbc52afb96b, deviceId = 8bb477e6-675f-43ae-8d37-53b0f64d749a, deviceName = 'device1', linkType = trunk, portName = 'Bridge-Aggregation1', vlans = '1-4094' }, Permit VLAN { id = 39811f54-30fc-4519-8eed-ffbc52afb9ad, deviceId = 8bb477e6-675f-43ae-8d37-53b0f64d749a, deviceName = 'device1', linkType = trunk, portName = 'Bridge-Aggregation2', vlans = '1-4094' } ] |
|
日志说明 |
用户进行了批量创建接口Permit VLAN的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · The service is disabled：服务未启动 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · The interface-permitted VLAN configuration is supported only on trunk interfaces：接口Permit VLAN目前仅支持Trunk类型 · Invalid permit VLANs：无效的Permit VLAN值 · Duplicate interface-permitted VLAN configuration：接口Permit VLAN ID重复 · The specified interface is already configured with a permit VLAN：指定的接口已配置接口Permit VLAN · The interface-permitted VLAN configuration is mutually exclusive with the LAG interface member configuration on an interface：指定的接口Permit VLAN与聚合接口成员冲突 · The interface-permitted VLAN configuration conflicts with the LAG interface configuration：指定的接口Permit VLAN与聚合接口配置有冲突 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
CREATE_PERMIT_VLAN_OP |
|
日志内容 |
Created permit VLAN : $1 |
|
参数解释 |
$1：接口Permit VLAN信息 |
|
举例 |
Created permit VLAN : [ Permit VLAN { id = 39811f54-30fc-4519-8eed-ffbc52afb96b, deviceId = 8bb477e6-675f-43ae-8d37-53b0f64d749a, deviceName = 'device1', linkType = trunk, portName = 'Bridge-Aggregation1', vlans = '1-4094' }, Permit VLAN { id = 39811f54-30fc-4519-8eed-ffbc52afb9ad, deviceId = 8bb477e6-675f-43ae-8d37-53b0f64d749a, deviceName = 'device1', linkType = trunk, portName = 'Bridge-Aggregation2', vlans = '1-4094' } ] |
|
日志说明 |
用户进行了批量创建或者批量修改接口Permit VLAN的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · The service is disabled：服务未启动 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · The interface-permitted VLAN configuration is supported only on trunk interfaces：接口Permit VLAN目前仅支持Trunk类型 · Invalid permit VLANs：无效的Permit VLAN值 · Duplicate interface-permitted VLAN configuration：接口Permit VLAN ID重复 · The specified interface is already configured with a permit VLAN：指定的接口已配置接口Permit VLAN · The interface-permitted VLAN configuration is mutually exclusive with the LAG interface member configuration on an interface：指定的接口Permit VLAN与聚合接口成员冲突 · The interface-permitted VLAN configuration conflicts with the LAG interface configuration：指定的接口Permit VLAN与聚合接口配置有冲突 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
Update_PERMIT_VLAN_OP |
|
日志内容 |
Update permit VLAN : $1 |
|
参数解释 |
$1：接口Permit VLAN信息 |
|
举例 |
Update permit VLAN : [ Permit VLAN{ id = 39811f54-30fc-4519-8eed-ffbc52afb96b, deviceId = 8bb477e6-675f-43ae-8d37-53b0f64d749a, deviceName = 'device1', linkType = trunk, portName = 'Bridge-Aggregation1', vlans = '1-4094' }, Permit VLAN { id = 39811f54-30fc-4519-8eed-ffbc52afb9ad, deviceId = 8bb477e6-675f-43ae-8d37-53b0f64d749a, deviceName = 'device1', linkType = trunk, portName = 'Bridge-Aggregation2', vlans = '1-4094' } ] |
|
日志说明 |
用户进行了修改单个接口Permit VLAN的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · The service is disabled：服务未启动 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · The interface-permitted VLAN configuration is supported only on trunk interfaces：接口Permit VLAN目前仅支持Trunk类型 · Invalid permit VLANs：无效的Permit VLAN值 · Duplicate interface-permitted VLAN configuration：接口Permit VLAN ID重复 · The specified interface is already configured with a permit VLAN：指定的接口已配置接口Permit VLAN · The interface-permitted VLAN configuration is mutually exclusive with the LAG interface member configuration on an interface：指定的接口Permit VLAN与聚合接口成员冲突 · The interface-permitted VLAN configuration conflicts with the LAG interface configuration：指定的接口Permit VLAN与聚合接口配置有冲突 · The Permit VLAN of the specified interface does not exist：指定接口的Permit VLAN不存在 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
DELETE_PERMIT_VLAN_OP |
|
日志内容 |
Deleted permit VLAN : $1 |
|
参数解释 |
$1：删除指定ID的Permit VLAN |
|
举例 |
Deleted permit VLAN : ID:[39811f54-30fc-4519-8eed-ffbc52afb96b] |
|
日志说明 |
用户进行了删除指定ID的Permit VLAN操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · The service is disabled：服务未启动 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · The Permit VLAN of the specified interface does not exist：指定接口的Permit VLAN不存在 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
CREATE_PERMIT_VLAN_OP |
|
日志内容 |
Deleted permit VLAN : $1 |
|
参数解释 |
$1：删除的接口Permit VLAN列表 |
|
举例 |
Deleted permit VLAN : Deleted [GigabitEthernet2/0/1] interface permit VLAN from device [100.100]. Deleted [GigabitEthernet2/0/2] interface permit VLAN from device [100.100]. |
|
日志说明 |
用户进行了批量删除接口Permit VLAN的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · The service is disabled：服务未启动 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Unknown internal server error：未知的内部服务器错误 · The specified interface or device does not have interface-permitted VLAN configuration：指定的网元或者接口不存在接口Permit VLAN · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
CREATE_MLAG_SYSTEM_PLAN_OP |
|
日志内容 |
Created M-LAG system plan: $1 |
|
参数解释 |
$1：M-LAG系统规划 |
|
举例 |
Created M-LAG system plan: id: [08f99f0d-3ac2-4d41-841d-2322476b2d84] serialNumberA: [210235A3JSH199007773] escapeVlanIpA: [44.44.44.30] serialNumberB: [210235A3JSH199007776] escapeVlanIpB: [44.44.44.31] virtualVtepIp: [44.44.44.32] fabric: [27a2984e-d8d1-45d1-919b-fabc81697476] keepaliveType: [direct_link] scene: [has_peer_link] keepalivePortA: [[Ten-GigabitEthernet1/0/1]] keepalivePortB: [[Ten-GigabitEthernet1/0/1]] peerlinkPortA: [[Ten-GigabitEthernet1/0/2]] peerlinkPortB: [[Ten-GigabitEthernet1/0/2]] |
|
日志说明 |
用户进行了增加M-LAG系统规划的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · Invalid JSON format：无效的JSON格式 · You have no privilege to perform this operation：用户无权限执行此操作 · Invalid parameter：无效的参数 · The serial number cannot be empty：设备序列号不能为空 · Invalid serial number：无效的设备序列号 · Please specify different serial numbers for Device A and Device B：A设备序列号和B设备序列号不允许相同 · The devices to form an M-LAG system plan must belong to the same fabric：组成M-LAG系统规划的两台设备必须属于相同Fabric · The SN is in use by another M-LAG system plan：设备序列号已被其他M-LAG系统规划使用 · The fabric specified for the M-LAG member devices must be the fabric specified in the corresponding device information entries：组成M-LAG系统两台设备Fabric必须和设备信息的Fabric一致 · The fabric does not exist：指定的Fabric不存在 · A VLAN-based fabric does not support planning the virtual VTEP IP address：VLAN类型的Fabric不支持规划虚拟VTEP IP · The virtual VTEP IP address cannot be identical to the IP address of a critical VLAN interface：虚拟VTEP IP不能和逃生VLAN IP相同 · The virtual VTEP IP address cannot be identical to another IP address specified in the M-LAG system plan：虚拟VTEP IP不能和M-LAG系统已规划的IP相同 · The IP address of the critical VLAN interface on Device A cannot be identical to another IP address specified in the M-LAG system plan：设备逃生VLAN IP不能和M-LAG系统已规划的IP相同 · The IP address of the critical VLAN interface on Device B cannot be identical to another IP address specified in the M-LAG system plan：B设备逃生VLAN IP不能和M-LAG系统已规划的IP相同 · The virtual VTEP IP address cannot be identical to the VTEP IP address of a switching device：虚拟VTEP IP不能和交换设备的VTEP IP相同 · The IP address of the critical VLAN interface on Device A cannot be identical to the VTEP IP address of a switching device：A设备逃生VLAN IP不能和交换设备的VTEP IP相同 · The IP address of the critical VLAN interface on Device B cannot be identical to the VTEP IP address of a switching device：B设备逃生VLAN IP不能和交换设备的VTEP IP相同 · The virtual VTEP IP address cannot be identical to a VTEP IP address in the device information list：虚拟VTEP IP不能和设备信息的VTEP IP相同 · The IP address of the critical VLAN interface on Device A cannot be identical to a VTEP IP address in the device information list：A设备逃生VLAN IP不能和设备信息的VTEP IP相同 · The IP address of the critical VLAN interface on Device B cannot be identical to a VTEP IP address in the device information list：B设备逃生VLAN IP不能和设备信息的VTEP IP相同 · The virtual VTEP IP address cannot be identical to the virtual VTEP IP address of another M-LAG system：虚拟VTEP IP不能和已存在的M-LAG系统虚拟VTEP IP相同 · The virtual VTEP IP address cannot be identical to the IP address of a critical VLAN interface on another M-LAG system：虚拟VTEP IP不能和已存在的M-LAG系统逃生VLAN IP相同 · The virtual VTEP IP address cannot be identical to an IP address used for keepalive detection on another M-LAG system：虚拟VTEP IP不能和已存在的M-LAG系统Keepalive IP相同 · The IP address of the critical VLAN interface on Device A cannot be identical to the virtual VTEP IP address of another M-LAG system：A设备逃生VLAN IP不能和已存在的M-LAG系统虚拟VTEP IP相同 · The IP address of the critical VLAN interface on Device A cannot be identical to the IP address of a critical VLAN interface on another M-LAG system：A设备逃生VLAN IP不能和已存在的M-LAG系统逃生VLAN IP相同 · The IP address of the critical VLAN interface on Device A cannot be identical to an IP address used for keepalive detection on another M-LAG system：A设备逃生VLAN IP不能和已存在的M-LAG系统Keepalive IP相同 · The IP address of the critical VLAN interface on Device B cannot be identical to the virtual VTEP IP address of another M-LAG system：B设备逃生VLAN IP不能和已存在的M-LAG系统虚拟VTEP IP相同 · The IP address of the critical VLAN interface on Device B cannot be identical to the IP address of a critical VLAN interface on another M-LAG system：B设备逃生VLAN IP不能和已存在的M-LAG系统逃生VLAN IP相同 · The IP address of the critical VLAN interface on Device B cannot be identical to an IP address used for keepalive detection on another M-LAG system：B设备逃生VLAN IP不能和已存在的M-LAG系统Keepalive IP相同 · The virtual VTEP IP address has been assigned by the VTEP IP pool：指定的虚拟VTEP IP已被VTEP IP地址池分配 · The IP address of the critical VLAN interface on Device A has been assigned by the VTEP IP pool：指定的A设备逃生VLAN IP已被VTEP IP地址池分配 · The IP address of the critical VLAN interface on Device B has been assigned by the VTEP IP pool：指定的B设备逃生VLAN IP已被VTEP IP地址池分配 · The IP addresses specified in the M-LAG system plan must be unique：M-LAG系统规划的IP相互之间不能相同 · The virtual VTEP IP address configured for the M-LAG system is not the one specified in the plan：M-LAG系统指定的虚拟VTEP IP和规划的虚拟VTEP IP不一致 · The IP address configured for the critical VLAN interface is not the one specified in the plan：M-LAG系统指定的逃生VLAN IP和规划的逃生VLAN IP不一致 · The VTEP IP address cannot be identical to another IP address specified in the M-LAG system plan：指定的VTEP IP不能M-LAG系统已规划的IP相同 · The virtual VTEP IP address cannot be identical to the VTEP IP address of a device group：虚拟VTEP IP不能和设备组的VTEP IP相同 · The IP address of the critical VLAN interface on Device A cannot be identical to the VTEP IP address of a device group：A设备逃生VLAN IP不能和设备组的VTEP IP相同 · The IP address of the critical VLAN interface on Device B cannot be identical to the VTEP IP address of a device group：B设备逃生VLAN IP不能和设备组的VTEP IP相同 · The serial number has been configured on another M-LAG group plan：设备序列号已被其他M-LAG组规划使用 · The keepalive interface fields are not supported if you select the tunnel peer link scene.：当场景为隧道peer-link时，M-LAG系统不支持指定Keepalive接口 · The peer-link interface fields are not supported if you select the tunnel peer link scene：当场景为隧道peer-link时，M-LAG系统不支持指定peer-link接口 · The keepalive interface fields are not supported if you select the management keepalive link type：Keepalive链路取值为管理网链路时，M-LAG系统不支持指定Keepalive接口 · The keepalive interfaces configured in the MLAG system plan are inconsistent with those configured in the MLAG group plan：M-LAG系统规划的Keepalive接口和M-LAG组规划的设备接口冲突 · The peer-link interfaces configured in the MLAG system plan are inconsistent with those configured in the MLAG group plan：M-LAG系统规划的peer-link接口和M-LAG组规划的设备接口冲突 · The peer-link interfaces configured in the MLAG system plan are inconsistent with the downlink interfaces configured in the device list plan：M-LAG系统规划的peer-link接口和设备清单规划的下行口冲突 · The keepalive interfaces configured in the MLAG system plan are inconsistent with the downlink interfaces configured in the device list plan：M-LAG系统规划的Keepalive接口和设备清单规划的下行口冲突 · Invalid scenario：无效的场景 · Invalid keepalive link type：Keepalive链路取值无效 · The keepalive interfaces configured in the MLAG system plan are inconsistent with peer-link interfaces：M-LAG系统规划的Keepalive接口和peer-link接口冲突 |
|
关键字 |
UPDATE_MLAG_SYSTEM_PLAN_OP |
|
日志内容 |
Updated M-LAG system plan: $1 |
|
参数解释 |
$1：M-LAG系统规划 |
|
举例 |
Updated M-LAG system plan: id: [08f99f0d-3ac2-4d41-841d-2322476b2d84] serialNumberA: [210235A3JSH199007773] escapeVlanIpA: [44.44.44.30] serialNumberB: [210235A3JSH199007776] escapeVlanIpB: [44.44.44.31] virtualVtepIp: [44.44.44.32] fabric: [27a2984e-d8d1-45d1-919b-fabc81697476] keepaliveType: [direct_link] scene: [has_peer_link] keepalivePortA: [[Ten-GigabitEthernet1/0/1]] keepalivePortB: [[Ten-GigabitEthernet1/0/1]] peerlinkPortA: [[Ten-GigabitEthernet1/0/2]] peerlinkPortB: [[Ten-GigabitEthernet1/0/2]] |
|
日志说明 |
用户进行了更新M-LAG系统规划的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · Invalid JSON format：无效的JSON格式 · Invalid parameter：无效的参数 · You have no privilege to perform this operation：用户无权限执行此操作 · The serial number cannot be empty：设备序列号不能为空 · Invalid serial number：无效的设备序列号 · Please specify different serial numbers for Device A and Device B：A设备序列号和B设备序列号不允许相同 · The devices to form an M-LAG system plan must belong to the same fabric：组成M-LAG系统规划的两台设备必须属于相同Fabric · The SN is in use by another M-LAG system plan：设备序列号已被其他M-LAG系统规划使用 · The fabric specified for the M-LAG member devices must be the fabric specified in the corresponding device information entries：组成M-LAG系统两台设备Fabric必须和设备信息的Fabric一致 · The fabric does not exist：指定的Fabric不存在 · A VLAN-based fabric does not support planning the virtual VTEP IP address：VLAN类型的Fabric不支持规划虚拟VTEP IP · The virtual VTEP IP address cannot be identical to the IP address of a critical VLAN interface：虚拟VTEP IP不能和逃生VLAN IP相同 · The virtual VTEP IP address cannot be identical to another IP address specified in the M-LAG system plan：虚拟VTEP IP不能和M-LAG系统已规划的IP相同 · The IP address of the critical VLAN interface on Device A cannot be identical to another IP address specified in the M-LAG system plan：设备逃生VLAN IP不能和M-LAG系统已规划的IP相同 · The IP address of the critical VLAN interface on Device B cannot be identical to another IP address specified in the M-LAG system plan：B设备逃生VLAN IP不能和M-LAG系统已规划的IP相同 · The virtual VTEP IP address cannot be identical to the VTEP IP address of a switching device：虚拟VTEP IP不能和交换设备的VTEP IP相同 · The IP address of the critical VLAN interface on Device A cannot be identical to the VTEP IP address of a switching device：A设备逃生VLAN IP不能和交换设备的VTEP IP相同 · The IP address of the critical VLAN interface on Device B cannot be identical to the VTEP IP address of a switching device：B设备逃生VLAN IP不能和交换设备的VTEP IP相同 · The virtual VTEP IP address cannot be identical to a VTEP IP address in the device information list：虚拟VTEP IP不能和设备信息的VTEP IP相同 · The IP address of the critical VLAN interface on Device A cannot be identical to a VTEP IP address in the device information list：A设备逃生VLAN IP不能和设备信息的VTEP IP相同 · The IP address of the critical VLAN interface on Device B cannot be identical to a VTEP IP address in the device information list：B设备逃生VLAN IP不能和设备信息的VTEP IP相同 · The virtual VTEP IP address cannot be identical to the virtual VTEP IP address of another M-LAG system：虚拟VTEP IP不能和已存在的M-LAG系统虚拟VTEP IP相同 · The virtual VTEP IP address cannot be identical to the IP address of a critical VLAN interface on another M-LAG system：虚拟VTEP IP不能和已存在的M-LAG系统逃生VLAN IP相同 · The virtual VTEP IP address cannot be identical to an IP address used for keepalive detection on another M-LAG system：虚拟VTEP IP不能和已存在的M-LAG系统Keepalive IP相同 · The IP address of the critical VLAN interface on Device A cannot be identical to the virtual VTEP IP address of another M-LAG system：A设备逃生VLAN IP不能和已存在的M-LAG系统虚拟VTEP IP相同 · The IP address of the critical VLAN interface on Device A cannot be identical to the IP address of a critical VLAN interface on another M-LAG system：A设备逃生VLAN IP不能和已存在的M-LAG系统逃生VLAN IP相同 · The IP address of the critical VLAN interface on Device A cannot be identical to an IP address used for keepalive detection on another M-LAG system：A设备逃生VLAN IP不能和已存在的M-LAG系统Keepalive IP相同 · The IP address of the critical VLAN interface on Device B cannot be identical to the virtual VTEP IP address of another M-LAG system：B设备逃生VLAN IP不能和已存在的M-LAG系统虚拟VTEP IP相同 · The IP address of the critical VLAN interface on Device B cannot be identical to the IP address of a critical VLAN interface on another M-LAG system：B设备逃生VLAN IP不能和已存在的M-LAG系统逃生VLAN IP相同 · The IP address of the critical VLAN interface on Device B cannot be identical to an IP address used for keepalive detection on another M-LAG system：B设备逃生VLAN IP不能和已存在的M-LAG系统Keepalive IP相同 · The virtual VTEP IP address has been assigned by the VTEP IP pool：指定的虚拟VTEP IP已被VTEP IP地址池分配 · The IP address of the critical VLAN interface on Device A has been assigned by the VTEP IP pool：指定的A设备逃生VLAN IP已被VTEP IP地址池分配 · The IP address of the critical VLAN interface on Device B has been assigned by the VTEP IP pool：指定的B设备逃生VLAN IP已被VTEP IP地址池分配 · The IP addresses specified in the M-LAG system plan must be unique：M-LAG系统规划的IP相互之间不能相同 · The virtual VTEP IP address configured for the M-LAG system is not the one specified in the plan： M-LAG系统指定的虚拟VTEP IP和规划的虚拟VTEP IP不一致 · The IP address configured for the critical VLAN interface is not the one specified in the plan：M-LAG系统指定的逃生VLAN IP和规划的逃生VLAN IP不一致 · The VTEP IP address cannot be identical to another IP address specified in the M-LAG system plan：指定的VTEP IP不能M-LAG系统已规划的IP相同 · The virtual VTEP IP address cannot be identical to the VTEP IP address of a device group：虚拟VTEP IP不能和设备组的VTEP IP相同 · The IP address of the critical VLAN interface on Device A cannot be identical to the VTEP IP address of a device group：A设备逃生VLAN IP不能和设备组的VTEP IP相同 · The IP address of the critical VLAN interface on Device B cannot be identical to the VTEP IP address of a device group：B设备逃生VLAN IP不能和设备组的VTEP IP相同 · The serial number has been configured on another M-LAG group plan：设备序列号已被其他M-LAG组规划使用 · The specified M-LAG system plan does not exist：指定的M-LAG系统规划不存在 · The keepalive interface fields are not supported if you select the tunnel peer link scene.：当场景为隧道peer-link时，M-LAG系统不支持指定Keepalive接口 · The peer-link interface fields are not supported if you select the tunnel peer link scene：当场景为隧道peer-link时，M-LAG系统不支持指定peer-link接口 · The keepalive interface fields are not supported if you select the management keepalive link type：Keepalive链路取值为管理网链路时，M-LAG系统不支持指定Keepalive接口 · The keepalive interfaces configured in the MLAG system plan are inconsistent with those configured in the MLAG group plan：M-LAG系统规划的Keepalive接口和M-LAG组规划的设备接口冲突 · The peer-link interfaces configured in the MLAG system plan are inconsistent with those configured in the MLAG group plan：M-LAG系统规划的peer-link接口和M-LAG组规划的设备接口冲突 · The peer-link interfaces configured in the MLAG system plan are inconsistent with the downlink interfaces configured in the device list plan：M-LAG系统规划的peer-link接口和设备清单规划的下行口冲突 · The keepalive interfaces configured in the MLAG system plan are inconsistent with the downlink interfaces configured in the device list plan：M-LAG系统规划的Keepalive接口和设备清单规划的下行口冲突 · Invalid scenario：无效的场景 · Invalid keepalive link type：Keepalive链路取值无效 · The keepalive interfaces configured in the MLAG system plan are inconsistent with peer-link interfaces：M-LAG系统规划的Keepalive接口和peer-link接口冲突 |
|
关键字 |
DELETE_MLAG_SYSTEM_PLAN_OP |
|
日志内容 |
Deleted M-LAG system plan: $1 |
|
参数解释 |
$1：M-LAG系统规划 |
|
举例 |
Deleted M-LAG system plan: id: [08f99f0d-3ac2-4d41-841d-2322476b2d84] serialNumberA: [210235A3JSH199007773] escapeVlanIpA: [44.44.44.30] serialNumberB: [210235A3JSH199007776] escapeVlanIpB: [44.44.44.31] virtualVtepIp: [44.44.44.32] fabric: [27a2984e-d8d1-45d1-919b-fabc81697476] |
|
日志说明 |
用户进行了删除M-LAG系统规划的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · Invalid JSON format：无效的JSON格式 · Invalid parameter：无效的参数 · You have no privilege to perform this operation：用户无权限执行此操作 · The specified M-LAG system plan does not exist：指定的M-LAG系统规划不存在 |
|
关键字 |
BULK_DELETE_MLAG_SYSTEM_PLAN_OP |
|
日志内容 |
Bulk deleted M-LAG system plans: $1 |
|
参数解释 |
$1：M-LAG系统规划的列表 |
|
举例 |
Bulk deleted M-LAG system plans: [ id: [08f99f0d-3ac2-4d41-841d-2322476b2d84] serialNumberA: [210235A3JSH199007773] escapeVlanIpA: [44.44.44.30] serialNumberB: [210235A3JSH199007776] escapeVlanIpB: [44.44.44.31] virtualVtepIp: [44.44.44.32] fabric: [27a2984e-d8d1-45d1-919b-fabc81697476] , keepaliveType: [direct_link] scene: [has_peer_link] keepalivePortA: [[Ten-GigabitEthernet1/0/1]] keepalivePortB: [[Ten-GigabitEthernet1/0/1]] peerlinkPortA: [[Ten-GigabitEthernet1/0/2]] peerlinkPortB: [[Ten-GigabitEthernet1/0/2]] id: [08f99f0d-3ac2-4d41-841d-2322476b3333] serialNumberA: [210235A3JSH199008883] escapeVlanIpA: [44.44.44.30] serialNumberB: [210235A3JSH199005556] escapeVlanIpB: [44.44.44.31] virtualVtepIp: [44.44.44.32] fabric: [27a2984e-d8d1-45d1-919b-fabc81697476] keepaliveType: [direct_link] scene: [has_peer_link] keepalivePortA: [[Ten-GigabitEthernet1/0/1]] keepalivePortB: [[Ten-GigabitEthernet1/0/1]] peerlinkPortA: [[Ten-GigabitEthernet1/0/2]] peerlinkPortB: [[Ten-GigabitEthernet1/0/2]] ] |
|
日志说明 |
用户进行了批量删除M-LAG系统规划的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · Invalid parameter：无效的参数 · You have no privilege to perform this operation：用户无权限执行此操作 · The specified M-LAG system plan does not exist：指定的M-LAG系统规划不存在 |
|
关键字 |
BATCH_ADD_MLAG_ROUTED_PEERLINK_OP |
|
日志内容 |
Bulk created M-LAG routed peer links: $1. |
|
参数解释 |
$1：批量操作信息 |
|
举例 |
Bulk created M-LAG routed peer links: fileName: [M-LAG互联链路创建模板.xlsx], totalNum: [1], successNum: [0], failedNum: [1]. |
|
日志说明 |
用户进行了批量创建M-LAG互联链路操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · Incorrect file name：文件名错误 · Failed to read the Excel file：Excel文件读取失败 · Failed to parse data：数据解析错误 |
|
关键字 |
BATCH_UPDATE_MLAG_ROUTED_PEERLINK_OP |
|
日志内容 |
Bulk updated M-LAG routed peer links: $1. |
|
参数解释 |
$1：批量操作信息 |
|
举例 |
Bulk updated M-LAG routed peer links: fileName: [M-LAG互联链路更新模板.xlsx], totalNum: [1], successNum: [0], failedNum: [1]. |
|
日志说明 |
用户进行了批量更新M-LAG互联链路操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · Incorrect file name：文件名错误 · Failed to read the Excel file：Excel文件读取失败 · Failed to parse data：数据解析错误 |
|
关键字 |
BATCH_DELETE_MLAG_ROUTED_PEERLINK_OP |
|
日志内容 |
Bulk deleted M-LAG routed peer links: $1. |
|
参数解释 |
$1：批量操作信息 |
|
举例 |
Bulk deleted M-LAG routed peer links: fileName: [M-LAG互联链路删除模板.xlsx], totalNum: [1], successNum: [0], failedNum: [1]. |
|
日志说明 |
用户进行了批量删除M-LAG互联链路操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · Incorrect file name：文件名错误 · Failed to read the Excel file：Excel文件读取失败 · Failed to parse data：数据解析错误 |
|
关键字 |
BATCH_EXPORT_MLAG_ROUTED_PEERLINK_OP |
|
日志内容 |
Bulk exported M-LAG routed peer links: $1. |
|
参数解释 |
$1：批量操作信息 |
|
举例 |
Bulk exported M-LAG routed peer links: M-LAG互联链路-2021-06-04 09-27-59.xlsx. |
|
日志说明 |
用户进行了批量导出M-LAG互联链路操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · Failed to export the file：Excel文件导出失败 |
|
关键字 |
EXPORT_DEVICE_AUDIT_OP |
|
日志内容 |
Exported Device Audit Info: $1. |
|
参数解释 |
$1：导出操作信息 |
|
举例 |
Exported Device Audit Info: DeviceId:[86fb1a5b-1e02-444a-b43c-fcd8d1e16e33] DeviceName:[55.30] Formats:[XML,CLI] . |
|
日志说明 |
用户进行了导出审计差异操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown internal server error：未知的内部服务器错误 · You have no privilege to perform the operation：当前用户无权限执行此操作 · Please perform the operation on the active leader：请在主Leader上进行操作 · Configuration recovery is in progress：配置正在恢复过程中 · The device is inactive.：设备处于未激活状态 · The system is synchronizing data or auditing configuration for the network element：该网元正在进行数据同步或配置审计 · Invalid parameter：无效的配置参数 · The NE does not exist：该物理网元不存在 · The device does not support this operation：该设备暂不支持此操作 · The device does not support converting XML profiles to command lines：此设备不支持将XML格式命令转换成CLI格式 · The audit result for the current device is being exported. You cannot export it again：当前设备的审计结果正在导出中，请勿重复操作 · Failed to obtain the audit data：获取设备审计数据失败 |
|
关键字 |
BULK_DELETE_VLAN_POOL_OP |
|
日志内容 |
Bulk deleted VLAN pools: $1 |
|
参数解释 |
$1：批量删除信息 |
|
举例 |
Bulk deleted VLAN pools: {"gateway_vlan_ranges":[{"id":"390f3b1d-dc22-4aa1-9f04-1583b0b30b34","name":"1"}]} |
|
日志说明 |
用户进行了批量删除VLAN池操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · Invalid JSON format：无效的JSON格式 · The service is disabled：服务未启动 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · The VLAN pool doesn't exist：VLAN池不存在 · The VLAN pool is already used：不允许删除正在使用的VLAN池 · The VLAN pool is already used by device group：VLAN池正在被设备组使用 · vRouter interconnection network VLAN pools cannot be deleted：虚拟路由器互通网络类型的VLAN池不可删除 · Unknown internal server error：未知的内部服务器错误 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
BULK_DELETE_VXLAN_POOL_OP |
|
日志内容 |
Bulk deleted VXLAN pools: $1 |
|
参数解释 |
$1：批量删除信息 |
|
举例 |
Bulk deleted VXLAN pools: {"vxlan_pools":[{"id":"1e203ed0-1628-4509-8a78-0a379f3fbc59","name":"1"}]} |
|
日志说明 |
用户进行了批量删除VXLAN池操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · Invalid JSON format：无效的JSON格式 · The service is disabled：服务未启动 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · The VXLAN pool does not exist：VXLAN池不存在 · VXLAN pools in use cannot be modified or deleted：不允许修改或删除正在使用的VXLAN池 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
BULK_DELETE_VLAN-VXLAN_OP |
|
日志内容 |
Bulk deleted VLAN-VXLAN mapping tables: $1 |
|
参数解释 |
$1：批量删除信息 |
|
举例 |
Bulk deleted VLAN-VXLAN mapping tables: [{"id":"93058f6e-c1b4-4d88-8f82-e4a7089804b8","domainName":"1"}] |
|
日志说明 |
用户进行了批量删除VLAN-VXLAN映射表操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · Invalid JSON format：无效的JSON格式 · The service is disabled：服务未启动 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · The mapping table is already bound to ports：该映射表已绑定接口 · The mapping table is already bound to physical access devices：该映射表已绑定物理接入设备 · The mapping table does not exist：该映射表不存在 · The mapping table is created through the bare metal module and cannot be deleted：该映射表通过裸金属管理模块创建，不允许删除 · The mapping table is created through the resource access template module and cannot be deleted：该映射表通过资源接入模板创建，不允许删除 · Unknown internal server error：未知的内部服务器错误 · You have no privilege to perform this operation：用户无权限执行此操作 · You have selected interfaces on an inactive device (management IP: management IP)：正在绑定的接口所属设备中存在未激活设备(管理IP：管理IP) |
|
关键字 |
BULK_DELETE_QINQ_OP |
|
日志内容 |
Bulk deleted QinQ mapping tables: $1 |
|
参数解释 |
$1：批量删除信息 |
|
举例 |
Bulk deleted QinQ mapping tables: [{"id":"d8cfc331-03a8-437b-a30f-f57d5d220814","domainName":"1"}] |
|
日志说明 |
用户进行了批量删除QinQ映射表操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · Invalid JSON format：无效的JSON格式 · The service is disabled：服务未启动 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · The mapping table is already bound to ports：该映射表已绑定接口 · The mapping table is already bound to physical access devices：该映射表已绑定物理接入设备 · The mapping table does not exist：该映射表不存在 · Unknown internal server error：未知的内部服务器错误 · You have no privilege to perform this operation：用户无权限执行此操作 · You have selected interfaces on an inactive device (management IP: management IP)：正在绑定的接口所属设备中存在未激活设备(管理IP：管理IP) |
|
关键字 |
BULK_DELETE_PVLAN_OP |
|
日志内容 |
Bulk deleted PVLAN mapping tables: $1. |
|
参数解释 |
$1：批量删除信息 |
|
举例 |
Bulk deleted PVLAN mapping tables: [{"id":"5dbf3cb4-dc1f-428d-8810-0e95de69412e","name":"1"}] |
|
日志说明 |
用户进行了批量删除PVLAN映射表操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · Invalid JSON format：无效的JSON格式 · The service is disabled：服务未启动 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · You have no privilege to perform this operation：用户无权限执行此操作 · The specified PVLAN does not exist：指定的PVLAN不存在 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
CREATE_FW_SERVICE_RESOURCE_NQA_BINDING_OP |
|
日志内容 |
Created a binding between an FW service resource and an NQA profile: $1. |
|
参数解释 |
$1：服务资源-NQA绑定关系信息 |
|
举例 |
Created a binding between an FW service resource and an NQA profile: ID: [c962169b-1a71-449c-8407-a36e938916ec] FW service resource ID: [94e28779-629f-4159-a7c6-261a57241658] NQA policy ID: [28ebfffc-865f-4784-a7d5-33938daf8db1] Type: [VPCC] |
|
日志说明 |
用户进行了创建服务资源-NQA绑定关系的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service is disabled：服务未启动 · You have no privilege to perform this operation：用户无权限执行此操作 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · The resource type should be VFW：服务资源类型应该是VFW · Service resources created for service chain scenarios or service leaf scenarios cannot be bound to NQA profiles：服务链类型和Service Leaf服务网关类型的服务资源不支持绑定NQA策略 · Cannot bind the subnet to an NQA profile. The border gateway in the subnet has been bound to a track entry：绑定NQA失败，服务资源绑定的网关成员已配置了Track项 · The specified NQA profile does not exist：指定的NQA策略不存在 · You cannot bind the service resource to an NQA profile when the auto NQA profile mode is used：当NQA策略配置为自动时，服务资源不能绑定NQA策略 · The specified NQA profile has been bound to another service resource of the same type：指定的NQA策略已被其他同类型服务资源绑定 · The NQA profile has been bound to another external network：指定的NQA策略已经被其他外部网络绑定 · Unknown internal server error：未知的内部服务器错误 · Invalid JSON format：无效的JSON格式 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · You can bind vFW service resources from a resource pool to only one NQA profile of a specific binding type：同一个资源池分配的虚拟防火墙服务资源，相同类型的联动NQA，只能配置同一个NQA策略 · You can select only External Network or vRouter Link for the Binding Type field in the NQA profile：联动NQA策略类型仅支持选择为“外网联动NQA策略”和“虚拟路由器连接联动NQA策略” · Please specify a service resource ID：服务资源ID不能为空 · Please specify an NQA profile ID：NQA策略ID不能为空 · The specified service resource does not exist：指定的服务资源不存在 · You can specify only one NQA profile of a specific binding type for the same service resource：同一服务资源绑定的每种NQA策略仅支持配置一个 |
|
关键字 |
DELETE_FW_SERVICE_RESOURCE_NQA_BINDING_OP |
|
日志内容 |
Deleted the binding between an FW service resource and an NQA profile: $1. |
|
参数解释 |
$1：服务资源-NQA绑定关系的ID |
|
举例 |
Deleted the binding between an FW service resource and an NQA profile: c962169b-1a71-449c-8407-a36e938916ec |
|
日志说明 |
用户进行了删除服务资源-NQA绑定关系的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service is disabled：服务未启动 · You have no privilege to perform this operation：用户无权限执行此操作 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · Invalid JSON format：无效的JSON格式 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · The specified data does not exist：指定数据不存在 · Please specify a service resource ID for the specified binding entry：指定数据的服务资源ID为空 |
|
关键字 |
CREATE_LB_SERVICE_RESOURCE_NQA_BINDING_OP |
|
日志内容 |
Created a binding between an LB service resource and an NQA profile: $1. |
|
参数解释 |
$1：LB服务资源-NQA绑定关系信息 |
|
举例 |
Created a binding between an LB service resource and an NQA profile: ID: [c962169b-1a71-449c-8407-a36e938916ec] LB service resource ID: [94e28779-629f-4159-a7c6-261a57241658] NQA policy ID: [28ebfffc-865f-4784-a7d5-33938daf8db1] Type: [EXTERNAL] |
|
日志说明 |
用户进行了创建LB服务资源-NQA绑定关系的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service is disabled：服务未启动 · You have no privilege to perform this operation：用户无权限执行此操作 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · The service resource type must be vLB：服务资源类型应该是vLB · Service resources created for service chain scenarios or service leaf scenarios cannot be bound to NQA profiles：服务链类型和Service Leaf服务网关类型的服务资源不支持绑定NQA策略 · Cannot bind the service resource to an NQA profile. The gateway member in the service resource has been bound to a track entry：绑定NQA失败，服务资源绑定的网关成员已配置了Track项 · The specified NQA profile does not exist：指定的NQA策略不存在 · You cannot bind the service resource to an NQA profile when the auto NQA profile mode is used：当NQA策略配置为自动时，服务资源不能绑定NQA策略 · The specified NQA profile has been bound to another service resource of the same type：指定的NQA策略已被其他同类型服务资源绑定 · The NQA profile has been bound to another external network：指定的NQA策略已经被其他外部网络绑定 · Unknown internal server error：未知的内部服务器错误 · Invalid JSON format：无效的JSON格式 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · For vLB service resources allocated from the same resource pool and specified with same binding type, you can bind them to only one NQA profile：同一个资源池分配的虚拟负载均衡服务资源，相同类型的联动NQA，只能配置同一个NQA策略 · You can specify the NQA profile binding type as only External Network for vLB service resources：VLB服务资源联动NQA策略类型仅支持选择为外网联动NQA策略 · Please specify a vLB service resource ID：vLB服务资源ID不能为空 · Please specify an NQA profile ID：NQA策略ID不能为空 · You can specify only one NQA profile of a specific binding type for the same service resource：同一服务资源绑定的每种NQA策略仅支持配置一个 · The NQA profile has been bound to a service path：该NQA策略已经被服务路径绑定 |
|
关键字 |
DELETE_LB_SERVICE_RESOURCE_NQA_BINDING_OP |
|
日志内容 |
Deleted the binding between an LB service resource and an NQA profile: $1. |
|
参数解释 |
$1：LB服务资源-NQA绑定关系的ID |
|
举例 |
Deleted the binding between an LB service resource and an NQA profile: c962169b-1a71-449c-8407-a36e938916ec |
|
日志说明 |
用户进行了删除服务资源-NQA绑定关系的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service is disabled：服务未启动 · You have no privilege to perform this operation：用户无权限执行此操作 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · Invalid JSON format：无效的JSON格式 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · The specified vLB service resource is not bound to the NQA profile：指定的VLB服务资源与NQA策略的绑定关系不存在 |
|
关键字 |
ACTION_MOD_THRESHOLD |
|
日志内容 |
Update resource alarm thresholds: $1. |
|
参数解释 |
$1：修改的资源阈值信息 |
|
举例 |
Update resource alarm thresholds: [ resourceType:[IP] poolType:[TENANT_SUPPORT_FW] upper:[90] lower:[40]]. |
|
日志说明 |
用户进行了修改资源阈值的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The resource type or address pool type for which the thresholds are set does not exist：资源阈值信息不存在 · Invalid alarm threshold：告警阈值不合法 · Invalid alarm clear threshold：告警恢复阈值不合法 · The alarm clear threshold must be smaller than the alarm threshold：告警恢复阈值必须小于告警阈值 |
|
关键字 |
MIGRATE_LINK_INFO_OP |
|
日志内容 |
Migrate Link: $1. |
|
参数解释 |
$1：迁移的老化链路和正常链路信息 |
|
举例 |
Migrate Link: System Name:[sys-5], Migrate PVID:[true], Unbind Old VLAN Domain:[false], Aging Link:[ Device ID:[77db16f0-c2b9-42fb-bd22-e7b65c0166bf], Port Name:[Bridge-Aggregation20], Link ID:[b4ce6d07-182d-4bf8-9b90-f7dedca726e7], PVID:[30], VLAN Domains:[ Mapping table ID:[36c5738e-295d-4647-8127-b0447a314a62], Mapping table Rules:[ Start VLAN:[120], End VLAN:[120], Start VXLAN:[12], End VXLAN:[12 ] ] ] ], Normal Link:[ Device ID:[512540fe-0082-46ef-bda2-af3fb46ba703], Port Name:[Bridge-Aggregation40], Link ID:[9104942f-38b3-4b0e-bcb7-69ed6ec252d1], PVID:[30], VLAN Domains:[] ] |
|
日志说明 |
用户进行了将老化链路上的配置迁移到正常链路上的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · Invalid JSON format：无效的JSON格式 · The service is disabled：服务未启动 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Unknown internal server error：未知的内部服务器错误 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · Please specify an aging link and a normal link for migration：请指定迁移的老化和正常链路信息 · The aging link and normal link for migration cannot be the same：迁移的老化和正常链路不能相同 · Please specify a system name：System name参数必填 · The aging link or normal link for migration is invalid, or the link information has changed. Please reselect the links：迁移的老化或正常链路信息无效或者链路发生变化，请重新选择链路进行迁移 · The aging link or normal link for migration does not exist. Please reselect the links：迁移的老化或正常链路信息不存在，请重新选择链路进行迁移 · The PVID of the port associated with the aging link has changed. Please reselect a link to be migrated：迁移的老化链路端口PVID发生变化，请重新选择链路进行迁移 · Mapping settings of the port associated with the aging link has changed. Please verify the condition and migrate the link again：迁移的老化链路端口映射配置变化，请确认后重新迁移 · No server link migration event exists：服务器链路迁移事件不存在 · Failed to bind the port of a normal link to VLAN-VXLAN/VLAN-network mappings：正常链路端口绑定VLAN-VXLAN/VLAN-NETWORK映射失败 · Failed to unbind the port of an aging link from VLAN-VXLAN/VLAN-network mappings：解绑老化链路端口VLAN-VXLAN/VLAN-NETWORK映射失败 · Failed to migrate the PVID of the port of an aging link to a port of a normal link：老化链路端口PVID迁移到正常链路端口失败 · A mapping table created through the bare metal module cannot be migrated. Please manually repair this issue：不支持迁移来源于裸金属模块创建的映射表，请自行手工修复 · A mapping table created through a service chain cannot be migrated. Please manually repair this issue：不支持迁移来源于服务链业务创建的映射表，请自行手工修复 |
|
关键字 |
CHECK_MLAG_GROUP_CONSISTENCY_OP |
|
日志内容 |
Checked M-LAG group consistency: $1 |
|
参数解释 |
$1：一致性检查结果 |
|
举例 |
Checked M-LAG group consistency: { "mlag_group_consists": [ { Device A ID: "5ef2c69f-f2f1-4a99-9a58-eeba38909497", Device B interface status: "DOWN", Device B ID: "4657f246-1c66-44be-a92d-266eb0aed902", Device A interface: "Bridge-Aggregation257", Device A interface status: "DOWN", Type2 Consistency Check Result: "fail", MLAG Lagg Group ID : "cb680146-3195-4f28-ae68-7e8b1e2a5766", Device B interface: "Bridge-Aggregation257", Type1 Consistency Check Result: "fail", ID : "537216a9-f978-4d3d-897d-bf66373ceef3", Time : “2023/7/10 20:31:00” } ] } } |
|
日志说明 |
用户进行了检查M-LAG组设备接口一致性操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · You have no privilege to perform this operation：用户无权限执行此操作 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · Failed to check interface configuration consistency for the M-LAG group：检查M-LAG组接口配置一致性失败 · Please specify an M-LAG group ID：M-LAG组ID不能为空 · The M-LAG group does not exist：指定的M-LAG组不存在 · The selected M-LAG groups must belong to the same M-LAG system：批量检查操作的M-LAG组必须属于同一个M-LAG系统 · The devices owning the M-LAG group are not activated：指定的M-LAG组的成员设备处于未激活状态 · The aggregate member interface of the specified M-LAG group must have member interfaces：指定的M-LAG组的成员聚合口必须有成员接口 · The device ID does not exist：设备不存在 |
|
关键字 |
DEPLOY_SSH_DEVICE_COMMON_CONFIG |
|
日志内容 |
Deployed configuration to devices through SSH: $1 |
|
参数解释 |
$1：通过SSH通道下发配置信息 |
|
举例 |
Deployed configuration to device through SSH: { "device_common_config": { "device_ip": "172.20.70.6", "configuration": "sys\n" } } |
|
日志说明 |
用户进行了通过SSH通道给指定设备下发配置操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · You have no privilege to perform this operation：用户无权限执行此操作 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · Please specify a device management IP：设备管理IP不能为空 · Please specify commands：下发的命令不能为空 · Some of the specified devices do not exist：指定的设备不存在 · The specified device is not configured with an SSH username or password：指定的设备未配置SSH用户名或密码 · The device is inactive：设备处于未激活状态 · The response timeout timer must be an integer in the range of 0 to 3600：响应超时时间取值范围为0~3600的整数 |
本节介绍网络搬迁输出的操作日志信息。
|
关键字 |
ACTION_CREATE_NETWORK_RELOCATION _OP |
|
日志内容 |
Created network relocation info:$1 |
|
参数解释 |
$1:搬迁任务请求体 |
|
举例 |
Created network relocation : { "network_relocation": { "id": "59488335-077e-4315-a5e8-bd6d906ab5ca", "name": "搬迁任务001", "traditional_network": { "fabric_id": "33a541c8-dcb4-4d18-8a8c-16d79ff52466" }, "sdn_network": { "fabric_id": "33a541c8-dcb4-4d18-8a8c-16d79ff52467", "tenant_id": "95a541c8-dcb4-4d18-8a8c-16d79ff524c9" }, } } |
|
日志说明 |
用户进行了创建网络搬迁任务操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Internal error：内部错误 · Invalid JSON format：JSON格式错误 · You have no privilege to perform the operation：当前用户无权限执行此操作 · The system service does not respond：内部系统错误 · Invalid parameter：非法参数 · The fabric of the old network cannot be the same as the fabric of the new network.：旧网Fabric和新网Fabric不能相同 · The relocation task already exists：指定的搬迁任务已存在 · Invalid UUID：无效的UUID · The specified tenant does not exist on the controller：控制器不存在指定租户 · The old fabric has been bound to a relocation task, and cannot be bound to a relocation task again：旧网fabric已绑定搬迁任务，无法再重新绑定搬迁任务 · The specified fabric does not exist：指定的Fabric不存在 |
|
关键字 |
ACTION_UPDATE_NETWORK_RELOCATION _OP |
|
日志内容 |
Updated network relocation info: $1. |
|
参数解释 |
$1：搬迁任务ID |
|
举例 |
Updated network relocation info: c505dfc4-c928-4905-a89c-64c8dc34c74f |
|
日志说明 |
用户进行了更新网络搬迁任务操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Internal error：内部错误 · Invalid JSON format：JSON格式错误 · You have no privilege to perform the operation：当前用户无权限执行此操作 · The system service does not respond：系统服务未响应 · Invalid parameter：非法参数 · The analyzer task is already bound：指定的SA任务已被绑定 · The relocation task is not exists：指定的搬迁任务不存在 · The specified analyzer task does not exist：指定的分析任务不存在 · The analyzer is not configured：分析组件未配置 · Invalid UUID：无效的UUID · The relocation task has been bound to an analysis task, and cannot be edited：搬迁任务已绑定分析任务，无法更新分析任务 · The current status of resource does not allow：当前资源状态不允许更新至指定状态 · The specified analyzer task can not be bound：指定的分析任务无法被绑定 · The analyzer does not respond：分析组件未响应 · The analyzer registration state is abnormal：分析组件注册状态异常 · The specified relocation task cannot be updated：指定的搬迁任务不支持更新 · Invalid relocation task state：无效的搬迁任务状态 |
|
关键字 |
ACTION_DELETE_NETWORK_RELOCATION _OP |
|
日志内容 |
Deleted network relocation info: $1. |
|
参数解释 |
$1：网络搬迁任务ID |
|
举例 |
Deleted network relocation info: a8869b93-1e3b-4fdc-9026-88d1dcf237af |
|
日志说明 |
用户进行了删除网络搬迁任务操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Internal error：内部错误 · You have no privilege to perform the operation：当前用户无权限执行此操作 · The system service does not respond：系统服务未响应 · Invalid parameter：非法参数 · The relocation task is not exists：指定的搬迁任务不存在 · The relocation task is not finished：指定的搬迁任务未完成 · Invalid UUID：无效的UUID · The relocation task is relocating resources, and cannot be deleted：搬迁任务正在搬迁中，无法删除 |
|
关键字 |
ACTION_UPDATE_RELOCATION_VRF_OP |
|
日志内容 |
Updated relocation VRFresource:$1. |
|
参数解释 |
$1：更新VRF资源请求体 |
|
举例 |
Updated relocation VRF resource: { "VRFs": [ { "id": "c505dfc4-c928-4905-a89c-64c8dc34c74f", "status": "RELOCATION_SKIP" } ] } |
|
日志说明 |
用户进行了批量更新VRF资源操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Internal error：内部错误 · Invalid JSON format：JSON格式错误 · You have no privilege to perform the operation：当前用户无权限执行此操作 · The system service does not respond：系统服务未响应 · Invalid parameter：非法参数 · The VRF is not exists：指定的VRF不存在 · Invalid UUID：无效的UUID · The current status of resource does not allow：当前资源状态不允许更新至指定状态 · The specified relocation task does not exist：指定搬迁任务不存在 · Failed to update the VRF, because the specified subnet is being relocated：指定的子网正在搬迁中，VRF更新失败 · Invalid VRF state：无效的VRF状态 · The specified VRF cannot be updated：指定的VRF不支持更新 |
|
关键字 |
ACTION_VRF_RELOCATION_OP |
|
日志内容 |
Relocated VRF resource:$1. |
|
参数解释 |
$1:vrf搬迁的请求体 |
|
举例 |
Relocated VRFresource: { "vpn": { "id": "59488335-077e-4315-a5e8-bd6d906ab5ca", "mapping": { "id": "c505dfc4-c928-4905-a89c-64c8dc34c74f", "name": "VPN_test", "vpninstance_name": "test", "segmentation_id": "555" }, "subnets": [ { id: "c505dfc4-c928-4905-a89c-64c8dc34c74f" }, { id: "2af4b7c6-cbeb-4ba9-a178-5c5b5975367e" }, ] } } |
|
日志说明 |
用户进行了VRF搬迁的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Internal error：内部错误 · Invalid JSON format：JSON格式错误 · You have no privilege to perform the operation：当前用户无权限执行此操作 · The system service does not respond：系统服务未响应 · Invalid parameter：非法参数 · The VRF is not in unrelocate status：VRF不处于未搬迁状态，无法配置发放 · The VRF is not exists：指定的VRF不存在 · The specified resource does not exist：指定的资源不存在 · The specified subnet does not exist：指定的虚拟子网不存在 · Invalid UUID：无效的UUID · The VM relocation task failed：VM迁移失败 · A VRF in the current state cannot be relocated：VRF当前状态不支持VRF迁移 · The VRF is not in the relocating state, and you cannot relocate VMs and gateways：VRF不处于搬迁中状态，无法进行VM和网关迁移 · The VRF resource to which the relocation task belongs is being relocated：搬迁任务相关VRF资源正在搬迁中 · VRF configuration deployment failed：VRF配置发放失败 · The VRF has been deployed, and cannot be deployed again：VRF已下发，无法再次下发 · The VRF is already relocating,please wait and try again：当前VRF资源正在 搬迁中，请稍后再试 · The current status of resource does not allow：当前资源状态不允许更新至指定状态 · The specified vRouter does not exist：控制器不存在指定虚拟路由器 · Some subnets do not belong to the specified VRF：子网不属于VRF |
|
关键字 |
ACTION_UPDATE_RELOCATION_SUBNET_OP |
|
日志内容 |
Updated relocation subnet resource:$1. |
|
参数解释 |
$1：更新subnet资源请求体 |
|
举例 |
Updated relocation subnet resource: { "relocation_subnets": [ { "id": "c505dfc4-c928-4905-a89c-64c8dc34c74f", "status": "UNRELOCATE" }, { "id": "2af4b7c6-cbeb-4ba9-a178-5c5b5975367e", "status": "RELOCATION_SKIP" } ] } |
|
日志说明 |
用户进行了批量更新subnet资源操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Internal error：内部错误 · Invalid JSON format：JSON格式错误 · You have no privilege to perform the operation：当前用户无权限执行此操作 · The system service does not respond：系统服务未响应 · Invalid parameter：非法参数 · The specified subnet does not exist：指定的虚拟子网不存在 · Invalid UUID：无效的UUID · The current status of resource does not allow：当前资源状态不允许更新至指定状态 · The specified relocation task does not exist：指定搬迁任务不存在 · The specified subnet cannot be updated：指定的子网不支持更新 · Invalid subnet state：无效的子网状态 |
|
关键字 |
ANALYZER_RESOURCE_CHANGE_OP |
|
日志内容 |
Changed analyzer resource:$1. |
|
参数解释 |
$1：分析器资源变更请求体 |
|
举例 |
Changed analyzer resource: { "sa_request": { "request_url": "/relocationGuarantee/relocation/addRelocationTask", "request_method": "POST", "request_param": "{\"name\": \"搬迁任务\",\"oldNetFabricId\": \"旧网Fabric\", \"newNetFabricId\": \"新网Fabric\",\"origin\": 0}", "response": "{\"id\":\"5b02c64d-b458-4129-af97-f0a59f037ff7\",\"name\":\"搬迁任务\",\"src_fabric_id\":null,\"dst_fabric_id\":null,\"status\":\"collecting\",\"origin\":0}" } } |
|
日志说明 |
用户进行了分析器资源变更操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Internal error：内部错误 · Invalid JSON format：JSON格式错误 · You have no privilege to perform the operation：当前用户无权限执行此操作 · The system service does not respond：系统服务未响应 · Invalid parameter：非法参数 · Invalid UUID：无效的UUID · The analyzer registration state is abnormal：分析组件注册状态异常 · The analyzer is not configured：分析组件未配置 · The analyzer does not respond：分析组件未响应 · The analyzer calling method can only be GET, POST, PUT, or DELETE：分析组件调用METHOD, 取值为:GET、POST、PUT、DELETE |
本节介绍网元YANG Manager模块输出的操作日志信息。
|
关键字 |
DOWNLOAD_YANG_FILES_OP |
|
日志内容 |
Download YANG files: $1 |
|
参数解释 |
$1：网元的ID |
|
举例 |
Download YANG files: NE ID: 84f2ab2c-fd56-48f1-9030-bf1c6297d644 |
|
日志说明 |
用户进行了下载指定网元的YANG文件的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The operation requires the administrator privilege：您需要管理员权限才能执行此操作 · The controller is not the active leader：该控制组件不是主Leader · The controller is obtaining the YANG files：控制组件正在获取网元的YANG文件，请稍后 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
GET_YANG_FILES_FROM_NE_OP |
|
日志内容 |
Get YANG files from NE: $1 |
|
参数解释 |
$1：网元的ID |
|
举例 |
Get YANG files from NE: NE ID: 84f2ab2c-fd56-48f1-9030-bf1c6297d644 |
|
日志说明 |
用户进行了同步指定网元的YANG文件的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The operation requires the administrator privilege：您需要管理员权限才能执行此操作 · The controller is not the active leader：该控制组件不是主Leader · The controller is obtaining the YANG files：控制组件正在获取网元的YANG文件，请稍后 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
SET_YANG_FILES_IDENTIFIER_OP |
|
日志内容 |
Set YANG files identifier: $1 |
|
参数解释 |
$1：网元YANG文件的标识信息 |
|
举例 |
Set YANG files identifier: NE ID: 84f2ab2c-fd56-48f1-9030-bf1c6297d644 Identifier: aaa |
|
日志说明 |
用户进行了配置指定网元的YANG文件标识的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The operation requires the administrator privilege：您需要管理员权限才能执行此操作 · The controller is not the active leader：该控制组件不是主Leader · You have no privilege to perform this operation：用户无权限执行此操作 |
本文介绍NGFW Manager模块输出的操作日志信息。
|
关键字 |
ADD_DEVICE_OP |
|
日志内容 |
Added device: $1 |
|
参数解释 |
$1：设备的配置信息 |
|
举例 |
Added device: ID: 8dfb8b46-50d9-46c1-87c4-7aac7976ef5b Name: device1 IP: 192.168.34.15 Port: 832 Username: admin Vendor: F5 Max. number of NGFW resources: 64 Data synchronization: ON |
|
日志说明 |
用户进行了添加设备的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The device name already exists：设备名称已存在 · Invalid device port：无效的端口 · Invalid username：无效的用户名 · Invalid password：无效的密码 · Invalid device name：无效的设备名称 · The IP address is used by a device： 设备的IP地址冲突 · Invalid IP address：无效的IP地址 · The device is unreachable or the username or password is incorrect：设备IP地址不可达或用户名及密码错误 · The NGFWM service is not started：NGFWM服务未启动 · The F5 service is not started：F5服务未启动 · Failed to add the F5 device：添加F5设备失败 · Invalid vendor：无效的厂商 · Server processing error：服务器处理失败 · Invalid JSON format：无效的JSON串格式 · You have no privilege to perform this operation：用户无权限执行此操作 · The specified IP address of the L4-L7 device is a management IP address. Please select another IP address：指定的L4-L7设备IP与已经存在的管理IP重复 |
|
关键字 |
UPDATE_DEVICE_OP |
|
日志内容 |
Updated device: $1 |
|
参数解释 |
$1：设备的配置信息 |
|
举例 |
Updated device: ID: 8dfb8b46-50d9-46c1-87c4-7aac7976ef5b Name: device1 IP: 192.168.34.15 Port: 832 Username: admin Max. number of NGFW resources: 64 Data synchronization: ON |
|
日志说明 |
用户进行了修改设备的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The max. number of NGFW resources cannot be smaller than the number of NGFW resources existing on the device：最大NGFW资源数不能小于设备上已有NGFW资源数 · The max. number of NGFW resources must be in the range of 1 to 2147483647：最大NGFW资源数的取值范围为1～2147483647 · The resource doesn't exist：指定的资源不存在 · The NGFWM service is not started：NGFWM服务未启动 · Server processing error：服务器处理失败 · Invalid JSON format：无效的JSON串格式 · F5 devices do not support changing NETCONF passwords：F5设备不支持修改NETCONF密码 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_DEVICE_OP |
|
日志内容 |
Deleted device: $1 |
|
参数解释 |
$1：设备的名称 |
|
举例 |
Deleted device: DeviceName |
|
日志说明 |
用户进行了删除设备的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The NGFWM service is not started：NGFWM服务未启动 · Server processing error：服务器处理失败 · The resource doesn't exist：指定的资源不存在 · Delete the NGFW resources on the device first：设备上存在NGFW资源，不允许删除 · Failed to delete the F5 device：删除F5设备失败 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
START_NGFW_DEVICE_DATA_SYNCHRONIZATION_OP |
|
日志内容 |
Started data synchronization on device: $1 |
|
参数解释 |
$1：设备的名称 |
|
举例 |
Started data synchronization on device: m9k |
|
日志说明 |
用户进行了手动触发指定设备进行数据同步的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The NGFWM service is not started：NGFWM服务未启动 · Server processing error：服务器处理失败 · Invalid JSON format：无效的JSON串格式 · F5 devices do not support this function：F5设备不支持本功能 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
START_NGFW_DEVICE_CONFIG_AUDIT_OP |
|
日志内容 |
Started configuration auditing on device: $1 |
|
参数解释 |
$1：设备的名称 |
|
举例 |
Started configuration auditing on device: m9k |
|
日志说明 |
用户进行了手动触发指定设备进行配置审计的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The NGFWM service is not started：NGFWM服务未启动 · Server processing error：服务器处理失败 · Invalid JSON format：无效的JSON串格式 · F5 devices do not support this function：F5设备不支持本功能 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_TEMPLATE_OP |
|
日志内容 |
Created template: $1 |
|
参数解释 |
$1：模板的配置信息 |
|
举例 |
Created template: ID: 8dfb8b46-50d9-46c1-87c4-7aac7976ef5b Name: F1000tmp108 Device name: device1 Security engine group ID: 3 Resource pool name: FW1 Template type: GatewayGroupFW Interface list: [ { Interface name: GigabitEthernet1/0/1 Interface type: Management } { Interface name: GigabitEthernet1/0/2 Interface type: Uplink } { Interface name: GigabitEthernet1/0/3 Interface type: Downlink } ] Extend setting: ip vpn-instance external_vpn ip vpn-instance external_vpn ospf 1 vpn-instance external_vpn import-route direct import-route static area 0.0.0.0 interface GigabitEthernet1/0/2 ip binding vpn-instance external_vpn ospf 1 area 0.0.0.0 ip route-static 0.0.0.0 0 1.2.2.254 interface loopback 2 ip binding vpn-instance external_vpn security-zone name SEC_ZONE_DEFAULT import interface GigabitEthernet1/0/1 Object-policy ip SEC_POLICY_DEFAULT rule 0 pass security-zone intra-zone default permit zone-pair security source Any destination Any object-policy apply ip SEC_POLICY_DEFAULT session synchronization enable nat port-block synchronization enable ipsec redundancy enable |
|
日志说明 |
用户进行了创建模板的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid template name：无效的模板名称 · The template name already exists：模板名称已存在 · Invalid parameter：无效的配置参数 · No available device：无可用的设备 · Invalid security engine group ID：无效的安全引擎组ID · Invalid resource pool name：无效的资源池名称 · The security engine group is not bound to the resource pool：资源池中未绑定指定设备的安全引擎组 · Invalid interface name：无效的接口名称 · The NGFWM service is not started：NGFWM服务未启动 · The IP address pool cannot contain broadcast or network addresses：IP地址池不能包含网络地址和广播地址 · An F5 device supports only gateway group LB resource templates：F5设备上只能创建网关组LB资源类型的模板 · Server processing error：服务器处理失败 · Invalid JSON format：无效的JSON串格式 · The IP address pool of the uplink interface has been used by another template：指定的上行接口IP地址池已被其他模板引用 · You have no privilege to perform this operation：用户无权限执行此操作 · Invalid max concurrent context sessions：无效的Context会话最大并发数 · Invalid session establishment rate：无效的会话新建速率 · Invalid throughput：无效的吞吐量 · Invalid unit of measurement for throughput：无效的吞吐量单位 · Invalid total firewall rules：无效的防火墙规则总数 · Invalid number of SSL VPN users：无效的SSLVPN用户数 · Throughput and its unit of measurement do not match：吞吐量和吞吐量单位不匹配 · Invalid gateway IPv4 or IPv6 address：无效的IPv4或IPv6网关地址 · To configure the gateway IPv4 address, you must first specify the IPv4 address pool and subnet mask：IPv4网关地址依赖于IPv4地址池和子网掩码，无法单独配置 · To configure the gateway IPv6 address, you must first specify the IPv6 address pool and prefix length：IPv6网关地址依赖于IPv6地址池和前缀长度，无法单独配置 · The start IP address, end IP address, and gateway IP address must be on the same segment：起始IP地址、结束IP地址和网关地址必须都属于同一网段 |
|
关键字 |
DELETE_TEMPLATE_OP |
|
日志内容 |
Deleted template: $1 |
|
参数解释 |
$1：模板的名称 |
|
举例 |
Deleted template: TemplateName |
|
日志说明 |
用户进行了删除模板的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The NGFWM service is not started：NGFWM服务未启动 · Server processing error：服务器处理失败 · The resource doesn't exist：指定的资源不存在 · You have no privilege to perform this operation：用户无权限执行此操作 · You cannot delete the template, because it is already used by a resource access template：L4-L7物理资源池模板已被资源接入模板使用，不允许删除 |
|
关键字 |
CREATE_NGFW_RESOURCE_OP |
|
日志内容 |
Created NGFW resource: $1 |
|
参数解释 |
$1：NGFW资源的配置信息 |
|
举例 |
Created NGFW resource: Name: resource1 Device name: device1 Resource pool name: FW Template type: GatewayGroupFW Description: XXXXX CPU weight: 2 Disk: 1000 Memory: 2000 Username: default Interface list: [ { Interface name: GigabitEthernet1/0/1 Interface type: Management IP: 1.2.3.3 Mask: 255.255.0.0 } { Interface name: GigabitEthernet1/0/2 Interface type: Uplink IP: 1.2.30.5 Mask: 255.255.0.0 } ] |
|
日志说明 |
用户进行了创建NGFW资源的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid NGFW resource name：无效的NGFW资源名称 · The NGFW resource name already exists：NGFW资源名称已存在 · The interface name and type of the NGFW resource are required：NGFW资源的接口名称和接口类型不能为空 · The IP address and mask must be both configured：IP地址和子网掩码必须同时指定或不指定 · Invalid parameter：无效的配置参数 · Server processing error：服务器处理失败 · The NGFWM service is not started：NGFWM服务未启动 · Invalid JSON format：无效的JSON串格式 · Failed to deploy the extended configuration and custom configuration to the NGFW resource through SSH：通过SSH向NGFW资源下发扩展配置和自定义配置失败 · Failed to establish the SSH connection between the controller and the device：控制组件与设备建立SSH连接失败 · The number of NGFW resources on all devices in the resource pool has reached the upper limit：指定资源池中所有设备上的NGFW资源数都已达最大值 · The F5 service is not started：F5服务未启动 · Failed to assign resources to the NGFW resource by using NETCONF：通过NETCONF为NGFW分配资源失败 · Failed to get information of the device where the NGFW resource resides：获取NGFW资源所在设备的信息失败 · The CPU weight of the NGFW resource must be in the range of 1 to 10：CPU权重的取值范围为1～10的整数 · The disk of the NGFW resource must be in the range of 1 to 999999999：磁盘的取值范围为1～999999999的整数 · The memory of the NGFW resource must be in the range of 1 to 999999999：内存的取值范围为1～999999999的整数 · The disk size can’t exceed the disk size of the security engine where the NGFW resource resides：指定的磁盘大小超过了该NGFW资源所在安全引擎的磁盘大小 · The memory size can’t exceed the memory size of the security engine where the NGFW resource resides：指定的内存大小超过了该NGFW资源所在安全引擎的内存大小 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_NGFW_RESOURCE_OP |
|
日志内容 |
Updated NGFW resource: $1 |
|
参数解释 |
$1：NGFW资源的配置信息 |
|
举例 |
Updated NGFW resource: Name: resource1 Device name: device1 Resource pool name: FW Template type: GatewayGroupFW Description: XXXXX CPU weight: 2 Disk: 1000 Memory: 2000 Username: default Interface list: [ { Interface name: GigabitEthernet1/0/1 Interface type: Management IP: 1.2.3.3 Mask: 255.255.0.0 } { Interface name: GigabitEthernet1/0/2 Interface type: Uplink IP: 1.2.30.5 Mask: 255.255.0.0 } ] |
|
日志说明 |
用户进行了修改NGFW资源的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The NGFWM service is not started：NGFWM服务未启动 · Server processing error：服务器处理失败 · The resource doesn't exist：指定的资源不存在 · Failed to assign resources to the NGFW resource by using NETCONF：通过NETCONF为NGFW资源分配资源失败 · Failed to get information of the device where the NGFW resource resides：获取NGFW资源所在设备的信息失败 · The CPU weight of the NGFW resource must be in the range of 1 to 10：CPU权重的取值范围为1～10的整数 · The disk of the NGFW resource must be in the range of 1 to 999999999：磁盘的取值范围为1～999999999的整数 · The memory of the NGFW resource must be in the range of 1 to 999999999：内存的取值范围为1～999999999的整数 · The disk size can’t exceed the disk size of the security engine where the NGFW resource resides：指定的磁盘大小超过了该NGFW资源所在安全引擎的磁盘大小 · The memory size can’t exceed the memory size of the security engine where the NGFW resource resides：指定的内存大小超过了该NGFW资源所在安全引擎的内存大小 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_NGFW_RESOURCE_OP |
|
日志内容 |
Deleted NGFW resource: $1 |
|
参数解释 |
$1：NGFW资源的名称 |
|
举例 |
Deleted NGFW resource: aa |
|
日志说明 |
用户进行了删除NGFW资源的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The NGFWM service is not started：NGFWM服务未启动 · Server processing error：服务器处理失败 · The resource doesn't exist：指定的资源不存在 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_RESOURCE_POOL_OP |
|
日志内容 |
Created resource pool: $1 |
|
参数解释 |
$1：资源池的配置信息 |
|
举例 |
Created resource pool: Name: FW1 Type: FW Device list: [ { Device name: M9K Security engine group ID: 1 } ] L4-L7 group list: [ L4-L7 group ID: c706d1cc-7fb3-46db-bb13-f7e4bebb4384 Security engine group ID: null ] |
|
日志说明 |
用户进行了创建资源池的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The NGFWM service is not started：NGFWM服务未启动 · Server processing error：服务器处理失败 · The resource pool name already exists：资源池名称已存在 · The default user of the NGFW resource must be configured：NGFW资源的默认用户不能为空 · Invalid resource pool name：无效的资源池名称 · Invalid device name：无效的设备名称 · The device bound to the resource pool doesn't exist：资源池绑定的设备不存在 · Invalid JSON format：无效的JSON串格式 · You have no privilege to perform this operation：用户无权限执行此操作 · The L4-L7 group bound to the resource pool doesn't exist：资源池绑定的L4L7设备组不存在 · The device is in RBM mode. To add an L4-L7 device in RBM mode, please specify its L4-L7 device group UUID：当设备为RBM模式时，需指定其绑定的L4-L7设备组的UUID · You cannot specify both the device name and device group UUID：设备名称和设备组UUID不能同时存在 · Please specify the device name or the device group UUID：设备名称和设备组UUID不能同时为空 · The L4-L7 device group does not exist：指定的L4-L7设备组不存在 |
|
关键字 |
UPDATE_RESOURCE_POOL_OP |
|
日志内容 |
Updated resource pool: $1 |
|
参数解释 |
$1：资源池的配置信息 |
|
举例 |
Updated resource pool: Name: FW1 Type: FW Device list: [ { Device name: M9K Security engine group ID: 1 } ] L4-L7 group list: [ L4-L7 group ID: c706d1cc-7fb3-46db-bb13-f7e4bebb4384 Security engine group ID: null ] |
|
日志说明 |
用户进行了修改资源池的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The NGFWM service is not started：NGFWM服务未启动 · Server processing error：服务器处理失败 · The resource pool name already exists：资源池名称已存在 · The default user of the NGFW resource must be configured：NGFW资源的默认用户不能为空 · Invalid resource pool name：无效的资源池名称 · Invalid device name：无效的设备名称 · The device bound to the resource pool doesn't exist：资源池绑定的设备不存在 · Invalid JSON format：无效的JSON串格式 · You have no privilege to perform this operation：用户无权限执行此操作 · The L4-L7 group bound to the resource pool doesn't exist：资源池绑定的L4L7设备组不存在 · The device is in RBM mode. To add an L4-L7 device in RBM mode, please specify its L4-L7 device group UUID：当设备为RBM模式时，需指定其绑定的L4-L7设备组的UUID · You cannot specify both the device name and device group UUID：设备名称和设备组UUID不能同时存在 · Please specify the device name or the device group UUID：设备名称和设备组UUID不能同时为空 · The L4-L7 device group does not exist：指定的L4-L7设备组不存在 |
|
关键字 |
DELETE_RESOURCE_POOL_OP |
|
日志内容 |
Deleted resource pool: $1 |
|
参数解释 |
$1：资源池的名称 |
|
举例 |
Deleted resource pool: aa |
|
日志说明 |
用户进行了删除资源池的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The NGFWM service is not started：NGFWM服务未启动 · Server processing error：服务器处理失败 · The resource doesn't exist：指定的资源不存在 · You have no privilege to perform this operation：用户无权限执行此操作 · Cannot delete the resource pool because the resource pool has NGFW resources：不允许删除存在NGFW资源的资源池。 |
|
关键字 |
SET_DEFAULT_USER_OP |
|
日志内容 |
Set default user: $1 |
|
参数解释 |
$1：NGFW资源的默认用户信息 |
|
举例 |
Set default user: Username: admin |
|
日志说明 |
用户进行了设置NGFW资源默认用户的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The NGFWM service is not started：NGFWM服务未启动 · Server processing error：服务器处理失败 · Invalid username：登录NGFW资源的用户名无效 · Invalid password：登录NGFW资源的密码无效 · Invalid JSON format：无效的JSON串格式 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_L4L7GROUP_OP |
|
日志内容 |
Created L4-L7 device group: $1 |
|
参数解释 |
$1：L4-L7设备组信息 |
|
举例 |
Created L4-L7 device group: Name: fff Device list: [ { Device name: fw160 } { Device name: fw44 } ] |
|
日志说明 |
用户进行了创建L4-L7设备组的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · The NGFWM service is not started：NGFWM服务未启动 · Invalid parameter：无效的配置参数 · Invalid JSON format：无效的JSON格式 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Operation failed because the user role doesn't have the permission：用户无权限执行此操作 · Invalid name：无效的L4-L7设备组名称 · Invalid L4-L7 device group UUID：无效的L4-L7设备组UUID · Invalid L4-L7 device group name：无效的L4-L7设备组名称 · The L4-L7 device group name already exists：指定的L4-L7设备组名称已存在 · The configuration item already exists：配置项已存在 · The device is not in RBM mode：指定的设备不是RBM模式 · The device is already bound to an L4-L7 device group：指定的设备已被L4-L7设备组绑定 · An L4-L7 device group can contain one or two L4-L7 devices：L4-L7设备组只能绑定一台或两台L4-L7设备 · The devices in the L4-L7 device group must operate in RBM active/standby mode (one primary device and one secondary device)：指定的设备只支持RBM主备模式 |
|
关键字 |
UPDATE_L4L7GROUP_OP |
|
日志内容 |
Updated L4-L7 device group: $1 |
|
参数解释 |
$1：L4-L7设备组信息 |
|
举例 |
Updated L4-L7 device group: Name: fff Device list: [ { Device name: fw160 } { Device name: fw44 } ] |
|
日志说明 |
用户进行了修改L4-L7设备组的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · The NGFWM service is not started：NGFWM服务未启动 · Invalid parameter：无效的配置参数 · Invalid JSON format：无效的JSON格式 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Operation failed because the user role doesn't have the permission：用户无权限执行此操作 · Invalid L4-L7 device group name：无效的L4-L7设备组名称 · Invalid L4-L7 device group UUID：无效的L4-L7设备组UUID · The device is not in RBM mode：指定的设备不是RBM模式 · The device is already bound to an L4-L7 device group：指定的设备已被L4-L7设备组绑定 · An L4-L7 device group can contain one or two L4-L7 devices：L4-L7设备组只能绑定一台或两台L4-L7设备 · The devices in the L4-L7 device group must operate in RBM active/standby mode (one primary device and one secondary device)：指定的设备只支持RBM主备模式 · The L4-L7 device group does not exist：指定的L4-L7设备组不存在 · Failed to edit the L4-L7 device group：修改L4-L7设备组失败 · Make sure the two L4-L7 devices have the same attributes：指定的L4-L7设备属性不匹配 |
|
关键字 |
DELETE_L4L7GROUP_OP |
|
日志内容 |
Deleted L4-L7 device group: $1 |
|
参数解释 |
$1：L4-L7设备组UUID |
|
举例 |
Deleted L4-L7 device group: 59aed13a-e769-43b7-8e34-05e55cbf5ec6 |
|
日志说明 |
用户进行了删除L4-L7设备组的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · The NGFWM service is not started：NGFWM服务未启动 · Invalid parameter：无效的配置参数 · Invalid JSON format：无效的JSON格式 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Operation failed because the user role doesn't have the permission：用户无权限执行此操作 · The configuration item does not exist：配置项不存在 · The L4-L7 device group is already used in an L4-L7 physical resource pool：L4-L7设备组已被L4-L7物理资源池使用 |
本节介绍OAM模块输出的操作日志信息。
|
关键字 |
CREATE_RADAR_DETECTION_OP |
|
日志内容 |
Created radar detection task: $1 |
|
参数解释 |
$1：雷达探测任务的参数信息 |
|
举例 |
Created radar detection task: Username: sdn Mission Id: 5e9693cc-c9d4-44a2-89d2-c9e7e5734cd2 Task type: multiple Task info: Path type: single Network type: VXLAN Segment ID: 2 Source IP: 70.68.68.68 Source port: 10000 Start device IP: 192.168.70.68 Start device ingress port: 0x1 Destination IP: 168.168.1.2 Destination port: 50000 End device IP: null DSCP: 62 Interval: 0 Packet count: 1 Timeout: 10 Period: 1440 Frequency: 600 |
|
日志说明 |
用户进行了创建指定雷达探测任务的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The start device IP address doesn't exist：起始探测设备IP不存在 · Task already exists. Please try again later：该探测任务正在进行，请稍后重试 · The controller hasn't obtained start device port information：控制组件上未获取到起始探测设备的任何接口信息 · The start device ingress port doesn't exist：起始探测设备入接口不存在 · The destination IP address doesn't exist：目的IP地址不存在 · The gateway device that source device belongs to doesn't exist：源设备所在的物理网关设备不存在 · The controller is not the active leader：该控制组件不是主Leader · Can't find the vPort with the source IP address：源IP地址对应的虚拟端口不存在 · The number of periodic detection tasks has reached the maximum：持续探测任务的数量已达最大值 · Radar detection is disabled：雷达探测功能未开启 · Please enable path detection first：雷达探测功能未开启 · The number of periodic radar detection tasks has reached the upper limit：持续探测任务总数已达上限 · You have no privilege to perform this operation：用户无权限执行此操作 · The source and destination addresses must be of the same IP version：源IP地址和目的IP地址必须为相同IP版本。 · The source IP address does not exist：源IP地址不存在 · The task is running. Please try again later：该探测任务正在进行，请稍后重试 · Wrong source device：起始探测设备错误 · The start device IP address and ingress port are required：请输入起始探测设备IP和入接口 · Packets out of range(1-100)：探测报文发送数量取值范围为1～100的整数 · Vni out of range(1-16777215)：Vni取值范围为1～16777215的整数 · Interval out of range(0-30)：探测报文发送时间间隔取值范围为0～30的整数 · Detection task timeout out of range(10-3600)：探测任务超时时间取值范围为10～3600的整数 · Detection Interval out of range(10-2592000)：探测间隔取值范围为10～2592000的整数 · Detection Duration out of range(1-525600)：探测时长取值范围为1～525600的整数 · The source vPort is not found：源虚拟端口未找到 · The start device does not exist：起始探测设备不存在 · The source vPort is in Inactive state：源虚拟端口处于Inactive状态 · The destination vPort is not found：目的虚拟端口未找到 · The destination vPort is in Inactive state：目的虚拟端口处于Inactive状态 · Please specify a DSCP value for the probe packets：探测报文DSCP值不能为空 · Invalid destination IP address：无效的目的IP地址 · The specified IP address does not match the actual IP address of the vPort：虚拟端口和对应的IP地址不匹配 · Multipath radar detection is not available for hosts：主机设备不支持雷达探测功能 · The source IP address and destination IP address are on different devices：源IP地址和目的IP地址所在的设备不同 · Failed to send the request：发送请求失败 · Coding error：编码错误 · Cannot find the master controller for the device：找不到设备的主处理控制组件 · Cannot find the subnet for the source IP address：源IP对应的子网未找到 · The VLAN and VNI parameters cannot be both specified：VLAN和VNI不能同时输入 · Please specify the source IP address：源IP地址不能为空 · Please specify the destination IP address：目的IP地址不能为空 · Please specify the source port ID：源端口ID不能为空 · Please specify the destination VXLAN ID：目的VXLAN ID不能为空 · Please specify the destination port ID：目的端口ID不能为空 · Please specify the destination VTEP IP address：目的VTEP IP不能为空 · Please specify the source VTEP IP address：源VTEP IP不能为空 · Please specify the source IP address, source VXLAN ID, and the vPort-attached interface on the start device：源IP地址、源VXLAN ID和起始探测设备入接口需同时输入 · Unsupported probe packet type：不支持的探测报文类型 · The port number must be an integer in the range of 0 to 65535：端口的取值范围为0～65535的整数 · The DSCP value must be an integer in the range of 1 to 63：DSCP的取值范围为0～63的整数 · The path type can only be single or multiple：探测类型取值仅支持single或multiple · The direction can only be forward or reverse：探测方向取值仅支持forward和reverse · The device with the specified source VTEP IP address does not exist：源VTEP IP对应的设备不存在 · The device with the specified destination VTEP IP address does not exist：目的VTEP IP对应的设备不存在 · The source IP address cannot be same as the destination IP address：源IP地址和目的IP地址不允许相同 · The start device is in abnormal state：起始探测设备状态异常 · The destination device is in abnormal state：目的探测设备状态异常 · The source IP address cannot be the gateway IP address of a subnet：源IP地址不能为子网网关IP · The destination IP address cannot be the gateway IP address of a subnet：目的IP地址不能为子网网关IP · Invalid IP address：IP地址不合法 · Invalid JSON format：无效的JSON格式 · Please use another means to test the connectivity between the specified VMs. The VMs are in the same vNetwork and attached to the same vPort on the same device or M-LAG system. In a network overlay environment, the traffic between them does not traverse their access switch and cannot be detected by using radar detection：网络Overlay环境，在相同设备或跨设备聚合组中，同虚拟链路层网络同端口上线的虚拟机，流量不上送设备，请自行检查虚拟机流量是否可达 · When the source vPort and the destination vPort are bound to different vRouters, configure a Normal-type vRouter link between the two vRouters. Otherwise, radar detection is not supported：源和目的虚拟端口位于不同的虚拟路由器下，且未配置Normal类型的虚拟路由器连接，不支持探测 |
|
关键字 |
DELETE_RADAR_DETECTION_OP |
|
日志内容 |
Deleted radar detection task: $1 |
|
参数解释 |
$1：雷达探测任务的UUID |
|
举例 |
Deleted radar detection task: 218b5f2f-e435-4365-a1ab-0eaa03b7fa19 |
|
日志说明 |
用户进行了删除指定雷达持续探测任务的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Radar detection is disabled：雷达探测功能未开启 · Please enable path detection first：雷达探测功能未开启 · The periodic scanning task ID doesn’t match the username of the task creator：用户名和持续探测任务的ID不匹配 · You have no privilege to perform this operation：用户无权限执行此操作 · The periodic scanning task does not exist：持续探测任务不存在 |
|
关键字 |
CLEAR_RADAR_DETECTION_OP |
|
日志内容 |
Clear all periodic radar detection tasks for user “$1”. |
|
参数解释 |
$1：用户名 |
|
举例 |
Clear all periodic radar detection tasks for user “sdn”. |
|
日志说明 |
用户进行了清空该用户的所有雷达持续探测任务的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Radar detection is disabled：雷达探测功能未开启 · Please enable path detection first：雷达探测功能未开启 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
OAM_NETWORK_CHECK_CREATE_OP |
|
日志内容 |
Created network check: $1 |
|
参数解释 |
$1：网络检测操作的信息 |
|
举例 |
Created network check: fabricId:[4e4cc938-a884-496f-b0f7-d83a4ce3a040] deviceId:[6b2c4642-31f4-447e-a3eb-f2e496c3c8f7] routingBlackholesAndLoops:[false] multipath:[false] operation:[create] |
|
日志说明 |
用户进行了对指定Fabric下的网络进行网络检测的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The fabric does not exist：指定的Fabric不存在 · Please first enable radar detection：请先开启雷达探测功能 · A network check task is running on the specified fabric：存在正在进行的检测任务 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
OAM_NETWORK_CHECK_CANCEL_OP |
|
日志内容 |
Cancelled network check: $1 |
|
参数解释 |
$1：网络检测操作的信息 |
|
举例 |
Cancelled network check: fabricId:[4e4cc938-a884-496f-b0f7-d83a4ce3a040] deviceId:[6b2c4642-31f4-447e-a3eb-f2e496c3c8f7] routingBlackholesAndLoops:[false] multipath:[false] operation:[create] |
|
日志说明 |
用户进行了对指定Fabric下的网络进行取消网络检测的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The fabric does not exist：指定的Fabric不存在 · Please first enable radar detection：请先开启雷达探测功能 · The task has not started yet：未启动检测任务 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPLOAD_IMAGE_FILE_OP |
|
日志内容 |
Uploaded image file: $1. |
|
参数解释 |
$1：软件版本文件名称 |
|
举例 |
Uploaded image file: 6800.ipe. |
|
日志说明 |
用户执行上传软件版本文件的操作 |
|
失败原因 |
当当操作失败时，可能的原因如下： · Invalid image file：无效的版本文件 · The microservice is initializing：服务正在初始化 · The image file with the specified name already exists：指定名称的版本文件已存在 · Failed to upload the image file：软件版本上传失败 · The system service does not respond：系统服务未响应 |
|
关键字 |
BULK_DELETE_IMAGE_FILE_OP |
|
日志内容 |
Bulk deleted image files: $1 |
|
参数解释 |
$1：版本文件名称 |
|
举例 |
Bulk deleted image files: { "Files deleted": [ "wa2600a.ipe" ], "Files failed to be deleted": [ "hp425.ipe" ] } |
|
日志说明 |
用户进行了批量删除软件版本文件的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The microservice was initializing：服务正在初始化 · The system service did not respond：系统服务未响应 · The image file does not exist：指定的版本文件不存在 · The image file was in use：指定的版本文件正在被使用 · Operation failed：操作失败 |
|
关键字 |
UPDATE_IMAGE_FILE_OP |
|
日志内容 |
Updated image file:$1. |
|
参数解释 |
$1：软件版本信息 |
|
举例 |
Updated image file: { "software_name":"s9850-h3c.ipe", "description":"111", "year_software":"true", }. |
|
日志说明 |
用户执行修改软件版本文件信息的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The microservice is initializing：服务正在初始化 · The system service does not respond：系统服务未响应 · The image file does not exist：指定的版本文件不存在 · The image file is in use：指定的版本文件正在被使用 · Operation failed：操作失败 |
|
关键字 |
GET_DEVICE_DISK_OP |
|
日志内容 |
Retrieved the disk partitions of device: $1 |
|
参数解释 |
$1：设备IP地址 |
|
举例 |
Retrieved the disk partitions of device: 192.168.1.1 |
|
日志说明 |
用户执行了查询设备的磁盘分区操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The microservice is initializing：服务正在初始化 · Failed to connect to the device：连接设备失败 |
|
关键字 |
SYNC_IMAGE_FILE_OP |
|
日志内容 |
Synced image file: $1 |
|
参数解释 |
$1：软件版本文件信息 |
|
举例 |
Synced image file: { "software_name":"s9850-h3c.ipe", }. |
|
日志说明 |
用户执行了同步软件版本文件的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The microservice is initializing：服务正在初始化 · The system service does not respond：系统服务未响应 · The image file does not exist：指定的版本文件不存在 |
|
关键字 |
UPGRADE_IMAGE_FILE_OP |
|
日志内容 |
Upgraded image file:$1 |
|
参数解释 |
$1：软件版本文件信息 |
|
举例 |
Upgraded image file: { “time_out":900, "selected_steps":[ "ISSU_UPGRADE_PRE_CHECK", "DISK_CHECK", "FTP_TRANSFER", "GIR_OUT", "ISSU_UPGRADE_SET_MPU_FILE", "ISSU_UPGRADE_TEST", "SAVE", "ISSU_UPGRADE_INSTALL", "ISSU_UPGRADE_RESET", "GIR_BACK" ], "paused_steps":[ "GIR_OUT", "ISSU_UPGRADE_SET_MPU_FILE", "GIR_BACK" ], "software_name": "vBRAS1000-CMW710-BOOT-E1218P01-X64.bin", "devices": [ { "name": "90.6", "ip": "192.168.1.1", "device_id": "605b26bc-b826-48aa-8476-5c6a3abed199", "device_disk": "" } ] } |
|
日志说明 |
用户执行了为设备升级软件版本的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The microservice is initializing：服务正在初始化 · Failed to connect to the device：连接设备失败 · The image file does not exist：指定的版本文件不存在 · The image file is in use：指定的版本文件正在被使用 · You can upgrade the members in an M-LAG system only one by one：M-LAG系统成员设备不能同时进行升级 · The device at %s is being upgraded：IP地址为%s的设备正在升级 |
|
关键字 |
DELETE_UPGRADE_RECORD_OP |
|
日志内容 |
Deleted device upgrade record: $1. |
|
参数解释 |
$1：设备IP地址 |
|
举例 |
Deleted device upgrade record: 192.168.1.1 |
|
日志说明 |
用户执行删除指定设备升级记录的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The microservice is initializing：服务正在初始化 · The system service does not respond：系统服务未响应 · Device upgrade in progress and the upgrade record cannot be deleted：设备升级中，不允许删除升级记录 |
|
关键字 |
SUSPEND_UPGRADE_OP |
|
日志内容 |
Suspended device upgrade: $1. |
|
参数解释 |
$1：设备信息 |
|
举例 |
Suspended device upgrade: { "devices": [ { "device_id": "c8741379-ebe4-4594-9fe2-e7e5c51bdd4b", "device_ip": "192.168.1.1", "device_name": "lll-2", "software_name": "vBRAS1000-X64-20191116-test12.ipe" } ] } |
|
日志说明 |
用户执行暂停设备升级的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The microservice is initializing：服务正在初始化 |
|
关键字 |
RESTART_UPGRADE_OP |
|
日志内容 |
Restarted device upgrade: $1. |
|
参数解释 |
$1：设备信息 |
|
举例 |
Restarted device upgrade: { "devices": [ { "device_id": "c8741379-ebe4-4594-9fe2-e7e5c51bdd4b", "device_ip": "192.168.1.1", "device_name": "lll-2", "software_name": "vBRAS1000-X64-20191116-test12.ipe" } ] } |
|
日志说明 |
用户执行继续设备升级的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The microservice is initializing：服务正在初始化 |
|
关键字 |
CONFIG_SCHEDULED_UPGRADE_OP |
|
日志内容 |
Configured scheduled upgrade: $1. |
|
参数解释 |
$1：用户配置定时升级信息 |
|
举例 |
Configured scheduled upgrade: { time_out":900, "selected_steps":[ "ISSU_UPGRADE_PRE_CHECK", "DISK_CHECK", "FTP_TRANSFER", "GIR_OUT", "ISSU_UPGRADE_SET_MPU_FILE", "ISSU_UPGRADE_TEST", "SAVE", "ISSU_UPGRADE_INSTALL", "ISSU_UPGRADE_RESET", "GIR_BACK" ], "paused_steps":[ "GIR_OUT", "ISSU_UPGRADE_SET_MPU_FILE", "GIR_BACK" ], "pre_upgrade_time": "2020-01-17 00:00:00", "upgrade_time": "2020-01-18 00:00:00", "devices": [ { “name”: “73.8”, "ip": "192.168.73.8", "device_id": "605b26bc-b826-48aa-8476-5c6a3abed199", “device_disk”: “”, “software_name”: “vBRAS1000-CMW710-BOOT-E1218P01-X64.bin” } ] } |
|
日志说明 |
用户执行配置定时升级操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The microservice is initializing：服务正在初始化 · Failed to connect to the device：连接设备失败 · The image file does not exist：指定的版本文件不存在 · The image file is in use：指定的版本文件正在被使用 · Invalid upgrade time：无效的定时升级时间 · You can upgrade the members in an M-LAG system only one by one：M-LAG系统成员设备不能同时进行升级 · The device at %s is being upgraded：IP地址为%s的设备正在升级 |
|
关键字 |
DELETE_SCHEDULED_UPGRADE_OP |
|
日志内容 |
Deleted scheduled upgrade: $1. |
|
参数解释 |
$1：定时升级时间 |
|
举例 |
Deleted scheduled upgrade: 2020-01-18 00:00:00 |
|
日志说明 |
用户执行删除已配置定时升级信息操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The microservice is initializing：服务正在初始化 · Failed to connect to the device：连接设备失败 |
|
关键字 |
ISSU_UPGRADE_IMAGE_FILE_OP |
|
日志内容 |
Performed an ISSU with upgrade image file $1. |
|
参数解释 |
$1：ISSU升级信息 |
|
举例 |
Performed an ISSU with upgrade image file: { "time_out":900, "selected_steps":[ "ISSU_UPGRADE_PRE_CHECK", "DISK_CHECK", "FTP_TRANSFER", "GIR_OUT", "ISSU_UPGRADE_SET_MPU_FILE", "ISSU_UPGRADE_TEST", "SAVE", "ISSU_UPGRADE_INSTALL", "ISSU_UPGRADE_RESET", "GIR_BACK" ], "paused_steps":[ "GIR_OUT", "ISSU_UPGRADE_SET_MPU_FILE", "GIR_BACK" ], "devices":[ { "name":"leaf-192.168.73.60", "device_id":"5cbf68f4-4f80-4fe2-8a53-1745f72ca627", "time":null, "device_disk":"", "boot":"s6800-cmw710-boot-f2802.bin", "system":"s6800-cmw710-system-f2802.bin", "features":null, "patches":null, "ipe":null } ] } |
|
日志说明 |
用户执行了为设备ISSU升级软件版本的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The microservice is initializing.：服务正在初始化 · Failed to connect to the device.：设备连接失败 · The image file does not exist.：指定的版本文件不存在 · The image file is in use.：指定的版本文件正在被使用 · You can upgrade the members in an M-LAG system only one by one.：DR系统成员设备不能同时进行升级 · The device at %s is being upgraded：IP地址为%s的设备正在升级 |
|
关键字 |
CREATE_REPLACE_TASK_OP |
|
日志内容 |
Created replacement task: $1 |
|
参数解释 |
$1：故障设备任务信息 |
|
举例 |
"Created replacement task": { "deviceId" : "837a4046-5ecc-4a48-9837-bb55eee69148", "deviceSn" : "005056b9321c542d20041013", "replaceDeviceSn" : "005056b962a1d82e20041013" }, Influece tenant Information: { "access"：[{ "tenant"："xxx"，"vrouter"：["vrouter1", "vrouter2"] }], "export"：[{ "tenant"："xxx"，"vrouter"：["vrouter1", "vrouter2"] }], "security"：[{ "tenant"："xxx"，"vrouter"：["vrouter1", "vrouter2"] }], "dci"：[{ "tenant"："xxx"，"vrouter"：["vrouter1", "vrouter2"] }] } |
|
日志说明 |
用户进行了创建设备替换任务的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The TFTP service is disabled：TFTP服务未开启 · Invalid JSON format：无效的JSON格式 · Internal error：内部错误 · The backup configuration file of the faulty device does not exist：故障设备的备份配置文件不存在 · The replacement device does not exist：替换设备不存在 · The serial number of the replacement device is invalid：替换设备的序列号无效 · The replacement device and failed device cannot be the same：替换设备与故障设备不允许相同 · Replacement device with the specified serial number has been specified in another replacement task：指定序列号的替换设备已经被其他故障替换任务使用 · Cannot replace a standalone device with an IRF fabric member device：不允许使用堆叠设备替换单体设备 · The device with the specified serial number does not exist:指定的故障设备序列号不存在 · The device has replaced the original device for 30 minutes but has not onboarded yet. Please check the device settings：设备替换后30分钟内未激活，请检查设备配置 · The replacement device must have the same role as the failed device：故障设备和替换设备的角色必须相同 · The replacement task already exists：替换任务已存在 · The faulty device is being used in another replacement task：该故障设备存在于其他替换任务中 · The replacement device does not exist：替换设备不存在 · Invalid network entity ID：无效的网络实体ID · Please specify the serial number of the replacement device：替换设备序列号不能为空 · Replacement device with the specified serial number has been specified in another replacement task：指定序列号的替换设备已经被其他故障替换任务使用 · Failed to update the DHCP client ID：CID更新失败 · The device is being replaced：设备正在被替换 · Cannot create the replacement task because a configuration backup or restore operation is being performed on the replacement device：新增替换任务时，替换设备已经存在备份或恢复任务 · Failed to obtain information about the IRF fabric：获取堆叠设备信息失败 · The member number of fault device and replace device for stack whole replace is not same：整体堆叠替换成员数不同 |
|
关键字 |
DELETE_REPLACE_TASK_OP |
|
日志内容 |
Deleted replacement task: $1. |
|
参数解释 |
$1：故障设备的UUID |
|
举例 |
Deleted replacement task: 29ced688-57ce-319c-9f72-5cdbfe2edb1c |
|
日志说明 |
用户进行了删除设备替换任务的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · Internal error：内部错误 · The specified replacement task does not exist：指定的替换设备任务不存在 · The replacement task cannot be deleted in the current phase：当前替换任务流程不允许删除 |
|
关键字 |
BACKUP_AND_SYNC_DEV_CFG_OP |
|
日志内容 |
Created configuration file backup task:$1 |
|
参数解释 |
$1：成功和失败创建备份任务的设备ip列表 |
|
举例 |
Created configuration file backup task: { "Operation succeeded on devices" : [ "192.168.116.134", "192.168.116.130" ], "Operation failed on devices" : [] } |
|
日志说明 |
用户进行了创建设备备份任务的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Failed to back up and synchronize the configuration file.：备份同步配置文件失败 · Invalid JSON format：无效的JSON格式 · Internal error：内部错误 |
|
关键字 |
CREATE_RESTORE_TASK_OP |
|
日志内容 |
Restored configuration file on device: $1 |
|
参数解释 |
$1：配置文件名称，设备id |
|
举例 |
Restored configuration file on device: { "fileName" : "192.168.67.203_20200808143922_m.cfg", "deviceId" : "837a4046-5ecc-4a48-9837-bb55eee69148" "isVirtualDevice" : "false" } |
|
日志说明 |
用户进行了恢复设备配置的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · Internal error：内部错误 · Failed to send the configuration file to the device：向设备发送配置文件失败 |
|
关键字 |
UPLOAD_CFG_OP |
|
日志内容 |
Uploaded configuration file: $1 |
|
参数解释 |
$1：配置文件名称、设备ID |
|
举例 |
Uploaded configuration file: { "fileName" : "192.168.67.203_20200808143922_m.cfg", "deviceId" : "f2016ce7-0d15-4721-a765-1a69f49e18ec" } |
|
日志说明 |
用户进行了上传配置文件的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · Internal error：内部错误 |
|
关键字 |
CONFIG_SCHEDULED_BACKUP_OP |
|
日志内容 |
Configured scheduled backup task: $1 |
|
参数解释 |
$1：定时备份任务信息 |
|
举例 |
Configured scheduled backup task: { "autoBackup" : true, "frequency" : "every month", "time" : "10:33", "week" : "", "date" : "" } |
|
日志说明 |
用户进行了定时备份设置 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · Internal error：内部错误 |
|
关键字 |
DELETE_CONFIG_FILE_OP |
|
日志内容 |
Deleted configuration file: $1. |
|
参数解释 |
$1：配置文件名称、设备ID |
|
举例 |
Deleted configuration file: { "configFileName" : "192.168.67.203_20200808143922_m.cfg", "deviceId" : "f2016ce7-0d15-4721-a765-1a69f49e18ec" } |
|
日志说明 |
用户进行了删除配置文件的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · Internal error：内部错误 · The NE device doesn't not exist：设备不存在 |
|
关键字 |
START_DATA_CHECK_OP |
|
日志内容 |
Started data check for module [$1]. |
|
参数解释 |
$1：模块名称 |
|
举例 |
Started data check for module [VSM]. |
|
日志说明 |
用户执行了开始数据检查的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Internal error：内部错误 · Cannot start the data check because the previous data check is not finished：开始数据检查失败，当前已存在数据检查任务 · Invalid parameter：无效的参数 · Failed to start the data check：开始数据检查失败 |
|
关键字 |
STOP_DATA_CHECK_OP |
|
日志内容 |
Stopped data check. |
|
参数解释 |
无 |
|
举例 |
Stopped data check. |
|
日志说明 |
用户执行了停止数据检查的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Internal error：内部错误 · No ongoing data check exists：停止数据检查失败，当前不存在数据检查任务 |
|
关键字 |
MODIFY_INTERFACE_STATUS_BY_INDEX_OP |
|
日志内容 |
Modified interface status by index: $1 |
|
参数解释 |
$1：端口信息 |
|
举例 |
Modified interface status by index: IP: [1.1.1.1] Interface Index: [1, 2, 3] Shutdown: [true] |
|
日志说明 |
用户通过端口号查询到指定端口，并对该端口进行了打开或关闭的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置恢复未完成 · The is_shut_down parameter is required：接口上下线参数不允许为空 · Invalid IP address：IP地址不合法 · Internal server error：内部错误 · Invalid JSON format：无效的JSON格式 · The is_shut_down parameter value must be true or false, which is case insensitive：接口开启关闭参数的取值为true或false，且不区分大小写 · The controller is not the active leader：该控制组件不是主Leader · The port ID is required：端口号不允许为空 · Invalid port ID：无效的端口号 · Unsupported device type：该设备的设备类型不支持 · The specified device doesn't exist：指定的设备不存在 · You have no privilege to perform this operation：用户无权限执行此操作 · Can not be configured with port up-mode command together：已经配置了port up-mode命令，下发失败 |
|
关键字 |
CREATE_REACHABILITY_CHECK_OP |
|
日志内容 |
Created connectivity detection task: $1. |
|
参数解释 |
$1：连通性检测任务的参数信息 |
|
举例 |
Created connectivity detection task: UserName:root [ Source IP:33.33.33.1 Destination IP:33.33.33.21 Ping Packet Count:10 Vxlan ID:23 Start device Dpid:00:00:00:50:56:b9:06:9b Source mac:null Start device ingress port:0x6 Destination mac:null Detection type:IPPING Execution type:One-Time ] |
|
日志说明 |
用户进行了创建指定连通性检测任务的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · When the detection type is MAC ping, the source IP addresses and destination IP addresses cannot be IPv6 addresses：检测类型为MAC Ping时，IP地址不支持IPv6版本 · The total number of periodic tasks has exceeded the upper limit：周期执行任务总数超过上限 · The source vPort is not found：源虚拟端口未找到 · The start device does not exist：起始探测设备不存在 · The source vPort is in Inactive state：源虚拟端口处于Inactive状态 · The destination vPort is not found：目的虚拟端口未找到 · The destination vPort is in Inactive state：目的虚拟端口处于Inactive状态 · The start device ingress port does not exist：起始探测设备入接口不存在 · The specified IP address does not match the actual IP address of the vPort：虚拟端口和对应的IP地址不匹配 · The task is running. Please try again later：该探测任务正在进行，请稍后重试 · Wrong source device：起始探测设备错误 · The source IP address cannot be same as the destination IP address：源IP地址和目的IP地址不允许相同 · The start device is in abnormal state：起始探测设备状态异常 · The destination device is in abnormal state：目的探测设备状态异常 · The source IP address cannot be the gateway IP address of a subnet：源IP地址不能为子网网关IP · The destination IP address cannot be the gateway IP address of a subnet：目的IP地址不能为子网网关IP · Please use another means to test the connectivity between the specified VMs. The VMs are in the same vNetwork and attached to the same vPort on the same device or M-LAG system. In a network overlay environment, the traffic between them does not traverse their access switch and cannot be detected by using radar detection：网络Overlay环境，在相同设备或跨设备聚合组中，同虚拟链路层网络同端口上线的虚拟机，流量不上送设备，请自行检查虚拟机流量是否可达 · In a network overlay scenario, the system cannot detect connectivity for VMs attached to M-LAG interfaces that belong to the same M-LAG group. You must manually detect connectivity for them：网络Overlay组网中，系统不支持对同一M-LAG组下的虚拟机进行连通性检测，用户可以自行检查 |
|
关键字 |
DELETE_REACHABILITY_CHECK_OP |
|
日志内容 |
Deleted connectivity detection task: $1 |
|
参数解释 |
$1：连通性检测任务的UUID |
|
举例 |
Deleted connectivity detection task: edf50b04-7b6d-4e7c-8f51-f53ee22a45e6 |
|
日志说明 |
用户进行了删除指定连通性检测任务的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · You have no privilege to perform this operation：用户无权限执行此操作 · The periodic scanning task does not exist：周期执行任务不存在 |
|
关键字 |
UPDATE_CHECK_PARAM_OP |
|
日志内容 |
Updated check settings: $1 |
|
参数解释 |
$1：巡检参数 |
|
举例 |
Updated check settings: { "timing_check":{ "date":"1", "week":"1", "hour":"0", "status":"close", "frequency":"day", "minute":"0" }, "node_max_num":"1" } |
|
日志说明 |
用户执行了更新巡检配置的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The check task is in progress. Please try again later：巡检任务正在进行中，请稍后重试 · Unknown errors：存在未知错误 |
|
关键字 |
EXECUTE_PORT_REPLACE_OP |
|
日志内容 |
Changed port: $1 |
|
参数解释 |
$1：端口替换信息 |
|
举例 |
Changed port: { "fault_port_name": "GigabitEthernet1/2/2", "displace_port_name": "GigabitEthernet1/2/0", "device_id": "50c6b4d3-c054-43e8-b057-4121f9b31389", "fault_port_type": "AGG_MEMBER" } |
|
日志说明 |
用户执行了端口替换的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Service was initializing：服务正在初始化 · Failed to obtain member ports of the M-LAG interface：查询聚合组成员失败 · Failed to obtain the M-LAG group：查询跨设备聚合组失败 · Failed to change the interface aggregation mode：修改接口聚合模式失败 · Failed to add member ports to the M-LAG interface：增加聚合组成员失败 · Failed to remove member ports from the M-LAG interface：删除聚合组成员失败 · Failed to obtain the device MAC address：获取设备MAC地址失败 · Failed to obtain service link information：查询服务链路信息失败 · Failed to add a service link：增加服务链路信息失败 · Failed to delete a service link：删除服务链路信息失败 · Failed to obtain the VLAN-VXLAN mapping bound to the port：查询VLAN接口绑定关系失败 · Failed to edit the VLAN-VXLAN mapping bound to the port：修改VLAN接口绑定关系失败 · Failed to obtain the interface availability zone of the port：查询接口可用区间失败 · The new port is already in an interface availability zone：替换接口已经在接口可用区中 · Failed to edit the interface availability zone：修改接口可用区失败 · Failed to obtain the M-LAG group：查询聚合组失败 · Failed to obtain telemetry stream entries：查询Telemetry Stream失败 · Failed to edit the telemetry stream entry：更新Telemetry Stream失败 · Failed to obtain INT nodes：查询INT节点信息失败 · Failed to delete the INT node：删除INT节点信息失败 · Failed to add the INT node：新增INT节点信息失败 · Failed to obtain INT infos：查询INT信息失败 · Failed to obtain remote mirroring profiles：查询远程镜像失败 · Failed to edit the remote mirroring profile：更新远程镜像失败 · Failed to obtain physical port policies：查询物理端口策略失败 · Failed to edit the physical port policy：更新物理端口策略失败 · Failed to obtain the PVID of the interface：查询接口PVID失败 · Failed to add the PVID of the interface：增加接口PVID失败 · Failed to delete the PVID of the interface：删除接口PVID失败 |
|
关键字 |
CREATE_RESTORE_POINT_OP |
|
日志内容 |
Created restore point: $1 |
|
参数解释 |
$1：回滚点信息 |
|
举例 |
Created restore point: { “id”:”5cb9db7e-eca5-4b0a-a866-13c65ce3425d”, “serial_number”:”20210310130256001”, "north_lock":true, "description":"1111", "devices":[ "e87701a4-af3b-467b-a571-8b7115a7389e", "eb8323f5-f046-4d53-a081-12fbd4d60a05e" ] } |
|
日志说明 |
用户基于当前控制组件和设备配置创建了一条回滚点配置 |
|
失败原因 |
当操作失败时，可能的原因如下： · A configuration restoration task is in progress. Please try again later：存在正在执行的恢复任务，请稍后再试 · Unknown errors：存在未知错误 |
|
关键字 |
UPDATE_RESTORE_POINT_OP |
|
日志内容 |
Updated restore point: $1 |
|
参数解释 |
$1：回滚点信息 |
|
举例 |
Updated restore point: { “id”:”5cb9db7e-eca5-4b0a-a866-13c65ce3425d”, “serial_number”:”20210310130256001”, "north_lock":true, "description":"1111", "devices":[ "e87701a4-af3b-467b-a571-8b7115a7389e", "eb8323f5-f046-4d53-a081-12fbd4d60a05e" ] } |
|
日志说明 |
用户进行了修改指定回滚点配置的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The restore point does not exist：回滚点不存在 · Unknown errors：存在未知错误 |
|
关键字 |
DELETE_RESTORE_POINT_OP |
|
日志内容 |
Deleted restore point: $1 |
|
参数解释 |
$1：回滚点信息 |
|
举例 |
Deleted restore point: { "id_list":[ "e87701a4-af3b-467b-a571-8b7115a7389e", "eb8323f5-f046-4d53-a081-12fbd4d60a05e" ] } |
|
日志说明 |
用户进行了删除多条回滚点配置的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown errors：存在未知错误 · Restore point is in use：回滚点正在被使用 · The restore point does not exist：回滚点不存在 |
|
关键字 |
RESTORE_CONTROLLER_AND_DEVICES_OP |
|
日志内容 |
Created rollback record: $1 |
|
参数解释 |
$1：还原记录信息 |
|
举例 |
Created rollback record: { "id":"8eed6dfd-eb33-4e96-9760-e66636e6739f", “point_id”:” 5cb9db7e-eca5-4b0a-a866-13c65ce3425d”, "north_lock":"true", "devices":[
"e87701a4-af3b-467b-a571-8b7115a7389e", "eb8323f5-f046-4d53-a081-12fbd4d60a05e"
] "timeout":35 } |
|
日志说明 |
用户创建了一条还原记录 |
|
失败原因 |
当操作失败时，可能的原因如下： · A configuration restoration task is in progress. Please try again later：存在正在执行的恢复任务，请稍后再试 · Unknown errors：存在未知错误 · The specified restore point does not exist：指定的回滚点不存在 · You cannot restore the backup site：备用站点不允许进行还原操作 · You cannot restore the primary site in auto switchover mode：当前灾备系统为自动倒换模式，不允许执行还原操作 |
|
关键字 |
ROLLBACK_DEVICE_OP |
|
日志内容 |
Rolled back device: $1 |
|
参数解释 |
$1：还原记录信息 |
|
举例 |
Rolled back device: { "id":"8eed6dfd-eb33-4e96-9760-e66636e6739f", "devices":[
"e87701a4-af3b-467b-a571-8b7115a7389e"， "eb8323f5-f046-4d53-a081-12fbd4d60a05e" ] } |
|
日志说明 |
用户重试还原某台还原失败的设备 |
|
失败原因 |
当操作失败时，可能的原因如下： · A configuration restoration task is in progress. Please try again later：存在正在执行的恢复任务，请稍后再试 · Unknown errors：存在未知错误 · The specified restore point does not exist：指定的回滚点不存在 |
|
关键字 |
START_CREATE_SNAPSHOT_OP |
|
日志内容 |
Created a snapshot: $1 |
|
参数解释 |
$1：快照名称 |
|
举例 |
Created a snapshot: tn-111_20210224102230_M.zip |
|
日志说明 |
用户执行了创建快照的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Failed to obtain the snapshot creation parameters：创建快照的参数获取失败 · Please configure the snapshot parameters first：请先进行快照的参数设置 · Failed to save the created snapshot：创建的快照保存失败 · Operation in progress. Please try again later：操作进行中，请稍后 · The system service does not respond：系统服务未响应 · Invalid parameter：无效的参数 · You cannot perform this operation, because the tenant of the specified snapshot does not exist or has been deleted：指定快照文件的租户不存在或已被删除，无法进行操作 · Failed to notify the controller to create a snapshot：通知控制组件创建快照失败 |
|
关键字 |
START_UPLOAD_SNAPSHOT_OP |
|
日志内容 |
Uploaded a snapshot: $1 |
|
参数解释 |
$1：快照名称 |
|
举例 |
Uploaded a snapshot: tn-111_20210224102230_M.zip |
|
日志说明 |
用户执行了导入快照的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The system service does not respond：系统服务未响应 · The snapshot already exists：快照文件已存在 · Invalid snapshot file content：无效的快照文件内容 · Failed to get snapshot create config：获取创建快照的配置失败 · Please configure the snapshot parameters first：请先进行快照的参数设置 · Failed to synchronize the snapshot file to other nodes：快照文件同步至其他节点失败 · You cannot perform this operation, because the tenant of the specified snapshot does not exist or has been deleted：指定快照文件的租户不存在或已被删除，无法进行操作 |
|
关键字 |
START_DOWNLOAD_SNAPSHOT_OP |
|
日志内容 |
Downloaded a snapshot: $1 |
|
参数解释 |
$1：快照名称 |
|
举例 |
Downloaded a snapshot: tn-111_20210224102230_M.zip |
|
日志说明 |
用户执行了下载快照的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The snapshot file does not exist：快照文件不存在 · Failed to download the snapshot：快照文件下载失败 · Invalid parameter：无效的参数 |
|
关键字 |
UPDATE_SNAPSHOT_CREATE_CONFIG_OP |
|
日志内容 |
Updated the snapshot parameter settings: $1 |
|
参数解释 |
$1：快照参数 |
|
举例 |
Updated the snapshot parameter settings: { "prefix":"AA", "wholeNetworkNum":30, "singleTenantNum" : 50, "remoteIp":"192.168.135.10", "remotePath":"/opt/sdn/snapshot/source", "userName":"admin", "password":"admin@123", "protocol":"protocol", "passwordChanged":true } |
|
日志说明 |
用户执行了修改快照参数设置的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The system service does not respond：系统服务未响应 · Invalid parameter：无效的参数 |
|
关键字 |
UPDATE_TIMING_CREATE_OP |
|
日志内容 |
Updated the auto snapshot schedule settings: $1 |
|
参数解释 |
$1：定时创建快照参数 |
|
举例 |
Updated the auto snapshot schedule settings: { "open" : true, "frequency" : "EVERYDAY", "startTime" : "00:00:00", "selectedTenantList" : [ { "snapshotType" : "WHOLE_NETWORK", "tenantId" : ,"" "tenantName" : "" "snapshotType" : "TENANT", "tenantId" : "9ffdec4b-6e14-49a7-b025-b6fc1198421b", "tenantName" : "222" }, { "snapshotType" : "TENANT", "tenantId" : "ffffffff-0000-0000-0000-000000000001", "tenantName" : "default" }, { "snapshotType" : "TENANT", "tenantId" : "6d465c28-fdc7-481d-8ab6-0d932b4095c0", "tenantName" : "tenant1" } ] } |
|
日志说明 |
用户执行了修改定时创建快照参数的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The system service does not respond：系统服务未响应 · Invalid parameter：无效的参数 · Please configure the snapshot parameters first：请先进行快照的参数设置 |
|
关键字 |
SNAPSHOT_COMPARE_OP |
|
日志内容 |
Compared snapshots $1 and $2. |
|
参数解释 |
$1：左对比点（基准快照）的快照名称 $2：右对比点的快照名称或当前配置 |
|
举例 |
Compared snapshots: tn-111_20210224102230_M.zip and tn-111_20210724002785_M.zip. |
|
日志说明 |
用户执行了快照比对的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Failed to obtain the snapshot creation parameters：创建快照的参数获取失败 · Please configure the snapshot parameters first：请先进行快照的参数设置 · Invalid parameter：无效的参数 · The snapshots used for comparison must belong to the same tenant or both are network-wide services snapshots：比对的快照必须属于同一租户或均为全网业务快照 · Operation in progress. Please try again later：操作进行中，请稍后 · The snapshot file does not exist：快照文件不存在 · The system service does not respond：系统服务未响应 · You cannot perform this operation, because the tenant of the specified snapshot does not exist or has been deleted：指定快照文件的租户不存在或已被删除，无法进行操作 · Failed to notify the controller to compare snapshots：通知控制组件比对快照失败 |
|
关键字 |
SNAPSHOT_ROLLBACK_OP |
|
日志内容 |
Rolled back a snapshot: $1 |
|
参数解释 |
$1：基准快照名称 |
|
举例 |
Rolled back a snapshot: tn-111_20210224102230_M.zip |
|
日志说明 |
用户执行了快照回滚的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid parameter：无效的参数 · The change information has expired. Please run the comparison task again before rollback：差异信息已过期，请重新进行比对后再回滚 · Operation in progress. Please try again later：操作进行中，请稍后 · The system service does not respond：系统服务未响应 · The snapshot file does not exist：快照文件不存在 · The number of selected resources to roll back has exceeded the upper limit：选择回滚的资源数量超过上限 · You cannot perform this operation, because the tenant of the specified snapshot does not exist or has been deleted：指定快照文件的租户不存在或已被删除，无法进行操作 |
|
关键字 |
DELETE_SNAPSHOTS_OP |
|
日志内容 |
Deleted snapshots: $1 |
|
参数解释 |
$1：快照名称 |
|
举例 |
Deleted snapshots: [tn-111_20210224102230_M.zip, all_20210222101703_M.zip] |
|
日志说明 |
用户执行了删除快照的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid parameter：无效的参数 · The system service does not respond：系统服务未响应 · The snapshot file does not exist：快照文件不存在 |
|
关键字 |
UPDATE_SSH_AUTH_OP_DESC |
|
日志内容 |
Updated SSH connection parameters: $1 |
|
参数解释 |
$1：SSH连接参数信息 |
|
举例 |
Updated SSH connection parameters: status:[98.0.51.102] Modify authentication method: [ { "device_username":"test", "auth_type":"password", "publickey":null } ] |
|
日志说明 |
用户进行了修改SSH连接配置信息的操作 |
|
· 失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · Failed to connect to the device：设备连接失败 · You do not have privilege to perform the operation：无权限操作 · Invalid parameter：无效的参数 · Invalid JSON format：无效的JSON格式 · Invalid IP address：无效的IP地址 · Invalid fingerprints：无效的指纹 |
|
关键字 |
UPDATE_FINGERPRINT_CONFIG_OP_DESC |
|
日志内容 |
Updated SSH fingerprint parameters: $1 |
|
参数解释 |
$1：SSH指纹信息 |
|
举例 |
Updated SSH fingerprint parameters: [ { "trust_first_publickey":true， "locker_first_publickey":true } ] |
|
日志说明 |
用户进行了修改SSH指纹配置信息的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · Unknown error：未知错误 · You do not have privilege to perform the operation：无权限操作 |
|
关键字 |
UPLOAD_FILE_OP_DESC |
|
日志内容 |
Import SSH fingerprints: $1 |
|
参数解释 |
$1：导入的指纹 |
|
举例 |
Import SSH fingerprints: Upload fingerprint size:[2] list:[[SSHFingerprint [deviceIp=98.0.50.101, deviceUsername=null, fingerprint=AAAAB3NzaC1yc2EAAAADAQABAAAAgQC6HYrze6 aLFUmYxTF/PRO+a+hScZ6iBttgPgCNcsAsTu+PR7IEfbdz5RPh5+4fPacoplord6gtyslMS uLR07W/LaT4OmkXTkDpmCXoUchAojUIZii7VF8Wi7xAhxPY8cW1QO9nSbQx3S8hsFbPk66gyADU/a3hJsnb1Qb0Y8k/hQ==, fingerprintType=RSA, authType=null], SSHFingerprint [deviceIp=98.0.51.102, deviceUsername=null, fingerprint=AAAAB3Nz aC1yc2EAAAADAQABAAAAgQC6HYrze6aLFUmYxTF/PRO+a+hScZ6iBttgPgCNcsAsTu+PR7IEfbdz5RPh5+4fPacoplord6gtyslMSuLR07W/LaT4OmkXTkDpmCXoUchAojUIZii7VF8Wi7 xAhxPY8cW1QO9nSbQx3S8hsFbPk66gyADU/a3hJsnb1Qb0Y8k/hQ==, fingerprintType =RSA, authType=null]]] |
|
日志说明 |
用户进行了导入SSH指纹的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Failed to parse the uploaded file：上传文件无效 · Unknown error：未知错误 · The name of the file to upload is invalid：上传文件名无效 · The file to upload is empty：上传文件内容为空 · You can upload up to 500 fingerprints：上传文件内容超出500 · Invalid IP address：无效的IP地址 · Invalid fingerprints：无效的指纹 · An import or export task is in progress. Please try again later：正在导入，请稍后再试 |
|
关键字 |
CREATE_EXPANSION_LINK_OP |
|
日志内容 |
Created expansion link: $1. |
|
参数解释 |
$1：扩容链路信息，包括链路类型、链路两端所在端口和设备信息 |
|
举例 |
Created expansion link: { ID: [ c352f537-ad49-48eb-ab05-1c6b8cb92233] Local Device IP: [192.168.1.1] Remote Device IP: [192.168.1.2] Local Port Name: [GE2/0/1] Remote Port Name: [GE2/0/1] Type: [Spine-Leaf] }. |
|
日志说明 |
用户进行了创建扩容链路的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service does not exist：服务不存在 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · Failed to add the configuration item：添加配置项失败 · The local device does not exist：本端设备不存在 · The local interface does not exist：本端设备选中的端口不存在 · The remote device does not exist：对端设备不存在 · The remote interface does not exist：对端设备选中的端口不存在 · You can skip this step. The local device has been configured for automatic deployment, including link expansion：本端设备为自动化上线设备，链路可自动扩容，无需进行此步骤操作 · You can skip this step. The peer device has been configured for automatic deployment, including link expansion：对端设备为自动化上线设备，链路可自动扩容，无需进行此步骤操作 · The local device is an M-LAG system member, and it does not support manual link expansion：本端设备已组成跨设备聚合组，不支持对该设备进行链路扩容 · The remote device is an M-LAG system member, and it does not support manual link expansion：对端设备已组成跨设备聚合组，不支持对该设备进行链路扩容 · No links exist between the two selected devices：指定的两个设备间没有链路 · A link already exists on the local port：指定的本端端口上已存在链路 · A link already exists on the remote port：指定的对端端口上已存在链路 · The selected local port has been specified for link expansion：指定的本端设备端口已经配置过链路扩容 · The selected remote port has been specified for link expansion：指定的对端设备端口已经配置过链路扩容 · The controller failed to establish a connection to the device：控制组件与设备建立连接失败 · No OSPF ports exist on the local device：指定的本端设备上没有OSPF端口 · No OSPF ports exist on the remote device：指定的对端设备上没有OSPF端口 · The IP addresses in the underlay IP address pool are insufficient：Underlay地址池中IP地址不足 · Failed to obtain local M-LAG interface information：获取本端设备上M-LAG接口信息失败 · Failed to obtain remote M-LAG interface information：获取对端设备上M-LAG接口信息失败 · For a peer-link, you must specify two devices that belong to the same M-LAG system：在peer-link链路中，指定的两台设备必须属于同一个跨设备聚合组 · The local device is in Inactive state：本端设备没有激活 · The remote device is in Inactive state：远端设备没有激活 · The role of the local device must be spine for a spine-leaf link：Spine-Leaf链路本端设备的角色必须为Spine · The role of the remote device must be leaf for a spine-leaf link：Spine-Leaf链路远端设备的角色必须为Leaf · The role of the local device must be spine or leaf for a peer-link：peer-link链路本端设备的角色必须为Spine或Leaf · The role of the remote device must be spine or leaf for a peer-link：peer-link链路远端设备的角色必须为Spine或Leaf · To expand a peerlink, make sure the roles of the local device and remote device are the same：peer-link链路扩容时，本端和对端设备的角色必须相同。 |
|
关键字 |
CONFIG_EXPANSION_LINK_OP |
|
日志内容 |
Configured expansion link: $1 |
|
参数解释 |
$1：扩容链路的UUID |
|
举例 |
Configured expansion link: { ID: [ c352f537-ad49-48eb-ab05-1c6b8cb92233] Local Device IP: [192.168.1.1] Remote Device IP: [192.168.1.2] Local Port Name: [GE2/0/1] Remote Port Name: [GE2/0/1] Type: [IPL] }. |
|
日志说明 |
用户使用一个扩容链路进行配置下发操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service does not exist：服务不存在 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · The configuration item does not exist：配置项不存在 · Failed to modify the configuration item：修改配置项失败 · The controller failed to establish a connection to the device：控制组件与设备建立连接失败 · The specified link has been configured for expansion：该扩容链路已经下发过配置 |
|
关键字 |
DELETE_EXPANSION_LINK_OP |
|
日志内容 |
Deleted expansion link: $1 |
|
参数解释 |
$1：扩容链路的UUID |
|
举例 |
Deleted expansion link: { ID:[fb6dca26-e1bf-42e3-a59c-1d2991faf8d3] Local Device IP:[98.0.50.102] Remote Device IP:[98.0.50.103] Local Port Name:[WGE1/0/1] Remote Port Name:[WGE1/0/1] Type:[Spine-Leaf] }. |
|
日志说明 |
用户进行了删除扩容链路的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service does not exist：服务不存在 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · Failed to delete the configuration item：删除配置项失败 · The configuration item does not exist：配置项不存在 · The controller failed to establish a connection to the device：控制组件与设备建立连接失败 |
本节介绍资源接入模块输出的操作日志信息。
|
关键字 |
CREATE_RESOURCETEMPLATE_OP |
|
日志内容 |
Created resource access template $1 |
|
参数解释 |
$1：资源接入模块配置信息 |
|
举例 |
Created resource access template ID: e356dfe6-d1c1-4bac-8fd9-940c97e15524 Name: 资源接入模板1 Vlan pool name: vlan200 Vxlan pool name: vxlan200 Ip pool name: IP地址池200 Rs template name: 物理资源池模板1 Rs template type: NGFW Access device: [{ Device name: 686 Ingress port: Ten-GigabitEthernet1/2/23 Egress Port: Ten-GigabitEthernet1/2/23 }] |
|
日志说明 |
用户进行了创建资源接入模板的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置正在恢复中 · The controller is not the active leader：该控制组件不是主Leader · The resource access template already exists：资源接入模板已存在 · The ingress port isn't the downlink port of the access device：入接口必须为接入设备的下行口 · The egress port isn't the downlink port of the access device：出接口必须为接入设备的下行口 · The specified access device doesn't exists：指定的接入设备不存在 · The VXLAN pool doesn't exists：指定的VXLAN池不存在 · The VLAN pool doesn't exists：指定的VLAN池不存在 · The IP pool doesn't exists：指定的地址池不存在 · Invalid name：无效的名称 · The type of resource can only be VNF or NGFW：资源类型仅支持VNF和NGFW · Duplicate entries exist in the resource access template：资源接入模板中存在完全相同的接入信息 · The resource access template cannot contain more than 16 entries：接入信息最多不能超过16个 · You have no privilege to perform this operation：用户无权限执行此操作 · When the connection mode is one arm, make sure the input and output interfaces for the access device are the same：当连接模式为单臂时，接入设备的出入接口必须相同 · When the connection mode is one arm, make sure the service type is FW for the associated resource template：当连接模式为单臂时，资源模板服务类型必须为FW · When the connection mode is one arm, make sure the uplink and downlink interfaces for the associated resource template are the same：当连接模式为单臂时，资源模板的上下行接口必须相同 · The specified VNF template does not exist：VNF模版不存在 · The specified NGFW template does not exist：NGFW模板不存在 · Incorrect resource template type. Please select the PBR service chain FW or PBR service chain LB：资源模板类型错误，请选择PBR服务链FW资源或PBR服务链LB资源 · The resource source can only be VNF, NGFW, or Custom：资源来源必须是VNF，NGFW，Custom · The rs_template_id parameter is required when the resource source is NGFW：当资源来源是NGFW，rs_template_id字段是必选字段 · The rs_template_name parameter is required when the resource source is VNF：当资源来源是VNF，rs_template_name字段是必选字段 · The name parameter is required：name字段是必选字段 · The rs_template_type parameter is required：rs_template_type字段是必选字段 · The egress_port parameter is required：egress_port字段是必选字段 · The ingress_port parameter is required：ingress_port字段是必选字段 · The device_id parameter is required：device_id字段是必选字段 · The ip_pool_id parameter is required：ip_pool_id字段是必选字段 · The vxlan_pool_id parameter is required：vxlan_pool_id字段是必选字段 · The vlan_pool_id parameter is required：vlan_pool_id字段是必选字段 · The device_name parameter is read only：device_name字段是只读字段 · The vxlan_pool_name parameter is read only：vxlan_pool_name字段是只读字段 · The vlan_pool_name parameter is read only：vlan_pool_name字段是只读字段 · One or both of the selected device interfaces are used in another resource access template. Please reselect：指定的设备接口已被其他资源接入模板使用，请重新选择其他接口 · Make sure an access device interface is specified as either the output interface or input interface for different access information entries in the resource access template：资源接入模板内多个接入信息的相同设备接口只能同为出接口或同为入接口 · The ingress port isn't the downlink port of the access device：入接口是无效的的接入设备下行口 · The egress port isn't the downlink port of the access device：出接口是无效的的接入设备下行口 · You can bind only service leaf devices to service leaf templates：Service Leaf资源接入模板仅支持绑定Service Leaf设备 · The specified input and output interfaces on the access device are already used by another service：Service Leaf资源接入模板绑定的设备的出入接口已被其他映射使用 |
|
关键字 |
DELETE_RESOURCETEMPLATE_OP |
|
日志内容 |
Deleted resource access template $1. |
|
参数解释 |
$1：资源接入模板UUID |
|
举例 |
Deleted resource access template 7fda0d76-9a0a-4129-bc53-31e3b215f854. |
|
日志说明 |
用户进行了删除资源接入模板的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The resource access template doesn't exist：资源接入模板不存在 · Configuration recovery is in progress：配置恢复未完成 · The controller is not the active leader：该控制组件不是主Leader · You have no privilege to perform this operation：用户无权限执行此操作 · Cannot delete the resource access template, because it has been bound to a service resource：资源接入模板已绑定服务资源，不允许删除 · You cannot delete the resource access template, because a service leaf firewall that has vRouter bindings is associated with the template：由资源接入模板所关联资源模板创建的Service Leaf类型防火墙被虚拟路由器绑定，不允许删除该资源接入模板 |
本节介绍ROCENETWORK模块输出的操作日志信息。
|
关键字 |
UNBIND_ADDRESS_PLANNING_OP |
|
日志内容 |
Unbind server network address plan $1. |
|
参数解释 |
$1：静态DHCP参数体 |
|
举例 |
Unbind server network address plan AgentIP: 192.168.165.5, NIC:ens226, MAC:10:70:fd:11:82:76, IP:20.2.2.22. |
|
日志说明 |
用户进行了服务器网卡MAC解绑IP的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service does not exist：该服务不存在 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · Unbinding succeeded on the controller but failed on the server. Please log in to the server and manually unbind it：控制组件侧解绑成功，但服务器侧解绑失败，请登录服务器手动解绑 |
|
关键字 |
IMPORT_ADDRESS_PLANNING_OP |
|
日志内容 |
Import server network address plan "$1", successfully imported IPs: $2, failed imported IPs: $3. |
|
参数解释 |
$1：导入的文件名 $2：导入规划IP的成功数 $3：导入规划IP的失败数 |
|
举例 |
Import server network address plan "1.xlsx", successfully imported IPs: 0, failed imported IPs: 3. |
|
日志说明 |
用户进行了导入静态DHCP的地址规划的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · Incorrect file name：文件名错误 · An import task is in progress. Please try again later：当前正在导入文件，不允许执行该操作 · An export task is in progress. Please try again later：当前正在导出文件，不允许执行该操作 · Failed to parse the file：文件解析失败 · The uploaded file content is invalid：上传的文件内容无效 · The uploaded file type is invalid：上传的文件类型无效 · Invalid template. Please download the latest template：模板不匹配，请使用最新模板 · Failed to parse the Excel file：Excel文件读取失败 · The file content is required：文件内容不能为空 |
|
关键字 |
EXPORT_ADDRESS_PLANNING_OP |
|
日志内容 |
Exported server network address plan "$1". |
|
参数解释 |
$1：导出的文件名 |
|
举例 |
Exported server network address plan "1.xlsx ". |
|
日志说明 |
用户进行了导出静态DHCP的地址规划模板的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service does not exist：该服务不存在 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The configuration item does not exist.：指定的配置项不存在 |
|
关键字 |
CONFIG_SERVER_OP |
|
日志内容 |
Configure server $1. |
|
参数解释 |
$1：批量配置的内容 |
|
举例 |
Configure server :{ “server_configs":{ agent_ips": [ "1.1.1.1", "1.1.1.12", ], " operation_config ":"ip route add default via 192.168.1.254 dev enp68s0 table 2" } } |
|
日志说明 |
用户进行了批量配置服务器的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service does not exist：该服务不存在 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · Invalid IP address：无效的IP地址 |
|
关键字 |
DEL_SERVER_CONFIG_OP |
|
日志内容 |
Deleted server configuration $1. |
|
参数解释 |
$1：删除端网配置 |
|
举例 |
Deleted server configuration agent IP: 192.168.118.206. |
|
日志说明 |
用户进行了删除服务器配置的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service does not exist：该服务不存在 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 |
本节介绍Runbook模块输出的操作日志信息。
|
关键字 |
ACTION_CREATE_DATATYPE |
|
日志内容 |
Created data type:$1. |
|
参数解释 |
$1：数据类型实体信息 |
|
举例 |
Created data type: { "id": "cf6a80d2-a305-43f6-a8a8-9b8566a3b4ae", "name": "name", "description": 描述", "ownerType": "public", "createTime": "2023-05-04 18:45:45" } |
|
日志说明 |
用户进行了创建数据类型操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · You have no privilege to perform the operation：当前用户无权限执行此操作 · The request body cannot be empty：请求体不能为空 · Invalid UUID：无效的UUID · Please specify a name：名称为必选项 · The description can contain up to 255 characters：描述最长255位字符 · The name can contain up to 64 characters, only letters, numbers and underscores (_) are supported, not support starting with number：仅支持字母、数字和下划线，不支持以数字开头，最长64位字符 · Please specify a description：描述不能为空 · Failed to create the data type：创建数据类型失败 · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · Duplicate name for data types：数据类型名称字段重复 |
|
关键字 |
ACTION_UPDATE_DATATYPE |
|
日志内容 |
Edited data type:$1. |
|
参数解释 |
$1：数据类型信息 |
|
举例 |
Edited data type: { "id": "cf6a80d2-a305-43f6-a8a8-9b8566a3b4ae", "name": "name", "description": 描述", "ownerType": "public", "createTime": "2023-05-04 18:45:45" } |
|
日志说明 |
用户进行更新数据类型操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid UUID：无效的UUID · The request body cannot be empty：请求体不能为空 · The specified data type does not exist：指定的数据类型不存在 · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · The description can contain up to 255 characters：描述最长255位字符 · Failed to edit the data type：修改数据类型接口失败 · You have no privilege to perform the operation：当前用户无权限执行此操作 |
|
关键字 |
ACTION_DELETED_DATATYPE |
|
日志内容 |
Deleted data type:$1. |
|
参数解释 |
$1：数据类型的ID |
|
举例 |
Deleted data type:0f0ce03d-d40a-4a1b-b745-cb1d9944f3ac |
|
日志说明 |
用户进行了删除数据类型的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid UUID：无效的UUID · The specified data type does not exist：指定的数据类型不存在 · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · Failed to delete the data type：删除数据类型失败 · You have no privilege to perform the operation：当前用户无权限执行此操作 · You cannot delete the data type, because it is in use：数据类型被引用，不允许删除 |
|
关键字 |
ACTION_CREATE_DATATYPE_PROPERTY |
|
日志内容 |
Created data type attributes:$1. |
|
参数解释 |
$1：数据类型属性信息 |
|
举例 |
Created data type attributes: { "properties": [{ "name": "acl_number_or_name", "type": "string", "description": "acl编号或者名称", "required": true, "constraints": [{ "valid_values": ["a", "b", "c"] }, { "min_length": 1 } ] }] } |
|
日志说明 |
用户进行了创建数据类型属性 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid UUID：无效的UUID · The request body cannot be empty：请求体不能为空 · The specified data type does not exist：指定的数据类型不存在 · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · Invalid UUID：无效的UUID · Please specify a name：名称为必选项 · The description can contain up to 255 characters：描述最长255位字符 · Please specify a name：名称为必选项 · JSON format error： JSON格式错误 · The data type attribute’s type must be a basic data type or custom data type：数据类型的属性类型仅支持基本数据类型和除自身外的自定义数据类型 · When the type is not list, the entry_schema cannot be configured for the attribute：属性类型为基本数据类型时 不允许配置默认值和约束项 · When the type is list, the entry_schema can be configured only as a basic data type except list or a custom data type for the attribute：属性类型为list时，entry_schema只允许配置为除list外的基本数据类型和自定义数据类型 · The data type attribute’s default value can be set only for a basic data type：仅基本数据类型支持配置默认值 · When the type is not a basic data type, the default value or constraints cannot be configured for the attribute：属性类型不为基本数据类型时，不允许配置默认值和约束项 · The data type attribute’s type must be a basic data type：数据类型属性类型必须为基本数据类型 · The element value does not match the basic data type：值与基本数据类型不匹配 · Invalid attribute constraint item：无效的属性约束项 · Failed to create the data type attribute：创建数据类型属性失败 · You have no privilege to perform the operation：当前用户无权限执行此操作 · Duplicate name for data type attributes：数据类型属性名称字段重复 · The name can contain up to 64 characters. Only letters, numbers and underscores (_) are supported, Names starting with a number and keywords like true, false, null, not, and empty are not supported：仅支持字母、数字和下划线，不支持以数字开头且不支持true、false、null、not和empty等关键词，最长64位字符 · Circular dependency for the attribute type：属性type循环依赖 · The data type attribute's default value can be set only for a basic data type other than list：仅支持为list以外的基本数据类型设置数据类型属性的默认值 · Duplicate attribute constraint items：存在重复的属性约束项 |
|
关键字 |
ACTION_UPDATE_DATATYPE_PROPERTY |
|
日志内容 |
Edited data type attribute:$1. |
|
参数解释 |
$1：数据类型属性信息 |
|
举例 |
Edited data type attribute：{ "name": "acl_number_or_name", "type": "string", "description": "acl编号或者名称", "required": true, "constraints": [{ "valid_values": ["a", "b", "c"] }, { "min_length": 1 } ] } |
|
日志说明 |
用户进行了修改了指定数据类型属性操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid UUID：无效的UUID · The request body cannot be empty：请求体不能为空 · The specified data type does not exist：指定的数据类型不存在 · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · You have no privilege to perform the operation：当前用户无权限执行此操作 · Invalid UUID：无效的UUID · Please specify a name：名称为必选项 · The description can contain up to 255 characters：描述最长255位字符 · Please specify a name：名称为必选项 · JSON format error： JSON格式错误 · The data type attribute’s type must be a basic data type or custom data type：数据类型的属性类型仅支持基本数据类型和除自身外的自定义数据类型 · When the type is not list, the entry_schema cannot be configured for the attribute：属性类型为基本数据类型时 不允许配置默认值和约束项 · When the type is list, the entry_schema can be configured only as a basic data type except list or a custom data type for the attribute：属性类型为list时，entry_schema只允许配置为除list外的基本数据类型和自定义数据类型 · The data type attribute’s default value can be set only for a basic data type：仅基本数据类型支持配置默认值 · When the type is not a basic data type, the default value or constraints cannot be configured for the attribute：属性类型不为基本数据类型时，不允许配置默认值和约束项 · The specified data type does not exist：指定的数据类型不存在 · The data type attribute’s type must be a basic data type：数据类型属性类型必须为基本数据类型 · The element value does not match the basic data type：值与基本数据类型不匹配 · Invalid attribute constraint item：无效的属性约束项 · Failed to edit the data type attribute：修改数据类型属性失败 · Duplicate name for data type attributes：数据类型属性名称字段重复 · The name can contain up to 64 characters. Only letters, numbers and underscores (_) are supported, Names starting with a number and keywords like true, false, null, not, and empty are not supported：仅支持字母、数字和下划线，不支持以数字开头且不支持true、false、null、not和empty等关键词，最长64位字符 · Circular dependency for the attribute type：属性type循环依赖 · The data type attribute's default value can be set only for a basic data type other than list：仅支持为list以外的基本数据类型设置数据类型属性的默认值 · Duplicate attribute constraint items：存在重复的属性约束项 |
|
关键字 |
ACTION_DELETED_DATATYPE_PROPERTY |
|
日志内容 |
Deleted data type attribute:$1. |
|
参数解释 |
$1：数据类型属性ID |
|
举例 |
Deleted data type attribute: 6e2d585b-ff32-4b61-85ba-cb987f6e4a19 |
|
日志说明 |
用户进行删除指定数据类型属性操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid UUID：无效的UUID · The request body cannot be empty：请求体不能为空 · The specified data type does not exist：指定的数据类型不存在 · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · You cannot delete the data type, because it is in use：数据类型被引用，不允许删除 · Failed to delete the data type attribute：删除数据类型属性失败 · You have no privilege to perform the operation：当前用户无权限执行此操作 |
|
关键字 |
ACTION_CREATE_CATEGORY |
|
日志内容 |
Created category:$1. |
|
参数解释 |
$1：分类的信息 |
|
举例 |
Created category: { "createTime": "2023-05-04 18:45:45", "id": "758b5348-80c5-4965-b006-34fa4810f7c4", "name": "category_test", "parentId": "18910a6f-2f4c-4b29-a4f8-79eaec189c1f", "type": "action" } |
|
日志说明 |
用户进行了创建分类的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request body cannot be empty：请求体不能为空 · Invalid UUID：无效的UUID · The name can contain up to 64 characters, only
letters, · Please specify a category type：分类类型不能为空 · Invalid category type：无效的分类类型 · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · The specified parent category does not exist：指定的父分类不存在 · The specified category type does match the parent category type：指定分类类型和父分类的类型不一致 · A maximum of three levels of categories are supported：分类最多支持3个层级 · Duplicate name for subcategories under the same category level：同级分类下子分类不允许重 · Failed to create the category：创建分类失败 · You have no privilege to perform the operation：当前用户无权限执行此操作 · Internal server error：内部错误 |
|
关键字 |
ACTION_DELETE_CATEGORY |
|
日志内容 |
Deleted category:$1. |
|
参数解释 |
$1：分类的ID |
|
举例 |
Deleted category:758b5348-80c5-4965-b006-34fa4810f7c4 |
|
日志说明 |
用户进行了删除分类的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid UUID：无效的UUID · The specified category does not exist：指定的分类不存在 · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · A subcategory exists under the specified category：指定的分类下存在子分类 · A process package exists under the specified category：指定的分类下存在流程包 · An action package exists under the specified category：指定的分类下存在动作包 · Failed to delete the category：删除分类失败 · Internal server error：内部错误 · You have no privilege to perform the operation：当前用户无权限执行此操作 |
|
关键字 |
ACTION_CREATE_ACTION_PACKAGE |
|
日志内容 |
Created action package:$1. |
|
参数解释 |
$1：动作包的信息 |
|
举例 |
Created action package: { "categoryId": "18910a6f-2f4c-4b29-a4f8-79eaec189c1f", "createBy": "admin", "createTime": "2023-05-04 18:45:45", "description": "this is a description", "id": "d4f4f305-dcfe-441a-baaa-a5baf9d23c9b", "name": "action_package_test", "status": "unpublished", "versionX": 1, "versionY": 0, "versionZ": 1 } |
|
日志说明 |
用户进行了创建动作包的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request body cannot be empty：请求体不能为空 · Please specify a name：名称为必选项 · The name can contain up to 64 characters, only letters, numbers and underscores (_) are supported, not support starting with number：仅支持字母、数字和下划线，不支持以数字开头，最长64位字符 · The description can contain up to 255 characters：描述最长255位字符 · Invalid UUID：无效的UUID · The specified category does not exist：指定的分类不存在 · The specified category type does not match the package resource：指定的分类类型和包资源不匹配 · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · An action package already exists with the specified name：动作包不允许重名 · An process package already exists with the specified name：指定名称的流程包已存在 · Failed to create the action package：创建动作包失败 · Internal server error：内部错误 · You have no privilege to perform the operation：当前用户无权限执行此操作 · The name cannot start with "builtin_"：名称不支持以builtin_字符开头 |
|
关键字 |
ACTION_UPDATE_ACTION_PACKAGE |
|
日志内容 |
Edited action package:$1. |
|
参数解释 |
$1：动作包的信息 |
|
举例 |
Edited action package: { "categoryId": "18910a6f-2f4c-4b29-a4f8-79eaec189c1f", "createBy": "admin", "createTime": "2023-05-04 18:45:45", "description": "update action package description", "id": "d4f4f305-dcfe-441a-baaa-a5baf9d23c9b", "name": "action_package_test", "status": "unpublished", "updateBy": "admin", "updateTime": "2023-05-07 18:45:45", "versionX": 1, "versionY": 0, "versionZ": 1 } |
|
日志说明 |
用户进行了更新动作包的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid UUID：无效的UUID · The description can contain up to 255 characters：描述最长255位字符 · The specified action package does not exist：动作包不存在 · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · The specified action package is already published：指定的动作包已发布 · Failed to edit the action package：更新动作包失败 · Internal server error：内部错误 · You have no privilege to perform the operation：当前用户无权限执行此操作 |
|
关键字 |
ACTION_DELETE_ACTION_PACKAGE |
|
日志内容 |
Deleted action package:$1. |
|
参数解释 |
$1：动作包的ID |
|
举例 |
Deleted action package:d4f4f305-dcfe-441a-baaa-a5baf9d23c9b |
|
日志说明 |
用户进行了删除动作包的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid UUID：无效的UUID · The specified action package does not exist：动作包不存在 · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · The specified action package is already published：指定的动作包已发布 · Failed to delete the action package：删除动作包失败 · Internal server error：内部错误 · You have no privilege to perform the operation：当前用户无权限执行此操作 |
|
关键字 |
ACTION_CREATE_ACTION_MODEL |
|
日志内容 |
Created action model:$1. |
|
参数解释 |
$1：动作模型的信息 |
|
举例 |
Created action model: { "actionPackageId": "64e524d2-7cd4-4d31-9ccc-1e6c620f76e7", "createBy": "admin", "createTime": "2023-05-04 18:45:45", "description": "this is a description", "id": "f707d076-1f0e-4b0b-90c5-544d940b2426", "name": "create_ospf_area" } |
|
日志说明 |
用户进行了创建动作模型的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request body cannot be empty：请求体不能为空 · Invalid UUID：无效的UUID · Please specify a name：名称为必选项 · The name can contain up to 64 characters, only letters, numbers and underscores (_) are supported, not support starting with number：仅支持字母、数字和下划线，不支持以数字开头，最长64位字符 · The description can contain up to 255 characters：描述最长255位字符 · The specified action package does not exist：指定的动作包不存在 · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · The specified action package is already published：指定的动作包已发布 · An action model already exists with the specified name：同一动作包下的动作模型不允许重名 · Failed to create the action model：创建动作模型失败 · Internal server error：内部错误 · You have no privilege to perform the operation：当前用户无权限执行此操作 |
|
关键字 |
ACTION_UPDATE_ACTION_MODEL |
|
日志内容 |
Edited action model:$1. |
|
参数解释 |
$1：动作模型的信息 |
|
举例 |
Edited action model: { "actionPackageId": "64e524d2-7cd4-4d31-9ccc-1e6c620f76e7", "createBy": "admin", "createTime": "2023-05-04 18:45:45", "description": "update model description", "id": "f707d076-1f0e-4b0b-90c5-544d940b2426", "name": "create_ospf_area", "updateBy": "admin", "updateTime": "2023-05-07 18:45:45" } |
|
日志说明 |
用户进行了更新动作模型的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid UUID：无效的UUID · The specified action model does not exist：动作模型不存在 · The description can contain up to 255 characters：描述最长255位字符 · The name can contain up to 64 characters, only letters, numbers and underscores (_) are supported, not support starting with number：仅支持字母、数字和下划线，不支持以数字开头，最长64位字符 · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · The specified action package is already published：指定的动作包已发布 · An action model already exists with the specified name：同一动作包下的动作模型不允许重名 · Failed to edit the action model：更新动作模型失败 · Internal server error：内部错误 · You have no privilege to perform the operation：当前用户无权限执行此操作 |
|
关键字 |
ACTION_DELETE_ACTION_MODEL |
|
日志内容 |
Deleted action model:$1. |
|
参数解释 |
$1：动作模型的ID |
|
举例 |
Deleted action model:f707d076-1f0e-4b0b-90c5-544d940b2426 |
|
日志说明 |
用户进行了删除动作模型的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid UUID：无效的UUID · The specified action model does not exist：动作模型不存在 · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · The specified action package is already published：指定的动作包已发布 · Failed to delete the action model：删除动作模型失败 · Internal server error：内部错误 · You have no privilege to perform the operation：当前用户无权限执行此操作 |
|
关键字 |
ACTION_CREATE_ACTION_MODEL_PROPERTIES |
|
日志内容 |
Created action model:$1. |
|
参数解释 |
$1：动作模型输入、输出属性的信息 |
|
举例 |
Created action model properties: { "inputs": [{ "constraints": [{ "pattern": "uuid" }], "id": "e2f0cc8f-4e1d-463b-9727-7e1e70ecc113", "name": "ospf_policy_id", "required": false, "sensitive": false, "type": "string" }], "outputs": [{ "constraints": [], "id": "905ab388-cd6a-4ea2-824b-f40b2197a75a", "name": "ospf_policy_id", "required": false, "sensitive": false, "type": "string" }] } |
|
日志说明 |
用户进行了创建动作模型属性的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request body cannot be empty：请求体不能为空 · Invalid UUID：无效的UUID · Input or output attributes cannot be empty at the same time：输入或输出属性不能同时为空 · The specified action model does not exist：动作模型不存在 · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · The specified action package is already published：指定的动作包已发布 · An input or output attribute already exists with the specified name：指定名称的输入或输出属性已存在 · Please specify a name：名称为必选项 · The description can contain up to 255 characters：描述最长255位字符 · JSON format error：JSON格式错误 · The data type attribute's type must be a basic data type or custom data type：数据类型的属性类型仅支持基本数据类型和除自身外的自定义数据类型 · When the type is not list, the entry_schema cannot be configured for the attribute：属性类型不为list时，不允许配置entry_schema · When the type is not a basic data type, the default value or constraints cannot be configured for the attribute：属性类型不为基本数据类型时，不允许配置默认值和约束项 · Invalid name for the attribute constraint item：无效的属性约束项名称 · The attribute constraint item does not match the attribute type：属性约束项与属性类型不匹配 · The value assigned to the attribute is not within the valid value range for the attribute：属性赋值不在属性有效值范围内 · The number of subelements is inaccurate for the attribute constraint item value：属性约束项与子元素数量不匹配 · Invalid value for attribute constraint item：无效的属性约束项取值 · The data type attribute's default value can be set only for a basic data type：仅基本数据类型支持配置默认值 · Property constraint items are mutually exclusive：属性约束项存在互斥 · The attribute constraint item does not match the attribute type：属性约束项与属性类型不匹配 · Invalid name for the attribute constraint item：无效的属性约束项名称 · When the type is list, the entry_schema can be configured only as a basic data type except list or a custom data type for the attribute：属性类型为list时，entry_schema只允许配置为除list外的基本数据类型和自定义数据类型 · The value does not match the basic data type：值与基本数据类型不匹配 · The data type attribute's type must be a basic data type：数据类型属性type必须为基本数据类型 · Invalid attribute constraint item：无效的属性约束项 · The value assigned to the attribute is not within the valid value range for the attribute：属性赋值不在属性有效值范围内 · Failed to create the action model attribute：创建动作模型输入输出属性失败 · Internal server error：内部错误 · You have no privilege to perform the operation：当前用户无权限执行此操作 · The name can contain up to 64 characters. Only letters, numbers and underscores (_) are supported, Names starting with a number and keywords like true, false, null, not, and empty are not supported：仅支持字母、数字和下划线，不支持以数字开头且不支持true、false、null、not和empty等关键词，最长64位字符 · The data type attribute's default value can be set only for a basic data type other than list：仅支持为list以外的基本数据类型设置数据类型属性的默认值 · Duplicate attribute constraint items：存在重复的属性约束项 |
|
关键字 |
ACTION_UPDATE_ACTION_MODEL_PROPERTY |
|
日志内容 |
Edited action model property:$1. |
|
参数解释 |
$1：动作模型输入、输出属性的信息 |
|
举例 |
Edited action model property: { "constraints": [{ "min_length": 7 }], "defaultValue": "0.0.0.1", "description": "ipv4格式", "id": "5014322c-8198-4b4d-9655-c830560a78d2", "name": "area_id", "required": true, "sensitive": true, "type": "string" } |
|
日志说明 |
用户进行了创建动作模型的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid UUID：无效的UUID · The specified action model attribute does not exist：指定的动作模型属性不存在 · The specified action model does not exist：动作模型不存在 · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · The specified action package is already published：指定的动作包已发布 · An input or output attribute already exists with the specified name：指定名称的输入或输出属性已存在 · Please specify a name：名称为必选项 · The description can contain up to 255 characters：描述最长255位字符 · JSON format error：JSON格式错误 · The data type attribute's type must be a basic data type or custom data type：数据类型的属性类型仅支持基本数据类型和除自身外的自定义数据类型 · When the type is not list, the entry_schema cannot be configured for the attribute：属性类型不为list时，不允许配置entry_schema · When the type is not a basic data type, the default value or constraints cannot be configured for the attribute：属性类型不为基本数据类型时，不允许配置默认值和约束项 · Invalid name for the attribute constraint item：无效的属性约束项名称 · The attribute constraint item does not match the attribute type：属性约束项与属性类型不匹配 · The value assigned to the attribute is not within the valid value range for the attribute：属性赋值不在属性有效值范围内 · The number of subelements is inaccurate for the attribute constraint item value：属性约束项与子元素数量不匹配 · Invalid value for attribute constraint item：无效的属性约束项取值 · The data type attribute's default value can be set only for a basic data type：仅基本数据类型支持配置默认值 · Property constraint items are mutually exclusive：属性约束项存在互斥 · The attribute constraint item does not match the attribute type：属性约束项与属性类型不匹配 · Invalid name for the attribute constraint item：无效的属性约束项名称 · When the type is list, the entry_schema can be configured only as a basic data type except list or a custom data type for the attribute：属性类型为list时，entry_schema只允许配置为除list外的基本数据类型和自定义数据类型 · The value does not match the basic data type：值与基本数据类型不匹配 · The data type attribute's type must be a basic data type：数据类型属性type必须为基本数据类型 · Invalid attribute constraint item：无效的属性约束项 · The value assigned to the attribute is not within the valid value range for the attribute：属性赋值不在属性有效值范围内 · Failed to edit the action model attribute：修改动作模型输入输出属性失败 · Internal server error：内部错误 · You have no privilege to perform the operation：当前用户无权限执行此操作 · The name can contain up to 64 characters. Only letters, numbers and underscores (_) are supported, Names starting with a number and keywords like true, false, null, not, and empty are not supported：仅支持字母、数字和下划线，不支持以数字开头且不支持true、false、null、not和empty等关键词，最长64位字符 · The data type attribute's default value can be set only for a basic data type other than list：仅支持为list以外的基本数据类型设置数据类型属性的默认值 · Duplicate attribute constraint items：存在重复的属性约束项 |
|
关键字 |
ACTION_DELETE_ACTION_MODEL_PROPERTY |
|
日志内容 |
Deleted action model property:$1. |
|
参数解释 |
$1：动作模型输入输出属性的ID |
|
举例 |
Deleted action model property:ffff7ae8-e166-4a07-a2ea-90fcb0bd2c80 |
|
日志说明 |
用户进行了删除动作模型输入输出属性的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid UUID：无效的UUID · The specified action model attribute does not exist：指定的动作模型属性不存在 · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · The specified action package is already published：指定的动作包已发布 · Failed to delete the action model attribute：删除动作模型输入输出属性失败 · Internal server error：内部错误 · You have no privilege to perform the operation：当前用户无权限执行此操作 |
|
关键字 |
ACTION_CREATE_ACTION_STEP |
|
日志内容 |
Created action step:$1. |
|
参数解释 |
$1：动作步骤的信息 |
|
举例 |
Created action step: { "actionModelId": "141d4a36-e4ca-4a47-828f-d45abcda3e2b", "actionType": "do", "condition": "equals: [a, a]", "id": "678f9d2d-e2b0-4377-b8e9-b1b3e9ed57ab", "method": "POST", "orderNo": 1, "repeat": { "enable": true, "interval": 5000, "stopCondition": "equals: [\"${responseBody.status}\", 'active']", "timeout": 300000 }, "request": { "body": "id: ${requestData.id}", "headers": { "Content-Type": "application/json" }, "pathParameters": "id: ${requestData.id}", "queryParameters": "id: ${requestData.id}", "timeout": 300000 }, "requestType": "DCN", "response": { "attributes": "name: ${responseBody.name}\r\nvalue: ${responseBody.value}", "responseCode": "if_else:\r\n- equals: [\"${stateCode}\", 201] \r\n- 200\r\n- ${stateCode}", "result": "vpnInfo: ${responseBody.vpn}" }, "url": "/aaa/test/{id}" } |
|
日志说明 |
用户进行了创建动作步骤的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request body cannot be empty：请求体不能为空 · Invalid UUID：无效的UUID · Please specify type for the action step：动作类型不能为空 · Invalid action step type：无效的动作类型 · Please specify order number for the action step：步骤执行顺序不能为空 · Invalid action step order. The step order value must be an integer in the range of 1 to 100：无效的步骤执行顺序，步骤执行顺序取值范围为1~100的整数 · Please specify request type for the action step：请求类型不能为空 · Invalid request type for the action step：无效的请求类型 · Please specify a URL for the action step：请求URL不能为空 · Please configure query parameters in request：请在request中配置查询参数 · Invalid action step URL：无效的url · Please specify request method for the action step：请求方法不能为空 · Invalid request method for the action step：无效的请求方法 · Invalid condition configuration for the action step：无效的Condition配置 · Variables in the URL must be assigned values in the path parameters：url中的变量必须在路径参数中赋值 · Invalid output attributes for the action step：无效的动作输出参数 · Invalid result for the action step：无效的全局变量 · Invalid response code for the action step：无效的响应状态码 · When the repeat is enabled, the repeat stop condition must be configured for the action step：开启轮询时，必须配置轮询结束条件 · Invalid timeout for the action step：无效的超时时间 · Invalid repeat interval for the action step：无效的轮询间隔时间 · Invalid repeat stop condition for the action step：无效的轮询结束条件 · The specified action model does not exist：动作模型不存在 · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · The action step order number conflicts：步骤执行顺序存在冲突 · Failed to create the action step：创建动作步骤失败 · Internal server error：内部错误 · You have no privilege to perform the operation：当前用户无权限执行此操作 |
|
关键字 |
ACTION_UPDATE_ACTION_STEP |
|
日志内容 |
Edited action step:$1. |
|
参数解释 |
$1：动作步骤的信息 |
|
举例 |
Edited action step: { "actionType": "do", "condition": "equals: [a, a]", "id": "678f9d2d-e2b0-4377-b8e9-b1b3e9ed57ab", "method": "POST", "orderNo": 1, "repeat": { "enable": true, "interval": 5000, "stopCondition": "equals: [\"${responseBody.status}\", 'active']", "timeout": 300000 }, "request": { "body": "id: ${requestData.id}", "headers": { "Content-Type": "application/json" }, "pathParameters": "id: ${requestData.id}", "queryParameters": "id: ${requestData.id}", "timeout": 300000 }, "requestType": "DCN", "response": { "attributes": "name: ${responseBody.name}\r\nvalue: ${responseBody.value}", "responseCode": "if_else:\r\n- equals: [\"${stateCode}\", 201] \r\n- 200\r\n- ${stateCode}", "result": "vpnInfo: ${responseBody.vpn}" }, "url": "/aaa/test/{id}" } |
|
日志说明 |
用户进行了动作步骤的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid UUID：无效的UUID · The specified action step does not exist：指定的动作步骤不存在 · Invalid action step type：无效的动作类型 · Please specify order number for the action step：步骤执行顺序不能为空 · Invalid action step order The step order value must be an integer in the range of 1 to 100：无效的步骤执行顺序 · Please specify request type for the action step：请求类型不能为空 · Invalid request type for the action step：无效的请求类型 · Please specify a URL for the action step：请求URL不能为空 · Please configure query parameters in request：请在request中配置查询参数 · Invalid action step URL：无效的url · Please specify request method for the action step：请求方法不能为空 · Invalid request method for the action step：无效的请求方法 · Invalid condition configuration for the action step：无效的Condition配置 · Variables in the URL must be assigned values in the path parameters：url中的变量必须在路径参数中赋值 · Invalid output attributes for the action step：无效的动作输出参数 · Invalid result for the action step：无效的全局变量 · Invalid response code for the action step：无效的响应状态码 · When the repeat is enabled, the repeat stop condition must be configured for the action step：开启轮询时，必须配置轮询结束条件 · Invalid timeout for the action step：无效的超时时间 · Invalid repeat interval for the action step：无效的轮询间隔时间 · Invalid repeat stop condition for the action step：无效的轮询结束条件 · The specified action model does not exist：动作模型不存在 · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · The action step order number conflicts：步骤执行顺序存在冲突 · The specified action model does not exist：动作模型不存在 · The description can contain up to 255 characters：描述最长255位字符 · The name can contain up to 64 characters, only letters, numbers and underscores (_) are supported, not support starting with number：仅支持字母、数字和下划线，不支持以数字开头，最长64位字符 · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · The specified action package is already published：指定的动作包已发布 · An action model already exists with the specified name：同一动作包下的动作模型不允许重名 · You cannot change the action step type：动作类型不允许修改 · Failed to edit the action step：修改动作步骤失败 · Internal server error：内部错误 · You have no privilege to perform the operation：当前用户无权限执行此操作 |
|
关键字 |
ACTION_DELETE_ACTION_STEP |
|
日志内容 |
Deleted action step:$1. |
|
参数解释 |
$1：动作步骤的ID |
|
举例 |
Deleted action step:58a5f3ec-a8d9-46e5-a22a-fa1e8ac49141 |
|
日志说明 |
用户进行了删除动作步骤的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid UUID：无效的UUID · The specified action step does not exist：指定的动作步骤不存在 · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · The specified action package is already published：指定的动作包已发布 · Failed to delete the action step：删除动作步骤失败 · Internal server error：内部错误 · You have no privilege to perform the operation：当前用户无权限执行此操作 |
|
关键字 |
ACTION_BATCH_PROCESS_ACTION_STEPS |
|
日志内容 |
Batch processed action steps:$1. |
|
参数解释 |
$1：动作步骤列表的信息 |
|
举例 |
Batch processed action steps: { "actionType": "do", "steps": [{ "actionType": "do", "condition": "dequals: [\"${responseBody.status}\", 'active']", "method": "GET", "orderNo": 1, "repeat": { "enable": true, "interval": 1000, "stopCondition": "equals: [\"${responseBody.status}\", 'active']", "timeout": 300000 }, "request": { "headers": { "name": "luqidddang" }, "pathParameters": "id: \"e2f0cc8f-4e1d-463b-9727-7e1e70ecc115\"", "queryParameters": "name: \"luqiadddddddng\"", "timeout": 3000003 }, "requestType": "DCN", "response": { "attributes": "name: \"luqddddddiang\"", "responseCode": "if_else:\n - equals: [\"${stateCodde}\", 201] \n - 200\n - ${stateCode}", "result": "output_result \"ssddddddddddddddddd\"" }, "url": "/latesddt/{id}" }] } |
|
日志说明 |
用户进行了批量处理动作步骤的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request body cannot be empty：请求体不能为空 · Invalid UUID：无效的UUID · Please specify type for the action step：动作类型不能为空 · Invalid action step type：无效的动作类型 · The specified step action type does not match the patch action type：动作类型和批量处理的动作类型不匹配 · Please specify order number for the action step：步骤执行顺序不能为空 · Invalid action step order The step order value must be an integer in the range of 1 to 100：无效的步骤执行顺序 · Please specify request type for the action step：请求类型不能为空 · Invalid request type for the action step：无效的请求类型 · Please specify a URL for the action step：请求URL不能为空 · Please configure query parameters in request：请在request中配置查询参数 · Invalid action step URL：无效的url · Please specify request method for the action step：请求方法不能为空 · Invalid request method for the action step：无效的请求方法 · Invalid condition configuration for the action step：无效的Condition配置 · Variables in the URL must be assigned values in the path parameters：url中的变量必须在路径参数中赋值 · Invalid output attributes for the action step：无效的动作输出参数 · Invalid result for the action step：无效的全局变量 · Invalid response code for the action step：无效的响应状态码 · When the repeat is enabled, the repeat stop condition must be configured for the action step：开启轮询时，必须配置轮询结束条件 · Invalid timeout for the action step：无效的超时时间 · Invalid repeat interval for the action step：无效的轮询间隔时间 · Invalid repeat stop condition for the action step：无效的轮询结束条件 · The specified action model does not exist：动作模型不存在 · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · The action step order number conflicts：步骤执行顺序存在冲突 · Failed to batch process the action steps：批量处理动作步骤失败 · Internal server error：内部错误 · You have no privilege to perform the operation：当前用户无权限执行此操作 |
|
关键字 |
ACTION_PUBLISH_ACTION_PACKAGE |
|
日志内容 |
Published action package:$1. |
|
参数解释 |
$1：动作包的ID |
|
举例 |
Published action package:64e524d2-7cd4-4d31-9ccc-1e6c620f76e7 |
|
日志说明 |
用户进行了发布动作包的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid UUID：无效的UUID · The specified action package does not exist：指定的动作包不存在 · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · The specified action package is already published：指定的动作包已发布 · No action models exist in the action package：动作包中没有任何动作模型 · No action step of the do type exists in the action package：动作包中没有do类型的动作步骤 · Invalid output attributes for the action step：无效的动作输出参数 · The required output attributes of the action model must be assigned values for action steps：动作模型的必填输出属性必须在动作步骤中赋值 · Failed to publish the action package：发布动作包失败 · Internal server error：内部错误 · You have no privilege to perform the operation：当前用户无权限执行此操作 · You cannot assign values to output attributes that do not exist in the action step：在动作步骤中不能给不存在的输出属性赋值 · The specified action package has non-compatible changes and cannot be published in compatible mode：指定的动作包已经发生非兼容变更，无法进行兼容发布 · The version number has reached the upper limit：版本号达到上限 |
|
关键字 |
ACTION_UNPUBLISH_ACTION_PACKAGE |
|
日志内容 |
Unpublished action package:$1. |
|
参数解释 |
$1：动作包的ID |
|
举例 |
Unpublished action package:64e524d2-7cd4-4d31-9ccc-1e6c620f76e7 |
|
日志说明 |
用户进行了取消发布动作包的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid UUID：无效的UUID · The specified action package does not exist：指定的动作包不存在 · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · The specified action package is unpublished：指定的动作包未发布 · The action package has been used by the process node：动作包已被应用到流程节点 · Failed to publish the action package：发布动作包失败 · Internal server error：内部错误 · You have no privilege to perform the operation：当前用户无权限执行此操作 · The built-in action packages do not support this operation：系统内置动作包不支持该操作 · An unpublished action package version already exists in the specified action package：指定动作包下已存在未发布的动作包版本 · The current action package is not of the latest version. The system only supports unpublishing the latest action package version：当前动作包不是最新的动作包版本，仅支持从最新的动作包版本开始取消发布 |
|
关键字 |
ACTION_CREATE_ACTION_PACKAGE_VERSION |
|
日志内容 |
Created an action package version:$1. |
|
参数解释 |
$1：动作包版本信息 |
|
举例 |
Created an action package version: { "package_name":"test", "package_version":"1.0.2" } |
|
日志说明 |
用户进行了取消发布动作包的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request body cannot be empty：请求体不能为空 · Please specify an action package name: 动作包名称不能为空 · Please specify an action package version: 动作包版本号不能为空 · Invalid action package version: 无效的动作包版本号 · The specified action package does not exist: 指定的动作包不存在 · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · The specified action package is unpublished：指定的动作包未发布 · An unpublished action package version already exists in the specified action package：指定动作包下已存在未发布的动作包版本 · Failed to create the action package version：创建动作包版本失败 · You have no privilege to perform the operation：当前用户无权限执行此操作 |
|
关键字 |
ACTION_EXPORT_ACTION_PACKAGE |
|
日志内容 |
Exported action packages:$1. |
|
参数解释 |
$1：动作包UUID集合 |
|
举例 |
Exported action packages:{45367387-1b26-4e06-ac07-8f719390b0a7} |
|
日志说明 |
用户进行导出动作包操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · The system supports exporting up to 1000 action packages at a time：单次最多支持导出1000个动作包 · None of the action packages to be exported exists：导出动作包均不存在 |
|
关键字 |
ACTION_IMPORT_ACTION_PACKAGE |
|
日志内容 |
Imported action packages: $1. |
|
参数解释 |
$1：文件名称 |
|
举例 |
Imported action packages: runbook_action_packages-20230818140110.zip |
|
日志说明 |
用户进行导入动作包的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · The imported file format must be ZIP：导入文件仅支持zip格式 · The imported file cannot exceed 10M：导入文件大小最大为10M · Data errors in the imported file：导入文件数据错误 · MD5 checksum errors in the imported file：导入文件MD5校验错误 · The imported file does not contain action packages：导入文件内不包含动作包 · A maximum of 1000 action package files are supported：动作包文件数量最多支持1000个 · The action package file format must be ZIP：动作包文件仅支持zip格式 · An action package file already exists with the specified name：动作包文件名称重复 · The data in the following action package file is incorrect: {name}：如下动作包文件数据错误：{动作包名称} · The following action package already has an unpublished action package version: {name}：如下动作包已经存在未发布的动作包版本：{动作包名称} · A process package has the same name as the following action package: {name}：如下动作包的名称与流程包重复：{动作包名称} |
|
关键字 |
ACTION_CREATE_PROCESS_PACKAGE |
|
日志内容 |
Created process package:$1. |
|
参数解释 |
$1：流程包信息 |
|
举例 |
Created process package: { "categoryId":"3733b9f8-c10f-456c-98b5-44dca7abde85", "createBy":"admin", "createTime":"2023-06-30 15:40:39", "description":"", "id":"93ec2ac7-1c73-4d13-aa2f-1312ab1f3136", "name":"dddfsf", "status":"unpublished", "versionX":1, "versionY":0, "versionZ":1 } |
|
日志说明 |
用户进行了创建流程包动作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request body cannot be empty：请求体不能为空 · Invalid UUID：无效的UUID · Please specify a name：名称为必选项 · The name can contain up to 64 characters, only letters, numbers and underscores (_) are supported, not support starting with number：仅支持字母、数字和下划线，不支持以数字开头，最长64位字符 · The description can contain up to 255 characters：描述最长255位字符 · The specified category does not exist：指定的分类不存在 · The specified category type does not match the package resource：指定的分类类型和包资源不匹配 · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · An action package already exists with the specified name 指定名称的动作包已经存在 · An process package already exists with the specified name：指定名称的流程包已存在 · Failed to create the process package：创建流程包失败 · You have no privilege to perform the operation：当前用户无权限执行此操作 · Insufficient license for the process package, please apply for a license：流程包License数量不足，请申请License · The name cannot start with "builtin_"：名称不支持以builtin_字符开头 |
|
关键字 |
ACTION_UPDATE_PROCESS_PACKAGE |
|
日志内容 |
Edited process package:$1. |
|
参数解释 |
$1：流程包信息 |
|
举例 |
Edited process package: { "description": "This is an example" } |
|
日志说明 |
用户进行更新流程包操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid UUID：无效的UUID · The request body cannot be empty：请求体不能为空 · The specified process package does not exist：指定的流程包不存在 · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · The specified process package is already published：指定的流程包已发布 · The description can contain up to 255 characters：描述最长255位字符 · Failed to edit the process package：更新流程包失败 · You have no privilege to perform the operation：当前用户无权限执行此操作 |
|
关键字 |
ACTION_DELETE_PROCESS_PACKAGE |
|
日志内容 |
Deleted process package:$1. |
|
参数解释 |
$1：流程包的ID |
|
举例 |
Deleted process package:0f0ce03d-d40a-4a1b-b745-cb1d9944f3ac |
|
日志说明 |
用户进行了删除流程包的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid UUID：无效的UUID · The specified process package does not exist：指定的流程包不存在 · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · The specified process package is already published：指定的流程包已发布 · Failed to delete the process package：删除流程包失败 · You have no privilege to perform the operation：当前用户无权限执行此操作 · The process package is being verified：流程包正在验证中 |
|
关键字 |
ACTION_CREATE_PROCESS_PACKAGE_PROPERTIES |
|
日志内容 |
Created process package properties:$1. |
|
参数解释 |
$1：流程包属性信息 |
|
举例 |
Created process package properties: { "inputs": [ { "name": "AAA", "description": "ARP-logswitch", "type": "string", "required": true, "sensitive": false, "constraints": [{"min_length":2}] } ], "outputs": [ { "name": "BBB", "description": "ARP-logswitch", "type": "string", "required": true, "sensitive": false, "constraints": [{"min_length":2}] } ] } |
|
日志说明 |
用户进行了创建流程输入输出属性 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid UUID：无效的UUID · The request body cannot be empty：请求体不能为空 · The specified process package does not exist：流程包不存在 · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · The specified process package is already published：指定的流程包已发布 · Input or output attributes cannot be empty at the same time：输入或输出属性不能同时为空 · An input or output attribute already exists with the specified name：指定名称的输入或输出属性已存在 · Please specify a name：名称为必选项 · The description can contain up to 255 characters：描述最长255位字符 · JSON format error： JSON格式错误 · The data type attribute’s type must be a basic data type or custom data type：数据类型的属性类型仅支持基本数据类型和除自身外的自定义数据类型 · When the type is not list, the entry_schema cannot be configured for the attribute：属性类型为基本数据类型时 不允许配置默认值和约束项 · When the type is list, the entry_schema can be configured only as a basic data type except list or a custom data type for the attribute：属性类型为list时，entry_schema只允许配置为除list外的基本数据类型和自定义数据类型 · The data type attribute’s default value can be set only for a basic data type：仅基本数据类型支持配置默认值 · When the type is not a basic data type, the default value or constraints cannot be configured for the attribute：属性类型不为基本数据类型时，不允许配置默认值和约束项 · The specified data type does not exist：指定的数据类型不存在 · The data type attribute’s type must be a basic data type：数据类型属性类型必须为基本数据类型 · The element value does not match the basic data type：值与基本数据类型不匹配 · Invalid attribute constraint item：无效的属性约束项 · Failed to create the process package attribute：流程包属性创建失败 · You have no privilege to perform the operation：当前用户无权限执行此操作 · The name can contain up to 64 characters. Only letters, numbers and underscores (_) are supported, Names starting with a number and keywords like true, false, null, not, and empty are not supported：仅支持字母、数字和下划线，不支持以数字开头且不支持true、false、null、not和empty等关键词，最长64位字符 · The data type attribute's default value can be set only for a basic data type other than list：仅支持为list以外的基本数据类型设置数据类型属性的默认值 · Duplicate attribute constraint items：存在重复的属性约束项 |
|
关键字 |
ACTION_UPDATE_PROCESS_PACKAGE_PROPERTY |
|
日志内容 |
Edited process package property:$1. |
|
参数解释 |
$1：流程包属性信息 |
|
举例 |
Edited process package property: { "id": "6e2d585b-ff32-4b61-85ba-cb987f6e4a19", "name": "CCC", "description": "ARP-logswitch", "type": "string", "required": true, "sensitive": true, "constraints": [{"min_length":2}] } |
|
日志说明 |
用户进行了修改了指定流程属性操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid UUID：无效的UUID · The request body cannot be empty：请求体不能为空 · The specified process package does not exist：流程包不存在 · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · The specified process package is already published：指定的流程包已发布 · The specified process package attribute does not exist：指定的流程属性不存在 · The description can contain up to 255 characters：描述最长255位字符 · JSON format error： JSON格式错误 · The data type attribute’s type must be a basic data type or custom data type：数据类型的属性类型仅支持基本数据类型和除自身外的自定义数据类型 · When the type is not list, the entry_schema cannot be configured for the attribute：属性类型为基本数据类型时 不允许配置默认值和约束项 · When the type is list, the entry_schema can be configured only as a basic data type except list or a custom data type for the attribute：属性类型为list时，entry_schema只允许配置为除list外的基本数据类型和自定义数据类型 · The data type attribute’s default value can be set only for a basic data type：仅基本数据类型支持配置默认值 · When the type is not a basic data type, the default value or constraints cannot be configured for the attribute：属性类型不为基本数据类型时，不允许配置默认值和约束项 · The specified data type does not exist：指定的数据类型不存在 · The data type attribute’s type must be a basic data type：数据类型属性类型必须为基本数据类型 · The element value does not match the basic data type：值与基本数据类型不匹配 · Invalid attribute constraint item：无效的属性约束项 · Failed to edit the process package attribute：流程包属性更新失败 · You have no privilege to perform the operation：当前用户无权限执行此操作 · The data type attribute's default value can be set only for a basic data type other than list：仅支持为list以外的基本数据类型设置数据类型属性的默认值 · Duplicate attribute constraint items：存在重复的属性约束项 |
|
关键字 |
ACTION_DELETE_PROCESS_PACKAGE_PROPERTY |
|
日志内容 |
Deleted process package property:$1. |
|
参数解释 |
$1：流程包属性ID |
|
举例 |
Deleted process package property: 6e2d585b-ff32-4b61-85ba-cb987f6e4a19 |
|
日志说明 |
用户进行删除指定流程属性操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid UUID：无效的UUID · The request body cannot be empty：请求体不能为空 · The specified process package does not exist：指定的流程包不存在 · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · The specified process package is already published：指定的流程包已发布 · The input attribute has been used, and cannot be deleted：输入属性被引用，不允许删除 · The output attribute has been assigned a value, and cannot be deleted：输出属性已被赋值设计，不允许删除 · Failed to delete the process package attribute：流程包属性删除失败 · You have no privilege to perform the operation：当前用户无权限执行此操作 |
|
关键字 |
ACTION_CREATE_PROCESS_NODE |
|
日志内容 |
Created process node:$1. |
|
参数解释 |
$1：流程节点信息 |
|
举例 |
Created process node: { "description":"", "id":"b704ffb6-8143-4964-ae04-b4fd3136f8d7", "instancePolicy":"default", "modelName":"net1", "name":"net1_0", "packageName":"aaa0", "packageVesion":"1.0.1", "processPackageId":"49178b7c-cbe5-4179-b836-be6b50b488cc", "type":"action" } ] } |
|
日志说明 |
用户进行了创建流程节点的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid UUID：无效的UUID · The request body cannot be empty：请求体不能为空 · The specified process package does not exist：指定的流程包不存在 · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · The specified process package is already published：指定的流程包已发布 · The process node name can contain up to 80 characters. Only letters, numbers and underscores (_) are supported, not support starting with number：仅支持字母、数字和下划线，不支持以数字开头，最长80位字符 · The description can contain up to 255 characters：描述最长255位字符 · The process node type can be set only to action or process：流程节点类型仅支持action ， process · A node already exist with the same name in the process package：同一流程包内节点不允许重复 · The specified action package does not exist：动作包不存在 · The specified action model does not exist：动作模型不存在 · The specified action package is unpublished：指定的动作包未发布 · The instantiation policy type of the node can be set only to default, fixed_num, condition, or loop：节点实例化策略类型仅支持： default、fixed_num、condition、loop · When the instantiation policy of the node is the default policy, the instantiation assignment design must be null：当节点实例化策略为默认策略时，实例化赋值设计必须为空 · Invalid instantiation assignment design for the node：无效的节点实例化赋值设计 · The instantiation assignment design of a node cannot be empty：节点实例化赋值设计不能为空 · When the instantiation policy of the node is the specified number, the constant value must be positive integer and the maximum value is 100：当节点实例化策略为指定数量时，常量值为正整数，且最大值为100 · The specified process package attribute does not exist：指定的流程包属性不存在 · The specified data type does not exist：指定的数据类型不存在 · When the instantiation policy of the node is the specified number, the referenced attribute must be of the Integer data type：节点的实例化策略为指定数量时，引用的属性必须为Integer类型 · When the instantiation policy of the node is a circular policy, the attribute referenced must be of the List data type：节点的实例化策略为循环策略时，引用的属性必须为List类型 · When the instantiation policy of the node is conditional, the instantiation assignment design cannot be constant：节点实例化策略为条件策略时，实例化赋值设计不能为常量值 · Invalid assignment policy for the input attribute：无效的输入属性赋值策略 · Invalid attribute constraint item：无效的属性约束项 · When the attribute assignment policy is an iterative value, the attribute value can be set only to iterator_index or iterator_value：属性赋值策略为迭代值时，属性值仅支持iterator_index，iterator_value · When the property is of boolean type, the constant only supports true or false：属性类型为boolean时，常量仅支持true或false · The length of the value assigned to the attribute does not meet the minimum length requirements in the constraints for the attribute：属性赋值不满足属性约束要求最小长度 · The length of the value assigned to the attribute does not meet the maximum length requirements in the constraints for the attribute：属性赋值长度大于属性约束要求最大长度 · The length of the value assigned to the attribute is less than the regular expression in the constraints for the attribute：属性赋值长度小于属性约束正则表达式 · The value assigned to the attribute is less than the minimum value in the constraints for the attribute：属性赋值小于属性约束最小值 · The value assigned to the attribute is greater than the maximum value in the constraints for the attribute:：属性赋值大于属性约束大最值 · The value assigned to the attribute is greater than the maximum value in the constraints for the attribute：属性赋值大于属性约束要求最大长度 · The value assigned to the attribute is less than the minimum value in the constraints for the attribute：属性赋值小于属性约束要求最小长度 · The range of the value assigned to the attribute is not within the value range in constraints for the attribute：属性赋值范围不在属性约束要求范围内 · The attribute value does not match attribute type：属性赋值与对应属性类型不匹配 · Attribute object type and attribute assignment object type do not match：属性对象和属性赋值对象类型不匹配 · The value assigned to the attribute is not within the valid value range for the attribute：属性赋值不在属性有效值范围内 · Failed to create the process node：流程节点创建失败 · You have no privilege to perform the operation：当前用户无权限执行此操作 · You can select the custom assignment policy only for custom attributes：仅自定义属性类型可以选择自定义赋值策略 · To assign values to a child attribute, you must set the attribute assignment policy to custom for the parent attribute：仅父属性赋值选择自定义策略时，子属性可以赋值 · When the attribute assignment policy is custom for a custom attribute, the value must be null：当自定义属性赋值策略选择自定义时，值必须是null · Invalid package version for the process node：流程节点的包版本号无效 |
|
关键字 |
ACTION_UPDATE_PROCESS_NODE |
|
日志内容 |
Edited process node:$1. |
|
参数解释 |
$1：流程节点信息 |
|
举例 |
Edited process node: { "description": " ", "id": "3cd01aa8-0fce-40ab-b41e-7509b82552ec", "instancePolicy": "default", "modelName": "audit_device", "name": "audit_device_0", "processPackageId": "49178b7c-cbe5-4179-b836-be6b50b488cc", "propertyInstancePolicy": [{ "nodeId": "3cd01aa8-0fce-40ab-b41e-7509b82552ec", "policy": "get_dependent_node_property", "propId": "0f5889aa-3dfb-4c16-939d-8e6308f2a69c", "subPropPath": "device_id", "valuePath": "getdedeeevice_0.id1" }], "type": "action" } |
|
日志说明 |
用户进行了更新流程节点的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid UUID：无效的UUID · The request body cannot be empty：请求体不能为空 · The specified process package does not exist：指定的流程包不存在 · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · The specified process package is already published：指定的流程包已发布 · The description can contain up to 255 characters：描述最长255位字符 · A node already exist with the same name in the process package：同一流程包内节点不允许重复 · The specified action package does not exist：动作包不存在 · The specified action model does not exist：动作模型不存在 · The specified action package is unpublished：指定的动作包未发布 · The instantiation policy type of the node can be set only to default, fixed_num, condition, or loop：节点实例化策略类型仅支持： default、fixed_num、condition、loop · When the instantiation policy of the node is the default policy, the instantiation assignment design must be null：当节点实例化策略为默认策略时，实例化赋值设计必须为空 · Invalid instantiation assignment design for the node：无效的节点实例化赋值设计 · The instantiation assignment design of a node cannot be empty：节点实例化赋值设计不能为空 · When the instantiation policy of the node is the specified number, the constant value must be positive integer and the maximum value is 100：当节点实例化策略为指定数量时，常量值为正整数，且最大值为100 · The specified process package attribute does not exist：指定的流程包属性不存在 · The specified data type does not exist：指定的数据类型不存在 · When the instantiation policy of the node is the specified number, the referenced attribute must be of the Integer data type：节点的实例化策略为指定数量时，引用的属性必须为Integer类型 · When the instantiation policy of the node is a circular policy, the attribute referenced must be of the List data type：节点的实例化策略为循环策略时，引用的属性必须为List类型 · When the instantiation policy of the node is conditional, the instantiation assignment design cannot be constant：节点实例化策略为条件策略时，实例化赋值设计不能为常量值 · Invalid assignment policy for the input attribute：无效的输入属性赋值策略 · Invalid attribute constraint item：无效的属性约束项 · When the attribute assignment policy is an iterative value, the attribute value can be set only to iterator_index or iterator_value：属性赋值策略为迭代值时，属性值仅支持iterator_index，iterator_value · When the property is of boolean type, the constant only supports true or false：属性类型为boolean时，常量仅支持true或false · The length of the value assigned to the attribute does not meet the minimum length requirements in the constraints for the attribute：属性赋值不满足属性约束要求最小长度 · The length of the value assigned to the attribute does not meet the maximum length requirements in the constraints for the attribute：属性赋值长度大于属性约束要求最大长度 · The length of the value assigned to the attribute is less than the regular expression in the constraints for the attribute：属性赋值长度小于属性约束正则表达式 · The value assigned to the attribute is less than the minimum value in the constraints for the attribute：属性赋值小于属性约束最小值 · The value assigned to the attribute is greater than the maximum value in the constraints for the attribute:：属性赋值大于属性约束大最值 · The value assigned to the attribute is greater than the maximum value in the constraints for the attribute：属性赋值大于属性约束要求最大长度 · The value assigned to the attribute is less than the minimum value in the constraints for the attribute：属性赋值小于属性约束要求最小长度 · The range of the value assigned to the attribute is not within the value range in constraints for the attribute：属性赋值范围不在属性约束要求范围内 · The attribute value does not match attribute type：属性赋值与对应属性类型不匹配 · Attribute object type and attribute assignment object type do not match：属性对象和属性赋值对象类型不匹配 · The value assigned to the attribute is not within the valid value range for the attribute：属性赋值不在属性有效值范围内 · Failed to edit the process node：流程节点更新失败 · You have no privilege to perform the operation：当前用户无权限执行此操作 · You can select the custom assignment policy only for custom attributes：仅自定义属性类型可以选择自定义赋值策略 · To assign values to a child attribute, you must set the attribute assignment policy to custom for the parent attribute：仅父属性赋值选择自定义策略时，子属性可以赋值 · When the attribute assignment policy is custom for a custom attribute, the value must be null：当自定义属性赋值策略选择自定义时，值必须是null |
|
关键字 |
ACTION_DELETE_PROCESS_NODE |
|
日志内容 |
Deleted process node:$1. |
|
参数解释 |
$1：流程节点信息 |
|
举例 |
Deleted process node:0f0ce03d-d40a-4a1b-b745-cb1d9944f3ac |
|
日志说明 |
用户进行了删除流程节点的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid UUID：无效的UUID · The specified process package does not exist：指定的流程包不存在 · The specified process node does not exist：流程节点不存在 · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · The specified process package is already published：指定的流程包已发布 · You cannot delete the process node, because other nodes have depended on it：流程节点被其他节点依赖，不能删除 · Failed to delete the process node：流程节点删除失败 · You have no privilege to perform the operation：当前用户无权限执行此操作 |
|
关键字 |
ACTION_CREATE_PROCESS_DEPENDENCES |
|
日志内容 |
Created process dependencese:$1. |
|
参数解释 |
$1：节点依赖信息 |
|
举例 |
Created process dependencese: { "destNodeId":"214ccb85-da3c-499f-8f5a-703b24eea1d1", "id":"7b6fb2fc-6b2f-4a22-b012-fc8fb12c7a99", "sourceNodeId":"b704ffb6-8143-4964-ae04-b4fd3136f8d7" } |
|
日志说明 |
用户进行了创建节点依赖的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid UUID：无效的UUID · The request body cannot be empty：请求体不能为空 · The specified process package does not exist：指定的流程包不存在 · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · The specified process package is already published：指定的流程包已发布 · The source and destination cannot be the same node in the node dependency：节点依赖关系中，源和目的不能为同一个节点 · The specified process node does not exist：流程节点不存在 · The specified node dependency already exists：节点依赖已存在 · There is a dependency relationship between the source node and the end of the process package, forming a circular dependency：流程包内节点依赖关系不能环形依赖 · Failed to create the node dependency：节点依赖创建失败 · You have no privilege to perform the operation：当前用户无权限执行此操作 |
|
关键字 |
ACTION_DELETE_PROCESS_DEPENDENCES |
|
日志内容 |
Deleted process dependencese:$1. |
|
参数解释 |
$1：节点依赖信息 |
|
举例 |
Deleted process dependencese:0f0ce03d-d40a-4a1b-b745-cb1d9944f3ac |
|
日志说明 |
用户进行了删除节点依赖的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid UUID：无效的UUID · The specified process package does not exist：指定的流程包不存在 · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · The specified process package is already published：指定的流程包已发布 · The specified node dependency does not exist：节点依赖不存在 · Failed to delete the node dependency：节点依赖删除失败 · You have no privilege to perform the operation：当前用户无权限执行此操作 |
|
关键字 |
ACTION_DESIGNED_PROCESS_OUTPUTS |
|
日志内容 |
Designed process outputs assignment policy:$1. |
|
参数解释 |
$1：输出属性赋值信息 |
|
举例 |
Designed process outputs assignment policy:[ { "policy":"constant", "processId":"49178b7c-cbe5-4179-b836-be6b50b488cc", "propId":"37209616-1e62-40a0-a244-b76a40e1fc98", "subPropPath":"ccc1", "valueId":"37209616-1e62-40a0-a244-b76a40e1fc98", "valuePath":"555" } ] |
|
日志说明 |
用户进行了流程输出属性赋值的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid UUID：无效的UUID · The request body cannot be empty：请求体不能为空 · The specified process package does not exist：指定流程包不存在 · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · The specified process package is already published：指定的流程包已发布 · The specified process package attribute does not exist：指定的流程包属性不存在 · Invalid assignment policy for the input attribute：无效的输入属性赋值策略 · Invalid attribute constraint item：无效的属性约束项 · Attribute object type and attribute assignment object type do not match：属性对象和属性赋值对象类型不匹配 · When the property is of boolean type, the constant only supports true or false：属性类型为boolean时，常量仅支持true或false · The value assigned to the attribute is not within the valid value range for the attribute：属性赋值不在属性有效值范围内 · The length of the value assigned to the attribute does not meet the minimum length requirements in the constraints for the attribute：属性赋值不满足属性约束要求最小长度 · The length of the value assigned to the attribute does not meet the maximum length requirements in the constraints for the attribute：属性赋值长度大于属性约束要求最大长度 · The length of the value assigned to the attribute is less than the regular expression in the constraints for the attribute：属性赋值长度小于属性约束正则表达式 · The value assigned to the attribute is less than the minimum value in the constraints for the attribute：属性赋值小于属性约束最小值 · The value assigned to the attribute is greater than the maximum value in the constraints for the attribute：属性赋值大于属性约束大最值 · The value assigned to the attribute is greater than the maximum value in the constraints for the attribute：属性赋值大于属性约束要求最大长度 · The value assigned to the attribute is less than the minimum value in the constraints for the attribute：属性赋值小于属性约束要求最小长度 · The range of the value assigned to the attribute is not within the value range in constraints for the attribute：属性赋值范围不在属性约束要求范围内 · The attribute value does not match attribute type：属性赋值与对应属性类型不匹配 · Attribute object type and attribute assignment object type do not match：属性对象和属性赋值对象类型不匹配ERROR_CREATE_OUTPUT_VALUE：流程输出属性赋值失败 · You have no privilege to perform the operation：当前用户无权限执行此操作 · You can select the custom assignment policy only for custom attributes：仅自定义属性类型可以选择自定义赋值策略 · To assign values to a child attribute, you must set the attribute assignment policy to custom for the parent attribute：仅父属性赋值选择自定义策略时，子属性可以赋值 · When the attribute assignment policy is custom for a custom attribute, the value must be null：当自定义属性赋值策略选择自定义时，值必须是null |
|
关键字 |
ACTION_PUBLISH_PROCESS_PACKAGE |
|
日志内容 |
Published process package:$1. |
|
参数解释 |
$1：流程包的ID |
|
举例 |
Published process package:64e524d2-7cd4-4d31-9ccc-1e6c620f76e7 |
|
日志说明 |
用户进行了发布流程包的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid UUID：无效的UUID · The specified process package does not exist：指定的流程包不存在 · The specified process package is already published：指定的流程包已发布 · No process node exists in the specified process package：指定的流程包中没有流程节点 · No assignment policy is designed for required input attribute '%s' for node '%s'：节点必填输入属性未做赋值设计 · No assignment policy is designed for required output attribute '%s' of the process package：流程包必填输出属性未做赋值设计 · Failed to publish the process package：发布流程包失败 · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · You have no privilege to perform the operation：当前用户无权限执行此操作 · Internal server error：内部错误 · The process package is being verified：流程包正在验证中 · The specified process package has non-compatible changes and cannot be published in compatible mode：指定的流程包已经发生非兼容变更，无法进行兼容发布 · The version number has reached the upper limit：版本号达到上限 |
|
关键字 |
ACTION_UNPUBLISH_ACTION_PACKAGE |
|
日志内容 |
Unpublished process package:$1. |
|
参数解释 |
$1：流程包的ID |
|
举例 |
Unpublished process package:64e524d2-7cd4-4d31-9ccc-1e6c620f76e7 |
|
日志说明 |
用户进行了取消发布流程包的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid UUID：无效的UUID · The specified process package does not exist：指定的流程包不存在 · The specified process package is unpublished：指定的流程包未发布 · A process instance has been created for the specified process package：指定的流程包已经创建流程实例 · The specified process package has been used by another process package：指定的流程包已被其他流程包使用 · The specified process package has been used by custom APIs：指定的流程包已被自定义接口使用 · Failed to unpublish the process package：取消发布流程包失败 · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · You have no privilege to perform the operation：当前用户无权限执行此操作 · Internal server error：内部错误 · An unpublished process package version already exists in the specified process package：指定流程包下已存在未发布的流程包版本 · The current process package is not of the latest version. The system only supports unpublishing the latest process package version：当前流程包不是最新的流程包版本，仅支持从最新的流程包版本开始取消发布 |
|
关键字 |
ACTION_CREATE_PROCESS_PACKAGE_VERSION |
|
日志内容 |
Created a process package version:$1. |
|
参数解释 |
$1：动作包版本信息 |
|
举例 |
Created an process package version: { "package_name":"test", "package_version":"1.0.2" } |
|
日志说明 |
用户进行了取消发布动作包的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request body cannot be empty：请求体不能为空 · Please specify a process package name：流程包名称不能为空 · Please specify a process package version：流程包版本号不能为空 · Invalid process package version：无效的流程包版本号 · The specified process package does not exist：指定的流程包不存在 · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · The specified process package is unpublished：指定的流程包未发 · An unpublished process package version already exists in the specified process package：指定流程包下已存在未发布的流程包版本 · Failed to create the process package version：创建流程包版本失败 · You have no privilege to perform the operation：当前用户无权限执行此操作 |
|
关键字 |
ACTION_EXPORT_PROCESS_PACKAGE |
|
日志内容 |
Exported process packages:$1. |
|
参数解释 |
$1：流程包UUID集合 |
|
举例 |
Exported process packages:{45367387-1b26-4e06-ac07-8f719390b0a7} |
|
日志说明 |
用户进行导出流程包的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · The system supports exporting up to 1000 process packages at a time：单次最多支持导出1000个流程包 · None of the process packages to be exported exists：导出流程包均不存在 · The following process package is in dryrun state and cannot be exported: {name}：如下流程包状态为dryrun，不支持导出：{流程包名称} |
|
关键字 |
ACTION_IMPORT_PROCESS_PACKAGE |
|
日志内容 |
Imported process packages: $1. |
|
参数解释 |
$1：文件名称 |
|
举例 |
Imported process packages: runbook_process_packages-20230918103459.zip |
|
日志说明 |
用户进行导入流程包的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · The imported file format must be ZIP：导入文件仅支持zip格式 · The imported file cannot exceed 10M：导入文件大小最大为10M · Data errors in the imported file：导入文件数据错误 · MD5 checksum errors in the imported file：导入文件MD5校验错误 · The imported file does not contain process packages：导入文件内不包含流程包 · A maximum of 1000 process package files are supported：流程包文件数量最多支持1000个 · The process package file format must be ZIP：流程包文件仅支持zip格式 · A process package file already exists with the specified name：流程包文件名称重复 · The data in the following process package file is incorrect: {name}：如下流程包文件数据错误：{流程包名称} · The following process package has an unpublished process package version: {name}：如下流程包已经存在未发布的的流程包版本：{流程包名称} · An action package has the same name as the following process package: {name}：如下流程包的名称与动作包重复：{流程包名称} · The dependent action package does not exist: {name(version)}：依赖的动作包不存在：{动作包名称(版本号)} · The dependent process package does not exist: {name(version)}：依赖的流程包不存在：{流程包名称(版本号)} |
|
关键字 |
ACTION_COPY_PROCESS_PACKAGE |
|
日志内容 |
Copied a process package:$1. |
|
参数解释 |
$1：流程包信息 |
|
举例 |
Copied a process package: { "categoryId":"3733b9f8-c10f-456c-98b5-44dca7abde85", "createBy":"admin", "createTime":"2023-06-30 15:40:39", "description":"", "id":"93ec2ac7-1c73-4d13-aa2f-1312ab1f3136", "name":"dddfsf", "status":"unpublished", "versionX":1, "versionY":0, "versionZ":1 } |
|
日志说明 |
用户进行了复制流程包的动作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request body cannot be empty：请求体不能为空 · Invalid UUID：无效的UUID · Please specify a name：名称为必选项 · The name can contain up to 64 characters, only letters, numbers and underscores (_) are supported, not support starting with number：仅支持字母、数字和下划线，不支持以数字开头，最长64位字符 · The description can contain up to 255 characters：描述最长255位字符 · The specified category does not exist：指定的分类不存在 · The specified category type does not match the package resource：指定的分类类型和包资源不匹配 · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · An action package already exists with the specified name：指定名称的动作包已经存在 · An process package already exists with the specified name：指定名称的流程包已存在 · Failed to create the process package：创建流程包失败 · You have no privilege to perform the operation：当前用户无权限执行此操作 · Insufficient license for the process package, please apply for a license：流程包License数量不足，请申请License · The name cannot start with "builtin_"：名称不支持以builtin_字符开头 · The origin_package_name and origin_package_version fields must be both specified：origin_package_name和origin_package_version字段必须同时存在 |
|
关键字 |
ACTION_UPDATE_PROCESS_PACKAGE_STATUS |
|
日志内容 |
Changed the state of a process package:$1 |
|
参数解释 |
$1：流程包UUID |
|
举例 |
Changed the state of a process package:45367387-1b26-4e06-ac07-8f719390b0a7 |
|
日志说明 |
用户进行更新流程包状态的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid UUID：无效的UUID · The specified process package does not exist：指定的流程包不存在 · Please specify the status field for the process package：流程包状态字段不能为空 · You can change the state only to unpublished or dryrun for the process package：程包状态只允许修改为unpublished或dryrun · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · Failed to publish the process package：发布流程包失败 · A process instance has been created for the specified process package：指定的流程包已经创建流程实例 · You have no privilege to perform the operation：当前用户无权限执行此操作 · Failed to change the state of the process package：修改流程包状态失败 · Internal server error：内部错误 |
|
关键字 |
ACTION_CREATE_PROCESS_PACKAGE_CASE |
|
日志内容 |
Added a test case for a process package:$1. |
|
参数解释 |
$1：流程包测试用例信息 |
|
举例 |
Added a test case for a process package: { "createBy":"admin", "createTime":"2023-09-16 11:38:31", "id":"c6ce3494-1251-48c9-94b0-dde907e565aa", "inputs":{ "name":"测试用例" }, "name":"测试用例-01", "nodeOutputs":{ "actionModel_0":{ "hostInput":{ "id":"e9501574-431e-4017-8c09-695b290f5ffd", "name":"hostname" } } }, "processPackageId":"7566b597-e453-4050-bb22-950fbe4b6ac2" } |
|
日志说明 |
用户进行新增流程包测试用例操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request body cannot be empty：请求体不能为空 · Invalid UUID：无效的UUID · Please specify a name：名称为必选项 · Invalid name. The name can contain up to 64 characters and supports only Chinese characters, letters, digits, underscores (_), and hyphens (-)：无效的名称，只支持中文、字母、数字、下划线和连字符，最长64位字符 · Invalid process input, which must be a JSON：无效的流程输入，必须为JSON形式 · Invalid node output, which must be a JSON：无效的节点输出，必须为JSON形式 · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · A test case already exists with the specified name for the specified process package：指定的流程包下测试用例名称已存在 · The specified process package does not exist：指定的流程包不存在 · You cannot operate the test case, because the current state of the process package is not dryrun：流程包状态不支持操作测试用例 · Failed to create the test case：创建测试用例失败 · Internal server error：内部错误 |
|
关键字 |
ACTION_UPDATE_PROCESS_PACKAGE_CASE |
|
日志内容 |
Edited a test case of a process package: $1 |
|
参数解释 |
$1：流程包测试用例信息 |
|
举例 |
Edited a test case of a process package: { "inputs":{ "name":"测试用例" }, "nodeOutputs":{ "actionModel_0":{ "hostInput":{ "id":"e9501574-431e-4017-8c09-695b290f5ffd", "name":"hostname" } } } } |
|
日志说明 |
用户进行更新流程包测试用例操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request body cannot be empty：请求体不能为空 · Invalid UUID：无效的UUID · Invalid name. The name can contain up to 64 characters and supports only Chinese characters, letters, digits, underscores (_), and hyphens (-)：无效的名称，只支持中文、字母、数字、下划线和连字符，最长64位字符 · Invalid process input, which must be a JSON：无效的流程输入，必须为JSON形式 · Invalid node output, which must be a JSON：无效的节点输出，必须为JSON形式 · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · A test case already exists with the specified name for the specified process package：指定的流程包下测试用例名称已存在 · The specified process package does not exist：指定的流程包不存在 · The specified test case does not exist：指定测试用例不存在 · You cannot operate the test case, because the current state of the process package is not dryrun：流程包状态不支持操作测试用例 · Failed to edit the test case：修改测试用例失败 · The test case is in use：测试用例正在被使用 · Internal server error：内部错误 |
|
关键字 |
ACTION_DELETE_PROCESS_PACKAGE_CASE |
|
日志内容 |
Deleted a test case of a process package: $1 |
|
参数解释 |
$1：流程包测试用例UUID |
|
举例 |
Deleted a test case of a process package: 45367387-1b26-4e06-ac07-8f719390b0a7 |
|
日志说明 |
用户进行删除流程包测试用例操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid UUID：无效的UUID · The specified process instance does not exist：指定的流程实例不存在 · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · The specified process package does not exist：指定的流程包不存在 · You cannot operate the test case, because the current state of the process package is not dryrun：流程包状态不支持操作测试用例 · The specified test case does not exist：指定测试用例不存在 · The test case is in use：测试用例正在被使用 · Failed to delete the test case：删除测试用例失败 · Internal server error：内部错误 |
|
关键字 |
ACTION_CREATE_PROCESS_PACKAGE_CASE_INSTANCE |
|
日志内容 |
Created a test case debugging instance for a process package:$1. |
|
参数解释 |
$1：流程包测试用例UUID |
|
举例 |
Created a test case debugging instance for a process package:45367387-1b26-4e06-ac07-8f719390b0a7 |
|
日志说明 |
用户进行创建流程包测试用例调试实例操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid UUID：无效的UUID · The specified process package does not exist：指定的流程包不存在 · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · You cannot operate the test case, because the current state of the process package is not dryrun：流程包状态不支持操作测试用例 · The specified test case does not exist：指定测试用例不存在 · The test case is in use：测试用例正在被使用 · You have no privilege to perform the operation：当前用户无权限执行此操作 · Internal server error：内部错误 |
|
关键字 |
ACTION_EXEC_PROCESS_PACKAGE_CASE_INSTANCE_TASK |
|
日志内容 |
Executed a test case debugging instance task for a process package: $1 |
|
参数解释 |
$1：测试用例流程实例任务ID |
|
举例 |
Executed a test case debugging instance task for a process package: NODE_actionModel_0:8567c89a-5442-11ee-82ab-2a4317d13aef |
|
日志说明 |
用户进行更新数据类型操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid UUID：无效的UUID · You cannot operate the process instance, because it is not a process instance of a test case：非测试用例的流程实例，不允许操作 · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · The specified task does not exist：指定的节点实例任务不存在 · The specified task has been processed：指定任务已被处理 · Failed to execute the process instance task：执行流程实例任务失败 · You have no privilege to perform the operation：当前用户无权限执行此操作 · Internal server error：内部错误 |
|
关键字 |
ACTION_ROLLBACK_PROCESS_PACKAGE_CASE_INSTANCE_TASK |
|
日志内容 |
Rolled back a test case debugging instance task for a process package: $1 |
|
参数解释 |
$1：测试用例流程实例任务ID |
|
举例 |
Rolled back a test case debugging instance task for a process package: NODE_actionModel_0:8567c89a-5442-11ee-82ab-2a4317d13aef |
|
日志说明 |
用户进行更新数据类型的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid UUID：无效的UUID · You cannot operate the process instance, because it is not a process instance of a test case：非测试用例的流程实例，不允许操作 · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · The specified task does not exist：指定的节点实例任务不存在 · You cannot roll back a node instance in the current state：节点实例状态不允许回滚操作 · The process instance cannot be rolled back in the current state：指定的流程实例不支持回滚操作 · You have no privilege to perform the operation：当前用户无权限执行此操作 · Internal server error：内部错误 |
|
关键字 |
ACTION_DELETE_PROCESS_PACKAGE_CASE_INSTANCE |
|
日志内容 |
Deleted a test case debugging instance for a process package:$1. |
|
参数解释 |
$1：调试流程实例UUID |
|
举例 |
Deleted a test case debugging instance for a process package:45367387-1b26-4e06-ac07-8f719390b0a7 |
|
日志说明 |
用户进行删除流程包测试用例调试实例的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid UUID：无效的UUID · The specified process instance does not exist：指定的流程实例不存在 · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · You cannot operate the process instance, because it is not a process instance of a test case：非测试用例的流程实例，不允许操作 · The process instance cannot be deleted in the current state：指定的流程实例不支持删除操作 · Failed to delete the process instance：删除流程实例失败 · You have no privilege to perform the operation：当前用户无权限执行此操作 · Internal server error：内部错误 |
|
关键字 |
ACTION_CREATE_CUSTOM_API |
|
日志内容 |
Created custom api:$1. |
|
参数解释 |
$1：自定义接口配置信息 |
|
举例 |
Created custom api: { "createBy": "admin", "createTime": "2023-05-04 18:45:45", "description": "", "id": "0fd7c021-308f-4a54-b104-a0491e423d12", "method": "DELETE", "name": "zzzz", "processPackageName": "zmr_login_p", "processPackageVersion": "1.0", "process_package_id": "3f439115-6614-4b90-8350-1a0b9d16fe9b", "uri": "/a/a/a" } |
|
日志说明 |
用户进行了创建自定义接口配置操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request body cannot be empty：请求体不能为空 · Please specify a name：名称不能为空 · The name contains a maximum of 64 characters, including Chinese characters, letters, digits, underscores (_), and hyphens (-)：名称支持中文，字母，数字，下划线，连字符，最长64位 · The description can contain up to 255 characters：描述最长255位字符 · Invalid process package ID：流程包ID不合法 · Please specify a URI：自定义接口URI不能为空 · A custom API already exists with the specified URI and method：指定URI+method的自定义接口已经存在 · Please specify a request method：请求方法不能为空 · The custom API URI contains a maximum of 512 characters：自定义接口URI最长512位字符 · Invalid request method. Only POST, PUT, GET, DELETE, and PATCH are supported, case-insensitive：无效的请求方法，仅支持POST, PUT, GET, DELETE和PATCH · The custom API URI cannot overlap with the existing gateway routes：自定义接口URI和已存在的网关路由路径冲突 · Failed to create the custom API：创建自定义北向接口失败 · A custom API already exists with the specified name：指定名称的自定义接口已经存在 · The specified process package does not exist：指定的流程包不存在 · The specified process package is unpublished：指定的流程包未发布 · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · You have no privilege to perform the operation：当前用户无权限执行此操作 · Internal server error：内部错误 · A custom API URI must start with a slash (/), and supports only letters, digits, underscores (_), hyphens (-), and colons (:) between path level separators：自定义接口URI必须以/开头，路径层级间仅支持大小写字母、数字、下划线、连字符和冒号 · The process package ID and the combination of process package name and process package version cannot be assigned values simultaneously：流程包ID和流程包名称、流程包版本号的组合不能同时赋值 · Please specify a process package：请指定一个流程包 · Please specify a process package name：流程包名称不能为空 · Please specify a process package version：流程包版本号不能为空 · Invalid process package version：无效的流程包版本号 |
|
关键字 |
ACTION_UPDATE_CUSTOM_API |
|
日志内容 |
Edited custom api:$1. |
|
参数解释 |
$1：数据类型信息 |
|
举例 |
Edited custom api: { "createBy": "admin", "createTime": "2023-05-04 18:45:45", "description": "222", "id": "ec448bb4-ea49-496d-9c78-73ff062d1f66", "method": "DELETE", "name": "delete-test", "processPackageName": "dsw", "processPackageVersion": "1.0", "process_package_id": "60087806-0082-4ece-93e9-62d5db0292b8", "updateBy": "admin", "updateTime": "2023-05-06 18:45:45", "uri": "/dataType" } |
|
日志说明 |
用户进行更新自定义接口配置操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid UUID：无效的UUID · The specified custom API does not exist：指定的自定义接口不存在 · The request body cannot be empty：请求体不能为空 · Please specify a name：名称不能为空 · The name contains a maximum of 64 characters, including Chinese characters, letters, digits, underscores (_), and hyphens (-)：名称支持中文，字母，数字，下划线，连字符，最长64位 · The description can contain up to 255 characters：描述最长255位字符 · Invalid process package ID：流程包ID不合法 · A custom API already exists with the specified name：指定名称的自定义接口已经存在 · The specified process package does not exist：指定的流程包不存在 · The specified process package is unpublished：指定的流程包未发布 · Failed to edit the custom API：修改自定义北向接口失败 · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · You have no privilege to perform the operation：当前用户无权限执行此操作 · Internal server error：内部错误 · The process package ID and the combination of process package name and process package version cannot be assigned values simultaneously：流程包ID和流程包名称、流程包版本号的组合不能同时赋值 · Please specify a process package：请指定一个流程包 · Please specify a process package name：流程包名称不能为空 · Please specify a process package version：流程包版本号不能为空 · Invalid process package version：无效的流程包版本号 |
|
关键字 |
ACTION_DELETED_CUSTOM_API |
|
日志内容 |
Deleted custom api:$1. |
|
参数解释 |
$1：自定义接口配置UUID |
|
举例 |
Deleted custom api:0fd7c021-308f-4a54-b104-a0491e423d12 |
|
日志说明 |
用户进行了删除自定义接口配置的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid UUID：无效的UUID · The specified custom API does not exist：指定的自定义接口不存在 · Failed to delete the custom API：删除自定义北向接口失败 · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · You have no privilege to perform the operation：当前用户无权限执行此操作 · Internal server error：内部错误 |
|
关键字 |
ACTION_EXECUTE_CUSTOM_API |
|
日志内容 |
Executed custom api:$1. |
|
参数解释 |
$1：自定义接口配置信息 |
|
举例 |
Executed custom api: { "createBy": "admin", "createTime": "2023-05-04 18:45:45", "description": "登录接口", "id": "ad4fa2da-311f-4afd-b96b-cb0deb1880e2", "method": "POST", "name": "zmr_login_interface", "processPackageName": "zmr_login_p", "processPackageVersion": "1.0.1", "process_package_id": "3f439115-6614-4b90-8350-1a0b9d16fe9b", "uri": "/api/rest/securityManagement/v1/oauth/token" } |
|
日志说明 |
用户进行了执行自定义接口的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The specified custom API does not exist：指定的自定义接口不存在 · Failed to execute the custom API：执行自定义北向接口失败 · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · You have no privilege to perform the operation：当前用户无权限执行此操作 · Internal server error：内部错误 |
|
关键字 |
ACTION_CREATED_PROCESS_INSTANCE |
|
日志内容 |
Created process instance:$1. |
|
参数解释 |
$1：流程实例信息 |
|
举例 |
Created process instance: { "autoRollback": false, "createTime": "2023-05-04 18:45:45", "id": "5f93d27d-4780-463e-a01d-90c0c4d5e22d", "inputs": "{\"password\":\"G6BJcjOmCBVvfUIdH9p6gg==\",\"userName\":\"admin\"}", "name": "zmr-login-050519", "process": 0, "processPackageId": "3f439115-6614-4b90-8350-1a0b9d16fe9b", "processPackageName": "zmr_login_p", "processPackageVersion": "1.0.1", "status": "init", "type": "root" } |
|
日志说明 |
用户进行了创建数据类型动作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request body cannot be empty：请求体不能为空 · Please specify a name for the process instance：流程实例名称不能为空 · Please specify a process package name：流程包名称不能为空 · The name can contain up to 64 characters, only letters, numbers, underscores (_) are supported, and hyphens (-)：无效的名称，仅支持字母、数字、下划线，连字符，最长64位字符 · A process instance already exists with the specified name：指定名称的流程实例已存在 · The specified process package does not exist：指定的流程包不存在 · The specified process package is unpublished：指定的流程包未发布 · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · You have no privilege to perform the operation：当前用户无权限执行此操作 · Internal server error：内部错误 |
|
关键字 |
ACTION_ROLLBACK_PROCESS_INSTANCE |
|
日志内容 |
Executed rollback process instance: $1. Rollbacked process instance:$1 |
|
参数解释 |
$1：流程实例UUID |
|
举例 |
Executed rollback process instance:d5e358b3-4355-42a3-8de7-8af95f3cc62e Rollbacked process instance:d5e358b3-4355-42a3-8de7-8af95f3cc62e |
|
日志说明 |
用户进行更新数据类型操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid UUID：无效的UUID · The specified process instance does not exist：指定的流程实例不存在 · The process instance cannot be rolled back in the current state：指定的流程实例不支持回滚操作 · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · To roll back this process instance, please make sure you have rolled back all process instances executed later than it, starting from the one being executed most recently：若要回滚此流程实例，请确保您已回滚所有晚于此实例执行的流程实例，回滚时请从最近执行的流程实例开始 · Failed to execute process instance rollback：执行回滚流程实例失败 · Failed to roll back the process instance：回滚流程实例失败 · You have no privilege to perform the operation：当前用户无权限执行此操作 · Internal server error：内部错误 |
|
关键字 |
ACTION_RETRY_PROCESS_INSTANCE |
|
日志内容 |
Retried process instance:$1. |
|
参数解释 |
$1：流程实例UUID |
|
举例 |
Retried process instance:5e28c146-3a2d-45b5-a57b-0b6bf531be0e |
|
日志说明 |
用户进行了删除数据类型的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid UUID：无效的UUID · The specified process instance does not exist：指定的流程实例不存在 · The process instance cannot be retried in the current state：指定的流程实例不支持进行重试操作 · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · You have no privilege to perform the operation：当前用户无权限执行此操作 · Internal server error：内部错误 |
|
关键字 |
ACTION_EXEC_PROCESS_INSTANCE |
|
日志内容 |
Executed process instance:$1. |
|
参数解释 |
$1：流程实例UUID |
|
举例 |
Executed process instance:d5e358b3-4355-42a3-8de7-8af95f3cc62e |
|
日志说明 |
用户进行了创建数据类型动作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid UUID：无效的UUID · The specified process instance does not exist：指定的流程实例不存在 · The process instance cannot be republished in the current state：指定的流程实例不支持进行重新发放操作 · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · You have no privilege to perform the operation：当前用户无权限执行此操作 · Internal server error：内部错误 |
|
关键字 |
ACTION_DELETED_PROCESS_INSTANCE |
|
日志内容 |
Deleted process instance:$1. |
|
参数解释 |
$1：流程实例UUID |
|
举例 |
Deleted process instance:45367387-1b26-4e06-ac07-8f719390b0a7 |
|
日志说明 |
用户进行更新数据类型操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid UUID：无效的UUID · The specified process instance does not exist：指定的流程实例不存在 · Another user is processing the resource. Please try again later：当前资源正在被操作，请稍后再试 · The process instance cannot be deleted in the current state：指定的流程实例不支持删除操作 · Failed to delete the process instance：删除流程实例失败 · You have no privilege to perform the operation：当前用户无权限执行此操作 · Internal server error：内部错误 |
本节介绍SEERENGINE模块输出的操作日志信息。
|
关键字 |
CREATE_CAR_PROFILE_OP |
|
日志内容 |
Created rate limit template: $1 |
|
参数解释 |
$1：限速模板的信息 |
|
举例 |
Created rate limit template: ID: [dfbce4db-8e72-4fd4-a659-f6889c709e15] Name: [addTest ] Description: [111] CIR: [64] CBS: [512] PIR: [80] EBS: [512] Status: [false]. |
|
日志说明 |
用户进行了创建限速模板的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service does not exist：服务不存在 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · The name is required and cannot exceed 255 characters：名称必选并且长度不能超过255个字符 · The description cannot exceed 255 characters：描述信息字段最长255个字符 · The CIR cannot be null：承诺信息速率不允许为空 · If the EBS is not null, the CBS and PIR are required：当超出突发尺寸不为空时，承诺突发尺寸和峰值信息速率必须不为空 · The CIR must be a multiple of 8 and in the range of 8 to 4294967288：承诺信息速率的取值范围为8～4294967288，且必须为8的倍数 · The CBS must be a multiple of 512 and in the range of 512 to 256000000：承诺突发尺寸的取值范围为512～256000000，且必须为512的倍数 · The PIR must be a multiple of 8 and in the range of 8 to 4294967288. Its value must be smaller than the CIR：峰值信息速率的取值范围为8～4294967288，必须为8的倍数，且取值必须小于承诺信息速率 · The EBS must be a multiple of 512 and in the range or 0 to 256000000：承诺突发尺寸的取值范围为0～256000000，且必须为512的倍数 · Failed to add the configuration item：添加配置项失败 · You have no privilege to perform this operation：用户无权限执行此操作 · The rate limit profile with the specified name in same tenant already exists：相同租户下，指定名称的限速模板已存在 |
|
关键字 |
UPDATE_CAR_PROFILE_OP |
|
日志内容 |
Updated rate limit template: $1. |
|
参数解释 |
$1：限速模板的信息 |
|
举例 |
Updated rate limit template: ID: [dfbce4db-8e72-4fd4-a659-f6889c709e15] Name: [modTest] Description: [01]↵ CIR: [64]↵ CBS: [512] PIR: [80] EBS : [512] Status: [false]. |
|
日志说明 |
用户进行了修改限速模板的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service does not exist：服务不存在 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · The configuration item does not exist：配置项不存在 · The rate limit profile ID cannot be edited：限速模板的ID不支持修改 · The rate limit profile name cannot be edited：限速模板的名称不支持修改 · The CIR cannot be modified：承诺信息速率不允许修改 · The CBS cannot be modified：承诺突发尺寸不允许修改 · The PIR cannot be modified：峰值信息速率不允许修改 · The EBS cannot be modified：超出突发尺寸不允许修改 · The status field cannot be modified：状态字段不允许修改 · The description cannot exceed 255 characters：描述信息字段最长255个字符 · Failed to modify the configuration item：修改配置项失败 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_CAR_PROFILE_OP |
|
日志内容 |
Deleted rate limit template $1. |
|
参数解释 |
$1：限速模板的名称 |
|
举例 |
Deleted rate limit template test |
|
日志说明 |
用户进行了删除限速模板的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service does not exist：服务不存在 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · The configuration item does not exist：配置项不存在 · The rate limit profile is used：限速模板已经被使用 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_MIRROR_DESTINATION_PROFILE_OP |
|
日志内容 |
Created mirroring destination template: $1 |
|
参数解释 |
$1：镜像目的模板的信息 |
|
举例 |
Created mirroring destination template: ID: [a36f1d47-3cc5-4b1c-ad1b-64a07fc6ad66] Name: [addMirrorTemplate] Description: [描述111] Destination vPort: [94575fea-604d-4c18-8f65-3b5c3871384a] Destination IPv4 addresses: [18.16.15.16, 16.15.16.15, 192.168.16.15] Cloud region name:[aaa] VRF: [111] Tenant ID: [null] VXLAN ID: [null] VXLAN ID Source: [94575fea-604d-4c18-8f65-3b5c3871384a] |
|
日志说明 |
用户进行了创建镜像目的模板的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service does not exist：服务不存在 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · The name is required and cannot exceed 255 characters：名称必选并且长度不能超过255个字符 · Failed to add the configuration item：添加配置项失败 · You have no privilege to perform this operation：用户无权限执行此操作 · Invalid vrf：无效的VRF |
|
关键字 |
UPDATE_MIRROR_DESTINATION_PROFILE_OP |
|
日志内容 |
Updated mirroring destination template: $1 |
|
参数解释 |
$1：镜像目的模板的信息 |
|
举例 |
Updated mirroring destination template: ID: [a36f1d47-3cc5-4b1c-ad1b-64a07fc6ad66] Name: [test] Description: [111] Destination vPort: [94575fea-604d-4c18-8f65-3b5c3871384a] Destination IPv4 addresses: [18.16.15.16, 16.15.16.15, 192.168.16.15] Cloud region name:[aaa] VRF: [111] Tenant ID: [null] VXLAN ID: [null] VXLAN ID Source: [94575fea-604d-4c18-8f65-3b5c3871384a] |
|
日志说明 |
用户进行了修改镜像目的模板的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service does not exist：服务不存在 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · The configuration item does not exist：配置项不存在 · The name is required and cannot exceed 255 characters：名称必选并且长度不能超过255个字符 · Failed to modify the configuration item：修改配置项失败 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_MIRROR_DESTINATION_PROFILE_OP |
|
日志内容 |
Deleted mirroring destination template $1. |
|
参数解释 |
$1：镜像目的模板的名称 |
|
举例 |
Deleted mirroring destination template test. |
|
日志说明 |
用户进行了删除镜像目的模板的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service does not exist：服务不存在 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · The configuration item does not exist：配置项不存在 · The specified mirroring destination profile is used：指定的镜像目的模板已经被使用 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_CLASSIFIER_OP |
|
日志内容 |
Created classifier: $1 |
|
参数解释 |
$1：分类器的信息 |
|
举例 |
Created classifier: ID: [76d78185-3144-410a-96c1-3fe212c5a2de] Name : [addTest] Description: [01] ServiceVlanId: [23] Dscp: [2] Dot1p: [3] Status: [false] ACL rules: { Rule ID: Id[value=aa25f6d9-2354-4e74-9679-a905376b3d29] Rule name: [ruleName02] Rule protocol: [UDP] Rule source IP: [16.16.16.16/24] Rule destination IP: [16.16.16.188/24] Rule source Port: [5] Rule destination port: [4] Rule IP type: [IPV4] Rule VRF: [7of0ho1hqt9scbseq4vhqh8g91] } { Rule ID: Id[value=30f40435-55fb-490f-a650-9ee3cd5ae5e1] Rule name: [ruleName01] Rule protocol: [TCP] Rule source IP: [16.15.16.16/24] Rule destination IP: [15.16.16.16/24] Rule source port: [5] Rule destination port: [6] Rule IP type: [IPV4] Rule VRF: [5oc54lmbue9arr9ecop71hqdln] } |
|
日志说明 |
用户进行了创建分类器的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service does not exist：服务不存在 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · The name is required and cannot exceed 255 characters：名称必选并且长度不能超过255个字符 · The description cannot exceed 255 characters：描述信息字段最长255个字符 · Failed to add the configuration item：添加配置项失败 · You have no privilege to perform this operation：用户无权限执行此操作 · The classifier with the specified name in same tenant already exists：相同租户下，指定名称的分类器已存在 |
|
关键字 |
UPDATE_CLASSIFIER_OP |
|
日志内容 |
Updated classifier: $1. |
|
参数解释 |
$1：分类器的信息 |
|
举例 |
Updated classifier: ID: [76d78185-3144-410a-96c1-3fe212c5a2de] Name: [modTest01] Description: [描述111] ServiceVlanId: [23] Dscp: [2] Dot1p: [3] Status: [false] ACL rules: { Rule ID: Id[value=aa25f6d9-2354-4e74-9679-a905376b3d29] Rule name: [ruleName02] Rule protocol: [UDP] Rule source IP: [16.16.16.16/24] Rule destination IP: [16.16.16.188/24] Rule source port: [5] Rule destination port: [4] Rule IP type: [IPV4] Rule VRF: [7of0ho1hqt9scbseq4vhqh8g91] } |
|
日志说明 |
用户进行了修改分类器的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service does not exist：服务不存在 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · The configuration item does not exist：配置项不存在 · The name is required and cannot exceed 255 characters：名称必选并且长度不能超过255个字符 · The description cannot exceed 255 characters：描述信息字段最长255个字符 · Failed to modify the configuration item：修改配置项失败 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · The classifier with the specified name in same tenant already exists：相同租户下，指定名称的分类器已存在 |
|
关键字 |
DELETE_CLASSIFIER_OP |
|
日志内容 |
Deleted classifier $1. |
|
参数解释 |
$1：分类器的名称 |
|
举例 |
Deleted classifier test. |
|
日志说明 |
用户进行了删除分类器的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service does not exist：服务不存在 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · The configuration item does not exist：配置项不存在 · The specified classifier is used：指定的分类器已经被使用 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_FLOW_POLICY_OP |
|
日志内容 |
Created flow policy: $1. |
|
参数解释 |
$1：流量策略的信息 |
|
举例 |
Created flow policy: ID: [e075ca4c-938d-4d57-abb1-1ba2ccde5981] Name: [策略名称11] Dot1p: [233] Classifier ID: [060455ab-61da-4313-b370-d67c2da33b71] Mirroring destination profile ID: [1942b945-756a-4c5d-b1dc-bab33d1328cc] Rate limit profile ID: [52d32dab-19fc-4f7c-a2ab-e52218ef7ac3] |
|
日志说明 |
用户进行了创建流量策略的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service does not exist：服务不存在 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · The name is required and cannot exceed 255 characters：名称必选并且长度不能超过255个字符 · Failed to add the configuration item：添加配置项失败 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_FLOW_POLICY_OP |
|
日志内容 |
Updated flow policy: $1. |
|
参数解释 |
$1：流量策略的信息 |
|
举例 |
Updated flow policy: ID: [e075ca4c-938d-4d57-abb1-1ba2ccde5981] Name: [11] Dot1p: [233] Classifier ID: [060455ab-61da-4313-b370-d67c2da33b71] Mirroring destination profile ID: [1942b945-756a-4c5d-b1dc-bab33d1328cc] Rate limit profile ID: [52d32dab-19fc-4f7c-a2ab-e52218ef7ac3] |
|
日志说明 |
用户进行了修改流量策略的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service does not exist：服务不存在 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · The configuration item does not exist：配置项不存在 · The name is required and cannot exceed 255 characters：名称必选并且长度不能超过255个字符 · Failed to modify the configuration item：修改配置项失败 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_FLOW_POLICY_OP |
|
日志内容 |
Deleted flow policy $1. |
|
参数解释 |
$1：流量策略的名称 |
|
举例 |
Deleted flow policy 11. |
|
日志说明 |
用户进行了删除流量策略的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service does not exist：服务不存在 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · The configuration item does not exist：配置项不存在 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_PHYSICAL_PORT_POLICY_OP |
|
日志内容 |
Created physical port policy: $1. |
|
参数解释 |
$1：物理端口策略的信息 |
|
举例 |
Created physical port policy: ID: [6913d1cc-bad2-454b-b213-65ee4f6181be] Name: [11] Description: [111] Device IP: [192.168.67.208] Interfaces: [[XGE1/0/1, XGE1/0/4]] Congestion temp ID: [6913d1cc-bad2-454b-b213-65ee4f6181bb] Traffic policies: [ ID: [072f501d-fdf8-4131-b1f5-4e85761fd08a] Name: [policy] Remark: [TaasRemark{dot1p=null, localPrecedence=null, dscp=null}] Classifier ID: [Id[value=4d3e94e8-d8f0-452d-a8c1-4f171eb1ad22]] Rate limit profile ID: [null] Mirroring destination profile ID: [[Id[value=0cc5a797-5989-4d0b-88cd-d5bf8eee00ae]]] Local mirror interface names: [[WGE1/0/3, WGE1/0/4]] Direction: [IN] Traffic size measurement: [In Bytes] ] |
|
日志说明 |
用户进行了创建物理端口策略的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service does not exist：服务不存在 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · The name is required and cannot exceed 255 characters：名称必选并且长度不能超过255个字符 · Failed to add the configuration item：添加配置项失败 · You have no privilege to perform this operation：用户无权限执行此操作 · The switching device is not active：设备未激活 · A traffic behavior cannot contain remote mirroring destination profiles that have the same destination IP address：同一流量行为关联的多个远程镜像目的模板中指定的目的IP不能相同 |
|
关键字 |
UPDATE_PHYSICAL_PORT_POLICY_OP |
|
日志内容 |
Updated physical port policy: $1. |
|
参数解释 |
$1：物理端口策略的信息 |
|
举例 |
Updated physical port policy: ID: [6913d1cc-bad2-454b-b213-65ee4f6181be] Name: [11] Description: [111] Device IP: [192.168.67.208] Interfaces: [[XGE1/0/1, XGE1/0/4]] Congestion temp ID: [6913d1cc-bad2-454b-b213-65ee4f6181bb] Traffic policies: [ ID: [072f501d-fdf8-4131-b1f5-4e85761fd08a] Name: [policy] Remark: [TaasRemark{dot1p=null, localPrecedence=null, dscp=null}] Classifier ID: [Id[value=4d3e94e8-d8f0-452d-a8c1-4f171eb1ad22]] Rate limit profile ID: [null] Mirroring destination profile ID: [[Id[value=0cc5a797-5989-4d0b-88cd-d5bf8eee00ae]]] Local mirror interface names: [[WGE1/0/3, WGE1/0/4]] Direction: [IN]. Traffic size measurement: [In Bytes] ]
|
|
日志说明 |
用户进行了修改物理端口策略的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service does not exist：服务不存在 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · The configuration item does not exist：配置项不存在 · The name is required and cannot exceed 255 characters：名称必选并且长度不能超过255个字符 · Failed to modify the configuration item：修改配置项失败 · You have no privilege to perform this operation：用户无权限执行此操作 · The switching device is not active：设备未激活 · A traffic behavior cannot contain remote mirroring destination profiles that have the same destination IP address：同一流量行为关联的多个远程镜像目的模板中指定的目的IP不能相同 |
|
关键字 |
DELETE_PHYSICAL_PORT_POLICY_OP |
|
日志内容 |
Deleted physical port policy $1. |
|
参数解释 |
$1：物理端口策略的名称 |
|
举例 |
Deleted physical port policy 11. |
|
日志说明 |
用户进行了删除物理端口策略的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service does not exist：服务不存在 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · The configuration item does not exist：配置项不存在 · You have no privilege to perform this operation：用户无权限执行此操作 · The switching device is not active：设备未激活 |
|
关键字 |
CREATE_MIRRORING_PROFILE_OP |
|
日志内容 |
Created mirroring profile: $1. |
|
参数解释 |
$1：镜像的信息 |
|
举例 |
Created mirroring profile: ID: [39e57447-76e2-4b66-894d-625428ecb8e5] Name: [flowName01] Description: [desc01] Tenant ID:[bde03f0b-bf0c-4fcd-a124-b1feb7802c71] Cloud region name:[aaa] vPort ID: [785f1a33-b1c0-48cb-bcae-dfae830ac6df] Local IPv4 Subnet:[11.11.11.11/32] Local IPv6 Subnet:[22::/102] Remote IPv4 Subnet:[22.22.20.0/22] Remote IPv6 Subnet:[11::/22] Mirroring destination template ID: [1942b945-756a-4c5d-b1dc-bab33d1328cc] Direction: [OUT] |
|
日志说明 |
用户进行了创建镜像的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service does not exist：服务不存在 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · The default VXLAN is required：未设置默认VXLAN · The name is required and cannot exceed 255 characters：名称必选并且长度不能超过255个字符 · The description cannot exceed 255 characters：描述信息字段最长255个字符 · The vPort is required：未指定虚拟端口 · The vPort cannot be the same as the vPort in the mirroring destination profile：虚拟端口和镜像目的模板下的虚拟端口不允许相同 · Failed to add the configuration item：添加配置项失败 · No available VXLAN IDs：VXLAN ID已用尽 · The specified mirroring destination profile does not exist：指定的镜像目的模板不存在 · No VXLAN resources are configured, or VXLAN resources have been used up：VXLAN资源未配置或已用尽 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
UPDATE_MIRRORING_PROFILE_OP |
|
日志内容 |
Updated mirroring profile: $1. |
|
参数解释 |
$1：镜像的信息 |
|
举例 |
Updated mirroring profile: ID: [39e57447-76e2-4b66-894d-625428ecb8e5] Name: [flowName01] Description: [desc01] Tenant ID: [bde03f0b-bf0c-4fcd-a124-b1feb7802c71] Cloud region name:[aaa] vPort ID: [785f1a33-b1c0-48cb-bcae-dfae830ac6df] Local IPv4 Subnet:[11.11.11.11/32] Local IPv6 Subnet:[22::/102] Remote IPv4 Subnet:[22.22.20.0/22] Remote IPv6 Subnet:[11::/22] Mirroring destination template ID: [1942b945-756a-4c5d-b1dc-bab33d1328cc] Direction: [IN] |
|
日志说明 |
用户进行了修改镜像的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service does not exist：服务不存在 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · The configuration item does not exist：配置项不存在 · The default VXLAN is required：未设置默认VXLAN · The name is required and cannot exceed 255 characters：名称必选并且长度不能超过255个字符 · The description cannot exceed 255 characters：描述信息字段字段最长255个字符 · The vPort cannot be edited：虚拟端口不允许修改 · The VXLAN ID cannot be modified：VXLAN ID不允许修改 · The vPort cannot be the same as the vPort in the mirroring destination profile：虚拟端口和镜像目的模板下的虚拟端口不允许相同 · Failed to modify the configuration item：修改配置项失败 |
|
关键字 |
DELETE_MIRRORING_PROFILE_OP |
|
日志内容 |
Deleted mirroring profile $1. |
|
参数解释 |
$1：镜像的名称 |
|
举例 |
Deleted mirroring profile 11. |
|
日志说明 |
用户进行了删除镜像的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service does not exist：服务不存在 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · The configuration item does not exist：配置项不存在 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
UPDATE_DEFAULT_VXLAN_OP |
|
日志内容 |
Updated default VXLAN: $1. |
|
参数解释 |
$1：默认VXLAN池的信息 |
|
举例 |
Updated default VXLAN: ID: [ae851830-a200-45e5-8456-e5e79b3a07d6] VXLAN ID: [11] |
|
日志说明 |
用户进行了修改默认VXLAN的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service does not exist：服务不存在 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · The default VXLAN is in use and cannot be edited：默认VXLAN正在被使用，不允许修改 · Failed to modify the configuration item：修改配置项失败 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_CONGESTION_MANAGE_PROFILE_OP |
|
日志内容 |
Created congestion management profile: $1. |
|
参数解释 |
$1：拥塞模板的信息 |
|
举例 |
Created congestion management profile: ID: [dfbce4db-8e72-4fd4-a659-f6889c709e15] Name: [addTest ] Description: [111] Scheduling mode: [Packet-Count WFQ] Queues: { Queue number: [111] Priority queue group: [1] Scheduling weight: [2] Min bandwidth: [1] } |
|
日志说明 |
用户进行了创建拥塞模板的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service does not exist：服务不存在 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · The name is required and cannot exceed 255 characters：名称必选并且长度不能超过255个字符 · The description cannot exceed 255 characters：描述信息字段最长255个字符 · Failed to add the configuration item：添加配置项失败 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_CONGESTION_MANAGE_PROFILE_OP |
|
日志内容 |
Updated congestion management profile: $1. |
|
参数解释 |
$1：拥塞模板的信息 |
|
举例 |
Updated congestion management profile: ID: [dfbce4db-8e72-4fd4-a659-f6889c709e15] Name: [modTest] Description: [01]↵ Scheduling mode: [Packet-Count WRR] Queues: { Queue number: [111] Priority queue group: [1] Scheduling weight: [2] } |
|
日志说明 |
用户进行了修改拥塞模板的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service does not exist：服务不存在 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · The configuration item does not exist：配置项不存在 · The description cannot exceed 255 characters：描述信息字段最长255个字符 · Failed to modify the configuration item：修改配置项失败 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_CONGESTION_MANAGE_PROFILE_OP |
|
日志内容 |
Deleted congestion management profile $1. |
|
参数解释 |
$1：拥塞模板的名称 |
|
举例 |
Deleted congestion management profile test |
|
日志说明 |
用户进行了删除拥塞模板的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service does not exist：服务不存在 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · The configuration item does not exist：配置项不存在 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_GTS_MANAGE_PROFILE_OP |
|
日志内容 |
Created GTS profile: $1. |
|
参数解释 |
$1：流量整形模板的信息 |
|
举例 |
Created GTS profile: ID: [dfbce4db-8e72-4fd4-a659-f6889c709e15] Name: [addTest ] Description: [111] Queues: { Queue number: [111] CIR: [2] CBS: [1] } |
|
日志说明 |
用户进行了创建流量整形模板的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service does not exist：服务不存在 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · The name is required and cannot exceed 255 characters：名称必选并且长度不能超过255个字符 · The description cannot exceed 255 characters：描述信息字段最长255个字符 · Failed to add the configuration item：添加配置项失败 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_GTS_MANAGE_PROFILE_OP |
|
日志内容 |
Updated GTS profile: $1. |
|
参数解释 |
$1：流量整形模板的信息 |
|
举例 |
Updated GTS profile: ID: [dfbce4db-8e72-4fd4-a659-f6889c709e15] Name: [addTest ] Description: [111] Queues: { Queue number: [111] CIR: [2] CBS: [1] } |
|
日志说明 |
用户进行了修改流量整形模板的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service does not exist：服务不存在 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · The name is required and cannot exceed 255 characters：名称必选并且长度不能超过255个字符 · The description cannot exceed 255 characters：描述信息字段最长255个字符 · Failed to add the configuration item：添加配置项失败 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_GTS_MANAGE_PROFILE_OP |
|
日志内容 |
Deleted GTS profile $1. |
|
参数解释 |
$1：流量整形模板的名称 |
|
举例 |
Deleted GTS profile 111. |
|
日志说明 |
用户进行了删除流量整形模板的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service does not exist：服务不存在 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · The configuration item does not exist：配置项不存在 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_QOS_POLICY_OP |
|
日志内容 |
Created QoS policy “$1”. |
|
参数解释 |
$1：QoS策略参数体 |
|
举例 |
Created QoS policy networkId:[7a570d3c-89ab-473c-9059-534aa1164a08] tenantId:[ffffffff-0000-0000-0000-000000000001] vni:[1] deviceIps:[[]] Traffic policies:[ ID:[3a220c89-a6b3-464f-b3e9-ea9e6cf317ea] Name:[1] Remark:[TaasRemark{dot1p=null, localPrecedence=null, dscp=null}] Classifier ID:[Id[value=30750e59-afb5-494d-8847-756a0f6c0836]] Rate limit profile ID:[null] Mirroring destination profile ID:[null] Local mirror interface names:[null] direction:[IN]]. |
|
日志说明 |
用户进行了创建QoS策略的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The specified QoS policy already exists：该QoS策略已经存在 · The specified vNetwork does not exist：指定的虚拟链路层网络不存在 · The specified tenant does not exist：指定的租户不存在 · The tenant is required：未指定租户 · You cannot edit the tenant_id：租户不允许修改 · The network_id parameter is required：缺少参数network_id · The network_id parameter is invalid：参数network_id非法 · The tenant_id parameter is required：缺少参数tenant_id · The tenant_id parameter is invalid：参数tenant_id非法 · The classifier_id parameter is required：缺少参数classifier_id · The classifier_id parameter is invalid：参数classifier_id非法 · The name parameter is required：缺少参数name · The car_id parameter is invalid：参数car_id非法 · The direction parameter is required：缺少参数direction · The cloud region name cannot exceed 255 characters：云区域名称字段长度不能超过255个字符 · The tenant of classifier is required：分类器中缺少租户属性 · The tenant of rate limit profile is required：限速模板中缺少租户属性 · The tenant of classifier must be the same：分类器中租户必须一致 · The tenant of rate limit profile must be the same：限速模板中租户必须一致 · The service does not exist：该服务不存在 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The specified classifier does not exist：指定的分类器不存在 · The specified direction is not supported：指定的方向不支持 · The specified rate limit profile does not exist：指定的限速模板不存在 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_QOS_POLICY_OP |
|
日志内容 |
Updated QoS policy “$1”. |
|
参数解释 |
$1：QoS策略参数体 |
|
举例 |
Updated QoS policy networkId:[7a570d3c-89ab-473c-9059-534aa1164a08] tenantId:[ffffffff-0000-0000-0000-000000000001] vni:[0] deviceIps:[[]] Traffic policies:[ ID:[3a220c89-a6b3-464f-b3e9-ea9e6cf317ea] Name:[12] Remark:[TaasRemark{dot1p=null, localPrecedence=null, dscp=null}] Classifier ID:[Id[value=30750e59-afb5-494d-8847-756a0f6c0836]] Rate limit profile ID:[null] Mirroring destination profile ID:[null] Local mirror interface names:[null] direction:[IN]]. |
|
日志说明 |
用户进行了修改QoS策略的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The specified QoS policy does not exist：指定的QoS策略不存在 · The specified vNetwork does not exist：指定的虚拟链路层网络不存在 · The specified tenant does not exist：指定的租户不存在 · The tenant is required：未指定租户 · You cannot edit the tenant_id：租户不允许修改 · The network_id parameter is required：缺少参数network_id · The network_id parameter is invalid：参数network_id非法 · The tenant_id parameter is required：缺少参数tenant_id · The tenant_id parameter is invalid：参数tenant_id非法 · The classifier_id parameter is required：缺少参数classifier_id · The classifier_id parameter is invalid：参数classifier_id非法 · The name parameter is required：缺少参数name · The car_id parameter is invalid：参数car_id非法 · The direction parameter is required：缺少参数direction · The cloud region name cannot exceed 255 characters：云区域名称字段长度不能超过255个字符 · The tenant of classifier is required：分类器中缺少租户属性 · The tenant of rate limit profile is required：限速模板中缺少租户属性 · The tenant of classifier must be the same：分类器中租户必须一致 · The tenant of rate limit profile must be the same：限速模板中租户必须一致 · The service does not exist：该服务不存在 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The specified classifier does not exist：指定的分类器不存在 · The specified direction is not supported：指定的方向不支持 · The specified rate limit profile does not exist：指定的限速模板不存在 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_QOS_POLICY_OP |
|
日志内容 |
Deleted QoS policy “$1”. |
|
参数解释 |
$1：虚拟链路层网络UUID |
|
举例 |
Deleted QoS policy 23671e07-3c2a-45f4-a7b5-1fb6f0e43a57. |
|
日志说明 |
用户进行了删除QoS策略的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The specified QoS policy does not exist：指定的QoS策略不存在 · The service does not exist：该服务不存在 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_ROCE_POLICY_OP |
|
日志内容 |
Created RoCE policy: $1. |
|
参数解释 |
$1：RoCE策略信息 |
|
举例 |
Created RoCE policy: { id=Id[value=abc077c4-8f13-41c1-81c8-902d95d1f1a7], name='11, fabricId='44c6161b-b177-4861-b8da-d03b71904ce5, fabricName='null, deviceIpList=[66.66.66.110], roceDscpPrecedences=[{importQueue=5, exportQueue=4, wfqWeight=60}], cnpDscpPrecedences=[{importQueue=3, exportQueue=6}], excludedInfo=[ { deviceIp=66.66.66.110, interfaceSet=[], usedInterSet=[XGE5/1/1], unusedInterSet=[] } ], dcbxInfoList=[], deadLockPreventList=[], ipccInfoList=[], excludeFlag=true, version=V3, ecnMode=STATIC, recordUsedInterface=true }. |
|
日志说明 |
用户进行了创建RoCE策略的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller was not the active leader ：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Failed to synchronize information from the primary controller to the backup controller：主控制组件向备控制组件同步信息失败 · The RoCE policy already exists：策略已经存在 · Invalid JSON format：无效的请求格式 · Invalid number：无效的输入数值 · The export parameter is invalid：export字段无效 · The import parameter is invalid：import字段无效 · Invalid fabric ID：Fabric ID无效 · The DSCP values of service packets overlap with the DSCP values of CNP packets：DSCP数值和CNP数值冲突 · Field can not be null：字段不能为空 · Fabric id conflict：Fabric ID冲突 · Unknown system error：系统未知错误 · Southbound devices at the following IP addresses were disconnected: {ip}：{ip}对应的南向设备已断开连接 · Please make sure all interface names on the same device are unique：相同同设备下的接口名称不能重复 · Please make sure all IP addresses are unique：IP地址重复 · Please specify an ECN mode：ECN模式不能为空 · The RoCE DSCP queue ID must be in the range of 1 to 5：RoCE队列取值范围为1～5的整数 · Please specify a WFQ weight：WFQ调度权重不能为空 · Please specify an RoCE template：RoCE模板不能为空 · The DSCP values in different DSCP mappings cannot overlap：业务报文DSCP优先级不能重叠 · Please specify a CNP queue：CNP队列不能为空 · The DSCP value must be an integer or a range of integers in the range of 0 to 63：DSCP优先级取值范围为0～63的整数或区间 · The value for the CNP queue must be 6：CNP队列必须为6 · The WFQ weight must be an integer in the range of 1 to 127：WFQ调度权重取值范围为1～127的整数 · Please specify a DSCP value：DSCP优先级不允许为空 · Some of the specified DCBX interfaces have been configured as excluded interfaces：DCBX接口和例外接口中含有相同的接口 |
|
关键字 |
UPDATE_ROCE_POLICY_OP |
|
日志内容 |
Updated RoCE policy: $1. |
|
参数解释 |
$1：RoCE策略信息 |
|
举例 |
Updated RoCE policy: { id=Id[value=abc077c4-8f13-41c1-81c8-902d95d1f1a7], name='11, fabricId='44c6161b-b177-4861-b8da-d03b71904ce5, fabricName='vlan, deviceIpList=[66.66.66.110], roceDscpPrecedences=[{ importQueue=5, exportQueue=4, wfqWeight=60 }], cnpDscpPrecedences=[{ importQueue=3, exportQueue=6 }], excludedInfo=[{ deviceIp=66.66.66.110, interfaceSet=[FGE5/0/2], usedInterSet=[XGE5/1/1], unusedInterSet=[FGE5/0/2] }], dcbxInfoList=[], deadLockPreventList=[], ipccInfoList=[], excludeFlag=true, version=V3, ecnMode=STATIC, recordUsedInterface=true }. |
|
日志说明 |
用户进行了更新RoCE策略的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller was not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Failed to synchronize information from the primary controller to the backup controller：主控制组件向备控制组件同步信息失败 · Failed to modify the configuration item：修改对应配置失败 · The configuration item does not exist：对应的配置条目不存在 · Invalid JSON format：错误的JSON格式 · Invalid number：无效的数字 · The export parameter is invalid：export字段无效 · The import parameter is invalid：import字段无效 · The DSCP values of service packets overlap with the DSCP values of CNP packets：DSCP数值和CNP数值冲突 · The name is required and cannot exceed 255 characters：名称字段不能超过255字符 · not supported device ip：不支持的设备IP · The fabric does not exist：Fabric不存在 · Unknown system error：系统未知错误 · Southbound devices at the following IP addresses were disconnected: {ip}：{ip}对应的南向设备已断开连接 · Please make sure all interface names on the same device are unique：相同同设备下的接口名称不能重复 · Please make sure all IP addresses are unique：IP地址重复 · Please specify an ECN mode：ECN模式不能为空 · The RoCE DSCP queue ID must be in the range of 1 to 5：RoCE队列取值范围为1～5的整数 · Please specify a WFQ weight：WFQ调度权重不能为空 · Please specify an RoCE template：RoCE模板不能为空 · The DSCP values in different DSCP mappings cannot overlap：业务报文DSCP优先级不能重叠 · Please specify a CNP queue：CNP队列不能为空 · The DSCP value must be an integer or a range of integers in the range of 0 to 63：DSCP优先级取值范围为0～63的整数或区间 · The value for the CNP queue must be 6：CNP队列必须为6 · The WFQ weight must be an integer in the range of 1 to 127：WFQ调度权重取值范围为1～127的整数 · Please specify a DSCP value：DSCP优先级不允许为空 · Some of the specified DCBX interfaces have been configured as excluded interfaces：DCBX接口和例外接口中含有相同的接口 |
|
关键字 |
DELETE_ROCE_POLICY_OP |
|
日志内容 |
Deleted RoCE policy: $1. |
|
参数解释 |
$1：RoCE策略UUID |
|
举例 |
Deleted RoCE policy: RoCE policy ID: abc077c4-8f13-41c1-81c8-902d95d1f1a7. |
|
日志说明 |
用户进行了删除RoCE策略的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Southbound devices at the following IP addresses were disconnected: {ip}.：{ip}对应的南向设备已断开连接 · Failed to delete the configuration item ：策略删除失败 · Unknown error：未知错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Failed to synchronize information from the primary controller to the backup controller：主控制组件向备控制组件同步信息失败 |
|
关键字 |
UPDATE_DEVICE_OPTIMIZATION_OP |
|
日志内容 |
Updated device optimization configuration: $1 |
|
参数解释 |
$1：设备级调优参数 |
|
举例 |
Updated device optimization configuration: { "device_ips":[ “192.168.67.206”, “192.168.67.207” ], “headroom”:19246 } |
|
日志说明 |
用户更新了一次设备级调优参数 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown errors：存在未知错误 |
|
关键字 |
UPDATE_INTERFACE_OPTIMIZATION_OP |
|
日志内容 |
Updated interface optimization configuration: $1 |
|
参数解释 |
$1：接口级调优参数 |
|
举例 |
Updated interface optimization configuration: { "interfaces": [ { "device_ip": "192.168.67.206", "interface_names": [ "WGE1/0/36" ] } ], "pfc_configs": [ { "queue": 4, "pfc_headroom": 19641, "pfc_reserved_buffer": 17, "pfc_ingress_buffer_dynamic": 5, "pfc_ingress_threshold_offset": 12 }, { "queue": 5, "pfc_headroom": 19642, "pfc_reserved_buffer": 17, "pfc_ingress_buffer_dynamic": 5, "pfc_ingress_threshold_offset": 12 } ], "cnp_configs": [ { "queue": 6, "gts_cir": 50000000, "gts_cbs": 16000000 } ], "wred_configs": [ { "queue": 4, "drop_level_configs": [ { "drop_level": 0, "low_limit": 1000, "high_limit": 2000, "discard-probability": 20 }, { "drop_level": 1, "low_limit": 1000, "high_limit": 2000, "discard-probability": 20 } ] }, { "queue": 5, "drop_level_configs": [ { "drop_level": 0, "low_limit": 1000, "high_limit": 2000, "discard-probability": 20 }, { "drop_level": 1, "low_limit": 1000, "high_limit": 2000, "discard-probability": 20 } ] }, { "queue": 6, "drop_level_configs": [ { "drop_level": 0, "low_limit": 1000, "high_limit": 2000, "discard-probability": 20 }, { "drop_level": 1, "low_limit": 1000, "high_limit": 2000, "discard-probability": 20 } ] } ] } |
|
日志说明 |
用户更新了一次接口级调优参数 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown errors：存在未知错误 |
|
关键字 |
CONFIGURE_PVID_OP |
|
日志内容 |
Configured PVID: $1. |
|
参数解释 |
$1：设备信息，包括设备的管理IP和指定设备的多个接口PVID |
|
举例 |
Configured PVID: { Device IP:[192.168.67.203] Interface List:[ { Interface name:[BAGG10] Pvid:[444] }, { Interface name:[XGE1/2/2] Pvid:[444] } ] }, { Device IP:[192.168.67.209] Interface List:[ { Interface name:[BAGG10] Pvid:[444] }, { Interface name:[HGE1/0/29] Pvid:[444] } ] }. |
|
日志说明 |
用户进行了对指定设备的多个接口配置PVID的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service does not exist：服务不存在 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · Failed to add the configuration item：添加配置项失败 · Please specify IP addresses：IP地址不能为空 · Please specify interface names：接口名称不能为空 · Please specify PVIDs：接口PVID不能为空 · Please make sure all device IP addresses are unique：设备的IP地址重复 · Please make sure all interface names on the same device are unique：相同设备下的接口名称不能重复 · A PVID must be in the range of 1 to 4094：PVID的取值范围是1～4094之间的整数 · A minimum of one specified Layer 2 interface does not exist：指定的二层接口不存在 · The switching device is not active：指定的交换设备未激活 · The specified device type must be underlay：指定设备的类型只支持Underlay物理设备 · The service network type on the fabric must be VLAN：指定设备所在Fabric的业务网络类型必须为VLAN |
|
关键字 |
UPDATE_PVID_OP |
|
日志内容 |
Updated PVID: $1 |
|
参数解释 |
$1：设备信息，包括设备的管理IP、接口简称和PVID |
|
举例 |
Updated PVID: Device IP:[192.168.67.203] Interface List:[ { Interface name:[BAGG10] Pvid:[444] }, { Interface name:[XGE1/2/2] Pvid:[33] } ].
|
|
日志说明 |
用户进行了修改指定设备下一个或多个接口PVID的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service does not exist：服务不存在 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · Failed to modify the configuration item：修改配置项失败 · Please specify IP addresses：IP地址不能为空 · Please specify interface names：接口名称不能为空 · Please specify PVIDs：接口PVID不能为空 · Please make sure all interface names on the same device are unique：相同设备下的接口名称不能重复 · A PVID must be in the range of 1 to 4094：PVID的取值范围是1～4094之间的整数 · A minimum of one specified Layer 2 interface does not exist：指定的二层接口不存在 · The switching device is not active：指定的交换设备未激活 · The specified device type must be underlay：指定设备的类型只支持Underlay物理设备 · The service network type on the fabric must be VLAN：指定设备所在Fabric的业务网络类型必须为VLAN |
|
关键字 |
DELETE_PVID_OP |
|
日志内容 |
Deleted PVID: $1 |
|
参数解释 |
$1：设备信息，包括设备的管理IP和设备简称 |
|
举例 |
Deleted PVID: { Device IP:[192.168.67.203] }, { Device IP:[192.168.67.209] Interface List:[ { Interface name:[BAGG10] }, { Interface name:[XGE1/2/2] } ] }. |
|
日志说明 |
用户进行了删除指定设备PVID的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service does not exist：服务不存在 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · Failed to delete the configuration item：删除配置项失败 · Please specify IP addresses：IP地址不能为空 · Please make sure all device IP addresses are unique：设备的IP地址重复 · Please make sure all interface names on the same device are unique：相同设备下的接口名称不能重复 · No PVID is configured for the interface on the controller：控制组件上未配置该接口的PVID |
|
关键字 |
CREATE_COLLECTOR_OP |
|
日志内容 |
Created SeerEngine collector: $1 |
|
参数解释 |
$1：采集器的信息 |
|
举例 |
Created SeerEngine collector: ID: [1] Name: [TEST_COLLECTOR] ip_address: [1] port: [2] isUsed: [In use] Description: [] |
|
日志说明 |
用户进行了创建采集器的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · The UUID already exists：指定的UUID已存在 · The name is required and cannot exceed 255 characters：名称不允许为空且最长255个字符 · The port number range is 0 to 65535：端口的取值范围为0～65535 · The collector with the same IP and port already exists：采集器已存在相同IP和端口 · The state cannot be modified：状态值不允许修改 · You have no privilege to perform this operation：用户无权限执行此操作 · The IP address cannot unmodifiable：IP地址不允许修改 · The collector ID is unmodifiable：采集器的ID不允许修改 · The states cannot be modified：状态值不允许修改 · If you specify a VRF, the value for the management network VRF must be false：若指定VRF，则管理网VRF必须配置为false · If the value for the management network VRF is true, you cannot specify a VRF：若管理网VRF配置为true，则不允许指定VRF |
|
关键字 |
UPDATE_COLLECTOR_OP |
|
日志内容 |
Updated SeerEngine collector: $1 |
|
参数解释 |
$1：采集器的信息 |
|
举例 |
Updated SeerEngine collector: ID: [1] Name: [TEST_COLLECTOR] ip_address: [1] port: [2] isUsed: [In use] Description: [] |
|
日志说明 |
用户进行了修改采集器的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · The state cannot be modified：状态值不允许修改 · The port number cannot be modified：端口号不允许修改 · The ID cannot be modified：ID不允许修改 · The IP address cannot be modified：IP地址不允许修改 · The configuration item does not exist：配置项不存在 · You have no privilege to perform this operation：用户无权限执行此操作 · The IP address cannot unmodifiable：IP地址不允许修改 · The collector ID is unmodifiable：采集器的ID不允许修改 · The states cannot be modified：状态值不允许修改 |
|
关键字 |
DELETE_COLLECTOR_OP |
|
日志内容 |
Deleted SeerEngine collector: $1. |
|
参数解释 |
$1：采集器的名称 |
|
举例 |
Deleted SeerEngine collector: 1. |
|
日志说明 |
用户进行了删除采集器的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · The configuration item does not exist：配置项不存在 · The configuration item is in use：删除失败，指定的配置项正在使用中 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_COMM_INFO_OP |
|
日志内容 |
Updated gRPC common info: $1 |
|
参数解释 |
$1：gRPC公共配置信息 |
|
举例 |
Updated gRPC common info: ID: [1] Sample_interval: 10 PathList: [-1] |
|
日志说明 |
用户进行了修改gRPC公共配置的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Invalid JSON format：无效的JSON格式 · The sensor path is required：未指定采样路径 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
CREATE_GRPC_DEV_OP |
|
日志内容 |
Created data collection policy: $1 |
|
参数解释 |
$1：采集策略信息 |
|
举例 |
Created data collection policy: ID: [1] Name: [TEST_GRPC] Device IP List: [10.2.1.1] Collector List: [3] Collection Template ID: [8b2d9e45-760c-42e4-9cc5-43c157e88cf0] |
|
日志说明 |
用户进行了创建采集策略的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · The name is required and cannot exceed 255 characters：名称不允许为空且最长255个字符 · The collector name is read only：采集器名称为只读 · The collector does not exist：指定的采集器不存在 · The switching device does not exist：指定的交换设备不存在 · The configuration item already exists：指定的配置项已存在 · You have no privilege to perform this operation：用户无权限执行此操作 · The device list cannot be empty：设备列表不能为空 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · The sensor paths is required：未指定采样路径 · The sensor path is invalid：无效的采样路径 · The bound collector port can't be 0：gRPC绑定的采集器端口不允许为0 · Invalid path name：无效的路径名称 · A data collection template cannot be bound to the same switching device：交换设备不允许绑定相同的采集模板 · The switching device is already added to the data collection policy：该采集策略不支持添加重复的交换设备 · Do not bind a data collection policy to two collectors that have the same IP address but one without a port number configured and the other with port number 50051：采集策略不允许同时绑定相同IP的未配置端口号和端口号为50051的采集器 |
|
关键字 |
UPDATE_GRPC_DEV_OP |
|
日志内容 |
Updated data collection policy: $1 |
|
参数解释 |
$1：采集策略信息 |
|
举例 |
Updated data collection policy: ID: [1] Name: [TEST_GRPC] Device IP List: [10.2.1.1] Device IP: [2] Collector List: [3] |
|
日志说明 |
用户进行了修改采集策略的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · The name is required and cannot exceed 255 characters：名称不允许为空且最长255个字符 · The collector name is read only：采集器名称为只读 · The switching device does not exist：指定的交换设备不存在 · The name is required and cannot exceed 255 characters：名称不允许为空且最长255个字符 · The collector does not exist：指定的采集器不存在 · The switching device does not exist：指定的交换设备不存在 · You have no privilege to perform this operation：用户无权限执行此操作 · The device list cannot be empty：设备列表不能为空 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · The sensor paths is required：未指定采样路径 · The sensor path is invalid：无效的采样路径 · The bound collector port can't be 0：gRPC绑定的采集器端口不允许为0 · Invalid path name：无效的路径名称 · A data collection template cannot be bound to the same switching device：交换设备不允许绑定相同的采集模板 · The switching device is already added to the data collection policy：该采集策略不支持添加重复的交换设备 · Do not bind a data collection policy to two collectors that have the same IP address but one without a port number configured and the other with port number 50051：采集策略不允许同时绑定相同IP的未配置端口号和端口号为50051的采集器 · Operation failed. You cannot disable gRPC, because another data collection policy has gRPC configuration：操作失败，其他采集策略中存在gRPC配置，无法关闭gRPC开关 |
|
关键字 |
DELETE_GRPC_DEV_OP |
|
日志内容 |
Deleted data collection policy: $1 |
|
参数解释 |
$1：采集策略名称 |
|
举例 |
Deleted data collection policy: 1 |
|
日志说明 |
用户进行了删除采集策略的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · The configuration item does not exist：配置项不存在 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · Operation failed. You cannot disable gRPC, because another data collection policy has gRPC configuration：操作失败，其他采集策略中存在gRPC配置，无法关闭gRPC开关 |
|
关键字 |
CREATE_COLLECTION_TEMPLATE_OP |
|
日志内容 |
Created data collection template: $1. |
|
参数解释 |
$1：采集模板信息 |
|
举例 |
Created data collection template: { ID:[ c352f537-ad49-48eb-ab05-1c6b8cb92233] Name: [采集模板名称01] Paths : [ { Sensor path:[acl/ipv4namedadvancerules] Push Interval:[200] Unit:MILLISECOND }, { Sensor path:[buffermonitor/bufferusages] Push Interval:[888] Unit:SECOND } ] }. |
|
日志说明 |
用户进行了创建一个采集模板的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service does not exist：服务不存在 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · Invalid UUID：无效的UUID · The UUID already exists：UUID已经存在 · Failed to add the configuration item：添加配置项失败 · The name is required and cannot exceed 255 characters：名称必选并且长度不能超过255个字符 · A data collection template already exists with the specified name：指定名称的采集模板已存在 · Please add a minimum of one sensor path in a data collection template：采集模板中至少配置一条采集路径 · Please specify the sensor path name. The name cannot exceed 255 characters. Chinese characters, spaces, and question marks (?) are not allowed：采集路径名称不能为空，且最长255个字符，不支持中文、空格和问号 · Please make sure all specified sensor paths are unique：不支持配置相同的采集路径 · The data push interval is required. When the time unit is seconds, its value must be an integer in the range of 0 to 86400. When the time unit is milliseconds, its value must be a multiple of 100 and within the range of 0 to 900. A value of 0 means event-triggered data push：推送周期不能为空。时间单位为秒时，取值为0到86400的整数；时间单位为毫秒时，取值范围为0～900之间可以被100整除的整数。其中推送周期为0时表示由事件触发采集上送 · The unit parameter can only be second or millisecond and is case insensitive：时间单位字段取值必须为second或millisecond，不区分大小写 |
|
关键字 |
MOD_COLLECTION_TEMPLATE_OP |
|
日志内容 |
Updated data collection template: $1 |
|
参数解释 |
$1：南向配置记录的UUID和采集模板信息 |
|
举例 |
Updated data collection template: { ID:[ c352f537-ad49-48eb-ab05-1c6b8cb92233] Operate ID:[ 9e3ceb22-691b-4d03-94f7-decee2618454] Name: [采集模板名称01] Paths : [ { Sensor path:[acl/ipv4namedadvancerules] Push Interval:[200] Unit:MILLISECOND
}, { Sensor path:[buffermonitor/bufferusages] Push Interval:[888] Unit:SECOND } ] }. |
|
日志说明 |
用户进行了修改一个采集模板的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service does not exist：服务不存在 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · Invalid UUID：无效的UUID · The configuration item does not exist：配置项不存在 · Failed to modify the configuration item：修改配置项失败 · The data collection template name cannot be edited：采集模板名称不支持修改 · Please add a minimum of one sensor path in a data collection template：采集模板中至少配置一条采集路径 · Please specify the sensor path name. The name cannot exceed 255 characters. Chinese characters, spaces, and question marks (?) are not allowed：采集路径名称不能为空，且最长255个字符，不支持中文、空格和问号 · Please make sure all specified sensor paths are unique：不支持配置相同的采集路径 · The data push interval is required. When the time unit is seconds, its value must be an integer in the range of 0 to 86400. When the time unit is milliseconds, its value must be a multiple of 100 and within the range of 0 to 900. A value of 0 means event-triggered data push：推送周期不能为空。时间单位为秒时，取值为0到86400的整数；时间单位为毫秒时，取值范围为0～900之间可以被100整除的整数。其中推送周期为0时表示由事件触发采集上送 · The unit parameter can only be second or millisecond and is case insensitive：时间单位字段取值必须为second或millisecond，不区分大小写 · Southbound devices at the following IP addresses were disconnected: {%s}.：存在南向设备断连，断连南向设备的IP集合：{192.168.11.11, 192.168.156.156} |
|
关键字 |
DEL_COLLECTION_TEMPLATE_OP |
|
日志内容 |
Deleted data collection template: $1 |
|
参数解释 |
$1：采集模板名称 |
|
举例 |
Deleted data collection template: [templateName01] |
|
日志说明 |
用户进行了删除采集模板的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service does not exist：服务不存在 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid UUID：无效的UUID · Failed to delete the configuration item：删除配置项失败 · The configuration item does not exist：配置项不存在 · The specified data collection template has been used：指定的采集模板已经被使用 |
|
关键字 |
MOD_SENSOR_PATH_LIBRARY_OP |
|
日志内容 |
Updated sensor path library: $1 |
|
参数解释 |
$1：预置路径库信息 |
|
举例 |
Updated sensor path library: { Paths : [ { Sensor path: [acl/ipv4namedadvancerules] Push Interval:[200] Unit:MILLISECOND Predefined Path: [true] Description: [采集路径描述] }, { Sensor path: [buffermonitor/bufferusages] Push Interval: [888] Unit:SECOND Predefined Path: [false] Description: [采集路径描述] } ] }. |
|
日志说明 |
用户使用一个预置路径库进行配置下发操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service does not exist：服务不存在 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · The configuration item does not exist：配置项不存在 · Failed to modify the configuration item：修改配置项失败 · Please specify the sensor path name. The name cannot exceed 255 characters. Chinese characters, spaces, and question marks (?) are not allowed：采集路径名称不能为空，且最长255个字符，不支持中文、空格和问号 · Please make sure all specified sensor paths are unique：不支持配置相同的采集路径 · The sensor path description cannot exceed 255 characters：采集路径的描述长度范围为0～255 · The sensor path library must contain all predefined paths：采集路径库中必须包括所有的预置路径 · The data push interval is required. When the time unit is seconds, its value must be an integer in the range of 0 to 86400. When the time unit is milliseconds, its value must be a multiple of 100 and within the range of 0 to 900. A value of 0 means event-triggered data push：推送周期不能为空。时间单位为秒时，取值为0到86400的整数；时间单位为毫秒时，取值范围为0～900之间可以被100整除的整数。其中推送周期为0时表示由事件触发采集上送 · The unit parameter can only be second or millisecond and is case insensitive：时间单位字段取值必须为second或millisecond，不区分大小写 |
|
关键字 |
CREATE_INT_DEV_OP |
|
日志内容 |
Created INT device: $1 |
|
参数解释 |
$1：INT设备信息 |
|
举例 |
Created INT device: ID: [1] Name: [TEST_INT_DEVICE] Device IP: [2] |
|
日志说明 |
用户进行了创建INT设备的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · The service has not been found：服务未启动 · The name is required and cannot exceed 255 characters：名称不允许为空且最长255个字符 · The switching device does not exist：指定的交换设备不存在 · The UUID already exists：指定的UUID已存在 · You have no privilege to perform this operation：用户无权限执行此操作 · The switching device is not active：交换设备未激活 |
|
关键字 |
UPDATE_INT_DEV_OP |
|
日志内容 |
Updated INT device: $1 |
|
参数解释 |
$1：INT设备信息 |
|
举例 |
Updated INT device: ID: [1] Name: [TEST_INT_DEVICE] Device IP: [2] |
|
日志说明 |
用户进行了修改INT设备的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · The name is required and cannot exceed 255 characters：名称不允许为空且最长255个字符 · The ID cannot be modified：ID不允许修改 · The IP address cannot be modified：IP地址不允许修改 · The configuration item does not exist：配置项不存在 · You have no privilege to perform this operation：用户无权限执行此操作 · The switching device is not active：交换设备未激活 |
|
关键字 |
DELETE_INT_DEV_OP |
|
日志内容 |
Deleted INT device: $1 |
|
参数解释 |
$1：INT设备名称 |
|
举例 |
Deleted INT device: [TEST_INT_DEVICE] |
|
日志说明 |
用户进行了删除INT设备的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · The configuration item does not exist：配置项不存在 · You have no privilege to perform this operation：用户无权限执行此操作 · The switching device is not active：交换设备未激活 |
|
关键字 |
CREATE_IFA_NODE_OP |
|
日志内容 |
Created INT node: $1 |
|
参数解释 |
$1：INT节点信息 |
|
举例 |
Created INT node: ID: [1] Name: [TEST_INT_NODE] Device ID: [2] Interface Name: [3] Type: [egress] Egress IP: [4] Egress Port: [5] Collector ID: [6] |
|
日志说明 |
用户进行了创建INT节点的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · The name is required and cannot exceed 255 characters：名称不允许为空且最长255个字符 · The collector name is read only：采集器名称为只读 · The interface name is required：未指定接口名称 · The switching device ID is required：未指定交换设备ID · The switching device does not exist：指定的交换设备不存在 · Invalid interface：无效的接口 · The UUID already exists：指定的UUID已存在 · The collector does not exist：指定的采集器不存在 · The collector ID is required：未指定采集器ID · The configuration item already exists：指定的配置项已存在 · Integer (1 to 86400)：采样速率的取值范围为1～86400的整数 · You have no privilege to perform this operation：用户无权限执行此操作 · The switching device is not active：交换设备未激活 · The traffic collection node type is required：未指定INT接口角色 · The node type cannot be modified：接口角色不允许修改 · The IP address of the switching device is required：未指定交换设备IP地址 · The IP address of the switching device cannot be modified：交换设备IP地址不允许修改 · The switching device ID is cannot be modified：交换设备ID不允许修改 · The IP address type is required：IP地址类型不允许为空 · The IP address does not match the IP address type：输入的IP地址必须和IP地址类型保持一致 · The egress IP is required：未指定尾节点的IP地址 · Invalid source or destination IP address：无效的源或目的IP地址 · ICMP does not support port configuration：ICMP协议类型不支持配置端口 · The egress port is required：未指定尾节点端口 · The collector, egress ip and egress port must be configured at the same time：源IP地址、源端口和采集器名称必须同时存在并且当接口角色为尾节点时，必须指定这三个参数 · The collector name, source IP address, and source port must be specified：当接口角色为尾节点时，采集器名称、源IP地址、源端口必须被指定 · The egress node exist, cannot modify egress ip ,egress port and collector：当设备存在尾节点时，采集器名称、源IP地址、源端口不允许删除 · Sampler rate is only used for ingress node：仅首节点需要指定采样率 · The traffic collection node type is read only：INT的接口角色为只读 · The interfaces are read only：修改配置时不允许携带接口字段 · The value for the vxlan_flag field can only be true or false, case sensitive：vxlan_flag字段取值必须为true或false，区分大小写 · The operation code must be an integer in the range of 0 to 255：Opcode取值范围为0～255的整数 · The destination QPair value must be an integer in the range of 0 to 16777215：目的QPair取值范围为0～16777215的整数 · The source QPair value must be an integer in the range of 0 to 16777215：源QPair取值范围为0～16777215的整数 · The NACK value must be an integer in the range of 0 to 31：Nack取值范围为0～31的整数 |
|
关键字 |
UPDATE_IFA_NODE_OP |
|
日志内容 |
Updated INT node: $1 |
|
参数解释 |
$1：INT节点信息 |
|
举例 |
Updated INT node: Name: [TEST_INT_NODE] Egress IP: [4] Egress Port: [5] Collector ID: [6] |
|
日志说明 |
用户进行了修改INT节点的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · The name is required and cannot exceed 255 characters：名称不允许为空且最长255个字符 · The collector name is read only：采集器名称为只读 · The switching device does not exist：指定的交换设备不存在 · The collector ID is required：未指定采集器ID · The collector does not exist：指定的采集器不存在 · Interface list is read only：接口列表为只读 · You have no privilege to perform this operation：用户无权限执行此操作 · The switching device is not active：交换设备未激活 · The traffic collection node type is required：未指定INT接口角色 · The node type cannot be modified：接口角色不允许修改 · The IP address of the switching device is required：未指定交换设备IP地址 · The IP address of the switching device cannot be modified：交换设备IP地址不允许修改 · The switching device ID is cannot be modified：交换设备ID不允许修改 · The IP address type is required：IP地址类型不允许为空 · The IP address does not match the IP address type：输入的IP地址必须和IP地址类型保持一致 · The egress IP is required：未指定尾节点的IP地址 · Invalid source or destination IP address：无效的源或目的IP地址 · ICMP does not support port configuration：ICMP协议类型不支持配置端口 · The egress port is required：未指定尾节点端口 · The collector, egress ip and egress port must be configured at the same time：源IP地址、源端口和采集器名称必须同时存在并且当接口角色为尾节点时，必须指定这三个参数 · The collector name, source IP address, and source port must be specified：当接口角色为尾节点时，采集器名称、源IP地址、源端口必须被指定 · The egress node exist, cannot modify egress ip ,egress port and collector：当设备存在尾节点时，采集器名称、源IP地址、源端口不允许删除 · Sampler rate is only used for ingress node：仅首节点需要指定采样率 · The traffic collection node type is read only：INT的接口角色为只读 · The interfaces are read only：修改配置时不允许携带接口字段 · The value for the vxlan_flag field can only be true or false, case sensitive：vxlan_flag字段取值必须为true或false，区分大小写 · The operation code must be an integer in the range of 0 to 255：Opcode取值范围为0～255的整数 · The destination QPair value must be an integer in the range of 0 to 16777215：目的QPair取值范围为0～16777215的整数 · The source QPair value must be an integer in the range of 0 to 16777215：源QPair取值范围为0～16777215的整数 · The NACK value must be an integer in the range of 0 to 31：Nack取值范围为0～31的整数 |
|
关键字 |
DELETE_IFA_NODE_OP |
|
日志内容 |
Deleted INT node: $1 |
|
参数解释 |
$1：INT节点名称 |
|
举例 |
Deleted INT node: [TEST_INT_NODE] |
|
日志说明 |
用户进行了删除INT节点的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · The configuration item does not exist：配置项不存在 · You have no privilege to perform this operation：用户无权限执行此操作 · The switching device is not active：交换设备未激活 |
|
关键字 |
CREATE_ERS_DEV_OP |
|
日志内容 |
Created erspan device $1 |
|
参数解释 |
$1：ERSPAN设备信息 |
|
举例 |
不同设备类型对应不同的日志内容，具体如下： · 设备类型为主机： Created ERSPAN device: ID : 1f38924a-7159-4cb0-a374-a62388fe2dbe Name : 22 Device Ip : 192.168.154.232 Interface Name : null Collector Id : Id[value=010d0f08-6fa0-4d2b-830c-a459c26eb10f] Inner protocol: null Outer protocol: null device name: null rule set: null device type: OVS.
· 设备类型为交换设备： Created ERSPAN device: ID : a56f6831-76c7-44a9-9879-e3979793b7fe Name : 222 Device Ip : 192.102.0.51 Interface Name : null Collector Id : Id[value=010d0f08-6fa0-4d2b-830c-a459c26eb10f] Inner protocol: false Outer protocol: true device name: null rule set: [SeerengineErspanRule{name='22', protocol=TCP, ipType=IPV4, sourceIP='null', destinationIP='null', sourcePort=null, destinationPort=null, tcpFlag=SYN}] device type: PHY. |
|
日志说明 |
用户进行了创建ERSPAN设备的操作 |
|
失败原因 |
· The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · The name is required and cannot exceed 255 characters：名称不允许为空且最长255个字符 · The collector name is read only：采集器名称为只读 · The switching device does not exist：指定的交换设备不存在 · The collector does not exist：指定的采集器不存在 · The configuration item already exists：指定的配置项已存在 · Invalid interface：无效的接口 · The UUID already exists：指定的UUID已存在 · You have no privilege to perform this operation：用户无权限执行此操作 · The switching device is not active：交换设备未激活 · Invalid VRF name：无效的VRF名称 · The rule list cannot be empty：规则信息列表不能为空 · You can not configure the same rules for a remote mirroring：同一远程镜像下不允许配置相同的规则 · The configuration item name already exists：配置项名称已存在 · Invalid port：无效的端口 · Invalid IP address：无效的IP地址 · Invalid parameter：无效的参数 · This field cannot be used to sort items：无效的排序字段 · The page index must be in the range of 1 to 2147483647：页数索引范围为1~2147483647 · The page size must be in the range of 1 to 2147483647：页数必须为1~2147483647 · Invalid descending or ascending field：无效的升序或降序字段 · The fabric id cannot be modified：fabric id不能被修改 · Invalid source IP address：无效的源IP地址 · Invalid destination IP address：无效的目的IP地址 · You must set the value to true for the inner_protocol field, the outer_protocol field, or both fields：inner_protocol和outer_protocol参数的取值必须有一个为true · Please specify the ip_flag setting：ip_flag参数取值不允许为空 · Please specify IPv4 or IPv6 (case insensitive) for the ip_flag field：ip_flag参数取值仅支持IPv4和IPv6，不区分大小写 · Please specify the protocol name：协议名称不允许为空 · Please specify TCP or UDP (case insensitive) for the protocol name：协议名称仅支持TCP和UDP，不区分大小写 · The source IP address does not match the IP version setting：源IP地址格式与IP版本不匹配 · The destination IP address does not match the IP version setting：目的IP地址格式与IP版本不匹配 · Invalid device IP address：无效的设备IP地址 · The value for the protocol_flag field can only be true or false, not case sensitive：协议状态只能填true或false，不分大小写 · The device IP address for remote monitoring and the collector IP address must be the same IP version：远程镜像的设备IP地址和采集器IP地址的IP版本必须相同 · The specified host does not exist：指定的主机不存在 · The specified host has been bound by remote monitoring：该主机已被远程镜像绑定 · The specified host is inactive：指定主机的状态异常 · The specified host does not contain ERSPAN interfaces：指定的主机不存在ERSPAN接口 · The type parameter can only be phy or ovs and is case insensitive：type参数取值仅支持phy和ovs，不区分大小写 · The device is a traditional device and does not support configuration deployment from the controller：设备类型为传统设备，不支持下发配置 |
|
关键字 |
UPDATE_ERS_DEV_OP |
|
日志内容 |
Updated erspan device $1 |
|
参数解释 |
$1：ERSPAN设备信息 |
|
举例 |
Updated erspan device ID : 2bb90bd1-674d-4af1-bd4c-45812c488e04 Name : 22test Device Ip : 192.168.154.232 Interface Name : null Collector Id : Id[value=010d0f08-6fa0-4d2b-830c-a459c26eb10f] Inner protocol: null Outer protocol: null device name: ovs-232 rule set: [] device type: OVS.
说明：设备类型不允许修改，修改ERSPAN设备日志内容以主机的为例。 |
|
日志说明 |
用户进行了修改ERSPAN设备的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · The name is required and cannot exceed 255 characters：名称不允许为空且最长255个字符 · The collector name is read only：采集器名称为只读 · The switching device does not exist：指定的交换设备不存在 · The collector does not exist：指定的采集器不存在 · The configuration item already exists：指定的配置项已存在 · Invalid interface：无效的接口 · You have no privilege to perform this operation：用户无权限执行此操作 · The switching device is not active：交换设备未激活 · Invalid VRF name：无效的VRF名称 · The rule list cannot be empty：规则信息列表不能为空 · You can not configure the same rules for a remote mirroring：同一远程镜像下不允许配置相同的规则 · The configuration item name already exists：配置项名称已存在 · Invalid port：无效的端口 · Invalid IP address：无效的IP地址 · Invalid parameter：无效的参数 · This field cannot be used to sort items：无效的排序字段 · The page index must be in the range of 1 to 2147483647：页数索引范围为1~2147483647 · The page size must be in the range of 1 to 2147483647：页数必须为1~2147483647 · Invalid descending or ascending field：无效的升序或降序字段 · The fabric id cannot be modified：fabric id不能被修改 · Invalid source IP address：无效的源IP地址 · Invalid destination IP address：无效的目的IP地址 · You must set the value to true for the inner_protocol field, the outer_protocol field, or both fields：inner_protocol和outer_protocol参数的取值必须有一个为true · Please specify the ip_flag setting：ip_flag参数取值不允许为空 · Please specify IPv4 or IPv6 (case insensitive) for the ip_flag field：ip_flag参数取值仅支持IPv4和IPv6，不区分大小写 · Please specify the protocol name：协议名称不允许为空 · Please specify TCP or UDP (case insensitive) for the protocol name：协议名称仅支持TCP和UDP，不区分大小写 · The source IP address does not match the IP version setting：源IP地址格式与IP版本不匹配 · The destination IP address does not match the IP version setting：目的IP地址格式与IP版本不匹配 · Invalid device IP address：无效的设备IP地址 · The value for the protocol_flag field can only be true or false, not case sensitive：协议状态只能填true或false，不分大小写 · The device IP address for remote monitoring and the collector IP address must be the same IP version：远程镜像的设备IP地址和采集器IP地址的IP版本必须相同 · The device type for remote monitoring cannot be edited：远程镜像的设备类型不允许修改 · The specified host does not exist：指定的主机不存在 · The specified host is inactive：指定主机的状态异常 · The specified host does not contain ERSPAN interfaces：指定的主机不存在ERSPAN接口 · The device IP address cannot be modified：设备IP地址不允许修改 · The device name is read only：设备名称为只读字段 · The device is a traditional device and does not support configuration deployment from the controller：设备类型为传统设备，不支持下发配置 |
|
关键字 |
DELETE_ERS_DEV_OP |
|
日志内容 |
Deleted erspan device $1. |
|
参数解释 |
$1：ERSPAN设备名称 |
|
举例 |
Deleted erspan device TEST_ERSPAN_DEVICE. |
|
日志说明 |
用户进行了删除ERSPAN设备的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · The configuration item does not exist：配置项不存在 · You have no privilege to perform this operation：用户无权限执行此操作 · The switching device is not active：交换设备未激活 |
|
关键字 |
CREATE_TELEMETRY_STREAM_DEV_OP |
|
日志内容 |
Created telemetry stream profile: $1 |
|
参数解释 |
$1：Telemetry stream信息 |
|
举例 |
Created telemetry stream profile: ID : 9a8265fe-2d99-417a-ac18-1774a597f685 Name: 3 deviceIpList: [192.168.67.204] sourceIp: 192.168.67.204 sourcePort: 12 collectorId: Id[value=3d9f3712-54dc-4d2a-af8a-e8ab8438a4da] serviceLoopbackInterfaceNames: [WGE1/0/4] policies: [ id : Id[value=d34c8109-19c4-4a00-9e9e-db38fb422376] interfaceNames : [WGE1/0/2, WGE1/0/3] sampleRate: 4]. |
|
日志说明 |
用户进行了创建一个Telemetry stream操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The collector name is read only.：采集器名称为只读字段 · Invalid JSON format：无效的JSON格式 · Internal error：内部错误 · The name is required and cannot exceed 255 characters.：名称字段超过255个字符 · The source ip is required.：源ip地址为必选 · Only IPv4 is supported.：源ip地址仅支持IPv4 · The source port is required.：源端口为必选 · The port number range is 0 to 65535.：源端口大小为0至65535 · The collector ID is required：采集器ID为必选 · The collector does not exist.：指定的采集器不存在 · The collector has no ports.:指定的采集器没有端口 · The interface doesn't exist or illegal.：指定的接口不存在或者非法 · The interface name or sampling rate is required.：采样率和接口名称为必选 · The sampling rate is required.：采样率为必选 · The sampling interval value must be in the range of 0 to 15.：采样率的取值范围为0至15 · The device list cannot be empty.：交换设备不允许为空 · The switching device does not exist.：交换设备不存在 · The switching device is not active.：替换设备序列号不能为空 · The switching device is not active.：交换设备未激活 · The switching device has already been bound on INT or Telemetry Stream.：交换设备已经被INT或者Telemetry Stream绑定 · The switching device not support Telemetry Stream.：交换设备不支持TelemetryStream · Failed to add the configuration item.：添加配置项失败 · The interface name and sampling rate is required：接口名称或者采样率不能为空 · The Service Loopback Group Member Interface parameter cannot be edited：业务环回组为只读字段 · A minimum of one selected interface has been assigned to a service loopback group：指定的接口中存在已加入业务环回组的接口 · Please specify a switching device name：交换设备名称不能为空 · You can specify only one sampling rate for a telemetry stream profile：一个Telemetry Stream下仅支持指定一个采样率 · You can specify only one service loopback group member interface：业务环回组接口至多配置1个 · The policy ID cannot be empty：policy ID不能为空 · The policy ID does not exist：policy ID不存在 |
|
关键字 |
UPDATE_TELEMETRY_STREAM_OP |
|
日志内容 |
Updated telemetry stream profile: $1 |
|
参数解释 |
$1：Telemetry stream信息 |
|
举例 |
Updated telemetry stream profile: ID : 47ae87b0-f7f2-4fd9-bf15-93fb78033de2 Name: 3 deviceIpList: [192.168.67.204] sourceIp: 192.168.67.204 sourcePort: 12 collectorId: Id[value=3d9f3712-54dc-4d2a-af8a-e8ab8438a4da] collectorName: 1 serviceLoopbackInterfaceNames: [] policies: [ id : Id[value=44fe2a6d-7712-4a5a-a1a5-ee8d8c373f0d] interfaceNames : [WGE1/0/1, WGE1/0/2, WGE1/0/3] sampleRate: 3 telemetryStreamId: Id[value=47ae87b0-f7f2-4fd9-bf15-93fb78033de2]]. |
|
日志说明 |
用户进行了更新Telemetry stream的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The name is required and cannot exceed 255 characters.：名称字段超过255个字符 · The source ip is required.：源ip地址为必选 · Only IPv4 is supported.：源ip地址仅支持IPv4 · The source port is required.：源端口为必选 · The port number range is 0 to 65535.：源端口大小为0至65535 · The collector ID is required：采集器ID为必选 · The collector does not exist.：指定的采集器不存在 · The collector has no ports.:指定的采集器没有端口 · The interface doesn't exist or illegal.：指定的接口不存在或者非法 · The interface name or sampling rate is required.：采样率和接口名称为必选 · The sampling rate is required.：采样率为必选 · The sampling interval value must be in the range of 0 to 15.：采样率的取值范围为0至15 · The device list cannot be empty.：交换设备不允许为空 · The switching device does not exist.：交换设备不存在 · The switching device is not active.：替换设备序列号不能为空 · The switching device is not active.：交换设备未激活 · The switching device has already been bound on INT or Telemetry Stream.：交换设备已经被INT或者Telemetry Stream绑定 · The switching device not support Telemetry Stream.：交换设备不支持TelemetryStream · Failed to modify the configuration item..：修改配置项失败 · Invalid JSON format：无效的JSON格式 · Internal error：内部错误 · The interface name and sampling rate is required：接口名称或者采样率不能为空 · The Service Loopback Group Member Interface parameter cannot be edited：业务环回组为只读字段 · A minimum of one selected interface has been assigned to a service loopback group：指定的接口中存在已加入业务环回组的接口 · Please specify a switching device name：交换设备名称不能为空 · You can specify only one sampling rate for a telemetry stream profile：一个Telemetry Stream下仅支持指定一个采样率 · You can specify only one service loopback group member interface：业务环回组接口至多配置1个 · The policy ID cannot be empty：policy ID不能为空 · The policy ID does not exist：policy ID不存在 |
|
关键字 |
DEL_TELEMETRY_STREAM_OP |
|
日志内容 |
Deleted telemetry stream profile “$1”. |
|
参数解释 |
$1：Telemetry stream的名称 |
|
举例 |
Deleted telemetry stream profile “3”. |
|
日志说明 |
用户进行了删除Telemetry stream的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · Internal error：内部错误 · The configuration item does not exist.：指定的配置项不存在 |
|
关键字 |
CREATE_NET_ANALYSIS_OP |
|
日志内容 |
Added intelligent analytics $1. |
|
参数解释 |
$1：智能分析信息 |
|
举例 |
Added intelligent analytics { operateId=66c5e979-68f7-4da6-b626-b4c02b979922', fabricId='Id [ value=255327d5-619a-4ac9-b3ff-d8a10b148bb2 ]', netAnalysisRuleList=[ SeerengineNetAnalysisRule { name='rule3', protocol=UDP, ipVersion=IPV4, sourceIP='7.7.7.7/24', destinationIP='8.8.8.8/24' }, SeerengineNetAnalysisRule { name='rule2', protocol=UDP, ipVersion=IPV4, sourceIP='3.3.3.3/24', destinationIP='4.4.4.4/24' } ] }. |
|
日志说明 |
· 若指定Fabric下未开启智能分析功能，则用户进行了开启智能分析功能并配置相关参数的操作 · 若指定Fabric下已开启智能分析功能，则用户进行了配置相关参数的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · You must specify a fabric ID：Fabric ID不能为空 · Please check the rule list for duplicate rules：规则列表中存在重复的规则 · The name cannot exceed 255 characters：名称最长255个字符 · You must specify the IP version of the rule as IPv4：规则的IP版本不能为空，必须为IPv4 · Invalid fabric ID：无效的Fabric ID · The name cannot exceed 255 characters：名称最长255个字符 · The value for the global_enable field can only be true or false, case sensitive：global_enable字段取值必须为true或false，区分大小写 · Failed to edit the value for the global_enable field：global_enable字段修改失败 · A fabric already exists with the specified ID：指定的Fabric ID已存在 · You must specify the IP version of the rule and must be IPv4：规则的IP版本不能为空，必须为IPv4 · You must specify the source IP address, destination IP address, or both in each rule：规则的源IP地址和目的IP地址不能同时为空 · You must specify the protocol type of the rule and must be UDP：规则的协议类型不能为空，必须为UDP · The fabric ID does not exist：指定的Fabric ID不存在 · The fabric has configured：指定的fabric已经被配置了 · The global has configured：RoceV2的全局开关已经被配置了 · You cannot configure rules when intelligent analytics is disabled：智能分析开关处于关闭状态时，不允许配置规则 · The collector with the specified name already exists：指定名称的采集器已存在 · The netanalysis configs is confict with ai ecn mode：智能分析配置和AI ECN模式冲突 · This fabric ID not contains one device：指定的Fabric ID不存在设备 · This fabric ID not contains this device IP：指定的Fabric ID不包含该设备 · The device type or device role is not supported：不支持该设备类型或角色 |
|
关键字 |
DELETE_NET_ANALYSIS_OP |
|
日志内容 |
Deleted intelligent analytics for fabric $1. |
|
参数解释 |
$1：智能分析对应的Fabric信息 |
|
举例 |
Deleted intelligent analytics for fabric Id[value=255327d5-619a-4ac9-b3ff-d8a10b148bb2]. |
|
日志说明 |
用户进行了关闭指定Fabric下智能分析功能的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · You must specify a fabric ID：Fabric ID不能为空 · Invalid fabric ID：无效的Fabric ID · The netanalysis configs is confict with ai ecn mode：智能分析配置和AI ECN模式冲突 · This fabric ID not contains this device IP：指定的Fabric ID不包含该设备 |
|
关键字 |
CREATE_ROUTER_POLICY_OP |
|
日志内容 |
Created router policy “$1”. |
|
参数解释 |
$1：ROUTER策略参数体 |
|
举例 |
Created router policy policyId:[7a570d3c-89ab-473c-9059-534aa1164a08] tenantId:[ffffffff-0000-0000-0000-000000000001] routerId:[ a78ab377-e0bd-4d24-acc3-d4f157a978c3]. Traffic policies:[ ID:[3a220c89-a6b3-464f-b3e9-ea9e6cf317ea] Name:[1] Remark:[null] Classifier ID:[Id[value=30750e59-afb5-494d-8847-756a0f6c0836]] Rate limit profile ID:[null] Mirroring destination profile ID:[null] Local mirror interface names:[null] direction:[IN]]. taasRemarkLocalQos:[TaasRemarkLocalQos{qosLocalId='1'}]] |
|
日志说明 |
用户进行了创建ROUTER策略的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The specified router policy already exists：该ROUTER策略已经存在 · The specified tenant does not exist：指定的租户不存在 · The tenant is required：未指定租户 · You cannot edit the tenant_id：租户不允许修改 · The router_id parameter is required：缺少参数router_id · The router_id parameter is invalid：参数router_id非法 · The tenant_id parameter is required：缺少参数tenant_id · The tenant_id parameter is invalid：参数tenant_id非法 · The classifier_id parameter is required：缺少参数classifier_id · The classifier_id parameter is invalid：参数classifier_id非法 · The name parameter is required：缺少参数name · The direction parameter is required：缺少参数direction · The cloud region name cannot exceed 255 characters：云区域名称字段长度不能超过255个字符 · The tenant of classifier is required：分类器中缺少租户属性 · The service does not exist：该服务不存在 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The specified classifier does not exist：指定的分类器不存在 · The specified direction is not supported：指定的方向不支持 · You have no privilege to perform this operation：用户无权限执行此操作 · The qosLocalId parameter is required：缺少参数qos_id · The qosLocalId parameter is invalid：参数qosLocalId非法 · On the same device, the physical port policy created by using the DC controller is mutually exclusive with that created by another component：同一设备，DC控制组件创建的物理端口策略与其他组件创建的物理端口策略互斥 · A router policy cannot contain duplicate traffic behaviors：ROUTER策略下的流量行为重复 · The router policy has been configured on the same device：相同设备上已经配置了对应的ROUTER策略 |
|
关键字 |
UPDATE_ROUTER_POLICY_OP |
|
日志内容 |
Updated router policy “$1”. |
|
参数解释 |
$1：ROUTER策略参数体 |
|
举例 |
Updated router policy policyId:[7a570d3c-89ab-473c-9059-534aa1164a08] tenantId:[ffffffff-0000-0000-0000-000000000001] Traffic policies:[ ID:[3a220c89-a6b3-464f-b3e9-ea9e6cf317ea] Name:[1] Remark:[null] Classifier ID:[Id[value=30750e59-afb5-494d-8847-756a0f6c0836]] Rate limit profile ID:[null] Mirroring destination profile ID:[null] Local mirror interface names:[null] direction:[IN]]. taasRemarkLocalQos:[TaasRemarkLocalQos{qosLocalId='1'}]] |
|
日志说明 |
用户进行了修改ROUTER策略的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The specified router policy already exists：该ROUTER策略已经存在 · The specified tenant does not exist：指定的租户不存在 · The tenant is required：未指定租户 · You cannot edit the tenant_id：租户不允许修改 · You cannot edit the router_id：租户不允许修改 · The tenant_id parameter is required：缺少参数tenant_id · The tenant_id parameter is invalid：参数tenant_id非法 · The classifier_id parameter is required：缺少参数classifier_id · The classifier_id parameter is invalid：参数classifier_id非法 · The name parameter is required：缺少参数name · The direction parameter is required：缺少参数direction · The cloud region name cannot exceed 255 characters：云区域名称字段长度不能超过255个字符 · The tenant of classifier is required：分类器中缺少租户属性 · The service does not exist：该服务不存在 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The specified classifier does not exist：指定的分类器不存在 · The specified direction is not supported：指定的方向不支持 · You have no privilege to perform this operation：用户无权限执行此操作 · The qosLocalId parameter is required：缺少参数qos_id · The qosLocalId parameter is invalid：参数qosLocalId非法 · The vrf_name field cannot be edited：vrf_name字段不允许修改 · You cannot edit a physical port policy that is created by using a component except the DC controller：非DC控制组件创建的物理端口策略不支持修改 · A router policy cannot contain duplicate traffic behaviors：ROUTER策略下的流量行为重复 |
|
关键字 |
DELETE_ROUTER_POLICY_OP |
|
日志内容 |
Deleted router policy “$1” "$2" |
|
参数解释 |
$1：ROUTER ID $2：策略ID |
|
举例 |
Deleted router policy a78ab377-e0bd-4d24-acc3-d4f157a978c3 22103cb9-5d77-4b64-8869-6659847d6a59. |
|
日志说明 |
用户进行了删除虚拟路由器策略的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The router_id parameter is invalid：参数router_id非法 · The policy_id parameter is invalid：参数policy_id非法 · The service does not exist：该服务不存在 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · You have no privilege to perform this operation：用户无权限执行此操作 · You cannot delete a physical port policy that is created by using a component except the DC controller：非DC控制组件创建的物理端口策略不支持删除 |
|
关键字 |
CREATE_ECMP_MODE_OP |
|
日志内容 |
Created ECMP mode “$1”. |
|
参数解释 |
$1：等价路由模式信息 |
|
举例 |
Created ECMP mode Device ips: ["192.168.148.126","192.168.148.136"] Ecmp mode: Spray Flowset inactive time: null |
|
日志说明 |
用户进行了创建等价路由模式的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The flowset inactive time is supported only in Eligible ECMP mode：Flowset inactive time只在ECMP模式为Eligible的时候有效。 · Please specify a device：设备不能为空 · The configuration already exists：配置项已存在 · The device has been specified：设备不能重复 · The flowset inactive time value is out of range 16~3200：Flowset inactive time的值应该在16～32000之间 |
|
关键字 |
UPDATE_ECMP_MODE_OP |
|
日志内容 |
Updated ECMP mode “$1”. |
|
参数解释 |
$1：等价路由模式信息 |
|
举例 |
Updated ECMP mode Id: 4da5ff2c-b824-493d-9035-82f1d0fe474f Device ip: 192.168.148.136 Ecmp mode: Eligible Flowset_inactive_time: 555 |
|
日志说明 |
用户进行了修改等价路由模式的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The flowset inactive time is supported only in Eligible ECMP mode：Flowset inactive time只在ECMP模式为Eligible的时候有效。 · The flowset inactive time value is out of range 16~3200：Flowset inactive time的值应该在16～32000之间 · The configuration item does not exist：指定的配置项不存在 · The specified device doesn't exist：指定的设备不存在 · The device is inactive：设备未激活 |
|
关键字 |
DELETE_ECMP_MODE_OP |
|
日志内容 |
Deleted ECMP mode “$1” |
|
参数解释 |
$1：等价路由模式ID |
|
举例 |
Deleted ECMP mode ID: a78ab377-e0bd-4d24-acc3-d4f157a978c3. |
|
日志说明 |
用户进行了删除等价路由模式的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The router_id parameter is invalid：参数router_id非法 · The policy_id parameter is invalid：参数policy_id非法 · The service does not exist：该服务不存在 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · You have no privilege to perform this operation：用户无权限执行此操作 · You cannot delete a physical port policy that is created by using a component except the DC controller：非DC控制组件创建的物理端口策略不支持删除 |
本节介绍SENC模块输出的操作日志信息。
|
关键字 |
CREATE_SUBSCRIBE_OP |
|
日志内容 |
Created subscribe $1 |
|
参数解释 |
$1：控制组件注册信息 |
|
举例 |
Created subscribe id: e3936eb4-6ec9-49b4-92f7-b422b734f1e6, event_list: [ { event : EPG, filter : [campus], callback_url : http://campus.campus.svc:80/campus/dcepg/v1.0 } ], description : campus |
|
日志说明 |
用户进行了注册控制组件信息的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · You have no privilege to perform this operation：用户无权限执行此操作 · Invalid JSON format：无效的请求格式 · The controller has not finished initialization：控制组件SCM状态未完全恢复 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The service is disabled：服务未启动 · Unknown internal server error：服务内部错误 · Request parameter error：请求参数错误 · This operation is not allowed：没有访问权限 · This operation has no permissions：禁止访问 · This operation is conflict：操作冲突 · The specified resource doesn't exist：指定的资源不存在 · No registration information found for the controller：控制组件的注册信息不存在 · Registration information for the controller already exist：控制组件的注册信息已存在 |
|
关键字 |
DELETE_SUBSCRIBE_OP |
|
日志内容 |
Deleted subscribe $1 |
|
参数解释 |
$1：控制组件注册信息 |
|
举例 |
Deleted subscribe subscribe1 |
|
日志说明 |
用户进行了删除指定注册信息的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · You have no privilege to perform this operation：用户无权限执行此操作 · Invalid JSON format：无效的请求格式 · The controller has not finished initialization：控制组件SCM状态未完全恢复 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The service is disabled：服务未启动 · No registration information found for the controller：控制组件的注册信息不存在 |
本节介绍服务链模块输出的操作日志信息。
|
关键字 |
CREATE_SC_OP |
|
日志内容 |
Created service chain $1 |
|
参数解释 |
$1：服务链配置信息 |
|
举例 |
Created service chain ID: 2f01ad00-e54e-48c2-8e79-2beb78f25237 Name: insertion0001 Base: Source context name: net10 Destination context name: net11 Service nodes: [{ Instance name: 6263 Bypass : NONE },{ Instance name: 8283 Bypass : NONE }] Enable detect: false |
|
日志说明 |
用户进行了创建服务链的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The firewall service has not been found：防火墙服务未启动 · The load balancer service has not been found：负载均衡器服务未启动 · Configuration recovery is in progress：配置正在恢复中 · The controller is not the active leader：该控制组件不是主Leader · The operation requires the administrator privilege：您需要管理员权限才能执行此操作 · The service chain already exists：指定的服务链已存在 · The specified context doesn't exist：服务链引用的流量特征组不存在 · The specified tenant doesn't exist：指定的租户不存在 · The service instance doesn't exist：服务实例不存在 · The tenant IDs for the service chain and the specified service instance are different：服务链与指定服务实例的租户ID不匹配 · The mode of the service instance is not SERVICE_CHAIN：服务实例的模式不是SERVICE_CHAIN · The tenant IDs for the service chain and the specified source or destination context are different：服务链的租户ID与指定源特征组或目的特征组的租户ID不匹配 · The source and destination contexts are already used by another service chain：源特征组和目的特征组的组合已经被其他服务链使用 · The types of the source and destination contexts cannot both be external：源特征组和目的特征组类型不能同时为external · The service instance is already used by another service chain：服务链引用的服务实例已经被其他服务链引用 · Only one firewall service instance is allowed in a service chain：一条服务链只能包含一个防火墙实例 · Only one loadbalancer service instance is allowed in a service chain：一条服务链只能包含一个负载均衡器实例 · The name cannot exceed 255 characters：服务链名称不能超过255个字符 · Failed to obtain fabric information：获取Fabric信息失败 · A service instance of the PBR firewall type cannot form a service chain with service instances of other types：PBR防火墙类型的服务节点不支持与其他类型服务节点组成一条服务链 · A service chain can contain a maximum of 1 PBR firewall service instances：一条服务链最多包含一个PBR防火墙实例 · The resource access template corresponding to the PBR firewall service instance has configuration errors or does not exist：PBR防火墙服务实例对应的资源接入模板配置错误或不存在 · Not enough VLAN pools, VXLAN pools, or address pools in the resource access template corresponding to the PBR firewall service instance：PBR防火墙服务实例对应的资源接入模板中VLAN池、VXLAN池或地址池不足 · The subnets of the vRouter to which the source context belongs cannot include vPort IP addresses of service instances：源特征组所属虚拟路由器下的子网不能包含服务节点对应的虚拟端口IP地址 · The subnets of the vRouter to which the destination context belongs cannot include vPort IP addresses of service instances：目的特征组所属虚拟路由器下的子网不能包含服务节点对应的虚拟端口IP地址 · The external subnet of the source and destination contexts cannot be empty when both source and destination contexts are external contexts：当源目的特征组类型均为External时，源目的特征组的外部网络子网不能为空 · A service instance of the Third-party type cannot form a service chain with service instances of other types：第三方服务节点不支持与其他类型服务节点组成一条服务链 · A PBRFirewall or PBRLoadbalance service instance cannot form a service chain with service instances of other types：PBR类型（PBRFirewall和PBRLoadbalance）的服务实例不支持与其它类型的服务实例组成一条服务链 · The destination context cannot be external when the service type is PBRLoadbalance：当指定PBRLoadbalance类型的服务实例时，目的特征组不能为external · The context ID cannot be specified in any type：特征组类型为any时，不能指定特征组ID · Unknown internal service error：未知的内部服务器错误 · You have no privilege to perform this operation：用户无权限执行此操作 · Cannot configure the subnet as a context member because the subnet has been bound to a vRouter enabled with multicast network capabilities：服务链的流量特性组使用的虚拟子网已经绑定了使能组播网络的虚拟路由器 · When firewall service nodes exist in the service chain,make sure all service nodes use the two-arm connection mode：当服务链存在防火墙服务节点时，服务节点的连接模式必须都为双臂 · You cannot create a vRouter link of the normal, PBR, or NBAC type, because the local or remote vRouter on the link has been bound to both a centralized vNetwork and an IPv6 subnet：当虚拟路由器连接为Normal、PBR或NBAC类型时，本端和对端虚拟路由器下不能同时绑定集中式虚拟链路层网络和IPv6子网 · The source or destination context of the service chain cannot be any：服务链的源/目的特征组不能为any · Duplicate external network CIDRs exist：外网网段地址中存在重复的网段地址 · You can specify up to 12 external network CIDRs：外网网段地址数量不允许超过12个 · Invalid external network CIDRs：无效的外网网段地址 · The node is a third-party node configured with IPsec or NAT. A service chain for north-south traffic can have a maximum of one such node：配置了IPsec或NAT功能的第三方服务节点在南北向服务链中至多存在一个 · The service chain contains a third-party node with IPsec or NAT configured and an external context. Make sure no NAT-capable node exists between them：配置了IPsec或NAT功能的第三方服务节点与External流量特征组之间不允许存在有地址转换功能的节点 · The node is a third-party node configured with IPsec or NAT. It can be used only by a service chain for north-south traffic：配置了IPsec或NAT功能的第三方服务节点只能应用于南北向服务链 · The destination context can't be External when the service type is PBRLoadbalance：当指定PBRLoadbalance类型的服务实例时，目的特征组不能为External · The external network CIDRs of the source and destination contexts cannot be both empty when both source and destination contexts are external contexts：当源目的特征组类型均为External时，源目的特征组的外网网段不能同时为空 · The external subnet of the source and destination contexts cannot be empty when both source and destination contexts are external contexts：当源目的特征组类型均为External时，源目的特征组的外部网络子网不能为空 · Cannot configure service chains for the vRouter, because the vRouter has been configured with IPv4 or IPv4&IPv6 application policies：同一虚拟路由器下不可同时配置IPv4或IPv4&IPv6的应用策略和服务链 · The segment ID is out of range：Segment ID超出范围 · The source context already has onboarded vPorts in an associated external network：源流量特征组对应的外部网络中存在已上线虚拟端口 · The destination context already has onboarded vPorts in an associated external network：目的流量特征组对应的外部网络中存在已上线虚拟端口 · The source context has a vRouter bound to a vPort in an external network：源流量特征组对应的虚拟路由器已绑定外部网络的虚拟端口 · The destination context has a vRouter bound to a vPort in an external network：目的流量特征组对应的虚拟路由器已绑定外部网络的虚拟端口 · The source and destination contexts overlap with the source and destination contexts used by another service chain：该服务链引用的源和目的流量特征组的组合与其他服务链有重叠 · The context uses primary/backup gateway deployment mode. Make sure the associated vRouter is bound to two gateway members or external subnets：流量特征组为主备出口模式时，关联的虚拟路由器必须绑定两个出口网关成员或两个外网子网 · The context uses single gateway deployment mode. Make sure the associated vRouter is bound to one gateway member or external subnet：流量特征组为单出口模式时，关联的虚拟路由器必须绑定一个出口网关成员或一个外网子网 · One or more selected third-party service instances are invalid：已选服务中存在无效的第三方服务实例 · PBR firewall service instances of a service chain must belong to different virtual devices：一条服务链的每个PBR防火墙服务实例所在的虚拟设备不能相同 · Failed to bind the context to the service chain, because a vRouter associated with this context has been bound to an external EPG containing external network CIDR 0.0.0.0/0：服务链关联流量特征组失败，该流量特征组对应的虚拟路由器已被External类型且外网网段包含0.0.0.0/0的EPG绑定 · The service chain does not support DNAT nodes：服务链不支持使用DNAT节点 · Manual bypass and auto bypass cannot be both configured：手动旁路和自动旁路不能同时配置 · The ingress_port_ip_status is read only：服务实例入接口vPort的IPv4地址状态为只读字段 · The egress_port_ip_status is read only：服务实例出接口vPort的IPv4地址状态为只读字段 · A resource is required to be bound with each PBRFirewall or PBRLoadbalance service instance：每个PBR类型（PBRFirewall和PBRLoadbalance）的服务实例均需绑定资源 · The resource access template corresponding to the PBRFirewall or PBRLoadbalance service instance has configuration errors or does not exist：PBR类型（PBRFirewall和PBRLoadbalance）的服务实例对应的资源接入模板配置错误或不存在 · A service chain can contain a maximum of 16 service instances：一条服务链最多包含16个服务实例 · A service chain can contain a maximum of three service instances when the service chain path ID format is 24-bit：服务链定制化Path ID格式为24比特，一条服务链最多包含3个服务实例 · A service chain can contain a maximum of seven service instances when the service chain path ID format is 16-bit：服务链定制化Path ID格式为16比特，一条服务链最多包含7个服务实例 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · Failed to create a vRouter link in the service chain, because the associated vRouters have already established a vRouter link of the normal type：服务链生成的虚拟路由器连接与已存在的虚拟路由器连接冲突 · VRF {%s} automatically generated for the service chain has been specified for a vRouter. Please delete that vRouter：服务链自动生成的VRF{%s}与已有VRF重复，请前往虚拟路由器页面删除对应VRF的虚拟路由器 · The devices in the resource access template belong to different fabrics：资源接入模板下设备属于不同的Fabric |
|
关键字 |
UPDATE_SC_OP |
|
日志内容 |
Updated service chain $1 |
|
参数解释 |
$1：服务链配置信息 |
|
举例 |
Updated service chain ID: 2f01ad00-e54e-48c2-8e79-2beb78f25237 Name: insertion0001 Base: Source context name: net10 Destination context name: net11 Service nodes: [{ Instance name: 6263 Bypass : NONE },{ Instance name: 8283 Bypass : NONE }] Enable detect: false |
|
日志说明 |
用户进行了修改服务链的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service of the service chain has not been found：服务链服务未启动 · Configuration recovery is in progress：配置正在恢复中 · The controller is not the active leader：该控制组件不是主Leader · The operation requires the administrator privilege：您需要管理员权限才能执行此操作 · The configuration item doesn't exist：配置项不存在 · The specified context doesn't exist：服务链引用的流量特征组不存在 · The service instance doesn't exist：服务实例不存在 · The tenant IDs for the service chain and the specified service instance are different：服务链与指定服务实例的租户ID不匹配 · The mode of the service instance is not SERVICE_CHAIN：服务实例的模式不是SERVICE_CHAIN · The tenant IDs for the service chain and the specified source or destination context are different：服务链的租户ID与指定源特征组或目的特征组的租户ID不匹配 · The source and destination contexts are already used by another service chain：源特征组和目的特征组的组合已经被其他服务链使用 · The types of the source and destination contexts cannot both be external：源特征组和目的特征组类型不能同时为external · The service instance is already used by another service chain：服务链引用的服务实例已经被其他服务链引用 · Only one firewall service instance is allowed in a service chain：一条服务链只能包含一个防火墙实例 · Only one loadbalancer service instance is allowed in a service chain：一条服务链只能包含一个负载均衡器实例 · The name cannot exceed 255 characters：服务链名称不能超过255个字符 · Failed to obtain fabric information：获取Fabric信息失败 · A service instance of the PBR firewall type cannot form a service chain with service instances of other types：PBR防火墙类型的服务节点不支持与其他类型服务节点组成一条服务链 · A service chain can contain a maximum of 1 PBR firewall service instances：一条服务链最多包含一个PBR防火墙实例 · The resource access template corresponding to the PBR firewall service instance has configuration errors or does not exist：PBR防火墙服务实例对应的资源接入模板配置错误或不存在 · Not enough VLAN pools, VXLAN pools, or address pools in the resource access template corresponding to the PBR firewall service instance：PBR防火墙服务实例对应的资源接入模板中VLAN池、VXLAN池或地址池不足 · The subnets of the vRouter to which the source context belongs cannot include vPort IP addresses of service instances：源特征组所属虚拟路由器下的子网不能包含服务节点对应的虚拟端口IP地址 · The subnets of the vRouter to which the destination context belongs cannot include vPort IP addresses of service instances：目的特征组所属虚拟路由器下的子网不能包含服务节点对应的虚拟端口IP地址 · The external subnet of the source and destination contexts cannot be empty when both source and destination contexts are external contexts：当源目的特征组类型均为External时，源目的特征组的外部网络子网不能为空 · The ID cannot be modified：ID不允许修改 · The tenant ID cannot be modified：租户ID不允许修改 · The routerlinks ID cannot be modified：虚拟路由器连接ID不允许修改 · A service instance of the Third-party type cannot form a service chain with service instances of other types：第三方服务节点不支持与其他类型服务节点组成一条服务链 · A PBRFirewall or PBRLoadbalance service instance cannot form a service chain with service instances of other types：PBR类型（PBRFirewall和PBRLoadbalance）的服务实例不支持与其它类型的服务实例组成一条服务链 · The destination context cannot be external when the service type is PBRLoadbalance：当指定PBRLoadbalance类型的服务实例时，目的特征组不能为external · The context ID cannot be specified in any type：特征组类型为any时，不能指定特征组ID · Unknown internal service error：未知的内部服务器错误 · You have no privilege to perform this operation：用户无权限执行此操作 · Cannot configure the subnet as a context member because the subnet has been bound to a vRouter enabled with multicast network capabilities：服务链的流量特性组使用的虚拟子网已经绑定了使能组播网络的虚拟路由器 · When firewall service nodes exist in the service chain,make sure all service nodes use the two-arm connection mode：当服务链存在防火墙服务节点时，服务节点的连接模式必须都为双臂 · You cannot create a vRouter link of the normal, PBR, or NBAC type, because the local or remote vRouter on the link has been bound to both a centralized vNetwork and an IPv6 subnet：当虚拟路由器连接为Normal、PBR或NBAC类型时，本端和对端虚拟路由器下不能同时绑定集中式虚拟链路层网络和IPv6子网 · The source or destination context of the service chain cannot be any：服务链的源/目的特征组不能为any · Duplicate external network CIDRs exist：外网网段地址中存在重复的网段地址 · You can specify up to 12 external network CIDRs：外网网段地址数量不允许超过12个 · Invalid external network CIDRs：无效的外网网段地址 · The node is a third-party node configured with IPsec or NAT. A service chain for north-south traffic can have a maximum of one such node：配置了IPsec或NAT功能的第三方服务节点在南北向服务链中至多存在一个 · The service chain contains a third-party node with IPsec or NAT configured and an external context. Make sure no NAT-capable node exists between them：配置了IPsec或NAT功能的第三方服务节点与External流量特征组之间不允许存在有地址转换功能的节点 · The node is a third-party node configured with IPsec or NAT. It can be used only by a service chain for north-south traffic：配置了IPsec或NAT功能的第三方服务节点只能应用于南北向服务链 · The destination context can't be External when the service type is PBRLoadbalance：当指定PBRLoadbalance类型的服务实例时，目的特征组不能为External · The external network CIDRs of the source and destination contexts cannot be both empty when both source and destination contexts are external contexts：当源目的特征组类型均为External时，源目的特征组的外网网段不能同时为空 · The external subnet of the source and destination contexts cannot be empty when both source and destination contexts are external contexts：当源目的特征组类型均为External时，源目的特征组的外部网络子网不能为空 · Cannot configure service chains for the vRouter, because the vRouter has been configured with IPv4 or IPv4&IPv6 application policies：同一虚拟路由器下不可同时配置IPv4或IPv4&IPv6的应用策略和服务链 · The segment ID is out of range：Segment ID超出范围 · The source context already has onboarded vPorts in an associated external network：源流量特征组对应的外部网络中存在已上线虚拟端口 · The destination context already has onboarded vPorts in an associated external network：目的流量特征组对应的外部网络中存在已上线虚拟端口 · The source context has a vRouter bound to a vPort in an external network：源流量特征组对应的虚拟路由器已绑定外部网络的虚拟端口 · The destination context has a vRouter bound to a vPort in an external network：目的流量特征组对应的虚拟路由器已绑定外部网络的虚拟端口 · The source and destination contexts overlap with the source and destination contexts used by another service chain：该服务链引用的源和目的流量特征组的组合与其他服务链有重叠 · The context uses primary/backup gateway deployment mode. Make sure the associated vRouter is bound to two gateway members or external subnets：流量特征组为主备出口模式时，关联的虚拟路由器必须绑定两个出口网关成员或两个外网子网 · The context uses single gateway deployment mode. Make sure the associated vRouter is bound to one gateway member or external subnet：流量特征组为单出口模式时，关联的虚拟路由器必须绑定一个出口网关成员或一个外网子网 · One or more selected third-party service instances are invalid：已选服务中存在无效的第三方服务实例 · PBR firewall service instances of a service chain must belong to different virtual devices：一条服务链的每个PBR防火墙服务实例所在的虚拟设备不能相同 · Failed to bind the context to the service chain, because a vRouter associated with this context has been bound to an external EPG containing external network CIDR 0.0.0.0/0：服务链关联流量特征组失败，该流量特征组对应的虚拟路由器已被External类型且外网网段包含0.0.0.0/0的EPG绑定 · The service chain does not support DNAT nodes：服务链不支持使用DNAT · Manual bypass and auto bypass cannot be both configured：手动旁路和自动旁路不能同时配置 · The ingress_port_ip_status is read only：服务实例入接口vPort的IPv4地址状态为只读字段 · The egress_port_ip_status is read only：服务实例出接口vPort的IPv4地址状态为只读字段 · A resource is required to be bound with each PBRFirewall or PBRLoadbalance service instance：每个PBR类型（PBRFirewall和PBRLoadbalance）的服务实例均需绑定资源 · The resource access template corresponding to the PBRFirewall or PBRLoadbalance service instance has configuration errors or does not exist：PBR类型（PBRFirewall和PBRLoadbalance）的服务实例对应的资源接入模板配置错误或不存在 · A service chain can contain a maximum of 16 service instances：一条服务链最多包含16个服务实例 · A service chain can contain a maximum of three service instances when the service chain path ID format is 24-bit：服务链定制化Path ID格式为24比特，一条服务链最多包含3个服务实例 · A service chain can contain a maximum of seven service instances when the service chain path ID format is 16-bit：服务链定制化Path ID格式为16比特，一条服务链最多包含7个服务实例 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · Failed to create a vRouter link in the service chain, because the associated vRouters have already established a vRouter link of the normal type：服务链生成的虚拟路由器连接与已存在的虚拟路由器连接冲突 · The devices in the resource access template belong to different fabrics：资源接入模板下设备属于不同的Fabric |
|
关键字 |
DELETE_SC_OP |
|
日志内容 |
Deleted service chain $1 |
|
参数解释 |
$1：服务链名称 |
|
举例 |
Deleted service chain insertion1 |
|
日志说明 |
用户进行了删除服务链的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service of the service chain has not been found：服务链服务未启动 · Configuration recovery is in progress：配置恢复未完成 · The controller is not the active leader：该控制组件不是主Leader · The operation requires the administrator privilege：您需要管理员权限才能执行此操作 · The configuration item doesn't exist：配置项不存在 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
CREATE_CONTEXT_OP |
|
日志内容 |
Created context $1 |
|
参数解释 |
$1：流量特征组配置信息 |
|
举例 |
Created context ID: 0b9fe13b-094e-4341-9eeb-6bef8fed62a3 Name: net10 Context base: type: NETWORK Networks: [ 4d6c0aa4-15bf-497c-bea7-6d137317ee0f] |
|
日志说明 |
用户进行了创建流量特征组的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service of the service chain has not been found：服务链服务未启动 · Configuration recovery is in progress：配置正在恢复中 · The controller is not the active leader：该控制组件不是主Leader · The operation requires the administrator privilege：您需要管理员权限才能执行此操作 · The context already exists：指定的流量特征组已存在 · The specified tenant doesn't exist：指定的租户不存在 · The specified vPort doesn't exist：流量特征组引用的虚拟端口不存在 · The tenant IDs for the context and the specified vPort are different：流量特征组与指定虚拟端口的租户ID不匹配 · The specified vSubnet doesn't exist：流量特征组引用的虚拟子网不存在 · The tenant IDs for the context and the specified vSubnet are different：流量特征组与指定虚拟子网的租户ID不匹配 · The specified vNetwork doesn't exist：流量特征组引用的虚拟链路层网络不存在 · The tenant IDs for the context and the specified vNetwork are different：流量特征组与指定虚拟链路层网络的租户ID不匹配 · The specified external subnet does not exist：指定的外网子网不存在 · The specified subnet is not an external subnet：指定的子网不是外网子网 · The context uses single gateway deployment mode.Please specify one and only one external subnet, or do not specify any external subnets：单出口模式下，只能绑定一个外网子网，或者不指定任何外网子网 · The context uses primary/backup gateway deployment mode. Please specify two and only two external subnets, or do not specify any external subnets：主备出口模式下，只能绑定两个外网子网，或者不指定任何外网子网 · The context uses primary/backup gateway deployment mode. Make sure the associated vRouter is bound to two gateway members or external subnets：流量特征组为主备出口模式时，关联的虚拟路由器必须绑定两个出口网关成员或两个外网子网 · The context uses single gateway deployment mode. Make sure the associated vRouter is bound to one gateway member or external subnet：流量特征组为单出口模式时，关联的虚拟路由器必须绑定一个出口网关成员或一个外网子网 · The name cannot exceed 255 characters：流量特征组名称不能超过255个字符 · The specified IP address for the context of the Manual type cannot be broadcast, multicast, or loopback address：非法的IP地址或网段 · The vPort resource cannot be used because it is created by PBR service chain：PBR类型的vPort不能作为源目的特征组 · The subnet resource cannot be used because it is created by PBR service chain：PBR类型的Subnet不能作为源目的特征组 · The network resource cannot be used because it is created by PBR service chain：PBR类型的Network不能作为源目的特征组 · The external subnet cannot be configured as a context member when the context type is subnet：流量特征组类型为Subnet时，成员不能为外网子网 · You have no privilege to perform this operation：用户无权限执行此操作 · Duplicate external network CIDRs exist：外网网段地址中存在重复的网段地址 · You can specify up to 12 external network CIDRs：外网网段地址数量不允许超过12个 · Invalid external network CIDRs：无效的外网网段地址 · Only external contexts support exception CIDRs：仅External类型的流量特征组支持配置例外网段地址 · Make sure all specified exception CIDRs are valid：无效的例外网段地址 · Make sure the context does not have overlapping exception CIDRs：例外网段地址不允许重叠 · Exception CIDRs support only IPv4 addresses：例外网段地址仅支持IPv4 · The exception CIDRs must be within the ranges of the external network CIDRs：例外网段地址必须在外网网段地址中 · You can specify only the vRouter UUID for the context of the router type：Router类型特征组中只能引用虚拟路由器的UUID · Duplicate vRouter UUIDs exist：存在重复的虚拟路由器UUID · The tenant UUIDs for the context and the specified vRouter are different：流量特征组的租户UUID和虚拟路由器的租户UUID不匹配 · A PBR-type vRouter cannot be specified for a router-type context：PBR类型的虚拟路由器不能被Router类型的特征组引用 · A context cannot contain vPorts of external networks：流量特征组中不能包括外部网络的虚拟端口 · The vRouter must be a normal vRouter：指定的虚拟路由器只能选择NORMAL类型 · Make sure the selected external subnets have been bound to the vRouter specified for the context：外网子网成员必须绑定流量特征组指定的虚拟路由器 |
|
关键字 |
UPDATE_CONTEXT_OP |
|
日志内容 |
Updated context $1 |
|
参数解释 |
$1：流量特征组配置信息 |
|
举例 |
Updated context ID: 0b9fe13b-094e-4341-9eeb-6bef8fed62a3 Name: net10 Context base: type: NETWORK Networks: [ 4d6c0aa4-15bf-497c-bea7-6d137317ee0f] |
|
日志说明 |
用户进行了修改流量特征组的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service of the service chain has not been found：服务链服务未启动 · Configuration recovery is in progress：配置正在恢复中 · The controller is not the active leader：该控制组件不是主Leader · The operation requires the administrator privilege：您需要管理员权限才能执行此操作 · The configuration item doesn't exist：配置项不存在 · The context is being used by a service chain：指定的流量特征组正在被服务链使用 · The specified vPort doesn't exist：流量特征组引用的虚拟端口不存在 · The tenant IDs for the context and the specified vPort are different：流量特征组与指定虚拟端口的租户ID不匹配 · The specified vSubnet doesn't exist：流量特征组引用的虚拟子网不存在 · The tenant IDs for the context and the specified vSubnet are different：流量特征组与指定虚拟子网的租户ID不匹配 · The specified vNetwork doesn't exist：流量特征组引用的虚拟链路层网络不存在 · The tenant IDs for the context and the specified vNetwork are different：流量特征组与指定虚拟链路层网络的租户ID不匹配 · The specified external subnet does not exist：指定的外网子网不存在 · The specified subnet is not an external subnet：指定的子网不是外网子网 · The context uses single gateway deployment mode.Please specify one and only one external subnet, or do not specify any external subnets：单出口模式下，只能绑定一个外网子网，或者不指定任何外网子网 · The context uses primary/backup gateway deployment mode. Please specify two and only two external subnets, or do not specify any external subnets：主备出口模式下，只能绑定两个外网子网，或者不指定任何外网子网 · The context uses primary/backup gateway deployment mode. Make sure the associated vRouter is bound to two gateway members or external subnets：流量特征组为主备出口模式时，关联的虚拟路由器必须绑定两个出口网关成员或两个外网子网 · The context uses single gateway deployment mode. Make sure the associated vRouter is bound to one gateway member or external subnet：流量特征组为单出口模式时，关联的虚拟路由器必须绑定一个出口网关成员或一个外网子网 · The name cannot exceed 255 characters：流量特征组名称不能超过255个字符 · The ID cannot be modified：ID不允许修改 · The tenant ID cannot be modified：租户ID不允许修改 · The vPort resource cannot be used because it is created by PBR service chain：PBR类型的vPort不能作为源目的特征组 · The subnet resource cannot be used because it is created by PBR service chain：PBR类型的Subnet不能作为源目的特征组 · The network resource cannot be used because it is created by PBR service chain：PBR类型的Network不能作为源目的特征组 · You have no privilege to perform this operation：用户无权限执行此操作 · Cannot configure the subnet as a context member because the subnet has been bound to a vRouter enabled with multicast network capabilities：服务链的流量特性组使用的虚拟子网已经绑定了使能组播网络的虚拟路由器 · The external subnet cannot be configured as a context member when the context type is subnet：流量特征组类型为Subnet时，成员不能为外网子网 · The source or destination context of the service chain cannot be any：服务链的源/目的特征组不能为any · Duplicate external network CIDRs exist：外网网段地址中存在重复的网段地址 · You can specify up to 12 external network CIDRs：外网网段地址数量不允许超过12个 · Invalid external network CIDRs：无效的外网网段地址 · The destination context can't be External when the service type is PBRLoadbalance：当指定PBRLoadbalance类型的服务实例时，目的特征组不能为External · The external network CIDRs of the source and destination contexts cannot be both empty when both source and destination contexts are external contexts：当源目的特征组类型均为External时，源目的特征组的外网网段不能同时为空 · The external subnet of the source and destination contexts cannot be empty when both source and destination contexts are external contexts：当源目的特征组类型均为External时，源目的特征组的外部网络子网不能为空 · The context has been specified for a service chain. Make sure the context members do not use the vRouters of any IPv4 or IPv4 & IPv6 application policies：已被引用的流量特征组其成员的虚拟路由器不能与IPv4或IPv4 & IPv6的应用策略的虚拟路由器相同 · Only external contexts support exception CIDRs：仅External类型的流量特征组支持配置例外网段地址 · Make sure all specified exception CIDRs are valid：无效的例外网段地址 · Make sure the context does not have overlapping exception CIDRs：例外网段地址不允许重叠 · Exception CIDRs support only IPv4 addresses：例外网段地址仅支持IPv4 · The exception CIDRs must be within the ranges of the external network CIDRs：例外网段地址必须在外网网段地址中 · You can specify only the vRouter UUID for the context of the router type：Router类型特征组中只能引用虚拟路由器的UUID · Duplicate vRouter UUIDs exist：存在重复的虚拟路由器UUID · The tenant UUIDs for the context and the specified vRouter are different：流量特征组的租户UUID和虚拟路由器的租户UUID不匹配 · A PBR-type vRouter cannot be specified for a router-type context：PBR类型的虚拟路由器不能被Router类型的特征组引用 · A context cannot contain vPorts of external networks：流量特征组中不能包括外部网络的虚拟端口 · The source and destination contexts overlap with the source and destination contexts used by another service chain：该服务链引用的源和目的流量特征组的组合与其他服务链有重叠 · Failed to change the context type, because the context has been used by a service chain and an associated vRouter has been bound to an external EPG containing external network CIDR 0.0.0.0/0：流量特征组类型修改失败，该流量特征组已被服务链使用，且流量特征组对应的虚拟路由器已被External类型且外网网段包含0.0.0.0/0的EPG绑定 · The vRouter must be a normal vRouter：指定的虚拟路由器只能选择NORMAL类型 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
DELETE_CONTEXT_OP |
|
日志内容 |
Deleted context $1 |
|
参数解释 |
$1：流量特征组名称 |
|
举例 |
Deleted context context001 |
|
日志说明 |
用户进行了删除流量特征组的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service of the service chain has not been found：服务链服务未启动 · Configuration recovery is in progress：配置正在恢复中 · The controller is not the active leader：该控制组件不是主Leader · The operation requires the administrator privilege：您需要管理员权限才能执行此操作 · The configuration item doesn't exist：配置项不存在 · The context is being used by a service chain：指定的流量特征组正在被服务链使用 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_SERVICE_PATH_OP |
|
日志内容 |
Created service path $1 |
|
参数解释 |
$1：服务路径配置信息 |
|
举例 |
Created service path ID: 945b4091-265d-45b7-bc83-f7099025903d Name: graph0001 Ip version: 4 Service nodes: [{ Instance name: 6263 Bypass : NONE },{ Instance name: 8283 Bypass : NONE }] Enable detect: false |
|
日志说明 |
用户进行了创建服务路径的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The firewall service has not been found：防火墙服务未启动 · The load balancer service has not been found：负载均衡器服务未启动 · Configuration recovery is in progress：配置正在恢复中 · The controller is not the active leader：该控制组件不是主Leader · The operation requires the administrator privilege：您需要管理员权限才能执行此操作 · The service chain already exists：指定的服务路径已存在 · The specified tenant doesn't exist：指定的租户不存在 · The service instance doesn't exist：服务实例不存在 · Invalid IP version：无效的IP版本 · When multiple service nodes exist in the service path, make sure all service nodes use the two-arm connection mode：当服务路径存在多个服务节点时，服务节点的连接模式必须都为双臂 · The service instance is already used by another service chain：服务路径引用的服务实例已经被其他服务路径引用 · Only one loadbalancer service instance is allowed in a service path：一条服务路径只能包含一个负载均衡器实例 · The name cannot exceed 255 characters：服务路径名称不能超过255个字符 · Failed to obtain fabric information：获取Fabric信息失败 · A resource is required to be bound with each PBRFirewall or PBRLoadbalance service instance：每个PBR类型（PBRFirewall和PBRLoadbalance）的服务实例均需绑定资源 · Duplicated service instances exist in the service path：该服务路径中存在重复的服务实例 · A service instance of the Third-party type cannot form a service path with service instances of other types：第三方服务节点不支持与其他类型服务节点组成一条服务路径 · A PBRFirewall or PBRLoadbalance service instance cannot form a service chain with service instances of other types：PBR类型（PBRFirewall和PBRLoadbalance）的服务实例不支持与其它类型的服务实例组成一条服务路径 · You cannot add a shared third-party service node to the service path：当服务节点为共享节点时，不能被应用到服务路径中 · Please specify a resource for the service node：服务节点未绑定资源 · Make sure the service node and the resource access template use the same connection mode：服务节点的连接模式和资源接入模板的连接模式必须相同 · Make sure the third-party service path and all service devices in it use the same IP version：第三方服务路径的IP版本必须与第三方服务设备的IP版本一致 · Make sure no EPGs contain any member IP address of the EPG automatically generated upon service path creation：服务路径自动生成的EPG的成员IP已存在 · Make sure a vRouter is bound to each of the subnets attached to the ingress and egress vPorts：第三方服务设备的出入虚拟端口所属子网没有绑定虚拟路由器 · Unknown internal service error：未知的内部服务器错误 · You have no privilege to perform this operation：用户无权限执行此操作 · A subnet of the third-party service device is not bound to a vNetwork：存在第三方服务设备的子网没有绑定虚拟链路层网络 · A subnet of the third-party service device is not bound to a vRouter：存在第三方服务设备的子网没有绑定虚拟路由器 · One or more selected third-party service instances are invalid：已选服务中存在无效的第三方服务实例 · The service path cannot contain both a third-party LB service node and a controller-managed LB service node：第三方负载均衡实例和被控制组件纳管的负载均衡实例不能在同一条服务路径上 · The service path does not support third-party service nodes with IPsec or SNAT settings：服务路径上不支持添加有IPsec和SNAT功能的第三方服务节点 · A service path can contain a maximum of 16 service instances：一条服务路径最多包含16个服务实例 · PBR firewall service instances of a service path must belong to different virtual devices：一条服务路径的每个PBR防火墙服务实例所在的虚拟设备不能相同 · The service path supports only one third-party service node with IPsec or NAT settings：已配置IPsec或NAT功能的第三方服务节点在服务路径中最多只能有一个 · The service path has a third-party service node with IPsec settings. You can specify the service path only in exception rules that contain an external source or destination EPG：指定服务路径已使用配置了IPsec功能的第三方服务节点，只能应用于源或目的EPG为External类型的例外规则 · The service path has a third-party service node with IPsec or NAT settings and an external EPG. You cannot add LB service nodes between them：服务路径中，已配置IPsec或NAT功能的第三方服务节点与External类型的EPG之间不允许存在LB类型的服务节点 · Make sure all third-party service instances in the service path are bound to the same vRouter：服务路径中的所有第三方服务实例必须属于同一虚拟路由器 · VRF (%s) automatically generated for the service path has been specified for a vRouter. Please delete that vRouter：服务路径自动生成的VRF：%s与已有VRF重复，请前往虚拟路由器页面删除对应VRF的虚拟路由器 · Manual bypass and auto bypass cannot be both configured：手动旁路和自动旁路不能同时配置 · The ingress_port_ip_status is read only：服务实例入接口vPort的IPv4地址状态为只读字段 · The egress_port_ip_status is read only：服务实例出接口vPort的IPv4地址状态为只读字段 · The ingress_port_ipv6_status is read only：服务实例入接口vPort的IPv6地址状态为只读字段 · The egress_port_ipv6_status is read only：服务实例出接口vPort的IPv6地址状态为只读字段 · Make sure the service node and the resource access template use the same connection mode：服务节点的连接模式和资源接入模板的连接模式必须相同 · A resource is required to be bound with each PBRFirewall or PBRLoadbalance service instance：每个PBR类型（PBRFirewall和PBRLoadbalance）的服务实例均需绑定资源 · The resource access template corresponding to the PBRFirewall or PBRLoadbalance service instance has configuration errors or does not exist：PBR类型（PBRFirewall和PBRLoadbalance）的服务实例对应的资源接入模板配置错误或不存在 · Make sure the ingress and egress vPort IP addresses of the third-party service device do not belong to the address pool of the resource access template specified for the firewall or LB device：第三方服务设备的出入虚拟端口IP地址与防火墙或LB节点使用的IP地址池冲突 · A service path can contain a maximum of 16 service instances：一条服务路径最多包含16个服务实例 · A service path can contain a maximum of three service instances when the service chain path ID format is 24-bit：服务链定制化Path ID格式为24比特，一条服务路径最多包含3个服务实例 · A service path can contain a maximum of seven service instances when the service chain path ID format is 16-bit：服务链定制化Path ID格式为16比特，一条服务路径最多包含7个服务实例 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · The specified NQA policy does not exist：指定的NQA策略不存在 · You cannot bind the service path to an NQA profile when the auto NQA profile mode is used：当NQA策略配置为自动时，服务路径不能绑定该NQA策略 · The standby service path can only be used for the cross-virtual router/cross-tenant EPG policy that uses the static route of the transit type virtual router to divert traffic：备服务路径只能用于使用transit类型虚拟路由器的静态路由引流的跨虚拟路由器/跨租户EPG间策略 · The specified NQA profile has been bound to an external network：指定的NQA策略已经被外部网络绑定 · The specified NQA profile has been bound to a service resource：指定的NQA策略已经被服务资源绑定 · The specified NQA profile has been bound to another service path：指定的NQA策略已经被其他服务路径绑定 · The devices in the resource access template belong to different fabrics：资源接入模板下设备属于不同的Fabric |
|
关键字 |
UPDATE_SERVICE_PATH_OP |
|
日志内容 |
Updated service path $1 |
|
参数解释 |
$1：服务路径配置信息 |
|
举例 |
Updated service path ID: 945b4091-265d-45b7-bc83-f7099025903d Name: graph0001 Ip version: 4 Service nodes: [{ Instance name: 6263 Bypass : NONE },{ Instance name: 8283 Bypass : NONE }] Enable detect: false |
|
日志说明 |
用户进行了修改服务路径的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The firewall service has not been found：防火墙服务未启动 · The load balancer service has not been found：负载均衡器服务未启动 · Configuration recovery is in progress：配置正在恢复中 · The controller is not the active leader：该控制组件不是主Leader · The operation requires the administrator privilege：您需要管理员权限才能执行此操作 · The service chain already exists：指定的服务路径已存在 · The specified tenant doesn't exist：指定的租户不存在 · The service instance doesn't exist：服务实例不存在 · The tenant ID cannot be modified：租户ID不允许修改 · The ID cannot be modified：ID不允许修改 · Invalid IP version：无效的IP版本 · When multiple service nodes exist in the service path, make sure all service nodes use the two-arm connection mode：当服务路径存在多个服务节点时，服务节点的连接模式必须都为双臂 · The service instance is already used by another service chain：服务路径引用的服务实例已经被其他服务路径引用 · Only one loadbalancer service instance is allowed in a service chain：一条服务路径只能包含一个负载均衡器实例 · The name cannot exceed 255 characters：服务路径名称不能超过255个字符 · Failed to obtain fabric information：获取Fabric信息失败 · A resource is required to be bound with each PBRFirewall or PBRLoadbalance service instance：每个PBR类型（PBRFirewall和PBRLoadbalance）的服务实例均需绑定资源 · Duplicated service instances exist in the service chain：该服务路径中存在重复的服务实例 · A service instance of the Third-party type cannot form a service chain with service instances of other types：第三方服务节点不支持与其他类型服务节点组成一条服务路径 · A PBRFirewall or PBRLoadbalance service instance cannot form a service chain with service instances of other types：PBR类型（PBRFirewall和PBRLoadbalance）的服务实例不支持与其它类型的服务实例组成一条服务路径 · You cannot add a shared third-party service node to the service path：当服务节点为共享节点时，不能被应用到服务路径中 · You cannot change the IP version of the service path, because it has been specified in an exception rule：服务路径已被引用,IP版本不允许修改 · Please specify a resource for the service node：服务节点未绑定资源 · Make sure the service node and the resource access template use the same connection mode：服务节点的连接模式和资源接入模板的连接模式必须相同 · Make sure the third-party service path and all service devices in it use the same IP version：第三方服务路径的IP版本必须与第三方服务设备的IP版本一致 · The service path name cannot be modified：服务路径名称不能被修改 · Make sure no EPGs contain any member IP address of the EPG automatically generated upon service path creation：服务路径自动生成的EPG的成员IP已存在 · Make sure a vRouter is bound to each of the subnets attached to the ingress and egress vPorts：第三方服务设备的出入虚拟端口所属子网没有绑定虚拟路由器 · Unknown internal service error：未知的内部服务器错误 · You have no privilege to perform this operation：用户无权限执行此操作 · A subnet of the third-party service device is not bound to a vNetwork：存在第三方服务设备的子网没有绑定虚拟链路层网络 · A subnet of the third-party service device is not bound to a vRouter：存在第三方服务设备的子网没有绑定虚拟路由器 · One or more selected third-party service instances are invalid：已选服务中存在无效的第三方服务实例 · The service path cannot contain both a third-party LB service node and a controller-managed LB service node：第三方负载均衡实例和被控制组件纳管的负载均衡实例不能在同一条服务路径上 · The service path does not support third-party service nodes with IPsec or SNAT settings：服务路径上不支持添加有IPsec和SNAT功能的第三方服务节点 · A service path can contain a maximum of 16 service instances：一条服务路径最多包含16个服务实例 · PBR firewall service instances of a service path must belong to different virtual devices：一条服务路径的每个PBR防火墙服务实例所在的虚拟设备不能相同 · When the source or destination EPG is an external EPG, the service path can contain only two-arm service nodes：当源EPG或目的EPG为External类型时，服务路径的服务节点必须为双臂连接模式 · When the source and destination EPGs and source and destination ports are the same, make sure the service path contains only a one-arm service node：当源EPG、源端口和目的EPG、目的端口相同时，服务路径的服务节点必须为单臂连接模式 · The service path cannot contain PBRLoadbalance service instances. This is because it has been specified for an exception rule in an application policy, and the exception rule uses an external destination EPG：服务路径已被应用策略中的例外规则引用，且该例外规则的目的EPG为External，服务路径中不能包含PBRLoadbalance类型的服务实例 · The service path supports only one third-party service node with IPsec or NAT settings：已配置IPsec或NAT功能的第三方服务节点在服务路径中最多只能有一个 · The service path has a third-party service node with IPsec settings. You can specify the service path only in exception rules that contain an external source or destination EPG：指定服务路径已使用配置了IPsec功能的第三方服务节点，只能应用于源或目的EPG为External类型的例外规则 · The service path has a third-party service node with IPsec or NAT settings and an external EPG. You cannot add LB service nodes between them：服务路径中，已配置IPsec或NAT功能的第三方服务节点与External类型的EPG之间不允许存在LB类型的服务节点 · Make sure all third-party service instances in the service path are bound to the same vRouter：服务路径中的所有第三方服务实例必须属于同一虚拟路由器 · Manual bypass and auto bypass cannot be both configured：手动旁路和自动旁路不能同时配置 · The ingress_port_ip_status is read only：服务实例入接口vPort的IPv4地址状态为只读字段 · The egress_port_ip_status is read only：服务实例出接口vPort的IPv4地址状态为只读字段 · The ingress_port_ipv6_status is read only：服务实例入接口vPort的IPv6地址状态为只读字段 · The egress_port_ipv6_status is read only：服务实例出接口vPort的IPv6地址状态为只读字段 · Make sure the service node and the resource access template use the same connection mode：服务节点的连接模式和资源接入模板的连接模式必须相同 · A resource is required to be bound with each PBRFirewall or PBRLoadbalance service instance：每个PBR类型（PBRFirewall和PBRLoadbalance）的服务实例均需绑定资源 · The resource access template corresponding to the PBRFirewall or PBRLoadbalance service instance has configuration errors or does not exist：PBR类型（PBRFirewall和PBRLoadbalance）的服务实例对应的资源接入模板配置错误或不存在 · A service path can contain a maximum of 16 service instances：一条服务路径最多包含16个服务实例 · A service path can contain a maximum of three service instances when the service chain path ID format is 24-bit：服务链定制化Path ID格式为24比特，一条服务路径最多包含3个服务实例 · A service path can contain a maximum of seven service instances when the service chain path ID format is 16-bit：服务链定制化Path ID格式为16比特，一条服务路径最多包含7个服务实例 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · The service path has been specified in an application policy whose method for traffic routing is static route. The service path can contain only one node, and the node type must be FW, LB, third-party FW, or third-party LB：服务路径被静态路由引流的应用策略引用时，只能包含一个节点，并且节点类型为FW、LB、第三方FW或第三方LB · You cannot enable the bypass feature for the service path, because it has been specified in an application policy that uses static route-based service chain traffic routing：服务路径已被静态路由引流的应用策略引用，不能使用旁路功能 · The specified NQA policy does not exist：指定的NQA策略不存在 · You cannot bind the service path to an NQA profile when the auto NQA profile mode is used：当NQA策略配置为自动时，服务路径不能绑定该NQA策略 · The standby service path can only be used for the cross-virtual router/cross-tenant EPG policy that uses the static route of the transit type virtual router to divert traffic：备服务路径只能用于使用transit类型虚拟路由器的静态路由引流的跨虚拟路由器/跨租户EPG间策略 · The specified NQA profile has been bound to an external network：指定的NQA策略已经被外部网络绑定 · The specified NQA profile has been bound to a service resource：指定的NQA策略已经被服务资源绑定 · The specified NQA profile has been bound to another service path：指定的NQA策略已经被其他服务路径绑定 · The service path is applied to an app policy with two transit vRouters specified and the app policy contains a service path that has a primary/secondary relationship with this service path. You cannot change the primary/secondary role of the service path：无法修改服务路径的主备角色，因为该路径已被transit类型虚拟路由器的应用策略引用，并且该应用策略中存在与指定服务路径互为主备关系的其他服务路径 · The devices in the resource access template belong to different fabrics：资源接入模板下设备属于不同的Fabric |
|
关键字 |
DELETE_SERVICE_PATH_OP |
|
日志内容 |
Deleted service path $1 |
|
参数解释 |
$1：服务路径名称 |
|
举例 |
Deleted service path service path1 |
|
日志说明 |
用户进行了删除服务路径的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service has not been found：服务未启动 · Configuration recovery is in progress：配置恢复未完成 · The controller is not the active leader：该控制组件不是主Leader · The operation requires the administrator privilege：您需要管理员权限才能执行此操作 · The configuration item doesn't exist：配置项不存在 · You have no privilege to perform this operation：用户无权限执行此操作 · The service chain has been used by a redirection rule and cannot be deleted.：服务路径已被重定向规则引用，不允许删除 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
CREATE_DETECT_OP |
|
日志内容 |
Created detection task $1 |
|
参数解释 |
$1：链路探测任务的配置信息 |
|
举例 |
Created detection task Service graph ID: 945b4091-265d-45b7-bc83-f7099025903d Type: MANUAL |
|
日志说明 |
用户进行了创建链路探测任务的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service has not been found：服务未启动 · Configuration recovery is in progress：配置正在恢复中 · The controller is not the active leader：该控制组件不是主Leader · The detection task already exists：已存在该探测任务 · Make sure the detection type is manual or periodic：探测类型必须为手动探测或定时探测 · Make sure the service path ID or service chain ID is specified：必须携带服务路径ID或服务链ID · You can specify only the service path ID or service chain ID for the detection task, not both：探测任务中服务路径或者服务链ID只能选择一个 · Invalid detection interval：探测时间间隔无效 · Please specify a detection interval：探测间隔不能为空 · The specified service path does not exist：指定的服务路径不存在 · The specified service chain does not exist：指定的服务链不存在 · Please specify the detection type：探测类型不能为空 |
|
关键字 |
UPDATE_SC_TENANT_CONFIG_OP |
|
日志内容 |
Updated service chain settings for a tenant $1 |
|
参数解释 |
$1：基于租户的服务链全局配置信息 |
|
举例 |
Updated service chain settings for a tenant Tenant ID: ffffffff-0000-0000-0000-000000000001 Set priority: true |
|
日志说明 |
用户进行了修改基于租户的服务链全局配置的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The configuration item doesn't exist：配置项不存在 · Failed to modify the configuration item：修改配置项失败 · Invalid JSON format：无效的JSON格式 · The tenant ID must be specified：必须指定租户ID · Invalid tenant ID：无效的租户ID · You cannot turn off this option, because some service chains have priority settings：存在使用优先级的服务链，不允许关闭服务链优先级开关 |
|
关键字 |
UPDATE_SC_CUSTOM_CONFIG_OP |
|
日志内容 |
Updated service chain settings $1 |
|
参数解释 |
$1：服务链定制化配置信息 |
|
举例 |
Updated service chain settings Path ID format: Default |
|
日志说明 |
用户进行了修改服务链定制化配置的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The configuration item doesn't exist：配置项不存在 · Failed to modify the configuration item：修改配置项失败 · Invalid JSON format：无效的JSON格式 · You have no privilege to perform this operation：用户无权限执行此操作 · Configuration recovery is in progress：配置正在恢复中 · The controller is not the active leader：该控制组件不是主Leader · A service chain already exists with more than three service instances：已存在服务实例数量大于3的服务链 · A service chain already exists with more than seven service instances：已存在服务实例数量大于7的服务链 · A service path already exists with more than three service instances：已存在服务实例数量大于3的服务路径 · A service path already exists with more than seven service instances：已存在服务实例数量大于7的服务路径 |
本节介绍仿真模块输出的操作日志信息。
|
关键字 |
CREATE_NETWORK_WIDE_IMPACT_ANALYSIS_OP |
|
日志内容 |
Created network-wide impact analysis task: $1. |
|
参数解释 |
$1：全网分析数据参数信息 |
|
举例 |
Created network-wide impact analysis task: { "network_analysis": { "tenant_id": "aca81959-a3a9-4928-a30e-3784a7dfdbf4", "type": "simulation_after" } } |
|
日志说明 |
用户进行了创建全网分析的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request body cannot be empty：请求体不能为空 · The tenantId parameter cannot be empty when type is simulation_after：类型为simulation_after时参数tenantId不能为空 · The tenantId parameter does not match regex：参数tenantId不匹配正则表达式 · The type parameter range must be simulation_before,simulation_after：类型必须匹配simulation_before或simulation_after · The controller is unreachable：控制组件不可达 · The vPort cannot be empty：虚拟端口不能为空 · Internal error：内部错误 · Failed to obtain resources：获取资源失败 · Another user is processing this resource. Please try again later：其他用户正在操作，请稍后再试 · You cannot perform this operation, because all simulated devices are inactive：当前所有仿真设备都处于Inactive状态，无法执行当前操作 · Network-wide impact evaluation is in progress for the current tenant. Please try again later：当前租户正在进行全网影响评估，请稍候再试 |
|
关键字 |
CREATE_CONNECTIVITY_TEST_TASK_OP |
|
日志内容 |
Created connectivity test task: $1. |
|
参数解释 |
$1：连通性检测的信息 |
|
举例 |
Created connectivity test task: { "connectivityDetectId": "5ed58808-3796-4dfa-9a71-bdc404a1d9b3", "connectivity_detect": { "protocol": "6", "ori_device": [ { "src_ip": "81.1.1.2", "type": "vPort", "vni": "81", "origin_device": "172.20.8.114", "inport": "WGE1/0/2", "inDcport": "WGE1/0/2", "src_port": "10000", "subnetId": "3d120566-1a15-4f66-a31d-37919b2cc690" } ], "dst_device": [ { "dst_ip": "80.1.1.2", "type": "vPort", "dst_port": "50000", "dst_device": "172.20.8.110", "dstDcInport": "WGE1/0/2", "dst_inport": "WGE1/0/2", "subnetId": "f034cc3f-a536-4c3f-a698-0335eebfba6c" } ] }, "taskNum": "1" } |
|
日志说明 |
用户进行了创建连通性检测的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The system service does not respond：系统未响应 · Invalid parameter：参数异常 · Failed to obtain resources：获取资源失败 · Failed to enable DC detection：无法启用DC检测 · Failed to obtain resources：获取资源失败 · Another user is processing this resource. Please try again later：其他用户正在操作，请稍后再试 · The source and destination vPorts must be different in a connectivity test：连通性探测时，源和目的不允许是同一个虚拟端口 · Network-wide impact evaluation is in progress for the current tenant. Please try again later：当前租户正在进行全网影响评估，请稍候再试 |
|
关键字 |
STOP_SIMULATION_OP |
|
日志内容 |
Stopped simulation task: $1. |
|
参数解释 |
$1：仿真任务信息 |
|
举例 |
Stopped simulation task: simulation_before |
|
日志说明 |
用户进行了取消仿真任务的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request body cannot be empty：请求体不能为空 · The operation does not exist：指定操作不存在 |
|
关键字 |
ENABLE_TENANT_DESIGN_STATE_OP |
|
日志内容 |
Enabled design mode for tenant: $1 |
|
参数解释 |
$1：租户ID |
|
举例 |
Enabled design mode for tenant: 95a541c8-dcb4-4d18-8a8c-16d79ff524c9 |
|
日志说明 |
用户进行了开启指定租户设计态的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The specified tenant does not exist on the controller：控制组件不存在指定租户 · Internal error：内部错误 · The (parameter) parameter value does not match the regular expression：参数(parameter)不匹配正则表达式 · Cannot enable the design mode for the tenant, because the design mode has been enabled for another tenant：多个租户的设计态不能同时开启 · Failed to enable the design mode for the tenant：开启租户设计态失败 · The controller is synchronizing data to all tenants in design mode. Please try again later：控制组件正在向设计态同步数据，请稍后重试 · The design mode has been enabled for the tenant：指定租户的设计态已开启 · No simulation network is built for the tenant：该租户未构建仿真网络 · Network-wide impact evaluation is in progress for the current tenant. Please try again later：当前租户正在进行全网影响评估，请稍候再试 |
|
关键字 |
ENABLE_TENANT_DESIGN_STATE_OP |
|
日志内容 |
Disabled design mode for tenant: $1 |
|
参数解释 |
$1：租户ID |
|
举例 |
Disabled design mode for tenant: e6ee5063-05f4-40e8-8e27-e909b0ce7ff2 |
|
日志说明 |
用户进行了关闭指定租户设计态的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The (parameter) parameter value does not match the regular expression：参数(parameter)不匹配正则表达式 · Internal error：内部错误 · The tenant doesn't start the design state：指定租户的设计态未开启 · Failed to disable the design mode for the tenant：关闭租户设计态失败 · Another user is processing this resource. Please try again later：其他用户正在操作，请稍后再试 · Failed to delete the simulation vPort：删除虚拟端口失败 · Failed to obtain the tenant list：查询租户列表失败 · You have selected interfaces on an inactive device (management IP)：正在绑定的接口所属设备或已绑定的接口所属设备中存在未激活设备 · The mapping table doesn't exist：该映射表不存在 · Network-wide impact evaluation is in progress for the current tenant. Please try again later：当前租户正在进行全网影响评估，请稍候再试 |
|
关键字 |
RCV_DEPLOY_REQ |
|
日志内容 |
Received request to deploy services to tenant $1. |
|
参数解释 |
$1：租户ID |
|
举例 |
Received request to deploy services to tenant 95a541c8-dcb4-4d18-8a8c-16d79ff524c9. |
|
日志说明 |
用户进行了对指定租户进行配置下发的操作 |
|
失败原因 |
无 |
|
关键字 |
DEPLOY_OP |
|
日志内容 |
Deployed services to tenant: $1. |
|
参数解释 |
$1：配置下发的详细信息 |
|
举例 |
Deployed services to tenant : { "deployed_resources": [{ "resource_type": "subnet", "number": 12 }, { "resource_type": "vRouter", "number": 10 }] } |
|
日志说明 |
控制组件处理用户请求，向指定的租户部署业务 |
|
失败原因 |
当操作失败时，可能的原因如下： · Internal error：内部错误 · The specified tenant does not exist on the controller：控制组件不存在指定租户 · The (parameter) parameter value does not match the regular expression：参数(parameter)不匹配正则表达式 · The design mode has been disabled for the tenant：指定租户的设计态未开启 · Failed to deploy the service：配置下发失败 · No services to deploy：不存在未部署的业务 · Another user is processing this resource. Please try again later：其他用户正在操作，请稍后再试 · The simulated resources have been changed. This operation cannot be done：仿真资源已发生变更，不支持该操作 · Network-wide impact evaluation is in progress for the current tenant. Please try again later：当前租户正在进行全网影响评估，请稍候再试 |
|
关键字 |
SIMULATION_DELETE_VM_OP |
|
日志内容 |
Deleted VM for simulation: $1. |
|
参数解释 |
$1：仿真VM信息 |
|
举例 |
Deleted VM for simulation: e6ee5063-05f4-40e8-8e27-e909b0ce7ff2. |
|
日志说明 |
用户进行了删除仿真VM的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The tenant does not exist：租户不存在 · Internal error：内部错误 · The (parameter) parameter does not match the regular expression：参数(parameter)不匹配正则表达式 · Failed to delete VM from the simulation network：仿真网络删除仿真VM失败 · Failed to delete VM from the simulation DC：仿真DC删除仿真VM失败 · The specified VM does not exist：指定的仿真VM不存在 · Network-wide impact evaluation is in progress for the current tenant. Please try again later：当前租户正在进行全网影响评估，请稍候再试 |
|
关键字 |
SIMULATION_CREATE_VM_OP |
|
日志内容 |
Created VM for simulation: $1. |
|
参数解释 |
$1：仿真VM信息 |
|
举例 |
Created VM for simulation: { "simulation_vms": [{ "name": "sample_port1", "network_id": "f73ca945-bc2d-4b85-97b7-f4ecb8138dff", "enableDhcp": true, "ip_address": "150.1.1.12", "ip_version": 4, "mac_address": "00:50:56:bd:2c:b6", "vlan": "500", "fabric_id": "7465ebf5-7359-43be-b36d-6d84d3b314d2", "access_device_id": "14ed05b2-2a52-4f04-aa4e-6f215e622a39", "abbreviated_access_port_name": "XGE1/0/40", "enableHide": false }] } |
|
日志说明 |
用户进行了创建仿真VM的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · The request body cannot be empty：请求体不能为空 · Please specify the (parameter) parameter：参数(parameter)不能为空 · The (parameter) parameter does not match the regular expression：参数(parameter)不匹配正则表达式 · The (parameter) parameter is invalid：非法的参数(parameter) · The tenant does not exist：租户不存在 · Internal error：内部错误 · The specified access interface does not exist：指定的接入端口不存在 · The specified vNetwork does not exist：指定的虚拟链路层网络不存在 · The VM has been specified：指定的仿真VM和已存在的仿真VM重复 · You must specify an IP address when the access mode of the vPort is static：虚拟端口的接入方式为“静态IP接入”时，IP地址不能为空 · DHCP is disabled for the vSubnet：虚拟子网未开启DHCP功能 · A static IP cannot be in a DHCP address pool：静态IP地址不能在DHCP地址池内 · Failed to obtain VM in the simulation DC：查询仿真DC的仿真VM失败 · Failed to obtain vNetworks in the simulation DC：查询仿真DC的虚拟链路层网络失败 · Failed to obtain vRouters in the simulation DC：查询仿真DC的虚拟路由器失败 · Failed to save VM：保存仿真VM失败 · Failed to create simulation VMs：创建模拟VM失败 · Failed to obtain the progress of creating simulated VMs in the simulation vNetwork：仿真网络查询创建模拟VM进度失败 · The IP address is already used by another port：该IP地址已被其他端口占用 · The aggregation interface is not bound to a physical interface：该聚合口未绑定物理口 · Network-wide impact evaluation is in progress for the current tenant. Please try again later：当前租户正在进行全网影响评估，请稍候再试 |
|
关键字 |
GET_SYNC_BATCH_CONFIG_OP |
|
日志内容 |
Audited configuration. |
|
参数解释 |
无 |
|
举例 |
Audited configuration. |
|
日志说明 |
用户进行了差异发现操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid token：认证失败，Token信息不合法 · Internal error：内部错误 · Invalid parameter：非法参数 · The value for the pageIndex parameter must be in the range of 1 to 2147483647：页数的索引范围取值范围为1～2147483647之间的整数 · The value for the pageSize parameter must be in the range of 1 to 2147483647：每页大小的取值范围为1～2147483647之间的整数 · Failed to obtain the synchronization state：查询同步状态失败 · An incremental synchronization task is in progress. Please try again later：增量同步任务正在执行中，请稍后再试 · Some incremental configuration data is lost. Please rebuild the simulation network：增量配置数据存在丢失，请重新构建仿真网络 · The backfill request failed on the controller：控制组件回填业务请求失败 · The specified tenant does not exist on the controller：控制组件不存在指定租户 · The simulation incremental sync function is unavailable, because no simulation network is built in some fabrics when you build the simulation network：构建仿真网络时存在未构建仿真网络的Fabric，仿真数据一致性功能不可用 |
|
关键字 |
SET_AUTO_APPLY_OP |
|
日志内容 |
Set auto sync: $1. |
|
参数解释 |
$1：自动同步设置参数信息 |
|
举例 |
Set auto sync: { "setting": { "auto_apply": true, "audit_mode": "TIMING", "cron_time": { "days_of_month": "1,6,8,11,13", "months": "*", "days_of_week": "?", "hours": "12", "minutes": "12", "seconds": "0" } } } |
|
日志说明 |
用户进行了自动同步设置操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid token：认证失败，Token信息不合法 · The parameter cannot be empty：路径参数不能为空 · Invalid parameter：非法参数 · Internal error：内部错误 · The cron expression is invalid：非法的cron时间 · Failed to set auto synchronization：设置自动同步失败 |
|
关键字 |
CREATE_SYNC_CONFIGS_TASK_OP |
|
日志内容 |
Created sync task: $1. |
|
参数解释 |
$1：创建同步配置任务参数信息 |
|
举例 |
Created sync task: { "apply_task": { "id": "11111118-0000-0000-0000-000000000001", "mode": "MANUAL", "total": "20" } } |
|
日志说明 |
用户进行了手动同步操作或定时任务执行了自动同步操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid token：认证失败，Token信息不合法 · Internal error：内部错误 · The parameter cannot be empty：路径参数不能为空 · The %s parameter does not match regex：参数不合法 · Invalid parameter：非法参数 · Failed to obtain the design mode state of the tenant：查询租户设计态状态失败 · To perform incremental synchronization, first disable the design mode for the tenant：增量同步时，不允许开启租户设计态 · Failed to obtain the synchronization state：查询同步状态失败 · An incremental synchronization task is in progress. Please try again later：增量同步任务正在执行中，请稍后再试 · Some incremental configuration data is lost. Please rebuild the simulation network：增量配置数据存在丢失，请重新构建仿真网络 · The backfill request failed on the controller：控制组件回填业务请求失败 · No configuration data to be synchronized：不存在未同步的配置数据 · Failed to update the synchronization state：更新同步状态失败 · Failed to create the incremental synchronization task：创建增量同步任务失败 · The simulation incremental sync function is unavailable, because no simulation network is built in some fabrics when you build the simulation network：构建仿真网络时存在未构建仿真网络的Fabric，仿真数据一致性功能不可用 |
|
关键字 |
SIMULATION_RESOURCE_REVOKED_OP |
|
日志内容 |
Revoked resources: $1. |
|
参数解释 |
$1：资源的信息 |
|
举例 |
Revoked resources: { "recovery": {"resource_info": {"name":"1","id":"132dd253-5b42-492b-961c-43363d43cf24", "type":"applicationDescription","operation":"create"}, "state":"success", "error_code":null, "error_message":null } } |
|
日志说明 |
用户进行了资源撤销的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The simulation function does not support this request：仿真功能不支持该请求 · The design mode is not enabled for the tenants to which the resources belong：资源所在租户的设计态未开启 · You cannot delete the vNetwork, because it has been specified in a VLAN-network mapping：指定的虚拟链路层网络已配置VLAN-NETWORK映射，不允许删除 · You cannot delete the subnet, because it has been bound to a vRouter：指定的子网已被虚拟路由器绑定，不允许删除 · You cannot delete the subnet, because it has been bound to a EPG：指定的子网已被EPG绑定，不允许删除 · The subnet cannot be unbound. The vRouter for the subnet has been associated with the EPG that contains the subnet's vNetwork as a member. Deleting the subnet will remove the binding between the vNetwork and the vRouter：解绑子网失败，子网所属的虚拟链路层网络已作为EPG成员，且子网绑定的虚拟路由器下配置了该EPG，若解绑子网将会导致指定虚拟链路层网络和虚拟路由器不匹配 · Failed to obtain the service resources of the tenant：查询服务资源失败 · The (parameter) only support true or false：参数(parameter)仅支持true或者false · You cannot delete the vNetwork, because it has been bound to a EPG：指定的虚拟链路层网络已被EPG绑定，不允许删除 · Internal error：内部错误 · You cannot bulk create resources of this type：不支持批量创建该资源 · The edge device to the external network for the vRouter is a border device. Please specify external subnets for the external EPG：指定虚拟路由器的外网出口设备为边界设备，External类型的EPG的外部网络子网不能为空 · The exception rules of epg bound redirect are not allowed to be modified：指定的EPG已绑定redirect的例外规则不允许修改 · Failed to delete the vRouter because a gateway has been bound to the vRouter：虚拟路由器已绑定网关，不允许删除 · You cannot delete the vPort, because it has been bound to a EPG：指定的虚拟端口已被EPG绑定，不允许删除 · No revocable resources exist：环境中不存在待撤销的资源 · The design mode has been disabled for the tenant：指定租户的设计态未开启 · Resource orchestration is in progress：当前状态为资源编排 · Resource revocation is in progress：前状态为资源撤销 · Network-wide impact evaluation is in progress for the current tenant. Please try again later：当前租户正在进行全网影响评估，请稍候再试 · Capacity evaluation is in progress for the current tenant. Please try again later：当前租户正在进行容量评估，请稍候再试 · Connectivity detection is in progress for the current tenant. Please try again later：当前租户正在进行连通性检测，请稍候再试 · Configuration deployment is in progress for the current tenant. Please try again later：当前租户正在进行配置发放，请稍候再试 · Service rollback is in progress for the current tenant. Please try again later：当前租户正在进行业务回滚，请稍候再试 · Connectivity detection is in progress for the current tenant. Please try again later：当前租户正在进行连通性检测，请稍候再试 · The system is not ready. Please try again later：系统正在准备中，请稍后再试 · The router already has service resource：指定的虚拟路由器已绑定服务资源 · For successful simulation & evaluation and data synchronization, accurate evaluation results, and simulation data consistency, do not operate the production environment when using the simulation function：使用仿真功能时，请不要对生产环境进行操作，否则可能导致仿真评估失败、评估结果不准确、仿真数据差异发现失败、数据同步失败等 |
|
关键字 |
SIMULATION_RESOURCE_CHANGE_OP |
|
日志内容 |
Orchestrated simulation resource: $1. |
|
参数解释 |
$1：资源的信息 |
|
举例 |
Orchestrated simulation resource: { "vpc-connection": { "name": "o", "description": null, "tenant_id": "155b287f-ac4a-4807-90c1-b6a6e1cdd41e", "local_router": "e434c2b2-5431-49e0-998f-7348088d2bd7", "peer_router": "0e27ade1-36ef-4dfa-8a7b-7ac30a884882", "local_subnets": [ "abecfc35-6bf3-4c00-9cb7-1dedea5a7a63", "72365061-545b-4e5e-a78f-ffc349ecd66e" ], "peer_subnets": [ "f1d6b3ba-957a-4ead-822d-216c42f770f2", "b7473307-6d4e-4d79-abe0-b61e34d35741", "85b07c4e-f718-4743-b862-2c3b9796aa13", "95484f87-6b18-4c53-965c-396c7fb0a90a" ], "local_cidrs": [], "peer_cidrs": [], "local_firewall_enable": false, "peer_firewall_enable": true, "reduce_routes": null, "mode": "NORMAL" } } |
|
日志说明 |
用户进行了统一编排仿真资源的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The simulation function does not support this request：仿真功能不支持该请求 · The design mode is not enabled for the tenants to which the resources belong：资源所在租户的设计态未开启 · You cannot delete the vNetwork, because it has been specified in a VLAN-network mapping：指定的虚拟链路层网络已配置VLAN-NETWORK映射，不允许删除 · You cannot delete the subnet, because it has been bound to a vRouter：指定的子网已被虚拟路由器绑定，不允许删除 · You cannot delete the subnet, because it has been bound to a EPG：指定的子网已被EPG绑定，不允许删除 · The subnet cannot be unbound. The vRouter for the subnet has been associated with the EPG that contains the subnet's vNetwork as a member. Deleting the subnet will remove the binding between the vNetwork and the vRouter：解绑子网失败，子网所属的虚拟链路层网络已作为EPG成员，且子网绑定的虚拟路由器下配置了该EPG，若解绑子网将会导致指定虚拟链路层网络和虚拟路由器不匹配 · Failed to obtain the service resources of the tenant：查询服务资源失败 · The (parameter) only support true or false：参数(parameter)仅支持true或者false · You cannot delete the vNetwork, because it has been bound to a EPG：指定的虚拟链路层网络已被EPG绑定，不允许删除 · Internal error：内部错误 · You cannot bulk create resources of this type：不支持批量创建该资源 · The edge device to the external network for the vRouter is a border device. Please specify external subnets for the external EPG：指定虚拟路由器的外网出口设备为边界设备，External类型的EPG的外部网络子网不能为空 · The exception rules of epg bound redirect are not allowed to be modified：指定的EPG已绑定redirect的例外规则不允许修改 · Failed to delete the vRouter because a gateway has been bound to the vRouter：虚拟路由器已绑定网关，不允许删除 · You cannot delete the vPort, because it has been bound to a EPG：指定的虚拟端口已被EPG绑定，不允许删除 · No revocable resources exist：环境中不存在待撤销的资源 · The design mode has been disabled for the tenant：指定租户的设计态未开启 · Resource orchestration is in progress：当前状态为资源编排 · Resource revocation is in progress：当前状态为资源撤销 · Network-wide impact evaluation is in progress for the current tenant. Please try again later：当前租户正在进行全网影响评估，请稍候再试 · Capacity evaluation is in progress for the current tenant. Please try again later：当前租户正在进行容量评估，请稍候再试 · Connectivity detection is in progress for the current tenant. Please try again later：当前租户正在进行连通性检测，请稍候再试 · Configuration deployment is in progress for the current tenant. Please try again later：当前租户正在进行配置发放，请稍候再试 · Service rollback is in progress for the current tenant. Please try again later：当前租户正在进行业务回滚，请稍候再试 · Connectivity detection is in progress for the current tenant. Please try again later：当前租户正在进行连通性检测，请稍候再试 · The system is not ready. Please try again later：系统正在准备中，请稍后再试 · The router already has service resource：指定的虚拟路由器已绑定服务资源 · For successful simulation & evaluation and data synchronization, accurate evaluation results, and simulation data consistency, do not operate the production environment when using the simulation function：使用仿真功能时，请不要对生产环境进行操作，否则可能导致仿真评估失败、评估结果不准确、仿真数据差异发现失败、数据同步失败等 |
|
关键字 |
EXECUTE_CAPACITY_SIMULATION_TASK_OP |
|
日志内容 |
Executed simulation evaluation task: $1. |
|
参数解释 |
$1：租户信息 |
|
举例 |
Executed simulation evaluation task: ffffffff-0000-0000-0000-000000000001 |
|
日志说明 |
用户进行了仿真评估的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · The request body cannot be empty：请求体不能为空 · The (parameter) parameter cannot be empty：参数(parameter)不能为空 · The (parameter) parameter value does not match the regular expression：参数(parameter)不匹配正则表达式 · The value for the type parameter can only be AC, VSI, VSI-Interface, VRF, Route：参数type取值范围必须为AC、VSI、VSI-Interface、VRF、Route · An I/O exception occurred while reading the request data：读取请求数据时发生读写异常 · The capacity simulation task does not exist：指定的容量仿真任务不存在 · Cannot find the specified device：找不到指定的设备 · Internal error：内部错误 · The NETCONF configuration file does not exist：指定的NETCONF配置文件不存在 · The NETCONF configuration file is empty or has no valid resources：指定的NETCONF配置文件为空或没有合法资源 · The NETCONF configuration file content does not match the regular expression：指定的NETCONF配置文件内容不符合正则表达式 · Failed to obtain command configuration from the device：查询设备命令行配置失败 · Failed to connect to the database：建立数据库连接失败 · The specified {resourceType} with {indexType} values {indexValue} does not exist：（indexType）等于（indexValue）对应的（resourceType）值在数据库中不存在 · The specified device is offline on the production network：指定的设备在生产网络中已下线 · Failed to query tenant designs：查询租户设计表失败 · Another user is processing this resource. Please try again later：其他用户正在操作，请稍后再试 · The executor rejected the task：线程池拒绝执行线程任务 · Exception in getting redis lock：获取redis锁异常 · The NETCONF configuration file does not exist on the device：NETCONF配置文件在当前设备上不存在 · The CLI configuration file does not exist on the device：命令行配置文件在当前设备上不存在 · No service changes detected：本次仿真未检测到业务变更 · You cannot perform this operation, because all simulated devices are inactive：当前所有仿真设备都处于Inactive状态，无法执行当前操作 · Resource orchestration is in progress：当前状态为资源编排 · Resource revocation is in progress：当前状态为资源撤销 · Network-wide impact evaluation is in progress for the current tenant. Please try again later：当前租户正在进行全网影响评估，请稍候再试 · Capacity evaluation is in progress for the current tenant. Please try again later：当前租户正在进行容量评估，请稍候再试 · Connectivity detection is in progress for the current tenant. Please try again later：当前租户正在进行连通性检测，请稍候再试 · Configuration deployment is in progress for the current tenant. Please try again later：当前租户正在进行配置发放，请稍候再试 · Service rollback is in progress for the current tenant. Please try again later：当前租户正在进行业务回滚，请稍候再试 · Connectivity test is in progress for the current tenant. Please try again later：当前租户正在进行连通性检测，请稍候再试 · The system is not ready. Please try again later：系统正在准备中，请稍后再试 · Device capacity analysis failed：设备容量分析失败 · The simulation network is abnormal：仿真网络异常 · The specified resource doesn't exist：指定资源不存在 |
本节介绍仿真Manager模块输出的操作日志信息
|
关键字 |
ADD_IMAGE_OP |
|
日志内容 |
Added image: $1 |
|
参数解释 |
$1：镜像名称 |
|
举例 |
Added image: v6850-56hf-CMW710-r6555p01-X64.qco |
|
日志说明 |
用户进行了上传镜像的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid image file：无效的镜像文件 · An image already exists with the specified name：指定名称的镜像文件已存在 · An image of the specified type already exists：指定类型的镜像文件已存在 · Invalid image file type：无效的镜像文件类型 · Invalid image name：无效的镜像名称 · The HTTP method is not supported：HTTP方法不支持 · The system service does not respond：系统服务未响应 |
|
关键字 |
DELETE_IMAGE_OP |
|
日志内容 |
Deleted image: “$1”. |
|
参数解释 |
$1：镜像的UUID |
|
举例 |
Deleted image: 957d8a48-55c6-4f79-9c6d-db5566afd583. |
|
日志说明 |
用户进行了删除镜像的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The HTTP method is not supported：HTTP方法不支持 · The system service does not respond：系统服务未响应 · Failed to delete the image because it is being used：镜像正在被使用不允许删除 |
本节介绍仿真网络模块输出的操作日志信息。
|
关键字 |
CREATE_SIMNETWORK_OP |
|
日志内容 |
Created simulation network: $1. |
|
参数解释 |
$1：网络模型所属Fabric的信息 |
|
举例 |
Created simulation network: { "network_instance_id": "b82c8540-4275-4b23-bf9c-e3fede6b1899", "fabrics": [ { "fabric_id": "b82c8540-4275-4b23-bf9c-e3fede6b18a8" } ] }. |
|
日志说明 |
用户进行了创建仿真网络模型的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · Invalid network_instance_id：network_instance_id格式非法 · Invalid fabric_id：fabric_id格式非法 · The system service does not respond：系统服务未响应 · The specified fabric does not exist：指定的fabric不存在 · Internal error：內部错误 · Invalid token：无效的Token · The HTTP method is not supported：HTTP方法不支持 · No available host：没有可用的主机 · The simulation network model already exists：已创建仿真网络模型 · Invalid device list：无效的设备列表 · No simulation network model needs to be created：没有需要创建的仿真网络模型 · Failed to create some VMs：部分虚机创建失败 · Data synchronization failed：数据同步失败 · Failed to update the VLAN-VXLAN mappings：更新VLAN-VXLAN映射失败 · Failed to initialize the simulation service：初始化仿真服务失败 · The DTN component failed to incorporate the simulation twin data：DTN组件纳管仿真孪生体数据失败 · Cannot bulid a simulated network when the network cloud feature is enable. Please first disable the network cloud feature：构建仿真网络不支持网络云场景，请先关闭网络云场景开关 · Failed to build a simulation network for the following devices because of invalid device roles: {name}：无效的设备角色，如下设备无法构建仿真网络：{name} · Failed to obtain the service bridge：获取Fabric连接网桥失败 · Insufficient free interfaces on the device：当前设备无足够的可用空闲口 · The specified fabric has a fabric interconnect on the real network, but it does not have one on the simulation network. Please delete the fabric interconnect on the real network, or delete the simulation network for the opposite fabric：指定Fabric在真实组网中存在Fabric连接但在仿真网络中无Fabric连接，请删除真实组网中的连接关系或删除对端Fabric的仿真网络 · Failed to obtain design mode information for the tenant：获取租户设计态信息失败 · The simulation network model is being operated. Please try again later：正在对仿真网络模型进行操作，请稍后再试 · The service network type of the specified fabric must be VXLAN：指定Fabric的业务网络类型必须为VXLAN · To simulate services for the tenant, please disable design mode first：请关闭租户设计态后再进行网络仿真 · Insufficient available interconnect port numbers in the UDP port range：UDP Port范围的可分配互联端口号不足 · Insufficient available IPv4 addresses for interconnect interfaces：互联口IPv4地址的可分配IP不足 · Insufficient available IPv6 addresses for interconnect interfaces：互联口IPv6地址的可分配IP不足 · Failed to obtain the destination device configuration for the fabric connection：获取Fabric连接中目的设备的配置失败 · Cannot create each device successfully, because resources are insufficient on the available hosts：可用的主机资源不足，无法支持所有设备的构建 · You cannot perform this operation, because the simulation network function is used for another service：仿真网络功能已被占用，不允许该操作 · The value for the operType parameter must be overlay or underlay, case-sensitive：operType参数取值仅支持为overlay和underlay，区分大小写 · Failed to obtain the following devices configuration. Please verify that the controller management network is operating correctly：获取如下设备配置失败，请检查控制组件管理网络是否正常 · You cannot build the simulation network based on both online data and offline data: 不允许同时构建在线数据和离线数据 · Failed to create the veth pair：创建veth-pair失败 · Failed to enable the promiscuous mode：开启混杂模式失败 · The management IP address of the device and the DTN controller IP address must be the same IP version：设备的管理IP和DTN控制组件IP的IP版本必须一致 |
|
关键字 |
DELETE_SIMNETWORK_OP |
|
日志内容 |
Deleted simulation network: $1. |
|
参数解释 |
$1：网络模型所属Fabric的信息 |
|
举例 |
Deleted simulation network: { "network_instance_id": "b82c8540-4275-4b23-bf9c-e3fede6b1899", "fabrics": [ { "fabric_id": "b82c8540-4275-4b23-bf9c-e3fede6b18a8" } ] }. |
|
日志说明 |
用户进行了删除仿真网络模型的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · Please specify all required parameters：请指定所有必选参数 · Invalid fabric ID：Fabric ID无效 · The specified network model does not exist：指定的网络模型不存在 · Failed to delete the VNF：删除虚机失败 · Failed to add the operation record：添加操作记录失败 · Failed to delete the VNF template：删除VNF模板失败 · Failed to delete the network model：删除网络模型失败 · Failed to delete simulation configuration：删除仿真配置失败 · The simulation network model is being operated. Please try again later：正在对仿真网络模型进行操作，请稍后再试 · Internal error：內部错误 · Invalid token：无效的Token · The HTTP method is not supported：HTTP方法不支持 · The system service does not respond：系统服务未响应 · Password decryption failed：解密失败 · Password encryption failed：加密失败 · Failed to obtain design mode information for the tenant：获取租户设计态信息失败 · You cannot perform this operation, because the simulation network function is used for another service：仿真网络功能已被占用，不允许该操作 · The value for the operType parameter must be overlay or underlay, case-sensitive：operType参数取值仅支持为overlay和underlay，区分大小写 |
|
关键字 |
ADD_HOST_OP |
|
日志内容 |
Added host: $1 |
|
参数解释 |
$1：主机的信息 |
|
举例 |
Added host: { "host": { "name": "host1", "ip_address": "192.168.12.42", "user": "root", "password": "******" } } |
|
日志说明 |
用户进行了创建主机的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · Please specify all required parameters：请输入所有指定的参数 · Invalid username：无效的用户名称 · Invalid host name：无效的主机名称 · Invalid host IP：无效的主机IP地址 · Invalid host password：无效的主机密码 · The system service does not respond：系统服务未响应 · Failed to add the host：添加主机失败 · The specify name of host already exists：指定名称的主机已经存在 · The specify IP of host already exists：指定IP的主机已经存在 · Internal error：內部错误 · Invalid token：无效的Token · The HTTP method is not supported：HTTP方法不支持 · Password decryption failed：解密失败 · Password encryption failed：加密失败 · Host authentication failed. Verify that the authentication information is correct：主机认证失败，请检查主机认证信息是否准确 · To perform this operation with this user account, please first assign root priviledges to this user account：非root用户无权限执行此操作，请进行赋权操作 · Failed to obtain the service bridge of the simulation host：获取主机业务网桥失败 · Failed to obtain the uplink interfaces of hosts：获取主机上行口失败 · Invalid host uplink IPs：无效的主机上行IP地址 |
|
关键字 |
UPDATE_HOST_OP |
|
日志内容 |
Updated host: $1 |
|
参数解释 |
$1：主机的信息 |
|
举例 |
Updated host: { "host": { "name": "host2", "ip_address": "192.168.12.42", "user": "root", "password": "******" } } |
|
日志说明 |
用户进行了修改主机信息的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · Please specify all required parameters：请指定所有必选参数 · The simulation network model is being operated. Please try again later：正在对仿真网络模型进行操作，请稍后再试 · The specified host does not exist：指定的主机不存在 · Invalid username：无效的用户名称 · Invalid host password：无效的主机密码 · Internal error：內部错误 · Password decryption failed：解密失败 · Password encryption failed：加密失败 · Some necessary param can not be changed：主机关键参数不允许修改 · Host authentication failed. Verify that the authentication information is correct：主机认证失败，请检查主机认证信息是否准确 · To perform this operation with this user account, please first assign root priviledges to this user account：非root用户无权限执行此操作，请进行赋权操作 |
|
关键字 |
DELETE_HOST_OP |
|
日志内容 |
Deleted host: $1. |
|
参数解释 |
$1：主机的UUID |
|
举例 |
Deleted host: 690d3260-5dc0-4266-a51b-d752559523ff. |
|
日志说明 |
用户进行了删除主机的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The system service does not respond：系统服务未响应 · You cannot delete the host, because a simulation network has been created on the host：指定的主机正在被仿真网络使用，不允许删除 · Failed to delete the host：删除主机失败 · The simulation network model is being operated. Please try again later：正在对仿真网络模型进行操作，请稍后再试 · Internal error：內部错误 · Invalid token：无效的Token · The HTTP method is not supported：HTTP方法不支持 · Invalid JSON format：无效的JSON格式 |
|
关键字 |
UPDATE_PARAM_SETTING_OP |
|
日志内容 |
Updated param setting: $1 |
|
参数解释 |
$1：参数设置的信息 |
|
举例 |
Updated param setting:ParamSettingModel { "udp_port_start": 10000, "udp_port_end": 15000, "ipv4_cidr": "1.0.0.0/24", "ipv6_cidr": "1::/120", "ipv4_mge_cidr": "2.0.0.0/22", "ipv6_mge_cidr ": "2::/118", "ipv4_mge_gateway": "2.0.0.1", "ipv6_mge_gateway": "2::1", "license_server_ip": "192.3.3.0", "license_server_port": "3040", "license_server_username": "admin", "flavor_id": "ffffffff-0000-0000-0000-000000000001", "mlag_build_mode": "1" } |
|
日志说明 |
用户进行了修改参数设置的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The HTTP method is not supported：HTTP方法不支持 · The system service does not respond：系统服务未响应 · The simulation network model is being operated. Please try again later：正在对仿真网络模型进行操作，请稍后再试 · Invalid UDP port numbers：UDP端口号无效 · The start UDP port number must be smaller than the end UDP port number：UDP端口起始值必须小于结束值 · The new UDP port range must contain UDP ports in use：新UDP端口号范围必须包含已使用的端口号 · Specify all of the license server IP, port number, username, and password parameters, or specify none of them：License Server的IP地址、端口号、用户名和密码必须同时全部为空或者全部不为空 · Invalid license server IP address. Format: IPv4 or IPv6 address. An IPv4 address must be in dotted decimal notation, and cannot be a broadcast, loopback, multicast, or reserved IP address. An IPv6 address must be in colon hexadecimal notation, and must be a global unicast address：无效的License Server IP地址。格式为IPv4地址/IPv6地址，IPv4地址为点分十进制格式，不支持广播地址、环回地址、组播地址和保留地址；IPv6地址为冒分十六进制格式，仅支持全球单播地址 · Invalid license server port number：无效的License Server端口号 · Invalid license server username：无效的License Server用户名 · Invalid license server password：无效的License Server密码 · The specified flavor does not exist：指定的Flavor不存在 · You cannot change the simulation network M-LAG building mode after the simulation network is built：仿真网络构建完成后不允许修改M-LAG系统构建模式 · The address pool is in use and is not configurable：地址池已被使用不允许修改 · Invalid CIDR：无效的CIDR · Insufficient available IP addresses in the IPv4 management network address pool：管理IPv4地址的可分配IP不足 · Insufficient available IP addresses in the IPv6 management network address pool：管理IPv6地址的可分配IP不足 · The number of Layer 2 aggregate interfaces (BAGG interfaces) used by the security device has exceeded 64. Please reclaim some useless aggregate interfaces：安全设备已使用的BAGG端口序号已超过64，请考虑回收部分无用聚合口 · You cannot edit the management network address pools and their gateways after the simulation network is built：仿真网络构建完成后不允许修改管理地址池以及其网关 · Invalid management CIDRs：无效的管理CIDR · Invalid mask length：无效的掩码 · Invalid IPv4 mask for the management network address pool：无效的管理地址池IPv4掩码 · Invalid prefix length：无效的前缀长度 · Invalid IPv6 prefix length for the management network address pool：无效的管理地址池IPv6前缀长度 · Invalid IPv4 management network gateway：无效的管理IPv4网关 · Invalid IPv6 management network gateway：无效的管理IPv6网关 · The IPv4 management network gateway must be within the IPv4 management network address pool：管理IPv4网关与其地址池须一致 · The IPv6 management network gateway must be within the IPv6 management network address pool：管理IPv6网关与其地址池须一致 · You cannot change the Flavor after the simulation network is built：仿真网络构建完成后不允许修改Flavor |
|
关键字 |
UPLOAD_DEVICE_CONFIG_OP |
|
日志内容 |
Uploaded configuration information file: $1. |
|
参数解释 |
$1：配置信息文件的名称 |
|
举例 |
Uploaded configuration information file: device_config. |
|
日志说明 |
用户进行了上传配置信息文件的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The HTTP method is not supported：HTTP方法不支持 · The system service does not respond：系统服务未响应 · The simulation network model is being operated. Please try again later：正在对仿真网络模型进行操作，请稍后再试 · The file to be uploaded must be a .zip file：上传的文件必须为zip格式 · Failed to parse the file. Verify that contents in all files in the .zip file are valid：文件解析失败，请检查zip包中的文件内容是否有效 · Please specify a file name：文件名不能为空 · No devices exist on the production network. Please first back up and restore device information：生产态中不存在设备，请备份恢复设备信息后在进行该操作 · Before uploading a configuration information file, fist clear the existing configuration information：上传配置信息文件前，请先清空已经存在的配置信息 · The imported device configuration information file is empty：导入的设备配置信息为空 · All files in the .zip file must be .cfg files：zip文件中的全部文件必须为.cfg格式 · A .cfg file must be named in the format of ip_x_x.cfg. ip is an IPv4 or IPv6 address, and the colons in an IPv6 address must be replaced with underscores (_) in a file name. x is an arbitrary length and any character that is not an underscore. For example, the file name for the 1.1.1.1 address is 1.1.1.1_a_b.cfg; the file name for the 2::2:2 address is 2__2_2_a_b.cfg：cfg文件名称必须为ip_x_x.cfg格式。其中，ip为IPv4或IPv6地址，且IPv6地址中冒号（:）需替换为下划线（_）；x为非下划线的任意长度的任意字符。例如，1.1.1.1地址的文件名为1.1.1.1_a_b.cfg；2::2:2地址的文件名为2__2_2_a_b.cfg。 · The IP address in the cfg file name is invalid：cfg文件名称中的IP地址无效 · Some .cfg file names contain the same IP address：某些 .cfg 文件名称包含相同的IP地址 · Some configuration files do not match the devices in production state: xxx.cfg, xxx.cfg: 存在与生产态设备不匹配的配置文件：xxx.cfg, xxx.cfg |
|
关键字 |
UPLOAD_DEVICE_LINK_OP |
|
日志内容 |
Uploaded link information file: $1. |
|
参数解释 |
$1：链路信息文件的名称 |
|
举例 |
Uploaded link information file: device_link. |
|
日志说明 |
用户进行了上传链路信息文件的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The HTTP method is not supported：HTTP方法不支持 · The system service does not respond：系统服务未响应 · The simulation network model is being operated. Please try again later：正在对仿真网络模型进行操作，请稍后再试 · The file to be uploaded must be a .txt file：上传的文件必须为txt文件 · Failed to parse the file. Verify that contents in the .txt file are valid：文件解析失败，请检查txt文件中的内容是否有效 · Please specify a file name：文件名不能为空 · The specified link information does not match the device information in production state. Please upload a link information file again：指定的链路信息与生产态设备信息不匹配，请重新上传 · Before uploading a link file, first clear the existing link information：上传链路信息文件前，请先清空已经存在的链路信息 · Duplicated port numbers exist in the link file. Please upload again：链路信息文件中含有重复的端口号，请重新上传 · The port name in the link file must be abbreviated, please upload again：链路信息文件中的端口名必须为缩写，请重新上传 · The port number cannot be empty. Please upload again：端口名称不能为空，请重新上传 · The .txt file cannot exceed 50 MB：txt文件最大不允许超过50MB · The link status can be active, inactive, fault, or unknown(case-insensitive): 链路状态仅支持active，inactive，fault，unknown，不区分大小写 |
|
关键字 |
CLEAR_DEVICE_CONFIG_OP |
|
日志内容 |
Cleared configuration information. |
|
参数解释 |
无 |
|
举例 |
Cleared configuration information. |
|
日志说明 |
用户进行了清空配置信息的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The HTTP method is not supported：HTTP方法不支持 · The system service does not respond：系统服务未响应 · The simulation network model is being operated. Please try again later：正在对仿真网络模型进行操作，请稍后再试 |
|
关键字 |
CLEAR_LINK_CONFIG_OP |
|
日志内容 |
Cleared link information. |
|
参数解释 |
无 |
|
举例 |
Cleared link information. |
|
日志说明 |
用户进行了清空链路信息的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The HTTP method is not supported：HTTP方法不支持 · The system service does not respond：系统服务未响应 · The simulation network model is being operated. Please try again later：正在对仿真网络模型进行操作，请稍后再试 |
本节介绍SSL VPN服务模块输出的操作日志信息。
|
关键字 |
CREATE_PKI_DOMAIN_OP |
|
日志内容 |
Created PKI domain $1 |
|
参数解释 |
$1：PKI域的配置信息 |
|
举例 |
Created PKI domain ID: 9a83d713-8e79-4ca8-a2e9-8df29daf5fd6 Name: pkiDomain1 Tenant ID: ffffffff-0000-0000-0000-000000000001 Tenant name: default Description: pki domain Public key name: dmpubkey Local certification file name: local.crt CA certification file name: ca.crt |
|
日志说明 |
用户进行了创建PKI域的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The configuration item ID already exists：配置项ID已存在 · The configuration item name already exists：配置项名称已存在 · The tenant doesn't exist：指定的租户不存在 · The controller is not the active leader：该控制组件不是主Leader · The operation requires the administrator privilege：您需要管理员权限才能执行此操作 · Configuration recovery is in progress：配置正在恢复过程中 · The service has not been found：服务未启动 · Unknown error：未知错误 · Invalid PKI domain name：无效的PKI域名称 · Invalid description：无效的描述 · The PKI domain name is required：PKI域名称不能为空 · The public key name is required：公钥名称不能为空 · Invalid public key name：无效的公钥名称 · The CA certification file name is required：CA证书文件名称不能为空 · The local certification file name is required：本地证书文件名称不能为空 · Invalid CA certification file name：无效的CA证书文件名称 · Invalid local certification file name：无效的本地证书文件名称 · The tenant ID is required：租户ID不能为空 · Invalid tenant ID：无效的租户ID · Invalid JSON format：无效的JSON串格式 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_PKI_DOMAIN_OP |
|
日志内容 |
Updated PKI domain $1. |
|
参数解释 |
$1：PKI域的配置信息 |
|
举例 |
Updated PKI domain ID: 9a83d713-8e79-4ca8-a2e9-8df29daf5fd6 Name: pkiDomain1 Tenant ID: ffffffff-0000-0000-0000-000000000001 Tenant name: default Description: pki domain Public key name: dmpubkey Local certification file name: local.crt CA certification file name: ca.crt |
|
日志说明 |
用户进行了修改PKI域的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The PKI domain doesn't exist：该PKI域不存在 · The controller is not the active leader：该控制组件不是主Leader · The operation requires the administrator privilege：您需要管理员权限才能执行此操作 · Configuration recovery is in progress：配置正在恢复过程中 · The service has not been found：服务未启动 · Unknown error：未知错误 · The PKI domain ID is read only：PKI域ID为只读字段 · Invalid PKI domain name：无效的PKI域名称 · Invalid description：无效的描述 · The PKI domain name is read only：PKI域名称为只读字段 · Invalid PKI domain ID：无效的PKI域ID · Invalid public key name：无效的公钥名称 · Invalid CA certification file name：无效的CA证书文件名称 · Invalid local certification file name：无效的本地证书文件名称 · The tenant ID is read only：租户ID为只读字段 · Invalid JSON format：无效的JSON串格式 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_PKI_DOMAIN_OP |
|
日志内容 |
Deleted PKI domain $1 |
|
参数解释 |
$1：PKI域的名称 |
|
举例 |
Deleted PKI domain pki |
|
日志说明 |
用户进行了删除PKI域的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The PKI domain doesn't exist：该PKI域不存在 · The PKI domain is being used by an SSL policy：该PKI域正在被SSL策略引用 · The controller is not the active leader：该控制组件不是主Leader · The operation requires the administrator privilege：您需要管理员权限才能执行此操作 · Configuration recovery is in progress：配置正在恢复过程中 · The service has not been found：服务未启动 · Unknown error：未知错误 · Invalid PKI domain ID：无效的PKI域ID · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_SSL_POLICY_OP |
|
日志内容 |
Created SSL policy $1 |
|
参数解释 |
$1：SSL策略的配置信息 |
|
举例 |
Created SSL policy ID: b52fff79-7bcf-4bff-9340-68c5f6c1c495 Name: sslpolicy Tenant ID: ffffffff-0000-0000-0000-000000000001 Tenant name: default PKI domain ID: e0cdcbe7-3623-4270-becb-8390d88d8009 PKI domain name: pkidomain Description: sslpolicy |
|
日志说明 |
用户进行了创建SSL策略的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The configuration item ID already exists：配置项ID已存在 · The PKI domain doesn't exist：指定的PKI域不存在 · The SSL policy and PKI domain belong to different tenants：该SSL策略所属租户与指定的PKI域所属租户不一致 · The configuration item name already exists：配置项名称已存在 · The tenant doesn't exist：指定的租户不存在 · The controller is not the active leader：该控制组件不是主Leader · The operation requires the administrator privilege：您需要管理员权限才能执行此操作 · Configuration recovery is in progress：配置正在恢复过程中 · The service has not been found：服务未启动 · Unknown error：未知错误 · The PKI domain ID is required：PKI域ID不能为空 · Invalid description：无效的描述 · The SSL policy name is required：SSL策略名称不能为空 · Invalid SSL policy name：无效的SSL策略名称 · The tenant ID is required：租户ID不能为空 · Invalid tenant ID：无效的租户ID · Invalid JSON format：无效的JSON串格式 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_SSL_POLICY_OP |
|
日志内容 |
Updated SSL policy $1 |
|
参数解释 |
$1：SSL策略的配置信息 |
|
举例 |
Updated SSL policy ID: b52fff79-7bcf-4bff-9340-68c5f6c1c495 Name: sslpolicy Tenant ID: ffffffff-0000-0000-0000-000000000001 Tenant name: default PKI domain ID: e0cdcbe7-3623-4270-becb-8390d88d8009 PKI domain name: pkidomain Description: sslpolicy |
|
日志说明 |
用户进行了修改SSL策略的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The configuration item doesn’t exist：配置项不存在 · The PKI domain doesn't exist：指定的PKI域不存在 · The SSL policy and PKI domain belong to different tenants：该SSL策略所属租户与指定的PKI域所属租户不一致 · The controller is not the active leader：该控制组件不是主Leader · The operation requires the administrator privilege：您需要管理员权限才能执行此操作 · Configuration recovery is in progress：配置正在恢复过程中 · The service has not been found：服务未启动 · The SSL policy doesn't exist：指定的SSL策略不存在 · Unknown error：未知错误 · Invalid description：无效的描述 · Invalid SSL policy ID：无效的SSL策略ID · The SSL policy ID is read only：SSL策略ID为只读字段 · The SSL policy name is read only：SSL策略名称为只读字段 · Invalid SSL policy name：无效的SSL策略名称 · The tenant ID is read only：租户ID为只读字段 · Invalid JSON format：无效的JSON串格式 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_SSL_POLICY_OP |
|
日志内容 |
Deleted SSL policy $1 |
|
参数解释 |
$1：SSL策略的名称 |
|
举例 |
Deleted SSL policy sslpolicy |
|
日志说明 |
用户进行了删除SSL策略的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The SSL policy doesn't exist：该SSL策略不存在 · The SSL policy is being used by gateways：该SSL策略正在被网关引用 · The controller is not the active leader：该控制组件不是主Leader · The operation requires the administrator privilege：您需要管理员权限才能执行此操作 · Configuration recovery is in progress：配置正在恢复过程中 · The service has not been found：服务未启动 · Unknown error：未知错误 · Invalid SSL policy ID：无效的SSL策略ID · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_SSLVPN_GATEWAY_OP |
|
日志内容 |
Created SSL VPN gateway $1 |
|
参数解释 |
$1：SSL VPN网关的配置信息 |
|
举例 |
Created SSL VPN gateway ID: 70dc3186-ac5b-4ba1-ac7f-7a27ef566efb Name: sslvpngateway Tenant ID: ffffffff-0000-0000-0000-000000000001 Tenant name: default IP: 192.168.0.1 Port: 443 Description: sslvpngateway vRouter ID: e9f32f57-a8f0-4bfa-9b6c-7b377775f0f0 vRouter name: def Enabled: true |
|
日志说明 |
用户进行了创建SSL VPN网关的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The configuration item name already exists：配置项名称已存在 · The vRouter doesn't exist：指定的虚拟路由器不存在 · The configuration item and the bound vRouter belong to different tenants：配置项所属租户与绑定的虚拟路由器所属租户不一致 · The SSL policy doesn't exist：指定的SSL策略不存在 · The gateway and SSL policy belong to different tenants：该网关所属租户与指定的SSL策略所属租户不一致 · If two gateways are bound with different vRouters but the vRouters share the same external IP address, the gateways must use different port numbers：不同网关绑定的虚拟路由器共享外网IP时，网关端口号不能相同 · No external network is specified for the vRouter：指定的虚拟路由器未配置外部网络 · The configuration item ID already exists：配置项ID已存在 · The tenant doesn't exist：指定的租户不存在 · The controller is not the active leader：该控制组件不是主Leader · The operation requires the administrator privilege：您需要管理员权限才能执行此操作 · Configuration recovery is in progress：配置正在恢复过程中 · The service has not been found：服务未启动 · Invalid gateway port number：无效的网关端口号 · Unknown error：未知错误 · Invalid description：无效的描述 · The gateway name is required：网关名称不能为空 · Invalid gateway name：无效的网关名称 · The gateway port number is required：网关端口号不能为空 · The tenant ID is required：租户ID不能为空 · Invalid tenant ID：无效的租户ID · The vRouter ID is required：虚拟路由器ID不能为空 · Invalid vRouter ID：无效的虚拟路由器ID · Invalid JSON format：无效的JSON串格式 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_SSLVPN_GATEWAY_OP |
|
日志内容 |
Updated SSL VPN gateway $1 |
|
参数解释 |
$1：SSL VPN网关的配置信息 |
|
举例 |
Updated SSL VPN gateway ID: 70dc3186-ac5b-4ba1-ac7f-7a27ef566efb Name: sslvpngateway Tenant ID: ffffffff-0000-0000-0000-000000000001 Tenant name: default IP: 192.168.0.1 Port: 443 Description: sslvpngateway vRouter ID: e9f32f57-a8f0-4bfa-9b6c-7b377775f0f0 vRouter name: def Enabled: true |
|
日志说明 |
用户进行了修改SSL VPN网关的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The configuration item doesn’t exist：配置项不存在 · The SSL policy doesn't exist：指定的SSL策略不存在 · The gateway and SSL policy belong to different tenants：该网关所属租户与指定的SSL策略所属租户不一致 · If two gateways are bound with different vRouters but the vRouters share the same external IP address, the gateways must use different port numbers：不同网关绑定的虚拟路由器共享外网IP时，网关端口号不能相同 · No external network is specified for the vRouter：指定的虚拟路由器未配置外部网络 · The configuration item and the bound vRouter belong to different tenants：配置项所属租户与绑定的虚拟路由器所属租户不一致 · The gateway is being used by SSL VPN contexts：该网关正在被访问实例引用 · The controller is not the active leader：该控制组件不是主Leader · The operation requires the administrator privilege：您需要管理员权限才能执行此操作 · Configuration recovery is in progress：配置正在恢复过程中 · The service has not been found：服务未启动 · The gateway doesn't exist：该网关不存在 · Invalid gateway port number：无效的网关端口号 · The vRouter doesn't exist：指定的虚拟路由器不存在 · Unknown error：未知错误 · Invalid description：无效的描述 · Invalid gateway ID：无效的网关ID · The gateway ID is read only：网关ID为只读字段 · Invalid gateway name：无效的网关名称 · The gateway name is read only：网关名称为只读字段 · The tenant ID is read only：租户ID为只读字段 · The vRouter ID is required：虚拟路由器ID不能为空 · Invalid JSON format：无效的JSON串格式 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_SSLVPN_GATEWAY_OP |
|
日志内容 |
Deleted SSL VPN gateway $1 |
|
参数解释 |
$1：SSL VPN网关的名称 |
|
举例 |
Deleted SSL VPN gateway gateway |
|
日志说明 |
用户进行了删除SSL VPN网关的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The gateway doesn't exist：该网关不存在 · The gateway is being used by SSL VPN contexts：该网关正在被访问实例引用 · The controller is not the active leader：该控制组件不是主Leader · The operation requires the administrator privilege：您需要管理员权限才能执行此操作 · Configuration recovery is in progress：配置正在恢复过程中 · The service has not been found：服务未启动 · Unknown error：未知错误 · Invalid gateway ID：无效的网关ID · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_SSLVPN_POOL_OP |
|
日志内容 |
Created SSL VPN IP address pool $1 |
|
参数解释 |
$1：SSL VPN地址池的配置信息 |
|
举例 |
Created SSL VPN IP address pool ID: 6835896c-5152-4bed-a2ab-092c9980e2b8 Name: ippool Tenant ID: ffffffff-0000-0000-0000-000000000001 Tenant name: default vRouter ID: ffffffff-0000-0000-0000-000000000001 vRouter name: vrt1 Start IP address: 14.14.14.14 End IP address: 14.14.14.16 Mask: 255.255.0.0 Description: ippool |
|
日志说明 |
用户进行了创建SSL VPN地址池的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The configuration item ID already exists：配置项ID已存在 · The configuration item name already exists：配置项名称已存在 · The start IP address must be lower than the end IP address：结束IP地址必须大于起始IP地址 · Maximum number of SSL VPN AC interfaces was reached on the gateway resources for the specified vRouter：指定的虚拟路由器绑定的网关资源上SSL VPN AC接口个数超出限制 · Overlapping IP address pool range：该地址池的IP地址范围与其他地址池重叠 · The tenant doesn't exist：指定的租户不存在 · The vRouter doesn't exist：指定的虚拟路由器不存在 · The configuration item and the bound vRouter belong to different tenants：配置项所属租户与绑定的虚拟路由器所属租户不一致 · The controller is not the active leader：该控制组件不是主Leader · The operation requires the administrator privilege：您需要管理员权限才能执行此操作 · For different IP address pools, their start IP addresses must belong to different subnets：不同地址池的起始IP地址不能属于同一网段 · Configuration recovery is in progress：配置正在恢复过程中 · The service has not been found：服务未启动 · Invalid start IP address：无效的起始IP地址 · Invalid end IP address：无效的结束IP地址 · Unknown error：未知错误 · Invalid description：无效的描述 · Invalid IP address pool name：无效的地址池名称 · The IP address pool name is required：地址池名称不能为空 · The start IP address is required：起始IP地址不能为空 · The end IP address is required：结束IP地址不能为空 · The subnet mask is required：子网掩码不能为空 · Invalid subnet mask：无效的地址池子网掩码 · The tenant ID is required：租户ID不能为空 · Invalid tenant ID：无效的租户ID · The vRouter ID is required：虚拟路由器ID不能为空 · Invalid vRouter ID：无效的虚拟路由器ID · Invalid JSON format：无效的JSON串格式 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_SSLVPN_POOL_OP |
|
日志内容 |
Updated SSL VPN IP address pool $1 |
|
参数解释 |
$1：SSL VPN地址池的配置信息 |
|
举例 |
Updated SSL VPN IP address pool ID: 6835896c-5152-4bed-a2ab-092c9980e2b8 Name: ippool Tenant ID: ffffffff-0000-0000-0000-000000000001 Tenant name: default vRouter ID: ffffffff-0000-0000-0000-000000000001 vRouter name: vrt1 Start IP address: 14.14.14.14 End IP address: 14.14.14.16 Mask: 255.255.0.0 Description: ippool |
|
日志说明 |
用户进行了修改SSL VPN地址池的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The configuration item doesn’t exist：配置项不存在 · The start IP address must be lower than the end IP address：结束IP地址必须大于起始IP地址 · Overlapping IP address pool range：该地址池的IP地址范围与其他地址池重叠 · The vRouter doesn't exist：指定的虚拟路由器不存在 · The configuration item and the bound vRouter belong to different tenants：配置项所属租户与绑定的虚拟路由器所属租户不一致 · The controller is not the active leader：该控制组件不是主Leader · The operation requires the administrator privilege：您需要管理员权限才能执行此操作 · For different IP address pools, their start IP addresses must belong to different subnets：不同地址池的起始IP地址不能属于同一网段 · Configuration recovery is in progress：配置正在恢复过程中 · The service has not been found：服务未启动 · Invalid start IP address：无效的起始IP地址 · Invalid end IP address：无效的结束IP地址 · The IP address pool doesn't exist：指定的地址池不存在 · The IP address pool is being used by SSL VPN contexts：该地址池正在被访问实例引用 · Maximum number of SSL VPN AC interfaces was reached on the gateway resources for the specified vRouter：指定的虚拟路由器绑定的网关资源上SSL VPN AC接口个数超出限制 · Unknown error：未知错误 · Invalid description：无效的描述 · The IP address pool ID is read only：地址池ID为只读字段 · Invalid IP address pool ID：无效的地址池ID · Invalid IP address pool name：无效的地址池名称 · The IP address pool name is read only：地址池名称为只读字段 · Invalid subnet mask：地址池子网掩码无效 · The tenant ID is read only：租户ID为只读字段 · The vRouter ID is required：虚拟路由器ID不能为空 · Invalid JSON format：无效的JSON串格式 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_SSLVPN_POOL_OP |
|
日志内容 |
Deleted SSL VPN IP address pool $1 |
|
参数解释 |
$1：SSL VPN地址池的名称 |
|
举例 |
Deleted SSL VPN IP address pool ippool |
|
日志说明 |
用户进行了删除SSL VPN地址池的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The IP address pool doesn't exist：该地址池不存在 · The IP address pool is being used by SSL VPN contexts：该地址池正在被访问实例引用 · The controller is not the active leader：该控制组件不是主Leader · The operation requires the administrator privilege：您需要管理员权限才能执行此操作 · Configuration recovery is in progress：配置正在恢复过程中 · The service has not been found：服务未启动 · Unknown error：未知错误 · Invalid IP address pool ID：无效的地址池ID · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_SSLVPN_CONTEXT_OP |
|
日志内容 |
Created SSL VPN context $1 |
|
参数解释 |
$1：SSL VPN访问实例的配置信息 |
|
举例 |
Created SSL VPN context ID: 6835896c-5152-4bed-a2ab-092c9980e2b8 Name: 123 Tenant ID: ffffffff-0000-0000-0000-000000000001 Tenant name: default vRouter ID: e9f32f57-a8f0-4bfa-9b6c-7b377775f0f0 vRouter name: def SSL VPN gateway ID: 83974693-027a-441b-9c40-805910abfdd2 SSL VPN gateway name: gateway IP address pool ID: 0b403e57-06b8-41ee-85f6-6feb8fa4c2bc IP address pool name: ippool ISP domain: aaa Description: sslvpnContext Enabled: true |
|
日志说明 |
用户进行了创建SSL VPN访问实例的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The configuration item ID already exists：配置项ID已存在 · The tenant doesn't exist：指定的租户不存在 · The vRouter doesn't exist：指定的虚拟路由器不存在 · The gateway doesn't exist：指定的网关不存在 · The configuration item and the bound vRouter belong to different tenants：配置项所属租户与绑定的虚拟路由器所属租户不一致 · The SSL VPN context and gateway belong to different vRouters：该访问实例绑定的虚拟路由器与指定的网关绑定的虚拟路由器不一致 · The configuration item name already exists：配置项的名称已存在 · The IP address pool doesn't exist：指定的地址池不存在 · The SSL VPN context and IP address pool belong to different tenants：该访问实例所属租户与指定的地址池所属租户不一致 · The controller is not the active leader：该控制组件不是主Leader · The operation requires the administrator privilege：您需要管理员权限才能执行此操作 · Configuration recovery is in progress：配置正在恢复过程中 · The service has not been found：服务未启动 · Invalid domain name：无效的域名 · Unknown error：未知错误 · Invalid description：无效的描述 · The gateway ID is required：网关ID不能为空 · The IP address pool ID is required：地址池ID不能为空 · The SSL VPN context name is required：访问实例名称不能为空 · Invalid SSL VPN context name：无效的访问实例名称 · Invalid ISP domain name：无效的ISP域名称 · The tenant ID is required：租户ID不能为空 · Invalid tenant ID：无效的租户ID · The vRouter ID is required：虚拟路由器ID不能为空 · Invalid vRouter ID：无效的虚拟路由器ID · Invalid JSON format：无效的JSON串格式 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_SSLVPN_CONTEXT_OP |
|
日志内容 |
Updated SSL VPN context $1 |
|
参数解释 |
$1：SSL VPN访问实例的配置信息 |
|
举例 |
Updated SSL VPN context ID: 6835896c-5152-4bed-a2ab-092c9980e2b8 Name: 123 Tenant ID: ffffffff-0000-0000-0000-000000000001 Tenant name: default vRouter ID: e9f32f57-a8f0-4bfa-9b6c-7b377775f0f0 vRouter name: def SSL VPN gateway ID: 83974693-027a-441b-9c40-805910abfdd2 SSL VPN gateway name: gateway IP address pool ID: 0b403e57-06b8-41ee-85f6-6feb8fa4c2bc IP address pool name: ippool ISP domain: aaa Description: sslvpnContext Enabled: true |
|
日志说明 |
用户进行了修改SSL VPN访问实例的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The SSL VPN context doesn't exist：指定的访问实例不存在 · The gateway doesn't exist：指定的网关不存在 · The SSL VPN context and gateway belong to different vRouters：该访问实例绑定的虚拟路由器与指定的网关绑定的虚拟路由器不一致 · The IP address pool doesn't exist：指定的地址池不存在 · The SSL VPN context and IP address pool belong to different tenants：该访问实例所属租户与指定的地址池所属租户不一致 · The configuration item and the bound vRouter belong to different tenants：配置项所属租户与指定的地址池所属租户不一致 · The tenant doesn't exist：指定的租户不存在 · The vRouter doesn't exist：指定的虚拟路由器不存在 · The configuration item and the bound vRouter belong to different tenants：配置项与绑定的虚拟路由器属于不同的租户 · The controller is not the active leader：该控制组件不是主Leader · The operation requires the administrator privilege：您需要管理员权限才能执行此操作 · Configuration recovery is in progress：配置正在恢复过程中 · The service has not been found：服务未启动 · Invalid domain name：无效的域名 · Unknown error：未知错误 · Invalid description：无效的描述 · The gateway ID is required：网关ID不能为空 · The IP address pool ID is required：地址池ID不能为空 · The SSL VPN context ID is read only：访问实例ID为只读字段 · Invalid SSL VPN context name：无效的访问实例名称 · The SSL VPN context name is read only：访问实例名称为只读字段 · Invalid ISP domain name：无效的ISP域名称 · The tenant ID is read only：租户ID为只读字段 · Invalid JSON format：无效的JSON串格式 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_SSLVPN_CONTEXT_OP |
|
日志内容 |
Deleted SSL VPN context $1 |
|
参数解释 |
$1：SSL VPN访问实例的名称 |
|
举例 |
Deleted SSL VPN context context1 |
|
日志说明 |
用户进行了删除SSL VPN访问实例的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The SSL VPN context doesn't exist：指定的访问实例不存在 · The controller is not the active leader：该控制组件不是主Leader · The operation requires the administrator privilege：您需要管理员权限才能执行此操作 · Configuration recovery is in progress：配置正在恢复过程中 · The service has not been found：服务未启动 · Unknown error：未知错误 · Invalid SSL VPN context ID：无效的访问实例ID · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_ROUTE_LIST_OP |
|
日志内容 |
Created route list $1 |
|
参数解释 |
$1：路由列表的配置信息 |
|
举例 |
Created route list ID: 6835896c-5152-4bed-a2ab-092c9980e2b8 Name: 123 SSL VPN context ID: e5471ec1-4a5d-4ce8-81a8-70fc74634c24 SSL VPN context name: sslvpncontext Route list: [ CIDR: 192.168.0.1/8, CIDR: 192.168.0.2/16 ] |
|
日志说明 |
用户进行了创建路由列表的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The configuration item ID already exists：配置项ID已存在 · The SSL VPN context doesn't exist：指定的访问实例不存在 · The configuration item name already exists：配置项名称已存在 · The controller is not the active leader：该控制组件不是主Leader · The operation requires the administrator privilege：您需要管理员权限才能执行此操作 · Configuration recovery is in progress：配置正在恢复过程中 · The service has not been found：服务未启动 · Invalid CIDR：无效的目的网段 · Unknown error：未知错误 · The SSL VPN context ID is required：访问实例ID不能为空 · Invalid route list name：无效的路由列表名称 · The route list name is required：路由列表名称不能为空 · Invalid JSON format：无效的JSON串格式 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_ROUTE_LIST_OP |
|
日志内容 |
Updated route list $1 |
|
参数解释 |
$1：路由列表的配置信息 |
|
举例 |
Updated route list ID: 6835896c-5152-4bed-a2ab-092c9980e2b8 Name: 123 SSL VPN context ID: e5471ec1-4a5d-4ce8-81a8-70fc74634c24 SSL VPN context name: sslvpncontext Route list: [ CIDR: 192.168.0.1/8, CIDR: 192.168.0.2/16 ] |
|
日志说明 |
用户进行了修改路由列表的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The route list doesn't exist：指定的路由列表不存在 · The SSL VPN context doesn't exist：指定的访问实例不存在 · The controller is not the active leader：该控制组件不是主Leader · The operation requires the administrator privilege：您需要管理员权限才能执行此操作 · Configuration recovery is in progress：配置正在恢复过程中 · The service has not been found：服务未启动 · Invalid CIDR：无效的目的网段 · Unknown error：未知错误 · Invalid SSL VPN context ID：无效的访问实例ID · The SSL VPN context ID is read only：访问实例ID为只读字段 · Invalid policy group ID：无效的策略组ID · The route list ID is read only：路由列表ID为只读字段 · The route list name is read only：路由列表名称为只读字段 · The route list doesn't exist：指定的路由列表不存在 · Invalid JSON format：无效的JSON串格式 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_ROUTE_LIST_OP |
|
日志内容 |
Deleted route list $1 |
|
参数解释 |
$1：路由列表的名称 |
|
举例 |
Deleted route list routelist1 |
|
日志说明 |
用户进行了删除路由列表的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The route list doesn't exist：该路由列表不存在 · The route list is being used by policy groups：该路由列表正在被策略组引用 · The controller is not the active leader：该控制组件不是主Leader · The operation requires the administrator privilege：您需要管理员权限才能执行此操作 · Configuration recovery is in progress：配置正在恢复过程中 · The service has not been found：服务未启动 · Unknown error：未知错误 · The route list doesn't exist：指定的路由列表不存在 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_POLICY_GROUP_OP |
|
日志内容 |
Created policy group $1 |
|
参数解释 |
$1：策略组的配置信息 |
|
举例 |
Created policy group ID: 6835896c-5152-4bed-a2ab-092c9980e2b8 Name: 123 SSL VPN context ID: e5471ec1-4a5d-4ce8-81a8-70fc74634c24 SSL VPN context name: sslvpncontext Route type: ROUTE_LIST Route list ID: 3b020a55-cc55-4882-b6f1-d26d5f21f8a9 Route list name: routelist |
|
日志说明 |
用户进行了创建策略组的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The SSL VPN context doesn't exist：指定的访问实例不存在 · The route list doesn't exist：指定的路由列表不存在 · The configuration item ID already exists：配置项ID已存在 · The configuration item name already exists：配置项名称已存在 · The controller is not the active leader：该控制组件不是主Leader · The operation requires the administrator privilege：您需要管理员权限才能执行此操作 · Configuration recovery is in progress：配置正在恢复过程中 · The service has not been found：服务未启动 · Invalid policy group name：无效的策略组名称 · Unknown error：未知错误 · The SSL VPN context ID is required：访问实例ID不能为空 · The policy group name is required：策略组名称不能为空 · The route list ID is required：路由列表ID不能为空 · The route list doesn't exist：指定的路由列表不存在 · Invalid JSON format：无效的JSON串格式 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_POLICY_GROUP_OP |
|
日志内容 |
Updated policy group $1 |
|
参数解释 |
$1：策略组的配置信息 |
|
举例 |
Updated policy group ID: 6835896c-5152-4bed-a2ab-092c9980e2b8 Name: 123 SSL VPN context ID: e5471ec1-4a5d-4ce8-81a8-70fc74634c24 SSL VPN context name: sslvpncontext Route type: ROUTE_LIST Route list ID: 3b020a55-cc55-4882-b6f1-d26d5f21f8a9 Route list name: routelist |
|
日志说明 |
用户进行了修改策略组的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The policy group doesn't exist.：指定的策略组不存在 · The SSL VPN context doesn't exist：指定的访问实例不存在 · The route list doesn't exist：指定的路由列表不存在 · The controller is not the active leader：该控制组件不是主Leader · The operation requires the administrator privilege：您需要管理员权限才能执行此操作 · Configuration recovery is in progress：配置正在恢复过程中 · The service has not been found：服务未启动 · Invalid policy group name：无效的策略组名称 · Unknown error：未知错误 · Invalid SSL VPN context ID：无效的访问实例ID · The SSL VPN context ID is read only：访问实例ID为只读字段 · Invalid policy group ID：无效的策略组ID · The policy group ID is read only：策略组ID为只读字段 · The policy group name is read only：策略组名称为只读字段 · Invalid JSON format：无效的JSON串格式 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_POLICY_GROUP_OP |
|
日志内容 |
Deleted policy group $1 |
|
参数解释 |
$1：策略组的名称 |
|
举例 |
Deleted policy group policygroup1 |
|
日志说明 |
用户进行了删除策略组的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The policy group doesn't exist：该策略组不存在 · The controller is not the active leader：该控制组件不是主Leader · The operation requires the administrator privilege：您需要管理员权限才能执行此操作 · Configuration recovery is in progress：配置正在恢复过程中 · The service has not been found：服务未启动 · Unknown error：未知错误 · The policy group doesn't exist：指定的策略组不存在 · Invalid JSON format：无效的JSON串格式 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_SSLVPN_USER_OP |
|
日志内容 |
Created SSL VPN user $1 |
|
参数解释 |
$1：SSL VPN用户的配置信息 |
|
举例 |
Created SSL VPN user ID : 53b06a75-bd34-4b68-864d-243b171ba70f Name : user1 Description : ssl vpn user Tenant ID : 6632aef0-5c2a-49b5-8ac0-ec4a9809f0de Tenant name : default Username : sdn User password : sdn123456 User type : local |
|
日志说明 |
用户进行了创建SSL VPN用户的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid user UUID：无效的用户UUID · The login username is required：未指定登录用户名 · The password is required：未指定登录密码 · The user type is required：未指定用户类型 · Invalid username：无效的用户名称 · Invalid user type：无效的用户类型 · Invalid login username：无效的登录用户名 · Invalid password：无效的登录密码 · The login username already exists：登录用户名已存在 · Invalid JSON format：无效的JSON串格式 · The controller is not the active leader：该控制组件不是主Leader · The operation requires the administrator privilege：您需要管理员权限才能执行此操作 · Configuration recovery is in progress：配置正在恢复过程中 · The service has not been found：服务未启动 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_SSLVPN_USER_OP |
|
日志内容 |
Updated SSL VPN user $1 |
|
参数解释 |
$1：SSL VPN用户的配置信息 |
|
举例 |
Updated SSL VPN user ID : 53b06a75-bd34-4b68-864d-243b171ba70f Name: user1 Description : ssl vpn user Tenant ID : 6632aef0-5c2a-49b5-8ac0-ec4a9809f0de Tenant name : default Username : sdn User password : sdn123456 User type : local |
|
日志说明 |
用户进行了修改SSL VPN用户的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid user UUID：无效的用户UUID · The user UUID cannot be edited：用户UUID不允许修改 · The user does not exist：指定的用户不存在 · The username cannot be edited：用户名称不允许修改 · The user type cannot be edited：用户类型不允许修改 · Invalid login username：无效的登录用户名 · Invalid password：无效的登录密码 · The login username already exists：登录用户名已存在 · Invalid JSON format：无效的JSON串格式 · The controller is not the active leader：该控制组件不是主Leader · The operation requires the administrator privilege：您需要管理员权限才能执行此操作 · Configuration recovery is in progress：配置正在恢复过程中 · The service has not been found：服务未启动 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_SSLVPN_USER_OP |
|
日志内容 |
Deleted SSL VPN user $1 |
|
参数解释 |
$1：SSL VPN用户的名称 |
|
举例 |
Deleted SSL VPN user user1 |
|
日志说明 |
用户进行了删除SSL VPN用户的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid user UUID：无效的用户UUID · The user does not exist：指定的用户不存在 · Cannot delete the user because it is being used：用户正在被使用,不允许删除 · Invalid JSON format：无效的JSON串格式 · The controller is not the active leader：该控制组件不是主Leader · The operation requires the administrator privilege：您需要管理员权限才能执行此操作 · Configuration recovery is in progress：配置正在恢复过程中 · The service has not been found：服务未启动 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_USER_GROUP_OP |
|
日志内容 |
Created SSL VPN user group $1 |
|
参数解释 |
$1：用户组的配置信息 |
|
举例 |
Created SSL VPN User Group ID: ee009cbb-6563-48f7-9c2b-922ea7447253 Name: userGroup1 Tenant ID: 6632aef0-5c2a-49b5-8ac0-ec4a9809f0de User group type : local Context ID: e45a4086-9c34-446c-9db3-25a77e20a2ea Policy group ID: e45a4086-9c34-446c-9db3-25a77e20a2ea Description: user group |
|
日志说明 |
用户进行了创建SSL VPN用户组的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid user group UUID：无效的用户组UUID · The user group type is required：未指定用户组类型 · Invalid user group type：无效的用户组类型 · Invalid user group name：无效的用户组名称 · The user group and the SSL VPN context must belong to the same tenant：用户组和访问实例的所属租户不一致 · The policy group has been used by another user group：策略组已被其他用户组使用 · The SSL VPN context and policy group bound to the user group must be both specified or both not specified：用户组绑定的访问实例和策略组必须同时指定或不指定 · Invalid JSON format：无效的JSON串格式 · The controller is not the active leader：该控制组件不是主Leader · The operation requires the administrator privilege：您需要管理员权限才能执行此操作 · Configuration recovery is in progress：配置正在恢复过程中 · The service has not been found：服务未启动 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_USER_GROUP_OP |
|
日志内容 |
Updated SSL VPN user group $1 |
|
参数解释 |
$1：SSL VPN用户组的配置信息 |
|
举例 |
Updated SSL VPN user group ID : ee009cbb-6563-48f7-9c2b-922ea7447253 Name : userGroup1 Tenant ID : 6632aef0-5c2a-49b5-8ac0-ec4a9809f0de User group Type : local Context ID : e45a4086-9c34-446c-9db3-25a77e20a2ea User list : [18b322aa-6b77-492e-b510-ee30c4c9cfc9, 53b06a75-bd34-4b68-864d-243b171ba70f, 3341bda9-ce17-4ff2-a7ff-a4506df184e4, 72345b2e-b716-43f5-8374-7376506551c1] Policy group ID: e45a4086-9c34-446c-9db3-25a77e20a2ea Description : user group |
|
日志说明 |
用户进行了修改SSL VPN用户组的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The user group UUID cannot be edited：用户组UUID不允许修改 · The user group name cannot be edited：用户组名称不允许修改 · The tenant to which the user group belongs cannot be edited：用户组所属租户不允许修改 · The user group type cannot be edited：用户组类型不允许修改 · The user group does not exist：指定的用户组不存在 · The user group and the SSL VPN context must belong to the same tenant：用户组和访问实例的所属租户不一致 · The policy group has been used by another user group：策略组已被其他用户组使用 · The user has been used by another user group：用户已被其他用户组使用 · The user group does not contain the user：指定的用户组下不存在该用户 · The user and the user group must belong to the same tenant：用户和用户组所属租户不一致 · The user type and user group type must be the same：用户和用户组类型不一致 · The SSL VPN context and policy group bound to the user group must be both specified or both not specified：用户组绑定的访问实例和策略组必须同时指定或不指定 · Invalid JSON format：无效的JSON串格式 · The controller is not the active leader：该控制组件不是主Leader · The operation requires the administrator privilege：您需要管理员权限才能执行此操作 · Configuration recovery is in progress：配置正在恢复过程中 · The service has not been found：服务未启动 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_USER_GROUP_OP |
|
日志内容 |
Deleted SSL VPN user group $1 |
|
参数解释 |
$1：SSL VPN用户组的名称 |
|
举例 |
Deleted SSL VPN user group userGroup1 |
|
日志说明 |
用户进行了删除SSL VPN用户组的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid user group UUID：无效的用户组UUID · The user group does not exist：指定的用户组不存在 · Invalid JSON format：无效的JSON串格式 · The controller is not the active leader：该控制组件不是主Leader · The operation requires the administrator privilege：您需要管理员权限才能执行此操作 · Configuration recovery is in progress：配置正在恢复过程中 · The service has not been found：服务未启动 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 |
本节介绍租户管理模块输出的操作日志信息。
|
关键字 |
ADD_TENANT_OP |
|
日志内容 |
Added tenant $1 |
|
参数解释 |
$1：租户的配置信息 |
|
举例 |
Added tenant ID: ec4bf666-5c73-4897-b4fc-3fcbae79f746 Name: tenant1 Type: local-create VDS ID: ffffffff-0000-0000-0000-000000000001 Auto allocation: true Cloud region name: region Cloud domain name: domain |
|
日志说明 |
用户进行了创建租户的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service has not been found：未找到相应的服务 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · The length of name is too long：传入的JSON串中租户名称的长度太长 · Invalid parameter：无效的配置参数 · The tenant already exists：租户已存在 · The tenant name is required：租户名称不允许为空 · The VDS ID is required：VDS ID不能为空 · Invalid VDS ID ：无效的VDS ID · You have no privilege to perform this operation：用户无权限执行此操作 · Up to 255 characters, case sensitive：参数不能超过255个字符，区分大小写 |
|
关键字 |
UPDATE_TENANT_OP |
|
日志内容 |
Updated tenant $1 |
|
参数解释 |
$1：租户的配置信息 |
|
举例 |
Updated tenant ID: ec4bf666-5c73-4897-b4fc-3fcbae79f746 Name: tenant1 Type: local-create VDS ID: ffffffff-0000-0000-0000-000000000001 Auto allocation: true Cloud region name: region Cloud domain name: domain |
|
日志说明 |
用户进行了修改租户的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service has not been found：未找到相应的服务 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · The length of name is too long：传入的JSON串中租户名称的长度太长 · Invalid parameter：无效的配置参数 · The tenant name is required：租户名称不允许为空 · Can't modify the default tenant：默认租户不允许修改 · The VDS ID cannot be modified：VDS ID不允许修改 · The NEM service does not exist：NEM服务不存在 · Cannot modify the auto allocation setting because the tenant has automatically allocated resources：该租户下已存在自动分配的资源，不允许修改自动分配功能 · You have no privilege to perform this operation：用户无权限执行此操作 · You cannot edit or delete the cloud region name：云区域名称不允许修改或删除 · You cannot edit or delete the domain name：租户所属域不允许修改或删除 · Up to 255 characters, case sensitive：参数不能超过255个字符，区分大小写 · The border gateway has been bound to a vRouter configured with a south-north service chain：出口网关已被虚拟路由器绑定，并且虚拟路由器下配置了南北向服务链 |
|
关键字 |
DELETE_TENANT_OP |
|
日志内容 |
Delete tenant $1 |
|
参数解释 |
$1：租户的配置信息 |
|
举例 |
Delete tenant ID: ec4bf666-5c73-4897-b4fc-3fcbae79f746 Name: tenant1 Type: local-create |
|
日志说明 |
用户进行了删除租户的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service has not been found：未找到相应的服务 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Can't delete the default tenant：默认租户不允许删除 · The tenant has bound resources：租户已绑定资源 · A vPort has been configured for the tenant：本租户已配置虚拟端口 · You have no privilege to perform this operation：用户无权限执行此操作 · The tenant has already been bound to a gateway：该租户已经绑定出口网关 · An OSPF or OSPFv3 policy has been configured for the tenant：该租户已配置OSPF或OSPFv3策略 · A route policy has been configured for the tenant：该租户已配置路由策略 · An IP prefix has been configured for the tenant：该租户已配置地址前缀 · A security policyhas been configured for the tenant：本租户已配置安全策略 · A vRouter link hasbeen configured for the tenant：本租户已配置虚拟路由器连接 · A vRouterinterconnection has been configured for the tenant：本租户已配置虚拟路由器互通 · A network has been configured for the tenant：本租户已配置虚拟链路层网络 · A vRouter has been configured for the tenant：本租户已配置虚拟路由器 |
|
关键字 |
IMPORT_TENANTS_OP |
|
日志内容 |
Import tenants |
|
参数解释 |
无 |
|
举例 |
Import tenants |
|
日志说明 |
用户进行了导入租户的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service has not been found：未找到相应的服务 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · The Keystone URL can't be null：Keystone地址不允许为空 · The administrator name can't be null：管理员用户名不允许为空 · The administrator password can't be null：管理员密码不允许为空 · The administrator tenant can't be null：管理员租户不允许为空 · The Keystone URL is too long：Keystone地址的长度不合法 · The administrator name is too long：管理员用户名的长度不合法 · The administrator password is too long：管理员密码的长度不合法 · The administrator tenant name is too long：管理员租户的名字长度不合法 · Invalid parameter：无效的配置参数 · Invalid Keystone URL format：Keystone地址错误 · Failed to import tenant accounts from the OpenStack server：从OpenStack导入租户失败 · You have no privilege to perform this operation：用户无权限执行此操作 |
本节介绍第三方服务模块输出的操作日志信息。
|
关键字 |
CREATE_THIRD_PARTY_SERVICE_DEVICE_OP |
|
日志内容 |
Created third-party service device: $1 |
|
参数解释 |
$1：第三方服务设备配置信息 |
|
举例 |
Created third-party service device: UUID: 8032909d-47a1-4715-90af-5153ffe39899 Name: TP1 Description: text Incoming vPort VXLAN ID: 100 Outgoing vPort VXLAN ID: 200 Incoming vPort IP address: 1.1.1.1 Outgoing vPort IP address: 192.168.0.1 |
|
日志说明 |
用户进行了创建第三方服务设备的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · The service is disabled：服务未启动 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · Unknown internal server error：未知的内部服务器错误 · Invalid name：无效的名称 · Invalid description：无效的描述信息 · The specified tenant does not exist：指定的租户不存在 · Invalid access mode：无效的接入方式 · The vPort does not exist：指定的虚拟端口不存在 · The incoming vPort does not exist：指定的入虚拟端口不存在 · The outgoing vPort does not exist：指定的出虚拟端口不存在 · Invalid incoming vPort VXLAN ID：无效的入虚拟端口VXLAN ID · Invalid outgoing vPort VXLAN ID：无效的出虚拟端口VXLAN ID · Invalid incoming vPort IP address：无效的入虚拟端口IP地址 · Invalid outgoing vPort IP address：无效的出虚拟端口IP地址 · The ingress vPort IP address is required：入虚拟端口IP地址不能为空 · The egress vPort IP address is required：出虚拟端口IP地址不能为空 · The ingress vPort VXLAN ID is required：入虚拟端口VXLAN ID不能为空 · The egress vPort VXLAN ID is required：出虚拟端口VXLAN ID不能为空 · The UUID already exists：UUID已存在 · The name already exists：名称已存在 · The incoming vPort has been used by another third-party service device：入虚拟端口已被其他第三方服务设备占用 · The outgoing vPort has been used by another third-party service device：出虚拟端口已被其他第三方服务设备占用 · When the access mode is auto access, only the incoming vPort VXLAN ID, outgoing vPort VXLAN ID, incoming vPort IP address, and outgoing vPort IP address can be configured：当接入方式为自动接入时，仅支持配置入虚拟端口VXLAN ID、出虚拟端口VXLAN ID、入虚拟端口IP地址和出虚拟端口IP地址 · An egress vPort and an ingress vPort cannot belong to the same virtual link layer network：出虚拟端口与入虚拟端口不能属于同一虚拟链路层网络 · The type of egress/ingress vPort only supports phy：出/入虚拟端口的类型目前仅支持为phy · The access type of the third party service device is invalid：无效的第三方服务设备接入方式 · When the access mode is set to manual access, you cannot specify the ingress/egress vPort VXLAN ID or IP address：接入方式为手动接入时，不允许指定入虚拟端口和出虚拟端口的VXLAN和IP地址 · You have no privilege to perform this operation：用户无权限执行此操作 · Please specify a local IP address：本端身份不能为空 · Please specify a peer IP address：对端身份不能为空 · Please specify a local subnet：本端子网不能为空 · Please specify a peer subnet：远端子网不能为空 · Invalid local subnet：无效的本端子网 · Invalid peer subnet：无效的远端子网 · Make sure the local subnets do not overlap：本端子网中存在重叠的子网 · Make sure the peer subnets do not overlap：远端子网中存在重叠的子网 · Cannot configure IPsec settings for the third-party service device because its deployment mode is Single vPort：第三方服务设备为单臂时，不允许配置IPsec信息 · Cannot configure NAT settings for the third-party service device because its deployment mode is Single vPort：第三方服务设备为单臂时，不允许配置NAT功能 · The same IPsec settings have been specified：IPsec信息不允许重复 · Make sure the local and peer subnets do not overlap：本段子网和远端子网不允许重叠 · Make sure the local IP address and peer IP address are different：本端地址和对端地址不允许相同 · Make sure the local and peer IP addresses have not been specified in existing IPsec settings：本端地址、对端地址与已经存在的IPsec本端地址、对端地址重复 · Make sure the local and peer subnets do not overlap with the subnets in existing IPsec settings：本端子网、远端子网与已经存在的IPsec本端子网、远端子网重叠 |
|
关键字 |
UPDATE_THIRD_PARTY_SERVICE_DEVICE_OP |
|
日志内容 |
Updated third-party service device: $1 |
|
参数解释 |
$1：第三方服务设备配置信息 |
|
举例 |
Updated third-party service device: UUID: 8032909d-47a1-4715-90af-5153ffe39899 Name: TP1 Description: text1 |
|
日志说明 |
用户进行了修改第三方服务设备配置的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · The service is disabled：服务未启动 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · Unknown internal server error：未知的内部服务器错误 · The third-party service device does not exist：配置项不存在 · Invalid name：无效的名称 · Invalid description：无效的描述信息 · The tenant field is read only：租户为只读字段 · The access mode field is read only：接入方式为只读字段 · The incoming vPort VXLAN ID field is read only：入虚拟端口VXLAN ID为只读字段 · The outgoing vPort VXLAN ID field is read only：出虚拟端口VXLAN ID为只读字段 · The incoming vPort IP address field is read only：入虚拟端口IP地址为只读字段 · The outgoing vPort IP address field is read only：出虚拟端口IP地址为只读字段 · The incoming vPort field is read only：入虚拟端口为只读字段 · The outgoing vPort field is read only：出虚拟端口为只读字段 · The VIP list cannot be modified：VIP列表不允许修改 · The SNAT IP list cannot be modified：SNAT IP地址列表不允许修改 · You have no privilege to perform this operation：用户无权限执行此操作 · The local_address field is read-only：local_address为只读字段 · The peer_address field is read-only：peer_address为只读字段 · The local_cidrs field is read-only：local_cidrs为只读字段 · The peer_cidrs field is read-only：peer_cidrs为只读字段 |
|
关键字 |
DELETE_THIRD_PARTY_SERVICE_DEVICE_OP |
|
日志内容 |
Deleted third-party service device: $1 |
|
参数解释 |
$1：第三方服务设备名称 |
|
举例 |
Deleted third-party service device: fw1 |
|
日志说明 |
用户进行了删除第三方服务设备的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · The service is disabled：服务未启动 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · The third-party service device does not exist：配置项不存在 · Failed to delete the third-party service device because it has been used by a service：该第三方服务设备已被第三方服务功能引用 · Invalid UUID：无效的UUID · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_THIRD_PARTY_SERVICE_FUNC_OP |
|
日志内容 |
Created third-party service function: $1 |
|
参数解释 |
$1：第三方服务资源配置信息 |
|
举例 |
Created third-party service function: UUID: 8032909d-47a1-4715-90af-5153ffe39899 Name: TPservice Description: text Tenant: ffffffff-0000-0000-0000-000000000001 Third-party service device: 954a1680-fd27-4cc1-b5ec-8f530c81f57a |
|
日志说明 |
用户进行了创建第三方服务资源的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · The service is disabled：服务未启动 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · Unknown internal server error：未知的内部服务器错误 · Invalid name：无效的名称 · Invalid parameter：无效的配置参数 · Invalid description：无效的描述信息 · The tenant doesn’t exist：指定的租户不存在 · The UUID already exists：UUID已存在 · The third party service device is not existed：指定的第三方服务设备不存在 · Failed to bind third party service device because it is used by another third party service function：服务功能已被其他服务设备引用 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_THIRD_PARTY_SERVICE_FUNCTION_OP |
|
日志内容 |
Updated third-party service function: $1 |
|
参数解释 |
$1：第三方服务资源配置信息 |
|
举例 |
Updated third-party service function: UUID: 8032909d-47a1-4715-90af-5153ffe39899 Name: TPservice Description: text1 |
|
日志说明 |
用户进行了修改第三方服务资源配置的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · The service is disabled：服务未启动 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · Unknown internal server error：未知的内部服务器错误 · The third-party service device does not exist：配置项不存在 · Invalid name：无效的名称 · Invalid description：无效的描述信息 · The tenant field is read only：租户为只读字段 · The third-party service device field is read only：服务设备不可修改 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_THIRD_PARTY_SERVICE_FUNCTION_OP |
|
日志内容 |
Deleted third-party service function: $1 |
|
参数解释 |
$1：第三方服务资源名称 |
|
举例 |
Deleted third-party service function: TPservice |
|
日志说明 |
用户进行了删除第三方服务资源的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · The service is disabled：服务未启动 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · The third-party service does not exist：配置项不存在 · Failed to delete the third-party service because it has been used by a service chain：该第三方服务功能已被服务链引用 · Invalid UUID：无效的UUID · You have no privilege to perform this operation：用户无权限执行此操作 |
本节介绍第三方防火墙模块输出的操作日志信息。
|
关键字 |
ADD_TPFW_OP |
|
日志内容 |
Added third-party firewall $1. |
|
参数解释 |
$1：第三方防火墙名称，如名称不存在则显示为UUID |
|
举例 |
Added third-party firewall tpfw1. |
|
日志说明 |
用户进行了创建第三方防火墙的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · You have no privilege to perform the operation：当前用户无权限执行此操作 · Configuration recovery is in progress：配置正在恢复 · Invalid JSON format：无效JSON格式 · The configuration item already exists：配置项已存在 · The name field up to 60 characters, case sensitive. Valid characters include Chinese characters, letters, digits, and underscores (_).：名称字段最长60个字符，区分大小写，仅支持中文、字母、数字和下划线 · The description field up to 255 characters, case sensitive.：描述信息字段最长255个字符，区分大小写 · Incorrect UUID format of the synchronization operation：同步操作的UUID格式错误 · Can't find the BUS type for the operation：不能找到这种操作的bus类型 · Team HA startup failure：Team HA启动失败 · Team HA processing error：Team HA处理有误 · Data format error：数据格式有误 · Failed to insert the data：插入数据失败 · Failed to add the configuration：添加配置失败 · Failed to bind the dedicated subnet to the dedicated vRouter：绑定专属子网到专属虚拟路由器失败 · The redirect subnet can't be null：导流子网不能为空 · The redirect IP address can't be null：导流IP地址不能为空 · The dedicated vRouter can't be null：专属虚拟路由器不能为空 · The dedicated subnet can't be null：专属子网不能为空 · The dedicated IP address can't be null：专属IP地址不能为空 · The service NE can't be null：服务网元不能为空 · The UUID of the redirect vRouter is read-only：导流虚拟路由器UUID为只读参数 · The redirect subnet doesn't exist：指定的导流子网不存在 · The dedicated vRouter doesn't exist：指定的专属虚拟路由器不存在 · The dedicated subnet doesn't exist：指定的专属子网不存在 · The redirect IP address and dedicated IP address can't be the same：导流IP地址与专属IP地址不能相同 · The dedicated IP address is not in the dedicated subnet：专属IP地址不在专属子网的网段内 · The redirect IP address is not in the redirect subnet：导流IP地址不在导流子网的网段内 · The redirect subnet and dedicated subnet can't be the same：导流子网与专属子网不能相同 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_TPFW_OP |
|
日志内容 |
Updated third-party firewall $1. |
|
参数解释 |
$1：第三方防火墙名称，如名称不存在则显示为UUID |
|
举例 |
Updated third-party firewall tpfw1. |
|
日志说明 |
用户进行了修改第三方防火墙配置的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · You have no privilege to perform the operation：当前用户无权限执行此操作 · Configuration recovery is in progress：配置正在恢复 · UUID format error：指定的UUID格式错误 · The UUID can't be modified：UUID不支持修改 · Invalid JSON format：无效JSON格式 · Incorrect UUID format of the synchronization operation：同步操作的UUID格式错误 · Can't find the BUS type for the operation：不能找到这种操作的bus类型 · Team HA startup failure：Team HA启动失败 · Team HA processing error：Team HA处理有误 · Team HA update failure：Team HA更新失败 · The configuration doesn't exist：该配置不存在 · Failed to modify the configuration：修改配置失败 · The name field up to 60 characters, case sensitive. Valid characters include Chinese characters, letters, digits, and underscores (_).：名称字段最长60个字符，区分大小写，仅支持中文、字母、数字和下划线 · The description field up to 255 characters, case sensitive.：描述信息字段最长255个字符，区分大小写 · The name of the third-party firewall can't be modified：第三方防火墙名称不能修改 · The redirect IP address can't be modified：导流IP地址不支持修改 · The dedicated IP address can't be modified：专属IP地址不支持修改 · The service NE ID can't be modified：服务网元ID不支持修改 · A vRouter link already exists on the third-party firewall：第三方防火墙已存在虚拟路由器连接 · The UUID of the vRouter can't be modified：虚拟路由器UUID不支持修改 · The redirect vRouter doesn't exist：指定的导流虚拟路由器不存在 · Failed to add the redirect routing table：增加导流路由表失败 · Failed to add the dedicated routing table：增加专属路由表失败 · Failed to add the routes to the third-party firewall：第三方防火墙增加路由表项失败 · Failed to delete the dedicated routing table：删除专属路由表失败 · Failed to delete the redirect routing table：删除导流路由表失败 · Failed to bind the redirect subnet to the redirect vRouter：导流子网和导流虚拟路由器绑定失败 · Failed to unbound the redirect subnet from the redirect vRouter：导流子网与导流虚拟路由器解绑失败 · The redirect vRouter and dedicated vRouter are the same：指定的导流虚拟路由器与专属虚拟路由器相同 · The configuration doesn't exist：该配置不存在 · Data format error：数据格式有误 · Failed to update the data in the database ：在数据库中更新数据失败 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_TPFW_OP |
|
日志内容 |
Deleted third-party firewall $1. |
|
参数解释 |
$1：第三方防火墙名称，如名称不存在则显示为UUID |
|
举例 |
Deleted third-party firewall tpfw1. |
|
日志说明 |
用户进行了删除第三方防火墙的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · You have no privilege to perform the operation：当前用户无权限执行此操作 · Configuration recovery is in progress：配置正在恢复 · UUID format error：指定的UUID格式错误 · Incorrect UUID format of the synchronization operation：同步操作的UUID格式错误 · Can't find the BUS type for the operation：不能找到这种操作的bus类型 · Team HA startup failure：Team HA启动失败 · Team HA processing error：Team HA处理有误 · Team HA deletion failure：Team HA删除失败 · The configuration doesn't exist：该配置不存在 · Data deletion error：删除数据有误 · Can't delete the third-party firewall because it is already bound to a Redirect vRouter：该第三方防火墙已绑定导流虚拟路由器，无法删除 · Failed to unbind the dedicated vRouter from the dedicated subnet：专属虚拟路由器与专属子网解绑失败 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_VROUTERLINK_OP |
|
日志内容 |
Created vRouter link $1. |
|
参数解释 |
$1：虚拟路由器连接的名称，如名称不存在则显示UUID |
|
举例 |
Created vRouter link vrlink1. |
|
日志说明 |
用户进行了创建虚拟路由器连接的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · You have no privilege to perform the operation：当前用户无权限执行此操作 · Configuration recovery is in progress：配置正在恢复 · Invalid JSON format：无效JSON格式 · The configuration item already exists：配置项已存在 · The name field up to 60 characters, case sensitive. Valid characters include Chinese characters, letters, digits, and underscores (_).：名称字段最长60个字符，区分大小写，仅支持中文、字母、数字和下划线 · Team HA startup failure：Team HA启动失败 · Data format error：数据格式有误 · Failed to insert the data：插入数据失败 · Failed to add the configuration：添加配置失败 · Failed to create the vRouter link：虚拟路由器连接创建失败 · vRouter 1 doesn't exist：虚拟路由器1不存在 · vRouter 2 doesn't exist：虚拟路由器2不存在 · vRouter 1 can't be null：虚拟路由器1不能为空 · vRouter 2 can't be null：虚拟路由器2不能为空 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_VROUTERLINK_OP |
|
日志内容 |
Deleted vRouter link $1. |
|
参数解释 |
$1：虚拟路由器连接的名称，如名称不存在则显示UUID |
|
举例 |
Deleted vRouter link vrlink1. |
|
日志说明 |
用户进行了删除虚拟路由器连接的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · You have no privilege to perform the operation：当前用户无权限执行此操作 · Configuration recovery is in progress：配置正在恢复 · UUID format error：指定的UUID格式错误 · The configuration doesn't exist：该配置不存在 · Data format error：数据格式有误 · Team HA startup failure：Team HA启动失败 · Team HA deletion failure：Team HA删除失败 · Data deletion error：删除数据有误 · Failed to delete the vRouter link：删除虚拟路由器连接失败 |
本节介绍新建Underlay模块输出的操作日志信息。
|
关键字 |
CREATE_INTENT_TASK_OP |
|
日志内容 |
Created fabric setup task: $1. |
|
参数解释 |
$1：新建Fabric方案信息 |
|
举例 |
Created fabric setup task: id:[Id[value=3b1cb854-744b-4f30-b489-3701c40eaacc]] name:[simulateFabric] spineNum:[2] leafNum:[2] borderLeaf:[2] leafStatus:[single] step:[To Simulate Solution] buildNetworkProcessId:[null] sourceType:[null] addDataToSimDC:[false] |
|
日志说明 |
用户进行了创建“新建Fabric”方案的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · Please perform the operation on the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · Unknown internal server error：服务器未响应。 · You have no privilege to perform the operation：用户无权限执行此操作 · Expressing intent does not support IPv6：意图采集不支持IPv6 · The fabric setup task already exists：新建Fabric任务已存在 |
|
关键字 |
UPDATE_INTENT_TASK_OP |
|
日志内容 |
Updated fabric setup task: $1. |
|
参数解释 |
$1：新建Fabric方案信息 |
|
举例 |
Updated fabric setup task: id:[Id[value=3b1cb854-744b-4f30-b489-3701c40eaacc]] name:[simulateFabric] spineNum:[2] leafNum:[2] borderLeaf:[2] leafStatus:[single] step:[To Simulate Solution] buildNetworkProcessId:[null] sourceType:[null] addDataToSimDC:[false] |
|
日志说明 |
用户进行了修改“新建Fabric”方案的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · Please perform the operation on the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · Unknown internal server error：服务器未响应 · You have no privilege to perform the operation：用户无权限执行此操作 · The specified fabric setup task does not exist：指定的新建Fabric任务不存在 |
|
关键字 |
DELETE_INTENT_TASK_OP |
|
日志内容 |
Deleted fabric setup task: $1. |
|
参数解释 |
$1：新建Fabric方案ID |
|
举例 |
Deleted fabric setup task: id: [3a8465a6-32d3-4980-91a0-67c0af1f27d0] |
|
日志说明 |
用户进行了删除“新建Fabric”方案的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · Please perform the operation on the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · Unknown internal server error：服务器未响应 · You have no privilege to perform the operation：用户无权限执行此操作 · The specified fabric setup task does not exist：指定的新建Fabric任务不存在 · Underlay check in progress. Please wait and try again later：Underlay检测正在进行中，请稍后再试 · The simulation network is being built. Please try again later：仿真网络正在构建中，请稍后删除 |
|
关键字 |
ADJUST_FABRICSETUP_OP |
|
日志内容 |
Adjusted fabric setup task: $1 |
|
参数解释 |
$1：新建Fabric方案信息 |
|
举例 |
Adjusted fabric setup task: id:[Id[value=3b1cb854-744b-4f30-b489-3701c40eaacc]] name:[simulateFabric] spineNum:[2] leafNum:[2] borderLeaf:[2] leafStatus:[single] step:[Reset] buildNetworkProcessId:[null] sourceType:[null] addDataToSimDC:[false] |
|
日志说明 |
用户进行了调整“新建Fabric”方案的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：无效的JSON格式 · Please perform the operation on the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · Unknown internal server error：服务器未响应 · You have no privilege to perform the operation：用户无权限执行此操作 · The specified fabric setup task does not exist：指定的新建Fabric任务不存在 |
本节介绍云对接模块输出的操作日志信息。
|
关键字 |
CREATE_VCENTER_OP |
|
日志内容 |
Created vCenter $1. |
|
参数解释 |
$1：vCenter参数体 |
|
举例 |
Created vCenter { "uuid":"bce117e8-bf42-420f-9e2b-ca2a6cad9069", "name":"vCenter", "ip address":"3.2.6.3", "port number":"443", "tls protocol":"TLSv1.2", "certificate":"vcenter.cer", "connect status":"false", "smooth status":"consistant" “vlan_pool_id”:”6c28a7e8-b242-420f-a22b-ca2a691ca260” }. |
|
日志说明 |
用户进行了创建vCenter的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置恢复未完成 · The controller is not the active leader：该设备不是当前Leader控制组件 · The request is invalid：传入的JSON串错误 · Invalid vCenter name：无效的vCenter名称 · Invalid username：无效的用户名称 · Invalid password：无效的用户密码 · Invalid IP address：无效的IP地址 · The IP address already exists：IP地址已存在 · The specified certificate does not exist or is not activated：指定证书不存在或者未被激活 · Invalid TLS protocol：无效的TLS协议 · The port number must be an integer in the range of 0 to 65535：端口号必须为0~65535的整数 · The vCenter name already exists：该vCenter名称已存在 · The UUID already exists：该UUID已存在 · Each vCenter server must have a unique name：批量创建的vCenter的名称存在重复 · Each vCenter server must have a unique UUID：批量创建的vCenter的UUID存在重复 · Each vCenter server must have a unique IP address：批量创建的vCenter的IP地址存在重复 · The specified VLAN pool does not exist：指定的VLAN池不存在 · The VLAN pool has already been used by another resource：指定的VLAN池已被其他资源引用 · Failed to bind the vCenter platform to the VLAN pool：vCenter绑定VLAN池失败 · Please specify a VLAN pool configured for tenant access networks：输入的VLAN池非租户接入网类型 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_VCENTER_OP |
|
日志内容 |
Updated vCenter $1. |
|
参数解释 |
$1：vCenter的参数体 |
|
举例 |
Update vCenter { "uuid":"f4c6e8be-cea2-4b2a-9738-2aa6d7108e38", "name":"vCenter", "ip address":"6.3.2.3", "port number":"443", "tls protocol":"TLSv1.2", "certificate":"vcenter.cer", "connect status":"false", "smooth status":"consistant" }. |
|
日志说明 |
用户进行了修改vCenter的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置恢复未完成 · The controller is not the active leader：该设备不是当前Leader控制组件 · The request is invalid：传入的JSON串错误 · The specified vCenter does not exist：指定的vCenter不存在 · The vCenter name cannot be modified：vCenter名称不允许修改 · The IP address cannot be modified：IP地址不允许修改 · Invalid username：无效的用户名称 · Invalid password：无效的用户密码 · Invalid TLS protocol：无效的TLS协议 · The specified certificate does not exist or is not activated：指定证书不存在或者未被激活 · The specified VLAN pool does not exist：指定的VLAN池不存在 · The VLAN pool has already been used by another resource：指定的VLAN池已被其他资源引用 · The port number must be an integer in the range of 0 to 65535：端口号必须为0~65535的整数 · Failed to bind the vCenter platform to the VLAN pool：vCenter绑定VLAN池失败 · Failed to unbind the vCenter platform to the VLAN pool：vCenter解绑VLAN池失败 · Please specify a VLAN pool configured for tenant access networks：输入的VLAN池非租户接入网类型 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_VCENTER_OP |
|
日志内容 |
Deleted vCenter $1. |
|
参数解释 |
$1：vCenter的参数体 |
|
举例 |
Delete vCenter { "uuid":"f4c6e8be-cea2-4b2a-9738-2aa6d7108e38", "name":"vCenter", "ip address":"6.3.2.3", "port number":"4432", "tls protocol":"TLSv1.2", "certificate":"vcenter.cer", "connect status":"false", "smooth status":"consistant" }. |
|
日志说明 |
用户进行了删除vCenter的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置恢复未完成 · The controller is not the active leader：该设备不是当前Leader控制组件 · The specified vCenter does not exist：指定的vCenter不存在 · Cannot delete the vCenter because it contains VDSs：vCenter下存在VDS，不允许删除 · The specified VLAN ID in the VLAN pool has been allocated：指定的VLAN池内资源已被分配 · The specified VLAN pool does not exist：指定的VLAN池不存在 · Failed to unbind the vCenter platform to the VLAN pool：vCenter解绑VLAN池失败 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_VDS_OP |
|
日志内容 |
Added vCenter VDS $1. |
|
参数解释 |
$1：VDS参数体 |
|
举例 |
Added vCenter VDS { "name":"21", "dc_name":"21" “vds_version”:”6.0.0” }. |
|
日志说明 |
用户进行了创建VDS的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置恢复未完成 · The controller is not the active leader：该设备不是当前Leader控制组件 · The request is invalid：传入的JSON串错误 · Illegal VDS name：VDS名称不合法 · Illegal data center name：数据中心名称不合法 · In vCenter, only one vCenter data center and vCenter VDS binding relationship can be set：在vCenter中，只能设置一条vCenter数据中心与vCenter VDS绑定关系 · The specified vCenter does not exist：指定的vCenter不存在 · Invalid VDS version：无效的VDS版本号 · VDS already exists：VDS已存在 · You have no privilege to perform this operation：用户无权限执行此操作 · The vCenter VDS name cannot be the same as the distributed port group name in the same vCenter data center：同一个vCenter数据中心中vCenter VDS的名称与分布式端口组名称不能相同 · vCenter connection error：vCenter连接异常 |
|
关键字 |
DELETE_VDS_OP |
|
日志内容 |
Deleted vCenter VDS $1. |
|
参数解释 |
$1：VDS参数体 |
|
举例 |
Deleted vCenter VDS { "name":"21", "dc_name":"21" } |
|
用户进行了删除VDS的操作 |
|
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置恢复未完成 · The controller is not the active leader：该设备不是当前Leader控制组件 · The VDS does not exist：指定的VDS不存在 · Cannot delete the VDS because it has distributed port groups：指定的VDS下存在端口组，不允许删除 · The specified vCenter does not exist：指定的vCenter不存在 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_QOS_PROFILE_OP |
|
日志内容 |
Created QoS profile $1. |
|
参数解释 |
$1：QoS模板参数体 |
|
举例 |
Created QoS profile { "name":"qos1", "uuid":"2c0c46d2-84a4-4848-884e-91cac7fdb84d", "inbound_policy":{ "avg_bandwidth":"100000", "peak_bandwidth":"100000", "burst_size":"102400" }, "outbound_policy":{ "avg_bandwidth":"100000", "peak_bandwidth":"100000", "burst_size":"102400" } } |
|
日志说明 |
用户进行了创建QoS模板的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置恢复未完成 · The controller is not the active leader：该设备不是当前Leader控制组件 · The request is invalid：传入的JSON串错误 · Illegal QoS profile name：QoS模板名称不合法 · The QoS profile already exists：指定的QoS模板已存在 · The average bandwidth cannot be greater than the peak bandwidth：平均带宽不能大于带宽峰值 · The average bandwidth value must be an integer in the range of 1 to 9007199254740991：平均带宽必须为1-9007199254740991的整数 · The peak bandwidth value must be an integer in the range of 1 to 9007199254740991：带宽峰值必须为1-9007199254740991的整数 · The burst size must be an integer in the range of 1 to 9007199254740991：突发大小必须为1-9007199254740991的整数 · Each QoS profile must have a unique name：批量创建的QoS模板的名称存在重复 · Each QoS profile must have a unique UUID：批量创建的QoS模板的UUID存在重复 · The UUID already exists：该UUID已存在 · Invalid QoS policy staus：无效的QoS流量策略状态 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_QOS_PROFILE_OP |
|
日志内容 |
Updated QoS profile $1. |
|
参数解释 |
$1：QoS模板参数体 |
|
举例 |
Updated QoS profile { "name":"qos1", "uuid":"2c0c46d2-84a4-4848-884e-91cac7fdb84d", "inbound_policy":{ "avg_bandwidth":"100000", "peak_bandwidth":"100000", "burst_size":"102400" }, "outbound_policy":{ "avg_bandwidth":"100000", "peak_bandwidth":"100000", "burst_size":"102400" } } |
|
日志说明 |
用户进行了修改QoS模板的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置恢复未完成 · The controller is not the active leader：该设备不是当前Leader控制组件 · The request is invalid：传入的JSON串错误 · Illegal QoS profile name:QoS模板名称不合法 · The specified QoS profile does not exist:：指定的QoS模板不存在 · The average bandwidth cannot be greater than the peak bandwidth：平均带宽不能大于带宽峰值 · The average bandwidth value must be an integer in the range of 1 to 9007199254740991：平均带宽必须为1-9007199254740991的整数 · The peak bandwidth value must be an integer in the range of 1 to 9007199254740991：带宽峰值必须为1-9007199254740991的整数 · The burst size must be an integer in the range of 1 to 9007199254740991：突发大小必须为1-9007199254740991的整数 · Cannot edit the QoS profile name：QoS模板的名称不允许修改 · Invalid QoS policy staus：无效的QoS流量策略状态 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_QOS_PROFILE_OP |
|
日志内容 |
Deleted QoS profile $1. |
|
参数解释 |
$1：QoS模板参数体 |
|
举例 |
Deleted QoS profile { "name":"qos1", "uuid":"2c0c46d2-84a4-4848-884e-91cac7fdb84d", "inbound_policy":{ "avg_bandwidth":"100000", "peak_bandwidth":"100000", "burst_size":"102400" }, "outbound_policy":{ "avg_bandwidth":"100000", "peak_bandwidth":"100000", "burst_size":"102400" } } |
|
日志说明 |
用户进行了删除QoS模板的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置恢复未完成 · The controller is not the active leader：该设备不是当前Leader控制组件 · The specified QoS profile does not exist：指定的QoS模板不存在 · The specified QoS profile has been used and cannot be deleted：指定的QoS模板已被使用，不允许删除 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_VDS_DISTRIBUTED_PORT_GROUP_OP |
|
日志内容 |
Created distributed port group $1. |
|
参数解释 |
$1：分布式端口组部分参数体 |
|
举例 |
Created distributed port group { "uuid":"ba9d834d-7bcc-4dde-987a-b89167df29a2", "name":"ffffffff-0000-0000-0000-000000000001|xuni|21", "vdsID":"d0e9522b-c8f4-4a72-bfb5-76770cd15c00", "vlanType":"VLAN", "vlanRange":"21", "qosID":"f332a43f-a801-42c8-bdfc-78be1c9c1949", "vnetworkID":"9585fee4-52eb-4037-b410-3c7e7d218d01", "uplinkMode":"DEPENDENTUPLINK", "lagName":"null", "lbAlgorithms":"ROUTE_ON_ORIGINATING_VIRTUAL_POR", "interfaceAvailabilityZone":"null", “qosInboundFlowStatus":"enable", "qosOutboundFlowStatus":"disable" }. |
|
日志说明 |
用户进行了创建分布式端口组的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid parameter：参数不合法 · The distributed port group name cannot exceed 80 characters.：分布式端口组名称最长80个字符 · The specified vNetwork does not exist：指定的虚拟链路层网络不存在 · The link aggregation group name cannot exceed 16 characters.：链路聚合组名称最长16个字符 · The specified uplink mode does not exist.：上行链路方式不存在 · The VLAN type does not exist.：指定的VLAN类型不存在 · Invalid VLAN ID or VLAN range：VLAN ID或VLAN ID范围不合法 · Duplicated distributed port group names exist.：存在重复的分布式端口组名称 · The distributed port group already exists：指定的分布式端口组已存在 · Each distributed port group must have a unique UUID：批量创建的分布式端口组的UUID存在重复 · The distributed port group name already exists：分布式端口组名称已存在 · The specified QoS profile does not exist：指定的QoS模板不存在 · The specified uplink LB policy does not exist：上行链路LB策略不存在 · The VLAN type does not exist：VLAN类型不存在 · VLAN ID needs to be specified or VLAN pool needs to be configured：需指定VLAN ID或配置VLAN池 · No VLAN ID available：没有可用的VLAN ID · The distributed port group name already exists in the same vCenter datacenter：同一个vCenter数据中心中分布式端口组名称已存在 · Please specify a VLAN pool for the vCenter platform when no VLAN ID is specified：VLAN ID为空时，对应的vCenter必须配置VLAN池 · When multiple distributed port groups for different vNetworks use the same interface availability zone, make sure they do not contain the same or overlapping VLAN IDs：当分布式端口组引用同一个接口可用区且虚拟链路层网络不同时，VLAN ID不能相同或VLAN范围不能重叠 · No VLAN ID is available in the VLAN pool：VLAN池中无可分配的VLAN ID · The specified LAG name does not exist on VDS：指定的链路聚合组在VDS上不存在 · You have no privilege to perform this operation：用户无权限执行此操作 · The VLAN ID must be an integer in the range of 1 to 4094：VLAN ID的取值范围必须为1-4094的整数 · Invalid egress traffic shaping status：无效的输出流量调整状态 · Invalid ingress traffic shaping status：无效的输入流量调整状态 · When no QoS profile is bound to the distributed port group, you must leave both the ingress traffic shaping status and egress traffic shaping status fields empty：当分布式端口组未绑定QoS模板时，输入流量调整状态和输出流量调整状态的取值必须为空 · On the same vCenter server, if the vCenter VDSs of two distributed port groups are the same and the VLAN IDs of the two distributed port groups overlap, the vNetworks of the two distributed port groups must be the same：同一个vCenter下，分布式端口组的vCenter VDS相同且VLAN ID有重叠，则两者的虚拟链路层网络必须相同 · On the same vCenter server, if the vCenter VDSs of two distributed port groups are different, the VLAN IDs of the two distributed port groups cannot overlap：同一个vCenter下，分布式端口组的vCenter VDS不同，则两者的VLAN ID不能重叠 · The vCenter VDS name cannot be the same as the distributed port group name in the same vCenter data center：同一个vCenter数据中心中vCenter VDS的名称与分布式端口组名称不能相同。 · Please specify both the primary VLAN and secondary VLAN：主VLAN和从VLAN不能为空 · The primary VLAN and secondary VLAN cannot be the same：主VLAN和从VLAN不能相同 · The primary or secondary VLAN of the PVLAN conflicts with an existing VLAN：PVLAN与VLAN冲突 · The specified VLAN conflicts with the primary or secondary VLAN of a PVLAN.：VLAN与PVLAN冲突 · The specified PVLAN conflicts with another PVLAN：指定PVLAN与其他的PVLAN冲突 · The vNetwork of the PVLAN cannot be the same as the vNetwork of an existing VLAN：PVLAN绑定的虚拟链路层网络和已存在的VLAN的虚拟链路层网络不能相同 · When the PVLANs are different and the vNetwork is the same for two distributed port groups on different vCenter servers, the interface availability zones cannot be the same：不同的vCenter下，当分布式端口组的PVLAN不同，虚拟链路层网络相同时，接口可用区不能相同 · You cannot configure the PVLAN mapping for the distributed port group, because a different PVLAN mapping has been configured for another distributed port group configured with the same vCenter and vNetwork：相同vCenter下的相同的虚拟链路层网络不能接入不同的PVLAN映射 · Unknown internal server error：未知的内部服务器错误 · A PVLAN already exists with the specified UUID：PVLAN UUID已存在 · A PVLAN already exists with the specified name：PVLAN名称已存在 · The vNetwork specified for the PVLAN does not exist：PVLAN的虚拟链路层网络不存在 · The PVLAN data source must be default：PVLAN的来源必须为默认 · The PVLAN data source must be VMM：PVLAN的来源必须为VMM · Please specify a primary VLAN for the PVLAN：PVLAN的主VLAN不能为空 · The primary VLAN ID must be in the range of 1 to 4094：PVLAN的主VLAN取值范围为1-4094的整数 · Please specify a secondary VLAN：从VLAN不能为空 · You can specify only one secondary VLAN：只支持配置一个从VLAN · The secondary VLAN ID must be in the range of 1 to 4094：从VLAN的VLAN取值范围为1-4094的整数 · Insufficient resources in the VXLAN pool：VXLAN池资源不足 · No available VXLAN ID is obtained. Please verify correctness of the global VXLAN pool configuration and status：未分配到可用VXLAN ID, 请检查全局VXLAN池配置及状态 · vCenter connection error：vCenter连接异常 |
|
关键字 |
UPDATE_VDS_DISTRIBUTED_PORT_GROUP_OP |
|
日志内容 |
Updated distributed port group $1. |
|
参数解释 |
$1：分布式端口组的部分参数体 |
|
举例 |
Updated distributed port group { "uuid":"d150f90e-8ac5-4299-a9e0-27774e9315fc", "name":"ffffffff-0000-0000-0000-000000000001|xuni3|21", "vdsID":"d0e9522b-c8f4-4a72-bfb5-76770cd15c00", "vlanType":"VLAN", "vlanRange":"21", "qosID":"f332a43f-a801-42c8-bdfc-78be1c9c1949", "vnetworkID":"314ad88b-a105-4884-94f4-21d892e5eb60", "uplinkMode":"DEPENDENTUPLINK", "lagName":"null", "lbAlgorithms":"ROUTE_ON_ORIGINATING_VIRTUAL_POR", "interfaceAvailabilityZone":"null", “qosInboundFlowStatus":"enable", "qosOutboundFlowStatus":"disable" }. |
|
日志说明 |
用户进行了修改分布式端口组的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid parameter：参数不合法 · Invalid UUID：UUID不合法 · The specified distributed port group does not exist：指定的端口组不存在 · The specified uplink mode does not exist：上行链路方式不存在 · The specified uplink LB policy does not exist：上行链路LB策略不存在 · The specified QoS profile does not exist：指定的QoS模板不存在 · Cannot edit the distributed port group name：分布式端口组的名称不允许修改 · When multiple distributed port groups for different vNetworks use the same interface availability zone, make sure they do not contain the same or overlapping VLAN IDs：当分布式端口组引用同一个接口可用区且虚拟链路层网络不同时，VLAN ID不能相同或VLAN范围不能重叠 · Cannot edit the interface availability zone. It is being used by a distributed port group that has VMs：指定的分布式端口组下已存在VM，不允许修改接口可用区 · The specified LAG name does not exist on VDS：指定的链路聚合组在VDS上不存在 · You have no privilege to perform this operation：用户无权限执行此操作 · Invalid egress traffic shaping status：无效的输出流量调整状态 · Invalid ingress traffic shaping status：无效的输入流量调整状态 · When no QoS profile is bound to the distributed port group, you must leave both the ingress traffic shaping status and egress traffic shaping status fields empty：当分布式端口组未绑定QoS模板时，输入流量调整状态和输出流量调整状态的取值必须为空 · vCenter connection error：vCenter连接异常 |
|
关键字 |
DELETE_VDS_DISTRIBUTED_PORT_GROUP_OP |
|
日志内容 |
Deleted distributed port group $1. |
|
参数解释 |
$1：分布式端口组的部分参数体 |
|
举例 |
Deleted distributed port group { "uuid":"d2c4bad4-a81a-449c-a8d8-795647a75f26", "name":"ffffffff-0000-0000-0000-000000000001|xuni3|22", "vdsID":"d0e9522b-c8f4-4a72-bfb5-76770cd15c00", "vlanType":"VLAN", "vlanRange":"22", "qosID":"436192ec-b605-4d14-a317-0f1dea87de9a", "vnetworkID":"314ad88b-a105-4884-94f4-21d892e5eb60", "uplinkMode":"DEPENDENTUPLINK", "lagName":"null", "lbAlgorithms":"ROUTE_ON_ORIGINATING_VIRTUAL_POR", "interfaceAvailabilityZone":"null", "qosInboundFlowStatus":"disable", "qosOutboundFlowStatus ":"disable" }. |
|
日志说明 |
用户进行了删除分布式端口组的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid parameter：参数不合法 · Invalid UUID：UUID不合法 · The distributed port group contains VMs and cannot be deleted：分布式端口组存在VM，不允许删除 · The specified distributed port group does not exist：指定的端口组不存在 · You have no privilege to perform this operation：用户无权限执行此操作 · Unknown internal server error：未知的内部服务器错误 · The specified PVLAN does not exist：指定的PVLAN不存在 |
|
关键字 |
SYNC_VCENTER_OP |
|
日志内容 |
Synchronized data of vCenter: $1. |
|
参数解释 |
$1：vCenter名称 |
|
举例 |
Synchronized data of vCenter: vCenter1. |
|
日志说明 |
用户进行了vCenter的差异修复操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置恢复未完成 · The controller is not the active leader：该设备不是当前Leader控制组件 · vCenter connection error：vCenter连接异常 · The vCenter does not exist：指定的vCenter不存在 · Cannot audit or synchronize a vCenter that is in Audit or Sync state：vCenter在差异发现或修复状态下，不允许执行差异发现或修复操作 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
SYNC_VCENTER_VPORT_OP |
|
日志内容 |
Synchronized data of vPort: $1. |
|
参数解释 |
$1：虚拟端口UUID |
|
举例 |
Synchronized data of vPort: 29a70df9-cdee-4e9b-9ce1-df7f324246df. |
|
日志说明 |
用户进行了虚拟端口的差异修复操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置恢复未完成 · The controller is not the active leader：该设备不是当前Leader控制组件 · vCenter connection error：vCenter连接异常 · The vCenter does not exist：指定的vCenter不存在 · The vPort doesn't exist：指定的虚拟端口不存在 · Cannot audit or synchronize a vCenter that is in Audit or Sync state：vCenter在差异发现或修复状态下，不允许执行差异发现或修复操作 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_VCENTER_SMOOTH_SETTING_OP |
|
日志内容 |
Updated auto audit and sync settings for vCenters: audit interval:$1 minutes, auto audit state:$2, auto sync state:$3, audit schedule:$4, Schedule:{ "months":$5, "days of week":$6, "days of month":$7, "hh":$8, "mm":$9, "ss":$10 }. |
|
参数解释 |
$1：自动对账周期 $2：自动对账开关 $3：自动修复开关 $4：对账模式 $5：每月 $6：每周 $7：每天 $8：时 $9：分 $10：秒 |
|
举例 |
Updated auto audit and sync settings for vCenters: audit interval:null minutes, auto audit state:true, auto sync state:OFF, audit schedule:TIMING, Schedule:{ "months":"*", "days of week":"?", "days of month":"*", "hh":"0", "mm":"0", "ss":"0" }. |
|
日志说明 |
用户进行了修改自动对账&修复配置参数的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置恢复未完成 · The controller is not the active leader：该设备不是当前Leader控制组件 · The request is invalid：传入的JSON串错误 · Invalid auto smooth setting：无效的auto_smooth_setting · The value of the auto sync interval must be an integer in the range of 60 to 10080：自动同步周期必须为60～10080的整数 · Invalid sync parameters：无效的自动修复参数 · The vCenter does not exist：指定的vCenter不存在 · You have no privilege to perform this operation：用户无权限执行此操作 · Invalid audit schedule：无效的对账模式 · When the audit schedule is interval-based, you must specify the audit interval：当对账模式为周期对账时，对账间隔不能为空 · Please configure Cron expression parameters：Cron表达式参数不能为空 · Invalid Cron expression parameters：无效的Cron表达式参数 |
|
关键字 |
AUDIT_VCENTER_OP |
|
日志内容 |
Audited data of vCenter: $1. |
|
参数解释 |
$1：vCenter名称 |
|
举例 |
Audited data of vCenter: vcenter1. |
|
日志说明 |
用户进行了vCenter的差异审计操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress： 配置恢复未完成 · The controller is not the active leader：该设备不是当前Leader控制组件 · vCenter connection error：vCenter连接异常 · The vCenter does not exist：指定的vCenter不存在 · Cannot audit or synchronize a vCenter that is in Audit or Sync state：vCenter在差异发现或修复状态下，不允许执行差异发现或修复操作 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
EXPORT_VCENTER_DIFFERENCE_DETAILS_OP |
|
日志内容 |
Exported vCenter difference details: $1. |
|
参数解释 |
$1：vCenter名称 |
|
举例 |
Exported vCenter difference details: vcenter1. |
|
日志说明 |
用户进行了vCenter的差异详情导出操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress： 配置恢复未完成 · The controller is not the active leader：该设备不是当前Leader控制组件 · The vCenter does not exist：指定的vCenter不存在 · The vCenter platform is in Audit or Sync state. Please export the differences later：vCenter正在进行差异发现或者差异修复，请稍后再导出差异 · The specified vCenter platform is exporting configuration differences. Please try again later：指定的vCenter正在导出差异数据，请稍后再试 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATED_ZONE_OP |
|
日志内容 |
Created interface availability zone: $1. |
|
参数解释 |
$1：接口可用区信息 |
|
举例 |
Created interface availability zone: { "interface_availability_zones": [ { "id": "0ef2a524-b889-4fc9-8ab5-91b8287a5403", "name": "group01", "bind_port_list": [ { "device_id": "1ef2a524-b889-4fc9-8ab5-91b8287a5402", "port_name": "Ten-GigabitEthernet1/0/48" } ] }, { "id": "0ef2a524-b889-4fc9-8ab5-91b8287a540d", "name": "group02", "bind_port_list": [ { "device_id": "1ef2a524-b889-4fc9-8ab5-91b8287a5402", "port_name": "Ten-GigabitEthernet1/0/47" } ] } ] } |
|
日志说明 |
用户进行了添加接口可用区操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该设备不是当前Leader控制组件 · Configuration recovery is in progress：配置恢复未完成 · The specified resource does not exist：指定的资源不存在 · Invalid parameter：参数不合法 · The specified device does not exist：指定的设备不存在 · The device to which the interface belongs or the device to which a bound interface belongs is inactive：正在绑定的接口所属设备或已绑定的接口所属设备中存在未激活设备 · The device type doesn't match：指定设备的类型不匹配 · Non-VTEP interfaces exist：存在非VTEP接口 · Invalid UUID：无效的UUID · Invalid interface availability zone name：无效的接口可用区名称 · Duplicate interface availability zone name：存在重复的接口可用区名称 · Duplicate interface availability zone UUID：存在重复的接口可用区UUID · Duplicate interfaces exist in the interface availability zone：存在重复的接口可用区接口 · An interface availability zone already exists with the specified name：接口可用区名称已存在 · The specified device interface has already been bound to another interface availability zone：指定的设备接口已被其它的接口可用区绑定 · You have no privilege to perform this operation：用户无权限执行此操作 · The interface of the service leaf device is bound to a resource access template. You cannot apply VLAN-related mappings to the interface：Service Leaf设备的接口被资源接入模板绑定时，不可用于其他映射 |
|
关键字 |
DELETED_ZONE_OP |
|
日志内容 |
Deleted interface availability zone: $1. |
|
参数解释 |
$1：接口可用区信息 |
|
举例 |
Deleted interface availability zone { "name":" group02", "id":"cc7c3ead-0f7a-4422-8fcd-18d1e1f5cae9", "bind_port_list":[], } |
|
日志说明 |
用户进行了删除接口可用区操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该设备不是当前Leader控制组件 · Configuration recovery is in progress：配置恢复未完成 · The specified interface availability zone does not exist：指定的接口可用区不存在 · Cannot delete the interface availability zone. It has already been used by a distributed port group：指定的接口可用区已被分布式端口组引用，不允许删除 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATED_ZONE_OP |
|
日志内容 |
Updated interface availability zone: $1. |
|
参数解释 |
$1：接口可用区信息 |
|
举例 |
Updated interface availability zone: { "interface_availability_zone": { "id": "0ef2a524-b889-4fc9-8ab5-91b8287a540d", "name": "group01", "bind_port_list": [ { "device_id": "1ef2a524-b889-4fc9-8ab5-91b8287a5402", "port_name": "Ten-GigabitEthernet1/0/48" } ] } } |
|
日志说明 |
用户进行了修改接口可用区操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该设备不是当前Leader控制组件 · Configuration recovery is in progress：配置恢复未完成 · The specified resource does not exist：指定的资源不存在 · Invalid parameter：参数不合法 · The specified device does not exist：指定的设备不存在 · The device to which the interface belongs or the device to which a bound interface belongs is inactive：正在绑定的接口所属设备或已绑定的接口所属设备中存在未激活设备 · The device type doesn't match：指定设备的类型不匹配 · Non-VTEP interfaces exist：存在非VTEP接口 · The specified device interface is bound to another interface availability zone：指定的设备接口已绑定其它的接口可用区 · Invalid UUID：无效的UUID · Invalid interface availability zone name：无效的接口可用区名称 · You have no privilege to perform this operation：用户无权限执行此操作 · The interface of the service leaf device is bound to a resource access template. You cannot apply VLAN-related mappings to the interface：Service Leaf设备的接口被资源接入模板绑定时，不可用于其他映射 |
|
关键字 |
DISCOVER_VCENTER_OP |
|
日志内容 |
Discovered data of vCenter: $1. |
|
参数解释 |
$1：vCenter名称 |
|
举例 |
Discovered data of vCenter: vCenter1. |
|
日志说明 |
用户进行了vCenter数据发现操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The specified vCenter does not exist：指定的vCenter不存在 · vCenter connection error：vCenter连接异常 · The vCenter status does not allow audit smoothing and reverse management related operations：指定的vCenter在当前状态下不允许进行差异发现、差异修复和反向纳管操作 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
REVERSE_SYNC_VCENTER_OP |
|
日志内容 |
Pulled and incorporated data from vCenter: $1. |
|
参数解释 |
$1：vCenter名称 |
|
举例 |
Pulled and incorporated data from vCenter: vCenter1. |
|
日志说明 |
用户进行了vCenter数据纳管操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The specified vCenter does not exist：指定的vCenter不存在 · vCenter connection error：vCenter连接异常 · The vCenter status does not allow audit smoothing and reverse management related operations：指定的vCenter在当前状态下不允许进行差异发现、差异修复和反向纳管操作 · Invalid parameter：参数不合法 · The data to incorporate is inconsistent with the data discovered：数据纳管与数据发现内容不一致 · The specified vNetwork does not exist：指定的虚拟链路层网络不存在 · The specified VDS already exists：指定的VDS已存在 · You have no privilege to perform this operation：用户无权限执行此操作 · The vCenter VDS name cannot be the same as the distributed port group name in the same vCenter data center：同一个vCenter数据中心中vCenter VDS的名称与分布式端口组名称不能相同 |
|
关键字 |
CREATE_RHVM_OP |
|
日志内容 |
Created RHVM $1. |
|
参数解释 |
$1：RHVM参数体 |
|
举例 |
Created RHVM { "uuid":"cd05ab0b-d499-435b-80a5-d594282eb525", "name":"yuyang", "ip address":"192.168.125.1", "port number":"443", "vlan pool":"vlan-zj", "connect status":"false" "certificate name":"null", "smooth status":"init", "reverse status":"init" }. |
|
日志说明 |
用户进行了创建RHVM的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · Unknown error code：未知错误 · The controller is not the active leader：该设备不是当前Leader控制组件 · Server processing error：服务器处理失败 · The UUID already exists：该UUID已存在 · Invalid RedHat VM name：无效的RHVM名称 · Invalid username：无效的用户名称 · Invalid password：无效的用户密码 · The port number must be an integer in the range of 0 to 65535：端口号必须为0~65535的整数 · Invalid IP address：无效的IP地址 · Please specify a VLAN pool configured for tenant access networks：输入的VLAN池非租户接入网类型 · The specified VLAN pool does not exist：指定的VLAN池不存在 · The RedHat VM name already exists：RHVM名称已存在 · The IP address already exists：IP地址已存在 · Failed to bind the RHVM to a VLAN pool：RHVM绑定VLAN池失败 · Duplicate RHVM IPs in bulk creation：批量创建的RHVM的IP存在重复 · Duplicate RHVM names in bulk creation：批量创建的RHVM的名称存在重复 · Duplicate RHVM UUIDs in bulk creation：批量创建的RHVM的UUID存在重复 · You have no privilege to perform this operation：用户无权限执行此操作 · The specified certificate does not exist or is not activated：指定证书不存在或者未被激活 |
|
关键字 |
UPDATE_RHVM_OP |
|
日志内容 |
Updated RHVM $1. |
|
参数解释 |
$1：RHVM的参数体 |
|
举例 |
Updated RHVM { "uuid":"96bd9627-caf0-436e-aad1-885fe62ec274", "name":"13", "ip address":"192.168.25.3", "port number":"443", "vlan pool":"null", "connect status":"false", "certificate name":"null", "smooth status":"init", "reverse status":"init" }. |
|
日志说明 |
用户进行了修改RHVM的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · Unknown error code：未知错误 · The controller is not the active leader：该设备不是当前Leader控制组件 · Server processing error：服务器处理失败 · The specified RedHat VM does not exist：指定的RHVM不存在 · Invalid username：无效的用户名称 · Invalid password：无效的用户密码 · Please specify a VLAN pool configured for tenant access networks：输入的VLAN池非租户接入网类型 · The specified VLAN pool does not exist：指定的VLAN池不存在 · The specified VLAN ID in the VLAN pool has been allocated：指定的VLAN池内资源已被分配 · Cannot edit the RHVM name：RHVM名称不允许修改 · The port number must be an integer in the range of 0 to 65535：端口号必须为0~65535的整数 · The IP address cannot be modified：IP地址不允许修改 · You have no privilege to perform this operation：用户无权限执行此操作 · The specified certificate does not exist or is not activated：指定证书不存在或者未被激活 |
|
关键字 |
DELETE_RHVM_OP |
|
日志内容 |
Deleted RHVM $1. |
|
参数解释 |
$1：RHVM的参数体 |
|
举例 |
Deleted RHVM { "uuid":"ecc6f914-79dc-4fe2-97f1-5714c30f7f1c", "name":"1", "ip address":"192.168.23.3", "port number":"443", "vlan pool":"null", "connect status":"false", "certificate name":"null", "smooth status":"init", "reverse status":"init" }. |
|
日志说明 |
用户进行了删除RHVM的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · Unknown error code：未知错误 · The controller is not the active leader：该设备不是当前Leader控制组件 · Server processing error：服务器处理失败 · The specified RedHat VM does not exist：指定的RHVM不存在 · Cannot delete the RHVM, because it has logical networks：RHVM下存在逻辑网络，不允许删除 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
RECONNECT_RHVM_OP |
|
日志内容 |
Reconnected RHVM $1. |
|
参数解释 |
$1：RHVM的参数体 |
|
举例 |
Reconnected RHVM { "uuid":"96bd9627-caf0-436e-aad1-885fe62ec274", "name":"13", "ip address":"192.168.25.3", "port number":"443", "vlan pool":"null", "connect status":"false", "certificate name":"null", "smooth status":"init", "reverse status":"init" }. |
|
日志说明 |
用户进行了重新连接RHVM的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · Unknown error code：未知错误 · The controller is not the active leader：该设备不是当前Leader控制组件 · Server processing error：服务器处理失败 · The specified RedHat VM does not exist：指定的RHVM不存在 · The controller failed to connect to the RHVM. The account is locked or disabled：控制组件连接RHVM失败，账户被锁住或禁用。 · The controller failed to connect to the RHVM. The account failed to pass authentication：控制组件连接RHVM失败，账户认证失败 · The controller failed to connect to the RHVM：控制组件连接RHVM失败 · You have no privilege to perform this operation：用户无权限执行此操作 · You cannot manually connect to the RHVM server, because it is isolated：当RHVM被隔离时，不允许进行手动连接操作。 |
|
关键字 |
CREATE_LOGICAL_NETWORK_OP |
|
日志内容 |
Created logical network $1. |
|
参数解释 |
$1：逻辑网络参数体 |
|
举例 |
Created logical network { "uuid":"da51f7ee-8d3f-4b62-8759-5ab93603f42b", "name":"default|zjtnetwork|123", "rhvmId":"760c2dd3-8512-48f4-bbce-862b1319923e", "rhvmName":"rhvm", "vlanType":"VLAN", "vlanRange":"123", "dcName":"Default", "vnetworkID":"4d8091b6-2104-4757-a9d7-7436ac754b58", "vnetworkName":"zjtnetwork" }. |
|
日志说明 |
用户进行了创建逻辑网络的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该设备不是当前Leader控制组件 · The request is invalid：传入的JSON串错误 · Invalid parameter：参数不合法 · Invalid UUID：无效的UUID · The specified RedHat VM does not exist：指定的RHVM不存在 · Cannot create the logical network, because the RHVM is disconnected：RHVM连接状态异常，不允许创建 · The specified vNetwork does not exist：指定的虚拟链路层网络不存在 · Illegal data center name：数据中心名称不合法 · The data center does not exist：RHVM Data Center不存在 · Invalid VLAN type：无效的VLAN类型 · The specified VLAN ID in the VLAN pool has been allocated：指定的VLAN池内资源已被分配 · Please configure a VLAN ID for the logical network because the RedHat VM bound to the network is not configured with a VLAN pool：当RHVM未分配VLAN池时，逻辑网络需手动配置VLAN ID · No VLAN ID is available in the VLAN pool：VLAN池中无可分配的VLAN ID · The VLAN ID must be an integer in the range of 1 to 4094：VLAN ID的取值范围必须为1-4094的整数 · The logical network name cannot exceed 256 characters or be all spaces：逻辑网络名称最长256个字符且不能全为空格 · The logical network name already exists：指定的逻辑网络已存在 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_LOGICAL_NETWORK_OP |
|
日志内容 |
Deleted logical network $1. |
|
参数解释 |
$1：逻辑网络参数体 |
|
举例 |
Deleted logical network { "uuid":"da51f7ee-8d3f-4b62-8759-5ab93603f42b", "name":"default|zjtnetwork|123", "rhvmId":"760c2dd3-8512-48f4-bbce-862b1319923e", "rhvmName":"rhvm", "vlanType":"VLAN", "vlanRange":"123", "dcName":"Default", "vnetworkID":"4d8091b6-2104-4757-a9d7-7436ac754b58", "vnetworkName":"zjtnetwork", }. |
|
日志说明 |
用户进行了删除逻辑网络的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该设备不是当前Leader控制组件 · The specified logical network does not exist：指定的逻辑网络不存在 · Cannot delete the logical network, because it has VMs：逻辑网络下存在VM，不允许删除 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
AUDIT_RHVM_OP |
|
日志内容 |
Audited data for RHVM: $1. |
|
参数解释 |
$1：RHVM名称 |
|
举例 |
Audited data for RHVM: RHVM. |
|
日志说明 |
用户进行了RHVM的差异发现的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置恢复未完成 · The controller is not the active leader：该设备不是当前Leader控制组件 · The specified RedHat VM does not exist：指定的RHVM不存在 · The connection state of the RHVM is abnormal：指定的RHVM连接状态异常 · The system is auditing or synchronizing data for the RHVM. Please try again later：指定的RHVM正在进行差异发现或差异修复，请稍后再试 · The system is detecting or incorporating data on the RHVM. Please try again later：指定的RHVM正在进行数据发现或数据纳管，请稍后再试 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
SYNC_RHVM_OP |
|
日志内容 |
Synchronized data for RHVM: $1. |
|
参数解释 |
$1：RHVM名称 |
|
举例 |
Synchronized data for RHVM: RHVM. |
|
日志说明 |
用户进行了RHVM的差异修复的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置恢复未完成 · The controller is not the active leader：该设备不是当前Leader控制组件 · The specified RedHat VM does not exist：指定的RHVM不存在 · The connection state of the RHVM is abnormal：指定的RHVM连接状态异常 · The system is auditing or synchronizing data for the RHVM. Please try again later：指定的RHVM正在进行差异发现或差异修复，请稍后再试 · The system is detecting or incorporating data on the RHVM. Please try again later：指定的RHVM正在进行数据发现或数据纳管，请稍后再试 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DISCOVERY_RHVM_OP |
|
日志内容 |
Detected data on RHVM: $1. |
|
参数解释 |
$1：RHVM名称 |
|
举例 |
Detected data on RHVM: RHVM. |
|
日志说明 |
用户进行了RHVM的数据发现的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置恢复未完成 · The controller is not the active leader：该设备不是当前Leader控制组件 · The specified RedHat VM does not exist：指定的RHVM不存在 · The connection state of the RHVM is abnormal：指定的RHVM连接状态异常 · The system is auditing or synchronizing data for the RHVM. Please try again later：指定的RHVM正在进行差异发现或差异修复，请稍后再试 · The system is detecting or incorporating data on the RHVM. Please try again later：指定的RHVM正在进行数据发现或数据纳管，请稍后再试 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
REVERSE_SYNC_RHVM_OP |
|
日志内容 |
Pulled and incorporated data from RHVM: $1. |
|
参数解释 |
$1：RHVM名称 |
|
举例 |
Pulled and incorporated data from RHVM: RHVM. |
|
日志说明 |
用户进行了RHVM的反向纳管的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置恢复未完成 · The controller is not the active leader：该设备不是当前Leader控制组件 · The specified RedHat VM does not exist：指定的RHVM不存在 · The connection state of the RHVM is abnormal：指定的RHVM连接状态异常 · The system is auditing or synchronizing data for the RHVM. Please try again later：指定的RHVM正在进行差异发现或差异修复，请稍后再试 · The system is detecting or incorporating data on the RHVM. Please try again later：指定的RHVM正在进行数据发现或数据纳管，请稍后再试 · Invalid parameter：参数不合法 · The data to incorporate is inconsistent with the data discovered：数据纳管与数据发现内容不一致 · Data incorporation failed. Make sure data detection has been performed and new configuration exists：反向纳管失败，确保已执行数据发现并存在新配置 · Please specify a vNetwork：请指定一个虚拟链路层网络 · The specified vNetwork does not exist：指定的虚拟链路层网络不存在 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_RHVM_SMOOTH_SETTING_OP |
|
日志内容 |
Updated auto audit and sync settings for RHVMs: audit interval:$1 minutes, auto audit state:$2, auto sync state:$3, audit schedule:$4, Schedule:{ "months":$5, "days of week":$6, "days of month":$7, "hh":$8, "mm":$9, "ss":$10 }. |
|
参数解释 |
$1：对账周期 $2：自动对账开关 $3：自动修复开关 $4：对账模式 $5：每月 $6：每周 $7：每天 $8：时 $9：分 $10：秒 |
|
举例 |
Updated auto audit and sync settings for RHVMs: audit interval:null minutes, auto audit state:true, auto sync state:OFF, audit schedule:TIMING, Schedule:{ "months":"*", "days of week":"?", "days of month":"*", "hh":"19", "mm":"40", "ss":"0" }. |
|
日志说明 |
用户进行了修改自动对账&修复配置参数的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置恢复未完成 · The controller is not the active leader：该设备不是当前Leader控制组件 · The request is invalid：传入的JSON串错误 · The value of the auto sync interval must be an integer in the range of 60 to 10080：自动同步周期必须为60～10080的整数 · Invalid auto smooth setting：无效的auto_smooth_setting · Invalid sync parameters：无效的自动修复参数 · You have no privilege to perform this operation：用户无权限执行此操作 · Invalid audit schedule：无效的对账模式 · When the audit schedule is interval-based, you must specify the audit interval：当对账模式为周期对账时，对账间隔不能为空 · Please configure Cron expression parameters：Cron表达式参数不能为空 · Invalid Cron expression parameters：无效的Cron表达式参数 |
|
关键字 |
CREATE_OPENSTACK_OP |
|
日志内容 |
Created OpenStack-based cloud platform $1. |
|
参数解释 |
$1：OpenStack参数体 |
|
举例 |
Created OpenStack-based cloud platform { "uuid":"17be5f2d-cd3a-4799-b828-bc5f925e958c", "name":"op1", "vni range list":"[1-2]", "data sync status":"init", "controller node list":"[]", "default openstack":"false", "openstack config":"{ "network overlay mode":"true", "ip mac binding":"true", "dhcp lease time":"365", "dhcp v6 preferred time":"0", "dhcp v6 valid time":"0", "network force flat":"true", "directly external suffix":"null", "generate vrf":"false", "enableMultiSeg":"false", "tenantGwName":"null", "directly external":"ANY", "emptyRuleAction":"deny", "tenantGwSelectionStrategy":"match_first", "network Node access strategy":"NO_ACCESS", "dhcp service proxy":"false", }" }. |
|
日志说明 |
用户进行了创建OpenStack的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置恢复未完成 · The controller is not the active leader：该设备不是当前Leader控制组件 · The request is invalid：传入的JSON串错误 · Please specify a VNI range for the cloud platform：OpenStack的VNI范围不能为空 · The start number of a VNI range cannot be greater than the end number：OpenStack的VNI范围起始值VNI不能大于其结束值 · The UUID already exists：该UUID已存在 · Invalid cloud platform name：无效的OpenStack名称 · Invalid tenant name：无效的租户名称 · Invalid username：无效的用户名称 · Invalid password：无效的用户密码 · The port number must be an integer in the range of 1 to 65535：端口号必须为1~65535的整数 · Invalid URL type：无效的URL类型 · Invalid certificate version：无效的认证版本 · You can specify a domain name only when the certificate version is set to V3：认证版本为V3时，才能配置域名 · Invalid domain name：无效的域名 · The cloud platform name already exists：该OpenStack名称已存在 · The VNI range conflicts with a VNI range on another OpenStack-based cloud platform：OpenStack的VNI范围与其他OpenStack的VNI范围冲突 · Each OpenStack-based cloud platform must have a unique IP address：批量创建的OpenStack的IP地址存在重复 · Each OpenStack-based cloud platform must have a unique name：批量创建的OpenStack的名称存在重复 · Each OpenStack-based cloud platform must have a unique UUID：批量创建的OpenStack的UUID存在重复 · When the certificate version is V2, the region cannot be configured：认证版本为V2时，不允许配置区域 · The IP address of the controller node is invalid：无效的控制节点IP地址 · The IP address of the controller node already exists：控制节点IP地址已存在 · The IP address of the controller node cannot be duplicated：存在重复的控制节点的IP地址 · Invalid region：无效的区域 · Invalid keystone URL：无效的Keystone URL · When the communication mode is Keystone authentication, please specify a Keystone URL for the cloud platform：当通信方式为Keystone认证时，OpenStack的Keystone URL不能为空 · When the communication mode is WebSocket, the username field is not supported：当通信方式为WebSocket时，不支持配置用户名 · When the communication mode is WebSocket, the password field is not supported：当通信方式为WebSocket时，不支持配置密码 · When the communication mode is WebSocket, the tenant field is not supported：当通信方式为WebSocket时，不支持配置租户 · When the communication mode is WebSocket, the certificate version field is not supported：当通信方式为WebSocket时，不支持配置认证版本 · When the communication mode is WebSocket, the domain field is not supported：当通信方式为WebSocket时，不支持配置域名 · When the communication mode is WebSocket, the URL type field is not supported：当通信方式为WebSocket时，不支持配置URL类型 · When the communication mode is WebSocket, the Keystone URL field is not supported：当通信方式为WebSocket时，不支持配置Keystone URL · When the communication mode is WebSocket, the northbound link state status field is not supported：当通信方式为WebSocket时，不支持配置连接状态 · When the communication mode is WebSocket, the region field is not supported：当通信方式为WebSocket时，不支持配置区域 · Please specify a valid value for the keystone auth parameter：无效的keystone auth · The OpenStack-based cloud platform cannot have the same region and Keystone URL as any other OpenStack-based cloud platform：OpenStack的区域和Keystone URL不能同时和其他OpenStack相同 · You have no privilege to perform this operation：用户无权限执行此操作 · Invalid empty rule action for the security policy：无效的安全策略的空规则行为 · Invalid external network configuration：无效的外部网络配置 · Invalid tenant border gateway policy：无效的租户出口网关策略 · When the value of the tenant border gateway policy is not the border gateway name, the border gateway name must be empty：当租户出口网关策略不为出口网关名称时，出口网关名称必须为空 · Invalid border gateway name：无效的出口网关名称 · Invalid vRouter name suffix：无效的虚拟路由器后缀 · The DHCP lease duration must be an integer in the range of 0 to 365：DHCP租约时长取值范围必须为0~365的整数 · DHCPv6 valid lifetime is beyond the value range：DHCPv6有效生命期值超出了范围限制 · DHCPv6 preferred lifetime is beyond the value range：DHCPv6首选生命期值超出了范围限制 · The DHCPv6 preferred lifetime must be less than or equal to the DHCPv6 valid lifetime：DHCPv6首选生命期值需要小于等于DHCPv6有效生命期值 · If the DHCPv6 preferred lifetime is 0, the DHCPv6 valid lifetime must also be 0：DHCPv6首选生命期值为0时，DHCPv6有效生命期值必须为0 · Preconfiguring border gateways for external networks is mutually exclusive with forcibly converting external networks to flat networks：外网预配置出口网关与外网强制转换为Flat不能同时开启 |
|
关键字 |
UPDATE_OPENSTACK_OP |
|
日志内容 |
Updated OpenStack-based cloud platform $1. |
|
参数解释 |
$1：OpenStack的参数体 |
|
举例 |
Updated OpenStack-based cloud platform { "uuid":"17be5f2d-cd3a-4799-b828-bc5f925e958c", "name":"op1", "vni range list":"[1-2]", "data sync status":"init", "controller node list":"[]", "default openstack":"false", "openstack config":"{ "network overlay mode":"false", "ip mac binding":"true", "dhcp lease time":"365", "dhcp v6 preferred time":"0", "dhcp v6 valid time":"0", "network force flat":"true", "directly external suffix":"null", "generate vrf":"false", "enableMultiSeg":"false", "tenantGwName":"null", "directly external":"ANY", "emptyRuleAction":"deny", "tenantGwSelectionStrategy":"match_first", "network Node access strategy":"NO_ACCESS", "dhcp service proxy":"false", }" }. |
|
日志说明 |
用户进行了修改OpenStack的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置恢复未完成 · The controller is not the active leader：该设备不是当前Leader控制组件 · The request is invalid：传入的JSON串错误 · The specified OpenStack-based cloud platform does not exist：指定的OpenStack不存在 · Please specify a VNI range for the cloud platform：OpenStack的VNI范围不能为空 · The start number of a VNI range cannot be greater than the end number：OpenStack的VNI范围起始值VNI不能大于其结束值 · The port number must be an integer in the range of 1 to 65535：端口号必须为1~65535的整数 · Invalid tenant name：无效的租户名称 · Invalid username：无效的用户名称 · Invalid password：无效的用户密码 · Invalid certificate version：无效的认证版本 · You can specify a domain name only when the certificate version is set to V3：认证版本为V3时，才能配置域名 · Invalid domain name：无效的域名 · Invalid URL type：无效的URL类型 · The VNI range conflicts with a VNI range on another OpenStack-based cloud platform：OpenStack的VNI范围与其他OpenStack的VNI范围冲突 · Cannot edit the VNI range. The VNI range is being used by DHCP vPorts：缩减的VNI范围正在被DHCP虚拟端口使用，不允许修改 · The IP address of the controller node is invalid：无效的控制节点IP地址 · The IP address of the controller node already exists：控制节点IP地址已存在 · The IP address of the controller node cannot be duplicated：存在重复的控制节点的IP地址 · When the communication mode is Keystone authentication, please specify a Keystone URL for the cloud platform：当通信方式为Keystone认证时，OpenStack的Keystone URL不能为空 · When the communication mode is WebSocket, the username field is not supported：当通信方式为WebSocket时，不支持配置用户名 · When the communication mode is WebSocket, the password field is not supported：当通信方式为WebSocket时，不支持配置密码 · When the communication mode is WebSocket, the tenant field is not supported：当通信方式为WebSocket时，不支持配置租户 · When the communication mode is WebSocket, the certificate version field is not supported：当通信方式为WebSocket时，不支持配置认证版本 · When the communication mode is WebSocket, the domain field is not supported：当通信方式为WebSocket时，不支持配置域名 · When the communication mode is WebSocket, the URL type field is not supported：当通信方式为WebSocket时，不支持配置URL类型 · When the communication mode is WebSocket, the Keystone URL field is not supported：当通信方式为WebSocket时，不支持配置Keystone URL · When the communication mode is WebSocket, the northbound link state status field is not supported：当通信方式为WebSocket时，不支持配置连接状态 · When the communication mode is WebSocket, the region field is not supported：当通信方式为WebSocket时，不支持配置区域 · You have no privilege to perform this operation：用户无权限执行此操作 · Invalid empty rule action for the security policy：无效的安全策略的空规则行为 · Invalid external network configuration：无效的外部网络配置 · Invalid tenant border gateway policy：无效的租户出口网关策略 · When the value of the tenant border gateway policy is not the border gateway name, the border gateway name must be empty：当租户出口网关策略不为出口网关名称时，出口网关名称必须为空 · Invalid border gateway name：无效的出口网关名称 · Invalid vRouter name suffix：无效的虚拟路由器后缀 · The DHCP lease duration must be an integer in the range of 0 to 365：DHCP租约时长取值范围必须为0~365的整数 · DHCPv6 valid lifetime is beyond the value range：DHCPv6有效生命期值超出了范围限制 · DHCPv6 preferred lifetime is beyond the value range：DHCPv6首选生命期值超出了范围限制 · The DHCPv6 preferred lifetime must be less than or equal to the DHCPv6 valid lifetime：DHCPv6首选生命期值需要小于等于DHCPv6有效生命期值 · If the DHCPv6 preferred lifetime is 0, the DHCPv6 valid lifetime must also be 0：DHCPv6首选生命期值为0时，DHCPv6有效生命期值必须为0 · Preconfiguring border gateways for external networks is mutually exclusive with forcibly converting external networks to flat networks：外网预配置出口网关与外网强制转换为Flat不能同时开启 |
|
关键字 |
DELETE_OPENSTACK_OP |
|
日志内容 |
Deleted OpenStack-based cloud platform $1. |
|
参数解释 |
$1：OpenStack的参数体 |
|
举例 |
Deleted OpenStack-based cloud platform { "uuid":"851d14bb-0938-456e-a076-8aa931330675", "name":"Openstack", "vni range list":"[600-999]", "data sync status":"consistent" "controller node list":"[ControllerNode{ip='192.168.132.221', controllerStatus='connected', openstackUuid='851d14bb-0938-456e-a076-8aa931330675'}]" }. |
|
日志说明 |
用户进行了删除OpenStack的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置恢复未完成 · The controller is not the active leader：该设备不是当前Leader控制组件 · Invalid UUID：无效的UUID · The specified OpenStack-based cloud platform does not exist：指定的OpenStack不存在 · Cannot delete the platform. The platform contains DHCP vPorts：该OpenStack下存在DHCP虚拟端口，不允许删除 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
SYNC_OPENSTACK_OP |
|
日志内容 |
Synchronized data of OpenStack-based cloud platform: $1. |
|
参数解释 |
$1：OpenStack名称 |
|
举例 |
Synchronized data of OpenStack-based cloud platform: OpenStack1. |
|
日志说明 |
用户进行了OpenStack的差异修复操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置恢复未完成 · The controller is not the active leader：该设备不是当前Leader控制组件 · The specified OpenStack-based cloud platform does not exist：指定的OpenStack不存在 · Cannot start an audit or repair. The northbound links of the platform are abnormal：OpenStack连接状态异常，不允许执行差异发现或差异修复操作 · Cannot repair the cloud platform. The platform is being audited or repaired：OpenStack在差异发现或修复状态下，不允许执行差异修复操作 · No controller node is available on the OpenStack-based cloud platform. The OpenStack-based cloud platform cannot start an audit or repair：OpenStack下无可用的控制节点，对应的OpenStack 不允许进行差异发现或差异修复 · You have no privilege to perform this operation：用户无权限执行此操作 · You cannot repair configuration differences on the OpenStack cloud platform, because the DHCP agent feature is not enabled for the platform：指定的OpenStack未开启DHCP服务代理开关，不支持差异修复 |
|
关键字 |
UPDATE_OPENSTACK_RECONCILIATION_SETTING_OP |
|
日志内容 |
Updated auto audit and sync settings for OpenStack-based cloud platforms: audit interval:$1 minutes, auto audit state:$2, auto sync state:$3, audit schedule:$4, Schedule:{ "months":$5, "days of week":$6, "days of month":$7, "hh":$8, "mm":$9, "ss":$10 }. |
|
参数解释 |
$1：对账周期 $2：自动对账开关 $3：自动修复开关 $4：对账模式 $5：每月 $6：每周 $7：每天 $8：时 $9：分 $10：秒 |
|
举例 |
Updated auto audit and sync settings for OpenStack-based cloud platforms: audit interval:null minutes, auto audit state:true, auto sync state:true, audit schedule:TIMING, Schedule:{ "months":"*", "days of week":"?", "days of month":"*", "hh":"19", "mm":"40", "ss":"0" }. |
|
日志说明 |
用户进行了修改自动对账&修复配置参数的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置恢复未完成 · The controller is not the active leader：该设备不是当前Leader控制组件 · The request is invalid：传入的JSON串错误 · The reconciliation interval must be an integer in the range of 60 to 10080：对账周期必须为60～10080的整数 · Please specify a valid value for the auto reconciliation parameter：无效的auto reconciliation · Please specify a valid value for the auto smooth parameter：无效的auto smooth · You have no privilege to perform this operation：用户无权限执行此操作 · Invalid audit schedule：无效的对账模式 · When the audit schedule is interval-based, you must specify the audit interval：当对账模式为周期对账时，对账间隔不能为空 · Please configure Cron expression parameters：Cron表达式参数不能为空 · Invalid Cron expression parameters：无效的Cron表达式参数 |
|
关键字 |
AUDIT_OPENSTACK_OP |
|
日志内容 |
Audited data of OpenStack-based cloud platform: $1. |
|
参数解释 |
$1：OpenStack名称 |
|
举例 |
Audited data of OpenStack-based cloud platform: OpenStack. |
|
日志说明 |
用户进行了OpenStack的差异审计操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置恢复未完成 · The controller is not the active leader：该设备不是当前Leader控制组件 · The specified OpenStack-based cloud platform does not exist：指定的OpenStack不存在 · Cannot start an audit or repair. The northbound links of the platform are abnormal：OpenStack连接状态异常，不允许执行差异发现或差异修复操作 · Cannot start audit on a cloud platform. The cloud platform is being audited or repaired：OpenStack在差异发现或修复状态下，不允许执行差异发现操作 · No controller node is available on the OpenStack-based cloud platform. The OpenStack-based cloud platform cannot start an audit or repair：OpenStack下无可用的控制节点，对应的OpenStack 不允许进行差异发现或差异修复 · You have no privilege to perform this operation：用户无权限执行此操作 · You cannot audit configuration differences on the OpenStack cloud platform, because the DHCP agent feature is not enabled for the platform：指定的OpenStack未开启DHCP服务代理开关，不支持差异发现 |
|
关键字 |
CREATE_PLUGIN_AGENT_OP |
|
日志内容 |
Created agent $1. |
|
参数解释 |
$1：Agent参数体 |
|
举例 |
Created agent { "id":"a12159d8-3817-4e9b-9aa7-6c81c3ee2e12", "host":"network", "binary":"neutron-dhcp-agent", "alive":"false", "agentType":"DHCP agent", "cloudRegionName":"default" } }. |
|
日志说明 |
用户进行了创建Agent的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · Invalid host：无效的主机名称 · Invalid binary value：无效的binary · Invalid agent type：无效的Agent类型 · Invalid network segment physical network name：无效的网络分段物理网络名称 · Invalid device mapping key：无效的设备配置项参数的键 · Invalid device mapping value：无效的设备配置项参数的值 · Invalid bridge mapping key：无效的bridge配置项参数的键 · Invalid bridge mapping value：无效的bridge配置项参数的值 · Invalid icontrol endpoint：无效的icontrol endpoints配置项 · Invalid device name：无效的设备名称 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The specified OpenStack-based cloud platform does not exist：指定的云平台不存在 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 · All OpenStack-based cloud platforms have been isolated：所有的云平台已被隔离 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
SYNC_PLUGIN_AGENT_OP |
|
日志内容 |
Synchronized agents $1. |
|
参数解释 |
$1：Agent参数体 |
|
举例 |
Synchronized agents { "id":"e1269b89-5138-4e8c-bc32-66f1a12fd9cd", "host":"network", "binary":"neutron-metadata-agent", "alive":"false", "agentType":"Metadata agent", "cloudRegionName":"default" } }. |
|
日志说明 |
用户进行了同步Agent的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · Invalid host：无效的主机名称 · Invalid binary value：无效的binary · Invalid agent type：无效的Agent类型 · Invalid network segment physical network name：无效的网络分段物理网络名称 · Invalid device mapping key：无效的设备配置项参数的键 · Invalid device mapping value：无效的设备配置项参数的值 · Invalid bridge mapping key：无效的bridge配置项参数的键 · Invalid bridge mapping value：无效的bridge配置项参数的值 · Invalid icontrol endpoint：无效的icontrol endpoints配置项 · Invalid device name：无效的设备名称 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The specified OpenStack-based cloud platform does not exist：指定的云平台不存在 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 · Make sure each agent has a unique UUID：批量同步的Agent的UUID存在重复 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
UPDATE_PLUGIN_AGENT_OP |
|
日志内容 |
Updated agent $1. |
|
参数解释 |
$1：Agent参数体 |
|
举例 |
Updated agent { "id":"a12159d8-3817-4e9b-9aa7-6c81c3ee2e12", "host":"network", "binary":"neutron-dhcp-agent", "alive":"false", "agentType":"DHCP agent", "cloudRegionName":"default" } }. |
|
日志说明 |
用户进行了修改Agent的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · Invalid host：无效的主机名称 · Invalid binary value：无效的binary · Invalid agent type：无效的Agent类型 · Invalid network segment physical network name：无效的网络分段物理网络名称 · Invalid device mapping key：无效的设备配置项参数的键 · Invalid device mapping value：无效的设备配置项参数的值 · Invalid bridge mapping key：无效的bridge配置项参数的键 · Invalid bridge mapping value：无效的bridge配置项参数的值 · Invalid icontrol endpoint：无效的icontrol endpoints配置项 · Invalid device name：无效的设备名称 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The specified agent does not exist：指定的Agent不存在 · The specified OpenStack-based cloud platform does not exist：指定的云平台不存在 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 · All OpenStack-based cloud platforms have been isolated：所有的云平台已被隔离 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
DELETE_PLUGIN_AGENT_OP |
|
日志内容 |
Deleted agent $1. |
|
参数解释 |
$1：Agent参数体 |
|
举例 |
Deleted agent { "id":"a12159d8-3817-4e9b-9aa7-6c81c3ee2e12", "host":"network", "binary":"neutron-dhcp-agent", "alive":"false", "agentType":"DHCP agent", "cloudRegionName":"default" } }. |
|
日志说明 |
用户进行了删除Agent的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The specified OpenStack-based cloud platform does not exist：指定的云平台不存在 · The specified agent does not exist：指定的Agent不存在 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 · All OpenStack-based cloud platforms have been isolated：所有的云平台已被隔离 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
CREATE_ROUTER_OP |
|
日志内容 |
Created vRouter $1. |
|
参数解释 |
$1：虚拟路由器的参数体 |
|
举例 |
Created vRouter { "id":"56a937a9-55ce-48c1-866b-0be6386f16ec", "admin_state_up":"vrouter", "external_gateway_info":"{ "network_id":"10236dae-b97a-49b7-89ed-c225baa39d4e", "enable_snat":"true", "external_fixed_ips":"[FixedIpDto { "ip address":"26.3.3.10", "subnet id":"e2d81808-6b61-4ef2-85c6-65839489172b", }]" }", "name":"vrouter", "routes":"[{ "destination":"23.3.3.3/32", "nexthop":"12.3.3.31" }]", "tenant_id":"2b2151a2-f111-40f0-a0ea-61a76879e972", "tenant_name":"admin", "gw_port_id":"null", "tags":"[]", "cloud_region_name":"openstack", "subnets":"null" }. |
|
日志说明 |
用户进行了创建路由器的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · Invalid tenant ID：无效的租户ID · The router ID is already used：路由器ID已经存在 · vRouters created in bulk cannot use the same ID：批量创建的虚拟路由器的ID存在重复 · The router is required：未指定虚拟路由器 · The is_bind_gw field is a read-only field：is_bind_gw为只读字段 · The segment ID number is already used：Segment ID number已经被使用 · The segment ID is out of range：Segment ID超出范围 · Invalid routing table：无效的路由表 · The VDS doesn't exist：VDS不存在 · The VPN instance name is already used：VPN实例名称已经被使用 · The AS number is required：未指定AS号 · The value for the maximum number of ECMP routes is invalid：最大等价路由条目不可用 · Invalid summary route network：聚合路由网段不可用 · The IPv4 address of the peer is required：未指定对等体的IPv4地址 · Invalid CIDR：无效的CIDR · The CIDR overlaps with another CIDR：CIDR配置中有重叠项 · The AS number of the peer is invalid：无效的对等体AS号 · The vRouter cannot be configured with the same summary route network：不允许配置重复的聚合路由网段 · The vRouters using the public VRF cannot be bound to the same service device group：使用公网VRF的虚拟路由器不能绑定同一个服务设备组 · The specified device doesn't exist：指定的设备不存在 · The device ID and the device name do not match：设备的ID和名称不匹配 · The BGP peer already exists：存在冲突的BGP对等体 · The vRouter name cannot exceed 255 characters：虚拟路由器名称最长255个字符 · The VPN name cannot exceed 31 bytes：VPN名称最长31个字节 · The specified tenant doesn't exist：指定的租户不存在 · Failed to add the vRouter because the number of vRouters has reached the limit：虚拟路由器的数量已达上限 · The specified tenant doesn't bind VDS：指定的租户没有绑定VDS · The VDS of the vRouter is different than the tenant：虚拟路由器与租户的VDS不一致 · The external network bound to the vRouter does not have segments. The vRouter can be bound only to one IPv4 subnet：指定的外部网络未配置Segment，只能绑定一个IPv4子网 · The border gateways to the IPv4 and IPv6 external subnets are located on the same interface. You must configure them with the same segment ID：IPv4外网子网和IPv6外网子网的出口网关相同时，Segment ID必须相同 · The external network egress IP has been bound to another vRouter. To bind the current vRouter to the external network egress IP, you must make sure the current vRouter has exactly the same external subnet bindings as that vRouter：虚拟路由器绑定多个外网子网，且多个虚拟路由器共享外网IP时，必须同时共享所有外网IP · Unknown error：未知错误 · The address pool does not exist or no IP addresses are available in the address pool：绑定服务资源失败，指定的地址池不存在，或该地址池内没有足够的IP地址 · The segment or border gateway already has a priority：不允许重复配置网络分段或者出口网关的优先级 · If a vRouter is bound to both a gateway resource and a network segment, you can configure a priority for either the gateway resource or the network segment, but not both：不能同时配置网关资源和网络分段的优先级 · If service resources have been bound to a virtual router, the border gateways bound to the virtual router must have different priorities：虚拟路由器已绑定服务资源时，两个出口网关的优先级不允许相同 · Invalid tags：无效的tags · The priority is out of range：tags优先级超出范围 · The specified segment doesn't exist：指定的网络分段不存在 · The specified gateway doesn't exist：指定的网关资源不存在 · Cannot configure a priority for the gateway resource. For more information, see the online help：该网关资源不支持配置优先级，具体情况请查看联机帮助 · Failed to bind the vRouter to an external network because the specified network is not an indirectly connected external network：虚拟路由器无法与该外网绑定，因为选定的网络不是共享型外网 · Cannot disable east-west traffic offload in network cloud scenarios：网络云场景下不允许关闭东西向流量卸载开关 · The public network VPN cannot be configured in the weak control scenario：弱控场景下不支持配置公网VPN · You have no privilege to perform this operation：用户无权限执行此操作 · A vRouter cannot be bound to internal network vPorts：虚拟路由器仅支持绑定外网虚拟端口 · Cannot bind the external network vPort to the vRouter, because the vRouter has been bound to the external network to which the vPort belongs：虚拟路由器已绑定外部网络，不允许绑定该外网虚拟端口 · A vRouter cannot be bound to multiple IPv6 external network vPorts in the same network：虚拟路由器绑定多个IPv6外网虚拟端口时，这些端口所属的外部网络不能相同 · Cannot bind the external network to the vRouter, because the vRouter has been bound to a vPort in the external network：虚拟路由器已绑定外网虚拟端口，不允许再绑定该端口所属的外部网络 · You cannot bind VLAN external networks to a vRouter after you bind a flat external network to the vRouter. Only one flat external network can be bound to a vRouter：一个虚拟路由器只允许绑定一个Flat类型外网，且不能绑定VLAN类型外网 · A VPN instance name cannot start with 'external_vpn' or 'management_vpn'：VPN实例名称不能以“external_vpn”或者"management_vpn"为前缀 · The RT generated based on the segment ID of the vRouter conflicts with the import RT of a Layer 2 DC interconnect：虚拟路由器Segment ID生成的RT与数据中心二层互联的引入RT冲突 · The RT generated based on the segment ID of the vRouter conflicts with the export RT of a Layer 2 DC interconnect：虚拟路由器Segment ID生成的RT与数据中心二层互联的引出RT冲突 · The RT reserved for the vRouter link conflicts with the import RT of a Layer 2 DC interconnect：系统预留的虚拟路由器连接的RT与数据中心二层互联的引入RT冲突 · The RT reserved for the vRouter link conflicts with the export RT of a Layer 2 DC interconnect associated with the local or remote vRouter：系统预留的虚拟路由器连接的RT与数据中心二层互联的引出RT冲突 · The RT generated based on the segment ID of the vRouter conflicts with the import RT of a Layer 3 DC interconnect：虚拟路由器Segment ID生成的RT与数据中心三层互联的引入RT冲突 · The RT generated based on the segment ID of the vRouter conflicts with the export RT of a Layer 3 DC interconnect：虚拟路由器Segment ID生成的RT与数据中心三层互联的引出RT冲突 · The RT reserved for the vRouter link conflicts with the import RT of a Layer 3 DC interconnect：系统预留的虚拟路由器连接的RT与数据中心三层互联的引入RT冲突 · The RT reserved for the vRouter link conflicts with the export RT of a Layer 3 DC interconnect：系统预留的虚拟路由器连接的RT与数据中心三层互联的引出RT冲突 · Check the directly connected external networks and the border interfaces in the device group bound to this vRouter with the same segment ID. Make sure only one primary IPv4 address exists for each border interface：虚拟路由器下的独享型外网子网和该虚拟路由器绑定的设备组中的外网出口使用相同Segment ID时，最多只允许有一个主IP · vRouters do not support vPorts in flat external networks：虚拟路由器不支持绑定FLAT类型的外部网络中的虚拟端口 · The vRouter context or external network vPort context has been used in a service chain：指定的虚拟路由器或外部网络虚拟端口类型的流量特征组已被服务链使用 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · The segment ID cannot be identical to a VXLAN ID in a VXLAN pool or the VXLAN ID reserved for the automation template and the M-LAG system：Segment ID不能在VXLAN池范围内且不能和自动化模版、M-LAG系统的保留VXLAN ID重叠 · Please specify a peer IP address or network address：对等体IP地址/网段不能为空 · Invalid peer IP address or network address：对等体IP地址/网段无效 · Invalid source IP address：源IP地址无效 · Invalid IP version：IP版本无效 · Neighbor IP/network address must be of the same IP version as the source IP address：对等体IP地址/网段与源IP地址必须为相同IP版本 · Neighbor IP/network address and IP version are inconsistent：对等体IP地址/网段和IP版本不一致 · The peer IP address cannot be the same as the source IP address：对等体地址和源IP地址不能相同 · Please specify the device ID, device name, or both：设备ID和设备名称不能为空 · All OpenStack-based cloud platforms have been isolated：所有的云平台已被隔离 · No system VDS is specified：未指定系统虚拟分布式交换机 · The gateway list contains gateways that do not have members：出口网关列表中存在未配置成员的网关 · The network addresses of some neighbors overlap：BGP对等体中存在网段重叠 · The value for the create_loopback parameter cannot be true when no source IP address is specified：源IP地址为空时，不允许开启创建LoopBack口开关 · BGP neighbors with the same source IP address must be consistent in the value for the create_loopback parameter：相同源IP地址的BGP对等体的创建LoopBack口开关必须一致 · A transit vRouter cannot be bound to an internal subnet：虚拟路由器是TRANSIT类型时，不支持绑定内网子网 · A transit vRouter does not support aggregate CIDRs：虚拟路由器是TRANSIT类型时，不支持Aggregate CIDRs · A transit vRouter does not support CIDRs：虚拟路由器是TRANSIT类型时，不支持CIDRs · A normal vRouter does not support export RTs：虚拟路由器是NORMAL类型时，不支持引出RT · A normal vRouter does not support import RTs：虚拟路由器是NORMAL类型时，不支持引入RT · Invalid export target：无效的引出RT · Invalid import target：无效的引入RT · The vRouter type is invalid：无效的虚拟路由器类型 · The import RT %s of the vRouter conflicts with the RT of a Layer 2 DC interconnect：虚拟路由器配置的引入RT与数据中心二层互联的RT冲突 · The export RT %s of the vRouter conflicts with the RT of a Layer 2 DC interconnect：虚拟路由器配置的引出RT与数据中心二层互联的RT冲突 · The import RT %s of the vRouter conflicts with the RT of a Layer 3 DC interconnect：虚拟路由器配置的引入RT与数据中心三层互联的RT冲突 · The export RT %s of the vRouter conflicts with the RT of a Layer 3 DC interconnect：虚拟路由器配置的引出RT与数据中心三层互联的RT冲突 · The export RT on the vRouter conflicts with the RT on a vNetwork：虚拟路由器配置的引出RT与虚拟链路层网络的RT冲突 · The export RT of the vRouter conflicts with an RT reserved for fabric interconnects：虚拟路由器配置的引出RT与系统预留的Fabric互联RT冲突 · The export RT of the vRouter conflicts with an RT reserved for vRouter links：虚拟路由器配置的引出RT与系统预留的虚拟路由器连接的RT冲突 · The export RT of the vRouter conflicts with the RT of another vRouter：虚拟路由器配置的引出RT与其他虚拟路由器的RT冲突 · The import RT of the vRouter conflicts with an RT reserved for vRouter links：虚拟路由器配置的引入RT与系统预留的虚拟路由器连接的RT冲突 · The import RT of the vRouter conflicts with the RT of another vRouter：虚拟路由器配置的引入RT与其他虚拟路由器的RT冲突 · The import RT of the vRouter conflicts with the RT of a vNetwork：虚拟路由器配置的引入RT与虚拟链路层网络的RT冲突 · The import RT of the vRouter conflicts with an RT reserved for fabric interconnects：虚拟路由器配置的引入RT与系统预留的Fabric互联RT冲突 · When host route recursion is enabled, the next hop IP address cannot reside on an external network：当迭代主机路由开关开启时，下一跳IP地址不能属于外网网段 · You cannot enable ND direct route redistribution for a vRouter in the network cloud scenario：网络云场景下，不允许开启引入ND直连路由开关 · A vRouter and its attached external network must be bound to the same gateway：虚拟路由器的出口网关和外部网络的出口网关必须一致 · You cannot bind the external network to the vRouter, because the external network has been bound to a border gateway and the border gateway is not bound to the vRouter：不允许绑定配置了出口网关的外部网络，因为虚拟路由器未绑定出口网关 · The security external network feature is disabled. You cannot bind the vRouter to an external subnet with a VLAN-type segment, because the vRouter has been bound to a firewall configured with a security external network address pool：禁用安全外网时，该虚拟路由器已绑定的防火墙使用了安全外网，不能同时绑定Segment为VLAN类型的外网子网 · The security external network feature is disabled. You cannot bind the vRouter to an external network of the VLAN type, because the vRouter has been bound to a firewall configured with a security external network address pool：禁用安全外网时，该虚拟路由器已绑定的防火墙使用了安全外网，不能同时绑定VLAN类型的外部网络 · The internal or external subnets of the same vRouter cannot overlap：同一虚拟路由器内网或外网子网网段不能重叠 · You cannot enable the multicast network feature for any external transit vRouter：EXTERNALTRANSIT类型虚拟路由器不允许开启组播网络 · You cannot enable the multicast network feature for any external transit vRouter：EXTERNALTRANSIT类型虚拟路由器不允许开启组播网络 · You cannot bind the external transit vRouter to an external network that has no vPort-vRouter bindings：EXTERNALTRANSIT类型虚拟路由器不支持绑定未被虚拟路由器外网虚拟端口绑定的外部网络 · The external subnets cannot overlap：多数据中心外网网段信息中存在子网网段重叠 · You cannot bind the external transit vRouter to any external network referenced by OSPF：EXTERNALTRANSIT类型虚拟路由器不支持绑定被OSPF引用的外网 · You cannot bind the transit vRouter to any external network：TRANSIT类型虚拟路由器不支持绑定外网 · You cannot bind the external transit vRouter to any internal subnets：EXTERNALTRANSIT类型虚拟路由器不支持绑定内网子网 · The internal subnets cannot overlap：多数据中心内网网段信息中存在子网网段重叠 · Invalid multi-DC internal subnet information：无效的多数据中心内网网段信息 · You cannot bind an external transit vRouter to any external network enabled with the network segmentation feature：开启了网络分段的外网不允许绑定External Transit 类型VRouter · The vRouters bound to an external network must be of the same type：外网不允许被不同类型虚拟路由器绑定 · Invalid multi-DC external subnet information：无效的多数据中心外网网段信 · You cannot bind a vPort that meets the following requirements to the external transit vRouter:• The firewall status of the vPort is default.• The vPort's edge device to external network is border device：EXTERNALTRANSIT类型虚拟路由器不允许绑定防火墙开关为默认且虚拟路由器外网出口设备为边界设备的外网虚拟端口 · Internal subnets cannot overlap with any external subnet：多数据中心内网网段信息和多数据中心外网网段信息中存在子网网段重叠 · External transit vrouter cannot be bound to an external network has bound to another type vrouter：已绑定其他类型VRouter的外网不允许绑定External Transit 类型VRouter · You cannot bind any vPorts to an external transit vRouter if the vRouter is already in a centralized vRouter link and the peer vRouter is not enabled with firewall：EXTERNALTRANSIT类型虚拟路由器已绑定到集中式虚拟路由器连接，且对端防火墙关闭时，不允许绑定外部网络中的虚拟端口 · Overlapping items are not allowed in the information configuration of the external network segment of the multi data center of different transitvrouter corresponding to the same tenant virtual router in the VPC：同一个虚拟路由器与不同的EXTERNALTRANSIT类型虚拟路由器建立集中式虚拟路由器连接，EXTERNALTRANSIT类型虚拟路由器间的多数据中心外网网段信息存在子网网段重叠 · You cannot bind any vPorts to the external transit vRouter if the vRouter is already in a centralized vRouter link and the peer vRouter is not enabled with firewall：EXTERNALTRANSIT类型虚拟路由器，外网出口设备为边界设备时，不允许绑定外部网络中的虚拟端口 · You must specify a segment ID for the external transit vRouter：EXTERNALTRANSIT类型虚拟路由器的Segment ID不能为空 · You cannot disable firewall for the peer vRouter in the vRouter link if the external transit vRouter already has vPort bindings：EXTERNALTRANSIT类型虚拟路由器已绑定外部网络中的虚拟端口，对端防火墙不允许关闭 · The VPN instance name is invalid：无效的VPN实例名称 · Invalid inbound routing policy name：无效的入方向路由策略名称 · The external network has been bound to a vRouter that uses a different edge device placement mode than this vRouter. To bind to that network, first set the third-party firewall deployment mode to Off：边界设备对接第三方防火墙为开启状态（旁挂和直连）时，外部网络不能同时绑定外网出口设备为边界设备的虚拟路由器和外网出口设备为防火墙的虚拟路由器 · Invalid outbound routing policy name：无效的出方向路由策略名称 · You cannot bind the external network to the vRouter, because the external network is enabled with route reduction and bound to another vRouter configured with the same internal subnet as this vRouter：外部网络已开启路由精简且绑定的虚拟路由器存在相同网段的内网子网时，虚拟路由器不允许绑定该外部网络 · You cannot bind the external network vPort to the vRouter, because the external network is enabled with route reduction and bound to another vRouter configured with the same internal subnet as this vRouter：外部网络已开启路由精简且绑定的虚拟路由器存在相同网段的内网子网时，虚拟路由器不允许绑定该外网虚拟端口 · You cannot bind the internal subnet to the vRouter, because the vRouter-associated external network is enabled with route reduction, and the internal subnet has been specified for another vRouter bound to this external network：虚拟路由器已绑定开启路由精简的外部网络时，虚拟路由器不允许绑定与该外部网络所属的其他虚拟路由器网段相同的内网子网 · When you add a vRouter that has the same vSubnet bindings and external network binding as an existing vRouter, you can disable SNAT for the bound external network on either vRouter, but not both of them：绑定了相同子网网段、相同外部网络的虚拟路由器，不允许均关闭外网SNAT开关 · An MDC north-south vRouter link (with islocalAll set to false and isPeerAll set to true) and an MDC east-west vRouter link (with both islocalAll and isPeerAll set to false) are created on the tenant. Make sure the routes to an external subnet of the south-north vRouter link and a remote CIDR of the east-west vRouter link do not overlap：当相同租户同时创建MDC南北向业务（指定源）和东西向业务（指定源和目的）时，南北向的多数据中心外网网段与东西向的对端网段明细路由不能相同 · If the firewall service type specified for a vRouter is service leaf, you cannot enable the multicast network feature for the vRouter：当虚拟路由器绑定Service Leaf类型防火墙时，不允许开启组播网络 · The vRouter is bound to a gateway whose firewall deployment mode is off and method to deploy basic external connectivity settings is manual. You cannot bind the vRouter to an external network that does not have gateway bindings or has vPort-vRouter bindings without a gateway specified：当虚拟路由器绑定设备组防火墙接入模式为关闭且外网转发基础配置为手动预配置的出口网关时，不可同时绑定未指定出口网关的外部网络，或者未指定出口网关的已被虚拟路由器外网虚拟端口绑定的外部网络 · The vRouter is bound to a gateway whose firewall deployment mode is off and method to deploy basic external connectivity settings is manual. You cannot bind the vRouter to a vPort associated with an external network that has no gateway binding：当虚拟路由器绑定设备组防火墙接入模式为关闭且外网转发基础配置为手动预配置的出口网关时，不支持绑定未指定出口网关的的外部网络中的虚拟端口 · When you bind a vRouter to an external network that has no vPort bindings, the external network's subnets cannot overlap with the access subnet for the firewall associated with the vRouter：虚拟路由器绑定未被虚拟路由器外网虚拟端口绑定的外部网络时，该外网下的子网不能和防火墙接入网段存在重叠 · When you bind an internal subnet to the vRouter, the subnet cannot overlap with the access subnet for the firewall associated with the vRouter：虚拟路由器绑定内网子网时，该内网子网不能和防火墙接入网段存在重叠 · When you bind a vRouter to a directly-connected external network, the external network's subnets cannot overlap with the access subnet for the firewall associated with the vRouter：虚拟路由器绑定独享外网时，该外网下的子网不能和防火墙接入网段存在重叠 · When you bind a vRouter to an external vPort, the subnets of the external network associated with the vPort cannot overlap with the access subnet for the firewall associated with the vRouter：虚拟路由器绑定外部网络中的虚拟端口时，该外网下的子网不能和防火墙接入网段存在重叠 · If the following conditions exist, you cannot bind a vRouter to any external network that has no gateway binding: ¡ The edge device to external networks for the vRouter is firewall. ¡ firewall service type specified for the vRouter is service leaf. 当虚拟路由器的外网出口设备为防火墙且绑定Service Leaf类型防火墙时，不支持绑定未指定出口网关的外部网络 · If the following conditions exist, you cannot bind a vRouter to any external network that has no segment ID: ¡ The edge device to external networks for the vRouter is firewall. ¡ The firewall service type specified for the vRouter is service leaf. 当虚拟路由器的外网出口设备为防火墙且绑定Service Leaf类型防火墙时，不支持绑定未指定External Segment ID的外部网络 · If the following conditions exist, you can only bind a vRouter to any external network that has no vPort bindings and has a gateway whose firewall deployment mode is off: ¡ The edge device to external networks for the vRouter is firewall. ¡ The firewall service type specified for the vRouter is service leaf. 当虚拟路由器的外网出口设备为防火墙且绑定Service Leaf类型防火墙时，仅支持绑定设备组防火墙接入模式为关闭的出口网关的未被虚拟路由器外网虚拟端口绑定的外部网络 · If the following conditions exist, you cannot bind a vRouter to any external network that has a gateway whose method to deploy basic external connectivity settings is auto: ¡ The edge device to external networks for the vRouter is firewall. ¡ The firewall service type specified for the vRouter is service leaf. 当虚拟路由器的外网出口设备为防火墙且绑定Service Leaf类型防火墙时，不支持绑定出口网关外网转发基础配置为自动下发的外部网络 · If the following conditions exist, you cannot bind a vRouter to any external network that has a gateway whose firewall deployment mode is off: ¡ The edge device to external networks for the vRouter is firewall. ¡ The firewall service type specified for the vRouter is not service leaf. 当虚拟路由器的外网出口设备为防火墙且绑定非Service Leaf类型防火墙时，不支持绑定出口网关设备组防火墙接入模式为关闭的外部网络 · If the following conditions exist, you cannot bind an external vPort to the vRouter: ¡ You have enabled firewall for the external vPort. ¡ The external network bound to the vPort has no segment ID. ¡ The firewall service type specified for the vRouter is service leaf. 虚拟路由器绑定Service Leaf类型防火墙时，不支持绑定未指定External Segment ID的外部网络中防火墙开关开启的虚拟端口 · If the following conditions exist, you cannot bind an external vPort to the vRouter: ¡ You have enabled firewall for the external vPort. ¡ The external network bound to the vPort has no gateway binding. ¡ The firewall service type specified for the vRouter is service leaf. 虚拟路由器绑定Service Leaf类型防火墙时，不支持绑定未指定出口网关的外部网络中防火墙开关开启的虚拟端口 · If the following conditions exist, you can bind an external vPort to the vRouter: ¡ You have enabled firewall for the external vPort. ¡ The external network bound to the vPort has a gateway whose firewall deployment mode is off. ¡ The firewall service type specified for the vRouter is service leaf. 虚拟路由器绑定Service Leaf类型防火墙时，仅支持绑定设备组防火墙接入模式为关闭出口网关的外部网络中防火墙开关开启的虚拟端口 · If the following conditions exist, you cannot bind an external vPort to the vRouter: ¡ You have enabled firewall for the external vPort. ¡ The external network bound to the vPort has a gateway whose method to deploy basic external connectivity settings is auto. ¡ The firewall service type specified for the vRouter is service leaf. 虚拟路由器绑定Service Leaf类型防火墙时，不支持绑定外网转发基础配置为自动下发的出口网关的外部网络中防火墙开关开启的虚拟端口 · If the following conditions exist, you cannot bind an external vPort to the vRouter: ¡ You have enabled firewall for the external vPort. ¡ The firewall service type specified for the vRouter is service leaf. ¡ The vRouter is bound to a centralized vRouter link that is not enabled with firewall or route reduction. 虚拟路由器绑定Service Leaf类型防火墙，且该虚拟路由器已绑定两端防火墙关闭且路由精简开关关闭的集中式虚拟路由器连接时，不支持绑定外部网络中防火墙开关开启的虚拟端口 · If the following conditions exist, you cannot bind an external vPort to the vRouter: ¡ You have enabled firewall for the external vPort. ¡ The external network bound to the vPort has a gateway whose firewall deployment mode is off. ¡ The firewall service type specified for the vRouter is not service leaf. 虚拟路由器绑定非Service Leaf类型防火墙时，不支持绑定设备组防火墙接入模式为关闭出口网关的外部网络中防火墙开关开启的虚拟端口 · If the following conditions exist, you cannot enable firewall for an external vPort bound to the vRouter: ¡ The firewall service type specified for the vRouter is service leaf. ¡ The external network bound to the vPort has no segment ID. 虚拟路由器绑定Service Leaf类型防火墙和未指定External Segment ID外部网络中的虚拟端口时，该虚拟端口的防火墙开关不允许从关闭到开启 · If the following conditions exist, you cannot enable firewall for an external vPort bound to the vRouter: ¡ The firewall service type specified for the vRouter is service leaf. ¡ The external network bound to the vPort has no gateway binding. 虚拟路由器绑定Service Leaf类型防火墙和未指定出口网关外部网络中的虚拟端口时，该虚拟端口的防火墙开关不允许从关闭到开启 · If the following conditions exist, you cannot enable firewall for an external vPort bound to the vRouter: ¡ The firewall service type specified for the vRouter is service leaf. ¡ The vPort's external network is bound to a gateway whose method to deploy basic external connectivity settings is auto. 虚拟路由器绑定Service Leaf类型防火墙和指定外网转发基础配置为自动下发的出口网关的外部网络中的虚拟端口时，该虚拟端口的防火墙开关不允许从关闭到开启 · If the following conditions exist, you cannot enable firewall for an external vPort bound to the vRouter: ¡ The firewall service type specified for the vRouter is service leaf. ¡ The vPort's external network is bound to a gateway whose firewall deployment mode is not off. 虚拟路由器绑定Service Leaf类型防火墙和指定设备组防火墙接入模式为非关闭的出口网关的外部网络中的虚拟端口时，该虚拟端口的防火墙开关不允许从关闭到开启 · You cannot enable firewall service for the external vPorts bound to the vRouter. This is because the firewall service type specified for a vRouter is service leaf, the vRouter is one end of a centralized-mode vRouter link that has route reduction off and firewall service off at both ends：虚拟路由器绑定Service Leaf类型防火墙和两端防火墙关闭且路由精简开关关闭的集中式虚拟路由器连接时，不支持虚拟路由器绑定的外网虚拟端口防火墙开关从关闭切换为开启 · When you bind an external subnet to the vRouter, the subnet cannot overlap with the access subnet for the firewall associated with the vRouter：虚拟路由器绑定外网子网时，该外网子网与防火墙接入网段不能重叠 · Unsupported device type：该设备的设备类型不支持 · After you select a gateway whose firewall deployment mode is off and method to deploy basic external connectivity settings is manual, you cannot enable OSPF for the external network, and vice versa：外部网络不允许同时配置OSPF路由协议和绑定设备组防火墙接入模式为关闭且外网转发基础配置为手动预配置的出口网关 · After you bind to the external network a gateway whose firewall deployment mode is off and method to deploy basic external connectivity settings is manual, you cannot configure any NQA profile-subnet bindings, and vice versa：外部网络不允许同时配置子网绑定NQA策略和绑定设备组防火墙接入模式为关闭且外网转发基础配置为手动预配置的出口网关 · After you bind to the external network a gateway whose firewall deployment mode is off and method to deploy basic external connectivity settings is manual, you cannot enable primary IP allocation for any subnets, and vice versa：外部网络不允许同时开启子网主IP所在子网和绑定设备组防火墙接入模式为关闭且外网转发基础配置为手动预配置的出口网关 · After you select a gateway whose firewall deployment mode is off and method to deploy basic external connectivity settings is manual, you must configure a segment ID for the external network：当外部网络绑定设备组防火墙接入模式为关闭且外网转发基础配置为手动预配置的出口网关时，必须配置External Segment ID · When a vRouter has been bound to the external network, the external subnets cannot overlap with the subnet for firewall access：外部网络已被虚拟路由器绑定时，外网子网与防火墙接入网段重叠 · The external network is bound to a gateway whose firewall deployment mode is off and method to deploy basic external connectivity settings is manual. You must configure a segment ID：当外部网络绑定设备组防火墙接入模式为关闭且外网转发基础配置为手动预配置的出口网关时，External Segment ID不允许配置为空 · A vRouter that has border gateway bindings is bound to the external network. You cannot bind to the external network a gateway whose firewall deployment mode is off and method to deploy basic external connectivity settings is manual：外部网络已被虚拟路由器绑定且该虚拟路由器绑定了出口网关时，外部网络不允许绑定设备组防火墙接入模式为关闭且外网转发基础配置为手动预配置出口网关 · A vRouter that has a non-service leaf firewall binding is bound to the external network. You cannot bind a gateway whose firewall deployment mode is off to the external network：外部网络已被虚拟路由器绑定且该虚拟路由器绑定了非Service Leaf类型的防火墙时，不允许绑定设备组防火墙接入模式为关闭的出口网关 · You cannot disable firewall service for an external vPort bound to a vRouter when the following conditions exist: ¡ The vPort's external network is bound to a gateway that uses a device group with firewall deployment off and uses manual basic external connectivity deployment.. ¡ The border gateway bound to the vRouter is different from that bound to the vPort's external network. 外网虚拟端口所属的外部网络的出口网关设备组防火墙接入模式为关闭且外网转发基础配置为手动预配置，虚拟路由器绑定的出口网关和该外部网络指定的出口网关不一致时，该虚拟端口的防火墙开关不允许从开启切换为关闭 · The vRouter is bound to a service leaf firewall. Please make sure the firewall is enabled or disabled across all IP addresses and subnets in the external network：虚拟路由器绑定了Service Leaf类型的防火墙时，同外部网络下的外网子网过墙行为必须一致 · You cannot bind a flat-type external network to a vRouter that uses a service-leaf attached firewall as the edge device to the external network：当虚拟路由器的外网出口设备为防火墙且绑定Service Leaf类型防火墙时，不支持绑定FLAT类型的外部网络 · Auto basic external connectivity deployment is not available for the border gateway on an external network attached to a firewall-enabled vPort if the vPort is bound to a vRouter configured with a leaf-attached firewall：虚拟路由器绑定Service Leaf类型防火墙下，绑定防火墙开关为开启的虚拟端口时，虚拟端口所关联外部网络中指定的出口网关外网转发基础配置不支持自动下发模式 · When you bind an external network to a vRouter that uses a leaf-attached firewall as the edge device to the external network, the external network must meet the following requirements: 1. The network type is VLAN and the operating mode is indirectly connected. 2. The gateway to the external network uses manual basic external connectivity deployment and is bound to a device group with firewall deployment off. 3. The vRouter is not bound to any vPorts attached to the external network：当虚拟路由器的外网出口设备为防火墙且绑定Service Leaf类型防火墙时，绑定的外部网络必须满足：1）VLAN类型，2）共享模式，3)指定出口网关，该出口网关为手动预配置，且关联的设备组防火墙接入模式为关闭，4）未绑定此外部网络下的虚拟端口 · Please edit the tenant or vRouter name to ensure that the generated VPN instance name does not start with "external_vpn"：自动生成的VPN实例名称不能以"external_vpn"开头，请根据VPN实例名称生成规则检查并修改租户名称或者虚拟路由器名称 · The external network egress IP is already bound to a vRouter. For vRouters to share this IP, make sure these vRouters use the same third-party firewall setting. You can configure this setting when you configure the device group associated with a gateway member of a border gateway bound to a vRouter：该外网出口IP已被其他虚拟路由器绑定，如需共享，需确保共享该IP的所有虚拟路由器绑定的出口网关对应的设备组第三方防火墙开关必须一致 · Transit vRouters do not support configuring the tags field：TRANSIT类型虚拟路由器不支持配置tags字段 · When you configure the tags field for a normal or external transit vRouter, do not specify any tenant-exclusive border gateway：NORMAL或者EXTERNALTRANSIT类型虚拟路由器的tags字段中不能包含租户独占的出口网关 · The global VXLAN ID pool does not have assignable VXLAN IDs：全局VXLAN池没有可用的VXLAN ID · In the network cloud scenario, BGP neighbors do not support binding interconnect interfaces：网络云场景BGP邻居不支持绑定互联接口 · You must bind an interconnect interface or an external subnet to a BGP neighbor：BGP邻居必须绑定外部子网和互联接口其中之一 · The specified interconnect interface does not exist：互联接口不存在 · When you bind an interconnect interface to a BGP neighbor, make sure the interconnect interface has a border gateway binding：BGP邻居绑定的互联接口未绑定出口网关 · When you bind an interconnect interface to a BGP neighbor, make sure the border gateway associated with that interconnect interface has a vRouter binding：BGP邻居绑定的互联接口关联的出口网关未绑定虚拟路由器 · You must specify import RTs for a transit vRouter：虚拟路由器是TRANSIT类型时，必须指定引入RT · You must specify export RTs for a transit vRouter：虚拟路由器是TRANSIT类型时，必须指定引出RT · You must specify import RTs for an external transit vRouter：虚拟路由器是EXTERNALTRANSIT类型时，必须指定引入RT · You must specify export RTs for an external transit vRouter：虚拟路由器是EXTERNALTRANSIT类型时，必须指定引出RT · Make sure the import RTs and export RTs are consistent on a vRouter：虚拟路由器配置的引入RT与引出RT不一致 · Resource application or rollback failed, internal unknown error：资源申请或回滚失败，内部未知错误 · The（resource）does not exist or the resources are insufficient：（资源）不存在或资源不足 · The（resource）does not exist or the resources are insufficient, device group name（name）：（资源）不存在或资源不足，设备组名称（名称） · The （resource） does not exist or the resources are insufficient, resource access template name （name）：（资源）不存在或资源不足，资源接入模板名称（名称） · Invalid BGP peer authentication mode：无效的BGP对等体认证模式 · Password configuration is not supported if the BGP peer authentication mode is not Password Authentication：未指定BGP对等体认证模式为密码认证时不允许配置密码 · Password configuration is required if the BGP peer authentication mode is Password Authentication：指定BGP对等体认证模式为密码认证时不允许密码为空 · The password is case sensitive and cannot exceed 80 characters. Only letters, digits, and special characters except for question marks (?) are supported：密码长度最长80个字符，区分大小写，仅支持英文、数字和特殊字符（英文问号除外） · Cannot allocate this segment ID, because synchronization is in progress for the VXLAN pool containing this segment ID：无法分配该Segment ID，其所在的VXLAN池正在平滑中 · Cannot allocate segment IDs automatically, because no VXLAN pool is configured：未配置VXLAN池，无法自动分配Segment ID · Cannot allocate segment IDs automatically, because the VXLAN pool does not have available resources：VXLAN池中资源已耗尽，无法自动分配Segment ID · Cannot allocate segment IDs automatically. Please verify correctness of the VXLAN pool configuration and status：无法自动分配Segment ID，请检查VXLAN池配置及状态 · In the IPv6 scenario, a vRouter cannot have the same subnet bindings or external network binding as another vRouter：IPv6场景下，不允许存在绑定相同子网网段、相同外部网络的虚拟路由器 · The source IP address cannot be the IP address that the device uses as the interconnect address in an M-LAG routed peer link：源IP地址不能与M-LAG互联链路中相同设备的本端或对端互联地址相同 · The gatewaylist field is a read-only field：gatewaylist为只读字段 |
|
关键字 |
DELETE_ROUTE_OP |
|
日志内容 |
Deleted vRouter $1. |
|
参数解释 |
$1：虚拟路由器的参数体 |
|
举例 |
Deleted vRouter { "id":"56a937a9-55ce-48c1-866b-0be6386f16ec", "admin_state_up":"vrouter", "external_gateway_info":"{ "network_id":"10236dae-b97a-49b7-89ed-c225baa39d4e", "enable_snat":"true", "external_fixed_ips":"[FixedIpDto { "ip address":"26.3.3.10", "subnet id":"e2d81808-6b61-4ef2-85c6-65839489172b", }]" }", "name":"vrouter", "routes":"[{ "destination":"23.3.3.3/32", "nexthop":"12.3.3.31" }]", "tenant_id":"2b2151a2-f111-40f0-a0ea-61a76879e972", "tenant_name":"admin", "gw_port_id":"null", "tags":"[]", "cloud_region_name":"openstack", "subnets":"null" }. |
|
日志说明 |
用户进行了删除路由器的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The specified resource doesn't exist：指定的资源不存在 · Failed to delete the router, because it has a bound subnet：此路由器存在绑定的子网 · Failed to delete the vRouter because it has been bound to service resources：路由器已被服务资源绑定，无法删除 · Failed to delete the vRouter because it has been bound to a vRouter link：该虚拟路由器已绑定虚拟路由器连接，不允许删除 · Failed to delete the vRouter because the vRouter has routing tables：该虚拟路由器下存在路由表，不允许删除 · Failed to delete the vRouter because a routing table has been bound to the vRouter：虚拟路由器已绑定路由表，不允许删除 · The vRouter has been bound to a vRouter interconnection：该虚拟路由器已被虚拟路由器连接绑定 · The vRouter has been bound to a Layer 3 DC interconnection：该虚拟路由器已被数据中心三层互联绑定 · Failed to delete the vRouter because it has been bound to route entries：该虚拟路由器已被路由表项绑定，不允许删除 · Unknown error：未知错误 · Failed to delete the vRouter because the vRouter has BGP peers：删除虚拟路由器失败，指定的虚拟路由器正在被BGP邻居使用 · You have no privilege to perform this operation：用户无权限执行此操作 · You cannot delete the vRouter, because it has been bound to a EPG：该虚拟路由器已被EPG绑定,不允许删除 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · You cannot delete the vRouter, because it has been bound to an application policy：该虚拟路由器已被应用描述绑定，不允许删除 · The vRouter cannot be deleted because it has been bound to network ACL：指定的虚拟路由器已被网络ACL绑定，不允许删除 · All OpenStack-based cloud platforms have been isolated：所有的云平台已被隔离 · Resource application or rollback failed, internal unknown error：资源申请或回滚失败，内部未知错误 · The（resource）does not exist or the resources are insufficient：（资源）不存在或资源不足 · The（resource）does not exist or the resources are insufficient, device group name（name）：（资源）不存在或资源不足，设备组名称（名称） · The （resource） does not exist or the resources are insufficient, resource access template name （name）：（资源）不存在或资源不足，资源接入模板名称（名称） |
|
关键字 |
ADD_ROUTER_INTERFACE_OP |
|
日志内容 |
Added router interface $1. |
|
参数解释 |
$1：router interface信息 |
|
举例 |
Added router interface { "subnet_id":"a12159d8-3817-4e9b-9aa7-6c81c3ee2e12", “port_id”:” 828e4a01-09c6-4562-9d7e-5b9f3be2de39” }. |
|
日志说明 |
用户进行了创建虚拟路由接口的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The subnet has already been bound to another router：虚拟子网已经绑定了其它的虚拟路由器 · The subnet and the router are not in the same VDS：子网和虚拟路由器不在同一个VDS · The specified subnet doesn’t exist：指定的虚拟子网不存在 · The specified resource doesn't exist：指定的资源不存在 · The subnet overlaps with another subnet：子网与其它的子网重叠 · The subnet ID was null：子网ID为空 · The subnet and the vRouter are not in the same tenant：子网和路由器必须属于同一租户 · The subnet has already been bound to the vRouter：子网已关联虚拟路由器 · The subnet of the vRouter overlaps with the subnet of the other vRouter of the vRouter link：子网与虚拟路由器连接中的其他虚拟路由器下的子网重叠The subnet overlaps with a selected subnet of the other vRouter in a vRouter interconnection：该子网与虚拟路由器连接绑定的另一个虚拟路由器的已选子网重叠 · The subnet overlaps with a remote subnet in a Layer 3 DC interconnection that involves the vRouter：该子网与数据中心三层互联远端网段重叠 · The vPort already exists：虚拟端口已存在 · The port ID is different than the gateway port ID：端口ID与网关端口ID不一致 · The selected subnet cannot overlap with the network that contains the ingress or egress vPort in the vRouter's service chain：虚拟路由器下存在服务链业务，且已选子网与服务链中服务资源的入/出虚拟端口网段重叠 · Unknown error：未知错误 · The source IP address of a route entry with a vPort-type next hop on the vRouter cannot overlap with any vNetwork subnet on another vRouter：建立虚拟路由器连接的两个虚拟路由器，一个虚拟路由器下虚拟端口类型的路由表项的源IP不允许和另一个虚拟路由器下虚拟链路层网络的子网重叠 · The source IP address of a route entry with a vPort-type next hop on the vRouter cannot overlap with any external subnet on another vRouter：建立虚拟路由器连接的两个虚拟路由器，一个虚拟路由器下虚拟端口类型的路由表项的源IP不允许和另一个虚拟路由器下外部网络的子网重叠 · The source IP address of a route entry with a vPort-type next hop on the vRouter cannot be the same as any vNetwork subnet gateway IP of another vRouter：建立虚拟路由器连接的两个虚拟路由器，一个虚拟路由器下虚拟端口类型的路由表项的源IP不允许和另一个虚拟路由器下虚拟链路层网络子网的网关IP地址相同 · The source IP address of a route entry on the vRouter cannot be the same as any vNetwork subnet gateway IP on the vRouter：源IP地址不允许和同一虚拟路由器下虚拟链路层子网的网关IP地址相同 · The source IP address of a route entry on the vRouter cannot be within any vNetwork subnet on the vRouter：源IP地址不允许在同一虚拟路由器下虚拟链路层子网网段范围内 · The source IP address of a route entry on the vRouter cannot be within any external subnet on the vRouter：源IP地址不允许在同一虚拟路由器下外部网络的子网网段范围内 · Subnets in the same vNetwork must be bound to the same vRouter：同一虚拟链路层网络下的子网必须绑定同一虚拟路由器 · The indirectly connected external network can't be directly deleted from or added to the router：共享型外网子网不能直接从关联路由器中添加和删除 · Subnets in the same external network must be bound to the same vRouter：同一外部网络下的的子网必须绑定同一虚拟路由器 · You have no privilege to perform this operation：用户无权限执行此操作 · You cannot bind a vRouter to a vPort created by using a subnet for primary IP allocation：虚拟路由器不支持绑定使用主IP所在子网创建的虚拟端口 · The IPv4 subnet has been bound to a context, or it overlaps with the subnet attached to a service instance's ingress/egress vPort in a service chain. It cannot be assignedto the vRouter already specified in an IPv4 or IPv4 & IPv6 application policy：当IPv4子网已被服务链流量特征组绑定或子网网段与服务链中服务实例的出入虚拟端口网段相等时，其绑定的虚拟路由器与IPv4或IPv4 & IPv6的应用策略的虚拟路由器必须不同 · The IPv4 subnet overlaps with the subnet attached to the ingress or egress vPort for a service instance of a service path specified in an application policy. It cannot be assigned to this vRouter, which has been bound to a service chain：当IPv4子网网段与已被引用的服务路径中服务实例的出入虚拟端口网段相等时，其绑定的虚拟路由器与服务链的虚拟路由器必须不同 · Failed to assign the IPv4 subnet to the vRouter, because the vRouter has been bound to both a router context in a service chain and an IPv4 or IPv4 & IPv6 application policy：IPv4子网绑定虚拟路由器失败，因为目标虚拟路由器被服务链引用的Router类型流量特征组和IPv4或IPv4 & IPv6的应用策略同时绑定 · Failed to add some of the vSubnets. Please make sure the selected vSubnets are not used in the service chain associated with the vRouter：绑定子网失败，指定子网与该虚拟路由器绑定的服务链下的子网重叠 · Failed to bind the subnet to the vRouter, because it overlaps with a network bound to the context in another service chain：虚拟路由器绑定子网失败，该绑定会导致虚拟路由器所在特征组的服务链与其他服务链网段重叠 · The vRouter-attached gateway members enable the third-party firewall option. Please enable or disable the firewall option across all IP addresses or subnets in the vRouter-attached external network if the egress of the external network is the firewall or border device, respectively：虚拟路由器绑定了第三方防火墙开启的设备组，该虚拟路由器绑定外部网络下的外网子网防火墙设置需要和虚拟路由器上的外网出口设置一致 · The vRouter-attached gateway members disable the third-party firewall option and use hairpin firewall deployment. Please make sure the firewall is enabled or disabled across all IP addresses and subnets in the external network：虚拟路由器绑定了第三方防火墙关闭且防火墙接入模式是旁挂的设备组，同外部网络下的外网子网过墙行为必须一致 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · You cannot bind the IPv6 subnet to the vRouter, because the vRouter belongs to a vRouter link and has been bound to a centralized vNetwork：当虚拟路由器存在虚拟路由器连接时，不能同时绑定IPv6子网和集中式虚拟链路层网络 · Failed to bind the subnet to the vRouter, because the vRouter has been used by a service chain and bound to an external EPG containing external network CIDR 0.0.0.0/0：子网绑定虚拟路由器失败，该虚拟路由器已被服务链和External类型且外网网段包含0.0.0.0/0的EPG绑定 · The multicast network feature has been enabled for the external network, and the external network cannot be bound to a vRouter through a vPort：外部网络已开启组播网络开关，不允许使用虚拟端口方式绑定vRouter · A Layer 3 multicast network has been added to the external network, and the external network cannot be bound to a vRouter through a vPort：外部网络已有L3组播，不允许使用虚拟端口方式绑定vRouter · Operation failed. The vNetwork of the subnet has been an EPG member, and the subnet has been used by the private network CIDR：子网绑定虚拟路由器失败。指定子网所在的虚拟链路层网络已是EPG成员，该子网网段已被EPG的私有网段使用 · Make sure the extended SNAT IP addresses have not been used in the vNetwork：相同虚拟链路层网络下，扩展SNAT IP地址不能与已经存在的扩展SNAT IP地址或虚拟端口IP地址冲突 · You cannot specify an extended SNAT IP address as a floating IP address in the same external network：扩展SNAT IP地址不能与浮动IP冲突 · You cannot specify an extended SNAT IP address as a gateway IP address in the same external network：扩展SNAT IP地址不能与子网网关IP地址冲突 · If the edge device to external networks for an external transit vRouter is firewall, you cannot bind the vRouter to any directly-connected external network：EXTERNALTRANSIT类型虚拟路由器，外网出口设备为防火墙时，不允许绑定独享外网 · If the edge device to external networks for an external transit vRouter is border device, you cannot bind any vPorts to the vRouter：EXTERNALTRANSIT类型虚拟路由器，外网出口设备为边界设备时，不允许绑定外部网络中的虚拟端口 · You cannot bind an external transit vRouter to any external network that has subnets enabled with the primary IP allocation feature：EXTERNALTRANSIT类型虚拟路由器不允许绑定存在主IP子网的外网 · You cannot bind an external transit vRouter to any external network enabled with the multicast network feature：EXTERNALTRANSIT类型虚拟路由器不允许绑定开启了组播网络开关的外网 · The vRouters bound to an external network must be of the same type：外网不允许被不同类型虚拟路由器绑定 · You cannot bind the external transit vRouter to any external network referenced by OSPF：EXTERNALTRANSIT类型虚拟路由器不支持绑定被OSPF引用的外网 |
|
关键字 |
DELETE_ROUTER_INTERFACE_OP |
|
日志内容 |
Deleted router interface $1. |
|
参数解释 |
$1：router interface信息 |
|
举例 |
Deleted router interface { "subnet_id":"a12159d8-3817-4e9b-9aa7-6c81c3ee2e12", “port_id”:” 828e4a01-09c6-4562-9d7e-5b9f3be2de39” }. |
|
日志说明 |
用户进行了删除虚拟路由接口的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The subnet can’t be directly deleted from or added to the router：外网子网不能直接从关联路由器中添加和删除 · The specified subnet doesn’t exist：指定的虚拟子网不存在 · The subnet has already been unbound from router：该子网已经从虚拟路由器中移除 · The subnet ID is required：未指定子网ID · Failed to delete the interface from the vRouter, because the vPort or APP cluster VIP in the subnet has a floating IP：从vRouter解绑定接口失败，子网下存在绑定浮动IP的端口或应用集群虚IP · The specified resource doesn't exist：指定的资源不存在 · The subnet has been bound to a routing table：该子网已绑定路由表 · The vPort has been bound to a routing table：该虚拟端口已绑定路由表 · The subnet overlaps with the destination subnet of the route entry：子网网段与路由表项的目的网段重叠 · Unknown error：未知错误 · The indirectly connected external network can't be directly deleted from or added to the router：共享型外网子网不能直接从关联路由器中添加和删除 · Failed to remove the subnet from the vRouter because the vRouter has BGP peers on this subnet：删除子网失败，指定的子网正在被BGP邻居使用 · You have no privilege to perform this operation：用户无权限执行此操作 · The vRouter has not been bound to the port：虚拟路由器未绑定该端口 · The vNetwork is an interface-specific multicast network. You cannot unbind its only subnet from the vRouter：指定的虚拟链路层网络已经绑定组播接口，该虚拟链路层网络下的最后一个子网不允许解绑虚拟路由器 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · You cannot delete the subnet, because it has been specified for the ingress or egress vPort of a third-party service device bound to a service path：指定子网已被第三方服务设备的出入虚拟端口使用，且该第三方服务设备已被服务路径使用，不允许解绑 |
|
关键字 |
DELETE_ROUTERINTERFACE_DEVCHECK_OP |
|
日志内容 |
Checked the state of southbound devices upon router interface deletion. |
|
参数解释 |
无 |
|
举例 |
Checked the state of southbound devices upon router interface deletion. |
|
日志说明 |
用户删除虚拟路由器接口时，云插件校验了南向设备失联状态 |
|
失败原因 |
当操作失败时，可能的原因如下： · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
CREATE_QOS_POLICY_OP |
|
日志内容 |
Created QoS policy $1. |
|
参数解释 |
$1：QoS模板的参数体 |
|
举例 |
Created QoS policy { "id":"80a9c840-41be-416f-b70f-abd8ddb1adee", "name":"111", "description":"null", "rules":"[{ "max_kbps":"null", "max_burst_kbps":"null", "rule_type":"dscp_marking", "dscp_mark":"5", "direction":"null" }, { "max_kbps":"1", "max_burst_kbps":"16", "rule_type":"bandwidth_limit", "dscp_mark":"null", "direction":"INGRESS" }, { "max_kbps":"3", "max_burst_kbps":"32", "rule_type":"bandwidth_limit", "dscp_mark":"null", "direction":"EGRESS" }]", "cloud_region_name":"openstack" }. |
|
日志说明 |
用户进行了创建QoS模板的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The QoS profile UUID is already used：QoS模板UUID已存在 · Invalid CIR value of inbound QoS profile：入方向QoS模板平均速率参数无效 · Invalid CIR value of outbound QoS profile：出方向QoS模板平均速率参数无效 · Invalid CBS value of inbound QoS profile：入方向QoS模板突发尺寸参数无效 · Invalid CBS value of outbound QoS profile：出方向QoS模板突发尺寸参数无效 · Invalid DSCP value：无效的DSCP参数 · Invalid QoS profile rate value：QoS模板的速率值不可用 · QoS profiles created in bulk cannot use the same UUID：批量创建的QoS模板的UUID存在重复 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作All OpenStack-based cloud platforms have been isolated：所有的云平台已被隔离 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · You can configure up to 65534 flow-based rate limiting rules in a QoS template：QoS模板中流限速的QoS规则最多配置65534条 · You cannot configure both flow-based rate limiting and port-based rate limiting：流限速类型和端口限速类型不允许同时配置 · Duplicate flow-based rate limiting rule IDs：流限速规则的ID重复 · Invalid IP version：无效的IP版本 · Invalid protocol type：无效的协议类型 · The value for the average field must be in the range of 1 to 4294967295：平均速率取值范围为1~4294967295 · The value for the burst field must be in the range of 1 to 536869888：突发尺寸的取值范围为1~536869888 · Please specify the average field and the burst field：平均速率和突发尺寸都不能为空 · The value for the icmp_type field must be in the range of 0 to 255：icmp_type参数的取值范围为0~255 · The value for the icmp_code field must be in the range of 0 to 255：icmp_code参数的取值范围为0~255 · The value range for the port number is 0 to 65535. The source_port or destination_port field can be a single port or a port range in the format of XX-XX. To specify a port number range, make sure the start value is not greater than the end value：source_port参数和destination_port参数的取值范围为0～65535的整数或区间，当取值为区间时，格式为XX-XX，且起始值不能大于结束值 · Invalid direction for the flow-based rate limiting rule：无效的流限速规则方向 · Please specify a source IP/subnet, destination IP/subnet, or both：源IP地址/网段和目的IP地址/网段至少指定一个 · Invalid IP or subnet：无效的IP地址或网段 · The specified IP or subnet does not match the IP version：IP地址或网段与IP版本不匹配 · Overlapping quintuple information for flow-based rate limiting rules in the same direction：同一流限速下同方向QoS规则的五元组信息重叠 · You can edit only the average and burst fields for a flow-based rate limiting rule：流限速规则仅允许修改平均速度和突发尺寸 · The specified QoS template has been bound to a floating IP. You cannot set the rate limiting type to flow-based：指定的QoS模板已绑定浮动IP，限速类型不允许为流限速类型 · The icmp_type and icmp_code fields can be configured only when the protocol type is ICMP：协议类型为ICMP时，才允许配置icmp_type和icmp_code字段 · The source_port and destination_port fields can be configured only when the protocol type is TCP or UDP：协议类型为TCP或UDP时，才允许配置source_port和destination_port字段 · A parent port and its subports must be configured with the same QoS profile：父端口和其子端口必须配置相同类型的QoS策略 · Do not set both the Source IP/Subnet and Destination IP/Subnet parameters to a subnet with an all-zero mask. If you configure one of the parameters as a subnet with an all-zero mask, the other parameter cannot be empty：源IP/网段和目的IP/网段不允许同时配置为掩码全0的网段，且不允许一个参数为空，另一个参数的掩码全为0 · DSCP values cannot be configured, when a QoS rule is applied to the inbound (VM) direction：QoS入方向流规则，不支持配置DSCP · The DSCP value range is 0 to 63, when a QoS rule is applied to the outbound (VM) direction：存在出方向流规则，DSCP缺省为空，支持配置，取值范围是0~63的整数 |
|
关键字 |
UPDATE_QOS_POLICY_OP |
|
日志内容 |
Updated QoS policy $1. |
|
参数解释 |
$1：QoS模板的参数体 |
|
举例 |
Updated QoS policy { "id":"80a9c840-41be-416f-b70f-abd8ddb1adee", "name":"111", "description":"null", "rules":"[{ "max_kbps":"null", "max_burst_kbps":"null", "rule_type":"dscp_marking", "dscp_mark":"5", "direction":"null" }, { "max_kbps":"1", "max_burst_kbps":"16", "rule_type":"bandwidth_limit", "dscp_mark":"null", "direction":"INGRESS" }, { "max_kbps":"3", "max_burst_kbps":"32", "rule_type":"bandwidth_limit", "dscp_mark":"null", "direction":"EGRESS" }]", "cloud_region_name":"openstack" }. |
|
日志说明 |
用户进行了修改QoS模板的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The QoS profile ID is required：未指定QoS模板UUID · Failed to remove the inbound QoS profile：取消入方向QoS模板失败 · Failed to remove the outbound QoS profile：取消出方向QoS模板失败 · Invalid CIR value of inbound QoS profile：入方向QoS模板平均速率参数无效 · Invalid CIR value of outbound QoS profile：出方向QoS模板平均速率参数无效 · Invalid CBS value of inbound QoS profile：入方向QoS模板突发尺寸参数无效 · Invalid CBS value of outbound QoS profile：出方向QoS模板突发尺寸参数无效 · Invalid DSCP value：无效的DSCP参数 · The specified resource doesn't exist：指定的资源不存在 · Invalid QoS profile rate value：QoS模板的速率值不可用 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · You cannot edit or delete the cloud region name：云区域名称不允许修改或删除 · All OpenStack-based cloud platforms have been isolated：所有的云平台已被隔离 · You can configure up to 65534 flow-based rate limiting rules in a QoS template：QoS模板中流限速的QoS规则最多配置65534条 · You cannot configure both flow-based rate limiting and port-based rate limiting：流限速类型和端口限速类型不允许同时配置 · Duplicate flow-based rate limiting rule IDs：流限速规则的ID重复 · Invalid IP version：无效的IP版本 · Invalid protocol type：无效的协议类型 · The value for the average field must be in the range of 1 to 4294967295：平均速率取值范围为1~4294967295 · The value for the burst field must be in the range of 1 to 536869888：突发尺寸的取值范围为1~536869888 · Please specify the average field and the burst field：平均速率和突发尺寸都不能为空 · The value for the icmp_type field must be in the range of 0 to 255：icmp_type参数的取值范围为0~255 · The value for the icmp_code field must be in the range of 0 to 255：icmp_code参数的取值范围为0~255 · The value range for the port number is 0 to 65535. The source_port or destination_port field can be a single port or a port range in the format of XX-XX. To specify a port number range, make sure the start value is not greater than the end value：source_port参数和destination_port参数的取值范围为0～65535的整数或区间，当取值为区间时，格式为XX-XX，且起始值不能大于结束值 · Invalid direction for the flow-based rate limiting rule：无效的流限速规则方向 · Please specify a source IP/subnet, destination IP/subnet, or both：源IP地址/网段和目的IP地址/网段至少指定一个 · Invalid IP or subnet：无效的IP地址或网段 · The specified IP or subnet does not match the IP version：IP地址或网段与IP版本不匹配 · Overlapping quintuple information for flow-based rate limiting rules in the same direction：同一流限速下同方向QoS规则的五元组信息重叠 · You can edit only the average and burst fields for a flow-based rate limiting rule：流限速规则仅允许修改平均速度和突发尺寸 · The specified QoS template has been bound to a floating IP. You cannot set the rate limiting type to flow-based：指定的QoS模板已绑定浮动IP，限速类型不允许为流限速类型 · The icmp_type and icmp_code fields can be configured only when the protocol type is ICMP：协议类型为ICMP时，才允许配置icmp_type和icmp_code字段 · The source_port and destination_port fields can be configured only when the protocol type is TCP or UDP：协议类型为TCP或UDP时，才允许配置source_port和destination_port字段 · A parent port and its subports must be configured with the same QoS profile：父端口和其子端口必须配置相同类型的QoS策略 · DSCP values cannot be configured, when a QoS rule is applied to the inbound (VM) direction：QoS入方向流规则，不支持配置DSCP · The DSCP value range is 0 to 63, when a QoS rule is applied to the outbound (VM) direction：存在出方向流规则，DSCP缺省为空，支持配置，取值范围是0~63的整数 |
|
关键字 |
DELETE_QOS_POLICY_OP |
|
日志内容 |
Deleted QoS policy $1. |
|
参数解释 |
$1：QoS模板的参数体 |
|
举例 |
Deleted QoS policy { "id":"80a9c840-41be-416f-b70f-abd8ddb1adee", "name":"111", "description":"null", "rules":"[{ "max_kbps":"null", "max_burst_kbps":"null", "rule_type":"dscp_marking", "dscp_mark":"5", "direction":"null" }, { "max_kbps":"1", "max_burst_kbps":"16", "rule_type":"bandwidth_limit", "dscp_mark":"null", "direction":"INGRESS" }, { "max_kbps":"3", "max_burst_kbps":"32", "rule_type":"bandwidth_limit", "dscp_mark":"null", "direction":"EGRESS" }]", "cloud_region_name":"openstack" }. |
|
日志说明 |
用户进行了删除QoS模板的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The Qos profile has been bound to a port：QoS模板已被虚拟端口绑定 · The Qos profile has been bound to a port group：QoS模板已被端口组绑定 · The Qos profile has been bound to a virtual network：QoS模板已被虚拟链路层网络绑定 · The QoS profile has been bound to floating IPs：QoS模板已被浮动IP绑定 · The specified resource doesn't exist：指定的资源不存在 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 · All OpenStack-based cloud platforms have been isolated：所有的云平台已被隔离 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
UPDATE_QOSPOLICY_DEVCHECK_OP |
|
日志内容 |
Checked the state of southbound devices upon QoS policy update. |
|
参数解释 |
无 |
|
举例 |
Checked the state of southbound devices upon QoS policy update. |
|
日志说明 |
用户更新QoS模板时，云插件校验了南向设备失联状态 |
|
失败原因 |
当操作失败时，可能的原因如下： · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
CREATE_FLOATING_IP_OP |
|
日志内容 |
Created floating IP $1. |
|
参数解释 |
$1：浮动IP地址的参数体 |
|
举例 |
Created floating IP { "id":"74d2775e-3065-4fb0-bf88-6629ef0abcea", "tenant_id":"2b2151a2-f111-40f0-a0ea-61a76879e972", "qos_policy_id":"null", "floating_network_id":"0184331f-e0b4-431a-9a8c-dcf7245cbaf6", "router_id":"null", "floating_ip_address":"20.20.0.3", "port_id":"3f829afd-2581-4d34-bc22-55f69eee4c01", "extra":"{ "rx_averateLimit":"null", "tx_averateLimit":"null" }", "protocol":"null", "port_number":"null", "local_port_number":"null", "local_port_number":"null", "cloud_region_name":"openstack" }. |
|
日志说明 |
用户进行了创建浮动IP的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The specified subnet doesn't exist：指定的虚拟子网不存在 · The specified subnet is not an external subnet：指定子网不是外网子网 · The specified port doesn't exist：指定的端口不存在 · Invalid port type：无效的端口类型 · The fixed IP address must be the IP address of the port：fixed_ip_address必须与端口IP地址一致 · The port has not been bound to the router：端口未绑定虚拟路由器 · Floating IP address allocation failed：地址分配失败 · The IP address must belong to the specified subnet：IP地址不在子网内 · The network doesn't exist：虚拟网络不存在 · Failed to bind the floating IP to the vPort or APP cluster VIP, because the floating IP doesn't belong to the external network bound to the vRouter of the vPort or APP cluster VIP：关联浮动IP地址失败，浮动IP地址所属外部网络与端口或应用集群虚IP所属vRouter的外部网络不一致 · The floating IP ID already exists：浮动IP的ID已存在 · Floating IPs created in bulk cannot use the same ID：批量创建的浮动IP的ID存在重复 · The APP cluster VIP doesn't exist：应用集群虚IP不存在 · Invalid protocol type：无效的协议类型 · Invalid port number：指定的端口号错误 · The configuration conflicts with the configuration of an existing floating IP：该配置与其他浮动IP的配置相冲突 · The floating IP can be bound only to a vPort or an APP cluster VIP：浮动IP只能绑定虚拟端口或应用集群虚IP · The subnet to which the APP cluster VIP belongs is not bound to a vRouter：应用集群虚IP所属子网未绑定虚拟路由器 · The configuration of the floating IP conflicts with the configuration of a bound floating IP：浮动IP的配置与已绑定的浮动IP相冲突 · Invalid local port number：参数local_port_number不可用 · The IP address doesn't belong to the network：该IP地址不属于该网络 · The specified network is not an external network：指定的网络不是外网网络 · The specified subnet doesn't belong to the network：指定的子网不属于该网络 · The vRouter is not bound to an external network：虚拟路由器未绑定外网 · The external network doesn't exist：外网不存在 · The external network doesn't have any subnets：指定的外网无子网 · The floating IP conflicts with an extranet IP：指定的浮动IP地址与外网IP冲突 · The floating IP conflicts with a gateway IP：指定的浮动IP地址与网关IP冲突 · The floating IP conflicts with the broadcast address of the subnet：浮动IP地址和子网广播IP地址冲突 · The floating IP conflicts with the subnet address：浮动IP地址和子网地址冲突 · The UUIDs of the vPort, APP cluster VIP, subnet, and network to which the floating IP belongs are not specified：未指定端口ID、应用集群虚IP和浮动IP所属子网 · Invalid IP address：无效的IP地址 · The QoS policy and inbound/outbound CIR cannot be both configured：QoS策略与入/出方向平均速率不能同时配置 · Unknown error：未知错误 · Cannot set floating IPs for a directly connected external network：浮动IP不支持配置独享型外部网络 · When you create a floating IP, if you specify only the vPort or App cluster VIP and the vRouter of the floating IP is bound to one external network with network segmentation enabled or multiple external networks, you must specify an IP address for the floating IP：创建浮动IP时，如果仅指定了虚拟端口或应用集群虚IP，且所属虚拟路由器绑定多个外网或一个外网开启了网络分段功能，则需要指定浮动IP地址 · You have no privilege to perform this operation：用户无权限执行此操作 · You cannot select a subnet for primary IP allocation when creating a floating IP：不支持使用主IP所在子网创建浮动IP · The external network does not have IPv4 vSubnets for allocating floating IPs：分配浮动IP失败，不存在对应IPv4版本的外网子网 · All OpenStack-based cloud platforms have been isolated：所有的云平台已被隔离 · You cannot specify the floating IP address as an extended SNAT IP address in the same external network：浮动IP不能与扩展SNAT IP地址冲突 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · The network_id and subnet_id fields of an INTERNAL_IP floating IP cannot be empty at the same time：INTERNAL_IP类型浮动IP的network_id，subnet_id不能同时为空 · Invalid floating IP type：无效的浮动IP类型 · You must specify an internal IP address for an INTERNAL_IP floating IP：INTERNAL_IP类型浮动IP的内网IP地址不能为空 · The floating IP type is not editable：浮动IP类型不支持修改 · You must specify the IP address of an INTERNAL_IP floating IP：INTERNAL_IP类型浮动IP的IP地址不能为空 · The port_id field of an INTERNAL_IP floating IP must be empty：INTERNAL_IP类型浮动IP的port_id必须为空 · The clusterIpId field of an INTERNAL_IP floating IP must be empty：INTERNAL_IP类型浮动IP的clusterIpId必须为空 · The vrouter_id field of an INTERNAL_IP floating IP cannot be empty：INTERNAL_IP类型浮动IP的vrouter_id不能为空 · You can specify only an external transit vRouter for a floating IP of the INTERNAL_IP floating type：INTERNAL_IP类型浮动IP仅支持EXTERNALTRANSIT类型虚拟路由器 · You cannot bind a floating IP to a flow-based rate limiting QoS policy：浮动IP不允许绑定流限速类型的QoS策略 |
|
关键字 |
UPDATE_FLOATING_IP_OP |
|
日志内容 |
Updated floating IP $1. |
|
参数解释 |
$1：浮动IP地址的参数体 |
|
举例 |
Updated floating IP { "id":"74d2775e-3065-4fb0-bf88-6629ef0abcea", "tenant_id":"2b2151a2-f111-40f0-a0ea-61a76879e972", "qos_policy_id":"null", "floating_network_id":"0184331f-e0b4-431a-9a8c-dcf7245cbaf6", "router_id":"null", "floating_ip_address":"20.20.0.3", "port_id":"3f829afd-2581-4d34-bc22-55f69eee4c01", "extra":"{ "rx_averateLimit":"null", "tx_averateLimit":"null" }", "protocol":"null", "port_number":"null", "local_port_number":"null", "local_port_number":"null", "cloud_region_name":"openstack" }. |
|
日志说明 |
用户进行了修改浮动IP的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The specified port doesn't exist：指定的端口不存在 · The port has not been bound to the router：端口未绑定虚拟路由器 · The external network doesn't exist：外网不存在 · The floating IP has been bound to another port：浮动IP已绑定其他端口 · The specified resource doesn't exist：指定的资源不存在 · The gateway of the vRouter to which the floating IP belongs doesn't support floating IP addresses：浮动IP所属虚拟路由器的网关不支持浮动IP功能 · The floating IP address has been used by another gateway resource：浮动IP地址已被其他网关资源占用 · The vRouter to which the floating IP address belongs doesn't bind a gateway service resource：浮动IP所属的虚拟路由器未绑定网关服务资源 · The vRouter to which the floating IP address belongs has not been bound to a gateway：浮动IP所属的虚拟路由器未指定网关 · Failed to bind the floating IP to the vPort or APP cluster VIP, because the floating IP doesn't belong to the external network bound to the vRouter of the vPort or APP cluster VIP：关联浮动IP地址失败，浮动IP地址所属外部网络与端口或应用集群虚IP所属vRouter的外部网络不一致 · The APP cluster VIP doesn't exist：应用集群虚IP不存在 · Invalid protocol type：无效的协议类型 · Invalid port number：指定的端口号错误 · The floating IP can be bound only to a vPort or an APP cluster VIP：浮动IP只能绑定虚拟端口或应用集群虚IP · The subnet to which the APP cluster VIP belongs is not bound to a vRouter：应用集群虚IP所属子网未绑定虚拟路由器 · The floating IP has been bound to another APP cluster VIP：浮动IP已绑定其它应用集群虚IP · The configuration of the floating IP conflicts with the configuration of a bound floating IP：浮动IP的配置与已绑定的浮动IP相冲突 · Invalid local port number：参数local_port_number不可用 · Invalid IP address：无效的IP地址 · The IP address of the floating IP can't be modified：浮动IP的IP地址不允许被修改 · The protocol type and the port number of the floating IP can't be modified：浮动IP的协议类型和端口号不允许被修改 · The UUIDs of the vPort, APP cluster VIP, subnet, and network to which the floating IP belongs are not specified：未指定端口ID、应用集群虚IP和浮动IP所属子网 · The QoS policy and inbound/outbound CIR cannot be both configured：QoS策略与入/出方向平均速率不能同时配置 · The subnet to which the floating IP belongs is already bound to a network segment. However, all IPv4 subnets of that network segment are not bound to the vRouter or any of its peer vRouters in distributed-mode vRouter links：浮动IP所属子网已绑定网络分段，且该网络分段绑定的所有IPv4子网均未被虚拟路由器或与该虚拟路由器建立分布式虚拟路由器连接的虚拟路由器绑定 · Unknown error：未知错误 · Cannot set floating IPs for a directly connected external network：浮动IP不支持配置独享型外部网络 · You have no privilege to perform this operation：用户无权限执行此操作 · You cannot edit or delete the cloud region name：云区域名称不允许修改或删除 · All OpenStack-based cloud platforms have been isolated：所有的云平台已被隔离 · You cannot specify the floating IP address as an extended SNAT IP address in the same external network：浮动IP不能与扩展SNAT IP地址冲突 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · The network_id and subnet_id fields of an INTERNAL_IP floating IP cannot be empty at the same time：INTERNAL_IP类型浮动IP的network_id，subnet_id不能同时为空 · Invalid floating IP type：无效的浮动IP类型 · You must specify an internal IP address for an INTERNAL_IP floating IP：INTERNAL_IP类型浮动IP的内网IP地址不能为空 · The floating IP type is not editable：浮动IP类型不支持修改 · You must specify the IP address of an INTERNAL_IP floating IP：INTERNAL_IP类型浮动IP的IP地址不能为空 · The port_id field of an INTERNAL_IP floating IP must be empty：INTERNAL_IP类型浮动IP的port_id必须为空 · The clusterIpId field of an INTERNAL_IP floating IP must be empty：INTERNAL_IP类型浮动IP的clusterIpId必须为空 · The vrouter_id field of an INTERNAL_IP floating IP cannot be empty：INTERNAL_IP类型浮动IP的vrouter_id不能为空 · You can specify only an external transit vRouter for a floating IP of the INTERNAL_IP floating type：INTERNAL_IP类型浮动IP仅支持EXTERNALTRANSIT类型虚拟路由器 · You cannot bind a floating IP to a flow-based rate limiting QoS policy：浮动IP不允许绑定流限速类型的QoS策略 · All IPv4 subnets of the external network to which the floating IP belongs are not bound by the vRouter：浮动IP所属外部网络所有IPv4子网均未被虚拟路由器绑定 |
|
关键字 |
DELETE_FLOATING_IP_OP |
|
日志内容 |
Deleted floating IP $1. |
|
参数解释 |
$1：浮动IP地址的参数体 |
|
举例 |
Deleted floating IP { "id":"74d2775e-3065-4fb0-bf88-6629ef0abcea", "tenant_id":"2b2151a2-f111-40f0-a0ea-61a76879e972", "qos_policy_id":"null", "floating_network_id":"0184331f-e0b4-431a-9a8c-dcf7245cbaf6", "router_id":"null", "floating_ip_address":"20.20.0.3", "port_id":"3f829afd-2581-4d34-bc22-55f69eee4c01", "extra":"{ "rx_averateLimit":"null", "tx_averateLimit":"null" }", "protocol":"null", "port_number":"null", "local_port_number":"null", "local_port_number":"null", "cloud_region_name":"openstack" }. |
|
日志说明 |
用户进行了删除浮动IP的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The specified resource doesn't exist：指定的资源不存在 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 · All OpenStack-based cloud platforms have been isolated：所有的云平台已被隔离 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
UPDATE_FLOATINGIP_DEVCHECK_OP |
|
日志内容 |
Checked the state of southbound devices upon floating IP update. |
|
参数解释 |
无 |
|
举例 |
Checked the state of southbound devices upon floating IP update. |
|
日志说明 |
用户更新浮动IP时，云插件校验了南向设备失联状态 |
|
失败原因 |
当操作失败时，可能的原因如下： · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
CREATE_PORT_OP |
|
日志内容 |
Created vPort $1. |
|
参数解释 |
$1：虚拟端口的参数体 |
|
举例 |
Created vPort { "id": "46d4bfb9-b26e-41f3-bd2e-e6dcc1ccedb2", "name": "11", "device id": "5e3898d7-11be-483e-9732-b2f5eccd2b2e", "device owner": "compute:nova", "network id": "6a21c566-692a-4214-a3a1-79eb654ba9ab", "tenant id": "4fd44f30-2929-45e4-81c7-b8a0c8908869", "fixed ips": [ { "ip address": "4.4.4.5", "subnet id": "8941dfed-517f-42e6-a56a-576e82efb740" } ], "binding:profile": { "enable_snat": true, "fw_enabled": "false", "migrating_to": "host1", "external snat ips": [] }, "binding host id": "hostname", "binding vif type": "none", "binding vnic type": "normal", "delete vlan map flag": false, "cloud region name": "default", "vlan": "2" } } |
|
日志说明 |
用户进行了创建虚拟端口的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · Invalid tenant ID：无效的租户ID · The network doesn’t exist：虚拟网络不存在 · Ports created in bulk cannot use the same ID：批量创建的虚拟端口的ID存在重复 · Duplicate port ID：虚拟端口ID重复 · The network ID is required：未指定虚拟网络ID · Invalid port group ID：无效的端口组ID · The port group and the port don’t reside on the same network：端口组所在网络和虚拟端口所在网络不一致 · The default uplink port policy can’t be used as the port policy：端口策略不能使用缺省上行口策略 · The specified QoS policy doesn't exist：指定的QoS策略不存在 · Invalid port security policy UUID：无效的端口安全策略UUID · The MAC address is already used by another port：端口MAC地址冲突 · The port and the gateway can't use the same IP address：端口IP地址和网关IP地址冲突 · Neither the MAC address nor the IP address is configured：未配置端口IP地址和MAC地址 · The IP address is already used by another port：该IP地址已被其他端口占用 · The port IP address must belong to an existing subnet：未找到IP地址对应的子网 · The IP address must belong to the specified subnet：IP地址不在子网内 · The subnet must belong to the specified network：子网不在指定的虚拟链路层网络内 · The domain doesn't exist：计算域不存在 · The mirror direction is required：未指定镜像方向 · The mirror type is required：未指定镜像类型 · Invalid mirror direction：无效的镜像方向 · Invalid mirror type：无效的镜像类型 · Invalid mirror remote IP：无效的镜像远端IP · The mirror remote IP is required：镜像远端IP不准确 · The length of the description is out of range：描述的长度超出范围 · The VLAN ID must be an integer in the range of 1 to 4094：VLAN ID必须为1～4094的整数 · Invalid flooding domain：无效的泛洪域 · Invalid APP cluster VIP：无效的应用集群虚IP · The APP cluster VIP and the vPort don't reside on the same network：应用集群虚IP所在网络和虚拟端口所在网络不一致 · The flooding domain and the vPort don't reside on the same network：泛洪域所在网络和虚拟端口所在网络不一致 · The vPort can be bound to a maximum of 10 flooding domains：vPort最多只能绑定10个泛洪域 · The specified subnet doesn't exist：指定的虚拟子网不存在 · Invalid IP address：无效的IP地址 · The host name cannot exceed 255 characters.：主机名最长255个字符 · APP cluster VIPs bound to the same vPort must belong to the same subnet：同一个虚拟端口上绑定的应用集群虚IP必须属于同一个子网 · The subnet to which the vPort belongs must be bound to a vRouter because the vPort has been bound to a routing table：vPort已绑定路由表时，vPort所在的子网必须绑定vRouter · The subnets of the flooding domains bound to the same vPort can't overlap with each other：同一虚拟端口下的不同泛洪域的IP网段不能相互重叠 · The specified resource doesn't exist：指定的资源不存在 · The MAC address conflicts with the gateway MAC address， reserved gateway MAC address or device group MAC：MAC地址与网关MAC地址、保留的网关MAC地址或者设备组的MAC地址冲突 · Invalid MAC address：无效的MAC地址 · The vPort name cannot exceed 255 characters：虚拟端口名称最长255个字符 · Operation failed. The security policy rule failed to take effect because of insufficient hardware resources：操作失败，硬件资源不足导致安全策略规则无法生效 · The specified tenant doesn't exist：指定的租户不存在 · The extend_dhcp_options field is invalid：无效的extend_dhcp_options · The value of the opt_name field is required：未指定DHCP选项名称 · The value of the opt_name field is invalid：无效的DHCP选项名称 · The value of the opt_value field is required：未指定DHCP选项值 · The value of the server-ip-address DHCP option is invalid：DHCP选项server-ip-address的选项值无效 · The value of the tftp-server DHCP option cannot exceed 63 characters：DHCP选项tftp-server的选项值最长63个字符 · The value of the bootfile-name DHCP option cannot exceed 127 characters：DHCP选项bootfile-name的选项值最长127个字符 · The values of the opt_name fields cannot be the same：DHCP选项名称不能重复 · The number of NTP server addresses cannot exceed 63：NTP服务器地址个数不能超过63个 · The NTP server address is invalid：无效的NTP服务器地址 · Duplicated NTP server addresses exist：NTP服务器地址列表中存在冲突的地址 · The fixed_ips field is required：fixed_ips不能为空 · The IP address of a vPort can be null only when the vPort resides on an external network or the subnet to which the vPort belongs is enabled with DHCP：仅当虚拟端口所属网络为外部网络或其所属子网使能DHCP功能时，端口IP地址才允许为空 · The vPort cannot have duplicated IP addresses：该虚拟端口的多个IP地址不能重复 · The vPort type is invalid：无效的虚拟端口类型 · You cannot delete the gateway vPort：网关类型虚拟端口不允许删除 · The value of the device owner parameter for LB vPorts must be neutron:LOADBALANCER or neutron:LOADBALANCERV2：该LB类型虚拟端口对应的device_owner必须配置为neutron:LOADBALANCER或neutron:LOADBALANCERV2 · The vPort type and the value of the device owner parameter do not match：虚拟端口的类型与设备拥有者的类型不匹配 · IP addresses in the subnet to which the vPort belongs are used up：该虚拟端口所属子网的IP地址已分配完 · Unknown error：未知错误 · vPorts do not support directly connected external networks：虚拟端口不支持独享型外部网络 · The value of the port_security_enabled is invalid：port_security_enabled参数非法 · A port group cannot be bound to a security policy when it contains port security disabled vPorts：虚拟端口未开启端口安全时，不允许该端口所属的端口组绑定安全策略 · A vPort with port security disabled cannot be bound to a security policy：虚拟端口未开启端口安全时，不允许绑定安全策略 · A vPort with port security disabled cannot be configured with allowed address pairs：虚拟端口未开启端口安全时，不允许配置可用地址对 · You have no privilege to perform this operation：用户无权限执行此操作 · The MAC address cannot contain all zeros or all Fs：MAC地址不能为全0或全F · Do not specify the port_isolated field when you create a vPort：创建虚拟端口时，port_isolated字段不允许携带 · A vPort name cannot start with "gateway"：虚拟端口名称不能以“gateway”开头 · Please enter an IP address for the external network vPort：外网虚拟端口IP不能为空 · Do not specify the port_isolated field when you create a vPort：创建虚拟端口时，port_isolated字段不允许携带 · You cannot bind a vPort to a subnet for primary IP allocation in an external network：虚拟端口不允许绑定外部网络下主IP所在子网 · The external subnet where the specified IP address resides has been bound to an NQA profile. You cannot assign the IP address to a vPort：指定IP地址所在的外网子网已关联NQA策略，无法绑定至虚拟端口 · Failed to connect to (hosts or access devices). Host or access device IPs: {IP addresses}：(主机/接入设备){IP地址集合}连接失败 · The latest links are invalid or no links exist on the netoverlay hosts found by names of (hosts or access devices)：(主机/接入设备)名称匹配的Netoverlay主机中的最新链路无效或者不存在 · No device exists at either end or both ends of the latest links on the netoverlay hosts found by names of (hosts or access devices)：(主机/接入设备)名称匹配的Netoverlay主机中的最新链路对应的设备不存在 · No device exists at either end or both ends of the links found by names of (hosts or access devices)：(主机/接入设备)名称匹配的链路对应的设备不存在 · The interfaces of some links found by names of (hosts or access devices) are not AC interfaces：(主机/接入设备)名称对应的链路非AC口 · The destination host name for the migrating_to parameter cannot exceed 255 characters：migrating_to参数最长255个字符 · All OpenStack-based cloud platforms have been isolated：所有的云平台已被隔离 · No system VDS is specified：未指定系统虚拟分布式交换机 · The gateway list contains gateways that do not have members：出口网关列表中存在未配置成员的网关 · Invalid allowed address pair：无效的可用地址对 · Invalid running state：无效的运行状态 · The value for the binding:profile:cvk_host parameter can contain up to 255 characters：binding:profile:cvk_host最长255个字符 · The value for the binding:profile:esxi_host parameter can contain up to 255 characters：binding:profile:esxi_host最长255个字符 · You cannot set both the binding:profile:cvk_host and binding:profile:esxi_host parameters：不能同时设置binding:profile:cvk_host与binding:profile:esxi_host · The specified IP address has been configured as a protocol IP：虚拟端口IP已被子网协议IP使用 · Failed to create the vPort. A vPort cannot be assigned to an external network if it has extended SNAT IP addresses. To create the vPort, remove its extended SNAT IP addresses or specify an internal network for it：若指定的虚拟端口已配置扩展SNAT IP地址，则该端口必须属于外部网络 · The extended SNAT IP addresses must belong to an existing subnet：未找到扩展SNAT IP地址对应的子网 · You cannot configure extended SNAT IP addresses on the vPort, because the external network to which the vPort belongs is segmented：外部网络已开启网络分段，不允许配置扩展SNAT IP地址 · You cannot configure extended SNAT IP addresses for a vPort if the vPort does not have an IPv4 address：虚拟端口没有IPv4的地址时，不允许配置扩展SNAT IP地址 · You cannot specify an extended SNAT IP address as an IPv6 address：扩展SNAT IP地址不支持配置IPv6版本 · You cannot specify an extended SNAT IP address as the vPort IP address：扩展SNAT IP地址不能与虚拟端口IP地址冲突 · Make sure the extended SNAT IP addresses are not in the subnet of the primary IP address specified for the vNetwork：扩展SNAT IP地址不能在主IP所在子网内 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · You cannot bind a vPort to a subnet for primary IP allocation in an external network：虚拟端口不允许绑定外部网络下主IP所在子网 · Cannot delete vPorts created on VMM：不允许删除来源为VMM的虚拟端口 · You cannot apply a QoS policy to this vPort, because the vNetwork of this vPort has been specified for a PVLAN mapping：当虚拟端口所属的虚拟链路层网络已被PVLAN映射绑定，不允许绑定QoS策略 · The flooding domain must belong to the same tenant as the current user：泛洪域所属的租户与当前用户所绑定的租户不一致 · The vNetwork must belong to the same tenant as the current user：虚拟链路层网络所属的租户与当前用户所绑定的租户不一致 · The security policy must belong to the same tenant as the current user：安全策略所属的租户与当前用户所绑定的租户不一致 · The port group must belong to the same tenant as the current user：端口组所属的租户与当前用户所绑定的租户不一致 · A parent port and its subports must be configured with the same QoS profile：父端口和其子端口必须配置相同类型的QoS策略 · The IP address conflicts with the subnet address：IP地址和子网地址冲突 · The vPort IP address conflicts with the subnet broadcast address：虚拟端口IP地址与子网广播IP地址冲突 · Resource application or rollback failed, internal unknown error：资源申请或回滚失败，内部未知错误 · The（resource）does not exist or the resources are insufficient：（资源）不存在或资源不足 · The（resource）does not exist or the resources are insufficient, device group name（name）：（资源）不存在或资源不足，设备组名称（名称） · The （resource） does not exist or the resources are insufficient, resource access template name （name）：（资源）不存在或资源不足，资源接入模板名称（名称） · The value of binding:profile:agent_binary is invalid：binding:profile:agent_binary的值无效 |
|
关键字 |
UPDATE_PORT_OP |
|
日志内容 |
Updated vPort $1. |
|
参数解释 |
$1：虚拟端口的参数体 |
|
举例 |
Updated vPort { "id": "46d4bfb9-b26e-41f3-bd2e-e6dcc1ccedb2", "name": "11", "device id": "5e3898d7-11be-483e-9732-b2f5eccd2b2e", "device owner": "compute:nova", "network id": "6a21c566-692a-4214-a3a1-79eb654ba9ab", "tenant id": "4fd44f30-2929-45e4-81c7-b8a0c8908869", "fixed ips": [ { "ip address": "4.4.4.5", "subnet id": "8941dfed-517f-42e6-a56a-576e82efb740" } ], "binding:profile": { "enable_snat": true, "fw_enabled": "false", "migrating_to": "host1", "external snat ips": [] }, "binding host id": "hostname", "binding vif type": "none", "binding vnic type": "normal", "delete vlan map flag": false, "cloud region name": "default", "vlan": "2" } } |
|
日志说明 |
用户进行了修改虚拟端口的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The parameter (parameters) can't be modified：(parameters)参数不允许被修改 · Invalid port group ID：无效的端口组ID · The port group and the port don’t reside on the same network：端口组所在网络和虚拟端口所在网络不一致 · The default uplink port policy can’t be used as the port policy：端口策略不能使用缺省上行口策略 · The specified QoS policy doesn't exist：指定的QoS策略不存在 · Invalid port security policy UUID：无效的端口安全策略UUID · The mirror direction is required：未指定镜像方向 · The mirror type is required：未指定镜像类型 · Invalid mirror direction：无效的镜像方向 · Invalid mirror type：无效的镜像类型 · Invalid mirror remote IP：无效的镜像远端IP · The mirror remote IP is required：镜像远端IP不准确 · The port IP address must belong to an existing subnet：未找到IP地址对应的子网 · The IP address is already used by another port：该IP地址已被其他端口占用 · The port and the gateway can’t use the same IP address：端口IP地址和网关IP地址冲突 · Can’t update the MAC address：不能更新MAC地址 · The IP address must belong to the specified subnet：IP地址不在子网内 · The subnet must belong to the specified network：子网不在指定的虚拟链路层网络内 · Unknown error：未知错误 · The vPort is created through vCenter and the port group can't be modified：该端口由vCenter创建，不能通过本操作修改端口组 · The network doesn't exist：虚拟网络不存在 · The specified subnet doesn't exist：指定的虚拟子网不存在 · The specified resource doesn't exist：指定的资源不存在 · The length of the description is out of range：描述的长度超出范围 · Invalid APP cluster VIP：无效的应用集群虚IP · The APP cluster VIP and the vPort don't reside on the same network：应用集群虚IP所在网络和虚拟端口所在网络不一致 · The flooding domain and the vPort don't reside on the same network：泛洪域所在网络和虚拟端口所在网络不一致 · The vPort can be bound to a maximum of 10 flooding domains：vPort最多只能绑定10个泛洪域 · phy type auto created vPorts does not support editing IP address：phy类型南向自动创建端口不支持修改IP地址 · Invalid IP address：无效的IP地址 · The flooding domain doesn't exist：泛洪域不存在 · The host name cannot exceed 255 characters.：主机名最长255个字符 · APP cluster VIPs bound to the same vPort must belong to the same subnet：同一个虚拟端口上绑定的应用集群虚IP必须属于同一个子网 · The subnet to which the vPort belongs must be bound to a vRouter because the vPort has been bound to a routing table：vPort已绑定路由表时，vPort所在的子网必须绑定vRouter · The MAC address conflicts with the gateway MAC address， reserved gateway MAC address or device group MAC：MAC地址与网关MAC地址、保留的网关MAC地址或者设备组的MAC地址冲突 · Invalid MAC address：无效的MAC地址 · The vPort name cannot exceed 255 characters：虚拟端口名称最长255个字符 · Operation failed. The security policy rule failed to take effect because of insufficient hardware resources：操作失败，硬件资源不足导致安全策略规则无法生效 · The extend_dhcp_options field is invalid：无效的extend_dhcp_options · The value of the opt_name field is required：未指定DHCP选项名称 · The value of the opt_name field is invalid：无效的DHCP选项名称 · The value of the opt_value field is required：未指定DHCP选项值 · The value of the server-ip-address DHCP option is invalid：DHCP选项server-ip-address的选项值无效 · The value of the tftp-server DHCP option cannot exceed 63 characters：DHCP选项tftp-server的选项值最长63个字符 · The value of the bootfile-name DHCP option cannot exceed 127 characters：DHCP选项bootfile-name的选项值最长127个字符 · The values of the opt_name fields cannot be the same：DHCP选项名称不能重复 · The number of NTP server addresses cannot exceed 63：NTP服务器地址个数不能超过63个 · The NTP server address is invalid：无效的NTP服务器地址 · Duplicated NTP server addresses exist：NTP服务器地址列表中存在冲突的地址 · The fixed_ips field is required：fixed_ips不能为空 · The IP address of a vPort can be null only when the vPort resides on an external network or the subnet to which the vPort belongs is enabled with DHCP：仅当虚拟端口所属网络为外部网络或其所属子网使能DHCP功能时，端口IP地址才允许为空 · The vPort cannot have duplicated IP addresses：该虚拟端口的多个IP地址不能重复 · The vPort type is invalid：无效的虚拟端口类型 · The vPort type and the value of the device owner parameter do not match：虚拟端口的类型与设备拥有者的类型不匹配 · IP addresses in the subnet to which the vPort belongs are used up：该虚拟端口所属子网的IP地址已分配完 · vPorts do not support directly connected external networks：虚拟端口不支持独享型外部网络 · The value of the port_security_enabled is invalid：port_security_enabled参数非法 · A port group cannot be bound to a security policy when it contains port security disabled vPorts：虚拟端口未开启端口安全时，不允许该端口所属的端口组绑定安全策略 · A vPort with port security disabled cannot be bound to a security policy：虚拟端口未开启端口安全时，不允许绑定安全策略 · A vPort with port security disabled cannot be configured with allowed address pairs：虚拟端口未开启端口安全时，不允许配置可用地址对 · You have no privilege to perform this operation：用户无权限执行此操作 · The MAC address cannot contain all zeros or all Fs：MAC地址不能为全0或全F · A vPort name cannot start with "gateway"：虚拟端口名称不能以“gateway”开头 · Please enter an IP address for the external network vPort：外网虚拟端口IP不能为空 · Only OVS vPorts can be blocked：仅ovs类型的虚拟端口支持开启端口封堵 · You cannot bind a vPort to a subnet for primary IP allocation in an external network：虚拟端口不允许绑定外部网络下主IP所在子网 · The external subnet where the specified IP address resides has been bound to an NQA profile. You cannot assign the IP address to a vPort：指定IP地址所在的外网子网已关联NQA策略，无法绑定至虚拟端口 · Failed to edit the IP address for the vPort, because the new IP address is in a network bound to the context in another service chain：虚拟端口修改IP地址失败，该修改会导致虚拟端口所在特征组的服务链与其他服务链网段重叠 · The value for the fw_enabled parameter is invalid：无效的使能防火墙参数 · The vRouter-attached gateway members enable the third-party firewall option. Please enable or disable the firewall option across all IP addresses or subnets in the vRouter-attached external network if the egress of the external network is the firewall or border device, respectively：虚拟路由器绑定了第三方防火墙开启的设备组，该虚拟路由器绑定外部网络下的外网子网防火墙设置需要和虚拟路由器上的外网出口设置一致 · The vRouter-attached gateway members disable the third-party firewall option and use hairpin firewall deployment. Please make sure the firewall is enabled or disabled across all IP addresses and subnets in the external network：虚拟路由器绑定了第三方防火墙关闭且防火墙接入模式是旁挂的设备组，同外部网络下的外网子网过墙行为必须一致 · Failed to connect to (hosts or access devices). Host or access device IPs: {IP addresses}：(主机/接入设备){IP地址集合}连接失败 · The latest links are invalid or no links exist on the netoverlay hosts found by names of (hosts or access devices)：(主机/接入设备)名称匹配的Netoverlay主机中的最新链路无效或者不存在 · No device exists at either end or both ends of the latest links on the netoverlay hosts found by names of (hosts or access devices)：(主机/接入设备)名称匹配的Netoverlay主机中的最新链路对应的设备不存在 · No device exists at either end or both ends of the links found by names of (hosts or access devices)：(主机/接入设备)名称匹配的链路对应的设备不存在 · The interfaces of some links found by names of (hosts or access devices) are not AC interfaces：(主机/接入设备)名称对应的链路非AC口 · The destination host name for the migrating_to parameter cannot exceed 255 characters：migrating_to参数最长255个字符 · You cannot edit or delete the cloud region name：云区域名称不允许修改或删除 · All OpenStack-based cloud platforms have been isolated：所有的云平台已被隔离 · Invalid allowed address pair：无效的可用地址对 · You cannot edit the host ID or VLAN of a subport, because the transparent mode is enabled：透传模式开启时，子端口不允许修改host_id或者VLAN · Invalid running state：无效的运行状态 · The value for the binding:profile:cvk_host parameter can contain up to 255 characters：binding:profile:cvk_host最长255个字符 · The value for the binding:profile:esxi_host parameter can contain up to 255 characters：binding:profile:esxi_host最长255个字符 · You cannot set both the binding:profile:cvk_host and binding:profile:esxi_host parameters：不能同时设置binding:profile:cvk_host与binding:profile:esxi_host · The specified IP address has been configured as a protocol IP：虚拟端口IP已被子网协议IP使用 · You cannot specify an extended SNAT IP address as an IPv6 address：扩展SNAT IP地址不支持配置IPv6版本 · You cannot configure extended SNAT IP addresses on the vPort, because the external network to which the vPort belongs is segmented：外部网络已开启网络分段，不允许配置扩展SNAT IP地址 · You cannot specify an extended SNAT IP address as the vPort IP address：扩展SNAT IP地址不能与虚拟端口IP地址冲突 · You cannot specify the vPort IP address as extended SNAT IP address：虚拟端口IP地址不能与扩展SNAT IP地址冲突 · Make sure the extended SNAT IP addresses have not been used in the external network：相同外部网络下，扩展SNAT IP地址不能与已经存在的扩展SNAT IP地址或虚拟端口IP地址冲突 · You cannot specify an extended SNAT IP address as a gateway IP address in the same external network：扩展SNAT IP地址不能与子网网关IP地址冲突 · You cannot specify an extended SNAT IP address as a floating IP address in the same external network：扩展SNAT IP地址不能与浮动IP冲突 · Make sure the extended SNAT IP addresses are not in the subnet of the primary IP address specified for the vNetwork：扩展SNAT IP地址不能在主IP所在子网内 · You cannot configure extended SNAT IP addresses for a vPort if the vPort does not have an IPv4 address：虚拟端口没有IPv4的地址时，不允许配置扩展SNAT IP地址 · The extended SNAT IP addresses must belong to an existing subnet：未找到扩展SNAT IP地址对应的子网 · The vRouter does not contain information about the network segment associated with the subnet to which the new IP address belongs：虚拟路由器中不存在该IP版本子网对应的网络分段 · The external network specified for the vRouter is not segmented. You can bind only one IPv4 subnet and one IPv6 subnet to the vRouter：指定的外部网络未配置网络分段时，虚拟路由器只允许绑定一个IPv4和IPv6子网 · The vRouter is bound to multiple IPv4 and IPv6 external subnets. The network segments to which external subnets of the same IP version are bound cannot be bound to the same border gateway：虚拟路由器绑定多个的外网子网时，同IP版本外网子网对应的出口网关不能相同 · The external subnet is bound to the vRouter：外网子网已被虚拟路由器绑定 · The border gateways to the IPv4 and IPv6 external subnets are located on the same interface. You must configure them with the same segment ID：IPv4外网子网和IPv6外网子网的出口网关相同时，Segment ID必须相同 · The subnet overlaps with another subnet：子网与其他的子网重叠 · The vRouter context or external network vPort context has been used in a service chain：指定的虚拟路由器或外部网络虚拟端口已被服务链使用 · You cannot bind a vRouter to a vPort created by using a subnet for primary IP allocation：虚拟路由器不支持绑定使用主IP所在子网创建的虚拟端口 · The source IP address of a route entry on the vRouter cannot be within any external subnet on the vRouter：源IP地址不允许在同一虚拟路由器下外部网络的子网网段范围内 · You cannot bind the external subnet to the vRouter. The gateway address for the subnet is the next hop address of a route entry bound to the vRouter. You cannot bind them when the external subnet and that route entry are each bound to an NQA profile：虚拟路由器的路由表项的下一跳IP地址与外网子网网关IP相同，且路由表项已绑定NQA策略，则虚拟路由器不允许绑定配置了NQA策略的外部网络 · A vRouter cannot be bound to multiple IPv6 external network vPorts in the same network：虚拟路由器绑定多个IPv6外网虚拟端口时，这些端口所属的外部网络不能相同 · Subnets in the external network do not have sufficient IP addresses for allocation：外部网络下的子网可分配IP不足 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · The external network egress IP has been bound to another vRouter. To bind the current vRouter to the external network egress IP, you must make sure the current vRouter has exactly the same external subnet bindings as that vRouter：虚拟路由器绑定多个外网子网，且多个虚拟路由器共享外网IP时，必须同时共享所有外网IP · Failed to bind the router to the external network, because the external subnet does not have enough assignable IP addresses：绑定外网失败，外网子网没有可分配的IP地址 · Make sure all vRouters that use this sharing IP are bound to the same edge device for external network access：共享IP绑定的所有虚拟路由器的外网出口设备必须相同 · Invalid external IP binding. An external IP address has been bound to a minimum of one vRouter. To share that external IP address, the vRouters must be assigned the same service resources：该外网出口IP已被其他虚拟路由器绑定，如需共享，需确保共享该IP的所有虚拟路由器绑定相同的服务资源 · The external network egress IP has already been bound to a vRouter that uses different gateway resources from the current vRouter. Only vRouters that use the same gateway resources can share an external network egress IP：该外网出口IP已被其他虚拟路由器绑定，如需共享，需确保共享该IP的所有虚拟路由器绑定相同的网关资源 · Not enough addresses in subnets in network segment：网络分段内可分配IP不足 · You cannot remove the network segment, because it is used by multicast sources：指定的网络分段已被组播源使用，不允许解绑 · Failed to unbind the vRouter from the external network, because the vRouter and the external network (or a segment of the external network) have been bound to the same Layer 3 multicast network：解绑失败，L3组播使用了该虚拟路由器及其绑定的外部网络或网络分段 · You cannot bind the vRouter to an external network with a firewall specified as the edge device, because the external network has been bound to an MSDP peer：指定的外部网络已绑定MSDP对等体，不允许绑定外网出口设备为防火墙的虚拟路由器 · You cannot edit the IPv4 subnets or egress IPv4 address of the external network, because the default external vPort has extended SNAT IP addresses：默认外网端口已配置扩展SNAT IP地址，IPv4外网子网和外网出口IPv4地址不允许修改 · A vPort or application cluster VIP on the vRouter has been bound to a floating IP：该虚拟路由器下存在已绑定浮动IP的虚拟端口或应用集群虚IP · The vRouter to which the external network belongs is in a vRouter link, and a vPort on the peer vRouter of the vRouter link has been bound to the floating IP address of the external network：外部网络所属的虚拟路由器已建立虚拟路由器连接，且对端虚拟路由器下的虚拟端口已绑定了该外部网络的浮动IP · The external subnet has been bound to a context. Please access the context page to remove the binding first：该虚拟路由器的外网子网已关联流量特征组，请先前往流量特征组页面取消关联 · The context uses single gateway deployment mode. Make sure the associated vRouter is bound to one gateway member or external subnet：流量特征组为单出口模式时，关联的虚拟路由器必须绑定一个出口网关成员或一个外网子网 · The context uses primary/backup gateway deployment mode. Make sure the associated vRouter is bound to two gateway members or external subnets：流量特征组为主备出口模式时，关联的虚拟路由器必须绑定两个出口网关成员或两个外网子网 · The extranet IP is invalid：外网IP无效 · The IP address doesn't belong to the network：该IP地址不属于该网络 · The IP address doesn't belong to the subnet：指定的IP地址不属于该子网 · The extranet IP conflicts with a gateway IP：外网IP与网关IP冲突 · The extranet IP conflicts with the broadcast address of the subnet：外网IP地址和子网广播IP地址冲突 · The extranet IP conflicts with the subnet address：外网IP地址和子网地址冲突 · The extranet IP conflicts with a floating IP：外网IP与浮动IP冲突 · The external subnets of a vRouter cannot overlap with the networks manually specified for the vRouter link to which the vRouter belongs：外网子网网段不能与虚拟路由器所属的虚拟路由器连接的手动输入网段重叠 · Please make sure the firewall is enabled or disabled for both an external vPort and the vRouter bound to it：外网虚拟端口与所绑定的虚拟路由器过墙行为必须一致 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · You cannot disable firewall for the vPort if the vPort is already bound to an external transit vRouter：虚拟端口已绑定EXTERNALTRANSIT类型虚拟路由器，不允许关闭防火墙开关 · You must enable or disable firewall for a vPort if the following conditions exist:• The vPort is bound to an external transit vRouter.• The type of the border gateway bound to the vRouter is border device：虚拟端口已绑定外网出口设备为边界设备的EXTERNALTRANSIT类型虚拟路由器，不允许防火墙开关为空 · You cannot bind a vPort to a subnet for primary IP allocation in an external network：虚拟端口不允许绑定外部网络下主IP所在子网 · You cannot apply a QoS policy to this vPort, because the vNetwork of this vPort has been specified for a PVLAN mapping：当虚拟端口所属的虚拟链路层网络已被PVLAN映射绑定，不允许绑定QoS策略 · The cluster VIP must belong to the same tenant as the current user：应用集群虚IP所属的租户与当前用户所绑定的租户不一致 · The flooding domain must belong to the same tenant as the current user：泛洪域所属的租户与当前用户所绑定的租户不一致 · The security policy must belong to the same tenant as the current user：安全策略所属的租户与当前用户所绑定的租户不一致 · The port group must belong to the same tenant as the current user：端口组所属的租户与当前用户所绑定的租户不一致 · The vPort-attached external network has been bound to MSDP peers. You cannot enable the firewall feature or use a firewall as the edge device to the external network：指定虚拟端口对应的外部网络已绑定MSDP对等体，不允许开启防火墙或不允许外网出口设备为防火墙 · You cannot specify an extended SNAT IP address as a gateway IP address in the same external network：扩展SNAT IP地址不能与子网网关IP地址冲突 · Invalid interface names exist：存在无效的接口名称 · A parent port and its subports must be configured with the same QoS profile：父端口和其子端口必须配置相同类型的QoS策略 · The IP address conflicts with the subnet address：IP地址和子网地址冲突 · The vPort IP address conflicts with the subnet broadcast address：虚拟端口IP地址与子网广播IP地址冲突 · The external network egress IP is already bound to a vRouter. For vRouters to share this IP, make sure these vRouters use the same third-party firewall setting. You can configure this setting when you configure the device group associated with a gateway member of a border gateway bound to a vRouter：该外网出口IP已被其他虚拟路由器绑定，如需共享，需确保共享该IP的所有虚拟路由器绑定的出口网关对应的设备组第三方防火墙开关必须一致 · If multiple vRouters share an automatically created vPort, you cannot change the IP addresses of that vPort：当自动创建的外网虚拟端口被多个虚拟路由器绑定时，不允许修改其IP地址 · Invalid interface names exist：存在无效的接口名称 · Resource application or rollback failed, internal unknown error：资源申请或回滚失败，内部未知错误 · The（resource）does not exist or the resources are insufficient：（资源）不存在或资源不足 · The（resource）does not exist or the resources are insufficient, device group name（name）：（资源）不存在或资源不足，设备组名称（名称） · The （resource） does not exist or the resources are insufficient, resource access template name （name）：（资源）不存在或资源不足，资源接入模板名称（名称） · The value of binding:profile:agent_binary is invalid：binding:profile:agent_binary的值无效 |
|
关键字 |
DELETE_PORT_OP |
|
日志内容 |
Deleted vPort $1. |
|
参数解释 |
$1：虚拟端口的参数体 |
|
举例 |
Deleted vPort { "id": "46d4bfb9-b26e-41f3-bd2e-e6dcc1ccedb2", "name": "11", "device id": "5e3898d7-11be-483e-9732-b2f5eccd2b2e", "device owner": "compute:nova", "network id": "6a21c566-692a-4214-a3a1-79eb654ba9ab", "tenant id": "4fd44f30-2929-45e4-81c7-b8a0c8908869", "fixed ips": [ { "ip address": "4.4.4.5", "subnet id": "8941dfed-517f-42e6-a56a-576e82efb740" } ], "binding:profile": { "enable_snat": true, "fw_enabled": "false", "migrating_to": "host1", "external snat ips": [] }, "binding host id": "hostname", "binding vif type": "none", "binding vnic type": "normal", "delete vlan map flag": false, "cloud region name": "default", "vlan": "2" } } |
|
日志说明 |
用户进行了删除虚拟端口的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · Can't delete the port because it is created by vCenter：vCenter创建的端口，不能删除 · Can't delete the auto created LB vPort：不允许删除自动创建的LB类型的vPort · The specified resource doesn't exist：指定的资源不存在 · You cannot delete the gateway vPort：网关类型虚拟端口不允许删除 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 · Failed to connect to (hosts or access devices). Host or access device IPs: {IP addresses}：(主机/接入设备){IP地址集合}连接失败 · The latest links are invalid or no links exist on the netoverlay hosts found by names of (hosts or access devices)：(主机/接入设备)名称匹配的Netoverlay主机中的最新链路无效或者不存在 · No device exists at either end or both ends of the latest links on the netoverlay hosts found by names of (hosts or access devices)：(主机/接入设备)名称匹配的Netoverlay主机中的最新链路对应的设备不存在 · No device exists at either end or both ends of the links found by names of (hosts or access devices)：(主机/接入设备)名称匹配的链路对应的设备不存在 · The interfaces of some links found by names of (hosts or access devices) are not AC interfaces：(主机/接入设备)名称对应的链路非AC口 · The destination host name for the migrating_to parameter cannot exceed 255 characters：migrating_to参数最长255个字符 · All OpenStack-based cloud platforms have been isolated：所有的云平台已被隔离 · Can't delete the port because it has been bound to trunk：不允许删除已绑定端口中继的端口 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · Cannot delete vPorts created on VMM：不允许删除来源为VMM的虚拟端口 · Resource application or rollback failed, internal unknown error：资源申请或回滚失败，内部未知错误 · The（resource）does not exist or the resources are insufficient：（资源）不存在或资源不足 · The（resource）does not exist or the resources are insufficient, device group name（name）：（资源）不存在或资源不足，设备组名称（名称） · The （resource） does not exist or the resources are insufficient, resource access template name （name）：（资源）不存在或资源不足，资源接入模板名称（名称） |
|
关键字 |
DELETE_PORT_DEVCHECK_OP |
|
日志内容 |
Checked the state of southbound devices upon vPort deletion. |
|
参数解释 |
无 |
|
举例 |
Checked the state of southbound devices upon vPort deletion. |
|
日志说明 |
用户删除虚拟端口时，云插件校验了南向设备失联状态 |
|
失败原因 |
当操作失败时，可能的原因如下： · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
UPDATE_PORT_DEVCHECK_OP |
|
日志内容 |
Checked the state of southbound devices upon vPort update. |
|
参数解释 |
无 |
|
举例 |
Checked the state of southbound devices upon vPort update. |
|
日志说明 |
用户更新虚拟端口时，云插件校验了南向设备失联状态 |
|
失败原因 |
当操作失败时，可能的原因如下： · Failed to connect to {host/access_device}. Host or access device IPs: {IP addresses}：{主机/接入设备}{IP地址集合}连接失败 |
|
关键字 |
TAPFLOW_DEVCHECK_OP |
|
日志内容 |
Checked the state of southbound devices upon tap flow |
|
参数解释 |
无 |
|
举例 |
Checked the state of southbound devices upon tap flow |
|
日志说明 |
用户操作虚拟端口策略时，云插件校验了南向设备失联状态 |
|
失败原因 |
当操作失败时，可能的原因如下： · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
BIND_PORT_OP |
|
|
日志内容 |
Bound vPort $1. |
|
|
参数解释 |
$1：端口绑定的参数体 |
|
|
举例 |
Bound vPort { "port id":"1408326a-8b43-4343-83a7-0ef9214ad27e", "host name":"compute2", "tenant id":"91fb3087412f4718a0d99a9b6db6ac4c", "vlan segment":"90", "add vlan map flag":"true", "cloud region name":"zgb-t-openstack", "network id":"7ba2f880-50cc-4606-a97e-2a3376954734", }. |
|
|
日志说明 |
用户进行了绑定端口的操作 |
|
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · Unknown error：未知错误 · The specified vPort cannot be bound, because it does not meet the binding requirements：指定的虚拟端口不满足绑定条件，不允许绑定 · You have no privilege to perform this operation：用户无权限执行此操作 · Failed to connect to (hosts or access devices). Host or access device IPs: {IP addresses}：(主机/接入设备){IP地址集合}连接失败 · The latest links are invalid or no links exist on the netoverlay hosts found by names of (hosts or access devices)：(主机/接入设备)名称匹配的Netoverlay主机中的最新链路无效或者不存在 · No device exists at either end or both ends of the latest links on the netoverlay hosts found by names of (hosts or access devices)：(主机/接入设备)名称匹配的Netoverlay主机中的最新链路对应的设备不存在 · No device exists at either end or both ends of the links found by names of (hosts or access devices)：(主机/接入设备)名称匹配的链路对应的设备不存在 · The interfaces of some links found by names of (hosts or access devices) are not AC interfaces：(主机/接入设备)名称对应的链路非AC口 · The destination host name for the migrating_to parameter cannot exceed 255 characters：migrating_to参数最长255个字符 · All OpenStack-based cloud platforms have been isolated：所有的云平台已被隔离 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
|
关键字 |
CREATE_NETWORK_OP |
|
日志内容 |
Created network $1. |
|
参数解释 |
$1：虚拟链路层网络的参数体 |
|
举例 |
Created network { "id":"null", "name":"waiwang", "tenant id":"4fd44f30-2929-45e4-81c7-b8a0c8908869", "admin state up":"true", "router external":"false", "shared":"false", "network type":"vlan", "original network type":"null", "physical network":"public", "segmentation id":"3", "segment uuid":"null", "cloud region name":"openstack", "description":"null", "force flat":"false" }. |
|
日志说明 |
用户进行了创建虚拟链路层网络的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · Invalid tenant ID：无效的租户ID · The segment ID number is already used：Segment ID number已经被使用 · The segment ID is out of range：Segment ID超出范围 · The network's parameter is incorrect：虚拟网络参数错误 · The virtual network already exists：虚拟网络已存在 · Networks created in bulk cannot use the same ID：批量创建的虚拟路由器连接的ID存在重复 · The router doesn't exist：虚拟路由器不存在 · The router and network doesn't belong to the same tenant：虚拟链路层网络与虚拟路由器不属于同一个租户 · Failed to create the VXLAN because no available overlay license exists：Overlay license不可用，不能创建VXLAN类型的虚拟链路层网络 · Invalid broadcast suppression configuration：无效的广播报文抑制配置 · Invalid unknown multicast suppression configuration：无效的未知组播报文抑制配置 · Invalid unknown unicast suppression configuration：无效的未知单播报文抑制配置 · Unknown network type：未知的虚拟链路层网络类型 · The type of the network is different than the other networks in the tenant：同一个租户内只能创建一种类型的网络 · The ARP packet sending rate exceeds the rate limit：ARP报文发送速率超过速度限制 · The VDS doesn't exist：VDS不存在 · The number of DHCP servers on the DHCP relay agent can't exceed 8：DHCP服务器的IP地址数不能超过8个 · The IP address of the DHCP server is invalid：无效的DHCP服务器IP地址 · The IP address of the DHCP server is required：未指定DHCP服务器的IP地址 · External networks and VLANs do not support network sharing：外部网络或VLAN类型的网络不支持开启共享功能 · No available segment ID：没有可用的Segment ID · The network name cannot exceed 255 characters：虚拟链路层网络名称最长255个字符 · The specified tenant doesn't exist：指定的租户不存在 · Only external networks can be configured as flat networks：仅外部网络支持配置为Flat类型 · When the external network is a VXLAN, the value of the force_flat field cannot be false：当外部网络的类型为VXLAN时，force_flat不能为false · The segment ID of a flat network must be null：Flat类型网络的Segment ID必须为空 · The value of the force_flat field can be configured as true only when the network is an external network：仅外部网络支持配置force_flat为true · The value of the router:external field is required：router:external不能为空 · The value of the shared field is required：shared不能为空 · The value of the admin_state_up field is required：admin_state_up不能为空 · The value of the distributed field is required：distributed不能为空 · The value of the vswitch_flood_and_learn field is invalid：无效的vswitch_flood_and_learn · The specified tenant doesn't bind VDS：指定的租户没有绑定VDS · The VDS of the network is different than the tenant：虚拟链路层网络与租户的VDS不一致 · The provider field and the segment field cannot be both configured：provider字段和segments字段不能同时配置 · The flat type external network cannot be configured with segment：FLAT类型的外部网络不支持配置Segment · The ID already exists：ID已存在 · The value of the network type can only be VLAN：仅支持VLAN类型外网 · The network type is required：网络类型不能为空 · The segment ID is not in the VLAN pool：Segment ID不在VLAN池范围内 · physical network is required：physical_network字段不能为空 · The specified border gateway doesn't exist：指定的出口网关不存在 · You can create segments only for external networks：仅外部网络支持创建网络分段 · The segment name cannot exceed 255 characters：Segment名称最长255个字符 · The description cannot exceed 255 characters：描述信息最长255个字符 · Invalid segmentUUID：无效的 segmentUUID · The external network has been bound to a vRouter：外部网络已被虚拟路由器绑定 · Invalid segment ID：无效的segment ID · The value of the MTU must be an integer in the range of 68 to 65535：MTU必须为68～65535的整数 · The specified QoS policy doesn't exist：指定的QoS策略不存在 · Unknown error：未知错误 · Invalid value in the physical_network field：无效的physical_network字段 · A vNetwork cannot use directly connected mode：虚拟链路层网络不支持独享模式 · When the Network Cloud feature is disabled, directly connected external networks are not supported：网络云开关关闭时，不支持配置独享模式的外部网络 · Only internal network can be configured as resource operating mode：仅内部网络可配置为Resource工作模式 · You have no privilege to perform this operation：用户无权限执行此操作 · Cannot bind the DHCP host group to an external network：外部网络不支持绑定DHCP主机组 · The DHCP host group does not exist：指定的DHCP主机组不存在 · The RT generated based on the segment ID of the vNetwork conflicts with the import RT of a Layer 2 DC interconnect：虚拟链路层网络Segment ID生成的RT与数据中心二层互联的引入RT冲突 · The RT generated based on the segment ID of the vNetwork conflicts with the export RT of a Layer 2 DC interconnect：虚拟链路层网络Segment ID生成的RT与数据中心二层互联的引出RT冲突 · The RT generated based on the segment ID of the vNetwork conflicts with the import RT of a Layer 3 DC interconnect：虚拟链路层网络Segment ID生成的RT与数据中心三层互联的引入RT冲突 · The RT generated based on the segment ID of the vNetwork conflicts with the export RT of a Layer 3 DC interconnect：虚拟链路层网络Segment ID生成的RT与数据中心三层互联的引出RT冲突 · Invalid auto port creation configuration：无效的自动创建虚拟端口配置 · You cannot bind the DHCP host group to the vNetwork. A network node in the DHCP host group has already created a DHCP vPort for the vNetwork：DHCP主机组中的网络节点已存在虚拟链路层网络的DHCP虚拟端口，不允许绑定 · To disable preprovisioning, make sure all its dependent features use their default settings. For information about these features, see online help：当以下开关全部取值为默认时，预配置开关才允许关闭。ARP泛洪、ARP上送控制组件、RARP泛洪、RARP上送控制组件、DHCP上送控制组件、IPv6 NS/NA上送控制组件、IPv6 NS/NA泛洪、IPv6 RS/RA上送控制组件和DHCPv6上送控制组件 · Make sure the segment ID (VLAN ID) is not in a tenant carrier network VLAN pool and vRouter interconnection network VLAN pool when the external network or vNetwork type is VLAN：VLAN类型网络的VLAN ID不允许在租户承载网类型和虚拟路由器互通网络类型的VLAN池范围内 · You cannot change the status of the multicast network feature when the network segmentation feature is enabled：当外部网络开启网络分段开关时，不允许切换组播网络开关 · The external segment ID is already in use：External Segment ID 已经被使用 · The external segment ID is out of range：External Segment ID超出范围 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · You can enable external route redistribution only for external networks：仅外部网络支持配置引入外网路由开关 · You can enable external route redistribution only when the L3VNI is specified：仅L3VNI不为空时支持开启引入外网路由开关 · The segment ID cannot be identical to a VXLAN ID in a VXLAN pool or the VXLAN ID reserved for the automation template and the M-LAG system：Segment ID不能在VXLAN池范围内且不能和自动化模版、M-LAG系统的保留VXLAN ID重叠 · VLAN ID of VLAN type network is not allowed to conflict with M-LAG routed peer links border device VLAN ID：VLAN类型网络的VLAN ID不允许与M-LAG互联链路border设备互联VLAN冲突 · You must specify a valid VXLAN pool type when automatic allocation of L3VNIs for external networks is enabled：当自动分配外网L3VNI开关开启时VXLAN池类型不能为无效值 · vxlanPoolType cannot be vxlanPoolForL3vni or vdsPoolForL3vni when automatic allocation is not enabled：当自动分配外网L3VNI开关关闭时VXLAN池类型不能为VXLAN或VDS · Automatic allocation cannot be enabled when l3vni is exist：当外网L3VNI存在时不能开启自动分配外网L3VNI开关 · All OpenStack-based cloud platforms have been isolated：所有的云平台已被隔离 · No system VDS is specified：未指定系统虚拟分布式交换机 · The gateway list contains gateways that do not have members：出口网关列表中存在未配置成员的网关 · The gateway MAC cannot be a reserved MAC or device group MAC：网关MAC地址与系统保留MAC地址或设备组的MAC地址冲突 · The value for MAC address learning is invalid：无效的MAC地址学习开关 · The gateway MAC is invalid：无效的网关MAC地址 · Invalid transparent mode configuration：无效的透传模式配置 · You cannot enable LLDP-based vPort onboarding for the vNetwork, because automatic vPort creation has been enabled for the vNetwork：当前虚拟链路层网络已开启自动创建虚拟端口，不允许开启LLDP上线虚拟端口开关 · Invalid LLDP-based vPort onboarding configuration：无效的LLDP上线虚拟端口配置 · You cannot enable both LLDP-based vPort onboarding and automatic vPort creation for the vNetwork：虚拟链路层网络的LLDP上线虚拟端口和自动创建虚拟端口开关不能同时开启 · You cannot enable the IPv4 multicast network feature for a directly connected external network：独享型外部网络不支持开启IPv4组播网络开关 · You cannot enable network segmentation to a directly connected external network：外部网络的工作模式为独享时，不支持开启网络分段功能 · You cannot configure external segment ID to a directly connected external network：外部网络的工作模式为独享时，不支持配置External Segment ID · In a non-network cloud scenario, you cannot specify a borderinterface for the device group bound to a shared external network：非网络云场景，共享型外部网络不允许指定设备组的外网出口 · The value for the arp_mac_learning parameter is invalid：ARP MAC地址学习参数取值无效 · The value for the nd_mac_learning parameter is invalid：IPv6 ND MAC地址学习参数取值无效 · The RT generated based on the segment ID of the vNetwork conflicts with the import RT on a vRouter：虚拟链路层网络Segment ID生成的RT与虚拟路由器配置的引入RT冲突 · The RT generated based on the segment ID of the vNetwork conflicts with the export RT on a vRouter：虚拟链路层网络Segment ID生成的RT与虚拟路由器配置的引出RT冲突 · The RT generated based on the external segment ID of the external network conflicts with the import RT on a vRouter：外部网络External Segment ID生成的RT与虚拟路由器配置的引入RT冲突 · The RT generated based on the external segment ID of the external network conflicts with the export RT on a vRouter：外部网络External Segment ID生成的RT与虚拟路由器配置的引出RT冲突 · You cannot enable both route reduction and directly connected mode：路由精简开关与独享型工作模式不允许同时开启 · You cannot enable both route reduction and redistribution of external routes：路由精简开关与引入外网路由开关不允许同时开启 · In the network cloud scenario, you cannot enable route reduction for the external network：网络云场景下，不允许开启外部网络路由精简开关 · When network segmentation is enabled, you cannot enable route reduction for the external network：外部网络开启网络分段时，不允许开启外部网络路由精简开关 · Route reduction can be enabled only when the external network type is VLAN：仅VLAN类型外部网络允许开启路由精简开关 · When route reduction is enabled, you cannot enable network segmentation for the external network：外部网络开启路由精简开关时，不允许开启网络分段 · You cannot specify an external segment ID for a flat external network or vNetwork：Flat类型外部网络或者虚拟链路层网络的External Segment ID必须为空 · The RT generated based on the external segment ID of the external network is identical to the import RT of a Layer 2 DC interconnect：外部网络External Segment ID生成的RT与数据中心二层互联的引入RT冲突 · The RT generated based on the external segment ID of the external network is identical to the export RT of a Layer 2 DC interconnect：外部网络External Segment ID生成的RT与数据中心二层互联的引出RT冲突 · The RT generated based on the external segment ID of the external network is identical to the import RT of a Layer 3 DC interconnect：外部网络External Segment ID生成的RT与数据中心三层互联的引入RT冲突 · The RT generated based on the external segment ID of the external network is identical to the export RT of a Layer 3 DC interconnect：外部网络External Segment ID生成的RT与数据中心三层互联的引出RT冲突 · A vRouter and its attached external network must be bound to the same gateway：虚拟路由器的出口网关和外部网络的出口网关必须一致 · You cannot bind a gateway to a flat external network：FLAT类型外部网络不支持绑定出口网关 · You can bind only one gateway to an external network：外部网络只支持绑定一个出口网关 · The external network has been attached to a vRouter that has multiple gateways. You cannot specify a gateway for the external network：当虚拟路由器已绑定多个出口网关时，已绑定的外部网络不支持绑定出口网关 · You cannot both enable network segmentation and specify a gateway for an external network：外部网络的网络分段和出口网关冲突 · You cannot bind a border gateway to a directly connected external network：独享型外部网络不支持绑定出口网关 · In the network cloud scenario, you cannot bind a gateway to an external network：网络云场景下，外部网络不支持绑定出口网关 · You cannot bind the border gateway to the external network, because the external network has been bound to a vRouter and the border gateway is not bound to the vRouter：不允许外部网络配置出口网关，因为外部网络所绑定的虚拟路由器没绑定该出口网关 · You cannot bind a border gateway to the external network, because the external network has been bound to a vRouter and a border gateway bound to the vRouter has been configured with a priority：不允许外部网络配置出口网关，因为外部网络所绑定的虚拟路由器的该出口网关存在优先级 · When the type of an external network is FLAT, the operating mode of the external network cannot be Directly Connected：FLAT类型外部网络不支持配置独享型的工作模式 · The max rate of broadcasts must be an integer in the range of 64 to 167772159：广播报文最大速率范围必须为64～167772159的整数 · The primary_network_id field is a read-only field：primary_network_id为只读字段 · Cannot set the max rate of unknown unicasts when the value for the Unknown Unicast Suppression field is On or Default：未知单播报文泛洪抑制开关为开启或默认状态时，不允许配置未知单播报文最大速率 · The max rate of unknown unicasts must be an integer in the range of 64 to 167772159：未知单播报文最大速率范围必须为64～167772159的整数 · The segment ID cannot be identical to the VLAN ID configured for the M-LAG routed peer links between two border devices：Segment ID不能与边界设备的M-LAG互联链路下的VLAN ID冲突 · The max rate of unknown multicasts must be an integer in the range of 64 to 167772159：未知组播报文最大速率范围必须为64～167772159的整数 · Cannot set the max rate of broadcasts when the value for the Broadcast Suppression field is On or Default：广播报文泛洪抑制开关为开启或默认状态时，不允许配置广播报文最大速率 · Cannot set the max rate of unknown multicasts when the value for the Unknown Multicast Suppression field is On or Default：未知组播报文泛洪抑制开关为开启或默认状态时，不允许配置未知组播报文最大速率 · You cannot apply a QoS policy to this vNetwork, because this vNetwork has been specified for a PVLAN mapping：指定的虚拟链路层网络已被PVLAN映射绑定，不允许绑定QoS策略 · A parent port and its subports must be configured with the same QoS profile：父端口和其子端口必须配置相同类型的QoS策略 · Invalid value for the gateway disabling feature：无效的禁用网关 · After you enable the IPv4 multicast network feature for the external network, you cannot select a gateway whose firewall deployment mode is off and method to deploy basic external connectivity settings is manual, and vice versa：外部网络不允许同时开启IPv4组播网络和绑定设备组防火墙接入模式为关闭且外网转发基础配置为手动预配置的出口网关 · After you select a gateway whose firewall deployment mode is off and method to deploy basic external connectivity settings is manual, you cannot enable OSPF for the external network, and vice versa：外部网络不允许同时配置OSPF路由协议和绑定设备组防火墙接入模式为关闭且外网转发基础配置为手动预配置的出口网关 · After you bind to the external network a gateway whose firewall deployment mode is off and method to deploy basic external connectivity settings is manual, you cannot configure any NQA profile-subnet bindings, and vice versa：外部网络不允许同时配置子网绑定NQA策略和绑定设备组防火墙接入模式为关闭且外网转发基础配置为手动预配置的出口网关 · After you bind to the external network a gateway whose firewall deployment mode is off and method to deploy basic external connectivity settings is manual, you cannot enable primary IP allocation for any subnets, and vice versa：外部网络不允许同时开启子网主IP所在子网和绑定设备组防火墙接入模式为关闭且外网转发基础配置为手动预配置的出口网关 · After you select a gateway whose firewall deployment mode is off and method to deploy basic external connectivity settings is manual, you must configure a segment ID for the external network：当外部网络绑定设备组防火墙接入模式为关闭且外网转发基础配置为手动预配置的出口网关时，必须配置External Segment ID · When a vRouter has been bound to the external network, the external subnets cannot overlap with the subnet for firewall access：外部网络已被虚拟路由器绑定时，外网子网与防火墙接入网段重叠 · The external network is bound to a gateway whose firewall deployment mode is off and method to deploy basic external connectivity settings is manual. You must configure a segment ID：当外部网络绑定设备组防火墙接入模式为关闭且外网转发基础配置为手动预配置的出口网关时，External Segment ID不允许配置为空 · A vRouter that has border gateway bindings is bound to the external network. You cannot bind to the external network a gateway whose firewall deployment mode is off and method to deploy basic external connectivity settings is manual：外部网络已被虚拟路由器绑定且该虚拟路由器绑定了出口网关时，外部网络不允许绑定设备组防火墙接入模式为关闭且外网转发基础配置为手动预配置出口网关 · A vRouter that has a non-service leaf firewall binding is bound to the external network. You cannot bind a gateway whose firewall deployment mode is off to the external network：外部网络已被虚拟路由器绑定且该虚拟路由器绑定了非Service Leaf类型的防火墙时，不允许绑定设备组防火墙接入模式为关闭的出口网关 · When you bind an external subnet to the vRouter, the subnet cannot overlap with the access subnet for the firewall associated with the vRouter：虚拟路由器绑定外网子网时，该外网子网与防火墙接入网段不能重叠 · DHCPv6 valid lifetime is beyond the value range：DHCPv6有效生命期值超出了范围限制 · DHCPv6 preferred lifetime is beyond the value range：DHCPv6首选生命期值超出了范围限制 · The DHCPv6 preferred lifetime must be less than or equal to the DHCPv6 valid lifetime：DHCPv6首选生命期值需要小于等于DHCPv6有效生命期值 · If the DHCPv6 preferred lifetime is 0, the DHCPv6 valid lifetime must also be 0：DHCPv6首选生命期值为0时，DHCPv6有效生命期值必须为0 · If the type of an external network is directly connected, you cannot enable the IPv6 multicast network feature for that external network：独享型外部网络不支持开启IPv6组播网络开关 · After you enable the IPv6 multicast network feature for the external network, you cannot select a gateway whose firewall deployment mode is off and method to deploy basic external connectivity settings is manual, and vice versa：外部网络不允许同时开启IPv6组播网络和绑定设备组防火墙接入模式为关闭且外网转发基础配置为手动预配置的出口网关 · Resource application or rollback failed, internal unknown error：资源申请或回滚失败，内部未知错误 · The（resource）does not exist or the resources are insufficient：（资源）不存在或资源不足 · The（resource）does not exist or the resources are insufficient, device group name（name）：（资源）不存在或资源不足，设备组名称（名称） · The （resource） does not exist or the resources are insufficient, resource access template name （name）：（资源）不存在或资源不足，资源接入模板名称（名称） · When adding a VLAN-type external network, make sure the segment ID is not in the VLAN range of any global VLAN-VXLAN mappings：VLAN类型的外部网络创建时，不允许Segment ID值在全局VLAN-VXLAN映射的VLAN范围内 · Cannot allocate this external segment ID, because synchronization is in progress for the VXLAN pool containing this external segment ID：无法分配该External Segment ID，其所在的VXLAN池正在平滑中 · The value of the vSwitch Flooding field is invalid：无效的虚拟交换机泛洪 · The value of the vSwitch Learning field is invalid：无效的虚拟交换机自学习 |
|
关键字 |
DELETE_NETWORK_OP |
|
日志内容 |
Deleted network $1. |
|
参数解释 |
$1：虚拟链路层网路的参数体 |
|
举例 |
Deleted network { "id":"null", "name":"waiwang", "tenant id":"4fd44f30-2929-45e4-81c7-b8a0c8908869", "admin state up":"true", "router external":"false", "shared":"false", "network type":"vlan", "original network type":"null", "physical network":"public", "segmentation id":"3", "segment uuid":"null", "cloud region name":"openstack", "description":"null", "force flat":"false" }. |
|
日志说明 |
用户进行了删除虚拟链路层网络的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · Can’t delete the network because a port resides on the network：此网络正在被端口使用，不允许删除 · Can’t delete the network because a port group resides on the network：此网络正在被端口组使用，不允许删除 · The network contains a subnet：虚拟网络存在子网 · The specified resource doesn't exist：指定的资源不存在 · The port group has not been unbound from the subnet：请先删除端口组 · The subnet has not been unbound from the router：请先解除和虚拟路由器的绑定关系 · A port resides on the subnet：虚拟子网存在端口 · Can't delete the network because the network has flooding domains：虚拟链路层网络下存在泛洪域，不允许删除 · The network has been bound to a Layer 2 DC interconnection：虚拟链路层网络已被数据中心二层互联绑定 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · Cannot delete the vNetwork because it has been bound to an OSPF or OSPFv3 policy：虚拟链路层网络已被OSPF或OSPFv3策略绑定 · All OpenStack-based cloud platforms have been isolated：所有的云平台已被隔离 · You cannot delete the vNetwork, because it has been bound to a Layer 2 multicast network：删除虚拟链路层网络失败，该虚拟链路层网络已经绑定了L2组播 · Cannot delete the vNetwork because it is being used by a System Center VM network：虚拟链路层网络已被VM网络使用，不允许删除 · Cannot delete the vNetwork because it is being used by a vCenter port group：虚拟链路层网络已被分布式端口组使用，不允许删除 · You cannot delete the external network, because it is bound to a Layer 3 multicast network：指定的外部网络已绑定L3组播，不允许删除 · You cannot delete a vNetwork with the source as PVLAN：不允许删除来源为PVLAN的虚拟链路层网络 · Cannot delete the vNetwork because it has been bound to an OSPF or OSPFv3 policy application：虚拟链路层网络已绑定OSPF策略，不允许删除 · Cannot delete the vNetwork because it is being used by a rhvm logical network：虚拟链路层网络已被逻辑网络使用，不允许删除 · Resource application or rollback failed, internal unknown error：资源申请或回滚失败，内部未知错误 · The（resource）does not exist or the resources are insufficient：（资源）不存在或资源不足 · The（resource）does not exist or the resources are insufficient, device group name（name）：（资源）不存在或资源不足，设备组名称（名称） · The （resource） does not exist or the resources are insufficient, resource access template name （name）：（资源）不存在或资源不足，资源接入模板名称（名称） |
|
关键字 |
DELETE_NETWORK_DEVCHECK_OP |
|
日志内容 |
Checked the state of southbound devices upon vNetwork deletion. |
|
参数解释 |
无 |
|
举例 |
Checked the state of southbound devices upon vNetwork deletion. |
|
日志说明 |
用户删除虚拟链路层网络时，云插件校验了南向设备失联状态 |
|
失败原因 |
当操作失败时，可能的原因如下： · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
CREATE_MIRROR_DESTINATION_PROFILE_OP |
|
日志内容 |
Created mirroring destination template: $1. |
|
参数解释 |
$1：镜像目的模板的信息 |
|
举例 |
Created tap mirroring destination template { "id":"c352f537-ad49-48eb-ab05-1c6b8cb900ff", "name":"tap1", "tenant_id":"6883573e-ba4e-4fd5-8df5-f59b6c365b5b", "description":"", "port_id":"c9beb5a1-21f5-4225-9eaf-02ddccdd50a9", "remote_v4ip":"192.122.222.8", "cloud_region_name":"openstack" }. |
|
日志说明 |
用户进行了创建镜像目的模板的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service does not exist：服务不存在 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · The name is required and cannot exceed 255 characters：名称必选并且长度不能超过255个字符 · Failed to add the configuration item：添加配置项失败 · You have no privilege to perform this operation：用户无权限执行此操作 · All OpenStack-based cloud platforms have been isolated：所有的云平台已被隔离 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · Invalid vrf：无效的VRF |
|
关键字 |
UPDATE_MIRROR_DESTINATION_PROFILE_OP |
|
日志内容 |
Updated mirroring destination template: $1. |
|
参数解释 |
$1：镜像目的模板的信息 |
|
举例 |
Updated mirroring destination template { "id":"c352f537-ad49-48eb-ab05-1c6b8cb900ff", "name":"tap1", "tenant_id":"6883573e-ba4e-4fd5-8df5-f59b6c365b5b", "description":"", "port_id":"c9beb5a1-21f5-4225-9eaf-02ddccdd50a9", "remote_v4ip":"192.122.222.8", "cloud_region_name":"openstack" }. |
|
日志说明 |
用户进行了修改镜像目的模板的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service does not exist：服务不存在 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · The configuration item does not exist：配置项不存在 · The name is required and cannot exceed 255 characters：名称必选并且长度不能超过255个字符 · Failed to modify the configuration item：修改配置项失败 · You have no privilege to perform this operation：用户无权限执行此操作 · All OpenStack-based cloud platforms have been isolated：所有的云平台已被隔离 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
DELETE_MIRROR_DESTINATION_PROFILE_OP |
|
日志内容 |
Deleted mirroring destination template $1. |
|
参数解释 |
$1：镜像目的模板的信息 |
|
举例 |
Deleted mirroring destination template { "id":"c352f537-ad49-48eb-ab05-1c6b8cb900ff", "name":"tap1", "tenant_id":"6883573e-ba4e-4fd5-8df5-f59b6c365b5b", "description":"", "port_id":"c9beb5a1-21f5-4225-9eaf-02ddccdd50a9", "remote_v4ip":"192.122.222.8", "cloud_region_name":"openstack" }. |
|
日志说明 |
用户进行了删除镜像目的模板的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service does not exist：服务不存在 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · The configuration item does not exist：配置项不存在 · The specified mirroring destination profile is used：指定的镜像目的模板已经被使用 · You have no privilege to perform this operation：用户无权限执行此操作 · All OpenStack-based cloud platforms have been isolated：所有的云平台已被隔离 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
CREATE_MIRRORING_PROFILE_OP |
|
日志内容 |
Created mirroring profile $1. |
|
参数解释 |
$1：虚拟端口策略的参数体 |
|
举例 |
Created mirroring profile { "id":"cc47f881-345f-4e62-ad24-bea79eb28304", "name":"flow1", "tenant_id":"2b2151a2-f111-40f0-a0ea-61a76879e972", "description":"", "source_port":"d396a0e8-d89a-40d7-9f86-b7cb8ee96905", "destination_v4ip_prefix":"1.2.5.0/24", "tap_service_id":"1a97a957-b4f4-431e-94f3-38a25c82b158", "direction":"OUT", "cloud_region_name":"openstack" }. |
|
日志说明 |
用户进行了创建镜像的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service does not exist：服务不存在 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · The default VXLAN is required：未设置默认VXLAN · The name is required and cannot exceed 255 characters：名称必选并且长度不能超过255个字符 · The description cannot exceed 255 characters：描述信息字段最长255个字符 · The vPort is required：未指定虚拟端口 · The vPort cannot be the same as the vPort in the mirroring destination profile：虚拟端口和镜像目的模板下的虚拟端口不允许相同 · Failed to add the configuration item：添加配置项失败 · No available VXLAN IDs：VXLAN ID已用尽 · The specified mirroring destination profile does not exist：指定的镜像目的模板不存在 · No VXLAN resources are configured, or VXLAN resources have been used up：VXLAN资源未配置或已用尽 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · All OpenStack-based cloud platforms have been isolated：所有的云平台已被隔离 |
|
关键字 |
UPDATE_MIRRORING_PROFILE_OP |
|
日志内容 |
Updated mirroring profile $1. |
|
参数解释 |
$1：镜像的参数体 |
|
举例 |
Updated mirroring profile { "id":"cc47f881-345f-4e62-ad24-bea79eb28304", "name":"flow1", "tenant_id":"2b2151a2-f111-40f0-a0ea-61a76879e972", "description":"", "source_port":"d396a0e8-d89a-40d7-9f86-b7cb8ee96905", "destination_v4ip_prefix":"1.2.5.0/24", "tap_service_id":"1a97a957-b4f4-431e-94f3-38a25c82b158", "direction":"OUT", "cloud_region_name":"openstack" }. |
|
日志说明 |
用户进行了修改镜像的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service does not exist：服务不存在 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · The configuration item does not exist：配置项不存在 · The default VXLAN is required：未设置默认VXLAN · The name is required and cannot exceed 255 characters：名称必选并且长度不能超过255个字符 · The description cannot exceed 255 characters：描述信息字段字段最长255个字符 · The vPort cannot be edited：虚拟端口不允许修改 · The VXLAN ID cannot be modified：VXLAN ID不允许修改 · The vPort cannot be the same as the vPort in the mirroring destination profile：虚拟端口和镜像目的模板下的虚拟端口不允许相同 · Failed to modify the configuration item：修改配置项失败 · All OpenStack-based cloud platforms have been isolated：所有的云平台已被隔离 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
DELETE_MIRRORING_PROFILE_OP |
|
日志内容 |
Deleted mirroring profile $1. |
|
参数解释 |
$1：镜像的参数体 |
|
举例 |
Deleted mirroring profile { "id":"cc47f881-345f-4e62-ad24-bea79eb28304", "name":"flow1", "tenant_id":"2b2151a2-f111-40f0-a0ea-61a76879e972", "description":"", "source_port":"d396a0e8-d89a-40d7-9f86-b7cb8ee96905", "destination_v4ip_prefix":"1.2.5.0/24", "tap_service_id":"1a97a957-b4f4-431e-94f3-38a25c82b158", "direction":"OUT", "cloud_region_name":"openstack" }. |
|
日志说明 |
用户进行了删除镜像的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service does not exist：服务不存在 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · The configuration item does not exist：配置项不存在 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · All OpenStack-based cloud platforms have been isolated：所有的云平台已被隔离 |
|
关键字 |
CREATE_BGP_NEIGHBOR_OP |
|
日志内容 |
Created BGP neighbor $1. |
|
参数解释 |
$1：BGP邻居的参数体 |
|
举例 |
Created BGP neighbor { "bgpneighbor_id":"b3848485-eff1-427f-a012-f1fff28c65c8", "name":"bgpn_example", "description":"", "tenant_id":"6883573e-ba4e-4fd5-8df5-f59b6c365b5b", "router_id":"2f5d01a1-1cef-4067-9280-f6dcf086b43c", "exsubnet_id":"null", "local_as_number":"1", "ip_version":"4", "peer_ip_address":"1.1.1.1", "peer_as_number":"2", "suppress":"true", "source_ips":"[2.2.2.2]", "cloud_region_name":"openstack" }. |
|
日志说明 |
用户进行了创建BGP邻居的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · Invalid JSON format：无效的JSON格式 · The service is disabled：服务未启动 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Invalid parameter：无效参数 · Unknown internal server error：未知的内部服务器错误 · A name is required for the BGP instance：BGP实例的名称不允许为空 · A tenant ID is required：租户ID不允许为空 · A router ID is required for the BGP instance：BGP实例的Router ID不允许为空 · Specify either a source IP address or an external subnet ID：指定源IP地址和外部子网ID只允许填一个 · A local AS number is required：本地AS号不允许为空 · Invalid local AS number：无效的本地AS号 · Invalid IP version：无效的IP版本 · The IP address of the BGP peer must be the same version as the source IP address：BGP对等体的IP地址必须和源IP地址版本一致 · An AS number is required for the BGP peer：BGP对等体的AS号不允许为空 · The AS number of the BGP peer is invalid：BGP对等体的AS号无效 · The BGP peer UUID already exists：指定的BGP对等体ID已存在 · An IP address is required for the BGP peer：BGP对等体的IP地址不允许为空 · The source IP address or external subnet ID is invalid：源IP地址或者外部子网ID无效 · A name is required：未指定name · A UUID is required for the BGP peer：BGP对等体的ID不允许为空 · An external subnet ID is required：外部子网的ID不允许为空 · An IP version is required：IP版本不允许为空 · The IP address of the BGP peer is invalid：无效的BGP对等体的IP地址 · An IP address is required for the BGP peer：BGP对等体的IP地址不允许为空 · An AS number is required for the BGP peer：BGP对等体的AS号不允许为空 · The specified BGP peer has already been bound to the vRouter：指定的虚拟路由器下已经绑定了BGP对等体 · The specified subnet is not an external subnet：指定的子网不是外网类型 · The connection type of the external network must be Directly Connected：外部网络的模式必须为独享模式 · The external subnet type must be VLAN：外网子网的类型必须是VLAN类型 · The specified external subnet has not been bound to a vRouter：指定UUID的外网子网没有绑定虚拟路由器 · The vRouter to which the external subnet is bound is different from the vRouter specified by the router_id parameter：外网子网对应的虚拟路由器和router_id对应的虚拟路由器不一致 · When the HA mode is multi-active, you must specify two different source IP addresses for the BGP neighbor：HA部署模式为多活时，BGP邻居的源IP地址最多只能配置两个，且不能相同 · You have no privilege to perform this operation：用户无权限执行此操作 · When the Network Cloud feature is disabled, you cannot create BGP peers：网络云开关关闭时，不允许创建BGP邻居 · BGP peer with the specified IP address already exists：指定BGP对等体的IP地址已存在 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · Up to 255 characters, case sensitive：参数不能超过255个字符，区分大小写 · All OpenStack-based cloud platforms have been isolated：所有的云平台已被隔离 · The password is case sensitive and cannot exceed 80 characters. Only letters, digits, and special characters except for question marks (?) are supported：密码长度最长80个字符，区分大小写，仅支持英文、数字和特殊字符（英文问号除外） · When you configure a border interface in a non-network cloud scenario, you must specify a minimum of one external subnet：非网络云场景外部子网不能为空 · When you configure a BGP neighbor in a non-network cloud scenario, you cannot specify a source IP：非网络云场景不允许指定源IP · In a non-network cloud scenario, you cannot disable BGP route advertisement to the controller：非网络云场景，不支持配置抑制BGP路由发布到DC开关 · In a non-network cloud scenario, you cannot bind both a BGP peer and a BGP neighbor to a vRouter if the peer IP address configured for the BGP neighbor is the same as the neighbor IP/network address configured for the BGP peer：非网络云场景，同一个虚拟路由器下，BGP邻居的对端对等体IP与BGP对等体IP地址/网段不能重叠 · BFD cannot be enabled in the network cloud scenario：网络云场景下，不支持开启BFD探测功能 · In the network cloud scenario, BGP neighbors do not support binding interconnect interfaces：网络云场景BGP邻居不支持绑定互联接口 · You must bind an interconnect interface or an external subnet to a BGP neighbor：BGP邻居必须绑定外部子网和互联接口其中之一 · The specified interconnect interface does not exist：互联接口不存在 · When you bind an interconnect interface to a BGP neighbor, make sure the interconnect interface has a border gateway binding：BGP邻居绑定的互联接口未绑定出口网关 · When you bind an interconnect interface to a BGP neighbor, make sure the border gateway associated with that interconnect interface has a vRouter binding：BGP邻居绑定的互联接口关联的出口网关未绑定虚拟路由器 |
|
关键字 |
UPDATE_BGP_NEIGHBOR_OP |
|
日志内容 |
Updated BGP neighbor $1. |
|
参数解释 |
$1：BGP邻居的参数体 |
|
举例 |
Updated BGP neighbor { "bgpneighbor_id":"b3848485-eff1-427f-a012-f1fff28c65c8", "name":"bgpn_example", "description":"", "tenant_id":"6883573e-ba4e-4fd5-8df5-f59b6c365b5b", "router_id":"2f5d01a1-1cef-4067-9280-f6dcf086b43c", "exsubnet_id":"null", "local_as_number":"1", "ip_version":"4", "peer_ip_address":"1.1.1.1", "peer_as_number":"2", "suppress":"true", "source_ips":"[2.2.2.2]", "cloud_region_name":"openstack" }. |
|
日志说明 |
用户进行了修改BGP邻居的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · Invalid JSON format：无效的JSON格式 · The service is disabled：服务未启动 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Invalid parameter：无效参数 · Unknown internal server error：未知的内部服务器错误 · The BGP peer UUID does not exist：BGP对等体的ID不存在。 · The BGP peer UUID cannot be modified：BGP对等体的ID不允许修改。 · The tenant ID cannot be modified：租户的ID不允许修改。 · The router ID of the BGP instance cannot be modified：BGP实例的Router ID不允许修改。 · The local AS number cannot be modified：本地AS号不允许修改。 · The IP version cannot be modified：IP版本不允许修改。 · The IP address of the BGP peer cannot be modified：BGP对等体的IP地址不允许修改。 · The AS number of the BGP peer cannot be modified：BGP对等体的AS号不允许修改。 · You have no privilege to perform this operation：用户无权限执行此操作 · When the Network Cloud feature is disabled, you cannot edit BGP peers：网络云开关关闭时，不允许修改BGP邻居 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · You cannot edit or delete the cloud region name：云区域名称不允许修改或删除 · Up to 255 characters, case sensitive：参数不能超过255个字符，区分大小写 · All OpenStack-based cloud platforms have been isolated：所有的云平台已被隔离 · The password is case sensitive and cannot exceed 80 characters. Only letters, digits, and special characters except for question marks (?) are supported：密码长度最长80个字符，区分大小写，仅支持英文、数字和特殊字符（英文问号除外） · When you configure a border interface in a non-network cloud scenario, you must specify a minimum of one external subnet：非网络云场景外部子网不能为空 · When you configure a BGP neighbor in a non-network cloud scenario, you cannot specify a source IP：非网络云场景不允许指定源IP · In a non-network cloud scenario, you cannot disable BGP route advertisement to the controller：非网络云场景，不支持配置抑制BGP路由发布到DC开关 · In a non-network cloud scenario, you cannot bind both a BGP peer and a BGP neighbor to a vRouter if the peer IP address configured for the BGP neighbor is the same as the neighbor IP/network address configured for the BGP peer：非网络云场景，同一个虚拟路由器下，BGP邻居的对端对等体IP与BGP对等体IP地址/网段不能重叠 · BFD cannot be enabled in the network cloud scenario：网络云场景下，不支持开启BFD探测功能 · You cannot change the interconnect interface binding of a BGP neighbor：BGP邻居绑定的互联接口不允许修改 |
|
关键字 |
DELETE_BGP_NEIGHBOR_OP |
|
日志内容 |
Deleted BGP neighbor $1. |
|
参数解释 |
$1：BGP邻居的参数体 |
|
举例 |
Deleted BGP neighbor { "bgpneighbor_id":"b3848485-eff1-427f-a012-f1fff28c65c8", "name":"bgpn_example", "description":"", "tenant_id":"6883573e-ba4e-4fd5-8df5-f59b6c365b5b", "router_id":"2f5d01a1-1cef-4067-9280-f6dcf086b43c", "exsubnet_id":"null", "local_as_number":"1", "ip_version":"4", "peer_ip_address":"1.1.1.1", "peer_as_number":"2", "suppress":"true", "source_ips":"[2.2.2.2]", "cloud_region_name":"openstack" }. |
|
日志说明 |
用户进行了删除BGP邻居的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid license：无效的License · Invalid JSON format：无效的JSON格式 · The service is disabled：服务未启动 · Configuration recovery is in progress：配置正在恢复过程中 · The controller is not the active leader：该控制组件不是主Leader · Invalid parameter：无效参数 · Unknown internal server error：未知的内部服务器错误 · The BGP peer UUID does not exist：BGP对等体的ID不存在 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · All OpenStack-based cloud platforms have been isolated：所有的云平台已被隔离 |
|
关键字 |
CREATE_ROUTE_ENTITY_OP |
|
日志内容 |
Created route entities $1 |
|
参数解释 |
$1：路由表项的参数体 |
|
举例 |
Created route entities { "id":"null", "destination":"10.10.0.0/16", "nexthop":"12.3.3.3", "type":"401", "ip_version":"4", "source_ips":"[1.0.0.2]", "bfd":"true", "routetable_id":"b930d7f6-ceb7-40a0-8b81-a425dd994ccf", "cloud_region_name":"openstack" },{ "id":"null", "destination":"11.11.0.0/16", "nexthop":"13.3.3.3", "type":"401", "ip_version":"4", "source_ips":"[1.0.0.2]", "bfd":"true", "routetable_id":"b930d7f6-ceb7-40a0-8b81-a425dd994ccf", "cloud_region_name":"openstack" }. |
|
日志说明 |
用户进行了创建路由表项的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The route has already existed：该路由已存在 · Invalid next hop：无效的下一跳 · Invalid CIDR：无效的CIDR · Invalid routing table ID：无效的路由表ID · Invalid next hop type：无效的下一跳类型 · The destination subnet of the route entry overlaps with the subnet bound to the interface of the vRouter：路由表项中的目的网段与虚拟路由器接口的子网网段重叠 · The specified device doesn't exist：指定的设备不存在 · The device ID and the device name do not match：设备的ID和名称不匹配 · Duplicate devices exist：设备列表中存在重复的设备 · The specified next hop vRouter does not exist：下一跳虚拟路由器不存在 · When the next hop type is Blackhole, the next hop is not required：当下一跳类型为黑洞时，不需配置下一跳 · When the next hop type is Blackhole, the value of the host route recursion parameter must be false：当下一跳类型为黑洞时，迭代主机路由参数必须为false · When the next hop type is Blackhole, the next hop vRouter is not required：当下一跳类型为黑洞时，不需配置下一跳虚拟路由器 · Unknown error：未知错误 · The route entries cannot be created on edge devices：路由表项中的设备不支持ED设备 · Can't specify a vRouter whose origin is PBR：不允许指定来源为PBR的虚拟路由器 · The first BFD source IP address in a route entry cannot be the same as the second BFD source IP address in another route entry, and vice versa：路由表中存在配置了BFD源IP地址2的路由表项时，该表项的BFD源IP地址2不能与其他表项的BFD源IP地址1相同 · The first BFD source IP address in a route entry cannot be the same as the second source IP address of a BGP peer bound to the same vRouter as the route entry, and vice versa：对于绑定同一个虚拟路由器的路由表和BGP邻居，路由表中路由表项的BFD源IP地址1不能与BGP邻居的源IP地址2相同，反之，BGP邻居的源IP地址1也不能与路由表中路由表项的BFD源IP地址2相同 · The source IP address of a route entry with a vPort-type next hop on the vRouter cannot overlap with any vNetwork subnet on another vRouter：建立虚拟路由器连接的两个虚拟路由器，一个虚拟路由器下虚拟端口类型的路由表项的源IP不允许和另一个虚拟路由器下虚拟链路层网络的子网重叠 · The source IP address of a route entry with a vPort-type next hop on the vRouter cannot overlap with any external subnet on another vRouter：建立虚拟路由器连接的两个虚拟路由器，一个虚拟路由器下虚拟端口类型的路由表项的源IP不允许和另一个虚拟路由器下外部网络的子网重叠 · The source IP address of a route entry with a vPort-type next hop on the vRouter cannot be the same as any vNetwork subnet gateway IP of another vRouter：建立虚拟路由器连接的两个虚拟路由器，一个虚拟路由器下虚拟端口类型的路由表项的源IP不允许和另一个虚拟路由器下虚拟链路层网络子网的网关IP地址相同 · The source IP address of a route entry on the vRouter cannot be the same as any vNetwork subnet gateway IP on the vRouter：源IP地址不允许和同一虚拟路由器下虚拟链路层子网的网关IP地址相同 · The source IP address of a route entry on the vRouter cannot be within any vNetwork subnet on the vRouter：源IP地址不允许在同一虚拟路由器下虚拟链路层子网网段范围内 · The source IP address of a route entry on the vRouter cannot be within any external subnet on the vRouter：源IP地址不允许在同一虚拟路由器下外部网络的子网网段范围内 · The next hop type cannot be blackhole when the value of the type field is 401 or 402：当type字段取值为401和402时，不支持下一跳类型为黑洞 · When network cloud is enabled, the value for the type field cannot be 0：网络云开关开启时，不支持配置type为0 · The value of the type field is invalid：type字段无效 · The IP version of the IP address is invalid：IP地址的版本无效 · The two source IP address must be different：两个源IP地址不允许相同 · Invalid source IP address：源IP地址无效 · When the value of the type field is 401 and BFD enabled, a source IP is required：当type为401且BFD使能时，源IP地址必填 · A maximum of two source IP addresses are supported：源IP地址最多两个 · When the Network Cloud feature is disabled, routes with vPort or non-vPort as the next hop type are not supported：网络云开关关闭时，不支持配置下一跳类型为虚拟端口或非虚拟端口的路由表项 · The next hop type and next hop IP address do not match：下一跳类型和下一跳IP地址不匹配 · The destination subnet and the next hop type do not match：目的网段与下一跳类型不匹配 · When the next hop type is IPv6, host route recursion is not supported：当下一跳类型为IPv6时，不支持迭代主机路由 · Route entries that are enabled with BFD and use vPort next hops must have the same source IP address if they have the same next hop IP address：已存在下一跳类型为虚拟端口且已开启BFD的路由表项，如果下一跳地址相同，源IP地址也必须相同 · A route entry with the same settings already exists. Route entries that are enabled with BFD and use vPort next hops cannot have the same next hop IP address：下一跳类型为虚拟端口且开启使能BFD功能的路由表项仅允许创建一个 · Cannot enable BFD for route entries that use non-vPort next hops：非虚拟端口类型的路由表项不允许开启BFD功能 · Route entries that use vPort or non-vPort next hops cannot be edited：虚拟端口和非虚拟端口类型的路由表项不允许修改。 · When BFD is disabled, a source IP address is not required：当BFD参数取值为False时，不支持配置源IP地址 · The source IP address cannot be the same as the IP address of any gateway bound to the vRouter：源IP地址不允许和同一虚拟路由器下的网关IP地址相同 · The source IP address cannot belong to any subnet bound to the vRouter：源IP地址不允许在同一虚拟路由器下的子网网段范围内 · The source IP address cannot belong to any external subnet bound to the vRouter：源IP地址不允许在同一虚拟路由器下外部网络的子网网段内 · Do not specify the next hop vRouter when the next hop type is ExtIPv4 or ExtIPv6：当下一跳类型为ExtIPv4、ExtIPv6时，下一跳虚拟路由器无需配置 · The next hop in the route entry is a vPort and BFD is enabled for the route entry. You cannot set its IP address to be the gateway IP address of a vNetwork bound to the same vRouter as the routing table：路由表项的下一跳类型为虚拟端口且开启BFD功能时，下一跳IP地址不允许和同一虚拟路由器下虚拟链路层网络的网关IP地址相同 · Cannot apply the route entry to devices when the next hop type of the route entry is ExtIPv4 or ExtIPv6：下一跳类型为IPv4外网子网网关或IPv6外网子网网关时，路由表项不允许绑定设备 · You have no privilege to perform this operation：用户无权限执行此操作 · The source IP address cannot be within the destination subnet：源IP地址不能属于目的网段 · The source IP address conflicts with the next hop IP address：源IP地址不能与下一跳IP地址相同 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · All OpenStack-based cloud platforms have been isolated：所有的云平台已被隔离 · You cannot specify a NQA profile for a route entry with a blackhole next hop：当下一跳类型为黑洞时，不允许配置NQA策略 · The NQA profile with the specified ID does not exist：指定ID的NQA策略不存在 · The NQA profile with the specified name does not exist：指定名称的NQA策略不存在 · A route entry does not support auto NQA profiles：不支持绑定配置为自动的NQA策略 · The NQA profile name and ID do not match：通过名称获取的NQA策略与通过ID获取的NQA策略不一致 · You cannot specify a NQA profile for the route entry. The next hop address of the entry is the same as the gateway address of an external subnet configured with a NQA profile, and the external subnet has been bound to the same vRouter as the route entry：当下一跳IP地址与虚拟路由器绑定的外网子网网关IP相同，且外网子网已绑定NQA策略，则路由表项不允许手动指定NQA策略 · Invalid BFD session：无效的BFD会话 · BFD session is not configurable in network cloud scenarios：网络云场景下不支持配置BFD会话 · BFD session is not configurable when the next hop type is blackhole route：下一跳类型是黑洞路由时，不允许配置BFD会话 · You can configure the NQA profile or BFD session parameter for a route entry, but not both：同一条路由表项中不能同时配置NQA策略和BFD会话 · BFD session is not configurable when the next hop's IP address does not belong to the directly connected external network bound to the vRouter or the vRouter is not bound to a routing table：下一跳IP地址不属于虚拟路由器绑定的独享型外网子网，不允许配置BFD会话 · You cannot specify an NQA profile or BFD session for the route entry, because a next hop vRouter has been specified for the route entry：该路由表项已指定下一跳虚拟路由器，不允许配置NQA策略或BFD会话 · If a centralized-mode vRouter link, routing table, and Layer 3 DCI are attached to the same vRouter, you cannot specify the same subnet as a remote CIDR, destination subnet, and remote subnet for them, respectively：当集中式虚拟路由器连接、路由表和数据中心三层互联关联同一个虚拟路由器时，对端网段、目的网段和远端网段不能相同 · You can configure a tag for a route entry only when the network cloud scenario is disabled：Tag仅支持非网络云场景 · When host route recursion is enabled, the next hop IP address cannot reside on an external network：当迭代主机路由开关开启时，下一跳IP地址不能属于外网网段 · The tag must be an integer in the range of 1 to 4294967295：Tag的取值范围为1~4294967295的整数 · The tag value cannot be 2019091122, 2019080822, or any value in the range of 99990001 to 99999999：Tag不支持取值为2019091122和2019080822，以及99990001~99999999范围内的任意值 · If the remote end of a centralized-mode vRouter link is an external transit vRouter, the destination subnets in the route entries for the local vRouter cannot overlap with the external subnets specified for the remote vRouter：EXTERNALTRANSIT类型集中式虚拟路由器连接，本端虚拟路由器绑定的路由表项的目的网段与多数据中心外网网段信息不能重叠 · You cannot specify a tag, because a tag has been specified for a route entry destined for the same subnet in the routing table：当同一路由表中存在多条目的网段相同的路由表项时，仅允许其中一条路由表项配置Tag · You cannot enable host route recursion for a route entry when the next hop network type of that route entry is private and no next hop IP address is specified for that route entry：下一跳网络为private，下一跳IP为空的路由表项不支持开启迭代主机路由 · You cannot configure an NQA profile for a route entry when the next hop network type of that route entry is private and no next hop IP address is specified for that route entry：下一跳网络为private，下一跳IP为空的路由表项不支持配置NQA策略 · You cannot configure a BFD session for a route entry when the next hop network type of that route entry is private and no next hop IP address is specified for that route entry：下一跳网络为private，下一跳IP为空的路由表项不支持配置BFD会话 · You cannot enable host route recursion for a route entry when the next hop network type of that route entry is public：下一跳网络为public的路由表项不支持开启迭代主机路由 · You cannot configure an NQA profile for a route entry when the next hop network type of that route entry is public：下一跳网络为public的路由表项不支持配置策略NQA · You cannot configure a BFD session for a route entry when the next hop network type of that route entry is public：下一跳网络为public的路由表项不支持配置BFD会话 · You cannot configure a next hop vRouter for a route entry when the next hop network type of that route entry is public：下一跳网络为public的路由表项不支持配置下一跳虚拟路由器 · Invalid next hop network type：无效的下一跳网络 · You cannot set the next hop network type to public for a route entry when the next hop type of that route entry is ExtIPv4, ExtIPv6, or Blackhole：下一跳类型为ExtIPv4、ExtIPv6或黑洞路由的路由表项不支持配置下一跳网络为public · You must configure a minimum of one parameter from the next hop vRouter and next hop IP address for a route entry：路由表项不支持下一跳虚拟路由器和下一跳IP同时为空 · In the same routing table, route entries with the same destination subnet cannot overlap：同一路由表下目的网段相同的路由表项存在重叠 · No next hop IP address is specified for the route entry, the next hop type is IPv4 or IPv6, and the vRouter of the routing table has been bound to a non-shared gateway. The destination subnet of a route entry cannot be 0.0.0.0/0 or ::/0：当路由表项未指定下一跳IP地址，下一跳类型为IPv4或IPv6，且路由表所属的虚拟路由器已绑定非共享出口网关时，路由表项的目的地址不能为0.0.0.0/0或::/0 |
|
关键字 |
DELETE_ROUTE_ENTITY_OP |
|
日志内容 |
Deleted extended route entities $1 |
|
参数解释 |
$1：路由表项的参数体 |
|
举例 |
Deleted extended route entities { "id":"null", "destination":"10.10.0.0/16", "nexthop":"12.3.3.3", "type":"401", "ip_version":"4", "source_ips":"[1.0.0.2]", "bfd":"true", "routetable_id":"b930d7f6-ceb7-40a0-8b81-a425dd994ccf", "cloud_region_name":"openstack" },{ "id":"null", "destination":"11.11.0.0/16", "nexthop":"13.3.3.3", "type":"401", "ip_version":"4", "source_ips":"[1.0.0.2]", "bfd":"true", "routetable_id":"b930d7f6-ceb7-40a0-8b81-a425dd994ccf", "cloud_region_name":"openstack" }. |
|
日志说明 |
用户进行了删除扩展路由表项的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The specified resource doesn't exist：指定的资源不存在 · The specified device doesn't exist：指定的设备不存在 · The device ID and the device name do not match：设备的ID和名称不匹配 · Duplicate devices exist：设备列表中存在重复的设备 · Unknown error：未知错误 · The route entries cannot be created on edge devices：路由表项中的设备不支持ED设备 · The value of the type field is invalid：type字段无效 · When the Network Cloud feature is disabled, routes with vPort or non-vPort as the next hop type are not supported：网络云开关关闭时，不支持配置下一跳类型为虚拟端口或非虚拟端口的路由表项 · When the next hop type is IPv6, host route recursion is not supported：当下一跳类型为IPv6时，不支持迭代主机路由 · Cannot apply the route entry to devices when the next hop type of the route entry is ExtIPv4 or ExtIPv6：下一跳类型为IPv4外网子网网关或IPv6外网子网网关时，路由表项不允许绑定设备 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · You cannot edit or delete the cloud region name：云区域名称不允许修改或删除 · All OpenStack-based cloud platforms have been isolated：所有的云平台已被隔离 · Invalid BFD session：无效的BFD会话 · BFD session is not configurable in network cloud scenarios：网络云场景下不支持配置BFD会话 · BFD session is not configurable when the next hop type is blackhole route：下一跳类型是黑洞路由时，不允许配置BFD会话 · You can configure the NQA profile or BFD session parameter for a route entry, but not both：同一条路由表项中不能同时配置NQA策略和BFD会话 · BFD session is not configurable when the next hop's IP address does not belong to the directly connected external network bound to the vRouter：下一跳IP地址不属于虚拟路由器绑定的独享型外网子网，不允许配置BFD会话 · You cannot specify an NQA profile or BFD session for the route entry, because a next hop vRouter has been specified for the route entry：该路由表项已指定下一跳虚拟路由器，不允许配置NQA策略或BFD会话 · You can configure a tag for a route entry only when the network cloud scenario is disabled：Tag仅支持非网络云场景 · When host route recursion is enabled, the next hop IP address cannot reside on an external network：当迭代主机路由开关开启时，下一跳IP地址不能属于外网网段 · The tag must be an integer in the range of 1 to 4294967295：Tag的取值范围为1~4294967295的整数 · The tag value cannot be 2019091122, 2019080822, or any value in the range of 99990001 to 99999999：Tag不支持取值为2019091122和2019080822，以及99990001~99999999范围内的任意值 · You cannot bind devices to a route entry when the effective next hop type for the route entry is intranet IP：当生效的下一跳类型为内网IP时，不允许指定设备 · You cannot specify a tag, because a tag has been specified for a route entry destined for the same subnet in the routing table：当同一路由表中存在多条目的网段相同的路由表项时，仅允许其中一条路由表项配置Tag · You cannot enable host route recursion for a route entry when the next hop network type of that route entry is private and no next hop IP address is specified for that route entry：下一跳网络为private，下一跳IP为空的路由表项不支持开启迭代主机路由 · You cannot configure an NQA profile for a route entry when the next hop network type of that route entry is private and no next hop IP address is specified for that route entry：下一跳网络为private，下一跳IP为空的路由表项不支持配置NQA策略 · You cannot configure a BFD session for a route entry when the next hop network type of that route entry is private and no next hop IP address is specified for that route entry：下一跳网络为private，下一跳IP为空的路由表项不支持配置BFD会话 · You cannot enable host route recursion for a route entry when the next hop network type of that route entry is public：下一跳网络为public的路由表项不支持开启迭代主机路由 · You cannot configure an NQA profile for a route entry when the next hop network type of that route entry is public：下一跳网络为public的路由表项不支持配置策略NQA · You cannot configure a BFD session for a route entry when the next hop network type of that route entry is public：下一跳网络为public的路由表项不支持配置BFD会话 · When the next hop type is Blackhole, the value of the host route recursion parameter must be false：当下一跳类型为黑洞时，迭代主机路由参数必须为false |
|
关键字 |
DELETE_ROUTE_ENTITY_OP |
|
日志内容 |
Deleted route entry $1. |
|
参数解释 |
$1：路由表项的参数体 |
|
举例 |
Deleted route entry { "id":"e13b19a2-e8a7-4d04-afe3-c71ffeb467f9", "destination":"10.10.0.0/16", "nexthop":"12.3.3.3", "type":"401", "ip_version":"4", "source_ips":"[1.0.0.2]", "bfd":"true", "routetable_id":"6e439816-a1a1-4985-beba-2604f04e68e3", "cloud_region_name":"openstack" }. |
|
日志说明 |
用户进行了删除路由表项的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The specified resource doesn't exist：指定的资源不存在 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · All OpenStack-based cloud platforms have been isolated：所有的云平台已被隔离 |
|
关键字 |
UPDATE_SEGMENT_OP |
|
日志内容 |
Updated segment $1. |
|
参数解释 |
$1：网络分段的参数体 |
|
举例 |
Updated segment { "id":"57fe85e4-ca2f-4192-b3cd-d5c249d7a21f", "name":"se01", "network_id":"5c0cb560-4089-41dd-be29-469907a23b49", "segmentation_id":"2000", "network_type":"vlan", "physical_network":"segment-1", "description":"11111", "cloud_region_name":"openstack", }. |
|
日志说明 |
用户进行了修改网络分段的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The operation requires the administrator privilege：您需要管理员权限才能执行此操作 · The specified resource doesn't exist：指定的资源不存在 · The segment name cannot exceed 255 characters：Segment名称最长255个字符 · The description cannot exceed 255 characters：描述信息最长255个字符 · You have no privilege to perform this operation：用户无权限执行此操作 · The external segment ID is already in use：External Segment ID 已经被使用 · The external segment ID is out of range：External Segment ID超出范围 · You cannot edit or delete the cloud region name：云区域名称不允许修改或删除 · You must specify a valid VXLAN pool type when automatic allocation of L3VNIs for external networks is enabled：当自动分配外网L3VNI开关开启时VXLAN池类型不能为无效值 · vxlanPoolType cannot be vxlanPoolForL3vni or vdsPoolForL3vni when automatic allocation is not enabled：当自动分配外网L3VNI开关关闭时VXLAN池类型不能为VXLAN或VDS · Automatic allocation cannot be enabled when l3vni is exist：当外网L3VNI存在时不能开启自动分配外网L3VNI开关 · All OpenStack-based cloud platforms have been isolated：所有的云平台已被隔离 · You cannot both enable network segmentation and specify a gateway for an external network：外部网络的网络分段和出口网关冲突 · The RT generated based on the external segment ID of the external network conflicts with the import RT of vRouter：外部网络External Segment ID生成的RT与虚拟路由器配置的引入RT冲突 · The RT generated based on the external segment ID of the external network conflicts with the export RT of vRouter：外部网络External Segment ID生成的RT与虚拟路由器配置的引出RT冲突 · The RT generated based on the external segment ID of the external network is identical to the import RT of a Layer 2 DC interconnect：外部网络External Segment ID生成的RT与数据中心二层互联的引入RT冲突 · The RT generated based on the external segment ID of the external network is identical to the export RT of a Layer 2 DC interconnect：外部网络External Segment ID生成的RT与数据中心二层互联的引出RT冲突 · The RT generated based on the external segment ID of the external network is identical to the import RT of a Layer 3 DC interconnect：外部网络External Segment ID生成的RT与数据中心三层互联的引入RT冲突 · The RT generated based on the external segment ID of the external network is identical to the export RT of a Layer 3 DC interconnect：外部网络External Segment ID生成的RT与数据中心三层互联的引出RT冲突 · Cannot allocate this external segment ID, because synchronization is in progress for the VXLAN pool containing this external segment ID：无法分配该External Segment ID，其所在的VXLAN池正在平滑中 |
|
关键字 |
DELETE_SEGMENT_OP |
|
日志内容 |
Deleted segment $1. |
|
参数解释 |
$1：网络分段的参数体 |
|
举例 |
Deleted segment { "id":"57fe85e4-ca2f-4192-b3cd-d5c249d7a21f", "name":"se01", "network_id":"5c0cb560-4089-41dd-be29-469907a23b49", "segmentation_id":"2000", "network_type":"vlan", "physical_network":"segment-1", "description":"11111", "cloud_region_name":"openstack", }. |
|
日志说明 |
用户进行了删除网络分段的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The operation requires the administrator privilege：您需要管理员权限才能执行此操作 · The segment has been bound to subnets：Segment已被子网绑定 · The specified resource doesn't exist：指定的资源不存在 · You have no privilege to perform this operation：用户无权限执行此操作 · All OpenStack-based cloud platforms have been isolated：所有的云平台已被隔离 |
|
关键字 |
CREATE_TRUNK_OP |
|
日志内容 |
Created trunk $1. |
|
参数解释 |
$1：端口中继的参数体 |
|
举例 |
Created trunk { "sub_ports":"[{ "segmentation id":"44", "port id":"4b4c691b-086d-43d2-8a65-5487e9434155", "segmentation type":"vlan", }]", "name":"foo", "tenant_id":"145a14e4-a64b-49bf-98ba-ad8945dbd4f1", "port_id":"8027c4da-772f-4e43-bfbf-023b4a4e63de", "id"":"114a26b1-d124-4835-bb4f-021d3d886023", "description"":"", "cloud_region_name":"openstack" }. |
|
日志说明 |
用户进行了增加端口中继的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The trunk name is invalid：无效的Trunk名称 · The tenant ID is invalid：无效的租户ID · The parent port has been bound to another trunk：指定的父端口已被其他Trunk绑定 · The parent port does not exist：指定的父端口不存在 · The parent port and subport must be the same type：指定父端口和子端口的类型必须一致 · The port ID of the parent is invalid：无效的父端口ID · The port ID of the subport is invalid：无效的子端口ID · The subport has been bound to another trunk：指定的子端口已被其他Trunk绑定 · The trunk ID already exists：Trunk ID已存在 · The value of the segmentation_Type on subport must be VLAN：指定的子端口必须为VLAN类型 · The segmentation_Type of the subport is invalid.：无效的子端口VLAN类型 · Duplicate segmentation ID：重复的Segmentation ID · The segmentation ID is out of range：子端口Segmentation ID超出范围 · The segmentation ID of the subport is invalid：无效的子端口Segmentation ID · The trunk description cannot exceed 255 characters：Trunk的描述信息不能超过255字符 · The trunk name cannot exceed 255 characters：Trunk的名称不能超过255字符 · Duplicate trunk ID：重复的 Trunk ID · Duplicate parent port ID：重复的 父端口ID · Duplicate subport port ID：重复的子端口ID · The subport does not exist：指定的子端口不存在 · The controller is not the active leader：当前设备不是Leader控制组件，无法进行此操作 · Token aged：Token已老化 · Online vPorts cannot be used as subports：已上线虚拟端口不支持作为子端口 · The parent port and the subport cannot be the same：父端口与子端口不能为同一个虚拟端口 · The tenant ID of the parent port and the subport must be the same as the specified tenant ID：指定的父端口和子端口所属的租户ID必须与指定的租户ID相同 · You have no privilege to perform this operation：用户无权限执行此操作 · Trunks do not support LB, GW, DHCP, or PBR vPorts：Trunk不支持绑定LB、GW、DHCP、PBR类型的虚拟端口 · Up to 255 characters, case sensitive：参数不能超过255个字符，区分大小写 · All OpenStack-based cloud platforms have been isolated：所有的云平台已被隔离 · Please specify an SVLAN：外层VLAN不能为空 · Please specify a CVLAN：内层VLAN不能为空 · The SVLAN is out of range：外层VLAN超出范围 · The CVLAN is out of range：内层VLAN超出范围 · The cloud region name of the QinQ mapping can contain up to 255 characters：QinQ映射的云区域名称最长255个字符 · Please specify the host_id parameter：host_id不能为空 · You cannot bind the network overlay host to a network overlay cluster, because it has been configured with QinQ mappings：Netoverlay主机已添加QinQ映射，不允许绑定Netoverlay集群 · A QinQ mapping on the network overlay host already contains the specified SVLAN range and CVLAN range：Netoverlay主机上的QinQ映射已存在指定SVLAN和CVLAN范围 · The QinQ mappings on the same network overlay host must have exclusive SVLAN ranges and CVLAN ranges：同一个Netoverlay主机的QinQ映射不能配置重复的SVLAN和CVLAN范围 · You cannot bind the parent port to a port automatically onboarded by southbound packets：父端口不支持绑定南向自动创建的端口 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · You cannot bind the subport to a port automatically onboarded by southbound packets：子端口不支持绑定南向自动创建的端口 · Online OVS vPorts cannot be used as subports：已上线OVS类型虚拟端口不支持作为子端口 · Online vPorts cannot be used as subports, because the transparent mode is enabled：透传模式开启时，已上线虚拟端口不支持作为子端口 · A parent port and its subports must be configured with the same QoS profile：父端口和其子端口必须配置相同类型的QoS策略 |
|
关键字 |
UPDATE_TRUNK_OP |
|
日志内容 |
Updated trunk $1. |
|
参数解释 |
$1：端口中继的参数体 |
|
举例 |
Updated trunk { "sub_ports":"[{ "segmentation id":"44", "port id":"4b4c691b-086d-43d2-8a65-5487e9434155", "segmentation type":"vlan", }]", "name":"foo", "tenant_id":"145a14e4-a64b-49bf-98ba-ad8945dbd4f1", "port_id":"8027c4da-772f-4e43-bfbf-023b4a4e63de", "id"":"114a26b1-d124-4835-bb4f-021d3d886023", "description"":"", "cloud_region_name":"openstack" }. |
|
日志说明 |
用户进行了更新端口中继的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The specified trunk does not exist：指定Trunk不存在 · The trunk name is invalid：无效的Trunk名称 · The controller is not the active leader：当前设备不是Leader控制组件，无法进行此操作 · The trunk description cannot exceed 255 characters：Trunk的描述信息不能超过255字符 · The trunk name cannot exceed 255 characters：Trunk的名称不能超过255字符 · Token aged：Token已老化 · You have no privilege to perform this operation：用户无权限执行此操作 · Trunks do not support LB, GW, DHCP, or PBR vPorts：Trunk不支持绑定LB、GW、DHCP、PBR类型的虚拟端口 · You cannot edit or delete the cloud region name：云区域名称不允许修改或删除 · All OpenStack-based cloud platforms have been isolated：所有的云平台已被隔离 · Please specify an SVLAN：外层VLAN不能为空 · Please specify a CVLAN：内层VLAN不能为空 · The SVLAN is out of range：外层VLAN超出范围 · The CVLAN is out of range：内层VLAN超出范围 · The cloud region name of the QinQ mapping can contain up to 255 characters：QinQ映射的云区域名称最长255个字符 · Please specify the host_id parameter：host_id不能为空 · You cannot bind the network overlay host to a network overlay cluster, because it has been configured with QinQ mappings：Netoverlay主机已添加QinQ映射，不允许绑定Netoverlay集群 · A QinQ mapping on the network overlay host already contains the specified SVLAN range and CVLAN range：Netoverlay主机上的QinQ映射已存在指定SVLAN和CVLAN范围 · The QinQ mappings on the same network overlay host must have exclusive SVLAN ranges and CVLAN ranges：同一个Netoverlay主机的QinQ映射不能配置重复的SVLAN和CVLAN范围 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · A parent port and its subports must be configured with the same QoS profile：父端口和其子端口必须配置相同类型的QoS策略 |
|
关键字 |
DELETE_TRUNK_OP |
|
日志内容 |
Deleted trunk $1. |
|
参数解释 |
$1：端口中继的参数体 |
|
举例 |
Deleted trunk { "sub_ports":"[{ "segmentation id":"44", "port id":"4b4c691b-086d-43d2-8a65-5487e9434155", "segmentation type":"vlan", }]", "name":"foo", "tenant_id":"145a14e4-a64b-49bf-98ba-ad8945dbd4f1", "port_id":"8027c4da-772f-4e43-bfbf-023b4a4e63de", "id"":"114a26b1-d124-4835-bb4f-021d3d886023", "description"":"", "cloud_region_name":"openstack" }. |
|
日志说明 |
用户进行了删除端口中继的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The specified trunk does not exist：指定Trunk不存在 · The controller is not the active leader：当前设备不是Leader控制组件，无法进行此操作 · Token aged：Token已老化 · You have no privilege to perform this operation：用户无权限执行此操作 · All OpenStack-based cloud platforms have been isolated：所有的云平台已被隔离 · The specified resource doesn't exist：指定的资源不存在 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
CREATE_SUBPORT_OP |
|
日志内容 |
Created subports to trunk $1. The subports information is as follows: $2 |
|
参数解释 |
$1：端口中继的UUID $2：子端口的参数体 |
|
举例 |
Created subports to trunk 4ebb89c6-31c8-4ec5-9d83-c801153b5f1b. The subports information is as follows: [{ "segmentation id":"203", "port id":"9c079e97-60be-4a6e-88b8-6b8becaf69df", "segmentation type":"vlan" }]. |
|
日志说明 |
用户进行了增加子端口的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The specified trunk does not exist：指定Trunk不存在 · The parent port and subport must be the same type：指定父端口和子端口的类型必须一致 · The port ID of the subport is invalid：无效的子端口ID · The subport has been bound to another trunk：指定的子端口已被其他Trunk绑定 · The value of the segmentation_Type on subport must be VLAN：指定的子端口必须为VLAN类型 · The segmentation_Type of the subport is invalid：无效的子端口VLAN类型 · The segmentation ID of the subport is invalid：无效的子端口Segmentation ID · The segmentation ID is out of range：子端口Segmentation ID超出范围 · Duplicate segmentation ID：重复的Segmentation ID · Duplicate subport port ID：重复的子端口ID · The subport does not exist：指定的子端口不存在 · The controller is not the active leader：当前设备不是Leader控制组件，无法进行此操作 · Token aged：Token已老化 · Online vPorts cannot be used as subports：已上线虚拟端口不支持作为子端口 · You have no privilege to perform this operation：用户无权限执行此操作 · Trunks do not support LB, GW, DHCP, or PBR vPorts：Trunk不支持绑定LB、GW、DHCP、PBR类型的虚拟端口 · All OpenStack-based cloud platforms have been isolated：所有的云平台已被隔离 · Please specify an SVLAN：外层VLAN不能为空 · Please specify a CVLAN：内层VLAN不能为空 · The SVLAN is out of range：外层VLAN超出范围 · The CVLAN is out of range：内层VLAN超出范围 · The cloud region name of the QinQ mapping can contain up to 255 characters：QinQ映射的云区域名称最长255个字符 · Please specify the host_id parameter：host_id不能为空 · You cannot bind the network overlay host to a network overlay cluster, because it has been configured with QinQ mappings：Netoverlay主机已添加QinQ映射，不允许绑定Netoverlay集群 · A QinQ mapping on the network overlay host already contains the specified SVLAN range and CVLAN range：Netoverlay主机上的QinQ映射已存在指定SVLAN和CVLAN范围 · The QinQ mappings on the same network overlay host must have exclusive SVLAN ranges and CVLAN ranges：同一个Netoverlay主机的QinQ映射不能配置重复的SVLAN和CVLAN范围 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · You cannot bind the subport to a port automatically onboarded by southbound packets：子端口不支持绑定南向自动创建的端口 · Online OVS vPorts cannot be used as subports：已上线OVS类型虚拟端口不支持作为子端口 · Online vPorts cannot be used as subports, because the transparent mode is enabled：透传模式开启时，已上线虚拟端口不支持作为子端口 |
|
关键字 |
DELETE_SUBPORT_OP |
|
日志内容 |
Deleted subports from trunk $1. The subports information is as follows: $2. |
|
参数解释 |
$1：端口中继的UUID $2：子端口的参数体 |
|
举例 |
Deleted subports from trunk 36c2caa5-0352-4015-ab6b-35b635efe8fd. The subports information is as follows: [{ "segmentation id":"212", "port id":"9c079e97-60be-4a6e-88b8-6b8becaf69df", "segmentation type":"vlan" }]. |
|
日志说明 |
用户进行了删除子端口的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The specified trunk does not exist：指定Trunk不存在 · The subport does not exist：指定的子端口不存在 · The controller is not the active leader：当前设备不是Leader控制组件，无法进行此操作 · You have no privilege to perform this operation：用户无权限执行此操作 · All OpenStack-based cloud platforms have been isolated：所有的云平台已被隔离 · The specified resource doesn't exist：指定的资源不存在 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
CREATE_VPC_CONNECTION_OP |
|
日志内容 |
Created VPC connection $1. |
|
参数解释 |
$1：虚拟路由器连接的参数体 |
|
举例 |
Created VPC connection { "id":"e594591e-27ba-45e9-8792-9ce5ca29b0ed", "vpc_connection_id":"e594591e-27ba-45e9-8792-9ce5ca29b0ed", "fw_enabled":"e594591e-27ba-45e9-8792-9ce5ca29b0ed", "name":"vpc1", "tenant_id":"ffffffff-0000-0000-0000-000000000001", "description":"aaaaaaaaa", "local_router":"ffffffff-0000-0000-0000-000000000001", "local_cidrs":"[10.10.10.10/24]", "local_subnets"":"[073ceea5-4c17-4b24-8eb0-18407ca420e8]", "local_firewall_enable"":"false", "peer_router":"355973f6-69dd-4018-82f3-8ba3159ddf1e", "peer_cidrs":"[20.20.20.20/24]", "peer_subnets"":"[2de17490-4293-448d-9eee-b82aa446b4db]", "peer_firewall_enable"":"false", "mode":"0", "cloud_region_name":"openstack", }. |
|
日志说明 |
用户进行了创建虚拟路由器连接的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The vRouter interconnection ID already exists：虚拟路由器连接ID已经存在 · The tenant ID is required：租户ID不能为空 · The tenant does not exist：租户不存在 · The local vRouter ID is required：本端虚拟路由器ID不能为空 · The remote vRouter ID is required：对端虚拟路由器ID不能为空 · The local vRouter does not exist：本端虚拟路由器不存在 · The remote vRouter does not exist：对端虚拟路由器不存在 · The local subnet ID is required：本端虚拟子网ID不能为空 · The remote subnet ID is required：对端虚拟子网ID不能为空 · The local subnet list contains nonexistent subnets：本端子网列表中包含不存在的子网 · The remote subnet list contains nonexistent subnets：对端子网列表中包含不存在的子网 · A remote subnet of the vRouter interconnection overlaps with a remote subnet of a Layer 3 DC interconnection. The subnet of the vRouter interconnection must cover the overlapping subnet of the Layer 3 DC interconnection：虚拟路由器连接的对端子网范围必须大于数据中心三层互联同网段的远端网段范围 · The local vRouter and the remote vRouter cannot be the same：本端虚拟路由器与对端虚拟路由器重复 · The local subnets overlap with the subnets of the remote vRouter：本端虚拟子网与对端虚拟路由器的虚拟子网发生重叠 · The remote subnets overlap with the subnets of the local vRouter：对端虚拟子网与本端虚拟路由器的虚拟子网发生重叠 · The vRouter interconnection already exists：虚拟路由器连接配置已存在 · The status field is a read-only field：status为只读字段 · The vRouter interconnection name cannot exceed 255 characters：虚拟路由器连接名称不能大于255个字符 · The vRouter interconnection description cannot exceed 255 characters：虚拟路由器连接描述不能大于255个字符 · The network to which the remote subnet belongs cannot be a VLAN：对端子网所属的虚拟链路层网络不能为VLAN类型 · The remote subnet cannot be an external subnet：对端子网不能为外网子网 · The network to which the local subnet belongs cannot be a VLAN：本端子网所属的虚拟链路层网络不能为VLAN类型 · The local subnet cannot be an external subnet：本端子网不能为外网子网 · If a vRouter is bound to multiple vRouter interconnections, the selected subnets of the other vRouters bound to these vRouter interconnections cannot overlap：多个虚拟路由器连接绑定同一虚拟路由器时，连接绑定的另一个虚拟路由器之间的已选子网不能重叠 · The vRouter link is enabled with the firewall feature. You can add only vRouters that are bound to a single-member gateway to the vRouter link：虚拟路由器连接已启用防火墙，指定的虚拟路由器只能绑定一个出口网关，且出口网关只能为单成员 · Unknown error：未知错误 · The source IP address of a route entry with a vPort-type next hop on the vRouter cannot overlap with any vNetwork subnet on another vRouter：建立虚拟路由器连接的两个虚拟路由器，一个虚拟路由器下虚拟端口类型的路由表项的源IP不允许和另一个虚拟路由器下虚拟链路层网络的子网重叠 · The source IP address of a route entry with a vPort-type next hop on the vRouter cannot overlap with any external subnet on another vRouter：建立虚拟路由器连接的两个虚拟路由器，一个虚拟路由器下虚拟端口类型的路由表项的源IP不允许和另一个虚拟路由器下外部网络的子网重叠 · The source IP address of a route entry with a vPort-type next hop on the vRouter cannot be the same as any vNetwork subnet gateway IP of another vRouter：建立虚拟路由器连接的两个虚拟路由器，一个虚拟路由器下虚拟端口类型的路由表项的源IP不允许和另一个虚拟路由器下虚拟链路层网络子网的网关IP地址相同 · The value of the firewallenable field must be true (case sensitive) or false (case sensitive)：firewallenable字段取值必须为true或false，且区分大小写 · The local_router and peer_router fields must be configured：local_router和peer_router字段不允许为空 · The value of the mode field is invalid：mode字段取值不合法 · When the value of the Mode field is 1, local subnets and remote subnets are not supported：MODE为1时，不支持local_subnets和peer_subnets字段 · Local CIDRs cannot overlap with remote subnets：本端网段和对端路由器下的所有子网不允许重叠 · The local vRouter has established links with multiple vRouters and the CIDRs specified for the peer vRouters of the local vRouter cannot overlap：本端虚拟路由器与多个虚拟路由器建立连接时，不支持目的网段重叠 · Local subnets cannot overlap with remote subnets：本端路由器子网和对端路由器子网的网段不允许重叠 · Local CIDRs cannot overlap with remote CIDRs：本端网段和对端网段不允许重叠 · Invalid subnet mask：掩码位非法 · Invalid IP address：无效的IP地址 · The remote vRouter has established links with multiple vRouters and the CIDRs specified for the peer vRouters of the remote vRouter cannot overlap：对端虚拟路由器与多个虚拟路由器建立连接时，不支持目的网段重叠 · When the value of the Mode field is 1, local CIDRs are required：MODE为1时，本端网段不能为空 · When the value of the Mode field is 1, remote CIDRs are required：MODE为1时，远端网段不能为空 · Duplicated CIDRs exist in local or remote CIDRs：本端网段/远端网段中存在网段重叠 · When the network cloud feature is off, the mode value cannot be 1：网络云场景关闭时，mode字段不允许配置为1 · You have no privilege to perform this operation：用户无权限执行此操作 · The vRouter link is disabled with the firewall feature. The border gateways for the local and remote vRouters must be bound to the same device group：防火墙关闭场景下，虚拟路由器连接本端和对端虚拟路由器所绑定的出口网关必须绑定相同的设备组 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · The VLAN range pool does not exist or no VLAN IDs are available in the VLAN range pool：指定的租户承载网类型的VLAN池不存在，或该VLAN池内没有足够的VLAN ID · The address pool does not exist or no IPv4 or IPv6 addresses are available in the address pool：指定的地址池不存在，或该地址池内没有可用的IPv4/IPv6地址 · All OpenStack-based cloud platforms have been isolated：所有的云平台已被隔离 · The VLAN range pool does not exist or no VLAN IDs are available in the VLAN range pool：指定的租户承载网类型的VLAN池不存在，或该VLAN池内没有足够的VLAN ID · The address pool does not exist or no IPv4 or IPv6 addresses are available in the address pool：指定的地址池不存在，或该地址池内没有可用的IPv4/IPv6地址 · The vRouter link is enabled with the firewall feature. You can add only vRouters that are bound to a single-member gateway to the vRouter link：虚拟路由器连接已启用防火墙，指定的虚拟路由器只能绑定一个出口网关，且出口网关只能为单成员 · You can add only vRouters that are bound to a single-member gateway to the vRouter link：指定的虚拟路由器只能绑定一个出口网关，且出口网关只能为单成员 · If the two vRouters of a vRouter link are in different fabrics, you must configure these fabrics with device groups used for fabric interconnect deployment：虚拟路由器互联两端的虚拟路由器跨Fabric时，需配置网络位置为Fabric间互通的设备组 · Remote CIDRs cannot overlap with local subnets：对端网段和本端路由器下的所有子网不允许重叠 · Local subnets cannot overlap with local cidrs：本端子网和本端网段不允许重叠 · Peer subnets cannot overlap with peer cidrs：对端子网和对端网段不允许重叠 · You must specify local subnets, local CIDRs, or both：本端子网和本端网段不允许同时为空 · You must specify remote subnets, remote CIDRs, or both：对端子网和对端网段不允许同时为空 · If the firewall feature is enabled for only one vRouter on the vRouter link, you must bind a firewall to that vRouter：本端或对端防火墙开关开启时，虚拟路由器必须绑定防火墙 · You must bind a gateway to both the local and remote vRouters：本端和对端虚拟路由器必须绑定网关 · When the firewall mode is normal, the vRouter type cannot be PBR：防火墙Mode为NORMAL时，虚拟路由器不支持PBR类型 · When the firewall mode is normal, the local and remote vRouters cannot both be transit nodes：防火墙Mode为NORMAL时，不支持本端虚拟路由器和对端虚拟路由器同时为Transit类型 · You cannot enable the firewall feature for the remote vRouter, because the remote vRouter type is transit：对端虚拟路由器类型为TRANSIT时，不支持开启防火墙 · You cannot enable the firewall feature for the local vRouter, because the local vRouter type is transit：本端虚拟路由器类型为TRANSIT时，不支持开启防火墙 · You cannot advertise all remote networks：当前不支持开启发布对端所有路由 · You cannot advertise all local networks：当前不支持开启发布本端所有路由 · The subnet parameter and CIDR network parameter must both be null for a transit vRouter：Transit类型虚拟路由器子网和网段必须同时为null · The subnet parameter and CIDR network parameter cannot both be null for a normal vRouter：Normal类型虚拟路由器子网和网段不允许同时为null · If the normal vRouter on a vRouter link advertises all networks, the transit vRouter on the vRouter link must also advertise all networks：NORMAL虚拟路由器发布所有路由字段为开启时，TRANSIT虚拟路由器发布所有路由字段不支持关闭 · If a transit vRouter has been used to create a firewall protected VPC connection, the vRouter cannot be used to create VPC connection disabled with the firewall feature, and vice versa：同一Transit虚拟路由器不支持同时创建过墙与不过墙两种类型的VPC互通 · The normal vRouter in a transit VPC enabled with the firewall feature must be bound to a DCI-capable gateway or firewall：在过墙Transit VPC中,NORMAL类型的虚拟路由器没有绑定具有DCI能力的网关或防火墙 · The normal vRouter in a transit VPC without firewall protection or the tenant of the vRouter must be bound to a gateway with the DCI capability：在不过墙Transit VPC中,NORMAL类型的虚拟路由器或所属租户没有绑定具有DCI能力的网关 · When you advertise all local networks, the subnet parameter and CIDR network parameter must both be null for the local vRouter：发布本端所有路由开启时，本端虚拟路由器子网和网段必须同时为null · When you advertise all remote networks, the subnet parameter and CIDR network parameter must both be null for the remote vRouter：发布对端所有路由开启时，对端虚拟路由器子网和网段必须同时为null · The subnet parameter and CIDR network parameter cannot both be null for the remote vRouter：对端虚拟路由器子网和网段不允许同时为null · The vRouter is not bound to a firewall：虚拟路由器没有绑定防火墙资源 · The specified tenant carrier network VLAN pool does not exist or the VLAN pool does not have sufficient VLAN IDs：指定的租户承载网类型的VLAN池不存在，或VLAN池内VLAN ID不足 · When a vRouter link is established between a normal vRouter and a transit vRouter, you cannot enable the advertising all networks feature for the normal vRouter when the advertising all networks feature is disabled for the transit vRouter：不支持NORMAL虚拟路由器端发布所有路由开启且TRANSIT虚拟路由器端发布所有路由关闭 · The manually specified networks cannot overlap with external subnets bound to the vRouter：手动输入网段不能与虚拟路由器绑定的外网子网网段重叠 · If a centralized-mode vRouter link, routing table, and Layer 3 DCI are attached to the same vRouter, you cannot specify the same subnet as a remote CIDR, destination subnet, and remote subnet for them, respectively：当集中式虚拟路由器连接、路由表和数据中心三层互联关联同一个虚拟路由器时，对端网段、目的网段和远端网段不能相同 · In non-network cloud scenarios, you can enable route reduction for a centralized-mode vRouter link only when the peer vRouters are normal type and the firewalls are disabled at both ends of the link：非网络云场景下，集中式虚拟路由器连接本端和对端防火墙都为关闭，且本端和对端虚拟路由器类型为NORMAL时，才允许开启路由精简开关 · You cannot enable route reduction in the network cloud scenario：网络云场景下，不允许开启路由精简开关 · Incorrect configuration for the host route advertisement feature：当前配置下，发布主机路由开关取值错误 · An external transit vRouter, The local vRouter and the peer vRouter must bind the same gateway：集中式虚拟路由器连接绑定EXTERNALTRANSIT类型虚拟路由器时，本端虚拟路由器和对端虚拟路由器绑定的出口网关必须相同 · The local vRouter cannot be an external transit vRouter：本端虚拟路由器类型不能为EXTERNALTRANSIT类型 · You must bind a gateway to the local vRouter enabled with the firewall feature：本端防火墙开关开启时，本端虚拟路由器必须绑定网关 · When the value for the Mode field is NORMAL, the vRouter type of either the local vRouter or remote vRouter must be NORMAL：MODE为NORMAL时，不支持本端虚拟路由器和对端虚拟路由器的类型同时为非NORMAL类型 · You cannot modify the configuration for the host route advertisement feature if the type of the peer vRouter is normal：对端虚拟路由器类型是NORMAL类型，不支持修改发布主机路由开 · You must bind a firewall to the local vRouter enabled with the firewall feature：本端防火墙开关开启时，本端虚拟路由器必须绑定防火墙 · If the external transit vRouter is the remote vRouter in a centralized vRouter link, you must enable advertisement of all remote routes：集中式虚拟路由器连接绑定EXTERNALTRANSIT类型虚拟路由器时，发布对端所有路由开关 必须开启 · An external transit vRouter, you must disable the remote firewall：集中式虚拟路由器连接绑定EXTERNALTRANSIT类型虚拟路由器时，对端防火墙必须关闭 · The remote vRouter cannot be an external transit vRouter：对端虚拟路由器类型不能为EXTERNALTRANSIT类型 · The tenant has not bind dci gateway：集中式虚拟路由器连接绑定EXTERNALTRANSIT类型虚拟路由器时，租户必须绑定具有DCI能力的网关 · You must configure multi-DC internal subnets for an external transit vRouter if the vRouter is in a centralized vRouter link and uses firewall as the edge device to external networks：集中式虚拟路由器连接绑定EXTERNALTRANSIT类型虚拟路由器，且虚拟路由器外网出口设备为防火墙时，EXTERNALTRANSIT类型虚拟路由器的多数据中心内网网段信息不能为空 · If the remote vRouter in a centralized vRouter link is an external transit vRouter, the firewall feature must be disabled for the remote vRouter：集中式虚拟路由器连接绑定EXTERNALTRANSIT类型虚拟路由器时，对端防火墙必须关闭 · If the local vRouter in a centralized vRouter link is enabled with the firewall feature, the device group position of the border gateways bound to the vRouter must be border gateway and DCI：集中式虚拟路由器连接本端防火墙开启时，本端虚拟路由器必须绑定设备组网络位置为出口网关和DC间互联的出口网关 · The remote vRouter for a centralized-mode vRouter link cannot have a default subnet included in its external subnets if the following conditions exist: 1. The remote vRouter is an external transit vRouter. 2. A border gateway with gateway sharing disabled is already bound to the local vRouter：EXTERNALTRANSIT类型集中式虚拟路由器连接，本端虚拟路由器已绑定非共享出口网关，多数据中心外网网段信息不能包含默认网段 · If the remote end of a centralized-mode vRouter link is an external transit vRouter, the destination subnets in the route entries for the local vRouter cannot overlap with the external subnets specified for the remote vRouter：EXTERNALTRANSIT类型集中式虚拟路由器连接，本端虚拟路由器绑定的路由表项的目的网段与多数据中心外网网段信息不能重叠 · Local CIDRs cannot overlap with the external subnets specified for the remote vRouter：本端网段和对端路由器多数据中心外网网段信息不允许重叠 · If the remote end of a centralized-mode vRouter link is an external transit vRouter, you must disable the local vRouter from advertising loacl host routes：集中式虚拟路由器连接绑定EXTERNALTRANSIT类型虚拟路由器时，发布本端所有路由开关必须关闭 · Overlapping items are not allowed in the information configuration of the external network segment of the multi data center of different transitvrouter corresponding to the same tenant virtual router in the VPC：同一个虚拟路由器与不同的EXTERNALTRANSIT类型虚拟路由器建立集中式虚拟路由器连接，EXTERNALTRANSIT类型虚拟路由器间的多数据中心外网网段信息存在子网网段重叠 · When the remote vRouter in a centralized-mode vRouter link is an external transit vRouter and the local vRouter is not enabled with the firewall service, make sure one of the following requirements is met: ¡ The local vRouter is bound to a DCI-capable border gateway. ¡ The tenant of the local vRouter is bound to a border gateway used only for DCI deployment. 集中式虚拟路由器连接绑定EXTERNALTRANSIT类型虚拟路由器且本端防火墙关闭时，本端虚拟路由器必须绑定具有DCI能力的网关或租户必须绑定独立DCI网关 · When no CIDRs are specified, the internal subnet specified for the local vRouter cannot overlap with the access subnet for the firewall bound to the remote vRouter：未指定CIDR时，本端虚拟路由器的内网子网和对端虚拟路由器的防火墙接入网段重叠 · When you specify CIDRs for the local and remote vRouters, the local CIDRs cannot overlap with the access subnet for the firewall bound to the remote vRouter：指定CIDR时，本端的CIDR和对端虚拟路由器的防火墙接入网段重叠 · The access subnet for the firewall bound to the vRouter cannot include the source IP address in any route entry：虚拟路由器的防火墙接入网段和源IP地址重叠 · The access subnet for the firewall bound to each end in the centralized vRouter link cannot include the source IP address in any route entry：集中式虚拟路由器连接中虚拟路由器的防火墙接入网段和源IP地址存在重叠 · The local CIDRs and subnets cannot overlap with the access subnet for the firewall bound to the remote vRouter：本端的CIDR和子网与对端虚拟路由器的防火墙接入网段存在重叠 · The remote CIDRs and subnets cannot overlap with the access subnet for the firewall bound to the local vRouter：对端的CIDR和子网与本端虚拟路由器的防火墙接入网段存在重叠 · If you enable firewall for both ends in the vRouter link, they must use the same firewall service type：集中式虚拟路由器连接两端的防火墙开关开启时，两端防火墙类型必须一致 · If you enable firewall for one end in the vRouter link, the firewall service type specified for that end cannot be service leaf：集中式虚拟路由器连接一端的防火墙开关开启时，其防火墙必须为非Service Leaf类型 · If the following conditions exist, you must enable route reduction for a centralized vRouter link: ¡ You have disabled firewall for both ends in the vRouter link. ¡ One end is using service leaf firewall services. 集中式虚拟路由器连接两端的防火墙开关关闭，且一端的虚拟路由器绑定了Service Leaf类型防火墙和外部网络时，路由精简开关必须开启 · If a transit vRouter is bound to the vRouter link and a vRouter in that link is enabled with firewall, the firewall service type specified for the vRouter cannot be service leaf：集中式虚拟路由器连接绑定TRANSIT类型虚拟路由器时，防火墙开关开启侧的虚拟路由器不允许绑定Service Leaf类型防火墙 For a centralized vRouter link, you must bind border gateways to the local and remote vRouters when both the local and remote firewalls are off and service leaf firewalls are bound to the vRouters：当集中式虚拟路由器连接的两端防火墙关闭，且两个虚拟路由器同时绑定Service Leaf防火墙时，本端和对端虚拟路由器必须绑定出口网关 · To connect a normal-type vRouter to multiple remote vRouters of any types, make sure the destination subnets specified for the remote vRouters do not overlap：NORMAL类型虚拟路由器与多个虚拟路由器（不限定类型）建立连接时，目的网段不能重叠 · When you configure a centralized VAS vRouter link, configure the role of the local firewall as primary or secondary. The role of the local firewall cannot be both primary and secondary：集中式VAS VPC互通场景，本端防火墙配置角色主和备不能同时配置也不能同时为空 · When you configure a centralized non-VAS vRouter link, you cannot configure the role of the local firewall：非集中式VAS VPC互通场景，本端防火墙配置角色不能配置 · When you configure a centralized VAS vRouter link, enable the firewall service for the local transit vRouter：集中式VAS VPC互通场景，本端防火墙必须开启 · When you configure a centralized VAS vRouter link, disable the firewall service for the remote transit vRouter：集中式VAS VPC互通场景，对端防火墙必须关闭 · When you edit a centralized VAS vRouter link, you cannot change the role of the local firewall：集中式VAS VPC互通场景，本端防火墙配置角色不支持修改 · When you configure a centralized VAS vRouter link, disable both local route advertisement and remote route advertisement：集中式VAS VPC互通场景，发布本端所有路由和发布对端所有路由开关必须都关闭 · When you configure a centralized VAS vRouter link, the local transit vRouter must be bound to a DCI-capable border gateway and a firewall service resource：集中式VAS VPC互通场景，本端虚拟路由器必须绑定具备DCI能力的出口网关和防火墙资源 · When you configure a centralized VAS vRouter link, make sure the service resource ID of the local firewall is the same as that bound to the local transit vRouter：集中式VAS VPC互通场景，本端防火墙的服务资源ID和本端虚拟路由器绑定的服务资源ID必须一致 · If an east-west transit vRouter link enabled with remote route advertisement shares one transit vRouter with a centralized VAS vRouter link, the following items cannot overlap:1. Destination subnets configured for the route entries on the local vRouter of the east-west transit vRouter link.2. CIDRs configured for the remote vRouter of the centralized VAS vRouter link：TRANSIT类型虚拟路由器分别与两台虚拟路由器建立VAS VPC互通和发布对端所有路由开启的东西向TRANSIT VPC互通，东西向TRANSIT VPC互通的本端虚拟路由器的路由表项目的网段不能与VAS VPC互通的对端虚拟路由器CIDR重叠 · If the following conditions exist, you cannot establish a vRouter link between an external transit vRouter and a transit vRouter: 1. A gateway member of the border gateway bound to the external transit vRouter belongs to the same device group as that of a border gateway bound to the transit vRouter. 2. The tags field of the external transit vRouter is not empty：EXTERNALTRANSIT和TRANSIT类型虚拟路由器绑定的出口网关的出口网关成员关联了同一个设备组，EXTERNALTRANSIT类型虚拟路由器的tags字段不为空时，两者不允许创建虚拟路由器连接 · An external transit vRouter cannot establish vRouter links with both a normal vRouter and a transit vRouter：EXTERNALTRANSIT类型的虚拟路由器不能同时与TRANSIT类型虚拟路由器和NORMAL类型虚拟路由器建立虚拟路由器连接 · L3VNI configuration is supported only in the scenario where either the local or remote firewall is enabled：仅单边过墙场景支持配置L3VNI · RT %s of the vRouter link conflicts with an RT of the vRouter：虚拟路由器连接的互通RT %s与虚拟路由器RT冲突 · RT %s reserved for the vRouter link conflicts with an RT of the vRouter：系统预留的虚拟路由器连接互通RT %s与虚拟路由器RT冲突 · RT %s of the vRouter link conflicts with the import RT of a Layer 3 DC interconnect：虚拟路由器连接的互通RT %s与数据中心三层互联的引入RT冲突 · RT %s reserved for the vRouter link conflicts with the import RT of a Layer 3 DC interconnect：系统预留的虚拟路由器连接互通RT %s与数据中心三层互联的引入RT冲突 · RT %s of the vRouter link conflicts with the export RT of a Layer 3 DC interconnect：虚拟路由器连接的互通RT %s与数据中心三层互联的引出RT冲突 · RT %s reserved for the vRouter link conflicts with the export RT of a Layer 3 DC interconnect：系统预留的虚拟路由器连接互通RT %s与数据中心三层互联的引出RT冲突 · RT %s of the vRouter link conflicts with the import RT of a Layer 2 DC interconnect：虚拟路由器连接的互通RT %s与数据中心二层互联的引入RT冲突 · RT %s reserved for the vRouter link conflicts with the import RT of a Layer 2 DC interconnect：系统预留的虚拟路由器连接互通RT %s与数据中心二层互联的引入RT冲突 · RT %s of the vRouter link conflicts with the export RT of a Layer 2 DC interconnect：虚拟路由器连接的互通RT %s与数据中心二层互联的引出RT冲突 · RT %s reserved for the vRouter link conflicts with the export RT of a Layer 2 DC interconnect：系统预留的虚拟路由器连接互通RT %s与数据中心二层互联的引出RT冲突 · Resource application or rollback failed, internal unknown error：资源申请或回滚失败，内部未知错误 · The（resource）does not exist or the resources are insufficient：（资源）不存在或资源不足 · The（resource）does not exist or the resources are insufficient, device group name（name）：（资源）不存在或资源不足，设备组名称（名称） · The （resource） does not exist or the resources are insufficient, resource access template name （name）：（资源）不存在或资源不足，资源接入模板名称（名称） · The specified L3VNI is not in the VXLAN pool：指定的L3VNI不在VXLAN池范围内 · Cannot allocate this L3VNI, because synchronization is in progress for the VXLAN pool containing this L3VNI：无法分配该L3VNI，其所在的VXLAN池正在平滑中 · Cannot allocate L3VNIs automatically, because no VXLAN pool is configured：未配置VXLAN池，无法自动分配L3VNI · Cannot allocate L3VNIs automatically, because the VXLAN pool does not have available resources：VXLAN池中资源已耗尽，无法自动分配L3VNI · Cannot allocate L3VNIs automatically. Please verify correctness of the VXLAN pool configuration and status：无法自动分配L3VNI，请检查VXLAN池配置及状态 · The L3VNI is in use：指定的L3VNI已被使用 The L4-L7 physical resource pool templates bound to the two firewalls must contain vRouter link interfaces if: 1. Both ends of a centralized vRouter link use the firewall service. 2. The contexts created on the two selected firewalls are different：集中式虚拟路由器连接两端防火墙开启且两端防火墙对应的虚拟防火墙不同时，L4-L7物理资源池模板中必须配置跨虚拟路由器互通接口 · You cannot enable the host route advertisement feature if the value for the Mode field is 0 or 1：MODE为0或1时，不允许开启发布主机路由开关 |
|
关键字 |
UPDATE_ VPC_CONNECTION_OP |
|
日志内容 |
Updated VPC connection $1. |
|
参数解释 |
$1：虚拟路由器连接的参数体 |
|
举例 |
Updated VPC connection { "id":"e594591e-27ba-45e9-8792-9ce5ca29b0ed", "vpc_connection_id":"e594591e-27ba-45e9-8792-9ce5ca29b0ed", "fw_enabled":"e594591e-27ba-45e9-8792-9ce5ca29b0ed", "name":"vpc1", "tenant_id":"ffffffff-0000-0000-0000-000000000001", "description":"aaaaaaaaa", "local_router":"ffffffff-0000-0000-0000-000000000001", "local_cidrs":"[10.10.10.10/24]", "local_subnets"":"[073ceea5-4c17-4b24-8eb0-18407ca420e8]", "local_firewall_enable"":"false", "peer_router":"355973f6-69dd-4018-82f3-8ba3159ddf1e", "peer_cidrs":"[20.20.20.20/24]", "peer_subnets"":"[2de17490-4293-448d-9eee-b82aa446b4db]", "peer_firewall_enable"":"false", "mode":"0", "cloud_region_name":"openstack", }. |
|
日志说明 |
用户进行了修改虚拟路由器连接的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The specified resource doesn't exist：指定的资源不存在 · The status field is a read-only field：status为只读字段 · The local subnetID is required：本端虚拟子网ID不能为空 · The remote subnet ID is required：对端虚拟子网ID不能为空 · The local subnet list contains nonexistent subnets：本端子网列表中包含不存在的子网 · The remote subnet list contains nonexistent subnets：对端子网列表中包含不存在的子网 · The local vRouter cannot be modified：本端虚拟路由器不允许修改 · The remote vRouter cannot be modified：对端虚拟路由器不允许修改 · The tenant cannot be modified：租户不允许修改 · A remote subnet of the vRouter interconnection overlaps with a remote subnet of a Layer 3 DC interconnection. The subnet of the vRouter interconnection must cover the overlapping subnet of the Layer 3 DC interconnection：虚拟路由器互通的对端子网范围必须大于数据中心三层互联同网段的远端子网范围 · The vRouter interconnection name cannot exceed 255 characters：虚拟路由器连接名称不能大于255个字符 · The vRouter interconnection description cannot exceed 255 characters：虚拟路由器连接描述不能大于255个字符 · The network to which the remote subnet belongs cannot be a VLAN：对端子网所属的虚拟链路层网络不能为VLAN类型 · The remote subnet cannot be an external subnet：对端子网不能为外网子网 · The network to which the local subnet belongs cannot be a VLAN：本端子网所属的虚拟链路层网络不能为VLAN类型 · The local subnet cannot be an external subnet：本端子网不能为外网子网 · If a vRouter is bound to multiple vRouter interconnections, the selected subnets of the other vRouters bound to these vRouter interconnections cannot overlap：多个虚拟路由器连接绑定同一虚拟路由器时，连接绑定的另一个虚拟路由器之间的已选子网不能重叠 · Unknown error：未知错误 · The local_router and peer_router fields must be configured：local_router和peer_router字段不允许为空 · When the value of the Mode field is 1, local subnets and remote subnets are not supported：MODE为1时，不支持local_subnets和peer_subnets字段 · Local CIDRs cannot overlap with remote subnets：本端网段和对端路由器下的所有子网不允许重叠 · The local vRouter has established links with multiple vRouters and the CIDRs specified for the peer vRouters of the local vRouter cannot overlap：本端虚拟路由器与多个虚拟路由器建立连接时，不支持目的网段重叠 · Local subnets cannot overlap with remote subnets：本端路由器子网和对端路由器子网的网段不允许重叠 · Local CIDRs cannot overlap with remote CIDRs：本端网段和对端网段不允许重叠 · Cannot edit the local or remote router：不允许修改本端路由器和对端路由器 · Invalid subnet mask：掩码位非法 · Invalid IP address：无效的IP地址 · The remote vRouter has established links with multiple vRouters and the CIDRs specified for the peer vRouters of the remote vRouter cannot overlap：对端虚拟路由器与多个虚拟路由器建立连接时，不支持目的网段重叠 · When the value of the Mode field is 1, local CIDRs are required：MODE为1时，本端网段不能为空 · When the value of the Mode field is 1, remote CIDRs are required：MODE为1时，远端网段不能为空 · Duplicated CIDRs exist in local or remote CIDRs：本端网段/远端网段中存在网段重叠 · The mode field cannot be modified：mode字段不允许修改 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · You cannot edit or delete the cloud region name：云区域名称不允许修改或删除 · All OpenStack-based cloud platforms have been isolated：所有的云平台已被隔离 · You cannot change the enabling status of the local or remote firewall：本端或对端防火墙开关不允许修改 · Remote CIDRs cannot overlap with local subnets：对端网段和本端路由器下的所有子网不允许重叠 · Local subnets cannot overlap with local cidrs：本端子网和本端网段不允许重叠 · Peer subnets cannot overlap with peer cidrs：对端子网和对端网段不允许重叠 · You must specify local subnets, local CIDRs, or both：本端子网和本端网段不允许同时为空 · You must specify remote subnets, remote CIDRs, or both：对端子网和对端网段不允许同时为空 · When the firewall mode is normal, the vRouter type cannot be PBR：防火墙Mode为NORMAL时，虚拟路由器不支持PBR类型 · When the firewall mode is normal, the local and remote vRouters cannot both be transit nodes：防火墙Mode为NORMAL时，不支持本端虚拟路由器和对端虚拟路由器同时为Transit类型 · You cannot enable the firewall feature for the remote vRouter, because the remote vRouter type is transit：对端虚拟路由器类型为TRANSIT时，不支持开启防火墙 · You cannot enable the firewall feature for the local vRouter, because the local vRouter type is transit：本端虚拟路由器类型为TRANSIT时，不支持开启防火墙 · You cannot advertise all remote networks：当前不支持开启发布对端所有路由 · You cannot advertise all local networks：当前不支持开启发布本端所有路由 · The subnet parameter and CIDR network parameter must both be null for a transit vRouter：Transit类型虚拟路由器子网和网段必须同时为null · The subnet parameter and CIDR network parameter cannot both be null for a normal vRouter：Normal类型虚拟路由器子网和网段不允许同时为null · If the normal vRouter on a vRouter link advertises all networks, the transit vRouter on the vRouter link must also advertise all networks：NORMAL虚拟路由器发布所有路由字段为开启时，TRANSIT虚拟路由器发布所有路由字段不支持关闭 · If a transit vRouter has been used to create a firewall protected VPC connection, the vRouter cannot be used to create VPC connection disabled with the firewall feature, and vice versa：同一Transit虚拟路由器不支持同时创建过墙与不过墙两种类型的VPC互通 · The normal vRouter in a transit VPC enabled with the firewall feature must be bound to a DCI-capable gateway or firewall：在过墙Transit VPC中,NORMAL类型的虚拟路由器没有绑定具有DCI能力的网关或防火墙 · The normal vRouter in a transit VPC without firewall protection or the tenant of the vRouter must be bound to a gateway with the DCI capability：在不过墙Transit VPC中,NORMAL类型的虚拟路由器或所属租户没有绑定具有DCI能力的网关 · When you advertise all local networks, the subnet parameter and CIDR network parameter must both be null for the local vRouter：发布本端所有路由开启时，本端虚拟路由器子网和网段必须同时为null · When you advertise all remote networks, the subnet parameter and CIDR network parameter must both be null for the remote vRouter：发布对端所有路由开启时，对端虚拟路由器子网和网段必须同时为null · The subnet parameter and CIDR network parameter cannot both be null for the remote vRouter：对端虚拟路由器子网和网段不允许同时为null · The vRouter is not bound to a firewall：虚拟路由器没有绑定防火墙资源 · The firewall enabling state cannot be changed：防火墙开关不支持修改 · When a vRouter link is established between a normal vRouter and a transit vRouter, you cannot enable the advertising all networks feature for the normal vRouter when the advertising all networks feature is disabled for the transit vRouter：不支持NORMAL虚拟路由器端发布所有路由开启且TRANSIT虚拟路由器端发布所有路由关闭 · The manually specified networks cannot overlap with external subnets bound to the vRouter：手动输入网段不能与虚拟路由器绑定的外网子网网段重叠 · If a centralized-mode vRouter link, routing table, and Layer 3 DCI are attached to the same vRouter, you cannot specify the same subnet as a remote CIDR, destination subnet, and remote subnet for them, respectively：当集中式虚拟路由器连接、路由表和数据中心三层互联关联同一个虚拟路由器时，对端网段、目的网段和远端网段不能相同 · You cannot enable route reduction in the network cloud scenario：网络云场景下，不允许开启路由精简开关 · In non-network cloud scenarios, you can enable route reduction for a centralized-mode vRouter link only when the peer vRouters are normal type and the firewalls are disabled at both ends of the link：非网络云场景下，集中式虚拟路由器连接本端和对端防火墙都为关闭，且本端和对端虚拟路由器类型为NORMAL时，才允许开启路由精简开关 · Incorrect configuration for the host route advertisement feature：当前配置下，发布主机路由开关取值错误 · You cannot modify the configuration for the host route advertisement feature if the type of the peer vRouter is normal：对端虚拟路由器类型是NORMAL类型，不支持修改发布主机路由开关 · If the external transit vRouter is the remote vRouter in a centralized vRouter link, you must enable advertisement of all remote routes：集中式虚拟路由器连接绑定EXTERNALTRANSIT类型虚拟路由器时，发布对端所有路由开关必须开启 · Local CIDRs cannot overlap with the external subnets specified for the remote vRouter：本端网段和对端路由器多数据中心外网网段信息不允许重叠 · The VLAN range pool does not exist or no VLAN IDs are available in the VLAN range pool：指定的租户承载网类型的VLAN池不存在，或该VLAN池内没有足够的VLAN ID · The address pool does not exist or no IPv4 or IPv6 addresses are available in the address pool: 指定的地址池不存在，或该地址池内没有可用的IPv4/IPv6地址 · To connect a normal-type vRouter to multiple remote vRouters of any types, make sure the destination subnets specified for the remote vRouters do not overlap：NORMAL类型虚拟路由器与多个虚拟路由器（不限定类型）建立连接时，目的网段不能重叠 · When you configure a centralized VAS vRouter link, configure the role of the local firewall as primary or secondary. The role of the local firewall cannot be both primary and secondary：集中式VAS VPC互通场景，本端防火墙配置角色主和备不能同时配置也不能同时为空 · When you configure a centralized non-VAS vRouter link, you cannot configure the role of the local firewall：非集中式VAS VPC互通场景，本端防火墙配置角色不能配置 · When you configure a centralized VAS vRouter link, enable the firewall service for the local transit vRouter：集中式VAS VPC互通场景，本端防火墙必须开启 · When you configure a centralized VAS vRouter link, disable the firewall service for the remote transit vRouter：集中式VAS VPC互通场景，对端防火墙必须关闭 · When you edit a centralized VAS vRouter link, you cannot change the role of the local firewall：集中式VAS VPC互通场景，本端防火墙配置角色不支持修改 · When you configure a centralized VAS vRouter link, disable both local route advertisement and remote route advertisement：集中式VAS VPC互通场景，发布本端所有路由和发布对端所有路由开关必须都关闭 · When you configure a centralized VAS vRouter link, the local transit vRouter must be bound to a DCI-capable border gateway and a firewall service resource：集中式VAS VPC互通场景，本端虚拟路由器必须绑定具备DCI能力的出口网关和防火墙资源 · When you configure a centralized VAS vRouter link, make sure the service resource ID of the local firewall is the same as that bound to the local transit vRouter：集中式VAS VPC互通场景，本端防火墙的服务资源ID和本端虚拟路由器绑定的服务资源ID必须一致 · If an east-west transit vRouter link enabled with remote route advertisement shares one transit vRouter with a centralized VAS vRouter link, the following items cannot overlap:1. Destination subnets configured for the route entries on the local vRouter of the east-west transit vRouter link.2. CIDRs configured for the remote vRouter of the centralized VAS vRouter link：TRANSIT类型虚拟路由器分别与两台虚拟路由器建立VAS VPC互通和发布对端所有路由开启的东西向TRANSIT VPC互通，东西向TRANSIT VPC互通的本端虚拟路由器的路由表项目的网段不能与VAS VPC互通的对端虚拟路由器CIDR重叠 · Resource application or rollback failed, internal unknown error：资源申请或回滚失败，内部未知错误 · The（resource）does not exist or the resources are insufficient：（资源）不存在或资源不足 · The（resource）does not exist or the resources are insufficient, device group name（name）：（资源）不存在或资源不足，设备组名称（名称） · The （resource） does not exist or the resources are insufficient, resource access template name （name）：（资源）不存在或资源不足，资源接入模板名称（名称） · You cannot enable the host route advertisement feature if the value for the Mode field is 0 or 1：MODE为0或1时，不允许开启发布主机路由开关 |
|
关键字 |
DELETE_VPC_CONNECTION_OP |
|
日志内容 |
Deleted VPC connection $1. |
|
参数解释 |
$1：虚拟路由器连接的参数体 |
|
举例 |
Deleted VPC connection { "id":"e594591e-27ba-45e9-8792-9ce5ca29b0ed", "vpc_connection_id":"e594591e-27ba-45e9-8792-9ce5ca29b0ed", "fw_enabled":"e594591e-27ba-45e9-8792-9ce5ca29b0ed", "name":"vpc1", "tenant_id":"ffffffff-0000-0000-0000-000000000001", "description":"aaaaaaaaa", "local_router":"ffffffff-0000-0000-0000-000000000001", "local_cidrs":"[10.10.10.10/24]", "local_subnets"":"[073ceea5-4c17-4b24-8eb0-18407ca420e8]", "local_firewall_enable"":"false", "peer_router":"355973f6-69dd-4018-82f3-8ba3159ddf1e", "peer_cidrs":"[20.20.20.20/24]", "peer_subnets"":"[2de17490-4293-448d-9eee-b82aa446b4db]", "peer_firewall_enable"":"false", "mode":"0", "cloud_region_name":"openstack", }. |
|
日志说明 |
用户进行了删除虚拟路由器连接的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The specified resource doesn't exist：指定的资源不存在 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · All OpenStack-based cloud platforms have been isolated：所有的云平台已被隔离 · Resource application or rollback failed, internal unknown error：资源申请或回滚失败，内部未知错误 · The（resource）does not exist or the resources are insufficient：（资源）不存在或资源不足 · The（resource）does not exist or the resources are insufficient, device group name（name）：（资源）不存在或资源不足，设备组名称（名称） · The （resource） does not exist or the resources are insufficient, resource access template name （name）：（资源）不存在或资源不足，资源接入模板名称（名称） |
|
关键字 |
CREATE_SECURITY_GROUP_OP |
|
日志内容 |
Created security group $1. |
|
参数解释 |
$1：安全组的参数体 |
|
举例 |
Created security group { "id":"85cc3048-abc3-43cc-89b3-377341426ac6", "name":"default", "tenant id":"2b2151a2-f111-40f0-a0ea-61a76879e972", "tenant name":"admin2333", "rules":"[{ "direction":"ingress", "ether type":"IPv4", "id":"0cf4ffd7-4e7c-4fac-98c4-8c301d6d3015", "port range max":"65534", "port range min":"65534", "protocol":"udp", "remote group id":"null", "remote ip prefix":"0.0.0.0/0", "description":"", "security group id":"bcf2512f-e8c9-40d2-98ef-a8ab1df1b8d9", "tenant id":"2b2151a2-f111-40f0-a0ea-61a76879e972", "cloud region name":"default", }]", "cloud region name":"default" }. |
|
日志说明 |
用户进行了创建安全组的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · Duplicate security policy UUID：安全策略UUID冲突 · Security policies created in bulk cannot use the same ID：批量创建的安全策略的ID存在重复 · Invalid empty rule action：无效的空规则行为 · The security policy name cannot exceed 255 characters：安全策略名称最长255个字符 · The ip_mac_bingding is required：未指定IP-MAC防欺骗参数 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 · All OpenStack-based cloud platforms have been isolated：所有的云平台已被隔离 · No system VDS is specified：未指定系统虚拟分布式交换机 · The gateway list contains gateways that do not have members：出口网关列表中存在未配置成员的网关 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
UPDATE_SECURITY_GROUP_OP |
|
日志内容 |
Updated security group $1. |
|
参数解释 |
$1：安全组参数体 |
|
举例 |
Updated security group { "id":"85cc3048-abc3-43cc-89b3-377341426ac5", "name":"mysecgroup", "tenant id":"ae511e66-546b-45a2-ad3e-a46cf64600a3", "tenant name":"admin2333", "rules":"null", "cloud region name":"default" }. |
|
日志说明 |
用户进行了修改安全组的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The security policy ID is required：未指定安全策略UUID · Invalid empty rule action：无效的空规则行为 · The specified resource doesn't exist：指定的资源不存在 · The security policy name cannot exceed 255 characters：安全策略名称最长255个字符 · The specified tenant ID cannot be modified：已指定的租户ID不允许修改 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · You cannot edit or delete the cloud region name：云区域名称不允许修改或删除 · All OpenStack-based cloud platforms have been isolated：所有的云平台已被隔离 |
|
关键字 |
DELETE_SECURITY_GROUP_OP |
|
日志内容 |
Deleted security group $1. |
|
参数解释 |
$1：安全组的参数体 |
|
举例 |
Deleted security group { "id":"85cc3048-abc3-43cc-89b3-377341426ac6", "name":"default", "tenant id":"2b2151a2-f111-40f0-a0ea-61a76879e972", "rules":"[{ "direction":"ingress", "ether type":"IPv4", "id":"0cf4ffd7-4e7c-4fac-98c4-8c301d6d3015", "port range max":"65534", "port range min":"65534", "protocol":"udp", "remote group id":"null", "remote ip prefix":"0.0.0.0/0", "description":"", "security group id":"85cc3048-abc3-43cc-89b3-377341426ac6", "tenant id":"2b2151a2-f111-40f0-a0ea-61a76879e972", "cloud region name":"default", }]", "cloud region name":"default" }. |
|
日志说明 |
用户进行了删除安全组的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The security policy has been bound to a port or a port group：安全策略已被端口组或者虚拟端口绑定 · The specified resource doesn't exist：指定的资源不存在 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 · All OpenStack-based cloud platforms have been isolated：所有的云平台已被隔离 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
CREATE_SECURITY_GROUP_RULE_OP |
|
日志内容 |
Created security group rule $1. |
|
参数解释 |
$1：安全规则的参数体 |
|
举例 |
Created security group rule { "direction":"ingress", "ether type":"IPv4", "id":"93aa42e5-80db-4581-9391-3a608bd0e448", "port range max":"null", "port range min":"null", "protocol":"null", "remote group id":"null", "remote ip prefix":"null", "description":"rule2", "security group id":"85cc3048-abc3-43cc-89b3-377341426ac5", "tenant id":"2b2151a2-f111-40f0-a0ea-61a76879e972", "cloud region name":"default" }. |
|
日志说明 |
用户进行了创建安全组规则的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · Invalid security policy UUID：无效的安全策略UUID · Duplicate security rule UUID：安全规则UUID冲突 · Security rules created in bulk cannot use the same UUID：批量创建的安全规则的UUID存在重复 · The new security rule conflicts with the old rules：该安全规则与已存在的安全规则冲突 · Invalid IP version：无效的IP版本 · Invalid IP prefix：无效的IP前缀 · Invalid protocol type：无效的协议类型 · Invalid port range：无效的端口范围 · Invalid ICMP type：无效的ICMP报文类型 · Invalid ICMP code：无效的ICMP代码 · Invalid direction：方向不可用 · Operation failed. The security policy rule failed to take effect because of insufficient hardware resources：操作失败，硬件资源不足导致安全策略规则无法生效 · The IP prefix and the security policy can't both be configured：不能同时配置IP前缀和安全策略 · The IP prefix and the IP version do not match：IP前缀与IP协议版本不匹配 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · All OpenStack-based cloud platforms have been isolated：所有的云平台已被隔离 |
|
关键字 |
UPDATE_SECURITY_GROUP_RULE_OP |
|
日志内容 |
Updated security group rule $1. |
|
参数解释 |
$1：安全组规则的参数体 |
|
举例 |
Updated security group rule { "direction":"ingress", "ether type":"IPv4", "id":"0cf4ffd7-4e7c-4fac-98c4-8c301d6d3015", "port range max":"65534", "port range min":"65534", "protocol":"udp", "remote group id":"null", "remote ip prefix":"0.0.0.0/0", "description":"default", "security group id":"bcf2512f-e8c9-40d2-98ef-a8ab1df1b8d9", "tenant id":"2b2151a2-f111-40f0-a0ea-61a76879e972", "cloud region name":"null" }. |
|
日志说明 |
用户进行了修改安全组规则的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The new security rule conflicts with the old rules：该安全规则与已存在的安全规则冲突 · Invalid IP version：无效的IP版本 · Invalid IP prefix：无效的IP前缀 · Invalid protocol type：无效的协议类型 · Invalid port range：无效的端口范围 · Invalid ICMP type：无效的ICMP报文类型 · Invalid ICMP code：无效的ICMP代码 · Invalid direction：方向不可用 · The specified resource doesn’t exist：指定的资源不存在 · Operation failed. The security policy rule failed to take effect because of insufficient hardware resources：操作失败，硬件资源不足导致安全策略规则无法生效 · The IP prefix and the security policy can't both be configured：不能同时配置IP前缀和安全策略 · The IP prefix and the IP version do not match：IP前缀与IP协议版本不匹配 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · You cannot edit or delete the cloud region name：云区域名称不允许修改或删除 · All OpenStack-based cloud platforms have been isolated：所有的云平台已被隔离 |
|
关键字 |
DELETE_SECURITY_GROUP_RULE_OP |
|
日志内容 |
Deleted security group rule $1. |
|
参数解释 |
$1：安全组规则的参数体 |
|
举例 |
Deleted security group rule { "direction":"ingress", "ether type":"IPv4", "id":"93aa42e5-80db-4581-9391-3a608bd0e448", "port range max":"null", "port range min":"null", "protocol":"null", "remote group id":"null", "remote ip prefix":"null", "description":"rule2", "security group id":"85cc3048-abc3-43cc-89b3-377341426ac5", "tenant id":"2b2151a2-f111-40f0-a0ea-61a76879e972", "cloud region name":"default" }. |
|
日志说明 |
用户进行了删除安全组规则的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The specified resource doesn't exist：指定的资源不存在 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · All OpenStack-based cloud platforms have been isolated：所有的云平台已被隔离 |
|
关键字 |
CREATE_VLANMAP_OP |
|
日志内容 |
Created VLAN-VXLAN mapping $1. |
|
参数解释 |
$1：VLAN-VXLAN映射的参数体 |
|
举例 |
Created VLAN-VXLAN mapping { "id":"null", "host id":"null", "host name":"null", "group id":"d266e3b2-8f5c-4a13-b9a1-034522de725a", "group name":"null", "vlan range":"120", "vxlan range":"2", "cloud region name":"openstack", }. |
|
日志说明 |
用户进行了创建VLAN-VXLAN映射的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The netoverlay host ID is required：Netoverlay主机ID不能为空 · The netoverlay host does not exist：Netoverlay主机不存在 · The VLAN ranges of hosts in a netoverlay cannot be the same：同一个Netoverlay主机不能配置重复的VLAN范围 · The VLAN ranges of hosts in a netoverlay already exists：Netoverlay主机上已存在指定的VLAN范围 · VLAN-VXLAN mappings cannot be added on a netoverlay host bound to a netoverlay group：Netoverlay主机已绑定Netoverlay集群时，不允许添加VLAN-VXLAN映射 · The netoverlay host and the netoverlay group cannot both be null：Netoverlay主机和Netoverlay集群不能同时为空 · The specified netoverlay group does not exist：指定的Netoverlay集群不存在 · The netoverlay host and the netoverlay group cannot be both configured：Netoverlay主机和Netoverlay集群不能同时配置 · The VLAN ID is required：VLAN ID不能为空 · The VXLAN ID is required：VXLAN ID不能为空 · The VLAN ID is out of range：VLAN ID超出范围 · The VXLAN ID is out of range：VXLAN ID超出范围 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 · All OpenStack-based cloud platforms have been isolated：所有的云平台已被隔离 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
DELETE_VLANMAP_OP |
|
日志内容 |
Deleted VLAN-VXLAN mapping $1. |
|
参数解释 |
$1：VLAN-VXLAN映射的参数体 |
|
举例 |
Deleted VLAN-VXLAN mapping { "id":"null", "host id":"null", "host name":"null", "group id":"d266e3b2-8f5c-4a13-b9a1-034522de725a", "group name":"null", "vlan range":"120", "vxlan range":"2", "cloud region name":"openstack", }. |
|
日志说明 |
用户进行了删除VLAN-VXLAN映射的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The specified resource doesn't exist：指定的资源不存在 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 · Cannot delete VLAN-VXLAN mapping because it was created on VMM：不允许删除来源为VMM的VLAN-VXLAN映射 · All OpenStack-based cloud platforms have been isolated：所有的云平台已被隔离 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
UPDATE_SUBNET_OP |
|
日志内容 |
Updated subnet $1. |
|
参数解释 |
$1：子网的参数体 |
|
举例 |
Updated subnet { "id":"54d6f61d-db07-451c-9ab3-b9609b6b6f0c", "name":"subnet1", "network id":"d32019d3-bc6e-4319-9c1d-6722fc136a33", "segment id":"null", "router id":"null", "tenant id":"4fd44f30-2929-45e4-81c7-b8a0c8908869", "cidr":"192.0.0.0/8", "ip version":"4", "gateway ip":"192.0.0.1", "enable dhcp":"true", "external":"null", "origin":"null", "cloud region name":"openstack" }. |
|
日志说明 |
用户进行了修改子网的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The subnet ID is required：未指定子网ID · The pool's start IP can't be higher than the end IP：地址池起始地址不能大于结束地址 · Please check the DHCP address pool for overlappingsubnets：DHCP地址池内网段重叠 · The IP addresses in the address pool don't belong to the subnet：地址池地址不在子网范围内 · Invalid routing table：无效的路由表 · Invalid IP address：无效的IP地址 · The domain name can't exceed 255 characters：计算域名称应少于255个字符 · Invalid server identifier：服务器标示符不可用 · The format of the host route destination is invalid：主机路由目的网段格式不正确 · The format of the host route next hop is invalid：主机路由下一跳格式不正确 · The configuration contains duplicate host routes：配置包含重复的主机路由 · The address pool of the internal subnet can't be modified：内网子网的地址池不允许修改 · The specified resource doesn't exist：指定的资源不存在 · The subnet is not bound to a vRouter：该子网没有绑定的虚拟路由器 · The configuration contains duplicate DNS：配置包含重复的DNS · The subnet name cannot exceed 255 characters：虚拟子网名称最长255个字符 · The gateway IP address doesn’t belong to the subnet：网关IP地址与子网不在同一网段 · The gateway IP address conflicts with the subnet broadcast address：网关IP地址和子网广播IP地址冲突 · The gateway IP address conflicts with the subnet address：网关IP地址和子网IP地址冲突 · An external subnet must be configured with a gateway IP address：外网子网的网关IP地址不能为空 · Subnets not configured with a gateway IP address cannot be enabled with DHCP：未配置网关IP地址的子网不允许使能DHCP功能 · The gateway IP for the subnet of a VLAN cannot be null：VLAN类型网络的子网，网关IP不能为空 · Cannot modify the gateway IP address for the subnet, because the subnet is bound to a vRouter：该子网已被虚拟路由器绑定，不允许修改网关IP地址 · The gateway IP address is already used by a vPort：指定的网关IP地址已被虚拟端口占用 · The gateway IP address is already used by an APP cluster VIP：指定的网关IP地址已被应用集群虚IP占用 · The gateway IP address is already used by a floating IP：指定的网关IP地址已被浮动IP占用 · You must specify whether to enable DHCP for the subnet or not：未指定虚拟子网是否使能DHCP功能 · The segment UUID can't be delete or modify：子网绑定的Segment不允许修改和解绑 · An IP address in the DHCP address pool has been automatically assigned to an online vPort. The DHCP address pool must still contain the IP address after being edited：DHCP地址池中存在已上线的虚拟端口，修改后的DHCP地址池必须包含该虚拟端口IP地址 · The DHCP address pool cannot contain IP addresses that have been manually assigned to online vPorts：修改后的DHCP地址池范围内存在静态配置IP地址的已上线虚拟端口 · An IP address in the DHCP address pool has been automatically assigned to an online vPort. The DHCP address pool must still contain the IP address after being edited：DHCP地址池中存在已上线的虚拟端口，修改后的DHCP地址池必须包含该虚拟端口IP地址 · The DHCP address pool cannot contain IP addresses that have been manually assigned to online vPorts：修改后的DHCP地址池范围内存在静态配置IP地址的已上线虚拟端口 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 · Cannot edit the primary IP allocation setting for a subnet if the subnet is already used for primary IP allocation：不允许修改主IP所在的子网 · The gateway IP address has been used as the primary IP address：指定的网关IP地址已被主IP使用 · The external subnet contains an IP address that has been assigned to a vPort. You cannot bind the external subnet to an NQA profile：该外网子网中存在被虚拟端口指定的IP地址，不支持绑定NQA策略 · The specified NQA profile has been bound to another service resource：指定NQA策略已经被服务资源绑定 · The specified NQA profile does not exist：指定的NQA策略不存在 · Cannot bind the subnet to an NQA profile. The border gateway in the subnet has been bound to a track entry：NQA策略绑定失败，指定子网已绑定配置了Track项的出口网关 · A vNetwork supports only one primary IP：一个虚拟链路层网络下只允许有一个主IP · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · You cannot edit or delete the cloud region name：云区域名称不允许修改或删除 · All OpenStack-based cloud platforms have been isolated：所有的云平台已被隔离 · You cannot bind a NQA profile to the external IPv4 subnet, because primary IP allocation has been enabled for the subnet：外部网络IPv4子网已配置主IP，不允许绑定NQA策略 · You cannot specify an NQA profile for the external subnet. The gateway address for the subnet is the same as the next hop address of a route entry configured with an NQA profile, and the route entry has been bound to the same vRouter as the subnet：当外网子网网关IP与所属虚拟路由器的路由表项下一跳IP地址相同，且该路由表项已绑定NQA策略，则外网子网不允许绑定NQA策略 · You cannot specify an NQA profile for the external subnet. The gateway address for the subnet is the same as the next hop address of a route entry configured with an NQA profile, and the route entry has been bound to the same vRouter as the subnet：当外网子网网关IP与所属虚拟路由器的路由表项下一跳IP地址相同，且该路由表项已绑定NQA策略，则外网子网不允许绑定NQA策略 · You cannot bind an NQA profile to a subnet of a directly connected external network：独享型外部网络子网不支持绑定NQA策略 · You cannot unbind the subnet from the vRouter. This is because the routing table bound to the vRouter contains a route entry that uses an IP address in the subnet as the next hop, and the route entry is configured with a BFD session：当前虚拟路由器存在下一跳IP地址属于该子网且配置了BFD会话的路由表项，不允许解绑该子网 · The protocol IP format is invalid：协议IP格式无效 · You can configure a protocol IP for only one subnet in a vNetwork：同一个虚拟链路层网络下，最多只有一个子网能配置协议IP · The protocol IP conflicts with a vPort IP or gateway IP：协议IP与虚拟端口IP或网关IP冲突 · You must specify two protocol IPs：协议IP仅支持配置两个地址 · The protocol IPs must belong to the subnet：协议IP必须在子网范围内 · Only IPv4 subnets support the protocol IP parameter：仅IPv4子网支持配置协议IP · The subnet broadcast address cannot be configured as a protocol IP：协议IP不支持配置为子网广播地址 · You cannot specify a subnet address as a protocol IP：协议IP不支持配置为子网IP地址 · If DHCP is enabled, the subnet mask length for IPv4 cannot be 31 and the prefix length for IPv6 cannot be 127：IPv4版本且开启DHCP时，子网网段不允许配置31位掩码；IPv6版本且开启DHCP时，子网网段不允许配置127前缀长度 · You cannot specify an extended SNAT IP address as a gateway IP address in the same external network：扩展SNAT IP地址不能与子网网关IP地址冲突 · The lease duration exceeds the limit：租约时间超出了范围限制 · The specified NQA profile has been bound to a service path：该NQA策略已经被服务路径绑定 |
|
关键字 |
DELETE_SUBNET_OP |
|
日志内容 |
Deleted subnet $1. |
|
参数解释 |
$1：子网的参数体 |
|
举例 |
Deleted subnet { "id":"54d6f61d-db07-451c-9ab3-b9609b6b6f0c", "name":"subnet1", "network id":"d32019d3-bc6e-4319-9c1d-6722fc136a33", "segment id":"null", "router id":"null", "tenant id":"4fd44f30-2929-45e4-81c7-b8a0c8908869", "cidr":"192.0.0.0/8", "ip version":"4", "gateway ip":"192.0.0.1", "enable dhcp":"true", "external":"null", "origin":"null", "cloud region name":"openstack" }. |
|
日志说明 |
用户进行了删除子网的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · A port resides on the subnet：虚拟子网存在端口 · The port group has not been unbound from the subnet：请先删除端口组 · The subnet has not been unbound from the router：请先解除和虚拟路由器的绑定关系 · An APP cluster VIP resides on the subnet：该子网内存在应用集群虚IP · The specified resource doesn't exist：指定的资源不存在 · The external subnet has floating IPs：外网子网存在浮动IP · The subnet has been bound to a vRouter interconnection：该子网已被虚拟路由器连接绑定 · The subnet has been bound to a Layer 3 DC interconnection：该子网已被数据中心三层互联绑定 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 · The vNetwork is an interface-specific multicast network. You cannot unbind its only subnet from the vRouter：指定的虚拟链路层网络已经绑定组播接口，该虚拟链路层网络下的最后一个子网不允许解绑虚拟路由器 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · All OpenStack-based cloud platforms have been isolated：所有的云平台已被隔离 · You cannot delete the subnet, because it contains extended SNAT IP addresses：指定的子网中包含扩展SNAT IP地址，不允许删除 · IP addresses in the subnet used for primary IP allocation have been allocated：主IP所在子网已分配IP地址 · You cannot delete the subnet, because it has been specified for the ingress or egress vPort of a third-party service device bound to a service path：指定子网已被第三方服务设备的出入虚拟端口使用，且该第三方服务设备已被服务路径使用，不允许删除 |
|
关键字 |
DELETE_SUBNET_DEVCHECK_OP |
|
日志内容 |
Checked the state of southbound devices upon subnet deletion. |
|
参数解释 |
无 |
|
举例 |
Checked the state of southbound devices upon subnet deletion. |
|
日志说明 |
用户删除虚拟子网时，云插件校验了南向设备失联状态 |
|
失败原因 |
当操作失败时，可能的原因如下： · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
CREATE_TENANT_OP |
|
日志内容 |
Created tenant $1. |
|
参数解释 |
$1：租户的参数体 |
|
举例 |
Created tenant { "id":"ae511e66-546b-45a2-ad3e-a46cf64600af", "name":"admin2" }. |
|
日志说明 |
用户进行了创建租户的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service has not been found：未找到相应的服务 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · The length of name is too long：传入的JSON串中租户名称的长度太长 · Invalid parameter：无效的配置参数 · The tenant already exists：租户已存在 · The tenant name is required：租户名称不允许为空 · The VDS ID is required：VDS ID不能为空 · Invalid VDS ID ：无效的VDS ID · You have no privilege to perform this operation：用户无权限执行此操作 · Up to 255 characters, case sensitive：参数不能超过255个字符，区分大小写 · All OpenStack-based cloud platforms have been isolated：所有的云平台已被隔离 |
|
关键字 |
UPDATE_TENANT_OP |
|
日志内容 |
Updated tenant $1. |
|
参数解释 |
$1：租户的参数体 |
|
举例 |
Updated tenant { "id":"ae511e66-546b-45a2-ad3e-a46cf64600af", "name":"2" } |
|
日志说明 |
用户进行了修改租户的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service has not been found：未找到相应的服务 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Invalid JSON format：无效的JSON格式 · The length of name is too long：传入的JSON串中租户名称的长度太长 · Invalid parameter：无效的配置参数 · The tenant name is required：租户名称不允许为空 · Can't modify the default tenant：默认租户不允许修改 · The VDS ID cannot be modified：VDS ID不允许修改 · The NEM service does not exist：NEM服务不存在 · Cannot modify the auto allocation setting because the tenant has automatically allocated resources：该租户下已存在自动分配的资源，不允许修改自动分配功能 · You have no privilege to perform this operation：用户无权限执行此操作 · You cannot edit or delete the cloud region name：云区域名称不允许修改或删除 · You cannot edit or delete the domain name：租户所属域不允许修改或删除 · Up to 255 characters, case sensitive：参数不能超过255个字符，区分大小写 · All OpenStack-based cloud platforms have been isolated：所有的云平台已被隔离 · The border gateway has been bound to a vRouter configured with a south-north service chain：出口网关已被虚拟路由器绑定，并且虚拟路由器下配置了南北向服务链 |
|
关键字 |
DELETE_TENANT_OP |
|
日志内容 |
Delete tenant $1. |
|
参数解释 |
$1：租户的参数体 |
|
举例 |
Deleted tenant { "id":"ae511e66-546b-45a2-ad3e-a46cf64600af", "name":"admin2" }. |
|
日志说明 |
用户进行了删除租户的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The service has not been found：未找到相应的服务 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置正在恢复过程中 · Can't delete the default tenant：默认租户不允许删除 · The tenant has bound resources：租户已绑定资源 · A vPort has been configured for the tenant：本租户已配置虚拟端口 · You have no privilege to perform this operation：用户无权限执行此操作 · The tenant has already been bound to a gateway：该租户已经绑定出口网关 · An OSPF or OSPFv3 policy has been configured for the tenant：该租户已配置OSPF或OSPFv3策略 · A route policy has been configured for the tenant：该租户已配置路由策略 · An IP prefix has been configured for the tenant：该租户已配置地址前缀 · A security policyhas been configured for the tenant：本租户已配置安全策略 · A vRouter link hasbeen configured for the tenant：本租户已配置虚拟路由器连接 · A vRouterinterconnection has been configured for the tenant：本租户已配置虚拟路由器互通 · A network has been configured for the tenant：本租户已配置虚拟链路层网络 · A vRouter has been configured for the tenant：本租户已配置虚拟路由器 · All OpenStack-based cloud platforms have been isolated：所有的云平台已被隔离 |
|
关键字 |
ISOLATE_SETTING_OP |
|
日志内容 |
Setting platform isolate state $1. |
|
参数解释 |
$1：隔离配置的参数体 |
|
举例 |
Setting platform isolate state: { "uuid":"9a1b9306-81a4-4fb6-856f-40fdf6a0c731", "type":"VCENTER", "state":"false" }. |
|
日志说明 |
用户进行了设置平台隔离状态的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · Invalid platform type for the isolation action：无效的隔离平台类型 · Please specify the isolation state of the platform：平台的隔离状态不能为空 · The specified vCenter does not exist：指定的vCenter不存在 · The specified RedHat VM does not exist：指定的RHVM不存在 · Unknown error：未知错误 |
|
关键字 |
CREATE_SYSTEM_CENTER_OP |
|
日志内容 |
Created System Center $1. |
|
参数解释 |
$1：System Center参数体 |
|
举例 |
Created System Center { "uuid":"cd05ab0b-d499-435b-80a5-d594282eb525", "name":"SC", "ip address":"192.168.125.1", "port number":"10002", "vlan pool":"null", "connect status":"false" "certificate name":"null" }. |
|
日志说明 |
用户进行了创建System Center的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · Unknown error code：未知错误 · The controller is not the active leader：该设备不是当前Leader控制组件 · Server processing error：服务器处理失败 · The UUID already exists：该UUID已存在 · Invalid System Center name：无效的System Center名称 · Invalid username：无效的用户名称 · Invalid password：无效的用户密码 · The port number must be an integer in the range of 0 to 65535：端口号必须为0~65535的整数 · Invalid IP address：无效的IP地址 · Please specify a VLAN pool configured for tenant access networks：输入的VLAN池非租户接入网类型 · The specified VLAN pool does not exist：指定的VLAN池不存在 · The VLAN pool has already been used by another resource：指定的VLAN池已被其他资源引用 · The System Center name already exists：System Center名称已存在 · The IP address already exists：IP地址已存在 · Failed to bind the System Center to a VLAN pool：System Center绑定VLAN池失败 · Duplicate System Center IPs in bulk creation：批量创建的System Center的IP存在重复 · Duplicate System Center names in bulk creation：批量创建的System Center的名称存在重复 · Duplicate System Center UUIDs in bulk creation：批量创建的System Center的UUID存在重复 · Duplicate System Center VLAN pools in bulk creation：批量创建的System Center的VLAN资源池存在重复 · You have no privilege to perform this operation：用户无权限执行此操作 · The specified certificate does not exist or is not activated：指定证书不存在或者未被激活 · The specified certificate does not exist：指定的证书不存在 · The specified certificate is invalid：指定的证书内容不合法 |
|
关键字 |
UPDATE_SYSTEM_CENTER_OP |
|
日志内容 |
Updated System Center $1. |
|
参数解释 |
$1：System Center的参数体 |
|
举例 |
Updated System Center { "uuid":"96bd9627-caf0-436e-aad1-885fe62ec274", "name":"SC", "ip address":"192.168.25.3", "port number":"443", "vlan pool":"null", "connect status":"false", "certificate name":"null" }. |
|
日志说明 |
用户进行了修改System Center的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · Unknown error code：未知错误 · The controller is not the active leader：该设备不是当前Leader控制组件 · Server processing error：服务器处理失败 · The specified System Center does not exist：指定的System Center不存在 · Invalid username：无效的用户名称 · Invalid password：无效的用户密码 · Please specify a VLAN pool configured for tenant access networks：输入的VLAN池非租户接入网类型 · The specified VLAN pool does not exist：指定的VLAN池不存在 · The specified VLAN ID in the VLAN pool has been allocated：指定的VLAN池内资源已被分配 · The VLAN pool has already been used by another resource：指定的VLAN池已被其他资源引用 · Cannot edit the System Center name：System Center名称不允许修改 · The port number must be an integer in the range of 0 to 65535：端口号必须为0~65535的整数 · The IP address cannot be modified：IP地址不允许修改 · You have no privilege to perform this operation：用户无权限执行此操作 · The specified certificate does not exist or is not activated：指定证书不存在或者未被激活 |
|
关键字 |
DELETE_SYSTEM_CENTER_OP |
|
日志内容 |
Deleted System Center $1. |
|
参数解释 |
$1：System Center的参数体 |
|
举例 |
Deleted System Center { "uuid":"ecc6f914-79dc-4fe2-97f1-5714c30f7f1c", "name":"SC", "ip address":"192.168.23.3", "port number":"443", "vlan pool":"null", "connect status":"false", "certificate name":"null" }. |
|
日志说明 |
用户进行了删除System Center的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · Unknown error code：未知错误 · The controller is not the active leader：该设备不是当前Leader控制组件 · Server processing error：服务器处理失败 · The specified System Center does not exist：指定的System Center不存在 · Cannot delete the System Center, because it has logical switches：System Center下存在逻辑交换机，不允许删除 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_LOGICAL_SWITCH_OP |
|
日志内容 |
Created logical switch $1. |
|
参数解释 |
$1：logical switch参数体 |
|
举例 |
Created logical switch { "id":"41ee1d95-b26e-496e-83a3-72c370f58632", "name":"switch", "scvmm id":" ecc6f914-79dc-4fe2-97f1-5714c30f7f15" “scvmm name”:”SC” }. |
|
日志说明 |
用户进行了创建逻辑交换机的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置恢复未完成 · The controller is not the active leader：该设备不是当前Leader控制组件 · The request is invalid：传入的JSON串错误 · Illegal logical switch name：逻辑交换机名称不合法 · The specified System Center does not exist：指定的System Center不存在 · The specified logical switch does not exist：指定的逻辑交换机不存在 · Invalid logical switch name：无效的逻辑交换机名称 · logical switch already exists：逻辑交换机已存在 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_LOGICAL_SWITCH_OP |
|
日志内容 |
Deleted logical switch $1. |
|
参数解释 |
$1：逻辑交换机参数体 |
|
举例 |
Deleted logical switch { "id":"41ee1d95-b26e-496e-83a3-72c370f58632", "name":"21", "scvmm id":" ecc6f914-79dc-4fe2-97f1-5714c30f7f15", “scvmm name”:”switch” } |
|
日志说明 |
用户进行了删除逻辑交换机的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置恢复未完成 · The controller is not the active leader：该设备不是当前Leader控制组件 · The logical switch does not exist：指定的逻辑交换机不存在 · Cannot delete the logical switch, because it has logical switches：指定的逻辑交换机下存在VM网络，不允许删除 · The specified System Center does not exist：指定的System Center不存在 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_VMNETWORK_OP |
|
日志内容 |
Created VM network $1. |
|
参数解释 |
$1：VM网络参数体 |
|
举例 |
Created VM network { "id":"da51f7ee-8d3f-4b62-8759-5ab93603f42b", "name":"default|zjtnetwork|123", "scvmm id":"cec54ab1-ed88-4df6-b31e-ae81736738f6", "scvmm name":"SC", "logical switch id":"1e5eb3c5-3873-47b0-80b8-004a32d409e1", "logical switch name":"switch", "tenant id":"2b2151a2-f111-40f0-a0ea-61a76879e972", "tenant name":"admin", "vnetwork id":"a1b2c184-2da1-4e73-b0ce-59c8b49e1c50", "vnetwork name":"vnet", "vlan range":"66" }. |
|
日志说明 |
用户进行了创建VM网络的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该设备不是当前Leader控制组件 · The request is invalid：传入的JSON串错误 · Invalid parameter：参数不合法 · Invalid UUID：无效的UUID · The specified System Center does not exist：指定的System Center不存在 · The specified vNetwork does not exist：指定的虚拟链路层网络不存在 · The specified tenant does not exist：指定的租户不存在 · The specified VLAN ID in the VLAN pool has been allocated：指定的VLAN池内资源已被分配 · Please configure a VLAN ID for the VM network because the System Center bound to the VM network is not configured with a VLAN pool：当System Center未分配VLAN池时，VM网络需手动配置VLAN ID · No VLAN ID is available in the VLAN pool：VLAN池中无可分配的VLAN ID · The VLAN ID must be an integer in the range of 1 to 4094：VLAN ID的取值范围必须为1-4094的整数 · Invalid VM network name：无效的VM网络名称 · The specified VM network already exists：指定的VM网络已存在 · A VM network with the same VLAN ID already exists in the selected System Center. You must assign the two VM networks to the same vNetwork：对于同一个System Center，如果两个不同逻辑交换机下的VM网络的VLAN ID相同，则两个VM网络的虚拟链路层网络必须相同 · Please change the VLAN ID. A VM network with the same VLAN ID attached to the specified logical switch already exists in the selected System Center：同一个逻辑交换机下的两个不同VM网络不能有相同VLAN ID · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_VMNETWORK_OP |
|
日志内容 |
Deleted VM network $1. |
|
参数解释 |
$1：VM网络参数体 |
|
举例 |
Deleted VM network { "id":"da51f7ee-8d3f-4b62-8759-5ab93603f42b", "name":"default|zjtnetwork|123", "scvmm id":"cec54ab1-ed88-4df6-b31e-ae81736738f6", "scvmm name":"SC", "logical switch id":"1e5eb3c5-3873-47b0-80b8-004a32d409e1", "logical switch name":"switch", "tenant id":"2b2151a2-f111-40f0-a0ea-61a76879e972", "tenant name":"admin", "vnetwork id":"a1b2c184-2da1-4e73-b0ce-59c8b49e1c50", "vnetwork name":"vnet", "vlan range":"66" }. |
|
日志说明 |
用户进行了删除逻辑网络的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该设备不是当前Leader控制组件 · The specified VM network does not exist：指定的VM网络不存在 · Cannot delete the VM network, because it has VMs：VM网络下存在VM，不允许删除 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
AUDIT_SCVMM_OP |
|
日志内容 |
Audited data for System Center: $1. |
|
参数解释 |
$1：System Center名称 |
|
举例 |
Audited data for System Center: SystemCenter. |
|
日志说明 |
用户进行了System Center的差异发现的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置恢复未完成 · The controller is not the active leader：该设备不是当前Leader控制组件 · The specified System Center does not exist：指定的System Center不存在 · The connection state of the System Center is abnormal：指定的System Center连接状态异常 · The system is auditing or synchronizing data for the System Center. Please try again later.：指定的System Center正在进行差异发现或差异修复，请稍后再试 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
SYNC_SCVMM_OP |
|
日志内容 |
Synchronized data for System Center: $1. |
|
参数解释 |
$1：System Center名称 |
|
举例 |
Synchronized data for System Center: SystemCenter. |
|
日志说明 |
用户进行了System Center的差异修复的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置恢复未完成 · The controller is not the active leader：该设备不是当前Leader控制组件 · The specified System Center does not exist：指定的System Center不存在 · The connection state of the System Center is abnormal：指定的System Center连接状态异常 · The system is auditing or synchronizing data for the System Center. Please try again later.：指定的System Center正在进行差异发现或差异修复，请稍后再试 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_SCVMM_SMOOTH_SETTING_OP |
|
日志内容 |
Updated auto audit and sync settings for System Centers: audit interval:$1 minutes, auto audit state:$2, auto sync state:$3, audit schedule:$4, Schedule:{ "months":$5, "days of week":$6, "days of month":$7, "hh":$8, "mm":$9, "ss":$10 }. |
|
参数解释 |
$1：对账周期 $2：自动对账开关 $3：自动修复开关 $4：对账模式 $5：每月 $6：每周 $7：每天 $8：时 $9：分 $10：秒 |
|
举例 |
Updated auto audit and sync settings for System Centers: audit interval:null minutes, auto audit state:true, auto sync state:OFF, audit schedule:TIMING, Schedule:{ "months":"*", "days of week":"?", "days of month":"*", "hh":"19", "mm":"40", "ss":"0" }. |
|
日志说明 |
用户进行了修改自动对账&修复配置参数的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置恢复未完成 · The controller is not the active leader：该设备不是当前Leader控制组件 · The request is invalid：传入的JSON串错误 · The value of the auto sync interval must be an integer in the range of 60 to 10080：自动同步周期必须为60～10080的整数 · Invalid auto smooth setting：无效的auto_smooth_setting · Invalid sync parameters：无效的自动修复参数 · You have no privilege to perform this operation：用户无权限执行此操作 · Invalid audit schedule：无效的对账模式 · When the audit schedule is interval-based, you must specify the audit interval：当对账模式为周期对账时，对账间隔不能为空 · Please configure Cron expression parameters：Cron表达式参数不能为空 · Invalid Cron expression parameters：无效的Cron表达式参数 |
|
关键字 |
STANDBY_VCENTER_HOST_OP |
|
日志内容 |
Standby vCenter host $1. |
|
参数解释 |
$1：vCenter主机参数体 |
|
举例 |
Standby vCenter host { "id":"5f79544e-cb58-46e4-998b-d5887865ec09", "vcenter host id":"host-70", "name":"192.168.1.225", "vcenter id":"c389ce2d-5a53-4062-8235-9346b0f28bba", "dc name":"Datacenter", "state":"notResponding", "power state":"standBy", "vm number":"0", "hardware up time":"0", "idle time":"1" }. |
|
日志说明 |
用户进行了待机vCenter主机的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置恢复未完成 · The controller is not the active leader：该设备不是当前Leader控制器 · The vCenter host does not exist：指定的vCenter主机不存在 · The host does not exist on vCenter：vCenter上不存在指定的主机 · You cannot place the vCenter host in standby state, because VMs exist on the host：虚拟机数量不为0，不允许待机 · The vCenter host cannot be placed in standby state：该主机不支持待机 · You cannot place the vCenter host in standby state, because the vCenter host is not connected：主机连接状态不是已连接，不允许待机 · You cannot place the vCenter host in standby state, because its state is standby, entering standby, or awaking up：电源状态为待机、待机中或唤醒中的主机不允许待机 · The task already exists and is in progress：任务已存在且正在执行中 |
|
关键字 |
AWAKE_VCENTER_HOST_OP |
|
日志内容 |
Awake vCenter host $1. |
|
参数解释 |
$1：vCenter主机参数体 |
|
举例 |
Awake vCenter host { "id":"5f79544e-cb58-46e4-998b-d5887865ec09", "vcenter host id":"host-70", "name":"192.168.1.225", "vcenter id":"c389ce2d-5a53-4062-8235-9346b0f28bba", "dc name":"Datacenter", "state":"notResponding", "power state":"standBy", "vm number":"0", "hardware up time":"0", "idle time":"1" }. |
|
日志说明 |
用户进行了唤醒vCenter主机的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置恢复未完成 · The controller is not the active leader：该设备不是当前Leader控制器 · The vCenter host does not exist：指定的vCenter主机不存在 · The host does not exist on vCenter：vCenter上不存在指定的主机 · You cannot wake up the vCenter host, because the vCenter host is not in standby state：主机未处于待机状态，不允许唤醒 · The vCenter host cannot be placed in waking up state：该主机不支持唤醒 · The task already exists and is in progress：任务已存在且正在执行中 |
|
关键字 |
CREATE_KUBERNETES |
|
日志内容 |
Create Kubernetes: $1 |
|
参数解释 |
$1：Kubernetes参数体 |
|
举例 |
Create Kubernetes: [ { "certificateName":"sdnc_monitor.crt", "cniMode":"BRIDGE", "connected":false, "dataSyncStatus":"INIT", "id":"535805ad-f9c4-4071-adaf-0ea4f16c3e28", "lastSyncTime":1682238093000, "tenant_id": "5f8114b0-2e2f-4294-969d-d84027772b22", "masterNodeDtos":[
], "name":" l2131", "privateKey":"sdnc_monitor.key" } ] |
|
日志说明 |
用户进行了创建Kubernetes的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid JSON format：JSON格式错误 · Invalid UUID：无效的UUID · Please specify the Kubernetes platform name：Kubernetes的名称必填 · The Kubernetes platform name is a string of up to 255 characters：Kubernetes的名称最长255个字符 · Invalid CNI mode：无效的CNI模式 · Please specify the certificate：必须指定证书 · The suffix of the certificate name must be cer：证书名称的后缀必须是.cer · Please specify the private key：必须指定私钥 · The suffix of the private key must be key：私钥的后缀必须是.key · The UUID already exists：UUID已存在 · The Kubernetes platform name already exists：指定的Kubernetes名称已存在 · The certificate does not exist or is not activated：指定证书不存在或者未被激活 · The private key does not exist or is not activated：指定的私钥不存在或者未被激活 · Please specify the tenant ID：租户ID必填 · The specified tenant does not exist：指定的租户不存在 |
|
关键字 |
UPDATE_KUBERNETES |
|
日志内容 |
Update Kubernetes: $1 |
|
参数解释 |
$1：Kubernetes参数体 |
|
举例 |
Update kubernetes: { "certificateName":"sdnc_monitor.crt", "cniMode":"BRIDGE", "connected":false, "dataSyncStatus":"INIT", "id":"535805ad-f9c4-4071-adaf-0ea4f16c3e28", "lastSyncTime":1682238093000, "masterNodeDtos":[
], "name":" l2131", "privateKey":"sdnc_monitor.key" } |
|
日志说明 |
用户进行了修改Kubernetes的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Please specify the UUID：必须指定UUID · The Kubernetes platform does not exist：指定的Kubernetes不存在 · Please specify the certificate：必须指定证书 · The suffix of the certificate name must be cer：证书名称的后缀必须是.cer · Please specify the private key：必须指定私钥 · The suffix of the private key must be key：私钥的后缀必须是.key · The certificate does not exist or is not activated：指定证书不存在或者未被激活 · The private key does not exist or is not activated：指定的私钥不存在或者未被激活 |
|
关键字 |
DELETE_KUBERNETES |
|
日志内容 |
Delete Kubernetes: $1 |
|
参数解释 |
$1：Kubernetes的UUID |
|
举例 |
Delete kubernetes: "535805ad-f9c4-4071-adaf-0ea4f16c3e28" |
|
日志说明 |
用户进行了删除Kubernetes的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Please specify the UUID：必须指定UUID · The Kubernetes platform does not exist：指定的Kubernetes不存在 |
|
关键字 |
DATA_SYNCHRONIZE |
|
日志内容 |
Synchronized Kubernetes: $1 |
|
参数解释 |
$1：Kubernetes的UUID |
|
举例 |
Synchronized Kubernetes: "535805ad-f9c4-4071-adaf-0ea4f16c3e28" |
|
日志说明 |
用户进行了同步Kubernetes数据的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Please specify the UUID：必须指定UUID · The Kubernetes platform does not exist：指定的Kubernetes不存在 · Failed to connect to the Kubernetes platform：指定的Kubernetes连接异常 · Data is synchronizing from the Kubernetes platform. Please try again later：指定的Kubernetes正在进行数据同步，请稍后再试 |
本节介绍VNF Manager模块输出的操作日志信息。
|
关键字 |
CREATE_VNFD_OP |
|
日志内容 |
Created VNF descriptor: $1 |
|
参数解释 |
$1：VNF Descriptor信息 |
|
举例 |
Created VNF descriptor: { "name": "VNFDescriptor5G", "image": "VSR1000_H3C-CMW710-D0314P01-X64", "flavor": "1_cpu_1024MB_memory_8192MB_storage", "extended_config": "telnet server enable", "network_binding": [ { "host_name":"63", "availability_zone": "nova", "host_ip":"192.168.67.63", "vm_ports": [ { "vm_port_name": "Interface1/0", "host_nic": "ens161", "vm_port_index": 1, "vm_port_type": "external", }] }], "interface_binding": [ { "interface_name": "Reth44", "interface_type": "Reth", "memberInterfaces": [ "Interface2/0" ], "serviceType": "internal,external,virtual_router_interconnect" } ], "advanced_config": { "setting_disable_security_group": false }, "login_username": "admin" } |
|
日志说明 |
用户进行了创建VNF Descriptor的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The VNF descriptor already exists：VNF Descriptor已存在 · The VNF image file doesn’t exist：VNF镜像不存在 · The VNF flavor doesn’t exist：VNF Flavor不存在 · The start IP address must be smaller than or equal to the end IP address：起始IP地址必须小于等于结束IP地址 · Invalid parameter：参数不正确 · The host doesn't exist：主机不存在 · Invalid IP address：无效的IP地址 · Invalid subnet mask：无效的子网掩码 · The VNFM service is not started：VNFM服务未开启 · Server processing error：服务器处理失败 · Incorrect interface binding parameters for the VNF descriptor：VNF Descriptor中接口绑定参数错误 · The host authentication failed：主机认证失败 · The NIC doesn't exist on the host：主机上的网卡不存在 · Invalid IP address：无效的IP地址 · Invalid subnet mask：无效的子网掩码 · Invalid license：License不合法 · The specified availability zone doesn't exist.：指定的可用域不存在 · A CAS host does not support physical CPU binding：CAS类型的主机不支持绑定物理CPU · The hosts must be the same type in the Descriptor template used for creating HA VNFs：用于创建高可用VNF的Descriptor模板所选主机类型需一致 · A CAS host in the Descriptor template should be compute host：Descriptor模板中所选CAS主机需为计算节点 · For one descriptor or two different descriptors, the address pools configured for the same NIC of a host cannot overlap：相同Descriptor/不同Descriptor间，相同主机且相同网卡的IP地址池不能冲突 · Make sure the IP addresses assigned to the interfaces of the Descriptor are from non-overlapping subnets：Descriptor中不同接口的IP地址网段不能冲突 |
|
关键字 |
DELETE_VNFD_OP |
|
日志内容 |
Deleted VNF descriptor: $1 |
|
参数解释 |
$1：VNF Descriptor名称 |
|
举例 |
Deleted VNF descriptor: vnfd-1442766462213 |
|
日志说明 |
用户进行了删除VNF Descriptor的操作 |
|
失败原因 |
· The VNFM service is not started：VNFM服务未开启 · Server processing error：服务器处理失败 · Failed to delete the VNF descriptor because it is being used：该VNF Descriptor正在被使用，无法删除 · Invalid license：License不合法 |
|
关键字 |
UPDATE_VNFD_OP |
|
日志内容 |
Update VNF descriptor: $1 |
|
参数解释 |
$1：VNF Descriptor信息 |
|
举例 |
Update VNF descriptor: { "name": "vnfd1", "image": "vBRAS1000_H3C-CMW710-D0504-X64.qco", "network_binding": [ { "vm_ports": [ { "vm_port_name": "Interface1/0" } ] } ], "interface_binding": [] } |
|
日志说明 |
用户进行了修改VNF Descriptor的操作 |
|
失败原因 |
· The VNF image file doesn’t exist：VNF镜像不存在 · The VNF flavor doesn’t exist：VNF Flavor不存在 · The start IP address must be smaller than or equal to the end IP address：起始IP地址必须小于等于结束IP地址 · Invalid parameter：参数不正确 · The host doesn't exist：主机不存在 · Invalid IP address：无效的IP地址 · Invalid subnet mask：无效的子网掩码 · The VNFM service is not started：VNFM服务未开启 · Server processing error：服务器处理失败 · Incorrect interface binding parameters for the VNF descriptor：VNF Descriptor中接口绑定参数错误 · The host authentication failed：主机认证失败 · The NIC doesn't exist on the host：主机上的网卡不存在 · Invalid IP address：无效的IP地址 · Invalid subnet mask：无效的子网掩码 · Invalid license：License不合法 · For one descriptor or two different descriptors, the address pools configured for the same NIC of a host cannot overlap：相同Descriptor/不同Descriptor间，相同主机且相同网卡的IP地址池不能冲突 · Make sure the IP addresses assigned to the interfaces of the Descriptor are from non-overlapping subnets：Descriptor中不同接口的IP地址网段不能冲突 |
|
关键字 |
ADD_FLAVOR_OP |
|
日志内容 |
Added flavor: $1 |
|
参数解释 |
$1：VNF Flavor信息 |
|
举例 |
Added flavor: { "id":"403cc5e9-8f31-4379-9c01-7a93dba58c18", "name": "large", "ram": 1024, "vcpus": 2, "disk": 8192, "is_irf":false } |
|
日志说明 |
用户进行了创建VNF Flavor的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The VNF flavor already exists：VNF Flavor已存在 · Invalid parameter：参数不正确 · The parameters do not match the specification：参数与规格不匹配 · The VNFM service is not started：VNFM服务未开启 · Server processing error：服务器处理失败 · Invalid license：License不合法 |
|
关键字 |
DELETE_FLAVOR_OP |
|
日志内容 |
Deleted flavor: $1 |
|
参数解释 |
$1：VNF Flavor名称 |
|
举例 |
Deleted flavor: large |
|
日志说明 |
用户进行了删除VNF Flavor的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The VNFM service is not started：VNFM服务未开启 · Server processing error：服务器处理失败 · The default configuration can’t be deleted：默认配置不可删除 · Invalid license：License不合法 · Can't delete the VNF flavor because it is used by a VNF descriptor：该Flavor被Descriptor引用，删除失败 |
|
关键字 |
CREATE_VNF_OP |
|
日志内容 |
Created VNF: $1 |
|
参数解释 |
$1：VNF信息 |
|
举例 |
Created VNF: { "name":"vnf", "vnf_descriptor_name":"vnf_descriptor", “vnf_count”:”2” } |
|
日志说明 |
用户进行了创建VNF的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid VNF name：无效的VNF名称 · The VNF already exists：VNF已经存在 · The VNF descriptor doesn't exist：指定的VNF Descriptor不存在 · The VNF image file doesn’t exist：VNF镜像不存在 · The VNF flavor doesn’t exist：VNF Flavor不存在 · There are incorrect parameters for host binding：主机绑定参数中存在错误 · The NIC doesn't exist on the host：主机上的网卡不存在 · The host authentication failed：主机认证失败 · Failed to create the VNF on the host：在主机上创建VNF失败 · Invalid parameter：无效的参数 · Server processing error：服务器处理失败 · The VNFM service is not started：VNFM服务未开启 · Invalid license：License不合法 · The host doesn't exist：主机不存在 · Invalid IP address：无效的IP地址 · Invalid subnet mask：无效的子网掩码 |
|
关键字 |
DELETE_VNF_OP |
|
日志内容 |
Deleted VNF: $1 |
|
参数解释 |
$1：VNF名称 |
|
举例 |
Deleted VNF: aa |
|
日志说明 |
用户进行了删除VNF的操作 |
|
失败原因 |
· The VNFM service is not started：VNFM服务未开启 · Server processing error：服务器处理失败 · Invalid license：License不合法 |
|
关键字 |
ADD_ HOST _OP |
|
日志内容 |
Added host: $1 |
|
参数解释 |
$1：主机信息 |
|
举例 |
Added host: { "name": "host_sample", “host_type”: ”VIM”, “ip_version”: “ipv4”, "ip_address": "10.10.10.10", "user": "admin", "tenant": "admin", "port": "5000", "domain": "default", "url_type": "public" "identify_version": "V3" } Added host: { "name": "host_sample", “host_type”: ”CAS”, “ip_version”: “ipv4”, "ip_address": "10.10.10.10", "user": "admin", "port": "8080", "protocol_type": "HTTP" } |
|
日志说明 |
用户进行了添加主机的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The host already exists：主机已存在 · Invalid parameter：无效的参数 · The host authentication failed：主机认证失败 · Invalid IP address：无效的IP地址 · The VNFM service is not started：VNFM服务未开启 · Server processing error：服务器处理失败 · Invalid license：License不合法 · The CAS service is unavailable：CAS服务不可用 |
|
关键字 |
UPDATE_HOST_OP |
|
日志内容 |
Updated host: $1 |
|
参数解释 |
$1：主机信息 |
|
举例 |
Updated host : { "name": "host_sample", “host_type”: ”VIM”, "ip": "10.10.10.10", "user": "admin", "tenant": "admin", "port": "5000", "domain": "default", "url_type": "public" "identify_version": "V3", } Updated host : { "name": "host_sample", “host_type”: ”CAS”, "ip": "10.10.10.10", "user": "admin", "port": "8080", " protocol_type ": "HTTP", } |
|
日志说明 |
用户进行了添加主机的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid parameter：无效的参数 · The host doesn`t exist:：主机不存在 · Invalid IP address：无效的IP地址 · You cannot change the VIM type：主机类型不允许修改 · The host name and the IP address do not match：主机名称和IP地址不匹配 · Compute doesn’t allowed to modify：计算节点不允许修改 · The host authentication failed：主机认证失败 · The VNFM service is not started：VNFM服务未开启 · Server processing error：服务器处理失败 · Invalid license：License不合法 |
|
关键字 |
DELETE_HOST_OP |
|
日志内容 |
Deleted host: $1 |
|
参数解释 |
$1：主机名称 |
|
举例 |
Deleted host: 254_4 |
|
日志说明 |
用户进行了删除主机的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · There are VNFs running on the host. Please delete the VNFs first：主机上有VNF存在，请先删除VNF · The VNFM service is not started：VNFM服务未开启 · Server processing error：服务器处理失败 · Invalid license：License不合法 |
|
关键字 |
UPLOAD_IMAGE_OP |
|
日志内容 |
Uploaded image: $1 |
|
参数解释 |
$1：VNF镜像名称 |
|
举例 |
Uploaded image: VSR1000_H3C-CMW710-D0314P02.qco |
|
日志说明 |
用户进行了上传VNF镜像的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The image file already exists：镜像已经存在 · The file uploaded is incorrect：上传的文件错误 · Failed to upload the file：文件上传失败 · The VNFM service is not started：VNFM服务未开启 · Invalid license：License不合法 · Failed to change the FTP directory：FTP切换目录操作失败 · Invalid parameter：无效的参数 · The file doesn't exist on the FTP server：FTP服务器上文件不存在 · The file doesn't exist：指定的文件不存在 |
|
关键字 |
DELETE_IMAGE_OP |
|
日志内容 |
Deleted image: $1 |
|
参数解释 |
$1：VNF镜像名称 |
|
举例 |
Deleted image: VSR1000_H3C-CMW710-D0314P02.qco |
|
日志说明 |
用户进行了删除VNF镜像的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The VNFM service is not started：VNFM服务未开启 · Server processing error：服务器处理失败 · Invalid license：License不合法。 · Can't delete the image because it is used by a VNF descriptor：该镜像被Descriptor引用，删除失败 |
|
关键字 |
REFERENCE_IMAGE_OP |
|
日志内容 |
Referemce_image: name: $1 openstack_image_id: $2 |
|
参数解释 |
$1：VNF镜像名称 $2：VNF镜像在OpenStack上的ID |
|
举例 |
Reference_image: name: vBRAS1000_H3C-CMW710-E0324L03-X64.qco openstack_image_id: 8f5cef9c-3dd8-4ddb-a461-82cadf63f42c |
|
日志说明 |
用户进行了引用VNF镜像的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The VNFM service is not started：VNFM服务未开启 · Server processing error：服务器处理失败 · Invalid license：License不合法。 · The image file already exists：指定的镜像文件已经存在 |
|
关键字 |
Uploaded IPE: $1 |
|
日志内容 |
Uploaded IPE: $1 |
|
参数解释 |
$1：IPE文件名称 |
|
举例 |
Uploaded IPE: VSR1000-B62.ipe |
|
日志说明 |
用户进行了上传IPE文件的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The file already exists：文件已经存在 · The file uploaded is incorrect：上传的文件错误 · Failed to upload the file：文件上传失败 · The VNFM service is not started：VNFM服务未开启 · Server processing error：服务器处理失败 · Invalid license：License不合法 · Failed to change the FTP directory：FTP切换目录操作失败 · Invalid parameter：无效的参数 · The file doesn't exist on the FTP server：FTP服务器不存在该文件 · The file doesn't exist：指定的文件不存在 |
|
关键字 |
DELETE_IPE_OP |
|
日志内容 |
Deleted IPE: $1 |
|
参数解释 |
$1：IPE文件名称 |
|
举例 |
Deleted IPE: VSR1000-B62.ipe |
|
日志说明 |
用户进行了删除IPE文件的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The VNFM service is not started：VNFM服务未开启 · Server processing error：服务器处理失败 · Invalid license：License不合法 |
|
关键字 |
ISSU_VNF_OP |
|
日志内容 |
ISSU VNF: $1 |
|
参数解释 |
$1：VNF信息 |
|
举例 |
ISSU VNF: { "vnf_name":"vnf", "ipe_filename":"VSR-X64-base.ipe" } |
|
日志说明 |
用户进行了VNF ISSU升级的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The virtual machine is not ready for upgrade：升级准备未就绪 · The virtual machine failed to download the .ipe file：虚拟机下载IPE文件失败 · Failed to set the startup file for the master device：设置主设备的启动文件失败 · Compatibility check failed：兼容检查失败 · Failed to save the current configuration：设备保存当前配置失败 · ISSU upgrade failed：设备进行ISSU升级操作失败 · Can't get the management IP address：获取管理IP地址失败 · The VNFM service is not started：VNFM服务未开启 · Server processing error：服务器处理失败 · Invalid license：License不合法 · Invalid parameter：无效的参数 · Invalid JSON format：无效的JSON格式 |
|
关键字 |
REBOOT_VM_OP |
|
日志内容 |
Rebooted virtual machine: $1 |
|
参数解释 |
$1：虚拟机信息，包括所属主机名称和虚拟机ID |
|
举例 |
Rebooted virtual machine: { "vnf_name": "vnf1", "vm_id": "403cc5e9-8f31-4379-9c01-7a93dba58c18" } |
|
日志说明 |
用户进行了重启虚拟机的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The host doesn't exist：主机不存在 · The virtual machine doesn't exist：虚拟机不存在 · The virtual machine is busy. Please try again later：虚拟机正忙，请稍后再试 · The virtual machine can't perform the operation in this state：当前状态的虚拟机不能执行本操作 · The VNFM service is not started：VNFM服务未开启 · Server processing error：服务器处理失败 · Invalid license：License不合法 |
|
关键字 |
START_VM_OP |
|
日志内容 |
Started virtual machine: $1 |
|
参数解释 |
$1：虚拟机信息，包括所属主机名称和虚拟机ID |
|
举例 |
Started virtual machine: { "vnf_name": "vnf1", "vm_id": "403cc5e9-8f31-4379-9c01-7a93dba58c18" } |
|
日志说明 |
用户进行启动虚拟机的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The host doesn't exist：主机不存在 · The virtual machine doesn't exist：虚拟机不存在 · The virtual machine is busy. Please try again later：虚拟机正忙，请稍后再试 · The virtual machine can't perform the operation in this state：当前状态的虚拟机不能执行本操作 · The VNFM service is not started：VNFM服务未开启 · Server processing error：服务器处理失败 · Invalid license：License不合法 |
|
关键字 |
STOP_VM_OP |
|
日志内容 |
Stopped virtual machine: $1 |
|
参数解释 |
$1：虚拟机信息，包括所属主机名称和虚拟机ID |
|
举例 |
Stopped virtual machine: { "vnf_name": "vnf1", "vm_id": "403cc5e9-8f31-4379-9c01-7a93dba58c18" } |
|
日志说明 |
用户进行了停止虚拟机的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The host doesn't exist：主机不存在 · The virtual machine doesn't exist：虚拟机不存在 · The virtual machine is busy. Please try again later：虚拟机正忙，请稍后再试 · The virtual machine can't perform the operation in this state：当前状态的虚拟机不能执行本操作 · The VNFM service is not started：VNFM服务未开启 · Server processing error：服务器处理失败 · Invalid license：License不合法 |
本节介绍IPsec VPN服务模块输出的操作日志信息。
|
关键字 |
CREATE_IKEPOLICY_OP |
|
日志内容 |
Create IKE policy $1 |
|
参数解释 |
$1：IKE策略信息 |
|
举例 |
Create IKE policy Name: ikepolicy1 UUID: 5522aff7-1b3c-48dd-9c3c-b50f016b73db Description: ikepolicy1 IKE Version: v1 Auth Algorithm: sha1 Encryption Algorithm: aes-128 PFS: group5 Phase1 Negotiation Mode: main Lifetime: Units: seconds Value: 3600 |
|
日志说明 |
用户进行了创建IKE策略的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · The operation requires the administrator privilege：您需要管理员权限才能执行此操作 · The tenant doesn't exist：指定的租户不存在 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_IKEPOLICY_OP |
|
日志内容 |
Delete IKE policy $1 |
|
参数解释 |
$1: IKE策略的UUID |
|
举例 |
Delete IKE policy UUID: 5522aff7-1b3c-48dd-9c3c-b50f016b73db |
|
日志说明 |
用户进行了删除IKE策略的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · The operation requires the administrator privilege：您需要管理员权限才能执行此操作 · The IKE policy is in use：IKE策略正在被使用 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_IKEPOLICY_OP |
|
日志内容 |
Update IKE policy $1 |
|
参数解释 |
$1：IKE策略信息 |
|
举例 |
Update IKE policy Name: ikepolicy1 Description: ikepolicy1 IKE Version: v1 Auth Algorithm: sha1 Encryption Algorithm: aes-128 PFS: group5 Phase1 Negotiation Mode: main Lifetime: Units: seconds Value: 3600 |
|
日志说明 |
用户进行了修改IKE策略的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · The operation requires the administrator privilege：您需要管理员权限才能执行此操作 · The IKE policy is in use：IKE策略正在被使用 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_IPSECPOLICY_OP |
|
日志内容 |
Create IPsec policy $1 |
|
参数解释 |
$1：IPsec策略信息 |
|
举例 |
Create IPsec policy Name: policy UUID: 5291b189-fd84-46e5-84bd-78f40c05d69c Description: policy1 Encapsulation Mode: tunnel Transform Protocol: ESP Auth Algorithm: sha1 Encryption Algorithm: aes-128 Lifetime: Units: seconds Value: 3600 PFS: group5 |
|
日志说明 |
用户进行了创建IPsec策略的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · The operation requires the administrator privilege：您需要管理员权限才能执行此操作 · The tenant doesn't exist：指定的租户不存在 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_IPSECPOLICY_OP |
|
日志内容 |
Delete IPsec policy $1 |
|
参数解释 |
$1：IPsec策略的UUID |
|
举例 |
Delete IPsec policy UUID: 5291b189-fd84-46e5-84bd-78f40c05d69c |
|
日志说明 |
用户进行了删除IPsec策略的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · The operation requires the administrator privilege：您需要管理员权限才能执行此操作 · The IPsec policy is in use：IPsec策略正在被使用 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_IPSECPOLICY_OP |
|
日志内容 |
Update IPsec policy $1 |
|
参数解释 |
$1：IPsec策略信息 |
|
举例 |
Update IPsec policy Name: policy Description: policy1 Encapsulation Mode: tunnel Transform Protocol: AH Auth Algorithm: sha1 Encryption Algorithm: aes-128 Lifetime: Units: seconds Value: 3600 PFS: group5 |
|
日志说明 |
用户进行了修改IPsec策略的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · The operation requires the administrator privilege：您需要管理员权限才能执行此操作 · The IPsec policy is in use：IPsec策略正在被使用 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_VPNSERVICE_OP |
|
日志内容 |
Create VPN service $1 |
|
参数解释 |
$1：VPN服务信息 |
|
举例 |
Create VPN service Name: vpn1 UUID: 9faaf49f-dd89-4e39-a8c6-101839aa49bc Description: 33 Router Id: ec8619be-0ba8-4955-8835-3b49ddb76f89 Subnet Id: f4fb4528-ed93-467c-a57b-11c7ea9f963e Admin State Up: ACTIVE |
|
日志说明 |
用户进行了创建VPN服务的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · The operation requires the administrator privilege：您需要管理员权限才能执行此操作 · The VPN service can't be bound to external subnet：VPN服务不支持外部网络 · The tenant doesn't exist：指定的租户不存在 · The vRouter doesn’t exist：指定的虚拟路由器不存在 · The vSubnet doesn't exist：指定的虚拟子网不存在 · The VPN service and the specified vRouter belong to different tenants：该VPN服务与指定的虚拟路由器属于不同的租户 · The vSubnet is not bound to the specified vRouter：指定的虚拟子网未绑定指定的虚拟路由器 · Only an IPv4 subnet can be specified：仅支持指定IPv4子网 · All local subnets must use the same IP version：所有本端子网的IP版本必须一致 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_VPNSERVICE_OP |
|
日志内容 |
Delete VPN service $1 |
|
参数解释 |
$1：VPN服务的UUID |
|
举例 |
Delete VPN service UUID: 9faaf49f-dd89-4e39-a8c6-101839aa49bc |
|
日志说明 |
用户进行了删除VPN服务的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · The operation requires the administrator privilege：您需要管理员权限才能执行此操作 · The VPN service is in use：VPN服务正在被使用 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_VPNSERVICE_OP |
|
日志内容 |
Update VPN service $1 |
|
参数解释 |
$1：VPN服务信息 |
|
举例 |
Update VPN service Name: vpn1 UUID: 9faaf49f-dd89-4e39-a8c6-101839aa49bc Description: vpnservice1 |
|
日志说明 |
用户进行了修改VPN服务的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · The operation requires the administrator privilege：您需要管理员权限才能执行此操作 · The VPN service is in use：VPN服务正在被使用 · The vSubnet doesn't exist：指定的虚拟子网不存在 · The vSubnet is not bound to the specified vRouter：指定的虚拟子网未绑定指定的虚拟路由器 · Only an IPv4 subnet can be specified：仅支持指定IPv4子网 · All local subnets must use the same IP version：所有本端子网的IP版本必须一致 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_IPSEC_SITE_CONNS_OP |
|
日志内容 |
Create IPsec Site Connections $1 |
|
参数解释 |
$1：IPsec站点连接信息 |
|
举例 |
Create IPsec Site Connections Name: vpnconnection1 UUID: cbc152a0-7e93-4f98-9f04-b085a4bf2511 Description: connections 1 VPN Service Id: c2f3178d-5530-4c4a-89fc-050ecd552636 IKE Policy Id: bf5612ac-15fb-460c-9b3d-6453da2fafa2 IPsec Policy Id: 8ba867b2-67eb-4835-bb61-c226804a1584 Peer Address: 172.24.4.226 Peer Id: 172.24.4.226 Peer CIDRS: [10.1.0.0/24] Auth Mode: PSK PSK: ****** Initiator: bi-directional Admin State Up: true MTU: 1500 DPD: Action: clear Interval: 30 Timeout: 120 Route Mode: static |
|
日志说明 |
用户进行了创建IPsec站点连接的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · The operation requires the administrator privilege：您需要管理员权限才能执行此操作 · The tenant doesn’t exist：IPsec站点连接的租户不存在 · The IPsec site connection and the specified VPN service belong to different tenants：该IPsec站点连接与指定的VPN服务属于不同的租户 · The IPsec site connection and the specified IKE policy belong to different tenants：该IPsec站点连接与指定的IKE策略属于不同的租户 · The IPsec site connection and the specified IPsec policy belong to different tenants：该IPsec站点连接与指定的IPsec策略属于不同的租户 · The VPN service doesn't exist：指定的VPN服务不存在 · The IKE policy doesn't exist：指定的IKE策略不存在 · The IPsec policy doesn't exist：指定的IPsec策略不存在 · Configuration recovery is in progress：配置正在恢复过程中 · The number of IPsec site connections has reached the maximum：IPsec站点连接数量已达最大值 · The PSK parameter cannot be null if the authentication mode is PSK：当认证模式为“预共享密钥”时，预共享密钥参数不能为空 · The VPN service referenced by the IPsec site connection is not bound to a vSubnet：该IPsec站点连接引用的VPN服务未绑定虚拟子网 · The local subnet and peer subnet must use the same IP version：本端子网和对端子网的IP版本必须一致 · The peer address and peer subnet must use the same IP version：对端地址与对端子网的IP版本必须一致 · The local subnet, peer subnet, peer address, and peer ID (in IP address format) must use the same IP version：本端子网、对端子网、以及IP地址格式的对端地址、对端身份，必须使用相同IP版本 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_IPSEC_SITE_CONN_OP |
|
日志内容 |
Delete IPsec Site Connection $1 |
|
参数解释 |
$1：IPsec站点连接的UUID |
|
举例 |
Delete IPsec Site Connection UUID: cbc152a0-7e93-4f98-9f04-b085a4bf2511 |
|
日志说明 |
用户进行了删除IPsec站点连接的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · The operation requires the administrator privilege：您需要管理员权限才能执行此操作 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_IPSEC_SITE_CONNS_OP |
|
日志内容 |
Update IPsec Site Connections $1. |
|
参数解释 |
$1：IPsec站点连接信息 |
|
举例 |
Update IPsec Site Connections Name: vpnconnection1 UUID: cbc152a0-7e93-4f98-9f04-b085a4bf2511 Description: connections 2 Peer Address: 172.24.4.226 Peer Id: 172.24.4.226 Peer CIDRS: [10.1.0.0/24] PSK: ****** Initiator: bi-directional Admin State Up: true MTU: 1500 DPD: Action: clear Interval: 30 Timeout: 120 Route Mode: static |
|
日志说明 |
用户进行了修改IPsec站点连接的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · The operation requires the administrator privilege：您需要管理员权限才能执行此操作 · The IPsec site connection and the specified VPN service belong to different tenants：该IPsec站点连接与指定的VPN服务属于不同的租户 · The IPsec site connection and the specified IKE policy belong to different tenants：该IPsec站点连接与指定的IKE策略属于不同的租户 · The IPsec site connection and the specified IPsec policy belong to different tenants：该IPsec站点连接与指定的IPsec策略属于不同的租户 · The VPN service doesn't exist：指定的VPN服务不存在 · The IKE policy doesn't exist：指定的IKE策略不存在 · The IPsec policy doesn't exist：指定的IPsec策略不存在 · Configuration recovery is in progress：配置正在恢复过程中 · The VPN service referenced by the IPsec site connection is not bound to a vSubnet：该IPsec站点连接引用的VPN服务未绑定虚拟子网 · The local subnet and peer subnet must use the same IP version：本端子网和对端子网的IP版本必须一致 · The peer address and peer subnet must use the same IP version：对端地址与对端子网的IP版本必须一致 · The local subnet, peer subnet, peer address, and peer ID (in IP address format) must use the same IP version：本端子网、对端子网、以及IP地址格式的对端地址、对端身份，必须使用相同IP版本 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_IPSEC_SITE_CONNS_PEER_CIDR_OP |
|
日志内容 |
Create IPsec site connection peer CIDR $1. |
|
参数解释 |
$1：IPsec站点连接的对端子网信息 |
|
举例 |
Create IPsec site connection peer CIDR IPsec site connection UUID: cbc152a0-7e93-4f98-9f04-b085a4bf2511 Peer CIDR: 12.2.2.2/12. |
|
日志说明 |
用户进行了创建IPsec站点连接的对端子网的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The IPsec site connection doesn't exist：指定的IPsec站点连接不存在 · The IPsec site peer CIDR already exists：该对端子网已存在 · The number of IPsec site connections has reached the maximum：IPsec站点连接数量已达最大值 · The VPN service referenced by the IPsec site connection is not bound to a vSubnet：该IPsec站点连接引用的VPN服务未绑定虚拟子网 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_IPSEC_SITE_CONNS_PEER_CIDR_OP |
|
日志内容 |
Delete IPsec site connection peer CIDR $1. |
|
参数解释 |
$1：IPsec站点连接的对端子网信息 |
|
举例 |
Delete IPsec site connection peer CIDR IPsec site connection UUID: cbc152a0-7e93-4f98-9f04-b085a4bf2511 Peer CIDR: 12.2.2.2/12. |
|
日志说明 |
用户进行了删除IPsec站点连接的对端子网的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The IPsec site connection doesn't exist：指定的IPsec站点连接不存在 · The IPsec site peer CIDR doesn't exist：该对端子网不存在 · The VPN service referenced by the IPsec site connection is not bound to a vSubnet：该IPsec站点连接引用的VPN服务未绑定虚拟子网 · You have no privilege to perform this operation：用户无权限执行此操作 |
本节介绍虚拟网络模块输出的操作日志。
|
关键字 |
CREATE_VDS_OP |
|
日志内容 |
Created VDS “$1”. |
|
参数解释 |
$1：VDS的名称 |
|
举例 |
Created VDS “vds2”. |
|
日志说明 |
用户进行了创建VDS的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · A VDS already exists with the specified name：虚拟分布式交换机名称已存在 · VDSs created in bulk cannot use the same ID：批量创建的分布式虚拟交换机的ID存在重复 · The bridge name cannot exceed 255 characters：Bridge名称最长255个字符 · The VXLAN tunnel name cannot exceed 255 characters：VXLAN隧道口名称最长255个字符 · The length of the automatically generated VXLAN tunnel name exceeded the limit：自动生成的VXLAN隧道口名称超出长度范围限制 · A bridge already exists with the specified name：Bridge名称已存在 · A VXLAN tunnel already exists with the specified name：VXLAN隧道口名称已存在 · The OpenFlow hard aging time exceeded the limit：OpenFlow流表老化时间超出范围 · Invalid VXLAN range：VXLAN范围无效 · Invalid global virtual MAC address：全局虚拟MAC地址无效 · Invalid VTEP IP for the network node：无效的Metadata Agent节点的VTEP IP · Invalid VTEP MAC for the network node：无效的Metadata Agent节点的VTEP MAC · Invalid forwarding mode：无效的转发模式 · The VDS name and the bridge name cannot both be null：虚拟分布式交换机名称和桥名称不能同时为空 · The VDS already exists：VDS已经存在 · Please specify the VXLAN ID range：未配置VXLAN ID范围 · The number of VXLAN ID digits in the VSI interface name is invalid：无效的VXLAN ID填充网关接口名称位数 · The VDS name cannot exceed 62 characters：VDS名称最长62个字符 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 · The RT generated based on the AS number of the fabric conflicts with the import RT of a Layer 2 DC interconnect：Fabric的AS号生成的RT与数据中心二层互联的引入RT冲突 · The RT generated based on the AS number of the fabric conflicts with the export RT of a Layer 2 DC interconnect：Fabric的AS号生成的RT与数据中心二层互联的引出RT冲突 · The RT generated based on the AS number of the fabric conflicts with the import RT of a Layer 3 DC interconnect：Fabric的AS号生成的RT与数据中心三层互联的引入RT冲突 · The RT generated based on the AS number of the fabric conflicts with the export RT of a Layer 3 DC interconnect：Fabric的AS号生成的RT与数据中心三层互联的引出RT冲突 · The RT reserved for the fabric connection conflicts with the import RT of a Layer 2 DC interconnect：系统预留的Fabric互联的RT与数据中心二层互联的引入RT冲突 · The RT reserved for the fabric connection conflicts with the export RT of a Layer 2 DC interconnect：系统预留的Fabric互联的RT与数据中心二层互联的引出RT冲突 · The RT reserved for the fabric connection conflicts with the import RT of a Layer 3 DC interconnect：系统预留的Fabric互联的RT与数据中心三层互联的引入RT冲突 · The RT reserved for the fabric connection conflicts with the export RT of a Layer 3 DC interconnect：系统预留的Fabric互联的RT与数据中心三层互联的引出RT冲突 · You cannot enable automatic vPort creation for the VDS, because LLDP-based vPort onboarding has been enabled globally：控制组件已开启LLDP上线虚拟端口开关，虚拟分布式交换机不允许开启自动创建虚拟端口开关 · Fabrics that have been bound to another VDS exist：Fabric列表中部分Fabric已被其他VDS关联 · The fabric does not exist：指定的Fabric不存在 · The forwarding mode of the VDS does not match the EVPN state of the fabric：VDS的转发模式和Fabric中的EVPN开关不一致 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · The RT generated based on the AS number of the fabric conflicts with the import RT of a vRouter：Fabric的AS号生成的RT与虚拟路由器的引入RT冲突 · The RT generated based on the AS number of the fabric conflicts with the export RT of a vRouter：Fabric的AS号生成的RT与虚拟路由器的引出RT冲突 · The RT reserved for the fabric connection conflicts with the import RT of a vRouter：系统预留的Fabric互联的RT与虚拟路由器的引入RT冲突 · The RT reserved for the fabric connection conflicts with the export RT of a vRouter：系统预留的Fabric互联的RT与虚拟路由器的引出RT冲突 |
|
关键字 |
UPDATE_VDS_OP |
|
日志内容 |
Updated VDS “$1”. |
|
参数解释 |
$1：VDS的名称 |
|
举例 |
Updated VDS “vds2”. |
|
日志说明 |
用户进行了修改VDS的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · Cannot modify the bridge name because the VDS has been bound to a domain：VDS已绑定计算域，不允许修改Bridge名称 · Operation failed. The new VXLAN range does not contain existing VXLAN IDs：修改后的VXLAN范围未包含已使用的VXLAN ID · You cannot change the VXLAN tunnel interface name, because the VDS has hosts：VDS已绑定计算域，不允许修改VXLAN隧道口名称 · Cannot modify the global virtual MAC address because the VDS has virtual link layer networks：VDS下存在虚拟链路层网络，不允许修改全局虚拟MAC地址 · The value of the vswitch_flood_and_learn field is invalid：无效的vswitch_flood_and_learn · Please specify the VDS ID：未指定虚拟分布式交换机ID · A VDS already exists with the specified name：虚拟分布式交换机名称已存在 · A bridge already exists with the specified name：Bridge名称已存在 · A VXLAN tunnel already exists with the specified name：VXLAN隧道口名称已存在 · The bridge name cannot exceed 255 characters：Bridge名称最长255个字符 · The VXLAN tunnel name cannot exceed 255 characters：VXLAN隧道口名称最长255个字符 · The OpenFlow hard aging time exceeded the limit：OpenFlow流表老化时间超出范围 · Invalid VXLAN range：VXLAN范围无效 · Invalid global virtual MAC address：全局虚拟MAC地址无效 · Invalid VTEP IP for the network node：无效的Metadata Agent节点的VTEP IP · Invalid VTEP MAC for the network node：无效的Metadata Agent节点的VTEP MAC · Invalid forwarding mode：无效的转发模式 · The specified resource doesn't exist：指定的资源不存在 · You cannot change the default VDS name：不允许修改缺省VDS名称 · You cannot edit the number of VXLAN ID digits in a VSI interface name：VXLAN ID填充网关接口名称位数不允许修改 · The bridge name is required：未指定虚拟分布式Bridge名称 · Please specify the VXLAN tunnel name：未指定虚拟分布式VXLAN隧道口名称 · The parameter (parameters) can't be modified：(parameters)参数不允许被修改 · The VDS name cannot exceed 62 characters：VDS名称最长62个字符 · Please specify the backup_link_enable parameter：主备网卡联动不能为空 · Please specify the lldp_to_controller parameter：LLDP上送控制组件不能为空 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 · The RT generated based on the AS number of the fabric conflicts with the import RT of a Layer 2 DC interconnect：Fabric的AS号生成的RT与数据中心二层互联的引入RT冲突 · The RT generated based on the AS number of the fabric conflicts with the export RT of a Layer 2 DC interconnect：Fabric的AS号生成的RT与数据中心二层互联的引出RT冲突 · The RT generated based on the AS number of the fabric conflicts with the import RT of a Layer 3 DC interconnect：Fabric的AS号生成的RT与数据中心三层互联的引入RT冲突 · The RT generated based on the AS number of the fabric conflicts with the export RT of a Layer 3 DC interconnect：Fabric的AS号生成的RT与数据中心三层互联的引出RT冲突 · The RT reserved for the fabric connection conflicts with the import RT of a Layer 2 DC interconnect：系统预留的Fabric互联的RT与数据中心二层互联的引入RT冲突 · The RT reserved for the fabric connection conflicts with the export RT of a Layer 2 DC interconnect：系统预留的Fabric互联的RT与数据中心二层互联的引出RT冲突 · The RT reserved for the fabric connection conflicts with the import RT of a Layer 3 DC interconnect：系统预留的Fabric互联的RT与数据中心三层互联的引入RT冲突 · The RT reserved for the fabric connection conflicts with the export RT of a Layer 3 DC interconnect：系统预留的Fabric互联的RT与数据中心三层互联的引出RT冲突 · You cannot enable automatic vPort creation for the VDS, because LLDP-based vPort onboarding has been enabled for some vNetworks of the VDS：VDS内的虚拟链路层网络已开启LLDP上线虚拟端口开关，不允许开启自动创建虚拟端口开关 · You cannot enable automatic vPort creation for the VDS, because LLDP-based vPort onboarding has been enabled globally：控制组件已开启LLDP上线虚拟端口开关，虚拟分布式交换机不允许开启自动创建虚拟端口开关 · The fabric has host：Fabric中存在主机 · Fabrics that have been bound to another VDS exist：Fabric列表中部分Fabric已被其他VDS关联 · The fabric does not exist：指定的Fabric不存在 · The forwarding mode of the VDS does not match the EVPN state of the fabric：VDS的转发模式和Fabric中的EVPN开关不一致 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · You cannot delete the fabric, because it is automatically generated by the system：系统自动生成的Fabric不支持解绑 · The RT generated based on the AS number of the fabric conflicts with the import RT of a vRouter：Fabric的AS号生成的RT与虚拟路由器的引入RT冲突 · The RT generated based on the AS number of the fabric conflicts with the export RT of a vRouter：Fabric的AS号生成的RT与虚拟路由器的引出RT冲突 · The RT reserved for the fabric connection conflicts with the import RT of a vRouter：系统预留的Fabric互联的RT与虚拟路由器的引入RT冲突 · The RT reserved for the fabric connection conflicts with the export RT of a vRouter：系统预留的Fabric互联的RT与虚拟路由器的引出RT冲突 |
|
关键字 |
DELETE_VDS_OP |
|
日志内容 |
Deleted VDS “$1”. |
|
参数解释 |
$1：VDS的名称 |
|
举例 |
Deleted VDS “vds2”. |
|
日志说明 |
用户进行了删除VDS的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The specified resource doesn't exist：指定的资源不存在 · You cannot delete the VDS, because it is in use：VDS正在使用中，不允许删除 · You cannot delete the default VDS：不允许删除默认VDS · You cannot delete the VDS, because it has fabrics：VDS已绑定Fabric，不允许删除 · You cannot delete the specified VDS, because it has been bound to a tenant：指定的VDS已绑定到租户，不允许删除 · You cannot delete the specified VDS, because it has fabric connections：指定的VDS已创建Fabric连接，不允许删除 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
ADD_HOST_OP |
|
日志内容 |
Added host “$1”. |
|
参数解释 |
$1：主机的IP地址 |
|
举例 |
Added host “1.1.1.1” |
|
日志说明 |
用户进行了增加主机的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · Invalid IP address：无效的IP地址 · Cannot add the host because no available regions exist：没有可用的Region，不允许添加主机 · The UUID already exists：主机UUID已存在 · Failed to add the host because the domain type is vCenter：vCenter类型的计算域不能添加主机 · The bridge of the host does not match any bridges of VDSs bound to the domain to which the host belongs：主机的Bridge与其所属计算域关联的VDS的Bridge不匹配 · Unknown error：未知错误 · Number of CPUs that can be managed is insufficient. Please purchase a new license or expand the old one：可管理的CPU不足，请购买或扩容vSwitch License · The domain doesn't exist：计算域不存在 · The request is invalid：传入的JSON串错误 · No available IP addresses in the VTEP IP address pool：VTEP IP池没有可分配的IP地址 · Host host, parameter is required：主机host，parameter不能为空 · The host type and the domain type do not match：主机类型与计算域类型不匹配 · The host name cannot exceed 255 characters：主机名称最长255个字符 · The IP address is already used：主机IP地址已经被使用 · No VDS exists in the domain：指定的计算域没有关联VDS · The bridge configuration is invalid. Please verify correctness of the host bridge configuration and reachability of the host IP address：无效的主机桥配置，请检查主机桥配置以及主机IP是否可达 · Bridges on the same host cannot use the same name：同一个主机上的Bridge名称不能相同 · You can select a fabric for a host only from fabrics of VDSs in the domain to which the host belongs：该主机指定的Fabric不在所属计算域中的VDS指定的Fabric列表中 · Insufficient third-party vSwitch licenses：第三方vSwitch不足 · Failed to get the vSwitch version. Please verify the correctness of the OVS version and reachability of the host IP address：获取vSwitch版本失败，请检查OVS版本是否正确以及主机IP是否可达 · You have no privilege to perform this operation：用户无权限执行此操作 · The VXLAN tunnel name of the VDS cannot exceed 15 characters：VDS的VXLAN隧道口名称不能超过15个字符 · The bridge name of the VDS cannot exceed 15 characters：VDS的Bridge名称不能超过15个字符 · Invalid role：无效的角色 · The nodes added to a DHCP host group can only be network nodes：DHCP主机组不允许增加非网络节点主机 · The DHCP host group does not exist：指定的DHCP主机组不存在 · A DHCP host group can contain a maximum of two network nodes：DHCP主机组最多增加两台主机 · The network node and the DHCP host group are in different fabrics：DHCP主机组与主机不属于同一Fabric · The uplink interface name is a case-senstive string of up to 255 characters. Valid characters are letters, digits, underscores (_), hyphens (-) and dots(.)：上行口名称最长255个字符，区分大小写，仅支持字母、数字、下划线、连字符和点 · The datapath ID has been specified for another device：该主机与其他设备的Datapath ID冲突 |
|
关键字 |
UPDATE_HOST_OP |
|
日志内容 |
Updated host “$1”. |
|
参数解释 |
$1：主机的IP地址 |
|
举例 |
Updated host “1.1.1.1”. |
|
日志说明 |
用户进行了修改主机的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · Failed to add the host because the domain type is vCenter：vCenter类型的计算域不能添加主机 · The bridge of the host does not match any bridges of VDSs bound to the domain to which the host belongs：主机的Bridge与其所属计算域关联的VDS的Bridge不匹配 · Invalid IP address：无效的IP地址 · The domain doesn't exist：计算域不存在 · The request is invalid：传入的JSON串错误 · Unknown error：未知错误 · No available IP addresses in the VTEP IP address pool：VTEP IP池没有可分配的IP地址 · Host host, parameter is required：主机host，parameter不能为空 · The max packet-in packet rate is invalid：无效的Packet-in报文最大速率 · Cannot configure the max packet-in packet rate：不支持配置Packet-in报文最大速率 · The flow entry aging acceleration threshold is invalid：无效的流表加速老化阈值 · Cannot configure the flow entry aging acceleration threshold：不支持配置流表加速老化阈值 · No VDS exists in the domain：指定的计算域没有关联VDS · The bridge configuration is invalid. Please verify correctness of the host bridge configuration and reachability of the host IP address：无效的主机桥配置，请检查主机桥配置以及主机IP是否可达 · The IP address and UUID cannot both be null：主机IP地址和UUID不能同时为空 · The IP address and UUID do not match：主机IP地址与UUID不匹配 · Bridges on the same host cannot use the same name：同一个主机上的Bridge名称不能相同 · You can select a fabric for a host only from fabrics of VDSs in the domain to which the host belongs：该主机指定的Fabric不在所属计算域中的VDS指定的Fabric列表中 · You have no privilege to perform this operation：用户无权限执行此操作 · The uplink interface name is a case-senstive string of up to 255 characters. Valid characters are letters, digits, underscores (_), hyphens (-) and dots(.)：上行口名称最长255个字符，区分大小写，仅支持字母、数字、下划线、连字符和点 · The host name cannot exceed 255 characters：主机名称最长255个字符 · You cannot edit or delete the cloud region name：云区域名称不允许修改或删除 · The datapath ID has been specified for another device：该主机与其他设备的Datapath ID冲突 |
|
关键字 |
DELETE_HOST_OP |
|
日志内容 |
Deleted host “$1”. |
|
参数解释 |
$1：主机的IP地址 |
|
举例 |
Deleted host “1.1.1.1” |
|
日志说明 |
用户进行了删除主机的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The specified resource doesn't exist：指定的资源不存在 · Cannot delete the host because it is a network element：该主机为网元设备，不允许删除 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 · The address pool for the vRouter interconnection network does not exist or no IP addresses are available in the address pool：虚拟路由器互通网络类型的地址池不存在或地址池中无可用的IP地址 · The VLAN pool for the vRouter interconnection network does not exist：虚拟路由器互联网络类型的VLAN池不存在 |
|
关键字 |
CREATE_ROUTE_OP |
|
日志内容 |
Created vRouter “$1”. |
|
参数解释 |
$1：虚拟路由器的名称 |
|
举例 |
Created vRouter “router01” |
|
日志说明 |
用户进行了创建路由器的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · Invalid tenant ID：无效的租户ID · The router ID is already used：路由器ID已经存在 · vRouters created in bulk cannot use the same ID：批量创建的虚拟路由器的ID存在重复 · The router is required：未指定虚拟路由器 · The is_bind_gw field is a read-only field：is_bind_gw为只读字段 · The segment ID number is already used：Segment ID number已经被使用 · The segment ID is out of range：Segment ID超出范围 · Invalid routing table：无效的路由表 · The VDS doesn't exist：VDS不存在 · The VPN instance name is already used：VPN实例名称已经被使用 · The AS number is required：未指定AS号 · The value for the maximum number of ECMP routes is invalid：最大等价路由条目不可用 · Invalid summary route network：聚合路由网段不可用 · The IPv4 address of the peer is required：未指定对等体的IPv4地址 · Invalid CIDR：无效的CIDR · The CIDR overlaps with another CIDR：CIDR配置中有重叠项 · The AS number of the peer is invalid：无效的对等体AS号 · The vRouter cannot be configured with the same summary route network：不允许配置重复的聚合路由网段 · The vRouters using the public VRF cannot be bound to the same service device group：使用公网VRF的虚拟路由器不能绑定同一个服务设备组 · The specified device doesn't exist：指定的设备不存在 · The device ID and the device name do not match：设备的ID和名称不匹配 · The BGP peer already exists：存在冲突的BGP对等体 · The vRouter name cannot exceed 255 characters：虚拟路由器名称最长255个字符 · The VPN name cannot exceed 31 bytes：VPN名称最长31个字节 · The specified tenant doesn't exist：指定的租户不存在 · Failed to add the vRouter because the number of vRouters has reached the limit：虚拟路由器的数量已达上限 · The specified tenant doesn't bind VDS：指定的租户没有绑定VDS · The VDS of the vRouter is different than the tenant：虚拟路由器与租户的VDS不一致 · The external network bound to the vRouter does not have segments. The vRouter can be bound only to one IPv4 subnet：指定的外部网络未配置Segment，只能绑定一个IPv4子网 · The border gateways to the IPv4 and IPv6 external subnets are located on the same interface. You must configure them with the same segment ID：IPv4外网子网和IPv6外网子网的出口网关相同时，Segment ID必须相同 · The external network egress IP has been bound to another vRouter. To bind the current vRouter to the external network egress IP, you must make sure the current vRouter has exactly the same external subnet bindings as that vRouter：虚拟路由器绑定多个外网子网，且多个虚拟路由器共享外网IP时，必须同时共享所有外网IP · Unknown error：未知错误 · The address pool does not exist or no IP addresses are available in the address pool：绑定服务资源失败，指定的地址池不存在，或该地址池内没有足够的IP地址 · The segment or border gateway already has a priority：不允许重复配置网络分段或者出口网关的优先级 · If a vRouter is bound to both a gateway resource and a network segment, you can configure a priority for either the gateway resource or the network segment, but not both：不能同时配置网关资源和网络分段的优先级 · If service resources have been bound to a virtual router, the border gateways bound to the virtual router must have different priorities：虚拟路由器已绑定服务资源时，两个出口网关的优先级不允许相同 · Invalid tags：无效的tags · The priority is out of range：tags优先级超出范围 · The specified segment doesn't exist：指定的网络分段不存在 · The specified gateway doesn't exist：指定的网关资源不存在 · Cannot configure a priority for the gateway resource. For more information, see the online help：该网关资源不支持配置优先级，具体情况请查看联机帮助 · Failed to bind the vRouter to an external network because the specified network is not an indirectly connected external network：虚拟路由器无法与该外网绑定，因为选定的网络不是共享型外网 · Cannot disable east-west traffic offload in network cloud scenarios：网络云场景下不允许关闭东西向流量卸载开关 · The public network VPN cannot be configured in the weak control scenario：弱控场景下不支持配置公网VPN · You have no privilege to perform this operation：用户无权限执行此操作 · A vRouter cannot be bound to internal network vPorts：虚拟路由器仅支持绑定外网虚拟端口 · Cannot bind the external network vPort to the vRouter, because the vRouter has been bound to the external network to which the vPort belongs：虚拟路由器已绑定外部网络，不允许绑定该外网虚拟端口 · A vRouter cannot be bound to multiple IPv6 external network vPorts in the same network：虚拟路由器绑定多个IPv6外网虚拟端口时，这些端口所属的外部网络不能相同 · Cannot bind the external network to the vRouter, because the vRouter has been bound to a vPort in the external network：虚拟路由器已绑定外网虚拟端口，不允许再绑定该端口所属的外部网络 · A VPN instance name cannot start with 'external_vpn' or 'management_vpn'：VPN实例名称不能以“external_vpn”或者"management_vpn"为前缀 · The RT generated based on the segment ID of the vRouter conflicts with the import RT of a Layer 2 DC interconnect：虚拟路由器Segment ID生成的RT与数据中心二层互联的引入RT冲突 · The RT generated based on the segment ID of the vRouter conflicts with the export RT of a Layer 2 DC interconnect：虚拟路由器Segment ID生成的RT与数据中心二层互联的引出RT冲突 · The RT reserved for the vRouter link conflicts with the import RT of a Layer 2 DC interconnect：系统预留的虚拟路由器连接的RT与数据中心二层互联的引入RT冲突 · The RT reserved for the vRouter link conflicts with the export RT of a Layer 2 DC interconnect associated with the local or remote vRouter：系统预留的虚拟路由器连接的RT与数据中心二层互联的引出RT冲突 · The RT generated based on the segment ID of the vRouter conflicts with the import RT of a Layer 3 DC interconnect：虚拟路由器Segment ID生成的RT与数据中心三层互联的引入RT冲突 · The RT generated based on the segment ID of the vRouter conflicts with the export RT of a Layer 3 DC interconnect：虚拟路由器Segment ID生成的RT与数据中心三层互联的引出RT冲突 · The RT reserved for the vRouter link conflicts with the import RT of a Layer 3 DC interconnect：系统预留的虚拟路由器连接的RT与数据中心三层互联的引入RT冲突 · The RT reserved for the vRouter link conflicts with the export RT of a Layer 3 DC interconnect：系统预留的虚拟路由器连接的RT与数据中心三层互联的引出RT冲突 · Check the directly connected external networks and the border interfaces in the device group bound to this vRouter with the same segment ID. Make sure only one primary IPv4 address exists for each border interface：虚拟路由器下的独享型外网子网和该虚拟路由器绑定的设备组中的外网出口使用相同Segment ID时，最多只允许有一个主IP · vRouters do not support vPorts in flat external networks：虚拟路由器不支持绑定FLAT类型的外部网络中的虚拟端口 · The vRouter context or external network vPort context has been used in a service chain：指定的虚拟路由器或外部网络虚拟端口类型的流量特征组已被服务链使用 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · The segment ID cannot be identical to a VXLAN ID in a VXLAN pool or the VXLAN ID reserved for the automation template and the M-LAG system：Segment ID不能在VXLAN池范围内且不能和自动化模版、M-LAG系统的保留VXLAN ID重叠 · Please specify a peer IP address or network address：对等体IP地址/网段不能为空 · Invalid peer IP address or network address：对等体IP地址/网段无效 · Invalid source IP address：源IP地址无效 · Invalid IP version：IP版本无效 · Neighbor IP/network address must be of the same IP version as the source IP address：对等体IP地址/网段与源IP地址必须为相同IP版本 · Neighbor IP/network address and IP version are inconsistent：对等体IP地址/网段和IP版本不一致 · The peer IP address cannot be the same as the source IP address：对等体地址和源IP地址不能相同 · Please specify the device ID, device name, or both：设备ID和设备名称不能为空 · The network addresses of some neighbors overlap：BGP对等体中存在网段重叠 · The value for the create_loopback parameter cannot be true when no source IP address is specified：源IP地址为空时，不允许开启创建LoopBack口开关 · BGP neighbors with the same source IP address must be consistent in the value for the create_loopback parameter：相同源IP地址的BGP对等体的创建LoopBack口开关必须一致 · A transit vRouter cannot be bound to an internal subnet：虚拟路由器是TRANSIT类型时，不支持绑定内网子网 · A transit vRouter does not support aggregate CIDRs：虚拟路由器是TRANSIT类型时，不支持Aggregate CIDRs · A transit vRouter does not support CIDRs：虚拟路由器是TRANSIT类型时，不支持CIDRs · A normal vRouter does not support export RTs：虚拟路由器是NORMAL类型时，不支持引出RT · A normal vRouter does not support import RTs：虚拟路由器是NORMAL类型时，不支持引入RT · Invalid export target：无效的引出RT · Invalid import target：无效的引入RT · The vRouter type is invalid：无效的虚拟路由器类型 · The import RT %s of the vRouter conflicts with the RT of a Layer 2 DC interconnect：虚拟路由器配置的引入RT与数据中心二层互联的RT冲突 · The export RT %s of the vRouter conflicts with the RT of a Layer 2 DC interconnect：虚拟路由器配置的引出RT与数据中心二层互联的RT冲突 · The import RT %s of the vRouter conflicts with the RT of a Layer 3 DC interconnect：虚拟路由器配置的引入RT与数据中心三层互联的RT冲突 · The export RT %s of the vRouter conflicts with the RT of a Layer 3 DC interconnect：虚拟路由器配置的引出RT与数据中心三层互联的RT冲突 · The export RT on the vRouter conflicts with the RT on a vNetwork：虚拟路由器配置的引出RT与虚拟链路层网络的RT冲突 · The export RT of the vRouter conflicts with an RT reserved for fabric interconnects：虚拟路由器配置的引出RT与系统预留的Fabric互联RT冲突 · The export RT of the vRouter conflicts with an RT reserved for vRouter links：虚拟路由器配置的引出RT与系统预留的虚拟路由器连接的RT冲突 · The export RT of the vRouter conflicts with the RT of another vRouter：虚拟路由器配置的引出RT与其他虚拟路由器的RT冲突 · The import RT of the vRouter conflicts with an RT reserved for vRouter links：虚拟路由器配置的引入RT与系统预留的虚拟路由器连接的RT冲突 · The import RT of the vRouter conflicts with the RT of another vRouter：虚拟路由器配置的引入RT与其他虚拟路由器的RT冲突 · The import RT of the vRouter conflicts with the RT of a vNetwork：虚拟路由器配置的引入RT与虚拟链路层网络的RT冲突 · The import RT of the vRouter conflicts with an RT reserved for fabric interconnects：虚拟路由器配置的引入RT与系统预留的Fabric互联RT冲突 · When host route recursion is enabled, the next hop IP address cannot reside on an external network：当迭代主机路由开关开启时，下一跳IP地址不能属于外网网段 · You cannot enable ND direct route redistribution for a vRouter in the network cloud scenario：网络云场景下，不允许开启引入ND直连路由开关 · A vRouter and its attached external network must be bound to the same gateway：虚拟路由器的出口网关和外部网络的出口网关必须一致 · You cannot bind the external network to the vRouter, because the external network has been bound to a border gateway and the border gateway is not bound to the vRouter：不允许绑定配置了出口网关的外部网络，因为虚拟路由器未绑定出口网关 · The security external network feature is disabled. You cannot bind the vRouter to an external subnet with a VLAN-type segment, because the vRouter has been bound to a firewall configured with a security external network address pool：禁用安全外网时，该虚拟路由器已绑定的防火墙使用了安全外网，不能同时绑定Segment为VLAN类型的外网子网 · The security external network feature is disabled. You cannot bind the vRouter to an external network of the VLAN type, because the vRouter has been bound to a firewall configured with a security external network address pool：禁用安全外网时，该虚拟路由器已绑定的防火墙使用了安全外网，不能同时绑定VLAN类型的外部网络 · The internal or external subnets of the same vRouter cannot overlap：同一虚拟路由器内网或外网子网网段不能重叠 · You cannot enable the multicast network feature for any external transit vRouter：EXTERNALTRANSIT类型虚拟路由器不允许开启组播网络 · You cannot enable the multicast network feature for any external transit vRouter：EXTERNALTRANSIT类型虚拟路由器不允许开启组播网络 · You cannot bind the external transit vRouter to an external network that has no vPort-vRouter bindings：EXTERNALTRANSIT类型虚拟路由器不支持绑定未被虚拟路由器外网虚拟端口绑定的外部网络 · The external subnets cannot overlap：多数据中心外网网段信息中存在子网网段重叠 · You cannot bind the external transit vRouter to any external network referenced by OSPF：EXTERNALTRANSIT类型虚拟路由器不支持绑定被OSPF引用的外网 · You cannot bind the transit vRouter to any external network：TRANSIT类型虚拟路由器不支持绑定外网 · You cannot bind the external transit vRouter to any internal subnets：EXTERNALTRANSIT类型虚拟路由器不支持绑定内网子网 · The internal subnets cannot overlap：多数据中心内网网段信息中存在子网网段重叠 · Invalid multi-DC internal subnet information：无效的多数据中心内网网段信息 · You cannot bind an external transit vRouter to any external network enabled with the network segmentation feature：开启了网络分段的外网不允许绑定External Transit 类型VRouter · The vRouters bound to an external network must be of the same type：外网不允许被不同类型虚拟路由器绑定 · Invalid multi-DC external subnet information：无效的多数据中心外网网段信 · You cannot bind a vPort that meets the following requirements to the external transit vRouter:• The firewall status of the vPort is default.• The vPort's edge device to external network is border device：EXTERNALTRANSIT类型虚拟路由器不允许绑定防火墙开关为默认且虚拟路由器外网出口设备为边界设备的外网虚拟端口 · Internal subnets cannot overlap with any external subnet：多数据中心内网网段信息和多数据中心外网网段信息中存在子网网段重叠 · External transit vrouter cannot be bound to an external network has bound to another type vrouter：已绑定其他类型VRouter的外网不允许绑定External Transit 类型VRouter · You cannot bind any vPorts to an external transit vRouter if the vRouter is already in a centralized vRouter link and the peer vRouter is not enabled with firewall：EXTERNALTRANSIT类型虚拟路由器已绑定到集中式虚拟路由器连接，且对端防火墙关闭时，不允许绑定外部网络中的虚拟端口 · Overlapping items are not allowed in the information configuration of the external network segment of the multi data center of different transitvrouter corresponding to the same tenant virtual router in the VPC：同一个虚拟路由器与不同的EXTERNALTRANSIT类型虚拟路由器建立集中式虚拟路由器连接，EXTERNALTRANSIT类型虚拟路由器间的多数据中心外网网段信息存在子网网段重叠 · You cannot bind any vPorts to the external transit vRouter if the vRouter is already in a centralized vRouter link and the peer vRouter is not enabled with firewall：EXTERNALTRANSIT类型虚拟路由器，外网出口设备为边界设备时，不允许绑定外部网络中的虚拟端口 · You must specify a segment ID for the external transit vRouter：EXTERNALTRANSIT类型虚拟路由器的Segment ID不能为空 · You cannot disable firewall for the peer vRouter in the vRouter link if the external transit vRouter already has vPort bindings：EXTERNALTRANSIT类型虚拟路由器已绑定外部网络中的虚拟端口，对端防火墙不允许关闭 · The VPN instance name is invalid：无效的VPN实例名称 · Invalid inbound routing policy name：无效的入方向路由策略名称 · The external network has been bound to a vRouter that uses a different edge device placement mode than this vRouter. To bind to that network, first set the third-party firewall deployment mode to Off：边界设备对接第三方防火墙为开启状态（旁挂和直连）时，外部网络不能同时绑定外网出口设备为边界设备的虚拟路由器和外网出口设备为防火墙的虚拟路由器 · Invalid outbound routing policy name：无效的出方向路由策略名称 · You cannot bind the external network to the vRouter, because the external network is enabled with route reduction and bound to another vRouter configured with the same internal subnet as this vRouter：外部网络已开启路由精简且绑定的虚拟路由器存在相同网段的内网子网时，虚拟路由器不允许绑定该外部网络 · You cannot bind the external network vPort to the vRouter, because the external network is enabled with route reduction and bound to another vRouter configured with the same internal subnet as this vRouter：外部网络已开启路由精简且绑定的虚拟路由器存在相同网段的内网子网时，虚拟路由器不允许绑定该外网虚拟端口 · You cannot bind the internal subnet to the vRouter, because the vRouter-associated external network is enabled with route reduction, and the internal subnet has been specified for another vRouter bound to this external network：虚拟路由器已绑定开启路由精简的外部网络时，虚拟路由器不允许绑定与该外部网络所属的其他虚拟路由器网段相同的内网子网 · When you add a vRouter that has the same vSubnet bindings and external network binding as an existing vRouter, you can disable SNAT for the bound external network on either vRouter, but not both of them：绑定了相同子网网段、相同外部网络的虚拟路由器，不允许均关闭外网SNAT开关 · An MDC north-south vRouter link (with islocalAll set to false and isPeerAll set to true) and an MDC east-west vRouter link (with both islocalAll and isPeerAll set to false) are created on the tenant. Make sure the routes to an external subnet of the south-north vRouter link and a remote CIDR of the east-west vRouter link do not overlap：当相同租户同时创建MDC南北向业务（指定源）和东西向业务（指定源和目的）时，南北向的多数据中心外网网段与东西向的对端网段明细路由不能相同 · If the firewall service type specified for a vRouter is service leaf, you cannot enable the multicast network feature for the vRouter：当虚拟路由器绑定Service Leaf类型防火墙时，不允许开启组播网络 · The vRouter is bound to a gateway whose firewall deployment mode is off and method to deploy basic external connectivity settings is manual. You cannot bind the vRouter to an external network that does not have gateway bindings or has vPort-vRouter bindings without a gateway specified：当虚拟路由器绑定设备组防火墙接入模式为关闭且外网转发基础配置为手动预配置的出口网关时，不可同时绑定未指定出口网关的外部网络，或者未指定出口网关的已被虚拟路由器外网虚拟端口绑定的外部网络 · The vRouter is bound to a gateway whose firewall deployment mode is off and method to deploy basic external connectivity settings is manual. You cannot bind the vRouter to a vPort associated with an external network that has no gateway binding：当虚拟路由器绑定设备组防火墙接入模式为关闭且外网转发基础配置为手动预配置的出口网关时，不支持绑定未指定出口网关的的外部网络中的虚拟端口 · When you bind a vRouter to an external network that has no vPort bindings, the external network's subnets cannot overlap with the access subnet for the firewall associated with the vRouter：虚拟路由器绑定未被虚拟路由器外网虚拟端口绑定的外部网络时，该外网下的子网不能和防火墙接入网段存在重叠 · When you bind an internal subnet to the vRouter, the subnet cannot overlap with the access subnet for the firewall associated with the vRouter：虚拟路由器绑定内网子网时，该内网子网不能和防火墙接入网段存在重叠 · When you bind a vRouter to a directly-connected external network, the external network's subnets cannot overlap with the access subnet for the firewall associated with the vRouter：虚拟路由器绑定独享外网时，该外网下的子网不能和防火墙接入网段存在重叠 · When you bind a vRouter to an external vPort, the subnets of the external network associated with the vPort cannot overlap with the access subnet for the firewall associated with the vRouter：虚拟路由器绑定外部网络中的虚拟端口时，该外网下的子网不能和防火墙接入网段存在重叠 · If the following conditions exist, you cannot bind a vRouter to any external network that has no gateway binding: ¡ The edge device to external networks for the vRouter is firewall. ¡ firewall service type specified for the vRouter is service leaf. 当虚拟路由器的外网出口设备为防火墙且绑定Service Leaf类型防火墙时，不支持绑定未指定出口网关的外部网络 · If the following conditions exist, you cannot bind a vRouter to any external network that has no segment ID: ¡ The edge device to external networks for the vRouter is firewall. ¡ The firewall service type specified for the vRouter is service leaf. 当虚拟路由器的外网出口设备为防火墙且绑定Service Leaf类型防火墙时，不支持绑定未指定External Segment ID的外部网络 · If the following conditions exist, you can only bind a vRouter to any external network that has no vPort bindings and has a gateway whose firewall deployment mode is off: ¡ The edge device to external networks for the vRouter is firewall. ¡ The firewall service type specified for the vRouter is service leaf. 当虚拟路由器的外网出口设备为防火墙且绑定Service Leaf类型防火墙时，仅支持绑定设备组防火墙接入模式为关闭的出口网关的未被虚拟路由器外网虚拟端口绑定的外部网络 · If the following conditions exist, you cannot bind a vRouter to any external network that has a gateway whose method to deploy basic external connectivity settings is auto: ¡ The edge device to external networks for the vRouter is firewall. ¡ The firewall service type specified for the vRouter is service leaf. 当虚拟路由器的外网出口设备为防火墙且绑定Service Leaf类型防火墙时，不支持绑定出口网关外网转发基础配置为自动下发的外部网络 · If the following conditions exist, you cannot bind a vRouter to any external network that has a gateway whose firewall deployment mode is off: ¡ The edge device to external networks for the vRouter is firewall. ¡ The firewall service type specified for the vRouter is not service leaf. 当虚拟路由器的外网出口设备为防火墙且绑定非Service Leaf类型防火墙时，不支持绑定出口网关设备组防火墙接入模式为关闭的外部网络 · If the following conditions exist, you cannot bind an external vPort to the vRouter: ¡ You have enabled firewall for the external vPort. ¡ The external network bound to the vPort has no segment ID. ¡ The firewall service type specified for the vRouter is service leaf. 虚拟路由器绑定Service Leaf类型防火墙时，不支持绑定未指定External Segment ID的外部网络中防火墙开关开启的虚拟端口 · If the following conditions exist, you cannot bind an external vPort to the vRouter: ¡ You have enabled firewall for the external vPort. ¡ The external network bound to the vPort has no gateway binding. ¡ The firewall service type specified for the vRouter is service leaf. 虚拟路由器绑定Service Leaf类型防火墙时，不支持绑定未指定出口网关的外部网络中防火墙开关开启的虚拟端口 · If the following conditions exist, you can bind an external vPort to the vRouter: ¡ You have enabled firewall for the external vPort. ¡ The external network bound to the vPort has a gateway whose firewall deployment mode is off. ¡ The firewall service type specified for the vRouter is service leaf. 虚拟路由器绑定Service Leaf类型防火墙时，仅支持绑定设备组防火墙接入模式为关闭出口网关的外部网络中防火墙开关开启的虚拟端口 · If the following conditions exist, you cannot bind an external vPort to the vRouter: ¡ You have enabled firewall for the external vPort. ¡ The external network bound to the vPort has a gateway whose method to deploy basic external connectivity settings is auto. ¡ The firewall service type specified for the vRouter is service leaf. 虚拟路由器绑定Service Leaf类型防火墙时，不支持绑定外网转发基础配置为自动下发的出口网关的外部网络中防火墙开关开启的虚拟端口 · If the following conditions exist, you cannot bind an external vPort to the vRouter: ¡ You have enabled firewall for the external vPort. ¡ The firewall service type specified for the vRouter is service leaf. ¡ The vRouter is bound to a centralized vRouter link that is not enabled with firewall or route reduction. 虚拟路由器绑定Service Leaf类型防火墙，且该虚拟路由器已绑定两端防火墙关闭且路由精简开关关闭的集中式虚拟路由器连接时，不支持绑定外部网络中防火墙开关开启的虚拟端口 · If the following conditions exist, you cannot bind an external vPort to the vRouter: ¡ You have enabled firewall for the external vPort. ¡ The external network bound to the vPort has a gateway whose firewall deployment mode is off. ¡ The firewall service type specified for the vRouter is not service leaf. 虚拟路由器绑定非Service Leaf类型防火墙时，不支持绑定设备组防火墙接入模式为关闭出口网关的外部网络中防火墙开关开启的虚拟端口 · If the following conditions exist, you cannot enable firewall for an external vPort bound to the vRouter: ¡ The firewall service type specified for the vRouter is service leaf. ¡ The external network bound to the vPort has no segment ID. 虚拟路由器绑定Service Leaf类型防火墙和未指定External Segment ID外部网络中的虚拟端口时，该虚拟端口的防火墙开关不允许从关闭到开启 · If the following conditions exist, you cannot enable firewall for an external vPort bound to the vRouter: ¡ The firewall service type specified for the vRouter is service leaf. ¡ The external network bound to the vPort has no gateway binding. 虚拟路由器绑定Service Leaf类型防火墙和未指定出口网关外部网络中的虚拟端口时，该虚拟端口的防火墙开关不允许从关闭到开启 · If the following conditions exist, you cannot enable firewall for an external vPort bound to the vRouter: ¡ The firewall service type specified for the vRouter is service leaf. ¡ The vPort's external network is bound to a gateway whose method to deploy basic external connectivity settings is auto. 虚拟路由器绑定Service Leaf类型防火墙和指定外网转发基础配置为自动下发的出口网关的外部网络中的虚拟端口时，该虚拟端口的防火墙开关不允许从关闭到开启 · If the following conditions exist, you cannot enable firewall for an external vPort bound to the vRouter: ¡ The firewall service type specified for the vRouter is service leaf. ¡ The vPort's external network is bound to a gateway whose firewall deployment mode is not off. 虚拟路由器绑定Service Leaf类型防火墙和指定设备组防火墙接入模式为非关闭的出口网关的外部网络中的虚拟端口时，该虚拟端口的防火墙开关不允许从关闭到开启 · You cannot enable firewall service for the external vPorts bound to the vRouter. This is because the firewall service type specified for a vRouter is service leaf, the vRouter is one end of a centralized-mode vRouter link that has route reduction off and firewall service off at both ends：虚拟路由器绑定Service Leaf类型防火墙和两端防火墙关闭且路由精简开关关闭的集中式虚拟路由器连接时，不支持虚拟路由器绑定的外网虚拟端口防火墙开关从关闭切换为开启 · When you bind an external subnet to the vRouter, the subnet cannot overlap with the access subnet for the firewall associated with the vRouter：虚拟路由器绑定外网子网时，该外网子网与防火墙接入网段不能重叠 · Unsupported device type：该设备的设备类型不支持 · After you select a gateway whose firewall deployment mode is off and method to deploy basic external connectivity settings is manual, you cannot enable OSPF for the external network, and vice versa：外部网络不允许同时配置OSPF路由协议和绑定设备组防火墙接入模式为关闭且外网转发基础配置为手动预配置的出口网关 · After you bind to the external network a gateway whose firewall deployment mode is off and method to deploy basic external connectivity settings is manual, you cannot configure any NQA profile-subnet bindings, and vice versa：外部网络不允许同时配置子网绑定NQA策略和绑定设备组防火墙接入模式为关闭且外网转发基础配置为手动预配置的出口网关 · After you bind to the external network a gateway whose firewall deployment mode is off and method to deploy basic external connectivity settings is manual, you cannot enable primary IP allocation for any subnets, and vice versa：外部网络不允许同时开启子网主IP所在子网和绑定设备组防火墙接入模式为关闭且外网转发基础配置为手动预配置的出口网关 · After you select a gateway whose firewall deployment mode is off and method to deploy basic external connectivity settings is manual, you must configure a segment ID for the external network：当外部网络绑定设备组防火墙接入模式为关闭且外网转发基础配置为手动预配置的出口网关时，必须配置External Segment ID · When a vRouter has been bound to the external network, the external subnets cannot overlap with the subnet for firewall access：外部网络已被虚拟路由器绑定时，外网子网与防火墙接入网段重叠 · The external network is bound to a gateway whose firewall deployment mode is off and method to deploy basic external connectivity settings is manual. You must configure a segment ID：当外部网络绑定设备组防火墙接入模式为关闭且外网转发基础配置为手动预配置的出口网关时，External Segment ID不允许配置为空 · A vRouter that has border gateway bindings is bound to the external network. You cannot bind to the external network a gateway whose firewall deployment mode is off and method to deploy basic external connectivity settings is manual：外部网络已被虚拟路由器绑定且该虚拟路由器绑定了出口网关时，外部网络不允许绑定设备组防火墙接入模式为关闭且外网转发基础配置为手动预配置出口网关 · A vRouter that has a non-service leaf firewall binding is bound to the external network. You cannot bind a gateway whose firewall deployment mode is off to the external network：外部网络已被虚拟路由器绑定且该虚拟路由器绑定了非Service Leaf类型的防火墙时，不允许绑定设备组防火墙接入模式为关闭的出口网关 · You cannot disable firewall service for an external vPort bound to a vRouter when the following conditions exist: ¡ The vPort's external network is bound to a gateway that uses a device group with firewall deployment off and uses manual basic external connectivity deployment.. ¡ The border gateway bound to the vRouter is different from that bound to the vPort's external network. 外网虚拟端口所属的外部网络的出口网关设备组防火墙接入模式为关闭且外网转发基础配置为手动预配置，虚拟路由器绑定的出口网关和该外部网络指定的出口网关不一致时，该虚拟端口的防火墙开关不允许从开启切换为关闭 · The vRouter is bound to a service leaf firewall. Please make sure the firewall is enabled or disabled across all IP addresses and subnets in the external network：虚拟路由器绑定了Service Leaf类型的防火墙时，同外部网络下的外网子网过墙行为必须一致 · You cannot bind a flat-type external network to a vRouter that uses a service-leaf attached firewall as the edge device to the external network：当虚拟路由器的外网出口设备为防火墙且绑定Service Leaf类型防火墙时，不支持绑定FLAT类型的外部网络 · Auto basic external connectivity deployment is not available for the border gateway on an external network attached to a firewall-enabled vPort if the vPort is bound to a vRouter configured with a leaf-attached firewall：虚拟路由器绑定Service Leaf类型防火墙下，绑定防火墙开关为开启的虚拟端口时，虚拟端口所关联外部网络中指定的出口网关外网转发基础配置不支持自动下发模式 · When you bind an external network to a vRouter that uses a leaf-attached firewall as the edge device to the external network, the external network must meet the following requirements: 1. The network type is VLAN and the operating mode is indirectly connected. 2. The gateway to the external network uses manual basic external connectivity deployment and is bound to a device group with firewall deployment off. 3. The vRouter is not bound to any vPorts attached to the external network：当虚拟路由器的外网出口设备为防火墙且绑定Service Leaf类型防火墙时，绑定的外部网络必须满足：1）VLAN类型，2）共享模式，3)指定出口网关，该出口网关为手动预配置，且关联的设备组防火墙接入模式为关闭，4）未绑定此外部网络下的虚拟端口 · Please edit the tenant or vRouter name to ensure that the generated VPN instance name does not start with "external_vpn"：自动生成的VPN实例名称不能以"external_vpn"开头，请根据VPN实例名称生成规则检查并修改租户名称或者虚拟路由器名称 · The external network egress IP is already bound to a vRouter. For vRouters to share this IP, make sure these vRouters use the same third-party firewall setting. You can configure this setting when you configure the device group associated with a gateway member of a border gateway bound to a vRouter：该外网出口IP已被其他虚拟路由器绑定，如需共享，需确保共享该IP的所有虚拟路由器绑定的出口网关对应的设备组第三方防火墙开关必须一致 · Transit vRouters do not support configuring the tags field：TRANSIT类型虚拟路由器不支持配置tags字段 · When you configure the tags field for a normal or external transit vRouter, do not specify any tenant-exclusive border gateway：NORMAL或者EXTERNALTRANSIT类型虚拟路由器的tags字段中不能包含租户独占的出口网关 · You must specify import RTs for a transit vRouter：虚拟路由器是TRANSIT类型时，必须指定引入RT · You must specify export RTs for a transit vRouter：虚拟路由器是TRANSIT类型时，必须指定引出RT · You must specify import RTs for an external transit vRouter：虚拟路由器是EXTERNALTRANSIT类型时，必须指定引入RT · You must specify export RTs for an external transit vRouter：虚拟路由器是EXTERNALTRANSIT类型时，必须指定引出RT · Make sure the import RTs and export RTs are consistent on a vRouter：虚拟路由器配置的引入RT与引出RT不一致 · Invalid BGP peer authentication mode：无效的BGP对等体认证模式 · Password configuration is not supported if the BGP peer authentication mode is not Password Authentication：未指定BGP对等体认证模式为密码认证时不允许配置密码 · Password configuration is required if the BGP peer authentication mode is Password Authentication：指定BGP对等体认证模式为密码认证时不允许密码为空 · The password is case sensitive and cannot exceed 80 characters. Only letters, digits, and special characters except for question marks (?) are supported：密码长度最长80个字符，区分大小写，仅支持英文、数字和特殊字符（英文问号除外） · Cannot allocate this segment ID, because synchronization is in progress for the VXLAN pool containing this segment ID：无法分配该Segment ID，其所在的VXLAN池正在平滑中 · Cannot allocate segment IDs automatically, because no VXLAN pool is configured：未配置VXLAN池，无法自动分配Segment ID · Cannot allocate segment IDs automatically, because the VXLAN pool does not have available resources：VXLAN池中资源已耗尽，无法自动分配Segment ID · Cannot allocate segment IDs automatically. Please verify correctness of the VXLAN pool configuration and status：无法自动分配Segment ID，请检查VXLAN池配置及状态 · Resource application or rollback failed, internal unknown error：资源申请或回滚失败，内部未知错误 · The（resource）does not exist or the resources are insufficient：（资源）不存在或资源不足 · The（resource）does not exist or the resources are insufficient, device group name（name）：（资源）不存在或资源不足，设备组名称（名称） · The （resource） does not exist or the resources are insufficient, resource access template name （name）：（资源）不存在或资源不足，资源接入模板名称（名称） · In the IPv6 scenario, a vRouter cannot have the same subnet bindings or external network binding as another vRouter：IPv6场景下，不允许存在绑定相同子网网段、相同外部网络的虚拟路由器 · The source IP address cannot be the IP address that the device uses as the interconnect address in an M-LAG routed peer link：源IP地址不能与M-LAG互联链路中相同设备的本端或对端互联地址相同 · The gatewaylist field is a read-only field：gatewaylist为只读字段 |
|
关键字 |
UPDATE_ROUTE_OP |
|
日志内容 |
Updated vRouter “$1”. |
|
参数解释 |
$1：虚拟路由器的名称 |
|
举例 |
Updated vRouter ”router01” |
|
日志说明 |
用户进行了修改路由器的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The subnet and the router are not in the same VDS：子网和虚拟路由器不在同一个VDS · The specified external network doesn’t exist：所选的外部网络不存在 · The specified external network has no subnet：所选的外部网络中没有子网，请先配置子网 · Failed to bind the router to the external network, because the external subnet doesn’t have enough assignable IP addresses：绑定外网失败，外网子网没有可分配的IP地址 · The router ID is required：未指定虚拟路由器ID · The specified resource doesn't exist：指定的资源不存在 · Invalid external IP binding. An external IP address has been bound to a minimum of one vRouter. To share that external IP address, the vRouters must be assigned the same service resources：该外网出口IP已被其他虚拟路由器绑定，如需共享，需确保共享该IP的所有虚拟路由器绑定相同的服务资源 · The IP address is already used by another port：该IP地址已被其他端口占用 · Invalid routing table：无效的路由表 · The segment ID number is already used：Segment ID number已经被使用 · The segment ID is out of range：Segment ID超出范围 · The AS number is required：未指定AS号 · The value for the maximum number of ECMP routes is invalid：最大等价路由条目不可用 · Invalid summary route network：聚合路由网段不可用 · The ID of the routing table is different than the vRouter：指定的路由表ID与虚拟路由器ID不一致 · The IPv4 address of the peer is required：未指定对等体的IPv4地址 · Invalid CIDR：无效的CIDR · The AS number of the peer is invalid：无效的对等体AS号 · The is_bind_gw field is a read-only field：is_bind_gw为只读字段 · The subnet overlaps with another subnet：子网与其他的子网重叠 · The subnet must belong to the specified network：子网不在指定的虚拟链路层网络内 · The CIDR overlaps with another CIDR：CIDR配置中有重叠项 · Failed to bind the vRouter to an external network because the specified network is not an external network：虚拟路由无法与该外网绑定，因为选定的网络不是外网 · The IP address doesn't belong to the network：该IP地址不属于该网络 · The IP address doesn't belong to the subnet：指定的IP地址不属于该子网 · The extranet IP is invalid：外网IP无效 · The external network is required：外网不能为空 · The subnet and the extranet IP can't both be null：子网和外网IP不能同时为空 · The extranet IP conflicts with a floating IP：外网IP与浮动IP冲突 · The extranet IP conflicts with a gateway IP：外网IP与网关IP冲突 · The extranet IP conflicts with the broadcast address of the subnet：外网IP地址和子网广播IP地址冲突 · The extranet IP conflicts with the subnet address：外网IP地址和子网地址冲突 · The external subnet doesn't exist：外网子网不存在 · Invalid external IP binding. An external IP address has been bound to a minimum of one vRouter. To share that external IP address, the vRouters must be bound to the gateway resources that use the same border device group：该外网出口IP已被其他虚拟路由器绑定，如需共享，需确保共享该IP的所有虚拟路由器绑定的网关资源的边界设备组相同 · Invalid external IP binding. An external IP address has been bound to a minimum of one vRouter. To share that external IP address, the vRouters must be bound to the gateway resources that use the same type of border device group：该外网出口IP已被其他虚拟路由器绑定，如需共享，需确保共享该IP的所有虚拟路由器绑定的网关资源的边界设备组类型相同 · The extranet IP has been used by another gateway resource：该外网IP地址已被其他网关资源占用 · The vRouter cannot be configured with the same summary route network：不允许配置重复的聚合路由网段 · The vRouters using the public network VPN can not be bound to the same service gateway group：使用公网VPN的虚拟路由器不能绑定同一个服务网关组 · The specified device doesn't exist：指定的设备不存在 · The device ID and the device name do not match：设备的ID和名称不匹配 · The BGP peer already exists：存在冲突的BGP对等体 · The vRouter name cannot exceed 255 characters：虚拟路由器名称最长255个字符 · The VPN instance name cannot exceed 31 bytes：VPN实例名称最长31个字节 · Make sure all vRouters that use this sharing IP are bound to the same edge device for external network access：共享IP绑定的所有虚拟路由器的外网出口设备必须相同 · When the value of the direct_external field is true, the external network bound to the vRouter must be a VLAN and the value of the force_flat field must be false：当dierct_external为true时，虚拟路由器绑定的外部网络必须为VLAN类型且外部网络的force_flat必须为false · You cannot bind a vRouter to both a VLAN-type external network and a virtual firewall configured with a security external network if either of the following conditions exists: 1The vRouter uses a firewall as the edge device to the external network. 2. A vPort bound to the vRouter is enabled with the firewall feature：外网出口设备为防火墙或者外网虚拟端口防火墙开启时，虚拟路由器不能同时绑定存在安全外网的虚拟防火墙和VLAN类型的外部网络 · If a vRouter uses a firewall as the edge device to the external network, the vRouter cannot be bound to a virtual firewall configured with a security external network and an external network of the VLAN type at the same time：外网出口设备为防火墙时，虚拟路由器不能同时绑定存在安全外网的虚拟防火墙和VLAN类型的外部网络 · The router and network doesn't belong to the same VDS：虚拟链路层网络与虚拟路由器不属于同一个VDS · The exit gateway corresponding to the subnet repeats：虚拟路由器绑定的多个外网子网对应的出口网关不能相同 · You must specify a priority value for each subnet when more than one subnet is bound to the vRouter：绑定的子网多于一个时，必须指定优先级 · The tags field has duplicate segment IDs：字段Tags存在重复的Segment ID · The tags field has duplicate priorities：字段tags中存在重复的优先级 · Invalid priority：无效的优先级 · The external subnet is bound to the vRouter：外网子网已被虚拟路由器绑定 · The external network bound to the vRouter does not have segments. The vRouter can be bound only to one IPv4 subnet：指定的外部网络未配置Segment，只能绑定一个IPv4子网 · If a vRouter uses a firewall as the edge device to the external network or a vPort bound to the vRouter is enabled with the firewall feature, you cannot bind both the following items to the vRouter: 1. An external subnet associated with a VLAN-type network segment. 2. A virtual firewall configured with a security external network.：外网出口设备为防火墙或者外网虚拟端口防火墙开启时，虚拟路由器不能同时绑定存在安全外网的虚拟防火墙和Segment为VLAN类型的外网子网The vRouter to which the external network belongs is in a vRouter link, and a vPort on the peer vRouter of the vRouter link has been bound to the floating IP address of the external network：外部网络所属的虚拟路由器已建立虚拟路由器连接，且对端虚拟路由器下的虚拟端口已绑定了该外部网络的浮动IP · The specified external network is segmented and has only IPv4 subnets. You must bind at least one of its IPv4 subnets to the vRouter：指定的外部网络已开启网络分段功能，且只存在IPv4子网时，虚拟路由器绑定的IPv4外网子网不能为空 · The external network is segmented. You cannot unbind a subnet from the vRouter if that subnet is an IPv4 subnet and is the only subnet in the external network：虚拟路由器绑定了已开启网络分段功能的外部网络，且仅绑定了IPv4外网子网时，绑定的IPv4外网子网不能为空 · The border gateways to the IPv4 and IPv6 external subnets are located on the same interface. You must configure them with the same segment ID：IPv4外网子网和IPv6外网子网的出口网关相同时，Segment ID必须相同 · The external network egress IP has been bound to another vRouter. To bind the current vRouter to the external network egress IP, you must make sure the current vRouter has exactly the same external subnet bindings as that vRouter：虚拟路由器绑定多个外网子网，且多个虚拟路由器共享外网IP时，必须同时共享所有外网IP · Unknown error：未知错误 · The address pool does not exist or no IP addresses are available in the address pool：绑定服务资源失败，指定的地址池不存在，或该地址池内没有足够的IP地址 · The external network specified for the vRouter is not segmented. You can bind only one IPv4 subnet and one IPv6 subnet to the vRouter：指定的外部网络未配置网络分段时，虚拟路由器只允许绑定一个IPv4和IPv6子网 · The vRouter is bound to multiple IPv4 and IPv6 external subnets. The network segments to which external subnets of the same IP version are bound cannot be bound to the same border gateway：虚拟路由器绑定多个的外网子网时，同IP版本外网子网对应的出口网关不能相同 · The border gateways to the IPv4 and IPv6 external subnets are located on the same interface. You must configure them with the same segment ID：IPv4外网子网和IPv6外网子网的出口网关相同时，Segment ID必须相同 · The segment or border gateway already has a priority：不允许重复配置网络分段或者出口网关的优先级 · If a vRouter is bound to both a gateway resource and a network segment, you can configure a priority for either the gateway resource or the network segment, but not both：不能同时配置网关资源和网络分段的优先级 · You cannot assign priorities to the external subnets bound to the vRouter if they belong to different segments configured with the same border gateway：虚拟路由器绑定不同IP版本外网子网时，若外网子网绑定了不同的网络分段且网络分段绑定了相同的出口网关，则不允许配置外网子网的优先级 · If service resources have been bound to a virtual router, the border gateways bound to the virtual router must have different priorities：虚拟路由器已绑定服务资源时，两个出口网关的优先级不允许相同 · Invalid tags：无效的tags · The priority is out of range：tags优先级超出范围 · The specified segment doesn't exist：指定的网络分段不存在 · The specified gateway doesn't exist：指定的网关资源不存在 · Cannot configure a priority for the gateway resource. For more information, see the online help：该网关资源不支持配置优先级 ，具体情况请查看联机帮助 · External subnets of the same version bound to the vRouter cannot be bound to the same network segment：指定的外部网络已开启网络分段功能，虚拟路由器绑定的外网子网不能为空 · Cannot specify a gateway resource configured with a priority and a segmented external network for a vRouter at the same time：网关资源的优先级和开启网络分段的外网不允许同时配置 · The external network specified for the vRouter is segmented. You must bind a minimum of one external subnet to the vRouter：指定的外部网络已开启网络分段功能，虚拟路由器绑定的外网子网不允许为空 · The external network egress IP has already been bound to a vRouter that uses different gateway resources from the current vRouter. Only vRouters that use the same gateway resources can share an external network egress IP：该外网出口IP已被其他虚拟路由器绑定，如需共用，需确保共用该IP的所有虚拟路由器绑定相同的网关资源 · The source IP address of a route entry with a vPort-type next hop on the vRouter cannot overlap with any vNetwork subnet on another vRouter：建立虚拟路由器连接的两个虚拟路由器，一个虚拟路由器下虚拟端口类型的路由表项的源IP不允许和另一个虚拟路由器下虚拟链路层网络的子网重叠 · The source IP address of a route entry with a vPort-type next hop on the vRouter cannot overlap with any external subnet on another vRouter：建立虚拟路由器连接的两个虚拟路由器，一个虚拟路由器下虚拟端口类型的路由表项的源IP不允许和另一个虚拟路由器下外部网络的子网重叠 · The source IP address of a route entry with a vPort-type next hop on the vRouter cannot be the same as any vNetwork subnet gateway IP of another vRouter：建立虚拟路由器连接的两个虚拟路由器，一个虚拟路由器下虚拟端口类型的路由表项的源IP不允许和另一个虚拟路由器下虚拟链路层网络子网的网关IP地址相同 · The source IP address of a route entry on the vRouter cannot be the same as any vNetwork subnet gateway IP on the vRouter：源IP地址不允许和同一虚拟路由器下虚拟链路层子网的网关IP地址相同 · The source IP address of a route entry on the vRouter cannot be within any vNetwork subnet on the vRouter：源IP地址不允许在同一虚拟路由器下虚拟链路层子网网段范围内 · The source IP address of a route entry on the vRouter cannot be within any external subnet on the vRouter：源IP地址不允许在同一虚拟路由器下外部网络的子网网段范围内 · Failed to bind the vRouter to an external network because the specified network is not an indirectly connected external network：虚拟路由器无法与该外网绑定，因为选定的网络不是共享型外网 · Failed to configure BGP peers for the vRouter because the vRouter has been configured with BGP neighbors：绑定BGP对等体失败，指定的虚拟路由器下已经绑定了BGP邻居 · Cannot disable east-west traffic offload in network cloud scenarios：网络云场景下不允许关闭东西向流量卸载开关 · You cannot bind the routing table to the vRouter. The routing table contains a BFD-enabled route entry whose next hop is a vPort with the same IP address as the gateway IP address of a vNetwork bound to the vRouter：绑定路由表失败，路由表项的下一跳类型为虚拟端口且开启BFD功能时，下一跳IP地址不允许和同一虚拟路由器下虚拟链路层网络的网关IP地址相同 · Failed to enable multicast capabilities because the vRouter has already established a vRouter link：使能组播网络失败。该虚拟路由器已经建立了虚拟路由器连接 · You have no privilege to perform this operation：用户无权限执行此操作 · Cannot enable multicast network capabilities for the vRouter because the vRouter has been bound to a Layer 3 DC interconnect：指定的虚拟路由器已绑定数据中心三层互联，不允许开启组播网络 · A vRouter cannot be bound to internal network vPorts：虚拟路由器仅支持绑定外网虚拟端口 · Cannot bind the external network vPort to the vRouter, because the vRouter has been bound to the external network to which the vPort belongs：虚拟路由器已绑定外部网络，不允许绑定该外网虚拟端口 · A vRouter cannot be bound to multiple IPv6 external network vPorts in the same network：虚拟路由器绑定多个IPv6外网虚拟端口时，这些端口所属的外部网络不能相同 · Cannot bind the external network to the vRouter, because the vRouter has been bound to a vPort in the external network：虚拟路由器已绑定外网虚拟端口，不允许再绑定该端口所属的外部网络 · You cannot bind the vRouter to a segmented external network. The vRouter uses a firewall as the edge device to the external network and has been bound to a device group that uses the hairpin or inline third-party firewall deployment mode：边界设备对接第三方防火墙开关取值为旁挂或直连时，外网出口设备为防火墙的虚拟路由器不能绑定开启了网络分段的外部网络 · The RT generated based on the segment ID of the vRouter conflicts with the import RT of a Layer 2 DC interconnect：虚拟路由器Segment ID生成的RT与数据中心二层互联的引入RT冲突 · The RT generated based on the segment ID of the vRouter conflicts with the export RT of a Layer 2 DC interconnect：虚拟路由器Segment ID生成的RT与数据中心二层互联的引出RT冲突 · The RT reserved for the vRouter link conflicts with the import RT of a Layer 2 DC interconnect：系统预留的虚拟路由器连接的RT与数据中心二层互联的引入RT冲突 · The RT reserved for the vRouter link conflicts with the export RT of a Layer 2 DC interconnect associated with the local or remote vRouter：系统预留的虚拟路由器连接的RT与数据中心二层互联的引出RT冲突 · The RT generated based on the segment ID of the vRouter conflicts with the import RT of a Layer 3 DC interconnect：虚拟路由器Segment ID生成的RT与数据中心三层互联的引入RT冲突 · The RT generated based on the segment ID of the vRouter conflicts with the export RT of a Layer 3 DC interconnect：虚拟路由器Segment ID生成的RT与数据中心三层互联的引出RT冲突 · The RT reserved for the vRouter link conflicts with the import RT of a Layer 3 DC interconnect：系统预留的虚拟路由器连接的RT与数据中心三层互联的引入RT冲突 · The RT reserved for the vRouter link conflicts with the export RT of a Layer 3 DC interconnect：系统预留的虚拟路由器连接的RT与数据中心三层互联的引出RT冲突 · Cannot bind the subnet to a vRouter if the subnet is used for primary IP allocation：如果外部网络的子网被指定为主IP所在子网时，外部网络的子网不能绑定虚拟路由器 · Subnets in the external network do not have sufficient IP addresses for allocation：外部网络下的子网可分配IP不足 · Failed to assign IP addresses to devices attached to the border gateway, because the IP addresses in the primary IP allocation are insufficient：为出口网关下的设备分配IP失败，主IP所在子网地址不足 · Cannot bind the subnet to a vRouter if the subnet is used for primary IP allocation：如果外部网络的子网被指定为主IP所在子网时，外部网络的子网不能绑定虚拟路由器 · Check the directly connected external networks and the border interfaces in the device group bound to this vRouter with the same segment ID. Make sure only one primary IPv4 address exists for each border interface：虚拟路由器下的独享型外网子网和该虚拟路由器绑定的设备组中的外网出口使用相同Segment ID时，最多只允许有一个主IP · vRouters do not support vPorts in flat external networks：虚拟路由器不支持绑定FLAT类型的外部网络中的虚拟端口 · The vRouter context or external network vPort context has been used in a service chain：指定的虚拟路由器或外部网络虚拟端口类型的流量特征组已被服务链使用 · Please specify two and only two external subnets for the external context. This is required because the context uses primary/backup gateway deployment mode and the edge device to the external network in the vRouter for the context is the border device：主备出口模式下，如果南北向服务链是直出外网，External类型的流量特征组必须指定两个外网子网 · The external subnet has been bound to a context. Please access the context page to remove the binding first：该虚拟路由器的外网子网已关联流量特征组，请先前往流量特征组页面取消关联 · The context uses primary/backup gateway deployment mode. Make sure the associated vRouter is bound to two gateway members or external subnets：流量特征组为主备出口模式时，关联的虚拟路由器必须绑定两个出口网关成员或两个外网子网 · The context uses single gateway deployment mode. Make sure the associated vRouter is bound to one gateway member or external subnet：流量特征组为单出口模式时，关联的虚拟路由器必须绑定一个出口网关成员或一个外网子网 · The vRouter-attached gateway members enable the third-party firewall option. Please enable or disable the firewall option across all IP addresses or subnets in the vRouter-attached external network if the egress of the external network is the firewall or border device, respectively：虚拟路由器绑定了第三方防火墙开启的设备组，该虚拟路由器绑定外部网络下的外网子网防火墙设置需要和虚拟路由器上的外网出口设置一致 · The vRouter-attached gateway members disable the third-party firewall option and use hairpin firewall deployment. Please make sure the firewall is enabled or disabled across all IP addresses and subnets in the external network：虚拟路由器绑定了第三方防火墙关闭且防火墙接入模式是旁挂的设备组，同外部网络下的外网子网过墙行为必须一致 · Failed to unbind the vRouter from the external network. The vRouter has been bound to a Layer 3 multicast network or a multicast source used for external services：解绑失败。指定的虚拟路由器已经绑定了使能外网业务的组播或组播源 · Not enough addresses in subnets in network segment：网络分段内可分配IP不足 · Failed to unbind the vRouter from the subnet. The subnet has been bound to a Layer 3 multicast network or a multicast source used for external services：解绑子网失败，指定子网对应的外部网络已经绑定了L3组播或组播源 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · The segment ID cannot be identical to a VXLAN ID in a VXLAN pool or the VXLAN ID reserved for the automation template and the M-LAG system：Segment ID不能在VXLAN池范围内且不能和自动化模版、M-LAG系统的保留VXLAN ID重叠 · Please specify a peer IP address or network address：对等体IP地址/网段不能为空 · Invalid peer IP address or network address：对等体IP地址/网段无效 · Invalid source IP address：源IP地址无效 · Invalid IP version：IP版本无效 · Neighbor IP/network address must be of the same IP version as the source IP address：对等体IP地址/网段与源IP地址必须为相同IP版本 · Neighbor IP/network address and IP version are inconsistent：对等体IP地址/网段和IP版本不一致 · The peer IP address cannot be the same as the source IP address：对等体地址和源IP地址不能相同 · Please specify the device ID, device name, or both：设备ID和设备名称不能为空 · You cannot edit or delete the cloud region name：云区域名称不允许修改或删除 · You cannot edit the segment ID of the vRouter, because the vRouter has OVS vPorts：当虚拟路由器中存在ovs类型的虚拟端口时，不允许修改已配置的Segment ID · You cannot configure CIDR addresses for the vRouter, because the vRouter is in a vRouter link configured with local or remote subnets：指定的虚拟路由器已绑定配置了本端或对端子网的虚拟路由器连接，不允许配置CIDR · The subnet has been specified as a local or remote subnet for a vRouter link：指定的子网已被虚拟路由器连接下的本端或对端子网使用 · The network addresses of some neighbors overlap：BGP对等体中存在网段重叠 · The value for the create_loopback parameter cannot be true when no source IP address is specified：源IP地址为空时，不允许开启创建LoopBack口开关 · BGP neighbors with the same source IP address must be consistent in the value for the create_loopback parameter：相同源IP地址的BGP对等体的创建LoopBack口开关必须一致 · You cannot edit the create_loopback parameter：不允许修改创建LoopBack口开关 · The external network contains only subnets for primary IP allocation. Please make sure the external network also contains subnets with primary IP allocation disabled：指定的外部网络下不允许仅有主IP所在的子网 · You cannot bind the external subnet to the vRouter. The gateway address for the subnet is the next hop address of a route entry bound to the vRouter. You cannot bind them when the external subnet and that route entry are each bound to an NQA profile：虚拟路由器的路由表项的下一跳IP地址与外网子网网关IP相同，且路由表项已绑定NQA策略，则虚拟路由器不允许绑定配置了NQA策略的外部网络 · You cannot unbind the routing table from the vRouter, because the routing table contains route entries configured with a BFD session：该路由表中存在配置了BFD会话的路由表项,不允许解绑该路由表 · Failed to unbind the vRouter from the external network, because the vRouter and the external network (or a segment of the external network) have been bound to the same Layer 3 multicast network：解绑失败，L3组播使用了该虚拟路由器及其绑定的外部网络或网络分段 · A transit vRouter cannot be bound to an internal subnet：虚拟路由器是TRANSIT类型时，不支持绑定内网子网 · A transit vRouter does not support aggregate CIDRs：虚拟路由器是TRANSIT类型时，不支持Aggregate CIDRs · A transit vRouter does not support CIDRs：虚拟路由器是TRANSIT类型时，不支持CIDRs · A normal vRouter does not support export RTs：虚拟路由器是NORMAL类型时，不支持引出RT · A normal vRouter does not support import RTs：虚拟路由器是NORMAL类型时，不支持引入RT · Invalid export target：无效的引出RT · Invalid import target：无效的引入RT · The vRouter type is invalid：无效的虚拟路由器类型 · The import RT %s of the vRouter conflicts with the RT of a Layer 2 DC interconnect：虚拟路由器配置的引入RT与数据中心二层互联的RT冲突 · The export RT %s of the vRouter conflicts with the RT of a Layer 2 DC interconnect：虚拟路由器配置的引出RT与数据中心二层互联的RT冲突 · The import RT %s of the vRouter conflicts with the RT of a Layer 3 DC interconnect：虚拟路由器配置的引入RT与数据中心三层互联的RT冲突 · The export RT %s of the vRouter conflicts with the RT of a Layer 3 DC interconnect：虚拟路由器配置的引出RT与数据中心三层互联的RT冲突 · The export RT on the vRouter conflicts with the RT on a vNetwork：虚拟路由器配置的引出RT与虚拟链路层网络的RT冲突 · The export RT of the vRouter conflicts with an RT reserved for fabric interconnects：虚拟路由器配置的引出RT与系统预留的Fabric互联RT冲突 · The export RT of the vRouter conflicts with an RT reserved for vRouter links：虚拟路由器配置的引出RT与系统预留的虚拟路由器连接的RT冲突 · The export RT of the vRouter conflicts with the RT of another vRouter：虚拟路由器配置的引出RT与其他虚拟路由器的RT冲突 · The import RT of the vRouter conflicts with an RT reserved for vRouter links：虚拟路由器配置的引入RT与系统预留的虚拟路由器连接的RT冲突 · The import RT of the vRouter conflicts with the RT of another vRouter：虚拟路由器配置的引入RT与其他虚拟路由器的RT冲突 · The import RT of the vRouter conflicts with the RT of a vNetwork：虚拟路由器配置的引入RT与虚拟链路层网络的RT冲突 · The import RT of the vRouter conflicts with an RT reserved for fabric interconnects：虚拟路由器配置的引入RT与系统预留的Fabric互联RT冲突 · The vRouter has been used on a transit VPC interconnect：虚拟路由器已被Transit VPC互通使用，不允许使用 · The segment ID of a transit vRouter cannot be edited：Transit类型虚拟路由器Segment ID不允许修改 · The external subnets of a vRouter cannot overlap with the networks manually specified for the vRouter link to which the vRouter belongs：外网子网网段不能与虚拟路由器所属的虚拟路由器连接的手动输入网段重叠 · You cannot bind the external network to the vRouter. This is because the external network has been bound to a remote vRouter connected to this vRouter, and either or both of the vRouters have been bound to a shared gateway：当该虚拟路由器和虚拟路由器连接对端的虚拟路由器中存在共享网关，且对端虚拟路由器已绑定外部网络时，不支持绑定该外部网络 · You cannot bind the vPort to the vRouter. This is because the vPort is in the external network bound to the remote vRouter connected to this vRouter, and either or both of the vRouters have been bound to a shared gateway：当该虚拟路由器和虚拟路由器连接对端的虚拟路由器中存在共享网关，且对端虚拟路由器已绑定外部网络时，不支持添加该外部网络所属的虚拟端口 · The value for the port_id fields in the external_gateway_info is invalid：external_gateway_info下的port_id字段取值无效 · The vPort specified by the port_id fields in the external_gateway_info must be the gateway-purpose vPort generated after the vRouter is bound to the external network：external_gateway_info下的port_id所属的的虚拟端口不是指定虚拟路由器绑定外部网络后内部生成的网关类型虚拟端口 · When host route recursion is enabled, the next hop IP address cannot reside on an external network：当迭代主机路由开关开启时，下一跳IP地址不能属于外网网段 · You cannot enable ND direct route redistribution for a vRouter in the network cloud scenario：网络云场景下，不允许开启引入ND直连路由开关 · You cannot edit the IPv4 subnets or egress IPv4 address of the external network, because the default external vPort has extended SNAT IP addresses：默认外网端口已配置扩展SNAT IP地址，IPv4外网子网和外网出口IPv4地址不允许修改 · Please make sure the firewall is enabled or disabled for both an external vPort and the vRouter bound to it：外网虚拟端口与所绑定的虚拟路由器过墙行为必须一致 · A vRouter and its attached external network must be bound to the same gateway：虚拟路由器的出口网关和外部网络的出口网关必须一致 · You cannot bind the external network to the vRouter, because the external network has been bound to a border gateway and the border gateway is not bound to the vRouter：不允许绑定配置了出口网关的外部网络，因为虚拟路由器未绑定出口网关 · You cannot edit the segment ID for a vRouter when you bind it to an external network or unbind it from an external network：虚拟路由器绑定或者解绑外网时，不允许同时修改Segmeng ID · The security external network feature is disabled. You cannot bind the vRouter to an external subnet with a VLAN-type segment, because the vRouter has been bound to a firewall configured with a security external network address pool：禁用安全外网时，该虚拟路由器已绑定的防火墙使用了安全外网，不能同时绑定Segment为VLAN类型的外网子网 · The security external network feature is disabled. You cannot bind the vRouter to an external network of the VLAN type, because the vRouter has been bound to a firewall configured with a security external network address pool：禁用安全外网时，该虚拟路由器已绑定的防火墙使用了安全外网，不能同时绑定VLAN类型的外部网络 · If multiple vRouters share an external vPort, directly add their external IP addresses to the IP list bound to the vPort when you expand their external IP addresses from single stack to dual stack：存在多个虚拟路由器共享外网IP时，请通过更改虚拟端口IP地址扩容其他协议类型的外网IP地址 · The internal or external subnets of the same vRouter cannot overlap：同一虚拟路由器内网或外网子网网段不能重叠 · The segment ID of an external transit vRouter is not editable：EXTERNALTRANSIT类型虚拟路由器不允许修改Segment ID · The internal subnets cannot overlap：多数据中心内网网段信息中存在子网网段重叠 · Invalid multi-DC internal subnet information：无效的多数据中心内网网段信息 · Invalid multi-DC external subnet information：无效的多数据中心外网网段信 · Internal subnets cannot overlap with any external subnet：多数据中心内网网段信息和多数据中心外网网段信息中存在子网网段重叠 · You must configure multi-DC internal subnets for an external transit vRouter if the vRouter is in a centralized vRouter link and uses firewall as the edge device to external networks：集中式虚拟路由器连接绑定EXTERNALTRANSIT类型虚拟路由器，且虚拟路由器外网出口设备为防火墙时，EXTERNALTRANSIT类型虚拟路由器的多数据中心内网网段信息不能为空 · The remote vRouter for a centralized-mode vRouter link cannot have a default subnet included in its external subnets if the following conditions exist: 1. The remote vRouter is an external transit vRouter. 2. A border gateway with gateway sharing disabled is already bound to the local vRouter：EXTERNALTRANSIT类型集中式虚拟路由器连接，本端虚拟路由器已绑定非共享出口网关，多数据中心外网网段信息不能包含默认网段 · If the remote end of a centralized-mode vRouter link is an external transit vRouter, the destination subnets in the route entries for the local vRouter cannot overlap with the external subnets specified for the remote vRouter：EXTERNALTRANSIT类型集中式虚拟路由器连接，本端虚拟路由器绑定的路由表项的目的网段与多数据中心外网网段信息不能重叠 · Local CIDRs cannot overlap with the external subnets specified for the remote vRouter：本端网段和对端路由器多数据中心外网网段信息不允许重叠 · Overlapping items are not allowed in the information configuration of the external network segment of the multi data center of different transitvrouter corresponding to the same tenant virtual router in the VPC：同一个虚拟路由器与不同的EXTERNALTRANSIT类型虚拟路由器建立集中式虚拟路由器连接，EXTERNALTRANSIT类型虚拟路由器间的多数据中心外网网段信息存在子网网段重叠 · The VPN instance name is invalid：无效的VPN实例名称 · Subnets in the external network do not have sufficient IP addresses for allocation：外部网络下的子网可分配IP不足 · Invalid inbound routing policy name：无效的入方向路由策略名称 · The external network has been bound to a vRouter that uses a different edge device placement mode than this vRouter. To bind to that network, first set the third-party firewall deployment mode to Off：边界设备对接第三方防火墙为开启状态（旁挂和直连）时，外部网络不能同时绑定外网出口设备为边界设备的虚拟路由器和外网出口设备为防火墙的虚拟路由器 · Invalid outbound routing policy name：无效的出方向路由策略名称 · The vPort-attached external network has been bound to MSDP peers. You cannot enable the firewall feature or use a firewall as the edge device to the external network：指定虚拟端口对应的外部网络已绑定MSDP对等体，不允许开启防火墙或不允许外网出口设备为防火墙 · In a non-network cloud scenario, you cannot bind both a BGP peer and a BGP neighbor to a vRouter if the peer IP address configured for the BGP neighbor is the same as the neighbor IP/network address configured for the BGP peer：非网络云场景，同一个虚拟路由器下，BGP邻居的对端对等体IP与BGP对等体IP地址/网段不能重叠 · You cannot bind the subnet to the vRouter, because the vRouter is on a vRouter link and the subnet overlaps with the remote subnets attached to the vRouter link：该子网网段与虚机路由器连接对端的子网网段存在地址重叠 · You cannot bind the external network to the vRouter, because the external network is enabled with route reduction and bound to another vRouter configured with the same internal subnet as this vRouter：外部网络已开启路由精简且绑定的虚拟路由器存在相同网段的内网子网时，虚拟路由器不允许绑定该外部网络 · You cannot bind the external network vPort to the vRouter, because the external network is enabled with route reduction and bound to another vRouter configured with the same internal subnet as this vRouter：外部网络已开启路由精简且绑定的虚拟路由器存在相同网段的内网子网时，虚拟路由器不允许绑定该外网虚拟端口 · You cannot bind the internal subnet to the vRouter, because the vRouter-associated external network is enabled with route reduction, and the internal subnet has been specified for another vRouter bound to this external network：虚拟路由器已绑定开启路由精简的外部网络时，虚拟路由器不允许绑定与该外部网络所属的其他虚拟路由器网段相同的内网子网 · When you add a vRouter that has the same vSubnet bindings and external network binding as an existing vRouter, you can disable SNAT for the bound external network on either vRouter, but not both of them：绑定了相同子网网段、相同外部网络的虚拟路由器，不允许均关闭外网SNAT开关 · An MDC north-south vRouter link (with islocalAll set to false and isPeerAll set to true) and an MDC east-west vRouter link (with both islocalAll and isPeerAll set to false) are created on the tenant. Make sure the routes to an external subnet of the south-north vRouter link and a remote CIDR of the east-west vRouter link do not overlap：当相同租户同时创建MDC南北向业务（指定源）和东西向业务（指定源和目的）时，南北向的多数据中心外网网段与东西向的对端网段明细路由不能相同 · If the firewall service type specified for a vRouter is service leaf, you cannot enable the multicast network feature for the vRouter：当虚拟路由器绑定Service Leaf类型防火墙时，不允许开启组播网络 · The vRouter is bound to a gateway whose firewall deployment mode is off and method to deploy basic external connectivity settings is manual. You cannot bind the vRouter to an external network that does not have gateway bindings or has vPort-vRouter bindings without a gateway specified：当虚拟路由器绑定设备组防火墙接入模式为关闭且外网转发基础配置为手动预配置的出口网关时，不可同时绑定未指定出口网关的外部网络，或者未指定出口网关的已被虚拟路由器外网虚拟端口绑定的外部网络 · The vRouter is bound to a gateway whose firewall deployment mode is off and method to deploy basic external connectivity settings is manual. You cannot bind the vRouter to a vPort associated with an external network that has no gateway binding：当虚拟路由器绑定设备组防火墙接入模式为关闭且外网转发基础配置为手动预配置的出口网关时，不支持绑定未指定出口网关的的外部网络中的虚拟端口 · When you bind a vRouter to an external network that has no vPort bindings, the external network's subnets cannot overlap with the access subnet for the firewall associated with the vRouter：虚拟路由器绑定未被虚拟路由器外网虚拟端口绑定的外部网络时，该外网下的子网不能和防火墙接入网段存在重叠 · When you bind an internal subnet to the vRouter, the subnet cannot overlap with the access subnet for the firewall associated with the vRouter：虚拟路由器绑定内网子网时，该内网子网不能和防火墙接入网段存在重叠 · When you bind a vRouter to a directly-connected external network, the external network's subnets cannot overlap with the access subnet for the firewall associated with the vRouter：虚拟路由器绑定独享外网时，该外网下的子网不能和防火墙接入网段存在重叠 · When you bind a vRouter to an external vPort, the subnets of the external network associated with the vPort cannot overlap with the access subnet for the firewall associated with the vRouter：虚拟路由器绑定外部网络中的虚拟端口时，该外网下的子网不能和防火墙接入网段存在重叠 · If the following conditions exist, you cannot bind a vRouter to any external network that has no gateway binding: ¡ The edge device to external networks for the vRouter is firewall. ¡ firewall service type specified for the vRouter is service leaf. 当虚拟路由器的外网出口设备为防火墙且绑定Service Leaf类型防火墙时，不支持绑定未指定出口网关的外部网络 · If the following conditions exist, you cannot bind a vRouter to any external network that has no segment ID: ¡ The edge device to external networks for the vRouter is firewall. ¡ The firewall service type specified for the vRouter is service leaf. 当虚拟路由器的外网出口设备为防火墙且绑定Service Leaf类型防火墙时，不支持绑定未指定External Segment ID的外部网络 · If the following conditions exist, you can only bind a vRouter to any external network that has no vPort bindings and has a gateway whose firewall deployment mode is off: ¡ The edge device to external networks for the vRouter is firewall. ¡ The firewall service type specified for the vRouter is service leaf. 当虚拟路由器的外网出口设备为防火墙且绑定Service Leaf类型防火墙时，仅支持绑定设备组防火墙接入模式为关闭的出口网关的未被虚拟路由器外网虚拟端口绑定的外部网络 · If the following conditions exist, you cannot bind a vRouter to any external network that has a gateway whose method to deploy basic external connectivity settings is auto: ¡ The edge device to external networks for the vRouter is firewall. ¡ The firewall service type specified for the vRouter is service leaf. 当虚拟路由器的外网出口设备为防火墙且绑定Service Leaf类型防火墙时，不支持绑定出口网关外网转发基础配置为自动下发的外部网络 · If the following conditions exist, you cannot bind a vRouter to any external network that has a gateway whose firewall deployment mode is off: ¡ The edge device to external networks for the vRouter is firewall. ¡ The firewall service type specified for the vRouter is not service leaf. 当虚拟路由器的外网出口设备为防火墙且绑定非Service Leaf类型防火墙时，不支持绑定出口网关设备组防火墙接入模式为关闭的外部网络 · If the following conditions exist, you cannot bind an external vPort to the vRouter: ¡ You have enabled firewall for the external vPort. ¡ The external network bound to the vPort has no segment ID. ¡ The firewall service type specified for the vRouter is service leaf. 虚拟路由器绑定Service Leaf类型防火墙时，不支持绑定未指定External Segment ID的外部网络中防火墙开关开启的虚拟端口 · If the following conditions exist, you cannot bind an external vPort to the vRouter: ¡ You have enabled firewall for the external vPort. ¡ The external network bound to the vPort has no gateway binding. ¡ The firewall service type specified for the vRouter is service leaf. 虚拟路由器绑定Service Leaf类型防火墙时，不支持绑定未指定出口网关的外部网络中防火墙开关开启的虚拟端口 · If the following conditions exist, you can bind an external vPort to the vRouter: ¡ You have enabled firewall for the external vPort. ¡ The external network bound to the vPort has a gateway whose firewall deployment mode is off. ¡ The firewall service type specified for the vRouter is service leaf. 虚拟路由器绑定Service Leaf类型防火墙时，仅支持绑定设备组防火墙接入模式为关闭出口网关的外部网络中防火墙开关开启的虚拟端口 · If the following conditions exist, you cannot bind an external vPort to the vRouter: ¡ You have enabled firewall for the external vPort. ¡ The external network bound to the vPort has a gateway whose method to deploy basic external connectivity settings is auto. ¡ The firewall service type specified for the vRouter is service leaf. 虚拟路由器绑定Service Leaf类型防火墙时，不支持绑定外网转发基础配置为自动下发的出口网关的外部网络中防火墙开关开启的虚拟端口 · If the following conditions exist, you cannot bind an external vPort to the vRouter: ¡ You have enabled firewall for the external vPort. ¡ The firewall service type specified for the vRouter is service leaf. ¡ The vRouter is bound to a centralized vRouter link that is not enabled with firewall or route reduction. 虚拟路由器绑定Service Leaf类型防火墙，且该虚拟路由器已绑定两端防火墙关闭且路由精简开关关闭的集中式虚拟路由器连接时，不支持绑定外部网络中防火墙开关开启的虚拟端口 · If the following conditions exist, you cannot bind an external vPort to the vRouter: ¡ You have enabled firewall for the external vPort. ¡ The external network bound to the vPort has a gateway whose firewall deployment mode is off. ¡ The firewall service type specified for the vRouter is not service leaf. 虚拟路由器绑定非Service Leaf类型防火墙时，不支持绑定设备组防火墙接入模式为关闭出口网关的外部网络中防火墙开关开启的虚拟端口 · If the following conditions exist, you cannot enable firewall for an external vPort bound to the vRouter: ¡ The firewall service type specified for the vRouter is service leaf. ¡ The external network bound to the vPort has no segment ID. 虚拟路由器绑定Service Leaf类型防火墙和未指定External Segment ID外部网络中的虚拟端口时，该虚拟端口的防火墙开关不允许从关闭到开启 · If the following conditions exist, you cannot enable firewall for an external vPort bound to the vRouter: ¡ The firewall service type specified for the vRouter is service leaf. ¡ The external network bound to the vPort has no gateway binding. 虚拟路由器绑定Service Leaf类型防火墙和未指定出口网关外部网络中的虚拟端口时，该虚拟端口的防火墙开关不允许从关闭到开启 · If the following conditions exist, you cannot enable firewall for an external vPort bound to the vRouter: ¡ The firewall service type specified for the vRouter is service leaf. ¡ The vPort's external network is bound to a gateway whose method to deploy basic external connectivity settings is auto 虚拟路由器绑定Service Leaf类型防火墙和指定外网转发基础配置为自动下发的出口网关的外部网络中的虚拟端口时，该虚拟端口的防火墙开关不允许从关闭到开启 · If the following conditions exist, you cannot enable firewall for an external vPort bound to the vRouter: ¡ The firewall service type specified for the vRouter is service leaf. ¡ The vPort's external network is bound to a gateway whose firewall deployment mode is not off. 虚拟路由器绑定Service Leaf类型防火墙和指定设备组防火墙接入模式为非关闭的出口网关的外部网络中的虚拟端口时，该虚拟端口的防火墙开关不允许从关闭到开启 · You cannot enable firewall service for the external vPorts bound to the vRouter. This is because the firewall service type specified for a vRouter is service leaf, the vRouter is one end of a centralized-mode vRouter link that has route reduction off and firewall service off at both ends：虚拟路由器绑定Service Leaf类型防火墙和两端防火墙关闭且路由精简开关关闭的集中式虚拟路由器连接时，不支持虚拟路由器绑定的外网虚拟端口防火墙开关从关闭切换为开启 · When you bind an external subnet to the vRouter, the subnet cannot overlap with the access subnet for the firewall associated with the vRouter：虚拟路由器绑定外网子网时，该外网子网与防火墙接入网段不能重叠 · Unsupported device type：该设备的设备类型不支持 · After you enable the IPv4 multicast network feature for the external network, you cannot select a gateway whose firewall deployment mode is off and method to deploy basic external connectivity settings is manual, and vice versa：外部网络不允许同时开启IPv4组播网络和绑定设备组防火墙接入模式为关闭且外网转发基础配置为手动预配置的出口网关 · After you enable the IPv6 multicast network feature for the external network, you cannot select a gateway whose firewall deployment mode is off and method to deploy basic external connectivity settings is manual, and vice versa：外部网络不允许同时开启IPv6组播网络和绑定设备组防火墙接入模式为关闭且外网转发基础配置为手动预配置的出口网关 · After you select a gateway whose firewall deployment mode is off and method to deploy basic external connectivity settings is manual, you cannot enable OSPF for the external network, and vice versa：外部网络不允许同时配置OSPF路由协议和绑定设备组防火墙接入模式为关闭且外网转发基础配置为手动预配置的出口网关 · After you bind to the external network a gateway whose firewall deployment mode is off and method to deploy basic external connectivity settings is manual, you cannot configure any NQA profile-subnet bindings, and vice versa：外部网络不允许同时配置子网绑定NQA策略和绑定设备组防火墙接入模式为关闭且外网转发基础配置为手动预配置的出口网关 · After you bind to the external network a gateway whose firewall deployment mode is off and method to deploy basic external connectivity settings is manual, you cannot enable primary IP allocation for any subnets, and vice versa：外部网络不允许同时开启子网主IP所在子网和绑定设备组防火墙接入模式为关闭且外网转发基础配置为手动预配置的出口网关 · After you select a gateway whose firewall deployment mode is off and method to deploy basic external connectivity settings is manual, you must configure a segment ID for the external network：当外部网络绑定设备组防火墙接入模式为关闭且外网转发基础配置为手动预配置的出口网关时，必须配置External Segment ID · When a vRouter has been bound to the external network, the external subnets cannot overlap with the subnet for firewall access：外部网络已被虚拟路由器绑定时，外网子网与防火墙接入网段重叠 · The external network is bound to a gateway whose firewall deployment mode is off and method to deploy basic external connectivity settings is manual. You must configure a segment ID：当外部网络绑定设备组防火墙接入模式为关闭且外网转发基础配置为手动预配置的出口网关时，External Segment ID不允许配置为空 · A vRouter that has border gateway bindings is bound to the external network. You cannot bind to the external network a gateway whose firewall deployment mode is off and method to deploy basic external connectivity settings is manual：外部网络已被虚拟路由器绑定且该虚拟路由器绑定了出口网关时，外部网络不允许绑定设备组防火墙接入模式为关闭且外网转发基础配置为手动预配置出口网关 · A vRouter that has a non-service leaf firewall binding is bound to the external network. You cannot bind a gateway whose firewall deployment mode is off to the external network：外部网络已被虚拟路由器绑定且该虚拟路由器绑定了非Service Leaf类型的防火墙时，不允许绑定设备组防火墙接入模式为关闭的出口网关 · You cannot disable firewall service for an external vPort bound to a vRouter when the following conditions exist: ¡ The vPort's external network is bound to a gateway that uses a device group with firewall deployment off and uses manual basic external connectivity deployment. ¡ The border gateway bound to the vRouter is different from that bound to the vPort's external network. 外网虚拟端口所属的外部网络的出口网关设备组防火墙接入模式为关闭且外网转发基础配置为手动预配置，虚拟路由器绑定的出口网关和该外部网络指定的出口网关不一致时，该虚拟端口的防火墙开关不允许从开启切换为关闭 · You cannot bind a flat-type external network to a vRouter that uses a service-leaf attached firewall as the edge device to the external network：当虚拟路由器的外网出口设备为防火墙且绑定Service Leaf类型防火墙时，不支持绑定FLAT类型的外部网络 · Auto basic external connectivity deployment is not available for the border gateway on an external network attached to a firewall-enabled vPort if the vPort is bound to a vRouter configured with a leaf-attached firewall：虚拟路由器绑定Service Leaf类型防火墙下，绑定防火墙开关为开启的虚拟端口时，虚拟端口所关联外部网络中指定的出口网关外网转发基础配置不支持自动下发模式 · When you bind an external network to a vRouter that uses a leaf-attached firewall as the edge device to the external network, the external network must meet the following requirements: 1. The network type is VLAN and the operating mode is indirectly connected. 2. The gateway to the external network uses manual basic external connectivity deployment and is bound to a device group with firewall deployment off. 3. The vRouter is not bound to any vPorts attached to the external network：当虚拟路由器的外网出口设备为防火墙且绑定Service Leaf类型防火墙时，绑定的外部网络必须满足：1）VLAN类型，2）共享模式，3)指定出口网关，该出口网关为手动预配置，且关联的设备组防火墙接入模式为关闭，4）未绑定此外部网络下的虚拟端口 · A VPN instance name cannot start with 'management_vpn'：VPN实例名称不能以"management_vpn"为前缀 · A VPN instance already exists with the specified name：VPN实例名称已被使用 · The external network egress IP is already bound to a vRouter. For vRouters to share this IP, make sure these vRouters use the same third-party firewall setting. You can configure this setting when you configure the device group associated with a gateway member of a border gateway bound to a vRouter：该外网出口IP已被其他虚拟路由器绑定，如需共享，需确保共享该IP的所有虚拟路由器绑定的出口网关对应的设备组第三方防火墙开关必须一致 · If multiple vRouters share an automatically created vPort, you cannot change the IP addresses of that vPort：当自动创建的外网虚拟端口被多个虚拟路由器绑定时，不允许修改其IP地址 · The vRouter has been associated with the source (or destination) EPG in an inter-vRouter EPG policy or inter-tenant EPG policy. Make sure the vRouter-associated subnets do not conflict with any members of the destination (source) EPG：若该虚拟路由器是跨虚拟路由器EPG间策略或跨租户EPG间策略中源（目的）EPG指定的虚拟路由器，则其绑定的子网与目的（源）EPG成员不能存在冲突 · Transit vRouters do not support configuring the tags field：TRANSIT类型虚拟路由器不支持配置tags字段 · When you configure the tags field for a normal or external transit vRouter, do not specify any tenant-exclusive border gateway：NORMAL或者EXTERNALTRANSIT类型虚拟路由器的tags字段中不能包含租户独占的出口网关 · If the following conditions exist, you cannot configure the tags field for an external transit vRouter: 1. The external transit vRouter has established a vRouter link to a transit vRouter. 2. A gateway member of the border gateway bound to the external transit vRouter belongs to the same device group as that of a border gateway bound to the transit vRouter：EXTERNALTRANSIT和TRANSIT类型虚拟路由器已创建虚拟路由器连接，两者绑定的出口网关的出口网关成员关联了同一个设备组，EXTERNALTRANSIT类型虚拟路由器不允许配置tags字段 · You must specify import RTs for a transit vRouter：虚拟路由器是TRANSIT类型时，必须指定引入RT · You must specify export RTs for a transit vRouter：虚拟路由器是TRANSIT类型时，必须指定引出RT · You must specify import RTs for an external transit vRouter：虚拟路由器是EXTERNALTRANSIT类型时，必须指定引入RT · You must specify export RTs for an external transit vRouter：虚拟路由器是EXTERNALTRANSIT类型时，必须指定引出RT · Make sure the import RTs and export RTs are consistent on a vRouter：虚拟路由器配置的引入RT与引出RT不一致 · The vRouter has been specified in an inter-vRouter EPG policy or inter-tenant EPG policy. Make sure the source (or destination) EPG members do not conflict with any subnets or members of the vRouter associated with the destination (source) EPG：指定的虚拟路由器已创建跨虚拟路由器EPG间策略或跨租户EPG间策略，源（目的）EPG成员与目的（源）EPG所属虚拟路由器下的子网和EPG成员不能存在重复 · Invalid BGP peer authentication mode：无效的BGP对等体认证模式 · Password configuration is not supported if the BGP peer authentication mode is not Password Authentication：未指定BGP对等体认证模式为密码认证时不允许配置密码 · Password configuration is required if the BGP peer authentication mode is Password Authentication：指定BGP对等体认证模式为密码认证时不允许密码为空 · The password is case sensitive and cannot exceed 80 characters. Only letters, digits, and special characters except for question marks (?) are supported：密码长度最长80个字符，区分大小写，仅支持英文、数字和特殊字符（英文问号除外） · Cannot allocate this segment ID, because synchronization is in progress for the VXLAN pool containing this segment ID：无法分配该Segment ID，其所在的VXLAN池正在平滑中 · Cannot allocate segment IDs automatically, because no VXLAN pool is configured：未配置VXLAN池，无法自动分配Segment ID · Cannot allocate segment IDs automatically, because the VXLAN pool does not have available resources：VXLAN池中资源已耗尽，无法自动分配Segment ID · Cannot allocate segment IDs automatically. Please verify correctness of the VXLAN pool configuration and status：无法自动分配Segment ID，请检查VXLAN池配置及状态 · Resource application or rollback failed, internal unknown error：资源申请或回滚失败，内部未知错误 · The（resource）does not exist or the resources are insufficient：（资源）不存在或资源不足 · The（resource）does not exist or the resources are insufficient, device group name（name）：（资源）不存在或资源不足，设备组名称（名称） · The （resource） does not exist or the resources are insufficient, resource access template name （name）：（资源）不存在或资源不足，资源接入模板名称（名称） · You cannot unbind the external subnet, because it has been specified in an EPG or context：被EPG或流量特征组使用的外网子网不允许解绑 · In the IPv6 scenario, a vRouter cannot have the same subnet bindings or external network binding as another vRouter：IPv6场景下，不允许存在绑定相同子网网段、相同外部网络的虚拟路由器 · The source IP address cannot be the IP address that the device uses as the interconnect address in an M-LAG routed peer link：源IP地址不能与M-LAG互联链路中相同设备的本端或对端互联地址相同 · You cannot remove the external network, because it is used by multicast sources：指定的外部网络已被组播源使用，不允许解绑 |
|
关键字 |
DELETE_ROUTE_OP |
|
日志内容 |
Deleted vRouter “$1”. |
|
参数解释 |
$1：虚拟路由器的名称 |
|
举例 |
Deleted vRouter ”router01”. |
|
日志说明 |
用户进行了删除路由器的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The specified resource doesn't exist：指定的资源不存在 · Failed to delete the router, because it has a bound subnet：此路由器存在绑定的子网 · Failed to delete the vRouter because it has been bound to service resources：路由器已被服务资源绑定，无法删除 · Failed to delete the vRouter because it has been bound to a vRouter link：该虚拟路由器已绑定虚拟路由器连接，不允许删除 · Failed to delete the vRouter because the vRouter has routing tables：该虚拟路由器下存在路由表，不允许删除 · Failed to delete the vRouter because a routing table has been bound to the vRouter：虚拟路由器已绑定路由表，不允许删除 · The vRouter has been bound to a vRouter interconnection：该虚拟路由器已被虚拟路由器连接绑定 · The vRouter has been bound to a Layer 3 DC interconnection：该虚拟路由器已被数据中心三层互联绑定 · Failed to delete the vRouter because it has been bound to route entries：该虚拟路由器已被路由表项绑定，不允许删除 · Unknown error：未知错误 · Failed to delete the vRouter because the vRouter has BGP peers：删除虚拟路由器失败，指定的虚拟路由器正在被BGP邻居使用 · You have no privilege to perform this operation：用户无权限执行此操作 · You cannot delete the vRouter, because it has been bound to a EPG：该虚拟路由器已被EPG绑定，不允许删除 · You cannot delete the vRouter, because it has been bound to a context：该虚拟路由器已被流量特征组绑定，不允许删除 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · You cannot delete the vRouter, because it has been bound to an application policy：该虚拟路由器已被应用策略绑定，不允许删除 · The vRouter cannot be deleted because it has been bound to network ACL：指定的虚拟路由器已被网络ACL绑定，不允许删除 · Resource application or rollback failed, internal unknown error：资源申请或回滚失败，内部未知错误 · The（resource）does not exist or the resources are insufficient：（资源）不存在或资源不足 · The（resource）does not exist or the resources are insufficient, device group name（name）：（资源）不存在或资源不足，设备组名称（名称） · The （resource） does not exist or the resources are insufficient, resource access template name （name）：（资源）不存在或资源不足，资源接入模板名称（名称） |
|
关键字 |
CREATE_INTERNAL_ROUTE_OP |
|
日志内容 |
Created internal route to router “$1”, “dest: $2, next hop: $3”. |
|
参数解释 |
$1：虚拟路由器的名称 $2：内网路由的目的网段 $3：内网路由的下一跳 |
|
举例 |
Created internal route to router "vRouter1", “dest: 100.1.1.1/24, next hop: 100.1.1.1”. |
|
日志说明 |
用户进行了创建内网路由的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The next hop is required：未指定下一跳 · The specified resource doesn't exist：指定的资源不存在 · Invalid IP address：无效的IP地址 · Invalid CIDR：无效的CIDR · The request is invalid：传入的JSON串错误 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_INTERNAL_ROUTE_OP |
|
日志内容 |
Deleted internal route from router $1, “dest: $2, next hop: $3”. |
|
参数解释 |
$1：虚拟路由器的名称 $2：内网路由的目的网段 $3：内网路由的下一跳 |
|
举例 |
Deleted internal route from router "vrouter1", “dest: 100.1.1.1/24, next hop: 100.1.1.1”. |
|
日志说明 |
用户进行了删除静态路由的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The specified resource doesn't exist：指定的资源不存在 · The subnet has been bound to a vRouter interconnection：该子网已被虚拟路由器连接绑定 · The subnet has been bound to a Layer 3 DC interconnection：该子网已被数据中心三层互联绑定 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_INTERFACE_OP |
|
日志内容 |
Created interface "$1" to vRouter "$2". |
|
参数解释 |
$1：虚拟路由器绑定的子网的名称或者与虚拟路由器绑定的外网虚拟端口的名称 $2：虚拟路由器的名称 |
|
举例 |
Created interface "subnet3" to vRouter "vrouter1". |
|
日志说明 |
用户进行了子网或外网虚拟端口与虚拟路由器的绑定操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The subnet has already been bound to another router：虚拟子网已经绑定了其它的虚拟路由器 · The subnet and the router are not in the same VDS：子网和虚拟路由器不在同一个VDS · The specified subnet doesn’t exist：指定的虚拟子网不存在 · The specified resource doesn't exist：指定的资源不存在 · The subnet overlaps with another subnet：子网与其它的子网重叠 · The subnet ID was null：子网ID为空 · The subnet and the vRouter are not in the same tenant：子网和路由器必须属于同一租户 · The subnet has already been bound to the vRouter：子网已关联虚拟路由器 · The subnet of the vRouter overlaps with the subnet of the other vRouter of the vRouter link：子网与虚拟路由器连接中的其他虚拟路由器下的子网重叠The subnet overlaps with a selected subnet of the other vRouter in a vRouter interconnection：该子网与虚拟路由器连接绑定的另一个虚拟路由器的已选子网重叠 · The subnet overlaps with a remote subnet in a Layer 3 DC interconnection that involves the vRouter：该子网与数据中心三层互联远端网段重叠 · The vPort already exists：虚拟端口已存在 · The port ID is different than the gateway port ID：端口ID与网关端口ID不一致 · The selected subnet cannot overlap with the network that contains the ingress or egress vPort in the vRouter's service chain：虚拟路由器下存在服务链业务，且已选子网与服务链中服务资源的入/出虚拟端口网段重叠 · Unknown error：未知错误 · The source IP address of a route entry with a vPort-type next hop on the vRouter cannot overlap with any vNetwork subnet on another vRouter：建立虚拟路由器连接的两个虚拟路由器，一个虚拟路由器下虚拟端口类型的路由表项的源IP不允许和另一个虚拟路由器下虚拟链路层网络的子网重叠 · The source IP address of a route entry with a vPort-type next hop on the vRouter cannot overlap with any external subnet on another vRouter：建立虚拟路由器连接的两个虚拟路由器，一个虚拟路由器下虚拟端口类型的路由表项的源IP不允许和另一个虚拟路由器下外部网络的子网重叠 · The source IP address of a route entry with a vPort-type next hop on the vRouter cannot be the same as any vNetwork subnet gateway IP of another vRouter：建立虚拟路由器连接的两个虚拟路由器，一个虚拟路由器下虚拟端口类型的路由表项的源IP不允许和另一个虚拟路由器下虚拟链路层网络子网的网关IP地址相同 · The source IP address of a route entry on the vRouter cannot be the same as any vNetwork subnet gateway IP on the vRouter：源IP地址不允许和同一虚拟路由器下虚拟链路层子网的网关IP地址相同 · The source IP address of a route entry on the vRouter cannot be within any vNetwork subnet on the vRouter：源IP地址不允许在同一虚拟路由器下虚拟链路层子网网段范围内 · The source IP address of a route entry on the vRouter cannot be within any external subnet on the vRouter：源IP地址不允许在同一虚拟路由器下外部网络的子网网段范围内 · Subnets in the same vNetwork must be bound to the same vRouter：同一虚拟链路层网络下的子网必须绑定同一虚拟路由器 · The indirectly connected external network can't be directly deleted from or added to the router：共享型外网子网不能直接从关联路由器中添加和删除 · Subnets in the same external network must be bound to the same vRouter：同一外部网络下的的子网必须绑定同一虚拟路由器 · You have no privilege to perform this operation：用户无权限执行此操作 · You cannot bind a vRouter to a vPort created by using a subnet for primary IP allocation：虚拟路由器不支持绑定使用主IP所在子网创建的虚拟端口 · The IPv4 subnet has been bound to a context, or it overlaps with the subnet attached to a service instance's ingress/egress vPort in a service chain. It cannot be assignedto the vRouter already specified in an IPv4 or IPv4 & IPv6 application policy：当IPv4子网已被服务链流量特征组绑定或子网网段与服务链中服务实例的出入虚拟端口网段相等时，其绑定的虚拟路由器与IPv4或IPv4 & IPv6的应用策略的虚拟路由器必须不同 · The IPv4 subnet overlaps with the subnet attached to the ingress or egress vPort for a service instance of a service path specified in an application policy. It cannot be assigned to this vRouter, which has been bound to a service chain：当IPv4子网网段与已被引用的服务路径中服务实例的出入虚拟端口网段相等时，其绑定的虚拟路由器与服务链的虚拟路由器必须不同 · Failed to assign the IPv4 subnet to the vRouter, because the vRouter has been bound to both a router context in a service chain and an IPv4 or IPv4 & IPv6 application policy：IPv4子网绑定虚拟路由器失败，因为目标虚拟路由器被服务链引用的Router类型流量特征组和IPv4或IPv4 & IPv6的应用策略同时绑定 · Failed to add some of the vSubnets. Please make sure the selected vSubnets are not used in the service chain associated with the vRouter：绑定子网失败，指定子网与该虚拟路由器绑定的服务链下的子网重叠 · Failed to bind the subnet to the vRouter, because it overlaps with a network bound to the context in another service chain：虚拟路由器绑定子网失败，该绑定会导致虚拟路由器所在特征组的服务链与其他服务链网段重叠 · The vRouter-attached gateway members enable the third-party firewall option. Please enable or disable the firewall option across all IP addresses or subnets in the vRouter-attached external network if the egress of the external network is the firewall or border device, respectively：虚拟路由器绑定了第三方防火墙开启的设备组，该虚拟路由器绑定外部网络下的外网子网防火墙设置需要和虚拟路由器上的外网出口设置一致 · The vRouter-attached gateway members disable the third-party firewall option and use hairpin firewall deployment. Please make sure the firewall is enabled or disabled across all IP addresses and subnets in the external network：虚拟路由器绑定了第三方防火墙关闭且防火墙接入模式是旁挂的设备组，同外部网络下的外网子网过墙行为必须一致 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · You cannot bind the IPv6 subnet to the vRouter, because the vRouter belongs to a vRouter link and has been bound to a centralized vNetwork：当虚拟路由器存在虚拟路由器连接时，不能同时绑定IPv6子网和集中式虚拟链路层网络 · Failed to bind the subnet to the vRouter, because the vRouter has been used by a service chain and bound to an external EPG containing external network CIDR 0.0.0.0/0：子网绑定虚拟路由器失败，该虚拟路由器已被服务链和External类型且外网网段包含0.0.0.0/0的EPG绑定 · A Layer 3 multicast network has been added to the external network, and the external network cannot be bound to a vRouter through a vPort：外部网络已有L3组播，不允许使用虚拟端口方式绑定vRouter · Operation failed. The vNetwork of the subnet has been an EPG member, and the subnet has been used by the private network CIDR：子网绑定虚拟路由器失败。指定子网所在的虚拟链路层网络已是EPG成员，该子网网段已被EPG的私有网段使用 · Make sure the extended SNAT IP addresses have not been used in the external network：相同外部网络下，扩展SNAT IP地址不能与已经存在的扩展SNAT IP地址或虚拟端口IP地址冲突 · You cannot specify an extended SNAT IP address as a floating IP address in the same external network：扩展SNAT IP地址不能与浮动IP冲突 · You cannot specify an extended SNAT IP address as a gateway IP address in the same external network：扩展SNAT IP地址不能与子网网关IP地址冲突 · If the edge device to external networks for an external transit vRouter is firewall, you cannot bind the vRouter to any directly-connected external network：EXTERNALTRANSIT类型虚拟路由器，外网出口设备为防火墙时，不允许绑定独享外网 · If the edge device to external networks for an external transit vRouter is border device, you cannot bind any vPorts to the vRouter：EXTERNALTRANSIT类型虚拟路由器，外网出口设备为边界设备时，不允许绑定外部网络中的虚拟端口 · You cannot bind an external transit vRouter to any external network that has subnets enabled with the primary IP allocation feature：EXTERNALTRANSIT类型虚拟路由器不允许绑定存在主IP子网的外网 · You cannot bind an external transit vRouter to any external network enabled with the IPv4 multicast network feature：EXTERNALTRANSIT类型虚拟路由器不允许绑定开启了IPv4组播网络开关的外网 · The vRouters bound to an external network must be of the same type：外网不允许被不同类型虚拟路由器绑定 · You cannot bind the external transit vRouter to any external network referenced by OSPF：EXTERNALTRANSIT类型虚拟路由器不支持绑定被OSPF引用的外网 · You can bind a manually created external vPort to a vRouter only when its port type is none or gateway：虚拟路由器仅支持绑定手工创建的none类型或gateway类型的外网虚拟端口 · Invalid external IP binding. An external IP address has been bound to a minimum of one vRouter. To share that external IP address, the vRouters must be bound to the gateway resources that use the same border device group：该外网出口IP已被其他虚拟路由器绑定，如需共享，需确保共享该IP的所有虚拟路由器绑定的网关资源的边界设备组相同 · Invalid external IP binding. An external IP address has been bound to a minimum of one vRouter. To share that external IP address, the vRouters must be bound to the gateway resources that use the same type of border device group：该外网出口IP已被其他虚拟路由器绑定，如需共享，需确保共享该IP的所有虚拟路由器绑定的网关资源的边界设备组类型相同 · Invalid external IP binding. An external IP address has been bound to a minimum of one vRouter. To share that external IP address, the vRouters must be assigned the same service resources：该外网出口IP已被其他虚拟路由器绑定，如需共享，需确保共享该IP的所有虚拟路由器绑定相同的服务资源 · Failed to bind the resource. The VLAN pool does not exist or no VLAN IDs are available in the VLAN pool：绑定资源失败，指定的租户承载网类型的VLAN池不存在，或该VLAN池内没有足够的VLAN ID · The address pool does not exist or no IPv4 or IPv6 addresses are available in the address pool：绑定资源失败，指定的地址池不存在，或该地址池内没有可用的IPv4/IPv6地址 · You cannot bind an external transit vRouter to any external network enabled with the IPv6 multicast network feature：EXTERNALTRANSIT类型虚拟路由器不允许绑定开启了IPv6组播网络开关的外网 · The vRouter is bound to a gateway that uses the manual method to deploy basic external connectivity settings and that is enabled with external route reduction. It cannot be bound to any internal subnet addresses of other vRouters bound to the gateway：虚拟路由器已绑定外网转发基础配置为手动预配置且外网路由精简开启的出口网关时，虚拟路由器不允许绑定与该出口网关绑定的其他虚拟路由器网段相同的内网子网 · You cannot bind a vRouter to any vPort that belongs to an external network enabled with network segmentation：虚拟路由器不支持绑定开启网络分段功能的外网虚拟端口 |
|
关键字 |
DELETE_INTERFACE_OP |
|
日志内容 |
Deleted interface "$1" from vRouter "$2". |
|
参数解释 |
$1：虚拟路由器绑定的子网的名称或者与虚拟路由器绑定的外网虚拟端口的名称 $2：虚拟路由器的名称 |
|
举例 |
Deleted interface "subnet1" from vRouter "vrouter1". |
|
日志说明 |
用户删除了子网或外网虚拟端口与虚拟路由器的绑定关系 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The subnet can’t be directly deleted from or added to the router：外网子网不能直接从关联路由器中添加和删除 · The specified subnet doesn’t exist：指定的虚拟子网不存在 · The subnet has already been unbound from router：该子网已经从虚拟路由器中移除 · The subnet ID is required：未指定子网ID · Failed to delete the interface from the vRouter, because the vPort or APP cluster VIP in the subnet has a floating IP：从vRouter解绑定接口失败，子网下存在绑定浮动IP的端口或应用集群虚IP · The specified resource doesn't exist：指定的资源不存在 · The subnet has been bound to a routing table：该子网已绑定路由表 · The vPort has been bound to a routing table：该虚拟端口已绑定路由表 · The subnet overlaps with the destination subnet of the route entry：子网网段与路由表项的目的网段重叠 · Unknown error：未知错误 · The indirectly connected external network can't be directly deleted from or added to the router：共享型外网子网不能直接从关联路由器中添加和删除 · Failed to remove the subnet from the vRouter because the vRouter has BGP peers on this subnet：删除子网失败，指定的子网正在被BGP邻居使用 · You have no privilege to perform this operation：用户无权限执行此操作 · The vRouter has not been bound to the port：虚拟路由器未绑定该端口 · The vNetwork is an interface-specific multicast network. You cannot unbind its only subnet from the vRouter：指定的虚拟链路层网络已经绑定组播接口，该虚拟链路层网络下的最后一个子网不允许解绑虚拟路由器 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · You cannot delete the subnet, because it has been specified for the ingress or egress vPort of a third-party service device bound to a service path：指定子网已被第三方服务设备的出入虚拟端口使用，且该第三方服务设备已被服务路径使用，不允许解绑 |
|
关键字 |
CREATE_NETWORK_OP |
|
日志内容 |
Created network "$1". |
|
参数解释 |
$1：虚拟链路层网络的名称 |
|
举例 |
Created network "network01". |
|
日志说明 |
用户进行了创建虚拟链路层网络的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · Invalid tenant ID：无效的租户ID · The segment ID number is already used：Segment ID number已经被使用 · The segment ID is out of range：Segment ID超出范围 · The network's parameter is incorrect：虚拟网络参数错误 · The virtual network already exists：虚拟网络已存在 · Networks created in bulk cannot use the same ID：批量创建的虚拟路由器连接的ID存在重复 · The router doesn't exist：虚拟路由器不存在 · The router and network doesn't belong to the same tenant：虚拟链路层网络与虚拟路由器不属于同一个租户 · Failed to create the VXLAN because no available overlay license exists：Overlay license不可用，不能创建VXLAN类型的虚拟链路层网络 · Invalid broadcast suppression configuration：无效的广播报文抑制配置 · Invalid unknown multicast suppression configuration：无效的未知组播报文抑制配置 · Invalid unknown unicast suppression configuration：无效的未知单播报文抑制配置 · Unknown network type：未知的虚拟链路层网络类型 · The type of the network is different than the other networks in the tenant：同一个租户内只能创建一种类型的网络 · The ARP packet sending rate exceeds the rate limit：ARP报文发送速率超过速度限制 · The VDS doesn't exist：VDS不存在 · The number of DHCP servers on the DHCP relay agent can't exceed 8：DHCP服务器的IP地址数不能超过8个 · The IP address of the DHCP server is invalid：无效的DHCP服务器IP地址 · The IP address of the DHCP server is required：未指定DHCP服务器的IP地址 · External networks and VLANs do not support network sharing：外部网络或VLAN类型的网络不支持开启共享功能 · No available segment ID：没有可用的Segment ID · The network name cannot exceed 255 characters：虚拟链路层网络名称最长255个字符 · The specified tenant doesn't exist：指定的租户不存在 · Only external networks can be configured as flat networks：仅外部网络支持配置为Flat类型 · When the external network is a VXLAN, the value of the force_flat field cannot be false：当外部网络的类型为VXLAN时，force_flat不能为false · The segment ID of a flat network must be null：Flat类型网络的Segment ID必须为空 · The value of the force_flat field can be configured as true only when the network is an external network：仅外部网络支持配置force_flat为true · The value of the router:external field is required：router:external不能为空 · The value of the shared field is required：shared不能为空 · The value of the admin_state_up field is required：admin_state_up不能为空 · The value of the distributed field is required：distributed不能为空 · The value of the vswitch_flood_and_learn field is invalid：无效的vswitch_flood_and_learn · The specified tenant doesn't bind VDS：指定的租户没有绑定VDS · The VDS of the network is different than the tenant：虚拟链路层网络与租户的VDS不一致 · The provider field and the segment field cannot be both configured：provider字段和segments字段不能同时配置 · The flat type external network cannot be configured with segment：FLAT类型的外部网络不支持配置Segment · The ID already exists：ID已存在 · The value of the network type can only be VLAN：仅支持VLAN类型外网 · The network type is required：网络类型不能为空 · The segment ID is not in the VLAN pool：Segment ID不在VLAN池范围内 · physical network is required：physical_network字段不能为空 · The specified border gateway doesn't exist：指定的出口网关不存在 · You can create segments only for external networks：仅外部网络支持创建网络分段 · The segment name cannot exceed 255 characters：Segment名称最长255个字符 · The description cannot exceed 255 characters：描述信息最长255个字符 · Invalid segmentUUID：无效的 segmentUUID · The external network has been bound to a vRouter：外部网络已被虚拟路由器绑定 · Invalid segment ID：无效的segment ID · The value of the MTU must be an integer in the range of 68 to 65535：MTU必须为68～65535的整数 · The specified vPort QoS policy doesn't exist：指定的虚拟端口QoS策略不存在 · Unknown error：未知错误 · Invalid value in the physical_network field：无效的physical_network字段 · A vNetwork cannot use directly connected mode：虚拟链路层网络不支持独享模式 · When the Network Cloud feature is disabled, directly connected external networks are not supported：网络云开关关闭时，不支持配置独享模式的外部网络 · Only internal network can be configured as resource operating mode：仅内部网络可配置为Resource工作模式 · You have no privilege to perform this operation：用户无权限执行此操作 · Cannot bind the DHCP host group to an external network：外部网络不支持绑定DHCP主机组 · The DHCP host group does not exist：指定的DHCP主机组不存在 · The RT generated based on the segment ID of the vNetwork conflicts with the import RT of a Layer 2 DC interconnect：虚拟链路层网络Segment ID生成的RT与数据中心二层互联的引入RT冲突 · The RT generated based on the segment ID of the vNetwork conflicts with the export RT of a Layer 2 DC interconnect：虚拟链路层网络Segment ID生成的RT与数据中心二层互联的引出RT冲突 · The RT generated based on the segment ID of the vNetwork conflicts with the import RT of a Layer 3 DC interconnect：虚拟链路层网络Segment ID生成的RT与数据中心三层互联的引入RT冲突 · The RT generated based on the segment ID of the vNetwork conflicts with the export RT of a Layer 3 DC interconnect：虚拟链路层网络Segment ID生成的RT与数据中心三层互联的引出RT冲突 · Invalid auto port creation configuration：无效的自动创建虚拟端口配置 · You cannot bind the DHCP host group to the vNetwork. A network node in the DHCP host group has already created a DHCP vPort for the vNetwork：DHCP主机组中的网络节点已存在虚拟链路层网络的DHCP虚拟端口，不允许绑定 · To disable preprovisioning, make sure all its dependent features use their default settings. For information about these features, see online help：当以下开关全部取值为默认时，预配置开关才允许关闭。ARP泛洪、ARP上送控制组件、RARP泛洪、RARP上送控制组件、DHCP上送控制组件、IPv6 NS/NA上送控制组件、IPv6 NS/NA泛洪、IPv6 RS/RA上送控制组件和DHCPv6上送控制组件 · Make sure the segment ID (VLAN ID) is not in a tenant carrier network VLAN pool and vRouter interconnection network VLAN pool when the external network or vNetwork type is VLAN：VLAN类型网络的VLAN ID不允许在租户承载网类型和虚拟路由器互通网络类型的VLAN池范围内 · You cannot change the status of the multicast network feature when the network segmentation feature is enabled：当外部网络开启网络分段开关时，不允许切换组播网络开关 · The external segment ID is already in use：External Segment ID 已经被使用 · The external segment ID is out of range：External Segment ID超出范围 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · You can enable external route redistribution only for external networks：仅外部网络支持配置引入外网路由开关 · You can enable external route redistribution only when the L3VNI is specified：仅L3VNI不为空时支持开启引入外网路由开关 · The segment ID cannot be identical to a VXLAN ID in a VXLAN pool or the VXLAN ID reserved for the automation template and the M-LAG system：Segment ID不能在VXLAN池范围内且不能和自动化模版、M-LAG系统的保留VXLAN ID重叠 · VLAN ID of VLAN type network is not allowed to conflict with M-LAG routed peer links border device VLAN ID：VLAN类型网络的VLAN ID不允许与M-LAG互联链路border设备互联VLAN冲突 · The gateway MAC cannot be a reserved MAC or device group MAC：网关MAC地址与系统保留MAC地址或设备组的MAC地址冲突 · The value for MAC address learning is invalid：无效的MAC地址学习开关 · The gateway MAC is invalid：无效的网关MAC地址 · Invalid transparent mode configuration：无效的透传模式配置 · You cannot enable LLDP-based vPort onboarding for the vNetwork, because automatic vPort creation has been enabled for the vNetwork：当前虚拟链路层网络已开启自动创建虚拟端口，不允许开启LLDP上线虚拟端口开关 · Invalid LLDP-based vPort onboarding configuration：无效的LLDP上线虚拟端口配置 · You cannot enable both LLDP-based vPort onboarding and automatic vPort creation for the vNetwork：虚拟链路层网络的LLDP上线虚拟端口和自动创建虚拟端口开关不能同时开启 · You cannot enable the IPv4 multicast network feature for a directly connected external network：独享型外部网络不支持开启IPv4组播网络开关 · You cannot enable network segmentation to a directly connected external network：外部网络的工作模式为独享时，不支持开启网络分段功能 · You cannot configure external segment ID to a directly connected external network：外部网络的工作模式为独享时，不支持配置External Segment ID · In a non-network cloud scenario, you cannot specify a borderinterface for the device group bound to a shared external network：非网络云场景，共享型外部网络不允许指定设备组的外网出口 · The value for the arp_mac_learning parameter is invalid：ARP MAC地址学习参数取值无效 · The value for the nd_mac_learning parameter is invalid：IPv6 ND MAC地址学习参数取值无效 · The RT generated based on the segment ID of the vNetwork conflicts with the import RT on a vRouter：虚拟链路层网络Segment ID生成的RT与虚拟路由器配置的引入RT冲突 · The RT generated based on the segment ID of the vNetwork conflicts with the export RT on a vRouter：虚拟链路层网络Segment ID生成的RT与虚拟路由器配置的引出RT冲突 · The RT generated based on the external segment ID of the external network conflicts with the import RT on a vRouter：外部网络External Segment ID生成的RT与虚拟路由器配置的引入RT冲突 · The RT generated based on the external segment ID of the external network conflicts with the export RT on a vRouter：外部网络External Segment ID生成的RT与虚拟路由器配置的引出RT冲突 · You cannot enable both route reduction and directly connected mode：路由精简开关与独享型工作模式不允许同时开启 · You cannot enable both route reduction and redistribution of external routes：路由精简开关与引入外网路由开关不允许同时开启 · In the network cloud scenario, you cannot enable route reduction for the external network：网络云场景下，不允许开启外部网络路由精简开关 · When network segmentation is enabled, you cannot enable route reduction for the external network：外部网络开启网络分段时，不允许开启外部网络路由精简开关 · Route reduction can be enabled only when the external network type is VLAN：仅VLAN类型外部网络允许开启路由精简开关 · When route reduction is enabled, you cannot enable network segmentation for the external network：外部网络开启路由精简开关时，不允许开启网络分段 · You cannot specify an external segment ID for a flat external network or vNetwork：Flat类型外部网络或者虚拟链路层网络的External Segment ID必须为空 · The RT generated based on the external segment ID of the external network is identical to the import RT of a Layer 2 DC interconnect：外部网络External Segment ID生成的RT与数据中心二层互联的引入RT冲突 · The RT generated based on the external segment ID of the external network is identical to the export RT of a Layer 2 DC interconnect：外部网络External Segment ID生成的RT与数据中心二层互联的引出RT冲突 · The RT generated based on the external segment ID of the external network is identical to the import RT of a Layer 3 DC interconnect：外部网络External Segment ID生成的RT与数据中心三层互联的引入RT冲突 · The RT generated based on the external segment ID of the external network is identical to the export RT of a Layer 3 DC interconnect：外部网络External Segment ID生成的RT与数据中心三层互联的引出RT冲突 · A vRouter and its attached external network must be bound to the same gateway：虚拟路由器的出口网关和外部网络的出口网关必须一致 · You cannot bind a gateway to a flat external network：FLAT类型外部网络不支持绑定出口网关 · You can bind only one gateway to an external network：外部网络只支持绑定一个出口网关 · The external network has been attached to a vRouter that has multiple gateways. You cannot specify a gateway for the external network：当虚拟路由器已绑定多个出口网关时，已绑定的外部网络不支持绑定出口网关 · You cannot both enable network segmentation and specify a gateway for an external network：外部网络的网络分段和出口网关冲突 · You cannot bind a border gateway to a directly connected external network：独享型外部网络不支持绑定出口网关 · In the network cloud scenario, you cannot bind a gateway to an external network：网络云场景下，外部网络不支持绑定出口网关 · You cannot bind the border gateway to the external network, because the external network has been bound to a vRouter and the border gateway is not bound to the vRouter：不允许外部网络配置出口网关，因为外部网络所绑定的虚拟路由器没绑定该出口网关 · When the type of an external network is FLAT, the operating mode of the external network cannot be Directly Connected：FLAT类型外部网络不支持配置独享型的工作模式 · The max rate of broadcasts must be an integer in the range of 64 to 167772159：广播报文最大速率范围必须为64～167772159的整数 · The primary_network_id field is a read-only field：primary_network_id为只读字段 · Cannot set the max rate of unknown unicasts when the value for the Unknown Unicast Suppression field is On or Default：未知单播报文泛洪抑制开关为开启或默认状态时，不允许配置未知单播报文最大速率 · The max rate of unknown unicasts must be an integer in the range of 64 to 167772159：未知单播报文最大速率范围必须为64～167772159的整数 · The segment ID cannot be identical to the VLAN ID configured for the M-LAG routed peer links between two border devices：Segment ID不能与边界设备的M-LAG互联链路下的VLAN ID冲突 · The max rate of unknown multicasts must be an integer in the range of 64 to 167772159：未知组播报文最大速率范围必须为64～167772159的整数 · Cannot set the max rate of broadcasts when the value for the Broadcast Suppression field is On or Default：广播报文泛洪抑制开关为开启或默认状态时，不允许配置广播报文最大速率 · Cannot set the max rate of unknown multicasts when the value for the Unknown Multicast Suppression field is On or Default：未知组播报文泛洪抑制开关为开启或默认状态时，不允许配置未知组播报文最大速率 · You cannot apply a QoS policy to this vNetwork, because this vNetwork has been specified for a PVLAN mapping：指定的虚拟链路层网络已被PVLAN映射绑定，不允许绑定QoS策略 · A parent port and its subports must be configured with the same QoS profile：父端口和其子端口必须配置相同类型的QoS策略 · Invalid value for the gateway disabling feature：无效的禁用网关 · After you enable the IPv4 multicast network feature for the external network, you cannot select a gateway whose firewall deployment mode is off and method to deploy basic external connectivity settings is manual, and vice versa：外部网络不允许同时开启IPv4组播网络和绑定设备组防火墙接入模式为关闭且外网转发基础配置为手动预配置的出口网关 · After you select a gateway whose firewall deployment mode is off and method to deploy basic external connectivity settings is manual, you cannot enable OSPF for the external network, and vice versa：外部网络不允许同时配置OSPF路由协议和绑定设备组防火墙接入模式为关闭且外网转发基础配置为手动预配置的出口网关 · After you bind to the external network a gateway whose firewall deployment mode is off and method to deploy basic external connectivity settings is manual, you cannot configure any NQA profile-subnet bindings, and vice versa：外部网络不允许同时配置子网绑定NQA策略和绑定设备组防火墙接入模式为关闭且外网转发基础配置为手动预配置的出口网关 · After you bind to the external network a gateway whose firewall deployment mode is off and method to deploy basic external connectivity settings is manual, you cannot enable primary IP allocation for any subnets, and vice versa：外部网络不允许同时开启子网主IP所在子网和绑定设备组防火墙接入模式为关闭且外网转发基础配置为手动预配置的出口网关 · After you select a gateway whose firewall deployment mode is off and method to deploy basic external connectivity settings is manual, you must configure a segment ID for the external network：当外部网络绑定设备组防火墙接入模式为关闭且外网转发基础配置为手动预配置的出口网关时，必须配置External Segment ID · When a vRouter has been bound to the external network, the external subnets cannot overlap with the subnet for firewall access：外部网络已被虚拟路由器绑定时，外网子网与防火墙接入网段重叠 · The external network is bound to a gateway whose firewall deployment mode is off and method to deploy basic external connectivity settings is manual. You must configure a segment ID：当外部网络绑定设备组防火墙接入模式为关闭且外网转发基础配置为手动预配置的出口网关时，External Segment ID不允许配置为空 · A vRouter that has border gateway bindings is bound to the external network. You cannot bind to the external network a gateway whose firewall deployment mode is off and method to deploy basic external connectivity settings is manual：外部网络已被虚拟路由器绑定且该虚拟路由器绑定了出口网关时，外部网络不允许绑定设备组防火墙接入模式为关闭且外网转发基础配置为手动预配置出口网关 · A vRouter that has a non-service leaf firewall binding is bound to the external network. You cannot bind a gateway whose firewall deployment mode is off to the external network：外部网络已被虚拟路由器绑定且该虚拟路由器绑定了非Service Leaf类型的防火墙时，不允许绑定设备组防火墙接入模式为关闭的出口网关 · When you bind an external subnet to the vRouter, the subnet cannot overlap with the access subnet for the firewall associated with the vRouter：虚拟路由器绑定外网子网时，该外网子网与防火墙接入网段不能重叠 · DHCPv6 valid lifetime is beyond the value range：DHCPv6有效生命期值超出了范围限制 · DHCPv6 preferred lifetime is beyond the value range：DHCPv6首选生命期值超出了范围限制 · The DHCPv6 preferred lifetime must be less than or equal to the DHCPv6 valid lifetime：DHCPv6首选生命期值需要小于等于DHCPv6有效生命期值 · If the DHCPv6 preferred lifetime is 0, the DHCPv6 valid lifetime must also be 0：DHCPv6首选生命期值为0时，DHCPv6有效生命期值必须为0 · If the type of an external network is directly connected, you cannot enable the IPv6 multicast network feature for that external network：独享型外部网络不支持开启IPv6组播网络开关 · After you enable the IPv6 multicast network feature for the external network, you cannot select a gateway whose firewall deployment mode is off and method to deploy basic external connectivity settings is manual, and vice versa：外部网络不允许同时开启IPv6组播网络和绑定设备组防火墙接入模式为关闭且外网转发基础配置为手动预配置的出口网关 · When adding a VLAN-type external network, make sure the segment ID is not in the VLAN range of any global VLAN-VXLAN mappings：VLAN类型的外部网络创建时，不允许Segment ID值在全局VLAN-VXLAN映射的VLAN范围内 · Cannot allocate this external segment ID, because synchronization is in progress for the VXLAN pool containing this external segment ID：无法分配该External Segment ID，其所在的VXLAN池正在平滑中 · Resource application or rollback failed, internal unknown error：资源申请或回滚失败，内部未知错误 · The（resource）does not exist or the resources are insufficient：（资源）不存在或资源不足 · The（resource）does not exist or the resources are insufficient, device group name（name）：（资源）不存在或资源不足，设备组名称（名称） · The （resource） does not exist or the resources are insufficient, resource access template name （name）：（资源）不存在或资源不足，资源接入模板名称（名称） · The value of the vSwitch Flooding field is invalid：无效的虚拟交换机泛洪 · The value of the vSwitch Learning field is invalid：无效的虚拟交换机自学习 |
|
关键字 |
UPDATE_NETWORK_OP |
|
日志内容 |
Updated network "$1". |
|
参数解释 |
$1：虚拟链路层网络的名称 |
|
举例 |
Updated network "network01". |
|
日志说明 |
用户进行了修改虚拟链路层网络的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The external attribute can’t be modified：外部属性不能被修改 · The network's parameter is incorrect：虚拟网络参数错误 · The specified resource doesn't exist：指定的资源不存在 · Invalid broadcast suppression configuration：无效的广播报文抑制配置 · Invalid unknown multicast suppression configuration：无效的未知组播报文抑制配置 · Invalid unknown unicast suppression configuration：无效的未知单播报文抑制配置 · The ARP packet sending rate exceeds the rate limit：ARP报文发送速率超过速度限制 · The number of DHCP servers on the DHCP relay agent can't exceed 8：DHCP服务器的IP地址数不能超过8个 · The IP address of the DHCP server is invalid：无效的DHCP服务器IP地址 · The IP address of the DHCP server is required：未指定DHCP服务器的IP地址 · Failed to disable network sharing for the virtual link layer network because it is being used by other tenants：该虚拟链路层网络已被其他租户共享，不允许关闭共享 · External networks and VLANs do not support network sharing：外部网络或VLAN类型的网络不支持开启共享功能 · The network name cannot exceed 255 characters：虚拟链路层网络名称最长255个字符 · The VDS doesn't exist：VDS不存在 · The value of the router:external field is required：router:external不能为空 · The value of the shared field is required：shared不能为空 · The value of the admin_state_up field is required：admin_state_up不能为空 · The value of the distributed field is required：distributed不能为空 · The value of the vswitch_flood_and_learn field is invalid：无效的vswitch_flood_and_learn · Unknown error：未知错误 · Cannot segment the external network because it has been bound to a vRouter that is bound to a gateway resource configured with a priority：外部网络被虚拟路由器绑定后，若虚拟路由器的网关资源已配置优先级，则该外部网络不支持开启网络分段功能 · The value of the MTU must be an integer in the range of 68 to 65535：MTU必须为68～65535的整数 · The specified vPort QoS policy doesn't exist：指定的虚拟端口QoS策略不存在 · Invalid value in the physical_network field：无效的physical_network字段 · A vNetwork cannot use directly connected mode：虚拟链路层网络不支持独享模式 · When the Network Cloud feature is disabled, directly connected external networks are not supported：网络云开关关闭时，不支持配置独享模式的外部网络 · You have no privilege to perform this operation：用户无权限执行此操作 · Cannot bind the DHCP host group to an external network：外部网络不支持绑定DHCP主机组 · The DHCP host group does not exist：指定的DHCP主机组不存在 · Invalid auto port creation configuration：无效的自动创建虚拟端口配置 · You cannot bind the DHCP host group to the vNetwork. A network node in the DHCP host group has already created a DHCP vPort for the vNetwork：DHCP主机组中的网络节点已存在虚拟链路层网络的DHCP虚拟端口，不允许绑定 · The vNetwork is an interface-specific multicast network. You cannot disable its IPv4 multicast capabilities：指定的虚拟链路层网络已经绑定组播接口，不允许关闭IPv4组播开关 · To disable preprovisioning, make sure all its dependent features use their default settings. For information about these features, see online help：当以下开关全部取值为默认时，预配置开关才允许关闭。ARP泛洪、ARP上送控制组件、RARP泛洪、RARP上送控制组件、DHCP上送控制组件、IPv6 NS/NA上送控制组件、IPv6 NS/NA泛洪、IPv6 RS/RA上送控制组件和DHCPv6上送控制组件 · You cannot change the status of the multicast network feature when the network segmentation feature is enabled：当外部网络开启网络分段开关时，不允许切换组播网络开关 · The external segment ID is already in use：External Segment ID 已经被使用 · The external segment ID is out of range：External Segment ID超出范围 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · You can enable external route redistribution only for external networks：仅外部网络支持配置引入外网路由开关 · You can enable external route redistribution only when the L3VNI is specified：仅L3VNI不为空时支持开启引入外网路由开关 · You cannot edit or delete the cloud region name：云区域名称不允许修改或删除 · The gateway MAC cannot be a reserved MAC or device group MAC：网关MAC地址与系统保留MAC地址或设备组的MAC地址冲突 · The value for MAC address learning is invalid：无效的MAC地址学习开关 · The gateway MAC is invalid：无效的网关MAC地址 · You cannot edit the gateway MAC when the vNetwork contains OVS VMs：该虚拟链路层网络下存在主机Overlay的虚拟机，不允许修改网关MAC地址 · The gateway MAC of the vNetwork cannot be the same as the MAC address of the vPort on the vNetwork：虚拟链路层网络的网关MAC地址不能与该虚拟链路层网络的虚拟端口MAC地址相同 · You cannot change the status of the IPv4 multicast capabilities, because the vNetwork has been bound to a Layer 2 multicast network：虚拟链路层网络已被L2组播引用，IPv4组播网络开关不允许修改 · You cannot change the transparent mode state：透传模式不支持修改 · You cannot change the LLDP-based vPort onboarding state for the vNetwork, because some phy vPorts in the vNetwork have come online：当前虚拟链路层网络已有phy虚拟端口上线，不允许切换LLDP上线虚拟端口开关 · You cannot enable LLDP-based vPort onboarding for the vNetwork, because automatic vPort creation has been enabled for the vNetwork：当前虚拟链路层网络已开启自动创建虚拟端口，不允许开启LLDP上线虚拟端口开关 · Invalid LLDP-based vPort onboarding configuration：无效的LLDP上线虚拟端口配置 · Invalid transparent mode configuration：无效的透传模式配置 · You cannot enable both LLDP-based vPort onboarding and automatic vPort creation for the vNetwork：虚拟链路层网络的LLDP上线虚拟端口和自动创建虚拟端口开关不能同时开启 · You cannot enable the IPv4 multicast network feature for a directly connected external network：独享型外部网络不支持开启IPv4组播网络开关 · You cannot enable network segmentation to a directly connected external network：外部网络的工作模式为独享时，不支持开启网络分段功能 · You cannot configure external segment ID to a directly connected external network：外部网络的工作模式为独享时，不支持配置External Segment ID · The value for the arp_mac_learning parameter is invalid：ARP MAC地址学习参数取值无效 · The value for the nd_mac_learning parameter is invalid：IPv6 ND MAC地址学习参数取值无效 · The RT generated based on the segment ID of the vNetwork conflicts with the import RT on a vRouter：虚拟链路层网络Segment ID生成的RT与虚拟路由器配置的引入RT冲突 · The RT generated based on the segment ID of the vNetwork conflicts with the export RT on a vRouter：虚拟链路层网络Segment ID生成的RT与虚拟路由器配置的引出RT冲突 · The RT generated based on the external segment ID of the external network conflicts with the import RT on a vRouter：外部网络External Segment ID生成的RT与虚拟路由器配置的引入RT冲突 · The RT generated based on the external segment ID of the external network conflicts with the export RT on a vRouter：外部网络External Segment ID生成的RT与虚拟路由器配置的引出RT冲突 · You cannot enable both route reduction and directly connected mode：路由精简开关与独享型工作模式不允许同时开启 · You cannot enable both route reduction and redistribution of external routes：路由精简开关与引入外网路由开关不允许同时开启 · In the network cloud scenario, you cannot change the enabling state of route reduction for the external network：网络云场景下，不允许修改外部网络路由精简开关 · When network segmentation is enabled, you cannot change the enabling state of route reduction for the external network：网络分段开关开启时，不允许修改外部网络路由精简开关 · When route reduction is enabled, you cannot enable network segmentation for the external network：外部网络开启路由精简开关时，不允许开启网络分段 · When network segmentation is enabled, you cannot enable route reduction for the external network：外部网络开启网络分段时，不允许开启外部网络路由精简开关 · Route reduction can be enabled only when the external network type is VLAN：仅VLAN类型外部网络允许开启路由精简开关 · You cannot specify an external segment ID for a flat external network or vNetwork：Flat类型外部网络或者虚拟链路层网络的External Segment ID必须为空 · The specified border gateway doesn't exist：指定的出口网关不存在 · The RT generated based on the external segment ID of the external network is identical to the import RT of a Layer 2 DC interconnect：外部网络External Segment ID生成的RT与数据中心二层互联的引入RT冲突 · The RT generated based on the external segment ID of the external network is identical to the export RT of a Layer 2 DC interconnect：外部网络External Segment ID生成的RT与数据中心二层互联的引出RT冲突 · The RT generated based on the external segment ID of the external network is identical to the import RT of a Layer 3 DC interconnect：外部网络External Segment ID生成的RT与数据中心三层互联的引入RT冲突 · The RT generated based on the external segment ID of the external network is identical to the export RT of a Layer 3 DC interconnect：外部网络External Segment ID生成的RT与数据中心三层互联的引出RT冲突 · A vRouter and its attached external network must be bound to the same gateway：虚拟路由器的出口网关和外部网络的出口网关必须一致 · The vRouter has been bound to an external network, the gateway bound to the external network cannot be modified：虚拟路由器已绑定外部网络，该外部网络已绑定的出口网关不允许修改 · You cannot bind a gateway to a flat external network：FLAT类型外部网络不支持绑定出口网关 · You can bind only one gateway to an external network：外部网络只支持绑定一个出口网关 · The external network has been attached to a vRouter that has multiple gateways. You cannot specify a gateway for the external network：当虚拟路由器已绑定多个出口网关时，已绑定的外部网络不支持绑定出口网关 · You cannot both enable network segmentation and specify a gateway for an external network：外部网络的网络分段和出口网关冲突 · You cannot bind a border gateway to a directly connected external network：独享型外部网络不支持绑定出口网关 · In the network cloud scenario, you cannot bind a gateway to an external network：网络云场景下，外部网络不支持绑定出口网关 · You cannot bind the border gateway to the external network, because the external network has been bound to a vRouter and the border gateway is not bound to the vRouter：不允许外部网络配置出口网关，因为外部网络所绑定的虚拟路由器没绑定该出口网关 · You cannot enable the IPv4 multicast network feature for the external network, because it is already bound to an external transit vRouter：外部网络已被EXTERNALTRANSIT类型虚拟路由器绑定，不支持开启IPv4组播网络开关 · You cannot change the name of the external network, because a vRouter is already bound to the external network in the network cloud scenario：网络云场景下，虚拟路由器已绑定该外部网络，不允许修改外部网络名称 · The external network has been configured as a Layer 3 multicast network. You cannot change the status of the IPv4 multicast network feature：外部网络已被L3组播使用，不允许修改其IPv4组播网络开关 · The max rate of broadcasts must be an integer in the range of 64 to 167772159：广播报文最大速率范围必须为64～167772159的整数 · Cannot set the max rate of unknown unicasts when the value for the Unknown Unicast Suppression field is On or Default：未知单播报文泛洪抑制开关为开启或默认状态时，不允许配置未知单播报文最大速率 · The max rate of unknown unicasts must be an integer in the range of 64 to 167772159：未知单播报文最大速率范围必须为64～167772159的整数 · You cannot edit a vNetwork with the source as PVLAN：不允许修改来源为PVLAN的虚拟链路层网络 · The max rate of unknown multicasts must be an integer in the range of 64 to 167772159：未知组播报文最大速率范围必须为64～167772159的整数 · Cannot set the max rate of broadcasts when the value for the Broadcast Suppression field is On or Default：广播报文泛洪抑制开关为开启或默认状态时，不允许配置广播报文最大速率 · Cannot set the max rate of unknown multicasts when the value for the Unknown Multicast Suppression field is On or Default：未知组播报文泛洪抑制开关为开启或默认状态时，不允许配置未知组播报文最大速率 · The attached vRouter belongs to a vRouter link. It cannot be bound to both an IPv6 subnet and a centralized vNetwork：当虚拟链路层网络子网所绑定的虚拟路由器存在虚拟路由器连接时，不能同时绑定IPv6子网和集中式虚拟链路层网络 · You cannot apply a QoS policy to this vNetwork, because this vNetwork has been specified for a PVLAN mapping：指定的虚拟链路层网络已被PVLAN映射绑定，不允许绑定QoS策略 · You cannot enable route reduction for the external network, because it is bound to multiple vRouters configured with the same internal subnet：指定的外部网络已被多个虚拟路由器绑定，且多个虚拟路由器绑定的内网子网存在相同网段时，不允许开启路由精简开关 · A parent port and its subports must be configured with the same QoS profile：父端口和其子端口必须配置相同类型的QoS策略 · Invalid value for the gateway disabling feature：无效的禁用网关 · After you enable the IPv4 multicast network feature for the external network, you cannot select a gateway whose firewall deployment mode is off and method to deploy basic external connectivity settings is manual, and vice versa：外部网络不允许同时开启IPv4组播网络和绑定设备组防火墙接入模式为关闭且外网转发基础配置为手动预配置的出口网关 · After you select a gateway whose firewall deployment mode is off and method to deploy basic external connectivity settings is manual, you cannot enable OSPF for the external network, and vice versa：外部网络不允许同时配置OSPF路由协议和绑定设备组防火墙接入模式为关闭且外网转发基础配置为手动预配置的出口网关 · After you bind to the external network a gateway whose firewall deployment mode is off and method to deploy basic external connectivity settings is manual, you cannot configure any NQA profile-subnet bindings, and vice versa：外部网络不允许同时配置子网绑定NQA策略和绑定设备组防火墙接入模式为关闭且外网转发基础配置为手动预配置的出口网关 · After you bind to the external network a gateway whose firewall deployment mode is off and method to deploy basic external connectivity settings is manual, you cannot enable primary IP allocation for any subnets, and vice versa：外部网络不允许同时开启子网主IP所在子网和绑定设备组防火墙接入模式为关闭且外网转发基础配置为手动预配置的出口网关 · After you select a gateway whose firewall deployment mode is off and method to deploy basic external connectivity settings is manual, you must configure a segment ID for the external network：当外部网络绑定设备组防火墙接入模式为关闭且外网转发基础配置为手动预配置的出口网关时，必须配置External Segment ID · When a vRouter has been bound to the external network, the external subnets cannot overlap with the subnet for firewall access：外部网络已被虚拟路由器绑定时，外网子网与防火墙接入网段重叠 · The external network is bound to a gateway whose firewall deployment mode is off and method to deploy basic external connectivity settings is manual. You must configure a segment ID：当外部网络绑定设备组防火墙接入模式为关闭且外网转发基础配置为手动预配置的出口网关时，External Segment ID不允许配置为空 · A vRouter that has border gateway bindings is bound to the external network. You cannot bind to the external network a gateway whose firewall deployment mode is off and method to deploy basic external connectivity settings is manual：外部网络已被虚拟路由器绑定且该虚拟路由器绑定了出口网关时，外部网络不允许绑定设备组防火墙接入模式为关闭且外网转发基础配置为手动预配置出口网关 · A vRouter that has a non-service leaf firewall binding is bound to the external network. You cannot bind a gateway whose firewall deployment mode is off to the external network：外部网络已被虚拟路由器绑定且该虚拟路由器绑定了非Service Leaf类型的防火墙时，不允许绑定设备组防火墙接入模式为关闭的出口网关 · When you bind an external subnet to the vRouter, the subnet cannot overlap with the access subnet for the firewall associated with the vRouter：虚拟路由器绑定外网子网时，该外网子网与防火墙接入网段不能重叠 · DHCPv6 valid lifetime is beyond the value range：DHCPv6有效生命期值超出了范围限制 · DHCPv6 preferred lifetime is beyond the value range：DHCPv6首选生命期值超出了范围限制 · The DHCPv6 preferred lifetime must be less than or equal to the DHCPv6 valid lifetime：DHCPv6首选生命期值需要小于等于DHCPv6有效生命期值 · If the DHCPv6 preferred lifetime is 0, the DHCPv6 valid lifetime must also be 0：DHCPv6首选生命期值为0时，DHCPv6有效生命期值必须为0 · You cannot enable the IPv6 multicast network feature for the vNetwork, because the vNetwork has a Layer 2 DC interconnect binding：指定的虚拟链路层网络已绑定数据中心二层互联，不允许开启IPv6组播网络功能 · You cannot change the state of the IPv6 multicast network feature, because the vNetwork has been bound to a Layer 2 multicast network：虚拟链路层网络已被L2组播引用，IPv6组播网络开关不允许修改 · If the type of an external network is directly connected, you cannot enable the IPv6 multicast network feature for that external network：独享型外部网络不支持开启IPv6组播网络开关 · You cannot change the state of the IPv6 multicast network feature, because the external network has been bound to a Layer 3 multicast network：外部网络已被L3组播使用，不允许修改其IPv6组播网络开关 · You cannot disable the IPv6 multicast network feature for the vNetwork, because it has been bound to a multicast network interface：指定的虚拟链路层网络已经绑定组播接口，不允许关闭IPv6组播网络开关 · You cannot enable the IPv6 multicast network feature for the external network, because it has been bound to an external transit vRouter：外部网络已被EXTERNALTRANSIT类型虚拟路由器绑定，不支持开启IPv6组播网络开关 · After you enable the IPv6 multicast network feature for the external network, you cannot select a gateway whose firewall deployment mode is off and method to deploy basic external connectivity settings is manual, and vice versa：外部网络不允许同时开启IPv6组播网络和绑定设备组防火墙接入模式为关闭且外网转发基础配置为手动预配置的出口网关 · Cannot allocate this external segment ID, because synchronization is in progress for the VXLAN pool containing this external segment ID：无法分配该External Segment ID，其所在的VXLAN池正在平滑中 · Resource application or rollback failed, internal unknown error：资源申请或回滚失败，内部未知错误 · The（resource）does not exist or the resources are insufficient：（资源）不存在或资源不足 · The（resource）does not exist or the resources are insufficient, device group name（name）：（资源）不存在或资源不足，设备组名称（名称） · The （resource） does not exist or the resources are insufficient, resource access template name （name）：（资源）不存在或资源不足，资源接入模板名称（名称） · The value of the vSwitch Flooding field is invalid：无效的虚拟交换机泛洪 · The value of the vSwitch Learning field is invalid：无效的虚拟交换机自学习 |
|
关键字 |
DELETE_NETWORK_OP |
|
日志内容 |
Deleted network "$1". |
|
参数解释 |
$1：虚拟链路层网路的名称 |
|
举例 |
Deleted network "network02". |
|
日志说明 |
用户进行了删除虚拟链路层网络的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · Can’t delete the network because a port resides on the network：此网络正在被端口使用，不允许删除 · Can’t delete the network because a port group resides on the network：此网络正在被端口组使用，不允许删除 · The network contains a subnet：虚拟网络存在子网 · The specified resource doesn't exist：指定的资源不存在 · The port group has not been unbound from the subnet：请先删除端口组 · The subnet has not been unbound from the router：请先解除和虚拟路由器的绑定关系 · Can't delete the network because the network has flooding domains：虚拟链路层网络下存在泛洪域，不允许删除 · The network has been bound to a Layer 2 DC interconnection：虚拟链路层网络已被数据中心二层互联绑定 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · Cannot delete the vNetwork because it has been bound to an OSPF or OSPFv3 policy：虚拟链路层网络已被OSPF或OSPFv3策略绑定 · You cannot delete the vNetwork, because it has been bound to a Layer 2 multicast network：删除虚拟链路层网络失败，该虚拟链路层网络已经绑定了L2组播 · Cannot delete the vNetwork because it is being used by a System Center VM network：虚拟链路层网络已被VM网络使用，不允许删除 · Cannot delete the vNetwork because it is being used by a vCenter port group：虚拟链路层网络已被分布式端口组使用，不允许删除 · You cannot delete the external network, because it is bound to a Layer 3 multicast network：指定的外部网络已绑定L3组播，不允许删除 · You cannot delete a vNetwork with the source as PVLAN：不允许删除来源为PVLAN的虚拟链路层网络 · Cannot delete the vNetwork because it has been bound to an OSPF or OSPFv3 policy application：虚拟链路层网络已绑定OSPF策略，不允许删除 · Cannot delete the vNetwork because it is being used by a rhvm logical network：虚拟链路层网络已被逻辑网络使用，不允许删除 · Resource application or rollback failed, internal unknown error：资源申请或回滚失败，内部未知错误 · The（resource）does not exist or the resources are insufficient：（资源）不存在或资源不足 · The（resource）does not exist or the resources are insufficient, device group name（name）：（资源）不存在或资源不足，设备组名称（名称） · The （resource） does not exist or the resources are insufficient, resource access template name （name）：（资源）不存在或资源不足，资源接入模板名称（名称） |
|
关键字 |
CREATE_SUBNET_OP |
|
日志内容 |
Created subnet "$1" in vNetwork "$2" for tenant "$3". |
|
参数解释 |
$1：子网的名称 $2：子网所属虚拟链路层网络的名称或UUID $3：子网所属租户的名称或UUID |
|
举例 |
Created subnet "sub1" in vNetwork “net1” for tenant “admin”. |
|
日志说明 |
用户进行了创建子网的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · Invalid tenant ID：无效的租户ID · The network doesn’t exist：虚拟网络不存在 · The CIDR is required：未指定CIDR · The gateway IP is required：未指定网关IP · The gateway IP address doesn’t belong to the subnet：网关IP地址与子网不在同一网段 · The IP addresses in the address pool don't belong to the subnet：地址池地址不在子网范围内 · The gateway IP address conflicts with the subnet broadcast address：网关IP地址和子网广播IP地址冲突 · The gateway IP address conflicts with the subnet address：网关IP地址和子网IP地址冲突 · The subnet overlaps with another subnet：子网与其它的子网重叠 · The pool's start IP can't be higher than the end IP：地址池起始地址不能大于结束地址 · Please check the DHCP address pool for overlappingsubnets：DHCP地址池内网段重叠 · The subnet's tenant ID is different than the network：虚拟子网的租户ID与虚拟链路层网络的租户ID不一致 · The subnet ID already exists：该子网ID已存在 · Subnets created in bulk cannot use the same ID：批量创建的子网的ID存在重复 · Invalid IP address：无效的IP地址 · The domain name can't exceed 255 characters：计算域名称应少于255个字符 · Invalid server identifier：服务器标示符不可用 · The lease duration exceeds the limit：租约时间超出了范围限制 · The address pool address format is invalid：地址池的地址格式不可用 · The DNS server address format is invalid：DNS服务器地址格式不可用 · The format of the host route destination is invalid：主机路由目的网段格式不正确 · The format of the host route next hop is invalid：主机路由下一跳格式不正确 · The configuration contains duplicate host routes：配置包含重复的主机路由 · Invalid CIDR：无效的CIDR · The configuration contains duplicate DNS：配置包含重复的DNS · Failed to create subnets for a VXLAN because no available overlay license exists：Overlay license不可用，不能创建VXLAN类型网络的子网 · The subnet name cannot exceed 255 characters：虚拟子网名称最长255个字符 · An external subnet must be configured with a gateway IP address：外网子网的网关IP地址不能为空 · Subnets not configured with a gateway IP address cannot be enabled with DHCP：未配置网关IP地址的子网不允许使能DHCP功能 · The gateway IP for the subnet of a VLAN cannot be null：VLAN类型网络的子网，网关IP不能为空 · Failed to add the subnet because the number of subnets has reached the limit：虚拟子网的数量已达上限 · You must specify whether to enable DHCP for the subnet or not：未指定虚拟子网是否使能DHCP功能 · Failed to add subnets because the segment ID of the external network is empty and no segments exist：外部网络的Segment ID为空时，必须存在网络分段才能添加子网 · You must associate the subnet with a segment because the external network of the subnet has multiple segments：子网所在的外部网络存在多个网络分段时，子网必须绑定网络分段 · The subnet and its associated segment must belong to the same external network：子网和网络分段必须属于同一个外部网络 · The segment doesn't exist：指定的Segment不存在 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 · The specified NQA profile has been bound to another service resource：指定NQA策略已经被服务资源绑定 · The specified NQA profile does not exist：指定的NQA策略不存在 · Cannot bind the subnet to an NQA profile. The border gateway in the subnet has been bound to a track entry：NQA策略绑定失败，指定子网已绑定配置了Track项的出口网关 · Failed to add the subnet to the vNetwork, because it overlaps with a network bound to the context in another service chain：虚拟链路层网络添加子网失败，该修改会导致虚拟链路层网络所在特征组的服务链与其他服务链网段重叠 · A vNetwork supports only one primary IP：一个虚拟链路层网络下只允许有一个主IP · Up to one primray IP can be configured for an external network：一个外部网络下最多有一个主IP · You cannot bind a NQA profile to the external IPv4 subnet, because primary IP allocation has been enabled for the subnet：外部网络IPv4子网已配置主IP，不允许绑定NQA策略 · You cannot bind an NQA profile to a subnet of a directly connected external network：独享型外部网络子网不支持绑定NQA策略 · The protocol IP format is invalid：协议IP格式无效 · You can configure a protocol IP for only one subnet in a vNetwork：同一个虚拟链路层网络下，最多只有一个子网能配置协议IP · The protocol IP conflicts with a vPort IP or gateway IP：协议IP与虚拟端口IP或网关IP冲突 · You must specify two protocol IPs：协议IP仅支持配置两个地址 · The protocol IPs must belong to the subnet：协议IP必须在子网范围内 · Only IPv4 subnets support the protocol IP parameter：仅IPv4子网支持配置协议IP · The subnet broadcast address cannot be configured as a protocol IP：协议IP不支持配置为子网广播地址 · You cannot specify a subnet address as a protocol IP：协议IP不支持配置为子网IP地址 · You cannot add any subnets enabled with the primary IP allocation feature to the external network, because the external network is already bound to an external transit vRouter：外部网络已被EXTERNALTRANSIT类型虚拟路由器绑定，不支持创建主IP所在子网 · The vNetwork must belong to the same tenant as the current user：虚拟链路层网络所属的租户与当前用户所绑定的租户不一致 · If DHCP is enabled, the subnet mask length for IPv4 cannot be 31 and the prefix length for IPv6 cannot be 127：IPv4版本且开启DHCP时，子网网段不允许配置31位掩码；IPv6版本且开启DHCP时，子网网段不允许配置127前缀长度 · The specified NQA profile has been bound to a service path：该NQA策略已经被服务路径绑定 · Insufficient available IP addresses in the subnet for primary IP allocation：主IP所在子网可分配IP不足 |
|
关键字 |
UPDATE_SUBNET_OP |
|
日志内容 |
Updated subnet "$1" in vNetwork “$2” for tenant “$3”. |
|
参数解释 |
$1：子网的名称 $2：子网所属虚拟链路层网络的名称或UUID $3：子网所属租户的名称或UUID |
|
举例 |
Updated subnet "sub2" in vNetwork “net2” for tenant “admin”. |
|
日志说明 |
用户进行了修改子网的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The subnet ID is required：未指定子网ID · The pool's start IP can't be higher than the end IP：地址池起始地址不能大于结束地址 · Please check the DHCP address pool for overlappingsubnets：DHCP地址池内网段重叠 · The IP addresses in the address pool don't belong to the subnet：地址池地址不在子网范围内 · Invalid routing table：无效的路由表 · Invalid IP address：无效的IP地址 · The domain name can't exceed 255 characters：计算域名称应少于255个字符 · Invalid server identifier：服务器标示符不可用 · The format of the host route destination is invalid：主机路由目的网段格式不正确 · The format of the host route next hop is invalid：主机路由下一跳格式不正确 · The configuration contains duplicate host routes：配置包含重复的主机路由 · The address pool of the internal subnet can't be modified：内网子网的地址池不允许修改 · The specified resource doesn't exist：指定的资源不存在 · The subnet is not bound to a vRouter：该子网没有绑定的虚拟路由器 · The configuration contains duplicate DNS：配置包含重复的DNS · The subnet name cannot exceed 255 characters：虚拟子网名称最长255个字符 · The gateway IP address doesn’t belong to the subnet：网关IP地址与子网不在同一网段 · The gateway IP address conflicts with the subnet broadcast address：网关IP地址和子网广播IP地址冲突 · The gateway IP address conflicts with the subnet address：网关IP地址和子网IP地址冲突 · An external subnet must be configured with a gateway IP address：外网子网的网关IP地址不能为空 · Subnets not configured with a gateway IP address cannot be enabled with DHCP：未配置网关IP地址的子网不允许使能DHCP功能 · The gateway IP for the subnet of a VLAN cannot be null：VLAN类型网络的子网，网关IP不能为空 · Cannot modify the gateway IP address for the subnet, because the subnet is bound to a vRouter：该子网已被虚拟路由器绑定，不允许修改网关IP地址 · The gateway IP address is already used by a vPort：指定的网关IP地址已被虚拟端口占用 · The gateway IP address is already used by an APP cluster VIP：指定的网关IP地址已被应用集群虚IP占用 · The gateway IP address is already used by a floating IP：指定的网关IP地址已被浮动IP占用 · You must specify whether to enable DHCP for the subnet or not：未指定虚拟子网是否使能DHCP功能 · The segment UUID can't be delete or modify：子网绑定的Segment不允许修改和解绑 · An IP address in the DHCP address pool has been automatically assigned to an online vPort. The DHCP address pool must still contain the IP address after being edited：DHCP地址池中存在已上线的虚拟端口，修改后的DHCP地址池必须包含该虚拟端口IP地址 · The DHCP address pool cannot contain IP addresses that have been manually assigned to online vPorts：修改后的DHCP地址池范围内存在静态配置IP地址的已上线虚拟端口 · An IP address in the DHCP address pool has been automatically assigned to an online vPort. The DHCP address pool must still contain the IP address after being edited：DHCP地址池中存在已上线的虚拟端口，修改后的DHCP地址池必须包含该虚拟端口IP地址 · The DHCP address pool cannot contain IP addresses that have been manually assigned to online vPorts：修改后的DHCP地址池范围内存在静态配置IP地址的已上线虚拟端口 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 · Cannot edit the primary IP allocation setting for a subnet if the subnet is already used for primary IP allocation：不允许修改主IP所在的子网 · The gateway IP address has been used as the primary IP address：指定的网关IP地址已被主IP使用 · The external subnet contains an IP address that has been assigned to a vPort. You cannot bind the external subnet to an NQA profile：该外网子网中存在被虚拟端口指定的IP地址，不支持绑定NQA策略 · The specified NQA profile has been bound to another service resource：指定NQA策略已经被服务资源绑定 · The specified NQA profile does not exist：指定的NQA策略不存在 · Cannot bind the subnet to an NQA profile. The border gateway in the subnet has been bound to a track entry：NQA策略绑定失败，指定子网已绑定配置了Track项的出口网关 · A vNetwork supports only one primary IP：一个虚拟链路层网络下只允许有一个主IP · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · You cannot edit or delete the cloud region name：云区域名称不允许修改或删除 · You cannot bind a NQA profile to the external IPv4 subnet, because primary IP allocation has been enabled for the subnet：外部网络IPv4子网已配置主IP，不允许绑定NQA策略 · You cannot specify an NQA profile for the external subnet. The gateway address for the subnet is the same as the next hop address of a route entry configured with an NQA profile, and the route entry has been bound to the same vRouter as the subnet：当外网子网网关IP与所属虚拟路由器的路由表项下一跳IP地址相同，且该路由表项已绑定NQA策略，则外网子网不允许绑定NQA策略 · You cannot bind an NQA profile to a subnet of a directly connected external network：独享型外部网络子网不支持绑定NQA策略 · You cannot unbind the subnet from the vRouter. This is because the routing table bound to the vRouter contains a route entry that uses an IP address in the subnet as the next hop, and the route entry is configured with a BFD session：当前虚拟路由器存在下一跳IP地址属于该子网且配置了BFD会话的路由表项，不允许解绑该子网 · The protocol IP format is invalid：协议IP格式无效 · You can configure a protocol IP for only one subnet in a vNetwork：同一个虚拟链路层网络下，最多只有一个子网能配置协议IP · The protocol IP conflicts with a vPort IP or gateway IP：协议IP与虚拟端口IP或网关IP冲突 · You must specify two protocol IPs：协议IP仅支持配置两个地址 · The protocol IPs must belong to the subnet：协议IP必须在子网范围内 · Only IPv4 subnets support the protocol IP parameter：仅IPv4子网支持配置协议IP · The subnet broadcast address cannot be configured as a protocol IP：协议IP不支持配置为子网广播地址 · You cannot specify a subnet address as a protocol IP：协议IP不支持配置为子网IP地址 · If DHCP is enabled, the subnet mask length for IPv4 cannot be 31 and the prefix length for IPv6 cannot be 127：IPv4版本且开启DHCP时，子网网段不允许配置31位掩码；IPv6版本且开启DHCP时，子网网段不允许配置127前缀长度 · You cannot specify an extended SNAT IP address as a gateway IP address in the same external network：扩展SNAT IP地址不能与子网网关IP地址冲突 · The lease duration exceeds the limit：租约时间超出了范围限制 · The specified NQA profile has been bound to a service path：该NQA策略已经被服务路径绑定 |
|
关键字 |
DELETE_SUBNET_OP |
|
日志内容 |
Deleted subnet "$1" in vNetwork “$2” for tenant “$3”. |
|
参数解释 |
$1：子网的名称 $2：子网所属虚拟链路层网络的名称或UUID $3：子网所属租户的名称或UUID |
|
举例 |
Deleted subnet "sub3" in vNetwork “net3” for tenant “admin”. |
|
日志说明 |
用户进行了删除子网的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The subnet contains manually created vPorts：虚拟子网中存在手动创建的虚拟端口 · The port group has not been unbound from the subnet：请先删除端口组 · The subnet has not been unbound from the router：请先解除和虚拟路由器的绑定关系 · An APP cluster VIP resides on the subnet：该子网内存在应用集群虚IP · The specified resource doesn't exist：指定的资源不存在 · The external subnet has floating IPs：外网子网存在浮动IP · The subnet has been bound to a vRouter interconnection：该子网已被虚拟路由器连接绑定 · The subnet has been bound to a Layer 3 DC interconnection：该子网已被数据中心三层互联绑定 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 · The vNetwork is an interface-specific multicast network. You cannot unbind its only subnet from the vRouter：指定的虚拟链路层网络已经绑定组播接口，该虚拟链路层网络下的最后一个子网不允许解绑虚拟路由器 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · You cannot delete the subnet, because it contains extended SNAT IP addresses：指定的子网中包含扩展SNAT IP地址，不允许删除 · IP addresses in the subnet used for primary IP allocation have been allocated：主IP所在子网已分配IP地址 · You cannot delete the subnet, because it has been specified for the ingress or egress vPort of a third-party service device bound to a service path：指定子网已被第三方服务设备的出入虚拟端口使用，且该第三方服务设备已被服务路径使用，不允许删除 · You cannot delete the specified subnet, because an auto-created vPort under the subnet is already used by a third-party service device.：指定子网下存在自动创建的vPort已被第三方服务设备引用，不允许删除 |
|
关键字 |
CREATE_QOS_OP |
|
日志内容 |
Created QoS "$1". |
|
参数解释 |
$1：QoS模板的名称 |
|
举例 |
Created QoS "policy01". |
|
日志说明 |
用户进行了创建QoS模板的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The QoS profile UUID is already used：QoS模板UUID已存在 · Invalid CIR value of inbound QoS profile：入方向QoS模板平均速率参数无效 · Invalid CIR value of outbound QoS profile：出方向QoS模板平均速率参数无效 · Invalid CBS value of inbound QoS profile：入方向QoS模板突发尺寸参数无效 · Invalid CBS value of outbound QoS profile：出方向QoS模板突发尺寸参数无效 · Invalid DSCP value：无效的DSCP参数 · Invalid QoS profile rate value：QoS模板的速率值不可用 · QoS profiles created in bulk cannot use the same UUID：批量创建的QoS模板的UUID存在重复 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 · You can configure up to 65534 flow-based rate limiting rules in a QoS template：QoS模板中流限速的QoS规则最多配置65534条 · You cannot configure both flow-based rate limiting and port-based rate limiting：流限速类型和端口限速类型不允许同时配置 · Duplicate flow-based rate limiting rule IDs：流限速规则的ID重复 · Invalid IP version：无效的IP版本 · Invalid protocol type：无效的协议类型 · The value for the average field must be in the range of 1 to 4294967295：平均速率取值范围为1~4294967295 · The value for the burst field must be in the range of 1 to 536869888：突发尺寸的取值范围为1~536869888 · Please specify the average field and the burst field：平均速率和突发尺寸都不能为空 · The value for the icmp_type field must be in the range of 0 to 255：icmp_type参数的取值范围为0~255 · The value for the icmp_code field must be in the range of 0 to 255：icmp_code参数的取值范围为0~255 · The value range for the port number is 0 to 65535. The source_port or destination_port field can be a single port or a port range in the format of XX-XX. To specify a port number range, make sure the start value is not greater than the end value：source_port参数和destination_port参数的取值范围为0～65535的整数或区间，当取值为区间时，格式为XX-XX，且起始值不能大于结束值 · Invalid direction for the flow-based rate limiting rule：无效的流限速规则方向 · Please specify a source IP/subnet, destination IP/subnet, or both：源IP地址/网段和目的IP地址/网段至少指定一个 · Invalid IP or subnet：无效的IP地址或网段 · The specified IP or subnet does not match the IP version：IP地址或网段与IP版本不匹配 · Overlapping quintuple information for flow-based rate limiting rules in the same direction：同一流限速下同方向QoS规则的五元组信息重叠 · You can edit only the average and burst fields for a flow-based rate limiting rule：流限速规则仅允许修改平均速度和突发尺寸 · The specified QoS template has been bound to a floating IP. You cannot set the rate limiting type to flow-based：指定的QoS模板已绑定浮动IP，限速类型不允许为流限速类型 · The icmp_type and icmp_code fields can be configured only when the protocol type is ICMP：协议类型为ICMP时，才允许配置icmp_type和icmp_code字段 · The source_port and destination_port fields can be configured only when the protocol type is TCP or UDP：协议类型为TCP或UDP时，才允许配置source_port和destination_port字段 · A parent port and its subports must be configured with the same QoS profile：父端口和其子端口必须配置相同类型的QoS策略 · Do not set both the Source IP/Subnet and Destination IP/Subnet parameters to a subnet with an all-zero mask. If you configure one of the parameters as a subnet with an all-zero mask, the other parameter cannot be empty：源IP/网段和目的IP/网段不允许同时配置为掩码全0的网段，且不允许一个参数为空，另一个参数的掩码全为0 · DSCP values cannot be configured, when a QoS rule is applied to the inbound (VM) direction：QoS入方向流规则，不支持配置DSCP · The DSCP value range is 0 to 63, when a QoS rule is applied to the outbound (VM) direction：存在出方向流规则，DSCP缺省为空，支持配置，取值范围是0~63的整数 |
|
关键字 |
UPDATE_QOS_OP |
|
日志内容 |
Updated QoS "$1". |
|
参数解释 |
$1：QoS模板的名称 |
|
举例 |
Updated QoS "policy01". |
|
日志说明 |
用户进行了修改QoS模板的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The QoS profile ID is required：未指定QoS模板UUID · Failed to remove the inbound QoS profile：取消入方向QoS模板失败 · Failed to remove the outbound QoS profile：取消出方向QoS模板失败 · Invalid CIR value of inbound QoS profile：入方向QoS模板平均速率参数无效 · Invalid CIR value of outbound QoS profile：出方向QoS模板平均速率参数无效 · Invalid CBS value of inbound QoS profile：入方向QoS模板突发尺寸参数无效 · Invalid CBS value of outbound QoS profile：出方向QoS模板突发尺寸参数无效 · Invalid DSCP value：无效的DSCP参数 · The specified resource doesn't exist：指定的资源不存在 · Invalid QoS profile rate value：QoS模板的速率值不可用 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · You cannot edit or delete the cloud region name：云区域名称不允许修改或删除 · You can configure up to 65534 flow-based rate limiting rules in a QoS template：QoS模板中流限速的QoS规则最多配置65534条 · You cannot configure both flow-based rate limiting and port-based rate limiting：流限速类型和端口限速类型不允许同时配置 · Duplicate flow-based rate limiting rule IDs：流限速规则的ID重复 · Invalid IP version：无效的IP版本 · Invalid protocol type：无效的协议类型 · The value for the average field must be in the range of 1 to 4294967295：平均速率取值范围为1~4294967295 · The value for the burst field must be in the range of 1 to 536869888：突发尺寸的取值范围为1~536869888 · Please specify the average field and the burst field：平均速率和突发尺寸都不能为空 · The value for the icmp_type field must be in the range of 0 to 255：icmp_type参数的取值范围为0~255 · The value for the icmp_code field must be in the range of 0 to 255：icmp_code参数的取值范围为0~255 · The value range for the port number is 0 to 65535. The source_port or destination_port field can be a single port or a port range in the format of XX-XX. To specify a port number range, make sure the start value is not greater than the end value：source_port参数和destination_port参数的取值范围为0～65535的整数或区间，当取值为区间时，格式为XX-XX，且起始值不能大于结束值 · Invalid direction for the flow-based rate limiting rule：无效的流限速规则方向 · Please specify a source IP/subnet, destination IP/subnet, or both：源IP地址/网段和目的IP地址/网段至少指定一个 · Invalid IP or subnet：无效的IP地址或网段 · The specified IP or subnet does not match the IP version：IP地址或网段与IP版本不匹配 · Overlapping quintuple information for flow-based rate limiting rules in the same direction：同一流限速下同方向QoS规则的五元组信息重叠 · You can edit only the average and burst fields for a flow-based rate limiting rule：流限速规则仅允许修改平均速度和突发尺寸 · The specified QoS template has been bound to a floating IP. You cannot set the rate limiting type to flow-based：指定的QoS模板已绑定浮动IP，限速类型不允许为流限速类型 · The icmp_type and icmp_code fields can be configured only when the protocol type is ICMP：协议类型为ICMP时，才允许配置icmp_type和icmp_code字段 · The source_port and destination_port fields can be configured only when the protocol type is TCP or UDP：协议类型为TCP或UDP时，才允许配置source_port和destination_port字段 · A parent port and its subports must be configured with the same QoS profile：父端口和其子端口必须配置相同类型的QoS策略 · DSCP values cannot be configured, when a QoS rule is applied to the inbound (VM) direction：QoS入方向流规则，不支持配置DSCP · The DSCP value range is 0 to 63, when a QoS rule is applied to the outbound (VM) direction：存在出方向流规则，DSCP缺省为空，支持配置，取值范围是0~63的整数 |
|
关键字 |
DELETE_QOS_OP |
|
日志内容 |
Deleted QoS "$1". |
|
参数解释 |
$1：QoS模板的名称 |
|
举例 |
Deleted QoS "policy01". |
|
日志说明 |
用户进行了删除QoS模板的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The Qos profile has been bound to a port：QoS模板已被虚拟端口绑定 · The Qos profile has been bound to a port group：QoS模板已被端口组绑定 · The Qos profile has been bound to a virtual network：QoS模板已被虚拟链路层网络绑定 · The QoS profile has been bound to floating IPs：QoS模板已被浮动IP绑定 · The specified resource doesn't exist：指定的资源不存在 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_SECURITY_POLICY_OP |
|
日志内容 |
Created security policy"$1". |
|
参数解释 |
$1：安全策略的名称 |
|
举例 |
Created security policy"spolicy01". |
|
日志说明 |
用户进行了创建安全策略的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · Duplicate security policy UUID：安全策略UUID冲突 · Security policies created in bulk cannot use the same ID：批量创建的安全策略的ID存在重复 · Invalid empty rule action：无效的空规则行为 · The security policy name cannot exceed 255 characters：安全策略名称最长255个字符 · The ip_mac_bingding is required：未指定IP-MAC防欺骗参数 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 · The ID pool for summarized OpenFlow entries of security policies does not have enough IDs for allocation：安全策略对应的集合流表ID池内可分配ID不足 |
|
关键字 |
UPDATE_SECURITY_POLICY_OP |
|
日志内容 |
Updated security policy "$1". |
|
参数解释 |
$1：安全策略的名称 |
|
举例 |
Updated security policy "spolicy01". |
|
日志说明 |
用户进行了修改安全策略的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The security policy ID is required：未指定安全策略UUID · Invalid empty rule action：无效的空规则行为 · The specified resource doesn't exist：指定的资源不存在 · The security policy name cannot exceed 255 characters：安全策略名称最长255个字符 · The specified tenant ID cannot be modified：已指定的租户ID不允许修改 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · You cannot edit or delete the cloud region name：云区域名称不允许修改或删除 |
|
关键字 |
DELETE_SECURITY_POLICY_OP |
|
日志内容 |
Deleted security policy "$1". |
|
参数解释 |
$1：安全策略的名称 |
|
举例 |
Deleted security policy "spolicy01". |
|
日志说明 |
用户进行了删除安全策略的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The security policy has been bound to a port or a port group：安全策略已被端口组或者虚拟端口绑定 · The specified resource doesn't exist：指定的资源不存在 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_FLOATING_IP_OP |
|
日志内容 |
Created floating IP "$1". |
|
参数解释 |
$1：浮动IP地址 |
|
举例 |
Created floating ip "202.100.1.10". |
|
日志说明 |
用户进行了创建浮动IP的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The specified subnet doesn't exist：指定的虚拟子网不存在 · The specified subnet is not an external subnet：指定子网不是外网子网 · The specified port doesn't exist：指定的端口不存在 · Invalid port type：无效的端口类型 · The fixed IP address must be the IP address of the port：fixed_ip_address必须与端口IP地址一致 · The port has not been bound to the router：端口未绑定虚拟路由器 · Floating IP address allocation failed：地址分配失败 · The IP address must belong to the specified subnet：IP地址不在子网内 · The network doesn't exist：虚拟网络不存在 · Failed to bind the floating IP to the vPort or APP cluster VIP, because the floating IP doesn't belong to the external network bound to the vRouter of the vPort or APP cluster VIP：关联浮动IP地址失败，浮动IP地址所属外部网络与端口或应用集群虚IP所属vRouter的外部网络不一致 · The floating IP ID already exists：浮动IP的ID已存在 · Floating IPs created in bulk cannot use the same ID：批量创建的浮动IP的ID存在重复 · The APP cluster VIP doesn't exist：应用集群虚IP不存在 · Invalid protocol type：无效的协议类型 · Invalid port number：指定的端口号错误 · The configuration conflicts with the configuration of an existing floating IP：该配置与其他浮动IP的配置相冲突 · The floating IP can be bound only to a vPort or an APP cluster VIP：浮动IP只能绑定虚拟端口或应用集群虚IP · The subnet to which the APP cluster VIP belongs is not bound to a vRouter：应用集群虚IP所属子网未绑定虚拟路由器 · The configuration of the floating IP conflicts with the configuration of a bound floating IP：浮动IP的配置与已绑定的浮动IP相冲突 · Invalid local port number：参数local_port_number不可用 · The IP address doesn't belong to the network：该IP地址不属于该网络 · The specified network is not an external network：指定的网络不是外网网络 · The specified subnet doesn't belong to the network：指定的子网不属于该网络 · The vRouter is not bound to an external network：虚拟路由器未绑定外网 · The external network doesn't exist：外网不存在 · The external network doesn't have any subnets：指定的外网无子网 · The floating IP conflicts with an extranet IP：指定的浮动IP地址与外网IP冲突 · The floating IP conflicts with a gateway IP：指定的浮动IP地址与网关IP冲突 · The floating IP conflicts with the broadcast address of the subnet：浮动IP地址和子网广播IP地址冲突 · The floating IP conflicts with the subnet address：浮动IP地址和子网地址冲突 · The UUIDs of the vPort, APP cluster VIP, subnet, and network to which the floating IP belongs are not specified：未指定端口ID、应用集群虚IP和浮动IP所属子网 · Invalid IP address：无效的IP地址 · The QoS policy and inbound/outbound CIR cannot be both configured：QoS策略与入/出方向平均速率不能同时配置 · Unknown error：未知错误 · Cannot set floating IPs for a directly connected external network：浮动IP不支持配置独享型外部网络 · When you create a floating IP, if you specify only the vPort or App cluster VIP and the vRouter of the floating IP is bound to one external network with network segmentation enabled or multiple external networks, you must specify an IP address for the floating IP：创建浮动IP时，如果仅指定了虚拟端口或应用集群虚IP，且所属虚拟路由器绑定多个外网或一个外网开启了网络分段功能，则需要指定浮动IP地址 · You have no privilege to perform this operation：用户无权限执行此操作 · You cannot select a subnet for primary IP allocation when creating a floating IP：不支持使用主IP所在子网创建浮动IP · The external network does not have IPv4 vSubnets for allocating floating IPs：分配浮动IP失败，不存在对应IPv4版本的外网子网 · You cannot specify the floating IP address as an extended SNAT IP address in the same external network：浮动IP不能与扩展SNAT IP地址冲突 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · The network_id and subnet_id fields of an INTERNAL_IP floating IP cannot be empty at the same time：INTERNAL_IP类型浮动IP的network_id，subnet_id不能同时为空 · Invalid floating IP type：无效的浮动IP类型 · You must specify an internal IP address for an INTERNAL_IP floating IP：INTERNAL_IP类型浮动IP的内网IP地址不能为空 · The floating IP type is not editable：浮动IP类型不支持修改 · You must specify the IP address of an INTERNAL_IP floating IP：INTERNAL_IP类型浮动IP的IP地址不能为空 · The port_id field of an INTERNAL_IP floating IP must be empty：INTERNAL_IP类型浮动IP的port_id必须为空 · The clusterIpId field of an INTERNAL_IP floating IP must be empty：INTERNAL_IP类型浮动IP的clusterIpId必须为空 · The vrouter_id field of an INTERNAL_IP floating IP cannot be empty：INTERNAL_IP类型浮动IP的vrouter_id不能为空 · You can specify only an external transit vRouter for a floating IP of the INTERNAL_IP floating type：INTERNAL_IP类型浮动IP仅支持EXTERNALTRANSIT类型虚拟路由器 · You cannot bind a floating IP to a flow-based rate limiting QoS policy：浮动IP不允许绑定流限速类型的QoS策略 |
|
关键字 |
UPDATE_FLOATING_IP_OP |
|
日志内容 |
Updated floating IP $1 |
|
参数解释 |
$1：浮动IP地址 |
|
举例 |
Updated floating IP "202.100.1.10" |
|
日志说明 |
用户进行了修改浮动IP的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The specified port doesn't exist：指定的端口不存在 · The port has not been bound to the router：端口未绑定虚拟路由器 · The external network doesn't exist：外网不存在 · The floating IP has been bound to another port：浮动IP已绑定其他端口 · The specified resource doesn't exist：指定的资源不存在 · The gateway of the vRouter to which the floating IP belongs doesn't support floating IP addresses：浮动IP所属虚拟路由器的网关不支持浮动IP功能 · The floating IP address has been used by another gateway resource：浮动IP地址已被其他网关资源占用 · The vRouter to which the floating IP address belongs doesn't bind a gateway service resource：浮动IP所属的虚拟路由器未绑定网关服务资源 · The vRouter to which the floating IP address belongs has not been bound to a gateway：浮动IP所属的虚拟路由器未指定网关 · Failed to bind the floating IP to the vPort or APP cluster VIP, because the floating IP doesn't belong to the external network bound to the vRouter of the vPort or APP cluster VIP：关联浮动IP地址失败，浮动IP地址所属外部网络与端口或应用集群虚IP所属vRouter的外部网络不一致 · The APP cluster VIP doesn't exist：应用集群虚IP不存在 · Invalid protocol type：无效的协议类型 · Invalid port number：指定的端口号错误 · The floating IP can be bound only to a vPort or an APP cluster VIP：浮动IP只能绑定虚拟端口或应用集群虚IP · The subnet to which the APP cluster VIP belongs is not bound to a vRouter：应用集群虚IP所属子网未绑定虚拟路由器 · The floating IP has been bound to another APP cluster VIP：浮动IP已绑定其它应用集群虚IP · The configuration of the floating IP conflicts with the configuration of a bound floating IP：浮动IP的配置与已绑定的浮动IP相冲突 · Invalid local port number：参数local_port_number不可用 · Invalid IP address：无效的IP地址 · The IP address of the floating IP can't be modified：浮动IP的IP地址不允许被修改 · The protocol type and the port number of the floating IP can't be modified：浮动IP的协议类型和端口号不允许被修改 · The UUIDs of the vPort, APP cluster VIP, subnet, and network to which the floating IP belongs are not specified：未指定端口ID、应用集群虚IP和浮动IP所属子网 · The QoS policy and inbound/outbound CIR cannot be both configured：QoS策略与入/出方向平均速率不能同时配置 · The subnet to which the floating IP belongs is already bound to a network segment. However, all IPv4 subnets of that network segment are not bound to the vRouter or any of its peer vRouters in distributed-mode vRouter links：浮动IP所属子网已绑定网络分段，且该网络分段绑定的所有IPv4子网均未被虚拟路由器或与该虚拟路由器建立分布式虚拟路由器连接的虚拟路由器绑定 · Unknown error：未知错误 · Cannot set floating IPs for a directly connected external network：浮动IP不支持配置独享型外部网络 · You have no privilege to perform this operation：用户无权限执行此操作 · You cannot edit or delete the cloud region name：云区域名称不允许修改或删除 · You cannot specify the floating IP address as an extended SNAT IP address in the same external network：浮动IP不能与扩展SNAT IP地址冲突 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · The network_id and subnet_id fields of an INTERNAL_IP floating IP cannot be empty at the same time：INTERNAL_IP类型浮动IP的network_id，subnet_id不能同时为空 · Invalid floating IP type：无效的浮动IP类型 · You must specify an internal IP address for an INTERNAL_IP floating IP：INTERNAL_IP类型浮动IP的内网IP地址不能为空 · The floating IP type is not editable：浮动IP类型不支持修改 · You must specify the IP address of an INTERNAL_IP floating IP：INTERNAL_IP类型浮动IP的IP地址不能为空 · The port_id field of an INTERNAL_IP floating IP must be empty：INTERNAL_IP类型浮动IP的port_id必须为空 · The clusterIpId field of an INTERNAL_IP floating IP must be empty：INTERNAL_IP类型浮动IP的clusterIpId必须为空 · The vrouter_id field of an INTERNAL_IP floating IP cannot be empty：INTERNAL_IP类型浮动IP的vrouter_id不能为空 · You can specify only an external transit vRouter for a floating IP of the INTERNAL_IP floating type：INTERNAL_IP类型浮动IP仅支持EXTERNALTRANSIT类型虚拟路由器 · You cannot bind a floating IP to a flow-based rate limiting QoS policy：浮动IP不允许绑定流限速类型的QoS策略 · All IPv4 subnets of the external network to which the floating IP belongs are not bound to the vRouter or any of its peer vRouters in distributed-mode vRouter links：浮动IP所属外部网络所有IPv4子网均未被虚拟路由器或与该虚拟路由器建立分布式虚拟路由器连接的虚拟路由器绑定 |
|
关键字 |
DELETE_FLOATING_IP_OP |
|
日志内容 |
Deleted floating IP $1 |
|
参数解释 |
$1：浮动IP地址 |
|
举例 |
Deleted floating IP "202.100.1.10". |
|
日志说明 |
用户进行了删除浮动IP的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The specified resource doesn't exist：指定的资源不存在 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
CREATE_PORT_GROUP_OP |
|
日志内容 |
Created port group "$1". |
|
参数解释 |
$1：端口组的名称 |
|
举例 |
Created port group "group01". |
|
日志说明 |
用户进行了创建端口组的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The port group name is already used：端口组名字已存在 · The port group ID is already used：端口组ID已存在 · Port groups created in bulk cannot use the same ID：批量创建的端口组的ID存在重复 · The port group name should be less than 255 characters：端口组名字最多255个字符 · The description cannot exceed 255 characters：描述最长255个字符 · The network ID is required：未指定虚拟网络ID · The network doesn't exist：虚拟网络不存在 · The specified QoS policy doesn't exist：指定的QoS策略不存在 · The specified security policy doesn't exist：指定的安全策略不存在 · Failed to create the port group on the vCenter：在vCenter上创建端口组失败 · The ID of the specified tenant is different than the tenant to which the specified virtual link layer network belongs：指定的租户ID和指定的虚拟链路层网络所属的租户ID不匹配 · The port group name is required：未指定端口组名称 · Can't specify a network whose origin is PBR：不允许指定来源为PBR的虚拟链路层网络 · A port group cannot be bound to a security policy when it contains port security disabled vPorts：端口组下存在未开启端口安全的虚拟端口，不允许绑定安全策略 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 · A parent port and its subports must be configured with the same QoS profile：父端口和其子端口必须配置相同类型的QoS策略 |
|
关键字 |
UPDATE_PORT_GROUP_OP |
|
日志内容 |
Updated port group “$1” |
|
参数解释 |
$1：端口组的名称 |
|
举例 |
Updated port group "group01". |
|
日志说明 |
用户进行了修改端口组的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The specified QoS policy doesn't exist：指定的QoS策略不存在 · The specified security policy doesn't exist：指定的安全策略不存在 · The port group ID is required：未指定端口组ID · Can't modify the port group name：端口组名称不能改变 · Can't modify the network where the port group resides：端口组所属的虚拟网络不能改变 · The specified resource doesn't exist：指定的资源不存在 · Operation failed. The security policy rule failed to take effect because of insufficient hardware resources：操作失败，硬件资源不足导致安全策略规则无法生效 · The description cannot exceed 255 characters：描述最长255个字符 · A port group cannot be bound to a security policy when it contains port security disabled vPorts：端口组下存在未开启端口安全的虚拟端口，不允许绑定安全策略 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · A parent port and its subports must be configured with the same QoS profile：父端口和其子端口必须配置相同类型的QoS策略 |
|
关键字 |
DELETE_PORT_GROUP_OP |
|
日志内容 |
Deleted port group “$1” |
|
参数解释 |
$1：端口组的名称 |
|
举例 |
Deleted port group "group01". |
|
日志说明 |
用户进行了删除端口组的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The port group contains visible ports：端口组内有可见端口 · The specified resource doesn't exist：指定的资源不存在 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_SECURITY_RULE_OP |
|
日志内容 |
Created security rules $1. |
|
参数解释 |
$1：安全规则的配置信息 |
|
举例 |
Created security rules { UUID: 9dc511fc-c4ba-413a-aa8e-c182cdb20e18 Security policy name: test1 Direction: egress IPv4 prefix: 2.2.2.0/24 Protocol type: UDP Port range: 3～17 }, { UUID: f48b45ff-db86-4969-93a7-b184ad8807aa Security policy name: test2 Direction: ingress Remote security policy name: remote1 Protocol type: UDP Port range: 1～2 }. |
|
日志说明 |
用户进行了创建ACL规则的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · Invalid security policy UUID：无效的安全策略UUID · Duplicate security rule UUID：安全规则UUID冲突 · Security rules created in bulk cannot use the same UUID：批量创建的安全规则的UUID存在重复 · The new security rule conflicts with the old rules：该安全规则与已存在的安全规则冲突 · Invalid IP version：无效的IP版本 · Invalid IP prefix：无效的IP前缀 · Invalid protocol type：无效的协议类型 · Invalid port range：无效的端口范围 · Invalid ICMP type：无效的ICMP报文类型 · Invalid ICMP code：无效的ICMP代码 · Invalid direction：方向不可用 · Operation failed. The security policy rule failed to take effect because of insufficient hardware resources：操作失败，硬件资源不足导致安全策略规则无法生效 · The IP prefix and the security policy can't both be configured：不能同时配置IP前缀和安全策略 · The IP prefix and the IP version do not match：IP前缀与IP协议版本不匹配 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
UPDATE_SECURITY_RULE_OP |
|
日志内容 |
Updated security rule $1. |
|
参数解释 |
$1：安全规则的配置信息 |
|
举例 |
Updated security rule { UUID: 536be81d-413e-420d-8c5f-8075b11affa6 Security policy name: test5 Direction: egress IPv4 prefix: 4.2.2.0/24 Protocol type: ICMP Type: 1 Code: 2 }. |
|
日志说明 |
用户进行了修改安全规则的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The new security rule conflicts with the old rules：该安全规则与已存在的安全规则冲突 · Invalid IP version：无效的IP版本 · Invalid IP prefix：无效的IP前缀 · Invalid protocol type：无效的协议类型 · Invalid port range：无效的端口范围 · Invalid ICMP type：无效的ICMP报文类型 · Invalid ICMP code：无效的ICMP代码 · Invalid direction：方向不可用 · The specified resource doesn’t exist：指定的资源不存在 · Operation failed. The security policy rule failed to take effect because of insufficient hardware resources：操作失败，硬件资源不足导致安全策略规则无法生效 · The IP prefix and the security policy can't both be configured：不能同时配置IP前缀和安全策略 · The IP prefix and the IP version do not match：IP前缀与IP协议版本不匹配 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · You cannot edit or delete the cloud region name：云区域名称不允许修改或删除 |
|
关键字 |
DELETE_SECURITY_RULE_OP |
|
日志内容 |
Deleted security rule $1. |
|
参数解释 |
$1：安全规则的配置信息 |
|
举例 |
Deleted security rule { UUID: 536be81d-413e-420d-8c5f-8075b11affa6 Security policy name: test5 Direction: egress IPv4 prefix: 4.2.2.0/24 Protocol type: ICMP Type: 1 Code: 2 }. |
|
日志说明 |
用户进行了删除安全规则的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The specified resource doesn't exist：指定的资源不存在 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
AUTH_VCENTER_OP |
|
日志内容 |
Authenticated with vCenter.. |
|
参数解释 |
无 |
|
举例 |
Authenticated with vCenter. |
|
日志说明 |
用户进行了连接并认证vCenter服务器的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Failed to connect to the vCenter：vCenter连接失败 · The vCenter has connected to another domain：vCenter已与其他计算域建立连接 · Invalid IP address：无效的IP地址 · The domain ID is required：未指定计算域ID · The domain can't connect to the vCenter：创建的计算域无法连接vCenter · The domain doesn't exist：计算域不存在 · The vCenter username cannot exceed 255 characters：登录vCenter的用户名最长255个字符 · The vCenter password cannot exceed 255 characters：登录vCenter的密码最长255个字符 · The vCenter name cannot exceed 255 characters：vCenter名称最长255个字符 · Domains of this type cannot connect to the vCenter：该类型的计算域不支持连接vCenter · The domain type is not vCenter：计算域的类型不是vCenter · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DISCONNECT_VCENTER_OP |
|
日志内容 |
Disconnected with vCenter. |
|
参数解释 |
无 |
|
举例 |
Disconnected with vCenter. |
|
日志说明 |
用户进行了断开vCenter连接的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · The specified resource doesn't exist：指定的资源不存在 · Failed to connect to the vCenter：vCenter连接失败 · Configuration recovery is in progress：配置恢复未完成 · Cannot delete the vCenter because it has connected to a domain：vCenter已与计算域建立连接，不允许删除 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPLOAD_VIB_OP |
|
日志内容 |
Uploaded vib $1. |
|
参数解释 |
$1：vib文件名称 |
|
举例 |
Uploaded vib s1020v_esx6.0.0-3.1.1.11.1_amd64.zip |
|
日志说明 |
用户进行了添加vib文件的操作 |
|
失败原因 |
You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_VIB_OP |
|
日志内容 |
Deleted vib $1. |
|
参数解释 |
$1：vib文件的UUID |
|
举例 |
Deleted vib 501172da-2514-3013-9a7e-5fb1f75d6090 |
|
日志说明 |
用户进行了删除vib文件的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Failed to delete the installation file：删除安装文件失败 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The specified resource doesn't exist：指定的资源不存在 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
INSTALL_VFE_OP |
|
日志内容 |
Installed VFE |
|
参数解释 |
无 |
|
举例 |
Installed VFE |
|
日志说明 |
用户进行了安装vSwitch版本的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Failed to connect to the vCenter：vCenter连接失败 · Installation failed：安装失败 · Failed to get the installation file：获取安装文件失败 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_VFE_OP |
|
日志内容 |
Updated VFE $1. |
|
参数解释 |
$1：vSwitch版本信息 |
|
举例 |
Updated VFE 1.0-1.001.55.D002. |
|
日志说明 |
用户进行了更新主机vSwitch版本的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Update failed：更新失败 · Failed to get the installation file：获取安装文件失败 · Versions not match：vSwitch版本与主机的EXSi版本不匹配 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UNINSTALL_VFE_OP |
|
日志内容 |
Uninstalled VFE. |
|
参数解释 |
无 |
|
举例 |
Uninstalled VFE. |
|
日志说明 |
用户进行了卸载主机vSwitch版本的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · Uninstallation failed：卸载失败 · Connection to the vCenter is not established：vCenter未连接 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_DOMAIN_OP |
|
日志内容 |
Created domain "$1". |
|
参数解释 |
$1：计算域的名称 |
|
举例 |
Created domain "domain01". |
|
日志说明 |
用户进行了创建计算域的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The domain name is required：未指定计算域名字 · Invalid domain type：无效的计算域类型 · The domain UUID is already used：计算域的UUID已存在 · Domains created in bulk cannot use the same UUID：批量创建的计算域的UUID存在重复 · The bridge name of the VDS cannot exceed 15 characters：VDS的Bridge名称最长15个字符 · The VXLAN tunnel name of the VDS cannot exceed 15 characters：VDS的VXLAN隧道口名称最长15个字符 · The domain name is already used：计算域名字已存在 · The host doesn't exist：操作失败，主机不存在 · The VDS doesn't exist：VDS不存在 · The domain name cannot exceed 255 characters：计算域名称最长255个字符 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_DOMAIN_OP |
|
日志内容 |
Updated domain "$1". |
|
参数解释 |
$1：计算域的名称 |
|
举例 |
Updated domain "domain01". |
|
日志说明 |
用户进行了修改计算域的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The domain ID is required：未指定计算域ID · The domain name is required：未指定计算域名字 · The specified resource doesn't exist：指定的资源不存在 · The host doesn't exist：操作失败，主机不存在 · Invalid domain type：无效的计算域类型 · The domain name is already used：计算域名字已存在 · Can't unbind the default VDS from the default domain：不能解除缺省VDS和缺省计算域的绑定关系 · Can't unbind the VDS from the domain because online hosts exist：存在上线主机，不能解绑VDS · The VDS doesn't exist：VDS不存在 · Can't unbind the VDS from the domain because the VDS has hosts：VDS下存在主机，不允许解绑VDS · The domain name cannot exceed 255 characters：计算域名称最长255个字符 · Cannot modify the name of the default domain：不允许修改缺省计算域名称 · The bridge name of the VDS cannot exceed 15 characters：VDS的Bridge名称最长15个字符 · The VXLAN tunnel name of the VDS cannot exceed 15 characters：VDS的VXLAN隧道口名称最长15个字符 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_DOMAIN_OP |
|
日志内容 |
Deleted domain "$1". |
|
参数解释 |
$1：计算域的名称 |
|
举例 |
Deleted domain "domain01". |
|
日志说明 |
用户进行了删除计算域的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · Failed to delete the domain：删除计算域失败 · Can't delete the default domain：不允许删除缺省计算域 · Can't delete the domain because it has been bound to VDS：计算域已关联VDS，不能被删除 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_VPORT_OP |
|
日志内容 |
Created vPort "Name: $1, IPv4: $2, IPv6: $3, MAC: $4". |
|
参数解释 |
$1：虚拟端口的名称 $2：虚拟端口的IPv4地址 $3：虚拟端口的IPv6地址 $4：虚拟端口的MAC地址 |
|
举例 |
Created vPort "Name: tap1, IPv4:100.1.1, IPv6: 150:1:ABCD, MAC: 00:01:00:01:10:00". |
|
日志说明 |
用户进行了创建虚拟端口的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · Invalid tenant ID：无效的租户ID · The network doesn’t exist：虚拟网络不存在 · Ports created in bulk cannot use the same ID：批量创建的虚拟端口的ID存在重复 · Duplicate port ID：虚拟端口ID重复 · The network ID is required：未指定虚拟网络ID · Invalid port group ID：无效的端口组ID · The port group and the port don’t reside on the same network：端口组所在网络和虚拟端口所在网络不一致 · The default uplink port policy can’t be used as the port policy：端口策略不能使用缺省上行口策略 · The specified QoS policy doesn't exist：指定的QoS策略不存在 · Invalid port security policy UUID：无效的端口安全策略UUID · The MAC address is already used by another port：端口MAC地址冲突 · The port and the gateway can't use the same IP address：端口IP地址和网关IP地址冲突 · Neither the MAC address nor the IP address is configured：未配置端口IP地址和MAC地址 · The IP address is already used by another port：该IP地址已被其他端口占用 · The port IP address must belong to an existing subnet：未找到IP地址对应的子网 · The IP address must belong to the specified subnet：IP地址不在子网内 · The subnet must belong to the specified network：子网不在指定的虚拟链路层网络内 · The domain doesn't exist：计算域不存在 · The mirror direction is required：未指定镜像方向 · The mirror type is required：未指定镜像类型 · Invalid mirror direction：无效的镜像方向 · Invalid mirror type：无效的镜像类型 · Invalid mirror remote IP：无效的镜像远端IP · The mirror remote IP is required：镜像远端IP不准确 · The length of the description is out of range：描述的长度超出范围 · The VLAN ID must be an integer in the range of 1 to 4094：VLAN ID必须为1～4094的整数 · Invalid flooding domain：无效的泛洪域 · Invalid APP cluster VIP：无效的应用集群虚IP · The APP cluster VIP and the vPort don't reside on the same network：应用集群虚IP所在网络和虚拟端口所在网络不一致 · The flooding domain and the vPort don't reside on the same network：泛洪域所在网络和虚拟端口所在网络不一致 · The vPort can be bound to a maximum of 10 flooding domains：vPort最多只能绑定10个泛洪域 · The specified subnet doesn't exist：指定的虚拟子网不存在 · Invalid IP address：无效的IP地址 · The host name cannot exceed 255 characters.：主机名最长255个字符 · APP cluster VIPs bound to the same vPort must belong to the same subnet：同一个虚拟端口上绑定的应用集群虚IP必须属于同一个子网 · The subnet to which the vPort belongs must be bound to a vRouter because the vPort has been bound to a routing table：vPort已绑定路由表时，vPort所在的子网必须绑定vRouter · The subnets of the flooding domains bound to the same vPort can't overlap with each other：同一虚拟端口下的不同泛洪域的IP网段不能相互重叠 · The specified resource doesn't exist：指定的资源不存在 · The MAC address conflicts with the gateway MAC address， reserved gateway MAC address or device group MAC：MAC地址与网关MAC地址、保留的网关MAC地址或者设备组的MAC地址冲突 · Invalid MAC address：无效的MAC地址 · The vPort name cannot exceed 255 characters：虚拟端口名称最长255个字符 · Operation failed. The security policy rule failed to take effect because of insufficient hardware resources：操作失败，硬件资源不足导致安全策略规则无法生效 · The specified tenant doesn't exist：指定的租户不存在 · The extend_dhcp_options field is invalid：无效的extend_dhcp_options · The value of the opt_name field is required：未指定DHCP选项名称 · The value of the opt_name field is invalid：无效的DHCP选项名称 · The value of the opt_value field is required：未指定DHCP选项值 · The value of the server-ip-address DHCP option is invalid：DHCP选项server-ip-address的选项值无效 · The value of the tftp-server DHCP option cannot exceed 63 characters：DHCP选项tftp-server的选项值最长63个字符 · The value of the bootfile-name DHCP option cannot exceed 127 characters：DHCP选项bootfile-name的选项值最长127个字符 · The values of the opt_name fields cannot be the same：DHCP选项名称不能重复 · The number of NTP server addresses cannot exceed 63：NTP服务器地址个数不能超过63个 · The NTP server address is invalid：无效的NTP服务器地址 · Duplicated NTP server addresses exist：NTP服务器地址列表中存在冲突的地址 · The fixed_ips field is required：fixed_ips不能为空 · The IP address of a vPort can be null only when the vPort resides on an external network or the subnet to which the vPort belongs is enabled with DHCP：仅当虚拟端口所属网络为外部网络或其所属子网使能DHCP功能时，端口IP地址才允许为空 · The vPort cannot have duplicated IP addresses：该虚拟端口的多个IP地址不能重复 · The vPort type is invalid：无效的虚拟端口类型 · You cannot delete the gateway vPort：网关类型虚拟端口不允许删除 · The value of the device owner parameter for LB vPorts must be neutron:LOADBALANCER or neutron:LOADBALANCERV2：该LB类型虚拟端口对应的device_owner必须配置为neutron:LOADBALANCER或neutron:LOADBALANCERV2 · The vPort type and the value of the device owner parameter do not match：虚拟端口的类型与设备拥有者的类型不匹配 · IP addresses in the subnet to which the vPort belongs are used up：该虚拟端口所属子网的IP地址已分配完 · Unknown error：未知错误 · vPorts do not support directly connected external networks：虚拟端口不支持独享型外部网络 · The value of the port_security_enabled is invalid：port_security_enabled参数非法 · A port group cannot be bound to a security policy when it contains port security disabled vPorts：虚拟端口未开启端口安全时，不允许该端口所属的端口组绑定安全策略 · A vPort with port security disabled cannot be bound to a security policy：虚拟端口未开启端口安全时，不允许绑定安全策略 · A vPort with port security disabled cannot be configured with allowed address pairs：虚拟端口未开启端口安全时，不允许配置可用地址对 · You have no privilege to perform this operation：用户无权限执行此操作 · The MAC address cannot contain all zeros or all Fs：MAC地址不能为全0或全F · Do not specify the port_isolated field when you create a vPort：创建虚拟端口时，port_isolated字段不允许携带 · A vPort name cannot start with "gateway"：虚拟端口名称不能以“gateway”开头 · Please enter an IP address for the external network vPort：外网虚拟端口IP不能为空Do not specify the port_isolated field when you create a vPort：创建虚拟端口时，port_isolated字段不允许携带 · You cannot bind a vPort to a subnet for primary IP allocation in an external network：虚拟端口不允许绑定外部网络下主IP所在子网 · The external subnet where the specified IP address resides has been bound to an NQA profile. You cannot assign the IP address to a vPort：指定IP地址所在的外网子网已关联NQA策略，无法绑定至虚拟端口 · Failed to connect to (hosts or access devices). Host or access device IPs: {IP addresses}：(主机/接入设备){IP地址集合}连接失败 · The latest links are invalid or no links exist on the netoverlay hosts found by names of (hosts or access devices)：(主机/接入设备)名称匹配的Netoverlay主机中的最新链路无效或者不存在 · No device exists at either end or both ends of the latest links on the netoverlay hosts found by names of (hosts or access devices)：(主机/接入设备)名称匹配的Netoverlay主机中的最新链路对应的设备不存在 · No device exists at either end or both ends of the links found by names of (hosts or access devices)：(主机/接入设备)名称匹配的链路对应的设备不存在 · The interfaces of some links found by names of (hosts or access devices) are not AC interfaces：(主机/接入设备)名称对应的链路非AC口 · The destination host name for the migrating_to parameter cannot exceed 255 characters：migrating_to参数最长255个字符 · Invalid allowed address pair：无效的可用地址对 · Invalid running state：无效的运行状态 · The value for the binding:profile:cvk_host parameter can contain up to 255 characters：binding:profile:cvk_host最长255个字符 · The value for the binding:profile:esxi_host parameter can contain up to 255 characters：binding:profile:esxi_host最长255个字符 · You cannot set both the binding:profile:cvk_host and binding:profile:esxi_host parameters：不能同时设置binding:profile:cvk_host与binding:profile:esxi_host · The specified IP address has been configured as a protocol IP：虚拟端口IP已被子网协议IP使用 · Failed to create the vPort. A vPort cannot be assigned to an external network if it has extended SNAT IP addresses. To create the vPort, remove its extended SNAT IP addresses or specify an internal network for it：若指定的虚拟端口已配置扩展SNAT IP地址，则该端口必须属于外部网络 · The extended SNAT IP addresses must belong to an existing subnet：未找到扩展SNAT IP地址对应的子网 · You cannot configure extended SNAT IP addresses on the vPort, because the external network to which the vPort belongs is segmented：外部网络已开启网络分段，不允许配置扩展SNAT IP地址 · You cannot configure extended SNAT IP addresses for a vPort if the vPort does not have an IPv4 address：虚拟端口没有IPv4的地址时，不允许配置扩展SNAT IP地址 · You cannot specify an extended SNAT IP address as an IPv6 address：扩展SNAT IP地址不支持配置IPv6版本 · You cannot specify an extended SNAT IP address as the vPort IP address：扩展SNAT IP地址不能与虚拟端口IP地址冲突 · Make sure the extended SNAT IP addresses are not in the subnet of the primary IP address specified for the vNetwork：扩展SNAT IP地址不能在主IP所在子网内 · You cannot bind a vPort to a subnet for primary IP allocation in an external network：虚拟端口不允许绑定外部网络下主IP所在子网 · Cannot delete vPorts created on VMM：不允许删除来源为VMM的虚拟端口 · You cannot apply a QoS policy to this vPort, because the vNetwork of this vPort has been specified for a PVLAN mapping：当虚拟端口所属的虚拟链路层网络已被PVLAN映射绑定，不允许绑定QoS策略 · The flooding domain must belong to the same tenant as the current user：泛洪域所属的租户与当前用户所绑定的租户不一致 · The vNetwork must belong to the same tenant as the current user：虚拟链路层网络所属的租户与当前用户所绑定的租户不一致 · The security policy must belong to the same tenant as the current user：安全策略所属的租户与当前用户所绑定的租户不一致 · The port group must belong to the same tenant as the current user：端口组所属的租户与当前用户所绑定的租户不一致 · A parent port and its subports must be configured with the same QoS profile：父端口和其子端口必须配置相同类型的QoS策略 · The IP address conflicts with the subnet address：IP地址和子网地址冲突 · The vPort IP address conflicts with the subnet broadcast address：虚拟端口IP地址与子网广播IP地址冲突 · Resource application or rollback failed, internal unknown error：资源申请或回滚失败，内部未知错误 · The（resource）does not exist or the resources are insufficient：（资源）不存在或资源不足 · The（resource）does not exist or the resources are insufficient, device group name（name）：（资源）不存在或资源不足，设备组名称（名称） · The （resource） does not exist or the resources are insufficient, resource access template name （name）：（资源）不存在或资源不足，资源接入模板名称（名称） · The value of binding:profile:agent_binary is invalid：binding:profile:agent_binary的值无效 |
|
关键字 |
UPDATE_VPORT_OP |
|
日志内容 |
Updated vPort "Name: $1, IPv4: $2, IPv6: $3, MAC: $4". |
|
参数解释 |
$1：虚拟端口的名称 $2：虚拟端口的IPv4地址 $3：虚拟端口的IPv6地址 $4：虚拟端口的MAC地址 |
|
举例 |
Updated vPort "Name: tap1, IPv4:100.1.1, IPv6: 150:1:ABCD, MAC: 00:01:00:01:10:00". |
|
日志说明 |
用户进行了修改虚拟端口的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The parameter (parameters) can't be modified：(parameters)参数不允许被修改 · Invalid port group ID：无效的端口组ID · The port group and the port don’t reside on the same network：端口组所在网络和虚拟端口所在网络不一致 · The default uplink port policy can’t be used as the port policy：端口策略不能使用缺省上行口策略 · The specified QoS policy doesn't exist：指定的QoS策略不存在 · Invalid port security policy UUID：无效的端口安全策略UUID · The mirror direction is required：未指定镜像方向 · The mirror type is required：未指定镜像类型 · Invalid mirror direction：无效的镜像方向 · Invalid mirror type：无效的镜像类型 · Invalid mirror remote IP：无效的镜像远端IP · The mirror remote IP is required：镜像远端IP不准确 · The port IP address must belong to an existing subnet：未找到IP地址对应的子网 · The IP address is already used by another port：该IP地址已被其他端口占用 · The port and the gateway can’t use the same IP address：端口IP地址和网关IP地址冲突 · Can’t update the MAC address：不能更新MAC地址 · The IP address must belong to the specified subnet：IP地址不在子网内 · The subnet must belong to the specified network：子网不在指定的虚拟链路层网络内 · Unknown error：未知错误 · The vPort is created through vCenter and the port group can't be modified：该端口由vCenter创建，不能通过本操作修改端口组 · The network doesn't exist：虚拟网络不存在 · The specified subnet doesn't exist：指定的虚拟子网不存在 · The specified resource doesn't exist：指定的资源不存在 · The length of the description is out of range：描述的长度超出范围 · Invalid APP cluster VIP：无效的应用集群虚IP · The APP cluster VIP and the vPort don't reside on the same network：应用集群虚IP所在网络和虚拟端口所在网络不一致 · The flooding domain and the vPort don't reside on the same network：泛洪域所在网络和虚拟端口所在网络不一致 · The vPort can be bound to a maximum of 10 flooding domains：vPort最多只能绑定10个泛洪域 · phy type auto created vPorts does not support editing IP address：phy类型南向自动创建端口不支持修改IP地址 · Invalid IP address：无效的IP地址 · The flooding domain doesn't exist：泛洪域不存在 · The host name cannot exceed 255 characters.：主机名最长255个字符 · APP cluster VIPs bound to the same vPort must belong to the same subnet：同一个虚拟端口上绑定的应用集群虚IP必须属于同一个子网 · The subnet to which the vPort belongs must be bound to a vRouter because the vPort has been bound to a routing table：vPort已绑定路由表时，vPort所在的子网必须绑定vRouter · The MAC address conflicts with the gateway MAC address， reserved gateway MAC address or device group MAC：MAC地址与网关MAC地址、保留的网关MAC地址或者设备组的MAC地址冲突 · Invalid MAC address：无效的MAC地址 · The vPort name cannot exceed 255 characters：虚拟端口名称最长255个字符 · Operation failed. The security policy rule failed to take effect because of insufficient hardware resources：操作失败，硬件资源不足导致安全策略规则无法生效 · The extend_dhcp_options field is invalid：无效的extend_dhcp_options · The value of the opt_name field is required：未指定DHCP选项名称 · The value of the opt_name field is invalid：无效的DHCP选项名称 · The value of the opt_value field is required：未指定DHCP选项值 · The value of the server-ip-address DHCP option is invalid：DHCP选项server-ip-address的选项值无效 · The value of the tftp-server DHCP option cannot exceed 63 characters：DHCP选项tftp-server的选项值最长63个字符 · The value of the bootfile-name DHCP option cannot exceed 127 characters：DHCP选项bootfile-name的选项值最长127个字符 · The values of the opt_name fields cannot be the same：DHCP选项名称不能重复 · The number of NTP server addresses cannot exceed 63：NTP服务器地址个数不能超过63个 · The NTP server address is invalid：无效的NTP服务器地址 · Duplicated NTP server addresses exist：NTP服务器地址列表中存在冲突的地址 · The fixed_ips field is required：fixed_ips不能为空 · The IP address of a vPort can be null only when the vPort resides on an external network or the subnet to which the vPort belongs is enabled with DHCP：仅当虚拟端口所属网络为外部网络或其所属子网使能DHCP功能时，端口IP地址才允许为空 · The vPort cannot have duplicated IP addresses：该虚拟端口的多个IP地址不能重复 · The vPort type is invalid：无效的虚拟端口类型 · The vPort type and the value of the device owner parameter do not match：虚拟端口的类型与设备拥有者的类型不匹配 · IP addresses in the subnet to which the vPort belongs are used up：该虚拟端口所属子网的IP地址已分配完 · vPorts do not support directly connected external networks：虚拟端口不支持独享型外部网络 · The value of the port_security_enabled is invalid：port_security_enabled参数非法 · A port group cannot be bound to a security policy when it contains port security disabled vPorts：虚拟端口未开启端口安全时，不允许该端口所属的端口组绑定安全策略 · A vPort with port security disabled cannot be bound to a security policy：虚拟端口未开启端口安全时，不允许绑定安全策略 · A vPort with port security disabled cannot be configured with allowed address pairs：虚拟端口未开启端口安全时，不允许配置可用地址对 · You have no privilege to perform this operation：用户无权限执行此操作 · The MAC address cannot contain all zeros or all Fs：MAC地址不能为全0或全F · A vPort name cannot start with "gateway"：虚拟端口名称不能以“gateway”开头 · Please enter an IP address for the external network vPort：外网虚拟端口IP不能为空 · Only OVS vPorts can be blocked：仅ovs类型的虚拟端口支持开启端口封堵 · You cannot bind a vPort to a subnet for primary IP allocation in an external network：虚拟端口不允许绑定外部网络下主IP所在子网 · The external subnet where the specified IP address resides has been bound to an NQA profile. You cannot assign the IP address to a vPort：指定IP地址所在的外网子网已关联NQA策略，无法绑定至虚拟端口 · Failed to edit the IP address for the vPort, because the new IP address is in a network bound to the context in another service chain：虚拟端口修改IP地址失败，该修改会导致虚拟端口所在特征组的服务链与其他服务链网段重叠 · The value for the fw_enabled parameter is invalid：无效的使能防火墙参数 · The vRouter-attached gateway members enable the third-party firewall option. Please enable or disable the firewall option across all IP addresses or subnets in the vRouter-attached external network if the egress of the external network is the firewall or border device, respectively：虚拟路由器绑定了第三方防火墙开启的设备组，该虚拟路由器绑定外部网络下的外网子网防火墙设置需要和虚拟路由器上的外网出口设置一致 · Failed to connect to (hosts or access devices). Host or access device IPs: {IP addresses}：(主机/接入设备){IP地址集合}连接失败 · The latest links are invalid or no links exist on the netoverlay hosts found by names of (hosts or access devices)：(主机/接入设备)名称匹配的Netoverlay主机中的最新链路无效或者不存在 · No device exists at either end or both ends of the latest links on the netoverlay hosts found by names of (hosts or access devices)：(主机/接入设备)名称匹配的Netoverlay主机中的最新链路对应的设备不存在 · No device exists at either end or both ends of the links found by names of (hosts or access devices)：(主机/接入设备)名称匹配的链路对应的设备不存在 · The interfaces of some links found by names of (hosts or access devices) are not AC interfaces：(主机/接入设备)名称对应的链路非AC口 · The destination host name for the migrating_to parameter cannot exceed 255 characters：migrating_to参数最长255个字符 · You cannot edit or delete the cloud region name：云区域名称不允许修改或删除 · Invalid allowed address pair：无效的可用地址对 · You cannot edit the host ID or VLAN of a subport, because the transparent mode is enabled：透传模式开启时，子端口不允许修改host_id或者VLAN · Invalid running state：无效的运行状态 · The value for the binding:profile:cvk_host parameter can contain up to 255 characters：binding:profile:cvk_host最长255个字符 · The value for the binding:profile:esxi_host parameter can contain up to 255 characters：binding:profile:esxi_host最长255个字符 · You cannot set both the binding:profile:cvk_host and binding:profile:esxi_host parameters：不能同时设置binding:profile:cvk_host与binding:profile:esxi_host · The specified IP address has been configured as a protocol IP：虚拟端口IP已被子网协议IP使用 · You cannot specify an extended SNAT IP address as an IPv6 address：扩展SNAT IP地址不支持配置IPv6版本 · You cannot configure extended SNAT IP addresses on the vPort, because the external network to which the vPort belongs is segmented：外部网络已开启网络分段，不允许配置扩展SNAT IP地址 · You cannot specify an extended SNAT IP address as the vPort IP address：扩展SNAT IP地址不能与虚拟端口IP地址冲突 · You cannot specify the vPort IP address as extended SNAT IP address：虚拟端口IP地址不能与扩展SNAT IP地址冲突 · Make sure the extended SNAT IP addresses have not been used in the external network：相同外部网络下，扩展SNAT IP地址不能与已经存在的扩展SNAT IP地址或虚拟端口IP地址冲突 · You cannot specify an extended SNAT IP address as a gateway IP address in the same external network：扩展SNAT IP地址不能与子网网关IP地址冲突 · You cannot specify an extended SNAT IP address as a floating IP address in the same external network：扩展SNAT IP地址不能与浮动IP冲突 · Make sure the extended SNAT IP addresses are not in the subnet of the primary IP address specified for the vNetwork：扩展SNAT IP地址不能在主IP所在子网内 · You cannot configure extended SNAT IP addresses for a vPort if the vPort does not have an IPv4 address：虚拟端口没有IPv4的地址时，不允许配置扩展SNAT IP地址 · The extended SNAT IP addresses must belong to an existing subnet：未找到扩展SNAT IP地址对应的子网 · The vRouter does not contain information about the network segment associated with the subnet to which the new IP address belongs：虚拟路由器中不存在该IP版本子网对应的网络分段 · The external network specified for the vRouter is not segmented. You can bind only one IPv4 subnet and one IPv6 subnet to the vRouter：指定的外部网络未配置网络分段时，虚拟路由器只允许绑定一个IPv4和IPv6子网 · The vRouter is bound to multiple IPv4 and IPv6 external subnets. The network segments to which external subnets of the same IP version are bound cannot be bound to the same border gateway：虚拟路由器绑定多个的外网子网时，同IP版本外网子网对应的出口网关不能相同 · The external subnet is bound to the vRouter：外网子网已被虚拟路由器绑定 · The border gateways to the IPv4 and IPv6 external subnets are located on the same interface. You must configure them with the same segment ID：IPv4外网子网和IPv6外网子网的出口网关相同时，Segment ID必须相同 · The subnet overlaps with another subnet：子网与其他的子网重叠 · The vRouter context or external network vPort context has been used in a service chain：指定的虚拟路由器或外部网络虚拟端口已被服务链使用 · You cannot bind a vRouter to a vPort created by using a subnet for primary IP allocation：虚拟路由器不支持绑定使用主IP所在子网创建的虚拟端口 · The source IP address of a route entry on the vRouter cannot be within any external subnet on the vRouter：源IP地址不允许在同一虚拟路由器下外部网络的子网网段范围内 · You cannot bind the external subnet to the vRouter. The gateway address for the subnet is the next hop address of a route entry bound to the vRouter. You cannot bind them when the external subnet and that route entry are each bound to an NQA profile：虚拟路由器的路由表项的下一跳IP地址与外网子网网关IP相同，且路由表项已绑定NQA策略，则虚拟路由器不允许绑定配置了NQA策略的外部网络 · The vRouter-attached gateway members disable the third-party firewall option and use hairpin firewall deployment. Please make sure the firewall is enabled or disabled across all IP addresses and subnets in the external network：虚拟路由器绑定了第三方防火墙关闭且防火墙接入模式是旁挂的设备组，同外部网络下的外网子网过墙行为必须一致 · A vRouter cannot be bound to multiple IPv6 external network vPorts in the same network：虚拟路由器绑定多个IPv6外网虚拟端口时，这些端口所属的外部网络不能相同 · Subnets in the external network do not have sufficient IP addresses for allocation：外部网络下的子网可分配IP不足 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · The external network egress IP has been bound to another vRouter. To bind the current vRouter to the external network egress IP, you must make sure the current vRouter has exactly the same external subnet bindings as that vRouter：虚拟路由器绑定多个外网子网，且多个虚拟路由器共享外网IP时，必须同时共享所有外网IP · Failed to bind the router to the external network, because the external subnet does not have enough assignable IP addresses：绑定外网失败，外网子网没有可分配的IP地址 · Make sure all vRouters that use this sharing IP are bound to the same edge device for external network access：共享IP绑定的所有虚拟路由器的外网出口设备必须相同 · Invalid external IP binding. An external IP address has been bound to a minimum of one vRouter. To share that external IP address, the vRouters must be assigned the same service resources：该外网出口IP已被其他虚拟路由器绑定，如需共享，需确保共享该IP的所有虚拟路由器绑定相同的服务资源 · The external network egress IP has already been bound to a vRouter that uses different gateway resources from the current vRouter. Only vRouters that use the same gateway resources can share an external network egress IP：该外网出口IP已被其他虚拟路由器绑定，如需共享，需确保共享该IP的所有虚拟路由器绑定相同的网关资源 · Not enough addresses in subnets in network segment：网络分段内可分配IP不足 · You cannot remove the network segment, because it is used by multicast sources：指定的网络分段已被组播源使用，不允许解绑 · Failed to unbind the vRouter from the external network, because the vRouter and the external network (or a segment of the external network) have been bound to the same Layer 3 multicast network：解绑失败，L3组播使用了该虚拟路由器及其绑定的外部网络或网络分段 · You cannot bind the vRouter to an external network with a firewall specified as the edge device, because the external network has been bound to an MSDP peer：指定的外部网络已绑定MSDP对等体，不允许绑定外网出口设备为防火墙的虚拟路由器 · You cannot edit the IPv4 subnets or egress IPv4 address of the external network, because the default external vPort has extended SNAT IP addresses：默认外网端口已配置扩展SNAT IP地址，IPv4外网子网和外网出口IPv4地址不允许修改 · A vPort or application cluster VIP on the vRouter has been bound to a floating IP：该虚拟路由器下存在已绑定浮动IP的虚拟端口或应用集群虚IP · The vRouter to which the external network belongs is in a vRouter link, and a vPort on the peer vRouter of the vRouter link has been bound to the floating IP address of the external network：外部网络所属的虚拟路由器已建立虚拟路由器连接，且对端虚拟路由器下的虚拟端口已绑定了该外部网络的浮动IP · The external subnet has been bound to a context. Please access the context page to remove the binding first：该虚拟路由器的外网子网已关联流量特征组，请先前往流量特征组页面取消关联 · The context uses single gateway deployment mode. Make sure the associated vRouter is bound to one gateway member or external subnet：流量特征组为单出口模式时，关联的虚拟路由器必须绑定一个出口网关成员或一个外网子网 · The context uses primary/backup gateway deployment mode. Make sure the associated vRouter is bound to two gateway members or external subnets：流量特征组为主备出口模式时，关联的虚拟路由器必须绑定两个出口网关成员或两个外网子网 · The extranet IP is invalid：外网IP无效 · The IP address doesn't belong to the network：该IP地址不属于该网络 · The IP address doesn't belong to the subnet：指定的IP地址不属于该子网 · The extranet IP conflicts with a gateway IP：外网IP与网关IP冲突 · The extranet IP conflicts with the broadcast address of the subnet：外网IP地址和子网广播IP地址冲突 · The extranet IP conflicts with the subnet address：外网IP地址和子网地址冲突 · The extranet IP conflicts with a floating IP：外网IP与浮动IP冲突 · The external subnets of a vRouter cannot overlap with the networks manually specified for the vRouter link to which the vRouter belongs：外网子网网段不能与虚拟路由器所属的虚拟路由器连接的手动输入网段重叠 · Please make sure the firewall is enabled or disabled for both an external vPort and the vRouter bound to it：外网虚拟端口与所绑定的虚拟路由器过墙行为必须一致 · You cannot disable firewall for the vPort if the vPort is already bound to an external transit vRouter：虚拟端口已绑定EXTERNALTRANSIT类型虚拟路由器，不允许关闭防火墙开关 · You must enable or disable firewall for a vPort if the following conditions exist: The vPort is bound to an external transit vRouter. The type of the border gateway bound to the vRouter is border device：虚拟端口已绑定外网出口设备为边界设备的EXTERNALTRANSIT类型虚拟路由器，不允许防火墙开关为空 · You cannot bind a vPort to a subnet for primary IP allocation in an external network：虚拟端口不允许绑定外部网络下主IP所在子网 · You cannot apply a QoS policy to this vPort, because the vNetwork of this vPort has been specified for a PVLAN mapping：当虚拟端口所属的虚拟链路层网络已被PVLAN映射绑定，不允许绑定QoS策略 · The cluster VIP must belong to the same tenant as the current user：应用集群虚IP所属的租户与当前用户所绑定的租户不一致 · The flooding domain must belong to the same tenant as the current user：泛洪域所属的租户与当前用户所绑定的租户不一致 · The security policy must belong to the same tenant as the current user：安全策略所属的租户与当前用户所绑定的租户不一致 · The port group must belong to the same tenant as the current user：端口组所属的租户与当前用户所绑定的租户不一致 · The vPort-attached external network has been bound to MSDP peers. You cannot enable the firewall feature or use a firewall as the edge device to the external network：指定虚拟端口对应的外部网络已绑定MSDP对等体，不允许开启防火墙或不允许外网出口设备为防火墙 · You cannot specify an extended SNAT IP address as a gateway IP address in the same external network：扩展SNAT IP地址不能与子网网关IP地址冲突 · A parent port and its subports must be configured with the same QoS profile：父端口和其子端口必须配置相同类型的QoS策略 · The IP address conflicts with the subnet address：IP地址和子网地址冲突 · The vPort IP address conflicts with the subnet broadcast address：虚拟端口IP地址与子网广播IP地址冲突 · The external network egress IP is already bound to a vRouter. For vRouters to share this IP, make sure these vRouters use the same third-party firewall setting. You can configure this setting when you configure the device group associated with a gateway member of a border gateway bound to a vRouter：该外网出口IP已被其他虚拟路由器绑定，如需共享，需确保共享该IP的所有虚拟路由器绑定的出口网关对应的设备组第三方防火墙开关必须一致 · If multiple vRouters share an automatically created vPort, you cannot change the IP addresses of that vPort：当自动创建的外网虚拟端口被多个虚拟路由器绑定时，不允许修改其IP地址 · Resource application or rollback failed, internal unknown error：资源申请或回滚失败，内部未知错误 · The（resource）does not exist or the resources are insufficient：（资源）不存在或资源不足 · The（resource）does not exist or the resources are insufficient, device group name（name）：（资源）不存在或资源不足，设备组名称（名称） · The （resource） does not exist or the resources are insufficient, resource access template name （name）：（资源）不存在或资源不足，资源接入模板名称（名称） · The value of binding:profile:agent_binary is invalid：binding:profile:agent_binary的值无效 |
|
关键字 |
DELETE_VPORT_OP |
|
日志内容 |
Deleted vPort "Name: $1, IPv4: $2, IPv6: $3, MAC: $4". |
|
参数解释 |
$1：虚拟端口的名称 $2：虚拟端口的IPv4地址 $3：虚拟端口的IPv6地址 $4：虚拟端口的MAC地址 |
|
举例 |
Deleted vPort "Name: tap1, IPv4:100.1.1, IPv6: 150:1:ABCD, MAC: 00:01:00:01:10:00". |
|
日志说明 |
用户进行了删除虚拟端口的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · Can't delete the port because it is created by vCenter：vCenter创建的端口，不能删除 · Can't delete the auto created LB vPort：不允许删除自动创建的LB类型的vPort · The specified resource doesn't exist：指定的资源不存在 · You cannot delete the gateway vPort：网关类型虚拟端口不允许删除 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 · Failed to connect to (hosts or access devices). Host or access device IPs: {IP addresses}：(主机/接入设备){IP地址集合}连接失败 · The latest links are invalid or no links exist on the netoverlay hosts found by names of (hosts or access devices)：(主机/接入设备)名称匹配的Netoverlay主机中的最新链路无效或者不存在 · No device exists at either end or both ends of the latest links on the netoverlay hosts found by names of (hosts or access devices)：(主机/接入设备)名称匹配的Netoverlay主机中的最新链路对应的设备不存在 · No device exists at either end or both ends of the links found by names of (hosts or access devices)：(主机/接入设备)名称匹配的链路对应的设备不存在 · The interfaces of some links found by names of (hosts or access devices) are not AC interfaces：(主机/接入设备)名称对应的链路非AC口 · The destination host name for the migrating_to parameter cannot exceed 255 characters：migrating_to参数最长255个字符 · Can't delete the port because it has been bound to trunk：不允许删除已绑定端口中继的端口 · Cannot delete vPorts created on VMM：不允许删除来源为VMM的虚拟端口 · Resource application or rollback failed, internal unknown error：资源申请或回滚失败，内部未知错误 · The（resource）does not exist or the resources are insufficient：（资源）不存在或资源不足 · The（resource）does not exist or the resources are insufficient, device group name（name）：（资源）不存在或资源不足，设备组名称（名称） · The （resource） does not exist or the resources are insufficient, resource access template name （name）：（资源）不存在或资源不足，资源接入模板名称（名称） |
|
关键字 |
CREATE_ROUTERLINK_OP |
|
日志内容 |
Created router link "$1" |
|
参数解释 |
$1：虚拟路由器连接的名称 |
|
举例 |
Created router link "zn_routelink" |
|
日志说明 |
用户进行了创建虚拟路由器连接的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The vRouter link ID has already been used：虚拟路由器连接的ID已经存在 · vRouter links created in bulk cannot use the same ID：批量创建的虚拟路由器连接的ID存在重复 · The specified vRouter doesn't exist：指定的虚拟路由器不存在 · The specified vRouter IDs cannot be the same：本端和对端虚拟路由器的ID不能相同 · The vRouter link already exists：该虚拟路由器连接已经存在 · Both router_id1 and router_id2 are required：参数router_id1和router_id2都不能为空 · The subnet of vRouter1 overlaps with the subnet of vRouter2：虚拟路由器1和虚拟路由器2的子网网段重叠 · The vRouter link name cannot exceed 255 characters：虚拟路由器连接名称最长255个字符 · Unknown error：未知错误 · Cannot create distributed vRouter links in Network cloud feature：网络云场景下不允许创建分布式虚拟路由器连接 · You have no privilege to perform this operation：用户无权限执行此操作 · Cannot create vRouter links when the Network Cloud feature is enabled：网络云场景开启时，不允许创建虚拟路由器连接 · You cannot create a vRouter link of the normal, PBR, or NBAC type, because the local or remote vRouter on the link has been bound to both a centralized vNetwork and an IPv6 subnet：当虚拟路由器连接为Normal、PBR或NBAC类型时，本端和对端虚拟路由器下不能同时绑定集中式虚拟链路层网络和IPv6子网 · Duplicated CIDRs exist in local or remote CIDRs：本端网段/远端网段中存在网段重叠 · Invalid subnet mask：掩码位非法 · Invalid IP address：无效的IP地址 · Local CIDRs cannot overlap with remote subnets：本端网段和对端路由器下的所有子网不允许重叠 · Local CIDRs cannot overlap with peer CIDRs：本端网段和对端网段不允许重叠 · You cannot specify local or remote subnets for the vRouter link, because the local or remote vRouter is configured with CIDR addresses：指定的本端或对端虚拟路由器已经配置了CIDR，不允许为该虚拟路由器连接指定本端或远端子网 · Invalid CIDR：无效的子网网段 · You cannot create a vRouter link between these two vRouters. This is because they have been bound to the same external network and either or both of them have been bound to a shared gateway：当虚拟路由器连接两端的虚拟路由器绑定同一个外部网络，且其中一个以上的虚拟路由器已绑定共享网关时，不允许创建虚拟路由器连接 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · An MDC north-south vRouter link (with islocalAll set to false and isPeerAll set to true) and an MDC east-west vRouter link (with both islocalAll and isPeerAll set to false) are created on the tenant. Make sure the routes to an external subnet of the south-north vRouter link and a remote CIDR of the east-west vRouter link do not overlap：当相同租户同时创建MDC南北向业务（指定源）和东西向业务（指定源和目的）时，南北向的多数据中心外网网段与东西向的对端网段明细路由不能相同 · You cannot specify the same pair of vRouters in both of the following settings:1.Inter-tenant or inter-vRouter EPG policy whose method for service chain traffic routing is static route.2.vRouter link of the normal type：两个虚拟路由器不能同时在以下两种场景中使用：1、服务链引流方式为静态路由，创建跨租户或者跨虚拟路由器EPG间策略。2、创建Normal的虚拟路由器连接 · The static route issued by the application policy that uses static route-based service chain traffic routing conflicts with the routes learned by the created vRouter links：引流方式为静态路由的应用策略下发的静态路由和创建虚拟路由器连接学习到的路由存在冲突 · Resource application or rollback failed, internal unknown error：资源申请或回滚失败，内部未知错误 · The（resource）does not exist or the resources are insufficient：（资源）不存在或资源不足 · The（resource）does not exist or the resources are insufficient, device group name（name）：（资源）不存在或资源不足，设备组名称（名称） · The （resource） does not exist or the resources are insufficient, resource access template name （name）：（资源）不存在或资源不足，资源接入模板名称（名称） · vRouter link creation failed, because: 1. The local or remote vRouter is enabled with firewall. 2. The firewall-enabled vRouter is bound to a service-leaf firewall resource associated with a resource access template that has insufficient addresses：防火墙开关开启侧的虚拟路由器绑定的Service Leaf服务资源所关联的资源接入模板地址池资源不足 · vRouter link creation failed, because: 1. The local or remote vRouter is enabled with firewall. 2. The firewall-enabled vRouter is bound to a service-leaf firewall resource associated with a resource access template that has insufficient VLAN IDs：防火墙开关开启侧的虚拟路由器绑定的Service Leaf服务资源所关联的资源接入模板VLAN池资源不足 · vRouter link creation failed, because: 1. The local or remote vRouter is enabled with firewall. 2. The firewall-enabled vRouter is bound to a service-leaf firewall resource associated with a resource access template that has insufficient VXLAN IDs：防火墙开关开启侧的虚拟路由器绑定的Service Leaf服务资源所关联的资源接入模板VXLAN池资源不足 |
|
关键字 |
UPDATE_ROUTERLINK_OP |
|
日志内容 |
Updated router link "$1" |
|
参数解释 |
$1：虚拟路由器连接的名称 |
|
举例 |
Updated router link "zn_routelink" |
|
日志说明 |
用户进行了修改虚拟路由器连接的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The vRouter link ID is required：未指定虚拟路由器连接的ID · The specified resource doesn't exist：指定的资源不存在 · The vRouter link name cannot exceed 255 characters：虚拟路由器连接名称最长255个字符 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 · Duplicated CIDRs exist in local or remote CIDRs：本端网段/远端网段中存在网段重叠 · Invalid subnet mask：掩码位非法 · Invalid IP address：无效的IP地址 · Local CIDRs cannot overlap with remote subnets：本端网段和对端路由器下的所有子网不允许重叠 · Local CIDRs cannot overlap with peer CIDRs：本端网段和对端网段不允许重叠 · You cannot specify local or remote subnets for the vRouter link, because the local or remote vRouter is configured with CIDR addresses：指定的本端或对端虚拟路由器已经配置了CIDR，不允许为该虚拟路由器连接指定本端或远端子网 · Invalid CIDR：无效的子网网段 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · An MDC north-south vRouter link (with islocalAll set to false and isPeerAll set to true) and an MDC east-west vRouter link (with both islocalAll and isPeerAll set to false) are created on the tenant. Make sure the routes to an external subnet of the south-north vRouter link and a remote CIDR of the east-west vRouter link do not overlap：当相同租户同时创建MDC南北向业务（指定源）和东西向业务（指定源和目的）时，南北向的多数据中心外网网段与东西向的对端网段明细路由不能相同 · The static route issued by the application policy that uses static route-based service chain traffic routing conflicts with the routes learned by the created vRouter links：引流方式为静态路由的应用策略下发的静态路由和创建虚拟路由器连接学习到的路由存在冲突 · Resource application or rollback failed, internal unknown error：资源申请或回滚失败，内部未知错误 · The（resource）does not exist or the resources are insufficient：（资源）不存在或资源不足 · The（resource）does not exist or the resources are insufficient, device group name（name）：（资源）不存在或资源不足，设备组名称（名称） · The （resource） does not exist or the resources are insufficient, resource access template name （name）：（资源）不存在或资源不足，资源接入模板名称（名称） · vRouter link creation failed, because: 1. The local or remote vRouter is enabled with firewall. 2. The firewall-enabled vRouter is bound to a service-leaf firewall resource associated with a resource access template that has insufficient addresses：防火墙开关开启侧的虚拟路由器绑定的Service Leaf服务资源所关联的资源接入模板地址池资源不足 |
|
关键字 |
DELETE_ROUTERLINK_OP |
|
日志内容 |
Deleted router link "$1" |
|
参数解释 |
$1：虚拟路由器连接的名称 |
|
举例 |
Deleted router link "zn_routelink" |
|
日志说明 |
用户进行了删除虚拟路由器连接的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The specified resource doesn't exist：指定的资源不存在 · A vPort on one vRouter of the vRouter link has been bound to the floating IP address of the external network bound to the other vRouter of the vRouter link：该虚拟路由器连接存在一端虚拟路由器下的虚拟端口绑定了对端虚拟路由器的外部网络浮动IP · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · Resource application or rollback failed, internal unknown error：资源申请或回滚失败，内部未知错误 · The（resource）does not exist or the resources are insufficient：（资源）不存在或资源不足 · The（resource）does not exist or the resources are insufficient, device group name（name）：（资源）不存在或资源不足，设备组名称（名称） · The （resource） does not exist or the resources are insufficient, resource access template name （name）：（资源）不存在或资源不足，资源接入模板名称（名称） |
|
关键字 |
CREATE_ROUTETABLE_OP |
|
日志内容 |
Created routing table "$1" |
|
参数解释 |
$1：路由表的名称 |
|
举例 |
Created routing table "zn_routetable" |
|
日志说明 |
用户进行了创建路由表的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The routing table already exists：此路由表已经存在 · Route tables created in bulk cannot use the same ID：批量创建的路由表的ID存在重复 · The router ID is required：未指定虚拟路由器ID · The router doesn't exist：虚拟路由器不存在 · The tenant ID of the routing table is different than the vRouter：路由表与虚拟路由器的租户ID不一致 · The tenant name of the routing table is different than the vRouter：路由表与虚拟路由器的租户名称不一致 · Failed to create the routing table because physical MAC address forwarding is disabled：实MAC转发模式未开启，无法创建路由表 · The routing table name cannot exceed 255 characters：路由表名称最长255个字符 · Can't specify a vRouter whose origin is PBR：不允许指定来源为PBR的虚拟路由器 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 · If an east-west transit vRouter link enabled with remote route advertisement shares one transit vRouter with a centralized VAS vRouter link, the following items cannot overlap：1. Destination subnets configured for the route entries on the local vRouter of the east-west transit vRouter link.2. CIDRs configured for the remote vRouter of the centralized VAS vRouter link：TRANSIT类型虚拟路由器分别与两台虚拟路由器建立VAS VPC互通和发布对端所有路由开启的东西向TRANSIT VPC互通，东西向TRANSIT VPC互通的本端虚拟路由器的路由表项目的网段不能与VAS VPC互通的对端虚拟路由器CIDR重叠 · Resource application or rollback failed, internal unknown error：资源申请或回滚失败，内部未知错误 · The（resource）does not exist or the resources are insufficient：（资源）不存在或资源不足 · The（resource）does not exist or the resources are insufficient, device group name（name）：（资源）不存在或资源不足，设备组名称（名称） · The （resource） does not exist or the resources are insufficient, resource access template name （name）：（资源）不存在或资源不足，资源接入模板名称（名称） |
|
关键字 |
UPDATE_ROUTETABLE_OP |
|
日志内容 |
Updated routing table "$1" |
|
参数解释 |
$1：路由表的名称 |
|
举例 |
Updated routing table "zn_routetable" |
|
日志说明 |
用户进行了修改路由表的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The specified resource doesn't exist：指定的资源不存在 · The route table id is required：未指定路由表的ID · The routing table name cannot exceed 255 characters：路由表名称最长255个字符 · The parameter (parameters) can’t be modified：(parameters)参数不允许被修改 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 · You cannot edit or delete the cloud region name：云区域名称不允许修改或删除 · If an east-west transit vRouter link enabled with remote route advertisement shares one transit vRouter with a centralized VAS vRouter link, the following items cannot overlap：1. Destination subnets configured for the route entries on the local vRouter of the east-west transit vRouter link.2. CIDRs configured for the remote vRouter of the centralized VAS vRouter link：TRANSIT类型虚拟路由器分别与两台虚拟路由器建立VAS VPC互通和发布对端所有路由开启的东西向TRANSIT VPC互通，东西向TRANSIT VPC互通的本端虚拟路由器的路由表项目的网段不能与VAS VPC互通的对端虚拟路由器CIDR重叠 · Resource application or rollback failed, internal unknown error：资源申请或回滚失败，内部未知错误 · The（resource）does not exist or the resources are insufficient：（资源）不存在或资源不足 · The（resource）does not exist or the resources are insufficient, device group name（name）：（资源）不存在或资源不足，设备组名称（名称） · The （resource） does not exist or the resources are insufficient, resource access template name （name）：（资源）不存在或资源不足，资源接入模板名称（名称） |
|
关键字 |
DELETE_ROUTETABLE_OP |
|
日志内容 |
Deleted routing table "$1" |
|
参数解释 |
$1：路由表的名称 |
|
举例 |
Deleted routing table "zn_routetable" |
|
日志说明 |
用户进行了删除路由表的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The specified resource doesn't exist：指定的资源不存在 · The routing table is being used by a subnet：路由表正在被subnet使用 · The routing table is being used by a vPort：路由表正在被vPort使用 · The routing table is used by a vRouter：该路由表已被虚拟路由器引用 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 · Resource application or rollback failed, internal unknown error：资源申请或回滚失败，内部未知错误 · The（resource）does not exist or the resources are insufficient：（资源）不存在或资源不足 · The（resource）does not exist or the resources are insufficient, device group name（name）：（资源）不存在或资源不足，设备组名称（名称） · The （resource） does not exist or the resources are insufficient, resource access template name （name）：（资源）不存在或资源不足，资源接入模板名称（名称） |
|
关键字 |
CREATE_ROUTE_OP |
|
日志内容 |
Created route "CIDR: $1, next hop type: $2", next hop $3, type: $4, enable BFD : $5, source IPs : $6, bfd session: $7" |
|
参数解释 |
$1：目的地址 $2：下一跳类型 $3：下一跳IP地址 $4：路由类型 $5：是否使能BFD $6：源IP地址 $7：BFD会话 |
|
举例 |
Created route "CIDR: 1.1.1.0/24, next hop type: IPv4, next hop: 1.1.1.1, type: 0, enable BFD: false, source IPs: [], bfd session: DOUBLE_AUTO_BFD". |
|
日志说明 |
用户进行了创建路由表项的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The route has already existed：该路由已存在 · Invalid next hop：无效的下一跳 · Invalid CIDR：无效的CIDR · Invalid routing table ID：无效的路由表ID · Invalid next hop type：无效的下一跳类型 · The destination subnet of the route entry overlaps with the subnet bound to the interface of the vRouter：路由表项中的目的网段与虚拟路由器接口的子网网段重叠 · The specified device doesn't exist：指定的设备不存在 · The device ID and the device name do not match：设备的ID和名称不匹配 · Duplicate devices exist：设备列表中存在重复的设备 · The specified next hop vRouter does not exist：下一跳虚拟路由器不存在 · When the next hop type is Blackhole, the next hop is not required：当下一跳类型为黑洞时，不需配置下一跳 · When the next hop type is Blackhole, the value of the host route recursion parameter must be false：当下一跳类型为黑洞时，迭代主机路由参数必须为false · When the next hop type is Blackhole, the next hop vRouter is not required：当下一跳类型为黑洞时，不需配置下一跳虚拟路由器 · Unknown error：未知错误 · The route entries cannot be created on Only fabric interconnection、DC interconnection or fabric interconnection and DC interconnection devices：路由表项中的设备不支持网络位置仅为Fabric间互通、DC间互联或Fabric间互通+DC间互联的设备 · Can't specify a vRouter whose origin is PBR：不允许指定来源为PBR的虚拟路由器 · The first BFD source IP address in a route entry cannot be the same as the second BFD source IP address in another route entry, and vice versa：路由表中存在配置了BFD源IP地址2的路由表项时，该表项的BFD源IP地址2不能与其他表项的BFD源IP地址1相同 · The first BFD source IP address in a route entry cannot be the same as the second source IP address of a BGP peer bound to the same vRouter as the route entry, and vice versa：对于绑定同一个虚拟路由器的路由表和BGP邻居，路由表中路由表项的BFD源IP地址1不能与BGP邻居的源IP地址2相同，反之，BGP邻居的源IP地址1也不能与路由表中路由表项的BFD源IP地址2相同 · The source IP address of a route entry with a vPort-type next hop on the vRouter cannot overlap with any vNetwork subnet on another vRouter：建立虚拟路由器连接的两个虚拟路由器，一个虚拟路由器下虚拟端口类型的路由表项的源IP不允许和另一个虚拟路由器下虚拟链路层网络的子网重叠 · The source IP address of a route entry with a vPort-type next hop on the vRouter cannot overlap with any external subnet on another vRouter：建立虚拟路由器连接的两个虚拟路由器，一个虚拟路由器下虚拟端口类型的路由表项的源IP不允许和另一个虚拟路由器下外部网络的子网重叠 · The source IP address of a route entry with a vPort-type next hop on the vRouter cannot be the same as any vNetwork subnet gateway IP of another vRouter：建立虚拟路由器连接的两个虚拟路由器，一个虚拟路由器下虚拟端口类型的路由表项的源IP不允许和另一个虚拟路由器下虚拟链路层网络子网的网关IP地址相同 · The source IP address of a route entry on the vRouter cannot be the same as any vNetwork subnet gateway IP on the vRouter：源IP地址不允许和同一虚拟路由器下虚拟链路层子网的网关IP地址相同 · The source IP address of a route entry on the vRouter cannot be within any vNetwork subnet on the vRouter：源IP地址不允许在同一虚拟路由器下虚拟链路层子网网段范围内 · The source IP address of a route entry on the vRouter cannot be within any external subnet on the vRouter：源IP地址不允许在同一虚拟路由器下外部网络的子网网段范围内 · The next hop type cannot be blackhole when the value of the type field is 401 or 402：当type字段取值为401和402时，不支持下一跳类型为黑洞 · When network cloud is enabled, the value for the type field cannot be 0：网络云开关开启时，不支持配置type为0 · The value of the type field is invalid：type字段无效 · The IP version of the IP address is invalid：IP地址的版本无效 · The two source IP address must be different：两个源IP地址不允许相同 · Invalid source IP address：源IP地址无效 · When the value of the type field is 401 and BFD enabled, a source IP is required：当type为401且BFD使能时，源IP地址必填 · A maximum of two source IP addresses are supported：源IP地址最多两个 · When the Network Cloud feature is disabled, routes with vPort or non-vPort as the next hop type are not supported：网络云开关关闭时，不支持配置下一跳类型为虚拟端口或非虚拟端口的路由表项 · The next hop type and next hop IP address do not match：下一跳类型和下一跳IP地址不匹配 · The destination subnet and the next hop type do not match：目的网段与下一跳类型不匹配 · When the next hop type is IPv6, host route recursion is not supported：当下一跳类型为IPv6时，不支持迭代主机路由 · Route entries that are enabled with BFD and use vPort next hops must have the same source IP address if they have the same next hop IP address：已存在下一跳类型为虚拟端口且已开启BFD的路由表项，如果下一跳地址相同，源IP地址也必须相同 · A route entry with the same settings already exists. Route entries that are enabled with BFD and use vPort next hops cannot have the same next hop IP address：下一跳类型为虚拟端口且开启使能BFD功能的路由表项仅允许创建一个 · Cannot enable BFD for route entries that use non-vPort next hops：非虚拟端口类型的路由表项不允许开启BFD功能 · Route entries that use vPort or non-vPort next hops cannot be edited：虚拟端口和非虚拟端口类型的路由表项不允许修改。 · When BFD is disabled, a source IP address is not required：当BFD参数取值为False时，不支持配置源IP地址 · The source IP address cannot be the same as the IP address of any gateway bound to the vRouter：源IP地址不允许和同一虚拟路由器下的网关IP地址相同 · The source IP address cannot belong to any subnet bound to the vRouter：源IP地址不允许在同一虚拟路由器下的子网网段范围内 · The source IP address cannot belong to any external subnet bound to the vRouter：源IP地址不允许在同一虚拟路由器下外部网络的子网网段内 · Do not specify the next hop vRouter when the next hop type is ExtIPv4 or ExtIPv6：当下一跳类型为ExtIPv4、ExtIPv6时，下一跳虚拟路由器无需配置 · The next hop in the route entry is a vPort and BFD is enabled for the route entry. You cannot set its IP address to be the gateway IP address of a vNetwork bound to the same vRouter as the routing table：路由表项的下一跳类型为虚拟端口且开启BFD功能时，下一跳IP地址不允许和同一虚拟路由器下虚拟链路层网络的网关IP地址相同 · Cannot apply the route entry to devices when the next hop type of the route entry is ExtIPv4 or ExtIPv6：下一跳类型为IPv4外网子网网关或IPv6外网子网网关时，路由表项不允许绑定设备 · You have no privilege to perform this operation：用户无权限执行此操作 · The source IP address cannot be within the destination subnet：源IP地址不能属于目的网段 · The source IP address conflicts with the next hop IP address：源IP地址不能与下一跳IP地址相同 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · You cannot specify a NQA profile for a route entry with a blackhole next hop：当下一跳类型为黑洞时，不允许配置NQA策略 · The NQA profile with the specified ID does not exist：指定ID的NQA策略不存在 · The NQA profile with the specified name does not exist：指定名称的NQA策略不存在 · A route entry does not support auto NQA profiles：不支持绑定配置为自动的NQA策略 · The NQA profile name and ID do not match：通过名称获取的NQA策略与通过ID获取的NQA策略不一致 · You cannot specify a NQA profile for the route entry. The next hop address of the entry is the same as the gateway address of an external subnet configured with a NQA profile, and the external subnet has been bound to the same vRouter as the route entry：当下一跳IP地址与虚拟路由器绑定的外网子网网关IP相同，且外网子网已绑定NQA策略，则路由表项不允许手动指定NQA策略 · Invalid BFD session：无效的BFD会话 · BFD session is not configurable in network cloud scenarios：网络云场景下不支持配置BFD会话 · BFD session is not configurable when the next hop type is blackhole route：下一跳类型是黑洞路由时，不允许配置BFD会话 · You can configure the NQA profile or BFD session parameter for a route entry, but not both：同一条路由表项中不能同时配置NQA策略和BFD会话 · BFD session is not configurable when the next hop's IP address does not belong to the directly connected external network bound to the vRouter：下一跳IP地址不属于虚拟路由器绑定的独享型外网子网，不允许配置BFD会话 · You cannot specify an NQA profile or BFD session for the route entry, because a next hop vRouter has been specified for the route entry：该路由表项已指定下一跳虚拟路由器，不允许配置NQA策略或BFD会话 · If a centralized-mode vRouter link, routing table, and Layer 3 DCI are attached to the same vRouter, you cannot specify the same subnet as a remote CIDR, destination subnet, and remote subnet for them, respectively：当集中式虚拟路由器连接、路由表和数据中心三层互联关联同一个虚拟路由器时，对端网段、目的网段和远端网段不能相同 · You can configure a tag for a route entry only when the network cloud scenario is disabled：Tag仅支持非网络云场景 · When host route recursion is enabled, the next hop IP address cannot reside on an external network：当迭代主机路由开关开启时，下一跳IP地址不能属于外网网段 · The tag must be an integer in the range of 1 to 4294967295：Tag的取值范围为1~4294967295的整数 · The tag value cannot be 2019091122, 2019080822, or any value in the range of 99990001 to 99999999：Tag不支持取值为2019091122和2019080822，以及99990001~99999999范围内的任意值 · If the remote end of a centralized-mode vRouter link is an external transit vRouter, the destination subnets in the route entries for the local vRouter cannot overlap with the external subnets specified for the remote vRouter：EXTERNALTRANSIT类型集中式虚拟路由器连接，本端虚拟路由器绑定的路由表项的目的网段与多数据中心外网网段信息不能重叠 · You cannot specify a tag, because a tag has been specified for a route entry destined for the same subnet in the routing table：当同一路由表中存在多条目的网段相同的路由表项时，仅允许其中一条路由表项配置Tag · You cannot enable host route recursion for a route entry when the next hop network type of that route entry is private and no next hop IP address is specified for that route entry：下一跳网络为private，下一跳IP为空的路由表项不支持开启迭代主机路由 · You cannot configure an NQA profile for a route entry when the next hop network type of that route entry is private and no next hop IP address is specified for that route entry：下一跳网络为private，下一跳IP为空的路由表项不支持配置NQA策略 · You cannot configure a BFD session for a route entry when the next hop network type of that route entry is private and no next hop IP address is specified for that route entry：下一跳网络为private，下一跳IP为空的路由表项不支持配置BFD会话 · You cannot enable host route recursion for a route entry when the next hop network type of that route entry is public：下一跳网络为public的路由表项不支持开启迭代主机路由 · You cannot configure an NQA profile for a route entry when the next hop network type of that route entry is public：下一跳网络为public的路由表项不支持配置策略NQA · You cannot configure a BFD session for a route entry when the next hop network type of that route entry is public：下一跳网络为public的路由表项不支持配置BFD会话 · You cannot configure a next hop vRouter for a route entry when the next hop network type of that route entry is public：下一跳网络为public的路由表项不支持配置下一跳虚拟路由器 · Invalid next hop network type：无效的下一跳网络 · You cannot set the next hop network type to public for a route entry when the next hop type of that route entry is ExtIPv4, ExtIPv6, or Blackhole：下一跳类型为ExtIPv4、ExtIPv6或黑洞路由的路由表项不支持配置下一跳网络为public · You must configure a minimum of one parameter from the next hop vRouter and next hop IP address for a route entry：路由表项不支持下一跳虚拟路由器和下一跳IP同时为空 · In the same routing table, route entries with the same destination subnet cannot overlap：同一路由表下目的网段相同的路由表项存在重叠 · No next hop IP address is specified for the route entry, the next hop type is IPv4 or IPv6, and the vRouter of the routing table has been bound to a non-shared gateway. The destination subnet of a route entry cannot be 0.0.0.0/0 or ::/0：当路由表项未指定下一跳IP地址，下一跳类型为IPv4或IPv6，且路由表所属的虚拟路由器已绑定非共享出口网关时，路由表项的目的地址不能为0.0.0.0/0或::/0 |
|
关键字 |
UPDATE_ROUTE_OP |
|
日志内容 |
Updated route " CIDR: $1, next hop type: $2, next hop $3, type: $4, enable BFD : $5, source IPs : $6, bfd session: $7" |
|
参数解释 |
$1：目的地址 $2：下一跳类型 $3：下一跳IP地址 $4：路由类型 $5：是否使能BFD $6：源IP地址 $7：BFD会话 |
|
举例 |
Updated route "CIDR: 1.1.1.0/24, next hop type: IPv4, next hop: 1.1.1.1, type: 0, enable BFD: false, source IPs: [], bfd session: DOUBLE_AUTO_BFD". |
|
日志说明 |
用户进行了修改路由表项的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The specified resource doesn't exist：指定的资源不存在 · The specified device doesn't exist：指定的设备不存在 · The device ID and the device name do not match：设备的ID和名称不匹配 · Duplicate devices exist：设备列表中存在重复的设备 · Unknown error：未知错误 · The route entries cannot be created on Only fabric interconnection、DC interconnection or fabric interconnection and DC interconnection devices：路由表项中的设备不支持网络位置仅为Fabric间互通、DC间互联或Fabric间互通+DC间互联的设备 · The value of the type field is invalid：type字段无效 · When the Network Cloud feature is disabled, routes with vPort or non-vPort as the next hop type are not supported：网络云开关关闭时，不支持配置下一跳类型为虚拟端口或非虚拟端口的路由表项 · When the next hop type is IPv6, host route recursion is not supported：当下一跳类型为IPv6时，不支持迭代主机路由 · Cannot apply the route entry to devices when the next hop type of the route entry is ExtIPv4 or ExtIPv6：下一跳类型为IPv4外网子网网关或IPv6外网子网网关时，路由表项不允许绑定设备 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · You cannot edit or delete the cloud region name：云区域名称不允许修改或删除 · You cannot specify a NQA profile for a route entry with a blackhole next hop：当下一跳类型为黑洞时，不允许配置NQA策略 · The NQA profile with the specified ID does not exist：指定ID的NQA策略不存在 · The NQA profile with the specified name does not exist：指定名称的NQA策略不存在 · A route entry does not support auto NQA profiles：不支持绑定配置为自动的NQA策略 · The NQA profile name and ID do not match：通过名称获取的NQA策略与通过ID获取的NQA策略不一致 · You cannot specify a NQA profile for the route entry. The next hop address of the entry is the same as the gateway address of an external subnet configured with a NQA profile, and the external subnet has been bound to the same vRouter as the route entry：当下一跳IP地址与虚拟路由器绑定的外网子网网关IP相同，且外网子网已绑定NQA策略，则路由表项不允许手动指定NQA策略 · Invalid BFD session：无效的BFD会话 · BFD session is not configurable in network cloud scenarios：网络云场景下不支持配置BFD会话 · BFD session is not configurable when the next hop type is blackhole route：下一跳类型是黑洞路由时，不允许配置BFD会话 · You can configure the NQA profile or BFD session parameter for a route entry, but not both：同一条路由表项中不能同时配置NQA策略和BFD会话 · BFD session is not configurable when the next hop's IP address does not belong to the directly connected external network bound to the vRouter：下一跳IP地址不属于虚拟路由器绑定的独享型外网子网，不允许配置BFD会话 · You cannot specify an NQA profile or BFD session for the route entry, because a next hop vRouter has been specified for the route entry：该路由表项已指定下一跳虚拟路由器，不允许配置NQA策略或BFD会话 · You can configure a tag for a route entry only when the network cloud scenario is disabled：Tag仅支持非网络云场景 · When host route recursion is enabled, the next hop IP address cannot reside on an external network：当迭代主机路由开关开启时，下一跳IP地址不能属于外网网段 · The tag must be an integer in the range of 1 to 4294967295：Tag的取值范围为1~4294967295的整数 · The tag value cannot be 2019091122, 2019080822, or any value in the range of 99990001 to 99999999：Tag不支持取值为2019091122和2019080822，以及99990001~99999999范围内的任意值 · You cannot bind devices to a route entry when the effective next hop type for the route entry is intranet IP：当生效的下一跳类型为内网IP时，不允许指定设备 · You cannot specify a tag, because a tag has been specified for a route entry destined for the same subnet in the routing table：当同一路由表中存在多条目的网段相同的路由表项时，仅允许其中一条路由表项配置Tag · You cannot enable host route recursion for a route entry when the next hop network type of that route entry is private and no next hop IP address is specified for that route entry：下一跳网络为private，下一跳IP为空的路由表项不支持开启迭代主机路由 · You cannot configure an NQA profile for a route entry when the next hop network type of that route entry is private and no next hop IP address is specified for that route entry：下一跳网络为private，下一跳IP为空的路由表项不支持配置NQA策略 · You cannot configure a BFD session for a route entry when the next hop network type of that route entry is private and no next hop IP address is specified for that route entry：下一跳网络为private，下一跳IP为空的路由表项不支持配置BFD会话 · You cannot enable host route recursion for a route entry when the next hop network type of that route entry is public：下一跳网络为public的路由表项不支持开启迭代主机路由 · You cannot configure an NQA profile for a route entry when the next hop network type of that route entry is public：下一跳网络为public的路由表项不支持配置策略NQA · You cannot configure a BFD session for a route entry when the next hop network type of that route entry is public：下一跳网络为public的路由表项不支持配置BFD会话 · When the next hop type is Blackhole, the value of the host route recursion parameter must be false：当下一跳类型为黑洞时，迭代主机路由参数必须为false |
|
关键字 |
DELETE_ROUTE_OP |
|
日志内容 |
Deleted route " CIDR: $1, next hop type: $2, next hop $3, type: $4, enable BFD : $5, source IPs : $6, bfd session: $7" |
|
参数解释 |
$1：目的地址 $2：下一跳类型 $3：下一跳IP地址 $4：路由类型 $5：是否使能BFD $6：源IP地址 $7：BFD会话 |
|
举例 |
Deleted route "CIDR: 1.1.1.0/24, next hop type: IPv4, next hop: 1.1.1.1, type: 0, enable BFD: false, source IPs: [], bfd session: DOUBLE_AUTO_BFD". |
|
日志说明 |
用户进行了删除路由表项的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The specified resource doesn't exist：指定的资源不存在 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
CREATE_CLUSTER_IP_OP |
|
日志内容 |
Created cluster IP ”$1”. |
|
参数解释 |
$1：应用集群虚IP的IP地址 |
|
举例 |
Created cluster IP ”192.168.1.1”. |
|
日志说明 |
用户进行了创建应用集群虚IP的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The network doesn't exist：虚拟网络不存在 · Invalid tenant ID：无效的租户ID · Invalid IP address：无效的IP地址 · The APP cluster VIP ID already exists：应用集群虚IP的ID已经存在 · APP cluster VIPs created in bulk cannot use the same ID：批量创建的应用集群虚IP的ID存在重复 · The APP cluster VIP already exists：应用集群虚IP已经存在 · The APP cluster VIP is required：未指定应用集群虚IP · The APP cluster VIP conflicts with the IP address of a vPort：应用集群虚IP地址与虚拟端口的IP地址冲突 · The APP cluster VIP must belong to an existing subnet：应用集群虚IP的地址必须属于一个已经存在的子网 · The tenant is required：未指定租户 · The network is required：未指定虚拟链路层网络 · The APP cluster VIP conflicts with the broadcast address of the subnet：应用集群虚IP地址和子网广播IP地址冲突 · The APP cluster VIP conflicts with the subnet address：应用集群虚IP地址和子网地址冲突 · The APP cluster mode is invalid：无效的应用集群虚IP类型 · The request is invalid：传入的JSON串错误 · Unknown error：未知错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · Can't specify a network whose origin is PBR：不允许指定来源为PBR的虚拟链路层网络 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_CLUSTER_IP_OP |
|
日志内容 |
Updated cluster IP ”$1”. |
|
参数解释 |
$1：应用集群虚IP的IP地址 |
|
举例 |
Updated cluster IP ”192.168.1.1”. |
|
日志说明 |
用户进行了修改应用集群虚IP的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The APP cluster mode is invalid：无效的应用集群虚IP类型 · The request is invalid：传入的JSON串错误 · Unknown error：未知错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The specified resource doesn't exist：指定的资源不存在 · The parameter (parameters) can’t be modified：(parameters)参数不允许被修改 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_CLUSTER_IP_OP |
|
日志内容 |
Deleted cluster IP “$1”. |
|
参数解释 |
$1：应用集群虚IP的IP地址 |
|
举例 |
Deleted cluster IP ”192.168.100.100”. |
|
日志说明 |
用户进行了删除应用集群虚IP的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The specified resource doesn't exist：指定的资源不存在 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
CREATE_FLOODINGDOMAIN_OP |
|
日志内容 |
Created flooding domain “$1”. |
|
参数解释 |
$1：泛洪域的名称 |
|
举例 |
Created flooding domain “domain1”. |
|
日志说明 |
用户进行了创建泛洪域的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The network doesn't exist：虚拟网络不存在 · The network ID is required：未指定虚拟网络ID · The flooding domain name already exists：泛洪域的名字已经存在 · The flooding domain name cannot exceed 255 characters：泛洪域名称最长255个字符 · The flooding domain ID already exists：泛洪域ID已存在 · Flooding domains created in bulk cannot use the same ID：批量创建的泛洪域的ID存在重复 · The flooding domain name is required：未指定泛洪域名字 · The MAC address type must be ANY for the flooding domain：泛洪域的MAC类型目前只支持 ANY · The MAC address type is required：未指定泛洪域的MAC类型 · The mask length for the subnet address of the flooding domain must be in the range of 4 to 32 bits：泛洪域IP网段的掩码配置错误 · The subnet address conflicts with the subnet address of another flooding domain within the same network：IP网段与同一虚拟链路层网络的其他泛洪域的IP网段相冲突 · No valid group IDs exist：没有合法的组ID · The IP address of the flooding domain must be a multicast or broadcast address：泛洪域的IP地址必须为组播或广播地址 · Invalid CIDR：无效的CIDR · The request is invalid：传入的JSON串错误 · Unknown error：未知错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The specified tenant doesn't exist：指定的租户不存在 · Can't specify a network whose origin is PBR：不允许指定来源为PBR的虚拟链路层网络 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_FLOODINGDOMAIN_OP |
|
日志内容 |
Updated flooding domain “$1”. |
|
参数解释 |
$1：泛洪域的名称 |
|
举例 |
Updated flooding domain “domain1”. |
|
日志说明 |
用户进行了修改泛洪域的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The MAC address type must be ANY for the flooding domain：泛洪域的MAC类型目前只支持 ANY · The MAC address type is required：未指定泛洪域的MAC类型 · The mask length for the subnet address of the flooding domain must be in the range of 4 to 32 bits：泛洪域IP网段的掩码配置错误 · The subnet address conflicts with the subnet address of another flooding domain within the same network：IP网段与同一虚拟链路层网络的其他泛洪域的IP网段相冲突 · The IP address of the flooding domain must be a multicast or broadcast address：泛洪域的IP地址必须为组播或广播地址 · The IP address of the flooding domain conflicts with the IP address of another flooding domain bound to the same vPort：泛洪域的IP地址与绑定在同一虚拟端口的其他泛洪域的IP地址冲突 · Invalid CIDR：无效的CIDR · The request is invalid：传入的JSON串错误 · Unknown error：未知错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The specified resource doesn't exist：指定的资源不存在 · The parameter (parameters) can’t be modified：(parameters)参数不允许被修改 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · The flooding domain name already exists：泛洪域的名字已经存在 · The flooding domain name cannot exceed 255 characters：泛洪域名称最长255个字符 |
|
关键字 |
DELETE_FLOODINGDOMAIN_OP |
|
日志内容 |
Deleted flooding domain “$1”. |
|
参数解释 |
$1：泛洪域的名称 |
|
举例 |
Deleted flooding domain “domain1”. |
|
日志说明 |
用户进行了删除泛洪域的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The specified resource doesn't exist：指定的资源不存在 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
SET_VCENTER_STATUS_OP |
|
日志内容 |
Updated vCenter status to “$1”. |
|
参数解释 |
$1：vCenter连接状态，包含connected和disconnected两种状态 |
|
举例 |
Updated vCenter status to connected. |
|
日志说明 |
用户进行了更新vCenter状态的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Failed to connect to the vCenter：vCenter连接失败 · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_PORT_PREFNAME_OP |
|
日志内容 |
Created port name prefix port type ”$1”, prefix name [$2]. |
|
参数解释 |
$1：端口类型 $2：端口名称前缀 |
|
举例 |
Created port name prefix port type “UPLINK”, prefix name [aaa, bbb], port type “VPORT”, prefix name [a1, b1]. |
|
日志说明 |
用户进行了添加端口名称前缀的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · Configuration recovery is in progress：配置恢复未完成 · The controller is not the active leader：该控制组件不是主Leader · Invalid port type：无效的端口类型 · The port name prefix prefixName already exists：指定的端口名称前缀prefixName已存在 · Invalid port name prefix：无效的端口名称前缀 · The port name prefix cannot exceed 64 characters：端口名称前缀应少于64个字符 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_PORT_PREFNAME_OP |
|
日志内容 |
Deleted port name prefix ”$1”. |
|
参数解释 |
$1：端口名称前缀 |
|
举例 |
Deleted port name prefix “aaa”. |
|
日志说明 |
用户进行了删除端口名称前缀的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Can't delete the default port name prefix：不允许删除默认端口名称前缀 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The specified resource doesn't exist：指定的资源不存在 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_GLOBAL_CONFIG_OP |
|
日志内容 |
Updated the global configuration of the controller: $1. |
|
参数解释 |
$1：全局配置信息 |
|
举例 |
Updated the global configuration of the controller. Stateful flow table: On. |
|
日志说明 |
用户进行了修改全局配置的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Configuration recovery is in progress：配置正在恢复中 · The controller is not the active leader：该控制组件不是主Leader · The VXLAN pool doesn't exists：指定的VXLAN池不存在 · You have no privilege to perform this operation：用户无权限执行此操作 · The VDS doesn't exist：VDS不存在 · The value for the dhcpFailOverMode parameter is invalid：无效的DHCP逃生支持第三方DHCP Server开关 · You cannot enable DHCP failover to third-party servers when distributed DHCP is enabled for host overlay：主机Overlay开启分布式DHCP开关开启时，不允许开启DHCP逃生支持第三方DHCP Server开关 · You cannot enable distributed DHCP for host overlay when DHCP failover to third-party servers is enabled：DHCP逃生支持第三方DHCP Server开关开启时，不允许开启主机Overlay开启分布式DHCP开关 · You cannot enable LLDP-based vPort onboarding, because automatic vPort creation has been enabled for some vNetworks：存在使能自动创建虚拟端口的虚拟链路层网络时，不允许开启LLDP上线虚拟端口开关 · You cannot change the LLDP-based vPort onboarding state, because some phy vPorts have come online：存在上线的phy虚拟端口,不允许切换LLDP上线虚拟端口开关 · You cannot enable LLDP-based vPort onboarding, because automatic vPort creation has been enabled for some VDSs：存在已开启自动创建虚拟端口开关的虚拟分布式交换机，不允许开启LLDP上线虚拟端口开关 · Network cloud scenario is not supported when external network route reduction is enabled：外部网络路由精简开关开启时，不允许开启网络云场景 · Route reduction for the controller global is not supported in network cloud scenarios：网络云场景下，不允许开启控制组件全局路由精简开关 · Failed to change the system VDS：切换系统VDS失败 · Failed to create a default fabric for the system VDS：为系统VDS创建默认Fabric失败 · You cannot enable the network cloud scenario when ND direct route redistribution is enabled：引入ND直连路由开关开启时，不允许开启网络云场景 · You cannot enable ND direct route redistribution globally in the network cloud scenario：网络云场景下，不允许开启控制组件全局引入ND直连路由开关 · You cannot enable centralized-mode vRouter link (firewall off) for route reduction in the network cloud scenario：网络云场景下，不允许开启集中式虚拟路由器连接(防火墙关闭)路由精简开关 · You cannot enable the network cloud feature when centralized-mode vRouter link (firewall off) is enabled for route reduction：集中式虚拟路由器连接(防火墙关闭)精简开关开启时，不允许开启网络云场景 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · The value for the l3_dci_fw_disable_reduce_routes parameter is invalid：无效的数据中心三层互联（防火墙关闭）路由精简参数 · The value for the l3_dci_fw_enable_reduce_routes parameter is invalid：无效的数据中心三层互联（防火墙开启）路由精简参数 · You cannot turn on the IPv6 option in the global VLAN-VXLAN mapping scenario：全局VLAN-VXLAN映射场景下，不允许IPv6开关从关闭到开启 · Resource application or rollback failed, internal unknown error：资源申请或回滚失败，内部未知错误 · The（resource）does not exist or the resources are insufficient：（资源）不存在或资源不足 · The（resource）does not exist or the resources are insufficient, device group name（name）：（资源）不存在或资源不足，设备组名称（名称） · The （resource） does not exist or the resources are insufficient, resource access template name （name）：（资源）不存在或资源不足，资源接入模板名称（名称） · The value of the vSwitch Flooding field is invalid：无效的虚拟交换机泛洪 · The value of the vSwitch Learning field is invalid：无效的虚拟交换机自学习 |
|
关键字 |
CREATE_NETOVERLAYHOST_OP |
|
日志内容 |
Created netoverlay host "$1". |
|
参数解释 |
$1：netoverlay主机的名称 |
|
举例 |
Created netoverlay host "112". |
|
日志说明 |
用户进行了创建Netoverlay主机的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The netoverlay host name is required：Netoverlay主机名称不能为空 · The netoverlay host already exists：Netoverlay主机已存在 · Netoverlay hosts created in bulk cannot use the same ID：批量创建的Netoverlay主机的ID存在重复 · The netoverlay host name cannot exceed 255 characters：Netoverlay主机名称最长255个字符 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
DELETE_NETOVERLAY_HOST_OP |
|
日志内容 |
Deleted netoverlay host "$1". |
|
参数解释 |
$1：netoverlay主机的名称 |
|
举例 |
Deleted netoverlay host "112". |
|
日志说明 |
用户进行了删除Netoverlay主机的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The specified resource doesn't exist：指定的资源不存在 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 · Cannot delete netoverlay host because it was created on VMM：不允许删除来源为VMM的Netoverlay主机 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
UPDATE_NETOVERLAYHOST_OP |
|
日志内容 |
Updated netoverlay host "$1". |
|
参数解释 |
$1：netoverlay主机的名称 |
|
举例 |
Updated netoverlay host "112". |
|
日志说明 |
用户进行了修改Netoverlay主机的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The netoverlay host name is required：Netoverlay主机名称不能为空 · The netoverlay host already exists：Netoverlay主机已存在 · The specified netoverlay group does not exist：指定的Netoverlay集群不存在 · A netoverlay host with VLAN-VXLAN mappings added cannot be bound to a netoverlay group：Netoverlay主机已添加VLAN-VLAN时，不允许绑定Netoverlay集群 · The netoverlay host name cannot exceed 255 characters：Netoverlay主机名称最长255个字符 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 · You cannot edit or delete the cloud region name：云区域名称不允许修改或删除 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
CREATE_NETOVERLAYGROUP_OP |
|
日志内容 |
Created netoverlay group "$1". |
|
参数解释 |
$1：netoverlay集群的名称 |
|
举例 |
Created netoverlay group "group1". |
|
日志说明 |
用户进行了创建Netoverlay集群的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The netoverlay group name is required：Netoverlay集群名称不能为空 · The netoverlay group already exists：Netoverlay集群已存在 · The netoverlay group name cannot exceed 255 characters：Netoverlay集群名称最长255个字符 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_NETOVERLAY_GROUP_OP |
|
日志内容 |
Deleted netoverlay group "$1". |
|
参数解释 |
$1：netoverlay集群的名称 |
|
举例 |
Deleted netoverlay group "group1". |
|
日志说明 |
用户进行了删除Netoverlay集群的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The specified resource doesn't exist：指定的资源不存在 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
CREATE_VLANVXLAN_MAP_OP |
|
日志内容 |
Created VLAN-VXLAN map "$1-$2". |
|
参数解释 |
$1：VLAN ID $2：VXLAN ID |
|
举例 |
Created VLAN-VXLAN map "11-22". |
|
日志说明 |
用户进行了创建VLAN-VXLAN映射的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The netoverlay host ID is required：Netoverlay主机ID不能为空 · The netoverlay host does not exist：Netoverlay主机不存在 · The VLAN ranges of hosts in a netoverlay cannot be the same：同一个Netoverlay主机不能配置重复的VLAN范围 · The VLAN ranges of hosts in a netoverlay already exists：Netoverlay主机上已存在指定的VLAN范围 · VLAN-VXLAN mappings cannot be added on a netoverlay host bound to a netoverlay group：Netoverlay主机已绑定Netoverlay集群时，不允许添加VLAN-VXLAN映射 · The netoverlay host and the netoverlay group cannot both be null：Netoverlay主机和Netoverlay集群不能同时为空 · The specified netoverlay group does not exist：指定的Netoverlay集群不存在 · The netoverlay host and the netoverlay group cannot be both configured：Netoverlay主机和Netoverlay集群不能同时配置 · The VLAN ID is required：VLAN ID不能为空 · The VXLAN ID is required：VXLAN ID不能为空 · The VLAN ID is out of range：VLAN ID超出范围 · The VXLAN ID is out of range：VXLAN ID超出范围 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
DELETE_VLANVXLAN_MAP_OP |
|
日志内容 |
Deleted VLAN-VXLAN map "$1-$2". |
|
参数解释 |
$1：VLAN ID $2：VXLAN ID |
|
举例 |
Deleted VLAN-VXLAN map "11-22". |
|
日志说明 |
用户进行了删除VLAN-VXLAN映射的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The specified resource doesn't exist：指定的资源不存在 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 · Cannot delete VLAN-VXLAN mapping because it was created on VMM：不允许删除来源为VMM的VLAN-VXLAN映射 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
CREATE_QinQ_MAP_OP |
|
日志内容 |
Created QinQ map "$1-$2". |
|
参数解释 |
$1：CVLAN ID $2：SVLAN ID |
|
举例 |
Created QinQ map "11-22". |
|
日志说明 |
用户进行了创建QinQ映射的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Please specify an SVLAN：外层VLAN不能为空 · Please specify a CVLAN：内层VLAN不能为空 · The SVLAN is out of range：外层VLAN超出范围 · The CVLAN is out of range：内层VLAN超出范围 · The cloud region name of the QinQ mapping can contain up to 255 characters：QinQ映射的云区域名称最长255个字符 · Please specify the host_id parameter：host_id不能为空 · You cannot bind the network overlay host to a network overlay cluster, because it has been configured with QinQ mappings：Netoverlay主机已添加QinQ映射，不允许绑定Netoverlay集群 · A QinQ mapping on the network overlay host already contains the specified SVLAN range and CVLAN range：Netoverlay主机上的QinQ映射已存在指定SVLAN和CVLAN范围 · The QinQ mappings on the same network overlay host must have exclusive SVLAN ranges and CVLAN ranges：同一个Netoverlay主机的QinQ映射不能配置重复的SVLAN和CVLAN范围 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
DELETE_QINQ_MAP_OP |
|
日志内容 |
Deleted QinQ-VXLAN map "ID: $1, SVLAN Range: $2, CVLAN Range: $3, VXLAN Range: $4". |
|
参数解释 |
$1：映射的UUID $2：SVLAN范围 $2：CVLAN范围 $4：VXLAN范围 |
|
举例 |
Deleted QinQ-VXLAN map "ID: ba66c2e4-7a10-4328-8b9b-1edd97585cdb,SVLAN Range: 6,CVLAN Range: 111, VXLAN Range: 100". |
|
日志说明 |
用户进行了删除QinQ映射的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The specified resource doesn't exist：指定的资源不存在 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
SET_VSWITCH_CFG_OP |
|
日志内容 |
Configured batch vSwitch deployment parameters. |
|
参数解释 |
无 |
|
举例 |
Configured batch vSwitch deployment parameters. |
|
日志说明 |
用户进行了更改vSwitch部署配置的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：请求参数无效 · The bridge name can contain up to 15 case-sensitive characters. Only letters, digits, underlines (_), hyphens (-), and dots (.) are supported：桥名称最长15个字符，区分大小写，仅支持字母、数字、下划线、连字符和点号 · he uplink port name can contain up to 15 case-sensitive characters. Only letters, digits, underlines (_), hyphens (-), and dots (.) are supported：上行口名称最长15个字符，区分大小写，仅支持字母、数字、下划线、连字符和点号 · Invalid gateway IP address：无效的网关IP地址 · Invalid OpenFlow connection mode：无效的OpenFlow连接方式 · Invalid OpenFlow port number：无效的OpenFlow端口号 · Invalid MTU value：无效的MTU值 · Invalid IP address：无效的IP地址 · Invalid subnet mask：无效的子网掩码 · The start IP address and the end IP address must belongs to the same IP family：起始IP和结束IP必须属于同一个地址族 · The start IP address can't be higher than the end IP address：起始IP不能大于结束IP · You must specify a subnet mask when a VTEP IP address pool is configured：当配置了VTEP IP地址池时，子网掩码不能为空 · Please specify the bridge type：桥模型不能为空 · Invalid bridge type：无效的桥模型 · You must specify a certificate when the OpenFlow connection type is SSL：当OpenFlow连接方式为SSL时，必须指定证书文件 · The specified private certificate does not exist：指定的Private证书文件不存在 · The specified certificate file does not exist：指定的CRT证书文件不存在 · The specified CA-CRT certificate does not exist：指定的CA-CRT证书文件不存在 · Invalid bond mode：无效的聚合模式 · The br-ex bridge name can contain up to 15 characters：Br-ex桥名称最长1~15个字符 · The private certificate does not exist in the directory：指定的Private证书文件在存储目录中不存在 · The CRT certificate does not exist in the directory：指定的CRT证书文件在存储目录中不存在 · The CA-CRT certificate does not exist in the directory：指定的CA-CRT证书文件在存储目录中不存在 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
IMPORT_DEPLOYING_HOST_LIST_OP |
|
日志内容 |
Imported $1 undeployed hosts. |
|
参数解释 |
$1：导入待部署S1020v主机的个数 |
|
举例 |
Imported 2 undeployed hosts. |
|
日志说明 |
用户进行了导入待部署S1020v主机列表文件的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · The request is invalid：请求参数无效 · Please specify a host IP address：主机IP地址不能为空 · Invalid IP address：无效的IP地址 · The bridge name can contain up to 15 case-sensitive characters. Only letters, digits, underlines (_), hyphens (-), and dots (.) are supported：桥名称最长15个字符，区分大小写，仅支持字母、数字、下划线、连字符和点号 · The uplink port name can contain up to 15 case-sensitive characters. Only letters, digits, underlines (_), hyphens (-), and dots (.) are supported：上行口名称最长15个字符，区分大小写，仅支持字母、数字、下划线、连字符和点号 · Invalid gateway IP address：无效的网关IP地址 · Invalid OpenFlow connection mode：无效的OpenFlow连接方式 · Invalid OpenFlow port number：无效的OpenFlow端口号 · Invalid MTU value：无效的MTU值 · Invalid subnet mask：无效的子网掩码 · Invalid encryption flag：无效的加密标志 · Invalid username and password：无效的用户名和密码 · Please specify a compute domain name：计算域名不能为空 · The domain doesn't exist：计算域不存在 · Deploying... Please try again later：正在部署中，请稍后重试 · Host {{hostIp}} already exists, and it belongs to compute domain {{domain}}：指定主机{{hostIp}}已存在，且所属计算域是{{domain}} · No available VTEP IP addresses：VTEP IP地址池内没有可用的IP地址 · Host %s , %s is required：{{hostIp}} , {{param}} 不能为空 · Please specify the bridge type：桥模型不能为空 · Invalid bridge type：无效的桥模型 · You must specify a certificate when the OpenFlow connection type is SSL：当OpenFlow连接方式为SSL时，必须指定证书文件 · The specified private certificate does not exist：指定的Private证书文件不存在 · The specified certificate file does not exist：指定的CRT证书文件不存在 · The specified CA-CRT certificate does not exist：指定的CA-CRT证书文件不存在 · Invalid bond mode：无效的聚合模式 · The private certificate does not exist in the directory：指定的Private证书文件在存储目录中不存在 · The CRT certificate does not exist in the directory：指定的CRT证书文件在存储目录中不存在 · The CA-CRT certificate does not exist in the directory：指定的CA-CRT证书文件在存储目录中不存在 · You have no privilege to perform this operation：用户无权限执行此操作 · Failed to read the Excel file. Reason: The hyperlink for cell $1 references relation $2, but that didn't exist：Excel文件读取失败，原因为单元格$1的超链接引用关系$2不存在 · Field pci_list not supported for normal bridge type：普通桥模型不支持pci_list字段 · Field large_page_set not supported for normal bridge type：普通桥模型不支持large_page_set字段 · Field bond_mode not supported for normal bridge type：普通桥模型不支持bond_mode字段 · Field br_ex not supported for normal bridge type：普通桥模型不支持br_ex字段 · Field bind_cpu_core not supported for normal bridge type：普通桥模型不支持bind_cpu_core字段 · The list of datapath core bindings contains invalid values：CPU数据核绑定列表存在无效取值 · The list of datapath core bindings contains duplicate values：CPU数据核绑定列表存在重复取值 · The list of hugepages settings contains invalid values：巨页数据列表存在无效取值 · HugePages field format error：巨页数据字段格式错误 · PCI field format error：PCI字段格式错误 · Datapath core bindings field format error：CPU数据核绑定字段格式错误 · Invalid VTEP IP address：无效的VTEP IP地址 · Domain type and sheet mismatch. Please specify the domain in the correct sheet：计算域类型与工作表不匹配。请在正确的工作表填写该计算域 |
|
关键字 |
ADD_DEPLOYMENT_HOST_OP |
|
日志内容 |
Added undeployed host “$1”. |
|
参数解释 |
$1：待部署S1020v主机的IP地址 |
|
举例 |
Added undeployed host “2.2.2.6”. |
|
日志说明 |
用户进行了添加单个待部署S1020v主机的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · The request is invalid：请求参数无效 · Please specify a host IP address：主机IP地址不能为空 · Invalid IP address：无效的IP地址 · The bridge name can contain up to 15 case-sensitive characters. Only letters, digits, underlines (_), hyphens (-), and dots (.) are supported：桥名称最长15个字符，区分大小写，仅支持字母、数字、下划线、连字符和点号 · The uplink port name can contain up to 15 case-sensitive characters. Only letters, digits, underlines (_), hyphens (-), and dots (.) are supported：上行口名称最长15个字符，区分大小写，仅支持字母、数字、下划线、连字符和点号 · Invalid gateway IP address：无效的网关IP地址 · Invalid OpenFlow connection mode：无效的OpenFlow连接方式 · Invalid OpenFlow port number：无效的OpenFlow端口号 · Invalid MTU value：无效的MTU值 · Invalid subnet mask：无效的子网掩码 · Invalid encryption flag：无效的加密标志 · Invalid username and password：无效的用户名和密码 · Please specify a compute domain name：计算域名不能为空 · The domain doesn't exist：计算域不存在 · Deploying... Please try again later：正在部署中，请稍后重试 · Host {{hostIp}} already exists, and it belongs to compute domain {{domain}}：指定主机{{hostIp}}已存在，且所属计算域是{{domain}} · No available VTEP IP addresses：VTEP IP地址池内没有可用的IP地址 · Host %s , %s is required：{{hostIp}} , {{param}} 不能为空 · Please specify the bridge type：桥模型不能为空 · Invalid bridge type：无效的桥模型 · You must specify a certificate when the OpenFlow connection type is SSL：当OpenFlow连接方式为SSL时，必须指定证书文件 · The specified private certificate does not exist：指定的Private证书文件不存在 · The specified certificate file does not exist：指定的CRT证书文件不存在 · The specified CA-CRT certificate does not exist：指定的CA-CRT证书文件不存在 · Invalid bond mode：无效的聚合模式 · The private certificate does not exist in the directory：指定的Private证书文件在存储目录中不存在 · The CRT certificate does not exist in the directory：指定的CRT证书文件在存储目录中不存在 · The CA-CRT certificate does not exist in the directory：指定的CA-CRT证书文件在存储目录中不存在 · You have no privilege to perform this operation：用户无权限执行此操作 · Field pci_list not supported for normal bridge type：普通桥模型不支持pci_list字段 · Field large_page_set not supported for normal bridge type：普通桥模型不支持large_page_set字段 · Field bond_mode not supported for normal bridge type：普通桥模型不支持bond_mode字段 · Field br_ex not supported for normal bridge type：普通桥模型不支持br_ex字段 · Field bind_cpu_core not supported for normal bridge type：普通桥模型不支持bind_cpu_core字段 · The list of datapath core bindings contains invalid values：CPU数据核绑定列表存在无效取值 · The list of datapath core bindings contains duplicate values：CPU数据核绑定列表存在重复取值 · The list of hugepages settings contains invalid values：巨页数据列表存在无效取值 · Invalid VTEP IP address：无效的VTEP IP地址 · The value for the Create ERSPAN Interface parameter is invalid：“创建ERSPAN接口”参数取值无效 |
|
关键字 |
EDIT_DEPLOYMENT_HOST_OP |
|
日志内容 |
Edited undeployed host “$1”. |
|
参数解释 |
$1：待部署S1020v主机的IP地址 |
|
举例 |
Edited undeployed host “98.0.38.24”. |
|
日志说明 |
用户进行了更新单个待部署S1020v主机的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · The request is invalid：请求参数无效 · Invalid IP address：无效的IP地址 · The bridge name can contain up to 15 case-sensitive characters. Only letters, digits, underlines (_), hyphens (-), and dots (.) are supported：桥名称最长15个字符，区分大小写，仅支持字母、数字、下划线、连字符和点号 · The uplink port name can contain up to 15 case-sensitive characters. Only letters, digits, underlines (_), hyphens (-), and dots (.) are supported：上行口名称最长15个字符，区分大小写，仅支持字母、数字、下划线、连字符和点号 · Invalid gateway IP address：无效的网关IP地址 · Invalid OpenFlow connection mode：无效的OpenFlow连接方式 · Invalid OpenFlow port number：无效的OpenFlow端口号 · Invalid MTU value：无效的MTU值 · Invalid subnet mask：无效的子网掩码 · Invalid encryption flag：无效的加密标志 · Invalid username and password：无效的用户名和密码 · Please specify a compute domain name：计算域名不能为空 · The domain doesn't exist：计算域不存在 · Deploying... Please try again later：正在部署中，请稍后重试 · Host {{hostIp}} already exists, and it belongs to compute domain {{domain}}：指定主机{{hostIp}}已存在，且所属计算域是{{domain}} · No available VTEP IP addresses：VTEP IP地址池内没有可用的IP地址 · Host %s , %s is required：{{hostIp}} , {{param}} 不能为空 · Invalid bridge type：无效的桥模型 · You must specify a certificate when the OpenFlow connection type is SSL：当OpenFlow连接方式为SSL时，必须指定证书文件 · The specified private certificate does not exist：指定的Private证书文件不存在 · The specified certificate file does not exist：指定的CRT证书文件不存在 · The specified CA-CRT certificate does not exist：指定的CA-CRT证书文件不存在 · Invalid bond mode：无效的聚合模式 · The private certificate does not exist in the directory：指定的Private证书文件在存储目录中不存在 · The CRT certificate does not exist in the directory：指定的CRT证书文件在存储目录中不存在 · The CA-CRT certificate does not exist in the directory：指定的CA-CRT证书文件在存储目录中不存在 · You have no privilege to perform this operation：用户无权限执行此操作 · Field pci_list not supported for normal bridge type：普通桥模型不支持pci_list字段 · Field large_page_set not supported for normal bridge type：普通桥模型不支持large_page_set字段 · Field bond_mode not supported for normal bridge type：普通桥模型不支持bond_mode字段 · Field br_ex not supported for normal bridge type：普通桥模型不支持br_ex字段 · Field bind_cpu_core not supported for normal bridge type：普通桥模型不支持bind_cpu_core字段 · The list of datapath core bindings contains invalid values：CPU数据核绑定列表存在无效取值 · The list of datapath core bindings contains duplicate values：CPU数据核绑定列表存在重复取值 · The list of hugepages settings contains invalid values：巨页数据列表存在无效取值 · Invalid VTEP IP address：无效的VTEP IP地址 · The value for the Create ERSPAN Interface parameter is invalid：“创建ERSPAN接口”参数取值无效 |
|
关键字 |
DELETE_DEPLOYMENT_HOST_OP |
|
日志内容 |
Deleted undeployed host “$1”. |
|
参数解释 |
$1：待部署S1020v主机的IP地址 |
|
举例 |
Deleted undeployed host “2.2.2.2”. |
|
日志说明 |
用户进行了删除待部署S1020v主机的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · Invalid IP address：无效的IP地址 · Deploying... Please try again later：正在部署中，请稍后重试 · The host doesn't exist：指定主机不存在 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
EXPORT_DEPLOYING_HOST_LIST_OP |
|
日志内容 |
Exported $1 undeployed hosts. |
|
参数解释 |
$1：导出的待部署S1020v的主机个数 |
|
举例 |
Exported 3 undeployed hosts. |
|
日志说明 |
用户进行了导出待部署S1020v主机列表的操作 |
|
失败原因 |
· Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 · The host export API is being used by another user：导出主机接口正在被其他用户使用 |
|
关键字 |
EXPORT_SSH_KEY_OP |
|
日志内容 |
Exported SSH key. |
|
参数解释 |
无 |
|
举例 |
Exported SSH key. |
|
日志说明 |
用户进行了导出SSH密钥的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · No SSH keys are configured：SSH密钥不存在 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
INSTALL_VSWITCH_OP |
|
日志内容 |
Installed vSwitch. Total: $1. Success: $2. Failure: $3. |
|
参数解释 |
$1：安装vSwitch版本的主机总数量 $2：安装vSwitch版本成功的主机数量 $3：安装vSwitch版本失败的主机数量 |
|
举例 |
Installed vSwitch. |
|
日志说明 |
用户进行了安装vSwitch版本到主机的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：请求参数无效 · Deploying... Please try again later：正在部署中，请稍后重试 · The task has been terminated by user user：该任务已被用户user终止 · For more information, see the deployment logs：详细信息请查阅部署日志 · The certificate has been specified as the default CA-CRT certificate and cannot be deleted：指定的CA-CRT证书文件已添加到默认配置中，不允许删除 · The private certificate does not exist in the directory：指定的Private证书文件在存储目录中不存在 · The CRT certificate does not exist in the directory：指定的CRT证书文件在存储目录中不存在 · The CA-CRT certificate does not exist in the directory：指定的CA-CRT证书文件在存储目录中不存在 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_VSWITCH_OP |
|
日志内容 |
Updated vSwitch. Total: $1. Success: $2. Failure: $3. |
|
参数解释 |
$1：更新vSwitch版本的主机总数量 $2：更新vSwitch版本成功的主机数量 $3：更新vSwitch版本失败的主机数量 |
|
举例 |
Updated vSwitch. |
|
日志说明 |
用户进行了更新主机vSwitch版本的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：请求参数无效 · The task has been terminated by user user：该任务已被用户user终止 · For more information, see the deployment logs：详细信息请查阅部署日志 · Deploying... Please try again later：正在部署中，请稍后再试 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UNINSTALL_VSWITCH_OP |
|
日志内容 |
Uninstalled vSwitch. Total: $1. Success: $2. Failure: $3. |
|
参数解释 |
$1：卸载vSwitch版本的主机总数量 $2：卸载vSwitch版本成功的主机数量 $3：卸载vSwitch版本失败的主机数量 |
|
举例 |
Uninstalled vSwitch. |
|
日志说明 |
用户进行了卸载主机vSwitch版本的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：请求参数无效 · The task has been terminated by user user：该任务已被用户user终止 · For more information, see the deployment logs：详细信息请查阅部署日志 · Deploying... Please try again later：正在部署中，请稍后再试 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CHECK_HOST_STATUS |
|
日志内容 |
Checked host status. |
|
参数解释 |
无 |
|
举例 |
Checked host status. |
|
日志说明 |
检查主机的连通性. |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：请求参数无效 · Deploying... Please try again later：正在部署中，请稍后重试 · The task has been terminated by user (sdn)：该任务已被用户sdn终止 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPLOAD_VSWITCH_FILE_OP |
|
日志内容 |
Uploaded vSwitch file ”$1”. |
|
参数解释 |
$1：vSwitch版本文件名称 |
|
举例 |
Uploaded vSwitch file “s1020v_F2237.zip”. |
|
日志说明 |
用户进行了上传vSwitch版本文件的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Failed to upload file：上传文件失败 · Failed to parse file：解析文件失败 · Please specify the file name：文件名称不能为空 · The file name can contain up to 255 characters：文件名称最长255个字符 · Another file already exists with the specified name：指定的证书文件名称已存在 · Failed to parse the .zip file：解析ZIP文件失败 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPLOAD_CERTIFICATE_FILE_OP |
|
日志内容 |
Uploaded certificate file ”$1”. |
|
参数解释 |
$1：证书文件名称 |
|
举例 |
Uploaded certificate file “private.crt”. |
|
日志说明 |
用户进行了上传证书文件的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Failed to upload file：上传文件失败 · Failed to parse file：解析文件失败 · Please specify the file name：文件名称不能为空 · The file name can contain up to 255 characters：文件名称最长255个字符 · Another flie already exists with the specified name：指定的证书文件名称已存在 · Invalid certificate type：无效的证书类型 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_FILE_OP |
|
日志内容 |
Deleted file “$1”. |
|
参数解释 |
$1：文件的UUID |
|
举例 |
Deleted file “501172da-2514-3013-9a7e-5fb1f75d6090”. |
|
日志说明 |
用户进行了删除版本文件或证书文件的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · The certificate has been specified as the default private certificate and cannot be deleted：指定的Private证书文件已添加到默认配置中，不允许删除 · The certificate has been specified as the default CRT certificate and cannot be deleted：指定的CRT证书文件已添加到默认配置中，不允许删除 · The certificate has been specified as the default CA-CRT certificate and cannot be deleted：指定的CA-CRT证书文件已添加到默认配置中，不允许删除 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_NETWORKNODE_OP |
|
日志内容 |
Created network nodes ”$1”. |
|
参数解释 |
$1：网络节点的名称 |
|
举例 |
Created network nodes "network1", "network2". |
|
日志说明 |
用户进行了创建网络节点的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · The request is invalid：传入的JSON串错误 · The controller is not the active leader：请在主Leader上进行操作 · Configuration recovery is in progress：配置恢复未完成 · You have no privilege to perform this operation：用户无权限执行此操作 · The network node name is required：未指定网络节点名称 · The VDS doesn't exist：VDS不存在 · The network node name has been used：网络节点名称已被使用 · The network node VTEP IP has been used：网络节点VTEP IP已被使用 · The network node name cannot exceed 255 characters：网络节点名称最长255个字符 · The cloud region name for the network node cannot exceed 255 characters：网络节点云区域名称最长255个字符 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
UPDATE_NETWORKNODE_OP |
|
日志内容 |
Updated network node ”$1”. |
|
参数解释 |
$1：网络节点的名称 |
|
举例 |
Updated network node “netnode”. |
|
日志说明 |
用户进行了修改网络节点的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · The request is invalid：传入的JSON串错误 · The specified resource doesn't exist：指定的资源不存在 · You have no privilege to perform this operation：用户无权限执行此操作 · You cannot edit or delete the cloud region name：云区域名称不允许修改或删除 · The controller is not the active leader：请在主Leader上进行操作 · Configuration recovery is in progress：配置恢复未完成 · The network node name cannot be modified：网络节点名称不允许修改 · The network node VDS UUID cannot be modified：网络节点VDS UUID不允许修改 · The network node VTEP IP has been used：网络节点VTEP IP已被使用 · The cloud region name for the network node cannot exceed 255 characters：网络节点云区域名称最长255个字符 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
DELETE_NETWORKNODE_OP |
|
日志内容 |
Deleted network node ”$1”. |
|
参数解释 |
$1：网络节点的名称 |
|
举例 |
Deleted network node “netnode”. |
|
日志说明 |
用户进行了删除网络节点的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · The request is invalid：传入的JSON串错误 · The specified resource doesn't exist：指定的资源不存在 · You have no privilege to perform this operation：用户无权限执行此操作 · The controller is not the active leader：请在主Leader上进行操作 · Configuration recovery is in progress：配置恢复未完成 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
UPDATE_GLOBALDEFAULTACTION_OP |
|
日志内容 |
Updated global default action “$1”. |
|
参数解释 |
$1：分布式防火墙全局默认动作 |
|
举例 |
Updated global default action “forward”. |
|
日志说明 |
用户进行了配置分布式防火墙的全局默认动作的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The global default action is required：未指定全局默认动作 · The global default action is invalid：非法的全局默认动作 · The maximum number of sessions is invalid：非法的最大会话数 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_DFW_POLICY_OP |
|
日志内容 |
Created DFW policy “$1”. |
|
参数解释 |
$1：分布式防火墙策略或子策略的名称 |
|
举例 |
Created DFW policy “policy1”. |
|
日志说明 |
用户进行了创建分布式防火墙策略或子策略的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The DFW policy already exists：该策略已存在 · The DFW policy name cannot exceed 255 characters：策略名称长度不能超过255字符 · The DFW policy description cannot exceed 255 characters：策略的描述信息长度不能超过255字符 · The policy type is required：未指定策略类型 · The default action is required：未指定策略默认动作 · The default action is invalid：非法的策略默认动作 · DFW Policies created in bulk cannot use the same ID：批量创建的分布式防火墙策略的ID存在重复 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_DFW_POLICY_OP |
|
日志内容 |
Updated DFW policy “$1”. |
|
参数解释 |
$1：分布式防火墙策略或子策略的名称 |
|
举例 |
Updated DFW policy “policy1”. |
|
日志说明 |
用户进行了修改分布式防火墙策略或子策略的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The specified resource doesn't exist：指定的资源不存在 · Invalid DFW policy ID：非法的策略ID · The DFW policy does not exist：指定的策略不存在 · The DFW policy name cannot exceed 255 characters：策略名称长度不能超过255字符 · The DFW policy description cannot exceed 255 characters：策略的描述信息长度不能超过255字符 · The default action is invalid：非法的策略默认动作 · The specified tenant ID cannot be modified：已指定的租户ID不允许修改 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_DFW_POLICY_OP |
|
日志内容 |
Deleted DFW policy “$1”. |
|
参数解释 |
$1：分布式防火墙策略或子策略的名称 |
|
举例 |
Deleted DFW policy “policy1”. |
|
日志说明 |
用户进行了删除分布式防火墙策略或子策略的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The specified resource doesn't exist：指定的资源不存在 · The DFW subpolicy cannot be deleted because it is in used：子策略已被引用，不能删除 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_DFW_POLICY_RULE_OP |
|
日志内容 |
Created DFW policy rule “$1”. |
|
参数解释 |
$1：分布式防火墙策略或子策略规则的名称 |
|
举例 |
Created DFW policy rule “rule1”. |
|
日志说明 |
用户进行了创建分布式防火墙策略规则或子策略规则的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · Invalid policy rule ID：非法的策略规则ID · The policy rule already exists：该策略规则已存在 · The specified subpolicy does not exist：指定的子策略不存在 · You can specify the subpolicy only when the value of the target is sub-policy：仅当字段target值为sub-policy时，才允许指定子策略 · Invalid target：无效的动作 · The policy rule number is out of range：规则的编号超出了范围 · The specified policy or subpolicy does not exist：指定的策略或者子策略不存在 · The policy rule name cannot exceed 255 characters：规则名称的长度不能超过255字符 · The source IP is invalid：非法的源IP地址 · The destination IP is invalid：非法的目的IP地址 · The IP set does not exist：指定的IP地址集不存在 · The source IP and the source IP set cannot be both configured：源IP地址与源IP地址集不能同时配置 · The Net&Port IP set and protocol cannot be configured at the same time：不能同时指定Net&Port类型的IP地址集和协议类型 · The Net&Port IP set and port range cannot be configured at the same time：不能同时指定Net&Port类型的IP地址集和端口范围 · The source IP set port direction is invalid：非法的源IP地址集端口方向 · Cannot configure the port direction for a NET IP set：不能为NET类型的IP地址集指定端口方向 · The destination IP and the destination IP set cannot be both configured：目的IP地址与目的IP地址集不能同时配置 · The destination IP set port direction is invalid：非法的目的IP地址集端口方向 · The ICMP type is required：未指定ICMP报文类型 · Invalid ICMP type：无效的ICMP报文类型 · Invalid ICMP code：无效的ICMP代码 · The ICMP protocol type and port range cannot be configured at the same time：不能同时指定协议类型ICMP和端口范围 · The ICMP protocol type and TCP flag check or match cannot be configured at the same time：ICMP协议类型和TCP标志位检查或匹配不能同时配置 · The tcp flag match and check must be configured at the same time：TCP标志位检查和匹配必须同时存在 · The TCP flag check is invalid：非法的TCP标志位检查 · The TCP flag match is invalid：非法的TCP标志位匹配 · The TCP flag match parameter is not a TCP flag check parameter：TCP标志位匹配超出了TCP标志位检查的范围 · The UDP protocol type and ICMP flag cannot be configured at the same time：不能同时指定协议类型UDP和ICMP标志 · The UDP protocol type and TCP flag cannot be configured at the same time：不能同时指定协议类型UDP和TCP标志位 · The protocol type is invalid：非法的协议类型 · The protocol type is required：未指定协议类型 · Invalid port number range：非法的端口范围 · Invalid port number：非法的端口号 · The start port number cannot be greater than the end port number：端口范围起始值应小于或者等于端口范围的结束值 · Invalid state：非法的规则状态 · The new DFW policy rule conflicts with another rule：创建的分布式防火墙策略规则和已存在的分布式防火墙策略规则冲突 · DFW policy rules created in bulk cannot use the same ID：批量创建的分布式防火墙策略规则的ID存在重复。 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_DFW_POLICY_RULE_OP |
|
日志内容 |
Deleted DFW policy rule “$1”. |
|
参数解释 |
$1：分布式防火墙策略或子策略规则的名称 |
|
举例 |
Deleted DFW policy rule “rule1”. |
|
日志说明 |
用户进行了删除分布式防火墙策略规则或子策略规则的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The specified resource doesn't exist：指定的资源不存在 · The rule does not belong to any DFW policy：该规则不属于任何策略 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_DFW_IPSET_OP |
|
日志内容 |
Created DFW IP set “$1”. |
|
参数解释 |
$1：分布式防火墙IP地址集的名称 |
|
举例 |
Created DFW IP set “set1”. |
|
日志说明 |
用户进行了创建分布式防火墙IP地址集的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The IP set ID is invalid：非法的IP地址集ID · The IP set already exists：该IP地址集已存在 · The IP set name cannot exceed 255 characters：IP地址集名称长度不能超过255字符 · The IP set type is invalid：非法的IP地址集类型 · The maximum number of IP set rules is invalid：非法的最大条目数 · IP sets created in bulk cannot use the same ID：批量创建的IP地址集的ID存在重复 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_DFW_IPSET_OP |
|
日志内容 |
Updated DFW IP set “$1”. |
|
参数解释 |
$1：分布式防火墙IP地址集的名称 |
|
举例 |
Updated DFW IP set “set1”. |
|
日志说明 |
用户进行了修改分布式防火墙IP地址集的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The IP set ID is required：未指定IP地址集ID · The IP set does not exist：指定的IP地址集不存在 · The IP set name cannot exceed 255 characters：IP地址集名称长度不能超过255字符 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_DFW_IPSET_OP |
|
日志内容 |
Deleted DFW IP set “$1”. |
|
参数解释 |
$1：分布式防火墙IP地址集的名称 |
|
举例 |
Deleted DFW IP set “set1”. |
|
日志说明 |
用户进行了删除分布式防火墙IP地址集的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The specified resource doesn't exist：指定的资源不存在 · The IP set is used by a policy rule：该IP地址集正在被策略的规则引用 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_DFW_IPSET_RULE_OP |
|
日志内容 |
Created DFW IP set rule “$1”. |
|
参数解释 |
$1：分布式防火墙IP地址集规则的名称 |
|
举例 |
Created DFW IP set rule “rule1”. |
|
日志说明 |
用户进行了创建分布式防火墙IP地址集规则的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The IP set rule ID is invalid：非法的IP地址集规则ID · The IP set rule already exists：指定的IP地址集规则已存在 · The IP set ID is required：未指定规则所属的IP地址集ID · The IP set does not exist：指定的IP地址集不存在 · The CIDR is required：未指定CIDR · Invalid CIDR：无效的CIDR · The ICMP type is required：未指定ICMP报文类型 · The ICMP code is required：未指定ICMP代码 · Invalid ICMP type：无效的ICMP报文类型 · Invalid ICMP code：无效的ICMP代码 · The protocol type is invalid：非法的协议类型 · You cannot specify a protocol type for a Net IP set：Net类型的IP地址集无法指定协议类型 · The IP set rule overlaps with another rule：IP地址集规则与其它规则重叠 · The number of IP set rules exceeds the limit：IP地址集容量不足，超出指定的最大条目数 · IP set rules created in bulk cannot use the same ID：批量创建的IP地址集规则的ID存在重复 · The IP set rule name cannot exceed 255 characters：IP地址集名称不能超过255个字符 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_DFW_IPSET_RULE_OP |
|
日志内容 |
Deleted DFW IP set rule “$1”. |
|
参数解释 |
$1：分布式防火墙IP地址集规则的名称 |
|
举例 |
Deleted DFW IP set rule “rule1”. |
|
日志说明 |
用户进行了删除分布式防火墙IP地址集规则的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The specified resource doesn't exist：指定的资源不存在 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
TRACK_FLOWENTRY_IP_PACKET_OP |
|
日志内容 |
Tracked the flow entries of an IP packet on $1. |
|
参数解释 |
$1：报文所在主机的IP地址 |
|
举例 |
Tracked the flow entries of an IP packet on 172.16.1.1. |
|
日志说明 |
用户进行了获取IP报文在主机上流表轨迹的操作 |
|
失败原因 |
· The request is invalid：传入的JSON串错误 · The host IP address is required：未指定主机IP地址 · Invalid host IP address：无效的主机IP地址 · The OpenFlow input port number is required：未指定OpenFlow入端口号 · Invalid OpenFlow input port number：无效的OpenFlow入端口号 · Supported packet type is IP, TCP, UDP, or ICMP：报文类型只能为IP、TCP、UDP或ICMP · Invalid VXLAN ID：无效的VXLAN ID · The source IP address is required：未指定源IP地址 · Invalid source IP address：无效的源IP地址 · The destination IP address is required：未指定目的IP地址 · Invalid destination IP address：无效的目的IP地址 · Invalid source MAC address：无效的源MAC地址 · Invalid destination MAC address：无效的目的MAC地址 · Invalid source port number：无效的源端口号 · Invalid destination port number：无效的目的端口号 · Invalid ICMP message type：无效的ICMP消息类型 · Invalid ICMP message code：无效的ICMP消息码 · Only ICMP packets support the ICMP message type and code configurations：仅报文类型为ICMP时支持配置ICMP消息类型和ICMP消息码 · Only TCP or UDP packets support the source and destination port number configurations：仅报文类型为TCP或UDP时支持配置源端口号和目的端口号 · Invalid SSH port number：无效的SSH端口号 · The username is required：未指定用户名 · The password is required：未指定密码 · The username cannot exceed 255 characters：用户名最长255个字符 · The password cannot exceed 255 characters：密码最长255个字符 · Tracking the flow entries of packets is not supported on a host with a stateful flow table deployed by the controller：已下发带状态流表的主机不支持流表轨迹功能 · SSH connection failed：SSH连接建立失败 · Error username or password：用户名或密码错误 · Tracking the flow entries of packets is supported only on an online host installed with S1020V：仅安装S1020V的已上线主机支持流表轨迹功能 · The port has not come online on the specified host：该端口未在指定的主机上线 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 · Invalid NS packet type：无效的NS报文类型 · The NS packet type cannot be empty if the packet type is ICMP and the ICMP packet type is 135：当报文类型为ICMP且type为135时，NS报文类型不能为空 · Invalid target address：无效的Target Address · The target address cannot be empty if the packet type is ICMP and the ICMP packet type is 135：当报文类型为ICMP且type为135时，Target Address不能为空 · The target address must be global unicast address or link local address：Target Address必须是IPv6全球单播地址或链路本地地址 |
|
关键字 |
TRACK_FLOWENTRY_ARP_PACKET__OP |
|
日志内容 |
Tracked the flow entries of an ARP packet on $1. |
|
参数解释 |
$1：报文所在主机的IP地址 |
|
举例 |
Tracked the flow entries of an ARP packet on 172.16.1.1. |
|
日志说明 |
用户进行了获取ARP报文在主机上的流表轨迹的操作 |
|
失败原因 |
· The request is invalid：传入的JSON串错误 · The host IP address is required：未指定主机IP地址 · Invalid host IP address：无效的主机IP地址 · The OpenFlow input port number is required：未指定OpenFlow入端口号 · Invalid OpenFlow input port number：无效的OpenFlow入端口号 · Invalid VXLAN ID：无效的VXLAN ID · The source IP address is required：未指定源IP地址 · Invalid source IP address：无效的源IP地址 · The destination IP address is required：未指定目的IP地址 · Invalid destination IP address：无效的目的IP地址 · Invalid source MAC address：无效的源MAC地址 · Invalid destination MAC address：无效的目的MAC地址 · The ARP message type is required：未指定ARP报文类型 · Invalid ARP message type：无效的ARP报文类型 · Invalid sender MAC address：无效的发送端MAC地址 · Invalid target MAC address：无效的目标MAC地址 · Invalid SSH port number：无效的SSH端口号 · The username is required：未指定用户名 · The password is required：未指定密码 · The username cannot exceed 255 characters：用户名最长255个字符 · The password cannot exceed 255 characters：密码最长255个字符 · Tracking the flow entries of packets is not supported on a host with a stateful flow table deployed by the controller：已下发带状态流表的主机不支持流表轨迹功能 · SSH connection failed：SSH连接建立失败 · Error username or password：用户名或密码错误 · Tracking the flow entries of packets is supported only on an online host installed with S1020V：仅安装S1020V的已上线主机支持流表轨迹功能 · The port has not come online on the specified host：该端口未在指定的主机上线 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
START_OPENFLOW_AUDIT_OP |
|
日志内容 |
Started auditing $1 on host $2. |
|
参数解释 |
$1：审计的对象 $2：主机的IP地址 |
|
举例 |
Started auditing [flow tables, group tables] on host 1.1.1.1. |
|
日志说明 |
用户进行了审计主机的流表或组表的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · Invalid IP address：无效的IP地址 · The host has not established an OpenFlow connection to the controller：该主机与控制组件未建立OpenFlow连接 · The device does not support data synchronization or audit because of the device type restriction：因设备类型限制，该设备不支持数据同步和审计 · The host is not connected to the master controller. Please try again later：主机的主用控制组件未连接，请稍后重试 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
START_OPENFLOW_ DATA_SYNCHRONIZATION_OP |
|
日志内容 |
Started synchronizing $1 to host $2. |
|
参数解释 |
$1：数据同步的对象 $2：主机的IP地址 |
|
举例 |
Started synchronizing [flow tables, group tables] to host 1.1.1.2. |
|
日志说明 |
用户进行了数据同步主机的流表或组表的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · Invalid IP address：无效的IP地址 · The host has not established an OpenFlow connection to the controller：该主机与控制组件未建立OpenFlow连接 · The device does not support data synchronization or audit because of the device type restriction：因设备类型限制，该设备不支持数据同步和审计 · The host is not connected to the master controller. Please try again later：主机的主用控制组件未连接，请稍后重试 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
START_OVSDB_AUDIT_OP |
|
日志内容 |
Started auditing “$1” on host “$2” |
|
参数解释 |
$1：对全部模块进行审计或无法解析模块时，该值为OVSDB；当对部分模块进行审计时，该值为OVSDB[模块名]，例如OVSDB[MTU,QoS] $2：主机的IP地址 |
|
举例 |
Started auditing “OVSDB[MTU,QoS]” on host “1.1.1.1”. |
|
日志说明 |
用户进行了审计主机OVSDB配置的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · Invalid IP address：无效的IP地址 · The host has not established an OpenFlow connection to the controller：该主机与控制组件未建立OpenFlow连接 · The device does not support data synchronization or audit because of the device type restriction：因设备类型限制，该设备不支持数据同步和审计 · The host is not connected to the master controller. Please try again later：主机的主用控制组件未连接，请稍后重试 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
START_OVSDB_DATA_SYNCHRONIZATION_OP |
|
日志内容 |
Started synchronizing “$1” on host “$2”. |
|
参数解释 |
$1：对全部模块进行数据同步或无法解析模块时，该值为OVSDB；当对部分模块进行数据同步时，该值为OVSDB[模块名]，例如OVSDB[MTU,QoS] $2：主机的IP地址 |
|
举例 |
Started synchronizing “OVSDB[MTU,QoS]” on host “1.1.1.2”. |
|
日志说明 |
用户进行了数据同步主机的OVSDB配置的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · Invalid IP address：无效的IP地址 · The host has not established an OpenFlow connection to the controller：该主机与控制组件未建立OpenFlow连接 · The device does not support data synchronization or audit because of the device type restriction：因设备类型限制，该设备不支持数据同步和审计 · The host is not connected to the master controller. Please try again later：主机的主用控制组件未连接，请稍后重试 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
START_DHCP_CONFIG_AUDIT_OP |
|
日志内容 |
Started auditing DHCP configuration on host $1. |
|
参数解释 |
$1：主机的IP地址 |
|
举例 |
Started auditing DHCP configuration on host 1.1.1.1. |
|
日志说明 |
用户进行了审计主机的DHCP配置数据的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration restoration is in progress：配置恢复未完成 · Invalid IP address：无效的IP地址 · The host has not established a WebSocket connection to the controller：该主机与控制组件未建立WebSocket连接 · The device model does not support data synchronization or audit because of the device type restriction：因设备类型限制，该设备不支持数据同步和审计 · The system is synchronizing or auditing data for the host：平滑或审计流程未结束 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
START_DHCP_CONFIG_SYNCHRONIZATION_OP |
|
日志内容 |
Started synchronizing DHCP configuration to host $1. |
|
参数解释 |
$1：主机的IP地址 |
|
举例 |
Started synchronizing DHCP configuration to host 1.1.1.2. |
|
日志说明 |
用户进行了数据同步主机的DHCP配置数据的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration restoration is in progress：配置恢复未完成 · Invalid IP address：无效的IP地址 · The host has not established a WebSocket connection to the controller：该主机与控制组件未建立WebSocket连接 · The device model does not support data synchronization or audit because of the device type restriction：因设备类型限制，该设备不支持数据同步和审计 · The system is synchronizing or auditing data for the host：平滑或审计流程未结束 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_STATICLINK_OP |
|
日志内容 |
Created static link “$1”. |
|
参数解释 |
$1：静态Link名称 |
|
举例 |
Created static link “link1”. |
|
日志说明 |
用户进行了创建静态Link的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The request is invalid：传入的JSON串错误 · The system name is required：Netoverlay主机名称不能为空 · The system name cannot exceed 255 characters：Netoverlay主机名称长度不能超过255个字符 · The device IP is required：设备IP不能为空 · The device IP is invalid：设备IP不合法 · The abbreviated access port name is required：接入端口简称不能为空 · The abbreviated access port name cannot exceed 255 characters：接入端口简称长度不能超过255个字符 · The static link already exists：静态Link已存在 · The netoverlay host contains duplicate static link：指定的Netoverlay主机包含重复的静态Link · Unknown error：未知错误 · The static link created in bulk cannot use the same ID：批量创建的静态Link存在重复的ID。 · You have no privilege to perform this operation：用户无权限执行此操作 · The access interface of a static link cannot be an AC interface in the resource access template：静态link的接入口不能是资源接入模版的AC口 |
|
关键字 |
DELETE_STATICLINK_OP |
|
日志内容 |
Deleted static link “$1”. |
|
参数解释 |
$1：静态Link名称 |
|
举例 |
Deleted static link “link1”. |
|
日志说明 |
用户进行了删除静态Link的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The specified resource doesn't exist：指定的资源不存在 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 · Cannot delete static link because it was created on VMM：不允许删除来源为VMM的静态Link |
|
关键字 |
CREATE_VROUTERCONNECTION_OP |
|
日志内容 |
Created vRouter interconnection "$1". |
|
参数解释 |
$1：虚拟路由器连接的名称 |
|
举例 |
Created vRouter interconnection "vpc 01". |
|
日志说明 |
用户进行了创建虚拟路由器连接的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The vRouter interconnection ID already exists：虚拟路由器连接ID已经存在 · The tenant ID is required：租户ID不能为空 · The tenant does not exist：租户不存在 · The local vRouter ID is required：本端虚拟路由器ID不能为空 · The remote vRouter ID is required：对端虚拟路由器ID不能为空 · The local vRouter does not exist：本端虚拟路由器不存在 · The remote vRouter does not exist：对端虚拟路由器不存在 · The local subnet ID is required：本端虚拟子网ID不能为空 · The remote subnet ID is required：对端虚拟子网ID不能为空 · The local subnet list contains nonexistent subnets：本端子网列表中包含不存在的子网 · The remote subnet list contains nonexistent subnets：对端子网列表中包含不存在的子网 · A remote subnet of the vRouter interconnection overlaps with a remote subnet of a Layer 3 DC interconnection. The subnet of the vRouter interconnection must cover the overlapping subnet of the Layer 3 DC interconnection：虚拟路由器连接的对端子网范围必须大于数据中心三层互联同网段的远端网段范围 · The local vRouter and the remote vRouter cannot be the same：本端虚拟路由器与对端虚拟路由器重复 · The local subnets overlap with the subnets of the remote vRouter：本端虚拟子网与对端虚拟路由器的虚拟子网发生重叠 · The remote subnets overlap with the subnets of the local vRouter：对端虚拟子网与本端虚拟路由器的虚拟子网发生重叠 · The vRouter interconnection already exists：虚拟路由器连接配置已存在 · The status field is a read-only field：status为只读字段 · The vRouter interconnection name cannot exceed 255 characters：虚拟路由器连接名称不能大于255个字符 · The vRouter interconnection description cannot exceed 255 characters：虚拟路由器连接描述不能大于255个字符 · The network to which the remote subnet belongs cannot be a VLAN：对端子网所属的虚拟链路层网络不能为VLAN类型 · The remote subnet cannot be an external subnet：对端子网不能为外网子网 · The network to which the local subnet belongs cannot be a VLAN：本端子网所属的虚拟链路层网络不能为VLAN类型 · The local subnet cannot be an external subnet：本端子网不能为外网子网 · If a vRouter is bound to multiple vRouter interconnections, the selected subnets of the other vRouters bound to these vRouter interconnections cannot overlap：多个虚拟路由器连接绑定同一虚拟路由器时，连接绑定的另一个虚拟路由器之间的已选子网不能重叠 · The vRouter link is enabled with the firewall feature. You can add only vRouters that are bound to a single-member gateway to the vRouter link：虚拟路由器连接已启用防火墙，指定的虚拟路由器只能绑定一个出口网关，且出口网关只能为单成员 · Unknown error：未知错误 · The source IP address of a route entry with a vPort-type next hop on the vRouter cannot overlap with any vNetwork subnet on another vRouter：建立虚拟路由器连接的两个虚拟路由器，一个虚拟路由器下虚拟端口类型的路由表项的源IP不允许和另一个虚拟路由器下虚拟链路层网络的子网重叠 · The source IP address of a route entry with a vPort-type next hop on the vRouter cannot overlap with any external subnet on another vRouter：建立虚拟路由器连接的两个虚拟路由器，一个虚拟路由器下虚拟端口类型的路由表项的源IP不允许和另一个虚拟路由器下外部网络的子网重叠 · The source IP address of a route entry with a vPort-type next hop on the vRouter cannot be the same as any vNetwork subnet gateway IP of another vRouter：建立虚拟路由器连接的两个虚拟路由器，一个虚拟路由器下虚拟端口类型的路由表项的源IP不允许和另一个虚拟路由器下虚拟链路层网络子网的网关IP地址相同 · The value of the firewallenable field must be true (case sensitive) or false (case sensitive)：firewallenable字段取值必须为true或false，且区分大小写 · The local_router and peer_router fields must be configured：local_router和peer_router字段不允许为空 · The value of the mode field is invalid：mode字段取值不合法 · When the value of the Mode field is 1, local subnets and remote subnets are not supported：MODE为1时，不支持local_subnets和peer_subnets字段 · Local CIDRs cannot overlap with remote subnets：本端网段和对端路由器下的所有子网不允许重叠 · The local vRouter has established links with multiple vRouters and the CIDRs specified for the peer vRouters of the local vRouter cannot overlap：本端虚拟路由器与多个虚拟路由器建立连接时，不支持目的网段重叠 · Local subnets cannot overlap with remote subnets：本端路由器子网和对端路由器子网的网段不允许重叠 · Local CIDRs cannot overlap with remote CIDRs：本端网段和对端网段不允许重叠 · Invalid subnet mask：掩码位非法 · Invalid IP address：无效的IP地址 · The remote vRouter has established links with multiple vRouters and the CIDRs specified for the peer vRouters of the remote vRouter cannot overlap：对端虚拟路由器与多个虚拟路由器建立连接时，不支持目的网段重叠 · When the value of the Mode field is 1, local CIDRs are required：MODE为1时，本端网段不能为空 · When the value of the Mode field is 1, remote CIDRs are required：MODE为1时，远端网段不能为空 · Duplicated CIDRs exist in local or remote CIDRs：本端网段/远端网段中存在网段重叠 · When the network cloud feature is off, the mode value cannot be 1：网络云场景关闭时，mode字段不允许配置为1 · You have no privilege to perform this operation：用户无权限执行此操作 · The vRouter link is disabled with the firewall feature. The border gateways for the local and remote vRouters must be bound to the same device group：防火墙关闭场景下，虚拟路由器连接本端和对端虚拟路由器所绑定的出口网关必须绑定相同的设备组 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · The VLAN range pool does not exist or no VLAN IDs are available in the VLAN range pool：指定的租户承载网类型的VLAN池不存在，或该VLAN池内没有足够的VLAN ID · The address pool does not exist or no IPv4 or IPv6 addresses are available in the address pool：指定的地址池不存在，或该地址池内没有可用的IPv4/IPv6地址 · The vRouter link is enabled with the firewall feature. You can add only vRouters that are bound to a single-member gateway to the vRouter link：虚拟路由器连接已启用防火墙，指定的虚拟路由器只能绑定一个出口网关，且出口网关只能为单成员 · You can add only vRouters that are bound to a single-member gateway to the vRouter link：指定的虚拟路由器只能绑定一个出口网关，且出口网关只能为单成员 · If the two vRouters of a vRouter link are in different fabrics, you must configure these fabrics with device groups used for fabric interconnect deployment：虚拟路由器互联两端的虚拟路由器跨Fabric时，需配置网络位置为Fabric间互通的设备组 · Remote CIDRs cannot overlap with local subnets：对端网段和本端路由器下的所有子网不允许重叠 · Local subnets cannot overlap with local cidrs：本端子网和本端网段不允许重叠 · Peer subnets cannot overlap with peer cidrs：对端子网和对端网段不允许重叠 · You must specify local subnets, local CIDRs, or both：本端子网和本端网段不允许同时为空 · You must specify remote subnets, remote CIDRs, or both：对端子网和对端网段不允许同时为空 · If the firewall feature is enabled for only one vRouter on the vRouter link, you must bind a firewall to that vRouter：本端或对端防火墙开关开启时，虚拟路由器必须绑定防火墙 · You must bind a gateway to both the local and remote vRouters：本端和对端虚拟路由器必须绑定网关 · When the firewall mode is normal, the vRouter type cannot be PBR：防火墙Mode为NORMAL时，虚拟路由器不支持PBR类型 · When the firewall mode is normal, the local and remote vRouters cannot both be transit nodes：防火墙Mode为NORMAL时，不支持本端虚拟路由器和对端虚拟路由器同时为Transit类型 · You cannot enable the firewall feature for the remote vRouter, because the remote vRouter type is transit：对端虚拟路由器类型为TRANSIT时，不支持开启防火墙 · You cannot enable the firewall feature for the local vRouter, because the local vRouter type is transit：本端虚拟路由器类型为TRANSIT时，不支持开启防火墙 · You cannot advertise all remote networks：当前不支持开启发布对端所有路由 · You cannot advertise all local networks：当前不支持开启发布本端所有路由 · The subnet parameter and CIDR network parameter must both be null for a transit vRouter：Transit类型虚拟路由器子网和网段必须同时为null · The subnet parameter and CIDR network parameter cannot both be null for a normal vRouter：Normal类型虚拟路由器子网和网段不允许同时为null · If the normal vRouter on a vRouter link advertises all networks, the transit vRouter on the vRouter link must also advertise all networks：NORMAL虚拟路由器发布所有路由字段为开启时，TRANSIT虚拟路由器发布所有路由字段不支持关闭 · If a transit vRouter has been used to create a firewall protected VPC connection, the vRouter cannot be used to create VPC connection disabled with the firewall feature, and vice versa：同一Transit虚拟路由器不支持同时创建过墙与不过墙两种类型的VPC互通 · The normal vRouter in a transit VPC enabled with the firewall feature must be bound to a DCI-capable gateway or firewall：在过墙Transit VPC中,NORMAL类型的虚拟路由器没有绑定具有DCI能力的网关或防火墙 · The normal vRouter in a transit VPC without firewall protection or the tenant of the vRouter must be bound to a gateway with the DCI capability：在不过墙Transit VPC中,NORMAL类型的虚拟路由器或所属租户没有绑定具有DCI能力的网关 · When you advertise all local networks, the subnet parameter and CIDR network parameter must both be null for the local vRouter：发布本端所有路由开启时，本端虚拟路由器子网和网段必须同时为null · When you advertise all remote networks, the subnet parameter and CIDR network parameter must both be null for the remote vRouter：发布对端所有路由开启时，对端虚拟路由器子网和网段必须同时为null · The subnet parameter and CIDR network parameter cannot both be null for the remote vRouter：对端虚拟路由器子网和网段不允许同时为null · The vRouter is not bound to a firewall：虚拟路由器没有绑定防火墙资源 · The specified tenant carrier network VLAN pool does not exist or the VLAN pool does not have sufficient VLAN IDs：指定的租户承载网类型的VLAN池不存在，或VLAN池内VLAN ID不足 · When a vRouter link is established between a normal vRouter and a transit vRouter, you cannot enable the advertising all networks feature for the normal vRouter when the advertising all networks feature is disabled for the transit vRouter：不支持NORMAL虚拟路由器端发布所有路由开启且TRANSIT虚拟路由器端发布所有路由关闭 · The manually specified networks cannot overlap with external subnets bound to the vRouter：手动输入网段不能与虚拟路由器绑定的外网子网网段重叠 · If a centralized-mode vRouter link, routing table, and Layer 3 DCI are attached to the same vRouter, you cannot specify the same subnet as a remote CIDR, destination subnet, and remote subnet for them, respectively：当集中式虚拟路由器连接、路由表和数据中心三层互联关联同一个虚拟路由器时，对端网段、目的网段和远端网段不能相同 · In non-network cloud scenarios, you can enable route reduction for a centralized-mode vRouter link only when the peer vRouters are normal type and the firewalls are disabled at both ends of the link：非网络云场景下，集中式虚拟路由器连接本端和对端防火墙都为关闭，且本端和对端虚拟路由器类型为NORMAL时，才允许开启路由精简开关 · You cannot enable route reduction in the network cloud scenario：网络云场景下，不允许开启路由精简开关 · Incorrect configuration for the host route advertisement feature：当前配置下，发布主机路由开关取值错误 · An external transit vRouter, The local vRouter and the peer vRouter must bind the same gateway：集中式虚拟路由器连接绑定EXTERNALTRANSIT类型虚拟路由器时，本端虚拟路由器和对端虚拟路由器绑定的出口网关必须相同 · The local vRouter cannot be an external transit vRouter：本端虚拟路由器类型不能为EXTERNALTRANSIT类型 · You must bind a gateway to the local vRouter enabled with the firewall feature：本端防火墙开关开启时，本端虚拟路由器必须绑定网关 · When the value for the Mode field is NORMAL, the vRouter type of either the local vRouter or remote vRouter must be NORMAL：MODE为NORMAL时，不支持本端虚拟路由器和对端虚拟路由器的类型同时为非NORMAL类型 · You cannot modify the configuration for the host route advertisement feature if the type of the peer vRouter is normal：对端虚拟路由器类型是NORMAL类型，不支持修改发布主机路由开 · You must bind a firewall to the local vRouter enabled with the firewall feature：本端防火墙开关开启时，本端虚拟路由器必须绑定防火墙 · If the external transit vRouter is the remote vRouter in a centralized vRouter link, you must enable advertisement of all remote routes：集中式虚拟路由器连接绑定EXTERNALTRANSIT类型虚拟路由器时，发布对端所有路由开关 必须开启 · An external transit vRouter, you must disable the remote firewall：集中式虚拟路由器连接绑定EXTERNALTRANSIT类型虚拟路由器时，对端防火墙必须关闭 · The remote vRouter cannot be an external transit vRouter：对端虚拟路由器类型不能为EXTERNALTRANSIT类型 · The tenant has not bind dci gateway：集中式虚拟路由器连接绑定EXTERNALTRANSIT类型虚拟路由器时，租户必须绑定具有DCI能力的网关 · You must configure multi-DC internal subnets for an external transit vRouter if the vRouter is in a centralized vRouter link and uses firewall as the edge device to external networks：集中式虚拟路由器连接绑定EXTERNALTRANSIT类型虚拟路由器，且虚拟路由器外网出口设备为防火墙时，EXTERNALTRANSIT类型虚拟路由器的多数据中心内网网段信息不能为空 · If the remote vRouter in a centralized vRouter link is an external transit vRouter, the firewall feature must be disabled for the remote vRouter：集中式虚拟路由器连接绑定EXTERNALTRANSIT类型虚拟路由器时，对端防火墙必须关闭 · If the local vRouter in a centralized vRouter link is enabled with the firewall feature, the device group position of the border gateways bound to the vRouter must include border gateway and DC interconnection：集中式虚拟路由器连接本端防火墙开启时，本端虚拟路由器必须绑定设备组网络位置包含出口网关和DC间互联的出口网关 · The remote vRouter for a centralized-mode vRouter link cannot have a default subnet included in its external subnets if the following conditions exist: 1. The remote vRouter is an external transit vRouter. 2. A border gateway with gateway sharing disabled is already bound to the local vRouter：EXTERNALTRANSIT类型集中式虚拟路由器连接，本端虚拟路由器已绑定非共享出口网关，多数据中心外网网段信息不能包含默认网段 · If the remote end of a centralized-mode vRouter link is an external transit vRouter, the destination subnets in the route entries for the local vRouter cannot overlap with the external subnets specified for the remote vRouter：EXTERNALTRANSIT类型集中式虚拟路由器连接，本端虚拟路由器绑定的路由表项的目的网段与多数据中心外网网段信息不能重叠 · Local CIDRs cannot overlap with the external subnets specified for the remote vRouter：本端网段和对端路由器多数据中心外网网段信息不允许重叠 · If the remote end of a centralized-mode vRouter link is an external transit vRouter, you must disable the local vRouter from advertising loacl host routes：集中式虚拟路由器连接绑定EXTERNALTRANSIT类型虚拟路由器时，发布本端所有路由开关必须关闭 · Overlapping items are not allowed in the information configuration of the external network segment of the multi data center of different transitvrouter corresponding to the same tenant virtual router in the VPC：同一个虚拟路由器与不同的EXTERNALTRANSIT类型虚拟路由器建立集中式虚拟路由器连接，EXTERNALTRANSIT类型虚拟路由器间的多数据中心外网网段信息存在子网网段重叠 · When the remote vRouter in a centralized-mode vRouter link is an external transit vRouter and the local vRouter is not enabled with the firewall service, make sure one of the following requirements is met: ¡ The local vRouter is bound to a DCI-capable border gateway. ¡ The tenant of the local vRouter is bound to a border gateway used only for DC interconnection or fabric interconnection and DC interconnection. 集中式虚拟路由器连接绑定EXTERNALTRANSIT类型虚拟路由器且本端防火墙关闭时，本端虚拟路由器必须绑定具有DCI能力的出口网关或租户必须绑定设备组网络位置仅为DC间互联或者Fabric间互通+DC间互联的出口网关 · When no CIDRs are specified, the internal subnet specified for the local vRouter cannot overlap with the access subnet for the firewall bound to the remote vRouter：未指定CIDR时，本端虚拟路由器的内网子网和对端虚拟路由器的防火墙接入网段重叠 · When you specify CIDRs for the local and remote vRouters, the local CIDRs cannot overlap with the access subnet for the firewall bound to the remote vRouter：指定CIDR时，本端的CIDR和对端虚拟路由器的防火墙接入网段重叠 · The access subnet for the firewall bound to the vRouter cannot include the source IP address in any route entry：虚拟路由器的防火墙接入网段和源IP地址重叠 · The access subnet for the firewall bound to each end in the centralized vRouter link cannot include the source IP address in any route entry：集中式虚拟路由器连接中虚拟路由器的防火墙接入网段和源IP地址存在重叠 · The local CIDRs and subnets cannot overlap with the access subnet for the firewall bound to the remote vRouter：本端的CIDR和子网与对端虚拟路由器的防火墙接入网段存在重叠 · The remote CIDRs and subnets cannot overlap with the access subnet for the firewall bound to the local vRouter：对端的CIDR和子网与本端虚拟路由器的防火墙接入网段存在重叠 · If you enable firewall for both ends in the vRouter link, they must use the same firewall service type：集中式虚拟路由器连接两端的防火墙开关开启时，两端防火墙类型必须一致 · If you enable firewall for one end in the vRouter link, the firewall service type specified for that end cannot be service leaf：集中式虚拟路由器连接一端的防火墙开关开启时，其防火墙必须为非Service Leaf类型 · If the following conditions exist, you must enable route reduction for a centralized vRouter link: ¡ You have disabled firewall for both ends in the vRouter link. ¡ One end is using service leaf firewall services. 集中式虚拟路由器连接两端的防火墙开关关闭，且一端的虚拟路由器绑定了Service Leaf类型防火墙和外部网络时，路由精简开关必须开启 · If a transit vRouter is bound to the vRouter link and a vRouter in that link is enabled with firewall, the firewall service type specified for the vRouter cannot be service leaf：集中式虚拟路由器连接绑定TRANSIT类型虚拟路由器时，防火墙开关开启侧的虚拟路由器不允许绑定Service Leaf类型防火墙 For a centralized vRouter link, you must bind border gateways to the local and remote vRouters when both the local and remote firewalls are off and service leaf firewalls are bound to the vRouters：当集中式虚拟路由器连接的两端防火墙关闭，且两个虚拟路由器同时绑定Service Leaf防火墙时，本端和对端虚拟路由器必须绑定出口网关 · To connect a normal-type vRouter to multiple remote vRouters of any types, make sure the destination subnets specified for the remote vRouters do not overlap：NORMAL类型虚拟路由器与多个虚拟路由器（不限定类型）建立连接时，目的网段不能重叠 · When you configure a centralized VAS vRouter link, configure the role of the local firewall as primary or secondary. The role of the local firewall cannot be both primary and secondary：集中式VAS VPC互通场景，本端防火墙配置角色主和备不能同时配置也不能同时为空 · When you configure a centralized non-VAS vRouter link, you cannot configure the role of the local firewall：非集中式VAS VPC互通场景，本端防火墙配置角色不能配置 · When you configure a centralized VAS vRouter link, enable the firewall service for the local transit vRouter：集中式VAS VPC互通场景，本端防火墙必须开启 · When you configure a centralized VAS vRouter link, disable the firewall service for the remote transit vRouter：集中式VAS VPC互通场景，对端防火墙必须关闭 · When you edit a centralized VAS vRouter link, you cannot change the role of the local firewall：集中式VAS VPC互通场景，本端防火墙配置角色不支持修改 · When you configure a centralized VAS vRouter link, disable both local route advertisement and remote route advertisement：集中式VAS VPC互通场景，发布本端所有路由和发布对端所有路由开关必须都关闭 · When you configure a centralized VAS vRouter link, the local transit vRouter must be bound to a DCI-capable border gateway and a firewall service resource：集中式VAS VPC互通场景，本端虚拟路由器必须绑定具备DCI能力的出口网关和防火墙资源 · When you configure a centralized VAS vRouter link, make sure the service resource ID of the local firewall is the same as that bound to the local transit vRouter：集中式VAS VPC互通场景，本端防火墙的服务资源ID和本端虚拟路由器绑定的服务资源ID必须一致 · If an east-west transit vRouter link enabled with remote route advertisement shares one transit vRouter with a centralized VAS vRouter link, the following items cannot overlap:1. Destination subnets configured for the route entries on the local vRouter of the east-west transit vRouter link.2. CIDRs configured for the remote vRouter of the centralized VAS vRouter link：TRANSIT类型虚拟路由器分别与两台虚拟路由器建立VAS VPC互通和发布对端所有路由开启的东西向TRANSIT VPC互通，东西向TRANSIT VPC互通的本端虚拟路由器的路由表项目的网段不能与VAS VPC互通的对端虚拟路由器CIDR重叠 · If the following conditions exist, you cannot establish a vRouter link between an external transit vRouter and a transit vRouter: 1. A gateway member of the border gateway bound to the external transit vRouter belongs to the same device group as that of a border gateway bound to the transit vRouter. 2. The tags field of the external transit vRouter is not empty：EXTERNALTRANSIT和TRANSIT类型虚拟路由器绑定的出口网关的出口网关成员关联了同一个设备组，EXTERNALTRANSIT类型虚拟路由器的tags字段不为空时，两者不允许创建虚拟路由器连接 · An external transit vRouter cannot establish vRouter links with both a normal vRouter and a transit vRouter：EXTERNALTRANSIT类型的虚拟路由器不能同时与TRANSIT类型虚拟路由器和NORMAL类型虚拟路由器建立虚拟路由器连接 · L3VNI configuration is supported only in the scenario where either the local or remote firewall is enabled：仅单边过墙场景支持配置L3VNI · RT %s of the vRouter link conflicts with an RT of the vRouter：虚拟路由器连接的互通RT %s与虚拟路由器RT冲突 · RT %s reserved for the vRouter link conflicts with an RT of the vRouter：系统预留的虚拟路由器连接互通RT %s与虚拟路由器RT冲突 · RT %s of the vRouter link conflicts with the import RT of a Layer 3 DC interconnect：虚拟路由器连接的互通RT %s与数据中心三层互联的引入RT冲突 · RT %s reserved for the vRouter link conflicts with the import RT of a Layer 3 DC interconnect：系统预留的虚拟路由器连接互通RT %s与数据中心三层互联的引入RT冲突 · RT %s of the vRouter link conflicts with the export RT of a Layer 3 DC interconnect：虚拟路由器连接的互通RT %s与数据中心三层互联的引出RT冲突 · RT %s reserved for the vRouter link conflicts with the export RT of a Layer 3 DC interconnect：系统预留的虚拟路由器连接互通RT %s与数据中心三层互联的引出RT冲突 · RT %s of the vRouter link conflicts with the import RT of a Layer 2 DC interconnect：虚拟路由器连接的互通RT %s与数据中心二层互联的引入RT冲突 · RT %s reserved for the vRouter link conflicts with the import RT of a Layer 2 DC interconnect：系统预留的虚拟路由器连接互通RT %s与数据中心二层互联的引入RT冲突 · RT %s of the vRouter link conflicts with the export RT of a Layer 2 DC interconnect：虚拟路由器连接的互通RT %s与数据中心二层互联的引出RT冲突 · RT %s reserved for the vRouter link conflicts with the export RT of a Layer 2 DC interconnect：系统预留的虚拟路由器连接互通RT %s与数据中心二层互联的引出RT冲突 · The specified L3VNI is not in the VXLAN pool：指定的L3VNI不在VXLAN池范围内 · Cannot allocate this L3VNI, because synchronization is in progress for the VXLAN pool containing this L3VNI：无法分配该L3VNI，其所在的VXLAN池正在平滑中 · Cannot allocate L3VNIs automatically, because no VXLAN pool is configured：未配置VXLAN池，无法自动分配L3VNI · Cannot allocate L3VNIs automatically, because the VXLAN pool does not have available resources：VXLAN池中资源已耗尽，无法自动分配L3VNI · Cannot allocate L3VNIs automatically. Please verify correctness of the VXLAN pool configuration and status：无法自动分配L3VNI，请检查VXLAN池配置及状态 · The L3VNI is in use：指定的L3VNI已被使用 · The L4-L7 physical resource pool templates bound to the two firewalls must contain vRouter link interfaces if: 1. Both ends of a centralized vRouter link use the firewall service. 2. The contexts created on the two selected firewalls are different：集中式虚拟路由器连接两端防火墙开启且两端防火墙对应的虚拟防火墙不同时，L4-L7物理资源池模板中必须配置跨虚拟路由器互通接口 · You cannot enable the host route advertisement feature if the value for the Mode field is 0 or 1：MODE为0或1时，不允许开启发布主机路由开关 |
|
关键字 |
UPDATE_VROUTERCONNECTION_OP |
|
日志内容 |
Updated vRouter interconnection "$1". |
|
参数解释 |
$1：虚拟路由器连接的名称 |
|
举例 |
Updated vRouter interconnection "vpc ". |
|
日志说明 |
用户进行了修改虚拟路由器连接的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The specified resource doesn't exist：指定的资源不存在 · The status field is a read-only field：status为只读字段 · The local subnetID is required：本端虚拟子网ID不能为空 · The remote subnet ID is required：对端虚拟子网ID不能为空 · The local subnet list contains nonexistent subnets：本端子网列表中包含不存在的子网 · The remote subnet list contains nonexistent subnets：对端子网列表中包含不存在的子网 · The local vRouter cannot be modified：本端虚拟路由器不允许修改 · The remote vRouter cannot be modified：对端虚拟路由器不允许修改 · The tenant cannot be modified：租户不允许修改 · A remote subnet of the vRouter interconnection overlaps with a remote subnet of a Layer 3 DC interconnection. The subnet of the vRouter interconnection must cover the overlapping subnet of the Layer 3 DC interconnection：虚拟路由器互通的对端子网范围必须大于数据中心三层互联同网段的远端子网范围 · The vRouter interconnection name cannot exceed 255 characters：虚拟路由器连接名称不能大于255个字符 · The vRouter interconnection description cannot exceed 255 characters：虚拟路由器连接描述不能大于255个字符 · The network to which the remote subnet belongs cannot be a VLAN：对端子网所属的虚拟链路层网络不能为VLAN类型 · The remote subnet cannot be an external subnet：对端子网不能为外网子网 · The network to which the local subnet belongs cannot be a VLAN：本端子网所属的虚拟链路层网络不能为VLAN类型 · The local subnet cannot be an external subnet：本端子网不能为外网子网 · If a vRouter is bound to multiple vRouter interconnections, the selected subnets of the other vRouters bound to these vRouter interconnections cannot overlap：多个虚拟路由器连接绑定同一虚拟路由器时，连接绑定的另一个虚拟路由器之间的已选子网不能重叠 · Unknown error：未知错误 · The local_router and peer_router fields must be configured：local_router和peer_router字段不允许为空 · When the value of the Mode field is 1, local subnets and remote subnets are not supported：MODE为1时，不支持local_subnets和peer_subnets字段 · Local CIDRs cannot overlap with remote subnets：本端网段和对端路由器下的所有子网不允许重叠 · The local vRouter has established links with multiple vRouters and the CIDRs specified for the peer vRouters of the local vRouter cannot overlap：本端虚拟路由器与多个虚拟路由器建立连接时，不支持目的网段重叠 · Local subnets cannot overlap with remote subnets：本端路由器子网和对端路由器子网的网段不允许重叠 · Local CIDRs cannot overlap with remote CIDRs：本端网段和对端网段不允许重叠 · Cannot edit the local or remote router：不允许修改本端路由器和对端路由器 · Invalid subnet mask：掩码位非法 · Invalid IP address：无效的IP地址 · The remote vRouter has established links with multiple vRouters and the CIDRs specified for the peer vRouters of the remote vRouter cannot overlap：对端虚拟路由器与多个虚拟路由器建立连接时，不支持目的网段重叠 · Remote CIDRs cannot overlap with remote subnets that already have VPC connections：远端网段和本端路由器已建立过VPC连接的子网不允许重叠 · When the value of the Mode field is 1, local CIDRs are required：MODE为1时，本端网段不能为空 · When the value of the Mode field is 1, remote CIDRs are required：MODE为1时，远端网段不能为空 · Duplicated CIDRs exist in local or remote CIDRs：本端网段/远端网段中存在网段重叠 · The mode field cannot be modified：mode字段不允许修改 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · You cannot edit or delete the cloud region name：云区域名称不允许修改或删除 · You cannot change the enabling status of the local or remote firewall：本端或对端防火墙开关不允许修改 · Remote CIDRs cannot overlap with local subnets：对端网段和本端路由器下的所有子网不允许重叠 · Local subnets cannot overlap with local cidrs：本端子网和本端网段不允许重叠 · Peer subnets cannot overlap with peer cidrs：对端子网和对端网段不允许重叠 · You must specify local subnets, local CIDRs, or both：本端子网和本端网段不允许同时为空 · You must specify remote subnets, remote CIDRs, or both：对端子网和对端网段不允许同时为空 · When the firewall mode is normal, the vRouter type cannot be PBR：防火墙Mode为NORMAL时，虚拟路由器不支持PBR类型 · When the firewall mode is normal, the local and remote vRouters cannot both be transit nodes：防火墙Mode为NORMAL时，不支持本端虚拟路由器和对端虚拟路由器同时为Transit类型 · You cannot enable the firewall feature for the remote vRouter, because the remote vRouter type is transit：对端虚拟路由器类型为TRANSIT时，不支持开启防火墙 · You cannot enable the firewall feature for the local vRouter, because the local vRouter type is transit：本端虚拟路由器类型为TRANSIT时，不支持开启防火墙 · You cannot advertise all remote networks：当前不支持开启发布对端所有路由 · You cannot advertise all local networks：当前不支持开启发布本端所有路由 · The subnet parameter and CIDR network parameter must both be null for a transit vRouter：Transit类型虚拟路由器子网和网段必须同时为null · The subnet parameter and CIDR network parameter cannot both be null for a normal vRouter：Normal类型虚拟路由器子网和网段不允许同时为null · If the normal vRouter on a vRouter link advertises all networks, the transit vRouter on the vRouter link must also advertise all networks：NORMAL虚拟路由器发布所有路由字段为开启时，TRANSIT虚拟路由器发布所有路由字段不支持关闭 · If a transit vRouter has been used to create a firewall protected VPC connection, the vRouter cannot be used to create VPC connection disabled with the firewall feature, and vice versa：同一Transit虚拟路由器不支持同时创建过墙与不过墙两种类型的VPC互通 · The normal vRouter in a transit VPC enabled with the firewall feature must be bound to a DCI-capable gateway or firewall：在过墙Transit VPC中,NORMAL类型的虚拟路由器没有绑定具有DCI能力的网关或防火墙 · The normal vRouter in a transit VPC without firewall protection or the tenant of the vRouter must be bound to a gateway with the DCI capability：在不过墙Transit VPC中,NORMAL类型的虚拟路由器或所属租户没有绑定具有DCI能力的网关 · When you advertise all local networks, the subnet parameter and CIDR network parameter must both be null for the local vRouter：发布本端所有路由开启时，本端虚拟路由器子网和网段必须同时为null · When you advertise all remote networks, the subnet parameter and CIDR network parameter must both be null for the remote vRouter：发布对端所有路由开启时，对端虚拟路由器子网和网段必须同时为null · The subnet parameter and CIDR network parameter cannot both be null for the remote vRouter：对端虚拟路由器子网和网段不允许同时为null · The vRouter is not bound to a firewall：虚拟路由器没有绑定防火墙资源 · The firewall enabling state cannot be changed：防火墙开关不支持修改 · When a vRouter link is established between a normal vRouter and a transit vRouter, you cannot enable the advertising all networks feature for the normal vRouter when the advertising all networks feature is disabled for the transit vRouter：不支持NORMAL虚拟路由器端发布所有路由开启且TRANSIT虚拟路由器端发布所有路由关闭 · The manually specified networks cannot overlap with external subnets bound to the vRouter：手动输入网段不能与虚拟路由器绑定的外网子网网段重叠 · If a centralized-mode vRouter link, routing table, and Layer 3 DCI are attached to the same vRouter, you cannot specify the same subnet as a remote CIDR, destination subnet, and remote subnet for them, respectively：当集中式虚拟路由器连接、路由表和数据中心三层互联关联同一个虚拟路由器时，对端网段、目的网段和远端网段不能相同 · You cannot enable route reduction in the network cloud scenario：网络云场景下，不允许开启路由精简开关 · In non-network cloud scenarios, you can enable route reduction for a centralized-mode vRouter link only when the peer vRouters are normal type and the firewalls are disabled at both ends of the link：非网络云场景下，集中式虚拟路由器连接本端和对端防火墙都为关闭，且本端和对端虚拟路由器类型为NORMAL时，才允许开启路由精简开关 · Incorrect configuration for the host route advertisement feature：当前配置下，发布主机路由开关取值错误 · You cannot modify the configuration for the host route advertisement feature if the type of the peer vRouter is normal：对端虚拟路由器类型是NORMAL类型，不支持修改发布主机路由开关 · If the external transit vRouter is the remote vRouter in a centralized vRouter link, you must enable advertisement of all remote routes：集中式虚拟路由器连接绑定EXTERNALTRANSIT类型虚拟路由器时，发布对端所有路由开关必须开启 · Local CIDRs cannot overlap with the external subnets specified for the remote vRouter：本端网段和对端路由器多数据中心外网网段信息不允许重叠 · The VLAN range pool does not exist or no VLAN IDs are available in the VLAN range pool：指定的租户承载网类型的VLAN池不存在，或该VLAN池内没有足够的VLAN ID · The address pool does not exist or no IPv4 or IPv6 addresses are available in the address pool: 指定的地址池不存在，或该地址池内没有可用的IPv4/IPv6地址 · To connect a normal-type vRouter to multiple remote vRouters of any types, make sure the destination subnets specified for the remote vRouters do not overlap：NORMAL类型虚拟路由器与多个虚拟路由器（不限定类型）建立连接时，目的网段不能重叠 · When you configure a centralized VAS vRouter link, configure the role of the local firewall as primary or secondary. The role of the local firewall cannot be both primary and secondary：集中式VAS VPC互通场景，本端防火墙配置角色主和备不能同时配置也不能同时为空 · When you configure a centralized non-VAS vRouter link, you cannot configure the role of the local firewall：非集中式VAS VPC互通场景，本端防火墙配置角色不能配置 · When you configure a centralized VAS vRouter link, enable the firewall service for the local transit vRouter：集中式VAS VPC互通场景，本端防火墙必须开启 · When you configure a centralized VAS vRouter link, disable the firewall service for the remote transit vRouter：集中式VAS VPC互通场景，对端防火墙必须关闭 · When you edit a centralized VAS vRouter link, you cannot change the role of the local firewall：集中式VAS VPC互通场景，本端防火墙配置角色不支持修改 · When you configure a centralized VAS vRouter link, disable both local route advertisement and remote route advertisement：集中式VAS VPC互通场景，发布本端所有路由和发布对端所有路由开关必须都关闭 · When you configure a centralized VAS vRouter link, the local transit vRouter must be bound to a DCI-capable border gateway and a firewall service resource：集中式VAS VPC互通场景，本端虚拟路由器必须绑定具备DCI能力的出口网关和防火墙资源 · When you configure a centralized VAS vRouter link, make sure the service resource ID of the local firewall is the same as that bound to the local transit vRouter：集中式VAS VPC互通场景，本端防火墙的服务资源ID和本端虚拟路由器绑定的服务资源ID必须一致 · If an east-west transit vRouter link enabled with remote route advertisement shares one transit vRouter with a centralized VAS vRouter link, the following items cannot overlap:1. Destination subnets configured for the route entries on the local vRouter of the east-west transit vRouter link.2. CIDRs configured for the remote vRouter of the centralized VAS vRouter link：TRANSIT类型虚拟路由器分别与两台虚拟路由器建立VAS VPC互通和发布对端所有路由开启的东西向TRANSIT VPC互通，东西向TRANSIT VPC互通的本端虚拟路由器的路由表项目的网段不能与VAS VPC互通的对端虚拟路由器CIDR重叠 · You cannot enable the host route advertisement feature if the value for the Mode field is 0 or 1：MODE为0或1时，不允许开启发布主机路由开关 |
|
关键字 |
DELETE_VPCCONNECTION_OP |
|
日志内容 |
Deleted vRouter interconnection "$1". |
|
参数解释 |
$1：虚拟路由器连接的名称 |
|
举例 |
Deleted vRouter interconnection "vpc". |
|
日志说明 |
用户进行了删除虚拟路由器连接的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The specified resource doesn't exist：指定的资源不存在 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
CREATE_L2DCICONNECT_OP |
|
日志内容 |
Created Layer 2 DC interconnection "$1". |
|
参数解释 |
$1：数据中心二层互联的名称 |
|
举例 |
Created Layer 2 DC interconnection "l2-dci-connect 01". |
|
日志说明 |
用户进行了创建数据中心二层互联的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The Layer 2 DC interconnection ID has already been used：数据中心二层互联ID已被使用 · The Layer 2 DC interconnection name is required：数据中心二层互联名称不能为空 · The network ID is required：未指定虚拟网络ID · The mapping segment ID is required：未指定映射Segment ID · The network has been bound to another Layer 2 DC interconnection：虚拟链路层网络已经被使用 · The VDS doesn’t exist：VDS不存在 · The mapping segment ID is out of range：映射Segment ID超出范围 · The mapping segment ID is already used：映射Segment ID已经被使用 · Invalid import target：无效的引入RT · Invalid export target：无效的引出RT · The Layer 2 DC import target is required：数据中心二层互联引入RT不能为空 · The Layer 2 DC export target is required：数据中心二层互联引出RT不能为空 · The export target conflicts with the export target of a Layer 2 DC interconnection：引出RT与已存在的数据中心二层互联的引出RT冲突 · The import target conflicts with the export target of a Layer 2 DC interconnection：引入RT与已存在的数据中心二层互联的引出RT冲突 · The export target conflicts with the import target of a Layer 2 DC interconnection：引出RT与已存在的数据中心二层互联的引入RT冲突 · The import target conflicts with the import target of a Layer 2 DC interconnection：引入RT与已存在的数据中心二层互联的引入RT冲突 · The export target conflicts with the export target of a Layer 3 DC interconnection：引出RT与已存在的数据中心三层互联的引出RT冲突 · The import target conflicts with the export target of a Layer 3 DC interconnection：引入RT与已存在的数据中心三层互联的引出RT冲突 · The export target conflicts with the import target of a Layer 3 DC interconnection：引出RT与已存在的数据中心三层互联的引入RT冲突 · The import target conflicts with the import target of a Layer 3 DC interconnection：引入RT与已存在的数据中心三层互联的引入RT冲突 · The network type cannot be VLAN：不支持指定VLAN类型的虚拟链路层网络 · The network cannot be external：不支持指定外部网络 · The Layer 2 DC interconnection name cannot exceed 255 characters：数据中心二层互联名称不能大于255个字符 · The Layer 2 DC interconnection description cannot exceed 255 characters：数据中心二层互联描述不能大于255个字符 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 · The import RT of the Layer 2 DC interconnect conflicts with the RT of the vNetwork：数据中心二层互联的引入RT与虚拟链路层网络的RT冲突 · The export RT of the Layer 2 DC interconnect conflicts with the RT of a vNetwork：数据中心二层互联的引出RT与虚拟链路层网络的RT冲突 · The import RT of the Layer 2 DC interconnect conflicts with the RT reserved for a fabric connection：数据中心二层互联的引入RT与系统预留的Fabric互联RT冲突 · The export RT of the Layer 2 DC interconnect conflicts with the RT reserved for a fabric connection：数据中心二层互联的引出RT与系统预留的Fabric互联RT冲突 · The import RT of the Layer 2 DC interconnect conflicts with the RT of a vRouter：数据中心二层互联的引入RT与虚拟路由器的RT冲突 · The export RT of the Layer 2 DC interconnect conflicts with the RT of the vRouter：数据中心二层互联的引出RT与虚拟路由器的RT冲突 · The import RT of the Layer 2 DC interconnect conflicts with the RT reserved for a vRouter link：数据中心二层互联的引入RT与系统预留的虚拟路由器连接的RT冲突 · The export RT of the Layer 2 DC interconnect conflicts with the RT reserved for a vRouter link：数据中心二层互联的引出RT与系统预留的虚拟路由器连接的RT冲突 · The import RT of the Layer 2 DC interconnect is identical to the RT generated based on the external segment ID of an external network：数据中心二层互联的引入RT与外部网络External Segment ID生成的RT冲突 · The export RT of the Layer 2 DC interconnect is identical to the RT generated based on the external segment ID of an external network：数据中心二层互联的引出RT与外部网络External Segment ID生成的RT冲突 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · Failed to bind the Layer 2 DC interconnect to the specified vNetwork, because the vNetwork is already enabled with the IPv6 multicast network feature：绑定虚拟链路层网络失败，指定的虚拟链路层网络已开启IPv6组播网络功能 · The cloud region name for the Layer 2 DC interconnection cannot exceed 255 characters：数据中心二层互联云区域名称最长255个字符 |
|
关键字 |
UPDATE_L2DCICONNECT_OP |
|
日志内容 |
Updated Layer 2 DC interconnection "$1". |
|
参数解释 |
$1：数据中心二层互联的名称 |
|
举例 |
Updated Layer 2 DC interconnection "l2-dci-connect". |
|
日志说明 |
用户进行了修改数据中心二层互联的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The specified resource doesn't exist：指定的资源不存在 · The name cannot be modified：名称不允许修改 · The network ID cannot be modified：虚拟链路层网络ID不允许修改 · The mapping segment ID is required：未指定映射Segment ID · Invalid import target：无效的引入RT · Invalid export target：无效的引出RT · The Layer 2 DC import target is required：数据中心二层互联引入RT不能为空 · The Layer 2 DC export target is required：数据中心二层互联引出RT不能为空 · The export target conflicts with the export target of a Layer 2 DC interconnection：引出RT与已存在的数据中心二层互联的引出RT冲突 · The import target conflicts with the export target of a Layer 2 DC interconnection：引入RT与已存在的数据中心二层互联的引出RT冲突 · The export target conflicts with the import target of a Layer 2 DC interconnection：引出RT与已存在的数据中心二层互联的引入RT冲突 · The import target conflicts with the import target of a Layer 2 DC interconnection：引入RT与已存在的数据中心二层互联的引入RT冲突 · The export target conflicts with the export target of a Layer 3 DC interconnection：引出RT与已存在的数据中心三层互联的引出RT冲突 · The import target conflicts with the export target of a Layer 3 DC interconnection：引入RT与已存在的数据中心三层互联的引出RT冲突 · The export target conflicts with the import target of a Layer 3 DC interconnection：引出RT与已存在的数据中心三层互联的引入RT冲突 · The import target conflicts with the import target of a Layer 3 DC interconnection：引入RT与已存在的数据中心三层互联的引入RT冲突 · The Layer 2 DC interconnection description cannot exceed 255 characters：数据中心二层互联描述不能大于255个字符 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 · The import RT of the Layer 2 DC interconnect conflicts with the RT of the vNetwork：数据中心二层互联的引入RT与虚拟链路层网络的RT冲突 · The export RT of the Layer 2 DC interconnect conflicts with the RT of a vNetwork：数据中心二层互联的引出RT与虚拟链路层网络的RT冲突 · The import RT of the Layer 2 DC interconnect conflicts with the RT reserved for a fabric connection：数据中心二层互联的引入RT与系统预留的Fabric互联RT冲突 · The export RT of the Layer 2 DC interconnect conflicts with the RT reserved for a fabric connection：数据中心二层互联的引出RT与系统预留的Fabric互联RT冲突 · The import RT of the Layer 2 DC interconnect conflicts with the RT of a vRouter：数据中心二层互联的引入RT与虚拟路由器的RT冲突 · The export RT of the Layer 2 DC interconnect conflicts with the RT of the vRouter：数据中心二层互联的引出RT与虚拟路由器的RT冲突 · The import RT of the Layer 2 DC interconnect conflicts with the RT reserved for a vRouter link：数据中心二层互联的引入RT与系统预留的虚拟路由器连接的RT冲突 · The export RT of the Layer 2 DC interconnect conflicts with the RT reserved for a vRouter link：数据中心二层互联的引出RT与系统预留的虚拟路由器连接的RT冲突 · The import RT of the Layer 2 DC interconnect is identical to the RT generated based on the external segment ID of an external network：数据中心二层互联的引入RT与外部网络External Segment ID生成的RT冲突 · The export RT of the Layer 2 DC interconnect is identical to the RT generated based on the external segment ID of an external network：数据中心二层互联的引出RT与外部网络External Segment ID生成的RT冲突 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · The cloud region name for the Layer 2 DC interconnection cannot exceed 255 characters：数据中心二层互联云区域名称最长255个字符 · You cannot edit or delete the cloud region name：云区域名称不允许修改或删除 |
|
关键字 |
DELETE_L2DCICONNECT_OP |
|
日志内容 |
Deleted Layer 2 DC interconnection "$1". |
|
参数解释 |
$1：数据中心二层互联的名称 |
|
举例 |
Deleted Layer 2 DC interconnection "l2-dci-connect". |
|
日志说明 |
用户进行了删除数据中心二层互联的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The specified resource doesn't exist：指定的资源不存在 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
CREATE_L3DCICONNECT_OP |
|
日志内容 |
Created Layer 3 DC interconnection "$1". |
|
参数解释 |
$1：数据中心三层互联的名称 |
|
举例 |
Created Layer 3 DC interconnection "l3-dci-connect 01". |
|
日志说明 |
用户进行了创建数据中心三层互联的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The layer 3 DC interconnection name is required：数据中心三层互联名称不能为空 · The router ID is required：未指定虚拟路由器ID · The specified vRouter doesn't exist：指定的虚拟路由器不存在 · The remote subnet is required when the firewall service is enabled：开启防火墙时远端网段不能为空 · Invalid remote subnet：无效的远端网段 · Duplicated remote subnets exist：远端网段配置中有重叠项 · A remote subnet of the Layer 3 DC interconnection overlaps with a remote subnet of a vRouter interconnection. The subnet of the Layer 3 DC interconnection must be covered by the overlapping subnet of the vRouter interconnection：数据中心三层互联的远端网段范围必须小于虚拟路由器连接的同网段子网范围 · The remote subnets overlap with the subnets of the vRouter：远端网段与指定虚拟路由器的虚拟子网发生重叠 · The remote subnet cannot be configured when the firewall service is disabled：防火墙未开启时不能配置远端网段 · Invalid packet encapsulation type：无效的报文封装类型 · The specified subnet doesn't exist：指定的虚拟子网不存在 · The specified subnet is not bound to the vRouter：指定的虚拟子网没有绑定此虚拟路由器 · The mapping segment ID is required：未指定映射Segment ID · The VDS doesn't exist：VDS不存在 · The mapping segment ID is out of range：映射Segment ID超出范围 · The mapping segment ID is already used：映射Segment ID已被使用 · Invalid export target：无效的引出RT · The Layer 3 DC export target is required：数据中心三层互联引出RT不能为空 · The Layer 3 DC interconnection ID has already been used：数据中心三层互联ID已被使用 · Invalid import target：无效的引入RT · The Layer 3 DC import target is required：数据中心三层互联引入RT不能为空 · The export target conflicts with the export target of a Layer 2 DC interconnection：引出RT与已存在的数据中心二层互联的引出RT冲突 · The import target conflicts with the export target of a Layer 2 DC interconnection：引入RT与已存在的数据中心二层互联的引出RT冲突 · The export target conflicts with the import target of a Layer 2 DC interconnection：引出RT与已存在的数据中心二层互联的引入RT冲突 · The import target conflicts with the import target of a Layer 2 DC interconnection：引入RT与已存在的数据中心二层互联的引入RT冲突 · The export target conflicts with the export target of a Layer 3 DC interconnection：引出RT与已存在的数据中心三层互联的引出RT冲突 · The import target conflicts with the export target of a Layer 3 DC interconnection：引入RT与已存在的数据中心三层互联的引出RT冲突 · The export target conflicts with the import target of a Layer 3 DC interconnection：引出RT与已存在的数据中心三层互联的引入RT冲突 · The import target conflicts with the import target of a Layer 3 DC interconnection：引入RT与已存在的数据中心三层互联的引入RT冲突 · The VPN instance name is already used. Please modify the mapping segment ID：VPN实例名称已被使用，请修改映射Segment ID · You can configure the same mapping segment ID for multiple Layer 3 DC interconnections using different vRouters only when all these interconnections are enabled with the firewall service：配置不同虚拟路由器的两个数据中心三层互联，仅当均开启防火墙时，才可配置相同的映射Segment ID · The Layer 3 DC interconnection name cannot exceed 255 characters：数据中心三层互联名称不能大于255个字符 · The Layer 3 DC interconnection description cannot exceed 255 characters：数据中心三层互联描述不能大于255个字符 · Some remote subnets overlap with the remote subnets of other Layer 3 DC interconnections of the vRouter：远端网段与该虚拟路由器的其他数据中心三层互联使用的远端网段存在重叠 · The mapping segment ID has been used by another Layer 3 DC interconnection of the vRouter：映射Segment ID已被该虚拟路由器的其他数据中心三层互联使用 · For two Layer 3 DC interconnections configured with the same mapping segment ID, their remote subnets and local subnets cannot both overlap：配置相同映射Segment ID的两个数据中心三层互联，远端网段和本端子网不能同时重叠 · For two Layer 3 DC interconnections configured with the same mapping segment ID, the remote subnets of one Layer 3 DC interconnection cannot overlap with the local subnets of the other Layer 3 DC interconnection：配置相同映射Segment ID的两个数据中心三层互联，其中一个数据中心三层互联的远端网段与另一个数据中心三层互联的本端子网不能重叠 · The network to which the local subnet belongs cannot be a VLAN：本端子网所属的虚拟链路层网络不能为VLAN类型 · The local subnet cannot be an external subnet：本端子网不能为外网子网 · The import RTs of Layer 3 DC interconnections configured with the same mapping segment ID must be the same, and so must the export RTs：配置相同映射Segment ID的两个数据中心三层互联，引入RT和引出RT必须分别相同 · The vRouter does not bind a gateway or the gateway bound to the vRouter is not assigned with a data center interconnection network IP address：指定的虚拟路由器未绑定网关或绑定的网关未分配到数据中心互联网络类型的IP地址 · The vRouter can be bound to only one border gateway. Make sure the device group associated with the gateway members is enabled with DC interconnection, or the vRouter-attached tenant is bound to a border gateway that uses a device group only for DC interconnection or fabric interconnection and DC interconnection：虚拟路由器只能绑定一个出口网关，且出口网关的成员设备组必须开启DC间互联功能或者租户下有设备组网络位置仅为DC间互联或者Fabric间互通+DC间互联的出口网关 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 · The mapping segment ID already exists：映射Segment ID已存在 · The import RT of the Layer 3 DC interconnect conflicts with the RT of a vNetwork：数据中心三层互联的引入RT与虚拟链路层网络的RT冲突 · The export RT of the Layer 3 DC interconnect conflicts with the RT of a vNetwork：数据中心三层互联的引出RT与虚拟链路层网络的RT冲突 · The import RT of the Layer 3 DC interconnect conflicts with the RT reserved for a fabric connection：数据中心三层互联的引入RT与系统预留的Fabric互联RT冲突 · The export RT of the Layer 3 DC interconnect conflicts with the RT reserved for a fabric connection：数据中心三层互联的引出RT与系统预留的Fabric互联RT冲突 · The import RT of the Layer 3 DC interconnect conflicts with the RT of a vRouter：数据中心三层互联的引入RT与虚拟路由器的RT冲突 · The export RT of the Layer 3 DC interconnect conflicts with the RT of a vRouter：数据中心三层互联的引出RT与虚拟路由器的RT冲突 · The import RT of the Layer 3 DC interconnect conflicts with the RT reserved for a vRouter link：数据中心三层互联的引入RT与系统预留的虚拟路由器连接的RT冲突 · The export RT of the Layer 3 DC interconnect conflicts with the RT reserved for a vRouter link：数据中心三层互联的引出RT与系统预留的虚拟路由器连接的RT冲突 · You cannot enable the firewall feature for the Layer 3 DCI, because the associated gateway uses a device group only for DC interconnection or fabric interconnection and DC interconnection：设备组网络位置仅为DC间互联或者Fabric间互通+DC间互联的出口网关不支持数据中心三层互联过墙 · If a centralized-mode vRouter link, routing table, and Layer 3 DCI are attached to the same vRouter, you cannot specify the same subnet as a remote CIDR, destination subnet, and remote subnet for them, respectively：当集中式虚拟路由器连接、路由表和数据中心三层互联关联同一个虚拟路由器时，对端网段、目的网段和远端网段不能相同 · The import RT of the Layer 3 DC interconnect is identical to the RT generated based on the external segment ID of an external network：数据中心三层互联的引入RT与外部网络External Segment ID生成的RT冲突 · The export RT of the Layer 3 DC interconnect is identical to the RT generated based on the external segment ID of an external network：数据中心三层互联的引出RT与外部网络External Segment ID生成的RT冲突 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · You cannot bind the vRouter to the Layer 3 DC interconnect, because the vRouter has been bound to an external transit vRouter link operating in centralized mode：数据中心三层互联不允许绑定已被EXTERNALTRANSIT类型集中式虚拟路由器连接使用的虚拟路由器 · The vRouter is not the vRouter bound to the Layer 3 DC interconnect：指定的虚拟路由器与数据中心三层互联绑定的虚拟路由器不一致 · The export RT of the Layer 3 DC interconnect is identical to the RT generated based on the external segment ID of an external network：数据中心三层互联的防火墙开关开启时，不允许绑定Service Leaf类型防火墙的虚拟路由器 · Resource application or rollback failed, internal unknown error：资源申请或回滚失败，内部未知错误 · The（resource）does not exist or the resources are insufficient：（资源）不存在或资源不足 · The（resource）does not exist or the resources are insufficient, device group name（name）：（资源）不存在或资源不足，设备组名称（名称） · The （resource） does not exist or the resources are insufficient, resource access template name （name）：（资源）不存在或资源不足，资源接入模板名称（名称） |
|
关键字 |
UPDATE_L3DCICONNECT_OP |
|
日志内容 |
Updated Layer 3 DC interconnection "$1". |
|
参数解释 |
$1：数据中心三层互联的名称 |
|
举例 |
Updated Layer 3 DC interconnection "l3-dci-connect". |
|
日志说明 |
用户进行了修改数据中心三层互联的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The specified resource doesn't exist：指定的资源不存在 · The name cannot be modified：名称不允许修改 · The vRouter ID cannot be modified：虚拟路由器ID不允许修改 · The firewall service status cannot be modified：防火墙开关状态不能修改 · The logical firewall cannot be modified：逻辑防火墙不能修改 · The packet encapsulation type cannot be modified：报文封装类型不能修改 · The specified subnet does not exist：指定的虚拟子网不存在 · The specified subnet is not bound to the vRouter：指定的虚拟子网没有绑定此虚拟路由器 · A remote subnet of the Layer 3 DC interconnection overlaps with a remote subnet of a vRouter interconnection：指定的虚拟子网没有绑定此虚拟路由器 · The mapping segment ID is required：未指定映射Segment ID · A remote subnet of the Layer 3 DC interconnection overlaps with a remote subnet of a vRouter interconnection. The subnet of the Layer 3 DC interconnection must be covered by the overlapping subnet of the vRouter interconnection：数据中心三层互联的远端网段范围必须小于虚拟路由器连接的同网段子网范围 · The remote subnet is required when the firewall service is enabled：开启防火墙时远端网段不能为空 · The remote subnets overlap with the subnets of the vRouter：远端网段与指定虚拟路由器的虚拟子网发生重叠 · The remote subnet cannot be configured when the firewall service is disabled：防火墙未开启时远端网段不允许配置 · Invalid import target：无效的引入RT · Invalid export target：无效的引出RT · The Layer 3 DC import target is required：数据中心三层互联引入RT不能为空 · The Layer 3 DC export target is required：数据中心三层互联引出RT不能为空 · The export target conflicts with the export target of a Layer 2 DC interconnection：引出RT与已存在的数据中心二层互联的引出RT冲突 · The import target conflicts with the export target of a Layer 2 DC interconnection：引入RT与已存在的数据中心二层互联的引出RT冲突 · The export target conflicts with the import target of a Layer 2 DC interconnection：引出RT与已存在的数据中心二层互联的引入RT冲突 · The import target conflicts with the import target of a Layer 2 DC interconnection：引入RT与已存在的数据中心二层互联的引入RT冲突 · The export target conflicts with the export target of a Layer 3 DC interconnection：引出RT与已存在的数据中心三层互联的引出RT冲突 · The import target conflicts with the export target of a Layer 3 DC interconnection：引入RT与已存在的数据中心三层互联的引出RT冲突 · The export target conflicts with the import target of a Layer 3 DC interconnection：引出RT与已存在的数据中心三层互联的引入RT冲突 · The import target conflicts with the import target of a Layer 3 DC interconnection：引入RT与已存在的数据中心三层互联的引入RT冲突 · You can configure the same mapping segment ID for multiple Layer 3 DC interconnections using different vRouters only when all these interconnections are enabled with the firewall service：配置不同虚拟路由器的两个数据中心三层互联，仅当均开启防火墙时，才可配置相同的映射Segment ID · The Layer 3 DC interconnection description cannot exceed 255 characters：数据中心三层互联描述不能大于255个字符 · Some remote subnets overlap with the remote subnets of other Layer 3 DC interconnections of the vRouter：远端网段与该虚拟路由器的其他数据中心三层互联使用的远端网段存在重叠 · The mapping segment ID has been used by another Layer 3 DC interconnection of the vRouter：映射Segment ID已被该虚拟路由器的其他数据中心三层互联使用 · For two Layer 3 DC interconnections configured with the same mapping segment ID, their remote subnets and local subnets cannot both overlap：配置相同映射Segment ID的两个数据中心三层互联，远端网段和本端子网不能同时重叠 · For two Layer 3 DC interconnections configured with the same mapping segment ID, the remote subnets of one Layer 3 DC interconnection cannot overlap with the local subnets of the other Layer 3 DC interconnection：配置相同映射Segment ID的两个数据中心三层互联，其中一个数据中心三层互联的远端网段与另一个数据中心三层互联的本端子网不能重叠 · The network to which the local subnet belongs cannot be a VLAN：本端子网所属的虚拟链路层网络不能为VLAN类型 · The local subnet cannot be an external subnet：本端子网不能为外网子网 · The import RTs of Layer 3 DC interconnections configured with the same mapping segment ID must be the same, and so must the export RTs：配置相同映射Segment ID的两个数据中心三层互联，引入RT和引出RT必须分别相同 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 · The mapping segment ID already exists：映射Segment ID已存在 · The import RT of the Layer 3 DC interconnect conflicts with the RT of a vNetwork：数据中心三层互联的引入RT与虚拟链路层网络的RT冲突 · The export RT of the Layer 3 DC interconnect conflicts with the RT of a vNetwork：数据中心三层互联的引出RT与虚拟链路层网络的RT冲突 · The import RT of the Layer 3 DC interconnect conflicts with the RT reserved for a fabric connection：数据中心三层互联的引入RT与系统预留的Fabric互联RT冲突 · The export RT of the Layer 3 DC interconnect conflicts with the RT reserved for a fabric connection：数据中心三层互联的引出RT与系统预留的Fabric互联RT冲突 · The import RT of the Layer 3 DC interconnect conflicts with the RT of a vRouter：数据中心三层互联的引入RT与虚拟路由器的RT冲突 · The export RT of the Layer 3 DC interconnect conflicts with the RT of a vRouter：数据中心三层互联的引出RT与虚拟路由器的RT冲突 · The import RT of the Layer 3 DC interconnect conflicts with the RT reserved for a vRouter link：数据中心三层互联的引入RT与系统预留的虚拟路由器连接的RT冲突 · The export RT of the Layer 3 DC interconnect conflicts with the RT reserved for a vRouter link：数据中心三层互联的引出RT与系统预留的虚拟路由器连接的RT冲突 · The value for the reduce_routes parameter is invalid：无效的路由精简参数 · You cannot both configure an extra Layer 3 DC interconnection and enable route reduction：不支持同时配置数据中心三层互联增强和开启路由精简 · If a centralized-mode vRouter link, routing table, and Layer 3 DCI are attached to the same vRouter, you cannot specify the same subnet as a remote CIDR, destination subnet, and remote subnet for them, respectively：当集中式虚拟路由器连接、路由表和数据中心三层互联关联同一个虚拟路由器时，对端网段、目的网段和远端网段不能相同 · The import RT of the Layer 3 DC interconnect is identical to the RT generated based on the external segment ID of an external network：数据中心三层互联的引入RT与外部网络External Segment ID生成的RT冲突 · The export RT of the Layer 3 DC interconnect is identical to the RT generated based on the external segment ID of an external network：数据中心三层互联的引出RT与外部网络External Segment ID生成的RT冲突 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · Resource application or rollback failed, internal unknown error：资源申请或回滚失败，内部未知错误 · The（resource）does not exist or the resources are insufficient：（资源）不存在或资源不足 · The（resource）does not exist or the resources are insufficient, device group name（name）：（资源）不存在或资源不足，设备组名称（名称） · The （resource） does not exist or the resources are insufficient, resource access template name （name）：（资源）不存在或资源不足，资源接入模板名称（名称） |
|
关键字 |
DELETE_L3DCICONNECT_OP |
|
日志内容 |
Deleted Layer 3 DC interconnection "$1". |
|
参数解释 |
$1：数据中心三层互联的名称 |
|
举例 |
Deleted Layer 3 DC interconnection "l3-dci-connect". |
|
日志说明 |
用户进行了删除数据中心三层互联的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The specified resource doesn't exist：指定的资源不存在 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · Resource application or rollback failed, internal unknown error：资源申请或回滚失败，内部未知错误 · The（resource）does not exist or the resources are insufficient：（资源）不存在或资源不足 · The（resource）does not exist or the resources are insufficient, device group name（name）：（资源）不存在或资源不足，设备组名称（名称） · The （resource） does not exist or the resources are insufficient, resource access template name （name）：（资源）不存在或资源不足，资源接入模板名称（名称） |
|
关键字 |
CREATE_L3DCICONNECT_EXTRA_OP |
|
日志内容 |
Created an extra Layer 3 DC interconnection. |
|
参数解释 |
无 |
|
举例 |
Created an extra Layer 3 DC interconnection. |
|
日志说明 |
用户进行了创建数据中心三层互联增强的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The extra UUID already exists：增强UUID已存在 · The L3 DC interconnection ID is required：数据中心三层互联ID为空 · The specified resource doesn't exist：指定的资源不存在 · Invalid CIDR：无效的CIDR · IPv6 link-local addresses cannot be used as subnet addresses：link-local地址无效 · The subnets in the redistributed routes overlap：引入路由网段重叠 · The subnets in the summary routes overlap：聚合路由网段重叠 · When the firewall is enabled, do not set routeControlMode to denylist：当防火墙开启时，routeControlMode不能为denylist · Invalid routeControlMode value：无效的routeControlMode字段 · When the firewall is enabled, do not configure EXTERNALCIDRS：当防火墙开启时，EXTERNALCIDRS不能配置 · When the firewall is enabled, do not set MACIPROUTESUPPRESSION to true：当防火墙开启时，MACIPROUTESUPPRESSION不能为true · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 · You cannot both configure an extra Layer 3 DC interconnection and enable route reduction：不支持同时配置数据中心三层互联增强和开启路由精简 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
UPDATE_L3DCICONNECT_OP |
|
日志内容 |
Updated the extra Layer 3 DC interconnection. |
|
参数解释 |
无 |
|
举例 |
Updated the extra Layer 3 DC interconnection. |
|
日志说明 |
用户进行了修改数据中心三层互联增强的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：请在主Leader上进行操作 · Configuration recovery is in progress：配置恢复未完成 · The specified resource doesn't exist：指定的资源不存在 · The L3 DC interconnection ID is required：数据中心三层互联ID为空 · Invalid CIDR：无效的CIDR · IPv6 link-local addresses cannot be used as subnet addresses：link-local地址无效 · The subnets in the redistributed routes overlap：引入路由网段重叠 · The subnets in the summary routes overlap：聚合路由网段重叠 · When the firewall is enabled, do not set routeControlMode to denylist：当防火墙开启时，routeControlMode不能为denylist · Invalid routeControlMode value：无效的routeControlMode字段 · When the firewall is enabled, do not configure EXTERNALCIDRS：当防火墙开启时，EXTERNALCIDRS不能配置 · When the firewall is enabled, do not set MACIPROUTESUPPRESSION to true：当防火墙开启时，MACIPROUTESUPPRESSION不能为true · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
DELETE_L3DCICONNECT_OP_EXTRA |
|
日志内容 |
Deleted the extra Layer 3 DC interconnection. |
|
参数解释 |
无 |
|
举例 |
Deleted the extra Layer 3 DC interconnection. |
|
日志说明 |
用户进行了删除数据中心三层互联增强的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：请在主Leader上进行操作 · Configuration recovery is in progress：配置恢复未完成 · The specified resource doesn't exist：指定的资源不存在 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
ADD_L3DCICONNECTSUBNET_OP |
|
日志内容 |
Added subnet "$1" to Layer 3 DC interconnection "$2" |
|
参数解释 |
$1：本端子网名称 $2：数据中心三层互联名称 |
|
举例 |
Added subnet "subnet 1" to Layer 3 DC interconnection "l3-dci-connect 2" |
|
日志说明 |
用户进行了添加数据中心三层互联本端子网的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The subnet ID was null：子网ID为空 · The router ID is required：未指定虚拟路由器 ID · The specified subnet doesn't exist：指定的虚拟子网不存在 · The specified subnet is not bound to the vRouter：指定的虚拟子网没有绑定此虚拟路由器 · The specified vRouter doesn't exist：指定的虚拟路由器不存在 · The subnet has already been bound to the Layer 3 DC interconnection：该虚拟子网已被数据中心三层互联绑定 · The request is invalid：传入的JSON串错误 · The specified resource doesn't exist：指定的资源不存在 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
DELETE_L3DCICONNECTsubnet_OP |
|
日志内容 |
Deleted subnet "$1" from Layer 3 DC interconnection "$2" |
|
参数解释 |
$1：本端子网名称 $2：数据中心三层互联的名称 |
|
举例 |
Deleted subnet "interface 1" from Layer 3 DC interconnection "l3-dci-connect 2" |
|
日志说明 |
用户进行了删除数据中心三层互联的本端子网的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The subnet ID is required：子网ID为空 · The vRouter ID is required：未指定虚拟路由器ID · The specified subnet doesn't exist：指定的虚拟子网不存在 · The specified vRouter doesn't exist：指定的虚拟路由器不存在 · The subnet is not bound to the Layer 3 DC interconnection：该虚拟子网未绑定数据中心三层互联 · The specified subnet is not bound to the vRoute：指定的虚拟子网没有绑定此虚拟路由器 · The specified resource is not exist：指定的资源不存在 · The request is invalid：传入的JSON串错误 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
UPLOAD_LICENSE_OP |
|
日志内容 |
Uploaded the vSwitch license file. |
|
参数解释 |
无 |
|
举例 |
Uploaded the vSwitch license file. |
|
日志说明 |
用户进行了上传本地vSwitch License文件的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Failed to upload the file：文件上传失败 · License file error：License文件有误 · Configuration recovery is in progress：配置恢复未完成 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_HOSTLOADLIMIT_OP |
|
日志内容 |
Updated host load limit “$1”. |
|
参数解释 |
$1：主机的IP地址 |
|
举例 |
Updated host load limit “98.0.25.103”. |
|
日志说明 |
用户进行了修改主机的虚拟交换机桥配置的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The max packet-in packet rate is invalid：无效的Packet-in报文最大速率 · The host version does not support the max packet-in packet rate parameter：该主机版本不支持配置Packet-in报文最大速率 · The flow entry aging acceleration threshold is invalid：无效的流表加速老化阈值 · The host version does not support the flow entry aging acceleration threshold parameter：该主机版本不支持配置流表加速老化阈值 · Failed to deploy the max packet-in packet rate to the host：Packet-in报文最大速率下发到主机失败 · Failed to deploy the flow entry aging acceleration threshold to the host：流表加速老化阈值下发到主机失败 · EXSi hosts do not support the max packet-in packet rate or flow entry aging acceleration threshold parameter：EXSi主机不支持配置Packet-in报文最大速率和流表加速老化阈值 · The request is invalid：传入的JSON串错误 · Unknown error：未知错误 · The specified resource doesn't exist：指定的资源不存在 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_SEGMENT_OP |
|
日志内容 |
Create segment：$1. |
|
参数解释 |
$1：网络分段的名称 |
|
举例 |
Created segment “segment01”. |
|
日志说明 |
用户进行了添加网络分段的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The operation requires the administrator privilege：您需要管理员权限才能执行此操作 · The ID already exists：ID已存在 · The segment ID number already exists：Segment ID number已存在 · The value of the network type can only be VLAN：仅支持VLAN类型外网 · The network type is required：网络类型不能为空 · The network ID is required：网络ID不能为空 · The segment ID is not in the VLAN pool：Segment ID不在VLAN池范围内 · The segment has been bound to subnets：Segment已被子网绑定 · physical network is required：physical_network字段不能为空 · The specified border gateway doesn't exist：指定的出口网关不存在 · The network doesn't exist：指定的网络不存在 · Invalid segmentUUID：无效的 segmentUUID · You can create segments only for external networks：仅外部网络支持创建网络分段 · The segment name cannot exceed 255 characters：Segment名称最长255个字符 · The description cannot exceed 255 characters：描述信息最长255个字符 · When you create the first segment for the external network, the segment type must be the same as the type of the external network：为外部网络首次创建Segment时，Segment的类型和外部网络的类型必须一致 · When you create the first segment for the external network, the ID of the segment must be the same as the segment ID of the external network：为外部网络首次创建网络分段时，网络分段的Segment ID和外部网络的Segment ID必须一致 · Operation failed. To enable network segmentation for the external network, make sure all vRouters bound to the external network use the same border gateway or none of them uses a border gateway：开启网络分段失败，该外部网络已绑定一个或多个虚拟路由器。每个虚拟路由器最多只能绑定一个出口网关，且所有虚拟路由器绑定的出口网关必须相同 · The external network is bound to a vRouter that is configured with a gateway, and you must specify this gateway for the segment：外部网络已被一个存在出口网关的虚拟路由器绑定，网络分段指定的出口网关必须与该虚拟路由器绑定的出口网关一致 · Invalid segment ID：无效的segment ID · Cannot segment the external network because it has been bound to a vRouter that is bound to a gateway resource configured with a priority：外部网络被虚拟路由器绑定后，若虚拟路由器的网关资源已配置优先级，则该外部网络不支持开启网络分段功能 · You have no privilege to perform this operation：用户无权限执行此操作 · You cannot change the status of the network segmentation feature when the multicast network feature is enabled：当外部网络开启组播网络开关时，不允许切换网络分段开关 · You cannot change the network segmentation state for the external network, because it has been bound to a Layer 3 multicast network：指定的外部网络已经绑定了L3组播，不能修改网络分段开关 · The external segment ID is already in use：External Segment ID 已经被使用 · The external segment ID is out of range：External Segment ID超出范围 · You cannot bind the external network segment to a border gateway that uses a device group only for DC Interconnection：网络分段不支持绑定设备组的网络位置仅为DC间互联的出口网关 · You cannot enable network segmentation for the external network, because the external network contains vPorts configured with extended SNAT IP addresses：外部网络存在配置了扩展SNAT IP地址的虚拟端口，不能开启网络分段 · You cannot both enable network segmentation and specify a gateway for an external network：外部网络的网络分段和出口网关冲突 · You cannot enable network segmentation for the external network, because it is already bound to an external transit vRouter：外网已绑定EXTERNALTRANSIT类型虚拟路由器，不允许开启网络分段 · A VPN instance name cannot start with 'management_vpn'：VPN实例名称不能以"management_vpn"为前缀 · A VPN instance already exists with the specified name：VPN实例名称已被使用 · When an external network has a vPort bound to a vRouter, you cannot enable network segmentation for that external network：外部网络存在虚拟端口绑定虚拟路由器时，不允许开启网络分段功能 · The RT generated based on the external segment ID of the external network conflicts with the import RT of vRouter：外部网络External Segment ID生成的RT与虚拟路由器配置的引入RT冲突 · The RT generated based on the external segment ID of the external network conflicts with the export RT of vRouter：外部网络External Segment ID生成的RT与虚拟路由器配置的引出RT冲突 · The RT generated based on the external segment ID of the external network is identical to the import RT of a Layer 2 DC interconnect：外部网络External Segment ID生成的RT与数据中心二层互联的引入RT冲突 · The RT generated based on the external segment ID of the external network is identical to the export RT of a Layer 2 DC interconnect：外部网络External Segment ID生成的RT与数据中心二层互联的引出RT冲突 · The RT generated based on the external segment ID of the external network is identical to the import RT of a Layer 3 DC interconnect：外部网络External Segment ID生成的RT与数据中心三层互联的引入RT冲突 · The RT generated based on the external segment ID of the external network is identical to the export RT of a Layer 3 DC interconnect：外部网络External Segment ID生成的RT与数据中心三层互联的引出RT冲突 · The segment ID of a network segment cannot be included in the VLAN range of any global VLAN-VXLAN mapping：网络分段的Segment ID不允许在全局VLAN-VXLAN映射的VLAN范围内 · Cannot allocate this external segment ID, because synchronization is in progress for the VXLAN pool containing this external segment ID：无法分配该External Segment ID，其所在的VXLAN池正在平滑中 |
|
关键字 |
UPDATE_SEGMENT_OP |
|
日志内容 |
Updated segment：$1. |
|
参数解释 |
$1：网络分段的名称 |
|
举例 |
Update segment “segment01”. |
|
日志说明 |
用户进行了修改网络分段的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The operation requires the administrator privilege：您需要管理员权限才能执行此操作 · The specified resource doesn't exist：指定的资源不存在 · The segment name cannot exceed 255 characters：Segment名称最长255个字符 · The description cannot exceed 255 characters：描述信息最长255个字符 · You have no privilege to perform this operation：用户无权限执行此操作 · The external segment ID is already in use：External Segment ID 已经被使用 · The external segment ID is out of range：External Segment ID超出范围 · You cannot edit or delete the cloud region name：云区域名称不允许修改或删除 · You cannot both enable network segmentation and specify a gateway for an external network：外部网络的网络分段和出口网关冲突 · The RT generated based on the external segment ID of the external network conflicts with the import RT of vRouter：外部网络External Segment ID生成的RT与虚拟路由器配置的引入RT冲突 · The RT generated based on the external segment ID of the external network conflicts with the export RT of vRouter：外部网络External Segment ID生成的RT与虚拟路由器配置的引出RT冲突 · The RT generated based on the external segment ID of the external network is identical to the import RT of a Layer 2 DC interconnect：外部网络External Segment ID生成的RT与数据中心二层互联的引入RT冲突 · The RT generated based on the external segment ID of the external network is identical to the export RT of a Layer 2 DC interconnect：外部网络External Segment ID生成的RT与数据中心二层互联的引出RT冲突 · The RT generated based on the external segment ID of the external network is identical to the import RT of a Layer 3 DC interconnect：外部网络External Segment ID生成的RT与数据中心三层互联的引入RT冲突 · The RT generated based on the external segment ID of the external network is identical to the export RT of a Layer 3 DC interconnect：外部网络External Segment ID生成的RT与数据中心三层互联的引出RT冲突 · Cannot allocate this external segment ID, because synchronization is in progress for the VXLAN pool containing this external segment ID：无法分配该External Segment ID，其所在的VXLAN池正在平滑中 |
|
关键字 |
DELETE_SEGMENT_OP |
|
日志内容 |
Deleted segment：$1. |
|
参数解释 |
$1：网络分段的名称 |
|
举例 |
Deleted segment “segment01” |
|
日志说明 |
用户进行了删除网络分段的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The operation requires the administrator privilege：您需要管理员权限才能执行此操作 · The segment has been bound to subnets：Segment已被子网绑定 · The specified resource doesn't exist：指定的资源不存在 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
CREATE_TRUNK_OP |
|
日志内容 |
Create trunk $1. |
|
参数解释 |
$1：端口中继名称 |
|
举例 |
Create trunk "trunk0". |
|
日志说明 |
用户进行了增加端口中继的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The trunk name is invalid：无效的Trunk名称 · The tenant ID is invalid：无效的租户ID · The parent port has been bound to another trunk：指定的父端口已被其他Trunk绑定 · The parent port does not exist：指定的父端口不存在 · The parent port and subport must be the same type：指定父端口和子端口的类型必须一致 · The port ID of the parent is invalid：无效的父端口ID · The port ID of the subport is invalid：无效的子端口ID · The subport has been bound to another trunk：指定的子端口已被其他Trunk绑定 · The trunk ID already exists：Trunk ID已存在 · The value of the segmentation_Type on subport must be VLAN：指定的子端口必须为VLAN类型 · The segmentation_Type of the subport is invalid.：无效的子端口VLAN类型 · Duplicate segmentation ID：重复的Segmentation ID · The segmentation ID is out of range：子端口Segmentation ID超出范围 · The segmentation ID of the subport is invalid：无效的子端口Segmentation ID · The trunk description cannot exceed 255 characters：Trunk的描述信息不能超过255字符 · The trunk name cannot exceed 255 characters：Trunk的名称不能超过255字符 · Duplicate trunk ID：重复的 Trunk ID · Duplicate parent port ID：重复的 父端口ID · Duplicate subport port ID：重复的子端口ID · The subport does not exist：指定的子端口不存在 · The controller is not the active leader：当前设备不是Leader控制组件，无法进行此操作 · Token aged：Token已老化 · Online vPorts cannot be used as subports：已上线虚拟端口不支持作为子端口 · The parent port and the subport cannot be the same：父端口与子端口不能为同一个虚拟端口 · The tenant ID of the parent port and the subport must be the same as the specified tenant ID：指定的父端口和子端口所属的租户ID必须与指定的租户ID相同 · You have no privilege to perform this operation：用户无权限执行此操作 · Trunks do not support LB, GW, DHCP, or PBR vPorts：Trunk不支持绑定LB、GW、DHCP、PBR类型的虚拟端口 · Up to 255 characters, case sensitive：参数不能超过255个字符，区分大小写 · You cannot bind the parent port to a port automatically onboarded by southbound packets：父端口不支持绑定南向自动创建的端口 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · You cannot bind the subport to a port automatically onboarded by southbound packets：子端口不支持绑定南向自动创建的端口 · Online OVS vPorts cannot be used as subports：已上线OVS类型虚拟端口不支持作为子端口 · Online vPorts cannot be used as subports, because the transparent mode is enabled：透传模式开启时，已上线虚拟端口不支持作为子端口 · A parent port and its subports must be configured with the same QoS profile：父端口和其子端口必须配置相同类型的QoS策略 |
|
关键字 |
UPDATE_TRUNK _OP |
|
日志内容 |
Update trunk $1. |
|
参数解释 |
$1：端口中继名称 |
|
举例 |
Update trunk "trunk0". |
|
日志说明 |
用户进行了更新端口中继的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The specified trunk does not exist：指定Trunk不存在 · The trunk name is invalid：无效的Trunk名称 · The controller is not the active leader：当前设备不是Leader控制组件，无法进行此操作 · The trunk description cannot exceed 255 characters：Trunk的描述信息不能超过255字符 · The trunk name cannot exceed 255 characters：Trunk的名称不能超过255字符 · Token aged：Token已老化 · You have no privilege to perform this operation：用户无权限执行此操作 · Trunks do not support LB, GW, DHCP, or PBR vPorts：Trunk不支持绑定LB、GW、DHCP、PBR类型的虚拟端口 · You cannot edit or delete the cloud region name：云区域名称不允许修改或删除 · A parent port and its subports must be configured with the same QoS profile：父端口和其子端口必须配置相同类型的QoS策略 |
|
关键字 |
DELETE_TRUNK _OP |
|
日志内容 |
Delete trunk $1. |
|
参数解释 |
$1：端口中继名称 |
|
举例 |
Delete trunk "trunk1". |
|
日志说明 |
用户进行了删除端口中继的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The specified trunk does not exist：指定Trunk不存在 · The controller is not the active leader：当前设备不是Leader控制组件，无法进行此操作 · Token aged：Token已老化 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
CREATE_SUBPORTS_OP |
|
日志内容 |
Created subports to trunk “$1”. The subports information is as follows: $2. |
|
参数解释 |
$1：端口中继名称 $2：子端口信息 |
|
举例 |
Created subports to trunk"trunk". The subports information is as follows: [{ segmentationType=VLAN, portId=d153ce28-a392-4699-ab52-611318199b57, segmentationId=2233}]. |
|
日志说明 |
用户进行了增加子端口的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The specified trunk does not exist：指定Trunk不存在 · The parent port and subport must be the same type：指定父端口和子端口的类型必须一致 · The port ID of the subport is invalid：无效的子端口ID · The subport has been bound to another trunk：指定的子端口已被其他Trunk绑定 · The value of the segmentation_Type on subport must be VLAN：指定的子端口必须为VLAN类型 · The segmentation_Type of the subport is invalid：无效的子端口VLAN类型 · The segmentation ID of the subport is invalid：无效的子端口Segmentation ID · The segmentation ID is out of range：子端口Segmentation ID超出范围 · Duplicate segmentation ID：重复的Segmentation ID · Duplicate subport port ID：重复的子端口ID · The subport does not exist：指定的子端口不存在 · The controller is not the active leader：当前设备不是Leader控制组件，无法进行此操作 · Token aged：Token已老化 · Online vPorts cannot be used as subports：已上线虚拟端口不支持作为子端口 · You have no privilege to perform this operation：用户无权限执行此操作 · Trunks do not support LB, GW, DHCP, or PBR vPorts：Trunk不支持绑定LB、GW、DHCP、PBR类型的虚拟端口 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 · You cannot bind the subport to a port automatically onboarded by southbound packets：子端口不支持绑定南向自动创建的端口 · Online OVS vPorts cannot be used as subports：已上线OVS类型虚拟端口不支持作为子端口 · Online vPorts cannot be used as subports, because the transparent mode is enabled：透传模式开启时，已上线虚拟端口不支持作为子端口 |
|
关键字 |
DELETE_SUBPORTS_OP |
|
日志内容 |
Deleted subports from trunk “$1”. The subports information is as follows: $2. |
|
参数解释 |
$1：端口中继名称 $2：子端口信息 |
|
举例 |
Deleted subports from trunk "trunk". The subports information is as follows: [{ segmentationType=VLAN, portId=f3127698-b31b-4a42-a4aa-66b93ca8238e, segmentationId=122}]. |
|
日志说明 |
用户进行了删除子端口的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The specified trunk does not exist：指定Trunk不存在 · The subport does not exist：指定的子端口不存在 · The controller is not the active leader：当前设备不是Leader控制组件，无法进行此操作 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {IP addresses}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
UPDATE_GLOBALCONFIG_OP |
|
日志内容 |
Updated Network Cloud feature: $1 |
|
参数解释 |
$1：网络云场景开关 |
|
举例 |
Updated Network Cloud feature “true”. |
|
日志说明 |
用户进行了切换网络云场景的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Failed to disable the Network Cloud feature. The controller cannot have virtual link layer networks or external networks：切换网络云场景失败，控制组件中不允许存在虚拟链路层网络和外部网络 · Failed to disable the Network Cloud feature. The controller cannot host vRouters：切换网络云场景失败，控制组件中不允许存在虚拟路由器 · You cannot disable the network cloud feature, because border devices exist：存在边界设备，不能切换网络云场景 · You have no privilege to perform this operation：用户无权限执行此操作 · You cannot enable the network cloud feature when the third-party firewall deployment mode of the device group is hairpin or inline：设备组的对接第三方防火墙开关取值为旁挂或直连时，不允许开启网络云场景开关 · You cannot enable the network cloud scenario when service resources attached to service leaf nodes exist：存在Service Leaf类型服务资源，不允许开启网络云场景开关 · You cannot enable the network cloud scenario if a device group exists whose position is border gateway with firewall deployment off, service leaf, or DC interconnection：存在网络位置为Service Leaf的设备组、网络位置为DC间互联的设备组或网络位置为出口网关且防火墙接入模式开关是关闭的设备组，不允许开启网络云场景开关 |
|
关键字 |
DOWNLOAD_AUDIT_DIFF_OP |
|
日志内容 |
Started downloading audit difference $1. |
|
参数解释 |
$1：审计差异信息文件名 |
|
举例 |
Started downloading audit difference 00-05-00-50-56-9a-6c-08-flow.xlsx. |
|
日志说明 |
用户进行了导出审计差异信息的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The specified resource doesn't exist：指定的资源不存在 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
BATCH_IMPORT_HOST_OP |
|
日志内容 |
Imported “$1” hosts. |
|
参数解释 |
$1：主机数 |
|
举例 |
Imported 2 hosts. |
|
日志说明 |
用户进行了导入主机的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · Invalid IP address：无效的IP地址 · Cannot add the host because no available regions exist：没有可用的Region，不允许添加主机 · The UUID already exists：主机UUID已存在 · Failed to add the host because the domain type is vCenter：vCenter类型的计算域不能添加主机 · The bridge of the host does not match any bridges of VDSs bound to the domain to which the host belongs：主机的Bridge与其所属计算域关联的VDS的Bridge不匹配 · Unknown error：未知错误 · Number of CPUs that can be managed is insufficient. Please purchase a new license or expand the old one：可管理的CPU不足，请购买或扩容vSwitch License · The domain doesn't exist：计算域不存在 · The request is invalid：传入的JSON串错误 · No available IP addresses in the VTEP IP address pool：VTEP IP池没有可分配的IP地址 · Host host, parameter is required：主机host，parameter不能为空 · The host type and the domain type do not match：主机类型与计算域类型不匹配 · The host name cannot exceed 255 characters：主机名称最长255个字符 · The IP address is already used：主机IP地址已经被使用 · No VDS exists in the domain：指定的计算域没有关联VDS · The bridge configuration is invalid. Please verify correctness of the host bridge configuration and reachability of the host IP address：无效的主机桥配置，请检查主机桥配置以及主机IP是否可达 · Bridges on the same host cannot use the same name：同一个主机上的Bridge名称不能相同 · You can select a fabric for a host only from fabrics of VDSs in the domain to which the host belongs：该主机指定的Fabric不在所属计算域中的VDS指定的Fabric列表中 · Insufficient third-party vSwitch licenses：第三方vSwitch不足 · Failed to get the vSwitch version. Please verify the correctness of the OVS version and reachability of the host IP address：获取vSwitch版本失败，请检查OVS版本是否正确以及主机IP是否可达 · You have no privilege to perform this operation：用户无权限执行此操作 · Please specify a compute domain name：计算域名不能为空 · Please specify a fabric：Fabric不能为空 · The fabric does not exist：Fabric不存在 · Invalid OVSDB port number：无效的OVSDB端口号 · The OVSDB port number must be an integer in the range of 0 to 65535：OVSDB端口号范围必须为0~65535的整数 · Invalid template. Please download the latest template：模板不匹配，请使用最新模板 · Failed to read the Excel file. Reason: The hyperlink for cell $1 references relation $2, but that didn't exist：Excel文件读取失败，原因为单元格$1的超链接引用关系$2不存在 |
|
关键字 |
BATCH_DELETE_HOST_OP |
|
日志内容 |
Batch deleted hosts “$1”. |
|
参数解释 |
$1：主机IP地址 |
|
举例 |
Batch deleted hosts “1.1.1.1,1.1.1.2”. |
|
日志说明 |
用户进行了批量删除主机的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · The specified resource doesn't exist：指定的资源不存在 · Cannot delete the host because it is a network element：该主机为网元设备，不允许删除 · Unknown error：未知错误 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
ADD_DHCP_HOST_GROUP_OP |
|
日志内容 |
Created DHCP host group “$1”. |
|
参数解释 |
$1：DHCP主机组的名称 |
|
举例 |
Created DHCP host group “group”. |
|
日志说明 |
用户进行了创建DHCP主机组的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · Please specify a DHCP host group name：DHCP主机组名称不能为空 · The DHCP host group name cannot exceed 255 characters：DHCP主机组名称不能超过255个字符 · Please specify a fabric UUID：Fabric UUID不能为空 · The fabric does not exist：指定的Fabric不存在 · A DHCP host group already exists with the specified UUID：指定的DHCP主机组已存在 · A DHCP host group already exists with the specified name：DHCP主机组名称已存在 · Please examine the DHCP host group UUIDs and make sure they are all unique：存在重复的DHCP主机组UUID · Please examine the DHCP host group names and make sure they are all unique：存在重复的DHCP主机组名称 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
UPDATE_DHCP_HOST_GROUP_OP |
|
日志内容 |
Updated DHCP host group “$1”. |
|
参数解释 |
$1：DHCP主机组的名称 |
|
举例 |
Updated DHCP host group “group”. |
|
日志说明 |
用户进行了修改DHCP主机组的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · Please specify a DHCP host group name：DHCP主机组名称不能为空 · The DHCP host group name cannot exceed 255 characters：DHCP主机组名称不能超过255个字符 · Please specify a fabric UUID：Fabric UUID不能为空 · The fabric does not exist：指定的Fabric不存在 · A DHCP host group already exists with the specified name：DHCP主机组名称已存在 · Cannot edit the fabric UUID：Fabric UUID不支持修改 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
DELETE_DHCP_HOST_GROUP_OP |
|
日志内容 |
Deleted DHCP host group “$1”. |
|
参数解释 |
$1：DHCP主机组的名称 |
|
举例 |
Deleted DHCP host group “group”. |
|
日志说明 |
用户进行了删除DHCP主机组的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · Cannot delete the DHCP host group. The group contains network nodes：DHCP主机组已存在主机，不允许删除 · Cannot delete the DHCP host group. The group has been bound to a vNetwork：虚拟链路层网络已绑定DHCP主机组，不允许删除 · Cannot delete the DHCP host group. The group has been bound to a DHCP resource pool：DHCP主机组已绑定DHCP资源池，不允许删除 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
ADD_DHCP_RESOURCE_OP |
|
日志内容 |
Created DHCP resource pool “$1”. |
|
参数解释 |
$1：DHCP资源池的名称 |
|
举例 |
Created DHCP resource pool “resource”. |
|
日志说明 |
用户进行了创建DHCP资源池的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · Please specify a DHCP resource pool name：DHCP资源池名称不能为空 · You have no privilege to perform this operation：用户无权限执行此操作 · The DHCP resource pool name cannot exceed 255 characters：名称不能超过255个字符 · Please specify a VNI range：VNI范围不能为空 · Invalid VNI range：无效的VNI范围 · Please specify a VNI value in the range of 1 to 16777215：VNI的取值范围为1～16777215的区间 · Please examine the VNI ranges and make sure they do not overlap：VNI范围列表中存在重叠的范围 · Invalid DHCP host group UUID：无效的DHCP主机组UUID · Some of the specified DHCP host groups have not been created yet：DHCP主机组列表内指定DHCP主机组不存在 · Please examine the DHCP host group UUIDs and make sure they are all unique：存在重复的DHCP主机组UUID · A DHCP resource pool already exists with the specified UUID：指定的DHCP资源池已存在 · A DHCP resource pool already exists with the specified name：DHCP资源池名称已存在 · Please specify a DHCP host group that has not been bound to any DHCP resource pool：DHCP主机组已被其他DHCP资源池关联 · The VNI ranges overlap with those in another DHCP resource pool：DHCP资源池中的VNI范围与其他DHCP资源池的VNI范围冲突 · Please examine the DHCP resource pool UUIDs and make sure they are all unique：存在重复的DHCP资源池UUID · Please examine the DHCP resource pool names and make sure they are all unique：存在重复的DHCP资源池名称 · Please make sure no DHCP host groups are added to more than one DHCP resource pool：批量创建DHCP资源池时，不允许绑定相同的DHCP主机组 · Please examine the VNI ranges and make sure they do not overlap：批量创建DHCP资源池时，VNI范围存在冲突 |
|
关键字 |
UPDATE_DHCP_RESOURCE_OP |
|
日志内容 |
Updated DHCP resource pool “$1”. |
|
参数解释 |
$1：DHCP资源池的名称 |
|
举例 |
Updated DHCP resource pool “group”. |
|
日志说明 |
用户进行了修改DHCP资源池的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · Please specify a DHCP resource pool name ：DHCP资源池名称不能为空 · You have no privilege to perform this operation：用户无权限执行此操作 · The DHCP resource pool name cannot exceed 255 characters：名称不能超过255个字符 · Please specify a VNI range：VNI范围不能为空 · Invalid VNI range：无效的VNI范围 · Please specify a VNI value in the range of 1 to 16777215：VNI的取值范围为1～16777215的区间 · Please examine the VNI ranges and make sure they do not overlap：VNI范围列表中存在重叠的范围 · Invalid DHCP host group UUID：无效的DHCP主机组UUID · Some of the specified DHCP host groups have not been created yet：DHCP主机组列表内指定DHCP主机组不存在 · Please examine the DHCP host group UUIDs and make sure they are all unique：存在重复的DHCP主机组UUID · The API does not support editing the DHCP host group list：该接口不允许修改DHCP主机组列表 · The VNI ranges overlap with those in another DHCP resource pool：DHCP资源池中的VNI范围与其他DHCP资源池的VNI范围冲突 · A DHCP resource pool already exists with the specified name：DHCP资源池名称已存在 |
|
关键字 |
DELETE_DHCP_RESOURCE_OP |
|
日志内容 |
Deleted DHCP resource pool “$1”. |
|
参数解释 |
$1：DHCP资源池的名称 |
|
举例 |
Deleted DHCP resource pool “group”. |
|
日志说明 |
用户进行了删除DHCP资源池的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
ADD_HOSTGROUP_INTERFACE_OP |
|
日志内容 |
Added DHCP host group “$1” to DHCP resource pool “$2”. |
|
参数解释 |
$1：DHCP主机组名称 $2：DHCP资源池名称 |
|
举例 |
Added DHCP host group “group” to DHCP resource “resource”. |
|
日志说明 |
用户进行了添加DHCP主机组到DHCP资源池的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · You have no privilege to perform this operation：用户无权限执行此操作 · Invalid DHCP host group UUID：无效的DHCP主机组UUID · Some of the specified DHCP host groups have not been created yet：DHCP主机组列表内指定DHCP主机组不存在 · Please examine the DHCP host group UUIDs and make sure they are all unique：存在重复的DHCP主机组UUID · Some of the specified DHCP host groups have already been added to the DHCP resource pool：列表中存在已属于该DHCP资源池的DHCP主机组 · Please specify a DHCP host group that has not been bound to any DHCP resource pool：DHCP主机组已被其他DHCP资源池关联 |
|
关键字 |
DELETE_HOSTGROUP_INTERFACE_OP |
|
日志内容 |
Deleted DHCP host group “$1” from DHCP resource “$2”. |
|
参数解释 |
$1：DHCP主机组名称 $2：DHCP资源池名称 |
|
举例 |
Delete DHCP host group “group” from DHCP resource “resource”. |
|
日志说明 |
用户进行了从资源池删除DHCP主机组的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The controller is not the active leader：该控制组件不是主Leader · Configuration recovery is in progress：配置恢复未完成 · You have no privilege to perform this operation：用户无权限执行此操作 · The request is invalid：传入的JSON串错误 |
|
关键字 |
UPDATE_DETECT_UPLINK_OP |
|
日志内容 |
Updated the name of the uplink port on the host. Uplink port name: $1. |
|
参数解释 |
$1：上行口名称 |
|
举例 |
Updated the name of the uplink port on the host. Uplink port name: ens255. |
|
日志说明 |
用户进行了修改上行口名称的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The uplink interface name is a case-senstive string of up to 255 characters. Valid characters are letters, digits, underscores (_), hyphens (-) and dots(.)：上行口名称最长255个字符，区分大小写，仅支持字母、数字、下划线、连字符和点 · You have no privilege to perform this operation：用户无权限执行此操作 |
|
关键字 |
FLOW_BACKUP_OP |
|
日志内容 |
· 如果所有主机的流表备份失败，日志内容为“Backed up flow tables.” · 若所有主机的流表都备份完成，日志内容为“Backup completed on all selected hosts.”。 · 若部分主机的流表恢复完成，日志内容为“Backup succeeded on hosts: $1”。 · 若没有主机进行备份，日志内容为“Backup not performed on any one of the hosts. Please check for backup-incapable hosts or OVS bridge disconnection.”。 |
|
参数解释 |
$1：已完成流表备份操作的主机IP地址 |
|
举例 |
· Backed up flow tables. · Backup completed on all selected hosts. · Backup succeeded on hosts: 98.0.69.8,98.0.69.9 · Backup not performed on any one of the hosts. Please check for backup-incapable hosts or OVS bridge disconnection. |
|
日志说明 |
用户进行了对所有主机的流表进行备份的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · OpenFlow connections are disconnected on some hosts：存在OpenFlow断连的主机 · The specified device doesn't exist：指定的设备不存在 · Invalid IP address：无效的IP地址 · Unknown error：未知错误 · The value for the coverage field must be all or batch：coverage字段取值必须为all或者batch · The host list cannot be empty when the coverage field is set to batch：当coverage取值为batch时，主机列表不能为空 · Host configuration obtaining or deployment timed out：获取或下发主机配置超时 |
|
关键字 |
FLOW_RESTORE_OP |
|
日志内容 |
· 若所有主机的流表恢复失败，日志内容为“Restored flow tables. ” · 若所有主机的流表都恢复完成，日志内容为“Restoration completed on all selected hosts.”。 · 若部分主机的流表恢复完成，日志内容为“Restoration succeeded on hosts: $1”。 · 若没有主机进行恢复，日志内容为“Restoration not performed on any one of the hosts. Please check for restoration-incapable hosts or OVS bridge disconnection.”。 |
|
参数解释 |
$1：已完成流表恢复操作的主机IP地址 |
|
举例 |
· Restored flow tables. · Restoration completed on all selected hosts. · Restoration succeeded on hosts: 98.0.69.8,98.0.69.9 · Restoration not performed on any one of the hosts. Please check for restoration-incapable hosts or OVS bridge disconnection. |
|
日志说明 |
用户进行了对所有主机的流表进行恢复的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Please specify a file name：流表还原文件名称不能为空 · The flow table restoration mode can only be replace or merge：流表还原策略取值必须为replace或merge · OpenFlow connections are disconnected on some hosts：存在OpenFlow断连的主机 · The specified device doesn't exist：指定的设备不存在 · Invalid IP address：无效的IP地址 · Unknown error：未知错误 · The request is invalid：传入的JSON串错误 · The value for the coverage field must be all or batch：coverage字段取值必须为all或者batch · The host list cannot be empty when the coverage field is set to batch：当coverage取值为batch时，主机列表不能为空 · Host configuration obtaining or deployment timed out：获取或下发主机配置超时 |
|
关键字 |
PUT_BACKUP_OP |
|
日志内容 |
Updated settings: $1 |
|
参数解释 |
$1：更新后的参数 |
|
举例 |
Updated settings: backup_enable: true, backup_internal: 12, backup_filenumber: 10, delete_backup_file: false |
|
日志说明 |
用户进行了更新参数设置的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The backup interval must be an integer in the range of 1 to 128：备份时间间隔取值为1～128的整数 · The maximum number of files to retain must be an integer in the range of 1 to 30：流表备份文件个数取值为1～30的整数 · Unknown error：未知错误 · The request is invalid：传入的JSON串错误 |
|
关键字 |
UPDATE_GLOBALCONFIG_OP |
|
日志内容 |
Set the state of the auto identification of vPorts without host IDs in network overlay feature to $1. |
|
参数解释 |
$1：网络Overlay虚IP占位端口自动识别开关 |
|
举例 |
Set the state of the auto identification of vPorts without host IDs in network overlay feature to On. |
|
日志说明 |
用户进行了切换网络Overlay虚IP占位端口自动识别开关的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · 无 |
|
关键字 |
CREATE_NQAPOLICY_OP |
|
日志内容 |
Created NqaProfile “$1”. |
|
参数解释 |
$1：NQA策略的名称 |
|
举例 |
Created NqaProfile “nqa1”. |
|
日志说明 |
用户进行了创建NQA策略的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · An NQA profile already exists with the specified name：指定NQA策略名称已存在 · An NQA operation already exists with the specified admin name and tag：NQA测试组的管理员名称和操作标签已存在 · The NQA profile name cannot exceed 255 characters：NQA策略名称最长255个字符 · The NQA operation admin name cannot exceed 32 bytes, case insensitive, Hyphens (-) and question marks (?) are not supported：测试组管理员名称最长32个字节，不区分大小写，不支持连字符和“?” · The NQA operation tag cannot exceed 32 bytes, case insensitive, Hyphens (-) and question marks (?) are not supported：测试组操作标签名称最长32个字节，不区分大小写，不支持连字符和“?” · The NQA description cannot exceed 255 characters：NQA描述信息最长255个字符 · Please specify an NQA profile name：NQA策略名称不能为空 · You cannot specify an NQA operation admin name when the manual NQA profile mode is used： 当NQA策略配置为手动时，不能配置测试组管理员 · You cannot specify an NQA operation tag when the manual NQA profile mode is used：当NQA策略配置为手动时，不能配置测试组操作标签 · You cannot specify an NQA probe interval when the manual NQA profile mode is used：当NQA策略配置为手动时，不能配置探测时间间隔 · You cannot specify the maximum number of consecutive NQA probe failures when the manual NQA profile mode is used：当NQA策略配置为手动时，不能配置探测失败次数 · Please specify an NQA track entry number：当NQA策略配置为手动时，必须配置Track项序号 · You cannot specify an NQA track entry number when the auto NQA profile mode is used：当NQA策略配置为自动时，不能配置Track项序号 · The track entry number must be an integer in the range of 1 to 512：Track项序号取值范围为1～512的整数 · The system failed to assign an administrator name or operation tag to the NQA profile：系统自动分配NQA测试组管理员名称或测试标签失败 |
|
关键字 |
UPDATE_NQAPOLICY_OP |
|
日志内容 |
Updated NqaProfile “$1”. |
|
参数解释 |
$1：NQA策略的名称 |
|
举例 |
Updated NqaProfile “nqa1”. |
|
日志说明 |
用户进行了修改NQA策略的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The NQA description cannot exceed 255 characters：NQA描述信息最长255个字符 · An NQA profile already exists with the specified name：指定NQA策略名称已存在 · The NQA profile name cannot exceed 255 characters：NQA策略名称最长255个字符 · The NQA operation admin name cannot be edited：测试组管理员不允许修改 · The NQA operation tag cannot be edited：测试组操作标签不允许修改 · The probe interval cannot be edited：探测时间间隔不允许修改 · The probe failure count cannot be edited：探测失败次数不允许修改 |
|
关键字 |
DELETE_NQAPOLICY_OP |
|
日志内容 |
Deleted NqaProfile “$1”. |
|
参数解释 |
$1：NQA策略的名称 |
|
举例 |
Deleted NqaProfile “nqa1”. |
|
日志说明 |
用户进行了删除NQA策略的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The specified NQA profile has been bound to another service resource：指定的NQA策略已被其他服务资源绑定 · The NQA profile has been bound to an external network and cannot be deleted：指定的NQA策略已被外部网络绑定，不允许删除 · The NQA profile cannot be deleted, because it has been bound to a route entry：指定的NQA策略已被路由表项绑定，不允许删除 · The NQA profile cannot be deleted, because it has been bound to a service path：指定的NQA策略已被服务路径绑定，不允许删除 · The specified NQA profile has been bound to a service path：该NQA策略已经被服务路径绑定 |
|
关键字 |
EXPORT_FLOATING_IP_OP |
|
日志内容 |
Exported floating IPs. |
|
参数解释 |
无 |
|
举例 |
Exported floating IPs. |
|
日志说明 |
用户进行了导出浮动IP信息的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · Failed to export floating IP addresses：导出浮动IP异常 |
|
关键字 |
CREATE_BYPASS_LINK_OP |
|
日志内容 |
Created bypass link "Type: $1, Local vPort: $2, Local IP Address: $3, Remote IP Address: $4, Remote VTEP IP: $5". |
|
参数解释 |
$1：流表短接模式 $2：本端端口名称或UUID $3：本端IP地址 $4：对端IP地址 $5：对端VTEP IP地址 |
|
举例 |
Created bypass link "Type: Bidirectional, Local vPort: tapvm1, Local IP Address: 1.0.0.1, Remote IP Address: 2.0.0.1, Remote VTEP IP: 40.0.29.103" |
|
日志说明 |
用户进行了创建流表短接的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The bypass link already exists：该流表短接已经存在 · Invalid IP address：无效的IP地址 · The ID already exists：ID已存在 · Failed to obtain the MAC address of the distributed gateway：获取分布式网关MAC失败 · Please specify the local port ID：本端端口ID不能为空 · The local resource type is invalid：本端类型不合法 · Please specify the local IP address：本端IP地址不能为空 · The local port does not exist：指定的本端端口不存在 · You must specify the L2VNI when the remote resource type is type-2 route：对端是二类路由类型时，L2VNI不能为空 · The local port is invalid：无效的本端端口 · The remote port is invalid：无效的对端端口 · The bypass link type is invalid：无效的短接模式 · The device does not exist：指定的设备不存在 · The remote resource type is invalid：对端的类型不合法 · Please specify the remote port ID：对端端口ID不能为空 · Please specify the remote IP address：对端IP地址不能为空 · The remote port does not exist：指定的对端端口不存在 · Please specify the remote VTEP IP and remote VTEP router MAC：对端VTEP IP和对端VTEP Router MAC都不能为空 · The remote resource type is external network. You must bind an external network and a border gateway to the vRouter attached to the subnet that contains the local port：当对端IP类型为“外网”时，本端端口所在子网绑定的虚拟路由器必须绑定外部网络和出口网关 · The local port and remote port must be different：本端端口和对端端口不能相同 · The local and remote IP versions must be the same：本端IP地址和对端IP地址必须为相同IP版本 · The local and remote VTEP IP versions must be the same：VTEP IP版本不一致 · The type-2 route does not exist：指定的二类路由未找到 · The IP address of the remote host is invalid：无效的对端主机IP地址 · The remote VTEP IP address is invalid：对端VTEP IP地址无效 · The local and remote devices must belong to the same fabric：本端设备和对端设备必须在相同Fabric下 · A centralized vRouter link must have been established between the vRouters attached to the subnet containing the local IP and the subnet containing the remote IP：本端IP所在子网绑定的虚拟路由器和对端IP所在子网绑定的虚拟路由器必须建立集中式虚拟路由器互通 · Failed to obtain the default route：获取默认路由失败 · You must specify the L2VNI when the remote resource type is type-2 route：对端是二类路由类型时，L2VNI不能为空 · The MAC address of the router is invalid：无效的短接模式 · The value range for the L2VNI is 1 to 16777215：L2VNI取值范围为1～16777215 · The OpenFlow connection to the OVS host where the local port resides is down：本端端口所在主机的OpenFlow连接断开 · The OpenFlow connection to the OVS host where the remote port resides is down：对端端口所在主机的OpenFlow连接断开 · The route entry does not exist：指定的路由表项未找到 · Please bind a vRouter to the subnet that contains the local IP or any IP of the same version as the local IP on the local vPort：本端端口对应协议栈的IP所在子网必须绑定虚拟路由器 · The remote VTEP IP address is invalid：对端VTEP IP地址无效 · The local port and remote port must be different：本端端口和对端端口不能相同 · You must specify the MAC address of the local port：本端端口MAC地址不能为空 · You must specify the MAC address of the remote port：对端端口MAC地址不能为空 |
|
关键字 |
UPDATE_BYPASS_LINK_OP |
|
日志内容 |
Updated bypass link “Type: Bidirectional, Local vPort: tapvm1, Local IP Address: 1.0.0.1, Remote IP Address: 2.0.0.1, Remote VTEP IP: 40.0.29.103” |
|
参数解释 |
$1：流表短接模式 $2：本端端口名称或UUID $3：本端IP地址 $4：对端IP地址 $5：对端VTEP IP地址 |
|
举例 |
Updated bypass link “Type: Bidirectional, Local vPort: tapvm1, Local IP Address: 1.0.0.1, Remote IP Address: 2.0.0.1, Remote VTEP IP: 40.0.29.103” |
|
日志说明 |
用户进行了修改流表短接的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The request is invalid：传入的JSON串错误 · The bypass link flow entry has been deployed：短接流表项已下发 · Invalid IP address：无效的IP地址 · Failed to obtain the MAC address of the distributed gateway：获取分布式网关MAC失败 · Please specify the local port ID：本端端口ID不能为空 · The local resource type is invalid：本端类型不合法 · Please specify the local IP address：本端IP地址不能为空 · The local port does not exist：指定的本端端口不存在 · You must specify the L2VNI when the remote resource type is type-2 route：对端是二类路由类型时，L2VNI不能为空 · The local port is invalid：无效的本端端口 · The remote port is invalid：无效的对端端口 · The bypass link type is invalid：无效的短接模式 · The device does not exist：指定的设备不存在 · The remote resource type is invalid：对端的类型不合法 · Please specify the remote port ID：对端端口ID不能为空 · Please specify the remote IP address：对端IP地址不能为空 · The remote port does not exist：指定的对端端口不存在 · Please specify the remote VTEP IP and remote VTEP router MAC：对端VTEP IP和对端VTEP Router MAC都不能为空 · The remote resource type is external network. You must bind an external network and a border gateway to the vRouter attached to the subnet that contains the local port：当对端IP类型为“外网”时，本端端口所在子网绑定的虚拟路由器必须绑定外部网络和出口网关 · The local port and remote port must be different：本端端口和对端端口不能相同 · The local and remote IP versions must be the same：本端IP地址和对端IP地址必须为相同IP版本 · The local and remote VTEP IP versions must be the same：VTEP IP版本不一致 · The type-2 route does not exist：指定的二类路由未找到 · The IP address of the remote host is invalid：无效的对端主机IP地址 · The remote VTEP IP address is invalid：对端VTEP IP地址无效 · The local and remote devices must belong to the same fabric：本端设备和对端设备必须在相同Fabric下 · Failed to obtain the default route：获取默认路由失败 · You must specify the L2VNI when the remote resource type is type-2 route：对端是二类路由类型时，L2VNI不能为空 · The MAC address of the router is invalid：无效的短接模式 · The value range for the L2VNI is 1 to 16777215：L2VNI取值范围为1～16777215 · The OpenFlow connection to the OVS host where the local port resides is down：本端端口所在主机的OpenFlow连接断开 · The OpenFlow connection to the OVS host where the remote port resides is down：对端端口所在主机的OpenFlow连接断开 · Please bind a vRouter to the subnet that contains the local IP or any IP of the same version as the local IP on the local vPort：本端端口对应协议栈的IP所在子网必须绑定虚拟路由器 · The remote VTEP IP address is invalid：对端VTEP IP地址无效 · The local port and remote port must be different：本端端口和对端端口不能相同 · You must specify the MAC address of the local port：本端端口MAC地址不能为空 · You must specify the MAC address of the remote port：对端端口MAC地址不能为空 |
|
关键字 |
DELETE_BYPASS_LINK_OP |
|
日志内容 |
Deleted bypass link "Type: $1, Local vPort: $2, Local IP Address: $3, Remote IP Address: $4, Remote VTEP IP: $5". |
|
参数解释 |
$1：流表短接模式 $2：本端端口名称或UUID $3：本端IP地址 $4：对端IP地址 $5：对端VTEP IP地址 |
|
举例 |
Deleted bypass link “Type: Bidirectional, Local vPort: tapvm1, Local IP Address: 1.0.0.1, Remote IP Address: 2.0.0.1, Remote VTEP IP: 40.0.29.103” |
|
日志说明 |
用户进行了删除流表短接的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · 无 |
|
关键字 |
DEPLOYED_BYPASS_LINK_FLOW_ENTRIES_FOR_BYPASS_LINK_OP |
|
日志内容 |
Deployed bypass link flow entries for bypass link "Type: $1, Local vPort: $2, Local IP Address: $3, Remote IP Address: $4, Remote VTEP IP: $5". |
|
参数解释 |
$1：流表短接模式 $2：本端端口名称或UUID $3：本端IP地址 $4：对端IP地址 $5：对端VTEP IP地址 |
|
举例 |
Deployed bypass link flow entries for bypass link“Type: Bidirectional, Local vPort: tapvm1, Local IP Address: 1.0.0.1, Remote IP Address: 2.0.0.1, Remote VTEP IP: 40.0.29.103” |
|
日志说明 |
用户进行了下发短接流表表项的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The bypass link flow entry has been deployed：短接流表项已下发 · The OpenFlow connection to the OVS host where the local port resides is down：本端端口所在主机的OpenFlow连接断开 · The OpenFlow connection to the OVS host where the remote port resides is down：对端端口所在主机的OpenFlow连接断开 |
|
关键字 |
AUDIT_TASK_ALL_OP |
|
日志内容 |
Audited all bypass links. |
|
参数解释 |
无 |
|
举例 |
Audited all bypass links. |
|
日志说明 |
用户进行了审计当前所有的短接流表的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The specified resource doesn't exist：指定的资源不存在 · The request is invalid：传入的JSON串错误 · The bypass link type is invalid：无效的短接模式 · The local IP and the remote IP must be different：本端ip和对端ip不能相同 · Please specify the local IP address：本端IP地址不能为空 · Please specify the remote IP address：对端IP地址不能为空 · Invalid IP address：无效的IP地址 · The local resource type is invalid：本端类型不合法 · The remote resource type is invalid：对端的类型不合法 · Please specify the local port ID：本端端口ID不能为空 · The local port does not exist：指定的本端端口不存在 · The local port is invalid：无效的本端端口 · The remote resource type is invalid：对端类型不合法 · Please specify the remote port ID：对端端口ID不能为空 · You must specify the L2VNI when the remote resource type is type-2 route：对端是二类路由类型时，L2VNI不能为空 · The type-2 route does not exist：指定的二类路由未找到 · Please specify the remote VTEP IP and remote VTEP router MAC：对端VTEP IP和对端VTEP Router MAC都不能为空 · The remote VTEP IP address is invalid：对端VTEP IP地址无效 · The MAC address of the router is invalid：无效的路由器MAC地址 · The remote port does not exist：指定的对端端口不存在 · The remote port is invalid：无效的对端端口 · The IP address of the remote host is invalid：无效的对端主机IP地址 · lease bind a vRouter to the subnet that contains the local IP or any IP of the same version as the local IP on the local vPort：本端端口对应协议栈的IP所在子网必须绑定虚拟路由器 · The device does not exist：指定的设备不存在 · Failed to obtain the default route：获取默认路由失败 · The local and remote IP versions must be the same：本端IP地址和对端IP地址必须为相同IP版本 · The local and remote VTEP IP versions must be the same：VTEP IP版本不一致 · The local port and remote port must be different：本端端口和对端端口不能相同 · You must specify the MAC address of the local port：本端端口MAC地址不能为空 · You must specify the MAC address of the remote port：对端端口MAC地址不能为空 · The bypass link already exists：该流表短接已经存在 · The local and remote devices must belong to the same fabric：本端设备和对端设备必须在相同Fabric下 · The OpenFlow connection to the OVS host where the local port resides is down：本端端口所在主机的OpenFlow连接断开 · The OpenFlow connection to the OVS host where the remote port resides is down：对端端口所在主机的OpenFlow连接断开 · Failed to obtain the MAC address of the distributed gateway：获取分布式网关MAC失败 |
|
关键字 |
AUDIT_TASK_OP |
|
日志内容 |
Audited bypass link $1. |
|
参数解释 |
$1：流表表项 |
|
举例 |
Audited bypass link [“5e5c0769-3b4f-4576-a242-4b3da18e7174”, “3e5c0769-3b4f-4576-a242-4b3da18e7176”]. |
|
日志说明 |
用户进行了审计指定短接流表的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The specified resource doesn't exist：指定的资源不存在 · The request is invalid：传入的JSON串错误 · The bypass link type is invalid：无效的短接模式 · The local IP and the remote IP must be different：本端ip和对端ip不能相同 · Please specify the local IP address：本端IP地址不能为空 · Please specify the remote IP address：对端IP地址不能为空 · Invalid IP address：无效的IP地址 · The local resource type is invalid：本端类型不合法 · The remote resource type is invalid：对端的类型不合法 · Please specify the local port ID：本端端口ID不能为空 · The local port does not exist：指定的本端端口不存在 · The local port is invalid：无效的本端端口 · The remote resource type is invalid：对端类型不合法 · Please specify the remote port ID：对端端口ID不能为空 · You must specify the L2VNI when the remote resource type is type-2 route：对端是二类路由类型时，L2VNI不能为空 · The type-2 route does not exist：指定的二类路由未找到 · Please specify the remote VTEP IP and remote VTEP router MAC：对端VTEP IP和对端VTEP Router MAC都不能为空 · The remote VTEP IP address is invalid：对端VTEP IP地址无效 · The MAC address of the router is invalid：无效的路由器MAC地址 · The remote port does not exist：指定的对端端口不存在 · The remote port is invalid：无效的对端端口 · The IP address of the remote host is invalid：无效的对端主机IP地址 · lease bind a vRouter to the subnet that contains the local IP or any IP of the same version as the local IP on the local vPort：本端端口对应协议栈的IP所在子网必须绑定虚拟路由器 · The device does not exist：指定的设备不存在 · Failed to obtain the default route：获取默认路由失败 · The local and remote IP versions must be the same：本端IP地址和对端IP地址必须为相同IP版本 · The local and remote VTEP IP versions must be the same：VTEP IP版本不一致 · The local port and remote port must be different：本端端口和对端端口不能相同 · You must specify the MAC address of the local port：本端端口MAC地址不能为空 · You must specify the MAC address of the remote port：对端端口MAC地址不能为空 · The bypass link already exists：该流表短接已经存在 · The local and remote devices must belong to the same fabric：本端设备和对端设备必须在相同Fabric下 · The OpenFlow connection to the OVS host where the local port resides is down：本端端口所在主机的OpenFlow连接断开 · The OpenFlow connection to the OVS host where the remote port resides is down：对端端口所在主机的OpenFlow连接断开 · Failed to obtain the MAC address of the distributed gateway：获取分布式网关MAC失败 |
|
关键字 |
IMPORT_CREATE_NETWORK_OP |
|
日志内容 |
Bulk created vNetworks: $1. |
|
参数解释 |
$1：批量操作信息 |
|
举例 |
Bulk created vNetworks: fileName:[虚拟链路层网络-2021-05-27 03-45-44.xlsx], totalNum:[40], successNum:[1], failedNum:[39]. |
|
日志说明 |
用户进行了批量创建虚拟链路层网络操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · Incorrect file name：文件名错误 · Failed to read the Excel file：Excel文件读取失败 · Failed to parse data：数据解析错误 · Failed to read the Excel file. Reason: The hyperlink for cell $1 references relation $2, but that didn't exist：Excel文件读取失败，原因为单元格$1的超链接引用关系$2不存在 · Invalid value for the gateway disabling feature：无效的禁用网关 · The file does not exist：文件不存在 · The value of the vSwitch Flooding field is invalid：无效的虚拟交换机泛洪 · The value of the vSwitch Learning field is invalid：无效的虚拟交换机自学习 |
|
关键字 |
IMPORT_UPDATE_NETWORK_OP |
|
日志内容 |
Bulk updated vNetworks: $1. |
|
参数解释 |
$1：批量操作信息 |
|
举例 |
Bulk updated vNetworks: fileName:[虚拟链路层网络-2021-05-27 03-45-44.xlsx], totalNum:[40], successNum:[1], failedNum:[39]. |
|
日志说明 |
用户进行了批量更新虚拟链路层网络操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · Incorrect file name：文件名错误 · Failed to read the Excel file：Excel文件读取失败 · Failed to parse data：数据解析错误 · Failed to read the Excel file. Reason：The hyperlink for cell $1 references relation $2, but that didn't exist：Excel文件读取失败，原因为单元格$1的超链接引用关系$2不存在 · Invalid value for the gateway disabling feature：无效的禁用网关 · The file does not exist：文件不存在 · The value of the vSwitch Flooding field is invalid：无效的虚拟交换机泛洪 · The value of the vSwitch Learning field is invalid：无效的虚拟交换机自学习 |
|
关键字 |
IMPORT_DELETE_NETWORK_OP |
|
日志内容 |
Bulk deleted vNetworks: $1. |
|
参数解释 |
$1：批量操作信息 |
|
举例 |
Bulk deleted vNetworks: fileName:[虚拟链路层网络-2021-05-27 03-45-44.xlsx], totalNum:[40], successNum:[1], failedNum:[39]. |
|
日志说明 |
用户进行了批量删除虚拟链路层网络操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · Incorrect file name：文件名错误 · Failed to read the Excel file：Excel文件读取失败 · Failed to parse data：数据解析错误 · Failed to read the Excel file. Reason: The hyperlink for cell $1 references relation $2, but that didn't exist：Excel文件读取失败，原因为单元格$1的超链接引用关系$2不存在 · The file does not exist：文件不存在 |
|
关键字 |
EXPORT_NETWORK_OP |
|
日志内容 |
Bulk exported vNetworks: $1. |
|
参数解释 |
$1：批量操作信息 |
|
举例 |
Bulk exported vNetworks: 虚拟链路层网络-2021-06-03 03-51-24.xlsx. |
|
日志说明 |
用户进行了批量导出虚拟链路层网络操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · Failed to export the file：Excel文件导出失败 |
|
关键字 |
IMPORT_CREATE_EXTERNAL NETWORK_OP |
|
日志内容 |
Bulk created external networks: $1. |
|
参数解释 |
$1：批量操作信息 |
|
举例 |
Bulk created external networks: fileName:[外部网络-2021-05-27 03-45-44.xlsx], totalNum:[40], successNum:[1], failedNum:[39]. |
|
日志说明 |
用户进行了批量创建外部网络操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · Incorrect file name：文件名错误 · Failed to read the Excel file：Excel文件读取失败 · Failed to parse data：数据解析错误 · Failed to read the Excel file. Reason: The hyperlink for cell $1 references relation $2, but that didn't exist：Excel文件读取失败，原因为单元格$1的超链接引用关系$2不存在 · The file does not exist：文件不存在 |
|
关键字 |
IMPORT_UPDATE_EXTERNAL NETWORK_OP |
|
日志内容 |
Bulk updated external networks: $1. |
|
参数解释 |
$1：批量操作信息 |
|
举例 |
Bulk updated external networks: fileName:[外部网络-2021-05-27 03-45-44.xlsx], totalNum:[40], successNum:[1], failedNum:[39]. |
|
日志说明 |
用户进行了批量更新外部网络操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · Incorrect file name：文件名错误 · Failed to read the Excel file：Excel文件读取失败 · Failed to parse data：数据解析错误 · Failed to read the Excel file. Reason: The hyperlink for cell $1 references relation $2, but that didn't exist：Excel文件读取失败，原因为单元格$1的超链接引用关系$2不存在 · The file does not exist：文件不存在 |
|
关键字 |
IMPORT_DELETE_EXTERNAL NETWORK_OP |
|
日志内容 |
Bulk deleted external networks: $1. |
|
参数解释 |
$1：批量操作信息 |
|
举例 |
Bulk deleted external networks: fileName:[外部网络-2021-05-27 03-45-44.xlsx], totalNum:[40], successNum:[1], failedNum:[39]. |
|
日志说明 |
用户进行了批量删除外部网络操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · Incorrect file name：文件名错误 · Failed to read the Excel file：Excel文件读取失败 · Failed to parse data：数据解析错误 · Failed to read the Excel file. Reason: The hyperlink for cell $1 references relation $2, but that didn't exist：Excel文件读取失败，原因为单元格$1的超链接引用关系$2不存在 · The file does not exist：文件不存在 |
|
关键字 |
EXPORT_EXTERNAL NETWORK_OP |
|
日志内容 |
Bulk exported external networks: $1. |
|
参数解释 |
$1：批量操作信息 |
|
举例 |
Bulk exported external networks: 外部网络-2021-06-03 03-51-24.xlsx. |
|
日志说明 |
用户进行了批量导出外部网络操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · Failed to export the file：Excel文件导出失败 |
|
关键字 |
IMPORT_CREATE_SUBNET_OP |
|
日志内容 |
Bulk created subnets: $1. |
|
参数解释 |
$1：批量操作信息 |
|
举例 |
Bulk created subnets: fileName:[虚拟子网-2021-05-27 03-45-44.xlsx], totalNum:[40], successNum:[1], failedNum:[39]. |
|
日志说明 |
用户进行了批量创建虚拟子网操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · Incorrect file name：文件名错误 · Failed to read the Excel file：Excel文件读取失败 · Failed to parse data：数据解析错误 · Failed to read the Excel file. Reason: The hyperlink for cell $1 references relation $2, but that didn't exist：Excel文件读取失败，原因为单元格$1的超链接引用关系$2不存在 · The file does not exist：文件不存在 · The vRouter is bound to a gateway that uses the manual method to deploy basic external connectivity settings and that is enabled with external route reduction. It cannot be bound to any internal subnet addresses of other vRouters bound to the gateway：虚拟路由器已绑定外网转发基础配置为手动预配置且外网路由精简开启的出口网关时，虚拟路由器不允许绑定与该出口网关绑定的其他虚拟路由器网段相同的内网子网 |
|
关键字 |
IMPORT_UPDATE_SUBNET_OP |
|
日志内容 |
Bulk updated subnets: $1. |
|
参数解释 |
$1：批量操作信息 |
|
举例 |
Bulk updated subnets: fileName:[虚拟子网-2021-05-27 03-45-44.xlsx], totalNum:[40], successNum:[1], failedNum:[39]. |
|
日志说明 |
用户进行了批量更新虚拟子网操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · Incorrect file name：文件名错误 · Failed to read the Excel file：Excel文件读取失败 · Failed to parse data：数据解析错误 · Failed to read the Excel file. Reason: The hyperlink for cell $1 references relation $2, but that didn't exist：Excel文件读取失败，原因为单元格$1的超链接引用关系$2不存在 · The file does not exist：文件不存在 · The vRouter is bound to a gateway that uses the manual method to deploy basic external connectivity settings and that is enabled with external route reduction. It cannot be bound to any internal subnet addresses of other vRouters bound to the gateway：虚拟路由器已绑定外网转发基础配置为手动预配置且外网路由精简开启的出口网关时，虚拟路由器不允许绑定与该出口网关绑定的其他虚拟路由器网段相同的内网子网 |
|
关键字 |
IMPORT_DELETE_SUBNET_OP |
|
日志内容 |
Bulk deleted subnets: $1. |
|
参数解释 |
$1：批量操作信息 |
|
举例 |
Bulk deleted subnets: fileName:[虚拟子网-2021-05-27 03-45-44.xlsx], totalNum:[40], successNum:[1], failedNum:[39]. |
|
日志说明 |
用户进行了批量删除虚拟子网操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · Incorrect file name：文件名错误 · Failed to read the Excel file：Excel文件读取失败 · Failed to parse data：数据解析错误 · Failed to read the Excel file. Reason: The hyperlink for cell $1 references relation $2, but that didn't exist：Excel文件读取失败，原因为单元格$1的超链接引用关系$2不存在 · The file does not exist：文件不存在 |
|
关键字 |
EXPORT_SUBNET_OP |
|
日志内容 |
Bulk exported subnets: $1. |
|
参数解释 |
$1：批量操作信息 |
|
举例 |
Bulk exported subnets: 虚拟子网-2021-06-03 03-51-24.xlsx. |
|
日志说明 |
用户进行了批量导出虚拟子网操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · Failed to export the file：Excel文件导出失败 |
|
关键字 |
IMPORT_CREATE_VPORT_OP |
|
日志内容 |
Bulk created vPorts: $1. |
|
参数解释 |
$1：批量操作信息 |
|
举例 |
Bulk created vPorts: fileName:[虚拟端口-2021-05-27 03-45-44.xlsx], totalNum:[40], successNum:[1], failedNum:[39]. |
|
日志说明 |
用户进行了批量创建虚拟端口操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · Incorrect file name：文件名错误 · Failed to read the Excel file：Excel文件读取失败 · Failed to parse data：数据解析错误 · Failed to read the Excel file. Reason: The hyperlink for cell $1 references relation $2, but that didn't exist：Excel文件读取失败，原因为单元格$1的超链接引用关系$2不存在 · The file does not exist：文件不存在 |
|
关键字 |
IMPORT_UPDATE_VPORT_OP |
|
日志内容 |
Bulk updated vPorts: $1. |
|
参数解释 |
$1：批量操作信息 |
|
举例 |
Bulk updated vPorts: fileName:[虚拟端口-2021-05-27 03-45-44.xlsx], totalNum:[40], successNum:[1], failedNum:[39]. |
|
日志说明 |
用户进行了批量更新虚拟端口操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · Incorrect file name：文件名错误 · Failed to read the Excel file：Excel文件读取失败 · Failed to parse data：数据解析错误 · Failed to read the Excel file. Reason: The hyperlink for cell $1 references relation $2, but that didn't exist：Excel文件读取失败，原因为单元格$1的超链接引用关系$2不存在 · The file does not exist：文件不存在 |
|
关键字 |
IMPORT_DELETE_VPORT_OP |
|
日志内容 |
Bulk deleted vPorts: $1. |
|
参数解释 |
$1：批量操作信息 |
|
举例 |
Bulk deleted vPorts: fileName:[虚拟端口-2021-05-27 03-45-44.xlsx], totalNum:[40], successNum:[1], failedNum:[39]. |
|
日志说明 |
用户进行了批量删除虚拟端口操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · Incorrect file name：文件名错误 · Failed to read the Excel file：Excel文件读取失败 · Failed to parse data：数据解析错误 · Failed to read the Excel file. Reason: The hyperlink for cell $1 references relation $2, but that didn't exist：Excel文件读取失败，原因为单元格$1的超链接引用关系$2不存在 · The file does not exist：文件不存在 |
|
关键字 |
EXPORT_VPORT_OP |
|
日志内容 |
Bulk exported vPorts: $1. |
|
参数解释 |
$1：批量操作信息 |
|
举例 |
Bulk exported vPorts: 虚拟端口-2021-06-03 03-51-24.xlsx. |
|
日志说明 |
用户进行了批量导出虚拟端口操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · Failed to export the file：Excel文件导出失败 |
|
关键字 |
IMPORT_CREATE_VROUTER_OP |
|
日志内容 |
Bulk created vRouters: $1. |
|
参数解释 |
$1：批量操作信息 |
|
举例 |
Bulk created vRouters: fileName:[虚拟路由器-2021-05-27 03-45-44.xlsx], totalNum:[40], successNum:[1], failedNum:[39]. |
|
日志说明 |
用户进行了批量创建虚拟路由器操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · Incorrect file name：文件名错误 · Failed to read the Excel file：Excel文件读取失败 · Failed to parse data：数据解析错误 · Invalid setting for the feature that allows the vRouter to always provide external IPv6 connectivity for its connected remote vRouters：无效的手动配置IPv6外部网络 · Failed to read the Excel file. Reason: The hyperlink for cell $1 references relation $2, but that didn't exist：Excel文件读取失败，原因为单元格$1的超链接引用关系$2不存在 · The value for the Import Only One Route for Routes with the Same RD feature is invalid：相同RD BGP路由优选字段取值无效 · The file does not exist：文件不存在 |
|
关键字 |
IMPORT_UPDATE_VROUTER_OP |
|
日志内容 |
Bulk updated vRouters: $1. |
|
参数解释 |
$1：批量操作信息 |
|
举例 |
Bulk updated vRouters: fileName:[虚拟路由器-2021-05-27 03-45-44.xlsx], totalNum:[40], successNum:[1], failedNum:[39]. |
|
日志说明 |
用户进行了批量更新虚拟路由器操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · Incorrect file name：文件名错误 · Failed to read the Excel file：Excel文件读取失败 · Failed to parse data：数据解析错误 · Invalid setting for the feature that allows the vRouter to always provide external IPv6 connectivity for its connected remote vRouters：无效的手动配置IPv6外部网络 · Failed to read the Excel file. Reason: The hyperlink for cell $1 references relation $2, but that didn't exist：Excel文件读取失败，原因为单元格$1的超链接引用关系$2不存在 · Failed to edit vRouters numbered %s to %s. Failure reason for vRouter %s: %s.第n个至第m个虚拟路由器修改失败，第n个虚拟路由器修改失败原因为：xxx · Failed to edit the last vRouter. Failure reason: %s：最后一个虚拟路由器修改失败，原因为：xxx · The value for the Import Only One Route for Routes with the Same RD feature is invalid：相同RD BGP路由优选字段取值无效 · The file does not exist：文件不存在 · The user does not have the permission to update transit vRouter：用户无权限更新TRANSIT类型的虚拟路由器 · The user does not have the permission to update external transit vRouters：用户无权限更新EXTERNALTRANSIT类型的虚拟路由器 |
|
关键字 |
IMPORT_DELETE_VROUTER_OP |
|
日志内容 |
Bulk deleted vRouters: $1. |
|
参数解释 |
$1：批量操作信息 |
|
举例 |
Bulk deleted vRouters: fileName:[虚拟路由器-2021-05-27 03-45-44.xlsx], totalNum:[40], successNum:[1], failedNum:[39]. |
|
日志说明 |
用户进行了批量删除虚拟路由器操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · Incorrect file name：文件名错误 · Failed to read the Excel file：Excel文件读取失败 · Failed to parse data：数据解析错误 · Failed to read the Excel file. Reason: The hyperlink for cell $1 references relation $2, but that didn't exist：Excel文件读取失败，原因为单元格$1的超链接引用关系$2不存在 · The file does not exist：文件不存在 · The user does not have the permission to delete transit vRouters：用户无权限删除TRANSIT类型的虚拟路由器 · The user does not have the permission to delete external transit vRouters：用户无权限删除EXTERNALTRANSIT类型的虚拟路由器 |
|
关键字 |
EXPORT_VROUTER_OP |
|
日志内容 |
Bulk exported vRouters: $1. |
|
参数解释 |
$1：批量操作信息 |
|
举例 |
Bulk exported vRouters: 虚拟路由器-2021-06-03 03-51-24.xlsx. |
|
日志说明 |
用户进行了批量导出虚拟路由器操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · Failed to export the file：Excel文件导出失败 |
|
关键字 |
IMPORT_CREATE_FLOATINGIP_OP |
|
日志内容 |
Bulk created floating IPs: $1. |
|
参数解释 |
$1：批量操作信息 |
|
举例 |
Bulk created floating IPs: fileName:[浮动Ip-2021-05-27 03-45-44.xlsx], totalNum:[40], successNum:[1], failedNum:[39]. |
|
日志说明 |
用户进行了批量创建浮动Ip操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · Incorrect file name：文件名错误 · Failed to read the Excel file：Excel文件读取失败 · Failed to parse data：数据解析错误 · Failed to read the Excel file. Reason: The hyperlink for cell $1 references relation $2, but that didn't exist：Excel文件读取失败，原因为单元格$1的超链接引用关系$2不存在 · The file does not exist：文件不存在 |
|
关键字 |
IMPORT_UPDATE_FLOATINGIP_OP |
|
日志内容 |
Bulk updated floating IPs: $1. |
|
参数解释 |
$1：批量操作信息 |
|
举例 |
Bulk updated floating IPs: fileName:[浮动Ip-2021-05-27 03-45-44.xlsx], totalNum:[40], successNum:[1], failedNum:[39]. |
|
日志说明 |
用户进行了批量更新浮动IP操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · Incorrect file name：文件名错误 · Failed to read the Excel file：Excel文件读取失败 · Failed to parse data：数据解析错误 · Failed to read the Excel file. Reason: The hyperlink for cell $1 references relation $2, but that didn't exist：Excel文件读取失败，原因为单元格$1的超链接引用关系$2不存在 · The file does not exist：文件不存在 |
|
关键字 |
IMPORT_DELETE_FLOATINGIP_OP |
|
日志内容 |
Bulk deleted floating IPs: $1. |
|
参数解释 |
$1：批量操作信息 |
|
举例 |
Bulk deleted floating IPs: fileName:[浮动Ip-2021-05-27 03-45-44.xlsx], totalNum:[40], successNum:[1], failedNum:[39]. |
|
日志说明 |
用户进行了批量删除浮动IP操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · Incorrect file name：文件名错误 · Failed to read the Excel file：Excel文件读取失败 · Failed to parse data：数据解析错误 · Failed to read the Excel file. Reason: The hyperlink for cell $1 references relation $2, but that didn't exist：Excel文件读取失败，原因为单元格$1的超链接引用关系$2不存在 · The file does not exist：文件不存在 |
|
关键字 |
EXPORT_FLOATING_IP_BULK_OP |
|
日志内容 |
Bulk exported floating IPs: $1. |
|
参数解释 |
$1：批量操作信息 |
|
举例 |
Bulk exported floating IPs: 虚拟路由器-2021-06-03 03-51-24.xlsx. |
|
日志说明 |
用户进行了批量导出浮动IP操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · Failed to export the file：Excel文件导出失败 |
|
关键字 |
IMPORT_CREATE_ROUTETABLE_OP |
|
日志内容 |
Bulk created routing tables: $1. |
|
参数解释 |
$1：批量操作信息 |
|
举例 |
Bulk created routing tables: fileName:[ Routing-Table-2021-05-27 03-45-44.xlsx], totalNum:[40], successNum:[1], failedNum:[39]. |
|
日志说明 |
用户进行了批量创建路由表操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · Incorrect file name：文件名错误 · Failed to read the file：Excel文件读取失败 · Failed to parse data：数据解析错误 · The file does not exist：文件不存在 |
|
关键字 |
IMPORT_UPDATE_ROUTETABLE_OP |
|
日志内容 |
Bulk updated routing tables: $1. |
|
参数解释 |
$1：批量操作信息 |
|
举例 |
Bulk updated routing tables: fileName:[ Routing-Table-2021-05-27 03-45-44.xlsx], totalNum:[40], successNum:[1], failedNum:[39]. |
|
日志说明 |
用户进行了批量更新路由表操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · Incorrect file name：文件名错误 · Failed to read the file：Excel文件读取失败 · Failed to parse data：数据解析错误 · The file does not exist：文件不存在 |
|
关键字 |
IMPORT_DELETE_ROUTETABLE_OP |
|
日志内容 |
Bulk deleted routing tables: $1. |
|
参数解释 |
$1：批量操作信息 |
|
举例 |
Bulk deleted routing tables: fileName:[ Routing-Table -2021-05-27 03-45-44.xlsx], totalNum:[40], successNum:[1], failedNum:[39]. |
|
日志说明 |
用户进行了批量删除路由表操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · Incorrect file name：文件名错误 · Failed to read the file：Excel文件读取失败 · Failed to parse data：数据解析错误 · The file does not exist：文件不存在 |
|
关键字 |
EXPORT_ROUTETABLE_BULK_OP |
|
日志内容 |
Bulk exported routing tables: $1. |
|
参数解释 |
$1：批量操作信息 |
|
举例 |
Bulk exported routing tables: Routing-Table-2021-06-03 03-51-24.xlsx. |
|
日志说明 |
用户进行了批量导出路由表操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · Failed to export the file：Excel文件导出失败 |
|
关键字 |
UPDATE_GLOBALCONFIG_OP |
|
日志内容 |
Updated route reduction configuration: $1 |
|
参数解释 |
$1：开启路由精简模式的场景 |
|
举例 |
Updated route reduction configuration: Layer 3 DCI |
|
日志说明 |
用户进行了修改路由精简的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · The value for the l3_dci_reduce_routes parameter is invalid：无效的数据中心三层互联路由精简参数 |
|
关键字 |
CREATE_ACL_GROUP_OP |
|
日志内容 |
Created network ACL “$1”. |
|
参数解释 |
$1：网络ACL名称 |
|
举例 |
Created network ACL “acl01”. |
|
日志说明 |
用户进行了创建网络ACL的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid request：传入的JSON串错误 · Unknown error：未知错误 · The controller is not the active leader：请在主Leader上进行操作 · Configuration recovery is in progress：配置恢复未完成 · You have no privilege to perform this operation：用户无权限执行此操作 · Duplicate network ACL IDs exist：存在重复的网络ACL ID · A network ACL with the same ID already exists：网络ACL ID已存在 · Please specify a network ACL name：网络ACL名称不能为空 · The network ACL name cannot contain more than 255 characters：网络ACL名称最长255个字符 · Invalid network ACL default action：无效的网络ACL默认动作取值 · Please specify a default action for the network ACL：网络ACL默认动作不能为空 · Please specify a tenant ID：租户ID不能为空 · Please specify a vRouter ID：虚拟路由器ID不能为空 · The vRouter ID does not exist：虚拟路由器ID不存在 · The network ACL and the vRouter must belong to the same tenant：网络ACL和虚拟路由器必须属于同一个租户 · The subnet ID does not exist：子网ID不存在 · Duplicate subnet IDs exist：存在重复的子网ID · The subnet and the network ACL must be bound to the same vRouter：子网对应的虚拟路由器和网络ACL对应的虚拟路由器必须相同 · Please bind the subnet to a vRouter：子网没有绑定虚拟路由器 · The subnet has been bound to another network ACL：子网已被其他的网络ACL绑定 · Southbound devices at the following IP addresses were disconnected: {%s}：{IP地址集合}对应的南向设备已断开连接 · Only NORMAL type virtual routers are supported：只支持NORMAL类型的虚拟路由器 · Virtual routers created by PBR are not supported：不支持PBR创建的虚拟路由器 |
|
关键字 |
UPDATE_ACL_GROUP_OP |
|
日志内容 |
Updated network ACL “$1”. |
|
参数解释 |
$1：网络ACL名称 |
|
举例 |
Updated network ACL “acl01” |
|
日志说明 |
用户进行了修改网络ACL的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid request：传入的JSON串错误 · Unknown error：未知错误 · The controller is not the active leader：请在主Leader上进行操作 · Configuration recovery is in progress：配置恢复未完成 · You have no privilege to perform this operation：用户无权限执行此操作 · The specified resource does not exist：指定的资源不存在 · Please specify a network ACL name：网络ACL名称不能为空 · The network ACL name cannot contain more than 255 characters：网络ACL名称最长255个字符 · Invalid network ACL default action：无效的网络ACL默认动作取值 · Please specify a default action for the network ACL：网络ACL默认动作不能为空 · The tenant ID cannot be edited：指定的租户ID不允许修改 · The vRouter ID cannot be edited：虚拟路由器ID不允许修改 · The subnet ID does not exist：子网ID不存在 · The subnet has been bound to another network ACL：子网已被其他的网络ACL绑定 · Please bind the subnet to a vRouter：子网没有绑定虚拟路由器 · The subnet and the network ACL must be bound to the same vRouter：子网对应的虚拟路由器和网络ACL对应的虚拟路由器必须相同 · Duplicate subnet IDs exist：存在重复的子网ID · Southbound devices at the following IP addresses were disconnected: {%s}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
DELETE_ACL_GROUP_OP |
|
日志内容 |
Deleted network ACL “$1”. |
|
参数解释 |
$1：网络ACL名称 |
|
举例 |
Deleted network ACL “acl01” |
|
日志说明 |
用户进行了删除网络ACL的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · The controller is not the active leader：请在主Leader上进行操作 · Configuration recovery is in progress：配置恢复未完成 · You have no privilege to perform this operation：用户无权限执行此操作 · The specified resource does not exist：指定的资源不存在 · Southbound devices at the following IP addresses were disconnected: {%s}：{IP地址集合}对应的南向设备已断开连接 |
|
关键字 |
CREATE_ACL_RULE_OP |
|
日志内容 |
Created network ACL rule “$1”. |
|
参数解释 |
$1：网络ACL规则名称 |
|
举例 |
Created network ACL rule “rule01”. |
|
日志说明 |
用户进行了创建网络ACL规则的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid request：传入的JSON串错误 · Unknown error：未知错误 · The controller is not the active leader：请在主Leader上进行操作 · Configuration recovery is in progress：配置恢复未完成 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {%s}：{IP地址集合}对应的南向设备已断开连接 · Duplicate rule IDs exist：存在重复的规则ID · A rule with the same ID already exists：规则ID已存在 · The rule name cannot contain more than 255 characters：规则名称最长255个字符 · Please specify a rule name：规则名称不能为空 · Please specify an action：动作不能为空 · Invalid action：无效的动作取值 · Please specify a priority：优先级不能为空 · Invalid priority：无效的优先级取值 · The rules of the same direction in the same network ACL cannot have the same priority：同一个网络ACL下同方向的规则优先级不能相同 · Please specify a direction：规则方向不能为空 · Invalid direction：无效的方向取值 · Please specify a protocol version：协议版本不能为空 · Invalid protocol version：无效的协议版本取值 · Please specify a network ACL ID：网络ACL ID不能为空 · The network ACL ID does not exist：网络ACL ID不存在 · The network ACL ID cannot be edited：网络ACL ID不允许修改 · Please specify a protocol type：协议类型不能为空 · Invalid protocol type：无效的协议类型取值 · Invalid destination IP or subnet：无效的目的IP地址或网段 · The destination IP or subnet and the protocol version do not match：目的IP地址或网段与协议版本不匹配 · Invalid source IP or subnet：无效的源IP地址或网段 · The source IP or subnet and the protocol version do not match：源IP地址或网段与协议版本不匹配 · Please specify a source IP or subnet：源IP地址或网段不能为空 · Please specify a destination IP or subnet：目的IP地址或网段不能为空 · The source port and destination port must be in the range of 0 to 65535. The port range is in the format of XX-XX, and the start port cannot be greater than the end port：源端口范围或目的端口范围为0～65535，格式为XX-XX，且起始值不能大于结束值 · The source port range cannot be configured when the protocol type is ICMP：协议类型为ICMP时，不允许配置源端口范围 · The source port range cannot be configured when the protocol type is All：协议类型为ALL时，不允许配置源端口范围 · The destination port range cannot be configured when the protocol type is ICMP：协议类型为ICMP时，不允许配置目的端口范围 · The destination port range cannot be configured when the protocol type is All：协议类型为ALL时，不允许配置目的端口范围 |
|
关键字 |
UPDATE_ACL_RULE_OP |
|
日志内容 |
Updated network ACL rule “$1”. |
|
参数解释 |
$1：网络ACL规则名称 |
|
举例 |
Updated network ACL rule “rule01”. |
|
日志说明 |
用户进行了修改网络ACL规则的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Invalid request：传入的JSON串错误 · Unknown error：未知错误 · The controller is not the active leader：请在主Leader上进行操作 · Configuration recovery is in progress：配置恢复未完成 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {%s}：{IP地址集合}对应的南向设备已断开连接 · The specified resource does not exist：指定的资源不存在 · The rule name cannot contain more than 255 characters：规则名称最长255个字符 · Please specify a rule name：规则名称不能为空 · Please specify an action：动作不能为空 · Invalid action：无效的动作取值 · Please specify a priority：优先级不能为空 · Invalid priority：无效的优先级取值 · The rules of the same direction in the same network ACL cannot have the same priority：同一个网络ACL下同方向的规则优先级不能相同 · Please specify a direction：规则方向不能为空 · The rule direction cannot be edited：规则方向不允许修改 · Invalid direction：无效的方向取值 · Please specify a protocol version：协议版本不能为空 · Invalid protocol version：无效的协议版本取值 · The protocol version cannot be edited：协议版本不允许修改 · Please specify a network ACL ID：网络ACL ID不能为空 · The network ACL ID does not exist：网络ACL ID不存在 · Please specify a protocol type：协议类型不能为空 · Invalid protocol type：无效的协议类型取值 · Invalid destination IP or subnet：无效的目的IP地址或网段 · The destination IP or subnet and the protocol version do not match：目的IP地址或网段与协议版本不匹配 · Invalid source IP or subnet：无效的源IP地址或网段 · The source IP or subnet and the protocol version do not match：源IP地址或网段与协议版本不匹配 · Please specify a source IP or subnet：源IP地址或网段不能为空 · Please specify a destination IP or subnet：目的IP地址或网段不能为空 · The source port and destination port must be in the range of 0 to 65535. The port range is in the format of XX-XX, and the start port cannot be greater than the end port：源端口范围或目的端口范围为0～65535，格式为XX-XX，且起始值不能大于结束值 · The source port range cannot be configured when the protocol type is ICMP：协议类型为ICMP时，不允许配置源端口范围 · The source port range cannot be configured when the protocol type is All：协议类型为ALL时，不允许配置源端口范围 · The destination port range cannot be configured when the protocol type is ICMP：协议类型为ICMP时，不允许配置目的端口范围 · The destination port range cannot be configured when the protocol type is All：协议类型为ALL时，不允许配置目的端口范围 |
|
关键字 |
DELETE_ACL_RULE_OP |
|
日志内容 |
Deleted network ACL rule “$1”. |
|
参数解释 |
$1：网络ACL规则名称 |
|
举例 |
Deleted network ACL rule “rule01”. |
|
日志说明 |
用户进行了删除网络ACL规则的操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · The controller is not the active leader：请在主Leader上进行操作 · Configuration recovery is in progress：配置恢复未完成 · You have no privilege to perform this operation：用户无权限执行此操作 · Southbound devices at the following IP addresses were disconnected: {%s}：{IP地址集合}对应的南向设备已断开连接 · The specified resource does not exist：指定的资源不存在 |
|
关键字 |
IMPORT_CREATE_ACL_GROUP_OP |
|
日志内容 |
Bulk created network ACL: $1. |
|
参数解释 |
$1：批量操作信息 |
|
举例 |
Bulk created network ACL: fileName: [网络ACL-2023-04-13 09-53-18.xlsx], totalNum: [1], successNum: [1], failedNum: [0]. |
|
日志说明 |
用户进行了批量创建网络ACL操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · Incorrect file name：文件名错误 · Failed to read the file：Excel文件读取失败 · Failed to parse data：数据解析错误 · The file does not exist：文件不存在 · An import or export task is in progress. Please try again later：Excel文件导入导出并发错误 |
|
关键字 |
IMPORT_UPDATE_ACL_GROUP_OP |
|
日志内容 |
Bulk updated network ACL: $1. |
|
参数解释 |
$1：批量操作信息 |
|
举例 |
Bulk updated network ACL: fileName: [网络ACL-2023-04-13 09-53-18.xlsx], totalNum: [1], successNum: [1], failedNum: [0]. |
|
日志说明 |
用户进行了批量更新网络ACL操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · Incorrect file name：文件名错误 · Failed to read the file：Excel文件读取失败 · Failed to parse data：数据解析错误 · The file does not exist：文件不存在 · An import or export task is in progress. Please try again later：Excel文件导入导出并发错误 |
|
关键字 |
IMPORT_DELETE_ACL_GROUP_OP |
|
日志内容 |
Bulk deleted network ACL: $1. |
|
参数解释 |
$1：批量操作信息 |
|
举例 |
Bulk deleted network ACL: fileName: [网络ACL-2023-04-13 09-53-18.xlsx], totalNum: [1], successNum: [1], failedNum: [0]. |
|
日志说明 |
用户进行了批量删除网络ACL操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · Incorrect file name：文件名错误 · Failed to read the file：Excel文件读取失败 · Failed to parse data：数据解析错误 · The file does not exist：文件不存在 · An import or export task is in progress. Please try again later：Excel文件导入导出并发错误 |
|
关键字 |
EXPORT_ACL_GROUP_BULK_OP |
|
日志内容 |
Bulk exported network ACL: $1. |
|
参数解释 |
$1：批量操作信息 |
|
举例 |
Bulk exported network ACL: 网络ACL-2023-04-13 09-53-18.xlsx. |
|
日志说明 |
用户进行了批量导出网络ACL操作 |
|
失败原因 |
当操作失败时，可能的原因如下： · Unknown error：未知错误 · Failed to export the file：Excel文件导出失败 · An import or export task is in progress. Please try again later：Excel文件导入导出并发错误 |
支持
