Severity

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

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

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

ARP

ARP module.

BGPM

BGPM module.

CON_LICENSE

License management module.

CON_MONITOR

Operating information module.

CON_NETCONF

NETCONF module.

CON_NetworkMonitor

Network health monitor module.

CON_OAM

OAM module.

CON_OPENFLOW

OpenFlow module.

CON_PortMonitor

Port statistics module.

CON_REGION

Region module.

CON_SNMP

SNMP module.

CON_SYSTEM

System management module.

CON_TEAM

Team module.

CON_USER

User management module.

DHCP

DHCP module.

F5aaS

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

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.

0

Info

Information message.

1

Warning

Warning condition.

2

Error

Error condition.

3

Serious

Serious condition.

4

Critical

Critical condition.

0

6

1

4

2

3

3

2

4

0

Item

Content

Example

Keyword

Summary of the message that facilitates searching or memorizing.

OPENFLOW_SESSION_UP

Message text

Presents the message description.

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

Variable fields

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

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

$1: Datapath ID of the OpenFlow device.

$2: Management IP address of the OpenFlow device.

$3: Description information about the OpenFlow device.

$4: IP address of the controller.

Severity level

Provides the severity level of the message.

Example

Provides a real message example.

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

Explanation

Explains the message, including the event or error cause.

An OpenFlow device was connected to the controller.

Recommended action

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

No action is required.

Keyword

ARP_SYNC_FAILED

Message text

Failed to synchronize arp bus message.

Variable fields

N/A

Severity level

Warning

Example

Failed to synchronize arp bus message.

Explanation

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

Recommended action

Verify that the network connections are correct among the controllers.

Keyword

BEGIN_RECOVER_ARP_CONFIG

Message text

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

Variable fields

N/A

Severity level

Info

Example

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

Explanation

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

Recommended action

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

Keyword

FINISH_RECOVER_ARP_CONFIG

Message text

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

Variable fields

N/A

Severity level

Info

Example

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

Explanation

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

Recommended action

No action is required.

Keyword

ARP_MIGRATE_OVERFLOW

Message text

The VM (IP $1, MAC $2) failed to migrate to interface $3 of access device $4. The migration times of the VM have already reached the maximum within the migration time period.

Variable fields

$1: IP address of the VM.

$2: MAC address of the VM.

$3: Access interface number.

$4: Management IP address of the access device.

Severity level

Warning

Example

The VM (IP 1.1.1.1, MAC 12:00:00:00:1b:87) failed to migrate to interface Ten-GigabitEthernet 1/0/1 of access device 172.16.68.1. The migration times of the VM have already reached the maximum within the migration time period.

Explanation

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

Recommended action

1.     Verify that migration operations for the VM have not reached the upper limit.

2.     Verify that none of the following IP address conflicts occurs. If one of the IP conflicts occurs, ARP packets are generated and frequently delivered to the controller. As a result, the controller will move the VM frequently.

¡     VMs with different MAC address are assigned the same IP address.

¡     VMs in different VLANs are assigned the same IP address.

¡     VMs connected to different access interfaces are assigned the same IP address.

¡     VMs connected to different access devices are assigned the same IP address.

Keyword

ARP_MAC_CONFLICT

Message text

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

Variable fields

$1: IP address of the VM.

$2: MAC address of the VM.

$3: Access port number.

$4: Management IP address of the access device.

Severity level

Warning

Example

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

Explanation

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

Recommended action

Modify the VM MAC address.

Keyword

VBGP_NETCONF_CONFIG_FAILED

Message text

Failed to deploy NETCONF configuration of BGP node $1. ErrorReason: $2. The NETCONF configuration item is $3.

Variable fields

$1: IP address of the BGP node.

$2: NETCONF configuration deployment failure reason.

$3: NETCONF configuration item failed to be deployed.

Severity level

Warning

Example

Failed to deploy NETCONF configuration of BGP node192.168.10.11. ErrorReason: The specified address family doesn't exist. The NETCONF configuration item is <top xmlns="http://www.h3c.com/netconf/config:1.0"> <BGP> <Neighbors> <Neighbor> <Name>bgpins</Name> <VRF></VRF> <Family>9</Family> <SessAF>1</SessAF> <IpAddress>68.0.0.11</IpAddress> <Mask>255</Mask> </Neighbor> </Neighbors> </BGP> </top>.

Explanation

Failed to deploy NETCONF configuration to a vBGP node.

Recommended action

3.     Verify that the controller and the NETCONF server are correct connected.

4.     Verify that the configuration is correct.

Keyword

VBGP_DOUBLE_MASTER

Message text

vBGP cluster $1 has two master nodes: $2 and $3.

Variable fields

$1: vBGP cluster ID.

$2: IP address of the first master node.

$3: IP address of the second master node.

Severity level

Warning

Example

