Severity Level

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

Time

Date and time when the log message was generated.

SNA Component Name

Name of the SNA component that produced the message.

Host Name

Name of the host that produced the message.

Service Name

Name of the service that produced the message.

Module Name

Name of the module that produced the message.

Description

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

<PRI>

Priority identifier. It is calculated by using the following formula:

Priority identifier=facilityx8+severity

Where:

·     Facility represents the programming module defined by syslog. In the current software version, the facility is user-level and its value is 1.

·     Severity represents the syslog message severity level. For more information, see Table 4.

TIMESTAMP

Date and time when the event occurred.

Hostname

Name or IP address of the server or virtual machine where the controller that produced the message resides.

Origin

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

severity

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

Keywords

Keywords of the message that facilitate searching or memorizing.

CONTENT

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

Service module name

Description

CON_APP

Application management module.

CON_MONITOR

Operating information module.

CON_NETCONF

NETCONF module.

CON_NetworkMonitor

Network health monitor 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.

DHCP

DHCP module.

NEM

Carrier network module.

ServiceChain

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

Critical

Critical condition.

4

Emergency

Emergent condition.

Item

Content

Example

Keyword

Summary of the message that facilitates searching or memorizing.

SUCCESS_UPGRADE_DEVICE

Message text

Presents the message description.

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

Variable fields

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

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

$1: Device name

$2: Device IP

Severity level

Provides the severity level of the message.

Info

Example

Provides a real message example.

Software upgrade or patching succeeded on device01 with IP 192.168.1.1.

Explanation

Explains the message, including the event or error cause.

Software upgrading or patching succeeded.

Impact

Provides potential impacts on the system. For example, a service becomes unavailable, a user cannot come online, or sessions cannot be established.

High disk usage might cause write failures and database errors.

Recommended action

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

No action is required.

Keyword

APP_GETAPPARCHIVE_FAILED

Message text

Application package not found for $1.

Variable fields

$1: Application name.

Severity level

Error

Example

Application package not found for H3C VCFC VSM.

Explanation

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

Impact

No negative impact on the system.

Recommended action

Uninstall the application and then install the complete application package.

Keyword

APP_CHANGE_STATUS

Message text

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

Variable fields

$1: Application name.

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

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

Severity level

Info

Example

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

Explanation

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

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

Impact

No negative impact on the system.

Recommended action

Uninstall and reinstall the application.

Keyword

APP_MANAGER_STATUS

Message text

Application manager module initialization error: Damaged file $1.

Variable fields

$1: Name of the damaged file.

Severity level

Critical

Example

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

Explanation

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

Impact

No negative impact on the system.

Recommended action

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

·     If the problem persists, contact H3C Support.

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.

Impact

No negative impact on the system.

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.

Impact

No negative impact on the system.

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.

Impact

No negative impact on the system.

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.

Impact

No negative impact on the system.

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.

Impact

No negative impact on the system.

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.

Impact

No negative impact on the system.

Recommended action

No action is required.

Message text

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

Variable fields

$1: IP address of the NETCONF server.

Severity level

Warning

Example

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

Explanation

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

Impact

No negative impact on the system.

Recommended action

No action is required.

Message text

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

Variable fields

$1: IP address of the NETCONF server.

Severity level

Warning

Example

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

Explanation

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

Impact

The controller fails to deploy service configuration to specific devices.

Recommended action

To resolve the problem:

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

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

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

Impact

No negative impact on the system.

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.

Impact

No negative impact on the system.

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.

Impact

No negative impact on the system.

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

Device operating status changed to unhealthy:

  IP address: $1

  CPU usage: $2

  Memory usage: $3

Variable fields

$1: IP address of the device.

$2: CPU usage of the device.

$3: Memory usage of the device.

Severity level

Warning

Example

Device operating status changed to unhealthy:

  IP address: 192.168.67.200

  CPU usage: 13%

  Memory usage: 65%

Explanation

This message is generated when the device is in suboptimal health state.

Impact

No negative impact on the system.

Recommended action

Determine whether to handle the issue as required.

Message text

Device operating status changed to healthy:

  IP address: $1

  CPU usage: $2

  Memory usage: $3

Variable fields

$1: IP address of the device.

$2: CPU usage of the device.

$3: Memory usage of the device.

Severity level

Info

Example

Device operating status changed to healthy:

  IP address: 192.168.67.200

  CPU usage: 13%

  Memory usage: 50%

