H3C SeerEngine-DC System Log Messages Reference-E36xx-5W602

HomeSupportResource CenterSDNH3C SeerEngine-DCH3C SeerEngine-DCTechnical DocumentsMaintainMessage ReferencesH3C SeerEngine-DC System Log Messages Reference-E36xx-5W602

 

H3C SeerEngine-DC

System Log Messages Reference

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Document version: 5W602-20201218

 

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

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

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

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


Contents

Introduction· 1

Viewing system log messages· 1

Syslog message format 2

Using this document 4

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

Migration times of the VM reached the maximum within the migration time period· 6

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

BGPM·· 8

NETCONF configuration deployment failure· 8

Two master nodes exist in a vBGP cluster 8

vBGP cluster restores master/backup mode· 9

vBGP session being established· 9

vBGP session successfully established· 10

CLOSE_LOOP·· 11

Failed to log in to SeerAnalyzer 11

Logged in to SeerAnalyzer successfully· 11

Failed to connect to SeerAnalyzer 12

Connected to SeerAnalyzer successfully· 12

Failed to synchronize fault event 13

Fault event successfully synchronized· 13

Failed to update fault event 14

Updated fault event successfully· 14

Failed to update the fault event state· 15

Updated fault event state successfully· 15

Failed to synchronize the closed state of an event 16

Synchronized the closed state of an event successfully· 16

Sent port isolation request successfully· 17

Failed to send a port isolation request 17

Sent request for adding configuration fragment successfully· 18

Failed to send request for adding configuration fragment 18

Sent configuration fragment deployment request 19

Failed to send configuration fragment deployment request 19

Synchronized event resolution solution to SeerAnalyzer successfully· 20

Failed to synchronize event resolution solution to SeerAnalyzer 20

Sent NETCONF configuration deployment request successfully· 21

Failed to send NETCONF configuration deployment request 21

CON_CERTM·· 22

Service registration· 22

Service deregistration· 22

Certificate reached alarm threshold· 23

Certificate expired· 23

CON_LICENSE·· 24

License acquisition success· 24

License acquisition failure· 24

Single license reclaimed· 25

License server connection· 25

Disconnection from the license server 26

Failure of connection to the license server 26

Controller forced offline by license server 27

Reconnection to the license server 27

Entered fail-safe state due to authorization failure· 28

Entered fail-safe state due to connection failure· 28

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

Exited fail-safe state after authorization· 29

Exited fail-safe state after disconnection· 30

Remote license expiration pre-warning· 30

Insufficient quantity-based licenses· 31

CON_MONITOR·· 32

CPU usage exceeded threshold· 32

CPU usage dropped below threshold· 32

Memory usage exceeded threshold· 33

Memory usage dropped below threshold· 33

Disk usage exceeded threshold· 34

Disk usage dropped below threshold· 34

Process memory usage exceeded threshold· 35

Process memory usage dropped below threshold· 35

CON_NETCONF· 36

NETCONF session in up state· 36

NETCONF session in down state· 37

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

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

NETCONF configuration deployment failure· 39

NETCONF SSH session authentication failure· 40

NETCONF HTTPS connection failure· 40

CON_NetworkMonitor 41

Unhealthy device operating status· 41

Device operating status changes from unhealthy to healthy· 41

CON_OAM·· 42

Periodic radar detection task failure· 42

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

CON_OPENFLOW··· 44

Abnormal OpenFlow connection· 44

Successful OpenFlow connection· 44

Disconnected OpenFlow connection· 45

OpenFlow port in up state· 45

OpenFlow port in down state· 46

OpenFlow port removed· 46

Failure to deploy flow entries· 47

Packet-in message rate reaches threshold on controller 47

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

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

CON_PortMonitor 49

Change of port operating status from healthy to unhealthy· 49

Change of port operating status from unhealthy to healthy· 50

CON_REGION·· 51

Region creation· 51

Region activation· 51

Region update· 52

Region down· 52

Region deletion· 53

Failure to restore region settings· 53

Network device connection to a master 54

Master change for network devices· 54

Network device disconnection from a master 55

OpenFlow device connection with multiple regions· 55

Abnormal status of the other controller in the region· 56

Normal status of the other controller in the region· 56

CON_SNMP·· 57

Traditional NE created SNMP connection with controller 57

Traditional NE broke SNMP connection to controller 57

Traditional NE port up· 58

Traditional NE port down· 58

CON_SYSTEM·· 59

Database operation failure because of a nonexistent user 59

Database operation failure because of refused connections· 59

End of controller configuration recovery· 60

Controller configuration backup not performed when backup file exists· 60

Failed to send the backup file to the remote server 61

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

CON_TEAM·· 62

Failure to delete team IP· 62

Controller suspended· 62

Member joined team·· 63

Active leader changed· 63

Controller became active leader 64

Controller became member 64

Member left team unexpectedly· 65

Member left team expectedly· 66

Different team token than the active leader 66

Reboot for completing team merge· 67

Reboot to act as the leader 67

CON_USER·· 68

Login success· 68

Login failure· 68

User lock· 69

Logout success· 69

RADIUS authentication success· 69

RADIUS authentication rejection· 70

RADIUS authentication failure· 70

RADIUS attribute check failure· 71

TACACS+ authentication success· 71

TACACS+ authentication rejection· 71

TACACS+ authentication failure· 72

TACACS+ attribute check failure· 72

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

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

Operation failure due to user role privilege limit 74

User password expiration· 74

DATACHECK·· 75

Controller failed data entry count consistency check· 75

Controller passed data entry count consistency check· 75

Failure to obtain data entry count consistency check result for controller 76

Controller passed local data entry count consistency check· 76

Controller failed local data entry count consistency check· 77

Failure to obtain local data entry count consistency check result for controller 77

Controller passed cluster data content consistency check· 78

Controller failed cluster data content consistency check· 78

Failure to obtain cluster data content consistency check result for controller 79

DHCP·· 80

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

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

Failure of IP allocation to VM·· 81

F5aaS·· 82

Connection establishment between the F5 device and controller 82

Disconnection between the F5 device and controller 82

Failure to delete a floating IP· 83

FWaaS·· 84

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

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

Inconsistent DPI application profile information· 85

Inconsistent IPS policy information· 85

Inconsistent antivirus policy information· 86

DPI engine disabled· 86

IDM·· 87

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

LBaaS·· 88

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

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

NEM·· 89

Different VRF information than the network device· 89

Different VSI information than the network device· 90

Different tunnel information than the network device· 91

Different ACL information than the network device· 92

Different PBR information than the network device· 92

Different routing information than the network device· 93

Different VLAN information than the network device· 94

Different NAT information than the network device· 95

Different floating IP information than the network device· 96

Different DNS information than the network device· 97

Different host flow information than the network device· 98

Different subinterface information than the network device· 99

Different VLAN interface information than the network device· 100

Different loopback interface information than the network device· 101

Network device connection to another region· 101

VXLAN tunnel interface in up state· 102

VXLAN tunnel interface in down state· 103

Failed to add flow table· 104

VLAN ID allocation failure· 104

Used up VLAN IDs in the VLAN pools· 105

VLAN pool not exist 105

Used up VXLAN IDs in the VXLAN pools· 106

Used up IP addresses in general address pool 106

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

Used up IP addresses in security external network address pool 108

Used up IP addresses in default address pool 108

Address pool bound to service gateway group not exist 109

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

Default address pool not exist 110

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

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

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

Data synchronization status changed to Not Synchronized· 112

Data synchronization status changed to Synchronized· 112

Configuration initialization failure during NE activation· 113

Maximum number of Ethernet service instances reached on interface· 114

Controller failed to deploy settings to network device· 115

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

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

Startup configuration file backup success· 117

Startup configuration file backup failure· 117

VTEP IP assignment failure· 118

Software upgrading or patching failure· 118

Software upgrading or patching success· 119

Used up IP addresses in the underlay address pool 119

Device failed to come online automatically· 120

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

IRF member device was not powered off during replacement 121

CID editing failure· 121

Starting data synchronization or auditing· 122

Finishing data synchronization or auditing· 122

Starting fine-grained synchronization· 123

Finishing fine-grained synchronization· 123

Executing an audit task· 124

Track number allocation failure· 124

Used up loopback interfaces on a device· 125

NGFWM messages· 126

NGFW resource creation failure· 126

NGFW resource modification failure· 126

NGFW resource deletion failure· 127

NGFW resource creation with NETCONF failure· 127

NGFW resource creation with NETCONF success· 128

NGFW resource modification with NETCONF success· 128

NGFW resource modification with NETCONF failure· 129

Start of NGFWM configuration recovery on non-active leader controllers· 129

End of NGFWM configuration recovery on non-active leader controllers· 130

Changed NETCONF password successfully· 130

Failed to change the NETCONF password· 131

OAM·· 132

Failed to create image file upload path· 132

Software upgrade or patching failed· 133

Software upgrade or patching succeeded· 133

