H3C SeerEngine-Campus System Log Messages Reference-E65XX-5W100

HomeSupportResource CenterSDNH3C SeerEngine-CampusH3C SeerEngine-CampusTechnical DocumentsReference GuidesLog Message ReferencesH3C SeerEngine-Campus System Log Messages Reference-E65XX-5W100

 

H3C SeerEngine-Campus

System Log Messages Reference

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Document version: 5W100-20220725

 

Copyright © 2022 New H3C Technologies Co., Ltd. All rights reserved.

No part of this manual may be reproduced or transmitted in any form or by any means without prior written consent of New H3C Technologies Co., Ltd.

Except for the trademarks of New H3C Technologies Co., Ltd., any trademarks that may be mentioned in this document are the property of their respective owners.

The information in this document is subject to change without notice.


Contents

Introduction· 1

Viewing system log messages· 1

Syslog message format 2

Using this document 4

Campus· 5

No access location on authentication server 5

No controller info on authentication server 5

Isolation domain name same as access location name on authentication server 6

Failure to delete isolation domain· 6

Failure to add or edit access location member 7

CON_APP·· 8

Incomplete application package· 8

Application health status change· 8

Application manager module status· 9

CON_LICENSE·· 10

License installation· 10

Single license reclaimed· 10

License server connection· 11

Disconnection from the license server 11

Failure of connection to the license server 12

Controller forced offline by license server 12

Reconnection to the license server 13

Entered fail-safe state due to authorization failure· 13

Entered fail-safe state due to connection failure· 14

Exited fail-safe state after the fail-safe period· 14

Exited fail-safe state after authorization· 15

Exited fail-safe state after disconnection· 15

Remote license expiration pre-warning· 16

Insufficient quantity-based licenses· 16

CON_MONITOR·· 17

CPU usage exceeded threshold· 17

CPU usage dropped below threshold· 17

Memory usage exceeded threshold· 18

Memory usage dropped below threshold· 18

Disk usage exceeded threshold· 19

Disk usage dropped below threshold· 19

PBR configuration fails to take effect 20

AC configuration fails to take effect 22

CON_NETCONF· 24

NETCONF session in up state· 24

NETCONF session in down state· 25

Start of NETCONF configuration recovery on non-active leader controllers· 25

End of NETCONF configuration recovery on non-active leader controllers· 26

NETCONF configuration deployment failure· 27

CON_NetworkMonitor 28

Unhealthy device operating status· 28

Device operating status changes from unhealthy to healthy· 28

CON_OAM·· 30

Periodic radar detection task failure· 30

Periodic radar detection task result changes from failure to success· 31

CON_OPENFLOW··· 32

Abnormal OpenFlow connection· 32

Successful OpenFlow connection· 32

Disconnected OpenFlow connection· 33

OpenFlow port in up state· 33

OpenFlow port in down state· 34

OpenFlow port removed· 34

Failure to deploy flow entries· 35

Packet-in message rate reaches threshold on controller 35

Packet-in message rate reaches threshold on OpenFlow device· 36

Packet-in message rate reaches threshold on OpenFlow device port 36

No available OpenFlow node license· 37

CON_PortMonitor 38

Change of port operating status from healthy to unhealthy· 39

Change of port operating status from unhealthy to healthy· 40

CON_REGION·· 41

Region creation· 41

Region activation· 41

Region update· 42

Region down· 42

Region deletion· 43

Failure to restore region settings· 43

Network device connection to a master 44

Master change for network devices· 44

Network device disconnection from a master 45

OpenFlow device connection with multiple regions· 45

Abnormal status of the other controller in the region· 46

Normal status of the other controller in the region· 46

CON_SNMP·· 47

Traditional NE created SNMP connection with controller 47

Traditional NE broke SNMP connection to controller 47

Traditional NE port up· 48

Traditional NE port down· 48

CON_SYSTEM·· 49

Database operation failure because of a nonexistent user 49

Database operation failure because of refused connections· 50

APP in initializing status· 50

APP in ready status· 51

End of controller configuration recovery· 51

Controller configuration backup not performed when backup file exists· 52

Failed to send the backup file to the remote server 52

Up to six backup files created by using the same backup method at a time· 53

CON_TEAM·· 54