Explanation

This message is generated when the device health state changes to normal.

Impact

No negative impact on the system.

Recommended action

No action is required.

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.

Impact

Traffic forwarding errors might occur on switch ports.

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.

Impact

No negative impact on the system.

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.

Impact

No negative impact on the system.

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.

Impact

No negative impact on the system.

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.

Impact

No negative impact on the system.

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.

Impact

This region is unavailable.

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.

Impact

No negative impact on the system.

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.

Impact

This region is unavailable.

Recommended action

Log in to the active leader and create regions again.

Message text

The network devices were connected to master $1:$2.

Network device management IP: $3, datapath ID: $4

Network device management IP: $3, datapath ID: $4

Variable fields

$1: IP address of the master controller.

$2: Name of the master controller.

$3: Management IP addresses of the network devices.

$4: Datapath IDs of the network devices.

Severity level

Info

Example

The network devices were connected to master 192.168.105.21:vcfc1.

Network device management IP: 192.168.1.1, datapath ID: 00:01:a6:81:13:28:01:00

Network device management IP: 192.168.10.1, datapath ID: 00:05:a6:81:13:28:01:00

Explanation

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

Impact

No negative impact on the system.

Recommended action

No action is required.

Message text

The master of the network devices was changed from $1:$2 to $3:$4.

Network device management IP: $5, datapath ID: $6

Network device management IP: $5, datapath ID: $6

Variable fields

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

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

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

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

$5: Management IP addresses of the network devices.

$6: Datapath IDs of the network devices.

Severity level

Warning

Example

The master of the network devices was changed from 192.168.105.21:vcfc1 to 192.168.105.20:vcfc2.

Network device management IP: 192.168.1.1, datapath ID: 00:01:a6:81:13:28:01:00

Network device management IP: 192.168.1.11, datapath ID: 00:05:a6:81:13:28:01:00

Explanation

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

Impact

If the failure of a controller in the region causes master controller switchover and the failed controller cannot recover, the reliability of the region might be affected.

Recommended action

No action is required.

Message text

The network devices were disconnected from the master $1.

Network device management IP: $2, datapath ID: $3

Network device management IP: $2, datapath ID: $3

Variable fields

$1: Datapath IDs of the network devices.

$2: IP address of the master controller.

Severity level

Warning

Example

The network devices were disconnected from the master 192.168.105.21.

Network device management IP: 192.168.109.1, datapath ID: 00:01:a6:81:13:28:01:00

Network device management IP: 192.168.109.12, datapath ID: 00:05:a6:81:13:28:01:00

Explanation

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

Impact

Service configuration deployment might be affected.

Recommended action

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

·     Verify that the network is connected.

·     Configure the controller to issue the region configuration again.

Message text

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

Variable fields

$1: Datapath ID of the network device.

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

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

Severity level

Critical

Example

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

Explanation

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

Impact

Service configuration deployment might be affected.

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

Critical

Example

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

Explanation

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

Impact

The reliability of the region might be affected.

Recommended action

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

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

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

Impact

No negative impact on the system.

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.

Impact

No negative impact on the system.

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.

Impact

Service modules that depend on SNMP might be affected.

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.

Impact

No negative impact on the system.

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.

Impact

No negative impact on the system.

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

Critical

Example

Database operation failed because the user did not exist.

Explanation

The database operation failed because the user did not exist.

Impact

No negative impact on the system.

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

Critical

Example

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

Explanation

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

Impact

Data saving failures might occur.

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

SCM_STATUS_INITIATED

Message text

$1 was initializing.

Variable fields

$1: Name of the application.

Severity level

Info

Example

H3C VCFC VPNaaS was initializing.

Explanation

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

Impact

No negative impact on the system.

Recommended action

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

Keyword

SCM_STATUS_RUNNING

Message text

$1 was ready for processing services.

Variable fields

$1: Name of the application.

Severity level

Info

Example

H3C VCFC VPNaaS was ready for processing services.

Explanation

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

Impact

No negative impact on the system.

Recommended action

No action is required.

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.

Impact

No negative impact on the system.

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.

Impact

No negative impact on the system.

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.

Impact

No negative impact on the system.

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.

Impact

No negative impact on the system.

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.

Impact

No negative impact on the system.

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

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

Variable fields

$1: Team event.

$2: Member controller ID.

$3: Member controller IP address.

$4: Member controller name.

$5: Name of the team.

$6: Team IP address.