Failed to replace a device· 134

Failed to back up device configuration file· 135

Failed to restore a device· 135

RDR·· 137

PXC cluster anomaly· 137

PXC cluster creation failure· 137

Heartbeat channel anomaly· 137

Data channel anomaly· 138

Arbiter service anomaly· 138

Switchover to backup role failed· 138

Switchover to backup role succeeded· 139

Switchover to primary role failed· 139

Switchover to primary role succeeded· 139

SNA Installer service anomaly· 140

Disaster recovery component deletion failure· 140

SEERENGINE·· 141

IP version mismatch between vPort destination network segment and vPort IP· 141

Mirroring destination profile with PHY-type vPort and without any destination IP address· 141

IP version mismatch between OVS-type vPort VTEP IP and mirroring destination profile destination IP· 142

ServiceChain· 143

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

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

TELEMETRY·· 144

Configuration deployment failure· 144

Tenant 145

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

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

VMM·· 146

Failed to connect to vCenter 146

Connected to vCenter successfully· 146

Failed to disconnect from vCenter 147

Disconnected from vCenter successfully· 147

Failed to create VDS· 148

Created VDS successfully· 148

Failed to delete VDS· 149

Deleted VDS successfully· 149

Failed to update distributed port group QoS· 150

Updated distributed port group QoS successfully· 150

Failed to create distributed port group· 151

Created distributed port group successfully· 151

Failed to update distributed port group· 152

Updated distributed port group successfully· 152

Failed to delete distributed port group· 153

Deleted distributed port group successfully· 153

Added vPort to VSM successfully· 154

Failed to add vPort to VSM·· 154

Deleted vPort from VSM successfully· 155

Failed to delete vPort from VSM·· 155

Updated vPort on VSM successfully· 156

Failed to update vPort on VSM·· 156

Failed to synchronize vPort information· 157

Keyword· 157

Automatic reconciliation completed· 157

Data reconciliation completed· 158

Added network overlay host to VSM successfully· 158

Failed to add network overlay host to VSM·· 159

Deleted network overlay host from VSM successfully· 159

Failed to delete network overlay host from VSM·· 160

Updated network overlay host on VSM successfully· 160

Failed to update network overlay host on VSM·· 161

Failed to allocate VLAN IDs on NEM·· 161

Failed to obtain VLAN resource pool name on NEM·· 162

Failed to reclaim VLAN IDs on NEM·· 162

Failed to synchronize VLAN IDs on NEM·· 163

Failed to bind VLAN resource pool on NEM·· 163

Failed to unbind VLAN resource pool on NEM·· 164

Failed to obtain VLAN ID assignment information on NEM·· 164

Failed to connect to RHVM·· 165

Connected to RHVM successfully· 165

Failed to disconnect from RHVM·· 166

Disconnected from RHVM successfully· 166

Failed to create logical network· 167

Created logical network successfully· 167

Failed to update logical network· 168

Updated logical network successfully· 168

Failed to delete logical network· 169

Deleted logical network successfully· 169

Added vPort to VSM through RHVM successfully· 170

Failed to add vPort to VSM through RHVM·· 170

Deleted vPort from VSM through RHVM successfully· 171

Failed to delete vPort from VSM through RHVM·· 171

Updated vPort on VSM through RHVM successfully· 172

Failed to update vPort on VSM through RHVM·· 172

Failed to create VDS· 173

Failed to create distributed port group· 173

Failed to obtain vCenter data· 174

Data reconciliation completed· 174

Connected to OpenStack successfully· 175

Failed to connect to OpenStack· 175

Created DHCP vPort successfully· 176

Failed to create DHCP vPort 176

Deleted DHCP vPort successfully· 177

Connected to OpenStack controller node successfully· 177

Disconnected from OpenStack controller node· 178

VPNaaS·· 179

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

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

VSM·· 180

Failure to add host because of invalid license· 180

vPort number reaching threshold· 180

vPort number falling below threshold· 181

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

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

Compute node neighbor aging after a specific time period· 182

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

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

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

Network node neighbor aging after a specific time period· 185

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

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

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

Successful VM migration· 188

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

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

Controller failed to communicate with host through OVSDB· 190

Host IP change· 191

vPort UUID prefix conflict 191

Flow table synchronization or auditing started· 192

Flow table synchronization or auditing finished· 192

Host flow table issuing failure· 193

Host group table issuing failure· 194

Network node established WebSocket connection to controller 195

Network node terminated WebSocket connection to controller 195

DHCP configuration auditing or synchronization started· 196

DHCP configuration auditing or synchronization started finished· 196

 


Introduction

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

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

Viewing system log messages

1.     Log in to SNA Center.

2.     Click Settings in the System area.

3.     On the top navigation bar, click Logs.

4.     From the left navigation pane, select Information.

5.     Click the System Logs tab.

The paginated system log message list is displayed, as shown in Figure 1.

Figure 1 System log message list

 

 

Table 1 System log message elements

Element

Description

Severity level

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

Time

Date and time when the log message was generated.

Component Name

Name of the SNA component that generated the log message.

Host Name

Name of the host that generated the log message.

Service Name

Name of the service that produced the log message.

Description

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

 

Syslog message format

SNA Center can send system logs to syslog servers through the syslog protocol. To configure system log output to syslog servers, go to the Logs > Configuration > System Logs page.

By default, SNA Center sends system logs to syslog servers in the following format:

<PRI>TIMESTAMP Hostname Service/severity/Keywords CONTENT

Table 2 Syslog message elements

Element

Description

<PRI>

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

Priority identifier=facilityx8+severity

Where:

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

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

TIMESTAMP

Date and time when the event occurred.

Hostname

Name or IP address of the host that produced the message.

Service

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

severity

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

Keywords

Keywords of the message that facilitate searching or memorizing.

CONTENT

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

 

Table 3 lists the service modules that might produce system log messages.

Table 3 Service module list

Service module name

Description

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.

RDR

Remote disaster recovery 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

Info

Information message.

1

Warning

Warning condition.

2

Error

Error condition.

3

Serious

Serious condition.

4

Critical

Critical condition.

 

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

Table 6 Severity level mappings

System log message severity level

Syslog message severity level

0

6

1

4

2

3

3

2

4

0

 

Using this document

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

Table 7 Message explanation table contents

Item

Content

Example

Keyword

Summary of the message that facilitates searching or memorizing.

OPENFLOW_SESSION_UP

Message text

Presents the message description.

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

Variable fields

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

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

$1: Datapath ID of the OpenFlow device.

$2: Management IP address of the OpenFlow device.

$3: Description information about the OpenFlow device.

$4: IP address of the controller.

Severity level

Provides the severity level of the message.

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

Warning

Example

Failed to synchronize arp bus message.

Explanation

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

Recommended action

Verify that the network connections are correct among the controllers.

 

Start of ARP configuration recovery on non-active leader controllers

Keyword

BEGIN_RECOVER_ARP_CONFIG

Message text

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

Variable fields

N/A

Severity level

Info

Example

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

Explanation

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

Recommended action

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

 

End of ARP configuration recovery on non-active leader controllers

Keyword

FINISH_RECOVER_ARP_CONFIG

Message text

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

Variable fields

N/A

Severity level

Info

Example

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

Explanation

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

Recommended action

No action is required.

 

Migration times of the VM reached the maximum within the migration time period

Keyword

ARP_MIGRATE_OVERFLOW

Message text

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

Variable fields

$1: IP address of the VM.

$2: MAC address of the VM.

$3: Access interface number.

$4: Management IP address of the access device.

Severity level

Warning

Example

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

Explanation

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

Recommended action

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

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

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

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

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

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

 

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

Keyword

ARP_MAC_CONFLICT

Message text

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

Variable fields

$1: IP address of the VM.

$2: MAC address of the VM.

$3: Access port number.

$4: Management IP address of the access device.

Severity level

Warning

Example

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

Explanation

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

Recommended action

Modify the VM MAC address.

 

 


BGPM

This section contains BGPM messages.

NETCONF configuration deployment failure

Keyword

VBGP_NETCONF_CONFIG_FAILED

Message text

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

Variable fields

$1: IP address of the BGP node.

$2: NETCONF configuration deployment failure reason.

$3: NETCONF configuration item failed to be deployed.

Severity level

Warning

Example

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

Explanation

Failed to deploy NETCONF configuration to a vBGP node.

Recommended action

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

4.     Verify that the configuration is correct.

 

Two master nodes exist in a vBGP cluster

Keyword

VBGP_DOUBLE_MASTER

Message text

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

Variable fields

$1: vBGP cluster ID.

$2: IP address of the first master node.

$3: IP address of the second master node.

Severity level

Warning

Example

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

Explanation

Two master nodes exist in a vBGP cluster.

Recommended action

5.     Verify that the vBGP nodes can communicate correctly.

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

 

vBGP cluster restores master/backup mode

Keyword

VBGP_MASTER_BACKUP

Message text

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

