Login
H3C S9820-8M&S6880[S6550X-HI]&S5580X-EI[HI]&S5580S-EI Switch Series System Log Messages Reference-R1213P50-6W100-book.pdf(3.31 MB)
- Released At: 08-11-2024
- Page Views:
- Downloads:
- Table of Contents
- Related Documents
-
|
H3C S9820-8M&S6880[S6550X-HI]&S5580X-EI[HI]&S5580S-EI Switch Series |
|
System Log Messages Reference - R1213P50 |
|
|
|
|
Document version: 6W100-20230901
Copyright © 2023 New H3C Technologies Co., Ltd. All rights reserved.
No part of this manual may be reproduced or transmitted in any form or by any means without prior written consent of New H3C Technologies Co., Ltd.
Except for the trademarks of New H3C Technologies Co., Ltd., any trademarks that may be mentioned in this document are the property of their respective owners.
The information in this document is subject to change without notice.
Contents
Managing and obtaining system log messages
Obtaining log messages from the console terminal
Obtaining log messages from a monitor terminal
Obtaining log messages from the log buffer
Obtaining log messages from the log file
Obtaining log messages from a log host
ACL_ACCELERATE_NONCONTIGUOUSMASK
ACL_ACCELERATE_NOT_SUPPORTHOPBYHOP
ACL_ACCELERATE_NOT_SUPPORTMULTITCPFLAG
ARP_ACTIVE_ACK_NOREQUESTED_REPLY
ARP_USER_DUPLICATE_IPADDR_DETECT
AVC_THRESHOLDWARNING_FASTLOGGING_FMT
AVC_THRESHOLDWARNING_FASTLOGGING_IPV6FMT
CLKM_SOURCE_FREQDEVIATION_ALARM
CLKM_SOURCE_FREQDEVIATION_NORMAL
DOT1X_LOGIN_SUCC (in open mode)
DOT1X_LOGOFF_ABNORMAL (in open mode)
DOT1X_NOTENOUGH_EADFREEMSEG_RES
DOT1X_NOTENOUGH_EADFREERULE_RES
DOT1X_NOTENOUGH_EADMACREDIR_RES
DOT1X_NOTENOUGH_EADPORTREDIR_RES
DOT1X_NOTENOUGH_ENABLEDOT1X_RES
ETHOAM_CONNECTION_FAIL_TIMEOUT
ETHOAM_CONNECTION_FAIL_UNSATISF
ETHOAM_ENTER_LOOPBACK_CTRLLING
ETHOAM_LOCAL_ERROR_FRAME_PERIOD
ETHOAM_LOCAL_ERROR_FRAME_SECOND
ETHOAM_LOOPBACK_EXIT_ERROR_STATU
ETHOAM_REMOTE_ERROR_FRAME_PERIOD
ETHOAM_REMOTE_ERROR_FRAME_SECOND
IDENTITY_IMC_IMPORT_FAILED_NO_MEMORY
IDENTITY_LDAP_IMPORT_FAILED_NO_MEMORY
IDENTITY_LDAP_IMPORT_GROUP_FAILED
IDENTITY_LDAP_IMPORT_USER_FAILED
FLEXE_BANDWIDTH_MISMATCH_RECOVER
FLEXE_BANDWIDTH_REDUCE_RECOVER
FLEXE_CLIENTID_MISMATCH_RECOVER
FLEXE_GROUPMEMBER_FAULT_RECOVER
FLEXE_PHYGROUP_MISMATCH_RECOVER
IF_BUFFER_CONGESTION_OCCURRENCE
IP6ADDR_CREATEADDRESS_CONFLICT
IP6FW_SETTING_FAILED_HOPLIMITEXCEED
IP6FW_SETTING_FAILED_HOPLIMITUNVARIED
IPFW_SETTING_FAILED_TTLUNVARIED
IPSEC_ANTI-REPLAY_WINDOWS_ERROR
INDICATOR_PREDICT_UPPERLIMIT_ALARM
INDICATOR_PREDICT_LOWERLIMIT_ALARM
INDICATOR_PREDICT_RECOVER_ALARM
L2PT_CREATE_TUNNELGROUP_FAILED
LAGG_INACTIVE_RESOURCE_INSUFICIE
LLDP_NEIGHBOR_PROTECTION_BLOCK
LLDP_NEIGHBOR_PROTECTION_UNBLOCK
MAC_VLAN_LEARNLIMIT_NORESOURCE
MAC_VLAN_LEARNLIMIT_NOTSUPPORT
MACA_LOGIN_SUCC (in open mode)
M-LAG_IFEVT_MLAGIF_PRIORITY_CHG
MLAG_KEEPALIVEINTERVAL_MISMATCH
M-LAG_SYSEVENT_PRIORITY_CHANGE
NAT_SERVICE_CARD_RECOVER_FAILURE
ND_SET_VLAN_REDIRECT_NORESOURCE
NQA_TWAMP_LIGHT_PACKET_INVALID
OFP_FLOW_ADD_TABLE_MISS_FAILED
OFP_FLOW_DEL_TABLE_MISS_FAILED
OFP_FLOW_MOD_TABLE_MISS_FAILED
PFILTER_VLAN_IPV4_DACT_UNK_ERR
PFILTER_VLAN_IPV6_DACT_UNK_ERR
PORTSEC_PORTMODE_NOT_EFFECTIVE
PTP_TIME_OFFSE_EXCEED_THRESHOLD
PTS_CREATE_SELFVERIFY_COUNTER_FAILED
PTS_CREATE_SELFVERIFY_TIMER_FAILED
QOS_QMPROFILE_MODIFYQUEUE_FAIL
RBM_CLUSTER_CTRL_CHANNEL_CLOSED
RBM_CLUSTER_CTRL_CHANNEL_CREATED
RBM_CLUSTER_CTRL_CHANNEL_FAILED
SRPV6_SEGLIST_STATE_DOWN_CLEAR
SSLVPN_HTTP_BIND_ADDRESS_INUSED
SSLVPN_HTTP_BIND_PORT_ALLOCETED
SSLVPN_IPAC_ALLOC_ADDR_SUCCESS
SSLVPN_IPAC_RELEASE_ADD_SUCCESS
STAMGR_AUTHORUSERPROFILE_FAILURE
STAMGR_STA_ADDMOB_LKUP_ENDOFIOCTL
STRUNK_DROPPACKET_INCONSISTENCY
Introduction
This document includes the following system messages:
· Messages specific to Release 1213P50 of the switch.
· Messages for the Comware 9 software platform version based on which Release 1213P50 was produced. Some platform system messages might not be available on the switch.
This document is intended only for managing H3C S9820-8M&S6880[S6550X-HI]&S5580X-EI[HI]&S5580S-EI switches. 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. The CONTENT field in most log messages is represented by one or multiple sentences, for example, VTY logged in from 192.168.1.21. Certain log messages are used only to record parameter values. The CONTENT field for such messages is represented in the format of key info 1;key info 2,..key info n. The key information can be one of the following formats: · Keyword(keyword ID)=Value · Keyword(keyword ID)=(Text ID)Text description The IDs are factory default parameters that enable the log host software (for example, security management system) to parse keyword content: · The keyword ID represents the keyword before the ID. · The text ID represents the text description after the ID. For example, in the key information streamAlarmType(1032)=(42)Too fast speed of TCP session to destination IP, value 1032 represents keyword streamAlarmType, and value 42 represents text description Too fast speed of TCP session to destination IP. |
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, monitor terminal, log buffer, 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 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.
|
|
NOTE: Settings for the terminal monitor and terminal logging level commands take effect only on the current login session. The default settings for the commands restore at a relogin. |
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 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 flash:/logfile.
To view the contents of the log file on the device, use the more command.
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.
|
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 |
|
CLKM |
Clock Monitoring |
|
DEV |
Device Management |
|
DHCPR |
IPv4 DHCP Relay |
|
DHCPS |
DHCP Server |
|
DHCPS6 |
DHCPv6 Server |
|
DHCPSP4 |
DHCP Snooping |
|
DHCPSP6 |
DHCPv6 Snooping |
|
DIAG |
Diagnosis |
|
DIM |
DPI Engine |
|
DLDP |
Device Link Detection Protocol |
|
DOT1X |
802.1X |
|
DRVPLAT |
Drive Plat |
|
EDEV |
|
|
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 |
|
HA |
High Availability |
|
HOTPLUG |
Hotplug |
|
HQOS |
Hierarchical QoS |
|
HTTPD |
Hypertext Transfer Protocol Daemon |
|
iFIT |
in-situ Flow Information Telemetry |
|
IFNET |
Interface Net Management |
|
IKE |
Internet Key Exchange |
|
IMA |
Integrity Measurements Architecture |
|
IP6ADDR |
IPv6 Addressing |
|
IP6FW |
IPv6 Forwarding |
|
IPADDR |
IP Addressing |
|
IPFW |
IP Forwarding |
|
IPOE |
IP Over Ethernet |
|
IPSEC |
IP Security |
|
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 |
|
M-LAG |
Multichassis link aggregation |
|
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 |
|
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 |
|
PEX |
Port Extender |
|
PIM |
Protocol Independent Multicast |
|
PING |
Packet Internet Groper |
|
PKG |
Package |
|
PKI |
Public Key Infrastructure |
|
PKT2CPU |
Packet to CPU |
|
PoE |
Power over Ethernet |
|
PORTAL |
Portal |
|
PORTSEC |
Port Security |
|
PPP |
Point to Point Protocol |
|
PPPOES |
PPP over Ethernet Server |
|
PTP |
Precision Time Protocol |
|
PTS |
Platform Trust Services |
|
PWDCTL |
Password Control |
|
QOS |
Quality of Service |
|
RADIUS |
Remote Authentication Dial In User Service |
|
RBM |
Remote Backup Management |
|
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 |
|
SHELL |
Shell |
|
SLBG |
Service Loopback Groups |
|
SLSP |
Static LSP |
|
SMLK |
Smart Link |
|
SNMP |
Simple Network Management Protocol |
|
SRPV6 |
SRv6 TE Policy |
|
SSHC |
Secure Shell Client |
|
SSHS |
Secure Shell Server |
|
STAMGR |
Station Management |
|
STM |
Stack Topology Management |
|
STP |
Spanning Tree Protocol |
|
STRUNK |
Smart Trunk |
|
SYSEVENT |
System Event |
|
SYSLOG |
System Log |
|
TACACS |
Terminal Access Controller Access Control System |
|
TCSM |
Trusted Computing Services Management |
|
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 2900 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 |
ACL/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. |
ADVPN messages
This section contains ADVPN messages.
ADVPN_SESSION_DELETED
|
Message text |
An ADVPN tunnel was deleted: tunnel interface=[STRING], private addr=[STRING], public addr=[STRING], peer private addr=[STRING], peer public addr=[STRING], type=[STRING], last state=[STRING], last state duration=[STRING], domain name=[STRING], ADVPN group name=[STRING]. |
|
Variable fields |
$1: Tunnel interface name. $2: Private address of the ADVPN tunnel. $3: Public address of the ADVPN tunnel. $4: Peer private address of the ADVPN tunnel. $5: Peer public address of the ADVPN tunnel. $6: ADVPN tunnel type. $7: Last state of the ADVPN tunnel. $8: Duration for the last state of the ADVPN tunnel, in the format of xH yM zS. $9: ADVPN domain name. $10: ADVPN group name. |
|
Severity level |
4 |
|
Example |
ADVPN/4/ADVPN_SESSION_DELETED: An ADVPN tunnel was deleted: tunnel interface=888, private addr=112.168.60.56, public addr=192.168.60.137,peer private addr=112.168.60.18, peer public addr=192.168.60.11,type=Spoke-Hub, last state=Success, last state duration=0H 8M 8S,domain name=abc, ADVPN group name= |
|
Explanation |
An ADVPN tunnel was deleted. |
|
Recommended action |
Check the network connectivity and configuration. |
ADVPN_SESSION_STATE_CHANGED
|
Message text |
ADVPN tunnel state changed from [STRING] to [STRING]: tunnel interface=[STRING], private addr=[STRING], public addr=[STRING], peer private addr=[STRING], peer public addr=[STRING], type=[STRING], last state=[STRING], last state duration=[STRING], domain name=[STRING], ADVPN group name=[STRING]. |
|
Variable fields |
$1: Original state of the ADVPN tunnel. $2: New state of the ADVPN tunnel. $3: Tunnel interface name. $4: Private address of the ADVPN tunnel. $5: Public address of the ADVPN tunnel. $6: Peer private address of the ADVPN tunnel. $7: Peer public address of the ADVPN tunnel. $8: ADVPN tunnel type. $9: Last state of the ADVPN tunnel. $10: Duration for the last state of the ADVPN tunnel, in the format of xH yM zS. $11: ADVPN domain name. $12: ADVPN group name. |
|
Severity level |
4 |
|
Example |
ADVPN/4/ADVPN_SESSION_STATE_CHANGED: ADVPN tunnel state changed from Establishing to Success: tunnel interface=888, private addr=112.168.60.56, public addr=192.168.60.137,peer private addr=112.168.60.18, peer public addr=192.168.60.11,type=Spoke-Hub, last state=Establishing, last state duration=0H 0M 5S,domain name=abc, ADVPN group name= |
|
Explanation |
The state of an ADVPN tunnel was changed. |
|
Recommended action |
Check the network connectivity and configuration. |
AFT messages
This section contains AFT messages.
AFT_LOG_FLOW
|
Message text |
AFT PORTBLOCK was [STRING]: ipv6addr=[IPADDR]-VPNNameV6=[STRING]-ipv4addr=[IPADDR]-VPNNameV4=[STRING]-PortBlockSize=[UINT16]-[UINT16]-beginTime_e=[STRING]-endTime_e=[STRING]. |
|
Variable fields |
$1: Event type: ¡ allocated—Port block assignment. ¡ free—Port block release. $2: IPv6 address. $3: Name of the VPN instance to which the IPv6 address belongs. $4: IPv4 address. $5: Name of the VPN instance to which the IPv4 address belongs.. $6: Start port number of a port block that is assigned. $7: End port number of a port block that is assigned. $8: Time when the port block is assigned. $9: Time when the port block is released. |
|
Severity level |
6 |
|
Example |
AFT/6/AFT_LOG_FLOW: AFT PORTBLOCK was free: ipv6addr=1000::1b-VPNNameV6=--ipv4addr=10.0.0.140-VPNNameV4=--PortBlockSize=1024-1535-beginTime_e=02102020053558-endTime_e=02112020065040. |
|
Explanation |
This message is generated when the port block is released or allocated. |
|
Recommended action |
No action is required. |
AFT_V6TOV4_FLOW
|
Message text |
Protocol(1001)= [STRING];SrcIPv6Addr(1036)= [IPADDR];SrcPort(1004)= [UINT16];NatSrcIPAddr(1005)= [IPADDR];NatSrcPort(1006)= [UINT16];DstIPv6Addr(1037)= [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];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: Source IP address after translation. $5: Source port number after translation. S6: Destination IPv6 address. $7: Destination port number. $8: Destination IP address after translation. $9: Destination port number after translation. $10: Total number of incoming packets. $11: Total number of incoming bytes. $12: Total number of outgoing packets. $13: Total number of outgoing bytes. $14: Source VPN instance name. $15: Destination VPN instance name. $16: Time when the session is established. $17: Time when the session is removed. $18: Event type. $19: Event description: ¡ Session created. ¡ Session ended. ¡ Session aged out. ¡ Session deleted through configuration. ¡ Other. |
|
Severity level |
6 |
|
Example |
AFT/6/AFT_V6TOV4_FLOW:Protocol(1001)=IPv6-ICMP;SrcIPv6Addr(1036)=1000::10;SrcPort(1004)=1;NatSrcIPAddr(1005)=9.9.9.9;NatSrcPort(1006)=1027;DstIPv6Addr(1037)=2000::201:102;DstPort(1008)=32768;NatDstIPAddr(1009)=2.1.1.2;NatDstPort(1010)=2048;InitPktCount(1044)=177411959;InitByteCount(1046)=2122604543;RplyPktCount(1045)=1895856127;RplyByteCount(1047)=30720;RcvVPNInstance(1042)=;SndVPNInstance(1043)=;BeginTime_e(1013)=02102020134514;EndTime_e(1014)=;Event(1048)=(8)Session created. |
|
Explanation |
This message is generated when an IPv6-initiated session is established or deleted. |
|
Recommended action |
No action is required. |
AFT_V4TOV6_FLOW
|
Message text |
Protocol(1001)= [STRING]; SrcIPAddr(1003)= [IPADDR];SrcPort(1004)= [UINT16]; NatSrcIPv6Addr(1038)= [IPADDR];NatSrcPort(1006)= [UINT16]; DstIPAddr(1003)= [IPADDR];DstPort(1008)= [UINT16]; NatDstIPv6Addr(1039)= [IPADDR];NatDstPort(1010)= [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: Source IP address after translation. $5: Source port number after translation. S6: Destination IPv6 address. $7: Destination port number. $8: Destination IP address after translation. $9: Destination port number after translation. $10: Total number of incoming packets. $11: Total number of incoming bytes. $12: Total number of outgoing packets. $13: Total number of outgoing bytes. $14: Source VPN instance name. $15: Destination VPN instance name. $16: Time when the session is established. $17: Time when the session is removed. $18: Event type. $19: Event description: ¡ Session created. ¡ Session ended. ¡ Session aged out. ¡ Session deleted through configuration. ¡ Other. |
|
Severity level |
6 |
|
Example |
AFT/6/AFT_V4TOV6_FLOW:Protocol(1001)=ICMP;SrcIPAddr(1003)=2.1.1.4;SrcPort(1004)=197;NatSrcIPv6Addr(1038)=2000::201:104;NatSrcPort(1006)=197;DstIPAddr(1003)=5.5.5.5;DstPort(1008)=2048;NatDstIPv6Addr(1039)=1000::;NatDstPort(1010)=32768;InitPktCount(1044)=2092588805;InitByteCount(1046)=1166331903;RplyPktCount(1045)=1895856127;RplyByteCount(1047)=30720;RcvVPNInstance(1042)=;SndVPNInstance(1043)=;BeginTime_e(1013)=02052020152731;EndTime_e(1014)=;Event(1048)=(8)Sessioncreated. |
|
Explanation |
This message is generated when an IPv4-initiated session is established or deleted. |
|
Recommended action |
No action is required. |
APMGR messages
This section contains access point management messages.
AP_CREATE_FAILURE
|
Message text |
Failed to create an AP with entity ID [UINT32] and model [STRING]. Reason: Region code is not available. |
|
Variable fields |
$1: AP ID. $2: AP model. |
|
Severity level |
6 |
|
Example |
APMGR/6/AP_CREATE_FAILURE: Failed to create an AP with entity ID 1 and model WA2620i-AGN. Reason: Region code is not available. |
|
Explanation |
The system fails to create an AP because the AP is not specified with a region code. |
|
Recommended action |
Specify a region code in global configuration view. |
AP_REBOOT_REASON
|
Message text |
AP in Run state is rebooting. Reason: The physical status of the radio is down. |
|
Variable fields |
N/A |
|
Severity level |
6 |
|
Example |
APMGR/6/AP_REBOOT_REASON: AP in Run state is rebooting. Reason: The physical status of the radio is down. |
|
Explanation |
The AP is rebooting because a physical radio interface of the AP is in down state. |
|
Recommended action |
Verify that radio settings on the AP are correct after the reboot. |
APMGR_AP_CFG_FAILED
|
Message text |
Failed to reset AP [STRING]. Reason: The AP is writing an image file into the flash. |
|
Variable fields |
$1: AP name. |
|
Severity level |
4 |
|
Example |
APMGR/4/APMGR_CFG_FAILD: Failed to reset AP ap2. Reason: The AP is writing an image file into the flash. |
|
Explanation |
AP reset failed because the AP is writing an image file into the flash. |
|
Recommended action |
Restart the AP after the AP finishes writing an image file into the flash. |
APMGR_AP_ONLINE
|
Message text |
The AP failed to come online. Reason: AP model [$1] is not supported. AP ID=[$2], MAC address=[$3]. |
|
Variable fields |
$1: AP model. $2: AP ID. $3: AP MAC address. |
|
Severity level |
6 |
|
Example |
APMGR/6/APMGR_AP_ONLINE: The AP failed to come online. Reason: AP model wa6320 is not supported. AP ID=0, MAC address=b0f9-63da-db20. |
|
Explanation |
The AP fails to come online because its model is not supported by the AC and the AC cannot receive discovery requests from the AP. |
|
Recommended action |
No action is required. |
APMGR_GET_AP_MODEL_FAILURE
|
Message text |
Failed to get an AP model because no region code is configured globally or for AP group [STRING]. |
|
Variable fields |
$1: AP group name. |
|
Severity level |
6 |
|
Example |
APMGR/6/APMGR_GET_AP_MODEL_FAILURE: Failed to get an AP model because no region code is configured globally or for AP group g2. |
|
Explanation |
Failed to obtain the models of APs in an AP group because no region code is specified. |
|
Recommended action |
Specify a global region code or specify a region code for the AP group. |
APMGR_LOG_ADD_AP_FAIL
|
Message text |
AP [STRING] failed to come online using serial ID [STRING]: MAC address [STRING] is being used by AP [STRING]. |
|
Variable fields |
$1: AP name. $2: Serial ID. $3: MAC address. $4: AP name. |
|
Severity level |
4 |
|
Example |
APMGR/4/APMGR_LOG_ADD_AP_FAIL: AP ap1 failed to come online using serial ID 01247ef96: MAC address 0023-7961-5201 is being used by AP ap2. |
|
Explanation |
The AP failed to come online because a manual AP that has the same MAC address already exists on the AC. |
|
Recommended action |
Delete either the manual AP that has the MAC address or the serial ID. |
APMGR_LOG_MEMALERT
|
Message text |
The memory usage of the AC has reached the threshold. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
APMGR/4/APMGR_LOG_MEMALERT: The memory usage of the AC has reached the threshold. |
|
Explanation |
The AP failed to come online because the memory utilization exceeded the limit. |
|
Recommended action |
Stop creating manual APs and prevent APs from coming online. |
APMGR_LOG_NOLICENSE
|
Message text |
AP failed to come online in [STRING]. Reason: No license for the [STRING]. |
|
Variable fields |
$1: AP state: · discover. · join. $2: AP type: · common AP. · WTU AP. |
|
Severity level |
6 |
|
Example |
APMGR/6/APMGR_LOG_NOLICENSE: AP failed to come online in discover. Reason: No license for the common AP. |
|
Explanation |
The AP failed to come online because the number of APs allowed by the license on the AC has reached the upper limit. |
|
Recommended action |
Purchase an upgrade license for AP number extension. |
APMGR_LOG_OFFLINE
|
Message text |
AP [STRING] went offline. State changed to Idle. |
|
Variable fields |
$1: AP name. |
|
Severity level |
6 |
|
Example |
APMGR/6/APMGR_LOG_OFFLINE: AP ap1 went offline. State changed to Idle. |
|
Explanation |
The AP went offline. The state of the AP changed to Idle. |
|
Recommended action |
If the AP went offline abnormally, check the debugging information to locate the problem and resolve it. |
APMGR_LOG_ONLINE
|
Message text |
AP [STRING] came online. State changed to Run. |
|
Variable fields |
$1: AP name. |
|
Severity level |
6 |
|
Example |
APMGR/6/APMGR_LOG_ONLINE: AP ap1 came online. State changed to Run. |
|
Explanation |
The AP came online. The state of the AP changed to Run. |
|
Recommended action |
No action is required. |
APMGR_LOG_ONLINE_FAILED
|
Message text |
[STRING] ([STRING]) failed to come online in join state. Reason: [STRING] ([STRING]) was offline. |
|
Variable fields |
$1: Name of a WTU or WAP. $2: Serial ID of a WTU or WAP. $3: Name of the connected WT or SPM. $4: Serial ID of the connected WT or SPM. |
|
Severity level |
6 |
|
Example |
· APMGR/6/APMGR_AP_ONLINE_FAILED: WTU (219801A0WA916BQ12535) failed to come online in join state. Reason: WT (219801A11UC173000153) was offline. · APMGR/6/APMGR_AP_ONLINE_FAILED: WAP (219801A0VW916AG00254) failed to come online in join state. Reason: SPM (219801A13DB05B0004350) was offline. |
|
Explanation |
· The WTU cannot come online because its connected WT is offline. · The WAP cannot come online because its connected SPM is offline. |
|
Recommended action |
Make the WT or SPM come online. |
APMGR_REACH_MAX_APNUMBER
|
Message text |
An AP failed to come online: Maximum number of APs already reached. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
APMGR/4/APMGR_REACH_MAX_APNEMBER: An AP failed to come online: Maximum number of APs already reached. |
|
Explanation |
An AP failed to come online because the number of APs on the AC already reached the upper limit. |
|
Recommended action |
No action is required. |
APMGR_ERROR
|
Message text |
Failed to install WLAN feature package. Reason: Insufficient hardware resources. |
|
Variable fields |
N/A |
|
Severity level |
6 |
|
Example |
APMGR/6/ERROR: Failed to install WLAN feature package. Reason: Insufficient hardware resources. |
|
Explanation |
The system failed to install the WLAN feature package because of insufficient hardware resources. |
|
Recommended action |
To resolve the problem: 1. Uninstall the WLAN feature package. 2. Locate the reason that causes hardware resource exhaustion and remove the issue. 3. Reinstall the WLAN feature package. 4. If the problem persists, contact H3C Support. |
CWS_IMG_DOWNLOAD_FAILED
|
Message text |
Failed to download image file [STRING1] for [STRING2] [STRING3]. |
|
Variable fields |
$1: Image file name. $2: AP or local AC. $3: Name of the AP or local AC. |
|
Severity level |
6 |
|
Example |
CWS/6/CWS_IMG_DOWNLOAD_FAILED: Failed to download image file wa4300.ipe for AP ap1. |
|
Explanation |
The AP or the local AC failed to download the image file from the AC. |
|
Recommended action |
No action is required. |
CWS_AP_DOWN
|
Message text |
CAPWAP tunnel to AP [STRING] went down. Reason: [STRING]. |
|
Variable fields |
$1: AP name. $2: Reason: · Neighbor dead timer expired. · AP was reset by admin. · AP was reset by CloudTunnel. · AP was reset on cloud. · WT was offline. · AP was deleted. · Serial number changed. · Processed join request in Run state. · Failed to retransmit message. · Received WTP tunnel down event from AP. · Backup AC closed the backup tunnel. · Backup AP upgrade failed. · AC is inactive. · Tunnel switched. · N/A. |
|
Severity level |
6 |
|
Example |
CWS/6/CWS_AP_DOWN: CAPWAP tunnel to AP ap1 went down. Reason: AP was reset by admin. |
|
Explanation |
The AP went offline for a specific reason. |
|
Recommended action |
To resolve the problem: 1. Examine the network connection between the AP and the AC. 2. Verify that the AP is correctly configured. 3. Verify that the AC is correctly configured. 4. If the problem persists, contact H3C Support. |
CWS_AP_UP
|
Message text |
[STRING] CAPWAP tunnel to AP [STRING] went up. |
|
Variable fields |
$1: Tunnel type: · Master. · Backup. $2: AP name or serial ID. |
|
Severity level |
6 |
|
Example |
CWS/6/CWS_AP_UP: Backup CAPWAP tunnel to AP ap1 went up. |
|
Explanation |
The AP came online and entered Run state. |
|
Recommended action |
No action is required. |
CWS_IMG_DOWNLOAD_COMPLETE
|
Message text |
System software image file [STRING] downloading through the CAPWAP tunnel for AP [STRING] completed. |
|
Variable fields |
$1: Image file name. $2: AP name. |
|
Severity level |
6 |
|
Example |
CWS/6/CWS_IMG_DOWNLOAD_COMPLETE: System software image file 5800.ipe downloading through the CAPWAP tunnel for AP ap2 completed. |
|
Explanation |
The AP downloaded the image file from the AC successfully. |
|
Recommended action |
No action is required. |
CWS_IMG_DOWNLOAD_FAILED
|
Message text |
Failed to download image file [STRING] for the AP. AC memory is not enough. |
|
Variable fields |
$1: Name of an image file. |
|
Severity level |
6 |
|
Example |
CWS/6/CWS_IMG_DOWNLOAD_FAILED: Failed to download image file wa4300anchor.ipe for the AP. AC memory is not enough. |
|
Explanation |
The AP failed to download an image file from the AC because of insufficient AC memory. |
|
Recommended action |
No action is required. |
CWS_IMG_DOWNLOAD_START
|
Message text |
AP [STRING] started to download the system software image file [STRING]. |
|
Variable fields |
$1: AP name. $2: Image file name. |
|
Severity level |
6 |
|
Example |
CWS/6/CWS_IMG_DOWNLOAD_START: AP ap1 started to download the system software image file 5800.ipe. |
|
Explanation |
The AP started to download the image file from the AC. |
|
Recommended action |
No action is required. |
CWS_IMG_OPENFILE_FAILED
|
Message text |
Failed to open the image file [STRING]. |
|
Variable fields |
$1: Path of the image file to be downloaded to the AP. |
|
Severity level |
3 |
|
Example |
CWS/3/CWS_IMG_OPENFILE_FAILED: Failed to open the image file slot1#cfa0:/wa5600.ipe. |
|
Explanation |
The AP failed to open the image file downloaded from the AC. |
|
Recommended action |
No action is required. |
CWS_RUN_DOWNLOAD_COMPLETE
|
Message text |
File [STRING] successfully downloaded through the CAPWAP tunnel for AP [STRING]. |
|
Variable fields |
$1: File name. $2: AP name. |
|
Severity level |
6 |
|
Example |
CWS/6/CWS_RUN_DOWNLOAD_COMPLETE: File ac.cfg successfully downloaded through the CAPWAP tunnel for AP ap2. |
|
Explanation |
The AP downloaded the file from the AC successfully. |
|
Recommended action |
No action is required. |
CWS_RUN_DOWNLOAD_START
|
Message text |
AP [STRING] started to download the file [STRING]. |
|
Variable fields |
$1: AP name. $2: File name. |
|
Severity level |
6 |
|
Example |
CWS/6/CWS_RUN_DOWNLOAD_START: AP ap1 started to download the file ac.cfg. |
|
Explanation |
The AP started to download the file from the AC. |
|
Recommended action |
No action is required. |
RADIO
|
Message text |
APMGR/6/RADIO: Current channel usage [UINT32] of radio [CHAR] on AP [STRING] exceeded the threshold. |
|
Variable fields |
$1: Current channel usage. $2: Radio ID. $3: AP name. |
|
Severity level |
6 |
|
Example |
APMGR/6/RADIO: Current channel usage 63% of radio 2 on AP ap1 exceeded the threshold. |
|
Explanation |
The current channel usage on a radio has exceeded the channel usage threshold. |
|
Recommended action |
Execute the channel command to switch the working channel to a channel with low usage. |
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_ENTRY_ENOUGHRESOURCE
|
Message text |
Issued the software entry to the driver for IPv4 address [STRING] on VPN instance [STRING]. Issued the software entry to the driver for IPv4 address [STRING] on the public network. |
|
Variable fields |
$1: IP address. $2: VPN instance name. If the ARP entry belongs to the public network, this field is not displayed. |
|
Severity level |
6 |
|
Example |
ARP/6/ARP_ENTRY_ENOUGHRESOURCE: Issued the software entry to the driver for IPv4 address 10.1.1.1 on VPN instance vpn_1. ARP/6/ARP_ENTRY_ENOUGHRESOURCE: Issued the software entry to the driver for IPv4 address 10.1.1.2 on the public network. |
|
Explanation |
When using the arp consistency-check enable command to enable the ARP entry consistency check feature, a log is generated indicating that the driver hardware entry has been successfully refreshed based on the ARP software entry. |
|
Recommended action |
No action is required. |
ARP_ENTRY_ INCONSISTENT
|
Message text |
Inconsistent software and hardware ARP entries for IPv4 address [STRING] on VPN instance [STRING]. Inconsistent parameters: [STRING]. Inconsistent software and hardware ARP entries for IPv4 address [STRING] on the public network. Inconsistent parameters: [STRING]. |
|
Variable fields |
$1: IP address. $2: VPN instance name. If the ARP entry belongs to the public network, this field is not displayed. $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_INCONSISTENT: Inconsistent software and hardware ARP entries for IPv4 address 10.1.1.1 on VPN instance vpn_1. Inconsistent parameters: MAC address, output port, VSI index, and link ID. ARP/6/ARP_ENTRY_INCONSISTENT: Inconsistent software and hardware ARP entries for IPv4 address 10.1.1.2 on the public network. Inconsistent parameters: MAC address, output port, VSI index, and link ID. |
|
Explanation |
When using the arp consistency-check enable command to enable the ARP entry consistency check feature, the device generates a log message documenting any inconsistent ARP entries found between the software and hardware entries in the ARP table. |
|
Recommended action |
No action is required. ARP automatically refreshes the driver hardware entries. |
ARP_ENTRY_ NORESOURCE
|
Message text |
Not enough hardware resources to issue the software entry to the driver for IPv4 address [STRING] on VPN instance [STRING]. Not enough hardware resources to issue the software entry to the driver for IPv4 address [STRING] on the public network. |
|
Variable fields |
$1: IP address. $2: VPN instance name. If the ARP entry belongs to the public network, this field is not displayed. |
|
Severity level |
6 |
|
Example |
ARP/6/ARP_ENTRY_NORESOURCE: Not enough hardware resources to issue the software entry to the driver for IPv4 address 10.1.1.1 on VPN instance vpn_1. ARP/6/ARP_ENTRY_NORESOURCE: Not enough hardware resources to issue the software entry to the driver for IPv4 address 10.1.1.2 on the public network. |
|
Explanation |
When using the arp consistency-check enable command to enable the ARP entry consistency check feature, a log is generated if the driver has insufficient ARP hardware entry resources to handle the ARP software entry that was sent. |
|
Recommended action |
No action is required. ARP automatically refreshes the driver hardware entries. |
ARP_HOST_IP_CONFLICT
|
Message text |
|
|
Variable fields |
$1: IP address. $2: Interface name. $3: Interface name. |
|
Severity level |
4 |
|
Example |
|
|
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. |
ASPF messages
This section contains ASPF messages.
ASPF_IPV4_DNS
|
Message text |
SrcIPAddr(1003)=[IPADDR];DstIPAddr(1007)=[IPADDR];RcvVPNInstance(1042)=[STRING];RcvDSLiteTunnelPeer(1040)=[STRING];DomainName(1099)=[STRING];Action(1053)=[STRING];Reason(1056)=[STRING]. |
|
Variable fields |
$1: Source IPv4 address. $2: Destination IPv4 address. $3: VPN instance name. $4: Local address of a DS-Lite tunnel. $5: Domain name. $6: Action on the detected illegal packets: · drop—Drops illegal packets. · logging—Generates log messages. · none—Does not process the packets and allows illegal packets to pass. $7: Reason why the message was generated: · Invalid DNS RR. · Failed to check DNS header flag. · Failed to check DNS header ID. |
|
Severity level |
6 |
|
Example |
ASPF/6/ASPF_IPV4_DNS:SrcIPAddr(1003)=1.1.1.3;DstIPAddr(1007)=2.1.1.2;RcvVPNInstance(1042)=vpn;RcvDSLiteTunnelPeer(1040)=dstunnel1;DomainName(1099)=www.h3c.com;Action(1053)=drop,logging;Reason(1056)=Check DNS RR invalid. |
|
Explanation |
ASPF inspection for DNS is configured. The device takes a specific action on IPv4 packets that are determined to be illegal for a reason. |
|
Recommended action |
No action is required. |
ASPF_IPV6_DNS
|
Message text |
SrcIPv6Addr(1036)=[IPADDR];DstIPv6Addr(1037)=[IPADDR];RcvVPNInstance(1042)=[STRING];DomainName(1099)=[STRING];Action(1053)=[STRING];Reason(1056)=[STRING]. |
|
Variable fields |
$1: Source IPv6 address. $2: Destination IPv6 address. $3: VPN instance name. $4: Domain name. $5: Action on the detected illegal packets: · drop—Drops illegal packets. · logging—Generates log messages. · none—Does not process the packet and allows illegal packets to pass. $6: Reason why the message was generated: · Invalid DNS RR. · Failed to check DNS header flag. · Failed to check DNS header ID. |
|
Severity level |
6 |
|
Example |
ASPF/6/ASPF_IPV6_DNS:SrcIPv6Addr(1036)=2001::1;DstIPv6Addr(1037)=3001::1;RcvVPNInstance(1042)=vpn;DomainName(1099)=www.h3c.com;Action(1053)=drop,logging;Reason(1056)=Check DNS RR invalid. |
|
Explanation |
ASPF inspection for DNS is configured. The device takes a specific action on IPv6 packets that are determined to be illegal for a reason. |
|
Recommended action |
No action is required. |
AUTOCFG messages
This section contains automatic configuration messages.
AUTOCFG_URL_EXECUTE_FAILURE
|
Message text |
URL-based automatic configuration failed at command line [STRING] and stopped. |
|
Variable fields |
$1: Command line that failed to be executed. |
|
Severity level |
4 |
|
Example |
AUTOCFG/4/AUTOCFG_URL_EXECUTE_FAILURE: URL-based automatic configuration failed at command line "system-view" and stopped. |
|
Explanation |
The automatic configuration process stopped at a command line that failed to be executed. The following command lines were not executed. |
|
Recommended action |
Record the log message and contact the technical support. |
AUTOCFG_URL_EXECUTE_SUCCESS
|
Message text |
URL-based automatic configuration finished successfully. |
|
Variable fields |
None |
|
Severity level |
6 |
|
Example |
AUTOCFG/6/AUTOCFG_URL_EXECUTE_SUCCESS: URL-based automatic configuration finished successfully. |
|
Explanation |
A URL-based automatic configuration process finished successfully. |
|
Recommended action |
No action is required. |
AUTOCFG_URL_START_FAILED
|
Message text |
URL-based automatic configuration service by [STRING] from [STRING] failed. |
|
Variable fields |
$1: Username. $2: IP address. |
|
Severity level |
5 |
|
Example |
AUTOCFG/6/AUTOCFG_URL_START_FAILED: URL-based automatic configuration service by admin from 192.168.111.250 failed. |
|
Explanation |
A user failed to start URL-based automatic device configuration. |
|
Recommended action |
Verify that the username and password are correct. |
AUTOCFG_URL_START_SUCCESS
|
Message text |
URL-based automatic configuration started by [STRING] from [STRING]. |
|
Variable fields |
$1: Username. $2: IP address. |
|
Severity level |
6 |
|
Example |
AUTOCFG/6/AUTOCFG_URL_START_SUCCESS: URL-based automatic configuration started by admin from 192.168.111.250. |
|
Explanation |
A user started URL-based automatic device configuration successfully. |
|
Recommended action |
No action is required. |
AVC messages
This section contains bandwidth management messages.
AVC_MATCH_IPV4_LOG
|
Message text |
Application(1002)=[STRING];UserName(1113)=[STRING];SrcIPAddr(1003)=[IPADDR];SrcPort(1004)=[USHORT];DstIPAddr(1007)=[IPADDR];DstPort(1008)=[USHORT];SrcZoneName(1025)=[STRING];DstZoneName(1035)=[STRING];PolicyName(1079)=[STRING];HitTime(1114)=[STRING];Action(1053)=[STRING]; |
|
Variable fields |
$1: Application name. $2: User name. $3: Source IPv4 address. $4: Source port number. $5: Destination IPv4 address. $6: Destination port number. $7: Source security zone. $8: Destination security zone. $9: Policy name. $10: Hit time. $11: Rule action. |
|
Severity level |
6 |
|
Example |
AVC/6/AVC_MATCH_IPV4_LOG:Application(1002)=App;UserName(1113)=User1;SrcIPAddr(1003)=12.2.2.2;SrcPort(1004)=5141;DstIPAddr(1007)=13.1.1.14;DstPort(1008)=5784;SrcZoneName(1025)=whx;DstZoneName(1035)=hea;PolicyName(1079)=aaa;HitTime(1114)=Wed, 22 May 2019 16:43:47;Action(1053)=drop; |
|
Explanation |
This message is generated and sent to the log host as a fast output log when a packet matches a traffic rule. |
|
Recommended action |
None. |
AVC_MATCH_IPV6_LOG
|
Message text |
Application(1002)=[STRING];UserName(1113)=[STRING];SrcIPv6Addr(1036)=[IPADDR];SrcPort(1004)=[USHORT];DstIPv6Addr(1037)=[IPADDR];DstPort(1008)=[USHORT];SrcZoneName(1025)=[STRING];DstZoneName(1035)=[STRING];PolicyName(1079)=[STRING];HitTime(1114)=[STRING];Action(1053)=[STRING]; |
|
Variable fields |
$1: Application name. $2: User name. $3: Source IPv6 address. $4: Source port number. $5: Destination IPv6 address. $6: Destination port number. $7: Source security zone. $8: Destination security zone. $9: Policy name. $10: Hit time. |
|
Severity level |
6 |
|
Example |
AVC/6/AVC_MATCH_IPV6_LOG:Application(1002)=App;UserName(1113)=User1;SrcIPv6Addr(1036)=12::2;SrcPort(1004)=5141;DstIPv6Addr(1037)=13::4;DstPort(1008)=5784;SrcZoneName(1025)=whx;DstZoneName(1035)=hea;PolicyName(1079)=aaa;HitTime(1114)=Wed, 22 May 2019 16:52:08;Action(1053)=drop; |
|
Explanation |
This message is generated and sent to the log host as a fast output log when a packet matches a traffic rule. |
|
Recommended action |
None. |
AVC_THRESHOLDWARNING_FASTLOGGING_FMT
|
Message text |
SrcIPAddr(1003)=[IPADDR];PolicyName(1079)=[STRING];ProfileName(1158)=[STRING];DeviceInfo(1159)=[STRING];BandwidthUpperLimit(1160)=[UINT32];BandwidthLowerLimit(1161)=[UINT32];UpperWarningValue(1162)=[UINT32];LowerWarningValue(1163)=[UINT32];CurRateValue(1164)=[UINT32];WarningTime(1165)=[STRING];WarningDuration(1166)=[UINT32]; |
|
Variable fields |
$1: Source IPv4 address. $2: Traffic policy name. $3: Traffic profile name. $4: Device information. $5: Maximum bandwidth threshold in kbps. $6: Minimum bandwidth threshold in kbps. $7: Actual rate in kbps that exceeds the maximum bandwidth threshold. $8: Actual rate in kbps that falls below the minimum bandwidth threshold. $9: Current traffic rate in kbps. $10: Warning time when the device detected a threshold violation. $11: Warning duration. (length of time the threshold violation lasted). |
|
Severity level |
6 |
|
Example |
AVC/6/AVC_THRESHOLDWARNING_FASTLOGGING_FMT:SrcIPAddr(1003)=192.168.1.8;PolicyName(1079)=a;ProfileName(1158)=p;DeviceInfo(1159)=YuShi;BandwidthUpperLimit(1160)=8366;BandwidthLowerLimit(1161)=2091;UpperWarningValue(1162)=6;LowerWarningValue(1163)=6;CurRateValue(1164)=6;WarningTime(1165)=Fri, 8 Oct 2019 17:38:32;WarningDuration(1166)=7; |
|
Explanation |
This message is generated and sent to the log host as a fast output log if a threshold violation occurs one minute or more after the previous threshold violation. |
|
Recommended action |
None. |
AVC_THRESHOLDWARNING_FASTLOGGING_IPV6FMT
|
Message text |
SrcIPv6Addr(1036)=[IPADDR];PolicyName(1079)=[STRING];ProfileName(1158)=[STRING];DeviceInfo(1159)=[STRING];BandwidthUpperLimit(1160)=[UINT32];BandwidthLowerLimit(1161)=[UINT32];UpperWarningValue(1162)=[UINT32];LowerWarningValue(1163)=[UINT32];CurRateValue(1164)=[UINT32];WarningTime(1165)=[STRING];WarningDuration(1166)=[UINT32]; |
|
Variable fields |
$1: Source IPv6 address. $2: Traffic policy name. $3: Traffic profile name. $4: Device information. $5: Maximum bandwidth threshold in kbps. $6: Minimum bandwidth threshold in kbps. $7: Actual rate in kbps that exceeds the maximum bandwidth threshold. $8: Actual rate in kbps that falls below the minimum bandwidth threshold. $9: Current traffic rate in kbps. $10: Warning time (time when the device detected a threshold violation). $11: Warning duration (length of time the threshold violation lasted). |
|
Severity level |
6 |
|
Example |
AVC/6/AVC_THRESHOLDWARNING_FASTLOGGING_IPV6FMT:SrcIPv6Addr(1036)=2001::1;PolicyName(1079)=a;ProfileName(1158)=p;DeviceInfo(1159)=YuShi;BandwidthUpperLimit(1160)=8366;BandwidthLowerLimit(1161)=2091;UpperWarningValue(1162)=6;LowerWarningValue(1163)=6;CurRateValue(1164)=6;WarningTime(1165)=Fri, 8 Oct 2019 17:38:32;WarningDuration(1166)=7; |
|
Explanation |
This message is generated and sent to the log host as a fast output log if a threshold violation occurs more than one minute after the previous threshold violation occurred. |
|
Recommended action |
None. |
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_BMP_STATE_CHANGED
|
Message text |
BGP [STRING]: Disconnected from BMP Server [STRING] for maximum limit of sending buffer reached. |
|
Variable fields |
$1: BGP instance name. $2: BMP server number. |
|
Severity level |
3 |
|
Example |
BGP/3/BGP_BMP_STATE_CHANGED: BGP default: Disconnected from BMP Server 3 for maximum limit of sending buffer reached. |
|
Explanation |
The TCP connection between the BMP client and the BMP server was terminated, because the number of sent messages exceeded the limit of the sending buffer. |
|
Recommended action |
1. Verify that the BMP server operates in asynchronous reception mode. 2. If the issue persists after you set the message reception mode of the BMP server to asynchronous reception, use either of the following methods: ¡ Try other configurations that can speed up message reception on the BMP server. ¡ Contact the technical support for help. |
BGP_EXCEED_ROA_LIMIT
|
Message text |
BGP [STRING].[STRING]: The number of ROAs ([UINT32]) from server [STRING] exceeds the limit [UINT32]. |
|
Variable fields |
$1: BGP instance name. $2: VPN instance name. This field is blank for the public network. $3: Number of ROAs received from the RPKI server. $4: IP address of the RPKI server. $5: Maximum number of ROAs that can be received from the RPKI server. |
|
Severity level |
4 |
|
Example |
BGP/4/BGP_EXCEED_ROA_LIMIT: BGP default.vpn1: The number of ROAs (101) from server 192.168.56.10 exceeds the limit 100. |
|
Explanation |
The number of ROAs received from the RPKI server exceeded the limit. |
|
Recommended action |
Determine whether the received ROAs can satisfy the current service demands: · If yes, contact the RPKI server maintainer to cancel advertising unnecessary ROAs. · If not, increase the maximum number of ROAs that can be received from the RPKI server. |
BGP_EXCEED_ROA_LIMIT_CLEAR
|
Message text |
BGP [STRING].[STRING]: The number of ROAs ([UINT32]) from server [STRING] fell below the limit [UINT32]. |
|
Variable fields |
$1: BGP instance name. $2: VPN instance name. This field is blank for the public network. $3: Number of ROAs received from the RPKI server. $4: IP address of the RPKI server. $5: Maximum number of ROAs that can be received from the RPKI server. |
|
Severity level |
6 |
|
Example |
BGP/6/BGP_EXCEED_ROA_LIMIT_CLEAR: BGP default.vpn1: The number of ROAs (99) from server 192.168.56.10 fell below the limit 100. |
|
Explanation |
The number of ROAs received from the RPKI server dropped below the limit. |
|
Recommended action |
No action is required. |
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 percentage of prefixes received from peer [STRING] ([STRING]) to the 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_RTID_CONFLICT
|
Message text |
Local router ID conflicts with the originator ID carried by a route. (Router ID=[STRING], instance=[STRING], VPN instance=[STRING], Peer=[STRING]) |
|
Variable fields |
$1: Router ID. $2: BGP instance name. $3: VPN instance name. This field is blank for the public network. $4: IP address of the BGP peer. |
|
Severity level |
3 |
|
Example |
BGP/3/BGP_RTID_CONFLICT: Local router ID conflicts with the originator ID carried by a route. (Router ID=2.2.2.2, instance=default, VPN instance=vpn1,Peer=192.168.1.1) |
|
Explanation |
The ORIGINATOR_ID attribute value for the BGP route is the same as the local router ID and thus the local device cannot receive the route. |
|
Recommended action |
Verify that the router ID of each device on the network is unique. |
BGP_STATE_CHANGED
|
Message text |
· Text 1: BGP [STRING].[STRING]: [STRING] state has changed from [STRING] to [STRING]. · Text 2: BGP [STRING].[STRING]: [STRING] state has changed from [STRING] to [STRING] for [STRING]. |
|
Variable fields |
In text 1: $1: BGP instance name. $2: VPN instance name. This field is blank for the public network. $3: IP address of the BGP peer. $4: Peer state before the state change. $5: Peer state after the state change. In text 2: $1: BGP instance name. $2: VPN instance name. This field is blank for the public network. $3: IP address of the BGP peer. $4: Peer state before the state change. $5: Peer state after the state change. $6: Reason for the state change. |
|
Severity level |
5 |
|
Example |
BGP/5/BGP_STATE_CHANGED: BGP default.vpn1:192.99.0.2 state has changed from OPENCONFIRM to ESTABLISHED. |
|
Explanation |
The state 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. |
BGP_STATE_CHANGED_REASON
|
Message text |
BGP [STRING].[STRING]: [STRING] state has changed from [STRING] to [STRING]. ([STRING]) |
|
Variable fields |
$1: BGP instance name. $2: VPN instance name. This field is blank for the public network. $3: IP address of the BGP peer. $4: Peer state before the state change. $5: Peer state after the state change. $6: Information about the BGP session disconnection event. · Reason—Reason for the BGP session disconnection event. · Error code—Notification error code or sub error code advertised or received by BGP. If the BGP session goes down due to TCP connection failures, this field is not displayed. · Local interface—Physical interface used to establish the BGP session. This field is displayed only when the BGP session between two directly connected peers goes down due to interface inaccessibility. |
|
Severity level |
5 |
|
Example |
BGP/5/BGP_STATE_CHANGED_REASON: BGP.vpn1: 192.99.0.2 state has changed from ESTABLISHED to IDLE. (Reason: Directly connected physical interface was down, error code: Send Notificationcode 6/0, local interface: Ethernet1/0/0) |
|
Explanation |
This informational message appears when the state of the session to a peer changes from Established to another state. |
|
Recommended action |
Determine whether a network error or packet loss occurs according to the reason for the BGP session disconnection event. |
CELLULAR
This section contains mobile communication modem management messages.
CELLULAR_APNPROFILE_ALARM
|
Message text |
Failed to apply APN profile to [STRING], because the APN profile name exceeds 62 characters. |
|
Variable fields |
$1: Name of the cellular interface. |
|
Severity level |
4 |
|
Example |
CELLULAR/4/CELLULAR_APNPROFILE_ALARM: Failed to apply APN profile to Cellular1/0, because the APN profile name exceeds 62 characters. |
|
Explanation |
The system failed to apply an APN profile to a cellular interface, because the name of the APN profile has exceeded 62 characters. |
|
Recommended action |
Make sure the name of the APN profile does not exceed 62 characters, and then apply the APN profile to the cellular interface again. |
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. |
CFD_NO_HRD_RESOURCE
|
Message text |
Failed to start CCM on service instance [INT32] because of insufficient hardware frequency resources. |
|
Variable fields |
$1: Service instance ID. |
|
Severity level |
6 |
|
Example |
CFD/6/CFD_NO_HRD_RESOURCE: -MDC=1; Failed to start CCM on service instance 7 because of insufficient hardware frequency resources. |
|
Explanation |
This message is generated when CCM sending fails to be enabled in a service instance because of insufficient hardware frequency resources. |
|
Recommended action |
Contact H3C Support. |
CFD_REACH_LOWERLIMIT
|
Message text |
[STRING] reached or fell below the lower limit [STRING] on MEP [UINT16] in service instance [INT32]. |
|
Variable fields |
$1: Monitored indicator: · Far-end frame loss ratio. · Near-end frame loss ratio. · Frame delay. $2: Threshold. $3: Local MEP ID. $4: Service instance ID. |
|
Severity level |
6 |
|
Example |
CFD/6/ CFD_REACH_LOWERLIMIT: Far-end frame loss ratio reached or fell below the lower limit 4% on MEP 2 in service instance 3. |
|
Explanation |
This message is generated when a monitored indicator reaches or falls below the lower limit. |
|
Recommended action |
No action is required. |
CFD_REACH_LOWERLIMIT_EX
|
Message text |
[STRING] reached or fell below the lower limit [STRING] on synthetic-slm test instance [STRING] in service instance [INT32]. |
|
Variable fields |
$1: Monitored indicator: · Far-end frame loss ratio. · Near-end frame loss ratio. $2: Threshold. $3: Source MEP ID and target MEP ID. $4: Service instance ID. |
|
Severity level |
6 |
|
Example |
CFD/6/ CFD_REACH_LOWERLIMIT_EX: Far-end frame loss ratio reached or fell below the lower limit 4% on synthetic-slm test instance mep(1001) to target-mep(2001) in service instance 1. |
|
Explanation |
This message is generated when a monitored indicator for single-ended synthetic LM reaches or falls below the lower limit. |
|
Recommended action |
No action is required. |
CFD_REACH_UPPERLIMIT
|
Message text |
[STRING] reached or exceeded the upper limit [STRING] on MEP [UINT16] in service instance [INT32]. |
|
Variable fields |
$1: Monitored indicator: · Far-end frame loss ratio. · Near-end frame loss ratio. · Frame delay. $2: Threshold. $3: Local MEP ID. $4: Service instance ID. |
|
Severity level |
6 |
|
Example |
CFD/6/ CFD_REACH_LOWERLIMIT: Far-end frame loss ratio reached or fell below the lower limit 4% on MEP 2 in service instance 3. |
|
Explanation |
This message is generated when a monitored indicator reaches or exceeds the upper limit. |
|
Recommended action |
No action is required. |
CFD_REACH_UPPERLIMIT_EX
|
Message text |
[STRING] reached or exceeded the upper limit [STRING] on synthetic-slm test instance [STRING] in service instance [INT32]. |
|
Variable fields |
$1: Monitored indicator: · Far-end frame loss ratio. · Near-end frame loss ratio. $2: Threshold. $3: Source MEP ID and target MEP ID. $4: Service instance ID. |
|
Severity level |
6 |
|
Example |
CFD/6/ CFD_REACH_UPPERLIMIT_EX: Far-end frame loss ratio reached or exceeded the upper limit 80% on synthetic-slm test instance mep(1001) to target-mep(2001) in service instance 1. |
|
Explanation |
This message is generated when a monitored indicator for single-ended synthetic LM reaches or exceeds the upper limit. |
|
Recommended action |
No action is required. |
CFD_RECEIVE_CCM
|
Message text |
MEP [UINT16] in SI [INT32] received 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_RECEIVE_CCM: MEP 1 in SI 7 received CCMs from RMEP 2. |
|
Explanation |
A MEP received CCMs from a remote MEP. |
|
Recommended action |
No action is required. |
CFGMAN messages
This section contains configuration management messages.
CFGMAN_ARCHIVE_SCP_FAIL
|
Message text |
Archive configuration to SCP server failed: IP = [STRING], Directory = [STRING], Username = [STRING] |
|
Variable fields |
$1: IP address of the SCP server. $2: Directory that saves the configuration archives on the SCP server. $3: Username for logging in to the SCP server. |
|
Severity level |
5 |
|
Example |
CFGMAN/5/CFGMAN_ARCHIVE_SCP_FAIL: Archive configuration to SCP server failed: IP = 192.168.21.21, Directory = /test/, Username = admin |
|
Explanation |
The device failed to archive the running configuration to an SCP server. |
|
Recommended action |
No action is required. |
CFGMAN_ARCHIVE_FAIL
|
Message text |
Failed to archive the running configuration to a remote server: Location=[STRING] |
|
Variable fields |
$1: URL address of the remote server. For an FTP server, enter the URL in the format of ftp://username@server address[:port number]/file path. To specify an IPv6 address, enclose the IPv6 address in square brackets ([ ]). For an TFTP server, do not include the username in the URL address. |
|
Severity level |
4 |
|
Example |
CFGMAN/4/CFGMAN_ARCHIVE_FAIL: Failed to archive the running configuration to a remote server: Location=ftp://[email protected][:21]/test/ |
|
Explanation |
The device failed to archive the running configuration to a remote server. |
|
Recommended action |
1. Verify that the running configuration can be saved locally successfully. 2. Verify that you can log in to the remote server. 3. Verify that the remote server has sufficient storage space. |
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 SNMP or was a configuration database change detected by SNMP. ¡ 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. |
CFGMAN_REPLACE_CANCEL
|
Message text |
Configuration rollback from remote server was canceled: Replacement file=[STRING] |
|
Variable fields |
$1: URL address of the replacement file on the remote server. For an FTP server, enter the URL in the format of ftp://username@server address[:port number]/file path. To specify an IPv6 address, enclose the IPv6 address in square brackets ([ ]). For an TFTP server, do not include the username in the URL address. |
|
Severity level |
5 |
|
Example |
CFGMAN/5/CFGMAN_REPLACE_CANCEL: Configuration rollback from remote server was canceled: Replacement file=ftp://[email protected][:21]/test/startup.cfg |
|
Explanation |
This log is generated to inform the user that the configuration rollback operation has been canceled under the following conditions: · The configuration replace server file command was executed to enable remote configuration rollback at a specified time. · The system time is changed and exceeds the specified time. As a result, the configuration rollback operation is canceled. |
|
Recommended action |
Re-configure remote configuration rollback as needed. |
CFGMAN_REPLACE_FAIL
|
Message text |
Failed to replace running configuration with a remote configuration file: File=[STRING] |
|
Variable fields |
$1: URL address of the replacement file on the remote server. For an FTP server, enter the URL in the format of ftp://username@server address[:port number]/file path. To specify an IPv6 address, enclose the IPv6 address in square brackets ([ ]). For an TFTP server, do not include the username in the URL address. |
|
Severity level |
4 |
|
Example |
CFGMAN/4/CFGMAN_REPLACE_FAIL: Failed to replace running configuration with a remote configuration file: File=ftp://[email protected][:21]/test/startup.cfg |
|
Explanation |
The device failed to replace running configuration with a remote configuration file. |
|
Recommended action |
1. Verify that you can access the server successfully. 2. Verify that the specified configuration file exists on the server. 3. Verify that the local storage space is sufficient. 4. Verify that the content and format of the configuration file are correct. |
CFGMAN_REPLACE_SOON
|
Message text |
The system will replace running configuration with a remote file in 1 minute: File=[STRING] |
|
Variable fields |
$1: URL address of the replacement file on the remote server. For an FTP server, enter the URL in the format of ftp://username@server address[:port number]/file path. To specify an IPv6 address, enclose the IPv6 address in square brackets ([ ]). For an TFTP server, do not include the username in the URL address. |
|
Severity level |
5 |
|
Example |
CFGMAN/5/CFGMAN_REPLACE_SOON: The system will replace running configuration with a remote file in 1 minute: File=ftp://[email protected][:21]/test/startup.cfg |
|
Explanation |
The device is scheduled to roll back the running configuration with the specified replacement configuration file on the remote server at a specified time. This log information is printed one minute before the specified time. |
|
Recommended action |
To disable remote configuration rollback, execute the undo configuration replace server file command. |
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. |
CLKM messages
This section contains clock monitoring module messages.
CLKM_ESMC_PKT_ALARM
|
Message text |
ESMC packets were lost. (PortName=[STRING]) |
|
Variable fields |
$1: Name of the interface that receives ESMC packets. |
|
Severity level |
4 |
|
Example |
CLKM/4/CLKM_ESMC_PKT_ALARM: ESMC packets were lost. (PortName=G1/0/1) |
|
Explanation |
The device issues this message when ESMC packets were lost. |
|
Recommended action |
To resolve the issue: 1. Determine whether both the local and peer interfaces are ESMC-enabled. ¡ If both of them are ESMC-enabled, go to 3. ¡ If one or neither of them is ESMC-enabled, go to 2. ¡ If the device continues to output this message, go to 3. ¡ If the device does not output this message any more, the issue is resolved. 3. Collect alarm, log, and configuration information and contact the support. |
CLKM_SOURCE_FREQDEVIATION_ALARM
|
Message text |
The frequency offset of the clock reference for [STRING] has crossed the threshold. |
|
Variable fields |
|
|
Severity level |
4 |
|
Example |
CLKM/4/CLKM_SOURCE_FREQDEVIATION_ALARM: The frequency offset of the clock reference for chassis 1 has crossed the threshold. |
|
Explanation |
The clock frequency deviation crossed the threshold. |
|
Recommended action |
Identify whether the clock frequency deviation status is Alarm. |
CLKM_SOURCE_FREQDEVIATION_NORMAL
|
Message text |
The frequency offset of the clock reference for [STRING] has dropped below the threshold and resumed to normal. |
|
Variable fields |
$1: Device or chassis ID. |
|
Severity level |
4 |
|
Example |
CLKM/4/CLKM_SOURC_FREQDEVIATION_NORMAL: The frequency offset of the clock reference for chassis 1 has dropped below the threshold and resumed to normal. |
|
Explanation |
The clock frequency deviation resumed to normal. |
|
Recommended action |
N/A |
CLKM_SOURCE_LOST
|
Message text |
|
|
Variable fields |
$1: Device or chassis ID. |
|
Severity level |
4 |
|
Example |
CLKM/4/CLKM_SOURCE_LOST: Chassis 1 has lost signals from the clock reference. |
|
Explanation |
|
|
Recommended action |
Examine the related configuration and clock reference status. |
CLKM_SOURCE_SSM_DEGRADE
|
Message text |
|
|
Variable fields |
$1: Device or chassis ID. $2: SSM level before degradation. $3: SSM level after degradation. $4: SSM level degradation threshold. |
|
Severity level |
4 |
|
Example |
|
|
Explanation |
The SSM level of the clock reference degraded to a value lower than the degradation threshold. |
|
Recommended action |
Examine the related configuration and clock reference status. |
CLKM_SOURCE_SSM_RESUME
|
Message text |
The SSM quality level of the clock reference for [STRING] has risen from [STRING] to [STRING].The SSM quality level threshold is [STRING]. |
|
Variable fields |
$1: Device or chassis ID. $2: SSM level before degradation. $3: SSM level after degradation. $4: SSM level degradation threshold. |
|
Severity level |
4 |
|
Example |
CLKM/4/CLKM_SOURCE_SSM_RESUME: The SSM quality level of the clock reference for chassis 1 has risen from SEC to SSU-A. The SSM quality level threshold is SSU-A. |
|
Explanation |
The SSM quality level of the clock reference resumed to the acceptable ranges. |
|
Recommended action |
N/A |
CLKM_SOURCE_SWITCHOVER
|
Message text |
|
|
Variable fields |
$1: Device or chassis ID. $2: Clock source type. ¡ Name of the line clock input port. ¡ BITS0. ¡ BITS1. ¡ PTP. ¡ Local clock reference. |
|
Severity level |
4 |
|
Example |
CLKM/4/CLKM_SOURCE_SSM_SWITCHOVER: The clock reference of chassis 1 has changed to BITS0. |
|
Explanation |
The clock reference was changed. |
|
Recommended action |
N/A |
DEV messages
This section contains device management messages.
AUTOSWITCH_FAULT
|
Message text |
An active/standby or master/subordinate switchover was performed automatically on [STRING], and a fault occurred during the switchover process. |
|
Variable fields |
$1: Chassis number. The value is the device when the device is in standalone mode. |
|
Severity level |
1 |
|
Example |
DEV/1/ AUTO_SWITCH_FAULT: An active/standby or master/subordinate switchover was performed automatically on Chassis 1, and a fault occurred during the switchover process. |
|
Explanation |
A fault occurred during an automatic active/standby or master/subordinate switchover process. |
|
Recommended action |
1. Execute the display diagnostic-information command to collect and save diagnostic information. 2. Reboot the device manually for clearing the fault. 3. Execute the display device command to display the device status. If the device status is not Normal, contact H3C Support. |
AUTOSWITCH_FAULT_REBOOT
|
Message text |
An active/standby or master/subordinate switchover was performed automatically on [STRING], and a fault occurred during the switchover process. The system will immediately restart [STRING] to clear the fault. |
|
Variable fields |
$1: Chassis number. The value is "the device" when the device is in standalone mode. $2: Chassis number and slot number or slot number. |
|
Severity level |
1 |
|
Example |
DEV/1/AUTO_SWITCH_FAULT_REBOOT: An active/standby or master/subordinate switchover was performed automatically on Chassis 1, and a fault occurred during the switchover process. The system will immediately restart chassis 1 slot 0 to clear the fault. |
|
Explanation |
A fault occurred during an automatic active/standby or master/subordinate switchover process. The device will restart the faulty card immediately to clear the fault. |
|
Recommended action |
Execute the display device command to display the card status after the card is rebooted. If the card status is not Normal, contact H3C Support. |
BOARD_ALARM_CLEAR
|
Message text |
Board alarm cleared. (PhysicalIndex=<[UINT]>, PhysicalName=<[STRING]>, RelativeResource=<[STRING]>, ErrorCode=<[UINT]>, Reason=<[STRING]>) |
|
Variable fields |
$1: Entity index. $2: Entity name. $3: Fault location information. $4: Fault code. $5: Fault reason description. |
|
Severity level |
2 |
|
Example |
DEV/2/BOARD_ALARM_CLEAR: Board alarm cleared. (PhysicalIndex=140, PhysicalName=Level 1 Module 9 on Chassis 1, RelativeResource=1, ErrorCode=441002, Reason=FPGA load failed.) |
|
Explanation |
A card alarm was cleared. |
|
Recommended action |
No action is required. |
BOARD_ALARM_OCCUR
|
Message text |
Board alarm occurred. (PhysicalIndex=<[UINT]>, PhysicalName=<[STRING]>, RelativeResource=<[STRING]>, ErrorCode=<[UINT]>, Reason=<[STRING]>) |
|
Variable fields |
$1: Entity index. $2: Entity name. $3: Fault location information. $4: Fault code. $5: Fault reason description. |
|
Severity level |
2 |
|
Example |
DEV/2/BOARD_ALARM_OCCUR: Board alarm occurred. (PhysicalIndex=140, PhysicalName=Level 1 Module 9 on Chassis 1, RelativeResource=1, ErrorCode=441002, Reason=FPGA load failed.) |
|
Explanation |
A card alarm occurred. |
|
Recommended action |
For more information, review the related alarm information, or contact H3C Support. |
BOARD_FATALALARM_OCCUR
|
Message text |
Board fatal alarm occurred. (PhysicalIndex=<[UINT]>, PhysicalName=<[STRING]>, RelativeResource=<[STRING]>, ErrorCode=<[UINT]>, Reason=<[STRING]>) |
|
Variable fields |
$1: Entity index. $2: Entity name. $3: Fault location information. $4: Fault code. $5: Fault reason description. |
|
Severity level |
1 |
|
Example |
DEV/1/BOARD_FATALALARM_OCCUR: Board fatal alarm occurred. (PhysicalIndex=180136, PhysicalName=Level 1 Module 5 on Chassis 2, RelativeResource=2/5/0, ErrorCode=000008, Reason=System can't work without SFU board in slot 1.) |
|
Explanation |
This message was generated in one of the following situations: · The system cannot operate correctly because a slot is not installed with the correct card. · The system is not installed with the correct type of fabric modules or service modules. For more information, see the fault description. |
|
Recommended action |
Execute the display device command to display the fabric module status. If the fabric module status is Normal, but the fault is still present, contact H3C Support. |
BOARD_REBOOT
|
Message text |
Board is rebooting on [STRING]. |
|
Variable fields |
$1: Chassis number and slot number or slot number. |
|
Severity level |
5 |
|
Example |
DEV/5/BOARD_REBOOT: Board is rebooting on slot 1. |
|
Explanation |
A card was manually or automatically rebooted. |
|
Recommended action |
If an unexpected automatic reboot occurred, perform the following tasks: 1. Execute the display version command after the slot starts up. 2. Check the Last reboot reason field for the reboot reason. 3. If an exception caused the reboot, contact H3C Support. |
BOARD_REMOVED
|
Message text |
Board was removed from [STRING], type is [STRING]. |
|
Variable fields |
$1: Chassis number and slot number or slot number. $2: Card type. |
|
Severity level |
3 |
|
Example |
DEV/3/BOARD_REMOVED: Board was removed from slot 1, type is LSQ1FV48SA. |
|
Explanation |
An LPU or a standby MPU was removed from a member device, causing the device to leave the IRF fabric. |
|
Recommended action |
If the LPU or MPU was not manually removed, perform the following tasks: 1. Verify that the card is securely seated. 2. Replace the card if the message persists. 3. Reboot the device to make it join the IRF fabric. 4. If the issue persists, contact H3C Support. |
BOARD_RUNNING_FAULT
|
Message text |
A fault was detected on [STRING]. |
|
Variable fields |
$1: Chassis number and slot number or slot number. |
|
Severity level |
1 |
|
Example |
DEV/1/ BOARD_FAULT_REBOOT: A fault was detected on Chassis 1 slot 0. |
|
Explanation |
A fault was detected on a card. |
|
Recommended action |
1. Execute the display diagnostic-information command to collect and save diagnostic information. 2. Reboot the card manually for clearing the fault. 3. Execute the display device command to display the card status. If the card status is not Normal, contact H3C Support. |
BOARD_RUNNING_FAULT_REBOOT
|
Message text |
A fault was detected on [STRING]. The system will immediately restart [STRING] to clear the fault. |
|
Variable fields |
$1: Chassis number and slot number or slot number. $2: Chassis number and slot number or slot number. |
|
Severity level |
1 |
|
Example |
DEV/1/ BOARD_RUNNING_FAULT_REBOOT: A fault was detected on Chassis 1 slot 0. The system will immediately restart Chassis 1 Slot 0 to clear the fault. |
|
Explanation |
A fault was detected on a card. The device will restart the card immediately to clear the fault. |
|
Recommended action |
If the fault persists after the card reboots, contact H3C Support. |
BOARD_STATE_NORMAL
|
Message text |
Board state changed to Normal on [STRING], type is [STRING]. |
|
Variable fields |
$1: Chassis number and slot number or slot number. $2: Card type. |
|
Severity level |
5 |
|
Example |
DEV/5/BOARD_STATE_NORMAL: Board state changed to Normal on slot 1, type is LSQ1FV48SA. |
|
Explanation |
A newly installed LPU or standby MPU completed initialization. You cannot perform a master/standb switchover when this message, because this message does not indicate that the configuration has been recovered. |
|
Recommended action |
No action is required. |
CFCARD_INSERTED
|
Message text |
CF card was inserted in [STRING] [STRING]. |
|
Variable fields |
$1: Chassis number and slot number, slot number, or the device. $2: CF card slot number. This field is displayed only if the device supports multiple CF cards. |
|
Severity level |
4 |
|
Example |
DEV/4/CFCARD_INSERTED: CF card was inserted in slot 1 CF card slot 1. |
|
Explanation |
A CF card was installed. |
|
Recommended action |
No action is required. |
CFCARD_REMOVED
|
Message text |
CF card was removed from [STRING] [STRING]. |
|
Variable fields |
$1: Chassis number and slot number, slot number, or the device. $2: CF card slot number. This field is displayed only if the device supports multiple CF cards. |
|
Severity level |
3 |
|
Example |
DEV/3/CFCARD_REMOVED: CF card was removed from slot 1 CF card slot 1. |
|
Explanation |
A CF card was removed. |
|
Recommended action |
If the CF card was not manually removed, perform the following tasks: 1. Verify that the card is securely seated. 2. Replace the card if the message persists. 3. If the issue persists, contact H3C Support. |
CHASSIS_REBOOT
|
Message text |
Chassis [STRING] is rebooting now. |
|
Variable fields |
$1: Chassis number. |
|
Severity level |
5 |
|
Example |
DEV/5/CHASSIS_REBOOT: Chassis 1 is rebooting now. |
|
Explanation |
The chassis was manually or automatically rebooted. |
|
Recommended action |
If an unexpected automatic reboot occurs, perform the following tasks: 1. Execute the display version command after the chassis starts up. 2. Check the Last reboot reason field for the reboot reason. 3. If an exception caused the reboot, contact H3C Support. |
CPU_STATE_NORMAL
|
Message text |
Cpu state changed to Normal on [STRING]. |
|
Variable fields |
$1: Chassis number, slot number, and CPU number, or slot number and CPU number. The CPU number is displayed only if multiple CPUs are supported. |
|
Severity level |
5 |
|
Example |
DEV/5/CPU_STATE_NORMAL: Cpu state changed to Normal on slot 1 cpu 1. |
|
Explanation |
CPU status changed to normal. |
|
Recommended action |
No action is required. |
DEV_CLOCK_CHANGE
|
Message text |
-User=[STRING]-IPAddr=[IPADDR]; System clock changed from [STRING] to [STRING]. |
|
Variable fields |
$1: Username of the login user. $2: IP address of the login user. $3: Old time. $4: New time. |
|
Severity level |
5 |
|
Example |
DEV/5/DEV_CLOCK_CHANGE: -User=admin-IPAddr=192.168.1.2; System clock changed from 15:49:52 01/02/2013 to 15:50:00 01/02/2013. |
|
Explanation |
The system time changed. |
|
Recommended action |
No action is required. |
DEV_FAULT_TOOLONG
|
Message text |
Card in [STRING] is still in Fault state for [INT32] minutes. |
|
Variable fields |
$1: Chassis number and slot number or slot number. $2: Time duration during which the card stayed in Fault state. |
|
Severity level |
4 |
|
Example |
DEV/4/DEV_FAULT_TOOLONG: Card in slot 1 is still in Fault state for 60 minutes. |
|
Explanation |
A card stayed in Fault state for a long period of time. |
|
Recommended action |
1. Reboot the card. 2. If the issue persists, contact H3C Support. |
FAN_ABSENT
|
Message text |
Pattern 1: Fan [INT32] is absent. Pattern 2: Chassis [INT32] fan [INT32] is absent. |
|
Variable fields |
Pattern 1: $1: Fan tray number. Pattern 2: $1: Chassis number. $2: Fan tray number. |
|
Severity level |
3 |
|
Example |
DEV/3/FAN_ABSENT: Fan 2 is absent. |
|
Explanation |
A fan tray was not in place. |
|
Recommended action |
1. Check the fan tray slot: ¡ If the fan tray slot is empty, the temperature might have increased and the system recommends that you install a fan tray. ¡ If a fan tray is present, verify that the fan tray is securely seated. 2. Replace the fan tray if the message persists. 3. If the issue persists, contact H3C Support. |
FAN_ALARM_CLEAR
|
Message text |
Fan alarm cleared. (PhysicalIndex=<[UINT]>, PhysicalName=<[STRING]>, RelativeResource=<[STRING]>, ErrorCode=<[UINT]>, Reason=<[STRING]>) |
|
Variable fields |
$1: Entity index. $2: Entity name. $3: Fault location information. $4: Fault code. $5: Fault reason description. |
|
Severity level |
2 |
|
Example |
DEV/2/FAN_ALARM_CLEAR: Fan alarm cleared. (PhysicalIndex=199, PhysicalName=Fan 2, RelativeResource=0, ErrorCode=300020, Reason=Fan tray is not present.) |
|
Explanation |
A fan tray alarm was cleared. |
|
Recommended action |
No action is required. |
FAN_ALARM_OCCUR
|
Message text |
Fan alarm occurred. ( PhysicalIndex=<[UINT]>, PhysicalName=<[STRING]>, RelativeResource=<[STRING]>, ErrorCode=<[UINT]>, Reason=<[STRING]>) |
|
Variable fields |
$1: Entity index. $2: Entity name. $3: Fault location information. $4: Fault code. $5: Fault reason description. |
|
Severity level |
2 |
|
Example |
DEV/2/FAN_ALARM_OCCUR: Fan alarm occurred. (PhysicalIndex=199, PhysicalName=Fan 2, RelativeResource=0, ErrorCode=300020, Reason=Fan tray is not present.) |
|
Explanation |
A fan tray alarm occurred. |
|
Recommended action |
1. Re-install the fan tray that operates incorrectly. 2. Replace the fan tray. 3. If the issue persists, contact H3C Support. |
FAN_DIRECTION_NOT_PREFERRED
|
Message text |
Fan [INT32] airflow direction is not preferred on [STRING], please check it. |
|
Variable fields |
$1: Fan tray number. $2: Chassis number and slot number or slot number. |
|
Severity level |
1 |
|
Example |
DEV/1/FAN_DIRECTION_NOT_PREFERRED: Fan 1 airflow direction is not preferred on slot 1, please check it. |
|
Explanation |
The airflow direction of the fan tray is different from the airflow direction setting. |
|
Recommended action |
1. Verify that the airflow direction setting is correct. 2. Verify that the fan tray model provides the same airflow direction as the configured setting. 3. If the issue persists, contact H3C Support. |
FAN_FAILED
|
Message text |
Pattern 1: Fan [INT32] failed. Pattern 2: Chassis [STRING] fan [INT32] failed. |
|
Variable fields |
Pattern 1: $1: Fan tray number. Pattern 2: $1: Chassis number. $2: Fan tray number. |
|
Severity level |
2 |
|
Example |
DEV/2/FAN_FAILED: Fan 2 failed. |
|
Explanation |
The fan tray stopped because of an exception. |
|
Recommended action |
Replace the fan tray. |
FAN_FATALALARM_CLEAR
|
Message text |
Fan fatal alarm cleared. (PhysicalIndex=<[UINT]>, PhysicalName=<[STRING]>, RelativeResource=<[STRING]>, ErrorCode=<[UINT]>, Reason=<[STRING]>) |
|
Variable fields |
$1: Entity index. $2: Entity name. $3: Fault location information. $4: Fault code. $5: Fault reason description. |
|
Severity level |
1 |
|
Example |
DEV/1/FAN_FATALALARM_CLEAR: Fan warning alarm cleared. (PhysicalIndex=199, PhysicalName=Fan 2, RelativeResource=0, ErrorCode=300016, Reason=The fan resumed running.) |
|
Explanation |
A fatal fan tray alarm was cleared. |
|
Recommended action |
Contact H3C Support. |
FAN_FATALALARM_OCCUR
|
Message text |
Fan fatal alarm occurred. (PhysicalIndex=<[UINT]>, PhysicalName=<[STRING]>, RelativeResource=<[STRING]>, ErrorCode=<[UINT]>, Reason=<[STRING]>) |
|
Variable fields |
$1: Entity index. $2: Entity name. $3: Fault location information. $4: Fault code. $5: Fault reason description. |
|
Severity level |
1 |
|
Example |
DEV/1/FAN_FATALALARM_OCCUR: Fan fatal alarm occurred. (PhysicalIndex=199, PhysicalName=Fan 2, RelativeResource=0, ErrorCode=300016, Reason=The fan stopped running.) |
|
Explanation |
A fatal fan tray alarm occurred. |
|
Recommended action |
Contact H3C Support. |
FAN_RECOVERED
|
Message text |
Pattern 1: Fan [INT32] recovered. Pattern 2: Chassis [STRING] fan [INT32] recovered. |
|
Variable fields |
Pattern 1: $1: Fan tray number. Pattern 2: $1: Chassis number. $2: Fan tray number. |
|
Severity level |
2 |
|
Example |
DEV/2/FAN_RECOVERED: Fan 2 recovered. |
|
Explanation |
The fan tray started to operate correctly after it was installed. |
|
Recommended action |
No action is required. |
POWER_ABSENT
|
Message text |
Pattern 1: Power [INT32] is absent. Pattern 2: Chassis [STRING] power [INT32] is absent. |
|
Variable fields |
Pattern 1: $1: Power supply number. Pattern 2: $1: Chassis number. $2: Power supply number. |
|
Severity level |
3 |
|
Example |
DEV/3/POWER_ABSENT: Power 1 is absent. |
|
Explanation |
A power supply was removed. |
|
Recommended action |
1. Check the power supply slot. ¡ If the power supply slot is empty, install a power supply. ¡ If a power supply is present, verify that the power supply is securely seated. 2. If the issue persists, replace the power supply. 3. If the issue persists, contact H3C Support. |
POWER_ALARM_CLEAR
|
Message text |
Power alarm cleared. (PhysicalIndex=<[UINT]>, PhysicalName=<[STRING]>, RelativeResource=<[STRING]>, ErrorCode=<[UINT]>, Reason=<[STRING]>) |
|
Variable fields |
$1: Entity index. $2: Entity name. $3: Fault location information. $4: Fault code. $5: Fault reason description. |
|
Severity level |
2 |
|
Example |
DEV/2/POWER_ALARM_CLEAR: Power alarm cleared. (PhysicalIndex=163, PhysicalName=Unknown Power 2, RelativeResource=0, ErrorCode=233001, Reason=Overtemperature occurred on the power supply.) |
|
Explanation |
A power supply alarm was cleared. |
|
Recommended action |
No action is required. |
POWER_ALARM_OCCUR
|
Message text |
Power alarm occurred. (PhysicalIndex=<[UINT]>, PhysicalName=<[STRING]>, RelativeResource=<[STRING]>, ErrorCode=<[UINT]>, Reason=<[STRING]>) |
|
Variable fields |
$1: Entity index. $2: Entity name. $3: Fault location information. $4: Fault code. $5: Fault reason description. |
|
Severity level |
2 |
|
Example |
DEV/2/POWER_ALARM_OCCUR: Power alarm occurred. (PhysicalIndex=163, PhysicalName=Unknown Power 2, RelativeResource=0, ErrorCode=233001, Reason=Overtemperature occurred on the power supply.) |
|
Explanation |
A power supply alarm was cleared. |
|
Recommended action |
1. Execute the display power command to display the power supply status. 2. If the power supply status is Absent, verify that the power supply is installed correctly. 3. Replace the power supply. 4. If the issue persists, contact H3C Support. |
POWER_FAILED
|
Message text |
Pattern 1: Power [INT32] failed. Pattern 2: Chassis [STRING] power [INT32] failed. |
|
Variable fields |
Pattern 1: $1: Power supply number. Pattern 2: $1: Chassis number. $2: Power supply number. |
|
Severity level |
2 |
|
Example |
DEV/2/POWER_FAILED: Power 1 failed. |
|
Explanation |
A power supply failed. |
|
Recommended action |
Replace the power supply. |
POWER_MONITOR_ABSENT
|
Message text |
Pattern 1: Power monitor unit [INT32] is absent. Pattern 2: Chassis [STRING] power monitor unit [INT32] is absent. |
|
Variable fields |
Pattern 1: $1: Power monitoring module number. Pattern 2: $1: Chassis number. $2: Power monitoring module number. |
|
Severity level |
3 |
|
Example |
DEV/3/POWER_MONITOR_ABSENT: Power monitor unit 1 is absent. |
|
Explanation |
A power monitoring module was removed. |
|
Recommended action |
1. Check the power monitoring module slot. ¡ If the power monitoring module slot is empty, install a power monitoring module. ¡ If a power monitoring module is present, verify that the power monitoring module is securely seated. 2. If the issue persists, replace the power monitoring module. 3. If the issue persists, contact H3C Support. |
POWER_MONITOR_FAILED
|
Message text |
Pattern 1: Power monitor unit [INT32] failed. Pattern 2: Chassis [STRING] power monitor unit [INT32] failed. |
|
Variable fields |
Pattern 1: $1: Power monitoring module number. Pattern 2: $1: Chassis number. $2: Power monitoring module number. |
|
Severity level |
2 |
|
Example |
DEV/2/POWER_MONITOR_FAILED: Power monitor unit 1 failed. |
|
Explanation |
A power monitoring module failed. |
|
Recommended action |
Replace the power monitoring module. |
POWER_MONITOR_RECOVERED
|
Message text |
Pattern 1: Power monitor unit [INT32] recovered. Pattern 2: Chassis [STRING] power monitor unit [INT32] recovered. |
|
Variable fields |
Pattern 1: $1: Power monitoring module number. Pattern 2: $1: Chassis number. $2: Power monitoring module number. |
|
Severity level |
2 |
|
Example |
DEV/2/POWER_MONITOR_RECOVERED: Power monitor unit 1 recovered. |
|
Explanation |
The power monitoring module started to operate correctly after it was installed. |
|
Recommended action |
No action is required. |
POWER_RECOVERED
|
Message text |
Pattern 1: Power [INT32] recovered. Pattern 2: Chassis [STRING] power [INT32] recovered. |
|
Variable fields |
Pattern 1: $1: Power supply number. Pattern 2: $1: Chassis number. $2: Power supply number. |
|
Severity level |
2 |
|
Example |
DEV/2/POWER_RECOVERED: Power 1 recovered. |
|
Explanation |
The power supply started to operate correctly after it was installed. |
|
Recommended action |
No action is required. |
POWER_WARNING_CLEAR
|
Message text |
Power warning alarm cleared. (PhysicalIndex=<[UINT]>, PhysicalName=<[STRING]>, RelativeResource=<[STRING]>, ErrorCode=<[UINT]>, Reason=<[STRING]>) |
|
Variable fields |
$1: Entity index. $2: Entity name. $3: Fault location information. $4: Fault code. $5: Fault reason description. |
|
Severity level |
4 |
|
Example |
DEV/4/POWER_WARNING_CLEAR: Power warning alarm cleared. (PhysicalIndex=163, PhysicalName=Unknown Power 2, RelativeResource=0, ErrorCode=200037, Reason=No enough power to power on the board in chassis $1 slot $2. Required power is $3 W, available power is $4 W.) |
|
Explanation |
A warning power supply alarm was cleared. |
|
Recommended action |
No action is required. |
POWER_WARNING_OCCUR
|
Message text |
Power warning alarm occurred. (PhysicalIndex=<[UINT]>, PhysicalName=<[STRING]>, RelativeResource=<[STRING]>, ErrorCode=<[UINT]>, Reason=<[STRING]>) |
|
Variable fields |
$1: Entity index. $2: Entity name. $3: Fault location information. $4: Fault code. $5: Fault reason description. |
|
Severity level |
4 |
|
Example |
DEV/4/POWER_WARNING_OCCUR: Power warning alarm occurred. (PhysicalIndex=163, PhysicalName=Unknown Power 2, RelativeResource=0, ErrorCode=200037, Reason=No enough power to power on the board in chassis $1 slot $2. Required power is $3 W, available power is $4 W.) |
|
Explanation |
A warning power supply alarm occurred. |
|
Recommended action |
Replace the power supply or contact H3C Support. |
SUBCARD_FAULT
|
Message text |
Subcard state changed to Fault on [STRING] subslot [INT32], type is [STRING]. |
|
Variable fields |
$1: Chassis number and slot number or slot number. $2: Subslot number. $3: Subcard type. |
|
Severity level |
2 |
|
Example |
DEV/2/SUBCARD_FAULT: Subcard state changed to Fault on slot 1 subslot 1, type is MIM-1ATM-OC3SML. |
|
Explanation |
The subcard failed, or its status changed to Fault after it was rebooted. |
|
Recommended action |
Track the status of the subcard. · If the status of the subcard changes to Normal later, no action is required. · If the status is always Fault, replace the subcard. |
SUBCARD_INSERTED
|
Message text |
Subcard was inserted in [STRING] subslot [INT32], type is [STRING]. |
|
Variable fields |
$1: Chassis number and slot number or slot number. $2: Subslot number. $3: Subcard type. |
|
Severity level |
4 |
|
Example |
DEV/4/SUBCARD_INSERTED: Subcard was inserted in slot 1 subslot 1, type is MIM-1ATM-OC3SML. |
|
Explanation |
A subcard was installed. |
|
Recommended action |
No action is required. |
SUBCARD_REBOOT
|
Message text |
Subcard is rebooting on [STRING] subslot [INT32]. |
|
Variable fields |
$1: Chassis number and slot number or slot number. $2: Subslot number. |
|
Severity level |
5 |
|
Example |
DEV/5/SUBCARD_REBOOT: Subcard is rebooting on slot 1 subslot 1. |
|
Explanation |
The subcard was manually or automatically rebooted. |
|
Recommended action |
· If the subcard operates correctly after it starts up, no action is required. · If you want to know the reboot reason or the subcard keeps rebooting, contact H3C Support. |
SUBCARD_REMOVED
|
Message text |
Subcard was removed from [STRING] subslot [INT32], type is [STRING]. |
|
Variable fields |
$1: Chassis number and slot number or slot number. $2: Subslot number. $3: Subcard type. |
|
Severity level |
3 |
|
Example |
DEV/3/SUBCARD_REMOVED: Subcard was removed from slot 1 subslot 1, type is MIM-1ATM-OC3SML. |
|
Explanation |
A subcard was removed. |
|
Recommended action |
If the subcard was not manually removed, perform the following tasks: 1. Verify that the subcard is securely seated. 2. Replace the subcard if the message persists. 3. If the issue persists, contact H3C Support. |
SYSTEM_REBOOT
|
Message text |
System is rebooting now. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
DEV/4/SYSTEM_REBOOT: System is rebooting now. |
|
Explanation |
The system was manually or automatically rebooted. |
|
Recommended action |
If an unexpected automatic reboot occurred, perform the following tasks: 1. Execute the display version command after the system starts up. 2. Check the Last reboot reason field for the reboot reason. 3. If an exception caused the reboot, contact H3C Support. |
TEMPERATURE_ALARM
|
Message text |
Pattern 1: Temperature is greater than the high-temperature alarming threshold on sensor [STRING] [USHOT]. Pattern 2: Temperature is greater than the high-temperature alarming threshold on [STRING] sensor [STRING] [USHOT]. Pattern 3: Temperature is greater than the high-temperature alarming threshold on [STRING] [STRING] sensor [STRING] [USHOT]. |
|
Variable fields |
Pattern 1: $1: Sensor type. $2: Sensor number. Pattern 2: $1: Slot number. $2: Sensor type. $3: Sensor number. Pattern 3: $1: Chassis number. $2: Slot number. $3: Sensor type. $4: Sensor number. |
|
Severity level |
4 |
|
Example |
DEV/4/TEMPERATURE_ALARM: Temperature is greater than the high-temperature alarming threshold on slot 1 sensor inflow 1. |
|
Explanation |
A sensor's temperature exceeded the high-temperature alarming threshold. The ambient temperature was too high or the fan tray was not operating correctly. |
|
Recommended action |
1. Verify that the ambient temperature is normal and the ventilation system is operating correctly. 2. Use the display fan command to verify that the fan trays are in position and operating correctly. If a fan tray is missing, install the fan tray. If a fan tray does not operate correctly, replace it. |
TEMPERATURE_ALARM_CLEAR
|
Message text |
Temperature alarm cleared. (PhysicalIndex=<[UINT]>, PhysicalName=<[STRING]>, RelativeResource=<[STRING]>, ErrorCode=<[UINT]>, Reason=<[STRING]> , ThresholdType=<[STRING]>, ThresholdValue=<[STRING]>, CurrentValue=<[STRING]>) |
|
Variable fields |
$1: Entity index. $2: Entity name. $3: Fault location information. $4: Fault code. $5: Fault reason description. $6: Threshold type. $7: Threshold value. $8: Current value. |
|
Severity level |
2 |
|
Example |
DEV/2/TEMPERATURE_ALARM_CLEAR: Temperature alarm cleared. (PhysicalIndex=4011, PhysicalName=Temperature Sensor 1 on Board 0, RelativeResource=0/0, ErrorCode=433009, Reason=Board temperature restored, ThresholdType=LowAlarm, ThresholdValue=7, CurrentValue=31.) |
|
Explanation |
A temperature alarm was cleared. |
|
Recommended action |
No action is required. |
TEMPERATURE_ALARM_OCCUR
|
Message text |
Temperature alarm occurred. (PhysicalIndex=<[UINT]>, PhysicalName=<[STRING]>, RelativeResource=<[STRING]>, ErrorCode=<[UINT]>, Reason=<[STRING]> , ThresholdType=<[STRING]>, ThresholdValue=<[STRING]>, CurrentValue=<[STRING]>) |
|
Variable fields |
$1: Entity index. $2: Entity name. $3: Fault location information. $4: Fault code. $5: Fault reason description. $6: Threshold type. $7: Threshold value. $8: Current value. |
|
Severity level |
2 |
|
Example |
DEV/2/TEMPERATURE_ALARM_OCCUR: Temperature alarm occurred. (PhysicalIndex=4011, PhysicalName=Temperature Sensor 1 on Board 0, RelativeResource=0/0, ErrorCode=433009, Reason=Board temperature out of range, ThresholdType=LowAlarm, ThresholdValue=7, CurrentValue=3.) |
|
Explanation |
A temperature alarm occurred. |
|
Recommended action |
Make sure the ambient temperature is normal. |
TEMPERATURE_LOW
|
Message text |
Pattern 1: Temperature is less than the low-temperature threshold on sensor [STRING] [INT32]. Pattern 2: Temperature is less than the low-temperature threshold on [STRING] sensor [STRING] [INT32]. Pattern 3: Temperature is less than the low-temperature threshold on [STRING] [STRING] sensor [STRING] [INT32]. |
|
Variable fields |
Pattern 1: $1: Sensor type. $2: Sensor number. Pattern 2: $1: Slot number. $2: Sensor type. $3: Sensor number. Pattern 3: $1: Chassis number. $2: Slot number. $3: Sensor type. $4: Sensor number. |
|
Severity level |
4 |
|
Example |
DEV/4/TEMPERATURE_LOW: Temperature is less than the low-temperature threshold on slot 1 sensor inflow 1. |
|
Explanation |
A sensor's temperature fell below the low-temperature threshold. |
|
Recommended action |
Adjust the ambient temperature higher. |
TEMPERATURE_NORMAL
|
Message text |
Pattern 1: Temperature changed to normal on sensor [STRING] [INT32]. Pattern 2: Temperature changed to normal on [STRING] sensor [STRING] [INT32]. Pattern 3: Temperature changed to normal on [STRING] [STRING] sensor [STRING] [INT32]. |
|
Variable fields |
Pattern 1: $1: Sensor type. $2: Sensor number. Pattern 2: $1: Slot number. $2: Sensor type. $3: Sensor number. Pattern 3: $1: Chassis number. $2: Slot number. $3: Sensor type. $4: Sensor number. |
|
Severity level |
4 |
|
Example |
DEV/4/TEMPERATURE_NORMAL: Temperature changed to normal on slot 1 sensor inflow 1. |
|
Explanation |
A sensor's temperature was normal (between the low-temperature threshold and the high-temperature warning threshold). |
|
Recommended action |
No action is required. |
TEMPERATURE_SHUTDOWN
|
Message text |
Pattern 1: Temperature is greater than the high-temperature shutdown threshold on sensor [STRING] [INT32]. The slot will be powered off automatically. Pattern 2: Temperature is greater than the high-temperature shutdown threshold on [STRING] sensor [STRING] [INT32]. The slot will be powered off automatically. Pattern 3: Temperature is greater than the high-temperature shutdown threshold on [STRING] [STRING] sensor [STRING] [INT32]. The slot will be powered off automatically. |
|
Variable fields |
Pattern 1: $1: Sensor type. $2: Sensor number. Pattern 2: $1: Slot number. $2: Sensor type. $3: Sensor number. Pattern 3: $1: Chassis number. $2: Slot number. $3: Sensor type. $4: Sensor number. |
|
Severity level |
2 |
|
Example |
DEV/2/TEMPERATURE_SHUTDOWN: Temperature is greater than the high-temperature shutdown threshold on slot 1 sensor inflow 1. The slot will be powered off automatically. |
|
Explanation |
A sensor's temperature exceeded the high-temperature shutdown threshold. The ambient temperature was too high or the fan tray was not operating correctly. |
|
Recommended action |
1. Verify that the ambient temperature is normal and the ventilation system is operating correctly. 2. Use the display fan command to verify that the fan trays are in position and operating correctly. If a fan tray is missing, install the fan tray. If a fan tray does not operate correctly, replace it. |
TEMPERATURE_WARNING
|
Message text |
Pattern 1: Temperature is greater than the high-temperature warning threshold on sensor [STRING] [INT32]. Pattern 2: Temperature is greater than the high-temperature warning threshold on [STRING] sensor [STRING] [INT32]. Pattern 3: Temperature is greater than the high-temperature warning threshold on [STRING] [STRING] sensor [STRING] [INT32]. |
|
Variable fields |
Pattern 1: $1: Sensor type. $2: Sensor number. Pattern 2: $1: Slot number. $2: Sensor type. $3: Sensor number. Pattern 3: $1: Chassis number. $2: Slot number. $3: Sensor type. $4: Sensor number. |
|
Severity level |
4 |
|
Example |
DEV/4/TEMPERATURE_WARNING: Temperature is greater than the high-temperature warning threshold on slot 1 sensor inflow 1. |
|
Explanation |
A sensor's temperature exceeded the high-temperature warning threshold. The ambient temperature was too high or the fan tray was not operating correctly. |
|
Recommended action |
1. Verify that the ambient temperature is normal and the ventilation system is operating correctly. 2. Use the display fan command to verify that the fan trays are in position and operating correctly. If a fan tray is missing, install the fan tray. If a fan tray does not operate correctly, replace it. |
TIMER_CREATE_FAILED_FIRST
|
Message text |
The process with PID [UINT] failed to create a timer. Reason for the failure:[STRING]. |
|
Variable fields |
$1: PID of the process. $2: Reason for the first timer creation failure. The value is "Maximum number of timers already reached." |
|
Severity level |
4 |
|
Example |
DEV/4/TIMER_CREATE_FAILED_FIRST: The process with PID 70 failed to create a timer. Reason for the failure: Maximum number of timers already reached. |
|
Explanation |
The system outputs this message when a process fails to create a timer for the first time. The system uses the following mechanism to avoid frequent output of messages that report timer creation failures: · The system outputs a TIMER_CREATE_FAILED_FIRST message when a process fails to create a timer for the first time. · If a timer creation failure occurs again 15 minutes after the first failure, the system outputs a TIMER_CREATE_FAILED_MORE message. · The TIMER_CREATE_FAILED_MORE message records last time when the timer creation failure message was generated, and the number of timer creation failures between the last and current messages that report timer creation failures. The system does not generate log messages about timer creation failures that occurred within the 15 minutes. |
|
Recommended action |
1. Restart the device to recover the service module corresponding to the process. 2. If the issue persists, contact H3C Support. |
TIMER_CREATE_FAILED_MORE
|
Message text |
The process with PID [UINT] failed to create a timer:[UINT] consecutive failures since [STRING].Reason for the failure:[STRING]. |
|
Variable fields |
$1: PID of the process. $2: Number of timer creation failures between the last and current messages that report time creation failures. $3: Last time when the creation failure log message was generated. $4: Reason for this timer creation failure. The value is "Maximum number of timers already reached." |
|
Severity level |
4 |
|
Example |
DEV/4/TIMER_CREATE_FAILED_MORE: The process with PID 70 failed to create a timer:2 consecutive failures since 2019/11/21 16:00:00.Reason for the failure: Maximum number of timers already reached. |
|
Explanation |
The system outputs this message when a process fails to create a timer again 15 minutes after the first-time creation failure. The system uses the following mechanism to avoid frequent output of messages that report timer creation failures: · The system outputs a TIMER_CREATE_FAILED_FIRST message when a process fails to create a timer for the first time. · If a timer creation failure occurs again 15 minutes after the first failure, the system outputs a TIMER_CREATE_FAILED_MORE message. · The TIMER_CREATE_FAILED_MORE message records last time when the timer creation failure message was generated, and the number of timer creation failures between the last and current messages that report timer creation failures. The system does not generate log messages about timer creation failures that occurred within the 15 minutes. |
|
Recommended action |
1. Restart the device to recover the service module corresponding to the process. 2. If the issue persists, contact H3C Support. |
VCHK_VERSION_INCOMPATIBLE
|
Message text |
Software version of [STRING] is incompatible with that of the MPU. |
|
Variable fields |
$1: Chassis number and slot number or slot number. |
|
Severity level |
1 |
|
Example |
DEV/1/VCHK_VERSION_INCOMPATIBLE: Software version of slot 1 is incompatible with that of the MPU. |
|
Explanation |
A PEX that was starting up detected that its software version is incompatible with the parent device's software version. |
|
Recommended action |
Specify a set of startup software images for the PEX. Make sure the images are compatible with the parent device's software images. |
VOLTAGE_ALARM_CLEAR
|
Message text |
Voltage alarm cleared. (PhysicalIndex=<[UINT]>, PhysicalName=<[STRING]>, RelativeResource=<[STRING]>, ErrorCode=<[UINT]>, Reason=<[STRING]>) |
|
Variable fields |
$1: Entity index. $2: Entity name. $3: Fault location information. $4: Fault code. $5: Fault reason description. $6: Threshold type. $7: Threshold value. $8: Current value. |
|
Severity level |
2 |
|
Example |
DEV/2/VOLTAGE_ALARM_CLEAR: Voltage alarm cleared. (PhysicalIndex=199, PhysicalName=Voltage 2, RelativeResource=0, ErrorCode=420003, Reason=Voltage fell below the high output voltage warning threshold. ) |
|
Explanation |
A voltage alarm was cleared. |
|
Recommended action |
No action is required. |
VOLTAGE_ALARM_OCCUR
|
Message text |
Voltage alarm occurred. (PhysicalIndex=<[UINT]>, PhysicalName=<[STRING]>, RelativeResource=<[STRING]>, ErrorCode=<[UINT]>, Reason=<[STRING]> , ThresholdType=<[STRING]>, ThresholdValue=<[STRING]>, CurrentValue=<[STRING]>) |
|
Variable fields |
$1: Entity index. $2: Entity name. $3: Fault location information. $4: Fault code. $5: Fault reason description. $6: Threshold type. $7: Threshold value. $8: Current value. |
|
Severity level |
2 |
|
Example |
DEV/2/VOLTAGE_ALARM_OCCUR: Voltage alarm occurred. (PhysicalIndex=4043, PhysicalName=Voltage Sensor 0 on Board 0, RelativeResource=0/0, ErrorCode=420005, Reason=Voltage exceeded the high output voltage shutdown threshold., ThresholdType=LowAlarm, ThresholdValue=1031, CurrentValue=0.) |
|
Explanation |
A voltage alarm occurred. |
|
Recommended action |
Contact H3C Support. |
VOLTAGE_FATALALARM_CLEAR
|
Message text |
Voltage fatal alarm cleared. (PhysicalIndex=<[UINT]>, PhysicalName=<[STRING]>, RelativeResource=<[STRING]>, ErrorCode=<[UINT]>, Reason=<[STRING]> , ThresholdType=<[STRING]>, ThresholdValue=<[STRING]>, CurrentValue=<[STRING]>) |
|
Variable fields |
$1: Entity index. $2: Entity name. $3: Fault location information. $4: Fault code. $5: Fault reason description. $6: Threshold type. $7: Threshold value in units. $8: Current value in units. |
|
Severity level |
1 |
|
Example |
DEV/1/VOLTAGE_FATALALARM_CLEAR: Voltage fatal alarm cleared. (PhysicalIndex=5683, PhysicalName=Voltage Sensor 2 on Board 14, RelativeResource=0/14, ErrorCode=420001, Reason= Board powered up, ThresholdType=HighAlarm, ThresholdValue= INVALID, CurrentValue= INVALID) |
|
Explanation |
A fatal voltage alarm was cleared. |
|
Recommended action |
No action is required. |
VOLTAGE_FATALALARM_OCCUR
|
Message text |
Voltage fatal alarm occurred. (PhysicalIndex=<[UINT]>, PhysicalName=<[STRING]>, RelativeResource=<[STRING]>, ErrorCode=<[UINT]>, Reason=<[STRING]> , ThresholdType=<[STRING]>, ThresholdValue=<[STRING]>, CurrentValue=<[STRING]>) |
|
Variable fields |
$1: Entity index. $2: Entity name. $3: Fault location information. $4: Fault code. $5: Fault reason description. $6: Threshold type. $7: Threshold value in units. $8: Current value in units. |
|
Severity level |
1 |
|
Example |
DEV/1/VOLTAGE_FATALALARM_OCCUR: Voltage fatal alarm occurred. (PhysicalIndex=5683, PhysicalName=Voltage Sensor 2 on Board 14, RelativeResource=0/14, ErrorCode=420001, Reason=Board failed to power up, ThresholdType=HighAlarm, ThresholdValue=INVALID, CurrentValue= INVALID) |
|
Explanation |
A fatal voltage alarm occurred. |
|
Recommended action |
1. Execute the display voltage command to verify that the power provided by the power supplies meets the device requirements. 2. If the issue persists, contact H3C Support. |
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 |
|
|
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. |
DHCPSP4_UNTRUSTED_SERVER
|
Message text |
Detected reply packet from untrusted server. Server info: IPaddress = [IPADDR], MACaddress = [MAC], Interface = [STRING]. |
|
Variable fields |
$1: IP address of the untrusted DHCP server. $2: MAC address of the untrusted DHCP server. $3: Name of the interface that connects to the untrusted DHCP server. |
|
Severity level |
4 |
|
Example |
DHCPSP4/4/DHCPSP4_UNTRUSTED_SERVER: Detected reply packet from untrusted server. Server Info: IPaddress = 192.168.1.1, MACaddress = 78a0-7aa4-0307, Interface = GigabitEthernet1/0/1. |
|
Explanation |
This message is sent when the DHCP snooping device detects and drops a DHCP reply from an untrsusted DHCP server. |
|
Recommended action |
Locate the untrusted DHCP server according to the IP address and MAC address information, and isolate the server if necessary. |
DHCPSP4_DROP_PACKET
|
Message text |
DHCP snooping dropped a packet: Message type = [TYPE] Client hardware address = [MAC] Server ID = [IPADDR] Client address = [IPADDR] Drop reason: [STRING] |
|
Variable fields |
$2: MAC address of the DHCP client. $3: IP address of the DHCP server. $4: IP address of the DHCP client. $5: Reason why the DHCP packet is dropped. ¡ The sending and receiving interfaces are not in the same VLAN. ¡ The DHCP packet failed to pass the MAC address check. ¡ The DHCP packet failed to pass the DHCP-REQUEST check. ¡ The DHCP packet failed to pass the giaddr address check. |
|
Severity level |
5 |
|
Example |
DHCPSP4/5/DHCPSP4_DROP_PACKET: DHCP snooping dropped a packet: Message type = DHCPDISCOVER Client hardware address = 7ec9-5ce2-1600 Server ID = 0.0.0.0 Client address = 0.0.0.0 Drop reason: The DHCP packet failed to pass the giaddr address check. |
|
This message is sent when the number of invalid DHCP packets received by the DHCP snooping device reaches or exceeds the alarm threshold. |
|
|
Recommended action |
Figure out the reason why the client failed to obtain an IP address through DHCP and address the issue according to the IP address and MAC address information on the log. |
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. |
DHCPSP6_DROP_PACKET
|
Message text |
DHCPv6 snooping dropped a packet: Incoming interface = [STRING] Message type = [TYPE] Client hardware address = [MAC] Drop reason: [STRING] |
|
Variable fields |
$1: Interface that received the DHCPv6 packet. $2: DHCPv6 packet type. $3: MAC address of the DHCPv6 client. $4: Reason why the DHCPv6 packet is dropped. ¡ The DHCPv6 packet failed to pass the source address check. ¡ The DHCPv6 packet failed to pass the DHCPv6-REQUEST check. ¡ The DHCPv6 packet failed to pass the RELAY-FORW check. |
|
Severity level |
5 |
|
Example |
DHCPSP6/5/DHCPSP6_DROP_PACKET: DHCPv6 snooping drop a packet: Incoming interface = GigabitEthernet2/0/1 Message type = SOLICIT Client hardware address = 7ec9-5ce2-1600 Drop reason: The DHCPv6 packet failed to pass the RELAY-FORW check. |
|
Explanation |
This message is sent when the number of invalid DHCPv6 packets received by the DHCPv6 snooping device reaches or exceeds the alarm threshold. |
|
Recommended action |
Figure out the reason why the client failed to obtain an IPv6 address through DHCP and address the issue according to the interface and MAC address information on the log. |
DIAG messages
This section contains diagnostic messages.
CORE_EXCEED_THRESHOLD
|
Message text |
Usage of CPU [INT] core [INT] exceeded the threshold ([string]). |
|
Variable fields |
$1: CPU number. $2: CPU core number. $3: Severe usage alarm threshold. |
|
Severity level |
3 |
|
Example |
DIAG/3/CORE_EXCEED_THRESHOLD: Usage of CPU 0 core 2 exceeded the threshold (90%). |
|
Explanation |
The usage of the specified CPU core exceeded the severe usage alarm threshold. The CPU core usage was in severe alarm state. |
|
Recommended action |
1. Execute the display process cpu and monitor thread commands to display CPU usage information about all processes. 2. Contact the technical support. |
CORE_MINOR_RECOVERY
|
Message text |
Core usage minor alarm CPU [INT] core [INT] removed. |
|
Variable fields |
$1: CPU number. $2: CPU core number. |
|
Severity level |
5 |
|
Example |
DIAG/5/CORE_MINOR_RECOVERY: Core usage alarm CPU 0 core 1 removed. |
|
Explanation |
The usage of the specified CPU core dropped to or below the minor usage alarm threshold. The minor alarm was removed. |
|
Recommended action |
No action is required. |
CORE_MINOR_THRESHOLD
|
Message text |
Usage of CPU [INT] core [INT] exceeded the threshold ([string]). |
|
Variable fields |
$1: CPU number. $2: CPU core number. $3: Minor usage alarm threshold. |
|
Severity level |
4 |
|
Example |
DIAG/4/CORE_MINOR_THRESHOLD: Usage of CPU 0 core 2 exceeded the threshold (80%). |
|
Explanation |
The usage of the specified CPU core was greater than the minor usage alarm threshold. The CPU core usage was in minor alarm state. |
|
Recommended action |
1. Execute the display process cpu and monitor thread commands to display CPU usage information about all processes. 2. Contact the technical support. |
CORE_RECOVERY
|
Message text |
Core usage alarm CPU [INT] core [INT] removed. |
|
Variable fields |
$1: CPU number. $2: CPU core number. |
|
Severity level |
3 |
|
Example |
DIAG/3/CORE_RECOVERY: Core usage alarm CPU 0 core 1 removed. |
|
Explanation |
The usage of the specified CPU core dropped to or below the severe usage alarm threshold. The severe alarm was removed. |
|
Recommended action |
No action is required. |
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 is in severe alarm state. CPU usage: [string] in last 5 seconds. CPU usage thresholds: Minor: [string] Severe: [string] Process info: JID PID PRI State FDs HH:MM:SS CPU Name [INT] [INT] [INT] [string] [INT] [string] [string] [string] … Core states: ID Idle User Kernel Interrupt Busy [string] [string] [string] [string] [string] [string] |
|
Variable fields |
$1: CPU usage during the last five seconds. $2: Minor CPU usage alarm threshold. $3: Severe CPU usage alarm threshold. $4 to $11: Information about the top 5 processes with the highest CPU usage when the most recent CPU usage threshold crossing event occurred: · $4: Job ID, which uniquely identifies a process. This ID can survive a process restart. · $5: Process ID. · $6: Process priority. A process with a higher priority is scheduled the first. · $7: State of the process. Options include: ¡ R—running. ¡ S—Sleeping. ¡ T—Traced or stopped. ¡ D—Uninterruptible sleep. ¡ Z—Zombie. · $8: Number of FDs used by the process. · $9: Uptime of the process since the most recent startup. This field displays the uptime only in hours when the uptime is equal to or longer than 100 hours. · $10: CPU used by the process to the total CPU capacity of the device (containerization not supported). · $10: CPU used by the process to the total CPU capacity of the container (containerization supported). · $11: Name of the process. $12 to $11: Information about the CPU cores when the most recent CPU usage threshold crossing event occurred: · $12: ID of the CPU core. · $13: Total idle rate of the CPU core. · $14: CPU core usage of the user process. · $15: CPU core usage of the kernel. · $16: CPU core usage of interrupts. · $17: Total CPU core usage. |
|
Severity level |
3 |
|
Example |
DIAG/3/CPU_THRESHOLD: CPU usage is in severe alarm state. CPU usage: 100% in last 5 seconds. CPU usage thresholds: Minor: 79% Severe: 99% Process info: JID PID PRI State FDs HH:MM:SS CPU Name 981 981 120 R 2890 803h 92.90% forward 19169 3464131 120 S 234 00:35:4 6.33% bgpd 3526894 3526894 135 R 56 00:00:0 0.21% pkg_update 1555 1555 120 R 1002 00:41:0 0.06% diagd 17161 17161 120 S 180 00:49:2 0.10% isisd Core states: ID Idle User Kernel Interrupt Busy CPU1 0.01% 99.88% 0.10% 0.01% 99.99% CPU2 0.01% 99.89% 0.10% 0.00% 99.99% CPU3 0.01% 99.88% 0.10% 0.01% 99.99% CPU4 0.01% 99.88% 0.10% 0.01% 999.9% CPU5 0.01% 99.88% 0.11% 0.00% 99.99% |
|
Explanation |
The CPU usage rose above the severe alarm threshold and entered severe alarm state. In severe alarm state, the device sends this message regularly until the alarm is removed. |
|
Recommended action |
Use the display current-configuration | include "monitor cpu-usage" command to display the CPU alarm thresholds. If the settings are not appropriate, use the monitor cpu-usage command to change the settings. |
DIAG_FD_UPLIMIT_REACHED
|
Message text |
FD number upper limit already reached: Process name=[STRING], PID=[INTEGER]. |
|
Variable fields |
$1: Name of a process. $2: ID of the process. |
|
Severity level |
4 |
|
Example |
DIAG/4/DIAG_FD_UPLIMIT_REACHED: FD number upper limit already reached: Process name=snmpd, PID=244. |
|
Explanation |
The maximum number of file descriptors that a process can use has been reached. |
|
Recommended action |
No action is required. |
DIAG_FD_UPLIMIT_TO_REACH
|
Message text |
Number of FDs is about to reach the upper limit: Process name=[STRING], PID=[INTEGER]. |
|
Variable fields |
$1: Name of a process. $2: ID of the process. |
|
Severity level |
4 |
|
Example |
DIAG/4/DIAG_FD_UPLIMIT_TO_REACH: Number of FDs is about to reach the upper limit. Process name=snmpd, PID=244. |
|
Explanation |
The maximum number of file descriptors that a process can use was about to be reached. |
|
Recommended action |
No action is required. |
DIAG_STORAGE_BELOW_THRESHOLD
|
Message text |
The usage of [STRING] ([UINT32]%) was below or equal to the threshold of [UINT32]%. |
|
Variable fields |
$1: Name of the storage medium. $2: Disk usage of the storage medium. $3: Disk usage threshold for the storage medium. |
|
Severity level |
1 |
|
Example |
DIAG/1/DIAG_STORAGE_BELOW_THRESHOLD: The usage of flash (90%) was below or equal to the threshold of 95%. |
|
Explanation |
This message indicates that the storage medium has sufficient space, because the disk usage is not higher than the threshold. |
|
Recommended action |
No action is required. |
DIAG_STORAGE_EXCEED_THRESHOLD
|
Message text |
The usage of [STRING] ([UINT32]%) exceeded the threshold of [UINT32]%. |
|
Variable fields |
$1: Name of the storage medium. $2: Disk usage of the storage medium. $3: Disk usage threshold for the storage medium. |
|
Severity level |
1 |
|
Example |
DIAG/1/DIAG_STORAGE_EXCEED_THRESHOLD: The usage of flash (96%) exceeded the threshold of 95%. |
|
Explanation |
This message indicates that the storage medium does not have sufficient space, because the disk usage is higher than the threshold. |
|
Recommended action |
For files not in use, for example, log files and history software packages, execute the delete /unreserved command to delete the files or back up the files and then execute the delete /unreserved command to delete the files. |
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. |
DIM engine messages
This section contains DPI engine messages.
DIM_SIGNATURE_WARNING
|
Message text |
Failed to write signature file to storage, because there is not enough free space. |
|
Severity level |
4 |
|
Example |
DPI/4/DIM_SIGNATURE_WARNING: Failed to write signature file to storage, because there is not enough free space. |
|
Explanation |
This message is generated when a signature library fails to be updated or rolled back due to insufficient storage space in the flash memory. |
|
Recommended action |
Release some storage space (for example, in the flash memory) before updating or rolling back a signature library. |
DIM_ACTIVE_WARNING
|
Message text |
The device fails to activate the DPI engine due to insufficient memory space after the free-memory normal state threshold is reached. DPI services were no longer in effect. |
|
Severity level |
4 |
|
Example |
DPI/4/DIM_ACTIVE_WARNING: The device fails to activate the DPI engine due to insufficient memory space after the free-memory normal state threshold is reached. DPI services were no longer in effect. |
|
Explanation |
This message is generated when the device fails to activate the DPI engine due to insufficient memory space. |
|
Recommended action |
Release some storage space and then execute the inspect activate command. |
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. |
DOT1X messages
This section contains 802.1X messages.
DOT1X_CONFIG_NOTSUPPORT
|
Message text |
802.1X is not supported on interface [STRING]. |
|
Variable fields |
$1: Interface type and number. |
|
Severity level |
3 |
|
Example |
DOT1X/3/DOT1X_CONFIG_NOTSUPPORT: 802.1X is not supported on interface GigabitEthernet1/0/1. |
|
Explanation |
The interface does not support 802.1X configuration. |
|
Recommended action |
No action is required. |
DOT1X_LOGIN_FAILURE
|
Message text |
-IfName=[STRING]-MACAddr=[STRING]-VLANID=[STRING]-Username=[STRING]-ErrCode=[STRING]; User failed 802.1X authentication. Reason: [STRING]. |
|
Variable fields |
$1: Interface type and number. $2: MAC address. $3: VLAN ID. $4: Username. $5: Error code. $6: Failure cause: · MAC address authorization failed. · VLAN authorization failed. · VSI authorization failed. · ACL authorization failed. · User profile authorization failed. · URL authorization failed. · Microsegment authorization failed. |
|
Severity level |
6 |
|
Example |
DOT1X/6/DOT1X_LOGIN_FAILURE: -IfName=GigabitEthernet1/0/1-MACAddr=0000-0001-0020-VLANID=2-Username=aaa-ErrCode=5; User failed 802.1X authentication. Reason: ACL authorization failed. |
|
Explanation |
The user failed 802.1X authentication for a specific reason. |
|
Recommended action |
Locate the failure cause and handle the issue according to the failure cause. |
DOT1X_LOGIN_SUCC
|
Message text |
-IfName=[STRING]-MACAddr=[STRING]-AccessVLANID=[STRING]-AuthorizationVLANID=[STRING]-Username=[STRING]; User passed 802.1X authentication and came online. |
|
Variable fields |
$1: Interface type and number. $2: MAC address. $3: ID of the access VLAN. $4: ID of the authorization VLAN. $5: Username. |
|
Severity level |
6 |
|
Example |
DOT1X/6/DOT1X_LOGIN_SUCC:-IfName=GigabitEthernet1/0/4-MACAddr=0010-8400-22b9-AccessVLANID=444-AuthorizationVLANID=444-Username=aaa; User passed 802.1X authentication and came online. |
|
Explanation |
The user passed 802.1X authentication. |
|
Recommended action |
No action is required. |
DOT1X_LOGIN_SUCC (in open mode)
|
Message text |
-IfName=[STRING]-MACAddr=[STRING]-VLANID=[STRING]-Username=[STRING]; The user that failed 802.1X authentication passed open authentication and came online. |
|
Variable fields |
$1: Interface type and number. $2: MAC address. $3: VLAN ID. $4: Username. |
|
Severity level |
6 |
|
Example |
DOT1X/6/DOT1X_LOGIN_SUCC:-IfName=GigabitEthernet1/0/4-MACAddr=0010-8400-22b9-VLANID=444-Username=00-10-84-00-22-b9; The user that failed 802.1X authentication passed open authentication and came online. |
|
Explanation |
A user failed 802.1X authentication but passed open authentication. |
|
Recommended action |
No action is required. |
DOT1X_LOGOFF
|
Message text |
-IfName=[STRING]-MACAddr=[STRING]-VLANID=[STRING]-Username=[STRING]; 802.1X user was logged off. |
|
Variable fields |
$1: Interface type and number. $2: MAC address. $3: VLAN ID. $4: Username. |
|
Severity level |
6 |
|
Example |
DOT1X/6/DOT1X_LOGOFF:-IfName=GigabitEthernet1/0/4-MACAddr=0010-8400-22b9-VLANID=444-Username=aaa; 802.1X user was logged off. |
|
Explanation |
The 802.1X user was logged off as requested. |
|
Recommended action |
No action is required. |
DOT1X_LOGOFF (in open mode)
|
Message text |
-IfName=[STRING]-MACAddr=[STRING]-VLANID=[STRING]-Username=[STRING]; 802.1X open user was logged off. |
|
Variable fields |
$1: Interface type and number. $2: MAC address. $3: VLAN ID. $4: Username. |
|
Severity level |
6 |
|
Example |
DOT1X/6/DOT1X_LOGOFF:-IfName=GigabitEthernet1/0/4-MACAddr=0010-8400-22b9-VLANID=444-Username=aaa; 802.1X open user was logged off. |
|
Explanation |
An 802.1X open user was logged off as requested. |
|
Recommended action |
No action is required. |
DOT1X_LOGOFF_ABNORMAL
|
Message text |
-IfName=[STRING]-MACAddr=[STRING]-VLANID=[STRING]-Username=[STRING]-ErrCode=[STRING]; 802.1X user was logged off abnormally. |
|
Variable fields |
$1: Interface type and number. $2: MAC address. $3: VLAN ID. $4: Username. $5: Error code. |
|
Severity level |
6 |
|
Example |
DOT1X/6/DOT1X_LOGOFF_ABNORMAL:-IfName=GigabitEthernet1/0/4-MACAddr=0010-8400-22b9-VLANID=444-Username=aaa-ErrCode=11; 802.1X user was logged off abnormally. |
|
Explanation |
The 802.1X user was logged off abnormally. |
|
Recommended action |
Locate the logoff cause and remove the issue. |
DOT1X_LOGOFF_ABNORMAL (in open mode)
|
Message text |
-IfName=[STRING]-MACAddr=[STRING]-VLANID=[STRING]-Username=[STRING]-ErrCode=[STRING]; 802.1X open user was logged off abnormally. |
|
Variable fields |
$1: Interface type and number. $2: MAC address. $3: VLAN ID. $4: Username. $5: Error code. |
|
Severity level |
6 |
|
Example |
DOT1X/6/DOT1X_LOGOFF_ABNORMAL:-IfName=GigabitEthernet1/0/4-MACAddr=0010-8400-22b9-VLANID=444-Username=aaa-ErrCode=11; 802.1X open user was logged off abnormally. |
|
Explanation |
An 802.1X open user was logged off abnormally. |
|
Recommended action |
Locate the logoff cause and remove the issue. |
DOT1X_MACBINDING_EXIST
|
Message text |
-IfName=[STRING]-MACAddr=[STRING]-VLANID=[STRING]-Username=[STRING]; MAC address was already bound to interface [STRING]. |
|
Variable fields |
$1: Type and number of the access interface. $2: MAC address. $3: VLAN ID. $4: Username. $5: Type and number of the interface to which the MAC address was bound. |
|
Severity level |
6 |
|
Example |
DOT1X/6/DOT1X_MACBINDING_EXIST: -IfName=GigabitEthernet1/0/1-MACAddr=0000-0001-0020-VLANID=2-Username=aaa; MAC address was already bound to interface GigabitEthernet1/0/3. |
|
Explanation |
The user failed to come online on an interface because its MAC address was already bound to another interface. |
|
Recommended action |
Delete the related 802.1X MAC address binding entry from the bound interface. |
DOT1X_NOTENOUGH_EADFREEIP_RES
|
Message text |
Failed to assign a rule for free IP [IPADDR] on interface [STRING] due to lack of ACL resources. |
|
Variable fields |
$1: Free IP. $2: Interface type and number. |
|
Severity level |
3 |
|
Example |
DOT1X/3/DOT1X_NOTENOUGH_EADFREEIP_RES: Failed to assign a rule for free IP 1.1.1.0 on interface Ethernet3/1/2 due to lack of ACL resources. |
|
Explanation |
The device failed to assign an ACL rule to permit a free IP on an interface because of ACL resource shortage. |
|
Recommended action |
No action is required. |
DOT1X_NOTENOUGH_EADFREEMSEG_RES
|
Message text |
Failed to assign a rule for free microsegment [microsegment-id] on interface [STRING] due to lack of ACL resources. |
|
Variable fields |
$1: Free microsegment ID. $2: Interface type and number. |
|
Severity level |
3 |
|
Example |
DOT1X/3/DOT1X_NOTENOUGH_EADFREEMSEG_RES: Failed to assign a rule for free microsegment 1 on interface Ethernet3/1/2 due to lack of ACL resources. |
|
Explanation |
The device failed to assign an ACL rule to permit a free microsegment on an interface because of ACL resource shortage. |
|
Recommended action |
Disable 802.1X on the interface, and then re-enable 802.1X. |
DOT1X_NOTENOUGH_EADFREERULE_RES
|
Message text |
Failed to assign a rule for permitting DHCP and DNS packets on interface [STRING] due to lack of ACL resources. |
|
Variable fields |
$1: Interface type and number. |
|
Severity level |
3 |
|
Example |
DOT1X/3/DOT1X_NOTENOUGH_EADFREERULE_RES: Failed to assign a rule for permitting DHCP and DNS packets on interface Ethernet3/1/2 due to lack of ACL resources. |
|
Explanation |
The device failed to assign an ACL rule to permit DHCP and DNS packets on an interface because of ACL resource shortage. |
|
Recommended action |
No action is required. |
DOT1X_NOTENOUGH_EADMACREDIR_RES
|
Message text |
Failed to assign a rule for redirecting HTTP packets with source MAC address [MAC] on interface [STRING]. |
|
Variable fields |
$1: Source MAC address of HTTP packets. $2: Interface type and number. |
|
Severity level |
3 |
|
Example |
DOT1X/3/DOT1X_NOTENOUGH_EADMACREDIR_RES: Failed to assign a rule for redirecting HTTP packets with source MAC address 00e0-fc00-5915 on interface Ethernet3/1/2. |
|
Explanation |
The device failed to redirect HTTP packet with the designated source MAC on an interface because of ACL resource shortage. |
|
Recommended action |
No action is required. |
DOT1X_NOTENOUGH_EADPORTREDIR_RES
|
Message text |
Failed to assign a rule for redirecting HTTP packets on interface [STRING] due to lack of ACL resources. |
|
Variable fields |
$1: Interface type and number. |
|
Severity level |
3 |
|
Example |
DOT1X/3/DOT1X_NOTENOUGH_EADPORTREDIR_RES: Failed to assign a rule for redirecting HTTP packets on interface Ethernet3/1/2 due to lack of ACL resources. |
|
Explanation |
The device failed to assign an ACL rule to redirect HTTP packets on an interface because of ACL resource shortage. |
|
Recommended action |
No action is required. |
DOT1X_NOTENOUGH_ENABLEDOT1X_RES
|
Message text |
Failed to enable 802.1X on interface [STRING] due to lack of ACL resources. |
|
Variable fields |
$1: Interface type and number. |
|
Severity level |
3 |
|
Example |
DOT1X/3/DOT1X_NOTENOUGH_ENABLEDOT1X_RES: Failed to enable 802.1X on interface Ethernet3/1/2 due to lack of ACL resources. |
|
Explanation |
Failed to enable 802.1X on an interface because of ACL resource shortage. |
|
Recommended action |
Disable 802.1X on the interface, and then re-enable 802.1X. |
DOT1X_PEXAGG_NOMEMBER_RES
|
Message text |
Failed to enable 802.1X on interface [STRING] because the Layer 2 extended-link aggregate interface does not have member ports. |
|
Variable fields |
$1: Interface type and number. |
|
Severity level |
3 |
|
Example |
DOT1X/3/DOT1X_PEXAGG_NOMEMBER_RES: Failed to enable 802.1X on interface Bridge-Aggregation100 because the Layer 2 extended-link aggregate interface does not have member ports. |
|
Explanation |
Failed to enable 802.1X on a Layer 2 extended-link aggregate interface because the interface does not have member ports. |
|
Recommended action |
Disable 802.1X on the interface, add a member port to the interface, and then re-enable 802.1X. |
DOT1X_SMARTON_FAILURE
|
Message text |
-IfName=[STRING]-MACAddr=[STRING]; User failed SmartOn authentication because [STRING]. |
|
Variable fields |
$1: Interface type and number. $2: MAC address. $3: Cause of failure: · the password was wrong. · the switch ID was wrong. |
|
Severity level |
6 |
|
Example |
DOT1X/6/DOT1X_SMARTON_FAILURE:-IfName=GigabitEthernet1/0/4-MACAddr=0010-8400-22b9; User failed SmartOn authentication because the password was wrong. |
|
Explanation |
SmartOn authentication failed for a specific reason. |
|
Recommended action |
Handle the issue according to the failure cause. |
DOT1X_UNICAST_NOT_EFFECTIVE
|
Message text |
The unicast trigger feature is enabled but is not effective on interface [STRING]. |
|
Variable fields |
$1: Interface type and number. |
|
Severity level |
3 |
|
Example |
DOT1X/3/DOT1X_UNICAST_NOT_EFFECTIVE: The unicast trigger feature is enabled but is not effective on interface Ethernet3/1/2. |
|
Explanation |
The unicast trigger setting does not take effect on an interface, because the interface does not support unicast trigger. |
|
Recommended action |
1. Reconnect the 802.1X clients to another interface that supports the unicast trigger feature. 2. Enable the unicast trigger feature on the new interface. |
DRV messages
This section contains driver messages.
DRV_LIC_MORE_VCPU
|
Message text |
The device has a VCPU license that supports more VCPUs. Please restart the device for the license to take effect. |
|
Variable fields |
N/A |
|
Severity level |
6 |
|
Example |
DRV/6/DRV_LIC_MORE_VCPU: The device has a VCPU license that supports more VCPUs. Please restart the device for the license to take effect. |
|
Explanation |
The device has a vCPU license that supports more vCPUs than the vCPUs on the device. |
|
Recommended action |
To use more vCPUs, restart the device for the vCPU license to take effect. |
DRV_ANOTHER_VALID_VCPU_LIC
|
Message text |
The current VCPU license is invalid. Another valid VCPU license is available on the device. Please restart the device for the valid license to take effect. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
DRV/4/DRV_ANOTHER_VALID_VCPU_LIC: The current VCPU license is invalid. Another valid VCPU license is available on the device. Please restart the device for the valid license to take effect. |
|
Explanation |
The current vCPU license has expired, but the device has another valid vCPU license. |
|
Recommended action |
To avoid data forwarding, restart the device for the vCPU license to take effect. |
DRVPLAT messages
This section contains DRVPLAT messages..
DRVPLAT/4/DrvDebug
|
Message text |
Insufficient TTI resources. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
DRVPLAT/4/DrvDebug: Insufficient TTI resources. |
|
Explanation |
This message is generated when the device does not have enough TTI resources to create a new service loopback group. In this case, the device cannot correctly forward the packets entering a Layer 3 tunnel. |
|
Recommended action |
No action is required. |
DRVPLAT_NO_ENOUGH_RESOURCE
|
Message text |
No enough resources to add l3 ipmc. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
DRVPLAT/4/DRVPLAT_NO_ENOUGH_RESOURCE: No enough resources to add l3 ipmc. |
|
Impact |
The multicast traffic cannot be forwarded. |
|
Cause |
Layer 3 multicast entries failed to be issued because of hardware resource insufficiency. |
|
Recommended action |
Execute the display multicast routing-table command to identify whether the total number of (S, G) entries is within the specifications. Multicast packets beyond the specifications cannot be forwarded. Collect alarm information, log messages, and configuration data, and then contact H3C Support for help. |
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. |
ERPS_PEERLINK_CHECK
|
Message text |
An ERPS ring member port can't be configured as a peer-link interface. |
|
Variable fields |
None. |
|
Severity level |
6 |
|
Example |
ERPS/6/ERPS_PEERLINK_CHECK: An ERPS ring member port can't be configured as a peer-link interface. |
|
Explanation |
This message is generated when you configure an ERPS ring member port as a peer-link interface. |
|
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. |
FIB messages
This section contains FIB messages.
FIB_PREFIX_ENOUGHRESOURCE
|
Message text |
Text 1: Issued the software entry to the driver for IP address [STRING] and mask length [UINT32] on VPN instance [STRING]. Text 2: Issued the software entry to the driver for IP address [STRING] and mask length [UINT32]. |
|
Variable fields |
Text 1: $1: IPv4 or IPv6 address. $2: Mask or prefix length. $3: VPN instance name. Text 2: $1: IPv4 or IPv6 address. $2: Mask or prefix length. |
|
Severity level |
6 |
|
Example |
Text 1: FIB/6/FIB_PREFIX_ENOUGHRESOURCE: Issued the software entry to the driver for IP address 10.1.1.1 and mask length 32 on VPN instance vpn_1. Text 2: FIB/6/FIB_PREFIX_ENOUGHRESOURCE: Issued the software entry to the driver for IP address 10::2 and mask length 128. |
|
Explanation |
The device attempts to re-issue virtual next hop information to hardware if it has failed to issue this information during synchronization of some FIB entries from software to hardware for consistency. This message occurs after the system successfully re-issues virtual next hop information to hardware. You can use one of the following commands to enable FIB entry consistency check and the generation of this log for IPv4 and IPv6: · ip fib consistency-check enable (IPv4). · ipv6 fib consistency-check enable (IPv6). |
|
Recommended action |
No action is required. |
FIB_PREFIX_INCONSISTENT
|
Message text |
Text 1: Inconsistent software and hardware FIB entries for IP address [STRING] and mask length [UINT32] on VPN instance [STRING]. Inconsistent parameters:[STRING]. Text 2: Inconsistent software and hardware FIB entries for IP address [STRING] and mask length [UINT32]. Inconsistent parameters: [STRING]. |
|
Variable fields |
Text 1: $1: IPv4 or IPv6 address. $2: Mask or prefix length. $3: VPN instance name. $4: Inconsistent parameters. Options: · Next hop · MPLS label · Adjacent-table · Micro-segment ID Text 2: $1: IPv4 or IPv6 address. $2: Mask or prefix length. $3: Inconsistent parameters. Options: · Next hop · MPLS label · Adjacent-table · Micro-segment ID |
|
Severity level |
6 |
|
Example |
Text 1: FIB/6/FIB_PREFIX_INCONSISTENT: Inconsistent software and hardware FIB entries for IP address 10.1.1.1 and mask length 32 on VPN instance vpn_1. Inconsistent parameters: next hop and mpls label, adjacent-table and micro-segment ID. Text 2: FIB/6/FIB_PREFIX_INCONSISTENT: Inconsistent software and hardware FIB entries for IP address 10::2 and mask length 128. Inconsistent parameters: next hop and mpls label, adjacent-table and micro-segment ID. |
|
Explanation |
This message occurs when the system detects an inconsistency between the FIB entry in software and FIB entry in hardware for an IP address. You can use the following commands to enable FIB entry consistency check for IPv4 and IPv6: · ip fib consistency-check enable (IPv4). · ipv6 fib consistency-check enable (IPv6). Once the device detects an inconsistency, it will generate this type of log. |
|
Recommended action |
No action is required. The device will update the FIB entry in hardware with the FIB entry in software automatically. |
FIB_PREFIX_NORESOURCE
|
Message text |
Text 1: Not enough hardware resources to issue the software entry to the driver for IP address [STRING] and mask length [UINT32] on VPN instance [STRING]. Text 2: Not enough hardware resources to issue the software entry to the driver for IP address [STRING] and mask length [UINT32]. |
|
Variable fields |
Text 1: $1: IPv4 or IPv6 address. $2: Mask or prefix length. $3: VPN instance name. Text 2: $1: IPv4 or IPv6 address. $2: Mask or prefix length. |
|
Severity level |
4 |
|
Example |
Text 1: FIB/4/FIB_PREFIX_NORESOURCE: Not enough hardware resources to issue the software entry to the driver for IP address 10.1.1.1 and mask length 32 on VPN instance vpn_1. Text 2: FIB/4/FIB_PREFIX_NORESOURCE: Not enough hardware resources to issue the software entry to the driver for IP address 10::2 and mask length 128. |
|
Explanation |
This message occurs when the system fails to update the FIB entry in hardware with the FIB entry in software for an IP address for consistency. You can use the following commands to enable FIB entry consistency check and the generation of this log for IPv4 and IPv6: · ip fib consistency-check enable (IPv4). · ipv6 fib consistency-check enable (IPv6). |
|
Recommended action |
No action is required. The device will update the FIB entry in hardware with the FIB entry in software automatically. |
FIB_VN_ENOUGHRESOURCE
|
Message text |
Text 1: Issued the following [UINT32] software FIB entries to the driver: Entry for IP address [STRING] and mask length [UINT32] on VPN instance [STRING]. Text 2: Issued the following [UINT32] software FIB entries to the driver: Entry for IP address [STRING] and mask length [UINT32]. |
|
Variable fields |
Text 1: $1: Number of resynchronized FIB entries. $2: IPv4 or IPv6 address. $3: Mask or prefix length. $4: VPN instance name. Text 2: $1: Number of resynchronized FIB entries. $2: IPv4 or IPv6 address. $3: Mask or prefix length. |
|
Severity level |
6 |
|
Example |
Text 1: FIB/6/FIB_VN_ENOUGHRESOURCE: Issued the following 1 software FIB entries to the driver: Entry for IP address 10.1.1.1 and mask length 32 on VPN instance vpn_1. Text 2: FIB/6/FIB_VN_ENOUGHRESOURCE: Issued the following 1 software FIB entries to the driver: Entry for IP address 10::2 and mask length 128. |
|
Explanation |
The device attempts to re-issue virtual next hop information to hardware if it has failed to issue this information during synchronization of some FIB entries from software to hardware for consistency. This message occurs after the system successfully re-issues virtual next hop information to hardware. You can use one of the following commands to enable FIB entry consistency check and the generation of this log for IPv4 and IPv6: · ip fib consistency-check enable (IPv4). · ipv6 fib consistency-check enable (IPv6). |
|
Recommended action |
No action is required. |
FIB_VN_INCONSISTENT
|
Message text |
Text 1: Inconsistent software and hardware entries for the following [UINT32] FIB entries. Inconsistent parameters: [STRING]. Entry for IP address [STRING] and mask length [UINT32] on VPN instance [STRING]. Text 2: Inconsistent software and hardware entries for the following [UINT32] FIB entries. Inconsistent parameters: [STRING]. Entry for IP address [STRING] and mask length [UINT32]. |
|
Variable fields |
Text 1: $1: Number of inconsistent FIB entries. $2: Inconsistent parameters. Options: · Next hop · MPLS label · Maximum number of ECMP routes · Output tunnel interface $3: IPv4 or IPv6 address. $4: Mask or prefix length. $5: VPN instance name. Text 2: $1: Number of inconsistent FIB entries. $2: Inconsistent parameters. Options: · Next hop · MPLS label · Maximum number of ECMP routes · Output tunnel interface $3: IPv4 or IPv6 address. $4: Mask or prefix length. |
|
Severity level |
6 |
|
Example |
Text 1: FIB/6/FIB_VN_INCONSISTENT: Inconsistent software and hardware entries for the following 1 FIB entries. Inconsistent parameters: next hop and mpls label. Entry for IP address 10.1.1.1 and mask length 32 on VPN instance vpn_1. Text 2: FIB/6/FIB_VN_INCONSISTENT: Inconsistent software and hardware entries for the following 1 FIB entries. Inconsistent parameters: next hop and mpls label. Entry for IP address 10::2 and mask length 128. |
|
Explanation |
You can use one of the following commands to enable FIB entry consistency check: · ip fib consistency-check enable (IPv4). · ipv6 fib consistency-check enable (IPv6). Once the device detects an inconsistency between virtual nexthop entries in software and in hardware, it will generate this log to inform the user of the inconsistent FIB entries. |
|
Recommended action |
No action is required. The device will update the FIB entry in hardware with the FIB entry in software automatically. |
FIB_VN_NORESOURCE
|
Message text |
Text 1: Not enough hardware resources to issue the following [UINT32] software FIB entries to the driver: Entry for IP address [STRING] and mask length [UINT32] on VPN instance [STRING]. Text 2: Not enough hardware resources to issue the following [UINT32] software FIB entries to the driver: Entry for IP address [STRING] and mask length [UINT32]. |
|
Variable fields |
Text 1: $1: Number of resynchronized FIB entries. $2: IPv4 or IPv6 address. $3: Mask or prefix length. $4: VPN instance name. Text 2: $1: Number of resynchronized FIB entries. $2: IPv4 or IPv6 address. $3: Mask or prefix length. |
|
Severity level |
4 |
|
Example |
Text 1: FIB/4/FIB_VN_NORESOURCE: Not enough hardware resources to issue the following 1 software FIB entries to the driver: Entry for IP address 10.1.1.1 and mask length 32 on VPN instance vpn_1. Text 2: FIB/4/FIB_VN_NORESOURCE: Not enough hardware resources to issue the following 1 software FIB entries to the driver: Entry for IP address 10::2 and mask length 128. |
|
Explanation |
You can use one of the following commands to enable FIB entry consistency check and the generation of this log for IPv4 and IPv6: · ip fib consistency-check enable (IPv4). · ipv6 fib consistency-check enable (IPv6). With FIB entry consistency check enabled, the device will generate this type of log if it fails to issue some software virtual nexthop entries to the hardware due to insufficient hardware resources. This log informs the user of the invalid FIB entries. |
|
Recommended action |
No action is required. The device will update the FIB entry in hardware with the FIB entry in software automatically. |
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. |
FTP messages
This section contains File Transfer Protocol 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 |
|
|
Example |
|
|
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. |
GIR messages
This section contains GIR messages.
GIR_SYSTEM_MODE
|
Message text |
System change to [STRING] mode. |
|
Variable fields |
$1: System mode: normal or maintenance |
|
Severity level |
6 |
|
Example |
GIR/6/GIR_SYSTEM_MODE: System change to normal mode. |
|
Explanation |
The system changed to normal or maintenance mode. |
|
Recommended action |
No action is required. |
GIR_SYSTEM_REVERT
|
Message text |
System will change to normal after [UINT32] minutes. |
|
Variable fields |
$1: Delay for the system to automatically revert to normal mode. |
|
Severity level |
6 |
|
Example |
GIR/6/GIR_SYSTEM_REVERT: System will change to normal after 5 minutes. |
|
Explanation |
The system will automatically revert to normal mode from maintenance mode after a number of minutes. |
|
Recommended action |
No action is required. |
GIR_SYSTEM_MODE_FAILED
|
Message text |
System change to [STRING] mode failed because cmd "[STRING]" failed. |
|
Variable fields |
$1: System mode. $2: Command failing to be issued. |
|
Severity level |
4 |
|
Example |
GIR/4/GIR_SYSTEM_MODE_FAILED: System change to normal mode failed because cmd "isolate enable" failed. |
|
Explanation |
The system failed to change the mode because a command failed to be issued. |
|
Recommended action |
If a service module fails in switchover, use the following methods to identify and remove the issue: · Remove the issue based on the error message. · Compare the snapshots to identify configuration inconsistencies that might have caused the issue. |
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. |
HOTPLUG messages
This section contains interface hot swapping messages.
HOTPLUG_PORT_PLUGIN
|
Message text |
A port is hot pluged in: Port:[STRING], PCI:[STRING]. |
|
Variable fields |
$1: Interface name. $2: Port PCI information. |
|
Severity level |
6 |
|
Example |
HOTPLUG/6/HOTPLUG_PORT_PLUGIN: A port is hot pluged in: Port:GigabitEthernet1/0/1, PCI:08.00.0. |
|
Explanation |
A hot-swapping-in event was detected on a port. |
|
Recommended action |
No action is required. |
HOTPLUG_PORT_PLUGOUT
|
Message text |
A port is hot pluged out: Port:[STRING], PCI:[STRING]. |
|
Variable fields |
$1: Port name. $2: Port PCI information. |
|
Severity level |
6 |
|
Example |
HOTPLUG/6//HOTPLUG_PORT_PLUGOUT: A port is hot pluged out: Port:GigabitEthernet1/0/1, PCI:08.00.0. |
|
Explanation |
A hot-swapping-out event was detected on a port. |
|
Recommended action |
Verify that the hot-swapping operation was performed by an administrator. |
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. |
Identity messages
This section contains user identification messages.
IDENTITY_AUTO_IMPORT_FINISHED
|
Message text |
Finished importing identity user accounts and groups automatically. |
|
Variable fields |
N/A |
|
Severity level |
5 |
|
Example |
IDENTITY/5/IDENTITY_AUTO_IMPORT_FINISHED: Finished importing identity user accounts and groups automatically. |
|
Explanation |
The system finished importing identity user accounts and groups automatically. |
|
Recommended action |
No action is required. |
IDENTITY_AUTO_IMPORT_START
|
Message text |
Started to import identity user accounts and groups automatically. |
|
Variable fields |
N/A |
|
Severity level |
5 |
|
Example |
IDENTITY/5/IDENTITY_AUTO_IMPORT_START: Started to import identity user accounts and groups automatically. |
|
Explanation |
The system automatically started to import identity user accounts and groups. |
|
Recommended action |
No action is required. |
IDENTITY_CSV_IMPORT_FAILED
|
Message text |
Failed to import identity user [STRING] to domain [STRING] from the .csv file. |
|
Variable fields |
$1: Identity username. $2: Identity domain name. |
|
Severity level |
5 |
|
Example |
IDENTITY/5/IDENTITY_CSV_IMPORT_FAILED: Failed to import identity user network-us?er1 to domain system-domain from the .csv file. |
|
Explanation |
Failed to import an identity user account from a .csv file and stopped importing remaining identity user accounts. |
|
Recommended action |
1. Make sure no identity user account with the same name exists on the device. 2. Make sure the identity domain name or the identity username does not contain invalid characters. |
IDENTITY_IMC_IMPORT_FAILED_NO_MEMORY
|
Message text |
Failed to obtain data from IMC. Reason: Not enough memory. |
|
Variable fields |
N/A |
|
Severity level |
5 |
|
Example |
IDENTITY/5/IDENTITY_IMC_IMPORT_FAILED_NO_MEMORY: Failed to obtain data from IMC. Reason: Not enough memory. |
|
Explanation |
Failed to import identity user accounts and online identity user information from the IMC server because of insufficient memory. |
|
Recommended action |
No action is required. |
IDENTITY_LDAP_IMPORT_FAILED_NO_MEMORY
|
Message text |
Failed to obtain data from the LDAP server specified in scheme [STRING]. Reason: Not enough memory. |
|
Variable fields |
$1: LADP scheme name. |
|
Severity level |
5 |
|
Example |
IDENTITY/5/IDENTITY_LDAP_IMPORT_FAILED_NO_MEMORY: Failed to obtain data from the LDAP server specified in scheme test. Reason: Not enough memory. |
|
Explanation |
Failed to import identity users and identity groups from an LDAP server because of insufficient memory. |
|
Recommended action |
No action is required. |
IDENTITY_LDAP_IMPORT_GROUP_FAILED
|
Message text |
Failed to import identity group [STRING] to domain [STRING] from the LDAP server specified in scheme [STRING]. |
|
Variable fields |
$1: Identity group name. $2: Identity domain name. $3: LADP scheme name. |
|
Severity level |
5 |
|
Example |
IDENTITY/5/IDENTITY_LDAP_IMPORT_GROUP_FAILED: Failed to import identity group group-na?me1 to domain system-domain from the LDAP server specified in scheme ldap-scheme1. |
|
Explanation |
Failed to import an identity group from the LDAP server specified in an LDAP scheme. |
|
Recommended action |
1. Make sure no identity group with the same group name exists on the device. 2. Make sure the identity domain name or the identity group name does not contain invalid characters. |
IDENTITY_LDAP_IMPORT_USER_FAILED
|
Message text |
Failed to import identity user [STRING] to domain [STRING] from the LDAP server specified in scheme [STRING]. |
|
Variable fields |
$1: Identity username. $2: Identity domain name. $3: LADP scheme name. |
|
Severity level |
5 |
|
Example |
IDENTITY/5/IDENTITY_LDAP_IMPORT_USER_FAILED: Failed to import identity user user-na?me1 to domain system-domain from the LDAP server specified in scheme ldap-scheme1. |
|
Explanation |
Failed to import an identity user from the LDAP server specified in an LDAP scheme. |
|
Recommended action |
1. Make sure no identity user with the same name exists on the device. 2. Make sure the identity domain name or the identity username does not contain invalid characters. |
iFIT messages
This section contains in-situ Flow Information Telemetry (iFIT) messages.
IFIT_GLOBAL_FAILURE
|
Message text |
Failed to issue the ifit enable command to the driver. |
|
Severity level |
5 |
|
Example |
IFIT/5/IFIT_GLOBAL_FAILURE: Failed to issue the ifit enable command to the driver. |
|
Explanation |
The message is sent when the system fails to issue the ifit enable command to the driver after the command is executed successfully. |
|
Recommended action |
Please contact H3C support. |
IFIT_INST_ACTIVE
|
Message text |
iFIT measurement for instance [STRING] is active. |
|
Variable fields |
$1: Instance name. |
|
Severity level |
6 |
|
Example |
IFIT/6/IFIT_INST_ACTIVE: iFIT measurement for instance A is active. |
|
Explanation |
The message is sent when iFIT measurement for the instance becomes active and the system measures the packet loss and packet delay of the instance. |
|
Recommended action |
No action is required. |
IFIT_INST_FAILURE
|
Message text |
Failed to issue the configuration of the flow [UINT] to the driver. |
|
Variable fields |
$1: Flow ID. |
|
Severity level |
5 |
|
Example |
IFIT/5/IFIT_INST_FAILURE: Failed to issue the configuration of flow 4097 to the driver. |
|
Explanation |
This message is sent when the system fails to issue the flow configuration to the driver after the flow is configured successfully. |
|
Recommended action |
1. Use the display qos-acl resource command to verify that the ACL resources are sufficient. 2. If the resources are not sufficient, delete unnecessary ACLs and execute the measure enable command to enable iFIT measurement. |
IFIT_INST_INACTIVE
|
Message text |
iFIT measurement for instance [STRING] is inactive. Reason: [TEXT]. |
|
Variable fields |
$1: instance name. $2: Reason: · The bound interfaces are invalid. · The VPN instance does not exist. |
|
Severity level |
5 |
|
Example |
IFIT/5/IFIT_INST_INACTIVE: iFIT measurement for instance a is inactive. Reason: The bound interfaces are invalid. |
|
Explanation |
This message is sent when iFIT measurement for the instance is enabled but not active. |
|
Recommended action |
· Verify that the interfaces bound to the instance exist. · Verify that the VPN instance configured for the flow monitored by the instance exists. |
IFIT_NO_RESOURCE
|
Message text |
Failed to configure the flow [UINT] due to insufficient resources. |
|
Variable fields |
$1: Flow ID. |
|
Severity level |
5 |
|
Example |
IFIT/5/IFIT_NO_RESOURCE: Failed to configure the flow 4097 due to insufficient resources. |
|
Explanation |
This message is sent when the system fails to configure the flow to be monitored by the instance due to insufficient driver resources. |
|
Recommended action |
Delete the currently unused iFIT instances and restart iFIT measurement for the instance. |
IFIT_NO_SUPPORT
|
Message text |
iFIT is not supported in this slot. |
|
Severity level |
5 |
|
Example |
IFIT/5/IFIT_NO_SUPPORT: -slot=2; iFIT is not supported in this slot. |
|
Explanation |
This message is sent when iFIT measurement is not supported in the current slot. |
|
Recommended action |
Enable iFIT measurement in the slot that supports iFIT measurement. |
IFMON
This section contains interface monitoring messages.
BGTRAFFIC_SEND_BEGIN
|
Message text |
Interface [STRING] began sending background traffic. |
|
Variable fields |
$1: Interface name. |
|
Severity level |
6 |
|
Example |
IFMON/6/BGTRAFFIC_SEND_BEGIN: Interface GigabitEthernet1/0/1 began sending background traffic. |
|
Explanation |
When the outgoing traffic rate of an interface drops below 100 Mbps, the interface starts sending background traffic. |
|
Recommended action |
No action is required. |
BGTRAFFIC_SEND_END
|
Message text |
Interface [STRING] stopped sending background traffic. |
|
Variable fields |
$1: Interface name. |
|
Severity level |
6 |
|
Example |
IFMON/6/BGTRAFFIC_SEND_END: Interface GigabitEthernet1/0/1 stopped sending background traffic. |
|
Explanation |
When the outgoing traffic rate of an interface exceeds 300 Mbps, the interface stops sending background traffic. |
|
Recommended action |
No action is required. |
CRC_ERROR_RECOVERY
|
Message text |
The number of CRC error packets dropped below the lower threshold: Interface name=[STRING]. |
|
Variable fields |
$1: Interface name. |
|
Severity level |
4 |
|
Example |
IFMON/4/CRC_ERROR_RECOVERY: The number of CRC error packets dropped below the lower threshold: Interface name=GigabitEthernet1/0/1. |
|
Explanation |
This log message was generated when the number of CRC error packets detected within a statistics collection interval dropped below the threshold and the alarm was cleared. |
|
Recommended action |
No action is required. |
CRC_ERROR_THRESHOLD
|
Message text |
The number of CRC error packets exceeded the upper threshold: Interface name=[STRING], upper threshold=[UINT32], number of CRC error packets=[UINT64], interval=[UINT32]s. |
|
Variable fields |
$1: Interface name. $2: Upper threshold for the alarm or the upper bit error rate threshold. $3: Number of CRC error packets detected within the latest statistics collection interval. $4: Collection and comparison interval for CRC error packets, in seconds. |
|
Severity level |
4 |
|
Example |
IFMON/4/CRC_ERROR_THRESHOLD: The number of CRC error packets exceeded the upper threshold: Interface name=GigabitEthernet1/0/1, upper threshold=100, number of CRC error packets=200, interval=10s. |
|
Explanation |
This log message was generated when the number of CRC error packets within a statistics collection interval exceeded the upper threshold. Typically, this issue occurs because the threshold is set improperly or too many error packets appear because data is destroyed during transmission. |
|
Recommended action |
· Identify whether the upper threshold is set properly. · Identify whether the link environment quality is good. |
IFNET messages
This section contains interface management messages.
FLEXE_BANDWIDTH_MISMATCH
|
Message text |
The bandwidth of local FlexE logical interface [STRING] did not match the bandwidth of the peer interface with the same client ID. |
|
Variable fields |
$1: Interface name. |
|
Severity level |
4 |
|
Example |
IFNET/4/FLEXE_BANDWIDTH_MISMATCH: The bandwidth of local FlexE logical interface FlexE2/1/129 did not match the bandwidth of the peer interface with the same client ID. |
|
Explanation |
FlexE logical interfaces configured with the same client ID on two ends were configured with different available bandwidth. |
|
Recommended action |
Use the flexe-group bandwidth command to modify the available bandwidth of FlexE interfaces to ensure configuration consistency. |
FLEXE_BANDWIDTH_MISMATCH_RECOVER
|
Message text |
The bandwidth of local FlexE logical interface [STRING] matched the bandwidth of the peer interface with the same client ID. |
|
Variable fields |
$1: Interface name. |
|
Severity level |
5 |
|
Example |
IFNET/5/FLEXE_BANDWIDTH_MISMATCH_RECOVER: The bandwidth of local FlexE logical interface FlexE2/1/129 matched the bandwidth of the peer interface with the same client ID. |
|
Explanation |
FlexE logical interfaces configured with the same client ID on two ends were configured with the same available bandwidth. |
|
Recommended action |
No action is required. |
FLEXE_BANDWIDTH_REDUCE
|
Message text |
The actual bandwidth [INT32] Gbps of FlexE logical interface [STRING] became less than the configured bandwidth. |
|
Variable fields |
$1: Interface bandwidth. $2: Interface name. |
|
Severity level |
4 |
|
Example |
IFNET/4/FLEXE_BANDWIDTH_REDUCE: The actual bandwidth 50 Gbps of FlexE logical interface FlexE2/1/129 became less than the configured bandwidth. |
|
Explanation |
A FlexE physical interface went down. As a result, the bandwidth of the corresponding FlexE logical interface became less. |
|
Recommended action |
Check the physical connection of the FlexE physical interface and identify whether the link fails. |
FLEXE_BANDWIDTH_REDUCE_RECOVER
|
Message text |
The actual bandwidth [INT32] Gbps of FlexE logical interface [STRING] became equal to the configured bandwidth. |
|
Variable fields |
$1: Interface bandwidth. $2: Interface name. |
|
Severity level |
5 |
|
Example |
IFNET/5/FLEXE_BANDWIDTH_REDUCE_RECOVER: The actual bandwidth 100 Gbps of FlexE logical interface FlexE2/1/129 became equal to the configured bandwidth. |
|
Explanation |
A FlexE physical interface came up. As a result, the bandwidth of the corresponding FlexE logical interface recovered. |
|
Recommended action |
No action is required. |
FLEXE_CLIENTID_MISMATCH
|
Message text |
The client ID of local FlexE logical interface [STRING] did not match the client ID of a peer interface. |
|
Variable fields |
$1: Interface name. |
|
Severity level |
4 |
|
Example |
IFNET/4/FLEXE_CLIENTID_MISMATCH: The client ID of local FlexE logical interface FlexE2/1/129 did not match the client ID of a peer interface. |
|
Explanation |
FlexE logical interfaces on two ends were configured with different client IDs. |
|
Recommended action |
Use the flexe client-id command to modify the client IDs of FlexE logical interfaces to ensure configuration consistency. |
FLEXE_CLIENTID_MISMATCH_RECOVER
|
Message text |
The client ID of local FlexE logical interface [STRING] matched the client ID of a peer interface. |
|
Variable fields |
$1: Interface name. |
|
Severity level |
5 |
|
Example |
IFNET/5/FLEXE_CLIENTID_MISMATCH_RECOVER: The client ID of local FlexE logical interface FlexE2/1/129 matched the client ID of a peer interface. |
|
Explanation |
The FlexE logical interfaces on two ends were configured with the same client ID. |
|
Recommended action |
No action is required. |
FLEXE_GROUP_FAULT
|
Message text |
FlexE interface group [INT32] state changed to fault. |
|
Variable fields |
$1: FlexE interface group number. |
|
Severity level |
4 |
|
Example |
IFNET/4/FLEXE_GROUP_FAULT: FlexE interface group 1 state changed to fault. |
|
Explanation |
All FlexE physical interfaces in an FlexE interface group went down. As a result, the FlexE interface group failed. |
|
Recommended action |
Check the physical connections of the FlexE physical interfaces and identify whether the link fails. |
FLEXE_GROUP_FAULT_RECOVER
|
Message text |
FlexE interface group [INT32] state changed to normal |
|
Variable fields |
$1: FlexE interface group number. |
|
Severity level |
5 |
|
Example |
IFNET/5/FLEXE_GROUP_FAULT_RECOVER: FlexE interface group 1 state changed to normal. |
|
Explanation |
FlexE physical interfaces in up state existed in the FlexE interface group, and the FlexE interface group recovered. |
|
Recommended action |
No action is required. |
FLEXE_GROUPMEMBER_FAULT
|
Message text |
FlexE physical interface [STRING] in FlexE interface group [INT32] failed. |
|
Variable fields |
$1: Interface name. $2: FlexE interface group number. |
|
Severity level |
4 |
|
Example |
IFNET/4/FLEXE_GROUPMEMBER_FAULT: FlexE physical interface FlexE-50G2/1/1 in FlexE interface group 1 failed. |
|
Explanation |
FlexE physical interfaces in the FlexE interface group failed. |
|
Recommended action |
1. Check the physical connection of the FlexE physical interface and identify whether the link fails. 2. Identify whether the peer device fails. |
FLEXE_GROUPMEMBER_FAULT_RECOVER
|
Message text |
FlexE physical interface [STRING] in FlexE interface group [INT32] recovered. |
|
Variable fields |
$1: Interface name. $2: FlexE interface group number. |
|
Severity level |
5 |
|
Example |
IFNET/5/FLEXE_GROUPMEMBER_FAULT_RECOVER: FlexE physical interface FlexE-50G2/1/1 in FlexE interface group 1 recovered. |
|
Explanation |
FlexE physical interfaces in the FlexE interface group recovered. |
|
Recommended action |
No action is required. |
FLEXE_PHYFCSSD_ALARM
|
Message text |
FCS-SD error occurred on local FlexE physical interface [STRING]. |
|
Variable fields |
$1: Interface name. |
|
Severity level |
4 |
|
Example |
IFNET/4/FLEXE_PHYFCSSD_ALARM: FCS-SD error occurred on local FlexE physical interface FlexE-50G2/1/1. |
|
Explanation |
An FCS-SD error occurred on a FlexE physical interface. |
|
Recommended action |
Identify whether the physical link of the FlexE physical interface is normal. |
FLEXE_PHYFCSSD_ALARM_RECOVER
|
Message text |
FCS-SD error on local FlexE physical interface [STRING] was cleared. |
|
Variable fields |
$1: Interface name. |
|
Severity level |
5 |
|
Example |
IFNET/5/FLEXE_PHYFCSSD_ALARM_RECOVER: FCS-SD error on local FlexE physical interface FlexE-50G2/1/1 was cleared. |
|
Explanation |
The FCS-SD error on a FlexE physical interface was cleared. |
|
Recommended action |
No action is required. |
FLEXE_PHYGROUP_MISMATCH
|
Message text |
FlexE interface group [INT32] of local FlexE physical interface [STRING] did not match the FlexE interface group [INT32] of the peer interface. |
|
Variable fields |
$1: Local FlexE interface group number. $2: Interface name. $3: Peer FlexE interface group number. |
|
Severity level |
4 |
|
Example |
IFNET/4/FLEXE_PHYGROUP_MISMATCH: FlexE interface group 1 of local FlexE physical interface FlexE-50G2/1/1 did not match the FlexE interface group 2 of the peer interface. |
|
Explanation |
Two FlexE physical interfaces interconnected were in different FlexE interface groups. |
|
Recommended action |
Use the port flexe-group command to modify the FlexE interface groups of FlexE physical interfaces and assign the two interconnected FlexE physical interfaces to the same FlexE interface group. |
FLEXE_PHYGROUP_MISMATCH_RECOVER
|
Message text |
FlexE interface group [INT32] of local FlexE physical interface [STRING] matched the FlexE interface group [INT32] of the peer interface. |
|
Variable fields |
$1: Local FlexE interface group number. $2: Interface name. $3: Peer FlexE interface group number. |
|
Severity level |
5 |
|
Example |
IFNET/5/FLEXE_PHYGROUP_MISMATCH_RECOVER: FlexE interface group 1 of local FlexE physical interface FlexE-50G2/1/1 matched the FlexE interface group 1 of the peer interface. |
|
Explanation |
Two interconnected FlexE physical interfaces were assigned to the same FlexE interface group. |
|
Recommended action |
No action is required. |
FLEXE_PHYLOCAL_FAULT
|
Message text |
Local FlexE physical interface [STRING] failed and a port failure alarm was sent to the peer interface. |
|
Variable fields |
$1: Interface name. |
|
Severity level |
4 |
|
Example |
IFNET/4/FLEXE_PHYLOCAL_FAULT: Local FlexE physical interface FlexE-50G2/1/1 failed and a port failure alarm was sent to the peer interface. |
|
Explanation |
A failure occurred on a local FlexE physical interface and an alarm was generated to notify the peer FlexE physical interface. |
|
Recommended action |
Identify whether the physical connection of the local FlexE physical interface is normal or whether the local FlexE physical interface is manually shut down. |
FLEXE_PHYLOCAL_FAULT_RECOVER
|
Message text |
Local FlexE physical interface [STRING] recovered. |
|
Variable fields |
$1: Interface name. |
|
Severity level |
5 |
|
Example |
IFNET/5/FLEXE_PHYLOCAL_FAULT_RECOVER: Local FlexE physical interface FlexE-50G2/1/1 recovered. |
|
Explanation |
The failure on the local FlexE physical interface recovered. |
|
Recommended action |
No action is required. |
FLEXE_PHYNUM_MISMATCH
|
Message text |
PHY number [INT32] of local FlexE physical interface [STRING] did not match the PHY number [INT32] of the peer interface. |
|
Variable fields |
$1: PHY number for the local FlexE physical interface. $2: Interface name. $3: PHY number for the peer FlexE physical interface. |
|
Severity level |
4 |
|
Example |
IFNET/4/FLEXE_PHYNUM_MISMATCH: PHY number 10 of local FlexE physical interface Flex-50GE-2/1/1 did not match the PHY number 20 of the peer interface. |
|
Explanation |
Two interconnected FlexE physical interfaces were configured with different PHY numbers. |
|
Recommended action |
Use the phy-number command to modify PHY numbers of FlexE physical interfaces to ensure configuration consistency. |
FLEXE_PHYNUM_MISMATCH_RECOVER
|
Message text |
PHY number [INT32] of local FlexE physical interface [STRING] matched the PHY number [INT32] of the peer interface. |
|
Variable fields |
$1: PHY number for the local FlexE physical interface. $2: Interface name. $3: PHY number for the peer FlexE physical interface. |
|
Severity level |
5 |
|
Example |
IFNET/5/FLEXE_PHYNUM_MISMATCH_RECOVER: PHY number 10 of local FlexE physical interface FlexE-50G2/1/1 matched the PHY number 10 of the peer interface. |
|
Explanation |
Two interconnected FlexE physical interfaces were configured with the same PHY number. |
|
Recommended action |
No action is required. |
FLEXE_PHYREMOTE_FAULT
|
Message text |
The peer interface of local FlexE physical interface [STRING] failed. |
|
Variable fields |
$1: Interface name. |
|
Severity level |
4 |
|
Example |
IFNET/4/FLEXE_PHYREMOTE_FAULT: The peer interface of local FlexE physical interface FlexE-50G2/1/1 failed. |
|
Explanation |
The peer FlexE physical interface failed. |
|
Recommended action |
Identify whether the physical connection of the peer FlexE physical interface is normal or whether the peer FlexE physical interface is manually shut down. |
FLEXE_PHYREMOTE_FAULT_RECOVER
|
Message text |
The peer interface of local FlexE physical interface [STRING] recovered. |
|
Variable fields |
$1: Interface name. |
|
Severity level |
5 |
|
Example |
IFNET/5/FLEXE_PHYREMOTE_FAULT_RECOVER: The peer interface of local FlexE physical interface FlexE-50G2/1/1 recovered. |
|
Explanation |
The peer FlexE physical interface recovered. |
|
Recommended action |
No action is required. |
FLEXE_STSG_MISMATCH
|
Message text |
The sub-timeslot granularity [INT32] Gbps of the subcard where local FlexE physical interface [STRING] resides did not match that of the subcard where the peer interface resides. |
|
Variable fields |
$1: Sub-timeslot granularity. $2: Interface name. |
|
Severity level |
4 |
|
Example |
IFNET/4/FLEXE_STSG_MISMATCH: The sub-timeslot granularity 5 Gbps of the subcard where local FlexE interface FlexE-50G2/1/1 resides did not match that of the subcard where the peer interface resides. |
|
Explanation |
The subcards of two interconnected FlexE physical interfaces were configured with different sub-timeslot granularities. |
|
Recommended action |
Use the flexe sub-time-slot granula command to modify the sub-timeslot granularities of two interconnected devices to ensure configuration consistency. |
FLEXE_STSG_MISMATCH_RECOVER
|
Message text |
The sub-timeslot granularity [INT32] Gbps of the subcard where local FlexE physical interface [STRING] resides matched that of the subcard where the peer interface resides. |
|
Variable fields |
$1: Sub-timeslot granularity. $2: Interface name. |
|
Severity level |
5 |
|
Example |
IFNET/5/FLEXE_STSG_MISMATCH_RECOVER: The sub-timeslot granularity 5 Gbps of the subcard where local FlexE interface FlexE-50G2/1/1 resides matched that of the subcard where the peer interface resides. |
|
Explanation |
The subcards of two interconnected FlexE physical interfaces were configured with the same sub-timeslot granularity. |
|
Recommended action |
No action is required. |
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_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_LINKFLAP_DETECTED
|
Message text |
Link flapping was detected on [STRING]. |
|
Variable fields |
$1: Interface name |
|
Severity level |
3 |
|
Example |
IFNET/3/IF_LINKFLAP_DETECTED: Link flapping was detected on GigabitEthernet1/0/1. |
|
Explanation |
The number of detected flaps reached or exceeded the link flapping detection threshold during the link flapping detection interval. |
|
Recommended action |
1. Identify whether the cable is frequently plugged and unplugged for the local or peer interface. 2. Execute the port link-flap protect enable command to adjust the link flapping detection interval and the link flapping detection threshold. |
IFMGR_SPEED_CHANGE
|
Message text |
The speed of interface [STRING] has changed to [STRING]. |
|
Variable fields |
$1: Aggregate interface name. $2: Speed after change. |
|
Severity level |
6 |
|
Example |
IFNET/6/IFMGR_SPEED_CHANGE: The speed of interface Route-Aggregation6 has changed to 1Gbps. |
|
Explanation |
The speed of an aggregate interface changed. |
|
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. |
IMA
This section contains Integrity Measurements Architecture (IMA) messages.
IMA_ALLOCATE_FAILED
|
Message text |
Failed to allocate resource for file [STRING]. |
|
Variable fields |
$1: Name of the file of which you want to measure the integrity. |
|
Severity level |
4 |
|
Example |
IMA/4/IMA_ALLOCATE_FAILED: Failed to allocate resource for file /sbin/tcsmd. |
|
Explanation |
IMA failed to allocate resources to the specified file. |
|
Recommended action |
Contact H3C Support. |
IMA_DATA_ERROR
|
Message text |
Can't collect data of file [STRING]. |
|
$1: Name of the file of which you want to measure the integrity. |
|
|
Severity level |
4 |
|
Example |
IMA/4/IMA_DATA_ERROR: Can't collect data of file /sbin/tcsmd. |
|
Explanation |
IMA failed to open the specified file, read data from the file, or calculate the hash value of the file. |
|
Recommended action |
Contact H3C Support. |
IMA_FILE_HASH_FAILED
|
Message text |
Hash value of file [STRING] is not consistent with that in the RM file. |
|
Variable fields |
$1: Name of the file of which you want to measure the integrity. |
|
Severity level |
4 |
|
Example |
IMA/4/IMA_FILE_HASH_FAILED: Hash value of file /sbin/tcsmd is not consistent with that in the RM file. |
|
Explanation |
The computed hash value of the specified file is different from the hash value of the file stored in the RM file. The specified file is not trustworthy. |
|
Recommended action |
Contact H3C Support. |
IMA_RM_FILE_MISS
|
Message text |
File [STRING] is missing in the RM file. |
|
Variable fields |
$1: Name of the file of which you want to measure the integrity. |
|
Severity level |
4 |
|
Example |
IMA/4/IMA_RM_FILE_MISS: File /sbin/tcsmd is missing in the RM file. |
|
Explanation |
IMA did not find information about the specified file in the RM file. |
|
Recommended action |
Contact H3C Support. |
IMA_RM_HASH_MISS
|
Message text |
Hash value of file [STRING] is missing in the RM file. |
|
Variable fields |
$1: Name of the file of which you want to measure the integrity. |
|
Severity level |
4 |
|
Example |
IMA/4/IMA_RM_HASH_MISS: Hash value of file /sbin/tcsmd is missing in the RM file. |
|
Explanation |
IMA did not find the hash value of the specified file in the RM file. The hash algorithm used for integrity measurement of the specified file might not be supported in the RM. |
|
Recommended action |
Contact H3C Support. |
IMA_TEMPLATE_ERROR
|
Message text |
Failed to extend template hash value of file [STRING] to the PCR. |
|
Variable fields |
$1: Name of the file of which you want to measure the integrity. |
|
Severity level |
4 |
|
Example |
IMA/4/IMA_TEMPLATE_ERROR: Failed to extend template hash value of file /sbin/tcsmd to the PCR. |
|
Explanation |
IMA failed to extend the template hash value of the specified file to the PCRs. |
|
Recommended action |
Contact H3C Support. |
iNOF
This section contains Intelligent Lossless NVMe Over Fabric (iNOF) messages.
INOF_ADD_HOST
|
Message text |
The iNOF host is created from the [STRING] device, host’s IP is [STRING], port name is [STRING]. |
|
Variable fields |
$1: Device type: · Local—The host is connected to the local device. · Remote—The host is connected to a remote device. $2: IP address of the host. $3: If the device type is local, this field displays the host-facing port on the local device. If the device type is remote, this field displays the reflector-facing port on the local device. |
|
Severity level |
5 |
|
Example |
INOF/5/INOF_ADD_HOST: The iNOF host is created from the local device, host’s IP is 1.1.1.1, port name is GE0/0/1. |
|
Explanation |
This message is generated when iNOF detects an iNOF host online event. |
|
Recommended action |
No action is required. |
INOF_DELETE_HOST
|
Message text |
The iNOF host is deleted from the [STRING] device, because of [STRING], host’s IP is [STRING], port name is [STRING]. |
|
Variable fields |
$1: Device type: · Local—The host is connected to the local device. · Remote—The host is connected to a remote device. $2: Reason for the host offline event: · link down · pfc deadlock · network malfunction · zone configuration changes · endpoint configuration changes · lldp aged out · unknown $3: IP address of the host. $4: If the device type is local, this field displays the host-facing port on the local device. If the device type is remote, this field displays the reflector-facing port on the local device. |
|
Severity level |
5 |
|
Example |
INOF/5/INOF_DELETE_HOST: The iNOF host is deleted from the local device, because of link down. host’s IP is 1.1.1.1, port name is GE0/0/1. |
|
Explanation |
This message is generated when iNOF detects an iNOF host offline event. |
|
Recommended action |
Perform a troubleshooting based on the reason for the host offline event as follows: · link down—Check the link between the host and the iNOF switch to which the host is connected. · pfc deadlock—Check the state of PFC. · network malfunction—Check the network condition. · zone configuration changes—Check the iNOF zone configuration. · endpoint configuration changes—Check the host configuration. · lldp aged out—Use the display lldp status command to check the LLDP state of the device. |
INOF_LICENSE_ACTIVE
|
Message text |
The license for the iNOF feature is activated and the iNOF service will run normally. |
|
Variable fields |
N/A |
|
Severity level |
5 |
|
Example |
INOF/5/INOF_LICENSE_ACTIVE: The license for the iNOF feature is activated and the iNOF service will run normally. |
|
Explanation |
The iNOF license has been activated and the iNOF service will run normally. |
|
Recommended action |
No action is required. |
INOF_LICENSE_EXPIRE
|
Message text |
The license for the iNOF feature will expire in [UINT32] days. |
|
Variable fields |
$1: Remaining lifetime of the iNOF license. The value range is 1 to 30 days. |
|
Severity level |
5 |
|
Example |
INOF/5/INOF_LICENSE_EXPIRE: The license for the iNOF feature will expire in 5 days. |
|
Explanation |
The iNOF license will expire in some days. |
|
Recommended action |
Install a new iNOF license before the current iNOF license expires. |
INOF_NO_LICENSE
|
Message text |
The iNOF feature is disabled, because its license has expired or has been uninstalled. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
INOF/4/INOF_NO_LICENSE: The iNOF feature is disabled, because its license has expired or has been uninstalled. |
|
Explanation |
The iNOF feature is disabled, because its license has expired or has been uninstalled. |
|
Recommended action |
Install an iNOF license as soon as possible. |
iNQA
This section contains Intelligent Network Quality Analyzer (iNQA) messages.
INQA_BWD_LOSS_EXCEED
|
Message text |
Packet loss rate of the backward flow in instance [UINT] exceeded the upper limit. |
|
Variable fields |
$1: Instance ID. |
|
Severity level |
5 |
|
Example |
INQA/5/INQA_BWD_LOSS_EXCEED: Packet loss rate of the backward flow in instance 1 exceeded the upper limit. |
|
Explanation |
The message is sent when the packet loss rate of the backward flow exceeds the upper limit. |
|
Recommended action |
Examine the network and verify the physical connections are correct. |
INQA_BWD_LOSS_RECOV
|
Message text |
Packet loss rate of the backward flow in instance [UINT] recovered. |
|
Variable fields |
$1: Instance ID. |
|
Severity level |
6 |
|
Example |
INQA/6/INQA_BWD_LOSS_RECOV: Packet loss rate of the backward flow in instance 1 recovered. |
|
Explanation |
The message is sent when the packet loss rate of the backward flow drops down below the upper limit. |
|
Recommended action |
N/A |
INQA_DEBUG_FAIL
|
Message text |
Setting debugging switch to drive failed. |
|
Severity level |
5 |
|
Example |
INQA/5/INQA_DEBUG_FAIL: Setting debugging switch to drive failed. |
|
Explanation |
This message is sent when the system fails to set iNQA debugging switch to drive. |
|
Recommended action |
Delete the iNQA debugging switch setting and reconfigure the debugging. |
INQA_FLAG_DIFF
|
Message text |
Flags of collectors bound with the analyzer instance [UINT] are inconsistent. |
|
Variable fields |
$1: ID of the analyzer instance. |
|
Severity level |
5 |
|
Example |
INQA/5/INQA_FLAG_DIFF: Flags of collectors bound with the analyzer instance 1 are inconsistent. |
|
Explanation |
This message is sent when iNQA detects that the flag bit settings on the collectors bound to analyzer instance 1 are inconsistent. |
|
Recommended action |
Verify that the same flag bit is set on all collectors that are bound to the analyzer instance. |
INQA_FLAG_FAIL
|
Message text |
Setting coloring bit to drive failed. |
|
Severity level |
5 |
|
Example |
INQA/5/INQA_FLAG_FAIL: Setting coloring bit to drive failed. |
|
Explanation |
This message is sent when the system fails to set the color bit setting to the drive. |
|
Recommended action |
1. Use the display qos-acl resource command to verify that the ACL resources are sufficient. 2. If the resources are not sufficient, delete unnecessary ACLs and reconfigure the instance. |
INQA_FLOW_DIFF
|
Message text |
Flows of collectors bound with the analyzer instance [UINT] are inconsistent. |
|
Variable fields |
$1: ID of the analyzer instance. |
|
Severity level |
5 |
|
Example |
INQA/5/INQA_FLOW_DIFF: Flows of collectors bound with the analyzer instance 1 are inconsistent. |
|
Explanation |
This message is sent when iNQA detects that the target flows in statistics packets reported by the collectors bound to analyzer instance 1 are inconsistent. |
|
Recommended action |
Verify that the same target flow is defined on all collectors that are bound to the analyzer instance. |
INQA_FWD_LOSS_EXCEED
|
Message text |
Packet loss rate of the forward flow in instance [UINT] exceeded the upper limit. |
|
Variable fields |
$1: Instance ID. |
|
Severity level |
5 |
|
Example |
INQA/5/INQA_FWD_LOSS_EXCEED: Packet loss rate of the forward flow in instance 1 exceeded the upper limit. |
|
Explanation |
The message is sent when the packet loss rate of the forward flow exceeds the upper limit. |
|
Recommended action |
Examine the network and verify the physical connections are correct. |
INQA_FWD_LOSS_RECOV
|
Message text |
Packet loss rate of the forward flow in instance [UINT] recovered. |
|
Variable fields |
$1: Instance ID. |
|
Severity level |
6 |
|
Example |
INQA/6/INQA_FWD_LOSS_RECOV: Packet loss rate of the forward flow in instance 1 recovered. |
|
Explanation |
The message is sent when the packet loss rate of the forward flow drops down below the upper limit. |
|
Recommended action |
N/A |
INQA_INST_FAIL
|
Message text |
Setting instance [UINT] information to drive failed. |
|
Variable fields |
$1: Instance ID. |
|
Severity level |
5 |
|
Example |
INQA/5/INQA_INST_FAIL: Setting instance 1 information to drive failed. |
|
Explanation |
This message is sent when the system fails to send the instance configuration to the drive. |
|
Recommended action |
1. Use the display qos-acl resource command to verify that the ACL resources are sufficient. 2. If the resources are not sufficient, delete unnecessary ACLs and reconfigure the instance. |
INQA_INTVL_DIFF
|
Message text |
Intervals of collectors bound with analyzer instance [UINT] are inconsistent. |
|
Variable fields |
$1: ID of the analyzer instance. |
|
Severity level |
5 |
|
Example |
INQA/5/INQA_INTVL_DIFF: Intervals of collectors bound with analyzer instance 1 are inconsistent. |
|
Explanation |
This message is sent when iNQA detects that the measurement intervals in statistics packets reported by the collectors bound to analyzer instance 1 are inconsistent. |
|
Recommended action |
Verify that the same measurement intervals are configured on all collectors that are bound to the analyzer instance. |
INQA_MPNODATA
|
Message text |
No statistics on MP [UINT]. Reason:[text]. |
|
Severity level |
4 |
|
Example |
INQA/4/INQA_MPNODATA: No statistics on MP [UINT]. Reason:[text]. |
|
Explanation |
This message is sent when no statistics exist on the MP because the interface bound to the MP does not exist or the MP does not bound to any interface. |
|
Recommended action |
Bind a physical interface to the MP. |
INQA_NO_RESOURCE
|
Message text |
Failed to configure instance [UINT] due to insufficient resources. |
|
Variable fields |
$1: ID of the instance. |
|
Severity level |
5 |
|
Example |
INQA/5/INQA_NO_RESOURCE: Failed to configure instance 1 due to insufficient resources. |
|
Explanation |
This message is sent when iNQA fails to configure an instance due to insufficient ACL resources. |
|
Recommended action |
Release ACL resources by deleting unused iNQA instances or unused ACL resources, and then configure the instance. |
INQA_NO_SUPPORT
|
Message text |
iNQA is not supported in this slot. |
|
Severity level |
5 |
|
Example |
INQA/5/INQA_NO_SUPPORT: iNQA is not supported in this slot. |
|
Explanation |
This message is sent when the specified slot does not support iNQA. |
|
Recommended action |
Install an iNQA-capable module in the slot or switch the traffic for iNQA measurement to another slot that supports iNQA. |
INQA_SMOOTH_BEGIN_FAIL
|
Message text |
Setting smoothing beginning to kernel failed. |
|
Severity level |
5 |
|
Example |
INQA/5/INQA_SMOOTH_BEGIN_FAIL: Setting smoothing beginning to the kernel failed. |
|
Explanation |
This message is sent when iNQA fails to notify the kernel of the start of the smooth. |
|
Recommended action |
Please contact H3C support. |
INQA_SMOOTH_END_FAIL
|
Message text |
Setting smoothing ending to kernel failed. |
|
Severity level |
5 |
|
Example |
INQA/5/INQA_SMOOTH_END_FAIL: Setting smoothing ending to kernel failed. |
|
Explanation |
This message is sent when iNQA fails to notify the kernel of the end of the smooth. |
|
Recommended action |
Please contact H3C support. |
IP6ADDR
This section contains IPv6 addressing messages.
IP6ADDR_CREATEADDRESS_CONFLICT
|
Message text |
Failed to create an address by the prefix. Reason: [STRING] on [STRING] conflicts with SRv6 locator [STRING]. |
|
Variable fields |
$1: IPv6 address. $2: Interface name. $3: IPv6 prefix of the locator. |
|
Severity level |
4 |
|
Example |
IP6ADDR/4/IP6ADDR_CREATEADDRESS_CONFLICT: Failed to create an address by the prefix. Reason: 2000::1234:0:0:1/80 on GigabitEthernet1/0/1 conflicts with SRv6 locator 2000::1/64. |
|
Explanation |
This message is sent when the configuration of the ipv6 address prefix-number command conflicts with the SRv6 locator configuration in SRv6 view. |
|
Recommended action |
Remove the conflicting configuration and reconfigure the ipv6 address prefix-number command. |
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_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. |
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—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_ 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—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_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. |
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.
IPoE_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. |
3. Check whether the access interface has gone down. 4. Check whether the reset ip subscriber session command is executed to delete the dynamic IPoE sessions. 5. Check whether the undo ip subscriber session static command is executed to delete the static IPoE sessions. 6. Check whether new static users are added. 7. 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. |
8. Verify that the device communicates with the accounting server correctly. 9. 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. |
10. Verify that the device communicates with the accounting server correctly. 11. 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. |
12. Verify that the device communicates with the accounting server correctly. 13. 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. |
14. Verify that the device communicates with the accounting server correctly. 15. Verify that the accounting server operates correctly. |
|
Accounting request to AAA failed |
The device failed to send the accounting request to the accounting server. |
16. Verify that the device communicates with the accounting server correctly. 17. Verify that the accounting server operates correctly. |
|
Accounting update failure |
The accounting update failed. |
18. Verify that the device communicates with the accounting server correctly. 19. Verify that the accounting server operates correctly. |
|
Accounting failed |
The accounting failed. |
20. Verify that the device communicates with the accounting server correctly. 21. 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. |
22. Check the number of concurrent online users using the current local user name. 23. 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. |
24. Verify that the device communicates with the DHCP server correctly. 25. 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. |
26. Collect debugging information about the user login process by executing the following commands in sequence: ¡ terminal monitor ¡ terminal debugging ¡ debugging ip subscriber 27. 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. |
28. Verify that the device communicates with the authentication server correctly. 29. Verify that the username is correct. 30. Verify that the password is correct. 31. Verify that the authentication domain on the device is correct. |
|
Authorization failed |
The authorization failed. |
32. Verify that the device communicates with the authorization server correctly. 33. Verify that the authorization attributes deployed by the authorization server exist on the device and are configured correctly. 34. 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. |
35. Verify that the device communicates with the RADIUS server correctly. 36. Verify that the RADIUS server operates correctly. |
|
TACACS authentication reject |
The TACACS server returned an access-reject packet. |
37. Verify that the username is correct. 38. Verify that the password is correct. |
|
Authentication request to AAA failed |
The device failed to send the authentication request to the authentication server. |
39. Verify that the device communicates with the authentication server correctly. 40. Verify that the authentication server operates correctly. |
|
RADIUS authentication reject |
The RADIUS server returned an access-reject packet. |
41. Verify that the username is correct. 42. 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. |
43. Verify that the username is correct. 44. 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. |
45. Verify that the device communicates with the authentication server correctly. 46. Verify that the authentication server operates correctly. 47. 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. |
48. Verify that the dial-in user is a legal user. 49. 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. |
50. For dynamic individual users, check whether one or multiple of the following commands are configured: ¡ ip subscriber dhcp max-session ¡ ip subscriber unclassified-ip max-session 51. 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. 52. 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. |
IPS messages
This section contains IPS messages.
IPS_IPV4_INTERZONE
|
Message text |
Protocol(1001)=[STRING];Application(1002)=[STRING];SrcIPAddr(1003)=[IPADDR];SrcPort(1004)=[UINT16];DstIPAddr(1007)=[IPADDR];DstPort(1008)=[UINT16];RcvVPNInstance(1042)=[STRING];SrcZoneName(1025)=[STRING];DstZoneName(1035)=[STRING];UserName(1113)=[STRING];PolicyName(1079)=[STRING];AttackName(1088)=[STRING];AttackID(1089)=[UINT32];Category(1090)=[STRING];Protection(1091)=[STRING];SubProtection(1092)=[STRING];Severity(1087)=[STRING];Action(1053)=[STRING];CVE(1075)=[STRING];BID(1076)=[STRING];MSB(1077)=[STRING];HitDirection(1115)=[STRING];RealSrcIP(1100)=[STRING];SubCategory(1124)=[STRING];CapturePktName(1116)=[STRING];HttpHost(1117)=[STRING];HttpFirstLine(1118)=[STRING];PayLoad(1135)=[STRING]; |
|
Variable fields |
$1: Protocol type. $2: Application protocol name. $3: Source IP address. $4: Source port number. $5: Destination IP address. $6: Destination port number. $7: Source VPN instance name. $8: Source security zone name. $9: Destination security zone name. $10: Name of the identity user. $11: Policy name. $12: Attack name. $13: Attack ID. $14: Attack category. $15: Protected object type. $16: Protected object. $17: Severity level. Valid values are: ¡ INVALID: Severity level not specified. ¡ LOW. ¡ MEDIUM. ¡ HIGH. ¡ CRITICAL. $18: Actions applied to the packet. Available actions are: ¡ Block-Source. ¡ Drop. ¡ Reset. ¡ Permit. ¡ Redirect. ¡ Capture. ¡ Logging. $19: Common Vulnerabilities and Exposures (CVE). $20: Bugtraq ID (BID). $21: Microsoft Security Bulletins (MSB). $22: Packet direction: ¡ original. ¡ reply. $23: Original source IP address of the packet. $24: Attack subcategory. $25: Capture file name. $26: Host field. $27: Packet first line. $28: Event return value. |
|
Severity level |
4 |
|
Example |
IPS/4/IPS_IPV4_INTERZONE:-Context=1;Protocol(1001)=TCP;Application(1002)=http;SrcIPAddr(1003)=100.10.10.40;SrcPort(1004)=2999;DstIPAddr(1007)=200.10.10.40;DstPort(1008)=80;RcvVPNInstance(1042)=;SrcZoneName(1025)=spf;DstZoneName(1035)=spf;UserName(1113)=abc;PolicyName(1079)=ips;AttackName(1088)=WEB_CLIENT_Windows_Media_ASF_File_Download_SET;AttackID(1089)=5707;Category(1090)=Other;Protection(1091)=Other;SubProtection(1092)=Other;Severity(1087)=CRITICAL;Action(1053)=Reset & Logging;CVE(1075)=CVE-2014-6277 | CVE-2014-6278;BID(1076)=BID-22559;MSB(1077)=MS10-017;HitDirection(1115)=original;RealSrcIP(1100)=10.10.10.10,20.20.20.20;SubCategory(1124)=Other;CapturePktName(1116)=ips_100.10.10.40_20171205_101112_5707.pcap;HttpHost(1117)=www.shr.com;HttpFirstLine(1118)=/file/show.cgi%7cecho%20HSC/http_pic_300k.jpg;PayLoad(1135)=/file/show.cgi; |
|
Explanation |
This message is sent when an IPv4 packet matches a WAF signature. |
|
Recommended action |
No action is required. |
IPS_IPV6_INTERZONE
|
Message text |
Protocol(1001)=[STRING];Application(1002)=[STRING];SrcIPv6Addr(1036)=[IPADDR];SrcPort(1004)=[UINT16];DstIPv6Addr(1037)=[IPADDR];DstPort(1008)=[UINT16];RcvVPNInstance(1042)=-[ STRING];SrcZoneName(1025)=[STRING];DstZoneName(1035)=[STRING];UserName(1113)=[STRING];PolicyName(1079)=[STRING];AttackName(1088)=[STRING];AttackID(1089)=[UINT32];Category(1090)=[STRING];Protection(1091)=[STRING];SubProtection(1092)=[STRING];Severity(1087)=[STRING];Action(1053)=[STRING];CVE(1075)=[STRING];BID(1076)=[STRING];MSB(1077)=[STRING];HitDirection(1115)=[STRING];RealSrcIP(1100)=[STRING];SubCategory(1124)=[STRING];CapturePktName(1116)=[STRING];HttpHost(1117)=[STRING];HttpFirstLine(1118)=[STRING];PayLoad(1135)=[STRING]; |
|
Variable fields |
$1: Protocol type. $2: Application protocol name. $3: Source IPv6 address. $4: Source port number. $5: Destination IP address. $6: Destination port number. $7: Source VPN instance name. $8: Source security zone name. $9: Destination security zone name. $10: Name of the identity user. $11: Policy name. $12: Attack name. $13: Attack ID. $14: Attack category. $15: Protected object type. $16: Protected object. $17: Severity level. Valid values are: ¡ INVALID: Severity level not specified. ¡ LOW. ¡ MEDIUM. ¡ HIGH. ¡ CRITICAL. $18: Actions applied to the packet. Available actions are: ¡ Block-Source. ¡ Drop. ¡ Reset. ¡ Permit. ¡ Redirect. ¡ Capture. ¡ Logging. $19: Common Vulnerabilities and Exposures (CVE). $20: Bugtraq ID (BID). $21: Microsoft Security Bulletins (MSB). $22: Packet direction: ¡ original. ¡ reply. $23: Original source IP address of the packet. $24: Attack subcategory. $25: Capture file name. $26: Host field. $27: Packet first line. $28: Event return value. |
|
Severity level |
4 |
|
Example |
IPS/4/IPS_IPV6_INTERZONE:-Context=1;Protocol(1001)=TCP;Application(1002)=http;SrcIPv6Addr(1036)=100::40;SrcPort(1004)=2999;DstIPv6Addr(1037)=200::40;DstPort(1008)=80;RcvVPNInstance(1042)=;SrcZoneName(1025)=spf;DstZoneName(1035)=spf;UserName(1113)=aaa;PolicyName(1079)=ips;AttackName(1088)=WEB_CLIENT_Windows_Media_ASF_File_Download_SET;AttackID(1089)=5707;Category(1090)=Other;Protection(1091)=Other;SubProtection(1092)=Other;Severity(1087)=CRITICAL;Action(1053)=Reset & Logging;CVE(1075)=CVE-2014-6277 | CVE-2014-6278;BID(1076)=BID-22559;MSB(1077)=MS10-017;HitDirection(1115)=reply;RealSrcIP(1100)=10::1;SubCategory(1124)=Other;CapturePktName(1116)=ips_100::40_20171205_101112_5707.pcap;HttpHost(1117)=www.shr.com;HttpFirstLine(1118)=/file/show.cgi%7cecho%20HSC/http_pic_300k.jpg;PayLoad(1135)=/file/show.cgi; |
|
Explanation |
This message is sent when an IPv6 packet matches an IPS signature. |
|
Recommended action |
No action is required. |
IPS_WARNING
|
Message text |
Updated the IPS signature library successfully. |
|
Variable fields |
None. |
|
Severity level |
4 |
|
Example |
IPS/4/IPS_WARNING: -Context=1; Updated the IPS signature library successfully. |
|
Explanation |
The IPS signature library was updated successfully through a manual offline update or triggered online update. |
|
Recommended action |
No action is required. |
IPS_WARNING
|
Message text |
Rolled back the IPS signature library successfully. |
|
Variable fields |
None. |
|
Severity level |
4 |
|
Example |
IPS/4/IPS_WARNING: -Context=1; Rolled back the IPS signature library successfully. |
|
Explanation |
The IPS signature library was rolled back to the previous or factory default version successfully. |
|
Recommended action |
No action is required. |
IPSEC messages
This section contains IPsec messages.
IPSEC_ANTI-REPLAY_WINDOWS_ERROR
|
Message text |
Anti-replay dropped a packet: src=[STRING]; time-sent=[STRING], [UINT32] [STRING] [UINT32] [UINT32]:[UINT32]:[UINT32] [UINT32]us; time-received=[STRING], [UINT32] [STRING] [UINT32] [UINT32]:[UINT32]:[UINT32] [UINT32]us; time-diff=[UINT32]us; window-size= +-[FLOAT]ms. |
|
Variable fields |
$1: Source IP address of the packet. $2: Day of the week on which the packet was sent. $3: Day of the month on which the packet was sent. $4: Month in which the packet was sent. $5: Year in which the packet was sent. $6: Hour at which the packet was sent. $7: Minute at which the packet was sent. $8: Second at which the packet was sent. $9: Microsecond at which the packet was sent. $10: Day of the week on which the packet was received. $11: Day of the month on which the packet was received. $12: Month in which the packet was received. $13: Year in which the packet was received. $14: Hour at which the packet was received. $15: Minute at which the packet was received. $16: Second at which the packet was received. $17: Microsecond at which the packet was received. $18: Interval between the time the packet was sent and the time it was received, in microseconds. $19: Half the anti-replay window size, in milliseconds. |
|
Severity level |
6 |
|
Example |
IPSEC/6/IPSEC_ANTI-REPLAY_WINDOWS_ERROR:Anti-replay dropped a packet: src=192.168.58.178;time-sent=Sat, 23 Apr 2016 11:17:29 594565us; time-received =Sat, 23 Apr 2016 11:17:26 707866us; time-diff=2886699us; window-size =+-2500ms. |
|
Explanation |
A packet was dropped. Possible reasons include: · The interval between the time the packet was sent and the time it was received exceeds the anti-replay window size. · Anti-replay is enabled on the receiving IPsec tunnel end but the received packet does not have an anti-replay header. · In tunnel mode, anti-replay is not enabled but the received packet has an anti-replay header. |
|
Recommended action |
No action is required. |
IPSEC_FAILED_ADD_FLOW_TABLE
|
Message text |
Failed to add flow-table due to [STRING]. |
|
Variable fields |
$1: Reason for the failure. |
|
Severity level |
4 |
|
Example |
IPSEC/4/IPSEC_FAILED_ADD_FLOW_TABLE: Failed to add flow-table due to no enough resource. |
|
Explanation |
Failed to add the flow table. |
|
Recommended action |
If the failure is caused by not enough hardware resources, contact H3C Support. |
IPSEC_PACKET_DISCARDED
|
Message text |
IPsec packet discarded, Src IP:[STRING], Dst IP:[STRING], SPI:[UINT32], SN:[UINT32], Cause:[STRING]. |
|
Variable fields |
$1: Source IP address. $2: Destination IP address. $3: Security parameter index (SPI). $4: Sequence number of the packet. $5: Reason for dropping this packet: · Anti-replay checking failed. · AH authentication failed. · ESP authentication failed. · Invalid SA. · ESP decryption failed. · Source address of packet does not match the SA. · No ACL rule matched. |
|
Severity level |
6 |
|
Example |
IPSEC/6/IPSEC_PACKET_DISCARDED: IPsec packet discarded, Src IP:1.1.1.2, Dest IP:1.1.1.4, SPI:1002, SN:0, Cause:ah authentication failed. |
|
Explanation |
An IPsec packet was dropped. |
|
Recommended action |
No action is required. |
IPSEC_SA_ESTABLISH
|
Message text |
IPsec SA was established. Role: [STRING] Local address: [STRING] Remote address: [STRING] Sour addr: [STRING] Port: [UINT32] Protocol: [STRING] Dest addr: [STRING] Port: [UINT32] Protocol: [STRING] Inside VPN instance: [STRING] Outside VPN instance: [STRING] Inbound AH SPI: [STRING] Outbound AH SPI: [STRING] Inbound ESP SPI: [STRING] Outbound ESP SPI: [STRING] ACL number: [UINT32] ACL name: [STRING] |
|
Variable fields |
$1: Role, initiator or responder. $2: Local IP address. $3: Remote IP address. $4-$9: Data flow related parameters. $10: Inside VPN instance. $11: Outside VPN instance. $12: Inbound AH SPI. $13: Outbound AH SPI. $14: Inbound ESP SPI. $15: Outbound ESP SPI. $16: ACL number. The default is 4294967295. This field is not displayed if the ACL name is displayed. $17: ACL name. This field is not displayed if the ACL number is displayed. |
|
Severity level |
6 |
|
Example |
IPSEC/6/IPSEC_SA_ESTABLISH: IPsec SA was established. Role: Responder Local address: 2.2.2.2 Remote address: 1.1.1.1 Sour addr: 192.168.2.0/255.255.255.0 Port: 0 Protocol: IP Dest addr: 192.168.1.0/255.255.255.0 Port: 0 Protocol: IP Inside VPN instance: aaa Outside VPN instance: bbb Inbound AH SPI: 192365458 Outbound AH SPI: 13654581 Inbound ESP SPI: 292334583 Outbound ESP SPI: 5923654586 ACL number: 3101 |
|
Explanation |
An IPsec SA was established. |
|
Recommended action |
No action is required. |
IPSEC_SA_ESTABLISH_FAIL
|
Message text |
Failed to establish IPsec SA. Reason: [STRING]. SA information: Role: [STRING] Local address: [STRING] Remote address: [STRING] Sour addr: [STRING] Port: [UINT32] Protocol: [STRING] Dest addr: [STRING] Port: [UINT32] Protocol: [STRING] Inside VPN instance: [STRING] Outside VPN instance: [STRING] Inbound AH SPI: [STRING] Outbound AH SPI: [STRING] Inbound ESP SPI: [STRING] Outbound ESP SPI: [STRING] ACL number: [UINT32] ACL name: [STRING] |
|
Variable fields |
$1: Failure reason: · Get SP: Required configuration is missing in the SP. SP ID=%u. · Get SP: The SP's local address doesn't match the local address configured in the IKE profile. SP ID=%u, SP's local address=%s, p2policy's local address=%s. · Get SP: The remote address doesn't exist. SP ID=%u, hostname=%s. · Get SP: The SP's remote address doesn't match the remote address configured in the IKE profile. SP ID=%u, SP's remote address=%s, p2policy's remote address=%s. · Get SP: SP's mode [%d] is not IPSEC_PLCMODE_ISAKMP/ISAKMPTEMPLATE. · Get SP: The SP contains incomplete flow matching configuration. · Get SP: Failed to get the SP. · The policy contains incorrect ACL or IKE profile configuration. PolicyName=%s, Seqnum=%d. · Get SP: The SP doesn't have an IPsec transform set. · Get SP: Failed to create larval SA. · Create SA: Failed to fill the SA. · Create SA: Failed to create SA. · Create SA: Can't find SP. · Failed to create tunnel because a tunnel with the same index and sequence number already exists. Tunnel index=%d, tunnel seq=%d. · Failed to switch SA because the inbound SA can't be found. SPI=%u. · Failed to switch SA because the SA state is incorrect. · Failed to switch SA because the outbound SA can't be found. · Failed to switch SA because the outbound SA using another security protocol can't be found. · Failed to switch SA in kernel. · Failed to notify kernel of the link state change. · Number of IPsec tunnels reached the crypto capacity of the device. · Maximum number of IPsec tunnels already reached. · Failed to add IPsec tunnel. · Failed to add IPsec tunnel to kernel. · Getting SP: IPsec is smoothing. · Getting SP: IPsec is not running. · Getting SP: Failed to find SP by index and sequence number. · Getting SP: Creating SA timed out. · Getting SP by interface: Target node not online. · Getting SP by mGRE: Failed to get interface. · Getting SP: Failed to get SP by mGRE because interface type was invalid. · Getting SP: Failed to get SP by mGRE because profile %s was not found. · Getting SP: Failed to get SP by mGRE because of wrong profile type. · Getting SP by mGRE: Failed to find profile SP by profile %s. · Getting SP: Failed to get SP by mGRE. · Getting SP: Failed to get SP by SVTI because of invalid interface type. · Getting SP: Failed to get SP by SVTI because of no tunnel protection configuration. · Getting SP: Failed to get SP by SVTI because profile %s was not found. · Getting SP: Failed to get SP by SVTI because of wrong type of profile %s. · Getting SP by SVTI: Failed to find profile SP by profile %s. · Getting SP: Failed to get SP by SVTI because SP type was not ISAKMP. · Getting SP: Failed to match SVTI flow because IKE profile was not match. · Getting SP: Failed to match SVTI flow because flow was not match with ACL. · Getting SP by L3 interface: Failed to get interface data. · Getting SP: Failed to get SP by L3 interface because no SP entry was found by key. · Getting SP: Failed to get SP by L3 interface because no source interface SP entry was found by key. · Getting SP: Rejected peer's request of any flow when SP's mode was isakmp template and no ACL was specified. · Getting SP by L3 interface: Failed to match SP because policy cannot be found by SP. · Getting SP: Failed to match flow because renegotiation SP's index or Seqnum changed. · Getting SP by L3 interface: Failed to match SP because of no transform-set in SP. · Getting SP by L3 interface: Failed to create larval SA. · Getting SP: Failed to get SP matching ACL. $2: Role, initiator or responder. $3: Local IP address. $4: Remote IP address. $5-$10: Data flow related parameters. $11: Inside VPN instance. $12: Outside VPN instance. $13: Inbound AH SPI. $14: Outbound AH SPI. $15: Inbound ESP SPI. $16: Outbound ESP SPI. $17: ACL number. The default is 4294967295. This field is not displayed if the ACL name is displayed. $18: ACL name. This field is not displayed if the ACL number is displayed. |
|
Severity level |
6 |
|
Example |
IPSEC/6/IPSEC_SA_ESTABLISH_FAIL: Failed to establish IPsec SA Reason: Failed to add IPsec tunnel. SA information: Role: Responder Local address: 2.2.2.2 Remote address: 1.1.1.1 Sour addr: 192.168.2.0/255.255.255.0 Port: 0 Protocol: IP Dest addr: 192.168.1.0/255.255.255.0 Port: 0 Protocol: IP Inside VPN instance: aaa Outside VPN instance: bbb Inbound AH SPI: 192365458 Outbound AH SPI: 13654581 Inbound ESP SPI: 292334583 Outbound ESP SPI: 5923654586 ACL number: 3101 |
|
Explanation |
Failed to establish an IPsec SA. |
|
Recommended action |
Verify the IPsec configurations on the local and peer devices. |
IPSEC_SA_INITIATION
|
Message text |
Began to establish IPsec SA. Local address: [STRING] Remote address: [STRING] Sour addr: [STRING] Port: [UINT32] Protocol: [STRING] Dest addr: [STRING] Port: [UINT32] Protocol: [STRING] Inside VPN instance: [STRING] Outside VPN instance: [STRING] ACL number: [UINT32] ACL name: [STRING] |
|
Variable fields |
$1: Local IP address. $2: Remote IP address. $3-$8: Data flow related parameters. $9: Inside VPN instance. $10: Outside VPN instance. $11: ACL number. The default is 4294967295. This field is not displayed if the ACL name is displayed. $12: ACL name. This field is not displayed if the ACL number is displayed. |
|
Severity level |
6 |
|
Example |
IPSEC/6/IPSEC_SA_INITIATION: Began to establish IPsec SA. Local address: 2.2.2.2 Remote address: 1.1.1.1 Sour addr: 192.168.2.0/255.255.255.0 Port: 0 Protocol: IP Dest addr: 192.168.1.0/255.255.255.0 Port: 0 Protocol: IP Inside VPN instance: aaa Outside VPN instance: bbb ACL number: 3101 |
|
Explanation |
An IPsec SA was to be established. |
|
Recommended action |
No action is required. |
IPSEC_SA_TERMINATE
|
Message text |
The IPsec SA was deleted. Reason: [STRING] SA information: · Role: [STRING] · Local address: [STRING] · Remote address: [STRING] · Sour addr: [STRING] Port: [UINT32] Protocol: [STRING] · Dest addr: [STRING] Port: [UINT32] Protocol: [STRING] · Inside VPN instance: [STRING] · Outside VPN instance: [STRING] · Inbound AH SPI: [STRING] · Outbound AH SPI: [STRING] · Inbound ESP SPI: [STRING] · Outbound ESP SPI: [STRING] · ACL number: [UINT32] · ACL name: [STRING] |
|
Variable fields |
$1: Reason for the deletion: · SA idle timeout · The reset command was executed · Internal event · Configuration change · An IKE SA deletion message was received $2: Role, initiator or responder. $3: Local IP address. $4: Remote IP address. $5-$10: Data flow related parameters. $11: Inside VPN instance. $12: Outside VPN instance. $13: Inbound AH SPI $14: Outbound AH SPI $15: Inbound ESP SPI $16: Outbound ESP SPI $17: ACL number. The default is 4294967295. This field is not displayed if the ACL name is displayed. $18: ACL name. This field is not displayed if the ACL number is displayed. |
|
Severity level |
6 |
|
Example |
IPSEC/6/IPSEC_SA_TERMINATE: The IPsec SA was deleted. Reason: SA idle timeout. SA information: Role: initiator Local address: 2.2.2.2 Remote address: 1.1.1.1 Sour addr: 192.168.2.0/255.255.255.0 Port: 0 Protocol: IP Dest addr: 192.168.1.0/255.255.255.0 Port: 0 Protocol: IP Inside VPN instance: aaa Outside VPN instance: bbb Inbound AH SPI: 192365458 Outbound AH SPI: 13654581 Inbound ESP SPI: 292334583 Outbound ESP SPI: 5923654586 ACL number: 3101 |
|
Explanation |
An IPsec SA was deleted. |
|
Recommended action |
No action is required. |
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. |
IRF
This section contains IRF messages.
IRF_LINK_BLOCK
|
Message text |
IRF port went blocked. |
|
Variable fields |
N/A |
|
Severity level |
2 |
|
Example |
IRF/2/IRF_LINK_BLOCK: IRF port went blocked. |
|
Explanation |
The IRF port was blocked. A blocked IRF port cannot send or receive service packets, but it can send and receive IRF protocol packets. For example, this message might occur on the lower-priority member device when an IRF member ID conflict occurs between the member devices. |
|
Recommended action |
Check the IRF member ID on each member device for a conflict, and change their IRF member IDs to be unique. |
IRF_LINK_DOWN
|
Message text |
IRF port went down. |
|
Variable fields |
N/A |
|
Severity level |
3 |
|
Example |
IRF/3/IRF_LINK_DOWN: IRF port went down. |
|
Explanation |
The IRF port went down. |
|
Recommended action |
Verify the following items: · Network interfaces have been bound to the IRF port. · The IRF network interfaces and the peer interfaces have Layer 2 connectivity. |
IRF_LINK_UP
|
Message text |
IRF port came up. |
|
Variable fields |
N/A |
|
Severity level |
6 |
|
Example |
IRF/6/IRF_LINK_UP: IRF port came up. |
|
Explanation |
The IRF port came up. |
|
Recommended action |
No action is required. |
IRF_MEMBERID_CONFLICT
|
Message text |
IRF member ID conflict occurred. The ID [UINT32] has been used for another device with CPU-Mac: [STRING]. |
|
Variable fields |
$1: IRF member ID of the device. $2: CPU MAC address of the device. |
|
Severity level |
4 |
|
Example |
IRF/4/IRF_MEMBERID_CONFLICT:-slot = 5; IRF member ID conflict occurred, The ID 5 has been used for another device with CPU-Mac: 000c-29d7-c1ae. |
|
Explanation |
This message occurs when the device detects that it has the same IRF member ID as another device in the same broadcast domain. |
|
Recommended action |
Change the IRF member ID on either device. |
IRF_MERGE
|
Message text |
IRF merge occurred. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
IRF/4/IRF_MERGE: IRF merge occurred. |
|
Explanation |
IRF merge occurred. |
|
Recommended action |
No action is required. |
IRF_MERGE_NEED_REBOOT
|
Message text |
IRF merge occurred. This IRF system needs a reboot. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
IRF/4/IRF_MERGE_NEED_REBOOT: IRF merge occurred. This IRF system needs a reboot. |
|
Explanation |
IRF merge occurred. A reboot is required to complete the IRF merge because the master of this IRF fabric failed the master election for IRF merge. |
|
Recommended action |
Reboot the IRF fabric to complete the IRF merge. |
IRF_MERGE_NOT_NEED_REBOOT
|
Message text |
IRF merge occurred. This IRF system does not need to reboot. |
|
Variable fields |
N/A |
|
Severity level |
5 |
|
Example |
IRF/5/IRF_MERGE_NOT_NEED_REBOOT: IRF merge occurred. This IRF system does not need to reboot. |
|
Explanation |
IRF merge occurred. You do not need to reboot this IRF fabric because the master of this IRF fabric won the master election for IRF merge. |
|
Recommended action |
No action is required. |
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. Possible reasons are as follows: · circuit data clean—The neighbor state changed to DOWN because routing information was cleared. · holdtime expired—The neighbor state changed to DOWN because no hello packets were received within the hold time. · BFD session down—The neighbor state changed to DOWN because BFD detected a link failure. · peer reset—The neighbor state changed to DOWN because the reset isis peer command was executed. · circuit ID conflicts—The neighbor state changed to DOWN because a hello packet with incorrect circuit ID was received from the neighbor. · P2P peer GR down—The neighbor state changed to DOWN because a P2P hello packet with no GR option was received during GR. · 2way-pass—The neighbor state changed to UP because the neighbor relationship was established. · 2way-fail—The neighbor state changed to INIT because a one-way hello packet was received from the neighbor. |
|
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 |
When the neighbor state changes to DOWN or INIT, check the reason and take recommended actions. · circuit data clean—Check the interface state, IS-IS configuration, and network connectivity. · holdtime expired—Verify whether a hello packet has been received from the neighbor within the hold time. · BFD session down—Check the connectivity to the neighbor. · peer reset—Check whether the reset isis peer command has been executed. · circuit ID conflicts—Check whether the IS-IS interface settings have been edited multiples times on the neighbor. · P2P peer GR down—Check whether the neighbor supports GR. · 2way-fail—Check the following: ¡ Check whether the reset isis peer command has been executed. ¡ Verify whether a hello packet has been received from the neighbor within the hold time. ¡ Check whether the authentication settings are the same on the device and the neighbor. |
ISIS_SID_CONFLICT
|
Message text |
IS-IS [UINT16], [STRING], SID=[STRING], SID conflict might exist, check with command: display isis segment-routing ipv6 sid-info conflict. |
|
Variable fields |
$1: Process ID. $2: IS type. Options include Level-1 and Level-2. $3: SID. |
|
Severity level |
5 |
|
Example |
ISIS/5/ISIS_SID_CONFLICT: IS-IS 1, Level-1, SID=100::1, SID conflict might exist, check with command: display isis segment-routing ipv6 sid-info conflict. |
|
Explanation |
An SID conflict might have occurred in the network. |
|
Recommended action |
Execute the display isis segment-routing ipv6 sid-info conflict command to view SID conflict information. |
ISIS_SID_CONFLICT_CLEAR
|
Message text |
IS-IS [UINT16], [STRING], SID=[STRING], SID conflict is cleared. |
|
Variable fields |
$1: Process ID. $2: IS type. Options include Level-1 and Level-2. $3: SID. |
|
Severity level |
5 |
|
Example |
ISIS/5/ISIS_SID_CONFLICT_CLEAR: IS-IS 1, Level-1, SID=100::1, SID conflict is cleared. |
|
Explanation |
The SID conflict has been cleared. |
|
Recommended action |
No action is required. |
ISSU messages
This section contains ISSU messages.
ISSU_LOAD_FAILED
|
Message text |
Failed to execute the issu load command. |
|
Variable fields |
N/A |
|
Severity level |
5 |
|
Example |
ISSU/5/ISSU_LOAD_FAILED: -IPAddr=192.168.79.1-User=**; Failed to execute the issu load command. |
|
Explanation |
A user executed the issu load command, but the operation failed. |
|
Recommended action |
Take actions as prompted. |
ISSU_LOAD_SUCCESS
|
Message text |
Executed the issu load command successfully. |
|
Variable fields |
N/A |
|
Severity level |
5 |
|
Example |
ISSU/5/ISSU_LOAD_SUCCESS: -IPAddr=192.168.79.1-User=**; Executed the issu load command successfully. |
|
Explanation |
A user executed the issu load command successfully. |
|
Recommended action |
No action is required. |
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. |
KPI
This section contains KPI module messages.
INDICATOR_UPPERLIMIT_ALARM
|
Message text |
CHASSIS [[INT32]] SLOT [[INT32]] CPU [[INT32]] Module [[STRING]] Object [[STRING]] Indicator [[STRING]] Value [[STRING]] exceeded the upper limit of [STRING]. |
|
Variable fields |
$1: Chassis ID. $2: Slot ID. $3: CPU ID. $4: Module name. $5: Object name. $6: Indicator name. $7: Indicator value. $8: Upper limit value of the indicator. |
|
Severity Level |
5 |
|
Example |
KPI/5/INDICATOR_UPPERLIMIT_ALARM: CHASSIS [0] SLOT [2] CPU [0] Module [ifmgr] Object [GigabitEthernet2/0/1] Indicator [if actual speed] Value [950] exceeded the upper limit of 900. |
|
Explanation |
Intelligent monitoring is enabled. An indicator collected by the KPI module exceeds the upper limit value. |
|
Recommended action |
No action is required. |
INDICATOR_LOWERLIMIT_ALARM
|
Message text |
CHASSIS [[INT32]] SLOT [[INT32]] CPU [[INT32]] Module [[STRING]] Object [[STRING]] Indicator [[STRING]] Value [[STRING]] is below the lower limit of [STRING]. |
|
Variable fields |
$1: Chassis ID. $2: Slot ID. $3: CPU ID. $4: Module name. $5: Object name. $6: Indicator name. $7: Indicator value. $8: Lower limit value of the indicator. |
|
Severity Level |
5 |
|
Example |
KPI/5/INDICATOR_LOWERLIMIT_ALARM: CHASSIS [0] SLOT [2] CPU [0] Module [ifmgr] Object [GigabitEthernet2/0/1] Indicator [if actual speed] Value [50] is below the lower limit of 100. |
|
Explanation |
Intelligent monitoring is enabled. An indicator collected by the KPI module falls below the lower limit value. |
|
Recommended action |
No action is required. |
INDICATOR_RECOVER_ALARM
|
Message text |
CHASSIS [[INT32]] SLOT [[INT32]] CPU [[INT32]] Module [[STRING]] Object [[STRING]] Indicator [[STRING]] Value [[STRING]] returned to normal between [STRING] and [STRING]. |
|
Variable fields |
$1: Chassis ID. $2: Slot ID. $3: CPU ID. $4: Module name. $5: Object name. $6: Indicator name. $7: Indicator value. $8: Lower limit value of the indicator. $9: Upper limit value of the indicator. |
|
Severity Level |
5 |
|
Example |
KPI/5/INDICATOR_RECOVER_ALARM:CHASSIS [0] SLOT [2] CPU [0] Module [ifmgr] Object [GigabitEthernet2/0/1] Indicator [if actual speed] Value [500] returned to normal between 100 and 900. |
|
Explanation |
Intelligent monitoring is enabled. An indicator collected by the KPI module returns to the normal range between the upper and lower limit values. |
|
Recommended action |
No action is required. |
INDICATOR_PREDICT_UPPERLIMIT_ALARM
|
Message text |
CHASSIS [[INT32]] SLOT [[INT32]] CPU [[INT32]] Module [[STRING]] Object [[STRING]] Indicator [[STRING]] Predict Value [[STRING]] exceeded the upper limit of [STRING]. |
|
Variable fields |
$1: Chassis ID. $2: Slot ID. $3: CPU ID. $4: Module name. $5: Object name. $6: Indicator name. $7: Predicted value of the indicator. $8: Upper limit value of the indicator. |
|
Severity Level |
5 |
|
Example |
KPI/5/INDICATOR_PREDICT_UPPERLIMIT_ALARM: CHASSIS [0] SLOT [2] CPU [0] Module [ifmgr] Object [GigabitEthernet2/0/1] Indicator [if actual speed] Predict Value [950] exceeded the upper limit of 900. |
|
Explanation |
KPI intelligent prediction is enabled. The predicted value of an indicator exceeds the upper limit value of the indicator. |
|
Recommended action |
No action is required. |
INDICATOR_PREDICT_LOWERLIMIT_ALARM
|
Message text |
CHASSIS [[INT32]] SLOT [[INT32]] CPU [[INT32]] Module [[STRING]] Object [[STRING]] Indicator [[STRING]] Predict Value [[STRING]] is below the lower limit of [STRING]. |
|
Variable fields |
$1: Chassis ID. $2: Slot ID. $3: CPU ID. $4: Module name. $5: Object name. $6: Indicator name. $7: Predicted value of the indicator. $8: Lower limit value of the indicator. |
|
Severity Level |
5 |
|
Example |
KPI/5/INDICATOR_PREDICT_LOWERLIMIT_ALARM: CHASSIS [0] SLOT [2] CPU [0] Module [ifmgr] Object [GigabitEthernet2/0/1] Indicator [if actual speed] Predict Value [50] is below the lower limit of 100. |
|
Explanation |
KPI intelligent prediction is enabled. The predicted value of an indicator falls below the lower limit value of the indicator. |
|
Recommended action |
No action is required. |
INDICATOR_PREDICT_RECOVER_ALARM
|
Message text |
CHASSIS [[INT32]] SLOT [[INT32]] CPU [[INT32]] Module [[STRING]] Object [[STRING]] Indicator [[STRING]] Predict Value [[STRING]] returned to normal between [STRING] and [STRING]. |
|
Variable fields |
$1: Chassis ID. $2: Slot ID. $3: CPU ID. $4: Module name. $5: Object name. $6: Indicator name. $7: Predicted value of the indicator. $8: Lower limit value of the indicator. $9: Upper limit value of the indicator. |
|
Severity Level |
5 |
|
Example |
KPI/5/INDICATOR_PREDICT_RECOVER_ALARM: CHASSIS [0] SLOT [2] CPU [0] Module [ifmgr] Object [GigabitEthernet2/0/1] Indicator [if actual speed] Predict Value [500] returned to normal between 100 and 900. |
|
Explanation |
KPI intelligent prediction is enabled. The predicted value of an indicator returns to the normal range between the upper and lower limit values of the indicator. |
|
Recommended action |
No action is required. |
L2PT messages
This section contains L2PT messages.
L2PT_ADD_GROUPMEMBER_FAILED
|
Message text |
Failed to add [STRING] as a member to the VLAN tunnel group for [STRING]. |
|
Variable fields |
$1: Interface name. $2: Protocol name. |
|
Severity level |
4 |
|
Example |
L2PT/4/L2PT_ADD_GROUPMEMBER_FAILED: Failed to add GigabitEthernet2/0/1 as a member to the VLAN tunnel group for STP. |
|
Explanation |
Failed to add an interface to a VLAN tunnel group for a protocol. |
|
Recommended action |
No action is required. |
L2PT_CREATE_TUNNELGROUP_FAILED
|
Message text |
Failed to create a VLAN tunnel group for [STRING]. |
|
Variable fields |
$1: Protocol name. |
|
Severity level |
4 |
|
Example |
L2PT/4/L2PT_CREATE_TUNNELGROUP_FAILED: Failed to create a VLAN tunnel group for STP. |
|
Explanation |
Failed to create a VLAN tunnel group for a protocol. |
|
Recommended action |
No action is required. |
L2PT_ENABLE_DROP_FAILED
|
Message text |
Failed to enable [STRING] packet drop on [STRING]. |
|
Variable fields |
$1: Protocol name. $2: Interface name. |
|
Severity level |
4 |
|
Example |
L2PT/4/L2PT_ENABLE_DROP_FAILED: Failed to enable STP packet drop on GigabitEthernet2/0/1. |
|
Explanation |
Failed to enable L2PT drop for a protocol on an interface. |
|
Recommended action |
No action is required. |
L2PT_SET_MULTIMAC_FAILED
|
Message text |
|
|
Variable fields |
$1: MAC address. |
|
Severity level |
4 |
|
Example |
L2PT/4/L2PT_SET_MULTIMAC_FAILED: Failed to set a tunnel destination MAC address to 010f-e200-0003. |
|
Explanation |
Failed to specify the destination multicast MAC address for tunneled packets. |
|
Recommended action |
No action is required. |
L2TPv2 messages
This section contains L2TPv2 messages.
L2TPV2_TUNNEL_EXCEED_LIMIT
|
Message text |
Number of L2TP tunnels exceeded the limit. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
L2TPV2/4/L2TPV2_TUNNEL_EXCEED_LIMIT: Number of L2TP tunnels exceeded the limit. |
|
Explanation |
The number of established L2TP tunnels has reached the limit. |
|
Recommended action |
1. Perform one of the following tasks: ¡ Execute the reset l2tp tunnel command to disconnect an idle tunnel. ¡ Wait for the device to automatically disconnect an idle tunnel after the hello interval elapses. 2. If the problem persists, contact H3C for support. |
L2TPV2_SESSION_EXCEED_LIMIT
|
Message text |
Number of L2TP sessions exceeded the limit. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
L2TPV2/4/L2TPV2_SESSION_EXCEED_LIMIT: Number of L2TP sessions exceeded the limit. |
|
Explanation |
The number of established L2TP sessions has reached the limit. |
|
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. |
PROCESS
|
Message text |
The EVPN global MAC address is a reserved MAC. |
|
Variable fields |
N/A |
|
Severity level |
7 |
|
Example |
L2VPN/7/PROCESS: The EVPN global MAC address is a reserved MAC. |
|
Explanation |
The configured EVPN global MAC address is a reserved MAC address of the device. |
|
Recommended action |
Change the EVPN global MAC address to another MAC address. |
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_LACP_ISOLATE
|
Message text |
Member port [STRING] of aggregation group [STRING] changed to the inactive state, because the link-aggregation lacp isolate setting had been configured. |
|
Variable fields |
$1: Port name. $2: Link aggregation group type and ID. |
|
Severity level |
6 |
|
Example |
LAGG/6/LAGG_INACTIVE_LACP_ISOLATE: Member port FGE1/0/50 of aggregation group BAGG1 changed to the inactive state, because the link-aggregation lacp isolate setting had been configured. |
|
Explanation |
A member port in an aggregation group changed to the Unselected state because the aggregate interface was isolated. |
|
Recommended action |
Remove aggregate interface isolation. |
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. · LDP process stopped. |
|
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. |
License
This section contains license messages.
LICENSE_FILE_LOST
|
Message text |
License activation file [STRING] was lost. |
|
Variable fields |
$1: Name of the activation file. |
|
Severity level |
4 |
|
Example |
LIC/4/LICENSE_FILE_LOST: License activation file 0123456789.ak was lost. |
|
Explanation |
A license activation file was lost. |
|
Recommended action |
1. Copy the backup activation file to the license folder on the device. 2. If no backup activation file is available, go to the email box provided when the license is registered and obtain the activation file. Then, copy the activation file to the license folder on the device. 3. If you do not obtain the activation file in the email box provided when the license is registered, contact H3C Support to retrieve the lost activation file and copy the activation file to the license folder on the device. |
LICENSE_FILE_RESTORE
|
Message text |
License activation file [STRING] was successfully restored. |
|
Variable fields |
$1: Name of the activation file. |
|
Severity level |
6 |
|
Example |
LIC/6/LICENSE_FILE_RESTORE: License activation file 0123456789.ak was successfully restored. |
|
Explanation |
A license activation file was successfully restored. |
|
Recommended action |
No action is required. |
LICENSE_NEAR_EXPIRE
|
Message text |
License [STRING] will expire in [left days] days. |
|
Variable fields |
$1: License key, activation key, or activation file name. $2: Remaining validity days. |
|
Severity level |
4 |
|
Example |
LIC/4/LICENSE_NEAR_EXPIRE: License 0123456789.ak will expire in 2 days. |
|
Explanation |
A license will expire in n days. |
|
Recommended action |
Purchase and install a new license as soon as possible. |
LICENSE_EXPIRE
|
Message text |
License [STRING] expired. |
|
Variable fields |
$1: License key, activation key, or activation file name. |
|
Severity level |
4 |
|
Example |
LIC/4/LICENSE_EXPIRE: License 0123456789.ak expired. |
|
Explanation |
A license expired. |
|
Recommended action |
Purchase and install a new license as soon as possible. |
LICENSE_TAKE_EFFECT
|
Message text |
State of license [STRING] changed to in use. |
|
Variable fields |
$1: License key, activation key, or activation file name. |
|
Severity level |
6 |
|
Example |
LIC/6/LICENSE_TAKE_EFFECT: State of license 0123456789.ak changed to in use. |
|
Explanation |
The state of a license changed from usable to in use. |
|
Recommended action |
No action is required. |
LICENSE_PRE_NEAR_EXPIRE
|
Message text |
Preinstalled licenses will expire in [STRING] days. |
|
Variable fields |
$1: Remaining validity days. |
|
Severity level |
4 |
|
Example |
LIC/4/LICENSE_PRE_NEAR_EXPIRE: Preinstalled licenses will expire in 3 days. |
|
Explanation |
Preinstalled licenses will expire in n days. If no formal licenses are installed, license-based features will become inaccessible after the preinstalled licenses expire. To use the features, you must install formal licenses. |
|
Recommended action |
Examine whether usable formal licenses are installed. If no usable formal licenses are installed, purchase and install formal licenses. |
LICENSE_PRE_EXPIRE
|
Message text |
Preinstalled licenses expired. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
LIC/4/LICENSE_PRE_EXPIRE: Preinstalled licenses expired. |
|
Explanation |
Preinstalled licenses expired. |
|
Recommended action |
Examine whether usable formal licenses are installed. If no usable formal licenses are installed, purchase and install formal licenses. |
CLCP
This section contains CLCP messages.
CLCP_CLIENT_LOGIN_FAIL
|
Message text |
Failed to login. Reason: [STRING]. |
|
Variable fields |
$1: Login failure reason. Supported values: ¡ Network error. ¡ Incorrect username or password. ¡ Error occurred for communication between license client and license server. |
|
Severity level |
4 |
|
Example |
CLCP/4/CLCP_CLIENT_LOGIN_FAIL: Failed to login. Reason: Incorrect username or password. |
|
Explanation |
The license client failed to log in to the license server. |
|
Recommended action |
Handle the issue according to the failure reason: · If the reason is network error, verify that the server address configuration is correct. · If the reason is incorrect username or password, verify that the username and password configured on the device for accessing the license server are the same as those on the license server. · If communication error occurs, contact H3C Support. |
CLCP_NEAR_EXPIRE
|
Message text |
License [STRING] will expire in [STRING] days. |
|
Variable fields |
$1: Feature name. $2: Remaining validity days. |
|
Severity level |
4 |
|
Example |
CLCP/4/CLCP_NEAR_EXPIRE: License APMGR will expire in 2 days. |
|
Explanation |
A license will expire in n days. |
|
Recommended action |
Install a new license on the license server. |
CLCP_RECLAIM
|
Message text |
License [STRING] was reclaimed. Reason: [STRING]. |
|
Variable fields |
$1: Feature name. $2: Reclamation reason. Supported values: ¡ The license-based feature was not in use. ¡ The license aged out after the client had been disconnected from the license server for 30 days. ¡ The license was forcibly reclaimed by the license server. ¡ The license expired on the license server. ¡ The license was uninstalled on the license server. ¡ License information is inconsistent between license client and license server. ¡ Unknown. |
|
Severity level |
4 |
|
Example |
CLCP/4/CLCP_RECLAIM: License APMGR was reclaimed. Reason: The license expired on the license server. |
|
Explanation |
A license was reclaimed by the license server. |
|
Recommended action |
Handle the issue according to the reclamation reason: · If the license-based feature is not in use, no action is required. To use the feature, the license client will automatically request the license again from the license server. · If the license ages out because of long time disconnection, restore the connection between the device and the license server. · If the license is forcibly reclaimed by the license server, no action is required. · If the license expires on the license server, install a new license on the license server. · If the license is uninstalled on the license server, install a new license on the license server. · If license information is inconsistent between license client and license server, the license client will automatically request the license again after the license is reclaimed. In this case, no action is required. If exceptions exist, contact H3C Support. · For unknown reason, the license client will automatically request the license again after the license is reclaimed. In this case, no action is required. If exceptions exist, contact H3C Support. |
CLCP_REQUEST_FAIL
|
Message text |
Failed to request license [STRING]. Reason: [STRING]. |
|
Variable fields |
$1: Feature name. $2: Failure reason. Supported values: ¡ No sufficient license resources on the license server. ¡ Error occurred for communication between license client and license server. ¡ License server system error. |
|
Severity level |
4 |
|
Example |
CLCP/4/CLCP_REQUEST_FAIL: Failed to request license APMGR. Reason: No sufficient license resources on the license server. |
|
Explanation |
The license client failed to request a license. |
|
Recommended action |
Handle the issue according to the failure reason: · If no sufficient license resources are available on the license server, purchase new licenses and install them on the license server. · If communication error occurs, contact H3C Support. · If a system error exists on the license server, contact H3C Support. |
CLCP_RECLAIM_ALARM
|
Message text |
License [STRING] will be reclaimed in [STRING] days. Reason: [STRING]. |
|
Variable fields |
$1: Feature name. $2: Remaining validity days. $3: Reclamation reason. The value is The license client was disconnected from the license server. |
|
Severity level |
4 |
|
Example |
CLCP/4/CLCP_RECLAIM_ALARM: License APMGR will be reclaimed in 2 days. Reason: The license client was disconnected from the license server. |
|
Explanation |
A license will be reclaimed in n days, because the license client has been disconnected from the license server. |
|
Recommended action |
Restore the connection between the license client and license server. |
CLCP_CLIENT_OFFLINE
|
Message text |
The license client went offline. Reason: [STRING]. |
|
Variable fields |
$1: Offline reason. Supported values: ¡ The license server forced the license client to go offline. ¡ Client information aged out on the license server. ¡ The license client has been disconnected from the license server for a long time. |
|
Severity level |
4 |
|
Example |
CLCP/4/CLCP_CLIENT_OFFLINE: The license client went offline. Reason: The license server forced the license client to go offline. |
|
Explanation |
The license client went offline. |
|
Recommended action |
Handle the issue according to the offline reason: · If the license server forces the license client to go offline, no action is required. The device will be automatically reconnected to the license server after a period of time. · If client information ages out on the license server, no action is required. The device will be automatically reconnected to the license server after a period of time. · If the license client has been disconnected from the license server for a long time, restore the connection between the device and the license server. |
LIPC messages
This section contains Leopard inter-process communication (LIPC) messages.
LIPC_MTCP_CHECK
|
Message text |
Data stays in the receive buffer for an over long time. Owner=[STRING], VRF=[INTEGER], Group=[INTEGER], MID=[INTEGER]. |
|
Variable fields |
$1: Name of the process. $2: Name of the VRF to which the LIPC link belongs to. $3: Multicast group ID of the LIPC link. $4: Multicast group member ID of the LIPC link. |
|
Severity level |
4 |
|
Example |
LIPC/4/LIPC_MTCP_CHECK: Data stays in the receive buffer for an over long time. Owner=fsd, VRF=0, Group=134, MID=10001. |
|
Explanation |
Processes will establish an LIPC link during internal communication. LIPC MTCP assigns a receive buffer to the process and checks at intervals whether data in the buffer is retrieved by the process. If the process has not retrieved data from the receive buffer for a long time and a large amount of data accumulates in the buffer, the process might run abnormally. |
|
Recommended action |
No action is required. |
LIPC_STCP_CHECK
|
Message text |
Data stays in the receive buffer for an over long time. Owner=[STRING], VRF=[INTEGER], local address/port=[INTEGER]/[INTEGER], remote address/port=[INTEGER]/[INTEGER]. |
|
Variable fields |
$1: Name of the process that established the LIPC link. $2: Name of the VRF to which the LIPC link belongs. $3: LIP address of the local node. $4: Port number of the local node. $5: LIP address of the remote node. $6: Port number of the remote node. |
|
Severity level |
4 |
|
Example |
LIPC/4/LIPC_STCP_CHECK: Data stays in the receive buffer for an over long time. Owner=fsd, VRF=0, local address/port=8/10515, remote address/port=0/20415. |
|
Explanation |
Processes will establish an LIPC link during internal communication. LIPC STCP assigns a receive buffer to the process and checks at intervals whether data in the buffer is retrieved by the process. If the process has not retrieved data from the receive buffer for a long time and a large amount of data accumulates in the buffer, the process might run abnormally. |
|
Recommended action |
No action is required. |
LIPC_STCP_DUPLICATE_SOCKET
|
Message text |
Socket (LIP=[INTEGER], PortID=[INTEGER], Owner=[STRING]) has failed connect to server (LIP=[INTEGER],Port=[INTEGER]) too many times. |
|
Variable fields |
$1: LIP address of the local node. $2: Port number of the local node. $3: Name of the process. $5: LIP address of the remote node. $6: Service port number. |
|
Severity level |
4 |
|
Example |
LIPC/4/LIPC_STCP_DUPLICATE_SOCKET: Socket (LIP=8, PortID=123456, Owner=sfs) has failed connect to server (LIP=8, Port=10515) too many times. |
|
Explanation |
Typically, if a service module fails to establish a connection by using a socket, it will close that socket and apply for another socket for reconnection. If the module continues to use the failed socket for connection, LIPC will return a failure. This log records information about reconnection failures of a module by using a failed socket. |
|
Recommended action |
N/A |
LIPC_SUDP_CHECK
|
Message text |
Data stays in the receive buffer for an over long time. Owner=[STRING], VRF=[INTEGER], local address/port=[INTEGER]/[INTEGER], remote address/port=[INTEGER]/[INTEGER]. |
|
Variable fields |
$1: Name of the process that established the LIPC link. $2: Name of the VRF to which the LIPC link belongs. $3: LIP address of the local node. $4: Port number of the local node. $5: LIP address of the remote node. $6: Port number of the remote node. |
|
Severity level |
4 |
|
Example |
LIPC/4/LIPC_SUDP_CHECK: Data stays in the receive buffer for an over long time. Owner=snmpd, VRF=0, local address/port=0/10525, remote address/port=32768/0. |
|
Explanation |
Processes will establish an LIPC link during internal communication. LIPC SUDP assigns a receive buffer to the process and checks at intervals whether data in the buffer is retrieved by the process. If the process has not retrieved data from the receive buffer for a long time and a large amount of data accumulates in the buffer, the process might run abnormally. |
|
Recommended action |
No action is required. |
PORT_CHANGE
|
Message text |
STCP: Node where the listening port number [INTGER] (MDC: [INTGER] VRF: [INTGER]) resides changed from LIP [INTGER] to LIP [INTGER]. |
|
Variable fields |
$1: LIPC global port number. $2: Name of the MDC where the LIPC global port resides. $3: Name of the VRF to which the LIPC global port belongs. $4: Name of the old LIPC node where the LIPC global port resides. $5: Name of the new LIPC node where the LIPC global port resides. |
|
Severity level |
5 |
|
Example |
LIPC/5/PORT_CHANGE: STCP: Node where the listening port number 620 (MDC: 1 VRF: 1) resides changed from LIP 1 to LIP 3. |
|
Explanation |
STCP assigns an LIPC global port number as a listening port number to each service module as requested. Typically, a service module listens to the port number only on the LIPC node where the port has been requested. This message is generated if the service module listens to the port number on a different LIPC node. STCP will move the port number from the old LIPC node to the new node. |
|
Recommended action |
No action is required. |
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 |
|
|
Severity level |
|
|
Example |
|
|
Explanation |
|
|
Recommended action |
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_ADD_BLACKLIST
|
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 aaa 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
|
Message text |
The password of local [STRING] user [STRING] was modified. |
|
Variable fields |
$1: User type. Options are: ¡ network-access ¡ device-management $2: Username. |
|
Severity level |
5 |
|
Example |
LS/5/LS_PWD_CHGPWD: The password of local network-access user abc was modified. |
|
Explanation |
The password of a local user was modified. |
|
Recommended action |
No action is required under normal circumstances. The device administrator can audit any abnormal password modification behavior by checking this log. |
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] 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. |
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 reached 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 reached the maximum number 1024. |
|
Explanation |
The number of entries in the global MAC address table reached 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 reached 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 reached the maximum number 1024 for interface GigabitEthernet2/0/32. |
|
Explanation |
The number of entries in the MAC address table for an interface reached 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 reached 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 reached the maximum number 1024 in VLAN 2. |
|
Explanation |
The number of entries in the MAC address table for a VLAN reached 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. |
MACA messages
This section contains MAC authentication messages.
MACA_ENABLE_NOT_EFFECTIVE
|
Message text |
MAC authentication is enabled but is not effective on interface [STRING]. |
|
Variable fields |
$1: Interface type and number. |
|
Severity level |
3 |
|
Example |
MACA/3/MACA_ENABLE_NOT_EFFECTIVE: MAC authentication is enabled but is not effective on interface Ethernet3/1/2. |
|
Explanation |
MAC authentication configuration does not take effect on an interface, because the interface does not support MAC authentication. |
|
Recommended action |
1. Disable MAC authentication on the interface. 2. Reconnect the connected devices to another interface that supports MAC authentication. 3. Enable MAC authentication on the new interface. |
MACA_LOGIN_FAILURE
|
Message text |
-IfName=[STRING]-MACAddr=[STRING]-VLANID=[STRING]-Username=[STRING]-UsernameFormat=[STRING]; User failed MAC authentication. Reason: [STRING]. |
|
Variable fields |
$1: Interface type and number. $2: MAC address. $3: VLAN ID. $4: Username. $5: User account format. $6: Failure cause: · MAC address authorization failed. · VLAN authorization failed. · VSI authorization failed. · ACL authorization failed. · User profile authorization failed. · URL authorization failed. · Microsegment authorization failed. · Authentication process failed. |
|
Severity level |
6 |
|
Example |
MACA/6/MACA_LOGIN_FAILURE: -IfName=GigabitEthernet1/0/1-MACAddr=0000-0000-0001-VLANID=1-Username=0000-0000-0001-UsernameFormat=MAC address; User failed MAC authentication. Reason: VLAN authorization failed. |
|
Explanation |
The user failed MAC authentication for a specific reason. |
|
Recommended action |
Locate the failure cause and handle the issue according to the failure cause. |
MACA_LOGIN_SUCC
|
Message text |
-IfName=[STRING]-MACAddr=[STRING]-AccessVLANID=[STRING]-AuthorizationVLANID=[STRING]-Username=[STRING]-UsernameFormat=[STRING]; User passed MAC authentication and came online. |
|
Variable fields |
$1: Interface type and number. $2: MAC address. $3: ID of the access VLAN. $4: ID of the authorization VLAN. $5: Username. $6: User account format. |
|
Severity level |
6 |
|
Example |
MACA/6/MACA_LOGIN_SUCC:-IfName=GigabitEthernet1/0/4-MACAddr=0010-8400-22b9-AccessVLANID=444-AuthorizationVLANID=444-Username=00-10-84-00-22-b9-UsernameFormat=MAC address; User passed MAC authentication and came online. |
|
Explanation |
The user passed MAC authentication. |
|
Recommended action |
No action is required. |
MACA_LOGIN_SUCC (in open mode)
|
Message text |
-IfName=[STRING]-MACAddr=[STRING]-VLANID=[STRING]-Username=[STRING]-UsernameFormat=[STRING]; The user that failed MAC authentication passed open authentication and came online. |
|
Variable fields |
$1: Interface type and number. $2: MAC address. $3: VLAN ID. $4: Username. $5: User account format. |
|
Severity level |
6 |
|
Example |
MACA/6/MACA_LOGIN_SUCC:-IfName=GigabitEthernet1/0/4-MACAddr=0010-8400-22b9-VLANID=444-Username=00-10-84-00-22-b9-UsernameFormat=MAC address; The user that failed MAC authentication passed open authentication and came online. |
|
Explanation |
A user failed MAC authentication but passed open authentication. |
|
Recommended action |
No action is required. |
MACA_LOGOFF
|
Message text |
-IfName=[STRING]-MACAddr=[STRING]-VLANID=[STRING]-Username=[STRING]-UsernameFormat=[STRING]; MAC authentication user was logged off. |
|
Variable fields |
$1: Interface type and number. $2: MAC address. $3: VLAN ID. $4: Username. $5: User account format. |
|
Severity level |
6 |
|
Example |
MACA/6/MACA_LOGOFF:-IfName=GigabitEthernet1/0/4-MACAddr=0010-8400-22b9-VLANID=444-Username=00-10-84-00-22-b9-UsernameFormat=MAC address; MAC authentication user was logged off. |
|
Explanation |
The MAC authentication user was logged off. |
|
Recommended action |
Locate the logoff cause and remove the issue. If the logoff was requested by the user, no action is required. |
MACA_LOGOFF (in open mode)
|
Message text |
-IfName=[STRING]-MACAddr=[STRING]-VLANID=[STRING]-Username=[STRING]-UsernameFormat=[STRING]; MAC authentication open user was logged off. |
|
Variable fields |
$1: Interface type and number. $2: MAC address. $3: VLAN ID. $4: Username. $5: User account format. |
|
Severity level |
6 |
|
Example |
MACA/6/MACA_LOGOFF:-IfName=GigabitEthernet1/0/4-MACAddr=0010-8400-22b9-VLANID=444-Username=00-10-84-00-22-b9-UsernameFormat=MAC address; MAC authentication open user was logged off. |
|
Explanation |
A MAC authentication open user was logged off. |
|
Recommended action |
Locate the logoff cause and remove the issue. If the logoff was requested by the user, no action is required. |
MACSEC messages
This section contains MACsec messages.
MACSEC_MKA_KEEPALIVE_TIMEOUT
|
Message text |
The live peer with SCI [STRING] and CKN [STRING] aged out on interface [STRING]. |
|
Variable fields |
$1: SCI. $2: CKN. $3: Interface name. |
|
Severity level |
4 |
|
Example |
MACSEC/4/MACSEC_MKA_KEEPALIVE_TIMEOUT: The live peer with SCI 00E00100000A0006 and CKN 80A0EA0CB03D aged out on interface GigabitEthernet1/0/1. |
|
Explanation |
A live peer aged out on an interface, because the local participant had not received any MKA packets from the peer before the keepalive timer expired. The local participant removed the peer information from the port. |
|
Recommended action |
Check the link between the local participant and the live peer for link failure. If the link is down, recover the link. |
MACSEC_MKA_PRINCIPAL_ACTOR
|
Message text |
The actor with CKN [STRING] became principal actor on interface [STRING]. |
|
Variable fields |
$1: CKN. $2: Interface name. |
|
Severity level |
6 |
|
Example |
MACSEC/6/MACSEC_MKA_PRINCIPAL_ACTOR: The actor with CKN 80A0EA0CB03D became principal actor on interface GigabitEthernet1/0/1. |
|
Explanation |
The actor with the highest key server priority became the principal actor. |
|
Recommended action |
No action is required. |
MACSEC_MKA_SAK_REFRESH
|
Message text |
The SAK has been refreshed on interface [STRING]. |
|
Variable fields |
$1: Interface name. |
|
Severity level |
6 |
|
Example |
MACSEC/6/MACSEC_MKA_SAK_REFRESH: The SAK has been refreshed on interface GigabitEthernet1/0/1. |
|
Explanation |
The participant on the interface derived or received a new SAK. |
|
Recommended action |
No action is required. |
MACSEC_MKA_SESSION_REAUTH
|
Message text |
The MKA session with CKN [STRING] was re-authenticated on interface [STRING]. |
|
Variable fields |
$1: CKN. $2: Interface name. |
|
Severity level |
6 |
|
Example |
MACSEC/6/MACSEC_MKA_SESSION_REAUTH: The MKA session with CKN 80A0EA0CB03D was re-authenticated on interface GigabitEthernet1/0/1. |
|
Explanation |
The interface performed 802.1X reauthentication. After the 802.1X reauthentication, the participants received a new CAK, and used it to re-establish the MKA session. |
|
Recommended action |
No action is required. |
MACSEC_MKA_SESSION_SECURED
|
Message text |
The MKA session with CKN [STRING] was secured on interface [STRING]. |
|
Variable fields |
$1: CKN. $2: Interface name. |
|
Severity level |
6 |
|
Example |
MACSEC/6/MACSEC_MKA_SESSION_SECURED: The MKA session with CKN 80A020EA0CB03D was secured on interface GigabitEthernet1/0/1. |
|
Explanation |
The MKA session on the interface was secured. Packets are encrypted and transmitted in cipher text. The event occurs in the following situations: · The MKA session state changes from unsecured to secured. · The local participant and the peer negotiate a new MKA session when the following conditions exist: ¡ Both the key server and the peer support MACsec. ¡ A minimum of one participant is enabled with the MACsec desire feature. |
|
Recommended action |
No action is required. |
MACSEC_MKA_SESSION_START
|
Message text |
The MKA session with CKN [STRING] started on interface [STRING]. |
|
Variable fields |
$1: CKN. $2: Interface name. |
|
Severity level |
6 |
|
Example |
MACSEC/6/MACSEC_MKA_SESSION_START: The MKA session with CKN 80A020EA0CB03D started on interface GigabitEthernet1/0/1. |
|
Explanation |
The MKA session negotiation was initiated. Possible reasons include: · New CAK is available after MKA is enabled. · The user re-establishes the MKA session. · The interface that failed MKA session negotiation receives an MKA packet. |
|
Recommended action |
No action is required. |
MACSEC_MKA_SESSION_STOP
|
Message text |
The MKA session with CKN [STRING] stopped on interface [STRING]. |
|
Variable fields |
$1: CKN. $2: Interface name. |
|
Severity level |
5 |
|
Example |
MACSEC/5/MACSEC_MKA_SESSION_STOP: The MKA session with CKN 80A020EA0CB03D stopped on interface GigabitEthernet1/0/1. |
|
Explanation |
The MKA session was terminated. Possible reasons include: · The user removes or re-establishes the MKA session on the interface. · The link associated to the session is down. |
|
Recommended action |
1. Use the display mka session command to check whether the session exists: ¡ If the session has been re-established, ignore the message. ¡ If the session does not exist and is not removed by the user, check the link associated with the session for link failure. 2. Recover the link if the link is down. |
MACSEC_MKA_SESSION_UNSECURED
|
Message text |
The MKA session with CKN [STRING] was not secured on interface [STRING]. |
|
Variable fields |
$1: CKN. $2: Interface name. |
|
Severity level |
5 |
|
Example |
MACSEC/5/MACSEC_MKA_SESSION_UNSECURED: The MKA session with CKN 80A020EA0CB03D was not secured on interface GigabitEthernet1/0/1. |
|
Explanation |
The MKA session on the interface was not secured. Packets are transmitted in plain text. The event occurs in the following situations: · The MKA session state changes from secured to unsecured. · The local participant and the peer negotiate a new MKA session when the following conditions exist: ¡ The key server and the peer are not both MACsec capable. ¡ No participant is enabled with the MACsec desire feature. |
|
Recommended action |
To secure the MKA session, perform the following tasks: · Verify that both the key server and the peer support MACsec. · Verify that a minimum of one participant is enabled with the MACsec desire feature. |
MDC messages
This section contains MDC messages.
MDC_CREATE
|
Message text |
MDC [UINT16] was created. |
|
Variable fields |
$1: MDC ID. |
|
Severity level |
5 |
|
Example |
MDC/5/MDC_CREATE: MDC 2 was created. |
|
Explanation |
An MDC was created successfully. |
|
Recommended action |
No action is required. |
MDC_CREATE_ERR
|
Message text |
Failed to create MDC [UINT16] for insufficient resources. |
|
Variable fields |
$1: MDC ID. |
|
Severity level |
5 |
|
Example |
MDC/5/MDC_CREATE_ERR: -Slot=1; Failed to create MDC 2 for insufficient resources. |
|
Explanation |
The standby MPU did not have enough resources to create the MDC. At startup, the standby MPU obtains MDC configuration information from the active MPU. If the standby MPU does not have enough resources to create an MDC, it outputs this log message. |
|
Recommended action |
1. Use the display mdc resource command to display the CPU, memory, and disk space resources on the standby MPU. 2. Perform one of the following tasks: ¡ If the memory space is insufficient, increase the memory space. If the disk space is insufficient, delete unused files. ¡ Use the undo mdc command to delete the specified MDC. ¡ Replace the standby MPU with an MPU that has sufficient resources. |
MDC_DELETE
|
Message text |
MDC [UINT16] was deleted. |
|
Variable fields |
$1: MDC ID. |
|
Severity level |
5 |
|
Example |
MDC/5/MDC_DELETE: MDC 2 was deleted. |
|
Explanation |
An MDC was deleted successfully. |
|
Recommended action |
No action is required. |
MDC_LICENSE_EXPIRE
|
Message text |
The MDC feature's license will expire in [UINT32] days. |
|
Variable fields |
$1: Number of days, in the range of 1 to 30. |
|
Severity level |
5 |
|
Example |
MDC/5/MDC_LICENSE_EXPIRE: The MDC feature’s license will expire in 5 days. |
|
Explanation |
The license for the MDC feature was about to expire. |
|
Recommended action |
Install a new license. |
MDC_NO_FORMAL_LICENSE
|
Message text |
The feature MDC has no formal license. |
|
Variable fields |
N/A |
|
Severity level |
5 |
|
Example |
MDC/5/MDC_NO_FORMAL_LICENSE: The feature MDC has no formal license. |
|
Explanation |
The standby MPU became the active MPU but it did not have a formal license. The MDC feature has a free trial period. To use the feature after the period elapses, you must install a license for the standby MPU. |
|
Recommended action |
Install a formal license. |
MDC_NO_LICENSE_EXIT
|
Message text |
The MDC feature is being disabled, because it has no license. |
|
Variable fields |
N/A |
|
Severity level |
5 |
|
Example |
MDC/5/MDC_NO_LICENSE_EXIT: The MDC feature is being disabled, because it has no license. |
|
Explanation |
The MDC feature was disabled because the license for the MDC feature expired or was uninstalled. |
|
Recommended action |
Install the required license. |
MDC_OFFLINE
|
Message text |
MDC [UINT16] is offline now. |
|
Variable fields |
$1: MDC ID. |
|
Severity level |
5 |
|
Example |
MDC/5/MDC_OFFLINE: MDC 2 is offline now. |
|
Explanation |
An MDC was stopped. |
|
Recommended action |
No action is required. |
MDC_ONLINE
|
Message text |
MDC [UINT16] is online now. |
|
Variable fields |
$1: MDC ID. |
|
Severity level |
5 |
|
Example |
MDC/5/MDC_ONLINE: MDC 2 is online now. |
|
Explanation |
An MDC was started. |
|
Recommended action |
No action is required. |
MDC_STATE_CHANGE
|
Message text |
MDC [UINT16] status changed to [STRING]. |
|
Variable fields |
$1: MDC ID. $2: MDC status: ¡ updating–The system is assigning interface cards to the MDC (executing the location command). ¡ stopping–The system is stopping the MDC (executing the undo mdc start command). ¡ inactive–The MDC is inactive. ¡ starting–The system is starting the MDC (executing the mdc start command). ¡ active–The MDC is operating correctly. |
|
Severity level |
5 |
|
Example |
MDC/5/MDC_STATE_CHANGE: MDC 2 status changed to active. |
|
Explanation |
The status of an MDC changed. |
|
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. |
MLAG
This section contains M-LAG messages.
M-LAG_AUTORECOVERY_TIMEOUT
|
Message text |
The reload delay timer timed out. Please check configuration of the M-LAG system. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
M-LAG/4/M-LAG_AUTORECOVERY_TIMEOUT: The reload delay timer timed out. Please check configuration of the M-LAG system. |
|
Explanation |
The reload delay timer expired, and the M-LAG system had only one available member device or had two primary member devices. |
|
Recommended action |
· Verify that the unavailable member device is operating correctly. · Verify that the peer link and keepalive link are correctly configured and connected. · Increase the reload delay timer. |
M-LAG_DEVICE_MADDOWN
|
Message text |
[STRING] will change to the M-LAG MAD DOWN state because [STRING]. |
|
Variable fields |
$1: Interfaces to be placed in M-LAG MAD DOWN state: · All service interfaces not excluded from the M-LAG MAD DOWN action. · All service interfaces included in the M-LAG MAD DOWN action. · All new service interfaces not excluded from the M-LAG MAD DOWN. · All new service interfaces included in the M-LAG MAD DOWN action. $2: Cause of the M-LAG MAD DOWN state and recommended remedy: · The device is Initializing. Please set up the M-LAG system first. · The peer link went down and the keepalive link remains up. Please check the peer link settings on both ends of the peer link. · The peer link came up. Please wait for the data restoration delay timer to expire. · The peer link and all M-LAG interfaces went down. Please first check the peer link settings on both ends of the peer link. |
|
Severity level |
4 |
|
Example |
M-LAG/4/M-LAG_DEVICE_MADDOWN: All service interfaces not excluded from the M-LAG MAD DOWN action will change to the M-LAG MAD DOWN state because the peer link went down and the keepalive link remains up. Please check the peer link settings on both ends of the peer link. |
|
Explanation |
Network interfaces on the device will be shut down by M-LAG MAD. |
|
Recommended action |
Verify that the peer link is correctly connected and the cable is working correctly. |
M-LAG_DEVICE_MADRECOVERY
|
Message text |
All service interfaces on the device will be recovered from the M-LAG MAD DOWN state. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
M-LAG/4/M-LAG_DEVICE_MADRECOVERY: All service interfaces on the device will be recovered from the M-LAG MAD DOWN state. |
|
Explanation |
The device will restore the state of all service interfaces that have been placed in M-LAG MAD DOWN state. |
|
Recommended action |
No action is required. |
M-LAG_GLBCHECK_CONSISTENCY
|
Message text |
Finished global type [UINT16] configuration consistency check. No inconsistency exists. |
|
Variable fields |
$1: Configuration consistency check type. |
|
Severity level |
6 |
|
Example |
M-LAG/6/M-LAG_GLBCHECK_CONSISTENCY: Finished global type 1 configuration consistency check. No inconsistency exists. |
|
Explanation |
No inconsistency was detected in global type 1 or type 2 configuration. |
|
Recommended action |
No action is required. |
M-LAG_GLBCHECK_INCONSISTENCY
|
Message text |
Detected global type [UINT16] configuration inconsistency. |
|
Variable fields |
$1: Configuration consistency check type. |
|
Severity level |
6 |
|
Example |
M-LAG/6/M-LAG_GLBCHECK_INCONSISTENCY: Detected global type 1 configuration inconsistency. |
|
Explanation |
Inconsistencies were detected in global type 1 or type 2 configuration. |
|
Recommended action |
If type 1 configuration inconsistencies exist, use the display m-lag consistency command to view the inconsistent settings and modify them on the M-LAG member devices. If type 2 configuration inconsistencies exist, modify the inconsistent settings on the M-LAG member devices. |
M-LAG_IFCHECK_CONSISTENCY
|
Message text |
Finished M-LAG interface [STRING] type [UINT16] configuration consistency check. No inconsistency exists. |
|
Variable fields |
$1: Layer 2 aggregate interface name. $2: Configuration consistency check type. |
|
Severity level |
6 |
|
Example |
M-LAG/6/M-LAG_IFCHECK_CONSISTENCY: Finished M-LAG interface Bridge-Aggregation2 type 1 configuration consistency check. No inconsistency exists. |
|
Explanation |
No inconsistency was detected in type 1 or type 2 configuration of an M-LAG interface. |
|
Recommended action |
No action is required. |
M-LAG_IFCHECK_INCONSISTENCY
|
Message text |
Detected type [UINT16] configuration inconsistency on interface [STRING]. |
|
Variable fields |
$1: Layer 2 aggregate interface name. $2: Configuration consistency check type. |
|
Severity level |
6 |
|
Example |
M-LAG/6/M-LAG_IFCHECK_INCONSISTENCY: Detected type 1 configuration inconsistency on interface Bridge-Aggregation2. |
|
Explanation |
Inconsistencies were detected in type 1 or type 2 configuration of an M-LAG interface. |
|
Recommended action |
If type 1 configuration inconsistencies exist, use the display m-lag consistency command to view the inconsistent settings and modify them on the M-LAG interfaces. If type 2 configuration inconsistencies exist, modify the inconsistent settings on the M-LAG interfaces. |
M-LAG_IFEVT_MLAGIF_BIND
|
Message text |
Interface [STRING] was assigned to M-LAG group [UINT32]. |
|
Variable fields |
$1: Layer 2 aggregate interface name. $2: M-LAG group number. |
|
Severity level |
6 |
|
Example |
M-LAG/6/M-LAG_IFEVT_MLAGIF_BIND: Interface Bridge-Aggregation1 was assigned to M-LAG group 1. |
|
Explanation |
A Layer 2 aggregate interface was assigned to an M-LAG group. |
|
Recommended action |
No action is required. |
M-LAG_IFEVT_MLAGIF_GLOBALDOWN
|
Message text |
The state of M-LAG group [UINT32] changed to down. |
|
Variable fields |
$1: M-LAG group number. |
|
Severity level |
6 |
|
Example |
M-LAG/6/M-LAG_IFEVT_MLAGIF_GLOBALDOWN: The state of M-LAG group 2 changed to down. |
|
Explanation |
An M-LAG group went down because all the member interfaces of its M-LAG interfaces became Unselected. |
|
Recommended action |
Verify that the device and the M-LAG peer use the same system priority and system MAC address, and different system numbers. |
M-LAG_IFEVT_MLAGIF_GLOBALUP
|
Message text |
The state of M-LAG group [UINT32] changed to up. |
|
Variable fields |
$1: M-LAG group number. |
|
Severity level |
6 |
|
Example |
M-LAG/6/M-LAG_IFEVT_MLAGIF_GLOBALUP: The state of M-LAG group 2 changed to up. |
|
Explanation |
An M-LAG group came up because member interfaces of its M-LAG interfaces became Selected for the first time. |
|
Recommended action |
No action is required. |
M-LAG_IFEVT_MLAGIF_MAC_CHG
|
Message text |
Local M-LAG interface [STRING]'s system MAC address changed to [STRING]. Please ensure that the configuration is consistent with that of the peer M-LAG interface. |
|
Variable fields |
$1: Layer 2 aggregate interface name. $2: System MAC address. |
|
Severity level |
6 |
|
Example |
M-LAG/6/M-LAG_IFEVT_MLAGIF_MAC_CHG: Local M-LAG interface Bridge-Aggregation1's system MAC address changed to 2-2-2. Please ensure that the configuration is consistent with that of the peer M-LAG interface. |
|
Explanation |
The system MAC address of an M-LAG interface was modified. |
|
Recommended action |
No action is required. |
M-LAG_IFEVT_MLAGIF_NOSELECTED
|
Message text |
Local M-LAG interface [STRING] in M-LAG group [UINT32] does not have Selected member ports because [STRING]. |
|
Variable fields |
$1: Layer 2 aggregate interface name. $2: M-LAG group number. $3: Cause of the down state of the M-LAG interface: · the aggregate interface went down. Please check the aggregate link status. · no peer M-LAG interface was detected. Please check peer M-LAG interface configuration. · of configuration consistency check failure. Please check the type 1 configuration of the M-LAG member devices for inconsistencies. · it was removed from an M-LAG group. Please reconfigure the M-LAG interface settings as needed. |
|
Severity level |
6 |
|
Example |
M-LAG/6/M-LAG_IFEVT_MLAGIF_NOSELECTED: Local M-LAG interface Bridge-Aggregation1 in M-LAG group 2 does not have Selected member ports because no peer M-LAG interface was detected. Please check peer M-LAG interface configuration. |
|
Explanation |
The local M-LAG interface in an M-LAG group does not have member ports in Selected state. |
|
Recommended action |
Verify that the member ports of the M-LAG interface are correctly configured and connected. |
MLAG_IFEVT_MLAGIF_PEERBIND
|
Message text |
An aggregate interface on the peer M-LAG device was assigned to M-LAG group [UINT32]. |
|
Variable fields |
$1: M-LAG group number. |
|
Severity level |
6 |
|
Example |
MLAG/6/MLAG_IFEVT_MLAGIF_PEERBIND: An aggregate interface on the peer M-LAG device was assigned to M-LAG group 1. |
|
Explanation |
An aggregate interface on the peer M-LAG member device was assigned to an M-LAG group. |
|
Recommended action |
No action is required. |
MLAG_IFEVT_MLAGIF_PEERUNBIND
|
Message text |
An aggregate interface on the peer M-LAG device was removed from M-LAG group [UINT32]. |
|
Variable fields |
$1: M-LAG group number. |
|
Severity level |
6 |
|
Example |
MLAG/6/MLAG_IFEVT_MLAGIF_PEERUNBIND: An aggregate interface on the peer M-LAG device was removed from M-LAG group 1. |
|
Explanation |
An aggregate interface on the peer M-LAG member device was removed from an M-LAG group. |
|
Recommended action |
No action is required. |
M-LAG_IFEVT_MLAGIF_PRIORITY_CHG
|
Message text |
M-LAG interface [STRING]'s system priority changed to [UINT16]. Please ensure that the configuration is consistent with that of the peer M-LAG interface. |
|
Variable fields |
$1: Layer 2 aggregate interface name. $2: New system priority. |
|
Severity level |
6 |
|
Example |
M-LAG/6/M-LAG_IFEVT_MLAGIF_PRIORITY_CHG: M-LAG interface Bridge-Aggregation1's system priority changed to 564. Please ensure that the configuration is consistent with that of the peer M-LAG interface. |
|
Explanation |
The system priority of an M-LAG interface was modified. |
|
Recommended action |
No action is required. |
M-LAG_IFEVT_MLAGIF_SELECTED
|
Message text |
Local M-LAG interface [STRING] in M-LAG group [UINT32] has Selected member ports. |
|
Variable fields |
$1: Layer 2 aggregate interface name. $2: M-LAG group number. |
|
Severity level |
6 |
|
Example |
M-LAG/6/M-LAG_IFEVT_MLAGIF_SELECTED: Local M-LAG interface Bridge-Aggregation1 in M-LAG group 2 has Selected member ports. |
|
Explanation |
The local M-LAG interface has member ports in Selected state. |
|
Recommended action |
No action is required. |
M-LAG_IFEVT_MLAGIF_UNBIND
|
Message text |
Interface [STRING] was removed from M-LAG group [UINT32]. |
|
Variable fields |
$1: Layer 2 aggregate interface name. $2: M-LAG group number. |
|
Severity level |
6 |
|
Example |
M-LAG/6/M-LAG_IFEVT_MLAGIF_UNBIND: Interface Bridge-Aggregation1 was removed from M-LAG group 1. |
|
Explanation |
A Layer 2 aggregate interface was removed from an M-LAG group. |
|
Recommended action |
No action is required. |
MLAG_IFEVT_PEERIF_NOSELECTED
|
Message text |
Peer M-LAG interface in M-LAG group [UINT32] does not have Selected member ports. |
|
Variable fields |
$1: M-LAG group number. |
|
Severity level |
6 |
|
Example |
MLAG/6/MLAG_IFEVT_PEERIF_NOSELECTED: Peer M-LAG interface in M-LAG group 10 does not have Selected member ports. |
|
Explanation |
The peer M-LAG interface in an M-LAG group does not have member ports in Selected state. |
|
Recommended action |
Verify that the member ports of the M-LAG interface are correctly configured and connected. |
MLAG_IFEVT_PEERIF_SELECTED
|
Message text |
Peer M-LAG interface in M-LAG group [UINT32] has Selected member ports. |
|
Variable fields |
$1: M-LAG group number. |
|
Severity level |
6 |
|
Example |
MLAG/6/MLAG_IFEVT_PEERIF_SELECTED: Peer M-LAG interface in M-LAG group 10 has Selected member ports. |
|
Explanation |
The peer M-LAG interface in an M-LAG group has member ports in Selected state. |
|
Recommended action |
No action is required. |
M-LAG_IFEVT_PEERLINK_BIND
|
Message text |
Interface [STRING] was configured as peer-link interface [UINT16]. |
|
Variable fields |
$1: Layer 2 aggregate interface name. $2: Peer-link interface number. |
|
Severity level |
6 |
|
Example |
M-LAG/6/M-LAG_IFEVT_PEERLINK_BIND: Interface Bridge-Aggregation1 was configured as peer-link interface 1. |
|
Explanation |
A Layer 2 aggregate interface was configured as the peer-link interface. |
|
Recommended action |
No action is required. |
M-LAG_IFEVT_PEERLINK_DOWN
|
Message text |
Peer-link interface [STRING] went down because [STRING]. |
|
Variable fields |
$1: Layer 2 aggregate interface name. $2: Cause of the down state of the peer-link interface: · the aggregate interface went down. Please check the aggregate link status. · the tunnel interface went down. Please check the tunnel link status. · no DRCPDUs were received. Please check the devices' DRCPDU transmission and reception status. · the peer failed to receive DRCPDUs. Please check the devices' DRCPDU transmission and reception status. · the peer-link interface role of the interface was removed. Please reconfigure an interface as the peer-link interface. |
|
Severity level |
6 |
|
Example |
M-LAG/6/M-LAG_IFEVT_PEERLINK_DOWN: Peer-link interface Bridge-Aggregation1 went down because the tunnel interface went down. Please check the tunnel link status. |
|
Explanation |
The peer-link interface went down. |
|
Recommended action |
· Verify that the device and the M-LAG peer use the same system priority and system MAC address, and different system numbers. · Verify that the device and the M-LAG peer have the same authentication key and M-LAG sequence number check status. · Verify that the Layer 2 aggregate interface that acts as the peer-link interface is working correctly. |
M-LAG_IFEVT_PEERLINK_UNBIND
|
Message text |
Configuration for peer-link interface [UINT16] was removed from interface [STRING]. |
|
Variable fields |
$1: Peer-link interface number. $2: Layer 2 aggregate interface name. |
|
Severity level |
6 |
|
Example |
M-LAG/6/M-LAG_IFEVT_PEERLINK_UNBIND: Configuration for peer-link interface 1 was removed from interface Bridge-Aggregation1. |
|
Explanation |
The peer-link interface configuration was removed. |
|
Recommended action |
No action is required. |
M-LAG_IFEVT_PEERLINK_UP
|
Message text |
Peer-link interface [STRING] came up. |
|
Variable fields |
$1: Layer 2 aggregate interface name. |
|
Severity level |
6 |
|
Example |
M-LAG/6/M-LAG_IFEVT_PEERLINK_UP: Peer-link interface Bridge-Aggregation1 came up. |
|
Explanation |
The peer-link interface came up because it could receive and send DRCPDUs. |
|
Recommended action |
No action is required. |
MLAG_KEEPALIVEINTERVAL_MISMATCH
|
Message text |
Keepalive interval on the local M-LAG device is different from that on the neighbor. |
|
Variable fields |
N/A |
|
Severity level |
6 |
|
Example |
MLAG/6/MLAG_KEEPALIVEINTERVAL_MISMATCH: Keepalive interval on the local M-LAG device is different from that on the neighbor. |
|
Explanation |
The device and the M-LAG peer use different keepalive intervals. |
|
Recommended action |
Make sure the device and the M-LAG peer use the same keepalive interval. |
M-LAG_KEEPALIVELINK_DOWN
|
Message text |
Keepalive link went down because [STRING]. |
|
Variable fields |
$1: Cause of the down state of the keepalive link and recommended remedy: · keepalive IP address was not configured. Please configure keepalive IP address. · the device failed to send keepalive packets. Please check Layer 3 reachability to the peer. · the local keepalive timeout timer expired. Please check the keepalive packet transmission and reception status at the two ends. · the peer keepalive timeout timer expired. Please check the keepalive packet transmission and reception status at the two ends. |
|
Severity level |
6 |
|
Example |
M-LAG/6/M-LAG_KEEPALIVELINK_DOWN: Keepalive link went down because the local keepalive timeout timer expired. Please check the keepalive packet transmission and reception status at the two ends. |
|
Explanation |
The keepalive link went down. |
|
Recommended action |
· Verify that the role of the device is correct. · Verify that the device and the M-LAG peer use consistent packet source and destination IP addresses for keepalive detection. · Verify Layer 3 connectivity for the keepalive link. |
M-LAG_KEEPALIVELINK_UP
|
Message text |
Keepalive link came up. |
|
Variable fields |
N/A |
|
Severity level |
6 |
|
Example |
M-LAG/6/M-LAG_KEEPALIVELINK_UP: Keepalive link came up. |
|
Explanation |
The keepalive link came up. |
|
Recommended action |
No action is required. |
MLAG_KEEPALIVEPACKETS_FAILED
|
Message text |
Failed to send keepalive packets to the CPU due to [STRING]. |
|
Variable fields |
$1: Cause of the failure to send keepalive packets to the CPU. The cause can only be insufficient device ACL resources. |
|
Severity level |
6 |
|
Example |
MLAG/6/MLAG_KEEPALIVEPACKETS_FAILED: Failed to send keepalive packets to the CPU due to insufficient device ACL resources. |
|
Explanation |
The device failed to send keepalive packets to the CPU because of insufficient device ACL resources. |
|
Recommended action |
Release ACL resources as needed and verify that the keepalive link is operating correctly. |
MLAG_PEERLINK_BLOCK
|
Message text |
The status of peer-link interface [STRING] changed to blocked. |
|
Variable fields |
$1: Layer 2 aggregate interface name. |
|
Severity level |
6 |
|
Example |
MLAG/6/MLAG_PEERLINK_BLOCK: The status of peer-link interface Bridge-Aggregation20 changed to blocked. |
|
Explanation |
The status of the peer-link interface changed to blocked because the device had been assigned a M-LAG role, and the peer-link interface went down. |
|
Recommended action |
· Verify that the peer link is correctly connected and the cable is working correctly. · Verify that the device and the M-LAG peer have correct M-LAG settings. |
MLAG_PEERLINK_UNBLOCK
|
Message text |
The status of peer-link interface [STRING] changed to unblocked. |
|
Variable fields |
$1: Layer 2 aggregate interface name. |
|
Severity level |
6 |
|
Example |
MLAG/6/MLAG_PEERLINK_UNBLOCK: The status of peer-link interface Bridge-Aggregation20 changed to unblocked. |
|
Explanation |
The status of the peer-link interface changed to unblocked because the device had been assigned an M-LAG role, and the peer-link interface came up. |
|
Recommended action |
No action is required. |
M-LAG_SYSEVENT_DEVICEROLE_CHG
|
Message text |
Device role changed from [STRING] to [STRING] for [STRING]. |
|
Variable fields |
$1: Old device role, which can be primary, secondary, or none. $2: New device role, which can be primary, secondary, or none. $3: Reason for the role change: ¡ M-LAG system initialization—The M-LAG system initialized. ¡ peer link down and all M-LAG interfaces down—All M-LAG interfaces were shut down because the peer link failed. ¡ peer link and keepalive link down—Both the peer link and keepalive link failed. ¡ peer link calculation—The role was negotiated over the peer link. ¡ peer link down and role calculation based on keepalive link—The peer link failed and the local role was negotiated over the keepalive link. |
|
Severity level |
6 |
|
Example |
M-LAG/6/M-LAG_SYSEVENT_DEVICEROLE_CHG: Device role changed from Secondary to Primary for peer link calculation. |
|
Explanation |
The M-LAG role of the device changed. |
|
Recommended action |
Examine the reason for the change and take action to recover the peer link or keepalive link if it has failed. |
M-LAG_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 |
M-LAG/6/M-LAG_SYSEVENT_MAC_CHANGE: System MAC address changed from 1-1-1 to 2-2-2. |
|
Explanation |
The M-LAG system MAC address was modified. |
|
Recommended action |
No action is required. |
MLAG_SYSEVENT_MODE_CHANGE
|
Message text |
The device's working mode changed to [STRING]. |
|
Variable fields |
$1: Working mode of the device: · M-LAG system—The device is operating as an M-LAG member device. · standalone—The device is operating as a standalone device. |
|
Severity level |
6 |
|
Example |
MLAG/6/MLAG_SYSEVENT_MODE_CHANGE: The device's working mode changed to standalone. |
|
Explanation |
The working mode of the device changed because the M-LAG system split or reunited. |
|
Recommended action |
No action is required. |
M-LAG_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 |
M-LAG/6/M-LAG_SYSEVENT_NUMBER_CHANGE: System number changed from 1 to 2. |
|
Explanation |
The M-LAG system number was modified. |
|
Recommended action |
No action is required. |
M-LAG_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 |
M-LAG/6/M-LAG_SYSEVENT_PRIORITY_CHANGE: System priority changed from 123 to 564. |
|
Explanation |
The M-LAG system priority was modified. |
|
Recommended action |
No action is required. |
MLAG_VMAC_INEFFECTIVE
|
Message text |
Failed to assign virtual MAC address [STRING] to interface [STRING]. Cause: [STRING]. |
|
Variable fields |
$1: Virtual MAC address. $2: Interface name. This field is available only for VLAN interfaces and loopback interfaces in the current software version. $3: Failure cause, which can only be insufficient hardware resources. |
|
Severity level |
3 |
|
Example |
MLAG/3/MLAG_VMAC_INEFFECTIVE: Failed to assign virtual MAC address 0001-0001-0001 to interface Vlan-interface10. Cause: Insufficient hardware resources. |
|
Explanation |
Failed to assign a virtual MAC address to an interface because of insufficient hardware resources. |
|
Recommended action |
No action is required. |
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. |
MSDP messages
This section contains MSDP messages.
MSDP_PEER_START
|
Message text |
Started a session with peer [STRING]. |
|
Variable fields |
$1: IP address of an MSDP peer. |
|
Severity level |
5 |
|
Example |
MSDP/5/MSDP_PEER_START: Started a session with peer 192.168.0.1. |
|
Explanation |
The device established a session with an MSDP peer. |
|
Recommended action |
No action is required. |
MSDP_PEER_START
|
Message text |
NSR start a session with peer [STRING]. |
|
Variable fields |
$1: IP address of an MSDP peer. |
|
Severity level |
5 |
|
Example |
MSDP/5/MSDP_PEER_START: NSR started a session with peer 192.168.0.1. |
|
Explanation |
NSR recovered the session between the device and an MSDP peer |
|
Recommended action |
No action is required. |
MSDP_PEER_CLOSE
|
Message text |
Stopped a session with peer [STRING]. |
|
Variable fields |
$1: IP address of an MSDP peer. |
|
Severity level |
5 |
|
Example |
MSDP/5/MSDP_PEER_CLOSE: Stopped a session with peer 192.168.0.1. |
|
Explanation |
The device terminated the session with an MSDP peer. |
|
Recommended action |
Verify the MSDP configuration and network connectivity. |
MSDP_SA_LIMIT
|
Message text |
SA from peer [STRING] for ([STRING], [STRING]) exceeded sa-limit of [ULONG]. |
|
Variable fields |
$1: IP address of an MSDP peer. $2: Multicast source address in an SA message. $3: Multicast group address in an SA message. $4: Maximum number of (S, G) entries that can be cached for an MSDP peer. |
|
Severity level |
5 |
|
Example |
MSDP/5/MSDP_SA_LIMIT: SA from peer 192.168.0.1 for (1.1.1.1, 225.0.0.1) exceeded sa-limit of 1000. |
|
Explanation |
The maximum number of (S, G) entries cached for an MSDP peer already reached. |
|
Recommended action |
Verify that the maximum of (S, G) entries that can be cached for an MSDP peer is appropriate. To change the value, use the peer sa-cache-maximum command. |
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. |
NAT messages
This section contains NAT messages.
EIM_MODE_PORT_USAGE_ALARM
|
Message text |
[STRING] Port usage reaches [STRING]%; SrcIPAddr=[IPADDR]; VPNInstance=[STRING]; NATIPAddr=[IPADDR]; ConnectCount=[UINT16]. |
|
Variable fields |
$1: Protocol type. $2: Percentage. $3: Source IP address. $4: Source VPN instance name. $5: Source IP address after translation. $6: Numbers of ports that are assigned. |
|
Severity level |
6 |
|
Example |
NAT/6/EIM_MODE_PORT_USAGE_ALARM: UDP Port usage reaches 40%; SrcIPAddr=1.1.1.211; VPNInstance=-; NATIPAddr=198.1.1.16; ConnectCount=40. |
|
Explanation |
This message is sent in the following conditions: · The port usage in a port block equals or exceeds the threshold set by the nat log port-block port-usage threshold command. · The Endpoint-Independent Mapping mode is applied. |
|
Recommended action |
No action is required. |
NAT_ADDR_BIND_CONFLICT
|
Message text |
Failed to activate NAT configuration on interface [STRING], because global IP addresses already bound to another service card. |
|
Variable fields |
$1: Interface name. |
|
Severity level |
4 |
|
Example |
NAT/4/NAT_ADDR_BIND_CONFLICT: Failed to activate NAT configuration on interface GigabitEthernet1/0/1, because global IP addresses already bound to another service card. |
|
Explanation |
The NAT configuration did not take effect, because the global IP addresses that the interface references have been bound to another service card. |
|
Recommended action |
If multiple interfaces reference the same global IP addresses, you must specify the same service card to process NAT traffic passing through these interfaces. To resolve the problem: 1. Use the display nat all command to check the current configuration. 2. Remove the service card configuration on the interface. 3. Specify the same service card for interfaces referencing the same global IP addresses. |
NAT_EIM
|
Message text |
Protocol(1001)=[STRING];LocalIPAddr(1003)=[IPADDR];LocalPort(1004)=[UINT16];GlobalIPAddr(1005)=[IPADDR];GlobalPort(1006)=[UINT16];RcvVPNInstance(1042)=[STRING];SndVPNInstance(1043)=[STRING];RcvDSLiteTunnelPeer(1040)=[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: Source VPN instance name. $7: Destination VPN instance name. $8: Source DS-Lite tunnel. $9: Time when the EIM entry was created. $10: Time when the EIM entry was removed. $11: Event type. Available values are 1 and 8. $12: Event description: ¡ NAT EIM entry created: A NAT EIM entry was created. The value for the event type field is 8. ¡ NAT EIM entry deleted: A NAT EIM entry was deleted. The value for the event type field is 1. |
|
Severity level |
6 |
|
Example |
NAT/6/NAT_EIM: -Protocol(1001)=UDP;LocalIPAddr(1003)=1.1.1.2;LocalPort(1004)=1024;GlobalIPAddr(1005)=30.3.1.231;GlobalPort(1006)=1026;RcvVPNInstance(1042)=;SndVPNInstance(1043)=;RcvDSLiteTunnelPeer(1040)=;BeginTime_e(1013)=10261971001739;EndTime_e(1014)=;Event(1048)=(8)NAT EIM entry created; |
|
Explanation |
This message is sent when a NAT EIM entry is created or removed. |
|
Recommended action |
No action is required. |
NAT_FLOW
|
Message text |
Protocol(1001)=[STRING];Application(1002)=[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];VlanID(1175)=[UINT16];VNI(1213)=[UINT32]; |
|
Variable fields |
$1: Protocol type. $2: Application layer protocol. $3: Source IP address. $4: Source port number. $5: Source IP address after translation. $6: Source port number after translation. $7: Destination IP address. $8: Destination port number. $9: Destination IP address after translation. $10: Destination port number after translation. $11: Total number of incoming packets. $12: Total number of incoming bytes. $13: Total number of outgoing packets. $14: Total number of outgoing bytes. $15: Source VPN instance name. $16: Destination VPN instance name. $17: Source DS-Lite tunnel. $18: Destination DS-Lite tunnel. $19: Time when the session is created. $20: Time when the session is removed. $21: Event type. Available values are 1, 2, 3, 6, 8, and 254. $22: Event description: ¡ Session created. The value for the event type field is 8. ¡ Active data flow timeout The value for the event type field is 6. ¡ Normal over. The value for the event type field is 1. ¡ Aged for timeout. The value for the event type field is 2. ¡ Aged for reset or config-change. The value for the event type field is 3. ¡ Other. The value for the event type field is 254. $23: ID of the VLAN to which the session belongs. $24: ID of the VXLAN to which the session belongs. |
|
Severity level |
6 |
|
Example |
NAT/6/NAT_FLOW: Protocol(1001)=UDP;Application(1002)=other;SrcIPAddr(1003)=1.1.1.2;SrcPort(1004)=1024;NatSrcIPAddr(1005)=30.3.1.231;NatSrcPort(1006)=1026;DstIPAddr(1007)=2.1.1.2;DstPort(1008)=1024;NatDstIPAddr(1009)=2.1.1.2;NatDstPort(1010)=1024;InitPktCount(1044)=1;InitByteCount(1046)=110;RplyPktCount(1045)=0;RplyByteCount(1047)=0;RcvVPNInstance(1042)=;SndVPNInstance(1043)=;RcvDSLiteTunnelPeer(1040)=;SndDSLiteTunnelPeer(1041)=;BeginTime_e(1013)=03232019091640;EndTime_e(1014)=;Event(1048)=(8)Session created;VlanID(1175)=--;VNI(1213)=--; |
|
Explanation |
This message is sent in one of the following conditions: · A NAT session is created or removed. · Regularly during a NAT session. · The traffic threshold or aging time of a NAT session is reached. |
|
Recommended action |
No action is required. |
NAT_SERVER_INVALID
|
Message text |
The NAT server with Easy IP is invalid because its global settings conflict with that of another NAT server on this interface. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
NAT/4/NAT_SERVER_INVALID: The NAT server with Easy IP is invalid because its global settings conflict with that of another NAT server on this interface. |
|
Explanation |
The NAT Server with Easy IP did not take effect because its global settings conflict with that the global settings of another NAT Server on the same interface. |
|
Recommended action |
Modify the NAT Server configuration on the interface. The combination of protocol type, global IP addresses and global ports must be unique for each NAT Server on the same interface. |
NAT_SERVICE_CARD_RECOVER_FAILURE
|
Message text |
Pattern 1: Failed to recover the configuration of binding the service card on slot [UINT16] to interface [STRING], because [STRING]. Pattern 2: Failed to recover the configuration of binding the service card on chassis [UINT16] slot [UINT16] to interface [STRING], because [STRING]. |
|
Variable fields |
Pattern 1: $1: Slot number. $2: Interface name. $3: Reasons why restoring the binding between the service card and the interface fails. Pattern 2: $1: Chassis number. $2: Slot number. $3: Interface name. $4: Reasons why restoring the binding between the service card and the interface fails. |
|
Severity level |
4 |
|
Example |
NAT/4/NAT_SERVICE_CARD_RECOVER_FAILURE: Failed to recover the configuration of binding the service card on chassis 2 slot 3 to interface Ethernet0/0/2, because NAT service is not supported on this service card. |
|
Explanation |
Restoring the binding between the service card and the interface failed. |
|
Recommended action |
· If the operation fails because the NAT addresses have already been bound to another service card: ¡ Use the display nat all command to check the current configuration. ¡ Specify the same service card for interfaces referencing the same NAT addresses. · Check the service card for hardware problems if the failure is caused by one of the following reasons: ¡ NAT service is not supported on this service card. ¡ The hardware resources are not enough. ¡ Unknown error. |
NAT444_SYSLOG
|
Message text |
Failed to allocate port blocks from address group [UINT16]. |
|
Variable fields |
$1: Address group. |
|
Severity level |
6 |
|
Example |
NAT/6/NAT444_SYSLOG: Failed to allocate port blocks from address group 3. |
|
Explanation |
This message is sent when NAT444 port block assignment fails. |
|
Recommended action |
No action is required. |
PORT_USAGE_ALARM
|
Message text |
Port usage reaches [STRING]%; SrcIPAddr=[IPADDR]; VPNInstance=[STRING]; NATIPAddr=[IPADDR]; ConnectCount=[UINT16]. |
|
Variable fields |
$1: Percentage. $2: Source IP address. $3: Source VPN instance name. $4: Source IP address after translation. $5: Numbers of ports that are assigned. |
|
Severity level |
6 |
|
Example |
NAT/6/PORT_USAGE_ALARM: Port usage reaches 40%; SrcIPAddr=1.1.1.211; VPNInstance=-; NATIPAddr=16.1.1.198; ConnectCount=40. |
|
Explanation |
This message is sent in the following conditions: · The port usage in a port block equals or exceeds the threshold set by the nat log port-block port-usage threshold command. · The Connection-Dependent Mapping mode is applied. |
|
Recommended action |
No action is required. |
PORTBLOCK_ALARM
|
Message text |
Address group [UINT16]; total port blocks [UINT16]; active port blocks [UINT16]; usage over [UINT16]%. |
|
Variable fields |
$1: Address group. $2: Total number of port blocks. $3: Numbers of port blocks that are allocated. $4: Port block usage. |
|
Severity level |
6 |
|
Example |
NAT/6/PORTBLOCK_ALARM: Address group 3; total port blocks 16575; active port blocks 6630; usage over 40%. |
|
Explanation |
This message is sent when the port block usage equals or exceeds the threshold set by the nat log port-block usage threshold command. |
|
Recommended action |
No action is required. |
PORTBLOCKGRP_MEMORY_WARNING
|
Message text |
Insufficient memory caused by excessive public addresses in port block group [UINT16]. Please reconfigure the public address space. |
|
Variable fields |
$1: NAT port block group ID. |
|
Severity level |
4 |
|
Example |
NAT/4/PORTBLOCKGRP_MEMORY_WARNING: Insufficient memory caused by excessive public addresses in port block group 1. Please reconfigure the public address space. |
|
Explanation |
This message is sent when a public address range in a NAT port block group is too large and causes insufficient memory. |
|
Recommended action |
Reconfigure the public address range. |
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_LOCALPROXY_ENABLE_FAILED
|
Message text |
Failed to enable local ND proxy on interface [STRING]. |
|
Variable fields |
$1: Interface name. |
|
Severity level |
4 |
|
Example |
ND/4/ND_LOCALPROXY_ENABLE_FAILED: -MDC=1-Slot=2; Failed to enable local ND proxy on interface Vlan-interface 1. |
|
Explanation |
Failed to enable local ND proxy on an interface on the card. |
|
Recommended action |
· Verify that the card supports local ND proxy. · Make sure the device has sufficient hardware resources. |
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_RAGUARD_DROP
|
Message text |
Dropped RA messages with the source IPv6 address [STRING] on interface [STRING]. [STRING] messages dropped in total on the interface. |
|
Variable fields |
$1: IPv6 source IP address of the dropped RA messages. $2: Interface name on which the RA messages are dropped. $3: Total number of dropped RA messages on the interface. |
|
Severity level |
4 |
|
Example |
ND/4/ND_RAGUARD_DROP: Dropped RA messages with the source IPv6 address FE80::20 on interface GigabitEthernet1/0/1. 20 RA messages dropped in total on the interface. |
|
Explanation |
RA guard dropped RA messages and displayed the information when RA guard detected an attack. |
|
Recommended action |
Verify the validity of the RA message originator. |
ND_RATE_EXCEEDED
|
Message text |
The ND packet rate ([UINT32] pps) exceeded the rate limit ([UINT32] pps) on interface [STRING] in most recent [UINT32] seconds. |
|
Variable fields |
$1: ND packet rate. $2: ND limit rate. $3: Interface name. $4: Interval time. |
|
Severity level |
4 |
|
Example |
ND/4/ND_RATE_EXCEEDED: The ND packet rate (100 pps) exceeded the rate limit (80 pps) on interface GigabitEthernet1/0/1 in most recent 10 seconds. |
|
Explanation |
An interface received ND messages at a rate higher than the rate limit. |
|
Recommended action |
Verify that the hosts at the sender IP addresses are legitimate. |
ND_RATELIMIT_NOTSUPPORT
|
Message text |
Pattern 1: ND packet rate limit is not support on slot [INT32]. Pattern 2: ND 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 |
ND/6/ND_RATELIMIT_NOTSUPPORT: ND packet rate limit is not support on slot 2. |
|
Explanation |
ND packet rate limit is not supported on the slot. |
|
Recommended action |
No action is required. |
ND_SET_PORT_TRUST_NORESOURCE
|
Message text |
Not enough resources to complete the operation. |
|
Variable fields |
N/A |
|
Severity level |
6 |
|
Example |
ND/6/ND_SET_PORT_TRUST_NORESOURCE: Not enough resources to complete the operation. |
|
Explanation |
Failed to execute the command because driver resources were not enough. |
|
Recommended action |
Release the driver resources and execute the command again. |
ND_SET_VLAN_REDIRECT_NORESOURCE
|
Message text |
Not enough resources to complete the operation. |
|
Variable fields |
N/A |
|
Severity level |
6 |
|
Example |
ND/6/ND_VLAN_REDIRECT_NORESOURCE: Not enough resources to complete the operation. |
|
Explanation |
Failed to execute the command because driver resources were not enough. |
|
Recommended action |
Release the driver resources and execute the command again. |
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. |
EDIT_CONFIG_CLI
|
Message text |
User ([STRING], [STRING], session ID [UINT16]), message ID=[UINT16], row index=[UINT16], command=[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 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: Row index in the NETCONF request. $6: Commands for the operations in the NETCONF request. $7: Error message returned upon failed NETCONF row operations. The error message is Configuration failed. The device does not return this message if all operations in the request are executed successfully. |
|
Severity level |
6 |
|
Example |
XMLSOAP/6/EDIT_CONFIG_CLI: User (test, 192.168.100.20, session ID 1), message ID=100, row index=1, command=port trunk pvid vlan 100. |
|
Explanation |
If the XML-to-CLI feature for NETCONF logging is enabled, the device converts every <action> and <edit-config> operation from their XML forms to their CLI command forms and logs the CLI commands for the operations. This log also records the operation results. This log is available only for <action> and <edit-config> operations. |
|
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_ENTRY_PROBE_RESULT
|
Message text |
Reaction entry [STRING] of NQA entry admin-name [STRING] operation-tag [STRING]: [STRING]. |
|
Variable fields |
$1: ID of the NQA reaction entry. The value range is 1 to 10. $2: Admin name of the NQA entry. $3: Operation tag of the NQA entry. $4: Test result. The value can be: ¡ Probe-pass: Succeeded. ¡ Probe-fail: Failed. |
|
Severity level |
6 |
|
Example |
NQA/6/NQA_ENTRY_PROBE_RESULT Reaction entry 1 of NQA entry admin-name 1 operation-tag 1: Probe-pass. |
|
Explanation |
A change in the monitoring result of an NQA reaction entry was detected. |
|
Recommended action |
If the test result is Probe-fail, check the network environment. |
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. |
NQA_TWAMP_LIGHT_PACKET_INVALID
|
Message text |
NQA TWAMP Light test session [UINT32] index [UINT32]: The number of packets captured for statistics collection is invalid. |
|
Variable fields |
$1: Test session ID. $2: Serial number of the statistics data. |
|
Severity level |
6 |
|
Example |
NQA/6/ NQA_TWAMP_LIGHT_PACKET_INVALID: NQA TWAMP Light test session 1 index 7: The number of packets captured for statistics collection is invalid. |
|
Explanation |
The number of probe packets was invalid in the TWAMP Light test because the test collection interval was shorter than the packet sending interval. |
|
Recommended action |
Verify that the test collection interval is no less than the packet sending interval. |
NQA_TWAMP_LIGHT_REACTION
|
Message text |
NQA TWAMP Light test session [UINT32] reaction entry [UINT32]: Detected continual violation of the [STRING] [STRING] threshold for a threshold violation monitor time of [UINT32] ms. |
|
Variable fields |
$1: Test session ID. $2: Reaction entry ID. $3: Reaction entry type: · Two-way delay. · Two-way loss. · Two-way jitter. $4: Threshold violation value: · upper—Be equal to or greater than the upper threshold limit. · lower—Be equal to or less than the lower threshold limit. $5: Statistics collection interval. |
|
Severity level |
6 |
|
Example |
NQA/6/NQA_TWAMP_LIGHT_REACTION: NQA TWAMP Light test session 1 reaction entry 1: Detected continual violation of the two-way loss upper threshold for a threshold violation monitor time of 2000 ms. |
|
Explanation |
In a TWAMP test, the device monitors the test result, and starts the monitoring time when either of the following conditions is met: · The monitoring result goes beyond the upper threshold limit. · The monitoring result drops below the lower threshold limit from a monitoring result higher than the lower limit. If either condition is always true during the monitoring time, a threshold violation occurs. |
|
Recommended action |
No action is required. |
NQA_TWAMP_LIGHT_START_FAILURE
|
Message text |
NQA TWAMP Light test session [UINT32]: Failed to start the test session. Please check the parameters. |
|
Variable fields |
$1: Test session ID. |
|
Severity level |
6 |
|
Example |
NQAS/6/NQA_TWAMP_LIGHT_START_FAILURE: NQA TWAMP Light test session 1: Failed to start the test session, Please check the parameters. |
|
Explanation |
This message is sent when the TWAMP Light responder failed to start the test session. The message asks you to examine the parameter settings. |
|
Recommended action |
1. Execete the display this command to examine the parameter settings of the test-session command. 2. Re-execute the test-session command with the required parameters according to your network requirements. |
NQA_UPF_UE_PROBE
|
Message text |
Reaction entry [STRING] of NQA operation with administrator name [STRING] and operation tag [STRING] exceeded the threshold. Delay information between UPF and UE: · Round trip time [UINT32] us · UPF network to station two-way delay [UINT32] us · Downlink GTPU delay [UINT32] us · Uplink GTPU delay [UINT32] us · Downlink PDCP delay [UINT32] us · Uplink PDCP delay [UINT32] us · Donwlink RLC delay [UINT32] us · Uplink RLC delay [UINT32] us · Downlink MAC delay [UINT32] us · Uplink MAC delay [UINT32] us |
|
Variable fields |
$1: Reaction entry ID, in the range of 1 to 10. $2: Administrator name of the NQA operation. $3: Operation tag. $4: Round-trip time of the probe packet between the UPF and UE, in microseconds. $5: Round-trip time of the probe packet between the UPF and base station, in microseconds. $6: Time taken for the uplink packet to enter and leave the GTP-U layer of the base station, in microseconds. $7: Time taken for the downlink packet to enter and leave the GTP-U layer of the base station, in microseconds. $8: Time taken for the uplink packet to enter and leave the PDCP layer of the base station, in microseconds. $9: Time taken for the downlink packet to enter and leave the PDCP layer of the base station, in microseconds. $10: Time taken for the uplink packet to enter and leave the RLC layer of the base station, in microseconds. $11: Time taken for the downlink packet to enter and leave the RLC layer of the base station, in microseconds. $12: Time taken for the uplink packet to enter and leave the MAC layer of the base station, in microseconds. $13: Time taken for the downlink packet to enter and leave the MAC layer of the base station, in microseconds. |
|
Severity level |
6 |
|
Example |
NQA/6/NQA_UPF_UE_PROBE: Reaction entry 1 of NQA operation with administrator name 1 and operation tag 1 exceeded the threshold. Delay information between UPF and UE: · Round trip time 1500 us · UPF network to station two-way delay 1000 us · Downlink GTPU delay 35 us · Uplink GTPU delay 35 us · Downlink PDCP delay 35 us · Uplink PDCP delay 35 us · Donwlink RLC delay 35 us · Uplink RLC delay 35 us · Downlink MAC delay 35 us · Uplink MAC delay 35 us |
|
Explanation |
This message is sent when delay probing between the UPF and UE is enabled and the result reaches the configured threshold. |
|
Recommended action |
1. Execete the display nqa statistics command in any view to view the round-trip time between the UPF and UE. If the value of a parameter in the terminal display exceeds the empirical threshold range, proceed to the next step to locate and troubleshoot the issue. 2. Execute the display current-configuration | include "upf-ue-rtt threshold-value" command in any view to view the reaction entry for monitoring the packet round-trip time between the UPF and UE. If the configured threshold value is inappropriate, execute the reaction checked-element upf-ue-rtt command in ICMP echo operation view to configure a new one. 3. If the issue persists, collect alarm information and configuration data, and then contact H3C Support. |
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/2019 to 02:29:12 12/28/2019, 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 |
1. Verify the NTP server and network connection. 2. 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. 3. 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 |
|
|
Variable fields |
$1: Instance ID. $2: Controller ID. $3: Rule ID. $4: XID. $5: Cookie. $6: Table ID. |
|
Severity level |
5 |
|
Example |
|
|
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 |
|
|
Explanation |
A flow entry was deleted due to a group modification message. |
|
Recommended action |
No action is required. |
OFP_FLOW_RMV_HARDTIME
|
Message text |
|
|
Variable fields |
$1: Rule ID. $2: Table ID. $3: Instance ID. |
|
Severity level |
5 |
|
Example |
|
|
Explanation |
A flow entry was deleted because of a hard time expiration. |
|
Recommended action |
No action is required. |
OFP_FLOW_RMV_IDLETIME
|
Message text |
|
|
Variable fields |
$1: Rule ID. $2: Table ID. $3: Instance ID. |
|
Severity level |
5 |
|
Example |
|
|
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 |
|
|
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 |
|
|
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 |
|
|
Variable fields |
$1: Table ID. $2: Instance ID. |
|
Severity level |
5 |
|
Example |
|
|
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 |
|
|
Variable fields |
$1: Table ID. $2: Instance ID. |
|
Severity level |
5 |
|
Example |
|
|
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 |
|
|
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. |
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] (Transceiver Type=STRING): [STRING] was removed. |
|
Variable fields |
$1: Interface type and number. $2: Transceiver module type. $3: Fault type. |
|
Severity level |
5 |
|
Example |
OPTMOD/5/MOD_ALM_OFF: GigabitEthernet1/0/1 (Transceiver Type=1000_BASE_T_AN_SFP): 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] (Transceiver Type=STRING): [STRING] was detected. |
|
Variable fields |
$1: Interface type and number. $2: Transceiver module type. $3: Fault type. |
|
Severity level |
5 |
|
Example |
OPTMOD/5/MOD_ALM_ON: GigabitEthernet1/0/1 (Transceiver Type=1000_BASE_T_AN_SFP): Module_not_ready was detected. |
|
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: Transceiver absent. |
|
Explanation |
The transceiver module was removed. |
|
Recommended action |
No action is required. |
OPTICAL_WARNING_CLEAR
|
Message text |
Transceiver warning alarm cleared. (PhysicalIndex=<[UINT]>, PhysicalName=<[STRING]>, RelativeResource=<[STRING]>, ErrorCode=<[UINT]>, Reason=<[STRING]>) |
|
Variable fields |
$1: Entity index. $2: Entity name. $3: Fault location. $4: Error code. $5: Reason for the fault. |
|
Severity level |
4 |
|
Example |
OPTMOD/4/OPTICAL_WARNING_CLEAR: Transceiver warning alarm cleared. (PhysicalIndex=8833, PhysicalName=HGE1/3/0/7, RelativeResource=1/3/0, ErrorCode=600060, Reason=Transceiver RXCDR_unlock detected. Lane = 1.) |
|
Explanation |
A warning alarm for the specified transceiver module was cleared. |
|
Recommended action |
No action is required. |
OPTICAL_WARNING_OCCUR
|
Message text |
Transceiver warning alarm occurred. (PhysicalIndex=<[UINT]>, PhysicalName=<[STRING]>, RelativeResource=<[STRING]>, ErrorCode=<[UINT]>, Reason=<[STRING]>) |
|
Variable fields |
$1: Entity index. $2: Entity name. $3: Fault location. $4: Error code. $5: Reason for the fault. |
|
Severity level |
4 |
|
Example |
OPTMOD/4/OPTICAL_WARNING_OCCUR: Transceiver warning alarm occurred. (PhysicalIndex=8833, PhysicalName=HGE1/3/0/7, RelativeResource=1/3/0, ErrorCode=600060, Reason=Transceiver RXCDR_unlock detected. Lane = 1.) |
|
Explanation |
A warning alarm occurred for the specified transceiver module. |
|
Recommended action |
1. Ensure secure connection between the transceiver module and optical fiber. 2. Remove and reinstalled transceiver into the port. 3. Make sure the card is operating correctly. 4. Resolve the issue based on the error code. 5. If the issue persists, contact the technical support. |
OPTMOD_COUNTERFEIT_MODULE
|
Message text |
The following transceiver you are using is suspected to be a counterfeit/pirated/unauthorized H3C transceiver, which might cause compatibility problems and expose your device to security threats. Please contact H3C for further detection and verification promptly. [STRING]: Transceiver type [STRING], SN [STRING]. |
|
Variable fields |
$1: Interface type and number. $2: Transceiver type. $3: Transceiver sequence number. |
|
Severity level |
3 |
|
Example |
OPTMOD/3/OPTMOD_COUNTERFEIT_MODULE: The following transceiver you are using is suspected to be a counterfeit/pirated/unauthorized H3C transceiver, which might cause compatibility problems and expose your device to security threats. Please contact H3C for further detection and verification promptly. GigabitEthernet1/0/1: Transceiver type 1000_BASE_SX_SFP, SN 2013AYU0711103. GigabitEthernet1/0/2: Transceiver type 1000_BASE_SX_SFP, SN 2013AYU0711103. |
|
Explanation |
This log is generated when a probably counterfeit/pirated/unauthorized H3C transceiver module is detected. For a counterfeit/pirated/unauthorized H3C transceiver module, you cannot obtain any data from the display transceiver diagnosis command. |
|
Recommended action |
Contact Technical Support. |
OPTMOD_MODULE_CHECK
|
Message text |
An H3C transceiver is detected. Please go to the website www.h3c.com to verify its authenticity. |
|
Variable fields |
N/A |
|
Severity level |
6 |
|
Example |
OPTMOD/6/OPTMOD_MODULE_CHECK: An H3C transceiver is detected. Please go to the website www.h3c.com to verify its authenticity. |
|
Explanation |
The log is generated when an H3C transceiver module is detected. It reminds the user to verify the authenticity of the transceiver module from the H3C website (www.h3c.com). |
|
Recommended action |
No action is required. |
PHONY_MODULE
|
Message text |
[STRING]: A non-H3C transceiver is detected. Please confirm the label of the transceiver. If there is an H3C Logo, it is suspected to be a counterfeit H3C transceiver. This transceiver is NOT sold by H3C. H3C therefore shall NOT guarantee the normal function of the device or assume the maintenance responsibility thereof! |
|
Variable fields |
$1: Interface type and number. |
|
Severity level |
4 |
|
Example |
OPTMOD/4/PHONY_MODULE: GigabitEthernet1/0/1: A non-H3C transceiver is detected. Please confirm the label of the transceiver. If there is an H3C Logo, it is suspected to be a counterfeit H3C transceiver. This transceiver is NOT sold by H3C. H3C therefore shall NOT guarantee the normal function of the device or assume the maintenance responsibility thereof! |
|
Explanation |
This log is generated when a non-H3C transceiver module is detected. |
|
Recommended action |
Purchase and use genuine H3C transceiver modules for the device. |
RX_ALM_OFF
|
Message text |
[STRING] (Transceiver Type=STRING): [STRING] was removed. |
|
Variable fields |
$1: Interface type and number. $2: Transceiver module type. $3: RX fault type. |
|
Severity level |
5 |
|
Example |
OPTMOD/5/RX_ALM_OFF: GigabitEthernet1/0/1 (Transceiver Type=1000_BASE_T_AN_SFP): 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] (Transceiver Type=STRING): [STRING] was detected. |
|
Variable fields |
$1: Interface type and number. $2: Transceiver module type. $3: RX fault type. |
|
Severity level |
5 |
|
Example |
OPTMOD/5/RX_ALM_ON: GigabitEthernet1/0/1 (Transceiver Type=Unknown): 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] (Transceiver Type=STRING): [STRING] was removed. |
|
Variable fields |
$1: Interface type and number. $2: Transceiver module type. $3: TX fault type. |
|
Severity level |
5 |
|
Example |
OPTMOD/5/TX_ALM_OFF: GigabitEthernet1/0/1 (Transceiver Type=1000_BASE_T_AN_SFP): 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] (Transceiver Type=STRING): [STRING] was detected. |
|
Variable fields |
$1: Interface type and number. $2: Transceiver module type. $3: TX fault type. |
|
Severity level |
5 |
|
Example |
OPTMOD/5/TX_ALM_ON: GigabitEthernet1/0/1 (Transceiver Type=1000_BASE_T_AN_SFP): 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: · insufficient hardware resources. · unsupported operations. · insufficient hardware resources and unsupported operations. |
|
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 |
PFILTER/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_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_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 |
PFILTER/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_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. 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. 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. |
PKTCPT
This section contains packet capture messages.
PKTCPT_AP_OFFLINE
|
Message text |
Failed to start packet capture. Reason: AP was offline. |
|
Variable fields |
N/A |
|
Severity level |
6 |
|
Example |
PKTCPT/6/PKTCPT_AP_OFFLINE: Failed to start packet capture. Reason: AP was offline. |
|
Explanation |
Packet capture failed to start because the AP configured with packet capture was offline. |
|
Recommended action |
1. Verify the AP configuration, and restart packet capture after the AP comes online. 2. If the issue persists, contact H3C Support. |
PKTCPT_AREADY_EXIT
|
Message text |
Failed to start packet capture. Reason: The AP was uploading frames captured during the previous capturing operation. |
|
Variable fields |
N/A |
|
Severity level |
6 |
|
Example |
PKTCPT/6/PKTCPT_AREADY_EXIT: Failed to start packet capture. Reason: The AP was uploading frames captured during the previous capturing operation. |
|
Explanation |
This message occurs if you restart packet capture while the fit AP is till uploading the captured frames after the previous packet capturing operation stopped on the AC. |
|
Recommended action |
1. Restart packet capture later. 2. If the issue persists, contact H3C Support. |
PKTCPT_CONN_FAIL
|
Message text |
Failed to start packet capture. Reason: Failed to connect to the FTP server. |
|
Variable fields |
N/A |
|
Severity level |
6 |
|
Example |
PKTCPT/6/PKTCPT_CONN_FAIL: Failed to start packet capture. Reason: Failed to connect to the FTP server. |
|
Explanation |
Packet capture failed to start because the device failed to connect to the FTP server in the same network segment. |
|
Recommended action |
1. Verify that the URL of the FTP server is
valid. 2. Verify that the domain name can be resolved successfully. 3. Verify that the FTP server is reachable. 4. Verify that the FTP server is online. 5. If the issue persists, contact H3C Support. |
PKTCPT_INVALID_FILTER
|
Message text |
Failed to start packet capture. Reason: Invalid expression for matching packets to be captured. |
|
Variable fields |
N/A |
|
Severity level |
6 |
|
Example |
PKTCPT/6/PKTCPT_INVALD_FILTER: Failed to start packet capture. Reason: Invalid expression for matching packets to be captured. |
|
Explanation |
Packet capture failed to start because the capture filter expression was invalid. |
|
Recommended action |
1. Correct the capture filter expression. 2. If the issue persists, contact H3C Support. |
PKTCPT_LOGIN_DENIED
|
Message text |
Packet capture aborted. Reason: FTP server login failure. |
|
Variable fields |
N/A |
|
Severity level |
6 |
|
Example |
PKTCPT/6/PKTCPT_LOGIN_DENIED: Packet capture aborted. Reason: FTP server login failure. |
|
Explanation |
Packet capture stopped because the user failed to log in to the FTP server. |
|
Recommended action |
1. Verify the username and password. 2. If the issue persists, contact H3C Support. |
PKTCPT_MEMORY_ALERT
|
Message text |
Packet capture aborted. Reason: Memory threshold reached. |
|
Variable fields |
N/A |
|
Severity level |
6 |
|
Example |
PKTCPT/6/PKTCPT_MEMORY_ALERT: Packet capture aborted. Reason: Memory threshold reached. |
|
Explanation |
Packet capture stopped because the memory threshold was reached. |
|
Recommended action |
N/A |
PKTCPT_OPEN_FAIL
|
Message text |
Failed to start packet capture. Reason: File for storing captured frames not opened. |
|
Variable fields |
N/A |
|
Severity level |
6 |
|
Example |
PKTCPT/6/PKTCPT_OPEN_FAIL: Failed to start packet capture. Reason: File for storing captured frames not opened. |
|
Explanation |
Packer capture failed to start because the file for storing the captured frames cannot open. |
|
Recommended action |
1. Verify that the user has the write permission to the file. 2. If the user does not have the write permission, assign the permission to the user. 3. Verify that the specified file has been created and is not used by another feature. 4. If the file is used by another feature, use another file. 5. If the issue persists, contact H3C Support. |
PKTCPT_OPERATION_TIMEOUT
|
Message text |
Failed to start or continue packet capture. Reason: Operation timed out. |
|
Variable fields |
N/A |
|
Severity level |
6 |
|
Example |
PKTCPT/6/PKTCPT_OPERATION_TIMEOUT: Failed to start or continue packet capture. Reason: Operation timed out. |
|
Explanation |
If the FTP server is on a different subnet than the device, this message is generated when one of the following events occurs: · Packet capture failed to start because the FTP server was unreachable and the connection timed out. · Packet capture stopped because the FTP server was offline and uploading the captured frames timed out. |
|
Recommended action |
1. Verify that the FTP server is reachable. 2. Verify that the FTP server is online. 3. If the issue persists, contact H3C Support. |
PKTCPT_SERVICE_FAIL
|
Message text |
Failed to start packet capture. Reason: TCP or UDP port binding faults. |
|
Variable fields |
N/A |
|
Severity level |
6 |
|
Example |
PKTCPT/6/PKTCPT_SERVICE_FAIL: Failed to start packet capture. Reason: TCP or UDP port binding faults. |
|
Explanation |
Packet capture failed to start because of a TCP or UDP port binding issue, such as a port binding conflict. |
|
Recommended action |
1. Verify that Wireshark has been closed before you start packet capture. 2. If it is not closed, close Wireshark, and then restart packet capture. 3. Bind a new TCP or UDP port, and then restart packet capture. 4. If the issue persists, contact H3C Support. |
PKTCPT_UNKNOWN_ERROR
|
Message text |
Failed to start or continue packet capture. Reason: Unknown error. |
|
Variable fields |
N/A |
|
Severity level |
6 |
|
Example |
PKTCPT/6/PKTCPT_UNKNOWN_ERROR: Failed to start or continue the packet capture. Reason: Unknown error. |
|
Explanation |
Packet capture failed to start or packet capture stopped because of an unknown error. |
|
Recommended action |
N/A |
PKTCPT_UPLOAD_ERROR
|
Message text |
Packet capture aborted. Reason: Failed to upload captured frames. |
|
Variable fields |
N/A |
|
Severity level |
6 |
|
Example |
PKTCPT/6/PKTCPT_UPLOAD_ERROR: Packet capture aborted. Reason: Failed to upload captured frames. |
|
Explanation |
Packet capture stopped because the capture failed to upload the captured frames. |
|
Recommended action |
1. Make sure the FTP working directory is correct. 2. Verify that the user has the write permission to the file on the FTP server. 3. Verify that the FTP server is online. 4. Verify that the FTP server is reachable. 5. Verify that the FTP server has sufficient memory space. 6. Do not stop packet capture while the device uploading captured frames. 7. If the issue persists, contact H3C Support. |
PKTCPT_WRITE_FAIL
|
Message text |
Packet capture aborted. Reason: Not enough space to store captured frames. |
|
Variable fields |
N/A |
|
Severity level |
6 |
|
Example |
PKTCPT/6/PKTCPT_WRITE_FAIL: Packet capture aborted. Reason: Not enough space to store captured frames. |
|
Explanation |
Packet capture stopped because the memory space is not enough for storing captured frames. |
|
Recommended action |
1. Delete unnecessary files to release storage space. 2. If the issue persists, contact H3C Support. |
Portal messages
This section contains portal messages.
PORTAL_USER_LOGOFF
|
Message text |
UserName=[STRING], IPAddr=[IPADDR], IfName=[STRING], OuterVLAN=[UINT16], InnerVLAN=[UINT16], MACAddr=[MAC], Reason=[STRING], Input Octets=[UINT32], Output Octets=[UINT32], Input Gigawords=[UINT32], Output Gigawords=[UINT32], IPv6Input Octets=[UINT32], IPv6Output Octets=[UINT32], IPv6 Input Gigawords=[UINT32], IPv6Output Gigawords=[UINT32], SessionTime=[UINT32]; 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: Reason for user offline, see Table 12. $8: Statistics of the user's upstream IPv4 traffic, in bytes. $9: Statistics of the user's downstream IPv4 traffic, in bytes. $10: Statistics of the user's upstream IPv4 traffic. The measurement unit is 4G bytes. $11: Statistics of the user's downstream IPv4 traffic. The measurement unit is 4G bytes. $12: Statistics of the user's upstream IPv6 traffic, in bytes. $13: Statistics of the user's downstream IPv6 traffic, in bytes. $14: Statistics of the user's upstream IPv6 traffic. The measurement unit is 4G bytes. $15: Statistics of the user's downstream IPv6 traffic. The measurement unit is 4G bytes. $16: Online duration of the user, in seconds. |
|
Severity level |
6 |
|
Example |
PORTAL/6/PORTAL_USER_LOGOFF: -MDC=1; UserName=abc, IPAddr=1.1.1.2, IfName=Route-Aggregation1023.4000, OuterVLAN=N/A, InnerVLAN=4000, MACAddr=0230-0103-5601, Reason=User request, Input Octets=100, Output Octets=200, Input Gigawords=100, Output Gigawords=200, IPv6Input Octets=100, IPv6Output Octets=200, IPv6Input Gigawords=100, IPv6Output Gigawords=200, SessionTime=200; User logged off. |
|
Explanation |
A portal user went offline. Whether IPv6-related fields are displayed depends on the configuration of the portal user-log traffic-separate command. For more information, see portal commands in Security Command Reference. |
|
Recommended action |
Choose the recommended action according to the reason (see Table 12). |
Table 12 Reasons that a user goes offline and recommended actions
|
Reason |
Description |
Recommended action |
|
User request. |
The user requested to be offline. |
No action is required. |
|
DHCP entry deleted. |
The DHCP entry was deleted. |
Verify that the DHCP server configuration is correct. |
|
Idle timeout. |
The traffic of the user in the specified period of time does not reach the idle cut traffic threshold. |
No action is required. |
|
Session timeout. |
The user's online time has reached the session timeout time assigned by the server. |
No action is required. |
|
User detection failure. |
The user failed online detection. |
No action is required. |
|
Force logout by RADIUS server. |
The RADIUS server logged out the user. |
No action is required. |
|
Interface down. |
· The state of the access interface became Down or Deactive. · The access interface is a VLAN interface and a Layer 2 port left the VLAN. |
· Verify that a cable is correctly inserted to the user access interface, and the access interface is not shut down by using the shutdown command. · Verify that the user access interface card or subcard operates normally. · Verify that portal roaming is enabled on the user access Layer 2 Ethernet interface. |
|
Failed to assign a user rule. |
N/A. |
Release memory to ensure enough hardware memory space. |
|
Authorization info changed. |
Authorization information changed for the user. For example, the authorization ACL or user profile was deleted. |
No action is required. |
|
Force logout by access device. |
The device logged out the user. |
Make sure portal authentication functions normally on the user access interface. |
|
User info synchronization failure. |
The device failed to synchronize user information with the server. |
· Make sure the user heartbeat interval configured on the portal authentication server is not greater than the user synchronization detection timeout configured on the access device. · Verify that the server is reachable. |
|
User recovery failure. |
User information recovery failed. |
· Verify that the user access interface is up. · Verify that portal authentication is enabled on the user access interface. · Verify that the session timeout timer for the user does not expire. |
|
Authorization ACL for the online user changed. |
N/A |
· Verify that the authorization ACL for the user is correctly assigned. · Verify that strict checking on authorized ACLs is disabled. |
|
Authorization user profile for the online user changed. |
N/A |
· Verify that the authorization user profile for the user is correctly assigned by using the display user profile command. · Verify that strict checking on authorized user profiles is disabled. |
|
Accounting update failure. |
Failed to update accounting for the user. |
· Verify that the device can correctly communicate with the accounting server. · Verify that the status of the accounting server is active. |
|
Failed to start accounting. |
Failed to start accounting for the user. |
· Verify that the device can correctly communicate with the accounting server. · Verify that the status of the accounting server is active. |
|
User traffic reached threshold. |
Traffic of the user reached the traffic threshold set by the server. |
No action is required. |
|
Authorization VPN instance deleted. |
The authorization VPN instance was deleted. |
No action is required. |
|
Authorization ACL does not exist. |
The authorization ACL does not exist. |
Verify that the ACL is correctly configured on the device. |
|
Failed to get physical info. |
Failed to get the physical information. |
No action is required. |
|
Failed to add an ARP or ND entry for the user. |
Failed to add the ARP or ND entry of the user. |
No action is required. |
|
User information does not match user profile. |
The user information and the user profile do not match. |
No action is required. |
|
Authorization user profile does not exist. |
The authorization user profile does not exist. |
Verify that the user profile is correctly configured on the device. |
|
Failed to issue the user rule to the AP. |
Failed to issue the user rule to the AP. |
No action is required. |
|
Deleted the user for SSID switchover. |
The user was logged out after SSID switchover. |
No action is required. |
|
Failed to issue an OpenFlow rule to the AP. |
Failed to issue an OpenFlow rule to the AP. |
No action is required. |
|
Logged out the user after the wireless client disconnected. |
The user was logged out after the wireless client was disconnected. |
No action is required. |
|
Logged out the user when a new user with the same MAC address performed MAC-trigger authentication. |
The user was logged out because a new user with the same MAC address performed MAC-trigger authentication. |
No action is required. |
|
Logged out the user when a new dual-stack user with the same MAC address came online. |
The user was logged out because a new dual-stack user with the same MAC address came online. |
No action is required. |
|
The portal server failed to instruct the device to change the user IP address. |
The portal server failed to instruct the device to change the IP address of the user. |
No action is required. |
|
DHCP received a DHCP release packet. |
The user was logged out because DHCP received a DHCP release message. |
No action is required. |
|
DHCP lease expired. |
The DHCP lease of the user expired. |
No action is required. |
|
DHCP received a DHCP release packet from the WLAN roaming center. |
The WLAN roaming center instructed DHCP to log out the user because of a DHCP release message. |
No action is required. |
|
WLAN roaming center instructed portal to log out the user. |
The WLAN roaming center instructed portal to log out the user. |
No action is required. |
|
Logged out the user after user synchronization through WiFiDog. |
Portal logged out the user after it synchronized user information through WifFiDog. |
No action is required. |
|
The cloud portal server instructed portal to log out the user. |
The cloud portal server instructed portal to log out the user. |
No action is required. |
PORTAL_USER_LOGON_FAIL
|
Message text |
-UserName=[STRING]-IPAddr=[IPADDR]-IfName=[STRING]-OuterVLAN=[UINT16]-InnerVLAN=[UINT16]-MACAddr=[MAC]-Reason=[STRING]; User failed to get online. |
|
Variable fields |
$1: Username. $2: IP address. $3: Interface name. $4: Outer VLAN ID. $5: Inner VLAN ID. $6: MAC address. $7: Login failure reason, see Table 13. |
|
Severity level |
6 |
|
Example |
PORTAL/6/PORTAL_USER_LOGON_FAIL: -UserName=abc-IPAddr=1.1.1.2-IfName=Route-Aggregation1023.4000- OuterVLAN=100-InnerVLAN=4000-MACAddr=0230-0103-5601-Reason= Authentication Failed : 4; User failed to get online. |
|
Explanation |
A portal user failed to come online. |
|
Recommended action |
Choose the recommended action according to the reason, see Table 13. |
Table 13 Reasons that a user fails to come online and recommended actions
|
Reason |
Description |
Recommended action |
|
Authorization failure. |
Authorization failed, or authorization attributes deployment failed. |
· Verify that the device can correctly communicate with the authorization server. · Verify that the authorization user attributes exist on the device and are correctly configured. · Verify that the device supports the authorization user attributes. |
|
Received logout request. |
The user received a logout request from the portal server during the login process. |
Verify that the device can correctly communicate with the AAA server. |
|
Authentication failure. |
Authentication failed. |
· Verify that the device can correctly communicate with the authentication server. · Verify that the shared key is the same on the device and the authentication server. · Verify that the username is valid. · Verify that the password for the username is correct. · Verify that the authentication domain on the device is correct. |
|
Other error. |
Unknown error. |
N/A |
PORTAL_USER_LOGON_SUCCESS
|
Message text |
-UserName=[STRING]-IPAddr=[IPADDR]-IfName=[STRING]-OuterVLAN=[UINT16]-InnerVLAN=[UINT16]-MACAddr=[MAC]:User got 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 |
PORTAL/6/PORTAL_USER_LOGON_SUCCESS: -UserName=abc-IPAddr=1.1.1.2-IfName=Route-Aggregation1023.4000- OuterVLAN=100-InnerVLAN=4000-MACAddr=0230-0103-5601; User got online successfully. |
|
Explanation |
A portal user came online successfully. |
|
Recommended action |
No action is required. |
PORTSEC messages
This section contains port security messages.
PORTSEC_ACL_FAILURE
|
Message text |
-IfName=[STRING]-MACAddr=[STRING]; ACL authorization failed because [STRING]. |
|
Variable fields |
$1: Interface type and number. $2: MAC address. $3: Cause of failure: · the specified ACL didn't exist. · this type of ACL is not supported. · hardware resources were insufficient. · the specified ACL conflicted with other ACLs applied to the interface. · the specified ACL didn't contain any rules. |
|
Severity level |
4 |
|
Example |
PORTSEC/4/PORTSEC_ACL_FAILURE:-IfName=GigabitEthernet1/0/4-MACAddr=0010-8400-22b9; ACL authorization failed because the specified ACL didn't exist. |
|
Explanation |
ACL authorization failed for a specific reason. |
|
Recommended action |
Handle the issue according to the failure cause. |
PORTSEC_CAR_FAILURE
|
Message text |
-IfName=[STRING]-MACAddr=[STRING]; Failed to assign CAR attributes to driver. |
|
Variable fields |
$1: Interface type and number. $2: MAC address. |
|
Severity level |
5 |
|
Example |
PORTSEC/5/PORTSEC_CAR_FAILURE:-IfName=GigabitEthernet1/0/4-MACAddr=0010-8400-22b9; Failed to assign CAR attributes to driver. |
|
Explanation |
The device failed to assign CAR attributes to the driver. |
|
Recommended action |
No action is required. |
PORTSEC_CREATEAC_FAILURE
|
Message text |
-IfName=[STRING]-VLANID=[STRING]-MACAddr=[STRING]-VSIName=[STRING]; Failed to map an Ethernet service instance to the VSI. |
|
Variable fields |
$1: Interface type and number. $2: VLAN ID. $3: MAC address. $4: VSI name. |
|
Severity level |
3 |
|
Example |
PORTSEC/3/PORTSEC_CREATEAC_FAILURE:-IfName=GigabitEthernet1/0/4-VLANID=444-MACAddr=0010-8400-22b9-VSIName=aaa; Failed to map an Ethernet service instance to the VSI. |
|
Explanation |
The operation of mapping an Ethernet service instance to a specific VSI failed. |
|
Recommended action |
Execute the display l2vpn vsi command and verify that the VSI exists. If the VSI does not exist, create the VSI by using the vsi command. |
PORTSEC_LEARNED_MACADDR
|
Message text |
-IfName=[STRING]-MACAddr=[STRING]-VLANID=[STRING]; A new MAC address was learned. |
|
Variable fields |
$1: Interface type and number. $2: MAC address. $3: VLAN ID. |
|
Severity level |
6 |
|
Example |
PORTSEC/6/PORTSEC_LEARNED_MACADDR:-IfName=GigabitEthernet1/0/4-MACAddr=0010-8400-22b9-VLANID=444; A new MAC address was learned. |
|
Explanation |
A new secure MAC address was learned on the interface. |
|
Recommended action |
No action is required. |
PORTSEC_NTK_NOT_EFFECTIVE
|
Message text |
The NeedToKnow feature is configured but is not effective on interface [STRING]. |
|
Variable fields |
$1: Interface type and number. |
|
Severity level |
3 |
|
Example |
PORTSEC/3/PORTSEC_NTK_NOT_EFFECTIVE: The NeedToKnow feature is configured but is not effective on interface Ethernet3/1/2. |
|
Explanation |
The NeedToKnow mode does not take effect on an interface, because the interface does not support the NeedToKnow mode. |
|
Recommended action |
1. Disable the NeedToKnow feature on the interface. 2. Reconnect the connected devices to another interface that supports the NeedToKnow mode. 3. Configure the NeedToKnow mode on the new interface. |
PORTSEC_PORTMODE_NOT_EFFECTIVE
|
Message text |
The port security mode is configured but is not effective on interface [STRING]. |
|
Variable fields |
$1: Interface type and number. |
|
Severity level |
3 |
|
Example |
PORTSEC/3/PORTSEC_PORTMODE_NOT_EFFECTIVE: The port security mode is configured but is not effective on interface Ethernet3/1/2. |
|
Explanation |
The port security mode does not take effect on an interface, because the interface does not support this mode. |
|
Recommended action |
· Change the port security mode to another mode that is supported by the interface. · Reconnect the connected devices to another interface that supports this port security mode, and configure the port security mode on the new interface. |
PORTSEC_PROFILE_FAILURE
|
Message text |
-IfName=[STRING]-MACAddr=[STRING]; Failed to assign a user profile to driver. |
|
Variable fields |
$1: Interface type and number. $2: MAC address. |
|
Severity level |
5 |
|
Example |
PORTSEC/5/PORTSEC_PROFILE_FAILURE:-IfName=GigabitEthernet1/0/4-MACAddr=0010-8400-22b9; Failed to assign a user profile to driver. |
|
Explanation |
The device failed to assign a user profile to the driver. |
|
Recommended action |
No action is required. |
PORTSEC_URL_FAILURE
|
Message text |
-IfName=[STRING]-MACAddr=[STRING]; URL authorization failed because [STRING]. |
|
Variable fields |
$1: Interface type and number. $2: MAC address. $3: Cause of failure: · this operation was not supported. · hardware resources were insufficient. · parameters were invalid. · an unknown error existed. |
|
Severity level |
4 |
|
Example |
PORTSEC/4/PORTSEC_URL_FAILURE:-IfName=GigabitEthernet1/0/4-MACAddr=0010-8400-22b9; URL authorization failed because hardware resources were insufficient. |
|
Explanation |
URL authorization failed for a specific reason. |
|
Recommended action |
Handle the issue according to the failure cause. |
PORTSEC_VIOLATION
|
Message text |
-IfName=[STRING]-MACAddr=[STRING]-VLANID=[STRING]-IfStatus=[STRING]; Intrusion protection was triggered. |
|
Variable fields |
$1: Interface type and number. $2: MAC address. $3: VLAN ID. $4: Interface status. |
|
Severity level |
5 |
|
Example |
PORTSEC/5/PORTSEC_VIOLATION:-IfName=GigabitEthernet1/0/4-MACAddr=0010-8400-22b9-VLANID=444-IfStatus=Up; Intrusion protection was triggered. |
|
Explanation |
Intrusion protection was triggered. |
|
Recommended action |
· Check the port security configuration. · Change the port security mode to another mode. |
PORTSEC_VLANMACLIMIT
|
Message text |
-IfName=[STRING]-MACAddr=[STRING]-VLANID=[STRING]; Maximum number of MAC addresses already reached in the VLAN. |
|
Variable fields |
$1: Interface type and number. $2: MAC address. $3: VLAN ID. |
|
Severity level |
5 |
|
Example |
PORTSEC/5/PORTSEC_VLANMACLIMIT:-IfName=GigabitEthernet1/0/4-MACAddr=0010-8400-22b9-VLANID=444; Maximum number of MAC addresses already reached in the VLAN. |
|
Explanation |
Access attempt from a new user in a VLAN was rejected on a port because the number of MAC addresses has reached port security's limit on the port for that VLAN. |
|
Recommended action |
Examine the network for the risk of unknown source MAC attacks. |
PPP messages
This section contains PPP messages.
IPPOOL_ADDRESS_EXHAUSTED
|
Message text |
The address pool [STRING] was exhausted. |
|
Variable fields |
$1: Pool name. |
|
Severity level |
5 |
|
Example |
PPP/5/IPPOOL_ADDRESS_EXHAUSTED: The address pool aaa was exhausted. |
|
Explanation |
This message is generated when the last address is assigned from the pool. |
PPP_USER_LOGON_SUCCESS
|
Message text |
-UserName=[STRING]-IPAddr=[IPADDR]-IfName=[STRING]-OuterVLAN=[UINT16]-InnerVLAN=[UINT16]-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 |
PPP/6/PPP_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 successfully. |
|
Recommended action |
No action is required. |
PPP_USER_LOGON_FAILED
|
Message text |
-UserName=[STRING]-IPAddr=[IPADDR]-IfName=[STRING]-OuterVLAN=[UINT16]-InnerVLAN=[UINT16]-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 14). |
|
Severity level |
5 |
|
Example |
PPP/5/PPP_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 14. |
Table 14 Causes and recommended actions
|
Cause |
Description |
Recommended action |
|
Authentication method error |
The authentication method was configured incorrectly, possibly because the authentication method requested by users is inconsistent with the authentication method configured on the interface. |
Verify that the authentication method is configured correctly. |
|
AAA access limit reached |
The upper limit of concurrent logins using the same local user name is reached. |
4. Check the number of concurrent online users using the current local user name. 5. Modify the upper limit of the concurrent logins using the current local user name to a greater value by executing the access-limit command. |
|
The local user does not exist |
The local user was not configured. |
6. Verify that the dial-in user is a legal user. 7. Add the local user if the user is a legal user but the corresponding local user does not exist on the device. |
|
Local authentication failed: wrong password |
The local authentication was rejected because of the incorrect password. |
8. Verify that the username is correct. 9. Verify that the password is correct. |
|
No AAA response during authentication |
The device did not receive an AAA response from the authentication server during the authentication timeout time. |
10. Verify that the device communicates with the authentication server correctly. 11. Verify that the authentication server operates correctly. 12. Verify that the shared key on the device is the same as the shared key on the authentication server. |
|
RADIUS authentication reject |
The RADIUS server returned an access-reject packet. |
13. Verify that the username is correct. 14. 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. |
|
Authentication request to AAA failed |
The device failed to send the authentication request to the AAA server. |
15. Verify that the device communicates with the authentication server correctly. 16. Verify that the authentication server operates correctly. |
|
Accounting request to AAA failed |
The device failed to send the accounting request to the AAA server. |
17. Verify that the device communicates with the accounting server correctly. 18. Verify that the accounting server operates correctly. |
|
No authentication ACK from AAA |
The device failed to receive the authentication acknowledgment packet from the AAA server. |
19. Verify that the device communicates with the authentication server correctly. 20. Verify that the authentication server operates correctly. |
|
TACACS authentication reject |
The TACACS server returned an access-reject packet. |
21. Verify that the username is correct. 22. Verify that the password is correct. |
PPP_USER_LOGOFF
|
Message text |
-UserName=[STRING]-IPAddr=[IPADDR]-IfName=[STRING]-OuterVLAN=[UINT16]-InnerVLAN=[UINT16]-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 15). |
|
Severity level |
6 |
|
Example |
PPP/6/PPP_USER_LOGOFF: -UserName=abc-IPAddr=1.1.1.2-IfName=Route-Aggregation1023.4000-OuterVLAN=1000-InnerVLAN=4000-MACAddr=0230-0103-5601-Reason=Use request; The user logged off. |
|
Explanation |
The user has gone offline normally. |
|
Recommended action |
No action is required. |
|
Cause |
Description |
|
User request |
The user connection was terminated at the user's request. |
PPP_USER_LOGOFF_ABNORMAL
|
Message text |
-UserName=[STRING]-IPAddr=[IPADDR]-IfName=[STRING]-OuterVLAN=[UINT16]-InnerVLAN=[UINT16]-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 16). |
|
Severity level |
6 |
|
Example |
PPP/6/PPP_USER_LOGOFF_ABNORMAL: -UserName=abc-IPAddr=1.1.1.2-IfName=Route-Aggregation1023.4000-OuterVLAN=1000-InnerVLAN=4000-MACAddr=0230-0103-5601-Reason=Lost Carrier; The user logged off abnormally. |
|
Explanation |
The user has gone offline abnormally. |
|
Recommended action |
See Table 16. |
Table 16 Causes and recommended actions
|
Cause |
Description |
Recommended action |
|
Lost carrier |
The keepalive packets were lost, possibly because the link between the user device and the device connecting to the BAS fails. |
Save the related log information locally and contact the support. |
|
Lost service |
The service server (for example, L2TP) terminated the service. |
No action is required. |
|
Admin reset |
The user session was temporarily terminated by the administrator by executing the shutdown command because of management reasons. |
No action is required. |
|
BAS request |
Unknown reasons. |
Save the related log information locally and contact the support. |
|
Session timeout |
The user session timed out. |
Notify the user that the traffic quota is used up or to renew the user account. |
|
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. |
|
Logged off by the RADIUS server |
The AAA server logged off the user. |
No action is required. |
|
Accounting update failure |
The accounting update failed. |
23. Verify that the device communicates with the accounting server correctly. 24. Verify that the accounting server operates correctly. |
|
No AAA response during realtime accounting |
The user did not receive the response from the accounting server during the timeout time. (In the realtime accounting phase.) |
25. Verify that the device communicates with the accounting server correctly. 26. Verify that the accounting server operates correctly. |
|
No AAA response for accounting start |
The user did not receive the response from the accounting server during the timeout time. (In the accounting start phase.) |
27. Verify that the device communicates with the accounting server correctly. 28. Verify that the accounting server operates correctly. |
|
No AAA response for accounting stop |
The user did not receive the response from the accounting server during the timeout time. (In the accounting stop phase.) |
29. Verify that the device communicates with the accounting server correctly. 30. Verify that the accounting server operates correctly. |
|
PPP negotiation terminated |
The PPP negotiation was terminated. |
Verify that the configuration is correct. |
|
Repeated LCP negotiation packets |
Repeated LCP negotiation packets were received. |
Disconnect the client and initiate a connection again. |
|
The interface that the user accesses goes down |
N/A. |
31. Verify that the network cable of the user access interface is correctly connected. 32. Verify the user access card or subcard has no errors or is in position. |
|
The interface that the user accesses is shut down |
N/A. |
Verify that the shutdown command is not executed on the user access interface. |
|
Session idle cut |
The user traffic did not reach the threshold within the specified period. |
No action is required. |
PPPOES messages
This section contains PPPOES messages.
PPPOES_MAC_THROTTLE
|
Message text |
The MAC [STRING] triggered MAC throttle on interface [STRING]. |
|
Variable fields |
$1: MAC address. $2: Interface name. |
|
Severity level |
5 |
|
Example |
PPPOES/5/PPPOES_MAC_THROTTLE: -MDC=1; The MAC 001b-21a8-0949 triggered MAC throttle on interface GigabitEthernet1/0/1. |
|
Explanation |
The maximum number of PPPoE session requests from a user within the monitoring time reached the PPPoE access limit on the access interface. The access interface discarded the excessive requests. |
|
Recommended action |
1. Check the PPPoE access limit on the access interface that is configured by using the pppoe-server throttle per-mac command. 2. View the time left for the blocking user on the access interface by executing the display pppoe-server throttled-mac command. 3. If the problem persists, contact the support. |
PTP messages
This section contains PTP messages.
PTP_EXT_TIME_PORT_DISCONNECT
|
Message text |
The external time port became disconnect. (ExtTimePortType=[STRING]) |
|
Variable fields |
$1: ToD interface type: ¡ ToD0 ¡ ToD1 |
|
Severity level |
4 |
|
Example |
PTP/4/PTP_EXT_TIME_PORT_DISCONNECT: The external time port became disconnect. (ExtTimePortType=ToD0) |
|
Explanation |
The device failed to receive clock signals from the external clock source, or the external clock source terminated the connection to the device. |
|
Recommended action |
Identify whether the PTP interface connected to the external clock source is up. · If the PTP interface is up, collect log and configuration information and contact the support. · If the PTP interface is down, the link or the interface is down. Resolve the issue and recover the link. |
PTP_EXT_TIME_PORT_RECOVER
|
Message text |
The external time port status resumed. (ExtTimePortType=[STRING]) |
|
Variable fields |
¡ $1: External clock type: ¡ ToD0 ¡ ToD1 |
|
Severity level |
4 |
|
Example |
PTP/4/PTP_EXT_TIME_PORT_RECOVER: The external time port status resumed. (ExtTimePortType=ToD0) |
|
Explanation |
· The device resumed signal receiving from the external clock source. · The physical link between the device and the external clock source recovered. |
|
Recommended action |
No action is required. |
PTP_FREQUENCY_LOCK
|
Message text |
Clock frequency resumed to locked state. |
|
Variable fields |
N/A |
|
Severity level |
3 |
|
Example |
PTP/3/PTP_FREQUENCY_LOCK: Clock frequency resumed to locked state. |
|
Explanation |
The clock frequency resumed from not locked state. |
|
Recommended action |
No action is required. |
PTP_FREQUENCY_NOT_LOCK
|
Message text |
Clock frequency not in locked state. |
|
Variable fields |
N/A |
|
Severity level |
3 |
|
Example |
PTP/3/PTP_FREQUENCY_NOT_LOCK: Clock frequency not in locked state. |
|
Explanation |
The clock frequency is in unlocked state. Possible reasons include: · In SyncE frequency synchronization mode, the frequency offset of the reference source is large. · In 1588v2 frequency synchronization mode, the timestamps are abnormal. · The output frequency offset of the system clock exceeds +/-10 ppm. |
|
Recommended action |
Identify whether a PTP_FREQUENCY_LOCK log will be output after this log. · If a PTP_FREQUENCY_LOCK log is output, the device has just started up or frequency flapping has occurred. · If no PTP_FREQUENCY_LOCK log is output, identify whether the PTP settings have changed. ¡ If the PTP settings have changed, restore the settings. ¡ If the PTP settings have not changed, collect log and configuration information and contact the support. |
PTP_MEAN_PATH_DELAY_ABNORMAL
|
Message text |
In PTP instance [UINT16], PTP mean path delay is abnormal. (Delay-mechanism=[UINT64], MeanPathDelay=[UINT64] ns, MeanPathDelayThreshold=[UINT64] ns) |
|
Variable fields |
$1: PTP instance ID. (Support for PTP instances depends on the device model.) $2: Delay measurement mechanism: ¡ e2e—Request-response delay measurement mechanism. ¡ p2p—Peer delay measurement mechanism. $3: Mean path delay, in ns. $4: Mean path delay threshold, in ns. |
|
Severity level |
5 |
|
Example |
PTP/5/PTP_MEAN_PATH_DELAY_ABNORMAL: In PTP instance 1, PTP mean path delay is abnormal. (Delay-mechanism=e2e, MeanPathDelay=70000 ns, MeanPathDelayThreshold=7000 ns) |
|
Explanation |
This log is generated when the mean path delay in a PTP instance reaches the threshold. |
|
Recommended action |
PTP time synchronization continues even if the PTP mean path delay is increased. · If increase of the mean path delay is caused by network environment changes, check the network. · If the network delay is stable and has not fluctuated, collect alarm, log, and configuration information and contact Technical Support. |
PTP_MASTER_CLOCK_CHANGE
|
Message text |
PTP master clock property changed. (OldMasterClockId=[STRING], CurrentMasterClockId=[STRING], NewSourceIfIndex=[UINT16], OldSourcePortNum=[UINT16], CurrentSourcePortNum=[UINT16], OldSourcePortName=[STRING], CurrentSourcePortName=[STRING]) |
|
Variable fields |
$1: ID of the original master clock. $2: ID of the current master clock. $3: Index of the new clock source. $4: Number of the interface through which the old clock source distributed its time to the device. $5: Number of the interface through which the new clock source distributes its time to the device. $6: Name of the interface through which the old clock source distributed its time to the device. $7: Name of the interface through which the new clock source distributes its time to the device. |
|
Severity level |
4 |
|
Example |
PTP/4/PTP_MASTER_CLOCK_CHANGE: PTP master clock property changed. (OldMasterClockId=000FE2-FFFE-FF0000, CurrentMasterClockId=000FE2-FFFE-FF0000, NewSourceIfIndex=1, OldSourcePortNum=2, CurrentSourcePortNum=1, OldSourcePortName=G1/0/2, CurrentSourcePortName=G1/0/1) |
|
Explanation |
The attributes of the master clock changed. Possible reasons include: · The attributes of the clock nodes in the PTP domain had changed. As a result, a clock source with higher priority appeared or the path to the clock source changed. · The device had connected to a clock source with higher priority. · The PTP interface that received clock source signals is down or its link is down. |
|
Recommended action |
Execute the display ptp interface brief command to check for PTP interfaces in Disabled state. · If a PTP interface is in Disabled state, the interface does not handle PTP messages. Collect log and configuration information and contact the support. · If no PTP interface is in Disabled state, identify whether PTP settings have changed. ¡ If PTP settings have changed, restore the settings. ¡ If PTP settings have not changed, collect log and configuration information and contact the support. |
PTP_PKT_ABNORMAL
|
Message text |
Received an abnormal PTP packet. |
|
Variable fields |
N/A |
|
Severity level |
6 |
|
Example |
PTP/6/PTP_PKT_ABNORMAL: Received an abnormal PTP packet. |
|
Explanation |
The device received a defective PTP packet. The TimeSource, TimeTraceable, or FreqencyTraceable field of the packet might be incorrect. |
|
Recommended action |
To resolve the issue: 1. Determine whether the peer device has been configured with a special PTP technical standard. ¡ If the peer device has been configured with a special PTP technical standard, go to 3. ¡ If the peer device has not been configured with a special PTP technical standard, go to 2. ¡ If a PTP_PKT_ABNORMALCOUNT log has been output, go to 4. ¡ If no PTP_PKT_ABNORMALCOUNT log has been output, the issue is resolved. 3. Wait 20 minutes. Then identify whether a PTP_PKT_ABNORMALCOUNT log has been output. ¡ If a PTP_PKT_ABNORMALCOUNT log has been output, go to 4. ¡ If no PTP_PKT_ABNORMALCOUNT log has been output, the issue is resolved. 4. Collect alarm, log, and configuration information and contact the support. |
PTP_PKT_ABNORMALCOUNT
|
Message text |
Received [ULONG] abnormal PTP packets in the last 10 minutes. |
|
Variable fields |
$1: Number of abnormal PTP packets received in the last 10 minutes. |
|
Severity level |
6 |
|
Example |
PTP/6/PTP_PKT_ABNORMALCOUNT: Received 300 abnormal PTP packets in the last 10 minutes. |
|
Explanation |
The device has received abnormal PTP packets in the last 10 minutes. |
|
Recommended action |
To resolve the issue: 1. Determine whether the peer device has been configured with a special PTP technical standard. ¡ If the peer device has been configured with a special PTP technical standard, go to 3. ¡ If the peer device has not been configured with a special PTP technical standard, go to 2. ¡ If a PTP_PKT_ABNORMALCOUNT log has been output, go to 4. ¡ If no PTP_PKT_ABNORMALCOUNT log has been output, the issue is resolved. 3. Wait 20 minutes. Then identify whether a PTP_PKT_ABNORMALCOUNT log has been output. ¡ If a PTP_PKT_ABNORMALCOUNT log has been output, go to 4. ¡ If no PTP_PKT_ABNORMALCOUNT log has been output, the issue is resolved. 4. Collect alarm, log, and configuration information and contact the support. |
PTP_PKTLOST
|
Message text |
PTP packets were lost. (PktType=[STRING]) |
|
Variable fields |
$1: PTP message type: ¡ Delay_Resp ¡ Announce ¡ Sync ¡ Pdelay_Resp |
|
Severity level |
4 |
|
Example |
PTP/4/PTP_PKTLOST: PTP packets were lost. (PktType=Announce) |
|
Explanation |
The subordinate port failed to receive Announce, Delay_Resp, and Sync messages within the timeout period. |
|
Recommended action |
Execute the display ptp statistics command to identify whether the counts of the received PTP messages are increasing. · If the counts are increasing, the timeout was caused by link delay. No action is required. · If the counts are not increasing, execute the display ptp statistics command to identify whether the counts of transmitted messages are increasing. ¡ If the counts are increasing, a link failure caused the timeout. Resolve the issue and recover the link. ¡ If the counts are not increasing, collect log and configuration information and contact the support. |
PTP_PKTLOST_RECOVER
|
Message text |
PTP packets lost were recovered. (PktType=[STRING]) |
|
Variable fields |
$1: PTP message type: ¡ Delay_Resp ¡ Announce ¡ Sync ¡ Pdelay_Resp |
|
Severity level |
4 |
|
Example |
PTP/4/PTP_PKTLOST_RECOVER: PTP packets lost were recovered. (PktType =Announce) |
|
Explanation |
· The subordinate port resumed receiving of Announce, Delay_Resp, and Sync messages. A timeout had occurred before. · The device role changed from member clock to master clock. A PTP message receiving timeout had occurred before. |
|
Recommended action |
No action is required. |
PTP_PORT_BMCINFO_CHANGE
|
Message text |
The BMC info for port [UINT16] changed. (PortName=[STRING], PortSourceId=[STRING], PortSourcePortNum=[UINT16], PortSourceStepsRemoved=[UINT16], CurrentMasterClockId=[STRING]) |
|
Variable fields |
$1: PTP interface index. $2: PTP interface name. $3: Clock source ID that the PTP interface receives. $4: Clock source port number that the PTP interface receives. $5: Number of removed steps that the PTP interface receives. $6: Master clock ID. |
|
Severity level |
5 |
|
Example |
PTP/5/PTP_PORT_BMCINFO_CHANGE: The BMC info for port 1 changed. (PortName=G1/0/1, PortSourceId=000FE2-FFFE-FF0001, PortSourcePortNum=1, PortSourceStepsRemoved=5, CurrentMasterClockId=000FE2-FFFE-FF0000) |
|
Explanation |
Clock source information received by the PTP interface changed, including the clock source ID, port number, and number of removed steps. |
|
Recommended action |
No action is required. |
PTP_PORT_STATE_CHANGE
|
Message text |
PTP port state changed. (IfIndex=[UINT16], PortName=[STRING], PortState=[STRING], OldPortState=[STRING]) |
|
Variable fields |
$1: PTP interface index. $2: PTP interface name. $3: PTP interface state. ¡ Master—Sends synchronization messages. ¡ Slave—Receives synchronization messages. ¡ Passive—Neither receives nor sends synchronization messages. A PTP interface is in passive state after it receives an announce message. ¡ Listening—Neither receives nor sends synchronization messages. A PTP interface is in listening state after being initialized. ¡ Faulty—PTP is running incorrectly. A PTP interface in faulty state does not process PTP messages. ¡ Initializing—The interface is initializing. A PTP interface in initializing state does not process PTP messages. ¡ Premaster—Temporary state before the interface enters Master state. ¡ Disabled—PTP is not running on the interface. The interface does not process PTP messages. ¡ Uncalibrated—Temporary state before the interface enters Slave state. $4: Previous state of the PTP interface. |
|
Severity level |
5 |
|
Example |
PTP/5/PTP_PORT_STATE_CHANGE: PTP port state changed. (IfIndex=1, PortName=G1/0/1, PortState=Slave, OldPortState=Master) |
|
Explanation |
PTP interface state changed. Possible reasons include: · The attributes of the clock nodes in the PTP domain had changed, including the priority, time class, time accuracy, and NotSlave feature. · The device had connected to another clock source with higher priority. · The PTP interface or its link had gone down. |
|
Recommended action |
Execute the display ptp interface brief command to identify whether a PTP interface is in Fault state. · If there is a PTP interface in Fault state, the PTP interface or its link was down. Resolve the issue and recover the link. · If no PTP interface is in Fault state, identify whether PTP settings have changed. ¡ If PTP settings have changed, restore the settings. ¡ If PTP settings have not changed, collect log and configuration information and contact the support. |
PTP_SRC_CHANGE
|
Message text |
Clock source property changed. (SourceName=[STRING], Priority1=[UCHAR], Priority2=[UCHAR], ClockClass=[UINT16], ClockAccuracy=[UINT16]], ClockSourceType=[STRING]) |
|
Variable fields |
$1: Clock source: ¡ Local ¡ ToD1 ¡ ToD2 $2: Priority 1 $3: Priority 2 $4: Class of the clock source $5: Accuracy of the clock source $6: GM type: ¡ Atomic clock. ¡ Global Positioning System (GPS). ¡ Handset. ¡ Internal oscillator. ¡ NTP. ¡ Other. ¡ PTP. ¡ Terrestrial radio. ¡ Unknown. |
|
Severity level |
5 |
|
Example |
PTP/5/PTP_SRC_CHANGE: Clock source property changed. (SourceName=Tod1, Priority1=1, Priority2=2, ClockClass=6, ClockAccuracy=20, ClockSourceType=Atomic clock) |
|
Explanation |
The attributes of the clock source changed. Possible reasons include: · Command lines had been executed to change the clock source attributes. · The device had connected to another clock source with a higher accuracy. |
|
Recommended action |
No action is required. |
PTP_SRC_CLASS_BELOW_THRESHOLD
|
Message text |
The clock source class fell below the threshold. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
PTP/4/PTP_SRC_CLASS_BELOW_THRESHOLD: The clock source class fell below the threshold. |
|
Explanation |
The clock source class threshold was reached. |
|
Recommended action |
Execute the display ptp clock comand to check the Class field to determine whether the clock source class fell below the threshold. · If it fell below the threshold, raise the clock class level or use another clock source with a higher time class. Then check whether a PTP_SRC_CLASS_RECOVER log is output. ¡ If a PTP_SRC_CLASS_RECOVER log is output, the issue is resolved. ¡ If no PTP_SRC_CLASS_RECOVER log is output, collect alarm, log, and configuration information and contact technical support. · If it does not fall below the threshold, collect alarm, log, and configuration information and contact technical support. |
PTP_SRC_CLASS_RECOVER
|
Message text |
The clock source class crossed the threshold. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
PTP/4/PTP_SRC_CLASS_RECOVER: The clock source class crossed the threshold. |
|
Explanation |
The clock source class restored to normal level. |
|
Recommended action |
None. |
PTP_SRC_SWITCH
|
Message text |
Clock source switched. (LastClockID=[STRING], CurrentClockID=[STRING]) |
|
Variable fields |
$1: ID of the original clock source $2: ID of the current clock source. |
|
Severity level |
4 |
|
Example |
PTP/4/PTP_SRC_SWITCH: Clock source switched.(LastSource=000FE2-FFFE-FF0000, CurrentSource=000FE2-FFFE-FF0001) |
|
Explanation |
A clock source with higher accuracy and priority had been added to the PTP domain. The device had selected another clock source. |
|
Recommended action |
No action is required. |
PTP_SYNC_RESUME
|
Message text |
In PTP instance [UINT16], PTP time synchronization resumed because the PTP time offset between the instance and the master fell below the threshold or the maximum suppression counts were reached. (TimeOffset=[INT64] ns, TimeOffsetThreshold=[UINT64] ns, SuppressionCounts=[UINT16]) |
|
Variable fields |
$1: PTP instance ID. (Support for PTP instances depend on the device model.) $2: Offset between the current PTP time and the most recent PTP time provided from the master, in ns. $3: Maximum offset between the current PTP time and the most recent PTP time provided from the master, in ns. $4: Maximum counts that PTP time synchronization is suppressed. |
|
Severity level |
4 |
|
Example |
PTP/4/PTP_SYNC_RESUME: In PTP instance 1, PTP time synchronization resumed because the PTP time offset between the instance and the master fell below the threshold or the maximum suppression counts were reached. (TimeOffset=50 ns, TimeOffsetThreshold=3000 ns, SuppressionCounts=3) |
|
Explanation |
PTP time synchronization suppression in the specified PTP instance was released because the PTP time offset between the instance and the master had fallen below the threshold or the maximum suppression counts had been reached. |
|
Recommended action |
No action is required. |
PTP_SYNC_SUPPRESS
|
Message text |
In PTP instance [UINT16], PTP time synchronization was suppressed because the PTP time offset between the instance and the master exceeded the threshold. (TimeOffset=[INT64] ns, TimeOffsetThreshold=[UINT64] ns) |
|
Variable fields |
$1: PTP instance ID. (Support for PTP instances depend on the device model.) $2: Offset between the current PTP time and the most recent PTP time provided from the master, in ns. $3: Maximum offset between the current PTP time and the most recent PTP time provided from the master, in ns. |
|
Severity level |
4 |
|
Example |
PTP/4/PTP_SYNC_SUPPRESS: In PTP instance 1, PTP time synchronization was suppressed because the PTP time offset between the instance and the master exceeded the threshold. (TimeOffset=5000 ns, TimeOffsetThreshold=3000 ns) |
|
Explanation |
PTP time synchronization in the specified PTP instance was suppressed because the PTP time offset between the instance and the master had exceeded the threshold. |
|
Recommended action |
Collect alarm, log, and configuration information and contact Technical Support. |
PTP_TIME_OFFSE_EXCEED_THRESHOLD
|
Message text |
The PTP time offset exceeded the threshold. (TimeOffset=[UINT16], AlarmThresholdTimeOffset=[UINT16]) |
|
Variable fields |
$1: Offset between the PTP time and the external reference time. $2: Offset threshold between the PTP time and the external reference time. |
|
Severity level |
4 |
|
Example |
PTP/4/PTP_TIME_OFFSET_EXCEED_THRESHOLD: The PTP time offset exceeded the threshold. (TimeOffset=500, AlarmThresholdTimeOffset=400) |
|
Explanation |
The offset between the PTP time and the external reference time exceeded the threshold. |
|
Recommended action |
Execute the ptp asymmetry-correction command to set the asymmetric delay correction time so that the PTP time is consistent with the external reference time. Then identify whether a PTP_TIME_OFFSET_RECOVER log has been output. · If a PTP_TIME_OFFSET_RECOVER log has been output, the issue is resolved. · If no PTP_TIME_OFFSET_RECOVER log is output, collect log and configuration information and contact the support. |
PTP_TIME_OFFSET_RECOVER
|
Message text |
The PTP standard time offset resumed. (TimeOffset=[UINT16], AlarmThresholdTimeOffset=[UINT16]) |
|
Variable fields |
$1: Offset between the PTP time and the external reference time. $2: Offset threshold between the PTP time and the external reference time. |
|
Severity level |
4 |
|
Example |
PTP/4/PTP_STANDARD_TIME_OFFSET_RECOVER: The PTP standard time offset resumed. (TimeOffset=300, AlarmThresholdTimeOffset=400) |
|
Explanation |
The PTP time resumed from large offset with the external reference time. |
|
Recommended action |
No action is required. |
PTP_TIME_SYNC
|
Message text |
Time resumed to synchronized state. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
PTP/4/PTP_TIME_SYNC: Time resumed to synchronized state. |
|
Explanation |
The device time has been synchronized. |
|
Recommended action |
No action is required. |
PTP_TIME_UNSYNC
|
Message text |
Time changed to unsynchronized state. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
PTP/4/PTP_TIME_UNSYNC: Time changed to unsynchronized state. |
|
Explanation |
The device time is not synchronized. Possible reasons include: · The device failed to trace a clock source because of link or interface failure. · The clock source of the device has a priority so high that the device cannot synchronize time to another device. |
|
Recommended action |
1. Execute the display ptp interface brief command to identify whether a PTP subordinate port is available ¡ If a PTP subordinate port is available, contact the support. ¡ If no PTP subordinate port is available, go to step 2. 2. Execute the display ptp clock command to identify whether the clock type is ToD. ¡ If the clock type is ToD, go to step 3. ¡ If the clock type is not ToD, no clock source is available for the device. 3. Identify whether the ptp { tod0 | tod1 } input command has been executed to enable the device to receive signals from a ToD clock. ¡ If this configuration exists, contact the support. ¡ If no such configuration exists, go to step 4. 4. Execute the ptp { tod0 | tod1 } input command to specify the input direction for the device to receive ToD clock signals. Then identify whether a PTP_TIME_SYNC log has been output. ¡ If a PTP_TIME_SYNC log has been output, the issue is resolved. ¡ If no PTP_TIME_SYNC log is output, collect log and configuration information and contact the support. |
PTP_TIMESTAMP_CHANGE
|
Message text |
The timestamp state turned to normal. |
|
Variable fields |
N/A |
|
Severity level |
3 |
|
Example |
PTP/3/PTP_TIMESTAMP_CHANGE: The timestamp state turned to normal. |
|
Explanation |
The timestamp state resumed from remaining unchanged. |
|
Recommended action |
No action is required. |
PTP_TIMESTAMP_UNCHANGE
|
Message text |
The timestamp state turned to abnormal. |
|
Variable fields |
N/A |
|
Severity level |
3 |
|
Example |
PTP/3/PTP_TIMESTAMP_UNCHANGE: The timestamp state turned to abnormal. |
|
Explanation |
The timestamps in the PTP messages received by the device remained unchanged. |
|
Recommended action |
Execute the display ptp statistics command to identify whether the count of Sync messages is increasing. · If the count is increasing, collect log and configuration information and contact the support. · If the count is not increasing, check the link for errors. Fix the error if any and identify whether a PTP_TIMESTAMP_CHANGED log has been output. ¡ If a PTP_TIMESTAMP_CHANGED log has been output, the timestamp state has resumed. ¡ If no PTP_TIMESTAMP_CHANGED log is output, collect log and configuration information and contact the support. |
PTP_TIMOFFSUM_PK-PK_ALARM
|
Message text |
The PTP time offset sum exceeded the threshold. (TimeOffsetSum=[UINT16], TimeOffsetSumAlarmThreshold=[UINT16]) |
|
Variable fields |
$1: PTP time-offset-sum peak-to-peak value. $2: PTP time-offset-sum peak-to-peak threshold. |
|
Severity level |
4 |
|
Example |
PTP/4/PTP_TIMOFFSUM_PK-PK_ALARM: The PTP time offset sum exceeded the threshold. (TimeOffsetSum=500, TimeOffsetSumAlarmThreshold=400) |
|
Explanation |
The PTP time-offset-sum peak-to-peak value exceeded the threshold. |
|
Recommended action |
To resolve the issue: 1. Determine whether the PTP time is in locked state. ¡ If the PTP time is in locked state, go to 3. ¡ If the PTP time is in unlocked state, go to 2. 2. Wait 15 minutes. Then determine whether the PTP time is in locked state. ¡ If the PTP time is in locked state, go to 3. ¡ If the PTP time is in unlocked state, go to 4. 3. Wait 15 minutes. Then identify whether a PTP_TIMOFFSUM_RECOVER log has been output. ¡ If a PTP_TIMOFFSUM_RECOVER log has been output, the issue is resolved. ¡ If no PTP_TIMOFFSUM_RECOVER log has been output, go to 4. 4. Collect alarm, log, and configuration information and contact the support. |
PTP_TIMOFFSUM_PK-PK_RECOVER
|
Message text |
The PTP time offset sum resumed. (TimeOffsetSum=[UINT16], TimeOffsetSumAlarmThreshold=[UINT16]) |
|
Variable fields |
$1: PTP time-offset-sum peak-to-peak value. $2: PTP time-offset-sum peak-to-peak threshold. |
|
Severity level |
4 |
|
Example |
PTP/4/PTP_TIMOFFSUM_PK-PK_RECOVER: The PTP time offset sum resumed. (TimeOffsetSum=300, TimeOffsetSumAlarmThreshold=400) |
|
Explanation |
The PTP time-offset-sum peak-to-peak value dropped below the threshold. |
|
Recommended action |
No action is required. |
PTS
This section contains Platform Trust Services (PTS) messages.
PTS_AK_AUTH_FAILED
|
Message text |
Inconsistent authorization data for attestation key [STRING]. |
|
Variable fields |
$1: AK name. |
|
Severity level |
4 |
|
Example |
PTS/4/PTS_AK_AUTH_FAILED: Inconsistent authorization data for attestation key abc. |
|
Explanation |
The authorization data specified for the integrity report attestation-key command is different from the authorization data specified for the AK when the AK was created. The command for creating a key is key create. |
|
Recommended action |
Specify the same authorization data for the integrity report attestation-key command as the authorization data you specified when you created the key. |
PTS_AK_INVALID
|
Message text |
The attestation key [STRING] is incorrect. |
|
Variable fields |
$1: AK name. |
|
Severity level |
4 |
|
Example |
PTS/4/PTS_AK_INVALID: The attestation key abc is incorrect. |
|
Explanation |
The specified AK is invalid. |
|
Recommended action |
Specify a valid AK for TC reporting. |
PTS_AK_NO_CERT
|
Message text |
No certificate file found for attestation key [STRING]. |
|
Variable fields |
$1: AK name. |
|
Severity level |
4 |
|
Example |
PTS/4/PTS_AK_NO_CERT: No certificate file found for attestation key abc. |
|
Explanation |
No certificate was found for the AK. |
|
Recommended action |
Use the manager to sign an AK certificate for the AK of the device. |
PTS_AK_NO_EXIST
|
Message text |
Attestation key [STRING] doesn't exist. |
|
Variable fields |
$1: AK name. |
|
Severity level |
4 |
|
Example |
PTS/4/PTS_AK_NO_EXIST: The attestation key abc doesn't exist. |
|
Explanation |
The AK does not exist. |
|
Recommended action |
Use the key create command to create the AK. |
PTS_AK_NO_LOAD
|
Message text |
The attestation key [STRING] is not loaded. |
|
Variable fields |
$1: AK name. |
|
Severity level |
4 |
|
Example |
PTS/4/PTS_AK_NO_LOAD: The attestation key abc is not loaded. |
|
Explanation |
The AK is not loaded to the TC chip. |
|
Recommended action |
Use the key load command to load the AK to the TC chip. |
PTS_BTW_PCR_FAILED
|
Message text |
Hash value computed based on BootWare IML is not consistent with that in PCR ([UINT]). |
|
Variable fields |
$1: PCR index. |
|
Severity level |
4 |
|
Example |
PTS/4/PTS_BTW_PCR_FAILED: Hash value computed based on BootWare IML is not consistent with that in PCR(0). |
|
Explanation |
The hash value computed by using the BootWare IML for the basic or extended segment is different from the hash value stored in the PCR. The BootWare is not trustworthy. |
|
Recommended action |
Contact H3C Support. |
PTS_CHECK_RM_VERSION_FAILED
|
Message text |
Version the RM file [STRING] is not supported. |
|
Variable fields |
$1: RM file name. |
|
Severity level |
4 |
|
Example |
PTS/4/PTS_CHECK_RM_VERSION_FAILED: Version the RM file BOOTWARE_BASIC_52B.rm is not supported. |
|
Explanation |
The device does not support the RM file version. |
|
Recommended action |
Contact H3C Support. |
PTS_CREATE_AGED_TIMER_FAILED
|
Message text |
Failed to create PTS session ageing timer. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
PTS/4/PTS_CREATE_AGED_TIMER_FAILED: Failed to create PTS session ageing timer. |
|
Explanation |
PTS failed to create the session aging timer. |
|
Recommended action |
1. Execute the undo pts command and the pts command in turn to restart the PTS service. 2. If the issue persists, contact H3C Support. |
PTS_CREATE_CHECK_TIMER_FAILED
|
Message text |
Failed to create server check timer. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
PTS/4/PTS_CREATE_CHECK_TIMER_FAILED: Failed to create server check timer. |
|
Explanation |
PTS failed to create the server check timer. |
|
Recommended action |
1. Execute the undo pts command and the pts command in turn to restart the PTS service. 2. If the issue persists, contact H3C Support. |
PTS_CREATE_CONTEXT_FAILED
|
Message text |
Failed to create TSS context. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
PTS/4/PTS_CREATE_CONTEXT_FAILED: Failed to create TSS context. |
|
Explanation |
PTS failed to create the TPM software stack context. |
|
Recommended action |
Contact H3C Support. |
PTS_CREATE_EPOLL_FAILED
|
Message text |
Failed to create epoll service. |
|
Variable fields |
N/A |
|
Severity level |
3 |
|
Example |
PTS/3/PTS_CREATE_EPOLL_FAILED: Failed to create epoll service. |
|
Explanation |
PTS failed to create the epoll service. |
|
Recommended action |
3. Execute the undo pts command and the pts command in turn to restart the PTS service. 1. If the issue persists, contact H3C Support. |
PTS_CREATE_HASH_FAILED
|
Message text |
Failed to create hash table. |
|
Variable fields |
N/A |
|
Severity level |
3 |
|
Example |
PTS/3/PTS_CREATE_HASH_FAILED: Failed to create hash table. |
|
Explanation |
PTS failed to create the hash table. |
|
Recommended action |
2. Execute the undo pts command and the pts command in turn to restart the PTS service. 1. If the issue persists, contact H3C Support. |
PTS_CREATE_SELFVERIFY_COUNTER_FAILED
|
Message text |
Failed to create selfverify counter. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
PTS/4/PTS_CREATE_SELFVERIFY_COUNTER_FAILED: Failed to create selfverify counter. |
|
Explanation |
PTS failed to create the integrity self-verification IML counter. The integrity self-verification feature is not available. |
|
Recommended action |
2. Execute the undo pts command and the pts command in turn to restart the PTS service. 1. If the issue persists, contact H3C Support. |
PTS_CREATE_SELFVERIFY_TIMER_FAILED
|
Message text |
Failed to create selfverify timer. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
PTS/4/PTS_CREATE_SELFVERIFY_TIMER_FAILED: Failed to create selfverify timer. |
|
Explanation |
PTS failed to create the integrity self-verification timer. The periodic integrity self-verification feature is not available. |
|
Recommended action |
· Contact H3C Support. · Use the integrity selfverify command to manually perform an integrity self-verification. |
PTS_CREATE_SOCKET_FAILED
|
Message text |
Failed to create socket service. |
|
Variable fields |
N/A |
|
Severity level |
3 |
|
Example |
PTS/3/PTS_CREATE_SOCKET_FAILED: Failed to create socket service. |
|
Explanation |
PTS failed to create the socket service. |
|
Recommended action |
2. Execute the undo pts command and the pts command in turn to restart the PTS service. 3. If the issue persists, contact H3C Support. |
PTS_CREATE_TIMER_FAILED
|
Message text |
Failed to create timer. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
PTS/4/PTS_CREATE_TIMER_FAILED: Failed to create timer. |
|
Explanation |
PTS failed to create a timer. PTS generates this log message whenever it fails to create a timer. |
|
Recommended action |
1. Execute the undo pts command and the pts command in turn to restart the PTS service. 2. If the issue persists, contact H3C Support. |
PTS_FILE_HASH_FAILED
|
Message text |
Hash value of file [STRING] is not consistent with that in the RM file. |
|
Variable fields |
$1: Name of the file of which you want to measure the integrity. |
|
Severity level |
4 |
|
Example |
PTS/4/PTS_FILE_HASH_FAILED: Hash value of file /sbin/ls is not consistent with that in the RM file. |
|
Explanation |
The hash value computed for the specified file is different from the hash value of the file stored in the RM file. The file is not trustworthy. |
|
Recommended action |
Contact H3C Support. |
PTS_LOAD_KEY_FAILED
|
Message text |
Failed to load attestation key [STRING]. |
|
Variable fields |
$1: AK name. |
|
Severity level |
4 |
|
Example |
PTS/4/PTS_LOAD_KEY_FAILED: Failed to load attestation key abc. |
|
Explanation |
PTS failed to load the AK name to the TPM. |
|
Recommended action |
3. Verify that the AK exists and is enabled. To display AK information, use the display tcsm key name command. 1. If the issue persists, contact H3C Support. |
PTS_PARSE_IML_FAILED
|
Message text |
Failed to parse IML. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
PTS/4/PTS_PARSE_IML_FAILED: Failed to parse IML. |
|
Explanation |
PTS failed to parse an IML. |
|
Recommended action |
2. Execute the undo pts command and the pts command in turn to restart the PTS service. 1. If the issue persists, contact H3C Support. |
PTS_PKG_PCR_FAILED
|
Message text |
Hash value computed based on Package IML is not consistent with that in PCR ([UINT]). |
|
Variable fields |
$1: PCR index. |
|
Severity level |
4 |
|
Example |
PTS/4/PTS_PKG_PCR_FAILED: Hash value computed based on Package IML is not consistent with that in PCR (12). |
|
Explanation |
The hash value computed by using the Comware image IML is different from the hash value stored in the PCR. The Comware images are not trustworthy. |
|
Recommended action |
Contact H3C Support. |
PTS_READ_PCR_FAILED
|
Message text |
Failed to read PCR ([UINT]). |
|
Variable fields |
$1: PCR index. |
|
Severity level |
4 |
|
Example |
PTS/4/PTS_READ_PCR_FAILED: Failed to read PCR(0). |
|
Explanation |
PTS failed to read PCR data. |
|
Recommended action |
Contact H3C Support. |
PTS_RM_FILE_FAILED
|
Message text |
Wrong signature for RM file [STRING]. |
|
Variable fields |
$1: RM file name. |
|
Severity level |
4 |
|
Example |
PTS/4/PTS_RM_FILE_FAILED: Wrong signature for RM file BOOTWARE_BASIC_52B.rm. |
|
Explanation |
The signature for the RM file is incorrect. |
|
Recommended action |
Contact H3C Support. |
PTS_RUNTIME_PCR_FAILED
|
Message text |
Hash value computed based on runtime IML is not consistent with that in PCR ([UINT]). |
|
Variable fields |
$1: PCR index. |
|
Severity level |
4 |
|
Example |
PTS/4/PTS_RUNTIME_PCR_FAILED: Hash value computed based on runtime IML is not consistent with that in PCR (10). |
|
Explanation |
The hash value computed by using the runtime IML is different from the hash value stored in the PCR. The runtime-related executable files are not trustworthy. |
|
Recommended action |
Contact H3C Support. |
PTS_SELFVERIFY_FAILED
|
Message text |
Failed to start integrity selfverify. Reason: TPM doesn't exist or isn't enabled. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
PTS/4/PTS_SELFVERIFY_FAILED: Failed to start integrity selfverify because TPM does not exist or is not enabled. |
|
Explanation |
Because the TPM did not exist or was disabled, the integrity self-verification failed. |
|
Recommended action |
Verify that the TPM is available. To display relevant information, use the display tcsm trusted-computing-chip command. |
PTS_SELFVERIFY_START_FAILED
|
Message text |
Failed to start selfverify. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
PTS/4/PTS_SELFVERIFY_START_FAILED: Failed to start selfverify. |
|
Explanation |
PTS failed to start integrity self-verification. |
|
Recommended action |
2. Start integrity self-verification again. 1. If the issue persists, contact H3C Support. |
PTS_TEMPLATE_HASH_FAILED
|
Message text |
Calculated template hash value of [STRING] is not consistent with that in IML. |
|
Variable fields |
$1: Name of the file of which you want to measure the integrity. |
|
Severity level |
4 |
|
Example |
PTS/4/PTS_TEMPLATE_HASH_FAILED: Calculated template hash value of /sbin/ls is not consistent with that in IML. |
|
Explanation |
The template hash value computed by using parameters including the measurement time and the hash value of the program file is different from the template hash value in the IML. The IML might have been tempered with. |
|
Recommended action |
Contact H3C Support. |
PWDCTL messages
This section contains password control messages.
PWDCTL_ADD_BLACKLIST
|
Message text |
User [STRING] from [STRING] was added to the blacklist for failed login attempts. |
|
Variable fields |
$1: Username. $2: User IP address. |
|
Severity level |
6 |
|
Example |
PWDCTL/6/PWDCTL_ADD_BLACKLIST: User hhh from 1.1.1.1 was added to the blacklist for failed login attempts. |
|
Explanation |
The user entered an incorrect password, the user access type is incompatible, or the user is not activated. The user 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_DELETE_BLACKLIST
|
Message text |
User [STRING] was deleted from the blacklist. |
|
Variable fields |
$1: Username. |
|
Severity level |
6 |
|
Example |
PWDCTL/6/PWDCTL_DELETE_BLACLIST: User hhh was deleted from the blacklist. |
|
Explanation |
The user account is removed from the blacklist or the reset password-control blacklist command is executed to remove the user account from the blacklist. |
|
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. |
PWDCTL_NOENOUGHSPACE
|
Message text |
Not enough free space on the storage media where the file is located. |
|
Variable fields |
N/A |
|
Severity level |
3 |
|
Example |
PWDCTL/3/PWDCTL_NOENOUGHSPACE: Not enough free space on the storage media where the file is located. |
|
Explanation |
The operation failed, because not enough memory space is available on the storage media (such as the flash or CF card) where the .dat file is located. |
|
Recommended action |
Execute the dir command in user view to identify the current free storage space in the system. · If the free storage space is too small, delete unnecessary files to release the space. · If the free storage space is enough, collect alarm information, log information, and configuration information, and then contact H3C Support. |
PWDCTL_UPDATETIME
|
Message text |
Last login time updated after clock update. |
|
Variable fields |
N/A |
|
Severity level |
6 |
|
Example |
PWDCTL/6/PWDCTL_UPDATETIME: Last login time updated after clock update. |
|
Explanation |
This message is sent when the last login time is updated. |
|
Recommended action |
No action is required. |
PWDCTL_USER_INLOCKING
|
Message text |
User [STRING] has been locked due to exceeding the maximum number of login attempts. |
|
Variable fields |
$1: Username. |
|
Severity level |
6 |
|
Example |
PWDCTL/6/PWDCTL_USER_INLOCKING: User hhh has been locked due to exceeding the maximum number of login attempts. |
|
Explanation |
This message is generated when a user attempts to log in during the locking period after reaching the maximum number of login failures. |
|
Recommended action |
Identify whether the user account is locked because the number of login attempts has reached the limit: · If yes, try to log in again after the locking timer expires, or execute the reset password-control blacklist command to remove the user account from the blacklist. · If not, contact the administrator. |
PWDCTL_USER_LOCK
|
Message text |
User [STRING] was [STRING] because the maximum number of login attempts was exceeded. |
|
Variable fields |
$1: Username. $2: Action to be taken on a user account when the user has made the maximum number of login attempts: · locked for lock-time minutes—Locks the user account for a time period and allows to the user account to log in again after the time period expires. · permanently locked—Locks the user account forever. |
|
Severity level |
6 |
|
Example |
1. PWDCTL/6/PWDCTL_USER_LOCK: User hhh was locked for 1 minute because the maximum number of login attempts was exceeded. 2. PWDCTL/3/PWDCTL_LOCKBLACKLIST: User hhh was permanently locked because the maximum number of login attempts was exceeded. |
|
Explanation |
After the maximum number login attempts have been made, the device locks the user account depends on the password-control login-attempt command. |
|
Recommended action |
Identify whether the user account is locked because the number of login attempts has reached the limit: · If yes, try to log in again after the locking timer expires, or execute the reset password-control blacklist command to remove the user account from the blacklist. · If not, contact the administrator. |
PWDCTL_USER_UNLOCK
|
Message text |
User [STRING] was unlocked when the lock time expired. |
|
Variable fields |
$1: Username. |
|
Severity level |
6 |
|
Example |
PWDCTL/6/PWDCTL_USER_UNLOCK: User hhh was unlocked when the lock time expired. |
|
Explanation |
The user account is unlocked because the locking timer expires. |
|
Recommended action |
No action is required. |
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_BANDWIDTH_TOTALCHANNEL
|
Message text |
Failed to set the interface bandwidth for interface [STRING] because the interface bandwidth is less than the total channel bandwidth. |
|
Variable fields |
$1: Interface name. |
|
Severity level |
4 |
|
Example |
QOS/4/QOS_BANDWIDTH_TOTALCHANNEL: Failed to set the interface bandwidth for interface GigabitEthernet4/0/1 because the interface bandwidth is less than the total channel bandwidth. |
|
Explanation |
This message is generated when the bandwidth of the main interface is smaller than the total channelized bandwidth of subinterfaces. |
|
Recommended action |
Increase the bandwidth of the main interface or reduce the total channelized bandwidth of subinterfaces. |
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_CHANNEL_APPLYIF_FAIL
|
Message text |
Failed to set the channel bandwidth on interface [STRING] because the total channel bandwidth exceeds the interface bandwidth. |
|
Variable fields |
$1: Interface name. |
|
Severity level |
3 |
|
Example |
QOS/3/QOS_CHANNEL_APPLYIF_FAIL: Failed to set the channel bandwidth on interface GigabitEthernet4/0/1 because the total channel bandwidth exceeds the interface bandwidth. |
|
Explanation |
This message is generated when the total channelized bandwidth exceeds the interface bandwidth. |
|
Recommended action |
Increase the bandwidth of the main interface or reduce the total channelized bandwidth of subinterfaces. |
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_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_APPLYTUN_FAIL
|
Message text |
Failed to apply or refresh QoS policy [STRING] to [STRING]. Reason: [STRING]. |
|
Variable fields |
$1: Policy name. $2: Tunnel information. $3: Failure cause: ¡ The filtering action is not supported. ¡ The marking action is not supported. ¡ The mirroring action is not supported. ¡ The redirect action is not supported. ¡ The QoS policy does not exist. ¡ The QoS policy was deleted. |
|
Severity level |
4 |
|
Example |
QOS/4/QOS_POLICY_APPLYTUN_FAIL: Failed to apply or refresh QoS policy b to ADVPN session Tunnel1 192.168.0.10. Reason: The marking action is not supported. |
|
Explanation |
The system failed to perform one of the following actions: · Apply a QoS policy to an ADVPN tunnel. · Update a QoS policy applied to an ADVPN tunnel. |
|
Recommended action |
Modify the configuration of the QoS policy according to the failure cause. |
QOS_POLICY_APPLYTUN_SUCCESS
|
Message text |
QoS policy [STRING] was successfully applied or refreshed to [STRING]. |
|
Variable fields |
$1: Policy name. $2: Tunnel information. |
|
Severity level |
4 |
|
Example |
QOS/4/QOS_POLICY_APPLYTUN_SUCCESS: QoS policy b was successfully applied or refreshed to ADVPN session Tunnel1 192.168.0.10. |
|
Explanation |
The system successfully applied or refreshed a QoS policy for an ADVPN tunnel. |
|
Recommended action |
No action is required. |
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_ACCT_SERVER_DOWN
|
Message text |
RADIUS accounting server was blocked: Server IP=[STRING], port=[UINT32], VPN instance=[STRING]. |
|
Variable fields |
$1: IP address of the accounting server. $2: Port number of the accounting server. $3: VPN instance name. This field displays public if the server belongs to the public network. |
|
Severity level |
4 |
|
Example |
RADIUS/4/RADIUS_ACCT_SERVER_DOWN: RADIUS accounting server was blocked: Server IP=1.1.1.1, port=1812, VPN instance=public. |
|
Explanation |
An accounting server became blocked. |
|
Recommended action |
1. Verify that the accounting server has started up. 2. Ping the accounting server to verify that the server is reachable. If the server is not reachable, check the link for connectivity issues and resolve the issues. 3. Collect logs and diagnostic logs, and then contact H3C Support. |
RADIUS_ACCT_SERVER_UP
|
Message text |
RADIUS accounting server became active: Server IP=[STRING], port=[UINT32], VPN instance=[STRING]. |
|
Variable fields |
$1: IP address of the accounting server. $2: Port number of the accounting server. $3: VPN instance name. This field displays public if the server belongs to the public network. |
|
Severity level |
6 |
|
Example |
RADIUS/6/RADIUS_ACCT_SERVER_UP: RADIUS accounting server became active: Server IP=1.1.1.1, port=1812, VPN instance=public. |
|
Explanation |
An accounting server became active. |
|
Recommended action |
No action is required. |
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_SERVER_DOWN
|
Message text |
RADIUS authentication server was blocked: Server IP=[STRING], port=[UINT32], VPN instance=[STRING]. |
|
Variable fields |
$1: IP address of the authentication server. $2: Port number of the authentication server. $3: VPN instance name. This field displays public if the server belongs to the public network. |
|
Severity level |
4 |
|
Example |
RADIUS/4/RADIUS_AUTH_SERVER_DOWN: RADIUS authentication server was blocked: Server IP= 1.1.1.1, port=1812, VPN instance=public. |
|
Explanation |
An authentication server became blocked. |
|
Recommended action |
1. Verify that the authentication server has started up. 2. Ping the authentication server to verify that the server is reachable. If the server is not reachable, check the link for connectivity issues and resolve the issues. 3. Collect logs and diagnostic logs, and then contact H3C Support. |
RADIUS_AUTH_SERVER_UP
|
Message text |
RADIUS authentication server became active: Server IP=[STRING], port=[UINT32], VPN instance=[STRING]. |
|
Variable fields |
$1: IP address of the authentication server. $2: Port number of the authentication server. $3: VPN instance name. This field displays public if the server belongs to the public network. |
|
Severity level |
6 |
|
Example |
RADIUS/6/RADIUS_AUTH_SERVER_UP: RADIUS authentication server became active: Server IP=1.1.1.1, port=1812, VPN instance=public. |
|
Explanation |
An authentication server became active. |
|
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. |
RBM messages
This section contains RBM messages for the HA group module.
RBM_CFG_BATCH_SYNC
|
Message text |
Configuration synchronization message cache overflowed. The system will execute configuration synchronization again. |
|
Variable fields |
N/A |
|
Severity level |
5 |
|
Example |
RBM/5/RBM_CFG_BATCH_SYNC: -Context=1; Configuration synchronization message cache overflowed. The system will execute configuration synchronization again. |
|
Explanation |
Configuration backup failed because of configuration synchronization message cache overflow. The system will synchronize configuration again. |
|
Recommended action |
No action is required. |
RBM_CFG_BATCH_SYNC_FAILED
|
Message text |
Configuration synchronization failed [STRING]. |
|
Variable fields |
$1: Cause of configuration synchronization failure: · because of an exception in sending configuration files · because of a configuration file validation error. Please perform configuration synchronization again · because both devices had the primary role |
|
Severity level |
3 |
|
Example |
RBM/3/RBM_CFG_BATCH_SYNC_FAILED: -Context=1; Configuration synchronization failed because of an exception in sending configuration files. |
|
Explanation |
The device failed to synchronize configuration with a peer. |
|
Recommended action |
Manually back up configuration to the peer or configure the local or peer device as a secondary device in accordance to the failure cause. |
RBM_CFG_BATCH_SYNC_FINISH
|
Message text |
Finished batch configuration synchronization. |
|
Variable fields |
N/A |
|
Severity level |
6 |
|
Example |
RBM/6/RBM_CFG_BATCH_SYNC_FINISH: -Context=1; Finished batch configuration synchronization. |
|
Explanation |
Bulk configuration synchronization finished. |
|
Recommended action |
No action is required. |
RBM_CFG_BATCH_SYNC_START
|
Message text |
Started batch configuration synchronization. |
|
Variable fields |
N/A |
|
Severity level |
6 |
|
Example |
RBM/6/RBM_CFG_BATCH_SYNC_START: -Context=1; Started batch configuration synchronization. |
|
Explanation |
The device started to bulk back up configuration to the peer. |
|
Recommended action |
Do not perform any operation on the device during bulk configuration backup. |
RBM_CFG_COMPARE_FAILED
|
Message text |
Configuration consistency check failed because of an exception in sending configuration files. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
RBM/4/RBM_CFG_COMPARE_FAILED: -Context=1; Configuration consistency check failed because of an exception in sending configuration files. |
|
Explanation |
Configuration consistency check failed because an exception occurred in sending configuration files. |
|
Recommended action |
Manually perform configuration consistency check. |
RBM_CFG_COMPARE_FINISH
|
Message text |
Finished configuration consistency check. |
|
Variable fields |
N/A |
|
Severity level |
6 |
|
Example |
RBM/6/RBM_CFG_COMPARE_FINISH:Finished configuration consistency check. |
|
Explanation |
The configuration consistency check finished. |
|
Recommended action |
No action is required. |
RBM_CFG_COMPARE_RESULT
|
Message text |
The following modules have inconsistent configuration: [STRING]. |
|
Variable fields |
$1: Module name. |
|
Severity level |
6 |
|
Example |
RBM/6/RBM_CFG_COMPARE_RESULT: The following modules have inconsistent configuration: NAT. |
|
Explanation |
The configuration consistency check result was displayed. |
|
Recommended action |
No action is required. |
RBM_CFG_COMPARE_START
|
Message text |
Started configuration consistency check. |
|
Variable fields |
N/A |
|
Severity level |
6 |
|
Example |
BM/6/RBM_CFG_COMPARE_START:Started configuration consistency check. |
|
Explanation |
The configuration consistency check started. |
|
Recommended action |
No action is required. |
RBM_CFG_CONFLICT
|
Message text |
VLAN or interface monitoring configuration exists. For the HA group to collaborate with VRRP and routing protocols, first delete the VLAN or interface monitoring configuration. |
|
Variable fields |
N/A |
|
Severity level |
1 |
|
Example |
RBM/1/ RBM_CFG_CONFLICT: -Context=1; VLAN or interface monitoring configuration exists. For the HA group to collaborate with VRRP and routing protocols, first delete the VLAN or interface monitoring configuration. |
|
Explanation |
The HA group cannot collaborate with VRRP and routing protocols because VLAN or interface monitoring configuration exists. |
|
Recommended action |
Delete the VLAN or interface monitoring configuration. |
RBM_CFG_ROLLBCK
|
Message text |
Please perform configuration synchronization after configuration rollback is finished. |
|
Variable fields |
N/A |
|
Severity level |
6 |
|
Example |
RBM/6/RBM_CFG_ROLLBCK: -Context=1; Please perform configuration synchronization after configuration rollback is finished. |
|
Explanation |
Configuration rollback finished. |
|
Recommended action |
Perform configuration synchronization |
RBM_CLUSTER_CTRL_CHANNEL_CLOSED
|
Message text |
Disconnected the HA cluster UDP control channel. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
RBM/4/RBM_CLUSTER_CTRL_CHANNEL_CLOSED: -Context=1; Disconnected the HA cluster UDP control channel. |
|
Explanation |
The RBM control channel was disconnected. |
|
Recommended action |
Verify that the required HA cluster settings are configured. |
RBM_CLUSTER_CTRL_CHANNEL_CREATED
|
Message text |
Set up the HA cluster UDP control channel by using IP address [STRING] and port [STRING]. |
|
Variable fields |
$1: IP address. $2: Port number. |
|
Severity level |
6 |
|
Example |
RBM/6/RBM_CLUSTER_CTRL_CHANNEL_CREATED: -Context=1; Set up the HA cluster UDP control channel by using IP address 1.1.1.2 and port 60068. |
|
Explanation |
The RBM control channel was set up successfully. |
|
Recommended action |
No action is required. |
RBM_CLUSTER_CTRL_CHANNEL_FAILED
|
Message text |
Failed to configure IP address [STRING] and port [STRING] for the RBM UDP control channel. |
|
Variable fields |
$1: IP address. $2: Port number. |
|
Severity level |
3 |
|
Example |
RBM/3/RBM_CLUSTER_CTRL_CHANNEL_FAILED: -Context=1; Failed to configure IP address 1.1.1.2 and port 60068 for the RBM UDP control. |
|
Explanation |
RBM control channel setup failed, because the port number is used by other applications. |
|
Recommended action |
Modify the local IP address used for setting up the RBM control channel. |
RBM_CLUSTER_ELECT_ACTIVE
|
Message text |
Traffic group [STRING] became active. |
|
Variable fields |
$1: Traffic group ID. |
|
Severity level |
6 |
|
Example |
RBM/6/RBM_CLUSTER_ELECT_ACTIVE: -Context=1; Traffic group 1 became active. |
|
Explanation |
The local device became active in a traffic group. |
|
Recommended action |
No action is required. |
RBM_CLUSTER_ELECT_PRIMARY
|
Message text |
Cluster node [STRING] became the primary device in the cluster. |
|
Variable fields |
$1: Cluster member ID. |
|
Severity level |
6 |
|
Example |
RBM/6/RBM_CLUSTER_ELECT_PRIMARY: -Context=1; Cluster node 1 became the primary device in the cluster. |
|
Explanation |
A cluster member device became the primary device in the HA cluster. |
|
Recommended action |
No action is required. |
RBM_CLUSTER_ELECT_SECONDARY
|
Message text |
Cluster node [STRING] became a secondary device in the cluster. |
|
Variable fields |
$1: Cluster member ID. |
|
Severity level |
6 |
|
Example |
RBM/6/RBM_CLUSTER_ELECT_SECONDARY: -Context=1; Cluster node 1 became a secondary device in the cluster. |
|
Explanation |
A cluster member device became a secondary device in the HA cluster. |
|
Recommended action |
No action is required. |
RBM_CLUSTER_ELECT_STANDBY
|
Message text |
Traffic group [STRING] became standby. |
|
Variable fields |
$1: Traffic group ID. |
|
Severity level |
6 |
|
Example |
RBM/6/RBM_CLUSTER_ELECT_STANDBY: -Context=1; Traffic group 1 became standby. |
|
Explanation |
The local device became standby in a traffic group. |
|
Recommended action |
No action is required. |
RBM_CLUSTER_NODE_CONFILICT
|
Message text |
Failed to add a cluster node. Node ID [STRING] is already in use. |
|
Variable fields |
$1: Cluster member ID. |
|
Severity level |
3 |
|
Example |
RBM/3/RBM_CLUSTER_NODE_CONFILICT: -Context=1; Failed to add a cluster node. Node ID 1 is already in use. |
|
Explanation |
A device failed to join the HA cluster, because its cluster member ID is already in use. |
|
Recommended action |
Modify the cluster member ID of the new cluster member device. |
RBM_CLUSTER_NODE_OFFLINE
|
Message text |
Cluster node [STRING] went offline. |
|
Variable fields |
$1: Cluster member ID. |
|
Severity level |
4 |
|
Example |
RBM/4/RBM_CLUSTER_NODE_OFFLINE: -Context=1; Cluster node 1 went offline. |
|
Explanation |
A cluster member device went offline. |
|
Recommended action |
Verify that the cluster member device has Layer 3 connectivity to the primary device. |
RBM_CTRL_CHANNEL_BIND_FAILED
|
Message text |
Failed to bind IP address [STRING] and port [STRING] to the RBM channel. |
|
Variable fields |
$1: IP address. $2: Port number. |
|
Severity level |
3 |
|
Example |
RBM/3/RBM_CTRL_CHANNEL_BIND_FAILED: -Context=1; Failed to bind IP address 1.1.1.2 and port 50001 to the RBM channel. |
|
Explanation |
Failed to bind the IP address and port number to the RBM channel. The port has been used by another application. |
|
Recommended action |
Modify the local IP address or the port number associated with the peer IP address. |
RBM_DATA_CHANNEL_IP
|
Message text |
Please assign an IP address to the interface used for setting up the data channel. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
RBM/4/RBM_DATA_CHANNEL_IP: -Context=1; Please assign an IP address to the interface used for setting up the data channel. |
|
Explanation |
No IP address is assigned to the interface used for setting up the data channel. |
|
Recommended action |
Assign an IP address to the interface used for setting up the data channel. |
RBM_DEVICE_ROLE_SAME
|
Message text |
The member devices have the same role. Please assign different roles to them. |
|
Variable fields |
N/A |
|
Severity level |
3 |
|
Example |
RBM/3/RBM_DEVICE_ROLE_SAME: -Context=1; The member devices have the same role. Please assign different roles to them. |
|
Explanation |
The device and its peer have the same HA role. |
|
Recommended action |
Assign different HA roles to the device and its peer. |
RBM_KEEPALIVE_IPV4
|
Message text |
Local IP=[STRING], remote IP=[STRING], port=[STRING], status=[STRING]. |
|
Variable fields |
$1: Local IPv4 address used for setting up the HA control channel. $2: Peer IPv4 address used for setting up the HA control channel. $3: Server-side port number used for setting up the HA control channel. $4: Status of the HA control channel. · Connected. · Disconnected. |
|
Severity level |
1 |
|
Example |
RBM/1/RBM_KEEPALIVE_IPV4: Local IP=1.1.1.1, remote IP=1.1.1.2, port=60064, status=Connected. |
|
Explanation |
The device displayed information about the HA control channel. |
|
Recommended action |
If the HA control channel is disconnected, verify that the local and peer IPv4 addresses are correct and verify network connectivity between the device and its peer. |
RBM_KEEPALIVE_IPV6
|
Message text |
Local IPv6=[STRING], remote IPv6=[STRING], port=[STRING], status=[STRING]. |
|
Variable fields |
$1: Local IPv6 address used for setting up the HA control channel. $2: Peer IPv6 address used for setting up the HA control channel. $3: Server-side port number used for setting up the HA control channel. $4: Status of the HA control channel. · Connected. · Disconnected. |
|
Severity level |
1 |
|
Example |
RBM/1/RBM_KEEPALIVE_IPV6: Local IPv6=2001::1, remote IPv6=2001::2, port=60064, status=Connected. |
|
Explanation |
The device displayed information about the HA control channel. |
|
Recommended action |
If the HA control channel is disconnected, verify that the local and peer IPv4 addresses are correct and verify network connectivity between the device and its peer. |
RBM_TRAFFIC_GROUP_SWITCHOVER
|
Message text |
In traffic group [STRING], the active role was switched to cluster node [STRING]. |
|
Variable fields |
$1: Traffic group ID. $1: Cluster member ID. |
|
Severity level |
6 |
|
Example |
RBM/6/RBM_TRAFFIC_GROUP_SWITCHOVER: -Context=1; In traffic group [STRING], the active role was switched to cluster node 1. |
|
Explanation |
The active role was manually switched to a cluster member device in a traffic group. |
|
Recommended action |
No action is required. |
RESMON
This section contains resource monitoring messages.
RESMON_MINOR
|
Message text |
-Resource=[STRING]-Total=[STRING]-Used=[STRING]-Free=[STRING]; Free resource decreased to or below minor threshold [STRING]. [STRING]. |
|
Variable fields |
$1: Resource type. $2: Total amount. $3: Used amount. $4: Available amount. $5: Minor resource depletion threshold. $6: Resource usage description. Some types of resources do not have description information. |
|
Severity level |
4 |
|
Example |
RESMON/4/RESMON_MINOR: -Resource=AA-Total=100%-Used=83%-Free=17%; Free resource decreased to or below minor threshold 20%. |
|
Explanation |
When the available resource amount decreases to or below the minor resource depletion threshold, the resource type enters minor alarm state and the device outputs this log message periodically. |
|
Recommended action |
Configure the device based on the resource type so the device allocates the type of resources reasonably. |
RESMON_MINOR_RECOVERY
|
Message text |
-Resource=[STRING]-Total=[STRING]-Used=[STRING]-Free=[STRING]; Free resource increased above minor threshold [STRING]. [STRING]. |
|
Variable fields |
$1: Resource type. $2: Total amount. $3: Used amount. $4: Available amount. $5: Minor resource depletion threshold. $6: Resource usage description. Some types of resources do not have description information. |
|
Severity level |
5 |
|
Example |
RESMON/5/RESMON_MINOR_RECOVER: -Resource=AA-Total=100%-Used=77%-Free=23%; Free resource increased above minor threshold 20%. |
|
Explanation |
When the available resource amount increases above the minor resource depletion threshold, the resource type enters recovered state. The device removes the minor resource depletion alarm and outputs this log message. |
|
Recommended action |
No action is required. |
RESMON_SEVERE
|
Message text |
-Resource=[STRING]-Total=[STRING]-Used=[STRING]-Free=[STRING]; Free resource decreased to or below severe threshold [STRING]. [STRING]. |
|
Variable fields |
$1: Resource type. $2: Total amount. $3: Used amount. $4: Available amount. $5: Severe resource depletion threshold. $6: Resource usage description. Some types of resources do not have description information. |
|
Severity level |
3 |
|
Example |
RESMON/3/RESMON_SEVERE: -Resource=AA-Total=100%-Used=93%-Free=7%; Free resource decreased to or below severe threshold 10%. |
|
Explanation |
When the available resource amount decreases to or below the severe resource depletion threshold, the resource type enters severe alarm state and the device outputs this log message periodically. |
|
Recommended action |
Configure the device based on the resource type so the device allocates the type of resources reasonably. |
RESMON_SEVERE_RECOVERY
|
Message text |
-Resource=[STRING]-Total=[STRING]-Used=[STRING]-Free=[STRING]; Free resource increased above severe threshold [STRING]. [STRING]. |
|
Variable fields |
$1: Resource type. $2: Total amount. $3: Used amount. $4: Available amount. $5: Severe resource depletion threshold. $6: Resource usage description. Some types of resources do not have description information. |
|
Severity level |
5 |
|
Example |
RESMON/5/RESMON_SEVERE_RECOVER: -Resource=AA-Total=100%-Used=83%-Free=17%; Free resource increased above severe threshold 10%. |
|
Explanation |
When the available resource amount increases above the severe resource depletion threshold, the device removes the severe resource depletion alarm and outputs this log message. |
|
Recommended action |
No action is required. |
RESMON_USEDUP
|
Message text |
-Resource=[STRING]-Total=[STRING]-Used=[STRING]-Free=[STRING]; Resources used up. [STRING]. |
|
Variable fields |
$1: Resource type. $2: Total amount. $3: Used amount. $4: Available amount. $5: Resource usage description. Some types of resources do not have description information. |
|
Severity level |
2 |
|
Example |
RESMON/2/RESMON_USEDUP: -Resource=vlaninterface-Total=2048-Used=2048-Free=0; Resources used up. |
|
Explanation |
When the available resource amount decreases to zero, the device outputs this log message periodically. |
|
Recommended action |
To ensure correct operation of the relevant services, immediately clear data or entries of the resource type that are not used. |
RESMON_USEDUP_RECOVERY
|
Message text |
-Resource=[STRING]-Total=[STRING]-Used=[STRING]-Free=[STRING]; The amount of free resources increased from zero to a non-zero value. [STRING]. |
|
Variable fields |
$1: Resource type. $2: Total amount, which can be 100% or an integer for an absolute value. $3: Used amount, a percentage or an integer for an absolute value. $4: Available amount, a percentage or an integer for an absolute value. $5: Additional resource usage information. This field might be null. |
|
Severity level |
5 |
|
Example |
RESMON/5/RESMON_USEDUP_RECOVER: -Resource=vlaninterface-Total=2048-Used=2047-Free=1; The amount of free resources increased from zero to a non-zero value. |
|
Explanation |
When the available resource amount increases from zero, the device outputs this log message. |
|
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 |
1. Check for network attacks. 2. 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 |
1. Check for network attacks. 2. Reduce the number of routes. |
RIR
This section contains RIR messages.
RIR_APPQUAL_PROBE_FAILED
|
Message text |
Some SDWAN tunnels failed to start probe under the application quality probe instance(instance name [STRING], flow ID [UINT32]), because the maximum number of tunnels for application quality probe already reached. |
|
Variable fields |
$1: Name of an application quality probe instance. $2: Flow ID of the flow template enabled with application quality probe. |
|
Severity level |
4 |
|
Example |
RIR/4/RIR_APPQUAL_PROBE_FAILED: Some SDWAN tunnels failed to start probe under the application quality probe instance(instance name [STRING], flow ID [UINT32]), because the maximum number of tunnels for application quality probe already reached. |
|
Explanation |
Some SDWAN tunnels failed to start probe under an application quality probe instance, because the maximum number of tunnels for application quality probe already reached. |
|
Recommended action |
Stop application quality probe for tunnels if the probe is not necessary for the tunnels. |
RIR_BANDWIDTH_OVERUSED
|
Message text |
-Device=[IPADDR]-VPNInstance=[STRING]-Tunnel=[UINT32]-OutputInterface=[STRING]-TotalBandwidth=[UINT64] kbps-UsedBandwidth=[UINT64] kbps. The bandwidth usage of the tunnel interface has reached 90%. |
|
Variable fields |
$1: IP address of the device to which the tunnel interface belongs. ¡ If the tunnel interface belongs to the local device, the value for this field is 0.0.0.0. ¡ If the tunnel interface belongs to a peer device, the value for this field is the IP address of the peer device. $2: Name of the VPN instance to which the RIR collaboration relationship belongs. If the tunnel interface belongs to the local device or the peer device uses a public address to establish RIR collaboration relationship with the local device, this field displays N/A. $3: Tunnel interface number. $4: Output interface associated with the tunnel interface. $5: Total bandwidth of the tunnel interface. $6: Used bandwidth of the tunnel interface. |
|
Severity level |
4 |
|
Example |
RIR/4/RIR_BANDWIDTH_OVERUSED: -Device=1.1.1.1-VPNInstance=a-Tunnel=1-OutputInterface=GE1/0/1-TotalBandwidth=1000 kbps-UsedBandwidth=1000 kbps. The bandwidth usage of the tunnel interface has reached 90%. |
|
Explanation |
The bandwidth usage of a tunnel interface has reached 90%, and the device will perform link reselection. |
|
Recommended action |
If this message is generated frequently, increase the bandwidth of the tunnel interface. |
RIR_CFG_CHANGED
|
Message text |
RIR configuration (device [IPADDR], VPN instance [STRING]) changed. |
|
Variable fields |
$1: IP address of the device. For the local device, the value for this field is 0.0.0.0. $2: Name of the VPN instance to which the RIR collaboration relationship belongs. If the RIR configuration belongs to the local device or the peer device uses a public address to establish RIR collaboration relationship with the local device, this field displays N/A. |
|
Severity level |
6 |
|
Example |
RIR/6/RIR_CFG_CHANGED: RIR configuration (device 1.1.1.1, VPN instance a) changed. |
|
Explanation |
Any of the following configuration changes occurred: · Link index or link type change. · Link preference or link primary or backup role change. · Per-session expected bandwidth change. · Other configuration changes, for example, SLA configuration changes, that cause a link from qualified to unqualified or from unqualified to qualified for the service requirements. |
|
Recommended action |
No action is required. |
RIR_LINK_SELECT
|
Message text |
-SrcIPAddr=[IPADDR]-SrcPort=[UINT16]-DstIPAddr=[IPADDR]-DstPort=[UINT16]-Protocol=[STRING]-FlowID=[UINT32]. Selected a link (device [IPADDR], VPN instance [STRING], tunnel [UINT32]) for the session. |
|
Variable fields |
$1: Source IP address of the session. $2: Source port number of the session. $3: Destination IP address of the session. $4: Destination port number of the session. $5: Session protocol. Values: ¡ TCP. ¡ UDP. ¡ ICMP. ¡ IPv4. ¡ Other. $6: ID of the flow template to which the session belongs. $7: IP address of the device to which the tunnel interface belongs. ¡ If the tunnel interface belongs to the local device, the value for this field is 0.0.0.0. ¡ If the tunnel interface belongs to a peer device, the value for this field is the IP address of the peer device. $8: Name of the VPN instance to which the RIR collaboration relationship belongs. If the tunnel interface belongs to the local device or the peer device uses a public address to establish RIR collaboration relationship with the local device, this field displays N/A. $9: Tunnel interface number. |
|
Severity level |
6 |
|
Example |
RIR/6/RIR_LINK_SELECT: -SrcIPAddr=55.1.1.2-SrcPort=51457-DstIPAddr=11.1.1.1-DstPort=8-Protocol=ICMP-FlowID=1. Selected a link (device 1.1.1.1, VPN instance a, tunnel 1) for the session. |
|
Explanation |
RIR selected a link for the session. |
|
Recommended action |
No action is required. |
RIR_LINKFAULT
|
Message text |
The link (device [IPADDR], VPN instance [STRING], tunnel [UINT32]) became faulty. |
|
Variable fields |
$1: IP address of the device to which the tunnel interface belongs. ¡ If the tunnel interface belongs to the local device, the value for this field is 0.0.0.0. ¡ If the tunnel interface belongs to a peer device, the value for this field is the IP address of the peer device. $2: Name of the VPN instance to which the RIR collaboration relationship belongs. If the tunnel interface belongs to the local device or the peer device uses a public address to establish RIR collaboration relationship with the local device, this field displays N/A. $3: Tunnel interface number. |
|
Severity level |
4 |
|
Example |
RIR/4/RIR_LINKFAULT: The link (device 1.1.1.1, VPN instance a, tunnel 1) became faulty. |
|
Explanation |
NQA link connectivity probe detected that the link was disconnected or in down state. |
|
Recommended action |
No action is required. |
RIR_OUTIF_BANDWIDTH_OVERUSED
|
Message text |
-Device=[IPADDR]-VPNInstance=[STRING]-OutputInterface=[STRING]-TotalBandwidth=[UINT64] kbps-UsedBandwidth=[UINT64] kbps. The bandwidth usage of the output interface has reached 90%. |
|
Variable fields |
$1: IP address of the device to which the output interface belongs. ¡ If the output interface belongs to the local device, the value for this field is 0.0.0.0. ¡ If the output interface belongs to a peer device, the value for this field is the IP address of the peer device. $2: Name of the VPN instance to which the RIR collaboration relationship belongs. If the output interface belongs to the local device or the peer device uses a public address to establish RIR collaboration relationship with the local device, this field displays N/A. $3: Output interface associated with the tunnel interface. $4: Total bandwidth of the output interface. $5: Used bandwidth of the output interface. |
|
Severity level |
4 |
|
Example |
RIR/4/RIR_OUTIF_BANDWIDTH_OVERUSED: -Device=1.1.1.1-VPNInstance=a-OutputInterface=GE1/0/1-TotalBandwidth=1000 kbps-UsedBandwidth=1000 kbps. The bandwidth usage of the output interface has reached 90%. |
|
Explanation |
The bandwidth usage of an output interface has reached 90%, and the device will perform link reselection. |
|
Recommended action |
If this message is generated frequently, use another output interface with higher bandwidth. |
RIR_QUALITY_DELAY
|
Message text |
-FlowID=[UINT32]-Device=[IPADDR]-VPNInstance=[STRING]-Tunnel=[UINT32]-DetectedDelay=[UINT32] ms-DelayThreshold=[UINT32] ms. The link became unqualified because the link delay detected by NQA was higher than the link delay threshold in the SLA. |
|
Variable fields |
$1: ID of the flow template. $2: IP address of the device to which the tunnel interface belongs. ¡ If the tunnel interface belongs to the local device, the value for this field is 0.0.0.0. ¡ If the tunnel interface belongs to a peer device, the value for this field is the IP address of the peer device. $3: Name of the VPN instance to which the RIR collaboration relationship belongs. If the tunnel interface belongs to the local device or the peer device uses a public address to establish RIR collaboration relationship with the local device, this field displays N/A. $4: Tunnel interface number. $5: Link delay detected by NQA. $6: Link delay threshold in the SLA associated with the flow template. |
|
Severity level |
4 |
|
Example |
RIR/4/RIR_QUALITY_DELAY: -FlowID=2-Device=1.1.1.1-VPNInstance=a-Tunnel=1-DetectedDelay=100 ms-DelayThreshold=50 ms. The link became unqualified because the link delay detected by NQA was higher than the link delay threshold in the SLA. |
|
Explanation |
The link became unqualified because the link delay detected by NQA was higher than the link delay threshold in the SLA associated with the flow template. |
|
Recommended action |
No action is required. |
RIR_QUALITY_JITTER
|
Message text |
-FlowID=[UINT32]-Device=[IPADDR]-VPNInstance=[STRING]-Tunnel=[UINT32]-DetectedJitter=[UINT32] ms-JitterThreshold=[UINT32] ms. The link became unqualified because the link jitter was higher than the jitter threshold in the SLA. |
|
Variable fields |
$1: ID of the flow template. $2: IP address of the device to which the tunnel interface belongs. ¡ If the tunnel interface belongs to the local device, the value for this field is 0.0.0.0. ¡ If the tunnel interface belongs to a peer device, the value for this field is the IP address of the peer device. $3: Name of the VPN instance to which the RIR collaboration relationship belongs. If the tunnel interface belongs to the local device or the peer device uses a public address to establish RIR collaboration relationship with the local device, this field displays N/A. $4: Tunnel interface number. $5: Link jitter detected by NQA. $6: Jitter threshold in the SLA associated with the flow template. |
|
Severity level |
4 |
|
Example |
RIR/4/RIR_QUALITY_JITTER: -FlowID=2-Device=1.1.1.1-VPNInstance=a-Tunnel=1-DetectedJitter=100 ms-JitterThreshold=50 ms. The link became unqualified because the link jitter was higher than the jitter threshold in the SLA. |
|
Explanation |
The link became unqualified because the link jitter detected by NQA was higher than the jitter threshold in the SLA associated with the flow template. |
|
Recommended action |
No action is required. |
RIR_QUALITY_OTHER
|
Message text |
-FlowID=[UINT32]-Device=[IPADDR]-VPNInstance=[STRING]-Tunnel=[UINT32]. The link became unqualified because of a reason other than failing to meet the thresholds in the SLA. |
|
Variable fields |
$1: ID of the flow template. $2: IP address of the device to which the tunnel interface belongs. ¡ If the tunnel interface belongs to the local device, the value for this field is 0.0.0.0. ¡ If the tunnel interface belongs to a peer device, the value for this field is the IP address of the peer device. $3: Name of the VPN instance to which the RIR collaboration relationship belongs. If the tunnel interface belongs to the local device or the peer device uses a public address to establish RIR collaboration relationship with the local device, this field displays N/A. $4: Tunnel interface number. |
|
Severity level |
4 |
|
Example |
RIR/4/RIR_QUALITY_OTHER: -FlowID=2-Device=1.1.1.1-VPNInstance=a-Tunnel=1. The link became unqualified because of a reason other than failing to meet the thresholds in the SLA. |
|
Explanation |
The link became unqualified because of a reason other than failing to meet the thresholds in the SLA associated with the flow template. For example, this message is generated if the SLA thresholds are inconsistent on the hub and spoke sites. |
|
Recommended action |
No action is required. |
RIR_QUALITY_PKTLOSS
|
Message text |
-FlowID=[UINT32]-Device=[IPADDR]-VPNInstance=[STRING]-Tunnel=[UINT32]-DetectedPktLoss=[UINT32]/1000-PktLossThreshold=[UINT32]/1000. The link became unqualified because the packet loss ratio detected by NQA was higher than the packet loss threshold in the SLA. |
|
Variable fields |
$1: ID of the flow template. $2: IP address of the device to which the tunnel interface belongs. ¡ If the tunnel interface belongs to the local device, the value for this field is 0.0.0.0. ¡ If the tunnel interface belongs to a peer device, the value for this field is the IP address of the peer device. $3: Name of the VPN instance to which the RIR collaboration relationship belongs. If the tunnel interface belongs to the local device or the peer device uses a public address to establish RIR collaboration relationship with the local device, this field displays N/A. $4: Tunnel interface number. $5: Packet loss ratio detected by NQA. $6: Packet loss threshold in the SLA associated with the flow template. |
|
Severity level |
4 |
|
Example |
RIR/4/RIR_QUALITY_PKTLOSS: -FlowID=2-Device=1.1.1.1-VPNInstance=a-Tunnel=1-DetectedPktLoss=100/1000-PktLossThreshold=50/1000. The link became unqualified because the packet loss ratio detected by NQA was higher than the packet loss threshold in the SLA. |
|
Explanation |
The link became unqualified because the packet loss ratio detected by NQA was higher than the packet loss threshold in the SLA associated with the flow template. |
|
Recommended action |
No action is required. |
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_PEERLINK_CHECK
|
Message text |
An RRPP port can't be configured as a peer-link interface. |
|
Variable fields |
None. |
|
Severity level |
6 |
|
Example |
RRPP/6/RRPP_PEERLINK_CHECK: An RRPP port can't be configured as a peer-link interface. |
|
Explanation |
This message is generated when you configure an RRPP port as a peer-link interface. |
|
Recommended action |
No action is required. |
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 |
|
|
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_PROCESS_STILL_STARTING
|
Message text |
Pattern 1: The process [STRING] is still starting for [UINT32] minutes. Pattern 2: The process [STRING] on [STRING] [UINT16] is still starting for [UINT32] minutes. |
|
Variable fields |
$1: Process name. $2: Object type, MDC or Context. (This field is not displayed if the device does not support MDCs or contexts.) $3: ID of the MDC or context. (This field is not displayed if the device does not support MDCs or contexts.) $4: Time duration. |
|
Severity level |
6 |
|
Example |
SCMD/6/SCM_PROCESS_STILL_STARTING: The process ipbased on MDC 2 is still starting for 20 minutes. |
|
Explanation |
A specific process keeps starting. |
|
Recommended action |
Normal operation information. If the device subsequently outputs the SCM_PROCESS_STARTING_TOOLONG log, see recommended actions associated with the SCM_PROCESS_STARTING_TOOLONG log. |
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];VlanID(1175)=[UINT16];VNI(1213)=[UINT32]; |
|
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. $21: Event description: ¡ Session created. ¡ Active flow threshold. ¡ Normal over. ¡ Aged for timeout. ¡ Aged for reset or config-change. ¡ Other. $22: VLAN ID of the session. $23: VXLAN ID of the session. |
|
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;VlanID(1175)=--;VNI(1213)=--; |
|
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];VlanID(1175)=[UINT16];VNI(1213)=[UINT32]; |
|
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. $16: VLAN ID of the session. $17: VXLAN ID of the session. |
|
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;VlanID(1175)=--;VNI(1213)=--; |
|
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 |
|
|
Variable fields |
$1: Configuration item: update sampling mode $2: Interface name. $3: Failure reason: not supported operation |
|
Severity level |
4 |
|
Example |
|
|
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 two asterisks (**). $3: Username. If there is not username information, this field displays two asterisks (**). $4: Command string. |
|
Severity level |
6 |
|
Example |
SHELL/6/SHELL_CMD: -Line=aux0-IPAddr=**-User=**; Command is quit. |
|
Explanation |
A command was 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 that a background program issued failed to be executed. |
|
Recommended action |
No action is required. |
SHELL_CMD_INPUT
|
Message text |
|
|
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_LOCKEDBYOTHER
|
Message text |
SHELL/6/SHELL_CMD_LOCKEDBYOTHER: The system has been locked by [STRING]. |
|
Variable fields |
$1: Session type. |
|
Severity level |
6 |
|
Example |
SHELL/6/SHELL_CMD_LOCKEDBYOTHER: The system has been locked by NETCONF. |
|
Explanation |
Another user locked the configuration. You cannot configure the device. |
|
Recommended action |
Wait for the user to unlock the configuration. |
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
|
The [STRING] command failed to restore the configuration. |
|
|
Variable fields |
$1: Command string. |
|
Severity level |
6 |
|
Example |
SHELL/6/SHELL_CMDFAIL: The “vlan 1024” command failed to restore the configuration. |
|
Explanation |
The specified command failed to be restored during a configuration restoration from a .cfg file. |
|
Recommended action |
No action is required. |
SHELL_COMMIT
|
Message text |
The configuration has been committed. |
|
Variable fields |
N/A |
|
Severity level |
5 |
|
Example |
SHELL/5/SHELL_COMMIT: The configuration has been committed. |
|
Explanation |
A configuration commit operation succeeded. |
|
Recommended action |
No action is required. |
SHELL_COMMIT_DELAY
|
Message text |
A configuration rollback will be performed in [INT32] minutes. |
|
Variable fields |
$1: Configuration commit delay timer. |
|
Severity level |
5 |
|
Example |
SHELL/5/SHELL_COMMIT_DELAY: A configuration rollback will be performed in 3 minutes. |
|
Explanation |
The configuration commit delay timer was set successfully. |
|
Recommended action |
Complete and commit the configuration before the timer expires. If you cannot complete the configuration, execute the configuration commit delay command again to delay the expiration. |
SHELL_COMMIT_FAIL
|
Message text |
-Line=[STRING]-IPAddr=[STRING]-User=[STRING]; Failed to commit the target configuration. |
|
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 **. |
|
Severity level |
4 |
|
Example |
SHELL/4/SHELL_COMMIT_FAIL: -Line=aux0-IPAddr=**-User=**; Failed to commit the target configuration. |
|
Explanation |
A target configuration commit operation failed in private or exclusive mode. |
|
Recommended action |
No action is required. |
SHELL_COMMIT_REDELAY
|
Message text |
The commit delay has been reset, a configuration rollback will be performed in [INT32] minutes. |
|
Variable fields |
$1: Configuration commit delay timer reconfigured. |
|
Severity level |
5 |
|
Example |
SHELL/5/SHELL_COMMIT_REDELAY: The commit delay has been reset, a configuration rollback will be performed in 3 minutes. |
|
Explanation |
The configuration commit delay timer was reconfigured before the timer expires. |
|
Recommended action |
No action is required. |
SHELL_COMMIT_ROLLBACK
|
Message text |
The configuration commit delay is overtime, a configuration rollback will be performed. |
|
Variable fields |
N/A |
|
Severity level |
5 |
|
Example |
SHELL/5/SHELL_COMMIT_ROLLBACK: The configuration commit delay is overtime, a configuration rollback will be performed. |
|
Explanation |
The configuration commit delay timer expired. A configuration rollback will occur. |
|
Recommended action |
Stop configuring the device and wait for the rollback to finish. |
SHELL_COMMIT_ROLLBACKDONE
|
Message text |
The configuration rollback has been performed. |
|
Variable fields |
N/A |
|
Severity level |
5 |
|
Example |
SHELL/5/SHELL_COMMIT_ROLLBACKDONE: The configuration rollback has been performed. |
|
Explanation |
The configuration rollback was completed. |
|
Recommended action |
No action is required. |
SHELL_COMMIT_ROLLBACKFAIL
|
Message text |
Failed to roll back the configuration from the uncommitted changes. |
|
Variable fields |
N/A |
|
Severity level |
5 |
|
Example |
SHELL/5/ SHELL_COMMIT_ROLLBACKFAIL: Failed to roll back the configuration from the uncommitted changes. |
|
Explanation |
A configuration rollback occurred after the configuration commit delay timer expired but the rollback failed. |
|
Recommended action |
Roll back the configuration as required. |
SHELL_COMMIT_SUCCESS
|
Message text |
-Line=[STRING]-IPAddr=[STRING]-User=[STRING]; Target configuration successfully committed. |
|
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 **. |
|
Severity level |
5 |
|
Example |
SHELL/5/SHELL_COMMIT_SUCCESS: -Line=aux0-IPAddr=**-User=**; Target configuration successfully committed. |
|
Explanation |
A target configuration commit operation succeeded in private or exclusive mode. |
|
Recommended action |
No action is required. |
SHELL_COMMIT_WILLROLLBACK
|
Message text |
A configuration rollback will be performed in 1 minute. To retain the configuration you have made after executing the configuration commit delay command, execute the commit command. |
|
Variable fields |
N/A |
|
Severity level |
5 |
|
Example |
SHELL/5/SHELL_COMMIT_WILLROLLBACK: A configuration rollback will be performed in 1 minute. To retain the configuration you have made after executing the configuration commit delay command, execute the commit command. |
|
Explanation |
A configuration rollback will be performed in 1 minute. |
|
Recommended action |
Complete the configuration within 1 minute and commit the configuration, or execute the configuration commit delay command again to delay the expiration. |
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. |
|
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], reason: [STRING]. |
|
Variable fields |
$1: Username. $2: User line type and number. $3: Logout reason. This field is available only in FIPS mode. · exit normally. · time out. |
|
Severity level |
5 |
|
Example |
SHELL/5/SHELL_LOGOUT: Console logged out from console0, reason: exit normally. |
|
Explanation |
A user logged out. If the user logged out from the standby MPU, the user line type and number field displays local. In FIPS mode, this message also displays the user logout reason. |
|
Recommended action |
No action is required. |
SHELL_SAVE_FAILED
|
Message text |
Failed to save running configuration to configuration file for configuration rollback. |
|
Variable fields |
N/A |
|
Severity level |
5 |
|
Example |
SHELL/5/SHELL_SAVE_FAILED: Failed to save running configuration to configuration file for configuration rollback. |
|
Explanation |
The system failed to save the running configuration to the configuration file and does not support a rollback. The system saves the running configuration to the configuration file in the following situations: · The commit command is executed. · The commit command is not executed before the timer set by using the commit confirmed command expires. |
|
Recommended action |
If necessary, roll back the configuration manually. |
SHELL_SAVE_SUCCESS
|
Message text |
Saved running configuration to configuration file for configuration rollback. |
|
Variable fields |
N/A |
|
Severity level |
5 |
|
Example |
SHELL/5/SHELL_SAVE_SUCCESS: Saved running configuration to configuration file for configuration rollback. |
|
Explanation |
The system saved the running configuration to the configuration file successfully and is ready for a rollback. The system saves the running configuration to the configuration file in the following situations: · The commit command is executed. · The commit command is not executed before the timer set by using the commit confirmed command expires. |
|
Recommended action |
No action is required. |
SHELL_SAVEPOINT_EXIST
|
Message text |
The running configuration at this rollback point is the same as the configuration at the previous rollback point. |
|
Variable fields |
N/A |
|
Severity level |
5 |
|
Example |
SHELL/5/SHELL_SAVEPOINT_EXIST: The running configuration at this rollback point is the same as the configuration at the previous rollback point. |
|
Explanation |
The specified two rollback points have the same configuration. |
|
Recommended action |
No action is required. |
SHELL_SAVEPOINT_FAILED
|
Message text |
Failed to create a new rollback point. |
|
Variable fields |
N/A |
|
Severity level |
5 |
|
Example |
SHELL/5/SHELL_SAVEPOINT_FAILED: Failed to create a new rollback point. |
|
Explanation |
An attempt to create a new rollback point failed. |
|
Recommended action |
To save the rollback point, manually roll back to the rollback point, verify that the file system has sufficient space, and execute the commit command again. |
SHELL_SAVEPOINT_FAILED
|
Message text |
Created a new rollback point. |
|
Variable fields |
N/A |
|
Severity level |
5 |
|
Example |
SHELL/5/SHELL_SAVEPOINT_SUCCESS: Created a new rollback point. |
|
Explanation |
An attempt to create a new rollback point succeeded. |
|
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. |
SMLK_PORT_INACTIVE
|
Message text |
Not all the members in smart link group [UINT16] are M-LAG interfaces. |
|
Variable fields |
$1: Smart link group ID. |
|
Severity level |
4 |
|
Example |
SMLK/4/SMLK_PORT_INACTIVE: -MDC=1; Not all the members in smart link group 1 are M-LAG interfaces. |
|
Explanation |
This message is generated for an M-LAG network when not all the members in a smart link group are M-LAG interfaces. The members do not take effect. |
|
Recommended action |
Add only M-LAG interfaces to a smart link group in an M-LAG network. |
SMLK_PORT_INACTIVE
|
Message text |
A peer-link interface can't be a member of a smart link group. |
|
Variable fields |
None. |
|
Severity level |
4 |
|
Example |
SMLK/4/SMLK_PORT_INACTIVE: -MDC=1; A peer-link interface can't be a member of a smart link group. |
|
Explanation |
This message is generated for an M-LAG network when a smart link group includes a peer-link interface. |
|
Recommended action |
Add non-peer-link interfaces to a smart link group in an M-LAG network. |
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 |
|
|
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. |
SRPV6 messages
This section contains SRv6 TE policy messages.
SRPV6_BSID_CONFLICT
|
Message text |
Allocating a binding SID to an SRv6 TE policy failed. (Color [UINT32], Endpoint [STRING], BSID [STRING], Reason [STRING], ConflictState [STRING]). |
|
Variable fields |
$1: Color value of the SRv6 TE policy. $2: Destination node address of the SRv6 TE policy. $3: BSID of the SRv6 TE policy. $4: Reasons for BSID conflict: · The binding SID of a manually configured SRv6 TE policy is the same as that of a different SRv6 TE policy delivered by BGP. · Different SRv6-TE policies dynamically delivered by BGP have the same binding SID. · Different manually configured SRv6-TE policies have the same binding SID. · Binding SID allocation failed. $5: Conflict state. inConflict indicates that a conflict is ongoing. |
|
Severity level |
2 |
|
Example |
SRPV6/2/SRPV6_BSID_CONFLICT: Allocating a binding SID to an SRv6-TE policy fails.(Color 10, Endpoint 10::10, BSID 10::10, Reason The binding SID of a manually configured SRv6-TE policy is the same as that of a different SRv6-TE policy delivered by BGP, ConflictState inConflict). |
|
Explanation |
An SRv6 TE policy BSID allocation conflict or failure occurred. |
|
Recommended action |
1. Specify the color value and destination node address for the display segment-routing ipv6 te policy command to obtain the SRv6 TE policy using the BSID. Then modify the BSID value for the SRv6 TE policy. 2. If the issue persists, contact H3C Support. |
SRPV6_BSID_CONFLICT_CLEAR
|
Message text |
The binding SID allocation failure is resolved.(Color [UINT32], Endpoint [STRING], BSID [STRING], Reason [STRING], ConflictState [STRING]). |
|
Variable fields |
$1: Color value of the SRv6 TE policy. $2: Destination node address of the SRv6 TE policy. $3: BSID of the SRv6 TE policy. $4: Reason that the BSID conflict was resolved: · The binding SID that failed to be allocated was deleted. · The SRv6 TE policy with a binding SID allocation failure was deleted. · Binding SID allocation succeeded. $5: Conflict state. conflictResolved indicates that the conflict has been resolved. |
|
Severity level |
2 |
|
Example |
SRPV6/2/SRPV6_BSID_CONFLICT_CLEAR: The binding SID allocation failure is resolved.( Color 10, Endpoint 10::10, BSID 10::10, Reason The binding SID that failed to be allocated was deleted. ConflictState conflictResolved). |
|
Explanation |
The SRv6 TE policy BSID conflict was resolved. For example, the conflicting BSID was deleted and reconfigured, or the associated SRv6 TE policy was deleted. |
|
Recommended action |
No action is required. |
SRPV6_PATH_STATE_DOWN
|
Message text |
SRv6-TE policy candidate path is down: Color [UINT32], EndPoint [STRING], Origin [STRING], Instance [UINT32], Originator [STRING], Discriminator[UINT32], Preference [UINT32], PreviousRole [STRING], Reason [STRING]. |
|
Variable fields |
$1: Color value of the SRv6 TE policy. $2: Destination node address of the SRv6 TE policy. $3: Origin of the candidate path: · CLI: Manually configured. · BGP: Obtained through a BGP SRv6 policy route. · PCEP: Obtained through PCEP. $4: BGP instance number. This field is displayed only when the candidate path origin is BGP. $5: Head node of the candidate path, in the format of ASN Nodeaddress. ASN is the AS number, and Nodeaddress is the router ID of the BGP peer. This field is displayed only when the candidate path origin is BGP. $6: Candidate path identifier. $7: Candidate path priority. $8: Candidate path role: · Primary. · Backup. $9: Reason that the candidate path went down: · Higher preference path exists. · Candidate path is shutdown. · Candidate path is deleted. · No valid segment list. · Candidate path has empty segment list. · SBFD session was down. · The color and end-point were deleted. |
|
Severity level |
5 |
|
Example |
SRPV6/5/SRPV6_PATH_STATE_DOWN: SRv6-TE policy candidate path is down: Color 10, EndPoint 10::10, Origin BGP, Instance 0, Originator 10 100::10, Discriminator 100, Preference 100, PreviousRole Primary, Reason Higher preference path exists. |
|
Explanation |
The SRv6 TE policy candidate path went down. |
|
Recommended action |
Resolve the issue based on the candidate path down reason. Examine the SRv6 TE policy configuration and SBFD configuration, and check for network congestion. |
SRPV6_POLICY_STATUS_CHG
|
Message text |
SRv6-TE policy (Color [UINT32], EndPoint [STRING]) status changed from [STRING] to [STRING]. Down Reason: [STRING]. |
|
Variable fields |
$1: Color value of the SRv6 TE policy. $2: Destination node address of the SRv6 TE policy. $3: Previous state, which can only be up. $4: New state, which can only be down. $5: Reason that the SRv6 TE policy forwarding state went down: · SBFD session was down. · BFD session was down. · Administratively down. · No candidate path. · No valid candidate path. · No valid segment list. · The color and end-point were deleted. |
|
Severity level |
4 |
|
Example |
SRPV6/4/SRPV6_POLICY_STATUS_CHG: SRv6-TE policy Color 10 EndPoint 10::10 status changed from up to down. Down Reason: The color and end-point are deleted. |
|
Explanation |
The forwarding state of the SRv6 TE policy changed from up to down. |
|
Recommended action |
Resolve the issue based on the SRv6 TE policy forwarding state down reason. Examine the SRv6 TE policy, BFD, and SBFD configuration, and check for network congestion. |
SRPV6_RESOURCE_EXCEED
|
Message text |
The number of used SRv6-TE policy resources exceeded the upper threshold. (ReourceType [STRING], ResourceCurrentCount [UINT32], ResourceThresholdUpperLimit [UINT32]%, ResourceThresholdLowerLimit [UINT32]%, ResourceTotalCount [UINT32]). |
|
Variable fields |
$1: SRv6 TE policy resource type: · srv6Policy: Forwarding entry ID of the SRv6 TE policy. · srv6PolicySegmentList: Forwarding entry ID of the SID list. · srv6PolicyGroup: Forwarding entry ID of the SRv6 TE policy group. · srv6PolicyFwdPath: Forwarding path of the SRv6 TE policy. $2: Number of SRv6 TE policy resources. $3: Upper threshold for SRv6 TE policy resources. $4: Lower threshold for SRv6 TE policy resources. $5: Maximum SRv6 TE policy resources. |
|
Severity level |
4 |
|
Example |
SRPV6/4/SRPV6_RESOURCE_EXDCEED: The number of used SRv6-TE policy resources exceeded the upper threshold. (ReourceType srv6Policy, ResourceCurrentCount 4096, ResourceThresholdUpperLimit 80%, ResourceThresholdLowerLimit 75%, ResourceTotalCount 4096). |
|
Explanation |
The number of SRv6 TE policy resources exceeded the upper threshold. |
|
Recommended action |
Examine the SRv6 TE policy resource usage anomaly by resource type, and then delete unused SRv6 TE policies or SRv6 TE policy groups to save resources. |
SRPV6_RESOURCE_EXCEED_CLEAR
|
Message text |
The number of used SRv6-TE policy resources fell below the lower threshold. (ReourceType [STRING], ResourceCurrentCount [UINT32], ResourceThresholdUpperLimit [UINT32]%, ResourceThresholdLowerLimit [UINT32]%, ResourceTotalCount [UINT32]). |
|
Variable fields |
$1: SRv6 TE policy resource type: · srv6Policy: Forwarding entry ID of the SRv6 TE policy. · srv6PolicySegmentList: Forwarding entry ID of the SID list. · srv6PolicyGroup: Forwarding entry ID of the SRv6 TE policy group. · srv6PolicyFwdPath: Forwarding path of the SRv6 TE policy. $2: Number of SRv6 TE policy resources. $3: Upper threshold for SRv6 TE policy resources. $4: Lower threshold for SRv6 TE policy resources. $5: Maximum SRv6 TE policy resources. |
|
Severity level |
4 |
|
Example |
SRPV6/4/SRPV6_RESOURCE_EXCEED_CLEAR: The number of used SRv6-TE policy resources fell below the lower threshold. (ReourceType srv6Policy, ResourceCurrentCount 3072, ResourceThresholdUpperLimit 80%, ResourceThresholdLowerLimit 75%, ResourceTotalCount 4096). |
|
Explanation |
The number of SRv6 TE policy resources dropped below the lower threshold. |
|
Recommended action |
No action is required. |
SRPV6_SEGLIST_STATE_DOWN
|
Message text |
SRv6-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 SRv6 TE policy. $2: Destination node address of the SRv6 TE policy. $3: Origin of the candidate path: · CLI: Manually configured. · BGP: Obtained through a BGP SRv6 policy route. · PCEP: Obtained through PCEP. $4: BGP instance number. This field is displayed only when the candidate path origin is BGP. $5: Head node of the candidate path, in the format of ASN Nodeaddress. ASN is the AS number, and Nodeaddress is the router ID of the BGP peer. This field is displayed only when the candidate path origin is BGP. $6: SID list identifier. $7: SID list index. $8: Reason that the SID list forwarding state went down: · Segment list was unavailable. · SBFD session was down. |
|
Severity level |
5 |
|
Example |
SRPV6/5/SRPV6_SEGLIST_STATE_DOWN: SRv6-TE policy seglist forwarding state down event: Color 10, EndPoint 10::10, Origin BGP, Instance 0, Originator 10 100::10, Discriminator 100, SegListID 1, Reason Segment list was unavailable. |
|
Explanation |
The SID list forwarding state went down. |
|
Recommended action |
Examine the link status for the SID list forwarding path and the SBFD configuration. |
SRPV6_SEGLIST_STATE_DOWN_CLEAR
|
Message text |
SRv6-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 SRv6 TE policy. $2: Destination node address of the SRv6 TE policy. $3: Origin of the candidate path: · CLI: Manually configured. · BGP: Obtained through a BGP SRv6 policy route. · PCEP: Obtained through PCEP. $4: BGP instance number. This field is displayed only when the candidate path origin is BGP. $5: Head node of the candidate path, in the format of ASN Nodeaddress. ASN is the AS number, and Nodeaddress is the router ID of the BGP peer. This field is displayed only when the candidate path origin is BGP. $6: SID list identifier. $7: SID list index. |
|
Severity level |
5 |
|
Example |
SRPV6/5/SRPV6_ SEGLIST_STATE_DOWN _CLEAR: SRv6-TE policy seglist forwarding down is resolved. (Color 10, EndPoint 10::10, Origin BGP, Instance 0, Originator 10 100::10, Discriminator 100, SegListID 1) |
|
Explanation |
The SID list forwarding state down alarm was cleared. The forwarding state for the SID list came up. |
|
Recommended action |
No action is required. |
SRPV6_STATE_DOWN
|
Message text |
SRv6-TE policy (Color [UINT32], EndPoint [STRING]) forwarding state went down: [STRING]. |
|
Variable fields |
$1: Color value of the SRv6 TE policy. $2: Destination node address of the SRv6 TE policy. $3: Reason that the SRv6 TE policy forwarding state went down: · SBFD session was down. · BFD session was down. · Administratively down. · No candidate path. · No valid candidate path. · No valid segment list. · The color and end-point were deleted. |
|
Severity level |
2 |
|
Example |
SRPV6/2/SRPV6_STATE_DOWN: SRv6-TE policy forwarding (Color 10, EndPoint 10::10) state went down: SBFD session was down. |
|
Explanation |
The forwarding state of the SRv6 TE policy went down. |
|
Recommended action |
Resolve the issue based on the SRv6 TE policy forwarding state down reason. Examine the SRv6 TE policy configuration and BFD configuration, and check for network congestion. |
SRPV6_STATE_DOWN_CLEAR
|
Message text |
SRv6-TE policy (Color [UINT32], EndPoint [STRING]) down alarm was cleared. |
|
Variable fields |
$1: Color value of the SRv6 TE policy. $2: Destination node address of the SRv6 TE policy. |
|
Severity level |
2 |
|
Example |
SRPV6/2/SRPV6_STATE_DOWN_CLEAR: SRv6-TE policy (Color 10, EndPoint 10 10::10) down alarm was cleared. |
|
Explanation |
The SRv6 TE policy forwarding state down alarm was cleared. The forwarding state for the SRv6 TE policy came up. |
|
Recommended action |
No action is required. |
SSHC messages
This section contains SSH client messages.
SSHC_CERT_VERIFY_FAIL
|
Message text |
Failed to verify the certificate because [STRING]. |
|
Variable fields |
$1: Failure reason: ¡ null certificate. ¡ null certificate name. ¡ unable to get issuer certificate. ¡ unable to get certificate CRL. ¡ unable to decrypt CRL's signature. ¡ certificate signature failure. ¡ CRL signature failure. ¡ unable to decrypt certificate's signature. ¡ certificate is not yet valid. ¡ certificate has expired. ¡ CRL is not yet valid. ¡ CRL has expired. ¡ format error in certificate's notBefore field. ¡ format error in certificate's notAfter field. ¡ format error in CRL's lastUpdate field. ¡ format error in CRL's nextUpdate field. ¡ out of memory. ¡ self signed certificate. ¡ self signed certificate in certificate chain. ¡ unable to verify the first certificate. ¡ certificate chain too long. ¡ certificate revoked. ¡ invalid CA certificate. ¡ invalid non-CA certificate (has CA markings). ¡ path length constraint exceeded. ¡ proxy path length constraint exceeded. ¡ proxy certificates not allowed, please set the appropriate flag. ¡ unsupported certificate purpose. ¡ certificate not trusted. ¡ certificate rejected. ¡ application verification failure. ¡ subject issuer mismatch. ¡ authority and subject key identifier mismatch. ¡ authority and issuer serial number mismatch. ¡ key usage does not include certificate signing. ¡ unable to get CRL issuer certificate. ¡ unhandled critical extension. ¡ key usage does not include CRL signing. ¡ key usage does not include digital signature. ¡ unhandled critical CRL extension. ¡ invalid or inconsistent certificate extension. ¡ invalid or inconsistent certificate policy extension. ¡ no explicit policy. ¡ Different CRL scope. ¡ CRL path validation error. ¡ unsupported or invalid name syntax. ¡ unsupported or invalid name constraint syntax. ¡ Suite B: certificate version invalid. ¡ Suite B: invalid public key algorithm. ¡ Suite B: invalid ECC curve. ¡ Suite B: invalid signature algorithm. ¡ Suite B: curve not allowed for this LOS. ¡ Suite B: cannot sign P-384 with P-256. ¡ Invalid certificate verification context. ¡ Issuer certificate lookup error. ¡ proxy subject name violation. ¡ Absence of basic Constraints extension. ¡ failure to establish revocation status. |
|
Severity level |
5 |
|
Example |
SSHC/5/SSHC_CERT_VERIFY_FAIL: Failed to verify the certificate because null certificate. |
|
Explanation |
Certificate authentication failed. |
|
Recommended action |
Make sure the certificate is valid. |
SSHS messages
This section contains SSH server messages.
SSHS_ACL_DENY
|
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_CERT_VERIFY_FAIL
|
Message text |
Failed to verify the certificate because [STRING]. |
|
Variable fields |
$1: Failure reason: ¡ null certificate. ¡ null certificate name. ¡ unable to get issuer certificate. ¡ unable to get certificate CRL. ¡ unable to decrypt CRL's signature. ¡ certificate signature failure. ¡ CRL signature failure. ¡ unable to decrypt certificate's signature. ¡ certificate is not yet valid. ¡ certificate has expired. ¡ CRL is not yet valid. ¡ CRL has expired. ¡ format error in certificate's notBefore field. ¡ format error in certificate's notAfter field. ¡ format error in CRL's lastUpdate field. ¡ format error in CRL's nextUpdate field. ¡ out of memory. ¡ self signed certificate. ¡ self signed certificate in certificate chain. ¡ unable to verify the first certificate. ¡ certificate chain too long. ¡ certificate revoked. ¡ invalid CA certificate. ¡ invalid non-CA certificate (has CA markings). ¡ path length constraint exceeded. ¡ proxy path length constraint exceeded. ¡ proxy certificates not allowed, please set the appropriate flag. ¡ unsupported certificate purpose. ¡ certificate not trusted. ¡ certificate rejected. ¡ application verification failure. ¡ subject issuer mismatch. ¡ authority and subject key identifier mismatch. ¡ authority and issuer serial number mismatch. ¡ key usage does not include certificate signing. ¡ unable to get CRL issuer certificate. ¡ unhandled critical extension. ¡ key usage does not include CRL signing. ¡ key usage does not include digital signature. ¡ unhandled critical CRL extension. ¡ invalid or inconsistent certificate extension. ¡ invalid or inconsistent certificate policy extension. ¡ no explicit policy. ¡ Different CRL scope. ¡ CRL path validation error. ¡ unsupported or invalid name syntax. ¡ unsupported or invalid name constraint syntax. ¡ Suite B: certificate version invalid. ¡ Suite B: invalid public key algorithm. ¡ Suite B: invalid ECC curve. ¡ Suite B: invalid signature algorithm. ¡ Suite B: curve not allowed for this LOS. ¡ Suite B: cannot sign P-384 with P-256. ¡ Invalid certificate verification context. ¡ Issuer certificate lookup error. ¡ proxy subject name violation. ¡ Absence of basic Constraints extension. ¡ failure to establish revocation status. |
|
Severity level |
5 |
|
Example |
SSHS/5/SSHS_CERT_VERIFY_FAIL: Failed to verify the certificate because null certificate. |
|
Explanation |
Certificate authentication fails. |
|
Recommended action |
Make sure the certificate is valid. |
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_DISCONNECT
|
Message text |
SCP user [STRING] (IP: [STRING]) disconnected from the server, reason: [STRING]. |
|
Variable fields |
$1: Username. $2: IP address of the SCP client. $3: Reason for disconnection: · User logout. · Forced logout by admin. |
|
Severity level |
6 |
|
Example |
SSHS/6/SSHS_SCP_DISCONNECT: SCP user David (IP: 192.168.30.117) disconnected from the server, reason: User logout. |
|
Explanation |
An SCP user was disconnected from the server. |
|
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_DISCONNECT
|
Message text |
SFTP user [STRING] (IP: [STRING]) disconnected from the server, reason: [STRING]. |
|
Variable fields |
$1: Username. $2: IP address of the SFTP client. $3: Reason for disconnection: · User logout. · Timeout. · Forced logout by admin. |
|
Severity level |
6 |
|
Example |
SSHS/6/SSHS_SFTP_DISCONNECT: SFTP user David (IP: 192.168.30.117) disconnected from the server, reason: Timeout. |
|
Explanation |
An SFTP user was disconnected from the server. |
|
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. |
SSL VPN messages
This section contains SSL VPN messages.
SSLVPN_HTTP_BIND_ADDRESS_INUSED
|
Message text |
Failed to bind TCP connection [STRING]/[UINT32] to VPN instance [UINT32] because the address was already used. |
|
Variable fields |
$1: IP address to be bound. $2: Port number to be bound. $3: VPN instance index. |
|
Severity level |
3 |
|
Example |
SSLVPN/3/SSLVPN_HTTP_BIND_ADDRESS_INUSED: Failed to bind TCP connection 192.168.30.117/10000 to VPN instance 0 because the address was already used. |
|
Explanation |
Failed to bind the VPN instance with the IP address and the port number because the IP address to be bound has been used and cannot be reused. |
|
Recommended action |
Use display tcp-proxy to identify available IP addresses and then use an IP address that is not used or can be reused to perform the binding task again. |
SSLVPN_HTTP_BIND_PORT_ALLOCETED
|
Message text |
Failed to bind TCP connection [STRING]/[UINT32] to VPN instance [UINT32] because the port was already allocated. |
|
Variable fields |
$1: IP address to be bound. $2; Port number to be bound. $3: VPN instance index. |
|
Severity level |
3 |
|
Example |
SSLVPN/3/ SSLVPN_HTTP_BIND_PORT_ALLOCETED: Failed to bind TCP connection 192.168.30.117/10000 to VPN instance 0 because the port was already allocated. |
|
Explanation |
Failed to bind the VPN instance with the IP address and the port number because the port number to be bound has been allocated. |
|
Recommended action |
Use display tcp-proxy port-info and display ipv6 tcp-proxy port-info to identify available port numbers, and then perform the binding task again. |
SSLVPN_IP_RESOURCE_DENY
|
Message text |
User [STRING] of gateway [STRING] from [STRING] denied to access [STRING]:[STRING]. |
|
Variable fields |
$1: Username. $2: SSL VPN gateway name. $3: User IP address. $4: IP address of the requested resource. $5: Port number of the requested resource. |
|
Severity level |
6 |
|
Example |
SSLVPNK/6/SSLVPN_IP_RESOURCE_DENY: User abc of gateway ctx1 from 192.168.200.130 denied to access 10.1.1.255:137. |
|
Explanation |
A user was denied access to specific IP resources, which is possibly caused by ACL-based access filtering. |
|
Recommended action |
Verify that access to the requested resource is not denied by the ACL rules used for IP access filtering. |
SSLVPN_IP_RESOURCE_FAILED
|
Message text |
User [STRING] of gateway [STRING] from [STRING] failed to access [STRING]:[STRING]. |
|
Variable fields |
$1: Username. $2: SSL VPN gateway name. $3: User IP address. $4: IP address of the requested resource. $5: Port number of the requested resource. |
|
Severity level |
6 |
|
Example |
SSLVPNK/6/SSLVPN_IP_RESOURCE_FAILED: User abc of gateway ctx1 from 192.168.200.130 failed to access 10.1.1.255:137. |
|
Explanation |
A user failed to access IP resources, which is possibly caused by network issues. |
|
Recommended action |
Verify that a route is available to reach the requested IP resource. |
SSLVPN_IP_RESOURCE_PERMIT
|
Message text |
User [STRING] of gateway [STRING] from [STRING] permitted to access [STRING]:[STRING]. |
|
Variable fields |
$1: Username. $2: SSL VPN gateway name. $3: User IP address. $4: IP address of the requested resource. $5: Port number of the requested resource. |
|
Severity level |
6 |
|
Example |
SSLVPN/6/SSLVPN_IP_RESOURCE_PERMIT: User abc of gateway gw1 from 192.168.200.130 permitted to access 10.1.1.255:137. |
|
Explanation |
A user accessed IP resources. |
|
Recommended action |
No action is required. |
SSLVPN_IPAC_ALLOC_ADDR_FAIL
|
Message text |
Failed to allocate [STRING] address to user [STRING] at [STRING] in gateway [STRING]. Reason: [STRING]. |
|
Variable fields |
$1: Route version: · IPv4 · IPv6 $2: Username. $3: User IP address. $4: SSL VPN gateway name. $5: Reason why the SLS VPN gateway failed to allocate an IP address to the user. Options are: · Failed to obtain system resource data. · No address is available in the address pool. · Failed to obtain address pool. · Available addresses in the address pool have been bound to other users. |
|
Severity level |
6 |
|
Example |
SSLVPN/6/SSLVPN_IPAC_ALLOC_ADDR_FAIL: Failed to allocate IPv4 address to user user1 at 10.1.1.100 in gateway gw. Reason: No address is available in the address pool. |
|
Explanation |
The SSL VPN gateway failed to allocate an IP address to the user, which is possibly caused by an IP access attempt. |
|
Recommended action |
1. Verify that the device is operating correctly. 2. Verify that the address pool is configured. 3. Verify that the address pool has available addresses. 4. Verify that the available addresses are not bound to other users. |
SSLVPN_IPAC_ALLOC_ADDR_SUCCESS
|
Message text |
[STRING] address [STRING] successfully allocated to user [STRING] at [STRING] in gateway [STRING]. |
|
Variable fields |
$1: Route version: · IPv4 · IPv6 $2: IP address. $3: Username. $4: User IP address. $5: SSL VPN gateway name. |
|
Severity level |
6 |
|
Example |
SSLVPN/6/SSLVPN_IPAC_ALLOC_ADDR_SUCCESS: IPv4 address 10.1.1.1 successfully allocated to user user1 at 10.1.1.100 in gateway gw. |
|
Explanation |
The SSL VPN gateway allocated IP addresses to IP access clients successfully, and users accessed the gateway in IP access mode. |
|
Recommended action |
No action is required. |
SSLVPN_IPAC_CONN_CLOSE
|
Message text |
IP connection was [STRING]. Reason: [STRING]. |
|
Variable fields |
$1: Connection close type. Options are: · closed. · aborted. $2: Reason why the connection was closed. Options are: · User logout. · Failure to find peer. · Handshake failed. · Change of IP address pool. · Failure to receive data. · Local retransmission timeout. · Local keepalive timeout. · Local probe timeout. · Received FIN from peer. · Received RST from peer. · No authorized policy group. · Allocated address was bound to another user. · Failure to update client configuration. · Deleted old peer. · Other. |
|
Severity level |
6 |
|
Example |
SSLVPNK/6/SSLVPN_IPAC_CONN_CLOSE: IP connection was closed. Reason: User logout. |
|
Explanation |
The reason for the close of an IP connection was logged. |
|
Recommended action |
No action is required. |
SSLVPN_IPAC_PACKET_DROP
|
Message text |
Dropped [STRING] IP connection [STRING] packets in gateway [STRING]. Reason: [STRING]. |
|
Variable fields |
$1: Format of dropped packets. $2: Connection direction: · request. · reply. $3: SSL VPN gateway name. $4: Reason for the packet drop: · Buffer insufficient. · Gateway rate limit. |
|
Severity level |
6 |
|
Example |
SSLVPN/6/SSLVPN_IPAC_PACKET_DROP: Dropped 164 IP connection reply packets in gateway gw. Reason: Gateway rate limit. |
|
Explanation |
Packet drop information was logged, including number of dropped packets, packet drop direction, gateway name, and packet drop reason. |
|
Recommended action |
Verify that the gateway rate limit is configured or the buffer is insufficient . |
SSLVPN_IPAC_RELEASE_ADD_SUCCESS
|
Message text |
User [STRING] at [STRING] in gateway [STRING] released [STRING] address [STRING]. |
|
Variable fields |
$1: Username. $2: User IP address. $3: SSL VPN gateway name. $4: Route version: · IPv4 · IPv6 $5: IP address that the SSL VPN gateway allocated to a user. |
|
Severity level |
6 |
|
Example |
SSLVPNK/6/SSLVPN_IPAC_RELEASE_ADDR_SUCCESS: User abc at 10.1.1.1 in gateway gw released IPv4 address 10.1.1.100. |
|
Explanation |
The IP address allocated to the user was released successfully. |
|
Recommended action |
No action is required. |
SSLVPN_SERVICE_UNAVAILABLE
|
Message text |
SSL VPN service was unavailable. Reason: [STRING]. |
|
Variable fields |
$1: Reason why the SSL VPN service was unavailable. Options incldue SSL VPN gateway not enabled. |
|
Severity level |
6 |
|
Example |
SSLVPNK/6/SSLVPN_SERVICE_UNAVAILABLE: SSL VPN service was unavailable. Reason: SSL VPN gateway not enabled. |
|
Explanation |
The reason for the unavailability of an SSL VPN service was logged. |
|
Recommended action |
If the reason is SSL VPN gateway not enabled, enter SSL VPN gateway view and use the service ipv4 enable command to enable the gateway. |
SSLVPN_USER_LOGIN
|
Message text |
User [STRING] of gateway [STRING] logged in from [STRING]. |
|
Variable fields |
$1: Username. $2: SSL VPN gateway name. $3: User IP address. |
|
Severity level |
5 |
|
Example |
SSLVPN/5/SSLVPN_USER_LOGIN: User abc of gateway ctx logged in from 192.168.200.31. |
|
Explanation |
A user logged in to an SSL VPN gateway. |
|
Recommended action |
No action is required. |
SSLVPN_USER_LOGINFAILED
|
Message text |
User [STRING] of gateway [STRING] failed to log in from [STRING]. Reason: [STRING]. |
|
Variable fields |
$1: Username. $2: SSL VPN gateway name. $3: User IP address. $4: Reason for the login failure: · Authentication failed. · Authorization failed, reason: the authorizing process has failed. · Accounting failed. · Number of online users exceeded the limit. · Failed to get SMS message code from iMC server. · Maximum number of concurrent online connections for the user already reached. · Login timed out. · The authentication server is not reachable. · The authorization server is not reachable. · The accounting server is not reachable. · Authentication failed, reason: incorrect username or password or an internal error has occurred on the authentication server. · Authentication failed, reason: internal system error. · Authorization failed, reason: internal system error. · Accounting failed, reason: internal system error. · Other. |
|
Severity level |
5 |
|
Example |
SSLVPN/5/SSLVPN_USER_LOGINFAILED: User abc of gateway ctx failed to log in from 192.168.200.31. |
|
Explanation |
A user failed to log in to an SSL VPN gateway. |
|
Recommended action |
No action is required. |
SSLVPN_USER_LOGOUT
|
Message text |
User [STRING] of gateway [STRING] logged out from [STRING]. Reason: [STRING]. |
|
Variable fields |
$1: Username. $2: SSL VPN gateway name. $3: User IP address. $4: Reason for user logout: · Idle timeout. · A logout request was received from the Web browser. · A logout request was received from the client. · Forced logout. · A new login was attempted and logins using the account reach the maximum. · Accounting update failed. · Accounting session timed out. · Interface went down. · ADM request was received. · Idle cut for traffic not reach the minimum required amount. |
|
Severity level |
5 |
|
Example |
SSLVPN/5/SSLVPN_USER_LOGOUT: User abc of gateway ctx logged out from 192.168.200.31. Reason: A logout request was received from the Web browser. |
|
Explanation |
A user logged out of an SSL VPN gateway. |
|
Recommended action |
No action is required. |
SSLVPN_USER_NUMBER
|
Message text |
The number of SSL VPN users reached the upper limit. |
|
Variable fields |
None. |
|
Severity level |
6 |
|
Example |
SSLVPN/6/SSLVPN_USER_NUMBER: The number of SSL VPN users reached the upper limit. |
|
Explanation |
The number of SSL VPN users reached the upper limit. |
|
Recommended action |
No action is required. |
STAMGR messages
This section contains station management messages.
STAMGR_ADD_FAILVLAN
|
Message text |
|
|
Variable fields |
$1: SSID. $2: MAC address of the client. $3: Name of the AP associated with the client. $4: ID of the radio associated with the client. $5: ID of the Fail VLAN. |
|
Severity level |
5 |
|
Example |
|
|
Explanation |
The client failed to pass the authentication and was assigned to the Auth-Fail VLAN. |
|
Recommended action |
No action is required. |
STAMGR_ADDBAC_INFO
|
Message text |
Add BAS AC [STRING]. |
|
Variable fields |
$1: MAC address of the BAS AC. |
|
Severity level |
6 |
|
Example |
STAMGR/6/STAMGR_ADDBAC_INFO: Add BAS AC 3ce5-a616-28cd. |
|
Explanation |
The BAS AC was connected to the master AC. |
|
Recommended action |
No action is required. |
STAMGR_ADDSTA_INFO
|
Message text |
Add client [STRING]. |
|
Variable fields |
$1: MAC address of the client. |
|
Severity level |
6 |
|
Example |
STAMGR/6/STAMGR_ADDSTA_INFO: Add client 3ce5-a616-28cd. |
|
Explanation |
The client was connected to the BAS AC. |
|
Recommended action |
No action is required. |
STAMGR_AUTHORACL_FAILURE
|
Message text |
|
|
Variable fields |
$1: SSID. $2: MAC address of the client. $3: Name of the AP associated with the client. $4: ID of the radio associated with the client. $5: ACL number. $6: Reason: · This type of ACL is not supported. · The memory resource is not enough. · The ACL conflicts with other ACLs. · The ACL doesn't contain any rules. · The OpenFlow tunnel was not established. · The OpenFlow table is full. · Unknown reason. Error code code was returned. |
|
Severity level |
5 |
|
Example |
|
|
Explanation |
The authentication server failed to assign an ACL to the client. |
|
Recommended action |
No action is required. |
STAMGR_AUTHORUSERPROFILE_FAILURE
|
Message text |
-SSID=[STRING]-UserMAC=[STRING]-APName=[STRING]-RadioID=[STRING]; Failed to assign user profile [STRING]. Reason: [STRING]. |
|
Variable fields |
$1: SSID. $2: MAC address of the client. $3: Name of the AP associated with the client. $4: ID of the radio associated with the client. $5: Name of the authorization user profile. $6: Failure cause: · The user profile doesn’t exist. · No user profiles are created on the device. · The memory resource is not enough. · The OpenFlow tunnel was not established. · Unknown reason. Error code code was returned. |
|
Severity level |
5 |
|
Example |
STAMGR/5/STAMGR_AUTHORUSERPROFILE_FAILURE:-SSID=text-wifi-UserMAC=3ce5-a616-28cd-APName=ap1-RadioID=2; Failed to assign user profile aaa. Reason: No user profiles are created on the device. |
|
Explanation |
The authentication server failed to assign a user profile to the client. |
|
Recommended action |
No action is required. |
STAMGR_BSS_FAILURE
|
Message text |
-APID=[STRING]-RadioID=[STRING]-WLANID=[STRING]-ST Name=[STRING]; The number of BSSs exceeded the upper limit. |
|
Variable fields |
$1: AP ID. $2: Radio ID. $3: WLAN ID. $4: Service template name. |
|
Severity level |
6 |
|
Example |
STAMGR/6/SERVICE_BSS_FAILURE: -APID=1-RadioID=2-WLANID=3-ST Name=1; The number of BSSs exceeded the upper limit. |
|
Explanation |
The number of AP radios using this service template has exceeded the upper limit. |
|
Recommended action |
No action is required. |
STAMGR_CLEINT_BSS_MAXCOUNT
|
Message text |
SSID=[STRING]-APName=[STRING]-RadioID=[STRING]; Number of associated clients reached the upper limit allowed by the BSS. |
|
Variable fields |
$1: SSID defined in the service template. $2: Name of the AP associated with the client. $3: ID of the radio associated with the client. |
|
Severity level |
5 |
|
Example |
STAMGR/5/STAMGR_CLIENT_BSS_MAXCOUNT: SSID=test-wifi-APName=ap1-RadioID=2; Number of associated clients reached the upper limit allowed by the BSS. |
|
Explanation |
The number of associated clients reached the upper limit allowed by the BSS. |
|
Recommended action |
No action is required. |
STAMGR_CLIENT_FAILURE
|
Message text |
Client [STRING] failed to come online from BSS [STRING] with SSID [STRING] on AP [STRING] Radio ID [STRING]. Reason: [STRING]. |
|
Variable fields |
$1: MAC address of the client. $2: BSSID. $3: SSID defined in the service template. $4: Name of the AP associated with the client. $5: ID of the radio associated with the client. $6: Reasons for the client's failure to come online. Table 17 describes the possible reasons. |
|
Severity level |
5 |
|
Example |
STAMGR/5/STAMGR_CLIENT_FAILURE: Client 3303-c2af-b8d2 failed to come online from BSS 0023-12ef-78dc with SSID 1 on AP ap1 Radio ID 1. Reason: Unknown reason. |
|
Explanation |
The client failed to come online from the BSS for a specific reason. |
|
Recommended action |
To resolve the issue: 1. Check the debugging information to locate the issue and resolve it. 2. If the issue persists, contact H3C Support. |
Table 17 Possible failure reasons
|
Possible reasons |
|
Unknown error. |
|
Failed to process open authentication packet from the client. |
|
Failed to send responses when the AC successfully processed open authentication packet from the client. |
|
Failed to create state timer when the AC received authentication packet in Unauth state. |
|
Failed to refresh state timer when the AC received authentication packet in Unauth state. |
|
Received association packet Unauth state. |
|
Received deauthentication packet with reason code code in Unauth state: · 1—Unknown reason. · 3—Client is removed from BSS and is deauthenticated. · 6—Incorrect frame. · 9—Received association or reassociation request before authentication is complete. · 13—Invalid IE. |
|
Received dissociation packet with reason code code in Unauth state: · 1—Unknown reason. · 2—Prior authentication is invalid. · 4—Inactivity timer expired. · 5—Insufficient resources. · 7—Incorrect frame. · 8—Client is removed from BSS and is disassociated. · 10—Failed to negotiate the Power Capability IE. · 11—BSS management switchover. |
|
Received Auth failure packet in Unauth state. |
|
Received state timer timeout in Unauth state. |
|
Received deauthentication packet with reason code code in Auth state: · 1—Unknown reason. · 3—Client is removed from BSS and is deauthenticated. · 6—Incorrect frame. · 9—Received association or reassociation request before authentication is complete. · 13—Invalid IE. |
|
Received authentication packet with inconsistent authentication algorithm or shared key in Auth state. |
|
Received state timer timeout in Auth state. |
|
Failed to process Add Mobile message when client association succeeded in Auth state. |
|
Received inconsistent authentication algorithm or share key in Userauth state. |
|
Failed to check association request when the AC received association packet in Userauth state. |
|
Failed to process IE when the AC received association packet in Userauth state. |
|
Failed to send association responses when the AC received association packet in Userauth state. |
|
Failed to process Add Mobile message when client association succeeded in Userauth state. |
|
Received deauthentication packet with reason code code in Userauth state: · 1—Unknown reason. · 3—Client is removed from BSS and is deauthenticated. · 6—Incorrect frame. · 9—Received association or reassociation request before authentication is complete. · 13—Invalid IE. |
|
Received dissociation packet with reason code code in Userauth state: · 1—Unknown reason. · 2—Prior authentication is invalid. · 4—Inactivity timer expired. · 5—Insufficient resources. · 7—Incorrect frame. · 8—Client is removed from BSS and is disassociated. · 10—Failed to negotiate the Power Capability IE. · 11—BSS management switchover. |
|
Client authentication failed in Userauth state. |
|
Failed to get backup client data while using AP private data to upgrade client. |
|
Failed to set kernel forwarding table while using AP private data to upgrade client. |
|
Failed to add MAC while using AP private data to upgrade client. |
|
Failed to create keepalive and idle timeout timers while using AP private data to upgrade client. |
|
Failed to set kernel forwarding table while upgrading client without using AP private data. |
|
Failed to add MAC while upgrading client without using AP private data. |
|
Failed to activate client while upgrading client without using AP private data. |
|
Failed to synchronize client information to configuration thread while upgrading client without using AP private data. |
|
Failed to create keepalive and idle timeout timers while upgrading client without using AP private data. |
|
Failed to add MAC during inter-device client smooth creation. |
|
Failed to set kernel forwarding table during inter-device client smooth creation. |
|
Failed to send Add Mobile message during inter-device client smooth creation. |
|
Failed to get AP type during inter-device client smooth creation. |
|
Failed to recover service data while recovering running client data from database. |
|
Failed to synchronize data to service thread while recovering basic client data from database. |
|
Failed to add MAC when hierarchy device received upstream Add Mobile message. |
|
Failed to set kernel forwarding table when hierarchy device received upstream Add Mobile message. |
|
Failed to synchronize upstream message when hierarchy device received upstream Add Mobile message. |
|
Failed to create client when hierarchy device received upstream Add Mobile message. |
|
Failed to add MAC when hierarchy device received downstream Add Mobile message. |
|
Failed to synchronize data to service thread when hierarchy device received downstream Add Mobile message. |
|
Failed to set kernel forwarding table when hierarchy device received downstream Add Mobile message. |
|
Failed to send down add pbss to driver when hierarchy device received downstream Add Mobile message. |
|
Failed to synchronize downstream message when hierarchy device received downstream Add Mobile message. |
|
Failed to create client when hierarchy device received downstream Add Mobile message. |
|
Failed to create interval statistics timer when hierarchy device received downstream Add Mobile message. |
|
Failed to obtain AP private data when hierarchy device received downstream Add Mobile message. |
|
Failed to advertise Add Mobile message. |
|
Failed to activate client when hierarchy device received downstream client state synchronization message. |
|
Failed to get AP type when hierarchy device received downstream client state synchronization message. |
|
Failed to synchronize downstream message when hierarchy device received downstream client state synchronization message. |
|
The radio was in down state when hierarchy device received downstream Add Mobile message. |
|
Hierarchy device failed to process the upstream Add Mobile message. |
|
Hierarchy device failed to process downstream Add Mobile message. |
|
Failed to process service thread during inter-device client smooth creation. |
|
Failed to create client during inter-device smooth. |
|
Failed to process upstream client state synchronization message in Userauth state. |
|
Failed to process downstream client state synchronization message in Userauth state. |
|
Hierarchy device failed to process upstream client state synchronization message. |
|
Hierarchy device failed to process downstream client state synchronization message. |
|
AC received message for deleting the client entry. |
|
Fit AP received message for deleting the client. |
|
Different old and new region codes. |
|
Failed to update IGTK. |
|
Failed to update GTK. |
|
Failed to generate IGTK when the first client came online. |
|
TKIP is used to authenticate all clients. |
|
Channel changed. |
|
BssDelAllSta event logged off client normally. |
|
AP down. |
|
Radio down. |
|
Service template disabled. |
|
Service template unbound. |
|
Created BSS during master AC switchover process. |
|
Updated BSS base information when BSS was in deactive state. |
|
Intrusion protection. |
|
Local AC or AP deleted BSS. |
|
BssDelAllSta event logged off client abnormally. |
|
Received VLAN deleted event. |
|
CM received message for logging off client from AM. |
|
The reset wlan client command was executed to log off the client. |
|
Deleted private data on AP: DBM database recovered. |
|
Failed to synchronize authentication succeeded message downstream. |
|
Client RSSI was lower than the threshold and was decreasing. |
|
Configured whitelist for the first time or executed the reset wlan client all command. |
|
Received client offline websocket message. |
|
WMAC logged off all clients associated with the radio. |
|
Timer for sending deassociation message timed out. |
|
The client is in blacklist or deleted from whitelist. |
|
Client was added to the dynamic blacklist. |
|
Failed to roam out. |
|
Implemented inter-AC roaming for the first time. |
|
Successfully roamed to another BSS. |
|
Failed to roam in. |
|
Roaming process received a message for logging off the client. |
|
Roaming process processed Down event and logged off roam-in clients. |
|
Roaming failure. |
|
Successfully performed roaming but failed to recover authentication data. |
|
Roaming timed out. |
|
Seamless roaming failed. |
|
Logged off clients that performed inter- or intra-AC roaming. |
|
Failed to process AccessCtrlChk. Configure permitted AP group or permitted SSID. |
|
Synchronized client information to process and logged off client. |
|
Failed to synchronize client state to uplink devices. |
|
Local AC or remote AP received Add Mobile message updated BSS and logged off clients. |
|
Upgraded HA and logged off all clients. |
|
Synchronized BSS data during master/backup AC switchover process. |
|
Failed to synchronize service template data during master/backup AC switchover process. |
|
BSS aging timer timed out. |
|
Remote AP deleted non-local forwarding BSS. |
|
Failed to find configuration data when synchronizing data. |
|
BSS was deleted: BSS synchronization examination failed or there was no BSS data to be updated. |
|
Failed to get BSS by using WLAN ID. |
|
Unbound inherited service template. |
|
STAMGR process was down automatically or manually. |
|
Deleted redundant clients. |
|
Failed to process authorized doing nodes. |
|
Authorization failed. |
|
NSS value in Operating Mode Notification Action packet doesn't support mandatory VHT-MCS. |
|
Number of sent SA requests exceeded the permitted threshold. |
|
Local AC came online again and deleted all clients associated with the BSS. |
|
Failed to upgrade hot-backup. |
|
The illegally created BSS was deleted. |
|
Failed to process requests when receiving UserAuth Success message. |
|
Failed to get AP type when receiving UserAuth Successful message. |
|
Failed to notify client of the recovery of basic client data from database. |
|
Failed to recover basic client data from database. |
|
Client already existed when the AC received Auth packet from the client and checked online clients. |
|
Client already existed during FT Over-the-DS authentication. |
|
SKA authentication failed. |
|
Deadline timer timed out during FT authentication. |
|
Failed to send the response for the successful shared key authentication to the client. |
|
Failed to get FT data during FT authentication. |
|
FT authentication was performed and BSS does not support FT. |
|
Failed to process FT authentication-success result. |
|
Failed to process FT authentication. |
|
Maximum number of clients already reached when remote request message was received. |
|
Failed to fill authorization information while processing authorization message. |
|
Failed to process key negotiation during 802.1X authentication. |
|
Invalid session key length during 802.1X authentication. |
|
802.1X authentication failed. |
|
802.1X server was unreachable. |
|
User timer timed out during 802.1X authentication. |
|
Server timer timed out during 802.1X authentication. |
|
802.1X authentication configuration error. |
|
Received nonexistent authorization VLAN group during 802.1X authentication. |
|
MAC authentication failed. |
|
MAC server was unreachable. |
|
Session time is zero during MAC authentication. |
|
Server timer timed out during MAC authentication. |
|
802.1X authentication failed and the return code is code. |
|
MAC authentication failed and the return code is code. |
|
Authorization failed for 802.1X authentication and the return code is code. |
|
Authorization failed for MAC authentication and the return code is code. |
|
Accounting start failed for 802.1X authentication and the return code is code. |
|
Accounting start failed for MAC authentication and the return code is code. |
|
Accounting update failed for 802.1X authentication and the return code is code. |
|
Accounting update failed for MAC authentication and the return code is code. |
|
Failed to receive client EAP request for 802.1X authentication. |
|
Failed to receive server response for 802.1X authentication. |
|
Failed to receive server response for MAC authentication. |
|
Received client log-off packet during 802.1X authentication. |
|
802.1X client handshake failed. |
|
Incorrect 802.1X authentication method. |
|
WLAN roaming center notified IP conflict detected by address security check. |
|
WLAN roaming center notified MAC conflict detected by address security check. |
|
Roaming failed because the user is in the local address security denylist. |
|
Failed to notify the uplink device of user authentication failure. |
|
Failed to advertise Add Mobile message: CAPWAP translation failure. |
|
Failed to advertise Add Mobile message: Invalid length. |
|
Failed to advertise Add Mobile message: Radio down. |
|
Failed to advertise Add Mobile message: Insufficient memory on the downlink device. |
|
Failed to advertise Add Mobile message: MAC adding failure. |
|
Failed to advertise Add Mobile message: AVL adding failure. |
|
Failed to advertise Add Mobile message: PBSS adding failure. |
|
Failed to advertise Add Mobile message: Downlink synchronization failure. |
|
Failed to advertise Add Mobile message: Statistics report timer creation failure. |
|
Failed to advertise Add Mobile message: AP private data obtaining failure. |
|
Failed to advertise Add Mobile message: Client not found for Add Mobile response. |
|
Failed to advertise Add Mobile message: Client was being deleted for Add Mobile response. |
|
Failed to advertise Add Mobile message: Insufficient memory in kernel. |
|
Failed to advertise Add Mobile message: Forward entry adding failure. |
|
Failed to advertise Add Mobile message: PHY obtaining failure. |
|
Failed to advertise Add Mobile message: Invalid length in kernel. |
|
Failed to advertise Add Mobile message: Client adding failure in driver. |
|
Failed to advertise Add Mobile message: Preamble type setting failure in driver. |
|
Failed to advertise Add Mobile message: Dot11g protection setting failure in driver. |
|
Failed to advertise Add Mobile message: PTK setting failure in driver. |
|
Failed to advertise Add Mobile message: PTK flag update failure. |
|
The client does not match a permit ACL rule. |
|
The client is in the dynamic blacklist. |
|
The client is in the static blacklist. |
|
The client is not in the whitelist. |
|
The number of clients exceed the maximum allowed value of radio. |
|
The number of clients exceed the maximum allowed value of BSS. |
STAMGR_CLIENT_OFFLINE
|
Message text |
Client [STRING] went offline from BSS [STRING] with SSID [STRING] on AP [STRING] Radio ID [STRING]. State changed to Unauth. Reason [STRING] |
|
Variable fields |
$1: MAC address of the client. $2: BSSID. $3: SSID defined in the service template. $4: Name of the AP associated with the client. $5: ID of the radio associated with the client. $6: Reason why the client goes offline. Table 18 describes the possible reasons. |
|
Severity level |
6 |
|
Example |
STAMGR/6/STAMGR_CLIENT_OFFLINE: Client 0023-8933-2147 went offline from BSS 0023-12ef-78dc with SSID abc on AP ap1 Radio ID 2. State changed to Unauth. Reason: Radio down. |
|
Explanation |
The client went offline from the BSS for a specific reason. The state of the client changed to Unauth. |
|
Recommended action |
To resolve the issue: 1. Examine whether the AP and its radios operate correctly if the client went offline abnormally. If the logoff was requested by the client, no action is required. 2. If they do not operate correctly, check the debugging information to locate the issue and resolve it. 3. If the issue persists, contact H3C Support. |
Table 18 Possible logoff reasons
|
Possible reasons |
|
Received disassociation frame in Run state: reason code=String. |
|
Unknown reason. |
|
AC received message for deleting the client entry. |
|
Different old and new region codes. |
|
Failed to update IGTK. |
|
Failed to update GTK. |
|
Failed to generate IGTK when the first client came online. |
|
TKIP is used to authenticate all clients. |
|
Channel changed. |
|
BssDelAllSta event logged off client normally. |
|
Radio down. |
|
Service template disabled. |
|
Service template unbound. |
|
Created BSS during master/backup AC switchover process. |
|
Updated BSS base information when BSS was in deactive state. |
|
Intrusion protection. |
|
Local AC or AP deleted BSS. |
|
BssDelAllSta event logged off client abnormally. |
|
Received VLAN deleted event. |
|
CM received message for logging off client from AM. |
|
The reset wlan client command was executed to log off the client. |
|
DBM database failed to recover client operation data. |
|
Deleted private data on AP: DBM database recovered. |
|
Received deauthentication frame in Run state: reason code=String. |
|
Failed to process (re)association request in Run state. |
|
Unmatched authentication algorithm in received authentication message. |
|
Idle timer timeout. |
|
Keepalive timer timeout. |
|
Received authentication failure message. |
|
Failed to synchronize authentication succeeded message downstream. |
|
Client RSSI was lower than the threshold and was marked as decreasing. |
|
Configured whitelist for the first time or executed the reset wlan client all command. |
|
Received client offline websocket message. |
|
WMAC logged off all clients associated with the radio. |
|
Timer for sending disassociation message timed out. |
|
The client is in blacklist or deleted from whitelist. |
|
Client was added to the dynamic blacklist. |
|
Failed to roam out. |
|
Implemented inter-AC roaming for the first time. |
|
Successfully roamed to another BSS. |
|
Failed to roam in. |
|
Roaming process received a message for logging off the client. |
|
Roaming process processed Down event and logged off roam-in clients. |
|
Roaming failure. |
|
Successfully performed roaming but failed to recover authentication data. |
|
Roaming timed out. |
|
Seamless roaming failed. |
|
Logged off clients that performed inter- or intra-AC roaming. |
|
Failed to process AccessCtrlChk when configured permitted AP group or permitted SSID. |
|
Synchronized client information to process and logged off client in Run state. |
|
Failed to synchronize client state to uplink/downlink devices. |
|
Local AC or remote AP received add mobile message, updated BSS, and logged off clients in Run state. |
|
Upgraded HA and logged off all clients. |
|
Synchronized BSS data during master/backup AC switchover process. |
|
Failed to synchronize service template data during master/backup AC switchover process. |
|
BSS aging timer timed out. |
|
Remote AP deleted non-local forwarding BSS. |
|
Failed to find configuration data when synchronizing data. |
|
BSS was deleted: BSS synchronization examination failed or there was no BSS data to be updated. |
|
Failed to get BSS by using WLAN ID. |
|
Unbound inherited service template. |
|
STAMGR process was down automatically or manually. |
|
Deleted redundant clients. |
|
Failed to process authorized doing nodes. |
|
Authorization failed. |
|
NSS value in Operating Mode Notification Action packet doesn't support mandatory VHT-MCS. |
|
Number of sent SA requests exceeded the permitted threshold. |
|
Fit AP received message for deleting the client. |
|
Local AC came online again and deleted all clients associated with the BSS. |
|
Failed to upgrade hot backup. |
|
The illegally created BSS was deleted. |
|
Failed to process requests when receiving UserAuth Success message. |
|
Failed to get AP type when receiving UserAuth Success message. |
|
The client doesn't support mandatory rate. |
|
Disabled access services for 802.11b clients. |
|
The client doesn't support mandatory VHT-MCS. |
|
Enabled the client dot11ac-only feature. |
|
Disabled MUTxBF. |
|
Disabled SUTxBF. |
|
The client doesn't support mandatory MCS. |
|
Channel bandwidth changed. |
|
Enabled the client dot11n-only feature. |
|
Disabled short GI. |
|
Disabled the A-MPDU aggregation method. |
|
Disabled the A-MSDU aggregation method. |
|
Disabled STBC. |
|
Disabled LDPC. |
|
The MIMO capacity decreased, and the MCS supported by the AP can't satisfy the client's negotiated MCS. |
|
The MIMO capacity decreased, and the VHT-MCS supported by the AP can't satisfy the client's negotiated VHT-MCS. |
|
Hybrid capacity increased, which kicked off clients associated with other radios with lower Hybrid capacity. |
|
Failed to add MAC address. |
|
The roaming entry doesn't exist while the AC was processing the roaming request during client smooth reconnection. |
|
Home AC processed the move out response message to update the roaming entry and notified the foreign AC to force the client offline during an inter-AC roaming. |
|
The associated AC left from the mobility group and deleted roam-in entries and roaming entries of the client. |
|
Executed the reset wlan mobility roaming command. |
|
Kicked client because of roaming to another BSSID. |
|
The roaming entry doesn't exist while the AC was processing the Add Preroam message during client smooth reconnection. |
|
Deleted roaming entries of clients in the fail VLAN while processing a fail VLAN delete event. |
|
Deleted the roaming entry of the client while processing a client delete event. |
|
Moving to another SSID on the same radio. |
|
Fail-permit activated and clients were logged off. |
|
Fail-permit deactivated and clients were logged off. |
|
AP triggered (idle timeout). |
|
AP triggered (channel change). |
|
AP triggered (bandwidth change). |
|
Received log-off packet from 802.1X authentication client. |
|
802.1X client handshake failed. |
|
Accounting update timed out for the 802.1X authentication client. |
|
Accounting update timed out for the MAC authentication client. |
|
802.1X authentication client idle cut on AP. |
|
MAC authentication client idle cut on AP. |
|
Session timeout timer expired for the 802.1X authentication client. |
|
Session timeout timer expired for the MAC authentication client. |
|
Received client disassociation message from server for the 802.1X authentication client. |
|
Received client disassociation message from server for the MAC authentication client. |
|
Received nonexistent authorization VLAN group for the 802.1X authentication client. |
|
Received nonexistent authorization VLAN group for the MAC authentication client. |
|
Total client traffic failed to reach the minimum traffic threshold. |
|
Failed to obtain the client IP address before the accounting delay timer expired. |
|
Forced client disassociation because of rate limit issued by DingTalk app. |
|
Logged off client because the EoGRE tunnel went down. |
|
IP conflict detected by address security check. |
|
MAC conflict detected by address security check. |
|
WLAN roaming center notified IP conflict detected by address security check. |
|
WLAN roaming center notified MAC conflict detected by address security check. |
|
Roaming failed because the user is in the local address security denylist. |
|
Failed to notify the uplink device of user authentication failure. |
|
The client does not match a permit ACL rule. |
|
The client is in the dynamic blacklist. |
|
The client is in the static blacklist. |
|
The client is not in the whitelist. |
|
Client supporting BTM roamed to another BSS (Count: Count) successfully. |
|
Client not supporting BTM roamed to another BSS (Count: Count) successfully. |
|
AP triggered client disassociation. |
|
Client connected to another BSSID. |
|
Received disconnecion-request frame from server for the 802.1X or MAC authentication client. |
|
IP address conflict detected by AC. |
|
Received eapol-logoff frame. |
|
Received eapol-logoff frame during 802.1X authentication. |
|
Previous online user entry removed by clear-previous-connection. |
|
Client IP change triggered accounting restart. |
|
Session timed out for the 802.1X or MAC authentication client. |
|
Fast keepalive failed. |
STAMGR_CLIENT_ONLINE
|
Message text |
Client [STRING] went online from BSS [STRING] vlan [STRING] with SSID [STRING] on AP [STRING] Radio ID [STRING]. State changed to Run. |
|
Variable fields |
$1: MAC address of the client. $2: BSSID. $3: ID of the VLAN in which the client came online. $4: SSID defined in the service template. $5: Name of the AP associated with the client. $6: ID of the radio associated with the client. |
|
Severity level |
6 |
|
Example |
STAMGR/6/STAMGR_CLIENT_ONLINE: Client 0023-8933-2147 went online from BSS 0023-12ef-78dc vlan 1 with SSID abc on AP ap1 Radio ID 2. State changed to Run. |
|
Explanation |
The client came online from the BSS. The state of the client changed to Run. |
|
Recommended action |
No action is required. |
STAMGR_CLEINT_RADIO_MAXCOUNT
|
Message text |
APName=[STRING]-RadioID=[STRING]; Number of associated clients reached the upper limit allowed by the radio. |
|
Variable fields |
$1: Name of the AP associated with the client. $2: ID of the radio associated with the client. |
|
Severity level |
5 |
|
Example |
STAMGR/5/STAMGR_CLIENT_RADIO_MAXCOUNT: APName=ap1-RadioID=2; Number of associated clients reached the upper limit allowed by the radio. |
|
Explanation |
The number of associated clients reached the upper limit allowed by the radio. |
|
Recommended action |
No action is required. |
STAMGR_CLIENT_SNOOPING
|
Message text |
Detected client IP change: Client MAC: [SRTING], IP: [STRING], [STRING], [STRING], Username: [STRING], AP name: [STRING], Radio ID [UCHAR], Channel number: [UINT32], SSID: [STRING], BSSID: [STRING]. |
|
Variable fields |
$1: MAC address of the client. $2: Current IP address of the client. $3: Used IP address of the client. $4: Used IP address of the client. $5: Username of the client. $6: Name of the AP associated with the client. $7: ID of the radio associated with the client. $8: ID of the channel used by the client. $9: SSID of the service template associated with the client. $10: BSSID of the service template associated with the client. |
|
Severity level |
6 |
|
Example |
STAMGR_CLIENT_SNOOPING: Detected client IP change: Client MAC: 31ac-11ea-17ff,IP: 4.4.4.4, IP: 1.1.1.1, IP: 2.2.2.2, IP: -NA-, User name: test, AP name: ap1, Radio ID: 1, Channel number: 161,SSID: 123, BSSID: 25c8-3dd5-261a. |
|
Explanation |
IP change was detected for a specific client. |
|
Recommended action |
No action is required. |
STAMGR_DELBAC_INFO
|
Message text |
Delete BAS AC [STRING]. |
|
Variable fields |
$1: MAC address of the BAS AC. |
|
Severity level |
6 |
|
Example |
STAMGR/6/STAMGR_DELBAC_INFO: Delete BAS AC 3ce5-a616-28cd. |
|
Explanation |
The BAS AC was disconnected from the master AC. |
|
Recommended action |
No action is required. |
STAMGR_DELSTA_INFO
|
Message text |
Delete client [STRING]. |
|
Variable fields |
$1: MAC address of the client. |
|
Severity level |
6 |
|
Example |
STAMGR/6/STAMGR_DELSTA_INFO: Delete client 3ce5-a616-28cd. |
|
Explanation |
The client was disconnected from the BAS AC. |
|
Recommended action |
No action is required. |
STAMGR_ESCAPE_ACTIVE
|
Message text |
The fail-permit mode was activated on radio [STRING] bound with service template [STRING] and SSID [STRING] in BSS [STRING]. Reason: [STRING]. |
|
Variable fields |
$1: Radio ID. $2: Service template name. $3: SSID. $4: BSSID. $5: Reason why the fail-permit mode was activated. Options include: ¡ Unreachable domain—The RADIUS server cannot be reached. ¡ AP disconnected from the AC. |
|
Severity level |
4 |
|
Example |
STAMGR/4/STAMGR_ESCAPE_ACTIVE: The fail-permit mode was activated on radio 1 bound with service template st1 and SSID st1ssid in BSS 0023-12ef-78dc. Reason: AP disconnected from AC. |
|
Explanation |
The configured fail-prmit mode was activated because the RADIUS server cannot be reached or the AP is disconnected from the AC. |
|
Recommended action |
To resolve the issue: 1. Verify that the RADIUS server can be reached and the AP is connected to the AC correctly. 2. If the issue persists, contact H3C Support. |
STAMGR_ESCAPE_DEACTIVE
|
Message text |
The fail-permit mode was deactivated on radio [STRING] bound with service template [STRING] and SSID [STRING] in BSS [STRING]. Reason: [STRING]. |
|
Variable fields |
$1: Radio ID. $2: Service template name. $3: SSID. $4: BSSID. $5: Reason why the fail-permit mode was deactivated. Options include: ¡ Domain is reachable—Connection to the RADIUS server was restored. ¡ AP and AC connection restored. |
|
Severity level |
6 |
|
Example |
STAMGR/6/STAMGR_ESCAPE_DEACTIVE: The fail-permit mode was deactivated on radio 1 bound with service template st1 and SSID st1ssid in BSS 0023-12ef-78dc. Reason: AP and AC connection restored. |
|
Explanation |
The configured fail-prmit mode was deactivated because connection to the RADIUS server or the AP and AC connection was restored. |
|
Recommended action |
No action is required. |
STAMGR_DOMAIN_UNREACHABLE
|
Message text |
Domain [STRING] configured in service template [STRING] with SSID [STRING] is unreachable. |
|
Variable fields |
$1: Domain name. $2: Service template name. $3: SSID. |
|
Severity level |
4 |
|
Example |
STAMGR/4/STAMGR_DOMAIN_UNREACHABLE: Domain mydomain configured in service template st1 with SSID ssidst1 is unreachable. |
|
Explanation |
The authentication domain configured in the service template cannot be reached. |
|
Recommended action |
To resolve the issue: 1. Verify that the RADIUS server can be reached. 2. If the issue persists, contact H3C Support. |
STAMGR_DOMAIN_REACHABLE
|
Message text |
Domain [STRING] configured in service template [STRING] with SSID [STRING] is reachable. |
|
Variable fields |
$1: Domain name. $2: Service template name. $3: SSID. |
|
Severity level |
6 |
|
Example |
STAMGR/6/STAMGR_DOMAIN_REACHABLE: Domain mydomain configured in service template st1 with SSID ssidst1 is reachable. |
|
Explanation |
Connection to the authentication domain configured in the service template restored. |
|
Recommended action |
No action is required. |
STAMGR_MACA_LOGIN_FAILURE
|
Message text |
|
|
Variable fields |
$1: Username. $2: MAC address of the client. $3: SSID. $4: Name of the AP associated with the client. $5: ID of the radio associated with the client. $6: VLAN ID. $7: Username format: · fixed. · MAC address. $8: Reason for the authentication failure: · AAA processed authentication request and returned error code code. ¡ 4—Represents one of the following errors: nonexistent authentication domain, service type error, or incorrect username or password. ¡ 8—Represents one of the following errors: no IP addresses are added to the authentication server, preshared keys configured on the authentication server are different from preshared keys configured on the device, or the authentication server and the device cannot reach each other. ¡ 26—Configuration error exists in the authentication domain. · AAA processed authorization request and returned error code code. ¡ 8—The authentication server and the device cannot reach each other. · Client timeout timer expired. · Received user security information and kicked off the client. · Accounting-update timer expired, and no responses were received from the server. · Kicked off the client when the idle timeout timer expired. · Authentication method error. · Kicked off the client because the server-assigned session timeout timer is 0. · Received session disconnection event. · Unknown reason. |
|
Severity level |
5 |
|
Example |
|
|
Explanation |
The client failed to pass MAC authentication for a specific reason. |
|
Recommended action |
To resolve the issue: 1. Examine the network connection between the device and the AAA server. 2. Verify that the AAA server works correctly. 3. Verify that the AAA server is configured with the correct username and password. 4. Troubleshoot errors one by one according to the returned error code during authentication. 5. If the issue persists, contact H3C Support. |
STAMGR_MACA_LOGIN_SUCC
|
Message text |
|
|
Variable fields |
$1: Username. $2: MAC address of the client. $3: SSID. $4: Name of the AP associated with the client. $5: ID of the radio associated with the client. $6: VLAN ID. $7: Username format: · fixed. · MAC address. |
|
Severity level |
6 |
|
Example |
|
|
Explanation |
The client came online after passing MAC authentication. |
|
Recommended action |
No action is required. |
STAMGR_MACA_LOGOFF
|
Message text |
|
|
Variable fields |
$1: Username. $2: MAC address of the client. $3: SSID. $4: Name of the AP associated with the client. $5: ID of the radio associated with the client. $6: VLAN ID. $7: Username format: · fixed. · MAC address. $8: Reason why the client is logged off. · AAA processed authentication request and returned error code code. Server reason: reason. The reason field represents the reason returned from the server and is available only when the server returned a reason. Available error codes include: ¡ 4—Represents one of the following errors: nonexistent authentication domain, service type error, or incorrect username or password. ¡ 8—Represents one of the following errors: no IP addresses are added to the authentication server, preshared keys configured on the authentication server are different from preshared keys configured on the device, or the authentication server and the device cannot reach each other. ¡ 26—Configuration error exists in the authentication domain. · AAA processed authorization request and returned error code code. Server reason: reason. The reason field represents the reason returned from the server and is available only when the server returned a reason. Available error codes include: ¡ 8—The authentication server and the device cannot reach each other. · AAA processed accounting-start request and returned error code code. Server reason: reason. The reason field represents the reason returned from the server and is available only when the server returned a reason. Available error codes include: ¡ 8—The authentication server and the device cannot reach each other. · AAA processed accounting-update request and returned error code code. Server reason: reason. The reason field represents the reason returned from the server and is available only when the server returned a reason. Available error codes include: ¡ 8—The authentication server and the device cannot reach each other. · Client timeout timer expired. · Received user security information and kicked off the client. · Lost in shaking hands. · Accounting-update timer expired, and no responses were received from the server. · Kicked off the client when the idle timeout timer expired. · Authentication method error. · Kicked off the client because the server-assigned session timeout timer is 0. · Received session disconnection event. · Received disassociation frame in Run state: reason code=code. · Received deauthentication frame in Run state: reason code=code. · Received disassociation packet in Userauth state. · Received deauthentication packet in Userauth state. · Received client failure message with reason code=code. · Received client offline message with reason code=code. · Unknown reason. |
|
Severity level |
6 |
|
Example |
|
|
Explanation |
The MAC authenticated client was logged off for a specific reason. |
|
Recommended action |
To resolve the issue: 1. Check the debugging information to locate the logoff cause and remove the issue. If the logoff was requested by the client, no action is required. 2. If the issue persists, contact H3C Support. |
STAMGR_ROAM_FAILED
|
Message text |
Client [MAC] on AP [STRING] Radio ID [STRING] failed to roam with reason code [UINT32]. |
|
Variable fields |
$1: MAC address of the client. $2: Name of the AP associated with the client. $3: ID of the radio associated with the client. $4: Reason code for the roaming failure: · 1—Failed to select a roaming policy. · 2—Insufficient memory resources. · 3—Network communication failures. · 4—Lack of local roaming entries. · 5—Failed to add a VLAN. |
|
Severity level |
4 |
|
Example |
STAMGR/4/STAMGR_ROAM_FAILED: Client 001f-3ca8-1092 on AP ap1 Radio ID 2 failed to roam with reason code 1. |
|
Explanation |
The client failed to roam for a specific reason. |
|
Recommended action |
To resolve the issue, depending on the reason code: · 1—Use the display wlan client verbose command to verify that the authentication method has changed. · 2—Use the display process memory command to check memory resource usage for each module. · 3—Use the display wlan mobility group command to check the IACTP tunnel state. · 4—Use the display wlan mobility group command to check the IACTP tunnel state. · 5—Check the trace.log file for VLAN adding failure reason. |
STAMGR_ROAM_SUCCESS
|
Client [MAC] roamed from BSSID [MAC] on AP [STRING] Radio ID [STRING] of AC IP [IPADDR] to BSSID [MAC] on AP [STRING] Radio ID [STRING] of AC IP [IPADDR] successfully. |
|
|
Variable fields |
$1: MAC address of the client. $2: BSSID of the AP associated with the client before roaming. $3: Name of the AP associated with the client before roaming. $4: ID of the radio associated with the client before roaming. $5: IP address of the AC associated with the client before roaming. $6: BSSID of the AP associated with the client after roaming. $7: Name of the AP associated with the client after roaming. $8: ID of the radio associated with the client after roaming. $9: IP address of the AC associated with the client after roaming. |
|
Severity level |
6 |
|
Example |
STAMGR/6/STAMGR_ROAM_SUCCESS: Client 0021-005f-dffd roamed from BSSID 000f-e289-6ad0 on AP ap1 Radio ID 2 of AC IP 172.25.0.81 to BSSID 000f-e2ab-baf0 on AP ap2 Radio ID 2 of AC IP 172.25.0.82 successfully. |
|
Explanation |
The client roamed successfully. |
|
Recommended action |
No action is required. |
STAMGR_SAVI_BIND
|
Message text |
Bound IP address [STRING] to client [STRING] associated with radio [STRING] of AP [STRING] in BSS [STRING] with SSID [STRING]. Binding type: [STRING]. |
|
Variable fields |
$1: IP address of the client. $2: MAC address of the client. $3: ID of the radio associated with the client. $4: Name of the AP associated with the client. $5: BSSID. $6: SSID of the service template. $7: IP address binding type: · DHCP. · DHCPv6. · ND. |
|
Severity level |
6 |
|
Example |
STAMGR/6/STAMGR_SAVI_BIND: Bound IP address 192.168.1.1 to client b0f9-6393-72e0 associated with radio 2 of AP ap1 in BSS b0f9-6393-72f0 with SSID abc. Binding type: DHCP. |
|
Explanation |
The device created an SAVI binding entry. |
|
Recommended action |
No action is required. |
STAMGR_SAVI_UNBIND
|
Message text |
Unbound IP address [STRING] from client [STRING] associated with radio [STRING] of AP [STRING] in BSS [STRING] with SSID [STRING]. |
|
Variable fields |
$1: IP address of the client. $2: MAC address of the client. $3: ID of the radio associated with the client. $4: Name of the AP associated with the client. $5: BSSID. $6: SSID of the service template. |
|
Severity level |
6 |
|
Example |
STAMGR/6/STAMGR_SAVI_UNBIND: Unbound IP address 192.168.1.1 from client b0f9-6393-72e0 associated with radio 2 of AP ap1 in BSS b0f9-6393-72f0 with SSID abc. |
|
Explanation |
The device deleted an SAVI binding entry. |
|
Recommended action |
No action is required. |
STAMGR_SAVI_UNKNOWN_SOURCE_IP
|
Message text |
Received a data packet with unknown source IP [STRING] destined to IP [STRING] from client [STRING] associated with radio [STRING] of AP [STRING] in BSS [STRING] with SSID [STRING]. IP protocol: [STRING]. |
|
Variable fields |
$1: Source IP address. $2: Destination IP address. $3: MAC address of the client. $4: ID of the radio associated with the client. $5: Name of the AP associated with the client. $6: BSSID. $7: SSID of the service template. $8: IP protocol version. |
|
Severity level |
6 |
|
Example |
STAMGR/6/STAMGR_SAVI_UNKNOWN_SOURCE_IP: Received a data packet with unknown source IP 192.168.1.1 destined to IP 192.168.1.2 from client 0023-8933-2147 associated with radio 2 of AP ap1 in BSS 0023-12ef-78dc with SSID abc. IP protocol: 17. |
|
Explanation |
The device received a data packet with a source IP address that does not match any SAVI binding entries. |
|
Recommended action |
No action is required. |
STAMGR_SERVICE_FAILURE
|
Message text |
Service failure occurred on BSS [STRING] after service template [STRING] with SSID [STRING] was bound to radio [STRING] on AP [STRING] with AP ID [STRING]. Reason: [STRING], code=0x[STRING]. |
|
Variable fields |
$1: BSSID. $2: Name of the service template. $3: SSID defined in the service template. $4: Radio ID. $5: AP name. $6: AP ID. $7: Reason for the service failure, as described in Table 19. $8: Error code. |
|
Severity level |
6 |
|
Example |
STAMGR/6/SERVICE_FAILURE: Service failure occurred on BSS 0023-12ef-78dc after service template st1 with SSID st1ssid was bound to radio 1 on AP ap1 with AP ID 1. Reason: Failed to activate BSS when AP came online, code=0x61140001. |
|
Explanation |
After the AP came online, BSS activation failed for a specific reason with error code 0x61140001. |
|
Recommended action |
To resolve the issue: 1. Check the debugging information to locate the failure cause and remove the issue. 2. If the issue persists, contact H3C Support. |
Table 19 Possible service failure reasons
|
Possible reasons |
|
Failed to create a BSS interface during smooth BSS interface creation. |
|
Replied with failure to transmit interface creation node during smooth BSS interface creation. |
|
Failed to set forwarding location during smooth recovery of AP data. |
|
Failed to initiate a series of locations during smooth recovery of AP data. |
|
Failed to send message of creating BSS interface to worker thread during smooth recovery of AP data. |
|
Failed to create handle during smooth recovery of AP data. |
|
Failed to activate BSS during smooth recovery of AP data. |
|
Failed to set kernel forwarding table during smooth recovery of AP data. |
|
Failed to create BSS node when AP came online. |
|
Failed to create BSS handle when AP came online. |
|
Insufficient memory for creating BSS node when AP came online. |
|
Failed to get radio private data while creating BSS node in general process. |
|
Failed to initiate a series of locations while creating BSS node in general process. |
|
Failed to set kernel forwarding table while creating BSS node in general process. |
|
Failed to create BSS node during smooth recovery of BSS data. |
|
Failed to get AP location while recovering BSS running data from DBM. |
|
Failed to get radio private data while recovering BSS running data from DBM. |
|
Failed to add BSS index to interface index while recovering BSS running data from DBM. |
|
Failed to create BSS handle when hierarchy device received Add WLAN message. |
|
Failed to initiate a series of locations when hierarchy device received Add WLAN message. |
|
Failed to set forwarding location when hierarchy device received Add WLAN message. |
|
Failed to send message to worker thread when hierarchy device received Add WLAN message. |
|
Failed to set kernel forwarding table when hierarchy device received Add WLAN message. |
|
Failed to activate BSS when hierarchy device received Add WLAN message. |
|
Failed to issue Add WLAN message when hierarchy device received Add WLAN message. |
|
Failed to activate BSS when service template was bound. |
|
Failed to create BSS node when service template was bound. |
|
Failed to create BSS handle when service template was bound. |
|
Failed to add bind node to mapped radio list of the service template while recovering service template binding information for service thread from pending database. |
|
Failed to create BSS node while recovering service template binding information for service thread from pending database. |
|
Failed to add bind node to mapped radio list of the service template while creating BSS from Merger. |
|
Failed to create BSS node while creating BSS from Merger. |
|
Failed to apply for memory while creating BSS node. |
|
Failed to calculate BSSID while creating BSS node. |
|
Service thread received interface creation failure while creating BSS interface during smooth recovery of AP data. |
|
Failed to add BSS index to interface index while creating BSS interface during smooth recovery of AP data. |
|
Failed to add VLAN on the interface while creating BSS interface during smooth recovery of AP data. |
|
Failed to set the source MAC address of the interface while creating BSS interface during smooth recovery of AP data. |
|
Failed to set kernel forwarding table while creating BSS interface during smooth recovery of AP data. |
|
Failed to activate BSS while creating BSS interface during smooth recovery of AP data. |
|
Replied with failure to transmit interface creation node when hierarchy device created an interface accordingly. |
|
Failed to create BSS interface when BSS created an interface accordingly. |
|
Failed to add BSS index to interface index when BSS created an interface accordingly. |
|
Failed to add VLAN on the interface when BSS created an interface accordingly. |
|
Failed to set source MAC address of the interface when BSS created an interface accordingly. |
|
Failed to set kernel forwarding table when BSS created an interface accordingly. |
|
Failed to issue ADD BSS message when BSS created an interface accordingly. |
|
Replied with failure to transmit interface creation node when hierarchy device created an interface accordingly for an invalid interface. |
|
Created BSS rollback for failed resources while issuing ADD BSS message callback. |
|
Failed to enable packet socket while recovering BSS running data from DBM. |
|
Failed to create BSS node while recovering BSS running data from DBM. |
|
Failed to initiate BSS while creating BSS node. |
|
Failed to activate BSS when service template was enabled. |
|
Invalid BSS interface index while upgrading BSS with AP private data. |
|
Failed to upgrade backup BSS to real BSS while upgrading BSS with AP private data. |
|
Failed to set kernel forwarding table while upgrading BSS with AP private data. |
|
Failed to activate BSS while upgrading BSS with AP private data. |
|
Invalid BSS interface index while upgrading BSS without AP private data. |
|
Failed to set kernel forwarding table while upgrading BSS without AP private data. |
|
Failed to activate BSS while upgrading BSS without AP private data. |
|
Failed to create BSS interface while creating general BSS process. |
|
Failed to activate BSS during smooth recovery of BSS data. |
|
Failed to activate BSS while recovering service template binding information for service thread from pending database. |
|
Failed to activate BSS while creating BSS from Merger. |
|
Failed to activate BSS when AP came online. |
|
Failed to activate BSS when other module sent activation request. |
|
Failed to activate BSS when other module received activation request. |
|
Failed to send response node of creating interface while creating interface during smooth recovery of AP data. |
|
Failed to add BSS index to interface index when hierarchy device created an interface accordingly. |
|
Failed to add VLAN on the interface when hierarchy device created an interface accordingly. |
|
Failed to set source MAC address of the interface when hierarchy device created an interface accordingly. |
|
Failed to set kernel forwarding table when hierarchy device created an interface accordingly. |
|
Failed to activate BSS when hierarchy device created an interface accordingly. |
|
Failed to issue Add BSS message when hierarchy device created an interface accordingly. |
|
Insufficient memory when hierarchy device received BSS creation message. |
|
Failed to fill BSS basic data when hierarchy device received BSS creation message. |
|
Failed to initiate BSS service phase when hierarchy device received BSS creation message. |
|
Failed to receive Add WLAN message when hierarchy device received BSS creation message. |
|
Failed to get radio private data because of invalid AP ID when hierarchy device received BSS creation message. |
|
Failed to get radio private data because of invalid radio ID when hierarchy device received BSS creation message. |
|
Failed to get radio private data when hierarchy device received Add WLAN message. |
|
Failed to issue message when hierarchy device received Add WLAN message. |
|
Failed to get BSS data through WLAN ID during smooth recovery of BSS data. |
|
Failed to issue Add WLAN message while creating BSS node in general process. |
|
Failed to create BSS interface when hierarchy device created an interface accordingly. |
|
Failed to create BSS interface when hierarchy device created an interface accordingly for an invalid interface. |
|
Failed to set forwarding location while creating BSS node in general process. |
|
Replied with failure to transmit interface creation node when BSS created an interface accordingly. |
|
Failed to update BSS key data when hierarchy device received Add WLAN message. |
|
Replied with failure to transmit interface creation node when BSS created an interface accordingly for an existing BSS. |
STAMGR_SERVICE_OFF
|
Message text |
BSS [STRING] was deleted after service template [STRING] with SSID [STRING] was unbound from radio [STRING] on AP [STRING]. Reason: [STRING]. |
|
Variable fields |
$1: BSSID. $2: Name of the service template. $3: SSID defined in the service template. $4: Radio ID. $5: AP name. $6: Reason for the BSS deletion. · Unknown reason. · AP down. · Deleted BSS with the Delete mark when inter-AC BSS smooth ended. · Hierarchy device received BSS delete message. · Deleted AP private data from APMGR when AP smooth ended. · WLAS was triggered, and service was shut down temporarily. · Intrusion protection was triggered, and service was shut down permanently. · Service module received Update WLAN message when BSS was inactive. · Disabled service template. · Unbound service template. · Deleted BSS with the Delete mark when inter-AC AP smooth ended. · BSS aging timer timed out. · Deleted non-local forwarding BSS when AP enabled with remote AP went offline. · Failed to find configuration data while synchronizing data. · AP did not come online or service template was disabled. · Failed to find the WLAN ID from APMGR while BSS was smoothing WLAN ID. · Unbound inherited service template. · The stamgr process became down automatically or was shut down manually. · Failed to use AP private data to upgrade backup BSS. · Failed to upgrade backup BSS. · Failed to synchronize service template data to the Merger bind list while upgrading backup data. |
|
Severity level |
6 |
|
Example |
STAMGR/6/SERVICE_OFF: BSS 0023-12ef-78dc was deleted after service template st1 with SSID st1ssid was unbound from radio 1 on AP ap1. Reason: Failed to find configuration data while synchronizing data. |
|
Explanation |
The BSS was deleted for a specific reason. |
|
Recommended action |
To resolve the issue: 1. Verify that the BSS is deleted as requested. If the BSS is deleted as requested, no action is required. 2. Locate the deletion cause and remove the issue if the BSS is deleted abnormally, 3. If the issue persists, contact H3C Support. |
STAMGR_SERVICE_ON
|
Message text |
BSS [STRING] was created after service template [STRING] with SSID [STRING] was bound to radio [STRING] on AP [STRING]. |
|
Variable fields |
$1: BSSID. $2: Name of the service template. $3: SSID defined in the service template. $4: Radio ID. $5: AP name. |
|
Severity level |
6 |
|
Example |
STAMGR/6/SERVICE_ON: BSS 0023-12ef-78dc was created after service template st1 with SSID 1 was bound to radio 1 on AP ap1. |
|
Explanation |
The BSS was created. |
|
Recommended action |
No action is required. |
STAMGR_STA_ADDMOB_LKUP_ENDOFIOCTL
|
Message text |
APID=[UINT32]-MAC=[STRING]-BSSID=[STRING]; AC doesn't need to send client information to uplink device: Client information already arrived at the end of the IOCTL tunnel. |
|
Variable fields |
$1: ID of the AP associated with the client. $2: MAC address of the client. $3: BSSID of the service template associated with the client. |
|
Severity level |
7 |
|
Example |
STAMGR/7/STAMGR_STA_ADDMOB_LKUP_ENDOFIOCTL: APID=667-MAC=d4f4-6f69-d7a1-BSSID=600b-0301-d5a0; The AC doesn't need to send client information to uplink device: Client information already arrived at the end of the IOCTL tunnel. |
|
Explanation |
The AC does not need to send client information to the uplink device because client information already arrived at the end of the IOCTL tunnel. |
|
Recommended action |
To resolve the issue depending on the network infrastructure: · Fit AP+AC network—No action is required if this message is output. If no message is output, locate the issue according to the debugging information and resolve the issue. · AC hierarchical network—No action is required if this message is output by the central AC. If this message is output by a local AC, locate the issue according to the debugging information and resolve the issue. |
STAMGR_STAIPCHANGE_INFO
|
Message text |
IP address of client [STRING] changed to [STRING]. |
|
Variable fields |
$1: MAC address of the client. $2: New IP address of the client. |
|
Severity level |
6 |
|
Example |
STAMGR/6/STAMGR_STAIPCHANGE_INFO: IP address of client 3ce5-a616-28cd changed to 4.4.4.4. |
|
Explanation |
The IP address of the client was updated. |
|
Recommended action |
No action is required. |
STAMGR_TRIGGER_IP
|
Message text |
|
|
Variable fields |
$1: SSID. $2: MAC address of the client. $3: Name of the AP associated with the client. $4: ID of the radio associated with the client. $5: ID of the access VLAN. $6: Action: · Added the user to the blocked MAC address list. · Closed the user's BSS temporarily. · Closed the user's BSS permanently. |
|
Severity level |
5 |
|
Example |
|
|
Explanation |
Intrusion protection was triggered and the action was displayed. |
|
Recommended action |
No action is required. |
STM messages
This section contains IRF messages.
STM_AUTO_UPDATE_FAILED
|
Message text |
Pattern 1: Slot [UINT32] auto-update failed. Reason: [STRING]. Pattern 2: Chassis [UINT32] slot [UINT32] auto-update failed. Reason: [STRING]. |
|
Variable fields |
Pattern 1: $1: IRF member ID. $2: Failure reason: ¡ Timeout when loading—The IRF member device failed to complete loading software within the required time period. ¡ Wrong description when loading—The file description in the software image file does not match the current attributes of the software image. This issue might occur when the file does not exist or is corrupted. ¡ Disk full when writing to disk—The storage medium does not have sufficient space. Pattern 2: $1: IRF member ID. $2: Slot number of an MPU. $3: Failure reason: ¡ Timeout when loading—The MPU failed to complete loading software within the required time period. ¡ Wrong description when loading—The file description in the software image file does not match the current attributes of the software image. This issue might occur when the file does not exist or is corrupted. ¡ Disk full when writing to disk—The MPU does not have sufficient storage space. |
|
Severity level |
4 |
|
Example |
STM/4/STM_AUTO_UPDATE_FAILED: Slot 5 auto-update failed. Reason: Timeout when loading. |
|
Explanation |
Pattern 1: Software synchronization from the master failed on a subordinate device. Pattern 2: Software synchronization from the global active MPU failed on a standby MPU. |
|
Recommended action |
1. Remove the issue depending on the failure reason: ¡ If the failure reason is Timeout when loading, verify that all IRF links are up. ¡ If the failure reason is Wrong description when loading, download the software images again. ¡ If the failure reason is Disk full when writing to disk, delete unused files to free the storage space. 2. Upgrade software manually for the device or MPU to join the IRF fabric, and then connect the device to the IRF fabric. |
STM_AUTO_UPDATE_FINISHED
|
Message text |
Pattern 1: File loading finished on slot [UINT32]. Pattern 2: File loading finished on chassis [UINT32] slot [UINT32]. |
|
Variable fields |
Pattern 1: $1: IRF member ID. Pattern 2: $1: IRF member ID. $2: Slot number of an MPU. |
|
Severity level |
5 |
|
Example |
STM/5/STM_AUTO_UPDATE_FINISHED: File loading finished on slot 3. |
|
Explanation |
Pattern 1: The member device finished loading software images. Pattern 2: The MPU finished loading software images. |
|
Recommended action |
No action is required. |
STM_AUTO_UPDATING
|
Message text |
Pattern 1: Don't reboot the slot [UINT32]. It is loading files. Pattern 2: Don't reboot the chassis [UINT32] slot [UINT32]. It is loading files. |
|
Variable fields |
Pattern 1: $1: IRF member ID. Pattern 2: $1: IRF member ID. $2: Slot number of an MPU. |
|
Severity level |
5 |
|
Example |
STM/5/STM_AUTO_UPDATING: Don't reboot the slot 2. It is loading files. |
|
Explanation |
Pattern 1: The member device is loading software images. To avoid software upgrade failure, do not reboot the member device. Pattern 2: The MPU is loading software images. To avoid software upgrade failure, do not reboot the MPU. |
|
Recommended action |
No action is required. |
STM_HELLOPKT_NOTSEND
|
Message text |
Hello thread hasn't sent packets for [UINT32] seconds. |
|
Variable fields |
$1: Time value. |
|
Severity level |
5 |
|
Example |
STM/5/STM_HELLOPKT_NOTSEND: Hello thread hasn't sent packets for 10 seconds. |
|
Explanation |
The hello thread hasn't sent packets for a period of time. |
|
Recommended action |
1. Execute the display cpu-usage command to identify whether the CPU usage has temporarily increased to a high level and locate the cause. For example, the CPU usage increases dramatically when an attack occurs or when the system is processing CPU-intensive tasks. 2. Execute the display process command to identify the processes that cause the CPU usage increase and decrease the CPU usage accordingly. 3. If the issue persists, collect configuration files, log messages, and alarm messages and send them to the technical support for help. |
STM_HELLOPKT_NOTRCV
|
Message text |
Hello thread hasn't received packets for [UINT] seconds. |
|
Variable fields |
$1: Time value. |
|
Severity level |
5 |
|
Example |
STM/5/STM_HELLOPKT_NOTRCV: Hello thread hasn't received packets for 10 seconds. |
|
Explanation |
The hello thread hasn't received packets for a period of time. |
|
Recommended action |
Check for IRF link failure and follow the instructions in "STM_LINK_DOWN" to resolve the issue. |
STM_LINK_DOWN
|
Message text |
IRF port [UINT32] went down. |
|
Variable fields |
$1: IRF port name. |
|
Severity level |
3 |
|
Example |
STM/3/STM_LINK_DOWN: IRF port 2 went down. |
|
Explanation |
This event occurs when all physical interfaces bound to an IRF port are down. |
|
Recommended action |
Log in to the local device, and then execute the display irf link command to obtain the IRF physical interfaces used on the device. Perform the following tasks based on the IRF physical interfaces: 1. Execute the display device command on the neighboring member device to identify whether the neighboring member device is running correctly. If it is not running correctly, locate the cause and resolve the issue accordingly. 2. Execute the display irf link command on the neighboring member device to check the IRF port configuration for configuration errors. If configuration errors exist, modify IRF port bindings in IRF port view. 3. Verify that the IRF connections are correct. You must connect the physical interfaces of IRF-port 1 on one member to the physical interfaces of IRF-port 2 on the other. If the IRF fabric contains only two member devices, do not connect them in ring topology. After you ensure that the IRF connections are correct, execute the display irf link command again to verify that the IRF physical interfaces are up. If the IRF physical interfaces are not up, go to the next step. 4. Use other ports to replace the IRF physical interfaces that are not up. For this purpose, execute the undo port group interface command in IRF port view to unbind the IRF physical interfaces from the IRF port, and then execute the port group interface command in IRF port view to bind other ports to the IRF port. Connect the new IRF physical interfaces to the IRF physical interfaces on the neighboring member device. Then, execute the display irf link command again to verify that the new IRF physical interfaces are up. If the IRF physical interfaces are not up, go to the next step. 5. Change the cables or fibers, and then execute the display irf link command again to verify that the IRF physical interfaces are up. If the IRF physical interfaces are not up, go to the next step. 6. If the issue persists, collect alarm messages and configuration information and contact the technical support for help. |
STM_LINK_TIMEOUT
|
Message text |
IRF port [UINT32] went down because the heartbeat timed out. |
|
Variable fields |
$1: IRF port name. |
|
Severity level |
2 |
|
Example |
STM/2/STM_LINK_TIMEOUT: IRF port 1 went down because the heartbeat timed out. |
|
Explanation |
The IRF port went down because of heartbeat timeout. |
|
Recommended action |
Check the IRF link for link failure and follow the instructions in "STM_LINK_DOWN" to resolve the issue. |
STM_LINK_UP
|
Message text |
IRF port [UINT32] came up. |
|
Variable fields |
$1: IRF port name. |
|
Severity level |
6 |
|
Example |
STM/6/STM_LINK_UP: IRF port 1 came up. |
|
Explanation |
An IRF port came up. |
|
Recommended action |
No action is required. |
STM_MERGE
|
Message text |
IRF merge occurred. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
STM/4/STM_MERGE: IRF merge occurred. |
|
Explanation |
IRF merge occurred. |
|
Recommended action |
No action is required. |
STM_MERGE_NEED_REBOOT
|
Message text |
IRF merge occurred. This IRF system needs a reboot. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
STM/4/STM_MERGE_NEED_REBOOT: IRF merge occurred. This IRF system needs a reboot. |
|
Explanation |
You must reboot the current IRF fabric for IRF merge, because it failed in the master election. |
|
Recommended action |
Log in to the IRF fabric, and use the reboot command to reboot the IRF fabric. |
STM_MERGE_NOT_NEED_REBOOT
|
Message text |
IRF merge occurred. This IRF system does not need to reboot. |
|
Variable fields |
N/A |
|
Severity level |
5 |
|
Example |
STM/5/STM_MERGE_NOT_NEED_REBOOT: IRF merge occurred. This IRF system does not need to reboot. |
|
Explanation |
You do not need to reboot the current IRF fabric for IRF merge, because it was elected the master. |
|
Recommended action |
Reboot the IRF fabric that has failed in the master election to finish the IRF merge. |
STM_SAMEMAC
|
Message text |
Failed to stack because of the same bridge MAC addresses. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
STM/4/STM_SAMEMAC: Failed to stack because of the same bridge MAC addresses. |
|
Explanation |
Failed to set up the IRF fabric because some member devices are using the same bridge MAC address. |
|
Recommended action |
1. Verify that IRF bridge MAC persistence is disabled on the member devices. To disable this feature, use the undo irf mac-address persistent command. 2. If the issue persists, contact H3C Support. |
STM_SOMER_CHECK
|
Message text |
Neighbor of IRF port [UINT32] cannot be stacked. |
|
Variable fields |
$1: IRF port name. |
|
Severity level |
3 |
|
Example |
STM/3/STM_SOMER_CHECK: Neighbor of IRF port 1 cannot be stacked. |
|
Explanation |
The neighbor connected to the IRF port cannot form an IRF fabric with the device. |
|
Recommended action |
Check the following items: · The device models can form an IRF fabric. · The IRF settings are correct. For more information, see the IRF configuration guide for the device. |
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 |
M-LAG role assignment finished. Please verify that the local device and the peer device have consistent global and mlag-interface-specific STP settings. |
|
Variable fields |
N/A |
|
Severity level |
5 |
|
Example |
STP/5/STP_CONSISTENCY_CHECK: M-LAG role assignment finished. Please verify that the local device and the peer device have consistent global and mlag-interface-specific STP settings. |
|
Explanation |
The M-LAG member devices in an M-LAG system must have the same global and mlag-interface-specific STP settings. |
|
Recommended action |
N/A |
STP_CONSISTENCY_RESTORATION
|
Message text |
|
|
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_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 |
|
|
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 |
|
|
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 |
|
|
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. |
STP_STG_NUM_DETECTION
|
Message text |
STG count [UINT32] is smaller than the MPU's STG count [UINT32]. |
|
Variable fields |
$1: Number of STGs on a card. $2: Number of STGs on the MPU. |
|
Severity level |
4 |
|
Example |
STP/4/STP_STG_NUM_DETECTION: STG count 64 is smaller than the MPU's STG count 65. |
|
Explanation |
The system detected that the STG count on a card was smaller than that on the MPU. |
|
Recommended action |
Make sure the number of spanning tree instances is not larger than the smallest card-specific STG count. For example, if the number of spanning tree instances is m and the smallest STG count among cards is n, m cannot be larger than n. |
STRUNK
This section contains smart trunk messages.
STRUNK_DROPPACKET_INCONSISTENCY
|
Message text |
Smart trunk [UINT32] dropped the S-Trunk protocol packet because [STRING]. |
|
Variable fields |
$1: Smart trunk ID. $2: Reason for dropping packets: · the source and destination IP addresses or VPN instance of S-Trunk protocol packets are not configured on the local device. · the packet's source or destination IP address does not match the local configuration. · the VPN instance of S-Trunk protocol packets is different from the local VPN instance. · the sequence number check failed. · key verification failed. |
|
Severity level |
4 |
|
Example |
STRUNK/4/STRUNK_DROPPACKET_INCONSISTENCY: Smart trunk 10 dropped the S-Trunk protocol packet because key verification failed. |
|
Explanation |
The configurations on the local and the peer devices are inconsistent. |
|
Recommended action |
1. Verify that the configurations are consistent on the local and the peer devices in the smart trunk. 2. If the configurations in the smart trunk are consistent, verify that the illegitimate packets are present. |
STRUNK_MEMBER_ROLE_CHANGE
|
Message text |
Smart trunk member role changed: Interface type=[STRING], interface number=[UINT32], previous role (trigger)=[STRING] ([STRING]), new role (trigger)=[STRING] ([STRING]) |
|
Variable fields |
$1: Member interface type in the smart trunk, including BAGG and RAGG. $2: Member interface number. $3: Previous role of the interface: · Primary. · Secondary. $4: Reason for previous role of the interface: · MANUAL_SECONDARY—The member interface is assigned the secondary role in the smart trunk. · MANUAL_PRIMARY—The member interface is assigned the primary role in the smart trunk. · STRUNK_INIT—The smart trunk is initializing. · AUTO_SECONDARY—The local device in the smart trunk is secondary. · AUTO_PRIMARY—The local device in the smart trunk is primary. · PEER_MEMBER_DOWN—The peer member interface is down. · PEER_MEMBER_UP—The peer member interface is up. $5: Current role of the interface: · Primary. · Secondary. $6: Reason for current role of the interface: · MANUAL_SECONDARY—The member interface is assigned the secondary role in the smart trunk. · MANUAL_PRIMARY—The member interface is assigned the primary role in the smart trunk. · STRUNK_INIT—The smart trunk is initializing. · AUTO_SECONDARY—The local device in the smart trunk is secondary. · AUTO_PRIMARY—The local device in the smart trunk is primary. · PEER_MEMBER_DOWN—The peer member interface is down. · PEER_MEMBER_UP—The peer member interface is up. |
|
Severity level |
5 |
|
Example |
STRUNK/5/STRUNK_MEMBER_ROLE_CHANGE: Smart trunk member role changed: Interface type=BAGG, interface number=1, previous role (trigger)=Secondary (STRUNK_INIT), new role (trigger)=Primary (MANUAL_PRIMARY). |
|
Explanation |
Smart trunk member interface role changed. |
|
Recommended action |
· Verify that the local or peer member device is operating correctly. · Verify that the local or peer member interface is down. |
STRUNK_PDUINTERVAL_MISMATCH
|
Message text |
Smart trunk [UINT32] has a packet transmission interval different than the peer device. |
|
Variable fields |
$1: Smart trunk ID. |
|
Severity level |
5 |
|
Example |
STRUNK/5/STRUNK_PDUINTERVAL_MISMATCH: Smart trunk 1 has a packet transmission interval different than the peer device. |
|
Explanation |
The interval on the local device for sending S-Trunk protocol packets is different from the peer in the smart trunk. One of the devices times out incorrectly. |
|
Recommended action |
Set the same interval for sending S-Trunk protocol packets in the smart trunk. |
STRUNK_RECEIVE_TIMEOUT
|
Message text |
Hello timeout timer expired on smart trunk [UINT32]. |
|
Variable fields |
$1: Smart trunk ID. |
|
Severity level |
4 |
|
Example |
STRUNK/4/STRUNK_RECEIVE_TIMEOUT: Hello timeout timer expired on smart trunk 1. |
|
Explanation |
The local device does not receive S-Trunk protocol packets from the peer before the timeout timer expires. |
|
Recommended action |
· Verify that the S-Trunk link is up. · Verify that the CPU is occupying too much resource. |
STRUNK_ROLE_CHANGE
|
Message text |
The role of the device changed in a smart trunk: Smart trunk ID=[UINT32], previous role (trigger)=[STRING] ([STRING]), new role (trigger)=[STRING] ([STRING]) |
|
Variable fields |
$1: Smart trunk ID. $2: Previous role in the smart trunk: · Init—Initialized. · Primary. · Secondary. $4: Reason for previous role in the smart trunk: · INIT—The smart trunk is initializing. · PRIORITY—The role in the smart trunk depends on the priority. · TIMEOUT—The local device becomes primary for not receiving S-Trunk protocol packets from the peer before the timeout timer expires. · PEER_TIMEOUT—The peer device becomes primary for not receiving S-Trunk protocol packets from the local before the timeout timer expires. · BFD_DOWN—The local device detects that the link is down between the local and the peer through BFD. · PEER_BFD_DOWN—The peer device detects that the link is down between the local and the peer through BFD. $5: Current role in the smart trunk: · Init—Initialized. · Primary. · Secondary. $6: Reason for current role in the smart trunk: · INIT—The smart trunk is initializing. · PRIORITY—The role of the smart trunk depends on the priority. · TIMEOUT—The local device becomes primary for not receiving S-Trunk protocol packets from the peer before the timeout timer expires. · PEER_TIMEOUT—The peer device becomes primary for not receiving S-Trunk protocol packets from the local before the timeout timer expires. · BFD_DOWN—The local device detects that the link is down between the local and the peer through BFD. · PEER_BFD_DOWN—The peer device detects that the link is down between the local and the peer through BFD. |
|
Severity level |
5 |
|
Example |
STRUNK/5/STRUNK_ROLE_CHANGE: The role of the device changed in a smart trunk: Smart trunk ID=1, previous role (trigger)=Init (INIT), new role (trigger)=Secondary (PRIORITY) |
|
Explanation |
The smart trunk role changed. |
|
Recommended action |
Verify that the link between the devices in the smart trunk is Layer 3 reachable. |
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_ACCT_SERVER_DOWN
|
Message text |
TACACS accounting server was blocked: Server IP=[STRING], port=[UINT32], VPN instance=[STRING]. |
|
Variable fields |
$1: IP address of the accounting server. $2: Port number of the accounting server. $3: VPN instance name. This field displays public if the server belongs to the public network. |
|
Severity level |
4 |
|
Example |
TACACS/4/TACACS_ACCT_SERVER_DOWN: TACACS accounting server was blocked: Server IP=1.1.1.1, port=1812, VPN instance=public. |
|
Explanation |
An accounting server became blocked. |
|
Recommended action |
1. Verify that the accounting server has started up. 2. Ping the accounting server to verify that the server is reachable. If the server is not reachable, check the link for connectivity issues and resolve the issues. 3. Collect logs and diagnostic logs, and then contact the technical support. |
TACACS_ACCT_SERVER_UP
|
Message text |
TACACS accounting server became active: Server IP=[STRING], port=[UINT32], VPN instance=[STRING]. |
|
Variable fields |
$1: IP address of the accounting server. $2: Port number of the accounting server. $3: VPN instance name. This field displays public if the server belongs to the public network. |
|
Severity level |
6 |
|
Example |
TACACS/6/TACACS_ACCT_SERVER_UP: TACACS accounting server became active: Server IP=1.1.1.1, port=1812, VPN instance=public. |
|
Explanation |
An accounting server became active. |
|
Recommended action |
No action is required. |
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_SERVER_DOWN
|
Message text |
TACACS authentication server was blocked: Server IP=[STRING], port=[UINT32], VPN instance=[STRING]. |
|
Variable fields |
$1: IP address of the authentication server. $2: Port number of the authentication server. $3: VPN instance name. This field displays public if the server belongs to the public network. |
|
Severity level |
4 |
|
Example |
TACACS/4/TACACS_AUTH_SERVER_DOWN: TACACS authentication server was blocked: Server IP=1.1.1.1, port=1812, VPN instance=public. |
|
Explanation |
An authentication server became blocked. |
|
Recommended action |
1. Verify that the authentication server has started up. 2. Ping the authentication server to verify that the server is reachable. If the server is not reachable, check the link for connectivity issues and resolve the issues. 3. Collect logs and diagnostic logs, and then contact the technical support. |
TACACS_AUTH_SERVER_UP
|
Message text |
TACACS authentication server became active: Server IP=[STRING], port=[UINT32], VPN instance=[STRING]. |
|
Variable fields |
$1: IP address of the authentication server. $2: Port number of the authentication server. $3: VPN instance name. This field displays public if the server belongs to the public network. |
|
Severity level |
6 |
|
Example |
TACACS/6/TACACS_AUTH_SERVER_UP: TACACS authentication server became active: Server IP=1.1.1.1, port=1812, VPN instance=public. |
|
Explanation |
An authentication server became active. |
|
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_AUTHOR_SERVER_DOWN
|
Message text |
TACACS authorization server was blocked: Server IP=[STRING], port=[UINT32], VPN instance=[STRING]. |
|
Variable fields |
$1: IP address of the authorization server. $2: Port number of the authorization server. $3: VPN instance name. This field displays public if the server belongs to the public network. |
|
Severity level |
4 |
|
Example |
TACACS/4/TACACS_AUTHOR_SERVER_DOWN: TACACS authorization server was blocked: Server IP=1.1.1.1, port=1812, VPN instance=public. |
|
Explanation |
An authorization server became blocked. |
|
Recommended action |
1. Verify that the authorization server has started up. 2. Ping the authorization server to verify that the server is reachable. If the server is not reachable, check the link for connectivity issues and resolve the issues. 3. Collect logs and diagnostic logs, and then contact the technical support. |
TACACS_AUTHOR_SERVER_UP
|
Message text |
TACACS authorization server became active: Server IP=[STRING], port=[UINT32], VPN instance=[STRING]. |
|
Variable fields |
$1: IP address of the authorization server. $2: Port number of the authorization server. $3: VPN instance name. This field displays public if the server belongs to the public network. |
|
Severity level |
6 |
|
Example |
TACACS/6/TACACS_AUTHOR_SERVER_UP: TACACS authorization server became active: Server IP=1.1.1.1, port=1812, VPN instance=public. |
|
Explanation |
An authorization server became active. |
|
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. |
TCSM
This section contains Trusted Computing Services Management (TCSM) messages.
TCSM_CERT_BROKEN
|
Message text |
Certificate [STRING] is missing or corrupted. |
|
Variable fields |
$1: Certificate name. |
|
Severity level |
3 |
|
Example |
TCSM/3/TCSM_CERT_BROKEN: Certificate ak1-cert is missing or corrupted. |
|
Explanation |
A certificate stored in a storage medium is lost or corrupted. |
|
Recommended action |
· If the certificate is user defined, perform the following tasks: a. Replace the storage medium. b. From the manager, sign a new certificate for the TCSM key of the device. · If the certificate is system defined, contact H3C Support. |
TCSM_KEY_BROKEN
|
Message text |
Key [STRING] is corrupted or missing. |
|
Variable fields |
$1: Key name. |
|
Severity level |
3 |
|
Example |
TCSM/3/TCSM_KEY_BROKEN: Key abc is corrupted or missing. |
|
Explanation |
A key file stored in a storage medium is lost or corrupted. |
|
Recommended action |
· If the key is user defined, perform the following tasks: a. Use the key destroy command to destroy the key. b. As a best practice, replace the storage medium. · If the key is system defined, contact H3C Support. |
TCSM_KEY_HIERARCHY_BROKEN
|
Message text |
Key hierarchy of [STRING] is corrupted. |
|
Variable fields |
$1: Key name |
|
Severity level |
3 |
|
Example |
TCSM/3/TCSM_KEY_HIERARCHY_BROKEN: Key hierarchy of abc is corrupted. |
|
Explanation |
An upper-level key of the specified key is corrupted. |
|
Recommended action |
2. Use the key destroy command to destroy the specified key and its upper-level keys. 1. As a best practice, replace the storage medium. |
TCSM_TSS_SVC_DOWN
|
Message text |
TSS service is down. |
|
Variable fields |
N/A |
|
Severity level |
3 |
|
Example |
TCSM/3/TCSM_TSS_SVC_DOWN: TSS service is down. |
|
Explanation |
The TPM software stack process is down. |
|
Recommended action |
Contact H3C Support. |
TCSM_TSS_SVC_UP
|
Message text |
TSS service is up. |
|
Variable fields |
N/A |
|
Severity level |
5 |
|
Example |
TCSM/5/TCSM_TSS_SVC_UP: TSS service is up. |
|
Explanation |
The TPM software stack process is up. |
|
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 |
|
|
Example |
|
|
Explanation |
The number of Telnet connections reached the limit. |
|
Recommended action |
1. 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. 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. |
TSTREAM
This section contains telemetry stream messages.
STREAM_ENCAP_FAIL
|
Message text |
Failed to set telemetry stream addressing parameters. Reason: [STRING]. |
|
Variable fields |
$1: Failure reason. · The output interface is not supported. |
|
Severity level |
4 |
|
Example |
STREAM/4/STREAM_ENCAP_FAIL: Failed to set telemetry stream addressing parameters. Reason: The output interface is not supported. |
|
Explanation |
This message is generated when the IP address of the management port on the collector is specified as the destination IP address in the telemetry stream collector command. |
|
Recommended action |
1. Configure the IP address of any other port on the collector as the destination IP address. 2. If the problem persists, contact Technical Support. |
VCF messages
This section contains VCF messages.
VCF_AGGR_CREAT
|
Message text |
Phase [STRING], Device [STRING] created Layer 2 aggregation group [INT32]: member ports=[STRING]. |
|
Variable fields |
$1: Phase. $2: MAC address of the device. $3: ID of a Layer 2 aggregation group. $4: List of Layer 2 aggregation member ports. |
|
Severity level |
6 |
|
Example |
VCF/6/VCF_AGGR_CREAT: Phase 2.0.5, Device 0000-0000-0000 created Layer 2 aggregation group 10: member ports=Ten-GigabitEthernet1/0/2, Ten-GigabitEthernet1/0/10. |
|
Explanation |
A Layer 2 aggregation group was created and member ports were added to the aggregation group. |
|
Recommended action |
No action is required. |
VCF_AGGR_DELETE
|
Message text |
Phase [STRING], Device [STRING] deleted Layer 2 aggregation group [INT32]. |
|
Variable fields |
$1: Phase. $2: MAC address of the device. $3: ID of a Layer 2 aggregation group. |
|
Severity level |
6 |
|
Example |
VCF/6/VCF_AGGR_DELETE: Phase 2.0.6, Device 0000-0000-0000 deleted Layer 2 aggregation group 10. |
|
Explanation |
A Layer 2 aggregation group was deleted when only one link in the aggregation group was up. |
|
Recommended action |
No action is required. |
VCF_AGGR_FAILED
|
Message text |
Phase [STRING], Device [STRING] failed to create Layer 2 aggregation group [INT32]. |
|
Variable fields |
$1: Phase. $2: MAC address of the device. $3: ID of a Layer 2 aggregation group. |
|
Severity level |
3 |
|
Example |
VCF/3/ VCF_AGGR_FAILED: Phase 2.0.7, Device 0000-0000-0000 failed to create Layer 2 aggregation group 10. |
|
Explanation |
Failed to create a Layer 2 aggregation group. |
|
Recommended action |
Troubleshoot the reasons for the aggregation group creation failure, such as insufficient resources. |
VCF_AUTO_ANALYZE_USERDEF
|
Message text |
Phase [STRING], Device [STRING] started to parse template file. |
|
Variable fields |
$1: Phase. $2: MAC address of the device. |
|
Severity level |
6 |
|
Example |
VCF/6/VCF_AUTO_ANALYZE_USERDEF: Phase 1.2.2, Device 0000-0000-0000 started to parse template file. |
|
Explanation |
Started to parse user-defined configurations in the template file. |
|
Recommended action |
No action is required. |
VCF_AUTO_START
|
Message text |
Phase [STRING], Device [STRING] (Role [STRING]) started VCF automated deployment. |
|
Variable fields |
$1: Phase. $2: MAC address of the device. $3: Role of the device, spine, leaf, or access. |
|
Severity level |
5 |
|
Example |
VCF/5/VCF_AUTO_START: Phase 1.0.1, Device 0000-0000-0000 (Role leaf) started VCF automated deployment. |
|
Explanation |
Started VCF automated deployment. |
|
Recommended action |
No action is required. |
VCF_AUTO_STATIC_CMD
|
Message text |
Phase [STRING], Device [STRING] automatically executed static commands. |
|
Variable fields |
$1: Phase. $2: MAC address of the device. |
|
Severity level |
6 |
|
Example |
VCF/6/VCF_AUTO_STATIC_CMD: Phase 1.2.4, Device 0000-0000-0000 automatically executed static commands. |
|
Explanation |
Executed static commands in the template file. Static commands refer to commands that are independent from the VCF fabric topology. |
|
Recommended action |
No action is required. |
VCF_BGP
|
Message text |
Phase [STRING], Device [STRING] established a BGP session with peer [STRING] in AS [INT32]. Pattern 2: Phase [STRING], Device [STRING] established a BGP session with peers [[STRING]] in AS [INT32]. |
|
Variable fields |
Pattern 1: $1: Phase. $2: MAC address of the device. $3: Address of a BGP peer. $4: Number of the AS where the BGP peer resides. Pattern 2: $1: Phase. $2: MAC address of the device. $3: List of BGP peer addresses, separated by commas (,). $4: Number of the AS where the BGP peers reside. |
|
Severity level |
6 |
|
Example |
Pattern 1: VCF/6/VCF_BGP: Phase 3.0.5, Device 0000-0000-0000 established a BGP session with peer 1.1.1.1 in AS 100. Pattern 2: VCF/6/VCF_BGP: Phase 3.0.5, Device 0000-0000-0000 established a BGP session with peers [‘1.1.1.1’ , ‘1.1.1.2’] in AS 100. |
|
Explanation |
Pattern 1: Established a BGP session with a BGP peer. Pattern 2: Established BGP sessions with multiple BGP peers. Only the master spine node on a Layer 3 network generates this message. |
|
Recommended action |
No action is required. |
VCF_DOWN_LINK
|
Message text |
Phase [STRING], Device [STRING] discovered downlink interface [STRING]. |
|
Variable fields |
$1: Phase. $2: MAC address of the device. $3: Name of a downlink interface. |
|
Severity level |
6 |
|
Example |
VCF/6/VCF_DOWN_LINK: Phase 2.0.8, Device 0000-0000-0000 discovered downlink interface Ten-GigabitEthernet1/0/1. |
|
Explanation |
A downlink interface was found and the device deployed configuration to the downlink interface. On a spine node, a downlink interface is the interface through which the spine node connects to a leaf node. On a leaf node, a downlink interface is the interface through which the leaf node connects to a downstream access device. |
|
Recommended action |
No action is required. |
VCF_DRIVER_INIT
|
Message text |
Phase [STRING], failed to find driver [STRING]. Driver initialization failed. |
|
Variable fields |
$1: Phase. $2: Driver name. |
|
Severity level |
3 |
|
Example |
VCF/3/VCF_DRIVER_INIT: Phase 3.0.8, failed to find driver 6820. Driver initialization failed. |
|
Explanation |
Driver initialization failed because the driver was not found. |
|
Recommended action |
1. Verify that the name of the driver is correct. 2. Contact H3C Support to verify that VCF fabric supports the driver. |
VCF_FAILED_ADD_IRFPORT
|
Message text |
Phase [STRING], failed to bind IRF physical interface [STRING] on device with MAC address [STRING] to an IRF port three times. |
|
Variable fields |
$1: Phase. $2: IRF physical interface. $3: MAC address. |
|
Severity level |
4 |
|
Example |
VCF/4/VCF_FAILED_ADD_IRFPORT: Phase 2.0.10, failed to bind IRF physical interface [STRING] on device with MAC address 4c85-5206-0100 to an IRF port three times. |
|
Explanation |
This message is generated if the system fails to bind an IRF physical interface on a device to an IRF port three times and stops the attempt during automated deployment. |
|
Recommended action |
Check physical links between IRF member devices in the VCF fabric. |
VCF_GET_IMAGE
|
Message text |
Phase [STRING], Device [STRING] obtained information about update startup image file [STRING]: new version=[STRING], current version=[STRING]. |
|
Variable fields |
$1: Phase. $2: MAC address of the device. $3: Name of the new startup image file. $4: Version number of the new startup image file. $5: Version number of the current startup image file. |
|
Severity level |
6 |
|
Example |
VCF/6/VCF_GET_IMAGE: Phase 1.3.1, Device 0000-0000-0000 obtained information about update startup image file s6800.ipe: new version=V300R009B01D002, current version=V300R009B01D001. |
|
Explanation |
Obtained the name and the version number of the new startup image file through the template file. |
|
Recommended action |
No action is required. |
VCF_GET_TEMPLATE
|
Message text |
Phase [STRING], Device [STRING] downloaded template file [STRING]. |
|
Variable fields |
$1: Phase. $2: MAC address of the device. $3: Name of the template file. |
|
Severity level |
6 |
|
Example |
VCF/6/VCF_GET_TEMPLATE: Phase 1.2.1, Device 0000-0000-0000 downloaded template file /mnt/flash:/vxlan_spine.template. |
|
Explanation |
Downloaded the template file for automated deployment. |
|
Recommended action |
No action is required. |
VCF_INSTALL_IMAGE
|
Message text |
Phase [STRING], Device [STRING] started to install the [STRING] version of startup image. |
|
Variable fields |
$1: Phase. $2: MAC address of the device. $3: Version number of the new startup image file. |
|
Severity level |
6 |
|
Example |
VCF/6/VCF_INSTALL_IMAGE: Phase 1.3.3, Device 0000-0000-0000 started to install the V700R001B70D001 version of startup image. |
|
Explanation |
Started to install the new software version. |
|
Recommended action |
No action is required. |
VCF_IRF_FINISH
|
Message text |
Phase [STRING], Device [STRING] finished IRF configuration: result=[INT32]. |
|
Variable fields |
$1: Phase. $2: MAC address of the device. $3: Result of IRF configuration: · 0—Success. · -1—Failure. |
|
Severity level |
5 |
|
Example |
VCF/5/VCF_IRF_FINISH: Phase 2.0.3, Device 0000-0000-0000 finished IRF configuration: result=0. |
|
Explanation |
Finished IRF configuration. |
|
Recommended action |
Contact H3C Support if IRF configuration failed. |
VCF_IRF_FOUND
|
Message text |
Phase [STRING], Device [STRING] (Role [STRING]) found a peer ([STRING]) with the same role, IRF stackability check result: [INT32]. |
|
Variable fields |
$1: Phase. $2: MAC address of the device. $3: Role of the device. $4: MAC address of the peer device. $5: Result of the IRF stackability check: · 0—Capable to form an IRF fabric. · 1—MAC address conflict. |
|
Severity level |
5 |
|
Example |
VCF/5/VCF_IRF_FOUND: Phase 2.0.1, Device 0000-0000-0000 (Role leaf) found a peer with the same role, IRF stackability check result: 0. |
|
Explanation |
Found a peer device with the same role in VCF fabric topology discovery and checked whether the device can form an IRF fabric with the peer device. |
|
Recommended action |
No action is required. |
VCF_IRF_START
|
Message text |
Phase [STRING], Device [STRING] started IRF configuration: current member ID=[INT32], new member ID=[INT32], priority=[INT32], IRF-port 1's member ports=[STRING], IRF-port 2's member ports=[STRING]. |
|
Variable fields |
$1: Phase. $2: MAC address of the device. $3: Current IRF member ID of the device. $4: New IRF member ID of the device. $5: New IRF member priority of the device. $6: List of IRF physical interfaces bound to IRF-port 1. The value none indicates that no IRF physical interfaces were bound to IRF-port 1. $7: List of IRF physical interfaces bound to IRF-port 2. The value none indicates that no IRF physical interfaces were bound to IRF-port 2. |
|
Severity level |
5 |
|
Example |
VCF/5/VCF_IRF_START: Phase 2.0.2, Device 0000-0000-0000 started IRF configuration: current member ID=2, new member ID=1, priority=2, IRF-port 1's member ports=GigabitEthernet1/0/1, IRF-port 2's member ports=none. |
|
Explanation |
Started to deploy IRF configuration. |
|
Recommended action |
No action is required. |
VCF_LOOPBACK_START
|
Message text |
Phase [STRING], IP address assignment started for [STRING] on other nodes. |
|
Variable fields |
$1: Phase. $2: Interface name. |
|
Severity level |
5 |
|
Example |
VCF/5/VCF_LOOPBACK_START: Phase 3.0.1, IP address assignment started for Loopback0 on other nodes. |
|
Explanation |
The master spine node started to assign IP addresses to interfaces on other devices. |
|
Recommended action |
No action is required. |
VCF_LOOPBACK_START_FAILED
|
Message text |
Phase [STRING], failed to assign IP addresses to [STRING] on other nodes: reason=[STRING]. |
|
Variable fields |
$1: Phase. $2: Interface name. $3: Reason for failure to start IP address assignment: ¡ -1—No IP address range is specified. ¡ -2—Invalid IP addresses. |
|
Severity level |
5 |
|
Example |
VCF/5/VCF_LOOPBACK_START_FAILED: Phase 3.0.1, failed to assign IP addresses to Loopback0 on other nodes: reason=-1. |
|
Explanation |
The master spine node failed to assign IP addresses to interfaces on other devices due to one of the following reasons: · No IP address range is specified. · Invalid IP addresses. |
|
Recommended action |
Verify that whether the IP address range in the template file is correct. |
VCF_LOOPBACK_ALLOC
|
Message text |
Phase [STRING], assigned IP [STRING] to [STRING] on Device [STRING]: result=[INT32]. |
|
Variable fields |
$1: Phase. $2: IP address. $3: Interface name. $4: MAC address of the device. $5: Result of IP address assignment: ¡ 0—Success. ¡ -1—NETCONF failed to implement IP address assignment. ¡ -2—NETCONF processed IP address assignment incorrectly. ¡ -3—NETCONF failed to initialize. |
|
Severity level |
5 |
|
Example |
VCF/5/VCF_LOOPBACK_ALLOC: Phase 3.0.2, assigned IP 10.100.1.1 to Loopback0 on Device 0000-0000-0000: result=0. |
|
Explanation |
The master spine node assigned an IP address to an interface on a device. |
|
Recommended action |
Troubleshoot the reasons for the IP address assignment failure according to the result. |
VCF_LOOPBACK_NO_FREE_IP
|
Message text |
Phase [STRING], no IP addresses available for Device [STRING]. |
|
Variable fields |
$1: Phase. $2: MAC address of the device. |
|
Severity level |
4 |
|
Example |
VCF/4/VCF_LOOPBACK_NO_FREE_IP: Phase 3.0.4, no IP addresses available for Device 0000-0000-0000. |
|
Explanation |
The master spine node failed to assign an IP address to an interface on a device because no IP address was available. |
|
Recommended action |
Verify whether the specified IP address range in the template file is correct. |
VCF_REBOOT
|
Message text |
Phase [STRING], Device [STRING] will reboot. Reason: [STRING]. |
|
Variable fields |
$1: Phase. $2: MAC address of the device. $3: Reboot cause: ¡ Hardware resource mode change. ¡ Version upgrade success. ¡ IRF member ID change. ¡ IRF fabric setup success. ¡ Change of the maximum number of ECMP routes. ¡ Standalone-to-IRF mode switchover. |
|
Severity level |
5 |
|
Example |
VCF/5/VCF_REBOOT: Phase 1.2.3, Device 00e0-fc20-6304 will reboot. Reason: IRF member ID change. |
|
Explanation |
The device was about to reboot because of software update, IRF member ID change, or other reason. |
|
Recommended action |
No action is required. |
VCF_SKIP_INSTALL
|
Message text |
Phase [STRING], Device [STRING] skipped automatic version update. |
|
Variable fields |
$1: Phase. $2: MAC address of the device. |
|
Severity level |
5 |
|
Example |
VCF/5/VCF_SKIP_INSTALL: Phase 1.3.2, Device 0000-0000-0000 skipped automatic version update. |
|
Explanation |
Skipped software upgrade because the current startup image version is the same as the startup image version obtained from the template file. |
|
Recommended action |
No action is required. |
VCF_STATIC_CMD_ERROR
|
Message text |
Phase [STRING], Device [STRING] failed to automatically execute static command '[STRING]' in context '[STRING]'. |
|
Variable fields |
$1: Phase. $2: MAC address of the device. $3: Command that fail to be executed. $4: Context in which the command resides. |
|
Severity level |
4 |
|
Example |
VCF/4/VCF_STATIC_CMD_ERROR: Phase 1.2.5, Device 0000-0000-0000 failed to automatically execute static command 'port link bridge' in context 'interface ten-gigabitethernet1/0/1; port link bridge'. |
|
Explanation |
Failed to execute a static command during automated deployment. |
|
Recommended action |
Troubleshoot the reasons for the failure, correct the errors, and then restart the automated deployment. |
VCF_UP_LINK
|
Message text |
Phase [STRING], Device [STRING] discovered uplink interface [STRING]. |
|
Variable fields |
$1: Phase. $2: MAC address of the device. $3: Name of an uplink interface. |
|
Severity level |
6 |
|
Example |
VCF/6/VCF_UP_LINK: Phase 2.0.9, Device 0000-0000-0000 discovered uplink interface Ten-GigabitEthernet1/0/1. |
|
Explanation |
An uplink interface was found and the device deployed configuration to the uplink interface. An uplink interface is the interface through which a leaf node connects to an upstream spine node. |
|
Recommended action |
No action is required. |
VCF_UPDATE_COPY_FAILED
|
Message text |
Phase [STRING], Device [STRING] failed to copy image. Reason: [STRING]. |
|
Variable fields |
$1: Phase. $2: MAC address of the device. $3: Cause of image copying failure, including: · Insufficient spare space. · Copy failed. |
|
Severity level |
5 |
|
Example |
VCF/5/VCF_UPDATE_COPY_FAILED: Phase 1.3.5, Device 00e0-fc20-6304 failed to copy image. Reason: Insufficient spare space. |
|
Explanation |
A device failed to copy the image during automatic VCF upgrade. If the device failed for three consecutive times, the VCF process exited. |
|
Recommended action |
No action is required. |
VCF_UPDATE_FAILED
|
Message text |
Phase [STRING], Device [STRING] update has failed and end automated deployment. |
|
Variable fields |
$1: Phase. $2: MAC address of the device. |
|
Severity level |
4 |
|
Example |
VCF/5/VCF_UPDATE_FAILED: Phase 1.3.6, Device 00e0-fc20-6304 update has failed and end automated deployment. |
|
Explanation |
A device failed to perform automatic VCF upgrade, and the VCF process exited. |
|
Recommended action |
No action is required. |
VCF_WHITE_LIST_CHECK
|
Message text |
Phase [STRING], Device [STRING] failed whitelist check and automated undelay network deployment stopped. |
|
Variable fields |
$1: Phase. $2: MAC address of the device. |
|
Severity level |
5 |
|
Example |
VCF/5/VCF_WHITE_LIST_CHECK: Phase 1.0.1, Device 00e0-fc20-6304 failed whitelist check and automated undelay network deployment stopped. |
|
Explanation |
The device failed whitelist check, which caused automated undelay network deployment to stop. |
|
Recommended action |
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. · 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. · Controlled by RBM—The state of the VRRP group (master or backup) was controlled by the HA group associated with it. |
|
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. |
VRRP4_MANUAL_PREEMPT_FAILED
|
Message text |
IPv4 virtual router [UINT32] (configured on interface [STRING]) failed to execute manual preemption because the received packet has higher priority. |
|
Variable fields |
$1: VRRP group number. $2: Name of the interface where the VRRP group is configured. |
|
Severity level |
6 |
|
Example |
VRRP4/6/VRRP4_MANUAL_PREEMPT_FAILED: IPv4 virtual router 1 (configured on interface GigabitEthernet1/0/1) failed to execute manual preemption because the received packet has higher priority. |
|
Explanation |
Manual switchover to the original master failed, because the received VRRP advertisement packet has higher priority. |
|
Recommended action |
Check the router priority and status in the VRRP group. |
VRRP6_MANUAL_PREEMPT_FAILED
|
Message text |
IPv6 virtual router [UINT32] (configured on interface [STRING]) failed to execute manual preemption because the received packet has higher priority. |
|
Variable fields |
$1: IPv6 VRRP group number. $2: Name of the interface where the IPv6 VRRP group is configured. |
|
Severity level |
6 |
|
Example |
VRRP6/6/VRRP6_MANUAL_PREEMPT_FAILED: IPv6 virtual router 1 (configured on interface GigabitEthernet1/0/1) failed to execute manual preemption because the received packet has higher priority. |
|
Explanation |
Manual switchover to the original master failed, because the received IPv6 VRRP advertisement packet has higher priority. |
|
Recommended action |
Check the router priority and status in the IPv6 VRRP group. |
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. |
WEB
This section contains common Web messages.
LOGIN
|
Message text |
[STRING] logged in from [STRING]. |
|
Variable fields |
$1: Username. $2: User IP address. |
|
Severity level |
5 |
|
Example |
WEB/5/LOGIN: admin logged in from 127.0.0.1. |
|
Explanation |
A user logged in successfully. |
|
Recommended action |
No action is required. |
LOGIN_FAILED
|
Message text |
[STRING] failed to log in from [STRING], [STRING].. |
|
Variable fields |
1: Username. $2: User IP address. $3: Error message: · AAA authenticated failed · Maximum number of Web users exceeded · Incorrect verify code · Verify code expired |
|
Severity level |
5 |
|
Example |
WEB/5/LOGIN_FAILED: admin failed to log in from 127.0.0.1, AAA authenticated failed. |
|
Explanation |
A user login failed. |
|
Recommended action |
· If error message AAA authenticated failed appears, perform the following operation: ¡ Verify the device connection with the server. ¡ Enter the username and password again. ¡ Verify the server settings are correct. For example, verify that the server type is correct. · If error message Maximum number of Web users exceeded appears, execute the aaa session-limit command to specify the maximum number of Web users that are allowed to log in to the device. · If error message Incorrect verify code or Verify code expired appears, enter a new verification code. |
LOGOUT
|
Message text |
[STRING] logged out from [STRING]. |
|
Variable fields |
1: Username. $2: User IP address. |
|
Severity level |
5 |
|
Example |
WEB/5/LOGOUT: admin logged out from 127.0.0.1. |
|
Explanation |
A user logged out successfully. |
|
Recommended action |
No action is required. |
WEBCACHE messages
This section contains Web caching messages.
WEBCACHE_CHECK
|
Message text |
Web caching is not available.Reason: The system is checking whether the Web cache directory is accessible. Please wait... |
|
Variable fields |
None |
|
Severity level |
4 |
|
Example |
WEBCACHE/4/WEBCACHE_CHECK Web caching is not available. Reason: The system is checking whether the Web cache directory is accessible. Please wait... |
|
Explanation |
The Web caching feature was not available because the system was checking whether the Web cache directory was accessible. |
|
Recommended action |
Wait for the system to finish the check operation. |
WEBCACHE_AVAILABLE
|
Message text |
Web cache directory is accessible. Web caching is available now. |
|
Variable fields |
None |
|
Severity level |
6 |
|
Example |
WEBCACHE/6/WEBCACHE_AVAILABLE: Web cache directory is accessible. Web caching is available now. |
|
Explanation |
The Web cache directory was accessible. The Web caching feature was available. |
|
Recommended action |
No action is required. |
WEBCACHE_INAVAILABLE
|
Message text |
Web caching is not available. Reason: The Web cache directory is not accessible. |
|
Variable fields |
None |
|
Severity level |
6 |
|
Example |
WEBCACHE/6/WEBCACHE_INAVAILABLE: Web caching is not available. Reason: The Web cache directory is not accessible. |
|
Explanation |
Because the Web cache directory was not accessible, the Web caching feature was not available. |
|
Recommended action |
Use the file-directory command to specify a Web cache directory that is accessible. |
WIPS messages
This section contains WIPS messages.
AP_CHANNEL_CHANGE
|
Message text |
-VSD=[STRING]-SrcMAC=[MAC]; Channel change detected. |
|
Variable fields |
$1: VSD name. $2: MAC address of the AP. |
|
Severity level |
5 |
|
Example |
WIPS/5/AP_CHANNEL_CHANGE: -VSD=home-SrcMAC=1122-3344-5566; Channel change detected. |
|
Explanation |
The channel of the specified AP changed. |
|
Recommended action |
Determine whether the channel change is valid. |
APFLOOD
|
Message text |
-VSD=[STRING]; AP flood detected. |
|
Variable fields |
$1: VSD name. |
|
Severity level |
5 |
|
Example |
WIPS/5/APFLOOD: -VSD=home; AP flood detected. |
|
Explanation |
The number of APs detected in the specified VSD reached the threshold. |
|
Recommended action |
Determine whether the device has suffered an attack. |
ASSOCIATEOVERFLOW
|
Message text |
-VSD=[STRING]-SrcMAC=[MAC]; Association/Reassociation DoS attack detected. |
|
Variable fields |
$1: VSD name. $2: MAC address of the AP. |
|
Severity level |
5 |
|
Example |
WIPS/5/ASSOCIATEOVERFLOW: -VSD=home-SrcMAC=1122-3344-5566; Association/Reassociation DoS attack detected. |
|
Explanation |
The specified AP sent an association response with the status code 17. |
|
Recommended action |
Determine whether the AP has suffered an attack. |
HONEYPOT
|
Message text |
-VSD=[STRING]-SrcMAC=[MAC]; Honeypot AP detected. |
|
Variable fields |
$1: VSD name. $2: MAC address of the AP. |
|
Severity level |
5 |
|
Example |
WIPS/5/HONEYPOT: -VSD=home-SrcMAC=1122-3344-5566; Honeypot AP detected. |
|
Explanation |
The specified AP was detected as a honeypot AP. |
|
Recommended action |
Determine whether the device has suffered an attack. |
HTGREENMODE
|
Message text |
-VSD=[STRING]-SrcMAC=[MAC]; HT-Greenfield AP detected. |
|
Variable fields |
$1: VSD name. $2: MAC address of the AP. |
|
Severity level |
5 |
|
Example |
WIPS/5/HTGREENMODE: -VSD=home-SrcMAC=1122-3344-5566; HT-Greenfield AP detected. |
|
Explanation |
The specified AP was detected as an HT-greenfield AP. |
|
Recommended action |
Determine whether the device has suffered an attack. |
MAN_IN_MIDDLE
|
Message text |
-VSD=[STRING]-SrcMAC=[MAC]; Man-in-the-middle attack detected. |
|
Variable fields |
$1: VSD name. $2: MAC address of the client. |
|
Severity level |
5 |
|
Example |
WIPS/5/MAN_IN_MIDDLE: -VSD=home-SrcMAC=1122-3344-5566; Man-in-the-middle attack detected. |
|
Explanation |
The specified client suffered a man-in-the-middle attack. |
|
Recommended action |
Determine whether the client has suffered a man-in-the-middle attack. |
WIPS_DOS
|
Message text |
-VSD=[STRING]; [STRING] rate attack detected. |
|
Variable fields |
$1: VSD name. $2: Device type: AP or client. |
|
Severity level |
5 |
|
Example |
WIPS/5/WIPS_DOS: -VSD=home; AP rate attack detected. |
|
Explanation |
The number of device entries learned within the specified interval reached the threshold. |
|
Recommended action |
Determine whether the device suffers an attack. |
WIPS_FLOOD
|
Message text |
-VSD=[STRING]; [STRING] flood detected. |
|
Variable fields |
$1: VSD name. $2: Flood attack type. Options include the following: · Association request · Authentication · Disassociation · Reassociation request · Deauthentication · Null data · Beacon · Probe request · BlockAck · CTS · RTS · EAPOL start |
|
Severity level |
5 |
|
Example |
WIPS/5/WIPS_FLOOD: -VSD=home; Association request flood detected. |
|
Explanation |
The number of a specific type of packets detected within the specified interval reached the threshold. |
|
Recommended action |
No action is required. |
WIPS_MALF
|
Message text |
-VSD=[STRING]-SrcMAC=[MAC]; Error detected: [STRING]. |
|
Variable fields |
$1: VSD name. $2: Sender's MAC address. $3: Malformed packet type. Options include the following: · invalid ie length—Invalid IE length. · duplicated ie—Duplicate IE. · redundant ie—Redundant IE. · invalid pkt length—Invalid packet length. · illegal ibss ess—Abnormal IBSS and ESS setting. · invalid source addr—Invalid source MAC address. · overflow eapol key—Oversized EAPOL key. · malf auth—Malformed authentication request frame. · malf assoc req—Malformed association request frame. · malf ht ie—Malformed HT IE. · large duration—Oversized duration. · null probe resp—Malformed probe response frame. · invalid deauth code—Invalid deauthentication code. · invalid disassoc code—Invalid disassociation code. · over flow ssid—Oversized SSID. · fata jack—FATA-Jack. |
|
Severity level |
5 |
|
Example |
WIPS/5/WIPS_MALF: -VSD=home-SrcMAC=1122-3344-5566; Error detected: fata jack. |
|
Explanation |
A malformed packet was detected. |
|
Recommended action |
Determine whether the packet sender is an authorized device. |
WIPS_ROGUE
|
Message text |
-VSD=[STRING]-SrcMAC=[MAC]; Rogue AP detected by radio 1 of sensor [STRING] on channel 149 (RSSI=84). |
|
Variable fields |
$1: VSD name. $2: MAC address of the rogue AP. |
|
Severity level |
5 |
|
Example |
WIPS/5/WIPS_ROGUE: -VSD=home-SrcMAC=1122-3344-5566; Rogue AP detected by radio 1 of sensor ap1 on channel 149 (RSSI=84). |
|
Explanation |
A rogue AP was detected. |
|
Recommended action |
Enable WIPS to take countermeasures against rogue APs. |
WIPS_SIGNATURE
|
Message text |
-VSD=[STRING]-SrcMAC=[MAC]-RuleID=[UINT16]; Signature rule matched. |
|
Variable fields |
$1: VSD name. $2: Sender's MAC address. $3: Signature Rule ID. |
|
Severity level |
5 |
|
Example |
WIPS/5/WIPS_SIGNATURE: -VSD=home-SrcMAC=1122-3344-5566-RuleID=10; Signature rule matched. |
|
Explanation |
In the specified VSD, the packets matching the signature rule are detected. |
|
Recommended action |
Check whether the device is attacked. |
WIPS_SPOOF
|
Message text |
-VSD=[STRING]-SrcMAC=[MAC]; [STRING] detected. |
|
Variable fields |
$1: VSD name. $2: MAC address of the device being spoofed. $3: Spoofing attack type. Options include the following: · AP spoofing AP—A fake AP spoofs an authorized AP. · AP spoofing client—A fake AP spoofs an authorized client. · AP spoofing ad-hoc—A fake AP spoofs an Ad hoc device. · Ad-hoc spoofing AP—An Ad hoc device spoofs an authorized AP. · Client spoofing AP—A client spoofs an authorized AP. |
|
Severity level |
5 |
|
Example |
WIPS/5/WIPS_SPOOF: -VSD=home-SrcMAC=1122-3344-5566; AP spoofing AP detected. |
|
Explanation |
A spoofing attack was detected. |
|
Recommended action |
Determine whether the packet sender is an authorized device. |
WIPS_UNAUTH
|
Message text |
-VSD=[STRING]-SrcMAC=[MAC];Unauthorized client detected by radio 1 of sensor [STRING] on channel 149 (RSSI=84). |
|
Variable fields |
$1: VSD name. $2: MAC address of the unauthorized client. |
|
Severity level |
5 |
|
Example |
WIPS/5/WIPS_UNAUTH: -VSD=home-SrcMAC=1122-3344-5566; Unauthorized client detected by radio 1 of sensor ap1 on channel 149 (RSSI=84). |
|
Explanation |
An unauthorized client was detected. |
|
Recommended action |
Determine whether unauthorized clients exist. |
WIPS_WEAKIV
|
Message text |
-VSD=[STRING]-SrcMAC=[MAC]; Weak IV detected. |
|
Variable fields |
$1: VSD name. $2: Sender's MAC address. |
|
Severity level |
5 |
|
Example |
WIPS/5/WIPS_WEAKIV: -VSD=home-SrcMAC=1122-3344-5566; Weak IV detected. |
|
Explanation |
A weak IV was detected. |
|
Recommended action |
Use a more secure encryption method to encrypt packets. |
WIRELESSBRIDGE
|
Message text |
-VSD=[STRING]-AP1=[MAC]-AP2=[MAC]]; Wireless bridge detected. |
|
Variable fields |
$1: VSD name. $2: MAC address of AP 1. $3: MAC address of AP 2. |
|
Severity level |
5 |
|
Example |
WIPS/5/WIRELESSBRIDGE: -VSD=home-AP1=1122-3344-5566-AP2=7788-9966-5544; Wireless bridge detected. |
|
Explanation |
The specified APs set up a wireless bridge. |
|
Recommended action |
Determine whether the wireless bridge is valid. |
