With system log information, network administrators can monitor device running status, analyze network status, find network or security problems, and take corresponding actions against them.

You can display the system log information through the console port or by telnetting. The device can save logs or output them to the log server.

System Log Format

According to the syslog protocol, the system transmits logs through UDP port 514. Any UDP packet on port 514 is considered as a log message, which uses the following format.

<PRI>timestamp sysname %%vvmodule/level/digest: source content

1 2 3 4 5 6 7 8 9 10

Table 1 Description of a log message

Number	Description
1	Priority
2	Timestamp
3	Host name
4	Manufacturer
5	Version
6	Module name
7	Severity level
8	Message summary
9	Message creator
10	Message content

The system messages sent to log hosts are log messages.

The priority is calculated using the formula: facility*8+severity, in which facility is the logging facility name and can be configured when you set the log host parameters. The facility ranges from local0 to local7 (16 to 23 in decimal integers) and defaults to local7. It is mainly used to mark different log sources on the log host, query and filter the logs of the corresponding log source. Severity ranges from 0 to 7. Table 2 details the value and meaning associated with each severity.

Note that the priority field takes effect only when the information has been sent to the log host.

Table 2 Severity description

Severity	Severity value	Description
Emergency	0	The system is unusable.
Alert	1	Action must be taken immediately.
Critical	2	Critical conditions
Error	3	Error conditions
Warning	4	Warning conditions
Notice	5	Normal but significant conditions
Informational	6	Informational messages
Debug	7	Debug-level messages

timestamp

Time stamp records the time when system information is generated to allow users to check and identify system events. The time stamp of the system information sent from the information center to the log host is with a precision of milliseconds. The time stamp format of the system information sent to the log host is configured with the info-center timestamp loghost command, and that of the system information sent to the other destinations is configured with the info-center timestamp command. For the detailed description of the time stamp parameters, see the following table:

Table 3 Description on the time stamp parameters

Time stamp parameter	Description	Example
boot	System up time (that is, the duration for this operation of the device), in the format of xxxxxx.yyyyyy. xxxxxx represents the higher 32 bits, and yyyyyy represents the lower 32 bits. System information sent to all destinations except log host supports this parameter.	%0.16406399 Sysname IFNET/3/LINK_UPDOWN: Ethernet0/6 link status is DOWN. 0.16406399 is a time stamp in the boot format.
date	Current date and time of the system, in the format of Mmm dd hh:mm:ss:sss yyyy. System information sent to all destinations supports this parameter.	%Aug 19 16:11:03:288 2009 Sysname IFNET/3/LINK_UPDOWN: Ethernet0/6 link status is UP. Aug 19 16:11:03:288 2009 is a time stamp in the date format.
iso	Time stamp format stipulated in ISO 8601 Only the system information sent to a log host supports this parameter.	<187>2009-09-21T15:32:55 Sysname %%10 IFNET/3/LINK_UPDOWN(l): Ethernet0/6 link status is DOWN. 2009-09-21T15:32:55 is a time stamp in the iso format.
none	No time stamp is included. System information sent to all destinations supports this parameter.	% Sysname IFNET/3/LINK_UPDOWN: Ethernet0/6 link status is DOWN. No time stamp is included.
no-year-date	Current date and time of the system, with year information excluded. Only the system information sent to a log host supports this parameter.	<187>Aug 19 16:120:38 Sysname %%10 IFNET/3/LINK_UPDOWN(l): Ethernet0/6 link status is DOWN. Aug 19 16:120:38 is a time stamp in the no-year-date format.

Time stamp parameter

Description

Example

boot

System up time (that is, the duration for this operation of the device), in the format of xxxxxx.yyyyyy. xxxxxx represents the higher 32 bits, and yyyyyy represents the lower 32 bits.

System information sent to all destinations except log host supports this parameter.

%0.16406399 Sysname IFNET/3/LINK_UPDOWN: Ethernet0/6 link status is DOWN.

0.16406399 is a time stamp in the boot format.

date

Current date and time of the system, in the format of Mmm dd hh:mm:ss:sss yyyy.

System information sent to all destinations supports this parameter.

%Aug 19 16:11:03:288 2009 Sysname IFNET/3/LINK_UPDOWN: Ethernet0/6 link status is UP.

Aug 19 16:11:03:288 2009 is a time stamp in the date format.

iso

Time stamp format stipulated in ISO 8601

Only the system information sent to a log host supports this parameter.

<187>2009-09-21T15:32:55 Sysname %%10 IFNET/3/LINK_UPDOWN(l): Ethernet0/6 link status is DOWN.

2009-09-21T15:32:55 is a time stamp in the iso format.

none

No time stamp is included.

System information sent to all destinations supports this parameter.

% Sysname IFNET/3/LINK_UPDOWN: Ethernet0/6 link status is DOWN.

No time stamp is included.

no-year-date

Current date and time of the system, with year information excluded.

Only the system information sent to a log host supports this parameter.

<187>Aug 19 16:120:38 Sysname %%10 IFNET/3/LINK_UPDOWN(l): Ethernet0/6 link status is DOWN.

Aug 19 16:120:38 is a time stamp in the no-year-date format.

sysname (host name or IP address)

· If the system information is sent to a log host in the format of UNICOM, and the info-center loghost source command is configured, or vpn-instance vpn-instance-name is provided in the info-center loghost command, the field is displayed as the IP address of the device that generates the system information.

· In other cases (when the system information is sent to a log host in the format of H3C, or sent to other destinations), the field is displayed as the name of the device that generates the system information, namely, the system name of the device. You can use the sysname command to modify the system name. For more information, see the Fundamentals Command Reference.

%% (vendor ID)

This field indicates that system information is generated by a H3C device. It is displayed only when the system information is sent to a log host in the format of H3C.

vv (version)

This field is a version identifier of syslog, with a value of 10. It is displayed only when the output destination is log host.

module

This field represents the name of the module that generates system information. You can enter the info-center source? command in system view to view the module list

level (severity)

System information can be divided into eight levels based on its severity, from 0 to 7. See Table 2for definition and description of these severity levels. The levels of system information generated by modules are predefined by developers, so you cannot change the system information levels. However, with the info-center source command, you can configure to output information of the specified level and not to output information lower than the specified level.

digest

The digest field is a string of up to 32 characters, outlining the system information.

For system information destined to the log host:

· If the character string ends with (l), the information is log information

· If the character string ends with (t), the information is trap information

· If the character string ends with (d), the information is debugging information

For system information destined to other destinations:

· If the time stamp starts with a %, the information is log information

· If the time stamp starts with a #, the information is trap information

· If the time stamp starts with a *, the information is debugging information

source

This field indicates the source of the information.This field is optional and is displayed only when the system information is sent to a log host in the format of H3C.

content

This field provides the content of the system information.

For example:

%@354%Feb 15 19:03:21:985 2011 H3C CFGMAN/5/CFGMAN_EXIT: Exit from configuration mode.

The information shows that this log is generated on Feb. 15 19: 03:21 2011, and is sent by module CFGMAN, the host name is H3C, severity level is 5, and the content of the log is exit from configure mode.

Modules

Table 4 Module list

Module Name	Full spelling
ADDR	IPv4 address management
ADDR6	IPv6 address management
ACL	Access Control List
ACFPC	Application Control Forwarding Protocol Client
ARP	Address Resolution Protocol
ASPF	Application Specific Packet Filter
BFD	Bidirectional Forwarding Detection
BGP	Border Gateway Protocol
BLS	Blacklist
CFD	Connectivity Fault Detection
CFGMAN	Configuration Management
CFM	Configuration File Management
CLST	Cluster
CLKM	Clock Management
CMD	Command
CSPF	Constraint Shortest Path First
DAR	Deeper Application Recognition
DEVM	Device Management
DHBK	Double Hot Backup
DHCPC	Dynamic Host Configuration Protocol Client
DHCPR	Dynamic Host Configuration Protocol Relay
DHCPRULE	Dynamic Host Configuration Protocol Rule
DHCPS	Dynamic Host Configuration Protocol Server
DHCPSP6	DHCPv6 Snooping
DLDP	Device Link Detection Protocol
DOT1X	DOT1X
DPATTACK	Data Plane Attack defense
DPBRIDGE	Data Plane Bridge
DPCNNLMT	Data Plane Connection limit
DPPBR	Data Plane Policy Based Route
DPPBR6	Data Plane Policy Based Route IPv6
DPURPF	Data Plane Unicast Reverse Path Forwarding
DPVFR	Data Plane Virtual Fragment Reassembly
ETHOAM	Ethernet Operation, Administration and Maintenance
FLT6	Filter of IPv6
FILTER	Filter of IPv4
FTP Daemon	File Transfer Protocol Daemon
HA	High Availability
HOSTTRAF	Host traffic
IC	Information Center
IFNET	Interface Net Management
IKE	Internet Key Exchange
IPCIM	IP Client Information Management
IPSEC	IP Security
IPV6PP	Internet Protocol Version 6 Packet Process Management
ISIS	Intermediate System-to-Intermediate System
L2V	Layer 2 Virtual Private Network
L3VPN	Layer 3 Virtual Private Network
LAGG	Link Aggregation
LDP	Label Distribution Protocol
LICS	License
LLDP	Link Layer Discovery Protocol
LPDETECT	Loop Detect
LPDT	Loopback Detection
LS	Local Server
LSPM	LSP Management
LSPV	LSP Verification
LWPC	Light Weight Access Point Protocol client
LWPS	Light Weight Access Point Protocol server
MAC	Media Access Control
MAD	Multi-Active Detection
MD	Multicast domain
MEM	Memory Management
MFF	MAC-Forced Forwarding
MFW	MPLS Forwarding
MPLS OAM	MPLS Operation Administration and Maintenance
MSDP	Multicast Source Discovery Protocol
MSTP	Multiple Spanning Tree Protocol
MTLK	Monitor Link
NAT	Network Address Translation
ND	Neighbor Discovery
NTP	Network Time Protocol
OPTMOD	Optical Module
OSPF	Open Shortest Path First
OSPFv3	Open Shortest Path First Version 3
PBR	Policy Based Route
PBR6	Policy Based Route IPv6
PIM	Protocol Independent Multicast
PKEY	Public Key
PKI	Public Key Infrastructure
PORTAL	PORTAL
PORTSEC	PORTSEC
PPPOEC	Point to Point Protocol Over Ethernet Client
PS	Protection Switch
QINQ	802.1Q IN 802.1Q
QOS	Quality of Service
RDS	RADIUS
RIP	Routing Information Protocol
RIPNG	Routing Information Protocol Next Generation
RM	Routing Management
RMON	Remote Monitor
RPR	Resilient Packet Ring
RRPP	Rapid Ring Protect Protocol
RSVP	Resource Reservation Protocol
SC	Service Control
SHELL	Shell
SLBG	Service Loopback Group
SMLK	Smart Link
SNMP	Simple Network Management Protocol
SOCKET	SOCKET
SSH	Secure Shell
STM	Stack Topology Management
SVPN	Virtual Private Network based on Security Socket Layer
TNLM	Tunnel Management
URPF	Unicast Reverse Path Forwarding
USERLOG	User Log
UTM	Unified Threat Management
VFR	Virtual Fragment Reassembly
VFS	Virtual File System
VRRP	Virtual Router Redundancy Protocol
WIDS	WLAN Intrusion Detection system
WMAC	WLAN MAC
WMESH	WLAN Mesh
WROAM	WLAN Roaming
WEBOPT	Web Operation APPCTL is short for Application Control LDBL is short for Load Balance LS is short for Local User IC is short for Information Center

Support for the following modules depends on the device model.

Module Name	Supported Device	Not Supported Device
RIP	S2100,S3110, S5000PV2-EI,S5110,S5110-D, S5110-SI,IE4100,IE4300	S1850,S2600,S3110-SI
OSPF	S2100,S3110	S1850,S2600,S3110-SI,S5000PV2-EI, S5110, S5110-D,S5110-SI,IE4100,IE4300,
QINQ	S2100,S3110, S5000PV2-EI, S5110,S5110-D,S5110-SI,IE4100,IE4300	S1850,S2600,S3110-SI,

ADDR Messages

This section contains the entire system log messages related to ADDR.

ADDR_SETDRIVER_FAIL

Message text	-TaskId=[ULONG]-TaskName=[STRING]-BoardId=[ULONG]-IPAddr=[IPADDR]-IfName=[STRING]; Failed to add or delete IP address to or from driver.
Variable fields	$1: Task ID. $2: Task name. $3: Board ID. $4: IP address. $5: Interface name.
Severity level	3
Example	ADDR/3/ADDR_SETDRIVER_FAIL: -TaskId=1-TaskName=IP-BoardId=1-IPAddr=1.1.1.1-IfName=GigabitEthernet1/0/1; Failed to add or delete IP address to or from driver.
Explanation	Failed to add or delete IP address to/from driver.
Recommended action	No action is required.

ADDR6 Messages

This section contains the entire system log messages related to ADDR6.

ADDR6_ADD_ADDR_FAIL

Message text	IPv6 address [STRING] add error on [STRING] slot [ULONG].
Variable fields	$1: IPv6 address. $2: Chassis number. $3: Slot number.
Severity level	4
Example	ADDR6/4/ADDR6_ADD_ADDR_FAIL: IPv6 address 2::2 add error on slot 3.
Explanation	IPv6 address add error on IO board.
Recommended action	No action is required.

ACL Messages

This section contains the entire system log messages related to ACL.

ACL_NOT_ENOUGH_RES

Message text	Error occurred in ACL [ULONG] for not enough resource.
Variable fields	$1: The acl group ID.
Severity level	3
Example	ACL/3/ACL_NOT_ENOUGH_RES:Error occurred in ACL 3000 for not enough resource.
Explanation	There is no enough resource for the synchronization of acl group to driver.
Recommended action	Delete the acl group.

ACL_OTHER_ERROR

Message text	Error occurred in ACL [ULONG].
Variable fields	$1: The acl group ID.
Severity level	3
Example	ACL/3/ ACL_OTHER_ERROR:Error occurred in ACL 3000.
Explanation	Other error occurred when synchronization acl to driver.
Recommended action	Delete the acl group.

ACL_RULE_NOT_ENOUGH_RES

Message text	Error occurred in ACL [ULONG] rule [ULONG] for not enough resource.
Variable fields	$1: The acl group ID. $2: The acl rule ID.
Severity level	3
Example	ACL/3/ACL_RULE_NOT_ENOUGH_RES: Error occurred in ACL 3000 rule 100 for not enough resource.
Explanation	There is no enough resource for the synchronization of acl rule to driver.
Recommended action	Delete the acl rule.

ACL_RULE_OTHER_ERROR

Message text	Error occurred in ACL [ULONG] rule [ULONG].
Variable fields	$1: The acl group ID. $2: The acl rule ID.
Severity level	3
Example	ACL/3/ACL_RULE_OTHER_ERROR: Error occurred in ACL 3000 RULE 100.
Explanation	Other error occurred when synchronization acl rule to driver.
Recommended action	Delete the acl rule.

ACL_IPV6_NOT_ENOUGH_RES

Message text	Error occurred in ACL IPv6 [ULONG] for not enough resource.
Variable fields	$1: The acl group ID.
Severity level	3
Example	ACL/3/ACL_IPV6_NOT_ENOUGH_RES:Error occurred in ACL IPv6 3000 for not enough resource.
Explanation	There is no enough resource for the synchronization of acl group to driver.
Recommended action	Delete the acl group.

ACL_IPV6_OTHER_ERROR

Message text	Error occurred in ACL IPv6 [ULONG].
Variable fields	$1: The acl group ID.
Severity level	3
Example	ACL/3/ACL_IPV6_OTHER_ERROR: Error occurred in ACL IPv6 3000.
Explanation	Other error occurred when synchronization acl to driver.
Recommended action	Delete the acl group.

ACL_IPV6_RULE_NOT_ENOUGH_RES

Message text	Error occurred in ACL IPv6 [ULONG] rule [ULONG] for not enough resource.
Variable fields	$1: The acl group ID. $2: The acl rule ID.
Severity level	3
Example	ACL/3/ACL_IPV6_RULE_NOT_ENOUGH_RES: Error occurred in ACL IPv6 3000 rule 100 for not enough resource.
Explanation	There is no enough resource for the synchronization of acl rule to driver.
Recommended action	Delete the acl rule.

ACL_IPV6_RULE_OTHER_ERROR

Message text	Error occurred in ACL IPv6 [ULONG] rule [ULONG].
Variable fields	$1: The acl group ID. $2: The acl rule ID.
Severity level	3
Example	ACL/3/ACL_IPV6_RULE_OTHER_ERROR: Error occurred in ACL IPv6 3000 RULE 100.
Explanation	Other error occurred when synchronization acl rule to driver.
Recommended action	Delete the acl rule.