vBGP cluster 1 has two master nodes:192.168.10.11 and 192.168.10.22.

Explanation

Two master nodes exist in a vBGP cluster.

Recommended action

5.     Verify that the vBGP nodes can communicate correctly.

6.     Verify that the vBGP cluster and BGP instance configuration is correct.

Keyword

VBGP_MASTER_BACKUP

Message text

vBGP cluster $1 has restored to master/backup mode. Master node is $2 and backup node is $3.

Variable fields

$1: vBGP cluster ID.

$2: IP address of the master node.

$3: IP address of the backup node.

Severity level

Info

Example

vBGP cluster 1 has restored to master/backup mode. Master node is 192.168.10.11 and backup node is 192.168.10.33.

Explanation

The vBGP cluster restored the master/backup mode.

Recommended action

No action is required.

Keyword

VBGP_PEER_SESSION_STATE

Message text

The state of the session between vBGP node $1 and peer $2 in instance $3 is $4.

Variable fields

$1: Management IP address of the vBGP node.

$2: Peer IP address.

$3: Instance name.

$4: Session state. Options include Idle, Connect, Active, Openset, and Openconfirm.

Severity level

Info

Example

The state of the session between vBGP node 192.168.10.11 and peer 192.168.10.22 in instance A is Active.

Explanation

A vBGP session is being established.

Recommended action

If the vBGP session has not been established within a long period of time, verify the BGP configuration and IP connectivity between the BGP peers.

Keyword

VBGP_PEER_SESSION_STATE_ESTABLISHED

Message text

The state of the session between vBGP node $1 and peer $2 in instance $3 is Established.

Variable fields

$1: Management IP address of the vBGP node.

$2: Peer IP address.

$3: Instance name.

Severity level

Info

Example

The state of the session between vBGP node 192.168.10.11 and peer 192.168.10.22 in instance A is Established.

Explanation

A vBGP session was successfully established.

Recommended action

No action is required.

Keyword

LICENSE_INSTALL

Message text

$1 license successfully obtained.

Variable fields

$1: License name.

Severity level

Info

Example

Base license successfully obtained.

Explanation

The specified license was successfully obtained.

Recommended action

No action is required.

Keyword

LICENSE_INSTALL_FAILED

Message text

Failed to obtain the $1 license.

Variable fields

$1: License name.

Severity level

Info

Example

Failed to obtain the base license.

Explanation

Failed to obtain the specified license.

Recommended action

Identify whether the license server has enough licenses.

Keyword

LICENSE_RECLAIM

Message text

License for feature $1 (count: $2) has been reclaimed.

Variable fields

$1: Feature name.

$2: Capacity of the reclaimed license. This field is displayed only when a quantity-based license is reclaimed.

Severity level

Warning

Example

License for feature VirtualServiceNode (count: 100) has been reclaimed.

Explanation

The license for the specified feature was reclaimed.

Recommended action

No action is required.

Keyword

LICENSE_SERVER_CONNECT

Message text

The controller established a connection to the license server.

Variable fields

N/A

Severity level

Info

Example

The controller established a connection to the license server.

Explanation

The controller established a connection to the license server.

Recommended action

No action is required.

Keyword

LICENSE_SERVER_DISCONNECT

Message text

The controller was disconnected from the license server.

Variable fields

N/A

Severity level

Warning

Example

The controller was disconnected from the license server.

Explanation

The controller was disconnected from the license server.

Recommended action

If you disconnect the controller from the license server, no action is required. If the disconnection is unexpected, follow these steps:

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

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

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

Keyword

LICENSE_SERVER_CONNECT_FAILED

Message text

Failed to connect to the license server.

Variable fields

N/A

Severity level

Warning

Example

Failed to connect to the license server.

Explanation

The controller failed to connect to the license server.

Recommended action

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

11.     Verify that the license server is operating correctly.

Keyword

LICENSE_SERVER_FORCE_CLIENT_OFFLINE

Message text

The controller was forced offline by license server.

Variable fields

N/A

Severity level

Warning

Example

The controller was forced offline by license server.

Explanation

The license server forced the controller to go offline.

Recommended action

Reconnect the controller to the license server if you want to authorize the controller again.

Keyword

LICENSE_SERVER_AGED_RECONNECT

Message text

The controller started to reconnect to the license server because the token of the controller aged out.

Variable fields

N/A

Severity level

Warning

Example

The controller started to reconnect to the license server because the token of the controller aged out.

Explanation

The token of the controller aged out and the controller started to reconnect to the license server.

Recommended action

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

Keyword

ENTER_FAILSAFE_NO_LICENSE

Message text

The controller entered into fail-safe mode because it failed to obtain licenses from the remote license server.

Variable fields

N/A

Severity level

Warning

Example

The controller entered into fail-safe mode because it failed to obtain licenses from the remote license server.