Severity level

Warning

Example

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

Explanation

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

Impact

No negative impact on the system.

Recommended action

No action is required.

Keyword

MEMBER_JOIN

Message text

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

Variable fields

$1: Team event.

$2: Member controller ID.

$3: Member controller IP address.

$4: Member controller name.

$5: Name of the team.

$6: Team IP address.

Severity level

Info

Example

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

Explanation

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

Impact

No negative impact on the system.

Recommended action

No action is required.

Keyword

MEMBER_TO_LEADER

Message text

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

Variable fields

$1: Team event.

$2: Member controller ID.

$3: Member controller IP address.

$4: Member controller name.

$5: Name of the team.

$6: Team IP address.

Severity level

Warning

Example

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

Explanation

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

Impact

No negative impact on the system.

Recommended action

No action is required.

Keyword

BECOME_LEADER

Message text

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

Variable fields

$1: Team event.

$2: Member controller ID.

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

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

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

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

Severity level

Info

Example

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

Explanation

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

Impact

No negative impact on the system.

Recommended action

No action is required.

Keyword

BECOME_MEMBER

Message text

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

Variable fields

$1: Team event.

$2: Member controller ID.

$3: Member controller IP address.

$4: Member controller name.

$5: Name of the team.

$6: Team IP address.

Severity level

Info

Example

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

Explanation

A team event occurred: The controller joined the team.

Impact

No negative impact on the system.

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.

Impact

Cluster health might be affected.

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.

Impact

No negative impact on the system.

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.

Impact

No negative impact on the system.

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.

Keyword

LEADER_CONFILICT

Message text

Leader conflict was detected in stateful failover mode on the controller $1. The controller automatically rebooted to complete the team merge.

Variable fields

$1: IP address of the controller.

Severity level

Critical

Example

Leader conflict was detected in stateful failover mode on the controller 192.168.56.147. The controller automatically rebooted to complete the team merge.

Explanation

A leader conflict was detected in stateful failover mode on the controller. The controller rebooted automatically to complete the team merge.

Impact

No negative impact on the system.

Recommended action

No action is required.

Keyword

ILLEGAL_ROLE_CHANGE

Message text

Controller $1 will reboot because it is selected as the active leader during configuration recovery.

Variable fields

$1: IP address of the controller.

Severity level

Critical

Example

Controller 192.168.217.230 will reboot because it is selected as the active leader during configuration recovery.

Explanation

The controller was selected as the active leader during configuration recovery. To avoid configuration loss, the controller automatically reboots.

Impact

No negative impact on the system.

Recommended action

No action is required.

Message text

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

Variable fields

N/A

Severity level

Info

Example

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

Explanation

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

Impact

No negative impact on the system.

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

Variable fields

N/A

Severity level

Info

Example

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

Explanation

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

Impact

No negative impact on the system.

Recommended action

No action is required.

Keyword

NEM_SUBIFINFO_INCONSISTENT

Message text

The sub interface information of the NEM was different than the network device:

   Interface index: $1

   Interface name: $2

   Management IP: $3

Variable fields

$1: Subinterface index.

$2: Subinterface name.

$3: Management IP address of the network device.

Severity level

Warning

Example

The sub interface information of the NEM was different than the network device:

   Interface index: 1236

   Interface name: subif_a

   Management IP: 192.168.10.5

Explanation

The subinterface information of the NEM was different than the network device.

Impact

No negative impact on the system.

Recommended action

See the subinterface information differences between the controller and the network device on the Data Synchronization Details page, and find the reason why the differences exist.

Keyword

NEM_VLANIFINFO_INCONSISTENT

Message text

The VLAN interface information of the NEM was different than the network device:

   VLAN interface index: $1

   VLAN interface description: $2

   VLAN interface IP: $3

   Management IP: $4

Variable fields

$1: VLAN interface index.

$2: VLAN interface description.

$3: IP address of the VLAN interface.

$4: Management IP address of the network device.

Severity level

Warning

Example

The VLAN interface information of the NEM was different than the network device:

   VLAN interface index: 123

   VLAN interface description: SDN_VLAN_10

   VLAN interface IP: 18.18.18.1

   Management IP: 98.0.7.236

Explanation

The VLAN interface information for the NEM was different than the network device.

Impact

No negative impact on the system.

Recommended action

See the VLAN interface information differences between the controller and the network device on the Data Synchronization Details page, and find the reason why the differences exist.