ARP Messages

This section contains the entire system log messages related to ARP.

ARP_DUPIFIP

Message text	Duplicate address [IPADDR] on interface [STRING], sourced from [STRING].
Variable fields	$1: IP address. $2: Interface name. $3: MAC Address.
Severity level	5
Example	ARP/5/ARP_DUPIFIP: Duplicate address 1.1.1.1 on interface Vlan-interface1, sourced from 0015-E944-A947.
Explanation	The ARP checks the duplicate address.
Recommended action	Modify the IP address configuration.

ARP_DETECTION_SETDRIVER_FAIL

Message text	ARP Detection Warning: Failed to enable ARP detection on driver.
Variable fields
Severity level	3
Example	ARP/3/ARP_DETECTION_SETDRIVER_FAIL: ARP Detection Warning: Failed to enable ARP detection on driver.
Explanation	The driver failed to set ARP detection.
Recommended action	No action is required.

ARP_SRC_MAC_FOUND_ATTACK

Message text	An attack from MAC [STRING] was detected on interface [STRING].
Variable fields	$1: MAC address. $2: Interface name.
Severity level	6
Example	ARP/6/ARP_SRC_MAC_FOUND_ATTACK: An attack from MAC 0000-5E14-0E00 was detected on interface Ethernet1/0/1.
Explanation	An attack was detected by source MAC address based ARP attack detection.
Recommended action	Check the host with the source MAC address.

ARP_MULTIPORT_FULL

Message text	The maximum number of multiport ARP entries has been reached.
Variable fields	NA
Severity level	5
Example	ARP/5/ARP_MULTIPORT_FULL: The maximum number of multiport ARP entries has been reached.
Explanation	The maximum number of multiport ARP entries has been reached.
Recommended action	Delete a multiport ARP entry.

CFD Messages

This section contains all the system log messages related to CFD.

CFD_ENABLE

Message text	CFD is now enabled on the device.
Variable fields
Severity level	2
Example	CFD/2/CFD_ENABLE: CFD is now enabled on the device.
Explanation	CFD is enabled.
Recommended action	No action is required.

CFD_DISABLE

Message text	CFD is now disabled on the device.
Variable fields
Severity level	2
Example	CFD/2/CFD_DISABLE: CFD is now disabled on the device.
Explanation	CFD is disabled.
Recommended action	No action is required.

CFD_CROSS_CCM

Message text	MEP [string] in SI [string] received a cross-connect CCM. It’s SrcMAC is [string], SeqNum is 0x[string], RMEP is [string], MdName is [string], MaName is [string].
Variable fields	$1: Service instance ID $2: Local MEP ID $3: Source MAC address $4: Sequence Number $5: Remote MEP ID $6 MD name $7 MA name
Severity level	3
Example	CFD/3/CFD_CROSS_CCM: MEP 1 in SI 1 received a cross-connect CCM. It’s SrcMAC is 000f-e200-0001, SeqNum is 0x3254, RMEP is 2, MdName is md1, MaName is ma1.
Explanation	A MEP received a cross-connect CCM.
Recommended action	Check the links and the MA name configuration.

CFD_ERROR_CCM

Message text	MEP [string] in SI [string] received an error CCM. It’s SrcMAC is [string], SeqNum is 0x[string], RMEP is [string], MdName is [string], MaName is [string].
Variable fields	$1: Service instance ID $2: Local MEP ID $3: Source MAC address $4: Sequence Number $5: Remote MEP ID $6 MD name $7 MA name
Severity level	3
Example	CFD/3/CFD_ERROR_CCM: MEP 1 in SI 1 received an error CCM. It’s SrcMAC is 000f-e200-0001, SeqNum is 0x3254, RMEP is 5, MdName is md1, MaName is ma1.
Explanation	A MEP received an error CCM.
Recommended action	Check the CCM configuration.

CFD_LOST_CCM

Message text	MEP [string] in SI [string] failed to receive CCMs from RMEP [string].
Variable fields	$1: Local MEP ID $2: Service instance ID $3: Remote MEP ID
Severity level	4
Example	CFD/4/CFD_LOST_CCM: MEP 1 in SI 1 failed to receive CCMs from RMEP 2.
Explanation	A MEP failed to receive CCMs within 3.5 sending periods.
Recommended action	Check the link and the configuration of the remote MEP.

CFD_RECEIVE_CCM

Message text	MEP [string] in SI [string] received CCMs from RMEP [string].
Variable fields	$1: Local MEP ID $2: Service instance ID $3: Remote MEP ID
Severity level	4
Example	CFD/4/CFD_RECEIVE_CCM: MEP 1 in SI 1 received CCMs from RMEP 2.
Explanation	A MEP received CCMs from a remote MEP.
Recommended action	No action is required.

CFGMAN Messages

This section contains the entire system log messages related to CFGMAN.

CFGMAN_CFGCHANGED

Message text	-EventIndex=[INTEGER]-CommandSource=[INTEGER]-ConfigSource=[INTEGER]-ConfigDestination=[INTEGER]; Configuration is changed.
Variable fields	$1: Event index $2: Command source $3: Configuration source $5: Configuration destination
Severity level	5
Example	CFGMAN/5/CFGMAN_CFGCHANGED: -EventIndex=13-CommandSource=1-ConfigSource=3-ConfigDestination=2; Configuration is changed.
Explanation	Running-configuration is changed.
Recommended action	Please save current configuration if necessary.

CFGMAN_CFGCOPY

Message text	-OptType=[INTEGER]-OptTime=[TIMETICK]-OptState=[INTEGER]-OptEndTime=[TIMETICK]; Configuration is copied.
Variable fields	$1: Operation type $2: Operation time $3: Operation state $4: End time of operation
Severity level	5
Example	CFGMAN/5/CFGMAN_CFGCOPY: -OptType=6-OptTime=12-OptState=2-OptEndTime=10682324; Configuration is copied.
Explanation	Configuration was copied or saved by SNMP.
Recommended action	No action is required.

CFM Messages

This section contains the entire system log messages related to CFM.

CFM_SAVECONFIG_FAILED

Message text	Failed to save configuration!
Variable fields	N/A
Severity level	3
Example	CFM/3/CFM_SAVECONFIG_FAILED: Failed to save configuration!
Explanation	Save configuration failed for some reasons. Save configuration failed for some reasons.
Recommended action	Check reasons,for example: is device space enough; Is configuration file is opened and so on.

CFM_SAVECONFIG_SUCCESSFULLY

Message text	Configuration is saved successfully.
Variable fields	N/A
Severity level	5
Example	CFM/5/CFM_SAVECONFIG_SUCCESSFULLY: Configuration is saved successfully.
Explanation	Save configuration successfully. Save configuration successfully.
Recommended action	No action is required.

CLST Messages

This section contains the entire system log messages related to CLST.

CLST_SET_IP_ADDR

Message text	[IPADDR] is assigned by the cluster.
Variable fields	$1: Member’s IP address assigned by administrator device.
Severity level	6
Example	CLST/5/CLST_SET_IP_ADDR: 10.0.0.2 is assigned by the cluster.
Explanation	A member device has been assigned a private IP address, so it can communicate with the administrator device and network management device. When a member joins the cluster.
Recommended action	No action is required.

CLST_CMD_CFG

Message text	[STRING] is specified by the cluster.
Variable fields	$1: Some system command, for example info-center loghost 10.0.0.1.
Severity level	6
Example	CLST/6/CLST_CMD_CFG: info-center loghost 10.0.0.1 is specified by the cluster.
Explanation	The command has been configured on the member device. When a member joins the cluster.
Recommended action	No action is required.

CLST_SET_HOST_NAME_PREFIX

Message text	hostnamePrefix [STRING] is specified by the cluster.
Variable fields	$1: Hostname prefix used by cluster to specify the sysname of the device.
Severity level	6
Example	CLST/6/CLST_SET_HOST_NAME_PREFIX: hostnamePrefix aaa_1 is specified by the cluster.
Explanation	A hostname prefix is used by the cluster to specify the sysname.
Recommended action	No action is required.

CLST_SET_NAT_FAILED

Message text	Failed to enable NAT and the member device cannot communicate with the network administrator device.
Variable fields
Severity level	4
Example	CLST/4/CLST_SET_NAT_FAILED: Failed to enable NAT and the member device cannot communicate with the network administrator device.
Explanation	The administrator device failed to enable NAT and the reason may be memory shortage.
Recommended action	No action is required.

CLST_CHANGE_MVLAN_FAILED

Message text	Device [STRING] failed to modify MVLAN because [STRING].
Variable fields	$1: MAC address of the member device. $2: The reason, for example, the member device cannot create a new VLAN.
Severity level	4
Example	CLST/4/CLST_CHANGE_MVLAN_FAILED: Device 00E0-FC00-9912 failed to modify MVLAN because it failed to create a management VLAN.
Explanation	A member device cannot modify the management VLAN.
Recommended action	Check the configuration of the member device.

CLST_ADDPORT_MVLAN_FAILED

Message text	Device [STRING] failed to add some port to the management VLAN.
Variable fields	$1: MAC address of the member device.
Severity level	4
Example	CLST/4/CLST_ADDPORT_MVLAN_FAILED: Device 000F-E25D-F27B failed to add some port to the management VLAN.
Explanation	A member device failed to add some port to the management VLAN.
Recommended action	Check the configuration of the member device.

CLST_MEMBER_JOIN_CLUSTER

Message text	Member [STRING] has joined cluster [STRING].
Variable fields	$1: Member device number. $2: Cluster name.
Severity level	5
Example	CLST/5/CLST_MEMBER_JOIN_CLUSTER: Member 000F-E25D-F27B has joined cluster aaa.
Explanation	A member has joined cluster. (On administrator device)
Recommended action	No action is required.

CLST_MEMBER_DELETED_CLUSTER

Message text	Member [STRING] in the cluster was deleted.
Variable fields	$1: Member device number.
Severity level	5
Example	CLST/5/CLST_MEMBER_DELETED_CLUSTER: Member 000F-E25D-F27B in the cluster was deleted.
Explanation	A member has been deleted from the cluster. (On administrator device)
Recommended action	No action is required.

CLST_MEMBER_REJOIN_CLUSTER

Message text	Member [STRING] has joined the cluster again.
Variable fields	$1: Member device number.
Severity level	5
Example	CLST/5/CLST_MEMBER_REJOIN_CLUSTER: Member 00E0-FC00-3620 has rejoined the cluster again.
Explanation	When handshake exchange error occurred between the administrator and the member device. The member device can join the cluster again when it can exchange hand-shake packets with the administrator device. (On administrator device)
Recommended action	No action is required.

CLST_MEMBER_DOWN

Message text	Member [STRING] in the cluster was down.
Variable fields	$1: Member device number.
Severity level	4
Example	CLST/4/CLST_MEMBER_DOWN: Member 00E0-FC00-3620 in the cluster was down.
Explanation	If the administrator device does not receive the member’s hand-shake packet for sometime, the administrator device will consider the member device is down. (On administrator device)
Recommended action	Check if the communication between the administrator device and the member device fails or the administrator device is down.

CLST_DEVICE_JOIN_CLUSTER

Message text	A device [STRING] has joined cluster [STRING].
Variable fields	$1: MAC address $2: Cluster name.
Severity level	5
Example	CLST/5/CLST_DEVICE_JOIN_CLUSTER: A device 000f -e200-0004 has joined cluster ttt.
Explanation	A member was added into the cluster. (On member device)
Recommended action	No action is required.

CLST_DEVICE_DELETED_CLUSTER

Message text	A device was deleted from cluster [STRING].
Variable fields	$1: Cluster name.
Severity level	5
Example	CLST/5/CLST_DEVICE_DELETED_CLUSTER: A switch was deleted from cluster aaa.
Explanation	A member was deleted from the cluster. (On member device)
Recommended action	No action is required.

CLST_ADMINISTRATOR_DOWN

Message text	Cluster administrator was down.
Variable fields
Severity level	4
Example	CLST/4/CLST_ADMINISTRATOR_DOWN: Cluster administrator was down.
Explanation	When a member hasn’t received the administrator‘s hand-shake packet for sometime. The member will consider the administrator is down. (On member device)
Recommended action	Check if the communication between the administrator and the member fails or the administrator device is down.

CLST_DEVICE_REJOIN_CLUSTER

Message text	A device has joined the cluster again.
Variable fields
Severity level	5
Example	CLST/5/CLST_DEVICE_REJOIN_CLUSTER: A device has joined the cluster again.
Explanation	When handshake exchange error occurred between the administrator and the member device. The member device can join the cluster again when it can exchange hand-shake packets with the administrator device. (On member device)
Recommended action	No action is required.

CLST_LOG_HOST_NOT_CFG

Message text	Info-center loghost used by cluster not configured.
Variable fields
Severity level	5
Example	CLST/5/CLST_LOG_HOST_NOT_CFG: Info-center loghost used by cluster was not configured.
Explanation	The info-center loghost command is not configured on the administrator device.
Recommended action	Configure the info-center loghost command on the management device.

CLST_SYN_COM_SUC

Message text	Member [ULONG] has executed the [STRING] configuration successfully.
Variable fields	$1: Member ID. $2: A configuration, for example SNMP read-community.
Severity level	5
Example	CLST/5/CLST_SYN_COM_SUC: Member 1 has executed the read-community configuration successfully.
Explanation	Configuration has been performed successfully on the member.
Recommended action	No action is required.

CLST_SYN_COM_FAL

Message text	Member [STRING] failed to configure the [STRING] command.
Variable fields	$1: Member ID. $2: A configuration, for example SNMP read-community.
Severity level	4
Example	CLST/4/CLST_SYN_COM_FAL: Member 1 failed to configure the read-community command.
Explanation	A member device failed to perform a configuration.
Recommended action	Check the member device’s configuration and memory usage.

CLKM Messages

This section contains the entire system log messages related to CLKM.

CLKM_NOREFERENCE

Message text	Traced reference change alarm, no reference traced now.
Variable fields	N/A
Severity level	4
Example	CLKM/4/CLKM_NOREFERENCE: Traced reference change alarm, no reference traced now.
Explanation	no reference are traced now on the device.
Recommended action	Check the device and repair the fault.

CLKM_REFERENCE_CHANGE

Message text	Traced reference change alarm, current traced reference is [ULONG].
Variable fields	$1: Number of references.
Severity level	6
Example	CLKM/6/CLKM_REFERENCE_CHANGE: Traced reference change alarm, current traced reference is 15.
Explanation	current traced reference changes.
Recommended action	No action is required.

CLKM_REFERENCE_RECOVER

Message text	Reference [ULONG] is recovered.
Variable fields	$1: Number of references.
Severity level	6
Example	CLKM/6/CLKM_REFERENCE_RECOVER: Reference 5 is recovered.
Explanation	The specified reference is recovered.
Recommended action	No action is required.

CLKM_REFERENCE_LOST

Message text	Reference [ULONG] is lost.
Variable fields	$1: Number of references.
Severity level	5
Example	CLKM/5/CLKM_REFERENCE_LOST: Reference 5 is lost.
Explanation	The specified reference is lost.
Recommended action	Check the device and repair the fault.

CLKM_REFERENCE_ALLLOST

Message text	All references are lost.
Variable fields	N/A
Severity level	4
Example	CLKM/4/CLKM_REFERENCE_ALLLOST: All references are lost.
Explanation	All references are lost in the device.
Recommended action	Check the device and repair the fault.

CLKM_ALARM

Message text	[STRING] alarm, current state is [STRING].
Variable fields	$1: Alarm type. $2: Current state.
Severity level	4
Example	CLKM/4/CLKM_ALARM: SSM level alarm, current state is SSM_PRC on reference 5. CLKM/4/CLKM_ALARM: SSM out level alarm, current state is SSM_SETS. CLKM/4/CLKM_ALARM: Phase lock alarm, current state is hold judge. CLKM/4/CLKM_ALARM: Osc state alarm, current state is warm-up. CLKM/4/CLKM_ALARM: CLKM SRAM self-test alarm, current state is fault. CLKM/4/CLKM_ALARM: CLKM 38Mhz signal self-test alarm, current state is fault. CLKM/4/CLKM_ALARM: CLKM PLL tru050 self-test alarm, current state is fault. CLKM/4/CLKM_ALARM: CLKM PLL 88915 self-test alarm, current state is fault. CLKM/4/CLKM_ALARM: OSC self-test alarm, current state is fault. CLKM/4/CLKM_ALARM: CLKM I2C bus self-test alarm, current state is fault. CLKM/4/CLKM_ALARM: CLKM EPLD self-test alarm, current state is fault. CLKM/4/CLKM_ALARM: CLKM HDLC self-test alarm, current state is fault. CLKM/4/CLKM_ALARM: CLKM E1a self-test alarm, current state is fault. CLKM/4/CLKM_ALARM: CLKM E1b self-test alarm, current state is fault.
Explanation	The state of clock management system changes.
Recommended action	Check the device and repair the fault.