Failure to delete team IP· 54

Controller suspended· 55

Member joined team·· 55

Active leader changed· 56

Controller became active leader 56

Controller became member 57

Member left team unexpectedly· 58

Member left team expectedly· 59

Different team token than the active leader 59

Reboot for completing team merge· 60

Reboot to act as the leader 60

CON_USER·· 61

Login success· 61

Login failure· 61

User lock· 62

Logout success· 62

RADIUS authentication success· 63

RADIUS authentication rejection· 63

RADIUS authentication failure· 63

RADIUS attribute check failure· 64

TACACS+ authentication success· 64

TACACS+ authentication rejection· 65

TACACS+ authentication failure· 65

TACACS+ attribute check failure· 66

Start of user configuration recovery on non-active leader controllers· 66

End of user configuration recovery on non-active leader controllers· 67

Operation failure due to user role privilege limit 67

User password expiration· 68

DHCP·· 69

Start of DHCP configuration recovery on non-active leader controllers· 69

End of DHCP configuration recovery on non-active leader controllers· 69

IDM·· 70

Controller failed to synchronize bridge MAC and serial number information from device· 70

NEM·· 71

Different VRF information than the network device· 71

Different VSI information than the network device· 72

Different tunnel information than the network device· 73

Different ACL information than the network device· 74

Different PBR information than the network device· 74

Different routing information than the network device· 75

Different VLAN information than the network device· 76

Different NAT information than the network device· 77

Different floating IP information than the network device· 78

Different DNS information than the network device· 79

Different host flow information than the network device· 80

Different subinterface information than the network device· 81

Different VLAN interface information than the network device· 82

Network device connection to another region· 83

VXLAN tunnel interface in up state· 83

VXLAN tunnel interface in down state· 84

Failed to add flow table· 85

Used up VLAN IDs in the VLAN pools· 85

VLAN pool not exist 86

Used up VXLAN IDs in the VXLAN pools· 86

Used up IP addresses in general address pool 87

Used up IP addresses in address pool bound to service gateway group· 87

Used up IP addresses in security external network address pool 88

Used up IP addresses in default address pool 88

Address pool bound to service gateway group not exist 89

Failed to assign security external network IP address to resource node· 89

Default address pool not exist 90

Used up loopback interfaces on the firewall bound to the vRouters· 90

Start of NEM configuration recovery on non-active leader controllers· 91

End of NEM configuration recovery on non-active leader controllers· 91

Data synchronization status changed to Not Synchronized· 92

Data synchronization status changed to Synchronized· 92

Configuration initialization failure during NE activation· 93

Maximum number of Ethernet service instances reached on interface· 94

Controller failed to deploy settings to network device· 95

VLAN and PVID inconsistency between member ports and aggregate interface· 96

Mapping is unbound from port when port is added to aggregate interface· 96

Startup configuration file backup success· 97

Startup configuration file backup failure· 97

VTEP IP assignment failure· 98

Software upgrading or patching failure· 98

Software upgrading or patching success· 99

Used up IP addresses in the underlay address pool 99

Device failed to come online automatically· 100

Used up VLAN IDs of downlink port on leaf device· 100

IRF member device was not powered off during replacement 101

CID editing failure· 101

ONU coming online· 102

ONU going offline· 103

AP coming online· 104

AP going offline· 105

ROLT interface member changes· 106

Failure of notifying the EIA server to add, edit, or delete device role information· 106

Failure of notifying the EIA server to update links between leaf and access devices· 107

Device restart success· 107

Device restart failure· 108

Device configuration restoration success· 108

Device configuration restoration failure· 109

ServiceChain· 110

Start of service chain configuration recovery on non-active leader controllers· 110

End of service chain configuration recovery on non-active leader controllers· 110

VSM·· 111

Failure to add host because of invalid license· 111

vPort number reaching threshold· 111

vPort number falling below threshold· 112

Start of VSM configuration recovery on non-active leader controllers· 112

End of VSM configuration recovery on non-active leader controllers· 113

Compute node neighbor aging in 24 hours· 113

LLDP neighbor relationship restoration between compute node host and device· 114

LLDP neighbor relationship establishment between compute node host and device· 114

LLDP neighbor relationship interruption between compute node host and device· 115