Variable fields

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

 

vBGP session being established

Keyword

VBGP_PEER_SESSION_STATE

Message text

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

Variable fields

$1: Management IP address of the vBGP node.

$2: Peer IP address.

$3: Instance name.

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

Severity level

Info

Example

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

Explanation

A vBGP session is being established.

Recommended action

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

 

vBGP session successfully established

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.

 


CLOSE_LOOP

This section contains system messages generated by the Closed Loop module.

Failed to log in to SeerAnalyzer

Keyword

LOGIN_SA_FAILED

Message text

Login to SeerAnalyzer $1 failed.

Variable fields

$1: URL of SeerAnalyzer.

Severity level

Error

Example

Login to SeerAnalyzer http://192.168.1.123:10080 failed.

Explanation

Failed to log in to SeerAnalyzer.

Recommended action

Check the SeerAnalyzer configuration and verify that SeerAnalyzer is operating correctly.

 

Logged in to SeerAnalyzer successfully

Keyword

LOGIN_SA_SUCCESS

Message text

Login to SeerAnalyzer $1 successfully.

Variable fields

$1: URL of SeerAnalyzer.

Severity level

Info

Example

Login to SeerAnalyzer http://192.168.1.123:10080 successfully.

Explanation

Logged in to SeerAnalyzer successfully.

Recommended action

No action is required.

 

Failed to connect to SeerAnalyzer

Keyword

CONNECT_SA_FAIL

Message text

Failed to connect to SeerAnalyzer $1.

Variable fields

$1: URL of SeerAnalyzer.

Severity level

Error

Example

Failed to connect to SeerAnalyzer http://192.168.1.123:10080.

Explanation

Failed to connect to SeerAnalyzer because the token cannot be retrieved.

Recommended action

Check the SeerAnalyzer configuration and verify that SeerAnalyzer is operating correctly.

 

Connected to SeerAnalyzer successfully

Keyword

CONNECT_SA_SUCCESS

Message text

Connected to SeerAnalyzer $1 successfully.

Variable fields

$1: URL of SeerAnalyzer.

Severity level

Info

Example

Connected to SeerAnalyzer http://192.168.1.123:10080 successfully.

Explanation

Connected to SeerAnalyzer successfully.

Recommended action

No action is required.

 

Failed to synchronize fault event

Keyword

SA_SYNC_FAULT_TO_CTL_FAILED

Message text

Synchronizing event $1 failed.

Variable fields

$1: UUID of the event.

Severity level

Error

Example

Synchronizing event bb8bb083-c4a4-45eb-b5dc-2b251a7921f3 failed.

Explanation

SeerAnalyzer failed to synchronize fault event information to the Closed Loop microservice.

Recommended action

Check the diagnostic logs to locate the cause for the failure.

 

Fault event successfully synchronized

Keyword

SA_SYNC_FAULT_TO_CTL_SUCCESS

Message text

Synchronized event $1 successfully.

Variable fields

$1: UUID of the fault event.

Severity level

Info

Example

Synchronized event bb8bb083-c4a4-45eb-b5dc-2b251a7921f3 successfully.

Explanation

SeerAnalyzer successfully synchronized fault event information to the Closed Loop microservice.

Recommended action

No action is required.

 

Failed to update fault event

Keyword

SA_UPDATE_FAULT_TO_CTL_FAILED

Message text

Updating event $1 failed.

Variable fields

$1: UUID of the event.

Severity level

Error

Example

Updating event bb8bb083-c4a4-45eb-b5dc-2b251a7921f3 failed.

Explanation

SeerAnalyzer failed to update the fault event information in the Closed Loop microservice.

Recommended action

Check the diagnostic logs to locate the cause for the failure.

 

Updated fault event successfully

Keyword

SA_UPDATE_FAULT_TO_CTL_SUCCESS

Message text

Updated event $1 successfully.

Variable fields

$1: UUID of the event.

Severity level

Info

Example

Updated event bb8bb083-c4a4-45eb-b5dc-2b251a7921f3 successfully.

Explanation

SeerAnalyzer successfully updated the fault event information in the Closed Loop microservice.

Recommended action

No action is required.

 

Failed to update the fault event state

Keyword

SA_UPDATE_FAULT_STATUS_TO_CTL_FAILED

Message text

Updating event $1 status $2 failed.

Variable fields

$1: UUID of the event.

$2: New fault event state.

Severity level

Error

Example

Updating event bb8bb083-c4a4-45eb-b5dc-2b251a7921f3 status 1 failed.

Explanation

SeerAnalyzer failed to update the fault event state in the Closed Loop microservice.

Recommended action

Check the diagnostic logs to locate the cause for the failure.

 

Updated fault event state successfully

Keyword

SA_UPDATE_FAULT_STATUS_TO_CTL_SUCCESS

Message text

Updated event $1 status $2 successfully.

Variable fields

$1: UUID of the event.

$2: New fault event state.

Severity level

Info

Example

Updated event bb8bb083-c4a4-45eb-b5dc-2b251a7921f3 status 1 successfully.

Explanation

SeerAnalyzer updated the fault event state in the Closed Loop microservice successfully.

Recommended action

No action is required.

 

Failed to synchronize the closed state of an event

Keyword

CTL_SYNC_FAULT_CLOSED_STATUS_TO_SA_FAILED

Message text

Failed to synchronize the closed state of event $1.

Variable fields

$1: UUID of the event.

Severity level

Error

Example

Failed to synchronize the closed state of event bb8bb083-c4a4-45eb-b5dc-2b251a7921f3.

Explanation

The Closed Loop microservice failed to synchronize the closed state of a fault event to SeerAnalyzer.

Recommended action

Check the diagnostic logs to locate the cause for the failure.

 

Synchronized the closed state of an event successfully

Keyword

CTL_SYNC_FAULT_CLOSED_STATUS_TO_SA_SUCCESS

Message text

Successfully synchronized the closed state of event $1.

Variable fields

$1: UUID of the event.

Severity level

Info

Example

Successfully synchronized the closed state of event bb8bb083-c4a4-45eb-b5dc-2b251a7921f3.

Explanation

The Closed Loop microservice successfully synchronized the closed state of a fault event to SeerAnalyzer.

Recommended action

No action is required.

 

Sent port isolation request successfully

Keyword

ISOLATED_PHYSICAL_PORT_SUCCESS

Message text

Successfully sent port isolation request.

Variable fields

N/A

Severity level

Info

Example

Successfully sent port isolation request.

Explanation

The Closed Loop microservice sent a port isolation request to the corresponding device successfully.

Recommended action

No action is required.

 

Failed to send a port isolation request

Keyword

ISOLATED_PHYSICAL_PORT_FAILED

Message text

Failed to send port isolation request.

Variable fields

N/A

Severity level

Error

Example

Failed to send port isolation request.

Explanation

The Closed Loop microservice failed to send a port isolation request to the corresponding device.

Recommended action

Check the diagnostic logs to locate the cause for the failure.

 

Sent request for adding configuration fragment successfully

Keyword

ADD_CONFIGURATION_FRAGMENT_SUCCESS

Message text

Successfully sent request for adding configuration fragment.

Variable fields

N/A

Severity level

Info

Example

Successfully sent request for adding configuration fragment.

Explanation

The Closed Loop microservice sent a request for adding configuration fragment successfully.

Recommended action

No action is required.

 

Failed to send request for adding configuration fragment

Keyword

ADD_CONFIGURATION_FRAGMENT_FAILED

Message text

Failed to send request for adding configuration fragment.

Variable fields

N/A

Severity level

Error

Example

Failed to send request for adding configuration fragment.

Explanation

The Closed Loop microservice failed to send a request for adding configuration fragment to the controller.

Recommended action

Verify that the controller service is available and that the controller port is working correctly.

 

Sent configuration fragment deployment request

Keyword

SEND_CONFIGURATION_FRAGMENT_SUCCESS

Message text

Successfully sent request for deploying configuration fragment.

Variable fields

N/A

Severity level

Info

Example

Successfully sent request for deploying configuration fragment.

Explanation

The Closed Loop microservice successfully sent a request for adding configuration fragment to the controller.

Recommended action

No action is required.

 

Failed to send configuration fragment deployment request

Keyword

SEND_CONFIGURATION_FRAGMENT_FAILED

Message text

Failed to send request for deploying configuration fragment.

Variable fields

N/A

Severity level

Error

Example

Failed to send request for deploying configuration fragment.

Explanation

The Closed Loop microservice failed to send a request for adding configuration fragment to the controller.

Recommended action

Verify that the controller service is available and that the controller port is working correctly.

 

Synchronized event resolution solution to SeerAnalyzer successfully

Keyword

SYNC_SA_ACTION_STATUS_SUCCESS

Message text

Successfully synchronized event state to SeerAnalyzer.

Variable fields

N/A

Severity level

Info

Example

Successfully synchronized event state to SeerAnalyzer.

Explanation

