H3C VCF Controller System Log Messages Reference-5W217

HomeSupportResource CenterSDNH3C VCF ControllerH3C VCF ControllerTechnical DocumentsReference GuidesLog Message ReferencesH3C VCF Controller System Log Messages Reference-5W217
Download Book

Contents

Introduction· 1

Viewing system log messages· 1

Syslog message format 1

Using this document 3

ARP·· 5

Failure to synchronize ARP bus messages· 5

Start of ARP configuration recovery on non-active leader controllers· 5

End of ARP configuration recovery on non-active leader controllers· 6

Conflict between the VM MAC address and the gateway MAC address or reserved gateway MAC address· 6

CON_APP·· 7

Application health status change· 7

Application manager status· 7

CON_LICENSE·· 8

License installation· 8

Single license reclaimed· 8

Disconnection from the license server 9

License server connection· 9

Controller forced offline by license server 9

Insufficient quantity-based licenses· 10

CON_NETCONF· 11

NETCONF session in up state· 11

NETCONF session in down state· 11

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

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

CON_OPENFLOW··· 13

Abnormal OpenFlow connection· 13

Successful OpenFlow connection· 13

Disconnected OpenFlow connection· 14

OpenFlow port in up state· 14

OpenFlow port in down state· 15

Failure to deploy flow entries· 15

No available OpenFlow node license· 16

OpenFlow port binding failure· 16

CON_REGION·· 17

Region creation· 17

Region activation· 17

Region update· 17

Region down· 18

Region deletion· 18

Failure to restore region settings· 18

Network device connection to a master 19

Master change for network devices· 19

Network device disconnection from a master 20

OpenFlow device connection with multiple regions· 20

Abnormal status of the other controller in the region· 21

Normal status of the other controller in the region· 21

Region port binding failure· 22

CON_SYSTEM·· 23

Database operation failure because of a nonexistent user 23

Database operation failure because of refused connections· 23

Application in initializing state· 24

Application ready· 24

Controller configuration recovery completed· 24

Controller configuration backup started· 25

Controller configuration backup completed· 25

Controller configuration backup not performed when backup file exists· 25

Failed to send the backup file to the remote server 26

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

CON_TEAM·· 27

Failure to configure team IP· 27

Failure to delete team IP· 27

Controller suspended· 28

Member joined team·· 28

Active leader changed· 29

Controller became active leader 29

Controller became member 30

Member left team unexpectedly· 30

Member left team expectedly· 31

Different team token than the active leader 31

Reboot for completing team merge· 32

CON_USER·· 33

Login success· 33

Login failure· 33

User locked· 33

Logout success· 34

RADIUS authentication success· 34

RADIUS authentication rejection· 34

RADIUS authentication failure· 35

RADIUS attribute check failure· 35

TACACS+ authentication success· 35

TACACS+ authentication rejection· 36

TACACS+ authentication failure· 36

TACACS+ attribute check failure· 36

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

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

User privilege check failure· 38

DHCP·· 39

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

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

FWaaS·· 40

Start of firewall configuration recovery on non-active leader controllers· 40

End of firewall configuration recovery on non-active leader controllers· 41

Inconsistent DPI application profile information· 41

Inconsistent IPS policy information· 42

Inconsistent antivirus policy information· 42

DPI engine disabled· 43

LBaaS·· 44

Start of load balancing configuration recovery on non-active leader controllers· 44

End of load balancing configuration recovery on non-active leader controllers· 44

NEM·· 45

Different VRF information than the network device· 45

Different VSI information than the network device· 46

Different tunnel information than the network device· 47

Different ACL information than the network device· 47

Different PBR information than the network device· 48

Different routing information than the network device· 49

Different VLAN information than the network device· 50

Different NAT information than the network device· 50

Different floating IP information than the network device· 51

Different DNS information than the network device· 52

Different host flow information than the network device· 53

Different subinterface information than the network device· 54

Different VLAN interface information than the network device· 55

Network device connection to another region· 55

VXLAN tunnel interface in up state· 56

VXLAN tunnel interface in down state· 56

Failed to add flow table· 57

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

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

Change of network device smooth status to Not Synchronized· 58

Change of network device smooth status to Data Synchronized· 59

Initialization failure during network element activation· 59

NGFWM·· 60

Context creation failure· 60

Context deletion failure· 60

Context creation with NETCONF failure· 61

Context creation with NETCONF success· 61

Start of NGFW manager configuration recovery on non-active leader controllers· 62

End of NGFW manager configuration recovery on non-active leader controllers· 62

ServiceChain· 63

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

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

Tenant 64

Start of tenant configuration recovery on non-active leader controllers· 64