Explanation

After the controller connected to the license server, the controller failed to obtain a license and entered fail-safe state.

Recommended action

Log in to the license server and verify that a license is available for the controller.

Keyword

ENTER_FAILSAFE_CONNECT_FAILED

Message text

The controller entered into fail-safe mode because a connection error occurred between the controller and the license server.

Variable fields

N/A

Severity level

Warning

Example

The controller entered into fail-safe mode because a connection error occurred between the controller and the license server.

Explanation

The controller lost its connection to the license server and entered fail-safe state.

Recommended action

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

Keyword

EXIT_FAILSAFE_EXPIRED

Message text

The controller exited from fail-safe mode because the 30-day fail-safe period expired.

Variable fields

N/A

Severity level

Warning

Example

The controller exited from fail-safe mode because the 30-day fail-safe period expired.

Explanation

The 30-day fail-safe period expired and the controller exited fail-safe state.

Recommended action

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

13.     Verify that the license server can assign a license to the controller.

Keyword

EXIT_FAILSAFE_OBTAINED

Message text

The controller exited from fail-safe mode because it had obtained licenses from the license server.

Variable fields

N/A

Severity level

Warning

Example

The controller exited from fail-safe mode because it had obtained licenses from the license server.

Explanation

The controller obtained a license and exited fail-safe state.

Recommended action

No action is required.

Keyword

EXIT_FAILSAFE_DISCONNECTED

Message text

The controller exited from fail-safe mode because it disconnected from the license server.

Variable fields

N/A

Severity level

Warning

Example

The controller exited from fail-safe mode because it disconnected from the license server.

Explanation

The controller closed its connection to the license server and exited fail-safe state.

Recommended action

No action is required.

Keyword

LICENSE_EXPIRED

Message text

$1 license is about to expire in 10 days.

Variable fields

$1: Remote license name.

Severity level

Warning

Example

Base license is about to expire in 10 days.

Explanation

The specified remote license is about to expire in 10 days.

Recommended action

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

15.     If the remote license is not authorized, purchase the license.

Keyword

LICENSE_INSUFFICIENT

Message text

Insufficient $1 licenses. Please purchase more licenses.

Variable fields

$1: Name of the quantity-based licenses.

Severity level

Critical

Example

Insufficient MaxNodeNum licenses. Please purchase more licenses.

Explanation

The number of quantity-based licenses is insufficient.

Recommended action

Purchase more licenses.

Keyword

CPU_USAGE_EXCEED_THRESHOLD

Message text

CPU usage $1 exceeded the threshold $2.

Variable fields

$1: Current CPU usage.

$2: CPU usage threshold.

Severity level

Warning

Example

CPU usage 91% exceeded the threshold 90%.

Explanation

The CPU usage of the system exceeded the threshold.

Recommended action

·     Verify that the CPU usage threshold is appropriate.

·     Verify that the controller does not load too many services. If too many services are loaded, you can transfer some services to other controllers in the team or increase the CPU resources of the physical server.

Keyword

CPU_USAGE_UNDER_THRESHOLD

Message text

CPU usage $1 dropped below the threshold $2.

Variable fields

$1: Current CPU usage.

$2: CPU usage threshold.

Severity level

Info

Example

CPU usage 80% dropped below the threshold 90%.

Explanation

The CPU usage of the system dropped below the threshold.

Recommended action

No action is required.

Keyword

MEMORY_USAGE_EXCEED_THRESHOLD

Message text

Memory usage $1 exceeded the threshold $2.

Variable fields

$1: Current memory usage.

$2: Memory usage threshold.

Severity level

Warning

Example

Memory usage 91% exceeded the threshold 90%.

Explanation

The memory usage of the system exceeded the threshold.

Recommended action

·     Verify that the memory usage threshold is appropriate.

·     Verify that the controller does not load too many services. If too many services are loaded, you can transfer some services to other controllers in the team or increase the memory resources of the physical server.

Keyword

MEMORY_USAGE_UNDER_THRESHOLD

Message text

Memory usage $1 dropped below the threshold $2.

Variable fields

$1: Current memory usage.

$2: Memory usage threshold.

Severity level

Info

Example

Memory usage 80% dropped below the threshold 90%.

Explanation

The memory usage of the system dropped below the threshold.

Recommended action

No action is required.

Keyword

DISK_USAGE_EXCEED_THRESHOLD

Message text

Disk usage $1 exceeded the threshold $2.

Variable fields

$1: Current disk usage.

$2: Disk usage threshold.

Severity level

Warning

Example

Disk usage 91% exceeded the threshold 90%.

Explanation

The disk usage of the system exceeded the threshold.

Recommended action

·     Verify that the disk usage threshold is appropriate.

·     Delete unneeded files, export service-irrelevant files to other devices, or increase the disk space of the physical server.