The Closed Loop microservice successfully synchronized event the resolution solution to SeerAnalyzer.

Recommended action

No action is required.

 

Failed to synchronize event resolution solution to SeerAnalyzer

Keyword

SYNC_SA_ACTION_STATUS_FAILED

Message text

Failed to synchronize event state to SeerAnalyzer.

Variable fields

N/A

Severity level

Error

Example

Failed to synchronize event state to SeerAnalyzer.

Explanation

The Closed Loop microservice failed to synchronize the event resolution solution to SeerAnalyzer.

Recommended action

Verify that the controller service is available and that the controller port is working correctly.

 

Sent NETCONF configuration deployment request successfully

Keyword

SEND_CONFIGURATION_NETCONF_SUCCESS

Message text

Sent NETCONF configuration request to DC successfully.

Variable fields

N/A

Severity level

Info

Example

Sent NETCONF configuration request to DC successfully.

Explanation

The Closed Loop microservice successfully sent a NETCONF configuration deployment request to the controller.

Recommended action

No action is required.

 

Failed to send NETCONF configuration deployment request

Keyword

SEND_CONFIGURATION_NETCONF_FAILED

Message text

Failed to send NETCONF configuration request to DC.

Variable fields

N/A

Severity level

Error

Example

Failed to send NETCONF configuration request to DC.

Explanation

The Closed Loop microservice failed to send a NETCONF configuration deployment request to the controller.

Recommended action

·     Verify that the controller service is available and that the controller port is working correctly.

·     Verify that the device supports NETCONF.

·     Verify that the NETCONF connection to the device is available.

 

 


CON_CERTM

This section contains certificate management messages.

Service registration

Keyword

CERTM_SERVICE_REGISTER

Message text

The $1 service $2 registration $3

Variable fields

$1: Service name.

$2: List of built-in certificate names (optional).

$3: Registration result.

Severity level

Info

Example

·     The License Client service {k.pem, c.epm, ca.pem} registration succeeded.

·     The OpenFlow service registration failed. Reason: The user role doesn't provide the permission to perform the operation.

Explanation

The user performed service registration with certificate management.

Recommended action

Check the registration result. If the registration fails, view the failure reason.

 

Service deregistration

Keyword

CERTM_SERVICE_UNREGISTER

Message text

The $1 service deregistration $2

Variable fields

$1: Service name.

$2: Deregistration result.

Severity level

Info

Example

·     The OpenFlow service deregistration succeeded.

·     The OpenFlow service deregistration failed. Reason: The user role doesn't provide the permission to perform the operation.

Explanation

The user performed service deregistration with certificate management.

Recommended action

Check the deregistration result. If the deregistration fails, view the failure reason.

 

Certificate reached alarm threshold

Keyword

CERTIFICATE_WILL_EXPIRE

Message text

The certificate $1 for $2 service with subject "$3" will expire in $4 days.

Variable fields

$1: Certificate name.

$2: Service name.

$3: Subject information.

$4: Remaining days of the certificate.

Severity level

Warning

Example

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

Explanation

The validity of the certificate has reached or dropped below the alarm threshold.

Recommended action

Replace the certificate in time.

 

Certificate expired

Keyword

CERTIFICATE_EXPIRED

Message text

The certificate $1 for $2 service with subject "$3" expired.

Variable fields

$1: Certificate name.

$2: Service name.

$3: Subject information.

Severity level

Warning

Example

The certificate ca.jks for OpenFlow service with subject " C=CN, ST=ZheJiang, L=Hangzhou, O=Hangzhou H3C Technologies Co., Ltd., CN=*.h3c.com" expired.

Explanation

The certificate has expired.

Recommended action

Replace the certificate in time.

 


CON_LICENSE

This section contains CON_LICENSE messages.

License acquisition success

Keyword

LICENSE_INSTALL

Message text

$1 license successfully obtained.

Variable fields

$1: License name.

Severity level

Info

Example

Base license successfully obtained.

Explanation

The specified license was successfully obtained.

Recommended action

No action is required.

 

License acquisition failure

Keyword

LICENSE_INSTALL_FAILED

Message text

Failed to obtain the $1 license.

Variable fields

$1: License name.

Severity level

Info

Example

Failed to obtain the base license.

Explanation

Failed to obtain the specified license.

Recommended action

Identify whether the license server has enough licenses.

 

Single license reclaimed

Keyword

LICENSE_RECLAIM

Message text

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

Variable fields

$1: Feature name.

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

Severity level

Warning

Example

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

Explanation

The license for the specified feature was reclaimed.

Recommended action

No action is required.

 

License server connection

Keyword

LICENSE_SERVER_CONNECT

Message text

The controller established a connection to the license server.

Variable fields

N/A

Severity level

Info

Example

The controller established a connection to the license server.

Explanation

The controller established a connection to the license server.

Recommended action

No action is required.

 

Disconnection from the license server

Keyword

LICENSE_SERVER_DISCONNECT

Message text

The controller was disconnected from the license server.

Variable fields

N/A

Severity level

Warning

Example

The controller was disconnected from the license server.

Explanation

The controller was disconnected from the license server.

Recommended action

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

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

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

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

 

Failure of connection to the license server

Keyword

LICENSE_SERVER_CONNECT_FAILED

Message text

Failed to connect to the license server.

Variable fields

N/A

Severity level

Warning

Example

Failed to connect to the license server.

Explanation

The controller failed to connect to the license server.

Recommended action

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

11.     Verify that the license server is operating correctly.

 

Controller forced offline by license server

Keyword

LICENSE_SERVER_FORCE_CLIENT_OFFLINE

Message text

The controller was forced offline by license server.

Variable fields

N/A

Severity level

Warning

Example

The controller was forced offline by license server.

Explanation

The license server forced the controller to go offline.

Recommended action

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

 

Reconnection to the license server

Keyword

LICENSE_SERVER_AGED_RECONNECT

Message text

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

Variable fields

N/A

Severity level

Warning

Example

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

Explanation

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

Recommended action

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

 

Entered fail-safe state due to authorization failure

Keyword

ENTER_FAILSAFE_NO_LICENSE

Message text

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

Variable fields

N/A

Severity level

Warning

Example

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

Explanation

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

Recommended action

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

 

Entered fail-safe state due to connection failure

Keyword

ENTER_FAILSAFE_CONNECT_FAILED

Message text

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

Variable fields

N/A

Severity level

Warning

Example

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

Explanation

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

Recommended action

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

 

Exited fail-safe state after the fail-safe period

Keyword

EXIT_FAILSAFE_EXPIRED

Message text

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

Variable fields

N/A

Severity level

Warning

Example

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

Explanation

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

Recommended action

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

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

 

Exited fail-safe state after authorization

Keyword

EXIT_FAILSAFE_OBTAINED

Message text

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

Variable fields

N/A

Severity level

Warning

Example

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

Explanation

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

Recommended action

No action is required.

 

Exited fail-safe state after disconnection

Keyword

EXIT_FAILSAFE_DISCONNECTED

Message text

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

Variable fields

N/A

Severity level

Warning

Example

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

Explanation

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

Recommended action

No action is required.

 

Remote license expiration pre-warning

Keyword

LICENSE_EXPIRED

Message text

$1 license is about to expire in 10 days.

Variable fields

$1: Remote license name.

Severity level

Warning

Example

Base license is about to expire in 10 days.

Explanation

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

Recommended action

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

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

 

Insufficient quantity-based licenses

Keyword

LICENSE_INSUFFICIENT

Message text

Insufficient $1 licenses. Please purchase more licenses.

Variable fields

$1: Name of the quantity-based licenses.

Severity level

Critical

Example

Insufficient MaxNodeNum licenses. Please purchase more licenses.

Explanation

The number of quantity-based licenses is insufficient.

Recommended action

Purchase more licenses.

 

 


CON_MONITOR

This section contains CON_MONITOR messages.

CPU usage exceeded threshold

Keyword

CPU_USAGE_EXCEED_THRESHOLD

Message text

CPU usage $1 exceeded the threshold $2.

Variable fields

$1: Current CPU usage.

$2: CPU usage threshold.

Severity level

Warning

Example

CPU usage 91% exceeded the threshold 90%.

Explanation

The CPU usage of the system exceeded the threshold.

Recommended action

·     Verify that the CPU usage threshold is appropriate.

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

 

CPU usage dropped below threshold

Keyword

CPU_USAGE_UNDER_THRESHOLD

Message text

CPU usage $1 dropped below the threshold $2.

Variable fields

$1: Current CPU usage.

$2: CPU usage threshold.

Severity level

Info

Example

CPU usage 80% dropped below the threshold 90%.

Explanation

The CPU usage of the system dropped below the threshold.

Recommended action

No action is required.

 

Memory usage exceeded threshold

Keyword

MEMORY_USAGE_EXCEED_THRESHOLD

Message text

Memory usage $1 exceeded the threshold $2.

Variable fields

$1: Current memory usage.

$2: Memory usage threshold.

