Login
| Title | Size | Downloads |
|---|---|---|
| H3C Super Controller System Log Messages Reference-E63xx-5W301-book.pdf | 858.62 KB |
- Table of Contents
- Related Documents
-
|
|
|
H3C Super Controller |
|
System Log Messages Reference |
|
|
|
|
Document version: 5W301-20221205
Copyright © 2022 New H3C Technologies Co., Ltd. All rights reserved.
No part of this manual may be reproduced or transmitted in any form or by any means without prior written consent of New H3C Technologies Co., Ltd.
Except for the trademarks of New H3C Technologies Co., Ltd., any trademarks that may be mentioned in this document are the property of their respective owners.
The information in this document is subject to change without notice.
Contents
Added gateway route successfully
Deleted gateway route successfully
Failed to delete gateway route
Added authentication-free URL successfully
Failed to add authentication-free URL
Deleted authentication-free URL successfully
Failed to delete authentication-free URL
Successfully added classifier for site
Failed to add classifier for site
Successfully edited classifier for site by editing east-west traffic application on super controller
Failed to edit classifier for site by editing east-west traffic application on super controller
Failed to delete classifier for site by deleting east-west traffic application on super controller
Successful adding of EBGP connection
Failure in adding EBGP connection
Successful deletion of EBGP connection
Failure in deleting EBGP connection
Successful rollback upon a failure in adding EBGP connection
Failed rollback upon a failure in adding EBGP connection
Insufficient quantity-based licenses
Successful deletion of vNetwork
Failure in synchronizing vNetwork settings from site
Successful rollback of vNetwork adding configuration
Successful rollback of vNetwork updating configuration
Successful rollback of vNetwork deletion configuration
Rollback failure of vNetwork adding configuration
Rollback failure of vNetwork updating configuration
Rollback failure of vNetwork deletion configuration
Created VPC on AWS successfully
Edited VPC on AWS successfully
Deleted VPC from AWS successfully
Queried VPC from AWS successfully
Created IPv4 CIDR for VPC on AWS successfully
Failed to create IPv4 CIDR for VPC on AWS
Created IPv6 CIDR for VPC on AWS successfully
Failed to create IPv6 CIDR for VPC on AWS
Deleted IPv4 CIDR from VPC on AWS successfully
Failed to delete IPv4 CIDR from VPC on AWS
Deleted IPv6 CIDR from VPC on AWS successfully
Failed to delete IPv6 CIDR from VPC on AWS
Queried regions from AWS successfully
Failed to query regions from AWS
Queried authentication information from AWS successfully
Failed to query authentication information from AWS
Queried account information from AWS successfully
Failed to query account information from AWS
Authenticated account on AWS successfully
Failed to authenticate account on AWS
Created Internet gateway on AWS successfully
Failed to create Internet gateway on AWS
Created egress-only Internet gateway on AWS successfully
Failed to create egress-only Internet gateway on AWS
Edited border gateway on AWS successfully
Failed to edit border gateway on AWS
Deleted Internet gateway from AWS successfully
Failed to delete Internet gateway from AWS
Deleted egress-only Internet gateway from AWS successfully
Failed to delete egress-only Internet gateway from AWS
Created vRouter on AWS successfully
Failed to create vRouter on AWS
Edited vRouter on AWS successfully
Deleted vRouter from AWS successfully
Failed to delete vRouter from AWS
Created route entry on AWS successfully
Failed to create route entry on AWS
Deleted route entry from AWS successfully
Failed to delete route entry from AWS
Created subnet on AWS successfully
Failed to create subnet on AWS
Edited subnet on AWS successfully
Deleted subnet from AWS successfully
Failed to delete subnet from AWS
Created network ACL on AWS successfully
Failed to create network ACL on AWS
Edited network ACL on AWS successfully
Failed to edit network ACL on AWS
Deleted network ACL from AWS successfully
Failed to delete network ACL from AWS
Created network ACL rule on AWS successfully
Failed to create network ACL rule on AWS
Deleted network ACL rule from AWS successfully
Failed to delete network ACL rule from AWS
Associated subnet with network ACL on AWS successfully
Failed to associate subnet with network ACL on AWS
Created security group on AWS successfully
Failed to create security group on AWS
Deleted security group from AWS successfully
Failed to delete security group from AWS
Created security group inbound rule on AWS successfully
Failed to create security group inbound rule on AWS
Deleted security group inbound rule from AWS successfully
Failed to delete security group inbound rule from AWS
Created security group outbound rule on AWS successfully
Failed to create security group outbound rule on AWS
Deleted security group outbound rule from AWS successfully
Failed to delete security group outbound rule from AWS
Edited security group rule name on AWS successfully
Failed to edit security group rule name on AWS
Created endpoint node on AWS successfully
Failed to create endpoint node on AWS
Edited endpoint node on AWS successfully
Failed to edit endpoint node on AWS
Deleted endpoint node from AWS successfully
Failed to delete endpoint node from AWS
Synchronized AZ resources from AWS successfully
Synchronized service resources from AWS successfully
Synchronized VPC resources from AWS successfully
Synchronized egress gateway resources from AWS successfully
Synchronized network ACL resources from AWS successfully
Synchronized vRouter resources from AWS successfully
Synchronized subnet resources from AWS successfully
Synchronized security group resources from AWS successfully
Synchronized endpoint resources from AWS successfully
Failed to synchronize resources from a region on AWS
Created transit gateway on AWS successfully
Failed to create transit gateway on AWS
Edited transit gateway on AWS successfully
Failed to edit transit gateway on AWS
Deleted transit gateway from AWS successfully
Failed to delete transit gateway from AWS
Created transit router on AWS successfully
Failed to create transit router on AWS
Edited transit router on AWS successfully
Failed to edit transit router on AWS
Deleted transit router from AWS successfully
Failed to delete transit router from AWS
Created transit gateway peering on AWS successfully
Failed to create transit gateway peering on AWS
Edited transit gateway peering on AWS successfully
Failed to edit transit gateway peering on AWS
Deleted transit gateway peering from AWS successfully
Failed to delete transit gateway peering from AWS
Failed to query transit gateway peering information from AWS
Created vRouter access on AWS successfully
Failed to create vRouter access on AWS
Edited vRouter access on AWS successfully
Failed to edit vRouter access on AWS
Deleted vRouter access from AWS successfully
Failed to delete vRouter access from AWS
Created transit route entry on AWS successfully
Failed to create transit route entry on AWS
Deleted transit route entry from AWS successfully
Failed to delete transit route entry from AWS
Created transit gateway mount on AWS successfully
Failed to create transit gateway mount on AWS
Associated transit gateway attachment and transit router on AWS successfully
Failed to associate transit gateway attachment and transit router on AWS
Disassociated transit gateway attachment and transit router on AWS successfully
Failed to disassociate transit gateway attachment and transit router on AWS
Propagated transit gateway attachment and transit router association to AWS successfully
Failed to propagate transit gateway attachment and transit router association to AWS
Failed to disable propagation of transit gateway attachment and transit router association to AWS
Edited transit gateway mount on AWS successfully
Failed to edit transit gateway mount on AWS
Deleted transit gateway mount from AWS successfully
Failed to delete transit gateway mount from AWS
Successful deletion of vRouter
Failure to synchronize vRouter settings from site
Successful rollback of vRouter adding configuration
Successful rollback of vRouter updating configuration
Successful rollback of vRouter deletion configuration
Rollback failure of vRouter adding configuration
Rollback failure of vRouter updating configuration
Rollback failure of vRouter deletion configuration
Successful binding of vRouter to subnet in a site
Failure in binding vRouter to subnet in a site
Successful unbinding of vRouter from subnet in a site
Failure to unbind vRouter from subnet in a site
Successful rollback of vRouter-to-subnet binding configuration in a site
Rollback failure of vRouter-to-subnet binding configuration in a site
Successful rollback of vRouter-to-subnet unbinding configuration in a site
Rollback failure of vRouter-to-subnet unbinding configuration in a site
Bound firewall service resource to transit router of site successfully
Failed to bind firewall service resource to transit router of site
Unbound firewall service resource from transit router of site successfully
Failed to unbind firewall service resource from transit router of site
Failure in synchronizing subnet settings from site
Successful rollback of subnet adding configuration
Successful rollback of subnet update configuration
Successful rollback of subnet deletion configuration
Failure in rollback of subnet adding configuration
Failure in rollback of subnet update configuration
Failure in rollback of subnet deletion configuration
Failure in synchronizing tenant settings from site
Successful rollback of tenant adding configuration
Successful rollback of tenant update configuration
Successful rollback of tenant deletion configuration
Failure in rollback of tenant adding configuration
Failure in rollback of tenant update configuration
Failure in rollback of tenant deletion configuration
Successful adding of a transit router to a site
Failure in adding a transit router to a site
Successful edition of a transit router in a site
Failure in editing a transit router in a site
Successful deletion of a transit router from a site
Failure in deleting a transit router from a site
Successful configuration rollback after failure in adding a transit router
Successful configuration rollback after failure in deleting a transit router
Failed configuration rollback after failure in adding a transit router
Failed configuration rollback after failure in deleting a transit router
Successful creation of a transit router-gateway binding for a site
Failure in adding a transit router-gateway binding for a site
Successful removal of a transit router-gateway binding for a site
Failure in removing a transit router-gateway binding for a site
Successful creation of a transit router-vPort binding for a site
Failure in adding a transit router-vPort binding for a site
Successful removal of a transit router-vPort binding for a site
Failure in removing a transit router-vPort binding for a site
Successful creation of a transit router-subnet binding for a site
Failure in adding a transit router-subnet binding for a site
Successful removal of a transit router-subnet binding for a site
Failure in removing a transit router-subnet binding for a site
Successful adding of a VPC connect to a site
Failure in adding a VPC connect to a site
Successful update of a VPC connect for a site
Failure in updating a VPC connect for a site
Successful deletion of a VPC connect from a site
Failure in deleting a VPC connect from a site
Introduction
System logs record internal events that occur on the controller. System log messages include field description, message explanation, and recommended action, and provide reference for system analysis and maintenance.
This document assumes that the readers are familiar with data communications technologies and super controller products.
Viewing system log messages
Select System > Log Center > System Log List to enter system log view. The generated system log messages are displayed on pages as shown in Figure 1.
Table 1 System log message elements
|
Element |
Description |
|
Severity |
Severity level of the message. For more information about severity levels, see Table 5. |
|
Time |
Date and time when the log message was generated. |
|
Component Name |
Name of the component that produced the log message. |
|
Host Name |
Name of the host that produced the log message. |
|
Service Name |
Name of the service that produced the log message. |
|
Module Name |
Name of the service module that produced the log message. For more information about service modules, see Table 3. |
|
Description |
Text string that contains detailed information about the event or error. |
Syslog message format
The super controller can send system logs to syslog servers through the syslog protocol. To set the IP address and port number of a syslog server, select System > Settings > Log Settings on the top navigation bar, and then select System Log.
By default, controllers send system logs in the following format:
<PRI>TIMESTAMP Hostname Service/severity/Keywords CONTENT
Table 2 Syslog message elements
|
Element |
Description |
|
<PRI> |
Priority identifier. It is calculated by using the following formula: Priority identifier=facilityx8+severity Where: · Facility represents the programming module defined by syslog. In the current software version, the facility is user-level and its value is 1. · Severity represents the syslog message severity level. For more information, see Table 4. |
|
TIMESTAMP |
Date and time when the event occurred. |
|
Hostname |
Name of the container that produced the message. |
|
Service |
Name of the service module that produced the message. For more information about service modules, see Table 3. |
|
severity |
Severity level of the message. For more information, see Table 5. Five syslog message severity levels are used. |
|
Keywords |
Keywords of the message that facilitate searching or memorizing. |
|
CONTENT |
Text string that contains detailed information about the event or error. |
Table 3 lists the service modules that might produce system log messages.
|
Service module name |
Description |
|
COS |
Northbound service customization module. |
|
DATA_CONSISTENCY |
Data consistency module. |
|
EAST_WEST_APPLICATION |
East-west traffic application module. |
|
EBGP_CONNECTION |
EBGP neighbor management module |
|
FIREWALL |
Firewall module. |
|
FLOATING_IP |
Floating IP module. |
|
LICENSE |
License management module |
|
NETWORK |
vNetwork management module |
|
PUBLIC_CLOUD |
Public cloud connection management and orchestration module. |
|
ROUTE_ENTRY |
Route entry module. |
|
ROUTE_TABLE |
Routing table entry. |
|
ROUTER |
vRouter management module |
|
SERVICERESOURCE |
Firewall service resource module. |
|
SUBNET |
vSubnet management module |
|
TENANT |
Tenant management module |
|
TRANSIT_ROUTER |
Transit router management module |
|
VPC_CONNECT |
VPC connection management module |
|
VPORT |
vPort module. |
Syslog messages are classified into eight severity levels from 0 to 7. The lower the number, the higher the severity, as shown in Table 4.
Table 4 Syslog message severity levels
|
Level |
Severity |
Description |
|
0 |
Emergency |
Emergent condition. The system is unusable. |
|
1 |
Alert |
Action must be taken immediately. |
|
2 |
Critical |
Critical condition. |
|
3 |
Error |
Error condition. |
|
4 |
Warning |
Warning condition. |
|
5 |
Notice |
Normal but significant condition. |
|
6 |
Informational |
Informational message. |
|
7 |
Debug |
Debugging message. |
The super controller uses five syslog message severity levels, as shown in Table 5.
Table 5 System log message severity levels
|
Level |
Icon |
Severity |
Description |
|
6 |
|
Informational |
Information message. |
|
4 |
|
Warning |
Warning condition. |
|
3 |
|
Error |
Error condition. |
|
2 |
|
Critical |
Critical condition. |
|
0 |
|
Emergency |
Emergent condition. The system is unusable. |
Using this document
This document categories system log messages by service module. This document explains messages in tables. Table 6 describes information provided in these tables.
Table 6 Message explanation table contents
|
Item |
Content |
Example |
|
Keyword |
Summary of the message that facilitates searching or memorizing. |
LICENSE_INSTALL |
|
Message text |
Presents the message description. |
$1 license successfully installed. |
|
Variable fields |
Briefly describes the variable fields in the order that they appear in the message text. The variable fields are numbered in the "$Number" form to help you identify their location in the message text. |
$1: License name. |
|
Severity level |
Provides the severity level of the message. |
|
|
Example |
Provides a real message example. |
Base license successfully installed. |
|
Explanation |
Explains the message, including the event or error cause. |
The specified license has been successfully installed. |
|
Recommended action |
Provides recommended actions. For informational messages, no action is required. |
No action is required. |
COS
This section contains messages generated when the super controller creates and deletes gateway routes and authentication-free URLs on Unified Platform through northbound service customization.
Added gateway route successfully
|
Keyword |
COS_ADD_ROUTE_SUCCESS |
|
Message text |
Added gateway route $1 successfully. |
|
Variable fields |
$1: Gateway route information. |
|
Severity level |
|
|
Example |
Added gateway route { "name":"cos_d6c1057d-bded-497d-892d-b6ba13a30892", "strip_path":false, "preserve_host":true, "serviceName":"SUC_CUSTOMSERVICE", "paths":[ "/api/rest/securityManagement/v1.0/oauth/token", "/api/rest/securityManagement/v1.0/oauth/token", "/api/rest/securityManagement/v1.0/oauth/handshake"] } successfully. |
|
Explanation |
Added a gateway route through adding a northbound service on the super controller successfully. |
|
Recommended action |
No action is required. |
Failed to add gateway route
|
Keyword |
COS_ADD_ROUTE_FAILED |
|
Message text |
Failed to add gateway route $1. |
|
Variable fields |
$1: Gateway route information. |
|
Severity level |
|
|
Example |
Failed to add gateway route { "name":"cos_d6c1057d-bded-497d-892d-b6ba13a30892", "strip_path":false, "preserve_host":true, "serviceName":"SUC_CUSTOMSERVICE", "paths":[ "/api/rest/securityManagement/v1.0/oauth/token", "/api/rest/securityManagement/v1.0/oauth/token", "/api/rest/securityManagement/v1.0/oauth/handshake"] }. |
|
Explanation |
Failed to add a gateway route through adding a northbound service on the super controller. |
|
Recommended action |
View the failure cause on Unified Platform. |
Deleted gateway route successfully
|
Keyword |
COS_DELETE_ROUTE_SUCCESS |
|
Message text |
Deleted gateway route $1 successfully. |
|
Variable fields |
$1: Gateway route information. |
|
Severity level |
|
|
Example |
Deleted gateway route cos_d6c1057d-bded-497d-892d-b6ba13a30892 successfully. |
|
Explanation |
Deleted a gateway route through deleting a northbound service on the super controller successfully. |
|
Recommended action |
No action is required. |
Failed to delete gateway route
|
Keyword |
COS_DELETE_ROUTE_FAILED |
|
Message text |
Failed to delete gateway route $1. |
|
Variable fields |
$1: Gateway route information. |
|
Severity level |
|
|
Example |
Failed to delete gateway route cos_d6c1057d-bded-497d-892d-b6ba13a30892. |
|
Explanation |
Failed to delete a gateway route through deleting a northbound service on the super controller. |
|
Recommended action |
View the failure cause on Unified Platform. |
Added authentication-free URL successfully
|
Keyword |
COS_ADD_AUTH_URL_SUCCESS |
|
Message text |
Added authentication-free URL $1 successfully. |
|
Variable fields |
$1: Authentication-free URL information. |
|
Severity level |
|
|
Example |
Added authentication-free URL [ {"url":"/api/rest/securityManagement/v1.0/oauth/token"}, {"url":"/api/rest/securityManagement/v1.0/oauth/handshake"} ] successfully. |
|
Explanation |
Added an authentication-free URL through adding a northbound service on the super controller successfully. |
|
Recommended action |
No action is required. |
Failed to add authentication-free URL
|
Keyword |
COS_ADD_AUTH_URL_FAILED |
|
Message text |
Failed to add authentication-free URL $1. |
|
Variable fields |
$1: Authentication-free URL information. |
|
Severity level |
|
|
Example |
Failed to add authentication-free URL [ {"url":"/api/rest/securityManagement/v1.0/oauth/token"}, {"url":"/api/rest/securityManagement/v1.0/oauth/handshake"} ]. |
|
Explanation |
Failed to add an authentication-free URL through adding a northbound service on the super controller. |
|
Recommended action |
View the failure cause on Unified Platform. |
Deleted authentication-free URL successfully
|
Keyword |
COS_DEL_AUTH_URL_SUCCESS |
|
Message text |
Deleted authentication-free URL $1 successfully. |
|
Variable fields |
$1: Authentication-free URL information. |
|
Severity level |
|
|
Example |
Deleted authentication-free URL [ {"url":"/api/rest/securityManagement/v1.0/oauth/token"}, {"url":"/api/rest/securityManagement/v1.0/oauth/handshake"} ] successfully. |
|
Explanation |
Deleted an authentication-free URL through deleting a northbound service on the super controller successfully. |
|
Recommended action |
No action is required. |
Failed to delete authentication-free URL
|
Keyword |
COS_DEL_AUTH_URL_FAILED |
|
Message text |
Failed to delete authentication-free URL $1. |
|
Variable fields |
$1: Authentication-free URL information. |
|
Severity level |
|
|
Example |
Failed to delete authentication-free URL [ {"url":"/api/rest/securityManagement/v1.0/oauth/token"}, {"url":"/api/rest/securityManagement/v1.0/oauth/handshake"} ]. |
|
Explanation |
Failed to delete an authentication-free URL through deleting a northbound service on the super controller. |
|
Recommended action |
View the failure cause on Unified Platform. |
DATA_CONSISTENCY
This section contains data auditing and data synchronization messages.
Data auditing failed
|
Keyword |
DATA_CONSISTENCY_AUDIT_FALIED |
|
Message text |
Failed to audit differences for site $1. Reason: $2. |
|
Variable fields |
$1: Site name. $2: Failure cause. |
|
Severity level |
Warning |
|
Example |
Failed to audit differences for site dc1. Reason: The connection state of the site is abnormal. |
|
Explanation |
The super controller failed to audit data for a site. |
|
Recommended action |
· Verify that the super controller and site are reachable to each other. · Verify that the site is in normal state. |
Data synchronization failed
|
Keyword |
DATA_CONSISTENCY_SMOOTH_FALIED |
|
Message text |
Failed to repair configuration for site $1. Reason: $2. |
|
Variable fields |
$1: Site name. $2: Failure cause. |
|
Severity level |
Warning |
|
Example |
Failed to repair configuration for site dc1. Reason: The connection state of the site is abnormal. |
|
Explanation |
The super controller failed to synchronize data for a site. |
|
Recommended action |
· Verify that the super controller and site are reachable to each other. · Verify that the site is in normal state. |
EAST_WEST_APPLICATION
This section contains messages generated when the super controller deploys configuration to sites through east-west traffic applications.
Successfully added classifier for site
|
Keyword |
CLASSIFIER_ADD_SUCCESSED |
|
Message text |
Successfully added a classifier configuration for site "$1". The classifier information is as follows: $2 |
|
Variable fields |
$1: Site name. $2: Classifier information. |
|
Severity level |
|
|
Example |
Successfully added a classifier configuration for site "148.200". The classifier information is as follows: [ID=f02b1a2b-480f-474c-9547-b461a88f40ba, Name=21, Cloud Region Name=SuperController, Rules=[ [ID=fee1eeee-3d74-42e8-86ef-883aae06d061, Name=fee1eeee-3d74-42e8-86ef-883aae06d061, Protocol=ALL, Ip Version=IPV4, Source Ip=22.22.22.0/24, Destination Ip=11.11.11.0/24 ], [ID=2888e14b-2942-4ae5-960f-a33d0ed87d68, Name=2888e14b-2942-4ae5-960f-a33d0ed87d68, Protocol=ALL, Ip Version=IPV4, Source Ip=11.11.11.0/24, Destination Ip=11.11.11.0/24 ]] ] |
|
Explanation |
Successfully added a classifier for a site by creating an east-west traffic application on the super controller. |
|
Recommended action |
No action is required. |
Failed to add classifier for site
|
Keyword |
CLASSIFIER_ADD_FAILED |
|
Message text |
Failed to add a classifier configuration for site "$1". Reason: $2. The classifier information is as follows: $2 |
|
Variable fields |
$1: Site name. $2: Failure cause. $3: Classifier information. |
|
Severity level |
|
|
Example |
Failed to add a classifier configuration for site "148.150". Reason: Internal error. The classifier information is as follows: [ID=f02b1a2b-480f-474c-9547-b461a88f40ba, Name=21, Cloud Region Name=SuperController, Rules=[ [ID=fee1eeee-3d74-42e8-86ef-883aae06d061, Name=fee1eeee-3d74-42e8-86ef-883aae06d061, Protocol=ALL, Ip Version=IPV4, Source Ip=22.22.22.0/24, Destination Ip=11.11.11.0/24 ], [ID=2888e14b-2942-4ae5-960f-a33d0ed87d68, Name=2888e14b-2942-4ae5-960f-a33d0ed87d68, Protocol=ALL, Ip Version=IPV4, Source Ip=11.11.11.0/24, Destination Ip=11.11.11.0/24 ]] ] |
|
Explanation |
Failed to add a classifier for a site by creating an east-west traffic application on the super controller. |
|
Recommended action |
Follow the prompt to resolve the problem. |
Successfully edited classifier for site by editing east-west traffic application on super controller
|
Keyword |
CLASSIFIER_UPDATE_SUCCESSED |
|
Message text |
Successfully updated a classifier configuration for site "$1". The classifier information is as follows: $2 |
|
Variable fields |
$1: Site name. $2: Classifier information. |
|
Severity level |
|
|
Example |
Successfully updated a classifier configuration for site "148.150". The classifier information is as follows: [ID=f02b1a2b-480f-474c-9547-b461a88f40ba, Name=21, Cloud Region Name=SuperController, Rules=[ [ID=fee1eeee-3d74-42e8-86ef-883aae06d061, Name=fee1eeee-3d74-42e8-86ef-883aae06d061, Protocol=ALL, Ip Version=IPV4, Source Ip=22.22.22.0/24, Destination Ip=11.11.11.0/24 ], [ID=2888e14b-2942-4ae5-960f-a33d0ed87d68, Name=2888e14b-2942-4ae5-960f-a33d0ed87d68, Protocol=ALL, Ip Version=IPV4, Source Ip=11.11.11.0/24, Destination Ip=11.11.11.0/24 ]] ] |
|
Explanation |
Successfully edited a classifier for a site by editing an east-west traffic application on the super controller. |
|
Recommended action |
No action is required. |
Failed to edit classifier for site by editing east-west traffic application on super controller
|
Keyword |
CLASSIFIER_UPDATE_FAILED |
|
Message text |
Failed to update a classifier configuration for site "$1". Reason: $2. The classifier information is as follows: $3 |
|
Variable fields |
$1: Site name. $2: Failure cause. $3: Classifier information. |
|
Severity level |
|
|
Example |
Failed to update a classifier configuration for site "148.150". Reason: Internal error. The classifier information is as follows: [ID=f02b1a2b-480f-474c-9547-b461a88f40ba, Name=21, Cloud Region Name=SuperController, Rules=[ [ID=fee1eeee-3d74-42e8-86ef-883aae06d061, Name=fee1eeee-3d74-42e8-86ef-883aae06d061, Protocol=ALL, Ip Version=IPV4, Source Ip=22.22.22.0/24, Destination Ip=11.11.11.0/24 ], [ID=2888e14b-2942-4ae5-960f-a33d0ed87d68, Name=2888e14b-2942-4ae5-960f-a33d0ed87d68, Protocol=ALL, Ip Version=IPV4, Source Ip=11.11.11.0/24, Destination Ip=11.11.11.0/24 ]] ] |
|
Explanation |
Failed to edit a classifier for a site by editing an east-west traffic application on the super controller. |
|
Recommended action |
Follow the prompt to resolve the problem. |
Successfully deleted classifier for site by deleting east-west traffic application on super controller
|
Keyword |
CLASSIFIER_DELETE_SUCCESSED |
|
Message text |
Successfully deleted a classifier configuration for site "$1". The classifier information is as follows: $2 |
|
Variable fields |
$1: Site name. $2: Classifier information. |
|
Severity level |
|
|
Example |
Successfully deleted a classifier configuration for site "148.150". The classifier information is as follows: [ID=f02b1a2b-480f-474c-9547-b461a88f40ba, Name=21, Cloud Region Name=SuperController, Rules=[ [ID=fee1eeee-3d74-42e8-86ef-883aae06d061, Name=fee1eeee-3d74-42e8-86ef-883aae06d061, Protocol=ALL, Ip Version=IPV4, Source Ip=22.22.22.0/24, Destination Ip=11.11.11.0/24 ], [ID=2888e14b-2942-4ae5-960f-a33d0ed87d68, Name=2888e14b-2942-4ae5-960f-a33d0ed87d68, Protocol=ALL, Ip Version=IPV4, Source Ip=11.11.11.0/24, Destination Ip=11.11.11.0/24 ]] ] |
|
Explanation |
Successfully deleted a classifier for a site by deleting an east-west traffic application on the super controller. |
|
Recommended action |
No action is required. |
Failed to delete classifier for site by deleting east-west traffic application on super controller
|
Keyword |
CLASSIFIER_DELETE_FAILED |
|
Message text |
Failed to delete a classifier configuration for site "$1". Reason: $2. The classifier information is as follows: $3 |
|
Variable fields |
$1: Site name. $2: Failure cause. $3: Classifier information. |
|
Severity level |
|
|
Example |
Failed to delete a classifier configuration for site "148.150". Reason: Internal error. The classifier information is as follows: [ID=f02b1a2b-480f-474c-9547-b461a88f40ba, Name=21, Cloud Region Name=SuperController, Rules=[ [ID=fee1eeee-3d74-42e8-86ef-883aae06d061, Name=fee1eeee-3d74-42e8-86ef-883aae06d061, Protocol=ALL, Ip Version=IPV4, Source Ip=22.22.22.0/24, Destination Ip=11.11.11.0/24 ], [ID=2888e14b-2942-4ae5-960f-a33d0ed87d68, Name=2888e14b-2942-4ae5-960f-a33d0ed87d68, Protocol=ALL, Ip Version=IPV4, Source Ip=11.11.11.0/24, Destination Ip=11.11.11.0/24 ]] ] |
|
Explanation |
Failed to delete a classifier for a site by deleting an east-west traffic application on the super controller. |
|
Recommended action |
Follow the prompt to resolve the problem. |
Failed to deploy classifier creation configuration to site, and successfully rolled back configuration for site
|
Keyword |
ROLLBACK_CLASSIFIER_ADD_SUCCESSED |
|
Message text |
Successfully rolled back the classifier adding configuration for site "$1". The classifier information is as follows: $2. |
|
Variable fields |
$1: Site name. $2: Classifier configuration. |
|
Severity level |
|
|
Example |
Successfully rolled back the classifier adding configuration for site "148.150". The classifier information is as follows: [ID=f02b1a2b-480f-474c-9547-b461a88f40ba, Name=21, Cloud Region Name=SuperController, Rules=[ [ID=fee1eeee-3d74-42e8-86ef-883aae06d061, Name=fee1eeee-3d74-42e8-86ef-883aae06d061, Protocol=ALL, Ip Version=IPV4, Source Ip=22.22.22.0/24, Destination Ip=11.11.11.0/24 ], [ID=2888e14b-2942-4ae5-960f-a33d0ed87d68, Name=2888e14b-2942-4ae5-960f-a33d0ed87d68, Protocol=ALL, Ip Version=IPV4, Source Ip=11.11.11.0/24, Destination Ip=11.11.11.0/24 ]] ] |
|
Explanation |
Failed to deploy the classifier creation configuration to a site, and successfully rolled back the configuration for the site. |
|
Recommended action |
No action is required. |
Failed to deploy classifier deletion configuration to site, and successfully rolled back configuration for site
|
Keyword |
ROLLBACK_CLASSIFIER_DELETE_SUCCESSED |
|
Message text |
Successfully rolled back the classifier deleting configuration for site "$1". The classifier information is as follows: $2. |
|
Variable fields |
$1: Site name. $2: Classifier configuration. |
|
Severity level |
|
|
Example |
Successfully rolled back the classifier deleting configuration for site "148.150". The classifier information is as follows: [ID=f02b1a2b-480f-474c-9547-b461a88f40ba, Name=21, Cloud Region Name=SuperController, Rules=[ [ID=fee1eeee-3d74-42e8-86ef-883aae06d061, Name=fee1eeee-3d74-42e8-86ef-883aae06d061, Protocol=ALL, Ip Version=IPV4, Source Ip=22.22.22.0/24, Destination Ip=11.11.11.0/24 ], [ID=2888e14b-2942-4ae5-960f-a33d0ed87d68, Name=2888e14b-2942-4ae5-960f-a33d0ed87d68, Protocol=ALL, Ip Version=IPV4, Source Ip=11.11.11.0/24, Destination Ip=11.11.11.0/24 ]] ] |
|
Explanation |
Failed to deploy the classifier deletion configuration to a site, and successfully rolled back the configuration for the site. |
|
Recommended action |
No action is required. |
Failed to deploy classifier modification configuration to site, and successfully rolled back configuration for site
|
Keyword |
ROLLBACK_CLASSIFIER_UPDATE_SUCCESSED |
|
Message text |
Successfully rolled back the classifier updating configuration for site "$1". The classifier information is as follows: $2. |
|
Variable fields |
$1: Site name. $2: Classifier configuration. |
|
Severity level |
|
|
Example |
Successfully rolled back the classifier updating configuration for site "site1". The classifier information is as follows: [ID=f02b1a2b-480f-474c-9547-b461a88f40ba, Name=21, Cloud Region Name=SuperController, Rules=[ [ID=fee1eeee-3d74-42e8-86ef-883aae06d061, Name=fee1eeee-3d74-42e8-86ef-883aae06d061, Protocol=ALL, Ip Version=IPV4, Source Ip=22.22.22.0/24, Destination Ip=11.11.11.0/24 ], [ID=2888e14b-2942-4ae5-960f-a33d0ed87d68, Name=2888e14b-2942-4ae5-960f-a33d0ed87d68, Protocol=ALL, Ip Version=IPV4, Source Ip=11.11.11.0/24, Destination Ip=11.11.11.0/24 ]] ] |
|
Explanation |
Failed to deploy the classifier modification configuration to a site, and successfully rolled back the configuration for the site. |
|
Recommended action |
No action is required. |
Failed to deploy classifier creation configuration to site, and failed to roll back configuration for site
|
Keyword |
ROLLBACK_CLASSIFIER_ADD_FAILED |
|
Message text |
Failed to roll back the classifier adding configuration for site "$1". Reason: $2. The classifier information is as follows: $3. |
|
Variable fields |
$1: Site name. $2: Failure cause. $3: Classifier configuration. |
|
Severity level |
|
|
Example |
Failed to roll back the classifier adding configuration for site "site1". Reason: Cannot reach the site. The classifier information is as follows: [ID=f02b1a2b-480f-474c-9547-b461a88f40ba, Name=21, Cloud Region Name=SuperController, Rules=[ [ID=fee1eeee-3d74-42e8-86ef-883aae06d061, Name=fee1eeee-3d74-42e8-86ef-883aae06d061, Protocol=ALL, Ip Version=IPV4, Source Ip=22.22.22.0/24, Destination Ip=11.11.11.0/24 ], [ID=2888e14b-2942-4ae5-960f-a33d0ed87d68, Name=2888e14b-2942-4ae5-960f-a33d0ed87d68, Protocol=ALL, Ip Version=IPV4, Source Ip=11.11.11.0/24, Destination Ip=11.11.11.0/24 ]] ] |
|
Explanation |
Failed to deploy the classifier creation configuration to a site, and failed to roll back the configuration for the site. |
|
Recommended action |
Manually clear the residual configuration on the site. |
Failed to deploy classifier deletion configuration to site, and failed to roll back configuration for site
|
Keyword |
ROLLBACK_CLASSIFIER_DELETE_FAILED |
|
Message text |
Failed to roll back the classifier deleting configuration for site "$1". Reason: $2. The classifier information is as follows: $3 |
|
Variable fields |
$1: Site name. $2: Failure cause. $3: Classifier configuration. |
|
Severity level |
|
|
Example |
Failed to roll back the classifier deleting configuration for site "site1". Reason: Cannot reach the site. The classifier information is as follows: [ID=f02b1a2b-480f-474c-9547-b461a88f40ba, Name=21, Cloud Region Name=SuperController, Rules=[ [ID=fee1eeee-3d74-42e8-86ef-883aae06d061, Name=fee1eeee-3d74-42e8-86ef-883aae06d061, Protocol=ALL, Ip Version=IPV4, Source Ip=22.22.22.0/24, Destination Ip=11.11.11.0/24 ], [ID=2888e14b-2942-4ae5-960f-a33d0ed87d68, Name=2888e14b-2942-4ae5-960f-a33d0ed87d68, Protocol=ALL, Ip Version=IPV4, Source Ip=11.11.11.0/24, Destination Ip=11.11.11.0/24 ]] ] |
|
Explanation |
Failed to deploy the classifier deletion configuration to a site, and failed to roll back the configuration for the site. |
|
Recommended action |
Manually clear the residual configuration on the site. |
Failed to deploy classifier modification configuration to site, and failed to roll back configuration for site
|
Keyword |
ROLLBACK_CLASSIFIER_UPDATE_FAILED |
|
Message text |
Failed to classifier the router updating configuration for site "$1". Reason: $2. The classifier information is as follows: $3 |
|
Variable fields |
$1: Site name. $2: Failure cause. $3: Classifier configuration. |
|
Severity level |
|
|
Example |
Failed to roll back the classifier updating configuration for site "site1". Reason: Cannot reach the site. The classifier information is as follows: [ID=f02b1a2b-480f-474c-9547-b461a88f40ba, Name=21, Cloud Region Name=SuperController, Rules=[ [ID=fee1eeee-3d74-42e8-86ef-883aae06d061, Name=fee1eeee-3d74-42e8-86ef-883aae06d061, Protocol=ALL, Ip Version=IPV4, Source Ip=22.22.22.0/24, Destination Ip=11.11.11.0/24 ], [ID=2888e14b-2942-4ae5-960f-a33d0ed87d68, Name=2888e14b-2942-4ae5-960f-a33d0ed87d68, Protocol=ALL, Ip Version=IPV4, Source Ip=11.11.11.0/24, Destination Ip=11.11.11.0/24 ]] ] |
|
Explanation |
Failed to deploy the classifier modification configuration to a site, and failed to roll back the configuration for the site. |
|
Recommended action |
Manually clear the residual configuration on the site. |
Successfully added vRouter QoS policy for site by creating east-west traffic application on super controller
|
Keyword |
ROUTER_POLICY_ADD_SUCCESSED |
|
Message text |
Successfully added a router policy configuration for site "$1". The router policy information is as follows: $2 |
|
Variable fields |
$1: Site name. $2: vRouter QoS policy information. |
|
Severity level |
|
|
Example |
Successfully added a router policy configuration for site "148.200". The router policy information is as follows: [ID=null, Router ID=7b64e340-6d47-464a-b64e-6f89f7fca3b7, Tenant ID=9d6b6cb5-3159-4470-8d8e-2e244e7ab1d4, Cloud Region Name=SuperController, TrafficPolicies=[ [Policy ID=b93eacdc-b2f8-46c6-b433-d3c17f252f77, Policy Name=2111, Classifier ID=f02b1a2b-480f-474c-9547-b461a88f40ba, Direction=IN ]] ] |
|
Explanation |
Successfully added a vRouter QoS policy for a site by creating an east-west traffic application on the super controller. |
|
Recommended action |
No action is required. |
Failed to add vRouter QoS policy for site by creating east-west traffic application on super controller
|
Keyword |
ROUTER_POLICY_ADD_FAILED |
|
Message text |
Failed to add a router policy configuration for site "$1". Reason: $2. The router policy information is as follows: $2 |
|
Variable fields |
$1: Site name. $2: Failure cause. $3: vRouter QoS policy information. |
|
Severity level |
|
|
Example |
Failed to add a router policy configuration for site "148.150". Reason: Internal error. The router policy information is as follows: [ID=null, Router ID=7b64e340-6d47-464a-b64e-6f89f7fca3b7, Tenant ID=9d6b6cb5-3159-4470-8d8e-2e244e7ab1d4, Cloud Region Name=SuperController, TrafficPolicies=[ [Policy ID=b93eacdc-b2f8-46c6-b433-d3c17f252f77, Policy Name=2111, Classifier ID=f02b1a2b-480f-474c-9547-b461a88f40ba, Direction=IN ]] ] |
|
Explanation |
Failed to add a vRouter QoS policy for a site by creating an east-west traffic application on the super controller. |
|
Recommended action |
Follow the prompt to resolve the problem. |
Successfully edited vRouter QoS policy for site by editing east-west traffic application on super controller
|
Keyword |
ROUTER_POLICY_UPDATE_SUCCESSED |
|
Message text |
Successfully updated a router policy configuration for site "$1". The router policy information is as follows: $2 |
|
Variable fields |
$1: Site name. $2: vRouter QoS policy information. |
|
Severity level |
|
|
Example |
Successfully updated a router policy configuration for site "148.150". The router policy information is as follows: [ID=null, Router ID=7b64e340-6d47-464a-b64e-6f89f7fca3b7, Tenant ID=9d6b6cb5-3159-4470-8d8e-2e244e7ab1d4, Cloud Region Name=SuperController, TrafficPolicies=[ [Policy ID=b93eacdc-b2f8-46c6-b433-d3c17f252f77, Policy Name=2111, Classifier ID=f02b1a2b-480f-474c-9547-b461a88f40ba, Direction=IN ]] ] |
|
Explanation |
Successfully edited a vRouter QoS policy for a site by editing an east-west traffic application on the super controller. |
|
Recommended action |
No action is required. |
Failed to edit vRouter QoS policy for site by editing east-west traffic application on super controller
|
Keyword |
ROUTER_POLICY_UPDATE_FAILED |
|
Message text |
Failed to update a router policy configuration for site "$1". Reason: $2. The router policy information is as follows: $3 |
|
Variable fields |
$1: Site name. $2: Failure cause. $3: vRouter QoS policy information. |
|
Severity level |
|
|
Example |
Failed to update a router policy configuration for site "148.150". Reason: Internal error. The router policy information is as follows: [ID=null, Router ID=7b64e340-6d47-464a-b64e-6f89f7fca3b7, Tenant ID=9d6b6cb5-3159-4470-8d8e-2e244e7ab1d4, Cloud Region Name=SuperController, TrafficPolicies=[ [Policy ID=b93eacdc-b2f8-46c6-b433-d3c17f252f77, Policy Name=2111, Classifier ID=f02b1a2b-480f-474c-9547-b461a88f40ba, Direction=IN ]] ] |
|
Explanation |
Failed to edit a vRouter QoS policy for a site by editing an east-west traffic application on the super controller. |
|
Recommended action |
Follow the prompt to resolve the problem. |
Successfully deleted vRouter QoS policy for site by deleting east-west traffic application on super controller
|
Keyword |
ROUTER_POLICY_DELETE_SUCCESSED |
|
Message text |
Successfully deleted a router policy configuration for site "$1". The router policy information is as follows: $2 |
|
Variable fields |
$1: Site name. $2: vRouter QoS policy information. |
|
Severity level |
|
|
Example |
Successfully deleted a router policy configuration for site "148.150". The router policy information is as follows: [ID=null, Router ID=7b64e340-6d47-464a-b64e-6f89f7fca3b7, Tenant ID=9d6b6cb5-3159-4470-8d8e-2e244e7ab1d4, Cloud Region Name=SuperController, TrafficPolicies=[ [Policy ID=b93eacdc-b2f8-46c6-b433-d3c17f252f77, Policy Name=2111, Classifier ID=f02b1a2b-480f-474c-9547-b461a88f40ba, Direction=IN ]] ] |
|
Explanation |
Successfully deleted a vRouter QoS policy for a site by deleting an east-west traffic application on the super controller. |
|
Recommended action |
No action is required. |
Failed to delete vRouter QoS policy for site by deleting east-west traffic application on super controller
|
Keyword |
ROUTER_POLICY_DELETE_FAILED |
|
Message text |
Failed to delete a router policy configuration for site "$1". Reason: $2. The router policy information is as follows: $3 |
|
Variable fields |
$1: Site name. $2: Failure cause. $3: vRouter QoS policy information. |
|
Severity level |
|
|
Example |
Failed to delete a router policy configuration for site "148.150". Reason: Internal error. The router policy information is as follows: [ID=null, Router ID=7b64e340-6d47-464a-b64e-6f89f7fca3b7, Tenant ID=9d6b6cb5-3159-4470-8d8e-2e244e7ab1d4, Cloud Region Name=SuperController, TrafficPolicies=[ [Policy ID=b93eacdc-b2f8-46c6-b433-d3c17f252f77, Policy Name=2111, Classifier ID=f02b1a2b-480f-474c-9547-b461a88f40ba, Direction=IN ]] ] |
|
Explanation |
Failed to delete a vRouter QoS policy for a site by deleting an east-west traffic application on the super controller. |
|
Recommended action |
Follow the prompt to resolve the problem. |
Failed to deploy vRouter QoS policy creation configuration to site, and successfully rolled back configuration for site
|
Keyword |
ROLLBACK_ROUTER_POLICY_ADD_SUCCESSED |
|
Message text |
Successfully rolled back the router policy adding configuration for site "$1". The router policy information is as follows: $2. |
|
Variable fields |
$1: Site name. $2: vRouter QoS policy information. |
|
Severity level |
|
|
Example |
Successfully rolled back the router policy adding configuration for site "148.150". The router policy information is as follows: [ID=null, Router ID=7b64e340-6d47-464a-b64e-6f89f7fca3b7, Tenant ID=9d6b6cb5-3159-4470-8d8e-2e244e7ab1d4, Cloud Region Name=SuperController, TrafficPolicies=[ [Policy ID=b93eacdc-b2f8-46c6-b433-d3c17f252f77, Policy Name=2111, Classifier ID=f02b1a2b-480f-474c-9547-b461a88f40ba, Direction=IN ]] ] |
|
Explanation |
Failed to deploy the vRouter QoS policy creation configuration to a site, and successfully rolled back the configuration for the site. |
|
Recommended action |
No action is required. |
Failed to deploy vRouter QoS policy deletion configuration to site, and successfully rolled back configuration for site
|
Keyword |
ROLLBACK_ROUTER_POLICY_DELETE_SUCCESSED |
|
Message text |
Successfully rolled back the router policy deleting configuration for site "$1". The router policy information is as follows: $2. |
|
Variable fields |
$1: Site name. $2: vRouter QoS policy information. |
|
Severity level |
|
|
Example |
Successfully rolled back the router policy deleting configuration for site "148.150". The router policy information is as follows: [ID=null, Router ID=7b64e340-6d47-464a-b64e-6f89f7fca3b7, Tenant ID=9d6b6cb5-3159-4470-8d8e-2e244e7ab1d4, Cloud Region Name=SuperController, TrafficPolicies=[ [Policy ID=b93eacdc-b2f8-46c6-b433-d3c17f252f77, Policy Name=2111, Classifier ID=f02b1a2b-480f-474c-9547-b461a88f40ba, Direction=IN ]] ] |
|
Explanation |
Failed to deploy the vRouter QoS policy deletion configuration to a site, and successfully rolled back the configuration for the site. |
|
Recommended action |
No action is required. |
Failed to deploy vRouter QoS policy modification configuration to site, and successfully rolled back configuration for site
|
Keyword |
ROLLBACK_ROUTER_POLICY_UPDATE_SUCCESSED |
|
Message text |
Successfully rolled back the router policy updating configuration for site "$1". The router policy information is as follows: $2. |
|
Variable fields |
$1: Site name. $2: vRouter QoS policy information. |
|
Severity level |
|
|
Example |
Successfully rolled back the router policy updating configuration for site "site1". The router policy information is as follows: [ID=null, Router ID=7b64e340-6d47-464a-b64e-6f89f7fca3b7, Tenant ID=9d6b6cb5-3159-4470-8d8e-2e244e7ab1d4, Cloud Region Name=SuperController, TrafficPolicies=[ [Policy ID=b93eacdc-b2f8-46c6-b433-d3c17f252f77, Policy Name=2111, Classifier ID=f02b1a2b-480f-474c-9547-b461a88f40ba, Direction=IN ]] ] |
|
Explanation |
Failed to deploy the vRouter QoS policy modification configuration to a site, and successfully rolled back the configuration for the site. |
|
Recommended action |
No action is required. |
Failed to deploy vRouter QoS policy creation configuration to site, and failed to roll back configuration for site
|
Keyword |
ROLLBACK_ROUTER_POLICY_ADD_FAILED |
|
Message text |
Failed to roll back the router policy adding configuration for site "$1". Reason: $2. The router policy information is as follows: $3. |
|
Variable fields |
$1: Site name. $2: Failure cause. $3: vRouter QoS policy information. |
|
Severity level |
|
|
Example |
Failed to roll back the router policy adding configuration for site "site1". Reason: Cannot reach the site. The router policy information is as follows: [ID=null, Router ID=7b64e340-6d47-464a-b64e-6f89f7fca3b7, Tenant ID=9d6b6cb5-3159-4470-8d8e-2e244e7ab1d4, Cloud Region Name=SuperController, TrafficPolicies=[ [Policy ID=b93eacdc-b2f8-46c6-b433-d3c17f252f77, Policy Name=2111, Classifier ID=f02b1a2b-480f-474c-9547-b461a88f40ba, Direction=IN ]] ] |
|
Explanation |
Failed to deploy the vRouter QoS policy creation configuration to a site, and failed to roll back the configuration for the site. |
|
Recommended action |
Manually clear the residual configuration on the site. |
Failed to deploy vRouter QoS policy deletion configuration to site, and failed to roll back configuration for site
|
Keyword |
ROLLBACK_ROUTER_POLICY_DELETE_FAILED |
|
Message text |
Failed to roll back the router policy deleting configuration for site "$1". Reason: $2. The router policy information is as follows: $3 |
|
Variable fields |
$1: Site name. $2: Failure cause. $3: vRouter QoS policy information. |
|
Severity level |
|
|
Example |
Failed to roll back the router policy deleting configuration for site "site1". Reason: Cannot reach the site. The router policy information is as follows: [ID=null, Router ID=7b64e340-6d47-464a-b64e-6f89f7fca3b7, Tenant ID=9d6b6cb5-3159-4470-8d8e-2e244e7ab1d4, Cloud Region Name=SuperController, TrafficPolicies=[ [Policy ID=b93eacdc-b2f8-46c6-b433-d3c17f252f77, Policy Name=2111, Classifier ID=f02b1a2b-480f-474c-9547-b461a88f40ba, Direction=IN ]] ] |
|
Explanation |
Failed to deploy the vRouter QoS policy deletion configuration to a site, and failed to roll back the configuration for the site. |
|
Recommended action |
Manually clear the residual configuration on the site. |
Failed to deploy vRouter QoS policy modification configuration to site, and failed to roll back configuration for site
|
Keyword |
ROLLBACK_ROUTER_POLICY_UPDATE_FAILED |
|
Message text |
Failed to router policy the router updating configuration for site "$1". Reason: $2. The router policy information is as follows: $3 |
|
Variable fields |
$1: Site name. $2: Failure cause. $3: vRouter QoS policy information. |
|
Severity level |
|
|
Example |
Failed to roll back the router policy updating configuration for site "site1". Reason: Cannot reach the site. The router policy information is as follows: [ID=null, Router ID=7b64e340-6d47-464a-b64e-6f89f7fca3b7, Tenant ID=9d6b6cb5-3159-4470-8d8e-2e244e7ab1d4, Cloud Region Name=SuperController, TrafficPolicies=[ [Policy ID=b93eacdc-b2f8-46c6-b433-d3c17f252f77, Policy Name=2111, Classifier ID=f02b1a2b-480f-474c-9547-b461a88f40ba, Direction=IN ]] ] |
|
Explanation |
Failed to deploy the vRouter QoS policy modification configuration to a site, and failed to roll back the configuration for the site. |
|
Recommended action |
Manually clear the residual configuration on the site. |
EBGP_CONNECTION
This section contains EBGP connection messages generated during the EBGP peer relationship deployment from the controller to fabrics.
Successful adding of EBGP connection
|
Keyword |
EBGP_CONNECTION_ADD_SUCCESSED |
|
Message text |
Successfully added an EBGP connection configuration in site "$1". The EBGP connection information is as follows: $2 |
|
Variable fields |
$1: Site name. |
|
Severity level |
|
|
Example |
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'} |
|
Explanation |
Successfully added an EBGP peer for a site on the super controller. |
|
Recommended action |
No action is required. |
Failure in adding EBGP connection
|
Keyword |
EBGP_CONNECTION_ADD_FAILED |
|
Message text |
Failed to add an EBGP connection configuration in site "$1". Reason: $2.The EBGP connection information is as follows: $3 |
|
Variable fields |
$1: Site name. $2: Reason for the failure. $3: EBGP connection information. |
|
Severity level |
|
|
Example |
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'} |
|
Explanation |
Failed to add an EBGP peer for a site on the super controller. |
|
Recommended action |
Follow the prompt to resolve the problem. |
Successful deletion of EBGP connection
|
Keyword |
EBGP_CONNECTION_DELETE_SUCCESSED |
|
Message text |
Successfully deleted an EBGP connection configuration in site "$1". The EBGP connection information is as follows: $2 |
|
Variable fields |
$1: Site name. $2: EBGP connection information. |
|
Severity level |
|
|
Example |
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'} |
|
Explanation |
Successfully deleted an EBGP peer for a site on the super controller. |
|
Recommended action |
No action is required. |
Failure in deleting EBGP connection
|
Keyword |
EBGP_CONNECTION_DELETE_FAILED |
|
Message text |
Failed to delete an EBGP connection configuration in site "$1". Reason: $2.The EBGP connection information is as follows: $3 |
|
Variable fields |
$1: Site name. $3: EBGP connection information. |
|
Severity level |
|
|
Example |
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'} |
|
Explanation |
Failed to delete an EBGP peer for a site on the super controller. |
|
Recommended action |
Successful rollback upon a failure in adding EBGP connection
|
Keyword |
ROLLBACK_EBGP_CONNECTION_ADD_SUCCESSED |
|
Message text |
Successfully rolled back the EBGP connection deleting configuration for site "$1". The EBGP connection information is as follows: $2 |
|
Variable fields |
$1: Site name. $2: EBGP connection information. |
|
Severity level |
|
|
Example |
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'} |
|
Explanation |
Successfully rolled back the configuration after a failure in adding EBGP connection. |
|
Recommended action |
No action is required. |
Failed rollback upon a failure in adding EBGP connection
|
Keyword |
ROLLBACK_EBGP_CONNECTION_ADD_FAILED |
|
Message text |
Failed to roll back the EBGP connection deleting configuration for site "$1". Reason: $2. The EBGP connection information is as follows: $3 |
|
Variable fields |
$1: Site name. $2: Reason for the failure. $3: EBGP connection information. |
|
Severity level |
|
|
Example |
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'} |
|
Explanation |
Failed to roll back the configuration after a failure in adding EBGP connection. |
|
Recommended action |
Follow the prompt to resolve the problem. |
LICENSE
This section contains license management messages.
Insufficient quantity-based licenses
|
Keyword |
LICENSE_INSUFFICIENT |
|
Message text |
Insufficient $1 licenses. Please purchase more licenses. |
|
Variable fields |
$1: Name of the quantity-based licenses. |
|
Severity level |
|
|
Example |
Insufficient siteNodeNum licenses. Please purchase more licenses. |
|
Explanation |
Quantity-based licenses are insufficient. |
|
Recommended action |
Purchase more licenses. |
No quantity-based licenses
|
Keyword |
LICENSE_USED_UP |
|
Message text |
$1 licenses have been used up. Please purchase more licenses. |
|
Variable fields |
$1: Type of the quantity-based licenses. |
|
Severity level |
|
|
Example |
SiteNodeNum licenses have been used up. Please purchase more licenses. |
|
Explanation |
Quantity-based licenses have been used up. |
|
Recommended action |
Purchase more licenses as required. |
NETWORK
This section contains vNetwork messages generated during the synchronization between the super controller and sites.
Successful adding of vNetwork
|
Keyword |
NETWORK_ADD_SUCCESSED |
|
Message text |
|
|
Variable fields |
$1: Site name. $2: VNetwork information. |
|
Severity level |
|
|
Example |
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] |
|
Explanation |
Successfully added a vNetwork in a site through the super controller. |
|
Recommended action |
No action is required. |
Failure in adding vNetwork
|
Keyword |
NETWORK_ADD_FAILED |
|
Message text |
Failed to add a network configuration in site ”$1”. Reason: $2. The network configuration information is as follows: $3 |
|
Variable fields |
$1: Site name. $2: Failure reason. $3: VNetwork information. |
|
Severity level |
|
|
Example |
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] |
|
Explanation |
Failed to add a vNetwork in a site through the super controller. |
|
Recommended action |
Follow the prompt to resolve the problem. |
Successful update of vNetwork
|
Keyword |
NETWORK_UPDATE_SUCCESSED |
|
Message text |
Successfully updated a network configuration in site ”$1”. The network configuration information is as follows: $2 |
|
Variable fields |
$1: Site name. $2: VNetwork information. |
|
Severity level |
|
|
Example |
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] |
|
Explanation |
Successfully updated a vNetwork in a site through the super controller. |
|
Recommended action |
No action is required. |
Failure in updating vNetwork
|
Keyword |
NETWORK_UPDATE_FAILED |
|
Message text |
Failed to update a network configuration in site ”$1”. Reason: $2. The network configuration information is as follows: $3 |
|
Variable fields |
$1: Site name. $2: Failure reason. $3: VNetwork information. |
|
Severity level |
|
|
Example |
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] |
|
Explanation |
Failed to update a vNetwork in a site through the super controller. |
|
Recommended action |
Follow the prompt to resolve the problem. |
Successful deletion of vNetwork
|
Keyword |
NETWORK_DELETE_SUCCESSED |
|
Message text |
Successfully deleted a network configuration in site ”$1”. The network configuration information is as follows: $2 |
|
Variable fields |
$1: Site name. $2: VNetwork information. |
|
Severity level |
|
|
Example |
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] |
|
Explanation |
Successfully deleted a vNetwork in a site through the super controller. |
|
Recommended action |
No action is required. |
Failure in deleting vNetwork
|
Keyword |
NETWORK_DELETE_FAILED |
|
Message text |
Failed to delete a network configuration in site ”$1”. Reason: $2. The network configuration information is as follows: $3 |
|
Variable fields |
$1: Site name. $2: Failure reason. $3: VNetwork information. |
|
Severity level |
|
|
Example |
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] |
|
Explanation |
Failed to delete a vNetwork in a site through the super controller. |
|
Recommended action |
Follow the prompt to resolve the problem. |
Failure in synchronizing vNetwork settings from site
|
Keyword |
CONTROLLED_SITE |
|
Message text |
Failed to synchronize settings from site ”$1”. Settings failed to be synchronized: $2 |
|
Variable fields |
$1: Site name. $2: VNetwork information. |
|
Example |
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] |
|
Explanation |
The super controller failed to synchronize vNetwork settings from a site. |
|
Recommended action |
Resolve the problem based on the operation log. |
Successful rollback of vNetwork adding configuration
|
Keyword |
ROLLBACK_NETWORK_ADD_SUCCESSED |
|
Message text |
Successfully rolled back the network adding configuration for site "$1". The network information is as follows: $2. |
|
Variable fields |
$1: Site name. $2: VNetwork settings. |
|
Severity level |
|
|
Example |
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] |
|
Explanation |
Configuration rollback succeeded after failure to issue vNetwork adding configuration to the site. |
|
Recommended action |
No action is required. |
Successful rollback of vNetwork updating configuration
|
Keyword |
ROLLBACK_NETWORK_UPDATE_SUCCESSED |
|
Message text |
Successfully rolled back the network updating configuration for site "$1". The network information is as follows: $2. |
|
Variable fields |
$1: Site name. $2: VNetwork settings. |
|
Severity level |
|
|
Example |
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] |
|
Explanation |
Configuration rollback succeeded after failure to issue vNetwork updating configuration to the site. |
|
Recommended action |
No action is required. |
Successful rollback of vNetwork deletion configuration
|
Keyword |
ROLLBACK_NETWORK_DELETE_SUCCESSED |
|
Message text |
Successfully rolled back the network deleting configuration for site "$1". The network information is as follows: $2. |
|
Variable fields |
$1: Site name. $2: VNetwork settings. |
|
Severity level |
|
|
Example |
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] |
|
Explanation |
Configuration rollback succeeded after failure to issue vNetwork deletion configuration to the site. |
|
Recommended action |
No action is required. |
Rollback failure of vNetwork adding configuration
|
Keyword |
ROLLBACK_NETWORK_ADD_FAILED |
|
Message text |
Failed to roll back the network adding configuration for site "$1". Reason: $2. The network information is as follows: $3. |
|
Variable fields |
$1: Site name. $2: Failure reason. $3: VNetwork settings. |
|
Severity level |
|
|
Example |
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] |
|
Explanation |
Configuration rollback failed after failure to issue vNetwork adding configuration to the site. |
|
Recommended action |
As a best practice, manually delete residual configuration from the site. |
Rollback failure of vNetwork updating configuration
|
Keyword |
ROLLBACK_NETWORK_UPDATE_FAILED |
|
Message text |
Failed to roll back the network updating configuration for site "$1". Reason: $2. The network information is as follows: $3. |
|
Variable fields |
$1: Site name. $2: Failure reason. $3: VNetwork settings. |
|
Severity level |
|
|
Example |
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] |
|
Explanation |
Configuration rollback failed after failure to issue vNetwork updating configuration to the site. |
|
Recommended action |
As a best practice, manually delete residual configuration from the site. |
Rollback failure of vNetwork deletion configuration
|
Keyword |
ROLLBACK_NETWORK_DELETE_FAILED |
|
Message text |
Failed to roll back the network deleting configuration for site "$1". Reason: $2. The network information is as follows: $3. |
|
Variable fields |
$1: Site name. $2: Failure reason. $3: VNetwork settings. |
|
Severity level |
|
|
Example |
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] |
|
Explanation |
Configuration rollback failed after failure to issue vNetwork deletion configuration to the site. |
|
Recommended action |
As a best practice, manually delete residual configuration from the site. |
PUBLIC_CLOUD
This section contains public cloud management and orchestration messages.
Created VPC on AWS successfully
|
Keyword |
ADD_VPC_OP |
|
Message text |
Created VPC $1 on the public cloud successfully. |
|
Variable fields |
$1: VPC name. |
|
Severity level |
|
|
Example |
Created VPC vpc001 on the public cloud successfully. |
|
Explanation |
The controller created a VPC on AWS successfully. |
|
Recommended action |
No action is required. |
Failed to create VPC on AWS
|
Keyword |
ADD_VPC_OP |
|
Message text |
Failed to create VPC $1 on the public cloud. Reason: $2 |
|
Variable fields |
$1: VPC name. $2: Failure cause. |
|
Severity level |
|
|
Example |
Failed to create VPC vpc001 on the public cloud. Reason: Failed to request data from Amazon Web Services. |
|
Explanation |
The controller failed to create a VPC on AWS. |
|
Recommended action |
Resolve the issue based on the prompt. |
Edited VPC on AWS successfully
|
Keyword |
UPDATE_VPC_OP |
|
Message text |
Updated VPC $1 on the public cloud successfully. |
|
Variable fields |
$1: VPC name. |
|
Severity level |
|
|
Example |
Updated VPC vpc001 on the public cloud successfully. |
|
Explanation |
The controller edited a VPC on AWS successfully. |
|
Recommended action |
No action is required. |
Failed to edit VPC on AWS
|
Keyword |
UPDATE_VPC_OP |
|
Message text |
Failed to update VPC $1 on the public cloud. Reason:$2 |
|
Variable fields |
$1: VPC name. $2: Failure cause. |
|
Severity level |
|
|
Example |
Failed to update VPC vpc001 on the public cloud. Reason: Failed to request data from Amazon Web Services. |
|
Explanation |
The controller failed to edit a VPC on AWS. |
|
Recommended action |
Resolve the issue based on the prompt. |
Deleted VPC from AWS successfully
|
Keyword |
DEL_VPC_OP |
|
Message text |
Deleted VPC $1 from the public cloud successfully. |
|
Variable fields |
$1: VPC name. |
|
Severity level |
|
|
Example |
Deleted VPC vpc001 from the public cloud successfully. |
|
Explanation |
The controller deleted a VPC from AWS successfully. |
|
Recommended action |
No action is required. |
Failed to delete VPC from AWS
|
Keyword |
DEL_VPC_OP |
|
Message text |
Failed to delete VPC $1 from the public cloud. Reason: $2 |
|
Variable fields |
$1: VPC name. $2: Failure cause. |
|
Severity level |
|
|
Example |
Failed to delete VPC vpc001 from the public cloud. Reason: Failed to request data from Amazon Web Services. |
|
Explanation |
The controller failed to delete a VPC from AWS. |
|
Recommended action |
Resolve the issue based on the prompt. |
Queried VPC from AWS successfully
|
Keyword |
QUERY_VPC_OP |
|
Message text |
Queried VPC $1 from the public cloud successfully. |
|
Variable fields |
$1: VPC name. |
|
Severity level |
|
|
Example |
Queried VPC vpc001 from the public cloud successfully. |
|
Explanation |
The controller queried a VPC from AWS successfully. |
|
Recommended action |
No action is required. |
Failed to query VPC from AWS
|
Keyword |
QUERY_VPC_OP |
|
Message text |
Failed to query VPC $1 from the public cloud. Reason: $2 |
|
Variable fields |
$1: VPC name. $2: Failure cause. |
|
Severity level |
|
|
Example |
Failed to query VPC vpc001 from the public cloud. Reason: Failed to request data from Amazon Web Services. |
|
Explanation |
The controller failed to query a VPC from AWS. |
|
Recommended action |
Resolve the issue based on the prompt. |
Created IPv4 CIDR for VPC on AWS successfully
|
Keyword |
ADD_VPC_CIDR_OP |
|
Message text |
Created IPv4 CIDR $1 in VPC $2 successfully. |
|
Variable fields |
$1: IPv4 CIDR name. $2: VPC name. |
|
Severity level |
|
|
Example |
Created IPv4 CIDR 10.10.10.0/24 in VPC vpc001 successfully. |
|
Explanation |
The controller created an IPv4 CIDR for a VPC on AWS successfully. |
|
Recommended action |
No action is required. |
Failed to create IPv4 CIDR for VPC on AWS
|
Keyword |
ADD_VPC_CIDR_OP |
|
Message text |
Failed to create IPv4 CIDR $1 in VPC $2. Reason: $3 |
|
Variable fields |
$1: IPv4 CIDR name. $2: VPC name. $3: Failure cause. |
|
Severity level |
|
|
Example |
Failed to create IPv4 CIDR 10.10.10.0/24 in VPC vpc001. Reason: Failed to request data from Amazon Web Services. |
|
Explanation |
The controller failed to create an IPv4 CIDR for a VPC on AWS. |
|
Recommended action |
Resolve the issue based on the prompt. |
Created IPv6 CIDR for VPC on AWS successfully
|
Keyword |
ADD_VPC_CIDR_OP |
|
Message text |
Created IPv6 CIDR $1 in VPC $2 successfully. |
|
Variable fields |
$1: IPv6 CIDR name. $2: VPC name. |
|
Severity level |
|
|
Example |
Created IPv6 CIDR 1001::1000/64 in VPC vpc001 successfully. |
|
Explanation |
The controller created an IPv6 CIDR for a VPC on AWS successfully. |
|
Recommended action |
No action is required. |
Failed to create IPv6 CIDR for VPC on AWS
|
Keyword |
ADD_VPC_CIDR_OP |
|
Message text |
Failed to create IPv6 CIDR $1 in VPC $2. Reason: $3 |
|
Variable fields |
$1: IPv6 CIDR name. $2: VPC name. $3: Failure cause. |
|
Severity level |
|
|
Example |
Failed to create IPv6 CIDR 1001::1000/64 in VPC vpc001. Reason: Failed to request data from Amazon Web Services. |
|
Explanation |
The controller failed to create an IPv6 CIDR for a VPC on AWS. |
|
Recommended action |
Resolve the issue based on the prompt. |
Deleted IPv4 CIDR from VPC on AWS successfully
|
Keyword |
DEL_VPC_CIDR_OP |
|
Message text |
Deleted IPv4 CIDR $1 from VPC $2 successfully. |
|
Variable fields |
$1: IPv4 CIDR name. $2: VPC name. |
|
Severity level |
|
|
Example |
Deleted IPv4 CIDR 10.10.10.0/24 from VPC vpc001 successfully. |
|
Explanation |
The controller deleted an IPv4 CIDR from a VPC on AWS successfully. |
|
Recommended action |
No action is required. |
Failed to delete IPv4 CIDR from VPC on AWS
|
Keyword |
DEL_VPC_CIDR_OP |
|
Message text |
Failed to delete IPv4 CIDR $1 from VPC $2. Reason: $3 |
|
Variable fields |
$1: IPv4 CIDR name. $2: VPC name. $3: Failure cause. |
|
Severity level |
|
|
Example |
Failed to delete IPv4 CIDR 10.10.10.0/24 from VPC vpc001. Reason: Failed to request data from Amazon Web Services. |
|
Explanation |
The controller failed to delete an IPv4 CIDR from a VPC on AWS. |
|
Recommended action |
Resolve the issue based on the prompt. |
Deleted IPv6 CIDR from VPC on AWS successfully
|
Keyword |
DEL_VPC_CIDR_OP |
|
Message text |
Deleted IPv6 CIDR $1 from VPC $2 successfully. |
|
Variable fields |
$1: IPv6 CIDR name. $2: VPC name. |
|
Severity level |
|
|
Example |
Deleted IPv6 CIDR 1001::1000/64 from VPC vpc001 successfully. |
|
Explanation |
The controller deleted an IPv6 CIDR from a VPC on AWS successfully. |
|
Recommended action |
No action is required. |
Failed to delete IPv6 CIDR from VPC on AWS
|
Keyword |
DEL_VPC_CIDR_OP |
|
Message text |
Failed to delete IPv6 CIDR $1 from VPC $2. Reason: $3 |
|
Variable fields |
$1: IPv6 CIDR name. $2: VPC name. $3: Failure cause. |
|
Severity level |
|
|
Example |
Failed to delete IPv6 CIDR 1001::1000/64 from VPC vpc001. Reason: Failed to request data from Amazon Web Services. |
|
Explanation |
The controller failed to delete an IPv6 CIDR from a VPC on AWS. |
|
Recommended action |
Resolve the issue based on the prompt. |
Queried regions from AWS successfully
|
Keyword |
QUERY_REGION_OP |
|
Message text |
Queried regions from the public cloud successfully. |
|
Variable fields |
N/A |
|
Severity level |
|
|
Example |
Queried regions from the public cloud successfully. |
|
Explanation |
The controller queried regions from AWS successfully. |
|
Recommended action |
No action is required. |
Failed to query regions from AWS
|
Keyword |
QUERY_REGION_OP |
|
Message text |
Failed to query regions from the public cloud. Reason: $1 |
|
Variable fields |
$1: Failure cause. |
|
Severity level |
|
|
Example |
Failed to query regions from the public cloud. Reason: Failed to request data from Amazon Web Services. |
|
Explanation |
The controller failed to query regions from AWS. |
|
Recommended action |
Resolve the issue based on the prompt. |
Queried authentication information from AWS successfully
|
Keyword |
CHECK_ACCOUNT_OP |
|
Message text |
Got access keys of account $1 from the public cloud successfully. |
|
Variable fields |
$1: Account information. |
|
Severity level |
|
|
Example |
Got access keys of account 490509281347(yy@sdn.com) from the public cloud successfully. |
|
Explanation |
The controller queried authentication information from AWS successfully. |
|
Recommended action |
No action is required. |
Failed to query authentication information from AWS
|
Keyword |
CHECK_ACCOUNT_OP |
|
Message text |
Failed to get access keys of account $1 from the public cloud. Reason: $2 |
|
Variable fields |
$1: Account information. $2: Failure cause. |
|
Severity level |
|
|
Example |
Failed to get access keys of account 490509281347(yy@sdn.com) from the public cloud. Reason: Failed to request data from Amazon Web Services. |
|
Explanation |
The controller failed to query authentication information from AWS. |
|
Recommended action |
Resolve the issue based on the prompt. |
Queried account information from AWS successfully
|
Keyword |
CHECK_ACCOUNT_OP |
|
Message text |
Got users of account $1 from the public cloud successfully. |
|
Variable fields |
$1: Account information. |
|
Severity level |
|
|
Example |
Got users of account 490509281347(yy@sdn.com) from the public cloud successfully. |
|
Explanation |
The controller queried account information from AWS successfully |
|
Recommended action |
No action is required. |
Failed to query account information from AWS
|
Keyword |
CHECK_ACCOUNT_OP |
|
Message text |
Failed to get users of account $1 from the public cloud. Reason: $2 |
|
Variable fields |
$1: Account information. $2: Failure cause. |
|
Severity level |
|
|
Example |
Failed to get users of account 490509281347(yy@sdn.com) from the public cloud. Reason: Failed to request data from Amazon Web Services. |
|
Explanation |
The controller failed to query account information from AWS. |
|
Recommended action |
Resolve the issue based on the prompt. |
Authenticated account on AWS successfully
|
Keyword |
AUTH_ACCOUNT_OP |
|
Message text |
Authenticated the account $1 successfully. |
|
Variable fields |
$1: Account information. |
|
Severity level |
|
|
Example |
Authenticated the account yy@sdn.com successfully. |
|
Explanation |
The controller authenticated an account on AWS successfully. |
|
Recommended action |
No action is required. |
Failed to authenticate account on AWS
|
Keyword |
AUTH_ACCOUNT_OP |
|
Message text |
Failed to authenticate the account $1. Reason: $2 |
|
Variable fields |
$1: Account information. $2: Failure cause. |
|
Severity level |
|
|
Example |
Failed to authenticate the account yy@sdn.com. Reason: Failed to request data from Amazon Web Services. |
|
Explanation |
The controller failed to authenticate an account on AWS. |
|
Recommended action |
Resolve the issue based on the prompt. |
Created Internet gateway on AWS successfully
|
Keyword |
ADD_GATEWAY_OP |
|
Message text |
Created Internet gateway $1 on the public cloud successfully. |
|
Variable fields |
$1: Name of the border gateway to the Internet. |
|
Severity level |
|
|
Example |
Created Internet gateway 1111 on the public cloud successfully. |
|
Explanation |
The controller created an Internet gateway on AWS successfully. |
|
Recommended action |
No action is required. |
Failed to create Internet gateway on AWS
|
Keyword |
ADD_GATEWAY_OP |
|
Message text |
Failed to create Internet gateway $1 on the public cloud. Reason: $2 |
|
Variable fields |
$1: Name of the border gateway to the Internet. $2: Failure cause. |
|
Severity level |
|
|
Example |
Failed to create Internet gateway 111 on the public cloud. Reason: Failed to request data from Amazon Web Services. |
|
Explanation |
The controller failed to create an Internet gateway on AWS. |
|
Recommended action |
Resolve the issue based on the prompt. |
Created egress-only Internet gateway on AWS successfully
|
Keyword |
ADD_GATEWAY_OP |
|
Message text |
Created egress-only Internet gateway $1 on the public cloud successfully |
|
Variable fields |
$1: Name of the egress-only Internet gateway. |
|
Severity level |
|
|
Example |
Created egress-only Internet gateway 1111 on the public cloud successfully. |
|
Explanation |
The controller created an egress-only Internet gateway on AWS successfully. |
|
Recommended action |
No action is required. |
Failed to create egress-only Internet gateway on AWS
|
Keyword |
ADD_GATEWAY_OP |
|
Message text |
Failed to create egress-only Internet gateway $1 on the public cloud. Reason: $2 |
|
Variable fields |
$1: Name of the egress-only Internet gateway. $2: Failure cause. |
|
Severity level |
|
|
Example |
Failed to create egress-only Internet gateway 111 on the public cloud. Reason: Failed to request data from Amazon Web Services. |
|
Explanation |
The controller failed to create an egress-only Internet gateway on AWS. |
|
Recommended action |
Resolve the issue based on the prompt. |
Edited border gateway on AWS successfully
|
Keyword |
UPDATE_GATEWAY_OP |
|
Message text |
Updated egress gateway $1 on the public cloud successfully |
|
Variable fields |
$1: Border gateway name. |
|
Severity level |
|
|
Example |
Updated egress gateway 1111 on the public cloud successfully |
|
Explanation |
The controller edited a border gateway on AWS successfully. |
|
Recommended action |
No action is required. |
Failed to edit border gateway on AWS
|
Keyword |
UPDATE_GATEWAY_OP |
|
Message text |
Failed to update egress gateway $1 on the public cloud. Reason: $2 |
|
Variable fields |
$1: Border gateway name. $2: Failure cause. |
|
Severity level |
|
|
Example |
Failed to update egress gateway 111 on the public cloud. Reason: Failed to request data from Amazon Web Services. |
|
Explanation |
The controller failed to edit a border gateway on AWS. |
|
Recommended action |
Resolve the issue based on the prompt. |
Deleted Internet gateway from AWS successfully
|
Keyword |
DEL_GATEWAY_OP |
|
Message text |
Deleted Internet gateway $1 from the public cloud successfully. |
|
Variable fields |
$1: Name of the border gateway to the Internet. |
|
Severity level |
|
|
Example |
Deleted Internet gateway 111 from the public cloud successfully. |
|
Explanation |
The controller deleted an Internet gateway from AWS successfully. |
|
Recommended action |
No action is required. |
Failed to delete Internet gateway from AWS
|
Keyword |
DEL_GATEWAY_OP |
|
Message text |
Failed to delete Internet gateway %s from the public cloud. Reason: $2 |
|
Variable fields |
$1: Name of the border gateway to the Internet. $2: Failure cause. |
|
Severity level |
|
|
Example |
Failed to delete Internet gateway 111 from the public cloud. Reason: Failed to request data from Amazon Web Services. |
|
Explanation |
The controller failed to delete an Internet gateway from AWS. |
|
Recommended action |
Resolve the issue based on the prompt. |
Deleted egress-only Internet gateway from AWS successfully
|
Keyword |
DEL_GATEWAY_OP |
|
Message text |
Deleted egress-only Internet gateway $1 from the public cloud successfully |
|
Variable fields |
$1: Name of the egress-only Internet gateway. |
|
Severity level |
|
|
Example |
Deleted egress-only Internet gateway 1111 from the public cloud successfully |
|
Explanation |
The controller deleted an egress-only Internet gateway from AWS successfully. |
|
Recommended action |
No action is required. |
Failed to delete egress-only Internet gateway from AWS
|
Keyword |
DEL_GATEWAY_OP |
|
Message text |
Failed to delete egress-only Internet gateway $1 from the public cloud. Reason: $2 |
|
Variable fields |
$1: Name of the egress-only Internet gateway. $2: Failure cause. |
|
Severity level |
|
|
Example |
Failed to delete egress-only Internet gateway 111 from the public cloud. Reason: Failed to request data from Amazon Web Services. |
|
Explanation |
The controller failed to delete an egress-only Internet gateway from AWS. |
|
Recommended action |
Resolve the issue based on the prompt. |
Created vRouter on AWS successfully
|
Keyword |
ADD_VROUTER_OP |
|
Message text |
Created vRouter $1 on the public cloud successfully |
|
Variable fields |
$1: vRouter name. |
|
Severity level |
|
|
Example |
Created vRouter 1111 on the public cloud successfully. |
|
Explanation |
The controller created a vRouter on AWS successfully. |
|
Recommended action |
No action is required. |
Failed to create vRouter on AWS
|
Keyword |
ADD_VROUTER_OP |
|
Message text |
Failed to create vRouter $1 on the public cloud. Reason: $2 |
|
Variable fields |
$1: vRouter name. $2: Failure cause. |
|
Severity level |
|
|
Example |
Failed to create vRouter111 on the public cloud. Reason: Failed to request data from Amazon Web Services. |
|
Explanation |
The controller failed to create a vRouter on AWS. |
|
Recommended action |
Resolve the issue based on the prompt. |
Edited vRouter on AWS successfully
|
Keyword |
UPDATE_VROUTER_OP |
|
Message text |
Updated vRouter $1 on the public cloud successfully |
|
Variable fields |
$1: vRouter name. |
|
Severity level |
|
|
Example |
Updated vRouter 1111 on the public cloud successfully. |
|
Explanation |
The controller edited a vRouter on AWS successfully. |
|
Recommended action |
No action is required. |
Failed to edit vRouter on AWS
|
Keyword |
UPDATE_VROUTER_OP |
|
Message text |
Failed to update vRouter $1 on the public cloud. Reason: $2 |
|
Variable fields |
$1: vRouter name. $2: Failure cause. |
|
Severity level |
|
|
Example |
Failed to update vRouter 111 on the public cloud. Reason: Failed to request data from Amazon Web Services. |
|
Explanation |
The controller failed to edit a vRouter on AWS. |
|
Recommended action |
Resolve the issue based on the prompt. |
Deleted vRouter from AWS successfully
|
Keyword |
DEL_VROUTER_OP |
|
Message text |
Deleted vRouter $1 from the public cloud successfully |
|
Variable fields |
$1: vRouter name. |
|
Severity level |
|
|
Example |
Deleted vRouter 1111 from the public cloud successfully. |
|
Explanation |
The controller deleted a vRouter from AWS successfully. |
|
Recommended action |
No action is required. |
Failed to delete vRouter from AWS
|
Keyword |
DEL_VROUTER_OP |
|
Message text |
Failed to delete vRouter $1 from the public cloud. Reason: $2 |
|
Variable fields |
$1: vRouter name. $2: Failure cause. |
|
Severity level |
|
|
Example |
Failed to delete vRouter 111 from the public cloud. Reason: Failed to request data from Amazon Web Services. |
|
Explanation |
The controller failed to delete a vRouter from AWS. |
|
Recommended action |
Resolve the issue based on the prompt. |
Created route entry on AWS successfully
|
Keyword |
ADD_ROUTER_ITEM_OP |
|
Message text |
Created route entry $1 on the public cloud successfully. |
|
Variable fields |
$1: Destination network of the route entry. |
|
Severity level |
|
|
Example |
Created route entry 1111 on the public cloud successfully. |
|
Explanation |
The controller created a route entry on AWS successfully. |
|
Recommended action |
No action is required. |
Failed to create route entry on AWS
|
Keyword |
ADD_ROUTER_ITEM_OP |
|
Message text |
Failed to create route entry $1 on the public cloud. Reason: $2 |
|
Variable fields |
$1: Destination network of the route entry. $2: Failure cause. |
|
Severity level |
|
|
Example |
Failed to create route entry 111 on the public cloud. Reason: Failed to request data from Amazon Web Services. |
|
Explanation |
The controller failed to create a route entry on AWS. |
|
Recommended action |
Resolve the issue based on the prompt. |
Deleted route entry from AWS successfully
|
Keyword |
DEL_ROUTER_ITEM_OP |
|
Message text |
Deleted route entry $1 from the public cloud successfully. |
|
Variable fields |
$1: Destination network of the route entry. |
|
Severity level |
|
|
Example |
Deleted route entry 1111 from the public cloud successfully. |
|
Explanation |
The controller deleted a route entry from AWS successfully. |
|
Recommended action |
No action is required. |
Failed to delete route entry from AWS
|
Keyword |
DEL_ROUTER_ITEM_OP |
|
Message text |
Failed to delete route entry $1 from the public cloud. Reason: $2 |
|
Variable fields |
$1: Destination network of the route entry. $2: Failure cause. |
|
Severity level |
|
|
Example |
Failed to delete route entry 111 from the public cloud. Reason: Failed to request data from Amazon Web Services. |
|
Explanation |
The controller failed to delete a route entry from AWS. |
|
Recommended action |
Resolve the issue based on the prompt. |
Created subnet on AWS successfully
|
Keyword |
ADD_SUBNET_OP |
|
Message text |
Created subnet $1 on the public cloud successfully. |
|
Variable fields |
$1: Subnet name. |
|
Severity level |
|
|
Example |
Created subnet 1111 on the public cloud successfully. |
|
Explanation |
The controller created a subnet on AWS successfully. |
|
Recommended action |
No action is required. |
Failed to create subnet on AWS
|
Keyword |
ADD_SUBNET_OP |
|
Message text |
Failed to create subnet $1 on the public cloud. Reason: $2 |
|
Variable fields |
$1: Subnet name. $2: Failure cause. |
|
Severity level |
|
|
Example |
Failed to create subnet 111 on the public cloud. Reason: Failed to request data from Amazon Web Services. |
|
Explanation |
The controller failed to create a subnet on AWS. |
|
Recommended action |
Resolve the issue based on the prompt. |
Edited subnet on AWS successfully
|
Keyword |
UPDATE_SUBNET_OP |
|
Message text |
Updated subnet $1 on the public cloud successfully. |
|
Variable fields |
$1: Subnet name. |
|
Severity level |
|
|
Example |
Updated subnet 1111 on the public cloud successfully. |
|
Explanation |
The controller edited a subnet on AWS successfully. |
|
Recommended action |
No action is required. |
Failed to edit subnet on AWS
|
Keyword |
UPDATE_SUBNET_OP |
|
Message text |
Failed to update subnet $1 on the public cloud. Reason: $2 |
|
Variable fields |
$1: Subnet name. $2: Failure cause. |
|
Severity level |
|
|
Example |
Failed to update subnet 111 on the public cloud. Reason: Failed to request data from Amazon Web Services. |
|
Explanation |
The controller failed to edit a subnet on AWS. |
|
Recommended action |
Resolve the issue based on the prompt. |
Deleted subnet from AWS successfully
|
Keyword |
DEL_SUBNET_OP |
|
Message text |
Deleted subnet $1 from the public cloud successfully. |
|
Variable fields |
$1: Subnet name. |
|
Severity level |
|
|
Example |
Deleted subnet 1111 from the public cloud successfully. |
|
Explanation |
The controller deleted a subnet from AWS successfully. |
|
Recommended action |
No action is required. |
Failed to delete subnet from AWS
|
Keyword |
DEL_SUBNET_OP |
|
Message text |
Failed to delete subnet $1 from the public cloud. Reason: $2 |
|
Variable fields |
$1: Subnet name. $2: Failure cause. |
|
Severity level |
|
|
Example |
Failed to delete subnet 111 from the public cloud. Reason: Failed to request data from Amazon Web Services. |
|
Explanation |
The controller failed to delete a subnet from AWS. |
|
Recommended action |
Resolve the issue based on the prompt. |
Created network ACL on AWS successfully
|
Keyword |
ADD_NETWORK_ACL_OP |
|
Message text |
Created network ACL $1 on the public cloud successfully. |
|
Variable fields |
$1: Network ACL name. |
|
Severity level |
|
|
Example |
Created network ACL vpc001 on the public cloud successfully. |
|
Explanation |
The controller created a network ACL on AWS successfully. |
|
Recommended action |
No action is required. |
Failed to create network ACL on AWS
|
Keyword |
ADD_NETWORK_ACL_OP |
|
Message text |
Failed to create network ACL $1 on the public cloud. Reason: $2 |
|
Variable fields |
$1: Network ACL name. $2: Failure cause. |
|
Severity level |
|
|
Example |
Failed to create network ACL vpc001 on the public cloud. Reason: Failed to request data from Amazon Web Services. |
|
Explanation |
The controller failed to create a network ACL on AWS. |
|
Recommended action |
Resolve the issue based on the prompt. |
Edited network ACL on AWS successfully
|
Keyword |
UPDATE_NETWORK_ACL_OP |
|
Message text |
Updated network ACL $1 on the public cloud successfully. |
|
Variable fields |
$1: Network ACL name. |
|
Severity level |
|
|
Example |
Updated network ACL vpc001 on the public cloud successfully. |
|
Explanation |
The controller edited a network ACL on AWS successfully. |
|
Recommended action |
No action is required. |
Failed to edit network ACL on AWS
|
Keyword |
UPDATE_NETWORK_ACL_OP |
|
Message text |
Failed to update network ACL $1 on the public cloud. Reason:$2 |
|
Variable fields |
$1: Network ACL name. $2: Failure cause. |
|
Severity level |
|
|
Example |
Failed to update network ACL vpc001 on the public cloud. Reason: Failed to request data from Amazon Web Services. |
|
Explanation |
The controller failed to edit a network ACL on AWS. |
|
Recommended action |
Resolve the issue based on the prompt. |
Deleted network ACL from AWS successfully
|
Keyword |
DEL_NETWORK_ACL_OP |
|
Message text |
Deleted network ACL $1 from the public cloud successfully. |
|
Variable fields |
$1: Network ACL name. |
|
Severity level |
|
|
Example |
Deleted network ACL vpc001 from the public cloud successfully. |
|
Explanation |
The controller deleted a network ACL from AWS successfully. |
|
Recommended action |
No action is required. |
Failed to delete network ACL from AWS
|
Keyword |
DEL_NETWORK_ACL_OP |
|
Message text |
Failed to delete network ACL $1 from the public cloud. Reason: $2 |
|
Variable fields |
$1: Network ACL name. $2: Failure cause. |
|
Severity level |
|
|
Example |
Failed to delete network ACL vpc001 from the public cloud. Reason: Failed to request data from Amazon Web Services. |
|
Explanation |
The controller failed to delete a network ACL from AWS. |
|
Recommended action |
Resolve the issue based on the prompt. |
Created network ACL rule on AWS successfully
|
Keyword |
ADD_NETWORK_ACL_ENTRY_OP |
|
Message text |
Created network ACL rule $1 on the public cloud successfully. |
|
Variable fields |
$1: Number of the network ACL rule. |
|
Severity level |
|
|
Example |
Created network ACL rule 11 on the public cloud successfully. |
|
Explanation |
The controller created a network ACL rule on AWS successfully. |
|
Recommended action |
No action is required. |
Failed to create network ACL rule on AWS
|
Keyword |
ADD_NETWORK_ACL_ENTRY_OP |
|
Message text |
Failed to create network ACL rule $1 on the public cloud. Reason: $2 |
|
Variable fields |
$1: Number of the network ACL rule. $2: Failure cause. |
|
Severity level |
|
|
Example |
Failed to create network ACL rule 11 on the public cloud. Reason: Failed to request data from Amazon Web Services. |
|
Explanation |
The controller failed to create a network ACL rule on AWS. |
|
Recommended action |
Resolve the issue based on the prompt. |
Deleted network ACL rule from AWS successfully
|
Keyword |
DEL_ NETWORK_ACL_ENTRY_OP |
|
Message text |
Deleted network ACL rule $1 from the public cloud successfully. |
|
Variable fields |
$1: Number of the network ACL rule. |
|
Severity level |
|
|
Example |
Deleted network ACL rule 11 from the public cloud successfully. |
|
Explanation |
The controller deleted a network ACL rule from AWS successfully. |
|
Recommended action |
No action is required. |
Failed to delete network ACL rule from AWS
|
Keyword |
DEL_ NETWORK_ACL_ENTRY_OP |
|
Message text |
Failed to delete network ACL rule $1 from the public cloud. Reason: $2 |
|
Variable fields |
$1: Number of the network ACL rule. $2: Failure cause. |
|
Severity level |
|
|
Example |
Failed to delete network ACL rule 11 from the public cloud. Reason: Failed to request data from Amazon Web Services. |
|
Explanation |
The controller failed to delete a network ACL rule from AWS. |
|
Recommended action |
Resolve the issue based on the prompt. |
Associated subnet with network ACL on AWS successfully
|
Keyword |
ASSOCIATE_SUBNET_NETWORK_ACL_OP |
|
Message text |
Associated subnet $1 with network ACL $2 on the public cloud successfully. |
|
Variable fields |
$1: Subnet name. $2: Network ACL name. |
|
Severity level |
|
|
Example |
Associated subnet subnet1 with network ACL acl1 on the public cloud successfully. |
|
Explanation |
The controller associated a subnet with a network ACL on AWS successfully. |
|
Recommended action |
No action is required. |
Failed to associate subnet with network ACL on AWS
|
Keyword |
ASSOCIATE_SUBNET_NETWORK_ACL_OP |
|
Message text |
Failed to associate subnet $1 with network ACL $2 on the public cloud. Reason: $3 |
|
Variable fields |
$1: Subnet name. $2: Network ACL name. $3: Failure cause. |
|
Severity level |
|
|
Example |
Failed to associate subnet subnet1 with network ACL acl1 on the public cloud. Reason: Failed to request data from Amazon Web Services. |
|
Explanation |
The controller failed to associate a subnet with a network ACL on AWS. |
|
Recommended action |
Resolve the issue based on the prompt. |
Created security group on AWS successfully
|
Keyword |
ADD_SECURITY_GROUP_OP |
|
Message text |
Created security group $1 on the public cloud successfully. |
|
Variable fields |
$1: Security group name. |
|
Severity level |
|
|
Example |
Created security group vpc001 on the public cloud successfully. |
|
Explanation |
The controller created a security group on AWS successfully. |
|
Recommended action |
No action is required. |
Failed to create security group on AWS
|
Keyword |
ADD_SECURITY_GROUP_OP |
|
Message text |
Failed to create security group $1 on the public cloud. Reason: $2 |
|
Variable fields |
$1: Security group name. $2: Failure cause. |
|
Severity level |
|
|
Example |
Failed to create security group vpc001 on the public cloud. Reason: Failed to request data from Amazon Web Services. |
|
Explanation |
The controller failed to create a security group on AWS. |
|
Recommended action |
Resolve the issue based on the prompt. |
Deleted security group from AWS successfully
|
Keyword |
DEL_SECURITY_GROUP_OP |
|
Message text |
Deleted security group $1 from the public cloud successfully. |
|
Variable fields |
$1: Security group name. |
|
Severity level |
|
|
Example |
Deleted security group vpc001 from the public cloud successfully. |
|
Explanation |
The controller deleted a security group from AWS successfully. |
|
Recommended action |
No action is required. |
Failed to delete security group from AWS
|
Keyword |
DEL_SECURITY_GROUP_OP |
|
Message text |
Failed to delete security group $1 from the public cloud. Reason: $2 |
|
Variable fields |
$1: Security group name. $2: Failure cause. |
|
Severity level |
|
|
Example |
Failed to delete security group vpc001 from the public cloud. Reason: Failed to request data from Amazon Web Services. |
|
Explanation |
The controller failed to delete a security group from AWS. |
|
Recommended action |
Resolve the issue based on the prompt. |
Created security group inbound rule on AWS successfully
|
Keyword |
ADD_SECURITY_GROUP_INBOUND_RULE_OP |
|
Message text |
Created security group inbound rule $1 on the public cloud successfully. |
|
Variable fields |
$1: Name of the security group inbound rule. |
|
Severity level |
|
|
Example |
Created security group inbound rule 11 on the public cloud successfully. |
|
Explanation |
The controller created a security group inbound rule on AWS successfully. |
|
Recommended action |
No action is required. |
Failed to create security group inbound rule on AWS
|
Keyword |
ADD_SECURITY_GROUP_INBOUND_RULE_OP |
|
Message text |
Failed to create security group inbound rule $1 on the public cloud. Reason: $2 |
|
Variable fields |
$1: Name of the security group inbound rule. $2: Failure cause. |
|
Severity level |
|
|
Example |
Failed to create security group inbound rule 11 on the public cloud. Reason: Failed to request data from Amazon Web Services. |
|
Explanation |
The controller failed to create a security group inbound rule on AWS. |
|
Recommended action |
Resolve the issue based on the prompt. |
Deleted security group inbound rule from AWS successfully
|
Keyword |
DEL_ SECURITY_GROUP_INBOUND_RULE_OP |
|
Message text |
Deleted security group inbound rule $1 from the public cloud successfully. |
|
Variable fields |
$1: Name of the security group inbound rule. |
|
Severity level |
|
|
Example |
Deleted security group inbound rule 11 from the public cloud successfully. |
|
Explanation |
The controller deleted a security group inbound rule from AWS successfully. |
|
Recommended action |
No action is required. |
Failed to delete security group inbound rule from AWS
|
Keyword |
DEL_ SECURITY_GROUP_INBOUND_RULE_OP |
|
Message text |
Failed to delete security group inbound rule $1 from the public cloud. Reason: $2 |
|
Variable fields |
$1: Name of the security group inbound rule. $2: Failure cause. |
|
Severity level |
|
|
Example |
Failed to delete security group inbound rule 11 from the public cloud. Reason: Failed to request data from Amazon Web Services. |
|
Explanation |
The controller failed to delete a security group inbound rule from AWS. |
|
Recommended action |
Resolve the issue based on the prompt. |
Created security group outbound rule on AWS successfully
|
Keyword |
ADD_SECURITY_GROUP_OUTBOUND_RULE_OP |
|
Message text |
Created security group outbound rule $1 on the public cloud successfully. |
|
Variable fields |
$1: Name of the security group outbound rule. |
|
Severity level |
|
|
Example |
Created security group outbound rule 11 on the public cloud successfully. |
|
Explanation |
The controller created a security group outbound rule on AWS successfully. |
|
Recommended action |
No action is required. |
Failed to create security group outbound rule on AWS
|
Keyword |
ADD_SECURITY_GROUP_OUTBOUND_RULE_OP |
|
Message text |
Failed to create security group outbound rule $1 on the public cloud. Reason: $2 |
|
Variable fields |
$1: Name of the security group outbound rule. $2: Failure cause. |
|
Severity level |
|
|
Example |
Failed to create security group outbound rule 11 on the public cloud. Reason: Failed to request data from Amazon Web Services. |
|
Explanation |
The controller failed to create a security group outbound rule on AWS. |
|
Recommended action |
Resolve the issue based on the prompt. |
Deleted security group outbound rule from AWS successfully
|
Keyword |
DEL_ SECURITY_GROUP_OUTBOUND_RULE_OP |
|
Message text |
Deleted security group outbound rule $1 from the public cloud successfully. |
|
Variable fields |
$1: Name of the security group outbound rule. |
|
Severity level |
|
|
Example |
Deleted security group outbound rule 11 from the public cloud successfully. |
|
Explanation |
The controller deleted a security group outbound rule from AWS successfully. |
|
Recommended action |
No action is required. |
Failed to delete security group outbound rule from AWS
|
Keyword |
DEL_ SECURITY_GROUP_OUTBOUND_RULE_OP |
|
Message text |
Failed to delete security group outbound rule $1 from the public cloud. Reason: $2 |
|
Variable fields |
$1: Name of the security group outbound rule. $2: Failure cause. |
|
Severity level |
|
|
Example |
Failed to delete security group outbound rule 11 from the public cloud. Reason: Failed to request data from Amazon Web Services. |
|
Explanation |
The controller failed to delete a security group outbound rule from AWS. |
|
Recommended action |
Resolve the issue based on the prompt. |
Edited security group rule name on AWS successfully
|
Keyword |
UPDATE_SECURITY_GROUP_RULE_OP |
|
Message text |
Updated security group rule name $1 on the public cloud successfully. |
|
Variable fields |
$1: Security group rule name. |
|
Severity level |
|
|
Example |
Updated security group rule name sc001 on the public cloud successfully. |
|
Explanation |
The controller edited a security group rule name on AWS successfully. |
|
Recommended action |
No action is required. |
Failed to edit security group rule name on AWS
|
Keyword |
UPDATE_SECURITY_GROUP_RULE_OP |
|
Message text |
Failed to update security group rule name $1 on the public cloud. Reason: $2 |
|
Variable fields |
$1: Security group rule name. $2: Failure cause. |
|
Severity level |
|
|
Example |
Failed to update security group rule name vpc001 on the public cloud. Reason: Failed to request data from Amazon Web Services. |
|
Explanation |
The controller failed to edit a security group rule name on AWS. |
|
Recommended action |
Resolve the issue based on the prompt. |
Created endpoint node on AWS successfully
|
Keyword |
ADD_ENDPOINT_OP |
|
Message text |
Created endpoint $1 on the public cloud successfully. |
|
Variable fields |
$1: Endpoint node name. |
|
Severity level |
|
|
Example |
Created endpoint endpoint001 on the public cloud successfully. |
|
Explanation |
The controller created an endpoint node on AWS successfully. |
|
Recommended action |
No action is required. |
Failed to create endpoint node on AWS
|
Keyword |
ADD_ENDPOINT_OP |
|
Message text |
Failed to create endpoint $1 on the public cloud. Reason: $2 |
|
Variable fields |
$1: Endpoint node name. $2: Failure cause. |
|
Severity level |
|
|
Example |
Failed to create endpoint endpoint001 on the public cloud. Reason: Failed to request data from Amazon Web Services. |
|
Explanation |
The controller failed to create an endpoint node on AWS. |
|
Recommended action |
Resolve the issue based on the prompt. |
Edited endpoint node on AWS successfully
|
Keyword |
UPDATE_ENDPOINT_OP |
|
Message text |
Updated endpoint $1 on the public cloud successfully. |
|
Variable fields |
$1: Endpoint node name. |
|
Severity level |
|
|
Example |
Updated endpoint endpoint001 on the public cloud successfully. |
|
Explanation |
The controller edited an endpoint node on AWS successfully. |
|
Recommended action |
No action is required. |
Failed to edit endpoint node on AWS
|
Keyword |
UPDATE_ENDPOINT_OP |
|
Message text |
Failed to update endpoint $1 on the public cloud. Reason:$2 |
|
Variable fields |
$1: Endpoint node name. $2: Failure cause. |
|
Severity level |
|
|
Example |
Failed to update endpoint endpoint001 on the public cloud. Reason: Failed to request data from Amazon Web Services. |
|
Explanation |
The controller failed to edit an endpoint node on AWS. |
|
Recommended action |
Resolve the issue based on the prompt. |
Deleted endpoint node from AWS successfully
|
Keyword |
DEL_ENDPOINT_OP |
|
Message text |
Deleted endpoint $1 from the public cloud successfully. |
|
Variable fields |
$1: Endpoint node name. |
|
Severity level |
|
|
Example |
Deleted endpoint endpoint001 from the public cloud successfully. |
|
Explanation |
The controller deleted an endpoint node from AWS successfully. |
|
Recommended action |
No action is required. |
Failed to delete endpoint node from AWS
|
Keyword |
DEL_ENDPOINT_OP |
|
Message text |
Failed to delete endpoint $1 from the public cloud. Reason: $2 |
|
Variable fields |
$1: Endpoint node name. $2: Failure cause. |
|
Severity level |
|
|
Example |
Failed to delete endpoint endpoint001 from the public cloud. Reason: Failed to request data from Amazon Web Services. |
|
Explanation |
The controller failed to delete an endpoint node from AWS. |
|
Recommended action |
Resolve the issue based on the prompt. |
Synchronized AZ resources from AWS successfully
|
Keyword |
SYNC_RESOURCE |
|
Message text |
Synced AZ resources from region $1 successfully. |
|
Variable fields |
$1: Region name. |
|
Severity level |
|
|
Example |
Synced AZ resources from region us-east-2 successfully. |
|
Explanation |
The controller synchronized AZ resources from a region on AWS successfully. |
|
Recommended action |
No action is required. |
Synchronized service resources from AWS successfully
|
Keyword |
SYNC_RESOURCE |
|
Message text |
Synced service resources from region $1 successfully. |
|
Variable fields |
$1: Region name. |
|
Severity level |
|
|
Example |
Synced service resources from region us-east-2 successfully. |
|
Explanation |
The controller synchronized service resources from a region on AWS successfully. |
|
Recommended action |
No action is required. |
Synchronized VPC resources from AWS successfully
|
Keyword |
SYNC_RESOURCE |
|
Message text |
Synced VPC resources from region $1 successfully. |
|
Variable fields |
$1: Region name. |
|
Severity level |
|
|
Example |
Synced VPC resources from region us-east-2 successfully. |
|
Explanation |
The controller synchronized VPC resources from a region on AWS successfully. |
|
Recommended action |
No action is required. |
Synchronized egress gateway resources from AWS successfully
|
Keyword |
SYNC_RESOURCE |
|
Message text |
Synced egress gateway resources from region $1 successfully. |
|
Variable fields |
$1: Region name. |
|
Severity level |
|
|
Example |
Synced egress gateway resources from region us-east-2 successfully. |
|
Explanation |
The controller synchronized egress gateway resources from a region on AWS successfully. |
|
Recommended action |
No action is required. |
Synchronized network ACL resources from AWS successfully
|
Keyword |
SYNC_RESOURCE |
|
Message text |
Synced network ACL resources from region $1 successfully. |
|
Variable fields |
$1: Region name. |
|
Severity level |
|
|
Example |
Synced network ACL resources from region us-east-2 successfully. |
|
Explanation |
The controller synchronized network ACL resources from a region on AWS successfully. |
|
Recommended action |
No action is required. |
Synchronized vRouter resources from AWS successfully
|
Keyword |
SYNC_RESOURCE |
|
Message text |
Synced vRouter resources from region $1 successfully. |
|
Variable fields |
$1: Region name. |
|
Severity level |
|
|
Example |
Synced vRouter resources from region us-east-2 successfully. |
|
Explanation |
The controller synchronized vRouter resources from a region on AWS successfully. |
|
Recommended action |
No action is required. |
Synchronized subnet resources from AWS successfully
|
Keyword |
SYNC_RESOURCE |
|
Message text |
Synced subnet resources from region $1 successfully. |
|
Variable fields |
$1: Region name. |
|
Severity level |
|
|
Example |
Synced subnet resources from region us-east-2 successfully. |
|
Explanation |
The controller synchronized subnet resources from a region on AWS successfully. |
|
Recommended action |
No action is required. |
Synchronized security group resources from AWS successfully
|
Keyword |
SYNC_RESOURCE |
|
Message text |
Synced security group resources from region $1 successfully. |
|
Variable fields |
$1: Region name. |
|
Severity level |
|
|
Example |
Synced security group resources from region us-east-2 successfully. |
|
Explanation |
The controller synchronized security group resources from a region on AWS successfully. |
|
Recommended action |
No action is required. |
Synchronized endpoint resources from AWS successfully
|
Keyword |
SYNC_RESOURCE |
|
Message text |
Synced endpoint resources from region $1 successfully. |
|
Variable fields |
$1: Region name. |
|
Severity level |
|
|
Example |
Synced endpoint resources from region us-east-2 successfully. |
|
Explanation |
The controller synchronized endpoint resources from a region on AWS successfully. |
|
Recommended action |
No action is required. |
Failed to synchronize resources from a region on AWS
|
Keyword |
SYNC_RESOURCE |
|
Message text |
Failed to sync resources from region $1. Reason:$2 |
|
Variable fields |
$1: Region name. $2: Failure cause. |
|
Severity level |
|
|
Example |
Failed to sync resources from region us-east-2. Reason: Failed to request data from Amazon Web Services. |
|
Explanation |
The controller failed to synchronize resources from a region on AWS. |
|
Recommended action |
Resolve the issue based on the prompt. |
Created transit gateway on AWS successfully
|
Keyword |
ADD_TRANSIT_GATEWAY_OP |
|
Message text |
Created transit gateway $1 on the public cloud successfully. |
|
Variable fields |
$1: Transit gateway name. |
|
Severity level |
|
|
Example |
Created transit gateway TGW1 on the public cloud successfully. |
|
Explanation |
The controller created a transit gateway on AWS successfully. |
|
Recommended action |
No action is required. |
Failed to create transit gateway on AWS
|
Keyword |
ADD_TRANSIT_GATEWAY_OP |
|
Message text |
Failed to create transit gateway $1 on the public cloud. Reason: $2 |
|
Variable fields |
$1: Transit gateway name. $2: Failure cause. |
|
Severity level |
|
|
Example |
Failed to create transit gateway TGW1 on the public cloud. Reason: Failed to request data from Amazon Web Services. |
|
Explanation |
The controller failed to create a transit gateway on AWS. |
|
Recommended action |
Resolve the issue based on the prompt. |
Edited transit gateway on AWS successfully
|
Keyword |
UPDATE_TRANSIT_GATEWAY_OP |
|
Message text |
Updated transit gateway $1 on the public cloud successfully. |
|
Variable fields |
$1: Transit gateway name. |
|
Severity level |
|
|
Example |
Updated transit gateway TGW1 on the public cloud successfully. |
|
Explanation |
The controller edited a transit gateway on AWS successfully. |
|
Recommended action |
No action is required. |
Failed to edit transit gateway on AWS
|
Keyword |
UPDATE_TRANSIT_GATEWAY_OP |
|
Message text |
Failed to update transit gateway $1 on the public cloud. Reason:$2 |
|
Variable fields |
$1: Transit gateway name. $2: Failure cause. |
|
Severity level |
|
|
Example |
Failed to update transit gateway TGW1 on the public cloud. Reason: Failed to request data from Amazon Web Services. |
|
Explanation |
The controller failed to edit a transit gateway on AWS. |
|
Recommended action |
Resolve the issue based on the prompt. |
Deleted transit gateway from AWS successfully
|
Keyword |
DEL_TRANSIT_GATEWAY_OP |
|
Message text |
Deleted transit gateway $1 from the public cloud successfully. |
|
Variable fields |
$1: Transit gateway name. |
|
Severity level |
|
|
Example |
Deleted transit gateway TGW1 from the public cloud successfully. |
|
Explanation |
The controller deleted a transit gateway from AWS successfully. |
|
Recommended action |
No action is required. |
Failed to delete transit gateway from AWS
|
Keyword |
DEL_TRANSIT_GATEWAY_OP |
|
Message text |
Failed to delete transit gateway $1 from the public cloud. Reason: $2 |
|
Variable fields |
$1: Transit gateway name. $2: Failure cause. |
|
Severity level |
|
|
Example |
Failed to delete transit gateway TGW1 from the public cloud. Reason: Failed to request data from Amazon Web Services. |
|
Explanation |
The controller failed to delete a transit gateway from AWS. |
|
Recommended action |
Resolve the issue based on the prompt. |
Created transit router on AWS successfully
|
Keyword |
ADD_TRANSIT_ROUTER_OP |
|
Message text |
Created transit router $1 on the public cloud successfully. |
|
Variable fields |
$1: Transit router name. |
|
Severity level |
|
|
Example |
Created transit router TR1 on the public cloud successfully. |
|
Explanation |
The controller created a transit router on AWS successfully. |
|
Recommended action |
No action is required. |
Failed to create transit router on AWS
|
Keyword |
ADD_TRANSIT_ROUTER_OP |
|
Message text |
Failed to create transit router $1 on the public cloud. Reason: $2 |
|
Variable fields |
$1: Transit router name. $2: Failure cause. |
|
Severity level |
|
|
Example |
Failed to create transit router TR1 on the public cloud. Reason: Failed to request data from Amazon Web Services. |
|
Explanation |
The controller failed to create a transit router on AWS. |
|
Recommended action |
Resolve the issue based on the prompt. |
Edited transit router on AWS successfully
|
Keyword |
UPDATE_TRANSIT_ROUTER_OP |
|
Message text |
Updated transit router $1 on the public cloud successfully. |
|
Variable fields |
$1: Transit router name. |
|
Severity level |
|
|
Example |
Updated transit router TR1 on the public cloud successfully. |
|
Explanation |
The controller edited a transit router on AWS successfully. |
|
Recommended action |
No action is required. |
Failed to edit transit router on AWS
|
Keyword |
UPDATE_TRANSIT_ROUTER_OP |
|
Message text |
Failed to update transit router $1 on the public cloud. Reason:$2 |
|
Variable fields |
$1: Transit router name. $2: Failure cause. |
|
Severity level |
|
|
Example |
Failed to update transit router TR1 on the public cloud. Reason: Failed to request data from Amazon Web Services. |
|
Explanation |
The controller failed to edit a transit router on AWS. |
|
Recommended action |
Resolve the issue based on the prompt. |
Deleted transit router from AWS successfully
|
Keyword |
DEL_TRANSIT_ROUTER_OP |
|
Message text |
Deleted transit router $1 from the public cloud successfully. |
|
Variable fields |
$1: Transit router name. |
|
Severity level |
|
|
Example |
Deleted transit router TR1 from the public cloud successfully. |
|
Explanation |
The controller deleted a transit router from AWS successfully. |
|
Recommended action |
No action is required. |
Failed to delete transit router from AWS
|
Keyword |
DEL_TRANSIT_ROUTER_OP |
|
Message text |
Failed to delete transit router $1 from the public cloud. Reason: $2 |
|
Variable fields |
$1: Transit router name. $2: Failure cause. |
|
Severity level |
|
|
Example |
Failed to delete transit router TR1 from the public cloud. Reason: Failed to request data from Amazon Web Services. |
|
Explanation |
The controller failed to delete a transit router from AWS. |
|
Recommended action |
Resolve the issue based on the prompt. |
Created transit gateway peering on AWS successfully
|
Keyword |
ADD_TRANSIT_GATEWAY_OP |
|
Message text |
Created transit gateway peering $1 on the public cloud successfully. |
|
Variable fields |
$1: Transit gateway peering name. |
|
Severity level |
|
|
Example |
Created transit gateway peering TGWP1 on the public cloud successfully. |
|
Explanation |
The controller created a transit gateway peering on AWS successfully. |
|
Recommended action |
No action is required. |
Failed to create transit gateway peering on AWS
|
Keyword |
ADD_TRANSIT_GATEWAY_OP |
|
Message text |
Failed to create transit gateway peering $1 on the public cloud. Reason: $2 |
|
Variable fields |
$1: Transit gateway peering name. $2: Failure cause. |
|
Severity level |
|
|
Example |
Failed to create transit gateway peering TGWP1 on the public cloud. Reason: Failed to request data from Amazon Web Services. |
|
Explanation |
The controller failed to create a transit gateway peering on AWS. |
|
Recommended action |
Resolve the issue based on the prompt. |
Edited transit gateway peering on AWS successfully
|
Keyword |
UPDATE_TRANSIT_GATEWAY_OP |
|
Message text |
Updated transit gateway peering $1 on the public cloud successfully. |
|
Variable fields |
$1: Transit gateway peering name. |
|
Severity level |
|
|
Example |
Updated transit gateway peering TGWP1 on the public cloud successfully. |
|
Explanation |
The controller edited a transit gateway peering on AWS successfully. |
|
Recommended action |
No action is required. |
Failed to edit transit gateway peering on AWS
|
Keyword |
UPDATE_TRANSIT_GATEWAY_OP |
|
Message text |
Failed to update transit gateway peering $1 on the public cloud. Reason:$2 |
|
Variable fields |
$1: Transit gateway peering name. $2: Failure cause. |
|
Severity level |
|
|
Example |
Failed to update transit gateway peering TGWP1 on the public cloud. Reason: Failed to request data from Amazon Web Services. |
|
Explanation |
The controller failed to edit a transit gateway peering on AWS. |
|
Recommended action |
Resolve the issue based on the prompt. |
Deleted transit gateway peering from AWS successfully
|
Keyword |
DEL_TRANSIT_GATEWAY_OP |
|
Message text |
Deleted transit gateway peering $1 from the public cloud successfully. |
|
Variable fields |
$1: Transit gateway peering name. |
|
Severity level |
|
|
Example |
Deleted transit gateway peering TGWP1 from the public cloud successfully. |
|
Explanation |
The controller deleted a transit gateway peering from AWS successfully. |
|
Recommended action |
No action is required. |
Failed to delete transit gateway peering from AWS
|
Keyword |
DEL_TRANSIT_GATEWAY_OP |
|
Message text |
Failed to delete transit gateway peering $1 from the public cloud. Reason: $2 |
|
Variable fields |
$1: Transit gateway peering name. $2: Failure cause. |
|
Severity level |
|
|
Example |
Failed to delete transit gateway peering TGWP1 from the public cloud. Reason: Failed to request data from Amazon Web Services. |
|
Explanation |
The controller failed to delete a transit gateway peering from AWS. |
|
Recommended action |
Resolve the issue based on the prompt. |
Failed to query transit gateway peering information from AWS
|
Keyword |
QUERY_TRANSIT_GATEWAY_OP |
|
Message text |
Failed to obtain transit gateway peering $1 from the public cloud. Reason: $2 |
|
Variable fields |
$1: Transit gateway peering name. $2: Failure cause. |
|
Severity level |
|
|
Example |
Failed to obtain transit gateway peering TGWP1 from the public cloud. Reason: Failed to request data from Amazon Web Services. |
|
Explanation |
The controller failed to query transit gateway peering information from AWS. |
|
Recommended action |
Resolve the issue based on the prompt. |
Created vRouter access on AWS successfully
|
Keyword |
ADD_TRANSIT_ROUTER_OP |
|
Message text |
Created vRouter access $1 on the public cloud successfully. |
|
Variable fields |
$1: vRouter access name. |
|
Severity level |
|
|
Example |
Created vRouter access VRC1 on the public cloud successfully. |
|
Explanation |
The controller created a vRouter access on AWS successfully. |
|
Recommended action |
No action is required. |
Failed to create vRouter access on AWS
|
Keyword |
ADD_TRANSIT_ROUTER_OP |
|
Message text |
Failed to create vRouter access $1 on the public cloud. Reason: $2 |
|
Variable fields |
$1: vRouter access name. $2: Failure cause. |
|
Severity level |
|
|
Example |
Failed to create vRouter access VRC1 on the public cloud. Reason: Failed to request data from Amazon Web Services. |
|
Explanation |
The controller failed to create a vRouter access on AWS. |
|
Recommended action |
Resolve the issue based on the prompt. |
Edited vRouter access on AWS successfully
|
Keyword |
UPDATE_TRANSIT_ROUTER_OP |
|
Message text |
Updated vRouter access $1 on the public cloud successfully. |
|
Variable fields |
$1: vRouter access name. |
|
Severity level |
|
|
Example |
Updated vRouter access VRC1 on the public cloud successfully. |
|
Explanation |
The controller edited a vRouter access on AWS successfully. |
|
Recommended action |
No action is required. |
Failed to edit vRouter access on AWS
|
Keyword |
UPDATE_TRANSIT_ROUTER_OP |
|
Message text |
Failed to update vRouter access $1 on the public cloud. Reason:$2 |
|
Variable fields |
$1: vRouter access name. $2: Failure cause. |
|
Severity level |
|
|
Example |
Failed to update vRouter access VRC1 on the public cloud. Reason: Failed to request data from Amazon Web Services. |
|
Explanation |
The controller failed to edit a vRouter access on AWS. |
|
Recommended action |
Resolve the issue based on the prompt. |
Deleted vRouter access from AWS successfully
|
Keyword |
DEL_TRANSIT_ROUTER_OP |
|
Message text |
Deleted vRouter access $1 from the public cloud successfully. |
|
Variable fields |
$1: vRouter access name. |
|
Severity level |
|
|
Example |
Deleted vRouter access VRC1 from the public cloud successfully. |
|
Explanation |
The controller deleted a vRouter access from AWS successfully. |
|
Recommended action |
No action is required. |
Failed to delete vRouter access from AWS
|
Keyword |
DEL_TRANSIT_ROUTER_OP |
|
Message text |
Failed to delete vRouter access $1 from the public cloud. Reason: $2 |
|
Variable fields |
$1: vRouter access name. $2: Failure cause. |
|
Severity level |
|
|
Example |
Failed to delete vRouter access VRC1 from the public cloud. Reason: Failed to request data from Amazon Web Services. |
|
Explanation |
The controller failed to delete a vRouter access from AWS. |
|
Recommended action |
Resolve the issue based on the prompt. |
Created transit route entry on AWS successfully
|
Keyword |
ADD_TRANSIT_ROUTER_OP |
|
Message text |
Created transit route entry $1 on the public cloud successfully. |
|
Variable fields |
$1: Destination subnet of a transit route entry. |
|
Severity level |
|
|
Example |
Created transit route entry TRI1 on the public cloud successfully. |
|
Explanation |
The controller created a transit route entry on AWS successfully. |
|
Recommended action |
No action is required. |
Failed to create transit route entry on AWS
|
Keyword |
ADD_TRANSIT_ROUTER_OP |
|
Message text |
Failed to create transit route entry $1 on the public cloud. Reason: $2 |
|
Variable fields |
$1: Destination subnet of a transit route entry. $2: Failure cause. |
|
Severity level |
|
|
Example |
Failed to create transit route entry TRI1 on the public cloud. Reason: Failed to request data from Amazon Web Services. |
|
Explanation |
The controller failed to create a transit route entry on AWS. |
|
Recommended action |
Resolve the issue based on the prompt. |
Deleted transit route entry from AWS successfully
|
Keyword |
DEL_TRANSIT_ROUTER_OP |
|
Message text |
Deleted transit route entry $1 from the public cloud successfully. |
|
Variable fields |
$1: Destination subnet of a transit route entry. |
|
Severity level |
|
|
Example |
Deleted transit route entry TRI1 from the public cloud successfully. |
|
Explanation |
The controller deleted a transit route entry from AWS successfully. |
|
Recommended action |
No action is required. |
Failed to delete transit route entry from AWS
|
Keyword |
DEL_TRANSIT_ROUTER_OP |
|
Message text |
Failed to delete transit route entry $1 from the public cloud. Reason: $2 |
|
Variable fields |
$1: Destination subnet of a transit route entry. $2: Failure cause. |
|
Severity level |
|
|
Example |
Failed to delete transit route entry TRI1 from the public cloud. Reason: Failed to request data from Amazon Web Services. |
|
Explanation |
The controller failed to delete a transit route entry from AWS. |
|
Recommended action |
Resolve the issue based on the prompt. |
Created transit gateway mount on AWS successfully
|
Keyword |
CREATE_VROUTER_ACCESS_OP |
|
Message text |
Created transit gateway mount on the public cloud successfully |
|
Variable fields |
N/A |
|
Severity level |
|
|
Example |
Created transit gateway mount on the public cloud successfully |
|
Explanation |
The controller created a transit gateway mount on AWS successfully. |
|
Recommended action |
No action is required. |
Failed to create transit gateway mount on AWS
|
Keyword |
CREATE_VROUTER_ACCESS_OP |
|
Message text |
Failed to create transit gateway mount on the public cloud. Reason: $1 |
|
Variable fields |
$1: Failure cause. |
|
Severity level |
|
|
Example |
Failed to create transit gateway mount on the public cloud. Reason: Failed to request data from Amazon Web Services. |
|
Explanation |
The controller failed to create a transit gateway mount on AWS. |
|
Recommended action |
Resolve the issue based on the prompt. |
Associated transit gateway attachment and transit router on AWS successfully
|
Keyword |
CREATE_VROUTER_ACCESS_OP |
|
Message text |
Associated transit gateway attachment $1 and transit router $2 on the public cloud successfully |
|
Variable fields |
$1: ID of transit gateway attachment on the public cloud. $2: ID of a transit router on the public cloud. |
|
Severity level |
|
|
Example |
Associated transit gateway attachment tgw-attach-072094e54d04b1735 and transit router tgw-rtb-0e9b6219ce397deb7 on the public cloud successfully. |
|
Explanation |
The controller associated a transit gateway attachment and a transit router on AWS successfully. |
|
Recommended action |
No action is required. |
Failed to associate transit gateway attachment and transit router on AWS
|
Keyword |
CREATE_VROUTER_ACCESS_OP |
|
Message text |
Failed to associate transit gateway attachment $1 and transit router $2 on the public cloud. Reason:$3 |
|
Variable fields |
$1: ID of transit gateway attachment on the public cloud. $2: ID of a transit router on the public cloud. $3: Failure cause. |
|
Severity level |
|
|
Example |
Failed to associate transit gateway attachment tgw-attach-072094e54d04b1735 and transit router tgw-rtb-0e9b6219ce397deb7 on the public cloud.Reason: Failed to request data from Amazon Web Services. |
|
Explanation |
The controller failed to associate a transit gateway attachment and a transit router on AWS. |
|
Recommended action |
Resolve the issue based on the prompt. |
Disassociated transit gateway attachment and transit router on AWS successfully
|
Keyword |
DELETE_VROUTER_ACCESS_OP |
|
Message text |
Disassociated transit gateway attachment $1 and transit router $2 on the public cloud successfully. |
|
Variable fields |
$1: ID of transit gateway attachment on the public cloud. $2: ID of a transit router on the public cloud. |
|
Severity level |
|
|
Example |
Disassociated transit gateway attachment tgw-attach-072094e54d04b1735 and transit router tgw-rtb-0e9b6219ce397deb7 on the public cloud successfully. |
|
Explanation |
The controller disassociated a transit gateway attachment and a transit router on AWS successfully. |
|
Recommended action |
No action is required. |
Failed to disassociate transit gateway attachment and transit router on AWS
|
Keyword |
DELETE_VROUTER_ACCESS_OP |
|
Message text |
Failed to disassociate transit gateway attachment $1 and transit router $2 on the public cloud.Reason:$3 |
|
Variable fields |
$1: ID of transit gateway attachment on the public cloud. $2: ID of a transit router on the public cloud. $3: Failure cause. |
|
Severity level |
|
|
Example |
Failed to disassociate transit gateway attachment tgw-attach-072094e54d04b1735 and transit router tgw-rtb-0e9b6219ce397deb7 on the public cloud.Reason: Failed to request data from Amazon Web Services. |
|
Explanation |
The controller failed to disassociate a transit gateway attachment and a transit router on AWS. |
|
Recommended action |
Resolve the issue based on the prompt. |
Propagated transit gateway attachment and transit router association to AWS successfully
|
Keyword |
CREATE_VROUTER_ACCESS_OP |
|
Message text |
Propagated transit gateway attachment $1 and transit router $2 on the public cloud successfully |
|
Variable fields |
$1: ID of transit gateway attachment on the public cloud. $2: ID of a transit router on the public cloud. |
|
Severity level |
|
|
Example |
Propagated transit gateway attachment tgw-attach-072094e54d04b1735 and transit router tgw-rtb-0e9b6219ce397deb7 on the public cloud successfully. |
|
Explanation |
The controller propagated a transit gateway attachment and transit router association to AWS successfully. |
|
Recommended action |
No action is required. |
Failed to propagate transit gateway attachment and transit router association to AWS
|
Keyword |
DELETE_VROUTER_ACCESS_OP |
|
Message text |
Failed to propagate transit gateway attachment $1 and transit router $2 on the public cloud.Reason:$3 |
|
Variable fields |
$1: ID of transit gateway attachment on the public cloud. $2: ID of a transit router on the public cloud. $3: Failure cause. |
|
Severity level |
|
|
Example |
Failed to propagate transit gateway attachment tgw-attach-072094e54d04b1735 and transit router tgw-rtb-0e9b6219ce397deb7 on the public cloud.Reason: Failed to request data from Amazon Web Services. |
|
Explanation |
The controller failed to propagate a transit gateway attachment and transit router association to AWS successfully. |
|
Recommended action |
Resolve the issue based on the prompt. |
Disabled propagation of transit gateway attachment and transit router association to AWS successfully
|
Keyword |
DELETE_VROUTER_ACCESS_OP |
|
Message text |
Disabled propagate transit gateway attachment $1 and transit router $2 on the public cloud successfully |
|
Variable fields |
$1: ID of transit gateway attachment on the public cloud. $2: ID of a transit router on the public cloud. |
|
Severity level |
|
|
Example |
Disabled propagate transit gateway attachment tgw-attach-072094e54d04b1735 and transit router tgw-rtb-0e9b6219ce397deb7 on the public cloud successfully. |
|
Explanation |
The controller disabled propagation of a transit gateway attachment and transit router association to AWS successfully. |
|
Recommended action |
No action is required. |
Failed to disable propagation of transit gateway attachment and transit router association to AWS
|
Keyword |
DELETE_VROUTER_ACCESS_OP |
|
Message text |
Failed to disable propagate transit gateway attachment $1 and transit router $2 on the public cloud.Reason:$3 |
|
Variable fields |
$1: ID of transit gateway attachment on the public cloud. $2: ID of a transit router on the public cloud. $3: Failure cause. |
|
Severity level |
|
|
Example |
Failed to disable propagate transit gateway attachment tgw-attach-072094e54d04b1735 and transit router tgw-rtb-0e9b6219ce397deb7 on the public cloud.Reason: Failed to request data from Amazon Web Services. |
|
Explanation |
The controller failed to disable propagation of a transit gateway attachment and transit router association to AWS. |
|
Recommended action |
Resolve the issue based on the prompt. |
Edited transit gateway mount on AWS successfully
|
Keyword |
UPDATE_VROUTER_ACCESS_OP |
|
Message text |
Updated transit gateway mount on the public cloud successfully |
|
Variable fields |
N/A |
|
Severity level |
|
|
Example |
Updated transit gateway mount on the public cloud successfully |
|
Explanation |
The controller edited a transit gateway mount on AWS successfully. |
|
Recommended action |
No action is required. |
Failed to edit transit gateway mount on AWS
|
Keyword |
UPDATE_VROUTER_ACCESS_OP |
|
Message text |
Failed to update transit gateway mount on the public cloud.Reason:$1 |
|
Variable fields |
$1: Failure cause. |
|
Severity level |
|
|
Example |
Failed to update transit gateway mount on the public cloud.Reason: Failed to request data from Amazon Web Services. |
|
Explanation |
The controller failed to edit a transit gateway mount on AWS. |
|
Recommended action |
Resolve the issue based on the prompt. |
Deleted transit gateway mount from AWS successfully
|
Keyword |
DELETE_VROUTER_ACCESS_OP |
|
Message text |
Deleted transit gateway mount on the public cloud successfully |
|
Variable fields |
N/A |
|
Severity level |
|
|
Example |
Deleted transit gateway mount on the public cloud successfully |
|
Explanation |
The controller deleted a transit gateway mount from AWS successfully. |
|
Recommended action |
No action is required. |
Failed to delete transit gateway mount from AWS
|
Keyword |
DELETE_VROUTER_ACCESS_OP |
|
Message text |
Failed to delete transit gateway mount on the public cloud.Reason:$1 |
|
Variable fields |
$1: Failure cause. |
|
Severity level |
|
|
Example |
Failed to delete transit gateway mount on the public cloud. Reason: Failed to request data from Amazon Web Services. |
|
Explanation |
The controller failed to delete a transit gateway mount from AWS. |
|
Recommended action |
Resolve the issue based on the prompt. |
ROUTER
This section contains vRouter messages generated during the synchronization between the super controller and sites.
Successful adding of vRouter
|
Keyword |
ROUTER_ADD_SUCCESSED |
|
Message text |
Successfully added a router configuration in site ”$1”. The router configuration information is as follows: $2 |
|
Variable fields |
$1: Site name. $2: vRouter information. |
|
Severity level |
|
|
Example |
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] |
|
Explanation |
Successfully added a vRouter in a site through the super controller. |
|
Recommended action |
No action is required. |
Failure to add vRouter
|
Keyword |
ROUTER_ADD_FAILED |
|
Message text |
Failed to add a router configuration in site ”$1”. Reason: $2. The router configuration information is as follows: $3 |
|
Variable fields |
$1: Site name. $2: Failure reason. $3: vRouter information. |
|
Severity level |
|
|
Example |
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] |
|
Explanation |
Failed to add a vRouter in a site through the super controller. |
|
Recommended action |
Follow the prompt to resolve the problem. |
Successful update of vRouter
|
Keyword |
ROUTER_UPDATE_SUCCESSED |
|
Message text |
Successfully updated a router configuration in site ”$1”. The router configuration information is as follows: $2 |
|
Variable fields |
$1: Site name. $2: vRouter information. |
|
Severity level |
|
|
Example |
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] |
|
Explanation |
Successfully updated a vRouter in a site through the super controller. |
|
Recommended action |
No action is required. |
Failure to update vRouter
|
Keyword |
ROUTER_UPDATE_FAILED |
|
Message text |
Failed to update a router configuration in site ”$1”. Reason: $2. The router configuration information is as follows: $2 |
|
Variable fields |
$1: Site name. $2: Failure reason. $3: vRouter information. |
|
Severity level |
|
|
Example |
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] |
|
Explanation |
Failed to update a vRouter in a site through the super controller. |
|
Recommended action |
Follow the prompt to resolve the problem. |
Successful deletion of vRouter
|
Keyword |
ROUTER_DELETE_SUCCESSED |
|
Message text |
Successfully deleted a router configuration in site ”$1”. The router configuration information is as follows: $2 |
|
Variable fields |
$1: Site name. $2: vRouter information. |
|
Severity level |
|
|
Example |
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] |
|
Explanation |
Successfully deleted a vRouter in a site through the super controller. |
|
Recommended action |
No action is required. |
Failure to delete vRouter
|
Keyword |
ROUTER_DELETE_FAILED |
|
Message text |
Failed to delete a router configuration in site ”$1”. Reason: $2. The router configuration information is as follows: $3 |
|
Variable fields |
$1: Site name. $2: Failure reason. $3: vRouter information. |
|
Severity level |
|
|
Example |
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] |
|
Explanation |
Failed to delete a vRouter in a site through the super controller. |
|
Recommended action |
Follow the prompt to resolve the problem. |
Failure to synchronize vRouter settings from site
|
Keyword |
CONTROLLED_SITE |
|
Message text |
Failed to synchronize settings from site “$1”. Settings failed to be synchronized: $2 |
|
Variable fields |
$1: Site name. $2: vRouter information. |
|
Severity level |
|
|
Example |
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] |
|
Explanation |
The super controller failed to synchronize vRouter settings from a site. |
|
Recommended action |
Resolve the problem based on the operation log. |
Successful rollback of vRouter adding configuration
|
Keyword |
ROLLBACK_ROUTER_ADD_SUCCESSED |
|
Message text |
Successfully rolled back the router adding configuration for site "$1". The router information is as follows: $2. |
|
Variable fields |
$1: Site name. $2: vRouter settings. |
|
Severity level |
|
|
Example |
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] |
|
Explanation |
Configuration rollback succeeded after failure to issue vRouter adding configuration to the site. |
|
Recommended action |
No action is required. |
Successful rollback of vRouter updating configuration
|
Keyword |
ROLLBACK_ROUTER_UPDATE_SUCCESSED |
|
Message text |
Successfully rolled back the router updating configuration for site "$1". The router information is as follows: $2. |
|
Variable fields |
$1: Site name. $2: vRouter settings. |
|
Severity level |
|
|
Example |
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] |
|
Explanation |
Configuration rollback succeeded after failure to issue vRouter updating configuration to the site. |
|
Recommended action |
No action is required. |
Successful rollback of vRouter deletion configuration
|
Keyword |
ROLLBACK_ROUTER_DELETE_SUCCESSED |
|
Message text |
Successfully rolled back the router deleting configuration for site "$1". The router information is as follows: $2. |
|
Variable fields |
$1: Site name. $2: vRouter settings. |
|
Severity level |
|
|
Example |
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] |
|
Explanation |
Configuration rollback succeeded after failure to issue vRouter deletion configuration to the site. |
|
Recommended action |
No action is required. |
Rollback failure of vRouter adding configuration
|
Keyword |
ROLLBACK_ROUTER_ADD_FAILED |
|
Message text |
Failed to roll back the router adding configuration for site "$1". Reason: $2. The router information is as follows: $3. |
|
Variable fields |
$1: Site name. $2: Failure reason. $3: vRouter settings. |
|
Severity level |
|
|
Example |
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] |
|
Explanation |
Configuration rollback failed after failure to issue vRouter adding configuration to the site. |
|
Recommended action |
As a best practice, manually delete residual configuration from the site. |
Rollback failure of vRouter updating configuration
|
Keyword |
ROLLBACK_ROUTER_UPDATE_FAILED |
|
Message text |
Failed to roll back the router updating configuration for site "$1". Reason: $2. The router information is as follows: $3. |
|
Variable fields |
$1: Site name. $2: Failure reason. $3: vRouter settings. |
|
Severity level |
|
|
Example |
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] |
|
Explanation |
Configuration rollback failed after failure to issue vRouter updating configuration to the site. |
|
Recommended action |
As a best practice, manually delete residual configuration from the site. |
Rollback failure of vRouter deletion configuration
|
Keyword |
ROLLBACK_ROUTER_DELETE_FAILED |
|
Message text |
Failed to roll back the router deleting configuration for site "$1". Reason: $2. The router information is as follows: $3. |
|
Variable fields |
$1: Site name. $2: Failure reason. $3: vRouter settings. |
|
Severity level |
|
|
Example |
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] |
|
Explanation |
Configuration rollback failed after failure to issue vRouter deletion configuration to the site. |
|
Recommended action |
As a best practice, manually delete residual configuration from the site. |
Successful binding of vRouter to subnet in a site
|
Keyword |
ROUTER_ADD_ROUTER_INTERFACE_SUCCESSED |
|
Message text |
Successfully bound a vRouter to a subnet in site $1. The vRouter information is as follows: $2 |
|
Variable fields |
$1: Site name. $2: vRouter information. |
|
Severity level |
|
|
Example |
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] |
|
Explanation |
Successfully bound a vRouter to a subnet in a site through the super controller. |
|
Recommended action |
No action is required. |
Failure in binding vRouter to subnet in a site
|
Keyword |
ROUTER_ADD_ROUTER_INTERFACE_FAILED |
|
Message text |
Failed to bind a vRouter to a subnet in site $1. Reason: $2. The vRouter information is as follows: $3 |
|
Variable fields |
$1: Site name. $2: Failure reason. $3: vRouter information. |
|
Severity level |
|
|
Example |
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] |
|
Explanation |
Failed to bind a vRouter to a subnet in a site through the super controller. |
|
Recommended action |
Follow the prompt to resolve the problem. |
Successful unbinding of vRouter from subnet in a site
|
Keyword |
ROUTER_REMOVE_ROUTER_INTERFACE_SUCCESSED |
|
Message text |
Successfully removed the binding between a vRouter and a subnet in site $1. The vRouter information is as follows: $2 |
|
Variable fields |
$1: Site name. $2: vRouter information. |
|
Severity level |
|
|
Example |
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] |
|
Explanation |
Successfully unbound a vRouter from a subnet in a site through the super controller. |
|
Recommended action |
No action is required. |
Failure to unbind vRouter from subnet in a site
|
Keyword |
ROUTER_REMOVE_ROUTER_INTERFACE_FAILED |
|
Message text |
Failed to remove the binding between a vRouter and a subnet in site $1. Reason: $2. The vRouter information is as follows: $3 |
|
Variable fields |
$1: Site name. $2: Failure reason. $3: vRouter information. |
|
Severity level |
|
|
Example |
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] |
|
Explanation |
Failed to unbind a vRouter from a subnet in a site through the super controller. |
|
Recommended action |
Follow the prompt to resolve the problem. |
Successful rollback of vRouter-to-subnet binding configuration in a site
|
Keyword |
ROLLBACK_ROUTER_REMOVE_ROUTER_INTERFACE_SUCCESSED |
|
Message text |
Successfully rolled back the vRouter-to-subnet binding configuration in site $1. The vRouter information is as follows: $2 |
|
Variable fields |
$1: Site name. $2: vRouter information. |
|
Severity level |
|
|
Example |
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] |
|
Explanation |
Configuration rollback succeeded after failure to bind a vRouter to a subnet in a site through the super controller. |
|
Recommended action |
No action is required. |
Rollback failure of vRouter-to-subnet binding configuration in a site
|
Keyword |
ROLLBACK_ROUTER_REMOVE_ROUTER_INTERFACE_FAILED |
|
Message text |
Failed to roll back the vRouter-to-subnet binding configuration in site $1. Reason: $2. The vRouter information is as follows: $3 |
|
Variable fields |
$1: Site name. $2: Failure reason. $3: vRouter information. |
|
Severity level |
|
|
Example |
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] |
|
Explanation |
Configuration rollback failed after failure to bind a vRouter to a subnet in a site through the super controller. |
|
Recommended action |
Follow the prompt to resolve the problem. |
Successful rollback of vRouter-to-subnet unbinding configuration in a site
|
Keyword |
ROLLBACK_ROUTER_ADD_ROUTER_INTERFACE_SUCCESSED |
|
Message text |
Successfully rolled back the vRouter-to-subnet binding removal configuration in site $1. The vRouter information is as follows: $2 |
|
Variable fields |
$1: Site name. $2: vRouter information. |
|
Severity level |
|
|
Example |
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] |
|
Explanation |
Configuration rollback succeeded after failure to unbind a vRouter from a subnet in a site through the super controller. |
|
Recommended action |
No action is required. |
Rollback failure of vRouter-to-subnet unbinding configuration in a site
|
Keyword |
ROLLBACK_ROUTER_ADD_ROUTER_INTERFACE_FAILED |
|
Message text |
Failed to roll back the vRouter-to-subnet binding removal configuration in site $1. Reason: $2. The vRouter information is as follows: $3 |
|
Variable fields |
$1: Site name. $2: Failure reason. $3: vRouter information. |
|
Severity level |
|
|
Example |
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] |
|
Explanation |
Configuration rollback failed after failure to unbind a vRouter from a subnet in a site through the super controller. |
|
Recommended action |
Follow the prompt to resolve the problem. |
SERVICERESOURCE
This section contains firewall service resource messages generated when the super controller deploys configuration to a transit site.
Bound firewall service resource to transit router of site successfully
|
Keyword |
ROUTER_BIND_SERVICE_SUCCESSED |
|
Message text |
Successfully created a transit router-firewall binding for site "$1". The transit router-firewall binding information is as follows: $2 |
|
Variable fields |
$1: Site name. $2: Firewall service resource-transit router binding information. |
|
Severity level |
|
|
Example |
Successfully created a transit router-firewall binding for site "148.150".. The transit router-firewall binding information is as follows: [ID=null, ResourceId=66df0130-f445-4066-a7bf-176b4c46905e, Name=null, Tenant Id=null, Tenant Name=null, Features=null, Family=null, Type=null, Vtep=null, Gw Member Id=null, Router Id=6fe2d3ed-2b4c-4fd3-af67-90ca862225d4] |
|
Explanation |
Bound a firewall service resource to a transit router of a site through the super controller successfully. |
|
Recommended action |
No action is required. |
Failed to bind firewall service resource to transit router of site
|
Keyword |
ROUTER_BIND_SERVICE_FAILED |
|
Message text |
Failed to create a transit router-firewall binding for site "$1". Reason: $2. The transit router-firewall binding information is as follows: $3 |
|
Variable fields |
$1: Site name. $2: Failure notification. $3: Firewall service resource-transit router binding information. |
|
Severity level |
|
|
Example |
Failed to create a transit router-firewall binding for site "192.158.14.112". Reason: The transit router does not exist. The transit router-firewall binding information is as follows: [ [ID=null, ResourceId=66df0130-f445-4066-a7bf-176b4c46905e, Name=null, Tenant Id=null, Tenant Name=null, Features=null, Family=null, Type=null, Vtep=null, Gw Member Id=null, Router Id=6fe2d3ed-2b4c-4fd3-af67-90ca862225d4] |
|
Explanation |
Failed to bind a firewall service resource to a transit router of a site through the super controller. |
|
Recommended action |
Troubleshoot the issue as prompted. |
Unbound firewall service resource from transit router of site successfully
|
Keyword |
ROUTER_UNBIND_SERVICE_SUCCESSED |
|
Message text |
Successfully removed the transit router-firewall binding for site "$1". The transit router-firewall binding information is as follows: $2 |
|
Variable fields |
$1: Site name. $2: Firewall service resource-transit router binding information. |
|
Severity level |
|
|
Example |
Successfully removed the transit router-firewall binding for site "148.150". The transit router-firewall binding information is as follows: [ID=null, ResourceId=66df0130-f445-4066-a7bf-176b4c46905e, Name=null, Tenant Id=null, Tenant Name=null, Features=null, Family=null, Type=null, Vtep=null, Gw Member Id=null, Router Id=6fe2d3ed-2b4c-4fd3-af67-90ca862225d4] |
|
Explanation |
Unbound a firewall service resource from a transit router of a site through the super controller successfully. |
|
Recommended action |
No action is required. |
Failed to unbind firewall service resource from transit router of site
|
Keyword |
ROUTER_UNBIND_SERVICE_FAILED |
|
Message text |
Failed to remove the transit router-firewall binding for site "$1". Reason: $2. The transit router-firewall binding information is as follows: $3 |
|
Variable fields |
$1: Site name. $2: Failure notification. $3: Firewall service resource-transit router binding information. |
|
Severity level |
|
|
Example |
Failed to remove the transit router-firewall binding for site "192.158.14.112". Reason: The transit router does not exist. The transit router-firewall binding information is as follows: [ [ID=null, ResourceId=66df0130-f445-4066-a7bf-176b4c46905e, Name=null, Tenant Id=null, Tenant Name=null, Features=null, Family=null, Type=null, Vtep=null, Gw Member Id=null, Router Id=6fe2d3ed-2b4c-4fd3-af67-90ca862225d4] |
|
Explanation |
Failed to unbind a firewall service resource from a transit router of a site through the super controller. |
|
Recommended action |
Troubleshoot the issue as prompted. |
SUBNET
This section contains subnet messages generated during the synchronization between the super controller and sites.
Successful adding of subnet
|
Keyword |
SUBNET_ADD_SUCCESSED |
|
Message text |
Successfully added a subnet configuration in site ”$1”. The subnet configuration information is as follows: $2 |
|
Variable fields |
$1: Site name. $2: Subnet information. |
|
Severity level |
|
|
Example |
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] |
|
Explanation |
Successfully added a subnet in a site through the super controller. |
|
Recommended action |
No action is required. |
Failure in adding subnet
|
Keyword |
SUBNET_ADD_FAILED |
|
Message text |
Failed to add a subnet configuration in site ”$1”. Reason: $2. The subnet configuration information is as follows: $3 |
|
Variable fields |
$1: Site name. $2: Failure reason. $3: Subnet information. |
|
Severity level |
|
|
Example |
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] |
|
Explanation |
Failed to add a subnet in a site through the super controller. |
|
Recommended action |
Follow the prompt to resolve the problem. |
Successful update of subnet
|
Keyword |
SUBNET_UPDATE_SUCCESSED |
|
Message text |
Successfully updated a subnet configuration in site ”$1”. The subnet configuration information is as follows:$2 |
|
Variable fields |
$1: Site name. $2: Subnet information. |
|
Severity level |
|
|
Example |
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] |
|
Explanation |
Successfully updated a subnet in a site through the super controller. |
|
Recommended action |
No action is required. |
Failure in updating subnet
|
Keyword |
SUBNET_UPDATE_FAILED |
|
Message text |
Failed to update a subnet configuration in site ”$1”. Reason: $2. The subnet configuration information is as follows:$3 |
|
Variable fields |
$1: Site name. $2: Failure reason. $3: Subnet information. |
|
Severity level |
|
|
Example |
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] |
|
Explanation |
Failed to update a subnet in a site through the super controller. |
|
Recommended action |
Follow the prompt to resolve the problem. |
Successful deletion of subnet
|
Keyword |
SUBNET_DELETE_SUCCESSED |
|
Message text |
Successfully deleted a subnet configuration in site ”$1”. The subnet configuration information is as follows: $2 |
|
Variable fields |
$1: Site name. $2: Subnet information. |
|
Severity level |
|
|
Example |
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] |
|
Explanation |
Successfully deleted a subnet in a site through the super controller. |
|
Recommended action |
No action is required. |
Failure in deleting subnet
|
Keyword |
SUBNET_DELETE_FAILED |
|
Message text |
Failed to delete a subnet configuration in site ”$1”. Reason: $2. The subnet configuration information is as follows:$3 |
|
Variable fields |
$1: Site name. $2: Failure reason. $3: Subnet information. |
|
Severity level |
|
|
Example |
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] |
|
Explanation |
Failed to delete a subnet in a site through the super controller. |
|
Recommended action |
Follow the prompt to resolve the problem. |
Failure in synchronizing subnet settings from site
|
Keyword |
CONTROLLED_SITE |
|
Message text |
Failed to synchronize settings from site ”$1”. Settings failed to be synchronized: $2 |
|
Variable fields |
$1: Site name. $2: Subnet information. |
|
Severity level |
|
|
Example |
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] |
|
Explanation |
The super controller failed to synchronize subnet settings from a site. |
|
Recommended action |
Resolve the problem based on the operation log. |
Successful rollback of subnet adding configuration
|
Keyword |
ROLLBACK_SUBNET_ADD_SUCCESSED |
|
Message text |
Successfully rolled back the subnet adding configuration for site "$1". The subnet information is as follows: $2. |
|
Variable fields |
$1: Site name. $2: Subnet information. |
|
Severity level |
|
|
Example |
Successfully added a subnet configuration in site ”site1”. The subnet configuration information is as follows: 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] |
|
Explanation |
The super controller successfully rolled back the subnet adding configuration after it failed to add a subnet in a site. |
|
Recommended action |
No action is required. |
Successful rollback of subnet update configuration
|
Keyword |
ROLLBACK_SUBNET_UPDATE_SUCCESSED |
|
Message text |
Successfully rolled back the subnet updating configuration for site "$1". The subnet information is as follows: $2. |
|
Variable fields |
$1: Site name. $2: Subnet information. |
|
Severity level |
|
|
Example |
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] |
|
Explanation |
The super controller successfully rolled back the subnet update configuration after it failed to update a subnet in a site. |
|
Recommended action |
No action is required. |
Successful rollback of subnet deletion configuration
|
Keyword |
ROLLBACK_SUBNET_DELETE_SUCCESSED |
|
Message text |
Successfully rolled back the subnet deleting configuration for site "$1". The subnet information is as follows: $2. |
|
Variable fields |
$1: Site name. $2: Subnet configuration. |
|
Severity level |
|
|
Example |
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] |
|
Explanation |
The super controller successfully rolled back the subnet deletion configuration after it failed to delete a subnet in a site. |
|
Recommended action |
No action is required. |
Failure in rollback of subnet adding configuration
|
Keyword |
ROLLBACK_SUBNET_ADD_FAILED |
|
Message text |
Failed to roll back the subnet adding configuration for site "$1". Reason: $2. The subnet information is as follows: $3. |
|
Variable fields |
$1: Site name. $2: Failure reason. $3: Subnet configuration. |
|
Severity level |
|
|
Example |
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] |
|
Explanation |
The super controller failed to roll back the subnet adding configuration after it failed to add a subnet in a site. |
|
Recommended action |
Manually delete residual configuration on the site. |
Failure in rollback of subnet update configuration
|
Keyword |
ROLLBACK_SUBNET_ADD_FAILED |
|
Message text |
Failed to roll back the subnet update configuration for site "$1". Reason: $2. The subnet information is as follows: $3. |
|
Variable fields |
$1: Site name. $2: Failure reason. $3: Subnet configuration. |
|
Severity level |
|
|
Example |
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] |
|
Explanation |
The super controller failed to roll back the subnet update configuration after it failed to update a subnet in a site. |
|
Recommended action |
Manually delete residual configuration on the site. |
Failure in rollback of subnet deletion configuration
|
Keyword |
ROLLBACK_SUBNET_DELETE_FAILED |
|
Message text |
Failed to roll back the subnet deleting configuration for site "$1". Reason: $2. The subnet information is as follows: $3. |
|
Variable fields |
$1: Site name. $2: Failure reason. $3: Subnet configuration. |
|
Severity level |
|
|
Example |
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] |
|
Explanation |
The super controller failed to roll back the subnet deletion configuration after it failed to delete a subnet in a site. |
|
Recommended action |
Manually delete residual configuration on the site. |
TENANT
This section contains tenant messages generated during the synchronization between the super controller and sites.
Successful adding of tenant
|
Keyword |
TENANT_ADD_SUCCESSED |
|
Message text |
Successfully added a tenant configuration in site ”$1”. The tenant configuration information is as follows:$2 |
|
Variable fields |
$1: Site name. $2: Tenant information. |
|
Severity level |
|
|
Example |
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] |
|
Explanation |
Successfully added a tenant in a site through the super controller. |
|
Recommended action |
No action is required. |
Failure in adding tenant
|
Keyword |
TENANT_ADD_FAILED |
|
Message text |
Failed to add a tenant configuration in site ”$1”. Reason: $2. The tenant configuration information is as follows:$3 |
|
Variable fields |
$1: Site name. $2: Failure reason. $3: Tenant information. |
|
Severity level |
|
|
Example |
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] |
|
Explanation |
Failed to add a tenant in a site through the super controller. |
|
Recommended action |
Follow the prompt to resolve the problem. |
Successful update of tenant
|
Keyword |
TENANT_UPDATE_SUCCESSED |
|
Message text |
Successfully updated a tenant configuration in site ”$1”. The tenant configuration information is as follows:$2 |
|
Variable fields |
$1: Site name. $2: Tenant information. |
|
Severity level |
|
|
Example |
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] |
|
Explanation |
Successfully updated a tenant in a site through the super controller. |
|
Recommended action |
No action is required. |
Failure in updating tenant
|
Keyword |
TENANT_UPDATE_FAILED |
|
Message text |
Failed to update a tenant configuration in site ”$1”. Reason: $2. The tenant configuration information is as follows: $3 |
|
Variable fields |
$1: Site name. $2: Failure reason. $3: Tenant information. |
|
Severity level |
|
|
Example |
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] |
|
Explanation |
Failed to update a tenant in a site through the super controller. |
|
Recommended action |
Follow the prompt to resolve the problem. |
Successful deletion of tenant
|
Keyword |
TENANT_DELETE_SUCCESSED |
|
Message text |
Successfully deleted a tenant configuration in site ”$1”. The tenant configuration information is as follows: $2 |
|
Variable fields |
$1: Site name. $2: Tenant information. |
|
Severity level |
|
|
Example |
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] |
|
Explanation |
Successfully deleted a tenant in a site through the super controller. |
|
Recommended action |
No action is required. |
Failure in deleting tenant
|
Keyword |
TENANT_DELETE_FAILED |
|
Message text |
Failed to delete a tenant configuration in site ”$1”. Reason: $2. The tenant configuration information is as follows: $3 |
|
Variable fields |
$1: Site name. $2: Failure reason. $3: Tenant information. |
|
Severity level |
|
|
Example |
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] |
|
Explanation |
Failed to delete a tenant in a site through the super controller. |
|
Recommended action |
Follow the prompt to resolve the problem. |
Failure in synchronizing tenant settings from site
|
Keyword |
CONTROLLED_SITE |
|
Message text |
Failed to synchronize settings from site "$1". Settings failed to be synchronized: $2. |
|
Variable fields |
$1: Site name. $2: Tenant information. |
|
Severity level |
|
|
Example |
Failed to synchronize settings from site "site1". Settings failed to be synchronized: [ID=39840fd0-9d66-4cda-9bff-5c0dc2b727ba, Name=sdn, Description=The tenant information was synchronized from a site, Type=local-create] |
|
Explanation |
The super controller failed to synchronize tenant settings from a site. |
|
Recommended action |
Resolve the problem based on the operation log. |
Successful rollback of tenant adding configuration
|
Keyword |
ROLLBACK_TENANT_ADD_SUCCESSED |
|
Message text |
Successfully rolled back the tenant adding configuration for site "$1". The tenant information is as follows: $2. |
|
Variable fields |
$1: Site name. $2: Tenant information. |
|
Severity level |
|
|
Example |
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 ] |
|
Explanation |
The super controller successfully rolled back the tenant adding configuration after it failed to add a tenant in a site. |
|
Recommended action |
No action is required. |
Successful rollback of tenant update configuration
|
Keyword |
ROLLBACK_TENANT_UPDATE_SUCCESSED |
|
Message text |
Successfully rolled back the tenant updating configuration for site "$1". The tenant information is as follows: $2. |
|
Variable fields |
$1: Site name. $2: Tenant information. |
|
Severity level |
|
|
Example |
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 ] |
|
Explanation |
The super controller successfully rolled back the tenant update configuration after it failed to update a tenant in a site. |
|
Recommended action |
No action is required. |
Successful rollback of tenant deletion configuration
|
Keyword |
ROLLBACK_TENANT_DELETE_SUCCESSED |
|
Message text |
Successfully rolled back the tenant deleting configuration for site "$1". The tenant information is as follows: $2. |
|
Variable fields |
$1: Site name. $2: Tenant information. |
|
Severity level |
|
|
Example |
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 ] |
|
Explanation |
The super controller successfully rolled back the tenant deletion configuration after it failed to delete a tenant in a site. |
|
Recommended action |
No action is required. |
Failure in rollback of tenant adding configuration
|
Keyword |
ROLLBACK_TENANT_ADD_FAILED |
|
Message text |
Failed to roll back the tenant adding configuration for site "$1". Reason: $2. The tenant information is as follows: $3. |
|
Variable fields |
$1: Site name. $2: Failure reason. $3: Tenant information. |
|
Severity level |
|
|
Example |
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 ] |
|
Explanation |
The super controller failed to roll back the tenant adding configuration after it failed to add a tenant in a site. |
|
Recommended action |
Manually delete residual configuration on the site. |
Failure in rollback of tenant update configuration
|
Keyword |
ROLLBACK_TENANT_UPDATE_FAILED |
|
Message text |
Failed to roll back the tenant updating configuration for site "$1". Reason: $2. The tenant information is as follows: $3. |
|
Variable fields |
$1: Site name. $2: Failure reason. $3: Tenant information. |
|
Severity level |
|
|
Example |
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 ] |
|
Explanation |
The super controller failed to roll back the tenant update configuration after it failed to update a tenant in a site. |
|
Recommended action |
Manually delete residual configuration on the site. |
Failure in rollback of tenant deletion configuration
|
Keyword |
ROLLBACK_TENANT_DELETE_FAILED |
|
Message text |
Failed to roll back the tenant deleting configuration for site "$1". Reason: $2. The tenant information is as follows: $3. |
|
Variable fields |
$1: Site name. $2: Failure reason. $3: Tenant information. |
|
Severity level |
|
|
Example |
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 ] |
|
Explanation |
The super controller failed to roll back the tenant deletion configuration after it failed to delete a tenant in a site. |
|
Recommended action |
Manually delete residual configuration on the site. |
TRANSIT_ROUTER
This section contains transit router messages.
Successful adding of a transit router to a site
|
Keyword |
TRANSIT_ROUTER_ADD_SUCCESSED |
|
Message text |
Successfully added a transit router configuration in site "$1". The transit router configuration information is as follows: $2 |
|
Variable fields |
$1: Site name. $2: Transit router configuration. |
|
Severity level |
|
|
Example |
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, Type=EXTERNALTRANSIT, Direct External=false, 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]}, Internal Cidrs=null, External Cidrs={[2.2.2.0/24]} ] |
|
Explanation |
A transit router was successfully added to a site on the super controller. |
|
Recommended action |
No action is required. |
Failure in adding a transit router to a site
|
Keyword |
TRANSIT_ROUTER_ADD_FAILED |
|
Message text |
Failed to add a transit router configuration in site "$1". Reason: $2. The transit router configuration information is as follows: $3 |
|
Variable fields |
$1: Site name. $2: Failure reason. $3: Transit router configuration. |
|
Severity level |
|
|
Example |
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, Type=EXTERNALTRANSIT, Direct External=false, 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]} , Internal Cidrs=null, External Cidrs={[2.2.2.0/24]} ] |
|
Explanation |
Adding of a transit router to a site failed on the super controller. |
|
Recommended action |
Follow the prompt to resolve the problem. |
Successful edition of a transit router in a site
|
Keyword |
TRANSIT_ROUTER_UPDATE_SUCCESSED |
|
Message text |
Successfully updated a transit router configuration in site "$1". The transit router configuration information is as follows: $2 |
|
Variable fields |
$1: Site name. $2: Transit router configuration. |
|
Severity level |
|
|
Example |
Successfully updated 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, Type=EXTERNALTRANSIT, Direct External=false, 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]} , Internal Cidrs=null, External Cidrs={[2.2.2.0/24]} ] |
|
Explanation |
A transit router was successfully edited in a site on the super controller. |
|
Recommended action |
No action is required. |
Failure in editing a transit router in a site
|
Keyword |
TRANSIT_ROUTER_UPDATE_FAILED |
|
Message text |
Failed to update a transit router configuration in site "$1". Reason: $2. The transit router configuration information is as follows: $3 |
|
Variable fields |
$1: Site name. $2: Failure reason. $3: Transit router configuration. |
|
Severity level |
|
|
Example |
Failed to update a transit router configuration in site "192.158.14.112". Reason: The segment ID is already used. The transit router configuration information is as follows: [ID=e2e3abfe-f478-4e4f-9ef2-3c47236c55b2, Name=TR-0, Type=EXTERNALTRANSIT, Direct External=false, 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]} , Internal Cidrs=null, External Cidrs={[2.2.2.0/24]} ] |
|
Explanation |
Edition of a transit router in a site failed on the super controller. |
|
Recommended action |
Follow the prompt to resolve the problem. |
Successful deletion of a transit router from a site
|
Keyword |
TRANSIT_ROUTER_DELETE_SUCCESSED |
|
Message text |
Successfully deleted a transit router configuration in site "$1". The transit router configuration information is as follows: $2 |
|
Variable fields |
$1: Site name. $2: Transit router configuration. |
|
Severity level |
|
|
Example |
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, Type=EXTERNALTRANSIT, Direct External=false, 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]} , Internal Cidrs=null, External Cidrs={[2.2.2.0/24]} ] |
|
Explanation |
A transit router was successfully deleted from a site on the super controller. |
|
Recommended action |
No action is required. |
Failure in deleting a transit router from a site
|
Keyword |
TRANSIT_ROUTER_DELETE_FAILED |
|
Message text |
Failed to delete a transit router configuration in site "$1". Reason: $2. The transit router configuration information is as follows: $3 |
|
Variable fields |
$1: Site name. $2: Failure reason. $3: Transit router configuration. |
|
Severity level |
|
|
Example |
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, Type=EXTERNALTRANSIT, Direct External=false, 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]} , Internal Cidrs=null, External Cidrs={[2.2.2.0/24]} ] |
|
Explanation |
Deletion of a transit router from a site failed on the super controller. |
|
Recommended action |
Follow the prompt to resolve the problem. |
Successful configuration rollback after failure in adding a transit router
|
Keyword |
ROLLBACK_TRANSIT_ROUTER_ADD_SUCCESSED |
|
Message text |
Successfully rolled back the transit router adding configuration for site "$1". The transit router information is as follows: $2. |
|
Variable fields |
$1: Site name. $2: Transit router configuration. |
|
Severity level |
|
|
Example |
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, Type=EXTERNALTRANSIT, Direct External=false, 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]} , Internal Cidrs=null, External Cidrs={[2.2.2.0/24]} ] |
|
Explanation |
Configuration was rolled back successfully after adding of a transit router to a site failed. |
|
Recommended action |
No action is required. |
Successful configuration rollback after failure in deleting a transit router
|
Keyword |
ROLLBACK_TRANIST_ROUTER_DELETE_SUCCESSED |
|
Message text |
Successfully rolled back the transit router deleting configuration for site "$1". The transit router information is as follows: $2. |
|
Variable fields |
$1: Site name. $2: Transit router configuration. |
|
Severity level |
|
|
Example |
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, Type=EXTERNALTRANSIT, Direct External=false, 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]} , Internal Cidrs=null, External Cidrs={[2.2.2.0/24]} ] |
|
Explanation |
Configuration was rolled back successfully after deletion of a transit router from a site failed. |
|
Recommended action |
No action is required. |
Failed configuration rollback after failure in adding a transit router
|
Keyword |
ROLLBACK_TRANSIT_ROUTER_ADD_FAILED |
|
Message text |
Failed to roll back the transit router adding configuration for site "$1". Reason: $2. The transit router information is as follows: $3. |
|
Variable fields |
$1: Site name. $2: Failure reason. $3: Transit router configuration. |
|
Severity level |
|
|
Example |
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, Type=EXTERNALTRANSIT, Direct External=false, 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]} , Internal Cidrs=null, External Cidrs={[2.2.2.0/24]} ] |
|
Explanation |
Configuration rollback failed after adding of a transit router to a site failed. |
|
Recommended action |
Manually delete the residual configuration for the site. |
Failed configuration rollback after failure in deleting a transit router
|
Keyword |
ROLLBACK_TRANSIT_ROUTER_DELETE_FAILED |
|
Message text |
Failed to roll back the transit router deleting configuration for site "$1". Reason: $2. The transit router information is as follows: $3. |
|
Variable fields |
$1: Site name. $2: Failure reason. $3: Transit router configuration. |
|
Severity level |
|
|
Example |
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, Type=EXTERNALTRANSIT, Direct External=false, 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]} , Internal Cidrs=null, External Cidrs={[2.2.2.0/24]} ] |
|
Explanation |
Configuration rollback failed after deletion of a transit router from a site failed. |
|
Recommended action |
Manually delete the residual configuration for the site. |
Successful creation of a transit router-gateway binding for a site
|
Keyword |
ROUTER_BIND_GATEWAY_SUCCESSED |
|
Message text |
Successfully created a transit router-gateway binding for site $1. The transit router information is as follows: $2 |
|
Variable fields |
$1: Site name. $2: Transit router information. |
|
Severity level |
|
|
Example |
Successfully created a transit router-gateway binding for site ”site1”. The transit router information is as follows: [ID=a0e23ca5-b84e-4c6b-8f78-8a44dbc1fe1b, Name=TR1, Type=EXTERNALTRANSIT, Direct External=false, Description=, Tenant ID=066c23ce-31fe-ad22-4e75-53cf619f1038, Tenant name=150-200, Transit site ID=6257c723-fb62-48eb-ae72-9c4f4885a52b, VRF mode=AUTO, VRF name=50s8uabe2e9hlouu4a8jds3vgr, L3VNI=53, Import RTS={[0:53]}, Export RTS={[0:53]}, Internal Cidrs=null, External Cidrs={[2.2.2.0/24]} ] |
|
Explanation |
A transit router-gateway binding was successfully created for a site on the super controller. |
|
Recommended action |
No action is required. |
Failure in adding a transit router-gateway binding for a site
|
Keyword |
ROUTER_BIND_GATEWAY_FAILED |
|
Message text |
Failed to create a transit router-gateway binding for site $1. Reason: $2. The transit router information is as follows: $3 |
|
Variable fields |
$1: Site name. $2: Failure reason. $3: Transit router information. |
|
Severity level |
|
|
Example |
Failed to create a transit router-gateway binding for site ”site1”. Reason: Cannot reach the site. The transit router information is as follows: [ID=a0e23ca5-b84e-4c6b-8f78-8a44dbc1fe1b, Name=TR1, Type=EXTERNALTRANSIT, Direct External=false, Description=, Tenant ID=066c23ce-31fe-ad22-4e75-53cf619f1038, Tenant name=150-200, Transit site ID=6257c723-fb62-48eb-ae72-9c4f4885a52b, VRF mode=AUTO, VRF name=50s8uabe2e9hlouu4a8jds3vgr, L3VNI=53, Import RTS={[0:53]}, Export RTS={[0:53]}, Internal Cidrs=null, External Cidrs={[2.2.2.0/24]} ] |
|
Explanation |
Adding of a transit router-gateway binding for a site failed on the super controller. |
|
Recommended action |
Follow the prompt to resolve the problem. |
Successful removal of a transit router-gateway binding for a site
|
Keyword |
ROUTER_UNBIND_GATEWAY_SUCCESSED |
|
Message text |
Successfully removed a transit router-gateway binding for site $1. The transit router information is as follows: $2 |
|
Variable fields |
$1: Site name. $2: Transit router information. |
|
Severity level |
|
|
Example |
Successfully removed a transit router-gateway binding for site ”site1”. The transit router information is as follows: [ID=a0e23ca5-b84e-4c6b-8f78-8a44dbc1fe1b, Name=TR1, Type=EXTERNALTRANSIT, Direct External=false, Description=, Tenant ID=066c23ce-31fe-ad22-4e75-53cf619f1038, Tenant name=150-200, Transit site ID=6257c723-fb62-48eb-ae72-9c4f4885a52b, VRF mode=AUTO, VRF name=50s8uabe2e9hlouu4a8jds3vgr, L3VNI=53, Import RTS={[0:53]}, Export RTS={[0:53]}, Internal Cidrs=null, External Cidrs={[2.2.2.0/24]} ] |
|
Explanation |
A transit router-gateway binding was successfully removed from a site on the super controller. |
|
Recommended action |
No action is required. |
Failure in removing a transit router-gateway binding for a site
|
Keyword |
ROUTER_UNBIND_GATEWAY_FAILED |
|
Message text |
Failed to remove a transit router-gateway binding for site $1. Reason: $2. The transit router information is as follows: $3 |
|
Variable fields |
$1: Site name. $2: Failure reason. $3: Transit router information. |
|
Severity level |
|
|
Example |
Failed to remove a transit router-gateway binding for site ”site1”. Reason: Cannot reach the site. The transit router information is as follows: [ID=a0e23ca5-b84e-4c6b-8f78-8a44dbc1fe1b, Name=TR1, Type=EXTERNALTRANSIT, Direct External=false, Description=, Tenant ID=066c23ce-31fe-ad22-4e75-53cf619f1038, Tenant name=150-200, Transit site ID=6257c723-fb62-48eb-ae72-9c4f4885a52b, VRF mode=AUTO, VRF name=50s8uabe2e9hlouu4a8jds3vgr, L3VNI=53, Import RTS={[0:53]}, Export RTS={[0:53]}, Internal Cidrs=null, External Cidrs={[2.2.2.0/24]} ] |
|
Explanation |
Removal of a transit router-gateway binding for a site failed on the super controller. |
|
Recommended action |
Follow the prompt to resolve the problem. |
Successful creation of a transit router-vPort binding for a site
|
Keyword |
ADD_ROUTER_PORT_INTERFACE_SUCCESSED |
|
Message text |
Successfully created a transit router-vPort binding for site $1. The transit router information is as follows: $2 |
|
Variable fields |
$1: Site name. $2: Transit router information. |
|
Severity level |
|
|
Example |
Successfully created a transit router-vPort binding for site ”site1”. The transit router information is as follows: [ID=a0e23ca5-b84e-4c6b-8f78-8a44dbc1fe1b, Name=TR1, Type=EXTERNALTRANSIT, Direct External=false, Description=, Tenant ID=066c23ce-31fe-ad22-4e75-53cf619f1038, Tenant name=150-200, Transit site ID=6257c723-fb62-48eb-ae72-9c4f4885a52b, VRF mode=AUTO, VRF name=50s8uabe2e9hlouu4a8jds3vgr, L3VNI=53, Import RTS={[0:53]}, Export RTS={[0:53]}, Internal Cidrs=null, External Cidrs={[2.2.2.0/24]} ] |
|
Explanation |
A transit router-vPort binding was successfully created for a site on the super controller. |
|
Recommended action |
No action is required. |
Failure in adding a transit router-vPort binding for a site
|
Keyword |
ADD_ROUTER_PORT_INTERFACE_FAILED |
|
Message text |
Failed to create a transit router-vPort binding for site $1. Reason: $2. The transit router information is as follows: $3 |
|
Variable fields |
$1: Site name. $2: Failure reason. $3: Transit router information. |
|
Severity level |
|
|
Example |
Failed to create a transit router-vPort binding for site ”site1”. Reason: Cannot reach the site. The transit router information is as follows: [ID=a0e23ca5-b84e-4c6b-8f78-8a44dbc1fe1b, Name=TR1, Type=EXTERNALTRANSIT, Direct External=false, Description=, Tenant ID=066c23ce-31fe-ad22-4e75-53cf619f1038, Tenant name=150-200, Transit site ID=6257c723-fb62-48eb-ae72-9c4f4885a52b, VRF mode=AUTO, VRF name=50s8uabe2e9hlouu4a8jds3vgr, L3VNI=53, Import RTS={[0:53]}, Export RTS={[0:53]}, Internal Cidrs=null, External Cidrs={[2.2.2.0/24]} ] |
|
Explanation |
Adding of a transit router-vPort binding for a site failed on the super controller. |
|
Recommended action |
Follow the prompt to resolve the problem. |
Successful removal of a transit router-vPort binding for a site
|
Keyword |
REMOVE_ROUTER_PORT_INTERFACE_SUCCESSED |
|
Message text |
Successfully removed a transit router-vPort binding for site $1. The transit router information is as follows: $2 |
|
Variable fields |
$1: Site name. $2: Transit router information. |
|
Severity level |
|
|
Example |
Successfully removed a transit router-vPort binding for site ”site1”. The transit router information is as follows: [ID=a0e23ca5-b84e-4c6b-8f78-8a44dbc1fe1b, Name=TR1, Type=EXTERNALTRANSIT, Direct External=false, Description=, Tenant ID=066c23ce-31fe-ad22-4e75-53cf619f1038, Tenant name=150-200, Transit site ID=6257c723-fb62-48eb-ae72-9c4f4885a52b, VRF mode=AUTO, VRF name=50s8uabe2e9hlouu4a8jds3vgr, L3VNI=53, Import RTS={[0:53]}, Export RTS={[0:53]}, Internal Cidrs=null, External Cidrs={[2.2.2.0/24]} ] |
|
Explanation |
A transit router-vPort binding was successfully removed from a site on the super controller. |
|
Recommended action |
No action is required. |
Failure in removing a transit router-vPort binding for a site
|
Keyword |
REMOVE_ROUTER_PORT_INTERFACE_FAILED |
|
Message text |
Failed to remove a transit router-vPort binding for site $1. Reason: $2. The transit router information is as follows: $3 |
|
Variable fields |
$1: Site name. $2: Failure reason. $3: Transit router information. |
|
Severity level |
|
|
Example |
Failed to remove a transit router-vPort binding for site ”site1”. Reason: Cannot reach the site. The transit router information is as follows: [ID=a0e23ca5-b84e-4c6b-8f78-8a44dbc1fe1b, Name=TR1, Type=EXTERNALTRANSIT, Direct External=false, Description=, Tenant ID=066c23ce-31fe-ad22-4e75-53cf619f1038, Tenant name=150-200, Transit site ID=6257c723-fb62-48eb-ae72-9c4f4885a52b, VRF mode=AUTO, VRF name=50s8uabe2e9hlouu4a8jds3vgr, L3VNI=53, Import RTS={[0:53]}, Export RTS={[0:53]}, Internal Cidrs=null, External Cidrs={[2.2.2.0/24]} ] |
|
Explanation |
Removal of a transit router-vPort binding for a site failed on the super controller. |
|
Recommended action |
Follow the prompt to resolve the problem. |
Successful creation of a transit router-subnet binding for a site
|
Keyword |
ADD_ROUTER_SUBNET_INTERFACE_SUCCESSED |
|
Message text |
Successfully created a transit router-subnet binding for site $1. The transit router information is as follows: $2 |
|
Variable fields |
$1: Site name. $2: Transit router information. |
|
Severity level |
|
|
Example |
Successfully created a transit router-subnet binding for site ”site1”. The transit router information is as follows: [ID=a0e23ca5-b84e-4c6b-8f78-8a44dbc1fe1b, Name=TR1, Type=EXTERNALTRANSIT, Direct External=false, Description=, Tenant ID=066c23ce-31fe-ad22-4e75-53cf619f1038, Tenant name=150-200, Transit site ID=6257c723-fb62-48eb-ae72-9c4f4885a52b, VRF mode=AUTO, VRF name=50s8uabe2e9hlouu4a8jds3vgr, L3VNI=53, Import RTS={[0:53]}, Export RTS={[0:53]}, Internal Cidrs=null, External Cidrs={[2.2.2.0/24]} ] |
|
Explanation |
A transit router-subnet binding was successfully created for a site on the super controller. |
|
Recommended action |
No action is required. |
Failure in adding a transit router-subnet binding for a site
|
Keyword |
ADD_ROUTER_SUBNET_INTERFACE FAILED |
|
Message text |
Failed to create a transit router-subnet binding for site $1. Reason: $2. The transit router information is as follows: $3 |
|
Variable fields |
$1: Site name. $2: Failure reason. $3: Transit router information. |
|
Severity level |
|
|
Example |
Failed to create a transit router-subnet binding for site ”site1”. Reason: Cannot reach the site. The transit router information is as follows: [ID=a0e23ca5-b84e-4c6b-8f78-8a44dbc1fe1b, Name=TR1, Type=EXTERNALTRANSIT, Direct External=false, Description=, Tenant ID=066c23ce-31fe-ad22-4e75-53cf619f1038, Tenant name=150-200, Transit site ID=6257c723-fb62-48eb-ae72-9c4f4885a52b, VRF mode=AUTO, VRF name=50s8uabe2e9hlouu4a8jds3vgr, L3VNI=53, Import RTS={[0:53]}, Export RTS={[0:53]}, Internal Cidrs=null, External Cidrs={[2.2.2.0/24]} ] |
|
Explanation |
Adding of a transit router-subnet binding for a site failed on the super controller. |
|
Recommended action |
Follow the prompt to resolve the problem. |
Successful removal of a transit router-subnet binding for a site
|
Keyword |
REMOVE_ROUTER_SUBNET_INTERFACE_SUCCESSED |
|
Message text |
Successfully removed a transit router-subnet binding for site $1. The transit router information is as follows: $2 |
|
Variable fields |
$1: Site name. $2: Transit router information. |
|
Severity level |
|
|
Example |
Successfully removed a transit router-subnet binding for site ”site1”. The transit router information is as follows: [ID=a0e23ca5-b84e-4c6b-8f78-8a44dbc1fe1b, Name=TR1, Type=EXTERNALTRANSIT, Direct External=false, Description=, Tenant ID=066c23ce-31fe-ad22-4e75-53cf619f1038, Tenant name=150-200, Transit site ID=6257c723-fb62-48eb-ae72-9c4f4885a52b, VRF mode=AUTO, VRF name=50s8uabe2e9hlouu4a8jds3vgr, L3VNI=53, Import RTS={[0:53]}, Export RTS={[0:53]}, Internal Cidrs=null, External Cidrs={[2.2.2.0/24]} ] |
|
Explanation |
A transit router-subnet binding was successfully removed from a site on the super controller. |
|
Recommended action |
No action is required. |
Failure in removing a transit router-subnet binding for a site
|
Keyword |
REMOVE_ROUTER_SUBNET_INTERFACE_FAILED |
|
Message text |
Failed to remove a transit router-subnet binding for site $1. Reason: $2. The transit router information is as follows: $3 |
|
Variable fields |
$1: Site name. $2: Failure reason. $3: Transit router information. |
|
Severity level |
|
|
Example |
Failed to remove a transit router-subnet binding for site ”site1”. Reason: Cannot reach the site. The transit router information is as follows: [ID=a0e23ca5-b84e-4c6b-8f78-8a44dbc1fe1b, Name=TR1, Type=EXTERNALTRANSIT, Direct External=false, Description=, Tenant ID=066c23ce-31fe-ad22-4e75-53cf619f1038, Tenant name=150-200, Transit site ID=6257c723-fb62-48eb-ae72-9c4f4885a52b, VRF mode=AUTO, VRF name=50s8uabe2e9hlouu4a8jds3vgr, L3VNI=53, Import RTS={[0:53]}, Export RTS={[0:53]}, Internal Cidrs=null, External Cidrs={[2.2.2.0/24]} ] |
|
Explanation |
Removal of a transit router-subnet binding for a site failed on the super controller. |
|
Recommended action |
Follow the prompt to resolve the problem. |
VPC_CONNECT
This section contains VPC connect messages.
Successful adding of a VPC connect to a site
|
Keyword |
VPC_CONNECT_ADD_SUCCESSED |
|
Message text |
Successfully added a VPC connect configuration in site "$1". The VPC connect configuration information is as follows: $2 |
|
Variable fields |
$1: Site name. $2: VPC connect configuration. |
|
Severity level |
|
|
Example |
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], Is local all=false, Local CIDRS={[3.3.3.0/24]}, Is peer all=false, Peer CIDRS={[4.4.4.0/24]}, Advertise host route=false ] |
|
Explanation |
A VPC connect was successfully added to a site on the super controller. |
|
Recommended action |
No action is required. |
Failure in adding a VPC connect to a site
|
Keyword |
VPC_CONNECT_ADD_FAILED |
|
Message text |
Failed to add a VPC connect configuration in site "$1". Reason: $2. The VPC connect configuration information is as follows: $3 |
|
Variable fields |
$1: Site name. $2: Failure reason. $3: VPC connect configuration. |
|
Severity level |
|
|
Example |
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], Is local all=false, Local CIDRS={[3.3.3.0/24]}, Is peer all=false, Peer CIDRS={[4.4.4.0/24]}, Advertise host route=false ] |
|
Explanation |
Adding of a VPC connect to a site failed on the super controller. |
|
Recommended action |
Follow the prompt to resolve the problem. |
Successful update of a VPC connect for a site
|
Keyword |
VPC_CONNECT_UPDATE_SUCCESSED |
|
Message text |
Successfully updated a VPC connect configuration in site "$1". The VPC connect configuration information is as follows: $2 |
|
Variable fields |
$1: Site name. $2: VPC connect configuration. |
|
Severity level |
|
|
Example |
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], Is local all=false, Local CIDRS={[3.3.3.0/24]}, Is peer all=false, Peer CIDRS={[4.4.4.0/24]}, Advertise host route=false ] |
|
Explanation |
A VPC connect was successfully updated for a site on the super controller. |
|
Recommended action |
No action is required. |
Failure in updating a VPC connect for a site
|
Keyword |
VPC_CONNECT_UPDATE_FAILED |
|
Message text |
Failed to update a VPC connect configuration in site "$1". Reason: $2. The VPC connect configuration information is as follows: $2 |
|
Variable fields |
$1: Site name. $2: Failure reason. $3: VPC connect configuration. |
|
Severity level |
|
|
Example |
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], Is local all=false, Local CIDRS={[3.3.3.0/24]}, Is peer all=false, Peer CIDRS={[4.4.4.0/24]}, Advertise host route=false ] |
|
Explanation |
Update of a VPC connect for a site failed on the super controller. |
|
Recommended action |
Follow the prompt to resolve the problem. |
Successful deletion of a VPC connect from a site
|
Keyword |
VPC_CONNECT_DELETE_SUCCESSED |
|
Message text |
Successfully deleted a VPC connect configuration in site "$1". The VPC connect configuration information is as follows: $2 |
|
Variable fields |
$1: Site name. $2: VPC connect configuration. |
|
Severity level |
|
|
Example |
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], Is local all=false, Local CIDRS={[3.3.3.0/24]}, Is peer all=false, Peer CIDRS={[4.4.4.0/24]}, Advertise host route=false ] |
|
Explanation |
A VPC connect was successfully deleted from a site on the super controller. |
|
Recommended action |
No action is required. |
Failure in deleting a VPC connect from a site
|
Keyword |
VPC_CONNECT_DELETE_FAILED |
|
Message text |
Failed to delete a VPC connect configuration in site "$1". Reason: $2. The VPC connect configuration information is as follows: $3 |
|
Variable fields |
$1: Site name. $2: Failure reason. $3: VPC connect configuration. |
|
Severity level |
|
|
Example |
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], Is local all=false, Local CIDRS={[3.3.3.0/24]}, Is peer all=false, Peer CIDRS={[4.4.4.0/24]}, Advertise host route=false ] |
|
Explanation |
Deletion of a VPC connect from a site failed on the super controller. |
|
Recommended action |
Follow the prompt to resolve the problem. |