Keyword

DISK_USAGE_UNDER_THRESHOLD

Message text

Disk usage $1 dropped below the threshold $2.

Variable fields

$1: Current disk usage.

$2: Disk usage threshold.

Severity level

Info

Example

Disk usage 80% dropped below the threshold 90%.

Explanation

The disk usage of the system dropped below the threshold.

Recommended action

No action is required.

Message text

·     The NETCONF session between the controller and NETCONF server $1 $2 was up.

·     The https NETCONF session between the controller and NETCONF server $1 was up.

Variable fields

$1: IP address of the NETCONF server.

$2: Application name.

Severity level

Warning

Example

·     The NETCONF session between the controller and NETCONF server 98.0.50.10 sdn.fabric.monitor was up.

·     The https NETCONF session between the controller and NETCONF server 98.0.50.10 was up.

Explanation

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

Recommended action

No action is required.

Message text

·     The NETCONF session between the controller and NETCONF server $1 $2 was down.

·     The https NETCONF session between the controller and NETCONF server $1 was down.

Variable fields

$1: IP address of the NETCONF server.

$2: Application name.

Severity level

Warning

Example

·     The NETCONF session between the controller and NETCONF server 98.0.50.10 sdn.fabric.monitor was down.

·     The https NETCONF session between the controller and NETCONF server 98.0.50.10 was down.

Explanation

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

Recommended action

To resolve the problem:

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

17.     Examine whether the controller and the NETCONF server have the same NETCONF settings. If the controller and the NETCONF server have different NETCONF settings, modify the NETCONF settings on the controller or the NETCONF server.

18.     Examine whether the maximum number of NETCONF sessions on the NETCONF server is reached. If the maximum number of NETCONF sessions is reached, delete unnecessary sessions or modify the upper limit of NETCONF sessions on the NETCONF server.

Message text

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

Variable fields

N/A

Severity level

Info

Example

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

Explanation

All non-active leader controllers started recovering the NETCONF configuration, such as the NETCONF username and password.

Recommended action

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

Message text

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

Variable fields

N/A

Severity level

Info

Example

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

Explanation

All non-active leader controllers completed recovering the NETCONF configuration, such as the NETCONF username and password.

Recommended action

No action is required.

Message text

$1

Variable fields

$1: Error packet sent from the NETCONF server.

Severity level

Warning

Example

<env:Envelope xmlns:env="http://www.w3.org/2003/05/soap-envelope">

<env:Body>

  <env:Fault>

    <env:Code>

      <env:Value>env:Sender</env:Value>

    </env:Code>

    <env:Reason>

      <env:Text lang=\"en\">Failed to log in.</env:Text>

    </env:Reason>

  </env:Fault>

</env:Body>

Explanation

When the controller fails to deploy the NETCONF configuration to the NETCONF server, the NETCONF server returns an error packet to the controller. Only part of the content in the error packet is displayed in the log because the error packet is too large.

Recommended action

In this example, the configuration deployment failure is caused by controller login failure. To resolve this problem, verify that the controller uses the same NETCONF username and password as the NETCONF server.

In other situations, take actions based on the content of the error packet or contact H3C Support.

Message text

Failed to create the NETCONF over SSH session between the controller and NETCONF server $1 $2. $3

Variable fields

$1: NETCONF server IP address.

$2: Application name.

$3: Session creation failure reason.

Severity level

Warning

Example

Failed to create the NETCONF over SSH session between the controller and NETCONF server 98.0.50.10 sdn.fabric.monitor. Reason: Authentication failed.

Explanation

Failed to create a NETCONF SSH session between the controller and the NETCONF server.

Recommended action

·     Verify that the NETCONF username and password are correctly configured.

·     Verify that the network is operating correctly.

Message text

Device operating status changed to unhealthy:

  IP address: $1

  Device health level: $2

Variable fields

$1: IP address of the device.

$2: Health level of the device.

Severity level

Warning

Example

Device operating status changed to unhealthy:

  IP address: 192.168.67.200

  Device health level: 23

Explanation

This message is generated when the device health level is equal to or lower than 25.

Recommended action

Determine whether to handle the issue as required.

Message text

Device operating status changed to healthy:

  IP address: $1

  Device health level: $2

Variable fields

$1: IP address of the device.

$2: Health level of the device.

Severity level

Info

Example

Device operating status changed to healthy:

  IP address: 192.168.67.200

  Device health level: 30

Explanation

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

Recommended action

No action is required.

Message text

Periodic radar detection task failed: $1

Variable fields

$1: Periodic radar detection task parameters.

Severity level

Warning

Example

Periodic radar detection task failed:

  Path type: single

  Network type: vxlan

  Segment ID: 2

  Source IP: 172.71.1.5

  Start device IP: 192.168.106.3

  Start device ingress port: ---

  Destination IP: 172.172.1.2

  End device IP: ---