Severity level

Warning

Example

Memory usage 91% exceeded the threshold 90%.

Explanation

The memory usage of the system exceeded the threshold.

Recommended action

·     Verify that the memory usage threshold is appropriate.

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

 

Memory usage dropped below threshold

Keyword

MEMORY_USAGE_UNDER_THRESHOLD

Message text

Memory usage $1 dropped below the threshold $2.

Variable fields

$1: Current memory usage.

$2: Memory usage threshold.

Severity level

Info

Example

Memory usage 80% dropped below the threshold 90%.

Explanation

The memory usage of the system dropped below the threshold.

Recommended action

No action is required.

 

Disk usage exceeded threshold

Keyword

DISK_USAGE_EXCEED_THRESHOLD

Message text

Disk usage $1 exceeded the threshold $2.

Variable fields

$1: Current disk usage.

$2: Disk usage threshold.

Severity level

Warning

Example

Disk usage 91% exceeded the threshold 90%.

Explanation

The disk usage of the system exceeded the threshold.

Recommended action

·     Verify that the disk usage threshold is appropriate.

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

 

Disk usage dropped below threshold

Keyword

DISK_USAGE_UNDER_THRESHOLD

Message text

Disk usage $1 dropped below the threshold $2.

Variable fields

$1: Current disk usage.

$2: Disk usage threshold.

Severity level

Info

Example

Disk usage 80% dropped below the threshold 90%.

Explanation

The disk usage of the system dropped below the threshold.

Recommended action

No action is required.

 

Process memory usage exceeded threshold

Keyword

PROCESS_MEMORY_USAGE_EXCEED_THRESHOLD

Message text

Memory usage $1% exceeded the alarm threshold $2% in $3 process, and $4 garbage collections had happened.

Variable fields

$1: Current memory usage.

$2: Memory usage threshold.

$3: Process name.

$4: Number of GCs in the old generation.

Severity level

Warning

Example

Memory usage 91% exceeded the alarm threshold 90% in sdnc process, and 5 garbage collections had happened.

Explanation

The memory usage of the process exceeded the threshold, and GCs had happened. The memory might be exhausted.

Recommended action

·     Check the number of services on the controller. If the controller has carried too many services, transfer some services to other controllers in the team.

·     Contact H3C Support.

 

Process memory usage dropped below threshold

Keyword

PROCESS_MEMORY_USAGE_EXCEED_THRESHOLD

Message text

Memory usage $1% dropped below the alarm threshold $2% in $3 process.

Variable fields

$1: Current memory usage.

$2: Memory usage threshold.

$3: Process name.

Severity level

Info

Example

Memory usage 80% dropped below the alarm threshold 90% in sdnc process.

Explanation

After exceeding the threshold, the memory usage of the process dropped below the threshold.

Recommended action

No action is required.

 

 


CON_NETCONF

This section contains CON_NETCONF messages.

NETCONF session in up state

Keyword

NETCONF_SESSION_UP

Message text

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

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

Variable fields

$1: IP address of the NETCONF server.

$2: Application name.

Severity level

Warning

Example

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

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

Explanation

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

Recommended action

No action is required.

 

NETCONF session in down state

Keyword

NETCONF_SESSION_DOWN

Message text

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

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

Variable fields

$1: IP address of the NETCONF server.

$2: Application name.

Severity level

Warning

Example

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

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

Explanation

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

Recommended action

To resolve the problem:

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

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

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

 

Start of NETCONF configuration recovery on non-active leader controllers

Keyword

BEGIN_RECOVER_NETCONF_CONFIG

Message text

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

Variable fields

N/A

Severity level

Info

Example

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

Explanation

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

Recommended action

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

 

End of NETCONF configuration recovery on non-active leader controllers

Keyword

FINISH_RECOVER_NETCONF_CONFIG

Message text

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

Variable fields

N/A

Severity level

Info

Example

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

Explanation

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

Recommended action

No action is required.

 

NETCONF configuration deployment failure

Keyword

NETCONF_FAILED

Message text

$1

Variable fields

$1: Error packet sent from the NETCONF server.

Severity level

Warning

Example

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

<env:Body>

  <env:Fault>

    <env:Code>

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

    </env:Code>

    <env:Reason>

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

    </env:Reason>

  </env:Fault>

</env:Body>

Explanation

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

Recommended action

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

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

 

NETCONF SSH session authentication failure

Keyword

NETCONF_SSH_AUTH_FAILED

Message text

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

Variable fields

$1: NETCONF server IP address.

$2: Application name.

$3: Session creation failure reason.

Severity level

Warning

Example

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

Explanation

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

Recommended action

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

·     Verify that the network is operating correctly.

 

NETCONF HTTPS connection failure

Keyword

DEVICE_NETCONF_CONNECT_FAILED

Message text

The NETCONF HTTPS connection failed on device $1.

Variable fields

$1: Device IP address.

Severity level

Warning

Example

The NETCONF HTTPS connection failed on device 192.168.203.16.

Explanation

The NETCONF HTTPS connection failed on a device

Recommended action

·     Verify that the current software version of the device supports NETCONF.

·     Verify that the NETCONF HTTPS connection capability is enabled.

 

 

 


CON_NetworkMonitor

This section contains CON_NetworkMonitor messages.

Unhealthy device operating status

Keyword

MONITOR_DEVICE_ABNORMAL

Message text

Device operating status changed to unhealthy:

  IP address: $1

  Device health level: $2

Variable fields

$1: IP address of the device.

$2: Health level of the device.

Severity level

Warning

Example

Device operating status changed to unhealthy:

  IP address: 192.168.67.200

  Device health level: 23

Explanation

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

Recommended action

Determine whether to handle the issue as required.

 

Device operating status changes from unhealthy to healthy

Keyword

MONITOR_DEVICE_NORMAL

Message text

Device operating status changed to healthy:

  IP address: $1

  Device health level: $2

Variable fields

$1: IP address of the device.

$2: Health level of the device.

Severity level

Info

Example

Device operating status changed to healthy:

  IP address: 192.168.67.200

  Device health level: 30

Explanation

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

Recommended action

No action is required.

 

 


CON_OAM

This section contains CON_OAM messages.

Periodic radar detection task failure

Keyword

PERIODIC_DETECTION_FAILED

Message text

Periodic radar detection task failed: $1

Variable fields

$1: Periodic radar detection task parameters.

Severity level

Warning

Example

Periodic radar detection task failed:

  Path type: single

  Network type: vxlan

  Segment ID: 2

  Source IP: 172.71.1.5

  Start device IP: 192.168.106.3

  Start device ingress port: ---

  Destination IP: 172.172.1.2

  End device IP: ---

Explanation

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

Recommended action

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

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

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

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

 

Periodic radar detection task result changes from failure to success

Keyword

PERIODIC_DETECTION_CHANGE__SUCCEEDED

Message text

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

Variable fields

$1: Periodic radar detection task parameters.

Severity level

Info

Example

Periodic radar detection task result changed from failure to success:

   Path type: single

   Network type: vxlan

   Segment ID: 2

   Source IP: 172.71.1.5

   Start device IP: 192.168.106.3

   Start device ingress port: XGE2/0/1

   Destination IP: 172.172.1.2

   End device IP: 192.168.70.68

Explanation

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

Recommended action

No action is required.

 

 


CON_OPENFLOW

This section contains CON_OPENFLOW messages.

Abnormal OpenFlow connection

Keyword

OPENFLOW_CONNECT_ERROR

Message text

$1

Variable fields

$1: Abnormal connection information.

Severity level

Critical

Example

N/A

Explanation

An OpenFlow connection was abnormal.

Recommended action

Take actions according to the prompted abnormal connection information.

 

Successful OpenFlow connection

Keyword

OPENFLOW_SESSION_UP

Message text

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

Variable fields

$1: Datapath ID of the OpenFlow device.

$2: Management IP address of the OpenFlow device.

$3: Description information about the OpenFlow device.

$4: IP address of the controller.

Severity level

Info

Example

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

Explanation

An OpenFlow device was connected to the controller.

Recommended action

No action is required.

 

Disconnected OpenFlow connection

Keyword

OPENFLOW_SESSION_DOWN

Message text

An OpenFlow device with datapath ID $1 openflow ip $2 descriptor $3 was disconnected from the controller $4.

Variable fields

$1: Datapath ID of the OpenFlow device.

$2: Management IP address of the OpenFlow device.

$3: Description information about the OpenFlow device.

$4: IP address of the controller.

Severity level

Info

Example

An OpenFlow device with datapath ID 01:21:cc:3e:5f:09:04:7f openflow ip 192.168.100.1 descriptor 192.168.200.1 was disconnected from the controller 10.10.10.1.

Explanation

An OpenFlow device was disconnected from the controller.

Recommended action

Log in to the operating system where the controller is installed, and use the ping command to test the connectivity between the controller and OpenFlow device.

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

·     Specify the management IP address of the OpenFlow device as the destination IP.

