Title | Size | Downloads |
---|---|---|
H3C SeerEngine-DC System Log Messages Reference-E37xx-5W701-book.pdf | 1.50 MB |
- Table of Contents
- Related Documents
-
|
H3C SeerEngine-DC |
System Log Messages Reference |
|
|
Document version: 5W701-20210702
Copyright © 2021 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
Failure to synchronize ARP bus messages
Start of ARP configuration recovery on non-active leader controllers
End of ARP configuration recovery on non-active leader controllers
Migration times of the VM reached the maximum within the migration time period
Conflict between the VM MAC address and the gateway MAC address or reserved gateway MAC address
NETCONF configuration deployment failure
Two master nodes exist in a vBGP cluster
vBGP cluster restores master/backup mode
vBGP session being established
vBGP session successfully established
Failed to log in to SeerAnalyzer
Logged in to SeerAnalyzer successfully
Failed to connect to SeerAnalyzer
Connected to SeerAnalyzer successfully
Failed to synchronize fault event
Fault event successfully synchronized
Updated fault event successfully
Failed to update the fault event state
Updated fault event state successfully
Failed to synchronize the closed state of an event
Synchronized the closed state of an event successfully
Sent port isolation request successfully
Failed to send a port isolation request
Sent request for adding configuration fragment successfully
Failed to send request for adding configuration fragment
Sent configuration fragment deployment request
Failed to send configuration fragment deployment request
Synchronized event resolution solution to SeerAnalyzer successfully
Failed to synchronize event resolution solution to SeerAnalyzer
Sent NETCONF configuration deployment request successfully
Failed to send NETCONF configuration deployment request
Certificate reached alarm threshold
Disconnection from the license server
Failure of connection to the license server
Controller forced offline by license server
Reconnection to the license server
Entered fail-safe state due to authorization failure
Entered fail-safe state due to connection failure
Exited fail-safe state after the fail-safe period
Exited fail-safe state after authorization
Exited fail-safe state after disconnection
Remote license expiration pre-warning
Insufficient quantity-based licenses
CPU usage dropped below threshold
Memory usage exceeded threshold
Memory usage dropped below threshold
Disk usage dropped below threshold
Process memory usage exceeded threshold
Process memory usage dropped below threshold
Inconsistency between daemon thread count and core pool size in a thread pool
Excessive response waiting time of the controller
Start of NETCONF configuration recovery on non-active leader controllers
End of NETCONF configuration recovery on non-active leader controllers
NETCONF configuration deployment failure
NETCONF SSH session authentication failure
NETCONF HTTPS connection failure
Unhealthy device operating status
Device operating status changes from unhealthy to healthy
Periodic radar detection task failure
Periodic radar detection task result changes from failure to success
Successful OpenFlow connection
Disconnected OpenFlow connection
Failure to deploy flow entries
Packet-in message rate reaches threshold on controller
Packet-in message rate reaches threshold on OpenFlow device
Packet-in message rate reaches threshold on OpenFlow device port
Change of port operating status from healthy to unhealthy
Change of port operating status from unhealthy to healthy
Failure to restore region settings
Network device connection to a master
Master change for network devices
Network device disconnection from a master
OpenFlow device connection with multiple regions
Abnormal status of the other controller in the region
Normal status of the other controller in the region
Device created SNMP connection with controller
Device broke SNMP connection to controller
Database operation failure because of a nonexistent user
Database operation failure because of refused connections
End of controller configuration recovery
Controller configuration backup not performed when backup file exists
Failed to send the backup file to the remote server
Up to six backup files created by using the same backup method at a time
Controller became active leader
Different team token than the active leader
Reboot for completing team merge
RADIUS authentication rejection
RADIUS attribute check failure
TACACS+ authentication success
TACACS+ authentication rejection
TACACS+ authentication failure
TACACS+ attribute check failure
Start of user configuration recovery on non-active leader controllers
End of user configuration recovery on non-active leader controllers
Operation failure due to user role privilege limit
Controller failed data entry count consistency check
Controller passed data entry count consistency check
Failure to obtain data entry count consistency check result for controller
Controller passed local data entry count consistency check
Controller failed local data entry count consistency check
Failure to obtain local data entry count consistency check result for controller
Controller passed cluster data content consistency check
Controller failed cluster data content consistency check
Failure to obtain cluster data content consistency check result for controller
Start of DHCP configuration recovery on non-active leader controllers
End of DHCP configuration recovery on non-active leader controllers
Failure of IP allocation to VM
Connection establishment between the F5 device and controller
Disconnection between the F5 device and controller
Failure to delete a floating IP
Start of firewall configuration recovery on non-active leader controllers
End of firewall configuration recovery on non-active leader controllers
Inconsistent DPI application profile information
Inconsistent IPS policy information
Inconsistent antivirus policy information
Controller failed to synchronize bridge MAC and serial number information from device
Start of load balancing configuration recovery on non-active leader controllers
End of load balancing configuration recovery on non-active leader controllers
Different VRF information than the network device
Different VSI information than the network device
Different tunnel information than the network device
Different ACL information than the network device
Different PBR information than the network device
Different routing information than the network device
Different VLAN information than the network device
Different NAT information than the network device
Different floating IP information than the network device
Different DNS information than the network device
Different host flow information than the network device
Different subinterface information than the network device
Different VLAN interface information than the network device
Different loopback interface information than the network device
Network device connection to another region
VXLAN tunnel interface in up state
VXLAN tunnel interface in down state
Used up VLAN IDs in the VLAN pools
Used up VXLAN IDs in the VXLAN pools
Used up IP addresses in general address pool
Used up IP addresses in address pool bound to service gateway group
Used up IP addresses in security external network address pool
Used up IP addresses in default address pool
Address pool bound to service gateway group not exist
Failed to assign security external network IP address to resource node
Default address pool not exist
Used up loopback interfaces on the firewall bound to the vRouters
Start of NEM configuration recovery on non-active leader controllers
End of NEM configuration recovery on non-active leader controllers
Data synchronization status changed to Not Synchronized
Data synchronization status changed to Synchronized
Configuration initialization failure during NE activation
Maximum number of Ethernet service instances reached on interface
Controller failed to deploy settings to network device
VLAN and PVID inconsistency between member ports and aggregate interface
Mapping is unbound from port when port is added to aggregate interface
Startup configuration file backup success
Startup configuration file backup failure
Software upgrading or patching failure
Software upgrading or patching success
Used up IP addresses in the underlay address pool
Device failed to come online automatically
Used up VLAN IDs of downlink port on leaf device
IRF member device was not powered off during replacement
Starting data synchronization or auditing
Finishing data synchronization or auditing
Starting fine-grained synchronization
Finishing fine-grained synchronization
Track number allocation failure
Used up loopback interfaces on a device
Aggregate interface creation failure
Segment ID conflict between VLAN pool and VLAN-type network
NEW thread pool rejected tasks
Task rejected by the thread pool of the NERestconf module
NGFW resource creation failure
NGFW resource modification failure
NGFW resource deletion failure
NGFW resource creation with NETCONF failure
NGFW resource creation with NETCONF success
NGFW resource modification with NETCONF success
NGFW resource modification with NETCONF failure
Start of NGFWM configuration recovery on non-active leader controllers
End of NGFWM configuration recovery on non-active leader controllers
Changed NETCONF password successfully
Failed to change the NETCONF password
Failed to create image file upload path
Software upgrade or patching failed
Software upgrade or patching succeeded
Failed to back up device configuration file
Scheduled check executed successfully
Failed to execute scheduled check
Failed to create controller restore point
Failed to create device restore point
Failed to roll back controller configuration
Switchover to backup role failed
Switchover to backup role succeeded
Switchover to primary role failed
Switchover to primary role succeeded
Disaster recovery component deletion failure
IP version mismatch between vPort destination network segment and vPort IP
Mirroring destination profile with PHY-type vPort and without any destination IP address
IP version mismatch between OVS-type vPort VTEP IP and mirroring destination profile destination IP
Start of service chain configuration recovery on non-active leader controllers
End of service chain configuration recovery on non-active leader controllers
Successfully called the production interface
Failed to call the production interface
Successfully called the emulation interface
Failed to call the emulation interface
Failed to delete a VM template
Failed to delete simulation device configuration
Failed to create a VM template
Failed to obtain device configuration
Failed to obtain topology information
Failed to save the simulation device configuration
Failed to record user operations
Failed to update the VLAN-VXLAN interface mapping
Failed to create a network model
Failed to update a network model
Failed to delete a network model
Configuration deployment failure
Telemetry stream configuration deployment failure
Start of tenant configuration recovery on non-active leader controllers
End of tenant configuration recovery on non-active leader controllers
Task rejected by thread pool of tenant
Connected to vCenter successfully
Failed to disconnect from vCenter
Disconnected from vCenter successfully
Failed to update distributed port group QoS
Updated distributed port group QoS successfully
Failed to create distributed port group
Created distributed port group successfully
Failed to update distributed port group
Updated distributed port group successfully
Failed to delete distributed port group
Deleted distributed port group successfully
Added vPort to VSM successfully
Deleted vPort from VSM successfully
Failed to delete vPort from VSM
Updated vPort on VSM successfully
Failed to synchronize vPort information
Auto audit and sync completed for all vCenters
Added network overlay host to VSM successfully
Failed to add network overlay host to VSM
Deleted network overlay host from VSM successfully
Failed to delete network overlay host from VSM
Updated network overlay host on VSM successfully
Failed to update network overlay host on VSM
Failed to allocate VLAN IDs on NEM
Failed to obtain VLAN resource pool name on NEM
Failed to reclaim VLAN IDs on NEM
Failed to synchronize VLAN IDs on NEM
Failed to bind VLAN resource pool on NEM
Failed to unbind VLAN resource pool on NEM
Failed to obtain VLAN ID assignment information on NEM
Connected to RHVM successfully
Failed to disconnect from RHVM
Disconnected from RHVM successfully
Failed to create logical network
Created logical network successfully
Failed to update logical network
Updated logical network successfully
Failed to delete logical network
Deleted logical network successfully
Added vPort to VSM through RHVM successfully
Failed to add vPort to VSM through RHVM
Deleted vPort from VSM through RHVM successfully
Failed to delete vPort from VSM through RHVM
Updated vPort on VSM through RHVM successfully
Failed to update vPort on VSM through RHVM
Failed to create distributed port group
Auto audit and sync completed for all OpenStack-based cloud platforms
Connected to OpenStack successfully
Failed to connect to OpenStack
Created DHCP vPort successfully
Deleted DHCP vPort successfully
Connected to OpenStack controller node successfully
Disconnected from OpenStack controller node
Logical network creation failure because of data incorporation errors
RHVM data synchronization failure
Auto audit and sync completed for all RHVMs
Failed to start calendar-based audit for vCenters
Failed to start calendar-based audit for OpenStack-based cloud platforms
Failed to start calendar-based audit for RHVMs
Failed to push 1020V host information
Failed to bind gateway to tenant
Failed to unbind gateway from tenant
Failed to obtain gateway-tenant binding information
Failed to create vPort profile
Failed to delete vPort profile
Failed to create mirroring destination profile
Failed to delete mirroring destination profile
Failed to edit mirroring destination profile
Failed to verify whether a tenant has service resources
Failed to bind gateway to vRouter
Failed to unbind gateway from vRouter
Failed to verify whether a tenant exists
Failed to create routing table
Failed to delete routing table.
Failed to create vRouter interface
Failed to delete vRouter interface
Failed to edit network overlay host
Failed to delete network overlay group
Failed to delete network overlay host
Failed to create network overlay group
Failed to create network overlay host
Failed to create route entries
Failed to create VPC connection
Failed to delete VPC connection
Failed to create security group rule
Failed to edit security group rule
Failed to delete security group rule
Failed to create security group
Failed to delete security group
Failed to edit bare metal state
Failed to bind network port to VLAN-VXLAN mapping table
Failed to unbind network port from VLAN-VXLAN mapping table
Created routing table successfully
Deleted routing table successfully
Created network segment successfully
Deleted network segment successfully
Bound gateway to tenant successfully
Unbound gateway from tenant successfully
Bound vRouter to gateway successfully
Unbound vRouter from gateway successfully
Start of IPsec VPN configuration recovery on non-active leader controllers
End of IPsec VPN configuration recovery on non-active leader controllers
Failure to add host because of invalid license
vPort number reaching threshold
vPort number falling below threshold
Start of VSM configuration recovery on non-active leader controllers
End of VSM configuration recovery on non-active leader controllers
Compute node neighbor aging after a specific time period
LLDP neighbor relationship restoration between compute node host and device
LLDP neighbor relationship establishment between compute node host and device
LLDP neighbor relationship interruption between compute node host and device
Network node neighbor aging after a specific time period
LLDP neighbor relationship restoration between network node host and device
LLDP neighbor relationship establishment between network node host and device
LLDP neighbor relationship interruption between network node host and device
Failure to issue ACL rule because of insufficient hardware resources
Failure to issue default ACL rule because of insufficient hardware resources
Controller failed to communicate with host through OVSDB
Flow table synchronization or auditing started
Flow table synchronization or auditing finished
Host flow table issuing failure
Host group table issuing failure
Host MTU audit or sync started
Host MTU audit or sync finished
Network node established WebSocket connection to controller
Network node terminated WebSocket connection to controller
DHCP configuration auditing or synchronization started
DHCP configuration auditing or synchronization started finished
Introduction
System logs record internal events that occur on SNA Center. 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 controller products.
Viewing system log messages
1. Log in to SNA Center.
2. Click Settings in the System area.
3. On the top navigation bar, click Logs.
4. From the left navigation pane, select Information.
5. Click the System Logs tab.
The paginated system log message list is displayed, as shown in Figure 1.
Figure 1 System log message list
Table 1 System log message elements
Element |
Description |
Severity level |
Severity level of the log 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 SNA component that generated the log message. |
Host Name |
Name of the host that generated the log message. |
Service Name |
Name of the service that produced the log message. |
Description |
Text string that contains detailed information about the event or error. |
Syslog message format
SNA Center can send system logs to syslog servers through the syslog protocol. To configure system log output to syslog servers, go to the Logs > Configuration > System Logs page.
By default, SNA Center sends system logs to syslog servers 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 or IP address of the host 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. |
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 |
ARP |
ARP module. |
BGPM |
BGPM module. |
CLOSE_LOOP |
Issues module. |
CON_CERTM |
Certificate management module. |
CON_LICENSE |
License management module. |
CON_MONITOR |
Operating information module. |
CON_NETCONF |
NETCONF module. |
CON_NetworkMonitor |
Network health monitor module. |
CON_OAM |
OAM module. |
CON_OPENFLOW |
OpenFlow module. |
CON_PortMonitor |
Port statistics module. |
CON_REGION |
Region module. |
CON_SNMP |
SNMP module. |
CON_SYSTEM |
System management module. |
CON_TEAM |
Team module. |
CON_USER |
User management module. |
DataCheck |
Data check module. |
DHCP |
DHCP module. |
F5aaS |
F5 service module. |
FWaaS |
Firewall service module. |
LBaaS |
Load balancing service module. |
NEM |
Carrier network module. |
NGFWM |
NGFW manager module. |
OAM |
OAM module. |
RDR |
Remote disaster recovery module. |
SEERENGINE |
SeerEngine module. |
ServiceChain |
Service chain module. |
Tenant |
Tenant management module. |
VMM |
Virtual networking module. |
VPNaaS |
IPsec VPN service module. |
VSM |
Virtual network module. |
Syslog messages are classified into eight severity levels from 0 to 7. The lower the number, the higher the severity, as shown in Table 4.
Table 4 Syslog message severity levels
Level |
Severity |
Description |
0 |
Emergency |
The system is unusable. |
1 |
Alert |
Action must be taken immediately. |
2 |
Critical |
Critical condition. |
3 |
Error |
Error condition. |
4 |
Warning |
Warning condition. |
5 |
Notice |
Normal but significant condition. |
6 |
Informational |
Informational message. |
7 |
Debug |
Debugging message. |
System log messages are classified into five severity levels from 0 to 4. The higher the number, the higher the severity, as shown in Table 5.
Table 5 System log message severity levels
Level |
Icon |
Severity |
Description |
0 |
Info |
Information message. |
|
1 |
Warning |
Warning condition. |
|
2 |
Error |
Error condition. |
|
3 |
Serious |
Serious condition. |
|
4 |
Critical |
Critical condition. |
Table 6 shows the mappings between system log message severity levels and syslog message severity levels.
Table 6 Severity level mappings
System log message severity level |
Syslog message severity level |
0 |
6 |
1 |
4 |
2 |
3 |
3 |
2 |
4 |
0 |
Using this document
This document categories system log messages by service module. This document explains messages in tables. Table 7 describes information provided in these tables.
Table 7 Message explanation table contents
Item |
Content |
Example |
Keyword |
Summary of the message that facilitates searching or memorizing. |
OPENFLOW_SESSION_UP |
Message text |
Presents the message description. |
An OpenFlow device with datapath ID $1 OpenFlow IP $2 descriptor $3 was connected to the controller $4. |
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: Datapath ID of the OpenFlow device. $2: Management IP address of the OpenFlow device. $3: Description information about the OpenFlow device. $4: IP address of the controller. |
Severity level |
Provides the severity level of the message. |
|
Example |
Provides a real message example. |
An OpenFlow device with datapath ID 01:21:cc:3e:5f:09:04:7f OpenFlow IP 192.168.100.1 descriptor 192.168.200.1 was connected to the controller 10.10.10.1. |
Explanation |
Explains the message, including the event or error cause. |
An OpenFlow device was connected to the controller. |
Recommended action |
Provides recommended actions. For informational messages, no action is required. |
No action is required. |
ARP
This section contains ARP messages.
Failure to synchronize ARP bus messages
Keyword |
ARP_SYNC_FAILED |
Message text |
Failed to synchronize arp bus message. |
Variable fields |
N/A |
Severity level |
Warning |
Example |
Failed to synchronize arp bus message. |
Explanation |
The controllers in a team failed to synchronize ARP bus messages. |
Recommended action |
Verify that the network connections are correct among the controllers. |
Start of ARP configuration recovery on non-active leader controllers
Keyword |
BEGIN_RECOVER_ARP_CONFIG |
Message text |
All non-active leader controllers started recovering the ARP configuration. |
Variable fields |
N/A |
Severity level |
Info |
Example |
All non-active leader controllers started recovering the ARP configuration. |
Explanation |
All non-active leader controllers in the team started recovering the ARP configuration,. |
Recommended action |
As a best practice, do not perform any operations on the controllers during the configuration recovery process. |
End of ARP configuration recovery on non-active leader controllers
Keyword |
FINISH_RECOVER_ARP_CONFIG |
Message text |
All non-active leader controllers completed recovering the ARP configuration. |
Variable fields |
N/A |
Severity level |
Info |
Example |
All non-active leader controllers completed recovering the ARP configuration. |
Explanation |
All non-active leader controllers in the team completed recovering the ARP configuration. |
Recommended action |
No action is required. |
Migration times of the VM reached the maximum within the migration time period
Keyword |
ARP_MIGRATE_OVERFLOW |
Message text |
The VM (IP $1, MAC $2) failed to migrate to interface $3 of access device $4. The migration times of the VM have already reached the maximum within the migration time period. |
Variable fields |
$1: IP address of the VM. $2: MAC address of the VM. $3: Access interface number. $4: Management IP address of the access device. |
Severity level |
Warning |
Example |
The VM (IP 1.1.1.1, MAC 12:00:00:00:1b:87) failed to migrate to interface Ten-GigabitEthernet 1/0/1 of access device 172.16.68.1. The migration times of the VM have already reached the maximum within the migration time period. |
Explanation |
The migration times of the VM have reached the maximum within the migration time period. |
Recommended action |
1. Verify that migration operations for the VM have not reached the upper limit. 2. Verify that none of the following IP address conflicts occurs. If one of the IP conflicts occurs, ARP packets are generated and frequently delivered to the controller. As a result, the controller will move the VM frequently. ¡ VMs with different MAC address are assigned the same IP address. ¡ VMs in different VLANs are assigned the same IP address. ¡ VMs connected to different access interfaces are assigned the same IP address. ¡ VMs connected to different access devices are assigned the same IP address. |
Conflict between the VM MAC address and the gateway MAC address or reserved gateway MAC address
Keyword |
ARP_MAC_CONFLICT |
Message text |
The MAC address of VM (IP: $1, MAC: $2) that connects to interface $3 of access device $4 conflicts with the gateway MAC address or reserved gateway MAC address. |
Variable fields |
$1: IP address of the VM. $2: MAC address of the VM. $3: Access port number. $4: Management IP address of the access device. |
Severity level |
Warning |
Example |
The MAC address of VM (IP: 2.2.2.1, MAC: 3c:8c:40:4e:dd:46) that connects to interface BAGG2 of access device 172.16.68.4 conflicts with the gateway MAC address or reserved gateway MAC address. |
Explanation |
The VM MAC address conflicted with the gateway MAC address or the reserved gateway MAC address. |
Recommended action |
Modify the VM MAC address. |
BGPM
This section contains BGPM messages.
NETCONF configuration deployment failure
Keyword |
VBGP_NETCONF_CONFIG_FAILED |
Message text |
Failed to deploy NETCONF configuration of BGP node $1. ErrorReason: $2. The NETCONF configuration item is $3. |
Variable fields |
$1: IP address of the BGP node. $2: NETCONF configuration deployment failure reason. $3: NETCONF configuration item failed to be deployed. |
Severity level |
Warning |
Example |
Failed to deploy NETCONF configuration of BGP node192.168.10.11. ErrorReason: The specified address family doesn't exist. The NETCONF configuration item is <top xmlns="http://www.h3c.com/netconf/config:1.0"> <BGP> <Neighbors> <Neighbor> <Name>bgpins</Name> <VRF></VRF> <Family>9</Family> <SessAF>1</SessAF> <IpAddress>68.0.0.11</IpAddress> <Mask>255</Mask> </Neighbor> </Neighbors> </BGP> </top>. |
Explanation |
Failed to deploy NETCONF configuration to a vBGP node. |
Recommended action |
3. Verify that the controller and the NETCONF server are correct connected. 4. Verify that the configuration is correct. |
Two master nodes exist in a vBGP cluster
Keyword |
VBGP_DOUBLE_MASTER |
Message text |
vBGP cluster $1 has two master nodes: $2 and $3. |
Variable fields |
$1: vBGP cluster ID. $2: IP address of the first master node. $3: IP address of the second master node. |
Severity level |
Warning |
Example |
vBGP cluster 1 has two master nodes:192.168.10.11 and 192.168.10.22. |
Explanation |
Two master nodes exist in a vBGP cluster. |
Recommended action |
5. Verify that the vBGP nodes can communicate correctly. 6. Verify that the vBGP cluster and BGP instance configuration is correct. |
vBGP cluster restores master/backup mode
Keyword |
VBGP_MASTER_BACKUP |
Message text |
vBGP cluster $1 has restored to master/backup mode. Master node is $2 and backup node is $3. |
Variable fields |
$2: IP address of the master node. $3: IP address of the backup node. |
Severity level |
Info |
Example |
vBGP cluster 1 has restored to master/backup mode. Master node is 192.168.10.11 and backup node is 192.168.10.33. |
Explanation |
The vBGP cluster restored the master/backup mode. |
Recommended action |
No action is required. |
vBGP session being established
Keyword |
VBGP_PEER_SESSION_STATE |
Message text |
The state of the session between vBGP node $1 and peer $2 in instance $3 is $4. |
Variable fields |
$1: Management IP address of the vBGP node. $2: Peer IP address. $3: Instance name. $4: Session state. Options include Idle, Connect, Active, Openset, and Openconfirm. |
Severity level |
Info |
Example |
The state of the session between vBGP node 192.168.10.11 and peer 192.168.10.22 in instance A is Active. |
Explanation |
A vBGP session is being established. |
Recommended action |
If the vBGP session has not been established within a long period of time, verify the BGP configuration and IP connectivity between the BGP peers. |
vBGP session successfully established
VBGP_PEER_SESSION_STATE_ESTABLISHED |
|
Message text |
The state of the session between vBGP node $1 and peer $2 in instance $3 is Established. |
Variable fields |
$1: Management IP address of the vBGP node. $2: Peer IP address. $3: Instance name. |
Severity level |
Info |
Example |
The state of the session between vBGP node 192.168.10.11 and peer 192.168.10.22 in instance A is Established. |
Explanation |
A vBGP session was successfully established. |
Recommended action |
No action is required. |
The controller automatically deleted the master nodes of a dual-master vBGP cluster after the cluster was deleted
Keyword |
DUAL_MASTER_VBGP_CLUSTER_DELETED |
Message text |
Dual-master vBGP cluster $1 was deleted. Information about node $2 and node $3 in the cluster was deleted from the controller. |
Variable fields |
$1: vBGP cluster ID. $2: IP address of a master node. $3: IP address of another master node. |
Severity level |
Info |
Example |
Dual-master vBGP cluster 1 was deleted. Information about node 192.168.1.1 and node 192.168.1.2 in the cluster was deleted from the controller. |
Explanation |
Master nodes of a dual-master vBGP cluster were deleted from the controller after the cluster was deleted. |
Recommended action |
When the vBGP cluster still operates in dual-master mode after you delete the cluster from the controller, perform the following tasks: · Check whether the vBGP nodes can communicate with each other correctly. · Check whether the vBGP cluster and the BGP instance are configured correctly. |
CLOSE_LOOP
This section contains system messages generated by the Closed Loop module.
Failed to log in to SeerAnalyzer
Keyword |
LOGIN_SA_FAILED |
Message text |
Login to SeerAnalyzer $1 failed. |
Variable fields |
$1: URL of SeerAnalyzer. |
Severity level |
Error |
Example |
Login to SeerAnalyzer http://192.168.1.123:10080 failed. |
Explanation |
Failed to log in to SeerAnalyzer. |
Recommended action |
Check the SeerAnalyzer configuration and verify that SeerAnalyzer is operating correctly. |
Logged in to SeerAnalyzer successfully
Keyword |
LOGIN_SA_SUCCESS |
Message text |
Login to SeerAnalyzer $1 successfully. |
Variable fields |
$1: URL of SeerAnalyzer. |
Severity level |
Info |
Example |
Login to SeerAnalyzer http://192.168.1.123:10080 successfully. |
Explanation |
Logged in to SeerAnalyzer successfully. |
Recommended action |
No action is required. |
Failed to connect to SeerAnalyzer
Keyword |
CONNECT_SA_FAIL |
Message text |
Failed to connect to SeerAnalyzer $1. |
Variable fields |
$1: URL of SeerAnalyzer. |
Severity level |
Error |
Example |
Failed to connect to SeerAnalyzer http://192.168.1.123:10080. |
Explanation |
Failed to connect to SeerAnalyzer because the token cannot be retrieved. |
Recommended action |
Check the SeerAnalyzer configuration and verify that SeerAnalyzer is operating correctly. |
Connected to SeerAnalyzer successfully
Keyword |
CONNECT_SA_SUCCESS |
Message text |
Connected to SeerAnalyzer $1 successfully. |
Variable fields |
$1: URL of SeerAnalyzer. |
Severity level |
Info |
Example |
Connected to SeerAnalyzer http://192.168.1.123:10080 successfully. |
Explanation |
Connected to SeerAnalyzer successfully. |
Recommended action |
No action is required. |
Failed to synchronize fault event
Keyword |
SA_SYNC_FAULT_TO_CTL_FAILED |
Message text |
Failed to synchronize event: $1 |
Variable fields |
$1: Fault event details. |
Severity level |
Error |
Example |
Failed to synchronize event: { "faultSource": "SA", "faultName": "A switch is repeatedly rebooted", "faultName_en": "An IP address conflict is detected on the network side.", "faultId": "18bc6492-41cc-4bef-aaed-a58cc49999e4", "saIp": "192.158.25.79", "time": "2020-12-16 16:10:49", "faultObject": "Device: 192.158.25.95", "device": "192.158.25.95", "severity": 1, "eventType": 2, "suggestionList": [ { "action": "IsolatedSwitch", "description": "Use the shutdown command to shut down the port. This operation might interrupt services. Use this solution with caution.", "description_en": "Please operate with caution.", "priority": 12, "detail": [ { "deviceIp": "192.158.25.95", "deviceName": "2595" } ] } ] } |
Explanation |
SeerAnalyzer failed to synchronize fault event information to the Closed Loop microservice. |
Recommended action |
Check the diagnostic logs to locate the cause for the failure. |
Fault event successfully synchronized
Keyword |
SA_SYNC_FAULT_TO_CTL_SUCCESS |
Message text |
Successfully synchronized event: $1 |
Variable fields |
$1: Fault event details. |
Severity level |
Info |
Example |
Successfully synchronized event: { "faultSource": "SA", "faultName": "A switch is repeatedly rebooted", "faultName_en": "An IP address conflict is detected on the network side.", "faultId": "18bc6492-41cc-4bef-aaed-a58cc49999e4", "saIp": "192.158.25.79", "time": "2020-12-16 16:10:49", "faultObject": "Device:192.158.25.95", "device": "192.158.25.95", "severity": 1, "eventType": 2, "suggestionList": [ { "action": "IsolatedSwitch", "description": "Use the shutdown command to shut down the port. This operation might interrupt services. Use this solution with caution.", "description_en": "Please operate with caution.", "priority": 12, "detail": [ { "deviceIp": "192.158.25.95", "deviceName": "2595" } ] } ] } |
Explanation |
SeerAnalyzer successfully synchronized fault event information to the Closed Loop microservice. |
Recommended action |
No action is required. |
Failed to update fault event
Keyword |
SA_UPDATE_FAULT_TO_CTL_FAILED |
Message text |
Failed to update event $1: $2. |
Variable fields |
$1: UUID of the event. $2: Fault event details. |
Severity level |
Error |
Example |
Failed to update event bb8bb083-c4a4-45eb-b5dc-2b251a7921f3: { "faultSource":"SA", "saIp": "192.158.25.79", "faultName":"A switch is repeatedly rebooted", "faultName_en":"An IP address conflict is detected on the network side.", "time":"2020-12-16 16:10:49", "faultObject":"Device:192.158.25.95","device":"192.158.25.95", "severity":1, "eventType":2, "suggestionList": [ { "action":"IsolatedSwitch", "description":"Use the shutdown command to shut down the port. This operation might interrupt services. Use this solution with caution.", "description_en":"Please operate with caution.", "priority":12, "detail": [ { "deviceIp":"192.158.25.95", "deviceName":"2595" } ] } ] } |
Explanation |
SeerAnalyzer failed to update the fault event information in the Closed Loop microservice. |
Recommended action |
Check the diagnostic logs to locate the cause for the failure. |
Updated fault event successfully
Keyword |
SA_UPDATE_FAULT_TO_CTL_SUCCESS |
Message text |
Successfully updated event $1: $2 |
Variable fields |
$1: UUID of the event. $2: Fault event details. |
Severity level |
Info |
Example |
Successfully updated event bb8bb083-c4a4-45eb-b5dc-2b251a7921f3: { "faultSource":"SA", "saIp": "192.158.25.79", "faultName":"A switch is repeatedly rebooted", "faultName_en":"An IP address conflict is detected on the network side.", "time":"2020-12-16 16:10:49", "faultObject":"Device:192.158.25.95", "device":"192.158.25.95", "severity":1, "eventType":2, "suggestionList": [ { "action":"IsolatedSwitch", "description":"Use the shutdown command to shut down the port. This operation might interrupt services. Use this solution with caution.", "description_en":"Please operate with caution.", "priority":12, "detail": [ { "deviceIp":"192.158.25.95", "deviceName":"2595" } ] } ] } |
Explanation |
SeerAnalyzer successfully updated the fault event information in the Closed Loop microservice. |
Recommended action |
No action is required. |
Failed to update the fault event state
Keyword |
SA_UPDATE_FAULT_STATUS_TO_CTL_FAILED |
Message text |
Updating event $1 status $2 failed. |
Variable fields |
$1: UUID of the event. $2: New fault event state. |
Severity level |
Error |
Example |
Updating event bb8bb083-c4a4-45eb-b5dc-2b251a7921f3 status 1 failed. |
Explanation |
SeerAnalyzer failed to update the fault event state in the Closed Loop microservice. |
Recommended action |
Check the diagnostic logs to locate the cause for the failure. |
Updated fault event state successfully
Keyword |
SA_UPDATE_FAULT_STATUS_TO_CTL_SUCCESS |
Message text |
Updated event $1 status $2 successfully. |
Variable fields |
$1: UUID of the event. $2: New fault event state. |
Severity level |
Info |
Example |
Updated event bb8bb083-c4a4-45eb-b5dc-2b251a7921f3 status 1 successfully. |
Explanation |
SeerAnalyzer updated the fault event state in the Closed Loop microservice successfully. |
Recommended action |
No action is required. |
Failed to synchronize the closed state of an event
Keyword |
CTL_SYNC_FAULT_CLOSED_STATUS_TO_SA_FAILED |
Message text |
Failed to synchronize the closed state of event $1. |
Variable fields |
$1: UUID of the event. |
Severity level |
Error |
Example |
Failed to synchronize the closed state of event bb8bb083-c4a4-45eb-b5dc-2b251a7921f3. |
Explanation |
The Closed Loop microservice failed to synchronize the closed state of a fault event to SeerAnalyzer. |
Recommended action |
Check the diagnostic logs to locate the cause for the failure. |
Synchronized the closed state of an event successfully
Keyword |
CTL_SYNC_FAULT_CLOSED_STATUS_TO_SA_SUCCESS |
Message text |
Successfully synchronized the closed state of event $1. |
Variable fields |
$1: UUID of the event. |
Severity level |
Info |
Example |
Successfully synchronized the closed state of event bb8bb083-c4a4-45eb-b5dc-2b251a7921f3. |
Explanation |
The Closed Loop microservice successfully synchronized the closed state of a fault event to SeerAnalyzer. |
Recommended action |
No action is required. |
Sent port isolation request successfully
Keyword |
ISOLATED_PHYSICAL_PORT_SUCCESS |
Message text |
Successfully sent port isolation request. |
Variable fields |
N/A |
Severity level |
Info |
Example |
Successfully sent port isolation request. |
Explanation |
The Closed Loop microservice sent a port isolation request to the corresponding device successfully. |
Recommended action |
No action is required. |
Failed to send a port isolation request
Keyword |
ISOLATED_PHYSICAL_PORT_FAILED |
Message text |
Failed to send port isolation request. |
Variable fields |
N/A |
Severity level |
Error |
Example |
Failed to send port isolation request. |
Explanation |
The Closed Loop microservice failed to send a port isolation request to the corresponding device. |
Recommended action |
Check the diagnostic logs to locate the cause for the failure. |
Sent request for adding configuration fragment successfully
Keyword |
ADD_CONFIGURATION_FRAGMENT_SUCCESS |
Message text |
Successfully sent request for adding configuration fragment. |
Variable fields |
N/A |
Severity level |
Info |
Example |
Successfully sent request for adding configuration fragment. |
Explanation |
The Closed Loop microservice sent a request for adding configuration fragment successfully. |
Recommended action |
No action is required. |
Failed to send request for adding configuration fragment
Keyword |
ADD_CONFIGURATION_FRAGMENT_FAILED |
Message text |
Failed to send request for adding configuration fragment. |
Variable fields |
N/A |
Severity level |
Error |
Example |
Failed to send request for adding configuration fragment. |
Explanation |
The Closed Loop microservice failed to send a request for adding configuration fragment to the controller. |
Recommended action |
Verify that the controller service is available and that the controller port is working correctly. |
Sent configuration fragment deployment request
Keyword |
SEND_CONFIGURATION_FRAGMENT_SUCCESS |
Message text |
Successfully sent request for deploying configuration fragment. |
Variable fields |
N/A |
Severity level |
Info |
Example |
Successfully sent request for deploying configuration fragment. |
Explanation |
The Closed Loop microservice successfully sent a request for adding configuration fragment to the controller. |
Recommended action |
No action is required. |
Failed to send configuration fragment deployment request
Keyword |
SEND_CONFIGURATION_FRAGMENT_FAILED |
Message text |
Failed to send request for deploying configuration fragment. |
Variable fields |
N/A |
Severity level |
Error |
Example |
Failed to send request for deploying configuration fragment. |
Explanation |
The Closed Loop microservice failed to send a request for adding configuration fragment to the controller. |
Recommended action |
Verify that the controller service is available and that the controller port is working correctly. |
Synchronized event resolution solution to SeerAnalyzer successfully
Keyword |
SYNC_SA_ACTION_STATUS_SUCCESS |
Message text |
Successfully synchronized event state to SeerAnalyzer. |
Variable fields |
N/A |
Severity level |
Info |
Example |
Successfully synchronized event state to SeerAnalyzer. |
Explanation |
The Closed Loop microservice successfully synchronized event the resolution solution to SeerAnalyzer. |
Recommended action |
No action is required. |
Failed to synchronize event resolution solution to SeerAnalyzer
Keyword |
SYNC_SA_ACTION_STATUS_FAILED |
Message text |
Failed to synchronize event state to SeerAnalyzer. |
Variable fields |
N/A |
Severity level |
Error |
Example |
Failed to synchronize event state to SeerAnalyzer. |
Explanation |
The Closed Loop microservice failed to synchronize the event resolution solution to SeerAnalyzer. |
Recommended action |
Verify that the controller service is available and that the controller port is working correctly. |
Sent NETCONF configuration deployment request successfully
Keyword |
SEND_CONFIGURATION_NETCONF_SUCCESS |
Message text |
Sent NETCONF configuration request to DC successfully. |
Variable fields |
N/A |
Severity level |
Info |
Example |
Sent NETCONF configuration request to DC successfully. |
Explanation |
The Closed Loop microservice successfully sent a NETCONF configuration deployment request to the controller. |
Recommended action |
No action is required. |
Failed to send NETCONF configuration deployment request
Keyword |
SEND_CONFIGURATION_NETCONF_FAILED |
Message text |
Failed to send NETCONF configuration request to DC. |
Variable fields |
N/A |
Severity level |
Error |
Example |
Failed to send NETCONF configuration request to DC. |
Explanation |
The Closed Loop microservice failed to send a NETCONF configuration deployment request to the controller. |
Recommended action |
· Verify that the controller service is available and that the controller port is working correctly. · Verify that the device supports NETCONF. · Verify that the NETCONF connection to the device is available. |
CON_CERTM
This section contains certificate management messages.
Service registration
Keyword |
CERTM_SERVICE_REGISTER |
Message text |
The $1 service $2 registration $3 |
Variable fields |
$1: Service name. $2: List of built-in certificate names (optional). $3: Registration result. |
Severity level |
Info |
Example |
· The License Client service {k.pem, c.epm, ca.pem} registration succeeded. · The OpenFlow service registration failed. Reason: The user role doesn't provide the permission to perform the operation. |
Explanation |
The user performed service registration with certificate management. |
Recommended action |
Check the registration result. If the registration fails, view the failure reason. |
Service deregistration
Keyword |
CERTM_SERVICE_UNREGISTER |
Message text |
The $1 service deregistration $2 |
Variable fields |
$1: Service name. $2: Deregistration result. |
Severity level |
Info |
Example |
· The OpenFlow service deregistration succeeded. · The OpenFlow service deregistration failed. Reason: The user role doesn't provide the permission to perform the operation. |
Explanation |
The user performed service deregistration with certificate management. |
Recommended action |
Check the deregistration result. If the deregistration fails, view the failure reason. |
Certificate reached alarm threshold
Keyword |
CERTIFICATE_WILL_EXPIRE |
Message text |
The certificate $1 for $2 service with subject "$3" will expire in $4 days. |
Variable fields |
$1: Certificate name. $2: Service name. $3: Subject information. $4: Remaining days of the certificate. |
Severity level |
Warning |
Example |
The certificate ca.p12 for OpenFlow service with subject " C=CN, ST=ZheJiang, L=Hangzhou, O=Hangzhou H3C Technologies Co., Ltd., CN=*.h3c.com" will expire in 20 days. |
Explanation |
The validity of the certificate has reached or dropped below the alarm threshold. |
Recommended action |
Replace the certificate in time. |
Certificate expired
Keyword |
CERTIFICATE_EXPIRED |
Message text |
The certificate $1 for $2 service with subject "$3" expired. |
Variable fields |
$1: Certificate name. $2: Service name. $3: Subject information. |
Severity level |
Warning |
Example |
The certificate ca.jks for OpenFlow service with subject " C=CN, ST=ZheJiang, L=Hangzhou, O=Hangzhou H3C Technologies Co., Ltd., CN=*.h3c.com" expired. |
Explanation |
The certificate has expired. |
Recommended action |
Replace the certificate in time. |
CON_LICENSE
This section contains CON_LICENSE messages.
License acquisition success
Keyword |
LICENSE_INSTALL |
Message text |
$1 license successfully obtained. |
Variable fields |
$1: License name. |
Severity level |
Info |
Example |
Base license successfully obtained. |
Explanation |
The specified license was successfully obtained. |
Recommended action |
No action is required. |
License acquisition failure
Keyword |
LICENSE_INSTALL_FAILED |
Message text |
Failed to obtain the $1 license. |
Variable fields |
$1: License name. |
Severity level |
Info |
Example |
Failed to obtain the base license. |
Explanation |
Failed to obtain the specified license. |
Recommended action |
Identify whether the license server has enough licenses. |
Single license reclaimed
Keyword |
LICENSE_RECLAIM |
Message text |
License for feature $1 (count: $2) has been reclaimed. |
Variable fields |
$1: Feature name. $2: Capacity of the reclaimed license. This field is displayed only when a quantity-based license is reclaimed. |
Severity level |
Warning |
Example |
License for feature VirtualServiceNode (count: 100) has been reclaimed. |
Explanation |
The license for the specified feature was reclaimed. |
Recommended action |
No action is required. |
License server connection
Keyword |
LICENSE_SERVER_CONNECT |
Message text |
The controller established a connection to the license server. |
Variable fields |
N/A |
Severity level |
Info |
Example |
The controller established a connection to the license server. |
Explanation |
The controller established a connection to the license server. |
Recommended action |
No action is required. |
Disconnection from the license server
Keyword |
LICENSE_SERVER_DISCONNECT |
Message text |
The controller was disconnected from the license server. |
Variable fields |
N/A |
Severity level |
Warning |
Example |
The controller was disconnected from the license server. |
Explanation |
The controller was disconnected from the license server. |
Recommended action |
If you disconnect the controller from the license server, no action is required. If the disconnection is unexpected, follow these steps: 7. Verify the connectivity between the controller and the license server. 8. Verify that the license server settings on the controller are correct. 9. Verify that the license server is operating correctly and providing services. |
Failure of connection to the license server
Keyword |
LICENSE_SERVER_CONNECT_FAILED |
Message text |
Failed to connect to the license server. |
Variable fields |
N/A |
Severity level |
Warning |
Example |
Failed to connect to the license server. |
Explanation |
The controller failed to connect to the license server. |
Recommended action |
10. Verify that the license server settings on the controller are correct. 11. Verify that the license server is operating correctly. |
Controller forced offline by license server
Keyword |
LICENSE_SERVER_FORCE_CLIENT_OFFLINE |
Message text |
The controller was forced offline by license server. |
Variable fields |
N/A |
Severity level |
Warning |
Example |
The controller was forced offline by license server. |
Explanation |
The license server forced the controller to go offline. |
Recommended action |
Reconnect the controller to the license server if you want to authorize the controller again. |
Reconnection to the license server
Keyword |
LICENSE_SERVER_AGED_RECONNECT |
Message text |
The controller started to reconnect to the license server because the token of the controller aged out. |
Variable fields |
N/A |
Severity level |
Warning |
Example |
The controller started to reconnect to the license server because the token of the controller aged out. |
Explanation |
The token of the controller aged out and the controller started to reconnect to the license server. |
Recommended action |
Verify the network connectivity between the license server and the controller. |
Entered fail-safe state due to authorization failure
Keyword |
ENTER_FAILSAFE_NO_LICENSE |
Message text |
The controller entered into fail-safe mode because it failed to obtain licenses from the remote license server. |
Variable fields |
N/A |
Severity level |
Warning |
Example |
The controller entered into fail-safe mode because it failed to obtain licenses from the remote license server. |
Explanation |
After the controller connected to the license server, the controller failed to obtain a license and entered fail-safe state. |
Recommended action |
Log in to the license server and verify that a license is available for the controller. |
Entered fail-safe state due to connection failure
Keyword |
ENTER_FAILSAFE_CONNECT_FAILED |
Message text |
The controller entered into fail-safe mode because a connection error occurred between the controller and the license server. |
Variable fields |
N/A |
Severity level |
Warning |
Example |
The controller entered into fail-safe mode because a connection error occurred between the controller and the license server. |
Explanation |
The controller lost its connection to the license server and entered fail-safe state. |
Recommended action |
Verify the network connectivity between the license server and the controller. |
Exited fail-safe state after the fail-safe period
Keyword |
EXIT_FAILSAFE_EXPIRED |
Message text |
The controller exited from fail-safe mode because the 30-day fail-safe period expired. |
Variable fields |
N/A |
Severity level |
Warning |
Example |
The controller exited from fail-safe mode because the 30-day fail-safe period expired. |
Explanation |
The 30-day fail-safe period expired and the controller exited fail-safe state. |
Recommended action |
12. On the license management page, verify that the controller is connected to the license server. 13. Verify that the license server can assign a license to the controller. |
Exited fail-safe state after authorization
Keyword |
EXIT_FAILSAFE_OBTAINED |
Message text |
The controller exited from fail-safe mode because it had obtained licenses from the license server. |
Variable fields |
N/A |
Severity level |
Warning |
Example |
The controller exited from fail-safe mode because it had obtained licenses from the license server. |
Explanation |
The controller obtained a license and exited fail-safe state. |
Recommended action |
No action is required. |
Exited fail-safe state after disconnection
Keyword |
EXIT_FAILSAFE_DISCONNECTED |
Message text |
The controller exited from fail-safe mode because it disconnected from the license server. |
Variable fields |
N/A |
Severity level |
Warning |
Example |
The controller exited from fail-safe mode because it disconnected from the license server. |
Explanation |
The controller closed its connection to the license server and exited fail-safe state. |
Recommended action |
No action is required. |
Remote license expiration pre-warning
Keyword |
LICENSE_EXPIRED |
Message text |
$1 license is about to expire in 10 days. |
Variable fields |
$1: Remote license name. |
Severity level |
Warning |
Example |
Base license is about to expire in 10 days. |
Explanation |
The specified remote license is about to expire in 10 days. |
Recommended action |
14. Log in to the license server to verify that the remote license is authorized. 15. If the remote license is not authorized, purchase the license. |
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 |
Critical |
Example |
Insufficient MaxNodeNum licenses. Please purchase more licenses. |
Explanation |
The number of quantity-based licenses is insufficient. |
Recommended action |
Purchase more licenses. |
CON_MONITOR
This section contains CON_MONITOR messages.
CPU usage exceeded threshold
Keyword |
CPU_USAGE_EXCEED_THRESHOLD |
Message text |
CPU usage $1 exceeded the threshold $2. |
Variable fields |
$1: Current CPU usage. $2: CPU usage threshold. |
Severity level |
Warning |
Example |
CPU usage 91% exceeded the threshold 90%. |
Explanation |
The CPU usage of the system exceeded the threshold. |
Recommended action |
· Verify that the CPU usage threshold is appropriate. · Verify that the controller does not load too many services. If too many services are loaded, you can transfer some services to other controllers in the team or increase the CPU resources of the physical server. |
CPU usage dropped below threshold
Keyword |
CPU_USAGE_UNDER_THRESHOLD |
Message text |
CPU usage $1 dropped below the threshold $2. |
Variable fields |
$1: Current CPU usage. $2: CPU usage threshold. |
Severity level |
Info |
Example |
CPU usage 80% dropped below the threshold 90%. |
Explanation |
The CPU usage of the system dropped below the threshold. |
Recommended action |
No action is required. |
Memory usage exceeded threshold
Keyword |
MEMORY_USAGE_EXCEED_THRESHOLD |
Message text |
Memory usage $1 exceeded the threshold $2. |
Variable fields |
$1: Current memory usage. $2: Memory usage threshold. |
Severity level |
Warning |
Example |
Memory usage 91% exceeded the threshold 90%. |
Explanation |
The memory usage of the system exceeded the threshold. |
Recommended action |
· Verify that the memory usage threshold is appropriate. · Verify that the controller does not load too many services. If too many services are loaded, you can transfer some services to other controllers in the team or increase the memory resources of the physical server. |
Memory usage dropped below threshold
Keyword |
MEMORY_USAGE_UNDER_THRESHOLD |
Message text |
Memory usage $1 dropped below the threshold $2. |
Variable fields |
$1: Current memory usage. $2: Memory usage threshold. |
Severity level |
Info |
Example |
Memory usage 80% dropped below the threshold 90%. |
Explanation |
The memory usage of the system dropped below the threshold. |
Recommended action |
No action is required. |
Disk usage exceeded threshold
Keyword |
DISK_USAGE_EXCEED_THRESHOLD |
Message text |
Disk usage $1 exceeded the threshold $2. |
Variable fields |
$1: Current disk usage. $2: Disk usage threshold. |
Severity level |
Warning |
Example |
Disk usage 91% exceeded the threshold 90%. |
Explanation |
The disk usage of the system exceeded the threshold. |
Recommended action |
· Verify that the disk usage threshold is appropriate. · Delete unneeded files, export service-irrelevant files to other devices, or increase the disk space of the physical server. |
Disk usage dropped below threshold
Keyword |
DISK_USAGE_UNDER_THRESHOLD |
Message text |
Disk usage $1 dropped below the threshold $2. |
Variable fields |
$1: Current disk usage. $2: Disk usage threshold. |
Severity level |
Info |
Example |
Disk usage 80% dropped below the threshold 90%. |
Explanation |
The disk usage of the system dropped below the threshold. |
Recommended action |
No action is required. |
Process memory usage exceeded threshold
Keyword |
PROCESS_MEMORY_USAGE_EXCEED_THRESHOLD |
Message text |
Memory usage $1% exceeded the alarm threshold $2% in $3 process, and $4 garbage collections had happened. |
Variable fields |
$1: Current memory usage. $2: Memory usage threshold. $3: Process name. $4: Number of GCs in the old generation. |
Severity level |
Warning |
Example |
Memory usage 91% exceeded the alarm threshold 90% in sdnc process, and 5 garbage collections had happened. |
Explanation |
The memory usage of the process exceeded the threshold, and GCs had happened. The memory might be exhausted. |
Recommended action |
· Check the number of services on the controller. If the controller has carried too many services, transfer some services to other controllers in the team. · Contact H3C Support. |
Process memory usage dropped below threshold
Keyword |
PROCESS_MEMORY_USAGE_EXCEED_THRESHOLD |
Message text |
Memory usage $1% dropped below the alarm threshold $2% in $3 process. |
Variable fields |
$1: Current memory usage. $2: Memory usage threshold. $3: Process name. |
Severity level |
Info |
Example |
Memory usage 80% dropped below the alarm threshold 90% in sdnc process. |
Explanation |
After exceeding the threshold, the memory usage of the process dropped below the threshold. |
Recommended action |
No action is required. |
Nonexistent thread pool
Keyword |
THREAD_POOL_NO_EXIST |
Message text |
Thread pool $1 does not exist. |
Variable fields |
$1: Thread pool name. |
Severity level |
Error |
Example |
Thread pool LinkBusPro does not exist. |
Explanation |
The specified thread pool does not exist. |
Recommended action |
Contact H3C Support. |
Inconsistency between daemon thread count and core pool size in a thread pool
Keyword |
THREAD_COUNT_IS_WRONG |
Message text |
Daemon thread count $1 is inconsistent with core pool size $2 in thread pool $3. |
Variable fields |
$1: Daemon thread count. $1: Core pool size. $1: Thread pool name. |
Severity level |
Error |
Example |
Daemon thread count 0 is inconsistent with core pool size 1 in thread pool LinkBusPro. |
Explanation |
The daemon thread count is inconsistent with the core pool size in the specified thread pool. |
Recommended action |
Contact H3C Support. |
CON_NETCONF
This section contains CON_NETCONF messages.
NETCONF session in up state
Keyword |
NETCONF_SESSION_UP |
Message text |
· The NETCONF session between the controller and NETCONF server $1 $2 was up. · The https NETCONF session between the controller and NETCONF server $1 was up. |
Variable fields |
$1: IP address of the NETCONF server. $2: Application name. |
Severity level |
Warning |
Example |
· The NETCONF session between the controller and NETCONF server 98.0.50.10 sdn.fabric.monitor was up. · The https NETCONF session between the controller and NETCONF server 98.0.50.10 was up. |
Explanation |
The NETCONF session between the controller and the NETCONF server was up. |
Recommended action |
No action is required. |
NETCONF session in down state
Keyword |
NETCONF_SESSION_DOWN |
Message text |
· The NETCONF session between the controller and NETCONF server $1 $2 was down. · The https NETCONF session between the controller and NETCONF server $1 was down. |
Variable fields |
$1: IP address of the NETCONF server. $2: Application name. |
Severity level |
Warning |
Example |
· The NETCONF session between the controller and NETCONF server 98.0.50.10 sdn.fabric.monitor was down. · The https NETCONF session between the controller and NETCONF server 98.0.50.10 was down. |
Explanation |
The NETCONF session between the controller and the NETCONF server was down. |
Recommended action |
To resolve the problem: 16. Verify the connectivity between the controller and the NETCONF server. 17. Examine whether the controller and the NETCONF server have the same NETCONF settings. If the controller and the NETCONF server have different NETCONF settings, modify the NETCONF settings on the controller or the NETCONF server. 18. Examine whether the maximum number of NETCONF sessions on the NETCONF server is reached. If the maximum number of NETCONF sessions is reached, delete unnecessary sessions or modify the upper limit of NETCONF sessions on the NETCONF server. |
Excessive response waiting time of the controller
Keyword |
NETCONF_SESSION_LONG_WAIT |
Message text |
The controller has waited more than $1 minutes for a response from NETCONF server $2 $3. Request content: $4 |
Variable fields |
$1: Time to wait for a response from the NETCONF server. $2: NETCONF server address. $3: Application name. $4: Request content. |
Severity level |
Warning |
Example |
The controller has waited more than 20 minutes for a response from NETCONF server 192.168.41.91 com.h3c.sdn.nem.nemapp. Request content: <OFP> <LogicalSwitches> <LogicalSwitch> <InstanceID></InstanceID> </LogicalSwitch> </LogicalSwitches> </OFP> |
Explanation |
The controller has spent too much time to wait for a response from the NETCONF server. |
Recommended action |
Examine whether the request content requires long configuration time. If this issue exists, contact H3C Support. |
Start of NETCONF configuration recovery on non-active leader controllers
Keyword |
BEGIN_RECOVER_NETCONF_CONFIG |
Message text |
All non-active leader controllers started recovering the NETCONF configuration. |
Variable fields |
N/A |
Severity level |
Info |
Example |
All non-active leader controllers started recovering the NETCONF configuration. |
Explanation |
All non-active leader controllers started recovering the NETCONF configuration, such as the NETCONF username and password. |
Recommended action |
As a best practice, do not perform any operations on the controllers during the configuration recovery process. |
End of NETCONF configuration recovery on non-active leader controllers
Keyword |
FINISH_RECOVER_NETCONF_CONFIG |
Message text |
All non-active leader controllers completed recovering the NETCONF configuration. |
Variable fields |
N/A |
Severity level |
Info |
Example |
All non-active leader controllers completed recovering the NETCONF configuration. |
Explanation |
All non-active leader controllers completed recovering the NETCONF configuration, such as the NETCONF username and password. |
Recommended action |
No action is required. |
NETCONF configuration deployment failure
Keyword |
NETCONF_FAILED |
Message text |
$1 |
Variable fields |
$1: Error packet sent from the NETCONF server. |
Severity level |
Warning |
Example |
<env:Envelope xmlns:env="http://www.w3.org/2003/05/soap-envelope"> <env:Body> <env:Fault> <env:Code> <env:Value>env:Sender</env:Value> </env:Code> <env:Reason> <env:Text lang=\"en\">Failed to log in.</env:Text> </env:Reason> </env:Fault> </env:Body> |
Explanation |
When the controller fails to deploy the NETCONF configuration to the NETCONF server, the NETCONF server returns an error packet to the controller. Only part of the content in the error packet is displayed in the log because the error packet is too large. |
Recommended action |
In this example, the configuration deployment failure is caused by controller login failure. To resolve this problem, verify that the controller uses the same NETCONF username and password as the NETCONF server. In other situations, take actions based on the content of the error packet or contact H3C Support. |
NETCONF SSH session authentication failure
Keyword |
NETCONF_SSH_AUTH_FAILED |
Message text |
Failed to create the NETCONF over SSH session between the controller and NETCONF server $1 $2. $3 |
Variable fields |
$1: NETCONF server IP address. $2: Application name. $3: Session creation failure reason. |
Severity level |
Warning |
Example |
Failed to create the NETCONF over SSH session between the controller and NETCONF server 98.0.50.10 sdn.fabric.monitor. Reason: Authentication failed. |
Explanation |
Failed to create a NETCONF SSH session between the controller and the NETCONF server. |
Recommended action |
· Verify that the NETCONF username and password are correctly configured. · Verify that the network is operating correctly. |
NETCONF HTTPS connection failure
Keyword |
DEVICE_NETCONF_CONNECT_FAILED |
Message text |
The NETCONF HTTPS connection failed on device $1. |
Variable fields |
$1: Device IP address. |
Severity level |
Warning |
Example |
The NETCONF HTTPS connection failed on device 192.168.203.16. |
Explanation |
The NETCONF HTTPS connection failed on a device |
Recommended action |
· Verify that the current software version of the device supports NETCONF. · Verify that the NETCONF HTTPS connection capability is enabled. |
CON_NetworkMonitor
This section contains CON_NetworkMonitor messages.
Unhealthy device operating status
Keyword |
MONITOR_DEVICE_ABNORMAL |
Message text |
Device operating status changed to unhealthy: IP address: $1 Device health score: $2 Reason: $3. |
Variable fields |
$1: IP address of the device. $2: Health score of the device. $3: Possible reason. |
Severity level |
Warning |
Example |
Device operating status changed to unhealthy: IP address: 192.168.67.206 Device health score: 25 Reason: · Memory usage has exceeded the level 2 alarm threshold. · CPU usage has exceeded the Level 2 Alarm Threshold. · Resource-ud usage has exceeded the Level 2 Alarm Threshold. · Resource-route usage has exceeded the Level 2 Alarm Threshold. |
Explanation |
This message is generated when the device health level is equal to or lower than 25. |
Recommended action |
Determine whether to handle the issue as required. |
Device operating status changes from unhealthy to healthy
Keyword |
MONITOR_DEVICE_NORMAL |
Message text |
Device operating status changed to healthy: IP address: $1 Device health score: $2 Reason: $3. |
Variable fields |
$1: IP address of the device. $2: Health score of the device. $3: Possible reason. |
Severity level |
Info |
Example |
Device operating status changed to healthy: IP address: 192.168.67.206 Device health score: 50 Reason: · Memory usage has dropped below the Level 2 Alarm Threshold. · CPU usage has dropped below the Level 2 Alarm Threshold. · Resource-ud usage has dropped below the Level 2 Alarm Threshold. · Resource-route usage has dropped below the Level 2 Alarm Threshold. |
Explanation |
This message is generated when the device health level increases above 25. |
Recommended action |
No action is required. |
Insufficient resources
Keyword |
DEVICE_NO_RESOURCE |
Message text |
$1 $2 of tenant $3 has a configuration deployment exception on device {DevName} Details of the exception: {Reason}. Device error message: {DevErrMsg}. Device location information: Chassis {},Slot {}. |
Variable fields |
$1: Resource type, for example, vPort. $2: Resource name, for example, a vPort name. $3: Tenant name. This field displays N/A for a resource that is not tenant-specific. $4: Device name. $5: Failure reason. $6: Error message. $7: Chassis number. This field displays N/A if the chassis number is not available. $8: Slot number. This field displays N/A if the slot number is not available. |
Severity level |
Error |
Example |
vPort 33 of tenant 11 has a configuration deployment exception on device 01. Details of the exception: Failed to apply a policy. Device error message: Failed to apply an ACL rule to interface ten-gigabitethernet 1/0/1 on node 3. Device location information: Chassis N/A, Slot N/A. |
Explanation |
This message is generated when the device has insufficient resources. |
Recommended action |
No action is required. |
CON_OAM
This section contains CON_OAM messages.
Periodic radar detection task failure
Keyword |
PERIODIC_DETECTION_FAILED |
Message text |
Periodic radar detection task failed: $1 |
Variable fields |
$1: Periodic radar detection task parameters. |
Severity level |
Warning |
Example |
Periodic radar detection task failed: Path type: single Network type: vxlan Segment ID: 2 Source IP: 172.71.1.5 Start device IP: 192.168.106.3 Start device ingress port: --- Destination IP: 172.172.1.2 End device IP: --- |
Explanation |
A periodic radar detection task might contain one or more scanning tasks. This message is generated when a scanning task fails. |
Recommended action |
If the failure is caused by active leader switchover, perform the periodic radar detection task again after the switchover. If the failure is caused by other reasons, perform the following operations: · Verify that the start device is not faulty and the start device ingress port operates correctly. · Verify that the sending of LLDP packets to the controller is enabled. If the feature is disabled, enable it in the Link component by navigating to System > Parameters. |
Periodic radar detection task result changes from failure to success
Keyword |
PERIODIC_DETECTION_CHANGE__SUCCEEDED |
Message text |
Periodic radar detection task result changed from failure to success: $1 |
Variable fields |
$1: Periodic radar detection task parameters. |
Severity level |
Info |
Example |
Periodic radar detection task result changed from failure to success: Path type: single Network type: vxlan Segment ID: 2 Source IP: 172.71.1.5 Start device IP: 192.168.106.3 Start device ingress port: XGE2/0/1 Destination IP: 172.172.1.2 End device IP: 192.168.70.68 |
Explanation |
A periodic radar detection task might contain one or more scanning tasks. This message is generated when the previous scanning task fails but the current task succeeds. |
Recommended action |
No action is required. |
CON_OPENFLOW
This section contains CON_OPENFLOW messages.
Abnormal OpenFlow connection
Keyword |
OPENFLOW_CONNECT_ERROR |
Message text |
$1 |
Variable fields |
$1: Abnormal connection information. |
Severity level |
Warning |
Example |
N/A |
Explanation |
An OpenFlow connection was abnormal. |
Recommended action |
Take actions according to the prompted abnormal connection information. |
Successful OpenFlow connection
Keyword |
OPENFLOW_SESSION_UP |
Message text |
An OpenFlow device with datapath ID $1 openflow ip $2 descriptor $3 was connected to the controller $4. |
Variable fields |
$1: Datapath ID of the OpenFlow device. $2: Management IP address of the OpenFlow device. $3: Description information about the OpenFlow device. $4: IP address of the controller. |
Severity level |
Info |
Example |
An OpenFlow device with datapath ID 01:21:cc:3e:5f:09:04:7f openflow ip 192.168.100.1 descriptor 192.168.200.1 was connected to the controller 10.10.10.1. |
Explanation |
An OpenFlow device was connected to the controller. |
Recommended action |
No action is required. |
Disconnected OpenFlow connection
Keyword |
OPENFLOW_SESSION_DOWN |
Message text |
An OpenFlow device with datapath ID $1 openflow ip $2 descriptor $3 was disconnected from the controller $4. |
Variable fields |
$1: Datapath ID of the OpenFlow device. $2: Management IP address of the OpenFlow device. $3: Description information about the OpenFlow device. $4: IP address of the controller. |
Severity level |
Warning |
Example |
An OpenFlow device with datapath ID 01:21:cc:3e:5f:09:04:7f openflow ip 192.168.100.1 descriptor 192.168.200.1 was disconnected from the controller 10.10.10.1. |
Explanation |
An OpenFlow device was disconnected from the controller. |
Recommended action |
Log in to the operating system where the controller is installed, and use the ping command to test the connectivity between the controller and OpenFlow device. · Specify the IP address used by the controller to join the team as the source IP. · Specify the management IP address of the OpenFlow device as the destination IP. Log in to the OpenFlow device to verify that the OpenFlow configuration is correct. |
OpenFlow port in up state
Keyword |
OPENFLOW_DEVPORT_UP |
Message text |
Port $1 of an OpenFlow device with datapath ID $2 management IP $3 was up. |
Variable fields |
$1: Name of a physical port. $2: Datapath ID of an OpenFlow device. $3: Management IP address of the OpenFlow device. |
Severity level |
Info |
Example |
Port FGE1/0/1 of an OpenFlow device with datapath ID 01:21:cc:3e:5f:09:04:7f management IP 192.168.1.1 was up. |
Explanation |
A port on an OpenFlow device came up. |
Recommended action |
No action is required. |
OpenFlow port in down state
Keyword |
OPENFLOW_DEVPORT_DOWN |
Message text |
Port $1 of an OpenFlow device with datapath ID $2 management IP $3 was down. |
Variable fields |
$1: Name of a physical port. $2: Datapath ID of an OpenFlow device. $3: Management IP address of the OpenFlow device. |
Severity level |
Warning |
Example |
Port FGE1/0/1 of an OpenFlow device with datapath ID 01:21:cc:3e:5f:09:04:7f management IP 192.168.1.1 was down. |
Explanation |
A port on an OpenFlow device went down. |
Recommended action |
If the message appears when the OpenFlow device reports its port information to the controller upon connecting to the controller, no action is required. If the message appears in other situations, verify that the physical port operates correctly and the link where the port resides is up. |
OpenFlow port removed
Keyword |
OPENFLOW_DEVPORT_REMOVED |
Message text |
Port $1 of an OpenFlow device with datapath ID $2 management IP $3 was removed. |
Variable fields |
$1: Name of a port. $2: Datapath ID of an OpenFlow device. $3: Management IP address of the OpenFlow device. |
Severity level |
Info |
Example |
Port FGE1/0/1 of an OpenFlow device with datapath ID 01:21:cc:3e:5f:09:04:7f management IP 192.168.1.1 was removed. |
Explanation |
A port on an OpenFlow device was removed. |
Recommended action |
If the message appears when you delete or move a VM, no action is required. If the message appears in other situations, verify that the physical port operates correctly. |
Failure to deploy flow entries
Keyword |
OPENFLOW_ADD_FLOWTABLE_FAILED |
Message text |
$1. The OpenFlow device with datapath ID $2 manager ip $3 failed to add the flow table $4. |
Variable fields |
$1: Error information returned by the OpenFlow device. $2: Datapath ID of the OpenFlow device. $3: Management IP address of the OpenFlow device. $4: Flow table information. |
Severity level |
Warning |
Example |
BAD_FIELD. The OpenFlow device with datapath ID 01:21:cc:3e:5f:09:04:7f manager ip 192.168.10.10 failed to add the flow table [tableId:1,Priority:29999,cookie0x2555364126,Matches:{“vxlan_reserved”:”0xFE”}]. |
Explanation |
The controller failed to deploy flow entries to the specified OpenFlow device. |
Recommended action |
The controller deploys several flow entries to the OpenFlow device by default. If the OpenFlow device does not support such flow entries, update the OpenFlow device as required. If the flow entries are deployed through REST API, modify the flow entries according to the error information returned and then deploy the flow entries again. |
Packet-in message rate reaches threshold on controller
Keyword |
OPENFLOW_CON_PACKETIN_EXCEED |
Message text |
The Packet-in message rate has reached the threshold on the controller. The current rate is $1 pps. |
Variable fields |
$1: Current packet-in message rate on the controller, in pps. |
Severity level |
Warning |
Example |
The Packet-in message rate has reached the threshold on the controller. The current rate is 8 pps. |
Explanation |
The packet-in message rate reached the threshold on the controller. |
Recommended action |
Modify the threshold for packet-in message rate on the controller. |
Packet-in message rate reaches threshold on OpenFlow device
Keyword |
OPENFLOW_DEV_PACKETIN_EXCEED |
Message text |
The Packet-in message rate has reached the threshold on OpenFlow device with DPID $1 and management IP $2. The current rate is $3 pps. |
Variable fields |
$1: Datapath ID of the OpenFlow device. $2: Management IP address of the OpenFlow device. $3: Current packet-in message rate on the OpenFlow device, in pps. |
Severity level |
Warning |
Example |
The Packet-in message rate has reached the threshold on OpenFlow device with DPID 00:00:00:00:00:01 and management IP 192.168.109.10. The current rate is 10 pps. |
Explanation |
The packet-in message rate reached the threshold on the OpenFlow device. |
Recommended action |
Modify the threshold for packet-in message rate on the OpenFlow device. |
Packet-in message rate reaches threshold on OpenFlow device port
Keyword |
OPENFLOW_PORT_PACKETIN_EXCEED |
Message text |
The Packet-in message rate has reached the threshold on port $1 of OpenFlow device with DPID $2 and management IP $3. The current rate is $4 pps. |
Variable fields |
$1: Number of the port on the OpenFlow device. $2: Datapath ID of the OpenFlow device. $3: Management IP address of the OpenFlow device. $4: Current packet-in message rate on the OpenFlow device's port, in pps. |
Severity level |
Warning |
Example |
The Packet-in message rate has reached the threshold on port 68 of OpenFlow device with DPID 00:00:00:00:00:01 and management IP 192.168.109.11. The current rate is 15 pps. |
Explanation |
The packet-in message rate reached the threshold on the OpenFlow device's port. |
Recommended action |
Modify the threshold for packet-in message rate on the OpenFlow device's ports. |
CON_PortMonitor
This section contains CON_PortMonitor messages.
Change of port operating status from healthy to unhealthy
Keyword |
MONITOR_PORT_ABNORMAL |
Message text |
Port operating status changed to unhealthy: Device IP address: $1 Port name: $2 Inbound bandwidth usage: $3 Outbound bandwidth usage: $4 Inbound error packet rate: $5 Outbound error packet rate: $6 Inbound packet loss rate: $7 Outbound packet loss rate: $8 |
Variable fields |
$1: IP address of the device. $2: Port name. $3: Inbound bandwidth usage. $4: Outbound bandwidth usage. $5: Inbound error packet rate. $6: Outbound error packet rate. $7: Inbound packet loss rate. $8: Outbound packet loss rate. |
Severity level |
Warning |
Example |
Port operating status changed to unhealthy: Device IP address: 172.16.100.222 Port name: G1/0/1 Inbound bandwidth usage: 10% Outbound bandwidth usage: 10% Inbound error packet rate: 10% Outbound error packet rate: 10% Inbound packet loss rate: 10% Outbound packet loss rate: 10% |
Explanation |
This message is generated when the port operating status changes to unhealthy. The status change can be caused by the following threshold exceeding events: · The bandwidth usage exceeds the threshold. · The error packet rate exceeds the threshold. · The packet loss rate exceeds the threshold. |
Recommended action |
Take actions based on the causes |
Change of port operating status from unhealthy to healthy
Keyword |
MONITOR_PORT_NORMAL |
Message text |
Port operating status changed from unhealthy to healthy: Device IP address: $1 Port name: $2 Inbound bandwidth usage: $3 Outbound bandwidth usage: $4 Inbound error packet rate: $5 Outbound error packet rate: $6 Inbound packet loss rate: $7 Outbound packet loss rate: $8 |
Variable fields |
$1: IP address of the device. $2: Port name. $3: Inbound bandwidth usage. $4: Outbound bandwidth usage. $5: Inbound error packet rate. $6: Outbound error packet rate. $7: Inbound packet loss rate. $8: Outbound packet loss rate. |
Severity level |
Info |
Example |
Port operating status changed from unhealthy to healthy: Device IP address: 192.168.70.68 Port name: XGE1/0/5 Inbound bandwidth usage: 10% Outbound bandwidth usage: 20% Inbound error packet rate: 1% Outbound error packet rate: 1% Inbound packet loss rate: 0% Outbound packet loss rate: 0% |
Explanation |
This message is generated when the port operating status changes from unhealthy to healthy. |
Recommended action |
No action is required. |
CON_REGION
This section contains CON_REGION messages.
Region creation
Keyword |
REGION_ADD |
Message text |
REGION_ADDED : ID: $1 |
Variable fields |
$1: Region ID. |
Severity level |
Info |
Example |
REGION_ADDED:ID:Id[value=8aeffbea-7fce-457b-a753-8c228d72c24f] |
Explanation |
A region was created. |
Recommended action |
No action is required. |
Region activation
Keyword |
REGION_ACTIVE |
Message text |
REGION_ACTIVE : ID: $1 |
Variable fields |
$1: Region ID. |
Severity level |
Info |
Example |
REGION_ACTIVE:ID:Id[value=8aeffbea-7fce-457b-a753-8c228d72c24f] |
Explanation |
A minimum of one member in the region was activated. |
Recommended action |
No action is required. |
Region update
Keyword |
REGION_UPDATE |
Message text |
REGION_UPDATED : ID: $1 |
Variable fields |
$1: Region ID. |
Severity level |
Info |
Example |
REGION_UPDATED:ID:Id[value=8aeffbea-7fce-457b-a753-8c228d72c24f] |
Explanation |
A region was updated. |
Recommended action |
No action is required. |
Region down
Keyword |
REGION_DOWN |
Message text |
REGION_DOWN : ID: $1 |
Variable fields |
$1: Region ID. |
Severity level |
Info |
Example |
REGION_DOWN:ID:Id[value=8aeffbea-7fce-457b-a753-8c228d72c24f] |
Explanation |
The region was down because all controllers left the region or the region was deleted. |
Recommended action |
No action is required. |
Region deletion
Keyword |
REGION_DELETE |
Message text |
REGION_DELETED: ID: $1 |
Variable fields |
$1: Region ID. |
Severity level |
Info |
Example |
REGION_DELETED:ID:Id[value=8aeffbea-7fce-457b-a753-8c228d72c24f] |
Explanation |
A region was deleted. |
Recommended action |
No action is required. |
Failure to restore region settings
Keyword |
REGION_RECOVER_FAILED |
Message text |
Failed to restore all region settings because of inconsistent data format. All regions were automatically deleted. |
Variable fields |
N/A |
Severity level |
Error |
Example |
Failed to restore all region settings because of inconsistent data format. All regions were automatically deleted. |
Explanation |
All region settings failed to be restored because of inconsistent data format and all regions were automatically deleted. The message might appear when software upgrade is done on a controller and the current software version is incompatible with the previous software version. |
Recommended action |
Log in to the active leader and create regions again. |
Network device connection to a master
Keyword |
REGION_SELECT_MASTER |
Message text |
The network devices with datapath ID collection $1 were connected to master $2/$3. |
Variable fields |
$1: Datapath IDs of the network devices. $2: Name of the master controller. $3: IP address of the master controller. |
Severity level |
Info |
Example |
The network devices with datapath ID collection 00:01:28:ec:6e:4a:02:00 were connected to master 3/F001:0:0:0:1000:1000:1000:1004. |
Explanation |
The network devices with the specified datapath IDs were connected to a master. |
Recommended action |
No action is required. |
Master change for network devices
Keyword |
REGION_MASTER_CHANGE |
Message text |
The master of the network devices with datapath ID collection $1 was changed from $2/$3 to $4/$5. |
Variable fields |
$1: Datapath IDs of the network devices. $2: Name of the original master to which the network devices are connected. $3: IP address of the original master to which the network devices are connected. $4: Name of the new master to which the network devices are connected. $5: IP address of the new master to which the network devices are connected. |
Severity level |
Warning |
Example |
The master of the network devices with datapath ID collection 00:01:28:ec:6e:4a:02:00 was changed from 3/F001:0:0:0:1000:1000:1000:1004 to 2/F001:0:0:0:1000:1000:1000:1003. |
Explanation |
The master for the network devices with the specified datapath IDs was changed. |
Recommended action |
No action is required. |
Network device disconnection from a master
Keyword |
DEVICE_DISCONNECT_MASTER |
Message text |
The network devices with datapath ID collection $1 were disconnected from the master $2. |
Variable fields |
$1: Datapath IDs of the network devices. $2: IP address of the master controller. |
Severity level |
Warning |
Example |
The network devices with datapath ID collection 00:01:a6:81:13:28:01:00 00:05:a6:81:13:28:01:00 were disconnected from the master 192.168.105.21. |
Explanation |
The network devices with the specified datapath IDs were disconnected from a master. |
Recommended action |
Examine whether the disconnection is abnormal. If the disconnection is abnormal, perform the following steps: 19. Verify that the network is connected. 20. Configure the controller to issue the region configuration again. |
OpenFlow device connection with multiple regions
Keyword |
DEVICE_CONNECT_MULTIREGION |
Message text |
The network device with datapath ID $1 has joined region $2 and region $3 |
Variable fields |
$1: Datapath ID of the network device. $2: Name of one region to which the network device connects. $3: Name of the other region to which the network device connects. |
Severity level |
Emergency |
Example |
The network device with datapath ID 0c:6f:74:25:8a:c4:e3:a1 has joined region A and region B |
Explanation |
The OpenFlow device was connected to multiple controllers in different regions. |
Recommended action |
Disconnect the OpenFlow device from all controllers and then connect the OpenFlow device to controllers in the same region. |
Abnormal status of the other controller in the region
Keyword |
REGION_CONTROLLER_STATUS_DOWN |
Message text |
The connection between the current controller and controller $1 in the region is abnormal. |
Variable fields |
$1: IP address of the other controller in the current region. |
Severity level |
Emergency |
Example |
The connection between the current controller and controller 192.168.105.33 in the region is abnormal. |
Explanation |
The status of the other controller in the current region is abnormal. |
Recommended action |
21. Verify that the other controller in the region started up correctly. If the controller started up correctly, go to the next step. 22. Verify that the controller does not quit the team. If the controller quits the team, add the controller to the team. If the controller is in the team, go to the next step. 23. Reboot the controller or contact H3C Support because the handshake module of the controller might be abnormal. |
Normal status of the other controller in the region
Keyword |
REGION_CONTROLLER_STATUS_UP |
Message text |
The connection between the current controller and controller $1 in the region is normal. |
Variable fields |
$1: IP address of the other controller in the region. |
Severity level |
Info |
Example |
The connection between the current controller and controller 192.168.105.33 in the region is normal. |
Explanation |
The status of the other controller in the current region is normal. |
Recommended action |
No action is required. |
CON_SNMP
This section contains CON_SNMP messages.
Device created SNMP connection with controller
Keyword |
SNMP_SESSION_UP |
Message text |
An SNMP session was created between the device at $1 and the controller at $2. |
Variable fields |
$1: IP address of the device. $2: IP address of the controller. |
Severity level |
Info |
Example |
An SNMP session was created between the device at 192.168.70.72 and the controller at 192.168.89.155. |
Explanation |
The device established an SNMP connection to the controller. |
Recommended action |
No action is required. |
Device broke SNMP connection to controller
Keyword |
SNMP_SESSION_DOWN |
Message text |
The SNMP session between the device at $1 and the controller at $2 was disconnected. |
Variable fields |
$1: IP address of the device. $2: IP address of the controller. |
Severity level |
Warning |
Example |
The SNMP session between the device at 192.168.70.72 and the controller at 192.168.89.155 was disconnected. |
Explanation |
The device broke the SNMP connection to the controller. |
Recommended action |
Verify that the disconnection is normal. If the disconnection is abnormal, check the connectivity of the network. |
Device port up
Keyword |
DEVICE_PORT_UP |
Message text |
Port $1 of device at $2 was up. |
Variable fields |
$1: Name of the device port. $2: IP address of the device. |
Severity level |
Info |
Example |
Port FGE1/0/46 of device at 192.168.89.155 was up. |
Explanation |
This message is sent when the port of the device comes up. |
Recommended action |
No action is required. |
Device port down
Keyword |
DEVICE_PORT_DOWN |
Message text |
Port $1 of device at $2 was down. |
Variable fields |
$1: Name of the device port. $2: IP address of the device. |
Severity level |
Warning |
Example |
Port FGE1/0/46 of device at 192.168.89.155 was down. |
Explanation |
This message is sent when the port of the device goes down. |
Recommended action |
Verify that the physical status of the device port is correct. |
CON_SYSTEM
This section contains CON_SYSTEM messages.
Database operation failure because of a nonexistent user
Keyword |
DATABASE_NO_USER |
Message text |
Database operation failed because the user did not exist. |
Variable fields |
N/A |
Severity level |
Emergency |
Example |
Database operation failed because the user did not exist. |
Explanation |
The database operation failed because the user did not exist. |
Recommended action |
Verify that the user is configured in the database. |
Database operation failure because of refused connections
Keyword |
DATABASE_CONNECTION_FAILED |
Message text |
Database operation failed because the database sdndb rejected the connection request from the controller $1. |
Variable fields |
$1: IP address of the controller. |
Severity level |
Emergency |
Example |
Database operation failed because the database sdndb rejected the connection request from the controller 10.10.10.10. |
Explanation |
The database operation failed because the connection to the database was refused as a result of abnormal database shutdown and so on. |
Recommended action |
Use the service postgresql status command to verify that the database is in active (running) status. Use the netstat -antp | grep 5432 command to verify that the port of the database is not occupied by other processes. |
End of controller configuration recovery
Keyword |
FINISH_RECOVER_CONFIGURATIONS |
Message text |
Controller configuration recovery completed. |
Variable fields |
N/A |
Severity level |
Info |
Example |
Controller configuration recovery completed. |
Explanation |
Controller configuration recovery completed. |
Recommended action |
No action is required. |
Controller configuration backup not performed when backup file exists
Keyword |
BACKUP_CONFIGURATIONS_EXIST |
Message text |
The configuration file already exists. |
Variable fields |
N/A |
Severity level |
Info |
Example |
The configuration file already exists. |
Explanation |
Configuration backup is not performed when both of the following conditions exist: · The non-active leader controllers in the team are consecutively rebooted at least twice before the configuration recovery is completed. · A backup configuration file already exists on each non-active leader controller. |
Recommended action |
Do not consecutively reboot the non-active leader controllers in the team before the configuration recovery is completed. |
Failed to send the backup file to the remote server
Keyword |
BACKUP_FILE_SEND_FAILED |
Message text |
Failed to send the backup file to the remote server. |
Variable fields |
N/A |
Severity level |
Warning |
Example |
Failed to send the backup file to the remote server. |
Explanation |
Failed to send the backup file to the remote file server. |
Recommended action |
· Verify that the remote server IP address, username, and password in the remote backup settings are correct. · Verify that the connection between the controller and remote server is normal. · Verify that the username in the remote backup settings has read and write permission to the specified FTP path. |
Up to six backup files created by using the same backup method at a time
Keyword |
BACKUP_REACH_SIX_SAMETIME |
Message text |
The system stopped backing up the configuration because up to six backup files have been created by using the same method at a time. |
Variable fields |
N/A |
Severity level |
Warning |
Example |
The system stopped backing up the configuration because up to six backup files have been created by using the same method at a time. |
Explanation |
Typically, backup files are named in the format of backup time_controller version_backup method, for example, #20161121204142_D2011P07_M. When multiple backup files are created by using the same method at a time, the system names the backup files in another format to prevent duplicate file names. All backup files except the first one are named in the format of backup time_controller version_backup method_n. When n is greater than 5, the system generates this log and stops the current backup operation. |
Recommended action |
Do not perform multiple backup operations at a time on a controller. |
CON_TEAM
This section contains CON_TEAM messages.
Failure to delete team IP
Keyword |
DELETE_TEAMIP_FAILED |
Message text |
Failed to delete team IP $1. |
Variable fields |
$1: Team IP address. |
Severity level |
Warning |
Example |
Failed to delete team IP 192.168.56.211. |
Explanation |
The system failed to delete the team IP address from the original active leader. The message appears in any of the following situations: · The team is deleted. · An active leader switchover occurs. |
Recommended action |
Delete the team IP address on the original active leader by using the sudo ifconfig <NIC>:<subinterface number> <controller_ip> netmask <network_mask> down command. |
Controller suspended
Keyword |
BECOME_SUSPENDED |
Message text |
BECOME_SUSPENDED, ID: $1, IP: $2, Name: $3, Team name: $4, Team IP: $5. |
Variable fields |
$1: Member controller ID. $2: Member controller IP address. $3: Member controller name. $4: Name of the team. $5: Team IP address. |
Severity level |
Warning |
Example |
BECOME_SUSPENDED, ID:98394757-7760-4262-b71b-7b2dde8af5cd,IP:192.168.37.105, Name: controller1, Team name: ZOK, Team IP: 192.168.37.36. |
Explanation |
The controller was suspended. It was disconnected from other controllers in the team and stopped receiving new services. |
Recommended action |
No action is required. |
Member joined team
Keyword |
MEMBER_JOIN |
Message text |
MEMBER_JOIN, ID: $1, IP: $2, Name: $3, Team name: $4, Team IP: $5. |
Variable fields |
$1: Member controller ID. $2: Member controller IP address. $3: Member controller name. $4: Name of the team. $5: Team IP address. |
Severity level |
Info |
Example |
MEMBER_JOIN, ID:98394757-7760-4262-b71b-7b2dde8af5cd, IP:192.168.37.105, Name: controller1, Team name: ZOK, Team IP: 192.168.37.36. |
Explanation |
The controller joined the team. This event was recorded on the active leader. |
Recommended action |
No action is required. |
Active leader changed
Keyword |
MEMBER_TO_LEADER |
Message text |
MEMBER_TO_LEADER, ID: $1, IP: $2, Name: $3, Team name: $4, Team IP: $5. |
Variable fields |
$1: Member controller ID. $2: Member controller IP address. $3: Member controller name. $4: Name of the team. $5: Team IP address. |
Severity level |
Warning |
Example |
MEMBER_TO_LEADER, ID: 98394757-7760-4262-b71b-7b2dde8af5cd, IP: 192.168.37.105, Name: controller1, Team name: ZOK, Team IP: 192.168.37.36. |
Explanation |
A team event occurred: The controller was elected as the active leader. |
Recommended action |
No action is required. |
Controller became active leader
Keyword |
BECOME_LEADER |
Message text |
BECOME_LEADER, ID: $1, IP: $2, Name: $3, Team name: $4, Team IP: $5. |
Variable fields |
$1: Member controller ID. $2: Member controller IP address. (This field displays 127.0.0.1 in standalone mode.) $3: Member controller name. (This field displays Local in standalone mode.) $4: Name of the team. (This field displays Standalone in standalone mode.) $5: Team IP address. (This field displays 127.0.0.1 in standalone mode.) |
Severity level |
Info |
Example |
BECOME_LEADER, ID: 98394757-7760-4262-b71b-7b2dde8af5cd, IP: 192.168.37.105, Name: controller1, Team name: ZOK, Team IP: 192.168.37.36. |
Explanation |
A team event occurred: The controller was elected as the active leader. |
Recommended action |
No action is required. |
Controller became member
Keyword |
BECOME_MEMBER |
Message text |
BECOME_MEMBER,, ID: $1, IP: $2, Name: $3, Team name: $4, Team IP: $5. |
Variable fields |
$1: Member controller ID. $2: Member controller IP address. $3: Member controller name. $4: Name of the team. $5: Team IP address. |
Severity level |
Info |
Example |
BECOME_MEMBER, ID: 98394757-7760-4262-b71b-7b2dde8af5cd, IP: 192.168.37.105, Name: controller1, Team name: ZOK, Team IP: 192.168.37.36. |
Explanation |
A team event occurred: The controller joined the team. |
Recommended action |
No action is required. |
Member left team unexpectedly
Keyword |
MEMBER_LEAVE |
Message text |
MEMBER_LEAVE, ID $1, IP $2 from team $3 team IP $4. |
Variable fields |
$1: Member controller ID. $2: Member controller IP address. $3: Team name. $4: Team IP address. |
Severity level |
Warning |
Example |
MEMBER_LEAVE, ID 98394757-7760-4262-b71b-7b2dde8af5cd, IP 192.168.37.105 from team sdn team IP 192.168.10.1. |
Explanation |
The member controller left the team unexpectedly. This event was recorded on the active leader. |
Recommended action |
Log in to the operating system where the active leader is installed, and use the ping command to test the connectivity between the active leader and member controller. · Specify the IP address used by the active controller to join the team as the source IP. · Specify the IP address used by the member controller to join the team as the destination IP. Log in to the operating system, and verify that the sdnc and zookeeper processes are operating correctly. · Use the ps -aux | grep virgo command to verify that the sdnc process is operating correctly. · Use the ps -aux | grep zoo command to verify that the zookeeper process is operating correctly. · Use the following commands to verify that all TCP connections to the zookeeper ports are in Established status. ¡ netstat -anut | grep 2181 ¡ netstat -anut | grep 2888 ¡ netstat -anut | grep 3888 |
Member left team expectedly
Keyword |
MEMBER_LEAVE |
Message text |
MEMBER_LEAVE, ID $1 from team $2 team IP $3. |
Variable fields |
$1: Member controller ID. $2: Team name. $3: Team IP address. |
Severity level |
Info |
Example |
MEMBER_LEAVE, ID 98394757-7760-4262-b71b-7b2dde8af5cd from team sdn team IP 192.168.10.1. |
Explanation |
The member controller left the team expectedly. This event was recorded on the active leader. |
Recommended action |
No action is required. |
Different team token than the active leader
Keyword |
TEAMTOKEN_DIFF |
Message text |
The team token of the member $1 was different than the active leader. |
Variable fields |
$1: IP address of the member controller. |
Severity level |
Warning |
Example |
The team token of the member 192.168.56.147 was different than the active leader. |
Explanation |
The team token of the member was different than the active leader when the member was added to the team or the active leader issued configuration to the member. |
Recommended action |
Modify the team token of the member to be the same as that of the active leader. |
Reboot for completing team merge
Keyword |
LEADER_CONFILICT |
Message text |
Leader conflict was detected in stateful failover mode on the controller $1. The controller automatically rebooted to complete the team merge. |
Variable fields |
$1: IP address of the controller. |
Severity level |
Emergency |
Example |
Leader conflict was detected in stateful failover mode on the controller 192.168.56.147. The controller automatically rebooted to complete the team merge. |
Explanation |
A leader conflict was detected in stateful failover mode on the controller. The controller rebooted automatically to complete the team merge. |
Recommended action |
No action is required. |
Reboot to act as the leader
Keyword |
ILLEGAL_ROLE_CHANGE |
Message text |
Controller $1 will reboot because it is selected as the active leader during configuration recovery. |
Variable fields |
$1: IP address of the controller. |
Severity level |
Emergency |
Example |
Controller 192.168.217.230 will reboot because it is selected as the active leader during configuration recovery. |
Explanation |
The controller was selected as the active leader during configuration recovery. To avoid configuration loss, the controller automatically reboots. |
Recommended action |
No action is required. |
CON_USER
This section contains CON_USER messages.
Login success
Keyword |
LOGGED_IN_SUCCEED |
Message text |
User $1 successfully logged in by using the role $2 and the IP address $3. |
Variable fields |
$1: Username. $2: User role, including: ¡ sdn-admin. ¡ sdn-user. $3: IP address of the user. |
Severity level |
Info |
Example |
User sdn successfully logged in by using the role sdn-admin and the IP address 192.168.1.1. |
Explanation |
A user logged into the device. |
Recommended action |
No action is required. |
Login failure
Keyword |
LOGGED_IN_FAILED |
Message text |
User $1 failed to log in by using the IP address $2. |
Variable fields |
$1: Username. $2: IP address of the user. |
Severity level |
Info |
Example |
User sdn failed to log in by using the IP address 192.168.1.1. |
Explanation |
A user failed to log into the device. The message appears in any of the following situations: · The username is incorrect. · The password is incorrect. |
Recommended action |
Check the entered username and password. |
User lock
Keyword |
USER_LOCKED |
Message text |
The user $1 failed to log in because the login failures has reached five times, and the user is locked. |
Variable fields |
$1: Username. |
Severity level |
Info |
Example |
The user sdn failed to log in because the login failures has reached five times, and the user is locked. |
Explanation |
The user account was locked because the user failed to log in to the controller for five consecutive times. |
Recommended action |
Verify that the username and password are correct. The user account will be unlocked in 15 minutes or after a controller reboot. |
Logout success
Keyword |
LOGGED_OUT_SUCCEED |
Message text |
User $1 successfully logged out by using the role $2 and the IP address $3. |
Variable fields |
$1: Username. $2: User role, including: ¡ sdn-admin. ¡ sdn-user. $3: IP address of the user. |
Severity level |
Info |
Example |
User sdn successfully logged out by using the role sdn-admin and the IP address 192.168.1.1. |
Explanation |
A user logged out of the device. |
Recommended action |
No action is required. |
RADIUS authentication success
Keyword |
RADIUS_AUTHENTICATION_PASS |
Message text |
User $1 passed the RADIUS authentication. |
Variable fields |
$1: Username. |
Severity level |
Info |
Example |
User User1 passed the RADIUS authentication. |
Explanation |
A user passed RADIUS authentication. |
Recommended action |
No action is required. |
RADIUS authentication rejection
Keyword |
RADIUS_AUTHENTICATION_REJECT |
Message text |
The RADIUS authentication request from user $1 was rejected. |
Variable fields |
$1: Username. |
Severity level |
Warning |
Example |
The RADIUS authentication request from user User1 was rejected. |
Explanation |
A user was rejected for RADIUS authentication. The message appears in any of the following situations: · The user does not exist. · The password is incorrect. |
Recommended action |
Check the entered username and password. |
RADIUS authentication failure
Keyword |
RADIUS_AUTHENTICATION_FAILED |
Message text |
User $1 failed to pass the RADIUS authentication. |
Variable fields |
$1: Username. |
Severity level |
Warning |
Example |
User User1 failed to pass the RADIUS authentication. |
Explanation |
A user failed to pass RADIUS authentication. |
Recommended action |
Resolve the issue in the following steps: 24. Check for any incorrect authentication settings, for example, the server IP address and the authentication shared key. 25. Verify that the controller has been added to the AAA server as an AAA client. 26. Verify that the controller can communicate with the AAA server correctly. |
RADIUS attribute check failure
Keyword |
RADIUS_ATTRIBUTE_CHECK_FAILED |
Message text |
User $1 failed to pass the RADIUS authentication because attribute H3C_EXEC_PRIVILEGE was not configured. |
Variable fields |
$1: Username. |
Severity level |
Warning |
Example |
User User1 failed to pass the RADIUS authentication because attribute H3C_EXEC_PRIVILEGE was not configured. |
Explanation |
The RADIUS authentication failed because the H3C proprietary attribute was not configured. |
Recommended action |
Verify that the H3C_EXEC_PRIVILEGE attribute is configured on the AAA server. |
TACACS+ authentication success
Keyword |
TACACS+_AUTHENTICATION_PASS |
Message text |
User $1 passed the TACACS+ authentication. |
Variable fields |
$1: Username. |
Severity level |
Info |
Example |
User User1 passed the TACACS+ authentication. |
Explanation |
A user passed TACACS+ authentication. |
Recommended action |
No action is required. |
TACACS+ authentication rejection
Keyword |
TACACS+_AUTHENTICATION_REJECT |
Message text |
The TACACS+ authentication request from user $1 was rejected. |
Variable fields |
$1: Username. |
Severity level |
Warning |
Example |
The TACACS+ authentication request from user User1 was rejected. |
Explanation |
A user was rejected for TACACS+ authentication. The message appears in any of the following situations: · The user does not exist. · The password is incorrect. |
Recommended action |
Check the entered username and password. |
TACACS+ authentication failure
Keyword |
TACACS+_AUTHENTICATION_FAILED |
Message text |
User $1 failed to pass the TACACS+ authentication. |
Variable fields |
$1: Username. |
Severity level |
Warning |
Example |
User User1 failed to pass the TACACS+ authentication. |
Explanation |
A user failed to pass TACACS+ authentication. |
Recommended action |
Resolve the issue in the following steps: 27. Check for any incorrect authentication settings, for example, the server IP address and the authentication shared key. 28. Verify that the controller has been added to the AAA server as an AAA client. 29. Verify that the controller can communicate with the AAA server correctly. |
TACACS+ attribute check failure
Keyword |
TACACS+_ATTRIBUTE_CHECK_FAILED |
Message text |
User $1 failed to pass the TACACS+ authentication because attribute H3C_EXEC_PRIVILEGE was not configured. |
Variable fields |
$1: Username. |
Severity level |
Warning |
Example |
User User1 failed to pass the TACACS+ authentication because attribute H3C_EXEC_PRIVILEGE was not configured. |
Explanation |
The TACACS+ authentication failed because the H3C proprietary attribute was not configured. |
Recommended action |
Verify that the H3C_EXEC_PRIVILEGE attribute is configured on the AAA server. |
Start of user configuration recovery on non-active leader controllers
Keyword |
BEGIN_RECOVER_USER_CONFIG |
Message text |
All non-active leader controllers started recovering the user configuration. |
Variable fields |
N/A |
Severity level |
Info |
Example |
All non-active leader controllers started recovering the user configuration. |
Explanation |
All non-active leader controllers started recovering the user configuration, including the username, password, and role. |
Recommended action |
As a best practice, do not perform any operations on the controllers during the configuration recovery process. |
End of user configuration recovery on non-active leader controllers
Keyword |
FINISH_RECOVER_USER_CONFIG |
Message text |
All non-active leader controllers completed recovering the user configuration. |
Variable fields |
N/A |
Severity level |
Info |
Example |
All non-active leader controllers completed recovering the user configuration. |
Explanation |
All non-active leader controllers completed recovering the user configuration, including the username, password, and role. |
Recommended action |
No action is required. |
Operation failure due to user role privilege limit
Keyword |
ROLE_PERMISSION_CHECK_FAILED |
Message text |
Failed to $1 $2. The user role doesn’t have the permission. |
Variable fields |
$1: Request type: · post—Creates a resource. · put—Updates or creates a resource. · delete—Deletes a resource. · get—Gets resource information. $2: Requested resource path. |
Severity level |
Error |
Example |
Failed to put /sdn/v2.0/systems/4ff280bd-51c6-4768-9be4-4f9f72b51b77. The user role doesn’t have the permission. |
Explanation |
The user role does not have the permission to send the request. |
Recommended action |
Modify the privilege for the user role or use another user role that has the permission to send the request. |
User password expiration
Keyword |
USER_EXPIRED_CHECK |
Message text |
Password for user $1 expired. Please change the password immediately. |
Variable fields |
$1: User name. |
Severity level |
Error |
Example |
Password for user admin expired. Please change the password immediately. |
Explanation |
The password of a user expired. |
Recommended action |
Set a new password for the user. |
DATACHECK
This section contains data check messages.
Controller failed data entry count consistency check
Keyword |
CONFIG_NUM_CHECK_DIFF |
Message text |
Controller $1 failed to pass the data entry count consistency check. |
Variable fields |
$1: Controller IP address. |
Severity level |
Warning |
Example |
Controller 192.168.103.39 failed to pass the data entry count consistency check. |
Explanation |
The controller failed to pass the data entry count consistency check. |
Recommended action |
Verify that the number of data entries in the database and memory are consistent for the controller. |
Controller passed data entry count consistency check
Keyword |
CONFIG_NUM_CHECK_CONSISTENT |
Message text |
Controller $1 passed the data entry count consistency check. |
Variable fields |
$1: Controller IP address. |
Severity level |
Info |
Example |
Controller 192.168.103.39 passed the data entry count consistency check. |
Explanation |
The controller passed the data entry count consistency check. |
Recommended action |
No action is required. |
Failure to obtain data entry count consistency check result for controller
Keyword |
CONFIG_NUM_CHECK_FAILED |
Message text |
Failed to obtain the data entry count consistency check result for controller $1. |
Variable fields |
$1: Controller IP address. |
Severity level |
Warning |
Example |
Failed to obtain the data entry count consistency check result for controller 192.168.103.39. |
Explanation |
Failed to obtain the data entry count consistency check result for the controller. |
Recommended action |
Check error information recorded in diagnosis logs on the controller. |
Controller passed local data entry count consistency check
Keyword |
CONTENT_LOCAL_CHECK_CONSISTENT |
Message text |
Controller $1 passed the local data entry count consistency check. |
Variable fields |
$1: Controller IP address. |
Severity level |
Info |
Example |
Controller 192.168.103.39 passed the local data entry count consistency check. |
Explanation |
The controller passed the local data entry count consistency check. |
Recommended action |
No action is required. |
Controller failed local data entry count consistency check
Keyword |
CONTENT_LOCAL_CHECK_DIFF |
Message text |
Controller $1 failed to pass the local data content consistency check. |
Variable fields |
$1: Controller IP address. |
Severity level |
Warning |
Example |
Controller 192.168.103.39 failed to pass the local data content consistency check. |
Explanation |
The controller failed to pass the local data entry count consistency check. |
Recommended action |
Check error information recorded in diagnosis logs on the controller. |
Failure to obtain local data entry count consistency check result for controller
Keyword |
CONTENT_LOCAL_CHECK_FAILED |
Message text |
Failed to obtain the local data content consistency check result for controller $1. |
Variable fields |
$1: Controller IP address. |
Severity level |
Warning |
Example |
Failed to obtain the local data content consistency check result for controller 192.168.103.39. |
Explanation |
Failed to obtain the local data entry count consistency check result for the controller. |
Recommended action |
Check error information recorded in diagnosis logs on the controller. |
Controller passed cluster data content consistency check
Keyword |
CONTENT_TEAM_CHECK_CONSISTENT |
Message text |
Controller $1 passed the cluster data content consistency check. |
Variable fields |
$1: Controller IP address. |
Severity level |
Info |
Example |
Controller 192.168.103.39 passed the cluster data content consistency check. |
Explanation |
The controller passed the cluster data content consistency check. |
Recommended action |
No action is required. |
Controller failed cluster data content consistency check
Keyword |
CONTENT_TEAM_CHECK_DIFF |
Message text |
Controller $1 failed to pass the cluster data content consistency check. |
Variable fields |
$1: Controller IP address. |
Severity level |
Warning |
Example |
Controller 192.168.103.39 failed to pass the cluster data content consistency check. |
Explanation |
The controller failed to pass the cluster data content consistency check. |
Recommended action |
Check error information recorded in diagnosis logs on the controller. |
Failure to obtain cluster data content consistency check result for controller
Keyword |
CONTENT_TEAM_CHECK_FAILED |
Message text |
Failed to obtain the cluster data content consistency check result for controller $1. |
Variable fields |
$1: Controller IP address. |
Severity level |
Warning |
Example |
Failed to obtain the cluster data content consistency check result for controller 192.168.103.39. |
Explanation |
Failed to obtain the cluster data content consistency check result for the controller. |
Recommended action |
Check error information recorded in diagnosis logs on the controller. |
DHCP
This section contains DHCP messages.
Start of DHCP configuration recovery on non-active leader controllers
Keyword |
BEGIN_RECOVER_DHCP_CONFIG |
Message text |
All non-active leader controllers started recovering the DHCP configuration. |
Variable fields |
N/A |
Severity level |
Info |
Example |
All non-active leader controllers started recovering the DHCP configuration. |
Explanation |
All non-active leader controllers started recovering the DHCP configuration. |
Recommended action |
As a best practice, do not perform any operations on the controllers during the configuration recovery process. |
End of DHCP configuration recovery on non-active leader controllers
Keyword |
FINISH_RECOVER_DHCP_CONFIG |
Message text |
All non-active leader controllers completed recovering the DHCP configuration. |
Variable fields |
N/A |
Severity level |
Info |
Example |
All non-active leader controllers completed recovering the DHCP configuration. |
Explanation |
All non-active leader controllers completed recovering the DHCP configuration. |
Recommended action |
No action is required. |
Failure of IP allocation to VM
Keyword |
RECEIVE_DECLINE_PACKET |
Message text |
IP allocation failed. IP address “$1” in network “$2” has been used. |
Variable fields |
$1: IP address assigned by the VM by the controller. $2: Name of the virtual link network where the IP address resides. |
Severity level |
Error |
Example |
IP allocation failed. IP address “192.168.100.101” in network “network1” has been used. |
Explanation |
The VM cannot use the assigned IP address because another VM is using it. |
Recommended action |
Please locate the VM that is using this IP address, and change the IP address without affecting the services. |
F5aaS
This section contains F5aaS messages.
Connection establishment between the F5 device and controller
Keyword |
F5_SESSION_ESTABLISH |
Message text |
F5 device at $1 has connected to controller at $2. |
Variable fields |
$1: IP address of the F5 device. $2: IP address of the controller. |
Severity level |
Info |
Example |
F5 device at 192.168.100.1 has connected to controller at 10.10.10.1. |
Explanation |
An F5 device established a connection to the controller. |
Recommended action |
No action is required. |
Disconnection between the F5 device and controller
Keyword |
F5_SESSION_INTERRUPT |
Message text |
F5 device at $1 has disconnected from controller at $2. |
Variable fields |
$1: IP address of the F5 device. $2: IP address of the controller. |
Severity level |
Info |
Example |
F5 device at 192.168.100.1 has disconnected from controller at 10.10.10.1. |
Explanation |
An F5 device was disconnected from the controller. |
Recommended action |
· If you manually disconnect the F5 device from the controller, no action is required. · If an unexpected disconnection occurred, perform the following tasks: a. Log in to the operating system where the controller is installed. Use the IP address of the controller in the team to ping the IP address of the F5 device. b. Log in to the F5 device and verify the connection settings. |
Failure to delete a floating IP
Keyword |
F5_STANDBY_DELETE_FLOATIP_FAILED |
Message text |
Standby F5 device at $1 failed to delete floating IP $2. |
Variable fields |
$1: IP address of the F5 device. $2: Floating IP address. |
Severity level |
Warning |
Example |
Standby F5 device at 192.168.100.1 failed to delete floating IP 10.10.10.2. |
Explanation |
An F5 device deleted a floating IP address and notified the standby F5 device of the deletion, but the standby F5 device failed to delete the floating IP address. |
Recommended action |
The failure might cause leftovers of the floating IP address associated settings, such as Self IP, VLAN, and Route Domain. If the failure occurs, perform the following tasks: · Log in to the standby F5 device and then delete the floating IP address. · Clear the Self IP, VLAN, and Route Domain configuration leftovers. |
Fabric
This section contains fabric messages.
Thread pool rejected task
Keyword |
FABRIC_THREAD_POOL_REJECT_TASK |
Message text |
Thread pool $1 rejected task, current thread size $2, max thread size $3, current queue size $4, max queue size $5. |
Variable fields |
$1: Thread pool name. $2: Current number of threads. $3: Maximum number of threads. $4: Current number of queues. $5: Maximum number of queues. |
Severity level |
Error |
Example |
Thread pool FabricTeamEventProcessor rejected task, current thread size 1, max thread size 1, current queue size 1047586, max queue size 1047586. |
Explanation |
Failed to execute a new task, because the thread pool for the fabric module does not have resources. |
Recommended action |
Contact H3C Support. |
FWaaS
This section contains firewall messages.
Start of firewall configuration recovery on non-active leader controllers
Keyword |
BEGIN_RECOVER_FW_CONFIG |
Message text |
All non-active leader controllers started recovering the firewall configuration. |
Variable fields |
N/A |
Severity level |
Info |
Example |
All non-active leader controllers started recovering the firewall configuration. |
Explanation |
All non-active leader controllers started recovering the firewall configuration. The configuration to be recovered includes firewalls, firewall policies, and firewall rules. |
Recommended action |
As a best practice, do not perform any operations on the controllers during the configuration recovery process. |
End of firewall configuration recovery on non-active leader controllers
Keyword |
FINISH_RECOVER_FW_CONFIG |
Message text |
All non-active leader controllers completed recovering the firewall configuration. |
Variable fields |
N/A |
Severity level |
Info |
Example |
All non-active leader controllers completed recovering the firewall configuration. |
Explanation |
All non-active leader controllers completed recovering the firewall configuration. The recovered configuration includes firewalls, firewall policies, and firewall rules. |
Recommended action |
No action is required. |
Inconsistent DPI application profile information
Keyword |
FW_PROFILEINFO_INCONSISTENT |
Message text |
The application profile information of the controller was different than the network device: Application profile name: $1 Management IP: $2 |
Variable fields |
$1: DPI application profile name. $2: Management IP address of the network device. |
Severity level |
Warning |
Example |
The application profile information of the controller was different than the network device: Application profile name: Profile_VGW7ZJGNOFHVFT4YMQNVNPKEQM Management IP: 99.0.10.121 |
Explanation |
The DPI application profile information on the firewall module of the controller was inconsistent with that on the network device. |
Recommended action |
Terminate the existing connection between the network device and the controller, and then establish a new OpenFlow connection between them. |
Inconsistent IPS policy information
Keyword |
FW_IPSINFO_INCONSISTENT |
Message text |
The IPS policy information of the controller was different than the network device: IPS policy name: $1 Management IP: $2 |
Variable fields |
$1: IPS policy name. $7: Management IP address of the network device. |
Severity level |
Warning |
Example |
The IPS policy information of the controller was different than the network device: IPS policy name: ips_sksvwlb2z6zypw3ki3ogrncnt4 Management IP: 99.0.10.121 |
Explanation |
The IPS policy information on the firewall module of the controller was inconsistent with that on the network device. |
Recommended action |
Terminate the existing connection between the network device and the controller, and then establish a new OpenFlow connection between them. |
Inconsistent antivirus policy information
Keyword |
FW_AVINFO_INCONSISTENT |
Message text |
The antivirus policy information of the controller was different than the network device: Antivirus policy name: $1 Management IP: $2 |
Variable fields |
$1: Antivirus policy name. $2: Management IP address of the network device. |
Severity level |
Warning |
Example |
The antivirus policy information of the controller was different than the network device: Antivirus policy name: AV_WJJ2DVJLPDN7RJTZ24B2CYKH5A Management IP: 99.0.10.121 |
Explanation |
The antivirus policy information on the antivirus module of the controller was inconsistent with that on the network device. |
Recommended action |
Terminate the existing connection between the network device and the controller, and then establish a new OpenFlow connection between them. |
DPI engine disabled
Keyword |
FW_DPI_DOWN |
Message text |
The DPI function is not enabled on the firewall: Management IP: $1 |
Variable fields |
$1: Management IP address of the firewall. |
Severity level |
Warning |
Example |
The DPI function is not enabled on the firewall: Management IP: 192.168.0.10 |
Explanation |
The DPI engine is disabled on the firewall. |
Recommended action |
Log in to the firewall device, and then execute the inspect activate command to enable the DPI engine. |
IDM
This section contains IDM messages.
Controller failed to synchronize bridge MAC and serial number information from device
Keyword |
DEVICE_INFOR_SYNCHRONIZATION_FAIL |
Message text |
Controller $1 failed to synchronize bridge MAC and serial number information from the device. |
Variable fields |
$1: IP address of the controller. |
Severity level |
Warning |
Example |
Controller 98.0.45.4 failed to synchronize bridge MAC and serial number information from the device. |
Explanation |
The controller failed to synchronize bridge MAC and serial number information from the device. |
Recommended action |
Please try again after this synchronization task completes. |
LBaaS
This section contains load balancing messages.
Start of load balancing configuration recovery on non-active leader controllers
Keyword |
BEGIN_RECOVER_LB_CONFIG |
Message text |
All non-active leader controllers started recovering the load balancing configuration. |
Variable fields |
N/A |
Severity level |
Info |
Example |
All non-active leader controllers started recovering the load balancing configuration. |
Explanation |
All non-active leader controllers started recovering the load balancing configuration, including load balancer, server farm, virtual server, and health monitoring information. |
Recommended action |
As a best practice, do not perform any operations on the controllers during the configuration recovery process. |
End of load balancing configuration recovery on non-active leader controllers
Keyword |
FINISH_RECOVER_LB_CONFIG |
Message text |
All non-active leader controllers completed recovering the load balancing configuration. |
Variable fields |
N/A |
Severity level |
Info |
Example |
All non-active leader controllers completed recovering the load balancing configuration. |
Explanation |
All non-active leader controllers completed recovering the load balancing configuration, including load balancer, server farm, virtual server, and health monitoring information. |
Recommended action |
No action is required. |
NEM
This section contains carrier network messages.
Different VRF information than the network device
Keyword |
NEM_VRFINFO_INCONSISTENT |
Message text |
The VRF information of the NEM was different than the network device: VRF name: $1 Management IP: $2 |
Variable fields |
$1: VRF name. $2: Management IP address of the network device. |
Severity level |
Warning |
Example |
The VRF information of the NEM was different than the network device: VRF name: SDN_VRF_1234 Management IP: 192.168.10.5 |
Explanation |
The VRF information of the NEM was different than the network device. |
Recommended action |
See the VRF information differences between the controller and the network device on the Data Synchronization Details page, and find the reason why the differences exist. |
Different VSI information than the network device
Keyword |
NEM_VSIINFO_INCONSISTENT |
Message text |
The VSI information of the NEM was different than the network device: VSI name: $1 VSI interface name: $3 VRF name: $4 MAC address: $5 Subnet address: $6 Management IP: $7 |
Variable fields |
$1: VSI name. $3: VSI interface name. $4: VRF name. $5: MAC address of the VSI interface. $6: Subnet address and mask. $7: Management IP address of the network device. |
Severity level |
Warning |
Example |
The VSI information of the NEM was different than the network device: VSI name: SDN_VSI_1 VSI interface name: SDN_VSI_Interface_1234 VRF name: 3ji5uj3uan90dq3r3upa4h1484 MAC address: 3c8c-404e-dd46 Subnet address: 100.1.1.254255.255.255.0 Management IP: 192.168.10.5 |
Explanation |
The VSI information of the NEM was different than the network device. |
Recommended action |
See the VSI information differences between the controller and the network device on the Data Synchronization Details page, and find the reason why the differences exist. |
Different tunnel information than the network device
Keyword |
NEM_TUNNELINFO_INCONSISTENT |
Message text |
The tunnel information of the NEM was different than the network device: Tunnel interface ID: $1 Tunnel source IP: $2 Tunnel destination IP: $3 Management IP: $4 |
Variable fields |
$1: Tunnel interface number. $2: Tunnel source IP address. $3: Tunnel destination IP address. $4: Management IP address of the network device. |
Severity level |
Warning |
Example |
The tunnel information of the NEM was different than the network device: Tunnel interface ID: 10 Tunnel source IP: 100.1.1.10 Tunnel destination IP: 100.1.1.20 Management IP: 192.168.10.5 |
Explanation |
The tunnel information of the NEM was different than the network device. |
Recommended action |
See the tunnel information differences between the controller and the network device on the Data Synchronization Details page, and find the reason why the differences exist. |
Different ACL information than the network device
Keyword |
NEM_ACLINFO_INCONSISTENT |
Message text |
The ACL information of the NEM was different than the network device: ACL name: $1 ACL number: $2 Management IP: $3 |
Variable fields |
$1: ACL name. $2: ACL number. $3: Management IP address of the network device. |
Severity level |
Warning |
Example |
The ACL information of the NEM was different than the network device: ACL name: SDN_ACL_1234 ACL number: 12 Management IP: 192.168.10.5 |
Explanation |
The ACL information of the NEM was different than the network device. |
Recommended action |
See the ACL information differences between the controller and the network device on the Data Synchronization Details page, and find the reason why the differences exist. |
Different PBR information than the network device
Keyword |
NEM_PBRINFO_INCONSISTENT |
Message text |
The PBR information of the NEM was different than the network device: PBR name: $1 Management IP: $2 |
Variable fields |
$1: PBR name. $2: Management IP address of the network device. |
Severity level |
Warning |
Example |
The PBR information of the NEM was different than the network device: PBR name: SDN_1234 Management IP: 192.168.10.5 |
Explanation |
The PBR information of the NEM was different than the network device. |
Recommended action |
See the PBR information differences between the controller and the network device on the Data Synchronization Details page, and find the reason why the differences exist. |
Different routing information than the network device
Keyword |
NEM_ROUTEINFO_INCONSISTENT |
Message text |
The routing information of the NEM was different than the network device: Destination VRF name: $1 Destination VRF index: $2 Next hop VRF name: $3 Next hop VRF index: $4 Destination topology index: $5 IPv4 address: $6 Next hop IPv4 address: $7 Description: $8 IPv4 prefix length: $9 Interface index: $10 Management IP: $11 |
Variable fields |
$1: Destination VRF name. $2: Destination VRF index. $3: Next-hop VRF name. $4: Next-hop VRF index. $5: Destination topology index. $6: IP address. $7: Next-hop IP address. $8: Description. $9: IP prefix length. $10: Interface index. $11: Management IP address of the network device. |
Severity level |
Warning |
Example |
The routing information of the NEM was different than the network device: Destination VRF name: SDN_1234 Destination VRF index: 1234 Next hop VRF name: SDN_1235 Next hop VRF index: 1235 Destination topology index: 2345 IPv4 address: 1.1.1.1 Next hop IPv4 address: 1.1.1.2 Description: 123 IPv4 prefix length: 24 Interface index: 1236 Management IP: 192.168.10.5 |
Explanation |
The routing information of the NEM was different than the network device. |
Recommended action |
See the routing information differences between the controller and the network device on the Data Synchronization Details page, and find the reason why the differences exist. |
Different VLAN information than the network device
Keyword |
NEM_VLANINFO_INCONSISTENT |
Message text |
The VLAN information of the NEM was different than the network device: VLAN ID: $1 Management IP: $2 |
Variable fields |
$1: VLAN ID. $2: Management IP address of the network device. |
Severity level |
Warning |
Example |
The VLAN information of the NEM was different than the network device: VLAN ID: 123 Management IP: 192.168.10.5 |
Explanation |
The VLAN information of the NEM was different than the network device. |
Recommended action |
See the VLAN information differences between the controller and the network device on the Data Synchronization Details page, and find the reason why the differences exist. |
Different NAT information than the network device
Keyword |
NEM_NATINFO_INCONSISTENT |
Message text |
The NAT information of the NEM was different than the network device: Interface index: $1 Management IP: $2 |
Variable fields |
$1: Interface index. $2: Management IP address of the network device. |
Severity level |
Warning |
Example |
The NAT information of the NEM was different than the network device: Interface index: 123 Management IP: 192.168.10.5 |
Explanation |
The NAT information of the NEM was different than the network device. |
Recommended action |
See the NAT information differences between the controller and the network device on the Data Synchronization Details page, and find the reason why the differences exist. |
Different floating IP information than the network device
Keyword |
NEM_FLOATINGIPINFO_INCONSISTENT |
Message text |
The floating IP information of the NEM was different than the network device: Local VRF: $1 Local IP: $2 Global VRF: $3 Global IP: $4 Management IP: $5 |
Variable fields |
$1: Local VRF information. $2: Local IP address. $3: External VRF. $4: Floating IP address. $5: Management IP address of the network device. |
Severity level |
Warning |
Example |
The floating IP information of the NEM was different than the network device: Local VRF: 123 Local IP: 1.1.1.2 Global VRF: 234 Global IP: 1.1.1.3 Management IP: 192.168.10.5 |
Explanation |
The floating IP information of the NEM was different than the network device. |
Recommended action |
See the floating IP information differences between the controller and the network device on the Data Synchronization Details page, and find the reason why the differences exist. |
Different DNS information than the network device
Keyword |
NEM_DNSINFO_INCONSISTENT |
Message text |
The DNS information of the NEM was different than the network device: DNS server IP: $1 VRF name: $2 Management IP: $3 |
Variable fields |
$1: DNS server IP address. $2: VRF name. $3: Management IP address of the network device. |
Severity level |
Warning |
Example |
The DNS information of the NEM was different than the network device: DNS server IP: 1.1.1.1 VRF name: 123 Management IP: 192.168.10.5 |
Explanation |
The DNS information of the NEM was different than the network device. |
Recommended action |
See the DNS information differences between the controller and the network device on the Data Synchronization Details page, and find the reason why the differences exist. |
Different host flow information than the network device
Keyword |
NEM_HOSTFLOWINFO_INCONSISTENT |
Message text |
The host flow information of the NEM was different than the network device: Matching source IP: $1 Subnet mask: $2 Matching source MAC: $3 VRF number: $4 VRF name: $5 Destination VTEP IP: $6 Destination MAC: $7 VNI number: $8 Management IP: $9 |
Variable fields |
$1: Source IP address in the match fields of the flow entry. $2: Subnet mask. $3: Source MAC address in the match fields of the flow entry. $4: VRF number. $5: VRF name. $6: Destination VTEP IP address. $7: Destination MAC address. $8: VNI number. $9: Management IP address of the network device. |
Severity level |
Warning |
Example |
The host flow information of the NEM was different than the network device: Matching source IP: 1.1.1.1 Subnet mask: 255.255.255.0 Matching source MAC: 40:a8:f0:29:0a:7b VRF number: 1234 VRF name: abc Destination VTEP IP: 100.1.1.2 Destination MAC: 40:a8:f0:29:0a:7c VNI number: 10 Management IP: 192.168.10.5 |
Explanation |
The host flow information of the NEM was different than the network device. A host flow table entry is used to match packets sent by the virtual machine. |
Recommended action |
See the host flow information differences between the controller and the network device on the Data Synchronization Details page, and find the reason why the differences exist. |
Different subinterface information than the network device
Keyword |
NEM_SUBIFINFO_INCONSISTENT |
Message text |
The sub interface information of the NEM was different than the network device: Interface index: $1 Interface name: $2 Management IP: $3 |
Variable fields |
$1: Subinterface index. $2: Subinterface name. $3: Management IP address of the network device. |
Severity level |
Warning |
Example |
The sub interface information of the NEM was different than the network device: Interface index: 1236 Interface name: subif_a Management IP: 192.168.10.5 |
Explanation |
The subinterface information of the NEM was different than the network device. |
Recommended action |
See the subinterface information differences between the controller and the network device on the Data Synchronization Details page, and find the reason why the differences exist. |
Different VLAN interface information than the network device
Keyword |
NEM_VLANIFINFO_INCONSISTENT |
Message text |
The VLAN interface information of the NEM was different than the network device: VLAN interface index: $1 VLAN interface description: $2 VLAN interface IP: $3 Management IP: $4 |
Variable fields |
$1: VLAN interface index. $2: VLAN interface description. $3: IP address of the VLAN interface. $4: Management IP address of the network device. |
Severity level |
Warning |
Example |
The VLAN interface information of the NEM was different than the network device: VLAN interface index: 123 VLAN interface description: SDN_VLAN_10 VLAN interface IP: 18.18.18.1 Management IP: 98.0.7.236 |
Explanation |
The VLAN interface information for the NEM was different than the network device. |
Recommended action |
See the VLAN interface information differences between the controller and the network device on the Data Synchronization Details page, and find the reason why the differences exist. |
Different loopback interface information than the network device
Keyword |
NEM_LOOPBACKIFINFO_INCONSISTENT |
Message text |
The loopback interface information of the NEM was different than the network device: Interface index: $1 Interface name: $2 Management IP: $3 |
Variable fields |
$1: Loopback interface index. $2: Loopback interface name. $3: Management IP address of the network device. |
Severity level |
Warning |
Example |
The loopback interface information of the NEM was different than the network device: Interface index: 1647 Interface name: LoopBack1000 Management IP: 192.168.251.67 |
Explanation |
The loopback interface information for the NEM was different than the network device. |
Recommended action |
See the loopback interface information differences between the controller and the network device on the Data Synchronization Details page, and find the reason why the differences exist. |
Network device connection to another region
Keyword |
DEVICE_CHANGE_REGION |
Message text |
The region to which $1 was connected changed from $2 to $3. |
Variable fields |
$1: Name of the network device. $2: Name of the original region to which the network device is connected. $3: Name of the new region to which the network device is connected. |
Severity level |
Warning |
Example |
The region to which device1 was connected changed from A to B. |
Explanation |
The network device was disconnected from the original region and connected to another region. |
Recommended action |
No action is required. |
VXLAN tunnel interface in up state
Keyword |
OPENFLOW_TUNNEL_UP |
Message text |
Port $1 of an OpenFlow device with datapath ID $2 OpenFlow IP $3 descriptor $4 was up, src VTEP IP $5, dst VTEP IP $6. |
Variable fields |
$1: Name of the VXLAN tunnel interface. $2: Datapath ID of the OpenFlow device. $3: IP address used by the OpenFlow device to establish a connection with the controller. $4: Description of the OpenFlow device. $5: Source VTEP IP. $6: Destination VTEP IP. |
Severity level |
Info |
Example |
Port Tun257 of an OpenFlow device with datapath ID 01:21:cc:3e:5f:09:04:7f OpenFlow IP 97.0.45.116 descriptor management ip = 1.1.1.3 was up, src VTEP IP 21.0.5.20, dst VTEP IP 21.0.5.18. |
Explanation |
The VXLAN tunnel interface on the OpenFlow device came up. |
Recommended action |
No action is required. |
VXLAN tunnel interface in down state
Keyword |
OPENFLOW_TUNNEL_DOWN |
Message text |
Port $1 of an OpenFlow device with datapath ID $2 OpenFlow IP $3 descriptor $4 was down, src VTEP IP $5, dst VTEP IP $6. |
Variable fields |
$1: Name of the VXLAN tunnel interface. $2: Datapath ID of the OpenFlow device. $3: IP address used by the OpenFlow device to establish a connection with the controller. $4: Description of the OpenFlow device. $5: Source VTEP IP. $6: Destination VTEP IP. |
Severity level |
Info |
Example |
Port Tun257 of an OpenFlow device with datapath ID 01:21:cc:3e:5f:09:04:7f OpenFlow IP 97.0.45.116 descriptor management ip = 1.1.1.3 was down, src VTEP IP 21.0.5.20, dst VTEP IP 21.0.5.18. |
Explanation |
The VXLAN tunnel interface on the OpenFlow device went down. |
Recommended action |
If the OpenFlow device has just established a connection with the controller, no action is required. In other cases, perform the following tasks: 30. Use the display interface tunnel command to verify the status of the tunnel interface. 31. If the tunnel interface is down, use the ping command on the device to verify the network connection between both ends of the tunnel. Specify the source VTEP IP address as the source IP address, and the destination VTEP IP address as the destination IP address in the ping command. 32. If the ping operation fails, verify that the VXLAN tunnel interface and the link connected to the interface are normal. |
Failed to add flow table
Keyword |
OPENFLOW_ADD_FLOWTABLE_FAILED |
Message text |
$1. The OpenFlow device with datapath ID $2 failed to add the flow table $3. |
Variable fields |
$1: Error message sent by the OpenFlow device. $2: Datapath ID of the OpenFlow device. $3: Information about the flow table. |
Severity level |
Warning |
Example |
BAD_MATCH. The OpenFlow device with datapath ID 01:21:cc:3e:5f:09:04:7f failed to add the flow table [tableId:1,Priority:29999,cookie0x2555364126,Matches:{"eth_type":"ipv4"},{"ipv4_dst":"11.0.0.2","mask":"255.255.255.255"},{"vswitch_interface_id":9223372036854775807},Action: {"eth_dst":"11:11:11:11:11:11"}]. |
Explanation |
The controller failed to deploy the flow table to the OpenFlow device. |
Recommended action |
Verify that the OpenFlow device supports the deployed flow table. You can upgrade the OpenFlow device to support the flow table if necessary. |
VLAN ID allocation failure
Keyword |
VLAN_RANGE_USE_UP |
Message text |
Failed to assign a VLAN ID to $1 because VLAN IDs in the VLAN pools for service gateway group $2 are used up. |
Variable fields |
$1: Service name. Options include Layer 3 DC Interconnect, Virtual Router Bind Service Resource, and Third-Party Firewall Deployment Mode. $2: Name of the service gateway group. |
Severity level |
Warning |
Example |
Failed to assign a VLAN ID to Layer 3 DC Interconnect because VLAN IDs in the VLAN pools for service gateway group gw are used up. |
Explanation |
Failed to allocate a VLAN ID to the service, because VLAN IDs in the VLAN pool have been used up. |
Recommended action |
Determine whether to add VLAN IDs to the VLAN pool. |
Used up VLAN IDs in the VLAN pools
Keyword |
VLAN_RANGE_USE_UP |
Message text |
VLAN IDs in the VLAN pool $1 are used up. |
Variable fields |
$1: Name of the VLAN pool. |
Severity level |
Warning |
Example |
VLAN IDs in the VLAN pool vlan001 are used up. |
VLAN IDs in the VLAN pools were used up. |
|
Recommended action |
Determine whether to perform the following tasks based on services: · Stop services. · Migrate services. · Add VLAN IDs to the VLAN pool. |
VLAN pool not exist
Keyword |
VLAN_RANGE_NOTEXIST |
Message text |
The tenant carrier network VLAN pool $1 does not exist. |
Variable fields |
$1: UUID of the VLAN pool. |
Severity level |
Warning |
Example |
The tenant carrier network VLAN pool vlan001 does not exist. |
Explanation |
The tenant carrier network VLAN pool does not exist. |
Recommended action |
Determine whether to create a VLAN pool. |
Used up VXLAN IDs in the VXLAN pools
Keyword |
VXLAN_POOL_USE_UP |
Message text |
VXLAN IDs in the VXLAN pool $1 are used up. |
Variable fields |
$1: Name of the VXLAN pool. |
Severity level |
Warning |
Example |
VXLAN IDs in the VXLAN pools vxlan001 are used up. |
Explanation |
VXLAN IDs in the VXLAN pools were used up. |
Recommended action |
Determine whether to perform the following tasks based on services: · Stop services. · Migrate services. · Add VXLAN IDs to the VXLAN pool. |
Used up IP addresses in general address pool
Keyword |
GENERAL_ADDRESS_POOL_INSUFFICIENT |
Message text |
IP addresses in the general address pool $1 are insufficient. |
Variable fields |
$1: Name of the address pool. |
Severity level |
Warning |
Example |
IP addresses in the general address pool address001 are insufficient. |
Explanation |
IP addresses in the general address pool were used up. |
Recommended action |
Determine whether to perform the following tasks based on services: · Stop services. · Migrate services. · Add IP addresses to the address pool. |
Used up IP addresses in address pool bound to service gateway group
Keyword |
BOUND_ADDRESS_POOL_INSUFFICIENT |
Message text |
IP addresses in the $1 address pool for service gateway group $2 are insufficient. |
Variable fields |
$1: Address pool type: · virtual device management. · tenant carrier network. · security internal network. · tenant carrier FW internal network. · tenant carrier LB internal network. · data center interconnection network. $2: Service gateway group name. |
Severity level |
Warning |
Example |
IP addresses in the tenant carrier network address pool for service gateway group gw are insufficient. |
Explanation |
IP addresses in the specified type of address pool for the service gateway group were used up. |
Recommended action |
Determine whether to perform the following tasks based on services: · Stop services. · Migrate services. · Add IP addresses to the address pool. |
Used up IP addresses in security external network address pool
Keyword |
SECURITY_EXTERNAL_POOL_USE_UP |
Message text |
Failed to assign an IP address to resource node $1 because IP addresses in the security external network address pool are used up. |
Variable fields |
$1: Name of the resource node. |
Severity level |
Warning |
Example |
Failed to assign an IP address to resource node 1234 because IP addresses in the security external network address pool are used up. |
Explanation |
Failed to assign a security external network IP address to the resource node because IP addresses in the security external network address pool were used up. |
Recommended action |
Determine whether to perform the following tasks based on services: · Stop services. · Migrate services. · Add IP addresses to the IP address pool. |
Used up IP addresses in default address pool
Keyword |
DEFAULT_ADDRESS_POOL_INSUFFICIENT |
Message text |
IP addresses in the default $1 address pool are insufficient. |
Variable fields |
$1: Address pool type: · Multicast network. · virtual device management. · virtual router interconnection network. |
Severity level |
Warning |
Example |
IP addresses in the default virtual device management address pool are insufficient. |
Explanation |
IP addresses in the default address pool were used up. |
Recommended action |
Determine whether to perform the following tasks based on services: · Stop services. · Migrate services. · Add IP addresses to the IP address pool. |
Address pool bound to service gateway group not exist
Keyword |
BINDEDADDRESS_POOL_NOTEXIST |
Message text |
The $1 address pool for service gateway group $2 does not exist. |
Variable fields |
$1: IP address pool type: · virtual device management. · tenant carrier network. · security internal network. · tenant carrier FW internal network. · tenant carrier LB internal network. · virtual router interconnection network. · data center interconnection network. $2: Name of the service gateway group. |
Severity level |
Warning |
Example |
The virtual device management address pool for service gateway group 123 does not exist. |
Explanation |
The specified type of address pool configured for the service gateway group does not exist. |
Recommended action |
Determine whether to create the address pool. |
Failed to assign security external network IP address to resource node
Keyword |
SECURITY_EXTERNAL_POOL_NOTEXIST |
Message text |
Failed to assign an IP address to resource node $1 because the security external network address pool does not exist. |
Variable fields |
$1: Name of the resource node. |
Severity level |
Warning |
Example |
Failed to assign an IP address to resource node 1234 because the security external network address pool does not exist. |
Explanation |
Failed to assign a security external network IP address to the resource node because the security external network address pool does not exist. |
Recommended action |
Configure a security external network address pool for the NGFW template used by the service resource to which the resource node belongs. |
Default address pool not exist
Keyword |
DEFAULT_ADDRESS_POOL_NOTEXIST |
Message text |
The default $1 address pool does not exist. |
Variable fields |
$1: Address pool type: · Multicast network. · virtual device management. · virtual router interconnection network. |
Severity level |
Warning |
Example |
The default virtual device management network address pool does not exist. |
Explanation |
The default address pool does not exist. |
Recommended action |
Determine whether to create the default address pool. |
Used up loopback interfaces on the firewall bound to the vRouters
Keyword |
LOOPBACK_NUMBER_USE_UP |
Message text |
Failed to create the vRouter link because loopback interfaces on the firewall bound to the vRouters are used up. The management IP address of the firewall is $1. |
Variable fields |
$1: Management IP of the firewall. |
Severity level |
Warning |
Example |
Failed to create the vRouter link because loopback interfaces on the firewall bound to the vRouters are used up. The management IP address of the firewall is 9.9.9.3. |
Explanation |
Failed to create the vRouter link because loopback interfaces on the firewall bound to the vRouters were used up. |
Recommended action |
Determine whether to delete existing vRouter links to release loopback interfaces. |
Start of NEM configuration recovery on non-active leader controllers
Keyword |
BEGIN_RECOVER_NEM_CONFIG |
Message text |
All non-active leader controllers started recovering the NEM configuration. |
Variable fields |
None. |
Severity level |
Info |
Example |
All non-active leader controllers started recovering the NEM configuration. |
Explanation |
All non-active leader controllers started recovering the NEM configuration, including physical NEs, gateway groups, VNF NEs, third-party NEs, and VLAN-VXLAN mappings. |
Recommended action |
As a best practice, do not perform any operations on the controllers during the configuration recovery process. |
End of NEM configuration recovery on non-active leader controllers
Keyword |
FINISH_RECOVER_NEM_CONFIG |
Message text |
All non-active leader controllers completed recovering the NEM configuration. |
Variable fields |
None. |
Severity level |
Info |
Example |
All non-active leader controllers completed recovering the NEM configuration. |
Explanation |
All non-active leader controllers completed recovering the NEM configuration, including physical NEs, gateway groups, VNF NEs, third-party NEs, and VLAN-VXLAN mappings. |
Recommended action |
No action is required. |
Data synchronization status changed to Not Synchronized
Keyword |
NEM_SMOOTHSTATUS_CHANGE_NOT_SYNCHRONIZED |
Message text |
The smooth status of the network device with management IP $1 changed to Not Synchronized. |
Variable fields |
$1: Management IP address of the network device. |
Severity level |
Warning |
Example |
The smooth status of the network device with management IP 98.0.27.6 changed to Not Synchronized. |
Explanation |
When the data synchronization status was Synchronized, the network device was deactivated and then activated, and the data synchronization status changed to Not Synchronized. |
Recommended action |
· No action is required if the network device can operate correctly. · Click Data synchronization on the Provision > Devices > Physical Devices page if the network device cannot operate correctly. |
Data synchronization status changed to Synchronized
Keyword |
NEM_SMOOTHSTATUS_CHANGE_SYNCHRONIZED |
Message text |
The smooth status of the network device with management IP $1 changed to Data Synchronized. |
Variable fields |
$1: Management IP address of the network device. |
Severity level |
Info |
Example |
The smooth status of the network device with management IP 98.0.27.6 changed to Data Synchronized. |
Explanation |
This message is generated in either of the following conditions: · When the data synchronization status was Not Synchronized, the network device was deactivated and then activated, and the data synchronization status changed to Synchronized. · When the data synchronization status was Not Synchronized, data synchronization was manually triggered, and the data synchronization status changed to Synchronized. |
Recommended action |
No action is required. |
Configuration initialization failure during NE activation
Keyword |
ACTIVE_DEVICE_FAILED |
Message text |
Failed to initialize the network element. |
Variable fields |
N/A |
Severity level |
Warning |
Example |
Failed to initialize the network element. |
Explanation |
Failed to initialize the configuration of the NE during the NE activation. |
Recommended action |
· Verify that the network connection is correct. · Verify that the device memory threshold is not reached. |
Maximum number of Ethernet service instances reached on interface
Keyword |
NEM_IFSERVICEINSTANCE_EXCEED |
Message text |
The number of Ethernet service instances on interface $1 of the network device with the management IP $2 has reached the limit. Failed to assign an ID to the Ethernet service instance: $3 |
Variable fields |
$1: Interface name. $2: Management IP address of the network device. $3: Ethernet service instance information. |
Severity level |
Warning |
Example |
The number of Ethernet service instances on interface GigabitEthernet 1/0/1 of the network device with the management IP 12.2.2.2 has reached the limit. Failed to assign an ID to the Ethernet service instance: SVLAN range: 1-10 CVLAN range: 2-5 xconnect vsi: 3 |
Explanation |
The number of Ethernet service instances on an interface of a device has reached the upper limit. As a result, the system fails to assign an Ethernet service instance ID to the interface. |
Recommended action |
On network device interfaces, plan the usage of the following Ethernet service instances: · Ethernet service instances manually configured on the device. · Ethernet service instances generated through the mapping table on the device or device interfaces. |
Controller failed to deploy settings to network device
Keyword |
NEM_CONFIG_SEND_FAILED |
Message text |
Device IP: $1 Reason: $2 NETCONF content: $3 |
Variable fields |
$1: Management IP address of the network device. $2: Failure reason. $3: Settings failed to be deployed. |
Severity level |
Warning |
Example |
Device:IP: 98.0.15.201 Reason: The configuration not supported on the specified target <VSI> <VsiName>SDN_VSI_2002</VsiName> <Statistics>true</Statistics> </VSI> |
Explanation |
The controller failed to deploy the settings to the network device. |
Recommended action |
Determine a solution based on the failure reason. |
VLAN and PVID inconsistency between member ports and aggregate interface
Keyword |
LAGGMEMBER_PERMMIT_PVIDVLAN_DIFFERENT |
Message text |
The permitted VLAN or PVID of member port $1 on device $2 is different from that of aggregate interface $3. The setting of the member port will be modified. |
Variable fields |
$2: Management IP address of the device. $3: Name of the aggregate interface. |
Severity level |
Warning |
Example |
The permitted VLAN or PVID of member port Ten-GigabitEthernet1 1/0/1 on device 192.168.1.1 is different from that of aggregate interface bridge-aggregation 1. The setting of the member port will be modified. |
Explanation |
The permitted VLAN or PVID of a port is different from that of the aggregate interface to which the port will be added. The settings of the port will be modified after the port is added to the aggregate interface, and a log entry will be generated. |
Recommended action |
No action is required. |
Mapping is unbound from port when port is added to aggregate interface
Keyword |
LAGGMEMBER_HAS_BIND_VLANDOMAINMAP |
Message text |
Member port $1 of device $2 has been bound to a mapping. The setting might be deleted. |
Variable fields |
$1: Name of the member port. $2: Management IP address of the device. |
Severity level |
Warning |
Example |
Member port $1 of device $2 has been bound to a mapping. The setting might be deleted. |
Explanation |
The specified port on the specified device has been bound to a mapping. The mapping will be unbound from the port when the port is added to the aggregate interface. |
Recommended action |
No action is required. |
Startup configuration file backup success
Keyword |
BACKUP_DEVICE_STARTUP_CONF_SUCCESS |
Message text |
Backed up the startup configuration files at $1 successfully. |
Variable fields |
$1: Management IP address of the target device. |
Severity level |
Info |
Example |
Backed up the startup configuration files at 98.0.19.91 successfully. |
Explanation |
The controller backed up the most recent startup configuration file for the device with the specified management IP address successfully. |
Recommended action |
No action is required. |
Startup configuration file backup failure
Keyword |
BACKUP_DEVICE_STARTUP_CONF_FAILED |
Message text |
Failed to back up the startup configuration files at $1. |
Variable fields |
$1: Management IP address of the target device. |
Severity level |
Warning |
Example |
Failed to back up the startup configuration files at 98.0.19.90. |
Explanation |
The controller failed to back up the most recent startup configuration file for the device with the specified management IP address. |
Recommended action |
Verify that the controller can reach the device through NETCONF and FTP. |
VTEP IP assignment failure
Keyword |
PHY_VTEP_POOL_USE_UP |
Message text |
Failed to assign a VTEP IP address to the NE because all addresses in the management network VTEP address pool $1 have been allocated to NEs and whitelists. |
Variable fields |
$1: Name of the management network VTEP address pool. |
Severity level |
Warning |
Example |
Failed to assign a VTEP IP address to the NE because all addresses in the management network VTEP address pool pool27 have been allocated to NEs and whitelists. |
Explanation |
Failed to assign a VTEP IP address to the NE because addresses in the management network VTEP address pool were used up by NEs and whitelists. |
Recommended action |
A VTEP address pool cannot be scaled up if addresses in the VTEP address pool have been allocated. Therefore, make sure a VTEP address pool has sufficient addresses before using the VTEP address pool. |
Software upgrading or patching failure
Keyword |
FAILED_UPGRADE_DEVICE |
Message text |
Software upgrade or patching failed on device $1 with IP $2. Reason: $3. |
Variable fields |
$1: Device name. $2: Device IP. $3: Reason why software upgrading or patching failed. Options include the following: · The FTP settings are invalid. · The remaining storage space is insufficient. · Failed to send the software package to the device. · The device and the software do not match. · The software does not exist. |
Severity level |
Warning |
Example |
Failed to upgrade the software or patch on device device01 with IP 192.168.1.1. Reason: The FTP settings are invalid. |
Explanation |
The controller failed to upgrade the remote device. |
Recommended action |
Take actions as prompted. |
Software upgrading or patching success
Keyword |
SUCCESS_UPGRADE_DEVICE |
Message text |
Software upgrade or patching succeeded on device $1 with IP $2. |
Variable fields |
$1: Device name. $2: Device IP. |
Severity level |
Info |
Example |
Software upgrade or patching succeeded on device01 with IP 192.168.1.1. |
Explanation |
Software upgrading or patching succeeded. |
Recommended action |
No action is required. |
Used up IP addresses in the underlay address pool
Keyword |
UNDERLAY_NETWORK_POOL_USE_UP |
Message text |
Failed to assign an underlay IP address to the NE because all addresses in the underlay address pool $1 have been allocated to NEs and whitelists. |
Variable fields |
$1: Name of the underlay address pool. |
Severity level |
Warning |
Example |
Failed to assign an underlay IP address to the NE because all addresses in the underlay address pool pool1 have been allocated to NEs and whitelists. |
Explanation |
Failed to assign an underlay IP address to the NE because addresses in the underlay address pool were used up by NEs and whitelists. |
Recommended action |
An underlay address pool cannot be scaled up if addresses in the address pool have been allocated. Therefore, make sure an underlay address pool has sufficient addresses before using the address pool. |
Device failed to come online automatically
Keyword |
DEVICE_AUTO_ONLINE_FAILED |
Message text |
Failed to add the device to the NE list after the device comes online automatically. Reason: $1 |
Variable fields |
$1: Reason why the device failed to come online automatically. Options include the following: · The VTEP IP has been allocated. · Failed to allocate a VTEP IP. · Failed to allocate an underlay IP from the underlay address pool. · The VTEP IP is null when the underlay protocol is ISIS. · The VTEP IP cannot be in the underlay address pool. · The system failed to issue the IP address provided by the VTEP IP pool, management IP pool, or underlay IP pool to the device and failed to manage the device consequently. · Please first configure an IP pool for auto deployment. |
Severity level |
Warning |
Example |
Failed to add the device to the NE list after the device comes online automatically. Reason: The VTEP IP has been allocated. |
Explanation |
The device failed to come online automatically. |
Recommended action |
Take actions as prompted. |
Used up VLAN IDs of downlink port on leaf device
Keyword |
LEAF_VLAN_RANGE_USE_UP |
Message text |
VLAN IDs of leaf $1 port $2 for access $3 are used up. |
Variable fields |
$1: IP address of the leaf device. $2: Downlink port on the leaf device. $3: IP address of the access device. |
Severity level |
Warning |
Example |
VLAN IDs of leaf192.168.133.201 port Bridge-Aggregation123 for access 192.168.133.202 are used up. |
Explanation |
VLAN IDs that the downlink port on the leaf device can allocate to access devices have been used up. |
Recommended action |
Identify whether the port has allocated VLAN IDs to inactive access devices or migrate the target access device to another port of the leaf device. |
IRF member device was not powered off during replacement
Keyword |
DEVICE_NOT_POWERED_OFF |
Message text |
IRF member device $1 is not powered off while being replaced. |
Variable fields |
$1: Management IP address of the failed device. |
Severity level |
Warning |
Example |
IRF member device 10.100.0.1 is not powered off while being replaced. |
Explanation |
After the failed device in an IRF fabric was replaced, the IRF fabric split because the failed device was not powered off during replacement. |
Recommended action |
33. Power off the failed device in the IRF fabric. 34. If the problem persists, log in to the replacement device to set its member ID to that of the failed device. |
CID editing failure
Keyword |
DEVICE_CID_MODIFY_FAIL |
Message text |
Failed to modify the CID-IP binding relationship. Failed device management IP: $1, replacement device management IP: $2, replacement device VLAN4094 CID: $3, replacement device VLAN1 IP: $4, replacement device VLAN1 CID: $5. |
Variable fields |
$1: Management IP address of the failed device. $2: Management IP address of the replacement device. $3: VLAN4094 CID of the replacement device. $4: VLAN1 IP of the replacement device. $5: VLAN1 CID of the replacement device. |
Severity level |
Error |
Example |
Failed to modify the CID-IP binding relationship. Failed device management IP: 16.100.65.11, replacement device management IP: 16.100.65.12, replacement device VLAN4094 CID: 0037-3832-6332-3965-3661-3833-302d-564c-414e-3030-3031, replacement device VLAN1 IP: 16.100.55.66, replacement device VLAN1 CID: 0037-3832-6332-3965-3661-3833-302d-564c-414e-3030-3031. |
Explanation |
The controller failed to edit the CID-IP binding relationship on the DHCP server. |
Recommended action |
Manually edit the CID-IP binding relationship on the DHCP server. |
Starting data synchronization or auditing
Keyword |
DEVICE_START_SYNC |
Message text |
Device $1 started to synchronize or audit data. |
Variable fields |
$1: IP address of the device. |
Severity level |
Info |
Example |
Device 192.168.100.101 started to synchronize or audit data. |
Explanation |
Data synchronization or auditing was started on the device. |
Recommended action |
No action is required. |
Finishing data synchronization or auditing
Keyword |
DEVICE_END_SYNC |
Message text |
Device $1 finished to synchronize or audit data. |
Variable fields |
$1: IP address of the device. |
Severity level |
Info |
Example |
Device 192.168.100.101 finished to synchronize or audit data. |
Explanation |
Data synchronization or auditing was finished on the device. |
Recommended action |
No action is required. |
Starting fine-grained synchronization
Keyword |
DEVICE_START_SYNC |
Message text |
Fine-grained synchronization started on device $1. |
Variable fields |
$1: IP address of the device. |
Severity level |
Info |
Example |
Fine-grained synchronization started on device 192.168.2.100. |
Explanation |
The device started fine-grained synchronization. |
Recommended action |
No action is required. |
Finishing fine-grained synchronization
Keyword |
DEVICE_END_SYNC |
Message text |
Fine-grained synchronization finished on device $1. Result: $2. |
Variable fields |
$1: IP address of the device. $2: Result of fine-grained synchronization: · Success. · Unknown fine-grained synchronization error. · The data has expired. · The selected data does not exist. · The configuration differences on the controller are inconsistent with the actual configuration differences. · Settings dependent on other settings cannot be synchronized separately. |
Severity level |
Info |
Example |
Fine-grained synchronization finished on device 192.168.2.100. Result: Settings dependent on other settings cannot be synchronized separately. |
Explanation |
The device finished fine-grained synchronization. |
Recommended action |
No action is required. |
Executing an audit task
Keyword |
DEVICE_END_SYNC |
Message text |
The controller automatically audited devices as scheduled. Periodic configuration audit task name: $1. Audited objects:$2. |
Variable fields |
$1: Audit task name. $2: Names of the audited devices. |
Severity level |
Info |
Example |
The controller automatically audited devices as scheduled. Periodic configuration audit task name: audit1. Audited objects:[98.0.8.58] |
Explanation |
The controller executed an audit task. |
Recommended action |
No action is required. |
Track number allocation failure
Keyword |
DEVICE_TRACK_FULL |
Message text |
Device $1 have allocated all track. |
Variable fields |
$1: Device ID. |
Severity level |
Info |
Example |
Device b1e045fd-9de1-4347-8dae-30bb14b68a78 have allocated all track. |
Explanation |
Track numbers on the specified device have been used up. |
Recommended action |
Run the service on another device to obtain a track number. |
Used up loopback interfaces on a device
Keyword |
LOOPBACKIF_IDPOOL_USE_UP |
Message text |
Loopback interfaces on the device with management IP address $1 have been used up. |
Variable fields |
$1: Management IP address of the device. |
Severity level |
Warning |
Example |
Loopback interfaces on the device with management IP address 192.168.251.68 have been used up. |
Explanation |
Loopback interfaces on the device with the specified management IP address have been used up. |
Recommended action |
Determine whether to stop some services to release loopback interfaces. |
Aggregate interface creation failure
Keyword |
CREATE_AGGREGATION_PORT |
Message text |
The uplink interfaces $1 and $2 of the access device $3 is already in a link aggregation group. |
Variable fields |
$1: Uplink interface name. $2: Uplink interface name. $3: IP address of the device. |
Severity level |
Warning |
Example |
The uplink interfaces Ten-GigabitEthernet1/0/3 and Ten-GigabitEthernet1/0/5 of the access device 192.168.169.101 is already in a link aggregation group. |
Explanation |
The controller failed to aggregate two uplink interfaces on an access device, because the uplink interfaces are already in another aggregation group. |
Recommended action |
· Select other uplink interfaces on the access device. · Remove the uplink interfaces from the aggregation group, and then aggregate the interfaces again. |
Segment ID conflict between VLAN pool and VLAN-type network
Keyword |
VLAN_POOL_NETWORK_CONFILICT |
Message text |
The $1 VLAN pool cannot contain segment IDs of external networks or vNetworks of the VLAN type. |
Variable fields |
$1: VLAN pool type. |
Severity level |
Warning |
Example |
The tenant carrier network VLAN pool cannot contain segment IDs of external networks or vNetworks of the VLAN type. |
Explanation |
The VLAN pool contains segment IDs of external networks or vNetworks of the VLAN type. |
Recommended action |
Edit the VLAN ID ranges of the VLAN pool. |
NEW thread pool rejected tasks
Keyword |
NEM_THREAD_POOL_REJECT_TASK |
Message text |
Thread pool $1 rejected task, current thread size $2, max thread size $3, current queue size $4, max queue size $5. |
Variable fields |
$1: Thread pool name. $2: Current number of threads. $3: Maximum number of threads. $4: Current number of queues. $5: Maximum number of queues. |
Severity level |
Error |
Example |
Thread pool NemVsmEventProcessor rejected task, current thread size 1, max thread size 1, current queue size 1, max queue size 1. |
Explanation |
NEW thread pool rejected tasks because of insufficient resources. |
Recommended action |
Please contact the technical support. |
NEM deleted aged link entry
Keyword |
NEM_AGED_DELETE_LINK |
Message text |
Deleted an aged link entry: System name=$1, device IP=$2, interface name=$3. |
Variable fields |
$1: Device name. $2: Management IP address of the device. $3: Interface name. |
Severity level |
INFO |
Example |
Deleted an aged link entry: System name=22, device IP: 192.168.55.21, interface name=Twenty-FiveGigE1/0/12. |
Explanation |
NEM deleted an aged link entry. |
Recommended action |
No action is required. |
NERestconf
This section contains NERestconf messages.
Task rejected by the thread pool of the NERestconf module
Keyword |
NERESTCONF_THREAD_POOL_REJECT_TASK |
Message text |
Thread pool $1 rejected task, current thread size $2, max thread size $3, current queue size $4, max queue size $5. |
Variable fields |
$1: Name of the thread pool. $2: Current number of threads. $3: Maximum number of threads. $4: Current number of queues. $5: Maximum number of queues. |
Severity level |
Error |
Example |
Thread pool YangOperationManager rejected task, current thread size 1, max thread size 1, current queue size 1047586, max queue size 1047586. |
Explanation |
Failed to execute the new task because the thread pool of the NERestconf module is full. |
Recommended action |
Contact H3C support. |
NGFWM messages
This section contains NGFW manager messages.
NGFW resource creation failure
Keyword |
CREATE_NGFW_RESOURCE_FAILED |
Message text |
Failed to create NGFW resource $1. |
Variable fields |
$1: NGFW resource name. |
Severity level |
Error |
Example |
Failed to create NGFW resource resource1. |
Explanation |
Failed to create an NGFW resource. |
Recommended action |
To resolve the problem: 35. Verify that the network connection between the NGFW manager and device is correct. 36. Verify that a NETCONF session has been established between the NGFW manager and device. 37. Verify that the template or NGFW resource configuration is consistent with the device configuration. For example, the device interface bound to the template or NGFW resource is not used by other services. If inconsistency exists, change the template or NGFW resource configuration. |
NGFW resource modification failure
Keyword |
UPDATE_NGFW_RESOURCE_FAILED |
Message text |
Failed to update NGFW resource $1. |
Variable fields |
$1: NGFW resource name. |
Severity level |
Error |
Example |
Failed to update NGFW resource resource1. |
Explanation |
Failed to modify an NGFW resource. |
Recommended action |
To resolve the problem: 38. Verify that the network connection between the NGFW manager and device is correct. 39. Verify that a NETCONF session has been established between the NGFW manager and device. |
NGFW resource deletion failure
Keyword |
DELETE_NGFW_RESOURCE_FAILED |
Message text |
Failed to delete NGFW resource $1. |
Variable fields |
$1: NGFW resource name. |
Severity level |
Error |
Example |
Failed to delete NGFW resource resource1. |
Explanation |
Failed to delete an NGFW resource. |
Recommended action |
To resolve the problem: 40. Verify that the network connection between the NGFW manager and device is correct. 41. Verify that a NETCONF session has been established between the NGFW manager and device. |
NGFW resource creation with NETCONF failure
Keyword |
NETCONF_CREATE_NGFW_RESOURCE_FAILED |
Message text |
Failed to use NETCONF to create an NGFW resource for security engine group $1 on device at $2. |
Variable fields |
$1: Security engine group ID. If the parameter value is null, the device does not have a security engine group. $2: IP address of the device. |
Severity level |
Error |
Example |
Failed to use NETCONF to create an NGFW resource for security engine group 10 on device at 192.168.110.10. |
Explanation |
Failed to use NETCONF to create an NGFW resource. |
Recommended action |
To resolve the problem: 42. Verify that the network connection between the NGFW manager and device is correct. 43. Verify that a NETCONF session has been established between the NGFW manager and device. |
NGFW resource creation with NETCONF success
Keyword |
NETCONF_CREATE_NGFW_RESOURCE_SUCCESS |
Message text |
Used NETCONF to create an NGFW resource at $1: ID $2; Name $3. |
Variable fields |
$1: Device IP address. $2: NGFW resource ID. $3: NGFW resource name. |
Severity level |
Info |
Example |
Used NETCONF to create an NGFW resource at 192.168.110.10: ID 10; Name resource1. |
Explanation |
Used NETCONF to create an NGFW resource successfully. |
Recommended action |
No action is required. |
NGFW resource modification with NETCONF success
Keyword |
NETCONF_UPDATE_NGFW_RESOURCE_SUCCESS |
Message text |
Used NETCONF to update an NGFW resource at $1: ID $2; Name $3. |
Variable fields |
$1: Device IP address. $2: NGFW resource ID. $3: NGFW resource name. |
Severity level |
Info |
Example |
Used NETCONF to update an NGFW resource at 192.168.110.10: ID 10; Name resource1. |
Explanation |
Used NETCONF to modify an NGFW resource successfully. |
Recommended action |
No action is required. |
NGFW resource modification with NETCONF failure
Keyword |
NETCONF_UPDATE_NGFW_RESOURCE_FAILED |
Message text |
Failed to use NETCONF to update an NGFW resource at $1: ID $2; Name $3. |
Variable fields |
$1: Device IP address. $2: NGFW resource ID. $3: NGFW resource name. |
Severity level |
Error |
Example |
Failed to use NETCONF to update an NGFW resource at 192.168.110.10: ID 10; Name resource1. |
Explanation |
Failed to use NETCONF to modify an NGFW resource. |
Recommended action |
To resolve the problem: 44. Verify that the network connection between the NGFW manager and device is correct. 45. Verify that a NETCONF session has been established between the NGFW manager and device. |
Start of NGFWM configuration recovery on non-active leader controllers
Keyword |
BEGIN_RECOVER_NGFWM_CONFIG |
Message text |
All non-active leader controllers started recovering the NGFWM configuration. |
Variable fields |
N/A |
Severity level |
Info |
Example |
All non-active leader controllers started recovering the NGFWM configuration. |
Explanation |
All non-active leader controllers started recovering the NGFWM configuration, including devices, resource pools, and NGFW resources. |
Recommended action |
As a best practice, do not perform any operations on the controllers during the configuration recovery process. |
End of NGFWM configuration recovery on non-active leader controllers
Keyword |
FINISH_RECOVER_NGFWM_CONFIG |
Message text |
All non-active leader controllers completed recovering the NGFWM configuration. |
Variable fields |
N/A |
Severity level |
Info |
Example |
All non-active leader controllers completed recovering the NGFWM configuration. |
Explanation |
All non-active leader controllers completed recovering the NGFWM configuration, including devices, resource pools, and NGFW resources. |
Recommended action |
No action is required. |
Changed NETCONF password successfully
Keyword |
UPDATE_DEVICE_PASSWORD_SUCCESS |
Message text |
Successfully updated the NETCONF password for the device. |
Variable fields |
N/A |
Severity level |
Info |
Example |
Successfully updated the NETCONF password for the device. |
Explanation |
Changed the NETCONF password successfully. |
Recommended action |
No action is required. |
Failed to change the NETCONF password
Keyword |
UPDATE_DEVICE_PASSWORD_FAILED |
Message text |
Failed to update the NETCONF password for the device. |
Variable fields |
N/A |
Severity level |
Error |
Example |
Failed to update the NETCONF password for the device. |
Explanation |
Failed to change the NETCONF password. |
Recommended action |
Verify that the NETCONF connection is in normal state. |
OAM
This section contains OAM system messages.
Failed to create image file upload path
Keyword |
FAILED_CREATE_BASE_UPLOAD |
Message text |
Failed to create the image file upload path. Reason: $1 |
Variable fields |
$1: Possible failure reasons, including: · Failed to get the SNA Installer node information. · The user does not have the permission to perform the operation. |
Severity level |
Warning |
Example |
Failed to create the image file upload path. Reason: Failed to get the SNA Installer node information. |
Explanation |
Failed to create the image file upload path at system startup. |
Recommended action |
Perform the following steps: 46. Verify that the SNA Installer nodes are operating correctly. 47. Verify that the user has the directory creation privilege. |
Software upgrade or patching failed
Keyword |
FAILED_UPGRADE_DEVICE |
Message text |
Software upgrade or patching failed on device $1 at $2. Reason: $3. |
Variable fields |
$1: Device name. $2: Device IP address. $3: Possible failure reasons, including: · Failed to push image file to device. · Disk space check failed. · Failed to run command to start upgrade. · Failed to restart device. · Failed to connect to device. · Controller not available. · Failed to obtain the FTP state on the device. · Failed to execute the save command on the device. · Only devices in maintenance state can be upgraded. · Command execution timed out. · Failed to check settings before ISSU. · Failed to set the image file to use. · Failed to test ISSU upgrade. · Failed to perform ISSU. · Failed to reset ISSU configuration. · Failed to start GIR (place system in maintenance mode). · Failed to stop GIR (restore normal mode). |
Severity level |
Warning |
Example |
Software upgrade or patching failed on device device01 at 192.168.1.1. Reason: The remaining storage space is insufficient. |
Explanation |
The controller failed to upgrade a remote device. |
Recommended action |
Take the remediation action as prompted. |
Software upgrade or patching succeeded
Keyword |
SUCCESS_UPGRADE_DEVICE |
Message text |
Software upgrade or patching succeeded on device $1 at $2. |
Variable fields |
$1: Device name. $2: Device IP address. |
Severity level |
Info |
Example |
Software upgrade or patching succeeded on device device01 at 192.168.1.1. |
Explanation |
Software upgrade or patching succeeded on a device. |
Recommended action |
No action required. |
Failed to replace a device
Keyword |
DEVICE_REPLACE_FAILED |
Message text |
Device replacement failed on device $1 at $2. Reason: $3. |
Variable fields |
$1: Device UUID. $2: Device IP address. $3: Possible failure reasons, including: · The replacement device failed to come online. · The device failed to come online. · Failed to get the device SN. · Failed to get the configuration file. · Failed to deploy the TFTP server and configuration file information to the replacement device. · Failed to deploy the IRF member information to the replacement device. · Failed to reboot the replacement device. · Failed to delete the temporary configuration file. · The device is no in maintenance state. · The controller is not reachable. · Failed to connect to the device. · Failed to get the configuration file of the faulty device. · TFTP error. · The configuration file with the specified name does not exist. · The backup configuration file of the faulty device does not exist. · The replacement device does not exist. · Failed to activate the replacement device. · Failed to update the DHCP client ID. |
Severity level |
Warning |
Example |
device replace failed on device 13724991-d73c-48d2-82c1-c64f5842c6e1 at 192.168.154.180. Reason: device is non maintain. |
Explanation |
Failed to replace a device by using a device replacement task. |
Recommended action |
Determine the cause for the failure and re-create the device replacement task. |
Failed to back up device configuration file
Keyword |
FAILED_BACKUP_CONFIG_FILE |
Message text |
Configuration file backup failed on device $1 at $2. Reason: $3. |
Variable fields |
$1: Device name. $2: Device IP address. $3: Possible failure causes, including: · Failed to transmit the configuration file from the device to the controller. · Failed to get global FTP status on device. · Failed to get user FTP status on device. · Failed to get the configuration file info on the device. · Failed to save the configuration file on the device. · Failed to enable global FTP on device. · Failed to enable user FTP on device. · Failed to synchronize the configuration file. |
Severity level |
Warning |
Example |
Configuration file backup failed on device dev11 at 192.168.105.11. Reason: Failed to disable FTP on device. |
Explanation |
Failed to back up the configuration file on a device according to the configuration file backup task settings. |
Recommended action |
Determine the cause for the failure and re-create the backup task. |
Failed to restore a device
Keyword |
DEVICE_ROLLBACK_FAILED |
Message text |
Failed to restore device: $1 |
Variable fields |
$1: Device UUID. |
Severity level |
Warning |
Example |
Failed to restore device: [76f15eab-b5db-4184-b92f-3b64427b0387] |
Explanation |
Failed to restore a device. |
Recommended action |
Perform the following steps: 48. Verify that the device to be restored is online. 49. Verify that the configuration file to be restored exists. 50. Verify that the configuration file matches the device. |
Scheduled check executed successfully
Keyword |
SUCCESS_TIMER_CHECK |
Message text |
Scheduled check execution succeeded. |
Variable fields |
N/A |
Severity level |
Info |
Example |
Scheduled check execution succeeded. |
Explanation |
The scheduled check was executed successfully. |
Recommended action |
No action is required. |
Failed to execute scheduled check
Keyword |
FAILED_TIMER_CHECK |
Message text |
Scheduled check execution failed. |
Variable fields |
N/A |
Severity level |
Warning |
Example |
Scheduled check execution failed. |
Explanation |
Failed to run a scheduled check. |
Recommended action |
Please verify that the controller is operating correctly. |
Failed to create controller restore point
Keyword |
FAILED_CREATE_CONTROLLER_RESTORE_POINT |
Message text |
Failed to create the controller restore point. |
Variable fields |
N/A |
Severity level |
Warning |
Example |
Failed to create the controller restore point. |
Explanation |
Failed to create the controller restore point. |
Recommended action |
Please verify that the controller and nodes are operating correctly. |
Failed to create device restore point
Keyword |
FAILED_CREATE_DEVICE_RESTORE_POINT |
Message text |
Failed to create the restore point for device: $1. |
Variable fields |
$1: IP address of the device. |
Severity level |
Warning |
Example |
Failed to create the restore point for device: 1.1.1.1. |
Explanation |
Failed to create the restore point for a specific device. |
Recommended action |
Please verify that the controller and nodes are operating correctly. |
Failed to roll back controller configuration
Keyword |
FAILED_ROLLBACK_CONTROLLER |
Message text |
Failed to roll back the controller. |
Variable fields |
N/A |
Severity level |
Warning |
Example |
Failed to roll back the controller. |
Explanation |
Failed to roll back the controller configuration. |
Recommended action |
Please verify that the controller and nodes are operating correctly. |
RDR
This section contains remote disaster recovery messages.
PXC cluster anomaly
Keyword |
RDRS_PXC_CLUSTER_UNHEALTHY |
Message text |
The PXC cluster is unhealthy. |
Variable fields |
N/A |
Severity level |
Warning |
Example |
The PXC cluster is unhealthy. |
Explanation |
The PXC cluster became unhealthy. |
Recommended action |
· Verify that the PXC container is normal in the background. · Verify that the network is normal between the primary and backup sites. |
PXC cluster creation failure
Keyword |
PXC_CREATE_FAILED |
Message text |
Failed to create the PXC cluster on the site of backup component. |
Variable fields |
N/A |
Severity level |
Error |
Example |
Failed to create the PXC cluster on the site of backup component. |
Explanation |
Failed to create the PXC cluster. |
Recommended action |
· Verify that the PXC container is normal at the site of the backup component. · See the troubleshooting guide to resolve the issue. |
Failure to fix a PXC cluster
Keyword |
PXC_FIX_FAILED |
Message text |
Failed to fix the PXC cluster on the site of backup component. |
Variable fields |
N/A |
Severity level |
Error |
Example |
Failed to fix the PXC cluster on the site of backup component. |
Explanation |
Failed to fix the PXC cluster. |
Recommended action |
· Verify that the PXC container is normal at the site of the backup component. · See the troubleshooting guide to resolve the issue. |
Heartbeat channel anomaly
Keyword |
HEARTBEAT_CHANNEL_INACTIVE |
Message text |
The heartbeat channel is disconnected. |
Variable fields |
N/A |
Severity level |
Warning |
Example |
The heartbeat channel is disconnected. |
Explanation |
The heartbeat channel was disconnected. |
Recommended action |
Check the network connectivity between the primary and backup sites. |
Switchover to backup role failed
Keyword |
DROP_DC_FAILED |
Message text |
The primary component failed to switch to the backup role. Reason: $1. |
Variable fields |
$1: Failure reason: · HTTP request failed. · RDR system error. |
Severity level |
Error |
Example |
The primary component failed to switch to the backup role. Reason: HTTP request failed. |
Explanation |
The primary component failed to switch to the backup role. |
Recommended action |
· Check the connectivity of the primary and backup sites and the SNA Installer node state. · Check the remote disaster recovery system status by entering kubectl get po -n base-service | grep rdr on any node. |
Switchover to backup role succeeded
Keyword |
DROP_APP_DC |
Message text |
The primary component switched to the backup role. |
Variable fields |
N/A |
Severity level |
Info |
Example |
The primary component switched to the backup role. |
Explanation |
The primary component successfully switched to the backup role. |
Recommended action |
No action is required. |
Switchover to primary role failed
Keyword |
TAKE_OVER_DC_FAILED |
Message text |
The backup component failed to switch to the primary role. Reason: $1. |
Variable fields |
$1: Failure reason: · Request timed out. · HTTP request failed. · RDR system error. |
Severity level |
Error |
Example |
The backup component failed to switch to the primary role. Reason: Request timed out. |
Explanation |
The backup component failed switched to the primary role. |
Recommended action |
Verify that the remote disaster recovery system is normal at the site of the backup component. |
Switchover to primary role succeeded
Keyword |
TAKE_OVER_APP |
Message text |
The backup component switched to the primary role. |
Variable fields |
N/A |
Severity level |
Info |
Example |
The backup component switched to the primary role. |
Explanation |
The backup component successfully switched to the primary role. |
Recommended action |
No action is required. |
SNA Installer service anomaly
Keyword |
MATRIX_HTTP_FAILD |
Message text |
SNA Installer is unhealthy. Reason: $1. |
Variable fields |
$1: Reason for the SNA Installer service anomaly: · Failed to connect to the remote SNA Installer. · Failed to obtain the master node details. · Failed to obtain detailed information about the SNA Installer nodes. · Request to SNA Installer failed. |
Severity level |
Warning |
Example |
SNA Installer is unhealthy. Reason: Failed to connect to the remote SNA Installer. |
Explanation |
The SNA Installer service is unhealthy. |
Recommended action |
Verify that the SNA Installer service is normal at the primary and backup sites, and then try again. |
Disaster recovery component deletion failure
Keyword |
DEL_RDRS_RELATION_FAILED |
Message text |
Failed to delete the disaster recovery component. |
Variable fields |
N/A |
Severity level |
Error |
Example |
Failed to delete the disaster recovery component. |
Explanation |
Failed to delete the disaster recovery component. |
Recommended action |
Verify that the SNA Installer service is normal at the primary and backup sites, and then try again. |
SEERENGINE
This section contains SEERENGINE messages.
IP version mismatch between vPort destination network segment and vPort IP
Keyword |
VPORT_IP_VERSION_MISMATCH |
Message text |
Failed to deploy vPort policy configuration because of IP version mismatch between the destination network segment and the vPort IP address: vPort name=$1, destination network segment=$2, vPort IP address=$3. |
Variable fields |
$1: vPort name. $2: Destination network segment of a vPort. $3: IP address of a vPort. |
Severity level |
Info |
Example |
Failed to deploy vPort policy configuration because of IP version mismatch between the destination network segment and the vPort IP address: vPort name=vport_vxlan_30, destination network segment= 1::1/24, vPort IP address=1.1.1.1. |
Explanation |
Failed to deploy vPort configuration because of IP version mismatch between the destination network segment of the vPort and the vPort IP address. |
Recommended action |
Create the vPort configuration again and make sure the vPort destination network segment and the vPort IP use the same IP version. |
Mirroring destination profile with PHY-type vPort and without any destination IP address
Keyword |
INVALID_VPORT_PHY_DESTINATION_ADDRESS_EMPTY |
Message text |
Failed to deploy vPort policy configuration because the vPort is of the PHY type and the mirroring destination profile does not contain any destination IP addresses: vPort name=$1, mirroring destination profile ID=$2. |
Variable fields |
$1: Name of a vPort in a vPort policy. $2: Mirroring destination profile ID. |
Severity level |
Info |
Example |
Failed to deploy vPort policy configuration because the vPort is of the PHY type and the mirroring destination profile does not contain any destination IP addresses: vPort name= 11, mirroring destination profile ID=5ad24945-2a0a-4181-8424-427c432da88b. |
Explanation |
Failed to deploy vPort configuration because the vPort in the vPort policy is of the PHY type and the mirroring destination profile does not contain any destination IP addresses. |
Recommended action |
After a vPort policy is created, you cannot change the vPort bound to the policy. After a mirroring destination profile is created without any destination IP addresses, you cannot add new IP addresses to it. To resolve this problem, perform either of the following tasks: · Create the vPort policy again, and make sure the vPort in the vPort policy is not of the PHY type. · Create the mirroring destination profile again, and make sure the mirroring destination profile contains destination IP addresses. Then, create a new vPort policy, and specify this mirroring destination profile. |
IP version mismatch between OVS-type vPort VTEP IP and mirroring destination profile destination IP
Keyword |
REMOTE_IP_IS_INCONSISTENT_TO_VTEP_IP |
Message text |
vPort mirroring failed because of IP version mismatch between the destination IP address of the mirroring destination profile and the VTEP IP address of the vPort: VTEP IP address=$1, destination IP address=$2. |
Variable fields |
$1: VTEP IP of the OVS-type vPort. $2: Destination IP address in the mirroring destination profile. |
Severity level |
Info |
Example |
vPort mirroring failed because of IP version mismatch between the destination IP address of the mirroring destination profile and the VTEP IP address of the vPort: VTEP IP address=1.1.1.1, destination IP address=1::1/24. |
Explanation |
vPort mirroring failed because of IP version mismatch between the VTEP IP address of the OVS-type vPort and the destination IP address of the mirroring destination profile. |
Recommended action |
Create the mirroring destination profile again and make sure its destination IP address and the VTEP IP of the OVS-type vPort use the same IP version. |
ServiceChain
This section contains service chain messages.
Start of service chain configuration recovery on non-active leader controllers
Keyword |
BEGIN_RECOVER_SC_CONFIG |
Message text |
All non-active leader controllers started recovering the service chain configuration. |
Variable fields |
N/A |
Severity level |
Info |
Example |
All non-active leader controllers started recovering the service chain configuration. |
Explanation |
All non-active leader controllers started recovering the service chain configuration, such as settings for service chains and contexts. |
Recommended action |
As a best practice, do not perform any operations on the controllers during the configuration recovery process. |
End of service chain configuration recovery on non-active leader controllers
Keyword |
FINISH_RECOVER_SC_CONFIG |
Message text |
All non-active leader controllers completed recovering the service chain configuration. |
Variable fields |
N/A |
Severity level |
Info |
Example |
All non-active leader controllers completed recovering the service chain configuration. |
Explanation |
All non-active leader controllers completed recovering the service chain configuration, such as settings for service chains and contexts. |
Recommended action |
No action is required. |
Simulation
This section contains simulation messages.
Successfully called the production interface
Keyword |
SUCCESS_SIMULATION_APP_CALL_DC |
Message text |
Successfully called the production interface. |
Variable fields |
N/A |
Severity level |
Info |
Example |
Successfully called the production interface. |
Explanation |
The production interface was called successfully in the simulation state. |
Recommended action |
No action is required. |
Failed to call the production interface
Keyword |
FAILED_SIMULATION_APP_CALL_DC |
Message text |
Failed to call the production interface. Reason: $1 |
Variable fields |
$1: Possible failure causes. |
Severity level |
Warn |
Example |
Failed to call the production interface. Reason: The segment ID is out of range. |
Explanation |
Failed to call the production interface in the simulation state. |
Recommended action |
· Verify that the cluster nodes are operating properly. · Verify that the user has the permissions to create directories. · Verify that the controller is operating properly. · Verify that the design mode is operating properly. · Verify that the simulation microservice is operating properly. · Verify that the controller data is the same as the simulation state data. |
Successfully called the emulation interface
Keyword |
SUCCESS_SIMULATION_APP_CALL_SIMULATION_DC |
Message text |
Successfully called the emulation interface. |
Variable fields |
N/A |
Severity level |
Info |
Example |
Successfully called the emulation interface. |
Explanation |
The emulation interface was successfully called by simulation microservice. |
Recommended action |
No action is required. |
Failed to call the emulation interface
Keyword |
FAILED_SIMULATION_APP_CALL_SIMULATION_DC |
Message text |
Failed to call the emulation interface. Reason: $1 |
Variable fields |
$1: Possible failure causes. |
Severity level |
Warn |
Example |
Failed to call the emulation interface. Reason: The segment ID is out of range. |
Explanation |
The simulation microservice failed to call the emulation interface. |
Recommended action |
· Verify that the cluster nodes are operating properly. · Verify that the user has the permissions to create directories. · Verify that the controller is operating properly. · Verify that the design mode is operating properly. · Verify that the simulation microservice is operating properly. · Verify that the design mode parameters are valid. |
SIMULATION_NETWORK
This section contains simulation network messages.
Failed to delete a VM
Keyword |
DELETE_VNF_FAILED |
Message text |
Delete vnf “$1” in VNFM failed. Reason:$2. |
Variable fields |
$1: VM name. $2: Possible failure causes. |
Severity level |
Error |
Example |
Delete vnf “v6890-vnf” in VNFM failed. Reason:XXX. |
Explanation |
Failed to delete a VM. |
Recommended action |
Verify that the VNFM system is operating properly and the VM exists. |
Failed to delete a VM template
Keyword |
DELETE_VNF_TEMPLATE_FAILED |
Message text |
Delete vnf template “$1” in VNFM failed. Reason:$2. |
Variable fields |
$1: VM template name. $2: Possible failure causes. |
Severity level |
Error |
Example |
Delete vnf template “v6850-template” in VNFM failed. Reason:XXX. |
Explanation |
Failed to call the VNFM interface to delete a VM template. |
Recommended action |
Verify that the VNFM system is operating properly and the VM template exists. |
Failed to delete a bridge
Keyword |
DELETE_BRIDGE_FAILED |
Message text |
Delete bridge on vnf “$1” failed. Reason:$2. |
Variable fields |
$1: VM name. $2: Possible failure causes. |
Severity level |
Error |
Example |
Delete bridge on vnf “v6890-vnf” failed. Reason:XXX. |
Explanation |
Failed to call the VNFM interface to delete the bridge on a VM. |
Recommended action |
Verify that the VNFM system is operating properly, and troubleshoot the issue according to the diagnostics log. |
Failed to delete simulation device configuration
Keyword |
DELETE_SIMUATION_CONFIG_FAILED |
Message text |
Delete simulation device config failed. Reason:$1. |
Variable fields |
$1: Possible failure causes. |
Severity level |
Error |
Example |
Delete simulation device config failed. Reason:XXX. |
Explanation |
The simulation network microservice failed to call the simulation sandbox microservice to delete the simulation device configuration. |
Recommended action |
Troubleshoot the issue according to the diagnostics log. |
Failed to create a VM
Keyword |
CREATE_VNF_FAILED |
Message text |
Create vnf “$1” in VNFM failed. Reason:$2. |
Variable fields |
$1: VM name. $2: Possible failure causes. |
Severity level |
Error |
Example |
Create vnf “v6890-vnf” in VNFM failed. Reason:XXX. |
Explanation |
Failed to create a VM. |
Recommended action |
Verify that the VNFM system is operating properly and the VM exists. |
Failed to create a VM template
Keyword |
CREATE_VNF_TEMPLATE_FAILED |
Message text |
Create vnf template “$1” in VNFM failed. Reason:$2. |
Variable fields |
$1: VM template name. $2: Possible failure causes. |
Severity level |
Error |
Example |
Create vnf template “v6850-template” in VNFM failed. Reason:XXX. |
Explanation |
Failed to call the VNFM interface to create a VM template. |
Recommended action |
Verify that the VNFM system is operating properly and the VM template exists. |
Data synchronized failed
Keyword |
SYNC_DATA_FAILED |
Message text |
Data synchronized failed. Reason:$1 |
Variable fields |
$1: Possible failure causes. |
Severity level |
Error |
Example |
Data synchronized failed. Reason: All master nodes in the cluster are inactive.. |
Explanation |
Failed to call the data synchronization interface of the simulation microservice. |
Recommended action |
Verify that the simulation microservice is operating properly. |
Failed to obtain device configuration
Keyword |
GET_CONFIG_FAILED |
Message text |
Get device “$1” config failed. Reason:$2. |
Variable fields |
$1: Device name. $2: Possible failure causes. |
Severity level |
Error |
Example |
Get device “dev1” config failed. Reason:XXX. |
Explanation |
Failed to obtain device configuration. |
Recommended action |
Verify that the connection between the device and controller is normal. |
Failed to obtain a host
Keyword |
GET_HOST_FAILED |
Message text |
Get host for vnf “$1” failed. Reason:$2. |
Variable fields |
$1: VM name. $2: Possible failure causes. |
Severity level |
Error |
Example |
Get host for vnf “vnf1” failed. Reason:XXX. |
Explanation |
Failed to obtain a host. |
Recommended action |
Verify that VNFM is operating properly and verify that compatible hosts exist. |
Failed to create a bridge
Keyword |
CREATE_BRIDGE_FAILED |
Message text |
Create bridge on vnf “$1” failed. Reason:$2. |
Variable fields |
$1: VM name. $2: Possible failure causes. |
Severity level |
Error |
Example |
Create bridge on vnf “v6890-vnf” failed. Reason:XXX. |
Explanation |
Failed to call the VNFM interface to create the bridge on a VM. |
Recommended action |
Verify that VNFM is operating properly. |
Failed to obtain an image
Keyword |
GET_IMAGE_FAILED |
Message text |
Get image for vnf “$1” failed. Reason:$2. |
Variable fields |
$1: VM name. $2: Possible failure causes. |
Severity level |
Error |
Example |
Get image for vnf “vnf1” failed. Reason:XXX. |
Explanation |
Failed to obtain a simulation device image. |
Recommended action |
Verify that VNFM is operating properly and the image for the specified device model exists on VNFM. |
Failed to obtain topology information
Keyword |
GET_TOPO_FAILED |
Message text |
Get topology information failed. Reason:$1. |
Variable fields |
$1: Possible failure causes. |
Severity level |
Error |
Example |
Get topology information failed. Reason:XXX. |
Explanation |
Failed to call the topology obtaining interface of the DC production microservice. |
Recommended action |
Verify that the DC production microservice is operating properly. |
Failed to save the simulation device configuration
Keyword |
SAVE_SIMUATION_CONFIG_FAILED |
Message text |
Save simulation device config failed. Reason:$1. |
Variable fields |
$1: Possible failure causes. |
Severity level |
Error |
Example |
Save simulation device config failed. Reason:XXX. |
Explanation |
Failed to obtain the simulation device configuration saving interface of the simulation microservice. |
Recommended action |
Verify that the simulation microservice is operating properly. |
Failed to record user operations
Keyword |
RECORD_OPERATION_FAILED |
Message text |
Record user operation failed. Reason:$1. |
Variable fields |
$1: Possible failure causes. |
Severity level |
Error |
Example |
Record user operation failed. Reason:XXX. |
Explanation |
Failed to call the user operation recording interface of the DC simulation microservice. |
Recommended action |
Verify that the DC simulation microservice is operating properly. |
Failed to update the VLAN-VXLAN interface mapping
Keyword |
UPDATE_VLAN_VXLAN_INTERFACE_MAPPING_FAILED |
Message text |
Update VLAN-VXLAN interface mapping failed. Reason:$1. |
Variable fields |
$1: Possible failure causes. |
Severity level |
Error |
Example |
Update VLAN-VXLAN interface mapping failed. Reason:XXX. |
Explanation |
Failed to obtain the VLAN-VXLAN interface mapping updating interface of the simulation sandbox microservice. |
Recommended action |
Verify that all created VMs are activated and troubleshoot the issue according to the system log. |
Network data analysis failed
Keyword |
NETWOEK_DATA_ANALYSIS_FAILED |
Message text |
Network data analysis failed. Reason:$1. |
Variable fields |
$1: Possible failure causes. |
Severity level |
Error |
Example |
Network data analysis failed. Reason:XXX. |
Explanation |
Failed to call the network data analysis interface of the DC simulation microservice . |
Recommended action |
Verify that the DC simulation microservice is operating properly. |
Failed to create a network model
Keyword |
CREATE_NETWORK_MODEL_FAILED |
Message text |
Create network model failed. Reason: $1. |
Variable fields |
$1: Possible failure causes. |
Severity level |
Error |
Example |
Create network model failed. Reason: XXX. |
Explanation |
Failed to create a network model |
Recommended action |
Troubleshoot the issue according to the failure cause. |
Failed to update a network model
Keyword |
UPDATE_NETWORK_MODEL_FAILED |
Message text |
Update network model failed. Reason: $1. |
Variable fields |
$1: Possible failure causes |
Severity level |
Error |
Example |
Update network model failed. Reason: XXX. |
Explanation |
Failed to update a network model |
Recommended action |
Troubleshoot the issue according to the failure cause. |
Failed to delete a network model
Keyword |
DELETE_NETWORK_MODEL_FAILED |
Message text |
Delete network model failed. Reason: $1. |
Variable fields |
$1: Possible failure causes |
Severity level |
Error |
Example |
Delete network model failed. Reason: XXX. |
Explanation |
Failed to delete a network model |
Recommended action |
Troubleshoot the issue according to the failure cause. |
TELEMETRY
This section contains telemetry messages.
Configuration deployment failure
Keyword |
SP_NETCONF_FAILED |
Message text |
Seerengine management IP: $1 Reason: $2 NETCONF content: $3 |
Variable fields |
$1: Management IP address of the network device. $2: Failure reason. $3: Configuration that the controller failed to deploy to the network device. |
Severity level |
Warning |
Example |
Seerengine management IP: 17.100.100.3 Reason: The configuration not supported on the specified target NETCONF content: <SAMPLE> <SAMPLER> <Sampler> <SamplerEntry> <SamplerName>ifa_TCQ7JUPWZAOQ3UIPAZK4AOCPME</SamplerName> <Mode>2</Mode> <PacketInterval>10</PacketInterval> </SamplerEntry> </Sampler> </SAMPLER> |
Explanation |
The controller failed to deploy configuration to a network device. |
Recommended action |
Read the failure reason and take actions accordingly. |
Telemetry stream configuration deployment failure
Keyword |
SP_DEVICE_NOT_SUPPORT_TELEMETRY_STREAM |
Message text |
Management IP: $1 Reason: $2 |
Variable fields |
$1: Management IP address of the network device. $2: Failure reason. |
Severity level |
Error |
Example |
Management IP: 17.100.100.3 Reason: The device does not support telemetry stream. |
Explanation |
The controller failed to deploy telemetry stream configuration to a network device because the device does not support telemetry stream.. |
Recommended action |
Read the failure reason and take actions accordingly. |
Tenant
This section contains tenant messages.
Start of tenant configuration recovery on non-active leader controllers
Keyword |
BEGIN_RECOVER_TENANT_CONFIG |
Message text |
All non-active leader controllers started recovering the tenant configuration. |
Variable fields |
N/A |
Severity level |
Info |
Example |
All non-active leader controllers started recovering the tenant configuration. |
Explanation |
Except the active leader, all controllers in the team started recovering the tenant configuration. |
Recommended action |
As a best practice, do not perform any operations on the controllers during the configuration recovery process. |
End of tenant configuration recovery on non-active leader controllers
Keyword |
FINISH_RECOVER_TENANT_CONFIG |
Message text |
All non-active leader controllers completed recovering the tenant configuration. |
Variable fields |
N/A |
Severity level |
Info |
Example |
All non-active leader controllers completed recovering the tenant configuration. |
Explanation |
Except the active leader, all controllers in the team completed recovering the tenant configuration. |
Recommended action |
No action is required. |
Task rejected by thread pool of tenant
Keyword |
TENANT_THREAD_POOL_REJECT_TASK |
Message text |
Thread pool $1 rejected task, current thread size $2, max thread size $3, current queue size $4, max queue size $5. |
Variable fields |
$1: Name of the thread pool. $2: Current number of threads. $3: Maximum number of threads allowed. $4: Current number of queues. $5: Maximum number of queues allowed. |
Severity level |
Error |
Example |
Thread pool TenantBusMsgProcessor rejected task, current thread size 1, max thread size 1, current queue size 1047586, max queue size 1047586. |
Explanation |
The task cannot be executed because the maximum thread pool size of the tenant module was reached. |
Recommended action |
Contact the technical support. |
VMM
This section contains VMM messages.
Failed to connect to vCenter
Keyword |
CONNECT_VCENTER_FAILED |
Message text |
Failed to connect to vCenter $1. Reason: $2. |
Variable fields |
$1: vCenter name. $2: Failure cause. |
Severity level |
Warning |
Example |
Failed to connect to vCenter vCenter1. Reason: Connection timed out. |
Explanation |
The controller failed to connect to a vCenter. |
Recommended action |
· Verify that the controller and the vCenter can reach each other. · Verify that the username, password, and port number of the vCenter are correct. · Verify that the certificate settings are correct. |
Connected to vCenter successfully
Keyword |
CONNECT_VCENTER_SUCCESS |
Message text |
Connected to vCenter $1 successfully. |
Variable fields |
$1: vCenter name. |
Severity level |
Info |
Example |
Connected to vCenter vCenter1 successfully. |
Explanation |
The controller connected to a vCenter successfully. |
Recommended action |
No action is required. |
Failed to disconnect from vCenter
Keyword |
DISCONNECT_VCENTER_FAILED |
Message text |
Failed to disconnect from vCenter $1. Reason: $2. |
Variable fields |
$1: vCenter name. $2: Failure cause. |
Severity level |
Warning |
Example |
Failed to disconnect from vCenter vCenter1. Reason: Connection timed out. |
Explanation |
The controller failed to disconnect from a vCenter. |
Recommended action |
Verify that the controller and the vCenter can reach each other. |
Disconnected from vCenter successfully
Keyword |
DISCONNECT_VCENTER_SUCCESS |
Message text |
Disconnected from vCenter $1 successfully. |
Variable fields |
$1: vCenter name. |
Severity level |
Info |
Example |
Disconnected from vCenter vCenter1 successfully. |
Explanation |
The controller disconnected from a vCenter successfully. |
Recommended action |
No action is required. |
Failed to create VDS
Keyword |
ADDED_VCENTER_VDS_OP_FAILED |
Message text |
Failed to create the VDS in vCenter $1. Reason: $2. |
Variable fields |
$1: vCenter name. $2: Failure cause. |
Severity level |
Warning |
Example |
· Failed to create the VDS in vCenter vCenter1. Reason: A specified parameter was not correct: spec.name. · Failed to create the VDS in vCenter vCenter1. Reason: The data center does not exist. · Failed to create the VDS in vCenter vCenter1. Reason: vCenter connection error. · Failed to create the VDS in vCenter vCenter1. Reason: Waiting timer expired. |
Explanation |
Failed to create a VDS in a vCenter. |
Recommended action |
· Verify that the controller and the vCenter can reach each other. · Verify that the VDS does not exist in the vCenter. · Verify that the database exists. |
Created VDS successfully
Keyword |
ADDED_VCENTER_VDS_OP_SUCCESS |
Message text |
Created the VDS in vCenter $1 successfully. |
Variable fields |
$1: vCenter name. |
Severity level |
Info |
Example |
Created the VDS in vCenter vCenter1 successfully. |
Explanation |
Created a VDS in a vCenter successfully. |
Recommended action |
No action is required. |
Failed to delete VDS
Keyword |
DELETE_VCENTER_VDS_OP_FAILED |
Message text |
Failed to delete the VDS from vCenter $1. Reason: $2. |
Variable fields |
$1: vCenter name. $2: Failure cause. |
Severity level |
Warning |
Example |
· Failed to delete the VDS from vCenter vCenter1. Reason: The resource '14' is in use. · Failed to delete the VDS from vCenter vCenter1. Reason: Waiting timer expired. · Failed to delete the VDS from vCenter vCenter1. Reason: Failed to get the VDS. |
Explanation |
Failed to delete a VDS from a vCenter. |
Recommended action |
· Verify that the controller and the vCenter can reach each other. · Verify that no resources of the VDS are being used in the vCenter. |
Deleted VDS successfully
Keyword |
DELETE_VCENTER_VDS_OP_SUCCESS |
Message text |
Deleted the VDS from vCenter $1 successfully. |
Variable fields |
$1: vCenter name. |
Severity level |
Info |
Example |
Deleted the VDS from vCenter vCenter1 successfully. |
Explanation |
Deleted a VDS from a vCenter successfully. |
Recommended action |
No action is required. |
Failed to update distributed port group QoS
Keyword |
UPDATE_VDS_PORT_GROUP_OP_FAILED |
Message text |
Failed to update QoS policy $1 of distributed port group $2 in vCenter $3. Reason: $4. |
Variable fields |
$1: QoS name. $2: Name of the distributed port group. $3: vCenter name. $4: Failure cause. |
Severity level |
Warning |
Example |
· Failed to update QoS policy qos1 of distributed port group pg1 in vCenter vCenter1. Reason: The distributed port group does not exist. · Failed to update QoS policy qos1 of distributed port group pg1 in vCenter vCenter1. Reason: vCenter connection error. · Failed to update QoS policy qos1 of distributed port group pg1 in vCenter vCenter1. Reason: Waiting timer expired. |
Explanation |
Failed to update the QoS policy for a distributed port group. |
Recommended action |
· Verify that the controller and the vCenter can reach each other. · Verify that the distributed port group exists in the vCenter. |
Updated distributed port group QoS successfully
Keyword |
UPDATE_VDS_PORT_GROUP_OP_SUCCESS |
Message text |
Updated QoS policy $1 of distributed port group $2 in vCenter $3 successfully. |
Variable fields |
$1: QoS name. $2: Name of the distributed port group. $3: vCenter name. |
Severity level |
Info |
Example |
Updated QoS policy qos1 of distributed port group pg1 in vCenter vCenter1 successfully. |
Explanation |
Updated the QoS policy for a distributed port group successfully. |
Recommended action |
No action is required. |
Failed to create distributed port group
Keyword |
CREATE_VDS_PORT_GROUP_OP_FAILED |
Message text |
Failed to create distributed port group $1 in vCenter $2. Reason: $3. |
Variable fields |
$1: Name of the distributed port group. $2: vCenter name. $3: Failure cause. |
Severity level |
Warning |
Example |
· Failed to create distributed port group pg1 in vCenter vCenter1. Reason: The name 'pg2' already exists. · Failed to create distributed port group pg1 in vCenter vCenter1. Reason: vCenter connection error. · Failed to create distributed port group pg1 in vCenter vCenter1. Reason: Waiting timer expired. |
Explanation |
Failed to create a distributed port group in a vCenter. |
Recommended action |
· Verify that the controller and the vCenter can reach each other. · Verify that the distributed port group does not exist in the vCenter. |
Created distributed port group successfully
Keyword |
CREATE_VDS_PORT_GROUP_OP_SUCCESS |
Message text |
Created distributed port group $1 in vCenter $2 successfully. |
Variable fields |
$1: Name of the distributed port group. $2: vCenter name. |
Severity level |
Info |
Example |
Created distributed port group pg1 in vCenter vCenter1 successfully. |
Explanation |
Created a distributed port group in a vCenter successfully. |
Recommended action |
No action is required. |
Failed to update distributed port group
Keyword |
UPDATE_VDS_PORT_GROUP_OP_FAILED |
Message text |
Failed to update distributed port group $1 in vCenter $2. Reason: $3. |
Variable fields |
$1: Name of the distributed port group. $2: vCenter name. $3: Failure cause. |
Severity level |
Warning |
Example |
· Failed to update distributed port group pg1 in vCenter vCenter1. Reason: The VDS distributed port group does not exist. · Failed to update distributed port group pg1 in vCenter vCenter1. Reason: vCenter connection error. · Failed to update distributed port group pg1 in vCenter vCenter1. Reason: Waiting timer expired. |
Explanation |
Failed to update a distributed port group in a vCenter. |
Recommended action |
· Verify that the controller and the vCenter can reach each other. · Verify that the distributed port group exists in the vCenter. |
Updated distributed port group successfully
Keyword |
UPDATE_VDS_PORT_GROUP_OP_SUCCESS |
Message text |
Updated distributed port group $1 in vCenter $2 successfully. |
Variable fields |
$1: Name of the distributed port group. $2: vCenter name. |
Severity level |
Info |
Example |
Updated distributed port group pg1 in vCenter vCenter1 successfully. |
Explanation |
Updated a distributed port group in a vCenter successfully. |
Recommended action |
No action is required. |
Failed to delete distributed port group
Keyword |
DELETE_VDS_PORT_GROU_OP_FAILED |
Message text |
Failed to delete distributed port group $1 from vCenter $2. Reason: $3. |
Variable fields |
$1: Name of the distributed port group. $2: vCenter name. $3: Failure cause. |
Severity level |
Warning |
Example |
· Failed to delete distributed port group pg1 from vCenter vCenter1. Reason: The resource '20' is in use. · Failed to delete distributed port group pg1 from vCenter vCenter1. Reason: vCenter connection error. · Failed to delete distributed port group pg1 from vCenter vCenter1. Reason: Waiting timer expired. |
Explanation |
Failed to delete a distributed port group from a vCenter. |
Recommended action |
· Verify that the controller and the vCenter can reach each other. · Verify that the port IDs in the distributed port group are not being used. |
Deleted distributed port group successfully
Keyword |
DELETE_VDS_PORT_GROU_OP_SUCCESS |
Message text |
Deleted distributed port group $1 from vCenter $2 successfully. |
Variable fields |
$1: Name of the distributed port group. $2: vCenter name. |
Severity level |
Info |
Example |
Deleted distributed port group pg1 from vCenter vCenter1 successfully. |
Explanation |
Deleted a distributed port group from a vCenter successfully. |
Recommended action |
No action is required. |
Added vPort to VSM successfully
Keyword |
ADD_VPORT_SUCCESS |
Message text |
Added vPort $1 to VSM. |
Variable fields |
$1: UUID of the vPort. |
Severity level |
Info |
Example |
Added vPort 4a8370bf-ca60-4bfb-918c-3ecb3a9aa522 to VSM. |
Explanation |
The controller added a vPort on VSM based on the vCenter events successfully. |
Recommended action |
No action is required. |
Failed to add vPort to VSM
Keyword |
ADD_VPORT_FAILED |
Message text |
Failed to add vPort $1 to VSM. Reason: $2. |
Variable fields |
$1: UUID of the vPort. $2: Failure cause. |
Severity level |
Warning |
Example |
· Failed to add vPort 4a8370bf-ca60-4bfb-918c-3ecb3a9aa522 to VSM. Reason: The vPort already exists. · Failed to add vPort 4a8370bf-ca60-4bfb-918c-3ecb3a9aa522 to VSM. Reason: The VSM service does not exist. |
Explanation |
The controller failed to add a vPort on VSM based on the vCenter events. |
Recommended action |
· Verify that VSM services have been enabled. · Verify that the vPort does not exist on VSM. · View VSM log information to verify that the vPort does not have parameter conflict or network mismatching errors. |
Deleted vPort from VSM successfully
Keyword |
DELETE_VPORT_SUCCESS |
Message text |
Deleted vPort $1 from VSM successfully. |
Variable fields |
$1: UUID of the vPort. |
Severity level |
Info |
Example |
Deleted vPort 4a8370bf-ca60-4bfb-918c-3ecb3a9aa522 from VSM successfully. |
Explanation |
The controller deleted a vPort from VSM based on the vCenter events successfully. |
Recommended action |
No action is required. |
Failed to delete vPort from VSM
Keyword |
DELETE_VPORT_FAILED |
Message text |
Failed to delete vPort $1 from VSM. Reason: $2. |
Variable fields |
$1: UUID of the vPort. $2: Failure cause. |
Severity level |
Warning |
Example |
· Failed to delete vPort 4a8370bf-ca60-4bfb-918c-3ecb3a9aa522 from VSM. Reason: The vPort does not exist. · Failed to delete vPort 4a8370bf-ca60-4bfb-918c-3ecb3a9aa522 from VSM. Reason: The VSM service does not exist. |
Explanation |
The controller failed to delete a vPort from VSM based on the vCenter events. |
Recommended action |
· Verify that VSM services have been enabled. · Verify that the vPort does not exist on VSM. |
Updated vPort on VSM successfully
Keyword |
UPDATE_VPORT_SUCCESS |
Message text |
Updated vPort $1 on VSM. |
Variable fields |
$1: UUID of the vPort. |
Severity level |
Info |
Example |
Updated vPort 4a8370bf-ca60-4bfb-918c-3ecb3a9aa522 on VSM. |
Explanation |
The controller updated a vPort on VSM based on the vCenter events successfully. |
Recommended action |
No action is required. |
Failed to update vPort on VSM
Keyword |
UPDATE_VPORT_FAILED |
Message text |
Failed to update vPort $1 on VSM. Reason: $2. |
Variable fields |
$1: UUID of the vPort. $2: Failure cause. |
Severity level |
Warning |
Example |
· Failed to update vPort 4a8370bf-ca60-4bfb-918c-3ecb3a9aa522 on VSM. Reason: The vPort does not exist. · Failed to update vPort 4a8370bf-ca60-4bfb-918c-3ecb3a9aa522 on VSM. Reason: The VSM service does not exist. |
Explanation |
The controller failed to update a vPort on VSM based on the vCenter events. |
Recommended action |
· Verify that VSM services have been enabled. · Verify that the vPort does not exist on VSM. · View VSM log information to verify that the vPort does not have parameter conflict or network mismatching errors. |
Failed to synchronize vPort information
Keyword |
SMOOTH_VPORT_FAILED |
Message text |
Failed to synchronize information about vPort $1. Reason: $2. |
Variable fields |
$1: UUID of the vPort. $2: Failure cause. |
Severity level |
Error |
Example |
Failed to synchronize information about vPort 4a8370bf-ca60-4bfb-918c-3ecb3a9aa522. Reason: The distributed port group of the vPort does not exist. |
Explanation |
The controller failed to synchronize information about a vPort. |
Recommended action |
Verify that the controller for the port group to which the vPort belongs exists. |
Auto audit and sync completed for all vCenters
Keyword |
AUTO_RECONCILIATE_FINISH |
Message text |
· Auto audit and sync completed for all vCenters: auto audit state:$1, auto sync state:$2, audit schedule:$3, audit interval:$4 minutes. · Auto audit and sync completed for all vCenters: auto audit state:$1, auto sync state:$2, audit schedule:$3, monthly:$5, weekly:$6, daily:$7, hh:mm:ss: $8. |
Variable fields |
$1: Auto audit state. $2: Auto sync state. $3: Audit schedule. $4: Audit interval. $5: Monthly. $6: Weekly. $7: Daily. $8: Time. |
Severity level |
Info |
Example |
· Auto audit and sync completed for all vCenters: auto audit state:true, auto sync state:ON, audit schedule:PERIOD, audit interval:60 minutes. · Auto audit and sync completed for all vCenters: auto audit state:$1, auto sync state:$2, audit schedule:TIMING, monthly:*, weekly:?, daily:1,3, hh:mm:ss:08:09:10. |
Explanation |
Auto audit and sync completed for all vCenters. |
Recommended action |
No action is required. |
Added network overlay host to VSM successfully
Keyword |
ADD_NETOVERLAY_HOST |
Message text |
Added network overlay host $1 to VSM successfully. |
Variable fields |
$1: Name of the network overlay host. |
Severity level |
Info |
Example |
Added network overlay host A1 to VSM successfully. |
Explanation |
Added a network overlay host to VSM successfully |
Recommended action |
No action is required. |
Failed to add network overlay host to VSM
Keyword |
ADD_NETOVERLAY_HOST_FAILED |
Message text |
Failed to add network overlay host $1 to VSM. |
Variable fields |
$1: Name of the network overlay host. |
Severity level |
Error |
Example |
Failed to add network overlay host A1 to VSM. |
Explanation |
Failed to add a network overlay host to VSM. |
Recommended action |
· Verify that VSM services have been enabled. · Verify that the network overlay host does not exist on VSM. · View VSM log information to find the failure cause. |
Deleted network overlay host from VSM successfully
Keyword |
DELETE_NETOVERLAY_HOST |
Message text |
Deleted network overlay host $1 from VSM successfully. |
Variable fields |
$1: Name of the network overlay host. |
Severity level |
Info |
Example |
Deleted network overlay host A1 from VSM successfully. |
Explanation |
Deleted a network overlay host from VSM successfully. |
Recommended action |
No action is required. |
Failed to delete network overlay host from VSM
Keyword |
DELETE_NETOVERLAY_HOST_FAILED |
Message text |
Failed to delete network overlay host $1 from VSM. |
Variable fields |
$1: Name of the network overlay host. |
Severity level |
Error |
Example |
Failed to delete network overlay host A1 from VSM. |
Explanation |
Failed to delete a network overlay host from VSM. |
Recommended action |
· Verify that VSM services have been enabled. · Verify that the network overlay host does not exist on VSM. · View VSM log information to find the failure cause. |
Updated network overlay host on VSM successfully
Keyword |
UPDATE_NETOVERLAY_HOST |
Message text |
Updated network overlay host $1 to VSM successfully. |
Variable fields |
$1: Name of the network overlay host. |
Severity level |
Info |
Example |
Updated network overlay host A1 to VSM successfully. |
Explanation |
Updated a network overlay host on VSM successfully. |
Recommended action |
No action is required. |
Failed to update network overlay host on VSM
Keyword |
UPDATE_NETOVERLAY_HOST_FAILED |
Message text |
Failed to update network overlay host $1 to VSM. |
Variable fields |
$1: Name of the network overlay host. |
Severity level |
Error |
Example |
Failed to add network overlay host A1 to VSM. |
Explanation |
Failed to update a network overlay host on VSM. |
Recommended action |
· Verify that VSM services have been enabled. · Verify that the network overlay host does not exist on VSM. · View VSM log information to find the failure cause. |
Failed to allocate VLAN IDs on NEM
Keyword |
ALLOCATE_VLAN_ID_FAILED |
Message text |
Failed to allocate VLAN IDs from VLAN pool with ID $1 on NEM. Reason: The NEM service does not exist. |
Variable fields |
$1: UUID of the VLAN resource pool. |
Severity level |
Warning |
Example |
Failed to allocate VLAN IDs from VLAN pool with ID f80c8af8-9234-4cad-965d-eb5e6364f56c on NEM. Reason: The NEM service does not exist. |
Explanation |
Failed to allocate VLAN IDs on NEM. |
Recommended action |
Verify that the H3C VCFC Network Elements Management application has been enabled. |
Failed to obtain VLAN resource pool name on NEM
Keyword |
GET_VLAN_POOL_NAME_FAILED |
Message text |
Failed to get the VLAN pool name by VLAN pool ID $1 from NEM. Reason: The NEM service does not exist. |
Variable fields |
$1: UUID of the VLAN resource pool. |
Severity level |
Warning |
Example |
Failed to get the VLAN pool name by VLAN pool ID f80c8af8-9234-4cad-965d-eb5e6364f56c from NEM. Reason: The NEM service does not exist. |
Explanation |
Failed to obtain the name of a VLAN resource pool on NEM. |
Recommended action |
Verify that the H3C VCFC Network Elements Management application has been enabled. |
Failed to reclaim VLAN IDs on NEM
Keyword |
DRELEASE_VLAN_ID_FAILED |
Message text |
Failed to release VLAN IDs to VLAN pool $1 from NEM. Reason: The NEM service does not exist. |
Variable fields |
$1: UUID of the VLAN resource pool. |
Severity level |
Warning |
Example |
Failed to release VLAN IDs to VLAN pool f80c8af8-9234-4cad-965d-eb5e6364f56c from NEM. Reason: The NEM service does not exist. |
Explanation |
Failed to reclaim VLAN IDs on NEM. |
Recommended action |
Verify that the H3C VCFC Network Elements Management application has been enabled. |
Failed to synchronize VLAN IDs on NEM
Keyword |
SMOOTH_VLAN_ID_FAILED |
Message text |
Failed to smooth VLAN IDs on NEM. Reason: The NEM service does not exist. |
Variable fields |
N/A |
Severity level |
Warning |
Example |
Failed to smooth VLAN IDs on NEM. Reason: The NEM service does not exist. |
Explanation |
Failed to synchronize VLAN IDs on NEM. |
Recommended action |
Verify that the H3C VCFC Network Elements Management application has been enabled. |
Failed to bind VLAN resource pool on NEM
Keyword |
BIND_VLAN_POOL_FAILED |
Message text |
Failed to bind vCenter $1 with VLAN pool $2 to NEM. Reason: The NEM service does not exist. |
Variable fields |
$1: vCenter UUID $2: UUID of the VLAN resource pool. |
Severity level |
Warning |
Example |
Failed to bind vCenter f80c8af8-9234-4cad-965d-eb5e6364f56c with VLAN pool f80c8af8-9234-4cad-965d-eb5e6364f564 to NEM. Reason: The NEM service does not exist. |
Explanation |
Failed to bind a VLAN resource pool to a vCenter on NEM. |
Recommended action |
Verify that the H3C VCFC Network Elements Management application has been enabled. |
Failed to unbind VLAN resource pool on NEM
Keyword |
UNBIND_VLAN_POOL_FAILED |
Message text |
Failed to unbind vCenter $1 with VLAN pool $2 from NEM. Reason: The NEM service does not exist. |
Variable fields |
$1: vCenter UUID $2: UUID of the VLAN resource pool. |
Severity level |
Warning |
Example |
Failed to unbind vCenter f80c8af8-9234-4cad-965d-eb5e6364f56c with VLAN pool f80c8af8-9234-4cad-965d-eb5e6364f564 from NEM. Reason: The NEM service does not exist. |
Explanation |
Failed to unbind a VLAN resource pool from a vCenter on NEM. |
Recommended action |
Verify that the H3C VCFC Network Elements Management application has been enabled. |
Failed to obtain VLAN ID assignment information on NEM
Keyword |
CHECK_VLAN_ID_ALLOCATE_FAILED |
Message text |
Failed to check VLAN IDs allocated from VLAN pool with ID $1 on NEM. Reason: The NEM service does not exist. |
Variable fields |
$1: UUID of the VLAN resource pool. |
Severity level |
Warning |
Example |
Failed to check VLAN IDs allocated from VLAN pool with ID f80c8af8-9234-4cad-965d-eb5e6364f56c on NEM. Reason: The NEM service does not exist. |
Explanation |
Failed to obtain VLAN ID assignment information on NEM. |
Recommended action |
Verify that the H3C VCFC Network Elements Management application has been enabled. |
Failed to connect to RHVM
Keyword |
CONNECT_RHVM_FAILED |
Message text |
Failed to connect to RHVM $1. Reason: $2. |
Variable fields |
$1: RHVM name. $2: Failure cause. |
Severity level |
Warning |
Example |
Failed to connect to RHVM RHVM1. Reason: Connection timed out. |
Explanation |
The controller failed to connect to a RHVM. |
Recommended action |
· Verify that the controller and RHVM can reach each other. · Verify that the username, password, and port number of the RHVM are correct. |
Connected to RHVM successfully
Keyword |
CONNECT_RHVM_SUCCESS |
Message text |
Connected to RHVM $1 successfully. |
Variable fields |
$1: RHVM name. |
Severity level |
Info |
Example |
Connected to RHVM RHVM1 successfully. |
Explanation |
The controller connected to a RHVM successfully. |
Recommended action |
No action is required. |
Failed to disconnect from RHVM
Keyword |
DISCONNECT_RHVM_FAILED |
Message text |
Failed to disconnect from RHVM $1. Reason: $2. |
Variable fields |
$1: RHVM name. $2: Failure cause. |
Severity level |
Warning |
Example |
Failed to disconnect from RHVM RHVM1. Reason: Connection timed out. |
Explanation |
The controller failed to disconnect from a RHVM. |
Recommended action |
Verify that the controller and RHVM can reach each other. |
Disconnected from RHVM successfully
Keyword |
DISCONNECT_RHVM_SUCCESS |
Message text |
Disconnected from RHVM $1 successfully. |
Variable fields |
$1: RHVM name. |
Severity level |
Info |
Example |
Disconnected from RHVM RHVM1 successfully. |
Explanation |
The controller disconnected from a RHVM successfully. |
Recommended action |
No action is required. |
Failed to create logical network
Keyword |
CREATE_LOGICAL_NETWORK_OP_FAILED |
Message text |
Failed to create logical network $1 in RHVM $2. Reason: $3. |
Variable fields |
$1: Name of the logical network. $2: RHVM name. $3: Failure cause. |
Severity level |
Warning |
Example |
· Failed to create logical network net1 in RHVM RHVM1. Reason: A logical network already exits with the name 'net1'. · Failed to create logical network net1 in RHVM RHVM1. Reason: RHVM connection error. · Failed to create logical network net1 in RHVM RHVM1. Reason: Waiting timer expired. |
Explanation |
Failed to create a logical network on a RHVM. |
Recommended action |
· Verify that the controller and RHVM can reach each other. · Verify that the logical network does not exist on the RHVM. |
Created logical network successfully
Keyword |
CREATE_LOGICAL_NETWORK_OP |
Message text |
Created logical network $1 in RHVM $2 successfully. |
Variable fields |
$1: Name of the logical network. $2: RHVM name. |
Severity level |
Info |
Example |
Created logical network net1 in RHVM RHVM1 successfully. |
Explanation |
Created a logical network on a RHVM successfully. |
Recommended action |
No action is required. |
Failed to update logical network
Keyword |
UPDATE_LOGICAL_NETWORK_OP_FAILED |
Message text |
Failed to update logical network $1 in RHVM $2. Reason: $3. |
Variable fields |
$1: Name of the logical network. $2: RHVM name. $3: Failure cause. |
Severity level |
Warning |
Example |
· Failed to update logical network net1 in RHVM RHVM1. Reason: The logical network does not exist. · Failed to update logical network net1 in RHVM RHVM1. Reason: RHVM connection error. · Failed to update logical network net1 in RHVM RHVM1. Reason: Waiting timer expired. |
Explanation |
Failed to update a logical network on a RHVM. |
Recommended action |
· Verify that the controller and RHVM can reach each other. · Verify that the logical network exists on the RHVM. |
Updated logical network successfully
Keyword |
UPDATE_LOGICAL_NETWORK_OP |
Message text |
Updated logical network $1 in RHVM $2 successfully. |
Variable fields |
$1: Name of the logical network. $2: RHVM name. |
Severity level |
Info |
Example |
Updated logical network net1 in RHVM RHVM1 successfully. |
Explanation |
Updated a logical network on a RHVM successfully. |
Recommended action |
No action is required. |
Failed to delete logical network
Keyword |
DELETE_LOGICAL_NETWORK_OP_FAILED |
Message text |
Failed to delete logical network $1 from RHVM $2. Reason: $3. |
Variable fields |
$1: Name of the logical network. $2: RHVM name. $3: Failure cause. |
Severity level |
Warning |
Example |
· Failed to delete logical network net1 from RHVM RHVM1. Reason: The resource '20' is in use. · Failed to delete logical network net1 from RHVM RHVM1. Reason: RHVM connection error. · Failed to delete logical network pg1 from RHVM RHVM1. Reason: Waiting timer expired. |
Explanation |
Failed to delete a logical network from a RHVM. |
Recommended action |
· Verify that the controller and RHVM can reach each other. · Verify that the port IDs in the logical network are not being used. |
Deleted logical network successfully
Keyword |
DELETE_LOGICAL_NETWORK_OP |
Message text |
Deleted logical network $1 from RHVM $2 successfully. |
Variable fields |
$1: Name of the logical network. $2: RHVM name. |
Severity level |
Info |
Example |
Deleted logical network net1 from RHVM RHVM1 successfully. |
Explanation |
Deleted a logical network from a RHVM successfully. |
Recommended action |
No action is required. |
Added vPort to VSM through RHVM successfully
Keyword |
ADD_RHVM_VPORT_SUCCESS |
Message text |
Added vPort $1 to VSM. |
Variable fields |
$1: UUID of the vPort. |
Severity level |
Info |
Example |
Added vPort 4a8370bf-ca60-4bfb-918c-3ecb3a9aa522 to VSM. |
Explanation |
The controller added a vPort on VSM based on RHVM events successfully. |
Recommended action |
No action is required. |
Failed to add vPort to VSM through RHVM
Keyword |
ADD_RHVM_VPORT_FAILED |
Message text |
Failed to add vPort $1 to VSM. Reason: $2. |
Variable fields |
$1: UUID of the vPort. $2: Failure cause. |
Severity level |
Warning |
Example |
· Failed to add vPort 4a8370bf-ca60-4bfb-918c-3ecb3a9aa522 to VSM. Reason: The vPort already exists. · Failed to add vPort 4a8370bf-ca60-4bfb-918c-3ecb3a9aa522 to VSM. Reason: The VSM service does not exist. |
Explanation |
The controller failed to add a vPort on VSM based on RHVM events. |
Recommended action |
· Verify that VSM services have been enabled. · Verify that the vPort does not exist on VSM. · View VSM log information to verify that the vPort does not have parameter conflict or network mismatching errors. |
Deleted vPort from VSM through RHVM successfully
Keyword |
DELETE_RHVM_VPORT_SUCCESS |
Message text |
Deleted vPort $1 from VSM successfully. |
Variable fields |
$1: UUID of the vPort. |
Severity level |
Info |
Example |
Deleted vPort 4a8370bf-ca60-4bfb-918c-3ecb3a9aa522 from VSM successfully. |
Explanation |
The controller deleted a vPort from VSM based on RHVM events successfully. |
Recommended action |
No action is required. |
Failed to delete vPort from VSM through RHVM
Keyword |
DELETE_RHVM_VPORT_FAILED |
Message text |
Failed to delete vPort $1 from VSM. Reason: $2. |
Variable fields |
$1: UUID of the vPort. $2: Failure cause. |
Severity level |
Warning |
Example |
· Failed to delete vPort 4a8370bf-ca60-4bfb-918c-3ecb3a9aa522 from VSM. Reason: The vPort does not exist. · Failed to delete vPort 4a8370bf-ca60-4bfb-918c-3ecb3a9aa522 from VSM. Reason: The VSM service does not exist. |
Explanation |
The controller failed to delete a vPort from VSM based on RHVM events. |
Recommended action |
· Verify that VSM services have been enabled. · Verify that the vPort exists on VSM. |
Updated vPort on VSM through RHVM successfully
Keyword |
UPDATE_RHVM_VPORT_SUCCESS |
Message text |
Updated vPort $1 on VSM. |
Variable fields |
$1: UUID of the vPort. |
Severity level |
Info |
Example |
Updated vPort 4a8370bf-ca60-4bfb-918c-3ecb3a9aa522 on VSM. |
Explanation |
The controller updated a vPort on VSM based on RHVM events successfully. |
Recommended action |
No action is required. |
Failed to update vPort on VSM through RHVM
Keyword |
UPDATE_RHVM_VPORT_FAILED |
Message text |
Failed to update vPort $1 on VSM. Reason: $2. |
Variable fields |
$1: UUID of the vPort. $2: Failure cause. |
Severity level |
Warning |
Example |
· Failed to update vPort 4a8370bf-ca60-4bfb-918c-3ecb3a9aa522 on VSM. Reason: The vPort does not exist. · Failed to update vPort 4a8370bf-ca60-4bfb-918c-3ecb3a9aa522 on VSM. Reason: The VSM service does not exist. |
Explanation |
The controller failed to update a vPort on VSM based on RHVM events. |
Recommended action |
· Verify that VSM services have been enabled. · Verify that the vPort does not exist on VSM. · View VSM log information to verify that the vPort does not have parameter conflict or network mismatching errors. |
Failed to create VDS
Keyword |
REVERSE_ADDED_VCENTER_VDS_OP_FAILED |
Message text |
Failed to create VDS $1 on vCenter $2. Reason: $3. |
Variable fields |
$1: VDS name. $2: vCenter name. $3: Failure cause. |
Severity level |
Warning |
Example |
Failed to create VDS VDS1 on vCenter vCenter1. Reason: The specified VDS already exists. |
Explanation |
Failed to create a VDS in a vCenter. |
Recommended action |
· Verify that the controller and the vCenter can reach each other. · Verify that the VDS does not exist in the vCenter. |
Failed to create distributed port group
Keyword |
REVERSE_CREATE_VDS_PORT_GROUP_OP_FAILED |
Message text |
Failed to create distributed port group $1 on VDS $2. Reason: $3. |
Variable fields |
$1: Name of the distributed port group. $2: VDS name. $3: Failure cause. |
Severity level |
Warning |
Example |
Failed to create distributed port group PG1 on VDS VDS1. Reason: The VDS does not exist. |
Explanation |
Failed to create a distributed port group in a vCenter. |
Recommended action |
· Verify that the controller and the vCenter can reach each other. · Verify that the VDS exists on the vCenter. |
Failed to obtain vCenter data
Keyword |
DATA_DISCOVERY_OP_FAILED |
Message text |
Failed to obtain data from vCenter $1. Reason: $2. |
Variable fields |
$1: vCenter name. $2: Failure cause. |
Severity level |
Warning |
Example |
Failed to obtain data from vCenter vc1. Reason: The vCenter is abnormal. |
Explanation |
Failed to obtain vCenter data. |
Recommended action |
· Verify that the controller and the vCenter can reach each other. · Verify that the vCenter is in normal state. |
Auto audit and sync completed for all OpenStack-based cloud platforms
Keyword |
DATA_RECONCILIATE_FINISH |
Message text |
· Auto audit and sync completed for all OpenStack-based cloud platforms: auto audit state:$1, auto sync state:$2, audit schedule:$3, audit interval:$4 minutes. · Auto audit and sync completed for all OpenStack-based cloud platforms: auto audit state:$1, auto sync state:$2, audit schedule:$3, monthly:$5, weekly:$6, daily:$7, hh:mm:ss: $8. |
Variable fields |
$1: Auto audit state. $2: Auto sync state. $3: Audit schedule. $4: Audit interval. $5: Monthly. $6: Weekly. $7: Daily. $8: Time. |
Severity level |
Info |
Example |
· Auto audit and sync completed for all OpenStack-based cloud platforms: auto audit state:true, auto sync state:true, audit schedule:PERIOD, audit interval:60 minutes. · Auto audit and sync completed for all OpenStack-based cloud platforms: auto audit state:true, auto sync state:true, audit schedule:TIMING, monthly:*, weekly:?, daily: 1,3, hh:mm:ss: 08:09:10. |
Explanation |
Auto audit and sync completed for all OpenStack-based cloud platforms. |
Recommended action |
No action is required. |
Connected to OpenStack successfully
Keyword |
CONNECT_OPENSTACK_SUCCESS |
Message text |
Connected to OpenStack-based cloud platform $1 successfully. |
Variable fields |
$1: OpenStack name. |
Severity level |
Info |
Example |
Connected to OpenStack-based cloud platform OpenStack1 successfully |
Explanation |
The controller connected to OpenStack successfully. |
Recommended action |
No action is required. |
Failed to connect to OpenStack
Keyword |
CONNECT_OPENSTACK_FAILED |
Message text |
Failed to connect to OpenStack-based cloud platform $1. Reason: $2. |
Variable fields |
$1: OpenStack name. $2: Failure cause. |
Severity level |
Warning |
Example |
Failed to connect to OpenStack-based cloud platform OpenStack1. Reason: Connection timed out. |
Explanation |
The controller failed to connect to OpenStack. |
Recommended action |
· Verify that the controller and OpenStack can reach each other. · Verify that the username, password, and port number of OpenStack are correct. |
Created DHCP vPort successfully
Keyword |
ADD_DHCP_VPORT_SUCCESS |
Message text |
Added DHCP vPort $1 to the OpenStack-based cloud platform successfully. |
Variable fields |
$1: UUID of the DHCP vPort. |
Severity level |
Info |
Example |
Added DHCP vPort 4a8370bf-ca60-4bfb-918c-3ecb3a9aa522 to the OpenStack-based cloud platform successfully. |
Explanation |
Created a DHCP vPort on OpenStack successfully |
Recommended action |
No action is required. |
Failed to create DHCP vPort
Keyword |
ADD_DHCP_VPORT_FAILED |
Message text |
Failed to add DHCP vPort $1 to the OpenStack-based cloud platform. Reason: $2. |
Variable fields |
$1: UUID of the DHCP vPort. $2: Failure cause. |
Severity level |
Warning |
Example |
· Failed to add DHCP vPort 4a8370bf-ca60-4bfb-918c-3ecb3a9aa522 to the OpenStack-based cloud platform. Reason: OpenStack-based cloud platform connection error. · Failed to add DHCP vPort 4a8370bf-ca60-4bfb-918c-3ecb3a9aa522 to the OpenStack-based cloud platform. Reason: Invalid port parameter. |
Explanation |
Failed to create a DHCP vPort on OpenStack. |
Recommended action |
Verify that the controller and OpenStack can reach each other. |
Deleted DHCP vPort successfully
Keyword |
DELETE_DHCP_VPORT_SUCCESS |
Message text |
Deleted DHCP vPort $1 from the OpenStack-based cloud platform successfully. |
Variable fields |
$1: UUID of the DHCP vPort. |
Severity level |
Info |
Example |
Deleted DHCP vPort 4a8370bf-ca60-4bfb-918c-3ecb3a9aa522 from the OpenStack-based cloud platform successfully. |
Explanation |
Deleted a DHCP vPort successfully. |
Recommended action |
No action is required. |
Connected to OpenStack controller node successfully
Keyword |
CONNECT_OPENSTACK_CONTROLLER_NODE_SUCCESS |
Message text |
Connected to the controller node $1 of OpenStack-based cloud platform $2 successfully. |
Variable fields |
$1: IP address of the controller node. $2: OpenStack name. |
Severity level |
Info |
Example |
Connected to the controller node 192.168.1.2 of OpenStack-based cloud platform OP successfully. |
Explanation |
The controller connected to the OpenStack controller node successfully. |
Recommended action |
No action is required. |
Disconnected from OpenStack controller node
Keyword |
DISCONNECT_OPENSTACK_CONTROLLER_NODE |
Message text |
Disconnected from the controller node $1 of OpenStack-based cloud platform $2. |
Variable fields |
$1: IP address of the controller node. $2: OpenStack name. |
Severity level |
Error |
Example |
Disconnected from the controller node 192.168.2.2 of OpenStack-based cloud platform OP. |
Explanation |
The controller disconnected from the OpenStack controller node. |
Recommended action |
· Verify that the controller and the OpenStack controller node can reach each other. · Verify that the WebSocket session is correct. |
RHVM data detection failure
Keyword |
RHVM_DATA_DISCOVERY_FAILED |
Message text |
Failed to obtain data from RHVM $1. Reason: $2. |
Variable fields |
$1: RHVM name. $2: Failure reason. |
Severity level |
Warning |
Example |
Failed to obtain data from RHVM rhvm1. Reason: RHVM connection error. |
Explanation |
Failed to obtain data from an RHVM. |
Recommended action |
· Verify that the controller and the RHVM can reach each other. · Verify that the RHVM is in normal state. |
Logical network creation failure because of data incorporation errors
Keyword |
RHVM_REVERSE_CREATE_LOGICAL_NETWORK_FAILED |
Message text |
Failed to create logical network $1. Reason: $2. |
Variable fields |
$1: Logical network name. $2: Failure reason. |
Severity level |
Warning |
Example |
Failed to create logical network logic1. Reason: The reverse management parameters are abnormal, which is inconsistent with the reverse data. |
Explanation |
Failed to create a logical network because of data incorporation errors. |
Recommended action |
· Verify that the controller and the RHVM can reach each other. · Verify that the logical network data is consistent with the reverse discovered data. |
RHVM data synchronization failure
Keyword |
RHVM_SMOOTH_LOGICAL_NETWORK_FAILED |
Message text |
Failed to repair configuration for logical network $1. Reason:$2. |
Variable fields |
$1: Logical network name. $2: Failure reason. |
Severity level |
Warning |
Example |
Failed to repair configuration for logical network logic1. Reason: RHVM connection error. |
Explanation |
Failed to synchronize data for a logical network. |
Recommended action |
· Verify that the controller and the RHVM can reach each other. · Verify that the RHVM is in normal state. |
RHVM data auditing failure
Keyword |
RHVM_AUDIT_LOGICAL_NETWORK_FAILED |
Message text |
Failed to audit differences for logical network $1. Reason: $2. |
Variable fields |
$1: Logical network name. $2: Failure reason. |
Severity level |
Warning |
Example |
Failed to audit differences for logical network logic1. Reason: RHVM connection error. |
Explanation |
Failed to audit the logical network data. |
Recommended action |
· Verify that the controller and the RHVM can reach each other. · Verify that the RHVM is in normal state. |
Auto audit and sync completed for all RHVMs
Keyword |
AUTO_RECONCILIATE_FINISH |
Message text |
· Auto audit and sync completed for all RHVMs: auto audit state:$1, auto sync state:$2, audit schedule:$3, audit interval:$4 minutes. · Auto audit and sync completed for all RHVMs: auto audit state:$1, auto sync state:$2, audit schedule:$3, monthly:$5, weekly:$6, daily:$7, hh:mm:ss: $8. |
Variable fields |
$1: Auto audit state. $2: Auto sync state. $3: Audit schedule. $4: Audit interval. $5: Monthly. $6: Weekly. $7: Daily. $8: Time. |
Severity level |
Info |
Example |
· Auto audit and sync completed for all RHVMs: auto audit state:true, auto sync state:ON, audit schedule:PERIOD, audit interval:60 minutes. · Auto audit and sync completed for all RHVMs: auto audit state:true, auto sync state:ON, audit schedule:TIMING, monthly:*, monthly:?, daily:1,3, hh:mm:ss: 08:09:10. |
Explanation |
Auto audit and sync completed for all RHVMs. |
Recommended action |
No action is required. |
Failed to start calendar-based audit for vCenters
Keyword |
START_VCENTER_SCHEDULER_FAILED |
Message text |
Failed to start calendar-based audit for vCenters. |
Variable fields |
N/A |
Severity level |
Warning |
Example |
Failed to start calendar-based audit for vCenters. |
Explanation |
Failed to start calendar-based audit for vCenters. |
Recommended action |
Verify that the controller is running correctly. |
Failed to start calendar-based audit for OpenStack-based cloud platforms
Keyword |
START_OPENSTACK_SCHEDULER_FAILED |
Message text |
Failed to start calendar-based audit for OpenStack-based cloud platforms. |
Variable fields |
N/A |
Severity level |
Warning |
Example |
Failed to start calendar-based audit for OpenStack-based cloud platforms. |
Explanation |
Failed to start calendar-based audit for OpenStack-based cloud platforms. |
Recommended action |
Verify that the controller is running correctly. |
Failed to start calendar-based audit for RHVMs
Keyword |
START_RHVM_SCHEDULER_FAILED |
Message text |
Failed to start calendar-based audit for RHVMs. |
Variable fields |
N/A |
Severity level |
Warning |
Example |
Failed to start calendar-based audit for RHVMs. |
Explanation |
Failed to start calendar-based audit for RHVMs. |
Recommended action |
Verify that the controller is running correctly. |
Failed to delete network node
Keyword |
DELETE_NETWORK_NODE_FAILED |
Message text |
Failed to delete network node $1 from VSM. Reason: $2. |
Variable fields |
$1: Name of the network node. $2: Failure reason. |
Severity level |
Warning |
Example |
Failed to delete network node networkNode from VSM. Reason: The specified resource does not exist. |
Explanation |
Failed to delete a network node. |
Recommended action |
Verify that the specified network node exists. |
Failed to add network nodes
Keyword |
ADD_NETWORK_NODE_FAILED |
Message text |
Failed to add network nodes to VSM. Reason: $1 |
Variable fields |
$1: Failure reason. |
Severity level |
Warning |
Example |
Failed to add network nodes to VSM. Reason: The network node is already used. |
Explanation |
Failed to add network nodes to VSM. |
Recommended action |
Check whether the network nodes already exist. |
Failed to push 1020V host information
Keyword |
PUSH_1020V_HOST_FAILED |
Message text |
Failed to push 1020V host to the OpenStack-based cloud platform. Reason: $1. |
Variable fields |
$1: Failure reason. |
Severity level |
Warning |
Example |
Failed to push 1020V host to the OpenStack-based cloud platform. Reason: OpenStack-based cloud platform connection error. |
Explanation |
Failed to push 1020V host information. |
Recommended action |
Verify that the OpenStack connection is running correctly. |
Failed to bind gateway to tenant
Keyword |
CREATE_TENANTBINDGATEWAY_FAILED |
Message text |
Failed to create tenant-bound gateway $1 in NEM. Reason: The NEM service does not exist. |
Variable fields |
$1: UUID of the gateway-tenant binding. |
Severity level |
Warning |
Example |
Failed to create tenant-bound gateway b3848485-eff1-427f-a012-f1fff28c65c8 in NEM. Reason: The NEM service does not exist. |
Explanation |
Failed to bind a gateway to a tenant. |
Recommended action |
Verify that the device resource exists on NEM. |
Failed to unbind gateway from tenant
Keyword |
DELETE_TENANTBINDGATEWAY_FAILED |
Message text |
Failed to delete tenant-bound gateway $1 from NEM. Reason: The NEM service does not exist. |
Variable fields |
$1: UUID of the gateway-tenant binding. |
Severity level |
Warning |
Example |
Failed to delete tenant-bound gateway b3848485-eff1-427f-a012-f1fff28c65c8 from NEM. Reason: The NEM service does not exist. |
Explanation |
Failed to unbind a gateway from a tenant. |
Recommended action |
Verify that the device resource exists on NEM. |
Failed to obtain gateway-tenant binding information
Keyword |
GET_TENANTBINDGATEWAY_FAILED |
Message text |
Failed to get the tenant-bound gateway of tenant $1 from NEM. Reason: The NEM service does not exist. |
Variable fields |
$1: UUID of the tenant. |
Severity level |
Warning |
Example |
Failed to get the tenant-bound gateway of tenant b3848485-eff1-427f-a012-f1fff28c65c8 from NEM. Reason: The NEM service does not exist. |
Explanation |
Failed to obtain gateway-tenant binding information. |
Recommended action |
Verify that the device resource exists on NEM. |
Failed to create vPort profile
Keyword |
CREATE_TAP_FLOW_FAILED |
Message text |
Failed to create vPort profile $1 in TAAS. Reason: The TAAS service is not enabled. |
Variable fields |
$1: UUID of the vPort policy. |
Severity level |
Warning |
Example |
Failed to create vPort profile b3848485-eff1-427f-a012-f1fff28c65c8 in TAAS. Reason: The TAAS service is not enabled. |
Explanation |
Failed to create a vPort profile. |
Recommended action |
Verify that the TAAS service has been enabled. |
Failed to delete vPort profile
Keyword |
DELETE_TAP_FLOW_FAILED |
Message text |
Failed to delete vPort profile $1 from TAAS. Reason: The TAAS service is not enabled. |
Variable fields |
$1: UUID of the vPort policy. |
Severity level |
Warning |
Example |
Failed to delete vPort profile b3848485-eff1-427f-a012-f1fff28c65c8 from TAAS. Reason: The TAAS service is not enabled. |
Explanation |
Failed to delete a vPort profile. |
Recommended action |
Verify that the TAAS service has been enabled. |
Failed to edit vPort profile
Keyword |
UPDATE_TAP_FLOW_FAILED |
Message text |
Failed to update vPort profile $1 in TAAS. Reason: The TAAS service is not enabled. |
Variable fields |
$1: UUID of the vPort policy. |
Severity level |
Warning |
Example |
Failed to update vPort profile b3848485-eff1-427f-a012-f1fff28c65c8 in TAAS. Reason: The TAAS service is not enabled. |
Explanation |
Failed to edit a vPort profile. |
Recommended action |
Verify that the TAAS service has been enabled. |
Failed to create mirroring destination profile
Keyword |
CREATE_TAP_SERVICE_FAILED |
Message text |
Failed to create mirroring destination profile $1 in TAAS. Reason: The TAAS service is not enabled. |
Variable fields |
$1: UUID of the mirroring destination profile. |
Severity level |
Warning |
Example |
Failed to create mirroring destination profile b3848485-eff1-427f-a012-f1fff28c65c8 in TAAS. Reason: The TAAS service is not enabled. |
Explanation |
Failed to create a mirroring destination profile. |
Recommended action |
Verify that the TAAS service has been enabled. |
Failed to delete mirroring destination profile
Keyword |
DELETE_TAP_SERVICE_FAILED |
Message text |
Failed to delete mirroring destination profile $1 from TAAS. Reason: The TAAS service is not enabled. |
Variable fields |
$1: UUID of the mirroring destination profile. |
Severity level |
Warning |
Example |
Failed to delete mirroring destination profile b3848485-eff1-427f-a012-f1fff28c65c8 from TAAS. Reason: The TAAS service is not enabled. |
Explanation |
Failed to delete a mirroring destination profile. |
Recommended action |
Verify that the TAAS service has been enabled. |
Failed to edit mirroring destination profile
Keyword |
UPDATE_TAP_SERVICE_FAILED |
Message text |
Failed to update mirroring destination profile $1 in TAAS. Reason: The TAAS service is not enabled. |
Variable fields |
$1: UUID of the mirroring destination profile. |
Severity level |
Warning |
Example |
Failed to update mirroring destination profile b3848485-eff1-427f-a012-f1fff28c65c8 in TAAS. Reason: The TAAS service is not enabled. |
Explanation |
Failed to edit a mirroring destination profile. |
Recommended action |
Verify that the TAAS service has been enabled. |
Failed to verify whether a tenant has service resources
Keyword |
CHECK_RESOURCE_BY_TENANT_ID_FAILED |
Message text |
Failed to verify the existence of service resources for the specified tenant. Reason: The NEM service does not exist. |
Variable fields |
N/A |
Severity level |
Warning |
Example |
Failed to verify the existence of service resources for the specified tenant. Reason: The NEM service does not exist. |
Explanation |
Failed to verify whether a tenant has service resources. |
Recommended action |
Verify that the NEM service has been enabled. |
Failed to bind gateway to vRouter
Keyword |
ROUTER_BIND_GATEWAY_FAILED |
Message text |
Failed to bind a gateway to a vRouter. Reason: The NEM service does not exist. |
Variable fields |
N/A |
Severity level |
Warning |
Example |
Failed to bind a gateway to a vRouter. Reason: The NEM service does not exist. |
Explanation |
Failed to bind a gateway to a vRouter. |
Recommended action |
Verify that the NEM service has been enabled. |
Failed to unbind gateway from vRouter
Keyword |
ROUTER_UNBIND_GATEWAY_FAILED |
Message text |
Failed to unbind a gateway from a vRouter. Reason: The NEM service does not exist. |
Variable fields |
N/A |
Severity level |
Warning |
Example |
Failed to unbind a gateway from a vRouter. Reason: The NEM service does not exist. |
Explanation |
Failed to unbind a gateway from a vRouter. |
Recommended action |
Verify that the NEM service has been enabled. |
Failed to create BGP neighbor
Keyword |
CREATE_BGP_NEIGHBOR_FAILED |
Message text |
Failed to create BGP neighbor $1 in NEM. Reason: The NEM service is not enabled. |
Variable fields |
$1: UUID of the BGP neighbor. |
Severity level |
Warning |
Example |
Failed to create BGP neighbor b3848485-eff1-427f-a012-f1fff28c65c8 in NEM. Reason: The NEM service is not enabled. |
Explanation |
Failed to create a BGP neighbor. |
Recommended action |
Verify that the NEM service has been enabled. |
Failed to delete BGP neighbor
Keyword |
DELETE_BGP_NEIGHBOR_FAILED |
Message text |
Failed to delete BGP neighbor $1 from NEM. Reason: The NEM service is not enabled. |
Variable fields |
$1: UUID of the BGP neighbor. |
Severity level |
Warning |
Example |
Failed to delete BGP neighbor b3848485-eff1-427f-a012-f1fff28c65c8 from NEM. Reason: The NEM service is not enabled. |
Explanation |
Failed to delete a BGP neighbor. |
Recommended action |
Verify that the NEM service has been enabled. |
Failed to edit BGP neighbor
Keyword |
UPDATE_BGP_NEIGHBOR_FAILED |
Message text |
Failed to update BGP neighbor $1 in NEM. Reason: The NEM service is not enabled. |
Variable fields |
$1: UUID of the BGP neighbor. |
Severity level |
Warning |
Example |
Failed to update BGP neighbor b3848485-eff1-427f-a012-f1fff28c65c8 in NEM. Reason: The NEM service is not enabled. |
Explanation |
Failed to edit a BGP neighbor. |
Recommended action |
Verify that the NEM service has been enabled. |
Failed to verify whether a tenant exists
Keyword |
CHECK_TENANT_FAILED |
Message text |
Failed to check for tenant $1. Reason: The UI service is not enabled. |
Variable fields |
$1: UUID of the tenant. |
Severity level |
Warning |
Example |
Failed to check for tenant b3848485-eff1-427f-a012-f1fff28c65c8. Reason: The UI service is not enabled. |
Explanation |
Failed to verify whether a tenant exists. |
Recommended action |
Verify that the UI service has been enabled. |
Failed to create tenant
Keyword |
CREATE_TENANT_FAILED |
Message text |
Failed to create tenant $1 in UI. Reason: The UI service is not enabled. |
Variable fields |
$1: UUID of the tenant. |
Severity level |
Warning |
Example |
Failed to create tenant b3848485-eff1-427f-a012-f1fff28c65c8 in UI. Reason: The UI service is not enabled. |
Explanation |
Failed to create a tenant. |
Recommended action |
Verify that the UI service has been enabled. |
Failed to edit a tenant
Keyword |
UPDATE_TENANT_FAILED |
Message text |
Failed to update tenant $1 in UI. Reason: The UI service is not enabled. |
Variable fields |
$1: UUID of the tenant. |
Severity level |
Warning |
Example |
Failed to update tenant b3848485-eff1-427f-a012-f1fff28c65c8 in UI. Reason: The UI service is not enabled. |
Explanation |
Failed to edit a tenant. |
Recommended action |
Verify that the UI service has been enabled. |
Failed to delete tenant
Keyword |
DELETE_TENANT_FAILED |
Message text |
Failed to delete tenant $1 from UI. Reason: The UI service is not enabled |
Variable fields |
$1: UUID of the tenant. |
Severity level |
Warning |
Example |
Failed to delete tenant b3848485-eff1-427f-a012-f1fff28c65c8 from UI. Reason: The UI service is not enabled |
Explanation |
Failed to delete a tenant. |
Recommended action |
Verify that the UI service has been enabled. |
Failed to create vRouter
Keyword |
CREATE_ROUTER_FAILED |
Message text |
Failed to create router $1 in VSM. Reason: The VSM service is not enabled. |
Variable fields |
$1: UUID of the vRouter. |
Severity level |
Warning |
Example |
Failed to create router b3848485-eff1-427f-a012-f1fff28c65c8 in VSM. Reason: The VSM service is not enabled. |
Explanation |
Failed to create a vRouter. |
Recommended action |
Verify that the VSM service has been enabled. |
Failed to edit vRouter
Keyword |
UPDATE_ROUTER_FAILED |
Message text |
Failed to update router $1 in VSM. Reason: The VSM service is not enabled. |
Variable fields |
$1: UUID of the vRouter. |
Severity level |
Warning |
Example |
Failed to update router b3848485-eff1-427f-a012-f1fff28c65c8 in VSM. Reason: The VSM service is not enabled. |
Explanation |
Failed to edit a vRouter. |
Recommended action |
Verify that the VSM service has been enabled. |
Failed to delete vRouter
Keyword |
DELETE_ROUTER_FAILED |
Message text |
Failed to delete router $1 from VSM. Reason: The VSM service is not enabled. |
Variable fields |
$1: UUID of the vRouter. |
Severity level |
Warning |
Example |
Failed to delete router b3848485-eff1-427f-a012-f1fff28c65c8 from VSM. Reason: The VSM service is not enabled. |
Explanation |
Failed to delete a vRouter. |
Recommended action |
Verify that the VSM service has been enabled. |
Failed to create routing table
Keyword |
CREATE_ROUTE_TABLE_FAILED |
Message text |
Failed to create route table $1 in VSM. Reason: The VSM service is not enabled. |
Variable fields |
$1: UUID of the routing table. |
Severity level |
Warning |
Example |
Failed to create route table b3848485-eff1-427f-a012-f1fff28c65c8 in VSM. Reason: The VSM service is not enabled. |
Explanation |
Failed to create a routing table. |
Recommended action |
Verify that the VSM service has been enabled. |
Failed to edit routing table.
Keyword |
UPDATE_ROUTE_TABLE_FAILED |
Message text |
Failed to update route table $1 in VSM. Reason: The VSM service is not enabled. |
Variable fields |
$1: UUID of the routing table. |
Severity level |
Warning |
Example |
Failed to update route table b3848485-eff1-427f-a012-f1fff28c65c8 in VSM. Reason: The VSM service is not enabled. |
Explanation |
Failed to edit a routing table. |
Recommended action |
Verify that the VSM service has been enabled. |
Failed to delete routing table.
Keyword |
DELETE_ROUTE_TABLE_FAILED |
Message text |
Failed to delete route table $1 from VSM. Reason: The VSM service is not enabled. |
Variable fields |
$1: UUID of the routing table. |
Severity level |
Warning |
Example |
Failed to delete route table b3848485-eff1-427f-a012-f1fff28c65c8 from VSM. Reason: The VSM service is not enabled. |
Explanation |
Failed to delete a routing table. |
Recommended action |
Verify that the VSM service has been enabled. |
Failed to create vRouter interface
Keyword |
ADD_ROUTER_INTERFACE_FAILED |
Message text |
Failed to create vRouter interface $1 in VSM. Reason: The VSM service is not enabled. |
Variable fields |
$1: UUID of the vRouter interface. |
Severity level |
Warning |
Example |
Failed to create vRouter interface b3848485-eff1-427f-a012-f1fff28c65c8 in VSM. Reason: The VSM service is not enabled. |
Explanation |
Failed to create a vRouter interface. |
Recommended action |
Verify that the VSM service has been enabled. |
Failed to delete vRouter interface
Keyword |
DELETE_ROUTER_INTERFACE_FAILED |
Message text |
Failed to delete vRouter interface $1 from VSM. Reason: The VSM service is not enabled. |
Variable fields |
$1: UUID of the vRouter interface. |
Severity level |
Warning |
Example |
Failed to delete vRouter interface b3848485-eff1-427f-a012-f1fff28c65c8 from VSM. Reason: The VSM service is not enabled. |
Explanation |
Failed to delete a vRouter interface. |
Recommended action |
Verify that the VSM service has been enabled. |
Failed to create floating IP
Keyword |
CREATE_FLOATING_IP_FAILED |
Message text |
Failed to create floating IP $1 in VSM. Reason: The VSM service is not enabled. |
Variable fields |
$1: UUID of the floating IP. |
Severity level |
Warning |
Example |
Failed to create floating IP b3848485-eff1-427f-a012-f1fff28c65c8 in VSM. Reason: The VSM service is not enabled. |
Explanation |
Failed to create a floating IP. |
Recommended action |
Verify that the VSM service has been enabled. |
Failed to edit floating IP
Keyword |
UPDATE_FLOATING_IP_FAILED |
Message text |
Failed to update floating IP $1 in VSM. Reason: The VSM service is not enabled. |
Variable fields |
$1: UUID of the floating IP. |
Severity level |
Warning |
Example |
Failed to update floating IP b3848485-eff1-427f-a012-f1fff28c65c8 in VSM. Reason: The VSM service is not enabled. |
Explanation |
Failed to edit a floating IP. |
Recommended action |
Verify that the VSM service has been enabled. |
Failed to delete floating IP
Keyword |
DELETE_FLOATING_IP_FAILED |
Message text |
Failed to delete floating IP $1 from VSM. Reason: The VSM service is not enabled. |
Variable fields |
$1: UUID of the floating IP. |
Severity level |
Warning |
Example |
Failed to delete floating IP b3848485-eff1-427f-a012-f1fff28c65c8 from VSM. Reason: The VSM service is not enabled. |
Explanation |
Failed to delete a floating IP. |
Recommended action |
Verify that the VSM service has been enabled. |
Failed to create network
Keyword |
CREATE_NETWORK_FAILED |
Message text |
Failed to create network $1 in VSM. Reason: The VSM service is not enabled. |
Variable fields |
$1: UUID of the network. |
Severity level |
Warning |
Example |
Failed to create network b3848485-eff1-427f-a012-f1fff28c65c8 in VSM. Reason: The VSM service is not enabled. |
Explanation |
Failed to create a network. |
Recommended action |
Verify that the VSM service has been enabled. |
Failed to edit network
Keyword |
UPDATE_NETWORK_FAILED |
Message text |
Failed to update network $1 in VSM. Reason: The VSM service is not enabled. |
Variable fields |
$1: UUID of the network. |
Severity level |
Warning |
Example |
Failed to update network b3848485-eff1-427f-a012-f1fff28c65c8 in VSM. Reason: The VSM service is not enabled. |
Explanation |
Failed to edit a network. |
Recommended action |
Verify that the VSM service has been enabled. |
Failed to delete network
Keyword |
DELETE_NETWORK_FAILED |
Message text |
Failed to delete network $1 from VSM. Reason: The VSM service is not enabled. |
Variable fields |
$1: UUID of the network. |
Severity level |
Warning |
Example |
Failed to delete network b3848485-eff1-427f-a012-f1fff28c65c8 from VSM. Reason: The VSM service is not enabled. |
Explanation |
Failed to delete a network. |
Recommended action |
Verify that the VSM service has been enabled. |
Failed to create vPort
Keyword |
CREATE_PORT_FAILED |
Message text |
Failed to create port $1 in VSM. Reason: The VSM service is not enabled. |
Variable fields |
$1: UUID of the vPort. |
Severity level |
Warning |
Example |
Failed to create port b3848485-eff1-427f-a012-f1fff28c65c8 in VSM. Reason: The VSM service is not enabled. |
Explanation |
Failed to create a vPort. |
Recommended action |
Verify that the VSM service has been enabled. |
Failed to edit vPort
Keyword |
UPDATE_PORT_FAILED |
Message text |
Failed to update port $1 in VSM. Reason: The VSM service is not enabled. |
Variable fields |
$1: UUID of the vPort. |
Severity level |
Warning |
Example |
Failed to update port b3848485-eff1-427f-a012-f1fff28c65c8 in VSM. Reason: The VSM service is not enabled. |
Explanation |
Failed to edit a vPort. |
Recommended action |
Verify that the VSM service has been enabled. |
Failed to delete vPort
Keyword |
DELETE_PORT_FAILED |
Message text |
Failed to delete port $1 from VSM. Reason: The VSM service is not enabled. |
Variable fields |
$1: UUID of the vPort. |
Severity level |
Warning |
Example |
Failed to delete port b3848485-eff1-427f-a012-f1fff28c65c8 from VSM. Reason: The VSM service is not enabled. |
Explanation |
Failed to delete a vPort. |
Recommended action |
Verify that the VSM service has been enabled. |
Failed to edit network overlay host
Keyword |
UPDATE_NETOVERLAY_HOST_FAILED |
Message text |
Failed to update netoverlay host $1 to VSM. Reason: The VSM service is not enabled. |
Variable fields |
$1: UUID of the network overlay host. |
Severity level |
Warning |
Example |
Failed to update netoverlay host b3848485-eff1-427f-a012-f1fff28c65c8 to VSM. Reason: The VSM service is not enabled. |
Explanation |
Failed to edit a network overlay host. |
Recommended action |
Verify that the VSM service has been enabled. |
Failed to delete network overlay group
Keyword |
DELETE_NETOVERLAY_GROUP_FAILED |
Message text |
Failed to delete netoverlay group $1 from VSM. Reason: The VSM service is not enabled. |
Variable fields |
$1: Name of the network overlay group. |
Severity level |
Warning |
Example |
Failed to delete netoverlay group group1 from VSM. Reason: The VSM service is not enabled. |
Explanation |
Failed to delete a network overlay group |
Recommended action |
Verify that the VSM service has been enabled. |
Failed to delete network overlay host
Keyword |
DELETE_NETOVERLAY_HOST_FAILED |
Message text |
Failed to delete netoverlay host $1 from VSM. Reason: The VSM service is not enabled. |
Variable fields |
$1: Name of the network overlay host. |
Severity level |
Warning |
Example |
Failed to delete netoverlay host host1 from VSM. Reason: The VSM service is not enabled. |
Explanation |
Failed to delete a network overlay host. |
Recommended action |
Verify that the VSM service has been enabled. |
Failed to create subnet
Keyword |
CREATE_SUBNET_FAILED |
Message text |
Failed to create subnet $1 in VSM. Reason: The VSM service is not enabled. |
Variable fields |
$1: UUID of the subnet. |
Severity level |
Warning |
Example |
Failed to create subnet b3848485-eff1-427f-a012-f1fff28c65c8 in VSM. Reason: The VSM service is not enabled. |
Explanation |
Failed to create a subnet. |
Recommended action |
Verify that the VSM service has been enabled. |
Failed to edit subnet
Keyword |
UPDATE_SUBNET_FAILED |
Message text |
Failed to update subnet $1 in VSM. Reason: The VSM service is not enabled. |
Variable fields |
$1: UUID of the subnet. |
Severity level |
Warning |
Example |
Failed to update subnet b3848485-eff1-427f-a012-f1fff28c65c8 in VSM. Reason: The VSM service is not enabled. |
Explanation |
Failed to edit a subnet. |
Recommended action |
Verify that the VSM service has been enabled. |
Failed to delete subnet
Keyword |
DELETE_SUBNET_FAILED |
Message text |
Failed to delete subnet $1 from VSM. Reason: The VSM service is not enabled. |
Variable fields |
$1: UUID of the subnet. |
Severity level |
Warning |
Example |
Failed to delete subnet b3848485-eff1-427f-a012-f1fff28c65c8 from VSM. Reason: The VSM service is not enabled. |
Explanation |
Failed to delete a subnet. |
Recommended action |
Verify that the VSM service has been enabled. |
Failed to create network overlay group
Keyword |
CREATE_NETOVERLAY_GROUP_FAILED |
Message text |
Failed to create netoverlay group $1 in VSM. Reason: The VSM service is not enabled. |
Variable fields |
$1: UUID of the network overlay group. |
Severity level |
Warning |
Example |
Failed to create netoverlay group b3848485-eff1-427f-a012-f1fff28c65c8 in VSM. Reason: The VSM service is not enabled. |
Explanation |
Failed to create a network overlay group. |
Recommended action |
Verify that the VSM service has been enabled. |
Failed to create network overlay host
Keyword |
CREATE_NETOVERLAY_HOST_FAILED |
Message text |
Failed to create netoverlay host $1 in VSM. Reason: The VSM service is not enabled. |
Variable fields |
$1: UUID of the network overlay host. |
Severity level |
Warning |
Example |
Failed to create netoverlay host b3848485-eff1-427f-a012-f1fff28c65c8 in VSM. Reason: The VSM service is not enabled. |
Explanation |
Failed to create a network overlay host. |
Recommended action |
Verify that the VSM service has been enabled. |
Failed to create VLAN mapping
Keyword |
CREATE_VLAN_MAP_FAILED |
Message text |
Failed to create VLAN mapping $1 in VSM. Reason: The VSM service is not enabled. |
Variable fields |
$1: UUID of the VLAN mapping. |
Severity level |
Warning |
Example |
Failed to create VLAN mapping b3848485-eff1-427f-a012-f1fff28c65c8 in VSM. Reason: The VSM service is not enabled. |
Explanation |
Failed to create a VLAN mapping. |
Recommended action |
Verify that the VSM service has been enabled. |
Failed to delete VLAN mapping
Keyword |
DELETE_VLAN_MAP_FAILED |
Message text |
Failed to delete VLAN mapping $1 from VSM. Reason: The VSM service is not enabled. |
Variable fields |
$1: UUID of the VLAN mapping. |
Severity level |
Warning |
Example |
Failed to delete VLAN mapping b3848485-eff1-427f-a012-f1fff28c65c8 from VSM. Reason: The VSM service is not enabled. |
Explanation |
Failed to delete a VLAN mapping. |
Recommended action |
Verify that the VSM service has been enabled. |
Failed to create segment
Keyword |
CREATE_SEGMENT_FAILED |
Message text |
Failed to create segment $ in VSM. Reason: The VSM service is not enabled. |
Variable fields |
$1: UUID of the segment. |
Severity level |
Warning |
Example |
Failed to create segment b3848485-eff1-427f-a012-f1fff28c65c8 in VSM. Reason: The VSM service is not enabled. |
Explanation |
Failed to create a segment. |
Recommended action |
Verify that the VSM service has been enabled. |
Failed to edit segment
Keyword |
UPDATE_SEGMENT_FAILED |
Message text |
Failed to update segment &1 in VSM. Reason: The VSM service is not enabled. |
Variable fields |
$1: UUID of the segment. |
Severity level |
Warning |
Example |
Failed to update segment b3848485-eff1-427f-a012-f1fff28c65c8 in VSM. Reason: The VSM service is not enabled. |
Explanation |
Failed to edit a segment. |
Recommended action |
Verify that the VSM service has been enabled. |
Failed to delete segment
Keyword |
DELETE_SEGMENT_FAILED |
Message text |
Failed to delete segment $1 from VSM. Reason: The VSM service is not enabled. |
Variable fields |
$1: UUID of the segment. |
Severity level |
Warning |
Example |
Failed to delete segment b3848485-eff1-427f-a012-f1fff28c65c8 from VSM. Reason: The VSM service is not enabled. |
Explanation |
Failed to delete a segment. |
Recommended action |
Verify that the VSM service has been enabled. |
Failed to create route entries
Keyword |
CREATE_ROUTE_ENTITY_FAILED |
Message text |
Failed to create route entries in VSM. Reason: The VSM service is not enabled. |
Variable fields |
N/A |
Severity level |
Warning |
Example |
Failed to create route entries in VSM. Reason: The VSM service is not enabled. |
Explanation |
Failed to create route entries. |
Recommended action |
Verify that the VSM service has been enabled. |
Route entry deletion failed
Keyword |
DELETE_ROUTE_ENTITY_FAILED |
Message text |
· Failed to delete route entries from VSM. Reason: The VSM service is not enabled. · Failed to delete route entry $1 from VSM. Reason: The VSM service is not enabled |
Variable fields |
$1: UUID of the route entry. |
Severity level |
Warning |
Example |
· Failed to delete route entries from VSM. Reason: The VSM service is not enabled. · Failed to delete route entry b3848485-eff1-427f-a012-f1fff28c65c8 from VSM. Reason: The VSM service is not enabled. |
Explanation |
Route entry deletion failed. |
Recommended action |
Verify that the VSM service has been enabled. |
Failed to create trunk
Keyword |
CREATE_TRUNK_FAILED |
Message text |
Failed to create trunk $1 in VSM. Reason: The VSM service is not enabled. |
Variable fields |
$1: UUID of the trunk. |
Severity level |
Warning |
Example |
Failed to create trunk b3848485-eff1-427f-a012-f1fff28c65c8 in VSM. Reason: The VSM service is not enabled. |
Explanation |
Failed to create a trunk. |
Recommended action |
Verify that the VSM service has been enabled. |
Failed to edit trunk
Keyword |
UPDATE_TRUNK_FAILED |
Message text |
Failed to update trunk $1 in VSM. Reason: The VSM service is not enabled. |
Variable fields |
$1: UUID of the trunk. |
Severity level |
Warning |
Example |
Failed to update trunk b3848485-eff1-427f-a012-f1fff28c65c8 in VSM. Reason: The VSM service is not enabled. |
Explanation |
Failed to edit a trunk. |
Recommended action |
Verify that the VSM service has been enabled. |
Failed to delete trunk
Keyword |
DELETE_TRUNK_FAILED |
Message text |
Failed to delete trunk $1 from VSM. Reason: The VSM service is not enabled. |
Variable fields |
$1: UUID of the trunk. |
Severity level |
Warning |
Example |
Failed to delete trunk b3848485-eff1-427f-a012-f1fff28c65c8 from VSM. Reason: The VSM service is not enabled. |
Explanation |
Failed to delete a trunk. |
Recommended action |
Verify that the VSM service has been enabled. |
Failed to create VPC connection
Keyword |
CREATE_VPC_CONNECTION_FAILED |
Message text |
Failed to create VPC connection $1 in VSM. Reason: The VSM service is not enabled. |
Variable fields |
$1: UUID of the VPC connection. |
Severity level |
Warning |
Example |
Failed to create VPC connection b3848485-eff1-427f-a012-f1fff28c65c8 in VSM. Reason: The VSM service is not enabled. |
Explanation |
Failed to create a VPC connection. |
Recommended action |
Verify that the VSM service has been enabled. |
Failed to edit VPC connection
Keyword |
UPDATE_VPC_CONNECTION_FAILED |
Message text |
Failed to update VPC connection $1 in VSM. Reason: The VSM service is not enabled. |
Variable fields |
$1: UUID of the VPC connection. |
Severity level |
Warning |
Example |
Failed to update VPC connection b3848485-eff1-427f-a012-f1fff28c65c8 in VSM. Reason: The VSM service is not enabled. |
Explanation |
Failed to edit a VPC connection. |
Recommended action |
Verify that the VSM service has been enabled. |
Failed to delete VPC connection
Keyword |
DELETE_VPC_CONNECTION_FAILED |
Message text |
Failed to delete VPC connection $1 from VSM. Reason: The VSM service is not enabled. |
Variable fields |
$1: UUID of the VPC connection. |
Severity level |
Warning |
Example |
Failed to delete VPC connection b3848485-eff1-427f-a012-f1fff28c65c8 from VSM. Reason: The VSM service is not enabled. |
Explanation |
Failed to delete a VPC connection. |
Recommended action |
Verify that the VSM service has been enabled. |
Failed to create subports
Keyword |
CREATE_SUBPORT_FAILED |
Message text |
Failed to create subports in VSM. Reason: The VSM service is not enabled. |
Variable fields |
N/A |
Severity level |
Warning |
Example |
Failed to create subports in VSM. Reason: The VSM service is not enabled. |
Explanation |
Failed to create subports. |
Recommended action |
Verify that the VSM service has been enabled. |
Failed to delete subports
Keyword |
DELETE_SUBPORT_FAILED |
Message text |
Failed to delete subports from VSM. Reason: The VSM service is not enabled. |
Variable fields |
N/A |
Severity level |
Warning |
Example |
Failed to delete subports from VSM. Reason: The VSM service is not enabled. |
Explanation |
Failed to delete subports. |
Recommended action |
Verify that the VSM service has been enabled. |
Failed to create security group rule
Keyword |
CREATE_SECURITY_GROUP_RULE_FAILED |
Message text |
Failed to create security group rule $1 in VSM. Reason: The VSM service is not enabled. |
Variable fields |
$1: UUID of the security group rule. |
Severity level |
Warning |
Example |
Failed to create security group rule b3848485-eff1-427f-a012-f1fff28c65c8 in VSM. Reason: The VSM service is not enabled. |
Explanation |
Failed to create a security group rule. |
Recommended action |
Verify that the VSM service has been enabled. |
Failed to edit security group rule
Keyword |
UPDATE_SECURITY_GROUP_RULE_FAILED |
Message text |
Failed to update security group rule $1 in VSM. Reason: The VSM service is not enabled. |
Variable fields |
$1: UUID of the security group rule. |
Severity level |
Warning |
Example |
Failed to update security group rule b3848485-eff1-427f-a012-f1fff28c65c8 in VSM. Reason: The VSM service is not enabled. |
Explanation |
Failed to edit a security group rule. |
Recommended action |
Verify that the VSM service has been enabled. |
Failed to delete security group rule
Keyword |
DELETE_SECURITY_GROUP_RULE_FAILED |
Message text |
Failed to delete security group rule $1 from VSM. Reason: The VSM service is not enabled. |
Variable fields |
$1: UUID of the security group rule. |
Severity level |
Warning |
Example |
Failed to delete security group rule b3848485-eff1-427f-a012-f1fff28c65c8 from VSM. Reason: The VSM service is not enabled. |
Explanation |
Failed to delete a security group rule. |
Recommended action |
Verify that the VSM service has been enabled. |
Failed to create security group
Keyword |
CREATE_SECURITY_GROUP_FAILED |
Message text |
Failed to create security group $1 in VSM. Reason: The VSM service is not enabled. |
Variable fields |
$1: UUID of the security group. |
Severity level |
Warning |
Example |
Failed to create security group b3848485-eff1-427f-a012-f1fff28c65c8 in VSM. Reason: The VSM service is not enabled. |
Explanation |
Failed to create a security group. |
Recommended action |
Verify that the VSM service has been enabled. |
Failed to edit security group
Keyword |
UPDATE_SECURITY_GROUP_FAILED |
Message text |
Failed to update security group $1 in VSM. Reason: The VSM service is not enabled. |
Variable fields |
$1: UUID of the security group. |
Severity level |
Warning |
Example |
Failed to update security group b3848485-eff1-427f-a012-f1fff28c65c8 in VSM. Reason: The VSM service is not enabled. |
Explanation |
Failed to edit a security group. |
Recommended action |
Verify that the VSM service has been enabled. |
Failed to delete security group
Keyword |
DELETE_SECURITY_GROUP_FAILED |
Message text |
Failed to delete security group $1 from VSM. Reason: The VSM service is not enabled. |
Variable fields |
$1: UUID of the security group. |
Severity level |
Warning |
Example |
Failed to delete security group b3848485-eff1-427f-a012-f1fff28c65c8 from VSM. Reason: The VSM service is not enabled. |
Explanation |
Failed to delete a security group. |
Recommended action |
Verify that the VSM service has been enabled. |
Failed to create QoS policy.
Keyword |
CREATE_QoS_POLICY_FAILED |
Message text |
Failed to create QoS policy $1 in VSM. Reason: The VSM service is not enabled. |
Variable fields |
$1: UUID of the QoS policy. |
Severity level |
Warning |
Example |
Failed to create QoS policy b3848485-eff1-427f-a012-f1fff28c65c8 in VSM. Reason: The VSM service is not enabled. |
Explanation |
Failed to create a QoS policy. |
Recommended action |
Verify that the VSM service has been enabled. |
Failed to edit QoS policy.
Keyword |
UPDATE_QoS_POLICY_FAILED |
Message text |
Failed to update QoS policy $1 in VSM. Reason: The VSM service is not enabled. |
Variable fields |
$1: UUID of the QoS policy. |
Severity level |
Warning |
Example |
Failed to update QoS policy b3848485-eff1-427f-a012-f1fff28c65c8 in VSM. Reason: The VSM service is not enabled. |
Explanation |
Failed to edit a QoS policy. |
Recommended action |
Verify that the VSM service has been enabled. |
Failed to delete QoS policy
Keyword |
DELETE_QoS_POLICY_FAILED |
Message text |
Failed to delete QoS policy $1 from VSM. Reason: The VSM service is not enabled. |
Variable fields |
$1: UUID of the QoS policy. |
Severity level |
Warning |
Example |
Failed to delete QoS policy b3848485-eff1-427f-a012-f1fff28c65c8 from VSM. Reason: The VSM service is not enabled. |
Explanation |
Failed to delete a QoS policy. |
Recommended action |
Verify that the VSM service has been enabled. |
Failed to edit bare metal state
Keyword |
UPDATE_BARE_METAL_STATUS_FAILED |
Message text |
Failed to update bare metal status in BSM. Reason: The BSM service is not enabled. |
Variable fields |
N/A |
Severity level |
Warning |
Example |
Failed to update bare metal status in BSM. Reason: The BSM service is not enabled. |
Explanation |
Failed to edit bare metal state. |
Recommended action |
Verify that the BSM service has been enabled. |
Failed to bind network port to VLAN-VXLAN mapping table
Keyword |
CREATE_WORKING_MAP_FAILED |
Message text |
Failed to bind a port to a VLAN-VXLAN mapping table in BSM. Reason: The BSM service is not enabled. |
Variable fields |
N/A |
Severity level |
Warning |
Example |
Failed to bind a port to a VLAN-VXLAN mapping table in BSM. Reason: The BSM service is not enabled. |
Explanation |
Failed to bind a network port to a VLAN-VXLAN mapping table. |
Recommended action |
Verify that the BSM service has been enabled. |
Failed to unbind network port from VLAN-VXLAN mapping table
Keyword |
DELETE_WORKING_MAP_FAILED |
Message text |
Failed to unbind a port from a VLAN-VXLAN mapping table in BSM. Reason: The BSM service is not enabled. |
Variable fields |
N/A |
Severity level |
Warning |
Example |
Failed to unbind a port from a VLAN-VXLAN mapping table in BSM. Reason: The BSM service is not enabled. |
Explanation |
Failed to unbind a network port from a VLAN-VXLAN mapping table. |
Recommended action |
Verify that the BSM service has been enabled. |
Created tenant successfully
Keyword |
CREATE_TENANT_SUCCESS |
Message text |
Created a tenant in Tenant successfully: $1 |
Variable fields |
$1: Tenant information. |
Severity level |
Info |
Example |
Created a tenant in Tenant successfully :{ "ID":"c143f677-27b1-4464-b3ca-c98307a24cd7", "Tenant name":"test", "Tenant type":"local-create", "Cloud region name":"default", "Cloud domain name":"Default" } |
Explanation |
Created a tenant successfully. |
Recommended action |
N/A |
Delete tenant successfully
Keyword |
DELETE_TENANT_SUCCESS |
Message text |
Deleted tenant $1 in Tenant successfully. |
Variable fields |
$1: UUID of the tenant. |
Severity level |
Info |
Example |
Deleted tenant 2b2151a2-f111-40f0-a0ea-61a76879e972 in Tenant successfully. |
Explanation |
Deleted a tenant successfully. |
Recommended action |
N/A |
Created routing table successfully
Keyword |
CREATE_ROUTER_TABLE_SUCCESS |
Message text |
Created a routing table in VSM successfully: $1 |
Variable fields |
$1: Routing table information. |
Severity level |
Info |
Example |
Created a routing table in VSM successfully: { "ID":"2c980c74-aeb2-4cd0-a3db-26910aff90d2", "Name":"router3", "Tenant ID":"57a788e3-6c69-476b-a648-cecc81395aff", "Tenant name":"bpy(Default)", "Router ID":"2c980c74-aeb2-4cd0-a3db-26910aff90d2", "Router name":"router3", "Bound vRouter ID":"null", "Route entries":"[]", "Cloud region name":"openstack1" } |
Explanation |
Created a routing table successfully |
Recommended action |
N/A |
Deleted routing table successfully
Keyword |
DELETE_ROUTER_TABLE_SUCCESS |
Message text |
Deleted routing table $1 in VSM successfully. |
Variable fields |
$1: UUID of the routing table. |
Severity level |
Info |
Example |
Deleted routing table b3848485-eff1-427f-a012-f1fff28c65c8 in VSM successfully. |
Explanation |
Deleted a routing table successfully. |
Recommended action |
N/A |
Created network segment successfully
Keyword |
CREATE_SEGMENT_SUCCESS |
Message text |
Created a network segment in VSM successfully: $1 |
Variable fields |
$1: Network segment information. |
Severity level |
Info |
Example |
Created a network segment in VSM successfully: { "ID":"dcb034db-43ec-4aab-9cf3-06b3172d0f3d", "Name":"", "Description":"", "Network ID":"34878f49-712e-45f7-a48f-b5ddacbf23f2", "Segment ID":"8", "Network type":"VLAN", "Physical network":"gateway1", "Cloud region name":"openstack1" } |
Explanation |
Created a network segment successfully. |
Recommended action |
N/A |
Deleted network segment successfully
Keyword |
DELETE_SEGMENT_SUCCESS |
Message text |
Deleted network segment $1 in VSM successfully. |
Variable fields |
$1: UUID of the network segment. |
Severity level |
Info |
Example |
Deleted network segment b3848485-eff1-427f-a012-f1fff28c65c8 in VSM successfully. |
Explanation |
Deleted a network segment successfully. |
Recommended action |
N/A |
Bound gateway to tenant successfully
Keyword |
CREATE_TENANT_BOUND_GATEWAY_SUCCESS |
Message text |
Bound a gateway to the tenant in NEM successfully: $1 |
Variable fields |
$1: Binding information. |
Severity level |
Info |
Example |
Bound a gateway to the tenant in NEM successfully: { "ID":"f7b41670-f5f1-410c-83dd-ebe7c2eaf20a", "Tenant ID":"c143f677-27b1-4464-b3ca-c98307a24cd7", "Default gateway ID":"null", "Gateway":"[6cc2661f-1cf5-4531-97fa-51fecf5fecee, 693f82d5-15a6-4466-af20-46321f26ff21]" } |
Explanation |
Bound a gateway to a tenant successfully. |
Recommended action |
N/A |
Unbound gateway from tenant successfully
Keyword |
DELETE_TENANT_BOUND_GATEWAY_SUCCESS |
Message text |
Unbound gateway $1 from the tenant in NEM successfully. |
Variable fields |
$1:UUID of the gateway. |
Severity level |
Info |
Example |
Unbound gateway b3848485-eff1-427f-a012-f1fff28c65c8 from the tenant in NEM successfully. |
Explanation |
Unbound a gateway from a tenant successfully. |
Recommended action |
N/A |
Bound vRouter to gateway successfully
Keyword |
ROUTER_BIND_GATEWAY_SUCCESS |
Message text |
Bound vRouter $1 to gateway $2 in NEM successfully. |
Variable fields |
$1: UUID of the vRouter. $2: UUID of the gateway. |
Severity level |
Info |
Example |
Bound vRouter b3848485-eff1-427f-a012-f1fff28c65c8 to gateway a3838485- a012-427f-a eff1-f1fff28c11a8 in NEM successfully. |
Explanation |
Bound a vRouter to a gateway successfully. |
Recommended action |
N/A |
Unbound vRouter from gateway successfully
Keyword |
ROUTER_UNBIND_GATEWAY_SUCCESS |
Message text |
Unbound vRouter $1 from gateway $2 in NEM successfully. |
Variable fields |
$1: UUID of the vRouter. $2: UUID of the gateway. |
Severity level |
Info |
Example |
Unbound vRouter b3848485-eff1-427f-a012-f1fff28c65c8 from gateway a3838485- a012-427f-a eff1-f1fff28c11a8 in NEM successfully. |
Explanation |
Unbound a vRouter from a gateway successfully. |
Recommended action |
N/A |
VPNaaS
This section contains IPsec VPN messages.
Start of IPsec VPN configuration recovery on non-active leader controllers
Keyword |
BEGIN_RECOVER_VPNaaS_CONFIG |
Message text |
All non-active leader controllers started recovering the VPNaaS configuration. |
Variable fields |
N/A |
Severity level |
Info |
Example |
All non-active leader controllers started recovering the VPNaaS configuration. |
Explanation |
All non-active leader controllers started recovering the IPsec configuration. The IPsec configuration to be recovered includes IKE policies, IPsec policies, VPN services, and IPsec connection information. |
Recommended action |
As a best practice, do not perform any operations on the controllers during the configuration recovery process. |
End of IPsec VPN configuration recovery on non-active leader controllers
Keyword |
FINISH_RECOVER_VPNaaS_CONFIG |
Message text |
All non-active leader controllers completed recovering the VPNaaS configuration. |
Variable fields |
N/A |
Severity level |
Info |
Example |
All non-active leader controllers completed recovering the VPNaaS configuration. |
Explanation |
All non-active leader controllers completed recovering the IPsec configuration. The recovered IPsec configuration includes IKE policies, IPsec policies, VPN services, and IPsec connection information. |
Recommended action |
No action is required. |
VSM
This section contains virtual network messages.
Failure to add host because of invalid license
Keyword |
LICENSE_INVALID_DECS |
Message text |
License is invalid, failed to add host. |
Variable fields |
N/A |
Severity level |
Warning |
Example |
License is invalid, failed to add host. |
Explanation |
Failed to add the host because the license is invalid. |
Recommended action |
Determine whether the overlay license is available. If it is unavailable, apply for a new overlay license. |
vPort number reaching threshold
Keyword |
VPORTS_REACH_THRESHOLD |
Message text |
The number of vPorts [$1] has reached the threshold [$2]. |
Variable fields |
$1: Number of vPorts. $2: Threshold for the number of vPorts. |
Severity level |
Warning |
Example |
The number of vPorts [120] has reached the threshold [100]. |
Explanation |
The number of vPorts has reached the threshold. |
Recommended action |
Increase the vPort number threshold or reduce the number of vPorts. |
vPort number falling below threshold
Keyword |
VPORTS_BELOW_THRESHOLD |
Message text |
The number of vPorts [$1] has fallen below the threshold [$2]. |
Variable fields |
$1: Number of vPorts. $2: Threshold for the number of vPorts. |
Severity level |
Warning |
Example |
The number of vPorts [90] has fallen below the threshold [100]. |
Explanation |
The number of vPorts has fallen below the threshold. |
Recommended action |
No action is required. |
Start of VSM configuration recovery on non-active leader controllers
Keyword |
BEGIN_RECOVER_VSM_CONFIG |
Message text |
All non-active leader controllers started recovering the VSM configuration. |
Variable fields |
N/A |
Severity level |
Info |
Example |
All non-active leader controllers started recovering the VSM configuration. |
Explanation |
All non-active leader controllers started recovering the VSM configuration. |
Recommended action |
As a best practice, do not perform any operations on the controllers during the configuration recovery process. |
End of VSM configuration recovery on non-active leader controllers
Keyword |
FINISH_RECOVER_VSM_CONFIG |
Message text |
All non-active leader controllers completed recovering the VSM configuration. |
Variable fields |
N/A |
Severity level |
Info |
Example |
All non-active leader controllers completed recovering the VSM configuration. |
Explanation |
All non-active leader controllers completed recovering the VSM configuration. |
Recommended action |
No action is required. |
Compute node neighbor aging after a specific time period
Keyword |
LLDP_COMPUTE_NODE_NEIGHBOR_AGING |
Message text |
Compute node neighbor (host name: $1) on port $2 of device $3 will age out in $4 hours. |
Variable fields |
$1: Host name. $2: Access interface. $3: IP address of the access device. $4: Aging time. |
Severity level |
Info |
Example |
Compute node neighbor (host name: exsi-hypervisor.h3croot.huawei-3com.com) on port XGE1/0/21 of device 172.16.68.3 will age out in 24 hours. |
Explanation |
The compute node host that the device accesses will age after a specific time period. |
Recommended action |
· Verify that the link between the device and the host is correct. · Verify that the link between the device and the controller is correct. |
LLDP neighbor relationship restoration between compute node host and device
Keyword |
LLDP_COMPUTE_NODE_NEIGHBOR_RESTORE |
Message text |
Compute node neighbor (host name: $1) on port $2 of device $3 has restored. |
Variable fields |
$1: Host name. $2: Access interface. $3: IP address of the access device. |
Severity level |
Info |
Example |
Compute node neighbor (host name: exsi-hypervisor.h3croot.huawei-3com.com) on port XGE1/0/21 of device 172.16.68.3 has restored. |
Explanation |
The LLDP neighbor relationship between the compute node host and the device was restored. |
Recommended action |
No action is required. |
LLDP neighbor relationship establishment between compute node host and device
Keyword |
LLDP_COMPUTE_NODE_NEIGHBOR_SETUP |
Message text |
Compute node neighbor (host name: $1) on port $2 of device $3 has been set up. |
Variable fields |
$1: Host name. $2: Access interface. $3: IP address of the access device. |
Severity level |
Info |
Example |
Compute node neighbor (host name: exsi-hypervisor.h3croot.huawei-3com.com) on port XGE1/0/21 of device 172.16.68.3 has been set up. |
Explanation |
The compute node host and the device established an LLDP neighbor relationship. |
Recommended action |
No action is required. |
LLDP neighbor relationship interruption between compute node host and device
Keyword |
LLDP_COMPUTE_NODE_NEIGHBOR_RELEASED |
Message text |
· Compute node neighbor (host name: $1) on port $2 of device $3 has been released because the neighbor has aged out. · Compute node neighbor (host name: $1) on port $2 of device $3 has been released because the neighbor has been deleted. |
Variable fields |
$1: Host name. $2: Access interface. $3: IP address of the access device. |
Severity level |
Info |
Example |
· Compute node neighbor (host name: exsi-hypervisor.h3croot.huawei-3com.com) on port XGE1/0/21 of device 172.16.68.3 has been released because the neighbor has aged out. · Compute node neighbor (host name: exsi-hypervisor.h3croot.huawei-3com.com) on port XGE1/0/21 of device 172.16.68.3 has been released because the neighbor has been deleted. |
Explanation |
The LLDP neighbor relationship between the compute node host and the device was interrupted. Possible reasons include: · The host has aged. · The host has been deleted. |
Recommended action |
· Verify that the link between the device and the host is correct. · Verify that the link between the device and the controller is correct. · Verify that the host is not deleted. |
Network node neighbor aging after a specific time period
Keyword |
LLDP_NETWORK_NODE_NEIGHBOR_AGING |
Message text |
Network node neighbor (host name: $1, VTEP IP: $2) on port $3 of device $4 will age out in $5 hours. |
Variable fields |
$1: Host name. $2: VTEP IP of the host. $3: Access interface. $4: IP address of the access device. $5: Aging time. |
Severity level |
Info |
Example |
Network node neighbor (host name: exsi-hypervisor.h3croot.huawei-3com.com, VTEP IP: 101.1.1.10) on port XGE1/0/21 of device 172.16.68.3 will age out in 24 hours. |
Explanation |
The network node host that the device accesses will age after a specific time period. |
Recommended action |
· Verify that the link between the device and the host is correct. · Verify that the link between the device and the controller is correct. |
LLDP neighbor relationship restoration between network node host and device
Keyword |
LLDP_NETWORK_NODE_NEIGHBOR_RESTORE |
Message text |
Network node neighbor (host name: $1, VTEP IP: $2) on port $3 of device $4 has restored. |
Variable fields |
$1: Host name. $2: VTEP IP of the host. $3: Access interface. $4: IP address of the access device. |
Severity level |
Info |
Example |
Network node neighbor (host name: exsi-hypervisor.h3croot.huawei-3com.com, VTEP IP: 101.1.1.10) on port XGE1/0/21 of device 172.16.68.3 has restored. |
Explanation |
The LLDP neighbor relationship between the network node host and the device was restored. |
Recommended action |
No action is required. |
LLDP neighbor relationship establishment between network node host and device
Keyword |
LLDP_NETWORK_NODE_NEIGHBOR_SETUP |
Message text |
Network node neighbor (host name: $1, VTEP IP: $2) on port $3 of device $4 has been set up. |
Variable fields |
$1: Host name. $2: VTEP IP of the host. $3: Access interface. $4: IP address of the access device. |
Severity level |
Info |
Example |
Network node neighbor (host name: exsi-hypervisor.h3croot.huawei-3com.com, VTEP IP: 101.1.1.10) on port XGE1/0/21 of device 172.16.68.3 has been set up. |
Explanation |
The network node host and the device established an LLDP neighbor relationship. |
Recommended action |
No action is required. |
LLDP neighbor relationship interruption between network node host and device
Keyword |
LLDP_NETWORK_NODE_NEIGHBOR_RELEASED |
Message text |
· Network node neighbor (host name: $1, VTEP IP: $2) on port $3 of device $4 has been released because the neighbor has aged out. · Network node neighbor (host name: $1, VTEP IP: $2) on port $3 of device $4 has been released because the neighbor has been deleted. |
Variable fields |
$1: Host name. $2: VTEP IP of the host. $3: Access interface. $4: IP address of the access device. |
Severity level |
Info |
Example |
· Network node neighbor (host name: exsi-hypervisor.h3croot.huawei-3com.com, VTEP IP: 101.1.1.10) on port XGE1/0/21 of device 172.16.68.3 has been released because the neighbor has aged out. · Network node neighbor (host name: exsi-hypervisor.h3croot.huawei-3com.com, VTEP IP: 101.1.1.10) on port XGE1/0/21 of device 172.16.68.3 has been released because the neighbor has been deleted. |
Explanation |
The LLDP neighbor relationship between the network node host and the device was interrupted. Possible reasons include: · The host has aged. · The host has been deleted. |
Recommended action |
· Verify that the link between the device and the host is correct. · Verify that the link between the device and the controller is correct. · Verify that the host is not deleted. |
Successful VM migration
Keyword |
ARP_MIGRATE |
Message text |
The VM (IP $1, old MAC: $2, new MAC: $3) migrate from the source port $4 of access device $5 to the destination port $6 of access device $7 successfully. |
Variable fields |
$1: IP address of the VM. $2: Old MAC address of the VM. $3: New MAC address of the VM. $4: Old access interface. $5: Management IP address of the old access device. $6: New access interface. $7: Management IP address of the new access device. |
Severity level |
Warning |
Example |
The VM (IP 1.1.1.2, old MAC: 00:50:56:95:01:d1, new MAC: 00:50:56:95:60:1e) migrate from the source port XGE1/0/5:3 of access device 172.16.68.2 to the destination port XGE1/0/5:3 of access device 172.16.68.2 successfully. |
Explanation |
A VM successfully migrated. |
Recommended action |
No action is required. |
Failure to issue ACL rule because of insufficient hardware resources
Keyword |
VPORT_SECURITY_RULE_FAILED |
Message text |
The ACL rule [ID: $1, Security policy: $2, Direction: $3, IPv4 prefix: $4, Protocol: $5 ] failed to take effect on vPort [IP: $6, MAC: $7, Tenant ID: $8] because of insufficient hardware resources on device [IP: $9]. |
Variable fields |
$1: UUID of the rule. $2: Name of the security policy to which the rule belongs. $3: Packet direction that the rule matches. $4: IPv4 prefix that the rule matches. $5: Protocol type that the rule matches. $6: IP address of the vPort. $7: MAC address of the vPort. $8: UUID of the tenant to which the vPort belongs. $9: Management IP address of the device. |
Severity level |
Warning |
Example |
The ACL rule [ID: 608da4b7-64ba-49d3-9fc3-96a7fd5c67f7, Security policy: Policy1, Direction: ingress, IPv4 prefix: 1.1.1.1/32, Protocol: TCP ] failed to take effect on vPort [IP: 4.4.4.4,MAC: 00:50:56:95:09:8d, Tenant ID: ffffffff-0000-0000-0000-000000000001] because of insufficient hardware resources on device [IP: 172.16.68.1]. |
Explanation |
Failed to issue the ACL rule bound to the vPort to the access switch because the access switch does not have sufficient hardware resources. |
Recommended action |
Verify that the access switch has sufficient hardware resources. |
Failure to issue default ACL rule because of insufficient hardware resources
Keyword |
VPORT_DEFAULT_SECURITY_RULE_FAILED |
Message text |
The default ACL rule failed to take effect on vPort [IP: $1,MAC: $2,Tenant ID: $3] because of insufficient hardware resources on device [IP: $4]. |
Variable fields |
$1: IP address of the vPort. $2: MAC address of the vPort. $3: UUID of the tenant to which the vPort belongs. $4: Management IP address of the device. |
Severity level |
Warning |
Example |
The default ACL rule failed to take effect on vPort [IP:4.4.4.4,MAC:00:50:56:95:09:8d,Tenant ID:ffffffff-0000-0000-0000-000000000001] because of insufficient hardware resources on device [IP: 172.16.68.1]. |
Explanation |
Failed to issue the default ACL rule bound to the vPort to the access switch because the access switch does not have sufficient hardware resources. |
Recommended action |
Verify that the access switch has sufficient hardware resources. |
Controller failed to communicate with host through OVSDB
Keyword |
OVSDB_COMMUNICATE_FAILED |
Message text |
Failed to communicate with host $1 through OVSDB. The commands are $2. |
Variable fields |
$1: IP address of the host. $2: Commands that the controller attempted to deploy to the host through OVSDB. |
Severity level |
Warning |
Example |
Failed to communicate with host 172.16.38.60 through OVSDB. The commands are --columns=name find Bridge datapath_id=00000050569a0223. |
Explanation |
The controller failed to communicate with a host through OVSDB. |
Recommended action |
Verify that the virtual switch bridge of the host is running correctly. |
Host IP change
Keyword |
HOST_IP_CHANGED |
Message text |
Host IP changed from $1 to $2. |
Variable fields |
$1: Original IP address of the host. $2: New IP address of the host. |
Severity level |
Warning |
Example |
Host IP changed from 1.1.1.1 to 1.1.1.2. |
Explanation |
The IP address recorded on the controller is different from the actual IP address because the IP address of the host changed. |
Recommended action |
Make sure the IP address specified on the controller for the host is the same as the actual IP address of the host. |
vPort UUID prefix conflict
Keyword |
VPORT_UUID_PREFIX_CONFLICT |
Message text |
Conflict of the UUID's first segment exist on vPorts “$1”, “$2”. |
Variable fields |
$1: Information about vPort 1. $2: Information about vPort 2. |
Severity level |
Warning |
Example |
Conflict of the UUID's first segment exist on vPorts “Name: port1, ID: 5329dda9-353e-4408-a275-c13d99bfc445”, “Name: port2, ID: 5329dda9-353e-4408-a275-c13d99bfc446”. |
Explanation |
Multiple vPorts have the same UUID prefix. |
Recommended action |
Delete either vPort. |
Flow table synchronization or auditing started
Keyword |
HOST_FLOW_SYNC_START |
Message text |
Host $1 started smoothing or auditing flow tables for $2. |
Variable fields |
$1: IP address of the host. $2: Module name. |
Severity level |
Info |
Example |
Host 192.168.10.11 started smoothing or auditing flow tables for vswitch. |
Explanation |
Flow table synchronization or auditing for a service module on the host started. |
Recommended action |
No action is required. |
Flow table synchronization or auditing finished
Keyword |
HOST_FLOW_SYNC_END |
Message text |
Host $1 finished smoothing or auditing flow tables for $2. |
Variable fields |
$1: IP address of the host. $2: Module name. |
Severity level |
Info |
Example |
Host 192.168.101.11 finished smoothing or auditing flow tables for vswitch. |
Explanation |
Flow table synchronization or auditing for a service module on the host finished. |
Recommended action |
No action is required. |
Host flow table issuing failure
Keyword |
HOST_FLOW_MOD_FAILED |
Message text |
Failed to deploy a flow table to host $1. ErrorCode: $2. The flow table is $3. |
Variable fields |
$1: IP address of the host. $2: Error code that OpenFlow returned to the controller. $3: Information about the flow table failed to be issued. |
Severity level |
Warning |
Example |
Failed to deploy a flow table to host 192.168.10.11. ErrorCode: BAD_TIMEOUT. The flow table is { "version":"1.3.0", "flow": { "table_id":0, "priority":100, "idle_timeout":0, "hard_timeout":0, "flow_mod_cmd":"add", "cookie":"0x4234", "cookie_mask":"0xffff", "buffer_id":4294967295, "out_port":265, "out_group":4294967295, "flow_mod_flags":["check_overlap"], "match":[{"eth_type":"ipv4"},{"ipv4_src":"1.1.1.1"}],"instructions":[] } }. |
Explanation |
Failed to issue the flow table to the host. |
Recommended action |
· Verify that the network is operating correctly. · Log in to the host and verify that the OpenFlow settings are correct. |
Host group table issuing failure
Keyword |
HOST_GROUP_MOD_FAILED |
Message text |
Failed to deploy a group table to host $1. ErrorCode: $2. The group table is $3. |
Variable fields |
$1: IP address of the host. $2: Error code that OpenFlow returned to the controller. $3: Information about the group table failed to be issued. |
Severity level |
Warning |
Example |
Failed to deploy a group table to host 192.168.10.11. ErrorCode: BAD_TIMEOUT. The group table is { "version" : "1.3.0", "group" : { "id" : 3, "type" : "all", "command" : "add", "buckets" : [{ "weight" : 0, "watch_group" : 4294967295, "watch_port" : 4294967295, "actions" : [{ "output" : 5 }] }] } }. |
Explanation |
Failed to issue the group table to the host. |
Recommended action |
· Verify that the network is operating correctly. · Log in to the host and verify that the OpenFlow settings are correct. |
Host MTU audit or sync started
Keyword |
HOST_MTU_SYNC_START |
Message text |
Host $1 started smoothing or auditing MTU. |
Variable fields |
$1: IP address of the host. |
Severity level |
Info |
Example |
Host 192.168.10.10 started smoothing or auditing MTU. |
Explanation |
The system started to audit or synchronize MTU information for a host. |
Recommended action |
No action is required. |
Host MTU audit or sync finished
Keyword |
HOST_MTU_SYNC_END |
Message text |
Host $1 finished smoothing or auditing MTU. |
Variable fields |
$1: IP address of the host. |
Severity level |
Info |
Example |
Host 192.168.10.10 finished smoothing or auditing MTU. |
Explanation |
The system finished auditing or synchronizing MTU information for a host. |
Recommended action |
No action is required. |
Network node established WebSocket connection to controller
Keyword |
WEBSOCKET_CONNENT |
Message text |
The network node at IP $1 and the controller established a WebSocket connection with session ID $2. |
Variable fields |
$1: IP address of the network node. $2: Session ID. |
Severity level |
Info |
Example |
The network node at IP 98.0.61.8 and the controller established a WebSocket connection with session ID 6154-as51. |
Explanation |
A network node established a WebSocket connection to the controller. |
Recommended action |
No action is required. |
Network node terminated WebSocket connection to controller
Keyword |
WEBSOCKET_DISCONNENT |
Message text |
The WebSocket connection with session ID $1 between the network node at IP $2 and the controller was disconnected. |
Variable fields |
$1: Session ID. $2: IP address of the network node. |
Severity level |
Warning |
Example |
The WebSocket connection with session ID 6154-as51 between the network node at IP 98.0.61.8 and the controller was disconnected. |
Explanation |
A network node terminated the WebSocket connection to the controller. |
Recommended action |
No action is required. |
DHCP configuration auditing or synchronization started
Keyword |
HOST_DHCP_CONFIG_SYNC_START |
Message text |
Host $1 started smoothing or auditing DHCP configuration. |
Variable fields |
$1: IP address of the host. |
Severity level |
Info |
Example |
Host 98.0.61.8 started smoothing or auditing DHCP configuration. |
Explanation |
DHCP configuration auditing or synchronization for a network node started. |
Recommended action |
No action is required. |
DHCP configuration auditing or synchronization started finished
Keyword |
HOST_DHCP_CONFIG_SYNC_END |
Message text |
Host $1 finished smoothing or auditing DHCP configuration. |
Variable fields |
$1: IP address of the host. |
Severity level |
Info |
Example |
Host 98.0.61.8 finished smoothing or auditing DHCP configuration. |
Explanation |
DHCP configuration auditing or synchronization for a network node finished. |
Recommended action |
No action is required. |