Explanation

A periodic radar detection task might contain one or more scanning tasks. This message is generated when a scanning task fails.

Recommended action

If the failure is caused by active leader switchover, perform the periodic radar detection task again after the switchover.

If the failure is caused by other reasons, perform the following operations:

·     Verify that the start device is not faulty and the start device ingress port operates correctly.

·     Verify that the sending of LLDP packets to the controller is enabled. If the feature is disabled, enable it in the Link component by navigating to System > Parameters.

Message text

Periodic radar detection task result changed from failure to success: $1

Variable fields

$1: Periodic radar detection task parameters.

Severity level

Info

Example

Periodic radar detection task result changed from failure to success:

   Path type: single

   Network type: vxlan

   Segment ID: 2

   Source IP: 172.71.1.5

   Start device IP: 192.168.106.3

   Start device ingress port: XGE2/0/1

   Destination IP: 172.172.1.2

   End device IP: 192.168.70.68

Explanation

A periodic radar detection task might contain one or more scanning tasks. This message is generated when the previous scanning task fails but the current task succeeds.

Recommended action

No action is required.

Keyword

KEYSTORE_WILL_EXPIRE

Message text

The controller certificate for southbound communication with subject "$1" will expire in $2 days.

Variable fields

$1: Certificate subject.

$2: Remaining lifetime of the certificate.

Severity level

Warning

Example

The controller certificate for southbound communication with subject " C=CN, ST=ZheJiang, L=Hangzhou, O=Hangzhou H3C Technologies Co., Ltd., CN=*.h3c.com" will expire in 20 days.

Explanation

The remaining lifetime of the Keystore certificate decreased below the expiration early warning threshold.

Recommended action

Update the KeyStore in time.

Keyword

KEYSTORE_EXPIRED

Message text

The controller certificate for southbound communication with subject "$1" expired.

Variable fields

$1: Certificate subject.

Severity level

Warning

Example

The controller certificate for southbound communication with subject " C=CN, ST=ZheJiang, L=Hangzhou, O=Hangzhou H3C Technologies Co., Ltd., CN=*.h3c.com" expired.

Explanation

The Keystore certificate expired.

Recommended action

Update the KeyStore in time.

Message text

Port operating status changed to unhealthy:

  Device IP address: $1

  Port name: $2

  Inbound bandwidth usage: $3

  Outbound bandwidth usage: $4

  Inbound error packet rate: $5

  Outbound error packet rate: $6

  Inbound packet loss rate: $7

  Outbound packet loss rate: $8

Variable fields

$1: IP address of the device.

$2: Port name.

$3: Inbound bandwidth usage.

$4: Outbound bandwidth usage.

$5: Inbound error packet rate.

$6: Outbound error packet rate.

$7: Inbound packet loss rate.

$8: Outbound packet loss rate.

Severity level

Warning

Example

Port operating status changed to unhealthy:

  Device IP address: 172.16.100.222

  Port name: G1/0/1

  Inbound bandwidth usage: 10%

  Outbound bandwidth usage: 10%

  Inbound error packet rate: 10%

  Outbound error packet rate: 10%

  Inbound packet loss rate: 10%

  Outbound packet loss rate: 10%

Explanation

This message is generated when the port operating status changes to unhealthy. The status change can be caused by the following threshold exceeding events:

·     The bandwidth usage exceeds the threshold.

·     The error packet rate exceeds the threshold.

·     The packet loss rate exceeds the threshold.

Recommended action

Take actions based on the causes

Message text

Port operating status changed from unhealthy to healthy:

  Device IP address: $1

  Port name: $2

  Inbound bandwidth usage: $3

  Outbound bandwidth usage: $4

  Inbound error packet rate: $5

  Outbound error packet rate: $6

  Inbound packet loss rate: $7

  Outbound packet loss rate: $8

Variable fields

$1: IP address of the device.

$2: Port name.

$3: Inbound bandwidth usage.

$4: Outbound bandwidth usage.

$5: Inbound error packet rate.

$6: Outbound error packet rate.

$7: Inbound packet loss rate.

$8: Outbound packet loss rate.

Severity level

Info

Example

Port operating status changed from unhealthy to healthy:

  Device IP address: 192.168.70.68

  Port name: XGE1/0/5

  Inbound bandwidth usage: 10%

  Outbound bandwidth usage: 20%

  Inbound error packet rate: 1%

  Outbound error packet rate: 1%

  Inbound packet loss rate: 0%

  Outbound packet loss rate: 0%

Explanation

This message is generated when the port operating status changes from unhealthy to healthy.

Recommended action

No action is required.

Message text

REGION_ADDED : ID: $1

Variable fields

$1: Region ID.

Severity level

Info

Example