End of tenant configuration recovery on non-active leader controllers· 64

VPNaaS·· 65

Start of IPsec VPN configuration recovery on non-active leader controllers· 65

End of IPsec VPN configuration recovery on non-active leader controllers· 65

VSM·· 66

vPort number reaching threshold· 66

vPort number falling below threshold· 66

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

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

VM migration times reaching the maximum within migration time period· 68

VM going offline because of ARP entry deletion· 69

OVSDB communication failure between controller and host 69


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 VCF controller products.

Viewing system log messages

Select Monitor > System Log to enter system log view. The generated system log messages are displayed on pages as shown in Figure 1.

Figure 1 System log messages

 

Table 1 System log message elements

Element

Description

Severity

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

Time

Date and time when the log message was generated.

IP

IP address of the controller or device.

Origin

Name of the service module that produced the message. For more information about service modules, see Table 3.

Topic

Topic for the log message.

Description

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

 

Syslog message format

VCF controllers can send system logs to syslog servers through the syslog protocol. To set the IP address and port number of a syslog server, select Controller > System > Configurations on the top navigation bar, and then select System Log.

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. For more information about the mappings between system log message severity levels and syslog message severity levels, see Table 6.

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

ARP

ARP module.

CON_APP

Application management module.

CON_LICENSE

License management module.

CON_NETCONF

NETCONF module.

CON_OPENFLOW

OpenFlow module.

CON_REGION

Region module.

CON_SYSTEM

System management module.

CON_TEAM

Team module.

CON_USER

User management module.

DHCP

DHCP module.

FWaaS

Firewall service module.

LBaaS

Load balancing service module.

NEM

Carrier network module.

NGFWM

NGFW manager module.

ServiceChain

Service chain module.

Tenant

Tenant management module.

VPNaaS

IPsec VPN service module.

VSM

Virtual network module.

 

Syslog messages are classified into eight severity levels from 0 to 7. The lower the number, the higher the severity, as shown in Table 4.

Table 4 Syslog message severity levels

Level

Severity

Description

0

Emergency

The system is unusable.

1

Alert

Action must be taken immediately.

2

Critical

Critical condition.

3

Error

Error condition.

4

Warning

Warning condition.

5

Notice

Normal but significant condition.

6

Informational

Informational message.

7

Debug

Debugging message.

 

System log messages are classified into five severity levels from 0 to 4. The higher the number, the higher the severity, as shown in Table 5.

Table 5 System log message severity levels

Level

Icon

Severity

Description

0

alert-info

Info

Information message.

1

Warning

Warning condition.

2

Error

Error condition.

3

Serious

Serious condition.

4

alert-crit

Critical

Critical condition.

 

Table 6 shows the mappings between system log message severity levels and syslog message severity levels.

Table 6 Severity level mappings

System log message severity level

Syslog message severity level

0

6

1

4

2

3

3

2

4

0

 

Using this document

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

Table 7 Message explanation table contents

Item

Content

Example

Keyword

Summary of the message that facilitates searching or memorizing.

OPENFLOW_SESSION_UP

Message text

Presents the message description.

An OpenFlow device with datapath ID $1 OpenFlow IP $2 descriptor $3 was connected to the controller $4.

Variable fields

Briefly describes the variable fields in the order that they appear in the message text.

The variable fields are numbered in the "$Number" form to help you identify their location in the message text.

$1: Datapath ID of the OpenFlow device.

$2: Management IP address of the OpenFlow device.

$3: Description information about the OpenFlow device.

$4: IP address of the controller.

Severity level

Provides the severity level of the message.

alert-info

Example

Provides a real message example.

An OpenFlow device with datapath ID 01:21:cc:3e:5f:09:04:7f OpenFlow IP 192.168.100.1 descriptor 192.168.200.1 was connected to the controller 10.10.10.1.

Explanation

Explains the message, including the event or error cause.

An OpenFlow device was connected to the controller.

Recommended action

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

No action is required.

 


ARP

This section contains ARP messages.

Failure to synchronize ARP bus messages

Keyword

ARP_SYNC_FAILED

Message text

Failed to synchronize arp bus message.

Variable fields

N/A

Severity level

Example

Failed to synchronize arp bus message.

Explanation

The controllers in a team failed to synchronize ARP bus messages.

Recommended action

Verify that the network connections are correct among the controllers.

 

Start of ARP configuration recovery on non-active leader controllers

Keyword

BEGIN_RECOVER_ARP_CONFIG

Message text

All non-active leader controllers started recovering the ARP configuration.

Variable fields

N/A

Severity level

Example

All non-active leader controllers started recovering the ARP configuration.

Explanation