DEVM Messages

This section contains the entire system log messages related to DEVM.

FAN_RECOVERED

Message text	Fan [INTEGER] recovered.
Variable fields	$1: The fan ID
Severity level	5
Example	DEVM/5/FAN_RECOVERED: Fan 2 recovered.
Explanation	The fan state changes from failed or absent to OK.
Recommended action	No action is required.

FAN_FAILED

Message text	Fan [INTEGER] failed.
Variable fields	$1: The fan ID
Severity level	2
Example	DEVM/2/FAN_FAILED: Fan 2 failed.
Explanation	The fan failed to run.
Recommended action	Check the fan and repair it.

DHCPC Messages

This section contains the entire system log messages related to DHCPC.

DHCPC_REQIPFAILED_NETCONFLICT

Message text	IP address request failed on interface [STRING] because an IP address on the same network segment is being used on the device.
Variable fields	$1: Name of DHCP client interface from which the DHCP packets are received.
Severity level	4
Example	DHCPC/4/DHCPC_REQIPFAILED_NETCONFLICT: IP address request failed on interface VLAN-interface1 because an IP address on the same network segment is being used on the device.
Explanation	The same network segment IP address was detected on the device.
Recommended action	Check the IP address configuration on the device.

DHCPR Messages

This section contains the entire system log messages related to DHCPR.

DHCPR_DETECT_SERVER

Message text	DHCP Relay information: DHCP Relay interface = [STRING], server IP (detected by DHCP Relay) = [IPADDR].
Variable fields	$1: Name of the interface where the packet is received. $2: Server IP address.
Severity level	5
Example	DHCPR/5/DHCPR_DETECT_SERVER: DHCP Relay information: DHCP Relay interface = Ethernet1/0/1, server IP (detected by DHCP Relay) = 1.1.1.1.
Explanation	A DHCP server was detected by the relay device.
Recommended action	Check whether the DHCP server is legal.

DHCPRULE Messages

This section contains the entire system log messages related to DHCPRULE.

DHCPRULE_SET_DRVIER_FAIL

Message text	DHCP failed to apply a rule to driver because [STRING] on interface [STRING].
Variable fields	$1: The reason. $2: The interface name.
Severity level	4
Example	DHCPRULE/4/DHCPRULE_SET_DRIVER_FAIL: DHCP failed to apply a rule to driver because there is no enough resource for new rules on interface Ethernet1/0/1.
Explanation	DHCP failed to apply a rule to driver.
Recommended action	No action is required.

DLDP Messages

This section contains all the system log messages related to DLDP.

DLDP_AUTHENTICATION_FAIL

Message text	Packets failed to pass the DLDP authentication because of unmatched [STRING].
Variable fields	$1: Packet field
Severity level	3
Example	DLDP/3/DLDP_AUTHENTICATION_FAIL: Packets failed to pass the DLDP authentication because of unmatched INTERVAL.
Explanation	Packets failed to pass the DLDP authentication.
Recommended action	Check authentication-related configurations.

DLDP_UNIDIRECTION_AUTO

Message text	DLDP detects a unidirectional link on port [STRING]. The transceiver has malfunction in the Tx direction or cross-connected links exist between the local device and its neighbor. The shutdown mode is AUTO. DLDP shuts down the port.
Variable fields	$1: Port name
Severity level	3
Example	DLDP/3/DLDP_UNIDIRECTION_AUTO: DLDP detects a unidirectional link on port GigabitEthernet 1/0/25. The transceiver has malfunction in the Tx direction or cross-connected links exist between the local device and its neighbor. The shutdown mode is AUTO. DLDP shuts down the port.
Explanation	DLDP detects a unidirectional link and shuts down the port automatically.
Recommended action	Check the unidirectional link.

DLDP_UNIDIRECTION_MAN

Message text	DLDP detects a unidirectional link on port [STRING]. The transceiver has malfunction in the Tx direction or cross-connected links exist between the local device and its neighbor. The shutdown mode is MANUAL. The port needs to be shut down by the user.
Variable fields	$1: Port name
Severity level	3
Example	DLDP/3/DLDP_UNIDIRECTION_MAN: DLDP detects a unidirectional link on port GigabitEthernet 1/0/25. The transceiver has malfunction in the Tx direction or cross-connected links exist between the local device and its neighbor. The shutdown mode is MANUAL. The port needs to be shut down by the user.
Explanation	DLDP detects a unidirectional link and suggests that the port should be shut down.
Recommended action	Shut down the port and check the unidirectional link.

DLDP_UNIDIRECTION_AUTO_ENHANCE

Message text	In enhanced DLDP mode, port [STRING] cannot detect its aged-out neighbor. The transceiver has malfunction in the Tx direction or cross-connected links exist between the local device and its neighbor. The shutdown mode is AUTO. DLDP shuts down the port.
Variable fields	$1: Port name
Severity level	3
Example	DLDP/3/DLDP_UNIDIRECTION_AUTO_ENHANCE: In enhanced DLDP mode, port GigabitEthernet 1/0/25 cannot detect its aged-out neighbor. The transceiver has malfunction in the Tx direction or cross-connected links exist between the local device and its neighbor. The shutdown mode is AUTO. DLDP shuts down the port.
Explanation	In enhanced mode, DLDP detects a unidirectional link and shuts down the port automatically.
Recommended action	Check the unidirectional link.

DLDP_UNIDIRECTION_MAN_ENHANCE

Message text	In enhanced DLDP mode, port [STRING] cannot detect its aged-out neighbor. The transceiver has malfunction in the Tx direction or cross-connected links exist between the local device and its neighbor. The shutdown mode is MANUAL. The port needs to be shut down by the user.
Variable fields	$1: Port name
Severity level	3
Example	DLDP/3/ DLDP_UNIDIRECTION_MAN_ENHANCE: In enhanced DLDP mode, port GigabitEthernet 1/0/25 cannot detect its aged-out neighbor. The transceiver has malfunction in the Tx direction or cross-connected links exist between the local device and its neighbor. The shutdown mode is MANUAL. The port needs to be shut down by the user.
Explanation	In enhanced mode, DLDP detects a unidirectional link and suggests that the port should be shutdown.
Recommended action	Shut down the port and check the unidirectional link.

DLDP_UNIDIRECTION_AUTO_DISABLE

Message text	DLDP detects a unidirectional link on port [STRING]. The local port has received disable packets. The shutdown mode is AUTO. DLDP shuts down the port.
Variable fields	$1: Port name
Severity level	3
Example	DLDP/3/DLDP_UNIDIRECTION_AUTO_DISABLE: DLDP detects a unidirectional link on port GigabitEthernet1/0/25. The local port has received disable packets. The shutdown mode is AUTO. DLDP shuts down the port.
Explanation	DLDP detects a unidirectional link because DLDP received disable packets in AUTO shutdown mode.
Recommended action	Check the neighbour port and the unidirctional link.

DLDP_UNIDIRECTION_AUTO_LOOPBACK

Message text	DLDP detects a unidirectional link on port [STRING]. The local port has received looped back packets. The shutdown mode is AUTO. DLDP shuts down the port.
Variable fields	$1: Port name
Severity level	3
Example	DLDP/3/DLDP_UNIDIRECTION_AUTO_LOOPBACK: DLDP detects a unidirectional link on port GigabitEthernet1/0/25. The local port has received looped back packets. The shutdown mode is AUTO. DLDP shuts down the port.
Explanation	DLDP detects a unidirectional link because DLDP received looped back packets in AUTO shutdown mode.
Recommended action	Check the loopback link and the unidirectional link.

DLDP_UNIDIRECTION_AUTO_LINKDOWN

Message text	DLDP detects a unidirectional link on port [STRING]. The local port has received linkdown packets. The shutdown mode is AUTO. DLDP shuts down the port.
Variable fields	$1: Port name
Severity level	3
Example	DLDP/3/DLDP_UNIDIRECTION_AUTO_LINKDOWN: DLDP detects a unidirectional link on port GigabitEthernet1/0/25. The local port has received linkdown packets. The shutdown mode is AUTO. DLDP shuts down the port.
Explanation	DLDP detects a unidirectional link because DLDP received linkdown packets in AUTO shutdown mode.
Recommended action	Check the neighbour port and the unidirctional link.

DLDP_UNIDIRECTION_MAN_DISABLE

Message text	DLDP detects a unidirectional link on port [STRING]. The local port has received disable packets. The shutdown mode is MANUAL. The port needs to be shut down by the user.
Variable fields	$1: Port name
Severity level	3
Example	DLDP/3/DLDP_UNIDIRECTION_MAN_DISABLE: DLDP detects a unidirectional link on port GigabitEthernet1/0/25. The local port has received disable packets. The shutdown mode is MANUAL. The port needs to be shut down by the user.
Explanation	DLDP detects a unidirectional link because DLDP received disable packets in MANUAL shutdown mode.
Recommended action	Shut down the port, and check the neighbour port and the unidirctional link.

DLDP_UNIDIRECTION_MAN_LOOPBACK

Message text	DLDP detects a unidirectional link on port [STRING]. The local port has received looped back packets. The shutdown mode is MANUAL. The port needs to be shut down by the user.
Variable fields	$1: Port name
Severity level	3
Example	DLDP/3/DLDP_UNIDIRECTION_MAN_LOOPBACK: DLDP detects a unidirectional link on port GigabitEthernet1/0/25. The local port has received looped back packets. The shutdown mode is MANUAL. The port needs to be shut down by the user.
Explanation	DLDP detects a unidirectional link because DLDP received looped back packets in MANUAL shutdown mode.
Recommended action	Shut down the port, and check the loopback link and the unidirctional link.

DLDP_UNIDIRECTION_MAN_LINKDOWN

Message text	DLDP detects a unidirectional link on port [STRING]. The local port has received linkdown packets. The shutdown mode is MANUAL. The port needs to be shut down by the user.
Variable fields	$1: Port name
Severity level	3
Example	DLDP/3/DLDP_UNIDIRECTION_MAN_LINKDOWN: DLDP detects a unidirectional link on port GigabitEthernet1/0/25. The local port has received linkdown packets. The shutdown mode is MANUAL. The port needs to be shut down by the user.
Explanation	DLDP detects a unidirectional link because DLDP received linkdown packets in MANUAL shutdown mode.
Recommended action	Shut down the port, and check the neighbour port and the unidirctional link.

DOT1X Messages

This section contains the entire system log messages related to DOT1X.

DOT1X_AUTH_FAILURE

Message text	-IfName=[STRING]-UserName=[STRING]; DOT1X authentication failed.
Variable fields	$1: Interface type and number $2: Username
Severity level	6
Example	DOT1X/6/DOT1X_AUTH_FAILURE: -IfName=Ethernet1/0/1-UserName=test; DOT1X authentication failed.
Explanation	A user failed the authentication. This may result from incorrect username or password, or incorrect configuration on the user client, access device, or authentication server.
Recommended action	Check the relevant configuration.

DOT1X_SMARTON_FAILURE

Message text	-IfName=[STRING]-UserName=[STRING]; SmartOn authentication failed because [STRING]
Variable fields	$1: Interface type and number $2: Username $3: Failure reason.
Severity level	6
Example	DOT1X/6/DOT1X_SMARTON_FAILURE: -IfName=Ethernet1/0/1-UserName=test; SmartOn authentication failed because the switch ID is mismatched.
Explanation	A SmartOn user authentication failure. This may result from mismatched switch ID or password.
Recommended action	No action is required.

DOT1X_SOP_ACL_FAILURE

Message text	-IfName=[STRING]-UserName=[STRING]; [STRING]
Variable fields	$1: Interface type and number $2: Username $3: ACL rule assignment failure. Possible reasons include: “The specified ACL does not exist.” “Failed to delete the specified ACL.” “This type of ACL is not supported.” “Hardware resource is not enough.” “ACL contains a source MAC address that is different from the MAC address of the user.” “Failed to assign the specified ACL.”
Severity level	5
Example	DOT1X/5/DOT1X_SOP_ACL_FAILURE: -IfName=Ethernet1/0/1-UserName=test; This type of ACL is not supported.
Explanation	ACL rule assignment failure.
Recommended action	No action is required.

DPBRIDGE Messages

This section contains the entire system log messages related to DPBRIDGE.

DPBRIDGE_MACFULL

Message text	MAC address table is full.
Variable fields	N/A
Severity level	5
Example	DPBRIDGE/5/DPBRIDGE_MACFULL: MAC address table is full.
Explanation	The MAC address table is full.
Recommended action	Check the MAC address table.

DPCONLMT Messages

This section contains the entire system log messages related to CNNLMT.

CONNLMT_REACH_UPPERLIMIT

Message text	-srcIPAddr=[STRING]-srcIPMask=[ULONG]-srcVPNID=[STRING]-dstIPAddr=[STRING]-dstIPMask=[ULONG]-dstVPNID=[STRING]- protocol=[STRING]-MaxConnectionNum=[ULONG]; Number of connections reached the upper limit.
Variable fields	$1: Source IP address $2: Source IP address mask $3: source VPN ID $4: destination IP address $5: destination IP address mask $6: destination VPN ID $7: protocol of connection $8: Maximum connection number
Severity level	6
Example	DPCONLMT/6/CONNLMT_REACH_UPPERLIMIT: -srcIPAddr=5.5.5.6-srcIPMask=24-srcVPNID=None-dstIPAddr=6.6.6.6-dstIPMask=24-dstVPNID=None-protocol=HTTP-MaxConnectionNum=1024; Number of connections reached the upper limit.
Explanation	Number of connections reached the upper limit.
Recommended action	No action is required.

DPPBR Messages

This section contains the entire system log messages related to DPPBR.

DPPBR_FAILED_REFRESH

Message text	Failed to refresh data plane because [STRING].
Variable fields	$1: The reason, for example, there is not enough memory.
Severity level	4
Example	DPPBR/4/DPPBR_FAILED_REFRESH: Failed to refresh data plane because the memory is not enough.
Explanation	Failed to refresh data plane.
Recommended action	Check the configuration and the resource usage.

DPPBR6 Messages

This section contains the entire system log messages related to DPPBR6.

DPPBR6_FAILED_REFRESH

Message text	No enough resource when [STRING].
Variable fields	$1: What operation failed, for example allocating memory for a policy.
Severity level	4
Example	DPPBR6/4/DPPBR6_FAILED_REFRESH: No enough resource when allocating memory for a node.
Explanation	PBR6 failed to refresh data plane.
Recommended action	Check the configuration and the resource usage.

ETHOAM Messages

This section contains all the system log messages related to ETHOAM.

ETHOAM_ENABLE

Message text	Ethernet OAM is now enabled on port [string].
Variable fields	$1: Port name
Severity level	2
Example	ETHOAM/2/ETHOAM_ENABLE: Ethernet OAM is now enabled on port GigabitEthernet 1/0/25.
Explanation	Ethernet OAM is successfully enabled on a port.
Recommended action	No action is required.

ETHOAM_DISABLE

Message text	Ethernet OAM is now disabled on port [string].
Variable fields	$1: Port name
Severity level	2
Example	ETHOAM/2/ETHOAM_DISABLE: Ethernet OAM is now disabled on port GigabitEthernet 1/0/25.
Explanation	Ethernet OAM is successfully disabled on a port.
Recommended action	No action is required.

ETHOAM_CONNECTION_SUCCEED

Message text	An OAM connection is established on port [string].
Variable fields	$1: Port name
Severity level	3
Example	ETHOAM/3/ETHOAM_CONNECTION_SUCCEED: An Ethernet OAM connection is established on port Ethernet 1/0/1.
Explanation	An OAM connection has been established between two ports.
Recommended action	No action is required.

ETHOAM_CONNECTION_FAIL_UNSATISF

Message text	Port [string] failed to establish an OAM connection .because the peer is not satisfied with the capacity of the local port.
Variable fields	$1: Port name
Severity level	3
Example	ETHOAM/3/ETHOAM_CONNECTION_FAIL_UNSATISF: Port Ethernet 1/0/1 because the peer is not satisfied with the capacity of the local port.
Explanation	OAM connection is not successfully established between two ports because the peer is not satisfied with the capacity of the local port.
Recommended action	No action is required.