REGION_ADDED:ID:Id[value=8aeffbea-7fce-457b-a753-8c228d72c24f]

Explanation

A region was created.

Recommended action

No action is required.

Message text

REGION_ACTIVE : ID: $1

Variable fields

$1: Region ID.

Severity level

Info

Example

REGION_ACTIVE:ID:Id[value=8aeffbea-7fce-457b-a753-8c228d72c24f]

Explanation

A minimum of one member in the region was activated.

Recommended action

No action is required.

Message text

REGION_UPDATED : ID: $1

Variable fields

$1: Region ID.

Severity level

Info

Example

REGION_UPDATED:ID:Id[value=8aeffbea-7fce-457b-a753-8c228d72c24f]

Explanation

A region was updated.

Recommended action

No action is required.

Message text

REGION_DOWN : ID: $1

Variable fields

$1: Region ID.

Severity level

Info

Example

REGION_DOWN:ID:Id[value=8aeffbea-7fce-457b-a753-8c228d72c24f]

Explanation

The region was down because all controllers left the region or the region was deleted.

Recommended action

No action is required.

Message text

REGION_DELETED: ID:  $1

Variable fields

$1: Region ID.

Severity level

Info

Example

REGION_DELETED:ID:Id[value=8aeffbea-7fce-457b-a753-8c228d72c24f]

Explanation

A region was deleted.

Recommended action

No action is required.

Message text

Failed to restore all region settings because of inconsistent data format. All regions were automatically deleted.

Variable fields

N/A

Severity level

Error

Example

Failed to restore all region settings because of inconsistent data format. All regions were automatically deleted.

Explanation

All region settings failed to be restored because of inconsistent data format and all regions were automatically deleted. The message might appear when software upgrade is done on a controller and the current software version is incompatible with the previous software version.

Recommended action

Log in to the active leader and create regions again.

Message text

The network devices with datapath ID collection $1 were connected to master $2/$3.

Variable fields

$1: Datapath IDs of the network devices.

$2: Name of the master controller.

$3: IP address of the master controller.

Severity level

Info

Example

The network devices with datapath ID collection 00:01:28:ec:6e:4a:02:00 were connected to master 3/F001:0:0:0:1000:1000:1000:1004.

Explanation

The network devices with the specified datapath IDs were connected to a master.

Recommended action

No action is required.

Message text

The master of the network devices with datapath ID collection $1 was changed from $2/$3 to $4/$5.

Variable fields

$1: Datapath IDs of the network devices.

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

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

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

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

Severity level

Warning

Example

The master of the network devices with datapath ID collection 00:01:28:ec:6e:4a:02:00 was changed from 3/F001:0:0:0:1000:1000:1000:1004 to 2/F001:0:0:0:1000:1000:1000:1003.

Explanation

The master for the network devices with the specified datapath IDs was changed.

Recommended action

No action is required.

Message text

The network devices with datapath ID collection $1 were disconnected from the master $2.

Variable fields

$1: Datapath IDs of the network devices.

$2: IP address of the master controller.

Severity level

Warning

Example

The network devices with datapath ID collection 00:01:a6:81:13:28:01:00 00:05:a6:81:13:28:01:00 were disconnected from the master 192.168.105.21.

Explanation

The network devices with the specified datapath IDs were disconnected from a master.

Recommended action

Examine whether the disconnection is abnormal. If the disconnection is abnormal, perform the following steps:

19.     Verify that the network is connected.

20.     Configure the controller to issue the region configuration again.

Message text

The network device with datapath ID $1 has joined region $2 and region $3

Variable fields

$1: Datapath ID of the network device.

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

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

Severity level

Emergency

Example

The network device with datapath ID 0c:6f:74:25:8a:c4:e3:a1 has joined region A and region B

Explanation

The OpenFlow device was connected to multiple controllers in different regions.

Recommended action

Disconnect the OpenFlow device from all controllers and then connect the OpenFlow device to controllers in the same region.

Message text

The connection between the current controller and controller $1 in the region is abnormal.

Variable fields

$1: IP address of the other controller in the current region.

Severity level

Emergency

Example

The connection between the current controller and controller 192.168.105.33 in the region is abnormal.

Explanation

The status of the other controller in the current region is abnormal.

Recommended action

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

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

23.     Reboot the controller or contact H3C Support because the handshake module of the controller might be abnormal.

Message text

The connection between the current controller and controller $1 in the region is normal.

Variable fields

$1: IP address of the other controller in the region.

Severity level

Info

Example

The connection between the current controller and controller 192.168.105.33 in the region is normal.

Explanation

The status of the other controller in the current region is normal.

Recommended action

No action is required.

Keyword

SNMP_SESSION_UP

Message text

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

Variable fields

$1: IP address of the traditional NE.

$2: IP address of the controller.

Severity level

Info

Example

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

Explanation