All non-active leader controllers in the team started recovering the ARP configuration.

Recommended action

As a best practice, do not perform any operations on the controllers during the configuration recovery process.

 

End of ARP configuration recovery on non-active leader controllers

Keyword

FINISH_RECOVER_ARP_CONFIG

Message text

All non-active leader controllers completed recovering the ARP configuration.

Variable fields

N/A

Severity level

Example

All non-active leader controllers completed recovering the ARP configuration.

Explanation

All non-active leader controllers in the team completed recovering the ARP configuration.

Recommended action

No action is required.

 

Conflict between the VM MAC address and the gateway MAC address or reserved gateway MAC address

Keyword

ARP_MAC_CONFLICT

Message text

The MAC address of VM (IP: $1, MAC: $2) that connects to interface $3 of access device $4 conflicts with the gateway MAC address or reserved gateway MAC address.

Variable fields

$1: IP address of the VM.

$2: MAC address of the VM.

$3: Name of the access port.

$4: Management IP address of the access device.

Severity level

Example

The MAC address of VM (IP: 2.2.2.1, MAC: 3c:8c:40:4e:dd:46) that connects to interface BAGG2 of access device 172.16.68.4 conflicts with the gateway MAC address or reserved gateway MAC address.

Explanation

The VM MAC address conflicted with the gateway MAC address or the reserved gateway MAC address.

Recommended action

Modify the VM MAC address.

 

 


CON_APP

This section contains CON_APP messages.

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

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

Example

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

Explanation

An initialization error occurred to the application manager because the application file is damaged. The damage might be caused by a sudden power loss or reboot during controller upgrade.

Recommended action

1.     Uninstall the controller without retaining the configuration and reinstall the controller.

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

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

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.

 

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

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:

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

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

3.     Verify that the license server is operating correctly and providing services.

 

License server connection

Keyword

LICENSE_SERVER_CONNECT

Message text

The controller established a connection to the license server.

Variable fields

N/A

Severity level

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.

 

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

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.

 

Insufficient quantity-based licenses

Keyword

LICENSE_INSUFFICIENT

Message text

Insufficient $1 licenses. Please purchase more licenses.

Variable fields

$1: Name of the quantity-based licenses.

Severity level

Example

Insufficient MaxNodeNum licenses. Please purchase more licenses.

Explanation

The number of quantity-based licenses is insufficient.

Recommended action

Purchase more licenses.

 

 


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

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

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:

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

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

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

alert-info

Example

All non-active leader controllers started recovering the NETCONF configuration.

Explanation

Except the active leader, all controllers in the team started recovering the NETCONF configuration, including 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

alert-info

Example

All non-active leader controllers completed recovering the NETCONF configuration.

Explanation

Except the active leader, all controllers in the team completed recovering the NETCONF configuration, including the NETCONF username and password.

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

alert-crit

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. If no description is configured, this field displays three hyphens (---).

$4: IP address of the controller.

Severity level

alert-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. If no description is configured, this field displays three hyphens (---).

$4: IP address of the controller.

Severity level

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

No action is required.

 

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

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

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

 

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

*

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.

 

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

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.

 

OpenFlow port binding failure

Keyword

BIND_ADDRESS_FAILED

Message text

Failed to bind $1 to the openflow.

Variable fields

$1: IP address and port number.

Severity level

Example

Failed to bind 0.0.0.0/0.0.0.0:6633 to the openflow.

Explanation

Failed to bind a port to OpenFlow.

Recommended action

Identify whether another service is using the port.

 

 


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

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

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

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

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

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

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: Collection of the datapath IDs.

$2: IP address of the master controller.

$3: Name of the master controller.

Severity level

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: Collection of the datapath IDs.

$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

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: Collection of the datapath IDs.

$2: IP address of the master controller.

Severity level

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:

1.     Verify that the network is connected.

2.     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 OpenFlow network device.

$2: Name of the region to which the OpenFlow device connects.

$3: Name of the region to which the OpenFlow device connects.

Severity level

alert-crit

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

alert-crit

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

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

2.     Verify that the controller does not quit the team. If the controller quits the team, add the controller to team. If the controller is in the team, go to the next step.

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

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

 

Region port binding failure

Keyword

BIND_ADDRESS_FAILED

Message text

Failed to bind $1 to the region.

Variable fields

$1: IP address and port number.

Severity level

Example

Failed to bind 192.168.100.10:9170 to the region.

Explanation

Failed to bind a port to the region.

Recommended action

Identify whether another service is using the port.

 

 


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

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_SERVICE_DOWN

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

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

Verify that the database is correctly opened.

 

Application in initializing state

Keyword

SCM_STATUS_INITIATED

Message text