ETHOAM_CONNECTION_FAIL_TIMEOUT

Message text	Port [string] removed the OAM connection because it failed to receive information OAMPDU.
Variable fields	$1: Port name
Severity level	5
Example	ETHOAM/5/ETHOAM_CONNECTION_FAIL_TIMEOUT: Port Ethernet 1/0/1 removed the OAM connection because it failed to receive information OAMPDU.
Explanation	When an OAM entity fails to receive OAMPDUs in five seconds, it removes the OAM connection.
Recommended action	Check the link status or the OAM enable status on the peer.

ETHOAM_CONNECTION_FAIL_DOWN

Message text	The OAM connection on port [string] failed because the port link is down.
Variable fields	$1: Port name
Severity level	5
Example	ETHOAM/5/ETHOAM_CONNECTION_FAIL_DOWN: The OAM connection on port Ethernet 1/0/1 failed because the port link is down.
Explanation	When the port link transits from up to down, the OAM connection will be disconnected.
Recommended action	No action is required.

ETHOAM_ENTER_LOOPBACK_CONTROLLED

Message text	The local OAM entity enters remote loopback as controlled DTE on OAM Port [string].
Variable fields	$1: Port name
Severity level	6
Example	ETHOAM/6/ETHOAM_ENTER_LOOPBACK_CONTROLLED: The local OAM entity enters remote loopback as controlled DTE on OAM port Ethernet 1/0/1.
Explanation	After you run the “oam loopback” command on the remote OAM entity, the local OAM entity enters remote loopback as controlled DTE.
Recommended action	No action is required.

ETHOAM_QUIT_LOOPBACK_CONTROLLED

Message text	The local OAM entity quits remote loopback as controlled DTE on OAM Port [string].
Variable fields	$1: Port name
Severity level	6
Example	ETHOAM/6/ETHOAM_QUIT_LOOPBACK_CONTROLLED: The local OAM entity quits remote loopback as controlled DTE on OAM Port Ethernet 1/0/1.
Explanation	After you run the “undo oam loopback” command on the remote OAM entity, the local OAM entity quits remote loopback as controlled DTE.
Recommended action	No action is required.

ETHOAM_ENTER_LOOPBACK_CONTROLLIN

Message text	The local OAM entity enters remote loopback as controlling DTE on OAM Port [string].
Variable fields	$1: Port name
Severity level	6
Example	ETHOAM/6/ETHOAM_ENTER_LOOPBACK_CONTROLLIN: The local OAM entity enters remote loopback as controlling DTE on OAM Port Ethernet 1/0/1.
Explanation	After you run the “oam loopback” command on the local OAM entity, the remote OAM entity enters remote loopback as controlling DTE.
Recommended action	No action is required.

ETHOAM_QUIT_LOOPBACK_CONTROLLING

Message text	The local OAM entity quits remote loopback as controlling DTE on OAM Port [string].
Variable fields	$1: Port name
Severity level	6
Example	ETHOAM/6/ETHOAM_QUIT_LOOPBACK_CONTROLLING: The local OAM entity enters remote loopback as controlling DTE on OAM Port Ethernet1/0/1.
Explanation	After you run the “undo oam loopback” command on the local OAM entity, the local OAM entity quits remote loopback as controlling DTE.
Recommended action	No action is required.

ETHOAM_LOOPBACK_EXIT

Message text	OAM Port [string] quits remote loopback.
Variable fields	$1: Port name
Severity level	6
Example	ETHOAM/6/ETHOAM_LOOPBACK_EXIT: OAM Port Ethernet 1/0/1 quits remote loopback.
Explanation	When the link is down or the OAM entity working as controlled DTE is disabled, the local OAM entity quits remote loopback.
Recommended action	No action is required.

ETHOAM_LOOPBACK_EXIT_ERROR_STATU

Message text	OAM Port [string] quits remote loopback due to incorrect multiplexer or parser status.
Variable fields	$1: Port name
Severity level	6
Example	ETHOAM/6/ETHOAM_LOOPBACK_EXIT_ERROR_STATU: OAM port Ethernet 1/0/1 quits remote loopback due to incorrect multiplexer or parser status.
Explanation	The OAM entity quits remote loopback due to incorrect multiplexer or parser status.
Recommended action	Disable and then re-enable the OAM protocol on the OAM entity.

ETHOAM_LOCAL_LINK_FAULT

Message text	A local link fault event has occurred on [string].
Variable fields	$1: Name of a port on the local device
Severity level	4
Example	ETHOAM/4/ETHOAM_LOCAL_LINK_FAULT: A local link fault event has occurred on GigabitEthernet 1/0/25.
Explanation	A link fault event occurred on a local port. Disconnect the receiver fiber of a local port.
Recommended action	Re-connect the receiver fiber of the local port.

ETHOAM_REMOTE_LINK_FAULT

Message text	A remote link fault event has occurred on [string].
Variable fields	$1: Name of a port on a remote device
Severity level	4
Example	ETHOAM/4/ETHOAM_REMOTE_LINK_FAULT: A remote link fault event has occurred on GigabitEthernet 1/0/25.
Explanation	A link fault event occurred on a remote port.
Recommended action	Re-connect the receiver fiber of the remote port.

ETHOAM_LOCAL_ERROR_FRAME

Message text	An errored frame event has occurred on local port [string].
Variable fields	$1: Port name
Severity level	5
Example	ETHOAM/5/ETHOAM_LOCAL_ERROR_FRAME: An errored frame event has occurred on local port GigabitEthernet 1/0/25.
Explanation	An errored frame event occurred on a local port.
Recommended action	Check the link.

ETHOAM_REMOTE_ERROR_FRAME

Message text	An errored frame event has occurred on the peer of [string].
Variable fields	$1: Port name
Severity level	5
Example	ETHOAM/5/ ETHOAM_REMOTE_ERROR_FRAME: An errored frame event has occurred on the peer of port GigabitEthernet 1/0/25.
Explanation	An errored frame event occurred on a remote port.
Recommended action	Check the link.

ETHOAM_LOCAL_ERROR_FRAME_PERIOD

Message text	An errored frame period event has occurred on local port [string].
Variable fields	$1: Port name
Severity level	5
Example	ETHOAM/5/ETHOAM_LOCAL_ERROR_FRAME_PERIOD: An errored frame period event has occurred on local port GigabitEthernet 1/0/25.
Explanation	An errored frame period event occurred on a local port.
Recommended action	Check the link.

ETHOAM_REMOTE_ERROR_FRAME_PERIOD

Message text	An errored frame period event has occurred on remote port [string].
Variable fields	$1: Port name
Severity level	5
Example	ETHOAM/5/ETHOAM_REMOTE_ERROR_FRAME_PERIOD: An errored frame period event has occurred on the peer of port GigabitEthernet 1/0/25.
Explanation	An errored frame event occurred on a remote port.
Recommended action	Check the link.

ETHOAM_LOCAL_ERROR_FRAME_SECOND

Message text	An errored frame seconds summary event has occurred on local port [string].
Variable fields	$1: Port name
Severity level	5
Example	ETHOAM/5/ETHOAM_LOCAL_ERROR_FRAME_SECOND: An errored frame seconds summary event has occurred on local port GigabitEthernet 1/0/25.
Explanation	An errored frame seconds summary event occurred on a local port.
Recommended action	Check the link.

ETHOAM_REMOTE_ERROR_FRAME_SECOND

Message text	An errored frame seconds summary event has occurred on the peer of port [string].
Variable fields	$1: Port name
Severity level	5
Example	ETHOAM/5/ETHOAM_REMOTE_ERROR_FRAME_SECOND: An errored frame seconds summary event has occurred on the peer of port GigabitEthernet 1/0/25.
Explanation	An errored frame seconds summary event occurred on a remote port.
Recommended action	Check the link.

ETHOAM_REMOTE_DYING_GASP

Message text	A dying gasp event has occurred on the peer of port [string].
Variable fields	$1: Port name
Severity level	4
Example	ETHOAM/4/ETHOAM_REMOTE_DYING_GASP: A dying gasp event has occurred on the peer of port GigabitEthernet 1/0/25.
Explanation	A dying gasp event occurred on a remote port.
Recommended action	Don’t use this link until it returns to a normal condition.

ETHOAM_REMOTE_CRITICAL

Message text	A critical event has occurred on the peer of port [string].
Variable fields	$1: Port name
Severity level	4
Example	ETHOAM/4/ETHOAM_REMOTE_CRITICAL: A critical event has occurred on the peer of GigabitEthernet 1/0/25.
Explanation	A critical event occurred on a remote port.
Recommended action	Don’t use this link until it returns to a normal condition.

ETHOAM_LOOPBACK_NO_RESOURCE

Message text	OAM port [string] cannot enter remote loopback due to insufficient resources.
Variable fields	$1: Port name
Severity level	4
Example	ETHOAM/4/ETHOAM_LOOPBACK_NO_RESOURCE: OAM port GigabitEthernet 1/0/25 cannot enter remote loopback due to insufficient resources.
Explanation	When you try to enable remote loopback on the OAM port, there are not enough resources to complete the operation.
Recommended action	Release the resources, and run the “oam loopback” command again.

ETHOAM_LOOPBACK_NOT_SUPPORT

Message text	OAM port [STRING] cannot enter remote loopback because the operation is not supported.
Variable fields	$1: Port name
Severity level	4
Example	ETHOAM/4/ETHOAM_LOOPBACK_NOT_SUPPORT: OAM port Ethernet 1/0/1 cannot enter remote loopback because the operation is not supported.
Explanation	The operation of enabling remote loopback on the OAM port is not supported.
Recommended action	No action is required.

ETHOAM_LOCAL_DYING_GASP

Message text	A local dying gasp event has occurred on [string].
Variable fields	$1: Port name
Severity level	4
Example	ETHOAM/4/ETHOAM_LOCAL_DYING_GASP: A local dying gasp event has occurred on GigabitEthernet 1/0/25.
Explanation	A dying gasp event occurred on a local port.
Recommended action	Don’t use this link until it returns to a normal condition.

FILTER Messages

This section contains the entire system log messages related to Filter.

FLT_SET_POLICY_NOTSUPPORT_FAIL

Message text	Driver failed to apply the filter policy to or refresh the filter policy on interface [STRING].Not supported.
Variable fields	$1: Interface type and number
Severity level	5
Example	FILTER/5/FLT_SET_POLICY_NOTSUPPORT_FAIL: Failed to apply the filter policy to or refresh the filter policy on interface Ethernet1/0/1.Not supported.
Explanation	N/A
Recommended action	Check the configure of FILTER.

FLT_DRV_SET_POLICY_FAIL

Message text	Driver failed to apply the filter policy to or refresh the filter policy on interface [STRING].
Variable fields	$1: Interface type and number
Severity level	5
Example	FILTER/5/FLT_DRV_SET_POLICY_FAIL: Driver failed to apply the filter policy to or refresh the filter policy on interface Ethernet1/0/1.
Explanation	N/A N/A
Recommended action	Check the configure of FILTER.

FLT_DRV_DEL_POLICY_FAIL

Message text	Driver failed to delete the filter policy on interface [STRING].
Variable fields	$1: Interface type and number
Severity level	5
Example	FILTER/5/FLT_DRV_DEL_POLICY_FAIL: Driver failed to delete the filter policy on interface Ethernet1/0/1.
Explanation	N/A
Recommended action	Check the configure of FILTER.

FLT6 Messages

This section contains the entire system log messages related to FLT6.

FLT6_SET_POLICY_NOTSUPPORT_FAIL

Message text	Failed to apply the filter policy to or refresh the filter policy on interface [STRING].Not supported.
Variable fields	$1: Interface type and number
Severity level	5
Example	FLT6/5/FLT6_SET_POLICY_NOTSUPPORT_FAIL: Failed to apply the filter policy to or refresh the filter policy on interface Ethernet1/0/1.Not supported.
Explanation	N/A
Recommended action	Check the configure of FLT6.

FTPD Messages

This section contains the entire system log messages related to FTP Daemon.

FTPD_LOGIN

Message text	User [STRING] ([IPADDR]) has logged in successfully.
Variable fields	$1: User name. $2: Source IP address of the FTP client.
Severity level	5
Example	FTPD/5/FTPD_LOGIN: User ftpuser (192.168.0.99) has logged in successfully.
Explanation	An FTP user has logged in successfully.
Recommended action	No action is required.

FTPD_LOGOUT

Message text	User [STRING]([IPADDR]) logged out.
Variable fields	$1: User name. $2: Source IP address of FTP client.
Severity level	5
Example	FTPD/5/FTPD_LOGOUT: User ftpuser (192.168.0.99) logged out.
Explanation	An FTP user has logged out.
Recommended action	No action is required.

FTPD_LOGIN_FAILED

Message text	User [STRING] ([IPADDR]) failed to log in.
Variable fields	$1: User name. $2: Source IP address of the FTP client.
Severity level	5
Example	FTPD/5/FTPD_LOGIN_FAILED: User ftpuser (192.168.0.99) failed to log in.
Explanation	An FTP user failed to log in.
Recommended action	No action is required.

FTPD_REQUEST

Message text	User [STRING] ([IPADDR]) request: [STRING].
Variable fields	$1: User name. $2: Source IP address of FTP client. $3: Request command of FTP client.
Severity level	6
Example	FTPD/6/FTPD_REQUEST: User ftpuser (192.168.0.99) request: PORT 192,168,0,99,18,162.
Explanation	An FTP client sent a request to the server.
Recommended action	No action is required.

FTPD_SEND

Message text	FTP server has sent [ULONG] bytes to client [STRING] ([IPADDR]).
Variable fields	$1: File length transferred. $2: User name. $3: Source IP address of FTP client.
Severity level	5
Example	FTPD/5/FTPD_SEND: FTP server has sent 16045 bytes to client ftpuser (192.168.0.99).
Explanation	An FTP client has gotten a file successfully.
Recommended action	No action is required.

FTPD_RECEIVE

Message text	FTP server has received [ULONG] bytes from client [STRING] ([IPADDR]).
Variable fields	$1: File length transferred. $2: User name. $3: Source IP address of FTP client.
Severity level	5
Example	FTPD/5/FTPD_RECEIVE: FTP server has received 16045 bytes from client ftpuser (192.168.0.99).
Explanation	An FTP client has put a file successfully.
Recommended action	No action is required.

FTPD_WRITE_FINISHED

Message text	FTP server completed in writing a file.
Variable fields	N/A
Severity level	5
Example	FTPD/5/FTPD_WRITE_FINISHED: FTP server completed in writing a file.
Explanation	A file was written to the file system successfully.
Recommended action	No action is required.

FTPD_TRANSFER_FAILED

Message text	User [STRING] ([IPADDR]) failed to put a file.
Variable fields	$1: User name. $2: Source IP address of FTP client.
Severity level	5
Example	FTPD/5/FTPD_TRANSFER_FAILED: User ftpuser (192.168.0.99) failed to put a file.
Explanation	The FTP client failed to put a file to the FTP server.
Recommended action	Check network connection.

FTPD_WRITE_FAILED

Message text	FTP server failed to write a file.
Variable fields	N/A
Severity level	4
Example	FTPD/4/FTPD_WRITE_FAILED: FTP server failed to write a file.
Explanation	Failed to write a file to the file system.
Recommended action	Check the file system.

IC Messages

This section contains the entire system log messages related to SNMP.

SYS_RESTART

Message text	System restarted --\r\n[STRING] Software.
Variable fields	$1: Software name.
Severity level	6
Example	IC/6/SYS_RESTART: System restarted --\r\nComware Software.
Explanation	System started and ready to send syslog.
Recommended action	No action is required.

IFNET Messages

This section contains the entire system log messages related to IFNET.

LINEPROTO_UPDOWN

Message text	Line protocol on the interface [STRING] is [STRING].
Variable fields	$1: The name of interface. $2: The status of line protocol.
Severity level	5
Example	IFNET/5/LINEPROTO_UPDOWN: Line protocol on the interface Vlan-interface1is DOWN.
Explanation	The status of line protocol has been changed on an interface.
Recommended action	No action is required.

PROTOCOL_UPDOWN

Message text	Protocol [STRING] on the interface [STRING] is [STRING].
Variable fields	$1: The name of protocol. $2: The name of interface. $3: The status of protocol.
Severity level	5
Example	IFNET/5/PROTOCOL_UPDOWN: Protocol IPX on the interface Vlan-interface1 is UP
Explanation	The status of protocol has been changed on an interface.
Recommended action	No action is required.

LINK_UPDOWN