Network node neighbor aging in 24 hours· 115

LLDP neighbor relationship restoration between network node host and device· 116

LLDP neighbor relationship establishment between network node host and device· 116

LLDP neighbor relationship interruption between network node host and device· 117

Successful VM migration· 118

Failure to issue ACL rule because of insufficient hardware resources· 119

Failure to issue default ACL rule because of insufficient hardware resources· 120

Controller failed to communicate with host through OVSDB· 120

Host IP change· 121

 


 

Introduction

System logs record internal events that occur on the controller. System log messages include field description, message explanation, and recommended action, and provide reference for system analysis and maintenance.

This document assumes that the readers are familiar with data communications technologies and H3C SeerEngine-Campus controller products.

Viewing system log messages

To view system log messages:

1.     Log in to SNA Center.

2.     Click Settings.

3.     On the top navigation bar, click Logs.

4.     From the navigation pane, select Information.

5.     Click the System Logs tab.

6.     Select SeerEngine-Campus from the SNA Component Name list, and click Query.

7.     The generated SeerEngine-Campus system log messages are displayed as shown in Figure 1.

Figure 1 System log messages

 

 

Table 1 System log message elements

Element

Description

Severity Level

Severity level of the message. For more information about severity levels, see Table 5.

Time

Date and time when the log message was generated.

SNA Component Name

Name of the SNA component that produced the message.

Host Name

Name of the host that produced the message.

Service Name

Name of the service that produced the message.

Module Name

Name of the module that produced the message.

Description

Text string that contains detailed information about the event or error.

 

Syslog message format

SeerEngine-Campus controllers can send system logs to syslog servers through the syslog protocol. To set the IP address and port number of a syslog server:

1.     On the top navigation bar, click Logs.

2.     From the navigation pane, select Configuration.

3.     Click the System Logs tab.

4.     Set the IP addresses and port numbers of syslog servers.

By default, controllers send system logs in the following format:

<PRI>TIMESTAMP Hostname Origin/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 server or virtual machine where the controller that produced the message resides.

Origin

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.

Table 3 Service module list

Service module name

Description

Campus

Campus module.

CON_APP

Application 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.

DHCP

DHCP module.

IDM

IDM module.

NEM

Carrier network module.

ServiceChain

Service chain 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

Critical

Critical condition.

4

Emergency

Emergent condition.

 

Using this document

This document categories system log messages by service module. This document explains messages in tables. Table 6 describes information provided in these tables.

Table 6 Message explanation table contents

Item

Content

Example

Keyword

Summary of the message that facilitates searching or memorizing.

SUCCESS_UPGRADE_DEVICE

Message text

Presents the message description.

Software upgrade or patching succeeded on device $1 at $2.

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: Device name

$2: Device IP

Severity level

Provides the severity level of the message.

Info

Example

Provides a real message example.

Software upgrade or patching succeeded on device01 with IP 192.168.1.1.

Explanation

Explains the message, including the event or error cause.

Software upgrading or patching succeeded.

Recommended action

Provides recommended actions. For informational messages, no action is required.

No action is required.

 


Campus

This section contains campus messages.

No access location on authentication server

Keyword

ACCESS_LOCATION_NOT_EXIST

Message text

The access location does not exist on the authentication server.

Variable fields

None.

Severity level

Warning

Example

The access location does not exist on the authentication server.

Explanation

The controller failed to edit member devices for an access location because the access location does not exist on the authentication server (for example, the access location has  been manually deleted from the authentication server).

Explanation

Smooth the authentication server and try again.

 

No controller info on authentication server

Keyword

NO_CONTROLLER_CONF_ON_AUTHSERVER

Message text

No controller information is configured on the authentication server.

Variable fields

None.

Severity level

Warning

Example

No controller information is configured on the authentication server.

Explanation

Operation failed because the controller information was not configured on the authentication server.

Explanation

Add controller information on the authentication server.

 

Isolation domain name same as access location name on authentication server

Keyword

ISOLATED_DOMAIN_DUPLICATED_ACCESS_LOCATION

Message text

The isolation domain name is the same as an access location name on the authentication server.

Variable fields

None.

Severity level

Warning

Example

The isolation domain name is the same as an access location name on the authentication server.

Explanation

