手册下载
系统日志信息参考
资料版本：5W103-20220428
Copyright © 2022 新华三技术有限公司 版权所有，保留一切权利。
非经本公司书面许可，任何单位和个人不得擅自摘抄、复制本文档内容的部分或全部，并不得以任何形式传播。
除新华三技术有限公司的商标外，本手册中出现的其它公司的商标、产品标识及商品名称，由各自权利人拥有。
本文档中的信息可能变动，恕不另行通知。
目 录
10.1 控制器为指定站点新增Transit Router成功
10.2 控制器为指定站点新增Transit Router失败
10.3 控制器为指定站点删除Transit Router成功
10.4 控制器为指定站点删除Transit Router失败
10.5 Transit Router增加配置失败后，配置回退成功
10.6 Transit Router删除配置失败后，配置回退成功
10.7 Transit Router增加配置失败后，配置回退失败
10.8 Transit Router删除配置失败后，配置回退失败
系统日志用于通知用户控制器运行的内部事件。系统日志信息包含日志的参数介绍、产生原因、处理建议等，为用户进行系统诊断和维护提供参考。
本文假设您已具备数据通信技术知识，并熟悉H3C Super 控制器产品。
单击[系统/日志管理/系统日志列表]菜单项，进入系统日志视图。系统日志信息列表将分页显示控制器产生的系统日志信息，如图1-1所示。
表1-1 日志字段说明
|
字段 |
描述 |
|
级别 |
日志信息的严重等级 系统日志信息具有五种级别，用不同的图标表示，具体说明请参见表1-5 |
|
日期/时间 |
生成系统日志信息的日期和时间 |
|
组件名称 |
生成系统日志的容器名称 |
|
节点名称 |
生成系统日志的节点名称 |
|
服务名称 |
生成系统日志的服务名称 |
|
模块名称 |
生成系统日志信息的业务模块名称，具体介绍请参见表1-3 |
|
描述信息 |
系统日志具体内容，包含事件或错误发生的详细信息 |
Super Controller支持将系统日志通过Syslog协议发送至Syslog日志服务器。Syslog日志服务器的IP地址和端口号可以通过[系统/设置/日志设置]页面中的系统日志页面进行设置。
缺省情况下，控制器以Syslog协议发送的系统日志信息格式如下：
<PRI>TIMESTAMP Hostname Service/severity/Keywords CONTENT
表1-2 Syslog日志字段说明
|
字段 |
描述 |
|
<PRI> |
优先级标识符，优先级的计算公式为：facility×8＋severity · facility表示Syslog定义的程序模块，目前Super Controller发送Syslog日志的facility一般为user-level，取值为1 · severity表示Syslog协议定义的日志严重等级，具体说明请参见表1-4 |
|
TIMESTAMP |
时间戳记录了日志信息产生的时间，方便用户查看和定位系统事件 |
|
Hostname |
生成该日志信息的容器的名称 |
|
Service |
生成该系统日志信息的微服务的名称，具体介绍请参见表1-3 |
|
severity |
Super Controller定义的系统日志信息的等级，具体说明请参见表1-5，使用了Syslog协议定义的5个日志严重等级 |
|
Keywords |
关键字，本字段为该日志信息的概述，用于搜索或助记 |
|
CONTENT |
该日志的具体内容，包含事件或错误发生的详细信息 |
表1-3列出了可能生成系统日志信息的业务模块。
|
说明 |
|
|
EBGP_CONNECTION |
EBGP邻居管理模块 |
|
LICENSE |
License管理模块 |
|
NETWORK |
虚拟链路层网络管理模块 |
|
ROUTER |
虚拟路由器管理模块 |
|
SUBNET |
虚拟子网管理模块 |
|
TENANT |
租户管理模块 |
|
TRANSIT_ROUTER |
Transit Router管理模块 |
|
VPC_CONNECT |
VPC连接管理模块 |
Syslog协议定义的日志严重等级如表1-4所示，各等级的严重性依照数值从0～7依次降低。
表1-4 Syslog日志严重等级说明
|
级别 |
严重等级 |
描述 |
|
0 |
Emergency |
表示致命信息，可能导致系统不可用 |
|
1 |
Alert |
表示必须立即修复的状态 |
|
2 |
Critical |
表示严重信息 |
|
3 |
Error |
表示错误信息 |
|
4 |
Warning |
表示警告信息 |
|
5 |
Notice |
表示正常出现但是重要的信息 |
|
6 |
Informational |
表示需要记录的通知信息 |
|
7 |
Debug |
表示调试过程产生的信息 |
Super Controller使用了Syslog协议定义的5个日志严重等级，如表1-5所示。
|
级别 |
图标 |
严重等级 |
描述 |
|
6 |
|
Informational |
表示需要记录的通知信息 |
|
4 |
|
Warning |
表示警告信息 |
|
3 |
|
Error |
表示错误信息 |
|
2 |
|
Critical |
表示严重信息 |
|
0 |
|
Emergency |
表示致命信息，可能导致系统不可用 |
本文将系统日志信息按照业务模块分类，以表格的形式对日志信息进行介绍。有关表中各项的含义请参考表1-6。
|
表项 |
说明 |
举例 |
|
关键字 |
日志信息的概述，用于搜索或助记 |
LICENSE_INSTALL |
|
日志内容 |
显示日志信息的具体内容 |
$1 license successfully installed. |
|
参数解释 |
按照参数在日志中出现的顺序对参数进行解释 参数顺序用“$数字”表示，例如“$1”表示在该日志中出现的第一个参数 |
$1：License名称 |
|
日志等级 |
日志严重等级 |
|
|
举例 |
日志信息举例 |
Base license successfully installed. |
|
日志说明 |
解释日志信息和日志生成的原因 |
指定的License已成功安装 |
|
处理建议 |
建议用户应采取哪些处理措施 |
系统正常运行时产生的信息，无需处理 |
本节介绍Super Controller对站点进行差异发现或差异修复时输出的日志信息。
|
关键字 |
DATA_CONSISTENCY_AUDIT_FALIED |
|
日志内容 |
Failed to audit differences for site $1. Reason: $2. |
|
参数解释 |
$1：站点名称 $2：失败原因 |
|
日志等级 |
Warning |
|
举例 |
Failed to audit differences for site dc1. Reason: The connection state of the site is abnormal. |
|
日志说明 |
控制器对站点执行差异发现失败 |
|
处理建议 |
· 检查Super Controller与站点之间网络是否可达 · 检查站点状态是否正常 |
|
关键字 |
DATA_CONSISTENCY_SMOOTH_FALIED |
|
日志内容 |
Failed to repair configuration for site $1. Reason: $2. |
|
参数解释 |
$1：站点名称 $2：失败原因 |
|
日志等级 |
Warning |
|
举例 |
Failed to repair configuration for site dc1. Reason: The connection state of the site is abnormal. |
|
日志说明 |
控制器对站点执行差异修复失败 |
|
处理建议 |
· 检查Super Controller与站点之间网络是否可达 · 检查站点状态是否正常 |
本节介绍在Super Controller上对Transit Fabric进行EBGP邻居关系下发时EBGP_CONNECTION模块输出的日志信息。
|
关键字 |
EBGP_CONNECTION_ADD_SUCCESSED |
|
日志内容 |
Successfully added an EBGP connection configuration in site "$1". The EBGP connection information is as follows: $2 |
|
参数解释 |
$1：站点名称 $2：EBGP邻居关系信息 |
|
日志等级 |
|
|
举例 |
Successfully added an EBGP connection configuration in site "192.168.31.150". The EBGP connection information is as follows: {id='4618b843-1099-4243-97ce-fb2b3706fe98'name='null', transitSiteId=9029f283-39ed-4b4e-9db0-4f2b42c74dd9, localDeviceId=1872f0ab-8229-4434-804d-ce34790f6f2f, localConnectionId='null', peerDeviceId=f873a1af-8bf0-49fd-a7fa-efa9358cb83a, peerConnectionId='null'} |
|
日志说明 |
用户在Super Controller上为指定站点新增EBGP邻居关系成功 |
|
处理建议 |
系统正常运行时产生的信息，无需处理 |
|
关键字 |
EBGP_CONNECTION_ADD_FAILED |
|
日志内容 |
Failed to add an EBGP connection configuration in site "$1". Reason: $2.The EBGP connection information is as follows: $3 |
|
参数解释 |
$1：站点名称 $2：新增失败的异常原因 $3：EBGP邻居关系信息 |
|
日志等级 |
|
|
举例 |
Failed to add an EBGP connection configuration in site "192.168.31.180". Reason: A DC connection already exists between the local and remote devices. The EBGP connection information is as follows: {id='4618b843-1099-4243-97ce-fb2b3706fe98'name='null', transitSiteId=9029f283-39ed-4b4e-9db0-4f2b42c74dd9, localDeviceId=1872f0ab-8229-4434-804d-ce34790f6f2f, localConnectionId='4618b843-1099-4243-97ce-fb2b3706fe98', peerDeviceId=f873a1af-8bf0-49fd-a7fa-efa9358cb83a, peerConnectionId='null'} |
|
日志说明 |
用户在Super Controller上为指定站点新增EBGP邻居关系失败 |
|
处理建议 |
请根据异常提示处理异常 |
|
关键字 |
EBGP_CONNECTION_DELETE_SUCCESSED |
|
日志内容 |
Successfully deleted an EBGP connection configuration in site "$1". The EBGP connection information is as follows: $2 |
|
参数解释 |
$1：站点名称 $2：EBGP邻居关系信息 |
|
日志等级 |
|
|
举例 |
Successfully deleted an EBGP connection configuration in site "192.168.31.150". The EBGP connection information is as follows: {id='4618b843-1099-4243-97ce-fb2b3706fe98'name='null', transitSiteId=9029f283-39ed-4b4e-9db0-4f2b42c74dd9, localDeviceId=1872f0ab-8229-4434-804d-ce34790f6f2f, localConnectionId='4618b843-1099-4243-97ce-fb2b3706fe98', peerDeviceId=f873a1af-8bf0-49fd-a7fa-efa9358cb83a, peerConnectionId='null'} |
|
日志说明 |
用户在Super Controller上通过业务发放功能删除指定站点的EBGP邻居关系成功 |
|
处理建议 |
系统正常运行时产生的信息，无需处理 |
|
关键字 |
EBGP_CONNECTION_DELETE_FAILED |
|
日志内容 |
Failed to delete an EBGP connection configuration in site "$1". Reason: $2.The EBGP connection information is as follows: $3 |
|
参数解释 |
$1：站点名称 $2：删除失败的异常原因 $3：EBGP邻居关系信息 |
|
日志等级 |
|
|
举例 |
Failed to delete an EBGP connection configuration in site "192.168.31.180". Reason: Cannot reach site 192.168.31.180. The EBGP connection information is as follows: {id='4618b843-1099-4243-97ce-fb2b3706fe98'name='null', transitSiteId=9029f283-39ed-4b4e-9db0-4f2b42c74dd9, localDeviceId=1872f0ab-8229-4434-804d-ce34790f6f2f, localConnectionId='4618b843-1099-4243-97ce-fb2b3706fe98', peerDeviceId=f873a1af-8bf0-49fd-a7fa-efa9358cb83a, peerConnectionId='null'} |
|
日志说明 |
用户在Super Controller上通过业务发放功能删除指定站点的EBGP邻居关系失败 |
|
处理建议 |
请根据异常提示处理异常 |
|
关键字 |
ROLLBACK_EBGP_CONNECTION_ADD_SUCCESSED |
|
日志内容 |
Successfully rolled back the EBGP connection deleting configuration for site "$1". The EBGP connection information is as follows: $2 |
|
参数解释 |
$1：站点名称 $2：EBGP邻居关系的配置信息 |
|
日志等级 |
|
|
举例 |
Successfully rolled back the EBGP connection deleting configuration for site "192.168.31.150". The EBGP connection information is as follows: {id='4618b843-1099-4243-97ce-fb2b3706fe98'name='null', transitSiteId=9029f283-39ed-4b4e-9db0-4f2b42c74dd9, localDeviceId=1872f0ab-8229-4434-804d-ce34790f6f2f, localConnectionId='null', peerDeviceId=f873a1af-8bf0-49fd-a7fa-efa9358cb83a, peerConnectionId='null'} |
|
日志说明 |
用户在Super Controller上为指定站点新增EBGP邻居关系配置失败后，回退配置成功 |
|
处理建议 |
系统正常运行时产生的信息，无需处理 |
|
关键字 |
ROLLBACK_EBGP_CONNECTION_ADD_FAILED |
|
日志内容 |
Failed to roll back the EBGP connection deleting configuration for site "$1". Reason: $2. The EBGP connection information is as follows: $3 |
|
参数解释 |
$1：站点名称 $2：回退失败的异常原因 $3：EBGP邻居关系的配置信息 |
|
日志等级 |
|
|
举例 |
Failed to roll back the EBGP connection deleting configuration for site "192.168.31.180". Reason: Cannot reach site 192.168.31.180. The EBGP connection information is as follows: {id='4618b843-1099-4243-97ce-fb2b3706fe98'name='null', transitSiteId=9029f283-39ed-4b4e-9db0-4f2b42c74dd9, localDeviceId=1872f0ab-8229-4434-804d-ce34790f6f2f, localConnectionId='4618b843-1099-4243-97ce-fb2b3706fe98', peerDeviceId=f873a1af-8bf0-49fd-a7fa-efa9358cb83a, peerConnectionId='null'} |
|
日志说明 |
用户在Super Controller上为指定站点新增EBGP邻居关系配置失败后，回退配置失败 |
|
处理建议 |
请根据异常提示处理异常 |
本节介绍License管理模块输出的日志信息。
|
关键字 |
LICENSE_INSUFFICIENT |
|
日志内容 |
Insufficient $1 licenses. Please purchase more licenses. |
|
参数解释 |
$1：数量型License名称 |
|
日志等级 |
|
|
举例 |
Insufficient MaxNodeNum licenses. Please purchase more licenses. |
|
日志说明 |
数量型License的数量不足，请及时购买 |
|
处理建议 |
请及时购买License |
本节介绍Super Controller通过纳管或反向纳管功能管理站点控制器时虚拟链路层网络模块输出的日志信息。
|
关键字 |
NETWORK_ADD_SUCCESSED |
|
日志内容 |
Successfully added a network configuration in site ”$1”. The network configuration information is as follows: $2 |
|
参数解释 |
$1：站点名称 $2：虚拟链路层网络信息 |
|
日志等级 |
|
|
举例 |
Successfully added a network configuration in site ”site1”. The network configuration information is as follows: [ID=6cfc7b92-5d2f-d81d-28de-26a3bee73d93, Name=test22, Description=, Segment ID=98, Type=VXLAN, External network=false] |
|
日志说明 |
用户在Super Controller上通过纳管功能为指定站点新增虚拟链路层网络成功 |
|
处理建议 |
系统正常运行时产生的信息，无需处理 |
|
关键字 |
NETWORK_ADD_FAILED |
|
日志内容 |
Failed to add a network configuration in site ”$1”. Reason: $2. The network configuration information is as follows: $3 |
|
参数解释 |
$1：站点名称 $2：新增失败的异常提示 $3：虚拟链路层网络信息 |
|
日志等级 |
|
|
举例 |
Failed to add a network configuration in site ”site1”. Reason: Cannot reach the site. The network configuration information is as follows: [ID=6cfc7b92-5d2f-d81d-28de-26a3bee73d93, Name=test22, Description=, Segment ID=98, Type=VXLAN, External network=false] |
|
日志说明 |
用户在Super Controller上通过纳管功能为指定站点新增虚拟链路层网络失败 |
|
处理建议 |
请根据异常提示处理异常 |
|
关键字 |
NETWORK_UPDATE_SUCCESSED |
|
日志内容 |
Successfully updated a network configuration in site ”$1”. The network configuration information is as follows: $2 |
|
参数解释 |
$1：站点名称 $2：虚拟链路层网络信息 |
|
日志等级 |
|
|
举例 |
Successfully updated a network configuration in site ”site1”. The network configuration information is as follows: [ID=6cfc7b92-5d2f-d81d-28de-26a3bee73d93, Name=test22, Description=, Segment ID=98, Type=VXLAN, External network=false] |
|
日志说明 |
用户在Super Controller上通过纳管功能更新指定站点的虚拟链路层网络成功 |
|
处理建议 |
系统正常运行时产生的信息，无需处理 |
|
关键字 |
NETWORK_UPDATE_FAILED |
|
日志内容 |
Failed to update a network configuration in site ”$1”. Reason: $2. The network configuration information is as follows: $3 |
|
参数解释 |
$1：站点名称 $2：更新失败的异常提示 $3：虚拟链路层网络信息 |
|
日志等级 |
|
|
举例 |
Failed to update a network configuration in site ”site1”. Reason: Cannot reach the site. The network configuration information is as follows: [ID=6cfc7b92-5d2f-d81d-28de-26a3bee73d93, Name=test22, Description=, Segment ID=98 , Type=VXLAN, External network=false] |
|
日志说明 |
用户在Super Controller上通过纳管功能更新指定站点的虚拟链路层网络失败 |
|
处理建议 |
请根据异常提示处理异常 |
|
关键字 |
NETWORK_DELETE_SUCCESSED |
|
日志内容 |
Successfully deleted a network configuration in site ”$1”. The network configuration information is as follows: $2 |
|
参数解释 |
$1：站点名称 $2：虚拟链路层网络信息 |
|
日志等级 |
|
|
举例 |
Successfully deleted a network configuration in site ”site1”. The network configuration information is as follows: [ID=6cfc7b92-5d2f-d81d-28de-26a3bee73d93, Name=test22, Description=, Segment ID=98, Type=VXLAN, External network=false] |
|
日志说明 |
用户在Super Controller上通过纳管功能删除指定站点的虚拟链路层网络成功 |
|
处理建议 |
系统正常运行时产生的信息，无需处理 |
|
关键字 |
NETWORK_DELETE_FAILED |
|
日志内容 |
Failed to delete a network configuration in site ”$1”. Reason: $2. The network configuration information is as follows: $3 |
|
参数解释 |
$1：站点名称 $2：删除失败的异常提示 $3：虚拟链路层网络信息 |
|
日志等级 |
|
|
举例 |
Failed to delete a network configuration in site ”site1”. Reason: Cannot reach the site. The network configuration information is as follows: [ID=6cfc7b92-5d2f-d81d-28de-26a3bee73d93, Name=test22, Description=, Segment ID=98, Type=VXLAN, External network=false] |
|
日志说明 |
用户在Super Controller上通过纳管功能删除指定站点的虚拟链路层网络失败 |
|
处理建议 |
请根据异常提示处理异常 |
|
关键字 |
CONTROLLED_SITE |
|
日志内容 |
Failed to synchronize settings from site ”$1”. Settings failed to be synchronized: $2 |
|
参数解释 |
$1：站点名称 $2：虚拟链路层网络的配置信息 |
|
举例 |
Failed to synchronize settings from site ”site1”. Settings failed to be synchronized: [ID=d27f6f5e-63c4-4d39-b154-1b8190159067, Name=OutUss1912C01, Description=The vNetwork information was synchronized from a site, Segment ID=1912, Type=VXLAN, External network=false] |
|
日志说明 |
用户在Super Controller上通过反向纳管功能管理站点控制器时，由于虚拟链路层网络的配置同步失败，导致反向纳管操作失败 |
|
处理建议 |
请查看操作日志信息，根据操作日志的失败原因做相应处理 |
|
关键字 |
ROLLBACK_NETWORK_ADD_SUCCESSED |
|
日志内容 |
Successfully rolled back the network adding configuration for site "$1". The network information is as follows: $2. |
|
参数解释 |
$1：站点名称 $2：虚拟链路层网络的配置信息 |
|
日志等级 |
|
|
举例 |
Successfully rolled back the network adding configuration for site "site1". The network information is as follows: [ID=6cfc7b92-5d2f-d81d-28de-26a3bee73d93, Name=test22, Description=, Segment ID=98, Type=VXLAN, External network=false] |
|
日志说明 |
向站点下发虚拟链路层网络的增加配置失败后，回退配置成功 |
|
处理建议 |
无需处理 |
|
关键字 |
ROLLBACK_NETWORK_UPDATE_SUCCESSED |
|
日志内容 |
Successfully rolled back the network updating configuration for site "$1". The network information is as follows: $2. |
|
参数解释 |
$1：站点名称 $2：虚拟链路层网络的配置信息 |
|
日志等级 |
|
|
举例 |
Successfully rolled back the network updating configuration for site "site1". The network information is as follows: [ID=6cfc7b92-5d2f-d81d-28de-26a3bee73d93, Name=test22, Description=, Segment ID=98, Type=VXLAN, External network=false] |
|
日志说明 |
向站点下发虚拟链路层网络的修改配置失败后，回退配置成功 |
|
处理建议 |
无需处理 |
|
关键字 |
ROLLBACK_NETWORK_DELETE_SUCCESSED |
|
日志内容 |
Successfully rolled back the network deleting configuration for site "$1". The network information is as follows: $2. |
|
参数解释 |
$1：站点名称 $2：虚拟链路层网络的配置信息 |
|
日志等级 |
|
|
举例 |
Successfully rolled back the network deleting configuration for site "site1". The network information is as follows: [ID=6cfc7b92-5d2f-d81d-28de-26a3bee73d93, Name=test22, Description=, Segment ID=98, Type=VXLAN, External network=false] |
|
日志说明 |
向站点下发虚拟链路层网络的删除配置失败后，回退配置成功 |
|
处理建议 |
无需处理 |
|
关键字 |
ROLLBACK_NETWORK_ADD_FAILED |
|
日志内容 |
Failed to roll back the network adding configuration for site "$1". Reason: $2. The network information is as follows: $3. |
|
参数解释 |
$1：站点名称 $2：失败的异常提示 $3：虚拟链路层网络的配置信息 |
|
日志等级 |
|
|
举例 |
Failed to roll back the network adding configuration for site "site1". Reason: Cannot reach the site. The network information is as follows: [ID=6cfc7b92-5d2f-d81d-28de-26a3bee73d93, Name=test22, Description=, Segment ID=98, Type=VXLAN, External network=false] |
|
日志说明 |
向站点下发虚拟链路层网络的增加配置失败后，回退配置失败 |
|
处理建议 |
建议在站点上手动清除残留配置 |
|
关键字 |
ROLLBACK_NETWORK_UPDATE_FAILED |
|
日志内容 |
Failed to roll back the network updating configuration for site "$1". Reason: $2. The network information is as follows: $3. |
|
参数解释 |
$1：站点名称 $2：失败的异常提示 $3：虚拟链路层网络的配置信息 |
|
日志等级 |
|
|
举例 |
Failed to roll back the network updating configuration for site "site1". Reason: Cannot reach the site. The network information is as follows: [ID=6cfc7b92-5d2f-d81d-28de-26a3bee73d93, Name=test22, Description=, Segment ID=98, Type=VXLAN, External network=false] |
|
日志说明 |
向站点下发虚拟链路层网络的修改配置失败后，回退配置失败 |
|
处理建议 |
建议在站点上手动清除残留配置 |
|
关键字 |
ROLLBACK_NETWORK_DELETE_FAILED |
|
日志内容 |
Failed to roll back the network deleting configuration for site "$1". Reason: $2. The network information is as follows: $3. |
|
参数解释 |
$1：站点名称 $2：失败的异常提示 $3：虚拟链路层网络的配置信息 |
|
日志等级 |
|
|
举例 |
Failed to roll back the network deleting configuration for site "site1". Reason: Cannot reach the site. The network information is as follows: [ID=6cfc7b92-5d2f-d81d-28de-26a3bee73d93, Name=test22, Description=, Segment ID=98, Type=VXLAN, External network=false] |
|
日志说明 |
向站点下发虚拟链路层网络的删除配置失败后，回退配置失败 |
|
处理建议 |
建议在站点上手动清除残留配置 |
本节介绍Super Controller对接公有云管理和编排功能模块输出的日志信息。
|
关键字 |
ADD_VPC_OP |
|
日志内容 |
Created VPC $1 in the public cloud successfully. |
|
参数解释 |
$1：VPC名称 |
|
日志等级 |
|
|
举例 |
Created VPC vpc001 in the public cloud successfully. |
|
日志说明 |
用户在Super Controller上通过公有云管理向亚马逊云创建VPC成功 |
|
处理建议 |
系统正常运行时产生的信息，无需处理 |
|
关键字 |
ADD_VPC_OP |
|
日志内容 |
Failed to create VPC $1 in the public cloud. Reason: $2 |
|
参数解释 |
$1：VPC名称 $2：失败的异常提示 |
|
日志等级 |
|
|
举例 |
Failed to create VPC vpc001 in the public cloud. Reason: Failed to request data from Amazon Web Services. |
|
日志说明 |
用户在Super Controller上通过公有云管理向亚马逊云创建VPC失败 |
|
处理建议 |
请根据异常提示处理异常 |
|
关键字 |
UPDATE_VPC_OP |
|
日志内容 |
Updated VPC $1 in the public cloud successfully. |
|
参数解释 |
$1：VPC名称 |
|
日志等级 |
|
|
举例 |
Updated VPC vpc001 in the public cloud successfully. |
|
日志说明 |
用户在Super Controller上通过公有云管理向亚马逊云更新VPC成功 |
|
处理建议 |
系统正常运行时产生的信息，无需处理 |
|
关键字 |
UPDATE_VPC_OP |
|
日志内容 |
Failed to update VPC $1 in the public cloud. Reason:$2 |
|
参数解释 |
$1：VPC名称 $2：失败的异常提示 |
|
日志等级 |
|
|
举例 |
Failed to update VPC vpc001 in the public cloud. Reason: Failed to request data from Amazon Web Services. |
|
日志说明 |
用户在Super Controller上通过公有云管理向亚马逊云更新VPC失败 |
|
处理建议 |
请根据异常提示处理异常 |
|
关键字 |
DEL_VPC_OP |
|
日志内容 |
Deleted VPC $1 from the public cloud successfully. |
|
参数解释 |
$1：VPC名称 |
|
日志等级 |
|
|
举例 |
Deleted VPC vpc001 from the public cloud successfully. |
|
日志说明 |
用户在Super Controller上通过公有云管理向亚马逊云删除VPC成功 |
|
处理建议 |
系统正常运行时产生的信息，无需处理 |
|
关键字 |
DEL_VPC_OP |
|
日志内容 |
Failed to delete VPC $1 from the public cloud. Reason: $2 |
|
参数解释 |
$1：VPC名称 $2：失败的异常提示 |
|
日志等级 |
|
|
举例 |
Failed to delete VPC vpc001 from the public cloud. Reason: Failed to request data from Amazon Web Services. |
|
日志说明 |
用户在Super Controller上通过公有云管理向亚马逊云删除VPC失败 |
|
处理建议 |
请根据异常提示处理异常 |
|
关键字 |
QUERY_VPC_OP |
|
日志内容 |
Queried VPC $1 from the public cloud successfully. |
|
参数解释 |
$1：VPC名称 |
|
日志等级 |
|
|
举例 |
Queried VPCs from the public cloud successfully. |
|
日志说明 |
用户在Super Controller上通过公有云管理向亚马逊云查询VPC成功 |
|
处理建议 |
系统正常运行时产生的信息，无需处理 |
|
关键字 |
QUERY_VPC_OP |
|
日志内容 |
Failed to query VPC $1 from the public cloud. Reason: $2 |
|
参数解释 |
$1：VPC名称 $2：失败的异常提示 |
|
日志等级 |
|
|
举例 |
Failed to query VPC vpc001 from the public cloud. Reason: Failed to request data from Amazon Web Services. |
|
日志说明 |
用户在Super Controller上通过公有云管理向亚马逊云删除VPC失败 |
|
处理建议 |
请根据异常提示处理异常 |
|
关键字 |
ADD_VPC_CIDR_OP |
|
日志内容 |
Created IPv4 CIDR $1 in VPC $2 successfully. |
|
参数解释 |
$1：IPv4 CIDR名称 $2：VPC名称 |
|
日志等级 |
|
|
举例 |
Created IPv4 CIDR 10.10.10.0/24 in VPC vpc001 successfully. |
|
日志说明 |
用户在Super Controller上通过公有云管理向亚马逊云创建VPC网段成功 |
|
处理建议 |
系统正常运行时产生的信息，无需处理 |
|
关键字 |
ADD_VPC_CIDR_OP |
|
日志内容 |
Failed to create IPv4 CIDR $1 in VPC $2. Reason: $3 |
|
参数解释 |
$1：IPv4 CIDR名称 $2：VPC名称 $3：失败的异常提示 |
|
日志等级 |
|
|
举例 |
Failed to create IPv4 CIDR 10.10.10.0/24 in VPC vpc001. Reason: Failed to request data from Amazon Web Services. |
|
日志说明 |
用户在Super Controller上通过公有云管理向亚马逊云创建VPC网段失败 |
|
处理建议 |
请根据异常提示处理异常 |
|
关键字 |
ADD_VPC_CIDR_OP |
|
日志内容 |
Created IPv6 CIDR $1 in VPC $2 successfully. |
|
参数解释 |
$1：IPv6 CIDR名称 $2：VPC名称 |
|
日志等级 |
|
|
举例 |
Created IPv6 CIDR 1001::1000/64 in VPC vpc001 successfully. |
|
日志说明 |
用户在Super Controller上通过公有云管理向亚马逊云创建VPC网段成功 |
|
处理建议 |
系统正常运行时产生的信息，无需处理 |
|
关键字 |
ADD_VPC_CIDR_OP |
|
日志内容 |
Failed to create IPv6 CIDR $1 in VPC $2. Reason: $3 |
|
参数解释 |
$1：IPv6 CIDR名称 $2：VPC名称 $3：失败的异常提示 |
|
日志等级 |
|
|
举例 |
Failed to create IPv6 CIDR 1001::1000/64 in VPC vpc001. Reason: Failed to request data from Amazon Web Services. |
|
日志说明 |
用户在Super Controller上通过公有云管理向亚马逊云创建VPC网段失败 |
|
处理建议 |
请根据异常提示处理异常 |
|
关键字 |
DEL_VPC_CIDR_OP |
|
日志内容 |
Deleted IPv4 CIDR $1 from VPC $2 successfully. |
|
参数解释 |
$1：IPv4 CIDR名称 $2：VPC名称 |
|
日志等级 |
|
|
举例 |
Deleted IPv4 CIDR 10.10.10.0/24 from VPC vpc001 successfully. |
|
日志说明 |
用户在Super Controller上通过公有云管理向亚马逊云删除VPC网段成功 |
|
处理建议 |
系统正常运行时产生的信息，无需处理 |
|
关键字 |
DEL_VPC_CIDR_OP |
|
日志内容 |
Failed to delete IPv4 CIDR $1 from VPC $2. Reason: $3 |
|
参数解释 |
$1：IPv4 CIDR名称 $2：VPC名称 $3：失败的异常提示 |
|
日志等级 |
|
|
举例 |
Failed to delete IPv4 CIDR 10.10.10.0/24 from VPC vpc001. Reason: Failed to request data from Amazon Web Services. |
|
日志说明 |
用户在Super Controller上通过公有云管理向亚马逊云删除VPC网段失败 |
|
处理建议 |
请根据异常提示处理异常 |
|
关键字 |
DEL_VPC_CIDR_OP |
|
日志内容 |
Deleted IPv6 CIDR $1 from VPC $2 successfully. |
|
参数解释 |
$1：IPv6 CIDR名称 $2：VPC名称 |
|
日志等级 |
|
|
举例 |
Deleted IPv6 CIDR 1001::1000/64 from VPC vpc001 successfully. |
|
日志说明 |
用户在Super Controller上通过公有云管理向亚马逊云删除VPC网段成功 |
|
处理建议 |
系统正常运行时产生的信息，无需处理 |
|
关键字 |
DEL_VPC_CIDR_OP |
|
日志内容 |
Failed to delete IPv6 CIDR $1 from VPC $2. Reason: $3 |
|
参数解释 |
$1：IPv6 CIDR名称 $2：VPC名称 $3：失败的异常提示 |
|
日志等级 |
|
|
举例 |
Failed to delete IPv6 CIDR 1001::1000/64 from VPC vpc001. Reason: Failed to request data from Amazon Web Services. |
|
日志说明 |
用户在Super Controller上通过公有云管理向亚马逊云删除VPC网段失败 |
|
处理建议 |
请根据异常提示处理异常 |
|
关键字 |
QUERY_REGION_OP |
|
日志内容 |
Queried regions from the public cloud successfully. |
|
参数解释 |
无 |
|
日志等级 |
|
|
举例 |
Queried regions from the public cloud successfully. |
|
日志说明 |
用户在Super Controller上通过公有云管理向亚马逊云查询Region成功 |
|
处理建议 |
系统正常运行时产生的信息，无需处理 |
|
关键字 |
QUERY_REGION_OP |
|
日志内容 |
Failed to query regions from the public cloud. Reason: $1 |
|
参数解释 |
$1：失败的异常提示 |
|
日志等级 |
|
|
举例 |
Failed to query regions from the public cloud. Reason: Failed to request data from Amazon Web Services. |
|
日志说明 |
用户在Super Controller上通过公有云管理向亚马逊云查询Region失败 |
|
处理建议 |
请根据异常提示处理异常 |
|
关键字 |
QUERY_AZ_OP |
|
日志内容 |
Queried AZs from the public cloud successfully. |
|
参数解释 |
无 |
|
日志等级 |
|
|
举例 |
Queried AZs from the public cloud successfully. |
|
日志说明 |
用户在Super Controller上通过公有云管理向亚马逊云查询AZ成功 |
|
处理建议 |
系统正常运行时产生的信息，无需处理 |
|
关键字 |
QUERY_AZ_OP |
|
日志内容 |
Failed to query AZs from the public cloud. Reason: $1 |
|
参数解释 |
$1：失败的异常提示 |
|
日志等级 |
|
|
举例 |
Failed to query AZs from the public cloud. Reason: Failed to request data from Amazon Web Services. |
|
日志说明 |
用户在Super Controller上通过公有云管理向亚马逊云查询AZ失败 |
|
处理建议 |
请根据异常提示处理异常 |
|
关键字 |
CHECK_ACCOUNT_OP |
|
日志内容 |
Got access keys of account $1 from the public cloud successfully. |
|
参数解释 |
$1：认证账户信息 |
|
日志等级 |
|
|
举例 |
Got access keys of account [email protected] from the public cloud successfully. |
|
日志说明 |
用户在Super Controller上通过公有云管理向亚马逊云查询认证成功 |
|
处理建议 |
系统正常运行时产生的信息，无需处理 |
|
关键字 |
CHECK_ACCOUNT_OP |
|
日志内容 |
Failed to get access keys of account $1 from the public cloud. Reason: $2 |
|
参数解释 |
$1：认证账户信息 $2：失败的异常提示 |
|
日志等级 |
|
|
举例 |
Failed to get access keys of account [email protected] from the public cloud. Reason: Failed to request data from Amazon Web Services. |
|
日志说明 |
用户在Super Controller上通过公有云管理向亚马逊云查询认证失败 |
|
处理建议 |
请根据异常提示处理异常 |
|
关键字 |
CHECK_ACCOUNT_OP |
|
日志内容 |
Got users of account $1 from the public cloud successfully. |
|
参数解释 |
$1：账户下用户信息 |
|
日志等级 |
|
|
举例 |
Got users of account [email protected] from the public cloud successfully. |
|
日志说明 |
用户在Super Controller上通过公有云管理向亚马逊云查询账户下用户信息 |
|
处理建议 |
系统正常运行时产生的信息，无需处理 |
|
关键字 |
CHECK_ACCOUNT_OP |
|
日志内容 |
Failed to get users of account $1 from the public cloud. Reason: $2 |
|
参数解释 |
$1：账户下用户信息 $2：失败的异常提示 |
|
日志等级 |
|
|
举例 |
Failed to get users of account [email protected] from the public cloud. Reason: Failed to request data from Amazon Web Services. |
|
日志说明 |
用户在Super Controller上通过公有云管理向亚马逊云查询账户下用户信息失败 |
|
处理建议 |
请根据异常提示处理异常 |
|
关键字 |
AUTH_ACCOUNT_OP |
|
日志内容 |
Failed to authenticate the account $1. Reason: $2 |
|
参数解释 |
$1：账户信息 $2：失败的异常提示 |
|
日志等级 |
|
|
举例 |
Failed to authenticate the account [email protected]. Reason: Failed to request data from Amazon Web Services. |
|
日志说明 |
用户在Super Controller上通过公有云管理向亚马逊云账户认证失败 |
|
处理建议 |
请根据异常提示处理异常 |
|
关键字 |
ADD_GATEWAY_OP |
|
日志内容 |
Created Internet gateway $1 in the public cloud successfully. |
|
参数解释 |
$1：互联网出口网关名称 |
|
日志等级 |
|
|
举例 |
Created Internet gateway 1111 in the public cloud successfully. |
|
日志说明 |
用户在Super Controller上通过公有云管理向亚马逊云创建互联网出口网关成功 |
|
处理建议 |
系统正常运行时产生的信息，无需处理 |
|
关键字 |
ADD_GATEWAY_OP |
|
日志内容 |
Failed to create Internet gateway $1 in the public cloud. Reason: $2 |
|
参数解释 |
$1：互联网出口网关名称 $2：失败的异常提示 |
|
日志等级 |
|
|
举例 |
Failed to create Internet gateway 111 in the public cloud. Reason: Failed to request data from Amazon Web Services. |
|
日志说明 |
用户在Super Controller上通过公有云管理向亚马逊云创建互联网出口网关失败 |
|
处理建议 |
请根据异常提示处理异常 |
|
关键字 |
ADD_GATEWAY_OP |
|
日志内容 |
Created egress-only Internet gateway $1 in the public cloud successfully |
|
参数解释 |
$1：仅出口互联网网关名称 |
|
日志等级 |
|
|
举例 |
Created egress-only Internet gateway 1111 in the public cloud successfully. |
|
日志说明 |
用户在Super Controller上通过公有云管理向亚马逊云创建仅出口互联网网关成功 |
|
处理建议 |
系统正常运行时产生的信息，无需处理 |
|
关键字 |
ADD_GATEWAY_OP |
|
日志内容 |
Failed to create egress-only Internet gateway $1 in the public cloud. Reason: $2 |
|
参数解释 |
$1：仅出口互联网网关名称 $2：失败的异常提示 |
|
日志等级 |
|
|
举例 |
Failed to create egress-only Internet gateway 111 in the public cloud. Reason: Failed to request data from Amazon Web Services. |
|
日志说明 |
用户在Super Controller上通过公有云管理向亚马逊云创建仅出口互联网网关失败 |
|
处理建议 |
请根据异常提示处理异常 |
|
关键字 |
UPDATE_GATEWAY_OP |
|
日志内容 |
Updated egress gateway $1 in the public cloud successfully |
|
参数解释 |
$1：出口网关名称 |
|
日志等级 |
|
|
举例 |
Updated egress gateway 1111 in the public cloud successfully |
|
日志说明 |
用户在Super Controller上通过公有云管理向亚马逊云更新出口网关成功 |
|
处理建议 |
系统正常运行时产生的信息，无需处理 |
|
关键字 |
UPDATE_GATEWAY_OP |
|
日志内容 |
Failed to update egress gateway $1 in the public cloud. Reason: $2 |
|
参数解释 |
$1：出口网关名称 $2：失败的异常提示 |
|
日志等级 |
|
|
举例 |
Failed to update egress gateway 111 in the public cloud. Reason: Failed to request data from Amazon Web Services. |
|
日志说明 |
用户在Super Controller上通过公有云管理向亚马逊云更新出口网关失败 |
|
处理建议 |
请根据异常提示处理异常 |
|
关键字 |
DEL_GATEWAY_OP |
|
日志内容 |
Deleted Internet gateway $1 from the public cloud successfully. |
|
参数解释 |
$1：互联网出口网关名称 |
|
日志等级 |
|
|
举例 |
Deleted Internet gateway 111 from the public cloud successfully. |
|
日志说明 |
用户在Super Controller上通过公有云管理向亚马逊云删除互联网出口网关成功 |
|
处理建议 |
系统正常运行时产生的信息，无需处理 |
|
关键字 |
DEL_GATEWAY_OP |
|
日志内容 |
Failed to delete Internet gateway %s from the public cloud. Reason: $2 |
|
参数解释 |
$1：互联网出口网关名称 $2：失败的异常提示 |
|
日志等级 |
|
|
举例 |
Failed to delete Internet gateway 111 from the public cloud. Reason: Failed to request data from Amazon Web Services. |
|
日志说明 |
用户在Super Controller上通过公有云管理向亚马逊云删除互联网出口网关失败 |
|
处理建议 |
请根据异常提示处理异常 |
|
关键字 |
DEL_GATEWAY_OP |
|
日志内容 |
Deleted egress-only Internet gateway $1 from the public cloud successfully |
|
参数解释 |
$1：仅出口互联网网关名称 |
|
日志等级 |
|
|
举例 |
Deleted egress-only Internet gateway 1111 from the public cloud successfully |
|
日志说明 |
用户在Super Controller上通过公有云管理向亚马逊云删除仅出口互联网网关成功 |
|
处理建议 |
系统正常运行时产生的信息，无需处理 |
|
关键字 |
DEL_GATEWAY_OP |
|
日志内容 |
Failed to delete egress-only Internet gateway $1 from the public cloud. Reason: $2 |
|
参数解释 |
$1：仅出口互联网网关名称 $2：失败的异常提示 |
|
日志等级 |
|
|
举例 |
Failed to delete egress-only Internet gateway 111 from the public cloud. Reason: Failed to request data from Amazon Web Services. |
|
日志说明 |
用户在Super Controller上通过公有云管理向亚马逊云删除仅出口互联网网关失败 |
|
处理建议 |
请根据异常提示处理异常 |
|
关键字 |
ADD_VROUTER_OP |
|
日志内容 |
Created vRouter $1 in the public cloud successfully |
|
参数解释 |
$1：虚拟路由器名称 |
|
日志等级 |
|
|
举例 |
Created vRouter 1111 in the public cloud successfully. |
|
日志说明 |
用户在Super Controller上通过公有云管理向亚马逊云创建虚拟路由器成功 |
|
处理建议 |
系统正常运行时产生的信息，无需处理 |
|
关键字 |
ADD_VROUTER_OP |
|
日志内容 |
Failed to create vRouter $1 in the public cloud. Reason: $2 |
|
参数解释 |
$1：虚拟路由器名称 $2：失败的异常提示 |
|
日志等级 |
|
|
举例 |
Failed to create vRouter111 in the public cloud. Reason: Failed to request data from Amazon Web Services. |
|
日志说明 |
用户在Super Controller上通过公有云管理向亚马逊云创建虚拟路由器失败 |
|
处理建议 |
请根据异常提示处理异常 |
|
关键字 |
UPDATE_VROUTER_OP |
|
日志内容 |
Updated vRouter $1 in the public cloud successfully |
|
参数解释 |
$1：虚拟路由器名称 |
|
日志等级 |
|
|
举例 |
Updated vRouter 1111 in the public cloud successfully. |
|
日志说明 |
用户在Super Controller上通过公有云管理向亚马逊云更新虚拟路由器成功 |
|
处理建议 |
系统正常运行时产生的信息，无需处理 |
|
关键字 |
UPDATE_VROUTER_OP |
|
日志内容 |
Failed to update vRouter $1 in the public cloud. Reason: $2 |
|
参数解释 |
$1：虚拟路由器名称 $2：失败的异常提示 |
|
日志等级 |
|
|
举例 |
Failed to update vRouter 111 in the public cloud. Reason: Failed to request data from Amazon Web Services. |
|
日志说明 |
用户在Super Controller上通过公有云管理向亚马逊云更新虚拟路由器失败 |
|
处理建议 |
请根据异常提示处理异常 |
|
关键字 |
DEL_VROUTER_OP |
|
日志内容 |
Deleted vRouter $1 from the public cloud successfully |
|
参数解释 |
$1：虚拟路由器名称 |
|
日志等级 |
|
|
举例 |
Deleted vRouter 1111 from the public cloud successfully. |
|
日志说明 |
用户在Super Controller上通过公有云管理向亚马逊云删除虚拟路由器成功 |
|
处理建议 |
系统正常运行时产生的信息，无需处理 |
|
关键字 |
DEL_VROUTER_OP |
|
日志内容 |
Failed to delete vRouter $1 from the public cloud. Reason: $2 |
|
参数解释 |
$1：虚拟路由器名称 $2：失败的异常提示 |
|
日志等级 |
|
|
举例 |
Failed to delete vRouter 111 from the public cloud. Reason: Failed to request data from Amazon Web Services. |
|
日志说明 |
用户在Super Controller上通过公有云管理向亚马逊云删除虚拟路由器失败 |
|
处理建议 |
请根据异常提示处理异常 |
|
关键字 |
ADD_ROUTER_ITEM_OP |
|
日志内容 |
Created route entry $1 in the public cloud successfully. |
|
参数解释 |
$1：路由表项目标网段 |
|
日志等级 |
|
|
举例 |
Created route entry 1111 in the public cloud successfully. |
|
日志说明 |
用户在Super Controller上通过公有云管理向亚马逊云创建路由表项成功 |
|
处理建议 |
系统正常运行时产生的信息，无需处理 |
|
关键字 |
ADD_ROUTER_ITEM_OP |
|
日志内容 |
Failed to create route entry $1 in the public cloud. Reason: $2 |
|
参数解释 |
$1：路由表项目标网段 $2：失败的异常提示 |
|
日志等级 |
|
|
举例 |
Failed to create route entry 111 in the public cloud. Reason: Failed to request data from Amazon Web Services. |
|
日志说明 |
用户在Super Controller上通过公有云管理向亚马逊云创建路由表项失败 |
|
处理建议 |
请根据异常提示处理异常 |
|
关键字 |
DEL_ROUTER_ITEM_OP |
|
日志内容 |
Deleted route entry $1 from the public cloud successfully. |
|
参数解释 |
$1：路由表项目标网段 |
|
日志等级 |
|
|
举例 |
Deleted route entry 1111 from the public cloud successfully. |
|
日志说明 |
用户在Super Controller上通过公有云管理向亚马逊云删除路由表项成功 |
|
处理建议 |
系统正常运行时产生的信息，无需处理 |
|
关键字 |
DEL_ROUTER_ITEM_OP |
|
日志内容 |
Failed to delete route entry $1 from the public cloud. Reason: $2 |
|
参数解释 |
$1：路由表项目标网段 $2：失败的异常提示 |
|
日志等级 |
|
|
举例 |
Failed to delete route entry 111 from the public cloud. Reason: Failed to request data from Amazon Web Services. |
|
日志说明 |
用户在Super Controller上通过公有云管理向亚马逊云删除路由表项失败 |
|
处理建议 |
请根据异常提示处理异常 |
本节介绍Super Controller通过纳管或反向纳管功能管理站点控制器时虚拟路由器模块输出的日志信息。
|
关键字 |
ROUTER_ADD_SUCCESSED |
|
日志内容 |
Successfully added a router configuration in site ”$1”. The router configuration information is as follows: $2 |
|
参数解释 |
$1：站点名称 $2：虚拟路由器信息 |
|
日志等级 |
|
|
举例 |
Successfully added a router configuration in site ”site1”. The router configuration information is as follows: [ID=7c38e18f-a709-c81a-bc43-107c6320a3d4, Name=ds, Description=this is test, L3 VNI=2, CIDRS={[1.1.0.0/16]}, VRF name=3s73gov9o9p0dbogogfhhi18uk] |
|
日志说明 |
用户在Super Controller上通过纳管功能为指定站点新增虚拟路由器成功 |
|
处理建议 |
系统正常运行时产生的信息，无需处理 |
|
关键字 |
ROUTER_ADD_FAILED |
|
日志内容 |
Failed to add a router configuration in site ”$1”. Reason: $2. The router configuration information is as follows: $3 |
|
参数解释 |
$1：站点名称 $2：新增失败的异常提示 $3：虚拟路由器信息 |
|
日志等级 |
|
|
举例 |
Failed to add a router configuration in site ”site1”. Reason: Cannot reach the site. The router configuration information is as follows: [ID=7c38e18f-a709-c81a-bc43-107c6320a3d4, Name=ds, Description=this is test, L3 VNI=2, CIDRS={[1.1.0.0/16]}, VRF name=3s73gov9o9p0dbogogfhhi18uk] |
|
日志说明 |
用户在Super Controller上通过纳管功能为指定站点新增虚拟路由器失败 |
|
处理建议 |
请根据异常提示处理异常 |
|
关键字 |
ROUTER_UPDATE_SUCCESSED |
|
日志内容 |
Successfully updated a router configuration in site ”$1”. The router configuration information is as follows: $2 |
|
参数解释 |
$1：站点名称 $2：虚拟路由器信息 |
|
日志等级 |
|
|
举例 |
Successfully updated a router configuration in site ”site1”. The router configuration information is as follows: [ID=7c38e18f-a709-c81a-bc43-107c6320a3d4, Name=ds, Description=this is test, L3 VNI=2, CIDRS={[1.1.0.0/16]}, VRF name=3s73gov9o9p0dbogogfhhi18uk] |
|
日志说明 |
用户在Super Controller上通过纳管功能更新指定站点的虚拟路由器成功 |
|
处理建议 |
系统正常运行时产生的信息，无需处理 |
|
关键字 |
ROUTER_UPDATE_FAILED |
|
日志内容 |
Failed to update a router configuration in site ”$1”. Reason: $2. The router configuration information is as follows: $2 |
|
参数解释 |
$1：站点名称 $2：更新失败的异常提示 $3：虚拟路由器信息 |
|
日志等级 |
|
|
举例 |
Failed to update a router configuration in site ”site1”. Reason: Cannot reach the site. The router configuration information is as follows: [ID=7c38e18f-a709-c81a-bc43-107c6320a3d4, Name=ds, Description=this is test, L3 VNI=2, CIDRS={[1.1.0.0/16]}, VRF name=3s73gov9o9p0dbogogfhhi18uk] |
|
日志说明 |
用户在Super Controller上通过纳管功能更新指定站点的虚拟路由器失败 |
|
处理建议 |
请根据异常提示处理异常 |
|
关键字 |
ROUTER_DELETE_SUCCESSED |
|
日志内容 |
Successfully deleted a router configuration in site ”$1”. The router configuration information is as follows: $2 |
|
参数解释 |
$1：站点名称 $2：虚拟路由器信息 |
|
日志等级 |
|
|
举例 |
Successfully deleted a router configuration in site ”site1”. The router configuration information is as follows: [ID=7c38e18f-a709-c81a-bc43-107c6320a3d4, Name=ds, Description=this is test, L3 VNI=2, CIDRS={[1.1.0.0/16]}, VRF name=3s73gov9o9p0dbogogfhhi18uk] |
|
日志说明 |
用户在Super Controller上通过纳管功能删除指定站点的虚拟路由器成功 |
|
处理建议 |
系统正常运行时产生的信息，无需处理 |
|
关键字 |
ROUTER_DELETE_FAILED |
|
日志内容 |
Failed to delete a router configuration in site ”$1”. Reason: $2. The router configuration information is as follows: $3 |
|
参数解释 |
$1：站点名称 $2：删除失败的异常提示 $3：虚拟路由器信息 |
|
日志等级 |
|
|
举例 |
Failed to delete a router configuration in site ”site1”. Reason: Cannot reach the site. The router configuration information is as follows: [ID=7c38e18f-a709-c81a-bc43-107c6320a3d4, Name=ds, Description=this is test, L3 VNI=2, CIDRS={[1.1.0.0/16]}, VRF name=3s73gov9o9p0dbogogfhhi18uk] |
|
日志说明 |
用户在Super Controller上通过纳管功能删除指定站点的虚拟路由器失败 |
|
处理建议 |
请根据异常提示处理异常 |
|
关键字 |
CONTROLLED_SITE |
|
日志内容 |
Failed to synchronize settings from site “$1”. Settings failed to be synchronized: $2 |
|
参数解释 |
$1：站点名称 $2：虚拟路由器的配置信息 |
|
日志等级 |
|
|
举例 |
Failed to synchronize settings from site “site 1”. Settings failed to be synchronized: [ID=7c38e18f-a709-c81a-bc43-107c6320a3d4, Name=ds, Description=this is test, L3 VNI=2, CIDRS={[1.1.0.0/16]}, VRF name=3s73gov9o9p0dbogogfhhi18uk] |
|
日志说明 |
用户在Super Controller上通过反向纳管功能管理站点控制器时，由于虚拟路由器的配置同步失败，导致反向纳管操作失败 |
|
处理建议 |
请查看操作日志信息，根据操作日志的失败原因做相应处理 |
|
关键字 |
ROLLBACK_ROUTER_ADD_SUCCESSED |
|
日志内容 |
Successfully rolled back the router adding configuration for site "$1". The router information is as follows: $2. |
|
参数解释 |
$1：站点名称 $2：虚拟路由器的配置信息 |
|
日志等级 |
|
|
举例 |
Successfully rolled back the router adding configuration for site "site1". The router information is as follows: [ID=7c38e18f-a709-c81a-bc43-107c6320a3d4, Name=ds, Description=this is test, L3 VNI=2, CIDRS={[1.1.0.0/16]}, VRF name=3s73gov9o9p0dbogogfhhi18uk] |
|
日志说明 |
向站点下发虚拟路由器的增加配置失败后，回退配置成功 |
|
处理建议 |
无需处理 |
|
关键字 |
ROLLBACK_ROUTER_UPDATE_SUCCESSED |
|
日志内容 |
Successfully rolled back the router updating configuration for site "$1". The router information is as follows: $2. |
|
参数解释 |
$1：站点名称 $2：虚拟路由器的配置信息 |
|
日志等级 |
|
|
举例 |
Successfully rolled back the router updating configuration for site "site1". The router information is as follows: [ID=7c38e18f-a709-c81a-bc43-107c6320a3d4, Name=ds, Description=this is test, L3 VNI=2, CIDRS={[1.1.0.0/16]}, VRF name=3s73gov9o9p0dbogogfhhi18uk] |
|
日志说明 |
向站点下发虚拟路由器的修改配置失败后，回退配置成功 |
|
处理建议 |
无需处理 |
|
关键字 |
ROLLBACK_ROUTER_DELETE_SUCCESSED |
|
日志内容 |
Successfully rolled back the router deleting configuration for site "$1". The router information is as follows: $2. |
|
参数解释 |
$1：站点名称 $2：虚拟路由器的配置信息 |
|
日志等级 |
|
|
举例 |
Successfully rolled back the router deleting configuration for site "site1". The router information is as follows: [ID=7c38e18f-a709-c81a-bc43-107c6320a3d4, Name=ds, Description=this is test, L3 VNI=2, CIDRS={[1.1.0.0/16]}, VRF name=3s73gov9o9p0dbogogfhhi18uk] |
|
日志说明 |
向站点下发虚拟路由器的删除配置失败后，回退配置成功 |
|
处理建议 |
无需处理 |
|
关键字 |
ROLLBACK_ROUTER_ADD_FAILED |
|
日志内容 |
Failed to roll back the router adding configuration for site "$1". Reason: $2. The router information is as follows: $3. |
|
参数解释 |
$1：站点名称 $2：失败的异常提示 $3：虚拟路由器的配置信息 |
|
日志等级 |
|
|
举例 |
Failed to roll back the router adding configuration for site "site1". Reason: Cannot reach the site. The router information is as follows: [ID=7c38e18f-a709-c81a-bc43-107c6320a3d4, Name=ds, Description=this is test, L3 VNI=2, CIDRS={[1.1.0.0/16]}, VRF name=3s73gov9o9p0dbogogfhhi18uk] |
|
日志说明 |
向站点下发虚拟路由器的增加配置失败后，回退配置失败 |
|
处理建议 |
建议在站点上手动清除残留配置 |
|
关键字 |
ROLLBACK_ROUTER_UPDATE_FAILED |
|
日志内容 |
Failed to roll back the router updating configuration for site "$1". Reason: $2. The router information is as follows: $3. |
|
参数解释 |
$1：站点名称 $2：失败的异常提示 $3：虚拟路由器的配置信息 |
|
日志等级 |
|
|
举例 |
Failed to roll back the router updating configuration for site "site1". Reason: Cannot reach the site. The router information is as follows: [ID=7c38e18f-a709-c81a-bc43-107c6320a3d4, Name=ds, Description=this is test, L3 VNI=2, CIDRS={[1.1.0.0/16]}, VRF name=3s73gov9o9p0dbogogfhhi18uk] |
|
日志说明 |
向站点下发虚拟路由器的修改配置失败后，回退配置失败 |
|
处理建议 |
建议在站点上手动清除残留配置 |
|
关键字 |
ROLLBACK_ROUTER_DELETE_FAILED |
|
日志内容 |
Failed to roll back the router deleting configuration for site "$1". Reason: $2. The router information is as follows: $3. |
|
参数解释 |
$1：站点名称 $2：失败的异常提示 $3：虚拟路由器的配置信息 |
|
日志等级 |
|
|
举例 |
Failed to roll back the router deleting configuration for site "site1". Reason: Cannot reach the site. The router information is as follows: [ID=7c38e18f-a709-c81a-bc43-107c6320a3d4, Name=ds, Description=this is test, L3 VNI=2, CIDRS={[1.1.0.0/16]}, VRF name=3s73gov9o9p0dbogogfhhi18uk] |
|
日志说明 |
向站点下发虚拟路由器的删除配置失败后，回退配置失败 |
|
处理建议 |
建议在站点上手动清除残留配置 |
|
关键字 |
ROUTER_ADD_ROUTER_INTERFACE_SUCCESSED |
|
日志内容 |
Successfully bound a vRouter to a subnet in site $1. The vRouter information is as follows: $2 |
|
参数解释 |
$1：站点名称 $2：虚拟路由器信息 |
|
日志等级 |
|
|
举例 |
Successfully bound a vRouter to a subnet in site ”site1”. The vRouter information is as follows: [ID=7c38e18f-a709-c81a-bc43-107c6320a3d4, Name=ds, Description=this is test, L3 VNI=2, CIDRS={[1.1.0.0/16]}, VRF name=3s73gov9o9p0dbogogfhhi18uk] |
|
日志说明 |
用户在Super Controller上为指定站点的虚拟路由器绑定子网成功 |
|
处理建议 |
系统正常运行时产生的信息，无需处理 |
|
关键字 |
ROUTER_ADD_ROUTER_INTERFACE_FAILED |
|
日志内容 |
Failed to bind a vRouter to a subnet in site $1. Reason: $2. The vRouter information is as follows: $3 |
|
参数解释 |
$1：站点名称 $2：失败的异常提示 $3：虚拟路由器信息 |
|
日志等级 |
|
|
举例 |
Failed to bind a vRouter to a subnet in site ”site1”. Reason: Cannot reach the site. The vRouter information is as follows: [ID=7c38e18f-a709-c81a-bc43-107c6320a3d4, Name=ds, Description=this is test, L3 VNI=2, CIDRS={[1.1.0.0/16]}, VRF name=3s73gov9o9p0dbogogfhhi18uk] |
|
日志说明 |
用户在Super Controller上为指定站点的虚拟路由器绑定子网失败 |
|
处理建议 |
请根据异常提示处理异常 |
|
关键字 |
ROUTER_REMOVE_ROUTER_INTERFACE_SUCCESSED |
|
日志内容 |
Successfully removed the binding between a vRouter and a subnet in site $1. The vRouter information is as follows: $2 |
|
参数解释 |
$1：站点名称 $2：虚拟路由器信息 |
|
日志等级 |
|
|
举例 |
Successfully removed the binding between a vRouter and a subnet in site ”site1”. The vRouter information is as follows: [ID=7c38e18f-a709-c81a-bc43-107c6320a3d4, Name=ds, Description=this is test, L3 VNI=2, CIDRS={[1.1.0.0/16]}, VRF name=3s73gov9o9p0dbogogfhhi18uk] |
|
日志说明 |
用户在Super Controller上为指定站点的虚拟路由器解绑子网成功 |
|
处理建议 |
系统正常运行时产生的信息，无需处理 |
|
关键字 |
ROUTER_REMOVE_ROUTER_INTERFACE_FAILED |
|
日志内容 |
Failed to remove the binding between a vRouter and a subnet in site $1. Reason: $2. The vRouter information is as follows: $3 |
|
参数解释 |
$1：站点名称 $2：失败的异常提示 $3：虚拟路由器信息 |
|
日志等级 |
|
|
举例 |
Failed to remove the binding between a vRouter and a subnet in site ”site1”. Reason: Cannot reach the site. The vRouter information is as follows: [ID=7c38e18f-a709-c81a-bc43-107c6320a3d4, Name=ds, Description=this is test, L3 VNI=2, CIDRS={[1.1.0.0/16]}, VRF name=3s73gov9o9p0dbogogfhhi18uk] |
|
日志说明 |
用户在Super Controller上为指定站点的虚拟路由器解绑子网失败 |
|
处理建议 |
请根据异常提示处理异常 |
|
关键字 |
ROLLBACK_ROUTER_REMOVE_ROUTER_INTERFACE_SUCCESSED |
|
日志内容 |
Successfully rolled back the vRouter-to-subnet binding configuration in site $1. The vRouter information is as follows: $2 |
|
参数解释 |
$1：站点名称 $2：虚拟路由器信息 |
|
日志等级 |
|
|
举例 |
Successfully removed the binding between a vRouter and a subnet in site ”site1”. The vRouter information is as follows: [ID=7c38e18f-a709-c81a-bc43-107c6320a3d4, Name=ds, Description=this is test, L3 VNI=2, CIDRS={[1.1.0.0/16]}, VRF name=3s73gov9o9p0dbogogfhhi18uk] |
|
日志说明 |
用户在Super Controller上为指定站点的虚拟路由器绑定子网失败后配置回退成功 |
|
处理建议 |
系统正常运行时产生的信息，无需处理 |
|
关键字 |
ROLLBACK_ROUTER_REMOVE_ROUTER_INTERFACE_FAILED |
|
日志内容 |
Failed to roll back the vRouter-to-subnet binding configuration in site $1. Reason: $2. The vRouter information is as follows: $3 |
|
参数解释 |
$1：站点名称 $2：失败的异常提示 $3：虚拟路由器信息 |
|
日志等级 |
|
|
举例 |
Failed to roll back the vRouter-to-subnet binding configuration in site ”site1”. Reason: Cannot reach the site. The vRouter information is as follows: [ID=7c38e18f-a709-c81a-bc43-107c6320a3d4, Name=ds, Description=this is test, L3 VNI=2, CIDRS={[1.1.0.0/16]}, VRF name=3s73gov9o9p0dbogogfhhi18uk] |
|
日志说明 |
用户在Super Controller上为指定站点的虚拟路由器绑定子网失败后配置回退失败 |
|
处理建议 |
请根据异常提示处理异常 |
|
关键字 |
ROLLBACK_ROUTER_ADD_ROUTER_INTERFACE_SUCCESSED |
|
日志内容 |
Successfully rolled back the vRouter-to-subnet binding removal configuration in site $1. The vRouter information is as follows: $2 |
|
参数解释 |
$1：站点名称 $2：虚拟路由器信息 |
|
日志等级 |
|
|
举例 |
Successfully rolled back the vRouter-to-subnet binding removal configuration in site ”site1”. The vRouter information is as follows: [ID=7c38e18f-a709-c81a-bc43-107c6320a3d4, Name=ds, Description=this is test, L3 VNI=2, CIDRS={[1.1.0.0/16]}, VRF name=3s73gov9o9p0dbogogfhhi18uk] |
|
日志说明 |
用户在Super Controller上为指定站点的虚拟路由器解绑子网失败后配置回退成功 |
|
处理建议 |
系统正常运行时产生的信息，无需处理 |
|
关键字 |
ROLLBACK_ROUTER_ADD_ROUTER_INTERFACE_FAILED |
|
日志内容 |
Failed to roll back the vRouter-to-subnet binding removal configuration in site $1. Reason: $2. The vRouter information is as follows: $3 |
|
参数解释 |
$1：站点名称 $2：失败的异常提示 $3：虚拟路由器信息 |
|
日志等级 |
|
|
举例 |
Failed to roll back the vRouter-to-subnet binding removal configuration in site ”site1”. Reason: Cannot reach the site. The vRouter information is as follows: [ID=7c38e18f-a709-c81a-bc43-107c6320a3d4, Name=ds, Description=this is test, L3 VNI=2, CIDRS={[1.1.0.0/16]}, VRF name=3s73gov9o9p0dbogogfhhi18uk] |
|
日志说明 |
用户在Super Controller上为指定站点的虚拟路由器解绑子网失败后配置回退失败 |
|
处理建议 |
请根据异常提示处理异常 |
本节介绍Super Controller通过纳管或反向纳管功能管理站点控制器时虚拟子网模块输出的日志信息。
|
关键字 |
SUBNET_ADD_SUCCESSED |
|
日志内容 |
Successfully added a subnet configuration in site ”$1”. The subnet configuration information is as follows: $2 |
|
日志等级 |
|
|
参数解释 |
$1：站点名称 $2：虚拟子网信息 |
|
举例 |
Successfully added a subnet configuration in site ”site1”. The subnet configuration information is as follows: [Subnet ID=0d10bd11-0e0d-5119-05dc-26f65558e8c5, Network ID=3c730255-f0c3-996e-e70d-937e7dc994ec, Name=subnet1, IP version=4, CIDR=1.1.0.0/16, Gateway IP=1.1.1.11, DHCP enabling state=false, Description=null, Allocation pools={[]}, IPv6 address mode=Dhcpv6Stateful, IPv6 Ra mode=Dhcpv6Stateful] |
|
日志说明 |
用户在Super Controller上通过纳管功能为指定站点新增虚拟子网成功 |
|
处理建议 |
系统正常运行时产生的信息，无需处理 |
|
关键字 |
SUBNET_ADD_FAILED |
|
日志内容 |
Failed to add a subnet configuration in site ”$1”. Reason: $2. The subnet configuration information is as follows: $3 |
|
参数解释 |
$1：站点名称 $2：新增失败的异常提示 $3：虚拟子网信息 |
|
日志等级 |
|
|
举例 |
Failed to add a subnet configuration in site ”site1”. Reason: A port resides on the subnet. The subnet configuration information is as follows: [Subnet ID=0d10bd11-0e0d-5119-05dc-26f65558e8c5, Network ID=3c730255-f0c3-996e-e70d-937e7dc994ec, Name=subnet1, IP version=4, CIDR=1.1.0.0/16, Gateway IP=1.1.1.11, DHCP enabling state=false, Description=null, Allocation pools={[]}, IPv6 address mode=Dhcpv6Stateful, IPv6 Ra mode=Dhcpv6Stateful] |
|
日志说明 |
用户在Super Controller上通过纳管功能为指定站点新增虚拟子网失败 |
|
处理建议 |
请根据异常提示处理异常 |
|
关键字 |
SUBNET_UPDATE_SUCCESSED |
|
日志内容 |
Successfully updated a subnet configuration in site ”$1”. The subnet configuration information is as follows:$2 |
|
参数解释 |
$1：站点名称 $2：虚拟子网信息 |
|
日志等级 |
|
|
举例 |
Successfully updated a subnet configuration in site ”site1”. The subnet configuration information is as follows: [Subnet ID=0d10bd11-0e0d-5119-05dc-26f65558e8c5, Network ID=3c730255-f0c3-996e-e70d-937e7dc994ec, Name=subnet1, IP version=4, CIDR=1.1.0.0/16, Gateway IP=1.1.1.11, DHCP enabling state=false, Description=null, Allocation pools={[]}, IPv6 address mode=Dhcpv6Stateful, IPv6 Ra mode=Dhcpv6Stateful] |
|
日志说明 |
用户在Super Controller上通过纳管功能更新指定站点的虚拟子网成功 |
|
处理建议 |
系统正常运行时产生的信息，无需处理 |
|
关键字 |
SUBNET_UPDATE_FAILED |
|
日志内容 |
Failed to update a subnet configuration in site ”$1”. Reason: $2. The subnet configuration information is as follows:$3 |
|
参数解释 |
$1：站点名称 $2：更新失败的异常提示 $3：虚拟子网信息 |
|
日志等级 |
|
|
举例 |
Failed to update a subnet configuration in site ”site1”. Reason: A port resides on the subnet. The subnet configuration information is as follows: [Subnet ID=0d10bd11-0e0d-5119-05dc-26f65558e8c5, Network ID=3c730255-f0c3-996e-e70d-937e7dc994ec, Name=subnet1, IP version=4, CIDR=1.1.0.0/16, Gateway IP=1.1.1.11, DHCP enabling state=false, Description=null, Allocation pools={[]}, IPv6 address mode=Dhcpv6Stateful, IPv6 Ra mode=Dhcpv6Stateful] |
|
日志说明 |
用户在Super Controller上通过纳管功能更新指定站点的虚拟子网失败 |
|
处理建议 |
请根据异常提示处理异常 |
|
关键字 |
SUBNET_DELETE_SUCCESSED |
|
日志内容 |
Successfully deleted a subnet configuration in site ”$1”. The subnet configuration information is as follows: $2 |
|
参数解释 |
$1：站点名称 $2：虚拟子网信息 |
|
日志等级 |
|
|
举例 |
Successfully deleted a subnet configuration in site ”site1”. The subnet configuration information is as follows: [Subnet ID=0d10bd11-0e0d-5119-05dc-26f65558e8c5, Network ID=3c730255-f0c3-996e-e70d-937e7dc994ec, Name=subnet1, IP version=4, CIDR=1.1.0.0/16, Gateway IP=1.1.1.11, DHCP enabling state=false, Description=null, Allocation pools={[]}, IPv6 address mode=Dhcpv6Stateful, IPv6 Ra mode=Dhcpv6Stateful] |
|
日志说明 |
用户在Super Controller上通过纳管功能删除指定站点的虚拟子网成功 |
|
处理建议 |
系统正常运行时产生的信息，无需处理 |
|
关键字 |
SUBNET_DELETE_FAILED |
|
日志内容 |
Failed to delete a subnet configuration in site ”$1”. Reason: $2. The subnet configuration information is as follows:$3 |
|
参数解释 |
$1：站点名称 $2：删除失败的异常提示 $3：虚拟子网信息 |
|
日志等级 |
|
|
举例 |
Failed to delete a subnet configuration in site ”site1”. Reason: A port resides on the subnet. The subnet configuration information is as follows: [Subnet ID=0d10bd11-0e0d-5119-05dc-26f65558e8c5, Network ID=3c730255-f0c3-996e-e70d-937e7dc994ec, Name=subnet1, IP version=4, CIDR=1.1.0.0/16, Gateway IP=1.1.1.11, DHCP enabling state=false, Description=null, Allocation pools={[]}, IPv6 address mode=Dhcpv6Stateful, IPv6 Ra mode=Dhcpv6Stateful] |
|
日志说明 |
用户在Super Controller上通过纳管功能删除指定站点的虚拟子网失败 |
|
处理建议 |
请根据异常提示处理异常 |
|
关键字 |
CONTROLLED_SITE |
|
日志内容 |
Failed to synchronize settings from site ”$1”. Settings failed to be synchronized: $2 |
|
参数解释 |
$1：站点名称 $2：虚拟子网的配置信息 |
|
日志等级 |
|
|
举例 |
Failed to synchronize settings from site ”site1”. Settings failed to be synchronized: [Subnet ID=0d10bd11-0e0d-5119-05dc-26f65558e8c5, Network ID=3c730255-f0c3-996e-e70d-937e7dc994ec, Name=subnet1, IP version=4, CIDR=1.1.0.0/16, Gateway IP=1.1.1.11, DHCP enabling state=false, Description=null, Allocation pools={[]}, IPv6 address mode=Dhcpv6Stateful, IPv6 Ra mode=Dhcpv6Stateful] |
|
日志说明 |
用户在Super Controller上通过反向纳管功能管理站点控制器时，由于虚拟子网的配置同步失败，导致反向纳管操作失败 |
|
处理建议 |
请查看操作日志信息，根据操作日志的失败原因做相应处理 |
|
关键字 |
ROLLBACK_SUBNET_ADD_SUCCESSED |
|
日志内容 |
Successfully rolled back the subnet adding configuration for site "$1". The subnet information is as follows: $2. |
|
参数解释 |
$1：站点名称 $2：虚拟子网的配置信息 |
|
日志等级 |
|
|
举例 |
Successfully rolled back the subnet adding configuration for site "site1". The subnet information is as follows: [Subnet ID=0d10bd11-0e0d-5119-05dc-26f65558e8c5, Network ID=3c730255-f0c3-996e-e70d-937e7dc994ec, Name=subnet1, IP version=4, CIDR=1.1.0.0/16, Gateway IP=1.1.1.11, DHCP enabling state=false, Description=null, Allocation pools={[]}, IPv6 address mode=Dhcpv6Stateful, IPv6 Ra mode=Dhcpv6Stateful] |
|
日志说明 |
向站点下发虚拟子网的增加配置失败后，回退配置成功 |
|
处理建议 |
无需处理 |
|
关键字 |
ROLLBACK_SUBNET_UPDATE_SUCCESSED |
|
日志内容 |
Successfully rolled back the subnet updating configuration for site "$1". The subnet information is as follows: $2. |
|
参数解释 |
$1：站点名称 $2：虚拟子网的配置信息 |
|
日志等级 |
|
|
举例 |
Successfully rolled back the subnet updating configuration for site "site1". The subnet information is as follows: [Subnet ID=0d10bd11-0e0d-5119-05dc-26f65558e8c5, Network ID=3c730255-f0c3-996e-e70d-937e7dc994ec, Name=subnet1, IP version=4, CIDR=1.1.0.0/16, Gateway IP=1.1.1.11, DHCP enabling state=false, Description=null, Allocation pools={[]}, IPv6 address mode=Dhcpv6Stateful, IPv6 Ra mode=Dhcpv6Stateful] |
|
日志说明 |
向站点下发虚拟子网的修改配置失败后，回退配置成功 |
|
处理建议 |
无需处理 |
|
关键字 |
ROLLBACK_SUBNET_DELETE_SUCCESSED |
|
日志内容 |
Successfully rolled back the subnet deleting configuration for site "$1". The subnet information is as follows: $2. |
|
参数解释 |
$1：站点名称 $2：虚拟子网的配置信息 |
|
日志等级 |
|
|
举例 |
Successfully rolled back the subnet deleting configuration for site "site1". The subnet information is as follows: [Subnet ID=0d10bd11-0e0d-5119-05dc-26f65558e8c5, Network ID=3c730255-f0c3-996e-e70d-937e7dc994ec, Name=subnet1, IP version=4, CIDR=1.1.0.0/16, Gateway IP=1.1.1.11, DHCP enabling state=false, Description=null, Allocation pools={[]}, IPv6 address mode=Dhcpv6Stateful, IPv6 Ra mode=Dhcpv6Stateful] |
|
日志说明 |
向站点下发虚拟子网的删除配置失败后，回退配置成功 |
|
处理建议 |
无需处理 |
|
关键字 |
ROLLBACK_SUBNET_ADD_FAILED |
|
日志内容 |
Failed to roll back the subnet adding configuration for site "$1". Reason: $2. The subnet information is as follows: $3. |
|
参数解释 |
$1：站点名称 $2：失败的异常提示 $3：虚拟子网的配置信息 |
|
日志等级 |
|
|
举例 |
Failed to roll back the subnet adding configuration for site "site1". Reason: Cannot reach the site. The subnet information is as follows: [Subnet ID=0d10bd11-0e0d-5119-05dc-26f65558e8c5, Network ID=3c730255-f0c3-996e-e70d-937e7dc994ec, Name=subnet1, IP version=4, CIDR=1.1.0.0/16, Gateway IP=1.1.1.11, DHCP enabling state=false, Description=null, Allocation pools={[]}, IPv6 address mode=Dhcpv6Stateful, IPv6 Ra mode=Dhcpv6Stateful] |
|
日志说明 |
向站点下发虚拟子网的增加配置失败后，回退配置失败 |
|
处理建议 |
建议在站点上手动清除残留配置 |
|
关键字 |
ROLLBACK_SUBNET_UPDATE_FAILED |
|
日志内容 |
Failed to roll back the subnet updating configuration for site "$1". Reason: $2. The subnet information is as follows: $3. |
|
参数解释 |
$1：站点名称 $2：失败的异常提示 $3：虚拟子网的配置信息 |
|
日志等级 |
|
|
举例 |
Failed to roll back the subnet updating configuration for site "site1". Reason: Cannot reach the site. The subnet information is as follows: [Subnet ID=0d10bd11-0e0d-5119-05dc-26f65558e8c5, Network ID=3c730255-f0c3-996e-e70d-937e7dc994ec, Name=subnet1, IP version=4, CIDR=1.1.0.0/16, Gateway IP=1.1.1.11, DHCP enabling state=false, Description=null, Allocation pools={[]}, IPv6 address mode=Dhcpv6Stateful, IPv6 Ra mode=Dhcpv6Stateful] |
|
日志说明 |
向站点下发虚拟子网的修改配置失败后，回退配置失败 |
|
处理建议 |
建议在站点上手动清除残留配置 |
|
关键字 |
ROLLBACK_SUBNET_DELETE_FAILED |
|
日志内容 |
Failed to roll back the subnet deleting configuration for site "$1". Reason: $2. The subnet information is as follows: $3. |
|
参数解释 |
$1：站点名称 $2：失败的异常提示 $3：虚拟子网的配置信息 |
|
日志等级 |
|
|
举例 |
Failed to roll back the subnet deleting configuration for site "site1". Reason: Cannot reach the site. The subnet information is as follows: [Subnet ID=0d10bd11-0e0d-5119-05dc-26f65558e8c5, Network ID=3c730255-f0c3-996e-e70d-937e7dc994ec, Name=subnet1, IP version=4, CIDR=1.1.0.0/16, Gateway IP=1.1.1.11, DHCP enabling state=false, Description=null, Allocation pools={[]}, IPv6 address mode=Dhcpv6Stateful, IPv6 Ra mode=Dhcpv6Stateful] |
|
日志说明 |
向站点下发虚拟子网的删除配置失败后，回退配置失败 |
|
处理建议 |
建议在站点上手动清除残留配置 |
本节介绍Super Controller通过纳管或反向纳管功能管理站点控制器时租户模块输出的日志信息。
|
关键字 |
TENANT_ADD_SUCCESSED |
|
日志内容 |
Successfully added a tenant configuration in site ”$1”. The tenant configuration information is as follows:$2 |
|
参数解释 |
$1：站点名称 $2：租户信息 |
|
日志等级 |
|
|
举例 |
Successfully added a tenant configuration in site ”site1”. The tenant configuration information is as follows: [ID=bae92cb9-fcee-49ec-ad67-48a6fe13cc45, Name=test1747, Description=, Type=local-create] |
|
日志说明 |
用户在Super Controller上通过纳管功能向指定的站点新增租户成功 |
|
处理建议 |
系统正常运行时产生的信息，无需处理 |
|
关键字 |
TENANT_ADD_FAILED |
|
日志内容 |
Failed to add a tenant configuration in site ”$1”. Reason: $2. The tenant configuration information is as follows:$3 |
|
参数解释 |
$1：站点名称 $2：新增失败的异常提示 $3：租户信息 |
|
日志等级 |
|
|
举例 |
Failed to add a tenant configuration in site ”site1”. Reason: Cannot reach the site. The tenant configuration information is as follows: [ID=bae92cb9-fcee-49ec-ad67-48a6fe13cc45, Name=test1747, Description=, Type=local-create] |
|
日志说明 |
用户在Super Controller上通过纳管功能向指定的站点新增租户失败 |
|
处理建议 |
请根据异常提示处理异常 |
|
关键字 |
TENANT_UPDATE_SUCCESSED |
|
日志内容 |
Successfully updated a tenant configuration in site ”$1”. The tenant configuration information is as follows:$2 |
|
参数解释 |
$1：站点名称 $2：租户信息 |
|
日志等级 |
|
|
举例 |
Successfully updated a tenant configuration in site ”site1”. The tenant configuration information is as follows: [ID=bae92cb9-fcee-49ec-ad67-48a6fe13cc45, Name=test1747, Description=, Type=local-create] |
|
日志说明 |
用户在Super Controller上通过纳管功能更新指定站点中的租户成功 |
|
处理建议 |
系统正常运行时产生的信息，无需处理 |
|
关键字 |
TENANT_UPDATE_FAILED |
|
日志内容 |
Failed to update a tenant configuration in site ”$1”. Reason: $2. The tenant configuration information is as follows: $3 |
|
参数解释 |
$1：站点名称 $2：更新失败的异常提示 $3：租户信息 |
|
日志等级 |
|
|
举例 |
Failed to update a tenant configuration in site ”site1”. Reason: Cannot reach the site. The tenant configuration information is as follows: [ID=bae92cb9-fcee-49ec-ad67-48a6fe13cc45, Name=test1747, Description=, Type=local-create] |
|
日志说明 |
用户在Super Controller上通过纳管功能更新指定站点中的租户失败 |
|
处理建议 |
请根据异常提示处理异常 |
|
关键字 |
TENANT_DELETE_SUCCESSED |
|
日志内容 |
Successfully deleted a tenant configuration in site ”$1”. The tenant configuration information is as follows: $2 |
|
参数解释 |
$1：站点信息 $2：租户信息 |
|
日志等级 |
|
|
举例 |
Successfully deleted a tenant configuration in site ”site1”. The tenant configuration information is as follows: [ID=bae92cb9-fcee-49ec-ad67-48a6fe13cc45, Name=test1747, Description=, Type=local-create] |
|
日志说明 |
用户在Super Controller上通过纳管功能删除指定站点中的租户成功 |
|
处理建议 |
系统正常运行时产生的信息，无需处理 |
|
关键字 |
TENANT_DELETE_FAILED |
|
日志内容 |
Failed to delete a tenant configuration in site ”$1”. Reason: $2. The tenant configuration information is as follows: $3 |
|
参数解释 |
$1：站点信息 $2：删除失败的异常提示 $3：租户信息 |
|
日志等级 |
|
|
举例 |
Failed to delete a tenant configuration in site ”site1”. Reason: Cannot reach the site. The tenant configuration information is as follows: [ID=bae92cb9-fcee-49ec-ad67-48a6fe13cc45, Name=test1747, Description=, Type=local-create] |
|
日志说明 |
用户在Super Controller上通过纳管功能删除指定站点中的租户失败 |
|
处理建议 |
请根据异常提示处理异常 |
|
关键字 |
CONTROLLED_SITE |
|
日志内容 |
Failed to synchronize settings from site "$1". Settings failed to be synchronized: $2. |
|
参数解释 |
$1：站点信息 $2：租户的配置信息 |
|
日志等级 |
|
|
举例 |
Failed to synchronize settings from site "site1". Settings failed to be synchronized: [ID=39840fd0-9d66-4cda-9bff-5c0dc2b727ba, Name=h3csdn, Description=The tenant information was synchronized from a site, Type=local-create] |
|
日志说明 |
用户在Super Controller上通过反向纳管功能管理站点控制器时，由于租户的配置同步失败，导致反向纳管操作失败 |
|
处理建议 |
请查看操作日志信息，根据操作日志的失败原因做相应处理 |
|
关键字 |
ROLLBACK_TENANT_ADD_SUCCESSED |
|
日志内容 |
Successfully rolled back the tenant adding configuration for site "$1". The tenant information is as follows: $2. |
|
参数解释 |
$1：站点名称 $2：租户的配置信息 |
|
日志等级 |
|
|
举例 |
Successfully rolled back the tenant adding configuration for site "site1". The tenant information is as follows: [ID=04a6c724-f686-449a-9618-a2cf0990dcae, Name=wrc, Description=The tenant information was synchronized from a site., Type=local-create ] |
|
日志说明 |
向站点下发租户的增加配置失败后，回退配置成功 |
|
处理建议 |
无需处理 |
|
关键字 |
ROLLBACK_TENANT_UPDATE_SUCCESSED |
|
日志内容 |
Successfully rolled back the tenant updating configuration for site "$1". The tenant information is as follows: $2. |
|
参数解释 |
$1：站点名称 $2：租户的配置信息 |
|
日志等级 |
|
|
举例 |
Successfully rolled back the tenant updating configuration for site "site1". The tenant information is as follows: [ID=04a6c724-f686-449a-9618-a2cf0990dcae, Name=wrc, Description=The tenant information was synchronized from a site., Type=local-create ] |
|
日志说明 |
向站点下发租户的修改配置失败后，回退配置成功 |
|
处理建议 |
无需处理 |
|
关键字 |
ROLLBACK_TENANT_DELETE_SUCCESSED |
|
日志内容 |
Successfully rolled back the tenant deleting configuration for site "$1". The tenant information is as follows: $2. |
|
参数解释 |
$1：站点名称 $2：租户的配置信息 |
|
日志等级 |
|
|
举例 |
Successfully rolled back the tenant deleting configuration for site "site1". The tenant information is as follows: [ID=04a6c724-f686-449a-9618-a2cf0990dcae, Name=wrc, Description=The tenant information was synchronized from a site., Type=local-create ] |
|
日志说明 |
向站点下发租户的删除配置失败后，回退配置成功 |
|
处理建议 |
无需处理 |
|
关键字 |
ROLLBACK_TENANT_ADD_FAILED |
|
日志内容 |
Failed to roll back the tenant adding configuration for site "$1". Reason: $2. The tenant information is as follows: $3. |
|
参数解释 |
$1：站点名称 $2：失败的异常提示 $3：租户的配置信息 |
|
日志等级 |
|
|
举例 |
Failed to roll back the tenant adding configuration for site "site1". Reason: Cannot reach the site. The tenant information is as follows: [ID=04a6c724-f686-449a-9618-a2cf0990dcae, Name=wrc, Description=The tenant information was synchronized from a site., Type=local-create ] |
|
日志说明 |
向站点下发租户的增加配置失败后，回退配置失败 |
|
处理建议 |
建议在站点上手动清除残留配置 |
|
关键字 |
ROLLBACK_TENANT_UPDATE_FAILED |
|
日志内容 |
Failed to roll back the tenant updating configuration for site "$1". Reason: $2. The tenant information is as follows: $3. |
|
参数解释 |
$1：站点名称 $2：失败的异常提示 $3：租户的配置信息 |
|
日志等级 |
|
|
举例 |
Failed to roll back the tenant updating configuration for site "site1". Reason: Cannot reach the site. The tenant information is as follows: [ID=04a6c724-f686-449a-9618-a2cf0990dcae, Name=wrc, Description=The tenant information was synchronized from a site., Type=local-create ] |
|
日志说明 |
向站点下发租户的修改配置失败后，回退配置失败 |
|
处理建议 |
建议在站点上手动清除残留配置 |
|
关键字 |
ROLLBACK_TENANT_DELETE_FAILED |
|
日志内容 |
Failed to roll back the tenant deleting configuration for site "$1". Reason: $2. The tenant information is as follows: $3. |
|
参数解释 |
$1：站点名称 $2：失败的异常提示 $3：租户的配置信息 |
|
日志等级 |
|
|
举例 |
Failed to roll back the tenant deleting configuration for site "site1". Reason: Cannot reach the site. The tenant information is as follows: [ID=04a6c724-f686-449a-9618-a2cf0990dcae, Name=wrc, Description=The tenant information was synchronized from a site., Type=local-create ] |
|
日志说明 |
向站点下发租户的删除配置失败后，回退配置失败 |
|
处理建议 |
建议在站点上手动清除残留配置 |
本节介绍Super Controller通过业务发放功能对Transit Site做配置发放时Transit Router模块输出的日志信息。
|
关键字 |
TRANSIT_ROUTER_ADD_SUCCESSED |
|
日志内容 |
Successfully added a transit router configuration in site "$1". The transit router configuration information is as follows: $2 |
|
参数解释 |
$1：站点名称 $2：Transit Router信息 |
|
日志等级 |
|
|
举例 |
Successfully added a transit router configuration in site "192.158.14.112". The transit router configuration information is as follows: [ID=e2e3abfe-f478-4e4f-9ef2-3c47236c55b2, Name=TR-0, Description=, Tenant ID=b3f0c753-4320-4c1d-ab75-e5c50189b041, Tenant name=1st_tenant_1, Transit site ID=f6b2c8aa-b817-4bb6-8592-b081b7e77a6c, VRF mode=AUTO, VRF name=72selvtt3o9p7ptshs8shmoldi, L3VNI=5, Import RTS={[0:5]}, Export RTS={[0:5]} ] |
|
日志说明 |
用户在Super Controller上通过配置发放功能为指定站点新增Transit Router成功 |
|
处理建议 |
系统正常运行时产生的信息，无需处理 |
|
关键字 |
TRANSIT_ROUTER_ADD_FAILED |
|
日志内容 |
Failed to add a transit router configuration in site "$1". Reason: $2. The transit router configuration information is as follows: $3 |
|
参数解释 |
$1：站点名称 $2：新增失败的异常提示 $3：Transit Router信息 |
|
日志等级 |
|
|
举例 |
Failed to add a transit router configuration in site "192.158.14.112". Reason: The segment ID 6 is already used. The transit router configuration information is as follows: [ID=e2e3abfe-f478-4e4f-9ef2-3c47236c55b2, Name=TR-0, Description=, Tenant ID=b3f0c753-4320-4c1d-ab75-e5c50189b041, Tenant name=1st_tenant_1, Transit site ID=f6b2c8aa-b817-4bb6-8592-b081b7e77a6c, VRF mode=AUTO, VRF name=72selvtt3o9p7ptshs8shmoldi, L3VNI=5, Import RTS={[0:5]}, Export RTS={[0:5]} ] |
|
日志说明 |
用户在Super Controller上通过配置发放功能为指定站点新增Transit Router失败 |
|
处理建议 |
请根据异常提示处理异常 |
|
关键字 |
TRANSIT_ROUTER_DELETE_SUCCESSED |
|
日志内容 |
Successfully deleted a transit router configuration in site "$1". The transit router configuration information is as follows: $2 |
|
参数解释 |
$1：站点名称 $2：Transit Router信息 |
|
日志等级 |
|
|
举例 |
Successfully deleted a transit router configuration in site "192.158.14.111". The transit router configuration information is as follows: [ID=e2e3abfe-f478-4e4f-9ef2-3c47236c55b2, Name=TR-0, Description=, Tenant ID=b3f0c753-4320-4c1d-ab75-e5c50189b041, Tenant name=1st_tenant_1, Transit site ID=f6b2c8aa-b817-4bb6-8592-b081b7e77a6c, VRF mode=AUTO, VRF name=72selvtt3o9p7ptshs8shmoldi, L3VNI=5, Import RTS={[0:5]}, Export RTS={[0:5]} ] |
|
日志说明 |
用户在Super Controller上通过配置发放功能删除指定站点的Transit Router成功 |
|
处理建议 |
系统正常运行时产生的信息，无需处理 |
|
关键字 |
TRANSIT_ROUTER_DELETE_FAILED |
|
日志内容 |
Failed to delete a transit router configuration in site "$1". Reason: $2. The transit router configuration information is as follows: $3 |
|
参数解释 |
$1：站点名称 $2：删除失败的异常提示 $3：Transit Router信息 |
|
日志等级 |
|
|
举例 |
Failed to delete a transit router configuration in site "192.158.14.112". Reason: Failed to delete the router, because it has a bound subnet. The transit router configuration information is as follows: [ID=e2e3abfe-f478-4e4f-9ef2-3c47236c55b2, Name=TR-0, Description=, Tenant ID=b3f0c753-4320-4c1d-ab75-e5c50189b041, Tenant name=1st_tenant_1, Transit site ID=f6b2c8aa-b817-4bb6-8592-b081b7e77a6c, VRF mode=AUTO, VRF name=72selvtt3o9p7ptshs8shmoldi, L3VNI=5, Import RTS={[0:5]}, Export RTS={[0:5]} ] |
|
日志说明 |
用户在Super Controller上通过配置发放功能删除指定站点的Transit Router失败 |
|
处理建议 |
请根据异常提示处理异常 |
|
关键字 |
ROLLBACK_TRANSIT_ROUTER_ADD_SUCCESSED |
|
日志内容 |
Successfully rolled back the transit router adding configuration for site "$1". The transit router information is as follows: $2. |
|
参数解释 |
$1：站点名称 $2：Transit Router的配置信息 |
|
日志等级 |
|
|
举例 |
Successfully rolled back the transit router adding configuration for site "192.158.14.111". The transit router information is as follows: [ID=e2e3abfe-f478-4e4f-9ef2-3c47236c55b2, Name=TR-0, Description=, Tenant ID=b3f0c753-4320-4c1d-ab75-e5c50189b041, Tenant name=1st_tenant_1, Transit site ID=f6b2c8aa-b817-4bb6-8592-b081b7e77a6c, VRF mode=AUTO, VRF name=72selvtt3o9p7ptshs8shmoldi, L3VNI=5, Import RTS={[0:5]}, Export RTS={[0:5]} ] |
|
日志说明 |
向站点下发Transit Router的增加配置失败后，回退配置成功 |
|
处理建议 |
无需处理 |
|
关键字 |
ROLLBACK_TRANIST_ROUTER_DELETE_SUCCESSED |
|
日志内容 |
Successfully rolled back the transit router deleting configuration for site "$1". The transit router information is as follows: $2. |
|
参数解释 |
$1：站点名称 $2：Transit Router的配置信息 |
|
日志等级 |
|
|
举例 |
Successfully rolled back the transit router deleting configuration for site "site1". The transit router information is as follows: [ID=e2e3abfe-f478-4e4f-9ef2-3c47236c55b2, Name=TR-0, Description=, Tenant ID=b3f0c753-4320-4c1d-ab75-e5c50189b041, Tenant name=1st_tenant_1, Transit site ID=f6b2c8aa-b817-4bb6-8592-b081b7e77a6c, VRF mode=AUTO, VRF name=72selvtt3o9p7ptshs8shmoldi, L3VNI=5, Import RTS={[0:5]}, Export RTS={[0:5]} ] |
|
日志说明 |
向站点下发Transit Router的删除配置失败后，回退配置成功 |
|
处理建议 |
无需处理 |
|
关键字 |
ROLLBACK_TRANSIT_ROUTER_ADD_FAILED |
|
日志内容 |
Failed to roll back the transit router adding configuration for site "$1". Reason: $2. The transit router information is as follows: $3. |
|
参数解释 |
$1：站点名称 $2：失败的异常提示 $3：Transit Router的配置信息 |
|
日志等级 |
|
|
举例 |
Failed to roll back the transit router adding configuration for site "site1". Reason: Cannot reach the site. The transit router information is as follows: [ID=e2e3abfe-f478-4e4f-9ef2-3c47236c55b2, Name=TR-0, Description=, Tenant ID=b3f0c753-4320-4c1d-ab75-e5c50189b041, Tenant name=1st_tenant_1, Transit site ID=f6b2c8aa-b817-4bb6-8592-b081b7e77a6c, VRF mode=AUTO, VRF name=72selvtt3o9p7ptshs8shmoldi, L3VNI=5, Import RTS={[0:5]}, Export RTS={[0:5]} ] |
|
日志说明 |
向站点下发Transit Router的增加配置失败后，回退配置失败 |
|
处理建议 |
建议在站点上手动清除残留配置 |
|
关键字 |
ROLLBACK_TRANSIT_ROUTER_DELETE_FAILED |
|
日志内容 |
Failed to roll back the transit router deleting configuration for site "$1". Reason: $2. The transit router information is as follows: $3. |
|
参数解释 |
$1：站点名称 $2：失败的异常提示 $3：Transit Router的配置信息 |
|
日志等级 |
|
|
举例 |
Failed to roll back the transit router deleting configuration for site "site1". Reason: Cannot reach the site. The transit router information is as follows: [ID=e2e3abfe-f478-4e4f-9ef2-3c47236c55b2, Name=TR-0, Description=, Tenant ID=b3f0c753-4320-4c1d-ab75-e5c50189b041, Tenant name=1st_tenant_1, Transit site ID=f6b2c8aa-b817-4bb6-8592-b081b7e77a6c, VRF mode=AUTO, VRF name=72selvtt3o9p7ptshs8shmoldi, L3VNI=5, Import RTS={[0:5]}, Export RTS={[0:5]} ] |
|
日志说明 |
向站点下发Transit Router的删除配置失败后，回退配置失败 |
|
处理建议 |
建议在站点上手动清除残留配置 |
本节介绍Super Controller通过业务发放功能对Transit Fabric做配置发放时虚拟路由器互通模块输出的日志信息。
|
关键字 |
VPC_CONNECT_ADD_SUCCESSED |
|
日志内容 |
Successfully added a VPC connect configuration in site "$1". The VPC connect configuration information is as follows: $2 |
|
参数解释 |
$1：站点名称 $2：虚拟路由器互通信息 |
|
日志等级 |
|
|
举例 |
Successfully added a VPC connect configuration in site "192.158.14.112". The VPC connect configuration information is as follows: [ID=99753af0-c524-4a5c-82ba-b2848fb9626a, Name=1st_router, Site ID=aa84c57a-cd48-5e2a-6a02-5eec317c9115, Site name=192.158.14.112, Tenant ID=b3f0c753-4320-4c1d-ab75-e5c50189b041, Tenant name=1st_tenant_1, Router ID=58372ba8-966a-4b4a-bd0c-1e8738a0b041, Router name=1st_router, Transit router ID=e2e3abfe-f478-4e4f-9ef2-3c47236c55b2, Transit site ID=f6b2c8aa-b817-4bb6-8592-b081b7e77a6c, Fw enable=true, Local subnets=[09bd84b0-a44f-490d-b776-680b0906af6b, afb60b23-5997-4403-9376-c42eccd26a8b], Local CIDRS={[3.3.3.0/24]}, Peer CIDRS={[4.4.4.0/24]}, Is local all=false, Is peer all=false ] |
|
日志说明 |
用户在Super Controller上通过配置发放功能为指定站点新增虚拟路由器互通成功 |
|
处理建议 |
系统正常运行时产生的信息，无需处理 |
|
关键字 |
VPC_CONNECT_ADD_FAILED |
|
日志内容 |
Failed to add a VPC connect configuration in site "$1". Reason: $2. The VPC connect configuration information is as follows: $3 |
|
参数解释 |
$1：站点名称 $2：新增失败的异常提示 $3：虚拟路由器互通信息 |
|
日志等级 |
|
|
举例 |
Failed to add a VPC connect configuration in site "192.158.14.112". Reason: The local subnet list contains nonexistent subnets. The VPC connect configuration information is as follows: [ID=99753af0-c524-4a5c-82ba-b2848fb9626a, Name=1st_router, Site ID=aa84c57a-cd48-5e2a-6a02-5eec317c9115, Site name=192.158.14.112, Tenant ID=b3f0c753-4320-4c1d-ab75-e5c50189b041, Tenant name=1st_tenant_1, Router ID=58372ba8-966a-4b4a-bd0c-1e8738a0b041, Router name=1st_router, Transit router ID=e2e3abfe-f478-4e4f-9ef2-3c47236c55b2, Transit site ID=f6b2c8aa-b817-4bb6-8592-b081b7e77a6c, Fw enable=true, Local subnets=[09bd84b0-a44f-490d-b776-680b0906af6b, afb60b23-5997-4403-9376-c42eccd26a8b], Local CIDRS={[3.3.3.0/24]}, Peer CIDRS={[4.4.4.0/24]}, Is local all=false, Is peer all=false ] |
|
日志说明 |
用户在Super Controller上通过配置发放功能为指定站点新增虚拟路由器互通失败 |
|
处理建议 |
请根据异常提示处理异常 |
|
关键字 |
VPC_CONNECT_UPDATE_SUCCESSED |
|
日志内容 |
Successfully updated a VPC connect configuration in site "$1". The VPC connect configuration information is as follows: $2 |
|
参数解释 |
$1：站点名称 $2：虚拟路由器互通信息 |
|
日志等级 |
|
|
举例 |
Successfully updated a VPC connect configuration in site "site1". The VPC connect configuration information is as follows: [ID=99753af0-c524-4a5c-82ba-b2848fb9626a, Name=1st_router, Site ID=aa84c57a-cd48-5e2a-6a02-5eec317c9115, Site name=192.158.14.112, Tenant ID=b3f0c753-4320-4c1d-ab75-e5c50189b041, Tenant name=1st_tenant_1, Router ID=58372ba8-966a-4b4a-bd0c-1e8738a0b041, Router name=1st_router, Transit router ID=e2e3abfe-f478-4e4f-9ef2-3c47236c55b2, Transit site ID=f6b2c8aa-b817-4bb6-8592-b081b7e77a6c, Fw enable=true, Local subnets=[09bd84b0-a44f-490d-b776-680b0906af6b, afb60b23-5997-4403-9376-c42eccd26a8b], Local CIDRS={[3.3.3.0/24]}, Peer CIDRS={[4.4.4.0/24]}, Is local all=false, Is peer all=false ] |
|
日志说明 |
用户在Super Controller上通过配置发放功能更新指定站点的虚拟路由器互通成功 |
|
处理建议 |
系统正常运行时产生的信息，无需处理 |
|
关键字 |
VPC_CONNECT_UPDATE_FAILED |
|
日志内容 |
Failed to update a VPC connect configuration in site "$1". Reason: $2. The VPC connect configuration information is as follows: $2 |
|
参数解释 |
$1：站点名称 $2：更新失败的异常提示 $3：虚拟路由器互通信息 |
|
日志等级 |
|
|
举例 |
Failed to update a VPC connect configuration in site "site1". Reason: Cannot reach the site. The VPC connect configuration information is as follows: [ID=99753af0-c524-4a5c-82ba-b2848fb9626a, Name=1st_router, Site ID=aa84c57a-cd48-5e2a-6a02-5eec317c9115, Site name=192.158.14.112, Tenant ID=b3f0c753-4320-4c1d-ab75-e5c50189b041, Tenant name=1st_tenant_1, Router ID=58372ba8-966a-4b4a-bd0c-1e8738a0b041, Router name=1st_router, Transit router ID=e2e3abfe-f478-4e4f-9ef2-3c47236c55b2, Transit site ID=f6b2c8aa-b817-4bb6-8592-b081b7e77a6c, Fw enable=true, Local subnets=[09bd84b0-a44f-490d-b776-680b0906af6b, afb60b23-5997-4403-9376-c42eccd26a8b], Local CIDRS={[3.3.3.0/24]}, Peer CIDRS={[4.4.4.0/24]}, Is local all=false, Is peer all=false ] |
|
日志说明 |
用户在Super Controller上通过配置发放功能更新指定站点的虚拟路由器互通失败 |
|
处理建议 |
请根据异常提示处理异常 |
|
关键字 |
VPC_CONNECT_DELETE_SUCCESSED |
|
日志内容 |
Successfully deleted a VPC connect configuration in site "$1". The VPC connect configuration information is as follows: $2 |
|
参数解释 |
$1：站点名称 $2：虚拟路由器互通信息 |
|
日志等级 |
|
|
举例 |
Successfully deleted a VPC connect configuration in site "192.158.14.111". The VPC connect configuration information is as follows: [ID=99753af0-c524-4a5c-82ba-b2848fb9626a, Name=1st_router, Site ID=aa84c57a-cd48-5e2a-6a02-5eec317c9115, Site name=192.158.14.112, Tenant ID=b3f0c753-4320-4c1d-ab75-e5c50189b041, Tenant name=1st_tenant_1, Router ID=58372ba8-966a-4b4a-bd0c-1e8738a0b041, Router name=1st_router, Transit router ID=e2e3abfe-f478-4e4f-9ef2-3c47236c55b2, Transit site ID=f6b2c8aa-b817-4bb6-8592-b081b7e77a6c, Fw enable=true, Local subnets=[09bd84b0-a44f-490d-b776-680b0906af6b, afb60b23-5997-4403-9376-c42eccd26a8b], Local CIDRS={[3.3.3.0/24]}, Peer CIDRS={[4.4.4.0/24]}, Is local all=false, Is peer all=false ] |
|
日志说明 |
用户在Super Controller上通过配置发放功能删除指定站点的虚拟路由器互通成功 |
|
处理建议 |
系统正常运行时产生的信息，无需处理 |
|
关键字 |
VPC_CONNECT_DELETE_FAILED |
|
日志内容 |
Failed to delete a VPC connect configuration in site "$1". Reason: $2. The VPC connect configuration information is as follows: $3 |
|
参数解释 |
$1：站点名称 $2：删除失败的异常提示 $3：虚拟路由器互通信息 |
|
日志等级 |
|
|
举例 |
Failed to delete a VPC connect configuration in site "192.158.14.112". Reason: controller is unreachable. The VPC connect configuration information is as follows: [ID=99753af0-c524-4a5c-82ba-b2848fb9626a, Name=1st_router, Site ID=aa84c57a-cd48-5e2a-6a02-5eec317c9115, Site name=192.158.14.112, Tenant ID=b3f0c753-4320-4c1d-ab75-e5c50189b041, Tenant name=1st_tenant_1, Router ID=58372ba8-966a-4b4a-bd0c-1e8738a0b041, Router name=1st_router, Transit router ID=e2e3abfe-f478-4e4f-9ef2-3c47236c55b2, Transit site ID=f6b2c8aa-b817-4bb6-8592-b081b7e77a6c, Fw enable=true, Local subnets=[09bd84b0-a44f-490d-b776-680b0906af6b, afb60b23-5997-4403-9376-c42eccd26a8b], Local CIDRS={[3.3.3.0/24]}, Peer CIDRS={[4.4.4.0/24]}, Is local all=false, Is peer all=false ] |
|
日志说明 |
用户在Super Controller上通过配置发放功能删除指定站点的虚拟路由器互通失败 |
|
处理建议 |
请根据异常提示处理异常 |
支持