The traditional NE established an SNMP connection to the controller.

Recommended action

No action is required.

Keyword

SNMP_SESSION_DOWN

Message text

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

Variable fields

$1: IP address of the traditional NE.

$2: IP address of the controller.

Severity level

Warning

Example

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

Explanation

The traditional NE broke the SNMP connection to the controller.

Recommended action

Verify that the disconnection is normal. If the disconnection is abnormal, check the connectivity of the network.

Keyword

TRADITIONAL_NE_PORT_UP

Message text

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

Variable fields

$1: Name of the traditional NE port.

$2: IP address of the traditional NE.

Severity level

Info

Example

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

Explanation

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

Recommended action

No action is required.

Keyword

TRADITIONAL_NE_PORT_DOWN

Message text

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

Variable fields

$1: Name of the traditional NE port.

$2: IP address of the traditional NE.

Severity level

Warning

Example

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

Explanation

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

Recommended action

Verify that the physical status of the traditional NE port is correct.

Keyword

DATABASE_NO_USER

Message text

Database operation failed because the user did not exist.

Variable fields

N/A

Severity level

Emergency

Example

Database operation failed because the user did not exist.

Explanation

The database operation failed because the user did not exist.

Recommended action

Verify that the user is configured in the database.

Keyword

DATABASE_CONNECTION_FAILED

Message text

Database operation failed because the database sdndb rejected the connection request from the controller $1.

Variable fields

$1: IP address of the controller.

Severity level

Emergency

Example

Database operation failed because the database sdndb rejected the connection request from the controller 10.10.10.10.

Explanation

The database operation failed because the connection to the database was refused as a result of abnormal database shutdown and so on.

Recommended action

Use the service postgresql status command to verify that the database is in active (running) status.

Use the netstat -antp | grep 5432 command to verify that the port of the database is not occupied by other processes.

Keyword

FINISH_RECOVER_CONFIGURATIONS

Message text

Controller configuration recovery completed.

Variable fields

N/A

Severity level

Info

Example

Controller configuration recovery completed.

Explanation

Controller configuration recovery completed.

Recommended action

No action is required.

Keyword

BACKUP_CONFIGURATIONS_EXIST

Message text

The configuration file already exists.

Variable fields

N/A

Severity level

Info

Example

The configuration file already exists.

Explanation

Configuration backup is not performed when both of the following conditions exist:

·     The non-active leader controllers in the team are consecutively rebooted at least twice before the configuration recovery is completed.

·     A backup configuration file already exists on each non-active leader controller.

Recommended action

Do not consecutively reboot the non-active leader controllers in the team before the configuration recovery is completed.

Keyword

BACKUP_FILE_SEND_FAILED

Message text

Failed to send the backup file to the remote server.

Variable fields

N/A

Severity level

Warning

Example

Failed to send the backup file to the remote server.

Explanation

Failed to send the backup file to the remote file server.

Recommended action

·     Verify that the remote server IP address, username, and password in the remote backup settings are correct.

·     Verify that the connection between the controller and remote server is normal.

·     Verify that the username in the remote backup settings has read and write permission to the specified FTP path.

Keyword

BACKUP_REACH_SIX_SAMETIME

Message text

The system stopped backing up the configuration because up to six backup files have been created by using the same method at a time.

Variable fields

N/A

Severity level

Warning

Example

The system stopped backing up the configuration because up to six backup files have been created by using the same method at a time.

Explanation

Typically, backup files are named in the format of backup time_controller version_backup method, for example, #20161121204142_D2011P07_M. When multiple backup files are created by using the same method at a time, the system names the backup files in another format to prevent duplicate file names. All backup files except the first one are named in the format of backup time_controller version_backup method_n. When n is greater than 5, the system generates this log and stops the current backup operation.

Recommended action

Do not perform multiple backup operations at a time on a controller.

Keyword

DELETE_TEAMIP_FAILED

Message text

Failed to delete team IP $1.

Variable fields

$1: Team IP address.

Severity level

Warning

Example

Failed to delete team IP 192.168.56.211.

Explanation

The system failed to delete the team IP address from the original active leader. The message appears in any of the following situations:

·     The team is deleted.

·     An active leader switchover occurs.

Recommended action

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

Keyword

BECOME_SUSPENDED

Message text

BECOME_SUSPENDED, ID: $1, IP: $2, Name: $3, Team name: $4, Team IP: $5.

Variable fields

$1: Member controller ID.

$2: Member controller IP address.

$3: Member controller name.

$4: Name of the team.

$5: Team IP address.

Severity level

Warning

Example

BECOME_SUSPENDED, ID:98394757-7760-4262-b71b-7b2dde8af5cd,IP:192.168.37.105, Name: controller1, Team name: ZOK, Team IP: 192.168.37.36.

Explanation