$1 was initializing.

Variable fields

$1: Application name.

Severity level

alert-info

Example

H3C VCFC VPNaaS was initializing.

Explanation

The application cannot process any services because it was initializing.

Recommended action

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

 

Application ready

Keyword

SCM_STATUS_RUNNING

Message text

$1 was ready for processing services.

Variable fields

$1: Application name.

Severity level

alert-info

Example

H3C VCFC VPNaaS was ready for processing services.

Explanation

The application completed configuration recovery and was ready for processing services.

Recommended action

No action is required.

 

Controller configuration recovery completed

Keyword

FINISH_RECOVER_CONFIGURATIONS

Message text

Controller configuration recovery completed.

Variable fields

N/A

Severity level

alert-info

Example

Controller configuration recovery completed.

Explanation

Controller configuration recovery was completed.

Recommended action

No action is required.

 

Controller configuration backup started

Keyword

BEGIN_BACKUP_CONFIGURATIONS

Message text

Controller configuration backup started.

Variable fields

N/A

Severity level

alert-info

Example

Controller configuration backup started.

Explanation

Controller configuration backup was started.

Recommended action

Do not change the controller settings during configuration backup.

 

Controller configuration backup completed

Keyword

FINISH_BACKUP_CONFIGURATIONS

Message text

Controller configuration backup completed.

Variable fields

N/A

Severity level

alert-info

Example

Controller configuration backup completed.

Explanation

Controller configuration backup was 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

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

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

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 configure team IP

Keyword

CONFIG_TEAMIP_FAILED

Message text

Failed to configure team IP $1.

Variable fields

$1: Team IP address.

Severity level

alert-crit

Example

Failed to configure team IP 192.168.56.211.

Explanation

The system failed to configure the team IP address on the active leader after an active leader switchover.

Recommended action

Configure the team IP address on the active leader by using the sudo ifconfig <NIC>:<subinterface number> <controller_ip> netmask <network_mask> up command.

 

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

alert-crit

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

alert-info

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

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

alert-info

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

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

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

alert-info

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

1.     Verify that the network is connected.

2.     Verify that the member controller is operating correctly.

 

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

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

alert-crit

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

alert-crit

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.

 


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

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

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

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

alert-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 was locked by the system for failing to log in to the controller for five consecutive times.

Recommended action

·     Wait for 15 minutes or reboot the controller to unlock the user account.

·     Verify that the username and password for login are correct.

 

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

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

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

alert-warn

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

*

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:

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

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

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

alert-warn

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

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

alert-warn

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

alert-warn

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:

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

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

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

alert-warn

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

alert-info

Example

All non-active leader controllers started recovering the user configuration.

Explanation

All non-active leader controllers in the team 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

alert-info

Example

All non-active leader controllers completed recovering the user configuration.

Explanation

All non-active leader controllers in the team completed recovering the user configuration, including the username, password, and role.

Recommended action

No action is required.

 

User privilege check failure

Keyword

PERMISSION_CHECK_FAILED

Message text

Failed to $1 $2. The user role must be administrator.

Variable fields

$1: Request type:

·     post—Creates a resource.

·     put—Updates or creates a resource.

·     delete—Deletes a resource.

$2: Requested resource path.

Severity level

Example

Failed to put /sdn/v2.0/systems/4ff280bd-51c6-4768-9be4-4f9f72b51b77. The user role must be administrator.

Explanation

The administrator privilege is required to send the request.

Recommended action

Use the administrator account to send the request.

 

 


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

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

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.

 


FWaaS

This section contains firewall messages.

Start of firewall configuration recovery on non-active leader controllers

Keyword

BEGIN_RECOVER_FW_CONFIG

Message text

All non-active leader controllers started recovering the firewall configuration.

Variable fields

N/A

Severity level

Example

All non-active leader controllers started recovering the firewall configuration.

Explanation

All non-active leader controllers started recovering the firewall configuration. The configuration to be recovered includes firewalls, firewall policies, and firewall rules.

Recommended action

As a best practice, do not perform any operations on the controllers during the configuration recovery process.

 

End of firewall configuration recovery on non-active leader controllers

Keyword

FINISH_RECOVER_FW_CONFIG

Message text

All non-active leader controllers completed recovering the firewall configuration.

Variable fields

N/A

Severity level

Example

All non-active leader controllers completed recovering the firewall configuration.

Explanation

All non-active leader controllers completed recovering the firewall configuration. The recovered configuration includes firewalls, firewall policies, and firewall rules.

Recommended action

No action is required.

Inconsistent DPI application profile information

Keyword

FW_PROFILEINFO_INCONSISTENT

Message text

The application profile information of the controller was different than the network device:

Application profile name: $1

Management IP: $2

Variable fields

$1: DPI application profile name.

$2: Management IP address of the network device.

Severity level

Example

The application profile information of the controller was different than the network device:

   Application profile name: Profile_VGW7ZJGNOFHVFT4YMQNVNPKEQM

   Management IP: 99.0.10.121

Explanation

The DPI application profile information on the firewall module of the controller was inconsistent with that on the network device.

Recommended action

Terminate the existing connection between the network device and the controller, and then establish a new OpenFlow connection between them.

 

Inconsistent IPS policy information

Keyword

FW_IPSINFO_INCONSISTENT

Message text

The IPS policy information of the controller was different than the network device:

   IPS policy name: $1

   Management IP: $2

Variable fields

$1: IPS policy name.

$2: Management IP address of the network device.

Severity level

Example

The IPS policy information of the controller was different than the network device:

  IPS policy name: ips_sksvwlb2z6zypw3ki3ogrncnt4

  Management IP: 99.0.10.121

Explanation

The IPS policy information on the firewall module of the controller was inconsistent with that on the network device.

Recommended action

Terminate the existing connection between the network device and the controller, and then establish a new OpenFlow connection between them.

 

Inconsistent antivirus policy information

Keyword

FW_AVINFO_INCONSISTENT

Message text

The antivirus policy information of the controller was different than the network device:

  Antivirus policy name: $1

  Management IP: $2

Variable fields

$1: Antivirus policy name.

$2: Management IP address of the network device.

Severity level

Example

The antivirus policy information of the controller was different than the network device:

   Antivirus policy name: AV_WJJ2DVJLPDN7RJTZ24B2CYKH5A

   Management IP: 99.0.10.121

Explanation

The antivirus policy information on the antivirus module of the controller was inconsistent with that on the network device.

Recommended action

Terminate the existing connection between the network device and the controller, and then establish a new OpenFlow connection between them.

 

DPI engine disabled

Keyword

FW_DPI_DOWN

Message text

The DPI function is not enabled on the firewall:

  Management IP: $1

Variable fields

$1: Management IP address of the firewall.

Severity level

Example

The DPI function is not enabled on the firewall:

  Management IP: 192.168.0.10

Explanation

The DPI engine is disabled on the firewall.

Recommended action

Log in to the firewall device, and then execute the inspect activate command to enable the DPI engine.

 

 


LBaaS

This section contains load balancing messages.

Start of load balancing configuration recovery on non-active leader controllers

Keyword

BEGIN_RECOVER_LB_CONFIG

Message text

All non-active leader controllers started recovering the load balancing configuration.

Variable fields

N/A

Severity level

Example

All non-active leader controllers started recovering the load balancing configuration.

Explanation

All non-active leader controllers started recovering the load balancing configuration, including load balancer, server farm, virtual server, and health monitoring information.

Recommended action

As a best practice, do not perform any operations on the controllers during the configuration recovery process.

 

End of load balancing configuration recovery on non-active leader controllers

Keyword

FINISH_RECOVER_LB_CONFIG

Message text

All non-active leader controllers completed recovering the load balancing configuration.

Variable fields

N/A

Severity level

Example

All non-active leader controllers completed recovering the load balancing configuration.

Explanation

All non-active leader controllers completed recovering the load balancing configuration, including load balancer, server farm, virtual server, and health monitoring information.

Recommended action

No action is required.

 


NEM

This section contains carrier network messages.

Different VRF information than the network device

Keyword

NEM_VRFINFO_INCONSISTENT

Message text

The VRF information of the NEM was different than the network device:

   VRF name: $1

   Management IP: $2

Variable fields

$1: VRF name.

$2: Management IP address of the network device.

Severity level

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

Disconnect the network device from the controller and then connect the network device to the controller again.

 

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

   VRF name: $3

   MAC address: $4

   Subnet address: $5

   Management IP: $6

Variable fields

$1: VSI name.

$2: VSI interface name.

$3: VRF name.

$4: MAC address of the VSI interface.

$5: Subnet address and mask.

$6: Management IP address of the network device.

Severity level

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

Disconnect the network device from the controller and then connect the network device to the controller again.

 

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

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

Disconnect the network device from the controller and then connect the network device to the controller again.

 

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

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

Disconnect the network device from the controller and then connect the network device to the controller again.

 

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

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

Disconnect the network device from the controller and then connect the network device to the controller again.

 

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

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

Disconnect the network device from the controller and then connect the network device to the controller again.

 

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

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

Disconnect the network device from the controller and then connect the network device to the controller again.

 

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

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

Disconnect the network device from the controller and then connect the network device to the controller again.

 

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

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