Log in to the OpenFlow device to verify that the OpenFlow configuration is correct.

 

OpenFlow port in up state

Keyword

OPENFLOW_DEVPORT_UP

Message text

Port $1 of an OpenFlow device with datapath ID $2 management IP $3 was up.

Variable fields

$1: Name of a physical port.

$2: Datapath ID of an OpenFlow device.

$3: Management IP address of the OpenFlow device.

Severity level

Info

Example

Port FGE1/0/1 of an OpenFlow device with datapath ID 01:21:cc:3e:5f:09:04:7f management IP 192.168.1.1 was up.

Explanation

A port on an OpenFlow device came up.

Recommended action

No action is required.

 

OpenFlow port in down state

Keyword

OPENFLOW_DEVPORT_DOWN

Message text

Port $1 of an OpenFlow device with datapath ID $2 management IP $3 was down.

Variable fields

$1: Name of a physical port.

$2: Datapath ID of an OpenFlow device.

$3: Management IP address of the OpenFlow device.

Severity level

Info

Example

Port FGE1/0/1 of an OpenFlow device with datapath ID 01:21:cc:3e:5f:09:04:7f management IP 192.168.1.1 was down.

Explanation

A port on an OpenFlow device went down.

Recommended action

If the message appears when the OpenFlow device reports its port information to the controller upon connecting to the controller, no action is required.

If the message appears in other situations, verify that the physical port operates correctly and the link where the port resides is up.

 

OpenFlow port removed

Keyword

OPENFLOW_DEVPORT_REMOVED

Message text

Port $1 of an OpenFlow device with datapath ID $2 management IP $3 was removed.

Variable fields

$1: Name of a port.

$2: Datapath ID of an OpenFlow device.

$3: Management IP address of the OpenFlow device.

Severity level

Info

Example

Port FGE1/0/1 of an OpenFlow device with datapath ID 01:21:cc:3e:5f:09:04:7f management IP 192.168.1.1 was removed.

Explanation

A port on an OpenFlow device was removed.

Recommended action

If the message appears when you delete or move a VM, no action is required.

If the message appears in other situations, verify that the physical port operates correctly.

 

Failure to deploy flow entries

Keyword

OPENFLOW_ADD_FLOWTABLE_FAILED

Message text

$1. The OpenFlow device with datapath ID $2 manager ip $3 failed to add the flow table $4.

Variable fields

$1: Error information returned by the OpenFlow device.

$2: Datapath ID of the OpenFlow device.

$3: Management IP address of the OpenFlow device.

$4: Flow table information.

Severity level

Warning

Example

BAD_FIELD. The OpenFlow device with datapath ID 01:21:cc:3e:5f:09:04:7f manager ip 192.168.10.10 failed to add the flow table

[tableId:1,Priority:29999,cookie0x2555364126,Matches:{“vxlan_reserved”:”0xFE”}].

Explanation

The controller failed to deploy flow entries to the specified OpenFlow device.

Recommended action

The controller deploys several flow entries to the OpenFlow device by default. If the OpenFlow device does not support such flow entries, update the OpenFlow device as required.

If the flow entries are deployed through REST API, modify the flow entries according to the error information returned and then deploy the flow entries again.

 

Packet-in message rate reaches threshold on controller

Keyword

OPENFLOW_CON_PACKETIN_EXCEED

Message text

The Packet-in message rate has reached the threshold on the controller. The current rate is $1 pps.

Variable fields

$1: Current packet-in message rate on the controller, in pps.

Severity level

Warning

Example

The Packet-in message rate has reached the threshold on the controller. The current rate is 8 pps.

Explanation

The packet-in message rate reached the threshold on the controller.

Recommended action

Modify the threshold for packet-in message rate on the controller.

 

Packet-in message rate reaches threshold on OpenFlow device

Keyword

OPENFLOW_DEV_PACKETIN_EXCEED

Message text

The Packet-in message rate has reached the threshold on OpenFlow device with DPID $1 and management IP $2. The current rate is $3 pps.

Variable fields

$1: Datapath ID of the OpenFlow device.

$2: Management IP address of the OpenFlow device.

$3: Current packet-in message rate on the OpenFlow device, in pps.

Severity level

Warning

Example

The Packet-in message rate has reached the threshold on OpenFlow device with DPID 00:00:00:00:00:01 and management IP 192.168.109.10. The current rate is 10 pps.

Explanation

The packet-in message rate reached the threshold on the OpenFlow device.

Recommended action

Modify the threshold for packet-in message rate on the OpenFlow device.

 

Packet-in message rate reaches threshold on OpenFlow device port

Keyword

OPENFLOW_PORT_PACKETIN_EXCEED

Message text

The Packet-in message rate has reached the threshold on port $1 of OpenFlow device with DPID $2 and management IP $3. The current rate is $4 pps.

Variable fields

$1: Number of the port on the OpenFlow device.

$2: Datapath ID of the OpenFlow device.

$3: Management IP address of the OpenFlow device.

$4: Current packet-in message rate on the OpenFlow device's port, in pps.

Severity level

Warning

Example

The Packet-in message rate has reached the threshold on port  68 of OpenFlow device with DPID 00:00:00:00:00:01 and management IP 192.168.109.11. The current rate is 15 pps.

Explanation

The packet-in message rate reached the threshold on the OpenFlow device's port.

Recommended action

Modify the threshold for packet-in message rate on the OpenFlow device's ports.

 

 


CON_PortMonitor

This section contains CON_PortMonitor messages.

Change of port operating status from healthy to unhealthy

Keyword

MONITOR_PORT_ABNORMAL

Message text

Port operating status changed to unhealthy:

  Device IP address: $1

  Port name: $2

  Inbound bandwidth usage: $3

  Outbound bandwidth usage: $4

  Inbound error packet rate: $5

  Outbound error packet rate: $6

  Inbound packet loss rate: $7

  Outbound packet loss rate: $8

Variable fields

$1: IP address of the device.

$2: Port name.

$3: Inbound bandwidth usage.

$4: Outbound bandwidth usage.

$5: Inbound error packet rate.

$6: Outbound error packet rate.

$7: Inbound packet loss rate.

$8: Outbound packet loss rate.

Severity level

Warning

Example

Port operating status changed to unhealthy:

  Device IP address: 172.16.100.222

  Port name: G1/0/1

  Inbound bandwidth usage: 10%

  Outbound bandwidth usage: 10%

  Inbound error packet rate: 10%

  Outbound error packet rate: 10%

  Inbound packet loss rate: 10%

  Outbound packet loss rate: 10%

Explanation

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

·     The bandwidth usage exceeds the threshold.

·     The error packet rate exceeds the threshold.

·     The packet loss rate exceeds the threshold.

Recommended action

Take actions based on the causes

 

Change of port operating status from unhealthy to healthy

Keyword

MONITOR_PORT_NORMAL

Message text

Port operating status changed from unhealthy to healthy:

  Device IP address: $1

  Port name: $2

  Inbound bandwidth usage: $3

  Outbound bandwidth usage: $4

  Inbound error packet rate: $5

  Outbound error packet rate: $6

  Inbound packet loss rate: $7

  Outbound packet loss rate: $8

Variable fields

$1: IP address of the device.

$2: Port name.

$3: Inbound bandwidth usage.

$4: Outbound bandwidth usage.

$5: Inbound error packet rate.

$6: Outbound error packet rate.

$7: Inbound packet loss rate.

$8: Outbound packet loss rate.

Severity level

Info

Example

Port operating status changed from unhealthy to healthy:

  Device IP address: 192.168.70.68

  Port name: XGE1/0/5

  Inbound bandwidth usage: 10%

  Outbound bandwidth usage: 20%

  Inbound error packet rate: 1%

  Outbound error packet rate: 1%

  Inbound packet loss rate: 0%

  Outbound packet loss rate: 0%

Explanation

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

Recommended action

No action is required.

 

 


CON_REGION

This section contains CON_REGION messages.

Region creation

Keyword

REGION_ADD

Message text

REGION_ADDED : ID: $1

Variable fields

$1: Region ID.

Severity level

Info

Example

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

Explanation

A region was created.

Recommended action

No action is required.

 

Region activation

Keyword

REGION_ACTIVE

Message text

REGION_ACTIVE : ID: $1

Variable fields

$1: Region ID.

Severity level

Info

Example

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

Explanation

A minimum of one member in the region was activated.

Recommended action

No action is required.

 

Region update

Keyword

REGION_UPDATE

Message text

REGION_UPDATED : ID: $1

Variable fields

$1: Region ID.

Severity level

Info

Example

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

Explanation

A region was updated.

Recommended action

No action is required.

 

Region down

Keyword

REGION_DOWN

Message text

REGION_DOWN : ID: $1

Variable fields

$1: Region ID.

Severity level

Info

Example

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

Explanation

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

Recommended action

No action is required.

 

Region deletion

Keyword

REGION_DELETE

Message text

