· Messages for the Comware 9 software platform version based on which the switch release was produced. Some platform system messages might not be available on the switch.

This document is intended only for managing S12500R. Do not use this document for any other device models.

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

System log message format

By default, the system log messages use one of the following formats depending on the output destination:

· Log host:

<PRI>TIMESTAMP Sysname %%vendorMODULE/severity/MNEMONIC: location; CONTENT

· Destinations except for the log host:

Prefix TIMESTAMP Sysname MODULE/severity/MNEMONIC: CONTENT

NOTE:

Log message examples in this document use the format for destinations except the log host. They do not contain elements available only for the log host, including the location element.

Table 1 System log message elements

Element	Description
<PRI>	Priority identifier. This element is contained only in messages sent to the log host. It is calculated by using the following formula: Priority identifier=facilityx8+severity Where: · Facility is specified by using the info-center loghost command. A log host uses this parameter to identify log sources and filter log messages. · Severity represents the importance of the message. For more information about severity levels, see Table 2.
Prefix	Message type identifier. This element is contained in the system log messages sent to non-log host destinations. The element uses the following symbols to indicate message severity: · Percentage sign (%)—Informational and higher levels. · Asterisk (*)—Debug level.
TIMESTAMP	Date and time when the event occurred. The following are commands for configuring the timestamp format: · Log host—Use the info-center timestamp loghost command. · Non-log-host destinations—Use the info-center timestamp command.
Sysname	Name or IP address of the device that generated the message.
%%vendor	Manufacturer flag. This element is %%10 for H3C. This element is contained only in messages sent to the log host.
MODULE	Name of the module that produced the message.
severity	Severity level of the message. (For more information about severity levels, see Table 2.)
MNEMONIC	Text string that uniquely identifies the system message. The maximum length is 32 characters.
location	Optional. This element identifies where the message occurred. This element is contained only in messages sent to the log host. This element presents location information for the message in the following format: -attribute1=x-attribute2=y…-attributeN=z The following are examples of location attributes: · -MDC=XX, which represents the MDC on which the message occurred. · -DevIp=XXX.XXX.XXX.XXX, which represents the source IP of the message. · -Slot=XX, which represents the slot on which the message occurred. · -Chassis=XX-Slot=XX, which represents the chassis and slot on which the message occurred. This element is separated from the message description by using a semicolon (;).
CONTENT	Text string that contains detailed information about the event or error. For variable fields in this element, this document uses the representations in Table 3.

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

Table 2 System log message severity levels

Level	Severity	Description
0	Emergency	The system is unusable. For example, the system authorization has expired.
1	Alert	Action must be taken immediately. For example, traffic on an interface exceeds the upper limit.
2	Critical	Critical condition. For example, the device temperature exceeds the upper limit, the power module fails, or the fan tray fails.
3	Error	Error condition. For example, the link state changes or a storage card is unplugged.
4	Warning	Warning condition. For example, an interface is disconnected, or the memory resources are used up.
5	Notification	Normal but significant condition. For example, a terminal logs in to the device, or the device reboots.
6	Informational	Informational message. For example, a command or a ping operation is executed.
7	Debug	Debugging message.

For variable fields in the message text, this document uses the representations in Table 3. The values are case insensitive, even though the representations are uppercase letters.

Table 3 Variable field representations

Representation	Information type
INT16	Signed 16-bit decimal number.
UINT16	Unsigned 16-bit decimal number.
INT32	Signed 32-bit decimal number.
UINT32	Unsigned 32-bit decimal number.
INT64	Signed 64-bit decimal number.
UINT64	Unsigned 64-bit decimal number.
DOUBLE	Two dot-separated signed 32-bit decimal numbers. The format is [INTEGER].[INTEGER].
HEX	Hexadecimal number.
CHAR	Single character.
STRING	Character string.
IPADDR	IP address.
MAC	MAC address.
DATE	Date.
TIME	Time.

Managing and obtaining system log messages

You can manage system log messages by using the information center.

By default, the information center is enabled. Log messages can be output to the console, log buffer, monitor terminal, log host, and log file.

To filter log messages, use the info-center source command to specify log output rules. A log output rule specifies the source modules and the lowest severity level of log messages that can be output to a destination. A log message is output if its severity level is higher than or equal to the specified level. For example, if you specify a severity level of 6 (informational), log messages that have a severity level from 0 to 6 are output.

For more information about using the information center, see the network management and monitoring configuration guide for the product.

Obtaining log messages from the console terminal

Access the device through the console port. Real-time log messages are displayed on the console terminal.

Obtaining log messages from the log buffer

Use the display logbuffer command to display history log messages in the log buffer.

Obtaining log messages from a monitor terminal

Monitor terminals refer to terminals that access the device through the AUX, VTY, or TTY lines (for example, Telnet). To obtain log messages from a monitor terminal, use the following guidelines:

· To display log messages on the monitor terminal, you must configure the terminal monitor command.

· For monitor terminals, the lowest level of log messages that can be displayed is determined by both the terminal logging level and info-center source commands.

Obtaining log messages from the log file

By default, the log file feature automatically saves logs from the log file buffer to the log file every 24 hours. You can use the info-center logfile frequency command to change the automatic saving internal.

To manually save logs to the log file, use the logfile save command. The log file buffer is cleared each time a save operation is performed.

By default, you can obtain the log file from the cfa0:/logfile/ path if the CF card is not partitioned. If the CF card is partitioned, the file path is cfa1:/logfile/.

Obtaining log messages from a log host

Use the info-center loghost command to specify the service port number and IP address of a log host. To specify multiple log hosts, repeat the command.

For a successful log message transmission, make sure the specified port number is the same as the port number used on the log host. The default service port number is 514.

Software module list

Table 4 lists all software modules that might produce system log messages. This document uses "OPENSRC" to represent all open source modules.

Table 4 Software module list

Module name representation	Module name expansion
AAA	Authentication, Authorization and Accounting
ACL	Access Control List
ARP	Address Resolution Protocol
BFD	Bidirectional Forwarding Detection
BGP	Border Gateway Protocol
CFD	Connectivity Fault Detection
CFGMAN	Configuration Management
DEV	Device Management
DHCP	Dynamic Host Configuration Protocol
DHCPR	IPv4 DHCP Relay
DHCPS	DHCP Server
DHCPS6	DHCPv6 Server
DHCPSP4	DHCP Snooping
DHCPSP6	DHCPv6 Snooping
DIAG	Diagnosis
DLDP	Device Link Detection Protocol
DOT1X	802.1X
DRVPLAT	Drive Plat
DRNI	Distributed Resilient Network Interconnect
EDEV	Extended-Device Management
ERPS	Ethernet Ring Protection Switching
ETH	Ethernet
ETHOAM	Ethernet Operation, Administration and Maintenance
EVB	Edge Virtual Bridging
EVIISIS	Ethernet Virtual Interconnect Intermediate System-to-Intermediate System
FCOE	Fibre Channel Over Ethernet
FCLINK	Fibre Channel Link
FCZONE	Fibre Channel Zone
FIB	Forwarding Information Base
FILTER	Filter
FIPSNG	FIP Snooping
FS	File System
FTPD	File Transfer Protocol Daemon
HA	High Availability
HQOS	Hierarchical QoS
HTTPD	Hypertext Transfer Protocol Daemon
IFNET	Interface Net Management
IKE	Internet Key Exchange
IP6ADDR	IPv6 Addressing
IP6FW	IPv6 Forwarding
IPADDR	IP Addressing
IPFW	IP Forwarding
IPOE	IP Over Ethernet
IPSEC	IP Security
IPSG	IP Source Guard
IRDP	ICMP Router Discovery Protocol
ISIS	Intermediate System-to-Intermediate System
ISSU	In-Service Software Upgrade
L2TPV2	Layer 2 Tunneling Protocol Version 2
L2VPN	Layer 2 VPN
LAGG	Link Aggregation
LDP	Label Distribution Protocol
LLDP	Link Layer Discovery Protocol
LOAD	Load Management
LOGIN	Login
LPDT	Loopback Detection
LS	Local Server
LSPV	LSP Verification
MAC	Media Access Control
MACA	MAC Authentication
MACSEC	MAC Security
MBFD	MPLS BFD
MBUF	Memory buffer
MDC	Multitenant Device Context
MFIB	Multicast Forwarding Information Base
MGROUP	Mirroring group
MPLS	Multiprotocol Label Switching
MTLK	Monitor Link
NAT	Network Address Translation
NETCONF	Network Configuration Protocol
ND	Neighbor Discovery
NQA	Network Quality Analyzer
NTP	Network Time Protocol
OPENSRC	Open Source
OBJP	Object Policy
OFP	OpenFlow Protocol
OPTMOD	Optical Module
OSPF	Open Shortest Path First
OSPFV3	Open Shortest Path First Version 3
PKTCPT	Packet Capture
PFILTER	Packet Filter
PBB	Provider Backbone Bridge
PBR	Policy-Based Routing
PCE	Path Computation Element
PEX	Port Extender
PIM	Protocol Independent Multicast
PING	Packet Internet Groper
PKG	Package
PKI	Public Key Infrastructure
PKT2CPU	Packet to CPU
PORTAL	Portal
PORTSEC	Port Security
PPP	Point to Point Protocol
PPPOES	PPP over Ethernet Server
PWDCTL	Password Control
QOS	Quality of Service
RADIUS	Remote Authentication Dial In User Service
RDDC	Redundancy
RIP	Routing Information Protocol
RIPNG	Routing Information Protocol Next Generation
RM	Routing Management
RRPP	Rapid Ring Protection Protocol
RTM	Real-Time Event Manager
SCM	Service Control Manager
SCRLSP	Static CRLSP
SESSION	Session
SFLOW	Sampler Flow
SHELL	Shell
SLBG	Service Loopback Groups
SLSP	Static LSP
SMLK	Smart Link
SNMP	Simple Network Management Protocol
SSHC	Secure Shell Client
SSHS	Secure Shell Server
STAMGR	Station Management
STM	Stack Topology Management
STP	Spanning Tree Protocol
SYSEVENT	System Event
SYSLOG	System Log
TACACS	Terminal Access Controller Access Control System
TELNETD	Telnet Daemon
TRILL	Transparent Interconnect of Lots of Links
TSTREAM	Telemetry Stream
VCF	Vertical Converged Framework
VLAN	Virtual Local Area Network
VRRP	Virtual Router Redundancy Protocol
VSRP	Virtual Service Redundancy Protocol
VXLAN	Virtual eXtensible LAN
WIPS	Wireless Intrusion Prevention System

Using this document

This document categorizes system log messages by software module. The modules are ordered alphabetically. Except for OPENSRC, the system log messages for each module are listed in alphabetic order of their mnemonic names. The OPENSRC messages are unordered because they use the same mnemonic name (SYSLOG). For each OPENSRC message, the section title uses a short description instead of the mnemonic name.

This document explains messages in tables. Table 5 describes information provided in these tables.

Table 5 Message explanation table contents

Item	Content	Example
Message text	Presents the message description.	ACL [UINT32] [STRING] [UINT64] packet(s).
Variable fields	Briefly describes the variable fields in the order that they appear in the message text. The variable fields are numbered in the "$Number" form to help you identify their location in the message text.	$1: ACL number. $2: ID and content of an ACL rule. $3: Number of packets that matched the rule.
Severity level	Provides the severity level of the message.	6
Example	Provides a real message example. The examples do not include the "<PRI>TIMESTAMP Sysname %%vendor" part or the "Prefix TIMESTAMP Sysname" part, because information in this part varies with system settings.	ACL/6/ACL_STATIS_INFO: ACL 2000 rule 0 permit source 1.1.1.1 0 logging 10000 packet(s).
Explanation	Explains the message, including the event or error cause.	Number of packets that matched an ACL rule. This message is sent when the packet counter changes.
Recommended action	Provides recommended actions. For informational messages, no action is required.	No action is required.

AAA messages

This section contains AAA messages.

AAA_FAILURE

Message text	-AAAType=[STRING]-AAADomain=[STRING]-Service=[STRING]-UserName=[STRING]; AAA failed.
Variable fields	$1: AAA type. $2: AAA scheme. $3: Service. $4: Username.
Severity level	5
Example	AAA/5/AAA_FAILURE: -AAAType=AUTHOR-AAADomain=domain1-Service=login-UserName=cwf@system; AAA failed.
Explanation	An AAA request was rejected. The following are the common reasons: · No response was received from the server. · The username or password was incorrect. · The service type that the user applied for was incorrect.
Recommended action	1. Verify that the device is correctly connected to the server. 2. Enter the correct username and password. 3. Verify that the server settings are the same as the settings on the device. 4. If the problem persists, contact H3C Support.

AAA_LAUNCH

Message text	-AAAType=[STRING]-AAADomain=[STRING]-Service=[STRING]-UserName=[STRING]; AAA launched.
Variable fields	$1: AAA type. $2: AAA scheme. $3: Service. $4: Username.
Severity level	6
Example	AAA/6/AAA_LAUNCH: -AAAType=AUTHEN-AAADomain=domain1-Service=login-UserName=cwf@system; AAA launched.
Explanation	An AAA request was received.
Recommended action	No action is required.

AAA_SUCCESS

Message text	-AAAType=[STRING]-AAADomain=[STRING]-Service=[STRING]-UserName=[STRING]; AAA succeeded.
Variable fields	$1: AAA type. $2: AAA scheme. $3: Service. $4: Username.
Severity level	6
Example	AAA/6/AAA_SUCCESS: -AAAType=AUTHOR-AAADomain=domain1-Service=login-UserName=cwf@system; AAA succeeded.
Explanation	An AAA request was accepted.
Recommended action	No action is required.

ACL messages

This section contains ACL messages.

ACL_ACCELERATE_NO_RES

Message text	Failed to accelerate [STRING] ACL [UINT32]. The resources are insufficient.
Variable fields	$1: ACL type. $2: ACL number.
Severity level	4
Example	ACL/4/ACL_ACCELERATE_NO_RES: Failed to accelerate IPv6 ACL 2001. The resources are insufficient.
Explanation	Hardware resources were insufficient for accelerating an ACL.
Recommended action	Delete some rules or disabled ACL acceleration for other ACLs to release hardware resources.

ACL_ACCELERATE_NONCONTIGUOUSMASK

Message text	Failed to accelerate ACL [UINT32]. ACL acceleration supports only contiguous wildcard masks.
Variable fields	$1: ACL number.
Severity level	4
Example	ACL/4/ACL_ACCELERATE_NONCONTIGUOUSMASK: Failed to accelerate ACL 2001. ACL acceleration supports only contiguous wildcard masks.
Explanation	ACL acceleration failed because rules containing noncontiguous wildcard masks exist in the ACL.
Recommended action	Check the ACL rules and delete the unsupported configuration.

ACL_ACCELERATE_NOT_SUPPORT

Message text	Failed to accelerate [STRING] ACL [UINT32]. The operation is not supported.
Variable fields	$1: ACL type. $2: ACL number.
Severity level	4
Example	ACL/4/ACL_ACCELERATE_NOT_SUPPORT: Failed to accelerate IPv6 ACL 2001. The operation is not supported.
Explanation	ACL acceleration failed because the system does not support ACL acceleration.
Recommended action	No action is required.

ACL_ACCELERATE_NOT_SUPPORTHOPBYHOP

Message text	Failed to accelerate IPv6 ACL [UINT32]. ACL acceleration does not support the rules that contain the hop-by-hop keywords.
Variable fields	$1: ACL number.
Severity level	4
Example	ACL/4/ACL_ACCELERATE_NOT_SUPPORTHOPBYHOP: Failed to accelerate IPv6 ACL 2001. ACL acceleration does not support the rules that contain the hop-by-hop keywords.
Explanation	ACL acceleration failed for the IPv6 ACL because rules containing the hop-by-hop keyword exist in the ACL.
Recommended action	Check the ACL rules and delete the unsupported configuration.

ACL_ACCELERATE_NOT_SUPPORTMULTITCPFLAG

Message text	Failed to accelerate IPv6 ACL [UINT32]. ACL acceleration does not support specifying multiple TCP flags in one rule.
Variable fields	$1: ACL number.
Severity level	4
Example	ACL/4/ACL_ACCELERATE_NOT_SUPPORTMULTITCPFLAG: Failed to accelerate IPv6 ACL 2001. ACL acceleration does not support specifying multiple TCP flags in one rule.
Explanation	ACL acceleration failed for the IPv6 ACL because rules containing multiple TCP flags exist in the ACL.
Recommended action	Check the ACL rules and delete the unsupported configuration.

ACL_ACCELERATE_UNK_ERR

Message text	Failed to accelerate [STRING] ACL [UINT32].
Variable fields	$1: ACL type. $2: ACL number.
Severity level	4
Example	ACL/4/ACL_ACCELERATE_UNK_ERR: Failed to accelerate IPv6 ACL 2001.
Explanation	ACL acceleration failed because of an unknown error.
Recommended action	No action is required.

ACL_IPV6_STATIS_INFO

Message text	IPv6 ACL [UINT32] [STRING] [UINT64] packet(s).
Variable fields	$1: ACL number. $2: ID and content of an IPv6 ACL rule. $3: Number of packets that matched the rule.
Severity level	6
Example	ACL6/6/ACL_IPV6_STATIS_INFO: IPv6 ACL 2000 rule 0 permit source 1:1::/64 logging 1000 packet(s).
Explanation	The number of packets matching the IPv6 ACL rule changed.
Recommended action	No action is required.

ACL_NO_MEM

Message text	Failed to configure [STRING] ACL [UINT] due to lack of memory.
Variable fields	$1: ACL type. $2: ACL number.
Severity level	3
Example	ACL/3/ACL_NO_MEM: Failed to configure ACL 2001 due to lack of memory.
Explanation	Configuring the ACL failed because memory is insufficient.
Recommended action	Use the display memory-threshold command to check the memory usage.

ACL_STATIS_INFO

Message text	ACL [UINT32] [STRING] [UINT64] packet(s).
Variable fields	$1: ACL number. $2: ID and content of an IPv4 ACL rule. $3: Number of packets that matched the rule.
Severity level	6
Example	ACL/6/ACL_STATIS_INFO: ACL 2000 rule 0 permit source 1.1.1.1 0 logging 10000 packet(s).
Explanation	The number of packets matching the IPv4 ACL rule changed.
Recommended action	No action is required.

ARP messages

This section contains ARP messages.

ARP_ACTIVE_ACK_NO_REPLY

Message text	No ARP reply from IP [STRING] was received on interface [STRING].
Variable fields	$1: IP address. $2: Interface name.
Severity level	6
Example	ARP/6/ARP_ACTIVE_ACK_NO_REPLY: No ARP reply from IP 192.168.10.1 was received on interface GigabitEthernet1/0/1.
Explanation	The ARP active acknowledgement feature did not receive an ARP reply after it sent an ARP request to the sender IP of an ARP message. This message indicates the risk of attacks.
Recommended action	1. Verify that the learned ARP entries on the device are consistent with the existing legal devices. When gateways and servers are on the network, check the ARP entries for these devices first. 2. If the ARP entries are correct and the attack continues, contact H3C Support.

ARP_ACTIVE_ACK_NOREQUESTED_REPLY

Message text	Interface [STRING] received from IP [STRING] an ARP reply that was not requested by the device.
Variable fields	$1: Interface name. $2: IP address.
Severity level	6
Example	ARP/6/ARP_ACTIVE_ACK_NOREQUESTED_REPLY: Interface GigabitEthernet1/0/1 received from IP 192.168.10.1 an ARP reply that was not requested by the device.
Explanation	The ARP active acknowledgement feature received an unsolicited ARP reply from a sender IP. This message indicates the risk of attacks.
Recommended action	No action is required. The device discards the ARP reply automatically.

ARP_BINDRULETOHW_FAILED

Message text	Failed to download binding rule to hardware on the interface [STRING], SrcIP [IPADDR], SrcMAC [MAC], VLAN [UINT16], Gateway MAC [MAC].
Variable fields	$1: Interface name. $2: Source IP address. $3: Source MAC address. $4: VLAN ID. $5: Gateway MAC address.
Severity level	5
Example	ARP/5/ARP_BINDRULETOHW_FAILED: Failed to download binding rule to hardware on the interface GigabitEthernet1/0/1, SrcIP 1.1.1.132, SrcMAC 0015-E944-A947, VLAN 1, Gateway MAC 00A1-B812-1108.
Explanation	The system failed to set a binding rule to the hardware on an interface. The message is sent in any of the following situations: · The resources are not sufficient for the operation. · The memory is not sufficient for the operation. · A hardware error occurs.
Recommended action	To resolve the problem: 1. Execute the display qos-acl resource command to check if the ACL resources for the operation are sufficient. ¡ If yes, proceed to step 2. ¡ If no, delete unnecessary configuration to release ACL resources. If no configuration can be deleted, proceed to step 2. 2. Execute the display memory command to check if the memory for the operation is sufficient. ¡ If yes, proceed to step 3. ¡ If no, delete unnecessary configuration to release memory. If no configuration can be deleted, proceed to step 3. 3. Delete the configuration and perform the operation again.

ARP_DETECTION_LOG

Message text	Detected an ARP attack on interface [STRING]: IP [STRING], MAC [STRING], VLAN [STRING]. [UINT32] packet(s) dropped.
Variable fields	$1: Interface name. $2: IP address. $3: MAC address. $4: VLAN ID. $5: Number of dropped packets.
Severity level	5
Example	ARP/5/ARP_INSPECTION: -MDC=1; Detected an ARP attack on interface GigabitEthernet1/0/1: IP 1.1.1.1, MAC 1-1-1, VLAN 100. 2 packet(s) dropped.
Explanation	An ARP attack was detected on an interface and attack packets were dropped.
Recommended action	Check the source of the ARP attack.

ARP_DUPLICATE_IPADDR_DETECT

Message text	Detected an IP address conflict. The device with MAC address [STRING] connected to interface [STRING] in VSI [STRING] and the device with MAC address [STRING] connected to interface [STRING] in VSI [STRING] were using the same IP address [IPADDR].
Variable fields	$1: MAC address. $2: Interface name. (The interface can be a tunnel interface, Layer 3 interface, or Ethernet service instance.) $3: VSI name. $4: MAC address. $5: Interface name. (The interface can be a tunnel interface, Layer 3 interface, or Ethernet service instance.) $6: VSI name. $7: Conflicting IP address.
Severity level	6
Example	ARP/6/ ARP_DUPLICATE_IPADDR_DETECT: Detected an IP address conflict. The device with MAC address 00-00-01 connected to interface GigabitEthernet1/0/1 service-instance 1000 in VSI vpna and the device with MAC address 00-00-02 connected to interface tunnel 10 in VSI vpna were using the same IP address 192.168.1.1.
Explanation	This message is sent when an interface receives an ARP message in which the sender information conflicts with an existing ARP entry. The sender IP address is the same as the IP address in the entry, but the MAC addresses are different.
Recommended action	Change the IP address on either of the two devices.

ARP_DYNAMIC

Message text	The maximum number of dynamic ARP entries for the device reached.
Variable fields	N/A
Severity level	6
Example	ARP/6/ARP_DYNAMIC: The maximum number of dynamic ARP entries for the device reached.
Explanation	The maximum number of dynamic ARP entries for the device was reached.
Recommended action	No action is required.

ARP_DYNAMIC_IF

Message text	The maximum number of dynamic ARP entries for interface [STRING] reached.
Variable fields	$1: Interface name.
Severity level	6
Example	ARP/6/ARP_DYNAMIC_IF: The maximum number of dynamic ARP entries for interface GigabitEthernet1/0/1 reached.
Explanation	The maximum number of dynamic ARP entries for the specified interface was reached.
Recommended action	No action is required.

ARP_DYNAMIC_SLOT

Message text	Pattern 1: The maximum number of dynamic ARP entries for slot [INT32] reached. Pattern 2: The maximum number of dynamic ARP entries for chassis [INT32] slot [INT32] reached.
Variable fields	Pattern 1: $1: Slot number. Pattern 2: $1: Chassis number. $2: Slot number.
Severity level	6
Example	ARP/6/ARP_DYNAMIC_SLOT: The maximum number of dynamic ARP entries for slot 2 reached.
Explanation	Pattern 1: The maximum number of dynamic ARP entries for the slot was reached. Pattern 2: The maximum number of dynamic ARP entries for the slot on the chassis was reached.
Recommended action	No action is required.

ARP_ENTRY_CONFLICT

Message text	The software entry for [STRING] on [STRING] and the hardware entry did not have the same [STRING].
Variable fields	$1: IP address. $2: VPN instance name. If the ARP entry belongs to the public network, this field displays the public network. $3: Inconsistent items: ¡ MAC address. ¡ output interface. ¡ output port. ¡ outermost layer VLAN ID. ¡ second outermost layer VLAN ID. ¡ VSI index. ¡ link ID.
Severity level	6
Example	ARP/6/ARP_ENTRY_CONFLICT: The software entry for 1.1.1.1 on the VPN a and the hardware entry did not have the same MAC address, output port, VSI index, and link ID. ARP/6/ARP_ENTRY_CONFLICT: The software entry for 1.1.1.2 on the public network and the hardware entry did not have the same MAC address, output port, VSI index, and link ID.
Explanation	The software entry for the specified IP address is not the same as the hardware entry. For example, they do not have the same output interface.
Recommended action	No action is required. ARP automatically refreshes the hardware entries.

ARP_HOST_IP_CONFLICT

Message text	The host [STRING] connected to interface [STRING] cannot communicate correctly, because it uses the same IP address as the host connected to interface [STRING].
Variable fields	$1: IP address. $2: Interface name. $3: Interface name.
Severity level	4
Example	ARP/4/ARP_HOST_IP_CONFLICT: The host 1.1.1.1 connected to interface GigabitEthernet1/0/1 cannot communicate correctly, because it uses the same IP address as the host connected to interface GigabitEthernet1/0/2.
Explanation	The sender IP address in a received ARP message conflicted with the IP address of a host connected to another interface.
Recommended action	Check whether the hosts that send the ARP messages are legitimate. Disconnect the illegal host from the network.

ARP_LOCALPROXY_ENABLE_FAILED

Message text	Failed to enable local proxy ARP on interface [STRING].
Variable fields	$1: Interface name.
Severity level	4
Example	ARP/4/ARP_LOCALPROXY_ENABLE_FAILED: -MDC=1-Slot=2; Failed to enable local proxy ARP on interface VSI-interface 1.
Explanation	This message is sent when the device fails to enable local proxy ARP on an interface in a slot. If the interface resides on the MPU, the slot number is 0.
Recommended action	1. Verify that the card supports local proxy ARP. 2. Verify that sufficient hardware resources are available.

ARP_RATE_EXCEEDED

Message text	The ARP packet rate ([UINT32] pps) exceeded the rate limit ([UINT32] pps) on interface [STRING] in the last [UINT32] seconds.
Variable fields	$1: ARP packet rate. $2: ARP limit rate. $3: Interface name. $4: Interval time.
Severity level	4
Example	ARP/4/ARP_RATE_EXCEEDED: The ARP packet rate (100 pps) exceeded the rate limit (80 pps) on interface GigabitEthernet1/0/1 in the last 10 seconds.
Explanation	An interface received ARP messages at a higher rate than the rate limit.
Recommended action	Verify that the hosts at the sender IP addresses are legitimate.

ARP_RATELIMIT_NOTSUPPORT

Message text	Pattern 1: ARP packet rate limit is not support on slot [INT32]. Pattern 2: ARP packet rate limit is not support on chassis [INT32] slot [INT32].
Variable fields	Pattern 1: $1: Slot number. Pattern 2: $1: Chassis number. $2: Slot number.
Severity level	6
Example	ARP/6/ARP_RATELIMIT_NOTSUPPORT: ARP packet rate limit is not support on slot 2.
Explanation	Pattern 1: ARP packet rate limit is not supported on the slot. Pattern 2: ARP packet rate limit is not supported on the slot of the chassis was reached.
Recommended action	Verify that the host at the sender IP address is legitimate.

ARP_SENDER_IP_INVALID

Message text	Sender IP [STRING] was not on the same network as the receiving interface [STRING].
Variable fields	$1: IP address. $2: Interface name.
Severity level	6
Example	ARP/6/ARP_SENDER_IP_INVALID: Sender IP 192.168.10.2 was not on the same network as the receiving interface GigabitEthernet1/0/1.
Explanation	The sender IP of a received ARP message was not on the same network as the receiving interface.
Recommended action	Verify that the host at the sender IP address is legitimate.

ARP_SENDER_MAC_INVALID

Message text	Sender MAC [STRING] was not identical to Ethernet source MAC [STRING] on interface [STRING].
Variable fields	$1: MAC address. $2: MAC address. $3: Interface name.
Severity level	6
Example	ARP/6/ARP_SENDER_MAC_INVALID: Sender MAC 0000-5E14-0E00 was not identical to Ethernet source MAC 0000-5C14-0E00 on interface GigabitEthernet1/0/1.
Explanation	An interface received an ARP message. The sender MAC address in the message body was not identical to the source MAC address in the Ethernet header.
Recommended action	Verify that the host at the sender MAC address is legitimate.

ARP_SENDER_SMACCONFLICT

Message text	Packet was discarded because its sender MAC address was the MAC address of the receiving interface. Interface: [STRING], sender IP: [STRING], target IP: [STRING].
Variable fields	$1: Interface name. $2: Sender IP address. $3: Target IP address.
Severity level	6
Example	ARP/6/ ARP_SENDER_SMACCONFLICT: Packet discarded for the sender MAC address is the same as the receiving interface. Interface: GigabitEthernet1/0/1 sender IP: 1.1.2.2 target IP: 1.1.2.1,
Explanation	The sender MAC address of a received ARP packet conflicts with the MAC address of the device.
Recommended action	No action is required.

ARP_SENDER_SMACCONFLICT_VSI

Message text	Packet was discarded because its sender MAC address was the MAC address of the receiving interface. Interface: [STRING], sender IP: [STRING], target IP: [STRING],VSI index: [UINT32], link ID: [UINT32].
Variable fields	$1: Interface name. $2: Sender IP address. $3: Target IP address. $4: VSI index. $5: Link ID.
Severity level	6
Example	ARP/6/ ARP_SENDER_SMACCONFLICT_VSI: Packet discarded for the sender MAC address is the same as the receiving interface. Interface: VSI3 sender IP: 1.1.2.2 target IP: 1.1.2.1, VSI Index: 2, Link ID: 0
Explanation	The sender MAC address of a received ARP packet conflicts with the MAC address of the device. The receiving interface is a VSI interface.
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 GigabitEthernet1/0/1.
Explanation	The source MAC-based ARP attack detection feature received more ARP packets from the same MAC address within 5 seconds than the specified threshold. This message indicates the risk of attacks.
Recommended action	Verify that the host at the source MAC address is legitimate.

ARP_SUP_ENABLE_FAILED

Message text	Failed to enable ARP flood suppression on VSI [STRING].
Variable fields	$1: VSI name.
Severity level	4
Example	ARP/4/ARP_SUP_ENABLE_FAILED: -MDC=1; Failed to enable ARP flood suppression on VSI vpna.
Explanation	This message is sent when the system failed to enable ARP flood suppression for a VSI. The minimum interval between two log messages is 2 seconds. To make the system send the message successfully, wait for a minimum of 2 seconds before you enable ARP flood suppression for another VSI.
Recommended action	1. Verify that the device supports ARP flood suppression. 2. Verify that the hardware resources are sufficient.

ARP_TARGET_IP_INVALID

Message text	Target IP [STRING] was not the IP of the receiving interface [STRING].
Variable fields	$1: IP address. $2: Interface name.
Severity level	6
Example	ARP/6/ARP_TARGET_IP_INVALID: Target IP 192.168.10.2 was not the IP of the receiving interface GigabitEthernet1/0/1.
Explanation	The target IP address of a received ARP message was not the IP address of the receiving interface.
Recommended action	Verify that the host at the sender IP address is legitimate.

ARP_THRESHOLD_REACHED

Message text	The alarm threshold for dynamic ARP entry learning was reached on interface [STRING].
Variable fields	$1: Interface name.
Severity level	4
Example	ARP/4/ARP_THRESHOLD_REACHED: The alarm threshold for dynamic ARP entry learning was reached on interface GigabitEthernet1/0/1.
Explanation	This message is sent when the alarm threshold for dynamic ARP learning was reached on GigabitEthernet 1/0/1.
Recommended action	Verify that the number of learned dynamic ARP entries matches the actual number of devices in the network and no ARP attack sources exist in the network.

ARP_USER_DUPLICATE_IPADDR_DETECT

Message text	Detected a user IP address conflict. New user (MAC [STRING], SVLAN [STRING], CVLAN [STRING]) connecting on interface [STRING] and old user (MAC [STRING], SVLAN [STRING], CVLAN [STRING]) connecting on interface [STRING] were using the same IP address [IPADDR].
Variable fields	$1: MAC address of a new user. $2: Outer VLAN to which the new user belongs. $3: Inner VLAN to which the new user belongs. $4: Name of the interface connecting to the new user. $5: MAC address of an old user. $6: Outer VLAN to which the old user belongs. $7: Inner VLAN to which the old user belongs. $8: Name of the interface connecting to the old user. $9: IP address.
Severity level	6
Example	ARP/6/ARP_USER_DUPLICATE_IPADDR_DETECT: Detected a user IP address conflict. New user (MAC 0010-2100-01e1, SVLAN 100, CVLAN 10) connecting on interface GigabitEthernet1/0/1 and old user (MAC 0120-1e00-0102, SVLAN 100, CVLAN 10) connecting on interface GigabitEthernet1/0/1 were using the same IP address 192.168.1.1.
Explanation	ARP detected a user IP address conflict. The IP address of a new user is the same as the IP address of an old user.
Recommended action	Verify that all users have different IP addresses.

ARP_USER_MOVE_DETECT

Message text	Detected a user (IP address [IPADDR], MAC address [STRING]) moved to another interface. Before user move: interface [STRING], SVLAN [STRING], CVLAN [STRING]. After user move: interface [STRING], SVLAN [STRING], CVLAN [STRING].
Variable fields	$1: IP address of the user. $2: MAC address of the user. $3: Interface name before the migration. $4: Outer VLAN to which the user belongs before the migration. $5: Inner VLAN to which the user belongs before the migration. $6: Interface name after the migration. $7: Outer VLAN to which the user belongs after the migration. $8: Inner VLAN to which the user belongs after the migration.
Severity level	6
Example	ARP/6/ARP_USER_MOVE_DETECT: Detected a user (IP address 192.168.1.1, MAC address 0010-2100-01e1) moved to another interface. Before user move: interface GigabitEthernet1/0/1, SVLAN 100, CVLAN 10. After user move: interface GigabitEthernet1/0/2, SVLAN 100, CVLAN 10.
Explanation	ARP detected a user accesses the network through another port.
Recommended action	Use the display arp user-move record command to verify that the migration is legitimate.

DUPIFIP

Message text	Duplicate address [STRING] on interface [STRING], sourced from [STRING].
Variable fields	$1: IP address. $2: Interface name. $3: MAC Address.
Severity level	6
Example	ARP/6/DUPIFIP: Duplicate address 1.1.1.1 on interface GigabitEthernet1/0/1, sourced from 0015-E944-A947.
Explanation	ARP detected a duplicate address. The sender IP in the received ARP packet was being used by the receiving interface.
Recommended action	Modify the IP address configuration.

DUPIP

Message text	IP address [STRING] conflicted with global or imported IP address, sourced from [STRING].
Variable fields	$1: IP address. $2: MAC Address.
Severity level	6
Example	ARP/6/DUPIP: IP address 30.1.1.1 conflicted with global or imported IP address, sourced from 0000-0000-0001.
Explanation	The sender IP address of the received ARP packet conflicted with the global or imported IP address.
Recommended action	Modify the IP address configuration.

DUPVRRPIP

Message text	IP address [STRING] conflicted with VRRP virtual IP address on interface [STRING], sourced from [STRING].
Variable fields	$1: IP address. $2: Interface name. $3: MAC address.
Severity level	6
Example	ARP/6/DUPVRRPIP: IP address 1.1.1.1 conflicted with VRRP virtual IP address on interface GigabitEthernet1/0/1, sourced from 0015-E944-A947.
Explanation	The sender IP address of the received ARP packet conflicted with the VRRP virtual IP address.
Recommended action	Modify the IP address configuration.

BFD messages

This section contains BFD messages.

BFD_CHANGE_FSM

Message text	Sess[STRING], Ver, Sta: [STRING]->[STRING], Diag: [UINT32]
Variable fields	$1: Source address, destination address, interface, message type, and MPLS FEC of the BFD session. For LSP sessions, this field contains the destination address, mask, and next hop address of LSPs. For PW sessions, this field contains the LSR ID of the peer PE and the PW ID. For TE tunnel sessions, this field contains the source address, destination address, tunnel ID, and LSP ID. $2: Name of FSM before changing. $3: Name of FSM after changing. $4: Diagnostic information: · 0 (No Diagnostic). · 1 (Control Detection Time Expired)—A control packet mode BFD session goes down, because local detection times out. · 2 (Echo Function Failed)—An echo packet mode BFD session goes down, because local detection times out or the source IP address of echo packets is deleted. · 3 (Neighbor Signaled Session Down)—The remote end notifies the local end of BFD session down. · 7 (Administratively Down)—The local system prevents a BFD session from being established.
Severity level	5
Example	BFD/5/BFD_CHANGE_FSM: Sess[20.0.4.2/20.0.4.1,LD/RD:533/532, Interface:Vlan204, SessType:Ctrl, LinkType:INET], Ver.1, Sta: INIT->UP, Diag: 0 (No Diagnostic). BFD/5/BFD_CHANGE_FSM: Sess[20.0.4.2/20.0.4.1,LD/RD:533/532, Interface: Vlan204, SessType: Ctrl, LinkType: LSP, FEC: LSP, 20.0.4.0/24/10.1.1.1], Ver.1, Sta: INIT->UP, Diag: 0 (No Diagnostic). BFD/5/BFD_CHANGE_FSM: Sess[20.0.4.2/20.0.4.1,LD/RD:533/532, Interface: Vlan204, SessType: Ctrl, LinkType: LSP, FEC: PW FEC-128, 20.0.4.2/1], Ver.1, Sta: INIT->UP, Diag: 0 (No Diagnostic). BFD/5/BFD_CHANGE_FSM: Sess[20.0.4.2/20.0.4.1,LD/RD:533/532, Interface: Vlan204, SessType: Ctrl, LinkType: LSP, FEC: TE Tunnel, 20.0.4.2/20.0.4.1/100/100], Ver.1, Sta: INIT->UP, Diag: 0 (No Diagnostic).
Explanation	The FSM of the BFD session has been changed. This informational message appears when a BFD session comes up or goes down. Unexpected session loss might indicate high error or packet loss rates in the network.
Recommended action	Check for incorrect BFD configuration or network congestion.

BFD_CHANGE_SESS

Message text	Sess[STRING], Ver, Sta: [STRING], Diag: [UINT32]
Variable fields	$1: Source address, destination address, interface, message type, and MPLS FEC of the BFD session. For LSP sessions, this field contains the destination address, mask, and next hop address of LSPs. For PW sessions, this field contains the LSR ID of the peer PE and the PW ID. For TE tunnel sessions, this field contains the source address, destination address, tunnel ID, and LSP ID. $2: Session state. $3: Diagnostic code.
Severity level	5
Example	BFD/5/BFD_CHANGE_SESS: Sess[17.1.1.2/17.1.1.1, LD/RD:1537/1537, Interface:GE1/0/1, SessType:Ctrl, LinkType:INET], Ver:1, Sta: Deleted, Diag: 7
Explanation	This informational message appears when a BFD session is deleted.
Recommended action	Check the BFD session configuration.

BFD_REACHED_UPPER_LIMIT

Message text	The total number of BFD sessions [ULONG] reached the upper limit. Can’t create a new session.
Variable fields	$1: Total number of BFD sessions.
Severity level	5
Example	BFD/5/BFD_REACHED_UPPER_LIMIT: The total number of BFD session 100 reached upper limit.
Explanation	The total number of BFD sessions has reached the upper limit.
Recommended action	Check the BFD session configuration.

BGP messages

This section contains BGP messages.

BGP_EXCEED_ROUTE_LIMIT

Message text	BGP [STRING].[STRING]: The number of routes from peer [STRING] ([STRING]) exceeds the limit [UINT32].
Variable fields	$1: BGP instance name. This field displays default for the public network. $2: VPN instance name. This field is blank for the public network. $3: IP address of the BGP peer. $4: Address family of the BGP peer. $5: Maximum number of routes.
Severity level	4
Example	BGP/4/BGP_EXCEED_ROUTE_LIMIT: BGP default.vpn1: The number of routes from peer 1.1.1.1 (IPv4-UNC) exceeds the limit 100.
Explanation	The number of routes received from a peer exceeded the maximum number of routes that can be received from the peer.
Recommended action	Determine whether it is caused by attacks: · If yes, configure the device to defend against the attacks. · If not, increase the maximum number of routes.

BGP_REACHED_THRESHOLD

Message text	BGP [STRING].[STRING]: The proportion of prefixes received from peer [STRING] ([STRING]) to maximum allowed prefixes reached the threshold value ([UINT32]%).
Variable fields	$1: BGP instance name. This field displays default for the public network. $2: VPN instance name. This field is blank for the public network. $3: IP address of the BGP peer. $4: Address family of the BGP peer. $5: Percentage of received routes to the maximum allowed routes.
Severity level	5
Example	BGP/5/BGP_REACHED_THRESHOLD: BGP default.vpn1: The proportion of prefixes received from peer 1.1.1.1 (IPv4-UNC) to maximum allowed prefixes reached the threshold value (60%).
Explanation	The percentage of received routes to the maximum allowed routes reached the threshold.
Recommended action	Determine whether it is caused by attacks: · If yes, configure the device to defend against the attacks. · If not, increase the threshold value or the maximum number of routes that can be received from the peer.

BGP_LOG_ROUTE_FLAP

Message text	BGP [STRING].[STRING]: The route [STRING] [STRING]/[UINT32] learned from peer [STRING] ([STRING]) flapped.
Variable fields	$1: BGP instance name. This field displays default for the public network. $2: VPN instance name. This field is blank for the public network. $3: RD of the BGP route. This field is blank for a route without an RD. $4: BGP route prefix. $5: Mask of the BGP route prefix. $6: IP address of the BGP peer. $7: Address family of the BGP peer.
Severity level	4
Example	BGP/4/BGP_LOG_ROUTE_FLAP: BGP default.vpn1: The route 15.1.1.1/24 learned from peer 1.1.1.1 (IPv4-UNC) flapped.
Explanation	The route learned from a BGP peer flapped.
Recommended action	If a large number of routes flap, determine the route flapping cause and develop a solution.

BGP_MEM_ALERT

Message text	BGP [STRING] instance received system memory alert [STRING] event.
Variable fields	$1: BGP instance name. This field displays default for the public network. $2: Type of the memory alarm, stop and start.
Severity level	5
Example	BGP/5/BGP_MEM_ALERT: BGP default instance received system memory alert start event.
Explanation	BGP received a memory alarm.
Recommended action	If BGP received a system memory alert start event, check the system memory and try to free some memory by adjusting modules that occupied too much memory.

BGP_PEER_LICENSE_REACHED

Message text	BGP [STRING]: Number of peers in Established state reached the license limit.
Variable fields	$1: BGP instance name. This field displays default for the public network.
Severity level	5
Example	BGP/5/BGP_PEER_LICENSE_REACHED: BGP default: Number of peers in Established state reached the license limit.
Explanation	The number of peers in Established state reached the license limit.
Recommended action	Determine whether a new license is required.

BGP_ROUTE_LICENSE_REACHED

Message text	BGP [STRING]: Number of [STRING] routes reached the license limit.
Variable fields	$1: BGP instance name. This field displays default for the public network. $2: BGP address family: · IPv4-UNC public—IPv4 unicast routes for the public network. · IPv6-UNC public—IPv6 unicast routes for the public network. · IPv4 private—IPv4 unicast routes, VPNv4 routes, and nested VPN routes for the private network. · IPv6 private—IPv6 unicast routes and VPNv6 routes for the private network.
Severity level	5
Example	BGP/5/BGP_ROUTE_LICENSE_REACHED: BGP default: Number of IPv4-UNC public routes reached the license limit.
Explanation	The number of routes in the specified address family reached the license limit.
Recommended action	Determine whether a new license is required. After the number of routes in the specified family falls below the license limit or the license limit increases, you must manually restore the discarded routes.

BGP_STATE_CHANGED

Message text	BGP [STRING].[STRING]: [STRING] state has changed from [STRING] to [STRING].
Variable fields	$1: BGP instance name. This field displays default for the public network. $2: VPN instance name. This field is blank for the public network. $3: IP address of the BGP peer. $4: Name of FSM before the state change. $5: Name of FSM after the state change.
Severity level	5
Example	BGP/5/BGP_STATE_CHANGED: BGP default.vpn1:192.99.0.2 state has changed from ESTABLISHED to IDLE.
Explanation	The FSM of a BGP peer has changed. This informational message appears when a BGP peer comes up or goes down.
Recommended action	If a peer goes down unexpectedly, determine whether an error or packet loss occurs.

CFD messages

This section contains CFD messages.

CFD_CROSS_CCM

Message text	MEP [UINT16] in SI [INT32] received a cross-connect CCM. It’s SrcMAC is [MAC], SeqNum is [INT32], RMEP is [UINT16], MD ID is [STRING], MA ID 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 ID. If no MD ID is available, "without ID" is displayed. $7: MA ID.
Severity level	6
Example	CFD/6/CFD_CROSS_CCM: MEP 13 in SI 10 received a cross-connect CCM. Its SrcMAC is 0011-2233-4401, SeqNum is 78, RMEP is 12, MD ID is without ID, MA ID is 0.
Explanation	A MEP received a cross-connect CCM containing a different MA ID or MD ID.
Recommended action	Check the configurations of MEPs on both ends. Make sure the MEPs have consistent configurations, including MD, MA, and level.

CFD_DRVRET_NOTSUCCESS

Message text	Driver returned an error. Reason: [STRING]. Please check configuration or specification.
Variable fields	$1: Failure cause: ¡ CFD is not supported. ¡ No enough resources. ¡ Other.
Severity level	6
Example	CFD/6/ CFD_ DRVRET_NOTSUCCESS: Driver returned an error. Reason: No enough resources. Please check configuration or specification.
Explanation	The driver returned an error.
Recommended action	Check the configuration or specification.

CFD_ERROR_CCM

Message text	MEP [UINT16] in SI [INT32] received an error CCM. It’s SrcMAC is [MAC], SeqNum is [INT32], RMEP is [UINT16], MD ID is [STRING], MA ID 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 ID. If no MD ID is available, "without ID" is displayed. $7: MA ID.
Severity level	6
Example	CFD/6/CFD_ERROR_CCM: MEP 2 in SI 7 received an error CCM. Its SrcMAC is 0011-2233-4401, SeqNum is 21, RMEP is 2, MD ID is 7, MA ID is 1.
Explanation	A MEP received an error CCM containing an unexpected MEP ID or lifetime.
Recommended action	Check the CCM configuration. Make sure the CCM intervals are consistent on both ends, and the remote MEP ID is included in the MEP list of the local end.

CFD_LOST_CCM

Message text	MEP [UINT16] in SI [INT32] failed to receive CCMs from RMEP [UINT16].
Variable fields	$1: Local MEP ID. $2: Service instance ID. $3: Remote MEP ID.
Severity level	6
Example	CFD/6/CFD_LOST_CCM: MEP 1 in SI 7 failed to receive CCMs from RMEP 2.
Explanation	A MEP failed to receive CCMs within 3.5 sending intervals because the link is faulty or the remote MEP does not send CCM within 3.5 sending intervals.
Recommended action	Check the link status and the configuration of the remote MEP. If the link is down or faulty (becomes unidirectional, for example), restore the link. If the remote MEP is configured with the same service instance, make sure the CCM sending intervals are consistent on both ends.

CFGMAN messages

This section contains configuration management messages.

CFGMAN_CFGCHANGED

Message text	-EventIndex=[INT32]-CommandSource=[INT32]-ConfigSource=[INT32]-ConfigDestination=[INT32]; Configuration changed.
Variable fields	$1: Event index in the range of 1 to 2147483647. $2: Configuration change source: ¡ cli—The configuration change came from the CLI. ¡ snmp—The configuration change came from the MIB. ¡ other—The configuration change came from other sources. $3: Source configuration: ¡ erase—Deleting or renaming a configuration file. ¡ running—Saving the running configuration. ¡ commandSource—Copying a configuration file. ¡ startup—Saving the running configuration to the next-startup configuration file. ¡ local—Saving the running configuration to a local file. ¡ networkFtp—Using FTP to transfer and save a configuration file to the device as the running configuration or next-startup configuration file. ¡ hotPlugging—A card hot swapping caused the configuration to be deleted or become ineffective. $4: Destination configuration: ¡ erase—Deleting or renaming a configuration file. ¡ running—Saving the running configuration. ¡ commandSource—Copying a configuration file. ¡ startup—Saving the running configuration to the next-startup configuration file. ¡ local—Saving the running configuration to a local file. ¡ networkFtp—Using FTP to transfer and save a configuration file to the device as the running configuration or next-startup configuration file. ¡ hotPlugging—A card hot swapping caused the configuration to be deleted or become ineffective.
Severity level	5
Example	CFGMAN/5/CFGMAN_CFGCHANGED: -EventIndex=[6]-CommandSource=[snmp]-ConfigSource=[startup]-ConfigDestination=[running]; Configuration changed.
Explanation	The running configuration changed in the past 10 minutes.
Recommended action	No action is required.

CFGMAN_OPTCOMPLETION

Message text	-OperateType=[INT32]-OperateTime=[INT32]-OperateState=[INT32]-OperateEndTime=[INT32]; Operation completed.
Variable fields	$1: Operation type: ¡ running2startup—Saves the running configuration to the next-startup configuration file. ¡ startup2running—Loads the configuration in the next-startup configuration file. ¡ running2net—Saves the running configuration to a host on the network. ¡ net2running—Transfers a configuration file from a host on the network and loads the configuration. ¡ net2startup—Transfers a configuration file from a host on the network and specifies the file as the next-startup configuration file. ¡ startup2net—Copies the next-startup configuration file to a host on the network. $2: Operation start time. $3: Operation status: ¡ InProcess—Operation is in progress. ¡ success—Operation succeeded. ¡ InvalidOperation—Invalid operation. ¡ InvalidProtocol—Invalid protocol. ¡ InvalidSource—Invalid source file name. ¡ InvalidDestination—Invalid destination file name. ¡ InvalidServer—Invalid server address. ¡ DeviceBusy—The device is busy. ¡ InvalidDevice—Invalid device address. ¡ DeviceError—An error occurred on the device. ¡ DeviceNotWritable—The storage medium on the device is write protected. ¡ DeviceFull—The device does not have enough free storage space for the file. ¡ FileOpenError—Failed to open the file. ¡ FileTransferError—Failed to transfer the file. ¡ ChecksumError—File checksum error. ¡ LowMemory—The memory space is not sufficient. ¡ AuthFailed—User authentication failed. ¡ TransferTimeout—Transfer timed out. ¡ UnknownError—An unknown error occurred. ¡ invalidConfig—Invalid configuration. $4: Operation end time.
Severity level	5
Example	CFGMAN/5/CFGMAN_OPTCOMPLETION: -OperateType=[running2startup]-OperateTime=[248]-OperateState=[success]-OperateEndTime=[959983]; Operation completed.
Explanation	The device is performing or has completed an operation.
Recommended action	If the operation is not successful, locate and resolve the issue.

CGROUP messages

This section contains interface collaboration messages.

CGROUP_STATUS_CHANGE

Message text	The status of collaboration group [UINT32] is [STRING].
Variable fields	$1: Collaboration group ID. $2: Collaboration group state: down or up.
Severity level	6
Example	CGROUP/6/CGROUP_STATUS_CHANGE: The status of collaboration group 1 is up.
Explanation	The status of collaboration group 1 is up or down.
Recommended action	Check the links.

DHCP

This section contains DHCP messages.

DHCP_NORESOURCES

Message text	Failed to apply filtering rules for DHCP packets because hardware resources are insufficient.
Variable fields	N/A
Severity level	3
Example	DHCP/3/DHCP_NORESOURCES: Failed to apply filtering rules for DHCP packets because hardware resources are insufficient.
Explanation	The system failed to apply filtering rules for DHCP packets because the hardware resources are insufficient.
Recommended action	Release hardware resources and then apply the rules again.

DHCP_NOTSUPPORTED

Message text	Failed to apply filtering rules for DHCP packets because some rules are not supported.
Variable fields	N/A
Severity level	3
Example	DHCP/3/DHCP_NOTSUPPORTED: Failed to apply filtering rules for DHCP packets because some rules are not supported.
Explanation	The system failed to apply filtering rules for DHCP packets because some rules are not supported on the device.
Recommended action	No action is required.

DHCPR

This section contains DHCP relay agent messages.

DHCPR_SERVERCHANGE

Message text	Switched to the server at [IPADDR] because the current server did not respond.
Variable fields	$1: IP address of the DHCP server.
Severity level	3
Example	DHCPR/3/DHCPR_SERVERCHANGE: -MDC=1; Switched to the server at 2.2.2.2 because the current server did not respond.
Explanation	The DHCP relay agent did not receive any responses from the current DHCP server and switched to another DHCP server for IP address acquisition.
Recommended action	No action is required.

DHCPR_SWITCHMASTER

Message text	Switched to the master DHCP server at [IPADDR].
Variable fields	$1: IP address of the master DHCP server.
Severity level	3
Example	DHCPR/3/DHCPR_SWITCHMASTER: -MDC=1; Switched to the master DHCP server at 2.2.2.2.
Explanation	After a switchback delay time, the DHCP relay agent switched from a backup DHCP server back to the master DHCP server for IP address acquisition.
Recommended action	No action is required.

DHCPS messages

This section contains DHCP server messages.

DHCPS_ALLOCATE_IP

Message text	DHCP server received a DHCP client's request packet on interface [STRING], and allocated an IP address [IPADDR](lease [UINT32] seconds) for the DHCP client(MAC [MAC]) from [STRING] pool.
Variable fields	$1: Name of the interface on which DHCP server is configured. $2: IPv4 address assigned to the DHCP client. $3: Lease duration of the assigned IPv4 address. $4: MAC address of the DHCP client. $5: Name of the address pool to which the assigned IPv4 address belongs.
Severity level	5
Example	DHCPS/5/DHCPS_ALLOCATE_IP: DHCP server received a DHCP client’s request packet on interface Ethernet0/2, and allocated an IP address 1.0.0.91(lease 86400 seconds) for the DHCP client(MAC 0000-0000-905a) from p1 pool.
Explanation	The DHCP server assigned an IPv4 address with a lease to a DHCP client.
Recommended action	No action is required.

DHCPS_CONFLICT_IP

Message text	A conflict IP [IPADDR] from [STRING] pool was detected by DHCP server on interface [STRING].
Variable fields	$1: IPv4 address that is in conflict. $2: Name of the address pool to which the conflicting IPv4 address belongs. $3: Name of the interface on which DHCP server is configured.
Severity level	5
Example	DHCPS/5/DHCPS_CONFLICT_IP: A conflict IP 100.1.1.1 from p1 pool was detected by DHCP server on interface Ethernet0/2.
Explanation	The DHCP server deleted a conflicting IPv4 address from an address pool.
Recommended action	No action is required.

DHCPS_EXTEND_FAILURE

Message text	Extend request from DHCP client (IP [IPADDR], MAC [MAC]) failed, reply NAK message.
Variable fields	$1: IP address of the DHCP client. $2: MAC address of the DHCP client.
Severity level	5
Example	DHCPS/5/DHCPS_EXTEND_FAILURE: Extend request from DHCP client (IP 1.0.0.91, MAC 0000-0000-905a) failed, reply NAK message.
Explanation	The DHCP server failed to extend the lease for a DHCP client and replied a DHCP-NAK message.
Recommended action	No action is required.

DHCPS_EXTEND_IP

Message text	DHCP server received a DHCP client's request packet on interface [STRING], and extended lease from [STRING] pool for the DHCP client (IP [IPADDR], MAC [MAC]).
Variable fields	$1: Name of the interface on which DHCP server is configured. $2: Name of the address pool to which the client's IPv4 address belongs. $3: IPv4 address of the DHCP client. $4: MAC address of the DHCP client.
Severity level	5
Example	DHCPS/5/DHCPS_EXTEND_IP: DHCP server received a DHCP client’s request packet on interface Ethernet0/2, and extended lease from p1 pool for the DHCP client (IP 1.0.0.91, MAC 0000-0000-905a).
Explanation	The DHCP server extended the lease for a DHCP client.
Recommended action	No action is required.

DHCPS_FILE

Message text	Failed to save DHCP client information due to lack of storage resources.
Variable fields	N/A
Severity level	4
Example	DHCPS/4/DHCPS_FILE: Failed to save DHCP client information due to lack of storage resources.
Explanation	The DHCP server failed to back up DHCP bindings to the backup file due to lack of storage resources.
Recommended action	Delete unnecessary files to release resources.

DHCPS_RECLAIM_IP

Message text	DHCP server reclaimed a [STRING] pool’s lease(IP [IPADDR], lease [UINT32] seconds), which is allocated for the DHCP client (MAC [MAC]).
Variable fields	$1: Name of the address pool to which the assigned IPv4 address belongs. $2: IPv4 address assigned to the DHCP client. $3: Lease duration of the assigned IPv4 address. $4: MAC address of the DHCP client.
Severity level	5
Example	DHCPS/5/DHCPS_RECLAIM_IP: DHCP server reclaimed a p1 pool’s lease(IP 1.0.0.91, lease 86400 seconds), which is allocated for the DHCP client (MAC 0000-0000-905a).
Explanation	The DHCP server reclaimed the IPv4 address assigned to a DHCP client.
Recommended action	No action is required.

DHCPS_UNAVAILABLE_POOL

Message text	Available address pool [STRING] cannot be found.
Variable fields	$1: Address pool name. This field is displayed if the address pool is an authorized pool or a DHCP policy-assigned pool.
Severity level	5
Example	DHCPS/5/DHCPS_UNAVAILABLE_POOL: Available address pool 1 cannot be found.
Explanation	The DHCP server cannot find an available address pool.
Recommended action	Configure an address pool available for address assignment.

DHCPS_VERIFY_CLASS

Message text	Illegal DHCP client-PacketType=[STRING]-ClientAddress=[MAC];
Variable fields	$1: Type of the packet. $2: Hardware address of the DHCP client.
Severity level	5
Example	DHCPS/5/DHCPS_VERIFY_CLASS: Illegal DHCP client-PacketType= DHCPDISCOVER-ClientAddress=0000-5e01-0104;
Explanation	The DHCP server verified that the DHCP client was not on the user class whitelist.
Recommended action	Check the validity of the DHCP client.

DHCPS6 messages

This section contains DHCPv6 server messages.

DHCPS6_ALLOCATE_ADDRESS

Message text	DHCPv6 server received a DHCPv6 client’s request packet on interface [STRING], and allocated an IPv6 address [IPADDR] (lease [UINT32] seconds) for the DHCP client(DUID [HEX], IAID [HEX]) from [STRING] pool.
Variable fields	$1: Name of the interface on which DHCPv6 server is configured. $2: IPv6 address assigned to the DHCPv6 client. $3: Lease duration of the assigned IPv6 address. $4: DUID of the DHCPv6 client. $5: IAID of the DHCPv6 client. $6: Name of the address pool to which the assigned IPv6 address belongs.
Severity level	5
Example	DHCPS6/5/DHCPS6_ALLOCATE_ADDRESS: DHCPv6 server received a DHCPv6 client’s request packet on interface Ethernet0/2, and allocated an IPv6 address 2000::3(lease 60 seconds) for the DHCP client(DUID 0001000118137c37b4b52facab5a, IAID 10b4b52f) from p1 pool.
Explanation	The DHCPv6 server assigned an IPv6 address with a lease to a DHCPv6 client.
Recommended action	No action is required.

DHCPS6_ALLOCATE_PREFIX

Message text	DHCPv6 server received a DHCPv6 client’s request packet on interface [STRING], and allocated an IPv6 prefix [IPADDR] (lease [UINT32] seconds) for the DHCP client(DUID [HEX], IAID [HEX]) from [STRING] pool.
Variable fields	$1: Name of the interface on which DHCPv6 server is configured. $2: IPv6 prefix assigned to the DHCPv6 client. $3: Lease duration of the assigned IPv6 prefix. $4: DUID of the DHCPv6 client. $5: IAID of the DHCPv6 client. $6: Name of the address pool to which the assigned IPv6 prefix belongs.
Severity level	5
Example	DHCPS6/5/DHCPS6_ALLOCATE_PREFIX: DHCPv6 server received a DHCPv6 client’s request packet on interface Ethernet0/2, and allocated an IPv6 prefix 2000::(lease 60 seconds) for the DHCP client(DUID 0001000118137c37b4b52facab5a, IAID 10b4b52f) from p1 pool.
Explanation	The DHCPv6 server assigned an IPv6 prefix with a lease to a DHCPv6 client.
Recommended action	No action is required.

DHCPS6_CONFLICT_ADDRESS

Message text	A conflict IPv6 address [IPADDR] from [STRING] pool was detected by DHCPv6 server on interface [STRING].
Variable fields	$1: IPv6 address that is in conflict. $2: Name of the address pool to which the conflicting IPv6 address belongs. $3: Name of the interface on which DHCPv6 server is configured.
Severity level	5
Example	DHCPS6/5/DHCPS6_CONFLICT_ADDRESS: A conflict IPv6 address 33::1 from p1 pool was detected by DHCPv6 server on interface Ethernet0/2.
Explanation	The DHCPv6 server deleted a conflicting IPv6 address from an address pool.
Recommended action	No action is required.

DHCPS6_EXTEND_ADDRESS

Message text	DHCPv6 server received a DHCP client’s request packet on interface [STRING], and extended lease from [STRING] pool for the DHCP client (IPv6 address [IPADDR], DUID [HEX], IAID [HEX]).
Variable fields	$1: Name of the interface on which DHCPv6 server is configured. $2: Name of the address pool to which the client's IPv6 address belongs. $3: IPv6 address of the DHCPv6 client. $4: DUID of the DHCPv6 client. $5: IAID of the DHCPv6 client.
Severity level	5
Example	DHCPS6/5/DHCPS6_EXTEND_ADDRESS: DHCPv6 server received a DHCP client’s request packet on interface Ethernet0/2, and extended lease from p1 pool for the DHCP client (IPv6 address 2000::3, DUID 0001000118137c37b4b52facab5a, IAID 10b4b52f).
Explanation	The DHCPv6 server extended the address lease for a DHCPv6 client.
Recommended action	No action is required.

DHCPS6_EXTEND_ADDRESS_FAILURE

Message text	Extend request for address from DHCPv6 client (IPv6 address [IPADDR], DUID [HEX], IAID [HEX]) failed.
Variable fields	$1: IPv6 address of the DHCPv6 client. $2: DUID of the DHCPv6 client. $3: IAID of the DHCPv6 client.
Severity level	5
Example	DHCPS6/5/DHCPS6_EXTEND_ADDRESS_FAILURE: Extend request for address from DHCPv6 client (IPv6 address 2000::3, DUID 0001000118137c37b4b52facab5a, IAID 10b4b52f) failed.
Explanation	The DHCPv6 server failed to extend the address lease for a DHCPv6 client.
Recommended action	No action is required.

DHCPS6_EXTEND_PREFIX

Message text	DHCPv6 server received a DHCP client’s request packet on interface [STRING], and extended lease from [STRING] pool for the DHCP client (IPv6 prefix [IPADDR], DUID [HEX], IAID [HEX]).
Variable fields	$1: Name of the interface on which DHCPv6 server is configured. $2: Name of the address pool to which the client's IPv6 prefix belongs. $3: IPv6 prefix of the DHCPv6 client. $4: DUID of the DHCPv6 client. $5: IAID of the DHCPv6 client.
Severity level	5
Example	DHCPS6/5/DHCPS6_EXTEND_PREFIX: DHCPv6 server received a DHCP client’s request packet on interface Ethernet0/2, and extended lease from p1 pool for the DHCP client (IPv6 prefix 2000::, DUID 0001000118137c37b4b52facab5a, IAID 10b4b52f).
Explanation	The DHCPv6 server extended the prefix lease for a DHCPv6 client.
Recommended action	No action is required.

DHCPS6_EXTEND_PREFIX_FAILURE

Message text	Extend request for prefix from DHCPv6 client (IPv6 prefix [IPADDR], DUID [HEX], IAID [HEX]) failed.
Variable fields	$1: IPv6 prefix of the DHCPv6 client. $2: DUID of the DHCPv6 client. $3: IAID of the DHCPv6 client.
Severity level	5
Example	DHCPS6/5/DHCPS6_EXTEND_PREFIX_FAILURE: Extend request for prefix from DHCPv6 client (IPv6 prefix 2000::, DUID 0001000118137c37b4b52facab5a, IAID 10b4b52f) failed.
Explanation	The DHCPv6 server failed to extend the prefix lease for a DHCPv6 client.
Recommended action	No action is required.

DHCPS6_FILE

Message text	Failed to save DHCP client information due to lack of storage resources.
Variable fields	N/A
Severity level	4
Example	DHCPS6/4/DHCPS6_FILE: Failed to save DHCP client information due to lack of storage resources.
Explanation	The DHCPv6 server failed to back up DHCPv6 bindings to the backup file due to lack of storage resources.
Recommended action	Delete unnecessary files to release resources.

DHCPS6_RECLAIM_ADDRESS

Message text	DHCPv6 server reclaimed a [STRING] pool's lease(IPv6 address [IPADDR], lease [UINT32] seconds), which is allocated for the DHCPv6 client (DUID [HEX], IAID [HEX]).
Variable fields	$1: Name of the address pool to which the assigned IPv6 address belongs. $2: IPv6 address assigned to the DHCPv6 client. $3: Lease duration of the assigned IPv6 address. $4: DUID of the DHCPv6 client. $5: IAID of the DHCPv6 client.
Severity level	5
Example	DHCPS6/5/DHCPS6_RECLAIM_ADDRESS: DHCPv6 server reclaimed a p1 pool’s lease(IPv6 address 2000::3, lease 60 seconds), which is allocated for the DHCPv6 client (DUID 0001000118137c37b4b52facab5a, IAID 10b4b52f).
Explanation	The DHCPv6 server reclaimed the IPv6 address assigned to a DHCPv6 client.
Recommended action	No action is required.

DHCPS6_RECLAIM_PREFIX

Message text	DHCPv6 server reclaimed a [STRING] pool’s lease(IPv6 prefix [IPADDR], lease [INTEGER] seconds), which is allocated for the DHCPv6 client (DUID [HEX], IAID [HEX]).
Variable fields	$1: Name of the address pool to which the assigned IPv6 prefix belongs. $2: IPv6 prefix assigned to the DHCPv6 client. $3: Lease duration of the assigned IPv6 prefix. $4: DUID of the DHCPv6 client. $5: IAID of the DHCPv6 client.
Severity level	5
Example	DHCPS6/5/DHCPS6_RECLAIM_PREFIX: DHCPv6 server reclaimed a p1 pool’s lease(IPv6 prefix 2000::, lease 60 seconds), which is allocated for the DHCPv6 client (DUID 0001000118137c37b4b52facab5a, IAID 10b4b52f).
Explanation	The DHCPv6 server reclaimed the IPv6 prefix assigned to a DHCPv6 client.
Recommended action	No action is required.

DHCPS6_UNAVAILABLE_POOL

Message text	Available [STRING] pool [STRING] cannot be found.
Variable fields	$1: Address pool or prefix pool. $2: Name of the address pool or prefix pool. This field is displayed in one of the following conditions: ¡ The address pool is an authorized pool or a DHCP policy-assigned pool. ¡ The prefix pool is specified in an address pool.
Severity level	5
Example	DHCPS6/5/DHCPS6_UNAVAILABLE_POOL: Available address pool 1 cannot be found.
Explanation	The DHCPv6 server cannot find an available IPv6 address or prefix pool.
Recommended action	Configure an IPv6 address pool or prefix pool available for address assignment.

DHCPSP4

This section contains DHCP snooping messages.

DHCPSP4_FILE

Message text	Failed to save DHCP client information due to lack of storage resources.
Variable fields	N/A
Severity level	4
Example	DHCPSP4/4/DHCPSP4_FILE: Failed to save DHCP client information due to lack of storage resources.
Explanation	The DHCP snooping device failed to back up DHCP snooping entries to the backup file due to lack of storage resources.
Recommended action	Delete unnecessary files to release resources.

DHCPSP6

This section contains DHCPv6 snooping messages.

DHCPSP6_FILE

Message text	Failed to save DHCP client information due to lack of storage resources.
Variable fields	N/A
Severity level	4
Example	DHCPSP6/4/DHCPSP6_FILE: Failed to save DHCP client information due to lack of storage resources.
Explanation	The DHCPv6 snooping device failed to back up DHCPv6 snooping entries to the backup file due to lack of storage resources.
Recommended action	Delete unnecessary files to release resources.

DIAG messages

This section contains diagnostic messages.

CPU_MINOR_RECOVERY

Message text	CPU usage recovered to normal state.
Variable fields	N/A
Severity level	5
Example	DIAG/5/CPU_MINOR_THRESHOLD: CPU usage recovered to normal state.
Explanation	The CPU usage decreased below the recovery threshold. The minor alarm was removed and the CPU usage status changed from minor alarm state to recovered state.
Recommended action	No action is required.

CPU_MINOR_THRESHOLD

Message text	CPU usage is in minor alarm state.
Variable fields	N/A
Severity level	4
Example	DIAG/4/CPU_MINOR_THRESHOLD: CPU usage is in minor alarm state.
Explanation	The CPU usage increased above the minor alarm threshold and entered minor alarm state. The device sends this message periodically until the CPU usage increases above the severe threshold or the minor alarm is removed.
Recommended action	Operate according to prompt information and use CPU resource reasonably.

CPU_SEVERE_RECOVERY

Message text	CPU usage severe alarm removed.
Variable fields	N/A
Severity level	5
Example	DIAG/5/CPU_RECOVERY: CPU usage severe alarm removed.
Explanation	The CPU usage decreased to or below the minor alarm threshold and the severe alarm was removed.
Recommended action	No action is required.

CPU_SEVERE_THRESHOLD

Message text	CPU usage severe alarm removed.
Variable fields	N/A
Severity level	3
Example	DIAG/3/CPU_THRESHOLD: CPU usage is in severe alarm state.
Explanation	The CPU usage increased above the severe alarm threshold and entered severe alarm state. The device sends this message periodically until the severe alarm is removed.
Recommended action	Use the display current-configuration \| include "monitor cpu-usage" command to view the alarm thresholds. Use the monitor cpu-usage command to adjust the alarm thresholds as required.

MEM_ALERT

Message text	system memory info: total used free shared buffers cached Mem: [ULONG] [ULONG] [ULONG] [ULONG] [ULONG] [ULONG] -/+ buffers/cache: [ULONG] [ULONG] Swap: [ULONG] [ULONG] [ULONG] Lowmem: [ULONG] [ULONG] [ULONG]
Variable fields	· Mem—Memory information of the whole system: ¡ $1: Total size of allocatable physical memory. The system physical memory contains allocatable physical memory and unallocatable physical memory. Unallocatable physical memory is mainly used for kernel code storage, kernel management, and running of basic functions. Allocatable physical memory is used for such tasks as running service modules and storing files. The size of unallocatable physical memory is automatically calculated based on the system operation requirements. The size of allocatable physical memory is the total physical memory size minus the unallocatable physical memory size. ¡ $2: Size of the physical memory used by the system. ¡ $3: Size of free physical memory of the system. ¡ $4: Total size of physical memory shared by processes. ¡ $5: Size of physical memory used for buffers. ¡ $6: Size of physical memory used for caches. · -/+ buffers/cache—Memory usage information of applications: ¡ $7: -/+ Buffers/Cache:used = Mem:Used – Mem:Buffers – Mem:Cached, which indicates the size of physical memory used by applications. ¡ $8: -/+ Buffers/Cache:free = Mem:Free + Mem:Buffers + Mem:Cached, which indicates the size of physical memory available for applications. · Swap—Swap memory usage information: ¡ $9: Total size of swap memory. ¡ $10: Size of used swap memory. ¡ $11: Size of free swap memory. · Lowmem—Low memory usage information: ¡ $12: Total size of low memory. ¡ $13: Size of used low memory. ¡ $14: Size of free low memory.
Severity level	4
Example	DIAG/4/MEM_ALERT: system memory info: total used free shared buffers cached Mem: 1784424 920896 863528 0 0 35400 -/+ buffers/cache: 885496 898928 Swap: 0 0 0 Lowmem: 735848 637896 97952
Explanation	A memory alarm was generated, displaying memory usage information. The system generates this message when the used memory is greater than or equal to the minor, severe, or critical threshold of memory usage.
Recommended action	You can perform the following tasks to help remove the alarm: · Verify that appropriate alarm thresholds are set. To view the alarm thresholds, use the display memory-threshold command. Then you can use the memory-threshold command to modify the alarm thresholds if required. · Verify that the device is not under attack by checking the ARP table and routing table. · Examine and optimize the network, for example, reduce the number of routes, or replace the device with a higher-performance device.

MEM_BELOW_THRESHOLD

Message text	Memory usage has dropped below [STRING] threshold.
Variable fields	$1: Memory usage threshold name: minor, severe, or critical.
Severity level	1
Example	DIAG/1/MEM_BELOW_THRESHOLD: Memory usage has dropped below critical threshold.
Explanation	A memory alarm was removed. The message is sent when the system free memory is greater than a memory alarm recovery threshold.
Recommended action	No action is required.

MEM_EXCEED_THRESHOLD

Message text	Memory [STRING] threshold has been exceeded.
Variable fields	$1: Memory usage threshold name: minor, severe, or critical.
Severity level	1
Example	DIAG/1/MEM_EXCEED_THRESHOLD: Memory minor threshold has been exceeded.
Explanation	A memory alarm was notified. When the used memory size is greater than or equal to the minor, severe, or critical threshold of memory usage, the system generates this message and notifies services modules to perform auto repair, such as releasing memory and stopping requesting memory.
Recommended action	You can perform the following tasks to help remove the alarm: · Verify that appropriate alarm thresholds are set. To view the alarm thresholds, use the display memory-threshold command. Then you can use the memory-threshold command to modify the alarm thresholds if required. · Verify that the device is not under attack by checking the ARP table and routing table. · Examine and optimize the network, for example, reduce the number of routes or replace the device with a higher-performance device.

DLDP messages

This section contains DLDP messages.

DLDP_AUTHENTICATION_FAILED

Message text	The DLDP packet failed the authentication because of unmatched [STRING] field.
Variable fields	$1: Authentication field. · AUTHENTICATION PASSWORD—Authentication password mismatch. · AUTHENTICATION TYPE—Authentication type mismatch. · INTERVAL—Advertisement interval mismatch.
Severity level	5
Example	DLDP/5/DLDP_AUTHENTICATION_FAILED: The DLDP packet failed the authentication because of unmatched INTERVAL field.
Explanation	The packet authentication failed. Possible reasons include unmatched authentication type, unmatched authentication password, and unmatched advertisement interval.
Recommended action	Check the DLDP authentication type, authentication password, and advertisement interval are consistent with peer end.

DLDP_LINK_BIDIRECTIONAL

Message text	DLDP detected a bidirectional link on interface [STRING].
Variable fields	$1: Interface name.
Severity level	6
Example	DLDP/6/DLDP_LINK_BIDIRECTIONAL: DLDP detected a bidirectional link on interface Ethernet1/1.
Explanation	DLDP detected a bidirectional link on an interface.
Recommended action	No action is required.

DLDP_LINK_SHUTMODECHG

Message text	DLDP automatically [STRING] interface [STRING] because the port shutdown mode was changed [STRING].
Variable fields	$1: Action according to the port shutdown mode: ¡ blocked. ¡ brought up. $2: Interface name. $3: Shutdown mode change: ¡ from manual to auto. ¡ from manual to hybrid. ¡ from hybrid to auto. ¡ from hybrid to manual.
Severity level	5
Example	DLDP/5/DLDP_LINK_SHUTMODECHG: DLDP automatically blocked interface Ethernet1/1 because the port shutdown mode was changed from manual to auto.
Explanation	The interface was shut down or brought up because the shutdown mode changed.
Recommended action	No action is required.

DLDP_LINK_UNIDIRECTIONAL

Message text	DLDP detected a unidirectional link on interface [STRING]. [STRING].
Variable fields	$1: Interface name. $2: Action according to the port shutdown mode: · DLDP automatically blocked the interface. · Please manually shut down the interface. · DLDP automatically shut down the interface. Please manually bring up the interface.
Severity level	3
Example	DLDP/3/DLDP_LINK_UNIDIRECTIONAL: DLDP detected a unidirectional link on interface Ethernet1/1. DLDP automatically blocked the interface.
Explanation	DLDP detected a unidirectional link on an interface.
Recommended action	Check for incorrect cable connection, cable falloff, or other problems.

DLDP_NEIGHBOR_AGED

Message text	A neighbor on interface [STRING] was deleted because the neighbor was aged. The neighbor's system MAC is [MAC], and the port index is [UINT16].
Variable fields	$1: Interface name. $2: MAC address. $3: Port index.
Severity level	5
Example	DLDP/5/DLDP_NEIGHBOR_AGED: A neighbor on interface Ethernet1/1 was deleted because the neighbor was aged. The neighbor's system MAC is 000f-e269-5f21, and the port index is 1.
Explanation	The interface deleted an aged neighbor.
Recommended action	No action is required.

DLDP_NEIGHBOR_CONFIRMED

Message text	A neighbor was confirmed on interface [STRING]. The neighbor's system MAC is [MAC], and the port index is [UINT16].
Variable fields	$1: Interface name. $2: MAC address. $3: Port index.
Severity level	6
Example	DLDP/6/DLDP_NEIGHBOR_CONFIRMED: A neighbor was confirmed on interface Ethernet1/1. The neighbor's system MAC is 000f-e269-5f21, and the port index is 1.
Explanation	The interface detected a confirmed neighbor.
Recommended action	No action is required.

DLDP_NEIGHBOR_DELETED

Message text	A neighbor on interface [STRING] was deleted because a [STRING] packet arrived. The neighbor's system MAC is [MAC], and the port index is [UINT16].
Variable fields	$1: Interface name. $2: Packet type, DISABLE or LINKDOWN. $3: MAC address. $4: Port index.
Severity level	5
Example	DLDP/5/DLDP_NEIGHBOR_DELETED: A neighbor on interface Ethernet1/1 was deleted because a DISABLE packet arrived. The neighbor's system MAC is 000f-e269-5f21, and the port index is 1.
Explanation	The interface deleted a confirmed neighbor because it received a DISABLE or LINKDOWN packet.
Recommended action	No action is required.

DRNI

This section contains DRNI messages.

DRNI_GLBCONSISTENCYCHECK_SUCCESS

Message text	Global type [UINT16] configuration consistency check succeeded.
Variable fields	$1: Configuration consistency check type.
Severity level	6
Example	DRNI/6/DRNI_GLBCONSISTENCYCHECK_SUCCESS: Global type 1 configuration consistency check succeeded.
Explanation	No inconsistency was detected in global type 1 or type 2 configuration.
Recommended action	No action is required.

DRNI_GLBCONSISTENCYCHECK_FAILURE

Message text	Global type [UINT16] configuration consistency check failed.
Variable fields	$1: Configuration consistency check type.
Severity level	6
Example	DRNI/6/DRNI_GLBCONSISTENCYCHECK_FAILURE: Global type 1 configuration consistency check failed.
Explanation	Inconsistencies were detected in global type 1 or type 2 configuration.
Recommended action	If configuration inconsistencies exist, use the display drni consistency command to identify the inconsistent settings and modify them to be the same between the DR member devices.

DRNI_IFCONSISTENCYCHECK_SUCCESS

Message text	DR interface [STRING] type [UINT16] configuration consistency check succeeded.
Variable fields	$1: Layer 2 aggregate interface name. $2: Configuration consistency check type.
Severity level	6
Example	DRNI/6/DRNI_IFCONSISTENCYCHECK_SUCCESS: DR interface Bridge-Aggregation 2 type 1 configuration consistency check succeeded.
Explanation	No inconsistency was detected in type 1 or type 2 configuration of a DR interface.
Recommended action	No action is required.

DRNI_IFCONSISTENCYCHECK_FAILURE

Message text	DR interface [STRING] type [UINT16] configuration consistency check failed.
Variable fields	$1: Layer 2 aggregate interface name. $2: Configuration consistency check type.
Severity level	6
Example	DRNI/6/DRNI_IFCONSISTENCYCHECK_FAILURE: DR interface Bridge-Aggregation 2 type 1 configuration consistency check failed.
Explanation	Inconsistencies were detected in type 1 or type 2 configuration of a DR interface.
Recommended action	If configuration inconsistencies exist, use the display drni consistency command to identify the inconsistent settings and modify them to be the same between the DR member devices.

DRNI_IFEVENT_DR_BIND

Message text	Interface [STRING] was assigned to DR group [UINT32].
Variable fields	$1: Layer 2 aggregate interface name. $2: DR group number.
Severity level	6
Example	DRNI/6/DRNI_IFEVENT_DR_BIND: Interface Bridge-Aggregation1 was assigned to DR group 1.
Explanation	A Layer 2 aggregate interface was assigned to a DR group.
Recommended action	No action is required.

DRNI_IFEVENT_DR_GLOBALDOWN

Message text	The state of DR interface [STRING] changed to globally down.
Variable fields	$1: Layer 2 aggregate interface name.
Severity level	6
Example	DRNI/6/DRNI_IFEVENT_DR_GLOBALDOWN: The state of DR interface Bridge-Aggregation1 changed to globally down.
Explanation	One DR interface changed to the globally down state because all its member interfaces and all the member interfaces of the other DR interface in the same DR group became Unselected.
Recommended action	Verify that the device and the DR peer use the same system priority and system MAC address, and different system numbers.

DRNI_IFEVENT_DR_GLOBALUP

Message text	The state of DR interface [STRING] changed to globally up.
Variable fields	$1: Layer 2 aggregate interface name.
Severity level	6
Example	DRNI/6/DRNI_IFEVENT_DR_GLOBALUP: The state of DR interface Bridge-Aggregation1 changed to globally up.
Explanation	A DR interface changed to the globally up state. If member interfaces of DR interfaces in a DR group become Selected for the first time, the DR interfaces become globally up.
Recommended action	No action is required.

DRNI_IFEVENT_DR_NOSELECTED

Message text	Local DR interface [STRING] does not have Selected member ports.
Variable fields	$1: Layer 2 aggregate interface name.
Severity level	6
Example	DRNI/6/DRNI_IFEVENT_DR_NOSELECTED: Local DR interface Bridge-Aggregation1 does not have Selected member ports.
Explanation	The local DR interface does not have member ports in Selected state.
Recommended action	Verify that the member ports of the DR interface are correctly configured and connected.

DRNI_IFEVENT_DR_PEER_NOSELECTED

Message text	Peer DR interface [STRING] does not have Selected member ports.
Variable fields	$1: Layer 2 aggregate interface name.
Severity level	6
Example	DRNI/6/DRNI_IFEVENT_DR_PEER_NOSELECTED: Peer DR interface Bridge-Aggregation1 does not have Selected member ports.
Explanation	The peer DR interface does not have member ports in Selected state.
Recommended action	Verify that the member ports of the DR interface are correctly configured and connected.

DRNI_IFEVENT_DR_PEER_SELECTED

Message text	Peer DR interface [STRING] has Selected member ports.
Variable fields	$1: Layer 2 aggregate interface name.
Severity level	6
Example	DRNI/6/DRNI_IFEVENT_DR_PEER_SELECTED: Peer DR interface Bridge-Aggregation1 has Selected member ports.
Explanation	The peer DR interface has member ports in Selected state.
Recommended action	No action is required.

DRNI_IFEVENT_DR_SELECTED

Message text	Local DR interface [STRING] has Selected member ports.
Variable fields	$1: Layer 2 aggregate interface name.
Severity level	6
Example	DRNI/6/DRNI_IFEVENT_DR_SELECTED: Local DR interface Bridge-Aggregation1 has Selected member ports.
Explanation	The local DR interface has member ports in Selected state.
Recommended action	No action is required.

DRNI_IFEVENT_DR_UNBIND

Message text	Interface [STRING] was removed from DR group [UINT32].
Variable fields	$1: Layer 2 aggregate interface name. $2: DR group number.
Severity level	6
Example	DRNI/6/DRNI_IFEVENT_DR_UNBIND: Interface Bridge-Aggregation1 was removed from DR group 1.
Explanation	A Layer 2 aggregate interface was removed from a DR group.
Recommended action	No action is required.

DRNI_IFEVENT_IPP_BIND

Message text	Interface [STRING] was configured as IPP [UINT16].
Variable fields	$1: Layer 2 aggregate interface name. $2: IPP number.
Severity level	6
Example	DRNI/6/DRNI_IFEVENT_IPP_BIND: Interface Bridge-Aggregation1 was configured as IPP 1.
Explanation	A Layer 2 aggregate interface was configured as the IPP.
Recommended action	No action is required.

DRNI_IFEVENT_IPP_DOWN

Message text	IPP [STRING] went down.
Variable fields	$1: Layer 2 aggregate interface name.
Severity level	6
Example	DRNI/6/DRNI_IFEVENT_IPP_DOWN: IPP Bridge-Aggregation1 went down.
Explanation	The IPP went down because the DRCP timeout timer expired.
Recommended action	· Verify that the device and the DR peer use the same system priority and system MAC address, and different system numbers. · Verify that the Layer 2 aggregate interface that acts as the IPP is working correctly.

DRNI_IFEVENT_IPP_UNBIND

Message text	Configuration for IPP [UINT16] was removed from interface [STRING].
Variable fields	$1: IPP number. $2: Layer 2 aggregate interface name.
Severity level	6
Example	DRNI/6/DRNI_IFEVENT_IPP_UNBIND: Configuration for IPP 1 was removed from interface Bridge-Aggregation1.
Explanation	The IPP configuration was removed.
Recommended action	No action is required.

DRNI_IFEVENT_IPP_UP

Message text	IPP [STRING] came up.
Variable fields	$1: Layer 2 aggregate interface name.
Severity level	6
Example	DRNI/6/DRNI_IFEVENT_IPP_UP: IPP Bridge-Aggregation1 came up.
Explanation	The IPP came up because it could receive and send DRCPDUs.
Recommended action	No action is required.

DRNI_IPP_BLOCK

Message text	The status of IPP [STRING] changed to blocked.
Variable fields	$1: Layer 2 aggregate interface name.
Severity level	6
Example	DRNI/6/DRNI_IPP_BLOCK: The status of IPP Bridge-Aggregation20 changed to blocked.
Explanation	The status of the IPP changed to blocked because the device had been assigned a DR role, and the IPP went down.
Recommended action	· Verify that the IPL is correctly connected and the cable is working correctly. · Verify that the device and the DR peer have correct DR settings.

DRNI_IPP_UNBLOCK

Message text	The status of IPP [STRING] changed to unblocked.
Variable fields	$1: Layer 2 aggregate interface name.
Severity level	6
Example	DRNI/6/DRNI_IPP_UNBLOCK: The status of IPP Bridge-Aggregation20 changed to unblocked.
Explanation	The status of the IPP changed to unblocked because the device had been assigned a DR role, and the IPP came up.
Recommended action	No action is required.

DRNI_KEEPALIVEINTERVAL_MISMATCH

Message text	Keepalive interval on the local DR device was different than on the neighbor.
Variable fields	N/A
Severity level	6
Example	DRNI/6/DRNI_KEEPALIVEINTERVAL_MISMATCH: Keepalive interval on the local DR device was different than on the neighbor.
Explanation	The device and the DR peer use different keepalive intervals.
Recommended action	Make sure the device and the DR peer use the same keepalive interval.

DRNI_KEEPALIVELINK_DOWN

Message text	Keepalive link went down.
Variable fields	N/A
Severity level	6
Example	DRNI/6/DRNI_KEEPALIVELINK_DOWN: Keepalive link went down.
Explanation	The keepalive link went down.
Recommended action	· Verify Layer 3 connectivity for the keepalive link. · Verify that the device and the DR peer use consistent packet source and destination IP addresses for keepalive detection.

DRNI_KEEPALIVELINK_UP

Message text	Keepalive link came up.
Variable fields	N/A
Severity level	6
Example	DRNI/6/DRNI_KEEPALIVELINK_UP: Keepalive link came up.
Explanation	The keepalive link came up.
Recommended action	No action is required.

DRNI_SECONDARY_MADDOWN

Message text	The interfaces on the device will be placed in DRNI MAD DOWN state.
Variable fields	N/A
Severity level	4
Example	DRNI/6/DRNI_SECONDARY_MADDOWNN: The interfaces on the device will be placed in DRNI MAD DOWN state.
Explanation	All network interfaces on the secondary DR device were shut down because the IPL went down.
Recommended action	· Verify that the IPL is correctly connected and the cable is working correctly. · Verify that the device and the DR peer have correct DR settings.

DRNI_SYSEVENT_DEVICEROLE_CHANGE

Message text	Device role changed from [STRING] to [STRING].
Variable fields	$1: Old device role. $2: New device role.
Severity level	6
Example	DRNI/6/DRNI_SYSEVENT_DEVICEROLR_CHANGE: Device role changed from Secondary to Primary.
Explanation	The DR role of the device changed because of configuration changes on the device or the DR peer.
Recommended action	No action is required.

DRNI_SYSEVENT_MAC_CHANGE

Message text	System MAC address changed from [STRING] to [STRING].
Variable fields	$1: Old system MAC address. $2: New system MAC address.
Severity level	6
Example	DRNI/6/DRNI_SYSEVENT_MAC_CHANGE: System MAC address changed from 1-1-1 to 2-2-2.
Explanation	The DR system MAC address was modified.
Recommended action	No action is required.

DRNI_SYSEVENT_NUMBER_CHANGE

Message text	System number changed from [STRING] to [STRING].
Variable fields	$1: Old system number. $2: New system number.
Severity level	6
Example	DRNI/6/DRNI_SYSEVENT_NUMBER_CHANGE: System number changed from 1 to 2.
Explanation	The DR system number was modified.
Recommended action	No action is required.

DRNI_SYSEVENT_PRIORITY_CHANGE

Message text	System priority changed from [UINT16] to [UINT16].
Variable fields	$1: Old system priority. $2: New system priority.
Severity level	6
Example	DRNI/6/DRNI_SYSEVENT_PRIORITY_CHANGE: System priority changed from 123 to 564.
Explanation	The DR system priority was modified.
Recommended action	No action is required.

DRVPLAT messages

This section contains DRVPLAT messages.

DrvDebug

Message text	Chip [UINT32] temperature([UINT32]) in slot [UINT32] is too high and the board will be shutdown.
Variable fields	$1: Chip ID. $2: Temperature value. $3: Slot number.
Severity level	4
Example	DRVPLAT/4/DrvDebug: Chip 0 temperature(54) in slot 3 is too high and the board will be shutdown.
Explanation	The temperature of a chip on the specified card has exceeded the upper temperature threshold. The card will be shut down.
Recommended action	1. Check the fan tray status. Resolve the fan tray issue if any. 2. If it is not a fan tray issue, contact technical support.

Message text	hotspot [UINT32] in slot [UINT32] temperature([UINT32]) is too high, please check it.
Variable fields	$1: Hotspot ID. $2: Slot number. $3: Temperature value.
Severity level	4
Example	DRVPLAT/4/DrvDebug: hotspot 1 in slot 2 temperature(90) is too high, please check it.
Explanation	The temperature of the specified card has exceeded the upper temperature threshold. A check is required.
Recommended action	1. Check the fan tray status. Resolve the fan tray issue if any. 2. If it is not a fan tray issue, contact technical support.

Message text	hotspot [UINT32] in slot [UINT32] temperature([UINT32]) is too high and the board will be shutdown.
Variable fields	$1: Hotspot ID. $2: Slot number. $3: Temperature value.
Severity level	4
Example	DRVPLAT/4/DrvDebug: hotspot 1 in slot 2 temperature(90) is too high and the board will be shutdown.
Explanation	The temperature of the specified card has exceeded the upper temperature threshold. The card will be shut down.
Recommended action	1. Check the fan tray status. Resolve the fan tray issue if any. 2. If it is not a fan tray issue, contact technical support.

Message text	Warning: cpu temperature([UINT32]) in slot [UINT32] is too high, please check it.
Variable fields	$1: Temperature value. $2: Slot number.
Severity level	4
Example	DRVPLAT/4/DrvDebug: Warning: cpu temperature(90) in slot 2 is too high, please check it.
Explanation	The CPU temperature of the specified card has exceeded the upper temperature threshold. A check is required.
Recommended action	1. Check the fan tray status. Resolve the fan tray issue if any. 2. If it is not a fan tray issue, contact technical support.

Message text	Warning:Chip [UINT32] temperature([UINT32]) in slot [UINT32] is too high, please check it.
Variable fields	$1: Chip ID. $2: Temperature value. $3: Slot number.
Severity level	4
Example	DRVPLAT/4/DrvDebug: Warning:Chip 0 temperature(90) in slot 2 is too high, please check it.
Explanation	The temperature of a chip on the specified card has exceeded the upper temperature threshold. A check is required.
Recommended action	1. Check the fan tray status. Resolve the fan tray issue if any. 2. If it is not a fan tray issue, contact technical support.

Message text	FPGA [UINT32] temperature([UINT32]) in slot [UINT32] is too high and the board will be shutdown.
Variable fields	$1: FPGA chip ID. $2: Temperature value. $3: Slot number.
Severity level	4
Example	DRVPLAT/4/DrvDebug: FPGA 0 temperature(90) in slot 2 is too high and the board will be shutdown.
Explanation	The temperature of an FPGA chip on the card has exceeded the upper temperature threshold. The card will be shut down.
Recommended action	1. Check the fan tray status. Resolve the fan tray issue if any. 2. If it is not a fan tray issue, contact technical support.

Message text	SubCard cpu CN7809 temperature([UINT32]) in slot [UINT32] is too high and the board will be shutdown.
Variable fields	$1: Temperature value. $2: Slot number.
Severity level	4
Example	DRVPLAT/4/DrvDebug: SubCard cpu CN7809 temperature(90) in slot 2 is too high and the board will be shutdown.
Explanation	The temperature of the subcard CPU on the specified card has exceeded the upper temperature threshold. The card will be shut down.
Recommended action	1. Check the fan tray status. Resolve the fan tray issue if any. 2. If it is not a fan tray issue, contact technical support.

Message text	Power Error, there is no input in Power [UINT32].
Variable fields	$1: Power supply ID.
Severity level	4
Example	DRVPLAT/4/DrvDebug: Power Error, there is no input in Power 1.
Explanation	The specified power supply does not have power input.
Recommended action	Check the power supply status. If the power supply is abnormal, replace it or contact technical support.

Message text	Warning: Only one power exist!
Variable fields	N/A
Severity level	4
Example	DRVPLAT/4/DrvDebug: Warning: Only one power exist!
Explanation	The device has only one power supply present.
Recommended action	· Check the status of the other power supplies. If they are abnormal, replace them. · Install more power supplies.

Message text	Warning: Only one power [UINT32] exist !
Variable fields	$1: Power supply ID.
Severity level	4
Example	DRVPLAT/4/DrvDebug: Warning: Only one power [UINT32] exist !
Explanation	Only one power supply slot on the device has a power supply present.
Recommended action	· Check the status of the power supplies in the other power supply slots. If they are abnormal, replace them. · Install power supplies in the other power supply slots.

Message text	Warning: Power [UINT32] differs from power [UINT32] in types!
Variable fields	$1: Power supply ID_1. $2: Power supply ID_2.
Severity level	4
Example	DRVPLAT/4/DrvDebug: Warning: Power 1 differs from power 2 in types!
Explanation	The two specified power supplies are different in type.
Recommended action	Use power supplies of the same type.

Message text	Warning: power [UINT32] voltage is [UINT32], please check!
Variable fields	$1: Power supply ID. $2: Voltage.
Severity level	4
Example	DRVPLAT/4/DrvDebug: Warning: power 1 voltage is 220, please check!
Explanation	The voltage of the specified power supply is not in the acceptable range.
Recommended action	Check the power supply status. If the power supply is abnormal, replace it or contact technical support.

Message text	Warning: Chassis [UINT32] Fan [UINT32] is absent!
Variable fields	$1: Chassis ID $2: Fan tray ID.
Severity level	4
Example	DRVPLAT/4/DrvDebug: Warning: Chassis 1 Fan 1 is absent!
Explanation	The specified fan tray is in absent state.
Recommended action	Check the fan tray status. If the fan tray is abnormal, replace it or contact technical support..

Message text	Frame [HEX] power [HEX] state error!
Variable fields	$1: Chassis ID. $2: Power supply ID.
Severity level	4
Example	DRVPLAT/4/DrvDebug: Frame 0x01 power 0x01 state error!
Explanation	The specified power supply is in error state.
Recommended action	1. Replace the power supply. 2. If the issue persists, contact technical support.

Message text	Frame [HEX] fan [HEX] state error!
Variable fields	$1: Chassis ID. $2: Fan tray ID.
Severity level	4
Example	DRVPLAT/4/DrvDebug: Frame 0x01 fan 0x01 state error!
Explanation	The specified fan tray is in error state.
Recommended action	1. Replace the fan tray. 2. If the issue persists, contact technical support.

Message text	Frame [UINT32] fan command sending failed!
Variable fields	$1: Chassis ID.
Severity level	4
Example	DRVPLAT/4/DrvDebug: Frame 1 fan command sending failed!
Explanation	On the specified chassis, fan tray commands failed to be issued.
Recommended action	· Check the fan tray status. Resolve the fan tray issue if any. · Contact technical support.

Message text	Frame [UINT32] fan [UINT32] state: [HEX], write reg[HEX]:[HEX], reg[HEX]:[HEX] read reg[HEX]:[HEX], reg[HEX]:[HEX], reg[HEX]:[HEX]
Variable fields	$1: Chassis ID. $2: Fan tray ID. $3: State. $4: Write register ID. $5: Value written to the register. $6: Write register ID. $7: Value written to the register. $8: Read register ID. $9: Value read from the register. $10: Read register ID. $11: Value read from the register. $12: Read register ID. $13: Value read from the register.
Severity level	4
Example	DRVPLAT/4/DrvDebug: Frame 1 fan 2 state:0x0, write reg0x30:0x12, reg0x31:0x12 read reg0x32:0x12, reg0x33:0x12, reg0x34:0x12
Explanation	The system has written data to and read data from the registers of the fan tray.
Recommended action	No action is required.

Message text	Frame [UINT32] fan [UINT32] receive data [HEX] error!
Variable fields	$1: Chassis ID. $2: Fan tray ID. $3: Data value.
Severity level	4
Example	DRVPLAT/4/DrvDebug: Frame 1 fan 1 receive data 0x30 error!
Explanation	The fan tray received error data.
Recommended action	· Check the fan tray status. Resolve the fan tray issue if any. · Contact technical support.

Message text	Please check your fabric boards, at least one of them must be normal!
Variable fields	N/A
Severity level	2
Example	DRVPLAT/2/DrvDebug: Please check your fabric boards, at least one of them must be normal!
Explanation	You are required to check the fabric modules and ensure that a minimum one of fabric modules is normal.
Recommended action	Check the fabric module status.

Message text	In chassis [UINT32],the specified fabric-board [UINT32] does not work.
Variable fields	$1: Chassis ID. $2: Fabric module ID.
Severity level	2
Example	DRVPLAT/2/DrvDebug: In chassis 1,the specified fabric-board 10 does not work.
Explanation	The specified fabric module is faulty.
Recommended action	Replace the fabric module or contact technical support.

Message text	In chassis [UINT32],the specified fabric-board [UINT32] resume work.
Variable fields	$1: Chassis ID. $2: Fabric module ID.
Severity level	2
Example	DRVPLAT/2/DrvDebug: In chassis 1,the specified fabric-board 10 resume work.
Explanation	The specified fabric module resumed work.
Recommended action	No action is required.

Message text	Warning: In chassis [UINT32] slot [UINT32],all interconnected ports from chip [UINT32] to chip [UINT32] are fault,please check.
Variable fields	$1: Chassis ID. $2: Slot number. $3: Chip ID_1. $4: Chip ID_2.
Severity level	2
Example	DRVPLAT/2/DrvDebug: Warning: In chassis 1 slot 2,all interconnected ports from chip 0 to chip 1 are fault,please check.
Explanation	All interconnected ports between the two specified chips on the card are faulty.
Recommended action	Contact technical support.

Message text	Warning: In chassis [UINT32],all interconnected ports from slot [UINT32] to slot [UINT32] are fault,please check.
Variable fields	$1: Chassis ID. $2: Slot number_1. $3: Slot number_2.
Severity level	2
Example	DRVPLAT/2/DrvDebug: Warning: In chassis 1,all interconnected ports from slot 2 to slot 3 are fault,please check.
Explanation	All interconnected ports between the two specified cards are faulty.
Recommended action	Contact technical support.

Message text	On chip [UINT32] in chassis [UINT32] slot [UINT32], at least two internal ports are down. Please check the internal ports.The down ports are sfi[UINT32]
Variable fields	$1: Chip ID. $2: Chassis ID. $3: Slot number. $4: Port number.
Severity level	2
Example	DRVPLAT/2/DrvDebug: On chip 2 in chassis 1 slot 2, at least two internal ports are down. Please check the internal ports.The down ports are sfi35
Explanation	SFI interfaces on the chip were shut down.
Recommended action	Contact technical support.

Message text	In chassis [UINT32],from chip [UINT32] in slot [UINT32] to chip [UINT32] in slot [UINT32], the packet flow is dropped.
Variable fields	$1: Chassis ID. $2: Chip ID_1. $3: Slot number_1. $4: Chip ID_2. $5: Slot number_2.
Severity level	2
Example	DRVPLAT/2/DrvDebug: In chassis 1, from chip 0 in slot 1 to chip 0 in slot 2, the packet flow is dropped.
Explanation	Packet loss occurred from the source chip to the destination chip.
Recommended action	Contact technical support.

Message text	Fabric S in chassis [UINT32] slot [UINT32] can't start because Fabric B is inserted before, please reboot the system.
Variable fields	$1: Chassis ID. $2: Slot number.
Severity level	4
Example	DRVPLAT/4/DrvDebug: Fabric S in chassis 1 slot 10 can't start because Fabric B is inserted before, please reboot the system.
Explanation	Type S and Type B fabric modules are installed on the same device. The system must be rebooted.
Recommended action	Reboot the device.

Message text	Fabric A in chassis [UINT32] slot [UINT32] can't start because Fabric B is inserted before, please reboot the system.
Variable fields	$1: Chassis ID. $2: Slot number.
Severity level	4
Example	DRVPLAT/4/DrvDebug: Fabric A in chassis 1 slot 10 can't start because Fabric B is inserted before, please reboot the system.
Explanation	Type A and Type B fabric modules are installed on the same device. The system must be rebooted.
Recommended action	Reboot the device.

Message text	Fabric B in chassis [UINT32] slot [UINT32] can't start because Fabric S is inserted before, please reboot the system.
Variable fields	$1: Chassis ID. $2: Slot number.
Severity level	4
Example	DRVPLAT/4/DrvDebug: Fabric B in chassis 1 slot 10 can't start because Fabric S is inserted before, please reboot the system.
Explanation	Type B and Type S fabric modules are installed on the same device. The system must be rebooted.
Recommended action	Reboot the device.

Message text	Fabric B in chassis [UINT32] slot [UINT32] can't start because Fabric A is inserted before, please reboot the system.
Variable fields	$1: Chassis ID. $2: Slot number.
Severity level	4
Example	DRVPLAT/4/DrvDebug: Fabric B in chassis 1 slot 10 can't start because Fabric A is inserted before, please reboot the system.
Explanation	Type B and Type A fabric modules are installed on the same device. The system must be rebooted.
Recommended action	Reboot the device.

Message text	The port [UINT32] does not support the Enhance HigMode, please check.
Variable fields	$1: Port number.
Severity level	4
Example	DRVPLAT/4/DrvDebug: The port 17 does not support the Enhance HigMode, please check.
Explanation	The specified port does not support Enhance HigMode.
Recommended action	Contact technical support.

Message text	Power [UINT32] Remove.
Variable fields	$1: Power supply ID.
Severity level	2
Example	DRVPLAT/2/DrvDebug: Power 2 Remove.
Explanation	The specified power supply was removed.
Recommended action	No action is required.

Message text	The power of this device is not enough.
Variable fields	N/A
Severity level	2
Example	DRVPLAT/2/DrvDebug: The power of this device is not enough.
Explanation	Power is not sufficient for the device.
Recommended action	Install more power supplies on the device.

Message text	Fan Fault! Chassis [UINT32] Frame [UINT32] fan [UINT32] speed < 500(R.P.M).
Variable fields	$1: Chassis ID. $2: Fan tray ID. $3: Fan ID.
Severity level	2
Example	DRVPLAT/2/DrvDebug: Fan Fault! Chassis 1 Frame 1 fan 2 speed < 500(R.P.M).
Explanation	A fan is the specified fan tray is faulty.
Recommended action	Replace the fan tray.

Message text	Fan Adjusting failed! Chassis [UINT32] Frame [UINT32] fan [UINT32] speed is [UINT32](R.P.M), is too low!
Variable fields	$1: Chassis ID. $2: Fan tray ID. $3: Fan ID. $4: Fan speed.
Severity level	2
Example	DRVPLAT/2/DrvDebug: Fan Adjusting failed! Chassis 1 Frame 2 fan 3 speed is 1800(R.P.M), is too low!
Explanation	Fan speed adjustment failed. The speed of a fan on a specified fan tray is over low.
Recommended action	1. Replace the fan tray. 2. If the issue persists, contact technical support.

Message text	Fan Adjusting failed! Chassis [UINT32] Frame [UINT32] fan [UINT32] speed is [UINT32](R.P.M), is too high!
Variable fields	$1: Chassis ID. $2: Fan tray ID. $3: Fan ID. $4: Fan speed.
Severity level	2
Example	DRVPLAT/2/DrvDebug: Fan Adjusting failed! Chassis 1 Frame 2 fan 3 speed is 10000(R.P.M), is too high!
Explanation	Fan speed adjustment failed. The speed of a fan on a specified fan tray is too high.
Recommended action	1. Replace the fan tray. 2. If the issue persists, contact technical support.

Message text	All fabric boards are absent! Reboot all lpu boards.
Variable fields	N/A
Severity level	2
Example	DRVPLAT/2/DrvDebug: All fabric boards are absent! Reboot all lpu boards.
Explanation	No fabric modules were present. All LPUs will be rebooted.
Recommended action	Check the installation status of the fabric modules. If they are installed correctly, contact technical support.

Message text	Warning:Fans stop running in chassis [UINT32], please check it right now, otherwize all lpu boards will be powered down after [UINT32] minutes.
Variable fields	$1: Chassis ID. $2: Length of time.
Severity level	2
Example	DRVPLAT/2/DrvDebug: Warning:Fans stop running in chassis 1, please check it right now, otherwize all lpu boards will be powered off after 5 minutes.
Explanation	Fan trays stop rotating on the specified chassis. All LPUs will be powered off after the specified length of time.
Recommended action	· Check the fan tray status and identify the cause of the issue. · Replace the fan trays.

Message text	There is maybe some wrong with the ADM1029 temperature chip!
Variable fields	N/A
Severity level	2
Example	DRVPLAT/2/DrvDebug: There is maybe some wrong with the ADM1029 temperature chip!
Explanation	The ADM1029 temperature sensor chip is faulty.
Recommended action	Contact technical support.

Message text	There is maybe some wrong with the LM75 temperature chip!
Variable fields	N/A
Severity level	2
Example	DRVPLAT/2/DrvDebug: There is maybe some wrong with the LM75 temperature chip!
Explanation	The LM75 temperature sensor chip is faulty.
Recommended action	Contact technical support.

Message text	The Temperature is beyond the shutdown temperature limit, The POE Power is SHUT DOWN!
Variable fields	N/A
Severity level	2
Example	DRVPLAT/2/DrvDebug: The Temperature is beyond the shutdown temperature limit, The POE Power is SHUT DOWN!
Explanation	The temperature had exceeded the PoE shutdown temperature threshold. PoE was shut down.
Recommended action	1. Check the card temperature and fan tray status. Replace fan trays with high-speed ones or install filler panels in unused slots. 2. If the issue persists, contact technical support.

Message text	The Temperature is below the turn on temperature limit, The POE Power is TURN ON!
Variable fields	N/A
Severity level	2
Example	DRVPLAT/2/DrvDebug: The Temperature is below the turn on temperature limit, The POE Power is TURN ON!
Explanation	The temperature had dropped below the PoE turn-on temperature threshold. PoE was turned on.
Recommended action	Make sure the ambient temperature of the device is in the acceptable range. For more information, see the installation guide for the device.

Message text	Warning: Slot [UINT32] temperature too high, power off it, please check it right now, otherwize all lpu boards will be powered down after [UINT32] minutes.
Variable fields	$1: Slot number. $2: Length of time.
Severity level	2
Example	DRVPLAT/2/DrvDebug: Warning: Slot 2 temperature too high, power off it, please check it right now, otherwize all lpu boards will be powered off after 5 minutes.
Explanation	The temperature of the specified card is too high. All LPUs will be powered off after the specified length of time.
Recommended action	Check the fan tray status and determine whether a fan tray issue has occurred. If it is not a fan tray issue, replace the fan trays with high-speed ones and install filler panels in empty slots or contact technical support.

Message text	Warning: Power off all lpu boards, please check it right now.
Variable fields	N/A
Severity level	2
Example	DRVPLAT/2/DrvDebug: Warning: Power off all lpu boards, please check it right now.
Explanation	All LPUs were powered off.
Recommended action	Check the power supply status and identify the reason causing the issue, or contact technical support.

Message text	All lpu boards were powered down because Fans stopped running.
Variable fields	N/A
Severity level	2
Example	DRVPLAT/2/DrvDebug: All lpu boards were powered down because Fans stopped running.
Explanation	Fan trays stopped operation and all LPUs were powered off.
Recommended action	1. Check the fan tray status. If the fan trays are abnormal, replace the fan trays. 2. If the issue persists, contact technical support.

Message text	Warning: Not enough power to power on board chassis [UINT32] slot [UINT32]. Board power is [UINT32], system available power is [UINT32].
Variable fields	$1: Chassis ID. $2: Slot number. $3: Power supply ID_1 $4: Power supply ID_2.
Severity level	2
Example	DRVPLAT/2/DrvDebug: Warning: Not enough power to power on board chassis 1 slot 2. Board power is 3, system available power is 4.
Explanation	Power is insufficient.
Recommended action	Install more power supplies.

Message text	Warning: Try to supply power to slot [UINT32] fail!
Variable fields	$1: Slot number.
Severity level	2
Example	DRVPLAT/2/DrvDebug: Warning: Try to supply power to slot 2 fail!
Explanation	Failed to supply power to the specified card.
Recommended action	Identify the reason causing the issue and contact technical support.

Message text	Warning: the device bearing power is over charge ! Do not supply power to slot [UINT32] !
Variable fields	$1: Slot number.
Severity level	2
Example	DRVPLAT/2/DrvDebug: Warning: the device bearing power is over charge ! Do not supply power to slot 2!
Explanation	The power is insufficient. The device stops power supply to the specified card.
Recommended action	Check the power supplies to identify the reason causing the issue, and contact technical support.

Message text	Do not support this kind of hardware device!
Variable fields	N/A
Severity level	2
Example	DRVPLAT/2/DrvDebug: Do not support this kind of hardware device!
Explanation	A hardware device not supported by the device was installed.
Recommended action	Replace the hardware device with one compatible with the device.

Message text	This device does not support this kind of board!
Variable fields	N/A
Severity level	2
Example	DRVPLAT/2/DrvDebug: This device does not support this kind of board!
Explanation	A card not supported by the device was inserted.
Recommended action	Replace the card with one supported by the device.

Message text	Warning: Board on chassis [UINT32] slot [UINT32] is not compatible with master board. Board type and function is [UINT32].
Variable fields	$1: Chassis ID. $2: Slot number. $3: Card ID.
Severity level	2
Example	DRVPLAT/2/DrvDebug: Warning: Board on chassis 2 slot 2 is not compatible with master board. Board type and function is 28.
Explanation	The specified card is not compatible with the MPU.
Recommended action	Replace the card with one that is compatible with the MPU or replace the MPU.

Message text	Warning: Standby board on chassis [UINT32] slot [UINT32] is not compatible with master board, Standby board type is [UINT32].
Variable fields	$1: Chassis ID. $2: Slot number. $3: Card type.
Severity level	2
Example	DRVPLAT/2/DrvDebug: Warning: Standby board on chassis 1 slot 1 is not compatible with master board, Standby board type is 30.
Explanation	The specified standby MPU is not compatible with the active MPU.
Recommended action	Use active/standby MPUs compatible with each other.

Message text	Warning: The LPU board on chassis [UINT32] slot [UINT32] is not compatible with MPU board, its board type is [UINT32].
Variable fields	$1: Chassis ID. $2: Slot number. $3: Card type.
Severity level	2
Example	DRVPLAT/2/DrvDebug: Warning: The LPU board on chassis 1 slot 2 is not compatible with MPU board, its board type is 30.
Explanation	The specified LPU is not compatible with the MPU.
Recommended action	Replace the LPU with one compatible with the MPU, or replace the MPU.

Message text	Standby board software version differs from master board . Please download the same version!
Variable fields	N/A
Severity level	2
Example	DRVPLAT/2/DrvDebug: Standby board software version differs from master board . Please download the same version!
Explanation	The active and standby MPUs run different software versions.
Recommended action	Install the same software version for the active and standby MPUs.

Message text	Reboot Standby board for different version!
Variable fields	N/A
Severity level	2
Example	DRVPLAT/2/DrvDebug: Reboot Standby board for different version!
Explanation	The active and standby MPUs are of different versions. You are required to reboot the standby MPU.
Recommended action	Reboot the standby MPU.

Message text	Standby board type differs from master board . Warning: Standby board and master board must be same!!!
Variable fields	N/A
Severity level	2
Example	DRVPLAT/2/DrvDebug: Standby board type differs from master board . Warning: Standby board and master board must be same!!!
Explanation	The active and standby MPUs are of different models. You must use MPUs of same models.
Recommended action	Use MPUs of the same model.

Message text	WARNING: Ucast IPC packets were blocked between slot [UINT32] and slot [UINT32].
Variable fields	$1: Physical slot number. $2: Physical slot number.
Severity level	4
Example	DRVPLAT/4/DrvDebug: WARNING: Ucast IPC packets were blocked between slot 1 and slot 2.
Explanation	Unicast IPC packets were blocked between the two specified LPUs.
Recommended action	Contact technical support.

Message text	WARNING: Ucast IPC packets from slot [UINT32] to slot [UINT32] were blocked.
Variable fields	$1: Source physical slot number. $2: Destination physical slot number.
Severity level	4
Example	DRVPLAT/4/DrvDebug: WARNING: Ucast IPC packets from slot 1 to slot 2 were blocked
Explanation	Unicast IPC packets from the source LPU to the destination LPU were blocked.
Recommended action	Contact technical support.

Message text	WARNING: Bcast IPC packets from chassis [UINT32] slot [UINT32] to chassis [UINT32] slot [UINT32] were blocked.
Variable fields	$1: Source chassis ID. $2: Source physical slot number. $3: Destination chassis ID. $4: Destination physical slot number.
Severity level	4
Example	DRVPLAT/4/DrvDebug: WARNING: Bcast IPC packets from chassis 1 slot 2 to chassis 2 slot 4 were blocked
Explanation	Broadcast IPC packets from the source LPU to the destination LPU were blocked.
Recommended action	Contact technical support.

Message text	WARNING: Bcast IPC packets were blocked between slot [UINT32] and slot [UINT32]
Variable fields	$1: Physical slot number. $2: Physical slot number.
Severity level	4
Example	DRVPLAT/4/DrvDebug: WARNING: Bcast IPC packets were blocked between slot 1 and slot 2
Explanation	Broadcast IPC packets were blocked between the two specified LPUs.
Recommended action	Contact technical support.

Message text	WARNING: Bcast IPC packets from slot [UINT32] to slot [UINT32] were blocked.
Variable fields	$1: Source physical slot number. $2: Destination physical slot number.
Severity level	4
Example	DRVPLAT/4/DrvDebug: WARNING: Bcast IPC packets from slot 1 to slot 2 were blocked
Explanation	Broadcast IPC packets from the source LPU to the destination LPU were blocked.
Recommended action	Contact technical support.

Message text	WARNING: Slot [UINT32]: heartbeat with master board timed out
Variable fields	$1: Physical slot number.
Severity level	4
Example	DRVPLAT/4/DrvDebug: WARNING: Slot 1: heartbeat with master board timed out
Explanation	The specified card failed to receive heartbeat packets from the MPU within the timeout period.
Recommended action	Contact technical support.

Message text	WARNING: Heartbeat with slot [UINT32] timed out
Variable fields	$1: Physical slot number.
Severity level	4
Example	DRVPLAT/4/DrvDebug: WARNING: Heartbeat with slot 1 timed out
Explanation	The MPU failed to receive the heartbeat packets from the specified card within the timeout period.
Recommended action	Contact technical support.

Message text	WARNING: A minimum of three heartbeat timeouts occurred to slot [UINT32]. The slot will be isolated. Please replace it.
Variable fields	$1: Physical slot number.
Severity level	4
Example	DRVPLAT/4/DrvDebug: WARNING: A minimum of three heartbeat timeouts occurred to slot 1. The slot will be isolated. Please replace it
Explanation	The MPU failed to receive heartbeat packets from the specified card after three or more heartbeat timeout periods expired. The card will be isolated.
Recommended action	Replace the card or contact technical support.

Message text	WARNING: Heartbeat with slot [UINT32] timed out. The card in the slot will reboot automatically
Variable fields	$1: Physical slot number.
Severity level	4
Example	DRVPLAT/4/DrvDebug: WARNING: Heartbeat with slot 1 timed out. The card in the slot will reboot automatically
Explanation	The MPU failed to receive heartbeat packets from the specified card within the timeout period. The card will reboot automatically.
Recommended action	Reboot the card and determine whether the issue is resolved. If the issue persists, contact technical support.

Message text	WARNING: Detected persistent FCS error condition on inner port ([UINT32], [UINT32]).
Variable fields	$1: Chip ID. $2: Port number.
Severity level	4
Example	DRVPLAT/4/DrvDebug: WARNING: Detected persistent FCS error condition on inner port (0, 96).
Explanation	FCS errors were detected continuously on the specified port of the device.
Recommended action	Contact technical support.

Message text	WARNING: Inner port ([UINT32], [UINT32]) was down.
Variable fields	$1: Chip ID. $2: Port number.
Severity level	4
Example	DRVPLAT/4/DrvDebug: WARNING: Inner port (0, 96) was down.
Explanation	The specified inner port of the device went down.
Recommended action	Contact technical support.

Message text	WARNING: Link flappings occurred on inner port ([UINT32], [UINT32]).
Variable fields	$1: Chip ID. $2: Port number.
Severity level	4
Example	DRVPLAT/4/DrvDebug: WARNING: Link flappings occurred on inner port (1, 2).
Explanation	The specified internal port came up and went down frequently.
Recommended action	Contact technical support.

Message text	Task: CPU [UINT32] is occupied by process [STRING] for more than 15 seconds.
Variable fields	$1: CPU ID. $2: Process ID.
Severity level	4
Example	DRVPLAT/4/DrvDebug: Task: CPU 2 is occupied by process ifmgr for more than 15 seconds.
Explanation	The CPU was occupied by the specified process for a long time.
Recommended action	Contact technical support.

Message text	WARNING: Slot [UINT32] is isolated already. Maybe caused by the hardware failure, please remove and check it
Variable fields	$1: Slot number.
Severity level	4
Example	DRVPLAT/4/DrvDebug: WARNING: Slot 1 is isolated already. Maybe caused by the hardware failure, please remove and check it
Explanation	The specified card might have a hardware fault and has been isolated.
Recommended action	Replace the card.

Message text	WARNING: Chip [UINT32] IPT CRC [UINT32], please check.
Variable fields	$1: Chip ID. $2: IPT CRC error count.
Severity level	4
Example	DRVPLAT/4/DrvDebug: WARNING: Chip 1 IPT CRC 15, please check
Explanation	The specified chip has IPT CRC errors. A check is required.
Recommended action	Contact technical support.

Message text	WARNING: CPU Port has no packet input and output, please check
Variable fields	N/A
Severity level	4
Example	DRVPLAT/4/DrvDebug: WARNING: CPU Port has no packet input and output, please check
Explanation	The CPU port failed to send or receive packets correctly.
Recommended action	Contact technical support.

Message text	WARNING: CPU Port has no packet output, please check
Variable fields	N/A
Severity level	4
Example	DRVPLAT/4/DrvDebug: WARNING: CPU Port has no packet output, please check
Explanation	The CPU port failed to send packets correctly.
Recommended action	Contact technical support.

Message text	WARNING: CPU Port has no packet input, please check
Variable fields	N/A
Severity level	4
Example	DRVPLAT/4/DrvDebug: WARNING: CPU Port has no packet input, please check
Explanation	The CPU port failed to receive packets correctly.
Recommended action	Contact technical support.

Message text	WARNING: Slot [UINT32] Chip [UINT32] has timeout in scanning channel,please check!
Variable fields	$1: Global slot number. $2: Chip ID.
Severity level	4
Example	DRVPLAT/4/DrvDebug: WARNING: Slot 8 Chip 1 has timeout in scanning channel,please check!
Explanation	An issue has occurred on the inner channels on the specified card.
Recommended action	Contact technical support.

Message text	WARNING: Chassis [UINT32] Slot [UINT32] Chip [UINT32] has timeout in scanning channel,please check!
Variable fields	$1: Chassis ID. $2: Global slot number. $3: Chip ID.
Severity level	4
Example	DRVPLAT/4/DrvDebug: WARNING: Chassis 1 Slot 3 Chip 0 has timeout in scanning channel,please check!
Explanation	An issue has occurred on the inner channels on the specified card.
Recommended action	Contact technical support.

Message text	The max-ecmp-num configuration should be the same on devices in one IRF.
Variable fields	N/A
Severity level	4
Example	DRVPLAT/4/DrvDebug: The max-ecmp-num configuration should be the same on devices in one IRF.
Explanation	The devices in the IRF fabric support different maximum numbers of ECMP routes.
Recommended action	Configure the same maximum number of ECMP routes for the devices in the IRF fabric.

Message text	The Systemworking mode configuration should be the same on devices in one IRF.
Variable fields	N/A
Severity level	4
Example	DRVPLAT/4/DrvDebug: The Systemworking mode configuration should be the same on devices in one IRF.
Explanation	The devices in the IRF fabric do not operate in the same system working mode.
Recommended action	Specify the same system working mode for the devices in the IRF fabric.

Message text	The device does not support board in chassis [UINT32] slot [UINT32] ,type is unknown([HEX]), Please check.
Variable fields	$1: Chassis ID. $2: Slot ID. $3: Card type.
Severity level	4
Example	DRVPLAT/4/DrvDebug: The device does not support board in chassis 1 slot 2 ,type is unknown(0x18), Please check.
Explanation	The card type in the specified slot is not supported by the device.
Recommended action	Replace the card with one supported by the device.

Message text	The port [STRING] has been changed to inactive status, please check.
Variable fields	$1: Port type and number.
Severity level	4
Example	DRVPLAT/4/DrvDebug: The port Ten-GigabitEthernet1/3/0/1 has been changed to inactive status, please check.
Explanation	The specified port became inactive.
Recommended action	Check the IRF configuration and port status and identify the reason causing the issue. If the issue cannot be resolved, contact technical support.

Message text	The port [STRING] has been changed to active status.
Variable fields	$1: Port type and number.
Severity level	4
Example	DRVPLAT/4/DrvDebug: The port Ten-GigabitEthernet1/3/0/1 has been changed to active status.
Explanation	The specified port became active.
Recommended action	No action is required.

Message text	The port [STRING] can't receive irf pkt and has been changed to inactive status, please check.
Variable fields	$1: Port type and number.
Severity level	4
Example	DRVPLAT/4/DrvDebug: The port Ten-GigabitEthernet1/3/0/1 can't receive irf pkt and has been changed to inactive status, please check.
Explanation	The specified port failed to receive IRF packets and became inactive.
Recommended action	Check the IRF configuration and port status and identify the reason causing the issue. If the issue cannot be resolved, contact technical support.

Message text	The port [STRING] can't receive irf pkt, please check.
Variable fields	$1: Port type and number.
Severity level	4
Example	DRVPLAT/4/DrvDebug: The port Ten-GigabitEthernet1/3/0/1 can’t receive irf pkt, please check.
Explanation	The specified port failed to receive IRF packets.
Recommended action	Check the IRF configuration and port status and identify the reason causing the issue. If the issue cannot be resolved, contact technical support.

Message text	At least one fabric module slot is empty. Make sure a blank filler module has been installed in each empty slot so the switch can work correctly.
Variable fields	N/A
Severity level	4
Example	DRVPLAT/4/DrvDebug: At least one fabric module slot is empty. Make sure a blank filler module has been installed in each empty slot so the switch can work correctly.
Explanation	A minimum of one fabric module slot is empty. You are required to install a filler panel in each fabric module slot.
Recommended action	Install a filler panel in each empty fabric module slot.

Message text	All fabric boards are absent! Reboot all lpu boards.
Variable fields	N/A
Severity level	2
Example	DRVPLAT/2/DrvDebug: All fabric boards are absent! Reboot all lpu boards.
Explanation	No fabric modules are present. All LPUs will be rebooted.
Recommended action	Verify the installation of the fabric modules. If they are installed correctly, contact technical support.

Message text	Loopback exists on the interface [UINT32] [STRING].
Variable fields	$1: Interface index. $2: Interface type and number.
Severity level	2
Example	DRVPLAT/2/DrvDebug: Loopback exists on the interface 3 Ten-GigabitEthernet3/0/1.
Explanation	A loopback is present on the specified interface.
Recommended action	Check the port status and identify the reason causing the loopback. If the issue cannot be resolved, contact technical support.

Message text	This device do not support LSQ1IAGSC0 on chassis [UINT32] slot [UINT32]!
Variable fields	$1: Chassis ID $2: Slot number
Severity level	2
Example	DRVPLAT/2/DrvDebug: This device do not support LSQ1IAGSC0 on chassis 1 slot 10!
Explanation	The device does not support the LSQ1IAGSC0 card.
Recommended action	Replace the LSQ1IAGSC0 card with one compatible with the device.

Message text	WARNING: FCS error occurred on [UINT32].
Variable fields	$1: Port number.
Severity level	2
Example	DRVPLAT/2/DrvDebug: WARNING: FCS error occurred on 1/3/0/10.
Explanation	An FCS error occurred on the specified IRF port.
Recommended action	Check the IRF link status. If the IRF link status is normal, contact technical support.

Message text	Interface [UINT32] is isolated, it's will be cancelled after a down/up.
Variable fields	$1: Port number.
Severity level	2
Example	DRVPLAT/2/DrvDebug: Interface 1/3/0/10 is isolated, it's will be cancelled after a down/up.
Explanation	FCS errors occurred on the specified IRF port. The port will be isolated.
Recommended action	Locate the reason causing the FCS errors and resolve the issue.

Message text	WARNING: [UINT32] went down.
Variable fields	$1: Port number.
Severity level	2
Example	DRVPLAT/2/DrvDebug: WARNING: 1/3/0/10 went down.
Explanation	The specified IRF port went down.
Recommended action	Check the IRF link status.

Message text	WARNING: Chip [UINT32] Port [UINT32] has no packet input and output, please check.
Variable fields	$1: Chip ID. $2: Port number.
Severity level	2
Example	DRVPLAT/2/DrvDebug: WARNING: Chip 1 Port 2 has no packet input and output, please check.
Explanation	The specified IPC port failed to send or receive packets.
Recommended action	Contact technical support.

Message text	WARNING: Ucast IPC packets from slot [UINT32] to slot [UINT32] were occasionally dropped.
Variable fields	$1: Slot number. $2: Slot number.
Severity level	2
Example	DRVPLAT/2/DrvDebug: WARNING: Ucast IPC packets from slot 1 to slot 2 were occasionally dropped.
Explanation	Minor IPC unicast packet loss occurred from the source card to the destination card.
Recommended action	Contact technical support.

Message text	WARNING: Heavy Ucast IPC packet drops occurred in the direction from slot [UINT32] to slot [UINT32].
Variable fields	$1: Slot number. $2: Slot number.
Severity level	2
Example	DRVPLAT/2/DrvDebug: WARNING: Heavy Ucast IPC packet drops occurred in the direction from slot 1 to slot 2.
Explanation	Severe IPC unicast packet loss occurred from the source card to the destination card.
Recommended action	Contact technical support.

Message text	WARNING: Bcast IPC packets from slot [UINT32] to slot [UINT32] were occasionally dropped.
Variable fields	$1: Slot number. $2: Slot number.
Severity level	2
Example	DRVPLAT/2/DrvDebug: WARNING: Bcast IPC packets from slot 1 to slot 2 were occasionally dropped.
Explanation	Minor IPC broadcast packet loss occurred from the source card to the destination card.
Recommended action	Contact technical support.

Message text	WARNING: Heavy Bcast IPC packet drops occurred in the direction from slot [UINT32] to slot [UINT32].
Variable fields	$1: Slot number. $2: Slot number.
Severity level	2
Example	DRVPLAT/2/DrvDebug: WARNING: Heavy Bcast IPC packet drops occurred in the direction from slot 1 to slot 2.
Explanation	Severe IPC broadcast packet loss occurred from the source card to the destination card.
Recommended action	Contact technical support.

Message text	Forwarding Fault: Slot [UINT32] Chip [UINT32] to Slot [UINT32] chip [UINT32]
Variable fields	$1: Slot number. $2: Chip ID. $3: Slot number. $4: Chip ID.
Severity level	2
Example	DRVPLAT/2/DrvDebug: Forwarding Fault: Slot 1 Chip 2 to Slot 3 chip 4
Explanation	Forwarding failure occurred from the source chip to the destination chip.
Recommended action	Contact technical support.

Message text	Forwarding Warning: Slot [UINT32] Chip [UINT32] to Slot [UINT32] chip [UINT32]
Variable fields	$1: Slot number. $2: Chip ID. $3: Slot number. $4: Chip ID.
Severity level	2
Example	DRVPLAT/2/DrvDebug: Forwarding Warning: Slot 1 Chip 2 to Slot 3 chip 4
Explanation	Packet loss occurred from the source chip to the destination chip.
Recommended action	Contact technical support.

Message text	Interface [STRING] has MMU error. MMU: [UINT32], please check.
Variable fields	$1: Port number. $2: MMU cell count when the error occurs.
Severity level	2
Example	DRVPLAT/2/DrvDebug: Interface 1/0/0/23 has MMU error. MMU:150, please check.
Explanation	An MMU error occurred on the specified interface.
Recommended action	Check the device for hardware issues. If a software issue occurred, reboot the card to recover the services.

Message text	MMU error analysis failed, MMU interrupt disabled
Variable fields	N/A
Severity level	2
Example	DRVPLAT/2/DrvDebug: MMU error analysis failed, MMU interrupt disabled
Explanation	MMU error analysis failed, and MMU interrupt was disabled.
Recommended action	Contact technical support.

Message text	WARNING: Ucast IPC packets from chassis [UINT32] slot [UINT32] to chassis [UINT32] slot [UINT32] were blocked.
Variable fields	$1: Chassis ID. $2: Slot number. $3: Chassis ID. $4: Slot number.
Severity level	2
Example	DRVPLAT/2/DrvDebug: WARNING: Ucast IPC packets from chassis 1 slot 2 to chassis 3 slot 4 were blocked.
Explanation	Unicast IPC packets were blocked from the source card to the destination card.
Recommended action	Contact technical support.

Message text	WARNING: Ucast IPC packets were blocked between chassis [UINT32] slot [UINT32] and chassis [UINT32] slot [UINT32].
Variable fields	$1: Chassis ID. $2: Slot number. $3: Chassis ID. $4: Slot number.
Severity level	2
Example	DRVPLAT/2/DrvDebug: WARNING: Ucast IPC packets were blocked between chassis 1 slot 2 and chassis 3 slot 4.
Explanation	Unicast IPC packets were blocked between the two specified cards.
Recommended action	Contact technical support.

Message text	WARNING: Bcast IPC packets were blocked between chassis [UINT32] slot [UINT32] and chassis [UINT32] slot [UINT32].
Variable fields	$1: Chassis ID. $2: Slot number. $3: Chassis ID. $4: Slot number.
Severity level	2
Example	DRVPLAT/2/DrvDebug: WARNING: Bcast IPC packets were blocked between chassis 1 slot 2 and chassis 3 slot 4.
Explanation	Broadcast IPC packets were blocked between the two specified cards.
Recommended action	Contact technical support.

Message text	WARNING: Heartbeat with chassis [UINT32] slot [UINT32] timed out.
Variable fields	$1: Chassis ID. $2: Slot number.
Severity level	2
Example	DRVPLAT/2/DrvDebug: WARNING: Heartbeat with chassis %1 slot %2 timed out.
Explanation	The MPU failed to receive a heartbeat message from the specified card within the timeout period.
Recommended action	Contact technical support.

Message text	WARNING: Heartbeat with chassis [UINT32] slot [UINT32] timed out. The card in the slot will reboot automatically.
Variable fields	$1: Chassis ID. $2: Slot number.
Severity level	2
Example	DRVPLAT/2/DrvDebug: WARNING: Heartbeat with chassis 1 slot 2 timed out. The card in the slot will reboot automatically.
Explanation	The MPU failed to receive a heartbeat message from the specified card within the timeout period. The card will reboot automatically.
Recommended action	Identify the cause of the issue. If the issue persists after the card reboots, contact technical support.

Message text	WARNING: A minimum of three heartbeat timeouts occurred to chassis [UINT32] slot [UINT32]. The slot will be isolated. Please replace it.
Variable fields	$1: Chassis ID. $2: Slot number.
Severity level	2
Example	DRVPLAT/2/DrvDebug: WARNING: A minimum of three heartbeat timeouts occurred to chassis 1 slot 2. The slot will be isolated. Please replace it.
Explanation	The MPU failed to receive a heartbeat message from the specified card after three or more heartbeat timeout periods expired. The card will be isolated. You are required to replace the card.
Recommended action	Replace the card.

Message text	WARNING: Chassis [UINT32] slot [UINT32] is isolated already. Maybe caused by the hardware failure, please remove and check it.
Variable fields	$1: Chassis ID. $2: Slot number.
Severity level	2
Example	DRVPLAT/2/DrvDebug: WARNING: Chassis 1 slot 2 is isolated already. Maybe caused by the hardware failure, please remove and check it.
Explanation	The specified card was isolated, possibly because a hardware failure had occurred.
Recommended action	Replace the card.

Message text	Forwarding Fault: Chassis [UINT32] Slot [UINT32] Chip [UINT32] to Chassis [UINT32] Slot [UINT32]chip [UINT32]
Variable fields	$1: Chassis ID. $2: Slot number. $3: Chip ID. $4: Chassis ID. $5: Slot number. $6: Chip ID.
Severity level	2
Example	DRVPLAT/2/DrvDebug: Forwarding Fault: Chassis 1 Slot 2 Chip 0 to Chassis 2 Slot 1 chip 0
Explanation	Traffic forwarding from the source chip to the destination chip failed.
Recommended action	Identify whether an exception or packet loss has occurred on the forwarding path. If no exception or packet loss has occurred, contact technical support.

Message text	The spring-clips on the switching fabric module in slot [UINT16] are not closed. Please close the spring-clips.
Variable fields	$1: Slot number.
Severity level	2
Example	DRVPLAT/2/DrvDebug: The spring-clips on the switching fabric module in slot 1 are not closed. Please close the spring-clips.
Explanation	The spring clips on the specified fabric module are not closed.
Recommended action	Close the spring clips.

Message text	The spring-clips on the switching fabric module in slot [UINT16] of chassis [UINT32] are not closed. Please close the spring-clips.
Variable fields	$1: Slot number. $2: Chassis ID.
Severity level	2
Example	DRVPLAT/2/DrvDebug: The spring-clips on the switching fabric module in slot 1 of chassis 2 are not closed. Please close the spring-clips.
Explanation	The spring clips on the specified fabric module are not closed.
Recommended action	Close the spring clips.

Message text	(In standalone mode.) Warning: The card in slot [INT32] has a high power consumption and therefore a high cooling requirement. To continue to provide fan tray redundancy, substitute high speed fan trays. (In IRF mode.) Warning: The card in chassis [INT32] slot [INT32] has a high power consumption and therefore a high cooling requirement. To continue to provide fan tray redundancy, substitute high speed fan trays.
Variable fields	$1: Slot number. (In standalone mode.) $1: IRF member device ID. (In IRF mode.) $2: Slot number. (In IRF mode.)
Severity level	2
Example	DRVPLAT/2/DrvDebug: (In standalone mode.) Warning: The card in slot 9 has a high power consumption and therefore a high cooling requirement. To continue to provide fan tray redundancy, substitute high speed fan trays.
Explanation	A high-power card was installed on the device. To ensure adequate cooling for the device, you are required to replace all fan trays with high-speed ones.
Recommended action	Replace all fan trays on the device with high-speed ones.

Message text	The DSCP value to be marked is not an output value in the DSCP-DSCP priority map. The system will use 0 as the input value to obtain the output value and use the output value to overwrite the DSCP value in the packet.
Variable fields	N/A
Severity level	4
Example	H3C DRVPLAT/4/DrvDebug: The DSCP value to be marked is not an output value in the DSCP-DSCP priority map. The system will use 0 as the input value to obtain the output value and use the output value to overwrite the DSCP value in the packet.
Explanation	The DSCP value to be marked is not an output value in the DSCP-DSCP priority map. The system will use 0 as the input value to obtain the output value and use the output value to overwrite the DSCP value in the packet.
Recommended action	View DSCP-DSCP priority map settings and edit the settings as required.

Message text	Some bdbs were deleted on Chip $1. The DRAM might be faulty. Please replace the card.
Variable fields	$1: Chip number.
Severity level	4
Example	H3C DRVPLAT/4/DrvDebug: Some bdbs were deleted on Chip $1. The DRAM might be faulty. Please replace the card.
Explanation	A DRAM fault was detected and some bdbs were deleted.
Recommended action	Replace the faulty card.

ERPS messages

This section contains ERPS messages.

ERPS_FSM_CHANGED

Message text	Ethernet ring [UINT16] instance [UINT16] changed state to [STRING]
Variable fields	$1: ERPS ring ID. $2: ERPS instance ID. $3: ERPS instance status.
Severity level	6
Example	ERPS/4/ERPS_STATE_CHANGED: Ethernet ring 1 instance 1 changed state to Idle.
Explanation	The status of the ERPS instance changed.
Recommended action	No action is required.

ETHOAM messages

This section contains Ethernet OAM messages.

ETHOAM_CONNECTION_FAIL_DOWN

Message text	The link is down on interface [string] because a remote failure occurred on peer interface.
Variable fields	$1: Interface name.
Severity level	5
Example	ETHOAM/5/ETHOAM_CONNECTION_FAIL_DOWN: The link is down on interface Ethernet1/0/1 because a remote failure occurred on peer interface.
Explanation	The link goes down because a remote failure occurred on the peer interface.
Recommended action	Check the link status or the OAM status on the peer.

ETHOAM_CONNECTION_FAIL_TIMEOUT

Message text	Interface [string] removed the OAM connection because it received no Information OAMPDU before the timer times out.
Variable fields	$1: Interface name.
Severity level	5
Example	ETHOAM/5/ETHOAM_CONNECTION_FAIL_TIMEOUT: Interface Ethernet1/0/1 removed the OAM connection because it received no Information OAMPDU before the timer times out.
Explanation	The interface removed the OAM connection because it had not received Information OAMPDUs before the timer timed out.
Recommended action	Check the link status or the OAM status on the peer.

ETHOAM_CONNECTION_FAIL_UNSATISF

Message text	Interface [string] failed to establish an OAM connection because the peer doesn’t match the capacity of the local interface.
Variable fields	$1: Interface name.
Severity level	3
Example	ETHOAM/3/ETHOAM_CONNECTION_FAIL_UNSATISF: Interface Ethernet1/0/1 failed to establish an OAM connection because the peer doesn’t match the capacity of the local interface.
Explanation	Failed to establish an OAM connection because the peer does not match the OAM protocol state of the local interface.
Recommended action	Check the State field of the OAMPDUs sent from both ends.

ETHOAM_CONNECTION_SUCCEED

Message text	An OAM connection is established on interface [string].
Variable fields	$1: Interface name.
Severity level	6
Example	ETHOAM/6/ETHOAM_CONNECTION_SUCCEED: An OAM connection is established on interface Ethernet1/0/1.
Explanation	An OAM connection is established.
Recommended action	No action is required.

ETHOAM_DISABLE

Message text	Ethernet OAM is now disabled on interface [string].
Variable fields	$1: Interface name.
Severity level	6
Example	ETHOAM/6/ETHOAM_DISABLE: Ethernet OAM is now disabled on interface Ethernet1/0/1.
Explanation	Ethernet OAM is disabled.
Recommended action	No action is required.

ETHOAM_DISCOVERY_EXIT

Message text	OAM interface [string] quit the OAM connection.
Variable fields	$1: Interface name.
Severity level	5
Example	ETHOAM/5/ ETHOAM_DISCOVERY_EXIT: OAM interface Ethernet1/0/1 quit the OAM connection.
Explanation	The local interface ended the OAM connection.
Recommended action	No action is required.

ETHOAM_ENABLE

Message text	Ethernet OAM is now enabled on interface [string].
Variable fields	$1: Interface name.
Severity level	6
Example	ETHOAM/6/ETHOAM_ENABLE: Ethernet OAM is now enabled on interface Ethernet1/0/1.
Explanation	Ethernet OAM is enabled.
Recommended action	No action is required.

ETHOAM_ENTER_LOOPBACK_CTRLLED

Message text	The local OAM entity enters remote loopback as controlled DTE on OAM interface [string].
Variable fields	$1: Interface name.
Severity level	6
Example	ETHOAM/6/ ETHOAM_ENTER_LOOPBACK_CTRLLED: The local OAM entity enters remote loopback as controlled DTE on OAM interface Ethernet1/0/1.
Explanation	The local OAM entity enters remote loopback as controlled DTE after you enable OAM loopback on the peer end.
Recommended action	No action is required.

ETHOAM_ENTER_LOOPBACK_CTRLLING

Message text	The local OAM entity enters remote loopback as controlling DTE on OAM interface [string].
Variable fields	$1: Interface name.
Severity level	6
Example	ETHOAM/6/ ETHOAM_ENTER_LOOPBACK_CTRLLING: The local OAM entity enters remote loopback as controlling DTE on OAM interface Ethernet1/0/1.
Explanation	The local OAM entity enters remote loopback as controlling DTE after you enable OAM loopback on the interface.
Recommended action	No action is required.

ETHOAM_LOCAL_DYING_GASP

Message text	A local Dying Gasp event has occurred on [string].
Variable fields	$1: Interface name.
Severity level	4
Example	ETHOAM/4/ETHOAM_LOCAL_DYING_GASP: A local Dying Gasp event occurred on interface Ethernet1/0/1.
Explanation	A local Dying Gasp event occurs when you reboot the local device or shut down the interface.
Recommended action	Do not use the link until it recovers.

ETHOAM_LOCAL_ERROR_FRAME

Message text	An errored frame event occurred on local interface [string].
Variable fields	$1: Interface name.
Severity level	6
Example	ETHOAM/6/ETHOAM_LOCAL_ERROR_FRAME: An errored frame event occurred on local interface Ethernet1/0/1.
Explanation	An errored frame event occurred on the local interface.
Recommended action	Check the link between the local and peer ends.

ETHOAM_LOCAL_ERROR_FRAME_PERIOD

Message text	An errored frame period event occurred on local interface [string].
Variable fields	$1: Interface name.
Severity level	6
Example	ETHOAM/6/ETHOAM_LOCAL_ERROR_FRAME_PERIOD: An errored frame period event occurred on local interface Ethernet1/0/1.
Explanation	An errored frame period event occurred on the local interface.
Recommended action	Check the link between the local and peer ends.

ETHOAM_LOCAL_ERROR_FRAME_SECOND

Message text	An errored frame seconds event occurred on local interface [string].
Variable fields	$1: Interface name.
Severity level	6
Example	ETHOAM/6/ETHOAM_LOCAL_ERROR_FRAME_SECOND: An errored frame seconds event occurred on local interface Ethernet1/0/1.
Explanation	An errored frame seconds event occurred on the local interface.
Recommended action	Check the link between the local and peer ends.

ETHOAM_LOCAL_ERROR_SYMBOL

Message text	An errored symbol event occurred on local interface [string].
Variable fields	$1: Interface name.
Severity level	4
Example	ETHOAM/4/ETHOAM_LOCAL_ERROR_SYMBOL: An errored symbol event occurred on local interface Ethernet1/0/1.
Explanation	An errored symbol event occurred on the local interface.
Recommended action	Check the link between the local and peer ends.

ETHOAM_LOCAL_LINK_FAULT

Message text	A local Link Fault event occurred on interface [string].
Variable fields	$1: Interface name.
Severity level	4
Example	ETHOAM/4/ETHOAM_LOCAL_LINK_FAULT: A local Link Fault event occurred on interface Ethernet1/0/1.
Explanation	A local Link Fault event occurred when the local link goes down.
Recommended action	Re-connect the Rx end of the fiber on the local interface.

ETHOAM_LOOPBACK_EXIT

Message text	OAM interface [string] quit remote loopback.
Variable fields	$1: Interface name.
Severity level	4
Example	ETHOAM/4/ETHOAM_LOOPBACK_EXIT: OAM interface Ethernet1/0/1 quit remote loopback.
Explanation	The OAM interface ended remote loopback after one of the following events: · Remote loopback was disabled on the interface before the OAM connection was established . · The established OAM connection was torn down.
Recommended action	No action is required.

ETHOAM_LOOPBACK_EXIT_ERROR_STATU

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

ETHOAM_LOOPBACK_NO_RESOURCE

Message text	OAM interface [string] can’t enter remote loopback due to insufficient resources.
Variable fields	$1: Interface name.
Severity level	4
Example	ETHOAM/4/ETHOAM_LOOPBACK_NO_RESOURCE: OAM interface Ethernet1/0/1 can’t enter remote loopback due to insufficient resources.
Explanation	The OAM interface cannot enter remote loopback due to insufficient resources when you execute the oam remote-loopback start command on the local or remote OAM entity.
Recommended action	To enable remote loopback on an interface, you must set the hardware forwarding resources on the interface. Enabling remote loopback on a large number of interfaces might cause insufficient resources. Disable remote loopback on other interfaces, and execute the oam remote-loopback start command on the interface again.

ETHOAM_LOOPBACK_NOT_SUPPORT

Message text	OAM interface [string] can’t enter remote loopback because the operation is not supported.
Variable fields	$1: Interface name.
Severity level	4
Example	ETHOAM/4/ETHOAM_LOOPBACK_NOT_SUPPORT: OAM interface Ethernet1/0/1 can't enter remote loopback because the operation is not supported.
Explanation	The OAM interface cannot enter remote loopback because the operation is not supported on the device.
Recommended action	No action is required.

ETHOAM_QUIT_LOOPBACK_CTRLLED

Message text	The local OAM entity quit remote loopback as controlled DTE on OAM interface [string].
Variable fields	$1: Interface name.
Severity level	6
Example	ETHOAM/6/ ETHOAM_QUIT_LOOPBACK_CTRLLED: The local OAM entity quit remote loopback as controlled DTE on OAM interface Ethernet1/0/1.
Explanation	As the Loopback Control OAMPDUs receiving end, the local end quit remote loopback after you disabled OAM loopback on the peer end.
Recommended action	No action is required.

ETHOAM_QUIT_LOOPBACK_CTRLLING

Message text	The local OAM entity quit remote loopback as controlling DTE on OAM interface [string].
Variable fields	$1: Interface name.
Severity level	6
Example	ETHOAM/6/ETHOAM_QUIT_LOOPBACK_CONTROLLING: The local OAM entity quit remote loopback as controlling DTE on OAM interface Ethernet1/0/1.
Explanation	The local end quit remote loopback after you disabled OAM loopback on the local interface.
Recommended action	No action is required.

ETHOAM_REMOTE_CRITICAL

Message text	A remote Critical event occurred on interface [string].
Variable fields	$1: Interface name.
Severity level	4
Example	ETHOAM/4/ETHOAM_REMOTE_CRITICAL: A remote Critical event occurred on interface Ethernet1/0/1.
Explanation	A remote critical event occurred.
Recommended action	Do not use the link until it recovers.

ETHOAM_REMOTE_DYING_GASP

Message text	A remote Dying Gasp event occurred on interface [string].
Variable fields	$1: Interface name.
Severity level	4
Example	ETHOAM/4/ETHOAM_REMOTE_DYING_GASP: A remote Dying Gasp event occurred on interface Ethernet1/0/1.
Explanation	A remote Dying Gasp event occurred when you reboot the remote device and shut down the interface.
Recommended action	Do not use this link until it recovers.

ETHOAM_REMOTE_ERROR_FRAME

Message text	An errored frame event occurred on the peer interface [string].
Variable fields	$1: Interface name.
Severity level	6
Example	ETHOAM/6/ETHOAM_REMOTE_ERROR_FRAME: An errored frame event occurred on the peer interface Ethernet1/0/1.
Explanation	An errored frame event occurred on the peer.
Recommended action	Check the link between the local and peer ends.

ETHOAM_REMOTE_ERROR_FRAME_PERIOD

Message text	An errored frame period event occurred on the peer interface [string].
Variable fields	$1: Interface name.
Severity level	6
Example	ETHOAM/6/ETHOAM_REMOTE_ERROR_FRAME_PERIOD: An errored frame period event occurred on the peer interface Ethernet1/0/1.
Explanation	An errored frame period event occurred on the peer interface.
Recommended action	Check the link between the local and peer ends.

ETHOAM_REMOTE_ERROR_FRAME_SECOND

Message text	An errored frame seconds event occurred on the peer interface [string].
Variable fields	$1: Interface name.
Severity level	6
Example	ETHOAM/6/ETHOAM_REMOTE_ERROR_FRAME_SECOND: An errored frame seconds event occurred on the peer interface Ethernet1/0/1.
Explanation	An errored frame seconds event occurred on the peer.
Recommended action	Check the link between the local and peer ends.

ETHOAM_REMOTE_ERROR_SYMBOL

Message text	An errored symbol event occurred on the peer interface [string].
Variable fields	$1: Interface name.
Severity level	6
Example	ETHOAM/6/ETHOAM_REMOTE_ERROR_SYMBOL: An errored symbol event occurred on the peer interface Ethernet1/0/1.
Explanation	An errored symbol event occurred on the peer.
Recommended action	Check the link between the local and peer ends.

ETHOAM_REMOTE_EXIT

Message text	OAM interface [string] quit OAM connection because Ethernet OAM is disabled on the peer interface.
Variable fields	$1: Interface name.
Severity level	5
Example	ETHOAM/5/ ETHOAM_REMOTE_EXIT: OAM interface Ethernet1/0/1 quit OAM connection because Ethernet OAM is disabled on the peer interface.
Explanation	The local interface ended the OAM connection because Ethernet OAM was disabled on the peer interface.
Recommended action	No action is required.

ETHOAM_REMOTE_FAILURE_RECOVER

Message text	Peer interface [string] recovered.
Variable fields	$1: Interface name.
Severity level	5
Example	ETHOAM/5/ ETHOAM_REMOTE_FAILURE_RECOVER: Peer interface Ethernet1/0/1 recovered.
Explanation	The Link fault was cleared from the peer interface and the OAM connection was restored.
Recommended action	No action is required.

ETHOAM_REMOTE_LINK_FAULT

Message text	A remote Link Fault event occurred on interface [string].
Variable fields	$1: Interface name.
Severity level	4
Example	ETHOAM/4/ETHOAM_REMOTE_LINK_FAULT: A remote Link Fault event occurred on interface Ethernet1/0/1.
Explanation	A remote Link Fault event occurred when the remote link went down.
Recommended action	Reconnect the Rx end of the fiber on the remote interface.

ETHOAM_NO_ENOUGH_RESOURCE

Message text	The configuration failed on OAM interface [string] because of insufficient resources.
Variable fields	$1: Interface name.
Severity level	4
Example	ETHOAM/4/ ETHOAM_NO_ENOUGH_RESOURCE: The configuration failed on OAM interface Ethernet1/0/1 because of insufficient resources.
Explanation	The configuration failed on the OAM interface because of insufficient system resources.
Recommended action	Remove useless configurations to release the resources, and execute the command again.

ETHOAM_NOT_CONNECTION_TIMEOUT

Message text	Interface [string] quit Ethernet OAM because it received no Information OAMPDU before the timer times out.
Variable fields	$1: Interface name.
Severity level	5
Example	ETHOAM/5/ ETHOAM_NOT_CONNECTION_TIMEOUT: Interface Ethernet1/0/1 quit Ethernet OAM because it received no Information OAMPDU before the timer times out.
Explanation	The local interface ended Ethernet OAM because it had not received Information OAMPDUs before the timer timed out.
Recommended action	Check the link status and the OAM status on the peer.

FGROUP messages

This section contains flow group messages.

FLOWGROUP_APPLY_FAIL

Message text	Failed to apply flow group [STRING]. Reason: [STRING]
Variable fields	$1: Flow group ID. $2: Failure cause: · The operation is not supported. · Not enough resources to complete the operation.
Severity level	4
Example	FGROUP/4/FLOWGROUP_APPLY_FAIL: Failed to apply flow group 1. Reason: The operation is not supported.
Explanation	This message was generated when a flow group fails to be applied.
Recommended action	Modify or delete the flow group.

FLOWGROUP_MODIFY_FAIL

Message text	Failed to modify flow group [STRING]. Reason: [STRING]
Variable fields	$1: Flow group ID. $2: Failure cause: · The operation is not supported. · Not enough resources to complete the operation.
Severity level	4
Example	FGROUP/4/FLOWGROUP_MODIFY_FAIL: Failed to modify flow group 1. Reason: The operation is not supported.
Explanation	This message is generated when a flow group fails to be modified.
Recommended action	Delete unnecessary settings on the device if the failure is due to insufficient resources.

FNOTIFY messages

This section contains Forward Utility (FNOTIFY) messages.

NOTIFY

Message text	The feature [STRING] has not finished to process the [STRING] event in [UINT32] minutes.
Variable fields	$1: Feature name. ¡ ARP ¡ ND ¡ FIB ¡ WADJ ¡ L2VFIB ¡ WADJ6 ¡ OVERLAYMAC $2: Phase name. ¡ RESTORE: Data restoration. ¡ CROSSRESTORE: Data restoration between modules. ¡ RESTOREOVER: Restoration complete. ¡ PHASE3: SCM phase 3. $3: Time period, in minutes.
Severity level	6
Example	FNOTIFY/6/NOTIFY_EVENT: The feature ARP has not finished to process the PHASE3 event in 20 minutes
Explanation	This message is sent when a feature does not finish the event processing in a phase.
Recommended action	Locate which modules are encounting such problem.

‌

FS messages

This section contains file system messages.

FS_UNFORMATTED_PARTITION

Message text	Partition [%s] is not formatted yet. Please format the partition first.
Variable fields	$1: Partition name.
Severity level	4
Example	FS/4/FS_UNFORMATED_PARTITION: Partition usba0: is not formatted yet. Please format the partition first.
Explanation	The partition is not formatted. You must format a partition before you can perform other operations on the partition.
Recommended action	Format the specified partition.

FTPD messages

This section contains File Transfer Protocol daemon messages.

FTP_REACH_SESSION_LIMIT

Message text	FTP client [STRING] failed to log in. The current number of FTP sessions is [NUMBER]. The maximum number allowed is ([NUMBER]).
Variable fields	$1: IP address of the FTP client. $2: Current number of FTP sessions. $3: Maximum number of FTP sessions allowed by the device.
Severity level	6
Example	FTP/6/FTP_REACH_SESSION_LIMIT: FTP client 1.1.1.1 failed to log in. The current number of FTP sessions is 10. The maximum number allowed (10).
Explanation	The number of FTP connections reached the limit.
Recommended action	1. Use the display current-configuration \| include session-limit command to view the current limit for FTP connections. If the command does not display the limit, the device is using the default setting. 2. If you want to set a greater limit, execute the aaa session-limit command. If you think the limit is proper, no action is required.

gRPC messages

This section contains gRPC messages.

GRPC_LOGIN

Message text	[STRING] logged in from [STRING], session id [INT32].
Variable fields	$1: Username. $2: Client ID. $3: Session ID.
Severity level	6
Example	GRPC/6/GRPC_LOGIN: user logged in from 127.0.0.1, session id 1.
Explanation	A user logged in successfully.
Recommended action	No action is required.

GRPC_LOGIN_FAILED

Message text	[STRING] from [STRING] login failed. Or: [STRING] from [STRING] login failed. [STRING]
Variable fields	$1: Username. $2: Client ID. $3: Login failure reason. The value might be Number of the gRPC sessions reached the limit.
Severity level	4
Example	GRPC/4/GRPC_LOGIN_FAILED: user from 127.0.0.1 login failed.
Explanation	A user failed to log in.
Recommended action	1. If no failure reason is displayed, verify that the user is configured and the user entered the correct username and password. 2. If the maximum number of gRPC sessions was already reached, release gRPC sessions as required.

GRPC_LOGOUT

Message text	[STRING] logged out, session id [INT32].
Variable fields	$1: Username. $2: Session ID.
Severity level	6
Example	GRPC/6/GRPC_LOGOUT: user logged out, session id 1.
Explanation	A user logged out successfully.
Recommended action	No action is required.

GRPC_SERVER_FAILED

Message text	Failed to enable gRPC server.
Variable fields	N/A
Severity level	4
Example	GRPC/4/GRPC_SERVER_FAILED: Failed to enable gRPC server.
Explanation	A port conflict caused a gRPC server connection failure.
Recommended action	Identify whether a port conflict exist. If yes, modify the port settings as required.

GRPC_SUBSCRIBE_EVENT_FAILED

Message text	Failed to subscribe event [STRING].
Variable fields	$ 1: Event name.
Severity level	4
Example	GRPC/4/GRPC_SUBSCRIBE_EVENT_FAILED: Failed to subscribe event syslog.
Explanation	Failed to subscribe to an event.
Recommended action	No action is required.

GRPC_RECEIVE_SUBSCRIPTION

Message text	Received a subscription of module [STRING].
Variable fields	$ 1: Module name.
Severity level	6
Example	GRPC/6/GRPC_RECEIVE_SUBSCRIPTION: Received a subscription of module syslog.
Explanation	The device received a subscription request for a module.
Recommended action	No action is required.

HTTPD messages

This section contains HTTP daemon messages.

HTTPD_CONNECT

Message text	[STRING] client [STRING] connected to the server successfully.
Variable fields	$1: Connection type, HTTP or HTTPS. $2: Client IP address.
Severity level	6
Example	HTTPD/6/HTTPD_CONNECT: HTTP client 192.168.30.117 connected to the server successfully.
Explanation	The HTTP or HTTPS server accepted the request from a client. An HTTP or HTTPS connection was set up.
Recommended action	No action is required.

HTTPD_CONNECT_TIMEOUT

Message text	[STRING] client [STRING] connection idle timeout.
Variable fields	$1: Connection type, HTTP or HTTPS. $2: Client IP address.
Severity level	6
Example	HTTPD/6/HTTPD_CONNECT_TIMEOUT: HTTP client 192.168.30.117 connection to server idle timeout.
Explanation	An HTTP or HTTPS connection was disconnected because the idle timeout timer expires.
Recommended action	No action is required.

HTTPD_DISCONNECT

Message text	[STRING] client [STRING] disconnected from the server.
Variable fields	$1: Connection type, HTTP or HTTPS. $2: Client IP address.
Severity level	6
Example	HTTPD/6/HTTPD_DISCONNECT: HTTP client 192.168.30.117 disconnected from the server.
Explanation	An HTTP or HTTPS client was disconnected from the server.
Recommended action	No action is required.

HTTPD_FAIL_FOR_ACP

Message text	[STRING] client [STRING] was denied by the certificate access control policy and could not connect to the server.
Variable fields	$1: Connection type, HTTP or HTTPS. $2: Client IP address.
Severity level	6
Example	HTTPD/6/HTTPD_FAIL_FOR_ACP: HTTP client 192.168.30.117 was denied by the certificate attribute access control policy and could not connect to the server.
Explanation	An HTTP or HTTPS client was denied by the certificate access control policy.
Recommended action	No action is required.

HTTPD_REACH_CONNECT_LIMIT

Message text	[STRING] client [STRING] failed to connect to the server, because the number of connections reached the upper limit.
Variable fields	$1: Connection type, HTTP or HTTPS. $2: Client IP address.
Severity level	6
Example	HTTPD/6/HTTPD_REACH_CONNECT_LIMIT: HTTP client 192.168.30.117 failed to connect to the server, because the number of connections reached the upper limit.
Explanation	The number of connections reached the limit.
Recommended action	1. Use the display current-configuration \| include session-limit command to view the current limit for connections of the specified type. If the command does not display the limit, the device is using the default setting. 2. If you want to specify a greater limit, execute the aaa session-limit command. If you think the limit is proper, no action is required.

IFNET messages

This section contains interface management messages.

IF_BUFFER_CONGESTION_OCCURRENCE

Message text	[STRING] congestion occurs on queue [INTEGER] of [STRING].
Variable fields	$1: Data buffer type: ingress (for receive data buffer) or egress (for transmit data buffer). $2: Queue ID in the range of 0 to 7. $3: Interface name.
Severity level	4
Example	IFNET/4/IF_BUFFER_CONGESTION_OCCURRENCE: Ingress congestion occurs on queue 1 of GigabitEthernet1/0/1.
Explanation	On queue 1 of GigabitEthernet 1/0/1, congestion occurs in the receive data buffer.
Recommended action	Examine the network status.

IF_BUFFER_CONGESTION_CLEAR

Message text	[STRING] congestion on queue [UINT32] of [STRING] is cleared. [UINT64] packets are discarded.
Variable fields	$1: Data buffer type: ingress (for receive data buffer) or egress (for transmit data buffer). $2: Queue ID in the range of 0 to 7. $3: Interface name. $4: Number of packets dropped.
Severity level	5
Example	IFNET/5/IF_BUFFER_CONGESTION_CLEAR: Ingress congestion on queue 1 of GigabitEthernet1/0/1 is cleared. 1000 packets are discarded.
Explanation	On queue 1 of GigabitEthernet 1/0/1, congestion in the receive data buffer is removed. 1000 packets are dropped.
Recommended action	No action is required.

IF_JUMBOFRAME_WARN

Message text	The specified size of jumbo frames on the aggregate interface [STRING] is not supported on the member port [STRING].
Variable fields	$1: Aggregate interface name. $2: Member port name.
Severity level	3
Example	IFNET/3/IF_JUMBOFRAME_WARN: -MDC=1-Slot=3; The specified size of jumbo frames on the aggregate interface Bridge-Aggregation1 is not supported on the member port GigabitEthernet1/0/1.
Explanation	Some member ports do not support the jumbo frame size configured on the aggregate interface.
Recommended action	1. Identify the value ranges for the jumbo frame size supported on member ports. 2. Specify a jumbo frame size supported by member ports for the aggregate interface.

INTERFACE_NOTSUPPRESSED

Message text	Interface [STRING] is not suppressed.
Variable fields	$1: Interface name.
Severity level	6
Example	IFNET/6/INTERFACE_NOTSUPPRESSED: Interface Ethernet0/0/0 is not suppressed.
Explanation	The interface changed from suppressed state to unsuppressed state. When the interface is unsuppressed, the upper-layer services can detect the physical state changes of the interface.
Recommended action	No action is required.

INTERFACE_SUPPRESSED

Message text	Interface [STRING] was suppressed.
Variable fields	$1: Interface name.
Severity level	5
Example	IFNET/5/INTERFACE_SUPPRESSED: Interface Ethernet0/0/0 was suppressed.
Explanation	The interface was suppressed because its state frequently changed. When the interface is suppressed, the upper-layer services cannot detect the physical state changes of the interface.
Recommended action	1. Check whether the network cable of the interface or peer interface is frequently plugged and unplugged. 2. Configure physical state change suppression to adjust the suppression parameters.

LINK_UPDOWN

Message text	Line protocol state on the interface [STRING] changed to [STRING].
Variable fields	$1: Interface name. $2: State of link layer protocol, which can be up or down.
Severity level	5
Example	IFNET/5/LINK_UPDOWN: Line protocol state on the interface Ethernet0/0 changed to down.
Explanation	The link layer protocol state changed on an interface.
Recommended action	When the link layer protocol state of an interface is down, use the display interface command to display the link layer protocol state and locate the reason for which the link layer protocol state changed to down on the interface.

PFC_WARNING

Message text	On interface [STRING], the rate of [STRING] PFC packets of 802.1p priority [INTEGER] exceeded the PFC early-warning threshold [INTEGER] pps. The current rate is [INTEGER].
Variable fields	$1: Interface name. $2: Alarm direction, which can be input or output. $3: 802.1p priority. $4: Rate threshold at which the interface receives or sends PFC frames, in pps. $5: Rate at which the interface receives or sends PFC frames, in pps.
Severity level	4
Example	IFNET/4/PFC_WARNING: On interface GigabitEthernet1/0/1, the rate of input PFC packets of 802.1p priority 1 exceeded the PFC early-warning threshold 50 pps. The current rate is 60.
Explanation	The rate at which the interface receives or sends PFC frames reaches the early-warning threshold.
Recommended action	No action is required.

PHY_UPDOWN

Message text	Physical state on the interface [STRING] changed to [STRING].
Variable fields	$1: Interface name. $2: Link state, which can be up or down.
Severity level	3
Example	IFNET/3/PHY_UPDOWN: Physical state on the Ethernet0/0 changed to down.
Explanation	The physical state changed on an interface.
Recommended action	When the interface is physically down, check whether a physical link is present or whether the link fails.

PROTOCOL_UPDOWN

Message text	Protocol [STRING] state on the interface [STRING] changed to [STRING].
Variable fields	$1: Protocol name. $2: Interface name. $3: Protocol state, which can be up or down.
Severity level	5
Example	IFNET/5/PROTOCOL_UPDOWN: Protocol IPX state on the interface Ethernet6/4/1 changed to up.
Explanation	The state of a protocol has been changed on an interface.
Recommended action	When the state of a network layer protocol is down, check the network layer protocol configuration.

STORM_CONSTRAIN_BELOW

Message text	[STRING] is in controlled status, [STRING] flux falls below its lower threshold [STRING].
Variable fields	$1: Interface name. $2: Packet type, which can be BC, MC, or UC. $3: Lower suppression threshold: · lowerlimit% · lowerlimit pps · lowerlimit kbps
Severity level	1
Example	IFNET/1/STORM_CONSTRAIN_BELOW: GigabitEthernet1/0/1 is in controlled status, BC flux falls below its lower threshold 90%.
Explanation	The port is in controlled state. Any type of traffic on the port drops below the lower threshold from above the upper threshold.
Recommended action	No action is required.

STORM_CONSTRAIN_CONTROLLED

Message text	[STRING] turned into controlled status, port status is controlled, packet type is [STRING], upper threshold is [STRING].
Variable fields	$1: Interface name. $2: Packet type, which can be BC, MC, or UC. $3: Upper suppression threshold: · upperlimit% · upperlimit pps · upperlimit kbps
Severity level	1
Example	IFNET/1/STORM_CONSTRAIN_CONTROLLED: GigabitEthernet1/0/1 turned into controlled status, port status is controlled, packet type is BC, upper threshold is 90%.
Explanation	The port is in controlled state. Any type of traffic on the port exceeds the upper threshold.
Recommended action	No action is required.

STORM_CONSTRAIN_EXCEED

Message text	[STRING] is in controlled status, [STRING] flux exceeds its upper threshold [STRING].
Variable fields	$1: Interface name. $2: Packet type, which can be BC, MC, or UC. $3: Upper suppression threshold: · upperlimit% · upperlimit pps · upperlimit kbps
Severity level	1
Example	IFNET/1/STORM_CONSTRAIN_EXCEED: GigabitEthernet1/0/1 is in controlled status, BC flux exceeds its upper threshold 90%.
Explanation	The port is in controlled state. Any type of traffic on the port drops below the lower threshold from above the upper threshold.
Recommended action	No action is required.

STORM_CONSTRAIN_NORMAL

Message text	[STRING] returned to normal status, port status is [STRING], packet type is [STRING], lower threshold is [STRING].
Variable fields	$1: Interface name. $2: Packet type, which can be BC, MC, or UC. $3: Lower suppression threshold: · lowerlimit% · lowerlimit pps · lowerlimit kbps
Severity level	1
Example	IFNET/1/STORM_CONSTRAIN_NORMAL: GigabitEthernet1/0/1 returned to normal status, port status is normal, packet type is BC, lower threshold is 10%.
Explanation	The port is in normal state. Any type of traffic on the port drops below the lower threshold from above the upper threshold.
Recommended action	No action is required.

TUNNEL_LINK_UPDOWN

Message text	Line protocol state on the interface [STRING] changed to [STRING].
Variable fields	$1: Interface name. $2: Protocol state, which can be up or down.
Severity level	5
Example	IFNET/5/TUNNEL_LINK_UPDOWN: Line protocol state on the interface Tunnel1 changed to down.
Explanation	The state of a link layer protocol has been changed on a tunnel interface.
Recommended action	When the link layer protocol state of a tunnel interface is down, use the display interface command to display the link layer protocol state and locate the reason for which the link layer protocol state changed to down on the tunnel interface.

TUNNEL_PHY_UPDOWN

Message text	Physical state on the interface [STRING] changed to [STRING].
Variable fields	$1: Interface name. $2: Protocol state, which can be up or down.
Severity level	3
Example	IFNET/3/TUNNEL_PHY_UPDOWN: Physical state on the Tunnel1 changed to down.
Explanation	The state of a link layer protocol has been changed on a tunnel interface.
Recommended action	When the physical state of a link layer protocol is down, check whether a physical link is present or whether the link fails.

VLAN_MODE_CHANGE

Message text	Dynamic VLAN [INT32] has changed to a static VLAN.
Variable fields	$1: VLAN ID.
Severity level	5
Example	IFNET/5/VLAN_MODE_CHANGE: Dynamic VLAN 20 has changed to a static VLAN.
Explanation	Creating a VLAN interface for a VLAN cause the dynamic VLAN to become a static VLAN.
Recommended action	No action is required.

IP6ADDR

This section contains IPv6 addressing messages.

IP6ADDR_CREATEADDRESS_ERROR

Message text	Failed to create an address by the prefix. Reason: [STRING] on [STRING] and [STRING] on [STRING] overlap.
Variable fields	$1: IPv6 prefix. $2: Interface name. $3: IPv6 prefix. $4: Interface name.
Severity level	4
Example	IP6ADDR/4/IP6ADDR_CREATEADDRESS_ERROR: Failed to create an address by the prefix. Reason: 2001::/ 64 on GigabitEthernet1/0/2 and 2001::/64 on GigabitEthernet1/0/1 overlap.
Explanation	The device failed to use a prefix to generate an IPv6 address for an interface because the prefixes overlapped on this interface and another interface.
Recommended action	Cancel the IPv6 address configuration on the conflicting interface and configure the interface to generate an IPv6 address by using a different prefix.

IP6ADDR_CREATEADDRESS_INVALID

Message text	Can't configure the unspecified address or loopback address on [STRING] by using a prefix with all zeros.
Variable fields	$1: Interface name.
Severity level	4
Example	IP6ADDR/4/IP6ADDR_CREATEADDRESS_INVALID: Can't configure the unspecified address or loopback address on GigabitEthernet1/0/1 by using a prefix with all zeros.
Explanation	This message is sent when you use the ipv6 prefix command to configure an all-zero IPv6 prefix and then specify this prefix in the ipv6 address prefix-number command to configure an unspecified or loopback IPv6 address for an interface. Interfaces do not support the unspecified or loopback IPv6 address.
Recommended action	Cancel the configuration and reconfigure an IPv6 address for the interface.

IP6FW messages

This section contains IPv6 Forwarding (IP6FW) messages.

IP6FW_ABNORMAL_HEADERS

Message text	Received an IPv6 packet with repeated extension headers.
Variable fields	None.
Severity level	6
Example	IP6FW/6/IP6FW_ABNORMAL_HEADERS: Received an IPv6 packet with repeated extension headers.
Explanation	This message is sent when the device received an IPv6 packet with repeated extension headers.
Recommended action	Verify the packet source.

IP6FW_SETTING_FAILED_HOPLIMITEXCEED

Message text	Failed to add rule to forward packets with hop limit of 1: IPv6 address [STRING], VPN index [STRING], Error code: [STRING].
Variable fields	$1: IPv6 address. $2: VPN instance index. $3: Error code. · 0x40010001—Driver processing failed. · 0x40010008—Not supported by the driver. · 0x40010006—Driver configuration already exists. · 0x4001000b—Insufficient driver resource. · 0x20010002—Invalid driver parameters.
Severity level	6
Example	IP6FW/6/IP6FW_SETTING_FAILED_ HOPLIMITEXCEED: Failed to add rule to forward packets with hop limit of 1: IPv6 address 100::1, VPN index 1, Error code: 0x40010001.
Explanation	Failed to issue configuration of the forwarding hop-limit-exceeded destination command to the driver.
Recommended action	Check whether driver resources are sufficient.

‌

IP6FW_SETTING_FAILED_HOPLIMITUNVARIED

Message text	Failed to add rule to forward packets with the hop limit field unchanged: IPv6 address [STRING], VPN index [STRING], Error code: [STRING].
Variable fields	$1: IPv6 address. $2: VPN instance index. $3: Error code. · 0x40010001—Driver processing failed. · 0x40010008—Not supported by the driver. · 0x40010006—Driver configuration already exists. · 0x4001000b—Insufficient driver resource. · 0x20010002—Invalid driver parameters.
Severity level	6
Example	IP6FW/6/IP6FW_SETTING_FAILED_HOPLIMITUNVARIED: Failed to add rule to forward packets with the hop limit field unchanged: IPv6 address 100::1, VPN index 1, Error code: 0x40010001.
Explanation	Failed to issue configuration of the forwarding hop-limit-unvaried destination command to the driver.
Recommended action	Check whether driver resources are sufficient.

‌

IP6FW_SETTING_FAILED_NDFW

Message text	Failed to add rule to forward ND packets with IPv6 address [STRING] in VPN index [STRING] to tunnel index [STRING]. Error code: [STRING].
Variable fields	$1: IPv6 address. $2: VPN instance index. $3: Tunnel interface index. $4: Error code. · 0x40010001—Failed to issue configuration to the driver. · 0x40010008—Not supported by the driver. · 0x40010006—Driver configuration already exists. · 0x4001000b—Insufficient driver resource. · 0x20010002—Invalid driver parameters.
Severity level	6
Example	IP6FW/6/IP6FW_SETTING_FAILED_NDFW: Failed to add rule to forward ND packets with IPv6 address 100::1 in VPN index 1 to tunnel index 1. Error code: 0x40010001
Explanation	Failed to forward ND packets destined to a specific destination to the tunnel interface.
Recommended action	Contact Technical Support.

‌

IPADDR messages

This section contains IP addressing messages.

IPADDR_HA_EVENT_ERROR

Message text	A process failed HA upgrade because [STRING].
Variable fields	$1: HA upgrade failure reason: ¡ IPADDR failed the smooth upgrade. ¡ IPADDR failed to reupgrade to the master process. ¡ IPADDR stopped to restart the timer. ¡ IPADDR failed to upgrade to the master process. ¡ IPADDR failed to restart the upgrade. ¡ IPADDR failed to add the unicast object to the master task epoll. ¡ IPADDR failed to create an unicast object. ¡ IPADDR role switchover failed when the standby process switched to the master process. ¡ IPADDR switchover failed when the master process switched to the standby process. ¡ IPADDR HA upgrade failed. ¡ IPADDR failed to set the interface filtering criteria. ¡ IPADDR failed to register interface events. ¡ IPADDR failed to subscribe port events. ¡ IPADDR failed to add a VPN port event to the master epoll. ¡ IRDP failed to open DBM. ¡ IRDP failed to initiate a connection to the device management module. ¡ IRDP failed to add the master task epoll with the handle used to connect to the device management module. ¡ IRDP failed to register device management events. ¡ IRDP failed to subscribe port events. ¡ IRDP failed to add the master task epoll with the handle used to subscribe port events. ¡ IRDP failed to set the interface filtering criteria. ¡ IRDP failed to register interface events. ¡ IRDP failed to register network events. ¡ IRDP failed to create the interface control block storage handle. ¡ IRDP failed to create the timer. ¡ IRDP failed to add the master task epoll with the handle used to create the timer. ¡ IRDP failed to set the schedule time for the timer. ¡ IRDP failed to set the timer to unblocked status. ¡ IRDP failed to create a timer instance.
Severity level	4
Example	IPADDR/4/IPADDR_HA_EVENT_ERROR: A process failed HA upgrade because IPADDR failed the smooth upgrade.
Explanation	A process failed HA upgrade and the message showed the failure reason.
Recommended action	Please contact H3C Support.

IPADDR_HA_STOP_EVENT

Message text	The device received an HA stop event.
Variable fields	None.
Severity level	4
Example	IPADDR/4/IPADDR_HA_STOP_EVENT: The device received an HA stop event.
Explanation	This message is sent when the device receives an HA stop event.
Recommended action	Please contact H3C Support.

IPFW messages

This section contains IP Forwarding (IPFW) messages.

IPFW_SETTING_FAILED_ARPFW

Message text	Failed to add rule to forward ARP packets with IP address [STRING] in VPN index [STRING] to tunnel index [STRING]. Error code: [STRING].
Variable fields	$1: IP address. $2: VPN instance index. $3: Tunnel interface index. $4: Error code. · 0x40010001—Failed to issue configuration to the driver. · 0x40010008—Not supported by the driver. · 0x40010006—Driver configuration already exists. · 0x4001000b—Insufficient driver resource. · 0x20010002—Invalid driver parameters.
Severity level	6
Example	IPFW/6/IPFW_SETTING_FAILED_APPFW: Failed to add rule to forward ARP packets with IP address 10.0.0.1 in VPN index 1 to tunnel index 1. Error code: 0x40010001
Explanation	Failed to forward ARP packets destined to a specific destination to the tunnel interface.
Recommended action	Contact Technical Support.

‌

IPFW_SETTING_FAILED_TTLEXCEED

Message text	Failed to add rule to forward packets with TTL exceeded: IP address [STRING], VPN index [STRING], Error code: [STRING].
Variable fields	$1: IP address. $2: VPN instance index. $3: Error code. · 0x40010001—Failed to issue configuration to the driver. · 0x40010008—Not supported by the driver. · 0x40010006—Driver configuration already exists. · 0x4001000b—Insufficient driver resource. · 0x20010002—Invalid driver parameters.
Severity level	6
Example	IPFW/6/IPFW_SETTING_FAILED_TTLEXCEED: Failed to add rule to forward packets with TTL exceeded: IP address 10.0.0.1, VPN index 1, Error code: 0x40010001.
Explanation	Failed to issue configuration of the forwarding ttl-exceeded-packet destination command to the driver.
Recommended action	Check whether driver resources are sufficient.

‌

IPFW_SETTING_FAILED_TTLUNVARIED

Message text	Failed to add rule to forward packets with keeping the value unchanged in the TTL field: IP address [STRING], VPN index [STRING], Error code: [STRING].
Variable fields	$1: IP address. $2: VPN instance index. $3: Error code. · 0x40010001—Failed to issue configuration to the driver. · 0x40010008—Not supported by the driver. · 0x40010006—Driver configuration already exists. · 0x4001000b—Insufficient driver resource. · 0x20010002—Invalid driver parameters.
Severity level	6
Example	IPFW/6/IPFW_SETTING_FAILED_TTLUNVARIED:Failed to add rule to forward packets with the TTL field unchanged: IP address 10.0.0.1, VPN index 1, Error code: 0x40010001.
Explanation	Failed to issue configuration of the forwarding ttl-unvaried destination command to the driver.
Recommended action	Check whether driver resources are sufficient.

‌

IPoE messages

This section contains IPoE messages.

I PoE_USER_LOGOFF

Message text	-Username=[STRING]-IPAddr=[IPADDR]-IfName=[STRING]-OuterVLAN=[STRING] -InnerVLAN=[STRING]-MACAddr=[MAC]-Reason=[STRING]; The user logged off.
Variable fields	$1: Username. $2: IP address. $3: Interface name. $4: Outer VLAN ID. $5: Inner VLAN ID. $6: MAC address. $7: Cause (see Table 6).
Severity level	6
Example	IPOE/6/IPOE_USER_LOGOFF:-Username=abc-IPAddr=1.1.1.2-IfName=Route-Aggregation1023.4000-OutVLAN=1000-InnerVLAN=4000-MACAddr=0230-0103-5601-Reason=DHCP user request; The user logged off.
Explanation	The user has normally gone offline.
Recommended action	See Table 6.

Table 6 Causes and recommend actions

Cause	Description	Recommended action
DHCP user request	The user requested to go offline.	Check whether the user has gone offline.
DHCP decline	The use is logged off because of user address conflict.	Check whether changes are made for the DHCP configuration.
PORTAL notify	The portal module notified the user to go offline.	Check whether the user has gone offline.

IPoE_USER_LOGOFF_ABNORMAL

Message text	-Username=[STRING]-IPAddr=[IPADDR]-IfName=[STRING]-OuterVLAN=[STRING] -InnerVLAN=[STRING]-MACAddr=[MAC]-Reason=[STRING]; The user logged off abnormally.
Variable fields	$1: Username. $2: IP address. $3: Interface name. $4: Outer VLAN ID. $5: Inner VLAN ID. $6: MAC address. $7: Cause (see Table 7).
Severity level	6
Example	IPOE/6/IPOE_USER_LOGOFF_ABNORMAL:-Username=abc-IPAddr=1.1.1.2-IfName=Route-Aggregation1023.4000-OutVLAN=1000-InnerVLAN=4000-MACAddr=0230-0103-5601-Reason=Admin reset; The user logged off abnormally.
Explanation	The user has abnormally gone offline.
Recommended action	See Table 7.

Table 7 Causes and recommend actions

Cause	Description	Recommended action
Admin reset	The access interface went down, and the dynamic IPoE sessions were deleted or the static IPoE sessions were deleted.	1. Check whether the access interface has gone down. 2. Check whether the reset ip subscriber session command is executed to delete the dynamic IPoE sessions. 3. Check whether the undo ip subscriber session static command is executed to delete the static IPoE sessions. 4. Check whether new static users are added. 5. Check whether IPoE has been disabled by using the undo ip subscriber enable command.
Session timeout	The user session timed out or the traffic quota was used up.	Notify the user that the user session timed out or to renew the user account.
Session idle cut	The user traffic did not reach the threshold within the specified period.	Check whether the user has gone offline.
Traffic quota limit reached	The user traffic limit was reached.	Notify the user that the traffic is used up or to renew the user account.
Realtime accounting request to AAA failed	The device failed to receive a reply from any accounting server.	1. Verify that the device communicates with the accounting server correctly. 2. Verify that the accounting server operates correctly.
No AAA response during realtime accounting	In the realtime accounting phase, the device did not receive a response for the realtime accounting packets before the timeout timer expires.	1. Verify that the device communicates with the accounting server correctly. 2. Verify that the accounting server operates correctly.
No AAA response for accounting start	In the accounting start phase, the user did not receive a response for the start-accounting packets before the timeout timer expires.	1. Verify that the device communicates with the accounting server correctly. 2. Verify that the accounting server operates correctly.
No AAA response for accounting stop	In the accounting stop phase, the device did not receive a response for the stop-accounting packets before the timeout timer expires.	1. Verify that the device communicates with the accounting server correctly. 2. Verify that the accounting server operates correctly.
Accounting request to AAA failed	The device failed to send the accounting request to the accounting server.	1. Verify that the device communicates with the accounting server correctly. 2. Verify that the accounting server operates correctly.
Accounting update failure	The accounting update failed.	1. Verify that the device communicates with the accounting server correctly. 2. Verify that the accounting server operates correctly.
Accounting failed	The accounting failed.	1. Verify that the device communicates with the accounting server correctly. 2. Verify that the accounting server operates correctly.
AAA access limit reached	The upper limit of concurrent logins using the same local user name is reached.	1. Check the number of concurrent online users using the current local user name. 2. Modify the upper limit of the concurrent logins using the current local user name to a greater value by executing the access-limit command.
DHCP lease timeout	N/A.	Notify the user that the address lease has expired.
DHCP notify	The DHCP module notified the user to go offline.	Check whether the user has gone offline.
No response from DHCP server	N/A.	Check the DHCP server configuration.
DHCP configuration change	N/A.	Check the DHCP server configuration.
DHCP IP address allocation failure	N/A.	Check whether the DHCP address pool has been used up.
IP conflict on DHCP server	N/A.	Check whether the IP address allocated by the DHCP server conflicts with the IP address of the current device interface.
IPoE-DHCP data synchronization failed	N/A.	Save the related log information locally and contact the support.
User online detection failure	N/A.	Check whether the user has gone offline.
AAA request	The RADIUS server requested the user to go offline.	No action is required.
Insufficient hardware resources	N/A.	Save the related log information locally and contact the support.
Interface down	N/A.	Verify that the network cable of the user access interface is correctly connected.
Interface shutdown	N/A.	Check whether the shutdown command is configured on the user access interface.
Interface deactivation	N/A.	Check whether subcard hot swap is performed on the interface card.
VSRP status change	N/A.	Check whether the user has gone offline.
Standby device data deleted: master-standby device synchronization inconsistency	N/A.	Check whether the user has gone offline.
Failed to recover AAA resources	N/A.	Check whether hot swap of the interface card is performed and whether a primary/standby switchover is performed in VSRP mode.
Reauthorization during COA	N/A.	No action is required.
The static session already exists	The new online user conflicted with an existing static session.	Check whether the current online user conflicts with an existing static user.
The DHCP session is updated	The existing DHCP session was terminated because the new online user conflicted with the DHCP session.	Check whether the current online user conflicts with an existing DHCP user.
Inter-card data is synchronized	The local user was logged off because the synchronized sessions conflicted with the existing local session.	Save the related log information locally and contact the support.
User aged out before coming online	N/A.	1. Verify that the device communicates with the DHCP server correctly. 2. Check whether the DHCP address pool has been used up.
MPU-LPU data synchronization failure	N/A.	Save the related log information locally and contact the support.
NAK from the DHCP server or tenant duration is 0	N/A.	Check whether the user has gone offline.
NAT failed	N/A.	Check whether the card that supports the NAT collaboration feature fails.
BRAS errors	The BRAS software errors caused the user logoff.	1. Collect debugging information about the user login process by executing the following commands in sequence: ¡ terminal monitor ¡ terminal debugging ¡ debugging ip subscriber 2. Save the related log and debugging information locally and contact the support.

IPoE_USER_LOGON_FAILED

Message text	-Username=[STRING]-IPAddr=[IPADDR]-IfName=[STRING]-OuterVLAN=[STRING]-InnerVLAN=[STRING]-MACAddr=[MAC]-Reason=[STRING]; The user failed to come online.
Variable fields	$1: Username. $2: IP address. $3: Interface name. $4: Outer VLAN ID. $5: Inner VLAN ID. $6: MAC address. $7: Cause (see Table 8).
Severity level	5
Example	IPOE/5/IPOE_USER_LOGON_FAILED:-Username=abc-IPAddr=1.1.1.2-IfName=Route-Aggregation1023.4000-OuterVLAN=1000-InnerVLAN=4000-MACAddr=0230-0103-5601-Reason=Authentication failed; The user failed to come online.
Explanation	The user failed to come online.
Recommended action	See Table 8.

Table 8 Causes and recommended actions

Cause	Description	Recommended action
Authentication failed	The authentication failed.	1. Verify that the device communicates with the authentication server correctly. 2. Verify that the username is correct. 3. Verify that the password is correct. 4. Verify that the authentication domain on the device is correct.
Authorization failed	The authorization failed.	1. Verify that the device communicates with the authorization server correctly. 2. Verify that the authorization attributes deployed by the authorization server exist on the device and are configured correctly. 3. Verify that the device supports the authorization attributes deployed by the authorization server.
No authentication ACK from AAA	The RADIUS server failed to respond to the authentication request.	1. Verify that the device communicates with the RADIUS server correctly. 2. Verify that the RADIUS server operates correctly.
TACACS authentication reject	The TACACS server returned an access-reject packet.	1. Verify that the username is correct. 2. Verify that the password is correct.
Authentication request to AAA failed	The device failed to send the authentication request to the authentication server.	1. Verify that the device communicates with the authentication server correctly. 2. Verify that the authentication server operates correctly.
RADIUS authentication reject	The RADIUS server returned an access-reject packet.	1. Verify that the username is correct. 2. Verify that the password is correct.
AAA authorization information error	Failed to add user authorization information.	Verify that the authorization attributes deployed by the authorization server exist on the device and are configured correctly.
Local authentication failed: wrong password	The local authentication was rejected because of an incorrect password.	1. Verify that the username is correct. 2. Verify that the password is correct.
No AAA response during authentication	The device did not receive an AAA response from the authentication server before the timeout timer expires.	1. Verify that the device communicates with the authentication server correctly. 2. Verify that the authentication server operates correctly. 3. Verify that the shared key on the device is the same as the shared key on the authentication server.
The local user does not exist	The local user was not configured on the device.	1. Verify that the dial-in user is a legal user. 2. Add the local user if the user is a legal user but the respective local user does not exist on the device.
Exxxxxx (for example, E2531)	The RADIUS server returned an error code.	Verify that the RADIUS server operates correctly.
Maximum number of IPoE sessions already reached	The new user cannot come online because the number of online IPoE users has reached the upper limit allowed by the system or the interface.	1. For dynamic individual users, check whether one or multiple of the following commands are configured: 2. ip subscriber dhcp max-session 3. ip subscriber unclassified-ip max-session 4. If one or multiple of the commands are configured, check whether the number of online IPoE users has reached the upper limit allowed by the interface. 5. If the number of online IPoE users has reached the upper limit supported by the device, contact H3C Support.

IPoE_USER_LOGON_SUCCESS

Message text	-Username=[STRING]-IPAddr=[IPADDR]-IfName=[STRING]-OuterVLAN=[STRING]-InnerVLAN=[STRING]-MACAddr=[MAC]; The user came online successfully.
Variable fields	$1: Username. $2: IP address. $3: Interface name. $4: Outer VLAN ID. $5: Inner VLAN ID. $6: MAC address.
Severity level	6
Example	IPOE/6/IPOE_USER_LOGON_SUCCESS:-Username=abc-IPAddr=1.1.1.2-IfName=Route-Aggregation1023.4000-OuterVLAN=1000-InnerVLAN=4000-MACAddr=0230-0103-5601; The user came online successfully.
Explanation	The user has come online.
Recommended action	No action is required.

USER_TraceInfo

Message text	[objectID=[UINT16]][slotID=[UINT16]][STRING][user info: [STRING] ][trace info:[STRING]]
Variable fields	$1: ID of the service tracing object. $2: Slot number to which the access user belongs. $3: Service tracing phase. Options are IPoE and AAA. $4: User information (see Table 9). $5: Service tracing details. For more information about the tracing details of the IPoE phase and AAA phase, see Table 10 and Table 11, respectively.
Severity level	7
Example	USER/7/USER_TraceInfo:[objectID=1][slotID=1][IPoE][user info: MAC address: 4072-82a1-0206 IP address: 1.3.3.3 Access interface: GigabitEthernet1/0/1 Username: user1 Access mode: IPoE ] [trace info: AAA processed accounting-stop request and returned processing]
Explanation	The service tracing object with the ID of 1 in the IPoE phase. AAA processed accounting-stop request and returned processing.
Recommended action	No action is required.

Table 9 User information description

Field	Description
MAC address	MAC address of the access user.
Access interface	Access interface of the access user.
Service VLAN	Outer VLAN ID of the access user.
Customer VLAN	Inner VLAN ID of the access user.
Username	Username of the access user.
IP address	IP address of the access user.
Access mode	Access mode of the service tracing object.

Table 10 Tracing details in the IPoE phase

Filed	Description
IPoE session received an event:event, Phase:phase, State=state, UserID=userid	An IPoE session received an event: · event: Event name. Options are: ¡ Create and go—An IPoE session was created. ¡ Init—The user was online through packet initiation. ¡ Auth—The session was ready for authentication. ¡ AuthPass—The authentication succeeded. ¡ AuthFail—The authentication failed. ¡ AssignIP—An IP address was assigned successfully. ¡ Age—The dynamic session aged out. ¡ RuleOK—The rule deployment succeeded. ¡ RuleFail—The rule deployment failed. ¡ Offline—The user went offline. ¡ Quiet—The quiet timer expired. ¡ Destroy—The session was deleted. ¡ Change of Authorization—The AAA authorization attribute was changed. ¡ UserProfile OK—The user profile deployment succeeded. ¡ UserProfile Fail—The user profile deployment failed. ¡ Other—Other events. · phase: Phase of the session. Options are: ¡ Bind—Bind authentication phase. · state: State of the session. Options are: ¡ Invalid—The session is invalid. ¡ Init—The session is initiated. ¡ Offline—The session is going offline. ¡ Auth—The session is being authenticated. ¡ AuthFail—The authentication failed. ¡ AuthPass—The authentication succeeded. ¡ AssignedIP—The user has obtained an IP address. ¡ Online—The user comes online. ¡ Backup—Backup state, indicating that the user is an entry backed up from the peer. ¡ Unknown—Unknown state. · userID: User ID.
AAA processed type request and returned result	The type field can be one of the following values: · authentication · authorization · accounting-start · accounting-update · accounting-stop The result field can be one of the following values: · success · processing · fail(Errcode = code)
Received AAA type response and returned result	The type field can be one of the following values: · authentication · authorization · accounting-start · accounting-update · accounting-stop The result field can be one of the following values: · success · processing · fail(Errcode = code)
AAA processed type request and returned result, the traffic level is level	The type field can be one of the following values: · authentication · authorization · accounting-start · accounting-update · accounting-stop The result field can be one of the following values: · success · processing · fail(Errcode = code)
Received AAA type response and returned result, the traffic level is level	The type field can be one of the following values: · authentication · authorization · accounting-start · accounting-update · accounting-stop The result field can be one of the following values: · success · processing · fail(Errcode = code)
AAA processed type request and returned result, the service policy name is name	The type field can be one of the following values: · authentication · authorization · accounting-start · accounting-update · accounting-stop The result field can be one of the following values: · success · processing · fail(Errcode = code)
Received AAA type response and returned result, the service policy name is name	The type field can be one of the following values: · authentication · authorization · accounting-start · accounting-update · accounting-stop The result field can be one of the following values: · success · processing · fail(Errcode = code)
DHCP user request	The user requested to go offline.
DHCP lease timeout	N/A.
Session timeout	The user session timed out or the traffic quota was used up.
Authentication failure	The authentication failed.
Authorization failure	The authorization failed.
Admin reset	The access interface went down, and the dynamic IPoE sessions were deleted or the static IPoE sessions were deleted. · The reset ip subscriber session command was executed to delete the dynamic IPoE sessions. · The undo ip subscriber session static command was executed to delete the static IPoE sessions. · The undo ip subscriber enable command was executed to disable IPoE for users.
Session idle cut	The user traffic did not reach the threshold within the specified period.
User online detection failure	N/A.
AAA request	The RADIUS server requested the user to go offline.
Insufficient hardware resources	N/A.
Interface down	N/A.
Interface shutdown	N/A.
Interface deactivation	N/A.
BRAS errors	The BRAS software errors caused the user logoff.
Failed to recover AAA resources	N/A.
DHCP decline	The use is logged off because of user address conflict.
No response from DHCP server	N/A.
DHCP configuration change	N/A.
DHCP IP address allocation failure	N/A.
Accounting update failure	The accounting update failed.
Accounting failed	The accounting failed.
Reauthorization during COA	N/A.
The static session already exists	The new online user conflicted with an existing static session.
The DHCP session already exists	The new online user conflicted with an existing DHCP session.
Inter-card data is synchronized	The local user was logged off because the synchronized sessions conflicted with the existing local session.
User aged out before coming online	N/A.
MPU-LPU data synchronization failure	N/A.
NAK from the DHCP server or tenant duration is 0	N/A.
AAA access limit reached	The upper limit of concurrent logins using the same local user name is reached.
The local user does not exist	The local user was not configured on the device.
Local authentication failed: wrong password	The local authentication was rejected because of an incorrect password.
No AAA response during authentication	The device did not receive an AAA response from the authentication server before the timeout timer expires.
RADIUS authentication reject	The RADIUS server returned an access-reject packet.
AAA authorization information error	Failed to add user authorization information.
Realtime accounting request to AAA failed	The device failed to receive a reply from any accounting server.
No AAA response during realtime accounting	In the realtime accounting phase, the device did not receive a response for the realtime accounting packets before the timeout timer expires.
No AAA response for accounting start	In the accounting start phase, the user did not receive a response for the start-accounting packets before the timeout timer expires.
No AAA response for accounting stop	In the accounting stop phase, the device did not receive a response for the stop-accounting packets before the timeout timer expires.
Authentication request to AAA failed	The device failed to send the authentication request to the authentication server.
Accounting request to AAA failed	The device failed to send the accounting request to the accounting server.
No authentication ACK from AAA	The RADIUS server failed to respond to the authentication request.
TACACS authentication reject	The TACACS server returned an access-reject packet.
Traffic quota limit reached	The user traffic limit was reached.
IP conflict on DHCP server	N/A.
DHCP notify	The DHCP module notified the user to go offline.
IPoE-DHCP data synchronization failed	N/A.
NAT failed	N/A.
PORTAL notify	The portal module notified the user to go offline.

Table 11 Tracing details in the AAA phase

Field	Description
LocalAuth: Authentication request initiated	N/A.
LocalAuth: Authentication succeeded	N/A.
LocalAuth: Authorization request initiated	N/A.
LocalAuth: Authorization succeeded	N/A.
LocalAuth: Accounting start request initiated	N/A.
LocalAuth: Accounting start succeeded	N/A.
LocalAuth: Accounting stop request initiated	N/A.
LocalAuth: Accounting stop succeeded	N/A.
LocalAuth: Authentication failed/Wrong password	N/A.
LocalAuth: Authorization failed/Wrong password	N/A.
LocalAuth: Accounting start failed/Wrong password	N/A.
LocalAuth: Accounting stop failed/Wrong password	N/A.
LocalAuth: Authentication failed/User blocked	N/A.
LocalAuth: Authorization failed/User blocked	N/A.
LocalAuth: Accounting start failed/User blocked	N/A.
LocalAuth: Accounting stop failed/User blocked	N/A.
LocalAuth: Authentication failed/Service type mismatch	N/A.
LocalAuth: Authorization failed/Service type mismatch	N/A.
LocalAuth: Accounting start failed/Service type mismatch	N/A.
LocalAuth: Accounting stop failed/Service type mismatch	N/A.
LocalAuth: Authentication failed/Binding attribute mismatch	N/A.
LocalAuth: Authorization failed/Binding attribute mismatch	N/A.
LocalAuth: Accounting start failed/Binding attribute mismatch	N/A.
LocalAuth: Accounting stop failed/Binding attribute mismatch	N/A.
LocalAuth: Accounting start failed/Access limit reached	N/A.
LocalAuth: Authentication failed/User doesn’t exist	N/A.
LocalAuth: Authorization failed/User doesn’t exist	N/A.
LocalAuth: Accounting start failed/User doesn’t exist	N/A.
LocalAuth: Accounting stop failed/User doesn’t exist	N/A.
RADIUS: Authentication request initiated	N/A.
RADIUS: Authentication succeeded	N/A.
RADIUS: Accounting start request initiated	N/A.
RADIUS: Accounting start succeeded	N/A.
RADIUS: Accounting stop request initiated	N/A.
RADIUS: Accounting stop succeeded	N/A.
RADIUS: Authentication failed/Server reject	The RADIUS server rejected the authentication request because of password errors or other reasons.
RADIUS: Authentication failed/System error	The authentication failed because of system errors, for example, the specified RADIUS schemes did not exist.
RADIUS: Accounting start failed/System error	The accounting start failed because of system errors, for example, the specified RADIUS schemes did not exist.
RADIUS: Accounting update failed/System error	The accounting update failed because of system errors, for example, the specified RADIUS schemes did not exist.
RADIUS: Accounting stop failed/System error	The accounting stop failed because of system errors, for example, the specified RADIUS schemes did not exist.
RADIUS: Authentication failed/Response timeout	N/A.
RADIUS: Accounting start failed/Response timeout	N/A.
RADIUS: Accounting update failed/Response timeout	N/A.
RADIUS: Accounting stop failed/Response timeout	N/A.
RADIUS: Accounting update request initiated	N/A.
RADIUS: Authentication failed/Server blocked	The authentication failed because all the authentication servers configured in the specified RADIUS schemes did not respond.
RADIUS: Accounting start failed/Server blocked	The accounting start failed because all the accounting servers configured in the specified RADIUS schemes did not respond.
RADIUS: Accounting update failed/Server blocked	The accounting update failed because all the accounting servers configured in the specified RADIUS schemes did not respond.
RADIUS: Accounting stop failed/Server blocked	The accounting stop failed because all the accounting servers configured in the specified RADIUS schemes did not respond.

IPSG messages

This section contains IPSG messages.

IPSG_ADDENTRY_ERROR

Message text	Failed to add an IP source guard binding (IP [STRING], MAC [STRING], and VLAN [UINT16]) on interface [STRING]. [STRING].
Variable fields	$1: IPv4 address or IPv6 address. If you do not specify an IP address, this field displays N/A. $2: MAC address. If you do not specify a MAC address, this field displays N/A. $3: VLAN ID. If you do not specify a VLAN, this field displays 65535. $4: Interface name. If you do not specify an interface, this field displays N/A. $5: Failure reasons. Available options include: ¡ Feature not supported. ¡ Resources not sufficient. ¡ Maximum number of IPv4 binding entries already reached. ¡ Maximum number of IPv6 binding entries already reached. ¡ Unknown error.
Severity level	6
Example	IPSG/6/IPSG_ADDENTRY_ERROR: Failed to add an IP source guard binding (IP 1.1.1.1, MAC 0001-0001-0001, and VLAN 1) on interface Vlan-interface1. Resources not sufficient.
Explanation	IPSG failed to issue a static or dynamic IPSG binding. The message is sent in any of the following situations: · The IPSG feature is not supported. · The hardware resources are not sufficient for the operation. · The maximum number of IPv4SG or IPv6SG bindings is already reached. · An unknown error occurs.
Recommended action	To resolve the problem, you can perform the following tasks: · Clear the memory to release hardware resources when the failure is caused by insufficient hardware resources. · Add the IPSG binding again if you are adding a static binding. · Contact H3C Support if the failure is caused by an unknown error.

IPSG_DELENTRY_ERROR

Message text	Failed to delete an IP source guard binding (IP [STRING], MAC [STRING], and VLAN [UINT16]) on interface [STRING]. [STRING].
Variable fields	$1: IP address. If you do not specify an IP address, this field displays N/A. $2: MAC address. If you do not specify a MAC address, this field displays N/A. $3: VLAN ID. If you do not specify a VLAN, this field displays 65535. $4: Interface name. If you do not specify an interface, this field displays N/A. $5: Failure reason. Available options include: · Feature not supported. · Unknown error.
Severity level	6
Example	IPSG/6/IPSG_DELENTRY_ERROR: Failed to delete an IP source guard binding (IP 1.1.1.1, MAC 0001-0001-0001, and VLAN 1) on interface Vlan-interface1. Unknown error.
Explanation	IPSG failed to delete a global static IPSG binding. The message is sent in any of the following situations: · The IPSG feature is not supported. · An unknown error occurs.
Recommended action	To resolve the problem, you can perform the following tasks: · Delete the global static IPSG binding again. · Contact H3C Support if the failure is caused by an unknown error.

IPSG_ADDEXCLUDEDVLAN_ERROR

Message text	Failed to add excluded VLANs (start VLAN [UINT16] to end VLAN [UINT16]). [STRING].
Variable fields	$1: Start VLAN ID of the VLAN range that has been configured to be excluded from IPSG filtering. $2: End VLAN ID of the VLAN range that has been configured to be excluded from IPSG filtering. $3: Failure reasons. Available options include: · Feature not supported. · Resources not sufficient. · Unknown error.
Severity level	6
Example	IPSG/6/IPSG_ADDEXCLUDEDVLAN_ERROR: -MDC=1-Slot=4; Failed to add excluded VLANs (start VLAN 1 to end VLAN 5). Resources not sufficient.
Explanation	IPSG failed to issue the specified excluded VLANs. The message is sent in any of the following situations: · Excluded VLANs are not supported. · The hardware resources are not sufficient for the operation. · An unknown error occurs.
Recommended action	To resolve the problem, you can perform the following tasks: · Clear the memory to release hardware resources when the failure is caused by insufficient hardware resources. Then configure the excluded VLANs again. · Contact H3C Support if the failure is caused by an unknown error.

IPSG_DELEXCLUDEDVLAN_ERROR

Message text	Failed to delete excluded VLANs (start VLAN [UINT16] to end VLAN [UINT16]). [STRING].
Variable fields	$1: Start VLAN ID of the VLAN range that has been configured to be excluded from IPSG filtering. $2: End VLAN ID of the VLAN range that has been configured to be excluded from IPSG filtering. $3: Failure reasons. Available options include: · Feature not supported. · Resources not sufficient. · Unknown error.
Severity level	6
Example	IPSG/6/IPSG_DELEXCLUDEDVLAN_ERROR: -MDC=1-Slot=4; Failed to delete excluded VLANs (start VLAN 1 to end VLAN 5). Resources not sufficient.
Explanation	IPSG failed to delete the specified excluded VLANs. The message is sent in any of the following situations: · Excluded VLANs are not supported. · The hardware resources are not sufficient for the operation. · An unknown error occurs.
Recommended action	To resolve the problem, you can perform the following tasks: · Clear the memory to release hardware resources when the failure is caused by insufficient hardware resources. Then delete the excluded VLANs again. · Contact H3C Support if the failure is caused by an unknown error.

IRDP messages

This section contains IRDP messages.

IRDP_EXCEED_ADVADDR_LIMIT

Message text	The number of advertisement addresses on interface [STRING] exceeded the limit 255.
Variable fields	$1: Interface name.
Severity level	6
Example	IRDP/6/IRDP_EXCEED_ADVADDR_LIMIT: The number of advertisement addresses on interface Ethernet1/1/0/2 exceeded the limit 255.
Explanation	The number of addresses to be advertised on an interface exceeds the upper limit.
Recommended action	Remove unused addresses on the interface.

ISIS messages

This section contains IS-IS messages.

ISIS_LSP_CONFLICT

Message text	IS-IS [UINT16], [STRING] LSP, LSPID=[STRING], SeqNum=[HEX], system ID conflict might exist.
Variable fields	$1: IS-IS process ID. $2: IS type: Level-1 or Level-2. $3: LSP ID. $4: LSP sequence number.
Severity level	5
Example	ISIS/5/ISIS_LSP_CONFLICT: -MDC=1; IS-IS 1, Level-1 LSP, LSPID=1111.1111.1111.00-00, SeqNum=0x000045bf, system ID conflict might exist.
Explanation	System ID conflict might exist.
Recommended action	Determine whether the system ID of the device that generates the LSP conflicts with the system ID of another device.

ISIS_MEM_ALERT

Message text	ISIS Process received system memory alert [STRING] event.
Variable fields	$1: Type of the memory alarm.
Severity level	5
Example	ISIS/5/ISIS_MEM_ALERT: ISIS Process received system memory alert start event.
Explanation	IS-IS received a memory alarm.
Recommended action	Check the system memory and release memory for the modules that occupy too many memory resources.

ISIS_NBR_CHG

Message text	IS-IS [UINT16], [STRING] adjacency [STRING] ([STRING]), state changed to [STRING], Reason: [STRING].
Variable fields	$1: IS-IS process ID. $2: Neighbor level. $3: Neighbor ID. $4: Interface name. $5: Neighbor state. $6: Neighbor state change reason.
Severity level	5
Example	ISIS/5/ISIS_NBR_CHG: IS-IS 1, Level-1 adjacency 0000.0000.0001 (GigabitEthernet1/0/1), state changed to DOWN, Reason: circuit data clean.
Explanation	The neighbor state changed.
Recommended action	Pay attention to the neighbor state change reason. When the neighbor state changes to down, check for IS-IS configuration errors and loss of network connectivity.

ISSU messages

This section contains ISSU messages.

ISSU_PROCESSWITCHOVER

Message text	Switchover completed. The standby process became the active process.
Variable fields	N/A
Severity level	5
Example	ISSU/5/ISSU_PROCESSWITCHOVER: Switchover completed. The standby process became the active process.
Explanation	A user executed the issu run switchover command.
Recommended action	No action is required.

ISSU_ROLLBACKCHECKNORMAL

Message text	The rollback might not be able to restore the previous version for [STRING] because the status is not normal.
Variable fields	$1: Chassis number and slot number or slot number.
Severity level	4
Example	ISSU/4/ISSU_ROLLBACKCHECKNORMAL: The rollback might not be able to restore the previous version for chassis 1 slot 2 because the state is not normal.
Explanation	While an ISSU was in Switching state, a user executed the issu rollback command or the ISSU automatic-rollback timer expired. However, the status of the MPU was not Normal.
Recommended action	No action is required.

L2VPN messages

This section contains L2VPN messages.

L2VPN_BGPVC_CONFLICT_LOCAL

Message text	Remote site ID [INT32] (From [STRING], route distinguisher [STRING]) conflicts with local site.
Variable fields	$1: ID of a remote site. $2: IP address of the remote site. $3: Route distinguisher of the remote site.
Severity level	5
Example	L2VPN/5/L2VPN_BGPVC_CONFLICT_LOCAL: Remote site ID 1 (From 1.1.1.1, route distinguisher 1:1) conflicts with local site.
Explanation	A remote site ID conflicted with the local site ID. This message is generated when one of the following situations occurs: · The received remote site ID is the same as the local site ID. · The local site ID is configured the same as a received remote site ID.
Recommended action	Modify the site ID configuration on the local device or remote device. Or, configure the remote site ID in a different VPLS instance than the local site ID.

L2VPN_BGPVC_CONFLICT_REMOTE

Message text	Remote site ID [INT32] (From [STRING], route distinguisher [STRING]) conflicts with another remote site.
Variable fields	$1: ID of a remote site. $2: IP address of the remote site. $3: Route distinguisher of the remote site.
Severity level	5
Example	L2VPN/5/L2VPN_BGPVC_CONFLICT_REMOTE: Remote site ID 1 (From 1.1.1.1, route distinguisher 1:1) conflicts with another remote site.
Explanation	Two remote site IDs conflicted. This message is generated when the received remote site ID is the same as another received remote site ID.
Recommended action	Modify the site ID configuration on one remote device. Or, configure the two remote site IDs in different VPLS instances.

L2VPN_HARD_RESOURCE_NOENOUGH

Message text	No enough hardware resource for L2VPN.
Variable fields	N/A
Severity level	4
Example	L2VPN/4/L2VPN_HARD_RESOURCE_NOENOUGH: No enough hardware resource for L2VPN.
Explanation	Hardware resources for L2VPN were insufficient.
Recommended action	Check whether unnecessary VSIs, PWs, or ACs had been generated. If yes, delete them.

L2VPN_HARD_RESOURCE_RESTORE

Message text	Hardware resources for L2VPN are restored.
Variable fields	N/A
Severity level	6
Example	L2VPN/6/L2VPN_HARD_RESOURCE_RESTORE: Hardware resources for L2VPN are restored.
Explanation	Hardware resources for L2VPN were restored.
Recommended action	No action is required.

L2VPN_LABEL_DUPLICATE

Message text	Incoming label [INT32] for a static PW in [STRING] [STRING] is duplicate.
Variable fields	$1: Incoming label value. $2: Type of L2VPN, Xconnect-group or VSI. $3: Name of the Xconnect-group or VSI.
Severity level	4
Example	L2VPN/4/L2VPN_LABEL_DUPLICATE: Incoming label 1024 for a static PW in Xconnect-group aaa is duplicate.
Explanation	The incoming label of a static PW in this Xconnect-group or VSI was occupied by another configuration, for example, by a static LSP or by a static CRLSP. This message is generated when one of the following events occurs: · When MPLS is enabled, configure a static PW with an incoming label which is occupied by another configuration. · Enable MPLS when a static PW whose incoming label is occupied by another configuration already exists.
Recommended action	Remove this static PW, and reconfigure it with another incoming label.

LAGG messages

This section contains link aggregation messages.

LAGG_ACTIVE

Message text	Member port [STRING] of aggregation group [STRING] changed to the active state.
Variable fields	$1: Port name. $2: Link aggregation group type and ID.
Severity level	6
Example	LAGG/6/LAGG_ACTIVE: Member port FGE1/0/50 of aggregation group BAGG1 changed to the active state.
Explanation	A member port in an aggregation group changed to the Selected state.
Recommended action	No action is required.

LAGG_AUTO_AGGREGATION

Message text	Failed to assign automatic assignment-enabled interface [STRING] to an aggregation group. Please check the configuration on the interface.
Variable fields	$1: Port name.
Severity level	6
Example	LAGG/6/LAGG_AUTO_AGGREGATON: Failed to assign automatic assignment-enabled interface FGE1/0/1 to an aggregation group. Please check the configuration on the interface.
Explanation	A port failed to join an automatically created aggregation group for one of the following reasons: · The attribute configuration of the port is inconsistent with that of the aggregate interface. · Some settings on the port prevent it from joining the aggregation group.
Recommended action	To resolve this issue: · Modify the attribute configuration of the port to be consistent with the aggregate interface. · Remove the settings that affect automatic member port assignment from the port.

LAGG_INACTIVE_AICFG

Message text	Member port [STRING] of aggregation group [STRING] changed to the inactive state, because the member port and the aggregate interface have different attribute configurations.
Variable fields	$1: Port name. $2: Link aggregation group type and ID.
Severity level	6
Example	LAGG/6/LAGG_INACTIVE_AICFG: Member port FGE1/0/50 of aggregation group BAGG1 changed to the inactive state, because the member port and the aggregate interface have different attribute configurations.
Explanation	A member port in an aggregation group changed to the Unselected state because the member port and the aggregate interface had different attribute configurations.
Recommended action	Modify the attribute configurations of the member port to be consistent with the aggregate interface.

LAGG_INACTIVE_BFD

Message text	Member port [STRING] of aggregation group [STRING] changed to the inactive state, because the BFD session state of the port was down.
Variable fields	$1: Port name. $2: Link aggregation group type and ID.
Severity level	6
Example	LAGG/6/LAGG_INACTIVE_BFD: Member port FGE1/0/50 of aggregation group BAGG1 changed to the inactive state, because the BFD session state of the port is down.
Explanation	A member port in an aggregation group changed to the Unselected state because the BFD session on the port went down.
Recommended action	To resolve this issue: · Check for a link failure. · Modify the port settings to make sure it has the same operational key and attribute configuration as the reference port.

LAGG_INACTIVE_CONFIGURATION

Message text	Member port [STRING] of aggregation group [STRING] changed to the inactive state, because the aggregation configuration of the port is incorrect.
Variable fields	$1: Port name. $2: Link aggregation group type and ID.
Severity level	6
Example	LAGG/6/LAGG_INACTIVE_CONFIGURATION: Member port FGE1/0/50 of aggregation group BAGG1 changed to the inactive state, because the aggregation configuration of the port is incorrect.
Explanation	A member port in an aggregation group changed to the Unselected state because the member port and the aggregate interface had different aggregation configuration.
Recommended action	No action is required.

LAGG_INACTIVE_DUPLEX

Message text	Member port [STRING] of aggregation group [STRING] changed to the inactive state, because the duplex mode is different between the member port and the reference port.
Variable fields	$1: Port name. $2: Link aggregation group type and ID.
Severity level	6
Example	LAGG/6/LAGG_INACTIVE_DUPLEX: Member port FGE1/0/50 of aggregation group BAGG1 changed to the inactive state, because the duplex mode is different between the member port and the reference port.
Explanation	A member port in an aggregation group changed to the Unselected state because the duplex mode was different between the member port and the reference port.
Recommended action	Change the duplex mode of the member port to be the same as the reference port.

LAGG_INACTIVE_HARDWAREVALUE

Message text	Member port [STRING] of aggregation group [STRING] changed to the inactive state, because of the port's hardware restriction.
Variable fields	$1: Port name. $2: Link aggregation group type and ID.
Severity level	6
Example	LAGG/6/LAGG_INACTIVE_HARDWAREVALUE: Member port FGE1/0/50 of aggregation group BAGG1 changed to the inactive state, because of the port's hardware restriction.
Explanation	A member port in an aggregation group changed to the Unselected state because of the port's hardware restriction.
Recommended action	No action is required.

LAGG_INACTIVE_LOWER_LIMIT

Message text	Member port [STRING] of aggregation group [STRING] changed to the inactive state, because the number of active ports is below the lower limit.
Variable fields	$1: Port name. $2: Link aggregation group type and ID.
Severity level	6
Example	LAGG/6/LAGG_INACTIVE_LOWER_LIMIT: Member port FGE1/0/50 of aggregation group BAGG1 changed to the inactive state, because the number of active ports is below the lower limit.
Explanation	A member port in an aggregation group was placed in Unselected state because the required minimum number of Selected ports was not reached.
Recommended action	Make sure the minimum number of Selected ports is met.

LAGG_INACTIVE_PARTNER

Message text	Member port [STRING] of aggregation group [STRING] changed to the inactive state, because the aggregation configuration of its peer port is incorrect.
Variable fields	$1: Port name. $2: Link aggregation group type and ID.
Severity level	6
Example	LAGG/6/LAGG_INACTIVE_PARTNER: Member port FGE1/0/50 of aggregation group BAGG1 changed to the inactive state, because the aggregation configuration of its peer port is incorrect.
Explanation	A member port in an aggregation group changed to the Unselected state because the port's partner changed to the Unselected state.
Recommended action	No action is required.

LAGG_INACTIVE_PHYSTATE

Message text	Member port [STRING] of aggregation group [STRING] changed to the inactive state, because the physical state of the port is down.
Variable fields	$1: Port name. $2: Link aggregation group type and ID.
Severity level	6
Example	LAGG/6/LAGG_INACTIVE_PHYSTATE: Member port FGE1/0/50 of aggregation group BAGG1 changed to the inactive state, because the physical state of the port is down.
Explanation	A member port in an aggregation group changed to the Unselected state because the port went down.
Recommended action	Bring up the member port.

LAGG_INACTIVE_RESOURCE_INSUFICIE

Message text	Member port [STRING] of aggregation group [STRING] changed to the inactive state, because all aggregate resources are occupied.
Variable fields	$1: Port name. $2: Link aggregation group type and ID.
Severity level	6
Example	LAGG/6/LAGG_INACTIVE_RESOURCE_INSUFICIE: Member port FGE1/0/50 of aggregation group BAGG1 changed to the inactive state, because all aggregate resources are occupied.
Explanation	A member port in an aggregation group changed to the Unselected state because all aggregation resources were used.
Recommended action	No action is required.

LAGG_INACTIVE_SPEED

Message text	Member port [STRING] of aggregation group [STRING] changed to the inactive state, because the speed configuration of the port is incorrect.
Variable fields	$1: Port name. $2: Link aggregation group type and ID.
Severity level	6
Example	LAGG/6/LAGG_INACTIVE_SPEED: Member port FGE1/0/50 of aggregation group BAGG1 changed to the inactive state, because the speed configuration of the port is incorrect.
Explanation	A member port in an aggregation group changed to the Unselected state because the speed was different between the member port and the reference port.
Recommended action	Change the speed of the member port to be the same as the reference port.

LAGG_INACTIVE_UPPER_LIMIT

Message text	Member port [STRING] of aggregation group [STRING] changed to the inactive state, because the number of active ports has reached the upper limit.
Variable fields	$1: Port name. $2: Link aggregation group type and ID.
Severity level	6
Example	LAGG/6/LAGG_INACTIVE_UPPER_LIMIT: Member port FGE1/0/50 of aggregation group BAGG1 changed to the inactive state, because the number of active ports has reached the upper limit.
Explanation	The number of Selected ports reached the upper limit in a dynamic aggregation group. A member port in the aggregation group changed to the Unselected state because a more eligible port joined the aggregation group.
Recommended action	No action is required.

LDP messages

This section contains LDP messages.

LDP_SESSION_CHG

Message text	Session ([STRING], [STRING]) is [STRING].
Variable fields	$1: Peer's LDP ID. Value 0.0.0.0:0 indicates that the peer's LDP ID cannot be obtained. $2: VPN instance's name. Value public instance indicates that the session belongs to the public network. $3: State of the session, up or down. When the state is down, this field also displays the reason for the down state error. Possible reasons include: · interface not operational. · MPLS disabled on interface. · LDP disabled on interface. · LDP auto-configure disabled on interface. · VPN instance changed on interface. · LDP instance deleted. · targeted peer deleted. · L2VPN disabled targeted peer. · TE tunnel disabled targeted peer. · session protection disabled targeted peer. · process deactivated. · failed to receive the initialization message. · graceful restart reconnect timer expired. · failed to recover adjacency by NSR. · failed to upgrade session by NSR. · closed the GR session. · keepalive hold timer expired. · adjacency hold timer expired. · session reset. · TCP connection down. · received a fatal notification message. · internal error. · memory in critical state. · transport address changed on interface.
Severity level	5
Example	LDP/5/LDP_SESSION_CHG: Session (22.22.22.2:0, public instance) is up. LDP/5/LDP_SESSION_CHG: Session (22.22.22.2:0, VPN instance: vpn1) is down (hello hold timer expired).
Explanation	The session state changed.
Recommended action	When the session state is up, no action is required. When the session state is down, check the interface state, link state, and other configurations depending on the reason displayed.

LDP_SESSION_GR

Message text	Session ([STRING], [STRING]): ([STRING]).
Variable fields	$1: Peer's LDP ID. Value 0.0.0.0:0 indicates that the peer's LDP ID cannot be obtained. $2: VPN instance's name. Value public instance indicates that the session belongs to the public network. $3: State of the session graceful restart: · Start reconnection. · Reconnection failed. · Start recovery. · Recovery completed.
Severity level	5
Example	LDP/5/LDP_SESSION_GR: Session (22.22.22.2:0, VPN instance: vpn1): Start reconnection.
Explanation	State of the session graceful restart. When a GR-capable LDP session is down, the LDP GR started. This message is generated during the GR of the LDP session, indicating the current GR state.
Recommended action	Check for the reason of session graceful restart, which can be obtained from the LDP_SESSION_CHG log message. When the graceful restart state Reconnection failed is displayed, verify the interface state, link state, and other configurations according to the reason for the session graceful restart. No action is required for other graceful restart states.

LDP_SESSION_SP

Message text	Session ([STRING], [STRING]): ([STRING]).
Variable fields	$1: Peer's LDP ID. Value 0.0.0.0:0 indicates that the peer's LDP ID cannot be obtained. $2: VPN instance's name. Value public instance indicates that the session belongs to the public network. $3: State of the session protection: · Hold up the session. · Session recovered successfully. · Session recovery failed.
Severity level	5
Example	LDP/5/LDP_SESSION_SP: Session (22.22.22.2:0, VPN instance: vpn1): Hold up the session.
Explanation	When the last link adjacency of the session was lost, session protection started. This message is generated during the session protection process, indicating the current session protection state.
Recommended action	Verify the interface state and link state.

LLDP messages

This section contains LLDP messages.

LLDP_CREATE_NEIGHBOR

Message text	[STRING] agent new neighbor created on port [STRING] (IfIndex [UINT32]), neighbor's chassis ID is [STRING], port ID is [STRING].
Variable fields	$1: Agent type. $2: Port name. $3: Port ifIndex. $4: Neighbor's chassis ID. $5: Neighbor's port ID.
Severity level	6
Example	LLDP/6/LLDP_CREATE_NEIGHBOR: Nearest bridge agent new neighbor created on port Ten-GigabitEthernet10/0/15 (IfIndex 599), neighbor's chassis ID is 3822-d666-ba00, port ID is GigabitEthernet6/0/5.
Explanation	The port received an LLDP message from a new neighbor.
Recommended action	No action is required.

LLDP_DELETE_NEIGHBOR

Message text	[STRING] agent neighbor deleted on port [STRING] (IfIndex [UINT32]), neighbor's chassis ID is [STRING], port ID is [STRING].
Variable fields	$1: Agent type. $2: Port name. $3: Port ifIndex. $4: Neighbor's chassis ID. $5: Neighbor's port ID.
Severity level	6
Example	LLDP/6/LLDP_DELETE_NEIGHBOR: Nearest bridge agent neighbor deleted on port Ten-GigabitEthernet10/0/15 (IfIndex 599), neighbor's chassis ID is 3822-d666-ba00, port ID is GigabitEthernet6/0/5.
Explanation	The port received a deletion message when a neighbor was deleted.
Recommended action	No action is required.

LLDP_LESS_THAN_NEIGHBOR_LIMIT

Message text	The number of [STRING] agent neighbors maintained by port [STRING] (IfIndex [UINT32]) is less than [UINT32], and new neighbors can be added.
Variable fields	$1: Agent type. $2: Port name. $3: Port ifIndex. $4: Maximum number of neighbors a port can maintain.
Severity level	6
Example	LLDP/6/LLDP_LESS_THAN_NEIGHBOR_LIMIT: The number of nearest bridge agent neighbors maintained by port Ten-GigabitEthernet10/0/15 (IfIndex 599) is less than 5, and new neighbors can be added.
Explanation	New neighbors can be added for the port because the limit has not been reached.
Recommended action	No action is required.

LLDP_NEIGHBOR_AGE_OUT

Message text	[STRING] agent neighbor aged out on port [STRING] (IfIndex [UINT32]), neighbor's chassis ID is [STRING], port ID is [STRING].
Variable fields	$1: Agent type. $2: Port name. $3: Port ifIndex. $4: Neighbor's chassis ID. $5: Neighbor's port ID.
Severity level	5
Example	LLDP/5/LLDP_NEIGHBOR_AGE_OUT: Nearest bridge agent neighbor aged out on port Ten-GigabitEthernet10/0/15 (IfIndex599), neighbor's chassis ID is 3822-d666-ba00, port ID is GigabitEthernet6/0/5.
Explanation	This message is generated when the port failed to receive LLDPDUs from the neighbor within a certain period of time.
Recommended action	Verify the link status or the receive/transmit status of LLDP on the peer.

LLDP_NEIGHBOR_PROTECTION_BLOCK

Message text	The status of port [STRING] changed to blocked ([STRING]) for the [STRING] agent.
Variable fields	$1: Interface name. $2: Neighbor protection feature that caused the state change: aging or validation. $3: LLDP agent type.
Severity level	4
Example	LLDP/4/LLDP_NEIGHBOR_PROTECTION_BLOCK: -MDC=1; -ifDescr=GigabitEthernet1/0/1; The status of port GigabitEthernet1/0/1 changed to blocked (aging) for the nearest bridge agent.
Explanation	The port was blocked because of neighbor aging or neighbor validation failure.
Recommended action	· If the port is blocked because of neighbor aging, verify the link status or the receive/transmit status of LLDP on both ends. · If the port is blocked because of neighbor validation failure, verify that the following attribute values in the received LLDP packet match those configured on the port: ¡ Chassis ID subtype. ¡ Chassis ID. ¡ Port ID subtype. ¡ Port ID.

LLDP_NEIGHBOR_PROTECTION_DOWN

Message text	The status of port [STRING] changed to down (aging) for the [STRING] agent.
Variable fields	$1: Interface name. $2: LLDP agent type.
Severity level	4
Example	LLDP/4/LLDP_NEIGHBOR_PROTECTION_DOWN: -MDC=1; -ifDescr=GigabitEthernet1/0/1; The status of port GigabitEthernet1/0/1 changed to down (aging) for the nearest bridge agent.
Explanation	The port was shut down because of neighbor aging.
Recommended action	Verify the link status or the receive/transmit status of LLDP on both ends.

LLDP_NEIGHBOR_PROTECTION_UNBLOCK

Message text	The status of port [STRING] changed to unblocked for the [STRING] agent.
Variable fields	$1: Interface name. $2: LLDP agent type.
Severity level	4
Example	LLDP/4/LLDP_NEIGHBOR_PROTECTION_UNBLOCK: -MDC=1; -ifDescr=GigabitEthernet1/0/1; The status of port GigabitEthernet1/0/1 changed to unblocked for the nearest bridge agent.
Explanation	The port state changed from blocked to unblocked.
Recommended action	No action is required.

LLDP_NEIGHBOR_PROTECTION_UP

Message text	The status of port [STRING] changed to up for the [STRING] agent.
Variable fields	$1: Interface name. $2: LLDP agent type.
Severity level	4
Example	LLDP/4/LLDP_NEIGHBOR_PROTECTION_UP: -MDC=1; -ifDescr=GigabitEthernet1/0/1; The status of port GigabitEthernet1/0/1 changed to up for the nearest bridge agent.
Explanation	The port state changed from DOWN to UP.
Recommended action	No action is required.

LLDP_PVID_INCONSISTENT

Message text	PVID mismatch discovered on [STRING] (PVID [UINT32]), with [STRING] [STRING] (PVID [STRING]).
Variable fields	$1: Port name. $2: VLAN ID. $3: System name. $4: Port name. $5: VLAN ID.
Severity level	5
Example	LLDP/5/LLDP_PVID_INCONSISTENT: MDC=1; PVID mismatch discovered on Ten-GigabitEthernet0/2/6 (PVID 1), with Ten-GigabitEthernet0/2/7 (PVID 500).
Explanation	This message is generated when the PVID on the peer is different from the PVID of the local interface.
Recommended action	Configure the same PVID for the local and peer interfaces.

LLDP_REACH_NEIGHBOR_LIMIT

Message text	The number of [STRING] agent neighbors maintained by the port [STRING] (IfIndex [UINT32]) has reached [UINT32], and no more neighbors can be added.
Variable fields	$1: Agent type. $2: Port name. $3: Port ifIndex. $4: Maximum number of neighbors a port can maintain.
Severity level	5
Example	LLDP/5/LLDP_REACH_NEIGHBOR_LIMIT: The number of nearest bridge agent neighbors maintained by the port Ten-GigabitEthernet10/0/15 (IfIndex 599) has reached 5, and no more neighbors can be added.
Explanation	This message is generated when the port with its maximum number of neighbors reached received an LLDP packet.
Recommended action	No action is required.

LOAD messages

This section contains load management messages.

BOARD_LOADING

Message text	Board in chassis [INT32] slot [INT32] is loading software images.
Variable fields	$1: Chassis ID. $2: Slot ID.
Severity level	4
Example	LOAD/4/BOARD_LOADING: Board in chassis 1 slot 5 is loading software images.
Explanation	The card is loading software images during the boot process.
Recommended action	No action is required.

LOAD_FAILED

Message text	Board in chassis [INT32] slot [INT32] failed to load software images.
Variable fields	$1: Chassis ID. $2: Slot ID.
Severity level	3
Example	LOAD/3/LOAD_FAILED: Board in chassis 1 slot 5 failed to load software images.
Explanation	The card failed to load software images during the boot process.
Recommended action	1. Execute the display boot-loader command to identify the startup software images. 2. Execute the dir command to verify that the startup software images exist. If the startup software images do not exist or are damaged, re-upload the software images to the device or set another one as the startup software images. 3. If the problem persists, contract H3C/H3C Support.

LOAD_FINISHED

Message text	Board in chassis [INT32] slot [INT32] has finished loading software images.
Variable fields	$1: Chassis ID. $2: Slot ID.
Severity level	5
Example	LOAD/5/LOAD_FINISHED: Board in chassis 1 slot 5 has finished loading software images.
Explanation	The card has finished loading software images.
Recommended action	No action is required.

LOGIN messages

This section contains login messages.

LOGIN_AUTHENTICATION_FAILED

Message text	Authentication failed for [STRING] from [STRING] because of [STRING].
Variable fields	$1: Username. $2: Line name or IP address. $3: Failure reason: ¡ no AAA response from any server during the authentication. ¡ invalid username or password or service type mismatch. ¡ configuration error or other errors.
Severity level	5
Example	LOGIN/5/LOGIN_AUTHENTICATION_FAILED: Authentication failed for Usera from console0 because of no AAA response from any server during the authentication.
Explanation	A user failed the login authentication.
Recommended action	Read the failure reason and take actions accordingly.

LOGIN_FAILED

Message text	[STRING] failed to login from [STRING].
Variable fields	$1: Username. $2: Line name or IP address.
Severity level	5
Example	LOGIN/5/LOGIN_FAILED: TTY failed to log in from console0. LOGIN/5/LOGIN_FAILED: usera failed to log in from 192.168.11.22.
Explanation	A login attempt failed.
Recommended action	No action is required.

LOGIN_ INVALID_USERNAME_PWD

Message text	Invalid username or password from [STRING].
Variable fields	$1: User line name and user IP address.
Severity level	5
Example	LOGIN/5/LOGIN_INVALID_USERNAME_PWD: Invalid username or password from console0. LOGIN/5/LOGIN_INVALID_USERNAME_PWD: Invalid username or password from 192.168.11.22.
Explanation	A user entered an invalid username or password.
Recommended action	No action is required.

LPDT messages

This section contains loop detection messages.

LPDT_LOOPED

Message text	A loop was detected on [STRING].
Variable fields	$1: Port name.
Severity level	4
Example	LPDT/4/LPDT_LOOPED: A loop was detected on GigabitEthernet1/0/1.
Explanation	The first intra-VLAN loop was detected on a port.
Recommended action	Check the links and configuration on the device for the loop, and remove the loop.

LPDT_RECOVERED

Message text	All loops were removed on [STRING].
Variable fields	$1: Port name.
Severity level	5
Example	LPDT/5/LPDT_RECOVERED: All loops were removed on GigabitEthernet1/0/1.
Explanation	All intra-VLAN loops on a port were removed.
Recommended action	No action is required.

LPDT_VLAN_LOOPED

Message text	A loop was detected on [STRING] in VLAN [UINT16].
Variable fields	$1: Port name. $2: VLAN ID.
Severity level	4
Example	LPDT/4/LPDT_VLAN_LOOPED: A loop was detected on GigabitEthernet1/0/1 in VLAN 1.
Explanation	A loop in a VLAN was detected on a port.
Recommended action	Check the links and configurations in the VLAN for the loop, and remove the loop.

LPDT_VLAN_RECOVERED

Message text	A loop was removed on [STRING] in VLAN [UINT16].
Variable fields	$1: Port name. $2: VLAN ID.
Severity level	5
Example	LPDT/5/LPDT_VLAN_RECOVERED: A loop was removed on GigabitEthernet1/0/1 in VLAN 1.
Explanation	A loop in a VLAN was removed on a port.
Recommended action	No action is required.

LS messages

This section contains Local Server messages.

LOCALSVR_PROMPTED_CHANGE_PWD

Message text	Please change the password of [STRING] [STRING], because [STRING].
Variable fields	$1: Password type: ¡ device management user. ¡ user line. ¡ user line class. $2: Username, user line number, or user line class number. $3: Reason for password change: ¡ the current password is a weak-password. ¡ the current password is the default password. ¡ it is the first login of the current user or the password had been reset. ¡ the password had expired.
Severity level	6
Example	LOCALSVR/6/LOCALSVR_PROMPTED_CHANGE_PWD: Please change the password of device management user hhh, because the current password is a weak password.
Explanation	The device generated a log message to prompt a user to change the password of the user, user line, or user line class. The device will generate such a log message every 24 hours after the user logs in to the device if the password does not meet the password control requirements.
Recommended action	Change the user password as required: · If scheme authentication is used, change the local password of the user. · If password authentication is used, change the authentication password of the user line or user line class for the user.

LS_ADD_USER_TO_GROUP

Message text	Admin [STRING] added user [STRING] to group [STRING].
Variable fields	$1: Admin name. $2: Username. $3: User group name.
Severity level	4
Example	LS/4/LS_ADD_USER_TO_GROUP: Admin admin added user user1 to group group1.
Explanation	The administrator added a user into a user group.
Recommended action	No action is required.

LS_AUTHEN_FAILURE

Message text	User [STRING] from [STRING] failed authentication. [STRING]
Variable fields	$1: Username. $2: IP address. $3: Failure reason: ¡ "User not found." ¡ "Password verified failed." ¡ "User not active." ¡ "Access type mismatch." ¡ "Binding attribute is failed." ¡ "User in blacklist."
Severity level	5
Example	LS/5/LS_AUTHEN_FAILURE: User cwf@system from 192.168.0.22 failed authentication. "User not found."
Explanation	The local server rejected a user's authentication request.
Recommended action	No action is required.

LS_AUTHEN_SUCCESS

Message text	User [STRING] from [STRING] was authenticated successfully.
Variable fields	$1: Username. $2: IP address.
Severity level	6
Example	LS/6/LS_AUTHEN_SUCCESS: User cwf@system from 192.168.0.22 was authenticated successfully.
Explanation	The local server accepted a user's authentication request.
Recommended action	No action is required.

LS_DEL_USER_FROM_GROUP

Message text	Admin [STRING] delete user [STRING] from group [STRING].
Variable fields	$1: Admin name. $2: Username. $3: User group name.
Severity level	4
Example	LS/4/LS_DEL_USER_FROM_GROUP: Admin admin delete user user1 from group group1.
Explanation	The administrator deleted a user from a user group.
Recommended action	No action is required.

LS_DELETE_PASSWORD_FAIL

Message text	Failed to delete the password for user [STRING].
Variable fields	$1: Username.
Severity level	4
Example	LS/4/LS_DELETE_PASSWORD_FAIL: Failed to delete the password for user abcd.
Explanation	Failed to delete the password for a user.
Recommended action	Check the file system for errors.

LS_PWD_ADDBLACKLIST

Message text	User [STRING] was added to the blacklist due to multiple login failures, [STRING].
Variable fields	$1: Username. $2: Options include: ¡ but could make other attempts. ¡ and is permanently blocked. ¡ and was temporarily blocked for [UINT32] minutes.
Severity level	4
Example	LS/4/LS_PWD_ADDBLACKLIST: User user1 was added to the blacklist due to multiple login failures, but could make other attempts.
Explanation	A user was added to the blacklist because of multiple login failures.
Recommended action	Check the user's password.

LS_PWD_CHGPWD_FOR_AGEDOUT

Message text	User [STRING] changed the password because it was expired.
Variable fields	$1: Username.
Severity level	4
Example	LS/4/LS_PWD_CHGPWD_FOR_AGEDOUT: User aaa changed the password because it was expired.
Explanation	A user changed the password because the old password has expired.
Recommended action	No action is required.

LS_PWD_CHGPWD_FOR_AGEOUT

Message text	User [STRING] changed the password because it was about to expire.
Variable fields	$1: Username.
Severity level	4
Example	LS/4/LS_PWD_CHGPWD_FOR_AGEOUT: User aaa changed the password because it was about to expire.
Explanation	A user changed the password because the old password was about to expire.
Recommended action	No action is required.

LS_PWD_CHGPWD_FOR_COMPOSITION

Message text	User [STRING] changed the password because it had an invalid composition.
Variable fields	$1: Username.
Severity level	4
Example	LS/4/LS_PWD_CHGPWD_FOR_COMPOSITION: User aaa changed the password because it had an invalid composition.
Explanation	A user changed the password because it had an invalid composition.
Recommended action	No action is required.

LS_PWD_CHGPWD_FOR_FIRSTLOGIN

Message text	User [STRING] changed the password at the first login.
Variable fields	$1: Username.
Severity level	4
Example	LS/4/LS_PWD_CHGPWD_FOR_FIRSTLOGIN: User aaa changed the password at the first login.
Explanation	A user changed the password at the first login.
Recommended action	No action is required.

LS_PWD_CHGPWD_FOR_LENGTH

Message text	User [STRING] changed the password because it was too short.
Variable fields	$1: Username.
Severity level	4
Example	LS/4/LS_PWD_CHGPWD_FOR_LENGTH: User aaa changed the password because it was too short.
Explanation	A user changed the password because it was too short.
Recommended action	No action is required.

LS_PWD_FAILED2WRITEPASS2FILE

Message text	Failed to write the password records to file.
Variable fields	N/A
Severity level	4
Example	LS/4/LS_PWD_FAILED2WRITEPASS2FILE: Failed to write the password records to file.
Explanation	Failed to write the password records to file.
Recommended action	No action is required.

LS_PWD_MODIFY_FAIL

Message text	Admin [STRING] from [STRING] could not modify the password for user [STRING], because [STRING].
Variable fields	$1: Admin name. $2: IP address. $3: Username. $4: Failure reason: ¡ old password is incorrect. ¡ password is too short. ¡ password has not minimum different chars. ¡ invalid password composition. ¡ password has repeated chars. ¡ password contains username. ¡ password used already. ¡ password is in update-wait time.
Severity level	4
Example	LS/4/LS_PWD_MODIFY_FAIL: Admin admin from 1.1.1.1 could not modify the password for user user1, because old password is incorrect.
Explanation	An administrator failed to modify a user's password.
Recommended action	No action is required.

LS_PWD_MODIFY_SUCCESS

Message text	Admin [STRING] from [STRING] modify the password for user [STRING] successfully.
Variable fields	$1: Admin name. $2: IP address. $3: Username.
Severity level	6
Example	LS/6/LS_PWD_MODIFY_SUCCESS: Admin admin from 1.1.1.1 modify the password for user abc successfully.
Explanation	An administrator successfully modified a user's password.
Recommended action	No action is required.

LS_REAUTHEN_FAILURE

Message text	User [STRING] from [STRING] failed reauthentication.
Variable fields	$1: Username. $2: IP address.
Severity level	5
Example	LS/5/LS_REAUTHEN_FAILURE: User abcd from 1.1.1.1 failed reauthentication.
Explanation	A user failed reauthentication.
Recommended action	Check the old password.

LS_UPDATE_PASSWORD_FAIL

Message text	Failed to update the password for user [STRING].
Variable fields	$1: Username.
Severity level	4
Example	LS/4/LS_UPDATE_PASSWORD_FAIL: Failed to update the password for user abc.
Explanation	Failed to update the password for a user.
Recommended action	Check the file system for errors.

LS_USER_CANCEL

Message text	User [STRING] from [STRING] cancelled inputting the password.
Variable fields	$1: Username. $2: IP address.
Severity level	5
Example	LS/5/LS_USER_CANCEL: User 1 from 1.1.1.1 cancelled inputting the password.
Explanation	The user cancelled inputting the password or did not input the password in 90 seconds.
Recommended action	No action is required.

LS_USER_PASSWORD_EXPIRE

Message text	User [STRING]'s login idle timer timed out.
Variable fields	$1: Username.
Severity level	5
Example	LS/5/LS_USER_PASSWORD_EXPIRE: User 1's login idle timer timed out.
Explanation	The login idle time for a user expired.
Recommended action	No action is required.

LS_USER_ROLE_CHANGE

Message text	Admin [STRING] [STRING] the user role [STRING] for [STRING].
Variable fields	$1: Admin name. $2: Added/Deleted. $3: User role. $4: Username.
Severity level	4
Example	LS/4/LS_USER_ROLE_CHANGE: Admin admin add the user role network-admin for abcd.
Explanation	The administrator added a user role for a user.
Recommended action	No action is required.

LSM messages

This section contains LSM messages.

LSM_LABEL_CONFLICT

Message text	Label block reservation failed. Make sure the label range is available.
Variable fields	N/A
Severity level	5
Example	LSM/5/LSM_LABELBLOCK_ALLOCFAIL: Label block reservation failed. Make sure the label range is available.
Explanation	Failed to reserve labels in SRGBs or SRLB. Make sure the labels in the specified label ranges are available.
Recommended action	Modify the global SRGB, the SRGBs for IGPs, and the SRLB to ensure that labels in the specified label ranges are available.

LSM_SR_LABEL_CONFLICT

Message text	Protocol [STRING] assigned label ([STRING]) for prefix ([STRING]), which already has label ([STRING]) assigned by protocol [STRING].
Variable fields	$1: Routing protocol 1. $2: Label 1. $3: Prefix and the mask. $4: Label 2. $5: Routing protocol 2.
Severity level	4
Example	LSM/4/LSM_SR_LABEL_CONFLICT: Protocol ISIS assigned label (16000) to prefix (5.5.5.5/32), which already has label (17000) assigned by protocol OSPF.
Explanation	Two routing protocols running on the same SR node assigned different labels to the same prefix.
Recommended action	Perform one the following tasks: · Configure the routing protocols to assign the same label to the same prefix. · Remove one of the routing protocol process so only one routing protocol assigns labels to prefixes.

LSM_SR_PREFIX_CONFLICT

Message text	Label ([STRING]) for prefix ([STRING]) has been used by prefix ([STRING]).
Variable fields	$1: Label value. $2: Prefix 1 and the mask. $2: Prefix 2 and the mask.
Severity level	4
Example	LSM/4/LSM_SR_PREFIX_CONFLICT: The label(16700) for prefix(8.8.8.8/32) has been used by prefix(5.5.5.5/32).
Explanation	A label was assigned to two prefixes.
Recommended action	Assign a different label to one of the prefixes.

MAC messages

This section contains MAC messages.

MAC_DRIVER_ADD_ENTRY

Message text	Driver failed to add MAC address entry: MAC address=[STRING], VLAN=[UINT32], State=[UINT32], interface=[STRING].
Variable fields	$1: MAC address. $2: VLAN ID. $3: Entry type number. $4: Interface type and interface number.
Severity level	4
Example	MAC/4/MAC_DRIVER_ADD_ENTRY: Driver failed to add MAC address entry: MAC address=1-1-1, VLAN=1, State=2, interface=GigabitEthernet1/0/1.
Explanation	Failed to add a MAC address entry on an interface.
Recommended action	No action is required.

MAC_NOTIFICATION

Message text	Message format 1: MAC address [STRING] in VLAN [UNIT32] has moved from port [STRING] to port [STRING] for [UNIT32] times. Message format 2: MAC address [STRING] in VSI [STRING] has moved from [STRING] service-instance [UNIT32] to [STRING] service-instance [UNIT32] for [UNIT32] times.
Variable fields	Message format 1: $1: MAC address. $2: VLAN ID. $3: Interface name. $4: Interface name. $5: Number of MAC address moves. Message format 2: $1: MAC address. $2: VSI name. $3: Interface name. $4: Ethernet service instance ID. $5: Interface name. $6: Ethernet service instance ID. $7: Number of MAC address moves.
Severity level	4
Example	Message format 1: MAC/4/MAC_NOTIFICATION: MAC address 0000-0012-0034 in VLAN 500 has moved from port GE1/0/1 to port GE1/0/2 for 1 times Message format 2: MAC/4/MAC_NOTIFICATION: MAC address 0010-9400-0002 in VSI vpna has moved from Twenty-FiveGigE1/0/1 service-instance 40 to Twenty-FiveGigE1/0/3 service-instance 30 for 152499 times.
Explanation	A MAC address moved between two interfaces or Ethernet service instances.
Recommended action	No action is required.

MAC_TABLE_FULL_GLOBAL

Message text	The number of MAC address entries exceeded the maximum number [UINT32].
Variable fields	$1: Maximum number of MAC addresses.
Severity level	4
Example	MAC/4/MAC_TABLE_FULL_GLOBAL: The number of MAC address entries exceeded the maximum number 1024.
Explanation	The number of entries in the global MAC address table exceeded the maximum number supported by the table.
Recommended action	No action is required.

MAC_TABLE_FULL_PORT

Message text	The number of MAC address entries exceeded the maximum number [UINT32] for interface [STRING].
Variable fields	$1: Maximum number of MAC addresses. $2: Interface name.
Severity level	4
Example	MAC/4/MAC_TABLE_FULL_PORT: The number of MAC address entries exceeded the maximum number 1024 for interface GigabitEthernet2/0/32.
Explanation	The number of entries in the MAC address table for an interface exceeded the maximum number supported by the table.
Recommended action	No action is required.

MAC_TABLE_FULL_VLAN

Message text	The number of MAC address entries exceeded the maximum number [UINT32] in VLAN [UINT32].
Variable fields	$1: Maximum number of MAC addresses. $2: VLAN ID.
Severity level	4
Example	MAC/4/MAC_TABLE_FULL_VLAN: The number of MAC address entries exceeded the maximum number 1024 in VLAN 2.
Explanation	The number of entries in the MAC address table for a VLAN exceeded the maximum number supported by the table.
Recommended action	No action is required.

MAC_VLAN_LEARNLIMIT_NORESOURCE

Message text	The card does not have enough hardware resources to set MAC learning limit for VLAN [UINT16].
Variable fields	$1: VLAN ID.
Severity level	5
Example	MAC/5/MAC_VLAN_LEARNLIMIT_NORESOURCE: The card does not have enough hardware resources to set MAC learning limit for VLAN 100.
Explanation	Failed to set the MAC learning limit for a VLAN because the card does not have enough hardware resources.
Recommended action	No action is required.

MAC_VLAN_LEARNLIMIT_NOTSUPPORT

Message text	The card does not support setting MAC learning limit for VLAN [UINT16].
Variable fields	$1: VLAN ID.
Severity level	5
Example	MAC/5/ MAC_VLAN_LEARNLIMIT_NOTSUPPORT: The card does not support setting MAC learning limit for VLAN 100.
Explanation	MAC learning limit setting for a VLAN is not supported on the card.
Recommended action	No action is required.

MFIB messages

This section contains MFIB messages.

MFIB_MEM_ALERT

Message text	MFIB process received system memory alert [STRING] event.
Variable fields	$1: Type of the memory alert event.
Severity level	5
Example	MFIB/5/MFIB_MEM_ALERT: MFIB process receive system memory alert start event.
Explanation	The MFIB module received a memory alert event from the system.
Recommended action	1. Check the system memory to make sure the memory usage does not exceed the thresholds. 2. Release memory from memory-intensive modules.

MPLS messages

This section contains MPLS messages.

MPLS_HARD_RESOURCE_NOENOUGH

Message text	No enough hardware resource for MPLS.
Variable fields	N/A
Severity level	4
Example	MPLS/4/MPLS_HARD_RESOURCE_NOENOUGH: No enough hardware resource for MPLS.
Explanation	Hardware resources for MPLS were insufficient.
Recommended action	Check whether unnecessary LSPs had been generated. If yes, configure or modify the LSP generation policy, label advertisement policy, and label acceptance policy to filter out unnecessary LSPs.

MPLS_HARD_RESOURCE_RESTORE

Message text	Hardware resources for MPLS are restored.
Variable fields	N/A
Severity level	6
Example	MPLS/6/MPLS_HARD_RESOURCE_RESTORE: Hardware resources for MPLS are restored.
Explanation	Hardware resources for MPLS were restored.
Recommended action	No action is required.

MTLK messages

This section contains Monitor Link messages.

MTLK_UPLINK_STATUS_CHANGE

Message text	The uplink of monitor link group [UINT32] is [STRING].
Variable fields	$1: Monitor link group ID. $2: Monitor Link group status, up or down.
Severity level	6
Example	MTLK/6/MTLK_UPLINK_STATUS_CHANGE: The uplink of monitor link group 1 is up.
Explanation	The uplink of a monitor link group went up or down.
Recommended action	Troubleshoot the uplink when it fails.

ND messages

This section contains ND messages.

ND_CONFLICT

Message text	[STRING] is inconsistent.
Variable fields	$1: Configuration type: ¡ M_FLAG. ¡ O_FLAG. ¡ CUR_HOP_LIMIT. ¡ REACHABLE TIME. ¡ NS INTERVAL. ¡ MTU. ¡ PREFIX VALID TIME. ¡ PREFIX PREFERRED TIME.
Severity level	6
Example	ND/6/ND_CONFLICT: PREFIX VALID TIME is inconsistent
Explanation	The configuration information in the received router advertisement was not consistent with the configuration on the device. A message is sent if an inconsistency is detected.
Recommended action	Verify that the configurations on the device and the neighboring router are consistent.

ND_DUPADDR

Message text	Duplicate address: [STRING] on the interface [STRING].
Variable fields	$1: IPv6 address that is to be assigned to the interface. $2: Name of the interface.
Severity level	6
Example	ND/6/ND_DUPADDR: Duplicate address: 33::8 on the interface Vlan-interface9.
Explanation	The IPv6 address that was to be assigned to the interface is being used by another device.
Recommended action	Assign another IPv6 address to the interface.

ND_MAC_CHECK

Message text	Packet received on interface [STRING] was dropped because source MAC [STRING] was inconsistent with link-layer address [STRING].
Variable fields	$1: Receiving interface of the ND packet. $2: Source MAC address in the Ethernet frame header of the ND packet. $3: Source link-layer address in the ND packet.
Severity level	6
Example	ND/6/ND_MAC_CHECK: Packet received on interface Ethernet2/0/2 was dropped because source MAC 0002-0002-0001 was inconsistent with link-layer address 0002-0002-0002.
Explanation	The device dropped an ND packet because source MAC consistency check detected that the source MAC address and the source link-layer address in the packet are inconsistent.
Recommended action	Verify the validity of the ND packet originator.

ND_USER_DUPLICATE_IPV6ADDR

Message text	Detected a user IPv6 address conflict. New user (MAC [STRING], SVLAN [STRING], CVLAN [STRING]) on interface [STRING] and old user (MAC [STRING], SVLAN [STRING], CVLAN [STRING]) on interface [STRING] were using the same IPv6 address [IPV6ADDR].
Variable fields	$1: MAC address of the new user. $2: SVLAN of the new user. $3: CVLAN of the new user. $4: Name of the interface connected to the new user. $5: MAC address of the old user. $6: SVLAN of the old user. $7: CVLAN of the old user. $8: Name of the interface connected to the old user. $9: IPv6 address of the user.
Severity level	6
Example	ND/6/ND_USER_DUPLICATE_IPV6ADDR: Detected a user IPv6 address conflict. New user (MAC 0010-2100-01e1, SVLAN 100, CVLAN 10) on interface GigabitEthernet1/0/1 and old user (MAC 0120-1e00-0102, SVLAN 100, CVLAN 10) on interface GigabitEthernet1/0/1 were using the same IPv6 address 10::1.
Explanation	This message is sent when ND detects an IPv6 address conflict.
Recommended action	Examine IPv6 addresses of all endpoint users, locate the address conflict reason, and take actions to remove the conflict.

ND_USER_MOVE

Message text	Detected a user (IPv6 address [IPV6ADDR], MAC address [STRING]) moved to another interface. Before user move: interface [STRING], SVLAN [STRING], CVLAN [STRING]. After user move: interface [STRING], SVLAN [STRING], CVLAN [STRING].
Variable fields	$1: IPv6 address of the user. $2: MAC address of the user. $3: Interface name before the migration. $4: Old SVLAN of the user. $5: Old CVLAN of the user. $6: Interface name after the migration. $7: New SVLAN of the user. $8: New CVLAN of the user.
Severity level	6
Example	ND/6/ND_USER_MOVE: Detected a user (IPv6 address 10::1, MAC address 0010-2100-01e1) moved to another interface. Before user move: interface GigabitEthernet1/0/1, SVLAN 100, CVLAN 20. After user move: interface GigabitEthernet1/0/2, SVLAN 100, CVLAN 10.
Explanation	This message is sent when ND detects that a user accesses the network through another port.
Recommended action	Execute the display ipv6 nd user-move record command to verify that the migration is valid.

ND_USER_OFFLINE

Message text	Detected a user (IPv6 address [IPV6ADDR], MAC address [STRING]) was offline from interface [STRING].
Variable fields	$1: IPv6 address of the offline user. $2: MAC address of the offline user. $3: Name of the interface connected to the offline user.
Severity level	6
Example	ND/6/ND_USER_OFFLINE: Detected a user (IPv6 address 10::1, MAC address 0010-2100-01e1) was offline from interface GigabitEthernet1/0/1.
Explanation	This message is sent when ND detects a user offline event.
Recommended action	No action is required.

ND_USER_ONLINE

Message text	Detected a user (IPv6 address [IPV6ADDR], MAC address [STRING]) was online on interface [STRING].
Variable fields	$1: IPv6 address of the online user. $2: MAC address of the online user. $3: Name of the interface connected to the online user.
Severity level	6
Example	ND/6/ND_USER_ONLINE: Detected a user (IPv6 address 10::1, MAC address 0010-2100-01e1) was online on interface GigabitEthernet1/0/1.
Explanation	This message is sent when ND detects a user online event.
Recommended action	Verify the validity of the online user.

NETCONF messages

This section contains NETCONF messages.

CLI

Message text	User ([STRING], [STRING][STRING]) performed an CLI operation: [STRING] operation result=[STRING][STRING]
Variable fields	$1: Username or user line type. · If scheme login authentication was performed for the user, this field displays the username. · If no login authentication was performed or password authentication was performed, this field displays the user line type, such as VTY. $2: User IP address or user line type and relative number. · For a Telnet or SSH user, this field displays the IP address of the user. · For a user who logged in through the console or AUX port, this field displays the user line type and the relative line number, such as CON0. $3: ID of the NETCONF session. This field is not displayed for Web and RESTful sessions. $4: Message ID of the NETCONF request. This field is not displayed for Web and RESTful sessions. $5: Operation result, Succeeded or Failed. $6: Cause for an operation failure. This field is displayed only if the failure is caused by a known reason.
Severity level	6
Example	XMLSOAP/6/CLI: -MDC=1; User (test, 169.254.5.222, session ID=1) performed an CLI operation: message ID=101, operation result=Succeeded.
Explanation	After a CLI command is executed by using NETCONF, the device outputs this message to show the operation result.
Recommended action	No action is required.

EDIT-CONFIG

Message text	User ([STRING], [STRING], session ID [UINT16]) performed an edit-config operation: message ID=[STRING], operation result=Succeeded. Or: User ([STRING], [STRING], session ID [UINT16]) performed an edit-config operation: message ID=[STRING], operation result=Failed. [STRING] Or: User ([STRING], [STRING], session ID [UINT16]) performed an edit-config operation: message ID=[STRING], operation result=Failed, XPath=[STRING], error message=[STRING].
Variable fields	$1: Username or user line type. ¡ If scheme login authentication was performed for the user, this field displays the username. ¡ If no login authentication was performed or password authentication was performed, this field displays the user line type, such as VTY. $2: User IP address or user line type and relative number. ¡ For a Telnet or SSH user, this field displays the IP address of the user. ¡ For a user who logged in through the console or AUX port, this field displays the user line type and the relative line number, such as CON0. $3: ID of the NETCONF session. $4: Message ID of the NETCONF request. This field is not displayed if the request does not have a message ID. $5: Error information or XPath expression of the erroneous line. ¡ If the verbose keyword was not specified and the error reason was known, this field displays the detailed error information. ¡ If the verbose keyword was specified, this field displays the XPath expression of the erroneous line. $6: Error information. This field is displayed only when the verbose keyword was specified.
Severity level	6
Example	XMLSOAP/6/EDIT-CONFIG: -MDC=1; User (test, 192.168.100.20, session ID 1) performed an edit-config operation: message ID=101, operation result=Succeeded.
Explanation	A NETCONF client deployed settings by using the <edit-config> operation. An <edit-config> operation can contain multiple settings. The device might output multiple log messages at a time.
Recommended action	No action is required.

REPLY

Message text	Sent a NETCONF reply to the client: Session ID=[UINT16], Content=[STRING]. Or: Sent a NETCONF reply to the client: Session ID=[UINT16], Content (partial)=[STRING].
Variable fields	$1: ID of the NETCONF session. Before a session is established, this field displays a hyphen (-). $2: NETCONF packet sent by the device to the NETCONF client.
Severity level	7
Example	XMLSOAP/7/REPLY: -MDC=1; Sent a NETCONF reply to the client: Session ID=2, Content=</env:Body></env:Envelope>.
Explanation	The device sent a NETCONF packet to the NETCONF client to identify the status of NETCONF. If the NETCONF packet contains a lot of contents, the device might output multiple log messages, each with the partial flat.
Recommended action	No action is required.

NETCONF_MSG_DEL

Message text	A NETCONF message was dropped. Reason: Packet size exceeded the upper limit.
Variable fields	None
Severity level	7
Example	NETCONF/7/NETCONF_MSG_DEL: A NETCONF message was dropped. Reason: Packet size exceeded the upper limit.
Explanation	The system dropped a NETCONF request message that was received from a NETCONF over SSH client or at the XML view. The reason is that the message size exceeded the upper limit.
Recommended action	1. Reduce the size of the request message. For example, delete blank spaces, carriage returns, and tab characters. 2. Contact H3C Support to segment the request message and then re-encapsulate the segments before sending them to the device.

ROW-OPERATION

Message text	User ([STRING], [STRING][STRING])[STRING] operation=[STRING] [STRING] [STRING], result=[STRING]. No attributes. Or: User ([STRING], [STRING],[STRING]),[STRING] operation=[STRING] [STRING] [STRING], result=[STRING]. Attributes: [STRING].
Variable fields	$1: Username or user line type. ¡ If scheme login authentication was performed for the user, this field displays the username. ¡ If no login authentication was performed or password authentication was performed, this field displays the user line type, such as VTY. $2: User IP address or user line type and relative number. ¡ For a Telnet or SSH user, this field displays the IP address of the user. ¡ For a user who logged in through the console or AUX port, this field displays the user line type and the relative line number, such as CON0. $3: ID of the NETCONF session. This field is not displayed if the session does not have a session ID. $4: Message ID of the NETCONF request. This field is not displayed if the request does not have a message ID. $5: Name of a NETCONF row operation. $6: Module name and table name. $7: Index information. If there are multiple indexes, this field uses a comma as the delimiter. This field is displayed only when there are indexes. $8: Operation result, Succeeded or Failed. $9: Attribute column information. This field is displayed only when the operation configures an attribute column.
Severity level	6
Example	XMLSOAP/6/EDIT-CONFIG: User (test, 192.168.100.20, session ID 1), message ID=1, operation=create Ifmgr/Interfaces (IfIndex="GigabitEthernet1/0/1"), result=Succeeded. Attributes: Description="This is Desc1", AdminDown=1, Speed=1.
Explanation	The device outputs this log message for each row operation for an <action> or <edit-config> operation.
Recommended action	No action is required.

THREAD

Message text	Maximum number of NETCONF threads already reached.
Variable fields	N/A
Severity level	3
Example	XMLCFG/3/THREAD: -MDC=1; Maximum number of NETCONF threads already reached.
Explanation	The number of NETCONF threads already reached the upper limit.
Recommended action	Please try again later.

NQA messages

This section contains NQA messages.

NQA_LOG_UNREACHABLE

Message text	Server [STRING] unreachable.
Variable fields	$1: IP address of the NQA server.
Severity level	6
Example	NQA/6/NQA_LOG_UNREACHABLE: Server 192.168.30.117 unreachable.
Explanation	An unreachable server was detected.
Recommended action	Check the network environment.

NQA_PACKET_OVERSIZE

Message text	NQA entry ([STRING]-[STRING]): The payload size exceeds 65503 bytes, and all IPv6 UDP probe packets will be dropped by the NQA server.
Variable fields	$1: Admin name of the NQA operation. $2: Operation tag of the NQA operation.
Severity level	6
Example	NQA/6/NQA_PACKET_OVERSIZE: NQA entry (1-1): The payload size exceeds 65503 bytes, and all IPv6 UDP probe packets will be dropped by the NQA server.
Explanation	A packet oversize warning message was sent when the NQA client attempted to send to an IPv6 NQA server UDP probe packets with the data size exceeding 65503 bytes. The message indicates that the oversized probe packets will be dropped by the NQA server.
Recommended action	Modify the probe packet data size for the NQA operation.

NQA_SCHEDULE_FAILURE

Message text	NQA entry ([ STRING ]- [ STRING ]): Failed to start the scheduled NQA operation because port [ STRING] used by the operation is not available.
Variable fields	$1: Admin name of the NQA operation. $2: Operation tag of the NQA operation. $3: Port number.
Severity level	6
Example	NQA/6/NQA_SCHEDULE_FAILURE: NQA entry (admin-tag): Failed to start the scheduled NQA operation because port 10000 used by the operation is not available.
Explanation	Failed to start a scheduled NQA operation because the port number used by the operation is not available.
Recommended action	Change the port number of the NQA operation or disable the service that uses the port number.

NQA_SERVER_PORT_UNAVAILABLE

Message text	Failed to enable the NQA server because listening port [STRING] is not available.
Variable fields	$1: Port number.
Severity level	6
Example	NQA/6/NQA_SEVER_PORT_UNAVAILABLE: Failed to enable the NQA server because listening port 10000 is not available.
Explanation	Failed to enable the NQA server because the port number specified for the listening service is not available.
Recommended action	Change the port number of the listening service or disable the service that uses the port number.

NQA_SERVER_ADDR_UNAVAILABLE

Message text	Failed to enable the NQA server because the listening service's IP address [STRING] is not available.
Variable fields	$1: IP address of the listening service.
Severity level	6
Example	NQA/6/NQA_SEVER_ADDR_UNAVAILABLE: Failed to enable the NQA server because the listening service's IP address 192.168.10.100 is not available.
Explanation	Failed to enable the NQA server because the listening service's IP address is not specified or the server port that uses the specified IP address is down.
Recommended action	Verify that the IP address specified for the listening service is the IP address of a local interface on the NQA server and that the local interface in up.

NTP messages

This section contains NTP messages.

NTP_CLOCK_CHANGE

Message text	System clock changed from [STRING] to [STRING], the NTP server's IP address is [STRING].
Variable fields	$1: Time before synchronization. $2: Time after synchronization. $3: IP address.
Severity level	5
Example	NTP/5/NTP_CLOCK_CHANGE: System clock changed from 02:12:58 12/28/2012 to 02:29:12 12/28/2012, the NTP server's IP address is 192.168.30.116.
Explanation	The NTP client has synchronized its time to the NTP server.
Recommended action	No action is required.

NTP_LEAP_CHANGE

Message text	System Leap Indicator changed from [UINT32] to [UINT32] after clock update.
Variable fields	$1: Original Leap Indicator. $2: Current Leap Indicator.
Severity level	5
Example	NTP/5/NTP_LEAP_CHANGE: System Leap Indicator changed from 00 to 01 after clock update.
Explanation	The system Leap Indicator changed. For example, the NTP status changed from unsynchronized to synchronized. 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_SOURCE_CHANGE

Message text	NTP server's IP address changed from [STRING] to [STRING].
Variable fields	$1: IP address of the original time source. $2: IP address of the new time source.
Severity level	5
Example	NTP/5/NTP_SOURCE_CHANGE: NTP server's IP address changed from 1.1.1.1 to 1.1.1.2.
Explanation	The system changed the time source.
Recommended action	No action is required.

NTP_SOURCE_LOST

Message text	Lost synchronization with NTP server with IP address [STRING].
Variable fields	$1: IP address.
Severity level	5
Example	NTP/5/NTP_SOURCE_LOST: Lost synchronization with NTP server with IP address 1.1.1.1.
Explanation	The clock source of the NTP association is in unsynchronized state or it is unreachable.
Recommended action	3. Verify the NTP server and network connection. 4. For NTP server failures: ¡ Use the ntp-service unicast-server command to specify a new NTP server. ¡ Use the ntp-service multicast-client command to configure the device to operate in NTP multicast client mode and receive NTP multicast packets from a new NTP server. 5. If the problem persists, contract H3C Support.

NTP_STRATUM_CHANGE

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

OFP messages

This section contains OpenFlow messages.

OFP_ACTIVE

Message text	Activate openflow instance [UINT16].
Variable fields	$1: Instance ID.
Severity level	5
Example	OFP/5/OFP_ACTIVE: Activate openflow instance 1.
Explanation	A command is received from comsh to activate an OpenFlow instance.
Recommended action	No action is required.

OFP_ACTIVE_FAILED

Message text	Failed to activate instance [UINT16].
Variable fields	$1: Instance ID.
Severity level	4
Example	OFP/4/OFP_ACTIVE_FAILED: Failed to activate instance 1.
Explanation	An OpenFlow instance cannot be activated.
Recommended action	No action is required.

OFP_CONNECT

Message text	Openflow instance [UINT16], controller [CHAR] is [STRING].
Variable fields	$1: Instance ID. $2: Controller ID. $3: Connection status: connected or disconnected.
Severity level	5
Example	OFP/5/OFP_CONNECT: Openflow instance 1, controller 0 is connected.
Explanation	The connection status with a controller is changed in an OpenFlow instance.
Recommended action	No action is required.

OFP_FAIL_OPEN

Message text	Openflow instance [UINT16] is in fail [STRING] mode.
Variable fields	$1: Instance ID. $2: Connection interruption mode: secure or standalone.
Severity level	5
Example	OFP/5/OFP_FAIL_OPEN: Openflow instance 1 is in fail secure mode.
Explanation	An activated instance cannot connect to any controller or is disconnected from all controllers. The connection interrupt mode is also displayed.
Recommended action	No action is required.

OFP_FLOW_ADD

Message text	Openflow instance [UINT16] controller [CHAR]: add flow entry [UINT32], xid 0x[HEX], cookie 0x[HEX], table id [CHAR].
Variable fields	$1: Instance ID. $2: Controller ID. $3: Rule ID. $4: XID. $5: Cookie of the flow entry. $6: Table ID.
Severity level	5
Example	OFP/5/OFP_FLOW_ADD: Openflow instance 1 controller 0: add flow entry 1, xid 0x1, cookie 0x0, table id 0.
Explanation	A flow entry is to be added to a flow table, according to a flow table modification message that has passed the packet check.
Recommended action	No action is required.

OFP_FLOW_ADD_DUP

Message text	Openflow instance [UINT16] controller [CHAR]: add duplicate flow entry [UINT32], xid 0x[HEX], cookie 0x[HEX], table id [CHAR].
Variable fields	$1: Instance ID. $2: Controller ID. $3: Rule ID. $4: XID. $5: Cookie. $6: Table ID.
Severity level	5
Example	OFP/5/OFP_FLOW_ADD_DUP: Openflow instance 1 controller 0: add duplicate flow entry 1, xid 0x1, cookie 0x1, table id 0.
Explanation	A duplicate flow entry was added.
Recommended action	No action is required.

OFP_FLOW_ADD_FAILED

Message text	Openflow instance [UINT16] controller [CHAR]: failed to add flow entry [UINT32],table id [CHAR],because of insufficient resources.
Variable fields	$1: Instance ID. $2: Controller ID. $3: Rule ID. $4: Table ID.
Severity level	4
Example	OFP/4/OFP_FLOW_ADD_FAILED: Openflow instance 1 controller 0: failed to add flow entry 641,table id 0,because of insufficient resources.
Explanation	A flow entry failed to be added because of insufficient resources.
Recommended action	No action is required.

OFP_FLOW_ADD_FAILED

Message text	Openflow instance [UINT16] controller [CHAR]: failed to add flow entry [UINT32], table id [CHAR].
Variable fields	$1: Instance ID. $2: Controller ID. $3: Rule ID. $4: Table ID.
Severity level	4
Example	OFP/4/OFP_FLOW_ADD_FAILED: Openflow instance 1 controller 0: failed to add flow entry1, table id 0.
Explanation	Failed to add a flow entry.
Recommended action	No action is required.

OFP_FLOW_ADD_TABLE_MISS

Message text	Openflow instance [UINT16] controller [CHAR]: add table miss flow entry, xid 0x[HEX], cookie 0x[HEX], table id [CHAR].
Variable fields	$1: Instance ID. $2: Controller ID. $3: XID. $4: Cookie of the flow entry. $5: Table ID.
Severity level	5
Example	OFP/5/OFP_FLOW_ADD_TABLE_MISS: Openflow instance 1 controller 0: add table miss flow entry, xid 0x1, cookie 0x0, table id 0.
Explanation	A table-miss flow entry is to be added to a flow table, according to a flow table modification message that has passed the packet check.
Recommended action	No action is required.

OFP_FLOW_ADD_TABLE_MISS_FAILED

Message text	Openflow instance [UINT16] controller [CHAR]: failed to add table miss flow entry, table id [CHAR].
Variable fields	$1: Instance ID. $2: Controller ID. $3: Table ID.
Severity level	4
Example	OFP/4/OFP_FLOW_ADD_TABLE_MISS_FAILED: Openflow instance 1 controller 0: failed to add table miss flow entry, table id 0.
Explanation	Failed to add a table-miss flow entry.
Recommended action	No action is required.

OFP_FLOW_DEL

Message text	Openflow instance [UINT16] controller [CHAR]: delete flow entry, xid 0x[HEX], cookie 0x[HEX], table id [STRING].
Variable fields	$1: Instance ID. $2: Controller ID. $3: XID. $4: Cookie of the flow entry. $5: Table ID.
Severity level	5
Example	OFP/5/OFP_FLOW_DEL: Openflow instance 1 controller 0: delete flow entry, xid 0x1, cookie 0x0, table id 0.
Explanation	A list of flow entries are to be deleted, according to a flow table modification message that has passed the packet check.
Recommended action	No action is required.

OFP_FLOW_DEL_TABLE_MISS

Message text	Openflow instance [UINT16] controller [CHAR]: delete table miss flow entry, xid 0x[HEX], cookie 0x[HEX], table id [STRING].
Variable fields	$1: Instance ID. $2: Controller ID. $3: XID. $4: Cookie of the flow entry. $5: Table ID.
Severity level	5
Example	OFP/5/OFP_FLOW_DEL_TABLE_MISS: Openflow instance 1 controller 0: delete table miss flow entry, xid 0x1, cookie 0x0, table id 0.
Explanation	A list of table-misses flow entries are to be deleted, according to a flow table modification message that has passed the packet check.
Recommended action	No action is required.

OFP_FLOW_DEL_TABLE_MISS_FAILED

Message text	Openflow instance [UINT16] controller [CHAR]: failed to delete table miss flow entry, table id [STRING].
Variable fields	$1: Instance ID. $2: Controller ID. $3: Table ID.
Severity level	4
Example	OFP/4/OFP_FLOW_DEL_TABLE_MISS_FAILED: Openflow instance 1 controller 0: failed to delete table miss flow entry, table id 0.
Explanation	Failed to delete a table-miss flow entry.
Recommended action	No action is required.

OFP_FLOW_MOD

Message text	Openflow instance [UINT16] controller [CHAR]: modify flow entry, xid 0x[HEX], cookie 0x[HEX], table id [CHAR].
Variable fields	$1: Instance ID. $2: Controller ID. $3: XID. $4: Cookie of the flow entry. $5: Table ID.
Severity level	5
Example	OFP/5/OFP_FLOW_MOD: Openflow instance 1 controller 0: modify flow entry, xid 0x1, cookie 0x0, table id 0.
Explanation	A list of flow entries are to be modified, according to a flow table modification message that has passed the packet check.
Recommended action	No action is required.

OFP_FLOW_MOD_FAILED

Message text	Openflow instance [UINT16] controller [CHAR]: failed to modify flow entry, table id [CHAR].
Variable fields	$1: Instance ID. $2: Controller ID. $3: Table ID.
Severity level	4
Example	OFP/4/OFP_FLOW_MOD_FAILED: Openflow instance 1 controller 0: failed to modify flow entry, table id 0.
Explanation	Failed to modify a flow entry.
Recommended action	The controller must retry to modify the flow entry. If the flow entry still cannot be modified, the controller will delete it.

OFP_FLOW_MOD_TABLE_MISS

Message text	Openflow instance [UINT16] controller [CHAR]: modify table miss flow entry, xid 0x[HEX], cookie 0x[HEX], table id [CHAR].
Variable fields	$1: Instance ID. $2: Controller ID. $3: XID. $4: Cookie of the flow entry. $5: Table ID.
Severity level	5
Example	OFP/5/OFP_FLOW_MOD_TABLE_MISS: Openflow instance 1 controller 0: modify table miss flow entry, xid 0x1, cookie 0x0, table id 0.
Explanation	A list of flow entries are to be modified, according to a flow table modification message that has passed the packet check.
Recommended action	No action is required.

OFP_FLOW_MOD_TABLE_MISS_FAILED

Message text	Openflow instance [UINT16] controller [CHAR]: failed to modify table miss flow entry, table id [CHAR].
Variable fields	$1: Instance ID. $2: Controller ID. $3: Table ID.
Severity level	4
Example	OFP/4/OFP_FLOW_MOD_TABLE_MISS_FAILED: Openflow instance 1 controller 0: failed to modify table miss flow entry, table id 0.
Explanation	Failed to modify a table-miss flow entry.
Recommended action	The controller must retry to modify the table-miss flow entry. If the entry still cannot be modified, the controller will delete it.

OFP_FLOW_RMV_GROUP

Message text	The flow entry [UINT32] in table [CHAR] of instance [UINT16] was deleted with a group_mod message.
Variable fields	$1: Rule ID. $2: Table ID. $3: Instance ID.
Severity level	5
Example	OFP/5/OFP_FLOW_RMV_GROUP: The flow entry 1 in table 0 of instance 1 was deleted with a group_mod message.
Explanation	A flow entry was deleted due to a group modification message.
Recommended action	No action is required.

OFP_FLOW_RMV_HARDTIME

Message text	The flow entry [UINT32] in table [CHAR] of instance [UINT16] was deleted because of a hard-time expiration.
Variable fields	$1: Rule ID. $2: Table ID. $3: Instance ID.
Severity level	5
Example	OFP/5/OFP_FLOW_RMV_HARDTIME: The flow entry 1 in table 0 of instance 1 was deleted because of a hard-time expiration.
Explanation	A flow entry was deleted because of a hard time expiration.
Recommended action	No action is required.

OFP_FLOW_RMV_IDLETIME

Message text	The flow entry [UINT32] in table [CHAR] of instance [UINT16] was deleted because of an idle-time expiration.
Variable fields	$1: Rule ID. $2: Table ID. $3: Instance ID.
Severity level	5
Example	OFP/5/OFP_FLOW_RMV_IDLETIME: The flow entry 1 in table 0 of instance 1 was deleted because of an idle-time expiration.
Explanation	A flow entry was deleted because of an idle time expiration.
Recommended action	No action is required.

OFP_FLOW_RMV_METER

Message text	The flow entry [UINT32] in table [CHAR] of instance [UINT16] was deleted with a meter_mod message.
Variable fields	$1: Rule ID. $2: Table ID. $3: Instance ID.
Severity level	5
Example	OFP/5/OFP_FLOW_RMV_GROUP: The flow entry 1 in table 0 of instance1 was deleted with a meter_mod message.
Explanation	A flow entry was deleted due to a meter modification message.
Recommended action	No action is required.

OFP_FLOW_UPDATE_FAILED

Message text	OpenFlow instance [UINT16] table [CHAR]: failed to update or synchronize flow entry [UINT32].
Variable fields	$1: Instance ID. $2: Table ID. $3: Flow entry ID.
Severity level	4
Example	OFP/4/OFP_FLOW_SMOOTH_FAILED: OpenFlow instance 1 table 0: failed to update or synchronize flow entry 10000.
Explanation	When an active/standby switchover occurred, the new active MPU failed to update flow entries. When a new interface card was installed on the device, the interface card failed to synchronize flow entries from the MPUs. When a master/subordinate switchover occurred in an IRF fabric, the new master device failed to update flow entries. When new member devices joined an IRF fabric, the new member devices failed to synchronize flow entries from the master device.
Recommended action	Delete the flow entries that fail to be deployed.

OFP_GROUP_ADD

Message text	Openflow instance [UINT16] controller [CHAR]: add group [STRING], xid 0x[HEX].
Variable fields	$1: Instance ID. $2: Controller ID. $3: Group ID. $4: XID.
Severity level	5
Example	OFP/5/OFP_GROUP_ADD: Openflow instance 1 controller 0: add group 1, xid 0x1.
Explanation	A group entry is to be added to a group table, according to a group table modification message that has passed the packet check.
Recommended action	No action is required.

OFP_GROUP_ADD_FAILED

Message text	Openflow instance [UINT16] controller [CHAR]: failed to add group [STRING].
Variable fields	$1: Instance ID. $2: Controller ID. $3: Group ID.
Severity level	4
Example	OFP/4/OFP_GROUP_ADD_FAILED: Openflow Instance 1 controller 0: failed to add group 1.
Explanation	Failed to add a group entry.
Recommended action	No action is required.

OFP_GROUP_DEL

Message text	Openflow instance [UINT16] controller [CHAR]: delete group [STRING], xid [HEX].
Variable fields	$1: Instance ID. $2: Controller ID. $3: Group ID. $4: XID.
Severity level	5
Example	OFP/5/OFP_GROUP_DEL: Openflow instance 1 controller 0: delete group 1, xid 0x1.
Explanation	A group entry is to be deleted, according to a group table modification message that has passed the packet check.
Recommended action	No action is required.

OFP_GROUP_MOD

Message text	Openflow instance [UINT16] controller [CHAR]: modify group [STRING], xid 0x[HEX].
Variable fields	$1: Instance ID. $2: Controller ID. $3: Group ID. $4: XID.
Severity level	5
Example	OFP/5/OFP_GROUP_MOD: Openflow instance 1 controller 0: modify group 1, xid 0x1.
Explanation	A group entry is to be modified, according to a group table modification message that has passed the packet check.
Recommended action	No action is required.

OFP_GROUP_MOD_FAILED

Message text	Openflow instance [UINT16] controller [CHAR]: failed to modify group [STRING].
Variable fields	$1: Instance ID. $2: Controller ID. $3: Group ID.
Severity level	4
Example	OFP/4/OFP_GROUP_MOD_FAILED: Openflow instance 1 controller 0: failed to modify group 1.
Explanation	Failed to modify a group entry.
Recommended action	The controller must retry to modify the group. If the group still cannot be modified, the controller will delete it.

OFP_METER_ADD

Message text	Openflow instance [UINT16] controller [CHAR]: add meter [STRING], xid 0x[HEX].
Variable fields	$1: Instance ID. $2: Controller ID. $3: Meter ID. $4: XID.
Severity level	5
Example	OFP/5/OFP_METER_ADD: Openflow instance 1 controller 0: add meter 1, xid 0x1.
Explanation	A meter entry is to be added to a meter table.
Recommended action	No action is required.

OFP_METER_ADD_FAILED

Message text	Openflow instance [UINT16] controller [CHAR]: failed to add meter [STRING].
Variable fields	$1: Instance ID. $2: Controller ID. $3: Meter ID.
Severity level	4
Example	OFP/4/OFP_METER_ADD_FAILED: Openflow Instance 1 controller 0: failed to add meter 1.
Explanation	Failed to add a meter entry.
Recommended action	No action is required.

OFP_METER_DEL

Message text	Openflow instance [UINT16] controller [CHAR]: delete meter [STRING], xid 0x[HEX].
Variable fields	$1: Instance ID. $2: Controller ID. $3: Meter ID. $4: XID.
Severity level	5
Example	OFP/5/OFP_METER_DEL: Openflow instance 1 controller 0: delete meter 1, xid 0x1.
Explanation	A meter entry is to be deleted, according to a meter table modification message that has passed the packet check.
Recommended action	No action is required.

OFP_METER_MOD

Message text	Openflow instance [UINT16] controller [CHAR]: modify meter [STRING], xid 0x[HEX].
Variable fields	$1: Instance ID. $2: Controller ID. $3: Meter ID. $4: XID.
Severity level	5
Example	OFP/5/OFP_METER_MOD: Openflow Instance 1 controller 0: modify meter 1, xid 0x1.
Explanation	A meter entry is to be modified, according to a meter table modification message that has passed the packet check.
Recommended action	No action is required.

OFP_METER_MOD_FAILED

Message text	Openflow instance [UINT16] controller [CHAR]: failed to modify meter [STRING].
Variable fields	$1: Instance ID. $2: Controller ID. $3: Meter ID.
Severity level	4
Example	OFP/4/OFP_METER_MOD_FAILED: Openflow instance 1 controller 0: failed to modify meter 1.
Explanation	Failed to modify a meter entry.
Recommended action	The controller must retry to modify the meter entry. If the meter entry still cannot be modified, the controller will delete it.

OFP_MISS_RMV_GROUP

Message text	The table-miss flow entry in table [CHAR] of instance [UINT16] was deleted with a group_mod message.
Variable fields	$1: Table ID. $2: Instance ID.
Severity level	5
Example	OFP/5/OFP_MISS_RMV_GROUP: The table-miss flow entry in table 0 of instance 1 was deleted with a group_mod message.
Explanation	The table-miss flow entry was deleted due to a group modification message.
Recommended action	No action is required.

OFP_MISS_RMV_HARDTIME

Message text	The table-miss flow entry in table [CHAR] of instance [UINT16] was deleted because of a hard-time expiration.
Variable fields	$1: Table ID. $2: Instance ID.
Severity level	5
Example	OFP/5/OFP_MISS_RMV_HARDTIME: The table-miss flow entry in table 0 of instance 1 was deleted because of a hard-time expiration.
Explanation	The table-miss flow entry was deleted because of a hard time expiration.
Recommended action	No action is required.

OFP_MISS_RMV_IDLETIME

Message text	The table-miss flow entry in table [CHAR] of instance [UINT16] was deleted because of an idle-time expiration.
Variable fields	$1: Table ID. $2: Instance ID.
Severity level	5
Example	OFP/5/OFP_MISS_RMV_IDLETIME: The table-miss flow entry in table 0 of instance 1 was deleted because of an idle-time expiration.
Explanation	The table-miss flow entry was deleted because of an idle time expiration.
Recommended action	No action is required.

OFP_MISS_RMV_METER

Message text	The table-miss flow entry in table [CHAR] of instance [UINT16] was deleted with a meter_mod message.
Variable fields	$1: Table ID. $2: Instance ID.
Severity level	5
Example	OFP/5/OFP_MISS_RMV_METER: The table-miss flow entry in table 0 of instance 1 was deleted with a meter_mod message.
Explanation	The table-miss flow entry was deleted due to a meter modification message.
Recommended action	No action is required.

OFP_RADARDETECTION

Message text	inIfIndex = [UINT32], packageId = [UINT16], innerTTL = [CHAR], outerTTL = [CHAR].
Variable fields	$1: Index of the ingress port of the packet. $2: Packet identifier. $3: Time To Live value in the inner IP header of the packet. $4: Time To Live value in the outer IP header of the packet.
Severity level	5
Example	OFP/5/OFP_RADARDETECTION: inIfIndex = 1, packageId = 1, innerTTL = 128, outerTTL = 128.
Explanation	A packet used for radar detection or VM simulation was received.
Recommended action	No action is required.

OPTMOD messages

This section contains transceiver module messages.

BIAS_HIGH

Message text	[STRING]: Bias current is high.
Variable fields	$1: Interface type and number.
Severity level	2
Example	OPTMOD/2/BIAS_HIGH: GigabitEthernet1/0/1: Bias current is high.
Explanation	The bias current of the transceiver module exceeded the high threshold.
Recommended action	1. Execute the display transceiver diagnosis interface command to verify that the bias current of the transceiver module has exceeded the high threshold. 2. Execute the display transceiver alarm interface command to verify that a high bias current alarm for the transceiver module has been generated and not cleared. 3. Replace the transceiver module.

BIAS_LOW

Message text	[STRING]: Bias current is low.
Variable fields	$1: Interface type and number.
Severity level	5
Example	OPTMOD/5/BIAS_LOW: GigabitEthernet1/0/1: Bias current is low.
Explanation	The bias current of the transceiver module went below the low threshold.
Recommended action	1. Execute the display transceiver diagnosis interface command to verify that the bias current of the transceiver module is below the low threshold. 2. Execute the display transceiver alarm interface command to verify that a low bias current alarm for the transceiver module has been generated and not cleared. 3. Replace the transceiver module.

BIAS_NORMAL

Message text	[STRING]: Bias current is normal.
Variable fields	$1: Interface type and number.
Severity level	5
Example	OPTMOD/5/BIAS_NORMAL: GigabitEthernet1/0/1: Bias current is normal.
Explanation	The bias current of the transceiver module returned to the acceptable range.
Recommended action	No action is required.

CFG_ERR

Message text	[STRING]: Transceiver type and port configuration mismatched.
Variable fields	$1: Interface type and number.
Severity level	3
Example	OPTMOD/3/CFG_ERR: GigabitEthernet1/0/1: Transceiver type and port configuration mismatched.
Explanation	The transceiver module type does not match the port configurations.
Recommended action	Check for the transceiver module type and the current port configurations. If they mismatch, replace the transceiver module or update the port configurations.

CHKSUM_ERR

Message text	[STRING]: Transceiver information checksum error.
Variable fields	$1: Interface type and number.
Severity level	5
Example	OPTMOD/5/CHKSUM_ERR: GigabitEthernet1/0/1: Transceiver information checksum error .
Explanation	Checksum verification on the register information on the transceiver module failed.
Recommended action	Replace the transceiver module, or contact H3C Support.

FIBER_SFP MODULE_INVALID

Message text	[STRING]: This transceiver module is not compatible with the interface card. HP does not guarantee the correct operation of the transceiver module. The transceiver module will be invalidated in [UINT32] days. Please replace it with a compatible one as soon as possible.
Variable fields	$1: Interface type and number. $2: Number of days that the transceiver module will be invalid.
Severity level	4
Example	OPTMOD/4/FIBER_SFPMODULE_INVALID: GigabitEthernet1/0/1: This transceiver module is not compatible with the interface card. HP does not guarantee the correct operation of the transceiver module. The transceiver module will be invalidated in 3 days. Please replace it with a compatible one as soon as possible.
Explanation	The transceiver module is not compatible with the interface card.
Recommended action	Replace the transceiver module.

FIBER_SFPMODULE_NOWINVALID

Message text	[STRING]: This is not a supported transceiver for this platform. HP does not guarantee the normal operation or maintenance of unsupported transceivers. Please review the platform datasheet on the HP web site or contact your HP sales rep for a list of supported transceivers.
Variable fields	$1: Interface type and number.
Severity level	4
Example	OPTMOD/4/FIBER_SFPMODULE_NOWINVALID: GigabitEthernet1/0/1: This is not a supported transceiver for this platform. HP does not guarantee the normal operation or maintenance of unsupported transceivers. Please review the platform datasheet on the HP web site or contact your HP sales rep for a list of supported transceivers.
Explanation	The system does not support the transceiver module.
Recommended action	Replace the transceiver module.

IO_ERR

Message text	[STRING]: The transceiver information I/O failed.
Variable fields	$1: Interface type and number.
Severity level	5
Example	OPTMOD/5/IO_ERR: GigabitEthernet1/0/1: The transceiver information I/O failed.
Explanation	The device failed to access the register information of the transceiver module.
Recommended action	Execute the display transceiver diagnosis interface and display transceiver alarm interface commands. If both commands fail to be executed, the transceiver module is faulty. Replace the transceiver module.

MOD_ALM_OFF

Message text	[STRING]: [STRING] was removed.
Variable fields	$1: Interface type and number. $2: Fault type.
Severity level	5
Example	OPTMOD/5/MOD_ALM_OFF: GigabitEthernet1/0/1: Module_not_ready was removed..
Explanation	A fault was removed from the transceiver module.
Recommended action	No action is required.

MOD_ALM_ON

Message text	[STRING]: [STRING] was detected.
Variable fields	$1: Interface type and number. $2: Fault type.
Severity level	5
Example	OPTMOD/5/MOD_ALM_ON: GigabitEthernet1/0/1: Module_not_ready wasdetected.
Explanation	A fault was detected on the transceiver module.
Recommended action	1. Execute the display transceive alarm interface command to verify that a corresponding alarm for the fault has been generated and not cleared. 2. Replace the transceiver module.

MODULE_IN

Message text	[STRING]: The transceiver is [STRING].
Variable fields	$1: Interface type and number. $2: Type of the transceiver module.
Severity level	4
Example	OPTMOD/4/MODULE_IN: GigabitEthernet1/0/1: The transceiver is 1000_BASE_T_AN_SFP.
Explanation	When a transceiver module is inserted, the OPTMOD module generates the message to display the transceiver module type.
Recommended action	No action is required.

MODULE_OUT

Message text	[STRING]: Transceiver absent.
Variable fields	$1: Interface type and number.
Severity level	4
Example	OPTMOD/4/MODULE_OUT: GigabitEthernet1/0/1: The transceiver is absent.
Explanation	The transceiver module was removed.
Recommended action	No action is required.

PHONY_MODULE

Message text	[STRING]: This transceiver is not sold by H3C. H3C does not guarantee the correct operation of the module or assume maintenance responsibility.
Variable fields	$1: Interface type and number.
Severity level	4
Example	OPTMOD/4/PHONY_MODULE: GigabitEthernet1/0/1: This transceiver is not sold by H3C. H3C does not guarantee the correct operation of the module or assume maintenance responsibility.
Explanation	The transceiver module is not sold by H3C.
Recommended action	Replace the transceiver module.

RX_ALM_OFF

Message text	STRING]: [STRING] was removed.
Variable fields	$1: Interface type and number. $2: RX fault type.
Severity level	5
Example	OPTMOD/5/RX_ALM_OFF: GigabitEthernet1/0/1: RX_not_ready was removed.
Explanation	An RX fault was removed from the transceiver module.
Recommended action	No action is required.

RX_ALM_ON

Message text	[STRING]: [STRING] was detected.
Variable fields	$1: Interface type and number. $2: RX fault type.
Severity level	5
Example	OPTMOD/5/RX_ALM_ON: GigabitEthernet1/0/1: RX_not_ready was detected.
Explanation	An RX fault was detected on the transceiver module.
Recommended action	1. Execute the display transceiver alarm interface command to verify that a corresponding alarm for the fault has been generated and not cleared. 2. Replace the transceiver module.

RX_POW_HIGH

Message text	[STRING]: RX power is high.
Variable fields	$1: Interface type and number.
Severity level	5
Example	OPTMOD/5/RX_POW_HIGH: GigabitEthernet1/0/1: RX power is high.
Explanation	The RX power of the transceiver module exceeded the high threshold.
Recommended action	1. Execute the display transceiver diagnosis interface command to verify that the RX power of the transceiver module has exceeded the high threshold. 2. Execute the display transceiver alarm interface command to verify that a high RX power alarm for the transceiver module has been generated and not cleared. 3. Replace the transceiver module.

RX_POW_LOW

Message text	[STRING]: RX power is low.
Variable fields	$1: Interface type and number.
Severity level	5
Example	OPTMOD/5/RX_POW_LOW: GigabitEthernet1/0/1: RX power is low.
Explanation	The RX power of the transceiver module went below the low threshold.
Recommended action	1. Execute the display transceiver diagnosis interface command to verify that the RX power of the transceiver module is below the low threshold. 2. Execute the display transceiver alarm interface command to verify that a low RX power alarm for the transceiver module has been generated and not cleared. 3. Replace the transceiver module.

RX_POW_NORMAL

Message text	[STRING]: RX power is normal.
Variable fields	$1: Interface type and number.
Severity level	5
Example	OPTMOD/5/RX_POW_NORMAL: GigabitEthernet1/0/1: RX power is normal.
Explanation	The RX power of the transceiver module returned to the acceptable range.
Recommended action	No action is required.

TEMP_HIGH

Message text	[STRING]: Temperature is high.
Variable fields	$1: Interface type and number
Severity level	5
Example	OPTMOD/5/TEMP_HIGH: GigabitEthernet1/0/1: Temperature is high.
Explanation	The temperature of the transceiver module exceeded the high threshold.
Recommended action	1. Verify that the fan trays are operating correctly. ¡ If there are no fan trays, install fan trays. ¡ If the fan trays fail, replace the fan trays. 2. Verify that the ambient temperature is in the acceptable range. If it is out of the acceptable range, take measures to lower the temperature. 3. Replace the transceiver module.

TEMP_LOW

Message text	[STRING]: Temperature is low.
Variable fields	$1: Interface type and number.
Severity level	5
Example	OPTMOD/5/TEMP_LOW: GigabitEthernet1/0/1: Temperature is low.
Explanation	The temperature of the transceiver module went below the low threshold.
Recommended action	1. Verify that the ambient temperature is in the acceptable range. If it is out of the acceptable range, take measures to raise the temperature. 2. Replace the transceiver module.

TEMP_NORMAL

Message text	[STRING]: Temperature is normal.
Variable fields	$1: Interface type and number.
Severity level	5
Example	OPTMOD/5/TEMP_NORMAL: GigabitEthernet1/0/1: Temperature is normal.
Explanation	The temperature of the transceiver module returned to the acceptable range.
Recommended action	No action is required.

TX_ALM_OFF

Message text	[STRING]: [STRING] was removed.
Variable fields	$1: Interface type and number. $2: TX fault type.
Severity level	5
Example	OPTMOD/5/TX_ALM_OFF: GigabitEthernet1/0/1: TX_fault was removed.
Explanation	A TX fault was removed from the transceiver module.
Recommended action	No action is required.

TX_ALM_ON

Message text	[STRING]: [STRING] was detected.
Variable fields	$1: Interface type and number. $2: TX fault type.
Severity level	5
Example	OPTMOD/5/TX_ALM_ON: GigabitEthernet1/0/1: TX_fault was detected.
Explanation	A TX fault was detected on the transceiver module.
Recommended action	1. Execute the display transceiver alarm interface command to verify that a corresponding alarm for the fault has been generated and not cleared. 2. Replace the transceiver module.

TX_POW_HIGH

Message text	[STRING]: TX power is high.
Variable fields	$1: Interface type and number.
Severity level	2
Example	OPTMOD/2/TX_POW_HIGH: GigabitEthernet1/0/1: TX power is high.
Explanation	The TX power of the transceiver module exceeded the high threshold.
Recommended action	1. Execute the display transceiver diagnosis interface command to verify that the TX power of the transceiver module has exceeded the high threshold. 2. Execute the display transceiver alarm interface command to verify that a high TX power alarm for the transceiver module has been generated and not cleared. 3. Replace the transceiver module.

TX_POW_LOW

Message text	[STRING]: TX power is low.
Variable fields	$1: Interface type and number.
Severity level	5
Example	OPTMOD/5/TX_POW_LOW: GigabitEthernet1/0/1: TX power is low.
Explanation	The TX power of the transceiver module went below the low threshold.
Recommended action	1. Execute the display transceiver diagnosis interface command to verify that the TX power of the transceiver module is below the low threshold. 2. Execute the display transceiver alarm interface command to verify that a low TX power alarm for the transceiver module has been generated and not cleared. 3. Replace the transceiver module.

TX_POW_NORMAL

Message text	[STRING]: TX power is normal.
Variable fields	$1: Interface type and number.
Severity level	5
Example	OPTMOD/5/TX_POW_NORMAL: GigabitEthernet1/0/1: TX power is normal.
Explanation	The TX power of the transceiver module returned to the acceptable range.
Recommended action	No action is required.

TYPE_ERR

Message text	[STRING]: The transceiver type is not supported by port hardware.
Variable fields	$1: Interface type and number.
Severity level	3
Example	OPTMOD/3/TYPE_ERR: GigabitEthernet1/0/1: The transceiver type is not supported by port hardware.
Explanation	The transceiver module is not supported by the port.
Recommended action	Replace the transceiver module.

VOLT_HIGH

Message text	[STRING]: Voltage is high.
Variable fields	$1: Interface type and number
Severity level	5
Example	OPTMOD/5/VOLT_HIGH: GigabitEthernet1/0/1: Voltage is high.
Explanation	The voltage of the transceiver module exceeded the high threshold.
Recommended action	1. Execute the display transceiver diagnosis interface command to verify that the voltage of the transceiver module has exceeded the high threshold. 2. Execute the display transceiver alarm interface command to verify that a high voltage alarm for the transceiver module has been generated and not cleared. 3. Replace the transceiver module.

VOLT_LOW

Message text	[STRING]: Voltage is low.
Variable fields	$1: Interface type and number.
Severity level	5
Example	OPTMOD/5/VOLT_LOW: GigabitEthernet1/0/1: Voltage is low.
Explanation	The voltage of the transceiver module went below the low threshold.
Recommended action	1. Execute the display transceiver diagnosis interface command to verify that the voltage of the transceiver module is below the low threshold. 2. Execute the display transceiver alarm interface command to verify that a low voltage alarm for the transceiver module has been generated and not cleared. 3. Replace the transceiver module.

VOLT_NORMAL

Message text	[STRING]: Voltage is normal.
Variable fields	$1: Interface type and number.
Severity level	5
Example	OPTMOD/5/VOLT_NORMAL: GigabitEthernet1/0/1: Voltage is normal.
Explanation	The voltage of the transceiver module returned to the acceptable range.
Recommended action	No action is required.

OSPF messages

This section contains OSPF messages.

OSPF_DUP_RTRID_NBR

Message text	OSPF [UINT16] Duplicate router ID [STRING] on interface [STRING], sourced from IP address [IPADDR].
Variable fields	$1: OSPF process ID. $2: Router ID. $3: Interface name. $4: IP address.
Severity level	6
Example	OSPF/6/OSPF_DUP_RTRID_NBR: OSPF 1 Duplicate router ID 11.11.11.11 on interface GigabitEthernet0/0/3, sourced from IP address 11.2.2.2.
Explanation	Two directly connected devices were configured with the same router ID.
Recommended action	Modify the router ID on one device and use the reset ospf process command to make the new router ID take effect.

OSPF_IP_CONFLICT_INTRA

Message text	OSPF [UINT16] Received newer self-originated network-LSAs. Possible conflict of IP address [IPADDR] in area [STRING] on interface [STRING].
Variable fields	$1: OSPF process ID. $2: IP address. $3: OSPF area ID. $4: Interface name.
Severity level	6
Example	OSPF/6/OSPF_IP_CONFLICT_INTRA: OSPF 1 Received newer self-originated network-LSAs. Possible conflict of IP address 11.1.1.1 in area 0.0.0.1 on interface GigabitEthernet0/0/3.
Explanation	The interfaces on two devices in the same OSPF area might have the same primary IP address. At least one of the devices is a DR.
Recommended action	Modify IP address configuration after you make sure no router ID conflict occurs in the same OSPF area.

OSPF_LAST_NBR_DOWN

Message text	OSPF [UINT32] 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	The device records the OSPF neighbor down event caused by a specific reason.
Recommended action	· When a down event occurred because of configuration changes (for example, interface parameter changes), check for the configuration errors. · When a down event occurred because of dead interval expiration, check for the dead interval configuration error and loss of network connectivity. · When a down event occurred because of BFD session down, check for the BFD detection time configuration error and loss of network connectivity. · When a down event occurred because of interface status changes, check for loss of network connectivity.

OSPF_MEM_ALERT

Message text	OSPF Process received system memory alert [STRING] event.
Variable fields	$1: Type of the memory alarm.
Severity level	5
Example	OSPF/5/OSPF_MEM_ALERT: OSPF Process received system memory alert start event.
Explanation	OSPF received a memory alarm.
Recommended action	Check the system memory and release memory for the modules that occupy too many memory resources.

OSPF_NBR_CHG

Message text	OSPF [UINT32] Neighbor [STRING] ([STRING]) changed from [STRING] to [STRING]
Variable fields	$1: OSPF process ID. $2: Neighbor router ID. $3: Interface name. $4: Old adjacency state. $5: New adjacency state.
Severity level	5
Example	OSPF/5/OSPF_NBR_CHG: OSPF 1 Neighbor 2.2.2.2 (Vlan-interface100) changed from Full to Down.
Explanation	The OSPF adjacency state changed on an interface.
Recommended action	When the adjacency with a neighbor changes from Full to another state on an interface, check for OSPF configuration errors and loss of network connectivity.

OSPF_RT_LMT

Message text	OSPF [UINT32] route limit reached.
Variable fields	$1: OSPF process ID.
Severity level	4
Example	OSPF/4/OSPF_RT_LMT: OSPF 1 route limit reached.
Explanation	The number of routes of an OSPF process reached the upper limit.
Recommended action	1. Check for network attacks. 2. Reduce the number of routes.

OSPF_RTRID_CHG

Message text	OSPF [UINT32] 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	The OSPF router ID was changed because the user had changed the router ID or the interface IP address used as the router ID had changed.
Recommended action	Use the reset ospf process command to make the new router ID take effect.

OSPF_RTRID_CONFLICT_INTER

Message text	OSPF [UINT16] Received newer self-originated ase-LSAs. Possible conflict of router ID [STRING].
Variable fields	$1: OSPF process ID. $2: Router ID.
Severity level	6
Example	OSPF/6/OSPF_RTRID_CONFILICT_INTER: OSPF 1 Received newer self-originated ase-LSAs. Possible conflict of router ID 11.11.11.11.
Explanation	Two indirectly connected devices in the same OSPF area might have the same router ID. One of the devices is an ASBR.
Recommended action	Modify the router ID on one device and use the reset ospf process command to make the new router ID take effect.

OSPF_RTRID_CONFLICT_INTRA

Message text	OSPF [UINT16] Received newer self-originated router-LSAs. Possible conflict of router ID [STRING] in area [STRING].
Variable fields	$1: OSPF process ID. $2: Router ID. $3: OSPF area ID.
Severity level	6
Example	OSPF/6/OSPF_RTRID_CONFLICT_INTRA: OSPF 1 Received newer self-originated router-LSAs. Possible conflict of router ID 11.11.11.11 in area 0.0.0.1.
Explanation	Two indirectly connected devices in the same OSPF area might have the same router ID.
Recommended action	Modify the router ID on one device and use the reset ospf process command to make the new router ID take effect.

OSPF_VLINKID_CHG

Message text	OSPF [UINT32] Router ID changed, reconfigure Vlink on peer
Variable fields	$1: OSPF process ID.
Severity level	5
Example	OSPF/5/OSPF_VLINKID_CHG:OSPF 1 Router ID changed, reconfigure Vlink on peer
Explanation	A new OSPF router ID takes effect.
Recommended action	Check and modify the virtual link configuration on the peer router to match the new router ID.

OSPFV3 messages

This section contains OSPFv3 messages.

OSPFV3_LAST_NBR_DOWN

Message text	OSPFv3 [UINT32] Last neighbor down event: Router ID: [STRING] Local interface ID: [UINT32] Remote interface ID: [UINT32] Reason: [STRING].
Variable fields	$1: OSPFv3 process ID. $2: Router ID. $3: Local interface ID. $4: Remote interface ID. $5: Reason.
Severity level	6
Example	OSPFV3/6/OSPFV3_LAST_NBR_DOWN: OSPFv3 1 Last neighbor down event: Router ID: 2.2.2.2 Local interface ID: 1111 Remote interface ID: 2222 Reason: Dead Interval timer expired.
Explanation	The device records the OSPFv3 neighbor down event caused by a specific reason.
Recommended action	· When a down event occurred because of configuration changes (for example, interface parameter changes), check for the configuration errors. · When a down event occurred because of dead interval expiration, check for the dead interval configuration error and loss of network connectivity. · When a down event occurred because of BFD session down, check for the BFD detection time configuration error and loss of network connectivity. · When a down event occurred because of interface status changes, check for loss of network connectivity.

OSPFV3_MEM_ALERT

Message text	OSPFV3 Process received system memory alert [STRING] event.
Variable fields	$1: Type of the memory alarm.
Severity level	5
Example	OSPFV3/5/OSPFV3_MEM_ALERT: OSPFV3 Process received system memory alert start event.
Explanation	OSPFv3 received a memory alarm.
Recommended action	Check the system memory and release memory for the modules that occupy too many memory resources.

OSPFV3_NBR_CHG

Message text	OSPFv3 [UINT32] Neighbor [STRING] ([STRING]) received [STRING] and its state changed from [STRING] to [STRING].
Variable fields	$1: Process ID. $2: Neighbor router ID. $3: Interface name. $4: Neighbor event. $5: Old adjacency state. $6: New adjacency state.
Severity level	5
Example	OSPFV3/5/OSPFV3_NBR_CHG: OSPFv3 1 Neighbor 2.2.2.2 (Vlan100) received 1-Way and its state changed from Full to Init.
Explanation	The OSPFv3 adjacency state changed on an interface.
Recommended action	When the adjacency with a neighbor changes from Full to another state on an interface, check for OSPFv3 configuration errors and loss of network connectivity.

OSPFV3_RT_LMT

Message text	OSPFv3 [UINT32] route limit reached.
Variable fields	$1: Process ID.
Severity level	5
Example	OSPFV3/5/OSPFV3_RT_LMT:OSPFv3 1 route limit reached.
Explanation	The number of routes of an OSPFv3 process reached the upper limit.
Recommended action	1. Check for network attacks. 2. Reduce the number of routes.

PBR messages

This section contains PBR messages.

PBR_HARDWARE_ERROR

Message text	Failed to update policy [STRING] due to [STRING].
Variable fields	$1: Policy name. $2: Hardware error reasons: · The hardware resources are insufficient. · The system does not support the operation. · The hardware resources are insufficient and the system does not support the operation.
Severity level	4
Example	PBR/4/PBR_HARDWARE_ERROR: Failed to update policy aaa due to insufficient hardware resources and not supported operations.
Explanation	The device failed to update PBR configuration.
Recommended action	Modify the PBR policy configuration according to the failure reason.

PFILTER messages

This section contains PFILTER messages.

PFILTER_APPLY_REPEAT

Message text	[STRING] ACL [STRING] applied to the [STRING] direction of [STRING] is deleted, because the same ACL has been applied.
Variable fields	$1: ACL type. $2: ACL number or name. $3: Traffic direction. $4: Destination to which packet filter applies.
Severity level	5
Example	PFILTER/5/PFILTER_APPLY_REPEAT: IPv4 ACL aa applied to the inbound direction of interface GigabitEthernet 0/0/1 is deleted, because the same ACL has been applied.
Explanation	On the same direction of a destination, you can configure two ACL-based packet filters. One references the ACL number of an nonexisting ACL, and the other references the ACL name of an nonexisting ACL. This message is sent when you create one ACL by using the ACL number and ACL name of the ACLs used in the packet filters. The packet filter configured later is deleted.
Recommended action	On the same direction of a destination, you can configure two ACL-based packet filters. One references the ACL number of an nonexisting ACL, and the other references the ACL name of an nonexisting ACL. In this case, do not used the ACL number and ACL name of the ACLs used in the packet filters to create one ACL.

PFILTER_GLB_RES_CONFLICT

Message text	Failed to apply or refresh [STRING] ACL [UINT] to the [STRING] direction globally. [STRING] ACL [UINT] has already been applied globally.
Variable fields	$1: ACL type. $2: ACL number. $3: Traffic direction. $4: ACL type. $5: ACL number.
Severity level	3
Example	PFILTER/3/PFILTER_GLB_RES_CONFLICT: Failed to apply or refresh IPv6 ACL 2000 to the inbound direction globally. IPv6 ACL 3000 has already been applied globally.
Explanation	The system failed to perform one of the following actions because an ACL of the same type (IPv4 ACL, IPv6 ACL, or MAC ACL) has already been applied: Applying the ACL to a specific direction globally. Updating the ACL applied to a specific direction globally.
Recommended action	Remove the ACL of the same type.

PFILTER_GLB_IPV4_DACT_NO_RES

Message text	Failed to apply or refresh the IPv4 default action to the [STRING] direction globally. The resources are insufficient.
Variable fields	$1: Traffic direction.
Severity level	3
Example	PFILTER/3/PFILTER_GLB_IPV4_DACT_NO_RES: Failed to apply or refresh the IPv4 default action to the inbound direction globally. The resources are insufficient.
Explanation	The system failed to perform one of the following actions because hardware resources are insufficient: Applying the IPv4 default action to a specific direction globally. Updating the IPv4 default action applied to a specific direction globally.
Recommended action	Use the display qos-acl resource command to check hardware resource usage.

PFILTER_GLB_IPV4_DACT_UNK_ERR

Message text	Failed to apply or refresh the IPv4 default action to the [STRING] direction globally.
Variable fields	$1: Traffic direction.
Severity level	3
Example	PFILTER/3/PFILTER_GLB_IPV4_DACT_UNK_ERR: Failed to apply or refresh the IPv4 default action to the inbound direction globally.
Explanation	The system failed to perform one of the following actions due to an unknown error: Applying the IPv4 default action to a specific direction globally. Updating the IPv4 default action applied to a specific direction globally.
Recommended action	No action is required.

PFILTER_GLB_IPV6_DACT_NO_RES

Message text	Failed to apply or refresh the IPv6 default action to the [STRING] direction globally. The resources are insufficient.
Variable fields	$1: Traffic direction.
Severity level	3
Example	PFILTER/3/PFILTER_GLB_IPV6_DACT_NO_RES: Failed to apply or refresh the IPv6 default action to the inbound direction globally. The resources are insufficient.
Explanation	The system failed to perform one of the following actions because hardware resources are insufficient: Applying the IPv6 default action to a specific direction globally. Updating the IPv6 default action applied to a specific direction globally.
Recommended action	Use the display qos-acl resource command to check hardware resource usage.

PFILTER_GLB_IPV6_DACT_UNK_ERR

Message text	Failed to apply or refresh the IPv6 default action to the [STRING] direction globally.
Variable fields	$1: Traffic direction.
Severity level	3
Example	PFILTER/3/PFILTER_GLB_IPV6_DACT_UNK_ERR: Failed to apply or refresh the IPv6 default action to the inbound direction globally.
Explanation	The system failed to perform one of the following actions due to an unknown error: Applying the IPv6 default action to a specific direction globally. Updating the IPv6 default action applied to a specific direction globally.
Recommended action	No action is required.

PFILTER_GLB_MAC_DACT_NO_RES

Message text	Failed to apply or refresh the MAC default action to the [STRING] direction globally. The resources are insufficient.
Variable fields	$1: Traffic direction.
Severity level	3
Example	PFILTER/3/PFILTER_GLB_MAC_DACT_NO_RES: Failed to apply or refresh the MAC default action to the inbound direction globally. The resources are insufficient.
Explanation	The system failed to perform one of the following actions because hardware resources are insufficient: Applying the MAC default action to a specific direction globally. Updating the MAC default action applied to a specific direction globally.
Recommended action	Use the display qos-acl resource command to check hardware resource usage.

PFILTER_GLB_MAC_DACT_UNK_ERR

Message text	Failed to apply or refresh the MAC default action to the [STRING] direction globally.
Variable fields	$1: Traffic direction.
Severity level	3
Example	PFILTER/3/PFILTER_GLB_MAC_DACT_UNK_ERR: Failed to apply or refresh the MAC default action to the inbound direction globally.
Explanation	The system failed to perform one of the following actions due to an unknown error: Applying the MAC default action to a specific direction globally. Updating the MAC default action applied to a specific direction globally.
Recommended action	No action is required.

PFILTER_GLB_NO_RES

Message text	Failed to apply or refresh [STRING] ACL [UINT] [STRING] to the [STRING] direction globally. The resources are insufficient.
Variable fields	$1: ACL type. $2: ACL number. $3: ACL rule ID. $4: Traffic direction.
Severity level	3
Example	PFILTER/3/PFILTER_GLB_NO_RES: Failed to apply or refresh IPv6 ACL 2000 rule 1 to the inbound direction globally. The resources are insufficient.
Explanation	The system failed to perform one of the following actions because hardware resources are insufficient: Applying an ACL rule to a specific direction globally. Updating an ACL rule applied to a specific direction globally.
Recommended action	Use the display qos-acl resource command to check hardware resource usage.

PFILTER_GLB_NOT_SUPPORT

Message text	Failed to apply or refresh [STRING] ACL [UINT] [STRING] to the [STRING] direction globally. The ACL is not supported.
Variable fields	$1: ACL type. $2: ACL number. $3: ACL rule ID. $4: Traffic direction.
Severity level	3
Example	PFILTER/3/PFILTER_GLB_NOT_SUPPORT: Failed to apply or refresh IPv6 ACL 2000 rule 1 to the inbound direction globally. The ACL is not supported.
Explanation	The system failed to perform one of the following actions because the ACL rule is not supported: Applying an ACL rule to a specific direction globally. Updating an ACL rule applied to a specific direction globally.
Recommended action	Verify the ACL configuration and remove the settings that are not supported.

PFILTER_GLB_UNK_ERR

Message text	Failed to apply or refresh [STRING] ACL [UINT] [STRING] to the [STRING] direction globally.
Variable fields	$1: ACL type. $2: ACL number. $3: ACL rule ID. $4: Traffic direction.
Severity level	3
Example	PFILTER/3/PFILTER_GLB_UNK_ERR: Failed to apply or refresh IPv6 ACL 2000 rule 1 to the inbound direction globally.
Explanation	The system failed to perform one of the following actions due to an unknown error: Applying an ACL rule to a specific direction globally. Updating an ACL rule applied to a specific direction globally.
Recommended action	No action is required.

PFILTER_IF_IPV4_DACT_NO_RES

Message text	Failed to apply or refresh the IPv4 default action to the [STRING] direction of interface [STRING]. The resources are insufficient.
Variable fields	$1: Traffic direction. $2: Interface name.
Severity level	3
Example	PFILTER/3/PFILTER_IF_IPV4_DACT_NO_RES: Failed to apply or refresh the IPv4 default action to the inbound direction of interface Ethernet 3/1/2. The resources are insufficient.
Explanation	The system failed to perform one of the following actions because hardware resources are insufficient: Applying the IPv4 default action to a specific direction of an interface. Updating the IPv4 default action applied to a specific direction of an interface.
Recommended action	Use the display qos-acl resource command to check hardware resource usage.

PFILTER_IF_IPV4_DACT_UNK_ERR

Message text	Failed to apply or refresh the IPv4 default action to the [STRING] direction of interface [STRING].
Variable fields	$1: Traffic direction. $2: Interface name.
Severity level	3
Example	PFILTER/3/PFILTER_IF_IPV4_DACT_UNK_ERR: Failed to apply or refresh the IPv4 default action to the inbound direction of interface Ethernet 3/1/2.
Explanation	The system failed to perform one of the following actions because an unknown error: Applying the IPv4 default action to a specific direction of an interface. Updating the IPv4 default action applied to a specific direction of an interface.
Recommended action	No action is required.

PFILTER_IF_IPV6_DACT_NO_RES

Message text	Failed to apply or refresh the IPv6 default action to the [STRING] direction of interface [STRING]. The resources are insufficient.
Variable fields	$1: Traffic direction. $2: Interface name.
Severity level	3
Example	PFILTER/3/PFILTER_IF_IPV6_DACT_NO_RES: Failed to apply or refresh the IPv6 default action to the inbound direction of interface Ethernet 3/1/2. The resources are insufficient.
Explanation	The system failed to perform one of the following actions because hardware resources are insufficient: Applying the IPv6 default action to a specific direction of an interface. Updating the IPv6 default action applied to a specific direction of an interface.
Recommended action	Use the display qos-acl resource command to check hardware resource usage.

PFILTER_IF_IPV6_DACT_UNK_ERR

Message text	Failed to apply or refresh the IPv6 default action to the [STRING] direction of interface [STRING].
Variable fields	$1: Traffic direction. $2: Interface name.
Severity level	3
Example	PFILTER/3/PFILTER_IF_IPV6_DACT_UNK_ERR: Failed to apply or refresh the IPv6 default action to the inbound direction of interface Ethernet 3/1/2.
Explanation	The system failed to perform one of the following actions due to an unknown error: Applying the IPv6 default action to a specific direction of an interface. Updating the IPv6 default action applied to a specific direction of an interface.
Recommended action	No action is required.

PFILTER_IF_MAC_DACT_NO_RES

Message text	Failed to apply or refresh the MAC default action to the [STRING] direction of interface [STRING]. The resources are insufficient.
Variable fields	$1: Traffic direction. $2: Interface name.
Severity level	3
Example	PFILTER/3/PFILTER_IF_MAC_DACT_NO_RES: Failed to apply or refresh the MAC default action to the inbound direction of interface Ethernet 3/1/2. The resources are insufficient.
Explanation	The system failed to perform one of the following actions because hardware resources are insufficient: Applying the MAC default action to a specific direction of an interface. Updating the MAC default action applied to a specific direction of an interface.
Recommended action	Use the display qos-acl resource command to check hardware resource usage.

PFILTER_IF_MAC_DACT_UNK_ERR

Message text	Failed to apply or refresh the MAC default action to the [STRING] direction of interface [STRING].
Variable fields	$1: Traffic direction. $2: Interface name.
Severity level	3
Example	PFILTER/3/PFILTER_IF_MAC_DACT_UNK_ERR: Failed to apply or refresh the MAC default action to the inbound direction of interface Ethernet 3/1/2.
Explanation	The system failed to perform one of the following actions due to an unknown error: Applying the MAC default action to a specific direction of an interface. Updating the MAC default action applied to a specific direction of an interface.
Recommended action	No action is required.

PFILTER_IF_NO_RES

Message text	Failed to apply or refresh [STRING] ACL [UINT] [STRING] to the [STRING] direction of interface [STRING]. The resources are insufficient.
Variable fields	$1: ACL type. $2: ACL number. $3: ACL rule ID. $4: Traffic direction. $5: Interface name.
Severity level	3
Example	PFILTER/3/PFILTER_IF_NO_RES: Failed to apply or refresh IPv6 ACL 2000 rule 1 to the inbound direction of interface Ethernet 3/1/2. The resources are insufficient.
Explanation	The system failed to perform one of the following actions because hardware resources are insufficient: Applying an ACL rule to a specific direction of an interface. Updating an ACL rule applied to a specific direction of an interface.
Recommended action	Use the display qos-acl resource command to check hardware resource usage.

PFILTER_IF_NOT_SUPPORT

Message text	Failed to apply or refresh [STRING] ACL [UINT] [STRING] to the [STRING] direction of interface [STRING]. The ACL is not supported.
Variable fields	$1: ACL type. $2: ACL number. $3: ACL rule ID. $4: Traffic direction. $5: Interface name.
Severity level	3
Example	PFILTER/3/PFILTER_IF_NOT_SUPPORT: Failed to apply or refresh IPv6 ACL 2000 rule 1 to the inbound direction of interface Ethernet 3/1/2. The ACL is not supported.
Explanation	The system failed to perform one of the following actions because the ACL rule is not supported: Applying an ACL rule to a specific direction of an interface. Updating an ACL rule applied to a specific direction of an interface.
Recommended action	Verify the ACL configuration and remove the settings that are not supported.

PFILTER_IF_RES_CONFLICT

Message text	Failed to apply or refresh [STRING] ACL [UINT] to the [STRING] direction of interface [STRING]. [STRING] ACL [UINT] has already been applied to the interface.
Variable fields	$1: ACL type. $2: ACL number. $3: Traffic direction. $4: Interface name. $5: ACL type. $6: ACL number.
Severity level	3
Example	PFILTER/3/PFILTER_IF_RES_CONFLICT: Failed to apply or refresh IPv6 ACL 2000 to the inbound direction of interface Ethernet 3/1/2. IPv6 ACL 3000 has already been applied to the interface.
Explanation	The system failed to perform one of the following actions because an ACL of the same type (IPv4 ACL, IPv6 ACL, or MAC ACL) has already been applied: Applying the ACL to a specific direction of an interface. Updating the ACL applied to a specific direction of an interface.
Recommended action	Remove the ACL of the same type.

PFILTER_IF_UNK_ERR

Message text	Failed to apply or refresh [STRING] ACL [UINT] [STRING] to the [STRING] direction of interface [STRING].
Variable fields	$1: ACL type. $2: ACL number. $3: ACL rule ID. $4: Traffic direction. $5: Interface name.
Severity level	3
Example	PFILTER/3/PFILTER_IF_UNK_ERR: Failed to apply or refresh IPv6 ACL 2000 rule 1 to the inbound direction of interface Ethernet 3/1/2.
Explanation	The system failed to perform one of the following actions due to an unknown error: Applying an ACL rule to a specific direction of an interface. Updating an ACL rule applied to a specific direction of an interface.
Recommended action	No action is required.

PFILTER_IPV4_FLOW_INFO

Message text	ACL [STRING] [STRING] [STRING] rule [STRING] [STRING]
Variable fields	$1: ACL number or name. $2: Traffic direction. $3: Destination to which packet filter applies. $4: ID and content of an ACL rule. $5: Information about the first packet of a flow that matches the rule.
Severity level	6
Example	PFILTER/6/PFILTER_IPV4_FLOW_INFO: ACL 3000 inbound Ethernet 3/1/2 rule 0 permit tcp 192.168.1.1(1024) -> 192.168.5.1(1024).
Explanation	This message is sent when the first packet of a flow matches an IPv4 advanced ACL rule for packet filtering. The rule has been configured with the flow-logging keyword.
Recommended action	No action is required.

PFILTER_IPV4_FLOW_STATIS

Message text	ACL [STRING] [STRING] rule [STRING] [STRING], [UINT64] packet(s).
Variable fields	$1: ACL number or name. $2: Traffic direction. $3: ID and content of an ACL rule. $4: Information about the first packet of a flow that matched the rule. $5: Number of packets that match the rule.
Severity level	6
Example	PFILTER/6/PFILTER_IPV4_FLOWLOG_STATIS: ACL 3000 inbound rule 0 permit icmp 192.168.1.1(1024) -> 192.168.5.1(1024), 1000 packets.
Explanation	This message is sent at the logging interval. The rule has been configured with the flow-logging keyword.
Recommended action	No action is required.

PFILTER_IPV6_FLOW_INFO

Message text	IPv6 ACL [STRING] [STRING] [STRING] rule [STRING] [STRING]
Variable fields	$1: ACL number or name. $2: Traffic direction. $3: Destination to which packet filter applies. $4: ID and content of an ACL rule. $5: Information about the first packet of a flow that matches the rule.
Severity level	6
Example	PFILTER/6/PFILTER_IPV6_FLOW_INFO: IPv6 ACL 3000 inbound Ethernet 3/1/2 rule 0 permit tcp 0:1020::200:0(0)->0:720::200:0(0).
Explanation	This message is sent when the first packet of a flow matches an IPv6 advanced ACL rule applied for packet filtering. The rule has been configured with the flow-logging keyword.
Recommended action	No action is required.

PFILTER_IPV6_FLOW_STATIS

Message text	IPv6 ACL [STRING] [STRING] rule [STRING] [STRING], [UINT64] packet(s).
Variable fields	$1: ACL number or name. $2: Traffic direction. $3: ID and content of an ACL rule. $4: Information about the first packet of a flow that matched the rule. $5: Number of packets that match the rule.
Severity level	6
Example	PFILTER/6/PFILTER_IPV6_FLOWLOG_STATIS: IPv6 ACL 3000 rule 0 permit icmpv6 0:1020::200:0(0)->0:720::200:0(0), 1000 packets.
Explanation	This message is sent at the logging interval. The rule has been configured with the flow-logging keyword.
Recommended action	No action is required.

PFILTER_IPV6_STATIS_INFO

Message text	[STRING] ([STRING]): Packet-filter IPv6 [UINT32] [STRING] [STRING] [UINT64] packet(s).
Variable fields	$1: Destination to which packet filter applies. $2: Traffic direction. $3: ACL number. $4: ID and content of an ACL rule. $5: Number of packets that matched the rule.
Severity level	6
Example	ACL/6/PFILTER_IPV6_STATIS_INFO: Ethernet0/4/0 (inbound): Packet-filter IPv6 2000 rule 0 permit source 1:1::/64 logging 1000 packet(s).
Explanation	The number of packets matching the packet-filter IPv6 ACL rule changed.
Recommended action	No action is required.

PFILTER_STATIS_INFO

Message text	[STRING] ([STRING]): Packet-filter [UINT32] [STRING] [UINT64] packet(s).
Variable fields	$1: Destination to which packet filter applies. $2: Traffic direction. $3: ACL number. $4: ID and content of an ACL rule. $5: Number of packets that matched the rule.
Severity level	6
Example	ACL/6/PFILTER_STATIS_INFO: Ethernet0/4/0 (inbound): Packet-filter 2000 rule 0 permit source 1.1.1.1 0 logging 10000 packet(s).
Explanation	The number of packets matching the packet-filter IPv4 ACL rule changed.
Recommended action	No action is required.

PFILTER_MAC_FLOW_INFO

Message text	MAC ACL [STRING] [STRING] [STRING] rule [STRING] [STRING]
Variable fields	$1: ACL number or name. $2: Traffic direction. $3: Destination to which packet filter applies. $4: ID and content of an ACL rule. $5: Information about the first packet that matches the rule.
Severity level	6
Example	PFILTER/6/PFILTER_MAC_FLOW_INFO: MAC ACL 4000 inbound Ethernet 3/1/2 rule 0 permit 0800-2700-9000 -> 0CDA-411D-0676.
Explanation	This message is sent when the first packet matches an Layer 2 ACL rule for packet filtering.
Recommended action	No action is required.

PFILTER_VLAN_IPV4_DACT_NO_RES

Message text	Failed to apply or refresh the IPv4 default action to the [STRING] direction of VLAN [UINT16]. The resources are insufficient.
Variable fields	$1: Traffic direction. $2: VLAN ID.
Severity level	3
Example	PFILTER/3/PFILTER_VLAN_IPV4_DACT_NO_RES: Failed to apply or refresh the IPv4 default action to the inbound direction of VLAN 1. The resources are insufficient.
Explanation	The system failed to perform one of the following actions because hardware resources are insufficient: Applying the IPv4 default action to a specific direction of a VLAN. Updating the IPv4 default action applied to a specific direction of a VLAN.
Recommended action	Use the display qos-acl resource command to check hardware resource usage.

PFILTER_VLAN_IPV4_DACT_UNK_ERR

Message text	Failed to apply or refresh the IPv4 default action to the [STRING] direction of VLAN [UINT16].
Variable fields	$1: Traffic direction. $2: VLAN ID.
Severity level	3
Example	PFILTER/3/PFILTER_VLAN_IPV4_DACT_UNK_ERR: Failed to apply or refresh the IPv4 default action to the inbound direction of VLAN 1.
Explanation	The system failed to perform one of the following actions due to an unknown error: Applying the IPv4 default action to a specific direction of a VLAN. Updating the IPv4 default action applied to a specific direction of a VLAN.
Recommended action	No action is required.

PFILTER_VLAN_IPV6_DACT_NO_RES

Message text	Failed to apply or refresh the IPv6 default action to the [STRING] direction of VLAN [UINT16]. The resources are insufficient.
Variable fields	$1: Traffic direction. $2: VLAN ID.
Severity level	3
Example	PFILTER/3/PFILTER_VLAN_IPV6_DACT_NO_RES: Failed to apply or refresh the IPv6 default action to the inbound direction of VLAN 1. The resources are insufficient.
Explanation	The system failed to perform one of the following actions because hardware resources are insufficient: Applying the IPv6 default action to a specific direction of a VLAN. Updating the IPv6 default action applied to a specific direction of a VLAN.
Recommended action	Use the display qos-acl resource command to check hardware resource usage.

PFILTER_VLAN_IPV6_DACT_UNK_ERR

Message text	Failed to apply or refresh the IPv6 default action to the [STRING] direction of VLAN [UINT16].
Variable fields	$1: Traffic direction. $2: VLAN ID.
Severity level	3
Example	PFILTER/3/PFILTER_VLAN_IPV6_DACT_UNK_ERR: Failed to apply or refresh the IPv6 default action to the inbound direction of VLAN 1.
Explanation	The system failed to perform one of the following actions due to an unknown error: Applying the IPv6 default action to a specific direction of a VLAN. Updating the IPv6 default action applied to a specific direction of a VLAN.
Recommended action	No action is required.

PFILTER_VLAN_MAC_DACT_NO_RES

Message text	Failed to apply or refresh the MAC default action to the [STRING] direction of VLAN [UINT16]. The resources are insufficient.
Variable fields	$1: Traffic direction. $2: VLAN ID.
Severity level	3
Example	PFILTER/3/PFILTER_VLAN_MAC_DACT_NO_RES: Failed to apply or refresh the MAC default action to the inbound direction of VLAN 1. The resources are insufficient.
Explanation	The system failed to perform one of the following actions because hardware resources are insufficient: Applying the MAC default action to a specific direction of a VLAN. Updating the MAC default action applied to a specific direction of a VLAN.
Recommended action	Use the display qos-acl resource command to check hardware resource usage.

PFILTER_VLAN_MAC_DACT_UNK_ERR

Message text	Failed to apply or refresh the MAC default action to the [STRING] direction of VLAN [UINT16].
Variable fields	$1: Traffic direction. $2: VLAN ID.
Severity level	3
Example	PFILTER/3/PFILTER_VLAN_MAC_DACT_UNK_ERR: Failed to apply or refresh the MAC default action to the inbound direction of VLAN 1.
Explanation	The system failed to perform one of the following actions due to an unknown error: Applying the MAC default action to a specific direction of a VLAN. Updating the MAC default action applied to a specific direction of a VLAN.
Recommended action	No action is required.

PFILTER_VLAN_NO_RES

Message text	Failed to apply or refresh [STRING] ACL [UINT] [STRING] to the [STRING] direction of VLAN [UINT16]. The resources are insufficient.
Variable fields	$1: ACL type. $2: ACL number. $3: ACL rule ID. $4: Traffic direction. $5: VLAN ID.
Severity level	3
Example	PFILTER/3/PFILTER_VLAN_NO_RES: Failed to apply or refresh IPv6 ACL 2000 rule 1 to the inbound direction of VLAN 1. The resources are insufficient.
Explanation	The system failed to perform one of the following actions because hardware resources are insufficient: Applying an ACL rule to a specific direction of a VLAN. Updating an ACL rule applied to a specific direction of a VLAN.
Recommended action	Use the display qos-acl resource command to check hardware resource usage.

PFILTER_VLAN_NOT_SUPPORT

Message text	Failed to apply or refresh [STRING] ACL [UINT] [STRING] to the [STRING] direction of VLAN [UINT16]. The ACL is not supported.
Variable fields	$1: ACL type. $2: ACL number. $3: ACL rule ID. $4: Traffic direction. $5: VLAN ID.
Severity level	3
Example	PFILTER/3/PFILTER_VLAN_NOT_SUPPORT: Failed to apply or refresh ACL 2000 rule 1 to the inbound direction of VLAN 1. The ACL is not supported.
Explanation	The system failed to perform one of the following actions because the ACL rule is not supported: Applying an ACL rule to a specific direction of a VLAN. Updating an ACL rule applied to a specific direction of a VLAN.
Recommended action	Verify the ACL configuration and remove the settings that are not supported.

PFILTER_VLAN_RES_CONFLICT

Message text	Failed to apply or refresh [STRING] ACL [UINT] to the [STRING] direction of VLAN [UINT16]. [STRING] ACL [UINT] has already been applied to the VLAN.
Variable fields	$1: ACL type. $2: ACL number. $3: Traffic direction. $4: VLAN ID. $5: ACL type. $6: ACL number.
Severity level	3
Example	PFILTER/3/PFILTER_VLAN_RES_CONFLICT: Failed to apply or refresh IPv6 ACL 2000 to the inbound direction of VLAN 1. IPv6 ACL 3000 has already been applied to the VLAN.
Explanation	The system failed to perform one of the following actions because an ACL of the same type (IPv4 ACL, IPv6 ACL, or MAC ACL) has already been applied: Applying the ACL to a specific direction of a VLAN. Updating the ACL applied to a specific direction of a VLAN.
Recommended action	Remove the ACL of the same type.

PFILTER_VLAN_UNK_ERR

Message text	Failed to apply or refresh [STRING] ACL [UINT] [STRING] to the [STRING] direction of VLAN [UINT16].
Variable fields	$1: ACL type. $2: ACL number. $3: ACL rule ID. $4: Traffic direction. $5: VLAN ID.
Severity level	3
Example	PFILTER/3/PFILTER_VLAN_UNK_ERR: Failed to apply or refresh ACL 2000 rule 1 to the inbound direction of VLAN 1.
Explanation	The system failed to perform one of the following actions due to an unknown error: Applying an ACL rule to a specific direction of a VLAN. Updating an ACL rule applied to a specific direction of a VLAN.
Recommended action	No action is required.

PIM messages

This section contains PIM messages.

PIM_NBR_DOWN

Message text	[STRING]: Neighbor [STRING] ([STRING]) is down.
Variable fields	$1: VPN instance name enclosed in parentheses (()). If the PIM neighbor belongs to the public network, this field is not displayed. $2: IP address of the PIM neighbor. $3: Interface name.
Severity level	5
Example	PIM/5/PIM_NBR_DOWN: Neighbor 10.1.1.1(Vlan-interface10) is down.
Explanation	A PIM neighbor went down.
Recommended action	Check the PIM configuration and network status.

PIM_NBR_UP

Message text	[STRING]: Neighbor [STRING] ([STRING]) is up.
Variable fields	$1: VPN instance name enclosed in parentheses (()). If the PIM neighbor belongs to the public network, this field is not displayed. $2: IP address of the PIM neighbor. $3: Interface name.
Severity level	5
Example	PIM/5/PIM_NBR_UP: Neighbor 10.1.1.1(Vlan-interface10) is up.
Explanation	A PIM neighbor came up.
Recommended action	No action is required.

PING messages

This section contains ping messages.

PING_STATISTICS

Message text	[STRING] statistics for [STRING]: [UINT32] packets transmitted, [UINT32] packets received, [DOUBLE]% packet loss, round-trip min/avg/max/std-dev = [DOUBLE]/[DOUBLE]/[DOUBLE]/[DOUBLE] ms.
Variable fields	$1: Ping or ping6. $2: IP address, IPv6 address, or host name for the destination. $3: Number of sent echo requests. $4: Number of received echo replies. $5: Percentage of the non-replied packets to the total request packets. $6: Minimum round-trip delay. $7: Average round-trip delay. $8: Maximum round-trip delay. $9: Standard deviation round-trip delay.
Severity level	6
Example	PING/6/PING_STATISTICS: Ping statistics for 192.168.0.115: 5 packets transmitted, 5 packets received, 0.0% packet loss, round-trip min/avg/max/std-dev = 0.000/0.800/2.000/0.748 ms.
Explanation	A user uses the ping command to identify whether a destination in the public network is reachable.
Recommended action	If there is no packet received, identify whether the interface is down.

PING_VPN_STATISTICS

Message text	[STRING] statistics for [STRING] in VPN instance [STRING] : [UINT32] packets transmitted, [UINT32] packets received, [DOUBLE]% packet loss, round-trip min/avg/max/std-dev = [DOUBLE]/[DOUBLE]/[DOUBLE]/[DOUBLE] ms.
Variable fields	$1: Ping or ping6. $2: IP address, IPv6 address, or host name for the destination. $3: VPN instance name. $4: Number of sent echo requests. $5: Number of received echo replies. $6: Percentage of the non-replied packets to the total request packets. $7: Minimum round-trip delay. $8: Average round-trip delay. $9: Maximum round-trip delay. $10: Standard deviation round-trip delay.
Severity level	6
Example	PING/6/PING_VPN_STATISTICS: Ping statistics for 192.168.0.115 in VPN instance vpn1: 5 packets transmitted, 5 packets received, 0.0% packet loss, round-trip min/avg/max/std-dev = 0.000/0.800/2.000/0.748 ms.
Explanation	A user uses the ping command to identify whether a destination in a private network is reachable.
Recommended action	If there is no packet received, identify whether the interface is down and identify whether a valid route exists in the routing table.

PKG messages

This section contains package management messages.

PKG_BOOTLOADER_FILE_FAILED

Message text	Failed to execute the boot-loader file command.
Variable fields	None
Severity level	5
Example	PKG/5/PKG_BOOTLOADER_FILE_FAILED: -IPAddr=192.168.79.1-User=**; Failed to execute the boot-loader file command.
Explanation	A user executed the boot-loader file command, but the command failed.
Recommended action	Take actions as prompted by the command.

PKG_BOOTLOADER_FILE_SUCCESS

Message text	Executed the boot-loader file command successfully.
Variable fields	None
Severity level	5
Example	PKG/5/PKG_BOOTLOADER_FILE_SUCCESS: -IPAddr=192.168.79.1-User=**; Executed the boot-loader file command successfully.
Explanation	A user executed the boot-loader file command successfully.
Recommended action	No action is required.

PKG_INSTALL_ACTIVATE_FAILED

Message text	Failed to execute the install activate command.
Variable fields	None
Severity level	5
Example	PKG/5/PKG_INSTALL_ACTIVATE_FAILED: -IPAddr=192.168.79.1-User=**; Failed to execute the install activate command.
Explanation	A user executed the install activate command, but the command failed.
Recommended action	Take actions as prompted by the command.

PKG_INSTALL_ACTIVATE_SUCCESS

Message text	Executed the install activate command successfully.
Variable fields	None
Severity level	5
Example	PKG/5/PKG_INSTALL_ACTIVATE_SUCCESS: -IPAddr=192.168.79.1-User=**; Executed the install activate command successfully.
Explanation	A user executed the install activate command successfully.
Recommended action	No action is required.

PKI messages

This section contains PKI messages.

REQUEST_CERT_FAIL

Message text	Failed to request [STRING] certificate of domain [STRING].
Variable fields	$1: Certificate usage. $2: PKI domain name.
Severity level	5
Example	PKI/5/REQUEST_CERT_FAIL: Failed to request general certificate of domain abc.
Explanation	Failed to request a certificate for a PKI domain.
Recommended action	Check the configuration of the device and CA server, and the network between them.

REQUEST_CERT_SUCCESS

Message text	Request [STRING] certificate of domain [STRING] successfully.
Variable fields	$1: Certificate usage. $2: PKI domain name.
Severity level	5
Example	PKI/5/REQUEST_CERT_SUCCESS: Request general certificate of domain abc successfully.
Explanation	A certificate was successfully requested for a PKI domain.
Recommended action	No action is required.

PKT2CPU messages

This section contains PKT2CPU messages.

PKT2CPU_NO_RESOURCE

Message text	-Interface=[STRING]-ProtocolType=[UINT32]-MacAddr=[STRING]; The resources are insufficient. -Interface=[STRING]-ProtocolType=[UINT32]-SrcPort=[UINT32]-DstPort=[UINT32]; The resources are insufficient.
Variable fields	$1: Interface type and number. $2: Protocol type. $3: MAC address or source port. $4: Destination port.
Severity level	4
Example	PKT2CPU/4/PKT2CPU_NO_RESOURCE: -Interface=Ethernet0/0/2-ProtocolType=21-MacAddr=0180-c200-0014; The resources are insufficient.
Explanation	Hardware resources were insufficient.
Recommended action	Cancel the configuration.

PWDCTL messages

This section contains password control messages.

PWDCTL_ADD_BLACKLIST

Message text	[STRING] was added to the blacklist for failed login attempts.
Variable fields	$1: Username.
Severity level	6
Example	PWDCTL/6/PWDCTL_ADD_BLACKLIST: hhh was added to the blacklist for failed login attempts.
Explanation	The user entered an incorrect password. It failed to log in to the device and was added to the password control blacklist.
Recommended action	No action is required.

PWDCTL_CHANGE_PASSWORD

Message text	[STRING] changed the password because [STRING].
Variable fields	$1: Username. $2: The reasons for changing the password. · it was the first login of the account. · the password had expired. · the password was too short. · the password was not complex enough. · the password was default password
Severity level	6
Example	PWDCTL/6/PWDCTL_CHANGE_PASSWORD: hhh changed the password because it was the first login of the account.
Explanation	The user changed the password for some reason. For example, the user changed the password because it is the first login of the user's account.
Recommended action	No action is required.

PWDCTL_FAILED_TO_WRITEPWD

Message text	Failed to write the password records to file.
Variable fields	N/A
Severity level	6
Example	PWDCTL/6/PWDCTL_FAILED_TO_WRITEPWD: Failed to write the password records to file.
Explanation	The device failed to write a password to a file.
Recommended action	Check the file system of the device for memory space insufficiency.

QOS messages

This section contains QoS messages.

MIRROR_SYNC_CFG_FAIL

Message text	Failed to restore configuration for monitoring group [UINT32] in [STRING], because [STRING]
Variable fields	$1: Monitoring group. $2: Chassis number plus slot number or slot number. $3: Failure cause.
Severity level	4
Example	QOS/4/MIRROR_SYNC_CFG_FAIL: Failed to restore configuration for monitoring group 1 in chassis 2 slot 1, because monitoring resources are insufficient.
Explanation	After a card was installed, the system failed to restore the configuration for a monitoring group on the card for the following possible reasons: · The number of member ports in the monitoring group exceeds the limit. · The monitoring resources are insufficient on the card. · Member ports in the monitoring group are not supported by the card.
Recommended action	Delete or modify unsupported settings.

QOS_CAR_APPLYUSER_FAIL

Message text	[STRING]; Failed to apply the [STRING] CAR in [STRING] profile [STRING] to the user. Reason: [STRING].
Variable fields	$1: User identity. $2: Application direction. $3: Profile type. $4: Profile name. $5: Failure cause.
Severity level	4
Example	QOS/4/QOS_CAR_APPLYUSER_FAIL: -MAC=1111-2222-3333-IP=192.168.1.2-SVLAN=100-VPN=”N/A”-Port=GigabitEthernet5/1/5; Failed to apply the inbound CAR in user profile a to the user. Reason: The resources are insufficient.
Explanation	The system failed to perform one of the following actions: · Apply a CAR policy when a user went online. · Modify a configured CAR policy or configure a new CAR policy when a user is online.
Recommended action	Delete the CAR policy from the profile or modify the parameters of the CAR policy.

QOS_CBWFQ_REMOVED

Message text	CBWFQ is removed from [STRING].
Variable fields	$1: Interface name.
Severity level	3
Example	QOS/3/QOS_CBWFQ_REMOVED: CBWFQ is removed from GigabitEthernet4/0/1.
Explanation	CBWFQ was removed from an interface because the maximum bandwidth or speed configured on the interface was below the bandwidth or speed required for CBWFQ.
Recommended action	Increase the bandwidth or speed and apply the removed CBWFQ again.

QOS_GTS_APPLYUSER_FAIL

Message text	[STRING]; Failed to apply GTS in user profile [STRING] to the user. Reason: [STRING].
Variable fields	$1: User identity. $2: User profile name. $3: Failure cause.
Severity level	4
Example	QOS/4/QOS_GTS_APPLYUSER_FAIL: -MAC=1111-2222-3333-IP=192.168.1.2/16-CVLAN=100-Port=GigabitEthernet5/1/5; Failed to apply GTS in user profile a to the user. Reason: The resources are insufficient.
Explanation	The system failed to perform one of the following actions: · Apply a GTS action when a user went online. · Modify a configured GTS action or configure a new GTS action when a user is online.
Recommended action	Delete the GTS action from the user profile or modify the parameters of the GTS action.

QOS_IFA_OUTPUT_IFFAIL

Message text	Failed to find an output interface for destination IP address [STRING].
Variable fields	$1: IP address.
Severity level	4
Example	QOS/4/QOS_IFA_OUTPUT_IFFAIL: Failed to find an output interface for destination IP address 1.1.1.1.
Explanation	The system failed to find an output interface for a destination IP address.
Recommended action	Check whether the route is available.

QOS_IFA_REFRESH_FAIL

Message text	Failed to refresh IFA action [UINT32] on interface [STRING].
Variable fields	$1: INT action ID. $2: Interface name.
Severity level	4
Example	QOS/4/QOS_IFA_REFRESH_FAIL: Failed to refresh IFA action 1 on interface GigabitEthernet1/0/1.
Explanation	The system failed to issue an INT action to an interface.
Recommended action	1. Check whether the ACL in the action is correctly configured. 2. Reconfigure the action.

QOS_NOT_ENOUGH_BANDWIDTH

Message text	Policy [STRING] requested bandwidth [UINT32](kbps). Only [UINT32](kbps) is available on [STRING].
Variable fields	$1: Policy name. $2: Required bandwidth for CBWFQ. $3: Available bandwidth on an interface. $4: Interface name.
Severity level	3
Example	QOS/3/QOS_NOT_ENOUGH_BANDWIDTH: Policy d requested bandwidth 10000(kbps). Only 80(kbps) is available on GigabitEthernet4/0/1.
Explanation	Configuring CBWFQ on an interface failed because the maximum bandwidth on the interface was less than the bandwidth required for CBWFQ.
Recommended action	Increase the maximum bandwidth configured for the interface or set lower bandwidth required for CBWFQ.

QOS_NOT_ENOUGH_NNIBANDWIDTH

Message text	The total UNI bandwidth is greater than the NNI bandwidth. The total UNI bandwidth is greater than the NNI bandwidth. The bandwidth of [STRING] is changed. The total UNI bandwidth is greater than the NNI bandwidth. [STRING] is created based on [STRING] of the UNI interface
Variable fields	$1: Interface name.
Severity level	4
Example	QOS/4/ QOS_NOT_ENOUGH_NNIBANDWIDTH: The total UNI bandwidth is greater than the NNI bandwidth. QOS/4/ QOS_NOT_ENOUGH_NNIBANDWIDTH: The total UNI bandwidth is greater than the NNI bandwidth. The bandwidth of GigabitEthernet4/0/1 is changed. QOS/4/ QOS_NOT_ENOUGH_NNIBANDWIDTH: The total UNI bandwidth is greater than the NNI bandwidth. Virtual-Access1 is created based on Virtual-Template1 of the UNI interface.
Explanation	This message is generated when the total UNI bandwidth is still greater than the NNI bandwidth after the NNI bandwidth is increased or the total UNI bandwidth is reduced. This message is generated when the total UNI bandwidth is greater than the NNI bandwidth because the interface bandwidth is changed. This message is generated when the total UNI bandwidth is greater than the NNI bandwidth because a virtual access interface is created based on a virtual template of the UNI interface.
Recommended action	Increase the NNI bandwidth or reduce the total UNI bandwidth.

QOS_POLICY_APPLYCOPP_CBFAIL

Message text	Failed to apply classifier-behavior [STRING] in policy [STRING] to the [STRING] direction of control plane slot [UINT32]. [STRING].
Variable fields	$1: Name of a classifier-behavior association. $2: Policy name. $3: Application direction. $4: Slot number. $5: Failure cause.
Severity level	4
Example	QOS/4/QOS_POLICY_APPLYCOPP_CBFAIL: Failed to apply classifier-behavior d in policy b to the inbound direction of control plane slot 3. The behavior is empty.
Explanation	The system failed to perform one of the following actions: Apply a classifier-behavior association to a specific direction of a control plane. Update a classifier-behavior association applied to a specific direction of a control plane.
Recommended action	Modify the configuration of the QoS policy according to the failure cause.

QOS_POLICY_APPLYCOPP_FAIL

Message text	Failed to apply or refresh QoS policy [STRING] to the [STRING] direction of control plane slot [UINT32]. [STRING].
Variable fields	$1: Policy name. $2: Traffic direction. $3: Slot number. $4: Failure cause.
Severity level	4
Example	QOS/4/QOS_POLICY_APPLYCOPP_FAIL: Failed to apply or refresh QoS policy b to the inbound direction of control plane slot 3. The operation is not supported.
Explanation	The system failed to perform one of the following actions: · Apply a QoS policy to a specific direction of a control plane. · Update a QoS policy applied to a specific direction of a control plane.
Recommended action	Modify the configuration of the QoS policy according to the failure cause.

QOS_POLICY_APPLYGLOBAL_CBFAIL

Message text	Failed to apply classifier-behavior [STRING] in policy [STRING] to the [STRING] direction globally. [STRING].
Variable fields	$1: Name of a classifier-behavior association. $2: Policy name. $3: Traffic direction. $4: Failure cause.
Severity level	4
Example	QOS/4/QOS_POLICY_APPLYGLOBAL_CBFAIL: Failed to apply classifier-behavior a in policy b to the outbound direction globally. The behavior is empty.
Explanation	The system failed to perform one of the following actions: · Apply a classifier-behavior association to a specific direction globally. · Update a classifier-behavior association applied to a specific direction globally.
Recommended action	Modify the configuration of the QoS policy according to the failure cause.

QOS_POLICY_APPLYGLOBAL_FAIL

Message text	Failed to apply or refresh QoS policy [STRING] to the [STRING] direction globally. [STRING].
Variable fields	$1: Policy name. $2: Traffic direction. $3: Failure cause.
Severity level	4
Example	QOS/4/QOS_POLICY_APPLYGLOBAL_FAIL: Failed to apply or refresh QoS policy b to the inbound direction globally. The operation is not supported.
Explanation	The system failed to perform one of the following actions: · Apply a QoS policy to a specific direction globally. · Update a QoS policy applied to a specific direction globally.
Recommended action	Modify the configuration of the QoS policy according to the failure cause.

QOS_POLICY_APPLYIF_CBFAIL

Message text	Failed to apply classifier-behavior [STRING] in policy [STRING] to the [STRING] direction of interface [STRING]. [STRING].
Variable fields	$1: Name of a classifier-behavior association. $2: Policy name. $3: Traffic direction. $4: Interface name. $5: Failure cause.
Severity level	4
Example	QOS/4/QOS_POLICY_APPLYIF_CBFAIL: Failed to apply classifier-behavior b in policy b to the inbound direction of interface Ethernet3/1/2. The behavior is empty.
Explanation	The system failed to perform one of the following actions: · Apply a classifier-behavior association to a specific direction of an interface. · Update a classifier-behavior association applied to a specific direction of an interface.
Recommended action	Modify the configuration of the QoS policy according to the failure cause.

QOS_POLICY_APPLYIF_FAIL

Message text	Failed to apply or refresh QoS policy [STRING] to the [STRING] direction of interface [STRING]. [STRING].
Variable fields	$1: Policy name. $2: Traffic direction. $3: Interface name. $4: Failure cause.
Severity level	4
Example	QOS/4/QOS_POLICY_APPLYIF_FAIL: Failed to apply or refresh QoS policy b to the inbound direction of interface Ethernet3/1/2. The operation is not supported.
Explanation	The system failed to perform one of the following actions: · Apply a QoS policy to a specific direction of an interface. · Update a QoS policy applied to a specific direction of an interface.
Recommended action	Modify the configuration of the QoS policy according to the failure cause.

QOS_POLICY_APPLYUSER_FAIL

Message text	[STRING]; Failed to apply the [STRING] QoS policy [STRING] in user profile [STRING] to the user.Reason: [STRING].
Variable fields	$1: User identity. $2: Application direction. $3: QoS policy name. $4: User profile name. $5: Failure cause.
Severity level	4
Example	QOS/4/QOS_POLICY_APPLYUSER_FAIL: -MAC=1111-2222-3333-IP=192.168.1.2/16-CVLAN=100-Port=GigabitEthernet5/1/5; Failed to apply the inbound QoS policy p in user profile a to the user.Reason: The QoS policy is not supported.
Explanation	The system failed to perform one of the following actions: · Issue the settings of a QoS policy when a user went online. · Modify an applied QoS policy or apply a new QoS policy when a user is online.
Recommended action	Remove the QoS policy from the user profile or modify the parameters of the QoS policy.

QOS_POLICY_APPLYVLAN_CBFAIL

Message text	Failed to apply classifier-behavior [STRING] in policy [STRING] to the [STRING] direction of VLAN [UINT32]. [STRING].
Variable fields	$1: Name of a classifier-behavior association. $2: Policy name. $3: Application direction. $4: VLAN ID. $5: Failure cause.
Severity level	4
Example	QOS/4/QOS_POLICY_APPLYVLAN_CBFAIL: Failed to apply classifier-behavior b in policy b to the inbound direction of VLAN 2. The behavior is empty.
Explanation	The system failed to perform one of the following actions: · Apply a classifier-behavior association to a specific direction of a VLAN. · Update a classifier-behavior association applied to a specific direction of a VLAN.
Recommended action	Modify the configuration of the QoS policy according to the failure cause.

QOS_POLICY_APPLYVLAN_FAIL

Message text	Failed to apply or refresh QoS policy [STRING] to the [STRING] direction of VLAN [UINT32]. [STRING].
Variable fields	$1: Policy name. $2: Application direction. $3: VLAN ID. $4: Failure cause.
Severity level	4
Example	QOS/4/QOS_POLICY_APPLYVLAN_FAIL: Failed to apply or refresh QoS policy b to the inbound direction of VLAN 2. The operation is not supported.
Explanation	The system failed to perform one of the following actions: · Apply a QoS policy to a specific direction of a VLAN. · Update a QoS policy applied to a specific direction of a VLAN.
Recommended action	Modify the configuration of the QoS policy according to the failure cause.

QOS_QMPROFILE_APPLYUSER_FAIL

Message text	[STRING]; Failed to apply queue management profile [STRING] in session group profile [STRING] to the user. Reason: [STRING].
Variable fields	$1: User identity. $2: Queue scheduling profile name. $3: Session group profile name. $4: Failure cause.
Severity level	4
Example	QOS/4/QOS_QMPROFILE_APPLYUSER_FAIL: -MAC=1111-2222-3333-IP=192.168.1.2/16-SVLAN=100-Port=GigabitEthernet5/1/5; Failed to apply queue management profile b in session group profile a to the user. Reason: The QMProfile is not supported.
Explanation	The system failed to perform one of the following actions: · Issue the settings of a queue scheduling profile when a user went online. · Modify an applied queue scheduling profile or apply a new queue scheduling profile when a user is online.
Recommended action	Remove the queue scheduling profile from the session group profile or modify the parameters of the queue scheduling profile.

QOS_QMPROFILE_MODIFYQUEUE_FAIL

Message text	Failed to configure queue [UINT32] in queue scheduling profile [STRING]. [STRING].
Variable fields	$1: Queue ID. $2: Profile name. $3: Failure cause.
Severity level	4
Example	QOS/4/QOS_QMPROFILE_MODIFYQUEUE_FAIL: Failed to configure queue 1 in queue scheduling profile myqueue. The value is out of range.
Explanation	The system failed to modify a queue in a queue scheduling profile successfully applied to an interface because the new parameter was beyond port capabilities.
Recommended action	Remove the queue scheduling profile from the interface, and then modify the parameters for the queue.

QOS_UNI_RESTORE_FAIL

Message text	Failed to restore the UNI configuration of [STRING], because the total UNI bandwidth is greater than the NNI bandwidth.
Variable fields	$1: Interface name.
Severity level	4
Example	QOS/4/ QOS_NNIBANDWIDTH_OVERFLOW: Failed to restore the UNI configuration of the interface GigabitEthernet5/1/5, because the total UNI bandwidth is greater than the NNI bandwidth.
Explanation	The system failed to restore the UNI configuration of an interface, because the total UNI bandwidth is greater than the NNI bandwidth.
Recommended action	Increase the NNI bandwidth or reduce the total UNI bandwidth, and then reconfigure the downlink ports as UNI ports.

WRED_TABLE_CFG_FAIL

Message text	Failed to dynamically modify the configuration of WRED table [STRING], because [STRING].
Variable fields	$1: WRED table name. $2: Failure cause.
Severity level	4
Example	QOS/4/WRED_TABLE_CFG_FAIL: Failed to dynamically modify the configuration of WRED table a, because ECN is not supported.
Explanation	Failed to dynamically modify the configuration of a WRED table, because some settings are not supported.
Recommended action	No action is required.

RADIUS messages

This section contains RADIUS messages.

RADIUS_AUTH_FAILURE

Message text	User [STRING] from [STRING] failed authentication.
Variable fields	$1: Username. $2: IP address.
Severity level	5
Example	RADIUS/5/RADIUS_AUTH_FAILURE: User abc@system from 192.168.0.22 failed authentication.
Explanation	An authentication request was rejected by the RADIUS server.
Recommended action	No action is required.

RADIUS_AUTH_SUCCESS

Message text	User [STRING] from [STRING] was authenticated successfully.
Variable fields	$1: Username. $2: IP address.
Severity level	6
Example	RADIUS/6/RADIUS_AUTH_SUCCESS: User abc@system from 192.168.0.22 was authenticated successfully.
Explanation	An authentication request was accepted by the RADIUS server.
Recommended action	No action is required.

RADIUS_DELETE_HOST_FAIL

Message text	Failed to delete servers in scheme [STRING].
Variable fields	$1: Scheme name.
Severity level	4
Example	RADIUS/4/RADIUS_DELETE_HOST_FAIL: Failed to delete servers in scheme abc.
Explanation	Failed to delete servers from a RADIUS scheme.
Recommended action	No action is required.

RIP messages

This section contains RIP messages.

RIP_MEM_ALERT

Message text	RIP Process received system memory alert [STRING] event.
Variable fields	$1: Type of the memory alarm.
Severity level	5
Example	RIP/5/RIP_MEM_ALERT: RIP Process received system memory alert start event.
Explanation	RIP received a memory alarm.
Recommended action	Check the system memory and release memory for the modules that occupy too many memory resources.

RIP_RT_LMT

Message text	RIP [UINT32] Route limit reached
Variable fields	$1: Process ID.
Severity level	6
Example	RIP/6/RIP_RT_LMT: RIP 1 Route limit reached.
Explanation	The number of routes of a RIP process reached the upper limit.
Recommended action	3. Check for network attacks. 4. Reduce the number of routes.

RIPNG messages

This section contains RIPng messages.

RIPNG_MEM_ALERT

Message text	RIPng Process received system memory alert [STRING] event.
Variable fields	$1: Type of the memory alarm.
Severity level	5
Example	RIPNG/5/RIPNG_MEM_ALERT: RIPNG Process received system memory alert start event.
Explanation	RIPng received a memory alarm.
Recommended action	Check the system memory and release memory for the modules that occupy too many memory resources.

RIPNG_RT_LMT

Message text	RIPng [UINT32] Route limit reached
Variable fields	$1: Process ID
Severity level	6
Example	RIPNG/6/RIPNG_RT_LMT: RIPng 1 Route limit reached.
Explanation	The number of routes of a RIPng process reached the upper limit.
Recommended action	5. Check for network attacks. 6. Reduce the number of routes.

RM messages

This section contains RM messages.

RM_ACRT_REACH_LIMIT

Message text	Max active [STRING] routes [UINT32] reached in URT of [STRING]
Variable fields	$1: IPv4 or IPv6. $2: Maximum number of active routes. $3: VPN instance name.
Severity level	4
Example	RM/4/RM_ACRT_REACH_LIMIT: Max active IPv4 routes 100000 reached in URT of VPN1
Explanation	The number of active routes reached the upper limit in the unicast routing table of a VPN instance.
Recommended action	Remove unused active routes.

RM_ACRT_REACH_THRESVALUE

Message text	Threshold value [UINT32] of max active [STRING] routes reached in URT of [STRING]
Variable fields	$1: Threshold of the maximum number of active routes in percentage. $2: IPv4 or IPv6. $3: VPN instance name.
Severity level	4
Example	RM/4/RM_ACRT_REACH_THRESVALUE: Threshold value 50% of max active IPv4 routes reached in URT of vpn1
Explanation	The percentage of the maximum number of active routes was reached in the unicast routing table of a VPN instance.
Recommended action	Modify the threshold value or the route limit configuration.

RM_THRESHLD_VALUE_REACH

Message text	Threshold value [UINT32] of active [STRING] routes reached in URT of [STRING]
Variable fields	$1: Maximum number of active routes. $2: IPv4 or IPv6. $3: VPN instance name.
Severity level	4
Example	RM/4/RM_THRESHLD_VALUE_REACH: Threshold value 10000 of active IPv4 routes reached in URT of vpn1
Explanation	The number of active routes reached the threshold in the unicast routing table of a VPN instance.
Recommended action	Modify the route limit configuration.

RRPP messages

This section contains RRPP messages.

RRPP_RING_FAIL

Message text	Ring [UINT32] in Domain [UINT32] failed.
Variable fields	$1: Ring ID. $2: Domain ID.
Severity level	4
Example	RRPP/4/RRPP_RING_FAIL: Ring 1 in Domain 1 failed.
Explanation	A ring failure occurred in the RRPP domain.
Recommended action	Check each RRPP node to clear the network fault.

RRPP_RING_RESTORE

Message text	Ring [UINT32] in Domain [UINT32] recovered.
Variable fields	$1: Ring ID. $2: Domain ID.
Severity level	4
Example	RRPP/4/RRPP_RING_RESTORE: Ring 1 in Domain 1 recovered.
Explanation	The ring in the RRPP domain was recovered.
Recommended action	No action is required.

RTM messages

This section contains RTM messages.

RTM_TCL_NOT_EXIST

Message text	Failed to execute Tcl-defined policy [STRING] because the policy's Tcl script file was not found.
Variable fields	$1: Name of a Tcl-defined policy.
Severity level	4
Example	RTM/4/RTM_TCL_NOT_EXIST: Failed to execute Tcl-defined policy aaa because the policy's Tcl script file was not found.
Explanation	The system did not find the Tcl script file for the policy while executing the policy.
Recommended action	1. Check that the Tcl script file exists. 2. Reconfigure the policy.

RTM_TCL_MODIFY

Message text	Failed to execute Tcl-defined policy [STRING] because the policy's Tcl script file had been modified.
Variable fields	$1: Name of a Tcl-defined policy.
Severity level	4
Example	RTM/4/RTM_TCL_MODIFY: Failed to execute Tcl-defined policy aaa because the policy's Tcl script file had been modified.
Explanation	The Tcl script file for the policy was modified.
Recommended action	Reconfigure the policy, or modify the Tcl script to be the same as it was when it was bound with the policy.

RTM_TCL_LOAD_FAILED

Message text	Failed to load the Tcl script file of policy [STRING].
Variable fields	$1: Name of a Tcl-defined policy.
Severity level	4
Example	RTM/4/RTM_TCL_LOAD_FAILED: Failed to load the Tcl script file of policy [STRING].
Explanation	The system failed to load the Tcl script file for the policy to memory.
Recommended action	No action is required.

SCMD messages

This section contains SCMD messages.

PROCESS_ABNORMAL

Message text	The process [STRING] exited abnormally. ServiceName=[STRING], ExitCode=[STRING], KillSignal=[STRING], StartTime=[STRING], StopTime=[STRING].
Variable fields	$1: Process name. $2: Service name defined in the script. $3: Process exit code. If the process was closed by a signal, this field displays NA. $4: Signal that closed the process. If the process was not closed by a signal, this field displays NA. $5: Time when the process was created. $6: Time when the process was closed.
Severity level	4
Example	SCMD/4/PROCESS_ABNORMAL: The process diagd exited abnormally. ServiceName=DIAG, ExitCode=1, KillSignal=NA, StartTime=2019-03-06 14:18:06, StopTime=2019-03-06 14:35:25.
Explanation	A process exited abnormally. You can use the process parameters for troubleshooting.
Recommended action	1. Use the display process command to identify whether the process exists. If the process exists, the process is recovered. 2. If the process is not recovered, collect the following information: a. Execute the view /var/log/trace.log > trace.log command in probe view, and transfer the trace.log file saved in the storage media of the device to the server through FTP or TFTP. To use FTP, set the transfer mode to binary. b. To quickly troubleshoot the issue, leave the device as is and contact H3C Support. 3. If the process has been recovered, but reasons need to be located, go to step 2.

PROCESS_ACTIVEFAILED

Message text	The standby process [STRING] failed to switch to the active process due to uncompleted synchronization, and was restarted.
Variable fields	$1: Process name.
Severity level	4
Example	SCMD/4/PROCESS_ACTIVEFAILED: The standby process diagd failed to switch to the active process due to uncompleted synchronization, and was restarted.
Explanation	The standby process failed to switch to the active process because the active process exited abnormally when the standby process has not completed synchronization. The standby process was restarted.
Recommended action	No action is required.

PROCESS_CORERECORD

Message text	Exceptions occurred with process [STRING]. A core dump file was generated.
Variable fields	$1: Process name.
Severity level	4
Example	SCMD/4/PROCESS_CORERECORD: Exceptions occurred with process diagd. A core dump file was generated.
Explanation	A process had exceptions and a core dump file was generated.
Recommended action	1. Use the display exception context command to collect and save process exception information to a file. 2. Use the display exception filepath command to display the core dump file directory. 3. Use FTP to TFTP to transfer the core dump file and the file that stores the process exception information to a file server. To use FTP, set the transfer mode to binary. 4. To quickly troubleshoot the issue, leave the device as is and contact H3C Support.

SCM_ABNORMAL_REBOOT

Message text	Failed to restore process [STRING]. Rebooting [STRING].
Variable fields	$1: Process name. $2: Chassis number and slot number, slot number, or string the system.
Severity level	3
Example	SCMD/3/SCM_ABNORMAL_REBOOT: Failed to restore process ipbased. Rebooting slot 1.
Explanation	The process exited abnormally during the device startup. If the process cannot recover after multiple automatic restart attempts, the slot or device will restart automatically.
Recommended action	1. Use the display process command to verify that the process has recovered after the card or device restarts. 2. If the problem persists, contact H3C Support.

SCM_ABNORMAL_REBOOTMDC

Message text	Failed to restore process [STRING] on [STRING] [UINT16]. Rebooting [STRING] [UINT16].
Variable fields	$1: Process name. $2: Object type, MDC or context. $3: ID of the MDC or context. $4: Object type, MDC or context. $5: ID of the MDC or context.
Severity level	3
Example	SCMD/3/SCM_ABNORMAL_REBOOTMDC: Failed to restore process ipbased on MDC 2. Rebooting MDC 2.
Explanation	The process exited abnormally during the startup of the MDC on the active MPU or the context on the main security engine in the security engine group. If the process cannot recover after multiple automatic restart attempts, the MDC or context will restart automatically. This message will be output in MDC 1 or Context 1.
Recommended action	1. Use the display process command to verify that the process has recovered after the card restarts. 2. If the problem persists, contact H3C Support.

SCM_ABORT_RESTORE

Message text	Failed to restore process [STRING]. Restoration aborted.
Variable fields	$1: Process name.
Severity level	3
Example	SCMD/3/SCM_ABORT_RESTORE: Failed to restore process ipbased. Restoration aborted.
Explanation	The process exited abnormally during the system operation. If the process cannot recover after multiple automatic restart attempts, the device will not restore the process.
Recommended action	1. Use the display process log command in any view to display the details about process exit. 2. Restart the card or the MDC where the process is located. 3. Provide the output from the display process log command to H3C Support.

SCM_INSMOD_ADDON_TOOLONG

Message text	Failed to finish loading [STRING] in [UINT32] minutes.
Variable fields	$1: Kernel file name. $2: File loading duration.
Severity level	4
Example	SCMD/4/SCM_INSMOD_ADDON_TOOLONG: Failed to finish loading addon.ko in 30 minutes.
Explanation	Kernel file loading timed out during device startup.
Recommended action	1. Restart the card. 2. Contact H3C Support.

SCM_KERNEL_INIT_TOOLONG

Message text	Kernel init in sequence [STRING] function [STRING] is still starting for [UINT32] minutes.
Variable fields	$1: Kernel event phase. $2: Address of the function corresponding to the kernel event. $3: Time duration.
Severity level	4
Example	SCMD/4/SCM_KERNEL_INIT_TOOLONG: Kernel init in sequence 0x25e7 function 0x6645ffe2 is still starting for 15 minutes.
Explanation	A function at a phase during kernel initialization ran too long.
Recommended action	1. Restart the card. 2. Contact H3C Support.

SCM_PROCESS_STARTING_TOOLONG

Message text	Pattern 1: The process [STRING] has not finished starting in [UINT32] hours. Pattern 2: The process [STRING] on [STRING] [UINT16] has not finished starting in [STRING] hours.
Variable fields	Pattern 1: $1: Process name. $2: Time duration. Pattern 2: $1: Process name. $2: Object type, MDC or context. $3: ID of the MDC or context. $4: Time duration.
Severity level	4
Example	SCMD/4/SCM_PROCESS_STARTING_TOOLONG: The process ipbased has not finished starting in 1 hours.
Explanation	The process initialization takes a long time and has not been finished. Too many processes have been configured or the process is abnormal.
Recommended action	1. Wait 6 hours and then verify that the process has been started. 2. Restart the card/MDC/context, and then use the display process command to verify that the process has recovered. 3. Contact H3C Support.

SCM_SKIP_PROCESS

Message text	Pattern 1: The process [STRING] was skipped because it failed to start within 6 hours. Pattern 2: The process [STRING] on [STRING] [UINT16] was skipped because it failed to start within 6 hours.
Variable fields	Pattern 1: $1: Process name. Pattern 2: $1: Process name. $2: Object type, MDC or context. $3: ID of the MDC or context.
Severity level	3
Example	SCMD/3/SCM_SKIP_PROCESS: The process ipbased was skipped because it failed to start within 6 hours.
Explanation	A process failed to start within 6 hours. The device will skip this process and continue to start.
Recommended action	1. Restart the card/MDC/context, and then use the display process command to verify that the process has restored. 2. Contact H3C Support.

SESSION messages

This section contains session messages.

SESSION_IPV4_FLOW

Message text	Protocol(1001)=[STRING];SrcIPAddr(1003)=[IPADDR];SrcPort(1004)=[UINT16];NATSrcIPAddr(1005)=[IPADDR];NATSrcPort(1006)=[UINT16];DstIPAddr(1007)=[IPADDR];DstPort(1008)=[UINT16];NATDstIPAddr(1009)=[IPADDR];NATDstPort(1010)=[UINT16];InitPktCount(1044)=[UINT32];InitByteCount(1046)=[UINT32];RplyPktCount(1045)=[UINT32];RplyByteCount(1047)=[UINT32];RcvVPNInstance(1042)=[STRING];SndVPNInstance(1043)=[STRING];RcvDSLiteTunnelPeer(1040)=[STRING];SndDSLiteTunnelPeer(1041)=[STRING];BeginTime_e(1013)=[STRING];EndTime_e(1014)=[STRING];Event(1048)=([UNIT16])[STRING];
Variable fields	$1: Protocol type. $2: Source IP address. $3: Source port number. $4: Source IP address after translation. $5: Source port number after translation.. $6: Destination IP address. $7: Destination port number. $8: Destination IP address after translation. $9: Destination port number after translation. $10: Total number of inbound packets. $11: Total number of inbound bytes. $12: Total number of outbound packets. $13: Total number of outbound bytes. $14: Source VPN instance name. $15: Destination VPN instance name. $16: Source DS-Lite tunnel. This field is not supported in the current software version. $17: Destination DS-Lite tunnel. This field is not supported in the current software version. $18: Time when the session is created. $19: Time when the session is removed. $20: Event type. $20: Event description: Session created. Active flow threshold. Normal over. Aged for timeout. Aged for reset or config-change. Other.
Severity level	6
Example	SESSION/6/SESSION_IPV4_FLOW: Protocol(1001)=UDP;SrcIPAddr(1003)=10.10.10.1;SrcPort(1004)=1024;NATSrcIPAddr(1005)=10.10.10.1;NATSrcPort(1006)=1024;DstIPAddr(1007)=20.20.20.1;DstPort(1008)=21;NATDstIPAddr(1009)=20.20.20.1;NATDstPort(1010)=21;InitPktCount(1044)=1;InitByteCount(1046)=50;RplyPktCount(1045)=0;RplyByteCount(1047)=0;RcvVPNInstance(1042)=;SndVPNInstance(1043)=;RcvDSLiteTunnelPeer(1040)=;SndDSLiteTunnelPeer(1041)=;BeginTime_e(1013)=03182024082546;EndTime_e(1014)=;Event(1048)=(8)Session created;
Explanation	This message is sent in one of the following conditions: An IPv4 session is created or removed. Periodically during an IPv4 session. The traffic-based or time-based threshold of an IPv4 session is reached.
Recommended action	No action is required.

SESSION_IPV6_FLOW

Message text	Protocol(1001)=[STRING];SrcIPv6Addr(1036)=[IPADDR];SrcPort(1004)=[UINT16];DstIPv6Addr(1037)=[IPADDR];DstPort(1008)=[UINT16];InitPktCount(1044)=[UINT32];InitByteCount(1046)=[UINT32];RplyPktCount(1045)=[UINT32];RplyByteCount(1047)=[UINT32];RcvVPNInstance(1042)=[STRING];SndVPNInstance(1043)=[STRING];BeginTime_e(1013)=[STRING];EndTime_e(1014)=[STRING];Event(1048)=([UNIT16])[STRING];
Variable fields	$1: Protocol type. $2: Source IPv6 address. $3: Source port number. $4: Destination IP address. $5: Destination port number. $6: Total number of inbound packets. $7: Total number of inbound bytes. $8: Total number of outbound packets. $9: Total number of outbound bytes. $10: Source VPN instance name. $11: Destination VPN instance name. $12: Time when the session is created. $13: Time when the session is removed. $14: Event type. $15: Event description: Session created. Active flow threshold. Normal over. Aged for timeout. Aged for reset or config-change. Other.
Severity level	6
Example	SESSION/6/SESSION_IPV6_FLOW: Protocol(1001)=UDP;SrcIPv6Addr(1036)=2001::2;SrcPort(1004)=1024;DstIPv6Addr(1037)=3001::2;DstPort(1008)=53;InitPktCount(1044)=1;InitByteCount(1046)=110;RplyPktCount(1047)=0;RplyByteCount(1047)=0;RcvVPNInstance(1042)=;SndVPNInstance(1043)=;BeginTime_e(1013)=03182024082901;EndTime_e(1014)=;Event(1048)=(8)Session created;
Explanation	This message is sent in one of the following conditions: · An IPv6 session is created or removed. · Periodically during an IPv6 session. · The traffic-based or time-based threshold of an IPv6 session is reached.
Recommended action	No action is required.

SFLOW messages

This section contains sFlow messages.

SFLOW_HARDWARE_ERROR

Message text	Failed to [STRING] on interface [STRING] due to [STRING].
Variable fields	$1: Configuration item: update sampling mode $2: Interface name. $3: Failure reason: not supported operation
Severity level	4
Example	SFLOW/4/SFLOW_HARDWARE_ERROR: Failed to update sampling mode on interface GigabitEthernet1/0/1 due to not supported operation.
Explanation	The configuration failed because the device does not support the fixed flow sampling mode.
Recommended action	Specify the random flow sampling mode.

SHELL messages

This section contains shell messages.

SHELL_CMD

Message text	-Line=[STRING]-IPAddr=[STRING]-User=[STRING]; Command is [STRING]
Variable fields	$1: User line type and number. If there is not user line information, this field displays . $2: IP address. If there is not IP address information, this field displays . $3: Username. If there is not username information, this field displays **. $4: Command string.
Severity level	6
Example	SHELL/6/SHELL_CMD: -Line=aux0-IPAddr=-User=; Command is quit
Explanation	A command was successfully executed.
Recommended action	No action is required.

SHELL_CMD_CONFIRM

Message text	Confirm option of command [STRING] is [STRING].
Variable fields	$1: Command string. $2: Confirm option.
Severity level	6
Example	SHELL/6/SHELL_CMD_CONFIRM: Confirm option of command save is no.
Explanation	A user selected a confirmation option for a command.
Recommended action	No action is required.

SHELL_CMD_EXECUTEFAIL

Message text	-User=[STRING]-IPAddr=[STRING]; Command [STRING] in view [STRING] failed to be executed.
Variable fields	$1: Username. $2: IP address. $3: Command string. $4: Command view.
Severity level	4
Example	SHELL/4/SHELL_CMD_EXECUTEFAIL: -User=**-IPAddr=192.168.62.138; Command save in view system failed to be executed.
Explanation	A command failed to be executed.
Recommended action	No action is required.

SHELL_CMD_INPUT

Message text	Input string for the [STRING] command is [STRING].
Variable fields	$1: Command string. $2: String entered by the user.
Severity level	6
Example	SHELL/6/SHELL_CMD_INPUT: Input string for the save command is startup.cfg. SHELL/6/SHELL_CMD_INPUT: Input string for the save command is CTRL_C. SHELL/6/SHELL_CMD_INPUT: Input string for the save command is the Enter key.
Explanation	A user responded to the input requirement of a command.
Recommended action	No action is required.

SHELL_CMD_INPUT_TIMEOUT

Message text	Operation timed out: Getting input for the [STRING] command.
Variable fields	$1: Command string.
Severity level	6
Example	SHELL/6/SHELL_CMD_INPUT_TIMEOUT: Operation timed out: Getting input for the fdisk command.
Explanation	The user did not respond to the input requirement of a command before the timeout timer expired.
Recommended action	No action is required.

SHELL_CMD_INVALID_CHARACTER

Message text	Execution failed for the [STRING] command. Reason: The command contains invalid characters (? or \t).
Variable fields	$1: Command string.
Severity level	6
Example	SHELL/6/SHELL_CMD_INVALID_CHARACTER: Execution failed for the sysname abc?? command. Reason: The command contains invalid characters (? or \t).
Explanation	The device detected invalid characters in a command line of a text-type configuration file during a configuration recovery or rollback.
Recommended action	Correct the mistakes in the command line and execute the command.

SHELL_CMD_MATCHFAIL

Message text	-User=[STRING]-IPAddr=[STRING]; Command [STRING] in view [STRING] failed to be matched.
Variable fields	$1: Username. $2: IP address. $3: Command string. $4: Command view.
Severity level	4
Example	SHELL/4/SHELL_CMD_MATCHFAIL: -User=**-IPAddr=192.168.62.138; Command description 10 in view system failed to be matched.
Explanation	The command string has errors, or the view does not support the command.
Recommended action	Enter the correct command string. Make sure the command is supported in the view.

SHELL_CMDDENY

Message text	-Line=[STRING]-IPAddr=[STRING]-User=[STRING]; Command=[STRING] is denied.
Variable fields	$1: User line type and number. If there is not user line information, this field displays . $2: IP address. If there is not IP address information, this field displays . $3: Username. If there is not username information, this field displays **. $4: Command string.
Severity level	5
Example	SHELL/5/SHELL_CMDDENY: -Line=vty0-IPAddr=192.168.62.138-User=**; Command vlan 10 is permission denied.
Explanation	The user did not have the right to execute the command.
Recommended action	No action is required.

SHELL_CMDFAIL

Message text	Command [STRING] failed to restore the configuration.
Variable fields	$1: Command string.
Severity level	6
Example	SHELL/6/SHELL_CMDFAIL: The “save” command failed to restore the configuration.
Explanation	The command failed to restore the configuration.
Recommended action	No action is required.

SHELL_CRITICAL_CMDFAIL

Message text	-User=[STRING]-IPAddr=[STRING]; Command=[STRING] .
Variable fields	$1: Username. $2: IP address. $3: Command string.
Severity level	6
Example	SHELL/6/SHELL_CRITICAL_CMDFAIL: -User=admin-IPAddr=169.254.0.7; Command is save.
Explanation	A command failed to be executed or was canceled.
Recommended action	No action is required.

SHELL_LOGIN

Message text	[STRING] logged in from [STRING].
Variable fields	$1: Username. $2: User line type and number.
Severity level	5
Example	SHELL/5/SHELL_LOGIN: Console logged in from console0.
Explanation	A user logged in. If the user logged in to the standby MPU, the user line type and number field displays local.
Recommended action	No action is required.

SHELL_LOGOUT

Message text	[STRING] logged out from [STRING].
Variable fields	$1: Username. $2: User line type and number.
Severity level	5
Example	SHELL/5/SHELL_LOGOUT: Console logged out from console0.
Explanation	A user logged out. If the user logged out from the standby MPU, the user line type and number field displays local.
Recommended action	No action is required.

SLBG messages

This section contains SLBG messages.

SLBG_DRIVER_MODIFY_GROUP

Message text	[STRING] changed to unselected state because the device failed to set the driver after the interface-up event for the port.
Variable fields	$1: Port name.
Severity level	5
Example	SLBG/5/SLBG_DRIVER_MODIFY_GROUP: GigabitEthernet1/0/1 changed to unselected state because the device failed to set the driver after the interface-up event for the port.
Explanation	The state of a member port changed to the unselected state because the device failed to set the driver after the interface-up event of the port.
Recommended action	No action is required.

SLBG_REACH_MAXPORT_LIMIT

Message text	[STRING] was removed from group [UINT32] because group reached max port limit after the interface-active event for the port.
Variable fields	$1: Port name. $2: Service loopback group ID.
Severity level	5
Example	SLBG/5/SLBG_REACH_MAXPORT_LIMIT: GigabitEthernet1/0/1 was removed from group 1 because group reached max port limit after the interface-active event for the port.
Explanation	A port was removed from a service loopback group after the interface-active event of the port because the maximum number of member ports in the group already reached.
Recommended action	Check the number of member ports in the service loopback group.

SLSP messages

This section contains static LSP messages.

SLSP_LABEL_DUPLICATE

Message text	Incoming label [INT32] for static LSP [STRING] is duplicate.
Variable fields	$1: Incoming label value. $2: Static LSP name.
Severity level	4
Example	SLSP/4/SLSP_LABEL_DUPLICATE: Incoming label 1024 for static LSP aaa is duplicate.
Explanation	The incoming label of a static LSP was occupied by another configuration, for example, by a static PW or by a static CRLSP. This message is generated when one of the following events occurs: · When MPLS is enabled, configure a static LSP with an incoming label which is occupied by another configuration. · Enable MPLS when a static LSP whose incoming label is occupied by another configuration already exists.
Recommended action	Remove this static LSP, and reconfigure it with another incoming label.

SMLK messages

This section contains Smart Link messages.

SMLK_LINK_SWITCH

Message text	Status of port [STRING] in smart link group [UINT16] changes to active.
Variable fields	$1: Port name. $2: Smart link group ID.
Severity level	4
Example	SMLK/4/SMLK_LINK_SWITCH: Status of port GigabitEthernet0/1/4 in smart link group 1 changes to active.
Explanation	The port takes over to forward traffic after the primary port fails.
Recommended action	Remove the network faults.

SNMP messages

This section contains SNMP messages.

SNMP_ACL_RESTRICTION

Message text	SNMP [STRING] from [STRING] is rejected due to ACL restriction.
Variable fields	$1: SNMP community/usm-user/group name. $2: IP address of the NMS.
Severity level	3
Example	SNMP/3/SNMP_ACL_RESTRICTION: SNMP community public from 192.168.1.100 is rejected due to ACL restrictions.
Explanation	SNMP packets are denied because of ACL restrictions.
Recommended action	Check the ACL configuration on the SNMP agent, and identify whether the agent was attacked.

SNMP_AUTHENTICATION_FAILURE

Message text	Failed to authenticate SNMP message.
Variable fields	N/A
Severity level	4
Example	SNMP/4/SNMP_AUTHENTICATION_FAILURE: Failed to authenticate SNMP message.
Explanation	An NMS failed to be authenticated by the agent.
Recommended action	No action is required.

SNMP_GET

Message text	-seqNO=[UINT32]-srcIP=[STRING]-op=GET-node=[STRING]-value=[STRING]; The agent received a message.
Variable fields	$1: Sequence number of an SNMP operation log. $2: IP address of the NMS. $3: MIB object name and OID. $4: Value field of the request 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	SNMP received a Get request from an NMS. The system logs SNMP operations only when SNMP logging is enabled.
Recommended action	No action is required.

SNMP_NOTIFY

Message text	Notification [STRING][STRING].
Variable fields	$1: Notification name and OID. $2: Variable-binding field of notifications. ¡ If no MIB object exists, only notification name and OID are displayed. ¡ If MIB objects are included, " with " are displayed before the MIB object and OID. MIB objects are separated by semicolons (;).
Severity level	6
Example	SNMP/6/SNMP_NOTIFY: Notification hh3cLogIn(1.3.6.1.4.1.25506.2.2.1.1.3.0.1) with hh3cTerminalUserName(1.3.6.1.4.1.25506.2.2.1.1.2.1.0)=;hh3cTerminalSource(1.3.6.1.4.1.25506.2.2.1.1.2.2.0)=Console.
Explanation	The SNMP agent sent a notification. This message displays the notification content.
Recommended action	No action is required.

SNMP_SET

Message text	-seqNO=[UINT32]-srcIP=[STRING]-op=SET-errorIndex=[UINT32]-errorStatus=[STRING]-node=[STRING]-value=[STRING]; The agent received a message.
Variable fields	$1: Sequence number of an SNMP operation log. $2: IP address of the NMS. $3: Error index of the Set operation. $4: Error status of the Set operation. $5: MIB object name and OID. $6: Value of the MIB object changed by the Set operation.
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	SNMP received a Set request from an NMS. The system logs SNMP operations only when SNMP logging is enabled.
Recommended action	No action is required.

SNMP_USM_NOTINTIMEWINDOW

Message text	-User=[STRING]-IPAddr=[STRING]; SNMPv3 message is not in the time window.
Variable fields	$1: Username. $2: IP address of the NMS.
Severity level	4
Example	SNMP/4/SNMP_USM_NOTINTIMEWINDOW: -User=admin-IPAddr=169.254.0.7; SNMPv3 message is not in the time window.
Explanation	The SNMPv3 message is not in the time window.
Recommended action	No action is required.

SRP

This section contains SR-TE policy messages.

SRP_SEGLIST_STATE_DOWN

Message text	SR-TE policy seglist forwarding state down event: Color [UINT32], EndPoint [STRING], Origin [STRING], Instance [UINT32], Originator [STRING], Discriminator [UINT32], SegListID [UINT32], Reason [STRING].
Variable fields	$1: Color value of the SR-TE policy. $2: End-point address of the SR-TE policy. $3: Candidate path origin. Options include: · CLI—Manually configured. · BGP—Obtained from the BGP SR Policy route. · PCEP—Obtained through PCEP. $4: BGP instance number. This field is available only when the candidate path origin is BGP. $5: Head node of the candidate path, represented in the form of ASN Nodeaddress, where ASN is the AS number and Nodeaddress is the router ID of the BGP peer. This field is available only when the candidate path origin is BGP. $6: Discriminator of the SID list. $7: Index of the SID list. $8: Reason why the forwarding state of the SID list became down. Possible reasons include: · Segment list was unavailable. · SBFD session was down. · Segment list was up pending. · No SRLSP.
Severity level	5
Example	SRP/5/SRP_SEGLIST_STATE_DOWN: SR-TE policy seglist forwarding state down event: Color 10, EndPoint 1.1.1.1, Origin BGP, Instance 0, Originator 10 2.2.2.2, Discriminator 100, SegListID 1, Reason Segment list was unavailable.
Explanation	The forwarding state of a SID list became down.
Recommended action	Examine the link status of the forwarding path identified by the SID list. Verify that the SBFD settings are correct.

SRP_SEGLIST_STATE_DOWN_CLEAR

Message text	SR-TE policy seglist forwarding down is resolved. (Color [UINT32], EndPoint [STRING], Origin [STRING], Instance [UINT32], Originator [STRING], Discriminator [UINT32], SegListID [UINT32])
Variable fields	$1: Color value of the SR-TE policy. $2: End-point address of the SR-TE policy. $3: Candidate path origin. Options include: · CLI—Manually configured. · BGP—Obtained from the BGP SR Policy route. · PCEP—Obtained through PCEP. $4: BGP instance number. This field is available only when the candidate path origin is BGP. $5: Head node of the candidate path, represented in the form of ASN Nodeaddress, where ASN is the AS number and Nodeaddress is the router ID of the BGP peer. This field is available only when the candidate path origin is BGP. $6: Discriminator of the SID list. $7: Index of the SID list.
Severity level	5
Example	SRP/5/SRP_SEGLIST_STATE_DOWN _CLEAR: SR-TE policy seglist forwarding down is resolved. (Color 10, EndPoint 1.1.1.1, Origin BGP, Instance 0, Originator 10 2.2.2.2, Discriminator 100, SegListID 1)
Explanation	The forwarding state of a SID list became up, and the down state alarm has been cleared.
Recommended action	No action is required.

SRP_STATE_DOWN

Message text	SR-TE policy (Color [UINT32], EndPoint [STRING]) forwarding state went down: [STRING].
Variable fields	$1: Color value of the SR-TE policy. $2: End-point address of the SR-TE policy. $3: Reason when the SR-TE policy went down. Possible reasons include: · SBFD session was down. · No candidate path. · No valid candidate path. · No valid segment list. · The color and endpoint were deleted. · No valid BSID.
Severity level	2
Example	SRP/2/SRP_STATE_DOWN: SR-TE policy (Color 10, EndPoint 1.1.1.1) forwarding state went down: No candidate path.
Explanation	An SR-TE policy went down.
Recommended action	Process according to the reason displayed, for example: · Verify that the SR-TE policy and SBFD settings are correct. · Make sure the network is not congested.

SRP_STATE_DOWN_CLEAR

Message text	SR-TE policy (Color [UINT32], EndPoint [STRING]) down alarm was cleared.
Variable fields	$1: Color value of the SR-TE policy. $1: End-point address of the SR-TE policy.
Severity level	2
Example	SRP/2/SRP_STATE_DOWN_CLEAR: SR-TE policy (Color 10, EndPoint 1.1.1.1) down alarm was cleared.
Explanation	The forwarding state of an SR-TE policy became up, and the down state alarm has been cleared.
Recommended action	No action is required.

SSHS messages

This section contains SSH server messages.

SSHS_ACL_DENY

Message text	The SSH Connection [IPADDR]([STRING]) request was denied according to ACL rules.
Variable fields	$1: IP address of the SSH client. $2: VPN instance to which the IP address of the SSH client belongs.
Severity level	5
Example	SSHS/5/SSH_ACL_DENY: The SSH Connection 1.2.3.4(vpn1) request was denied according to ACL rules.
Explanation	The SSH server detected a login attempt from the invalid SSH client and denied the connection request of the client by using the ACL rules.
Recommended action	No action is required.

SSHS_ALGORITHM_MISMATCH

Message text	SSH client [STRING] failed to log in because of [STRING] algorithm mismatch.
Variable fields	$1: IP address of the SSH client. $2: Type of the algorithm, including encryption, key exchange, MAC, and public key.
Severity level	6
Example	SSHS/6/SSHS_ALGORITHM_MISMATCH: SSH client 192.168.30.117 failed to log in because of encryption algorithm mismatch.
Explanation	The SSH client and the SSH server used different algorithms.
Recommended action	Verify that the SSH client and the SSH server use the same algorithm.

SSHS_AUTH_EXCEED_RETRY_TIMES

Message text	SSH user [STRING] (IP: [STRING]) failed to log in, because the number of authentication attempts exceeded the upper limit.
Variable fields	$1: User name. $2: IP address of the SSH client.
Severity level	6
Example	SSHS/6/SSHS_AUTH_EXCEED_RETRY_TIMES: SSH user David (IP: 192.168.30.117) failed to log in, because the number of authentication attempts exceeded the upper limit.
Explanation	The number of authentication attempts by an SSH user reached the upper limit.
Recommended action	Prompt the SSH user to use the correct login data to try again.

SSHS_AUTH_FAIL

Message text	SSH user [STRING] (IP: [STRING]) didn't pass public key authentication for [STRING].
Variable fields	$1: Username. $2: IP address of the SSH client. $3: Failure reasons: · Wrong public key algorithm. · Wrong public key. · Wrong digital signature.
Severity level	6
Example	SSHS/6/SSHS_AUTH_FAIL: SSH user David (IP: 192.168.30.117) didn't pass public key authentication for wrong public key algorithm.
Explanation	An SSH user failed the publickey authentication.
Recommended action	Tell the SSH user to try to log in again.

SSHS_AUTH_SUCCESS

Message text	SSH user [STRING] from [IPADDR] port [INTEGER] passed [STRING] authentication.
Variable fields	$1: Username. $2: IP address of the SSH client. $3: Source TCP port. $4: Authentication method. Supported values are keyboard-interactive, password, and publickey.
Severity level	6
Example	SSHS/6/SSHS_AUTH_SUCCESS: SSH user ABC from 1.1.1.1 port 55361 passed keyboard-interactive authentication.
Explanation	An SSH user passed authentication.
Recommended action	No action is required.

SSHS_AUTH_TIMEOUT

Message text	Authentication timed out for [IPADDR].
Variable fields	$1: IP address of the SSH client.
Severity level	6
Example	SSHS/6/SSHS_AUTH_TIMEOUT: Authentication timed out for 1.1.1.1.
Explanation	The authentication timeout timer expired, and the SSH user failed the authentication.
Recommended action	Make sure the SSH user enters correct authentication information before the authentication timeout timer expires.

SSHS_CONNECT

Message text	SSH user [STRING] (IP: [STRING]) connected to the server successfully.
Variable fields	$1: Username. $2: IP address of the SSH client.
Severity level	6
Example	SSHS/6/SSHS_CONNECT: SSH user David (IP: 192.168.30.117) connected to the server successfully.
Explanation	An SSH user logged in to the server successfully.
Recommended action	No action is required.

SSHS_DECRYPT_FAIL

Message text	The packet from [STRING] failed to be decrypted with [STRING].
Variable fields	$1: IP address of the SSH client. $2: Encryption algorithm, such as AES256-CBC.
Severity level	5
Example	SSHS/5/SSHS_DECRYPT_FAIL: The packet from 192.168.30.117 failed to be decrypted with aes256-cbc.
Explanation	A packet from an SSH client failed to be decrypted.
Recommended action	No action is required.

SSHS_DISCONNECT

Message text	SSH user [STRING] (IP: [STRING]) disconnected from the server.
Variable fields	$1: Username. $2: IP address of the SSH client.
Severity level	6
Example	SSHS/6/SSHS_DISCONNECT: SSH user David (IP: 192.168.30.117) disconnected from the server.
Explanation	An SSH user logged out.
Recommended action	No action is required.

SSHS_ENCRYPT_FAIL

Message text	The packet to [STRING] failed to be encrypted with [STRING].
Variable fields	$1: IP address of the SSH client. $2: Encryption algorithm, such as aes256-cbc.
Severity level	5
Example	SSHS/5/SSHS_ENCRYPT_FAIL: The packet to 192.168.30.117 failed to be encrypted with aes256-cbc.
Explanation	A packet to an SSH client failed to be encrypted.
Recommended action	No action is required.

SSHS_LOG

Message text	Authentication failed for user [STRING] from [STRING] port [INT32] because of invalid username or wrong password. Authorization failed for user [STRING] from [STRING] port [INT32].
Variable fields	$1: Username. $2: IP address of the SSH client. $3: Port number.
Severity level	6
Example	SSHS/6/SSHS_LOG: Authentication failed for user David from 140.1.1.46 port 16266 because of invalid username or wrong password. SSHS/6/SSHS_LOG: Authorization failed for user David from 140.1.2.46 port 15000.
Explanation	An SSH user failed authentication because the username or password was wrong. An SSH user failed authorization.
Recommended action	No action is required.

SSHS_MAC_ERROR

Message text	SSH server received a packet with wrong message authentication code (MAC) from [STRING].
Variable fields	$1: IP address of the SSH client.
Severity level	6
Example	SSHS/6/SSHS_MAC_ERROR: SSH server received a packet with wrong message authentication code (MAC) from 192.168.30.117.
Explanation	The SSH server received a packet with a wrong MAC from a client.
Recommended action	No action is required.

SSHS_REACH_SESSION_LIMIT

Message text	SSH client [STRING] failed to log in. The current number of SSH sessions is [NUMBER]. The maximum number allowed is [NUMBER].
Variable fields	$1: IP address of the SSH client. $2: Current number of SSH sessions. $3: Maximum number of SSH sessions allowed on the device.
Severity level	6
Example	SSHS/6/SSHS_REACH_SESSION_LIMIT: SSH client 192.168.30.117 failed to log in. The current number of SSH sessions is 10. The maximum number allowed is 10.
Explanation	The number of SSH sessions reached the upper limit.
Recommended action	No action is required.

SSHS_REACH_USER_LIMIT

Message text	SSH client [STRING] failed to log in, because the number of users reached the upper limit.
Variable fields	$1: IP address of the SSH client.
Severity level	6
Example	SSHS/6/SSHS_REACH_USER_LIMIT: SSH client 192.168.30.117 failed to log in, because the number of users reached the upper limit.
Explanation	The number of SSH users reached the upper limit.
Recommended action	No action is required.

SSHS_SCP_OPER

Message text	User [STRING] at [IPADDR] requested operation: [STRING].
Variable fields	$1: Username. $2: IP address of the SCP client. $3: Requested file operations: · *get file "name"'—Downloads the file name* from the SCP server. · *put file "name"—Uploads the file name* to the SCP server.
Severity level	6
Example	SSHS/6/SSHS_SCP_OPER: -MDC=1; User user1 at 1.1.1.1 requested operation: put file "aa".
Explanation	The SCP sever received an operation request from an SCP client.
Recommended action	No action is required.

SSHS_SFTP_OPER

Message text	User [STRING] at [IPADDR] requested operation: [STRING].
Variable fields	$1: Username. $2: IP address of the SFTP client. $3: Requested operations on a file or directory: · *open dir "path"—Opens the directory path. · open "file" (attribute code code) in MODE* mode*—Opens the file file* with the attribute code code in mode MODE. · *remove file "path"—Deletes the file path. · mkdir "path" (attribute code code)—Creates a new directory path* with the attribute code code. · *rmdir "path"—Deletes the directory path. · rename old "old-name" to new "new-name"—Changes the name of a file or folder from old-name* to new-name.
Severity level	6
Example	SSHS/6/SSHS_SFTP_OPER: User user1 at 1.1.1.1 requested operation: open dir "flash:/".
Explanation	The SFTP sever received an operation request from an SFTP client.
Recommended action	No action is required.

SSHS_SRV_UNAVAILABLE

Message text	The [STRING] server is disabled or the [STRING] service type is not supported.
Variable fields	$1: Service type, which can be Stelnet, SCP, SFTP, or NETCONF.
Severity level	6
Example	SSHS/6/SSHS_SRV_UNAVAILABLE: The SCP server is disabled or the SCP service type is not supported.
Explanation	The server was disconnecting the connection because of unavailable Stelnet/SCP/SFTP service.
Recommended action	Verify that the Stelnet/SCP/SFTP service is available and the user configuration is correct.

SSHS_VERSION_MISMATCH

Message text	SSH client [STRING] failed to log in because of version mismatch.
Variable fields	$1: IP address of the SSH client.
Severity level	6
Example	SSHS/6/SSHS_VERSION_MISMATCH: SSH client 192.168.30.117 failed to log in because of version mismatch.
Explanation	The SSH client and the SSH server used different SSH versions.
Recommended action	Verify that the SSH client and the SSH server use the same SSH version.

STP messages

This section contains STP messages.

STP_BPDU_PROTECTION

Message text	BPDU-Protection port [STRING] received BPDUs.
Variable fields	$1: Interface name.
Severity level	4
Example	STP/4/STP_BPDU_PROTECTION: BPDU-Protection port GigabitEthernet1/0/1 received BPDUs.
Explanation	A BPDU-guard-enabled port received BPDUs.
Recommended action	Check whether the downstream device is a terminal and check for possible attacks from the downstream device or other devices.

STP_BPDU_RECEIVE_EXPIRY

Message text	Instance [UINT32]'s port [STRING] received no BPDU within the rcvdInfoWhile interval. Information of the port aged out.
Variable fields	$1: Instance ID. $2: Interface name.
Severity level	5
Example	STP/5/STP_BPDU_RECEIVE_EXPIRY: Instance 0's port GigabitEthernet1/0/1 received no BPDU within the rcvdInfoWhile interval. Information of the port aged out.
Explanation	The state of a non-designated port changed because the port did not receive a BPDU within the max age.
Recommended action	Check the STP status of the upstream device and possible attacks from other devices.

STP_CONSISTENCY_CHECK

Message text	DR role assignment finished. Please verify that the local device and the peer device have consistent global and DR-interface-specific STP settings.
Variable fields	N/A
Severity level	5
Example	STP/5/STP_CONSISTENCY_CHECK: DR role assignment finished. Please verify that the local device and the peer device have consistent global and DR-interface-specific STP settings.
Explanation	The DR member devices in a DR system must have the same global and DR-interface-specific STP settings.
Recommended action	Check the global and DR-interface-specific STP settings on the local and peer DR member devices.

STP_CONSISTENCY_RESTORATION

Message text	Consistency restored on VLAN [UINT32]'s port [STRING].
Variable fields	$1: VLAN ID. $2: Interface name.
Severity level	6
Example	STP/6/STP_CONSISTENCY_RESTORATION: Consistency restored on VLAN 10's port GigabitEthernet1/0/1.
Explanation	Port link type or PVID inconsistency was removed on a port.
Recommended action	No action is required.

STP_DETECTED_TC

Message text	[STRING] [UINT32]'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	STP/6/STP_DETECTED_TC: Instance 0's port GigabitEthernet1/0/1 detected a topology change.
Explanation	The MSTP instance or VLAN to which a port belongs had a topology change, and the local end detected the change.
Recommended action	Identify the topology change cause and handle the issue. For example, if the change is caused by a link down event, recover the link.

STP_DISABLE

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

STP_DISCARDING

Message text	Instance [UINT32]'s port [STRING] has been set to discarding state.
Variable fields	$1: Instance ID. $2: Interface name.
Severity level	6
Example	STP/6/STP_DISCARDING: Instance 0's port GigabitEthernet1/0/1 has been set to discarding state.
Explanation	MSTP calculated the state of ports within an instance, and a port was set to the discarding state.
Recommended action	No action is required.

STP_DISPUTE

Message text	[STRING] [UINT32]'s port [STRING] received an inferior BPDU from a designated port which is in forwarding or learning state.
Variable fields	$1: Instance or VLAN. $2: Instance ID or VLAN ID. $3: Interface name.
Severity level	4
Example	STP/4/STP_DISPUTE: Instance 0's port GigabitEthernet1/0/2 received an inferior BPDU from a designated port which is in forwarding or learning state.
Explanation	A port in the MSTI or VLAN received a low-priority BPDU from a designated port in forwarding or learning state.
Recommended action	Verify that the peer port can receive packets from the local port: 1. Use the display stp abnormal-port command to display information about ports that are blocked by dispute protection. 2. Verify that the VLAN configurations on the local and peer ports are consistent. 3. Shut down the link between the two ports and then bring up the link, or connect the local port to another port.

STP_DISPUTE_RESTORATION

Message text	[STRING] [UINT32]'s port [STRING] exited the dispute state.
Variable fields	$1: Instance or VLAN. $2: Instance ID or VLAN ID. $3: Interface name.
Severity level	6
Example	STP/6/STP_DISPUTE_RESTORATION: Instance 0's port GigabitEthernet1/0/2 exited the dispute state.
Explanation	A port in an MSTI or VLAN exited the dispute state.
Recommended action	No action is required.

STP_EDGEPORT_INACTIVE

Message text	Port [STRING] became a non-edge port after receiving a BPDU.
Variable fields	$1: Interface name.
Severity level	4
Example	STP/4/STP_EDGEPORT_INACTIVE: Port GigabitEthernet1/0/1 became a non-edge port after receiving a BPDU.
Explanation	An edge port received BPDUs and became a non-ednge port.
Recommended action	Verify that the network has been attacked by malicious users with forged BPDUs.

STP_ENABLE

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

STP_FORWARDING

Message text	Instance [UINT32]'s port [STRING] has been set to forwarding state.
Variable fields	$1: Instance ID. $2: Interface name.
Severity level	6
Example	STP/6/STP_FORWARDING: Instance 0's port GigabitEthernet1/0/1 has been set to forwarding state.
Explanation	MSTP calculated the state of ports within an instance, and a port was set to the forwarding state.
Recommended action	No action is required.

STP_LOOP_PROTECTION

Message text	Instance [UINT32]'s LOOP-Protection port [STRING] failed to receive configuration BPDUs.
Variable fields	$1: Instance ID. $2: Interface name.
Severity level	4
Example	STP/4/STP_LOOP_PROTECTION: Instance 0's LOOP-Protection port GigabitEthernet1/0/1 failed to receive configuration BPDUs.
Explanation	A loop-guard-enabled port failed to receive configuration BPDUs.
Recommended action	Check the STP status of the upstream device and possible attacks from other devices.

STP_LOOPBACK_PROTECTION

Message text	[STRING] [UINT32]'s port [STRING] received its own BPDU.
Variable fields	$1: Instance or VLAN. $2: Instance ID or VLAN ID. $3: Interface name.
Severity level	4
Example	STP/4/STP_LOOPBACK_PROTECTION: Instance 0's port GigabitEthernet1/0/2 received its own BPDU.
Explanation	A port in the MSTI or VLAN received a BPDU sent by itself.
Recommended action	Check for forged BPDUs from attackers or loops in the network.

STP_NOT_ROOT

Message text	The current switch is no longer the root of instance [UINT32].
Variable fields	$1: Instance ID.
Severity level	5
Example	STP/5/STP_NOT_ROOT: The current switch is no longer the root of instance 0.
Explanation	The current switch is no longer the root bridge of an instance. It received a superior BPDU after it was configured as the root bridge.
Recommended action	Check the bridge priority configuration and possible attacks from other devices.

STP_NOTIFIED_TC

Message text	[STRING] [UINT32]'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	STP/6/STP_NOTIFIED_TC: Instance 0's port GigabitEthernet1/0/1 was notified of a topology change.
Explanation	The neighboring device on a port notified the current device that a topology change occurred in the instance or VLAN to which the port belongs.
Recommended action	Identify the topology change cause and handle the issue. For example, if the change is caused by a link down event, recover the link.

STP_PORT_TYPE_INCONSISTENCY

Message text	Access port [STRING] in VLAN [UINT32] received PVST BPDUs from a trunk or hybrid port.
Variable fields	$1: Interface name. $2: VLAN ID.
Severity level	4
Example	STP/4/STP_PORT_TYPE_INCONSISTENCY: Access port GigabitEthernet1/0/1 in VLAN 10 received PVST BPDUs from a trunk or hybrid port.
Explanation	An access port received PVST BPDUs from a trunk or hybrid port.
Recommended action	Check the port link type setting on the ports.

STP_PVID_INCONSISTENCY

Message text	Port [STRING] with PVID [UINT32] received PVST BPDUs from a port with PVID [UINT32].
Variable fields	$1: Interface name. $2: VLAN ID. $3: VLAN ID.
Severity level	4
Example	STP/4/STP_PVID_INCONSISTENCY: Port GigabitEthernet1/0/1 with PVID 10 received PVST BPDUs from a port with PVID 20.
Explanation	A port received PVST BPDUs from a remote port with a different PVID.
Recommended action	Verify that the PVID is consistent on both ports.

STP_PVST_BPDU_PROTECTION

Message text	PVST BPDUs were received on port [STRING], which is enabled with PVST BPDU protection.
Variable fields	$1: Interface name.
Severity level	4
Example	STP/4/STP_PVST_BPDU_PROTECTION: PVST BPDUs were received on port GigabitEthernet1/0/1, which is enabled with PVST BPDU protection.
Explanation	In MSTP mode, a port enabled with PVST BPDU guard received PVST BPDUs.
Recommended action	Identify the device that sends the PVST BPDUs.

STP_ROOT_PROTECTION

Message text	Instance [UINT32]'s ROOT-Protection port [STRING] received superior BPDUs.
Variable fields	$1: Instance ID. $2: Interface name.
Severity level	4
Example	STP/4/STP_ROOT_PROTECTION: Instance 0's ROOT-Protection port GigabitEthernet1/0/1 received superior BPDUs.
Explanation	A root-guard-enabled port received BPDUs that are superior to the BPDUs generated by itself.
Recommended action	Check the bridge priority configuration and possible attacks from other devices.

SYSLOG messages

This section contains syslog (information center) messages.

SYSLOG_LOGBUFFER_FAILURE

Message text	Log cannot be sent to the logbuffer because of communication timeout between syslog and DBM processes.
Variable fields	N/A
Severity level	4
Example	SYSLOG/4/SYSLOG_LOGBUFFER_FAILURE: Log cannot be sent to the logbuffer because of communication timeout between syslog and DBM processes.
Explanation	Failed to output logs to the logbuffer because of the communication timeout between syslog and DBM processes.
Recommended action	Reboot the device or contact H3C Support.

SYSLOG_LOGFILE_FULL

Message text	Log file space is full.
Variable fields	N/A
Severity level	4
Example	SYSLOG/4/SYSLOG_LOGFILE_FULL: Log file space is full.
Explanation	The log file is full.
Recommended action	Back up the log file, remove the original file, and then bring up interfaces as needed.

SYSLOG_NO_SPACE

Message text	Failed to save log file due to lack of space resources.
Variable fields	N/A
Severity level	4
Example	SYSLOG/4/SYSLOG_NO_SPACE: -MDC=1; Failed to save log file due to lack of space resources.
Explanation	Failed to save logs to the log file due to lack of storage space.
Recommended action	Clean up the storage space of the device regularly to ensure sufficient storage space for saving logs to the log file.

SYSLOG_RESTART

Message text	System restarted -- [STRING] [STRING] Software.
Variable fields	$1: Company name. $2: Software name.
Severity level	6
Example	SYSLOG/6/SYSLOG_RESTART: System restarted -- H3C Comware Software
Explanation	A system restart log was generated.
Recommended action	No action is required.

SYSLOG_RTM_EVENT_BUFFER_FULL

Message text	In the last minute, [STRING] syslog logs were not monitored because the buffer was full.
Variable fields	$1: Number of system logs that were not sent to the EAA module in the last minute.
Severity level	5
Example	SYSLOG/5/SYSLOG_RTM_EVENT_BUFFER_FULL: In the last minute, 100 syslog logs were not monitored because the buffer was full.
Explanation	This message records the number of system logs that are not processed by EAA because the log buffer monitored by EAA is full. The log buffer can be filled up if the device generates large numbers of system logs in a short period of time.
Recommended action	Identify log sources and take actions to reduce system logs. Use the rtm event syslog buffer-size command to increase the log buffer size.

TACACS messages

This section contains TACACS messages.

TACACS_AUTH_FAILURE

Message text	User [STRING] from [STRING] failed authentication.
Variable fields	$1: Username. $2: IP address.
Severity level	5
Example	TACACS/5/TACACS_AUTH_FAILURE: User cwf@system from 192.168.0.22 failed authentication.
Explanation	An authentication request was rejected by the TACACS server.
Recommended action	No action is required.

TACACS_AUTH_SUCCESS

Message text	User [STRING] from [STRING] was authenticated successfully.
Variable fields	$1: Username. $2: IP address.
Severity level	6
Example	TACACS/6/TACACS_AUTH_SUCCESS: User cwf@system from 192.168.0.22 was authenticated successfully.
Explanation	An authentication request was accepted by the TACACS server.
Recommended action	No action is required.

TACACS_DELETE_HOST_FAIL

Message text	Failed to delete servers in scheme [STRING].
Variable fields	$1: Scheme name.
Severity level	4
Example	TACACS/4/TACACS_DELETE_HOST_FAIL: Failed to delete servers in scheme abc.
Explanation	Failed to delete servers from a TACACS scheme.
Recommended action	No action is required.

TELNETD messages

This section contains Telnet daemon messages.

TELNETD_REACH_SESSION_LIMIT

Message text	Telnet client [STRING] failed to log in. The current number of Telnet sessions is [NUMBER]. The maximum number allowed is ([NUMBER]).
Variable fields	$1: IP address of the Telnet client. $2: Current number of Telnet sessions. $3: Maximum number of Telnet sessions allowed by the device.
Severity level	6
Example	TELNETD/6/TELNETD_REACH_SESSION_LIMIT: Telnet client 1.1.1.1 failed to log in. The current number of Telnet sessions is 10. The maximum number allowed is (10).
Explanation	The number of Telnet connections reached the limit.
Recommended action	4. Use the display current-configuration \| include session-limit command to view the current limit for Telnet connections. If the command does not display the limit, the device is using the default setting. 5. If you want to set a greater limit, execute the aaa session-limit command. If you think the limit is proper, no action is required.

VLAN messages

This section contains VLAN messages.

VLAN_CREATEVLAN_NO_ENOUGH_RESOUR

Message text	Failed to create VLAN [STRING]. The maximum number of VLANs has been reached.
Variable fields	$1: VLAN ID.
Severity level	4
Example	VLAN/4/ VLAN_CREATEVLAN_NO_ENOUGH_RESOUR: Failed to create VLAN 1025-4094. The maximum number of VLANs has been reached.
Explanation	A VLAN failed to be created because hardware resources were insufficient.
Recommended action	No action is required.

VLAN_FAILED

Message text	Failed to add interface [STRING] to the default VLAN.
Variable fields	$1: Interface name.
Severity level	4
Example	VLAN/4/VLAN_FAILED: Failed to add interface S-Channel4/2/0/19:100 to the default VLAN.
Explanation	An S-channel interface was created when hardware resources were insufficient. The S-channel interface failed to be assigned to the default VLAN.
Recommended action	No action is required.

VLAN_VLANMAPPING_FAILED

Message text	The configuration failed because of resource insufficiency or conflicts on [STRING].
Variable fields	$1: Interface name.
Severity level	4
Example	VLAN/4/VLAN_VLANMAPPING_FAILED: The configuration failed because of resource insufficiency or conflicts on Ethernet0/0.
Explanation	Part of or all VLAN mapping configurations on the interface were lost because of one of the following occurrences: Hardware resources were insufficient for the interface. The interface joined or left a Layer 2 aggregation group.
Recommended action	No action is required.

VLAN_VLANTRANSPARENT_FAILED

Message text	The configuration failed because of resource insufficiency or conflicts on [STRING].
Variable fields	$1: Interface name.
Severity level	4
Example	VLAN/4/VLAN_VLANTRANSPARENT_FAILED: The configuration failed because of resource insufficiency or conflicts on Ethernet0/0.
Explanation	Part of or all VLAN transparent transmission configurations on the interface were lost because of one of the following occurrences: · Hardware resources were insufficient for the interface. · The interface joined or left a Layer 2 aggregation group.
Recommended action	No action is required.

VRRP messages

This section contains VRRP messages.

VRRP_STATUS_CHANGE

Message text	The status of [STRING] virtual router [UINT32] (configured on [STRING]) changed from [STRING] to [STRING]: [STRING].
Variable fields	$1: VRRP version. $2: VRRP group number. $3: Name of the interface where the VRRP group is configured. $4: Original status. $5: Current status. $6: Reason for status change: · Interface event received—An interface event was received. · IP address deleted—The virtual IP address has been deleted. · The status of the tracked object changed—The status of the associated track entry changed. · VRRP packet received—A VRRP advertisement was received. · Current device has changed to IP address owner—The current device has become the IP address owner. · Master-down-timer expired—The master down timer (3 × VRRP advertisement interval + Skew_Time) expired. · Zero priority packet received—A VRRP packet containing priority 0 was received. · Preempt—Preemption occurred. · Master group drove—The state of the master group changed.
Severity level	6
Example	VRRP/6/VRRP_STATUS_CHANGE: The status of IPv4 virtual router 10 (configured on Ethernet0/0) changed (from Backup to Master): Master-down-timer expired.
Explanation	The VRRP group status changed because of the following reasons: · An interface event was received. · The virtual IP address has been deleted. · The status of the associated track entry changed. · A VRRP advertisement was received. · The current device has become the IP address owner. · The master down timer (3 × VRRP advertisement interval + Skew_Time) expired. · A VRRP packet containing priority 0 was received. · Preemption occurred. · The state of the master group changed.
Recommended action	Check the VRRP group status to make sure it is operating correctly.

VRRP_VF_STATUS_CHANGE

Message text	The [STRING] virtual router [UINT32] (configured on [STRING]) virtual forwarder [UINT32] detected status change (from [STRING] to [STRING]): [STRING].
Variable fields	$1: VRRP version. $2: VRRP group number. $3: Name of the interface where the VRRP group is configured. $4: VF ID. $5: Original status of VF. $6: Current status of VF. $7: Reason for the status change.
Severity level	6
Example	VRRP/6/VRRP_VF_STATUS_CHANGE: The IPv4 virtual router 10 (configured on GigabitEthernet5/1) virtual forwarder 2 detected status change (from Active to Initialize): Weight changed.
Explanation	The status of the virtual forwarder has changed because the weight changed, the timeout timer expired, or VRRP went down.
Recommended action	Check the status of the track entry.

VRRP_VMAC_INEFFECTIVE

Message text	The [STRING] virtual router [UINT32] (configured on [STRING]) failed to add virtual MAC: [STRING].
Variable fields	$1: VRRP version. $2: VRRP group number. $3: Name of the interface where the VRRP group is configured. $4: Reason for the error.
Severity level	3
Example	VRRP/3/VRRP_VMAC_INEFFECTIVE: The IPv4 virtual router 10 (configured on Ethernet0/0) failed to add virtual MAC: Insufficient hardware resources.
Explanation	The virtual router failed to add a virtual MAC address.
Recommended action	Find out the root cause for the operation failure and fix the problem.

VXLAN messages

This section contains VXLAN messages.

VXLAN_LICENSE_UNAVAILABLE

Message text	The VXLAN feature is disabled, because no licenses are valid.
Variable fields	N/A
Severity level	3
Example	VXLAN/3/VXLAN_LICENSE_UNAVAILABLE: The VXLAN feature is disabled, because no licenses are valid.
Explanation	VXLAN was disabled because no licenses were valid.
Recommended action	Install valid licenses for VXLAN.