Disconnect the network device from the controller and then connect the network device to the controller again.

 

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

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

Disconnect the network device from the controller and then connect the network device to the controller again.

 

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 destination IP: $1

   Subnet mask: $2

   Matching destination MAC: $3

   VRF number: $4

   VRF name: $5

   Destination VTEP IP: $6

   Destination MAC: $7

   VNI number: $8

   Management IP: $9

Variable fields

$1: Destination IP address in the match fields of the flow entry.

$2: Subnet mask.

$3: Destination 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

Example

The host flow information of the NEM was different than the network device:

   Matching destination IP: 1.1.1.1

   Subnet mask: 255.255.255.0

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

Disconnect the network device from the controller and then connect the network device to the controller again.

 

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

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 for the NEM was different than the network device.

Recommended action

Disconnect the network device from the controller and then connect the network device to the controller again.

 

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

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

Disconnect the network device from the controller and then connect the network device to the controller again.

 

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

alert-info

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

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

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

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.

 

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

N/A

Severity level

Example

All non-active leader controllers started recovering the NEM configuration.

Explanation

All non-active leader controllers started recovering the NEM configuration, including physical NE, gateway group, VNF NE, third party NE, and VLAN-VXLAN mapping information.

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

N/A

Severity level

Example

All non-active leader controllers completed recovering the NEM configuration.

Explanation

All non-active leader controllers completed recovering the NEM configuration, including physical NE, gateway group, VNF NE, third party NE, and VLAN-VXLAN mapping information.

Recommended action

No action is required.

 

Change of network device smooth status to Not Synchronized

Keyword

NEM_SMOOTHSTATUS_CHANGE_NOT_SYNCHRONIZED

Message text

The smooth status of the network device with management IP $1 changed to Not Synchronized.

Variable fields

$1: Management IP of the network device.

Severity level

Example

The smooth status of the network device with management IP 98.0.27.6 changed to Not Synchronized.

Explanation

The smooth status of the network device changed from Data Synchronized to Not Synchronized after it was deactivated and then activated again.

Recommended action

·     No action is required if the features of the network device are not affected.

·     If the features of the network device are affected, click Data synchronization on the Carrier Network > Physical NEs page to synchronize data between the controller and network device.

 

Change of network device smooth status to Data Synchronized

Keyword

NEM_SMOOTHSTATUS_CHANGE_SYNCHRONIZED

Message text

The smooth status of the network device with management IP $1 changed to Data Synchronized.

Variable fields

$1: Management IP of the network device.

Severity level

alert-info

Example

The smooth status of the network device with management IP 98.0.27.6 changed to Data Synchronized.

Explanation

This message is generated in one of the following situations:

·     The smooth status of the network device changed from Not Synchronized to Data Synchronized after it was deactivated and then activated again.

·     The smooth status of the network device changed from Not Synchronized to Data Synchronized after data synchronization was manually triggered for the network device.

Recommended action

No action is required.

 

Initialization failure during network element activation

Keyword

ACTIVE_DEVICE_FAILED

Message text

Failed to initialize the network element.

Variable fields

N/A

Severity level

Example

Failed to initialize the network element.

Explanation

An initialization failure occurred during network element activation.

Recommended action

·     Verify that the network connection is normal.

·     Verify that the memory usage of the device does not reach the threshold.

 

 


NGFWM

This section contains NGFW manager messages.

Context creation failure

Keyword

CREATE_CONTEXT_FAILED

Message text

Failed to create context $1.

Variable fields

$1: Context name.

Severity level

alert-info

Example

Failed to create context Context1.

Explanation

Failed to create a context.

Recommended action

To resolve the problem:

1.     Verify that the network connection between the NGFW manager and device is correct.

2.     Verify that a NETCONF session has been established between the NGFW manager and device.

3.     Verify that the template or context information is consistent with the device configuration. For example, the device interface used by the template or context is not used by other services. If inconsistency exists, change the template or context configuration.

 

Context deletion failure

Keyword

DELETE_CONTEXT_FAILED

Message text

Failed to delete context $1.

Variable fields

$1: Context name.

Severity level

alert-info

Example

Failed to delete context context1.

Explanation

Failed to delete a context.

Recommended action

To resolve the problem:

1.     Verify that the network connection between the NGFW manager and device is correct.

2.     Verify that a NETCONF session has been established between the NGFW manager and device.

 

Context creation with NETCONF failure

Keyword

NETCONF_CREATE_CONTEXT_FAILED

Message text

Failed to use NETCONF to create a context for security engine group $1 on device at $2.

Variable fields

$1: Security engine group ID. The value of null indicates that the device does not have any security engine groups.