REGION_DELETED: ID:  $1

Variable fields

$1: Region ID.

Severity level

Info

Example

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

Explanation

A region was deleted.

Recommended action

No action is required.

 

Failure to restore region settings

Keyword

REGION_RECOVER_FAILED

Message text

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

Variable fields

N/A

Severity level

Error

Example

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

Explanation

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

Recommended action

Log in to the active leader and create regions again.

 

Network device connection to a master

Keyword

REGION_SELECT_MASTER

Message text

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

Variable fields

$1: Datapath IDs of the network devices.

$2: Name of the master controller.

$3: IP address of the master controller.

Severity level

Info

Example

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

Explanation

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

Recommended action

No action is required.

 

Master change for network devices

Keyword

REGION_MASTER_CHANGE

Message text

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

Variable fields

$1: Datapath IDs of the network devices.

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

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

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

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

Severity level

Warning

Example

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

Explanation

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

Recommended action

No action is required.

 

Network device disconnection from a master

Keyword

DEVICE_DISCONNECT_MASTER

Message text

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

Variable fields

$1: Datapath IDs of the network devices.

$2: IP address of the master controller.

Severity level

Warning

Example

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

Explanation

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

Recommended action

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

19.     Verify that the network is connected.

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

 

OpenFlow device connection with multiple regions

Keyword

DEVICE_CONNECT_MULTIREGION

Message text

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

Variable fields

$1: Datapath ID of the network device.

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

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

Severity level

Emergency

Example

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

Explanation

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

Recommended action

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

 

Abnormal status of the other controller in the region

Keyword

REGION_CONTROLLER_STATUS_DOWN

Message text

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

Variable fields

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

Severity level

Emergency

Example

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

Explanation

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

Recommended action

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

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

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

 

Normal status of the other controller in the region

Keyword

REGION_CONTROLLER_STATUS_UP

Message text

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

Variable fields

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

Severity level

Info

Example

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

Explanation

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

Recommended action

No action is required.

 

 


CON_SNMP

This section contains CON_SNMP messages.

Traditional NE created SNMP connection with controller

Keyword

SNMP_SESSION_UP

Message text

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

Variable fields

$1: IP address of the traditional NE.

$2: IP address of the controller.

Severity level

Info

Example

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

Explanation

The traditional NE established an SNMP connection to the controller.

Recommended action

No action is required.

 

Traditional NE broke SNMP connection to controller

Keyword

SNMP_SESSION_DOWN

Message text

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

Variable fields

$1: IP address of the traditional NE.

$2: IP address of the controller.

Severity level

Warning

Example

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

Explanation

The traditional NE broke the SNMP connection to the controller.

Recommended action

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

 

Traditional NE port up

Keyword

TRADITIONAL_NE_PORT_UP

Message text

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

Variable fields

$1: Name of the traditional NE port.

$2: IP address of the traditional NE.

Severity level

Info

Example

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

Explanation

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

Recommended action

No action is required.

 

Traditional NE port down

Keyword

TRADITIONAL_NE_PORT_DOWN

Message text

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

Variable fields

$1: Name of the traditional NE port.

$2: IP address of the traditional NE.

Severity level

Warning

Example

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

Explanation

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

Recommended action

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

 

 


CON_SYSTEM

This section contains CON_SYSTEM messages.

Database operation failure because of a nonexistent user

Keyword

DATABASE_NO_USER

Message text

Database operation failed because the user did not exist.

Variable fields

N/A

Severity level

Emergency

Example

Database operation failed because the user did not exist.

Explanation

The database operation failed because the user did not exist.

Recommended action

Verify that the user is configured in the database.

 

Database operation failure because of refused connections

Keyword

DATABASE_CONNECTION_FAILED

Message text

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

Variable fields

$1: IP address of the controller.

Severity level

Emergency

Example

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

Explanation

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

Recommended action

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

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

 

End of controller configuration recovery

Keyword

FINISH_RECOVER_CONFIGURATIONS

Message text

Controller configuration recovery completed.

Variable fields

N/A

Severity level

Info

Example

Controller configuration recovery completed.

Explanation

Controller configuration recovery completed.

Recommended action

No action is required.

 

Controller configuration backup not performed when backup file exists

Keyword

BACKUP_CONFIGURATIONS_EXIST

Message text

The configuration file already exists.

Variable fields

N/A

Severity level

Info

Example

The configuration file already exists.

Explanation

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

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

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

Recommended action

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

 

Failed to send the backup file to the remote server

Keyword

BACKUP_FILE_SEND_FAILED

Message text

Failed to send the backup file to the remote server.

Variable fields

N/A

Severity level

Warning

Example

Failed to send the backup file to the remote server.

Explanation

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

Recommended action

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

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

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

 

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

Keyword

BACKUP_REACH_SIX_SAMETIME

Message text

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

Variable fields

N/A

Severity level

Warning

Example

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

Explanation

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

Recommended action

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

 

 


CON_TEAM

This section contains CON_TEAM messages.

Failure to delete team IP

Keyword

DELETE_TEAMIP_FAILED

Message text

Failed to delete team IP $1.

Variable fields

$1: Team IP address.

Severity level

Warning

Example

Failed to delete team IP 192.168.56.211.

Explanation

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

·     The team is deleted.

·     An active leader switchover occurs.

Recommended action

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

 

Controller suspended

Keyword

BECOME_SUSPENDED

Message text

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

Variable fields

$1: Member controller ID.

$2: Member controller IP address.

$3: Member controller name.

$4: Name of the team.

$5: Team IP address.

Severity level

Warning

Example

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

Explanation

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

Recommended action

No action is required.

 

Member joined team

Keyword

MEMBER_JOIN

Message text

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

Variable fields

$1: Member controller ID.

$2: Member controller IP address.

$3: Member controller name.

$4: Name of the team.

$5: Team IP address.

Severity level

Info

Example

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

Explanation

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

Recommended action

No action is required.

 

Active leader changed

Keyword

MEMBER_TO_LEADER

Message text

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

Variable fields

$1: Member controller ID.

$2: Member controller IP address.

$3: Member controller name.

$4: Name of the team.

$5: Team IP address.

Severity level

Warning

Example

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

Explanation

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

Recommended action

No action is required.

 

Controller became active leader

Keyword

BECOME_LEADER

Message text

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

Variable fields

$1: Member controller ID.

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

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

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

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

Severity level

Info

Example

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

Explanation

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

Recommended action

No action is required.

 

Controller became member

Keyword

BECOME_MEMBER

Message text

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

Variable fields

$1: Member controller ID.

$2: Member controller IP address.

$3: Member controller name.

$4: Name of the team.

$5: Team IP address.

Severity level

Info

Example

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

Explanation

A team event occurred: The controller joined the team.

Recommended action

No action is required.

 

Member left team unexpectedly

Keyword

MEMBER_LEAVE

Message text

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

Variable fields

$1: Member controller ID.

$2: Member controller IP address.

$3: Team name.

$4: Team IP address.

Severity level

Warning

Example

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

Explanation

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

Recommended action

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

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

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

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

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

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

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

¡     netstat -anut | grep 2181

¡     netstat -anut | grep 2888

¡     netstat -anut | grep 3888

 

Member left team expectedly

Keyword

MEMBER_LEAVE

Message text

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

Variable fields

$1: Member controller ID.

$2: Team name.

$3: Team IP address.

Severity level

Info

Example

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

Explanation

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

Recommended action

No action is required.

 

Different team token than the active leader

Keyword

TEAMTOKEN_DIFF

Message text

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

Variable fields

$1: IP address of the member controller.

Severity level

Warning

Example

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

Explanation

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

Recommended action

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

 

Reboot for completing team merge

Keyword

LEADER_CONFILICT

Message text

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

Variable fields

$1: IP address of the controller.

Severity level

Emergency

Example

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

Explanation

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

Recommended action

No action is required.

 

Reboot to act as the leader

Keyword

ILLEGAL_ROLE_CHANGE

Message text

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

Variable fields

$1: IP address of the controller.

Severity level

Emergency

Example

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

Explanation

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

Recommended action

No action is required.

 


CON_USER

This section contains CON_USER messages.

Login success

Keyword

LOGGED_IN_SUCCEED

Message text

User $1 successfully logged in by using the role $2 and the IP address $3.

Variable fields

$1: Username.

$2: User role, including:

¡     sdn-admin.

¡     sdn-user.

$3: IP address of the user.

Severity level

Info

Example

User sdn successfully logged in by using the role sdn-admin and the IP address 192.168.1.1.

Explanation

A user logged into the device.

Recommended action

No action is required.

 

Login failure

Keyword

LOGGED_IN_FAILED

Message text

User $1 failed to log in by using the IP address $2.

Variable fields

$1: Username.

$2: IP address of the user.

Severity level

Info

Example

User sdn failed to log in by using the IP address 192.168.1.1.

Explanation

A user failed to log into the device. The message appears in any of the following situations:

·     The username is incorrect.