The isolation domain name is the same as an access location domain name on the authentication server.

Explanation

Change the isolation domain name, or delete the access location with the same name from the authentication server.

 

Failure to delete isolation domain

Keyword

DEL_ISOLATION_DOMAIN_FAILED

Message text

Failed to delete the isolation domain because its associated access location has been used in an access scenario on the authentication server.

Variable fields

None.

Severity level

Warning

Example

Failed to delete the isolation domain because its associated access location has been used in an access scenario on the authentication server.

Explanation

Failed to delete an isolation domain because the access location bound to the isolation domain has been used in an access scenario on the authentication server.

Explanation

Unbind the access location from the access scenario on the authentication server.

 

Failure to add or edit access location member

Keyword

MOD_ACCESS_LOCATION_MEMBER_FAILED

Message text

The device was already bound to the access location on the authentication server.

Variable fields

None.

Severity level

Warning

Example

The device was already bound to the access location on the authentication server.

Explanation

Failed to add or edit a member device for the access location because the device has been bound to the access location on the authentication server.

Explanation

Smooth the authentication server and try again.

 

 


CON_APP

This section contains CON_APP messages.

Incomplete application package

Keyword

APP_GETAPPARCHIVE_FAILED

Message text

Application package not found for $1.

Variable fields

$1: Application name.

Severity level

Error

Example

Application package not found for H3C VCFC VSM.

Explanation

The application package is incomplete. For example, the application package does not contain necessary JAR packages, WAR packages, or the description file.

Recommended action

Uninstall the application and then install the complete application package.

 

Application health status change

Keyword

APP_CHANGE_STATUS

Message text

The health status of $1 changed from $2 to $3.

Variable fields

$1: Application name.

$2: Health status of the application before the change.

$3: Health status of the application after the change.

Severity level

Info

Example

The health status of H3C VCFC VSM changed from initial to unhealthy.

Explanation

The application health statuses include initial, healthy, and unhealthy.

This log is generated when the health status of the application changes.

Recommended action

Uninstall and reinstall the application.

 

Application manager module status

Keyword

APP_MANAGER_STATUS

Message text

Application manager module initialization error: Damaged file $1.

Variable fields

$1: Name of the damaged file.

Severity level

Critical

Example

Application manager module initialization error: Damaged file "/opt/sdn/config/ com.h3c.arp.descriptor".

Explanation

An application initialization error has occurred because a relevant file was damaged. The reason for the damage might be a sudden power loss or reboot of the server during the controller upgrade.

Recommended action

1.     Uninstall the abnormal controller without retaining the configuration and then install the controller again.

2.     If the problem persists, contact H3C Support.

 

 


CON_LICENSE

This section contains CON_LICENSE messages.

License installation

Keyword

LICENSE_INSTALL

Message text

$1 license successfully installed.

Variable fields

$1: License name.

Severity level

Info

Example

Base license successfully installed.

Explanation

The specified license was successfully installed.

Recommended action

No action is required.

 

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:

3.     Verify the connectivity between the controller and the license server.

4.     Verify that the license server settings on the controller are correct.

5.     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

6.     Verify that the license server settings on the controller are correct.

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

8.     On the license management page, verify that the controller is connected to the license server.

9.     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

10.     Log in to the license server to verify that the remote license is authorized.

11.     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

Serious

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.

 

 

PBR configuration fails to take effect

Keyword

N/A

Message text

Configuration cannot take effect correctly for {$1}. Reason: {$2 }, Device: Name {$3}, IP {$4}, chassis N/A, slot 2. Details: {$5}

Variable fields

$1Service

$2Reason

$3Device Name

$4Device IP

$5Details

Severity level

Error

Example

Configuration cannot take effect correctly for {service}. Reason: {Error reason }. Device: Name {device-name}, IP {device-ip}, chassis N/A, slot 2. Details: {Detailed information}

·     Service

¡     Gateway {gateway-name}of private network {private-network-name}

¡     Service chain {service-chain-name} of private network {private-network-name}

¡     The default action of private network {private-network-name}

¡     The group policy of security group {group-name}

¡     The default actions of private networks {private-network-name, private-network-name}

¡     The group policies of private networks {private-network-name, private-network-name}