$2: Device IP address.

Severity level

alert-info

Example

Failed to use NETCONF to create a context for security engine group 10 on device at 192.168.110.10.

Explanation

Failed to use NETCONF to create a context.

Recommended action

To resolve the problem:

1.     Verify that the network connection between the NGFW manager and device is correct.

2.     Verify that a NETCONF session has been established between the NGFW manager and device.

 

Context creation with NETCONF success

Keyword

NETCONF_CREATE_CONTEXT_SUCCESS

Message text

Used NETCONF to create a context at $1: ID $2; Name $3.

Variable fields

$1: Device IP address.

$2: Context ID.

$3: Context name.

Severity level

alert-info

Example

Used NETCONF to create a context at 192.168.110.10: ID 10; Name Context1.

Explanation

Used NETCONF to create a context successfully.

Recommended action

No action is required.

 

Start of NGFW manager configuration recovery on non-active leader controllers

Keyword

BEGIN_RECOVER_NGFWM_CONFIG

Message text

All non-active leader controllers started recovering the NGFWM configuration.

Variable fields

N/A

Severity level

alert-info

Example

All non-active leader controllers started recovering the NGFWM configuration.

Explanation

All non-active leader controllers started recovering the NGFW manager configuration, including device, resource pool, and context information.

Recommended action

As a best practice, do not perform any operations on the controllers during the configuration recovery process.

 

End of NGFW manager configuration recovery on non-active leader controllers

Keyword

FINISH_RECOVER_NGFWM_CONFIG

Message text

All non-active leader controllers completed recovering the NGFWM configuration.

Variable fields

N/A

Severity level

alert-info

Example

All non-active leader controllers completed recovering the NGFWM configuration.

Explanation

All non-active leader controllers completed recovering the NGFW manager configuration, including device, resource pool, and context information.

Recommended action

No action is required.

 


ServiceChain

This section contains service chain messages.

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

Keyword

BEGIN_RECOVER_SC_CONFIG

Message text

All non-active leader controllers started recovering the service chain configuration.

Variable fields

N/A

Severity level

alert-info

Example

All non-active leader controllers started recovering the service chain configuration.

Explanation

All non-active leader controllers in the team started recovering the service chain configuration, such as settings for service chains and contexts.

Recommended action

As a best practice, do not perform any operations on the controllers during the configuration recovery process.

 

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

Keyword

FINISH_RECOVER_SC_CONFIG

Message text

All non-active leader controllers completed recovering the service chain configuration.

Variable fields

N/A

Severity level

alert-info

Example

All non-active leader controllers completed recovering the service chain configuration.

Explanation

All non-active leader controllers in the team completed recovering the service chain configuration, such as settings for service chains and contexts.

Recommended action

No action is required.

 

 


Tenant

This section contains tenant messages.

Start of tenant configuration recovery on non-active leader controllers

Keyword

BEGIN_RECOVER_TENANT_CONFIG

Message text

All non-active leader controllers started recovering the tenant configuration.

Variable fields

N/A

Severity level

alert-info

Example

All non-active leader controllers started recovering the tenant configuration.

Explanation

All non-active leader controllers in the team started recovering the tenant configuration.

Recommended action

As a best practice, do not perform any operations on the controllers during the configuration recovery process.

 

End of tenant configuration recovery on non-active leader controllers

Keyword

FINISH_RECOVER_TENANT_CONFIG

Message text

All non-active leader controllers completed recovering the tenant configuration.

Variable fields

N/A

Severity level

alert-info

Example

All non-active leader controllers completed recovering the tenant configuration.

Explanation

All non-active leader controllers in the team completed recovering the tenant configuration.

Recommended action

No action is required.

 

 


VPNaaS

This section contains IPsec VPN messages.

Start of IPsec VPN configuration recovery on non-active leader controllers

Keyword

BEGIN_RECOVER_VPNaaS_CONFIG

Message text

All non-active leader controllers started recovering the VPNaaS configuration.

Variable fields

N/A

Severity level

Example

All non-active leader controllers started recovering the VPNaaS configuration.

Explanation

All non-active leader controllers started recovering the IPsec configuration. The IPsec configuration to be recovered includes IKE policies, IPsec policies, VPN services, and IPsec connection information.

Recommended action

As a best practice, do not perform any operations on the controllers during the configuration recovery process.

 

End of IPsec VPN configuration recovery on non-active leader controllers

Keyword

FINISH_RECOVER_VPNaaS_CONFIG

Message text

All non-active leader controllers completed recovering the VPNaaS configuration.

Variable fields

N/A

Severity level

Example

All non-active leader controllers completed recovering the VPNaaS configuration.

Explanation