Message text	[STRING]: link status is [STRING].
Variable fields	$1: The name of interface. $2: The link status
Severity level	3
Example	IFNET/3/LINK_UPDOWN: Ethernet1/0/1 link status is DOWN.
Explanation	The link status has been changed on an interface.
Recommended action	No action is required.

LAGG Messages

This section contains the entire system log messages related to LAGG.

LAGG_INACTIVE_UPPER_LIMIT

Message text	Member port [STRING] of aggregation group [STRING] becomes INACTIVE because the current number of active ports has reached the upper limit.
Variable fields	$1: Port name $2: Link aggregation group type and ID
Severity level	5
Example	LAGG/5/LAGG_INACTIVE_UPPER_LIMIT: Member port GigabitEthernet1/0/25 of aggregation group BAGG1 becomes INACTIVE because the current number of active ports has reached the upper limit.
Explanation	The status of some member port(s) in an aggregation group becomes inactive because the number of current active ports has reached the upper limit.
Recommended action	No action is required.

LAGG_INACTIVE_RESOURCE_INSUFFICIE

Message text	Member port [STRING] of aggregation group [STRING] becomes INACTIVE because all aggregation resources are already in-use.
Variable fields	$1: Port name $2: Link aggregation group type and ID
Severity level	5
Example	LAGG/5/LAGG_INACTIVE_RESOURCE_INSUFFICIE: Member port GigabitEthernet1/0/25 of aggregation group BAGG1 becomes INACTIVE because all aggregation resources are already in-use.
Explanation	The status of some member port(s) in an aggregation group becomes inactive because all aggregation resources are already in-use.
Recommended action	No action is required.

LAGG_INACTIVE_CONFIGURATION

Message text	Member port [STRING] of aggregation group [STRING] becomes INACTIVE because the port's configuration is improper for being attached.
Variable fields	$1: Port name $2: Link aggregation group type and ID
Severity level	5
Example	LAGG/5/LAGG_INACTIVE_CONFIGURATION: Member port GigabitEthernet1/0/25 of aggregation group BAGG1 becomes INACTIVE because the port's configuration is improper for being attached.
Explanation	The status of some member port(s) in an aggregation group becomes inactive because the configuration of the port(s) is improper for being attached.
Recommended action	Modify the configuration of the member port(s) to be consistent with that of the aggregation interface.

LAGG_INACTIVE_PARTNER

Message text	Member port [STRING] of aggregation group [STRING] becomes INACTIVE because the port's partner is improper for being attached.
Variable fields	$1: Port name $2: Link aggregation group type and ID
Severity level	5
Example	LAGG/5/LAGG_INACTIVE_PARTNER: Member port GigabitEthernet1/0/25 of aggregation group BAGG1 becomes INACTIVE because the port's partner is improper for being attached.
Explanation	Status of some member port(s) in an aggregation group becomes inactive because the port's partner is improper for being attached.
Recommended action	Change the status of the partner to active.

LAGG_INACTIVE_LOWER_LIMIT

Message text	Member port [STRING] of aggregation group [STRING] becomes INACTIVE because the number of current active ports has not reached the lower limit.
Variable fields	$1: Port name $2: Link aggregation group type and ID
Severity level	5
Example	LAGG/5/LAGG_INACTIVE_LOWER_LIMIT: Member port GigabitEthernet1/0/25 of aggregation group BAGG1 becomes INACTIVE because the number of current active ports has not reached the lower limit.
Explanation	Status of some member port(s) in an aggregation group becomes inactive because the number of current active ports has not reached the lower limit according to the aggregation interface’s configuration.
Recommended action	Make more member ports to be active.

LAGG_INACTIVE_PHYSTATE

Message text	Member port [STRING] of aggregation group [STRING] becomes INACTIVE because the port's physical state (down) is improper for being attached.
Variable fields	$1: Port name $2: Link aggregation group type and ID
Severity level	5
Example	LAGG/5/LAGG_INACTIVE_PHYSTATE: Member port Ethernet1/0/1 of aggregation group BAGG1 becomes INACTIVE because the port's physical state (down) is improper for being attached.
Explanation	The status of a member port in an aggregation group becomes inactive because the port's physical state (down) is improper for being attached.
Recommended action	Change the physical state of the port to up.

LAGG_INACTIVE_HARDWARE_VALUE

Message text	Member port Ethernet1/0/1 of aggregation group BAGG1 becomes INACTIVE because the port's hardware restriction is improper for being attached.
Variable fields	$1: Port name $2: Link aggregation group type and ID
Severity level	5
Example	LAGG/5/LAGG_INACTIVE_HARDWARE_VALUE: Member port Ethernet1/0/1 of aggregation group BAGG1 becomes INACTIVE because the port's hardware restriction is improper for being attached.
Explanation	The status of a member port in an aggregation group becomes inactive because the port's hardware restriction is improper for being attached.
Recommended action	No action is required.

LAGG_INACTIVE_SPEED

Message text	Member port Ethernet1/0/1 of aggregation group BAGG1 becomes INACTIVE because the port's speed is improper for being attached.
Variable fields	$1: Port name $2: Link aggregation group type and ID
Severity level	5
Example	LAGG/5/LAGG_INACTIVE_SPEED: Member port Ethernet1/0/1 of aggregation group BAGG1 becomes INACTIVE because the port's speed is improper for being attached.
Explanation	The status of a member port in an aggregation group becomes inactive because the port's speed is improper for being attached.
Recommended action	Modify the speed of the member port(s) to be consistent with that of the active port(s).

LAGG_INACTIVE_DUPLEX

Message text	Member port Ethernet1/0/1 of aggregation group BAGG1 becomes INACTIVE because the port's duplex mode is improper for being attached.
Variable fields	$1: Port name $2: Link aggregation group type and ID
Severity level	5
Example	LAGG/5/LAGG_INACTIVE_DUPLEX: Member port Ethernet1/0/1 of aggregation group BAGG1 becomes INACTIVE because the port's duplex mode is improper for being attached.
Explanation	The status of a member port in an aggregation group becomes inactive because the port's duplex mode is improper for being attached.
Recommended action	Modify the duplex mode of the member port(s) to be consistent with that of the active port(s).

LLDP Messages

This section contains all the system log messages related to LLDP.

LLDP_CREATE_NEIGHBOR

Message text	New neighbor created on Port [STRING] (IfIndex [ULONG]), Chassis ID is [STRING], Port ID is [STRING].
Variable fields	$1: Port name $2: Port ifIndex $3: The neighbor’s chassis ID $4: The neighbor’s port ID
Severity level	6
Example	LLDP/6/LLDP_CREATE_NEIGHBOR: New neighbor created on Port 1 (IfIndex 587599), Chassis ID is 00-E0-10-6C-C3-E3, Port ID is Ethernet 1/0/1.
Explanation	The port discovers a new neighbor.
Recommended action	No action is required.

LLDP_DELETE_NEIGHBOR

Message text	Neighbor deleted on Port [STRING] (IfIndex [ULONG]), Chassis ID is [STRING], Port ID is [STRING].
Variable fields	$1: Port name $2: Port ifIndex $3: The neighbor’s chassis ID $4: The neighbor’s port ID
Severity level	6
Example	LLDP/6/LLDP_DELETE_NEIGHBOR: Neighbor deleted on Port 1 (IfIndex 587599), Chassis ID is 00-E0-10-6C-C3-E3, Port ID is Ethernet 1/0/1.
Explanation	A neighbor is shut down.
Recommended action	No action is required.

LLDP_NEIGHBOR_AGE_OUT

Message text	Neighbor aged out on Port [STRING] (IfIndex [ULONG]), Chassis ID is [STRING], Port ID is [STRING].
Variable fields	$1: Port name $2: Port ifIndex $3: The neighbor’s chassis ID $4: The neighbor’s port ID
Severity level	5
Example	LLDP/5/LLDP_NEIGHBOR_AGE_OUT: Neighbor age out on Port 1 (IfIndex 587599), Chassis ID is 00-E0-10-6C-C3-E3, Port ID is Ethernet 1/0/1.
Explanation	A neighbor had aged out.
Recommended action	Check the link status or the receive/transmit status of LLDP on the peer.

LLDP_REACH_NEIGHBOR_LIMIT

Message text	The number of neighbors maintained by the port [STRING] (IfIndex [ULONG]) has reached [ULONG], and no more neighbors can be added.
Variable fields	$1: Port name $2: Port ifIndex $3: The maximum number of neighbors a port can maintain
Severity level	5
Example	LLDP/5/LLDP_REACH_NEIGHBOR_LIMIT: The number of neighbors maintained by port 1 (IfIndex 587599) has reached 16, and no more neighbors can be added.
Explanation	The port received too many LLDP messages.
Recommended action	No action is required.

LLDP_LESS_THAN_NEIGHBOR_LIMIT

Message text	The number of neighbors maintained by port [STRING] (IfIndex [ULONG]) is less than [ULONG], and new neighbors can be added.
Variable fields	$1: Port name $2: Port ifIndex $3: The max number of neighbor that a port can maintain.
Severity level	6
Example	LLDP/6/LLDP_LESS_THAN_NEIGHBOR_LIMIT: The number of neighbors maintained by port 1 (IfIndex 587599) is less than 16, and new neighbors can be added.
Explanation	The port has not received too many LLDP messages.
Recommended action	No action is required.

LPDETECT Messages

This section contains the entire system log messages related to LPDETECT.

LPDETECT_BLOCK

Message text	Loopback exists on [STRING] and this interface is blocked.
Variable fields	$1: Interface name.
Severity level	5
Example	LPDETECT/5/LPDETECT_BLOCK: Loopback exists on Ethernet1/0/1 and this interface is blocked.
Explanation	Loopback exists on the interface and this interface is blocked.
Recommended action	Eliminate the loopback on the interface.

LPDETECT_SHUTDOWN

Message text	Loopback exists on [STRING] and this interface is shut down.
Variable fields	$1: Interface name.
Severity level	5
Example	LPDETECT/5/LPDETECT_SHUTDOWN: Loopback exists on Ethernet1/0/1 and this interface is shut down.
Explanation	Loopback exists on the interface and this interface is shut down.
Recommended action	Eliminate the loopback on the interface.

LPDETECT_LOOPBACKED

Message text	Loopback exists on [STRING].
Variable fields	Loopback exists on the interface
Severity level	5
Example	LPDETECT/5/LPDETECT_LOOPBACKED: Loopback exists on Ethernet1/0/1.
Explanation	Loopback exists on the interface.
Recommended action	Eliminate the loopback on the interface.

LPDETECT_RECOVERED

Message text	Loopback on [STRING] recovered.
Variable fields	$1: Interface name.
Severity level	5
Example	LPDETECT/5/LPDETECT_RECOVERED: Loopback on Ethernet1/0/1 recovered.
Explanation	Loopback on the interface is eliminated.
Recommended action	No action is required.

LS Messages

This section contains the entire system log messages related to LS.

LS_AUTHEN_FAILURE

Message text	-AccessType=[STRING]-UserName=[STRING]; Authentication is failed. [STRING]
Variable fields	$1:AccessType $2:Username $3: Reason of failure: “User not found.” “Password verified failed.” “User not active.” “User expired.” “Access type mismatch.” “Binding attribute is failed.”
Severity level	5
Example	LS/5/LS_AUTHEN_FAILURE: - AccessType=Login -UserName=cwf@system;Authentication is failed. User not found.
Explanation	A user’s authentication request is rejected by local.
Recommended action	No action is required.

LS_AUTHOR_FAILURE

Message text	-AccessType=[STRING]-UserName=[STRING]; Authorization is failed. [STRING]
Variable fields	$1:AccessType $2:Username $3: Reason of failure: “User not found.” “User not active.” “Privilege level mistach.”
Severity level	5
Example	LS/5/LS_AUTHOR_FAILURE: - AccessType=Login-UserName=cwf@system;Authorizaton is failed. User not found.
Explanation	A user’s authorization request is rejected by local.
Recommended action	No action is required.

LS_ACCT_FAILURE

Message text	-AccessType=[STRING]-UserName=[STRING]; Accounting is failed. [STRING]
Variable fields	$1:AccessType $2:Username $3: Reason of failure: “User not active.” “Concurrent access limitation.”
Severity level	5
Example	LS/5/LS_AUTHOR_FAILURE: - AccessType=Login -UserName=cwf@system;Accounting is failed. Concurrent access limitation.
Explanation	A user’s authorization request is rejected by local.
Recommended action	No action is required.

MAC Messages

This section contains the entire system log messages related to MAC.

MAC_TABLE_FULL

Message text	MAC address table is full.
Variable fields	N/A
Severity level	5
Example	MAC/5/MAC_TABLE_FULL: MAC address table is full.
Explanation	The MAC address table is full.
Recommended action	No action is required.

MAC_INFORMATION

Message text	-Action=[STRING]-MacAddr=[STRING]-VlanID=[ULONG]-MACType=[ULONG]-IfName=[STRING]; MAC address table changed.
Variable fields	$1: Added or Deleted. $2: MAC address. $3: Vlan ID. $4: MAC address type. $5: Interface name.
Severity level	6
Example	MAC/6/MAC_INFORMATION:-Action=Added-MacAddr=0000-0000-0001-VlanID=2-MACType=4-IfName=GigabitEthernet1/0/25; MAC address table changed.
Explanation	The MAC address table has changed.
Recommended action	No action is required.

MAC_TABLE_FULL_GLOBAL

Message text	MAC address table exceeded maximum number [ULONG].
Variable fields	$1: Max MAC address number.
Severity level	5
Example	MAC/5/MAC_TABLE_FULL_GLOBAL: MAC address table exceeded maximum number 2.
Explanation	The global MAC address table exceeded maximum number.
Recommended action	No action is required.

MAC_TABLE_FULL_PORT

Message text	MAC address table exceeded maximum number [ULONG] on interface [STRING].
Variable fields	$1: Max MAC address number. $2: Interface name.
Severity level	5
Example	MAC/5/MAC_TABLE_FULL_PORT: MAC address table exceeded maximum number 2 on interface GigabitEthernet1/0/25.
Explanation	MAC address table on interface exceeded maximum number.
Recommended action	No action is required.

MAC_TABLE_FULL_VLAN

Message text	MAC address table exceeded maximum number [ULONG] on Vlan [ULONG].
Variable fields	$1: Max MAC address number. $2: Vlan ID.
Severity level	5
Example	MAC/5/MAC_TABLE_FULL_VLAN: MAC address table exceeded maximum number 2 on Vlan 2.
Explanation	MAC address table on Vlan exceeded maximum number.
Recommended action	No action is required.

MFW Messages

This section contains all system log messages related to MFW.

MFW_DRV_DOWN

Message text	Failed to download information to driver, cause: [STRING].
Variable fields	$1: the reason for downloading to driver failure, include: invalid configuration parameter; configuration entry already exists; configuration is not supported; no enough system resource; configuration parameter is out of range; hardware resource is not ready; no enough hardware resource.
Severity level	3
Example	MFW/3/MFW_DRV_DOWN: Failed to download information to driver, cause: invalid configuration parameter.
Explanation	Failed to download information to driver.
Recommended action	Notify operator to check configuration and network.

MSTP Messages

This section contains all the system log messages related to MSTP.

MSTP_ENABLE

Message text	STP is now enabled on the device.
Variable fields	N/A
Severity level	6
Example	MSTP/6/MSTP_ENABLE: STP is now enabled on the device.
Explanation	STP is enabled.
Recommended action	No action is required.

MSTP_DISABLE

Message text	STP is now disabled on the device.
Variable fields	N/A
Severity level	6
Example	MSTP/6/MSTP_DISABLE: STP is now disabled on the device.
Explanation	STP is disabled.
Recommended action	No action is required.

MSTP_FORWARDING

Message text	[STRING] [ULONG]'s port [STRING] has been set to forwarding state.
Variable fields	$1: “Instance” or “VLAN” $2: Instance ID or VLAN ID $3: Interface name
Severity level	6
Example	MSTP/6/MSTP_FORWARDING: Instance 0's port Ethernet 1/0/2 has been set to forwarding state. MSTP/6/MSTP_FORWARDING: VLAN 10's port Ethernet 1/0/2 has been set to forwarding state.
Explanation	A certain port of the instance or VLAN is in forwarding state. MSTP calculates the state of the ports within the instance.
Recommended action	No action is required.

MSTP_DISCARDING