¡     Security group {group-name}and rule {N} in policy template {policy-template-name} of security group {group-name}

¡     Security group {group-name}and rule {N} in policy template {policy-template-name} of IT resource group {group-name}

¡     Security group {group-name} and exception rule {N} in IT resource group {group-name}

¡     The default device settings in group-based policy mode

·     {Error reason }

¡     Insufficient PBR resources.

¡     Not enough resources are available to complete the operation.

·     {device-name}Device Name

·     {device-ip}Device IP

·     {Detailed information}:

¡     Failed to create node {node-number} for PBR policy {policy-name}.

¡     Failed to configure node {node-number} of PBR policy {policy-name} to use ACL {ACL-name} to match traffic.

¡     Failed to configure node {node-number} of PBR policy {policy-name} to use the service chain with path ID {path-ID} and path index {path-index} to match traffic.

¡     Failed to apply output interface {interface-name} to node {node-number} of PBR policy {policy-name}.

¡     Failed to apply the service chain with path ID {path-ID} and path index {path-index} to node {node-number} of PBR policy {policy-name}.

¡     Failed to apply next hop {next-hop-IP-address} in VPN instance {VPN-instance-name} to node {node-number} of PBR policy {policy-name}.

¡     Failed to apply the default next hop {next-hop-IP-address} in VPN instance {VPN-instance-name} to node {node-number} of PBR policy {policy-name}.

¡     Failed to create rule {rule-number} in ACL {ACL-name}.

¡     Failed to apply PBR policy {policy-name} globally.

¡     Failed to apply PBR policy {policy-name} to interface {interface-name}.

¡     Failed to create node {node-number} for IPv6 PBR policy {policy-name}.

¡     Failed to configure node {node-number} of IPv6 PBR policy {policy-name} to use ACL {ACL-name} to match traffic.

¡     Failed to configure node {node-number} of IPv6 PBR policy {policy-name} to use the service chain with path ID {path-ID} and path index {path-index} to match traffic.

¡     Failed to apply output interface {interface-name} to node {node-number} of IPv6 PBR policy {policy-name}.

¡     Failed to apply the service chain with path ID {path-ID} and path index {path-index} to node {node-number} of IPv6 PBR policy {policy-name}.

¡     Failed to apply next hop {next-hop-IP-address} in VPN instance {VPN-instance-name} to node {node-number} of IPv6 PBR policy {policy-name}.

¡     Failed to apply the default next hop {next-hop-IP-address} in VPN instance {VPN-instance-name} to node {node-number} of IPv6 PBR policy {policy-name}.

¡     Failed to create rule {rule-number} in IPv6 ACL {ACL-name}.

¡     Failed to apply IPv6 PBR policy {policy-name} globally.

¡     Failed to apply IPv6 PBR policy {policy-name} to interface {interface-name}.

Explanation

The PBR configuration fails to take effect because of insufficient resources on the device.

Recommended action

·     Verify that the PBR usage threshold is appropriate.

·     Verify that the device does not load too many services. If too many services are loaded, you can transfer some services to other devices in the team.

·     Release resources on the device with proper service planning.

 

AC configuration fails to take effect

Keyword

N/A

Message text

Configuration cannot take effect correctly for {$1}. Reason: {$2 }. Device: Name {$3}, IP {$4}, chassis N/A, slot 2. Details: Configuration cannot take effect correctly for AC {$5} on interface {$6}.

Variable fields

$1Service

$2Reason

$3Device Name

$4Device IP

$5AC Instance Name

$6Interface Name

Severity level

Error

Example

Configuration cannot take effect correctly for {service}. Reason: {Error reason }. Device: Name {device-name}, IP {device-ip}, chassis N/A, slot 2. Details: Configuration cannot take effect correctly for AC {AC-instance-name} on interface {interface-name}.

·     {service}

¡     An unrecognizable service

¡     The auth-free service of security group {group-name}

¡     The WLAN service of security group {group-name}

¡     The static access service of Layer 2 network domain {domain-name}

¡     VLAN-VXLAN mapping table {mapping-table-name}

·     {Error reason }

¡     Insufficient AC resources.

¡     Not enough resources are available to complete the operation.

·     {device-name}Device Name

·      {device-ip}Device IP