All non-active leader controllers completed recovering the IPsec configuration. The recovered IPsec configuration includes IKE policies, IPsec policies, VPN services, and IPsec connection information.

Recommended action

No action is required.

 


VSM

This section contains virtual network messages.

vPort number reaching threshold

Keyword

VPORTS_REACH_THRESHOLD

Message text

The number of vPorts [$1] has reached the threshold [$2].

Variable fields

$1: Number of vPorts.

$2: Threshold for the number of vPorts.

Severity level

Example

The number of vPorts [120] has reached the threshold [100].

Explanation

The number of vPorts has reached the threshold.

Recommended action

Increase the vPort number threshold or reduce the number of vPorts.

 

vPort number falling below threshold

Keyword

VPORTS_BELOW_THRESHOLD

Message text

The number of vPorts [$1] has fallen below the threshold [$2].

Variable fields

$1: Number of vPorts.

$2: Threshold for the number of vPorts.

Severity level

Example

The number of vPorts [90] has fallen below the threshold [100].

Explanation

The number of vPorts has fallen below the threshold.

Recommended action

No action is required.

 

Start of VSM configuration recovery on non-active leader controllers

Keyword

BEGIN_RECOVER_VSM_CONFIG

Message text

All non-active leader controllers started recovering the VSM configuration.

Variable fields

N/A

Severity level

Example

All non-active leader controllers started recovering the VSM configuration.

Explanation

All non-active leader controllers started recovering the VSM configuration.

Recommended action

As a best practice, do not perform any operations on the controllers during the configuration recovery process.

 

End of VSM configuration recovery on non-active leader controllers

Keyword

FINISH_RECOVER_VSM_CONFIG

Message text

All non-active leader controllers completed recovering the VSM configuration.

Variable fields

N/A

Severity level

Example

All non-active leader controllers completed recovering the VSM configuration.

Explanation

All non-active leader controllers completed recovering the VSM configuration.

Recommended action

No action is required.

 

VM migration times reaching the maximum within migration time period

Keyword

ARP_MIGRATE_OVERFLOW

Message text

The VM (IP $1, old MAC: $2, new MAC: $3) failed to migrate from the source interface $4 of access device $5 to the destination interface $6 of access device $7. The migration times of the VM have already reached the maximum within the migration time period.

Variable fields

$1: IP address of the VM.

$2: Old MAC address of the VM.

$3: New MAC address of the VM.

$4: Source access interface.

$5: Management IP address of the source access device.

$6: Destination access interface.

$7: Management IP address of the destination access device.

Severity level

Example

The VM (IP 2.2.2.1, old MAC: 00:50:56:95:21:fa, new MAC: 00:50:56:95:0e:16) failed to migrate from the source interface XGE5/0/5:2 of access device 172.16.68.1 to the destination interface XGE1/0/5:4 of access device 172.16.68.2. The migration times of the VM have already reached the maximum within the migration time period.

Explanation

The migration times of the VM reached the maximum within the migration time period.

Recommended action

To resolve the problem:

·     Verity that the VM is not migrated for multiple times.

·     Verify that IP address conflicts do not exist.
The controller will migrate the VM frequently if ARP packets are sent to the controller frequently because of the following IP address conflicts:

?     Same IP address and different MAC addresses.

?     Same IP address and different VLANs.

?     Same IP address and different access interfaces.

?     Same IP address and different access devices.

 

VM going offline because of ARP entry deletion

Keyword

VM_OFFLINE

Message text

VM (IP: $1, MAC: $2, UUID: $3) has gone offline because its ARP entry has been deleted.

Variable fields

$1: IP address of the VM.

$2: MAC address of the VM.

$3: UUID of the VM.

Severity level

Example

VM (IP: 1.1.1.1, MAC: 12:00:00:00:1b:87, UUID: 6926a86b-9c5c-4b96-9739-99c93de118fc) has gone offline because its ARP entry has been deleted.

Explanation

The VM went offline because its ARP entry has been deleted.

Recommended action

To resolve the problem:

·     Verify that the VM is operating correctly.

·     Verify that the access device and VLAN-VXLAN mapping are not deleted.

 

OVSDB communication failure between controller and host

Keyword

OVSDB_COMMUNICATE_FAILED

Message text

Failed to communicate with host $1 through OVSDB. The commands are $2.

Variable fields

$1: IP address of the host.

$2: Commands that the controller failed to issue to the host through OVSDB.

Severity level

Example

Failed to communicate with host 172.16.38.60 through OVSDB. The commands are show.

Explanation

The controller failed to communicate with the host through OVSDB.

Recommended action

Verify that the connection between the vSwitch bridge and the controller is in correct state.