Message text	[STRING] [ULONG]'s port [STRING] has been set to discarding state.
Variable fields	$1: “Instance” or “VLAN” $2: Instance ID or VLAN ID $3: Interface name
Severity level	6
Example	MSTP/6/MSTP_DISCARDING: Instance 0's port Ethernet 1/0/2 has been set to discarding state. MSTP/6/MSTP_DISCARDING: VLAN 10's port Ethernet 1/0/2 has been set to discarding state.
Explanation	A certain port of the instance or VLAN is in discarding state.
Recommended action	No action is required.

MSTP_NOT_ROOT

Message text	The current switch is no longer the root of [STRING] [ULONG].
Variable fields	$1: “instance” or “VLAN” $2: Instance ID or VLAN ID
Severity level	5
Example	MSTP/5/MSTP_NOT_ROOT: The current switch is no longer the root of instance 0. MSTP/5/MSTP_NOT_ROOT: The current switch is no longer the root of VLAN 10.
Explanation	The current switch is not the root of an instance or a VLAN.
Recommended action	Check the bridge priority configuration and possible attacks from other devices.

MSTP_BPDU_PROTECTION

Message text	BPDU-Protection port [STRING] received BPDUs.
Variable fields	$1: Interface name
Severity level	4
Example	MSTP/4/MSTP_BPDU_PROTECTION: BPDU-Protection port Ethernet 1/0/4 received BPDUs.
Explanation	A BPDU-Protection port received BPDUs.
Recommended action	Check whether the downstream devices are terminals and check for possible attacks from other devices.

MSTP_ROOT_PROTECTION

Message text	[STRING] [ULONG]'s ROOT-Protection port [STRING] received superior BPDUs.
Variable fields	$1: “Instance” or “VLAN” $2: Instance ID or VLAN ID $3: Interface name
Severity level	4
Example	MSTP/4/MSTP_ROOT_PROTECTION: Instance 0's ROOT-Protection port Ethernet 1/0/2 received superior BPDUs. MSTP/4/MSTP_ROOT_PROTECTION: VLAN 10's ROOT-Protection port Ethernet 1/0/2 received superior BPDUs.
Explanation	A ROOT-Protection port received superior BPDUs.
Recommended action	Check the bridge priority configuration and possible attacks from other devices.

MSTP_LOOP_PROTECTION

Message text	[STRING] [ULONG]'s LOOP-Protection port [STRING] failed to receive configuration BPDUs.
Variable fields	$1: “Instance” or “VLAN” $2: Instance ID or VLAN ID $3: Interface name
Severity level	4
Example	MSTP/4/MSTP_LOOP_PROTECTION: Instance 0's LOOP-Protection port Ethernet 1/0/2 failed to receive configuration BPDUs. MSTP/4/MSTP_LOOP_PROTECTION: VLAN 10's LOOP-Protection port Ethernet 1/0/2 failed to receive configuration BPDUs.
Explanation	A LOOP-Protection port failed to receive configuration BPDUs.
Recommended action	Check the STP status of the upstream device and possible attacks from other devices.

MSTP_BPDU_FORMAT_ERROR

Message text	Port [STRING] received MSTP BPDUs of different formats continually. Shut it down in order to prevent broadcast.
Variable fields	$1: Interface name
Severity level	4
Example	MSTP/4/MSTP_BPDU_FORMAT_ERROR: Port Ethernet 1/0/1 received MSTP BPDUs of different formats continually. Shut it down in order to prevent broadcast.
Explanation	A port received MSTP BPDUs of different formats continually.
Recommended action	Check the MSTP format configuration of other devices.

MSTP_BPDU_FORMAT_CONFIG_ERROR

Message text	Port [STRING] received MSTP BPDUs of a different format than the configured one. Please change your MSTP BPDU format configuration.
Variable fields	$1: Interface name
Severity level	4
Example	MSTP/4/MSTP_BPDU_FORMAT_CONFIG_ERROR: Port Ethernet 1/0/1 received MSTP BPDUs of a different format than the configured one. Please change your MSTP BPDU format configuration.
Explanation	A port received MSTP BPDUs of a different format than the configured one.
Recommended action	Check the MSTP BPDU format configuration of the current device.

MSTP_BPDU_FORMAT_CONFIG_RIGHT

Message text	Port [STRING] received MSTP BPDUs of the same format as the configured one.
Variable fields	$1: Interface name
Severity level	5
Example	MSTP/5/MSTP_BPDU_FORMAT_CONFIG_RIGHT: Port Ethernet 1/0/1 received MSTP BPDUs of the same format as the configured one.
Explanation	A port received MSTP BPDUs of the same format as the configured one.
Recommended action	No action is required.

MSTP_BPDU_RECEIVE_EXPIRY

Message text	[STRING] [ULONG]'s port [STRING] received no BPDU within the rcvdInfoWhile interval. Information of the port aged out.
Variable fields	$1: “Instance” or “VLAN” $2: Instance ID or VLAN ID $3: Interface name
Severity level	5
Example	MSTP/5/MSTP_BPDU_RECEIVE_EXPIRY: Instance 0's port GigabitEthernet 1/0/25 received no BPDU within the rcvdInfoWhile interval. Information of the port aged out.
Explanation	When a non-designated port received no BPDU within the rcvdInfoWhile interval, information of the port ages out.
Recommended action	Check the STP status of the upstream device and possible attacks from other devices.

MSTP_NOTIFIED_TC

Message text	[STRING] [ULONG]'s port [STRING] was notified of a topology change.
Variable fields	$1: “Instance” or “VLAN” $2: Instance ID or VLAN ID $3: Interface name
Severity level	6
Example	MSTP/6/MSTP_NOTIFIED_TC: Instance 0's port GigabitEthernet 1/0/25 was notified of a topology change.
Explanation	The instance or VLAN to which the port belongs has a topology change.
Recommended action	Check whether the topology change is normal.

MSTP_DETECTED_TC

Message text	[STRING] [ULONG]'s port [STRING] detected a topology change.
Variable fields	$1: “Instance” or “VLAN” $2: Instance ID or VLAN ID $3: Interface name
Severity level	6
Example	MSTP/6/MSTP_DETECTED_TC: Instance 0's port GigabitEthernet 1/0/25 detected a topology change.
Explanation	The MSTP instance or VLAN to which the port belongs has a topology change.
Recommended action	Check whether the topology change is normal.

MSTP_PORT_TYPE_PROTECTION

Message text	[STRING] [ULONG]'s port [STRING] received BPDUs from an access port. Inconsistent port type.
Variable fields	$1: “VLAN” $2: VLAN ID $3: Interface name
Severity level	6
Example	MSTP/6/MSTP_PORT_TYPE_PROTECTION: VLAN 10's port GigabitEthernet 1/0/25 received BPDU from an access port. Inconsistent port type.
Explanation	An access port received a PVST PDU.
Recommended action	Check that port type configuration is correct.

MSTP_PVID_PROTECTION

Message text	[STRING] [ULONG]'s port [STRING] received BPDUs with inconsistent peer VLAN ID [STRING]. Inconsistent local VLAN.
Variable fields	$1: “VLAN” $2: VLAN ID $3: Interface name $4: VLAN ID
Severity level	6
Example	MSTP/6/MSTP_PVID_PROTECTION: VLAN 10's port GigabitEthernet 1/0/25 received BPDUs with inconsistent peer VLAN ID 20. Inconsistent local VLAN.
Explanation	A non-access port received a PVST PDU with an inconsistent peer VLAN ID.
Recommended action	Check that port PVID configuration is correct.

MSTP_CONSISTENCY_RESTRORATION

Message text	[STRING] [ULONG]'s port [STRING] consistency restored.
Variable fields	$1: “VLAN” $2: VLAN ID $3: Interface name
Severity level	6
Example	MSTP/6/MSTP_PVID_PROTECTION: VLAN 10's port GigabitEthernet 1/0/25 consistency restored.
Explanation	Port type or PVID protection is invalid.
Recommended action	No action is required.

ND Messages

This section contains the entire system log messages related to ND.

ND_CONFIG_CONFLICT

Message text	[STRING] is not consistent.
Variable fields	$1: Type of configuration.
Severity level	5
Example	ND/5/ND_CONFIG_CONFLICT: PREFIX VALID TIME is not consistent.
Explanation	Configurations on the two routers are different.
Recommended action	Check device’s configuration.

ND_DUPADDR

Message text	Duplicated address: [STRING] on interface [STRING].
Variable fields	$1: Address that is to be assigned to an interface. $2: Name of the interface.
Severity level	5
Example	ND/5/ND_DUPADDR: Duplicated address: 33::8 on interface Vlan-interface9.
Explanation	The address that was to be assigned to the interfaces is already used by another device.
Recommended action	Assign a different address to the interface.

ND_LIFETIME_ERROR

Message text	Preferred lifetime is greater than the valid lifetime of prefix [STRING].
Variable fields	$1: IPv6 prefix.
Severity level	5
Example	ND/5/ND_LIFETIME_ERROR: Preferred lifetime is greater than the valid lifetime of prefix 10::.
Explanation	The preferred lifetime is greater than the valid lifetime of the prefix information of RA received when address autoconfiguration is enabled.
Recommended action	Check device’s configuration.

ND_ROUTECONFLICT

Message text	IPv6 address [STRING] conflicts with route [STRING].
Variable fields	$1: IPv6 address. $2: If "on VPN instance instance-name" is displayed, the log indicates there is a route conflict in the specified VPN. Typically, this field is not displayed because IPv6 does not support VPN.
Severity level	6
Example	ND/5/ND_ROUTECONFLICT: IPv6 address 100::1 conflicts with route.
Explanation	The driver returned route conflict when an ND entry was added to the driver.
Recommended action	Check device’s configuration.

ND_SETRULE_FAILED

Message text	Failed to add a rule because [STRING] on interface [STRING].
Variable fields	$1: The reason. $2: The interface name.
Severity level	4
Example	ND/4/ND_SETRULE_FAILED: Failed to add a rule because no enough resource on interface GigabitEthernet1/0/25.
Explanation	Failed to add a rule to driver.
Recommended action	No action is required.

NTP Messages

This section contains the entire system log messages related to NTP.

NTP_CHANGE_LEAP

Message text	System Leap Indicator changed from [ULONG] to [ULONG] after clock update.
Variable fields	$1: Original Leap Indicator. $2: Current Leap Indicator.
Severity level	5
Example	NTP/5/NTP_CHANGE_LEAP: System Leap Indicator changed from 00 to 01 after clock update.
Explanation	NTP Leap Indicator is a two-bit code warning of an impending leap second to be inserted in the NTP timescale. The bits are set before 23:59 on the day of insertion and reset after 00:00 on the following day. This causes the number of seconds (rolloverinterval) in the day of insertion to be increased or decreased by one.
Recommended action	No action is required.

NTP_CHANGE_STRATUM

Message text	System stratum changed from [ULONG] to [ULONG] after clock update.
Variable fields	$1: Original stratum. $2: Current stratum.
Severity level	5
Example	NTP/5/NTP_CHANGE_STRATUM: System stratum changed from 6 to 5 after clock update.
Explanation	System stratum has changed.
Recommended action	No action is required.

NTP_SOURCE_LOST

Message text	System synchronization source lost.
Variable fields	N/A
Severity level	5
Example	NTP/5/NTP_SOURCE_LOST: System synchronization source lost.
Explanation	System synchronization source lost.
Recommended action	Check NTP server and network connection.

NTP_TOO_MANY_PEERS

Message text	Too many peers.
Variable fields	N/A
Severity level	6
Example	NTP/5/NTP_TOO_MANY_PEERS: Too many peers.
Explanation	The maximum number of NTP associations has been reached.
Recommended action	No action is required.

OPTMOD Messages

This section contains the entire system log messages related to OPTMOD.

MODULE_OUT

Message text	[STRING]: The transceiver is absent.
Variable fields	$1: A port name
Severity level	4
Example	OPTMOD/4/MODULE_OUT: GigabitEthernet1/0/26: The transceiver is absent.
Explanation	The transceiver is plugged out.
Recommended action	No action is required.

MODULE_IN

Message text	[STRING]: The transceiver is [STRING].
Variable fields	$1: A port name $2: The type string of the module.
Severity level	4
Example	OPTMOD/4/MODULE_IN: GigabitEthernet1/0/25: The transceiver is 1000_BASE_T_AN_SFP.
Explanation	The transceiver is plugged in, it’s type is 1000_BASE_BX_U_SFP.
Recommended action	No action is required.

OSPF Messages

This section contains the entire system log messages related to OSPF.

OSPF_RT_LMT

Message text	OSPF [ULONG] [STRING] route limit reached.
Variable fields	$1:OSPF Process ID $2:Route Type (intra area ,inter area or AS external)
Severity level	4
Example	OSPF/4/OSPF_RT_LMT: OSPF 1 AS External route limit reached.
Explanation	OSPF routes reach limit.
Recommended action	Please check OSPF routes and modify OSPF configuration to make routes under the limit.

OSPF_RTRID_CHG

Message text	OSPF [ULONG] New router ID elected, please restart OSPF if you want to make the new router ID take effect.
Variable fields	$1: OSPF Process ID
Severity level	5
Example	OSPF/5/OSPF_RTRID_CHG: OSPF 1 New router ID elected, please restart OSPF if you want to make the new router ID take effect.
Explanation	When OSPF Router ID is changed, user must restart OSPF manually in order to make the new Router ID take effect.
Recommended action	Please use “reset ospf process” command to make the new Router ID take effect.

OSPF_NBR_CHG

Message text	OSPF [ULONG] Neighbor [STRING] ([STRING]) from [STRING] to [STRING]
Variable fields	$1:OSPF Process ID $2:Neighbor IP Address $3:Interface Name $4:Old Neighbor State $5:New Neighbor State
Severity level	5
Example	OSPF/5/OSPF_NBR_CHG: OSPF 1 Neighbor 2.2.2.2 (Vlan-interface100) from Full to Down.
Explanation	An important neighbor state change event occurs.
Recommended action	When neighbor state change from Full to other state, please check OSPF configuration and network status.

OSPF_VLINKID_CHG

Message text	OSPF [ULONG] Router ID changed, re-configure Vlink on peer
Variable fields	$1: OSPF Process ID
Severity level	5
Example	OSPF/5/OSPF_VLINKID_CHG:OSPF 1 Router ID changed, re-configure Vlink on peer
Explanation	When new OSPF Router ID takes effect, user should check and modify Vlink configuration on peer router according to new Router ID.
Recommended action	Please check and modify Vlink configuration on peer router according to new Router ID.

OSPF_LAST_NBR_DOWN

Message text	OSPF [ULONG] Last neighbor down event: Router ID: [STRING] Local address: [STRING] Remote address: [STRING] Reason: [STRING]
Variable fields	$1:OSPF Process ID $2:Router ID $3:Local IP Address $4:Neighbor IP Address $5:Reason
Severity level	6
Example	OSPF/6/OSPF_LAST_NBR_DOWN: OSPF 1 Last neighbor down event: Router ID: 2.2.2.2 Local address: 10.1.1.1 Remote address: 10.1.1.2 Reason: Dead Interval timer expired.
Explanation	Record last OSPF neighbor down event.
Recommended action	Please check the reason of last OSPF neighbor down event.

PING Messages

This section contains the entire system log messages related to PING.

PING_LOG

Message text	PING/6/PING_LOG: [IPADDR] ping statistics: [ULONG] packet(s) transmitted; [ULONG] packet(s) received; [ULONG] duplicates; Somebody's printing up packets; packet loss: [ULONG]%; round-trip min/avg/max = [ULONG]/[ULONG]/[ULONG] ms.
Variable fields	$1: IP address. $2: packet(s) transmitted number. $3: packet(s) received number. $4: packet(s) duplicates number $5: The percentage of lost packet. $6: minimal time cost by round-trip. $7: average time cost by round-trip. $8: maximal time cost by round-trip.
Severity level	6
Example	PING/6/PING_LOG: 192.168.0.115 ping statistics: 5 packet(s) transmitted; 5 packet(s) received; packet loss: 0.00%; round-trip min/avg/max = 1/5/24 ms.
Explanation	The result of the ping.
Recommended action	If there is no packet received, please check wether the interface is down which causes missing of its route in the routing table, or the destination can be reached,

PING6 Messages

This section contains the entire system log messages related to IPv6 PING.

PING6_LOG