·     {AC-instance-name}AC Instance Name

·     {interface-name}Interface Name

Explanation

The AC configuration fails to take effect because of insufficient resources on the device.

Recommended action

·     Verify that the AC usage threshold is appropriate.

·     Verify that the device does not load too many services. If too many services are loaded, you can transfer some services to other devices in the team.

·     Release resources on the device with proper service planning.

 

 

 


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 was up.

Variable fields

$1: IP address of the NETCONF server.

Severity level

Warning

Example

The NETCONF session between the controller and NETCONF server 192.168.41.91 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 was down.

Variable fields

$1: IP address of the NETCONF server.

Severity level

Warning

Example

The NETCONF session between the controller and NETCONF server 192.168.41.91 was down.

Explanation

The NETCONF session between the controller and the NETCONF server was down.

Recommended action

To resolve the problem:

12.     Verify the connectivity between the controller and the NETCONF server.

13.     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.

14.     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.

 

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.

 

 


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 level: $2

Variable fields

$1: IP address of the device.

$2: Health level of the device.

Severity level

Warning

Example

Device operating status changed to unhealthy:

  IP address: 192.168.67.200

  Device health level: 23

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 level: $2

Variable fields

$1: IP address of the device.

$2: Health level of the device.

Severity level

Info

Example

Device operating status changed to healthy:

  IP address: 192.168.67.200

  Device health level: 30

Explanation

This message is generated when the device health level increases above 25.

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 Manager component in Controller > System > Configurations.

 

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

Critical

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

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

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

 

No available OpenFlow node license

Keyword

OPENFLOW_CONNECT_ERROR

Message text

No available license or insufficient node for the OpenFlow connection.

Variable fields

N/A

Severity level

Serious

Example

No available license or insufficient node for the OpenFlow connection.

Explanation

No available license for creating a node.

Recommended action

Purchase an OpenFlow node license.

 

 


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: IP address of the master controller.

$3: Name of the master controller.

Severity level

Info

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 connected to master 192.168.105.21:vcfc1.

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: IP address of the original master to which the network devices are connected.

$3: Name of the original master to which the network devices are connected.

$4: IP address of the new master to which the network devices are connected.

$5: Name 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:a6:81:13:28:01:00  00:05:a6:81:13:28:01:00 was changed from 192.168.105.21:vcfc1 to 192.168.105.20:vcfc2.

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:

15.     Verify that the network is connected.

16.     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

Critical

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

Critical

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

17.     Verify that the other controller in the region started up correctly. If the controller started up correctly, go to the next step.

18.     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.

19.     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.

Traditional NE created SNMP connection with controller

Keyword

SNMP_SESSION_UP

Message text

An SNMP session was created between the traditional NE at $1 and the controller at $2.

Variable fields

$1: IP address of the traditional NE.

$2: IP address of the controller.

Severity level

Info

Example

An SNMP session was created between the traditional NE at 192.168.70.72 and the controller at 192.168.89.155.

Explanation

The traditional NE established an SNMP connection to the controller.

Recommended action

No action is required.

 

Traditional NE broke SNMP connection to controller

Keyword

SNMP_SESSION_DOWN

Message text

The SNMP session between the traditional NE at $1 and the controller at $2 was disconnected.

Variable fields

$1: IP address of the traditional NE.

$2: IP address of the controller.

Severity level

Warning

Example

The SNMP session between the traditional NE at 192.168.70.72 and the controller at 192.168.89.155 was disconnected.

Explanation

The traditional NE 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.

 

Traditional NE port up

Keyword

TRADITIONAL_NE_PORT_UP

Message text

Port $1 of traditional NE at $2 was up.

Variable fields

$1: Name of the traditional NE port.

$2: IP address of the traditional NE.

Severity level

Info

Example

Port FGE1/0/46 of traditional NE at 192.168.89.155 was up.

Explanation

This message is sent when the port of the traditional NE comes up.

Recommended action

No action is required.

 

Traditional NE port down

Keyword

TRADITIONAL_NE_PORT_DOWN

Message text

Port $1 of traditional NE at $2 was down.

Variable fields

$1: Name of the traditional NE port.

$2: IP address of the traditional NE.

Severity level

Warning

Example

Port FGE1/0/46 of traditional NE at 192.168.89.155 was down.