The controller was suspended. It was disconnected from other controllers in the team and stopped receiving new services.

Recommended action

No action is required.

Keyword

MEMBER_JOIN

Message text

MEMBER_JOIN, ID: $1, IP: $2, Name: $3, Team name: $4, Team IP: $5.

Variable fields

$1: Member controller ID.

$2: Member controller IP address.

$3: Member controller name.

$4: Name of the team.

$5: Team IP address.

Severity level

Info

Example

MEMBER_JOIN, ID:98394757-7760-4262-b71b-7b2dde8af5cd, IP:192.168.37.105, Name: controller1, Team name: ZOK, Team IP: 192.168.37.36.

Explanation

The controller joined the team. This event was recorded on the active leader.

Recommended action

No action is required.

Keyword

MEMBER_TO_LEADER

Message text

MEMBER_TO_LEADER, ID: $1, IP: $2, Name: $3, Team name: $4, Team IP: $5.

Variable fields

$1: Member controller ID.

$2: Member controller IP address.

$3: Member controller name.

$4: Name of the team.

$5: Team IP address.

Severity level

Warning

Example

MEMBER_TO_LEADER, ID: 98394757-7760-4262-b71b-7b2dde8af5cd, IP: 192.168.37.105, Name: controller1, Team name: ZOK, Team IP: 192.168.37.36.

Explanation

A team event occurred: The controller was elected as the active leader.

Recommended action

No action is required.

Keyword

BECOME_LEADER

Message text

BECOME_LEADER, ID: $1, IP: $2, Name: $3, Team name: $4, Team IP: $5.

Variable fields

$1: Member controller ID.

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

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

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

$5: Team IP address. (This field displays 127.0.0.1 in standalone mode.)

Severity level

Info

Example

BECOME_LEADER, ID: 98394757-7760-4262-b71b-7b2dde8af5cd, IP: 192.168.37.105, Name: controller1, Team name: ZOK, Team IP: 192.168.37.36.

Explanation

A team event occurred: The controller was elected as the active leader.

Recommended action

No action is required.

Keyword

BECOME_MEMBER

Message text

BECOME_MEMBER,, ID: $1, IP: $2, Name: $3, Team name: $4, Team IP: $5.

Variable fields

$1: Member controller ID.

$2: Member controller IP address.

$3: Member controller name.

$4: Name of the team.

$5: Team IP address.

Severity level

Info

Example

BECOME_MEMBER, ID: 98394757-7760-4262-b71b-7b2dde8af5cd, IP: 192.168.37.105, Name: controller1, Team name: ZOK, Team IP: 192.168.37.36.

Explanation

A team event occurred: The controller joined the team.

Recommended action

No action is required.

Keyword

MEMBER_LEAVE

Message text

MEMBER_LEAVE, ID $1, IP $2 from team $3 team IP $4.

Variable fields

$1: Member controller ID.

$2: Member controller IP address.

$3: Team name.

$4: Team IP address.

Severity level

Warning

Example

MEMBER_LEAVE, ID 98394757-7760-4262-b71b-7b2dde8af5cd, IP 192.168.37.105 from team sdn team IP 192.168.10.1.

Explanation

The member controller left the team unexpectedly. This event was recorded on the active leader.

Recommended action

Log in to the operating system where the active leader is installed, and use the ping command to test the connectivity between the active leader and member controller.

·     Specify the IP address used by the active controller to join the team as the source IP.

·     Specify the IP address used by the member controller to join the team as the destination IP.

Log in to the operating system, and verify that the sdnc and zookeeper processes are operating correctly.

·     Use the ps -aux | grep virgo command to verify that the sdnc process is operating correctly.

·     Use the ps -aux | grep zoo command to verify that the zookeeper process is operating correctly.

·     Use the following commands to verify that all TCP connections to the zookeeper ports are in Established status.

¡     netstat -anut | grep 2181

¡     netstat -anut | grep 2888

¡     netstat -anut | grep 3888

Keyword

MEMBER_LEAVE

Message text

MEMBER_LEAVE, ID $1 from team $2 team IP $3.

Variable fields

$1: Member controller ID.

$2: Team name.

$3: Team IP address.

Severity level

Info

Example

MEMBER_LEAVE, ID 98394757-7760-4262-b71b-7b2dde8af5cd from team sdn team IP 192.168.10.1.

Explanation

The member controller left the team expectedly. This event was recorded on the active leader.

Recommended action

No action is required.

Keyword

TEAMTOKEN_DIFF

Message text

The team token of the member $1 was different than the active leader.

Variable fields

$1: IP address of the member controller.

Severity level

Warning

Example

The team token of the member 192.168.56.147 was different than the active leader.

Explanation

The team token of the member was different than the active leader when the member was added to the team or the active leader issued configuration to the member.

Recommended action

Modify the team token of the member to be the same as that of the active leader.