Message text	PING6/6/PING6_LOG: [IPv6ADDR] ping statistics: [ULONG] packet(s) transmitted; [ULONG] packet(s) received; [ULONG] duplicates; Somebody's printing up packets; packet loss: [ULONG]%; round-trip min/avg/max = [ULONG]/[ULONG]/[ULONG] ms.
Variable fields	$1: IPv6 address. $2: packet(s) transmitted number. $3: packet(s) received number. $4: packet(s) duplicates number $5: The percentage of lost packet. $6: minimal time cost by round-trip. $7: average time cost by round-trip. $8: maximal time cost by round-trip.
Severity level	6
Example	PING6/6/PING6_LOG: 2000::2 ping statistics: 5 packet(s) transmitted; 5 packet(s) received; packet loss: 0.00%; round-trip min/avg/max = 1/8/38 ms.
Explanation	The result of the IPv6 ping.
Recommended action	If there is no packet received, please check wether the interface is down which causes missing of its route in the routing table, or the destination can be reached,

PKEY Messages

This section contains the entire system log messages related to PKEY.

PKEY_HOST_KEY_BACKUP_FAIL

Message text	Failed to backup the host key pair.
Variable fields	N/A
Severity level	4
Example	PKEY/4/PKEY_HOST_KEY_BACKUP_FAIL: Failed to backup the host key pair.
Explanation	Failed to backup the host key pair.
Recommended action	Check the status of the device, such as the CPU usage, memory usage, and storage.

PKEY_SERVER_KEY_BACKUP_FAIL

Message text	Failed to backup the server key pair.
Variable fields	N/A
Severity level	4
Example	PKEY/4/PKEY_SERVER_KEY_BACKUP_FAIL: Failed to backup the server key pair.
Explanation	Failed to backup the server key pair.
Recommended action	Check the status of the device, such as the CPU usage, memory usage, and storage.

PKEY_EXPORT_PKEY_SUCC

Message text	Exported public key to file successfully.
Variable fields	N/A
Severity level	6
Example	PKEY/6/ PKEY_EXPORT_PKEY_SUCC: Exported public key to file successfully.
Explanation	Exported the public key to a file successfully.
Recommended action	No action is required.

PKEY_EXPORT_PKEY_FAIL

Message text	Failed to export public key to file.
Variable fields	N/A
Severity level	4
Example	PKEY/4/PKEY_EXPORT_PKEY_FAIL: Failed to export public key to file.
Explanation	Failed to export the public key to a file.
Recommended action	Check if there is something wrong with the Flash or CF card.

PKEY_CREATE_HOST_KEY_SUCC

Message text	Created the host key pair successfully.
Variable fields	N/A
Severity level	6
Example	PKEY/6/PKEY_CREATE_HOST_KEY_SUCC: Created the host key pair successfully.
Explanation	Created the host key pair successfully.
Recommended action	No action is required.

PKEY_CREATE_SERVER_KEY_SUCC

Message text	Created server key pair successfully.
Variable fields	N/A
Severity level	6
Example	PKEY/6/PKEY_CREATE_SERVER_KEY_SUCC: Created server key pair successfully.
Explanation	Created the server key pair successfully.
Recommended action	No action is required.

PKEY_CREATE_LOCAL_KEY_FAIL

Message text	Failed to create the key pair(s).
Variable fields	N/A
Severity level	4
Example	PKEY/4/PKEY_CREATE_LOCAL_KEY_FAIL: Failed to create the key pair(s).
Explanation	Create encryption key failure.
Recommended action	Check the file system.

PKEY_DESTORY_HOST_KEY_SUCC

Message text	Destroyed the host key pair successfully.
Variable fields	N/A
Severity level	6
Example	PKEY/6/PKEY_DESTORY_HOST_KEY_SUCC: Destroyed the host key pair successfully.
Explanation	Destroyed the host key pair successfully.
Recommended action	No action is required.

PKEY_DESTORY_SERVER_KEY_SUCC

Message text	Destroyed the server key pair successfully.
Variable fields	N/A
Severity level	6
Example	PKEY/6/PKEY_DESTORY_SERVER_KEY_SUCC: Destroyed the server key pair successfully.
Explanation	Destroyed the server key pair successfully.
Recommended action	No action is required.

PKEY_DESTORY_LOCAL_KEY_FAIL

Message text	Failed to destroy the key pair(s).
Variable fields	N/A
Severity level	4
Example	PKEY/4/PKEY_DESTORY_LOCAL_KEY_FAIL: Failed to destroy the key pair(s).
Explanation	Destroy encryption key failure.
Recommended action	Check the file system.

POE Messages

This section contains the entire system log messages related to POE.

PSE_STATUS

Message text	PSE [ULONG]: PSE power supply failed because of fan failure.
Variable fields	$1: PSE index
Severity level	4
Example	POE/4/PSE_STATUS: PSE 1: PSE power supply failed because of fan failure.
Explanation	PSE power supply failed because of fan failure.
Recommended action	Clear fan failure.

Message text	PSE [ULONG]: PSE power supply recovered because fan failure was cleared.
Variable fields	$1: PSE index
Severity level	4
Example	POE/4/PSE_STATUS: PSE 1: PSE power supply recovered because fan failure was cleared.
Explanation	PSE power supply recovered because fan failure was cleared.
Recommended action	No action is required.

Message text	PSE [ULONG]: Upgrade for PSE firmware is proceeding.
Variable fields	$1: PSE index.
Severity level	4
Example	POE/4/PSE_STATUS: PSE 1: Upgrade for PSE firmware is proceeding.
Explanation	PSE firmware was being upgraded.
Recommended action	No action is required.

Message text	PSE [ULONG]: PSE firmware upgraded successfully.
Variable fields	$1: PSE index
Severity level	4
Example	POE/4/PSE_STATUS: PSE 1: PSE firmware upgraded successfully.
Explanation	PSE firmware was upgraded successfully from the CLI.
Recommended action	No action is required.

Message text	PSE [ULONG]: The device will automatically reboot since the PSE firmware upgraded successfully.
Variable fields	$1: PSE index
Severity level	4
Example	POE/4/PSE_STATUS: PSE 1: The device will automatically reboot since the PSE firmware upgraded successfully.
Explanation	PSE firmware was automatically upgraded.
Recommended action	No action is required.

Message text	PSE [ULONG]: Failed to upgrade PSE firmware.
Variable fields	$1: PSE index
Severity level	4
Example	POE/4/PSE_STATUS: PSE 1: Failed to upgrade PSE firmware.
Explanation	PSE firmware failed to be upgraded.
Recommended action	Try to upgrade PSE firmware again.

Message text	PSE [ULONG]: Failed to upgrade PSE firmware and PSE will not operate correctly.
Variable fields	$1: PSE index
Severity level	4
Example	POE/4/PSE_STATUS: PSE 1: Failed to upgrade PSE firmware and PSE will not operate correctly.
Explanation	PSE firmware was automatically upgraded.
Recommended action	Try to upgrade PSE firmware again.

PORTSEC Messages

This section contains the entire system log messages related to PORTSEC.

PORTSEC_LEARNED_MACADDR

Message text	-IfName=[STRING]-MACAddr=[STRING]-VLANId=[INTEGER]; A new MAC address learned.
Variable fields	$1: Interface type and number $2: MAC address $3: VLAN ID
Severity level	6
Example	PORTSEC/6/PORTSEC_LEARNED_MACADDR: -IfName=Ethernet1/0/1-MACAddr=00:11:43:C5:4B:23-VLANId=1; A new MAC address learned.
Explanation	A new MAC address has been learned.
Recommended action	No action is required.

PORTSEC_VIOLATION

Message text	-IfName=[STRING]-MACAddr=[STRING]-VLANId=-[INTEGER]-IfStatus=[STRING]; Intrusion detected.
Variable fields	$1: Interface type and number $2: MAC address $3: VLAN ID $4: Interface status, up or down
Severity level	5
Example	PORTSEC/5/PORTSEC_VIOLATION: -IfName=Ethernet1/0/1-MAC Addr=00:11:43:C5:4B:23-VLANId=1-IfStatus=Up; Intrusion detected.
Explanation	An intrusion was detected.
Recommended action	No action is required.

PORTSEC_DOT1X_LOGIN_FAILURE

Message text	-IfName=[STRING]-MACAddr=[STRING]-VLANId=[INTEGER]-UserName=[STRING]; The user failed the 802.1X authentication.
Variable fields	$1: Interface type and number $2: MAC address $3: VLAN ID $4: Username
Severity level	6
Example	PORTSEC/6/PORTSEC_DOT1X_LOGIN_FAILURE: -IfName=Ethernet1/0/1-MACAddr=00:11:43:C5:4B:23-VLANId=1-UserName=test; The user failed the 802.1X authentication.
Explanation	The user failed the 802.1X authentication.
Recommended action	No action is required.

PORTSEC_DOT1X_LOGIN_SUCC

Message text	IfName=[STRING]-MACAddr=[STRING]-VLANId=[INTEGER]-UserName=[STRING]; The user passed 802.1X authentication and got online successfully.
Variable fields	$1: Interface type and number $2: MAC address $3: VLAN ID $4: Username
Severity level	6
Example	PORTSEC/6/PORTSEC_DOT1X_LOGIN_SUCC: -IfName=Ethernet1/0/1-MACAddr=00:11:43:C5:4B:23-VLANId=1-UserName=test; The user passed 802.1X authentication and got online successfully.
Explanation	A user passed 802.1X authentication and got online successfully.
Recommended action	No action is required.

PORTSEC_DOT1X_LOGOFF

Message text	-IfName=[STRING]-MACAddr=[STRING]-VLANId=[INTEGER]-UserName=[STRING]-ErrCode=[INTEGER]; Session of the 802.1X user was terminated.
Variable fields	$1: Interface type and number $2: MAC address $3: VLAN ID $4: Username $5: Error code
Severity level	6
Example	PORTSEC/6/PORTSEC_DOT1X_LOGOFF: -IfName=Ethernet1/0/1-MACAddr=00:11:43:C5:4B:23-VLANId=1-UserName=test-ErrCode=34; Session of the 802.1X user was terminated.
Explanation	The 802.1x user logged off or got kicked out.
Recommended action	No action is required.

PORTSEC_MACAUTH_LOGIN_FAILURE

Message text	-IfName=[STRING]-MACAddr=[STRING]-VLANId=[INTEGER]-UserName=[STRING]-UserNameFormat=[STRING]; The user failed the MAC address authentication.
Variable fields	$1: Interface type and number $2: MAC address $3: VLAN ID $4: Username $5: Username format, fixed or MAC address
Severity level	6
Example	PORTSEC/6/PORTSEC_MACAUTH_LOGIN_FAILURE: -IfName=Ethernet1/0/1 0/0-MACAddr=00:11:43:C5:4B:23-VLANId=1-UserName=test-UserNameFormat=fixed; The user failed the MAC address authentication.
Explanation	The user failed the MAC address authentication.
Recommended action	No action is required.

PORTSEC_MACAUTH_LOGIN_SUCC

Message text	-IfName=[STRING]-MACAddr=[STRING]-VLANId=[INTEGER]-UserName=[STRING]-UserNameFormat=[STRING]; The user passed MAC address authentication and got online successfully.
Variable fields	$1: Interface type and number $2: MAC address $3: VLAN ID $4: Username $5: Username format, fixed or MAC address
Severity level	6
Example	PORTSEC/6/PORTSEC_MACAUTH_LOGIN_SUCC: -IfName=Ethernet1/0/1-MACAddr=00:11:43:C5:4B:23-VLANId=1-UserName=test-UserNameFormat=fixed; The user passed MAC address authentication and got online successfully.
Explanation	A user passed MAC address authentication and got online successfully.
Recommended action	No action is required.

PORTSEC_MACAUTH_LOGOFF

Message text	-IfName=[STRING]-MACAddr=[STRING]-VLANId=[INTEGER]-UserName=[STRING]-UserNameFormat=[STRING]; Session of the MAC-AUTH user was terminated.
Variable fields	$1: Interface type and number $2: MAC address $3: VLAN ID $4: User name $5: Username format, fixed or MAC address
Severity level	6
Example	PORTSEC/6/PORTSEC_MACAUTH_LOGOFF: -IfName=Ethernet1/0/1-MACAddr=00:11:43:C5:4B:23-VLANId=1-UserName=test-UserNameFormat=fixed; Session of the MAC-AUTH user was terminated.
Explanation	The MAC-AUTH user logged off or got kicked out.
Recommended action	No action is required.

QINQ Messages

This section contains all the system log messages related to QINQ.

QINQ_ETHERNETTYPE_NORESOURCE

Message text	Failed to configure the Ethernet type on interface [STRING] because of insufficient resources. Please manually cancel the configuration.
Variable fields	$1: interface name
Severity level	4
Example	QINQ/4/QINQ_ETHERNETTYPE_NORESOURCE: Failed to configure the Ethernet type on interface GigabitEthernet 1/0/25 because of insufficient resources. Please manually cancel the configuration.
Explanation	The system displays error information for activating the configuration of Ethernet type.
Recommended action	Manually cancel the configuration of Ethernet type.

QINQ_OUTERVLANTAG_NORESOURCE

Message text	Failed to configure the outer VLAN tag to be added for packets on interface [STRING] because of insufficient resources. Please manually cancel the configuration.
Variable fields	$1: interface name
Severity level	4
Example	QINQ/4/QINQ_OUTERVLANTAG_NORESOURCE: Failed to configure the outer VLAN tag to be added for packets on interface GigabitEthernet 1/0/25 because of insufficient resources. Please manually cancel the configuration.
Explanation	The system displays error information for activating the configuration of outer VLAN tag.
Recommended action	Manually cancel the configuration of outer VLAN tag.

QoS Messages

This section contains the entire system log messages related to QOS.

QOS_POLICY_APPLYIF_CBFAIL

Message text	Classifier-behavior [STRING] in policy [STRING] applied on interface [STRING] failed. Reason: [STRING]
Variable fields	$1: The classifier-behavior name. $2: The policy name. $3: The port name. $4: The failed reason.
Severity level	4
Example	QOS/4/QOS_POLICY_APPLYIF_CBFAIL: Classifier-behavior b in policy b applied on interface Ethernet1/0/1 failed. Reason: No actions in behavior.
Explanation	Error info for applying policy on interface.
Recommended action	No action is required.

QOS_POLICY_APPLYGLOBAL_CBFAIL

Message text	Classifier-behavior [STRING] in policy [STRING] applied globally failed. Reason: [STRING]
Variable fields	$1: The classifier-behavior name. $2: The policy name. $3: The failed reason.
Severity level	4
Example	QOS/4/QOS_POLICY_APPLYGLOBAL_CBFAIL: Slot=3; Classifier-behavior b in policy b applied globally failed. Reason: No actions in behavior.
Explanation	Error info for applying policy globally.
Recommended action	No action is required.

QOS_POLICY_APPLYCOPP_CBFAIL

Message text	Applying classifier-behavior [STRING] in policy [STRING] to the control plane of slot [ULONG] failed. Reason: [STRING]
Variable fields	$1: The classifier-behavior name. $2: The policy name. $3: The slot number. $4: The failed reason.
Severity level	4
Example	QOS/4/QOS_POLICY_APPLYCOPP_CBFAIL: Slot=3; Applying classifier-behavior d in policy b to the control plane of slot 3 failed. Reason: No actions in behavior.
Explanation	Error info for applying a policy to a control plane.
Recommended action	No action is required.

QOS_POLICY_APPLYIF_FAIL

Message text	Applying or refreshing QoS policy [STRING] to interface [STRING] failed. Reason: [STRING]
Variable fields	$1: The policy name. $2: The port name. $3: The failed reason.
Severity level	4
Example	QOS/4/QOS_POLICY_APPLYIF_FAIL: Slot=3; Applying or refreshing QoS policy b to interface Ethernet1/0/1 failed. Reason: Not supported by hardware.
Explanation	Error info for applying a policy to an interface.
Recommended action	No action is required.

QOS_POLICY_APPLYGLOBAL_FAIL

Message text	Applying QoS policy [STRING] globally failed. Reason: [STRING]
Variable fields	$1: The policy name. $2: The failed reason.
Severity level	4
Example	QOS/4/ QOS_POLICY_APPLYGLOBAL_FAIL: Slot=3; Applying or refreshing QoS policy b globally failed. Reason: Not supported by hardware.
Explanation	Error info for applying a policy globally.
Recommended action	No action is required.

QOS_POLICY_APPLYCOPP_FAIL

Message text	Applying or refreshing QoS policy [STRING] to the control plane of slot [ULONG] failed. Reason: [STRING]
Variable fields	$1: The policy name. $2: The slot number. $3: The failed reason.
Severity level	4
Example	QOS/4/QOS_POLICY_APPLYCOPP_FAIL: Slot=3; Applying or refreshing QoS policy b to the control plane of slot 3 failed. Reason: Not supported by hardware.
Explanation	Error info for applying a policy to a control plane.
Recommended action	No action is required.

FAILED_TO_APPLY_QOS_PROFILE