Explanation

This message is sent when the port of the traditional NE goes down.

Recommended action

Verify that the physical status of the traditional NE 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

Critical

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

Critical

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.

 

APP in initializing status

Keyword

SCM_STATUS_INITIATED

Message text

$1 was initializing.

Variable fields

$1: Name of the application.

Severity level

Info

Example

H3C VCFC VPNaaS was initializing.

Explanation

The application was initializing. It is not ready for processing services.

Recommended action

Do not deploy new configuration until the application is ready for processing services.

 

APP in ready status

Keyword

SCM_STATUS_RUNNING

Message text

$1 was ready for processing services.

Variable fields

$1: Name of the application.

Severity level

Info

Example

H3C VCFC VPNaaS was ready for processing services.

Explanation

The application configuration recovery completed. The application is ready for processing services.

Recommended action

No action is required.

 

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

$1, ID: $2, IP: $3, VCFC name: $4, Team name: $5, Team IP: $6.

Variable fields

$1: Team event.

$2: Member controller ID.

$3: Member controller IP address.

$4: Member controller name.

$5: Name of the team.

$6: Team IP address.

Severity level

Warning

Example

BECOME_SUSPENDED, ID:98394757-7760-4262-b71b-7b2dde8af5cd,IP:192.168.37.105, VCFC name: vcfc1, 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

$1, ID: $2, IP: $3, VCFC name: $4, Team name: $5, Team IP: $6.

Variable fields

$1: Team event.

$2: Member controller ID.

$3: Member controller IP address.

$4: Member controller name.

$5: Name of the team.

$6: Team IP address.

Severity level

Info

Example

MEMBER_JOIN, ID:98394757-7760-4262-b71b-7b2dde8af5cd, IP:192.168.37.105, VCFC name: vcfc1, 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

$1, ID: $2, IP: $3, VCFC name: $4, Team name: $5, Team IP: $6.

Variable fields

$1: Team event.

$2: Member controller ID.

$3: Member controller IP address.

$4: Member controller name.

$5: Name of the team.

$6: Team IP address.

Severity level

Warning

Example

MEMBER_TO_LEADER, ID: 98394757-7760-4262-b71b-7b2dde8af5cd, IP: 192.168.37.105, VCFC name: vcfc1, 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

$1, ID: $2, IP: $3, VCFC name: $4, Team name: $5, Team IP: $6.

Variable fields

$1: Team event.

$2: Member controller ID.

$3: Member controller IP address. (This field displays 127.0.0.1 in standalone mode.)

$4: Member controller name. (This field displays Local in standalone mode.)

$5: Name of the team. (This field displays Standalone in standalone mode.)

$6: 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, VCFC name: vcfc1, 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

$1, ID: $2, IP: $3, VCFC name: $4, Team name: $5, Team IP: $6.

Variable fields

$1: Team event.

$2: Member controller ID.

$3: Member controller IP address.

$4: Member controller name.

$5: Name of the team.

$6: Team IP address.

Severity level

Info

Example

BECOME_MEMBER, ID: 98394757-7760-4262-b71b-7b2dde8af5cd, IP: 192.168.37.105, VCFC name: vcfc1, 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 by using any of the following methods:

·     Log in to the controller's GUI, select Controller > Configuration, and click Standalone config.

¡     If the team token is not created, enter the correct value in the Team token config field and click Create.

¡     If the team token has already been created, click Delete to delete the team token. Then enter the correct value in the Team token config field and click Create.

·     Remove the controller from the team and install the controller again. Enter the correct team token during the installation.

 

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

Critical

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

Critical

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:

20.     Check for any incorrect authentication settings, for example, the server IP address and the authentication shared key.

21.     Verify that the controller has been added to the AAA server as an AAA client.

22.     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:

23.     Check for any incorrect authentication settings, for example, the server IP address and the authentication shared key.

24.     Verify that the controller has been added to the AAA server as an AAA client.

25.     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.

·     getGets 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.

 

 


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.

 


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.

 


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.

 

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:

26.     Use the display interface tunnel command to verify the status of the tunnel interface.

27.     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.

28.     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.

 

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.

Explanation

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:

·     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 virtual device management 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:

·     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 virtual device management network 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