·     The password is incorrect.

Recommended action

Check the entered username and password.

 

User lock

Keyword

USER_LOCKED

Message text

The user $1 failed to log in because the login failures has reached five times, and the user is locked.

Variable fields

$1: Username.

Severity level

Info

Example

The user sdn failed to log in because the login failures has reached five times, and the user is locked.

Explanation

The user account was locked because the user failed to log in to the controller for five consecutive times.

Recommended action

Verify that the username and password are correct. The user account will be unlocked in 15 minutes or after a controller reboot.

 

Logout success

Keyword

LOGGED_OUT_SUCCEED

Message text

User $1 successfully logged out by using the role $2 and the IP address $3.

Variable fields

$1: Username.

$2: User role, including:

¡     sdn-admin.

¡     sdn-user.

$3: IP address of the user.

Severity level

Info

Example

User sdn successfully logged out by using the role sdn-admin and the IP address 192.168.1.1.

Explanation

A user logged out of the device.

Recommended action

No action is required.

 

RADIUS authentication success

Keyword

RADIUS_AUTHENTICATION_PASS

Message text

User $1 passed the RADIUS authentication.

Variable fields

$1: Username.

Severity level

Info

Example

User User1 passed the RADIUS authentication.

Explanation

A user passed RADIUS authentication.

Recommended action

No action is required.

 

RADIUS authentication rejection

Keyword

RADIUS_AUTHENTICATION_REJECT

Message text

The RADIUS authentication request from user $1 was rejected.

Variable fields

$1: Username.

Severity level

Warning

Example

The RADIUS authentication request from user User1 was rejected.

Explanation

A user was rejected for RADIUS authentication. The message appears in any of the following situations:

·     The user does not exist.

·     The password is incorrect.

Recommended action

Check the entered username and password.

 

RADIUS authentication failure

Keyword

RADIUS_AUTHENTICATION_FAILED

Message text

User $1 failed to pass the RADIUS authentication.

Variable fields

$1: Username.

Severity level

Warning

Example

User User1 failed to pass the RADIUS authentication.

Explanation

A user failed to pass RADIUS authentication.

Recommended action

Resolve the issue in the following steps:

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

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

26.     Verify that the controller can communicate with the AAA server correctly.

 

RADIUS attribute check failure

Keyword

RADIUS_ATTRIBUTE_CHECK_FAILED

Message text

User $1 failed to pass the RADIUS authentication because attribute H3C_EXEC_PRIVILEGE was not configured.

Variable fields

$1: Username.

Severity level

Warning

Example

User User1 failed to pass the RADIUS authentication because attribute H3C_EXEC_PRIVILEGE was not configured.

Explanation

The RADIUS authentication failed because the H3C proprietary attribute was not configured.

Recommended action

Verify that the H3C_EXEC_PRIVILEGE attribute is configured on the AAA server.

 

TACACS+ authentication success

Keyword

TACACS+_AUTHENTICATION_PASS

Message text

User $1 passed the TACACS+ authentication.

Variable fields

$1: Username.

Severity level

Info

Example

User User1 passed the TACACS+ authentication.

Explanation

A user passed TACACS+ authentication.

Recommended action

No action is required.

 

TACACS+ authentication rejection

Keyword

TACACS+_AUTHENTICATION_REJECT

Message text

The TACACS+ authentication request from user $1 was rejected.

Variable fields

$1: Username.

Severity level

Warning

Example

The TACACS+ authentication request from user User1 was rejected.

Explanation

A user was rejected for TACACS+ authentication. The message appears in any of the following situations:

·     The user does not exist.

·     The password is incorrect.

Recommended action

Check the entered username and password.

 

TACACS+ authentication failure

Keyword

TACACS+_AUTHENTICATION_FAILED

Message text

User $1 failed to pass the TACACS+ authentication.

Variable fields

$1: Username.

Severity level

Warning

Example

User User1 failed to pass the TACACS+ authentication.

Explanation

A user failed to pass TACACS+ authentication.

Recommended action

Resolve the issue in the following steps:

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

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

29.     Verify that the controller can communicate with the AAA server correctly.

 

TACACS+ attribute check failure

Keyword

TACACS+_ATTRIBUTE_CHECK_FAILED

Message text

User $1 failed to pass the TACACS+ authentication because attribute H3C_EXEC_PRIVILEGE was not configured.

Variable fields

$1: Username.

Severity level

Warning

Example

User User1 failed to pass the TACACS+ authentication because attribute H3C_EXEC_PRIVILEGE was not configured.

Explanation

The TACACS+ authentication failed because the H3C proprietary attribute was not configured.

Recommended action

Verify that the H3C_EXEC_PRIVILEGE attribute is configured on the AAA server.

 

Start of user configuration recovery on non-active leader controllers

Keyword

BEGIN_RECOVER_USER_CONFIG

Message text

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

Variable fields

N/A

Severity level

Info

Example

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

Explanation

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

Recommended action

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

 

End of user configuration recovery on non-active leader controllers

Keyword

FINISH_RECOVER_USER_CONFIG

Message text

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

Variable fields

N/A

Severity level

Info

Example

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

Explanation

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

Recommended action

No action is required.

 

Operation failure due to user role privilege limit

Keyword

ROLE_PERMISSION_CHECK_FAILED

Message text

Failed to $1 $2. The user role doesn’t have the permission.

Variable fields

$1: Request type:

·     post—Creates a resource.

·     put—Updates or creates a resource.

·     delete—Deletes a resource.

·     getGets resource information.

$2: Requested resource path.

Severity level

Error

Example

Failed to put /sdn/v2.0/systems/4ff280bd-51c6-4768-9be4-4f9f72b51b77. The user role doesn’t have the permission.

Explanation

The user role does not have the permission to send the request.

Recommended action

Modify the privilege for the user role or use another user role that has the permission to send the request.

 

User password expiration

Keyword

USER_EXPIRED_CHECK

Message text

Password for user $1 expired. Please change the password immediately.

Variable fields

$1: User name.

Severity level

Error

Example

Password for user admin expired. Please change the password immediately.

Explanation

The password of a user expired.

Recommended action

Set a new password for the user.

 

 


DATACHECK

This section contains data check messages.

Controller failed data entry count consistency check

Keyword

CONFIG_NUM_CHECK_DIFF

Message text

Controller $1 failed to pass the data entry count consistency check.

Variable fields

$1: Controller IP address.

Severity level

Warning

Example

Controller 192.168.103.39 failed to pass the data entry count consistency check.

Explanation

The controller failed to pass the data entry count consistency check.

Recommended action

Verify that the number of data entries in the database and memory are consistent for the controller.

 

Controller passed data entry count consistency check

Keyword

CONFIG_NUM_CHECK_CONSISTENT

Message text

Controller $1 passed the data entry count consistency check.

Variable fields

$1: Controller IP address.

Severity level

Info

Example

Controller 192.168.103.39 passed the data entry count consistency check.

Explanation

The controller passed the data entry count consistency check.

Recommended action

No action is required.

 

Failure to obtain data entry count consistency check result for controller

Keyword

CONFIG_NUM_CHECK_FAILED

Message text

Failed to obtain the data entry count consistency check result for controller $1.

Variable fields

$1: Controller IP address.

Severity level

Warning

Example

Failed to obtain the data entry count consistency check result for controller 192.168.103.39.

Explanation

Failed to obtain the data entry count consistency check result for the controller.

Recommended action

Check error information recorded in diagnosis logs on the controller.

 

Controller passed local data entry count consistency check

Keyword

CONTENT_LOCAL_CHECK_CONSISTENT

Message text

Controller $1 passed the local data entry count consistency check.

Variable fields

$1: Controller IP address.

Severity level

Info

Example

Controller $1 passed the local data entry count consistency check.

Explanation

The controller passed the local data entry count consistency check.

Recommended action

No action is required.

 

Controller failed local data entry count consistency check

Keyword

CONTENT_LOCAL_CHECK_DIFF

Message text

Controller $1 failed to pass the local data content consistency check.

Variable fields

$1: Controller IP address.

Severity level

Warning

Example

Controller 192.168.103.39 failed to pass the local data content consistency check.

Explanation

The controller failed to pass the local data entry count consistency check.

Recommended action

Check error information recorded in diagnosis logs on the controller.

 

Failure to obtain local data entry count consistency check result for controller

Keyword

CONTENT_LOCAL_CHECK_FAILED

Message text

Failed to obtain the local data content consistency check result for controller $1.

Variable fields

$1: Controller IP address.

Severity level

Warning

Example

Failed to obtain the local data content consistency check result for controller 192.168.103.39.

Explanation

Failed to obtain the local data entry count consistency check result for the controller.

Recommended action

Check error information recorded in diagnosis logs on the controller.

 

Controller passed cluster data content consistency check

Keyword

CONTENT_TEAM_CHECK_CONSISTENT

Message text

Controller $1 passed the cluster data content consistency check.

Variable fields