Message text	Failed to apply QoS policy [STRING] in the [STRING] direction of user profile [STRING]!
Variable fields	$1: Policy name $2: Direction: inbound or outbound $3: User profile name
Severity level	5
Example	QOS/5/FAILED_TO_APPLY_QOS_PROFILE: Failed to apply QoS policy policy1 in the inbound direction of user profile user1!
Explanation	User profile failed to apply qos policy.
Recommended action	No action is required.

FAILED_TO_CHECK_QOS_PROFILE

Message text	Failed to check QoS policy [STRING] in the [STRING] direction of user profile [STRING]!
Variable fields	$1: Policy name $2: Direction: inbound or outbound $3: User profile name
Severity level	5
Example	QOS/5/FAILED_TO_CHECK_QOS_PROFILE: Failed to check QoS policy policy1 in the inbound direction of user profile user1!
Explanation	User profile failed to check qos policy.
Recommended action	No action is required.

QOS_POLICY_NOTSUPPORT

Message text	Error occurred in policy [STRING] classifier [STRING] for not support.
Variable fields	$1: The policy name. $2: The classifier name.
Severity level	3
Example	QOS/3/QOS_POLICY_NOTSUPPORT: Error occurred in policy pp classifier cc for not support.
Explanation	The synchronization of policy-class to hardware is not supported.
Recommended action	Delete the policy-class.

QOS_POLICY_NO_ENOUGH_RESOURCE

Message text	Error occurred in policy [STRING] classifier [STRING] for not enough resource.
Variable fields	$1: The policy name. $2: The classifier name.
Severity level	3
Example	QOS/3/QOS_POLICY_NO_ENOUGH_RESOURCE: Error occurred in policy pp classifier cc for not enough resource.
Explanation	There is not enough resource for the synchronization of policy-class to hardware.
Recommended action	Delete the policy-class.

QOS_POLICY_COMMON_ERROR

Message text	Error occurred in policy [STRING] classifier [STRING].
Variable fields	$1: The policy name. $2: The classifier name.
Severity level	3
Example	QOS/3/QOS_POLICY_COMMON_ERROR: Error occurred in policy pp classifier cc.
Explanation	Other error occurred in the synchronization of policy-class to hardware.
Recommended action	Delete the policy-class.

RDS Messages

This section contains the entire system log messages related to RDS.

RDS_FAILURE

Message text	-IfName=[STRING]-VLANId=[ULONG]-MACAddr=[STRING]-IPAddr=[STRING]-IPv6Addr=[STRING]-UserName=[STRING]; User failed to get online. [STRING]
Variable fields	$1: Interface type and number $2: VLAN ID $3: MAC address $4: IP address $5: IPv6 address $6: Username $7:Authentication failure. Possible reasons include: “Failed to send the accounting packet.” "Failed to create the accounting packet." "Unsupported RADIUS attributes."
Severity level	5
Example	RDS/5/RDS_FAILURE: -IfName=Ethernet1/0/1-VLANId=1-MACAddr=00:11:43:C5:4B:23-IPAddr=192.168.0.1-IPv6Addr=2002::1-UserName=test@system; User failed to get online. Failed to send the accounting packet.
Explanation	A user failed to get online.
Recommended action	No action is required.

RDS_SUCC

Message text	-IfName=[STRING]-VLANId=[ULONG]-MACAddr=[STRING]-IPAddr=[STRING]-IPv6Addr=[STRING]-UserName=[STRING]; User got online successfully.
Variable fields	$1: Interface type and number $2: VLAN ID $3: MAC address $4: IP address $5: IPv6 address $6: Username
Severity level	6
Example	RDS/6/RDS_SUCC: -IfName=Ethernet1/0/1-VLANId=1-MACAddr=00:11:43:C5:4B:23-IPAddr=192.168.0.1-IPv6Addr=2002::1-UserName=test@system; User got online successfully.
Explanation	A user got online successfully.
Recommended action	No action is required.

RIP Messages

RIP_RT_LMT

Message text	RIP [ULONG] Route limit reached
Variable fields	$1: Process ID
Severity level	4
Example	RIP/4/RIP_RT_LMT: RIP 1 Route limit reached.
Explanation	RIP routes reach limit.
Recommended action	Please check RIP routes and modify RIP configuration to make routes under the limit.

RMON Messages

This section contains the entire system log messages related to RMON.

RMON_ADDINFO

Message text	[STRING] table is added a valid row with index [ULONG] by [STRING].
Variable fields	$1: The name of table. $2: An index that uniquely identifies an entry in the table. $3: The owner of the entry.
Severity level	6
Example	RMON/6/RMON_ADDINFO: Alarm table is added a valid row with index 15 by user.
Explanation	A new entry has been added into alarm table or event table successfully.
Recommended action	No action is required.

SC Messages

This section contains the entire system log messages related to SC.

SC_AAA_LAUNCH

Message text	-AAAType=[STRING]-AAAScheme=[STRING]-Service=[STRING]-UserName=[STRING]; AAA launched.
Variable fields	$1: AAA type $2: AAA Scheme $3: Service $4: Username
Severity level	6
Example	SC/6/SC_AAA_LAUNCH: -AAAType=AUTHEN-AAAScheme= radius-scheme cams-Service=login-UserName=cwf@system; AAA launched.
Explanation	A user start a AAA request. A user start a AAA request.
Recommended action	No action is required.

SC_AAA_SUCCESS

Message text	AAAType=[STRING]-AAAScheme=[STRING]-Service=[STRING]-UserName=[STRING]; AAA is successful.
Variable fields	$1: AAA type $2: AAA Scheme $3: Service $4: Username
Severity level	6
Example	SC/6/SC_AAA_SUCCESS: -AAAType=AUTHOR-AAAScheme= radius-scheme cams-Service=login-UserName=cwf@system; AAA is successful.
Explanation	A AAA request is accepted. A user ‘s AAA request is accepted.
Recommended action	No action is required.

SC_AAA_FAILURE

Message text	-AAAType=[STRING]-AAAScheme=[STRING]-Service=[STRING]-UserName=[STRING]; AAA is failed. [STRING]
Variable fields	$1: AAA type, may be authentication, authorization or accouting $2: AAA Scheme, may be radius-scheme, hwtacacs-scheme, local or none $3: Service, may be login, super or command. $4: Username $5: Reason of failure, may be: “Common.” “No response.”
Severity level	5
Example	SC/5/SC_AAA_FAILURE: -AAAType=ACCOUNT-AAAScheme= radius-scheme cams-Service=login-UserName=cwf@system; AAA is failed. No respon se.
Explanation	A user’s AAA request is rejected for no response from server, or for other common reasons such as user name or password error.
Recommended action	No action is required.

SHELL Messages

This section contains the entire system log messages related to SHELL.

SHELL_LOGIN

Message text	[STRING] logged in from [STRING].
Variable fields	$1: The name of users. $2: The type of users.
Severity level	5
Example	SHELL/5/SHELL_LOGIN: Console logged in from con0.
Explanation	A user login successfully.
Recommended action	No action is required.

SHELL_LOGOUT

Message text	[STRING] logged out from [STRING].
Variable fields	$1: The name of users. $2: The type of users.
Severity level	5
Example	SHELL/5/SHELL_LOGOUT: Console logged out from con0.
Explanation	A user quitted from system.
Recommended action	No action is required.

SHELL_CMD

Message text	-Task=[STRING]-IPAddr=[STRING]-User=[STRING]; Command is [STRING]
Variable fields	$1: Task name, if there isn’t task name, ‘*’ instead. $2: IP address, if there isn’t IP address, ‘’ instead. $3: User name, if there isn’t user name, ‘**’ instead. $4: Command string.
Severity level	6
Example	SHELL/6/SHELL_CMD: -Task=co0-IPAddr=-User=; Command is display this
Explanation	Record command string.
Recommended action	No action is required.

SHELL_LOGINFAIL

Message text	[STRING] failed to log in [STRING].
Variable fields	$1: the user name $2: from IP (MAC) on VTY index.
Severity level	5
Example	SHELL/5/SHELL_LOGINFAIL: TELNET user failed to log in from 12.130.2.19(000f-e239-1f97) on VTY0.
Explanation	This is a common print info and output the parameter info.
Recommended action	No action is required.

SNMP Messages

This section contains the entire system log messages related to SNMP.

SNMP_GET

Message text	-seqNO=[ULONG]-srcIP=[STRING]-op=GET-node=[STRING]-value=[STRING]; The agent received a message.
Variable fields	$1: The sequence number of snmp operation log $2: The source IP address of the NMS. $3: The operation type of the NMS $4: The MIB object name and OID $5: The value field of the response packet
Severity level	6
Example	SNMP/6/SNMP_GET: -seqNO=1-srcIP=192.168.28.28-op=GET-node=sysLocation(1.3.6.1.2.1.1.6.0)-value=; The agent received a message.
Explanation	Record the information about the SNMP get request packet.
Recommended action	No action is required.

SNMP_SET

Message text	-seqNO=[ULONG]-srcIP=[STRING]-op=SET-errorIndex=[ULONG]-errorStatus=[STRING]-node=[STRING]-value=[STRING]; The agent received a message.
Variable fields	$1: The sequence number of snmp operation log $2: The source IP address of the NMS. $3: The operation type of the NMS $4: The error index of the set operation $5: The error status of the set operation $6: The MIB object name and OID $7: The value field of the response packet
Severity level	6
Example	SNMP/6/SNMP_SET: -seqNO=3-srcIP=192.168.28.28-op=SET-errorIndex=0-errorStatus=noError-node=sysLocation(1.3.6.1.2.1.1.6.0)-value=Hangzhou China; The agent received a message.
Explanation	Record the information about set request and response packet
Recommended action	No action is required.

SSH Messages

This section contains the entire system log messages related to SSH.

SSH_LOGIN

Message text	[STRING] user [STRING] (IP: [STRING]) logged in successfully.
Variable fields	$1: User service type. $2: Username. $3: IP address of the SSH client.
Severity level	6
Example	SSH/6/SSH_LOGIN: STEL user user1 (IP: 1.1.1.1) logged in successfully.
Explanation	The SSH user logged in successfully.
Recommended action	No action is required.

SSH_LOGOUT

Message text	[STRING] user [STRING] (IP: [STRING]) logged out.
Variable fields	$1: User service type. $2: Username. $3: IP address of the SSH client.
Severity level	6
Example	SSH/6/SSH_LOGOUT: STEL user user1 (IP: 1.1.1.1) logged out.
Explanation	The SSH user logged out.
Recommended action	No action is required.

SSH_CONNECTION_CLOSE

Message text	[STRING] user [STRING] (IP: [STRING]) logged out because the SSH client closed the connection.
Variable fields	$1: User service type. $2: Username. $3: IP address of the SSH client.
Severity level	6
Example	SSH/6/SSH_CONNECTION_CLOSE: STEL user user1 (IP: 1.1.1.1) logged out because the SSH client closed the connection.
Explanation	The SSH client closed the connection and the disconnection logged out the user.
Recommended action	No action is required.

SSH_AUTH_TIMEOUT

Message text	[STRING] user [STRING] (IP: [STRING]) failed to log in because of authentication timeout.
Variable fields	$1: User service type. $2: Username. $3: IP address of the SSH client.
Severity level	6
Example	SSH/6/SSH_AUTH_TIMEOUT: SSH user user1 (IP: 1.1.1.1) failed to log in because of authentication timeout.
Explanation	The SSH user initiated a login request, but the authentication timed out. This caused the login failure.
Recommended action	Check network connection.

SSH_SFTP_OPER

Message text	Received SFTP user [STRING] (IP: [STRING]) request: [STRING].
Variable fields	$1: Username. $2: IP address of the SSH client. $3: Requested operation.
Severity level	5
Example	SSH/5/SSH_SFTP_OPER: Received SFTP user user1 (IP: 1.1.1.1) request: Read file flash:/logfile.txt.
Explanation	An SFTP user request was received.
Recommended action	No action is required.

USERLOG Messages

This section contains the entire system log messages related to USERLOG.

USERLOG_NAT

Message text	\r\n-protType(1001)=[STRING]-insideIPAddr(1003)=[STRING]-insidePortNum(1004)=[INTEGER]-insideNatIPAddr(1005)=[STRING]-insideNatPortNum(1006)=[INTEGER]-destIPAddr(1019)=[STRING]-destPortNum(1020)=[INTEGER]-beginTime_e(1013)=[STRING]-endTime_e(1014)=[STRING]-Operator(1112)=[STRING]
Variable fields	$1: IP protocol type; $2: Source IP address; $3: Source port number; $4: Source NAT IP address; $5: Source NAT port number; $6: Destination IP address; $7: Destination port number; $8: The time at which NAT session is created; $9: The time at which NAT session is deleted; $10: Session Operator;
Severity level	6
Example	USERLOG/6/USERLOG_NAT: -protType(1001)=ICMP-insideIPAddr(1003)=192.168.0.67-insidePortNum(1004)=512-insideNatIPAddr(1005)=169.254.0.67-insideNatPortNum(1006)=12289-destIPAddr(1019)=169.254.0.90-destPortNum(1020)=512-beginTime_e(1013)=04022009111607-endTime_e(1014)=04022009111709-Operator(1112)=(1)Normal over
Explanation	A NAT log is outputted by the way of syslog.
Recommended action	No action is required.

USERLOG_FLOW

Message text	\r\n-protType(1001)=[STRING]-srcIPAddr(1017)=[STRING]-srcPortNum(1018)=[INTEGER]-destIPAddr(1019)=[STRING]-destPortNum(1020)=[INTEGER]-beginTime_e(1013)=[STRING]-endTime_e(1014)=[STRING]-Operator(1112)=[STRING]
Variable fields	$1: IP protocol type; $2: Source IP address; $3: Source port number; $4: Destination IP address; $5: Destination port number; $6: The time at which a flow session is created; $7: The time at which a flow session is deleted; $8: Session Operator;
Severity level	6
Example	USERLOG/6/USERLOG_FLOW: -protType(1001)=UDP-srcIPAddr(1017)=192.168.0.90-srcPortNum(1018)=20202-destIPAddr(1019)=1.1.1.1-destPortNum(1020)=9029-beginTime_e(1013)=04262000133545-endTime_e(1014)=04262000133545-Operator(1112)=(8)Data flow created
Explanation	A flow log is outputted by the way of syslog
Recommended action	No action is required.

USERLOG_FLOW3.0

Message text	\r\n-protType(1001)=[STRING]-insideIPAddr(1003)=[STRING]-insidePortNum(1004)=[INTEGER]-insideNatIPAddr(1005)=[STRING]-insideNatPortNum(1006)=[INTEGER]-outsideIPAddr(1007)=[STRING]-outsidePortNum(1008)=[INTEGER]-outsideNatIPAddr(1009)=[STRING]-outsideNatPortAddr(1010)=[INTEGER]-InTotalPkg(1106)=[INTEGER]-InTotalByte(1107)=[INTEGER]-OutTotalPkg(1108)=[INTEGER]-OutTotalByte(1109)=[INTEGER]-SrcVPNNAME(1080)=[STRING]-DesVPNNAME(1081)=[STRING]-beginTime_e(1013)=[STRING]-endTime_e(1014)=[STRING]-Operator(1112)=[STRING]
Variable fields	$1: IP protocol type; $2: Source IP address; $3: Source port number; $4: Source NAT IP address; $5: Source NAT port; $6 : Destination IP address; $7 : Destination port number; $8: Destination NAT IP address; $9: Destination NAT port number; $10: Received packets; $11: Received bytes; $12: Send packets; $13: Send bytes; $14: Source VPN name; $15: Destination VPN name; $16: The time at which a flow session is created; $17: The time at which a flow session is deleted; $18: Session Operator;
Severity level	6
Example	USERLOG/6/USERLOG_FLOW:-protType(1001)=UDP-insideIPAddr(1003)=192.168.0.90-insidePortNum(1004)=20202-insideNatIPAddr(1005)=192.168.0.90-insideNatPortNum(1006)=20202-outsideIPAddr(1007)=1.1.1.1-outsidePortNum(1008)=9029-outsideNatIPAddr(1009)=1.1.1.1-outsideNatPortAddr(1010)=9029-InTotalPkg(1106)=0-InTotalByte(1107)=0-OutTotalPkg(1108)=1-OutTotalByte(1109)=440-SrcVPNNAME(1080)=none-DesVPNNAME(1081)=none-beginTime_e(1013)=04262000134247-endTime_e(1014)=04262000134247-Operator(1112)=(8)Data flow created.
Explanation	A flow log is outputted by the way of syslog
Recommended action	No action is required.